Related
Hello
I want to modify my partition table, I've read users get better 3D performance (in games) with a bigger Cache partition.
3D performance aside, what's the recommended minimum size I should set it to without compromising overall performance?
I'm using a Sense based rom if it matters.
Thanks!
Not sure... I'm running an AOSP ROM with the N1 table. No performance lag for me.
Android uses the cache partition, to cache memory, giving it much faster access to it, so obviously the bigger your cache, the more cached ram your device has access too, also the market uses the cache for downloads, so if you have a 10mb cache partition you cant download a 14mb app off the market ect...
Sent from my HTC Desire using Tapatalk
AndroHero said:
Android uses the cache partition, to cache memory, giving it much faster access to it, so obviously the bigger your cache, the more cached ram your device has access too, also the market uses the cache for downloads, so if you have a 10mb cache partition you cant download a 14mb app off the market ect...
Sent from my HTC Desire using Tapatalk
Click to expand...
Click to collapse
but how to modify the cache partition, or how to know the exact size of it?
Thanks,
williepeng said:
but how to modify the cache partition, or how to know the exact size of it?
Thanks,
Click to expand...
Click to collapse
This thread is nearly 3 years old and a bit redundant now.
You can modify the cache partition by using what is known as a custom hboot.
An hboot has 3 partitions: /system /data and /cache. Assuming you have not changed it, you are still on 'stock hboot' and your cache partition is 40MB. Your /system is 250MB, and your /data (internal memory) is only 147MB
However, nowadays we use custom hboots to change these sizes. We reduce /system and /cache in order to increase /data (-> more space for apps).
The /cache argument above is basically redundant because it is just used for temporary files. Most custom hboots actually reduce this cache partition from 40MB to 5MB.
Basically there is no real need to change the cache partition, certainly no need to make it bigger.
Also, you need to be "S-OFF" to achieve any of this. As this is your first post I'm not sure what other reading you've done and what your ultimate goal is.
Just got a notification for a thread about a device i havent even had for 3 years lol
Sent from my HTC One X+ using Tapatalk
eddiehk6 said:
This thread is nearly 3 years old and a bit redundant now.
You can modify the cache partition by using what is known as a custom hboot.
An hboot has 3 partitions: /system /data and /cache. Assuming you have not changed it, you are still on 'stock hboot' and your cache partition is 40MB. Your /system is 250MB, and your /data (internal memory) is only 147MB
However, nowadays we use custom hboots to change these sizes. We reduce /system and /cache in order to increase /data (-> more space for apps).
The /cache argument above is basically redundant because it is just used for temporary files. Most custom hboots actually reduce this cache partition from 40MB to 5MB.
Basically there is no real need to change the cache partition, certainly no need to make it bigger.
Also, you need to be "S-OFF" to achieve any of this. As this is your first post I'm not sure what other reading you've done and what your ultimate goal is.
Click to expand...
Click to collapse
Thanks you for your answer. Yes, I'm a beginner and only know the basic about Android system.
Actually I'm make a cache.img that can be flashed into a Samsung device with the recovery.img, but I don't know whether it would destroy the system if the one I made is bigger or smaller than the one in stock ROM.
williepeng said:
Thanks you for your answer. Yes, I'm a beginner and only know the basic about Android system.
Actually I'm make a cache.img that can be flashed into a Samsung device with the recovery.img, but I don't know whether it would destroy the system if the one I made is bigger or smaller than the one in stock ROM.
Click to expand...
Click to collapse
Well welcome to the Android world
Each device is different, so Samsung root methods are also different.
DO NOT flash any cache.img for this phone. You don't need to adjust any cache sizes...and you'll more than likely brick your phone if you manage to somehow flash it.
For this device, I always recommend you start here, read it many times
eddiehk6 said:
Well welcome to the Android world
Each device is different, so Samsung root methods are also different.
DO NOT flash any cache.img for this phone. You don't need to adjust any cache sizes...and you'll more than likely brick your phone if you manage to somehow flash it.
Click to expand...
Click to collapse
Actually flashing cache partition cannot brick the phone since it doesn't carry any unique content. For the same reason you don't need to flash it at all, system will create all necessary files by itself.
dean15 said:
Actually flashing cache partition cannot brick the phone since it doesn't carry any unique content. For the same reason you don't need to flash it at all, system will create all necessary files by itself.
Click to expand...
Click to collapse
Actually eddie was on bout flashing the samsung cache.img the guy had so yh u could/would brick ur phone. And the desire's internal memory layout is divided into 3 partitions, system (250mb) cache (40mb) data (147mb) totally size is 437mb, soo if the guy flashed just the cache.img it would probably **** up the phone's memory leaving u with a paper weight
dean15 said:
Actually flashing cache partition cannot brick the phone since it doesn't carry any unique content. For the same reason you don't need to flash it at all, system will create all necessary files by itself.
Click to expand...
Click to collapse
All I can say is I don't recommend it at all...I also really hope you're not thinking about flashing something meant for a Samsung phone.
The cache partition may not carry any unique content, but flashing an hboot is a critical part of the phone. A corrupted hboot flash = brick
Even if you somehow successfully managed to flash a cache separately...ultimately you won't actually gain anything by doing so.
Choice is yours, but don't say we didn't warn you
eddiehk6 said:
All I can say is I don't recommend it at all...I also really hope you're not thinking about flashing something meant for a Samsung phone.
The cache partition may not carry any unique content, but flashing an hboot is a critical part of the phone. A corrupted hboot flash = brick
Even if you somehow successfully managed to flash a cache separately...ultimately you won't actually gain anything by doing so.
Choice is yours, but don't say we didn't warn you
Click to expand...
Click to collapse
)))
OK, we're talking about the same thing in different words.
Hello guys
I´m new here and also quite new to the custom rom scene.
You can skip my story if you want. The questions are below
I bought a Desire (bravo Amoled) around a year ago with a T-mobile Branding.
At this time the actual android version was 2.1 Eclair. Later tehre was 2.2 Froyo out. Becaus i didn´t wanted to wait for the T-mobile update I debranded my phone so get the open 2.2 Froyo update.
I was so happy Froyo had the App2SD function, because now i can intall more apps then before. But with all the updates for google maps, google mail, facebook apps...and user that have to stay on phone memory and the user apps moved to SD still storing data on the internal memory and the dalvik cache i soon again had space problems. Still i can´t install all apps i like.
So lived with this problem not aware of a solution till 2-3 weeks ago, where i finally rooted my phone and installed a custom Rom with A2SD+.
Now I have a rooted, S-OFF phone with Insertcoin V49 A2SD+ Version. And i thought there would be no more space problems, because the dalvik cache and all apps are now on the fake internal memory (1,5 GB ext3). But NO, there are still apps storing stuff on the real internal memory. At last i had problems to move Plants vs. Zombies (~70MB) from SD (Froyoinstall) to the ext, because the internal mem hadn´t enough space and it wouldn´t let me move.
Next step CM7 Hboot?
So here are some questions to understand how that works.
1. When i install a CM7 Hboot, the data partition (internal memory) will be bigger, yes? Means there will be almost double space for app DATAs?
2. The system partition, where the actual ROM is stored and booted is smaller?
2a. But that means some parts of the ROM need to be moved to the SD?
2b. Doesn´t this make the entire phone slower? Because reading from the SD card is slower then from nand? (8GB Class4)
2c. Is there higher power consumtion because of constantly SD access?
3. The cache partition is dramatically decreased to 5 MB. What is ist used for and will there any diadvantages because of the small size?
4. What happens with the Dalvik? Where is ist stored?
5. Does A2SD+ still work with the CM7 insertcoin version? (big ext 3 fake internal memory) or only Froyo A2SD with the bigger real internal memory?
6. How do people get 160-180 free RAM? I have around 100-110 MB.
So my goal is to get as much space available for user apps and getting a faster device (or at least dont get a slower one)
Hope someone read all my questions and can give me clarity..
Thanks in advance
Beegee
no one?
indbeegee said:
So here are some questions to understand how that works.
1. When i install a CM7 Hboot, the data partition (internal memory) will be bigger, yes? Means there will be almost double space for app DATAs?
2. The system partition, where the actual ROM is stored and booted is smaller?
2a. But that means some parts of the ROM need to be moved to the SD?
2b. Doesn´t this make the entire phone slower? Because reading from the SD card is slower then from nand? (8GB Class4)
2c. Is there higher power consumtion because of constantly SD access?
3. The cache partition is dramatically decreased to 5 MB. What is ist used for and will there any diadvantages because of the small size?
4. What happens with the Dalvik? Where is ist stored?
5. Does A2SD+ still work with the CM7 insertcoin version? (big ext 3 fake internal memory) or only Froyo A2SD with the bigger real internal memory?
6. How do people get 160-180 free RAM? I have around 100-110 MB.
Beegee
Click to expand...
Click to collapse
Hi beegee,
I'm new to this myself, so not an expert, but I just flashed the CM7r2 hboot myself and will help where I can. Note, I am using CyanogenMod7, not InsertCoin.
1. Yes, the system and cache partitions used by the phone ROM are decreased substantially, system decreases from 250MB to 145MB and cache from 40MB to 5MB. This extra space is then added to the internal data partition for your apps and games. I only have a few apps installed at the moment and my data partition is 287MB total, 21MB used, 266MB free space.
2. Yes, see above.
2a. No, the ROM only requires 145MB, none of it is stored on the sdcard.
3. I'm sure the cache must be a fixed size. Mine (with CyanogenMod7) has remained at 4MB since install so a 5MB partition is large enough.
4. I store dalvik-cache on the ext3 partition of my sdcard as you are doing now. If you moved it back to the phone memory it would be stored in the data partition.
5. I use a version of A2SD with the CM7 hboot and it works fine.
6. I've not used insertcoin but as I said in the first answer I have 287MB data partition in my phone now. This is due to using the CM7 hboot.
Hope this helps,
Steve
The larger cache size from the stock Hboot is meant for OTA updates so we have no use for that. It's also used to flash radio images from recovery. If your cache is too small, like it is in the CM7 and Oxygen Hboots, you will need to flash the radio via fastboot but you don't really need to worry about flashing radio's anyways..can look into that later if you want.
Thanks for the answers by now.
What i found out:
The Insertcoin is a Sense enabled rom. The zip of the Rom is about 288 Meg big. Its not an AOSP like Cyanogen, which is so sleek to fit completely in the smaller system partition. I extracted both Insertcoin A2SD and CM7 zips and found that they have a sdext folder. On the cm7 version it is 365 Meg and on the a2sd+ 80 Meg big. So both versions install files on the external partition.
Only open question now is if the CM7 version supports A2SD+
Edit: Obviously the CM7 version has no A2SD+
Also the the new bigger system partition only has ~ 80 Meg free after first boot ?!
Hello. I haven't installed, yet a custom ROM (I'm still on Rooted Stock), but documented a little to understand even better what each ROM does.
1. I saw that you wanted a very fast ROM, the only ones that are really fast are the AOSP ROM's since they are in the most minimalistic form possible --> ~150MB
2. You should also take in consideration that a small cache partition may slow down some games. This was tested and problems appeared at some games, which use some improved graphics. The games also store there some of the "graphics files"? and since the partition is too small, it has to constanly read/write/delete.
3. CM7 version supports A2SD+: you should read the whole thread from here: http://forum.xda-developers.com/showthread.php?t=917570. It explains all. As I have read some of it two things popped-up:
-CyanogenMod do not officially support a2sd, i'm working on it because desire (not only) desperatly need it (cutted down Firerat script)
-Other a2sd can be used, this is just the easiest way: use recovery to partition your SD then install cm7_legacy_a2sd_rX-signed.zip
Hope this helps you.
UsManyDead said:
Hello. I haven't installed, yet a custom ROM (I'm still on Rooted Stock), but documented a little to understand even better what each ROM does.
1. I saw that you wanted a very fast ROM, the only ones that are really fast are the AOSP ROM's since they are in the most minimalistic form possible --> ~150MB
2. You should also take in consideration that a small cache partition may slow down some games. This was tested and problems appeared at some games, which use some improved graphics. The games also store there some of the "graphics files"? and since the partition is too small, it has to constanly read/write/delete.
3. CM7 version supports A2SD+: you should read the whole thread from here: http://forum.xda-developers.com/showthread.php?t=917570. It explains all. As I have read some of it two things popped-up:
-CyanogenMod do not officially support a2sd, i'm working on it because desire (not only) desperatly need it (cutted down Firerat script)
-Other a2sd can be used, this is just the easiest way: use recovery to partition your SD then install cm7_legacy_a2sd_rX-signed.zip
Hope this helps you.
Click to expand...
Click to collapse
Hello
Thanks for the infos. I know the ASOP roms are faster, but i don´t want to miss the Sense UI.
To 3. I think there was a misunderstanding. When is say CM7 i dont mean the rom "CyanogenMod7" but the CM7 Hboot Version of Insertcoin rom.
I just tried to postinstall a2sd via http://www.darktremor.info/files/a2sd/dtapps2sd-2.7.5.3-beta04-signed.zip
But after installation in recovery, the phone wont boot Insertcoin. Stuck at Alpharev Bootstreen now.
jordan.harris01 said:
The larger cache size from the stock Hboot is meant for OTA updates so we have no use for that. It's also used to flash radio images from recovery. If your cache is too small, like it is in the CM7 and Oxygen Hboots, you will need to flash the radio via fastboot but you don't really need to worry about flashing radio's anyways..can look into that later if you want.
Click to expand...
Click to collapse
Presumably the HBOOT and Radio partitions are the same size whichever HBOOT you use, and Radio immediately follows HBOOT. Otherwise you would have to flash the Radio if you changed he partition map by (eg) going from Stock to CM7.
indbeegee said:
I just tried to postinstall a2sd via http://www.darktremor.info/files/a2s...a04-signed.zip
But after installation in recovery, the phone wont boot Insertcoin. Stuck at Alpharev Bootstreen now.
Click to expand...
Click to collapse
If you've done a nandroid back-up before trying to flash the A2SD+ scripts (which is advised!!!) you should go back to recovery and restore it. You should go back to your InsertCoin again and try the steps once again. Maybe you did something wrong or got a wrong file.
UsManyDead said:
If you've done a nandroid back-up before trying to flash the A2SD+ scripts (which is advised!!!) you should go back to recovery and restore it. You should go back to your InsertCoin again and try the steps once again. Maybe you did something wrong or got a wrong file.
Click to expand...
Click to collapse
No, i didn´t made a nandroid backup, because ist was a new Insertcoin CM7 install. No personal data to lose.
I just wiped and made a new install. Now i have 199 Meg internal memory free.
Edit: After installing DT A2SD in recovery again, the phone is again stuck at Alpharev splash What now?
Edit2: After installing the Rom over without wipe, Insertcoin boots normaly. But i encountered, force reboots when installing any app.
So i made a new fresh isntall.
Conclusion: Insertcoin uses my Ext4 for its Data. But will not use it as fake internal memory. My Ext4 is ~1,5 GB big. Insertcoin uses 600 MB from it and the leftover 900 MB are wastetd, because no one uses it.
Edit 3: Insertcoin doesnt like Ext4. Everytime i tried to install Astro File Manager fom Market the phone rebootet. No problem with Ext3
Hi all.
I'd like to understand better the "alternate HBOOTSs and internal partitions" thing.
I've tried to look around but the information seems to be quite scattered.
What I'd like to understand is:
1. Pros and cons in general
2. Whether and how should i change my SD partitioning
Thanks.
with default hboot your system partition is 250mb.
some roms like oxygen or cm7 dont need 250mb. so installing them on stock hboot is a waste, lots of MBs arent used neither by ROM nor by you since we cant install apps in system.
so thats why there are custom hboots, so you use a CM7 hboot with CM7 rom, system is big enough to hold the ROM and you get bigger /data which is where apps go.
EXT is needed if it is writtien in the ROM thread.
there are also Sense 2.1/3.0 roms that run on data++ or cm7 hboots AND ext.
so for example insertcoin CM7 - 130mb is available on nand, however /system of the ROM is bigger. so essetntial parts go into nand, rest is stored on sd-ext. system is still super-fast, as apps run from NAND, not from ext. files present on ext are not essential for the system speed.
so generally
pros: super fast roms since apps run from NAND, lots of space for apps
cons: if you are a retard you can brick your phone if you flash something wrong
dzumagos said:
with default hboot your system partition is 250mb.
some roms like oxygen or cm7 dont need 250mb. so installing them on stock hboot is a waste, lots of MBs arent used neither by ROM nor by you since we cant install apps in system.
so thats why there are custom hboots, so you use a CM7 hboot with CM7 rom, system is big enough to hold the ROM and you get bigger /data which is where apps go.
EXT is needed if it is writtien in the ROM thread.
there are also Sense 2.1/3.0 roms that run on data++ or cm7 hboots AND ext.
so for example insertcoin CM7 - 130mb is available on nand, however /system of the ROM is bigger. so essetntial parts go into nand, rest is stored on sd-ext. system is still super-fast, as apps run from NAND, not from ext. files present on ext are not essential for the system speed.
so generally
pros: super fast roms since apps run from NAND, lots of space for apps
cons: if you are a retard you can brick your phone if you flash something wrong
Click to expand...
Click to collapse
+1
Sent from Oxygen
1st of all, thanks for the explanation!
So, If I understood well, my favorite ROM, which is Reflex S v2.1.7 should be installed in the CM7HBOOT variant. This ROM claims to support "AP2SD+".
Now, If the apps go in the internal /data partition, why should I bother about the EXT3 partition on my SD?
Very likely I'm still missing something else ...
Uqbar said:
1st of all, thanks for the explanation!
So, If I understood well, my favorite ROM, which is Reflex S v2.1.7 should be installed in the CM7HBOOT variant. This ROM claims to support "AP2SD+".
Now, If the apps go in the internal /data partition, why should I bother about the EXT3 partition on my SD?
Very likely I'm still missing something else ...
Click to expand...
Click to collapse
A2SD/A2SD+ works on this way:
Usually all apps will be installed to /data partition in the internal memory. If you use a2sd/a2sd+, all apps will be automatically redirected to /sd-ext/app. That's a2sd. When dalvik cache is also moved on sd ext, you use a2sd+. The big advantage is, you do not have to move apps yourself to sd card. It will be done automatically, wether the developer of the app has programmed the app for this or not.
NEVER MOVE APPS TO SD MANUALLY WHEN USING A2SD/A2SD+!!
Referring to reflex s rom running cm7 hboot. Actually, the /system partition of cm7 hboot (130 mb or 145 mb with r2 version) does not give you enough space for reflex s rom. So things will be moved to internal /data partition. Problem is, you don't have enough space for apps because internal /data partition gets filled. To avoid this problem you need the ext partition on your sd card.
Conclusion: You should really bother about an ext partition!!!
MatDrOiD said:
Conclusion: You should really bother about an ext partition!!!
Click to expand...
Click to collapse
I though to choose CM7HBOOT to have faster application startup.
You say that Reflex S will fill the /data up and the other apps will end in /sd-ext/app, that is my (sloooow) uSD.
So my question: do you think it's really worth it installing CM7HBOOT with this ROM?
no, no, no, it is not the way matdroid said.
/system is bigger than 130mb (or 145mb) so essential parts stay on NAND, rest goes to SD-EXT, to the folder that is symlinked to the /system (not to /data)
now the apps that you download.
in order for you to understand it, i need to explain a bit. this rom is deodexed. if you really want to know what .odex file is do some research, it is not important. anyway in deodexed roms, apps run from Dalvik-cache and not from the .apk itself (.apk is only needed to create dalvik on 1st boot)
so in reflex S your .apk go to sd-ext BUT the dalvik stays in internal, and since its dalvik what matters ROM is fast.
rom system files do not fill up /data, the /system files that could not fit into 130mb go to sd-ext.
and overally yes, it is worth it, i basically re-discovered my desire after S-OFFing and running custom hboot roms. i have a class 2 sd card, and rom performs super fast (on custom hboot roms your sd class really doesnt matter anymore)
Uqbar said:
1st of all, thanks for the explanation!
So, If I understood well, my favorite ROM, which is Reflex S v2.1.7 should be installed in the CM7HBOOT variant. This ROM claims to support "AP2SD+".
Now, If the apps go in the internal /data partition, why should I bother about the EXT3 partition on my SD?
Very likely I'm still missing something else ...
Click to expand...
Click to collapse
and also i as wrote before ....
why should you bother about ext ???
cause /system is 130mb (or145) but it is not enough !!! AND I DID WRITE THAT REST GOES TO SD-EXT.
seriously, you gotta read everything if you are going to s-off and play with custom hboots
and also apart from some /system files on sd-ext, your downloaded .apk's will be on sd-ext too. only their dalvik will stay on NAND
dzumagos said:
no, no, no, it is not the way matdroid said.
/system is bigger than 130mb (or 145mb) so essential parts stay on NAND, rest goes to SD-EXT, to the folder that is symlinked to the /system (not to /data)
now the apps that you download.
in order for you to understand it, i need to explain a bit. this rom is deodexed. if you really want to know what .odex file is do some research, it is not important. anyway in deodexed roms, apps run from Dalvik-cache and not from the .apk itself (.apk is only needed to create dalvik on 1st boot)
so in reflex S your .apk go to sd-ext BUT the dalvik stays in internal, and since its dalvik what matters ROM is fast.
rom system files do not fill up /data, the /system files that could not fit into 130mb go to sd-ext.
and overally yes, it is worth it, i basically re-discovered my desire after S-OFFing and running custom hboot roms. i have a class 2 sd card, and rom performs super fast (on custom hboot roms your sd class really doesnt matter anymore)
Click to expand...
Click to collapse
Good to know, thanks. Thought it would work the way I described.
Hmmm ... I don't understand why the ROM looks quite slower than before (STOCK HBOOT) ...
Accordingly to what dzumagos says, I should get a (much) better experience now.
I understand the Dalvik cache stuff and what he says makes sense to me.
Nonetheless the ROM seems to be way slower than before ...
My system should be 145MB, cache 5MB and data 287MB.
Settings say that I have 256MB available on /data e 34MB on /system.
This should mean that I'm not really exploiting the internal storage!!!
And in fact my 1GB ext3 partition is at 50% of capacity.
Now, if my /cache is 5MB as said by AlphaRev, I think it's way too small to fit the (Dalvik?) cache I'd need.
What'd be your view here?
Finally, I'm trying to read everything. But the information is scattered among a dozen of threads each with dozens of posts ... and, as you can see, it's far from easy to discern the cream from the crap.
I really tried to figure it out before posting!
Uqbar said:
Hmmm ... I don't understand why the ROM looks quite slower than before (STOCK HBOOT) ...
Accordingly to what dzumagos says, I should get a (much) better experience now.
I understand the Dalvik cache stuff and what he says makes sense to me.
Nonetheless the ROM seems to be way slower than before ...
My system should be 145MB, cache 5MB and data 287MB.
Settings say that I have 256MB available on /data e 34MB on /system.
This should mean that I'm not really exploiting the internal storage!!!
And in fact my 1GB ext3 partition is at 50% of capacity.
Now, if my /cache is 5MB as said by AlphaRev, I think it's way too small to fit the (Dalvik?) cache I'd need.
What'd be your view here?
Finally, I'm trying to read everything. But the information is scattered among a dozen of threads each with dozens of posts ... and, as you can see, it's far from easy to discern the cream from the crap.
I really tried to figure it out before posting!
Click to expand...
Click to collapse
Dalvik cache is not in the /cache partition.
I think I get the reasons for custom hboot but how do you tell which hboot you've got?
My Desire is rooted and S-OFF. I have flashed with STOCKHBOOT version of Reflex_S_2.1.7_LITE_GingerBread_Sense-2.1_GRI40_A2SD+
It works but don't know if I should have used the the CM7 version.
after s-offing you get a stock unlocked hboot.
roms designed for cm7 hboots will work on stock hboot but it works only this way.
MatDrOiD said:
A2SD/A2SD+ works on this way:
Usually all apps will be installed to /data partition in the internal memory. If you use a2sd/a2sd+, all apps will be automatically redirected to /sd-ext/app. That's a2sd. When dalvik cache is also moved on sd ext, you use a2sd+. The big advantage is, you do not have to move apps yourself to sd card. It will be done automatically, wether the developer of the app has programmed the app for this or not.
NEVER MOVE APPS TO SD MANUALLY WHEN USING A2SD/A2SD+!!
Referring to reflex s rom running cm7 hboot. Actually, the /system partition of cm7 hboot (130 mb or 145 mb with r2 version) does not give you enough space for reflex s rom. So things will be moved to internal /data partition. Problem is, you don't have enough space for apps because internal /data partition gets filled. To avoid this problem you need the ext partition on your sd card.
Conclusion: You should really bother about an ext partition!!!
Click to expand...
Click to collapse
Thanks for the heads up but am still a bit confused. Pls help me out.
I'm s-off and using the cm7 hboot running Insertcoin stable 1.0.8 cm7 version. Now in the rom under settings>applications>manage applications when you click on some apps you get the option to move the app to sd card and when you do so it frees up some internal memory. But you say not to move apps to sd card manually Should I do this or not?
Any help to clarify would be much appreciated
This is froyo/android a2sd and yes you can do it. It moves some app data to fat32 while a2sd+ move parts of the app itself (in this specific case the .apk only) to the ext. Dalvik will stay on internal unless you issue some superuser commands in adb or terminal.
Sent from my HTC Desire using XDA App
I'm also confused...so for Reflex S, which hboot should I be running?
Bravo Stock
Bravo N1Table
Bravo Data++
Bravo Sense
Bravo Oxygen r2
Bravo CM7 r2
Bravo Downgrader???
herb1 said:
I'm also confused...so for Reflex S, which hboot should I be running?
Bravo Stock
Bravo N1Table
Bravo Data++
Bravo Sense
Bravo Oxygen r2
Bravo CM7 r2
Bravo Downgrader???
Click to expand...
Click to collapse
Sense since its a sense rom?
herb1 said:
I'm also confused...so for Reflex S, which hboot should I be running?
Bravo Stock
Bravo N1Table
Bravo Data++
Bravo Sense
Bravo Oxygen r2
Bravo CM7 r2
Bravo Downgrader???
Click to expand...
Click to collapse
Use the recommended one. Maybe you need to search the thread for this.
You only need the downgrader if you flashed one of the r2 hboots and want to change it now.
Sent from Oxygen
Ok I use bravo sense but cm7 r2 does work with reflex s too
Then make sure you use cm 7 version of reflex!
I followed instructions on Apharev homepage and flashed the 'bravo_alphaspl-sense.img'
Downloaded the necessary PB99IMG zipfile and saved it to SD card
now phone goes silver ANDROID logo that reflects passing light after splash image but won't loaded my homepage afterwards
HELP????
Dear XDA forum,
since a few roms i always get a "low on storage" warning, even after factory reset and flashing a new rom.
So i'd want to ask for a small summery of what storage there is inside the desire and on the sdcard and how to solve this problem
My sdcard is 16GB class 10. I didnt partition it manually (i think).
according to my desire it has effective 14.2gb.about 2gb are used and 4gb are free? that doesnt sound right.
so i guess its 2 partitions?
could anyone please tell me which mountpoint is which?
and how do i solve the low storage problem? do i need some a2sd script or do i have to more the internal storage to the sdcard?
which mountpoints do the scripts actarlly move?
i have no problem with repartitioning my sdcard. i was given to understand that u usually need a fat32 partition (for apps i guess) and an ext2/3 partition afterwards. some scripts even allow a swap partition at the end of the sdcard to be used as swap space. is that a good idea?
i know its a lot of questions :/ but i hope for some good answers :>
thanks & greetings,
soomon
my advice would be to backup your sd card and (re)partition using gparted, start from scratch because I don't know what your current configuration is, step 5 here
choose ext3/ext4 partition (max ~1.5GB) depending on rom requirements, most support ext4 and should be slightly faster. most roms don't need swap partition.
in simple terms, your space will get taken up by apps (apks), dalvik cache, app cache and app data. most custom roms will automatically move apks to your sd-ext partition. there are various different scripts which move the other bits around. generally it is better to keep app data on internal (/data partition)
regardless of which rom you choose, use an app like 'diskusage' to browse all your partitions, so you can work out where and how all your space is being use.
to maximise space you also need to be s-off and correct hboot for the rom (again should be stated within each rom thread, or search within it)
ok so the first partition on the sdcard will become my sd-ext which will replace the /data partition on the internal storage.
I guess is hould try data2sd then?
with a class 10 it should not get that slow and i get loads of space on that partition.
thanks for your help.
also use links2d,very usefull.....
hi again,
as i see in a terminal emulator by typing "df -h"
my data is 150mb and has 15mb left, so i guess i better moe the whole partition to the sdcard as i'd have to move all the apps to the sdcard anyway sooner or later.
my /system has only 5mb of 250mb left. is that a problem?
soomon said:
hi again,
as i see in a terminal emulator by typing "df -h"
my data is 150mb and has 15mb left, so i guess i better moe the whole partition to the sdcard as i'd have to move all the apps to the sdcard anyway sooner or later.
my /system has only 5mb of 250mb left. is that a problem?
Click to expand...
Click to collapse
depends entirely what rom you're running if any, and what scripts it uses. basically you should be able to find some way to install many apps without running out of space (one of the main reasons for rooting in the first place ).
with your current setup, you could try something like link2sd to just move apps and dalvik to sd, see if you have enough space that way. you shouldnt have to manually 'move to sd', keeping them on 'internal' tricks them to sd-ext. (you can use something like 'diskusage' to check they're actually on the sd-ext)
the system partition is meant to be mostly full. free space on /system is wasted space.
you're still on stock hboot, which is why your data partition is so small.
if you install another rom, many of them have a smaller system size, so if you're s-off you can flash a different hboot to repartition your internal memory layout: your system size will reduce to roughly match your rom, and the saved space is converted into extra data space, see alpharev.nl for hboots.
e.g. if your rom system is 140MB, will fit nicely into cm7r2 hboot with 145MB system, and you get 287MB of data instead of 150MB. 287MB can be enough to store app data and dalvik cache if you don't have too many apps.
i refer you to these sets of guides for further reading, should explain a lot more, and better than i have...
thanks eddie,
i'm still s-on and stock hboot, but i use a custom rom: http://forum.xda-developers.com/showthread.php?t=1766550
i guess the problem is that LBE gues 4 and lookout together need over 22mb of space :/
i'll try link2sd then.
thanks!
hm.. when i try to install link2sd i get "insufficient storage available". that program is not even 1MB in size and i have 15mb of free space on the internal storage.. what can i do?
edit: i'll try to install it at home with an adb tool. maybe i have more luck with that.
follow instructions for a2sd with that rom (scroll down). this will move apps and dalvik to sd-ext automatically. or follow/search the thread for other methods, it's regularly discussed...
[not used link2sd, it should in theory do the same thing, but my advice would be to stick with the instructions as that's the recommended way if you really need/want to install link2sd...uninstall something else to make more space ]
ofc removing apps might help (althrough i only installed 2 or 3). but 15mb should be enough to install a 800kb software
gonna try to install some apps later after running a2sd.
thanks a lot man didnt see that information.
HI
Im new to this forum so please forgice me if my post is in the wrong place.
I have the 2010 htc desire and have it rooted and am running MILDWILD 8.0 which is great on this phone. my question is how do i add extra internal memory using partion ext on sd card. I can partion the sd card with clockword recovery but when i reboot it always hangs on the htc logo. can any one help with this?
Thanks
CWM-made partitions dont cope well with this phone. Reformat the partition using this guide.
I followed the guide but mildwild 8.0 still shows 148 on htc desire internal memory.
That's because you're still on stock hboot, no better than before it was rooted.
- Install DiskUsage, enable root and browse to your /system partition.
- You will see a lot of free space on /system. This is wasted space.
- You can convert this wasted space to extra /data (internal memory) by flashing a different hboot with a smaller /system partition.
(You need to be s-off for the following, if you're not, use 'revolutionary')
- Nandroid backup
- Flash cm7r2 hboot using fastboot
- Full wipe and nandroid restore
- Go again to DiskUsage, your free space on system is greatly reduced :good:, and your /data will go up to 287MB
- This 287MB will be used for app data (e.g. saved game data), and will allow for more apps to be installed.
- You won't see your sd-ext reported in your total internal memory (i.e. it won't read 'internal + sd-ext')
- Keep your apps on 'internal' (don't 'move to sd'), this will trick them automatically to sd-ext.
- If you use DiskUsage to browse to /sd-ext, you'll see apps and dalvik cache there, which means it's working as it should.
do i need to do this? if so can you show me a guide.
also does mild wild 8.0 have built in apps2sd scripts and if so how do i use them.
i have saw videos on youtube with the htc desire internal memory going from 148mb to 1.5gb how can i do this?
thanks
You don't technically need to do to it, but in order to gain more app space you should understand exactly how your memory is being used in the first place.
Apps2sd is already enabled in the ROM by default as stated in the ROM OP. You do not need to do anything extra. Like I said, keep apps on internal and your apps and dalvik cache will be moved to /sd-ext, you should be able to check this now with DiskUsage.
I recommend starting here for fastboot guide, that's the only thing you're missing. Flashing things through fastboot isn't that hard once you get used to it, and can be crucial in certain situations. Once you flash the ROM on cm7r2 hboot, you'll be using your space more efficiently and have a lot more space for apps.
I know 287MB doesn't seem like much more. But this is /data partition is only used for app data. This will still get filled up as you install apps, but much more slowly :good: The apps and dalvik cache which take up much more space go to sd-ext, which is what you want.
You can refer to the same videos if you really want to see 1.5GB internal memory, they likely use a 'data2sd' or equivalent script but in my experience it's not worth it. You would have to remove the current working script, and replace it with something else, which is risky if it's incompatible and untested. Even if you do this, you're not actually gaining anything extra. You have already created the sd-ext partition; it's size is whatever size you set it when you partitioned. It does not change depending on the A2SD script.
I understand that having a 'visible' 1.5GB memory looks better...but once you realise your partition is already there and being used correctly, you don't need to see it.
thanks
i now have 288mb of internal storage with an ext partion sd of 1.4gb,
is that all i need to do now?
so when i install apps the mildwild 8.0 rom will move all to ext4 partion automatically?
also some apps i use to use now say "compatible with your device" is there a way around this so i can install them on my desire?
Thanks
Pretty much yes. Keep them on internal as instructed (don't 'move to SD') to trick them to sd-ext.
All you really need is reassurance that your ext partition is actually being used, which is why I always recommend DiskUsage. Have you actually tried it as first recommended?
Browse to your /sd-ext (or similar name) folder, the one which is ~1.4GB in total size. What can you see?
As for incompatible apps. Don't know. Which ones, are they for higher versions of Android? Have you tried sideloading the apks?
eddiehk6 said:
Pretty much yes. Keep them on internal as instructed (don't 'move to SD') to trick them to sd-ext.
All you really need is reassurance that your ext partition is actually being used, which is why I always recommend DiskUsage. Have you actually tried it as first recommended?
Browse to your /sd-ext (or similar name) folder, the one which is ~1.4GB in total size. What can you see?
As for incompatible apps. Don't know. Which ones, are they for higher versions of Android? Have you tried sideloading the apks?
Click to expand...
Click to collapse
yes i have tried it as recommended.
when i browse /sd-ext i see 1423mib then the following dalvik-cache 76.7mib, app 66.4mib, system data 104.3 mib and freespace 1175mib
I also liked the guide on fast boot you sent me, as from using tips from it i was able to flash a new splash screen and boot animation. so thank you.
by side loading do you mean installing the apps with the apk file and not through the play store?
if so this works for some apps but now others. the app Im looking to use is the Argos app. before the recent update it worked fine but now when i went to update i get the device is incompatible message in play store. I have read some stuff on the build.prop method but am unsure if this would work.
tronic44522 said:
yes i have tried it as recommended.
when i browse /sd-ext i see 1423mib then the following dalvik-cache 76.7mib, app 66.4mib, system data 104.3 mib and freespace 1175mib
I also liked the guide on fast boot you sent me, as from using tips from it i was able to flash a new splash screen and boot animation. so thank you.
by side loading do you mean installing the apps with the apk file and not through the play store?
if so this works for some apps but now others. the app Im looking to use is the Argos app. before the recent update it worked fine but now when i went to update i get the device is incompatible message in play store. I have read some stuff on the build.prop method but am unsure if this would work.
Click to expand...
Click to collapse
Yep, all good, it's filling up so you have successfully added internal memory :good: plenty more space for apps.
Yeh that guide worked for me which is why I always recommend it. I liked changing the splash screen too (ironically can't be done on Nexus devices as far as I know)
Sideloading is as you described
The Argos app is compatible with Android versions 4.0 and higher as on the play store page, which is why it's incompatible with CM7 which is 2.3.x. The same probably applies to the other apps you're having trouble with. I've never messed with build.prop, probably could work, just make sure you make a nandroid backup before trying any of it.