Hi guys, Ive been experiencing this problem since a long time now, Ive read so much threads and opinions how to fix this, but nothing really worked. So my problem is basically this: When I leave the WiFi turned on the whole time the battery drain form the Android OS process rises massively. After I turn it off and reboot the tablet, everything is fine until I turn it on again...I tried really everything - from changing the rom and android version to unistalling the preinstalled google stuff, nothing helped. Is it just me or is there someone else with this bug?
P.S. My current Android is 4.4.2 KOT49H Rooted, Baseband 1231_0.18.0_0409
I guess you could be a little more specific than "massive" here. Maybe posting some stats could help others to help you!
Sent from my Nexus 7 using Tapatalk 2
I have two Nexus 4 phones and both are 100 % stock but have unlocked bootloader. Both at random get the black screen of death and I have to reboot by holding both volume buttons and power. Is this a known bug with stock?
Are you on lollipop? From what I can gather, this is a known issue among some of the lollipop users.
lolcakes203 said:
Are you on lollipop? From what I can gather, this is a known issue among some of the lollipop users.
Click to expand...
Click to collapse
Yes stock 5.0.1 thank you I was afraid it was a hardware issue
Same happened to me twice already
Zehlek said:
Yes stock 5.0.1 thank you I was afraid it was a hardware issue
Click to expand...
Click to collapse
did you got OTA or flashed factory image
If you got it through OTA then do a factory reset..it is even recommended by Google..
Factory reset will NOT wipe your rom back to kitkat.
I flashed factory images
Yeah, Google should be coming out with a fix soon, until then I'm afraid the only options are to roll back to KitKat or live with it. Perhaps try experimenting with a custom kernel designed for AOSP like Franco or matr1x?
My advice is flash a good custom ROM & kernel, then wait for the 5.1 update
There is a list of known bug with 5.0.2, 5.0.1 and 5.0.0 ?
You should flash CM12, no black screen of death here, i had it on Stock Lollipop like you
Mashed_Potatoes said:
You should flash CM12, no black screen of death here, i had it on Stock Lollipop like you
Click to expand...
Click to collapse
Flashing now
https://code.google.com/p/android/issues/detail?id=79942
This is the issue that is raised in the issue tracker. I have this problem, the only way to stop it from dying is to keep a constant wake lock on the device which drains battery. I might have to try a custom ROM over the weekend to see.
---------- Post added at 05:57 PM ---------- Previous post was at 05:57 PM ----------
https://code.google.com/p/android/issues/detail?id=79942
This is the issue that is raised in the issue tracker. I have this problem, the only way to stop it from dying is to keep a constant wake lock on the device which drains battery. I might have to try a custom ROM over the weekend to see.
Same problem on mine. Sleep of death at random, especially when charging the device. Also, rebooting while doing onerous tasks (such as time lapse recording or GPS navigation).
v5.1.1 seems to have reduced the chances for these problems to occur, but I still happen into them. And if you set a wake up alarm on the phone and it goes into sleep of death during the night, it is not pleasant at all.
I've sent the Nexus 4 to LG tech support because of the power button that is not working correctly, and mentioned the other two problems, even if I don't think LG can do anything on issues that seem to be software related.
Thank you, Lord! I though it was just me. The bug can be reproduced if you try to upload a video in Facebook Messenger app. The black screen is 100% guaranteed.
Mavasilisk said:
Thank you, Lord! I though it was just me. The bug can be reproduced if you try to upload a video in Facebook Messenger app. The black screen is 100% guaranteed.
Click to expand...
Click to collapse
I've just done that a hour ago, that didn't happen.
BTW in the meanwhile since my last reply I've sent my Nexus 4 to customer service two times, the second time was because LG Italia didn't fix the button issue, while they replaced mainboard and battery. During that week before sending the smartphone back to CS for the second time, I've never experienced a SOD (updated via OTA from 4.3 to 5.1.1, being under Lollipop for the whole week).
I've had it back two days ago, chart saying battery and mainboard have been replaced again, button has (finally been fixed) and... ta-dan! Another SOD yesterday, after 24 hours of activity (after a while afternoon of OTA updates from 4.3, again.
I'm glad to see that in the meantime the Issue 79942 has been moved to requesting more info first and assigned then. But that Priority-small makes my nose writhe...
I'm wondering if one can fix it by flashing a different kernel. I can't read of people suffering from SOD on, say, CM 12.1, so it's likely that a different ROM won't have this issue, who knows about only switching kernel.
I had stock SOD for a while, keeping a wake lock active stopped it but did eat through battery. Flashing hells-Core kernel (leaving the rest stock) fixed the issue for me, no wake lock needed.
I am currently using hC-b83-L with no issues, and no SOD.
You can pick it up here if you are interested:
https://drive.google.com/folderview...sharing&tid=0B77BTW0zStYCSTRIYWpZQS1nOWs#list
I've had this happen a few times. Also I've had a few reboots while listening to music using Google play music.
I've been using LMY48I for a long time now and just dirty flashed the system.img of LMY48T 2 days ago. Will have to see if this has solved it.
What bugs me alot more is how the Google camera still does not work...
Sent from my Nexus 4 using XDA Free mobile app
It's been a couple of days since I've removed all of the widgets from the desktop and no SOD since then. Will post updates about this and then try to re-insert widget one by one.
Someone else ever tried this yet?
Hoping somebody can help me out here. I just got my OnePlus Two (Chinese version) and it is running Oxygen 2.0.2. Granted its only been the first day with the phone, but its had a wake lock the entire day now. Installed BetterBatteryStats but I admittedly don't really know how to use it to actually solve the problem. Are other people having these issues and how can I solve it? Frustrating that its stock software and already having issues.
Phone is unlocked and rooted but not rom'ed.
Androids are always awake while charging. Thats normal.
So I'm on a ported s6 rom (aurora) for note 3 (n900w8).
I've been noticing this problem, where a phone call would come, but no vibration with it even though the mode was set as vibration mode.
I have missed many phone calls because of this.
At first I thought I simply failed to notice the vibration, but yesterday I witnessed it not vibrating during the incoming phone call. Screen comes on, incoming call screen pops, but no vibration.
This problem persisted ever since lollipop (I think). Had the same problem in the previous roms (other note 3 lollipop roms).
Oh and it happens when the phone is in idle. If a phone call comes while i'm using the phone, it vibrates just fine.
So I was suspecting it might be blocked wakelock or alarm issue. But then again, the only app i'm using for that purpose is Servicely (by chainfire), and I only have a couple apps checked (ie. facebook, google play services, keep, mega, supersu...etc).
TW 5.0.2.
No xposed framework installed.
Rooted/deodexed.
Anyone experiencing the same problem? Any fixes? Help plz. This is starting to bother me a lot...
anybody at all ?
Well as long as the vibrating motor is okay I don't think there is much to think. You are on a ported ROM, so some bugs are to be expected. If you were experiencing the same on an official 5.0 ROM that would be bothering, but as its not you should ask about this in that ROM's thread.
Do you have enabled the power saving option? If yes, try to deactivate it and see if it still not working.
Flash an official rom.
'Ported' Roms are usually very poorly done, as they are meant for other devices.
Sent from my SM-N9005 using Tapatalk
ithehappy said:
Well as long as the vibrating motor is okay I don't think there is much to think. You are on a ported ROM, so some bugs are to be expected. If you were experiencing the same on an official 5.0 ROM that would be bothering, but as its not you should ask about this in that ROM's thread.
Click to expand...
Click to collapse
celderic said:
Flash an official rom.
'Ported' Roms are usually very poorly done, as they are meant for other devices.
Sent from my SM-N9005 using Tapatalk
Click to expand...
Click to collapse
hm... The last rom I was on was Note 3 LP 5.0 rom built on official note 3 firmware (Vision X from Tmobile Note 3 xda forum), and I still saw that happening.
so yea it wasnt a problem of being ported rom or not...
and I dont want to go back to stock odex rom..
Thx for the replies anyways guys
IEAL said:
Do you have enabled the power saving option? If yes, try to deactivate it and see if it still not working.
Click to expand...
Click to collapse
and no I dont have them on
Hello,i had a very serious issue that it almost cost my job.i dirty flashed this latest flashable rom https://forum.xda-developers.com/showthread.php?t=3533559 from my previous with May security patches.Today my alarm didnt ring!!!I noticed also that ringer doesnt work.i tested the speaker and is fine when i play sounds.Before flashing this latest stock rom,i had again just once the same issue with ringer.I had made a reboot and my phone was ringing again.So now i rebooted once and cleared cache,but issue remained..I rebooted second time and suudenly my alarm and ringer works.Can anyone help me?I read sone forums and i see this happened to other Moto devices as well.I would appreciate possible help,cause i am really afraid now and i will have to buy a seperate alarm.Thanks.
I won't solve your problem, mate, but every custom rom thread warns you against possible issues for a reason. Even "stable" roms are kind of experimental, and anything may go wrong anytime. Alarm clock or solid, cheap phone to use it exclusively to wake you up in the morning is kinda must-have in this business.
thanks dude.but this seems to be stock rom related problem..i wonder if this happened to anyone else..