Attend XDA's Second Annual Developer Conference, XDA:DevCon 2014!
5,805,468 Members 37,886 Now Online
XDA Developers Android and Mobile Development Forum

Android L for Galaxy W? In Custom way?

Tip us?
 
r25txe
Old
#21  
r25txe's Avatar
Senior Member
Thanks Meter 84
Posts: 207
Join Date: Mar 2011
Quote:
Originally Posted by sir mordred View Post
Problem is not a system partition because system partition size(550mb) should be enough because at the moment with latest cm11+gapps i have a 150 mb free space on my system partition so i think our phone can/will handle next android release but we cant know at the moment so im not sure

But main problem is small cache partition
İt is just 60 mb
For that reason we are using some dirty workarounds(in my opinion) like this https://github.com/arco/android_devi...cd2202a9f629f3 with that workaround apps is using /data partition instead of /cache partition for dalvik-caching operations
Why im saying this is dirty workaround? Because i think each operation should use its own partition

Repartition is a real fix for that kind of problems but this way is a very dangerous and have brick risk

İm planning to make some experiments like this:
-With fdisk im planning to split out my internat sdcard(1.7 GB ,mmcblk0p28) to 2 new partitions(first partition will be mmcblk0p28 and have 1.3 GB size and second partition will be mmcblk0p29 and have 400 MB size)
Then we will use mmcblk0p29 as cache partition
-For that firstly we need to format the partition as ext4(because internal sd is vfat but cache partition must be ext4 fs type formatted)
-After converting from vfat to ext4 of new mmcblk0p29 partition, we will change cache partition from mmcblk0p16 to 29 through fstab.qcom
-and last thing we need to do is removing/disabling previous workaround so we will change the following build.prop line dalvik.vm.dexopt-data-only=1 to dalvik.vm.dexopt-data-only=0

This is the cleanest way i think because we arent touching to main partitions(system,data and cache)
We just need to split it internal sd(1.7 GB)

Regards
Dalvik cache is stored in /data, no? The 60Mb cache is used for running apps and is dynamically allocated as needed.

Repartition is probably the only way to go to ensure enough space though for the latest GApps, even a mini version. L ROMs themselves might be over 300 Mb before GApps.
GT-I9100 16Gb black (came unlocked on a contract )
Resurrection Remix (always latest)
No custom kernel (yet)
8Gb data partition ( 2Gb is passť)
BaNks Minmal GApps (coz Resurrection is too phat)

GT-S5360 black (bought second hand for hacking doing good things with)
Hyperion 9 (Simply amazing)
Hell's Fusion #50 (testing)

GT-I1850 black (I like black)
Mokee (latest)
Khan Kernel (LowMemoryKiller)
 
sir mordred
Old
(Last edited by sir mordred; 1st September 2014 at 05:36 PM.) Reason: typo fix
#22  
Senior Member
Thanks Meter 510
Posts: 468
Join Date: Sep 2013
Location: mmcblk0p15
Quote:
Originally Posted by r25txe View Post
Dalvik cache is stored in /data, no? The 60Mb cache is used for running apps and is dynamically allocated as needed.

Repartition is probably the only way to go to ensure enough space though for the latest GApps, even a mini version. L ROMs themselves might be over 300 Mb before GApps.
our /cache partition is too small(its just 60 mb and its designed for GB) so it cant hold the all dalvik-cache on newer android versions

because of that we are using some dalvik hacks like this https://github.com/arco/android_devi...cd2202a9f629f3

so dalvik-cache is stored on /data partition due to very small /cache partition(60 mb)

if you dont believe then try to change that line(delete or change 1 to 0) in build.prop

you will face bootloop
The Following User Says Thank You to sir mordred For This Useful Post: [ Click to Expand ]
 
Harakhti
Old
#23  
Harakhti's Avatar
Senior Member
Thanks Meter 50
Posts: 229
Join Date: Aug 2012
Location: Budapest
Quote:
Originally Posted by sir mordred View Post
our /cache partition is too small(its just 60 mb and its designed for GB) so it cant hold the all dalvik-cache on newer android versions

because of that we are using some dalvik hacks like this https://github.com/arco/android_devi...cd2202a9f629f3

so dalvik-cache is stored on /data partition due to very small /cache partition(60 mb)

if you dont believe then try to change that line(delete or change 1 to 0) in build.prop

you will face bootloop
Back on the previous topic, he also said that the current partition tables are not optimal which was also the reason of me halflazily suggesting to look at other 4GB devices' ones, I believe. I am not sure if it is possible, but it would be beneficial to create a better allocation.
Nokia 5110 (Battery Died) -> Nokia 6030 (Below the Elizabeth Bridge in the Danube) -> Motorola C140 (Dead Mainboard) -> Vodafone (Alcatel) 331 (Lost) -> Samsung E1190 (Snapped In Half) -> Samsung S2530 (Hardbricked, Disposed) -> Samsung GT-S5570 (Backup) -> Samsung GT-S5660 (Sold) -> Nokia C2-02 (Sold) -> Samsung GT-I8150 (Flawless!)

H/W Rev. 0x08, LCD Rev. 0x02
Currently using: XXLMI (XEU) / ClockWorkMod 6.0.5.0 / CyanogenMod 11 (2014/09/10) / Stock Kernel (3.4.103+396MB)
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes