[LG Optimus 2x] mateorod:
Okay, so here is (yet another) update. But this time with some results!

I have patched your files, pastime. I had switched from the baksmali binaries to apktool (which I hadn't used before) because I needed to patch the preloaded classes file in the framework.jar. I thought that apktool would output that change. However, it turns out apktool is basically just a zipping tool packaged with the exact same binaries I always use. Hmm.

I, of course, had all sorts of issues before I got smart enough to check these jar archives. :mad: I had PDroid working (fine, it seems) but kept getting some irritating gapps FCs. It was because framework and core didn't have all their pieces. This foray into apktool wasted a good six hours of work, since I had to learn how to use it and don't see any benefit over to what I already had.

Anyway, I didn't want to just not patch the preloaded classes, as I am sure those changes are there for a reason. Even though PDroid appeared to work, I wanted those in there. Soooo...

From what I understand, Google just updates the preloaded classes file from release to release. So, I packaged my patched encore framework.jar with a preloaded classes file from a Pdroided LG-P930 build. It has no discernable ill-effects on the ROMs operation.

So my plan for now is to just package the preloaded classes into the patcher and use the one file for all ROMs. It is possible that may limit the patcher to CM9, though, I am not sure about that yet. I will continue to try and find a way to decompile (or rebuild? Maybe I have already gotten at the code and just need to rebuild the thing?) the preloaded classes, but we'll see. For now, let's try this.

Pastime, here are your system apps, already patched. As a bonus test, you also have a preloaded classes file from LG-P930. Hopefully you don't encounter any problems either. Just extract and repackage them into that non-PDroided build, flash, and report.

I am going to attach the patches as well, the more eyes the better. They need some work, some of it very obvious, some of it maybe not so much. They work great for me, so far. These were made with apktool, but I may just go back to the smali binaries patches, as I know the baksmali tool WAY better and am more comfortable with it.

If anyone else wants to test for us, (UPDATE: CM9 for now, please)please package your framework, core and services.jars and build.prop into a zip and post them. (I only need three or four of testers for now, please). I will patch them and get them to you for flashing. Or, if you are comfortable decompiling and patching, use the attached patches below. Hopefully, the work for other devices and then we can get started building the patcher package itself.

Edit: I have added a patches zip. This zip has the three patches, made from apktool output and the preloaded classes file which needs to go in the framework.jar. Note that rebuilt system.jars still are really only zipped up classes.dex. The meta-info and other parts will still need to be added to those rebuilt zips. Just throw in the pieces from your stock system apps except add the included preloaded classes file to your framework.jar. Any questions can just be posted in the thread.