Patching away with WebOS Internals on webOS 1.4.1(.1) | webOS Nation

Patching away with WebOS Internals on webOS 1.4.1(.1)

by Derek Kessler Sun, 04 Apr 2010 6:37 pm EDT

Preware It’s a solemn act taken up after every update to webOS: reapplying all of your patches. While things have gotten to be significantly easier since the advent of Auto-Update Patch Technology (otherwise known as AUPT), there’s still some work that needs to be done. Or at least, some clarification.

So here’s the deal, as explained by WebOS Internals’ Rod Whitby: AUPT makes things easier for the end-user, but patience is still needed. As with webOS 1.3.5 and webOS 1.4, the version of webOS 1.4.1 that was pushed to users was different than the version distributed earlier to developers. While it’s not a major difference, the numerical difference is enough that the patches the WebOS Internals crew had prepped for release were no longer registered.

AUPT works like this: A log of your installed patches is stored on the device, when you perform a webOS update, Preware then references that log and redownloads the patches. If a patch hasn’t yet been ported to the new webOS version, then a dummy placeholder patch is downloaded merely to stand in place for when the update is made available. When the different version of webOS 1.4.1 was shipped and users attempted to reapply patches before they had been reverified, they simply downloaded a bunch of placeholders. A word of advice: don’t panic and doctor your phone the next time webOS is updated and none of your patches work. It takes time for the patches to be checked against the new version, and even then your favorite patch may end up broken.

The above-described situation was only exacerbated by the fact that Palm released webOS onto Sprint and webOS 1.4.1 to everybody else (sans Verizon). As far as the vast majority of patches are concerned, the difference is negligible, but Preware works by recognizing your webOS version and checking for patches that have been tagged as compatible. Double the pleasure, double the fun. Either way (or both, we suppose), the gang was able to pull everything together under their self-imposed 24-hours after any update hits. As always, you can follow WebOS Internals’ progress during updates and the times between on the Twitter.

A number of patches were found to be incompatible with webOS 1.4.1 in some shape or form. Rod has posted a list of them here, and noted that because all webOS patches are required to be open source, it’s not contingent upon the original developer to update them for compatibility - anybody with the proper code wizardry up their sleeves can crack open the IPKG and take a try at fixing it. Or creating your own, if you so desire.

It’s at this point that we are obliged to mention that WebOS Internals is an entirely open source and donation-funded operation. As such, they rely on the generosity of users like yourself (seriously, you’re reading this and not running patches?) to pay the bills, upgrade the servers for the always-increase user base, and cover developer costs. Sometimes those bills can be unexpected, like when the motherboard on the computer you use to automate a lot of your functions fails. So seriously, consider donating.