Boot loops in CM10 about platform_frameworks_base HOT 8 OPEN

I've merged this into my codebase, so I'll build for it (cm10) now and hopefully that will help. CM10.1 is still not booting when built, and AOKP jb-mr1 doesn't even build at the moment (even without any OpenPDroid changes).

In terms of the others - I've built AOKP JB branch (4.1.2), and AOSP 4.2.2.
http://digitalfeed.net/android/built_20130221.tgz

from platform_frameworks_base.

I don't see it on the Github app...but maybe you mean locally. We have built for this, and applied the build patches but there is something else conflicting in the code. Just to be clear.

from platform_frameworks_base.

Ah, right.
Well, for a start I'll push up all of my stuff to the repositories.

So what you're saying is that built CM10 gets bootloops: even if it has not been applied through autopatcher, but is actually just the output of the build directly?

(I've got a fresh build of CM10 which I'll try out tonight)

from platform_frameworks_base.

No, I am pretty sure that all the builds boot. I can't say what the problem you and Stefan are having with CM10.1 (there were a lot of binary updates...?). But we have something where we are casting things to PrivacySettingsManager and the stericson package (FM code, and high in the tree) is resisting because of a type conflict. Or that is what it looks like to me. I just got my first look at the log today as I was leaving the house.

Our CM10 auto patched makes previously working builds loop as a consequence. There is another code conflict of asimilar type in telephony (I believe) that allows a boot but causes constant FC in AOKP, CM10.1 and PA3.0. I have gotten around that by using the telephony patches from 0201. For the telephony stuff, I am not sure where the fault is yet, honestly.

from platform_frameworks_base.

I finally just bought a CM10 capable device and built 4.1.2. I am getting FCs and the keyboard won't work, so I never installed Pdroid2.0 or PdroidManager. I see a lot of PDroid:ContextImpl: ContextImpl being created but already has sOuterContext, but nothing similar to the above excerpt. 4.1.2 AOKP was just reported to have constant phone FCs as well.

The device I have isn't a phone (Nexus 7). There is also the chance that the FCs are unrelated to openpdroid. Even with a data wipe and factory reset in recovery, flashing the Cm10 build by itself retained the 4.2.1 gapps that were already on the device. I downloaded an flashed the 4.1.2 gapps, but maybe the keyboard issues are related to a gapp leftover from 4.2.1.

Either way, as of now, I haven't been able to get it to work. I have been reluctant to completely wipe it, as I have backups of all my son's games on the 'sdcard'. But if I have to, I can lock/unlock the bootloader to completely wipe and start fresh. Anyone ran a 4.1.2 build since I asked a couple weeks ago?

from platform_frameworks_base.

Shoot. Logcat here: http://pastebin.com/6YF9WL0R

from platform_frameworks_base.

I posted in the OpenPdroidDevs group, but we got a second logcat confirming my issues from above. 4.1.2 is broken officially, for the last month.

from platform_frameworks_base.

CollegeDev suggests that it is related to perhaps missing SIP and it's subclasses in telephony/java/com/internal/telephony. All of those files are in the tree, build patches, and smali patches, however. That does not necessarily mean there isn't another reason they cannot be found, the method cap work arounds make CM10 very messy. Although I don't see anything related to SIP at a glance...

from platform_frameworks_base.