21.11.21 4.4.4 System Dump - Droid Ultra General

For all those damn screw-ups.
Note: one file/folder in /etc would not copy as I am unrooted.
From my Maxx 16 GB. 853 MB's of fun!

Related

Why does desire builds take so much space

http://www.htc.com/www/product/desire/specification.html
ROM: 512 MB
Click to expand...
Click to collapse
http://www.htc.com/www/product/hd2/specification.html
ROM: 512 MB
Click to expand...
Click to collapse
Euro HD2 have same size of storage than Desire. Then how can we have such small amount of free storage after installing? Or desire also have only 180MB free after install? That sounds a bit too small for real android device.
What am i missing here?
Part of the problem is that "devs" are de-odexing apks and jars. While it's true that the system image is larger with the odexes (roughly about 20 MB), that space is soon used up, but on /data when the build first-boots and creates the dalvik-caches for system files (which don't need to be created in builds that are pre-odexed).
I'll give you an example. framework.jar (in /system/framework) is around 2.5-3 MB on a de-odexed system. The classes.dex inside it gets uncompressed to dalvik-cache, and uses an addiional 6 MB, for a total file of 8.5-9 MB.
On a regular, odexed system, framework.jar is around 30kb (since it doesn't contain a classes.dex inside) and the respective odex uses up 6 MB (and since it's already an odex, it doesn't have to be uncompressed to dalvik-cache). Total size for framework: 6.03 MB.
Now, for your question. Original desire builds are odexed, so they're about 20-40 MB smaller on a shipped device. You get about 220 MB free on a stock Desire.
On top of the de-odexing, something that costs space is that the devs write larger partition than necessary, but you can fix this when you flash your build by editing the flash.cfg and writing smaller partitions for all but userdata (that way you have more space available for apps), here's what I use:
Code:
boot ya|boot|ro filesize boot.img
system ya filesize system.img
cache ya 3M
userdata ya|asize|hr allsize
cache might be unnecessary now since 2.2. It's used for OTA updates (we don't care about those) and market cache, but since 2.2 market downloads are cached on SD if there's no space on cache, so that might be another 3 MB you can get back.
Plus my personal build is odexed, so I have (on TMOUS HD2) ~800 MB free on first boot.
jubeh said:
Part of the problem is that "devs" are de-odexing apks and jars. While it's true that the system image is larger with the odexes (roughly about 20 MB), that space is soon used up, but on /data when the build first-boots and creates the dalvik-caches for system files (which don't need to be created in builds that are pre-odexed).
I'll give you an example. framework.jar (in /system/framework) is around 2.5-3 MB on a de-odexed system. The classes.dex inside it gets uncompressed to dalvik-cache, and uses an addiional 6 MB, for a total file of 8.5-9 MB.
On a regular, odexed system, framework.jar is around 30kb (since it doesn't contain a classes.dex inside) and the respective odex uses up 6 MB (and since it's already an odex, it doesn't have to be uncompressed to dalvik-cache). Total size for framework: 6.03 MB.
Now, for your question. Original desire builds are odexed, so they're about 20-40 MB smaller on a shipped device. You get about 220 MB free on a stock Desire.
On top of the de-odexing, something that costs space is that the devs write larger partition than necessary, but you can fix this when you flash your build by editing the flash.cfg and writing smaller partitions for all but userdata (that way you have more space available for apps), here's what I use:
Code:
boot ya|boot|ro filesize boot.img
system ya filesize system.img
cache ya 3M
userdata ya|asize|hr allsize
cache might be unnecessary now since 2.2. It's used for OTA updates (we don't care about those) and market cache, but since 2.2 market downloads are cached on SD if there's no space on cache, so that might be another 3 MB you can get back.
Plus my personal build is odexed, so I have (on TMOUS HD2) ~800 MB free on first boot.
Click to expand...
Click to collapse
Might I ask what build you're using with 800Mb free?
Wow, thanks for the explanation. So what are the pros of de-odexed builds?
I will ask that here instead of starting new thread:
Is there a way to change treshold for "Low Disk Space" error message? According to the DiskSpace application, i have around 50MB of the free space, which is quite a lot when max is 180. But still i got Low Disk Space and i can't install any applications.
Friend have real Desire with 20MB of free space and he don't have that message.

Why is my system partition that big?

I'm wondering why the system partition of my D802 (16gb version) is 2700mb big. Is it just me or is it normal? Did I do something wrong while flashing ROMs? currently running latest omnirom.
For comparison, the system partition of my old nexus 7 (2012 16 GB version), also running omni has only 649mb.
g2: 2724 mb system, 10640 mb rest
nexus 7: 649 mb system, 13720 mb rest
Because lg set it to that size. Their stock ROM is actually big when uncompressed, but /system is always large.
Transmitted via Geass

Storage is counting internal files Twice taking up too much space

Anyone know how to fix this issue.
Build Number: LMY47X.G928PVPU2AOI6
Model Number: SM-G928P
/storage/emulated/0
/storage/emulated/legacy
They both contain the same files and are linked together. So if I erase something from one it is erased on the other. That's fine I understand they have the same files.
The issue is my phone is counting the space being used twice. Say I have 14 gb's of free space. Then I download a 2 gb file and I go from 14 gb to 10 gb free.
I also noticed that these 2 paths are linked and have the same files /storage/sdcard0 and /sdcard.
Now I've discovered that all 5 of these paths have the same files I have a Galaxy S6 so I only have internal memory.
/storage/emulated/0
/storage/emulated/legacy
/storage/sdcard0
/storage/sdcard
/mnt/sdcard
Please help it's bad enough I only have 25 gb of space to begin with. Having 12.5 is even worse.
/storage/emulated = 7 gb
/storage/emulated/0 = 3.5 gb
/storage/emulated/Legacy =3.5 gb
Shouldn't /storage/emulated = only say 3.5 gb?
I have space problem too.
Sent from my SM-G928C using Tapatalk
Download some random terminal from gplay and check with df what information will be showing
This is what I got.
I attached a screen shot of terminal screen
I also attached a screenshot of disk map using X-Plore App
Your device have different partitions from 928f. From what ive seen here, your internal memory is fine - check the line /0; /legacy and /data. You have 50% used space. Before year and more ive debugged Vibe s1 and there was the same situation, but with no problems with space, besides the mirrored/ linked partitions. Post pics from system storage in settings/ internal storage and scanned data partition in es file or so. There is no suck thing like "...2 gb file and I go from 14 gb to 10 gb free." Waiti g for your response.

I can't find files taking up space in my internal memory of an android phone

I have bought Lenovo k4 note n have recently upgraded to marshmallow. So I ve 16 GB of internal memory out of which the Android 6.0 inbuilt memory app inside storage and USB setting, says 5.37 GB is OS occupied. 9.46 GB out of 10.63 GB is used. Further break down are as follows:
Apps 5.29 GB
Images 105 MB
Videos 8 KB
Audio 588 KB
Other 488 MB
Cached Data 183 MB
Which totals to 6.066 GB. So now subtracting 9.46 with 6.066 GB I get 3.394 GB which I can't understand where it went.
Still after going inside file manager n clicking the view hidden files these are what I get:
Android 2.17 GB
Download 278.01 MB
Shareit 200 MB
WhatsApp 136 MB
Pictures 74 MB
Books 52 MB
DCIM 29 MB
Which comes to around 3 something GB and still 3 GB are missing.. so.. around 6 GB of files are not showing.. I am unable to find the files that are taking up space. Can anyone help please.
Now I have rooted my device with Twrp n SuperSU and and now I still have the same problem of large data files. Is it normal or can I get more space. The user data which I wasn't able to see is accessible now. Can I delete those data to free up space. And how do I get to look files taking up space which actually adds up to the space I have. The first pic I uploaded provides information of my phone's storage handled my marshmallow s219. You can see that 5.24 GB is OS occupied compared to unrooted 5.37 GB. The second image points to the fact that only around 3.2 GB of space is shown out of supposed 6.25 GB. The third image tells the accessible part of my phone data which is very low (around 700 MB). And the third is the inaccessible files which I have come to see through the blessing of rooting the phone. So I think my phone shouldn't use up that much data as I don't be very large app. Largest is Facebook. Can someone help me to optimise my phone. Thanking you guys in advance.?

Who Stole My 1.7 GB

Moto X Pure 16 GB android 6. If I look at storage in settings or in ES file explorer I see numbers that don't add up. Android OS 6.5 GB leaving me with 9.5 GB of which 8.7 is used. When I add up the individual usage amounts, they total about 7 GB not 8.7. I have a 32 GB sd card as external storage. The numbers there appear to be correct. So where is the 1.7 GB that is not accounted for? I looked for any large files like downloads or backups but there were none. I have 74 apps installed and about 700 mb of music and pictures which doesn't seems excessive to me..
It seems as though 16 GB is only good for the most basic of users.
Recovery partition, cache and probably other things such as the bootloader need to be accounted for too.
OK
I would have thought that the recovery partition would have been taken care of with the total space and the bootloader would have been included in the OS total. It would just have been nice if everything would be displayed what taping on Storage.

Categories

Resources