[penguin3107]

I had been using an 8703e on 4.1.3 BES (Lotus Domino).
Everything had been working fine on it.
I have a Software Configuration which pushes out the following apps with no problems:
Berry411 (Beyond411)
VNC+
Idokorro MobileSSH
Google Maps

Today I received an 8830 to replace that 8703e.

Using Blackberry Manager, I sent an 'Erase & Disable...' to the 8703e.
That finished fine.
Activated the 8830.
That went fine as well.
E-mail and wireless PIM sync are all OK.

The problem is the Software Configuration.
Currently, on the 8830, it's saying everything is Up To Date however no apps have been pushed to the device.
I refreshed a few times, but it's stuck on Up To Date.

Could this be related to the new Handheld OS (4.2.2) on the 8830?
Maybe those applications are simply not compatible with the 8830?
Are there any other things I should be looking at with regards to troubleshooting this?

[Frank Castle]

Having the same issue here ... I have the 8800 OS loaded but the 8830 OS is newer and it's not available to download yet.

Also I can't get any of the screenshot programs to work ..

[John Clark]

Originally Posted by jletendre

Also I can't get any of the screenshot programs to work ..

Opitronic said that the screenshot issue is due to this early OS. He said on future OS's his screenshot app will work. If I can find the thread I'll post it back here.

Edit: Here it is: http://www.blackberryforums.com/gene...tml#post538226

[Flying Dutchman]

I'm fairly sure that you need to put the latest device.xml file on your BES server for wireless apps pushing to work. The files is stored in c:\program files\common files\research in motion\apploader\. I noticed that only the 4.2.2 Desktop Manager that ships with the 8830 has an up to date device.xml file with the 8830 defined in it. So install the 4.2.2 Desktop Manager (or grab it from the data1.cab install files) and overwrite the one on your server. While you're at it I would copy the vendor.xml as well.

[jibi]

bing bing bing.

[penguin3107]

Originally Posted by Flying Dutchman

I'm fairly sure that you need to put the latest device.xml file on your BES server for wireless apps pushing to work. The files is stored in c:\program files\common files\research in motion\apploader\. I noticed that only the 4.2.2 Desktop Manager that ships with the 8830 has an up to date device.xml file with the 8830 defined in it. So install the 4.2.2 Desktop Manager (or grab it from the data1.cab install files) and overwrite the one on your server. While you're at it I would copy the vendor.xml as well.

Right on! This is exactly the reply I was looking for.
Thanks, Flying Dutchman. I will give this a go when I get into the office today and report back for anyone else interested in this issue.

[penguin3107]

Well... I guess it's progress... but not exactly working just yet.
Installed the 4.2.2 DM and took the device.xml and vendor.xml files and overwrite the server copies of those files.
Re-indexed using 'loader.exe /index' just for giggles.

The device configuration status on the 8830 now changed from 'Up to Date' to 'Downgrade Required'. Downgrade? Never saw that one before... and it has me slightly nervous.
How can a downgrade be required on an application that doesn't exist on the device yet?
Should I restart the entire BES at this point?

I'm just going to let it sit and see if it clears itself up

[penguin3107]

UPDATE: OK, ignore previous post.
I forgot that I had manually installed Beyond411 (3.91) and removed it a day ago.
When I deleted that app shortly after installing, it looks like the icon was removed, but the module remained on the device. Removed the old module, and all is well.

Device config status now reads 'Install Required' as it should.
Hopefully those apps will push out shortly.

[jibi]

FWIW, the new entries for the Device.xml, for those who don't have DM 4.2.2, is as follows:

        	<!-- 8300 -->
		<os radio="GPRS" series="8300" Colour="True" Theme="Normal" JVMLevel="1.0" Camera="True" VoiceNotes="True" pttApp="True" Memory="Large" KeyboardType="Qwerty" Sound="Tunes8700g" SystemSize="normal" Bluetooth="True" MMS="True" ThemeSupport="Enhanced" VAD="True">0x96000F03</os>

		<!-- 8830 -->
		<os radio="CDMA-GPRS" series="8800" Colour="True" Theme="Normal" JVMLevel="1.0" Memory="Large" KeyboardType="Qwerty" Sound="Tunes7130c" SystemSize="normal" MMS="True" Bluetooth="True" VAD="True" ThemeSupport="Enhanced">0x04000E04</os>

If you just want to open your Device.xml file and add those two entries somewhere, it adds support for the 8830 and 8300.

[penguin3107]

All applications just pushed successfully.
Thanks for the help, everyone.

[Marylw]

Thanks from me too! That's exactly what I was looking for!

[dmbascfan]

Originally Posted by penguin3107

Well... I guess it's progress... but not exactly working just yet.
Installed the 4.2.2 DM and took the device.xml and vendor.xml files and overwrite the server copies of those files.
Re-indexed using 'loader.exe /index' just for giggles.

The device configuration status on the 8830 now changed from 'Up to Date' to 'Downgrade Required'. Downgrade? Never saw that one before... and it has me slightly nervous.
How can a downgrade be required on an application that doesn't exist on the device yet?
Should I restart the entire BES at this point?

I'm just going to let it sit and see if it clears itself up

I'm having the same issue right now. I assigned a brand new software config to a device that never had the app before. Initially, it showed "Up to Date" yet the app did not exist on the device. This had been going on for days and I finally called RIM. they suggested to reboot the BES and if that didnt fix it, do wipe the handheld and reinstall the OS. So, I rebooted the BES on Friday and come Monday, still no app. I wiped the handheld and upgraded the OS. I assigned the software config again and how it shows "Downgrade Required". This is an 8700c running 4.2.1

I then assigned the software config to another handheld which never had the app, and the status immediately showed as "Up to Date". I'm checking the POLC logs and I dont even see the BES queuing this software for delivery.

I've read, and re-read all of the threads on pushing apps and I cant seem to find a culprit. HELP!!!

[BSquared]

Originally Posted by dmbascfan

I'm having the same issue right now. I assigned a brand new software config to a device that never had the app before. Initially, it showed "Up to Date" yet the app did not exist on the device. This had been going on for days and I finally called RIM. they suggested to reboot the BES and if that didnt fix it, do wipe the handheld and reinstall the OS. So, I rebooted the BES on Friday and come Monday, still no app. I wiped the handheld and upgraded the OS. I assigned the software config again and how it shows "Downgrade Required". This is an 8700c running 4.2.1

I then assigned the software config to another handheld which never had the app, and the status immediately showed as "Up to Date". I'm checking the POLC logs and I dont even see the BES queuing this software for delivery.

I've read, and re-read all of the threads on pushing apps and I cant seem to find a culprit. HELP!!!

Similar problem with delivering software to devices with the 4.2.1.x firmware update on 8800, 8100 and 8700 BBs. One software config applied to a number of users, who have received OTA applications before. Application not delivered and the POLC log shows no sign of the queuing the software for delivery. Will try reverting to 4.2.0 firmware on one device and see what happens. Interested to know if anyone else has had this problem and how it was resolved.

[Ugg]

If the POLC log doesn't show it queuing I'm guessing that the server thinks that the handheld is up to date already, rather than there being any problem with the handheld.

Maybe try (possibly to one device first) a software config that removes the app and then another to to reload it?

[RGOMike]

Originally Posted by jibi

FWIW, the new entries for the Device.xml, for those who don't have DM 4.2.2, is as follows:

        	<!-- 8300 -->
		<os radio="GPRS" series="8300" Colour="True" Theme="Normal" JVMLevel="1.0" Camera="True" VoiceNotes="True" pttApp="True" Memory="Large" KeyboardType="Qwerty" Sound="Tunes8700g" SystemSize="normal" Bluetooth="True" MMS="True" ThemeSupport="Enhanced" VAD="True">0x96000F03</os>

		<!-- 8830 -->
		<os radio="CDMA-GPRS" series="8800" Colour="True" Theme="Normal" JVMLevel="1.0" Memory="Large" KeyboardType="Qwerty" Sound="Tunes7130c" SystemSize="normal" MMS="True" Bluetooth="True" VAD="True" ThemeSupport="Enhanced">0x04000E04</os>

If you just want to open your Device.xml file and add those two entries somewhere, it adds support for the 8830 and 8300.

Thanks Jibi,

That was simple and it worked.

Cheers,
Mike

[jibi]

FWIW, I started getting the 'Downgrade Required' message yesterday for a new application. Looks like the bozos decided to include net_rim_bbapi_invoke.cod as part of the installation. This is standard fare for OS 4.1.x and above, if I'm not mistaken (possibly OS 4.0.x and above). Needless to say, their versioning it 0.9 versus the installed 4.2.2.x caused Application Loader to want to downgrade that file in order to install the others. I removed the COD from the installation package and it's reference in the ALX file, re-indexed the application and it pushed immediately from the BES to my device.

Just something to look at for those who get the 'Downgrade Required' message in the future.