I have LEO T8585, and when i flash Android 4.0.3. NAND (http://forum.xda-developers.com/showthread.php?t=1354267) i have only 100MB for apps. I tried this HD2 Android NAND toolkit to make partition bigger but no luck.
No matter what size i choose i'll get same size for downloaded apps - 100MB.
Im not total noob flashing NAND ROM-s , but do i miss something?
Or is it possible to make this partition bigger?
Thanks
First, the space shown as available doesn't include the system, boot or cache partition size, only the data partition size, and since during flashing, the data partition size is set to be whatever is left over after the rom is flashed, the only way to increase data size is by reducing the system partition size, , but then of course the rom wouldn't fit (because you flash the system partition to be only fractionally larger than the size of the system folder contents, if you flashed a larger system partition, the extra space would be wasted, unused by anything, example put a rom requiring 150mg onto a 250 Meg layout and you lose 100mb)
Secondly, if you set up an ext partition on the SD card, the rom will consider that internal memory BUT (on most roms) wont show it on the available internal storage calculation, but it WILL use it as internal.
third, the 4.x roms are still beta, and vary as to sizes required, whether they have ap2sd+ built in or whether you need to manually install and configure it. If you are looking for a rom you can keep as a daily for a while, wait until 4.x is a few more betas along.
Thanks!
Thats what i thougt. I made minimal part. 190MB and got 100 extra. My ext. on SD is 1024. For now its ok. And this 4.0 beta 10 it is very nice ROM, looks stable and smooth on HD2.
so I got a question. I see that the nexus roms need a 150 or 200 MB partition, and the sense roms take a 400 partition. so could I just set a 400 partition and not worry about changing when I want to flash a new rom
Wdustin1 said:
so I got a question. I see that the nexus roms need a 150 or 200 MB partition, and the sense roms take a 400 partition. so could I just set a 400 partition and not worry about changing when I want to flash a new rom
Click to expand...
Click to collapse
No partitions must be changed in order for the system to function properly. You can however switch bootloaders to clk 1.5 and change partition sizes without ever connecting to a computer.
Sent from my HD2 using xda premium
To clarify yes you could flash a 150 Meg rom to a 400meg layout, but android wouldn't use the extra 250 Meg for anything, since it isn't part of the data partition, so wouldn't count as internal storage and so wouldnt be used for data or apps., it would be wasted.
Wdustin1 said:
so I got a question. I see that the nexus roms need a 150 or 200 MB partition, and the sense roms take a 400 partition. so could I just set a 400 partition and not worry about changing when I want to flash a new rom
Click to expand...
Click to collapse
As the other two said I would advise not doing so as not only is it a waste of space but it will also prevent you from running some apps (and widgets) as they need to be installed on internal storage to function and you won't be able to have them due to insufficient storage space
Hi, I am using MIUI with Android version 2.3.7. Everything is allright, but I only have 217 mb of internal memory in total. The MIUI ROM and other apss take up about 180 mb and although I have moved some apps to sd I now only have 40 mb available. It should have 512 mb internal memory. Why can't I see and use all of it? Is it possible that I didn't delete windows mobile or one of the other android roms I have used so far, though I am sure I have tried "clean install" a few times?
Dalvik cache & app data take up a lot of space too, you could move these to th SD ext partition to free up more internal memory. You will need a2sd installed I think to enable this.
Peace
Sent from my HD2
the 'available internal memory' figure only counts the data partition size.
so (for example) if your rom requires a 200 meg system partition, you would show..
512 minus 200 minus whatever cache size you flashed minus the boot and recovery partitions (lets guess 50 meg) so your available internal memory on a completely fresh install, no data or apps, would still only show a max of 262meg available.
Also, if you flash a system partition bigger than required, you dont get the extra space to use. So flash a 180meg rom onto a 250 meg system partition, and you lose 70meg, the system wont use it for anything.
samsamuel said:
the 'available internal memory' figure only counts the data partition size.
so (for example) if your rom requires a 200 meg system partition, you would show..
512 minus 200 minus whatever cache size you flashed minus the boot and recovery partitions (lets guess 50 meg) so your available internal memory on a completely fresh install, no data or apps, would still only show a max of 262meg available.
Also, if you flash a system partition bigger than required, you dont get the extra space to use. So flash a 180meg rom onto a 250 meg system partition, and you lose 70meg, the system wont use it for anything.
Click to expand...
Click to collapse
Thank you so much. My ROM itself is about 100 mb. How much data partition size should I actually spare for such a rom? Also could you please direct me to the post that tells me how to arrange the data partition size and do the rest of flashing my rom again? I would really like to have more available internal memory. Also I would be happy if you told me what ext 3 or ext 4, whatever it is called, is and if it has anything to do with internal memory.
If the rom is 100mb then you need a partion of at most 110 so if your using clk or magdlr..after you have wiped nand...partition it to 110 if possible or use 105 even cos you don't wanna be giving up wanted space..
Hi,
Is that possible to set cache size to 45 mb with cLK?
Yes, it's possible.
Upgrade to 1.5, and you can do it by holding the back button then going to the settings.
Marvlesz said:
Yes, it's possible.
Upgrade to 1.5, and you can do it by holding the back button then going to the settings.
Click to expand...
Click to collapse
Hi there!
I've got a question regarden de ideal partition size. I use an HD2 with 0.5GB internal memory, with the HD2 Toolkit i partitiond the MAGLDR partition to 300MB, is that okay? What size should the cache be?:cyclops:
What size should the cLK partition be with an ROM installed of 140MB?
Thank you very much!:laugh:
Greetings
Maxxdiss
maxxdiss said:
Hi there!
I've got a question regarden de ideal partition size. I use an HD2 with 0.5GB internal memory, with the HD2 Toolkit i partitiond the MAGLDR partition to 300MB, is that okay? What size should the cache be?:cyclops:
What size should the cLK partition be with an ROM installed of 140MB?
Thank you very much!:laugh:
Greetings
Maxxdiss
Click to expand...
Click to collapse
It is always better to use the least size possible, as the remaining storage is going to be your internal storage for apps and so.
I think that 300MB is too much, no ROM currently uses such a big partition. (Taking into account the fact that you have a european HD2 and always using A2SD).
There is no such thing as "ideal partition size".
The best partition sizes (system, cache, boot ... etc) are the one recommended by the ROM developer himself, he built it, and he knows on a how big partition it will fit.
I have noticed that I mean read that the advice for the settings on partition sometimes can be set lower than the advice from the developper.
There are people here they test it out it is possible but I follow the directions always to begin and it works,
Titanium Backup
I know it may be a bit tedious, but what I can recommend is to experiment with it.
If you use European HD2 with A2SD then it does not really take much time since only the ROM takes place there.
You can start with a generous amount of system partition (say 300 MB) and start Titanium Backup (there may be an easier way, but TB is usually included in every ROM). In the lower part of the start screen there is an information about the free space in the "System ROM" partition (say it is 100 MB). If you use A2SD, then you can repartition your NAND using a 300-100+5 (for safety) = 205 MB.
Of course, if you have bad NAND blocks then you need to play a bit more around.
Here's my contribution,
A Friend has a TP that I 'keep upto date' for him, He wanted to get to 4.3, so I've done that, however resizing partitions in HP world just seems a pain. So here's some flashable ZIP's to do the hard lifting for you.
4 versions I'm uploading (shout if you want a different sizing).
First add's 8gb to the data size (ontop of what you have already, just look in the storage system setting option for that info) the second adds 12gb, then 16gb and finally 24gb.
UPDATE - As requested I've uploaded four new ZIP's, these set the System and the Data sizes. The System get's partitioned to the 'standard for 4.3' 512mb, the Data will get set to the relevant size marked in the ZIP.
Just pick the one that matches what you want (obviously don't try the 16 / 24 on the 16gb device! and make sure you have enough 'clean' space before you start)
What I recommend doing is moving everything you can off the old 'SDCard' partition, using Recovery in the tether mode (int the storage menu), once you have removed as much as you can (remember the 'hidden' .???? folders and don't go deleting anything that's WebOs based!)
Then just flash the ZIP you think meets your requirements.
UPDATE - Uploaded the revert scripts, I've not tested them but they should be fine.
Hope that helps.
Two way trip
Edit: To revert these changes users can do a full uninstall using the ACMEUinstaller2. This will remove all partition changes and files added when installing Android:
How to Uninstall Android or CyanogenMod on the HP TouchPad (All versions)
In addition Gradular The Ape have created flashable zips that can reverse the partition changes the previous Android state . Find these in the above post and in Gradular's second post in his thread here: How to guide for changing your system, data, and cache partition sizes to whatever you want.
RolandDeschain79 said:
This is great thank you! A few people have run into problems when moving around data with the tailor, this should totally get around that:good:
I've got to ask, would it be possible to create a reverse of these files? The problem with this setup is that it's a one way trip. If users don't like, or have problems, they'd have to go through the pain of using tailor to rearrange their space again. Being able to add and remove the space with a zip would be a lot more convenient and give users a round trip pass for changing the partition sizes.
Cheers:highfive:
Click to expand...
Click to collapse
Shouldn't be an issue, I've obviously not got a TP to play with here, so can't test, and I don't like to put stuff out there that I've not at least done a once over of.
I'll have a look at it tomorrow when I've got access to the device and post a few ZIP's. I'll just do an 'inverse' of the four I've already done so you can undo a change.
the_ape said:
Here's my contribution,
A Friend has a TP that I 'keep upto date' for him, He wanted to get to 4.3, so I've done that, however resizing partitions in HP world just seems a pain. So here's some flashable ZIP's to do the hard lifting for you.
4 versions I'm uploading (shout if you want a different sizing).
First add's 8gb to the data size (ontop of what you have already, just look in the storage system setting option for that info) the second adds 12gb, then 16gb and finally 24gb.
Just pick the one that matches what you want (obviously don't try the 16 / 24 on the 16gb device! and make sure you have enough 'clean' space before you start)
What I recommend doing is moving everything you can off the old 'SDCard' partition, using Recovery in the tether mode (int the storage menu), once you have removed as much as you can (remember the 'hidden' .???? folders and don't go deleting anything that's WebOs based!)
Then just flash the ZIP you think meets your requirements.
Hope that helps.
Click to expand...
Click to collapse
the_ape said:
Shouldn't be an issue, I've obviously not got a TP to play with here, so can't test, and I don't like to put stuff out there that I've not at least done a once over of.
I'll have a look at it tomorrow when I've got access to the device and post a few ZIP's. I'll just do an 'inverse' of the four I've already done so you can undo a change.
Click to expand...
Click to collapse
Great... Guess it would reverse to the ACMEInstaller3 default partitions... If u'r flash resizes the (system) to 512 MiB... I would leave that one alone instead of making it go back to 400 MiB...
What is the breakdown for a 32GB TP using the data_plus_24576mb-signed... Is this about right ???
USB (media) - Depends what size TouchPad u have... (Decreases 112 MiB to be added to the Android (system) partition & Decreases about 23076 to be added to the 1.5 GiB already in the (data) partition)
Android (system) - 512 MiB (Increase of 112 MiB from ACMEInstaller3 400 MiB size OR do u leave it at the 400 MiB size ??? OR does it assume we used the update-cm-tenderloin-system_resize_512-0.4 already ???)
Android (cache) - 200 MiB (Stays at ACMEInstaller3 size)
Android (data) - 24576 MiB
Plan to so some testing how ACMEInstaller3 would handle an update-data_plus_24576mb-signed thru the CMInstall when reconfiguring or coming from a stock TP (before Android & any Recovery is install on the TP)... Any thoughts on this ??? Doesn't work from ACMEInstaller3... Although I did see it run... It didn't change the size of the default partitions that ACMEInstaller3 creates...
Update: Was able to play with the 24576 file... This was the break down of the partitions now..
USB (media) - 1.539 GiB
Android (system) - 400 MiB
Android (cache) - 200 MiB
Android (data) - 25.5 GiB
Unused Space - 16 MiB
So we will need to increase the (system) partition separate using the update-cm-tenderloin-system_resize_512-0.4 file if u'r still @ 400 MiB...
Y314K said:
Great... Guess it would reverse to the ACMEInstaller3 default partitions... If u'r flash resizes the (system) to 512 MiB... I would leave that one alone instead of making it go back to 400 MiB...
What is the breakdown for a 32GB TP using the data_plus_24576mb-signed... Is this about right ???
USB (media) - Depends what size TouchPad u have... (Decreases 112 MiB to be added to the Android (system) partition & Decreases about 23076 to be added to the 1.5 GiB already in the (data) partition)
Android (system) - 512 MiB (Increase of 112 MiB from ACMEInstaller3 400 MiB size OR do u leave it at the 400 MiB size ??? OR does it assume we used the update-cm-tenderloin-system_resize_512-0.4 already ???)
Android (cache) - 200 MiB (Stays at ACMEInstaller3 size)
Android (data) - 24576 MiB
Plan to so some testing how ACMEInstaller3 would handle an update-data_plus_24576mb-signed thru the CMInstall when reconfiguring or coming from a stock TP (before Android & any Recovery is install on the TP)... Any thoughts on this ??? Doesn't work from ACMEInstaller3... Although I did see it run... It didn't change the size of the default partitions that ACMEInstaller3 creates...
Update: Was able to play with the 24576 file... This was the break down of the partitions now..
USB (media) - 1.539 GiB
Android (system) - 400 MiB
Android (cache) - 200 MiB
Android (data) - 25.5 GiB
Unused Space - 16 MiB
So we will need to increase the (system) partition separate using the update-cm-tenderloin-system_resize_512-0.4 file if u'r still @ 400 MiB...
Click to expand...
Click to collapse
I've only tested it using cwm 6, and no, my zips dont touch the system size. Forgive my ignorance, but what is ACMEInstaller?
the_ape said:
I've only tested it using cwm 6, and no, my zips dont touch the system size. Forgive my ignorance, but what is ACMEInstaller?
Click to expand...
Click to collapse
Using CWM6_tenderloin-20121215 here...
We've all used ACMEInstaller @ the initial setup of Android... It creates the Android partitions & it installs moboot, recovery & rom & gapps... It was the double penguin screen that installed them.. Most of u have not used it since then... You just use the recovery to change things... I've been reconfiguring my TP lately so I've been using it a few times.... More of the exception & not the norm...
U'r flash files only increase size right... It doesn't format anything... Can u do a version of the 24576 file that also changes the (system) partition to 512 MiB... I can test it if u like.. Thanks.. :good:
Y314K said:
Using CWM6_tenderloin-20121215 here...
We've all used ACMEInstaller @ the initial setup of Android... It creates the Android partitions & it installs moboot, recovery & rom & gapps... It was the double penguin screen that installed them.. Most of u have not used it since then... You just use the recovery to change things... I've been reconfiguring my TP lately so I've been using it a few times.... More of the exception & not the norm...
U'r flash files only increase size right... It doesn't format anything... Can u do a version of the 24576 file that also changes the (system) partition to 512 MiB... I can test it if u like.. Thanks.. :good:
Click to expand...
Click to collapse
I'll put some that do system together in the morning, I didn't bother as it was already done that way on my friends. And no, it doesn't delete anything, just shunts partitions around.
Oh and yes I do remember ACME now, back in he early days was all done via scripts and terminal, so never played with it as such, think used it once for cm9. But doubt my scripts will run under that as they make use of a lot more than just pure recovery, hats why I recommend at least cwm6
the_ape said:
I'll put some that do system together in the morning, I didn't bother as it was already done that way on my friends. And no, it doesn't delete anything, just shunts partitions around.
Click to expand...
Click to collapse
Great... Thanks.. Should help for when some CM9 or CM10 folks upgrade to the 4.3 options... Or for those still with just 400 MiB (system)... I myself feel comfortable with Tailor... Which lets u squeeze out every bit of space out of our TP's...
Y314K said:
Great... Thanks.. Should help for when some CM9 or CM10 folks upgrade to the 4.3 options... Or for those still with just 400 MiB (system)... I myself feel comfortable with Tailor... Which lets u squeeze out every bit of space out of our TP's...
Click to expand...
Click to collapse
UPDATE - As requested I've uploaded four new ZIP's, these set the System and the Data sizes. The System get's partitioned to the 'standard for 4.3' 512mb, the Data will get set to the relevant size marked in the ZIP.
See the OP
the_ape said:
UPDATE - As requested I've uploaded four new ZIP's, these set the System and the Data sizes. The System get's partitioned to the 'standard for 4.3' 512mb, the Data will get set to the relevant size marked in the ZIP.
See the OP
Click to expand...
Click to collapse
Thanks... Gonna try the two largest one's right now... I am guessing if we ever need a special size... We can just manually change the data_plus_24576mb-signed/update/update_script.sh for the data & data_plus_24576mb-signed/update/system_script.sh for the system...
Code:
CHANGE_SIZE=24576
EXTPART="cm-data"
Code:
CHANGE_SIZE=512
EXTPART="cm-system"
Looking good!
the_ape said:
UPDATE - As requested I've uploaded four new ZIP's, these set the System and the Data sizes. The System get's partitioned to the 'standard for 4.3' 512mb, the Data will get set to the relevant size marked in the ZIP.
See the OP
Click to expand...
Click to collapse
Thank you for these very helpful packages, great work! This will help a lot of people change their partitions easily. I will test them out once you also post the reverse files so I can try the round trip experience cheers:good:
the_ape said:
UPDATE - As requested I've uploaded four new ZIP's, these set the System and the Data sizes. The System get's partitioned to the 'standard for 4.3' 512mb, the Data will get set to the relevant size marked in the ZIP.
See the OP
Click to expand...
Click to collapse
Think I found something... Or maybe not...
I had already used the data_plus_24576mb-signed yesterday...
I tried to use the sys_512mb_data_plus_24576mb-signed patch just to resize the (system) partition... I thought it would recognize that the (data) partition was already 24576 MiB or that the (media) partition didn't have 24576 to give again...
Got the following:
DO NOT DO ANYTHING ELSE!
REBOOT NOW!!!
Resizing the Data Partition ...
=== Reallocating 24576MB from media to cm-data
Preparing tools...
Checking media...
media:1464=>23112 cm-data:26112=>50688
media_fs tot=1575 sz=628 free=947
cannot resize media
>>FAILED<<
Lets tidy up ...
All Done ...
Click the thanks button
if you found this useful
The_Ape
Install from sdcard complete.
Click to expand...
Click to collapse
Guess the FAIL part of it is the safety check...
Went back to WebOS... And Tailor is telling me my new partition break down is as follow...
USB (media) - 1.539 GiB => 1.43 GiB
Android (system) - 400 MiB => 512 MiB
Android (cache) - 200 MiB => 200 MiB
Android (data) - 25.5 GiB => 25.5 GiB (This includes the 24576MB + 1.5GiB that ACMEInstaller3 created the (data) partition with)
Unused Space - 16 MiB => 16 MiB
So everything worked fine... Wonder if the FAIL message can be specific enough when it's due to not having enough space in (media) to move over or if it's due to (data) already being the requested size... The part that said cm-data:26112=>50688 made me think it was forcing the mod... Also the media:1464=>23112 looks weird to me... Like it's shifting space from (data) to (system) to send back to (data)..
Y314K said:
Thanks... Gonna try the two largest one's right now... I am guessing if we ever need a special size... We can just manually change the data_plus_24576mb-signed/update/update_script.sh for the data & data_plus_24576mb-signed/update/system_script.sh for the system...
Code:
CHANGE_SIZE=24576
EXTPART="cm-data"
Code:
CHANGE_SIZE=512
EXTPART="cm-system"
Click to expand...
Click to collapse
Yup, that's the one, you can change the other partitions that way too if you wanted too, but the sizes here should be pretty close for most people.
However if your a bit more confident with what your doing then help yourself, after all, your device, you should know best what sizes are right for you.
Y314K said:
Think I found something... Or maybe not...
I had already used the data_plus_24576mb-signed yesterday...
I tried to use the sys_512mb_data_plus_24576mb-signed patch just to resize the (system) partition... I thought it would recognize that the (data) partition was already 24576 MiB or that the (media) partition didn't have 24576 to give again...
Got the following:
Guess the FAIL part of it is the safety check...
Went back to WebOS... And Tailor is telling me my new partition break down is as follow...
USB (media) - 1.539 GiB => 1.43 GiB
Android (system) - 400 MiB => 512 MiB
Android (cache) - 200 MiB => 200 MiB
Android (data) - 25.5 GiB => 25.5 GiB (This includes the 24576MB + 1.5GiB that ACMEInstaller3 created the (data) partition with)
Unused Space - 16 MiB => 16 MiB
So everything worked fine... Wonder if the FAIL message can be specific enough when it's due to not having enough space in (media) to move over or if it's due to (data) already being the requested size... The part that said cm-data:26112=>50688 made me think it was forcing the mod... Also the media:1464=>23112 looks weird to me... Like it's shifting space from (data) to (system) to send back to (data)..
Click to expand...
Click to collapse
There is very little error checking/reporting built in, it 'shouldnt' cause any issues if your sizes are not able to be changed, but the output has not been friendlied up, after all I knocked it up so I didnt have to use WebOS, it does however have a quick look to see if it's possible to do the command it's meant to be doing before it tries (as you can see)
RolandDeschain79 said:
Thank you for these very helpful packages, great work! This will help a lot of people change their partitions easily. I will test them out once you also post the reverse files so I can try the round trip experience cheers:good:
Click to expand...
Click to collapse
Damn! I forgot all about the revert ones, could anyone let me know what the 'original standard' partition sizes are for the 32gb and the 16gb and I'll knock a zip for each together.
the_ape said:
Damn! I forgot all about the revert ones, could anyone let me know what the 'original standard' partition sizes are for the 32gb and the 16gb and I'll knock a zip for each together.
Click to expand...
Click to collapse
Neve mind about WebOS partition sizes since most won't want to have to rerun ACMEInstaller3..
My 32GB after a reconfig & without any Android part install shows...
USB (media): 27.663 MiB (Partition Size 28296 MiB)
Unused Space: 8 MiB
My 32GB after a reconfig & first Android Installation shows..
USB (media): 25.539 GiB (Partition Size: 26152 MiB)
Android (system): 400 MiB
Android (cache): 200 MiB
Android (data): 1.5 GiB
Unused Space: 16 MiB
U would want a reverse flash that would only shift the 24576 MB back from (data) to (media)... Keeping the (system) @ 512 MB seems like a must thing to do now.. RolandDeschain79 probably has a better idea of what would be best for most...
Not sure about 16GB models...
That's the info I would need. What would be best for the 16GB models?
can we resize the partition from windows ?
HashTagHell said:
That's the info I would need. What would be best for the 16GB models?
Click to expand...
Click to collapse
:good: I want to try it also
the_ape said:
As requested I've uploaded four new ZIP's, these set the System and the Data sizes. The System get's partitioned to the 'standard for 4.3' 512mb, the Data will get set to the relevant size marked in the ZIP.
Click to expand...
Click to collapse
Thansk for your work. Now, pardon my newbines on the touchpad, but here it goes.
I have my TP with CM7, very old and unstable.
1) Can I use your ZIPs to repartition before moving to CM9 or CM10?
2) Can I just boot to recovery and flash this no matter what I have today?
3) I have a 32GB TP. If I use for example, sys_512mb_data_plus_16384mb-signed.zip I would have used about half meg for system, and 16GB for data, what happens with the remaining 15.5 GB?
Thanks!