Tried to switch from dalvik to ART but on reboot it doesn't seem to stick. I go back into dev options and it still says dalvik. I'm on the original soak test, which shouldn't matter, but I'm curious if anyway else switch to ART and got it to stick. Thanks.
I've heard that happens if you're using xposed
Sent from my XT1080 using Tapatalk
livinitwarrior said:
I've heard that happens if you're using xposed
Sent from my XT1080 using Tapatalk
Click to expand...
Click to collapse
I'll have to see if that works. Any idea if I can uninstall xposed switch to ART then reinstall xposed or do I have to choose to keep one or the other?
Should be able to. Don't mess with your modules, just install the framework in the app itself, reboot, and try it then.
Sent from my XT1080 using Tapatalk
Xposed doesn't work with ART (yet). The Xposed developer purposely has your runtime switch back to Dalvik upon reboot to keep you from going into a bootloop with ART.
tehcodeman said:
Xposed doesn't work with ART (yet). The Xposed developer purposely has your runtime switch back to Dalvik upon reboot to keep you from going into a bootloop with ART.
Click to expand...
Click to collapse
Okay, thanks.
I have this same problem. I uninstalled Xposed, but it still switches back to Dalvik. Is there another app that can automatically switch to Dalvik, or did Xposed leave something behind?
EDIT: Nevermind, figured it out. It does leave stuff behind, it came to me that I had to hit an INSTALL button to install the framework, so i had to reinstall Xposed and hit an Uninstall button to uninstall the framework.
After i've changed runtime to ART every start up of phone is accompanied by error message: Google Play services has stopped.
I've wiped Play data but it didn't help.
Any ideas how to solve this issue?
Droid Mini, 4.4.2, rooted
.: SID :. said:
After i've changed runtime to ART every start up of phone is accompanied by error message: Google Play services has stopped.
I've wiped Play data but it didn't help.
Any ideas how to solve this issue?
Droid Mini, 4.4.2, rooted
Click to expand...
Click to collapse
This is a known issue with google play services. There is an update in the works, and an APK is floating around that will resolve this, although the error only occurs on boot, and does not cause any negative effects beyond the single error message.
Teksu said:
This is a known issue with google play services. There is an update in the works, and an APK is floating around that will resolve this, although the error only occurs on boot, and does not cause any negative effects beyond the single error message.
Click to expand...
Click to collapse
I've seen already 2 or 3 updates for Google Services, but my is still the same. May be this error occurs when it can't be updated?
Related
I have been rebooting my Nexus 5 when using Xposed Framework modules and for every perfect reboot I get a bootloop. Is anyone else experiencing this? It's frustrating that my Stock Rooted with Xposed Framework setup would cause bootloops and every time a bootloop occurs it eats up a lot of battery and makes the phone uncomfortably warm.
do you have art selected?
I have the same setup as you.....xposed never sent my device into boot loop. As the poster above me stated, are you using art or dalvik? I believe xposed does not work with art. Also, could using a module within xposed that is not developed for 4.4+ cause such misbehavior?
Sent from my Nexus 5 using xda premium
I have had this problem.. I don't know how to fix it.. I just restore a backup and try it again.. Sometimes it works and sometimes it don't
Sent from my Nexus 5 using XDA Premium 4 mobile app
I use Xposed on all my devices, I've never had so much as a stutter from it, let alone a bootloop. You've got something else going on. As others pointed out, if you are using ART runtime, Xposed isn't compatible.
_MetalHead_ said:
I use Xposed on all my devices, I've never had so much as a stutter from it, let alone a bootloop. You've got something else going on. As others pointed out, if you are using ART runtime, Xposed isn't compatible.
Click to expand...
Click to collapse
Yeah it's not that, I don't have ART enabled and on top of that enabling ART while Xposed is installed automatically sends you back into the OS and cancels the request for ART as a part of Xposed Framework, so I couldn't have enabled it anyway.
grizzlywan said:
Yeah it's not that, I don't have ART enabled and on top of that enabling ART while Xposed is installed automatically sends you back into the OS and cancels the request for ART as a part of Xposed Framework, so I couldn't have enabled it anyway.
Click to expand...
Click to collapse
I wasn't inferring that ART was the only possible cause, just the most common. What modules are you trying to use?
_MetalHead_ said:
I wasn't inferring that ART was the only possible cause, just the most common. What modules are you trying to use?
Click to expand...
Click to collapse
GravityBox and Greenify. Nothing that should be causing this.
grizzlywan said:
GravityBox and Greenify. Nothing that should be causing this.
Click to expand...
Click to collapse
If you disable both mods do you still get boot loops? And are you using the version of GB that's meant for kitkat?
_MetalHead_ said:
If you disable both mods do you still get boot loops? And are you using the version of GB that's meant for kitkat?
Click to expand...
Click to collapse
Still getting boot loops with both mods disabled, even went as far as to uninstall Xposed Framework to see if it would happen. I rebooted 10 times and it boot looped 3 times out of those 10.
Yes, using GravityBox for KitKat.
Yesterday I rooted my phone and put on Xposed and gravity box. Since then I've been downloading various things and trying out different customisation options. The last thing I download was MotoXposed and I made my navigation bar completely transparent, when I tried to disable the effect my phone just came up with the message 'unfortunately the process com.android.systemui has stopped'. Now I can't use my phone and the message keeps coming up everytime I turn it on. How can I fix this? or get my phone working again?
Don't worry I've fixed my phone completely now.
how?
jamespat93 said:
Yesterday I rooted my phone and put on Xposed and gravity box. Since then I've been downloading various things and trying out different customisation options. The last thing I download was MotoXposed and I made my navigation bar completely transparent, when I tried to disable the effect my phone just came up with the message 'unfortunately the process com.android.systemui has stopped'. Now I can't use my phone and the message keeps coming up everytime I turn it on. How can I fix this? or get my phone working again?
Don't worry I've fixed my phone completely now.
Click to expand...
Click to collapse
Can you tell me how did you solve it w/o reseting your phone?
BlakeParker said:
Can you tell me how did you solve it w/o reseting your phone?
Click to expand...
Click to collapse
Boot into recovery and flash Xposed-Recovery-Framework located at /sdcard . This is assuming the problem was caused by an Xposed module in the first place. Not sure whether OP uses this
Sent from my XT1032 using XDA Premium 4 mobile app
thnx
thnxx got it!
BlakeParker said:
Can you tell me how did you solve it w/o reseting your phone?
Click to expand...
Click to collapse
All I had to do was reboot my phone and luckily (even though the message was still coming up) I could still use the touchscreen. This allowed me to go to the motoXposed module that caused the problems and undo the options I changed.
Unfortunately the process com android.systemui has stopped. Xposed Installer
Does anyone has any clue about this:
I have been having the same issue with my Galaxy S5.
I am using the rooted stock ROm with touchwhiz.
The issue started after I installed Xposed Installer with Wanam Xposed.
The "unfortunately the process com android.systemui has stopped" message does not come on until I received phone call while the phone is active. If I receive a call when the screen lock is on, the phone behaves normally.
The other issue I'm having with Xposed Installer are
1) a noticeable increase in lagging
2) apps takes close to 10 minutes to install
3) It takes a long time for the computer to see the phone after connecting them with USB....sometimes up to 15 minutes. thereafter it was not taking as long, but it was still being delayed.
I have flashed the phone three times with roughly the same observation after each flashing (i.e. issues cropping up only after installing Xposed Installer and some modules)
I'm going to try system tuner now...
Did you managed to fixed it? I have the same problem as well!
Sent from my GT-I9505 using XDA Free mobile app
edwardciasico said:
Did you managed to fixed it? I have the same problem as well!
Sent from my GT-I9505 using XDA Free mobile app
Click to expand...
Click to collapse
No I did not. I factory-reset the phone. Did not install xposed installer again and It's been working well since then. However, I'm still going to try it one last time...I'll keep you posted
I resolved this by booting into recovery (TWM in my case) and then manually deleting the offending .apk file from /data/app.
jimnu said:
I resolved this by booting into recovery (TWM in my case) and then manually deleting the offending .apk file from /data/app.
Click to expand...
Click to collapse
Which offending apk please?
ekitiboy said:
Which offending apk please?
Click to expand...
Click to collapse
In my case it was motoxposed.apk but YMMV.
sry for doublepost
To fix the systemui-crash u need to disable the (new):
"Heads up notification" on Wanam !!!
Help
I recently rooted my phone with TWRP using Odin. I did a few small things in customizing (ie: font, rotate screen) and now I get this error message.I've tried to boot in recovery and it just constantly flashes the Teamwin logo screen and i get no where. Could really use some help here, cannot use my phone at the moment
i have this issue too
I have this with Orbot. Simply restarted the phone and made a speed-run to uninstall it. Works to me.
So, the main question is: why this happen?
marc_miranda said:
Boot into recovery and flash Xposed-Recovery-Framework located at /sdcard . This is assuming the problem was caused by an Xposed module in the first place. Not sure whether OP uses this
Sent from my XT1032 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I'm facing the same problem i'm unable to use my phone, kindly explain in details how to flash xposed recovery.
the problem appeared after installing an xposed mod.
Hi everyone,
I got an issue with my Moto G. I was using ART runtime ever since I bought my Flacon and today by mistake I put off Developer Options. I turned on Dev Ops and the runtime was shown as Dalvik. After that I just cant change the runtime to ART. I get the reboot to change runtime from libvm.so to libart.so? popup but nothing happens after rebooting. Tried it about 10 times now.
Thank you!
EDIT: I should have googled first. As it turns out, I've got Xposed Framwork installed, hence, ART won't get enabled.
Sorry for the post.
Cheers!!
If you're using Xposed, it won't change.
rogeriorp said:
If you're using Xposed, it won't change.
Click to expand...
Click to collapse
I have same Problem. I had Xposed installed but uninstalled it. I still cant change runtime to ART even though xposed installer is not on my device anymore.
[Q] Please help! "unfortunately the process com.android.systemui has stopped"
I have a rooted nexus 5 running CM11. I kept getting this message before and I didn't know why so I posted here and someone told me to wipe my data so I did. That fixed the problem for about 2 weeks but it's back again. It happens so frequently now its very frustrating. It happens when I open an app, update an app or uninstall an app. Not every time but most frequently when updating. Why is this happening?! Please help and thanks in advance!
Just reflash your ROM or flash a different ROM and your problem should be fixed
Sent from my Nexus 5 using Tapatalk
Do you use Xposed or any theme mods? Probably something like that causing it.
As spinninbsod said, just dirty flash your ROM again or clean flash a new one.
CitizenLee said:
Do you use Xposed or any theme mods? Probably something like that causing it.
As spinninbsod said, just dirty flash your ROM again or clean flash a new one.
Click to expand...
Click to collapse
Ok I'll try reflashing. And yes I have xposed and around 10 mods.
lilfil3 said:
Ok I'll try reflashing. And yes I have xposed and around 10 mods.
Click to expand...
Click to collapse
Cool, just make sure none of the mods are trying to do the same thing, like change battery icon etc.
If you're reflashing ROM it also might be worth taking a fresh back up before reactivating Xposed, just to save reflashing if something ***** up again
CitizenLee said:
Cool, just make sure none of the mods are trying to do the same thing, like change battery icon etc.
If you're reflashing ROM it also might be worth taking a fresh back up before reactivating Xposed, just to save reflashing if something ***** up again
Click to expand...
Click to collapse
I think its XBLAST TOOLS that's giving me the problems. I don't get that error until I open the app.
lilfil3 said:
I think its XBLAST TOOLS that's giving me the problems. I don't get that error until I open the app.
Click to expand...
Click to collapse
Ok that's a good start. Can you remember what you were using it to do? There's probably a similar settings in XGEL or Gravity Box.
CitizenLee said:
Ok that's a good start. Can you remember what you were using it to do? There's probably a similar settings in XGEL or Gravity Box.
Click to expand...
Click to collapse
As soon as I open xblast I get the error. I just uninstalled it and I'm trying gravity box now to see if it was just xblast. And what do you mean what I was using?
lilfil3 said:
As soon as I open xblast I get the error. I just uninstalled it and I'm trying gravity box now to see if it was just xblast. And what do you mean what I was using?
Click to expand...
Click to collapse
Prior to your problems, were you using XBlast to do anything specific like changing statusbar or something like that?
CitizenLee said:
Prior to your problems, were you using XBlast to do anything specific like changing statusbar or something like that?
Click to expand...
Click to collapse
Yes. I had like everything enabled. I changed things in the status and notification bar and I also did stuff to my lock screen and a few other tweaks.
lilfil3 said:
Yes. I had like everything enabled. I changed things in the status and notification bar and I also did stuff to my lock screen and a few other tweaks.
Click to expand...
Click to collapse
You can change all that stuff in GravityBox and XGEL so might be best to just use those instead
Due to an update of an Xposed module, I had badly corrupted my systemui. The phone was totally unusable, and I could only press the OK button notifying the stopped event at startup.
Lucky me, I still had not updated to 4.4.3. Via Skipsoft Android Toolkit I updated to the last Android release, and my systemui got fixed. I did not choose to perform a complete wipe, so I actually maintained my previous apps. In relation to root, I did not loose it, but I had to reinstall SuperSU to get the non-official apps working again.
I hope this helps somebody else in my same condition, with no need to do a system wipe!
thank you. this helped me today.
woke up with the error. assuming its gravitybox and xblast causing an issue. will remove xblast.
i9o said:
Due to an update of an Xposed module, I had badly corrupted my systemui. The phone was totally unusable, and I could only press the OK button notifying the stopped event at startup.
Lucky me, I still had not updated to 4.4.3. Via Skipsoft Android Toolkit I updated to the last Android release, and my systemui got fixed. I did not choose to perform a complete wipe, so I actually maintained my previous apps. In relation to root, I did not loose it, but I had to reinstall SuperSU to get the non-official apps working again.
I hope this helps somebody else in my same condition, with no need to do a system wipe!
Click to expand...
Click to collapse
Xposed does not actually "touch" or change SystemUI in any way. Xposed puts a couple of "files" in system which allows intercepted commands to be changed, without changing the actual code.
When you updated the ROM via a toolkit (PLEASE don't use toolkits by the way) you would have overwritten these Xposed files.
The simplest fix is to just remove the Xposed files
Sent from my Nexus 5 using Tapatalk
I'm rooted, stock rom, stock recovery and my knox counter is 0x0.
I've enabled developer options and changed my runtime it to ART, it reboots and I go check it still says Dalvik, I don't know what I'm doing wrong... Any suggestions?
Sent from my SM-G900P using XDA Premium 4 mobile app
Ls1ssz28 said:
I'm rooted, stock rom, stock recovery and my knox counter is 0x0.
I've enabled developer options and changed my runtime it to ART, it reboots and I go check it still says Dalvik, I don't know what I'm doing wrong... Any suggestions?
Sent from my SM-G900P using XDA Premium 4 mobile app
Click to expand...
Click to collapse
are you on deodexed rom??? if you are ART won't work.
Nope, I'm running stock rom(OTA updates) right out of the box other than obtaining root
Sent from a Galaxy S5 Far Far Away
The only thing I can think of is me debloating? I'm stumped....
Sent from a Galaxy S5 Far Far Away
Ls1ssz28 said:
The only thing I can think of is me debloating? I'm stumped....
Sent from a Galaxy S5 Far Far Away
Click to expand...
Click to collapse
This doesn't quite answer your question but should read through this thread if you have not: http://forum.xda-developers.com/showthread.php?t=2713879
Seems others are having the same issue as you. Since ART is still experimental on the S5 it causes screen wake up issues, boot issues, some apps to not work, and Samsung has said to use with caution because TW framework is not fully compatible yet.
Do you all think if I were to backup everything and : 1)factory reset 2)switch to art and then 3)root
Would that work?
Sent from a Galaxy S5 Far Far Away
I'm having the same issue.
Sent from my SM-G900P using Tapatalk
Problem solved.. Here is what I did for future reference
1)Odined back to stock, then took it the otas to get to stock uprooted NE5
2)Switched to ART, no issue rebooted and was running art
3)Titanium backup was not working for me without being suuuper laggy, so I started to manually install all of my apps
4)Rooted my phone using towel
5)Realized that Xposed forces dalvik, and once the framework was installed it would revert to dalvik... Uninstalled framework and removed xposed
5)turned ART back on and have had no issue.... It definitely was due to xposed because that is the only app that I Uninstalled and have had no issues since
Sent from a Galaxy S5 Far Far Away
Ls1ssz28 said:
Problem solved.. Here is what I did for future reference
1)Odined back to stock, then took it the otas to get to stock uprooted NE5
2)Switched to ART, no issue rebooted and was running art
3)Titanium backup was not working for me without being suuuper laggy, so I started to manually install all of my apps
4)Rooted my phone using towel
5)Realized that Xposed forces dalvik, and once the framework was installed it would revert to dalvik... Uninstalled framework and removed xposed
5)turned ART back on and have had no issue.... It definitely was due to xposed because that is the only app that I Uninstalled and have had no issues since
Sent from a Galaxy S5 Far Far Away
Click to expand...
Click to collapse
I don't have Xposed installed and still can't turn ART on.
Y.G. said:
I don't have Xposed installed and still can't turn ART on.
Click to expand...
Click to collapse
??????
Y.G. said:
I don't have Xposed installed and still can't turn ART on.
Click to expand...
Click to collapse
I don't have Xposed installed either, and still can't turn ART on. When the reboot finishes and I go to the Configuration, it says that DALVIK still on. Any solution?
Igu1nh0 said:
I don't have Xposed installed either, and still can't turn ART on. When the reboot finishes and I go to the Configuration, it says that DALVIK still on. Any solution?
Click to expand...
Click to collapse
I think, for whatever reason, ART is disabled in TouchWiz.