[Q] Does Odex/Deodex still matter with Android Lollipop and Art? - Android Q&A, Help & Troubleshooting

Hey guys,
I was playing around with my Moto X 2014 running Android Lollipop and saw that there are still .odex files corresponding to each system application's .apk file. I have also seen Android lollipop ROMs here that says it's deodexed. Now I'm confused about the difference between odex and deodex for ART? I thought everything is compiled into byte-code when it's first installed?
Any explanation would be appreciated!

I think this is done by them to reduce boot time and reduce the overall system size (as ELF is supposed to use larger space).
BTW can you check if "/data/dalvik-cache" is still present ?

Related

[BOOTANIM][GO/P/SOLA/U] Smoother Intro Boot Animation + Alternating Boot Animations

Anyone who has installed the recently released Jelly Bean update will have noticed that the Xperia logo is now static.
I was annoyed at having to watch two static images on boot, so I took the images from the older firmware and made a replacement introductory animation.
I've made a preview so you can decide if you want it without having to go through the trouble of installing it, see the attached image below.
The only image that has been modified is the one in the generic1 folder; everything else has been left as-is. All pngs have been compressed using Ken Silverman's PNGOUT utility.
This is packaged in a CWM-compatible format, so manually installing it requires extracting bootanimation.zip from it first.
Since this is merely a boot animation, non-JB users can install it with no issues.
Credits:
Sony for the images used (and for releasing the JB update).
despotovski01 for his excellent tutorial on modifying bootanimations.
Ken Silverman for his highly-efficient PNGOUT tool.
TGRMN Software for their awesome bulk rename utility.
stifilz for uploading the stock Xperia Tablet S boot animation.
eddrowe for uploading the stock Xperia T boot animation.
Rhamon's for requesting the Xperia P versions.
miunkwn for requesting the Xperia sola/U versions and providing me with the files I requested.
Edit (9/5/13):
I attempted to eliminate the brief blank screen between the Sony logo vanishing and the boot animation actually starting as well, but was unable to - it actually ended up looking even worse since there's apparently no way to prevent that (should really have checked that first before going through the trouble of extracting kernel.sin-ramdisk/logo.rle, but oh well). :/
Update (15/5/13):
I've made two additional variants that alternate between differing boot animations in each cycle. See the attached images below for the previews. They are shown in the following order:
smooth intro + stock JB animation | smooth intro + alternating stock JB & Xperia Tablet S Cosmic Flow animations | smooth intro + alternating stock JB & Xperia T Cosmic Flow animations
Personally, I prefer the variant with the Xperia T's Cosmic Flow animation - those glowing particle effects really do make it look cooler. Unfortunately, it's also the largest set, weighing in at a hefty 4.10 MB.
Update (16/5/13):
At Rhamon's request, I've made versions for the Xperia P. I'm not adding new previews for them though since they're basically the exact same sequences, just in larger scale for the P's bigger screen. Look for the zip archives suffixed with _p for the versions targeted at the Xperia P (e.g. smooth_intro_bootanim_jbxts_p.zip). As with those for the go, these are packaged in CWM-compatible formats, so manual installation requires extracting bootanimation.zip from them first.
Update (20/5/13):
I've also made versions for the Xperia sola and Xperia U at miunkwn's request. As with those for the go and P, these are packaged in CWM-compatible formats, so manual installation requires extracting bootanimation.zip from them first. Look for the zip archives suffixed with _sola_u for the versions targeted at the Xperia sola and Xperia U (e.g. smooth_intro_bootanim_jbxts_sola_u.zip).
Minor Update (22/5/13):
It turns out that my little script had a bug where it was automatically zipaligning bootanimation.zip, it bloats the archives and doesn't really provide any benefit whatsoever (even the stock firmwares' own bootanimation.zip archives are unaligned). For those who have already installed this boot animation, please re-download and re-install them again.
I also took the opportunity to fix the CWM package filenames on the alternating variants for the Xperia go so they now correctly read _jbxts.zip and _jbxt.zip (previously _xtsjb.zip and _xtjb.zip respectively; merely a cosmetic change with no impact).
Added two variants with alternating animations; bumped for update visibility (was on page 5).
So awesome! Can you make it for Xperia P screen please?
Sure, but I'll need you to upload the bootanimation.zip from the P's GB/ICS firmware (not JB - I already have that one) so I can generate the smoothed intro from those - unless you don't want that, that is. The Xperia go ones would probably look minuscule on that massive screen, plus upscaling looks terribad in general. Since I already have the stock JB bootanimation.zip for the P, I'll start working on the looping sequence first. Disregard, see edits below.
Edit:
Since the Xperia T's boot animation frames are exactly the same size as the P's, I'll simply keep them as-is (i.e. I'll leave them untouched as .jpg files) and merely do renames to keep them in order.
The Xperia Tablet S' boot animation, on the other hand, needs to be resized, so I'll convert everything into .png files to preserve them and prevent further quality degradation (JPEG compression discards data with each compression pass, so I was pretty dismayed when I noticed that Sony used it in its newer boot animations :/ ).
Edit 2:
Okay, I've got the stock bootanimation.zip from the P's GB firmware, will work on the smooth introductory sequence.
forget about it then
Hmm, that's odd since my script only alters the permissions of the bootanimation.zip alone and nothing else. Possibly coincidence?
I've Downloaded the XT boot animation for P and it Works great!
Thanks!
It's good to hear that it's working fine for you and that you like it, that means my little idea of mixing the animations is working out pretty well.
celeritykid said:
thx. nice one. but i have a problem here. my livewallpaper would not save after flashing xtsjb and xtjb bootanimation. there was no such problem when i flash the smooth stock bootanimation. any idea?
Click to expand...
Click to collapse
Please friend
Do not quote the op
Kindly edit the post as it makes the post unnecessarily longer
Thank You
Can you make one for Xperia U?
I'll need you to upload the stock bootanimation.zip from the U's GB/ICS firmware and its JB firmware so I can make a complete version for it (although I already have larger ones from the P's boot animations, I try to avoid scaling images and stick with the pristine ones for maximum quality).
Edit:
Whoops, brainfart - just remembered that the Xperia U and sola phones don't have official JB firmwares, so I'll generate resized versions from the P's boot animation. Now I'll only need you to upload the GB/ICS one.
I have got a Xperia Z bootanimation for Xperia U, the alternating boot animation seems better.
It will be fine if you can make a good quality bootanimation like Xperia T, if it is easier than making alternating. Will PM you the link
Added Xperia sola and Xperia U versions; bumped for update visibility (was on page 2).
Thanks a lot for making a bootanimation as I requested. Looking nice.
Working perfectly on Xperia Go Stock JB 6.2.A.1.100
Excellent :laugh: thanks! :good:
Awesome thanks :laugh: :good:

[Q] How to Mod application with multiple DPI

Hello, guys
I guess this post is in the right place.
let's say I am a big fan of 250DPI. I dont like 320DPI of SGS3.
When I install ROM, Revolution or any stock ROM, I change DPI in built.pro to 250.
It works!
but still some stock applications are not showing in the right size such as
- SecPhone.apk
- SamsungIME.apk
- Camera
- etc
I know it is gonna be some where to change resource and re-compile or whatever....
and those apps are already mod by some developers here.
The question is Can you guys show me which files in resource to be edited?
this is gonna help to learn new thing....
Thanks

How to port Apps for Android L?

Hey everyone,
at the moment im switching between AOSP Android L and FlymeOS 4.
I really love some flyme apps especially the camera (because of filters), the calculator, sms app and file explorer.
But i don't want to miss the smooth, battery friendly experience of android l.
so my idea was to port the apps i want from flyme to android l. i found some tutorials, but the necessary pictures aren't available anymore.
anyone have an idea how to do the easiest way? i stuck at finding the correct libs and jar files. and if its possible to use flyme apps with the original framework-res.apk of android l or if i have to combine these?
i don't think that anybody portet these apps, so probably you could help me or give me the needed informations
thanks
nobody any ideas?

[Q] Help me with making this Safestrap ROM.

I recently have noticed the drastic increase of people downgrading to 3.2.8 and installing Nexus ROM on their devices. Let's be honest; stock JB isn't visually appealing, and with GAPPS it still doesn't meet the criteria for a modern Android ROM. I would like to present to you, Project ReTHORmation! My goal is get rid of what doesn't meet modern design standards, and to add a modern look to JB. The base is the same as the Safestrap version of the Nexus ROM to insure compatibility with 3.2.8 users. I believe Project ReTHORmation should run on older firmware versions (prior to 3.2.7). I've included GAPPS and a few other apps. I'll post some of them down below:
Greenify
HKThemes Xposed module
Gravity Box
Xposed
Black Out Theme BetterKat
Evernote
Nova Launcher
N7 Camera app
ES File Explorer
Google Keyboard
APK Tool
SuperSU
BusyBox
Chrome Dev
etc...
Here are my questions:
1. How do I compress this in a flashable format (/data and /system) without compromising my privacy (accounts, passwords, etc.) whilst still keeping settings in tact?
2. Is anyone interested in this project/want to help test it?
3. Could I compile openGL 3 and ART (which are included in 4.3) on 4.2.2?
4. Do you guys prefer Mega or Google Drive ?
RESERVED

[Q] Blocking standard system OTA updates on my own ROM

Hey guys,
I've created my own ROM by modifying a 5.0 stock one (deodexing, resigning and adding system apps). But the Android 5.1 OTA update keeps showing up (of course i can't update, because of the different signature).
So my question is: Is there a way to modify some config or delete something from the ROM files, for the system not to check for system updates?
Maybe the name of the ROM or something like that?
Any help is appreciated,
Thanks,
Vlad Ostrovski

Categories

Resources