Attend XDA's Second Annual Developer Conference, XDA:DevCon 2014!
5,728,360 Members 54,606 Now Online
XDA Developers Android and Mobile Development Forum

[ROM][KitKat]Unofficial CyanogenMod 11

Tip us?
 
SFxBA
Old
(Last edited by SFxBA; 1st June 2014 at 03:07 AM.)
#311  
SFxBA's Avatar
Junior Member
Thanks Meter 2
Posts: 20
Join Date: Dec 2010
Quote:
Originally Posted by zekemo View Post
What version would you recommend? I also cannot get gapps to install.
March version worked fine for me. Might have a work around for April, but haven't been able to check. Will update if it works.

Sent from my SCH-I535 using Tapatalk


**Update, no go on the work around. Thought I had it working, but then got too many FCs with play store. Finally settled in with March release and things are smooth.
The Following User Says Thank You to SFxBA For This Useful Post: [ Click to Expand ]
 
willmore
Old
(Last edited by willmore; 9th July 2014 at 09:38 PM.) Reason: Corrected some facts
#312  
Junior Member
Thanks Meter 0
Posts: 15
Join Date: Feb 2013
Default /system full with 4/28 update

I see that you noticed that we're over size on /system with the 4/28 update.

Is there some way to reduce the size of files put there or can we repartition the NAND to put more space in /system? Poking around, I found:
Code:
/system                248.0M   248.0M    40.0K   4096
/data                  748.0M   225.8M   522.2M   4096
/data/data             149.0M     6.0M   143.0M   4096
/cache                 196.8M    16.3M   180.6M   4096
Code:
/dev/block/mtdblock3 /system
/dev/block/mmcblk0p1 /data
/dev/block/mtdblock6 /data/data
/dev/block/mmcblk0p2 /cache
According to dmesg:
Code:
Creating 7 MTD partitions on "msm_nand":
0x00001ff60000-0x000020000000 : "misc"
0x000004240000-0x0000046c0000 : "recovery"
0x0000046c0000-0x0000049c0000 : "boot"
0x0000049c0000-0x0000141c0000 : "system"
0x00001fec0000-0x00001ff60000 : "local"
0x0000141c0000-0x0000169c0000 : "cache"
0x0000169c0000-0x00001fec0000 : "datadata"
It looks like there is space on the mtd--or we should. For a 1GB NAND device, we're not even using half of it--or something is formatting things wrong/misinterpreting block sizes.

/data/data could be shrunk so that system can be expanced.

Edited: Searching through teardowns and other solid info online makes me believe that all the common data for the NAND on this device got it wrong. The NAND chip is a 4Gb chip in a 256KBx16 configuration.
 
zachf714
Old
#313  
zachf714's Avatar
Senior Member - OP
Thanks Meter 982
Posts: 3,536
Join Date: Jun 2012
Location: Mooresville
Quote:
Originally Posted by willmore View Post
I see that you noticed that we're over size on /system with the 4/28 update.

Is there some way to reduce the size of files put there or can we repartition the NAND to put more space in /system? Poking around, I found:
Code:
/system                248.0M   248.0M    40.0K   4096
/data                  748.0M   225.8M   522.2M   4096
/data/data             149.0M     6.0M   143.0M   4096
/cache                 196.8M    16.3M   180.6M   4096
Code:
/dev/block/mtdblock3 /system
/dev/block/mmcblk0p1 /data
/dev/block/mtdblock6 /data/data
/dev/block/mmcblk0p2 /cache
According to dmesg:
Code:
Creating 7 MTD partitions on "msm_nand":
0x00001ff60000-0x000020000000 : "misc"
0x000004240000-0x0000046c0000 : "recovery"
0x0000046c0000-0x0000049c0000 : "boot"
0x0000049c0000-0x0000141c0000 : "system"
0x00001fec0000-0x00001ff60000 : "local"
0x0000141c0000-0x0000169c0000 : "cache"
0x0000169c0000-0x00001fec0000 : "datadata"
It looks like there is space on the mtd--or we should. For a 1GB NAND device, we're not even using half of it--or something is formatting things wrong/misinterpreting block sizes.

/data/data could be shrunk so that system can be expanced.

Edited: Searching through teardowns and other solid info online makes me believe that all the common data for the NAND on this device got it wrong. The NAND chip is a 4Gb chip in a 256KBx16 configuration.
I can't shrink it any more, it is just to large of a rom now. I believe tiny looked into resizing /system by using empty space but did not get very far. I think the nexus one actually does that with black rose so we would probably need a new hboot

Sent from my SCH-I535 using Tapatalk
OMNI-ROM Co-Maintainer for TF-101

Verizon Samsung Galaxy SIII Unlocked Bootloader Running my CM-11.0 Custom Builds

Droid Incredible AMOLED Unlocked Bootloader S-OFF Running My CM-11.0 Builds

Asus Transformer B60 with B80 Dock Running Omni 4.4
 
willmore
Old
#314  
Junior Member
Thanks Meter 0
Posts: 15
Join Date: Feb 2013
Quote:
Originally Posted by zachf714 View Post
I can't shrink it any more, it is just to large of a rom now. I believe tiny looked into resizing /system by using empty space but did not get very far. I think the nexus one actually does that with black rose so we would probably need a new hboot
You've exceeded my understanding of the devices boot process. I take it the NAND partitioning is built into the HBOOT in some way? And in such a way that it's hard to change? Hmm, how about leaving out some stuff like Camera2.apk and relying on things from the play store. Which is to say, do a lot of these system apps really need to be in /system? As long as we can get into the play store we can always find an app to do whatever we need, right?

I'm probably misunderstanding something fundamental.
 
zachf714
Old
#315  
zachf714's Avatar
Senior Member - OP
Thanks Meter 982
Posts: 3,536
Join Date: Jun 2012
Location: Mooresville
Quote:
Originally Posted by willmore View Post
You've exceeded my understanding of the devices boot process. I take it the NAND partitioning is built into the HBOOT in some way? And in such a way that it's hard to change? Hmm, how about leaving out some stuff like Camera2.apk and relying on things from the play store. Which is to say, do a lot of these system apps really need to be in /system? As long as we can get into the play store we can always find an app to do whatever we need, right?

I'm probably misunderstanding something fundamental.
It would still be too large, with the way themechooser was redone it would be just too large to fit with gapps

Sent from my SCH-I535 using Tapatalk
OMNI-ROM Co-Maintainer for TF-101

Verizon Samsung Galaxy SIII Unlocked Bootloader Running my CM-11.0 Custom Builds

Droid Incredible AMOLED Unlocked Bootloader S-OFF Running My CM-11.0 Builds

Asus Transformer B60 with B80 Dock Running Omni 4.4
 
willmore
Old
#316  
Junior Member
Thanks Meter 0
Posts: 15
Join Date: Feb 2013
Quote:
Originally Posted by zachf714 View Post
It would still be too large, with the way themechooser was redone it would be just too large to fit with gapps
So we're boned?
 
tiny4579
Old
#317  
Recognized Developer
Thanks Meter 4015
Posts: 7,442
Join Date: Jan 2011
Quote:
Originally Posted by zachf714 View Post
It would still be too large, with the way themechooser was redone it would be just too large to fit with gapps

Sent from my SCH-I535 using Tapatalk
There is the option of symlinking /system/app to somewhere else like /data/system.app like we did for the olds sense Roms. Not sure how it will play with selinux but we can disable it if that's a concern. This way no partitioning is needed.
 
zachf714
Old
#318  
zachf714's Avatar
Senior Member - OP
Thanks Meter 982
Posts: 3,536
Join Date: Jun 2012
Location: Mooresville
Quote:
Originally Posted by tiny4579 View Post
There is the option of symlinking /system/app to somewhere else like /data/system.app like we did for the olds sense Roms. Not sure how it will play with selinux but we can disable it if that's a concern. This way no partitioning is needed.
Selinux is already disabled, it does not play well with 2.6.x kernels I have found. I would like to not mess with the zip after it is compiled as much as possible

Sent from my SCH-I535 using Tapatalk
OMNI-ROM Co-Maintainer for TF-101

Verizon Samsung Galaxy SIII Unlocked Bootloader Running my CM-11.0 Custom Builds

Droid Incredible AMOLED Unlocked Bootloader S-OFF Running My CM-11.0 Builds

Asus Transformer B60 with B80 Dock Running Omni 4.4

Tags
inc cyanogenmod11 cm11 dinc qsd8k
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes