[ROM] CyanogenMod - Scary experimental builds! [UPDATED 6/30 - v3.5.3]

[ROM] CyanogenMod - Scary experimental builds! [UPDATED 6/30 - v3.5.3] - G1 Android Development

This is a new thread for a new "experimental" line of CM builds since the old thread is gigantic now.
If you want a *stable* version of this rom, go here! This thread is for the brave testers who want to live on the edge, and help build a new "stable" release. I can't test everything on my own, so I need help from the XDA community!
*** DISCLAIMER ***
While this build is heavily optimized, it is also capable of pushing your G1 much harder. I am not responsible for bricked devices, dead SD cards, thermonuclear war, or the current economic crisis. Please do some research if you have any concerns about features included in this ROM before flashing it!
Please also read the FAQ in the thread listed above. This is not a thread for asking questions about how to partition your SD card, GMail timeouts, or installing a recovery image.
(v3.5.3 - experimental, updated 6/30):
ROM Image: http://n0rp.chemlab.org/android/update-cm-3.5.3-signed.zip
MD5Sum: 181d1d63d4d7f8526afc9c54f6ed948d
Theme Template (for theme developers): http://n0rp.chemlab.org/android/template-cm-3.5.2-signed.zip
MD5Sum: 2e95fae7848985bed6bf7200f89e7bff
Build Environment (if you don't know what this is, don't download it): http://n0rp.chemlab.org/android/cm-android-buildenv-3.5.2.tar.bz2
MD5Sum: 3cbe6fef3433db2939df2aa61e6fa1f8
Audio Resources (unzip to your sdcard): http://n0rp.chemlab.org/android/audio-resources.zip
MD5Sum: 7340ba86ddd4fba918ef97601c675ef9
Changes in v3.5.3
* Dalvik patches from master (actually tested!)
* Update wpa_supplicant from master
* Update Freetype to 2.3.9 (nicer font hinting) (being reverted for next release)
* Multithreaded A2DP from master (should reduce skipping)
* Minor kernel tweaks
* Include AUFS as a module by request
* Fix lock screen glitches and shrink battery icons
* KNOWN BUG - PDFViewer & NDK apps crash (grab /system/lib/libsgl.so from an old version for a quick fix)
* KNOWN BUG - Lock screen still doesn't update correctly
Changes in v3.5.2
* Ditch SquashFS on /system/lib because of performance
* Clean up the lock screen a bit, new icons, etc
* Patch AlarmClock so it doesn't lose snoozes
* If /system/sd/userinit.sh exists, execute it after a2sd setup
Changes in v3.5.1
* Add missing netfilter kernel modules and apply backported ext4 fixes
* Included Stericson's spiffy lock screen
* Some settings enhancements- show mod version and don't allow SD unmount when A2SD is active
* Switched to squashfs instead of cramfs
* /system/lib is now on squashfs, saving TONS of space (first boot of system is a little slower though)
* Tweak some cpufreq settings
* Disabled camera noise in libcameraservice since the HTC camera does it internally.
Changes in v3.5
* Kernel 2.6.29
* Revert vold hack to default, for now.

Reserved for future.

testing it now. any reason the theme won't work? if not I'll flash straight into it.

Denkai said:
testing it now. any reason the theme won't work? if not I'll flash straight into it.
Click to expand...
Click to collapse
No reason, the only real change in this build is the kernel. What I'm primarily interested to know is if this ROM solves the so-called "coma" issue that some people are experiencing. And if not, hopefully we can do some tweaking here to solve it without destabilizing the 3.4 branch which works great for most folks.

Does it support ext4? Is there a way to convert without having to reformat the partition?
What are the advantages of ext4?

dwang said:
Does it support ext4? Is there a way to convert without having to reformat the partition?
What are the advantages of ext4?
Click to expand...
Click to collapse
Yes, it does support ext4. I am currently running it. I also included the newer e2fsprogs if you want to upgrade, but I am not going to force anyone into that. EXT4 has some nice stuff like delayed allocation which can save wear on your device. Google will tell you how to upgrade with tune2fs, if you want. The e2fsprogs in my 1.2 recovery don't currently support the required options, so you'd have to stop the runtime, unmount and run the commands. I'll add the new version in the next recovery release.

downloading it now

dwang said:
Does it support ext4? Is there a way to convert without having to reformat the partition?
What are the advantages of ext4?
Click to expand...
Click to collapse
no it doesn't, least not yet
as for advantages
http://en.wikipedia.org/wiki/Ext4

cyanogen said:
No reason, the only real change in this build is the kernel. What I'm primarily interested to know is if this ROM solves the so-called "coma" issue that some people are experiencing. And if not, hopefully we can do some tweaking here to solve it without destabilizing the 3.4 branch which works great for most folks.
Click to expand...
Click to collapse
thats what i'm talking about. effing go-getters here i'm luvin' it. and big thanks to KNK. biggest brain i know.
question, and i'm just purely throwing something out there cuz i have'nt dont much reading on it, or tried fully understanding it, but if there is apps2sd, can there possibly be themes2sd? and if there was no sd it would revert to the rom on the phone safely?

cyanogen said:
Yes, it does support ext4. I am currently running it. I also included the newer e2fsprogs if you want to upgrade, but I am not going to force anyone into that. EXT4 has some nice stuff like delayed allocation which can save wear on your device. Google will tell you how to upgrade with tune2fs, if you want. The e2fsprogs in my 1.2 recovery don't currently support the required options, so you'd have to stop the runtime, unmount and run the commands. I'll add the new version in the next recovery release.
Click to expand...
Click to collapse
okay, I stand corrected. I knew the kernal could do it, however I hadn't heard anything about you actually incorperating it into the file system. is it possible to run all that through the phone itself or do you have to adb into it?

Denkai said:
no it doesn't, least not yet
as for advantages
http://en.wikipedia.org/wiki/Ext4
Click to expand...
Click to collapse
It supports ext4, and upgrading is an in-place upgrade, no reformat necessary.

Denkai said:
okay, I stand corrected. I knew the kernal could do it, however I hadn't heard anything about you actually incorperating it into the file system. is it possible to run all that through the phone itself or do you have to adb into it?
Click to expand...
Click to collapse
You'd need to use adb because you need to stop the Android runtime to unmount /system/sd.

does this require a wipe from 3.4.6?

Here goes nothin'! I get freezes 3-4 times a day. Hoping this will fix that.

renegadedj said:
thats what i'm talking about. effing go-getters here i'm luvin' it. and big thanks to KNK. biggest brain i know.
question, and i'm just purely throwing something out there cuz i have'nt dont much reading on it, or tried fully understanding it, but if there is apps2sd, can there possibly be themes2sd? and if there was no sd it would revert to the rom on the phone safely?
Click to expand...
Click to collapse
uh, no? if you did that, and the sd card was removed, the theme and Ahome files required to operate would not be there, and you'd crash. as it is set up, you can remove your sdcard right now and not crash your phone.

moosefist said:
does this require a wipe from 3.4.6?
Click to expand...
Click to collapse
Nope. flashed it over with no issues. on a side note, I've flashed and run every app through the phone, everything is 100% right now. to bad I can't update my EXT3 to EXT4 right now, I'll have to wait till tomorrow unless 3.5.1 comes out with ext4 upgrade already.

Flashing in a few minutes..
I'm all yours for testing..

dwang said:
Does it support ext4? Is there a way to convert without having to reformat the partition?
What are the advantages of ext4?
Click to expand...
Click to collapse
I would not suggest ext4 with 2.6.29, especially considering android does not remount RO and shutdown cleanly. For that matter there is nothing to speak of that is useful in an environment like the G1.
Performance of ext4 is not terribly different from ext3. Large file size/directory depth improvements are pointless on the G1. Online defrag also pointless for flash. About the only feature I can think of that is useful would be journal checksumming.
Better to wait for 2.6.30 kernels on android and even then it is debatable.

JanetPanic said:
I would not suggest ext4 with 2.6.29, especially considering android does not remount RO and shutdown cleanly. For that matter there is nothing to speak of that is useful in an environment like the G1.
Performance of ext4 is not terribly different from ext3. Large file size/directory depth improvements are pointless on the G1. Online defrag also pointless for flash. About the only feature I can think of that is useful would be journal checksumming.
Better to wait for 2.6.30 kernels on android and even then it is debatable.
Click to expand...
Click to collapse
My ROM is modified to do a remount ro at shutdown

cyanogen said:
It supports ext4, and upgrading is an in-place upgrade, no reformat necessary.
Click to expand...
Click to collapse
But if I wanted I could simply reformat my ext3 to ext4 and re-install my apps right?

Related

[ROM]Denkai's Hero ROM (DHR) [Version 0.2.0 Updated 01JUL09] - No Noobs

Okay, I made a post a while back that got trashed about my own Hero ROM I was going to try and make, I've got my permissions from those I need (I believe, if i step on your feet, sorry! let me know). This is an attempt to make a ROM with "HTC Sense" aka Rosie, and still be as fast as the Original ROMs on the G1. I won't even make the hope I can get it as fast as Cyanogens, but using his ideas, we may with a little luck! This thread is being made to keep track of what is done to the Alpha phase (unreleased) of this ROM up to it's Open Beta Release client, which I expect around 0.7. There will be no Closed Beta's. "Final" versions will be Stable, other wise it will be a beta/RC.
Requirements:
* 2.22.19.26I Radio
* Haykuro's SPL
* 3 partition class 6 SD card (FAT32,EXT3/4,linux-swap in this order. May goto 4 partitions and skip the second one so users can boot multiple ROMS with just a flash.) Swap no larger then 32MB, suggest 16-24MB
****DISCLAIMER****
This is an attempt to bring the latest and greatest of android to a reasonable level, however just like others, this build is HIGHLY experimental, I'm not responsible if it breaks your system, causes unwanted performance, or lets out the leprechauns you put in that shoe box under your bed. Do yourself a favor and don't flash this if you have only 1 phone for right now. I'm no Haykuro or Cyanogen, so bear with me please.
Alpha Stage:
*****READ ME*****
Note That I have been restructuring this build alot to run more like Cyanogens but still keeping the Hero framework. if you do test this build, it most likely won't boot up completely, I'm not holding my breathe, but I've stopped for today and figured I'd let anyone who wanted to see, what I've done. The file is signed if you wish to run the alpha test and see how it works. if you do, do me a favor and copy down the logcat at *first* boot via adb for me, and post it at pastebin.com. Also, I believe I may have incorporated busybox without realizing it. test it and see if I did, if I did, great, one less thing to do, if I didn't let me know.
Oh, and if you have an ext2/3/4 you don't want screwed with, remove your SD card before you boot it.
DHR 0.2.0 Things done
* Using NK02 + Fat4lity's 1.1 as a base and working from there
* Auto-Swap with Swappiness @ 30 with 3rd partition linux-swap
* Ramdisk to mount partitions with noatime/nodiratime
* Symlinks and bind mounts enabled by default for APPS2SD
* EXT3, possibly EXT4 for APPS2SD
* Fix_Permissions Script from Cyanogen
* Cleaned up boot script
* Cleaned up extra files
* Removed Launcher.apk
* APP2SD
Left to do:
* Clean up Debug at boot
* Cyanogens Optimized 2.6.29 kernel
* Haykuro's APN list
* Latest HTC_IME with drawing pad
* Add script to separate internal mem from sdcard EXT3/4
* SU Binaires and apps
* Busybox
* Update ROM name
Attempt to do:
* if I can get rid of binds in dexopt I will odex application files, allowing for faster boot.
* Check for anything from master that may incorporate faster performance i.e. Davlik Patches.
Download:
http://www.mediafire.com/?sharekey=e044cc34daf9c0fed8f14848abf485dde04e75f6e8ebb871
Special Thanks:
Cyanogen (Without him I wouldn't be doing this)
JustAnotherCrowd
NK02 + Fat4lity
JesusFreke
Haykuro
Dwang

can recieve the link for beta testing

All day im waiting for fixs updates,and i get some more dreams i want the hero working i have a dream lol....hope this stuff works and a link will be provided.
This will make a big mess of things around here i'm sure,but still in all good work if you can fix what needs to be fixed. Really you should have held back till there was a link atleast this will be filled in two days.
Best of luck bro.

Ill beta test PM me if youre interested.
Got all the essentials and know how.

i fully expect this to be ignored, I need a place to put all my ideas, wants and desires for the ROM, and to help me remember what I have done and still need to do. I don't have a blog and don't care for one, and plus this will allow for communication to a community that has an intrest, thus allowing me to get last minute ideas in place.

what are the bugs in this rom? do u know.

i definately wanna try this 1 out 2

Denkai said:
Okay, I made a post a while back that got trashed about my own Hero ROM I was going to try and make, I've got my permissions from those I need (I believe, if i step on your feet, sorry! let me know). This is an attempt to make a ROM with "HTC Sense" aka Rosie, and still be as fast as the Original ROMs on the G1. I won't even make the hope I can get it as fast as Cyanogens, but using his ideas, we may with a little luck! This thread is being made to keep track of what is done to the Alpha phase (unreleased) of this ROM up to it's Open Beta Release client, which I expect around 0.7. There will be no Closed Beta's. "Final" versions will be Stable, other wise it will be a beta/RC.
Requirements:
* 2.22.19.26I Radio
* Haykuro's SPL
* 3 partition class 6 SD card (FAT32,EXT3/4,linux-swap in this order. May goto 4 partitions and skip the second one so users can boot multiple ROMS with just a flash.)
Alpha Stage:
DHR 0.0.6
* Using NK02 + Fat4lity's 1.1 as a base and working from there
* Auto-Swap with Swappiness @ 20 with 3rd partition linux-swap
* Ramdisk to mount partitions with noatime/nodiratime
* Symlinks and bind mounts enabled by default for APPS2SD
* EXT3, possibly EXT4 for APPS2SD
* Cyanogens Optimized 2.6.29 kernel
* Haykuro's APN list
* Latest HTC_IME with drawing pad
* Add script to seperate inernal mem from sdcard EXT3/4
* Reseach Camera functions for new HTC Camera
* Check for anything from master that may incorperate faster performance i.e. Davlik Patches.
* SU Binaires and apps
* Busybox
* Clean up Debug at boot
* if I can get rid of binds in dexopt I will odex application files, allowing for faster boot.
Special Thanks:
Cyanogen (Without him I wouldn't be doing this)
JustAnotherCrowd
NK02 + Fat4lity
JesusFreke
Haykuro
Dwang
Click to expand...
Click to collapse
ill beta test too....

I am willing to help, I do bug writing at work so this stuff is second nature.

I have no technical skills...I can't read or write code...but I am a fearless flasher (hah) and am more than willing to test this out.

i wouldnt mind beta testing
got a class 6 16gb and know adb pretty well
and i know my way around the g1 pretty well now and a little linux too

i would definitelly be interested in testing, especially with the auto swap on 3rd partition

Awesome! Let me know if you need more testers. Good luck!

cool shoot it my way i will try it also

Anyone able to find that new HTC_IME that came out last month? (JUNE) can't find it again and I lost my old copy.

I'm up for testing as well. This is sorely needed, as all the other implementations of Hero are just way too slow to be useful. Plus, I need stuff to do since cyanogen has taken over the appstosd scene(he seems to know what he's doing a bit better than I do) and all attempts to improve my appstosd2 app(tried to make it have the sdsplit script built in but it seems android has a max size for assets...) have ended in failure. *Sigh* need to come up with a new useful hack...

I'll give it a test

Second version of alpha release is up. I didn't post the first one. READ the first post before downloading.

Recommended sizes for the 3 partitions?
Thinking on my 16GB - 15GB/500MB/100MB?

read the first post. clear as day says your linux-swap should be fat32, ext,swap and your swap should be 16,24, or 32 MB.

[ROM][PORT] JACxHEROSkiv1.7r2 by JAC/CC [09/04/2009]

Hello,
Port for 32B :
Original thread for more details
First A big thanks to Haykuro for providing the system dump of the latest known Hero build. Great contributions from Haykuro always!!! Make sure to thank him!!!
This ROM is based off the latest "HTC" ROM leak 2.83.x.x with tons of mods enjoy!!
DO NOT RUN ANY OTHER APPS2SD APPLICATIONS ON THIS BUILD. YOU WILL BREAK YOUR SYSTEM. THEY ARE NOT NECESSARY BECAUSE THIS ROM WILL DO A2SD AUTOMATICALLY AND BETTER!
NOTES:Swap is linux-swap by default. Edit the user.conf in /system/bin to change swappiness etc. Compcache modules built with the latest source are included if you want compcache or compcache with backing etc. Run sh /system/bin/swap -s to check swap status and other mod values.
JACxHEROSki-v1.7r2
-Remixed 1.5/1.6 with the latest 2.83.x.x HTC Hero Dump
-Kept Old Mms.apk
-Removed Plurk related .apk's (I dont like plurk )
-Updated Modules with backing swap bugs fixed
-Updated libs from dump
-Compcache with Backing Swap now on by default instead of Linux-Swap (Still need the 3rd partition for backing swap!)
-added back the ophone dropdown
- Everything else reads as 1.6r2a does
JACxHEROSki-v1.6r2a :
*New 2.6.29 kernel by JAC-SKI CUSTOM HTC SOURCED
*reverted Mms.apk
*update wifi tether 1.52
****EXPERIMENTAL*******
JACxHEROSki-v1.5r2 :
- Thanks to Haykruo for the 1.79.482.3 Hero Dump .img's
* New 2.6.29 kernel by JAC-Ski w/perf patches
* Enhanced ramdisk with auto EXT2/EXT3/EXT4 A2SD Support!!
* Cyanogens Apps2SD with a2sd ran before user runtime starts
* Includes E2FSProgs for checking and converting Ext filesystems (Thanks Cyanogen!)
* Apps2SD is automatic. All you need is a second partition.
* Supports ext2/ext3/ext4 for Apps2SD
* Squashfs/Cramfs Support
* Linux-Swap is automatic! All you need is a linux-swap partition (32MB~)
* fsck at boot (should stop FS corruption)
* Tweaked frequency scaling options to be more responsive (Thanks Cyanogen!)
* Maximum CPU scaling frequency set to 528MHz
* TCP buffer changes
* PATH variable updates
* Calls to /data/init.rc /system/init.rc
-Latest BusyBox with working Modprobe
-Module updates
-Working Audio/Modified for better speaker/mic clarity
-Shafty's LED fixes on boot (not perfect)
-Auto backlight turned off by default in build.prop
-rwsystem, rosystem for easy remount from terminal (Thanks Soulife!)
-lucid already in /system/bin
-DalvikVM optimized
-Multi-Touch
-Compcache 0.6+ modules included
-Linux-swap support
-swap is controlled via user.conf in /system/bin
-Flash 9
Click to expand...
Click to collapse
Added Items
added ext2/ext3 tools to /system/bin
added Lucid script to /system/bin
added SDcard placeholder
added Telnet Binary
added BusyBox
added Java.apk (thanks xDan)
added Voice Search
added Wifi tether
added Superuser Binary
added sysctl.conf
added Haykuro's APN list
added HCItool to /system/bin
added Terminal
added EN_US to Locales
Removed Items
removed Learnmore.apk from HTC
removed HTC PCSync
Click to expand...
Click to collapse
Everything else has a function for someone or another remove via terminal if you dont want Stock etc
JACxHEROSkiv1.7r2 need wipe : : Download
JACxHEROSkiv1.5 to 1.6r2a no wipe : : Download ---Corrected corrupt file--
JACxHEROSkiv1.6r2a : Download
JACxHEROSkiv1.5r2 : Download

wait so the original thread was for 32a?

The rom is ported from Dream, that's the original rom .....

Faster than qtek? will give a try this night.
Thanks for the port!

Hi Setenza, how fast is this rom ? I m running drizzy's full v3, can you make a comparison between these two ?

ElChouch said:
Hi Setenza, how fast is this rom ? I m running drizzy's full v3, can you make a comparison between these two ?
Click to expand...
Click to collapse
No i don't use this rom.

I just flashed this - best part is that I do not get the "blurry screen" problem.
I enabled compcache and backing swap, and reversed apps2sd to run off the memory. This is a fast ROM - so far I'm really really liking it. This is subjective - but right now I think it is about the fastest hero I've run - but many of the recent ones have given the blurry screen, so I haven't given them a chance.

pbaird said:
I just flashed this - best part is that I do not get the "blurry screen" problem.
I enabled compcache and backing swap, and reversed apps2sd to run off the memory. This is a fast ROM - so far I'm really really liking it. This is subjective - but right now I think it is about the fastest hero I've run - but many of the recent ones have given the blurry screen, so I haven't given them a chance.
Click to expand...
Click to collapse
How you reversed app2sd? i allways thing that magic owners no need app2sd, we have more internal storage than dream one....
Any room run faster from internal memory than from microSD, i think.

setenza01 said:
The rom is ported from 32a, that's the original rom .....
Click to expand...
Click to collapse
So this is the first 32B ROM of JACxHero 1.4? If so that would explain why I was having problems running it on my 32B board.

fridlack said:
How you reversed app2sd? i allways thing that magic owners no need app2sd, we have more internal storage than dream one....
Any room run faster from internal memory than from microSD, i think.
Click to expand...
Click to collapse
I followed Loccy's instructions here -> http://forum.xda-developers.com/showpost.php?p=4353332&postcount=68

tried this rom, it seemed quick but brouser seems slow when loading a page and youtube cant play in HQ which tells me that im not getting 3g even tho the icon is their

wow this is even faster than qtek with compcache and back :O

GPS does not work
I have just flashed this ROM on MyTouch, here is my obeservation:
1) GPS Does not work
2) Weather widget does not work, even I used the City name it does not get data on widget screen (is says "Can not load weather data...something")
3) Overall its very slow, when placed only 4 settings widgets on first screen
4) Wifi, Phone call works good.
Rest I'll test and let you know. Thanks!

seems like these hero roms act different with each person who loads it. My weather widget worked fine for me. their was alittle bit of lag.
Still...the hero roms are getting better and better.

pbaird said:
I just flashed this - best part is that I do not get the "blurry screen" problem.
I enabled compcache and backing swap, and reversed apps2sd to run off the memory. This is a fast ROM - so far I'm really really liking it. This is subjective - but right now I think it is about the fastest hero I've run - but many of the recent ones have given the blurry screen, so I haven't given them a chance.
Click to expand...
Click to collapse
Can you explain how did you enabled compcache and backing swap?
Its needed a swap partition or its need two swaps partition?
Sorry for my english and thanks

pbaird said:
I followed Loccy's instructions here -> http://forum.xda-developers.com/showpost.php?p=4353332&postcount=68
Click to expand...
Click to collapse
Thanks for the link, as i undestand if i extract rom, delete cd /system/bin/a2sd and resing it, after instaling is it without app2sd? or need to make the full process after install the rom?

pbaird said:
I just flashed this - best part is that I do not get the "blurry screen" problem.
I enabled compcache and backing swap, and reversed apps2sd to run off the memory. This is a fast ROM - so far I'm really really liking it. This is subjective - but right now I think it is about the fastest hero I've run - but many of the recent ones have given the blurry screen, so I haven't given them a chance.
Click to expand...
Click to collapse
how did you disable A2SD? how did you enable compcache and backingswap? new to all 3. would appreciate any help. thanks much in advance.
nvm found link for A2SD removal

hitman4485 said:
how did you disable A2SD? how did you enable compcache and backingswap? new to all 3. would appreciate any help. thanks much in advance.
nvm found link for A2SD removal
Click to expand...
Click to collapse
Wanna share the link? Been lookin' for it for a while now. Tried different searches, but I don't know how it's worded, what thread it's in, etc. lol Any help would be great. Also, is it running smooth for you without A2SD?

Mi|enko said:
Wanna share the link? Been lookin' for it for a while now. Tried different searches, but I don't know how it's worded, what thread it's in, etc. lol Any help would be great. Also, is it running smooth for you without A2SD?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=4353332&postcount=68
i personally can't get it to work... i get stuck at the splash screen...
EDIT: you probably want to download connectbot found here
http://code.google.com/p/connectbot/
i was trying to use a plain windows command prompt, which is probably why its not working...

can someone verify this for me when i use hero rom like this and disable touchflo then restart the phone and go to people the app crashes everytime???

[Script][A2SD]Darktremor 2.7.5.3 Beta 04 [Evo] (01/29/2011)

Introducing...
Darktremor Apps2SD 2.7.5.3 Beta 04
Date of Release: January 29, 2011
Download Current Version
Instructions - Change Log - Commands - ROM List - Developer's Guide
Darktremor Apps2SD Fan Page ----
Darktremor Apps2SD Development Group
Are you installing Darktremor Apps2SD on your phone? Here are the instructions to help you: Facebook
Are you a developer wanting to include Darktremor Apps2SD in your latest ROM? Here is the Developer Guide: Facebook
Click to expand...
Click to collapse
Update on Beta 4
It seems I'm getting mixed results with these betas. I'm not sure why this is occurring, some people have been able to get this working right while others have had a hard time with it.
Currently, I'm rebuilding the entire program. This takes a while because I have to figure out how to pack all these options into the program but make it small enough to where it will run correctly.
I will say that some of the beta features are coming back out...one of them is the search for a partition code. I suspect that code may be leading me into issues with certain platforms, so I'm going back to the 2.7.5.2 method of mounting (mmcblk0p2 or mmcblk1p2).
Also, parts of the code will use Busybox Ash (the only code that won't will be starta2sd, which will still use Bash for the time being). The startup code will definitely use Busybox Ash.
Until then, here are the links to the the last two betas and the last official release:
Version 2.7.5.3 Beta 04 - http://www.darktremor.info/files/a2sd/dtapps2sd-2.7.5.3-beta04-signed.zip
Version 2.7.5.3 Beta 03 - http://www.darktremor.info/files/a2sd/dtapps2sd-2.7.5.3-beta03-signed.zip
Version 2.7.5.2-1 - http://www.darktremor.info/files/a2sd/dtapps2sd-2.7.5.2-1-signed.zip
And, if you want past versions, you can view the repository: ftp://dtuser:[email protected] (ignore the smiley face...that's XDA doing that.)
Click to expand...
Click to collapse
Beta 04 took longer than I expected to release. I have done major changes to the code:
1. New commands: convert-ext4 - This will convert your EXT3 partition into EXT4. Just a friendly reminder on this command: Not every rom supports EXT4, so it is possible to go into a boot loop if you switch roms. Use with caution.
2. Reworked convert-ext3 (convert-ext4 gets similar code)...now a flag file is set before the reboot (no conversion is done before the reboot). At load time, the conversion is performed. This takes longer in the reboot process and you may think your phone has locked up...wait about five minutes before doing anything with the phone.
3. Repair is rebuilt...now it uses existing commands to repair the setup (reinstall, remove, cachesd, cachepart, nocache, datasd, nodata). Definitely shrinks the code.
4. Added fix_permissions program to the package. This may help with Superuser issues when using the datasd feature. It is used in reinstall, remove, datasd and nodata.
5. a2sd install is back!!! Both a2sd install and a2sd reinstall do the exact same thing.
6. Dalvik heap code has been shrunk and now creates a file called dalvikheap. Actually, the code has been doing this all along (since about 2.7.5.2, I think), but I never put the code in to use the file.
7. Low Memory Killer code has also been shrunk and uses a file caled dtset_lowmem to set the low memory killer parameter.
8. Replaced Busybox PS function with Toolbox PS. The issue with Busybox PS is that it gives a false reading when I look for android.process.acore (which is the main program when the GUI starts up). If that is present, the program thinks you are trying to run Darktremor without any command line parameters. This was because Busybox would report the process was there when, in reality, it wasn't (validated this when my phone was boot looping.) Toolbox's PS reports the correct setting. This should fix the bootlooping issues some people are experiencing.
9. New commands: usedtbusybox and usedefaultbusybox - these commands may help in diagnosing issues that is may be related to the native Busybox on your rom. a2sd usedtbusybox will use the Busybox that is packaged with Darktremor. a2sd usedefaultbusybox will turn back on the scan behavior of the program introduced in Beta 03.
10. Support for Darktremor Apps2SD version 2.7 and earlier has been discontinued. To upgrade correctly from one of those versions, use version 2.7.5.3 Beta 03b or earlier.
11. Finally fixed stalled boot issues (or at least my tests with several roms says so.)
See the change log for additional details.
You will notice that if the program runs repair and finds a problem, it will correct the issue and reboot. You will see a second reboot when the dalvik-cache clears (this is to fix timing issues with CyanogenMod...I can't control that startup as well as I can other roms). This only happens if repair is ran or you flash a new rom (as repair will realign all data). If you are upgrading from a previous version of Darktremor, you should not see the reboots.
Click to expand...
Click to collapse
This is Darktremor Apps2SD, a multipurpose program that primarily allows a user to execute applications created for the Android OS on their Secure Digital card (with the proper setup...more on that later). But, Darktremor Apps2SD is all about stability. The goal is to be able for all users of the Android OS to be able to take advantage of a method to run their applications from a secure digital card.
But just because the Darktremor Apps2SD is all about stability, doesn't mean it isn't packed with features:
- Move applications (both free and paid) to the Secure Digital card.
- Move Dalvik Cache to run either from your Secure Digital card or from your cache partition and clears the cache on demand.
- Boot Loop Protection: prevents the phone from boot looping in the event the SD card could not be mounted.
- Dalvik JIT for faster performance on Roms which support it.
- User selectable sizes for the Dalvik heap sizes, allowing a user to freely optimize their system.
- Activate a swap partition on your SD card and sets how often the swap partition is utilized.
- Automatically fixes configuration issues.
- Users can check the free space on their SD card and check the installation to make sure all is setup correctly.
- Runs ZipAlign on demand...this makes your programs load faster.
- Built in help system for easy reference of commands.
- All features can also be reversed without repartitioning your Secure Digital card.
- New logging features assists in troubleshooting issues.
- Commands to set the Low Memory Killer feature at boot time. Great for those people who are the "set it and forget it" type.
- And more...
Darktremor Apps2SD is not the same as Froyo Apps2SD. Froyo Apps2SD creates a secure folder on the FAT32 section of your SD card (this is the section that you see when you mount your phone to your computer) and stores the programs there. This is nice as you don't have to do anything special with the phone, but it isn't backwards compatible with older versions of Android (Cupcake, Donut, Eclair) and, because of the way Froyo works, older programs not designed for Froyo will automatically stay on your internal storage (unless you install a program that forces the move to your SD card).
Darktremor Apps2SD takes a different approach. Based on the original CyanogenMod works, Darktremor Apps2SD uses symbolic linking to force Android into moving your applications to the SD card. Because Android will not allow anything to be ran from the FAT32 partition on your SD card (and, in Froyo, it will only allow you to run programs from a special folder), Darktremor utilizes filesystems called EXT2, EXT3 and EXT4. Each one of these filesystems is native to Linux (the operating system running Android), which allows you to run programs from them (same as, say, a computer running Ubuntu). This method is completely compatible with all versions of Android, including Froyo. In fact, you can run both the Darktremor Apps2SD and Froyo Apps2SD at the same time.
Check out the list of Roms that either have Darktremor Apps2SD installed or are compatible with Darktremor Apps2SD. Click on the link labeled ROM List at the top of this message.

Darktremor Apps2SD Installation Instructions
For the list of people that helped me test this on the various roms that use or can use Darktremor Apps2SD and the changelog: http://forum.xda-developers.com/showpost.php?p=7034326&postcount=3
Click to expand...
Click to collapse
The installation instructions can be found here: http://forum.xda-developers.com/showpost.php?p=7021325&postcount=2
Click to expand...
Click to collapse
If you want a list of commands for Apps2SD, type a2sd help.

Reserved...

Is there any chance we may have the option to store text messages on the SD card using a system similar to Apps2SD?

That would probably be dependent on the program you use. I was experimenting on moving the /data/data folder to the SD card. Unfortunately, I wasn't successful with it retaining settings during the move.
I did take out the code that forces /data/data to stay on the data partition, so if you want to move the /data/data folder to, say, /system/sd/data, you can.
I have the option in Darktremor A2SD 2.7.5 Alpha (based on 2.7 Update 1. The current code is based on 2.7 Update 3r1), I will put it in again if you wish to experiment with it (though I will leave it undocumented until it is proven successful).
`
Jykinturah said:
Is there any chance we may have the option to store text messages on the SD card using a system similar to Apps2SD?
Click to expand...
Click to collapse

tkirton said:
That would probably be dependent on the program you use. I was experimenting on moving the /data/data folder to the SD card. Unfortunately, I wasn't successful with it retaining settings during the move.
I did take out the code that forces /data/data to stay on the data partition, so if you want to move the /data/data folder to, say, /system/sd/data, you can.
I have the option in Darktremor A2SD 2.7.5 Alpha (based on 2.7 Update 1. The current code is based on 2.7 Update 3r1), I will put it in again if you wish to experiment with it (though I will leave it undocumented until it is proven successful).
Click to expand...
Click to collapse
To be honest, I am quite new with Android development. I think I will look at some documentation and such before I begin experimenting. Maybe I should do an adb pull of /data/data and look at the stuff there.
If you don't mind, I may request for it later.

Sure. Not a problem.
Jykinturah said:
To be honest, I am quite new with Android development. I think I will look at some documentation and such before I begin experimenting. Maybe I should do an adb pull of /data/data and look at the stuff there.
If you don't mind, I may request for it later.
Click to expand...
Click to collapse

Hi, what is he best heap size to use?
Also, can I use apps2sd on the updated 1.47 rooted ROM based on the OTA simply by flashing?

Normally on the Hero (the one I use), the heap size is 16mb (a2sd smallheap). DamageControl uses a heap size of 24mb (a2sd largeheap), which seems to make dalvik-cache runs faster. I included a 32mb heap setting (a2sd jumboheap) that I thought would be perfect for the added memory of the Evo.
Honestly, I'm not sure which one is better. I personally can't tell the difference between them. I would experiment between them and see...but I'm not sure you'll get a noticeable difference unless you clear your dalvik-cache.
As for running Apps2SD on the updated 1.47 rooted rom...if it is a stock rom, it won't run. This is because the stock rom by itself does not have the necessary components to launch any version of Apps2SD (CyanogenMod, Darktremor, DamageControl). Myself and another developer injected the Apps2SD functions in our stock rom and released it (it was just a stock rom...no other modifications was done). So, someone would have to inject the Apps2SD functions into the stock rom.
freeza said:
Hi, what is he best heap size to use?
Also, can I use apps2sd on the updated 1.47 rooted ROM based on the OTA simply by flashing?
Click to expand...
Click to collapse

Partition Size
Just received my 16G (C6) SD card and was wondering if anyone had recommendations for initial sizing of the partitions? Originally did a 50/50 split, but second guessing myself.

I have 4GB, but that's a bit excessive. Try around 1-2GB for the ext and, depending if you want a swap partition, 32MB for swap. All the rest goes to FAT32.
dpilcher said:
Just received my 16G (C6) SD card and was wondering if anyone had recommendations for initial sizing of the partitions? Originally did a 50/50 split, but second guessing myself.
Click to expand...
Click to collapse

Preview Fix 2 is out...more corrections to JIT (seems this one is hard to get my hands on).

tkirton said:
I have 4GB, but that's a bit excessive. Try around 1-2GB for the ext and, depending if you want a swap partition, 32MB for swap. All the rest goes to FAT32.
Click to expand...
Click to collapse
Thanks for the feedback. I moved to 3G, but will probably take that down to 1.5 (or almost 3 times the phone's internal system memory correct?) Don't think I will enable a swap, even though it's a C6 with protection elements on the card, don't want continual rw.

I have swap on mine and I don't see any ill effects.
But you have an Evo, which has twice the memory of the Hero. You probably would benefit without a swap file.
dpilcher said:
Thanks for the feedback. I moved to 3G, but will probably take that down to 1.5 (or almost 3 times the phone's internal system memory correct?) Don't think I will enable a swap, even though it's a C6 with protection elements on the card, don't want continual rw.
Click to expand...
Click to collapse

Guide to add Apps2SD to roms
I have added a guide on my main thread that shows you how to add Apps2SD support in roms that don't have it.
http://forum.xda-developers.com/showthread.php?t=715116

Bump...Preview Fix 4 is out (yes, I skipped PF3...Desire users got that one).

I'm trying to get apps2SD to work with the DC ROM and I'm not seeing this partition selection. When I click on partition, a menu opens up that says a lot about mount and unmount. Also says something about format boot, system, data,cache, sd card, sd-ext. Any help would be appreciated!

tkirton said:
I have swap on mine and I don't see any ill effects.
But you have an Evo, which has twice the memory of the Hero. You probably would benefit without a swap file.
Click to expand...
Click to collapse
I know this is probley a stupid question but whats the benefit of this?speed? And if so, is it a big differnence? Thanks

Are you trying to get Darktremor Apps2SD to work or the one already included with DamageControl.
If it is Darktremor, the GUI setup in DamageControl is not compatible. You need to use the commands via Terminal or adb shell. Type a2sd help for a list of commands and a description of what they do.
pastert33 said:
I'm trying to get apps2SD to work with the DC ROM and I'm not seeing this partition selection. When I click on partition, a menu opens up that says a lot about mount and unmount. Also says something about format boot, system, data,cache, sd card, sd-ext. Any help would be appreciated!
Click to expand...
Click to collapse

The only benefit is that it will allow programs to stay in memory longer. It is a little faster, but not significant.
Most people don't even bother putting a swap partition.
Using a program like Autokiller, which adjusts the values of the built-in auto termination routine, would benefit you far better than swap.
brownmc77 said:
I know this is probley a stupid question but whats the benefit of this?speed? And if so, is it a big differnence? Thanks
Click to expand...
Click to collapse

[Script][A2SD]Darktremor 2.7.5.3 Beta 04 [Desire] (01/29/2011)

Darktremor Apps2SD Installation Instructions
For the list of people that helped me test this on the various roms that use or can use Darktremor Apps2SD and the changelog: http://forum.xda-developers.com/showpost.php?p=7034326&postcount=3
Click to expand...
Click to collapse
The installation instructions can be found here: http://forum.xda-developers.com/showpost.php?p=7021325&postcount=2
Click to expand...
Click to collapse
If you want a list of commands for Apps2SD, type a2sd help.

Desire aint listed??

I don't have any roms using it in Desire...hence why I'm posting this. But:
Kurt666
- For testing on Pay's ROM for Desire v1.4 (HTC Desire)
Click to expand...
Click to collapse
So there is one rom that is tested with it.
I've checked a good segment of the roms here, and it should work just fine, especially the 2.7.5 version (as the swap, dalvik-cache and the applications are all separate functions now).
I'm trying to expand the program's scope. I have six different platforms that run it (21 roms total) and I have one Desire rom tested...but none actually using it (my fault...should've expanded this a month ago).
Nekromantik said:
Desire aint listed??
Click to expand...
Click to collapse

Backing up just now my Open Desire 1.5 on nandroid.
Going to be your guinea pig for Open Desire (AOSP)
I will paste the logcat output of my first boot (if there will be any)

Will try to test on modaco r3.1, wish me luck
Sent from my HTC Desire using Tapatalk

well, it seems that it changed... Nothing.
http://pastebin.com/6D346gwX
Maybe the chef was already using your script?

So it didn't work?
Sent from my HTC Desire using Tapatalk

antz88c said:
So it didn't work?
Sent from my HTC Desire using Tapatalk
Click to expand...
Click to collapse
It booted in the same time that it booted without applying the tremor script, and I think that the logcat was quite similar too.
And the free space reported is the same than before.
So, it didn't work, or it was already working before
EDIT:
I decompressed the script inside OSx, and I looked inside folders.
Well, it seems that the script didn't run at all, since I have no "a2sd" neither "app2sd" on my /system/bin.
REEDIT:
I ran it again, now it seems that it actually ran.
I will provide my new pastebin later

http://pastebin.com/mx3PsHwZ
First run, then I got a reset. Then it reset-loop. With the same message.
Sorry man, it isn't quite ready for AOSP it seems
Those are a couple of after-install output, it doesn't do much though.
http://pastebin.com/ZVx5svQj

Boot loop only here, nandroid back to my previous ROM.
Sent from my HTC Desire using Tapatalk

antz88c said:
Boot loop only here, nandroid back to my previous ROM.
Sent from my HTC Desire using Tapatalk
Click to expand...
Click to collapse
Please provide logcat, otherwise your test wil be useless to the developer.

This sounds very interesting, and I would like to try and help when I can, which probably won't be for a couple of days.
But........for when that day comes.......how do I do a logcat?
Sorry, I am still relatively new to the whole Android thing.

StuMcBill said:
This sounds very interesting, and I would like to try and help when I can, which probably won't be for a couple of days.
But........for when that day comes.......how do I do a logcat?
Sorry, I am still relatively new to the whole Android thing.
Click to expand...
Click to collapse
yes, i got a bootloop on defrost 1.8.
how to do a logcat?

bradputt said:
yes, i got a bootloop on defrost 1.8.
how to do a logcat?
Click to expand...
Click to collapse
decompress android sdk (check on google for the sdk package, is quite small), then go inside the "tools" folder (I assume you have already your drivers installed).
then go on command prompt, and
Code:
adb logcat
will show the logcat.
Code:
adb logcat > bootlog.txt
will create the boot log (you won't actually see anything on screen since the output is redirected on the txt file.
You can:
start your phone
type adb logcat
CTRL+C when the phone is booted.
It will automatically stop if a reset occurs.
Then you go on pastebin (search on google) and paste the txt inside the pastebin.
And you can provide here simply the pastebin url that you can find after the submit button.

Nope...I can tell that's not my script. That must be what's already in Modaco...which means it's another file I haven't caught on the renaming script.
Are you using Modaco?
gatsu_1981 said:
well, it seems that it changed... Nothing.
http://pastebin.com/6D346gwX
Maybe the chef was already using your script?
Click to expand...
Click to collapse

Last time I saw that message, root wasn't working correctly. At least it wasn't working correctly on my phone.
Is there something different relating to root on these phones? Does the boot sequence have root access to /system (or is this phone have nand protection on it? I know the Evo has that but can be circumvented).
That part is just a piece that moves other apps2sd/dalvik-cache/zipalign programs so they don't interfere...the 2.7.5 Preview Fix 2 also removes those files during the flashing process, so that part really is only a failsafe.
The main program comes after that part (04apps2sd for busybox run-parts, a2sd for direct run).
gatsu_1981 said:
http://pastebin.com/mx3PsHwZ
First run, then I got a reset. Then it reset-loop. With the same message.
Sorry man, it isn't quite ready for AOSP it seems
Those are a couple of after-install output, it doesn't do much though.
http://pastebin.com/ZVx5svQj
Click to expand...
Click to collapse

The important piece is the part after the realignment program...the one that starts with:
[*] Starting Darktremor Apps2SD version 2.7.5 preview fix 1
The lines after that one is the Apps2SD portion.
gatsu_1981 said:
http://pastebin.com/mx3PsHwZ
First run, then I got a reset. Then it reset-loop. With the same message.
Sorry man, it isn't quite ready for AOSP it seems
Those are a couple of after-install output, it doesn't do much though.
http://pastebin.com/ZVx5svQj
Click to expand...
Click to collapse

tkirton said:
The important piece is the part after the realignment program...the one that starts with:
[*] Starting Darktremor Apps2SD version 2.7.5 preview fix 1
The lines after that one is the Apps2SD portion.
Click to expand...
Click to collapse
I can't understand what you mean.
Do you need some other line from adb logcat output? Since there is no more lines after the * line it just keeps resetting.
Or are you telling that it's installed? If so, why it keeps resetting our phone on froyo?
If I can help please send more flashable version or update this thread, I already have my nandroid so testing it for you will be very quick.

EDIT: double post...sorry.

[27th Jun][Sense] INT2SD, a new D2EXT method (added Alex-V GB HD INT2SD-S)

Progress update and INT2SD implementation request form!
With holidays starting, and more free time on my hands, I've decided to revive this project. Having my hard drive fail on me recently, and losing the request log, it has become obvious that I need a new system of handling requests, and it is here. If you have requested a ROM before, please send a request again, via this form.
Please submit all further requests via this form!
---
This is the INT2SD thread for Sense ROMs and their developers and users.
INT2SD thread for AOSP ROMs
What is INT2SD?
INT2SD doesn't use symlinks. It mounts ext partition on your SD to /data, thus eliminating the need for the mtd5 userdata partition. This makes the mtd5 userdata partition unneeded. It is used in conjunction with the fatsys HBOOT (more info later on), allowing most of the vital parts of a ROM to stay on the system partition without the need to symlink half of it to the SD due to memory shortage.
For now, there is only one ROM here, but more will come! If you wish to see INT2SD in your favorite ROM or in your own ROM, please post here!
INT2SD-S - "Speed" (default as of 29th Jun)
Main characteristics:
/data on SD ext, /data/data on internal
/data/data limited to 280 MB (probably enough for more than 100 user apps)
noticeably faster on slower cards
for use with CM7r2 HBOOT
Description:
The new "speed" flavour mounts ext to /data and userdata to /data/data, achieving great speed while still retaining excellent storage capabilities. It's used with the CM7r2 HBOOT. This is now the default flavour, offering great speed while still being able to hold a hefty amount of apps.
INT2SD-M - "Mass" (discontinued)
Main characteristics:
/data on SD ext
number of apps is only limited by ext size
requires a faster card
for use with fatsys HBOOT
Description:
The classic "mass" flavour mounts ext to /data, thus eliminating the need for the mtd5 userdata partition. It has proven to be slow even on some of the faster cards. Due to INT2SD-S being able to hold a very high number of applications, and still being much faster, this flavour is discontinued.
FAQ
For users: How to get this in your favorite ROM
For ROM developers: How to get this implemented in your ROM
Please fill out this form.
Cross-device implementations
For now, no. You may submit requests, but I won't be able to fulfill them for a while. I have quite a lot of real life work on my plate, not to mention a list of Desire ROMs I have to tend to. After that's done, I'll be happy to try blind-porting it to whichever device you wish, but my priority are Desire ROMs, primarily because it's a lot easier to implement INT2SD into ROMs for a phone I already have.
Universal update zips
Also, no. Each ROM is different, and due to the nature of INT2SD, it is simply not possible to make a one-for-all universal update zip. Every ROM requires tending to its peculiarities, especially Sense ROMs, and I would rather not take the change of trying to make one and end up with a flashable bootloop zip.
Why don't you just publish instructions on how to implement INT2SD for devs to use?
Proz0r said:
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.
Click to expand...
Click to collapse
Before you download!
Although it is for the best part bug free, INT2SD is still a fairly fresh project so I'm looking for as much input as I can get to fix possible bugs I haven't yet uncovered. If you try a ROM featuring INT2SD, please be sure to comment in this thread on your experience, even if it works great or doesn't work at all. If you wish to further support the project, there is a donate button in my signature. Although a nice sign of support and appreciation, donations are not obligatory!
Due to /data/data being on the SD, a high-class card is recommended.
Another thing is the HBOOT, fatsys. You must flash it before flashing any of the INT2SD Sense ROMs.
fatsys HBOOT
bravo_alphaspl-fatsys.img
MD5: 2272c1cb06f8eb743aa1c0ad4c3fa36b
PB99IMG-fatsys.zip
MD5: 4d6b2e74c241361237df047bfed5ff08
INT2SD Sense ROMs require a special HBOOT, fatsys. This special HBOOT has 427 MB dedicated for /system, 5 MB for /cache and 5 MB for /data and there is probably no ROM without INT2SD that would work on it properly. It was made so that the largest part of Desire's internal memory can be used for quick access to vital system files by storing them in /system instead of symlinking them to /sd-ext, therefore slowing the entire system down. There is still plenty of space for your apps if you make a large enough SD ext partition, since SD ext gets mounted to /data and the real, 5 MB mtd5 userdata partition goes unused. So, /data on SD ext, huge /system and no symlinks! Before flashing a Sense INT2SD ROM, make sure you have flashed the fatsys HBOOT!
Download
Thanks to Ante0 for hosting the files!
INT2SD implemented in:
Alex-V1.8 GB Sense HD INT2SD-M fatsys (Thread | Download)
Alex-V1.8 GB Sense HD INT2SD-S CM7r2 (Thread | Download in a minute)
Runnymede AIO 6.1.1 Beta (Thread)
Current bugs:
-
To do list for the next version:
-
Credits (alphabetically):
Alex-V - providing me with the first Sense ROM to implement INT2SD in
Ante0 - providing proper hosting for the zips
brabo, GShellz admin - huge help with bash scripts implemented in the ROMs
CM - a base ROM for implementing the method in
Droidzone - suggestions, help with HBOOTs
Hacre - massive assistance as well, kicking me to try and realise the main idea and for coming up with names "INT2SD" and "fatsys"
JieeHD - help with compiling/decompiling the boot.img files and his excellent guides on FYA
Pulser_g2 - massive assistance, ideas on the reboot bug and hosting
Richard Trip - making GingerVillain which now has a version featuring INT2SD
snq- - pointing out a huge typo and saving me multiple hours of pointless work
ubuntubhoy - a kick in the arse I needed
... and everyone else in the #villainrom IRC channel for help and mental support! Thank you all, and everyone I forgot to mention (PM!).
Disclamer: I'm not responsible if something goes wrong and wreaks havoc upon you, your phone, your card, any part of your phone, your friends, your family, your close or distant relatives and/or your pet, but I will gladly provide assistance if it does.

I'm not a dev at all, but I think this tool can help you: a too for making coustoms hboot by _thalamus
http://thalamus-hacking.blogspot.com/2011/07/custom-hbootsupdate.html
I have been using for months without any problem

Well, if you manage to learn how to reverse engineer and manipulate hboot, do share.. You might want to ask thalamus. I read that he'd done it.
Edit: Ah blackhawk_LA has already posted that.
@blackhawk_LA, is there an open source version of this tool?

blackhawk_LA said:
I'm not a dev at all, but I think this tool can help you: a too for making coustoms hboot by _thalamus
http://thalamus-hacking.blogspot.com/2011/07/custom-hbootsupdate.html
I have been using for months without any problem
Click to expand...
Click to collapse
Awesome, thanks! Wish there was a Linux version of it, luckily, I have Windows in dual-boot so I'll whip something up in a minute!
Droidzone said:
Well, if you manage to learn how to reverse engineer and manipulate hboot, do share.. You might want to ask thalamus. I read that he'd done it.
Edit: Ah blackhawk_LA has already posted that.
@blackhawk_LA, is there an open source version of this tool?
Click to expand...
Click to collapse
Yeah, I'm interested in how this works too.

Droidzone said:
@blackhawk_LA, is there an open source version of this tool?
Click to expand...
Click to collapse
I don't know, I just found that tool and start using it, I can't do anything more

@blackhawk_LA
Have you ever had any issues with the application? It's making a very important part of the system and if any errors would occur, it would be a catastrophe, which is why I am a bit apprehensive towards this program.

Make HBOOTS with it which have the same sizes as the HBOOTs from Alpharev, compare MD5, if they match, it's probably safe. Then you should be good to go to make a custom HBOOT with it

Never had any issue, I have used it very carefully to make at least 10 different custom hboots, and my phone is still alive
More statistics are needed to say it's completely safe but I think thalamus did a perfect job

I can say the program is very safe... have a dozen of custom hboots with it... no problem at all.
And looking forward to your INT2SD for sense..

here you go..
http://www.multiupload.com/N0B1RHYFPW

I'm very interested too!!! Thanks and keep up the awesome work!
When it'll be available I'll try it into my rom.

msandeep said:
here you go..
http://www.multiupload.com/N0B1RHYFPW
Click to expand...
Click to collapse
Thanks man, have you tested it?

You're not telling me everyone is too afraid to flash it, so everyone hopes someone else tries it to take the risk... -.-

Proz0r said:
Thanks man, have you tested it?
Click to expand...
Click to collapse
yes...its the one i use in my roms...and 40mb real data is really good to add apps like maps (that can updated) to the rom
with kind regards

Chaosz-X said:
You're not telling me everyone is too afraid to flash it, so everyone hopes someone else tries it to take the risk... -.-
Click to expand...
Click to collapse
I need my phone for the next couple of days and therefore cannot try it myself.
Alex-V said:
yes...its the one i use in my roms...and 40mb real data is really good to add apps like maps (that can updated) to the rom
with kind regards
Click to expand...
Click to collapse
Nice. Should real data be reduced to 5 MB or be left at 40 MB then, in INT2SD? Since it won't be needed for symlinks with it, I only see the point in having the 5 MB for the fsck log.

Word of advice.. Before flashing new hboot, use the alpharev downgrader. Otherwise you're screwed if the hboot turns out to be a corrupt file
Sent from my HTC Desire using Tapatalk

Thanks man, could you briefly describe what would happen if I would flash a corrupted HBOOT with and without flashing the downgrader prior?

Proz0r said:
Thanks man, could you briefly describe what would happen if I would flash a corrupted HBOOT with and without flashing the downgrader prior?
Click to expand...
Click to collapse
Well, AFAIK the HBOOT is also the white screen you get when you press Vol Down+Power, and it probably also involves the bootprocess normally, so I would say: broken HBOOT = a very nice brick.
Though I don't know what the downgrader is..

Yup, I know about that, I'm wondering about the downgrader too.

Proz0r said:
Yup, I know about that, I'm wondering about the downgrader too.
Click to expand...
Click to collapse
I'm always use the hboot-downgrade whenever I change hboot no matter whether the previous hboot is a lock hboot or an unlock hboot. It is always best to unlock the hboot before flashing a new one to be on a safe side.
Here is hboot with 427mb/system, 5mb/cache & 5mb/data as you mentioned here
Proz0r said:
Now, we need a volunteer to make the said zero-data HBOOT for 5 MB for /cache, 5 MB for /data and the rest for /system.
Click to expand...
Click to collapse
I tested the hboot by flashing it to my phone.. no problem to go to recovery, no problem to boot to bootloader. but I don't have any ROM which can fit a 5mb data partition to test. The lowest I ever go is 30mb/data.
Note: to change to another hboot.. use the hboot_downgrade first as this is a lock hboot.
Edit : Manage to squeeze the ROM to fit a 5mb/data ... so confirm the hboot works.

Database Info

welcome