Hi All
I am running CyanogenMod version - 12.1-20160529-NIGHTLY-klimwifi
Kernel version 3.4.105g766de8b
I have as you can tell by my heading an issue, my tablet after using the plex app decided to power off and would not restart until I tried turning it on in recovery mode. When it did turn on the lock screen did not display the usual text (swipe to unlock) and the notification drawer would not display or pull down.
I tried cycling it on and off a few times and alternating between turning it on in recovery or download mode but no response, eventually allowed me to access the notification drawer and by creating a new profile I could access everything again. I deleted this profile just to make sure and tried it again and discovered the if I hit the volume buttons a few times everything works fine the tablet though has become slower in its response.
Has anyone else come across this issue.
Related
I've ran into a very odd problem recently: I can't turn off the screen while I'm in the lockscreen - it keeps flashing on and off constantly every 2 seconds.
I have to unlock first, and than the screen shuts down absolutely fine (using the power button / inactivity timeout).
This also happens when receiving an unanswered call - the lockscreen keeps blinking on and off until I unlock it.
I've tried re-flashing the ROM (and checking out other roms), and another kernel - no help, it still happens.
I've tried checking it out in safe mode - happens as well.
Happens when the phone is plugged or unplugged to USB, the connector is working fine.
Happens on 4.1.2 & 4.2.1 with all lockscreen options (slide PIN password etc) - with every gadget / extra feature disabled.
I've tried disabling every app I can think off, switch to airplane mode (in case it comes from some signal / wifi), and checking with airpush detector & AVG.
This is driving me crazy, is there a way to debug this and find out what keeps waking up the phone into this freaking loop?
Update: I've found a partial solution - using an alternative lockscreen (tested with go locker) seems to solve this problem.
this means something is wrong with the vanilla lockscreen apk / some setting.
does somebody have the 4.1.2 lockscren apk available?
[Q] Phone get stuck with screen locked. Rebooting starts an endless "startloop"
Hi, I have this Galaxy S3 i9300, with Wanam ROM and Boeffla-Kernel 2.12.
Sometimes, when I lock the screen, it just freezes in there. I'm unable to wake it up, and the LED keeps flashing the last notification.
Most of the time, I get notice of it when I receive a notification (it rings) and the phone cannot wake up. Calling and trying to trigger another notification does not wield any results.
The weird part is this: When I restart it, the OS starts as it should, but it "skips" the lockscreen (when I restart my phone, first thing I'm presented is the pattern lockscreen, all Android default), and it goes directly to the home screen. The touch screen is unresponsive (but it does vibrate when I press any of the two bottom buttons), but phone is still alive (few animations plays smoothly).
Then it restarts. The startup LED (fading blue to bright blue) doesn't turn off (normally it would turn off even before the lockscreen is presented).
Disabling the lockscreen wouldn't solve the problem, nor does starting on "safe mode". Same issue.
Booting into CWM and wiping data/cache folders solves it, but resets my phone. Restoring a backup (data folder only) also works.
Funny fact is that even with a fresh backup (which works), it might just hang up like before (although I didn't modify/install anything).
Logging files should give me some info, but I don't know how to retrieve them, let alone on this condition.
The only step I did so far to try to solve it was to disable a notification program (Logical, it seems to hang up when I receive a notification, and as a wipe to the data folder solves it, I presume it's an rogue app. But never, ever I had a problem with this app, but who knows if on an update, it's crashing my phone)
Does anyone have any information regarding to this? I've never seen something like that.
How do I recover my logfiles during an emergency?
-----------
Had another lock-up. No notifications received and the notification app was disabled. How do I get the log file?
[Q] Phone get stuck with screen locked. Rebooting starts an endless "startloop"
(I posted on the wrong location first time, sorry)
Hi, I have this Galaxy S3 i9300, with Wanam ROM and Boeffla-Kernel 2.12.
Sometimes, when I lock the screen, it just freezes in there. I'm unable to wake it up, and the LED keeps flashing the last notification.
Most of the time, I get notice of it when I receive a notification (it rings) and the phone cannot wake up. Calling and trying to trigger another notification does not wield any results.
The weird part is this: When I restart it, the OS starts as it should, but it "skips" the lockscreen (when I restart my phone, first thing I'm presented is the pattern lockscreen, all Android default), and it goes directly to the home screen. The touch screen is unresponsive (but it does vibrate when I press any of the two bottom buttons), but phone is still alive (few animations plays smoothly).
Then it restarts. The startup LED (fading blue to bright blue) doesn't turn off (normally it would turn off even before the lockscreen is presented).
Disabling the lockscreen wouldn't solve the problem, nor does starting on "safe mode". Same issue.
Booting into CWM and wiping data/cache folders solves it, but resets my phone. Restoring a backup (data folder only) also works.
Funny fact is that even with a fresh backup (which works), it might just hang up like before (although I didn't modify/install anything).
Logging files should give me some info, but I don't know how to retrieve them, let alone on this condition.
The only step I did so far to try to solve it was to disable a notification program (Logical, it seems to hang up when I receive a notification, and as a wipe to the data folder solves it, I presume it's an rogue app. But never, ever I had a problem with this app, but who knows if on an update, it's crashing my phone)
Does anyone have any information regarding to this? I've never seen something like that.
How do I recover my logfiles during an emergency?
-----------
Had another lock-up. No notifications received and the notification app was disabled. How do I get the log file?
I have been running my Tablet Z (pollux_windy) on the latest Oreo release (15.1) . Have installed a few nightly updates - but the problem below keeps occurring.
It generally runs really well - but I have discovered something that seems to be causing issues for me and wondered if anyone else has the same issue.
I like to use the full real estate of the screen, so found the Settings/Display/Expanded desktop setting that lets you hide the top status bar and the lower navigation keys go into autohide mode (you swipe up from the bottom of the screen to see them).
First time I enabled them all seemed great - Then I left the tab and the screen timed out.
I tried to wake it up (using the power button or double tap on the screen) - Nothing.
Tried this quite a few times over a few minutes.
Did a Hard power off.
Restarted eventually. Seemed ok until the screen blanked out - then the same as above.
I did eventually get the screen to wake back up without a reboot by trying the double tap and quick press of the power key. But it took quite a few attempts.
Finally I turned the full screen mode off (ie brings back the status bar and nav controls) and everything was back to normal behaviour - ie always wakes back up when required.
I have tried changing the expanded desktop mode several times and it always locks things up after the screen times out so have now given up on it.
Anyone else finding that setting this mode causes lockups?
robjg63 said:
I have been running my Tablet Z (pollux_windy) on the latest Oreo release (15.1) . Have installed a few nightly updates - but the problem below keeps occurring.
It generally runs really well - but I have discovered something that seems to be causing issues for me and wondered if anyone else has the same issue.
I like to use the full real estate of the screen, so found the Settings/Display/Expanded desktop setting that lets you hide the top status bar and the lower navigation keys go into autohide mode (you swipe up from the bottom of the screen to see them).
First time I enabled them all seemed great - Then I left the tab and the screen timed out.
I tried to wake it up (using the power button or double tap on the screen) - Nothing.
Tried this quite a few times over a few minutes.
Did a Hard power off.
Restarted eventually. Seemed ok until the screen blanked out - then the same as above.
I did eventually get the screen to wake back up without a reboot by trying the double tap and quick press of the power key. But it took quite a few attempts.
Finally I turned the full screen mode off (ie brings back the status bar and nav controls) and everything was back to normal behaviour - ie always wakes back up when required.
I have tried changing the expanded desktop mode several times and it always locks things up after the screen times out so have now given up on it.
Anyone else finding that setting this mode causes lockups?
Click to expand...
Click to collapse
Hello!
Please write your problem to an official bugreport https://wiki.lineageos.org/bugreport-howto.html to let the LOS developers team about the encountered issue.
Thanks. Signed up to add the fault and found someone witha different device reporting the same bug around a week ago.
Added my confirmation of the problem with different hardware.
Fingers crossed someone may have a look at it when time allows.
Hi all,
I got this Xperia M5 that's been giving out warnings about memory being full and I suppose it finally gave in. It only partially boots after like a full minute of showing you those blue waves. When it 'boots' the screen is black and nothing works, except you can see the status bar with just the battery icon, no-SIM icon and the clock.
Weird thing is when the device is powered off, you can press the power button once and it'll display a large battery indicator which shows the percentage normally-- I've seen this go up from 0 to over 90 something incrementally.
But when it's 'on' the way I just described, the battery is always at 0% with a red ! next to it.
Anyway, when it's in this weird half-life mode, you can actually pull down the notification bar normally, and tap stuff as well. Flashlight works, you can see an actual WiFi list (nothing happens when you connect) etc. When you launch stuff through here though, like settings, it won't open anything. It'll make the sound as if it's launched something but the remainder of the screen will still be black.
Using the dedicated camera button, I can access the camera. It works (sort of), meaning you can see the camera display where the screen used to be black. And it immediately says "system process is not responding," so I'm guessing this is a system issue where it can't load basic stuff like the homescreen?
Whatever you do or don't do, it stops responding after a couple minutes and shuts itself off.
Stuff I've already tried:
- Safe mode (volume down + power), just 'boots normally'
- Recovery mode (volume up + power) done that for over two minutes, does nothing or just 'boots normally'
- Hold down the tiny yellow 'off' button under the SIM/SD cover, did nothing.
- Xperia Companion: PC won't recognize the phone either in that zombie state, or when it's off, so I tried 'device cannot be detected', shut phone down, held down volume down button, connected USB still holding down, waited for a while and viola, nothing happened.
It's factory OS, never messed around with it and I don't know the version (could be 5?).
Any ideas?
Guys at this point all I'm wondering is if anyone ever managed to brick a phone that's as semi-responsive as this one, in the history of bricked android phones anywhere.. I mean how could it be bricked when you can (sort of) boot and even open the camera?
you said it boots in download mode?
paranoic(d) said:
you said it boots in download mode?
Click to expand...
Click to collapse
No I wouldn't say download, it's weird-- there's the status bar at the top and soft navigation keys at the bottom, but the homescreen in between these is black. I tried tapping this black area to see if stuff is there logically but you just can't see them, but there was no interaction, no sound or anything.
I am able to pull down the status bar to reveal the usual buttons and such, like I mentioned before you can turn on the flashlight, click to see a list of available wifis etc. But you can't access settings through here, I mean you tap settings and the main part of the screen is still black.
The only way to get the screen to work is to open the camera through its dedicated button, where the camera display works normally, you can switch cameras etc. Tried accessing the gallery through here but it didn't work.
I just don't wanna buy a new phone when this one doesn't seem bricked at all. If it like didn't respond at all and nothing appeared on the screen I wouldn't think twice before buying the first phone I see on Google.
im afraid that you have to flash stock rom again if you will boot into download/fastboot mode.but your problem seems strange.what was the last thing you have done before phone stuck like this?
paranoic(d) said:
im afraid that you have to flash stock rom again if you will boot into download/fastboot mode.but your problem seems strange.what was the last thing you have done before phone stuck like this?
Click to expand...
Click to collapse
Not my phone but it'd been going on about low memory for a while now. I got the PC to recognize it once in that zombie state, so I'll try that with Companion if I can get it to half-boot again. I'll post updates if anything happens.
antiglue said:
Not my phone but it'd been going on about low memory for a while now. I got the PC to recognize it once in that zombie state, so I'll try that with Companion if I can get it to half-boot again. I'll post updates if anything happens.
Click to expand...
Click to collapse
okay keep us updated