Develop Bugs

genius needed - utterly incomprehensible A2SD madness

Hey, wasn't sure where exactly this belonged so mods please forgive
ok so.....After having tried the whole proceedure two or three times to get a2sd working (root etc has always worked. It's just a2sd that's the problem)
Here's what I did in detail for debugging of the process:
1. Goldcard in
2. Head to recovery using recovery-linux.sh method.
3. Wipe/Factory Reset
4. Wipe cache
5. Wipe dalvik-cache.
6. Redo Wipe/Factory Reset for good measure.
7. Install from zip - 'rootedupdate.zip'
8. reboot to recovery again via recovery linux keeping goldcard in (accidently missed the hold down of the key so got to the first boot screen and pulled the battery...and entered recovery again).
9. Wipe cache
10. wipe dalvik-cache - overkill much? ;-)
11. Flash from zip -' r1-a2sd-desire-dalvik-upgrade-signed.zip'
12. Power off. Change to 4GB card. Start again entering recovery menu.
13. Wipe SD:ext partition (don't think it'll do anything as I'm about to overwrite the partition table anyway but hey extra steps that might help?)
14. Partition SD Card Swap: 0MB Ext2-size: 0MB Fat32=remainder.....To wipe the old table.
15. Partition SD card Swap: 0MB Ext2-size: 768MB Fat32-size = remainder.
16. Convert ext2 ---> ext3
Note - Rather than copy all of my files now, which is what I did previously I'll put an extra reboot into the proceedure
17. Reboot with newly created memory card -skip my way through the setup stuff. Install titanium backup from market place. Size before (from settings):140Mb free Size after: 137mb .......Application administrator page within settings is showing Titanium backup as only 540kb + 328kb market cache and 52kb data for market....not sure where the rest has come from).
adb shell
ls -l /data
Code:
# ls -l /data
drwx------ system system 2010-05-03 17:48 backup
-rw-rw-rw- media system 2 2010-05-03 17:43 pvcodec.txt
drwxrwxr-x system system 2010-05-03 17:48 system
drwxrwx--x system system 2010-05-03 17:43 anr
drwxrwx--x system system 2010-05-03 17:43 app-cache
drwxrwxrwx root root 2010-05-03 17:43 DxDrm
drwxrwx--x system system 2010-05-03 17:48 dalvik-cache
lrwxrwxrwx root root 2010-05-03 17:43 drm -> /data/local
drwx------ root root 2010-05-03 17:45 property
drwxrwx--x system system 2010-05-03 17:48 app
drwxrwx--x system system 2010-05-03 17:43 app-private
drwxrwx--x shell shell 2010-05-03 17:43 local
drwxrwxrwx wimax wimax 2010-05-03 17:43 wimax
drwxrwx--t system misc 2010-05-03 17:49 misc
drwxr-x--- root log 2010-05-03 17:43 dontpanic
drwxrwxrwx root root 2010-05-03 17:48 data
drwxrwx--- root root 2010-05-03 17:43 lost+found
busybox df -h
Code:
# busybox df -h
Filesystem Size Used Available Use% Mounted on
tmpfs 199.2M 0 199.2M 0% /dev
tmpfs 4.0M 0 4.0M 0% /sqlite_stmt_journals
/dev/block/mtdblock3 250.0M 220.2M 29.8M 88% /system
/dev/block/mtdblock5 147.6M 10.7M 137.0M 7% /data
/dev/block/mtdblock4 40.0M 2.7M 37.3M 7% /cache
tmpfs 8.0M 0 8.0M 0% /app-cache
/dev/block//vold/179:1
3.0G 48.0K 3.0G 0% /sdcard
18. I had intended copying accross the data from my SD card backup and using titanium to restore everything now.......but it looks like it hasn't worked again.
What am I doing wrongly?????

MrVarioII said:
11. Flash from zip -' r1-a2sd-desire-dalvik-upgrade-signed.zip'
Click to expand...
Click to collapse
You installed the WRONG A2SD file. As its a fresh install, you need r1-a2sd-desire-dalvik-fresh-signed.zip

PaulW21781 said:
You installed the WRONG A2SD file. As its a fresh install, you need r1-a2sd-desire-dalvik-fresh-signed.zip
Click to expand...
Click to collapse
Thank you soooooooooo much Paul!
I've been waiting to see this screen for so long:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
All's working great, though I observe that the market is working quite slowly. Images caching extremely slowly and things saying they'll download then not even appearing on the notification cue for a minute or two.....
Seems market doesn't like being on the SD card? any way we could arrange an exception for it? or is there some other work arround?
Anyway really really minor problem. I'm utterly ecstatic!

MrVarioII said:
Thank you soooooooooo much Paul!
I've been waiting to see this screen for so long:
All's working great, though I observe that the market is working quite slowly. Images caching extremely slowly and things saying they'll download then not even appearing on the notification cue for a minute or two.....
Seems market doesn't like being on the SD card? any way we could arrange an exception for it? or is there some other work arround?
Anyway really really minor problem. I'm utterly ecstatic!
Click to expand...
Click to collapse
Which Class SD card do you have? I have 8GB Class6 adn all work ok same as before root+A2SD
I have next partitions:
swap 64MB
ext3 1024MB (Im create ext2 and then upgrade it by ext2->ext3 option)
FAT32: alll space which left

MrVarioII said:
Seems market doesn't like being on the SD card? any way we could arrange an exception for it? or is there some other work arround?
Anyway really really minor problem. I'm utterly ecstatic!
Click to expand...
Click to collapse
The market runs slow at times for me too, it was doing it long before rooting aswell, so I'm leaving that down to a problem with Google themselves.
Think the longest I've waited (pre-root) was nearly 5 minutes for something to begin to download, but other times its pretty instant. Same happens with A2SD, times vary from a few minutes to instant, I guess it just depends on how loaded googles servers are which run the Market system.

The Market also has to rebuild itself after a flash and find all your apps, etc. Just leave it be, it'll be plenty fast again.

[Q] Whats eating up my internal storage space?

Hey, so I'm still a noob at everything but heres what I know...
I have an 16GB AT&T galaxy s3. I rooted it and installed Cyanogenmod 10 stable build (not sure if I should have posted in a Cyanogenmod forum...), anyways, I have cleared out all the bloat ware and made sure all my cache is kept cleared, but I still seem to have only half the internal storage space...
I have included a screenshot to show what my phone says about its storage.
Is there any app or any way to scan the internal storage to see whats (possibly?) left over from uninstalls or deletions?
Am i wrong to believe that the internal SD card of the galaxy is similar to standard harddrives where you delete files but they aren't ACTUALLY removed and still take up space? If so, is there a way to fully wipe the deleted items?
When I initially started with Cyanogenmod 10, I had the October nightly release (one of the last ones) and I had used Titanium Root to backup stuff (not sure where it all actually went, could it be on the phone still?). But I recently updated to the stable mod and tried to wipe everything off the phone to have a clean flash of the new ROM. So I've begun wondering if the backup files are still on the phone and where I could find them.
Or, lastly, I was thinking that maybe, just maybe, Cyanogenmod 10 takes up a lot of space, even though the file size is around 150MB...
Any ideas anyone? HELP!!!
Thanks!

Your operating system (CM10) takes up more than the 150MB download would suggest.
If you try "df" from shell, you'll see how your 16GB is partitioned. Here's what I got when I did it.
Filesystem Size Used Free Blksize
/dev 814M 52K 814M 4096
/mnt/asec 814M 0K 814M 4096
/mnt/obb 814M 0K 814M 4096
/system 1G 428M 1G 4096
/efs 13M 4M 8M 4096
/data 12G 8G 3G 4096
/cache 826M 102M 724M 4096
/persist 7M 4M 3M 4096
/firmware 63M 42M 21M 16384
/storage/sdcard0 12G 8G 3G 4096
I don't think there is more space that you can easily reclaim from the operating system. If you want more space, get a SD card.

mahler47 said:
Your operating system (CM10) takes up more than the 150MB download would suggest.
If you try "df" from shell, you'll see how your 16GB is partitioned. Here's what I got when I did it.
Filesystem Size Used Free Blksize
/dev 814M 52K 814M 4096
/mnt/asec 814M 0K 814M 4096
/mnt/obb 814M 0K 814M 4096
/system 1G 428M 1G 4096
/efs 13M 4M 8M 4096
/data 12G 8G 3G 4096
/cache 826M 102M 724M 4096
/persist 7M 4M 3M 4096
/firmware 63M 42M 21M 16384
/storage/sdcard0 12G 8G 3G 4096
I don't think there is more space that you can easily reclaim from the operating system. If you want more space, get a SD card.
Click to expand...
Click to collapse
What confuses me then, is that (I believe) TouchWiz is a larger ROM and comes with A LOT of bloatware, so how is it that I had more internal storage space back on the stock ROM?

You can download apps in the store that show you the space each folder takes up. Use one of them. They are more useful than any terminal commands because you can easily see the sub-folders in big folders which shows you where space is being wasted.
For example, in my apps folder, there was a large amount of Economist magazines downloaded which were taking up tons of space.

skomes said:
You can download apps in the store that show you the space each folder takes up. Use one of them. They are more useful than any terminal commands because you can easily see the sub-folders in big folders which shows you where space is being wasted.
For example, in my apps folder, there was a large amount of Economist magazines downloaded which were taking up tons of space.
Click to expand...
Click to collapse
Is there any specific app you recommend?

Kapak13 said:
Is there any specific app you recommend?
Click to expand...
Click to collapse
Disk Usage

Thank you! That is exactly what I was hoping to come across. I also just tried SDMaid, seems to be helping

I figured out what my problem was...
I used SDMaid to look at my "biggest" files and found that I still had about 6 of the Cyanogenmod nightlies zips still on my phone.
But now i have one further question, I have clockwork mod and I see a BUNCH of backups and files dealing with clockwork mod, each are around 25MB, I see 4 that are blobs, and 3 backups. How can I tell which ones are outdated? Or do I need to keep them all?
EDIT: I found even more blobs and backups but they are around 10MB.. Anyone know what to do?
And I also have 2 camera apps.... 120MB-VID_20121115_212426.mp4 /storage/sdcard/DCIM/camera/ and 74.33MB- VID_20121115_212425.mp4 /storage/sdcard/DCIM/camera/

This was the first device I had where cwm backed up in blob format. I changed the advance settings for backup format to tar and it resolved that issue
Sent from my SAMSUNG-SGH-I747M

mymusicathome said:
This was the first device I had where cwm backed up in blob format. I changed the advance settings for backup format to tar and it resolved that issue
Sent from my SAMSUNG-SGH-I747M
Click to expand...
Click to collapse
What did you use to change the advanced settings for backup format? ROMmanager?
EDIT: nevermind hahaha i figured it out. Went into CWM and found the advanced settings. Thank you!

was nndiro
mymusicathome said:
This was the first device I had where cwm backed up in blob format. I changed the advance settings for backup format to tar and it resolved that issue
Sent from my SAMSUNG-SGH-I747M
Click to expand...
Click to collapse
OK, so now that I've backed it up in tar format, can I now delete all the other backups? Should I keep the original cyanogenmod 10 zip on my phone? And can I delete ALL the backups, then make fresh backups without compromising my phone?

All Is Well
AH HA!!! I've done it!!! I went into clockwork mod recovery and went to advanced settings, changed the backup format to tar, made a backup. then rebooted phone and went into SDMaid, and went to the file explorer and found the "clockwordmod" folder, opened it up, found "backup", then deleted everything EXCEPT the latest backup I made with the tar format. Then I backed up all my photos onto dropbox and I'm currently deleting the photos and vids from my phone. now I have 10.61GB free!!!
Thank you all for helping me!

Gotta ask, did ur phone feel slow or something when u had 7gb free? Does it feel snappier now? I have had my memory down to 2gb and it still flew and was as smooth as when I have 9g of storage left. It makes no difference short of visually, but whatever crumbles ur cookies
Sent from my Nexus 7 using xda premium

Kapak13 said:
AH HA!!! I've done it!!! I went into clockwork mod recovery and went to advanced settings, changed the backup format to tar, made a backup. then rebooted phone and went into SDMaid, and went to the file explorer and found the "clockwordmod" folder, opened it up, found "backup", then deleted everything EXCEPT the latest backup I made with the tar format. Then I backed up all my photos onto dropbox and I'm currently deleting the photos and vids from my phone. now I have 10.61GB free!!!
Thank you all for helping me!
Click to expand...
Click to collapse
the questions you had and what you found out was just what i was going to ask about haha!
so changing clockwork settings to tar will make a folder for each backup instead of dumping some stuff into "blobs"?
from what i understand (i could be wrong?) CWM dumps essential files into blobs and backups up the "changes" into the backup folder so if you make a few backups with the same ROM/kernel, it won't have to take as long or take as much disk space

+1 for Disk Usage

Kapak13 said:
AH HA!!! I've done it!!! I went into clockwork mod recovery and went to advanced settings, changed the backup format to tar, made a backup. then rebooted phone and went into SDMaid, and went to the file explorer and found the "clockwordmod" folder, opened it up, found "backup", then deleted everything EXCEPT the latest backup I made with the tar format. Then I backed up all my photos onto dropbox and I'm currently deleting the photos and vids from my phone. now I have 10.61GB free!!!
Thank you all for helping me!
Click to expand...
Click to collapse
I store my CWM backups in the default blob format, "dup" I believe it's called. I keep my older unneeded backups cleared out but have noticed blob files remain.
In looking at the backup settings, I saw the option to remove unneeded backup data. Just tried it and freed several GB of space that was being used by obsolete blob data.
This clears the space without changing backup format.
Thanks for giving me the nudge that made me take a look and figure this out!

Please read forum rules before posting
Questions go in Q&A
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator

bbgt2 said:
Gotta ask, did ur phone feel slow or something when u had 7gb free? Does it feel snappier now? I have had my memory down to 2gb and it still flew and was as smooth as when I have 9g of storage left. It makes no difference short of visually, but whatever crumbles ur cookies
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
It wasn't so much speed as it was having all the space I should have. I had files everywhere and folders galore so it was slower to navigate.

phasion said:
the questions you had and what you found out was just what i was going to ask about haha!
so changing clockwork settings to tar will make a folder for each backup instead of dumping some stuff into "blobs"?
from what i understand (i could be wrong?) CWM dumps essential files into blobs and backups up the "changes" into the backup folder so if you make a few backups with the same ROM/kernel, it won't have to take as long or take as much disk space
Click to expand...
Click to collapse
Well being that I'm brand new at all this since coming from my iPhone modding days, I'm not really sure what I was looking at or dealing with. I just went into cwm and set the backup to tar and let it run, then when I went back into sdmaid I saw it was a file that was around 160mb where the original was 150mb but then had all the extra files not in the main folder. So it could have been the same. So since I only saw the one folder for the tar version, I knew everything was in one spot, in a 160mb folder. I then deleted all the other stuff to free up the internal storage and I was good to go. What have I really truly done? PSH, no clue. But its working still haha. I'm tempted to go back in cwm and do one normal backup with all the blobs just in case...

bsam55 said:
I store my CWM backups in the default blob format, "dup" I believe it's called. I keep my older unneeded backups cleared out but have noticed blob files remain.
In looking at the backup settings, I saw the option to remove unneeded backup data. Just tried it and freed several GB of space that was being used by obsolete blob data.
This clears the space without changing backup format.
Thanks for giving me the nudge that made me take a look and figure this out!
Click to expand...
Click to collapse
Haha yeah, I just can't sleep at night knowing that I don't know everything that's going on in my devices. And this is still brand new to me so when I saw I was low on memory and getting "error low memory" messages and couldn't install any apps, I snapped and signed up here and posted this thread. Thank you for reading and I'm glad it helped you out.
And speaking of the "error low memory" or more accurately, "insufficient storage available", I found the cure...
Download the app called LuckyPatcher, open it up, click the menu and click troubleshooting, then click the "remove fixes and backups" then you're done.

SD card location screwed after flashing ROM

Hey guys
let me give you some background informatie as to what happend
I went on a flashing spree today and I bumped into something irritating!
I've flashed JBSourcery V4.5 but it didn't satisfy my personal needs (didn't have some mods that I liked).
So back into recovery, factory reset, cache wipe... all the standard cleaning stuff. Next on my list was
LiquidSmooth and that's where my problem started. I was in recovery, wiped the lot and wanted to flash
LiquidSmooth which was already on my SDcard (I came prepared ) So I chose "Install ZIP from SD" and
my heart skipped a beat. Normally I'd see all my folders on my SD... Now I only saw "0", "Legacy" and "obb".
I kept my cool and opened each one untill I found my SD contents which where stuffed into the "0" folder.
No big deal... I could flash LiquidSmooth so everything was fine. Next one was XenonHD. Still same problem
but I could flash my stuff.
Long story short, how do I get my internal memory back to how it was?
Something on a side note though, It's only like that in recovery. If I connect my phone via USB it's normal. (Samsung Galaxy Nexus -> Internal Memory -> ...)
Ideas are welcome!
Thanks in advance! :good:
diSke

Move them with Root Explorer or hook it up to the comp and move them. Or check out some of the other threads about the /0/ folder, there are allot of them.

WiredPirate said:
Move them with Root Explorer or hook it up to the comp and move them. Or check out some of the other threads about the /0/ folder, there are allot of them.
Click to expand...
Click to collapse
Oh great... and I added one to the lot... Sorry guys!
Didn't think of searching with the "0" folder as keyword.
Thanks though for the reply and solution!
One quick question, do you know if the "Legacy" and "obb" folders are important?

I'm sure they are significant for some reason, but I am unsure of their specific purpose. I would for sure keep them in tact.

Hmmm... I moved them and now all my sd card files are scattered around...
Some in legacy, some in "0", some in media... probably best to wipe the lot and start from scratch?

From another post about Android 4.2's filesystem setup:
Cilraaz said:
Source: init.tuna.rc
Code:
on init
# See storage config details at [URL="http://source.android.com/tech/storage"][COLOR=#0066cc]http://source.android.com/tech/storage[/COLOR][/URL]
mkdir /mnt/shell/emulated 0700 shell shell
mkdir /storage/emulated 0555 root root
export EXTERNAL_STORAGE /storage/emulated/legacy
export EMULATED_STORAGE_SOURCE /mnt/shell/emulated
export EMULATED_STORAGE_TARGET /storage/emulated
# Support legacy paths
symlink /storage/emualted/legacy /sdcard
symlink /storage/emualted/legacy /mnt/sdcard
symlink /storage/emualted/legacy /storage/sdcard0
symlink /mnt/shell/emulated/0 /storage/emulated/legacy
[...]
# virtual sdcard daemon running as media_rw (1023)
service sdcard /system/bin/sdcard /data/media /mnt/shell/emulated 1023 1023
class late_start
[...]
Click to expand...
Click to collapse
You said which ROMs you flashed, but what version of Android are you on now? It sounds like you might be back on 4.1.x, since you're seeing 0, legacy, and obb in /sdcard.
If you went back to 4.1.x, then 0, legacy, and obb are not important. Only /data/media matters on 4.1.x. If you are on 4.1.x, go to /data/media/0 and copy all of the files there to /data/media, then reboot. That will fix your setup. Once that's done and 0, legacy, and obb are all empty, they are safe to delete.
If you are on 4.2 or 4.2.1, then the above quote is accurate. Your information should be in /data/media/0 and the system should be properly fuse mounting and symlink'ing to showyour data into /sdcard.
When moving files around, it's usually best to do it at the source (within /data/media) so you don't have to worry about the fuse mounts and symlinks causing a problem.

I switched from 4.1 to 4.2.1.
Problem is I started switching things around and now my sd card files seem te be everywhere.
Can't figure out what is what...
I moved everything from "data/media/0" to "data/media"
but now my system can't find my files.
When I try to move everything back it says "unable to execute the command"

diSke said:
I switched from 4.1 to 4.2.1.
Problem is I started switching things around and now my sd card files seem te be everywhere.
Can't figure out what is what...
I moved everything from "data/media/0" to "data/media"
but now my system can't find my files.
When I try to move everything back it says "unable to execute the command"
Click to expand...
Click to collapse
As my post said, if you're on 4.2.1, your files should be in /data/media/0. You'll see copies of them in multiple places (/storage/emulated/legacy, /sdcard, /mnt/shell/emulated/0, /mnt/sdcard, /storage/sdcard0, and /data/media/0), but these are fuse mounts and symlinks. Your data only "physically" exists in one place: /data/media/0. After rebooting, your files should be found in /sdcard, rather than /sdcard/0. If not, then you might have the multiple 0 folder issue (e.g. /data/media/0/0/0, which ends up being /sdcard/0/0) from having an outdated version of your recovery.
Long story short, if you're on 4.2.1, then any files from your "SD Card" should be found in /data/media/0. If you're on 4.1.x, then they should be in /data/media.
If you're getting that error when trying to copy from /data/media to /data/media/0, then you'll need to check that /data/media is mounted as r/w and that you have write permission to the 0 folder within it. You should also be copying these files around as root (either through terminal emulator or a root file browser like Root Explorer).

Cilraaz is correct, however if you are looking for an easy way to straighten it out you can do the following.
Copy everything you want to save to the computer.
Reboot into recovery and format data. (Not wipe data actually format.)
Reboot phone and data partition will be good to go again.
Copy files back from computer and you should be as you were previously.
Of course all other data will be gone but I'm sure if you are a crack flasher you can get all that back.
G-Nexus Sent

ifly4vamerica said:
Cilraaz is correct, however if you are looking for an easy way to straighten it out you can do the following.
Copy everything you want to save to the computer.
Reboot into recovery and format data. (Not wipe data actually format.)
Reboot phone and data partition will be good to go again.
Copy files back from computer and you should be as you were previously.
Of course all other data will be gone but I'm sure if you are a crack flasher you can get all that back.
G-Nexus Sent
Click to expand...
Click to collapse
Good call on the computer backup. You don't need to wipe data, though. Just backup what you want to save from storage to your computer, then flash userdata.img from the stock 4.2.1 ROM, which will wipe out and re-create the /data/media partition. Then when you reboot, the fuse mounts and symlinks will be properly recreated and you can use MTP to copy your data back (or adb push it to /data/media/0 or /sdcard).

Thanks guys.
Fixed it differently though, Completely wiped everything again and started from scratch.
Made a backup earlier of everything I wanted to save except for messages which I forgot (damnit)
But it's all good now

Please read forum rules before posting
Questions go in Q&A
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator

system partition at 100%

Does anyone else have this problem? I'm currently at 100% on my system partition running freedomos

slaya811 said:
Does anyone else have this problem? I'm currently at 100% on my system partition running freedomos
Click to expand...
Click to collapse
While installing try to avoid as many gapps as u can, u can install them later. I selected them all and it didn't boot for me.
Sent from my ONEPLUS A5010 using Tapatalk

[email protected] said:
While installing try to avoid as many gapps as u can, u can install them later. I selected them all and it didn't boot for me.
Click to expand...
Click to collapse
I've tried that as that was the only way I could get through the installation. What is your system partition at right now?

How to check that, I'm on OOS right now, twrp installed.
Sent from my ONEPLUS A5010 using Tapatalk

[email protected] said:
How to check that, I'm on OOS right now, twrp installed.
Click to expand...
Click to collapse
In a root browser file manager look for root storage or system partition

Like this

Mine is @96%. How does this affect my system?

[email protected] said:
Mine is @96%. How does this affect my system?
Click to expand...
Click to collapse
For me I can't install certain things like Xposed it says there is no room for it

Anyone on the stock oos know what their system partition is?

I assume it must be possible to make room in /system by deleting apks that have been updated in /data.
I have done so in the past with certain tools (need root), for example systemcleanup. However I am not sure which tool, today, would be best to specifically know what can be removed on oos (libs and dex and dalvik). Any suggestion is welcome.
Note: my /system is not full but I simple wonder what the experts might advice.

Dior DNA said:
I assume it must be possible to make room in /system by deleting apks that have been updated in /data.
I have done so in the past with certain tools (need root), for example systemcleanup. However I am not sure which tool, today, would be best to specifically know what can be removed on oos (libs and dex and dalvik). Any suggestion is welcome.
Note: my /system is not full but I simple wonder what the experts might advice.
Click to expand...
Click to collapse
Using Link2SD (or other tool) I spot >100MB System WebView apk to be frozen in system.
Can someone confirm it is safe to delete WebView apk (root required) from /system?
Similarly many (17) Gapps in system are updated. I guess I can delete the system apk's as well
(say for big apps that are not needed for Play Store). Notably Chrome is >100MB too.
Can someone confirm it is safe to delete Chrome apk (root required) from /system?

Dior DNA said:
Using Link2SD (or oher tool) I spot >100MB System WebView apk to be frozen in system.
Can someone confirm it is safe to delete WebView apk (root required) from /system?
Similarly many (17) Gapps in system are updated. I guess I can delete the system apk's as well
(say for big apps that are not needed for Play Store). Notably Chrome is >100MB too.
Can someone confirm it is safe to delete Chrome apk (root required) from /system?
Click to expand...
Click to collapse
Chrome, sure. Webview I would not delete

Dior DNA said:
Using Link2SD (or oher tool) I spot >100MB System WebView apk to be frozen in system.
Can someone confirm it is safe to delete WebView apk (root required) from /system?
Similarly many (17) Gapps in system are updated. I guess I can delete the system apk's as well
(say for big apps that are not needed for Play Store). Notably Chrome is >100MB too.
Can someone confirm it is safe to delete Chrome apk (root required) from /system?
Click to expand...
Click to collapse
It's frozen so it's not in use, same as on my system. I deleted it as it's in play store if I need it again but it didn't make a difference to my system partition storage at all, I still only have 81mb free. I also backed up with titanium backup.

I went ahead and deleted Chrome and WebViewGoogle directories from /system/app ...
There may be some libraries I could also have deleted. I don't know.
I saved few 100M in /system (and 1 file in dalvik-cache).
I made system TWRP backup first.
Code:
OnePlus5T:/data/root # cd /system
before:
Code:
OnePlus5T:/system # df -k .
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/block/bootdevice/by-name/system
2999516 2859676 123456 96% /system
after:
Code:
OnePlus5T:/system # df -k .
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/block/bootdevice/by-name/system
2999516 2621784 361348 88% /system
Have a nice day

Dior DNA said:
I went ahead and deleted Chrome and WebViewGoogle directories from /system/app ...
There may be some libraries I could also have deleted. I don't know.
I saved few 100M in /system (and 1 file in dalvik-cache).
I made system TWRP backup first.
Code:
OnePlus5T:/data/root # cd /system
before:
Code:
OnePlus5T:/system # df -k .
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/block/bootdevice/by-name/system
2999516 2859676 123456 96% /system
after:
Code:
OnePlus5T:/system # df -k .
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/block/bootdevice/by-name/system
2999516 2621784 361348 88% /system
Have a nice day
Click to expand...
Click to collapse
Hi all
I have no good explanation (expect from android.webkit.WebView logcat Errors),
but I would discourage to remove frozen WebViewGoogle.
It leads to random app crashes on my 1+5T ... so I restored /system (and SuperSU).
Removing Chrome turns out to not be a problem.
Have a nice day

[Dumpsys] - mrdump_preallocated - what is it for? can it be deleted?

Hey all,
Since that file is making my backup restores to fail, I had been wondering what is it for and if that can be safely deleted?
It is quite huge tbh, and increase considerably backup sizes.
Being very close in size to the total ramsize I wonder if that would not be something like a ram dump of some kind, generated upon error or to start OS faster, some kind of hibernate.sys maybe.
Code:
begonia:/data/vendor # ls -lah dumpsys/
total 2.8G
drwxrwxr-x 2 system system 4.0K 2020-07-21 20:33 .
drwxrwx--x 39 root root 4.0K 2020-07-28 13:19 ..
-r-------- 1 root root 5.6G 2020-07-28 10:00 mrdump_preallocated
Since it makes my TWRP backup restore fail, I wonder if I could safely delete it either prior backup or from backup archive itself so restore does not fail.
Technically when restore fail on that file which is quite at the end of the backup, it kind of success restoring everything anyway, still some files are probably missing and I dont like errors.
If any of you know about this file, please let me know.
Thank you.
Regards!