Now that i've finally gotten around to unlocking my bootloader & playing around with custom ROMs, i'm wondering if it's possible to resize the various partitions in the arc's internal storage, to reclaim some of the now unused space in the cache partition (since youre not going to be doing OTA updates on a custom ROM) and the system partition (if you install a cut down/minimal ROM) for apps.
On other phones (e.g. HTC Hero, HTC Desire) it's been possible to achieve this for quite a while now. Had a look around the arc forums but cant see anything that even hints that this being looked at for the arc.
Is it something that nobody's got around to yet (the arc is obviously newer than either of the phones mentioned above, and there are a lot more phones about now, diluting the pool of available geniuses to work on this sort of thing), or is there insufficient information available, or is there something about the arc's hardware that makes this fundamentally impossible?
I am pretty sure this is protected and can't be touched, although Sony allowed the bootloader to be unlocked they still keep some things locked.
I am not a dev so maybe proved wrong.
Sent from my LT18i using XDA App
I can remember that when arc was new on the market, some devs tried changing partition sizes for CWM, and they bricked theyre devices with it.
so yes repartitioning is possible, but i don't recommend you doing so cause doing it could totally brick your arc
Not to much, what can you do is, link dalvik-cache to SDCard.
We could reclaim about 250MB of space!!
Some devs know how to do it for sure. As they do it for x10.
Flashtool devs should be your targets.
My HTC Desire running cm7r2 hboot table right now.
Sent from my LT18i using Tapatalk 2
Bumping up this question. Is there no working way to do this after many months? Say for my Arc running on Arconium 8.2:
System ROM : 419 MB (201 MB free) = 620MB total capacity
Internal : 440 MB (118 MB free) = 558MB total capacity
Overall TOTAL : 1,178MB
DESIRED:
System ROM : 419 MB (77 MB free)
Internal : 440 MB (242 MB free)
Basically reduce the overall system ROM capacity from 620MB to 496MB, and the free space given to Internal (558MB to 682MB). The overall total remains the same of course.
Any way to do this? Or I am basically stuck at converting user app to system app in order to maximize the capacity?
I don't think that would be possible... Try rooting your phone and install clockwork mod... In tat you could partition your sd card say 500 mb and make it as internal memory via link2sd... Search in arc forum...
jtdc said:
Bumping up this question. Is there no working way to do this after many months? Say for my Arc running on Arconium 8.2:
System ROM : 419 MB (201 MB free) = 620MB total capacity
Internal : 440 MB (118 MB free) = 558MB total capacity
Overall TOTAL : 1,178MB
DESIRED:
System ROM : 419 MB (77 MB free)
Internal : 440 MB (242 MB free)
Basically reduce the overall system ROM capacity from 620MB to 496MB, and the free space given to Internal (558MB to 682MB). The overall total remains the same of course.
Any way to do this? Or I am basically stuck at converting user app to system app in order to maximize the capacity?
Click to expand...
Click to collapse
Your first calculations are wrong. System ROM has 201 MB free out of 419 MB, and Internal has 118 MB free out of 440 MB, so max is 419 + 440 which is 859 MB. The 1000/1024 difference, you get the 1000 MB of flash memory (hardware) on your phone.
Someguyfromhell said:
Your first calculations are wrong. System ROM has 201 MB free out of 419 MB, and Internal has 118 MB free out of 440 MB, so max is 419 + 440 which is 859 MB. The 1000/1024 difference, you get the 1000 MB of flash memory (hardware) on your phone.
Click to expand...
Click to collapse
That's correct.
Table can be changed if someone can break Sony's encryption keys.
My HTC Desire runs on changed partition table (cm7r2).
Sent from my LT18i using Tapatalk 2
i see, thanks for pointing that out. in any case, i can't do anything but do convert to system app to maximize the usage.
Hi, like in topic - i've at last installed CM 9.0 FXP 130, but when i enter system info its showing only 360MB of ram, instead of 512 (SEX PRO got 512 as far as i know).
Why is that happening? Is this bug, or i don't know something?
I think you can allocate more RAM to your phone...
That's not bug/issue. 360 mb is user-available from 512
Oh,,, hell yeah, i want it badly. :victory:
+1
No. No sources are released, and you'll have to find someone to port it when the sources are released in the fall.
SGWUser said:
No. No sources are released, and you'll have to find someone to port it when the sources are released in the fall.
Click to expand...
Click to collapse
Maybe sir arco will save us again when the sources are released You never know..
a port may come soon but we have to wait until it is final so they release cm 12
eri000 said:
a port may come soon but we have to wait until it is final so they release cm 12
Click to expand...
Click to collapse
That isn't necessarily true, for example CM 10.1 released by arco still in beta4 version
dqsnunes said:
That isn't necessarily true, for example CM 10.1 released by arco still in beta4 version
Click to expand...
Click to collapse
the CM team announced that there will be NO CM version until the google releases the final image of android L on AOSP.This doesn't mean we will have a final stable version of cm immediately BUT we will only see a cm12 build when final android L gets merged into aosp.
^That is for other phones that get CM OFFICIAL.For ancora we have to wait a little bit more for unofficial cm, which is based on official cm.So no official--- no unofficial (arco if he has time to mess with it,or others)
BTW, Android L is currently being ported to the Nexus 4 and Nexus 7 2012 right now. Both are almost functional.
I think even if we were to have Android L here, i don't think it will be responsive. Google said, Animation transitions run at 60fps, Im not sure if overall perfomance can run at the same fps because i bet our processor is not powerful enuff or smth. CMIIW.
Android L Port For Nexus 4
Newest Android L Port For Nexus 4 Is Now Fully Operational And Ready For Download
INFO
I strongly doubt that our device could get an Android L update.
The default runtime of android l is ART runtime.Our device does'nt hold that much of system memory for apps.
The only chance is to make a switchable runtime like in Kitkat (Dalvik/Art) or creating a new partition .
Anyway these are all guess and lets see what magic our Great devs can bring to our small beloved device.:good::fingers-crossed:
theloneseeker said:
I strongly doubt that our device could get an Android L update.
The default runtime of android l is ART runtime.Our device does'nt hold that much of system memory for apps.
The only chance is to make a switchable runtime like in Kitkat (Dalvik/Art) or creating a new partition .
Anyway these are all guess and lets see what magic our Great devs can bring to our small beloved device.:good::fingers-crossed:
Click to expand...
Click to collapse
A swap partition for art can't help?
theloneseeker said:
I strongly doubt that our device could get an Android L update.
The default runtime of android l is ART runtime.Our device does'nt hold that much of system memory for apps.
The only chance is to make a switchable runtime like in Kitkat (Dalvik/Art) or creating a new partition .
Anyway these are all guess and lets see what magic our Great devs can bring to our small beloved device.:good::fingers-crossed:
Click to expand...
Click to collapse
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_device_samsung_ancora/commit/3455d7837c951e297335295a36cd2202a9f629f3 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
sir mordred said:
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_device_samsung_ancora/commit/3455d7837c951e297335295a36cd2202a9f629f3 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
Click to expand...
Click to collapse
Nice thinking and good luck :good:
sir mordred said:
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_device_samsung_ancora/commit/3455d7837c951e297335295a36cd2202a9f629f3 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
Click to expand...
Click to collapse
Umm very interesting if you want some testers,i'm here.
If you have cm11 theme chooser:
http://forum.xda-developers.com/android/themes/theme-l-ready-t2802979
https://play.google.com/store/apps/details?id=nexbit.icons.moonshine
Settings>Performance>Force high-end graphics>check
AND YOU HAVE L IN YOUR WONDER(I LOVE MY WONDER)
what is android L? can someone tell me about it please?
smartiescoke said:
what is android L? can someone tell me about it please?
Click to expand...
Click to collapse
The upcoming Android version. About it...there are many things to say. You could search YouTube for "Google I/O 2014". There are a lot of new things about it. If you've got time to spend and curiosity, it might be very interesting to watch. This way, you will also answer your own question (and more).
arsradu said:
The upcoming Android version. About it...there are many things to say. You could search YouTube for "Google I/O 2014". There are a lot of new things about it. If you've got time to spend and curiosity, it might be very interesting to watch. This way, you will also answer your own question (and more).
Click to expand...
Click to collapse
whoa! really? awesome! i always been waiting google to update different kind of android version. ui and etc, hope it will come to our wonder soon! XD
oh man i love android L ui and statusbar. Hoping our Great Developer can bring this to our Wonder.
#sorry for my bad english.
Hello everybody
Currently my system partition has 2113 MB (it is default size), I have CM 13.0 installed with OpenGapps Pico package on it and only 988 MB is used so it's means that 1125 MB is free. I wonder if it is a good idea to resize this partition to e.g 1113 MB and shift all free 1000 MB to data partition? What's your opinion? Does anyone tried this?
best regards,
The question is "can it be done"? Usually resizing partitions is quite difficult and may brick your device.
hmmm... I didn't think about it like that. I thought that I can resize as I want but I have to keep big enough to put ROM on in.
Hi,
My Pixel 3 (blueline) works well on LineageOS 19.1 with microG but Android Auto does not works (that was the same for previous LineageOs version). According to many posts, Android Auto can't be installed from apk and has to be sideloaded.
Looking for help, i intend to sideload Android Auto AddOn after upgrading but the upgrade failed because of lack of space in system partition (error 70).
I precise that TWRP does not work because many post everywhere suggest to resize partition system with TWRP : i can't do that on my phone, that is why i ask for help.
I remain to have seen somewhere a long time ago - but i don't know where - that partition size can be set if i manually build LineageOS. According to this post i think i can manage with building the ROM by myself. But i don't know how to set system partition size.
Do you know where i can find any information how to set system partition in building ? Or to resize partition another way ? Or to find a really tiny zip of Android Auto ?
I've seen a post using parted and gdisk. I understand the post as a linux user who used to deal with parted but i'm not really enthousiast with the proposed solution.
Well, can you help me to expand my system partition ?
Thanks.