I've been dealing with an issue on the latest cm11 builds. I can't seem to remedy it. After using the tablet for a few minutes, the device would lock up, and the notification and navigation bars would disappear, and I get forced to the lockscreen with out any widgets. Trying to unlock the device causes a lock up again, requiring a force reboot.
I've tried clean installing and changing roms. I also noticed that pulling the quick tiles causes the crash often. However its difficult to replicate, as it randomly occurs.
I'm going to try flashing an older build.
Is this a cm11 issue?
Sent from my TouchPad using Tapatalk
Have had similar problems but they seem corrected now. I am using the latest Pac-man Shumash rom and on another TP, the latest Jcsullins.
Make sure to wipe the cache and Dalvik cache before installing. Also, use the latest gapps. I assume you are using the TPtoolbox for installing?
Also, set lock screen to off.
Same problem
I have the exact same problem. After a period of work, it just seizes up forcing me to lock screen and then just turning off the screen. Again it's most usually caused with the pull down tiles. A thing I noticed is when it seizes up you have some time before it locks you out. At that time I pressed the home button on the touchpad and it took me to the main screen. At that point the pull down tiles and the bottom 3 buttons (back, home, tasks) are unresponsive. I've now reset the Davik cache and cache, will see if this fixes the problem.
Edit: After the reset same thing is occurring, but this time there is no lockout. Just the menus becoming unresponsive. If I press one of the menu buttons everything becomes unresponsive, after a while it return to normal (except the menu buttons). If I press them again ... well just repeat the above. After a couple of times the tablet shuts down.
***I used the toolbox with pa_app, Cyanogenmode11 (the one from Jcssnuell (or something)) and Clockworkmod - all after deletion of previous systems. Before that I had Cyan9 which had the same issue i believe.
After some guesswork I believe I may have found the cause. I've tried resetting the cache and Dalvik cache a couple of times, problem persists...
Last reset I skipped the Google account thing and set the language to English (United States). I don't know what helped, but it seems to not be crashing any more.
I will add my google account after a little more time to see if it crashes or not and then see if it crashes with the account. It would be super funny and NOT FUNNY AT ALL if it was actually the language settings that are causing it.
I am having these exact same problems as well. Freezing up pulling down quick tiles. Nav buttons becoming unresponsive Also, sometimes is will just spontaneously do what looks like a "quick reboot" where is goes to the CM spinning boot animation for a few seconds, and then back to the home screen, usually followed by unresponsive buttons, etc.
I've tried jscullins 0625 and 0409, Milaq latest nightly, Shumash pac-man. All have the same issues. Gapps is gapps-kk-20140105.
I used TPToolbox to do the partitions and initial install. I think I'm going to try a full wipe and start over.
1905
I did some more searching and found that Google hotword detection can cause problems like these. I set that to disabled and my problems seem to have stopped, so far
Same problem here... Only all of my apps will not load before it crashes. Using latest milaq cm11. Wipe caches and problem persists. I rarely use googles hotword, believe its shut off...
Ideas??
Related
I'm getting a crashed UI when checking notifications by swiping the top left corner downward.
I'll get an email or hangout and when I go to check it via the notification area it just blacks out the screen, then has a slight panic attack and switches between the home screen and the lock screen once or twice but this takes 5-10 seconds and it is obvious there is some sort of crash. However there are no crash notifications from android. Then my notifications seem to work find for a little bit.
It is similar or possibly the exact same thing as what is described here http://forum.xda-developers.com/showthread.php?t=2743255
Does anyone know of a fix for the UI / Notification Bar crashes that are happening? I'm seriously considering getting a new tablet and using this as a good excuse.
Apparently clearing the davlik, cache, and doing a factory reset doesn't seem to help.
I'm running CM 11 M6 EMMC on my Nook HD+
_Boondock_ said:
I'm getting a crashed UI when checking notifications by swiping the top left corner downward.
I'll get an email or hangout and when I go to check it via the notification area it just blacks out the screen, then has a slight panic attack and switches between the home screen and the lock screen once or twice but this takes 5-10 seconds and it is obvious there is some sort of crash. However there are no crash notifications from android. Then my notifications seem to work find for a little bit.
It is similar or possibly the exact same thing as what is described here http://forum.xda-developers.com/showthread.php?t=2743255
Does anyone know of a fix for the UI / Notification Bar crashes that are happening? I'm seriously considering getting a new tablet and using this as a good excuse.
Apparently clearing the davlik, cache, and doing a factory reset doesn't seem to help.
I'm running CM 11 M6 EMMC on my Nook HD+
Click to expand...
Click to collapse
How did you install it? Can you describe the process or link to the tutorial you used?
Did you do the factory reset before or after the install?
deleted
I can confirm the same problem. It is reproducible. Which does not mean it happens every time but over the course of using the tablet for 5 hours it happend around 3 times. Very very annoying!
Something similar happend when I heavily used Firefox without using the notification bar. Maybe it is also an issue when all memory is taken?! Should hopefully be fairly easy to fix since it was introduced somewhere between M4 and M6.
sirbender42 said:
How did you install it? Can you describe the process or link to the tutorial you used?
Did you do the factory reset before or after the install?
Click to expand...
Click to collapse
I've installed it flashing in CWM
I've tried doing the factory reset before and after the install.
Same issue here.
I am running CM 11 internal and have the same issue...
According to this post, this bug is due to be fixed in the next nightly.
ejstubbs said:
According to this post, this bug is due to be fixed in the next nightly.
Click to expand...
Click to collapse
I posted this. The bug report I posted sounds like the notification bug we see. According to the changelog the bugfix should be in starting with the cm-11-20140513-NIGHTLY-ovation.zip
You can download here: http://download.cyanogenmod.org/?type=nightly&device=ovation
Please let people know if this fixed it.
Still an issues (running 0515-nightly)
I flashed the nightly from 20140515 and am still having the resetting issue... Anyone else?
Okay, I've got several Samsung Keyboard issues, so bear with me as I explain as it may be a bit long.
First and foremost, my keyboard keeps crashing. At first, I assumed this was just a general issue that a reboot was necessary in order to fix. This is entirely not the case, as it even happens directly after a reboot at times. Also, they keyboard crashing happens in several different ways. This normally happens while using Kik messenger, but it does happen at times while using normal text messaging as well, so I'm assuming Kik isn't the problem.
1)Normal keyboard crash, where it gives an error and the phone tells me it has stopped working.
2)Keyboard entirely disappears, yet I can still type by touching the black area where the keyboard would normally be.
3)Keyboard doesn't disappear, but text entered doesn't appear inside the text box until after closing the keyboard.
4)Keyboard crashes normally, causing either (2) or (3) to happen.
I'm unsure what's going on. I am running a rooted system, so I'm guessing it may be some issue with the root combined with something I've installed, but I'm unsure what it could be. Keyboard was (and has been) working fine for months and months, and I haven't installed anything new since the day I rooted.
I'm rooted with Rooted Community Rom. I've not had any problems with this root since I've installed it, so I don't know what the Hell is going on. Any input would be wonderful, especially if someone could tell me what's causing this to happen, or if others have this issue.
BobScramit said:
1)Normal keyboard crash, where it gives an error and the phone tells me it has stopped working.
2)Keyboard entirely disappears, yet I can still type by touching the black area where the keyboard would normally be.
3)Keyboard doesn't disappear, but text entered doesn't appear inside the text box until after closing the keyboard.
4)Keyboard crashes normally, causing either (2) or (3) to happen.
Click to expand...
Click to collapse
I'm thinking 1) is due to Low Memory causing Force Close (due to many running apps) or the Keyboard App data somehow got corrupted and 2) and 3) are happening due to GPU not being able to draw the Keyboard and letters when called upon; can't entirely be sure unfortunately.
I can think of two solutions to try however:
Clear Data and Cache of Keyboard App
Go to Settings -> Apps -> ALL -> Keyboard
Select Clear data and Clear cache
Reboot or start a messaging app and start typing again
Try another Keyboard App
Many options available, try: AOSP Keyboard, Google Keyboard, Swype
Hope that helps!
Clearing it and letting it reload does fix all of the issues, but it just happens again shortly after. I don't have very many apps, and normally still have around 100MB RAM free at all times. I don't use social media or anything on the phone at all, and most everything else is just Google things, Kik messenger, and stuff pre-installed on the phone(Like the normal sms app, phone app, etc) Reboot, clearing memory, etc, all have the same result. Fixes the problem, only for it to happen again shortly afterward. Sometimes, in the case of the keyboard going blank, clearing memory doesn't fix the issue. It re-loads with a blank keypad. Doesn't happen very often, but it did once or twice today.
I've tried using Swype since it's already pre-installed, but it's not really the same size as the standard keypad and it's difficult to adjust to typing on it :\ I suppose I'll have to make due with using it for now, because that keypad doesn't seem to freeze or crash at all as I've used it (wasn't for very long, but the normal keypad tends to crash at least twice within the span of an hour if it's used regularly).
It wouldn't even be a problem if it wasn't happening so damned often. I'm used to things crashing at random, because having a load of apps (before) caused it to make things crash sometimes. But this is definitely not a "sometimes" issue. It's a "Please God, make it stop" issue lol
BobScramit said:
It wouldn't even be a problem if it wasn't happening so damned often. I'm used to things crashing at random, because having a load of apps (before) caused it to make things crash sometimes. But this is definitely not a "sometimes" issue. It's a "Please God, make it stop" issue lol
Click to expand...
Click to collapse
I know how that feels. I remember experiencing those keyboard symptoms you mentioned in the past. Frankly, I couldn't leave the stock ROM fast enough.
You should try AOSP or Google Keyboard, the keys are bigger and appear less confusing than Swype.
It worked when I first booted up. After a few hours it quit. I did a factory reset, and the same thing happened. I then went through my running apps and turned them off until none were running except the system apps. Still didn't work.
Anyone else have this happen that can suggest a fix? If I have to reset and install apps one by one, how do I do that, since on signing into Google the apps auto load
gmermel said:
It worked when I first booted up. After a few hours it quit. I did a factory reset, and the same thing happened. I then went through my running apps and turned them off until none were running except the system apps. Still didn't work.
Anyone else have this happen that can suggest a fix? If I have to reset and install apps one by one, how do I do that, since on signing into Google the apps auto load
Click to expand...
Click to collapse
To fix auto load, you can change the system setting to not backup apps; it's in Settings > Backup & reset. I thought upon initial Google account sign in you could switch that setting off too, and that prevents the apps from auto-installing. I have backup turned off because on previous devices and versions of Android it was contributing to battery drain.
laur3n.newm4n said:
To fix auto load, you can change the system setting to not backup apps; it's in Settings > Backup & reset. I thought upon initial Google account sign in you could switch that setting off too, and that prevents the apps from auto-installing. I have backup turned off because on previous devices and versions of Android it was contributing to battery drain.
Click to expand...
Click to collapse
I did what you suggested, adding single apps and confirming the ambient function worked. Found an app that seemed to be the cause, and upon uninstalling it the ambient function came on line. However, about a half hour later, it stopped working again. Spent over an hour on the phone with Moto, and they figured out that ambient doesn't respond unless the phone has been asleep more than 10 seconds. That seemed to work for me. So I did my 4th reset/install of the day, and again, it worked for a while, even with all my apps (including the one that seemed to be the cause in the first place). And then, it stopped again.
I searched, and one suggestion was that ambient won't work unless you have a locked screen. I usually don't use a lock, but what the hey, I'll try it. Set up a pattern unlock and (wait for it.........).
Nope.
I'm stumped.......
Mine seems to stop displaying the ambient as well. It will display a few times initially and then stops. I don't know if it extends its sleep period after every interval or not. Also seems like if you lift up your phone to look at your ambient notifications, that disables any repeat display too
Has anyone else had problems with auto screen rotation,mine has twice now in 4 days started either getting stuck in landscape mode or would start rotating back and forth by itself,I fixed it for now by clearing cache,but curious if anyone else has had this issue.
I have the same problem on 910c variant, even factory reset does nothing, I hope it is not a faulty hardware
Ditto on my 910T3 TMo. Stock rooted. Auto screen rotate stopped working 2 days ago.
I have wiped cache and dalvik.
I have tested sensors with other apps (they work).
I have run self tests (dial *#0*#)
I disabled all Xposed modules
I tried 3rd party screen rotation app
None of these have resolved the problem.
Also tried wiping Dalvik and cache and reflashing the kernel.
That didn't fix the issue either.
the problem seems to happen when the phone is hot, because when I wake up In the morning I turn it on and doesn't have the problem
I have the same exact issue. I've replaced my phone 3 times because of it. BTW I'm on 910T.
Hopefully this new software update that just rolled out fixes this issue.
I also noticed when in the camera app, if i rotate the phone between portrait and landscape, the controls on the screen rotate appropriately.
So again, that verifies the sensors are working and it isn't a hardware issue for me.
Also tried using stock launcher, but no change.
Am about ready for a factory reset.
I've experienced this also but I thought/think it was a Nova launcher bug that seems to have corrected itself.
Since the recent update everything has been running fine. So far I haven't gotten the screen rotation issue!
It used to happen at least 2 times a day. I think it might just be a software based issue.
SM-N910T still on 5.0.1 stock having the same issues. It gets stuck in landscape, stays stuck in over landscape position.
I ended up doing a factory wipe and updating to the stock rooted DOK2 rom that just came out.
So far no issues and screen rotation is working (along with several other nuisance issues that went away).
Just as an update I lost screen rotation on DOK2 stock rooted ROM. However, I believe it may have been related to some debloat cleanup I was doing.
Under Ti Backup I searched for "facebook" and manually forced uninstall of the 4 "system" apps that came up.
I don't know what any of those would have to do with screen rotation, but one of them does.
I was not able to successfully restore those files via Ti Backup either, so ended up dirty flashing the same DOK2 zip file to restore them.
That fixed it. So rather than forcing uninstall of those files I just removed updates and disabled them via the android app manager.
So far so good.
Hi Everyone,
It has been going on for roughly a year now, while I'm using my phone it suddenly just freezes entirely. Touchscreen just becomes unresponsive, can't tap on anything, gestures don't work and notification bar can't be pulled down.
Physical buttons does not seem to be affected, even if my screen is totally frozen I can still adjust volume levels and I can lock the phone via the power button. After locking and unlocking my phone, everything goes back to normal, touch responsiveness comes back and starts working as it should till the next hiccup.
It happens frequently, there are times when the screen locks up 2 or 3 times in a 10 minute period window. Every time this happens, I need to lock and unlock my phone and it starts working again.
Also it doesn't seem like a specific application is doing it, it happens when I'm browsing websites via Google Chrome, it happens with Amazon App, Messenger, Google Play Store, even on the Google News feed.
It gets more and more annoying as time goes by and it still hasn't been fixed.
I have been in contact with Google Support in the beginning when it started, but all they suggested is that I should do a Factory Reset (which I did).
Has anyone else experienced this issue or is it just my device doing this?
PS.: My phone is fully stock, hasn't been messed around.
Any physical damage to the device? & Have you tried checking if the issue occurs in safe mode too? If it is caused by a 3rd party or background app it wont replicate in safe mode.
Scan with Malwarebytes.
Try clearing system cache.
Try safe mode and a hard reboot.
That qualifies for erratic behavior and may be the only sign of a virus or trojan you'll see... at first.
Either way you could be headed for a boot loop.
Regardless even if Malwarebytes finds nothing it's factory reset time. Nuke it; a trojan can do a lot of damage to you in a short amount of time.
After the reload change your Google password.
Before you load -anything- make sure the issue is gone!
If it persists it's either a firmware or more likely a hardware failure.