Hi guys I'm experiencing deep sleep issues. Sometimes my phone won't wake up. I have to keep pressing the power button for 10 seconds for the phone to reboot. It usually happens when the phone is in my pocket while I'm driving (it's paired to my car). I'm thinking there's an issue with the bluetooth pairing. I had the same problem with my s3 but it stopped when I disabled bluetooth. I'm running latest stock rom with Perseus kernel. Anyone else with same issue?
Swyped from another galaxy
I experience similar problems when I connect a bluetooth keyboard and a mouse at the same time. Usually everything works flawlessly, but after some use the phone rejects to get out of sleep. I can only resolve this by taking the battery out.
Need to investigate more. But my s3 hasn't been paired with my car for months and I haven't experienced any lockups since then. I'm sure it's the same issue on the gn2
Swyped from another galaxy
OK 2 days with bluetooth off= no reboots or lockups. So I'm assuming bt needs some fixing
Swyped from another galaxy
Try uneak or redpil kernel
Related
So I've been having some random reboot problems that surface every once in a while. They happened when I was on stock and now when i'm rooted running Gummy. The only way that I can consistently predict the reboot happens when im using Navigation. About 3-5 minutes after my location has been found, the phone will restart. It doesn't get that hot, or seem laggy.
Anyone else having this issue? This is happening with various kernels, governors, and voltage settings.
Skoogusmaximus said:
So I've been having some random reboot problems that surface every once in a while. They happened when I was on stock and now when i'm rooted running Gummy. The only way that I can consistently predict the reboot happens when im using Navigation. About 3-5 minutes after my location has been found, the phone will restart. It doesn't get that hot, or seem laggy.
Anyone else having this issue? This is happening with various kernels, governors, and voltage settings.
Click to expand...
Click to collapse
GSM? CDMA? Refurbished? New? Since when? Have you tried exchanging it?
CDMA, new, bought off wirefly so I don't feeling like dealing with replacements since I'd have to wait for it. The GPS problem has been around for a while, but is more prevalent now. Once it does restart though, it works fine and doesn't restart again.
what navigation software are you using.
I had this kind of issues with copilot, i switched now to Sygic and have no issues anymore. What I found out is that in my case it seems to happen more frequent when i have Bluetooth enabled.
Just bought a nexus from Verizon, on my second device now. First device was exchanged after 1 day, battery ran out in 6 hours, never held signal for more than 2 min. Second device is a refurb, phone worked great and had ZERO issues until updating to 4.0.4. Came with 4.0.2 on it, put off the update for several days to see if it worked ok. Everything ran smooth and fast, great battery life and signal. Immediately after the update, phone now hangs and freeze when unlocking, switching home screens, open app menu etc. Phone also seems to randomly think a headset is plugged in and will not make any sounds except ring, and in a call, neither ear speaker or mic work. Speakerphone works, and if a headset is plugged in, sounds works normally through headset. Found this app:Wired Headset Routing Fix which sometimes fixes mic issue. Sounds and mic work normally after a reboot, but will then randomly stop. Found several pages of threads all over about the mic issue, but with no fixes.
Tried flashing Bugless Beast rom to adress some of these issues, all problems remain. Mic/sound issue seems tom be related to something with the software that controls the headphone jack. Should I continue trying different roms? Try a different kernel? Possible to complete reset phone back to stock 4.0.2? It worked FANTASTICALLY before the update, how could I get it back to the way it was when I unboxed it? My 14 day warranty runs out on the 22nd, so I could exchange the phone again, but my Verizon store has been hounding me to switch to another device.
Any help would be greatly appreciated!
After your first device they gave you a refurb? Only After a day? That's strange.
Sent from my Galaxy Nexus using xda app-developers app
They initially gave me a brand new one, case was cracked completely through when they opened the box to activate it. The only other phone they had on hand was a refurb.
My mom has the Gnex on Verizon, which has just recently updated to Android OS 4.2.2 (Stock ROM). It seems that since the update, the phone automatically changed its displayed Bluetooth ID that other devices see. Now it seems that when the phone sleeps and is connected to her car radio (2012 Hyundai Elantra w/ built in Bluetooth connection), the connection interrupts itself for about 15-30 seconds and then automatically re-connects to the radio. Making a call on the phone practically impossible.
I was going to just try to set up a Tasker event to keep the display on when connected to power, but that option is unavailable in 4.2.2 without rooting the phone.
As odd as this sounds, any non-rooting solutions would be appreciated.
Thanks.
Sent from my SCH-I605 using xda premium
sbdunn1992 said:
My mom has the Gnex on Verizon, which has just recently updated to Android OS 4.2.2 (Stock ROM). It seems that since the update, the phone automatically changed its displayed Bluetooth ID that other devices see. Now it seems that when the phone sleeps and is connected to her car radio (2012 Hyundai Elantra w/ built in Bluetooth connection), the connection interrupts itself for about 15-30 seconds and then automatically re-connects to the radio. Making a call on the phone practically impossible.
I was going to just try to set up a Tasker event to keep the display on when connected to power, but that option is unavailable in 4.2.2 without rooting the phone.
As odd as this sounds, any non-rooting solutions would be appreciated.
Thanks.
Sent from my SCH-I605 using xda premium
Click to expand...
Click to collapse
I assume you tried to delete the pairing (both sides) and pair again?
You could buy an app like CarHome Ultra (or maybe try the free version if it has the option). It has a setting to keep the display on when plugged in (though I have not tested it as I use tasker with root/secure settings).
I've the same behaviour and my is a Maguro device (GSM).
During a phone conversation there is no problem at all but when in idle phone continuously connect and disconnect (I can see the BT status on the display of my car).
I tried to revert back to 4.1.x ROMs and problem disappear so I can the same recognize it's something in 4.2.x ROMs.
In these last days I tried (and report my feedback, of course not general to anyone else)
- CM 10.1 without BT disruption
- PitchBlack 1.7 with BT disruption
- PitchBlack 1.7 + Franco Kernel 3.0.70 with BT disruption
- PA3.1 with BT disruption (last PA which worked fine for BT is 2.54)
Any ideas?
What part of ROM/Kernel/bootloader/... is in charge to manage BT?
Can it be a problem of sleeping/deep sleep?
Sadly enough, I had not tried that. At any rate, the phone "magically" (I use this term loosely, mind you) appeared to sort itself out and is working fine once again. I don't know if Google had pushed another update to it in the meantime of trying to sort the problem out the first time or what, but at any rate all is well. Thanks for the tips.
Sent from my SCH-I605 using xda premium
I'm running the lates 3.21 quantum release with either the included kernel or using ktoonsez's kt747. Bluetooth issues were never an issue with 4.2.x ROM's but seem to be an issue on every ROM/Kernel I've found on the SGS3.
Does anyone know what the actual issue is? Seems like one driver worked possibly with the BMS kernel in early december but hasn't worked since.
I never get disconnects after connection, but once I turn off a bluetooth device I can't reconnect to it without a reboot.
I've been having a nightmare with bluetooth in my car.
It works flawlessly the first time - new connection, pair, works. Then if I disconnect by any method after that and try to reconnect, it spends about 10 minutes reconnecting and then is very sporadic and will disable/crash my phone. When my phone restarts, same thing unless I forget the pairing and recreate from scratch.
To start-
I am running the latest version of Pure Nexus. My 5x had been working perfectly til the update to Android 7.1.1
My Nexus is appx. 1 year old. I am currently on Google Fi.
This is my problem. The bluetooth and wifi will randomly shut off. It seems to happen when I wake the phone from doze- I can be listening to music on bluetooth headphones, then I wake the screen to do something and the bluetooth and wifi will shut off. I have also noticed that the cellular network may be resetting- not always, but sometimes. I've tried adjusting battery settings to no avail.
My question- what should I check? Is there a log that may be helpful? Is anyone else having this problem?
Thanks for the help!
Just an update. Moved to latest update. Problem is still there. Has anyone got any idea if the problem is with the ROM, the settings, or the phone?