Just noticed an install of e.g. Facebook takes 2+ minutes. While system said it was installing, I noticed dex2oat was running.
I am assuming this is compiling/conversion of old Dalvik to Art.
Still... Is this a normal execution time for such job?
Every phone that I installed fb takes more than 2mins to install, maybe fb app not uptated 100% to art, I installed that on a Xoom with 3.1 and the app tells me to I need to update Android version
Enviado desde mi XT1562 mediante Tapatalk
Yes. I'd assume it to be API vXX which means it does not support < 4.0 or something. Plus, because the majority is still on < 5.0 it comes with Dalvik. Someone correct me if optimising for 5.0 isn't even an option. I am further assuming that 5.0 can convert with dex2oat but there isn't necessarily something like oat2dex on < 5.0.
Related
I have been trying to set ART as my runtime environment.It asks me about the change in the library and reboots my device.But then again while checking in the developers option it shows me dalvik as the runtime environement.What should I do in order to use the delights of ART.My phone is rooted with stock kitkat image.
cnilesh said:
I have been trying to set ART as my runtime environment.It asks me about the change in the library and reboots my device.But then again while checking in the developers option it shows me dalvik as the runtime environement.What should I do in order to use the delights of ART.My phone is rooted with stock kitkat image.
Click to expand...
Click to collapse
Do you use Xposed? I know that only works with Dalvik at the moment and actively resets that setting to Dalvik.
JASN_DE said:
Do you use Xposed? I know that only works with Dalvik at the moment and actively resets that setting to Dalvik.
Click to expand...
Click to collapse
Yeah i use that module just to extent my greenify features.Is there any way to use exposed and make ART work at the same time?
Quote from rovo89: "After installing Xposed, the runtime gets reset from ART to Dalvik. Can you stop it please?
You can be glad that I implemented this, otherwise you would be in a bootloop know. Xposed isn't compatible with ART (yet). It's a completely different architecture with pretty much no documentation. I hope that I can rewrite Xposed for the ART runtime, but don't expect it in the near future. It requires understanding the concept, the code structure and many details to know how it works. Afterwards, I have to think about ways to hijack it and this needs to be implemented, tested and improved again and again. So please don't ask when it will be available - you will surely know when it is ready." Plz search xda before asking theses questions if you had you'd have found this http://forum.xda-developers.com/showthread.php?t=1574401
Sent from my Nexus 4 using Tapatalk
ART is still in early version so use Dalvik for next few months.
rishabl1d said:
ART is still in early version so use Dalvik for next few months.
Click to expand...
Click to collapse
it has been answered already, the op is just dumb enough to not read the sec post of xposed thread, witch says that it sets back to dalvik, so your answer is wrong, and you also are dumb enough to not read all posts//or u just wanna win more posts.
Is it that I will have to remove all the apps which does not support ART?I have greenify as well as titanium backup and removing xposed also did not help.What should I do?
I'm guessing you just uninstalled xposed without removing the framework... Sigh
Sent from my Nexus 4 using xda premium
Hi guys,
did you notice the lack of free space on N10 after upgrading to 5.0? (I used factory images, if that makes any difference). I have 148K free after rooting on /system. That's a disaster, can't even install BusyBox (around 1 meg), not mentioning Xposed once it's available.
Any ideas how to solve this, yet keep the device accepting future OTA updates?
Thx,
Aleq
I have the exact same problem. Something that I didn't face on my n5. Also fully wiped while installing the factory image.
Btw mate, you won't be able to install xposed anyways since it's not yet compatible with the new runtime
Yes, that's why I wrote "...once it's available".
Anyway the best solution so far is to backup the Stock with CWM (or TWRP), remove the data archive (to save space) and then remove unnecessary apps from /system like Korean input method etc. When OTA comes, restore the system only and apply it. A little bit cumbersome, but I'm not aware of any better solution at this moment. Or perhaps flash system.img via fastboot before OTA.
Could you get busybox to install that way? Or it's not just a problem of space left?
178kb left tho can't be...meant, can it?
PS: sorry, my bad about xposed, I thought you meant to say install xposed once that (busybox) becomes available
PPS: what do you mean with the data archive?
I flashed factory images. Rooted with cf auto. Flashed TWRP recovery and used filemanager to manually remove apps from /system/app folder like gmail maps etc. If needed get them from play store and they will get installed in /data partition instead.
Skickat från min GT-I9505 via Tapatalk
Johan1976 said:
I flashed factory images. Rooted with cf auto. Flashed TWRP recovery and used filemanager to manually remove apps from /system/app folder like gmail maps etc. If needed get them from play store and they will get installed in /data partition instead.
Skickat från min GT-I9505 via Tapatalk
Click to expand...
Click to collapse
But @Aleq suggestion of making a backup of /system before starting to modify it isn't a bad one, atm you have basically no way to be able to install OTAs as they will be released @Johan1976 , not even sideloading them.
I guess I can just flash the system.img from factory images if needed in the future.
Skickat från min GT-I9505 via Tapatalk
Johan1976 said:
I guess I can just flash the system.img from factory images if needed in the future.
Skickat från min GT-I9505 via Tapatalk
Click to expand...
Click to collapse
Also true
Use an app called System app remover (ROOT) found in the playstore. It has a feature which allows you to restore apps if you need them from a trash folder in your user space. I've used it successfully with KitKat and just saw in an XDA post that it works with Lollipop for this exact purpose.
https://play.google.com/store/apps/details?id=com.jumobile.manager.systemapp&hl=en
I liked it enough to purchase the pro version just to support the developer. It even rates what is safe to remove.
Sent from my Nexus 10 using XDA Premium HD app
You can also ship busybox into your kernel ramdisk. But I think for now the simplest remains like others said to remove unnecessary apps from /system partition
However, good news, cm12 takes only ~ 500 mb of space, will make it public when it is a bit more stable.
I'm having the same problem. All busybox apps showing 0.0 system space even after cleaning out 70mb of apps. Can't install busybox at all, tried jrummy, steiricson and busybox X. With the exception of the latter they failed. Suspicious of the legitimacy of busybox X because it said it succeeded when it didn't. I need busybox!!!
Thanks guys, I was able to install busybox after removing unnecessary system apps
Solved removing unnecessary apps with TB
I've uninstalled Korean and Japanese input apps, Cloud print app and stock Live Wallpapers using Titanium Bakchup (about 19 Mb free in System folder). Then Busybox install went OK.
I was finally able to install busybox and get init.d running, thank you.
On a side note, anyone know where lmk went? It's not in the usual /sys/module/lowmemorykiller/ location.
I recently updated "Android System Webveiw" which is installed by default on motorola's 5.02 lollipop. Afterwards, several apps would close without error (there were logcat errors that didn't suggest an obvious course of action.)
For instance, I could open ES file explorer (also latest), but when I clicked on the 'Playlist' folder, it would close... (1weather was another app that didn't work.)
So I restored to a backup and updated apps one a a time starting with "Android System Webview" (I suspected it) and Google Chrome. ES file explorer worked until I updated it, then it started crashing/closing.
When I 'uninstalled' Android System Webview (reverting to the version in /system) the problem went away... Then I found others having a similar problem with other apps: http://forums.androidcentral.com/ht...randomly-shut-down-while-i-am-using-them.html
Hope this helps someone...
No issue for me on 5.1
Sent from my Moto X using XDA Free mobile app
I had the same problem but I thought I messed it up.. It only does it on 5.0.2 for some reason
needleyepoke said:
I had the same problem but I thought I messed it up.. It only does it on 5.0.2 for some reason
Click to expand...
Click to collapse
In the beta community for ASW they discuss that it's actually caused by GPU driver bugs. ASW is exacerbating the bug. They have a beta version in development that it supposed to fix it, but it's not fixing for everyone. Underlying issue likely fixed in Motorola's 5.1 kernel and driver stack.
Hi
after flashing lollipop I recognized that the installation time for each app has been increased.
for example I could install instagram in only less than 1 min.
But now the installation time is longer that this. And also after using instagram for more than 5 mins it works laggy. (not any other apps)
But these never happen on stock 4.4 tw or for example on cm14.(the Final one)
my phone is S4 I-9500 stock tw. 5.0.1
Installation time for apps is longer in Android 5.0.1 because Google switched from using the Dalvik runtime engine to ART. With versions of Android prior to 5.x, Android would compile the resources for the app as you started it; what is referred to as "just in time" compiling. With Android 5.x and later it compiles the app at the time of installation, called "ahead of time" compiling.
The advantage of ahead of time compiling is that the app only has to be compiled once, at installation. The result is that an app in a ahead of time environment will start faster than an app in a just in time environment, where the app is compiled every time it's run.
thank U ☺
Is the fix for android system draining out battery after update to global android 10 known already? I mean real fix, no factory reset and such shouts.
up
Not sure whether you can eliminate google apps and some xiaomi apps by manually debloating (disabling them) via command prompt using adb shell, have you tried that?
I am on Android Pie and successfully debloated all those apps, which helps significantly with SoT.
Wmateria said:
Not sure whether you can eliminate google apps and some xiaomi apps by manually debloating (disabling them) via command prompt using adb shell, have you tried that?
I am on Android Pie and successfully debloated all those apps, which helps significantly with SoT.
Click to expand...
Click to collapse
Why not, ADB works the same.
Rename extension to bat and modify the script further on your iwn