Huawei Nexus 6P :: BLUESLEEP Wakelock Stuck - Won't Allow Any Deep Sleep / Always Awake
Dec 18, 2015
I have a bluesleep wakelock stuck on 100%. It won't allow any deep sleep, always awake. It will stop only when I turn off Bluetooth all together. Bluetooth and wifi scanning are both off. I have a watch, even turning it off won't work. Also froze Android wear apps. No change.... Maybe something to do with missing kernel binaries?
Here are some better battery stats. Thurs is obviously after a fresh reboot, makes no difference really.
My phone seems to be dropping the WiFi signal overnight. I noticed this because right after waking it up in the morning, the emails are getting synced. There is also a high wakelock time for "net_scheduler", which I suspect has something to do with it.
I installed CM12 on my Nexus 5 two month ago and it works fine. But I have the problem that it doesn't react when I press the powerbutton to wake it up from deepsleep mode. Then I could only reboot it.
I changed the "network type" in the settings to "3G" because my provider only supports it and I thought it could solve my problem. But it also hangs up the phone anymore.... I adapted the settings of the phone in the following way:
- Installed "Apex Launcher" as the default one - Installed Klear Kat CM12 as Theme - Additional Apps are: Greenify and SD Maid
I just tried the following steps to fix the problem:
1 . Installed another Launcher instead of "Apex Launcher" ---> I had the problem anymore with the other Launcher
2. Installed Open Gapps "nano" instead of "micro" ---> it ran without any crashes of the phone for a period of time. But now I have the problem again....
3. I wiped "cache" and "dalvik cache" again in TWRP --> System was clean and ran for a while. But after a period of time the problam "came back"
When I'm at home in my Wifi I doesn't have any problems with the phone to wake it up from deepsleep. Lastly I installed CM13 and had done an Fullwipe before... But I've the problem anymore .... I've the feeling that the phone looses it's reception and then the Launcher hangs and can't get up of his own....
I have been experiencing unexplained battery drain with Android OS, Android System and Google Play Services in top 3 along with Screen. I need some app to detect which app/service is causing the Wakelocks so that I can take action. I cannot root due to restrictions on my corporate apps and they will stop working after root, which doesn't work. So I am looking for some app which can show wakelocks when I am not rooted. Previously on Nexus 5 I had used 'Wakelock Detector' app, which had ADB workaround to make the app work even if your are not rooted. But unfortunately after Marshmallow update it stopped working.
I noticed that recently in "Battery"'s "History details", "Awake" is pretty much solid all the time( I do _NOT_ have "root", How should I go about finding which app is keeping my phone awake? I did not install any new apps recently, however I do update my apps all the time..
Just noticed yesterday that my battery life has been pretty poor on my new Nexus 6P. It took me a while to narrow it down, but I finally noticed that Bluetooth appears to be keeping the phone awake.
Whenever Bluetooth is on, regardless of whether it's connected or paired to anything (I normally use Android Wear, but I completely unpaired all bluetooth devices on the phone), "Android OS" in the battery info screen appears to be stuck awake. Its "Keep awake" time grows continuously as long as Bluetooth is turned on.
I really can't be leaving Bluetooth turned off, and the phone is not really going to make it through the day like this.
I've got my nexus 6p two weeks ago. In the last week i've noticed that the phone is always awake, even with screen off. In the first days of use doze was working well and i didn't have problems. It doesn't seem to be regular.
I'm in trouble with deep sleep. I'm on a G920i (VIVO-BRAZIL) and i can't get into deep sleep. I'm using Xtrestolite with UNIBASE Kernel, rooted with CF Root and flashed SuperSU, and my cellphone never get into deep sleep. I've already tried to use DeepSleep(zip) fix patch by chainfire, typed the code into ADB/Shell, used stock, custom recovery...anything and nothing! Still stuck in 400mhz..
Looking at BetterBattery Stats (Kernel Wakelock), on top i have GPSD, second GPS, third Ili_pm_wlock, fourth, 13930000.decon.fb, fifth PoewerManagerService.Display, sixth PowerManagerService.WakeLocks, seventh ssp_wake_lock. My guess about this wakelocks is, I have to desable all fuctions to get into deep sleep? Like GPS, WIFI, Bluetooth, etc?
gmail and other email clients notifications do not work after the phone has been unused for a while, I'm wondering if this at all is related to a deep sleep problem? Quite frustrating, have tried different email clients, some work and some don't, I'm at a loss here coming from the blackberry world where email is push and always works.
Is it possible to use the FPR to double tap to sleep? I am aware of all the kernel wake and sleep options for this device and the implementations ROM's have put in place but, it would be nifty to sleep the device with the FPR.
I'm with a 5.0.2 D6603. The issue I have is that the following Kernel wakelocks does not allow the phone to deep sleep.
I've just performed a sw repair via pc companion, and several factory reset. I'm running the Z3 with no apps.
It happens both with an LG G Watch R (5.0.2) and a regular BT Plantronics (voice only) headset. Using the same BT devices with a Nexus 4, Nexus 10 and an LG G2 does not have the same effect. As soon as there is no usage the phone goes to sleep immediately.
If we take the second device, I do expect a Kernel wakelock while speaking or streaming music. The phone is active any way while performing this task. What is strange is that even if there is no activity the wakelocks avoid deep sleep.
What is strange is that if I move away from the headset (and the BT icon goes the "non connected" status), the wakelocks are always there. The effect is that my phone (both on 4.4.4 and 5.0.2) almost never ever sleeps, and sometimes get warm. It is evident that the battery life affected a lot. If I switch BT off, everything goes back to normal.
I did a further test, in the below sequence:
- BT ON + connected to a Plantronics headset => wakelock + device always on - BT ON + disconnected to a Plantronics headset => wakelock + device always on - BT OFF + disconnected to a Plantronics headset => no wakelock + device sleep - BT ON + disconnected to a Plantronics headset => wakelock + device always on
I notice that my motoactv just eats battery when im not using it. My workaround is to power it off so i dont have to constantly have it charging and so its ready when i need it. Is there a setting coming or present that will allow the motoactv to enter deep sleep mode after x amount of inactivity and then to only be awakened by button presses?
The button will not respond, no matter how long/short I hold it down. It's like it's not "popping" back up, or gives anyresponse. I upgraded it to IOS5 last week, had no problems, until yesterday when it for no reason wouldn't act the way it should..
I've been running Android M preview (3?) for a while on my Nexus 6.2 months ago my USB-connector of the phone broke and only because I also have a wireless charger I can continue to use my phone.Just now I tried a headphone and noticed that viper4android wasn't working, which it did a while ago.I still had the file viper_aio_fixes.zip in my download folder I used to get it going a long time ago. [URL]..
I booted into recovery, flashed that zip and did a reboot.Now it is stuck at the black screen with only the text "Google" and a padlock.I am able to boot into fastboot where I can go in the several modes including recovery mode (Team Win Recovery Project v188.8.131.52). I don't have any possibility to connect it to my computer using an USB. The device does still have warranty, but I can't miss my phone.
I recently got my 6P and immediately proceeded to unlock the bootloader and flash TWRP to start loading custom roms. I decided to start use Pure Nexus with it's accompanying gapps package but when I go to reboot the device, I am stuck at the circles boot animation.
I decide to try CM13 nightlies and the same problem occurs. After searching online for some time, I realize I needed to flash a SuperSU file from recovery that flashes a custom boot.img. I flash Version 2.66 and restart the device. After 5+ minutes on the boot screen, I decided I am stuck still. What do I need to do, I am unable to boot the device.
So I have verizon and I'm using a nexus 6p. My phone died and I charged it and booted it back up.Problem was is I forgot my password. So since I'm rooted i went into twrp and tried my password there. it worked there but not on regular boot up. So i went into wipe and wiped everything. now when i go to reboot my phone it is stuck on the google logo.
Stuck @ "Downloading update..." screen when trying first time connection/start up.
"Downloading update... Waiting for download
This update is 43.8 MB. To continue the download, select a Wi-Fi network.
Via Wi-Fi only until Nov 26
Update size: 43.8MB".
Back button on "Downloading update..." screen doesn't respond.
6P is connected to Verizon mobile hotspot wifi. Verizon wifi speed more than 6Mbps, ping 60 ms (tested from Dolphin browser without data compression)
The 6P Wi-Fi list indicates Status- Connected Signal strength- Excellant Link speed- 72Mbps Frequency- 2.4 GHz Security- WPA2 PSK
Verified the wifi network works for all my other devices. Tried forgetting/rescaning wifi network many times, tried with and without the Google Fi sim card many times, tried wiping cache, factory reset, and recovery modes many times. Tried leaving the 6P connected to the Verizon mobile hotspot for more than 15 hours. Tried the Fi LTE.
After more than 25 restart/initialization attempts, only the previously mentioned web pages display on the 6P "Update phone" screen, on wifi or LTE.
Damnit. Something went wrong and I don't know how to get out of it.
I used Nexus Root Toolkit 2.0.7. Bootloader Unlock went just fine. Root went wrong (I think). It just sits there at the white Google logo. It never goes to the animated loading portion of boot up.
So, I stopped the process. Then went to select Flash Stock + Unroot to hopefully start over. It still stays at the white Google logo. Instructions say it could take up to 20 minutes, but I waited for about 30 and nothing happened.
So I entered Recovery. Formatted/Cleared all data and started fresh with the unlocked boot loader. I was able to flash TWRP and actually flash a custom ROM. It loaded, but the phone boot looped when I tried to flash a custom Kernel.
Fine. I went to restore a backup I made before flashing the Kernel and it boot looped. Restoring the backup did nothing and I couldn't load anything.
Loaded up Nexus Root Toolkit again, tried to root and it just stays on the white Google logo. Tried Flash Stock + Unroot and it still sits at the Google logo.
WTF. I've been doing this for a long ass time now.
So I tried to use the Nexus Root Toolkit to sideload the OTA, but now when I try to boot my phone it just shows the white google screen and doesn't do anything. I can use ADB and fastboot and get into the bootloader but I can't flash the factory image because I never checked the "Allow OEM Unlock" tick since I didn't plan on unlocking the bootloader.
128 GB Frost Nexus 6P, just got it today in the mail and decided to restart the phone after a day of installing all my apps and re downloading all my music, and now its stuck in the colorful bootloop and has been for over 2 hours. Not Rooted Not Unlocked, how to get it out of this.
So I tried to root my 6P with the Nexus Root toolkit , first I unlocked the bootloader, that went well . After that I tried to root it but my build number wasn't there (MDB08L) So I researched if that would be a problem and a couple of people said they followed the same instructions as with the MDB08K build and it worked just fine on theirs so I proceeded.
I selected the "any build" from the options on the toolkit and it seemed to be going well, I followed the instructions , flashed the files on twrp and from there I rebooted and it got stuck on a bootloop... :/ so then I tried to use the toolkit to fix the bootloop and selected the MDB08K and after it ran and finished it isn't exactly bootlooping but it is now stuck on the black Google logo and does nothing ...
So I flashed the latest firmware, after being unlocked, then rent back to bootloader, flashed recovery, went to recovery and installed file. Then restarted...now stuck in boot loop. It booted before I went to flash recovery in the new firmware just fine.
Do you need to flash something else when you flash recovery?
it says device is corrupt when I restart, but I was under the impression that screen comes up when bootloader is unlocked, so not sure if it means anything...
I have unlocked bootloader, flash modified boot.img and recovery but when I boot the device I get 'Your device is corrupt and may not work properly' I then get stuck on the google boot screen. When I go into TWRP recovery it cannot mount anything so I cannot even perform a factory reset.
Currently flashing back to stock with the steps given by Heisenberg's step by step guide, number 11, how to flash the factory image.
At the command fastboot flash system C:anglerimagessystem.img and it has sat here for over an hour and a half now with the output of writing 'system'. If I'm not mistaken, my phone is basically bricked at this point, as all I have written to the phone right now is recovery and bootloader really, and since I flashed the stock bootloader that means it is relocked.
Is there any way I can unlock it from here and then flash TWRP again, and then restore one of my backups of my 6P to at least get it working again?