I don't think he's still around. His last post was half a year ago.
Actually it was jan 4 (Dfferent thread). Just send him a PM
Sent from my HTC Desire
RSK Sattelite SuperSense4.1
I don't think he's still around. His last post was half a year ago.
starting to run out of space and desire getting very slow? any ideas? been using ur CM since Dec
any help if I could add this script into miui rom? I am currently using the miui xj a2sd version. I am still facing the problem of running of space with a2sd. any idea? thanks!
Install by first deleting any a2sd script in the init.d folder, then flashing this script.
any help if I could add this script into miui rom? I am currently using the miui xj a2sd version. I am still facing the problem of running of space with a2sd. any idea? thanks!
Ha, use d2ext miui xj. No problems anymore.
Sent from my HTC Desire using Tapatalk 2
You can take a look at the modified ROM and you will find 3 new files in /system/etc, dalchk, fsck and sleep. These files are executed by init.rc because of my modifications to it. You can also decompile the boot.img and use a tool such as diff or diffuse (a GUI for diff) and check the differences between it and the unmodified init.rc from Alex's standard, D2EXT ROM. However, his ROM required another init.d script to move weather animations to /data, and modifications to the updater-script to flash everything that would normally be flashed to /data, to be flashed to /sd-ext. Sounds simple enough, right? Well, it's actually not quite as simple. When I have first implemented INT2SD to CyanogenMod 7, all I had to do was edit a few lines and add those three scripts. There was not a single ROM (and there are a few unreleased ones which I've worked on) to which I could apply a "standard" procedure. Each ROM required further modifications on its own and being the one who devised INT2SD, I know what I should look out for in order to avoid catastrophical bugs. ROM developers do not. This is why I do NOT offer support for "homemade" INT2SD implementations. Every ROM has its own peculiarities that need tending to and INT2SD implementations need to be very flexible to allow the ROM to work in conjunction with it. Sure, everything could go great, but INT2SD is extremely easy to implement horribly wrong and have huge bugs and even unbootable systems, and without knowing what the dev did to put it in their ROM, it is next to impossible for me to troubleshoot and fix. It would probably end up with me having to implement it myself either way in most cases and having angry developers and possibly users on my hands being pissed at me for doing a bad job and releasing a ****ty product, when the problem was just a typo in init.rc. That's why I have not nor will I release instructions for devs on how to implement it themselves.