I'm experiencing a weird issue, pretty much since I got the phone last summer where the status bar is pulled down automatically when I unlock the phone. It's not all the way down but just a tiny bit, but it's very frustrating. I have experienced this since Android 9 and not even multiple factory resets during the time I've owned the phone has fixed the issue.
Has anyone else experienced this and maybe have a solution?
hoseth0711 said:
I'm experiencing a weird issue, pretty much since I got the phone last summer where the status bar is pulled down automatically when I unlock the phone. It's not all the way down but just a tiny bit, but it's very frustrating. I have experienced this since Android 9 and not even multiple factory resets during the time I've owned the phone has fixed the issue.
Has anyone else experienced this and maybe have a solution?
Click to expand...
Click to collapse
Yes, I get it too. Haven't found a solution.
Related
Hey,
So last night my Sensation was on charge when I received an email. When I tried to unlock the phone the screen didn't activate but the lights for the buttons at the bottom did. I tried a few times but was unsuccessful, though luckily a hard reset seemingly fixed the problem.
Has anyone else had this issue? I've already contacted Orange and they said they'll replace the handset.
I recorded a quick (and pretty poor quality ) video on my old BlackBerry that I might try and put up on youtube later.
probobly the launcher is loading or force closed. im not sure though, it happened to me too
Happened to me once so far
Hm, probably something that will be fixed in a future update then?... Still, might get a new handset anyway - I may see some improvements in battery at least.
I'm having a very strange problem with my Charge. It seems like pretty much every other time I unlock my phone, a color from the RGB spectrum is missing. Which in turn causes the screen to be a weird shade of blue, green or red. I can lock and unlock the phone again and it will be totally normal, but as I stated above, it seems like it's happening quite a lot more often here recently, and I'm wondering if anyone else has had this problem? I know I'm going to call Verizon tonight or tomorrow and see about getting a replacement because it's definitely not a software issue that I can see.
I had that happen once, and only once. However, it hasn't happened since then, so I'm pretty sure it was software related. Have you done a hard reset yet? If not, you need to do that to rule out a software issue. You need to try it for a bit in that clean state before loading 3rd party software to confirm.
I have the same problem, which just started this morning. When I woke up and looked at my phone, as it unlocked, sometimes it had a bluish or greenish tint. This would appear intermittently as I unlocked my phone.
I searched the internet, and found other instances of this happening as well.
I restarted my phone, and the problem hasn't returned since. Something to keep an eye on, but I'm hoping it's not hardware related, but rather software related (and can be fixed with a reboot).
Mko.
I had that happen a couple times. I have not seen it in a long time but it is software related. I could get it to do it a whole lot one day and after a reboot it never happened again.
I've never had this happen to me but I heard the Fascinate had a problem with the screen since amoled was still being developed, you can just attempt what these others have tried(factory reset, reboot, etc)
Sent from an awesome phone using an awesome app.
Homestar1217 said:
I'm having a very strange problem with my Charge. It seems like pretty much every other time I unlock my phone, a color from the RGB spectrum is missing. Which in turn causes the screen to be a weird shade of blue, green or red. I can lock and unlock the phone again and it will be totally normal, but as I stated above, it seems like it's happening quite a lot more often here recently, and I'm wondering if anyone else has had this problem? I know I'm going to call Verizon tonight or tomorrow and see about getting a replacement because it's definitely not a software issue that I can see.
Click to expand...
Click to collapse
For me when I unlock the phone it does a black screen with lines for a second,pretty much 5 out of 10 times I unlock my phone. I've already got a replacement charge,so my old one and the new one do it. I'm sending my phone to Samung because Verizon has sent me two charges with scatches on the screen, one also has a dead pixel.
Only had the weird color thing happen once upon unlocking several weeks ago. Locked and unlocked it again and it was normal again. Haven't had it happen again.
Sent from my GummyCharge using XDA App
I had this happen to me pretty consistently when. I tried running GummyCharged GBE. Rebooting didn't work for me, so I went back to GummyCharged FE, and that's what solved the problem for me, but it's possible that reflashing GBE may have done the trick too. I never tried that because I thought the issue was related to the ROM.
Sent from my SCH-I510 using XDA App
Well I called Verizon, and while they didn't have it listed as a known issue, I was told to reboot because it was more than likely a software issue. I did just that and haven't had this happen since.
Having said that, I noticed something else, the screen was at a different brightness nearly every time I unlocked it and it wasn't a funny color. Either full on 100% or dim as could be, never anywhere in between. I also stumbled upon an article from a lesser known tech site that suggested that the auto-brightness function was indeed the culprit. Seems to make perfect sense given what I saw. I've had this happen once in a blue moon before the other day, and as others stated after a lock/unlock all was well, but this was a different experience altogether. Hopefully this software problem can be fixed with an update (GB maybe? Probably right as they release Ice Cream Sandwich...).
As a side note my screen also does the gray lines once in a while, just 2 or 3 down the whole length of the screen for a split second before an unlock. Seems like it's not an issue so far.
I've had a completely black screen--my lockscreen will flash and just go black, but sliding where the normal unlock would be turns on the display to Home. Kind of odd, and I've only seen it twice.
Sent from my Droid Charge running GummyFroyo 1.9.1
I have been experiencing a rather annoying bug on my S6. After unlocking the screen, sometimes the status bar will not pull down. This happens about 1/5 unlocks. I have to lock the screen again and then unlock for it to work again. Since the status bar is usually the first thing I use after unlocking, this becomes a real pain. I was hoping that the recent update would fix this, but it's still happening.
Is anyone else experiencing this issue? I couldn't find anything on the forums or Google.
Shameless self bump. I think I may be the only one having this issue. Can't find a mention of it anywhere on the interwebs. Looks like I might have to try a factory reset, or an exchange if it comes down to it. Ugh
Looks like I'm not the only one. I also posted this over on the AT&T forum and someone else voted that they have this problem too. I wonder if it's only happening on the AT&T variant.
Looks like I'm going to have to factory reset. I was hoping more people would at least vote on the poll -.-
Wireless charging possible cause
It seems like this issue only happens if you use wireless charging. I did a factory reset on the phone and used it for a couple weeks with AC charging and I did not have this issue. As soon as I tried wireless charging again, the issue came right back.
Has anyone else here experienced this? I found a few people on the subreddit about Moto G so I am not the only one, but I wonder how many people it affects. I updated my phone to marshmallow and the next day the problem began - I can't normally scroll facebook or any other tab without opening random links and tabs. It's like the phone is registering touches when I am scrolling. It is really annoying after the 20th photo you accidentally liked. Or when checking out the settings you click on every single tab when trying to scroll down. I did a factory reset but it was normal for maybe less than a day (I might have not noticed since I was busy that day and didn't use the phone as much).
Do I wait for next update? It could be months and this is unbearable.
same problem after update, really annoing
Same issue here. It's driving me nuts. I contacted Motorola by email and they told me to factory reset or send it in for a hardware repair! It's obviously a software issue.
Same problem with me but after removing tampered glass my touch problem was solved.
nikhilpal2705 said:
Same problem with me but after removing tampered glass my touch problem was solved.
Click to expand...
Click to collapse
exactly the same solution!
Forever Alone said:
exactly the same solution!
Click to expand...
Click to collapse
Same... removing my tempered glass screen protector was the solution, and then I put one back on that was thinner than my original one and the problem returned but with much less severity. It is livable now, but still annoying once in a while.
My Pixel 7 Pro has started to randomly shut down every so often. Completely out of the blue, the screen will just go black and I need to long-press the power button to turn it back on. This started happening a couple of days ago. No idea why.
I don't know if there's any correlation, but this started happening after the December update.
Is anyone else seeing this, too? Any thoughts on what could cause this and how to remedy it?
Thanks!
--Ron
dutch_in_seattle said:
My Pixel 7 Pro has started to randomly shut down every so often. Completely out of the blue, the screen will just go black and I need to long-press the power button to turn it back on. This started happening a couple of days ago. No idea why.
I don't know if there's any correlation, but this started happening after the December update.
Is anyone else seeing this, too? Any thoughts on what could cause this and how to remedy it?
Thanks!
--Ron
Click to expand...
Click to collapse
No, but I know who can fix it for free, because it's a brand new phone that's still under warranty...
Of course I'll reach out to Google, but I wanted to see if anyone else is seeing this, too.
Will google cover when it is bought at Virgin Megastore?
dutch_in_seattle said:
My Pixel 7 Pro has started to randomly shut down every so often. Completely out of the blue, the screen will just go black and I need to long-press the power button to turn it back on. This started happening a couple of days ago. No idea why.
I don't know if there's any correlation, but this started happening after the December update.
Is anyone else seeing this, too? Any thoughts on what could cause this and how to remedy it?
Thanks!
--Ron
Click to expand...
Click to collapse
Have you backed up to Google one and done by a reset?
A reset might solve your problem?
I've read on GitHub that it's an issue with the 5g hand over to LTE on the T-Mobile network.. I had the same issue until I switch to use LTE and it's not shut off since. Hopefully Google is aware and it gets fixed
GitHub link - https://github.com/GrapheneOS/os-issue-tracker/issues/1809
dutch_in_seattle said:
My Pixel 7 Pro has started to randomly shut down every so often. Completely out of the blue, the screen will just go black and I need to long-press the power button to turn it back on. This started happening a couple of days ago. No idea why.
I don't know if there's any correlation, but this started happening after the December update.
Is anyone else seeing this, too? Any thoughts on what could cause this and how to remedy it?
Thanks!
--Ron
Click to expand...
Click to collapse
This issue exists from October...
After December update more users reportthing this
Pixel 7 pro freezes and reboots - Google Pixel Community
This happened to me this morning. American Verizon service with December update installed.
Happening to me even on custom ROM. I'm really wondering if this is an actual hardware issue rather instead of the OS issue.
lebangood said:
This happened to me this morning. American Verizon service with December update installed.
Click to expand...
Click to collapse
The december beta had this problem so it might apply to the stable one as well, I suggest you update to the stable january build.
ekin_strops said:
Happening to me even on custom ROM. I'm really wondering if this is an actual hardware issue rather instead of the OS issue.
Click to expand...
Click to collapse
If they're based on the december build it might be due to the kernel (the december build had some issues), since I updated to the january build I did not have any other random reboot.
MarcoReckless said:
If they're based on the december build it might be due to the kernel (the december build had some issues), since I updated to the january build I did not have any other random reboot.
Click to expand...
Click to collapse
I tried updating to TQ1A.230105.002 today which I think is the latest stable Jan build..? And just got the random shutdown again.
shinigenEddy said:
I tried updating to TQ1A.230105.002 today which I think is the latest stable Jan build..? And just got the random shutdown again.
Click to expand...
Click to collapse
I'd suggest to do a full factory reset while flashing all partitions, that's what I did and I don't have this issue anymore, otherwise it could very well be a hardware issue, but doing a full wipe is worth a try.
MarcoReckless said:
I'd suggest to do a full factory reset while flashing all partitions, that's what I did and I don't have this issue anymore, otherwise it could very well be a hardware issue, but doing a full wipe is worth a try.
Click to expand...
Click to collapse
I did do a full factory reset before flashing.. I was surprised to still have the shutdown issue as well since it must be a hardware issue then.. but it's so weird that a hardware issue would just randomly surface without dropping the device or anything at all..? Or could it be that the January Stable Build still has the software issue? I'll reach out to Support tomorrow.. for now I'm going to try putting it in my pocket with the screen facing up and not towards my leg and seeing if that makes a difference.
I didn't have this issue, i updated to the January patch and everything was ok, now today my phone started to shutting down tl not sure what is going on
I have the same problem since yesterday. Every time I block the phone and put it in my pocket, the next time I get it it's turned off. I'm sure the pocket isn't pressing any button, but it keeps powering off. I bought it on launch day and I had 0 problems with it until now.
EDIT: Updated applications since yesterday (22 of January): Google, IFTTT and my bank application.
EDIT2: I've just tested to use it on Safe Mode, and I got the same behaviour. I suspect it must be some screen or screen sensor problem... of maybe It has something to do with the fingerprint sensor.
EDIT3: After triple-checking (my phone was in the December update) it finally has updated to the January one. I'll update with more feedback after update.
I changed to only LTE and for some time it was not shutting down. Since pixel pro doesn't have a cache partition like others phones i opened the "files app from Google" and i cleaned the junk files , i rebooted the phone and since then i have no issues at all. Maybe is a coincidence but it's working for some days without shutting down
zenthek said:
I changed to only LTE and for some time it was not shutting down. Since pixel pro doesn't have a cache partition like others phones i opened the "files app from Google" and i cleaned the junk files , i rebooted the phone and since then i have no issues at all. Maybe is a coincidence but it's working for some days without shutting down
Click to expand...
Click to collapse
I had the same issue on the december beta, after wiping the device fully and flashing the january stable this issue disappeared; some users also reported this on GrapheneOS on previous Pixels so I just think it's a bug that went unnoticed.
I started having this issue after the February 5th Update. After reading through this thread it got me into thinking. I couldn't reproduce the issue into safe mode, I uninstalled new 3rd party apps and that didn't fix it. However, disabling the flip to shhh setting did! So disabling the sensor for when your phone is placed upside down to silence the phone seems to have resolved the problem for me. Let me know if this fixes it for others.
So same problem here, random shut downs while in my pocket, long press to power up, temperature check and no over heating. After a couple of chat sessions with FI support which were worthless, finally spoke to Google support and they seemed to be convinced that there is a problem, I think they know. They agreed to a replacement and awaiting a new phone from Google, we shall see.