Anyone enabled ART in dev options? On 442 unrooted? - Moto X Q&A

I am afraid to touch it. It is set to dalvik by default.

aviwdoowks said:
I am afraid to touch it. It is set to dalvik by default.
Click to expand...
Click to collapse
Does not hurt.. I have used it for a while -finally back to Dalvik because Deus Ex (sorry, I am an occasional gamer) did not work (FC) on ART. Actually did not have the feeling that ART faster/ snappier was (as it was claimed on 4.4) -but not worse than Davlik neither.
I guess it is your choice; but look out for app compatibility.

ART is not quite ready for primetime. Doesn't hurt to try it. I went back to Dalvik. Some of my apps didn't play nice with ART.
Sent from my Moto X.

Been running ART for more than a month now, I think. I don't have any real exotic apps so it works fine with all of them so far.

Related

[Q] Need help with CyanogenMod

I recently rooted and installed CyanogenMod RC 3, and now I'm not really sure what to do. I'm not really sure what CM can do that FroYo couldn't, other than little things like wakeup with trackball or customizing your notifications. What are some of the great features of CM that aren't apparent? A ton of people appear to be using this ROM, so I have to imagine that it's capable of a number of great things that I'm just not aware of.
I do have 3 specific questions though. First, I am just not feeling this ADW Launcher. I don't know if it's just not being utilized properly, but I came from LauncherPro and loved it much more than ADW so far. I mean I can't even figure out how to move/delete widgets from my screen! The one thing I do like is how customizable the widgets are, in terms of columns and rows. Is that an ADW thing or a CM thing? Also, can LP be installed on CM or will that cause problems/reduced functionality?
Secondly, since this is just an RC, inevitably we will have have another release of this mod. Will I need to Wipe my phone before installing the final version? I don't want to spend all this time re-downloading/installing all my apps only to have to do it again in a few weeks when the final release is available.
Thirdly, will Quick Profiles work on CM? I had that on Stock and I really liked how I could easily switch ringer/notification volume in different places.
TIA.
1. Yes, you can use launcher pro.
2. There's no need to wipe.
3. Yes
Developers always tell you to wipe to prevent odd stuff from happening. If you encounter bootloops after a flash, or any odd behavior, it's best to wipe and then reflash. Therefor, a full wipe is a preemptive measure, so you don't have to reflash. The only thing you should need to wipe would be the Cache partition and Dalvik Cache, but that's only if you switch from another rom usually.
The best way to think about cyanogenmod:
Stock froyo is like a Mustang. It's fast, it's sleek, and it feels good.
Cyanogenmod is like Saleen. They take the Mustang (stock froyo), and tune it to the optimum. They add features, remove/replace unnecessary bits, lighten up the load, and smack a sickass bodykit on it.
The only thing you should need to wipe would be the Cache partition and Dalvik Cache, but that's only if you switch from another rom usually.
The best way to think about cyanogenmod:
Stock Froyo is like a Mustang. It's fast, it's sleek, and it feels good.
Cyanogenmod is like a Saleen. They take the Mustang (stock froyo), and tune it to the optimum. They add features, remove/replace unnecessary bits, lighten up the load, and smack a sickass bodykit on it.
Click to expand...
Click to collapse
Booooom. You nailed it. CM is Like a Saleen or a Roush Mustang. Got that right
Sent from my CM6 Nexus One using XDA App
Mokurex said:
1. Yes, you can use launcher pro.
2. There's no need to wipe.
3. Yes
Click to expand...
Click to collapse
Can anyone attest to getting Quick Profiles to work? I recently installed it and I've had more Force Closes than Blockbuster Video. I mean it really is at the point of unusable.

[Q] Switching to ART Runtime - Side Effects?

I'm on a completely stock unrooted retail version of the Moto X (XT1052) in the UK.
The below article says switching to ART run time will speed up the overall performance of my device.
http://www.redmondpie.com/how-to-speed-up-galaxy-s5-htc-one-m8-nexus-5-in-a-matter-of-minutes/
My question is, are there any side effects to doing this?
Are all the popular apps like Skype, Facebook, Twitter, etc compatible with this feature??
Wutang200 said:
I'm on a completely stock unrooted retail version of the Moto X (XT1052) in the UK.
The below article says switching to ART run time will speed up the overall performance of my device.
http://www.redmondpie.com/how-to-speed-up-galaxy-s5-htc-one-m8-nexus-5-in-a-matter-of-minutes/
My question is, are there any side effects to doing this?
Are all the popular apps like Skype, Facebook, Twitter, etc compatible with this feature??
Click to expand...
Click to collapse
You should be fine --- try it! Any issues, and you can always switch back to Dalvik.
The only reason most people avoid ART is because it is incompatible with Xposed/GravityBox....but since you aren't rooted, this doesn't apply to you.
Good Luck
Just tried it and it's made my phone slower than before lol.
Also my power button doesn't respond no more so I'm not able to lock my phone as before.
Facebook didn't run either.
Currently changing back to Dalvik again as I don't think the feature is properly ready yet. Will wait for the official Moto release.
I switched to ART today out of curiosity. Everything works as usual, even xposed modules and gravitybox too... I only noticed that my phone is somewhat smoother. Maybe placebo effect...
ezeuba said:
I switched to ART today out of curiosity. Everything works as usual, even xposed modules and gravitybox too... I only noticed that my phone is somewhat smoother. Maybe placebo effect...
Click to expand...
Click to collapse
Lol, you can't have Xposed and ART at the same time. It must have reverted to Dalvik, check it :laugh:
devilsdouble said:
Lol, you can't have Xposed and ART at the same time. It must have reverted to Dalvik, check it :laugh:
Click to expand...
Click to collapse
Yes. It reverted. So, I must remove xposed before ART can work?
ezeuba said:
Yes. It reverted. So, I must remove xposed before ART can work?
Click to expand...
Click to collapse
Yeah mate unfortunately that's the only option
Yup, @devilsdouble is exactly correct. You can *thank* the Xposed DEVs for this. If it didn't switch you back to dalvik automatically, you would be in a boot-loop now...and probably have to return to stock in order to recover. :good:
Xposed is not compatible with ART. Adapting it to be compatible is in the works, but it's hard telling when that will be completed.
samwathegreat said:
Yup, @devilsdouble is exactly correct. You can *thank* the Xposed DEVs for this. If it didn't switch you back to dalvik automatically, you would be in a boot-loop now...and probably have to return to stock in order to recover. :good:
Xposed is not compatible with ART. Adapting it to be compatible is in the works, but it's hard telling when that will be completed.
Click to expand...
Click to collapse
Oh I think it'll be ready for the next version of android [emoji16]
Sent from my XT1060
Yesterday I did switch to ART for testing. So far, I have not seen much difference.
I'll test for a couple of weeks and post my 2 cents!
ART allegedely is better for your battery because It uses more than just the JIT compiler. It also takes a while for the apks to be reoptimized compared to how long Dalvik takes to optimize apks after some have been added or updated. The version that comes with 4.4.4 is good but ART likely won't be fully realized until Android L.
Just a little piece of advice, since I just had to factory reset the phone: do not install Monument Valley under ART. It is not fully compatible, and I after an update I got stuck on the boot screen.
Calendar lost is still an art problem - easy to solve with restart, but bugging..

Xposed on LG G3 running ART

I have a stock rooted LG G3 that's running ART (and has made a world of difference) . I read that xposed runs on Dalvik. Will I have issues loading Xposed with ART selected, or am I playing with fire?
I've read original post, but I would like some feedback from users who attempted.
-- Yeah, I'm an idiot. Just reread the non-support of ART, sorry for my stupidity!
schmoof said:
I have a stock rooted LG G3 that's running ART (and has made a world of difference) . I read that xposed runs on Dalvik. Will I have issues loading Xposed with ART selected, or am I playing with fire?
Click to expand...
Click to collapse
Xposed will automatically switch you back to Dalvik without prompting you
Honestly, ART is great, but its not THAT noticeable
Sent from my m7spr
Thanks. I guess I'll switch manually back to Dalvik to avoid bootloops. Can't wait until it's officially supported, as my battery life has been noticeably better.
So glad I made the change back. I've opened up a whole new world of mods.

[PSA]Using Xposed causes LAG!

If you are using Xposed framework on the Note 4, Secure storage will fail to process and save data, which leads to a Sensor service hangs, which causes the laggy experience some of you have been having.
This was an issue back on the S5, it is fixed by using this module XSecureStorage by @wanam or disabling S Health.
However from what I have heard this doesn't fix Private Mode.
just to clairfy...mine is laggy all the time. I am probably wrong considering it is 830am but it said s-health and private mode only...does that mean that module will only fix the lag
when using s-health?
installed XSecureStorage but S health still hang. it's really a difficult decision: use xposed for full control, or uninstall xposed for smoother operations...
RomBox said:
installed XSecureStorage but S health still hang. it's really a difficult decision: use xposed for full control, or uninstall xposed for smoother operations...
Click to expand...
Click to collapse
What if you "freeze" S health using ROM Toolbox?. Does it still cause problems?
are you using ART or DALVIK as your runtime?
Shtihi said:
are you using ART or DALVIK as your runtime?
Click to expand...
Click to collapse
You can't use Xposed with ART yet.
Batfink33 said:
What if you "freeze" S health using ROM Toolbox?. Does it still cause problems?
Click to expand...
Click to collapse
disabled S Health use TB and installed xposed back, so far no lag noticed...
Got my Note 4 last night, and it lagged right away straight out of the box.
If you boys are only getting lag after installing Xposed you're lucky!!! lol
Although I was planning to install it, I might think twice after your thread. How bad is it exactly?
For example my settings always stutters if I open it and start trying to scroll straight away. If I wait a couple of seconds, it's usually fine.
Same goes for pressing recently used apps button, and scrolling through the card stack. If I give it a second it's ok, but if I try straight away it's lag city.
So far I've found 0 difference between the Note 4 and the S4. Maybe I'm just unlucky!
prophet42 said:
Got my Note 4 last night, and it lagged right away straight out of the box.
If you boys are only getting lag after installing Xposed you're lucky!!! lol
Although I was planning to install it, I might think twice after your thread. How bad is it exactly?
For example my settings always stutters if I open it and start trying to scroll straight away. If I wait a couple of seconds, it's usually fine.
Same goes for pressing recently used apps button, and scrolling through the card stack. If I give it a second it's ok, but if I try straight away it's lag city.
So far I've found 0 difference between the Note 4 and the S4. Maybe I'm just unlucky!
Click to expand...
Click to collapse
TRY THIS I hope this helps as much as myself
https://www.youtube.com/watch?v=RAXtjgrfgEY
asia559571 said:
TRY THIS I hope this helps as much as myself
https://www.youtube.com/watch?v=RAXtjgrfgEY
Click to expand...
Click to collapse
First think I did out the box =)
Along with removing touchwiz, switching off certain google now features (such as "OK Google" detection), and removing flipboard.
Always slowed the animations down since the days of the Galaxy S 3. S Voice and health are the first things I remove since the S5.
It helps a little, but unfortuntely the lag is still there (well unless I leave it a split second for it to load).
But that's something I can live with. Thanks anyway. Anyone who doesn't done it, it will help.
Although one interesting side effect is the accessability options mess up, so now the calculator talks to me lol.
But hopefully that will be addressed soon. There are other threads on that subject.
Wanam xposed module already has these functions built in. Been using it since day 1. No need for a separate module guys
badwolf94 said:
If you are using Xposed framework on the Note 4, Secure storage will fail to process and save data, which leads to a Sensor service hangs, which causes the laggy experience some of you have been having.
This was an issue back on the S5, it is fixed by using this module XSecureStorage by @wanam or disabling S Health.
However from what I have heard this doesn't fix Private Mode.
Click to expand...
Click to collapse
I don't know but I think you are posting wrong information.
I've been using xposed and secure storage on FireKat without any lagging or secure storage issues.
My Note runs buttery smooth and 100% stable since day one.
Cheers ?
Sent from my SM-N910T using Tapatalk
Rayan said:
I don't know but I think you are posting wrong information.
I've been using xposed and secure storage on FireKat without any lagging or secure storage issues.
My Note runs buttery smooth and 100% stable since day one.
Cheers ?
Sent from my SM-N910T using Tapatalk
Click to expand...
Click to collapse
If you are running a custom rom chances are the dev has already fixed the issue by editing the buildprop to secure storage support false
sawdoctor said:
If you are running a custom rom chances are the dev has already fixed the issue by editing the buildprop to secure storage support false
Click to expand...
Click to collapse
Yeah this pretty much, the thread was made back when Note 4 first came out and their wasn't any custom ROMS available. All of the ROMS to-date have the necessary fixes enabled.
I have both private mode and S Health running without any problems or lag. Running Firekat v. 8, Xposed. Disabling secure storage in Xposed is the key.
sawdoctor said:
If you are running a custom rom chances are the dev has already fixed the issue by editing the buildprop to secure storage support false
Click to expand...
Click to collapse
I wish it was as simple as editing the Build.prop file... But no, for some reason DynamicKat's Secure Storage does not work for me even though it comes with the required settings on build.prop
No matter what I throw at it, paches, fixes, editing build.prop, disabling SHealth, xposed modules, etc, it simply refuses to work.
But the good thing is that at least on Firekat it does work flawlessly as I've mentioned before.
Cheers!
wipe cache and data of s health in app settings, you will have it running again, I have no lags

Got Annoying Lag on Lollipop? Here's a tip that can save your Nexus 7!

If you go to Settings>Developer Options, tap "Enable View Attribute Inspection", then boot into recovery and clear cache, your Nexus 7 will run like new, no lag, no freezing.
If you need help doing this, there are steps below for you to look at.
*HOW TO GET DEV OPTIONS IF YOU DON'T SEE IT*
-Go to Settings>About tablet.
-Find the build number.
-Mash it until a message telling you that you are a developer appears.
-You're done!
*HOW TO GET INTO RECOVERY AND CLEAR CACHE*
Do this after you enable "View Attribute Inspection".
-Power off your Nexus
-Press the power and volume down buttons until you see a screen with an Android guy with an open chest and some device info and options.
-To scroll through the options, use the volume up or down buttons to show an option, and use the power button to select it. The option we are looking for is "Recovery".
-Once you select it, the Google screen will appear and after a couple seconds, an Android guy with his chest open and the words "No command" appear.
-Don't freak out now! Now press the power and the volume up buttons and count to 3. After you count to 3, let go of the buttons, and a menu will appear. And again, to scroll through the options, use the volume up or down buttons to show an option, and use the power button to select it. Now highlight "Clear cache", and select it. The Nexus will do its magic, and when it's done, highlight "Reboot to system" and you will reboot to Lollipop.
Hope I helped!
I'm guessing that wiping the cache does more than anything else. Otherwise, its a harmless enough tweak to try. Like most of these things, for some it'll work, for others it wont.
May I ask what that View Attribute Inspection option does exactly? I know that clearing cache helps but its only a temporary solution and needs to be done regularly, but I have not heard of that option before so, what does it do?
Tried this on both my N5 and N7, with some strange (to me) results.
When I did it the first time on my N7 (maybe about 3 weeks ago) the wiping was pretty much instantaneous, whereas on the N5 it took close to ten minutes (!).
Did it again today on both devices, with the wiping being complete instantaneously on the N7, while on the N5 it took maybe about 3 minutes this time.
Any particular reason why that would happen?
I own the same devices, and I can confirm this weird behavior is, I think, normal. Wiping cache takes a second on the N7, and several minutes on the N5.
Sent from my Nexus 5
Wish39 said:
If you go to Settings>Developer Options, tap "Enable View Attribute Inspection", then boot into recovery and clear cache, your Nexus 7 will run like new, no lag, no freezing.
[...snip...]
Hope I helped!
Click to expand...
Click to collapse
I tried this, and it worked like a charm. Thanks for the great tip!
And as for the business of wiping the cache without following Wish39's Developers Options change: Nope. I've been wiping the cache on my N7 since the update, and things are noticeably faster now.
Do it; it'll make you happy.
cheers,
john
The reason why I recommend wiping cache is this: Your Nexus 7 may still lag or stutter after enabling the view attribute inspection (happened to my Nexus 7 after discovering and enabling the option).
So to summarize:
If your Nexus 7 is fast enough for you after doing the tweak, don't wipe the cache unless you really want to.
If your Nexus 7 still lags like hell, do wipe the cache to speed it up.
Sent from my HTC One
Thank you man, I did the tweak but few minutes ago but the tablet seems smoother and snappier indeed. I didn't even clear the cache (which I already did a couple of weeks ago).
My only concern is about what this option does, can you tell me more about the actual meaning of this checkbox?
Sent from my Nexus 5
I've actually done research on that. What it does is it opens some sort of new view into Android System Manager. But even I can't understand why it speeds up your device.
Sent from my HTC One
Wish39 said:
I've actually done research on that. What it does is it opens some sort of new view into Android System Manager. But even I can't understand why it speeds up your device.
Sent from my HTC One
Click to expand...
Click to collapse
Nothing to understand; it doesn't.
Whoops. Guess my memory is a bit fuzzy. I looked it up again and this is what I found.
"Enable view attribute inspection: Inspect views’ attributes in Android System Manager." -http://www.droidviews.com/guide-android-developer-options/
So far so good. This has made a significant difference for me. Many thanks to Wish39
Wish39 said:
Whoops. Guess my memory is a bit fuzzy. I looked it up again and this is what I found.
"Enable view attribute inspection: Inspect views’ attributes in Android System Manager." -http://www.droidviews.com/guide-android-developer-options/
Click to expand...
Click to collapse
Does that mean that this option has no effect on the performance? Because I did enable it and saw no actual improvement in performance, though there might have been something very small, but not sure if it was due to the option.
I didn't see a noticeable change in performance. Chrome still brings the Nexus 7 to its knees when it comes to performance.
i'm doing this procedure but in the recovey menu I don't see the option clear cache
I see
1. Wipe cache/factory reset
2. Wipe cache patrition data.
saloufas17 said:
i'm doing this procedure but in the recovey menu I don't see the option clear cache
I see
1. Wipe cache/factory reset
2. Wipe cache patrition data.
Click to expand...
Click to collapse
Choose wipe cache partition as you are wiping your cache.
Sent from my HTC One
Cheers I'll try this soon i was beginning to think Lollipop was a crock of sh*t to be honest my N7 was so sluggish
jonny68 said:
Cheers I'll try this soon i was beginning to think Lollipop was a crock of sh*t to be honest my N7 was so sluggish
Click to expand...
Click to collapse
FWIW, I went through both releases from Goog of L on my N7/2012/WiFi and in the end found it just "that much" too irritating.
Last couple weeks (3?) I've been running the nightly CyanogenMod 12 release and I haven't had a real reason to *****. I update my CM12 edition weekly, not nightly, and the last two weeks it's been pretty solidly non-irritating. Kindle App, Zinio, Firefox, Chrome, Facebook Lite, some others.
The only app which seems performance constrained so far is Rocket Player. Sometimes it hiccups. Haven't played with any tweaking though to get resolve it.
If you're interested in playing with CM12 nightly => https://download.cyanogenmod.org/?device=grouper&type=nightly
Cheers.
well this method works temporarily 2-3days it will soon starts to lag... so i'd be 50-50 neutral here. does speed up a lil but will lag few days later on.
MxFadzil92 said:
well this method works temporarily 2-3days it will soon starts to lag... so i'd be 50-50 neutral here. does speed up a lil but will lag few days later on.
Click to expand...
Click to collapse
Agreed. My n7 is lagging again... I think I'll opt for a faster custom ROM based on Lollipop.
Sent from my Nexus 5

Categories

Resources