Well I installed the CronMod script with a 2GB partition for it. But with only 400 MBs of apps the system displays, the "there is no more space in the system" message, I've checked the Partition Info located in about and indeed the /system partition is full, can someone guide me in the right direction to what have you achieved with CronMod?
Related
Hello,
After several problems with S2E and apps disappearing, I decided to completely erase and format my SD card.
I'm using CM 7 on HTC Desire (working quite well).
Now I'm facing a problem : I can mount the sdcard and sd-ext from the recovery. But only the sdcard is mounting automatically upon startup.
When launching S2E, it doesn't show the ext partition.
When I go to the terminal and manually mount (mount -w /dev/block/mmcblk0p2 /sd-ext), it works, and then S2E shows me the space available.
But apps still get installed on the "real" internal memory, so rapidly showing a "low memory" error.
I guess rebooting should enable the S2E memory management, but as long as the sd-ext doesn't mount on startup, it can't do anything.
As /etc/fstab is mounted as read-only (and it's starting to be a mess on my phone), do you have any solution ?
By the way, although it's an ext3 or ext4 partition (I don't remember), mounting without giving the type makes it mounting as ext2 (and working perfectly).
Regards,
Jonatan
Solved here
Go the below link , i think they solved this problem
http://forum.xda-developers.com/showthread.php?t=1971689
Hit THANKS if i helped You in this issue
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
WANT TO MAKE YOUR GALAXY Y AS A HIGH END DEVICE WITH 1.2GHZ , 1 GB INTERNAL STORAGE , HD GAMING , LAGGLESS
GO THE BELOW LINK
EMPOWER YOUR GALAXY Y
CLICK HERE
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 just got my first Android Device (Moto E) and tried to get around the small internal memory by using the sdcard instead of the internal memory for /data. As the KitKat mounting procedure does not seem to be based on vold.fstab anymore, the usual guides to doing that don't apply.
So my idea was to format the sdcard with ext4 and modify the /fstab.qcom file to mount the sdcard as /data instead of the internal data partition. But here's where I don't know how to proceed, as adb shell don't seem to have access to the proper partition during flashboot (though having mounted the rootfs parition which should contain those files?) and is unable to write to the file once the system is running.
I'd appreciate if anyone can point me in the right direction on how to do that.
lunaticat said:
I just got my first Android Device (Moto E) and tried to get around the small internal memory by using the sdcard instead of the internal memory for /data. As the KitKat mounting procedure does not seem to be based on vold.fstab anymore, the usual guides to doing that don't apply.
So my idea was to format the sdcard with ext4 and modify the /fstab.qcom file to mount the sdcard as /data instead of the internal data partition. But here's where I don't know how to proceed, as adb shell don't seem to have access to the proper partition during flashboot (though having mounted the rootfs parition which should contain those files?) and is unable to write to the file once the system is running.
I'd appreciate if anyone can point me in the right direction on how to do that.
Click to expand...
Click to collapse
A little late in the game (I am trying to do the same), but I come across this:
http://forum.xda-developers.com/showthread.php?t=443994
boot partition populates the rootfs. So hack the boot.img (unpack to analyze), and you may find your answer. Hope this helps.
I will give it a shot in the next week.
I cannot install anymore applications. I got an error "Can't install app - insufficient storage available".
I lack place on my device, so I move app as much as I can to the External card using AParted and Link2SD.
I found out that every time I want to link to SD card with Link2SD I got a warning: "NOT MOUNTED - /data/sdext2 mount not found"
When Link2SD starts, it opens a window asking to select my SD card's second partition from the following list: ext2, ext3, ext4 (the others are irrelevant). Whatever I choose I get an Mount script error "Mount script cannot be created. Mount invalid argument".
I checked the Storage Info (using the Link2SD app), and found that all the "partitions" - like Internal, SDcard, External SD, System and Cache - have some data and the percentage of free place - except "SD Card 2nd Partition" that remains empty. There is even a label that says "NOT MOUNTED".
I searched my phone trying to find the "sdext2" to mount it (how do I do it?) - but I couldn't find it. This is an CATCH 22 situation :laugh: I cannot download and install app but I can continue to use my phone with a lot of app removed!
Is there a way to delete the /data/ext2?
is there a way to mount the ext2?
How can I repair it?
Somebody with some help?! Please, don't recommend me to use the frightened FACTORY RESET - I had enough of this solution!
thanks, Roby
Do you have root explorer set and mount R/W set correctly?
Are you sure you followed instructions to setup Link2SD correctly?
Try posting your question in the GT-I9505 Q&A forum linked below.
http://forum.xda-developers.com/galaxy-s4/help?nocache=1&z=8359136844519526
Good luck
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.