Every time I press the button to turn the screen on it lags and I have to wait a second or two to turn the display on, any ideas on how to fix it or is it a software thing?
It's really frustrating me, I hope something gets sorted!!
Sorry to hear this. My power button is lightning quick. You might have a defect on your hands there..
It's that bad, sometimes it's quicker to double tap the screen then use the fingerprint sensor to unlock!
Pretty sure it has something to do with the update. Happened on the LG V20 as well
Same Issue
has anyone found a resolution to this? I got my device last week and it has been doing it ever sinse and driving me crazy!. Is it a hardware issue or is it fixed in software? waiting out for the oreo update hoping it will fix it but any help would be appreciated!
Thanks
Have you tried rebooting your phone to safe mode to ensure that no app is interfering?
I have experienced that issue only when I enabled the full immersive mode using ADB.
I have tried safe mode, yes, and the same issue persists, it's not every time the device is unlocked, it's only when it's left for around 2 minutes (it's almost like a deep sleep or something) and what's ADB mode?
Therazerkid said:
I have tried safe mode, yes, and the same issue persists, it's not every time the device is unlocked, it's only when it's left for around 2 minutes (it's almost like a deep sleep or something) and what's ADB mode?
Click to expand...
Click to collapse
ADB or Android Debug Bridge is a command line tool that lets you run commands on your phone from a computer, for installing/unistalling apps, tweaking hidden system settings, etc...
I used it to enable the full immersive mode (basically to hide status and navigation bars). Once I did it, my phone started to behave exactly like you described.
Was your phone having that issue since the first day?
Yes it has been doing it since new
Therazerkid said:
Yes it has been doing it since new
Click to expand...
Click to collapse
Have you tried updating to Oreo? The only other solution I can think of is a factory reset
Related
If I have the hardware keyboard out and the phone goes into sleep mode and I close the phone, when I hit the power button, I get the issues shown in the attached images. It won't respond to anything unless I open out the keyboard and close it again or, tap on the notification area and close the notification screen. No issues if the phone is not allowed to sleep.
Don't want to hard reset if I can avoid it, anyone else had this issue?
I have never seen my device do this, but I don't think I have ever let my device go to sleep while in landscape.
To avoid this, why don't you just change your backlight settings? While on battery power, set the backlight to turn off if idle for 5 minutes or something. This way you'll never have it fall asleep on you. Unless of course you read extremely slow and a page takes 5 minutes.
Was thinking about increasing the backlight settings for a bit longer. I had that situation by chance last night and tried various things, uninstalling software, bluetooth head set, changed radio, hard reset and even task29 and a new flash, still same issue.
Just starting to get fed up with these little annoyances, would be nice if it just worked, lol.
Wow that's rather odd that you did a hard reset and still had the issue. That would suggest that it is most definitely device specific. Maybe you can call your carrier, and if it's your lucky day they can replace your phone. ??
Why no try Energe ROM, It has no such problem.
Alright, so here is what's going on.
I had my alarm go off earlier today, got up, unplugged my phone like normal. I swiped off the notifications I didn't care about like a tapatalk message etc. I noticed that Google Current's automatically updated. I'm sure that's no huge deal.
I locked the screen and went about my day. I tried to swipe to unlock, and the phone freezes and reboots. The phone is responsive until you unlock it, then it just freezes and reboots.
Tried safe mode once, and it worked fine. I then turned it off, and tried normally booting again, same freezing and rebooting. So I went to go back to safe mode, and now safe mode is doing the same thing, which means that a factory reset is now out of the question.
What the hell man.
Specs:
- Samsung Galaxy Nexus
- All stock apps except added Facebook and Tapatalk
- Jellybean 4.2.2 software I believe. I'd double check if I could.
- Still locked and unrooted
Any ideas on where to go from here? No warranty, so any ideas would help
It turns on, goes to lock screen. Then freezes when I try to get anywhere from that lock screen. Even on safe mode.
Then it will reboot automatically after about 30 seconds.
I should note I received a text in this time, and thought maybe just pulling the notification bar down and going straight to the text would work. The notification bar works, but when I hit the text, it froze the same way.
This must be some sort of self check or some Android process crashing. But I can't utilize safe mode to fix it.
Any ideas on what to do? I know there are threads with this problem, but this involves an unrooted phone, of which I have seen no threads, or threads with answers. I am not experienced with getting too far into Android, so just a direction to go, or something to try when I get home would be awesome. (At work currently)
The only options I have right now are the options upon booting with the volume down, which are Start - Restart bootloader - Recovery Mode and Turn off. In this screen, here is my info:
FASTBOOT MODE
PRODUCT NAME - tuna
VARIANT - maguro 16GB
HW VERSION - 9
BOOTLOADER VERSION - PRIMELA03
BASEBAND VERSION I9250UGLL1
CARRIER INFO - NONE
SERIAL NUMBER - xxxxxxx
SIGNING - production
LOCK STATE - LOCKED
In recovery mode, I see a dead android guy with a red triangle and an exclamation mark in it.
I realize you guys probably get a lot of dumb questions so I tried unloading all the information I could. My replies will be 5 minutes apart, as I'm new and I see that's a restriction on being here.
Thanks in advance
You can try unlock the bootloader (it'll erase your data so be careful) and then try flashing the oficial google image via fastboot and see if it solves it.
EDIT: in that screen of red triangle press up and power at the same time to show the options. There you can do a factory reset to see if it solves it. No need to unlock the bootloader that way.
Daedalus93 said:
You can try unlock the bootloader (it'll erase your data so be careful) and then try flashing the oficial google image via fastboot and see if it solves it.
EDIT: in that screen of red triangle press up and power at the same time to show the options. There you can do a factory reset to see if it solves it. No need to unlock the bootloader that way.
Click to expand...
Click to collapse
Got it. It works now, but curious, is this a common occurrance? I have no idea what caused it, which worries me. But it seems to be working fine.
Wasn't worried about data loss, I haven't had the phone for too long yet. I plan on just installing the minimum apps. The point of me not unlocking it was to avoid issues, but I had more luck with unlocking it than leaving it locked.
That said, I wasn't aware you had to hold the vol up and power button to get to the options from the dead Android screen. That was an oversight on my part when I was looking up for data.
Words cannot explain how thankful I am, so thank you
Moderators can close this thread if needed.
slipstreamconversion said:
Got it. It works now, but curious, is this a common occurrance? I have no idea what caused it, which worries me. But it seems to be working fine.
Wasn't worried about data loss, I haven't had the phone for too long yet. I plan on just installing the minimum apps. The point of me not unlocking it was to avoid issues, but I had more luck with unlocking it than leaving it locked.
That said, I wasn't aware you had to hold the vol up and power button to get to the options from the dead Android screen. That was an oversight on my part when I was looking up for data.
Words cannot explain how thankful I am, so thank you
Moderators can close this thread if needed.
Click to expand...
Click to collapse
No problem everything should work as intended now. What happened was a bit strange indeed. It it happens again with everything in stock then there is a possibility that it is faulty hardware and you should replace it. Maybe it was some configuration bug and nothing extreme
Daedalus93 said:
No problem everything should work as intended now. What happened was a bit strange indeed. It it happens again with everything in stock then there is a possibility that it is faulty hardware and you should replace it. Maybe it was some configuration bug and nothing extreme
Click to expand...
Click to collapse
Fauly hardware can cause this issue? I baby this phone, has yet to be dropped (let's admit, it's inevitable), the only thing it's seen is three drops of water that fell off my sunroof onto it. I immediately grabbed my phone and wiped it off, but it was all on the screen, not in the speaker or anything.
Either way, I'll keep an eye on it. Thanks again
slipstreamconversion said:
Fauly hardware can cause this issue? I baby this phone, has yet to be dropped (let's admit, it's inevitable), the only thing it's seen is three drops of water that fell off my sunroof onto it. I immediately grabbed my phone and wiped it off, but it was all on the screen, not in the speaker or anything.
Either way, I'll keep an eye on it. Thanks again
Click to expand...
Click to collapse
Yes. My phone recently was stuck on a bootloop and I've already sent it for repair. Yeah drops are never good
No problem
MY v500 G Pad is experiencing a weird issue where immediately after waking the device (via knock-on or power button), my lock screen will appear as expected, but then almost immediately the screen will become unresponsive (I'm unable to swipe my pattern to unlock) and the display will dim in increments until black. Once the screen is off, I have to hold down the power button to get the device to reboot.
The changes I have made that seems to coincide with this issue are:
1. rooted the device using the .bat script method
2. installed TWRP recovery
3. switched to Nova Launcher
It's important to note, I have not rom'd my device, and am still running the stock rom.
This is happening one out of every 15 or so times I unlock my device. I have switched from pattern to password unlock to see if it's an issue related specifically to the pattern lock screen (although I have used pattern unlock since the day I got the device).
Any ideas would be greatly appreciated!
Thanks
longboarder543 said:
MY v500 G Pad is experiencing a weird issue where immediately after waking the device (via knock-on or power button), my lock screen will appear as expected, but then almost immediately the screen will become unresponsive (I'm unable to swipe my pattern to unlock) and the display will dim in increments until black. Once the screen is off, I have to hold down the power button to get the device to reboot.
The changes I have made that seems to coincide with this issue are:
1. rooted the device using the .bat script method
2. installed TWRP recovery
3. switched to Nova Launcher
It's important to note, I have not rom'd my device, and am still running the stock rom.
This is happening one out of every 15 or so times I unlock my device. I have switched from pattern to password unlock to see if it's an issue related specifically to the pattern lock screen (although I have used pattern unlock since the day I got the device).
Any ideas would be greatly appreciated!
Thanks
Click to expand...
Click to collapse
I don't have that issue and I'm stock , rooted and with twrp you should probably check it's either some settings causing this or more likely an app you installed.
Sent from my SGH-T889 using Tapatalk 2
Thanks for the info Naruto. I think I'm going to remove Nova launcher and see if the problem goes away.
Meanwhile, the problem just happened again, but manifested itself slightly differently. Basically, just a few minutes ago when I pushed the power button to wake the device, nothing happend for ~ 10 seconds. Finally, the lock screen came up, but I got an error message "Sorry! Process system isn't responding. Do you want to close it?" Options were "Wait" and "OK". I selected OK and was taken to the lock screen like normal.
What do you guys think?
I had root from dalingrin and twrp on stock rom for about 2 months and i never experienced this issue you report. The lock screen is related to the launcher and as you use nova launcher i d say that it is most probably caused by it.
Thanks for all the help guys. I'm not ready to say that the problem is fixed quite yet, but after switching back to the stock launcher and rebooting, I have locked and unlocked the tablet about 50 times without issue. Looks like the problem was indeed Nova Launcher. That's kind of a bummer because I love Nova, and I have it setup exactly like my phone and it works great for me.
Maybe you could try to re download nova again that's what I'm using and I have no issues. Maybe it was a setting you had checked inside of its settings ?
Sent from my SGH-T889 using Tapatalk 2
longboarder543 said:
MY v500 G Pad is experiencing a weird issue where immediately after waking the device (via knock-on or power button), my lock screen will appear as expected, but then almost immediately the screen will become unresponsive (I'm unable to swipe my pattern to unlock) and the display will dim in increments until black. Once the screen is off, I have to hold down the power button to get the device to reboot.
Click to expand...
Click to collapse
I got the same thing on a completely unmodified G Pad last weekend. It happened once, worked ok for a few unlocks, then happened a second time. Each time I had to hold the power button down to force a reboot. It's hasn't happened before or since, so I've no idea what caused it, but I did notice something that might or might not be relevant - I happened to be looking at the battery graph later that day, and noticed that at the time of the forced reboots, the battery appeared to drop instantly by about 10%. There was a break in the graph - no vertical line showing the drop, the line just ended, then started off again immediately 10% lower down. If you get the same issue again, it would be interesting to see if your battery graph behaved in the same way.
I had this problem with stock rom changed to Mahdi
No reboots yet.
By the way, I saw a review video on YouTube and the guy was showing knock knock (spell?) and the g pad just crashed and rebooted.
Edit:
I have an LG G2, best phone ever never crashed no lag and a fast phone with great LCD maybe the best mobile screen I have ever seen.
Sent from my LG-V500 using xda app-developers app
Ok, so I don't think the problem was nova launcher after all. After switching back to the stock launcher, the tablet worked great for several hours, but eventually the problem started happening again. At that point, I rebooted into recovery, cleared cache and dalvik, then fixed permissions, and rebooted. Fingers crossed, but the issue hasn't returned once since, and we're going on 18 hours. I've even been using nova launcher without issue. Still not sure what the issue is, but at least for me, clearing cache and fixing permissions has worked so far.
Sent from my LG-V500 using Tapatalk
There is a known issue with 4.2+ of rebooting if you have third party widgets (Not sure which) on the lock screen. Do you have any on there?
http://blogs.computerworld.com/android/21427/android-42-random-reboots
stevessvt said:
There is a known issue with 4.2+ of rebooting if you have third party widgets (Not sure which) on the lock screen. Do you have any on there?
http://blogs.computerworld.com/android/21427/android-42-random-reboots
Click to expand...
Click to collapse
Thanks for that -- unfortunately I don't have any third-party widgets on the lock screen.
Victoria75001 said:
I got the same thing on a completely unmodified G Pad last weekend. It happened once, worked ok for a few unlocks, then happened a second time. Each time I had to hold the power button down to force a reboot. It's hasn't happened before or since, so I've no idea what caused it, but I did notice something that might or might not be relevant - I happened to be looking at the battery graph later that day, and noticed that at the time of the forced reboots, the battery appeared to drop instantly by about 10%. There was a break in the graph - no vertical line showing the drop, the line just ended, then started off again immediately 10% lower down. If you get the same issue again, it would be interesting to see if your battery graph behaved in the same way.
Click to expand...
Click to collapse
When I get home I'll check my battery stats to see if similar happened on mine
So I've been seeing a lot of talk about the 8.1 finger print scanner delay, but to my knowledge, this is something else. Anywhere from 10-20% of the time when I go to wake my phone, whether by pressing the power button, or using the fingerprint scanner, the screen remains black. The phone will vibrate like it successfully read my fingerprint, but the display just won't come on. I have to then wait anywhere from a couple seconds to a full minute before it will come on. It's almost like the phone is in doze mode and just doesn't want to wake up. Has anyone had this problem, or know of a possible cause? It's driving me a little nutty. Definitely is something that has popped up since updating to 8.1.
OneNutShort said:
So I've been seeing a lot of talk about the 8.1 finger print scanner delay, but to my knowledge, this is something else. Anywhere from 10-20% of the time when I go to wake my phone, whether by pressing the power button, or using the fingerprint scanner, the screen remains black. The phone will vibrate like it successfully read my fingerprint, but the display just won't come on. I have to then wait anywhere from a couple seconds to a full minute before it will come on. It's almost like the phone is in doze mode and just doesn't want to wake up. Has anyone had this problem, or know of a possible cause? It's driving me a little nutty. Definitely is something that has popped up since updating to 8.1.
Click to expand...
Click to collapse
Is your phone stock with a locked bootloader? Have you tried wiping the cache partition from Recovery?
Edit: Possibly related LINK
It could be the 8.1 proximity sensor issue under discussion here.
Funny you bring that up, I just bought the phone and went straight to 8.1 . It's happened twice. I thought the phone powered off. I'm unlocked and rooted. I can't pinpoint the when and how but has happened and will pay closer attention.
v12xke said:
Is your phone stock with a locked bootloader? Have you tried wiping the cache partition from Recovery?
Edit: Possibly related LINK
Click to expand...
Click to collapse
This. Might be a problem related to Magisk
Sent from my Pixel 2 XL using Tapatalk
v12xke said:
Is your phone stock with a locked bootloader? Have you tried wiping the cache partition from Recovery?
Edit: Possibly related LINK
Click to expand...
Click to collapse
OMG thank you for linking this! I was going crazy trying to figure out whether it was something I'd done, or something related to the 8.1 update. My phone is rooted, and I'll have a go at removing magisk and seeing if that helps. Again, thank you!
Fe Mike said:
Funny you bring that up, I just bought the phone and went straight to 8.1 . It's happened twice. I thought the phone powered off. I'm unlocked and rooted. I can't pinpoint the when and how but has happened and will pay closer attention.
Click to expand...
Click to collapse
Exactly what happened to me. I was so confused the first time it happened.
Briankbl said:
This. Might be a problem related to Magisk
Click to expand...
Click to collapse
I'm not so sure.... maybe a root app? The long thread I linked to has several suspect root apps, but I haven't had a single reboot and have been rooted on both 8.0 & 8.1.
So it happened twice this morning, both while connected to pc and wall charger when left alone for awhile. Maybe something with deep sleep while charging? Not sure.
Hey guys.
I am posting this particular issue because while I could find something similar to this issue (recovering from a bootloop for this very device), I couldn't find much in case your screen remained black afterwards.
I know why the bootloop took place (or at least I'm almost sure I know why):
-Via dr.fone, I chose the root option. This is a naïve move, as I know that one-click rooting options basically never work. Well, I know this now at least. However, the root never happened, as my device didn't even have OEM activated (there are some issues happening in this regard with lenovo). The program just couldn't continue, telling me that my phone wasn't registered in the data base or something like that. I was honestly just messing around because I didn't have OEM access, just wanted to see what error would pop up.
-The bootloop happened the day after, about 16 hours later. It also happened randomly, while the phone was idle without being connected to the PC. The screen was black, but I knew it was bootlooped because it would vibrate consistently every 10 seconds or so.
-If I pressed the Up+down+power buttons simultaneously, the blue LED in the top right corner would light up and a very long vibration would happen. There's a thread on this issue already, and adding a new firmware solved this.
-I tried to solve this by using ADB to add the stock firmware again. The bootloop stopped after this and the phone would charge. It didn't while bootlooping.
-I tried to factory reset and nothing happened. Except that my USB debugging option is now turned off, which makes things harder because I can't find a way to turn it on without having access to my phone.
I was wondering if there'd be a solution for this very situation. It's also worth noting that my screen is basically shattered, but I don't think it's an LCD issue because these two things happened at the same time. I find it too much of a coincidence.
Do you guys know what could be going on? I also wiped the cache data, even though my phone was factory reset just to give it a shot.
I very much appreciate your attention.
PS: this is literally only the display and the touch screen. Even the fingerprint sensor works.
Did you unlocked bootloader before root ?
Shreyash01 said:
Did you unlocked bootloader before root ?
Click to expand...
Click to collapse
No, the root didn't even take place. I tried to unlock the bootloader, but the Lenovo servers are down for that. So my bootloader is not unlocked.
I think that is the reason..
Your bootloader is not unlocked. You must have to ask someone before doing..
I think costumer care is the only option.