Quote:
Originally Posted by natemcnutty
From what I've been reading, you are able to flash different radios/modems from CWM, but it seems when people make their own custom partition layouts, most of them say NOT to flash radio's from it. Read through a ton of different dev threads at XDA, and that seems to be the common consensus.
I doubt the radio needs access since other devices like the vogue work and don't have it, but if it is in AOSP to cache some info about the radio into that partition, we can always create it later on 
Also, I updated the partition layout for LMiller's spreadsheet. I just took 8 MB from data and moved it into recovery. I want to keep my cache at 64 MB until I can get a feel for the average size it gets up to. I've seen reports on native android phones that when people made it small like 24 MB, they were experiencing slowdowns because of the paging. |
I think for the radio we should just leave it alone. If we need to update the radio or anything like that we can just do it flash. It's more for Native android devices anyway.
Nate glad you got into the spreadsheet. I added in 4MB to your data, you want to make sure you have your left over the same value as your first starting location.
Have you tried using these values yet?
Anyone wanting to look at the spreadsheet can go
HERE.
@ACL,
I would say just go with this MTD Parts: (What we kinda decided on earlier) And boot can be recovery... I will leave that up to you...
Code:
mtdparts=msm_nand:0x20000000@0x0(nand),0x800000@0x4000000(root),0x0A000000@0x4800000(system),0xF800000@0xE800000(userdata),0x2000000@0x1E000000(cache)
Or If Nate has verified the starting location of 100000:
Code:
mtdparts=msm_nand:0x20000000@0x0(nand),0x800000@0x1000000(root),0x0A000000@0x1800000(system),0x12800000@0xB800000(userdata),0x2000000@0x1E000000(cache)
And remember... This can be changed by anyone who can open the NBH with a hex editor!