What can we move to /sytem/sd (ext2 partition) - G1 Android Development

I start using a second partition for my apps and some of the caches...
But is there more? Yes there is (i hope). But what else? Any ideas, more is better...
What do you need:
A FAT32 / EXT2 partition combo on your CLASS 6 MicroSD (the EXT2 from 100mb to 1,5gb as max recommend (real max = 2gb)!
Only at "others" there is one way to move cache without EXT2 partition.
Do it yourself:
(Private) Apps to SD: http://forum.xda-developers.com/showthread.php?t=462882 (Apply on your own Rooted System)
Complete ROM:
(Private) Apps to SD: http://forum.xda-developers.com/showthread.php?t=480582 (modded JF1.42 RC33)
Other:
- Apps Caches (no ext2 needed): http://forum.xda-developers.com/showthread.php?t=471653 and http://androidcommunity.com/forums/f28/updated-move-caches-to-sd-card-11167/
- Apps Caches (with ext2): Change the paths from: "/sdcard/cache" to "/system/sd/cache" from http://androidcommunity.com/forums/f28/updated-move-caches-to-sd-card-11167/
I will add everything that's relevant to putting stuff from your ROM to your FLASH!

i hope we can move everything to the sd lol ;P

Theoretically it is but i think it will be to damn slow But if we put the core and much used stuff on system (something like vista does it with mem, preload stuff i use alot to my system and stuff i don't use a lot to my sd or somthing... But i don't have skills to do something like that (i suck with linux :S).

Yeah, it's possible. But as you said, the issue would be with the speed of everything... I know some basic Linux, but not to move the entire OS to the SD, otherwise I'd try it myself, and test the speed of it.

Phromik said:
Yeah, it's possible. But as you said, the issue would be with the speed of everything... I know some basic Linux, but not to move the entire OS to the SD, otherwise I'd try it myself, and test the speed of it.
Click to expand...
Click to collapse
the most i have tried is i moved the entire /data folder over to the EXT2 partition and then mounted the SD to /data .. so when you pull up available space it says 1G+ available on the phone for apps .. actually pretty kool but i can't get the SD to mount to /data on the phone boot and the slowness is definitely a factor .. anyone who wants to try for themselves is welcome .. but i can't speak for any errors you might get

LucidREM said:
the most i have tried is i moved the entire /data folder over to the EXT2 partition and then mounted the SD to /data .. so when you pull up available space it says 1G+ available on the phone for apps .. actually pretty kool but i can't get the SD to mount to /data on the phone boot and the slowness is definitely a factor .. anyone who wants to try for themselves is welcome .. but i can't speak for any errors you might get
Click to expand...
Click to collapse
how do you do it that it shows in storage available that u have 1G+ available space. i would want that to show for me.

Smokuevo said:
how do you do it that it shows in storage available that u have 1G+ available space. i would want that to show for me.
Click to expand...
Click to collapse
in my script i put in my modified JFv1.42 you can do:
#copy.sh all
this moves everything to the SD (the ultimate in G1 lag) and then from Terminal again:
#mount /dev/mmcblk0p2 /data
this should work (unless i forgot a step) .. then when you look at the available space you should see the entire EXT2 partition listed for the phone .. to get my script you can either flash my modified update.zip that has the modified init.rc and mountd.conf or else just copy my script to your phone

what if i already did copy.sh data copy.sh app .. will copy.sh all mess anything up?
whats the reverse step

Well the first stap is backing up ofcourse! So the only step if you screw up is putting the backup back...

back up didnt work. got to try cupcake though. haha.
now getting stale nfs files

Smokuevo said:
what if i already did copy.sh data copy.sh app .. will copy.sh all mess anything up?
whats the reverse step
Click to expand...
Click to collapse
i did put in "copy.sh undoall" to reverse the steps .. but this will also move apps and if you have too many apps if could crash the phone .. i may need to remove apps from the undoall process

after i did the command to make the room on my SD show up as my memory how do i revert that back to normal to see the space on my phones internal mem?

Smokuevo said:
back up didnt work. got to try cupcake though. haha.
now getting stale nfs files
Click to expand...
Click to collapse
on a linux distribution type :
fsck.ext2 -p [your partition] mine is /dev/sdd2 for example

Related

Alternative to lucid rem

http://forum.xda-developers.com/showthread.php?t=462882&page=8
in case nobody knows.
download batch files and extract to tools folder in the sdk and follow readme.txt
i think this method allows you to download new apps and not have it effect the internal memory
i will try this soon because lucidrems method is a little disapointing that the internal memory still keeps draining even after doing the steps correctly.
if he fixes this then im sure everyone will be happy
It's the same method, including the optional step of moving the whole /data/data partition over, just some batch files to do it for you.
blacktortilla said:
http://forum.xda-developers.com/showthread.php?t=462882&page=8
in case nobody knows.
download batch files and extract to tools folder in the sdk and follow readme.txt
i think this method allows you to download new apps and not have it effect the internal memory
i will try this soon because lucidrems method is a little disapointing that the internal memory still keeps draining even after doing the steps correctly.
if he fixes this then im sure everyone will be happy
Click to expand...
Click to collapse
not to sound rude .. but if you knew the process you'd know that the internal memory will continue to drain no matter which method you choose .. they all do the same thing .. you can always try my "copy.sh all" script if you feel so inclined .. the more you move off the phone the more unstable it can become .. the "copy.sh all" is the only way i know to maintain maximum internal space on the phone .. you also have to realize this is not "memory" as people think in terms of RAM when you mention that word .. the space where apps are located in /data is in terms of HDD space for file storage .. there is a measure of cache files and temp files i'm sure that need to utilize the phone as well
now i'm not trying to down your process .. i'm sure it's great .. but the moving of /data/app and /data/data in the end is always the same result .. my goal was to eliminate the need for the SDK and hooking up to a computer
just as a side note .. i personally ran "copy.sh all" and then "copy.sh mount" and then you can take a look at available space .. mine was "1.4G"
LucidREM said:
not to sound rude .. but if you knew the process you'd know that the internal memory will continue to drain no matter which method you choose .. they all do the same thing .. you can always try my "copy.sh all" script if you feel so inclined .. the more you move off the phone the more unstable it can become .. the "copy.sh all" is the only way i know to maintain maximum internal space on the phone .. you also have to realize this is not "memory" as people think in terms of RAM when you mention that word .. the space where apps are located in /data is in terms of HDD space for file storage .. there is a measure of cache files and temp files i'm sure that need to utilize the phone as well
now i'm not trying to down your process .. i'm sure it's great .. but the moving of /data/app and /data/data in the end is always the same result .. my goal was to eliminate the need for the SDK and hooking up to a computer
just as a side note .. i personally ran "copy.sh all" and then "copy.sh mount" and then you can take a look at available space .. mine was "1.4G"
Click to expand...
Click to collapse
thanks for the info. and i wasnt trying to bag on you i know you contribute alot and its appreciated. your method is obviously easier but what i still dont get is.
1. when i do copy.sh app this doesnt move the apps to the sd? or is this just a link to the sd so that when the internal storage is used it starts puting them on the ext2 partition?
2. does copy.sh all move everything to the sdcard?
3. what does copy.sh mount do?
4. 1.4g of ext2 sd space? or of internal storage space that is shown under sd and storage in settings?
thanks
never mind i figured it out. but from what i read, copy.sh all makes your phone go really slow i would have thought so. thanks lucidrem

A2SD in the future

I'm going to start looking into running apps on the SD card.
What I'd like to know is, can I run the a2sd version (I plan on using Haykuro's ADP1.5Hr3) w/o any issues? Any differences to the regular version if I haven't moved my apps over?
I've been using A2SD for the past 3-4 version of Hakyuro's H series, I then went to the ADP A2SD, I have had no problem what so ever. It works great and is quick, I don't think I could ever go back to using the built in disk for application storage.
I'm currently running ADP1.5Hr3 with 192 applications.
If you dont have a SD card with the partitions necessary, and you load an a2sd version of firmware, when your phone boots up it will start looking for the partition to mount and will continue to do so in the background. This may have an adverse affect on the performance and or battery life.
If this has been fixed in any versions feel free to post it.
Dharkaron said:
If you dont have a SD card with the partitions necessary, and you load an a2sd version of firmware, when your phone boots up it will start looking for the partition to mount and will continue to do so in the background. This may have an adverse affect on the performance and or battery life.
If this has been fixed in any versions feel free to post it.
Click to expand...
Click to collapse
actually when u load an a2sd rom it doesnt look for anything to mount
because when u load an a2sd rom it only looks for a partition once you command it to
without your command it will work like an regular rom that doesnt have the a2sd mod...it will store applications and caches on your internal flash
once you start doing commands such a ln and rm that is when you are actually connecting folders to the ones on your sd card
the performance is the same if u have a2sd or not....the performance either increases or decreases when u tell the phone to do the symlinks to ur ext 2 partition
bigballa said:
actually when u load an a2sd rom it doesnt look for anything to mount
because when u load an a2sd rom it only looks for a partition once you command it to
without your command it will work like an regular rom that doesnt have the a2sd mod...it will store applications and caches on your internal flash
once you start doing commands such a ln and rm that is when you are actually connecting folders to the ones on your sd card
the performance is the same if u have a2sd or not....the performance either increases or decreases when u tell the phone to do the symlinks to ur ext 2 partition
Click to expand...
Click to collapse
????WHAT???
Looks for partition after you command to it???
The haykuro apps-to-sd roms load the ext2 module and a .sh script runs during boot that looks for the partition over and over in a loop. If found it is mounted, if not it keeps trying. This *can* cause battery issues, although I doubt it would be bad. I have no idea what you are saying about commanding to it, but that is wrong.
Re installed the app. Ran and have 54mb available happy.
on a mac
what is the equivalent of ex2 on a mac...it's not listed in the partition options
jaaronmoody said:
what is the equivalent of ex2 on a mac...it's not listed in the partition options
Click to expand...
Click to collapse
It's only possible with ext2 as far as I know. You are probably going to have to download a partition manager program
Darkrift said:
The haykuro apps-to-sd roms load the ext2 module and a .sh script runs during boot that looks for the partition over and over in a loop. If found it is mounted, if not it keeps trying. This *can* cause battery issues, although I doubt it would be bad. I have no idea what you are saying about commanding to it, but that is wrong.
Click to expand...
Click to collapse
Any more news about this and battery usage posted anywhere that i can read further?

Question Noobe

I would like to know exactly what these do before i do them. sorry guys im a noobe..
Build:RA-magic-v1.2.3G
- wipe sd:ext partition
- Wipe SD:dalink-cache
- part sd:fat32+ext2+swap
- part sdnly fat32
- repair ext filesystem
- convert ext2 to ext3
- fix apk uid mismatches
- fix rotate
- USB Mass storage on
- USB Mass Storage off
Also how do you flash this recovery img from the Recover Flasher App, VS using CMD & fastboot.
jdubdieslo said:
I would like to know exactly what these do before i do them. sorry guys im a noobe..
Build:RA-magic-v1.2.3G
- wipe sd:ext partition
- Wipe SD:dalink-cache
- part sd:fat32+ext2+swap
- part sdnly fat32
- repair ext filesystem
- convert ext2 to ext3
- fix apk uid mismatches
- fix rotate
- USB Mass storage on
- USB Mass Storage off
Also how do you flash this recovery img from the Recover Flasher App, VS using CMD & fastboot.
Click to expand...
Click to collapse
wipe sd: ext partition- deletes your apps on your ext partiton
wipe sd: davlik-cache wipes your cache on your sd
part sd: fat32+ext2+swap makes the three partitions you need to run hero roms
parted sd: fat32 only- just partitions your memory card for a fat32 for stock roms like cyanogen
convert ext2 to ext3- does exactly what it says. makes ext2 to ext3
repair ext filesystem- do this after you choose to convert ext2 to ext3
fix apk uid mismatches- does exactly what it says
fix rotate- fixes auto rotate issues some roms have
usb mass storage on- allows you to access your fat32 part of your sd from the recovery
usb mass storage off- turns off the mounting of your sd from the recovery
to flash it using the recovery flasher app, just look at the unlockr's video and substitute the recovery image name for the one that is in the video. Voila.
Hope this helps
Applause...
Getting a straight answer sometimes is the most difficult part of installing a rom.
thelastgoodbrother said:
Applause...
Getting a straight answer sometimes is the most difficult part of installing a rom.
Click to expand...
Click to collapse
lol thats very true but come on if you can't do the research to figure out the basic youll be posting another thread the next day but this time it'll be called "stuck on the g1 screen" lol sometimes not giving a straight answer may save their phone... but thats just my opinion
So use part sd: fat32+ext2+swap when useing hero rom... what if i use hero rom & go back to cyanogen can i leave it that way or do i need to parted sd: fat32 only? also if i did part sd: fat32+ext2+swap And then did part sdnly fat32 would it override the part sd: fat32+ext2+swap. another question i dont even know what ext 2 is so moving it to ext 3 would be? sorry guys im new at this.. just wanted to clarify this. is fat32 letting me store apps to sd? because i removed the sd card while phone was on & notices it froze; i put it back in removed & rrplaced battery and it was fine again.. also i noticed i part sd: fat32+ext2+swap again before i read your replies to see what it would do and everything on my sd card was goin..
also what is swap i saw an app that saved a swap file on sd..
thanks everyone for you help. loving the android community. as soon as i get some extra cash i will be donating to people that helped me make my android stand out from any one's android on my end of the computer. thanks
jdubdieslo said:
So use part sd: fat32+ext2+swap when useing hero rom... what if i use hero rom & go back to cyanogen can i leave it that way or do i need to parted sd: fat32 only? also if i did part sd: fat32+ext2+swap And then did part sdnly fat32 would it override the part sd: fat32+ext2+swap. another question i dont even know what ext 2 is so moving it to ext 3 would be? sorry guys im new at this.. just wanted to clarify this. is fat32 letting me store apps to sd? because i removed the sd card while phone was on & notices it froze; i put it back in removed & rrplaced battery and it was fine again.. also i noticed i part sd: fat32+ext2+swap again before i read your replies to see what it would do and everything on my sd card was goin..
also what is swap i saw an app that saved a swap file on sd..
thanks everyone for you help. loving the android community. as soon as i get some extra cash i will be donating to people that helped me make my android stand out from any one's android on my end of the computer. thanks
Click to expand...
Click to collapse
If you are running a hero rom and want to go to cyanogen, you can leave the fat32+ext2+swap. Just make sure that you wipe your sd partition and davlik cache using the options in the recovery image. Do this every time you are flashing any new rom for that matter, whether it's a different hero rom or a stock rom.
Ext is the partition of your memory card that stores all your apps. This was necessary for the g1 because it only had like 80 mb of memory for apps. The mytouch has nearly 300 so apps2sd is not really necessary, but most custom ROMs include this anyway. Ext3 is what most of these ROMs operate on. Ext2 is an old outdated version that no one really uses anymore and ext4 is even newer than ext3 but is not really necessary.
Fat32 only does not let you store your apps on your sd. It does not have the ext partition to let that happen. I don't know why your phone froze when you took your sd card out. It shouldn't have. When you part your memory card, whether its just fat32 or the combo fat, ext, and swap your memory card gets wiped and formatted to whatever you have, so of course you will lose all your contents on the memory card. It wipes and reformats all 3 partitons, or just the one if you are doing only the fat32.
As for swap, this is necessary for hero. Hero phones have 288 mb of ram and the mytouch only has 192mb so if you don't have this, the phone lags so bad and hangs up and you get constant load screens. The app you saw is known as swapper. Yes it does put a swap file on your sd card, but if you go into advanced settings, it lets you use your swap partition of your memory card, which is what you should always choose.
Keep them questions rolling, I like being able to contribute whenever I can.
tazz9690 said:
If you are running a hero rom and want to go to cyanogen, you can leave the fat32+ext2+swap. Just make sure that you wipe your sd partition and davlik cache using the options in the recovery image. Do this every time you are flashing any new rom for that matter, whether it's a different hero rom or a stock rom.
Ext is the partition of your memory card that stores all your apps. This was necessary for the g1 because it only had like 80 mb of memory for apps. The mytouch has nearly 300 so apps2sd is not really necessary, but most custom ROMs include this anyway. Ext3 is what most of these ROMs operate on. Ext2 is an old outdated version that no one really uses anymore and ext4 is even newer than ext3 but is not really necessary.
Fat32 only does not let you store your apps on your sd. It does not have the ext partition to let that happen. I don't know why your phone froze when you took your sd card out. It shouldn't have. When you part your memory card, whether its just fat32 or the combo fat, ext, and swap your memory card gets wiped and formatted to whatever you have, so of course you will lose all your contents on the memory card. It wipes and reformats all 3 partitons, or just the one if you are doing only the fat32.
As for swap, this is necessary for hero. Hero phones have 288 mb of ram and the mytouch only has 192mb so if you don't have this, the phone lags so bad and hangs up and you get constant load screens. The app you saw is known as swapper. Yes it does put a swap file on your sd card, but if you go into advanced settings, it lets you use your swap partition of your memory card, which is what you should always choose.
Keep them questions rolling, I like being able to contribute whenever I can.
Click to expand...
Click to collapse
ao since ext 2 is outdate we want to convert ext 2 to ext 3 then repair ext filesystemafter words.. so if you convert ext 2 to ext 3 is there only a ext 3 now or both ext 2 and it adds a ext 3? also what does dalvik mean? also i thought apps to sd was a big deal because if you switch roms all your apps are still there, but if you wipe ext partition then you lose the apps so the real reason is just for phone with low ram and cant store many apps at once.. intresting..and wats up with not wipe data/factory reset after installing roms? whats the reason behind that, i notice my IME keyboard is no longer there when i do that.. im trying to think of more questions lol. thanks a million.
jdubdieslo said:
ao since ext 2 is outdate we want to convert ext 2 to ext 3 then repair ext filesystemafter words.. so if you convert ext 2 to ext 3 is there only a ext 3 now or both ext 2 and it adds a ext 3? also what does dalvik mean? also i thought apps to sd was a big deal because if you switch roms all your apps are still there, but if you wipe ext partition then you lose the apps so the real reason is just for phone with low ram and cant store many apps at once.. intresting..and wats up with not wipe data/factory reset after installing roms? whats the reason behind that, i notice my IME keyboard is no longer there when i do that.. im trying to think of more questions lol. thanks a million.
Click to expand...
Click to collapse
if you convert ext2 to ext3, there will only be ext3. It converts it from ext2, it does not make an additional partition. Davlik cache, if I am not mistaken is all your cache from your browser to google maps gets saved to your sd card as well instead of your phone memory. The apps2sd was originally for the fact that you keep your apps, but when flashing hero roms, it did not work for some reason and it resulted in boot loops. So that's why they say always format your ext if flashing from a different rom. For stock roms, I don't believe this would be an issue so you probably could go on without wiping your sd as long as you are moving from a stock rom to another stock. It will not work if you go from stock to hero, and vice versa. Wipe data/factory reset clears all the settings from your phone so you do not have any lingering settings stored on the phone from an old rom when you flash a different one. The only time that you do not need to do this is if you are flashing a newer version of the same rom. The IME is probably still there, it just got unchecked from the input method. Go to locale and text and recheck the "input" box and it should work again.
yeah it is safest way to wipe and reformat the sd card before flashing a new rom.
tazz9690 said:
if you convert ext2 to ext3, there will only be ext3. It converts it from ext2, it does not make an additional partition. Davlik cache, if I am not mistaken is all your cache from your browser to google maps gets saved to your sd card as well instead of your phone memory. The apps2sd was originally for the fact that you keep your apps, but when flashing hero roms, it did not work for some reason and it resulted in boot loops. So that's why they say always format your ext if flashing from a different rom. For stock roms, I don't believe this would be an issue so you probably could go on without wiping your sd as long as you are moving from a stock rom to another stock. It will not work if you go from stock to hero, and vice versa. Wipe data/factory reset clears all the settings from your phone so you do not have any lingering settings stored on the phone from an old rom when you flash a different one. The only time that you do not need to do this is if you are flashing a newer version of the same rom. The IME is probably still there, it just got unchecked from the input method. Go to locale and text and recheck the "input" box and it should work again.
Click to expand...
Click to collapse
Previously I got a 2GB micro-sd card. so no problem for me to move my music, photos, videos and backup apps to my pc.
But i just bought a 8GB card 2 weeks ago and man, backup all before flashing a rom is pain in the a** . but can't help flashing this and that ROMs hee hee
so no choice. yesterday I flashed Eugene's supermagic rom. awesome!
cheers
tazz9690 said:
if you convert ext2 to ext3, there will only be ext3. It converts it from ext2, it does not make an additional partition. Davlik cache, if I am not mistaken is all your cache from your browser to google maps gets saved to your sd card as well instead of your phone memory. The apps2sd was originally for the fact that you keep your apps, but when flashing hero roms, it did not work for some reason and it resulted in boot loops. So that's why they say always format your ext if flashing from a different rom. For stock roms, I don't believe this would be an issue so you probably could go on without wiping your sd as long as you are moving from a stock rom to another stock. It will not work if you go from stock to hero, and vice versa. Wipe data/factory reset clears all the settings from your phone so you do not have any lingering settings stored on the phone from an old rom when you flash a different one. The only time that you do not need to do this is if you are flashing a newer version of the same rom. The IME is probably still there, it just got unchecked from the input method. Go to locale and text and recheck the "input" box and it should work again.
Click to expand...
Click to collapse
so when going to another rom should you part the sd before or after the rom is loaded? and honestly im running out of questions.. i got one that is throwing me off.. i have my phone in fastboot and in device manager it show andriod bootloader (cant remember the exact device); i type in the cmd
cd desktop
cd fastboot
then the code for the custom splash and i get
< waiting for device > and it just sits there. nothing will happen. & my splash is still stock.. the file is at the rights bytes and i have the folder on my cd on the desktop and the driver i beleive is installed correctly on the cp. what am i doing wrong?
I think the Title should be Changed, Something Like Recovery-101. Know Your Phone.
Alot of great Info for New comers
jdubdieslo said:
so when going to another rom should you part the sd before or after the rom is loaded? and honestly im running out of questions.. i got one that is throwing me off.. i have my phone in fastboot and in device manager it show andriod bootloader (cant remember the exact device); i type in the cmd
cd desktop
cd fastboot
then the code for the custom splash and i get
< waiting for device > and it just sits there. nothing will happen. & my splash is still stock.. the file is at the rights bytes and i have the folder on my cd on the desktop and the driver i beleive is installed correctly on the cp. what am i doing wrong?
Click to expand...
Click to collapse
Part the sd before you load the rom onto the phone. if it has apps2sd and you try to part your memory card after, you will get stuck at the splash more than likely because you are missing key components that are stored onto the sd, like all your apps for example that come with the ROM.
In fastboot, when it's plugged in, on the phone does it say "Fastboot USB"?
You might want to try to reupload the drivers for the fastboot. That may be why it's hanging. I never use fastboot through the desktop. I always use fastboot through the SDK folder on my C:\ drive. It always worked for me that way. For some reason I could never get it to work with the "cd destop" but thats just me.
tazz9690 said:
Part the sd before you load the rom onto the phone. if it has apps2sd and you try to part your memory card after, you will get stuck at the splash more than likely because you are missing key components that are stored onto the sd, like all your apps for example that come with the ROM.
In fastboot, when it's plugged in, on the phone does it say "Fastboot USB"?
You might want to try to reupload the drivers for the fastboot. That may be why it's hanging. I never use fastboot through the desktop. I always use fastboot through the SDK folder on my C:\ drive. It always worked for me that way. For some reason I could never get it to work with the "cd destop" but thats just me.
Click to expand...
Click to collapse
i figured taht was the right order part sd then load rom because i did it and it worked lol, and since it worked i never tried it rom the part sd. so do cyanogen roms have app2sd? and does the cyanogen rom have a overclocker built in now because i tried to use my overclock widget and it doesnt work and the phone seems as if its running faster even with out my widget..
and yes it says fastboot usb & ive tried uninstalling & reinstall the drivers mutliple times and still get < waiting for device > so if i do it on the c:/ drive were do i place the fastboot folder? /c:/fastboot? and what would the code be?
cd c:/
cd Fastboot
thent he other code that i have saved at home the flash_splash one? i cant remember it.
one really dumb question. i rooted my pops mytouch lol because he was complaining about the mytouch stock because of numerous things. so i rooted it to 4.2.2 and out of all things he is now complaining about the stock ringtones.. lol. anyone know where to get the stock ringtones? if not its cool i told him id make sum ringers with ringdroid for him like the temptations and willie nelson lol.. thanks all for your support.
jdubdieslo said:
i figured taht was the right order part sd then load rom because i did it and it worked lol, and since it worked i never tried it rom the part sd. so do cyanogen roms have app2sd? and does the cyanogen rom have a overclocker built in now because i tried to use my overclock widget and it doesnt work and the phone seems as if its running faster even with out my widget..
and yes it says fastboot usb & ive tried uninstalling & reinstall the drivers mutliple times and still get < waiting for device > so if i do it on the c:/ drive were do i place the fastboot folder? /c:/fastboot? and what would the code be?
cd c:/
cd Fastboot
thent he other code that i have saved at home the flash_splash one? i cant remember it.
one really dumb question. i rooted my pops mytouch lol because he was complaining about the mytouch stock because of numerous things. so i rooted it to 4.2.2 and out of all things he is now complaining about the stock ringtones.. lol. anyone know where to get the stock ringtones? if not its cool i told him id make sum ringers with ringdroid for him like the temptations and willie nelson lol.. thanks all for your support.
Click to expand...
Click to collapse
Cyanogen's rom has dynamic apps2sd. If it senses that you have a partition, it will do apps2sd. If you don't have an ext, it will save it to the phone, so it will work that way too.
For the fastboot, do you even have your computer set up for the use of ADB and fastboot? Like having the latest SDK downloaded and set up for your computer? That might be why it says, waiting for devices. When you do cd fastboot, afterward type fastboot devices and see if in the cmd it says "HTC Bootloader" or "Android Bootloader" I am not sure which one it is.
As for the ringtones, here is the link for the download in Cyanogen's 4.2.2 threat http://n0rp.chemlab.org/android/audio-resources.zip That downloads a zip of all the stock ringtones. Just upzip the file and place it on the root of your sd card.
tazz9690 said:
Cyanogen's rom has dynamic apps2sd. If it senses that you have a partition, it will do apps2sd. If you don't have an ext, it will save it to the phone, so it will work that way too.
For the fastboot, do you even have your computer set up for the use of ADB and fastboot? Like having the latest SDK downloaded and set up for your computer? That might be why it says, waiting for devices. When you do cd fastboot, afterward type fastboot devices and see if in the cmd it says "HTC Bootloader" or "Android Bootloader" I am not sure which one it is.
As for the ringtones, here is the link for the download in Cyanogen's 4.2.2 threat http://n0rp.chemlab.org/android/audio-resources.zip That downloads a zip of all the stock ringtones. Just upzip the file and place it on the root of your sd card.
Click to expand...
Click to collapse
thats good to know. so if you ext 2 will cm use ext 2 & if you converted it will it use ext 3? also how can i tell what i have ext 2 or ext 3 other than knowing if i click convert to ext 3? i downloaded the SDK and used the usb folder when the computer was looking for drivers & it says it installed drivers successfully; so now when im in fastboot usb on my phone the computer in device manager shows bootloader (cant remember exactly what it says untill i get home); & when my phone is in recovery the driver shows ADB (cant remember the exact name till i get home also); and then i do the codes because my fastboot & sdk folders are on my desktop; when i downloaded the sdk folder i dont think i did anything with it as far as isntalling it, what does the sdk folder do? lol. sorry..
thanks for the ringtones my pops says mucho gracias.
jdubdieslo said:
thats good to know. so if you ext 2 will cm use ext 2 & if you converted it will it use ext 3? also how can i tell what i have ext 2 or ext 3 other than knowing if i click convert to ext 3? i downloaded the SDK and used the usb folder when the computer was looking for drivers & it says it installed drivers successfully; so now when im in fastboot usb on my phone the computer in device manager shows bootloader (cant remember exactly what it says untill i get home); & when my phone is in recovery the driver shows ADB (cant remember the exact name till i get home also); and then i do the codes because my fastboot & sdk folders are on my desktop; when i downloaded the sdk folder i dont think i did anything with it as far as isntalling it, what does the sdk folder do? lol. sorry..
thanks for the ringtones my pops says mucho gracias.
Click to expand...
Click to collapse
I don't think any builds use ext2 anymore. They all either use ext3 or ext4. You have to make an ext2 first though, before you can convert it to ext3. Same goes for ext4, you have to have ext3 before you can upconvert to it. Just use ext3 just to be safe. If you go into "Parted" through the recovery image by typing in "parted /dev/block/mmcblk0" in adb shell, then typing 'print' it will show how big your fat32 is, it'll say which ext you have as well as your size, and the same for linux swap.
For a SDK, the folder stores the drivers needed for fastboot and adb in it. You should save it to the root of your C:\ drive because it makes things easier. I recommend you set up SDK using this thread guide: http://forum.xda-developers.com/showthread.php?t=532719
Setting up the Android 1.5r2 SDK
Download the file from above
Unzip to your desktop
Take the "android-sdk-windows-1.5_r2" folder and move it to the root of your hard drive (C:\)
Right click on My Computer and click properties
Select the Advanced Tab or Advanced System Setting (Vista)
Select Environment Variables...
Press New
For Variable Name type: adb
For Variable Value type: C:\android-sdk-windows-1.5_r2\tools
--------------------------------------------------------------------------
Preparing your phone for ADB
Go to Settings on your phone
Select Applications
Select Development
Make sure 'USB Debugging' is checked
--------------------------------------------------------------------------
Installing Drivers
Plug in your phone through USB and DO NOT MOUNT IT!!!!!
Your computer should see a new device and try to install Android 1.0 driver (If it doesnt, scroll down to the "Im not getting a notification of Android ADB when i plug in my USB" section)
Let it load
Once it cant find them select "Install drivers from my pc"
The drivers you need are in the Android SDK 1.5r2 folder (C:\android-sdk-windows-1.5_r2\usb_driver)
Depending on your OS pick x86 or amd64
You ADB Android Device should now be installed! Good Job
Those are basically what you need to look at.
jdubdieslo said:
I would like to know exactly what these do before i do them. sorry guys im a noobe..
Build:RA-magic-v1.2.3G
- wipe sd:ext partition
- Wipe SD:dalink-cache
- part sd:fat32+ext2+swap
- part sdnly fat32
- repair ext filesystem
- convert ext2 to ext3
- fix apk uid mismatches
- fix rotate
- USB Mass storage on
- USB Mass Storage off
Also how do you flash this recovery img from the Recover Flasher App, VS using CMD & fastboot.
Click to expand...
Click to collapse
Don't mean to hijack your thread OP, but I do have a question that I hope someone can answer. When partitioning the SD card, you choose the option I put in Bold. After that, could you use this link:
http://forum.xda-developers.com/showthread.php?t=535914
To adjust the different sizes of the 3 partitions? I know that in order to run any Hero ROMS, your SD card has to be partitioned with at least 3 (fat32+ext2+swap) parts. This is the only part that still confuses me when it comes to adequately rooting.
If you are using ubuntu, you create the partitions you want, as well as the size. If you use the recovery image, you would just be adding an unnecessary step because it will just get deleted when you make your partitions again with Ubuntu.
tazz9690 said:
I don't think any builds use ext2 anymore. They all either use ext3 or ext4. You have to make an ext2 first though, before you can convert it to ext3. Same goes for ext4, you have to have ext3 before you can upconvert to it. Just use ext3 just to be safe. If you go into "Parted" through the recovery image by typing in "parted /dev/block/mmcblk0" in adb shell, then typing 'print' it will show how big your fat32 is, it'll say which ext you have as well as your size, and the same for linux swap.
For a SDK, the folder stores the drivers needed for fastboot and adb in it. You should save it to the root of your C:\ drive because it makes things easier. I recommend you set up SDK using this thread guide: http://forum.xda-developers.com/showthread.php?t=532719
Those are basically what you need to look at.
Click to expand...
Click to collapse
So if u have a ext 3 how do u get ext 4? Also wat is linux swap? And yea i didnt do all that im sure thats why i was getting < waiting for device >. I will let u know the outcome of the splash screen... thanx.
jdubdieslo said:
So if u have a ext 3 how do u get ext 4? Also wat is linux swap? And yea i didnt do all that im sure thats why i was getting < waiting for device >. I will let u know the outcome of the splash screen... thanx.
Click to expand...
Click to collapse
If you want ext3, you have to go into parted like I stated in a previous post and create your partitions that way. From there, to upgrade to ext3, you type "upgrade_fs". You now have ext3. If you want ext 4, after that you would type
"tune2fs -O extents,uninit_bg,dir_index /dev/block/mmcblk0p2
e2fsck -fpDC0 /dev/block/mmcblk0p2"
That's just too much work for me. I am fine with ext3. If you want a more in depth explanation, go to this thread: http://forum.xda-developers.com/showthread.php?t=534714&highlight=wipe+partition
Linux swap, I believe I explained in one of my early posts. The mytouch only has 192 mb of ram. The Hero's have 288 and so do the 32A board Sapphire phones like the HTC Magic and the Rogers Magic. Since we were unfortunate to get that low of Ram, if you try to run a hero rom without the linux partition, the phone will lag, freeze, and get load screens constantly. Using a linux swap partition makes it possible to run the Hero ROM's at a decent speed, though it will not be as fast as if you had the actual HTC Hero phone or a 32A Sapphire.

[New Solution] - Faster Virtual Ram !!!!!

Hi,
I'm not a developer but I think my idea is great.
1. Using CACHE partition (50Mb) as virtual ram​
- I see that we are using swap ext partition to increase virtual ram, but access data speed of sdcard is not fast enough (for class2 or class4 sdcard),
- And I see that we have 50Mb free in cache partition which are only used when we use OTA update. But if we use a moded rom, why do we use OTA update ? access data speed of internal memory is really good, why don't we use cache partition as virtual ram ???
2. Runing faster with dalvik-cache on internal memory.​
- As you know, after install an application, we will have apk file in data/app or data/app-private and some odex file in dalvik-cache.
- If we only use app2sd with data/app and data/app-private, our application will run faster.
There was already an idea like that.
You mean using CACHE as swap partition.
At the moment this isn't possible because we would have to format this partitions and recovery wouldnt work then.
maxisma said:
There was already an idea like that.
You mean using CACHE as swap partition.
At the moment this isn't possible because we would have to format this partitions and recovery wouldnt work then.
Click to expand...
Click to collapse
What are the partitions formatted as now?
ivanmmj said:
What are the partitions formatted as now?
Click to expand...
Click to collapse
YAFFS2
Swapfiles aren't compatible with it.
Only 1 solution:
Create a loop-ext-file and loop mount it, put a swapfile on it and you're set.
But thats slow.
The partition wouldn't have to be formatted, you can use zeroed images for swap space, I've done it in Solaris before and I'm sure some of the memory techniques for Android have implemented this before, don't quote me!
maxisma said:
There was already an idea like that.
You mean using CACHE as swap partition.
At the moment this isn't possible because we would have to format this partitions and recovery wouldnt work then.
Click to expand...
Click to collapse
Is it not possible to use something like a swap file on the cache partition? I'm not familiar enough with the workings of Android, but I know that swap files are supported in Linux and I've seen it mentioned for Android, so is there any reason this wouldn't work? It would be an amazing improvement. I see you answered while I was typing this post, thanks.
I do wish people would stop putting their ideas as [new solution] and stuff and just put it forward as an [idea] or [concept] until there's a working implementation.
maxisma said:
YAFFS2
Swapfiles aren't compatible with it.
Only 1 solution:
Create a loop-ext-file and loop mount it, put a swapfile on it and you're set.
But thats slow.
Click to expand...
Click to collapse
Would the loop mounting be slow to create or slow for performance? I wouldn't mind a bit more boot time if it meant onboard swap, but obviously if it's a slowdown vs SD or none at all, it's probably not worth it.
How would u format a folder like that??? We could elimate the recovery and instead of useing it for 50 mb swap. Let's use it on the system folder. And then we could than drag eclair in our phones but then we would have to be stuck have just one rom. We could also ask rom devs to make us img instead of .zip roms so we could just flash the images
What about Nandroid etc?
This is a must-have.
Also I think the formation of the partition would be overwritten with every reboot..
But idk.
Won't try it out.
there's an issue for using /cache as swap or compcache like maxisma said.. recovery uses a small portion of /cache to write it's files to temporarily so this wouldn't be an easy work around. this idea was already started a long time ago by shafty and well, it never turned out.
maxisma said:
YAFFS2
Swapfiles aren't compatible with it.
Only 1 solution:
Create a loop-ext-file and loop mount it, put a swapfile on it and you're set.
But thats slow.
Click to expand...
Click to collapse
You don't need a swap partition, neither real nor looped
Code:
# dd if=/dev/zero of=/cache/swapfile bs=1M count=XX
# mkswap /cache/swapfile
# swapon /cache/swapfile
Ooops, forget about it: swapon (as a busybox internal) can't do that on my CM. It does work on my machines :/
But remember guys we also have the spl as backup. We could make the nandro-backup into a .nbh file to flash but it takes a longer time to do it. We could make an app or script that does it for as. I tried to customize the init.rc, build.prop, and fstab but it changes everytime - reboot. What should I do? These files were rewriten when I rebooted. If you guys want to talk this over with me and some of my friends on gtalk, I'll create a group for us to talk more in depth. My email address is [email protected].
jroid said:
there's an issue for using /cache as swap or compcache like maxisma said.. recovery uses a small portion of /cache to write it's files to temporarily so this wouldn't be an easy work around. this idea was already started a long time ago by shafty and well, it never turned out.
Click to expand...
Click to collapse
How much code do we have for recovery? I know there are modified recovery images, I have used Cyano and RA. It seems like it would be possible to create a small ramdisk or loop mount for recovery to use and recover this RAM for use by our applications. Or a mod to the init script to format that device properly for recovery when it boots and run mkswap on it when we boot to normal mode. I'm not real familiar with Android at this level, so perhaps I'm way off base here.
Do you know how to put a custom init.rc on to the g1? When I reboot it is gone and goes back to the orginal init.rc
mohsinkhan47 said:
Do you know how to put a custom init.rc on to the g1? When I reboot it is gone and goes back to the orginal init.rc
Click to expand...
Click to collapse
You have to change the one in the initial ram disk.
1) unpack boot.img
2) change initrc
3) repack boot.img
4) flash
farmatito said:
You have to change the one in the initial ram disk.
1) unpack boot.img
2) change initrc
3) repack boot.img
4) flash
Click to expand...
Click to collapse
I did that but got " broken image file ". What do I do now?
If the 50MB on the cache partition is never used, would it be possible to re-map it to /system? Probably something akin to what the "Death" SPL did.
That is what I said but then I guess you would have to reformat the phone to accept a different amount of info in this case megabytes. We would have to reformat the system folder to hold more info on it.
rgawenda said:
You don't need a swap partition, neither real nor looped
Code:
# dd if=/dev/zero of=/cache/swapfile bs=1M count=XX
# mkswap /cache/swapfile
# swapon /cache/swapfile
Ooops, forget about it: swapon (as a busybox internal) can't do that on my CM. It does work on my machines :/
Click to expand...
Click to collapse
YAFFS2 doesn't support swapfiles.
Thats why would need a loop mounted ext-image.
Placing a swap file/partition in internal memory is risky business. Flash memory has a limited number of write cycles, and swap does many writes per second. Whereas an SD card can be replaced if worn out, internal memory cannot, so the phone becomes a brick if the flash memory is damaged by swapping.

partition sd card

I reverted back to cinni bell froyo from 6.3 R3
I would like to get link2sd card to work. I got it semi working but it would use 10% of what I allocated and then say it was full so I couldnt install anything from there on.
I partitioned it using gparted... 15g and 1g for the ext2.
open recovery checking with sdcard utiilites. errors and says it fixes it.
check with the froyo sd card util and do not see the added space... says around 100meg
download and install link2sd.. crashes and pull battery... odd time I get it to install and when i select to move a program to sd it has a container error.
I can use the link feature tho.
Sometimes I get the memory is full and other times I get get a crash when I attempt to install either from apk or from market... (i have gotten different results between attempts to get the sd card partition properly from googling all sorts of threads)
I don't know what I'm doing wrong. Any help would be greatly appreciated!
Would the sd card util say the added space if the partition worked properly?
I don't think the cincinnati bell froyo supports Link2SD without changing the boot scripts (because it does automatic app2ext). How did you try to add Link2SD support?
I guess thats why I am having so much trouble. The Cinni keeps changing it on me?
I either installed the link2sd from sd card or from the market.
You're going to have to edit the /system/oc file. First copy the original to /system/oc.bak then edit /system/oc. At the end of /system/oc you will see:
Code:
# enable sd-ext
if [ -e /dev/block/mmcblk0p2 ] ; then
insmod /system/lib/modules/ext2.ko
insmod /system/lib/modules/jbd.ko
insmod /system/lib/modules/ext3.ko
[B] mount /dev/block/mmcblk0p2 /sd-ext
if [ $? -eq 0 ] ; then
mkdir /sd-ext/app ; chmod 777 /sd-ext/app
[[ -d /data/app ]] && cp -a /data/app/* /sd-ext/app/
[[ -d /data/app ]] && rm -R /data/app
ln -s /sd-ext/app /data/app
fi
[/B] fi
Delete the bolded lines.
Honestly, I strongly recommend RusMod 1.19 over the CBW if you really want to run a Dexter13 ROM. http://forum.xda-developers.com/showthread.php?t=1118575
I nandroided an image without link2sd.
I edited the OC file as suggested.
Restarted device. Installed Link2sd.
Rebooted again.
Tried to move a program and it is still getting the container error.
Went back to open recovery and checked with the sd utilities and it said
ext2 was ok.
So I guess I will try that russianmod and see how that goes.
I'll have to wait till it downloads. Its really slow...
Does that one still give full camera function?
xtwister6 said:
I nandroided an image without link2sd.
I edited the OC file as suggested.
Restarted device. Installed Link2sd.
Rebooted again.
Tried to move a program and it is still getting the container error.
Went back to open recovery and checked with the sd utilities and it said
ext2 was ok.
So I guess I will try that russianmod and see how that goes.
I'll have to wait till it downloads. Its really slow...
Does that one still give full camera function?
Click to expand...
Click to collapse
i'd try khalpower's v4 rom. it was my favourite before cm6 arrived. it has full camera functionality. get the one thats themed with steelepicblue. everyone's favourite. hehe
eejin2 said:
i'd try khalpower's v4 rom. it was my favourite before cm6 arrived. it has full camera functionality. get the one thats themed with steelepicblue. everyone's favourite. hehe
Click to expand...
Click to collapse
+1 on that. Too bad it isn't being worked on anymore, but it still works plenty good enough and stable too. I miss the radio but I have managed w/o it and moved on to Tune-in, Jango and Iheart.
I am always harking on this but ext partitions don't have to be sooo big. A good size is 350-400mb and even sometimes that is too big. 1GB imho is way too much wasted space that could be used for music, movies, pix,...
Figure that an average app is on the heavy side (like Flash or something like that) not usually more that 15-20mb. Like I said, on the heavy side. I have 60+/- apps and only about 125mb taken up in my partition. My /cache partition will fill up faster than my ext partition.
Look at it like this
8 bits = 1 Byte
1024 Bytes = 1 Kilo Byte
1024 Kilo Bytes = 1 Mega Byte
1024 Mega Bytes = 1 Giga Byte
1024 Giga Bytes = 1 Tera Byte
You would have to have a crapload of moster MBs (like Flash/ Moboplayer/ Angry Birds) to take up that whole 1gb partition. And even then your dalvik-cache will be too full to take that many apps and you'll have to start deleting some to make space.
xtwister6 said:
download and install link2sd.. crashes and pull battery... odd time I get it to install and when i select to move a program to sd it has a container error.
I can use the link feature tho.
Click to expand...
Click to collapse
I think I may have misunderstood what you wrote. So, Link2SD is working, it's the native froyo App2SD that doesn't work? You may have to delete the /sdcard/.android_secure directory.
So I thought I would start from scratch.
Put Bright 2.1 rom
Put steel blue v4 as suggested.
Install the link2sd 1.9.1
When I try to put an app on the SD it gives me an error
Failure
pkg: /data/app/ (filename.apk)
Then it says its on the sd. So I check the sd-ext directory and nope..
So I thought I could just create the directories data/app/
but still get the above failure
I tried changing the ext2.ko file to the 840kb but that doesn't do anything.
This os version doesnt have the OC file as stated above.
I think I'm close and don't know what else to try.
I appreciate the help.
-- I also redid the sdcard with gpart
formatted the whole card to fat32
-resized and created the ext2 partition
formatted to 500 meg using ext2
Woodrube said:
Figure that an average app is on the heavy side (like Flash or something like that) not usually more that 15-20mb. Like I said, on the heavy side. I have 60+/- apps and only about 125mb taken up in my partition. My /cache partition will fill up faster than my ext partition.
.
Click to expand...
Click to collapse
does link2sd not create use the ext2 if you link it? That's why I am trying to get this to work so that it doesn't touch too much of the internal memory?
Mioze7Ae
I am attaching the sd-card diagnotics like it says in your sig.
It does say fix me but I've run the util and it seems to go back to needing
repair each time after starting up?
Thanks for posting the sdcard-info.txt. You need to create an empty /sd-ext/link2sd directory and reboot.
I tried that and I am still getting the same error. Do I have to add sub directories into the link2sd directory such as data/app ?
No, you shouldn't have to touch /data at all and you don't need to do create any directories other than /sd-ext/link2sd. Can you rerun the diagnostics?
attached is the diagnostics.
Again thanks for your help!
Ate you putting your app folder on /sdext/link2sd and not /data/lunk2sd? Remember if you are using link2sd you name your folder link2sd. If you are using app2ext you name it app. It also kind of looks from the txt file that your ext partition is an ext4. Might be reading that wrong bit I definitely see ext4 in there and kahls v4 doesn't support that.
Edit: quick question. How are you trying to "put" your apps on ext? Hopefully you aren't going to settings>apps>manage>move to SD.
Oh, sorry I didn't also catch this the first time... only our most recent ROMs support ext4 (CM6, XDAspecial, Bravo). ext3 should work and ext2 will definitely work. You can use nandroid to backup your sd-ext partition (I think it's called SD data in the nandroid menus), Then just nandroid restore it and your /sd-ext will be reformatted as ext2.
It should be ext2. Thats how I formatted the partition.
I had both folders /data/app and link2sd on the card. I deleted the /data/app folder and rebooted.... still getting the error.
it seems to keep pointing to data/app folder in the error message
Oh, you're right. I was misreading my own diagnostic log. *facepalm* Hmm. Nothing looks wrong...
Here Mz, this is for you. Found it on another thread.
Do you have this folder, sd-ext/link2sd? What error do you get when you launch the link2sd apk? IIRC /data/app is only symbolic links.
Might want to reformat and start over by just putting folder in SD-ext/link2sd and wiping out all the previous issues. Am usually against reformatting, but in this case might be best option.

Categories

Resources