[Android Software/Hacking General [Developers Only]] mateorod:
GSMServiceStateTracker messages (if you choose to read them) make it clear that THOSE ARE

NOT

"ERRORS"!

I am going to make all of that happen in the background for the next update, people cannot handle the information. That is okay, now we know. It's too much. We have plenty of data at this point to support that the GSM can be copied no problem.

Let me say: The Auto-Patcher has 100% successfully ported that project to your rom and all the others.

Those FCs are due to bugs in CollegeDev's initial build patches. He has released an update to those patches. I was hoping some people would respond as to how well they work before I updated the auto-patcher, but so far as I can tell, the only person to try them is wbedard, who is a maintainer for us already.

Patches/ Maintenance

See, this is how it is: We now offer patches for something like 99% of the available roms, and all of our mods work on each one. The trouble is that creating that many patches is a bunch of work that takes a bunch of builds of the various roms. Not something that is reasonable for one person (read: me) to maintain.

So we have crowd-sourced it. We are lucky/blessed to have wbedard, FFU5y and poncik join the team and volunteer to help with the builds. But those builds still have to be made.

Ideally CollegeDev and I would have been in better contact about this update. Rallying and getting builds from my maintainers is a finite resource. There is only so many times I can ask for their time/effort before the law of diminishing returns kicks in and they decide it isn't worth it. 'Cause they do it for free, you see.

With the impending update to Android 4.2 almost here, I actually anticipate ALL of the pdroid/pd2.0 patches will break upon that release. So I would have liked to try and combine those two updates into one, as opposed to asking for multiple builds from each maintainer twice in one week.

None of the maintainers have complained, quite the opposite. I am just trying to be mindful of how often I go to the well.

This isn't directed at anyone in particular, I promise, the quoted post just represented an opportunity to explain/express ourselves. I simply wanted to somewhat clear the air as to why the patches weren't immediately updated like they usually are.

The Future (?)

For Auto-Patcher 3.0 (the form of which is under running debate) I am going to publish/emphasize the tools that we already have available that allow devs (or porters, or hobbyists) to maintain their own patches by the simple running of a script. It is really easy, we just don't have the infrastructure quite yet to support it (hosted patch repos...yadda..yadda)

But the tools are written and available...then this kind of thing could be handled all in-house by CollegeDev, giving him the ultimate power to debug and update patches as he sees fit. Which is how it should be, I am sure it is no fun for him to debug his program and then still get the same old bug reports.

The Update

Having said all that...look for an update tomorrow, covering the new pd2.0 build patches that fix Mms and Phone FCs. The patches will cover CM, PA, and AOSP at minimum, with AOKP and Evervolv to follow at some point.

Thanks for everyone's patience, as you can see we are working on covering the new release soon. We will have made the new pd2.0 software available to all ROMs and devices within a couple days of release, many mods never get that far ever. So we're happy here...