Hello fellow N4 users,
I noticed few threads about ART actually running quite well on our device and I thought I'd give it a go aswell. However when I go into Dev settings and select ART instead of Dalvik, my phone just simply reboots and nothing is changed, the option is set to Dalvik again. I'm rooted on stock ROM. Any ideas?
Thanks in advance.
The same happen to my phone on rooted rom. On my S5 art works fine, I don't know why it won't enable on N4.
mcreego said:
The same happen to my phone on rooted rom. On my S5 art works fine, I don't know why it won't enable on N4.
Click to expand...
Click to collapse
So there's completely nothing to do atm except waiting for 5.0?
I've notice this used to happen when I had xposed framework installed (xposed is not compatible with ART).
Do you have Xposed installed?
I feel like a real noob... You're right art is not compatible with Xposed... Thanks for pointing it out.
Related
Can anyone tell me which stock KitKat rom:
1. has NO CarrierIQ (fully disabled/removed, not just partially disabled/removed).
2. has fully working bluetooth (by "fully working" I mean doesn't randomly disconnect from my Pebble watch like CM11 snapshots do).
3. is flashable with TWRP recovery
4. keeps root
5. works with the AT&T G2 (D800)
I've searched and searched, but every rom I found is missing one of these things. I would love to stay with CM11 stables, but I'm tired of the constant bluetooth disconnects. It works great with my bluetooth headphones, but not my Pebble.
Thanks :good::victory:
This one has all those things http://forum.xda-developers.com/showthread.php?t=2680789 but you lose recovery after.
Art Vanderlay said:
This one has all those things http://forum.xda-developers.com/showthread.php?t=2680789 but you lose recovery after.
Click to expand...
Click to collapse
Thanks, but I forgot to say it needs to be compatible with the D800.
Is anyone else able to enable ART on their S5? I have the latest build, rooted, xposed installed, and some minor tweaks. Every time I go into developer options and enable ART, it prompts the reboot. My phone does a somewhat normal reboot and it stays on Dalvik. I know I tried ART on the original software build back is April or May. It worked at that time but it didn't play nice with a couple of my apps. Is anyone currently using ART on a rooted phone?
Xposed is not compatible with ART.
I was suspecting that. Thanks. I wouldn't give up Xposed for anything. I hope they can eventually make it work with Android L.
Supposedly there is already something that will work, but it's not being released until L.
Sent from my iPad using Tapatalk HD
The dev posted that he isn't seriously working on it until AFTER 'L' it's finalized. Google keeps changing too much in ART, and it is a waste of time to keep chasing it. He had a proof of concept working before he stopped tinkering though.
So it could be a while after L is released before xposed supports ART. But it definitely will eventually. Although even then it is probable that it will only support ART in L or newer due to changes in ART from 4.4 to 5.x.
when i change dalvik to art the note 4 stil to hot , really very hot and some apps included S healht dont work, i have no root.
someone know why?
thanks in advanved
I've heard it only runs hot for a while, but haven't tried it yet.
mrcarlos said:
when i change dalvik to art the note 4 stil to hot , really very hot and some apps included S healht dont work, i have no root.
someone know why?
thanks in advanved
Click to expand...
Click to collapse
why change, you gain nothing but loose xposed, the note has qualcomm optimized dalvik and bionic, this is faster than art
Hi thanks for the help anyway i don't have root, because i prefer wait for official lollipop ota update.
Sent from my SM-N910F using Tapatalk
Hey guys .. Really didnt wanted to open a new thread but i was reading through many threads in the past days and didnt find a solution. Ive installed viper4android as system app and changed selinux to permissive. But it just doesnt work
Is there anybody facing the same or is there anything i missed?
Thanks in advance
This is what driver status says...
Btw im on lp 30b with stock kernel
I'm getting the same problem on my ls980 (Sprint var.)
I'm running a lollipop ROM, (Resurrection Remix)
This is in lollipop 5.1, however.
Very sad though... I LOVE viper. Probably one of my biggest reasons for root, besides custom ROMs and Xposed.
Hopefully this will be looked into.
---EDIT---
My driver status is listed as abnormal, and not enabled.
Probably means I'm even worse off than you
Collserra said:
I'm getting the same problem on my ls980 (Sprint var.)
I'm running a lollipop ROM, (Resurrection Remix)
This is in lollipop 5.1, however.
Very sad though... I LOVE viper. Probably one of my biggest reasons for root, besides custom ROMs and Xposed.
Hopefully this will be looked into.
---EDIT---
My driver status is listed as abnormal, and not enabled.
Probably means I'm even worse off than you [emoji14]
Click to expand...
Click to collapse
I'm on D802 lollipop and viper4android installed. It worked very nicely for few days. But suddenly stopped working. I've tried reinstalling many times and even added the build.prop settings mentioned in one thread.
But now it just doesn't work. The status says abnormal. And whenever I open the app, music stops playing. Hope someone can help us.
Alleks1802 said:
Hey guys .. Really didnt wanted to open a new thread but i was reading through many threads in the past days and didnt find a solution. Ive installed viper4android as system app and changed selinux to permissive. But it just doesnt work
Is there anybody facing the same or is there anything i missed?
Thanks in advance
Click to expand...
Click to collapse
Collserra said:
I'm getting the same problem on my ls980 (Sprint var.)
I'm running a lollipop ROM, (Resurrection Remix)
This is in lollipop 5.1, however.
Very sad though... I LOVE viper. Probably one of my biggest reasons for root, besides custom ROMs and Xposed.
Hopefully this will be looked into.
---EDIT---
My driver status is listed as abnormal, and not enabled.
Probably means I'm even worse off than you
Click to expand...
Click to collapse
droidfan88 said:
I'm on D802 lollipop and viper4android installed. It worked very nicely for few days. But suddenly stopped working. I've tried reinstalling many times and even added the build.prop settings mentioned in one thread.
But now it just doesn't work. The status says abnormal. And whenever I open the app, music stops playing. Hope someone can help us.
Click to expand...
Click to collapse
Check my guide for poweramp and v4a, it might just be the thing to fix it.
Thanks man. It turned out that somehow my selinux had become enforcing. Changed it to permissive and things work as expected.
Check ,,Use ,,NuPlayer'' '' in developer setting.
And install SELinux Enabler script via recovery : http://blastagator.ddns.net/dorimanx.php
Hi,
I recently rooted my S5 successfully and then got rid of touchwiz and installed Cyanogenmod 13. But then I realized that the root was gone from my phone. So I rooted again and now Cyanogenmod won't boot. (Stuck on Cyanogenmod booting animation.)
I have an S5 g900I (Oceania edition).
I'm guessing the mod went away because I wiped the system through recovery before installing CM but why can't I root again? If anyones had the problem previously which is the best version to go with? I might try CM12.1 now just to be sure. But any ideas?
Thank you
Axle0 said:
Hi,
I recently rooted my S5 successfully and then got rid of touchwiz and installed Cyanogenmod 13. But then I realized that the root was gone from my phone. So I rooted again and now Cyanogenmod won't boot. (Stuck on Cyanogenmod booting animation.)
I have an S5 g900I (Oceania edition).
I'm guessing the mod went away because I wiped the system through recovery before installing CM but why can't I root again? If anyones had the problem previously which is the best version to go with? I might try CM12.1 now just to be sure. But any ideas?
Thank you
Click to expand...
Click to collapse
Flash the latest update supersu.zip and root your phone. I think now you can use supersu2.46.zip on aosp 6.0.1. I've done it and works for me. If not then use the latest systemless root by chainfire. The one that works for me is 2.62. Try 2.46 first. Thanks @Chainfire for all of your hard work and making it easy to root our phones. Good luck
CM13 has root built into the ROM.
Go to settings -- > about device, tap on "Build number" enough times until the Developer options appear, and enable root from within the developer menu.
jlbuck6212 said:
Flash the latest update supersu.zip and root your phone. I think now you can use supersu2.46.zip on aosp 6.0.1. I've done it and works for me. If not then use the latest systemless root by chainfire. The one that works for me is 2.62. Try 2.46 first. Thanks @Chainfire for all of your hard work and making it easy to root our phones. Good luck
Click to expand...
Click to collapse
I didn't try that since after wiping everything again I realized by installing CM13 your phones changes to g900f which is the international version and by installing the root for that version all works good. Thank you for your quick response
tangcla said:
CM13 has root built into the ROM.
Go to settings -- > about device, tap on "Build number" enough times until the Developer options appear, and enable root from within the developer menu.
Click to expand...
Click to collapse
That's actual hell cool but as mentioned above fixed it some other way.
The only other problem I'm having with CM13 which is really annoying is that it seems like its not as optimized for my phone. It overheats and drains the battery way too quickly. Any ideas for that? Thanks
Axle0 said:
The only other problem I'm having with CM13 which is really annoying is that it seems like its not as optimized for my phone. It overheats and drains the battery way too quickly. Any ideas for that? Thanks
Click to expand...
Click to collapse
Yes, it's NFC that's causing the issue. Use a root browser and delete the folder /system/app/NfcNci - try that.
tangcla said:
Yes, it's NFC that's causing the issue. Use a root browser and delete the folder /system/app/NfcNci - try that.
Click to expand...
Click to collapse
Fair enough. I don't use NFC anyways so I'll give that a shot