Hi all,
I'm curious to try what does or does not work under ART runtime, but when i try to switch my JFLTEXX to ART, it does not stick.
It asks if i'm sure, reboots back into Dalvik mode (normal boot-speed).
I'm on latest OMNI nightly, How do I make ART stick?
Are you using xposed framework?
You can't use ART if you are.
Yes I am. But I think I can live without it. Will give it a go without Xposed. :good:
Edit: Works like a charm. Had to switch back to Nova bc TSF Shell died, thats all.
Related
Hello All, I did some searching for this, but all I can come up with is quite the opposite of my issue. My issue is my phone got stuck in boot loop. Having been on this forum a few times the first thing I did was clear the cache and dalvik and it booted right up. But unfortunately anytime I reboot, it gets stuck on the bootanimation and no matter how many times I reboot, it absolutely will not work unless I clear the dalvik, every time.
Any thoughts on what may be going on, I would really love suggestions that I might can try to see if it's a permanent fix.
Regardless, thanks for your time and effort :fingers-crossed:
T-Mobile C6606
Updated To
[LB] eXistenZ v6.0.0 - Ultra Edition
10.4.1.B.0.101
Kinda hard to help with so little information.
Do you by any chance have xposed framework installed?
If so I know that if you restore app + data from titanium backup for xposed modules it can cause your phone to stick on the boot animation. Clearing dalvik cache would temporarily fix it.
If that's your case then you can go into setting / apps and clear data on all the modules.
If that's not your issue then you may ave flashed something incompatible with your framework. Without much information I can only suggest that you re-flash your rom or firmware.
Trucifix said:
Hello All, I did some searching for this, but all I can come up with is quite the opposite of my issue. My issue is my phone got stuck in boot loop. Having been on this forum a few times the first thing I did was clear the cache and dalvik and it booted right up. But :
Click to expand...
Click to collapse
Do you use gravity box?
If yes,then disable it in xposed modules and reboot
Gravity box has been causing these kind of bootloops for most of us
I had this issue sometimes when i was using advanced power menu with my previous stock rom. When rebooting from advanced power menu i always had bootloop, but when restarting from the xposed menu for example, no bootloop.
Thank you all very much, and I use all three of those, xposed, gravity box, and advanced power menu. I will try all three of those suggestions today and report back which one may have did it.
Most likely gravitybox. There's been a lot of talk about it. Some don't have it at all, some got rid of it in the newer version and some like me has it with all 'newer than 2.8.5' versions. I usually can get it by trying to boot some times but it happens randomly.
Incredibly annoying and there's some things in newer gravitybox versions that I'd really like
SOLVED - Phone won't boot unless Dalvik is cleared
Kocayine said:
Most likely gravitybox. There's been a lot of talk about it. Some don't have it at all, some got rid of it in the newer version and some like me has it with all 'newer than 2.8.5' versions. I usually can get it by trying to boot some times but it happens randomly.
Incredibly annoying and there's some things in newer gravitybox versions that I'd really like
Click to expand...
Click to collapse
It quit doing that after I cleared app data and cache for gravity box. Gravity Box is definitely a factor :silly: If it comes back again I will go through more appropriate channels now that I know the culprit.
Thanks every one !!!
I try to switch over... It reboots... Still on dalvik.
Any suggestions?
Sent from my XT1053 using Tapatalk
My guess....you need to get rid of xposed.
Or decide what's more important to you.
Xposed will not run on art, and kicks you back to dalvik.
KJ said:
My guess....you need to get rid of xposed.
Or decide what's more important to you.
Xposed will not run on art, and kicks you back to dalvik.
Click to expand...
Click to collapse
^ What he said.
And you can THANK the Xposed devs, because if they hadn't implemented the 'switch-back' feature, you would be in a bootloop now, and it would require SBFing back to stock.
Good Luck
Hello. I have a rooted, with CWM and Unlocked BL Moto G 2014, and ever since I got it I've been trying to switch to ART mode and it just won't turn on. It stays on dalvik all the time. Any tips?
Me too. What´s the issue that blocks the change?
ART
If u have xposed modules installed ART won't run...
Same problem here. Indeed I've installed xposed.
Is ART much better than dalvik ?
Trublood_ said:
Hello. I have a rooted, with CWM and Unlocked BL Moto G 2014, and ever since I got it I've been trying to switch to ART mode and it just won't turn on. It stays on dalvik all the time. Any tips?
Click to expand...
Click to collapse
Are you using the Xposed framework?
Yes, I AM using xposed but even when I didn't have it I couldn't switch to ART
Is it possible? I can't seem to find anything saying it is.
You can't even use xposed on this phone ..xposed doesn't work in art yet and this phone doesn't have dalvik.
that's probably why op asked for "hiding root without XPosed"
nexus6R3plicant said:
You can't even use xposed on this phone ..xposed doesn't work in art yet and this phone doesn't have dalvik.
Click to expand...
Click to collapse
Not only this phone, starting from Lollipop. Dalvik is removed, Xposed dev needs to update Xposed for ART.
I tried lolipop version, Im on 5.0.1
Is there any way to make it working?
I only use it on spotify.
Or is there any other good app/equalizer?
Thks
Fustigador said:
I tried lolipop version, Im on 5.0.1
Is there any way to make it working?
I only use it on spotify.
Or is there any other good app/equalizer?
Thks
Click to expand...
Click to collapse
I think this belongs in here: http://forum.xda-developers.com/shield-tablet/help
Well, is there a problem with flashing the .zip or does the app dont work properly?
I used this (first two .zips) and this.
If that is still not working you should try that too.
The app works ok, but the sound is the same, its like doesn't have any effect.
I'll try lá ter.
Its not only Q&A but a thread with the app funcional to ower device.
Fustigador said:
The app works ok, but the sound is the same, its like doesn't have any effect.
I'll try lá ter.
Its not only Q&A but a thread with the app functional to our device.
Click to expand...
Click to collapse
I got V4A working by using the zip/apk standard download, then installing the apk as usual (making it a User app).
Install the V4A driver.
Make sure your Compatibility Mode is set to Normal.
Reboot.
Install SE Linux Mode Changer app from the Play Store (or edit your build.prop) to switch your SE mode to Permissive. (L's default is Enforcing.)
Open V4A up and tick the Enable box to use V4A on the ”phone speaker” tab.
Play some music! Check to see if it is working by unticking the phone speaker Enable box.
*If* it still doesn't work... Try the following one at a time:
Set Compatibility Mode to Compatible.
Tick the Force Enforce V4A under the phone speaker tab.
Install as a System app instead of a User app.
Try a different music player app. I'm using Shuttle+ and it works perfectly. I've heard some player apps don't work as well as others though.
Hoping this helps you a bit. It seems to be one of those trial & error things to get Viper set up on Lollipop. I even have to do things a tad differently to get it working on my Nexus 4 & 5.
?
Ty worked Great. I didn't Changed to permissive.
Maybe some moderator could move this thread to Q&A?
?
MiePx3 said:
I think this belongs in here: http://forum.xda-developers.com/shield-tablet/help
Well, is there a problem with flashing the .zip or does the app dont work properly?
I used this (first two .zips) and this.
If that is still not working you should try that too.
Click to expand...
Click to collapse
Hello, I flashed all three zip files from the first link but upon rebooting, v4a continually force closes. Don't have any other sound mods.
I'm on 5.0.1. Any help would be greatly appreciated.
Thanks.
Sent from my 1+1
Mojar7070 said:
Hello, I flashed all three zip files from the first link but upon rebooting, v4a continually force closes. Don't have any other sound mods.
I'm on 5.0.1. Any help would be greatly appreciated.
Thanks.
Sent from my 1+1
Click to expand...
Click to collapse
The last .zip from the first link is outdated. Try to delete it and use this one.
Make sure you use the right .apk for 5.0 (should be A4.x).
MiePx3 said:
The last .zip from the first link is outdated. Try to delete it and use this one.
Make sure you use the right .apk for 5.0 (should be A4.x).
Click to expand...
Click to collapse
Hello, thanks for the response. However, v4a kept force closing constantly and continually so I'm not able to navigate within the device. My biggest idiotic move was I didn't make a nandroid....assuming all will be good.
Anyways, I'm now on a hunt to flash stock rooted rom. If you have any info on that would greatly appreciate it.
Thanks.
Sent from my 1+1
OK all the file flashing is not useful at all if ur running stock. The only reason they exist is for DIFFERENT DEVICES, meaning ur flashing crap that is meant for something else and can have bad consequences. The flushable zips all have scripts that add lib files or script to build.prop. The flushable zips also seem to mess with any app that handles kernel configuration. ie if u like to change clock speeds, nothing would stick on this tablet after I flashed those v4a zips. Would always revert to stock.
For v4a to work. FIRSTLY run selinux mode changer. The person that said they got this to work without it is wrong. Dead wrong. The driver will NOT I STILL OR INITIALIZE UNLESS SELINUX IS PERMISSIVE. This must be done to allow android to install the driver to the kernel. Period. Run selinux mode changer, set to permissive, reboot. Check selinux, sometimes u will have to do it 3-4 times for it to stick. Then install the newest v4a from their site I think it's @ 2.3.4.0 the older versions needed the flashable zips for some files the Nexus lollipop update didn't have. They fixed this. Now just install the app normally, then open it and install the driver. Reboot. If u r on cyanogen unlock the developer options and turn off or unchecked "use nuplayer" finally, if u use gone mad music player go to options, audio, tell it to use external dsp.
Profit!
I've never needed to use compatibility mode or anything else. Works like a champ.