yashsingh1/xdaforums huggingface dataset:
[Droid Incredible Android Development] funkpod:
Yes, the storage mod, to remove the low storage notification.

I will check out the cm10 that you posted! Thanks!
[Droid Incredible Android Development] tiny4579:
Hey, I've released a v2.0 of the ext4all mods with support for TWRP 2.3+. The ones starting with Convert2ext4(normal_data, no_data_limit_normal_data, no_data_limit_dalvik_moved, no_data_limit_dalvik_moved_revert) also fix the mount tweaks not applying on /data and /cache when they're already ext4:

Below is my dropbox URL (please no abusing, cmlusco, feel free to mirror after doing any additional testing you want)

https://www.dropbox.com/sh/b6x8ld0rvq9glir/J8mH5hENoC/EXT4MOD
[Droid Incredible Android Development] omniatic:
Is there a kernel in these zips? I've been using the no-kernel mod from invisiblek along with your ICS Incredikernel. Just need to know if I'll have to reflash the kernel after the mod.

Thanks,

...sorry...I was on the phone...
[Droid Incredible Android Development] tiny4579:
There is but it doesn't get flashed unless you're on a a sense ROM. That was Jermaine's and my idea so you get a kernel that supports ext4 as stock sense kernel doesn't have ext4 support. On anything but sense it uses the existing kernel. So invisiblek's concern wasn't needed.
[Droid Incredible Android Development] pmsrefugee:
Trying to flash the v2 ext4all using twrp (latest version) on pons cm10 kang and it gets stuck on the cyanogen spinning wheel. I need to restore to get running again. Any suggestions as to what I'm doing wrong? I can't install swype to the system\app because it says I only have 36 kb free.
[Droid Incredible Android Development] tiny4579:
Which one and I'll try it again myself?
[Droid Incredible Android Development] pmsrefugee:
Convert2ext4_no_data_limit_normal_dalvik.v2.0.zip. last time I flashed one of these I had to update some system files with a windows script for it to work on cm10. I can't remember the name though.
[Droid Incredible Android Development] tiny4579:
Worked fine for me. No modifications. Tested on evervolv and CM10.
[Droid Incredible Android Development] pmsrefugee:
I'll do a full wipe and try again. Thanks for testing it though.
[Droid Incredible Android Development] zimlokks:
I think he means the update binary for twrp 2.3 nd all that blah blah blah
[Droid Incredible Android Development] pmsrefugee:
Aarrggh! Did full wipe (system too) and factory restore and Flashed pons cm10 kang (10/25/2012) and rebooted. Then in twrp recovery I flashed the ext mod mentioned above and rebooted. The cyanogen animation has been spinning for 5 minutes now and still not booting. I honestly don't know why it won't work for me.

Edit. I'm going to flash a different cm10 aosp rom and see if it works. Might just be the rom. Nope. Restored an aosp cm 10 and still just never ending boot animation
[Droid Incredible Android Development] tiny4579:
@pmsrefugee,

Can you try and get a logcat via adb and adb shell dmesg > dmesg.txt
[Droid Incredible Android Development] pmsrefugee:
EDIT: I can make a logcat fine, but when I type adb shell dmesg > dmesg.txt the file contains "klogctl: Operation not permitted." It looks like it is a read only issue and I don't have the correct permissions. The logcat.txt file has no problem writing to the pc. Also do you want the files posted as txt or in zip form?

EDIT 2: I found under settings, developer options, launch tools, my root access was set for apps only not adb. Let me try that . . . still says can't create dmesg.txt: read only file system

EDIT 3: solved. had to use adb root switch to get it to write. Now I'm ready to load mod.
[Droid Incredible Android Development] pmsrefugee:
Here are both the files.
[Droid Incredible Android Development] tiny4579:
The dmesg says it's from the cyanogenmod kernel. When did you run the adb shell command? if you ran it from cm10 it should be incredikernel. Also, my bad earlier, you don't need root to output it. You can do adb shell dmesg > /sdcard/dmesg.txt and you won't need root.

Ok, do these for me:

1. adb shell uname -a while it's bootlooping and tell me its output. I want to verify the kernel.

2. adb pull /init.inc.rc and post it

3. adb pull /init.rc and post it

I'm curious if the mod failed. Also, does the normal data mod work? The one that doesn't move data.

EDIT: I forgot to ask. Are you using any other mods?

From the fact that I saw errors in logcat about files in /data/system not being found I'd say somehow /data won't mount. You can verify if it is with:

adb shell mount | grep /data. If you get no results that's bad. Try mounting /data in that case with adb shell mount /dev/block/mmcblk0p1 /data and report the error.
[Droid Incredible Android Development] pmsrefugee:
Wow, I got my work cut out for me! I won't be home until later tonight though. I didn't know I could adb during the boot looping. I'm not running any other mods. It all started because I couldn't install swype in my system\app directory because it was too full.
[Droid Incredible Android Development] tiny4579:
I'm wondering though. Why didn't you just install swype to /data/app? The no data limit only affects the size of /data/data making it part of /data. Nothing else.
[Droid Incredible Android Development] pmsrefugee:
It wouldn't install and I read on the forums to install it to system instead. It keeps force closing when installed to data
[Droid Incredible Android Development] tiny4579:
Probably the way that version of the app is written. There is or was a beta version that can be installed as a user app.
[Droid Incredible Android Development] pmsrefugee:
The dmesg says it's from the cyanogenmod kernel. When did you run the adb shell command? if you ran it from cm10 it should be incredikernel. Also, my bad earlier, you don't need root to output it. You can do adb shell dmesg > /sdcard/dmesg.txt and you won't need root.

Ok, do these for me: ALL COMMANDS ENTERED DURING BOOTLOOPING

1. adb shell uname -a while it's bootlooping and tell me its output. I want to verify the kernel.

Linux localhost 2.6.38.8-incredikernel-jb #3 preempt thu oct 25 06:30:20 hst 2012 armv71 gnu/linux

2. adb pull /init.inc.rc and post it

failed to copy . . . :Permission denied

3. adb pull /init.rc and post it

failed to copy . . . :Permission denied

I'm curious if the mod failed. Also, does the normal data mod work? NOPE The one that doesn't move data.

EDIT: I forgot to ask. Are you using any other mods? NOPE

From the fact that I saw errors in logcat about files in /data/system not being found I'd say somehow /data won't mount. You can verify if it is with:

adb shell mount | grep /data. If you get no results that's bad.

'grep' is not recognized as an internal or external command, operable program or batch file.

Try mounting /data in that case with adb shell mount /dev/block/mmcblk0p1 /data and report the error.

'grep' is not recognized as an internal or external command, operable program or batch file.
[Droid Incredible Android Development] pmsrefugee:
Forgot to add new files.
[Droid Incredible Android Development] pmsrefugee:
got one file. the other one did not exist

had to add .txt to get it uploaded

I did a complete wipe again and will install the new cm10 kang 10/28/12 from Ponsinorem for my dinc. after booting I will reboot to recovery and install the mod. We'll see if it takes this time. Darn. same results. Oh well :( can't say we didn't try
[Droid Incredible Android Development] tiny4579:
I forgot to ask you to run adb root so you have superuser rights to pull those files. That should make items 2 and 3 pull the right files and you should be able to do adb pull /init.inc.rc. Do the bottom commands work if you change grep to busybox grep? - all after doing adb root?

I am wondering what moving the /data/data partition contents to /data will accomplish in installing swype to system unless your /data/data was near full but I'm moreso wondering why the mod fails.
[Droid Incredible Android Development] pmsrefugee:
As Maxwell Smart would say "missed it by that much!" I read the directions again and I don't know which step fixed it but here is what I did different.

1. Moved the mod file from to root of my sdcard.

2. Changed TWRP setting to Mount the data and system directories as they were not checked. Since we were having so much trouble reading (I figured why not give it a shot.)

Flashed the mod again and it worked perfectly. As least it is good to know it was me and nothing else. :eek:

Thanks again Tiny for all the effort you put forth trying to get to the "root" of the problem. (forgive the pun) :good:

Btw Swype installed and working! Can't wait for Swiftkey Flow beta though
[Droid Incredible Android Development] tiny4579:
Good to hear pmsrefugee!

Updated OP with link to mods.
[Droid Incredible Android Development] pmsrefugee:
Do I need to reflash the mod after I do a dirty flash of a new nightly, or only after a full wipe?
[Droid Incredible Android Development] tiny4579:
Both
[Droid Incredible Android Development] pmsrefugee:
Ok. Which mod do you recommend?
[Droid Incredible Android Development] tiny4579:
Depends on your needs. If you want to have data and datadata share a partition and not worth about the 150mb limit on datadata then no data limit normal dalvik is what I suggest. Otherwise the normal data or no ext4 mod.
[Droid Incredible Android Development] WildZontar:
Trying to do this on an inc loaded with Pons' CM10. The no data limit normal dalvik zip craps out with "Unable to mount /data, Unable to mount /cache". When I rebooted, CM10 bootlooped.

Any ideas?
[Droid Incredible Android Development] pmsrefugee:
Read my post #68 to resolve. I had exact same problem. Good luck and hit the thanks button if this works for you. :D
[Droid Incredible Android Development] cmlusco:
Try doing an advanced restore with cwm of just data from your last backup. As to why it messed up im not sure. I believe cm10 already uses ext4, and i know tiny just updated something to do with already having ext4. Mabey it needs more tweaking, im sure tiny will have a look.
[Droid Incredible Android Development] WildZontar:
This? Mouting data and system before didn't seem to do anything, still fails to mount /data. I'll try to move it to the root of the SD and see if that does anything, but I doubt it will.

---------- Post added at 04:36 AM ---------- Previous post was at 04:32 AM ----------

I'm using the TWRP, perhaps it's incompatible or incompatible with some other part of my device, or this is a bug.

I'm attempting to do this mod on an existing install, so I'll also attempt it on clean install.
[Droid Incredible Android Development] tiny4579:
Can you mount in recovery after wiping data and/or cache? I've heard of this problem and it happened randomly and the filesystem was corrupt. A format of the parittions (data and cache) may be needed to clear the error.

The change with already having ext4 was to ensure the filesystem mount tweaks were actually applied if it was ext4. Before, the tweaks of the ext4 mod only happened if the filesystem was ext3 which means that the normal mod on ics/jb or later cm7 releases only applied the filesystem conversion part. Nothing changed in the regard of the no data limit part.

It works in TWRP 2.3.1.0
[Droid Incredible Android Development] WildZontar:
Mounting in recovery works until I attempt the mod, at which point I can no longer mount /data or /cache, and the device bootloops.

Fails to mount /data even after wiping both.

---------- Post added at 04:49 AM ---------- Previous post was at 04:46 AM ----------

Update: I moved the zip to the root of the SD card and attempted it on a full wipe. No errors. I'm booting into the wiped system now to check the size of /data/data, and will attempt to do the same on my restored backup.

---------- Post added at 05:03 AM ---------- Previous post was at 04:49 AM ----------

Yeah, it doesn't appear to work with my backup. Probably some sort of filesystem corruption. I'll start this off as a new install.
[Droid Incredible Android Development] iowabeakster:
So I was just playing around and did the "no data limit + dalvik moved" and then installed all my apps (never had them all installed at once). I just happened to notice today that my /data/dalvik is now 146/149 full.

Is there anything to worry about having no space in the dalivk cache? Should I flash back the "normal dalvik"? Is there any advantage to keeping it a yaffs2 instead of ext4?

I've got plenty of space in /data. I also certainly don't need all these games installed at the same time (most I haven't played in a long time). So, keeping it "moved" or moving it back to /data can be done with no issues.

Thanks
[Droid Incredible Android Development] tiny4579:
This mod was mainly so the 150MB /data/data isn't wasted. I remember it scored better in benchmarks with it moved. Though with 150MB running low I'd think either the dalvik would clear unused files or fail to build cache so new apps loading would not be able to use it. Most of the possibilities sound like they'd create issues or compromise some performance.

I forgot to mention, you'd want to use the no_data_limit_dalvik_moved_revert to switch it back.
[Droid Incredible Android Development] iowabeakster:
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.
[Droid Incredible Android Development] Sir Lancelot:
I'm having the exact same problem. Do we have a resolution to this?
[Droid Incredible Android Development] tiny4579:
Which problem? As you're not quoting acting not described the problem, I don't know what you're taking about.
[Droid Incredible Android Development] Sir Lancelot:
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?
[Droid Incredible Android Development] tiny4579:
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.
[Droid Incredible Android Development] cmlusco:
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.
[Droid Incredible Android Development] tiny4579:
No, I believe he's got an actual issue with data and cache based on his description.
[Droid Incredible Android Development] cmlusco:
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.
[Droid Incredible Android Development] Sir Lancelot:
Wipe and install it all again worked

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.
[Droid Incredible Android Development] tekweezle:
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...
[Droid Incredible Android Development] tiny4579:
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.
[Droid Incredible Android Development] kirkers:
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". :confused:

Can anyone explain where to look or how to search properly?
[Droid Incredible Android Development] tiny4579:
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.
[Droid Incredible Android Development] VisualPerfection:
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.
[Droid Incredible Android Development] tekweezle:
i believe that

no_data_limit_normal_dalvik

is the one most people use and is the recommended one.
[Droid Incredible Android Development] tiny4579:
Normal data has no benefits other than a few file system tweaks.
[Droid Incredible Android Development] VisualPerfection:
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.
[Droid Incredible Android Development] tiny4579:
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.
[Droid Incredible Android Development] VisualPerfection:
Much appreciated, Tiny! Am looking forward to trying out your creations!
[Droid Incredible Android Development] BelmontAl:
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
[Droid Incredible Android Development] musical_chairs:
I have a dinc exactly like that (or I did, it went swimming a bit ago and I haven't put a battery in it to see if it survived), as far as I can tell the cause for me was hardware failure of the emmc. I was going to try some more stuff when I got around to it, but since it got dunked I probably won't bother.
[Droid Incredible Android Development] jmez:
Just found the dropbox link in another thread for these files:

https://www.dropbox.com/sh/b6x8ld0rvq9glir/J8mH5hENoC/EXT4MOD
[HTC Sensation] Electrowide:
Hi everyone

I have what might turn out to be a dumb question, but I am a little confused and haven't been able to find a direct answer for me.

I currently have a Sensation 4g that is "ship s-off".

I'm running the stock recovery, with Android 4.0.3 and HBOOT 1.27.000.

What I'm wondering is can I get root being "ship s-off"? If so, what's the best/easiest way to get root being "ship s-off".

Thanks for the help
[HTC Sensation] Overlord-in-training:
This guide tells you how to permroot your phone

xdaforums.com/showthread.php?t=1192300
[HTC Sensation] Electrowide:
Thanks.

I'll take a look at that then.
[HTC Sensation] Electrowide:
Unfortunately that guide doesn't seem to work for me in this case.

I flashed the PG58IMG.zip for Clockwork and everything seems to go fine, even says it was successful, but when I reboot, I'm still stuck with the stock HBOOT screen, no clockworkmod.

I should also point out that at the top of my HBOOT screen is the word LOCKED highlighted in pink, not sure if that's why this wasn't successful or not.

Any other thoughts or ideas would be greatly appreciated.

Thanks
[HTC Sensation] ganeshp:
After flashing CWM you'll still have stock hboot screen.. Only after going on into recovery.. (browse through the menu in hboot using vol up/down and select using power button)

Then you'll see clock work recovery...

The locked on top of hboot over soff is like a closed door behind you.. So you can unlock it pretty easily...

First of all follow the guide to root your device.. Then we can unlock your bootloader

sent from my blazing fast pyramid through sonic waves
[HTC Sensation] Electrowide:
You're right, the recovery part has changed. Talk about feeling dumb. It just didn't occur to me to check the recovery, for some reason I thought the HBoot would look different.

Thanks to both of you, ganeshp and Overlord-in-training, for your help. I really appreciate your time and assistance.
[HTC Sensation] Electrowide:
Alright, I've run into a problem. I've tried rooting my phone as per the guide here: http://xdaforums.com/showthread.php?t=1192300&highlight=4+0+3&page=409 but I still can't seem to gain root.

I've installed the su-2.3.6.3-efgh-signed.zip, su-2.3.6.1-ef-signed.zip and even tried su-bin-3.0.3.2-efghi-signed.zip, all of which tell me that they've installed successfully, but when I reboot the phone I don't have root (checked with Terminal Emulator, trying to open BusyBox Installer and Root Checker). Any ideas as to what I'm missing?

Thanks
[HTC Sensation] Electrowide:
Yay! I got it rooted. Had to use Superuser-3.0.7-efghi-signed.zip

Thanks again guys for the help earlier
[General Questions and Answers] Fosterzz:
currently on all ics slider lock positions are like left side camera and right side un-lock, is there a way to switch the position, coz i'm left handed and i feel little bit uncomfortable to move slider to right side to unlock from my left hand..