Hey guys,
I recently upgraded my Tab S7 (T870) to Android 12 with One UI 4.0. The tablet worked perfectly fine before the update but now the screen stays black sometimes when I press the power button or double tap the screen, although the Tablet is turned on. I hold down all three buttons, force a restart and then it works again. Why is that happening from time to time? I think it's a bug related to the new update
Factory reset if you already haven't, otherwise clear the system cache.
Avoid using SmartSwitch.
It may be a 3rd party app that doesn't play well with 12.
Make sure your critical data is fully backed up. Boot loops if they do give any warning beforehand its usually lagging, glitches and instability... then boom.
I don't update my Samsung devices and they remain problem free.
Rule #1 - if your OS is fast, stable and fulfilling its mission... let it be!
This happend to me today for the first time ever. I just I rooted my t870 and locked bootloader and installed firmware over itself. It happend while charging the device it wouldn't wake up the screen was black but the back lights were on. Must be a bug. I'm on Android 11 and have had the tablet for like 5 months and it's the first time I noticed this.
Related
Using the stock ROM for the Galaxy Nexus, Android 4.04 from Google, I'm finding this bug (which has been elsewhere reported, but not acted upon by Google) where the touch screen is unresponsive. You press the 'power' button, the 'slide to unlock' screen appears, but the touch screen doesn't respond to anything.
If I get a call while the phone is sleep, the same thing occurs - can't answer the phone.
I usually have to put the phone to sleep/wake it up 5, 6, or more times before the touch screen again becomes enabled in these situations.
Does anyone know why this happens? There has been much conjecture about this, but I have yet to see anyone say for sure why this would be happening. A disabled touchscreen at such a crucial point in a GUI is pretty horrific.
- Tim
was gonna make a new thread on this but since i found one with the exact same thing happened figured why waste space, but anyway this just happned to me running stock 4.0.4 cdma unrooted. was just charging my phone unlocked it to check twitter and the lock screen was completely unresponsive for whatever reason. I continued to turn the screen off and on several times and then just decided to pull my battery and it worked fine.
This is the first time its happened to me and its kinda troubling as I dont want this to be a recurring thing and was wondering if this continues to happen or its just some single random occurence?
Hey,
I have been experiencing a bit of weird bug with my Nexus 7 2013. Basically, when I go to use my Nexus after it has been idling for a little while, it will often be on when I open the tablet from its case. However, it does not display any typical Android elements but shows only a lit black screen...I have to hard reset it to get it back to normal function...
Any ideas? Very perplexed....I have tried different kernels and factory reset several times.
--Android 4.4.4 (Rooted)
--Kernal: Faux Kernel 22u/Franco R17
One thing to note: I can replicate the behavior by quickly pressing the power button several times. It goes right into the 'lit black screen' and needs to be reset.
Thank you!
dsudi19 said:
Hey,
I have been experiencing a bit of weird bug with my Nexus 7 2013. Basically, when I go to use my Nexus after it has been idling for a little while, it will often be on when I open the tablet from its case. However, it does not display any typical Android elements but shows only a lit black screen...I have to hard reset it to get it back to normal function...
Any ideas? Very perplexed....I have tried different kernels and factory reset several times.
--Android 4.4.4 (Rooted)
--Kernal: Faux Kernel 22u/Franco R17
One thing to note: I can replicate the behavior by quickly pressing the power button several times. It goes right into the 'lit black screen' and needs to be reset.
Thank you!
Click to expand...
Click to collapse
What do you mean by 'lit black screen'? It sounds like a hardware problem to me.
-----------------------------------------------------------
Don't Say Thanks.
Press The Thanks Button.
DEVICE:
Nexus 7 2013 LTE (DEB)
Stock 4.4.3 KUT84L
Stock Kernel
I have the same problem with my nexus 7 2013. It happens very often. When the screen was turned off for a while, it won't react to anything and the screen stays black, but the notification led is still active. The only thing that helps is pushing the power button very long. Then the Google logo shows up and it boots up normally. The tablet is on original Android 4.4.4 not rooted.
I will ask for an exchange in the next couple days.
gaschue said:
I have the same problem with my nexus 7 2013. It happens very often. When the screen was turned off for a while, it won't react to anything and the screen stays black, but the notification led is still active. The only thing that helps is pushing the power button very long. Then the Google logo shows up and it boots up normally. The tablet is on original Android 4.4.4 not rooted.
I will ask for an exchange in the next couple days.
Click to expand...
Click to collapse
Great haha. I know that I am not the only person with this problem now ...So you think it is hardware related and not software?
If so, UGH! I've already had to sent this POS in twice now .
This morning I removed my SW2 device from the charger, and after noticing that my OnePlus smartphone didn't recognize it anymore I tried to reboot the smartwatch.
Since then it seems to be no longer working. The Sony logo appears, there is a loading bar for a few seconds, then the screen flashes for a moment, and it goes back to the Sony logo, and so on.
I have also tried to switch off my OnePlus completely in order to exclude any pairing bug.
I read from the web that it might be possible to force a factory reset by pressing the power button for 15 seconds, but this doesn't work for me - it simply switches the SW2 off.
By putting it again under charge I notice that it turns automatically on, but even then it remains stuck in the bootloop.
Please help, I feel like I bought just an expensive little wrist brick.
Something like this has started to happen to me to... when the watch boots the Sony logo can be either yellow.. .or blue.. or white...
Edit: Try the procedure described in this post. Only 5 mins since I did it.. but so far, so good. :highfive:
I've fixed the problem - by buying a Moto 360.
I would advise everyone to stay away from SW2. It runs a proprietary OS + proprietary software that is just not compatible with everything that is happening in the rest of the world with Android Wear, it's not compatible with all the apps released for Android Wear (and hence it's compatible with only few apps exclusively released for SW2), and in case something goes wrong for any reason (like my bootloop), it's not even possible to perform a factory reset.
Sony Smartwatch 2 stuck in bootloop after a normal reboot
anybody help????
Hi there,
i couldn't find my problem already discussed via the board search, so i'm posting it here. i hope this is the right board, if not please relocate.
i'm using the find7a since about 1 year now. the only updates i did for colorOS were the ones that have been proposed automatically via the popups. but these i did every time.
i have alwas had several issues with the phone/os, mostly random shutdowns without any reason. but at some point, these shutdowns suddenly declined and i got used to live with the few that still occur from time to time. but now i have a much bigger problem and i don't know where it came from:
few days ago, i got the popup that a new os-update was available. i had a little time so i did it instantly. without any problems the update was installed and after that the phone booted as always and nothing strange happened. 1 day later i recognized that something had changed. i wasn't able to turn on the wifi anymore! same goes for the bluetooth. also the automatic screen rotation (when you turn the phone in a right angle) didn't work anymore! but all of them DID work for the 1 day since i made the last update. so i assumed it has nothing to do with the new os-version (which is 1.2.9 btw). i didn't change anything in the phones settings, everything was the same. but from one moment to the other these three problems suddenly came up. maybe even more that i didn't recognize yet.
although everything worked fine for 1 day since the update, i thought maybe the update could be the problem after all. so i wanted to flash another version of colorOS. i tried the 2.0.8i which was considered stable by the official oppo board admins on friday. the flashing worked fine, colorOS 2.0.8i booted, but the problems remained! still no wifi, no bluetooth, no screen rotation.
next thing i thought: maybe it's a hardware problem. so i flashed another ROM (always making a factory reset + wiping all cashes and data from the internal storage first), i tried a few. they were all flashed successfull but most of them hung up during the first boot sequence (cyanogenmod, paranoid, nameless), i always got stuck in the loading screen. last one i tried was OMNI ROM, and this one finally worked, meaning i got it started. first thing i did was checking the wifi connection and what do you know? the wifi worked just fine, my home network was found immediately und the connection went all good! which means a hardware defect should be out of the question.
this brings me back to thinking the problem lies within colorOS. which would be very sad becaue i really like colorOS and i would like to keep using it!
reproduction of the issues:
to reproduce the problems, when you are on the home screen you simply have to drag down the shortcut-menu. then tap on "wifi" and watch the symbol turn into the one for "loading" (the circling line). and then: nothing happens. the loading symbol just keeps on circling on and on. when you slide the menu up and down again, the normal "wifi-off" symbol shows and wifi is not turned on.
almost the same goes for the bluetooth. only when you tap this icon, the loading animation stops after a few seconds und the "bluetooth-off" icon appers again, this time without sliding the menu up and down. bluetooth stays turned off anyway.
for the rotation problem you just need to got to an app, where you can type in some text, f.e. whatsapp or gmail. tap the message area to make the keyboard and the cursor appear and then turn the phone from vertical to horizontal. normally the display should rotate automatically, but it doesn't it just stays in the vertical view mode. of course the rotation ist activated all the time, so no need to advice that
the rotation problem does not only occur when trying to type sth. in but also when i want to watch videos (f.e. with the vlc player app). the video stays locked in the vertical mode, making the image very small of course. this is also very annoying!
so, what do you think could be the reason for my problems? and what could i do to solve them? i hope you can help me.
i attached a log-file which hopefully shows the bugs.
my current specs are:
find 7a
colorOS 1.2.9
TWRP 2.8.6.0
greetings
tim
Hey all,
I have searched the web, but most of the info I found relates to the screen going black during calls, which isn't the problem I'm having. My screen is actually fine during/after calls.
This is happening to me randomly and is just the home screen. The lock screen and notifications are still visible when this problem occurs.
I can randomly press the screen hoping to hit an app and they open fine. Sometimes when I back out of the app, the homescreen returns to normal although it can take a few goes, sometimes I have to restart the phone. It isn't happening all the time, in fact before today the last time it happened was Wednesday. I'm just worried that it will become more frequent and as is stands I am still under the 30 days in which I can return the phone for a refund.
I was using Go Launcher Z, although I have returned to the default launcher in case that's what the problem is. Phone has all updates installed, is on 5.1 with the build number LMY47D.
I cannot boot into recovery mode to wipe the cache partition, I must have tried about 30 times. Majority of time the phone just turns on, a couple of times it came up with the option to do a factory reset.
Would appreciate any help