guys,
I've issued this before in the rom specific thread, and searched for it, but no answer... (well, partially, but sure don't hope this is the answer; http://forum.xda-developers.com/showthread.php?t=835547)
When connected to bluetooth (streaming to my audio installation) and wifi on, when the signal drops, rosie freezes... only given time it unfreezes (after pressing the trackpad to wake and unlock and a loooot of time)...
It's quite an annoying error, and I seem to experience it with all gb roms...
It becomes more strange... when wifi on, and checking bluetooth on in wireless settings, wifi drops out... and gets on again...
Anyone any idea? It's kinda driving me nuts... now running the 3d version of acesmod007, but also experienced it on other roms...
- could it be gb related?
- could it be rosie related (somehow?)?
- could it be the radio (see signature)
- could it be kernel related?
- could it have anything to do with the build of the rom?
- could it have something to do....?
many thanks in advance...
Related
I am troubleshooting the SOD issue, and was wondering if anyone is / has been experiencing this problem when NOT using bluetooth (you get SOD when your bluetooth is turned off)?
In the meantime I am checking to see if auto updates set to "on" in Facebook / Twitter / or Weather could be the culprits.
mmicha said:
I am troubleshooting the SOD issue, and was wondering if anyone is / has been experiencing this problem when NOT using bluetooth (you get SOD when your bluetooth is turned off)?
In the meantime I am checking to see if auto updates set to "on" in Facebook / Twitter / or Weather could be the culprits.
Click to expand...
Click to collapse
sorry mmicha - when I was getting the sod I changed roms until I found a version without a problem. recently I've used roms with sys builds 23541 and 28232 running bluetooth as well as auto updates without any problems.
I once had the SOD with using bluetooth a while back (when paired with a rental car's BT stereo), but yesterday started getting it every time phone goes to standby (without using BT) - only soft reset/removing battery helps. I have made no changes to registry or even installed apps in the last couple of weeks so have no idea why it is happening. Continuing to search forums at the mo...
BTW: Stock 6.5 WWE ROM
SOLVED: Turns out it was SRS WOW HD causing the SOD as no had it once since uninstalling. It was strange as I had installed it days/week prior and the SOD just happened suddenly when I hadn't even used SRS or my music player at all that day!?
Hi all,
I have a problem with my GPS signal.
Normally (pre rooted era) I could switch on the GPS and get a fix. No freeze whatsoever.
With Gingervillain 2.1 I switch on the GPS and check the signal. I see several bars before the signal freezes. Tried flashing different radios but this made no difference. Also tried several radio / ril combinations same result.
At this moment I found a sort of workaround by switching on Google navigation and then switch on GPS. Check the signal with GPS Status and u usually get a fix within a minute (even indoor). After that I switch on Navigon to start driving.
It is not really a problem this way but what can I do to solve this problem. When I look in the threads (CM7 / Gingervillain) the GPS problem should be solved. Are there more people with this problem? What could be the best solution.
I have CM7 and no issues. I don't know what the problem is. Could be the rom, could the radio, could be other problems. It is too vast really. The only way you could fix it is to try different roms and see which one works. But like you said its not much of a problem.
Sent from CM7
Thanks for the reply,
Yesterday I switched to the latest radio (32.56.00.32U_5.17.05.08) and RIL (2.2.1003G).
As long as I start Google Navigation first and then switch on GPS no problem. This morning I drove to work with Google and Navigon switched on, no problem (30 min drive). Even switched off Google and Navigon kept the signal, no problem.
Whenever I switch on GPS first it looses track somehow. Can't figure it out..
Is there some keep alive GPS flow in Google Navigation?
No. When you turn GPS on its just on and idles. It needs to be used but I don't get how it doesn't work right. Grab an app from the market, GPS essentials I think and see what you can do with that.
Sent from CM7
With GPS essentials it works, better than GPS Status (think it has monitor function only). Think it has something to do with keeping GPS alive
Tried it from work - home, worked fine. Went shopping same procedure...
Might also be engergy savings mode in Ginger Villain. Batterydrain is less with it I noticed.....
With this working... perfect ROM!!!
Hi guiz!
I installed CM9 on my HOX. But besides the known bugs with that, i also have issues with the bluetooth and GPS software.
Bluetooth simply wont turn on; when i pull/push the slider it keeps going back to 'off'...
GPS wont turn on either; when i open any form of navigation it keeps saying 'searching for gps signals', and the little icon in the top bar doesn't show up. and yes, i have turned on the internal GPS in the options
although its not like i can test with a bluetooth gps now can i ^^
A lot of apps crash, too. Could be instantly, could be after 20 seconds, but they all crash with the 'has stopped working' or something alike. Kindof hard to use the phon this way. Stock rom didn't have those issues in the brief time i used that.
I can't ask this in the CM9 [WIP] forum, being a newbie and all. So I hope someone here can help me? Is my HOX different? Why it no work!?
Oh yeah, i have the international HOX, so the Tegra 3 one.
Nobody has any idea's on this? Flashed the kernel again, uploaded the new CM9 alpha 7. Still the same errors. Crashing seems less often; but still not bluetooth nor GPS :/
When using ANY android version beyond 2.3.5 my DHD is experiencing freezes when I turn on WiFi. The behavior is exactly the same from ROM to ROM:
Turn on WiFi and as soon as it makes a connection to the router the entire OS grinds to a glitchy halt. The only way to use the phone again is reboot by battery removal then turn WiFi off.
I have tried Wifix, radio changes, different Kernels, returning to stock (more than once), turning off WiFi battery optimization, checking antenna and many other supposed fixes with no change in behavior.
Attached are two logcats from when this happens. Hopefully someone can make sense of them and see the error because my basic coding knowledge doesn't help me much!
BTW, WiFi Tether was turned off during these logcats but works in general. This issue has me puzzled.
deleted
SOLVED.
This turned out to be caused by a tiny crack on the WiFi antenna (on the battery cover) located just beneath where the contacts are situated. A little bit of solder has fixed it and now WiFi works on every ROM again. Hope this helps someone.
Hi all,
I was wondering if anyone else was experiencing this, and/or had any solutions - as it's slowly driving me mad.
I do love my M8, but it's getting old and slow running Sense 6/7, and I much prefer the 'pureness' of GPe/CM12.
My phone is SuperCID'd and fully unlocked, and currently flashed the latest RUU for GPe (full firmware) then Candy5 ROM v2.5.5 flashed (based on CM12).
I've tried various Sense firmwares, and other hacked/full GPe firmwares... Bluetooth seems the same on all - works fine on Sense, but not as reliable on non-Sense.
The biggest issue I have is that I have a LG G Watch R and it will disconnect after a few hours, sometimes days, and won't reconnect unless I turn off and on Bluetooth on the phone. Even then it's temporary - I find Wiping Data on com.share.bluetooth makes it stable again for a few more hours/days.
And no, it's not the watch, as if I'm in the car at the same time - that will disconnect and not reconnect either. It's definitely the phone...
Now I generally keep Bluetooth and WiFi on at all times. I only use WiFi at home.
I have noticed it seems to become unreliable if WiFi is on, but hasn't been connected to anything for a while. It's almost like it's "scanning" buffer is full and it's affecting both WiFi and BT (as it's the same chip).
If I keep WiFi off, and only on at Home where it stays connected - my Bluetooth seems really reliable and I don't have an issue.
This isn't a fix, though. As I don't want to have to rely on Llama to switch my WiFi on and off based on my location. Surely a potential battery drain versus just keeping it on at all times.
I've tried a Tasker task to wipe com.share.bluetooth every couple of hours, but it didn't fix it. Would still die beforehand.
I've tried various GPe ROMs, and CM12 ROMs - all as Clean Flashes and not restoring Bluetooth data in Titanium Backup (I only restore user aps + data).
Just wondered if anyone had any ideas!!
Thanks for reading.
I'm having the exact same issue.
Gpe and sense work fine, but cm12,1 just won't stay connected to my car or watch. Very frustrating.
I really want to run cm as my daily driver, but it's totally incapable of keeping Bluetooth up.
Is anyone running cm 12.1 and has working Bluetooth? If so, can you let us know which radio firmware you're using?
I took a stab in the dark and applied firmware 4.16.401.10. So far my watch's connection has been solid. Still haven't tested the car, but will test today. Hopefully it'll be stable - if it is then I'll finally be able to use CM as my daily driver!
Full commute without Bluetooth disconnecting from my car, and I've had a solid connection to my watch for over 24 hrs! WOOOOOOOT!!!!
4.16.401.10 is the trick. Anyone having Bluetooth issues on CM12.1 should go download and apply the firmware. (must be s-off, obvs.)
Firmware is here (courtesy of Mike1986 of ARHD fame)
Ah great news - thanks.
I'll give it a go later!
Should know within 15 mins after if the bug is fixed!
Thanks again.
Update - looks like that's the fix!
Strange it doesn't seem to be mentioned anywhere else but at least it's now here for anyone else.
Thanks for the tip!