Related
Development continues here: http://forum.xda-developers.com/showthread.php?t=881837
Universal lagfix kernel project.
This project is aimed at multiple audiences.
If you think you're an end user read on.
For lagfix and kernel developers check the second post.
Download, changelog, bugs and other links can be found at the third post.
Credits
ChainFire for the original cf-root initramfs
hardcore for the speedup hacks
nikademus for the compiled jfs utils
neldar for BackLightNotification
newmail for some kernel modules
RyanZA for OCLF and for being helpful
supercurio for Voodoo
ykk_five for being helpful (and for the memory tweaks)
z4ziggy for z4mod
and for everyone else I might have missed. (like myself - I'm an egoist you know... and for all the people that helped the guys I credited above. And for the people who helped the guys that helped the guys credited above. And for XDA of course.)
If you only care about points
OhmygodIcanget2kpointsatquadranttoobadI'vealreadysoldSGSbecauseitonlyhas300MBraminsteadof512asadvertisedandboughtadesirebecauseilikehowitcrapsatmultitouch.
For the rest of the people
What is this about?
This project has multiple aims:
A JPM based kernel with ext4, jfs, tun and BLN support
An init script which supports multiple lagfix schemes
Init.d support (without early script support)
A modified ClockWorkMod that
Has better support for some features of the SGS-I9000
Includes support for rooting the device
Includes support for switching the lagfix schemes
Has some tweaking options
Various additions that might help the other lagfix/kernel developers
How does this work?
Simply flash the kernel to any JPM/JP6 based, unlagfixed ROM. By default it won't apply any lagfix scheme, so you might use it as a simple ROM, with built in ClockworkMod + rooting support. If you have a complete ROM package (with dbdata.rfs and an older csc file (it won't work with some of the newer csc files) ) you can also flash it with the other parts, just replace the zImage in the PDA.tar with the one supplied. The ROM was tested with the original JP6 and JPM ROMs, and with my Multinational 3.0 ROM.
How can I use the extra features?
Reboot your phone to recovery mode. Under "Advanced ULK", there are some new options:
Reboot to download: switches to download mode
Run 2e recovery: Switches to 2e recovery
Install superuser: installs busybox and superuser to the phone
Lagfix options: switch between various lagfix schemes
Tweak options: switch between various startup tweaks
BLN options: Turns BackLightNotification on or off
Reset permissions: Resets permissions to the same state as init does
What are the lagfix schemes?
They are ways on how to format and bind the various filesystems. You can chose how you want to format the partitions (data,dbdata and cache), whether you want to use an extra loop device or not, and whether you want to bind some directories from /data to /dbdata.
There are also 8 included pre-defined schemes:
OCLF: /data stays at rfs, but has an ext2 loop device on top of it
Voodoo: /data is ext4, all others are kept at rfs
JFS Voodoo: /data is jfs, all others are still rfs
No-RFS Standard: /data is rfs+ext2, all other partitions are ext4
No-RFS Advanced: all partitions are ext4
No-RFS Advanced JFS: all partitions are jfs
No-RFS Overkill: turns on all options: everything is ext4+ext2 and /data/data is bound to /dbdata
No-RFS Overkill JFS: turns on all options: everything is jfs+ext2 and /data/data is bound to /dbdata
(If using the overkill scheme using the bind option is dangerous if using too much apps, so you should disable it in the advanced menu.)
Although I used the names OCLF and Voodoo, the ROM is not compatible with any of them, it's just a naming convention I used. Hope RyanZA and supercurio won't mind
Which one should I use?
You decide. OCLF or Voodoo might seem simple but they are actually working great (but for those you can actually use the originals, they are probably much more stable), while NO-RFS Overkill might seem cool, it is clearly an overkill.
What happens after I chose a lagfix scheme?
If the chosen one is different from the active one the kernel will reformat your device the next start. Before reformatting it will create a nandroid backup, reformats the device then restores the data from your backup.
Is this ROM safe
alpha 0.2 means no. Switching between lagfix schemes might break, and data loss (mostly database corruption) can happen if you're using a lot of loop devices. And this kernel isn't thorougly tested anyway.
How to switch to another kernel/ROM
After disabling the lagfix everything should be fine (except for the possible data corruption). You can always flash another complete ROM package over this using Odin, you'll lose all your data however.
I've found a bug
And you'll find more of them. I'll try to collect them and answers to them at post #3
Internal workings.
In this post I'll try to describe how this works, and how it might be useful for other people.
The Kernel uses both the pre-init trick and the bootlogos trick to load up, and do it's stuff. In the pre-init phase it does the following:
initializes the devices
checks the actual state of the partitions, and decides which lagfix scheme is active
checks the config (resides in /system/etc/lagfix.conf), and if they differ runs the converter application
if they don't differ then it starts to mount the devices, and let's init run.
if during the mounting a fatal error occurs, it prints the log, waits for a couple of seconds and reboots the device.
It does the filesystem checks by mounting and checking whether mounting succeded or not. To defend against samsung's init's reformatting, it simply removes the fat.format command.
In the post-init phase it removes some files (mainly the symlinks to busybox, so they won't interfere with the busybox installed on the system). It also reinstalls fat.format, because it might be needed later.
The lagfixer is built inside clockworkmod, which has the following advantages:
Can use nandroid backup
Can use the framebuffer to show the progress (this makes it much easier to debug problems)
Besides the lagfixer there is also a "graphsh" application, which will run a specified command and prints its output to the framebuffer (the reasons for this are the same: it's much easier to debug this way than to check a log file copied to the sdcard). If a fatal error occurs this command is run so the end-user can see some logs. (all of this is still pre-init). The only problem with using the framebuffer is that core android won't boot up properly if the framebuffer was initialized beforehand (it switches to QVGA with overlapped screens... it's actually quite fun to try using android that way). That's why I always reboot after using either 'graphsh' or 'lagfixer', except for recovery modes, because CWM is using the same framebuffer anyway.
The initramfs is "ro.debuggable=1" so if anything happens one can connect to the phone in adb root mode, to check for errors. Adb is enabled by default in both CWM and base android mode. I don't know the drawbacks of using debuggable=1.
CWM was modified in order to be able to handle the various lagfix schemes. If it tries to mount, unmount or format /data,/dbdata or /cache, it asks for the lagfixer to do the actual mount, unmount or format. Therefore if one saves or restores a backup it will always see and use the actual files, and not the loop device file.
There were some other minor modifications, like binding the home button too to the enter key, using /mnt/sdcard instead of /sdcard, and the ability to back up the efs partition too. (/efs won't be restored however).
There is also a small modification in how the updates work. If there is an update, the init will always run samsung's 2e recovery, if not it will use CWM (you can use CWM's menu to run an update using CWM if desired). This is to maximize compatibility with updates.
About the compiled files:
I had a hard time getting the binaries to work, even when compiling in static mode. All of the binaries are either compiled by me using bionic (AOSP), or used from other sources (but they seem to be using bionic too). The main advantage is that the recovery binary is actually only around 700k, but has a working busybox implementation, a working recovery and some other small stuff. The main problem is with the other binaries (mainly with e2fsprogs). If I could cut from the size the whole initramfs might fit into an official kernel, so it could be used by anyone.
Links
Da kernel 0.3 + BLN 2.2: http://forum.xda-developers.com/showpost.php?p=9157498&postcount=738
Da kernel 0.3: http://android.sztupy.hu/dl/Universal_lagfix_kernel_JPM_0.3.tar
Da kernel 0.2: http://android.sztupy.hu/dl/Universal_lagfix_kernel_JPM_0.2.tar
Da kernel 0.1: http://android.sztupy.hu/dl/Universal_lagfix_kernel_JPM_0.1.tar
Source of the modified CWM: http://github.com/sztupy/android_bootable_recovery
Source of vendor/samsung/galaxys: http://github.com/sztupy/android_vendor_samsung_galaxys
Kernel sources I'm using: http://github.com/sztupy/universal_lagfix_kernel
Bionic port of jfsutils: http://github.com/sztupy/android_external_jfsutils
The contents of the initramfs: http://github.com/sztupy/universal_lagfix_kernel_initramfs
Changelog
Version 0.3
- before the lagfix gets applied there are now multiple options to chose from:
-- backup+restore (the original way)
-- backup, but don't restore (this eventualy results in a factory reset)
-- no backup (this also results in a factory reset)
-- go to recovery mode (to debug)
-- erase config file (to get back to the old options)
- the screen glitch in the first screen is now gone (because the kernel got smaller)
- jfsutils are ported to bionic (takes less space)
- there is a new option that will do the same restore permissions run, as the init script does
- I also added a few fixes to the CWM fix_permissions script, although I don't tested them yet (so it might brick the phone)
- Added two more rooting option:
-- the old one simply copyes busybox, superuser and su to the phone and adds symlinks to busybox
-- the new ones will also remove some old toolbox commands, so if you use the shell a lot, they won't interfere. The first mode only removes the base utils, like ls,mkdir,rm or ln
-- the second mode removes every toolbox command that has an equivalent busybox command (like mount, lsmod, rmmod, etc.)
- Adeed an option to get back to 2e recovery from CWM
Remarks
It seems that formatting dbdata as rfs only works, if you use the 512 PIT file (more exacty it only works if you have used the 512 PIT file the last time you've ticked re-partition in odin). This is probably due to the fact thet the 512 and 803 pit files reserve different space for the dbdata and for the system partition (the 803 pit file reserves 40 units less for the dbdata than the 512 pit file)
Version 0.2
- efs is not backed up automatically during lagfixing (but it's still backed up during ordinary backups)
- added jfs support and some more lagfix schemes using jfs
- added backlightnotification support, with the option to turn it on and off
- added startup script tweaks support, with options to turn them on and off
- removed ext2 support for the base mounts (might be put back into later)
- bind now only binds /data/data (should use less space)
- some minor bugfixes relating
Remarks
- If Updating from 0.1 to 0.2: If binds were turned on you have to turn them off before updating. After the update has finished you can turn them back on if desired.
Known bugs
After the lagfix conversion is done the phone reboots and the lagfix conversion starts over again
This means that the conversion took place, but the result is not the same as was desired. You should reboot into recovery mode and remove the config file.
After rebooting I have a lot of FC's - After switching lagfix schemes I have a lot of FC's
This is probably because of a database corruption. Try loading an earllier backup.
Can't download anything from market
Some configurations might have this problem, I'm still trying to find out why this happens.
Can't download some apps, like angry birds from the market
Retry, it should work after a while. If it still fails remove the external sd.
Shutdown fails on some configurations
Until I find a way to hook onto the shutdown script this might happen on more complex configurations (like the NO-RFS overkill)
Can't get back to rfs on /dbdata
Reverting the lagfix on /dbdata only works if you used the 512 pit file the last time you checked re-partition in odin.
I for one am excited
Dan
Can't wait to see this.
I am waiting too ++++
Lol 100% teasing ^^
gingerbread?
shahadat said:
gingerbread?
Click to expand...
Click to collapse
would be a bit early
Fantastic
Testing now on a very stripped JP6...
very interresting i think i will give it a try hehehe
any feedback?
Would it be unsavory to say that I got a little motion in my pants after reading that first post?
Nah, I think we all did
Sounds great! And I'll wait for a few more version points on that alpha before I try it... but I'm tempted!
wonderful,i'll try it
Sztupy is this kernel and method usable with your multilingual rom v3.0?
Thanks
kurudisease said:
Sztupy is this kernel and method usable with your multilingual rom v3.0?
Thanks
Click to expand...
Click to collapse
check first post. Tested with JPM, JP6 and Multinational 3.0
Test drive
I just used it, I had no issue. Everything worked fine and there is no lag at all, still too soon to say it's faster than voodoo though(which I was very happy with). All data is still there and no problem! Im using JP6 with NO-RFS Extended. Quadrant score is ~1900 for anyone that want to know .
looks great! gonna try this
ist it possible to add in that also??
Startup script speed tweaks
http://forum.xda-developers.com/showthread.php?t=813309
I applied the no-rfs advanced fix and everything worked fine. No issues so far.
Thanks!
Hi all,
is it poosible to get a2sd+ on stock htc sense froyo?. I`m desperately running out of space, but i want to retain the stock froyo because of app updates, those on customs had issue not been able to update for example map, yt, etc. I may be wrong. In that case is there a rom with stock sense and latest froyo update?
Any info about rooting the handset with latest froyo update (stock) would also be helpful.
Thanks.
Hi There
I found this link the other day about forcing apps to the SD card without rooting on Froyo
http://myhtcdesire.com/category/tipstweaks
I have tried it a few times but just can't get it to work for me, perhaps I am missing something
Hope thios helps
JaykaySLO said:
Hi all,
is it poosible to get a2sd+ on stock htc sense froyo?. I`m desperately running out of space, but i want to retain the stock froyo because of app updates, those on customs had issue not been able to update for example map, yt, etc. I may be wrong. In that case is there a rom with stock sense and latest froyo update?
Any info about rooting the handset with latest froyo update (stock) would also be helpful.
Thanks.
Click to expand...
Click to collapse
DISCLAIMER: be very, very careful especially if you don't have S-OFF yet and plan to use this method. Mind your exact Desire variant and read all the info on listed stuff before attempting
I use a rooted stock rom with Darktremors Apps2SD method. You just have to install the scripts and modify the init.rc script as described in this thread
You will need to prepare an update.zip with the boot.img or have S-OFF hboot (like AlphaRev) to flash the boot partition on which the init.rc script resides.
It might be also possible to use flash_image, but I'm not sure it will be possible without S-OFF.
I used AmonRA 1.7.0.1 Recovery R5 to repartition the SD, as it seemed to me that using Clockwork which was embedded in Unrevoked 3.21, caused my last USB brick.
This will enable you to move not only the apps but also the dalvik cache to the SD's ext partition. The data from /data/data still remains in the internal storage, but moving the apps and dalvik cache is a huge space saver.
IIRC moving some apps data from the /data/data (I think it was systems apps mostly but honestly I don't recall) to the ext partition may result in errors.
Right now the situation looks like this on my phone:
Code:
# df -h /data
Filesystem Size Used Available Use% Mounted on
/dev/block/mtdblock5 147.6M 102.8M 44.9M 70% /data
# du -sh /system/sd/*
200.3M /system/sd/app
8.0M /system/sd/app-private
54.9M /system/sd/dalvik-cache
# ls -1 /system/sd/app /system/sd/app-private | wc -l
129
Additional bonus:
Because the ext partition is not being unmounted when connecting the phone as external storage to a computer, you don't end up with screwed up app links, and disappearing widgets when you do.
good luck
thanks for the info.
2 things: what is S-OFF and is there a windows based procedure as I dont have a *.nix system
JaykaySLO said:
thanks for the info.
2 things: what is S-OFF and is there a windows based procedure as I dont have a *.nix system
Click to expand...
Click to collapse
This particular *.nix system in my example is the Android OS as seen from the adb shell.
Please search the forum for what S-OFF is, there are tons of tutorials and howtos on this subject, it's basicly an unlocked variant of the HBOOT bootloader. The standard HBOOT won't allow you to flash partitions using fastboot mode like in earlier HTC models, Dream for example.
My advice is not to touch the HBOOT if you're not familiar with it as screwing something up when trying to change it is the quickest way to a bricked phone.
best of luck
"To begin, you'll need a Linux or a Mac system and basic knowledge on how to navigate through your Linux or Mac via a terminal program. The tools presented in this guide will only work with those systems."
As u said, its best I dont mess with hboot.
First things first - I think it should be possible to flash boot.img from an update.zip (just a regular update from the recovery mode). So no S-OFF modification needed this way.
Or just ask around the forum. It could be possible to flash the boot partition on the device using flash_image. Since my phone is already s-off I can't verify that.
JaykaySLO said:
"To begin, you'll need a Linux or a Mac system
and basic knowledge on how to navigate through your Linux or Mac via a terminal program. The tools presented in this guide will only work with those systems."
As u said, its best I dont mess with hboot.
Click to expand...
Click to collapse
Ah, that My bad, I thought you meant the code in my post.
Well you need a *.nix-ish environment for that particular solution, but that doesn't necessarily has to be an actual Linux / MacOS box.
There are a couple of ways to work around not having a Linux / MacOSX box:
First: If you have at least some knowledge of operating a unix shell, you can just download a live boot linux distro in the form of ISO image. Download and install VirtualBox, run the iso from there.
Second choice would be Cygwin, which is basically your *.nix environment for Windows.
Third is to install just a Windows perl interpreter needed for some of the scripts, and download a windows version of the mkbootimg binary, and just do the whole procedure manually. You pretty much just have to be able to run:
1. perl
2. cpio
3. mkbootimg
You can google all the needed exe's, and then you google "how to unpack boot.img" and take your pick - OR just take a peak inside the scripts from the semi-automatic solution (the thread you just quoted). The scripts are simplicity itself, pretty much don't differ much from a simple windows / dos batch file.
Fourth is to ask someone you trust to prepare the image for you
Either way, you have to modify the init.rc to be able to run the a2sd scipt on android boot.
OFC you can just start the process manually from a Terminal Emulator directly on the phone, and repeat it every time after you power on the phone, but that's hardly a comfortable way to go
Tell you what. If you feel really courageous I can fashion up a web form for you (and anyone else interested) which could allow you to submit a boot.img and have it modifed automatically, allow you to download a modified version. But: no warranties and also I might end up being an evil sneaky, sneaky bastard Your call
Thanks for the comprehensive info, but I`m not willing to experiment too much for the sake of not bricking the phone. I thought there might be a simpler solution....
+1 from me, getting headache from running out of space, I read online saying EXT3 was the method to go, but how to do it with rooted stock rom? (I head the only way to root Desire 2.2 is unrevoked) , please help
hongkongtom said:
+1 from me, getting headache from running out of space, I read online saying EXT3 was the method to go, but how to do it with rooted stock rom? (I head the only way to root Desire 2.2 is unrevoked) , please help
Click to expand...
Click to collapse
Like I wrote in the earlier posts. Partition with AmonRA recovery, install Darktremors APPS2SD, modify the init.rc script located on the boot partition, flash the modified boot - just browse the earlier posts. There are links to threads containing all the info you need.
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.
What?! Thanks darktremor, used this with my slide, will be testing and update this post asap with feedback.
Just curious though, is this meant for froyo based roms or should it work with gingerbread also?... guess I could test and see. Also do we still need to used the 'a2sd reinstall' and 'a2sd cachesd' commands to install it?
Sent from my T-Mobile G2 using XDA App
will this also work with sense roms?
g1junky said:
will this also work with sense roms?
Click to expand...
Click to collapse
Not sure, that's why we are testing it.
I can't get it to work on CM7 nightly 11 ( That I know of).
Used Clockworkmod to set up the ext partition (which doesn't specify which filesystem so i'm guessing either ext2 or ext3); set partition to 512mb and swap to 0mb.
Card partitioned successfully according to CWM; upon flashing the app2sd.zip the installation goes through all steps and posts that the install was successful even though the little check box by install successful is the only one that is starred. I noticed that during the install the script mounts /system and /data to write to them...not sure if that is affected by GB. I thought I read somewhere that this script was designed to check for ext4.
Hell, idk lol. I nandroided and went for it, these are my findings.
scratch that, there's a part two i missed that involves command line functions in the terminal emulator app. It looks like it's working to me.
Edit2: From what ive moved to /sd-ext so far everything seems to be working. Moved my apps, app data, dalvik cache and /data/data.
So far I havent experienced any data loss when moving /data/data.
There's no reason it shouldn't work with Gingerbread, other than the usual suspect of the rom doesn't launch scripts at boot or doesn't have EXT support.
As for the commands, you shouldn't have to rerun those commands if you are upgrading.
KCRic said:
What?! Thanks darktremor, used this with my slide, will be testing and update this post asap with feedback.
Just curious though, is this meant for froyo based roms or should it work with gingerbread also?... guess I could test and see. Also do we still need to used the 'a2sd reinstall' and 'a2sd cachesd' commands to install it?
Sent from my T-Mobile G2 using XDA App
Click to expand...
Click to collapse
Yes, it should. I'm running a Sense UI rom on my Evo and it has 2.7.5.3 Beta 02.
g1junky said:
will this also work with sense roms?
Click to expand...
Click to collapse
I can honestly say that so far everything seems to be working well on my end. Dropped ~100megs of internal space usage and sent it to the sd.
The phone does seem a bit snappier, does this style of app2sd stress the card more than usual?
hmm.
I'm running cm 7 nightly 11, set 512mb, 0mb swap and I think I got everything right. Strangely enough, I keep getting reboots every time i run a command in terminal.
edit: a2sd command*
SWEEET..........
I too can confirm that this works with CM7 Nightly "Gingerbread" sweet, installed the zip file from recovery, QUICK NOTE: Had to mount /system and mount /data in recovery before installing the zip file from sdcard. This is great apps2ext that works with any rom. Now in my titanium back ups it shows three seperate storge locations: internal, SD card and SDCard(a2sd) plus it restored apps I previously had on my ext.2 partition from when I was running Enoms Rom....sweeeeeet.
Also dont forget to run the command in adb shell:
Code:
/system/bin/a2sd cachesd
if you want to move dalvik cache to sd.
UPDATE: internal memory free reads out of 1.37GB Avail. there is 1.28GB FREE and Ive got 77 apps installed right now and about too install a lot more..........
FYI im runnning a 16gb class 10 sd card with a 1024mb ext.2 partition
Most of the code is similar to the previous version. I think the snappiness may be that your SD card is faster than internal storage.
stevencpoynter said:
I can honestly say that so far everything seems to be working well on my end. Dropped ~100megs of internal space usage and sent it to the sd.
The phone does seem a bit snappier, does this style of app2sd stress the card more than usual?
Click to expand...
Click to collapse
Did you type su before you run an a2sd command?
zarskee seven nine said:
I'm running cm 7 nightly 11, set 512mb, 0mb swap and I think I got everything right. Strangely enough, I keep getting reboots every time i run a command in terminal.
edit: a2sd command*
Click to expand...
Click to collapse
Just so everyone knows (may want to add this to the OP you know, so you don't get a million ?'s) these are the commands you HAVE to enter after flashing it in recovery.
Code:
su [ENTER]
cd /system/bin [ENTER]
sh a2sd cachesd [ENTER]
Your phone will reboot and will take a bit to complete - be patient because it's moving all your apps and the dalvik cache.
Notes: Your memory will still drop (not by much) over time because the apps will still store cached memory on the phone. To deal with this use the 'datasd' command to move that info to the sdcard also. Also, use the 'a2sd help' command to find all the functions you can perform with this. If you've used this before then all of this is irrelevant
Was so excited about this , It worked perfectly on CM7 nightly builds but when I went to update the Nightly build from 11 to 12, problems, keep getting reboot, since all my apps including titanium were on EXT, I could not access them, so the modification didn't stick from build to build, had to full data wipe, so I guess I'll be coming back to this when CM7 stable is realeased.
Yah I did. It's a beta on a nightly rom...I'm not surprised that something would be weird. I know it worked sending my dalvik cache to sd for sure, but as far as my apps being reinstalled on sd..im not sure. I followed the directions to the t and i know i didnt skip steps cause i used to use this on my nexus one
joemm said:
Was so excited about this , It worked perfectly on CM7 nightly builds but when I went to update the Nightly build from 11 to 12, problems, keep getting reboot, since all my apps including titanium were on EXT, I could not access them, so the modification didn't stick from build to build, had to full data wipe, so I guess I'll be coming back to this when CM7 stable is realeased.
Click to expand...
Click to collapse
You may have to remove the script in terminal, reinstall the rom than rerun the zip script. I think that should work if you want to keep using this on nightlies
If you change roms (including moving between different nightly builds), you will need to reflash Darktremor.
The only time you don't have to do that is if Darktremor is already added on the rom you are loading. Since CM7 doesn't have Darktremor installed as part of its package, you'll have to reflash each time you change nightly builds.
If you still don't have access to your programs, type a2sd reinstall
My apologies.
zarskee seven nine said:
You may have to remove the script in terminal, reinstall the rom than rerun the zip script. I think that should work if you want to keep using this on nightlies
Click to expand...
Click to collapse
after several days nothing new in this android development section, today i saw something new here, keep your good work, gonna try it when i get home
This is about three months overdue. Unfortunately, job, family and the holiday season got the best of me.
fajarep said:
after several days nothing new in this android development section, today i saw something new here, keep your good work, gonna try it when i get home
Click to expand...
Click to collapse
For me it seems that it doesn't stick. I tried it with cm7, flashed it in recovery and when I booted up to run the commands in terminal they weren't there. No a2sd at all. Guess I could shove all in the ROM prior to flashing and see if that works.
It's a simple procedure.I've got it working on my DDKL2.But you need a custom kernel.
1.Partition your sd card with cwm or minitool partition
2.Follow the procedures below to add init.d support
http://forum.xda-developers.com/showthread.php?t=1422061
3.Flash dt a2sd zip through cwm
http://forum.xda-developers.com/showthread.php?t=715940
4.Flash mr.maroc's pre-final 2.0 kernel by any method you want
http://forum.xda-developers.com/showthread.php?t=1550065
You can also use Terma's kernel for this.Because merruk kernel has some bugs in recovery.
you can get it here http://www.mediafire.com/?81d1acx1c19m9k5
5.Now open android terminal emulator and type the a2sd commands,it'll work
do this at your own risk
please thank the real devs who made cwm,a2sd scripts,kernels,init.d support, not me
nice tut. you can remove the step to add init.d support since it won't work on sgy. merruk kernel is already support a2sd and it should be run without any problem. if you want to activate init.d script, you can find the working step on mikstev's post about droidwall.
thnks mate.But i was unable to flash dt a2sd from merruk 2.0 cwm.So i had to flash the zip before flashing the kernel.And i think flashing scripts need init.d.So i had to add init.d support to stock rom.I've tried flashing kernel first then the script.It is somehow not working.
merruk said that his kernel is support init.d script. maybe its not really working. another option for a2sd you can use terma's kernel. it support init.d and a2sd script.
yeah, but i heard it is not booting up with stock.And merruk one is fast.Almost 2.5 fps increase in 2d alone.But the only problem is that it not restoring my nandroid.Any idea?
__________________________________
sent while doin' some burnouts
his cwm is not working for backup and restore. sometimes it has problem with update files too.
so that's why i was not able to flash a2sd script through his cwm.
_________________________________
sent while doin' some burnouts
kurotsugi said:
nice tut. you can remove the step to add init.d support since it won't work on sgy. merruk kernel is already support a2sd and it should be run without any problem. if you want to activate init.d script, you can find the working step on mikstev's post about droidwall.
Click to expand...
Click to collapse
i'm gonna try that in my stock ddla3.And will try to see if a2sd works
sent while doin' some burnouts
kurotsugi said:
his cwm is not working for backup and restore. sometimes it has problem with update files too.
Click to expand...
Click to collapse
Never try for backup and restore but for update files just unmount system and/or change update-binary file.
Hey everybody,
Have a strange problem. My phone keeps saying I'm low on space, despite the fact that I have a 1,5 gb sd-ext, and still ~880 mb free.
The sd is formatted with 4ext, and the partition is ext4. The SD card is class 10.
See the attached file for a visual of what I'm talking about.
Hope that someone can help
Cheers,
- H
EDIT:
Aaaaannd, now it's stuck on boot...
I had simmilar problems with various APP 2 SD scripts, including INT2EXT (+)
I had problems downloading form Play Store, because it told me that I don't have enough space, nor I could install from SD Card.
My suggestion is:
1.Wipe everything except SD Card and flash the rom again, you can't boot in it anyway, can you?
2. Find a rom to install, and flash it.
3. Search for better app2sd scripts, ( If using gingerbread you could use Link2SD - Used it alot in gingerbread, it doesn't work well in ICS & up )
My questions:
What rom are you using?
What APP2SD script are you using?
Click to expand...
Click to collapse
Silly me, noticed your signature.
If you are stuck in a bootloop, and don't know what to do, do following:
1. Turn off your phone.
2. Boot in recovery
3. Connect your phone to pc with USB
4. If you're using 4ext then it will be toggle usb storage, if clockworkmod ( classic ) then it will be under mounts
5. Copy a downloaded rom to your sd card.
6. Flash it!
Hey bro,
Thanks for the response..
No, it boots just fine.. it's just weird.. but I think I get it now.. It has something to do what the script actually moves to sd-ext, what HBOOT u use, i.e. how much space is allocated for system, data, etc.. ..
You see, before I got a Desire, I had a Samsung Galaxy Gio, running a custom CM 7 ROM, with Darktremor a2sd script. That worked PERFECTLY for me, coz I had set it up to move more or less everything to sd-ext. And although I had almost 1GB of apps, I didn't notice any lag or performance loss.
But now, I'm new to Desire, and I don't know a lot of these "new" a2sd scripts and how to configure them properly.. So it's gonna take a little time experimenting what works, and so on.
The first custom ROM for Desire I installed was a MildWild GB ROM - great ROM. Fast, stabile, just awesome..
But then I started experimenting with various ICS and JB ROMS, and then the problems began to show.. but basicly I think, and I sure dont wont to offend anybody, that the devs should make their ROMS without a a2sd script of their choosing, or at least give us an option to install it or not. Then we're (more) free to install whatever a2sd script we wish, without having to go through /init.d and removing existing script, and what not..
But yeah, it's all good.. Just got play around with it some more
Thanks anyway tho,
- H
EvilShadeZ said:
I had simmilar problems with various APP 2 SD scripts, including INT2EXT (+)
I had problems downloading form Play Store, because it told me that I don't have enough space, nor I could install from SD Card.
My suggestion is:
1.Wipe everything except SD Card and flash the rom again, you can't boot in it anyway, can you?
2. Find a rom to install, and flash it.
3. Search for better app2sd scripts, ( If using gingerbread you could use Link2SD - Used it alot in gingerbread, it doesn't work well in ICS & up )
Silly me, noticed your signature.
If you are stuck in a bootloop, and don't know what to do, do following:
1. Turn off your phone.
2. Boot in recovery
3. Connect your phone to pc with USB
4. If you're using 4ext then it will be toggle usb storage, if clockworkmod ( classic ) then it will be under mounts
5. Copy a downloaded rom to your sd card.
6. Flash it!
Click to expand...
Click to collapse
hhaznadar85 said:
Hey bro,
Thanks for the response..
No, it boots just fine.. it's just weird.. but I think I get it now.. It has something to do what the script actually moves to sd-ext, what HBOOT u use, i.e. how much space is allocated for system, data, etc.. ..
You see, before I got a Desire, I had a Samsung Galaxy Gio, running a custom CM 7 ROM, with Darktremor a2sd script. That worked PERFECTLY for me, coz I had set it up to move more or less everything to sd-ext. And although I had almost 1GB of apps, I didn't notice any lag or performance loss.
But now, I'm new to Desire, and I don't know a lot of these "new" a2sd scripts and how to configure them properly.. So it's gonna take a little time experimenting what works, and so on.
The first custom ROM for Desire I installed was a MildWild GB ROM - great ROM. Fast, stabile, just awesome..
But then I started experimenting with various ICS and JB ROMS, and then the problems began to show.. but basicly I think, and I sure dont wont to offend anybody, that the devs should make their ROMS without a a2sd script of their choosing, or at least give us an option to install it or not. Then we're (more) free to install whatever a2sd script we wish, without having to go through /init.d and removing existing script, and what not..
But yeah, it's all good.. Just got play around with it some more
Thanks anyway tho,
- H
Click to expand...
Click to collapse
How did you partition your sd-card? Using what?
Using 4ext - following ur guide actually... (tnx btw - awesome guide)
Sent from my HTC Desire using xda app-developers app
hhaznadar85 said:
Using 4ext - following ur guide actually... (tnx btw - awesome guide)
Sent from my HTC Desire using xda app-developers app
Click to expand...
Click to collapse
Try re-flashing the CM7 and try using INT2EXT+, sometimes APP2SD scripts doesn't work as they should, If you don't want to use scripts, you could use Link2SD - good choice aswell.
My setup:
Previously:
Stock Alpha Rev HBOOT
1.5 GB SD-EXT
4ext
cm7.2
Int2ext+
Now:
Everything the same except app2sd script and rom.
Evervolv Kitkat w/ built in App2SD
EvilShadeZ said:
Try re-flashing the CM7 and try using INT2EXT+, sometimes APP2SD scripts doesn't work as they should, If you don't want to use scripts, you could use Link2SD - good choice aswell.
My setup:
Previously:
Stock Alpha Rev HBOOT
1.5 GB SD-EXT
4ext
cm7.2
Int2ext+
Now:
Everything the same except app2sd script and rom.
Evervolv Kitkat w/ built in App2SD
Click to expand...
Click to collapse
Yeah, tell me about it.. altough, I've never had problems with the "old", original DarkTremmor a2sd script.. it's this "new" modified a2sd xdata thing that bugs me.. And I can't, for the life of me, figure out how to remove it completly, and replace it with the original DT a2sd script.. (it's built-in VJ's JB ROM, which I'm currently playing with.. )
But thanks anyway man,
- H
hhaznadar85 said:
Yeah, tell me about it.. altough, I've never had problems with the "old", original DarkTremmor a2sd script.. it's this "new" modified a2sd xdata thing that bugs me.. And I can't, for the life of me, figure out how to remove it completly, and replace it with the original DT a2sd script.. (it's built-in VJ's JB ROM, which I'm currently playing with.. )
But thanks anyway man,
- H
Click to expand...
Click to collapse
If there's app2sd in rom, but you need to activate it with terminal, then you might consider not to. Just give other APP2SD / Mount 2 SD scripts a try.
Link for INT2EXT:
CronMod Scripts ( INT2EXT )
I suggest you taking Int2Ext+
INT2EXT+
-Mounts /sd-ext to /data
-Leaves /data/data on internal for speed
-Works with EXT 2/3/4 filesystems
-ZipAligns /data/app on every boot
-No symlinks
Click to expand...
Click to collapse
Never really had problems with space running out on internal w/ it.
As ICS / JB roms go, I find them slow, and unresponsive, but kitkat is opposite
EvilShadeZ said:
If there's app2sd in rom, but you need to activate it with terminal, then you might consider not to. Just give other APP2SD / Mount 2 SD scripts a try.
Link for INT2EXT:
CronMod Scripts ( INT2EXT )
I suggest you taking Int2Ext+
Never really had problems with space running out on internal w/ it.
As ICS / JB roms go, I find them slow, and unresponsive, but kitkat is opposite
Click to expand...
Click to collapse
Wow, thanks a lot! These CronMod scripts look great. Gonna try it out tomorrow.
But this is just weird.. I tried pretty much everything; not activating it in terminal, then try to remove it; stuck on boot, tried replacing the script manually using root explorer --> stuck. Tried replacing the script in the ROM package (zip file) before flashing it --> stuck.. I'd just LOVE to see the decompiled framework, to see how the f**k it's embeded in this ROM, to make it so impossible to get rid of...?!?
Cheers,
- H
hhaznadar85 said:
Wow, thanks a lot! These CronMod scripts look great. Gonna try it out tomorrow.
But this is just weird.. I tried pretty much everything; not activating it in terminal, then try to remove it; stuck on boot, tried replacing the script manually using root explorer --> stuck. Tried replacing the script in the ROM package (zip file) before flashing it --> stuck.. I'd just LOVE to see the decompiled framework, to see how the f**k it's embeded in this ROM, to make it so impossible to get rid of...?!?
Cheers,
- H
Click to expand...
Click to collapse
If you want the same rom:
Open .zip package of the on pc.
Then Go in system/etc/init.d
delete something like: mountext and app2sd ( should look simmilar )
Then archive it (System, BOOT.img, META-INF ) Swith archiver program - Winrar perhaps? ( Using .ZIP ) extension.
Then put it in your sd card.
Then Wipe everything ( except sdcard )
Flash the rom.
Flash the Int2Ext script,
Wipe sd-ext again.
Boot.
If this doesn't work for you, you're doomed!
j/k. Just try another rom.
Highly suggest trying latest nightly for Evervolv Kitkat. (Evervolv / Bravo page.)
Since it's nightly you'll gonna find bugs, but from my experience it's better than all the ICS / JB roms. Might argue about GB roms.
If you decide to get KitKat, you can enable App2SD in it's terminal (not in the rom - fetch it at google play)l:
su
a2sd install
y
n
y
Click to expand...
Click to collapse
NO EVERVOLV NIGHTLY TALKS HERE!