[ROM] JACHero 2.3.5 - Fully Optimized HTCHero Port 7/6/09 8:00PM - G1 Android Development

WWARNING:You must Have The Correct Radio and Latest SPL! You can find them here (RADIO MUST BE INSTALLED FIRST) You can find it here
PLEASE DO YOUR RESEARCH BEFORE FLASHING ANY ROM INCLUDING MINE!!!
Please give credit if you use my work
This ROM is built from the WWE HTC Hero leak.
As with any other ROM there is a risk involved in the process, I'f you have any doubts you should just leave it alone or do some more research and get comfortable with what you are actually doing before proceeding!
Me and Drizzy will be teaming up to bring you new releases from now on. Soon 2.4 with alot more modifications, new kernel etc but untill then its BT time
DrizzyJAC r2.3.6
-Drizzy/JAC collab
-Pretty much the same as 2.3.5 but with framework/.apk's optimized
-Changed a2sd config to try and decrease loops
-/system/media moved to sdcard
JACHero r2.3.5
-app_s now moved to the sdcard @ system/sd/data/app_s
-Modified Rosie from coolbho3000 (thanks)
-CPU freq modifications in init.rc thanks to Cyanogen
-No longer overclocked by default set @ 384
-SMSReceiver service set to Highest priority
-Busybox only @ /sbin now
-apns-conf.xml update
-AudioFilter changes (should slightly increase volume and lower mic sensitivity)
-Added userinit.sh run support
-3G icon instead of H for Data
-App setup reverted to WWE format, only 3rd part apps in /data/app
-Cleaned up a2sd.sh script to prevent mounting and parsing redundancy and removed unneeded code for Hero builds
-Cleaned up update-script
***KNOWN ISSUE - use 3G/Edge to accept TOS for Market no WiFi, also first browser page on Wifi doesnt want to load at first on WiFi, go to any other site and you should be good
***Also swapper at 32/60 seems to be a sweet spot
JACHero r2.3.3
-Modified Rosie.apk
-db.hates.you custom wallpaper for JACHero
JACHero r2.3.2 - Had to pull the modified Rosie before releasing 2.3.2 it will be done soon.
-Removed cache_pressure from sysctl.conf
-Reverted AudioMOD
-updated contributors.html
JACHero r2.3.1
-replaced BT firmware in system/etc/firmware
-Max CPU set to 528
-APN changes in system/etc
-sysctl.conf changes system
-cleaned up unused/unneeded files in system/etc
-AudioMOD in /system/etc
-BT changes to enable pramods BT fix
-HCItool added to /system/bin to enable pramods BT fix
-Boot.img changes to conform to pramods BT fix
-removed launcher.apk/.odex
-removed learnmore.apk/.odex
-removed footprints/footprintswidget .apk/.odex
-removed HTCsync
JACHero r2.3
-Auto APPS2SD w/EXT2/EXT3 included script @ /system/bin/a2sd.sh
-2.6.27 Kernel - will be moving back to 2.6.29 eventually
-RAMDISK modifications
~auto mount for EXT2/3 partitions with noatime, nodirtime
~Updated sbin
~updated Trigger Binary
~calls to /data/init/rc system/init/rc
~PATH changes
~BlueTooth changes from Hero init.hero.rc and init.rc imported
-DalvikVM optimized
-Superuser Binary
-SD card placeholder
-BusyBox
-Added APN's for T-mobile users (SMS fix inlcuded in apn-conf.xml Thanks Horrorwolf)
-Trout keymappings
-Camera replaced with working Hero camera (still has rotate issue)
-Updated trout gps
-Multi-Touch
-Working WiFi
-Flash 9
-Audio libs updated (working audio and HTCMusic.apk)
-build.prop modifications to reflect proper device
-Sensor updates for Auto-Rotate (TouchFlo still won't rotate of course)
-sysctl.conf added to /system/etc
-auto backlight turned off by default in build.prop
-Wifi tether
-Swapper included
-changes to /data/app removed any .odex'd apps due to upgrade issues
-/system/lib files updated
PLEASE SUBMIT BUGS HERE http://code.google.com/p/jacheroplus
**********PLEASE READ BEFORE INSTALLING*********
Please use Cyanogen's recovery image!
Make sure you have a partitioned SD card with a FAT32 partition and a EXT3 partition. (EXT2 is supported also) If you do not this ROM will install but you will have little space left due to APPS2SD not running. I personally like the clean slate location for Hero and then i use the widgets i need if any.
When I install I check the ext filesystems first, if it tells you to go to console to manually check do it! After I've repaired the EXT partition or if it didn't need repair I will now wipe and then apply the update and reboot.
A walkthrough by forum member sxfx is posted one post below for install.
ALSO run as few widgets as possible folks!
DOWNLOADS
JACHero r2.3.6 SYM/BIND APPS2SD - MD5: 2A64747A1048FD175B1C1667D17E50FA
http://www.justanotherdev.slackdev.com
http://altepeter.com/justanotherdev/JACHero2.3.6.zip
JACHero r2.3.5 SYM/BIND APPS2SD - MD5: D80155D128ECCD3010768B52D9FB8EC0
http://www.justanotherdev.slackdev.com
http://altepeter.com/justanotherdev/JACHero2.3.5.zip
JACHero r2.3.3 SYM/BIND APPS2SD - MD5: 417ADE957153FD0BE5F3C7C9816B276F
http://www.justanotherdev.slackdev.com
http://altepeter.com/justanotherdev/JACHero2.3.3.zip
JACHero r2.3.2 SYM/BIND APPS2SD - MD5: a05c4d8d5abccd19c416b6febe40d6d2
http://www.justanotherdev.slackdev.com
http://altepeter.com/justanotherdev/JACHero2.3.2.zip
JACHero r2.3.1 SYM/BIND APPS2SD - MD5: 28f0afcc47d7766c71ecdb71e74e332a
http://www.justanotherdev.slackdev.com
http://altepeter.com/justanotherdev/JACHero2.3.1.zip
JACHero r2.3 SYM/BIND APPS2SD - MD5: D40A33ED2B1DED9181E1EA7B0AA96CC4
http://www.justanotherdev.slackdev.com
http://altepeter.com/justanotherdev/JACHero2.3.zip
JACHero r2.2.1 SYM/BIND APPS2SD - MD5: 35ad30f844862fb559ffcddadd4d49d2
http://www.justanotherdev.slackdev.com
JACHeror2.2.1 Fatality Merge SYM/BIND APPS2SD - MD5:87b22fc0baf6fc4138c48114388990b5
http://www.justanotherdev.slackdev.com
Thanks to daproy, JesusFreke, Cyanogen, Haykuro , xDan, Sangeet.003, Twisted Umbrella, and everyone else in the android community helping out.
If you like my work visit me at my Twitter.

No Off-Topic Posts!!!!!! This is not a general support thread!!!!
CREDIT:sxfx
Ok Guys.
I created this thread cause in the JACHero thread on at least every page everyone asks how to install it, what am I doing wrong, and why is it broken.
So let me give you step by steps of what exactly I have done for me and others to run Hero with out a problem. I will also create a thread with step by step on how to use Ubuntu Linux Live distro to partition your card.
Things you will need to make this work.
Your Brain
G1 Phone
SD Card reader
And the files I included in this thread.
My phone right now is running.
JACHero 2.3
NEW SPL
cyanogens recovery 1.2
8gb class 6sd with Swapper(Swap file on ext2 sd)
setCPU slightly overclock.
Results.
Ever since I did my new Buttons, and the SPL I included in this write up, I have not had one problem flashing any hero rom at all on my phone, nor did I ever have problem actually running hero roms.
So here goes.
First before you partition your card or do anything make sure your card is at least portioned to fat32, don't worry about any other partitions yet.
OK once you do that go ahead and take the radio zip file I am including in this thread and flash it on your phone.
But first make sure you don't already have new radio installed which is 2.22.19.26I THIS IS VERY IMPORTANT. To check what radio you have, power off your phone, and power it on while holding the camera button.
If you do have new radio you can continue on to flashing the new SPL.
Flashing your SPL. (PLEASE MAKE SURE YOU HAVE THE NEW BUTTONS INSTALLED)
Ok this is where it might get a little tricky, and you might require a SD card reader I know I did and frankly I think this is the best way to do it and I recommend every time you do put a new update on your sd card to update your phone do it through a card reader.
Now after you flash your SPL you might or I should say more then likely will get stuck at the T-Mobile G1 screen, this also might happen after new radio flash in the previous step. If this is the case do not freak out it's normal and your phone is not bricked, but this is why having a sd card reader is important.
Ok so Here is what you do after you have flashed new Radio and SPL(Note:The steps on running Linux live distro and using it to partition your card is coming up). Boot up Live distro of Ubuntu, when its done booting, go ahead and go into the partitioning program while your sd card is hooked up in the computer.
Go ahead and set up two partitions at this time. One EXT3, and of course the other one Fat32. Your ext3 partition doesn't have to be all that big. I actually have mine set up to 512.
Once you are done creating partitions, go ahead and put the latest JACHero on the FAT32 portion and flash away (don't forget to rename to update.zip).
At this point if you follow all of these steps there is no way possible that your phone should not boot right into the system to run the initial setup.
These steps pretty much walk you through steps as if you were starting with a phone that has completly nothing on it.
Also the first boot up after flashing the new ROM, might take a few mins at the HTC screen.
Once your phone loads up and you go through the setup process go ahead and run swapper, it should be an APP that's already pre-installed.
Once you run swapper go into the setting and change the location of your swap file from /sdcard/swapfile.swp to /system/sd/swap.swp
Here is the reason why. The default location is your FAT32 partition. If you all of a sudden mount your phone to the computer with the swap file running on FAT32 you will corrupt your sd card, and then you will have to wipe and reinstall everything.
If you set the location of your swap file on /system/sd/ that's actually your ext2/3 partition and never gets mounted and you never have to turn swapper off.
Well I hope this helps some of you out. I will be writing the walk through on loading up live distro of Linux and partitioning your card sometime today.
I have used this method on a couple different phones and it has worked each time. Also I really recommend installing cyanogens recovery 1.2, as its an excellent way of making a back up of your phone and doing future flashing.
If there is anything anyone thinks that could be done better feel free to post in here.
Remember different people have different ways. I have posted this way cause it has worked for me on my phone and two other phones I setup, and each time there was no hicups.
FILES:
Radio 2_22_19_26I
NEW SPL
CM-Recovery-1.2
Ubuntu Linux Download
DISCLAIMER:
I am not responsible for anything that you might have done to your phone by following these directions. Like I mentioned before so far every time I have used this method, I have had nothing but success.
================================================== =============================
XDA Users, KEEP THIS THREAD ON TOPIC OR IT TOO WILL GOTO THE TRASH!!!
================================================== =============================[/CENTER]

ArmandHammer said:
old one is on this site and on the market,
the new one is also on this site and on the market,
just search
Click to expand...
Click to collapse
at least u can tell me what should i search for in the market....?

ArmandHammer said:
CHMOD didnt work for me,
chmod did,
ill report back on the apps to sd
After using the old apps2sd app i got an infinite loop.
Click to expand...
Click to collapse
Yeep I was running into the same problem. It wasn't working for me in upper case either. It started working once I did it as
su <enter>
chmod 777 /data/app <enter>
exit <enter>
exit <enter>
I think it should be noted on the first pase that chmod 777 should be in lowercase.

zgmf-x322a said:
at least u can tell me what should i search for in the market....?
Click to expand...
Click to collapse
AppsToSd search that in the market(old version)
I didnt buy the new one, its in the new and improved apps to sd thread
Alright back on topic

Okay so 1.4 is out now. He says Apps2Sd is included. I've never used Apps2sd and really don't know how to. So do I have to do anything with the 1.4 build to move it onto my sd card or will it automatically do it for me?

Run the APPS2D app with your EXT2/FAT32 partitioned SD card in and reboot that is all.
To make sure it is mounted go to the Terminal and type df, you should see
system/sd with your partitions size attributes etc
EXT3 support is next on the list.

justanothercrowd said:
Run the APPS2D app with your EXT2/FAT32 partitioned SD card in and reboot that is all.
To make sure it is mounted go to the Terminal and type df, you should see
system/sd with your partitions size attributes etc
Click to expand...
Click to collapse
Perfect thanks! Is this the only difference in 1.4? So I have to create the partition myself first correct? I thought Apps2sd created the partition for me. Oh well let me go create the partitions lol.
PS: the CHMOD command doesnt seem to work in upper case. Lower case only.

So will this new Rom with the app2sd app move everything but leave rosie.apk & launcher on the phone memory? Or is there something else that needs to be done?

justanothercrowd said:
Run the APPS2D app with your EXT2/FAT32 partitioned SD card in and reboot that is all.
To make sure it is mounted go to the Terminal and type df, you should see
system/sd with your partitions size attributes etc
EXT3 support is next on the list.
Click to expand...
Click to collapse
thanks a lot, you are doing it just right
question, if my apps are already in ext2 (system/sd/app) will it work? or they will now be located in : system/sd/app_s ?
thank you

Somebody respond with how much available space they have left after running the APPS2SD.apk

i've chmod 777'd the hell outta my system/app folder and I still can't download apps. I've run the command from terminal on phone from ADB Shell, from inside the folder, from the root, as root every possible way and I still can't download anything.
Would it make a difference if I had tried downloading from market before applying commands?

I did a lot of testing and left all the files needed to keep this ROM stable and FAST under /data/app_s
Somethings work better under the app_s directory un-linked.
Everything else is under /data/app like a normal ROM so normal APPS2SD methods work. Since Marcus already has the app up I just included it...its only 18kb anyways.

This isnt off topic but an inquery to the EXT3 comming soon
Here is a question. Everyone is head over heels about using ext3 which is understandable. But why when i create and use an ext3 partition, why does everything running from my sd slow down by far?
i have 2 partitions on my sd ones an ext2 ones ext3 if i switch my link to m ext partition everything is fine.. if i switch it to my ext3 it gets about .5x slower

rahduke said:
i've chmod 777'd the hell outta my system/app folder and I still can't download apps. I've run the command from terminal on phone from ADB Shell, from inside the folder, from the root, as root every possible way and I still can't download anything.
Would it make a difference if I had tried downloading from market before applying commands?
Click to expand...
Click to collapse
If it means anything i tried to download an app then forgot about the commands, typed the commands and it worked.

I've posted this before, but got no response.
Is anyone else having trouble getting wifi turned on? I can actually use the Wifi tether app, but just trying to turn it on myself, it fails.
Thoughts?
Bryan

TheGeekNextDoor said:
I've posted this before, but got no response.
Is anyone else having trouble getting wifi turned on? I can actually use the Wifi tether app, but just trying to turn it on myself, it fails.
Thoughts?
Bryan
Click to expand...
Click to collapse
i tried moving and linking the local file once and that made my wifi never be able to turn it on until i deleted the link and moved it back

ArmandHammer said:
If it means anything i tried to download an app then forgot about the commands, typed the commands and it worked.
Click to expand...
Click to collapse
did you reset after commands?

fleshdeep said:
Somebody respond with how much available space they have left after running the APPS2SD.apk
Click to expand...
Click to collapse
43 mb AWESOME!!! the apps to sd works now in v1.4 great job.
did you reset after commands?
Click to expand...
Click to collapse
i just ran the commands and then pressed exit twice.

pentace said:
i tried moving and linking the local file once and that made my wifi never be able to turn it on until i deleted the link and moved it back
Click to expand...
Click to collapse
I've learned a lot about linking, but I am not sure what local file you are refering to that would make my wifi work for me. Any help is appreciated.
Bryan

Related

[ROM] ZeroXd - Puzzles are FUN [8/13/2009 - 2:30PM EST]

http://twistedumbrella.googlepages.com/index.htm
All the necessary files can be found there, including my GScripts.
This is also where all the download links to NEW versions are posted
HEHE... Oh, you wait... Just wait.... New things.... Shiny, new things....
Housekeeping:
Back everything up. This means run some sort of data backup if you want to keep your settings
You may also want to run a nandroid backup in recovery (if all else fails, you can restore it)
Warnings:
You MUST have the newest SPL
You MUST have a Class 6 SD Card
You MUST know how to read
You MUST have 3 partitions
You MUST have at least 256MB EXT
If you don't, I WILL NOT HELP YOU! (Sorry, too many times...)
and no, I will NOT teach your grandmother how to root, install, or configure this ROM
Copy the update to the SD card (rename if using pre-1.4 recovery)
Boot into recovery mode (Home and Power)
Launch the Console and press Enter
***** Not Needed in 3.80 and Above *****
Commands to execute:
mount -a
rm -r system/sd/app_s
rm system/sd/dalvik-cache/* (if dalvik to sd was done)
reboot (Immediately press the Home key again)
**********************************
Apply the update (ZeroXd-v3.5.zip under any zip if using recovery 1.4, update.zip if pre-1.4)
After going through initial setup open console
Commands to execute:
runonce
(if it gives any issues, you may need to run this first:
mount -o remount,rw -t yaffs /dev/block/mtdblock3 /system
and that will make system rewritable)
After this has completed, reboot the phone normally.
http://twistedumbrella.slackdev.com/ZeroXd-v3.5.zip
MD5: a3958418020dfffce5028066c041b137
http://twistedumbrella.slackdev.com/ZeroXd-v3.52.zip
MD5: 1f14243a415caee74f14b1110ae07c40
http://twistedumbrella.slackdev.com/ZeroXd-v3.60.zip
MD5: a835a12717ea8144db24b3ab71f7c0bb
http://twistedumbrella.slackdev.com/ZeroXd-v3.75r2.zip
MD5: c852a0d48ad3a2030244bb269312b124
http://twistedumbrella.slackdev.com/ZeroXd-v3.80.zip
MD5: 816a1e88fcb191c9323857ae2b5fdeac
http://twistedumbrella.slackdev.com/ZeroXd-v3.82.zip
MD5: 78f963f6ce0318bc4064384a26c08359
http://twistedumbrella.slackdev.com/ZeroXd-v3.82r3.zip
MD5: a6b8382d654b05e6fe0dd91696b2085b
Average Results:
Fast, Highly responsive Hero with minimal internal usage
3.50 ROM is JACxHero-v1.2 with:
New Lockscreen based on old JACHero
VoiceDialer added in for speech commands
Some fun scripts to make things FAST
3.52 ROM is Drizzy's JACxHero-v1.2 with:
3.50 Modifications added
3.60 ROM is Drizzy's NewVision with:
3.52 Modifications added
Fixed SMS Priority to ensure messaging
3.75(r2) ROM is Drizzy's NewVision V2 with:
3.60 Modifications added
Some added apps with a new Hero theme
(r2) Updated scripts for speed complaints
It is called USER.CONF for a reason ya know
(r2) Cyanogens method of data transfering
The new data method relinks but no wipe
3.80 ROM is Drizzy's Touch3D V3 + Full V3 with:
3.75r2 Modifications added
Legacy boot.img for compatibility issues
(r2) Fixed rotation and some MAJOR bug issues
(r3) LED Support in the Userinit (works, not perfect)
Backup commands added in runonce (copies to SD)
Due to "nasty" complaints, old userinit backed up
The attatchments to this post are the Free Version of Hero Update and a Hero themed Chomp. There is also a link to a Hero Optimized Userinit.sh with User.conf file set. It has options to set SMS priority to urgent (for older builds), perform and maintain dalvik2sd and perform (cannot be maintained) data2sd upon boot. You can also configure cpu and swap options by editing the User.conf file to your liking. There are also the modified LED commands for text messaging (will be building from this).
http://twistedumbrella.slackdev.com/herouserinit.zip
Is this his 1.6 he just released?
And what APPS2SD method can/I should use? Auto Lucid, Apps2sd v1, Apps2sd v2, and/or cyanogen recovery?
Auctionedllama said:
Is this his 1.6 he just released?
Click to expand...
Click to collapse
Yeah, but it assumes you will apps to sd so I put back a lot that was removed, just as apps instead of system components.
Now if I apps2sd, Rosie and the core apps will stay on the actual phone, correct? Also, what Apps2sd method would you recommend my friend?
going to load this now. debating between this, ravenge's rogers, cyan's rogers and this rom. speed+exchange more important aspects...
Auctionedllama said:
Now if I apps2sd, Rosie and the core apps will stay on the actual phone, correct? Also, what Apps2sd method would you recommend my friend?
Click to expand...
Click to collapse
If you're on ext2 I recommend doing 2 with the package as is. If you're on ext3, flash the other boot and do autolucid, or 1. JAC's boot doesn't support ext3 very well, but soon I will get it all merged down.
you keep the launcher and rosie? and this doesnt have what manup did does it? and weather?
So correct me if I am wrong. Since this is UnionFS will apps2sd method 2 work? Please say yes!
Jrbourque said:
you keep the launcher and rosie? and this doesnt have what manup did does it? and weather?
Click to expand...
Click to collapse
djdeviance said:
So correct me if I am wrong. Since this is UnionFS will apps2sd method 2 work? Please say yes!
Click to expand...
Click to collapse
This does have manups mods because I liked launcher and yes unionfs does work, although if it keeps looping on the partition let me know. It did on mine but I have ext3. I think they put the scriipt in the wrong place but I need verification before I change the update.
Just to extra clarify things, all I do is install Apps2sdV2, and click move apps, and then move cache?
(if I'm on EXT2?)
twistedumbrella said:
This does have manups mods because I liked launcher and yes unionfs does work, although if it keeps looping on the partition let me know. It did on mine but I have ext3. I think they put the scriipt in the wrong place but I need verification before I change the update.
Click to expand...
Click to collapse
ok looks like I'm gonna flash.
can someone post if the weather widget works and weather apk
Once I find out about APPS2SDv2 because I'm tired of boot looping, I'll flash and report back.
Jrbourque said:
can someone post if the weather widget works and weather apk
Click to expand...
Click to collapse
after adding the weather widget and choosing a city, it just displays tap to go to weather application...
How do I make it support ext3???...can I flash that file through terminal?
Auctionedllama said:
Just to extra clarify things, all I do is install Apps2sdV2, and click move apps, and then move cache?
(if I'm on EXT2?)
Click to expand...
Click to collapse
I also need to make sure of this.
jc1337 said:
I also need to make sure of this.
Click to expand...
Click to collapse
Yeah I'm sitting here about to wipe and flash, but I need to double check this before I go any further!
Flash through fastboot, or by the flash_image command
Yes AppsToSD2 should be that simple
As for differences, did you check the very first post?
twistedumbrella said:
Flash through fastboot, or by the flash_image command
Yes AppsToSD2 should be that simple
As for differences, did you check the very first post?
Click to expand...
Click to collapse
I have flashed, signing into my gmail account and then will try the apps2sd.
All is going well so far.
twistedumbrella said:
Flash through fastboot, or by the flash_image command
Yes AppsToSD2 should be that simple
As for differences, did you check the very first post?
Click to expand...
Click to collapse
Alright, and you mean through recovery, not fastboot correct? Also, would you recommend a wipe before the flash, and a fresh format of the Ext2 partition if you were using APPS2SD before?

[FIXED] [ROM] CyanogenMod 4.2.5 PLUS RAM hack, better a2sd, auto swap, nav/facebook

I would suggest doing a Nandroid backup - just in case
Download: http://www.mediafire.com/?umznkzjtgdz
Someone mentioned a bug for a couple app crashes
All right, screw it. I am going to remove the CM stuff and just push the nav/fb, ram hack, etc as just an incremental update
To-Do:
Music.apk - Rewrite to ignore music less than 30sec long (aka voicemails)
BFS 310 Kernel with 10mb RAM hack (BFS 310 hasn't been tested by anyone else yet, why not try)
Add Fix_Permissions v2.03 (running the default 1.31 right now)
ZipAlign all apps (including Google apps)
[Suggest more!]
Converting from Cliq/Hero/1.5 - see below for instructions
Need Google Apps - see below for instructions
Includes:
10mb hack - working on adding bfs310 (seriously if you can help PLEASE DO)
Google Navigation works
Facebook included
Includes HTC IME
Clears cache of old files
Installs RA Recovery
MANY MANY TWEAKS
Adjusted a2sd (mt3g: one time copy from /system/sd to data for apps)
Note: this discontinues A2SD from then on for better performance after apps have been copied, am making script to copy back to SD
For fastest possible speed: have a swap partition on your SD card
The ROM will load a2sd for G1's
If you don't have /system/sd (and just swap partition), it will swapon to that
Trick is it utilises both Cyanogen's compcache plus the swap
Then with 10mb hack - hell this is a perfectly fast ROM
See at the bottom if you need Google Apps (starting on clean build or converting from any 1.5 ROM (Hero/Cliq) OR if you are starting with a blank phone lol (aka no system partition at all))
Hero/Cliq/1.5: Yyou will have to run the thing at the bottom for your phone to convert to 1.6 Donut - run that first, then run main zip).. if you still have probs see the bottom of this post
If you are switching from Hero or Cliq see the bottom
This rom does NOT include Google Apps
Install this first for Google Apps:
http://www.mediafire.com/?z3ozzmyzrad
If coming from Hero/Cliq
Run recovery mode
Hit console
Type these commands:
mount /data
cd /data/data
rm -r com.google.*
rm -r com.htc.*
rm -r com.android.*
Thanks to Cyanogen, Maxisma(for my base on a2sd), daproy (RAM hack),
Amon_RA (recovery image)
For help:
Search on Wave for the title of this post
Follow me on Twitter @wesgarner
wesgarner said:
Trick is it utilises both Cyanogen's compcache plus the swap for a very FAST build
Click to expand...
Click to collapse
I remember reading somewhere that this will lead to problems, and should not be done. From my understanding you should use one or the other, not both.
(otherwise wouldn't we see alot more Devs using that trick?)
can a no wipe update be done from cm 4.2.5?
Thanks for you~
hey guys Good work
Only thing ive ever had come out of the 10mb hack was random reboots, random ringtones. phone ringing when noone was calling. crashing getting texts...
But thanks for the effort lol
Didn't work. Caused me to get stuck on G1 boot screen for an hour. Then totally wiped and again sat there on the G1 boot screen. What is odd is that for some reason my recovery image disappeared and went to JF 1.42 so I couldn't even use recovery. Now I am trying to get my phone back to the way it was.
Fortunately, I still had all the files I needed on my SD card to get me back to where I was. i reinstalled the recovery image and then was able to load my recovery image again. How it got to JF 1.42 (which hasn't been on the phone is many months) is beyond me. I have been doing phone mods for many years and this is the first one that didn't work out.
So, no go?
Unexpected end of Archive......
I tried to do the same thing (cm 2.4.5 + ramhack + swap) but got nowhere, system became sluggish. This should work very well in theory (this should be fast as dwang but with all cm goodies) but I haven't been able to make it work so I'm following this thread and see how it works.
pascanu said:
I tried to do the same thing (cm 2.4.5 + ramhack + swap) but got nowhere, system became sluggish. This should work very well in theory (this should be fast as dwang but with all cm goodies) but I haven't been able to make it work so I'm following this thread and see how it works.
Click to expand...
Click to collapse
i used to run CM 2.4.x with ramhack and swap no problem, but since 2.4.5 the ramhack slowed my system down so much i just decided it would be better to go without it
btmec said:
Didn't work. Caused me to get stuck on G1 boot screen for an hour. Then totally wiped and again sat there on the G1 boot screen. What is odd is that for some reason my recovery image disappeared and went to JF 1.42 so I couldn't even use recovery. Now I am trying to get my phone back to the way it was.
Fortunately, I still had all the files I needed on my SD card to get me back to where I was. i reinstalled the recovery image and then was able to load my recovery image again. How it got to JF 1.42 (which hasn't been on the phone is many months) is beyond me. I have been doing phone mods for many years and this is the first one that didn't work out.
Click to expand...
Click to collapse
Looking into the G1 bug now, did you get a logcat?
Going to try to test on my old G1 in a few, if you have Wave get on there if you want to help debug
sacredsoul said:
can a no wipe update be done from cm 4.2.5?
Click to expand...
Click to collapse
Yup no wipe
no work.
Did not work ... G1 stays in boot screen and reboot ...
Takenover83 said:
I remember reading somewhere that this will lead to problems, and should not be done. From my understanding you should use one or the other, not both.
(otherwise wouldn't we see alot more Devs using that trick?)
Click to expand...
Click to collapse
Well with the newer compcache modules, it doesn't seem to cause any problems
grafyman said:
Did not work ... G1 stays in boot screen and reboot ...
Click to expand...
Click to collapse
Yea I am about to test on my G1 to look around for the bug - my main phone is my myTouch so I didn't test before I posted LOL - my bad on that (it is just in this recent version since worked fine on a friend's G1 before this post)
If you have wave, could you get on there if you want to help debug?
If you have a logcat, just post it here or on pastebin and shoot me the link on Twitter (@wesgarner)
One big thing I am trying to work on here is going through and doing some things Cyanogen couldn't do
Next version I am going to do zipalign on the Google Apps to post that (on a sep update zip for people who prefer to stay legal, hope I don't get a D&S - don't think anyone else has)
I am thinking about doing a choose your kernel like Cyrowski did here - good idea?
Please give any suggestions, this just seems a good way to do some playing around and experimenting that is a project by everybody - developers and users
Also, next project: Write a test into Music.apk to ignore files less than 30sec (I have my voicemails through Visual Voicemail and Google Voice)
It is annoying as crap! Going to get the GIT for Music.apk later today
Can someone mirror this or create a torrent? media fire is so slow today
Ok im seeding but warning if you go from 4.2.5 like me you may get a boot loop like i am right now good thing i backed up
Torrent link: http://bit.ly/blah234
guys this rom is ****. i flashed a number of times, then i wiped all partitions and tried again. dosent work just g1 boot loops, im going to stop seeding. dont trust this guy this rom is bad
LOL, dude, why are people keep thinking any Rom based on the same rom works better? Wake up people. If you use Cyanogen, use Cyanogen, If you use Dwang, use Dwang. any other so call hack does not make it better. Wake up, wake Up. Wake Up. LOL.
I have been using the so call Ram hack, it does NOT make it better after long hour of usage. It slows it down. At least on my G1. I reverted back to Stock boot img, it just WORKS.

[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)

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.
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.

data2extV2.2 and a2sd-blaster (updated 5/6/2011)

unCoRrUpTeD DATA2EXT
&
A2SD BLASTER​
DATA2EXT
What is data2ext?
data2ext was started as a way to move the entire contents of the data partition to an ext partition on the sdcard. It gives you a way to increase the size of your data partition and also increase benchmark scores. This should work on most phones as it detects the block location of the sdcard, regardless if it is /dev/block/mmcblk0 or /dev/block/mmcblk1.
SETUP
The following commands are optional and need to be put in before the 1st or 2nd boot
Make sure that the data partition is mounted before issueing the commands
Code:
adb shell
mount /data
*Converting to ext3 or ext4 on first boot
Code:
echo "extA" > /data/.d2ext
A is either 2, 3 or 4, depending on what ext format you want.
In the future you can convert to ext3 or ext4 even after data is on the sdcard.
*Formatting the ext partition on first boot to ensure a clean and fresh filesystem
(Note: This does not need to be done)
Code:
echo "extA format" > /data/.d2ext
A is either 2, 3 or 4, depending on what ext format you want.
*Create a custom read_ahead speed for the sdcard.
(Info on what it does can be found here courtesy of brainmaster)
Code:
echo XXXX > /data/.sdrw
XXXX is any value you want. By default it will be set at 2048.
You will need your sdcard partitioned with at least 1 ext partition. Either you can do that through your recovery or go here to download a script that will repartition without loosing your fat32 contents.
WARNING:
Due to some changes made, you will need to either backup your apps and do a fresh install or install over my data2extV1 script. Do not try and use the a2sd-copy-and-blast method at this time.
Install on a ROM you are currently running that has a2sd or data2ext enabled:
1. Reboot into recovery
2. Flash a2sd-copy-and-blast.zip
3. Flash data2ext.zip
4. Once your phone has booted, reboot again (This is to limit the time of the first boot and the setup won't be complete until you reboot.)
Install on a ROM you are currently running that has my previous data2ext installed:
1. Reboot into recovery
2. Flash data2ext.zip
3. Reboot your phone.
Install on a ROM you are currently running that does not have a2sd or data2ext enabled:
1. Reboot into recovery
2. Flash data2ext.zip
3. Once your phone has booted, reboot again (This is to limit the time of the first boot and the setup won't be complete until you reboot.)
Install on a fresh intall of a rom:
(It doesn't matter if it has a2sd or not as this will remove all a2sd scripts if they are present)
1. Reboot into recovery
2, Wipe everything
3. Flash ROM
4. Flash data2ext.zip
5. Reboot
6. Once your phone has booted, reboot again (This is to limit the time of the first boot and the setup won't be complete until you reboot.)
[/SIZE]
A2SD-BLASTER
unCoRrUpTeD-a2sd-blaster.zip: Use this one to remove a2sd from the ROM if you are doing a fresh install or want to keep all data on your ext partition for data2ext
unCoRrUpTeD-a2sd-copy-and-blast.zip: Use this one if the ROM your are currently running is using a2sd. It will remove a2sd from it and copy all apps from the ext partition back onto your phone's /data partition.
Changelog
data2ext-V2.2:Fixed issue with V2.1 freezing on boot, due to deleting /system/bin
data2ext-V2.1:Added a check for those already using data2ext
data2ext-V2:included checks if the ROM has the needed files, included the option to change the format to ext3 or ext4 on first boot, added sdcard read ahead tweak. Reboot needed after any install, added custom_backup_list.txt for new installs or updates
a2sd-copy-and-blast_V2:changed to move data back to phone along with apps
data2ext-V1: 1st release
a2sd-blaster: 1st release
a2sd-copy-and-blast: 1st release
i'm going to test on a fresh install of liquidsense and hopefully this works b/c i just switched back to gingerbread to get the speed of data2ext and i just installed all my apps again so hopefully you found the fix....i'll post back with results
sigh....bootloops.........i'm going back to gingerbread....
someday i wish someone could get app2sd removed so that i could have data2ext working on sense 2.1
kifno said:
sigh....bootloops.........i'm going back to gingerbread....
someday i wish someone could get app2sd removed so that i could have data2ext working on sense 2.1
Click to expand...
Click to collapse
I just downloaded and flashed liquidsense and then a2sd_removal.zip. Booted right up.
It does remove busybox.a2sd, but in all testing across several different phones that has not caused any problems as the regular busybox is still in the ROM. The copy_remove.zip was missing some code to mount data before copying over, but I changed that one as well.
unCoRrUpTeD said:
unCoRrUpTeD A2SD BLASTER
&
DATA2EXT​
SETUP:
You will need your sdcard partitioned with at least 1 ext partition. Either you can do that through your recovery or go here to download a script that will repartition without loosing your fat32 contents.
If you are currently running a rom with a2sd of data2ext enabled you will need to reboot into recovery and flash a2sd-copy-and-blast.zip and then data2ext.zip
If you are doing a fresh install or running a rom with a2sd disabled or nonexistent then flash data2ext.zip
If setting this up after a fresh install you will need to reboot the phone after it has booted up. This is only done to speed up the first boot startup time. Once it is running you can do whatever you want, and on the next reboot it will set everything up.
A2SD-BLASTER
unCoRrUpTeD-a2sd-blaster.zip: Use this one to remove a2sd from the ROM if you are doing a fresh install or want to keep all data on your ext partition for data2ext
unCoRrUpTeD-a2sd-copy-and-blast.zip: Use this one if the ROM your are currently running is using a2sd. It will remove a2sd from it and copy all apps from the ext partition back onto your phone's /data partition.
Click to expand...
Click to collapse
OKay so is this the correct instructions:
- wipe everything
- partition sd card to have 512mb ext2 (that's what i always use for ext)
- flash fresh install of rom
- flash data2ext.zip
- then reboot into system?
or do i
- wipe everything
- partition sd card to have 512mb ext2 (that's what i always use for ext)
- flash fresh install of rom
- reboot into rom
- reboot recovery
- then flash data2ext.zip?
thanks for all they help you've given me
kifno said:
OKay so is this the correct instructions:
- wipe everything
- partition sd card to have 512mb ext2 (that's what i always use for ext)
- flash fresh install of rom
- flash data2ext.zip
- then reboot into system?
or do i
- wipe everything
- partition sd card to have 512mb ext2 (that's what i always use for ext)
- flash fresh install of rom
- reboot into rom
- reboot recovery
- then flash data2ext.zip?
thanks for all they help you've given me
Click to expand...
Click to collapse
Updated OP.
Should be pretty clear now.
before i dive into this, bro, some questions if you will:
this moves everything in /data to sd-ext right? by everything, does this include even dalvik cache?
if, for any reason, i decide or need to return everything back to internal storage i could simply flash a2sd-copy-and-blast right?
thanks in advance!
EDIT 1:
bootloop! htc legend on cm6.1 w/ darktremor a2sd; ext3 partition. restored everything to internal storage, flashed a2sd-blaster then data2ext-V1. after restart, bootloop ..will try on ext2 partition later
EDIT 2:
bootloop also on ext2..was really hoping this mod will work on my phone
maxq1 said:
before i dive into this, bro, some questions if you will:
this moves everything in /data to sd-ext right? by everything, does this include even dalvik cache?
if, for any reason, i decide or need to return everything back to internal storage i could simply flash a2sd-copy-and-blast right?
thanks in advance!
EDIT 1:
bootloop! htc legend on cm6.1 w/ darktremor a2sd; ext3 partition. restored everything to internal storage, flashed a2sd-blaster then data2ext-V1. after restart, bootloop ..will try on ext2 partition later
EDIT 2:
bootloop also on ext2..was really hoping this mod will work on my phone
Click to expand...
Click to collapse
I'll look into it as this is also part of my dual-boot script that I am working on, which means that if this doesn't work on certain phones then the dual boot scripts won't work on all phones.
^ cool, man! i'm waiting on that as well. thanks!
this didn't give me bootloops so you've completed that step
but this didn't work at all
here's what i did:
- partition sd card
- wipe everything
- fresh install NFX stock 2.31.651.7 oxed (without apps2sd)
- install data2ext.zip
- reboot into rom
- once i approached the initial lock screen, i did adb shell reboot
- then i signed into google
- let it sync and load
- then i check application storage and it said 136mb
- so then installed titanium backup from makret
- after install i checked internal storage
- it went down to 131mb!
summary: not only did internal storage not say like 4xxmb like it does when gingerbread uses data2ext w/ 512mb, internal storage didn't even say anything different than the stock amount of internal storage
also even if the interal storage didn't correctly say how much storage we had after installing 1 app i knew this zip didn't take affect b/c of the great lost in internal storage
again i testing on nfx stock 2.31.651.7 (without apps2sd and oxed) and this did not work
edit: after fresh install method i tried the method where the rom doesn't have apps2sd.....this still doesn't work
this would be awesome if i got this to work on my rom but it doesn't even work on my rom's base.... and you haven't fixed yet....but i'll be checking up on this for fixes whenever you release a fix
I might be able to get to it tomorrow. If not it will be Wednesday. Been hard at work on my dualboot script, which uses a very complicated method of determining how to set it up. I only need to make a couple changes to this and symlink everything differently. I'm going to download nfx's Rom without a2sd as I had been testing on his a2sd stock Rom.
Sent from my dual-booted liquidsense 2.1
unCoRrUpTeD said:
I might be able to get to it tomorrow. If not it will be Wednesday. Been hard at work on my dualboot script, which uses a very complicated method of determining how to set it up. I only need to make a couple changes to this and symlink everything differently. I'm going to download nfx's Rom without a2sd as I had been testing on his a2sd stock Rom.
Sent from my dual-booted liquidsense 2.1
Click to expand...
Click to collapse
After talking with TGF about getting this to work with sense roms he said we need the correct e2fsck for sense 2.1 roms and also the libext2fs.so file for sense. Then we need to make sure busybox is intergrated into the ron by default. He couldn't help me get those files so the rest was left up to me but he did correct the script for sense roms though. Thought. I'd share that with you so that you could try and get this working for sense roms on the hero CDMA after you complete your dual boot mod.
unCoRrUpTeD said:
Install on a ROM you are currently running that has a2sd or data2ext enabled:
1. Reboot into recovery
2. Flash a2sd-copy-and-blast.zip
3. Flash data2ext.zip
4. Reboot your phone
Install on a ROM you are currently running that does not have a2sd or data2ext enabled:
1. Reboot into recovery
2. Flash data2ext.zip
3. Reboot your phone
Install on a fresh intall of a rom:
(It doesn't matter if it has a2sd or not as this will remove all a2sd scripts if they are present)
1. Reboot into recovery
2, Wipe everything...
A2SD-BLASTER[/B]
unCoRrUpTeD-a2sd-blaster.zip: Use this one to remove a2sd from the ROM if you are doing a fresh install or want to keep...
unCoRrUpTeD-a2sd-copy-and-blast.zip: Use this one if the ROM your are currently running is using a2sd...
Click to expand...
Click to collapse
Sorry to sound noobish here, but I'm running AOSP 2.2.1 on my heroc. i have moved all my apps to internal using titanium backup (in preparation for this). i have formatted by sdcard using cwm 3.0.0.5, with a 512 MB partition and 0 (zero) swap. Now I want to flash your cool data2ext! Which one do I use?
Important note! I have already tried flashing GrammarFreak's data2ext (ext2 version), and for some reason it didn't take.
And just now when I go into terminal emulator,
Code:
su
and then
Code:
data2ext -- enable
I get the following: "data2ext already enabled but not active."
Does this mess things up terribly? Can I still flash your stuff?
Yours,
Jim
[email protected] said:
Sorry to sound noobish here, but I'm running AOSP 2.2.1 on my heroc. i have moved all my apps to internal using titanium backup (in preparation for this). i have formatted by sdcard using cwm 3.0.0.5, with a 512 MB partition and 0 (zero) swap. Now I want to flash your cool data2ext! Which one do I use?
Important note! I have already tried flashing GrammarFreak's data2ext (ext2 version), and for some reason it didn't take.
And just now when I go into terminal emulator,
Code:
su
and then
Code:
data2ext -- enable
I get the following: "data2ext already enabled but not active."
Does this mess things up terribly? Can I still flash your stuff?
Yours,
Jim
Click to expand...
Click to collapse
I haven't changed what is here. It might work, might not. I tested on a couple of roms and it worked, but didn't work on others. Nandroid first. Flash a2sd-blaster.zip which removes any instance of a2sd and data2ext. Flash data2ext.zip.
Like I said I haven't changed it yet. Been working on my dualboot script. So it might work and might not.
unCoRrUpTeD said:
I haven't changed what is here. It might work, might not. I tested on a couple of roms and it worked, but didn't work on others. Nandroid first. Flash a2sd-blaster.zip which removes any instance of a2sd and data2ext. Flash data2ext.zip.
Like I said I haven't changed it yet. Been working on my dualboot script. So it might work and might not.
Click to expand...
Click to collapse
That's completely cool. Thanks for taking the time to reply!
Yrs,
Jim
...perfect...
very good apps.... i ' m very happy....
now i have used data2ext on new installation of rom and work perfectly on ideos with 1gb ext4....
it's a beautiful utility for adding space to internal memory...
excellent...
later i try with an already installed rom with a2sd....
thank you very much!!!!
update: i have a problem, apparently all work perfectly but when i active wifi the cell reboot :-(
grifovunque said:
update: i have a problem, apparently all work perfectly but when i active wifi the cell reboot :-(
Click to expand...
Click to collapse
same problem with wifi..
on my ideos script runs very very well but when i enabled wifi my phone reboot..sigh
i hope that's you can fix it..
however thanks,great script!
Works semi-great on a heavily modded Sprint stock rom. Overall, it took a few reboots, but is working. I have 409mb available. The only issue I found is that AlarmDroid does not work. I tried moving it to system/app and still not loading...i may try moving it in the actual rom, reflash everything and see what happens. The offending apk is not your fault by any means, just listing what I came across. I flashed the zip after I used your sd partitioner. On first reboot after flash, phone was normal...read that you said it takes another reboot, so I performed another reboot. On 2nd reboot, the whole system FC (just about every app came up and FC), performed another reboot. On 3rd reboot, AlarmDroid complained - but everything seemed fine...did a few more reboots, but it looks like the 3rd is the magic number for my rom...I may include this in my personal rom (obviously removing duplicate files like bb
I have one request and that is to make it more like the other scripts and allow it to be enabled, or not enabled. I am not saying have an on/off switch as the scripting for that would be extremely complicated, but have an off until enabled on switch for those looking to throw this in a rom. It is possible to put this in a rom, but some may not want it enabled right off the bat (like me)...Could it be possible to have an enabler script that upon running would move files where they needed to go? Like for instance have the tmp folder, add a file called enabled2e (or something) that runs mountpoints.sh and moves /tmp/50data2ext to system/etc/init.d...I dunno, just spitballing
evilvoice said:
Works semi-great on a heavily modded Sprint stock rom. Overall, it took a few reboots, but is working. I have 409mb available. The only issue I found is that AlarmDroid does not work. I tried moving it to system/app and still not loading...i may try moving it in the actual rom, reflash everything and see what happens. The offending apk is not your fault by any means, just listing what I came across. I flashed the zip after I used your sd partitioner. On first reboot after flash, phone was normal...read that you said it takes another reboot, so I performed another reboot. On 2nd reboot, the whole system FC (just about every app came up and FC), performed another reboot. On 3rd reboot, AlarmDroid complained - but everything seemed fine...did a few more reboots, but it looks like the 3rd is the magic number for my rom...I may include this in my personal rom (obviously removing duplicate files like bb
I have one request and that is to make it more like the other scripts and allow it to be enabled, or not enabled. I am not saying have an on/off switch as the scripting for that would be extremely complicated, but have an off until enabled on switch for those looking to throw this in a rom. It is possible to put this in a rom, but some may not want it enabled right off the bat (like me)...Could it be possible to have an enabler script that upon running would move files where they needed to go? Like for instance have the tmp folder, add a file called enabled2e (or something) that runs mountpoints.sh and moves /tmp/50data2ext to system/etc/init.d...I dunno, just spitballing
Click to expand...
Click to collapse
Creating a flag to enable or disable is pretty simple. Not sure if I put one in there. I'm not looking at it right now. All it needs is ...
Code:
if [ -f /data/.data2ext ];then
xxxx -------
xxxx /
xxxx | Existing commands
xxxx \
xxxx -------
else
# move everything back to /data
cp -a /xxx/xxxx/* /data
exit 0
I'm going to update this at one point with some checks and a different way to mount everything, which will reduce the overall script size and make it more compatible with more roms and phones. It's been a while since I looked at it , but I know that I include busybox in somethings as it has more functions than what is normally provided in the roms.

Categories

Resources