[Android Software/Hacking General [Developers Only]] mateorod:
Okay. I will use this to see what I can do. I was told that there was an official release and it was failing...which I thought was perhaps false. Devices only get unofficial releases when they have hardware requirements which stop them from working with the mainline Cyanogen tree. The unofficial ports use workarounds to create roms, but these same workarounds create the differences which stop major patches (like PDroid, which is major surgery) from applying cleanly. I have a bunch of work already logged as to how to get around this...once 4.2.1 and Autopatcher is stable (2.6.7.0 hopefully) that will again get my attention. There may be hope for you guys when that is done.

I see from the link that this CM rom is based on Quarx. Quarx roms are a long-known problem around here. We could support it, but we would need a maintainer. We are stretched to our limit with the 6 roms we carry now.

Sorry, I don't know if that is correct or not. Best thing to do is to try a rom from our supported list on OP, i.e. Cyanogen or AOKP or something. I dont know what kind of rom that is, but it is unfamiliar to me. If the "cfx" stands for CodefireX then I think that may be based on Cyanogen, in which case you perhaps will find more luck using 'cm' as a romtype. I try to catch all of this in the script, but build.prop parsing is still a black art. I am perhaps at the top of this mystical art, and still I search.

I don't really know what you are asking, sorry. We patch just about any file you can find in a built android rom, excepting kernels. There may be other exceptions, but none that I know of. Smali files, text editing, boot.imgs etc.

Okay. I see some AOKP problem of some sort. I can do something about this, I think. Look for it tommorrow. It is failing with the new patches, maybe there was a problem with those builds.

I actually firsty had replied to you guys that it was working, until I realized I was on a different computer and needed to pull down the latest autopatcher myself. With the new patches it does indeed fail. That means that you could likely use an older autopatcher (from before 2.6, say 2.5.0 or whatever) and it would work. But the openpdroid patches had some bugs then, which is why I yanked them from the recent auto-patcher. Probably best just to wait. Look for something tomorrow.

TabletUI is having weird trouble, I will be working on it this week and it's final fate will be announced with 2.6.7, whatever that fate may be.

Thanks for remnding me...now that openpdroid is closer to stable, I can devote a little time to this. The problem with GNex (toro versions) is the same as for Mako (Nexus 4),,,those devices do not have AOSP support. That almost always comes down to licensing issues, and just means that there were business considerations that have stopped support. Doesn't make it any easier for owners of those devices, especially devices branded "Nexus", you know?

No that happens and is completely normal. I could get pretty technical here, but lets just say that a bunch of functions, when decompiled, are labeled by indexs, and those are by definition dispersed on a first-come, first-served basis. Those ignored hunks simply mean that by chance, those methods are already slotted in the index they needed to be for our patches. So everything is kosher. Try it and see.

I am lumping all the replies about this issue here...I am not unaware of this, but I am trying to figure out exactly how to handle this. There are a bunch of hacky things I can do, but I would like to do something that makes sense for the program, and is expandable/repeatable should a simliar issue appear elsewhere. I am not 100% sure why this is even happening. I have looked at the PA manifest, they are simply using the CM opt/telephony repo, albeit an unmaintained version, they simply forked it, added no improvements and yet have not merged any of the commits from the last couple months. In my mind they would have been better served simply pointing to the CM repo instead of forking and abandoning their own copy. But whatever.

I could make some device specific stuff, yet this doesn't look to be related to just one device. I am loath to simply copy over the file as you need it since concievably someone could get that by mistake and get errors. We try and be pretty meticulous around here...excepting the one time with AussiLampChop and then some CM7 problems we had, if the auto-patcher produces an update.zip, your pdroid program should work.

I am considering the various ways I can include this fix so it doesn;t have to be done manually. Thanks to aussie for finding the solution for us. That is the kind of thing that has to happen for us to widen support, I just can't do it all myself.

Hi meteor. Yah, I almost told you about it when I saw you were trying permission management, but it seemed out of place so I didn't. Hope you like it. Above I talk about how I have used device-specific fixes before...the Nook Color uses a device-specific script due to a bug in the verygreen installer. But that doesn't matter, it should work on your Nook no problem.

Actually, no pappy. (I can call you pappy, right? :p). It is confusing (you can tell because wbedard, who knows his stuff, is off about this) but Nexus 4 stock is not currently supported. Nexus 4 does NOT have AOSP support. It is a common misconception, but Nexus stock roms and AOSP are different things. They are very close, but they are different. Things like Galaxy Nexus and Nexus 4 do not have AOSP support due to licensing issues, usually related to the GSM stack.

What that means is that for now, you cannot add openpdroid on your device, at least not without a bunch of effort hand editing decompiled apps. I aim to do something about that, but it will take some time. However, CM10.1 and AOKP should be supported for your device and I personally think that CM is great for people who have Nexus devices but want to keep that pure Android feel. Cm is basically pure AOSP at this point, just with all the features that Google witholds put back in. Sorry for the confusion, I can understand it is hard to keep straight.

There are so many roms, and so many different levels of user-experience, it is hard to walk the line between not offering too much info and yet still offering enough. You can ask any question here.