Is there any way to prepare a Gapps like package with additional apps of choice (any app i want to be installed) and install them after ROM into system partition?
If i install a debloated Gapps i end up with 3/4 of unused system partition which will not be used in the future-it is a space wasted. resizing partitons is dangerous if i have to use backups. If it would be possible to install apps of choice into the system partition then i could use up system partition space and use userdata space for other stuff. Of course app updates of apps installed into system partition should be installed/stored in system partition too.
Thank you
Personally never would abuse /system partition to store user-apps there.
xXx yYy said:
Personally never would abuse /system partition to store user-apps there.
Click to expand...
Click to collapse
Why if 3/4 of space is unused? Could you let me know if you are familiar with dangers of it? thanks
Never encountered or heard of that 3/4 of storage space under /system is unused. My experince is that only some 100KB are free for further use ( updates ).
xXx yYy said:
Never encountered or heard of that 3/4 of storage space under /system is unused. My experince is that only some 100KB are free for further use ( updates ).
Click to expand...
Click to collapse
Isnt this system space on the screenshot system partition? Let me know if i am wrong. thank you
If phone's Android is rooted and its /system partition is mounted as RW then apply the du command in Android's terminal to get the disk space memory utilized by files in /system partition.
To get the unused disk space memory in /system apply the df command.
Related
I have the latest stock Gingerbread ROM, AmonRA, ROQ kernel and I'm unsing link2SD.
I'm getting short of space on my data partition and I would like to recover some space from my cache partition (that is now 64Mb big).
Is there anyway to move some Mb from /cache to /data?
Possibly recovering a whole NAND backup.
I saw scripts for "Cusotm MTD Partitions" but they all looked for different phones.
Thank you very much
pdario said:
I have the latest stock Gingerbread ROM, AmonRA, ROQ kernel and I'm unsing link2SD.
I'm getting short of space on my data partition and I would like to recover some space from my cache partition (that is now 64Mb big).
Is there anyway to move some Mb from /cache to /data?
Possibly recovering a whole NAND backup.
I saw scripts for "Cusotm MTD Partitions" but they all looked for different phones.
Thank you very much
Click to expand...
Click to collapse
u can't change internal partitions in p500. but u can change the size of SD-ext partition that link2sd uses to store apps. U can do that with the help of ur recovery. But remember that changing size of sd-ext partition will format ur whole sd crd. so make the necessary backups
Souron29 said:
u can't change internal partitions in p500. but u can change the size of SD-ext partition that link2sd uses to store apps. U can do that with the help of ur recovery. But remember that changing size of sd-ext partition will format ur whole sd crd. so make the necessary backups
Click to expand...
Click to collapse
I'm running out of space in /data partition, /sd-ext is ok.
I see I can nandroid backup all partitions: can't I edit them somehow and then recovery them back?
BTW: I would use a Windows partition resizing software on the SD mounted in my PC to do what you meant, that should not lose any data
pdario said:
I'm running out of space in /data partition, /sd-ext is ok.
I see I can nandroid backup all partitions: can't I edit them somehow and then recovery them back?
BTW: I would use a Windows partition resizing software on the SD mounted in my PC to do what you meant, that should not lose any data
Click to expand...
Click to collapse
when u backup ur partitions it just means u r backing up the content of ur partitions as a whole. So editing them won't do any good.
instead flash an app2sd script which moves dalvik cache to sd too. like this one. http://forum.xda-developers.com/showthread.php?t=1668247
My dalvik cache is already on SD, using LInk2SD; the problem is the /data content; it would be great to move the data to SD too
I also used link2sd till recently and switched to S2E (simple2ext) from the market but I think it only works for cm7 and cm7 based roms.
If you use a lot of apps including games I would suggest making the ext partition 1gb when using set script.
Backup your apps with titanium backup, wipe the phone clean, flash the rom.
Install S2E, open it.
Press menu key and go to Settings, and enable “Mount as ext4″ (mandatory).
Close and reboot.
Open S2E again and select the folders you want to move to SD card. I recommend selecting Applications, Application Data and Dalvik cache. Leave Private apps and Download cache unselected.
Reboot and changes will take effect. (This reboot will be slower than usual as your dalvik cache will be rebuilt.)
Done.
Now you can restore from the titanium backup and you shouldn't have any more problems with space.
p.s.: don't backup or restore link2sd, it will mess with s2e
You mean it will move the /data folders too, in contrary to Link2SD?
pdario said:
You mean it will move the /data folders too, in contrary to Link2SD?
Click to expand...
Click to collapse
Yes
Sent from my LG-P500 using xda premium
Is it correct that, in the steps you listed, the old sd-ext partition is not needed? S2E won't read it, right?
pdario said:
Is it correct that, in the steps you listed, the old sd-ext partition is not needed? S2E won't read it, right?
Click to expand...
Click to collapse
The sd-ext partition is very needed. that's where all your apps and data and dalvik cache will go. S2E works basically like Link2SD only it moves data as well, to the same place.
When I said wipe the phone, I meant formating the system, internal and ext partitions + dalvik cache so you have a clean slate and bug free installation.
Souron29 said:
when u backup ur partitions it just means u r backing up the content of ur partitions as a whole. So editing them won't do any good.
instead flash an app2sd script which moves dalvik cache to sd too. like this one. http://forum.xda-developers.com/showthread.php?t=1668247
Click to expand...
Click to collapse
Use the script mentioned here. it moves ur \data partition to ext. it will give u ample amount of storage. and remember that u should increase the size of ext partition only if u have class 6 sdcards or else ur phone will suffer serious lag
Sorry, I meant the content of the sd-ext partition before this upgrade: I have to reinstall all apps, I don't need the old installations in the sd-ext, right?
Thank you!
the g330 comes with a reasonable storage. But there is not enough space for apps on /data. The internal sd-card got a lot of space. resizing /data (part. 18) may be critical and requires another recovery image. So my idea is to log in the phone, start fdisk /dev/block/mmcblk0, delete internal sd-card partition (19), then create a e.g. 1 GB partition with ext4, which I will mount on /data/app, and give the rest to a new partition 20 for internal sd-card.
I think this approach is more fail-save and can be done quite fast. I have to change just init.rc to add one mount and vold.fstab. Has somebody tried this?
yes, i know, the dalvik-cache and /data/data will still load the /data partition, and app2sd would save the same space from /data. But app2sd needs one mount for each app (at least in GB), so booting takes very long time and I have to wait until I can launch an app.
I read sometimes, the kernel get the offsets of the partitions of flash as parameters when booted - so some offsets would be wrong when I change the partion table. This would cause to fail mount /data/app - what about this?
rregn said:
the g330 comes with a reasonable storage. But there is not enough space for apps on /data. The internal sd-card got a lot of space. resizing /data (part. 18) may be critical and requires another recovery image. So my idea is to log in the phone, start fdisk /dev/block/mmcblk0, delete internal sd-card partition (19), then create a e.g. 1 GB partition with ext4, which I will mount on /data/app, and give the rest to a new partition 20 for internal sd-card.
I think this approach is more fail-save and can be done quite fast. I have to change just init.rc to add one mount and vold.fstab. Has somebody tried this?
yes, i know, the dalvik-cache and /data/data will still load the /data partition, and app2sd would save the same space from /data. But app2sd needs one mount for each app (at least in GB), so booting takes very long time and I have to wait until I can launch an app.
I read sometimes, the kernel get the offsets of the partitions of flash as parameters when booted - so some offsets would be wrong when I change the partion table. This would cause to fail mount /data/app - what about this?
Click to expand...
Click to collapse
I tried this and it works
its for g300 but it works on g330
http://www.htcmania.com/showthread.php?t=428466
sorry, its in spanish haha use the google tranlator
xals1997 said:
I tried this and it works
its for g300 but it works on g330
http://www.htcmania.com/showthread.php?t=428466
sorry, its in spanish haha use the google tranlator
Click to expand...
Click to collapse
Did i get the idea? You use link2SD (from Bülent Akpinar) , but instead of using a 2nd partition of the external SD-card with ext2, you use the internal SD-card for link2SD?
But i heard that link2SD need a ext2/3 partition? Also, in my version of link2SD there is:
mount -t ext2 -o rw /dev/block/vold/179:2 ...
btw. how is /system/etc/install-recovery.sh triggered
I have a Galaxy Nexus with not much space left in the /system partition, which means that after I have flashed the Blackberry apps (~250M) I can't even flash Pico GApps.
Is it possible to symlink or mount a sub-directory (e.g. /system/priv-app) to a different partition to free space?
OK I'm sure some of you have at least run into this problem when installing gapps over a custom ROM and I can tell you how to fix it!
after flashing your custom ROM be in twrp and from the main screen select: mount>select system>press home button>wipe>advanced wipe>select system>click repair or change file system>resize file system>swipe to resize. After that you are almost done, go back to main screen and flash the gapps zip and congratulations you got gapps successfully installed, if any errors when booting or bootloops make sure you try this again EXACTLY how i said. If this helped you please hit the thanks button ?
error 70 = no enough storage
Storage is storage and full is full... In most cases /system is almost full. This partition contains your OS. The GApps installer.zip is not an image file! It installs single files and files need storage. If there is not enough free storage then you should delete some other apps.
Resizing doesn't make sense because for the additional new storage on /system you lost storage on another partition. In most cases userdata.
WoKoschekk said:
error 70 = no enough storage
Storage is storage and full is full... In most cases /system is almost full. This partition contains your OS. The GApps installer.zip is not an image file! It installs single files and files need storage. If there is not enough free storage then you should delete some other apps.
Resizing doesn't make sense because for the additional new storage on /system you lost storage on another partition. In most cases userdata.
Click to expand...
Click to collapse
When you install gapps it installs it to the os partition and as such makes sense as of why it's a system app. Besides this worked for me Everytime
Well, I tried it with my Nexus 5 and lineage 14.1, Gapps 7.1 Nano. Didn't work! Got the same old Error 70.
And the answer is .... use a gapps.config.txt file. You can include/exclude the packages you want in gapps. This reduces the size needed in the recovery partition so it will fit. If you want to know how much space you have to work with, open a terminal and as su, enter df -h and see what the system partition is using and how much free space you have.
Worked for me!
I have 16GB phone and wanted to do a full backup but it's size is 11768MB which I think should be more, look at the calculation:
it's 16GB phone (in decimal) which in binary is 14.9GB. (16000/1074) so main internal storage in digital computation is 14.9GB.
my system partition+data partition (shown in TWRP backup) are 11768MB. (9500 /data and rest is /system)
my internal storage: 868MB free + 1.36GB used (=2228MB)
all other partitions are 167MB (excluding data and system and sdcard)
so far it's 11768+2228+167=14,163MB
but my whole internal storage is 14,900MB and now whole things on my phone is 14,163MB, so where is that 737MB?
also apps cache and system cache are almost nothing and dalvik cache is 629MB (which I think is included in TWRP's /data calculation)
do you have any idea of missing 737MB? does TWRP exclude anything or am I wrong?
TWRP saves only those partitions that may change due to flashing custom ROM.
An example is the vendor partition.
ze7zez said:
TWRP saves only those partitions that may change due to flashing custom ROM.
An example is the vendor partition.
Click to expand...
Click to collapse
yes I know and I calculated whole partitions and SDCARD and TWRP system and data and free storage and everything but the size isn't same as device internal storage space (you can look at my calculation above)
If you want you can always save a disk and not the partitions.
You won't be able to flash it with fastboot (I don't think), but if you have EDL or its equivalent you can.
Renate said:
If you want you can always save a disk and not the partitions.
You won't be able to flash it with fastboot (I don't think), but if you have EDL or its equivalent you can.
Click to expand...
Click to collapse
it's not about backing up, it's mostly because of my curiosity that why when I have root and calculated whole stuff (partitions) plus cache plus free space, altogether they don't fit my internal disk space (14.9GB) and are 737MB less!!! can you test it on your phone and see what will be the result.
I really have no idea what we are discussing.
Code:
Poke3:/ # dd if=/dev/block/mmcblk0 of=/dev/null
61071360+0 records in
61071360+0 records out
31268536320 bytes (29 G) copied, 209.698476 s, 142 M/s
I don't use TWRP.