Database Info

[Q] [BUG] - Not waking up from standby and not switching off!

Hi,
I got my Moto G on the weekend (Unlocked from Tesco Mobile for £2.04, thanks ebay)
However, on one occasion, the phone would not turn the screen off until I held the power button for 10 seconds to reboot it.
But more often (a few times every day), the phone will not wake up from standby until I do the same to reboot it. This morning this alarm clock to fail, so this could be an issue.
Does anyone else have the same issue and know of a fix?
Thanks!

Whichs apps do you have installed? Are you rooted? Did you already try a factory reset?
Sent from my LG-P760 using xda app-developers app

I am not rooted. I have tried a factory reset, and with only google account set up the issues still persist! Arghhh, i really like the phone and dont want to send it back

nig060983 said:
I am not rooted. I have tried a factory reset, and with only google account set up the issues still persist! Arghhh, i really like the phone and dont want to send it back
Click to expand...
Click to collapse
Do the issue exist if you don't add a Google account? Have you restored old settings through Google backup?

shaftenberg said:
Do the issue exist if you don't add a Google account? Have you restored old settings through Google backup?
Click to expand...
Click to collapse
I havent restored settings after a reboot, but i have noticed that I get reboots when I am editing google contacts on the phone....

Crappy sleep of death issue .... Seems moto g is having battery issues...

Mm not battery issues its just SW issues.
Simply fixed but will need an update.
Little tweeks like on a phone call when i move the phone away from my ear to open dialer to enter details on an automated service the screen won't come on until I press the power button twice. Once to lock and once to unlock. Then I can bring up dialler
Its due to all the little refinements in power management but it will get fixed.
I personally can live with the little niggles just now for the amazing 3.5-4 hours screen on time I'm getting.
Yest under heavy mobile data use it went a full 14 hours with the 3.5hours screen in time. It was great because I basically done all my Christmas shopping on my phone and checked store prices when out.
If its rebooting often enough I would do a fresh install and start again.
THE BIGGEST thing I found that made a difference in this phone and I think moto should highlight this is:
Do not import previous phone settings on initial start up. This somehow beings weird and wonderful phone settings over and seems to play Havoc with the overall performance of the device be it battery life or connectivity.
I ended up wiping the device in factory reset and on the section on initial set up about backup and restore I unchecked the second option of restore my device settings. Left everything else and since the phone has worked as it should.
My only issue is the power and volume keys location in my car holder means it can be powered off by the holder doh. So I'm looking for a new one which doesn't hug my buttons lol
Sent from my XT1032 using xda app-developers app

Thanks for your help guys, I was still getting random sleeps of death and random reboots so I took the device back to tesco.
They were quick to replace it and I will let you know if I am still getting these issues.

Don't import any old settings, do it manually or you could (if you have the software) do a migrate from My Backup Pro, which I used to migrate pics, contacts, call logs & sms from my old phone with zero issues. My phone hasn't rebooted or had any issues whatsoever. I suspect you just had a faulty unit. Mine is an unlocked tesco16gb too.

rare problem
techguyone said:
Don't import any old settings, do it manually or you could (if you have the software) do a migrate from My Backup Pro, which I used to migrate pics, contacts, call logs & sms from my old phone with zero issues. My phone hasn't rebooted or had any issues whatsoever. I suspect you just had a faulty unit. Mine is an unlocked tesco16gb too.
Click to expand...
Click to collapse
I,
Sorry for broken english
Has the dame problème , i called Motorola and they Say to return it to your cellshop to get new one, very rare hardware deffect,no problem since new phone

Connecting voice call blacks screen, must reboot

The Problem: As soon as I make a call or answer one I'm receiving, the screen goes completely black, although the call is connected and I can speak with them okay. I almost always must reboot the phone by holding power and volume button in order to use my phone again. Very rarely the screen has turned back on, I think after the call disconnects, but this is not reproducible.
I can't say when this started happening, but it may have been after I was fixing a "ERROR: LoadImageAndAuth Failed: Load Error" boot up issue I created when messing around, I think when I restored an old backup made with TWRP. I fixed the problem using this method (a modified Deuce script/.bat file that flashed in the 8.1 OTA to both A/B slots) but I'm not positive. I don't talk on my phone that much so it's hard to say what when.
I'm contemplating putting my phone as far back to storebought-stock-setup as I can before I modified it with Magisk and TWRP, but I wanted to check in here to see if anyone had suggestions on what to look at. My Hope is this will subside when I undo everything and then I can see where the problem was created as I walk the path again, checking as I go.
I tried wiping my data partition in TWRP and setting Android it up from scratch but it looks like the water is still black.

mentalfloss said:
The Problem: As soon as I make a call or answer one I'm receiving, the screen goes completely black, although the call is connected and I can speak with them okay. I almost always must reboot the phone by holding power and volume button in order to use my phone again. Very rarely the screen has turned back on, I think after the call disconnects, but this is not reproducible.
I can't say when this started happening, but it may have been after I was fixing a "ERROR: LoadImageAndAuth Failed: Load Error" boot up issue I created when messing around, I think when I restored an old backup made with TWRP. I fixed the problem using this method (a modified Deuce script/.bat file that flashed in the 8.1 OTA to both A/B slots) but I'm not positive. I don't talk on my phone that much so it's hard to say what when.
I'm contemplating putting my phone as far back to storebought-stock-setup as I can before I modified it with Magisk and TWRP, but I wanted to check in here to see if anyone had suggestions on what to look at. My Hope is this will subside when I undo everything and then I can see where the problem was created as I walk the path again, checking as I go.
I tried wiping my data partition in TWRP and setting Android it up from scratch but it looks like the water is still black.
Click to expand...
Click to collapse
I'm having the same issue but my pixel two is bone stock running 8.1.
Sent from my Pixel 2 using Tapatalk

Screen protectors that do not allow for the light sensor have this issue.

At least I'm not alone, if only for this problem, but my soul is still empty
steve0.adams said:
I'm having the same issue but my pixel two is bone stock running 8.1
Click to expand...
Click to collapse
That's good to know an unmodified version is also affected. Let us know what becomes your fix eventually, even if that means you had it swapped for another phone.
Turns out when the call disconnects I can access my screen again. A temporary fix I figured out is in Android's Accessibility settings you can set the power button to hang up a phone call, so that will let you get back into the system without forcing a reboot.

Doesn't apply to me
teakdamar said:
Screen protectors that do not allow for the light sensor have this issue.
Click to expand...
Click to collapse
I have a screen protector but the phone still functioned okay after it was applied. Just to double-check this I just peeled it back right now and the same behavior still happened. Good point, though.

Since updating to 5.1.8 - No notifications for Slack, Skype or email!

UPDATE: Factory Reset solved issue with notifications not coming in. But all notifications now play at 100% volume, even with ringer and notification volume set all the way down to 10%.
Phone Status: Bootloader unlocked, unrooted & running completely stock. Notification slider is set to "Ring".
I must say, I'm extremely annoyed with my Oneplus 6 and OOS at the moment. I was out of the office today, enjoying time with the wife on her rare day off. I kept thinking to myself that it was an oddly slow day since I wasn't getting any Slack, Skype for Business, or email notifications. But it is a Friday, so I didn't put much additional thought behind it.
I got back home late this afternoon and logged onto my computer, only to discover that I've been missing time sensitive messages and emails from clients all freaking day. Needless to say, this is quite frustrating and it has even put me in a bit of a bind with one of my clients. It's especially infuriating considering that it's not just 1 app, it's 3 of my most crucial apps. I even have the Slack, Newton Mail and Skype for Business apps all set to "Don't Optimize" within battery settings. So there is no reason these notifications shouldn't be coming through. I've tried rebooting and that hasn't solved the problem. Even as I sit here and watch new emails and Slack messages come in on my computer, I'm getting absolutely no alerts/notifications on my phone.
This is not an issue I've ever experienced with my Pixel XL, Pixel 2 XL or my iPhone X. It's a big enough problem that I've resorted to popping my sim back into my iPhone X and throwing the OnePlus 6 in a drawer, until I can get this problem sorted. I'm so pissed that I'm considering just putting the OP6 on Craigslist and never buying a OnePlus phone again. If I can't trust it to give me notifications when they come in, it's useless to me and, quite frankly, costing me money.
However, I will say that prior to receiving the OOS update to 5.1.8 yesterday, I do not recall missing any app notifications. So I'm thinking the recent update is the culprit. Is anyone else experiencing issues like this? If so, have you found a solution?
Regardless, it's quite disheartening to discover the hard way that this phone/software isn't able to properly handle something as basic as prompt message notifications. Even if I get the problem solved I'm not sure I'll ever fully trust it again and will inevitably resort to constantly opening each app, just to make sure.

Do you have advanced optimization turned on? Did you check Settings>Notifications to be sure they weren't blocked somehow?
You might try clearing data and reinstalling the apps. I have not had any issues with notifications nor heard of this issue from anyone else, thought I don't use Slack or Skype.

iElvis said:
Do you have advanced optimization turned on? Did you check Settings>Notifications to be sure they weren't blocked somehow?
You might try clearing data and reinstalling the apps. I have not had any issues with notifications nor heard of this issue from anyone else, thought I don't use Slack or Skype.
Click to expand...
Click to collapse
Just checked and "Advanced Optimization" is not enabled. I also went into Settings > Notifications and confirmed that those apps are not blocked. I might try a full factory reset to see if that solves it. Super annoying.

sn0warmy said:
Just checked and "Advanced Optimization" is not enabled. I also went into Settings > Notifications and confirmed that those apps are not blocked. I might try a full factory reset to see if that solves it. Super annoying.
Click to expand...
Click to collapse
I think a full wipe is needed with OEM ROM updates on this phone, at least if you have root/TWRP. Mine goes all ****y with notifications and bluetooth and fingerprint in 3rd party apps when I update.

TheNetwork said:
I think a full wipe is needed with OEM ROM updates on this phone, at least if you have root/TWRP. Mine goes all ****y with notifications and bluetooth and fingerprint in 3rd party apps when I update.
Click to expand...
Click to collapse
I think you're right. I've received 3 software updates since getting the phone and each time it throws my finger prints out of whack. Deleting them and re-creating them fixes it though.
I'll go through the factory reset and get everything reinstalled when I get more time in the morning.

I'm having the same issue with telegram..what's app seems to be working fine though

I'm having the same issue with Aquamail and my Facebook app (Power Facebook) and both are set to ignore battery optimizations.

80s Baby said:
I'm having the same issue with telegram..what's app seems to be working fine though
Click to expand...
Click to collapse
ajsmsg78 said:
I'm having the same issue with Aquamail and my Facebook app (Power Facebook) and both are set to ignore battery optimizations.
Click to expand...
Click to collapse
While I'm sorry to hear you guys are experiencing these issues, I must say that it's relieving to discover I'm not the only one. I'm convinced the 5.1.8 update broke something with notifications. I'm hoping a factory reset fixes it. Going to try that here in a bit.

sn0warmy said:
While I'm sorry to hear you guys are experiencing these issues, I must say that it's relieving to discover I'm not the only one. I'm convinced the 5.1.8 update broke something with notifications. I'm hoping a factory reset fixes it. Going to try that here in a bit.
Click to expand...
Click to collapse
These updates are breaking a lot of things. Bluetooth functionality for me was fine in 5.1.5, when I received the phone - was broken since updated.
Oneplus needs to concentrate on quality control. It is clearly the weakest point of the phone and the company.
Is it surprising that Oneplus paid an influencer to make a video about how their quality control is so great?
I think not.
https://www.youtube.com/watch?v=-8Kv9fWj9Co
Cool video though.

nabbed said:
These updates are breaking a lot of things. Bluetooth functionality for me was fine in 5.1.5, when I received the phone - was broken since updated.
Oneplus needs to concentrate on quality control. It is clearly the weakest point of the phone and the company.
Is it surprising that Oneplus paid an influencer to make a video about how their quality control is so great?
I think not.
https://www.youtube.com/watch?v=-8Kv9fWj9Co
Cool video though.
Click to expand...
Click to collapse
Yeah, I'm thinking about doing a clean install of Android P DP2 to see if that solves my issues. Not to happy with the "stable" OOS, at the moment.

I had issues with Hangouts mainly and not receiving any notifications so I downloaded the full 5.1.8 zip, factory reset then installed it in twrp and now no issues

sn0warmy said:
Yeah, I'm thinking about doing a clean install of Android P DP2 to see if that solves my issues. Not to happy with the "stable" OOS, at the moment.
Click to expand...
Click to collapse
Done with P dp2?

Have you turned off "advanced optimisation" in Battery settings?

harigavara said:
Done with P dp2?
Click to expand...
Click to collapse
Didn't bother with P DP2 since it apparently has a few notable bugs, including Google Assistant not working properly.
Pat123 said:
Have you turned off "advanced optimisation" in Battery settings?
Click to expand...
Click to collapse
Yes, we discussed this in post #2 and #3.
I ended up not having time to mess with my phone this weekend. And things have actually gotten worse. For some reason my ringtone and notifications (when they do come through) play at maximum volume, even if I turn the notification sound slider all the way down to minimum. Reboots don't solve it. Also, my ringtone is randomly changing to this obnoxious beeping noise. I reset it back to the "OnePlus Tone" and it works for 1-2 calls. Then on the 3rd call it's back to the obnoxious new beeping tone, regardless of who is calling.
It's as if the phone is possessed, at this point.
fantasy2c said:
I had issues with Hangouts mainly and not receiving any notifications so I downloaded the full 5.1.8 zip, factory reset then installed it in twrp and now no issues
Click to expand...
Click to collapse
Yeah, I think I need to do a fresh install of the 5.1.8 factory image. I don't see another way to solve this. OnePlus has really caused quite the mess with these updates. It's probably resulting in costly warranty returns/exchanges for them as well. If a fresh install of 5.1.8 doesn't solve it I'll be selling the phone. These days, I don't have time to be dealing with ridiculous issues like the ones this phone has.

sn0warmy said:
Didn't bother with P DP2 since it apparently has a few notable bugs, including Google Assistant not working properly.
Yes, we discussed this in post #2 and #3.
I ended up not having time to mess with my phone this weekend. And things have actually gotten worse. For some reason my ringtone and notifications (when they do come through) play at maximum volume, even if I turn the notification sound slider all the way down to minimum. Reboots don't solve it. Also, my ringtone is randomly changing to this obnoxious beeping noise. I reset it back to the "OnePlus Tone" and it works for 1-2 calls. Then on the 3rd call it's back to the obnoxious new beeping tone, regardless of who is calling.
It's as if the phone is possessed, at this point.
Yeah, I think I need to do a fresh install of the 5.1.8 factory image. I don't see another way to solve this. OnePlus has really caused quite the mess with these updates. It's probably resulting in costly warranty returns/exchanges for them as well. If a fresh install of 5.1.8 doesn't solve it I'll be selling the phone. These days, I don't have time to be dealing with ridiculous issues like the ones this phone has.
Click to expand...
Click to collapse
Sounds like you have malware. Or you are going crazy
EDIT: if you want a solid but discounted phone, check out Samsung website for discounts on their S9s - they have run $150 and $200 discounts on S9s in the past, and I got one and set it up for a friend. Top notch. But those discounts don't usually last more than a day.

nabbed said:
Sounds like you have malware. Or you are going crazy
Click to expand...
Click to collapse
I did a factory reset then installed TWRP and reinstalled the stock 5.1.8 ROM through TWRP a few hours ago. All has been working fine since. We'll see if it stays that way.

Same with Spotify, 5.1.8 seems to be killing the notification so the app gets killed in the background. Notifications seem to be wonky on 5.1.8.
Sent from my ONEPLUS A6003 using Tapatalk

It's been a few days since I did a factory reset and fresh install on 5.1.8. Notifications seem to be coming in as they should be. However, I'm finding that no matter what audio level I set my notifications and ringer to, notifications always play at full 100% volume. This remains the case even if I turn ringer and notification volume down to like 10%.
I swear this phone is possessed.

Laggy Pixel - almost impossible to make/receive phone calls

Hi all,
Pixel 1 after one of the latest updates turned into almost unusable piece of junk ;/
I do not know if this is OTA update issue or hardware fault, but phone must be restarted frequently, otherwise is almost impossible to make phone call - phone is laggy, screen doesn't respond properly, sometimes must hold power button for several seconds to force reboot, as it is not possible to reboot using the screen.
After reboot seems to work fine until someone is calling - when I answer, the caller cannot hear me and I must restart the phone again to make another try. Sometimes it work and I can talk over the phone, but mostly don't.
Phone never been rooted or anything, always updated with the latest OTA software.
I did factory reset - no change ;/
Is there anything I could try? I was thinking to try to go back to older software, but I'm not sure if this is software issue, as didn't found any other posts on this forum describing similar problems.
It is unusable anyway, so I will try anyhing.

pawel.mrk said:
Hi all,
Pixel 1 after one of the latest updates turned into almost unusable piece of junk ;/
I do not know if this is OTA update issue or hardware fault, but phone must be restarted frequently, otherwise is almost impossible to make phone call - phone is laggy, screen doesn't respond properly, sometimes must hold power button for several seconds to force reboot, as it is not possible to reboot using the screen.
After reboot seems to work fine until someone is calling - when I answer, the caller cannot hear me and I must restart the phone again to make another try. Sometimes it work and I can talk over the phone, but mostly don't.
Phone never been rooted or anything, always updated with the latest OTA software.
I did factory reset - no change ;/
Is there anything I could try? I was thinking to try to go back to older software, but I'm not sure if this is software issue, as didn't found any other posts on this forum describing similar problems.
It is unusable anyway, so I will try anyhing.
Click to expand...
Click to collapse
Ive updated to latest ota on pixel 1 and had no problems so far. You could check the dialer app is set as default dialer and all permissions are granted and maybe clear the apps storage/cache, force stop it and re open it and see if that solves anything? Could also check background apps and running services in developing options to see if an app is banging out the memory causing it to lag?
Sent from my Pixel using XDA Labs

pawel.mrk said:
Hi all,
Pixel 1 after one of the latest updates turned into almost unusable piece of junk ;/
I do not know if this is OTA update issue or hardware fault, but phone must be restarted frequently, otherwise is almost impossible to make phone call - phone is laggy, screen doesn't respond properly, sometimes must hold power button for several seconds to force reboot, as it is not possible to reboot using the screen.
After reboot seems to work fine until someone is calling - when I answer, the caller cannot hear me and I must restart the phone again to make another try. Sometimes it work and I can talk over the phone, but mostly don't.
Phone never been rooted or anything, always updated with the latest OTA software.
I did factory reset - no change ;/
Is there anything I could try? I was thinking to try to go back to older software, but I'm not sure if this is software issue, as didn't found any other posts on this forum describing similar problems.
It is unusable anyway, so I will try anyhing.
Click to expand...
Click to collapse
if you already did factory reset then it must be a sign of motherboard is dying soon or bad nand chip. motherboard failing on pixel is very common but it happens to less than 1% of people. there are plent of threads on reddit/xda on this.

What's the status of your Pixel? Is the bootloader unlocked? Rooted? Did you have any such problems on the December udpate?

As mentioned - I did factory reset as I thought it may help cure the problems, but it didn't.
I have never unlocked bootloder and phone is not rooted. All standard here.
I have the latest update installed and same problems persist ;/
I'll try another factory reset today.

Screen goes black, buttons don't respond, can get calls from other phones to me

Hi all, I have been facing a really weird problem for the past few weeks. Sometimes all of a sudden, my phone screen completely turns black, and the buttons (as well as the alert slider) stop responding. There is no indication whatsoever that it is NOT switched off. However when I try calling it from another phone, ring can be heard as if my phone is working fine. I don't understand where the problem lies. Any suggestions are welcome.
I am rooted with Magisk 19.3, Riru-EdXposed 0.4.5.1 Sandhook, Riru-Core v19.5.
Edit: Android Pie. OOS 9.5.10.GM21AA

I had this problem recently when accessing certain apks. Reflashing the firmware sorted it for me.

no root same problem to me after I update from Android 9 to Android 10

hallo dare said:
I had this problem recently when accessing certain apks. Reflashing the firmware sorted it for me.
Click to expand...
Click to collapse
Thanks I will try doing that.

Same problem here when opening quite a few apps. Issue didn't start until I updated to Android 10 (and rooted), on a converted T-Mobile variant. Wonder if that is the source of our problem. I'm sorely tempted to use the MSM tool and go back on TMO's Android 9 (and pray for a official update to 10). Unless someone can find a solution to this, rebooting the phone every time I want to open certain apps is a real pain.

NighthawkXL said:
Same problem here when opening quite a few apps. Issue didn't start until I updated to Android 10 (and rooted), on a converted T-Mobile variant. Wonder if that is the source of our problem. I'm sorely tempted to use the MSM tool and go back on TMO's Android 9 (and pray for a official update to 10). Unless someone can find a solution to this, rebooting the phone every time I want to open certain apps is a real pain.
Click to expand...
Click to collapse
It definitely is a A10 issue as I too have started to have this issue when opening games and ram extensive apps. A workaround is to open the game or app in split screen mode and once the app has started you can switch back to fullscreen mode or start the app from recents. That has worked for me 100% of the time. The 10.0.1 update seemed to make it worse because you have to reboot the phone to escape the black screen were as at first you could use gestures to escape the app.

mookiexl said:
It definitely is a A10 issue as I too have started to have this issue when opening games and ram extensive apps. A workaround is to open the game or app in split screen mode and once the app has started you can switch back to fullscreen mode or start the app from recents. That has worked for me 100% of the time. The 10.0.1 update seemed to make it worse because you have to reboot the phone to escape the black screen were as at first you could use gestures to escape the app.
Click to expand...
Click to collapse
Good idea using split screen, I'll have to start doing that for the time being. I moved over to Open Beta 3 and the issue is still there and worst as with 10.0.1. Hopefully OnePlus can nail this bug soon. It's turning a otherwise amazing phone into a headache.

I have the same problem. Running 10.0 rooted. For me, this has only happened when opening Youtube Vanced. One clever solution is to enable "Quickly turn on camera" and doublepress power if this happens. This launches camera and returns the screen to normal.

hallo dare said:
I had this problem recently when accessing certain apks. Re-flashing the firmware sorted it for me.
Click to expand...
Click to collapse
Experiencing this too, it does seem to be related to certain .apks, how bizarre is that? Really don't want to re-flash as I am encrypted... Can you dirty-flash with an encrypted system and not loose any data?

cantenna said:
Experiencing this too, it does seem to be related to certain .apks, how bizarre is that? Really don't want to re-flash as I am encrypted... Can you dirty-flash with an encrypted system and not loose any data?
Click to expand...
Click to collapse
I reflashed through TWRP and all data was fine. I'm encrypted too.
But it goes without saying, make sure you do a backup before flashing anything