In one of the recent news discussions, @KnightWRX was describing his experiences applying Preware patches to WebOS 3.0.2:
I had a lot of trouble believing this story at first, but there's plenty of evidence around that these patches have a dramatic impact on the responsiveness of the WebOS UI. What is unbelievable about the story is that HP would ship a product with a sluggish interface when it would have been so easy to make it work better. This wasn't the only factor, but it seems to be a huge factor in the failure of the TouchPad.
This sounds like a huge story, but I haven't seen any of the tech websites write about it. How could a company like HP make an error of this magnitude?
Thanks to @KnightWRX for the detailed description of his experience with his TouchPad and these patches.Well, have a hard time believing it, the patches are nothing extraordinary. They simply turn down the verbosity level on the logging going on behind the scenes, which is set to something like debug in some instances on the shipping WebOS 3.0.2 and the iptables DROP rules all being logged.
Turning it down to Error fixes much of the sluggishness and a few Homebrew patches on Preware actually do that for you (or you can do it yourself with novaterm and some command line hacking using the SDK/PDK). So it's not "Some Internet Dude's" patches, it's genuine understanding of the issue and a little homebrew ingenuity to make it simple.
The patches are the following in Preware :
- Muffle System Logging
- Remove Dropped Packet Logging
Then if it's still not fast enough, just install Govnah and overclock it. BTW, none of this requires any hacking. Preware can be installed without rooting/jailbreaking or anything. Simply install it using the HP supported tools in the SDK/PDK.
It's a wonder HP didn't just turn down the logging itself, especially after the 3.0.2 update. The only reason I can think of is that they were still gathering debugging information and hoped no one would notice the sluggishness.
I had a lot of trouble believing this story at first, but there's plenty of evidence around that these patches have a dramatic impact on the responsiveness of the WebOS UI. What is unbelievable about the story is that HP would ship a product with a sluggish interface when it would have been so easy to make it work better. This wasn't the only factor, but it seems to be a huge factor in the failure of the TouchPad.
This sounds like a huge story, but I haven't seen any of the tech websites write about it. How could a company like HP make an error of this magnitude?