I few Roms are available in DATA++ format. What exactly extra do they have and how does it compare to a2sd and d2ext?
http://forum.xda-developers.com/showthread.php?t=1036485
Data++ ROMs are "variant" of app2sd,aimed to have more speed by leaving dalvik cache on internal memory (most app2sd ROMs move apps and dalvik cache to sd-ext),on /data partition,BUT custom partion sizes are used to have bigger /data partition to have enough room for dalvik cache and still be able to install bunch of apps. Only "disadvantage" to data++ vs app2sd is that your device has to be s-off and you have to flash CM7 or Oxygen (or even data++) Hboot.
Can anybody tell me why some data++ roms give 302MB internal memory - CyanogenMod7
and others 212MB - RCMixHD 3.6.1 DeSensenized
I agree, they are different, number of preinstalled apps is different, but it is almost 100MB between them.
regards
Less apps installed in the AOSP ROMS on flash, just check their download size.
ur right, and i've checked also that dalvik of all apps goes to internal in RCMix.
another question
when i uninstalling an app in settings/application or in System app remover dalvik stayes and wasting memory, to keep it clean I have to delete it manually with Root Explorer.
is there any way to uninstall an app and automatic deleting also its dalvik?
Apps2SD
xarus08 said:
Can anybody tell me why some data++ roms give 302MB internal memory - CyanogenMod7
and others 212MB - RCMixHD 3.6.1 DeSensenized
I agree, they are different, number of preinstalled apps is different, but it is almost 100MB between them.
regards
Click to expand...
Click to collapse
AFAIK, CyanogenMod 7 doesn't use data++, but Apps2SD. I tried to link to their Wiki, but the forum won't allow me because I'm new here. You can find the link titled "Apps2SD" on their wiki's homepage.
shamanNS said:
Data++ ROMs are "variant" of app2sd,aimed to have more speed by leaving dalvik cache on internal memory (most app2sd ROMs move apps and dalvik cache to sd-ext),on /data partition,BUT custom partion sizes are used to have bigger /data partition to have enough room for dalvik cache and still be able to install bunch of apps. Only "disadvantage" to data++ vs app2sd is that your device has to be s-off and you have to flash CM7 or Oxygen (or even data++) Hboot.
Click to expand...
Click to collapse
Sorry for being a Nood (just saw de Noob vid ) but can you tell me what "device has to be s-off and you have to flash CM7 or Oxygen (or even data++) Hboot." mean? I an planning to install LeeDroid Data++ for HTC Desire!
ankushkool said:
Sorry for being a Nood (just saw de Noob vid ) but can you tell me what "device has to be s-off and you have to flash CM7 or Oxygen (or even data++) Hboot." mean? I an planning to install LeeDroid Data++ for HTC Desire!
Click to expand...
Click to collapse
It means you have to gain s-off using alpharev and then flash alternative hboot using fastboot. You have a lots of reading to do if you didn't know what it meant in the first place. Start by googling alpharev.
Related
Hello everyone,
I have a couple of questions regarding the Bravo CM7 partition table and Data++ (by ClassicalDude). I'm S-ON, so I have the stock partition table.
1) Does having the CM7 table make a ROM (for instance CM7 or RCMix S) run faster? And why? Does it have something to do with the large /data partition?
2) About data++: I understand that the dalvik cache is retained in the internal memory, and the .apks are moved to SD-ext. Does that include the .apk's provided with the ROM (e.g. youtube etc.)? Why is this faster?
3) Is the /cache directory the place where the dalvik cache is stored?
4) What is the difference between an Apps2SD+ ROM with stock hboot and a Data++ ROM with CM7 hboot? With the Apps2SD+ & stock hboot, the dalvik cache is also on the internal memory and the .apk's are also stored on sd-ext right?
I'm sorry for my noob questions, but I'm trying to understand the differences, for I'm quite new to rooting etc.. I've been searching a lot (perhaps not good enough), but I really couldn't find a clear answer.
Thanks in advance!
1. Speed depends on the ROM config, but you'll get more space.
2. http://www.shahz.net/android/what-is-dalvik-cache.html - Shortly, because all apps use the dalvik-cache (kind of a prefetch) - so dalvik on NAND, faster access.
3. No.
4. With the Apps2SD+ & stock hboot, the dalvik cache is on the SD CARD, but again, depends on ROM config/scripts.
A short question about the Data++ partition: having only 5 MB of cache, will games run slower on a ROM running on this setup?
Thanks in advance.
TVTV said:
A short question about the Data++ partition: having only 5 MB of cache, will games run slower on a ROM running on this setup?
Thanks in advance.
Click to expand...
Click to collapse
It could be. But I never heard/read anything about it.
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????
hello everyone. I have oxygen ROM with a2sd built in on my Desire.
my free internal storage is about 30mb and ext3 sd partition has about 800mb out of 1gb left. when I try to download some game which takes up to 40mb, google play says there is not enough free space. what should I do to download the app?
Are you sure the a2sd function is enabled in the settings menu? You can check this at:
settings-->apps-->development--> check if SD-EXT is enabled, and prefered install location is set to sd-ext under settings-->menu
Sent from my HTC Desire using xda app-developers app
the above reply is relevant only if you have mildwild version of oxygen.
regardless, you need to be s-off and flash different hboot to maximise space
- oxygenR2 hboot with original oxygen 2.3.2
- cm7r2 hboot with mildwild oxygen
currently, your a2sd script probably only moves apps to sd-ext, you still have app data and dalvik cache on internal? you can always check which bits of memory are stored where using an app like diskusage
change hboot first, then if you still run out of space, search for a script or zip that can also move dalvik cache to sd-ext.
TheRamon said:
Are you sure the a2sd function is enabled in the settings menu? You can check this at:
settings-->apps-->development--> check if SD-EXT is enabled, and prefered install location is set to sd-ext under settings-->menu
Click to expand...
Click to collapse
hey, thanks for reply. there isn't anything like sd-ext in development. and I can't find the second one too. maybe because of different ROMs?
s12[dot]postimage[dot]org/ev2a8n9i3/Screen_Shot.png
edit: does flashing new hboot wipe any data? is backup needed?
and I'm already s-off. I was pretty sure it was required to flash oxygen
Sorry I was a bit tired so I just take te settings as mine mildwild oxygen has to.
Assuming the a2sd script is working, you could install S2E to simply move the app data, dalvik cache and stuff to your sd card to increase the internal space
Sent from my HTC Desire using xda app-developers app
TheRamon said:
Sorry I was a bit tired so I just take te settings as mine mildwild oxygen has to.
Assuming the a2sd script is working, you could install S2E to simply move the app data, dalvik cache and stuff to your sd card to increase the internal space
Sent from my HTC Desire using xda app-developers app
Click to expand...
Click to collapse
if the a2sd script is working, you don't need to install anything else...
"S2E works only with CyanogenMod7, CyanogenMod9 and CyanogenMod10!", so no, do not use S2E with this ROM, there is no need anyway.
mightykiss said:
hey, thanks for reply. there isn't anything like sd-ext in development. and I can't find the second one too. maybe because of different ROMs?
s12[dot]postimage[dot]org/ev2a8n9i3/Screen_Shot.png
edit: does flashing new hboot wipe any data? is backup needed?
and I'm already s-off. I was pretty sure it was required to flash oxygen
Click to expand...
Click to collapse
which means you are probably on normal oxygen rom
you did not need s-off to flash oxygen. it only unlocks the nand partition so you can modify things on /system while the phone is running. more importantly s-off allows you to change hboots.
basically you are still on stock hboot with 250MB system. if oxygen rom system is say only 95MB, so you waste 155MB . oxygenR2 hboot has 100MB system, so you would waste only 5MB, and you gain an extra 250-100 = 150MB more internal memory :laugh:
flashing hboot does not wipe any data:
- nandroid backup!
- flash different hboot from alpharev.nl (it should fit into oxygenR2, but check your system size using another app like quick system info pro. if it is less than 100MB it will work). search for a guide on this, i recommend to use fastboot command lines. EDIT: further reading here
- boot into recovery
- full wipe and nandroid restore
eddiehk6 said:
if the a2sd script is working, you don't need to install anything else...
"S2E works only with CyanogenMod7, CyanogenMod9 and CyanogenMod10!", so no, do not use S2E with this ROM, there is no need anyway.
Click to expand...
Click to collapse
Wow... seriously? That means that I've installed S2E useless on my Mildwild Oxygen. I'm ashamed ALOT.
Sorry for all
ok, so basically I don't see the point of installing new hboot to gain extra 150mb of internal storage, because since yesterday another 15mb has just disappeared so these 150mb wouldnt mean anything. I think that apps just install on internal storage like there wasnt any a2sd. check out this screenshot: s8.postimage[DOT]org/9chhb1cvn/Screen_Shot.png
mightykiss said:
ok, so basically I don't see the point of installing new hboot to gain extra 150mb of internal storage, because since yesterday another 15mb has just disappeared so these 150mb wouldnt mean anything. I think that apps just install on internal storage like there wasnt any a2sd. check out this screenshot: s8.postimage[DOT]org/9chhb1cvn/Screen_Shot.png
Click to expand...
Click to collapse
it will definitely be worth it to flash a different hboot. you have 136MB free on system which is completely wasted...
you internal is being filled with app caches, app data and dalvik cache. you can use a cache cleaner to clean some things up.
i think your a2sd script is working because your sd-ext is being used. please check using 'diskusage'
flash oxygenR2 hboot first, see how you get on.
if you still run out of space, you can move dalvik cache to sd-ext as well using 'terminal emulator':
Type "su" and press enter
Type "a2sd cachesd" and press enter.
Click to expand...
Click to collapse
hey. sorry for not replying for so long, but I am really busy this month.
When I open my HBOOT it says s-off and revolutionary, so I think it's not about HBOOT. What do you think?
so, can you still help me?
mightykiss said:
hey. sorry for not replying for so long, but I am really busy this month.
When I open my HBOOT it says s-off and revolutionary, so I think it's not about HBOOT. What do you think?
Click to expand...
Click to collapse
i've already said what you should do , have you even read the guide that i linked?
it is everything to do with hboot...
you are still on stock hboot, you need to change hboot first to maximise space.
then if you still run out of space, move dalvik to sd-ext...
Yeah, I have read it, but why do you think I'm on stock HBOOT if it says revolutionary? Isn't it the version of HBOOT?
I has a similar issue with my Oxygen ROM even if I had Oxygen r2 HBOOT. Finally I solved the "space" issue by replacing default a2sd with amarullz 1.0RC1 script. I worked much better for me on Oxygen.
mightykiss said:
Yeah, I have read it, but why do you think I'm on stock HBOOT if it says revolutionary? Isn't it the version of HBOOT?
Click to expand...
Click to collapse
revolutionary means you are s-off, but still on stock hboot. you are definitely still on stock hboot if you haven't actually changed it
(you can check using various apps, like quick system info pro. if system size is 250MB you are on stock hboot)
up to you whether you want to change hboot and solve most of your problems...
hello again. sorry for this break but my phone was on a warranty repair. I finally got a new Desire and today rooted it. I flashed oxygenr2 HBOOT and Oxygen ROM + dalvik-cache2sd to avoid the problem of this topic but even now I still get my memory smaller and smaller! right now I have 325/350 mb free on phone memory and 950/1024 on sd (a2sd). not all applications installed yet so I might run out of space again. what do you think, what might still occupy my memory? how can I check if dalvik2sd works?
edit: okay, it's better than I thought cause the space doesn't descend as quickly as before (every 200mb on SD = 30mb of system). I think it should be enough for my needs so yeah, thanks for help and you can close the thread.
Sorry, but I have one more question. My free system space dropped in 2 days from 4mb to 3,5mb. will it stop or continue until it reaches 0? What does fill the memory except Oxygen ROM? What happens if I run out of space?
i have installed m2sd http://forum.xda-developers.com/showthread.php?t=1342387 via aroma installer and enabled apps, dalvik and cmdalvik. Installed fine...but when i go to settings-->storage--> i still have 148mb internal storage... any idea?
so this assumes you have an ext partition on your sd card, hopefully created with gparted or 4ext recovery (NOT minitool or clockworkmod recovery)
depending on your method of moving apps to sd-ext, a lot of the time it won't show your total internal memory as "internal + sd-ext", your apps should still be moved to sd-ext, you shouldn't need to 'move to SD', keeping it on internal tricks the apps to sd-ext. check using an app like 'diskusage'
regardless, you are still on stock hboot so are wasting space. Currently your rom system size is ~140MB out of 250MB stock hboot system size, wasting 110MB, and only 148MB data (internal memory).
if you change to cm7r2 hboot (requires s-off), it has 145MB system, so you waste only 5MB, and get 287MB data. this larger data partition is usually enough for app data and dalvik cache, so no need to move dalvik to sd-ext.
have a look here or google, search for guides on s-off if you're not already (use revolutionary), and how to change hboot
yup already have ext partition.. was using a2sd and int2sd on my previous sense rom... ok will try to install some apps and see if i still get insufficient storage warning...
i switched from cmr2 hboot to stock hboot as from time to time i flash an ICS/JB rom to see their progress.
thx for the explanation
yup already have ext partition.. was using a2sd and int2sd on my previous sense rom... ok will try to install some apps and see if i still get insufficient storage warning...
i switched from cmr2 hboot to stock hboot as from time to time i flash an ICS/JB rom to see their progress.
thx for the explanation
yeahman45 said:
yup already have ext partition.. was using a2sd and int2sd on my previous sense rom... ok will try to install some apps and see if i still get insufficient storage warning...
i switched from cmr2 hboot to stock hboot as from time to time i flash an ICS/JB rom to see their progress.
thx for the explanation
Click to expand...
Click to collapse
You should try using this script:
http://forum.xda-developers.com/showthread.php?t=1677709
I've used to for few weeks on the same Mild Wild Rom, it worked like a charm, btw I have the stock HBOOT installed, maybe it will fix your problem