Possible relief for the d-pad and bt issues w/2.16 ROM

[livejazz]

This is very early in trial stages, but 8notime "touched" the survace of this fix before jumping ship to the new Touch. He found that the bt and d-pad performance issues were greatly reduced by running the SBSH PhoneWeaver application. I downloaded the trial and, behold! Not one single freeze or d-pad lock-up and my bluetooth has been turned on the whole time. I have two routes that I can drive to work. One takes me through a Verizon and an Alltel exclusively branded coverage areas and the other takes me through two GSM branded areas without EVDO (obviously). I have driven both ways since yesterday and, still, no freezes or bt problems or d-pad lock-ups.

All the glory for this find should go to 8notime. There are a couple of us who are reporting on the success. I am not, by any means, endorsing this. Anybody interested might just want to give it a try, though. I don't mess with any of the settings. Just install it an leave it in the "Day" profile with bt turned on from the today plugin. Good luck!

matt

[Alpine-]

Hopefully someone can figure out what it is that SBSH PhoneWeaver "seems" to be doing in order to remedy this. I know I personally dont want to run PhoneWeaver...

It could give some valuable clues though. You should post this in SBSH's forums as well and see if there is any feedback.

[livejazz]

I know what you mean. I was nervous about running another app as unstable as this device is, but I figured it really wasn't doing a whole lot, memory wise, and was not not very invasive in general. So I did a backup and took the dive. Glad I did, so far. I'll know a lot more, tomorrow, because I'll be putting on a lot of miles using bt for everything (phone, music, gps). It'll be a good shake down cruise.

matt

[TheMostToys]

After seeing 8's post, I've been using "togglebth" and have not opened comm manager and my D-pad has been working perfectly (not the case when using comm manager.)

[sfaure03]

most likely its keepting the phone "alive" and not going down. I tested for a whole day, walking around playing mp3's, never a disconnect. wasnt until i quit listening to music that i had issue.

Phone should be able to go into sleep modes w/o the bluetooth munking up. It can NOT do so.

The preliminary on the Touch is that the bt works. The preliminary on the 2.16 patch was.. OH GREAT ITS ALL FIXED. 2-3 days later the complaining began. We shall see what the outcomes are there.

[holo]

I always install this app and I had it on 2.16 and still had all the issues with lockups and BT shutting off...

[sprintdude07]

lockups are due to the radio.. im convinced to that after i downgraded the radio as I was restarting my phone almost 5-10 times a day.... now the bt issue is a whole another issue in itself.

[veblen64]

I reflashed the 2.16 ROM to check this out. I haven't loaded a third-party ap to switch BT on and off though. I've been turning BT on and off through the old-fashioned "settings" route, avoiding the Comm Manager method. So far everything seems to be working flawlessly. That's after only about six hours of testing, however.

Could the BT on/off toggle in Comm Manager be causing many of the 2.16 ROM's problems somehow? Weird. Previously when I tried the 2.16 ROM, and as soon as I started using BT, the problems began, including d-pad lockup. D-pad is working perfectly this time, so far.

[freeza]

LOL i haven't used comm manager one time since i got my phone ( i remapped the button to something else ) and i got the d-pad issue moments after installing the 2.16 rom.

Trust me, it has absolutely nothing to do with comm manager at all.

[veblen64]

You're right!

I just logged on to report that my d-pad locked up. So fuggetaboutit. ... THIS IS NOT WORKING ON MY MOGUL AFTER ALL ... Now am flashing to, oh let's see ... something in an Alltel ROM perhaps. Thursdays are good days for an Alltell ROM on the Sprint Mogul.