• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Titanium Backup: Integrate Dalvik into ROM?

TnIan

Member
Titanium Backup's feature list includes this: "Integrate Dalvik cache system elements into ROM, which can free up internal memory as well."

Can someone explain what this does and how it works? Does it just move dalvik-cache into the /system partition?
 
I tried it and it did move some stuff out of dalvik-cache. I don't know what qualifies as movable or not. I emailed the dev about it but never heard back.
 
I'm really curious about this, since it would free a big chunk on my low-end LT Optimus T. Here's the actual description from the changelog:

Version 4.6.4 [PRO] Added the ability to integrate Dalvik cache system elements into ROM (as odex files) which can save a lot of internal data storage space.

When I select the option, it claims:

Found 37 integrable files in the Dalvik cache (total 23.6 MB). Do you want to integrate them into ROM?

The thing is, I thought that there was some good reason that the Dalvik cache wasn't already in the System partition. And call me old fashioned, but I still cringe when I'm about to *write* to the phone's *Read*-Only Memory (aka, R-O-M). Although I've been doing it like crazy, moving apps I use in and yanking crapware out, I'm leery of treating the nominal ROM like any other memory space.

If they had some info on their site, I'd be less worried. But a search for "odex" on their Wiki turned up zilch.

Complicating things further is the fact that the "odex" links that come up on a Google search generally have to do with "deodexed" apps in custom ROMs. Here's how one site defines the term:

WHAT IS AN ODEX FILE?

In Android file system, applications come in packages with the extension .apk. These application packages, or APKs contain certain .odex files whose supposed function is to save space. These
 
Excellent post RobertB-DC.

dex files are compiled bytecode for the dalvik virtual machine. Contrary to common belief, dalvik (android) does not run java, but rather the compiler translates the Java into dalvik bytecode (dex).

odex files are just optimized dex files. When a ROM dev talks about de-odexed files, they are saying they have removed the initial optimization, so that things are more customizable (ie you can change the color of buttons in an app that has been de-odexed).

I (think) they still get translated to odex files by dalvik after they are first run and put into the dalvik cache. This helps with bootup times and the speed of apps in general (due to the JIT).


To me, it's generally ill-advised to move the dalvik-cache unless you really, really know what you're doing.

The only thing (IMHO) a user should ever do to the dalvik-cache is clear it, and only if they are rooted and change ROMs often.
 
To me, it's generally ill-advised to move the dalvik-cache unless you really, really know what you're doing.

The only thing (IMHO) a user should ever do to the dalvik-cache is clear it, and only if they are rooted and change ROMs often.

WHY o Why didn't I find this thread when I searched for info an hour ago ? It sounded like a good thing so I unwittingly went ahead and clicked on this new feature and it rebooted into a loop.

I posted first to ask for help here, but I'm moving my request for help to "all things root" for my phone. I'll leave this much as a warning that these new options in Titanium BU can really screw your phone up. I got titanium to protect my phone, not mess it up. Probably should have looked for a backup app that's for regular users who don't understand the depths of Android.
 
Let me add a footnote to the "warning to other users".

If you are using Titanium, you must be rooted. So before messing with /system (i.e. the partition where the ROM lives), whether using Titanium or any other method, take a nandroid backup. That way if you do mess something up you can undo it in a couple of minutes.
 
Back
Top Bottom