Related
I add the next version info before i release it just so people know what will be changing next update. PLEASE everyone stop PMing, Posting comments about why you cant download the latest update. This is being posted on every rom I make on every site I use Not just here.
Ok so this is based off the system dump. 4-14-11
Thanks (I feel Thanks should be at the top not on the bottom like every1 else cause with out a few people this would never of happened)
To who ever uploaded the Sys Dump
Roach2010 for catching my script error and being the first to install the deodexed rom
mamoulian666 for being the first to even test it
friedgoldmole for installing also and catching a few bugs also
About
This is just a base for my rom. It have been deodexed spent all night getting the bootclasspaths correct and its done.
The update script that installs the rom has been changed to delete system/app and system/framework this is because its a DEODEXed rom meaning no ODEX files are needed so to make the phone less confused it will just delete the old stuff and install the new.
Now this I dont think has been tested sooo Flash at you own risk. Im not responsible if it breaks.
Tweaks
Root
BusyBox
SuperUser
DEODEXED
OPT FrameWork more
OPT Launcher more
Doing this removed 7MB of junk
Change Log
V4
Base is now from the 4-23-11 update
ODEXed (will boot faster will deodex when themes come out)
ZipAligned
V3
pngopt and zipaligned
DEODEXed
BATTERY SAVER (in testing on my acer i tripled my battery life)
V2
Fixed the update script to Edify my mistake thanks Roach2010 for catching me error.
ODEXed the keyboard and asus keyboard so that show fix the FC
added SuperUser.apk
V1.2Test
Based of a sys dump
added the full sys dump
has not been tested
Based off the latest OTA update on the 14th
V1.1
All the files have been deodexed
V1
Based off Hr1
Took out 7MB of Framework and launcher junk
Downloads
Latest
Ti-X AsusTransformer V3
Old
Ti-X AsusTransformer V2
Ti-X AsusTransformer V1.2 TEST
Ti-X AsusTransformer V1.1
Ti-X AsusTransformer V1
Congrats
thanks man i have had it tested and works small gain and 7mb isnt big but ill update once i get it back
ok right now its uploading the latest fixes.
I added in the update-script for it to delete the app and framework folders so it flashes a clean install of my rom. if something goes wrong you can always flash 1.0 as if nothing happened.
If i flash this, does it include the new things in the OTA update? I assume since it's based on the modaco rom it will have root.
the 1.2 is based off the 14ths OTA 1.1 and below is based of Modaco's
all have root and busy box and super user
Thanks for the ROM, dc13!
Tried 1.2test, on top of MCR r1, it errored with status 6.
ok bumma guess the deodex wont work
Actually the deodex works great, the status 6 error is simply because your updater-script uses Amend code which CWM 3 can't read, it only uses Edify.
You need to change two lines in your updater-script:
Code:
delete_recursive SYSTEM:app
delete_recursive SYSTEM:framework
should become:
Code:
delete_recursive ("/system/app");
delete_recursive ("/system/framework");
Here's a link to koush's thread explaining the changes in CWM 3.0
http://forum.xda-developers.com/showthread.php?p=10266810#post10266810
I haven't tested extensively but so far your rom works great with the one exception that the Asus keyboard app continuously force closes - XT9IME.apk. I have no experience of deodexing yet but is it possible it could be done again to try to resolve the FC?
And could you also add Superuser.apk to your next rom please, it would save people having to get it from the market?
Keep up the good work and I think it's awesome that you done all this without a transformer to test on.
wops i thought i did edify. hahaha woops ill cange to day and go from there thanks man for catching my error.
so i take it u r running 1.2? or 1.1?
I installed 1.2 to test after reading the comment about the status 6 as I was sure that it was only the script that wasn't working.
First boot was obviously slow but after that it ran great besides the Asus keyboard.
whats up with the asus kb i cant test till tomorrow or when ever mine is shipped
nm it fcs and i thought i added su woops lol ok 1.3 will b out to night ill make the kb odexed and try that. thanks for doing this man. glad it kinda works.
Working here too, changed the update-script as per Roach2010 and installed over the top of the Modaco rom and it seems to be working great, Asus keyboard is broken here as well but no issue as I am using Swiftkey anyway.
Seems to be missing the MyLibrary app, not sure if that was removed or its something to do with installing over the top of the Modaco rom.
Kinda off top but is there anyway to add a symbolic link from a folder the internal memory "sdcard" to the actual physical card, so for example we can put music on the sd and have it show up in the music app.
ok i made keyboard and the asus kb odexed for now and added SU.
My Library app i dont see that in the area on both mine and modaco's rom anyway we can try to find out what the app name is. the easiest way is to go back to modaco and in the application area find the name there.
once my stuff if done uploading another 600MB then 1.3 will be out.
1.2 is out enjoy.
Nice one, I've been working on deodexing the apk's myself so here's a copy of my deodexed XT9IME.apk for you to use in your roms. The only app I havent done yet is Asus Reader as it is a little trickier to do and I've not got time to sort it tonight.
Roach2010 said:
Nice one, I've been working on deodexing the apk's myself so here's a copy of my deodexed XT9IME.apk for you to use in your roms. The only app I havent done yet is Asus Reader as it is a little trickier to do and I've not got time to sort it tonight.
Click to expand...
Click to collapse
word thanks man ya im not touching asus reader till 3.1 source comes out soon.since its sim to 3.0
canceled my order will wait a bit to get one i just got a email stating may 17th is when id be getting one. So ya
getting a acer but will support this tho.
dc13 said:
canceled my order will wait a bit to get one i just got a email stating may 17th is when id be getting one. So ya
getting a acer but will support this tho.
Click to expand...
Click to collapse
Shame about your order
yep o well acer it is close to 10k that iv given them and i cant even get it a week after release. hmm o well.
Clarification on the poll question:
Yes = The ROM stays up
No = The ROM goes down
With the permission of MildWild I bring to you
MildWild v2.9.5 Lite Final
(based on MildWild V-2.9.5)
This is NOT a new ROM! It's only a trimmed down and fixed up version of MildWild V-2.9.5.
Change Log for Final Version:
- NEW - ZipAligned all system apks
- NEW - Automatic ZipAlign of new apks on every boot
- Fixed 720p HW encoding - works for H.264 format ONLY (see link to test file below)
- Fixed SuperCharger script - now using V6 SuperCharger update 8 with Aggressive 1 Setting
- Updated GO Launcher EX v2.77
- Updated Superuser v3.0.7
- Added HTC Stock Alarms, Notifications and Ringtones to the separate Media Package; converted all sounds to OGG Vorbis.
Fallout 3 Trailer @ 720p in H.264 - test file for HW decoding
F.A.Q.
I. Why would I want to install MildWild v2.9.5 Lite?
- It's smaller so it will fit on the Alpharev Oxygen r2 Hboot meaning that you will get a larger data partition and more space to install your applications. (Alpharev Oxygen r2 partition sizes: 100MB system, 5MB cache, 332MB data; Alpharev CM7 r2 partition sizes: 145MB system, 5MB cache, 287MB data)
- It stores apps and dalvik on sd-ext so you get even more space for your applications. On the downside, the ROM may become a bit slower.
- Alternatively, you can install the version which keeps dalvik on the internal memory.
II. So, how come MildWild v2.9.5 Lite is smaller?
- Some non vital system data and system applications have been removed from the instalation package.
III. Right, so what's missing?
- These applications have been removed:
1. GMmail (Gmail.apk) - you can install it from the Market so it will go to sd-ext instead on the internal memory, hence you get more space;
2. Google Talk (Talk2.apk) - well, you have to make some sacrifices; however, I think you can install it manually from the apk package but I haven't tried myself;
3. Google News & Weather Widget - you can find a whole range of simmilar applications on the Market; or you can probably install it from the apk package but I haven't tried;
4. Stock 3D Gallery (Gallery3D.apk - I recommend QuickPic from the Market instead; it is smaller and does the same job better;
5. Stock Music Application - there is a whole range of media players on the Market; this however will break the ability to play music through the Desk Clock Application; however, you can probably install it manually from the apk package but I haven't tried;
6. Typological Clock (TypoClock.apk) - you can most likely find something simmilar on the Market; or you can probably install it from the apk package but I haven't tried;
7. Timer Widget - you can most likely find something simmilar on the Market; or you can probably install it from the apk package but I haven't tried;
8. File Manager (FileManager.apk) - you can find a whole range of File Manager applications on the Market;
9. Compass (compass.apk) - you can find a whole range of Compass applications on the Market;
- Launcher 2 has been replaced with GO Laucher EX; it's smaller, faster and I think generally better; then again, it's a matter of taste;
- All alarms, notifications and ringtones have been removed from the installation package. Instead, you can download the media package attached (see link further down), unzip it, and place the folder as it is anywhere on the FAT32 partition of your SD card and it will work just the same. The system will automatically detect these files on the SD card.
- All PicoTTS (voice output) data files have been removed from the installation package. Instead, you can either download them from the Market or download the svox package attached (see link further down), unzip it, and place the folder as it is in the root of your FAT32 partition of your SD card and it will work just the same. The system will automatically detect these files on the SD card.
IV. So what's the point if I still want these applications?
- Whatever you install from the Market will go to sd-ext so you will have more space on the internal data partition for additional applications. If you keep the dalvik internal then the application data will stay on the internal memory but you still get some benefit as the apk still goes to the sd-ext.
- On the downside you can't get some of them on the Market and they may not install properly from the apk package so if you want to use exactly these apps then you'd better stick to the fully fledged MildWild ROM.
- However, you can download the apps package attached (see link futher down) and play with the apk files.
DISCLAIMER
ALL CREDITS go to MildWild.
I am NOT a delevoper and I have NOT developed any of the apps, bins, libs, etc. included inside the instalation file. I simply unpacked MildWild's zip file and removed/replaced a couple of things here and there, and then repacked it back. You can ask me questions but I cannot guarantee that I will be able to answer. Also, the responsability of installing the ROM and playing around with it lies 100% with YOU!
Download Links
MildWild v2.9.5 Lite Final (with dalvik on sd-ext)
MildWild v2.9.5 Lite Final (with dalvik on internal memory)
Media Package including HTC Stock Sounds - OGG Vorbis (alarms, notifications, ringtones)
Apps Package (all apks that have been revomed from the installation)
SVox Package (PicoTTS data files)
MildWild v2.9.5 based on Oxygen (The Original)
NOTE! This is the LAST and FINAL version of my modified ROM.
As you may or may not know, to concentrate on the CyanogenMod version MildWild has stopped development on the Oxygen version of this ROM for the foreseeable future (see here: http://forum.xda-developers.com/showpost.php?p=22130173&postcount=2568). As such, this is also the last update from me.
Do check out the ORIGINAL!
MildWild v2.9.5 based on Oxygen
Removing a launcher and replacing it with another one doesn't make it a custom ROM. This could all be put into a flashable ZIP which has to be flashed on top of a stock MildWild ROM, so that the update-script removes all the APKs. But another topic just for a modified ZIP only causes a lot of confusion.
what is the point of this ? everyone could make this.
Chaosz-X said:
Removing a launcher and replacing it with another one doesn't make it a custom ROM. This could all be put into a flashable ZIP which has to be flashed on top of a stock MildWild ROM, so that the update-script removes all the APKs. But another topic just for a modified ZIP only causes a lot of confusion.
Click to expand...
Click to collapse
Please read the description...
expler said:
what is the point of this ? everyone could make this.
Click to expand...
Click to collapse
Constructive comments would be very much appreciated...
Not a fan PERSONALLY of this "I can unzip, remove a few apps, then re-zip and post as a new rom" attitude, but it's a case of supply and demand I suppose. At least the OP has had permission from MildWild.
Screen ? ^_^
lolitz said:
Screen ? ^_^
Click to expand...
Click to collapse
Will do later on.
In any case, appart for the GO Launcher EX bits it looks exactly like MildWild - he's the BEST! (see link below)
MildWild v2.9.5 based on Oxygen
whats the point in making this a whole new thread?
it's some deleting/adding stuff to a zip file.. nothing else.
absolutely no need for this in my opinion, 'cause everyone can open a .zip file and delete stuff they don't want, and add stuff they want.
if we continue this road, we have 20 roms based on mildwild, and 20 different threads filled with the same questions over and over and over and over and over again.
horst0815 said:
whats the point in making this a whole new thread?
it's some deleting/adding stuff to a zip file.. nothing else.
absolutely no need for this in my opinion, 'cause everyone can open a .zip file and delete stuff they don't want, and add stuff they want.
if we continue this road, we have 20 roms based on mildwild, and 20 different threads filled with the same questions over and over and over and over and over again.
Click to expand...
Click to collapse
Please vote in the poll...
If people don't like it, then I'll remove it...
horst0815 said:
whats the point in making this a whole new thread?
it's some deleting/adding stuff to a zip file.. nothing else.
absolutely no need for this in my opinion, 'cause everyone can open a .zip file and delete stuff they don't want, and add stuff they want.
if we continue this road, we have 20 roms based on mildwild, and 20 different threads filled with the same questions over and over and over and over and over again.
Click to expand...
Click to collapse
whats with the hate? it saves people time of doing it themselves if they dont know what system related stuff they can remove without causing problems
it gives more space and mildwild allowed him to do it.
if you dont want it dont use it, im sure some people would be happy to use it.
as fopr putting it on the same thread? why would he hyjack an ops thread with different work. i doubt people would but it could be seen as trying to take people away from the original ops rom or some people might be confused with it being by mildwild himself as its displayed in a rom dev format..
people need to chill out, leave the complaining to the other devs if they have an issue with it and everyone else concentrates on flashing.
i dont see you complaining about the many different varients of stock roms that are modified in a kitchen using the same kernel as every other rom and called something different.
i dont see you complaining of the clones of 3.5 sense roms that have had different apps added just to call it something different.....
grow up
The ROM was great... That's very rude of you guys
He's just trying to help the people that don't know that much about ROM's.
OP, please continue what you're doing, it's great!
I'm already using your ROM
Guizzoni said:
The ROM was great... That's very rude of you guys
He's just trying to help the people that don't know that much about ROM's.
OP, please continue what you're doing, it's great!
I'm already using your ROM
Click to expand...
Click to collapse
Thanks...
Some people really put you down sometimes...
Rastaman-FB said:
whats with the hate? it saves people time of doing it themselves if they dont know what system related stuff they can remove without causing problems
it gives more space and mildwild allowed him to do it.
if you dont want it dont use it, im sure some people would be happy to use it.
as fopr putting it on the same thread? why would he hyjack an ops thread with different work. i doubt people would but it could be seen as trying to take people away from the original ops rom or some people might be confused with it being by mildwild himself as its displayed in a rom dev format..
people need to chill out, leave the complaining to the other devs if they have an issue with it and everyone else concentrates on flashing.
i dont see you complaining about the many different varients of stock roms that are modified in a kitchen using the same kernel as every other rom and called something different.
i dont see you complaining of the clones of 3.5 sense roms that have had different apps added just to call it something different.....
grow up
Click to expand...
Click to collapse
Dito!
Thank you for the support.
I voted yes. Do not delete this thread!
Oh, I do get annoyed by all the Sense ROMs too. With all that ROMs out there it's pretty hard to see the difference, so that's a mess too IMO.
Chaosz-X said:
Oh, I do get annoyed by all the Sense ROMs too. With all that ROMs out there it's pretty hard to see the difference, so that's a mess too IMO.
Click to expand...
Click to collapse
Please vote in the poll...
do3in said:
I voted yes. Do not delete this thread!
Click to expand...
Click to collapse
Do you know if we can get Android in Romanian? I would like to add it to this trimmed ROM.
I'm a little bit confused with the poll:
Do you think this trimmed ROM is useful = yes
or I should take it off = no
how to vote yes and no...? hehe
anyway good luck with the rom and thanks for sharing
Has anyone tried the supercharger V6 on the sidekick 4g? Is it me or do I just not notice nay significant difference on the sidekick 4g? My friend has tried it on his Galaxy S2 and I have noticed its gotten alot more snappy, but mine just seems the same as it was before.
I'm gonna second your post.. I actually wanted to ask the same thing.. I got supercharger v6 a few days ago too and haven't noticed any difference at all.. I saw some posts about people saying it improved their performance a lot. I have the widget and it seems like its working, i'm getting the right minfrees and all that.. Tried aggressive 1. but it doesn't seem to be any faster or anything.. but it wasn't that bad to begin with so maybe thats why?
check out:
http://forum.xda-developers.com/showthread.php?t=1187151
first of all, you need supercharger update 9, secondly, if you are on stock firmware and running the boot script to make supercharger permanent, it doesnt really make it permanent. if you are on stock firmware, you need a root file browser that allows you to remount system as read/write and also allows you to create new folders. browse to /system/etc, remount system as read/write, create a new folder, and name it init.d and supercharge will then be completely permanent and have total system integration. if you are on a custom rom, you should already have init.d but you can check to make sure. i am running update 9 on stock firmware and i ran options 7 and 13. it makes a huge difference.
vikramkhalsa said:
I'm gonna second your post.. I actually wanted to ask the same thing.. I got supercharger v6 a few days ago too and haven't noticed any difference at all.. I saw some posts about people saying it improved their performance a lot. I have the widget and it seems like its working, i'm getting the right minfrees and all that.. Tried aggressive 1. but it doesn't seem to be any faster or anything.. but it wasn't that bad to begin with so maybe thats why?
check out:
http://forum.xda-developers.com/showthread.php?t=1187151
Click to expand...
Click to collapse
Are you running any rooted/running any Custom Roms/or stock on your SK4G?
sidekick_fanatic said:
first of all, you need supercharger update 9, secondly, if you are on stock firmware and running the boot script to make supercharger permanent, it doesnt really make it permanent. if you are on stock firmware, you need a root file browser that allows you to remount system as read/write and also allows you to create new folders. browse to /system/etc, remount system as read/write, create a new folder, and name it init.d and supercharge will then be completely permanent and have total system integration. if you are on a custom rom, you should already have init.d but you can check to make sure. i am running update 9 on stock firmware and i ran options 7 and 13. it makes a huge difference.
Click to expand...
Click to collapse
Are the instructions the same when running the update9? Do you have to remove the .pdf extension like removing .txt in update8 before running script or does it not matter? Also what rom are you running?
not sure about the pdf extension. go to the supercharge thread and look for update 9. when you download it, you will figure it out. i just cant remember. see my signature for what firmware i am on.
yeah, I was running gingerclone v2.. but it was already running smooth and not slow so maybe thats why i didn't really notice? I'm on glorious overdose 2 now though so I'm going to try again on that. I also think I was using update 7, not 9 so maybe that will make a difference when I put the right one now..
Please comment
Sent from my HTC One XL using xda premium
Devs say yes cuz it splits app in half. I dont notice any difference.
Typically, a rom is supposed to be odexed for smoother and faster loading of apps into memory. Each app(.apk) has a corresponding sister file(.odex). When a app is opened, called to memory, the. Odex has the information needed to start loading the app. A rom that is deodexed has only the.apk file. So when it is opened/called to memory the information to load the app is inside of the .apk and and must be pulled from it to begin loading it into memory. So at this level you would probably ask "then why are most custom roms deodexed?" People really started deodexing roms for themability. It is much much simplier to theme roms that are deodexed. It wasnt for faster speeds but for easier customization. So "themers" could build custom themes instead of have to build a whole themed rom. So now on one side you have odexed for speed, or deodexed for customizations? Well the brilliant devs in the android world came up with pretty good solutions to even out the field. In most any custom deodexed, youll see that they zipalign all the .apks in boot. While boot up time will be slightly longer, zipaligning optimizes every. Apk on every reboot which basically optimizes the information in each. Apk so when it is called to memory, the information is at the ready and quickly loaded witbout the need of a. Odex file. I kinda rambled here but wanted to answer this one as best i could because i kno many people wonder, and not a whole lot always ask. Hope this helps explain a little bit for anyone curious. :beer:
Sent from my SPH-L710 using Tapatalk 2
Thanks very much for the explanation. Often wondered about difference. Good job.
Thanks for explaining mate. Are there any statistical data or experimental data on the performance of two idenrical roms one is deodexed and zipaligned while the other is odexed?
Thanks for the explanation. I have been flashing roms for a while now and haven't really understood the difference.
Thanks for all info
thanks alot for explaint this in detail it help novice like me alot ....
thanks once again.....
18th.abn said:
Typically, a rom is supposed to be odexed for smoother and faster loading of apps into memory. Each app(.apk) has a corresponding sister file(.odex). When a app is opened, called to memory, the. Odex has the information needed to start loading the app. A rom that is deodexed has only the.apk file. So when it is opened/called to memory the information to load the app is inside of the .apk and and must be pulled from it to begin loading it into memory. So at this level you would probably ask "then why are most custom roms deodexed?" People really started deodexing roms for themability. It is much much simplier to theme roms that are deodexed. It wasnt for faster speeds but for easier customization. So "themers" could build custom themes instead of have to build a whole themed rom. So now on one side you have odexed for speed, or deodexed for customizations? Well the brilliant devs in the android world came up with pretty good solutions to even out the field. In most any custom deodexed, youll see that they zipalign all the .apks in boot. While boot up time will be slightly longer, zipaligning optimizes every. Apk on every reboot which basically optimizes the information in each. Apk so when it is called to memory, the information is at the ready and quickly loaded witbout the need of a. Odex file. I kinda rambled here but wanted to answer this one as best i could because i kno many people wonder, and not a whole lot always ask. Hope this helps explain a little bit for anyone curious. :beer:
Sent from my SPH-L710 using Tapatalk 2
Click to expand...
Click to collapse
Best explanation of odexed vs deodexed. Deserves to be a sticky IMO.
18th.abn said:
Typically, a rom is supposed to be odexed for smoother and faster loading of apps into memory.
Click to expand...
Click to collapse
No, well not for the reasons you describe anyway. DexOpt is run to optimize the dex file (ie. the Java/Dalvik byte-code). See the link below for more information.
http://www.netmite.com/android/mydroid/dalvik/docs/dexopt.html
18th.abn said:
Each app(.apk) has a corresponding sister file(.odex). When a app is opened, called to memory, the. Odex has the information needed to start loading the app.
Click to expand...
Click to collapse
Well, it's just an optimized version of the classes.dex file from the APK so sure. The dex file also has the information required, just in a slightly less optimal format.
18th.abn said:
A rom that is deodexed has only the.apk file. So when it is opened/called to memory the information to load the app is inside of the .apk and and must be pulled from it to begin loading it into memory.
Click to expand...
Click to collapse
With zipalign that you mention below, resources in the APK can be loaded directly from the APK without the need to decompress everything. This is because zipalign uses padding in the zip file to make sure each resource starts at an address that aligns with a 4 byte boundry. That allows Android to allocate it directly.
18th.abn said:
So at this level you would probably ask "then why are most custom roms deodexed?" People really started deodexing roms for themability. It is much much simplier to theme roms that are deodexed. It wasnt for faster speeds but for easier customization. So "themers" could build custom themes instead of have to build a whole themed rom.
Click to expand...
Click to collapse
True. The argument that a deodexed rom is slower is still pretty shaky though.
18th.abn said:
So now on one side you have odexed for speed, or deodexed for customizations? Well the brilliant devs in the android world came up with pretty good solutions to even out the field. In most any custom deodexed, youll see that they zipalign all the .apks in boot. While boot up time will be slightly longer, zipaligning optimizes every. Apk on every reboot which basically optimizes the information in each. Apk so when it is called to memory, the information is at the ready and quickly loaded witbout the need of a. Odex file.
Click to expand...
Click to collapse
Zipaligning on boot is mostly pointless for ROMs built from source or ROMs that have not been modified since they will then already have been zipaligned during the build process. It is in no way a replacement for DexOpt.
Also, do note that DexOpt will run at boot and produce odex-files for every classes.dex in every APK and put them in dalvik-cache. That includes all the APK files in /system/app if the ROM is deodexed (or built without being DexOpt:ed) as well as all app that the user has installed from the Play Store etc. If the APKs on the device ever changes dalvik-cache will be updated with the new odex by DexOpt. In other words, you gain the customization benefit of a deodexed APK while at the same time get to enjoy the optimization of odex files by sacrificing a little storage space (due to keeping both the dex and odex files).
Can someone please explain the logic behind the argument that odexed ROMs are faster? I have yet to see a proper explanation that makes sense.
blunden said:
No, well not for the reasons you describe anyway. DexOpt is run to optimize the dex file (ie. the Java/Dalvik byte-code). See the link below for more information.
http://www.netmite.com/android/mydroid/dalvik/docs/dexopt.html
Well, it's just an optimized version of the classes.dex file from the APK so sure. The dex file also has the information required, just in a slightly less optimal format.
With zipalign that you mention below, resources in the APK can be loaded directly from the APK without the need to decompress everything. This is because zipalign uses padding in the zip file to make sure each resource starts at an address that aligns with a 4 byte boundry. That allows Android to allocate it directly.
True. The argument that a deodexed rom is slower is still pretty shaky though.
Zipaligning on boot is mostly pointless for ROMs built from source or ROMs that have not been modified since they will then already have been zipaligned during the build process. It is in no way a replacement for DexOpt.
Also, do note that DexOpt will run at boot and produce odex-files for every classes.dex in every APK and put them in dalvik-cache. That includes all the APK files in /system/app if the ROM is deodexed (or built without being DexOpt:ed) as well as all app that the user has installed from the Play Store etc. If the APKs on the device ever changes dalvik-cache will be updated with the new odex by DexOpt. In other words, you gain the customization benefit of a deodexed APK while at the same time get to enjoy the optimization of odex files by sacrificing a little storage space (due to keeping both the dex and odex files).
Can someone please explain the logic behind the argument that odexed ROMs are faster? I have yet to see a proper explanation that makes sense.
Click to expand...
Click to collapse
De-odex is only slower in first ever boot time or the first boot time after dalvik cache is cleared. You seem to know enough about it to understand why that is. And if not, 18th.abn's post does explain why pretty well. It is not slower in terms of everyday operation.
exad said:
De-odex is only slower in first ever boot time or the first boot time after dalvik cache is cleared. You seem to know enough about it to understand why that is. And if not, 18th.abn's post does explain why pretty well. It is not slower in terms of everyday operation.
Click to expand...
Click to collapse
Exactly my point. I see people and articles stating that there is a performance difference but I just don't see why that would be. To me it seems to be something that has been repeated enough times to become a "fact".
What if RAM is very low on a phone with limited cpu ?
DoctorPINK said:
What if RAM is very low on a phone with limited cpu ?
Click to expand...
Click to collapse
It will be slow but will have nothing to do with odex vs deodex.
18th.abn said:
Typically, a rom is supposed to be odexed for smoother and faster loading of apps into memory. Each app(.apk) has a corresponding sister file(.odex). When a app is opened, called to memory, the. Odex has the information needed to start loading the app. A rom that is deodexed has only the.apk file. So when it is opened/called to memory the information to load the app is inside of the .apk and and must be pulled from it to begin loading it into memory. So at this level you would probably ask "then why are most custom roms deodexed?" People really started deodexing roms for themability. It is much much simplier to theme roms that are deodexed. It wasnt for faster speeds but for easier customization. So "themers" could build custom themes instead of have to build a whole themed rom. So now on one side you have odexed for speed, or deodexed for customizations? Well the brilliant devs in the android world came up with pretty good solutions to even out the field. In most any custom deodexed, youll see that they zipalign all the .apks in boot. While boot up time will be slightly longer, zipaligning optimizes every. Apk on every reboot which basically optimizes the information in each. Apk so when it is called to memory, the information is at the ready and quickly loaded witbout the need of a. Odex file. I kinda rambled here but wanted to answer this one as best i could because i kno many people wonder, and not a whole lot always ask. Hope this helps explain a little bit for anyone curious. :beer:
Sent from my SPH-L710 using Tapatalk 2
Click to expand...
Click to collapse
Cheers mate, I was wondering what the heck is this odexed/deodexed and you just explained it smoothly.
Thanks again
I posted this in the I9300 forum but i got no responses....
I suppose this could work on all 1gb ram devices since these are non device specific tweaks,just optimised for the S3.
Intro:
Hi all...
I got a bit tired of restoring all of my build.prop and init.d tweaks every time i flashed i rom so i made a handpicked collection of the tweaks i use.
Since this may be useful to others aswell i though i need some testers to confirm everything goes ok after this...
Can anyone help me?
When it's confirmed working i'll update this to a full thread with how to and everything. [done already because of low demand.]
By the way,can't test myself because i already have those enabled.
I just want to see if the cwm file installs correctly and if values and permissions are set right.
Instructions
Flash through recovery and delete dalvik and cache.
Please do post back,I need feedback since this is the first flashable mod i created.
Also make a backup before installing,i don't know if this will work correctly on your S3.
Thanks!
Finally it is reccomended to use this to have full effect and eliminate redraws.
Fast.Simple.Working.
Just use the instructions and you're done.
http://forum.xda-developers.com/showthread.php?t=1869663
P.S. Nothing of this is mine,i just made the package becaue i don't want to install them manually every single time.
All credits go to their owners.
Anyone tested it?
Seems to make things a bit smoother.
Sent from my SGH-T999 using xda app-developers app