Related
Hello,
I apologize if this has been covered... It seems that our forum is unable to search for 3 character terms, specifically "192" and "ram".
The G1 is listed as having 192 megs of memory. Yet, running "free" from my rooted RC33(JF1.41) shows:
Code:
$ su
# free
total used free shared buffers
Mem: 99040 96292 2748 0 316
Swap: 0 0 0
Total: 99040 96292 2748
#
So, where's my other 96 megs?! If -all- this extra ram is being used for 3d (god forbid) I'd gladly tweak a setting to reclaim more ram for RUNNING APPS, versus bling bling.
Anyone have any ideas here?
mystica555 said:
Hello,
I apologize if this has been covered... It seems that our forum is unable to search for 3 character terms, specifically "192" and "ram".
The G1 is listed as having 192 megs of memory. Yet, running "free" from my rooted RC33(JF1.41) shows:
Code:
$ su
# free
total used free shared buffers
Mem: 99040 96292 2748 0 316
Swap: 0 0 0
Total: 99040 96292 2748
#
So, where's my other 96 megs?! If -all- this extra ram is being used for 3d (god forbid) I'd gladly tweak a setting to reclaim more ram for RUNNING APPS, versus bling bling.
Anyone have any ideas here?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?p=3262422
mystica555 said:
Code:
$ su
# free
total used free shared buffers
Mem: 99040 96292 2748 0 316
Swap: 0 0 0
Total: 99040 96292 2748
#
Click to expand...
Click to collapse
And ofcourse I end up reading the reply to my post -after- i write this one. Edited as I'm an idiot.
It still seems to me that 192 megs is A; misleading and B; clearly NOT enough to run this OS, along with radio "firmware" (why cant the radio have its own bloody discrete chip!?)
I presume this huge gaping usage of ram is why the Sprint Touch Pro shows 288 megs of ram; its really 384 with the rest being used by the phone's radio and framebuffer. Gah.
I wonder, will new Android hardware overcome this paltry 96 meg limit?
mystica555 said:
And ofcourse I end up reading the reply to my post -after- i write this one. Edited as I'm an idiot.
It still seems to me that 192 megs is A; misleading and B; clearly NOT enough to run this OS, along with radio "firmware" (why cant the radio have its own bloody discrete chip!?)
I presume this huge gaping usage of ram is why the Sprint Touch Pro shows 288 megs of ram; its really 384 with the rest being used by the phone's radio and framebuffer. Gah.
I wonder, will new Android hardware overcome this paltry 96 meg limit?
Click to expand...
Click to collapse
indeed .. but that would be why rooting the G1 is so nice .. move files over to a linux EXT2 partition on the SD card and viola!! ultimate space
i have 1.5G dedicated to the G1 .. keeps the phone free and clear
Flash is not SDRAM
LucidREM said:
indeed .. but that would be why rooting the G1 is so nice .. move files over to a linux EXT2 partition on the SD card and viola!! ultimate space
i have 1.5G dedicated to the G1 .. keeps the phone free and clear
Click to expand...
Click to collapse
I could care less about the total amount of installed apps; I've got plenty of free yaffs2 flash for what I end up running...I simply don't want my apps to get oom-killed.
I simply wish to run, ALL CONCURRENTLY, (cpu speed be damned!)
Connectbot
HelloAIM!
PicPush
StreamFurious or Last.fm
Gmail
AND the browser
without one or more (or the home screen) forcibly being killed due to out of memory errors.
Load Browser, 2 or 3 of those always end up dying.
A normal commute for me on the bus: I'm chatting on AIM. I've got a irssi session open on my VPS in Connectbot. Last.fm playing some futurepop. I tap the notification bar to read the new email I have, which contains an HTML link. Click the link...Boom, music stops playing. Close browser, homescreen reloads slowly. Go back to connectbot, well, im disconnected.
RAM = Godly.
Let's try this...
Code:
# cd /sdcard
# dd if=/dev/zero of=swap.fil bs=1M count=128
128+0 records in
128+0 records out
# mkswap ./swap.fil
Setting up swapspace version 1, size = 134213632 bytes
# swapon ./swap.fil
# free
total used free shared buffers
Mem: 99040 97112 1928 0 556
Swap: 131064 0 131064
Total: 230104 97112 132992
#
mystica555 said:
Code:
# cd /sdcard
# dd if=/dev/zero of=swap.fil bs=1M count=128
128+0 records in
128+0 records out
# mkswap ./swap.fil
Setting up swapspace version 1, size = 134213632 bytes
# swapon ./swap.fil
# free
total used free shared buffers
Mem: 99040 97112 1928 0 556
Swap: 131064 0 131064
Total: 230104 97112 132992
#
Click to expand...
Click to collapse
What does that do? Does it create a swap file on the sd card?
andonnguyen said:
What does that do? Does it create a swap file on the sd card?
Click to expand...
Click to collapse
Yessir
mystica555 said:
Code:
# cd /sdcard
# dd if=/dev/zero of=swap.fil bs=1M count=128
128+0 records in
128+0 records out
# mkswap ./swap.fil
Setting up swapspace version 1, size = 134213632 bytes
# swapon ./swap.fil
# free
total used free shared buffers
Mem: 99040 97112 1928 0 556
Swap: 131064 0 131064
Total: 230104 97112 132992
#
Click to expand...
Click to collapse
i'm slightly hesitant to try .. anyone? good / bad / indifferent???
What exactly will this do and will a reboot cancel this?
widto08 said:
What exactly will this do and will a reboot cancel this?
Click to expand...
Click to collapse
even if a reboot didn't cancel it .. the next update.zip would .. unless something was built into it
yeah a reboot will cancel... how can I make this permanent? What file can I put the swapon command into? I just tried init.rc, but that didn't work.
PROOF OF CONCEPT ONLY! Serious risks involved, still working on this!
As a test, it works. however:
This has a few(lot of?) problems!
Biggest: your sd card cant be mounted as a disk unless you stop swapping. or reboot.
Next: your sd card will die sooner rather than later, as you are doing what it never was intended to do (writing moving data back and forth when its really good just for storing files that may change. sometime.)
Finally, things can start to run slow...VERY slow...
Biggest issue, after my busride with last.fm never stopping, browsing, all the stuff that kept making me angry before. Then i got home and tried to make a phonecall... The dialer worked *reasonably* responsive.. All of about 10s to bring it up. However, MAKING the call took...an eternity.
Hit the green button to dial...phone starts ringing, friend answers, we start talking.. I look at the phone.. black screen...ITS WAITING FOR THE ANDROID PIC AND CALL TIMER THING TO COME UP...40s after i started the call, got a message saying that one process was not responding, force or wait. at this point, when *that* dialog came out of swap, lo and behold the process actually not responding was working fine behind said dialog...
So yeah. its got its benefits, but very large downfalls.
As you *WILL* destroy your flash after an unspecified amount of time, *do not* try to put this on your internal flash. Not in /cache for example. Flash cards are cheap; replacing the g1 because you nuked 64 megs of flash ram is not...
I will test a few methods of separating the flash card from the vfat filesystem (mountable via usb_mass_storage) and report back. Probably partitioning the card, one as swap and such.
ON the other hand, I may also try partitioning 128m as fat16, to make certain the small card's wear levelling scheme is able to do whatever it can to help mitigate the destruction-by-swapping.
Fat32 may not have the same wear levelling mechanisms at the card level on anything less than an SDHC, and guaranteed ext2 wont. Raw swap won't either... As far as I remember, flash wear levelling on sdcards is based entirely on how FAT allocates blocks. (someone knowledgeable about the SD/SDHC and wear levelling feel free to chime in!)
I'll post more later when I try a few more things!
I really hope this turns into a sound solution...and then I can die happy.
Or live with my G1 happily...yea thats better.
mystica555 said:
As a test, it works. however:
This has a few(lot of?) problems!
Biggest: your sd card cant be mounted as a disk unless you stop swapping. or reboot.
Click to expand...
Click to collapse
Which is why I put it in /system/sd/swap/swap.fil
mystica555 said:
Next: your sd card will die sooner rather than later, as you are doing what it never was intended to do (writing moving data back and forth when its really good just for storing files that may change. sometime.)
Click to expand...
Click to collapse
Not an issue for me. By the time it wears out, I will have upgraded to a newer faster card anyway.
mystica555 said:
Finally, things can start to run slow...VERY slow...
Biggest issue, after my busride with last.fm never stopping, browsing, all the stuff that kept making me angry before. Then i got home and tried to make a phonecall... The dialer worked *reasonably* responsive.. All of about 10s to bring it up. However, MAKING the call took...an eternity.
Hit the green button to dial...phone starts ringing, friend answers, we start talking.. I look at the phone.. black screen...ITS WAITING FOR THE ANDROID PIC AND CALL TIMER THING TO COME UP...40s after i started the call, got a message saying that one process was not responding, force or wait. at this point, when *that* dialog came out of swap, lo and behold the process actually not responding was working fine behind said dialog...
So yeah. its got its benefits, but very large downfalls.
Click to expand...
Click to collapse
Could this be due to the speed of your SD card? I am already noticing a marked performance increase.
I tell you what, if you can give me an idea of where to make this permanent, I am willing to run this card to destruction. I have another 8G class 6 card ready to go, and can swap out easily at any time. All I have to do is make regular backups on my laptop and I should be good to go. (And even then data loss is not really an issue for me anyway.)
Wear levelling..Different than I thought.
mystica555 said:
ON the other hand, I may also try partitioning 128m as fat16, to make certain the small card's wear levelling scheme is able to do whatever it can to help mitigate the destruction-by-swapping.
Fat32 may not have the same wear levelling mechanisms at the card level on anything less than an SDHC, and guaranteed ext2 wont. Raw swap won't either... As far as I remember, flash wear levelling on sdcards is based entirely on how FAT allocates blocks. (someone knowledgeable about the SD/SDHC and wear levelling feel free to chime in!)
Click to expand...
Click to collapse
Ok, I read a bit into this myself and it seems even back in 2003 wear leveling is done at a very low level: CHS/LBA blocks, versus FAT Blocks.
Sandisk Whitepaper from 2003
I would expect that this sort of wear-leveling is in effect on any of their current cards, including the microsdhc the G1 came with.
As such, it seems swap/ext2 won't have much if any difference compared to FAT filesystems. Its recommended to mount the ext2 with option "noatime" however, so that metadata won't be written for -every single read-.
t1n0m3n said:
Which is why I put it in /system/sd/swap/swap.fil
Click to expand...
Click to collapse
It seems I haven't read enough about where you can put files.. Is this /system/sd normal for a G1, or is this after you went and moved apps/caches to the SD card?
t1n0m3n said:
Not an issue for me. By the time it wears out, I will have upgraded to a newer faster card anyway.
Click to expand...
Click to collapse
Indeed! This is mainly a warning to not try and use the phone's internal flash.
t1n0m3n said:
Could this be due to the speed of your SD card? I am already noticing a marked performance increase.
Click to expand...
Click to collapse
I am 90% certain that it is the speed of the card. Note: I am still using the 1gb card that was installed initially, sadly this phone broke me. Payday friday though means a trip to microcenter
That, or you haven't run 64 megs of apps out of main ram into swap. I had a -lot- of junk running in the background, in addition to the laundry list of apps enumerated earlier in the thread. I think it was: connectbot, helloaim, browser with 4 windows, terminal, alarmclock, calendar (twice! wtf) tmo myfaves switcher, last.fm, maps, voice dialer (twice as well?) google talk messaging klaxon and about 2 or 3 others I cant remember. At peak usage, I had 68 megs swap used and all the ram used as well.
There should be a rather quick and dirty way of getting this into an init script. I'll mess with it at lunch tomorrow.
Right now, sleep is calling and this is one call I'm not forwarding to voicemail!
mystica555 said:
It seems I haven't read enough about where you can put files.. Is this /system/sd normal for a G1, or is this after you went and moved apps/caches to the SD card?
Click to expand...
Click to collapse
/system/sd is my ext2 partition on my SD card that I moved my apps/caches to.
Has anybody tried compcache yet? Its compressed swap and it is ideal for this device, if it can be made to run.
http://code.google.com/p/compcache/
I promise i've searched for this already, but i can't find any thread that addresses this really...
Anyway, i'm running CM7 on my EVO and i'd like to be able to connect it to my xoom to transfer files and stuff. I have the latest tiamat kernel (1.4.4) and i have no problem mounting flash drives, or even my hard drive using the ntfs app, but when i mount my phone nothing happens.
My phone shows mount usb, but when i select it, it seems to take longer than usual to 'mount'. But even though my phone says its mounted, my xoom can't see it. Hopefully that even makes sense...
I'm just curious if maybe there is a script or something i have to run, like when using usb to tether my phone? Which, again, seems odd that it works as a tether, but i can't see my storage?
Hopefully someone can point me in the right direction
Ok, i ran the following in terminal emulator while the phone was "mounted" (according to the phone, not the xoom). Its weird, it doesn't see anything at all. any other ideas guys? do i need to find drivers for it or something? hmmmm.....
export PATH=/data/local/bin:$PATH
$ export PATH=/data/local/bin:$PATH
$ su
# df
Filesystem Size Used Free Blksize
/dev 359M 32K 359M 4096
/mnt/asec 359M 0K 359M 4096
/mnt/obb 359M 0K 359M 4096
/system 236M 208M 27M 4096
/data 28G 6G 21G 2048
/cache 166M 4M 162M 4096
/pds 1M 108K 1M 2048
/data/media/external 14G 7G 7G 32768
/mnt/sdcard 28G 6G 21G 2048
#
I'm running ICBINB[1] and I'm experiencing poor performance. For instance, when running the Drag Racing game, a race may take 30-45 seconds while in "game time" it only takes 12 seconds.
I installed per the directions on the rom's thread.
I then waited 10 minutes
rebooted recovery and restored data, rebooted
waited 10 minutes
rebooted recovery and installed acid theme, cleared cache fixed permissions per op
rebooted and waited 10 minutes
I don't have a ton of apps and just have 2 widgets (simi clock and simple calendar). I'm running Launcher Pro. Quadrant scores (while not the end all) are around 1360, which seems really low based on what others have said.
I'm just reflashed ICBINB and am going to just run that for a bit (no restoring data, no theme, no launcher pro) and see what performance is like.
Any suggestions?
Thanks in advance,
Ryan
[1] http://forum.xda-developers.com/showthread.php?t=1157593
Drag racing has always run slow on samsungs for some reason.. unless I was OCed it wouldn't run properly half the time. Icbnb is pretty close to stock
Are you on froyo or gb? Ext4? If not try them and maybe oc should help
sent from my real Gs move in silence like lasagna
mbernusg said:
Drag racing has always run slow on samsungs for some reason.. unless I was OCed it wouldn't run properly half the time. Icbnb is pretty close to stock
Are you on froyo or gb? Ext4? If not try them and maybe oc should help
sent from my real Gs move in silence like lasagna
Click to expand...
Click to collapse
I find if I load the game then clear the ram then the game runs smooth. Otherwise its rediculously laggy, even if I clear the ram before I run it.
I'm not sure why it lags either, but GB gets rid if it. Maybe you should try ICBINB GB.
be sure to install chainfire 3d and get some of the drivers like nvidia
also OVERCLOCKING is always a big boost for games
and if you haven already try the adrenaline shot
also if you quad scores are that low sounds likes your not on ext4
dsexton702 said:
be sure to install chainfire 3d and get some of the drivers like nvidia
also OVERCLOCKING is always a big boost for games
and if you haven already try the adrenaline shot
also if you quad scores are that low sounds likes your not on ext4
Click to expand...
Click to collapse
Just wanted to add that my previous post referred to ICBINB KD1, before SAS was released. My setup was simply ICBINB KD1 stock.
I also never tried installing Chainfire 3D or overclocking when I was on Froyo. Maybe Chainfire 3D is the solution though.
What does chainfire 3d do that makes games run better?
Sent from my SGH-T959V using xda premium
Here is a link to Chainfire 3D
From his description:
Chainfire3D sits between your apps and the graphics drivers, and can intercept and/or change commands between the two. It has some built-in functions, and can be further extended with plugins to provide extra functionality.
Not that it matters, but pre/post quadrant/linpack scores were really no different before/after chainfire... I did not do a real graphics benchmark though.
s15274n said:
Here is a link to Chainfire 3D
From his description:
Chainfire3D sits between your apps and the graphics drivers, and can intercept and/or change commands between the two. It has some built-in functions, and can be further extended with plugins to provide extra functionality.
Not that it matters, but pre/post quadrant/linpack scores were really no different before/after chainfire... I did not do a real graphics benchmark though.
Click to expand...
Click to collapse
its not meant to boost quad scores but to make games run better, and it does a great job of doing so
dsexton702 said:
be sure to install chainfire 3d and get some of the drivers like nvidia
also OVERCLOCKING is always a big boost for games
and if you haven already try the adrenaline shot
also if you quad scores are that low sounds likes your not on ext4
Click to expand...
Click to collapse
Installed Chainfire 3D, Quad jumped to 1531. I searched, but can't find the nvidia drivers you're talking about, do you have a link?
I installed Adrenaline shot from the following link and my phone no longer booted (stuck at Samsung splash screen). So I booted into CWM and restored a backup. I tried it twice just in case it was a fluke.
http://forum.xda-developers.com/showthread.php?t=1236779
Here are the first few lines from running "adb shell mount". /system, /cache, and /data are ext4, but /sys is sysfs. Is this output right for EXT4? Also, noticed that sdcard is vfat.
rootfs / rootfs rw,noatime 0 0
proc /proc proc rw,noatime 0 0
sys /sys sysfs rw,noatime 0 0
/dev/block/stl9 /system ext4 ro,noatime,barrier=0,data=writeback,noauto_da_alloc 0 0
/dev/block/stl11 /cache ext4 rw,noatime,barrier=0,data=writeback,noauto_da_alloc 0 0
/dev/block/stl10 /data ext4 rw,noatime,barrier=0,nodelalloc,data=writeback,noauto_da_alloc 0 0
tmpfs /dev tmpfs rw,noatime,mode=755 0 0
devpts /dev/pts devpts rw,noatime,mode=600 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
/dev/block/stl6 /mnt/.lfs j4fs rw,noatime 0 0
tmpfs /mnt/asec tmpfs rw,noatime,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
...
/dev/block/vold/179:1 /mnt/sdcard vfat
I appreciate the help.
Honestly jump to gb and then your ext4 should be on data cache and system. That should be enough to help
sent from my real Gs move in silence like lasagna
Please use the Q&A Forum for questions Thanks
Moving to Q&A
Dear all,
Sensation XE specs state 4 gigs of internal memory and only 1 gig available.
Where is the other 3 gigs?
Could we recover them somehow?
Regards.
padvou said:
Dear all,
Sensation XE specs state 4 gigs of internal memory and only 1 gig available.
Where is the other 3 gigs?
Could we recover them somehow?
Regards.
Click to expand...
Click to collapse
boot partition
data partition
firmware partition
cache partition
system partition
that's why we have only 1gb available for the user
padvou said:
Dear all,
Sensation XE specs state 4 gigs of internal memory and only 1 gig available.
Where is the other 3 gigs?
Could we recover them somehow?
Regards.
Click to expand...
Click to collapse
As rzr86 said, there are a few partitions on the phone, of which only /data is available for us (unless rooted).
System is where the system apps and framework are located (the OS itself)
Boot is where the kernel is.
Firmware is where... the firmware is located
And there are a few more that, like firmware, are blocked unless S-OFF (even if HTC-Unlocked), to keep the device from being bricked (these partitions are responsible for the boot-up and for connecting the software to the hardware.
Other devices with larger internal storage also have this behaviour - models with 16GB usually have 12-13 available to the user. So is 32 and 64 GB versions of phones - about 3-4 GB are reserved for system usage.
As for recovering that area - It can't be "recovered", as it is needed for the OS to function. It's like Windows takes a couple of gigs to be installed (or any other OS).
The unavailable area is all of those partitions.
It is clear to me now.
Thank you for your responses. :good:
It sounds like a big waste of space right? Even if sense uncompressed takes around 1gb something along those partitions that must be a s**tload of space left. Oh well. I guess we have to have fun with the 1gb available for us lol.
PS -AOSP roms should take less than 200mb installed, talk about waste of space :b
MidnightDevil said:
It sounds like a big waste of space right? Even if sense uncompressed takes around 1gb something along those partitions that must be a s**tload of space left. Oh well. I guess we have to have fun with the 1gb available for us lol.
PS -AOSP roms should take less than 200mb installed, talk about waste of space :b
Click to expand...
Click to collapse
Just think about this - with have lots of room to expand our ROMs, we are not limited to just stock. For example, there is an old Optimus One (now unused, being used by me as a testing device for apps) in my house, to run Cyanogenmod, they had to remove all non-English languages, so I had to remove some system apps to put hebrew fonts inside. And there are many more devices with 512MB ROM.
The desire got it's 2.3 update as a "trimmed" version of sense to be able to have it, and on all phones there is almost no place for apps.
Some ROMs don't use all that space, right. But having this overhead benefits us as we aren't limited by space.
Also, in the future, if someone pulls it off - we can have an hboot with the ability to make custom partitions, like the Nexus One has.
I've seen the partition layout just a couple of days ago, will try to find it (incl. sizes).
Edit: Okay, found a shell command to give partition layout, here it is (those are all mounted partitions, not all of them
Filesystem Size Used Free Blksize
/dev 271.7M 52K 271.6M 4096
/storage 271.7M 0K 271.7M 4096
/vendor/firmware/misc 199.8M 21.5M 178.3M 4096
/vendor/firmware/adsp 199.8M 5.7M 194.1M 4096
/mnt/secure 271.7M 0K 271.7M 4096
/mnt/asec 271.7M 0K 271.7M 4096
/mnt/obb 271.7M 0K 271.7M 4096
/mnt/fuse 271.7M 0K 271.7M 4096
/system 787.4M 388.8M 398.6M 4096
/data 1.1G 484.6M 691.4M 4096
/cache 118.1M 98M 20.1M 4096
/devlog 19.7M 14.8M 4.9M 4096
Some of those I know, some are new to me, and they actually seem empty (all those /mnt/ for example), but I believe they have their purpose. If someone not S-OFF (or even not unlocked at all) could check we may have the answers.
Hi, this is probably a silly question, in the sense that the answer is simple, and yet right now I'm a bit lost. My total internal storage capacity, according to Windows when my phone is plugged, is 226gb. Also according to Windows, and file managers on Android, all the content is taking 180gb. So far so good. But on Windows I see free space: 16gb. So, 226 - 180 = 46.
Removing the 16gb free, that leaves me with something unknown taking 30gb. Is it the system, the apps, the apps data? If it's the system, I think 30gb is way too much. If it's the apps, also I think it's too much. If it's the app's data, that's actually OK, but I thought that data is usually on the internal storage. If not, were could it be?
I think this is a mix of all the three, but, to be certain, I would like to know a way to check the system size, the apps size and the apps data size. Can this be done? Thanks!
EDIT
OK, just found out that system is taking about 14gb and this is already excluded from the total capacity shown on Windows, so, I still don't know where the 30gb occupied space may be coming from.
Check device's internal storage's disk usage via du command. See also here:
How to Find Disk Usage of Files and Directories in Linux
This article explains 10 useful "du" (disk usage) commands that help you to find out disk usage of files and directories in Linux.
www.tecmint.com
Yes, du reports 180GB on internal sdcard, that I know. But if total is 226GB and free is 16GB, 226GB minus 180GB actually give us 46GB supposedly free, so, where are the 30GB left of the occupied space?
AFAIK a portion of the internal sdcard's total capacity is used to store certain functions including optimizations of the memory that support performance and endurance and therefore is not available for user storage.
xXx yYy said:
AFAIK a portion of the internal sdcard's total capacity is used to store certain functions including optimizations of the memory that support performance and endurance and therefore is not available for user storage.
Click to expand...
Click to collapse
It's not available, yet it shows as space taken? Would that take 30GB?
Sorry for making a new post instead of an edit, but there's new info and I think it should be separated. So, I've been playing around with the df and du command, and here are the results. I've deleted a 40GB folder from internal memory so forget about the numbers on the first post:
df output:
Code:
Filesystem Size Used Avail Use% Mounted on
/data/media 226G 160G 67G 71% /mnt/runtime/default/emulated
du output:
Code:
104M /data/adb
36K /data/anr
14K /data/apex
13G /data/app
3.5K /data/app-asec
3.5K /data/app-ephemeral
3.5K /data/app-lib
3.5K /data/app-private
3.5K /data/app-staging
0 /data/app-tmp
1.3M /data/backup
3.5K /data/bootchart
14K /data/cache
906M /data/dalvik-cache
9.2G /data/data
0 /data/data-tmp
3.5K /data/dpm
11K /data/drm
3.5K /data/extm
7.0K /data/gsi
1.4M /data/local
3.5K /data/lost+found
18M /data/magisk_backup_7d97454e4da0aa16d84783dfc5b6e31f1ca44c15
131G /data/media
3.5K /data/mediadrm
25M /data/misc
66K /data/misc_ce
105K /data/misc_de
3.5K /data/miui
2.8M /data/mqsas
11K /data/nfc
3.5K /data/ota
3.5K /data/ota_package
3.5K /data/per_boot
3.5K /data/preloads
12K /data/property
11K /data/rclone
260K /data/resource-cache
40K /data/rollback
3.5K /data/rollback-observer
4.5K /data/ru.bkqovrzm.cvkvlilxi
4.5K /data/ru.guhkdbvd.bioxbkqve
4.5K /data/ru.tsglwgsm.qdvpylesc
3.5K /data/sdcard
7.5K /data/server_configurable_flags
3.5K /data/ss
59M /data/system
4.0M /data/system_ce
289K /data/system_de
3.5K /data/tmp
18K /data/tombstones
27K /data/unencrypted
306M /data/user
805M /data/user_de
168M /data/vendor
18K /data/vendor_ce
7.5M /data/vendor_de
156G total
I have a couple of questions here. Is it the /data/media from df equal to /data folder? If they are, according to df there are 160GB occupied, but according to du theres 156GB in use. Where are the 4GB left?
Also, if those paths does not relate to the same thing, according to df there are 160GB occupied on "/data/media", but according to du theres 131GB in use in "/data/media". Where are the 29GB left?
I hope my questions make sense. I feel like I'm missing something here about how spaces a partitions work on Android, so let's hope someone can clarify me that.
Thanks!
Only to have mentioned it:
Android typically ( ext4 FS ) allocates disk space in 4KB chunks. Means the disk space allocated for files you store always is a multiple of 4KB. So storing a file of size 1B will allocate 4KB, if you store a file of size 5KB then 8KB disk space get allocated ...
Disk space allocated for a file in the rarest case is file's real size.
xXx yYy said:
Only to have mentioned it:
Android typically ( ext4 FS ) allocates disk space in 4KB chunks. Means the disk space allocated for files you store always is a multiple of 4KB. So storing a file of size 1B will allocate 4KB, if you store a file of size 5KB then 8KB disk space get allocated ...
Disk space allocated for a file in the rarest case is file's real size.
Click to expand...
Click to collapse
So you mean those 4GB left may came from that fact? So the "/data/media" from df command is the "same" one as "/data/" from du command?
Data/media is its own thing and sits next to data/data, data/obb.. AFAIK its a new thing and contains all the media related to apps and games etc.. Presuming video and audio files.. I wouldn't delete it as it might bork apps but you might be able to delete certain ones if they won't affect the OS..
Any storage discrepancy will be in cluster size and bits to bytes conversions.
shivadow said:
Data/media is its own thing and sits next to data/data, data/obb.. AFAIK its a new thing and contains all the media related to apps and games etc.. Presuming video and audio files.. I wouldn't delete it as it might bork apps but you might be able to delete certain ones if they won't affect the OS..
Any storage discrepancy will be in cluster size and bits to bytes conversions.
Click to expand...
Click to collapse
I'm talking about the difference in labels between commands.
According to df:
Code:
Filesystem Size Used Avail Use% Mounted on
/data/media 226G 160G 67G 71% /mnt/runtime/default/emulated
According to du:
Code:
131G /data/media
156G /data/ (total)
So, if the "/data/media" label from df equals the "/data/media" label from du, I'm missing 30GB (160GB used vs 131 GB used). If the "/data/media/" label from df it's actually the data partition, then I'm missing 4GB (160GB used vs 156GB used). You get what I mean? If they're the same I could understand 4GB discrepancy, if they are not the same, are you saying the filesystem format actually eats up 30GB out of nowhere???
In your case /data/media is a mounted partition ( block device ) with fixed maximum size 226GB. It houses the directories /storage emulated/<UID>/Downloads, /storage emulated/<UID>/Musics, /storage/emulated/<UID>/Pictures, storage emulated/<UID>/Videos, ...
The mentioned partition may already have so-called bad blocks, i.e. unusable blocks. It is not uncommon for sd-cards to have 2-6% bad blocks when they leave the factory.
xXx yYy said:
In your case /data/media is a mounted partition ( block device ) with fixed maximum size 226GB. It houses the directories /storage emulated/<UID>/Downloads, /storage emulated/<UID>/Musics, /storage/emulated/<UID>/Pictures, storage emulated/<UID>/Videos, ...
The mentioned partition may already have so-called bad blocks, i.e. unusable blocks. It is not uncommon for sd-cards to have 2-6% bad blocks when they leave the factory.
Click to expand...
Click to collapse
And the /data folder is also inside this partition, right? Because that one is taking 156GB according to du... if not, why according to df /data/media has 160GB occupied and according to du /data/media has 131GB occupied? Why this discrepancy?
OMG. Become familiar with your device's Android OS's partition structure. Learn what is difference between partition and directory. GIYF ...
I'm trying, but I haven't found anything solid enough so I'm asking here.