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.
Are there any roms or other easy ways to increase the size of the partition /data/data on the Droid Incredible? To this day, all I really find are ways to save space in there. That's been covered - everything from Cachemate to not using certain apps. I want to know if there are any roms out there that use space from internal or other areas and reroute them so that /data/data shows more space. Any help would be appreciated.
+1
I've run into this a lot lately. Even my Eris never had this problem.
enigmatl said:
Are there any roms or other easy ways to increase the size of the partition /data/data on the Droid Incredible? To this day, all I really find are ways to save space in there. That's been covered - everything from Cachemate to not using certain apps. I want to know if there are any roms out there that use space from internal or other areas and reroute them so that /data/data shows more space. Any help would be appreciated.
Click to expand...
Click to collapse
No roms do it currently. But its probably doable.
Sent from my ADR6300 using Tapatalk
There is an app on the market called Notenoughspace. I have never used it, but it is supposed to take stuff out of your data/data, and insert it somewhere else. I here it is tricky, so be careful if you use it. I really don't know much about it. The first couple of times I ran into this problem it drove me crazy. Have you read all of the threads for what causes this? Stay away from Facebook. If you sync contacts in Facebook it can cause this. I am a crackflasher, so I rarely run into the problem. I don't think that a Rom can fix this, but I am a newb myself. Really just wanted TP help since I saw your disgruntled post in the developers section....good luck
Thanks for the reply. But here's the thing. Please let's not go into the likes of notenoughspace and cachemate and whiping out facebook. This is what people say in EVERY thread on this from the beginning of the droid incredible.
I'm not looking for a solution that at best can let an extra app or 2 get installed on the droid incredible. I'm looking for a way to INCREASE the size of the /data/data partition by way of taking some unused space from other areas like system or cache or better yet, from that pointless internal storage (for all the SD card users).
There is a lot of extra space on these phones. Thus it is nonsensical to have a measly 150mb to use in that area.
AS this phone is for a friend (and I generally do the upgrading or fixing), I do not experience this on my photon nor do I experience it on my Iconia tab. There was a limit for /data/data on my evo but it was about twice the Droid Incredible I believe.
So this most likely has to be a partition issue. Is there really no fix for it? Since it's not a hardware limit, I'm surprised as I've seen some out of this world ROMs for the device (like Skyraider's which I hoped would make it to the Evo when I had that).
enigmatl said:
Thanks for the reply. But here's the thing. Please let's not go into the likes of notenoughspace and cachemate and whiping out facebook. This is what people say in EVERY thread on this from the beginning of the droid incredible.
I'm not looking for a solution that at best can let an extra app or 2 get installed on the droid incredible. I'm looking for a way to INCREASE the size of the /data/data partition by way of taking some unused space from other areas like system or cache or better yet, from that pointless internal storage (for all the SD card users).
There is a lot of extra space on these phones. Thus it is nonsensical to have a measly 150mb to use in that area.
AS this phone is for a friend (and I generally do the upgrading or fixing), I do not experience this on my photon nor do I experience it on my Iconia tab. There was a limit for /data/data on my evo but it was about twice the Droid Incredible I believe.
So this most likely has to be a partition issue. Is there really no fix for it? Since it's not a hardware limit, I'm surprised as I've seen some out of this world ROMs for the device (like Skyraider's which I hoped would make it to the Evo when I had that).
Click to expand...
Click to collapse
I have had the same problem, and I haven't seen any roms that come close to solving it. And there is no quick and easy solution.
The best work around I could find was to mod the stock rom and add Dark Tremor's APP2SD, and use notenoughspace.
With dtapps2sd you have to partiton the SD card so that you have a ext3 partition on it that can be mounted and apps can be ran from it. It does this for /data/app and a couple of other folders.
Notenoughspace will let you move folders in /data/data to the sd partition that dtapps2sd has mounted, and that survive through a reboot. The extra partition option is what you would use, not the NES partition.
Using this work around I have about 300 apps on my phone, and about 70mb free in /data/data.
My Android version is GB 2.3.4 (build 4.06.605.3).
enigmatl said:
Are there any roms or other easy ways to increase the size of the partition /data/data on the Droid Incredible? To this day, all I really find are ways to save space in there. That's been covered - everything from Cachemate to not using certain apps. I want to know if there are any roms out there that use space from internal or other areas and reroute them so that /data/data shows more space. Any help would be appreciated.
Click to expand...
Click to collapse
Bootmanager will install the whole rom on /sdcard or emmc storage and as an added bonus, /data and /data/data are all in one image so you have shared space. By default you have 950 MB to share for apps and app data. As an added bonus you have the ability to boot multiple roms and have them all loaded at once. It's available on the market and the devs who made it are awesome. However it costs a few dollars.
If you don't want to go that route then it's possible to create an image on the sdcard or emmc and symlink it to /data/data and you could set the size of the file. Then the ramdisk would need to be modified and maybe a couple of things done on the rom. You asked for an easy way and this is one but not easy though. Bootmanager is pretty easy though and no coding changes need to be done to the roms and it will leave your original rom intact.
I've been wondering about this as well.
I've tried a couple different approaches, and ended up sticking with one: it takes some setup overhead for every ROM I install, but it helps a lot.
I ended up deleting the datadata mount from init.inc.rc in boot.img (get ROM, unpack, edit init.inc.rc, repack, flash), and booting in recovery mode to move the data from ([email protected])/ over to (mmcblk0p1)/data (which is now just a subdir on the 768MB /data partition.)
Initial tests repartitioning mmcblk0 (houses /data, /cache, and /emmc) to make /data larger for this purpose didn't work out well: the bootloader rewrites the MBR/partition table when it finds that they don't match metrics it likes. /emmc can not really be reformatted because the bootloader updates some bits that it expects to be FAT32 on boot time as well, corrupting other filesystems.
Why on earth HTC would ship a phone in this day and age with such a crippled storage layout is beyond me.
DHowett said:
I've been wondering about this as well.
I've tried a couple different approaches, and ended up sticking with one: it takes some setup overhead for every ROM I install, but it helps a lot.
I ended up deleting the datadata mount from init.inc.rc in boot.img (get ROM, unpack, edit init.inc.rc, repack, flash), and booting in recovery mode to move the data from ([email protected])/ over to (mmcblk0p1)/data (which is now just a subdir on the 768MB /data partition.)
Initial tests repartitioning mmcblk0 (houses /data, /cache, and /emmc) to make /data larger for this purpose didn't work out well: the bootloader rewrites the MBR/partition table when it finds that they don't match metrics it likes. /emmc can not really be reformatted because the bootloader updates some bits that it expects to be FAT32 on boot time as well, corrupting other filesystems.
Why on earth HTC would ship a phone in this day and age with such a crippled storage layout is beyond me.
Click to expand...
Click to collapse
That doesn't sound too difficult (i moved CM7 from emmc img to the actual phone partitions so that should be pretty simple). The only downside is you do lose space for apps (easily solved with apps2sd). I haven't seen you around since you posted your idea for multiboot. Been busy?
Well, the emmc method would be a loopback image which would not touch the fat32 filesystem.
Or if you're doing nightlies for instance once you mod the boot.img just add it to each new nightly.
Would Conap's dual boot work the same way? I am comfortable with this, and all the coding is intimidating for this newb. Would one of you smarter members put out a small guide as to exactly how to do this. I know it is time consuming, but it would really be worth it to us low lifes. Thanks
How can you do this?
DHowett said:
I've been wondering about this as well.
I've tried a couple different approaches, and ended up sticking with one: it takes some setup overhead for every ROM I install, but it helps a lot.
I ended up deleting the datadata mount from init.inc.rc in boot.img (get ROM, unpack, edit init.inc.rc, repack, flash), and booting in recovery mode to move the data from ([email protected])/ over to (mmcblk0p1)/data (which is now just a subdir on the 768MB /data partition.)
Initial tests repartitioning mmcblk0 (houses /data, /cache, and /emmc) to make /data larger for this purpose didn't work out well: the bootloader rewrites the MBR/partition table when it finds that they don't match metrics it likes. /emmc can not really be reformatted because the bootloader updates some bits that it expects to be FAT32 on boot time as well, corrupting other filesystems.
Why on earth HTC would ship a phone in this day and age with such a crippled storage layout is beyond me.
Click to expand...
Click to collapse
Wow, that sounds like a great idea. Like the above poster, can I also ask if someone who knows how would write up some instructions on how to to this? It certainly would be appreciated by many! With Gingerbread, there's not much Incredible users can do about the tiny /data size. Thanks!
I'm encountering this issue with 384MB of phone storage free and nearly 4GB of SD free. When I checked, I only had 14.5MB free in /data/data. 150MB for this is ridiculous! I would appreciate any fix, preferably one I can set and forget (don't want to have to constantly move or create symlinks for ever new app I install).
possible fix
You should check out jermaine151's Stock+ version 2.1. http://forum.xda-developers.com/show....php?t=1260994. I can't personally vouch for it as he just released it and it's a little late to start reinstalling everything, but it looks promising.
I've just recently seen in some other threads information about this Ext4 update but after searching haven't really been able to get a handle on what exactly it does and the proper process for doing it. I would love to be rid of the Low Memory messages and may even decide to root my wives as well if it will fix it for her as well. Does anyone have a link to a step by step that covers what needs to be done? I am currently running the Albinoman's Jelly Bean ROM and loving it but would really like to kick this low memory message for good.
Thanks for any insight
devo4040 said:
I've just recently seen in some other threads information about this Ext4 update but after searching haven't really been able to get a handle on what exactly it does and the proper process for doing it. I would love to be rid of the Low Memory messages and may even decide to root my wives as well if it will fix it for her as well. Does anyone have a link to a step by step that covers what needs to be done? I am currently running the Albinoman's Jelly Bean ROM and loving it but would really like to kick this low memory message for good.
Thanks for any insight
Click to expand...
Click to collapse
Im not sure if the ext4 mod will work on JB, im pretty sure its only for GB. If you go to a GB rom, its as easy as flashing the mod thru recovery.
How it works is it flashes the gingertiny kernel with a modified ramdisk. Normally the phone has a larger /data partition, and a /datadata (/data/data) partition that is way undersized. The mod takes the undersized /datadata partition and instead mounts it to the larger /data partition, esentialy giving you /data/data just as you had before. So it makes /datadata a folder on the larger /data partition, instead of being on its own smaller seperate partition.
Hope that wasnt to confusing.
There's also an ext4 mod with no kernel, got it from invisiblek's stash. I've been using it on his nightly ICS builds and it seems to work very well.
Try Link2sd and see if that helps. I use both and have never seen a warning about low space.
...sorry...I was on the phone...
omniatic said:
There's also an ext4 mod with no kernel, got it from invisiblek's stash. I've been using it on his nightly ICS builds and it seems to work very well.
Try Link2sd and see if that helps. I use both and have never seen a warning about low space.
...sorry...I was on the phone...
Click to expand...
Click to collapse
The common misconception of my mod it seems is that it flashes the kernel all the time. No. It only does that if there is a specific HTC framework file in system and that's the only difference between mine and invisibleks. Mine should work fine on ICS as it basically does a find and replace to modify the ramdisk and leave the same kernel. If you look at the script in the mod you'll see that.
Sent from my Galaxy Nexus using Tapatalk 2
tiny4579 said:
The common misconception of my mod it seems is that it flashes the kernel all the time. No. It only does that if there is a specific HTC framework file in system and that's the only difference between mine and invisibleks. Mine should work fine on ICS as it basically does a find and replace to modify the ramdisk and leave the same kernel. If you look at the script in the mod you'll see that.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
So from what i'm gathering I should be ok on the Jelly Bean ROM even as it isn't going to affect the Kernel but just modify the ramdisk? I have seen a few links around is there a link to the developers site that has the most recent version to flash? Thanks for the input.
devo4040 said:
So from what i'm gathering I should be ok on the Jelly Bean ROM even as it isn't going to affect the Kernel but just modify the ramdisk? I have seen a few links around is there a link to the developers site that has the most recent version to flash? Thanks for the input.
Click to expand...
Click to collapse
I was under the impressin it always flashed the kernel, but i guess i was wrong. So it should work.
I cant find the ext4 thread right now, but you can get the files from here. http://dinc.does-it.net/EXT4_Mods/
cmlusco said:
I was under the impressin it always flashed the kernel, but i guess i was wrong. So it should work.
I cant find the ext4 thread right now, but you can get the files from here. http://dinc.does-it.net/EXT4_Mods/
Click to expand...
Click to collapse
Thanks for the link, do I just need the Convert2Ext4_normal_data.v1.0.zip or do I need one of the dalvik .zip files as well?
devo4040 said:
Thanks for the link, do I just need the Convert2Ext4_normal_data.v1.0.zip or do I need one of the dalvik .zip files as well?
Click to expand...
Click to collapse
There are 3 different mods.
1. Ext4 normal data - Converts data and cache to ext4. Does nothing for low space problem.
2. Ext4 no data limit normal dalvik - Converts data and cache to ext4. Moves /datadata to /data, fixing low space issue.
3. Ext4 no data limit dalvik moved - Converts data and cache to ext4. Moves /datadata to /data. Moves dalvik cache from /data to the former /datadata partition.
#2 is the most popular and will solve the low space issue. You can use #3, however some people have issues moving the dalvik. You can always try dalvik moved if you want. If it causes issues flash the dalvik moved revert, and you will be left with no data limit normal dalvik.
tiny4579 said:
The common misconception of my mod it seems is that it flashes the kernel all the time. No. It only does that if there is a specific HTC framework file in system and that's the only difference between mine and invisibleks.
Click to expand...
Click to collapse
But doesn't it always flash the kernel that's bundled with the mod? And won't flashing a new kernel afterward undo the mod?
(Given, all this only matters on Sense ROMs...)
Edit: Never mind. The mod only needs to modify boot.img, while a kernel uses the boot.img file that's already there. Derp.
ardax said:
But doesn't it always flash the kernel that's bundled with the mod? And won't flashing a new kernel afterward undo the mod?
(Given, all this only matters on Sense ROMs...)
Edit: Never mind. The mod only needs to modify boot.img, while a kernel uses the boot.img file that's already there. Derp.
Click to expand...
Click to collapse
Just FYI, We (jermaine151 and I) wouldn't have had a kernel in the mod for sense if it weren't for the fact that HTC's kernel doesn't support ext4 and CM's and other AOSP kernels already supported ext4.
You're correct, the mod takes the boot.img, unpacks it, makes the change, repacks it, and flashes the boot.img. If it's sense, instead of repacking with the same kernel it repacks with the bundled kernel. On AOSP it repacks with the existing kernel.
So I finally had a free night and attempted to flash Convert2Ext4_no_data_limit_normal_dalvik.zip last night. It appeared to go just fine for me but I am still getting the low space message this morning if I add any apps. I went in with Link2SD and it still shows my /system as only having 4% free while everything else has around 50% free. I've tried moving everything to the SD card that it will let me but still no luck.
devo4040 said:
So I finally had a free night and attempted to flash Convert2Ext4_no_data_limit_normal_dalvik.zip last night. It appeared to go just fine for me but I am still getting the low space message this morning if I add any apps. I went in with Link2SD and it still shows my /system as only having 4% free while everything else has around 50% free. I've tried moving everything to the SD card that it will let me but still no luck.
Click to expand...
Click to collapse
Go to menu - settings - sd & phone storrage - and look for application data storrage category. Total space should say 748mb if the mod worked. Or use a termimal app with su permission to type " mounts ". Look for /cache and /data, they should say ext4 after both.
Which EXT4 mod should I use with Pons CM10? Are there any performance improvements?
spectre559 said:
Which EXT4 mod should I use with Pons CM10? Are there any performance improvements?
Click to expand...
Click to collapse
Which mod you use is really up to you. No data limit normal dalvik is the most used. Heres a breakdown:
Convert2Ext4_no_data_limit_normal_dalvik.v2.0.zip - Converts cache and data to ext4 from ext3 (ext4 is faster than ext3), moves datadata partition to a folder on the data partition (fixes low space issues), leaves dalvik-cache in its original position on the data partition.
Convert2Ext4_no_data_limit_dalvik_moved.v2.0.zip - Converts cache and data to ext4 from ext3 (ext4 is faster than ext3), moves datadata partition to a folder on the data partition (fixes low space issues), moves dalvik-cache from the data partition to the former datadata partition (frees up more space for data, but has been said to slow the phone down/cause issues).
Convert2Ext4_no_data_limit_dalvik_moved_revert.v2.0.zip - Converts cache and data to ext4 from ext3 (ext4 is faster than ext3), moves datadata partition to a folder on the data partition (fixes low space issues), moves dalvik-cache from the datadata partition back to its original position on the data partition after using the dalvik moved mod.
Convert2Ext4_normal_data.v2.0.zip - Converts cache and data to ext4 from ext3 (ext4 is faster than ext3), leaves datadata on its original (undersized) partition (does not fix low space issues), leaves dalvik-cache in its original location on the data partition.
No_Data_Limit_Mod.v2.0.zip - Leaves data and cache as ext3 (no conversion to the faster ext4), moves the datadata partition to a folder on the data partition (fixes low space issues), leaves dalvik-cache in its original position on the data partition.
http://dinc.does-it.net/EXT4_Mods/
All right I went for the no data limit / normal dalvik option. Flashed with TWRP 2.3.x. Everything seems to have worked but is there any way I can verify that the mod took? Sorry for the noob question.
* EDIT * Never mind. The answer is a couple posts up!
spectre559 said:
All right I went for the no data limit / normal dalvik option. Flashed with TWRP 2.3.x. Everything seems to have worked but is there any way I can verify that the mod took? Sorry for the noob question.
* EDIT * Never mind. The answer is a couple posts up!
Click to expand...
Click to collapse
Go to menu - settings - sd & phone storrage - and look for application data storrage category. Total space should say 748mb if the mod worked. Or use a termimal app with su permission to type " mounts ". Look for /cache and /data, they should say ext4 after both.
Lol i copied and posted from above.
cmlusco said:
Go to menu - settings - sd & phone storrage - and look for application data storrage category. Total space should say 748mb if the mod worked. Or use a termimal app with su permission to type " mounts ". Look for /cache and /data, they should say ext4 after both.
Lol i copied and posted from above.
Click to expand...
Click to collapse
The first part is not a good way of telling (by checking storage). It will show 748mb regardless. Not mounting /data/data will not have an impact on the size of /data which is 748mb. The best way is to do the following from terminal:
su
mount | grep /data
It should show a line with /data and ext4 and, if it has the no data limit, also a line with /data/data and ext4. If you're on an ICS/JB ROM it will show ext4 anyways. The best way to tell with the new version of the mod is to see if noauto_da_alloc shows in the results of the above commands.
tiny4579 said:
The first part is not a good way of telling (by checking storage). It will show 748mb regardless. Not mounting /data/data will not have an impact on the size of /data which is 748mb. The best way is to do the following from terminal:
su
mount | grep /data
It should show a line with /data and ext4 and, if it has the no data limit, also a line with /data/data and ext4. If you're on an ICS/JB ROM it will show ext4 anyways. The best way to tell with the new version of the mod is to see if noauto_da_alloc shows in the results of the above commands.
Click to expand...
Click to collapse
Actually on the latest ota anyways, the sd & storage menu shows both Phone Memory (/data) as 748mb, and Application Data Storage (/data/data) as 748mb with the mod, and 147mb without. But your still correct, your way is a better way to see if its working. I just cant ever seem to remember that command.
cmlusco said:
Actually on the latest ota anyways, the sd & storage menu shows both Phone Memory (/data) as 748mb, and Application Data Storage (/data/data) as 748mb with the mod, and 147mb without. But your still correct, your way is a better way to see if its working. I just cant ever seem to remember that command.
Click to expand...
Click to collapse
I added the commands to check to the OP of the mod thread under FAQs.
Oh, the ota does show it? Wow, it's been a while since I've really used sense.
yo, this really speeded my INC up right away! thanks!
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.
I have a brand new G3 (D852) with Koodo that I just got 2 days ago. I've rooted, installed TWRP and flashed a few AOSP roms. Not a fan of any manufacturer UI, even though LG's is very minimal, so AOSP it is. I noticed that my system partition has more than 1GB of free space after everything is flashed and good to go. I also noticed that the latest TWRP (2.8.7.0) has a resize partition option inside the Wipe section. What I want to know is, how can I use this to resize the system and data partitions so that 1GB+ isn't being wasted and unused. I'd really like to get that 1GB+ added to my data partition for apps.
I've tried using it. The only time it didn't spit out an error was after I wiped the system partition. It succeeded in "resizing" it after that, but it didn't change anything. The system partition remained the same size.
ToYeD said:
I have a brand new G3 (D852) with Koodo that I just got 2 days ago. I've rooted, installed TWRP and flashed a few AOSP roms. Not a fan of any manufacturer UI, even though LG's is very minimal, so AOSP it is. I noticed that my system partition has more than 1GB of free space after everything is flashed and good to go. I also noticed that the latest TWRP (2.8.7.0) has a resize partition option inside the Wipe section. What I want to know is, how can I use this to resize the system and data partitions so that 1GB+ isn't being wasted and unused. I'd really like to get that 1GB+ added to my data partition for apps.
I've tried using it. The only time it didn't spit out an error was after I wiped the system partition. It succeeded in "resizing" it after that, but it didn't change anything. The system partition remained the same size.
Click to expand...
Click to collapse
This it why the option is there:
resize2fs feature: On some devices like the Nexus 6, the factory images include a userdata image that is the proper size only for the 32GB units. If you flash the factory image to a 64GB Nexus 6, the data partition will appear as if it only has the free space of a 32GB device. Using the resize2fs option, TWRP can resize your data partition to take up the full space available. The resize2fs may also be useful to resize system partitions on devices where custom ROM system images don’t take up the full partition space. Lastly, resize2fs may be useful in some cases to reserve the proper space at the end of a data partition for a full disk encryption key, should your partition be formatted incorrectly for some reason.
jeffrey268 said:
This it why the option is there:
resize2fs feature: On some devices like the Nexus 6, the factory images include a userdata image that is the proper size only for the 32GB units. If you flash the factory image to a 64GB Nexus 6, the data partition will appear as if it only has the free space of a 32GB device. Using the resize2fs option, TWRP can resize your data partition to take up the full space available. The resize2fs may also be useful to resize system partitions on devices where custom ROM system images don’t take up the full partition space. Lastly, resize2fs may be useful in some cases to reserve the proper space at the end of a data partition for a full disk encryption key, should your partition be formatted incorrectly for some reason.
Click to expand...
Click to collapse
Thank you for the reply
If I understand you correctly, the feature's original intent is to resize /data partitions in the event the rom/system image treats a larger storage capacity device as a lower capacity one, ie. 64GB device is treated like 32GB so /data will only reflect 32GB minus (system image install size), wasting 32GB and leaving it inaccessible to the user.
However, it also seemed like you were saying I also could use it to resize my /system partition to a smaller size so CM12.1 (with it's ~900MB install size after Full TK-Gapps) will only leave ~50MB to ~100MB on /system instead of ~1.5GB. However, the question remains. How do I do this and can I reallocate the ~1.5GB to the /data partition for apps and internal storage? If this can't be done then I see no point in resizing /system to begin with as it will still be inaccessible to me as the user.
ToYeD said:
Thank you for the reply
If I understand you correctly, the feature's original intent is to resize /data partitions in the event the rom/system image treats a larger storage capacity device as a lower capacity one, ie. 64GB device is treated like 32GB so /data will only reflect 32GB minus (system image install size), wasting 32GB and leaving it inaccessible to the user.
However, it also seemed like you were saying I also could use it to resize my /system partition to a smaller size so CM12.1 (with it's ~900MB install size after Full TK-Gapps) will only leave ~50MB to ~100MB on /system instead of ~1.5GB. However, the question remains. How do I do this and can I reallocate the ~1.5GB to the /data partition for apps and internal storage? If this can't be done then I see no point in resizing /system to begin with as it will still be inaccessible to me as the user.
Click to expand...
Click to collapse
I read a few things online and it seems you need aan unlocked bootlader, the G3 bootloader is not unlockable, so you are probily out of luck maby you can ask in the Q&A thread of the rom you are using.