Related
http://forum.xda-developers.com/showthread.php?t=480582
so the only things you have to do is this??
because as i read down the thread people are talking about some 'links' or something i dont get it.
can anyone help?
LucidREM said:
a new update file was created by me utilizing JFs build environment .. you can use this to modify your update to pretty much anything you can imagine .. so long as you know what you're doing .. otherwise you might end up on the flashing android .. so here's the deal
PREREQUISITE:
1. you rooted your phone
2. you created the FAT32 / EXT2 combo partitions
SPECIAL NOTE:
EXT2 seems to have problems bigger than 2G .. recommended not to exceed 1.5G .. 500M is actually more than enough for most people
MicroSD should be 2G/4G/8G class6 .. without class6 you should not bother moving apps to the SD
this update can help you .. it contains the modified init.rc, mountd.conf files necessary to load the EXT2 partition to /system/sd .. JFs normal update contains the original files and thus your /system/sd/ folder will not show up .. good news .. if you updated with JFs update and have not wiped your /data then you can just reflash my modified update and regain your phone
NOTE: if you WIPE your phone YOU MUST have the EXT2 on your MicroSD to use this modified update.zip
INSTRUCTION:
1. Have/Create the FAT32 / EXT2 Partitions on the MicroSD
2. Download Modified Update to the MicroSD FAT32
JFv1.42_RC33
JFv1.43_RC9
JFv1.43_ADP1.1H
3. Rename To "update.zip" & Flash the G1
4. Moved /data/app, /data/app-private, and/or /data/data (optional) to the SD in Terminal:
a. $su
b. #copy.sh app
c. #copy.sh data (OPTIONAL)
5. Enjoy!
Click to expand...
Click to collapse
oh **** i just did this and all my apps are gone x(
installing a buttload of apps and using very very mininal internal memory! how awesome xD
I did this a few days ago, works great.
I downloaded the trial version of Paragon Partition Manager.
Created an EXT2 partition (it's very easy to do and intuitive once you open the program) of around 450 MB (don't think I'll ever need more than this).
Flashed the update (renamed it update.zip, booted into recovery mode and did the whatever the alt+_ command was to flash it).
Ran all three scripts in the terminal (not recommended to move data unless you have a Class 6 card).
Works well so far.
can you install themes on this?
Why are you posting another thread in the apps forum instead of posting in the original thread?
I had to reset my phone today, since for some odd reason, I switched it off and back on, and it wouldnt get back the flashing android screen (havent even made any changes to it recently, God knows why it decided to do this).
Anyway, I figured, format the phone, reflash JF 1.5, and then move apply apps2sd (I already have my apps on my SD card, just have to link them back to the phone so it can see them), and the small customisations I can do later, I would get my phone back to functioning level.
I am using these instruction from SDK on my computer:
1. Check if your phone is recognised.
adb devices
2. Mount the phone into ADB.
adb remount
3. Bring up the shell.
adb shell
4. Check if /system/sd is visible.
df
5. Skip this step if you already have your apps on SD.
cp -a /data/app /system/sd
6. Skip this step if you already have your app-private on SD.
cp -a /data/app-private /system/sd
7. Remove the current apps folder on device.
rm -r /data/app
8. Remove the current app-private folder on device.
rm -r /data/app-private
9. Link the app folder on sd to the one on device.
ln -s /system/sd/app /data/app
10. Link the app-private folder on sd to the one on device.
ln -s /system/sd/app-private /data/app-private
11. Finally Reboot.
reboot
Well, I can flash the phone fine, but when I am trying to follow the instructions for relinking the apps from SD to the phone (stage 4), it doesnt show /system/sd, instead it shows /sdcard.
Does this mean I should change the following steps to say 'sdcard' instead of '/system/sd'? I have tried this with no luck, shows me the android screen indefinitely.
I have an ext2 partition on the phone on which I have my apps, I have done this whole process before many times, but not for a while so I am missing something important.
And I am skipping steps 5 and 6, since I have already got all my apps on my SD card.
Any help would be must appreciated, this is wasting quite a bit of my time.
PS: the only thing I have changed since I last did this, was I flashed the phone with a google ion build, while it had JF 1.5 on it. What I did notice after that was the phone ran a lot slower. That is the only change I can think of which separates this process working perfectly previously, and not at all now.
Um reformat your entire card to fat32. And then use cyanogen's recovery 1.31. to split your sd into 2 partitions. Msg me on gtalk or by email and I'll help you out
Many thanks for the reply.
Hmm I would have thought a reformat of the SD card would be last resort, is there no way to sort this out without going down that route?
Don't think there's another way, You could try switching ROMS see if that fixes it...
Might not need to reformat it all just yet.. Been awhile since I used JF, but I don't think it automatically mounts /system/sd
I think you might need the init.rc from this post -- http://forum.xda-developers.com/showthread.php?t=512743
Personally - and I try not to be preach about it, but I think CM users can't help that -- I'd suggest trying CyanogenMod since you're reflashing anyway. It isn't quite as stock as JF, but it is rock solid and fast, and it should pickup your existing A2SD partition automatically.
Agreed with Saiboogu. Try out Cyanogen's ROM you will NOT regret it
Ok, I am up for that.
BTW, when I format my phone (Alt+W I believe), and start it up again, its firmware is still upgraded.
If I reflash with a ROM, will that cause any problems or slowing, will it be overwriting anything? I guess I dont quite understand what the formatting of the phone is doing, and what it is leaving behind, and then what reflashing with a ROM is doing on top of that.
Also,m when you say Cyanogen's rom will do apps2sd automatically..how? Will it recognise the apps currently on the ext2 partition of my SD card? It wont delete them will it?
It will not delete them. It uses bind mounts to automatically do the apps to sd . Just wipe and flash
Ok, giving it a try now.
Hmm something I should have asked beforehand, my partition is ext2, do I need to change that to ext3 before I flash the cyanogen ROM?
Like alritewhadeva said - it just recognizes your existing apps.
A wipe clears out all the custom data.. Your settings, application data in the /data partition, your google account data that is synced to the phone. It doesn't touch the actual OS, which is why your ROM is still installed after a wipe.
With that said.. Cyanogen builds can be "broken" if you wipe after a flash. So always either just flash, or wipe *then* flash.
PERFECT! its worked like a charm! no hassle at all!
Great! You won't regret it.
one problem I have noticed, my camera keeps force closing (wont even start up without force closing straight away).
Any solution to this? Have tried going into the camera app in applications manager and clearing defaults, but no defaults were set.
That one sounds familiar, but I can't find an actual reference to it right now. Probably want to search the Cyanogen thread for mentions: http://forum.xda-developers.com/showthread.php?t=518851
Also keep an eye out for updates - Cyanogen is prolific, and will probably get one released sometime this evening. It may fix the issue.
That one sounds familiar, but I can't find an actual reference to it right now. Probably want to search the Cyanogen thread for mentions: http://forum.xda-developers.com/showthread.php?t=518851
Also keep an eye out for updates - Cyanogen is prolific, and will probably get one released sometime this evening. It may fix the issue.
Edit: Ah, here it is - http://forum.xda-developers.com/showthread.php?t=536687
He says he had to wipe his SD card, repartition and everything. Not sure if that is your issue or not.
Ah I posted a fix for that just take the camera.apk from an older cyanogen build (3.6.5) and push it over.
so put the camera.apk on sdcard
su
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
cd sdcard
cp Camera.apk /system/app
reboot
I am afraid due to my pathetic ignorance of how android works, I cant decipher what you said.
How do I get the camera apk? And once I acquire it, and put it on my SD card (I am assuming not in any folder, just on the main directory of the card), I use the terminal emulator to type in those commands?
well thats rather funny, just switched my phone on and off and the camera is working now.
raukodur said:
well thats rather funny, just switched my phone on and off and the camera is working now.
Click to expand...
Click to collapse
well then awesome
Great that you got it working. For future reference (because these things do happen occasionally), alritewhadeva was suggesting that you download an older version of CM (link on his build thread), unzip it and find the camera.apk file. Then place that file on your sd card, and follow his directions in Terminal Emulator on the phone.
After having apps working fine on my phone for a while now... a lot of the apps on my g1, once started, make me force close them.. apps include: anything that uses the accelerometer [except iliter?], lock 2.0, ringers extended.. and a bunch of other ones. I dont think the apps are corrupt considering that they have worked previousally and just started not working. Could the ext2 partition on my sd be full? I set the partition to 700mb and i only have about 20 apps or less.
Maybe somebody could advise on what this might be.. thanks!
Also, every time i turn my phone on i get process com.htc.calender stopped unexpectedly and asks a force close. it asks me to f.close it like 3 times when i first turn on the phone. YES I DID WIPE BEFORE FLASHING THIS ROM. Is there a way to just get rid of this process entirely? becuase after i force close if i go to calander in the menu it works.
what rom are you currently using? what was the rom you used before flashing to your current rom? did you try deleting your dalvik-cache? what about running fix_permissions?
I know when I went from a hero rom to cupcake, I had those same issues so if that is the same problem than you are gonna have to format your ext partion and reload your files, I know if you search the forums though there is a command that you enter in the terminal to just delete the files doing it to you
if you went from a hero rom to a cupcake rom then you need to go into the recovery console and type
Code:
mount /system
rm /system/sd/app_s/*
rm /system/sd/dalvik-cache/*
if that still does not fix it then you will need to just use
Code:
mount /system
rm /system/sd/*
david1171 said:
what rom are you currently using? what was the rom you used before flashing to your current rom? did you try deleting your dalvik-cache? what about running fix_permissions?
Click to expand...
Click to collapse
Running Cyan 4.02 + 1.4 [before this was running JACHero] and no i didnt delete my dalvik-cache??? <--whats that?
It's where your system wipes anything, just type in the codes that were posted and you will be alright, hero leaves files on your ext partion that need to be removed because they do not work with the non hero framework, the code that was post will remove those files, you must type them in the recovery console and not terminal emu
gridlock32404 said:
It's where your system wipes anything, just type in the codes that were posted and you will be alright, hero leaves files on your ext partion that need to be removed because they do not work with the non hero framework, the code that was post will remove those files, you must type them in the recovery console and not terminal emu
Click to expand...
Click to collapse
Will give that a try! thx.
Is that going to delete any of my apps?
Also-- is there a way to confirm that my apps are being automatically installed on my SD?
It will not delete any of your apps just the left over hero junk. To conform just go into manage apps under settings and check the space that is free internal and see how much is used of your ext
gridlock32404 said:
It will not delete any of your apps just the left over hero junk. To conform just go into manage apps under settings and check the space that is free internal and see how much is used of your ext
Click to expand...
Click to collapse
went into manage apps in settings... how do i check the space used by the ext? Menu option only include sort & filter
ALSO i know i sound exteremly noobie.. but..
mount /system
rm /system/sd/app_s/*
rm /system/sd/dalvik-cache/*
Do i replace the *'s with something else, or am i to actually type "*"
Whoops I meant sdcard and storage, sorry bout that I have been up since 5 yesterday and is now 3 in the afternoon so on that note, nighty night. Good luck
ONe more ?
Everytime i type rm /system/sd/app_s/* it tells me cannot remove - no such file or directory.
says the same thing with the rm davvik-cahce thing.
and yes i am in console in recovery.
Try without the *.
Than it's quite possible that you might have to format your sd card, backup your files using I think using app manager and backup for root users, transfer your files onto your computer and format, be a real good time to set yourself up with a nice 96mb swap file. Don't feel bad I plan to reformat mine tomorrow just to get all the old crap off just to have a clean slate
Thank you david I must be tired I didn't notice when he asked about the * and I also said the dalvik cache wipes to your system instead of writes, just noticed that after I just reread my post
Hey all,
My apologies if this question has been asked before. I have had a G1 for a while, but switched to the Desire recently. I never had the need to enable apps2sd, but since my lil bro got the G1 now he wants to install a lot more. He is new to Android and curious about every app. I am seeing some errors with the a2sd though.
I have installed the latest CM4 and enabled a2sd by partitioning the sdcard as 0 mb swap, 512 ext3.
The sdcard secondary is showing normally the correct values, but after a restart it states that there is no sdcard secondary and apps do not work obviously. The forceclose immediately after launch.
Am I doing something wrong with the settings or what? Is it normal for this to happen?
Also, is it safe to connect the sdcard to the pc, if a2sd is enabled? I remember him having problems with apps launching after transfering some music files via usb.
Is the EXT partition showing up when you run 'print' in parted?
PhatP said:
Is the EXT partition showing up when you run 'print' in parted?
Click to expand...
Click to collapse
I cannot check it right now. I don't have access to his phone since I won't be home for a week or two. I assume parted should be used within terminal, right?
su and then parted /dev/block/mmcblk0? According to him, this is not found.
But the secondary sd is showing, which should mean apps should work?
I let him install an app, and asked him about the memory. Only phone memory was reduced, meaning it didn't touch the sd secondary.
I can remember me having the same error, when I wanted to try out this a2sd, but never looked into it since I didn't need it.
edit: I just remembered it should be done in recovery. He is more of a noob than I am, so proabably doing it when I get home.
Depending on which ROM he is using, he may have to enable A2SD. For example, I'm running Cyanogen Mod 5.0.7 - DS and need to enable it under Application Settings. Good luck, I'm no expert but I've been through my fair share of problems with this phone for 2 years now.
delete dalvik cache
Delete your dalvik cache....this helped me
Hmm thnx for all the answers. I think I will just flash CM5 for him. I had deleted everything from personal settings to dalvik cache and battery settings and what not. The issue was still there. Either that or just forget about a2sd.
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