This is how it works:
1. I sync the latest CyanogenMod 10.1 source code to my development machine.
2. I add my various modifications and tweaks to the source code.
3. I compile the ROM.
Android 4.2.2 - mr1.1-release
This update is deceptively large in the change department, but still manageable. We are working on the same principle as with the update from 4.1 to 4.2, and are working in 'mr1.1-staging' in our github.
There are quite a few conflicts, which are to be expected as we are more than just a bare AOSP OS, but these will have to be sorted before we start issuing releases based on the 4.2.2 code base.
# Lots of translation conflicts.
# There don't appear to be new device repos nor any communication on the usual mailing lists regarding this. Even updated kernel source appears to be missing.
# Some major changes to hardware/qcom/display, which will affect most devices using that. Degree of the impact varies, but this seems to revolve around the new 4-layer composition.
Please don't bug your various maintainers asking 'when?'. These things take time to do properly and rarely apply cleanly. Good work takes effort, and effort takes time.
It sounds to me like your battery is just totally dead. Mine does the same thing (did it on stock ROM too) when its been run totally flat. Usually take 10 min or so before it will turn on.
As for the extreme battery drain, that would have to be a process stuck running on your tablet. There's no apps in the ROM that hog affinity by default and I get almost a week of standby time running this ROM.
When your tablet is charged up, look at the battery stats to see what's hogging affinity.
Are you running a custom kernel?
Of course, it is possible that you've experienced a total system failure. Have you tried booting into the bootloader?
This ROM only flashes the kernel and system partitions, the bootloader is untouched, so there's no way it could cause the a total system failure.
|cm10.1, cyanogenmod, manta, nexus 10, sentinelrom|
|Thread Tools||Search this Thread|