On previous kernels 1011M was valid, but now something is eating an extra 8M.
IMO The easiest test for this is to use CM Recovery and try to sideload a CM.zip. Android can (and does) boot with a too large value, but will eventually 'randomly crash', leading to difficult debugging.
When testing via CM Recovery, all low values will succeed, but when too high the kernel will instacrash once sideload has 100% sent the zip.
On previous kernels 1011M was valid, but now something is eating an extra 8M.
IMO The easiest test for this is to use CM Recovery and try to sideload a CM.zip. Android can (and does) boot with a too large value, but will eventually 'randomly crash', leading to difficult debugging.
When testing via CM Recovery, all low values will succeed, but when too high the kernel will instacrash once sideload has 100% sent the zip.
Signed-off-by: Adam Farden adam@farden.cz