I've had it happen on almost every ROM, Kernel, and Superuser app combination I can think of, and haven't actually seen anyone else report such a thing happening, but if I install ROM Toolbox Pro, from Play Store, and run it, my device will just lock up. Touch won't work, volume rockers won't work, Power button (just pressing it) will work after several seconds or so to sleep and wake the screen.
Sometimes it will "eventually" work fine, other times it will just sit longer. Has anyone encountered such a thing or have any ideas as to why it would be happening?
espionage724 said:
I've had it happen on almost every ROM, Kernel, and Superuser app combination I can think of, and haven't actually seen anyone else report such a thing happening, but if I install ROM Toolbox Pro, from Play Store, and run it, my device will just lock up. Touch won't work, volume rockers won't work, Power button (just pressing it) will work after several seconds or so to sleep and wake the screen.
Sometimes it will "eventually" work fine, other times it will just sit longer. Has anyone encountered such a thing or have any ideas as to why it would be happening?
Click to expand...
Click to collapse
Funny thing, I just installed the app and it locked up on me. First time it locked up on me, couldnt do anything, so had to hard reboot. I have no clue as to what is causing it though, I dont know where the logs for it are.
Same Thing just happened to me! Did it work for anyone after a reboot?
Edit: Its working after reboot; thats funny!
I won't loading it then?
Sent from my Nexus 7 using xda premium
It finally loaded and seems to work fine now. Just like the OP said; first time it was opened it locked the tablet up. I did a force shutdown, rebooted, then it worked!
Their latest update has been doing that, jrummy is aware.
Related
I have a stock phone, updated with the OTA update. I have this problem where the Home and Search softkeys will stop working all of a sudden. When you press them, they seem to flash so I dont believe this is hardware. Also when I restart the phone, the problem goes away, at least for a little while. When this is happening, to get to the homescreen I basically have to use the back soft key to go all the way back. I thought that maybe this was due to some updates I did so I uninstalled NoLed and TaskSwitcher and I was fine for a few days but it just happened again. Has anyone else experienced this? Thanks, this is my first Android.
If I were, I'd exchange the phone. Sounds like the sensor for those buttons is defective.
Sent from my SCH-I500 using XDA App
It's not the sensor as a reboot will immediately fix this issue. Some say that doing a reset will fix it. Thinking about trying that.
Hi!
I just had a very weird bug. Suddenly when I pressed the home button the stock clock app (which I think is useless by the way) opened. When I pressed again the phone didn't switch to my home screen but stayed in the clock app.
When I tried to put the phone in standby and wake it up again my lock screen didn't show up, it was the stupid clock again.
I rebooted my phone and now everything is like it should be...
I'm running 2.3.4 (not rooted) with Launcher Pro.
Anyone else familiar with this problem?
I believe that you can set home button behavior in Launcher Pro. Not sure about the lock screen though.
I've had the same issue, always resolves itself though, especially after a reboot. Odd bug but doesn't occur enough to bother me.
But I agree the clock app seems largely useless, I have no wish to leave my phone screen on all night, and I can access alarm clock, gallery etc fine without.
I had this issue in January when I first got the phone, I guess on 2.3.1 or so. Anyways, the buttons did random things, and launching App A would result in App C launching instead, if you get what I mean. For example, I'd try to open Dolphin browser and Youtube would come up instead. I'm not sure why this occurred, and a simple restart fixed it. I wouldn't worry too much unless it keeps happening.
I only had it happen to me the one time.
I'm also experiencing this on my Nexus S, First the Car/Dock Mode appeared out of nowhere. It literally just launched itself while I was working at my desk! Now the home button pen up the clock App. Windows can't even detect the Nexus S now. No "you phone is plugged, mount it?" dialog box.
help!
romdroid said:
I'm also experiencing this on my Nexus S, First the Car/Dock Mode appeared out of nowhere. It literally just launched itself while I was working at my desk! Now the home button pen up the clock App. Windows can't even detect the Nexus S now. No "you phone is plugged, mount it?" dialog box.
help!
Click to expand...
Click to collapse
Okay so I think I may have found a solution. I set my Nexus S beside my iPad 2 last night before going bed. I think it may have been the caused of magnets. yup. magnets. So I tried contacting both together. The iPad 2 reacted and lit up its screen and voila the Nexus S home button now works as a HOME and not a CLOCK button! I know its a little weird, may just be a coincidence for all I know! But mine works fine now.
Try it and let us know if this works for you!
Let me resurrect a dead thread here with a new solution. I began building my roms from source on the NS4G and immediately this bug appeared in them. Funny thing is only on my phone none of the testers had this issue. I decided to overwrite desk clock with desk clock pro on the market for free, and it knocked out the bug, and I still have my alarms for work.
It seems that there are some major issues with the new Nexus. This is unrooted, with locked bootloader.
People are reporting not being able to turn theirs on, or having random reboots.
My first boot never got past the Nexus X, and I had to hold the power button to restart.
Then I have had several times where the screen wouldn't come back on after sleep. Again, holding the power button down to restart worked fine.
Then I had gcore and gapps quit unexpectedly, followed by a reboot. I had just rebooted, and only opened one app: Evernote.
So I used the factory wipe option in the settings. Within seconds of completing and booting up the same processes quit unexpectedly.
I tried to reboot into recovery (by holding volume down and power) and got "no command". I tried 'adb reboot recovery' and got the same.
As far as I can tell, the factory ROM is not available for download at https://developers.google.com/android/nexus/images yet.
I obviously don't want to risk unlocking or installing anything custom if there's something wrong with the device.
I will probably have to return it to Amazon.
I haven't found much in the way of information out there, just a few complaints. If there are any well developed threads about how to deal with these issues, please let me know.
I've had a few apps quit on me and one time at the very first boot after the ROM update I had to force restart BUT I hardly consider these as "Major Issues".
There are always bad ones. Shipping, heat, cold, lightning, the chupacabra, darth vader, moisture, the blob, gremlins, or the Jaberwoky could have caused these "major" issues you have,
You're thread is bunk. Return it....
In stock recovery (when it says no command) have you tried pressing Vol+ to get the recovery menu.
I had the launcher force close on my Nexus 4 a few times shortly after I updated but after a few restarts it went away. Other than that I haven't had any issues with my Nexus 7.
Sent from my Nexus 7 using xda app-developers app
idheitmann said:
It seems that there are some major issues with the new Nexus. This is unrooted, with locked bootloader.
People are reporting not being able to turn theirs on, or having random reboots.
My first boot never got past the Nexus X, and I had to hold the power button to restart.
Then I have had several times where the screen wouldn't come back on after sleep. Again, holding the power button down to restart worked fine.
Then I had gcore and gapps quit unexpectedly, followed by a reboot. I had just rebooted, and only opened one app: Evernote.
So I used the factory wipe option in the settings. Within seconds of completing and booting up the same processes quit unexpectedly.
I tried to reboot into recovery (by holding volume down and power) and got "no command". I tried 'adb reboot recovery' and got the same.
As far as I can tell, the factory ROM is not available for download at https://developers.google.com/android/nexus/images yet.
I obviously don't want to risk unlocking or installing anything custom if there's something wrong with the device.
I will probably have to return it to Amazon.
I haven't found much in the way of information out there, just a few complaints. If there are any well developed threads about how to deal with these issues, please let me know.
Click to expand...
Click to collapse
Had I had these issues off the bat I would have returned the device for exchange or refund (if non where available for exchange). Definitely would not have rooted if I was experiencing issues, right back to the store I would of been.
Mine works very well and I LOVE it!
Thanks for all the encouraging words guys
I'm pretty sure the problem originated when the first boot failed and I forced reboot. The OS update must not have installed cleanly.
Anyway I just installed CleanROM and everything is peachy now. I guess whether shipping improperly flashed devices is a major issue or not is a matter of opinion, but I would expect better quality control from Google. I hope it's not too wide spread, and that anyone suffering this issue has the know how and confidence to install a stable ROM.
Sent from my Nexus 7 using Tapatalk 4 Beta
Here's a major issue. Do NOT install widget locker, and then turn on talkback! You can no longer unlock the tablet!
I thought it was a goner, and that I was going to have to return it, but I googled and found out about safe mode, and then once I got that running, found another link on how to turn off talkback.
My God, is that the most annoying feature you could ever think of!
I was reading the google library information, and it said you had to turn an assessibility feature on in order for google books to readbooks out loud.
I'm back to square one with that now... anyone know how to accomplish this?
No issues here. I absolutely love the device!!
Sent from my Nexus 7 using Tapatalk 2
I have had the launcher die a few times, but that's the only issue I've noticed on mine (and since it comes back, it isn't that big a deal).
Phone keeps turning off! Never while using it & sometimes when phone is not moving.
I have an LG-D801 running 4.4.2 kernal 3.4.0 and software D80120a. I also have and use TWRP for recovery. Ever since I rooted my phone and installed this rom, everything has been perfect! That was about 4 months ago. I have and use lots of apps, most of which I have been using for years without any issues. Lately I have been finding my phone off in my pocket for some reason. It now is happening maybe 6-10 times a day which is really getting annoying.
The LG G2 battery doesn't come out so not like it got loose. I have tested it by sitting on the desk lightly and checking it later to STILL find it turned off. So I know I'm not bumping it. I have tried an app killer to kill apps before turning off the screen but it still seems to happen. The phone is still relatively new so I doubt it's hardware, I baby my phones.
Any ideas for ways to make it STAY on without flashing a new rom? Or maybe ideas for how to diagnose what is shutting it down?
(I am looking for ideas and useable feedback, please don't respond that my phone has hardware issues and needs to be replaced!)
UnknownCloakedMan said:
I have an LG-D801 running 4.4.2 kernal 3.4.0 and software D80120a. I also have and use TWRP for recovery. Ever since I rooted my phone and installed this rom, everything has been perfect! That was about 4 months ago. I have and use lots of apps, most of which I have been using for years without any issues. Lately I have been finding my phone off in my pocket for some reason. It now is happening maybe 6-10 times a day which is really getting annoying.
The LG G2 battery doesn't come out so not like it got loose. I have tested it by sitting on the desk lightly and checking it later to STILL find it turned off. So I know I'm not bumping it. I have tried an app killer to kill apps before turning off the screen but it still seems to happen. The phone is still relatively new so I doubt it's hardware, I baby my phones.
Any ideas for ways to make it STAY on without flashing a new rom? Or maybe ideas for how to diagnose what is shutting it down?
(I am looking for ideas and useable feedback, please don't respond that my phone has hardware issues and needs to be replaced!)
Click to expand...
Click to collapse
Are you sure it's actually off and not just asleep and not waking up. I've never seen a generally working phone turn itself off. On another device we called it the SOD (Sleep of Death) and required a long press on the power to reboot. It's most likely a rooted app like something Xposed related perhaps.
wolfclan68 said:
Are you sure it's actually off and not just asleep and not waking up. I've never seen a generally working phone turn itself off. On another device we called it the SOD (Sleep of Death) and required a long press on the power to reboot. It's most likely a rooted app like something Xposed related perhaps.
Click to expand...
Click to collapse
How can I tell the difference? Basically I press the power button once quickly to turn the screen on and it doesn't come on. I hold it for maybe 3 seconds and get the booting up stuff. I am guessing if it was sleeping I'd have to hold it much longer?
UnknownCloakedMan said:
How can I tell the difference? Basically I press the power button once quickly to turn the screen on and it doesn't come on. I hold it for maybe 3 seconds and get the booting up stuff. I am guessing if it was sleeping I'd have to hold it much longer?
Click to expand...
Click to collapse
Yeah bud, that's a new one on me. Do you have any root apps that could be the cause? Like Xposed.
wolfclan68 said:
Yeah bud, that's a new one on me. Do you have any root apps that could be the cause? Like Xposed.
Click to expand...
Click to collapse
Thanks for the help. After reading your previous post, I decided to remove GravityBox KK and Xposed. I was using it because I find it annoying that when I plug in my phone at night, it turns on my screen. Not a big deal...
I also use SuperSU and LuckyPatcher which both use root. The only other thing I can think of is that I semi-recently upgraded my Play Store (v4.8.19 using Lucky Patcher) which I had some troubles with. It kept saying my /system was out of space and for some reason, even with root, it tells me acces denied when changing stuff inside the /system such as boot animation.
so... just an update. It's still doing it even after I uninstalled all the apps that need root. I really wish there was a log or something (like Windows) to tell me why it keeps turning off!
I have noticed it seems to happen much more often if I am texting somebody even though I'm using the default app for messages. It literally was turning off after every message I sent early before the other person was able to reply for about 5 messages in a row.
Hello XDA,
This is my very first community post so please don't judge if I do something wrong here
Let's cut to the chase. I am a happy owner of the OP6T 8/256gb phone and I am super happy with the device, however, I have been having an awkward issue. From time to time, couple of times a day, my phone would not recognize neither double tap nor the power button to wake the display up. Usually out of frustration I press the power button couple of more time, but nothing happens. Then after 3-4 seconds the display wakes up and even opens the camera (because I pressed the button couple of times, but not in a fast way...). Afterwards, the phone works without an issue until same thing happens hours later.
So my question is if anyone is experiencing anything similar and found the culprit of it?
If you need any additional info on my settings, please let me know!
It is not the worst thing that could be happening with a new phone, but you know, one expects the brand new phone to work 100% of the time
Looking forward to your replies and ideas!
Many thanks,
Donatas
It's happened to me only recently. I'm rooted with magisk 17.3 running a few modules such as dual speaker, Google dialer framework and viper. I was on stock kernel, but switched to Smurf kernel without any hiccups so far.
Well I am full stock, even with stock launcher... That's why it bothers me that it is happening:/ thanks for your reply
Donis.za said:
Hello XDA,
This is my very first community post so please don't judge if I do something wrong here
Let's cut to the chase. I am a happy owner of the OP6T 8/256gb phone and I am super happy with the device, however, I have been having an awkward issue. From time to time, couple of times a day, my phone would not recognize neither double tap nor the power button to wake the display up. Usually out of frustration I press the power button couple of more time, but nothing happens. Then after 3-4 seconds the display wakes up and even opens the camera (because I pressed the button couple of times, but not in a fast way...). Afterwards, the phone works without an issue until same thing happens hours later.
So my question is if anyone is experiencing anything similar and found the culprit of it?
If you need any additional info on my settings, please let me know!
It is not the worst thing that could be happening with a new phone, but you know, one expects the brand new phone to work 100% of the time
Looking forward to your replies and ideas!
Many thanks,
Donatas
Click to expand...
Click to collapse
Yes this has happened to me, glad to see I'm not alone.
It happeneds randomly, like few times a day, not too frequent to render the device unusable, but enough to be irritating - especially when it's a brand new device.
My setup;
*Rooted
*Magisk (viper & YouTube vanced module)
*Stock kernel
I'm at a loss as to what's the cause of this issue, it's very weird, it could just be an oxygen os bug that will be resolved by OnePlus. Who knows. Hopefully if more people comment about this here - we will eventually get to the bottom of it.
So far on 9.0.6 build the issue appears to have been fixed, I have not had any random temporary lock screen freeze.
Can anyone else confirm this?
krohme said:
So far on 9.0.6 build the issue appears to have been fixed, I have not had any random temporary lock screen freeze.
Can anyone else confirm this?
Click to expand...
Click to collapse
Glad to hear it is fixed for you!
Unfortunately, since the update, I already experienced it 4 times...
Even more so, sometimes now the phone would randomly stop playing music from Soundcloud (I dont know about other apps, i predominantly use Soundcloud).
I love the phone but it is a little shame that some of these features are failing
Hope 1+ will fix this and we all be happy!
Yeah, sometimes my device doesn't respond to double-tap. Usually I just have to double-tap again and it wakes up. I haven't noticed the issue with the power button, but I rarely use that to wake the device. I did have a situation recently where the device wouldn't wake from a screen tap no matter how many times I tried. I can't recall if using the power button woke it or if I had to force a reboot. But that's only happened that one time.
I just updated to 9.0.6 a day ago. I don't think I've experienced any non-wake issues since then. Really haven't been paying that close attention, I guess.
I believe I am having this issue. I just flashed 9.0.7 from TMO and I'm rooted with magisk v4a and vanced. I get random freezes where I can't tap anything on my screen. I have to turn it off and on with the power button.
I experience this as well. I thought it was just an isolated thing, and it's kinda annoying...
It's very irritating. I'm trying to pin point it and so far I notice it with Firefox and Spotify transitions.