I keep getting errors immediately after booting, saying that the System UI crashed. I'm on CM11S, and I don't have any major tweaks or frameworks, it should be pretty much stock. I was able to obtain a debug log at boot time, which I attached to this post.
Could anyone please give me a hand with this? TIA!
Bump!
KuduIO said:
I keep getting errors immediately after booting, saying that the System UI crashed. I'm on CM11S, and I don't have any major tweaks or frameworks, it should be pretty much stock. I was able to obtain a debug log at boot time, which I attached to this post.
Could anyone please give me a hand with this? TIA!
Click to expand...
Click to collapse
Well what tweaks do you have?
A SystemUI doesn't randomly start to crash. You had to do something prior to the crashing that caused it to crash.
As what mark said, what tweaks did you do?
Possible fix to UI crashes at boot time
Hi, in the official OnePlus forum I found out that this is due to a bug of the WiFi icon when it is set up to "text" to show the signal intensity. I had the same issue and fixed it going back to "icon" only.
Hope this solves to you as well!
Related
My phone worked perfectly for a few days with ADP1.5H r3 on it, but now it refuses to boot, it seems to be looping forever. The blue android logo comes up, but the "shining" animation stops moving after usually 1-2 seconds, then the screen flashes back and the same thing repeats over and over again. I have already tried a wipe earlier, but now I'm having the same problem again. Any clues on what causes this or (better) how to fix this?
bsander said:
My phone worked perfectly for a few days with ADP1.5H r3 on it, but now it refuses to boot, it seems to be looping forever. The blue android logo comes up, but the "shining" animation stops moving after usually 1-2 seconds, then the screen flashes back and the same thing repeats over and over again. I have already tried a wipe earlier, but now I'm having the same problem again. Any clues on what causes this or (better) how to fix this?
Click to expand...
Click to collapse
Are you doing Apps to SD? It could be your card.
Did you move any caches?
Do you have any nandroid backups? (just fastboot flash if so)
Did you recently try to update to anything and fail?
Try to use the update.zip again. If that doesn't work then start over from scrap.
bsander said:
My phone worked perfectly for a few days with ADP1.5H r3 on it, but now it refuses to boot, it seems to be looping forever. The blue android logo comes up, but the "shining" animation stops moving after usually 1-2 seconds, then the screen flashes back and the same thing repeats over and over again. I have already tried a wipe earlier, but now I'm having the same problem again. Any clues on what causes this or (better) how to fix this?
Click to expand...
Click to collapse
Wipe worked for me. It was sticking on the Android flash screen, but worked after the wipe.
Yeah, a wipe fixes it. Later today I stumbled upon a thread which suggested the problem is the "Contact Owner" app that doesn't play nice. Can anyone confirm that?
In answer to binary: yeah I do apps on SD but I've been doing that since ADP1.1, so I doubt the card is the problem. Didn't move any caches. Yeah I have a nandroid backup, and all the updates I did went smoothly. I had the whole system working for about 2 days until this happened (probably, because this was the first time I rebooted since installing Contact Owner, though I can't really remember that 100%)
bsander said:
Yeah, a wipe fixes it. Later today I stumbled upon a thread which suggested the problem is the "Contact Owner" app that doesn't play nice. Can anyone confirm that?
Click to expand...
Click to collapse
Contact Owner caused my phone to go into a reboot loop, but that was on the 5.02H build. I haven't had the guts to try it on JF1.5 or 1.5Hr3. If you look through the market comments for Contact Owner you'll see quite a few complaints of the same issue.
Hi there,
And sorry for reviving this old thread. I am the developer of Contact Owner an I kinda need your help in debugging this issue. I got a small number of messages from users of custom builds a while ago (about a month or two) but thought it was an issue with those builds.
Now it came back to bite me in the ass, as it seems the HTC builds in various countries (Canada, Sweden, South Africa) have the same issue: the phone goes into a reboot loop. I've tried (and failed) to install a custom build on my dev phone (almost bricked it) so I'm going to ask nicely if someone is willing to debug the issue for me. Please, please, please!
All that's needed is to install and run Contact Owner and if the device goes into a reboot loop, simply attach it to USB, run 'adb logcat' and then post the output. To recover from the reboot loop, simply start in 'safe mode' (hold Menu down while booting) and then uninstall Contact Owner.
I suspect the problem lies in SQLite, because I've seen similar complaints from Klaxon users and that app also sets the alarm message (which then ends up in a SQLite db, I guess). The Alarm Clock app that comes with Android also does that but I imagine it's because the message set by Alarm Clock is always short and has no newlines. I also don't think the issue is in Dalvik code, because the device should not crash if managed code causes an error.
TIA,
Paranoid Android.
I've decided to make a new thread solely dedicated to new releases of test builds of the DSI-fix kernel module, so the feedback is not scattered throughout several different ROM threads.
I'd like to thank you all for the feedback I've got so far.
As the DSI related kernel panic/freeze is extremely rare on my phone, and any extensive logging added to DSI/DSS driver would change all the timings => the working conditions of the DSS subsystem, the debugging and any progress solely depends on your feedback - I need to see your kernel logs.
As I'm experiencing the common OMAP SD card issue pointed out by HinotoriBR here: http://forum.xda-developers.com/showpost.php?p=17033833&postcount=5563
I've added omap hsmmc set_data_timeout kernel function replacement to DSI-fix v2.6.
Therefore DSI-fix becomes DSI/MMC-fix now.
Current release for testing: v2.6 (2011/08/28) - http://www.multiupload.com/DZGUJFVCPJ
Put it to /system/lib/modules.
Please attach /data/dontpanic/apanic_console [in case of reboot] or dmesg [in case of temporary freeze] to your report.
This is a very goid idea. Congratulations for your great work by the way.
Just to clarify, in order for the module to work correctlly, do I have to wipe the caches?
Or just replacing the mudule and resetting permissions will suffice?
Sent from my Milestone using XDA App
It's a kernel space matter, android cache wipe has no influence on it. No wipe is needed.
Hey kabaldan,
I'm on CM7 RC13.1 (It's great! ) and dsi-fix 2.31.
I just had a really weird reboot when the phone was entering sleep mode. I had the browser open.
Then came to the site to post the kernel log (only o find out the browser doesn't upload files) and the phone frooze on me twice while I was typing the message.
Here are the logs. Hope it helps you.
View attachment dmesg.txt
View attachment apanic_console.zip
Thanks.
v2.31 testing is finished for now.
I'll post a new test version when it will be ready.
Guess I'm a bit behind here but wasn't this fixed with the workaround several builds back? Maby you are trying to make a better fix and if so, should the DSI kernel bug workaround setting be unchecked while trying this fix?
Paitor said:
Guess I'm a bit behind here but wasn't this fixed with the workaround several builds back? Maby you are trying to make a better fix and if so, should the DSI kernel bug workaround setting be unchecked while trying this fix?
Click to expand...
Click to collapse
dsi kernel workaround not a fix, dsi modul is the real fix, just not perfect for now.
the workaround maybe help to avoid dsi error but cause screen tearing. dsi modul not just help to avoid dsi errors but speed up the phone display performance.
you can use both at the same time is you want, but is pointless.
vadonka said:
dsi kernel workaround not a fix, dsi modul is the real fix, just not perfect for now.
the workaround maybe help to avoid dsi error but cause screen tearing. dsi modul not just help to avoid dsi errors but speed up the phone display performance.
you can use both at the same time is you want, but is pointless.
Click to expand...
Click to collapse
Right now I have to have it checked. Without it I get the freezes all the time.
I really hope you can get the silly dsi fixed. For now the workaround works perfectly!
Sent from my Milestone using Tapatalk
@People:
Don't forget to add the right permissions when testing new modules, otherwise you will still receive the infamous DSI message as the module will not load properly.
wisefreakz said:
@People:
Don't forget to add the right permissions when testing new modules, otherwise you will still receive the infamous DSI message as the module will not load properly.
Click to expand...
Click to collapse
Thanks for letting us know, btw what permissions should it be set as?
~PsyCl0ne
PsyCl0ne said:
Thanks for letting us know, btw what permissions should it be set as?
~PsyCl0ne
Click to expand...
Click to collapse
644
Or
User: read, write
Group: read
All: read
Sent from my Milestone using Tapatalk
I'm on RC13 (not this v2.31 dsi-fix) and I got a reboot. Here's the log.
I'll try v2.31.
so i started testing 2.31 worked nice till half an hour ago, had a freeze. restarted the pohne with "left shift + right alt + del". phone boots up zeam launcher isn't even ready -> freeze. restarted again 2 minutes after boot ->freeze.
so i thought, okay i need my phone for the next hours so tried to go as fast as i could to:
settings>cm settings>display: DSI Workarround
DON'T DO THAT!!!!
phone won't boot anymore!!
i restored a Nandroid and tested it again, it worked with 2.2
but with 2.31 you are screwed
New test version v2.32 uploaded.
http://www.multiupload.com/DVJ88FYTQS
Thank you kabaldan, I've been having loads of trouble lately.
In 2.31...I got freeze and the 'ghost' issue that other user told...
I noticied they keep wake while charging, but that option is off in settings>app>development>stay wake while charging, it's because dsifix?
I have random reboots with all DSI fixes with correct battery management, except 2.1, now I will test 2.32 module and if I experience problems I'll send logs.
Had no random reboots with latest fix.
BUT I did have a random slow up, where everything goes really slow and haptic feedback doesn't work. Reboots fixes.
Had it on every module
Sent from my Milestone using Tapatalk
mcdevtingz said:
Had no random reboots with latest fix.
BUT I did have a random slow up, where everything goes really slow and haptic feedback doesn't work. Reboots fixes.
Had it on every module
Sent from my Milestone using Tapatalk
Click to expand...
Click to collapse
this is happening sometimes without the dsifix module, i think its related to something else
btw i have no problem with the dsifix 2.2 version
Hello! I'm running KK 4.4, rooted and unlocked. I recently had installed a couple of mods, most notably this mod to give me a battery percentage number. Well I installed the back-to-stock files provided by those developers in anticipation of installing Xposed. But inbetween, I noticed that my notification drawer didn't have a complete gray bar across the top (see screenshot, and picture of what it should look like).
After installing Xposed and GravityBox for KK, I tried using the notification drawer color fill option to see if that would correct or override it, but that completely filled the drawer, hiding everything in it. I could still click buttons, but could not see them. So I reversed that, but still have the gap in the bar. Edit: Seems I had to choose "underlay" as an option for the color fill, so it's unrelated/not an issue as far as that goes.
It seems like a minor thing, but given how the color fill reacted in addition to now having this gap, I'm worried that there may be other issues I could run into. Does anyone have any ideas or suggestions on how I could fix this, hopefully without reinstalling the OS?
Edit: Attached another screenshot better illustrating what's happening.
I'm having the same issues running franco kernel. Any help would be appreciated. Dirty flash does nothing for me.
EDIT: I was able to solve this by flashing this battery percent mod, you might want to give it a try:
http://forum.xda-developers.com/showthread.php?t=2559270
chickenrancher said:
I'm having the same issues running franco kernel. Any help would be appreciated. Dirty flash does nothing for me.
EDIT: I was able to solve this by flashing this battery percent mod, you might want to give it a try:
http://forum.xda-developers.com/showthread.php?t=2559270
Click to expand...
Click to collapse
Thanks, but I just came back to say that I completely wiped the phone and put a stock ROM back on.
My notification bar is randomly poppinig up and freezing the phone. Also, time and date settings just come up randomly. You can turn off screen and back on and it unfreezes. Any ideas WTH is causing this? Stock 4.4 Maxx. Same issue with multiple launchers so I don't think that's it. Any help would be appreciated
swigginpig said:
My notification bar is randomly poppinig up and freezing the phone. Also, time and date settings just come up randomly. You can turn off screen and back on and it unfreezes. Any ideas WTH is causing this? Stock 4.4 Maxx. Same issue with multiple launchers so I don't think that's it. Any help would be appreciated
Click to expand...
Click to collapse
if you are rooted try installing systemui.apk from someone else or download it from my rom on original development or if you are not rooted, reinstall the firmware again via FXZ.
Hey guys. I'm having an odd problem. I'm not sure what the proper terminology would be to describe it but my screen randomly "flickers?" or "refreshes?" itself. It's pretty similar to the effect you get when you click on a link within an app and it does a Window Transition to either a website, opens a new app, etc. It is doing this without being triggered by any user interaction. I can be within an app or looking at my home screen (not touching the screen at all) and it will do this transition animation thing with the result being itself. Unfortunately, I am unable to recreate the scenario at will. It is completely random. Sometimes happening within minutes of itself and other times it will happen hours apart.
It started happening again as I'm typing. Since it looks a window animation, I went into Developer Option and changed "Window Animation Scale", "Transition Animation Scale", and "Animator Duration Scale" all to OFF. It is still doing it but now it just looks different when it does it. It's more like a flash now.
Have any of you experienced this before? If so, were you able to resolve the issue in any way? I apologize if my description isn't that great. If you need more info just let me know. Thanks a head of time for anyone who can offer even just a suggestion.
My specs are:
Verizon Droid Ultra (Retail)
Android Version 4.4
System Version 19.6.3
Rooted
Radiohead84 said:
Hey guys. I'm having an odd problem. I'm not sure what the proper terminology would be to describe it but my screen randomly "flickers?" or "refreshes?" itself. It's pretty similar to the effect you get when you click on a link within an app and it does a Window Transition to either a website, opens a new app, etc. It is doing this without being triggered by any user interaction. I can be within an app or looking at my home screen (not touching the screen at all) and it will do this transition animation thing with the result being itself. Unfortunately, I am unable to recreate the scenario at will. It is completely random. Sometimes happening within minutes of itself and other times it will happen hours apart.
It started happening again as I'm typing. Since it looks a window animation, I went into Developer Option and changed "Window Animation Scale", "Transition Animation Scale", and "Animator Duration Scale" all to OFF. It is still doing it but now it just looks different when it does it. It's more like a flash now.
Have any of you experienced this before? If so, were you able to resolve the issue in any way? I apologize if my description isn't that great. If you need more info just let me know. Thanks a head of time for anyone who can offer even just a suggestion.
My specs are:
Verizon Droid Ultra (Retail)
Android Version 4.4
System Version 19.6.3
Rooted
Click to expand...
Click to collapse
i think something its wrong in the system, this may sound too heavy for a solution but you should reflash your firmware.
Jaocagomez said:
i think something its wrong in the system, this may sound too heavy for a solution but you should reflash your firmware.
Click to expand...
Click to collapse
Thanks so much for the response! After a few days of pulling my hair out about this...Would you believe that after I froze "MotorolaOTA" in Titanium Backup (I was tired of getting asked to update to 4.4.4) that I haven't experienced this issue anymore. Not a single flash, flicker, etc. Does that make any bit of sense lol? I can't believe that would cause my device to do that. Of course, it could just be coincidence that it stopped after I froze the OTA reminder. I don't know though, it sure does make it seem like that was the problem.