I upgraded my LG G2 android software to Lollipop a couple of days ago, and i have just rooted it successfully few hours ago. I am trying to convert Cerberus app to a system app which i actually succeeded when i still had Kitkat. Now that i have Lollipop, i cant seem to convert it anymore. Do any of you have any idea how to solve this within Link2SD app?
The error was "/system : not enough storage space". I tried to uninstall a system app to free up some system space and it did. But when i tried to convert Cerberus app again which has a size smaller than the available system space, failed again with the same error message. I checked the system storage info and surprisingly, there is no more system spaces left. What has just happened? I tried deleting another system apps again and did the same thing but still no go. Seems like something made my available system storage to be used up without any reason. Now i have a messed up software with full system space :S
I have attached a screenshot of Link2SD storage info. By the way, why does it say i only have a max of 2.66GB of system space? How can we increase that?
Thanks in advance for all your help!
Can you install Terminal Emulator from play store, open it, and run the command
Code:
dd
Or if you have got adb set up, you can also use the command
Code:
adb shell dd
And post here the screenshot (or readable output of any kind)? Because from screenshot, its showing that your /system partition is filled up. But running above command should clear scope for any confusion/reading bugs.
For increasing the space, you will have to repartition (since I dont have an LG phone, I cant provide much info on how to do this). And the end result would be something like-> your user-usable memory will decrease and the system usable memory will increase. In other words, you would be shrinking your /data partition and increasing size for /system partition.
Related
I am trying to make a script that will remove the dex files for apps that have not been used in a "long" time, thereby making free space.
I just went through the "/data/data is full, apps force closing lots" again.
I did the "wipe dalvik" "fix"... but I'd like to do 2 (3?) things better.
1. Not install another app just for this. I have Tasker. I don't need/want another.
2. Free space by removing dalvik files that are old, instead of just using "rm -f *".
3. Accomplish this apparent feat of magic without having a list of "you need to install this, this and this."
What is particularly "painful" is that the solution is SUPER simple.
Code:
find /data/dalvik-cache -atime +14 -delete
EXCEPT that BusyBox does not include the "-atime" (last accessed time) option. Only last modified time (-mtime) is supported, and I that's not going to have the affect I want.
I ran "ls -lu /data/dalvik-cache" (u=order by accessed time), but the displayed times can't be correct. I emptied the directory ~9/1/2012. Now, there are files showing dates back into 2011. !?!??!!? How is that possible????
Hi
Since ever I noticed a weird thing on XMP: /cache partition is always almost empty.
Yes, I checked many times during a long time, it's like is never used.
Code:
$ df
/cache 101.5M 1.1M 100.4M 4096
I have only an empty lost+found dir and two files under recovery dir:
Code:
# ls
-rw-r--r-- root root 105 2012-12-15 02:07 last_install
-rw-r----- root root 3214 2012-12-22 10:36 last_log
For example, in a previous phone /cache was actively used by market for downloading packages before installing them.
Here on XMP I can't upgrade also small packages (40+ megs free on /data) 'cause they're downloaded in /data and fill it before being upgraded, and /cache remains always empty.
In addition, if for some reason playstore crashes while downloading a big app (30megs+), it leaves my /data (almost)full and I must remove by hand a large temporary file from /data/system.
Well, /data is used instead of /cache, 100mb wasted in this way.
Someone else finds experiences the same behaviour?
I was thinking about a linking trick to use that space (for dalvick or swap...), but I'd prefer it would be correctly used by system.
Infos: SK17i, stock .587, root, locked BL, link2sd.
Thanks, bye.
Same in Xperia Mini
Well, this isn't nice...
some ideas
Hello! I was doing several searches and come to some results:
Note: I will not try it on my phone (Xperia Mini Pro) because I'm still an apprentice to flash and modify it, and secondly I have no resources to change my phone if something goes wrong. Finally, sorry for the grammatical errors, I do not speak English natively.
The following are links taken from different forums / blogs (neither is my property).
The general idea is the same, use parted (or any similar app) to edit the partitions inside the phone.
One of the problems that arise and I have doubts about is, what is the file system of internal partitions? ext3?. is something that I have to keep reading.
This is the first blog I found where it gives a possible procedure to follow:
http://aarondiep.blogspot.com.ar/2011/11/resize-partition-on-android.html
Here's a post where one of the users that modify his partitions and, later, returned to stock status.
http://www.droidforums.net/forum/htc-droid-eris/78650-internal-storage-partitions-screwed-up.html
Here is a guide on how you use parted (includes screenshots) BUT IT DOES WITH THE SD CARD
http://mobilecon.info/how-to-partition-sdcard-using-parted-partition.html
Finally, a tool for YAFFS2 file system:
http://forum.xda-developers.com/showthread.php?t=1645412
I hope these links are useful. I really would like to use optimally all the hardware of the phone.
Exitos!! :laugh:
Hi!
Thanks for your interest!
Resizing partitions, I read time ago, is a really critical operation.
I expect to have /cache partition as it has been made, the problem is that apps do not use it!
Resizing that block device to, let's say, zero, would give space to other partitions, but we'd lack a cache.
I definitely believe one of master questions is: where the hell does playstore download packages before installing?
During a big upgrade (let's say angry birds Rio 30+ megs) with df I only see /data growing (and /cache always empty), but after a lot of searching for newest and biggest files (busybox ls -ltrh, busybox ls -Shl) I could not find where they are put.
Once found this download location (no, it's not /data/data/com.android.vending/cache/main), would be easy to bind /cache to this dir.
Apk files from Google Play is downloaded to: data/data/com.android.providers.downloads/cache/
Wysyłane z mojego SK17i za pomocą Tapatalk 2
Hi
Many thanks for this tip!
Well, it's true apk are downloaded there.
BUT I see a strange behaviour: when I recieve the "low memory" (space on /data partition) notification, the apk suddenly disappears! :what:
In logs I see a lot of "couldn't openat chache: no such file or directory" immediately before low space notification log line...
You can use cache as swap if your kernel support it..
Sent from my Walkie'Talkie
Hi
Well, i symlinked /data/data/com.android.providers.downloads/cache to /cache/cache, and the partition is now correctly used by play store.
Is really strange that this is not a system default, btw.
EDIT: the /cache/cache was regularly erased by system, I symlinked /data/data/com.android.providers.downloads/cache to /cache and all is ok now.
EDIT2: you must previously remove (rmdir) the existing /data/data/com.android.providers.downloads/cache!
Could you put the exact command?
luchoz said:
Could you put the exact command?
Click to expand...
Click to collapse
Code:
ln -s /data/data/com.android.providers.downloads/cache /cache
:good:
thank you!!
would use XD
New info!!
http://forum.xda-developers.com/showthread.php?t=1959691
Really interesting
Hi there!
First of all excuse my bad English. I learned this language several years ago. But let me have a try to tell you about my problems:
I’m a proud owner of a Samsung Galaxy Ace 5830i. Before using this device I’ve been a real Apple nerd (shame on me) but now I’m proselytized completely.
However I’m facing a difficulty now. I tried to increase my internal memory, but it doesn’t work.
I’m actually running this custom firmware:
http://forum.xda-developers.com/showthread.php?t=2778000&nocache=1
And I‘ve tried all the solutions mentioned here:
http://www.droidthunder.com/increase-internal-memory-android-phone/
All of them are causing error messages – as a sample the Terminal Emulator App is telling me „a2SD“ is not found. And Link2SD seems to be working – but after receiving about 15 messages the device tells me the storage is full.
I’ve installed SuperUser and Clockwork Recovery for sure…
As I know myself as a little dopey, I’m sure it’s my own failure –but I can’t find it. So please help me!
I’m absolutely certain you need further information –so just let me please know what you exactly need.
Stollentrolle said:
Hi there!
First of all excuse my bad English. I learned this language several years ago. But let me have a try to tell you about my problems:
I’m a proud owner of a Samsung Galaxy Ace 5830i. Before using this device I’ve been a real Apple nerd (shame on me) but now I’m proselytized completely.
However I’m facing a difficulty now. I tried to increase my internal memory, but it doesn’t work.
I’m actually running this custom firmware:
http://forum.xda-developers.com/showthread.php?t=2778000&nocache=1
And I‘ve tried all the solutions mentioned here:
http://www.droidthunder.com/increase-internal-memory-android-phone/
All of them are causing error messages – as a sample the Terminal Emulator App is telling me „a2SD“ is not found. And Link2SD seems to be working – but after receiving about 15 messages the device tells me the storage is full.
I’ve installed SuperUser and Clockwork Recovery for sure…
As I know myself as a little dopey, I’m sure it’s my own failure –but I can’t find it. So please help me!
I’m absolutely certain you need further information –so just let me please know what you exactly need.
Click to expand...
Click to collapse
First of all do please explain all of the instruction(s) you did take from step one , rather than directing us to some general external links method .
Your custom rom comes pre-rooted with su app as i gathered and binary update installed , so i didn't get the part about installing stuff and please clarify the process you went through for play store an Gapps installation as com.android.vending-5.2.13-80321300-minAPI9.apk was omitted from system/app of your TWR v2.5 . ( post #270 my comment )
If you got any root explorer installed please give me what you see under /system/etc/init.d folder of your device ( you can also install terminal emulator and give me the following output command is generated >> "ls -l etc/init* " & type "su" to get elevated and then type " df" for now and FYI there are two method for increasing your internal space : 1-link2sd free version from play store and 2'; universal script method which is a bit complicated but does not require app linking method such as link2sd app .
On the side note though , If I am not mistaken TWR v 2.5 is heavily customized , therefore few MB of space will be remained under /System partition . You need to re-partition your external device through clock work mod and install link2sd app from play store to increase internal memory space , or use cronmod script which is a bit complicated . ( upon re-partitioning , all of your external SD card data will be erased , so back up your critical data ) . I need those output i requested to be any assistance to your cause , but this is a general guideline anyway :
Link2sd instructions :
1- Uninstall any new app you have downloaded through your built -in application manager or from play store/my app section ( before that unlinked then through link2sd , if you created link2sd connections ) . Delete any .apk file leftover within your Download folder , accessible through your built-in file manager ( root explorer /es file explorer will do).
2. assuming you are familiar with your custom recovery console ( a.k.a : CWM ) , turn off your phone and push the hardware combo key to get to your CWM :
3. Go to advanced>partition SD card>choose size ( 1024mb)
4. After that( ext4 or ext2 will be created upon entering 1024 Value , depend oc the CWM version and kernel you are using ), then choose 0mb as swap partition and continue .
5. After this is done go to mount and storage and format sd-ext there (back up your sensitive data as you will loose them ).
6, Reboot your device .
7. open up your internet browser and search for " free link2sd app from play store " , if you can't find it directly over play store search function and install the app.
8. Open up the app , you will asked to choose your sd-ext partition format : pick ext4 or ext2 ; if you got any script error , then from top left corner menu , choose recreate mount script and pick ext2 , if ext4 generated mount error .
9. from top right corner menu , choose multi-select > push on the option on toolbar or select your apps > push on three vertical dots from top right again and this time choose link to sd card > all of the app selected by link2sd or hand picked by you will be transferred to /sd-ext partition plus some other technical stuff .
10. now back to the first page and from top left menu , choose storage info : you must see something like :
Internal
SD card
SD Card 2nd part
System
Cache
spaces , from now on , your limited internal will remain at the fixed ratio and your /mnt/sdcard and /data/sdext2/4 will be involved with apk data and library and app cache
Soft rebooted from top left corner menu of link2sd in order to become effective .
So basically, twrp recovery was not mounting my internal memory(phone was perfectly working) and I made the crucial mistake of not backing up my stuff before following a guide to fix it which consisted going in twrp recovery and repairing/changing system files. That resulted in everything being gone. Now, i used my phone as little as possible and have tried using phone recovery programs like dr.fone without any success. I've tried by following this answer here: https://stackoverflow.com/a/41397418 and I got a mmcblk0p66.raw file which is userdata after i used the commands and is around 55gb and the whole mmcblk0.raw file itself which is around 61gb. All this by forwarding from a cygwin64 terminal to another cygwin64 terminal through adb.
Code:
adb shell
ls -al /dev/block/platform/*phoneSpecificFolder*/by-name
I've tried mounting it with osfmount and then using recovery programs and using linuxreader to mount it and no success. I'm baffled how this 55+ GB files contain either empty folders or no files found and such. Am i doing something wrong or is it just me that actually STUPIDLY deleted everything? Also, I would do
Code:
adb shell
su
dd if=/dev/block/mmcblk0p65 of=/sdcard/userdata.img
but I would effectively overwrite any remains of files left due to it being 55gb in space. Much thanks. Every answer is appreciated.
Note: I mainly care about recovering my photos,videos
Xiaomi Mi Max 2 64BG
This may be a little complicated but here is the basic gist:
1. Android 2.1 (B&N Nook Simple Touch)
2. I backup the dictionary files in /system/media/reference and then delete the originals. This shows a corresponding increase in the available space in /system
3. I create a symlink to alternate dictionary files in /sdcard/Dictionary (or /data/media/B&N Downloads/Dictionary--same result either way)
4. After rebooting I have access to new dictionary. Then I change my mind and want a different dictionary.
5. I delete the symlinks in /system/media/reference
6. I create new symlinks to a different dictionary, reboot, etc.
7. Now I get tired of all this and want to return to the stock dictionary.
8. I delete the symlinks in /system/media/reference and prepare to copy the stock backups to their original location.
BUT
9. I see that there is no longer enough space on /system to restore the original files! As an example, the stock available space in /system is 55906 kb (80% full--that's with the dictionary files in their normal place). After a few symlink cycles it may drop down to something like 30359 kb (89% full). Restoration of the stock dictionary requires about 57000 kb available space.
Blah-blah-blah. I've done this many times now, each time searching diligently for what is taking up the space that should be free. The only way to get the space back is to restore an earlier nandroid backup.
Surely this is not supposed to happen with symlinks? To delete one I am using adb shell rm. Is there something else I should be doing?
Why does the use of symlinks in /system gradually erode available space?
I am working on a routine for swapping dictionaries on an e-reader (Nook Simple Touch--Android 2.1). I've got the shell commands nailed down and have constructed an app using Tasker. It all works g...
android.stackexchange.com
Yep, and I did see your comment which turned out to be really helpful, @alecxs! I've solved the problem and answered my own question over at Stack Exchange.
The key is to kill the background process which is holding on to the dictionary databases before doing any file manipulations. If that is done, everything works as it should and no funny /system storage losses.
Thanks so much for nudging me in the right direction.
don't thank me, I had something different in mind. but yes, reading your answer remind me some strange behavior in 5 years old backup script:
after lazy umount + rm -rf /data still there was ~1GB disk space occupied.
this is because deleted files remain open for running processes, just the inode becomes orphaned.
killing system_server immediately freed up these 1GB and solved for me. lsof is your friend