I'm running 4.3 MI9 stock rooted. I have installed xposed and have several modules activated(see pic).
A lot of times during the day I'll be going to the home screen and touchwiz and screen will back out and pop up notifying that touchwiz has stopped. It will also always stop if I press the home button multiple times in quick succession. What am I doing wrong? And how can I fix?
Sent from my SM-N900V using XDA Premium 4 mobile app
I've had it happen on (rooted, lightly modded) MJ7 when holding the home button down. It first started happening after I manually froze (chmod 000) a fair number of preinstalled bloatware .apk s, but I don't really know if it is related to that. (Risk of a "post facto fallacy" error)
If you can force it to happen somewhat deterministically, it might be worthwhile to
- connect N3 to PC, verify adb connectivity (e.g. "adb shell ls")
- clear the log ("adb logcat -c")
- force the TouchWiz home crash error
- capture logcat output ("adb logcat -d > logcatout.txt")
The N3's logcat output seems incredibly busy, even when the phone is doing very little. (So that's why the capture of it to a file - the good stuff will roll off your screen otherwise.) If you can minimize motion and/or screen touches when attempting to force the crash there will be less chaff in the logcat output file.
HTH
I'm not that advanced I don't think I can do that. I'll just deal with it. And yes I did in isn't all Samsung apps, so I must've touched one that was not meant to be touched.
Sent from my SM-N900V using XDA Premium 4 mobile app
Related
Hello All,
I've been lurking in this forum for a year or so now... However, I wish to update the community of an issue with the Asus Transformer Pad TF300T and the OTA Jellybean update for the WW builds which was just pushed to us an hour or so ago.
If you are rooted but not unlocked, most probably you are running SuperSU and Voodoo OTA Rootkeeper. Normally, there shouldn't be a problem with the Jellybean OTA update. However, if you are like me and are also running EZOverclock, after the Jellybean update, the moment you restore root using Voodoo OTA Rootkeeper and reboot, the Transformer will get stuck in an endless bootloop, starting up normally then rebooting again in within 1 minute after the Android lock-screen/homescreen comes up.
Apparently, there is a serious incompatibility between EZOverclock which crashes the OS and forces it to reboot.
To all WW Build TF300T users who received the OTA update but haven't installed it yet, please uninstall EZOverclock before installing the update.
For those like me who found out the problem too late, you have to be a bit persistent and lucky and try to disable EZOverclock before it starts...
What I did was the following:
- remove any installed microSD cards
- force the unit to reboot by holding down the power button or just catch the bootup sequence at the moment the lockscreen/homescreen comes up and it can accept input
- quickly tap the menu button at the upper right-hand corner of the screen and quickly swipe the pages until you get to the page where your SuperSU app is
- tap the SuperSU app and tap the EZOverclock app and tap the "forget" button
This should disable the EZOverclock app and the system should stabilize after it crashes/reboots automatically for the last time. You can then uninstall EZOverclock at your leisure.
You may have to attempt to do this several times to get the timing right because you have to get all of this done in the short window of time when the system starts up but before EZOverclock loads and crashes the system.
I spent over two hours trying to find out what went wrong with my OTA update and trying several other things before finally discovering the problem. I spent another half an hour trying to get the timing right to be able to disable EZOverclock...
I hope this would help other rooted WW build users to avoid problems when updating to Jellybean.
Best Regards to All
^_^
The way I got rid of it was quickly unlock go into app drawer and drag uninstall ezoverclock, it should be in first page since it starts with e.
Sent from my ASUS Transformer Pad TF300T using Tapatalk 2
jgaf said:
The way I got rid of it was quickly unlock go into app drawer and drag uninstall ezoverclock, it should be in first page since it starts with e.
Click to expand...
Click to collapse
I didn't know that you could drag-uninstall an application... Well, you learn something new everyday... :laugh:
How did you no ezoverclock was causing the bootloops?
trevor7428 said:
How did you no ezoverclock was causing the bootloops?
Click to expand...
Click to collapse
Actually I didn't at first. After the initial panic attack had passed, I spent the next two hours searching the Internet for a situation similar to mine. I read somewhere that bootloops are generally caused either by bad ROMs or misbehaving software. I had several things loaded that startup on boot:
- EZOverclock
- DU Meter
- Lookout
- Micro CPU meter
Except for EZOverclock, all the other have some sort of notification that they have loaded:
- DU Meter --> notification panel
- Lookout --> notification panel
- Micro CPU meter --> 4px high by 200px wide moving lines at the upper right hand corner of the screen
The system works fine until the Lookout icon appears on the notification panel, then the system freezes and reboots. Neither the Micro CPU meter and the DU Meter loads before the system reboots, so I started with those two, quickly loading their apps and stopping them from loading into the notification tray. When I tried loading the EZOverclock app to disable it, the system froze with the app screen halfway open. I tried doing it again when the system rebooted. Same result. AHA! I think I have found the culprit. Searching the Internet yielded reports of users having trouble running EZOverclock on Transformer Primes running custom ROMs based on Jellybean. That's why I tried to find a way to unload it...
Sent from my ASUS Transformer Pad TF300T using XDA Premium HD app
something that might help also: To trigger safe mode in Android 4.1, you long-hold the power button to bring up the phone options menu, and then long-hold on the “power off” option to be presented with the opportunity to boot into safe mode.
source : http://pocketnow.com/2012/07/11/android-safe-mode-gives-you-power-over-misbehaving-apps/
note, this safe mode can often also be triggered on the device bootup, by using different combinations of key presses/holding keys. not sure what it is of tf300 though..
lawrence750 said:
something that might help also: To trigger safe mode in Android 4.1, you long-hold the power button to bring up the phone options menu, and then long-hold on the “power off” option to be presented with the opportunity to boot into safe mode.
Click to expand...
Click to collapse
That information could have saved me needless aggravation yesterday... ^_^
Grifter357 said:
That information could have saved me needless aggravation yesterday... ^_^
Click to expand...
Click to collapse
heh.. theres always a way
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
This makes my mind up, I won't be upgrading.
So i was annoyed by mymagazine being only 1 swipe away and being accessed by the double tapping home button. So i turned off the home button setting and then then turned off my magazine. it wasnt an issue but i ended up just rooting my phone and then uninstalled all the bloat apps....including mymagazine.
Now when ever i double tap the home button my TouchWiz crashes. however, if i swipe up, it just goes to the play store and says item cannot be found.
i really hope that we get some way to swap out the my magazine for google now or something useful. anyone know a work around that doesnt involve a different launcher??
SAME HERE
ThePwnageKing said:
So i was annoyed by mymagazine being only 1 swipe away and being accessed by the double tapping home button. So i turned off the home button setting and then then turned off my magazine. it wasnt an issue but i ended up just rooting my phone and then uninstalled all the bloat apps....including mymagazine.
Now when ever i double tap the home button my TouchWiz crashes. however, if i swipe up, it just goes to the play store and says item cannot be found.
i really hope that we get some way to swap out the my magazine for google now or something useful. anyone know a work around that doesnt involve a different launcher??
Click to expand...
Click to collapse
I am having the same issue - hitting home button when on my homescreen causes TouchWiz to crash. Did you ever figure anything out?
If you uninstall my magazine or freeze it, tw will fc. It's tied I to the framework of touchwiz, either use a different launcher or reinstall/unfreeze my magazine
Sent from my SM-N9005 using XDA Premium 4 mobile app
This might be a dumb question but If i use a different launcher other than TouchWiz will the s pen functions still work? Also, playstore doesn't have MyMagazine. Do i just need to install the apk if i want to keep using touchwiz? (very new to root)
thanks
Yup will still work - you'll probably find the mymagazine.apk around somewhere
Sent from my SM-N9005 using XDA Premium 4 mobile app
still stuck :\
When i try to install MagazineHome.apk i keep getting "Application not installed".
If i try to install it with Rom Toolbox APK installer it just says installing then goes away as if nothing happened.
I was reading on a few other threads but am quite confused. What is this term Push(ed) being thrown around.
http://forum.xda-developers.com/showthread.php?t=2487346
http://forum.xda-developers.com/showthread.php?t=2446489
You can push/side load via adb or cut n paste it into system apps and set correct permissions - not done it since I had my HTC one so not sure if it is different on the Note, just grab Nova launcher can customise as much as you want and have no fc and no mymagazine
Sent from my SM-N9005 using XDA Premium 4 mobile app
I noticed that when I am inside the app drawer, when I press the menu button, a two second delay is there before the actual menu come out. I compared this to my S3 as well as to my Note 8 and this delay does not exist.
The menu button outside the app drawer, i.e. the home screen or other quick launch pages is very quick (no delay between pressing the menu button and the actual menu coming out).
I am rooted, JB 4.3, running Stock ROM Rogers MJ4, SM-N900W8 with TouchWiz launcher.
Any idea if this is a settings thing?
I was manually debloating after root and I am concerned that I might have disabled something that would reflect the delay in pulling out the menu inside the app drawer.
Any help would be appreciated.
soal001 said:
I noticed that when I am inside the app drawer, when I press the menu button, a two second delay is there before the actual menu come out. I compared this to my S3 as well as to my Note 8 and this delay does not exist.
The menu button outside the app drawer, i.e. the home screen or other quick launch pages is very quick (about .5 second delay between pressing and the actual menu coming out).
I am rooted, JB 4.3, running Stock ROM Rogers MJ4, SM-N900W8 with TouchWiz launcher.
Any idea if this is a settings thing?
I was manually debloating after root and I am concerned that I might have disabled something tat would reflect the delay in pulling out the menu inside the app drawer.
Any help would be appreciated.
Click to expand...
Click to collapse
go into svoice settings and disable open with menu button...see if that helps
I have done that already before my post. It did not affect the problem.
Sent from my SM-N900W8 using xda premium
Since I rooted and installed TWRP and flashed the custom kernel that is required to continue using the stock ROM after installing TWRP, anytime I hold certain things (items on home screen in Nova), swipe up from the Navbar to bring up the ring, or tap the little gear in the sound popup (to show all the sound options instead of just ringer), my phone freezes completely for 2-4 seconds. It's especially bad with Swiftkey, which freezes after each button press. I don't actually use Swiftkey, I just wanted to see if it had changed since I last used it and it seems to have gotten worse. Holding or tapping anything in the AOSP and LG keyboards is fine, though. Bringing up recents by holding the home button works as usual without freezing.
Anyone know why this is happening or know of a fix?
Sent from my LG-D800 using xda app-developers app
EDIT: Only AOSP keyboard works, LG freezes after every press, just like Swiftkey.
EDIT: Discovered that disabling the "LG System Server 1.0" app was the issue.
I have the same problem on the D802
ChilliDroid said:
I have the same problem on the D802
Click to expand...
Click to collapse
Pretty sure I found the problem. You probably, likely myself, just froze/disabled all the LG and AT&T bloatware. That was what did it. Unfreeze/enable "LG System Server 1.0" and everything will work normally.
Sent from my LG-D800 using xda app-developers app
Curious on some improvements I can make. When I press the square it takes several seconds for the app picker to come up sometimes. Even sometimes when I press the home button it will hang.
I'm rooted and I've already done a few things like
LSpeed and Apps2SD.
Thanks!
Sent from my KFSUWI using Tapatalk