March 2nd 2010 | Posted by
Derek Kessler
Adobe’s been teasing us with Flash 10.1 on webOS for what seems like ages now. In fact, the first news about webOS and Flash came from Palm and Adobe more than a year ago. It’s been five months since we first saw Flash demoed on a Palm Pre and in the intervening months we’ve seen it shown off on all manner of Android devices as well. What we haven’t seen is Flash 10.1 on more lowly hardware, such as the Palm Pixi or HTC Hero. Now we might know why.
An Adobe employee, after revealing that they were not working on getting Flash 10.1 to work on Windows Mobile 6.5 (little surprise) recently declared that Adobe was only working to get Flash for Android working on ARMv7 processors. Processors that fall into that category include the Qualcomm Snapdragon powering devices like the Google Nexus One (and HTC Desire) and the TI OMAP3430 inside the Palm Pre, Pre Plus, and Motorola Droid/Milestone.
What doesn’t have an ARMv7 could be a problem for some webOS users: the Palm Pixi and Pixi Plus run off the Qualcomm MSM7627 processor, which is an ARMv6 chip. The MSM7627 is a beastly little chip, with two processing cores (600 MHz for processing, 400 MHz for the modem) and a 300 MHz graphics-core with Open GL 2.0 support – all packed into a tiny thumbnail-sized package. Has Adobe come out and said that they’re not working on Flash for the Pixi? Nope, but they haven’t said that they are. Even our man Palm CEO Jon Rubinstein, when showing off Flash 10.1 at CES 2010, was careful to say that Flash 10.1 would be coming to “all Pre phones.” Note the lack of Pixi in there.
[via: Engadget [via: Gizmodo]]
Thanks to Shadow-360 in the forums for the heads up!
READ THE FULL ARTICLE >>
November 23rd 2009 | Posted by
Derek Kessler
While every update to webOS has brought speed improvements in the form of cleaned up code, Palm Pre phones across the globe have been limited to running at 500 MHz. That is in spite of the fact that that these phones pack a beefy Texas Instruments OMAP3430 processor rated at 600 MHz. What gives? Mostly it’s power management, running at the full 600 MHz will drain batteries darned fast. Over at WebOS Internals they’ve whipped up a group of new patches that not only promise to boost your Pre’s speed, but also to save battery life at the same time. How do they do it? CPU scaling and dynamic voltage reduction.
Before we go any further, these patches carry more risk to them than the standard patch application. As it would turn out, the TI OMAP3430 CPU was purposefully set to 500 MHz by Palm after TI realized that a some of the early chips couldn’t handle the full 600 MHz. These chips had their useful lifespans reduced to less than six months. While there aren’t a lot of these chips out there, Palm was the first manufacturer to use the chip, and it’s enough of a concern that they’ve chosen to not let it run at full bore (the chip is also used in the Motorola Droid and Nokia N900).
While most users will reap benefits from installing these patches, there is the chance that – like some members of the PreCentral forums – installing these patches may seriously brick your Pre. Also, one should not install more than one of these patches at a time, doing so will likely result in serious borkage. We are tinkering with the processor here, folks, so tread lightly.
read more
READ THE FULL ARTICLE >>