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 was wondering what write speeds you guys are getting to the Nvidia Shield Tablet.
I bought the Samsung Evo 64GB, and I'm getting around 7MB/s write from the computer to the microsd card.
A1 bench reports 10MB/s write, and on computer people are reporting around 13MB/s for this card.
I want to change cards, but first I want to confirm you guys are getting faster write speeds (15MB/s+) on your faster cards.
Method for testing:
1) Create a test file using cmd: fsutil file createnew 1GB.dat 1073741824
2) copy to phone microsd, time with stop watch: http://www.online-stopwatch.com/
3) 1024 / seconds to copy file = write speed in MB/s.
Would appreciate it if you guys can test your cards
just copied 1.1714gb to the internal mem of tablet in 85secs =13.78mb/sec
the very same file copied to a sandisk 64gb ultra microsd in the tablet took 164secs =7.14mb/sec
This is a post, asking for some short of last chance of help, before calling the professionals
Yesterday, my phone went off (with quite a battery still) and when restarting a worrying message appear : "Impossible to mound SD card, it may be corrupted".
(and of course, with a outdated backup on my pc for weeks...)
I have read other posts, and nothing seems to help:
http://forum.xda-developers.com/showthread.php?t=1917058
http://forum.xda-developers.com/showthread.php?t=367912
The microSD is a Transcend 16GB class4, not sure this info is key, but let it be know.
As Android doesn't load, I switch to PC, I plug the microSD into a USB adapter and go
First on Windows:
I try to load content, SD appear for few seconds and then disappear again.
On DISKPART >> list volume, The error message: "Virtual Disk Service Error: the object has been "
Try ZAR-X, and it keeps on "Enumerating devices, please wait", and does not do anything else
As things get ugly, I switch to linux (Ubuntu)
Trying to load on folder browser I got:
Unable to mount sd-ext
Error mounting /dev/sdc2 at /media/ubuntu/sd-ext:
Command line 'mount -t "ext3" -o "uhelper=udisk2,nodev,nosuid" "/dev/sdc2" "/media/ubuntu/sd-ext/" '
exited with non-zero exit status 32: wrong fs type, bad option, bad superblock on /dev/sdc2,
missing codepage or helper program, or other error
In some cases useful info is found in syslog -try dmesg | tail or soor:Error mounting /dev/sdc2 at /media/ubuntu/sd-ext:
Command-line `mount -t "ext3" -o "uhelper=udisks2,nodev,nosuid" "/dev/sdc2" "/media/ubuntu/sd-ext"'
exited with non-zero exit status 32: mount: /dev/sdc2 is not a valid block deviceor:Unable to open folder for 15GB Volume
Error when getting information for file '/media/ubuntu/ES64-FA45': No such file or directory
went back to basis and run "sudo fdisk -l" and here I notice similar behiviour that windows, during the first 30 seconds or so after inserting the microSD/USB into the computer I it apear (among other disks) :
Disk /dev/sdc: 15.9 GB, 15931539456 bytes
255 heads, 63 sectors/track, 1936 cylinders, total 31116288 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x000d450f
Device Boot Start End Blocks Id System
/dev/sdc1 1 29617187 14808593+ c W95 FAT32 (LBA)
/dev/sdc2 29617188 30617187 500000 83 Linux
/dev/sdc3 30617188 31116287 249550 82 Linux swap / Solarisbut after those 30 second, no trace of the usb in the fdisk-list
I wonder if there is something else I can do from my limited hardware availability, and even that following attempts could damage further the microSD
On mention posts, it is told about dd_rescue :
On Linux can try dd_rescue. It creates copy like normal dd but it does not abort on errors.
Copy card to file and then mount this file like drive
http://forum.xda-developers.com/showpost.php?p=13196906&postcount=19
is that something I could apply? OR something else I could do on my side?
or my last chance would be to put the SD in the hands of professionals and let do the job with open-heart-surgery-microscopy-tools?
(like those on : http://card-recovery.biz/us/service.php)
The data I have in the SD and not in the backup is enough valuable indeed to go that way, (on the other hand, house&personal insurance may also cover part of this cost)
----
By the way, two more things:
S-OFF, on one post, it is said:
S-OFF
This actually sounds a lot like what can happen to SD cards on some HTC devices if the S-OFF goes bad
(http://forum.xda-developers.com/showthread.php?t=1917058)but I can't find what shrike1978 was refering to
Real Time backup sync
Even I do regulary backups (or I intent to) I come to this situation.
Is there a tool/app/configuration that allows to have a real time synced copy of the contents on the SD (and preferable internal memory of mobile also) so chances of going broke are reduce to nearly ZERO ?
(In my PC I have of course a RAID, really bad there is no such options on Mobiles at cent costs on SD nowadays)
any help, please?
I bough a tablet which claims to be Xgody T702 Pro-E. The seller says that it has 3 GB RAM and 32 GB internal storage. The internal storage is clearly not 32 GB, looks like it could be 16 GB.
But how can I find the real size of the RAM? CPU-Z says that it has 2982 MB of total RAM, with 1297 MB available. Droid Info says Total 2982 MB and 1291 MB available. Fake Device Test says MemTotal 3054480 kB, but MemFree is 18446744073708527148 kB!!!!
When I log into the device with adb shell, free and top give these results:
Code:
# adb shell
T702_Pro-E:/ $ free
total used free shared buffers
Mem: 2054045696 1999200256 54845440 25714688 2760704
-/+ buffers/cache: 1996439552 57606144
Swap: 1027018752 0 1027018752
T702_Pro-E:/ $ top
Tasks: 240 total, 1 running, 237 sleeping, 0 stopped, 1 zombie
Mem: 3054480k total,-2144429167k used,2147483647k free, 2696k buffers
Swap: 1002948k total, 0k used, 1002948k free, 1380256k cached
400%cpu 2%user 1%nice 4%sys 393%idle 0%iow 0%irq 0%sirq 0%host
Observe the insane values for used and free that the top command displays!
What is the true amount of RAM?
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.