11-11-2007, 01:56 AM
|
||||
|
||||
|
It's been more than 24 hours and this solution is still working fine for me. (2.16 ROM, using Effcmom instead of Comm Manager to switch BT. ) I can't offer a technical explanation for why this would work, but it does seem to be working.
Zero d-pad lockups. Zero BT disconnects. Zero systems freezes. The phone now wakes up and sounds alarms while charging. I can have conversations through the BT headset now. BT headset is usable -- a little muddy, not crystal clear, but not choppy like it was before. Possibly a different headset would work even better. Free RAM has fallen to 18.64 megs, but that's without soft-resetting at all in over a day and not using Oxios or any similar memory-reclaiming utility at all -- just closing out programs. If the situation holds, then this Mogul has pretty much finally become the device that I was expecting when I bought it. ... Hey, Sprint, hang onto that Touch for a few more days until further notice. edit: Just ran Oxios now for the first time in this experiment, and it upped free RAM to 20.44. So far, it really seems like the memory leak has been somewhat abated with this 2.16 configuration vs. any other ROM that I've tried. Last edited by veblen64; 11-11-2007 at 02:04 AM. 
|
|
11-11-2007, 08:44 AM
|
||||
|
||||
|
The only update I have is that I did, actually, have a d-pad lock-up, yesterday. It went away by itself after a few minutes and there have been no other of the reported problems with the 2.16 ROM. This will, definately, do me until any other ROM update comes out.
matt
__________________
........ and the moral of the story is: "you can't have a drink on the house"
|
|
11-11-2007, 07:09 PM
|
||||
|
||||
|
I'm running 2.16 as well and was having constant BT issues where it would shut off. I read this thread so I'm now trying effcomm. It's been a couple days, and BT stays on a bit longer than what I remember, but it still does shut off on it's own. I wish I had the same luck you guys are having.
|
|
11-11-2007, 09:09 PM
|
||||
|
||||
|
I just wanted to report that using this fix with the sfaure 2.16+TouchBT ROM has helped slightly. I am no longer experiencing the DPad bug but my BT still disconnects if the device goes idle with my headset active. If I'm on a call and the device goes idle the audio gateway will stay connected, but as soon as the call ends BT shuts off. At least now, the BT radio actually shuts off. Before when the BT would shut off the icon would still show it as on in the CommManager.
I am going to try updating my radio version from 1.32 (Telus WM6) to 1.40 and see how it goes. If that doesn't fix it for me I will be trying the Qwest 2.13 ROM that was posted recently. ~Scuzzell
|
|
11-15-2007, 09:43 AM
|
||||
|
||||
|
Okay guys, after days of testing since my last post (probably a week ago), I am still experiencing the Bluetooth radio shutting itself off. I have the little bluetooth icon at the bottom (in the system tray) and that says bluetooth is still on but I don't have a Bluetooth LED and the EffComm plugin says its turned off.
At this point I am not sure if there is any possible solution to this issue as DCDs ROM (including the hybrid Touch-Mogul ROM) is going through the same issues. The only ROM that I haven't tried now is the Quest ROM. Maybe I'll try that later but just getting tired of installing all programs and then having to restart all over again after a few days. If anyone wants, I'll post a list of programs that I have installed.
|
|
11-15-2007, 06:09 PM
|
||||
|
||||
|
FWIW, I tried the Qwest ROM for a couple of days and didn't have any BT turnoffs or dpad lockups.
|
|
11-16-2007, 10:04 AM
|
||||
|
||||
|
Can you report Free Storage and Program Memory upon reset? Have you had any memory issues whatsoever?
|
 |
|
«
Previous Thread
|
Next Thread
»
Linear Mode
|
|
All times are GMT -4. The time now is 08:16 PM.
