Last night I was using the tablet as normal. I sat it on the pillow next to me to grab my TV remote and I saw a pop-up on the screen out of the cornerbofbmy eye ,which was out of place. There was no reason for any kind of pop up.
This wasn't a notification. It was a pop-up window right in the center of the screen. The same place where the the window appears when you hold power down and you get the menu of Power, Restart, etc…
And in fact, all I saw of this pop-up was "… .. is turning off" and then it did.
But, it immediately came back on and the Android logo appeared like always then TWRP recovery screen flashed for a second and it went off. I have not been able to get it on since.
I have held the power button in for 30 seconds and I have tapped the power button. I have done every combination of power buttons with volume button and then repeated those with it plugged into the pc.
I just removed the back of the tablet and the battery out reading spot on. I'm confident that the battery is not the issue.
Now I'm lost on where I go from here. Is there a method to bypass everything and fire up the screen to see if that works?
I'm open to anything.
Any help would be life saving.
2kool2Bcruel said:
Last night I was using the tablet as normal. I sat it on the pillow next to me to grab my TV remote and I saw a pop-up on the screen out of the cornerbofbmy eye ,which was out of place. There was no reason for any kind of pop up.
This wasn't a notification. It was a pop-up window right in the center of the screen. The same place where the the window appears when you hold power down and you get the menu of Power, Restart, etc…
And in fact, all I saw of this pop-up was "… .. is turning off" and then it did.
But, it immediately came back on and the Android logo appeared like always then TWRP recovery screen flashed for a second and it went off. I have not been able to get it on since.
I have held the power button in for 30 seconds and I have tapped the power button. I have done every combination of power buttons with volume button and then repeated those with it plugged into the pc.
I just removed the back of the tablet and the battery out reading spot on. I'm confident that the battery is not the issue.
Now I'm lost on where I go from here. Is there a method to bypass everything and fire up the screen to see if that works?
I'm open to anything.
Any help would be life saving.
Click to expand...
Click to collapse
It sounds to me like you got the ota that killed your tablet. Is it the original shield tablet? You should check the serial to see if it was recalled. I don't know the address but just Google Nvidia recall battery, you'll find it
Sent from my SM-G386T1 using Tapatalk
Yes, it is an older tablet compared to the newer "K1 no stylus" version however, when checking the battery number it said it was a B01.
The idea ilof getting the kill switch never occured to me as a possibility due mostly to the above mentoned not being a candidate but also because i didnt realize the kill switch completely shut it off and somehow render the power switch useless.
I was thinking it caused a bootloop or something like that. My tablet has zero signs of life.
I will have to approach Nvidia tomorrow and hopefully get this somehow sorted out.
If this was in some way my fault and I misread the battery info i still shouldnt have recieved the kill switch because I never activated a replacement. Correct?
Is this is somehow reversible? I imagine its not since I can't power the damn thing on. I have 3 other Shield Tablets in the house. 2 OG tablets and 2 new K1s. If there was a method to use a working tablet to resuscitate my dead one, that'd be interesting.
I'm getting ahead of myself tho. I feel this is an Nvidia error and should be taken care of by them.
Word if caution there's guys going around on craigslist emailing about shield tablets that are for sale asking for serial number to verify warranty..only to submit a claim for the recall tablet .. Happened to my brother..
I'm not sure if anyone can help here, but I'm new to having an S2, so I have no idea on this stuff yet.
Anyway, so NFC will not turn off. If I go to it and select it to turn off (green dot is there), after 10-15 seconds it will show that it is off, however, when I back out and look at the previous screen, under NFC it says ON. Sure enough, when I select it again, the green dot is back... Obviously not a huge deal, but I will likely never use it, and I'm hoping it being off will help with battery life.
I also noticed you can't turn connections on/off with the Gear manager on a phone. Is there a better app to manage the Gear with? Something that gives more functionality and control?
Please and thanks!
I was told after the last update you can't turn NFC off. My acts just like yours.
Mine is the opposite problem - i can't turn mine on!
It has the same scenario. Turn on NFC, it freezes for 10 seconds, then it is still off
I have the same damn issue and its annoying me.
I have a few issues with my GS7 and am hoping someone here may be able to advise me.
1) Every now and then, approximately once or twice an hour, I get a notification sound or vibration (depending on setting), but no actual notification. I used a program to create a shortcut to the notification log and every time I look there is no notification in that log that corresponds, anybody have any ideas how I can work out what this is?
2) In a similar manner, I'm always getting the notification to choose my keyboard, even though I use Swiftkey and have the stock keyboard disabled. Any tips?
3) I have a wireless charging stand which until recently worked without issues, or none I remember. A few times recently I've taken my phone off in the morning and it's not at 100%, any idea what might stop it charging? The only thing I can think is that if I've woken up and disturbed the phone to check the time etc maybe that's causing it?
Any thoughts on these would be appreciated.
Any ideas anyone?
Same SwiftKey issue here no idea how to fix it.
i oressed the on/off button the home button and volume down buttton together and now have a blue screen ...saying downloading do not turn off target ...help needed how do i get my phone back to normal
Press and hold home + power for about 30 seconds, should come out of download mode.
Now this doesn't happen all the time every time, but usually around a notification and the screen is off, I go to hit a button to turn on the phone and it doesn't respond but the touch-keys are backlit. If Always-on Display is on, the screen is black regardless, not even showing the time or notifications. The only fix is waiting ~10 seconds for the phone to respond, which in some cases can be the difference between a missed call.
Now, seeing Always On Display off like that while it should be on made me think back to when I saw some sort of Nougat optimization setting that allowed me to select Always On Display, and as far as I remember, I did. That makes me think this process is killing AoD and it is taking that long to start back up, where the phone won't unlock until AoD (is back on and) can confirm that it's trying to wake up out of that state.
However, I don't believe this is the issue. I have turned off AoD and the issue still happened directly afterward, after a Messenger notification. This is stock firmware, however it is not factory firmware. I believe I downloaded it from Sam-Mobile, and they had the 7.0 Nougat upgrade that I would have gotten OTA with the factory firmware anyway.
Somehow I don't think it's the flashed firmware that is the problem, however please let me know if that's a possibility.
While the phone (or whatever) is hanging, I can still hold down the power button and I will feel haptic feedback as if the power menu has opened, and when the phone responds the power menu will be open, so the phone does still receive input. It just doesn't seem to act upon it or wake the screen properly. Is this perhaps merely a known Nougat bug or is it a glitch with my flashed stock firmware?
I'm sorry I don't have much more information. I do have Greenify, but I don't think that can or is set to disrupt anything that would affect the phone waking, or that would hang the OS, homescreen or whatever it is.
I haven't done other troubleshooting because I don't know what direction to attack this from, and that is why I have come here.
Help please!
Thanks in advance. :good:
UPDATE: It seems to happen directly after my screen shuts off from being on. So, if a notification wakes my phone but I don't interact with it in time and the screen goes off, when I press the power button it won't respond for ~10-15s. That's all I've really noticed... Anyone else have this problem??
BUMP.
Also, the same thing happens if I press the power button on my phone (by accident) and then go to turn it back on almost immediately - it won't respond for a while.
Cleared cache from recovery?
Got any settings enabled like "Keep screen off" which stops the screen coming on in your pocket, try disabling it in case that's causing it
Different gestures, disable them all in case they're messing with it
Last resort, factory reset
*Detection* said:
Cleared cache from recovery?
Got any settings enabled like "Keep screen off" which stops the screen coming on in your pocket, try disabling it in case that's causing it
Different gestures, disable them all in case they're messing with it
Last resort, factory reset
Click to expand...
Click to collapse
Won't be factory resetting unless I plan to root or something. I'll fiddle with the keep screen off setting that I do have on, and I highly doubt gestures would affect it but regardless I haven't enabled or used any. Thanks for the reply.
So the "Keep screen off" setting didn't affect anything. I turned Always On Display back on and I see the same issues. However, now sometimes I notice when I lock my screen or it shuts off, sometimes the AOD will appear and then quickly disappear, and stay in this hanging state for 10-15s. Then, if I haven't touched it during that time, the AOD will reappear. Any ideas? :/
So nobody else has this issue? This is still a problem, even if I press the power button and sometimes I'll want to turn it back on again as I just remember something to do before putting the phone away, it hangs on black for too long to be useful in that moment. The only potential solution is a factory reset?
Even if I lock the screen... If I try to turn it back on too soon, and I think it's specific timing... I have to wait 10-20 seconds. Sounds and vibrations still work.
UPDATE: This is still an issue. I've noticed a few more things, it does really seem like timing and as if there's some function in my phone literally not allowing me to turn on my screen - and I have never timed it but I think pressing buttons (power button) makes it take longer before it will respond again.
Kilva said:
UPDATE: This is still an issue. I've noticed a few more things, it does really seem like timing and as if there's some function in my phone literally not allowing me to turn on my screen - and I have never timed it but I think pressing buttons (power button) makes it take longer before it will respond again.
Click to expand...
Click to collapse
This happens for me also as a point of interest.
I am hoping that O solves it, since the monthly updates have never helped.
I haven't had this happen since upgrading to Oreo a week ago, so far so good!
Hi guys,
this morning i have a strange issue on my oneplus 7. The screen turned off, then it won't turn on again, the only thing on the screen was a little "pixel" flashing at the top center of the screen. I keept the power button pressed to turn off the phone, and after a bunch of seconds the screen turned back on (the phone was still on).
After that, i frequently see a flashing window that looks like a crash notification for some app, but it is so fast that i can not read what is related on... This window keeps popping out every few minutes (or seconds) but the phone seems working as alwatys. I've tried rebooting with no luck. There's no way to see some kind of log to check what app is crashing? The phone is consuming a lot of battery now (30% in the last 2h) and looks like Google Play Services has used almost 25% of battery.