[MOD] EXT4All Continued + Now with TWRP 2.3 Support

iowabeakster · Nov 5, 2012

Thanks man. I appreciate the info (and everything else you've done).

I felt like having the dalvik moved w/ yaffs2 really did make certain things go quicker. But the mind often plays tricks. And it didn't really make much difference. Of course I never ran benchmarks to compare or anything...

For now, I just deleted some games and cleaned out their dalvik files. I also integrated some updated gapps into the /system and integrated their dalvik caches into /system too. I've now got 28 MBs free in the dalvik. We'll see how it works for a while.

Sir Lancelot · Dec 8, 2012

I'm having the exact same problem. Do we have a resolution to this?

Sent from my inc using xda app-developers app

tiny4579 · Dec 8, 2012

Sir Lancelot said:
I'm having the exact same problem. Do we have a resolution to this?

Sent from my inc using xda app-developers app

Which problem? As you're not quoting acting not described the problem, I don't know what you're taking about.

Sent from my Galaxy Nexus using Tapatalk 2

Sir Lancelot · Dec 9, 2012

tiny4579 said:
Which problem? As you're not quoting acting not described the problem, I don't know what you're taking about.

Sent from my Galaxy Nexus using Tapatalk 2

Sorry Tiny. I should have proofed my text before sending.

I'm referring to not being able to add the nodatalimit mod. In TWERP it is not possible to mount cache so installing your latest ROM then nodatalimit then Pon's Gapps leaves me in boot loop(cyanogen circle hang). Returning to recovery shows I can't mount data or cache. I have to pull the battery and nandriod.

What needs to be mounted to install nodatalimit? What am I doing wrong?

Sent from my ADR6300 using xda app-developers app

tiny4579 · Dec 9, 2012

Sir Lancelot said:
Sorry Tiny. I should have proofed my text before sending.

I'm referring to not being able to add the nodatalimit mod. In TWERP it is not possible to mount cache so installing your latest ROM then nodatalimit then Pon's Gapps leaves me in boot loop(cyanogen circle hang). Returning to recovery shows I can't mount data or cache. I have to pull the battery and nandriod.

What needs to be mounted to install nodatalimit? What am I doing wrong?

Sent from my ADR6300 using xda app-developers app

Not being able to mount cache is a problem and it may be nothing you're doing wrong. I fear if a full wipe doesn't clear it you may need to RUU. I've seen it before where data or cache could not be mounted causing headaches for the users and it's a potential major issue. TWRP mounts data and cache fine for me. I can check and uncheck it.

cmlusco · Dec 9, 2012

Sir Lancelot said:
Sorry Tiny. I should have proofed my text before sending.

I'm referring to not being able to add the nodatalimit mod. In TWERP it is not possible to mount cache so installing your latest ROM then nodatalimit then Pon's Gapps leaves me in boot loop(cyanogen circle hang). Returning to recovery shows I can't mount data or cache. I have to pull the battery and nandriod.

What needs to be mounted to install nodatalimit? What am I doing wrong?

Sent from my ADR6300 using xda app-developers app

All of the ext4 mods have been updated to V2 to work with TWRP, so make sure your using the V2 no_data_limit_mod and not an older one. Or mabey one of the files got corrupted. I would try downloading all 3 files again and give it another try.

tiny4579 · Dec 9, 2012

cmlusco said:
All of the ext4 mods have been updated to V2 to work with TWRP, so make sure your using the V2 no_data_limit_mod and not an older one. Or mabey one of the files got corrupted. I would try downloading all 3 files again and give it another try.

No, I believe he's got an actual issue with data and cache based on his description.

cmlusco · Dec 9, 2012

tiny4579 said:
No, I believe he's got an actual issue with data and cache based on his description.

But he makes it sound as if when he restores a nandroid all is well with cache and data. If all is well with the nandroid restored, i assume one of the files hes flashing is messing things up. Mabey i misunderstood and it is an ongoing issue with cache and data.

Sir Lancelot · Dec 11, 2012

Wipe and install it all again worked

cmlusco said:
But he makes it sound as if when he restores a nandroid all is well with cache and data. If all is well with the nandroid restored, i assume one of the files hes flashing is messing things up. Mabey i misunderstood and it is an ongoing issue with cache and data.

I had to do a full wipe and clean install and now have the ext4 nodatalimit working. I can only assume it was something in my recent install that prevented me from selecting cache and data.

tekweezle · Dec 14, 2012

just wondering, if the file system is changed to ext4, is journaling enabled and would that cause issues down the road? i always thought the normal convention was to not use a journaling fs on flash memory due to excessive wear and tear.

of course for now, it;s the lesser of 2 evils as the stupid 149 mb app storage partition is just plain heinous...

tiny4579 · Dec 14, 2012

tekweezle said:
just wondering, if the file system is changed to ext4, is journaling enabled and would that cause issues down the road? i always thought the normal convention was to not use a journaling fs on flash memory due to excessive wear and tear.

of course for now, it;s the lesser of 2 evils as the stupid 149 mb app storage partition is just plain heinous...

It's changed from ext3 which is journaled already to ext4 which is journaled, but data is set to writeback with the scripts in the zip to help improve performance.

The standard filesystem on Android has been ext4 for a while.

kirkers · Jan 2, 2013

What does Convert2Ext4 do with the Dalvik cache?

I hope this thread is still live, as the last post is a couple of weeks old. :fingers-crossed:

I think I have had complete success using Convert2ext4 (aka EXT4ALL). The version I used was "unlimited data normal dalvik"

My storage values changed as follows after running the fix:
Total Internal memory: 748MB --> 770MB (22MB increase)
ROM free space: <1MB --> 20MB (close to the value change of total internal memory)
Used internal memory: ~335MB --> 464MB (close to 128MB increase)
Remaining internal memory: ~420MB --> 306MB (close to 128MB decrease)

So, it seems that my ROM was being used to cache app data, which would explain why the value kept declining even though I NEVER added anything to it (using Titanium Backup Pro or anything like it). When free space on my ROM literally ran out, Android OS hit the proverbial panic button and warned me to free 512kb minimum to allow Gmail to download new mail. Now, it has 20MB free (and will hopefully stay that way, since I NEVER intend to transfer anything into the ROM!) -- The internal memory usage jump of 128MB probably indicates the Dalvik cache.

When I searched for anything called "dalvik" or "cache" using ASTRO file manager, I only came up with folders reporting "EMPTY".

Can anyone explain where to look or how to search properly?

tiny4579 · Jan 2, 2013

kirkers said:
I hope this thread is still live, as the last post is a couple of weeks old. :fingers-crossed:

I think I have had complete success using Convert2ext4 (aka EXT4ALL). The version I used was "unlimited data normal dalvik"

My storage values changed as follows after running the fix:
Total Internal memory: 748MB --> 770MB (22MB increase)
ROM free space: <1MB --> 20MB (close to the value change of total internal memory)
Used internal memory: ~335MB --> 464MB (close to 128MB increase)
Remaining internal memory: ~420MB --> 306MB (close to 128MB decrease)

So, it seems that my ROM was being used to cache app data, which would explain why the value kept declining even though I NEVER added anything to it (using Titanium Backup Pro or anything like it). When free space on my ROM literally ran out, Android OS hit the proverbial panic button and warned me to free 512kb minimum to allow Gmail to download new mail. Now, it has 20MB free (and will hopefully stay that way, since I NEVER intend to transfer anything into the ROM!) -- The internal memory usage jump of 128MB probably indicates the Dalvik cache.

When I searched for anything called "dalvik" or "cache" using ASTRO file manager, I only came up with folders reporting "EMPTY".

Can anyone explain where to look or how to search properly?

The MOD you're talking about doesn't touch dalvik at all but it does move all the app data in a partition called /datadata in the /data/data location to the main 750MB /data partition. The app data allows only 150MB of app data. Basically the 128MB you're seeing is the app data being moved to the larger partition and not loading the old app data location. This is done in a way that everything looks the same but internal memory reports more used due to app data. This is usually a good thing as now you don't have to worry about the silly 150 MB limit for app data.

VisualPerfection · Mar 25, 2013

Was looking to flash Tiny's CM10.1 builds and was wondering what the recommended Ext4 mod would be. Should I flash normal_data, no_data_limit_normal_dalvik, or no_data_limit_dalvik_moved? I'm new to this so pardon my ignorance.

tekweezle · Mar 25, 2013

i believe that

no_data_limit_normal_dalvik

is the one most people use and is the recommended one.

tiny4579 · Mar 25, 2013

Normal data has no benefits other than a few file system tweaks.

Sent from my Galaxy Nexus using Tapatalk 2

VisualPerfection · Mar 25, 2013

tiny4579 said:
Normal data has no benefits other than a few file system tweaks.

Sent from my Galaxy Nexus using Tapatalk 2

So then it's sounding like I should go with no_data_limit_normal_dalvik... From what I've read, I would flash ROM, EXT4All mod, and then Gapps? Perhaps order doesn't even matter.

tiny4579 · Mar 25, 2013

VisualPerfection said:
So then it's sounding like I should go with no_data_limit_normal_dalvik... From what I've read, I would flash ROM, EXT4All mod, and then Gapps? Perhaps order doesn't even matter.

ROM first always. Then the order of the other two doesnt matter. Also if you update cm builds for instance you need to flash the no data limit mod again unless you're choosing to wipe to get rid of the mod.

Sent from my Galaxy Nexus using Tapatalk 2

VisualPerfection · Mar 25, 2013

tiny4579 said:
ROM first always. Then the order of the other two doesnt matter. Also if you update cm builds for instance you need to flash the no data limit mod again unless you're choosing to wipe to get rid of the mod.

Sent from my Galaxy Nexus using Tapatalk 2

Much appreciated, Tiny! Am looking forward to trying out your creations!

BelmontAl · Dec 17, 2013

I am having problems with my DInc (see http://xdaforums.com/showthread.php?t=2571761 ) but at least have it working again on Froyo.

I am already running into "Insufficient Storage Available" problems (Phone memory reads: Total Space 149MB, Available Space 18.63MB; Internal Phone Storage reads "unavailable")

Previously (before my phone died), I ran the Convert2Ext4_no_data_limit_normal_dalvik mod to address this problem.

Two questions:
1) My phone currently cannot flash via recovery as it cannot access the sd card. Is there a way to flash this mod using flashboot or abd?
2) Given my phones other memory related problems, is it recommended to even try this mod?

Thanks,
Al

[MOD] EXT4All Continued + Now with TWRP 2.3 Support

Senior Member

Senior Member

Inactive Recognized Developer

Senior Member

Inactive Recognized Developer

Senior Member

Inactive Recognized Developer

Senior Member

Senior Member

Senior Member

Inactive Recognized Developer

Senior Member

Inactive Recognized Developer

Member

Senior Member

Inactive Recognized Developer

Member

Inactive Recognized Developer

Member

Member

Similar threads

Top Liked Posts