I installed 4.2 and am having problems connecting my bluetooth device. I have a blackberry 8700c paired to my bmw 3 series vehicle. It worked fine with 4.1. It was not working so I paired it again and the connection is there.

Everytime i turn on the BB and it begins to connect I get this error, "javalangClassCastException". Once I click "Ok" the bluetooth connection is lost.

Anyone have any idea what this error is and how I can fix it? If I can't get this to pair properly, I will have to revert back to 4.1

Thanks

Jim

I am a Java developer. The ClassCast exception occurs when the wrong type of object is passed. This is almost likely due to a software version incompatibility. Either there are still some 4.1 modules on the BB conflicting with the 4.2 ones. Or what ever you are connecting to via bluetooth is returning data in an format unexpected format for 4.2


Check the modules version by going to Options > Advanced Options > Applications. Scroll though the list and see if any of the modules are not 4.2.

Either way reverting to 4.1 is probably your only option.

I did as you said in your response and don't see any 4.1 apps. The only thing additional installed was the mds runtime. Not sure why i added it but i did

The other apps on there are

fidelitylink 1.0
gmail 1.0
ubs 1.0.7 (not sure what this is)
pocketday 4.25
ramble 0.9.10.8
texas holdem 2.1.7
timezoneotapatcher 2.2

Other than that it is the 4.2 installation. Thanks for your assistance.

Jim

Ahhh. It could be that one of those apps is not compatible with 4.2. Can you try removing them to see if that removes the error?

I will do that. The only one that I don't know what it is the ubs app. Any idea?

Thanks,

Jim

anyone know how to fully wipe ur bb and start again..i have the same issue but cant get desktop mgr to connect now

I get the java.lang.classexpection error for some of the pre-loaded ringers. Still trying to figure it out. My desktop manager isn't working either.

What version of the JRE/JDE is installed on the phone? This is starting to sound like an issue with generics type enforcement.

To check if any 4.1 "modules" are present you need to go to the application screen and then select "modules" from the menu. This will show you all the modules loaded (there will be tons). This is where you check to see if any modules from the handheld 4.1 code are loaded....

SMF

Hi all, I'm having the same problem with my BB when it connects to my Parrot CK3100 bluetooth device since I upgraded to v4.2. I've tried different versions of v4.2 without results. It works fine with another bluetooth carkit I have in another car. If I can't find a solution I'll have to revert back to v4.1. I've checked that all the modules are at v4.2.1

My JAWBONE bt headset works just fine

Go to settings, options, Security options, general settings, click wheel and choose "wipe handheld". Be careful because if your setup with a BES account you'll need to reactivate the device with a password.

I would recommend this for the original post here as well. Always good to start with a fresh install for anything.

Has anyone been able to fix the bluetooth problem by wiping the device and reinstalling v4.2.1 from scratch? If so, I'd be interested in knowing the procedure. Or anyone has found another fix?

Thanks!

EDIT: Found a possible solution in another thread... I'd post a link to the thread, but I don't know how to do it... ;)

Please point me in the direction of that thread.

i experienced all the problems you are speaking of, and by switching to this version, they are all fixed: 8700M_PBr4.2.1_rel108_PL2.3.0.59_A4.2.1.66_Telefon ica_VE

i can use with all of my bluetooth devices: laptop as a modem tether, nav system for traffic, headset (moto h500)

Anyone tried the last v4.2.1.155/v4.2.1.96 and can tell me if it solves the problem?

Thank!

i installed x.x.96 and my bluetooth problems remain... it was actually working fine with x.x.66, but with x.x.96 its no good....

Wirelessly posted (BlackBerry8700/4.2.1 Profile/MIDP-2.0 Configuration/CLDC-1.1 VendorID/100)

Never had BT problems. What exacly causes this problem maybye you just have a faulty headset.

headset works fine... thats not the issue... read the thread