My OnePlus 3 is about one and half years old, bought from india. Recently I have updated to Open beta 31 by experience os. I also tried the z unleashed ROM. Then again gone back to experience os based on 5.0.1 . After some days my phone was crashing sometimes, also sometimes it was becoming unresponsive after going sleep.
∆ I looked for this issue in the internet and came to know that it is called Sleep Of Death Issue. I'm my case the symptoms are:
1. The mobile goes unresponsive after going to sleep, it doesn't do anything when power button pressed or fingerprint pressed.
2. The mobile stays black and little warm. Sometimes if battery low the red led was still blinking.
3. There is no connection to network, the mobile seems dead.
4. To wake up the phone I have to hold down the power button to turn it off. Again hold down to turn off. Sometime have to insert the charging cable, otherwise nothing happens.
∆ I have seen in forums that same happened with Nexus 4. Some OnePlus users also reported this issue. But nobody has found a sure solution to fix.
∆ Following some suggestions I have downgraded to oos 5.0.1 and 4.5.1 by urooting and going stock. the Sleep Of Death was still happening in both.
∆ Then I followed the hard brick recovery method to go back to oos 3.1.2. but sleep of death was still happening.
∆ Then I formatted all partition by twrp and flashed freedom os based on oos 4.5.1. It was ok for one day and then SOD started again.
1. I have tried Ex kernel, bluespark kernel. No fix.
2. Tried turning off doze, pocket mode. No fix.
3. Tried z unleashed ROM at first but no fix.
4. Tried turning off WiFi, removing sim card. No fix.
∆ Now I am using SOD killer app from play store which prevents the processor from going to deep sleep. There is no sod for one day now but it consumes battery so it's not a solution.
So does anybody have any solution plz help me. I am very disappointed because it is my primary device. Thank you in advance.
Related
Hi guys,
I been experiencing some very annoying bugs with my Note 2 lately so I thought I would share them all with you. First, here is a presentation of the device :
- N7100, second hand one, it fell a few times but I don't think it broke anything on the phone.
- Currently rooted Android 4.1.2
- I have installed Perseus kernel in response to that SDS chip I have... (but my problems were already there before)
Alright, now let's see my problems :
- the BIG one : phone turns off during the night sometimes, it happens like once a week, happened last night. OK, this is very weird because I would say that it is "shut down" if this didn't happen once : the phone looked like it was off but the led was working (green tilting which is my Whatsapp notification). Tried everything usual to turn the screen on but I had to push the power button for some seconds as I do to turn it on, it turned on as usual... important precision I think : I never had to remove the battery, just pushing the power button is enough.
- along with that bug, something weird happened last night. I was happily using wifi at my brother's and decided to sleep so I put the airplane as usual and good night... woke up with phone off as I said, turned it on and I had only 14% battery left, I am SURE I went to sleep with more than 55%... what the heck is my phone doing while I sleep ?!
- some of my apps shortscut disappear... they usually are in the apps so I just have to put them back on the desktop, and here comes the one that disappeared making the one I just added useless -_-'
- I use Viber and when I get a call, the phone won't stop vibrating! I have to turned it off and back on for it to stop.
Alright, now I have to tell you one thing : I am using Automateit and I have this rule "reboot the phone every night at five" and it worked great with my former SG3. I have like ten other rules that shouldn't be responsible for anything with these bugs. Just uninstalled it to make sure it has nothing to do with it. Does all of this remind you of any known bug ?
Here is a screenshot of my battery stats
]http:/ /nsa34.casimages.com/img/2013/12/26/131226025303836204 .png
Massive thanks for any readers and helpers :good:
Hi,
I have:
Sony Xperia Z1 Compact
Rooted
CyanogenMod version 11-20141112-SNAPSHOT-M12-amami
Android version 4.4.4
Kernel version 3.4.0cyanogenmod-g1b20e398 [email protected] #1
Build number cm_amami-userdebug 4.4.4 KTU84Q a265284510 test-keys
My phone's screen has the annoying problem of sometimes not waking when I press the power button (while the phone is turned on). The phone is still on, but doesn't respond to input. I can call it, but nothing happens. I can connect the charger, but it doesn't respond.
I did not experience the issue before rooting. After rooting and installing CyanogenMod, the problem occurred perhaps 1-2 a week.
Recently I encrypted my phone. After that the problem has become much more frequent. The screen is now unwakable roughly 2-3 times a day, some times even more!
The only solution I have found, it to either turn the phone off via the red off button next to the SIM card, or by rebooting it by holding the power button in for so long.
The issue is extremely annoying, especially after it started occurring 2-3 times a day.
I have tried searching for similar issues, but haven't found any solutions.
I have tried changing the brightness levels so the max level is 99% instead of 100%, as someone had suggested, but that hasn't made any difference. Unscrewing the phone and cleaning the proximity sensor, as someone else had suggested, is something I haven't tried yet, as I don't feel competent enough to unscrew the phone.
The phone used to have the protection plastic provided from the fabric, but I tore that off not too long ago. No change in behaviour.
I have not managed to find one special event that triggers this behaviour or reproduce the issue on demand.
Hopefully someone will have some tips as to what I can do to solve this issue. Thanks in advance.
Any modifications on the kernel? Like special governors or under/overclocking?
As you are using a custom ROM the clear advise here is: try out with stock ROM and see if the problem is still there.
If not, it is a problem with the ROM.
I'm having the exact same problem. I flashed cm11 snapshot two days ago, and today my screen wouldn't wake no matter what.not even a restart would solve the issue, cause the moment the phone goes to sleep after a boot, that was the last time the screen was on. I'm following this thread in case somebody comes up with a solution.
hi there, my phone is acting the same way as yours described. Mine is rooted on stock lolipop and it never happened before although i had a replacement unit and the one before that acting the same way. Pressed the power button and nothing happend regardless screen on or off. Had to do hard reset and it worked for like 1 or 2 days. I went to sony talk forum and ppl seems to say it a bug since the phone released. If anyone got anything would be great help. Thanks
I'm using my dad's Note 10.1 (2014) and I've been experiencing some problems. The screen would randomly just turn off (but it doesn't shut down) when I looked away. I thought it was the smart eye detection feature thingy but when I checked, it was already turned off. Another problem is that the home button and/or the capacitive just randomly stops working. Had to reboot the device in order to get it working again. At first I thought it was some hardware problem but I'm pretty sure it isn't. So yeah. Does anyone face the same problems? I've heard this device have some software issues that causes this but after some searching I got no answers.
Hi
I have your problem too. i have thiss issue on Stock rom. i use for one day Resurrection Remix ROM. i havn't see this issue.
I was just wondering if anyone else has an issue with their Note 4 rebooting randomly with no external input. This started happening with the Android 6.0 update both on the download from here and the AT&T official release, Any Ideas? I've already purchased a new battery due to a separate issue, any idea?
I had the same problem. The phone would freeze and randomly reboot. Sometimes the system crashes and asked me for the typed-in password (not fingerprint). Sometimes when I charge the phone, and unplug the power cable, the charging led stays lit and the battery has to be pulled. I decided to switch the battery with my wife's Note 4 and see if the effects remained. So far I haven't had any problems after switching the battery, so I believe the battery may be the cause of all these issues. I'll keep you updated on the issues.
I'm back. The battery replacement didn't fix the reboots. I think my phone's hardware is permanently damaged. :crying:
have you downgraded?
and can you help me with my problem?[
AlexanderDAB said:
have you downgraded?
and can you help me with my problem?[
Click to expand...
Click to collapse
I'm downgrading to stock 5.1.1 right now. I'll keep you updated. I placed an order for a Galaxy S7 Edge International Version (G935F) yesterday.
ajumatt said:
I'm downgrading to stock 5.1.1 right now. I'll keep you updated. I placed an order for a Galaxy S7 Edge International Version (G935F) yesterday.
Click to expand...
Click to collapse
can you downgrade to Android 5.0.1 and help me with my problem?
its something completely different to this topic
I've been having the same issue, started about 2 weeks ago. phone would start being sluggish then if I continue tapping on screen, it'll reboot. At least once I saw it go into recovery & reinstall firmware(?). Another time it just sat at the bootloader screen waiting for software download or something till I took out the battery. Most likely it's a software issue related to 6.0 update or updates afterwards. taking out the SD card helped a bit.
but basically got annoyed & upgraded to LG V20 today. Coincidentally, there was another person at the AT&T store with a Note 4 having the same issue.
Mine just rebooted twice on me a while ago, first is emergency calls only now the reboots then what. And yes the slow charging is a problem too. MM got serious issue dam att
Sent from my SAMSUNG-SM-N910A using XDA-Developers mobile app
adavis1201 said:
I was just wondering if anyone else has an issue with their Note 4 rebooting randomly with no external input. This started happening with the Android 6.0 update both on the download from here and the AT&T official release, Any Ideas? I've already purchased a new battery due to a separate issue, any idea?
Click to expand...
Click to collapse
use wakelock its an app u get it from play store.it makes ur cpu always running.some how it fixes the problem of random reboots. dl it and set it to partial lock (the 5th option)
Same problem. Just started a few weeks ago. REALLY frustrating having to enter my password every 3-4 minutes. NEVER buying another Samsung, too many damn issues with this phone.
My reboots tend to happen once the phone goes below 60% battery. It's fine above 60%. Once it goes below 50%, the reboots tend to happen with any intense network activity. The phone will often go from 50% to 22%. I forgot what the 30's and 40's look like. I will try the Wakelock app.
Ugh. I posted about this a few weeks ago. It's started happening more frequently and will occasionally go into a boot loop or show 0% battery even though there's a charge.
Has anyone found any solution? I haven't tried wiping / resetting but I'm getting close to trying it.
Here is a cautionary tale for you. My completely stock, unroooted phone started acting the same exact way. On the 4th or 5th battery pull (to fix a frozen screen) it just crapped out. It's totally unresponsive. Deader than a door nail. Tried everything. The download mode, discharging by power button depression/battery removal, etc. Adb shell command does not detect it. Nor Odin. Computer throws up a qhsusb_bulk error when I plug it into pc. I have NO CLUE how to fix it & I am desperately seeking a solution. Please proceed wisely with your oddly acting phones & don't let this happen to you.
k.babymamma said:
Here is a cautionary tale for you. My completely stock, unroooted phone started acting the same exact way. On the 4th or 5th battery pull (to fix a frozen screen) it just crapped out. It's totally unresponsive. Deader than a door nail. Tried everything. The download mode, discharging by power button depression/battery removal, etc. Adb shell command does not detect it. Nor Odin. Computer throws up a qhsusb_bulk error when I plug it into pc. I have NO CLUE how to fix it & I am desperately seeking a solution. Please proceed wisely with your oddly acting phones & don't let this happen to you.
Click to expand...
Click to collapse
Same issue. Just got off the phone with Samsung support, all possibility of having this particular phone with this particular issue sent in for evaluation has been suspended. Translation, they know it is an issue and will not stand by the changes they push to their products (latest OS). I am researching the prospect of legal action since THEY pushed the new OS against my request. Shouldn't that affect the warranty or coverage? Consulting my attorney friends as we speak. Will let you know. I am not sure how WakeLock will help, it is not going to sleep, it is repeatedly power cycling through a kernel process until the battery overheats or it reboots.
Same issue
Since Marshmallow, my 910A will get sluggish or freeze, shut down, sometimes reboot and sometimes just brick (temporarily). Sometimes--more often in recent days, I get a "dll_mmc read fail" message and the target that says do not stop downloading. No matter what I've tried--factory and soft resets, cache clearing, battery pull, replacement, and SD card switch, contacting AT&T and Samsung rep--it doesn't seem to change. This is a daily issue and becoming more frequent. Any suggestions or do I just need a new phone? Thank you.
The last two times I allowed my phone to charge fully, the phone locked up (would not come on when the power button was pressed) and I had to do a soft reset (hold the power button for 30 seconds). This happened on two different chargers with two different cables (one of which is the factory set). Thus, the issue is almost certainly not hardware related.
There have been no changes to my phone, no newly installed apps, etc. There have been a number of app updates, including several Google/Android core apps, and I am wondering if one of those could be the problem. (After the first time the phone locked, I updated the kernel to the latest version, i.e., PQ3A.190801.022. Note also that the phone is rooted with Magisk.)
Has anyone else experienced this problem? If so, what did you do to resolve it? What can I do to try to figure out why this is happening?
groston said:
...What can I do to try to figure out why this is happening?
Click to expand...
Click to collapse
Try replicating it in safe mode to rule out 3rd party apps.
I'm having the same issue the last 2 weeks. I haven't updated any apps and I have auto updates off. No changes to my phone since the end of august and it just started doing this.
Were you able to figure out what was causing it? My issues occur using a 5W Qi charger. So it is definitely not cable/charger related.
Sorry to report, but I have no idea. Since having posted my question, my phone has been behaving properly.
I've got the same issue on 10. I put my phone on a pixel stand at night and when I wake up I have to do a soft reboot to get the screen to turn on. Reverted back to Pie and the issue went away. Flashed the Oct factory image for 10 including wiping data and the issue returned. Booted into safe mode last night. Woke up this morning and had to force a reboot to get the screen to turn on.
darkstar73 said:
I've got the same issue on 10. I put my phone on a pixel stand at night and when I wake up I have to do a soft reboot to get the screen to turn on. Reverted back to Pie and the issue went away. Flashed the Oct factory image for 10 including wiping data and the issue returned. Booted into safe mode last night. Woke up this morning and had to force a reboot to get the screen to turn on.
Click to expand...
Click to collapse
Weird. I'm still on 9 that was working fine and no update that I know of.
I confirmed the issue with both QI charging and cable charging on my phone.
I've taken to making sure my phone is charged before bed and just pulling it off the charger before going to sleep. Since my phone is also my alarm and having it go unresponsive is no good. Only looses about 3% battery overnight.
Well, not sure what happened but the day before yesterday my phone did it's usual lock up while charging requiring a reboot. Unusually after reboot if I logged on too fast it would immediately shutdown. But for some reason this time it took me 7-8 tries to get in. I haven't updated any apps, changed any modules in Magisk or anything. It just went to almost boot looping.
As soon as I got it stable I popped into Magisk and looked at what modules were there. I noticed I had added Substratum previously, to try and do a dark theme, but apparently I never removed or disabled it. I disabled all the modules and suddenly no more problems. Reboots without shutting down after log in and no longer locking up on the charger.
I removed two audio mods (audio compatibility patch and audio modification library), as well as substratum. Three of 5 mods I had downloaded.
I am currently only have Active Edge Mod and V4A legacy FX for mods and my phone is now working fine. If it changes I'll let you guys know.