[Scott Spillers]

Originally Posted by ffejie

Does anyone think that 4.5.0.x is ever going to go official with the CDMA carriers? The 8830 seems to be a dead device at this point with all the rumors about Niagara. I'm still running 4.5.0.77 (which seems really slow) because I don't want to go through the upgrade process to 101, only to have to go through 127 or the official version in just a few weeks. Any hope for me to get 127 or the official version anytime in 2009?

The upgrade from .77 to .101 is painless and very much worth your while. You do not have to copy any files or make any modifications, everything just works.

[ScienceRules]

The 8830 has some unique problems that in general are not carrier specific and are being addressed by RIM. It's been incorrectly reported that since the 8830 betas have been made available to the carriers, that its the carrier that is holding things up. Not true. The availability of beta code to carriers and partners does not imply that the code is ready for prime time. A good example of this was bundle 138 - Platform 3.4.0.7, Apps 4.5.0.101. The media player was big-time broken.

The good news - Contrary to some rumours, 8830 4.5 production-grade code will be released.

I have been running 4.5.0.119 apps with platform 3.2.0.51 for a few weeks now with no major issues. Yes, you can mix and match apps with platforms (OS SFI code) if you know what you are doing.

sR

[wirelessgogo]

thats not the best way to do it!!

[ScienceRules]

Originally Posted by Xopher

Has the full-screen video bug from .101 been fixed in .127?

I'm running .119 with platform 3.2.0.51 and full-screen video works ok.

I'm not sure about the newer shipping platforms - 3.4.0.x

sR

[sibermage]

I am running version 4.5.0.127 (177) on an 8830 CDMA
Platform is 3.4.0.20

I haven't come across any issues so far. My only gripe is that memory tends to go down to about 2.5 megs. Right now, the phone is at 4.2 megs

Only apps installed are Opera mini; Gmail Apps (Gmail & Google Maps)

Also, I'm on BES.

Note: Rogers is not my carrier

[ScienceRules]

sibermage,

Thanx for reporting in.

sR

[HungrySage]

Shoot! You got 4.5.0.127 for your 8830! Searchin time!!!

[Bozo2007]

dont bother.

[mscooley]

visit www dot blackberry dot com/upgrades

[cjmac49]

This site redirects one to the official Verizon, in my case, software site which is still on 4.2.

[HungrySage]

Originally Posted by Bozo2007

dont bother.

[ScienceRules]

I've upgraded to the 4.5.0.131 apps using platform 3.4.0.7. It's been over 24 hrs and I have not encountered any major issues.

For the adventurous among you here's how it's done:

1) Install the 4.5.0.101 8830 distribution to the desktop

1a) Install the 4.5.0.101 device software on your 8830 (not absolutely necessary, but recommended)

(If you are already running the 4.5.0.101 apps on your 8830 you you would start from step 2)

2) Install the 4.5.0.131 8330 distribution to the desktop

3) Create a Java2 directory under 8830-v4.5.0.101_P3.4.0.7

Your directory tree should now look like this:

8830-v4.5.0.101_P3.4.0.7
CDMA
Java
Java2

4) Copy all the 8830 Java directory files to Java2 (for backup/recovery)

5) Copy all the 8330 Java directory files to the 8830 Java directory and allow overwrite.

At this stage the 8830 Java directory includes all of the 8330 cod files and these additional cod's which remain from the initial 8830 desktop install performed step 1.

net_rim_tcp_options.cod
net_rim_se13nettable.cod
net_rim_bb_simphonebook.cod
net_rim_bb_addressbook_simapp.cod
net_rim_bb_help_cdma_gprs__en.cod
net_rim_bb_help_wizard_images_8800.cod

Don't worry about the cod's that don't apply (camera, video, etc). The loader logic will key off of the 8830 ALX files and prevent them from being installed.

6) Invoke Desktop Manager or Loader from the command line to execute the upgrade.

Verbose logging is always useful - create or modify these two entries in registry under the Loader key

HKCU\Software\Research In Motion\BlackBerry\Loader
CFPLogLevel 0x6 dword
RetainLog 0x1 dword

With these two values added, a verbose log will be created in your temp directory.

sR