I'm running OP3T_O2_Open_20 and not rooted if that helps. Sometimes while playing Pokemon Go I will press the physical back button and it will light up, but the game will not pop the exit prompt. Most times it will do this, but sometimes pressing the back button works.
Also the extended screen shot does not work in the game. I got a warning that it cannot be used at first, now it just stays grayed out.
If this is common, I'd like to know. If it's just my 3T, then that's something else.
Thanks for the help.
Related
Hello,
I was wondering if there is some way to track what is happening on my phone? Since my screen stops working when waked up from standby. i.e. if i press the button at the top to standby and then when i press it again and reach the lock screen the touchscreen is not working, it is simply not registering touch and neither are the 4 small buttons on the bottom (back, settings, home, search). However, the OS in itself is still running as I think since I can still see the time move and if I hold the off button the menu comes up for reboot etc.
Anyone heard of anything like this or any tips how to solve this? I am rooted and running CM6 I think at the moment.
Thank you,
Svarto
Svarto said:
Hello,
I was wondering if there is some way to track what is happening on my phone? Since my screen stops working when waked up from standby. i.e. if i press the button at the top to standby and then when i press it again and reach the lock screen the touchscreen is not working, it is simply not registering touch and neither are the 4 small buttons on the bottom (back, settings, home, search). However, the OS in itself is still running as I think since I can still see the time move and if I hold the off button the menu comes up for reboot etc.
Anyone heard of anything like this or any tips how to solve this? I am rooted and running CM6 I think at the moment.
Thank you,
Svarto
Click to expand...
Click to collapse
so the only way to escape this is by pulling the battery and rebooting? when you do reboot and dont go in standby, the touchscreen works fine?
You can check the issue using logcat and /proc/kmsg.
Also, you can read my threads on the subject, describing the same error with logs, and see if your logs are the same.
I'm currently trying to check if the error repeats itself after full wipe and starting from scratch. In the meantime it didn't show up until I applied a theme, and then after reflashing the ROM it's gone again - I'm still checking, only a day has passed.
Yes, the only solution is to pull out the battery and reboot. Then it works fine and I can go in and out of standby. I havent found a particular pattern to it happening so it is hard to reproduce.
I will have a look at that logcat and your other thread!
Just to guide you - when it happens to me, the phone gets stuck with mmc0 access that receives "CRC error" reply and doesn't go through. Pressing power button for a long time several times and playing with trackball / touching the screen between presses "releases" the "lock", and you'll be able to work with the phone again until you put it to sleep again. If you turn WiFi and BT off and then back on - the problem seems to disappear.
Anyone using Button Savior? I love it but it doesn't seem to survive a reboot. In fact, sometimes, it seems to die even without a reboot. Is anyone else experiencing this? Is there a way to ensure that it's always running?
Sent from my XDA app on my Nook Color
I started using it today and have rebooted several times. Seems to actually work, whereas SoftKey didn't work as reliably for me.
I installed it via the Market. At some point, not right away, it asked for su. After that it has worked fine.
Homer
I'm another happy user of button savior. I use it on on my rooted HD2 and love it.
An update just came out for button savior, but I have never had problems with it. I do have to restart it once in awhile after a boot, but not every time. Not much to complain about because I love that some smart person actually came out with it!
I've been using it for several days and have rebooted many times. Installed via Market. So far so good.
I love button savior. I occasionally miss the button to pull up the menu because its so small but it has survived a few reboots.
I see the little button on my screen on the right but it does nothing, I cannot activate it, I have gone into the settings and I can move it from left to right but that's it, Help please
rog152 said:
I see the little button on my screen on the right but it does nothing, I cannot activate it, I have gone into the settings and I can move it from left to right but that's it, Help please
Click to expand...
Click to collapse
Are you sure your finger is touching it? I have trouble getting the nook to register my taps on the edges of the screen. Once you tap the icon a group of icons appear like home and back. Try reinstalling if you continue to have problems.
I've been having an issue with my soft keys pressing themselves randomly and repeatedly. Menu options pop up and ill press menu to make em go away and seconds later they'll pop up again, and again. The one that blows me up most is when it presses home, *%#@! Anyone having the same issue, anyone have any advice, anything?
Now I'm so broke i can't even pay attention!
when inside the hangouts app, or inside the facebook app, or inside the photos app..... or almost any app really...
when I want to go back a screen, I notice sometimes i press the back button, then press the back button again before I go back one screen.
has anyone else noticed this?
Ideally the phone will just push you back one screen fairly instantly when you press the back softkey.
However, I must admit this is not ALWAYS........ i just tried it again, and after pressing back, the phone did indeed go back a screen fairly instantly... I dont understand why sometimes yes and sometimes no.
Has this happened to anyone? also, do any of you think its because of the always-on encryption?
Yes this has been reported and it does it to me randomly but not often. I believe there is a thread already covering the topic
Hello,
I have a rooted and TWRP installed but otherwise stock 5.something T710 that I had worked on months ago. It's been great and my daughter had been using it to watch videos a couple days ago. I took the tablet from her at the end of our road trip and noticed it had about 63% battery left. I left it in the truck while we went to the movies(about 40 degrees f outsides) and then drove home without ever touching it until we got home. I went to use it when we got home and it would not turn on. I plugged it in to let it charge thinking it died for some reason, using the stock charger, though battery icon never appeared. The next morning I went to check it and it still would not turn on.
When I press the power button or plug in or unplug the charger the Recent and Back soft key lights will turn on for a second, then turn back off again.
I've tried:
Holding the power button down alone for over 3 minutes.
Held the power and volume up button for over a minute
Power and volume down for over a minute.
Home, volume down and power for over a minute
Home, volume up and power for over a minute.
I can connect it to my computer and it recognizes that my Tab S2 is connected but no files show as the default for the device was just charging mode and not the file modes.
Odin3 v3.10.7 recognizes it as connected. But fails to send the TWRP file again.
Any help?
Since the soft keys light up and the computer recognizes the device, it sounds like maybe the tab is still working but with no display? By any chance did you have adb working? I f so you could try rebooting, or booting into recovery to see if you see anything on the screen. It's possible that when you held the button combos, that it did boot into download and recovery but you couldn't see anything? In which case it could be a hardware problem. Hopefully it will fix itself! Sorry I can't be of more help..
Well adb shows the device as unauthorized. Reboot command says the same thing.
The home key is unresponsive to my finger print unlocks and no sound plays when I try to adjust the volume, like the ding sound it makes to hear if this is the volume level I want. There are never any of the capacitive touch vibrations or whatever its called to feel when you press a button on the screen.
I was wondering if it had something to do with hardware it's just strange that it would stop working from just being in my truck. From my knowledge it was never dropped or bumped heavily or anything, at least recently.
I guess it is possible something just burned up inside, that would be inconvenient, I've got to look up if its still in warranty. I love the size and performance of this thing.
Thanks for replying, hopefully more to come.
Still can't get it to work, same issues as above. I let the battery fully die which took about 2+weeks from the initial post. Which is to say that eventually the back and recent buttons stopped lighting up. I recharged it and after holding the power button for a few seconds the same condition repeated itself. If I touch the power button or home button the back and recent button back lights turn on for a moment and turn off again. There is no other indication of life. I would assume if it was just a dead screen then I should feel it try to turn on.
If I had to replace parts which ones should I look at first? Probably just the main board?
Buy a new one. Send yours in as defect. Done.
erase111
I see that is an old thread, but I having the same issue to a certain degree. The screen goes dark, but I can see the back light. If I play around enough times, (pressing the back and process button, before pressing the sensor button... Sometime, pressing the volume buttons and back button before pressing the sensor button), everything goes back to normal. Of course, it some random time, even when I am reading a web page or some other activity, it will go back to black.
So has anyone figured out what this issue actually might be? I thought maybe it was an issue with the ROM I was using, so I just moved over to LineageOS 16, but the problem still continues!