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.
Forgive me if this has been asked/answered before. I found similar threads related to the /system partition, but nothing related to the /data partition.
I'm running a custom ROM with A2SD (sd:ext)-- specifically, an ample 1GB partition on /system/sd. As you're probably aware, /data/app symlinks to /system/sd/app. Currently, I have 52MB free on /data, and 355MB free on /system/sd.
Here is my situation:
I have a large app (74MB) installed in .android_secure. Since I don't want apps in .android_secure (for my own personal irrelevant reasons), I would typically go into Settings->Applications (or TitaniumBackup) and actually move the app to the phone (which puts it into /data/app, hence /system/sd/app). The problem is that the system's move program that moves the app calculates the free space on the /data partition (52MB) instead of the free space in the finer destination, which is /system/sd/app (355MB), and ultimately rejects the move because it doesn't think there is enough free space (when there really is).
I was thinking of resizing the /data partition to "trick" the move program. But the only thing I can really steal space from is the /system partition, which isn't such a great idea. Seeing as my dalvik cache and app data takes up 350MB (or about 85%) of the /data partition, I'm further concerned I might eat up my /data partition, even without apps installed directly on it!!!
How have others dealt with this problem? I've seen some stuff about moving the dalvik cache to the sd card, though there are much better arguments AGAINST doing that.
Any help is much appreciated!
Related commands (FYI):
df -k - Shows the storage allocation and usage by partition
du -hs <path> - Calculates the free space (recursively) for given path. Note: it will not include any data within any symlinks.
Perhaps I don't understand the purpose of sd-ext/4ext/a2sd etc [I'm sure this is the case!]
I'm running the Aurora v3 rom - basically a sense2.1 with an ext partition. I cannot understand why I've 128mb free in /data after installing pretty much all my apps yet I'm getting insufficient storage errors; I can't install anything despite having a lot of /data free- it seems if my sd-ext if nearly full I can't use my /data?
1. The rom's files flash to /system, and a few to /data. As it's large, we partition the sd card with a 4ext part of say 342mb for overspill of the system/data files.
2. If we change the hboot (to cm7) such that the /system is smaller - overflowing into sd-ext - we get a larger /data partition for apps on the internal memory. (I've done this for for Oxygen/Redux roms and had over 340mb /data with no sd-ext.) Thus alpharev say's we'd get 287mb /data.
3. This rom installs apps to /sd-ext, and/or /data[?]; in Android's App usage I'm reporting 152mb used, 135mb free (the 287mb /data?); and 128mb free storage.
4. 4ext recovery reports 1.7mb free of 342mb for sd-ext - it's full. Which makes sense if apps install to /sd-ext, but why not fill the internal /data first? adb shell df -h gives:
Code:
Filesystem Size Used Available Use% Mounted on
/dev/block/mtdblock4 5.0M 796.0K 4.2M 16% /cache
/dev/block/mmcblk0p1 7.1G 4.5G 2.6G 63% /sdcard
/dev/block/mtdblock5 287.6M 159.3M 128.3M 55% /data
/dev/block/mmcblk0p2 331.3M 329.6M 1.7M 99% /sd-ext
/dev/block/mtdblock3 145.0M 122.8M 22.2M 85% /system
5. To me this means /data has 128mb free for apps; sd-ext is full with system files and apps - seeming to me that apps take space up on both /data and /sd-ext, duplicating space usage. Obviously I'm wrong on this but that's how I see my space disappearing lol Yet I cannot install any apps as I've insufficient storage.
6. Clearly I'm misunderstanding things after installing just 150mb apps and thinking I'd have 287mb of apps /data, not just /sd-ext: why shrink hboot's /system to make a large /data if the apps go to sd-ext?
7. I've not moved dalvik cache to sd as I thought I'd not need to given the seemingly large /data, and it's free amount. Clearly I can do so but why isn't my /data space available?
Sorry for long post and sounding dumb, I'm really trying not to be!
These Roms use sdext for both Rom and part of the apps and possibly dalvik too. Traditionally it would just be apps and maybe dalvik.
With these bigger roms, you need bigger ext to get the same. Yes when ext is full, you can't install anything. Maybe you need a bigger ext partition
Sent from my HTC Desire using XDA App
Thanks for the reply.
That's what I thought - I just cannot understand why I cannot use the free /data though; what's the point of changing to the CM7 hboot when your /data is limited to that of the sd-ext? Isn't it doubling up on storage use by apps, placing them in sd-ext and /data, and when one is full you can't utilise the other?
Sorry for sounding stupid, it just makes no sense to me.
btw I checked out your dGB, looks great. I do love miinimalist roms but also prize my Sense-720p'd camera!
No its not doubling up. The point is that /data/app and /data/dalvik-cache are symlinked to /sd-ext/app and /sd-ext/dalvik-cache.
However, /data/data where the libs, preferences and databases are, remain on /data/data
So when you install an .apk, it installs the app to /sd-ext/app, the dalvik is created on /sd-ext/dalvik-cache and the libs & db's etc will install to /data/data
If sd-ext is full, there is no where for the apk to go.
Thanks for clearing that up for me, I feel kinda stupid - I just couldn't get my head around it: why the nand wasn't being used for apk placement but I see they are split up and components spread over the combined sd-ext and /data. Thanks!
No probs. Not seen you on AF for a while?
OT
Android Forum? = xda? I've been offline a lot recently as this Indian Summer has made for some prime ultrarunning weather, but also takes a ton of time (by definition) although I've been rocking Redux/Aurora roms recently. Just been perusing the Desire forum today and there's been a ton of awesome rom progress since my last visit. I remember your help and work on Redux/thread/pm, great stuff. Still a beginner but it's very interesting learning this stuff, just also takes a lot of time for a non programmer!
Of potential note, 'found' a bug in gnu parted trying to partition out a 512mb 4ext sd-ext via 4EXTRecovery (madmaxx82 located it, I merely experienced it!) Always feels good to in a tiny way contribute
Apologies ahead of time if this has been answered before. I spent about 30 minutes Googling and trying solutions without any luck.
My situation is that I'm on MikG 3.11 and am using the built in A2SD to store all the apps on a 2GB SD-Ext partition. I have enough apps that the ~160MB internal /cache partition is pretty much filled with Dalvik Cache files in the /cache/dc subdirectory (only 3MB left on the partition).
Unfortunately, Google Play (formerly Market) seems to download app installs and updates into /cache with file names like "Download.apk" and "Download-1.apk" and then installs the apps from there. Since there is so little space, any app above 1.5MB or so fails to download and install (it seems to need the space for the download and then space to extract the download, so you can only get apps that are about 1/2 the size of the remaining partition space).
Is there any way to change where Google Play/Market downloads apps to install? I've got plenty of space on /data or the SD-Ext partition.
I found old directions to fix this issue by entering the following at terminal to create a sym link for Market to download on the SD card:
Code:
mkdir /mnt/sdcard/market-download-cache
su
cd /cache
mv download download.bak
ln -s /mnt/sdcard/market-download-cache download
ls -ahl
Unfortunately, Play/Market no longer uses a "download" sub-directory on /cache, so this won't work.
To fix the problem, I tried using "a2sd cachesd" to free up space on /cache by moving the Dalvik Cache to the SD-Ext partition, but that made for a really laggy experience (presumably because my SD card has bad random r/w access). I could also presumably just unmount the partition from /cache and make /cache a sym linke to a folder on the SD Ext card, but it doesn't seem that would perform much better.
My only thought at this point for a long term solution is to copy the current /cache contents to /system/sd/cache, mount the current partition on /cache at /mnt/cache (unmounting it from /cache first), create a sym link from /cache to /system/sd/cache, then set up a sym link from /mnt/cache/dc to /system/sd/cache/dc. All of this would have the effect of keeping the Dalvik Cache on the same internal partition where it currently resides while letting Play/Market have plenty of space in the new /cache which would actually be a directory on the SD-Ext partition. But, this seems kind of hacky and could negatively impact other things that might need /cache.
My short term solution is that every time I need to install or update apps, I just go into /cache/dc with Root Explorer and delete a bunch of the cached data to free up enough space for the app(s) and then do the update/install through Play/Market. The OS then seems to recreate the cached information the next time I run the app whose cached data I deleted (for example, I deleted the IMDB cached data and the next time I ran IMDB it took a long time to come up but then worked fine-- presumably the delay was recreating the cached data/app). The OS also seems to recreate the dalvik cached files on boot (not sure if that is a general feature or just in the MikG ROM I'm using).
In any case, I think all of the above is accurate so even if nobody has better solutions, maybe this will help others understand why they can't install/update apps even though it seems they have plenty of space.
If anybody is out there that has a good long term solution to this (like a place you can change the directory where Play/Market downloads), please let me know.
It's probably not cool to respond to your own post, but I had another idea for fixing this problem:
It looks like /data has 140MB of space left on it-- could I move the Dalvik Cache to that partition so there would be plenty of space on /cache to let Market/Play work?
As far as I can tell, /data/dalvik-cache is already a link (maybe a hard link?) to /cache/dc, so presumably I could just switch that to the Dalvik Cache was actually on /data?
Any thoughts on whether this would work and if it is a good idea or bad idea?
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!