Related
have the g1 rooted with jf1.5 rom , OTA, hrdSPL and trying to use apps2sd. The apps2sd application always tells me that I don't have my card formatted correctly and to follow the guide, which I followed explicitly (I think). Here is the output of print within parted for my sdcard using adb shell. Does any one know what is wrong?
Code:
Model: SD SU01G (sd/mmc)
Disk /dev/block/mmcblk0: 1016MB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Number Start End Size Type File system Flags
1 32.3kB 699MB 699MB primary fat32 lba
2 699MB 984MB 285MB primary ext3
3 984MB 1016MB 31.8MB primary linux-swap(v1)
open up on of cyanogen's roms, take out his a2sd script, either adb push it or drip into to the .zip on your computer and resign, or look for terminal commands.
that should work work, try and grab an older version that doesn't have compache built into the script or just comment out the lines for compache
Moving to Cyanogen
The point of this was to ensure card was formatted correctly before moving to Cyanogen since I have virtually no space left and want the increased performance from his release. Are you saying that if I just switch ROMs my sdcard looks good-to-go for a2sd?
sammarcow said:
The point of this was to ensure card was formatted correctly before moving to Cyanogen since I have virtually no space left and want the increased performance from his release. Are you saying that if I just switch ROMs my sdcard looks good-to-go for a2sd?
Click to expand...
Click to collapse
sorry i guess i didn't think enough (just woke up), yeah you will be fine going to cyanogen's roms with that setup. i thought you wanted a2sd on the jf rom.
Hi,
I'm looking at moving from JF1.5 ADP to the Hero release for my G1. I currently use a Class 6 memory card formated to use Apps2SD. I'm also using the latest radio SPL, but not sure which version of recovery image.
Would I be right in thinking I could jump to the recovery image section and continue from there, or would I have to fully wipe my memory card and reformat it before doing this
Just follow the instructions in the thread below to install the recovery image.
http://forum.xda-developers.com/showthread.php?p=3915123
Anytime you go from Hero to a pastry you will have to wipe. From a pastry to Hero you might be ok without a wipe but it's always best if you do.
Always best to wipe...
Do you currently have a swap partition? I believe hero requires all 3 partitions. Fat32, Ext3/4, Swap
Someone correct me please if I am wrong.
Hi managed to do this last night - had to download the hboot spl, as I had different spl but same version number, then had to format cards as only had 2 partitions (1 ext2 and 1 fat32) - so setup as per some instructions for a 8gb card leaving the swap @ 32mb
used the Modaco firmware
walkerx said:
Hi managed to do this last night - had to download the hboot spl, as I had different spl but same version number, then had to format cards as only had 2 partitions (1 ext2 and 1 fat32) - so setup as per some instructions for a 8gb card leaving the swap @ 32mb
used the Modaco firmware
Click to expand...
Click to collapse
So is it working or do you need help? You post is confusing.
I think he got it working. He just showed his solution and end result
I got a shiny new class 6 16GB sd card. I partitioned it at about 15.5GB fat32 and 512 ext2, using the info in cyanogen's wiki: http://wiki.cyanogenmod.com/index.php/Apps2SD_On_CyanogenMod
From there I did the ext3 and then the ext4 updates.
Although I've searched for answers for a few hours now, I've been unable to determine why the device slows to a crawl at each point of user interaction at this point. Even unlocking the screen can time out...
I backed out the changes and copied the apps back over to internal storage and everything is zippy again, so at this point I am looking for suggestions. One thing I noticed was that when I used parted to delete the ext partition so the apps wouldn't go back to the card on the next boot, it still listed the ext partition as ext2. Can someone running ext3 or 4 let me know whether parted lists their partitions as such or if they are always reported as ext2?
What other techniques should I try? I would very much like to make this work as I get constant low-space warnings in my current setup. Thanks.
jasper1 said:
I got a shiny new class 6 16GB sd card. I partitioned it at about 15.5GB fat32 and 512 ext2, using the info in cyanogen's wiki: http://wiki.cyanogenmod.com/index.php/Apps2SD_On_CyanogenMod
From there I did the ext3 and then the ext4 updates.
Although I've searched for answers for a few hours now, I've been unable to determine why the device slows to a crawl at each point of user interaction at this point. Even unlocking the screen can time out...
I backed out the changes and copied the apps back over to internal storage and everything is zippy again, so at this point I am looking for suggestions. One thing I noticed was that when I used parted to delete the ext partition so the apps wouldn't go back to the card on the next boot, it still listed the ext partition as ext2. Can someone running ext3 or 4 let me know whether parted lists their partitions as such or if they are always reported as ext2?
What other techniques should I try? I would very much like to make this work as I get constant low-space warnings in my current setup. Thanks.
Click to expand...
Click to collapse
just used parted to check and it says ext4 .... try using this guide .. worked really well for me to partition my sd ... also if you're having all these problems try wiping dalvik-cache and even data and your ext* partition if it comes down to it
What recovery image are you using?
jndd333 said:
What recovery image are you using?
Click to expand...
Click to collapse
amon ra's 1.2.3
EDIT: lol thought you were the OP
A more careful walk through the partitioning process and I can confirm that everything works as expected, as well as confirming that if upgrade_fs fails, then ext2 is a total dog. One particularly confusing thing was tracking down whether a swap partition was needed or not, but on the latest cyan roms it isn't so I skipped that one.
This error (error: /dev/block/mmcblk0: unrecognised disk label) is plaguing my life and I don't know how to get around it. I have scoured the net for two days and I only find other people asking about the error with no real solutions offered.
Basically, I am trying to set up my 16gb SD to work on my rooted G1 recently flashed to CyanogenMod 5.0.7-test2. I have tried running with all three current recovery builds (the RA build flat out states it doesn't work with apps2sd so I have gone with Cyanogen's 1.4)
Using parted in console and following all of the standard partition steps (found all over the web) I was previously able to get the three partitions set up with RA's recovery 1.6.2, however the apps2sd didn't work and no one seemed to have a work around to get it to work, so I started from scratch.
Now with Cyanogen's 1.4 recovery, I can't get the ext2 partition in at all. I get the above error every time. What am I doing wrong? What can I do to get this working? Please help as I know there are dozens of others with this issue and I have seen no solutions for Android. (Did find something on a Linux forum, but waaaayyyy over my head.)
Thanks,
JS
after the mmcblk0 did you remember to put "p" then the # which i think stands for what partition the secondary is on?
after the mmcblk0 did you remember to put "p" then the # which i think stands for what partition the secondary is on?
I did not. At what point would I do that? This is what I did, (where would the "P(#)" go?
Boot into recovery (Power Button + Home)
Go to console and hit Enter
Type ‘Parted /dev/block/mmcblk0’
Type ‘print’ to check existing partitions and storage size
If any partitions exist remove by typing ‘rm 1’ for first, ‘rm 2’ for second…
For new partitions it will be total 16384 (16GB) minus 96mb for swap minus 500mb for ext3 (15788, 16288, 16384)
Type ‘mkpartfs primary fat32 0 15776’
Type ‘mkpartfs primary ext2 15776 16288’
Type ‘mkpartfs primary swap-linux 16288 16384’
Type 'print' to see changes
Type 'quit' to leave parted
Type upgrade_fs to move ext2 to ext3
Reboot
I have this working flawlessly on my 2GB card, so it must be a hardware issue.
Just_s said:
after the mmcblk0 did you remember to put "p" then the # which i think stands for what partition the secondary is on?
I did not. At what point would I do that? This is what I did, (where would the "P(#)" go?
Boot into recovery (Power Button + Home)
Go to console and hit Enter
Type ‘Parted /dev/block/mmcblk0’
Type ‘print’ to check existing partitions and storage size
If any partitions exist remove by typing ‘rm 1’ for first, ‘rm 2’ for second…
For new partitions it will be total 16384 (16GB) minus 96mb for swap minus 500mb for ext3 (15788, 16288, 16384)
Type ‘mkpartfs primary fat32 0 15776’
Type ‘mkpartfs primary ext2 15776 16288’
Type ‘mkpartfs primary swap-linux 16288 16384’
Type 'print' to see changes
Type 'quit' to leave parted
Type upgrade_fs to move ext2 to ext3
Reboot
I have this working flawlessly on my 2GB card, so it must be a hardware issue.
Click to expand...
Click to collapse
why don't you just use amon_ras recovery to partition sdcard.
also, cyanogen's recovery will be updated way less than amon_ras - if it's ever updated again. either do amon_ras or clockwork.
why don't you just use amon_ras recovery to partition sdcard
I actually started with AmonRa's and I love it, but it says it is not compatible with apps2sd which is pretty much the main reason I got an Android phone, so tat was out for me. I posted about a half dozen queries on other sites asking if anyone could tell me how to get apps2sd working if I was running AmonRa 1.6.2 and I received no responses. If you know how that could work, I would be extremely elated and grateful!!
Ideally, I would get to run CyanogenMod 5.0.7test2 on my G1 running Amon Ra recover 1.6.2 with my 16GB card and all of my apps stored on the card via apps2sd. But I couldn't get it to work.
Right now, I have CyanogenMod 5.0.7test2 on my G1 running CM recover 1.4 with my 2GB card and all of my apps stored on the card via apps2sd and it is working flawlessly, just not much room left for media files.
BTW, I appreciate the advice, I haven't had much luck in any of the forums.
apps2sd has nothing to do with the recovery image, apps2sd has to do with the ROM itself. When you hear that, it's because cyanogen moved the place for apps2sd or something, which honestly changed nothing as long as you still partition your sdcard. It technically DID, but that's more under-the-hood. You just can't wipe ext partition, which you can do with a simple adb command. I personally don't know it as I've never used apps2sd.
Cyanogen's recovery is pretty old, and like I said, he probably won't update it. Also, don't worry about not being able to wipe your ext partition. Amon_RA will roll an update around soon enough to fix this and you won't have to type the code in yourself anymore. Well, maybe. I'm not him so I can't promise you that, but I'm sure he will.
Did you solve it?
Did you figure out how to get around the unrecognized disk label problem?
i had the same problem, for me was helpfully
format sd card and partition again in cwm
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.
Reserved...created because a Tattoo rom has it as part of its build.
I just tried to flash Apps2SD 2.7.5 RC1, but installation fails:
------------------------------------------------
E: Failure at line 48:
set_perm 0 0 0777 SYSTEM:xbin/a2sd
Installation aborted.
-----------------------------------------------
Is there something that I can do?
I love this script. I think I'm going to be using it in the next version of my ROM. Thanks for making it, it's great
It shouldn't do that.
Try the RC3 (about to release it): http://www.darktremor.info/files/a2sd/dtapps2sd-2.7.5-rc3-signed.zip
If that doesn't work, let me know and we go from there. There's a recovery log file that is created...I just have to remember where it is at (was looking at it just this morning).
dancer_69 said:
I just tried to flash Apps2SD 2.7.5 RC1, but installation fails:
------------------------------------------------
E: Failure at line 48:
set_perm 0 0 0777 SYSTEM:xbin/a2sd
Installation aborted.
-----------------------------------------------
Is there something that I can do?
Click to expand...
Click to collapse
alredy running rc3 in our rom hehe
Which rom is that?
danne_jo said:
alredy running rc3 in our rom hehe
Click to expand...
Click to collapse
PuzzleROM
Sent from my Tattoo using XDA App
tkirton said:
Which rom is that?
Click to expand...
Click to collapse
As said before, PuzzleROM
http://forum.xda-developers.com/showthread.php?t=749932&page=10
I saw that during my sweeps of the forums...added into my list.
danne_jo said:
As said before, PuzzleROM
http://forum.xda-developers.com/showthread.php?t=749932&page=10
Click to expand...
Click to collapse
i have installed your APPS2SD on a Tattoo with a shipped non modified rom (I rooted my phone and have ARMON 1.6 recovery though) fine however after the reboot I didn't notice any difference so i checked the with apps2sd check command. here is the output
# a2sd check
a2sd check
[ ] Apps2SD is launching...
[ ] Starting Apps2SD Check Program.
[ ] Searching for Mount Point...
[Ô£ö] Mount point /data/sd located.
[ ] Checking for ext partition
[Ô£û] Ext partition found, but not mounted.
Your rom may not be setup to run Apps2SD.
Check with your rom developer if the boot image
is programmed to run Apps2SD.
Your partition may be using an EXT4 partition,
but your rom may not support EXT4. Repartition
your SD card to use EXT2 or EXT3.
please note i have formatted my sd and have done a ext2->ext3 already.
what should i do now ?
pardol said:
i have installed your APPS2SD on a Tattoo with a shipped non modified rom (I rooted my phone and have ARMON 1.6 recovery though) fine however after the reboot I didn't notice any difference so i checked the with apps2sd check command. here is the output
# a2sd check
a2sd check
[ ] Apps2SD is launching...
[ ] Starting Apps2SD Check Program.
[ ] Searching for Mount Point...
[Ô£ö] Mount point /data/sd located.
[ ] Checking for ext partition
[Ô£û] Ext partition found, but not mounted.
Your rom may not be setup to run Apps2SD.
Check with your rom developer if the boot image
is programmed to run Apps2SD.
Your partition may be using an EXT4 partition,
but your rom may not support EXT4. Repartition
your SD card to use EXT2 or EXT3.
please note i have formatted my sd and have done a ext2->ext3 already.
what should i do now ?
Click to expand...
Click to collapse
Stock ROM doesn't support A2SD as it has no means to execute the script.
Try HCDR.ROM or PuzzleROM
Ahh. Makes more sense now.
Sent from my HTC Tattoo using XDA App
pardol said:
Ahh. Makes more sense now.
Sent from my HTC Tattoo using XDA App
Click to expand...
Click to collapse
Further to your last message i have accidentally found this link where it shows how to move the apps to /system/sd and then all should work.
i have not done anything as such because i am not too familiar with shell scripting and want to avoid to brick the phone.
I know you said APPS2SD does not work with stock roms (not sure why but you are the master here :> ). can this help or there is no way to get it to work ?
actually i noted i am missing a kin d of pre-requisite to complete the script: there is no system/sd entry when using this command so i guess no hope
busybox df -h
busybox df -h
Filesystem Size Used Available Use% Mounted on
tmpfs 93.0M 0 93.0M 0% /dev
tmpfs 4.0M 0 4.0M 0% /sqlite_stmt_journals
/dev/block/mtdblock3 150.0M 139.9M 10.1M 93% /system
/dev/block/mtdblock5 165.1M 142.1M 23.0M 86% /data
/dev/block/mtdblock4 150.0M 3.1M 146.9M 2% /cache
/dev/block//vold/179:1
5.8G 1.8G 4.0G 31% /sdcard
It doesn't work with Stock roms because there's no command in init.rc to launch Apps2SD (which is part of the boot.img). Now, you can modify the boot.img (or get an already modified boot.img) to add support. It will retain the stock rom feel but has a modified boot image.
pardol said:
Further to your last message i have accidentally found this link where it shows how to move the apps to /system/sd and then all should work.
i have not done anything as such because i am not too familiar with shell scripting and want to avoid to brick the phone.
I know you said APPS2SD does not work with stock roms (not sure why but you are the master here :> ). can this help or there is no way to get it to work ?
Click to expand...
Click to collapse
That is because the EXT partition isn't mounted, so Linux (the OS behind Android) doesn't see an EXT partition on the SD card (needs a mount command to be executed, which Apps2SD does, but the rom doesn't launch the program).
pardol said:
actually i noted i am missing a kin d of pre-requisite to complete the script: there is no system/sd entry when using this command so i guess no hope
busybox df -h
busybox df -h
Filesystem Size Used Available Use% Mounted on
tmpfs 93.0M 0 93.0M 0% /dev
tmpfs 4.0M 0 4.0M 0% /sqlite_stmt_journals
/dev/block/mtdblock3 150.0M 139.9M 10.1M 93% /system
/dev/block/mtdblock5 165.1M 142.1M 23.0M 86% /data
/dev/block/mtdblock4 150.0M 3.1M 146.9M 2% /cache
/dev/block//vold/179:1
5.8G 1.8G 4.0G 31% /sdcard
Click to expand...
Click to collapse
i have the same problem and in order to run A2SD i have to mount the EXT3 Partition manually ; anyone knows how to auto mount the ext3 partition at system startup ?!!
ok. i have been able to install a2sd correctly and have it running since a ferw weeks now. The only flipside is i need a PC to be able to reboot the phone since the Ext3 partition does not start.
Is there a command i can put in the init.rc file to autorun a2sd in place of doing a
adb shell a2sd
every time i reboot the phone ?
Hi, how about if after start up , manually mount the ext3 partition and manually run apps2sd app ? As I rarely reboot the system so I think this can be an alternative solution. but could someone let me know the command ? thx