Hey everyone,
I've been using my Nexus 5 since November and I have to say I love it. I have the phone rooted, running stock 4.4.2.
Here's my problem: when I try to switch to ART runtime in developer settings, I get the regular prompt and my phone reboots. But it doesn't switch to ART, it just does a regular reboot. I used to be able to switch between the two runtimes easily until recently. The only modifications I have are root access, custom recovery, and the Xposed framework with some modules. Do any of you guys know what's going on with my phone? I think something might be corrupted or incompatible in my software.
Thanks a lot for the help!
Current Devices: Google Nexus 5 and Nexus 10, both running KitKat 4.4.2
Before someone flames you I'll be polite. Xposed is not supported at this time that's why its not switching to art. To activate. Unsitall and remove any closed framework mods and xposed itself. Then it should let you.
Sent from my Nexus 5 using xda app-developers app
NyquilOverdose said:
Hey everyone,
I've been using my Nexus 5 since November and I have to say I love it. I have the phone rooted, running stock 4.4.2.
Here's my problem: when I try to switch to ART runtime in developer settings, I get the regular prompt and my phone reboots. But it doesn't switch to ART, it just does a regular reboot. I used to be able to switch between the two runtimes easily until recently. The only modifications I have are root access, custom recovery, and the Xposed framework with some modules. Do any of you guys know what's going on with my phone? I think something might be corrupted or incompatible in my software.
Thanks a lot for the help!
Current Devices: Google Nexus 5 and Nexus 10, both running KitKat 4.4.2
Click to expand...
Click to collapse
Xposed Module is incompatible with ART
It's causing this issue
Sent from my Nexus 5 using Tapatalk
Thanks guys! I think I'll hold off on art because I use xposed a lot.
Current Devices: Google Nexus 5 and Nexus 10, both running KitKat 4.4.2
Related
Hey, here is my problem:
I have a client who owns a restaurant, who wishes to have tablets in his restaurant so his customers can read it as a menu and order using the tablet.
However there is a really big problem, because I need to hide the system bar (Not to be confused) with the status bar, and I would need to do it on the most recent android, which currently happens to be Jelly bean.
I know that ordinarily one would need a rooted device to do this, however the real question is:
If I build android from source, and make an application which removes the system bar and install it as a system application, do I really need root?
I don't think I do because it would be a system app, but I'm not sure...
How to do plan on installing it as a system app, or building Android from source, without root?
Sent from my Nexus 4 using Tapatalk 2
You need root to do that?
TJBunch1228 said:
How to do plan on installing it as a system app, or building Android from source, without root?
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
I have compiled it from source and installed an app to test it out, however fastboot can't detect any devices...
Could it be that fastboot only detects rooted devices?
So it's been a little bit of time, and I'm curious to try out the new runtime. Problem is, every time I try to make the switch, all it does is reboot. I don't get the 5-10 build time, and I'm still running dalvik. Stock ROM, Franco r16 test kernel, rooted, unlocked boot loader, etc. Any ideas what could be preventing me from making the change? Or a method to find out for myself?
TIA
Sent from my Nexus 5 using Tapatalk
Seattleite said:
So it's been a little bit of time, and I'm curious to try out the new runtime. Problem is, every time I try to make the switch, all it does is reboot. I don't get the 5-10 build time, and I'm still running dalvik. Stock ROM, Franco r16 test kernel, rooted, unlocked boot loader, etc. Any ideas what could be preventing me from making the change? Or a method to find out for myself?
TIA
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Are you sure the kernel that you are running supports ART?
dabbill said:
Are you sure the kernel that you are running supports ART?
Click to expand...
Click to collapse
I don't think that's it, as I flashed back to stock to see if that was the case, and still no luck...
Sent from my Nexus 5 using Tapatalk
Seattleite said:
I don't think that's it, as I flashed back to stock to see if that was the case, and still no luck...
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Not sure then, i have switched from Dalvik to ART and back to Dalvik several times with no issues.
Do you have Xposed framework installed?
Sent from my Nexus 5 using xda app-developers app
A_Str8 said:
Do you have Xposed framework installed?
Sent from my Nexus 5 using xda app-developers app
Click to expand...
Click to collapse
I do not. I've reverted back to an old nandroid, and that worked. Topic can be closed/deleted.
Sent from my Nexus 5 using Tapatalk
Thanks
A_Str8 said:
Do you have Xposed framework installed?
Sent from my Nexus 5 using xda app-developers app
Click to expand...
Click to collapse
Thank you! Removing Xposed framework allowed me to convert.
Hey guys, I'm trying to switch my runtime to ART. I did it a couple days ago and was successful. But was just now looking around in my developer options and noticed it's back to Dalvik. Not sure how it got switched back and when I try and go back to ART, it does reboot the phone but doesn't actually switch to ART, just stays on Dalvik. Any ideas? Could it be an app I've installed that's switched it off, like ROM manager or Xposed Framework or something? The phone is rooted and on stock rom. It was rooted when I successfully switched to ART earlier too. Any ideas? First time actually posting, sorry if it's in the wrong area or I did anything wrong.... lol. Thanks!
Sent from my Nexus 5 using xda app-developers app
drumjeenyus said:
Hey guys, I'm trying to switch my runtime to ART. I did it a couple days ago and was successful. But was just now looking around in my developer options and noticed it's back to Dalvik. Not sure how it got switched back and when I try and go back to ART, it does reboot the phone but doesn't actually switch to ART, just stays on Dalvik. Any ideas? Could it be an app I've installed that's switched it off, like ROM manager or Xposed Framework or something? The phone is rooted and on stock rom. It was rooted when I successfully switched to ART earlier too. Any ideas? First time actually posting, sorry if it's in the wrong area or I did anything wrong.... lol. Thanks!
Sent from my Nexus 5 using xda app-developers app
Click to expand...
Click to collapse
yep, it's the xposed framework, for it doesn't work with ART it just prevent the system to switch
Sweet deal, okay, I have a decision to make than. Thanks so much! Hopefully it'll be compatible with ART soon.
Sent from my Nexus 5 using xda app-developers app
Has anyone that has upgraded to any rom with Android 5.0 or higher successfully installed both the Tasker app and the Utter app? I have been searching and see starting back in November a few posts about this but none have resloved it. I can install either one without difficulty from both the google playstore and titanium backup. I can not however install both. Some have suggested doing a fresh install of the 5.0 rom then immediately doing a factory data reset. This didn't work. I have an LG G2 on Sprint and am running lollipop. The rom is great. Having to choose between Tasker and Utter isn't so great.
I have been experiencing exactly the same problem. I'm on the galaxy nexus (maguro) using fml lollipop.
Did you find any solution?
Guys, it seems, there is nothing you can do apart from reporting the issue to the devs. With Android Lollipop it's not possible two apps that declare a permission using the same name in their manifest. So you have to wait for the developers of the apps change something or the android devs change something in the OS. Sadly for now, all you can do is install only the one of the affected apps. So since utter does not work on lollipop, I am gonna install tasker for the moment.
Error 505, Tasker-Utter
Same here, Nexus 5, Lollipop 5.0.2. end of January 2015. Still can't install Tasker and Utter, one or the other, error 505.
Hi all, this has now been resolved via bens latest utter! Test build. woo hoo! Enjoy!
Utter! Latest test build http://forum.xda-developers.com/showthread.php?p=58777792
Sent from my SM-G900F using XDA Free mobile app
mtomo82 said:
Hi all, this has now been resolved via bens latest utter! Test build. woo hoo! Enjoy!
Utter! Latest test build http://forum.xda-developers.com/showthread.php?p=58777792
Sent from my SM-G900F using XDA Free mobile app
Click to expand...
Click to collapse
Great news. I hope the new version will be published on google play, too.
I had tried the fix on my LG G2 rooted running AICP 5.0 and got the beeping problem. Just upgraded to the LG G4 and haven't rooted it yet. Tried this fix and it works perfectly. After several failed attempts to install it from the Playstore (tasker already installed). Finally a lollipop rom with both tasker and utter running fine. Thanks for posting.
I have also the problem that it is not possible to install tasker and utter together on android 6.0.1.
finished this one 4am this morning, and fell asleep before I could post, so here you go:
Writeup, details, etc all here:
http://dmitry.gr/index.php?r=06. Thoughts&proj=04. Android M on Grouper
What works: selinux, camera, NFC, GPS, WiFi, Bluetooth
No dirty patches in /platform, no dirty hacks
Lots of cool hacks though. Read up
This is for WiFi devices only (for now)
use latest public bootloader
and i suggest a data wipe - i do not support any conflicts with existing data - selinux policies changed in ways that might affect /data, so having things in /data can affect things like GPS adversely
Awesome! Do we need to update radio/bootloader first?
Sent from my Nexus 5 using Tapatalk
tcat007 said:
Awesome! Do we need to update radio/bootloader first?
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
use latest
and i suggest a data wipe - i do not support any conflicts with existing data - sepolicy changed so thing sin /data/can affect thing sliek GPS adversely
Did factory reset. Got error updating binary script in TWRP.
Sent from my Nexus 5 using Tapatalk
tcat007 said:
Did factory reset. Got error updating binary script in TWRP.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
try using fastboot
i did not test TWRP package (fell asleep)
will look into it later today
TWRP package fixed, uploaded
Is the 'Doze' functionality of Marshmallow working?
It is for me
what Gapps did you end up using? I've flashed multiple packages and it all leads to Setup Wizard problems
Yeah, rom flash works, but stuck with no playstore. Also tried flashing supersu and got a bootloop. Also tried to install an apk from Explorer and wouldn't install. I know this is real really so I'm sure things will get added. But what's here feels much faster and smooth! 6 on a 7, wow!
Edit: I downloaded these "mini" and they seem to be installing OK. http://androiding.how/android-6-0-marshmallow-gapps/
Got me to set up screen!
Sent from my Nexus 5 using Tapatalk
After fighting a bit, the ROM started and I'm restoring my apps from playstore, when I chose the restore point in the wizard, this failed, then select "New device" to continue, anyway restoration began. After finishing the wizard i modified play services permissions to stop FCs.
These were my steps:
1 Wipe Data/System/Cache/Dalvik
2 Flash ROM
3 Flash BETA-SuperSU-v2.52
4 Flash benzo-gapps-M-20151011-signed-chroma-r3
5 Wipe Data/Cache/Dalvik
6 Reboot
Seriously, this is quick and brilliant work. Congrats to all of you who put in the hours and stress. This.....is why I only use Nexus devices. Your efforts are truly appreciated. Best of luck as you continue to further this project.
rebel1699 said:
Congrats to all of you who put in the hours and stress..
Click to expand...
Click to collapse
Glad to help
I am not one of them people who make ROMs all the time. I just wanted to do all the actually hard work of the port and offer specific directions to them, so they can support M on this crop of nexus devices
I'm not getting su 2.52 to boot. Everything w/o root is great!
Sent from my Nexus 5 using Tapatalk
See Nexus 4/10 forums where people already figured it out
My Nexus 7 has been revived... 5.1.1 was unbearably slow. I'm very impressed. Great work!
M on N7
Happy to see that people still supports and share their work for the N7 - big thanks :good:
Now it's exciting to see if the N7 will be able to handle Android M for more than a day or two before slowing down :fingers-crossed:
I'll try this out
How does this differ from [WIP][ROM][6.0] Nexus 7 Marshmallow - Android 6.0?
Hello Guys! From where to download the file for grouper.Thank You!
Sent from my Nexus 7 using XDA Free mobile app
When do you think it is possible to have a version for the Nexus 7 3G (tilapia)?
Thanks a lot for your contribution.
hmmm