Related
Hello,
I was wondering, what are the advantages of deodexing, aside from theming?
I've done some tests with my everyday stock ROM and found an odex ROM was faster. I understand that odex files are basically classes.dex, but specifically made for my platform, Android version and is not compressed, thus accelerating the start times.
I went as far as pushing the system apps updates in /system directly (by hand, I can tell you it gets old fast). But I still had low memory in /data. Then I remembered, automatic odex files are stored in dalvik-cache, and thus, when Maps, which has a very big odex file or so, first starts, even if it's on /system, you end up still needing space in /data to start.
So I searched how I could hand-do these odex files, and came across dexopt-wrapper. I loaded it up on my phone, and started odexing all these system apps that used to be odexed.
All in all, you lose room in /system (because odex+apk is slightly larger than the apk, but you're not supposed to have /system writable anyway), or you lose valuable space in /data, where you could put all your apps.
Basically:
I backed up my stuff with Titanium (after cleaning the cache). I was on Geo411m's ROM. I had around 25MB left on my phone.
I then reflashed FRG33 from the PASSIMG.zip
then updated with the FRG83D OTA (straight from Google, not through update.zip)
I updated all system apps through the Market
I used rageagainstthecage to shell root, to read the system and data partitions
I used dexopt-wrapper to create odex files for all the updated apks I had
I pushed everything in /system
Finally, I restarted. Before this, I booted Amon-RA's recovery to clear all the user data
I rooted (permanently this time), restored all my apps through Titanium Backup. I had 65 MB left. That's a 40 MB difference, just by odexing.
So now I wonder, knowing I don't plan on theming, is deodexing useful outside of this, and should I give up some space for something that eluded me?
Sorry for the lonnnnnng post
Thanks!
I'm not aware of any benefit of deodexeding, other than theming.
i've heard people say there is definitely a performance difference between the two, but i really dont know from personal experience. it probably doesnt matter for general usage...
I believe you're right, deodex takes up more of your internal space, which to me is a problem
Sent from my Nexus One using XDA App
When I first flash a new rom from recovery the odex rom will start faster,but I cant feel any difference between odex and deodex rom on speed when my defy is on.
Aside from the first load, deodexed system runs at the same speed as odexed, or with negligible differences (not 100% sure if system-odexed files that are created in Dalvik-cache are the same as .odex that are in the apks).
The disadvantage of deodexed system is extra size of Dalvik-cache. While it can be quite a difference for those using N1's tiny internal space w/o any sort of A2SD solution, it's negligible for those running A2SD or on phones with proper internal memory size.
The advantage of deodexed system is being able to modify the apps themselves, and the framework. In addition to theming, it allows for different kinds of modifications - like trackball wake, or RTL (Hebrew/Arabic) framework patching.
Quite an old thread you managed to dig...
kingdragonfly said:
When I first flash a new rom from recovery the odex rom will start faster,but I cant feel any difference between odex and deodex rom on speed when my defy is on.
Click to expand...
Click to collapse
Way to bump a 1.5 years old thread, lol.
Theshawty said:
Way to bump a 1.5 years old thread, lol.
Click to expand...
Click to collapse
maybe because you all people tell noobs to serch and don't ask. and when i find 4 years old thread is still very usefull
Sent from my Nexus 5 using Tapatalk
magik300 said:
maybe because you all people tell noobs to serch and don't ask. and when i find 4 years old thread is still very usefull
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
You felt it was worth a two year bump just to convey that? Oh, ok.
Sent from my HTC One using Tapatalk
I don't know about a 2 year bump, but a 1 year bump to agree that this is a nice simple thread that is exactly what it says on the tin.
Lol
Lol
Is there any good resource I can be pointed to learn about the difference between Odex/Deodex?
nice info from this thread, thanks!
Hi
I would like to start automatically my Htc n1 when i put in the charger.
There are some methods on the internet,for some other phones.
Can someone tell me wich and how the folder i must modify?
My phone doesn't start when it's plugged in and take the battery out and put it back(i dont know why).
Sorry to write to you here, but I see you are very good at what you do.
I thought you could help me.
Thanks
First of all sorry for my english, i'm not a native english speaker.
I'm a new user, but a frequently anonymous visitor.
I finally decided to apply a custom ROM (FroyoMod 2.6.0) to my Milestone.
The problem is the following:
I have noticed that since i installed this particular ROM my /data directory is getting consumed by something.
I have not installed new apps, im just testing it and by some reason since yesterday i have lost more than 5MB.
For example since i started writing this post i have lost 100K more...
Perhaps is a log file that is consuming my /data directory but i can't seem to find the guilty one.
Has anyone experienced this problem?
Thanks in advanced for your help.
Try using busybox and 'find /data -mmin -5' to discover the files that are changing...
Thanks for the info i found that the files that are getting bigger and bigger are those under /data/logger/AOL_*
I'm a linux user, but i'm not sure if this logs files are important, because one solution that comes to my mind is just to empty those logs, i mean they are just logs after all.
I've decided that i will just clean those logs and for that i created a tiny bash script that cleans those logs, so far seems that i'm not losing to much memory.
Huge thanks to Hashcode for all his hard work thus far, what with the totally ingenious Safestrap and his latest victories with CM9. I hope this helps somebody out and that at least *someone* out there thinks this is as cool as I do.
Pushing OK+Backspace will force the console to kick you out back into the recovery, in case you get stuck. Keep in mind that the console is pretty powerful but also really dangerous if you don't know exactly what you're doing. Although, you'll never learn how to do anything awesome unless you get your hands dirty.
The Microphone button is now ESC, command history works, tab-autocompletion works via either the hardware Tab key or by pushing OK+i, and you can scroll back up through the text one line at at time with Alt+Up or Alt+Down or in chunks of 8 lines with Shift+Up and Shift+Down. Home is the home softkey, or the Search button on the keyboard, and End is the Power button. You could also push OK+A or OK+E for Home and End, respectively.
Make sure you uninstall Safestrap and then remove the application before you install this one. I just jacked Hashcode's .apk and stuffed my new binaries inside the .zips, if you don't want to bother with uninstalling and reinstalling the .apk, you can extract the recovery.zip and 2nd-init.zip from the archive and push them both to /system/etc/safestrap and reboot. Enjoy.
..............................................................
EDIT: I finally got my act together and put my modified sources on github:
http://github.com/buddyrich/android_bootable_recovery
............…………………………………………
EDIT: Just finished up my latest update to this branch of Hashcode/Koush's work. Added:
-Use numbers on the hardware keyboard to select menu entries. Got really tired of scrolling around and thought this would make things a bit quicker.
-Scrolling/repeating keys. Holding in for longer than about half a second will repeat even faster now, similar to a real terminal on a PC for instance.
-vim statically compiled to avoid the need for any external libs (ie: having /system or /systemorig mounted). Full color support and syntax is working great now; the only thing missing is background colors, which will be tricky to implement.
-a $HOME directory is now made at /emmc/safestrap/home. This is set up when the .apk is installed; it isn't necessary so it can be deleted if you want, but it is required if you want to have a persistent command history in bash as well as the ability to customize your .bashrc and .vimrc files. Most of you won't really know what this means, but if you do you'll probably appreciate it.
-Revamped all the menus and made everything look a little cooler. Let me know what you guys think! I got rid of the highlighting box that shows which menu entry is currently selected and changed it to simply highlight the text in white to distinguish from the green/yellow menus; I think it's a little easier on the eyes but some feedback would be cool. It wouldn't be very hard to allow the users to customize the menu colours themselves via external files placed on the sdcard/through a menu option.
-Fixed the issue some people were having with restoring to /systemorig; there aren't any more issues mounting/unmounting /systemorig or /system during a restore
-Probably many more things I've forgotten
-.bashrc tweaks, fixed a few aliases, nothing major
-You can flash updates from either safe or non-safe mode now, look in the advanced menu. Really though, be careful and remember to make backups of your /systemorig partitions. Don't say I didn't warn you! Guaranteed, someone out there will complain that they broke their phone so I was pretty hesitant to let that out in the wild, but I know I've found myself in the situation where I could've used it so there you have it.
Let me know if anyone finds any issues, I've done a pretty thorough job testing this over the last few weeks but there's always something to be missed. The new .apk is over the size limit to be posted in the forum due to the new bash and vim binaries and the vim runtime files, so you can download the new version from my dropbox here:
Safestrap (Tweaked) v1.08e for Droid 3
http://db.tt/CArenxr7
EDIT:
----------------------
Just finished thoroughly testing my latest release and think it's ready for human consumption! Another batch of sweet additions:
1) Proper implementation of /systemorig flashing while in non-safe mode... without any modifications needed to the updater-script present in any flashable zip. Even if the updater-script inside the. zip file you are flashing targets "/system", if you confirm it about three times in non-safe mode it will know to copy the files onto /systemorig to replace your stock system.
You can install Gingerbread-based ROMs such as MavROM 3.5 to the stock /system partition while in non-safe mode via the Advanced menu. Safestrap will backup and afterwards restore it's own files needed to ensure you can still get back in after a flash of the /systemorig partition. Note that flashing your original /system partition with an ICS ROM won't work yet because they need custom init.*.rc scripts in place during the 2nd-init process; this isn't hard to do but I was getting anxious to get something out so it'll have to wait until next time.
2) Redesign of the layout for the menus, much more organized
/* 3) Allow for rebooting directly into the recovery, either via the shell command "reboot recovery" or through the Reboot Menu */
// EDIT: Seemed to be causing some users to persistently boot straight into the recovery so on the backburner for now
4) Allow for custom colors for either safe or non-safe mode; to change the colors for now you have to execute a few little shell commands. Here's an example to change safe mode colors to a blue-grey and then non-safe mode colors to maroon:
Code:
s_rgb 139 137 137
ns_rgb 127 34 10
cc
Basically, "s_rgb" sets the colors for safe-mode and the three arguments (139 137 137 in the above example) are the codes for the red, green and blue components of the end result; you can look up rgb color codes for your own custom colors. "ns_rgb" is the command for non-safe colors. "cc" just tells the recovery to update the colors to whatever they've been changed to. If you don't like what you've done and just want to revert back to the stock ones, you can just wipe your /cache partition and they'll go back to normal.
Eventually I thought it'd be cool to be able to do this via the recovery UI but I haven't been able to envision how it would work yet.
5) Added background colors/highlighting in the console now, makes vim look a lot prettier. If there's anyone out there who cares, I preinstalled a few plugins (MiniBufExplorer, MRU (most recently used files), bash-style path completion, etc.)
Also, changed the cursor from the big ol' ugly white block to an easier-on-the-eyes one-character underline.
Yeah, it's overboard.
6) Much faster backups and somewhat quicker restores now. I clocked full backups (including /systemorig and ~350mb /data partition) at around 2 mins and full restores at around 7 minutes. Also fixed up the progress bars so they give a more accurate representation of how much longer the backup/restore will be.
7) Moved $HOME and other misc. Safestrap files to /cache instead of the /sdcard
8) Probably half a dozen other OCD details that I've already forgotten.
Test it out and let me know what you guys think!
As always, sources are posted on my github:
https://github.com/buddyrich/android_bootable_recovery
You can get the new .apk here:
Safestrap (Tweaked) 1.08f for Droid 3
http://db.tt/u4vAwv2u
i need this about 6 hrs ago lol.
Quite useful mate cheers.
=smc
Thank you so much for sharing this file. Your work is greatly appreciated.
This is a nice little(big)addition to safestrap! Thanks for adding it in!
I can't think of any better use for Christmas Eve than coding a bash console into recovery! Merry Christmas to the D3! Thank You!
Sounds good. I haven't grabbed it yet (as I need to keep my own customised Safestrap for ME863 nandroid support) but one thing I'd note is that the "OK" button (i.e. trackball click) is used for "Control" in Console+, and the console in Amon_RA's HTC Dream recovery. That saves you losing the @^ key.
Edit: Also: Source? Sounds like something that could be pushed upstream. I always found the console in Amon_RA's recovery very useful, missed it on my current device, when I didn't have a computer with ADB handy.
TBBIe,
I have an XT860, so I'm curious to see if this would work on your ME863. I remember seeing a post of yours a few months ago mentioning issues with the preinstall and data partitions (I think it seemed that the data partition was extended into the first bytes of the preinstall partition, rendering it unmountable during init) that should also have affected the XT860, but I have never experienced any issues with the partitions since Hashcode released v1.06.
I'll commit my sources to github shortly so you have take a look.
I am trying to get through the preinstall problem myself after flahing xt883 and I was wondering if I could fix it with this?
Sent from my DROID3 using xda premium
Hey there guys, Village Idiot here...I've been successfully using Hash's SafeStrap for a while now and wanted to try this one out. What's the difference here? Just by looking at it, I can't tell. It seems better from what everyone is saying, but I have no idea how to utilize it. Would you mind dumbing it down for Simple Jack over here? Thanks.
redsox985 said:
Hey there guys, Village Idiot here...I've been successfully using Hash's SafeStrap for a while now and wanted to try this one out. What's the difference here? Just by looking at it, I can't tell. It seems better from what everyone is saying, but I have no idea how to utilize it. Would you mind dumbing it down for Simple Jack over here? Thanks.
Click to expand...
Click to collapse
It has a console option included, allowing you to run shell commands, which could potentially save your butt if used right.
Otherwise it the same
Sent from my XT860 using xda premium
Endoroid said:
It has a console option included, allowing you to run shell commands, which could potentially save your butt if used right.
Otherwise it the same
Sent from my XT860 using xda premium
Click to expand...
Click to collapse
Which it just did lmao..hash really needs to include this in his release!
Once again thanks for this mod it is PERFECT!
ovelayer said:
Which it just did lmao..hash really needs to include this in his release!
Once again thanks for this mod it is PERFECT!
Click to expand...
Click to collapse
Oh I'm sure I'll be damn thankful at some point. Made a point of installinng it
Sent from my XT860 using xda premium
Rick#2 said:
I have an XT860, so I'm curious to see if this would work on your ME863. I remember seeing a post of yours a few months ago mentioning issues with the preinstall and data partitions (I think it seemed that the data partition was extended into the first bytes of the preinstall partition, rendering it unmountable during init) that should also have affected the XT860, but I have never experienced any issues with the partitions since Hashcode released v1.06.
Click to expand...
Click to collapse
The difference is the other way 'round. The /data partition is extended backwards over the end of the /preinstall partition.
It doesn't cause problems during init, it was causing nandroid to fail mounting /system, and presumably would make switching to safe-mode fail (although I never tried)
My patch to fix this for nandroid was based on 1.06. The only way this could be 'fixed completely' in safestrap was if safestrap had had repartitioning code added at some point to resize /data back down and grow /preinstall to be large enough to hold a safe system. And Hashcode'd said he didn't have time or real inclination to do that, I thought.
I'm fairly strapped for time at the moment, so I don't know when I'll have a chance to look at the source and/or try out your build. But it's definitely somewhere in my TODO list. ^_^
orry for dumb question...ok, i wanr root my friends drodi 3,i think i know how to do it using the one click software the same i used to root my bionic,now to order to go into custom recovery i need install this apk file am i right,i mean is the same as in bionics bootstrap???? sorr y for noob qustion ,just that i dont speak english very well so i need be 100% sure what am doing thanks again,,btw do u know if the last wifi tethering works on this droid 3???
@rick#2
I'm running CM9 for daily use, but it's a bit wobbly at times, so I run 7.1 as the "non-safe" system. The big limitation to this is that I can't maintain the 7.1 fallback properly as hashcode deliberately disabled installing zips in non-safe mode.
If the wife has forgiven you by now - any chance of adding the ability to install .zips when in non-safe mode?
The alternative is to keep swapping bootstraps all the time, and all it takes is one late night sleepy mistake to stop the device booting one system or both.
I'm in favor of this as well, and have even mentioned it in the main SS thread. Could you add flashing to non-safe, but say with like 3 layers of warnings saying something like "THIS IS YOUR NON-SAFE, MAIN SYSTEM. FLASHING HERE CAN BRICK YOU."
This would be really nice because it's a PITA to keep switching strappers, albeit it easy, just a burden.
This is a great hack! I was considering doing this myself but you beat me to it! BTW, is your modified source code on github or somewhere like that, or can you send it to me if not? Thanks again!
Hey guys, sorry for the lack of updates to this thread. Been buuuusy.
I made an account on github about two weeks ago, but still haven't gotten the chance to upload the sources there, for those of you who are interested. I'll do that shortly.
I've got a new version I'll put up pretty soon, just need to do some more testing. I've enabled scrolling (ie: holding a key down to repeat it as opposed to requiring you to push it each time) but have to iron a few things out, and I'd like to add another menu enabling some of the (somewhat dangerous although useful if you know what you're doing) features some of you have requested.
Rick#2 said:
Hey guys, sorry for the lack of updates to this thread. Been buuuusy.
I made an account on github about two weeks ago, but still haven't gotten the chance to upload the sources there, for those of you who are interested. I'll do that shortly.
I've got a new version I'll put up pretty soon, just need to do some more testing. I've enabled scrolling (ie: holding a key down to repeat it as opposed to requiring you to push it each time) but have to iron a few things out, and I'd like to add another menu enabling some of the (somewhat dangerous although useful if you know what you're doing) features some of you have requested.
Click to expand...
Click to collapse
Dude you rock!
Sence you introduced your mod i have used nothing else..
The scrolling feature would be a HUGE improvement i agree ..
Also it would be nice if you could flash on the non-safe system as well..
Hope you can get er done..
I allways seem to watch this thread for updated..i really hope you can continue this adventure without the wife killing you lol..stay real!
---------- Post added at 12:45 PM ---------- Previous post was at 12:41 PM ----------
denpad2010 said:
orry for dumb question...ok, i wanr root my friends drodi 3,i think i know how to do it using the one click software the same i used to root my bionic,now to order to go into custom recovery i need install this apk file am i right,i mean is the same as in bionics bootstrap???? sorr y for noob qustion ,just that i dont speak english very well so i need be 100% sure what am doing thanks again,,btw do u know if the last wifi tethering works on this droid 3???
Click to expand...
Click to collapse
Hey bro if you want wifi teather look up android-wifi-teather..it works!
I have one of the Virgin Mobile models that has the smaller memory. I have been looking through these forums looking for a way to clear up the memory. It looks like there is simply not enough progress on this phone currently. What I would really like is a basic ROM replacement that does not have any of the HTC crap in it to make it leaner and use less space. Am I right that I need to wait for future developments? I just want to make sure I am not missing something. Is there any way to free up more space right now with existing hacks? I see lots of different posts in here, and when I think I am on to something, I read that it does not work on the Virgin Mobile phones, so I am getting confused. I was hoping somebody who knows my phone really well could hold my hand and tell me exactly what I can do to get some more free space. I am familiar with a lot of the tools, and have rooted and installed recovery on my Kindle Fire, and on my Ouya. I have rooted an old LG phone, but that was cake compared to what I am reading for this phone! Thank you!
Probably the best you can do for now would be to flash a write protection removed kernel, remove as much uneccessary HTC and carrier bloat as possible, and then use an app from the Play Store called System App Manager to turn most of the apps you install into system apps, thereby using unused space on /system instead of your internal storage. My advice is to make a TWRP backup before converting any apps, because some apps will not act right after being moved to /system, so just do a process of elimination/trial & error until you figure out which apps can be moved without causing problems. When you figure out which apps act up, restore your backup and re-do the process without converting the unruly apps.
You also might want to flash Raptor Rom, as it's probably the smallest rom available, leaving tbe most empty space for those apps you move. Someday we'll get a rom/kernel that will allow the moving of apps & thier data to an sd partition, till then this is probly your best bet.
sent from a device
huggs said:
Probably the best you can do for now would be to flash a write protection removed kernel....You also might want to flash Raptor Rom, as it's probably the smallest rom available
Click to expand...
Click to collapse
Great! Can anybody point me in the right direction for some good/updated directions on performing each of these? Thank you!
jrburke99 said:
Great! Can anybody point me in the right direction for some good/updated directions on performing each of these? Thank you!
Click to expand...
Click to collapse
Firstly, if you haven't done so already: Follow this
Then go grab the download from whatever kernel you want to use thread or grab RaptorROM here. RaptorROM already includes a version of @Pattyboi's kernel, but you can always flash the newer kernel (which he put up last night?) on top.
Drop whatever files you plan on flashing onto the phone, or the sdcard. Reboot into TWRP (volume down and power button when phone's off then select Recovery), tap install, find the .zip or .img to flash, tap, then Swipe to Install/Flash
Hello,
because of the stupid bluetooth behaviour on Android Pie (see here), I am seriously concidering downgrading my N6 back to LOS 15.1
I know I can install LOS 15 on the system partition using TWRP. But what about the data partition? Have there been changes between 15 and 16, that would prevent to use the same data partition or to restore the data partition after downgrading? I would prefer not having to re-install every app after downgrading.
Sorry, but you always have to clear data when going backwards.
You can hope for Google's app backup, which only works some of time for me. Or bring out the old Titanium app - though even that isn't guaranteed to always do the right thing, so you need to be careful what you restore.
I guess this means, creating a backup with TWRP, installing LOS 15.1, and restoring data only from the backup won't work, will it?
No, it won't work. The problem is that different versions store data in different ways. Some roms, including LOS, have conversions from the old to the new. But never the other way.
runekock said:
No, it won't work. The problem is that different versions store data in different ways. Some roms, including LOS, have conversions from the old to the new. But never the other way.
Click to expand...
Click to collapse
Bummer.
I have taken a look at Titanium, and it claims to be usable for downgrading. Did you ever use it that way? Would I need the pro version, or would the free version be sufficient?
What exactly do you mean by different way of storing data? Different file systems? Different mount points? I am trying to look at this from a Linux user's point of view: what about manually creating a tar file of the data partition, and untar this package after downgrade? That way it would not matter what file system was used before and which file system is used afterwards, and the mount point wouldn't matter neither.
dvdram said:
Bummer.
I have taken a look at Titanium, and it claims to be usable for downgrading. Did you ever use it that way? Would I need the pro version, or would the free version be sufficient?
What exactly do you mean by different way of storing data? Different file systems? Different mount points? I am trying to look at this from a Linux user's point of view: what about manually creating a tar file of the data partition, and untar this package after downgrade? That way it would not matter what file system was used before and which file system is used afterwards, and the mount point wouldn't matter neither.
Click to expand...
Click to collapse
I haven't used Titanium for years, but my impression is that it works most of the time (and free should be fine). Probably highest risk of problems when restoring system settings, and less with ordinary apps. I've gone the hard way and only saved my user files.
Different ways of storing data: no, usually it is not big things like file system. More like a myriad of small changes: new file format of a database, new name for a setting, some file moved to another directory, etc. etc.
runekock said:
Different ways of storing data: no, usually it is not big things like file system. More like a myriad of small changes: new file format of a database, new name for a setting, some file moved to another directory, etc. etc.
Click to expand...
Click to collapse
Exactly a new database version is the reason why you can't downgrade
Thanks for explaining!
It wouldn't be hard to reinstall all the apps after installing LOS 15, Google PlayStore does this for you. But I hate to input all passwords and app settings again, that takes ages! Not every app offers to export its settings and options. Of course I could use my Google account for this, but if I wanted to be in Google's hands that much, I wouldn't use LOS in the first place. Play Store is the only thing I need from Google to install app. Thanks for all the other Google services, but: NO thanks!
I think, it would be a great idea if there was some possibility to export all those setting to a local and version indipendend file on your PC, maybe using adb, so that you can restore each setting and option later, no matter which LOS version you are using.
I tried LOS 15.1 yesterday, but the sound issue / bug is the same. So guess I would have to go back to LOS 14.1, because I know that 14.1 does not show this stupid behaviour. My tablet is working with 14.1 and BT behaves as expected and wanted there. And I remember my Nexus doing so on 14.1 as well.
Being forced to downgrade to LOS 14.1 because of this stupid idea by Google is totally frustrating. Either I am forced to live with every bug in 14.1 that is not developed any further, or I can't use my phone's bluetooth capability correctly.
Either way, a great portion of usability is cut of from my phone. Thanks, Google!
Please stop complaining. It's unproductive and wearing on the rest of us.
Have you tried playing with "enable in band ringing" in developer settings? Or the selection of various types of output to support on the detailed settings of the Bluetooth device?
Don't know if it helps, the default behavior hasn't bothered me.