Quote:
Originally Posted by rvashi
That is exactly my point. People are saying that its Radio 1.47 that is causing issues while I think otherwise. ANd believe me, I've tested many many combinations and the issue seems to be with 2.16 OS ROM and not the 1.47 Radio ROM.
|
Ok, there may have been some misunderstandings here, but the general theory behind the problems since the new ROM was released is this:
2.16 OS causes BT to sound better, however it has a tendency to disable bluetooth at random intervals. Also, some have reported that the D-pad does not work coming out of standby.
1.47 Radio (at least as packaged with the 2.16 ROM) causes problems when the phone is switching in/out of certain network conditions.
Someone may have mistakenly blamed the 1.47 Radio for the Bluetooth shut offs, but it seems that the Radio ROM has very little connection with Bluetooth performance.
I think the problem is that we are all looking at different problems thinking we're on the same page here.
My problem with the 2.16 update was the constant freezing when switching to roam on Verizon (which it does inside any building in my area). The BT shut-off was mildly annoying, but I found it more useable than 2.08, so I would be willing to live with it if my phone weren't frozen everytime I take it out.
You seem more concerned with BT stability.
Switching to a different Radio ROM (1.40) while using the 2.16 OS fixes my lockups issue, and 2.16 was fairly stable aside from BT mysteriously turning itself off. At least the device wasn't frozen!
Using the 1.47 Radio on any other ROM that I've tried also froze it (Alltel, the plethora of customs, etc...). Now, I'll admit that I didn't try it with 2.08, so its possible that whatever conflict existed in other OS versions didn't exist in 2.08... however, I don't really see what the point is in doing this.
I never tried it with 2.08 because, well, I didn't see any reason to. The new one had more problems than the old one, so why keep any of it at all? All the visible improvements (BT sound quality, alarms) were in the OS, not the radio.
As far as I know, 1.47 did NOT add any better signal (especially compared to 1.40, which was still negligible compared to the prior version if any at all), and had rumored battery benefits in fringe areas. However, you're taking a chance with radio code that DOES freeze on some configurations, so why bother for a possible "advantage" that you'll probably never notice?
I'm curious, has anyone found that the 1.47 works better with 2.08 than the original setup?
Quote:
|
Originally Posted by Gilliland
Just for the record, I've got 2.16 and 1.47, and I'm having no problems whatsoever with Bluetooth or lockups. I know that a lot of people are having trouble with that combination, but it seems to be working fine here. I've gone in and out of EVDO, 1X, Roaming, etc, with no problems. The phone sleeps, wakes, no problem. Bluetooth stays on, works correctly.
...
And I don't mean to imply that I have absolutely no problems. I have several pieces of software that simply won't run on my phone, foremost among them is Microsoft Live Search (which fails with a "Native Exception" whenever I try to start it). And I do occasionally (every few days) find myself in a situation where the phone seems to need a reboot, but that's happening at about the same frequency that it did under 2.09, so there's nothing new there.
|
That, my friend, sounds like a contradiction. You claim that You need to reboot with the same frequency as under 2.09?? That should have set off a red flag... you're not supposed to reboot so often!
There might be something wrong with your device because I hardly remembering having to reboot my stock mogul rom without reason (mucking around in the registry, etc). The new combination introduced new situations for it to freeze for most of us, and I am able to recreate it at will.
Do you live in an area with a strong verizon signal?
Try forcing your phone into roam-only, or if in a 1x area, force EVDO service only. You might have no problems because of geographic location... it seems to depend on what networks your phone is switching to, but forcing actions like this successfully simulated the problem on everyone's phone I tried.
I'm happy its working for you in your situation, though. I wonder if all the sprint techs live in an area like yours which would explain why they didn't anticipate this.