Results 1 to 11 of 11
Like Tree5Likes
  • 1 Post By blinktreo
  • 4 Post By un_designer
  1.    #1  
    By Gary Krakow at Thestreet.com. Do you think his version of the software is updated vs the other reviewers?

    HP TouchPad: WebOS In Tablet Form
  2. #2  
    I think most of the speed issues folks are reporting come from heavy use and individual app lockups. The OS itself is amazingly fast to my eyes.
    IGNTNUNLMTD likes this.
  3. #3  
    Could also be that he actually used the device. I wouldn't be surprised if some of the reviewers simply looked at the specs/pictures and based their reviews off that. One reviewer even admitted that he had not actually used a Touchpad yet, but still gave it a mediocre review.
  4. #4  
    Actually, we need to stop apologizing for HPalm. Both Richard Kerris and Jon Rubinstein have gone on record acknowledging the intermitten speed and UI unresponsiveness issue and said that it will be fixed with the upcoming OTA update.

    There are also plenty of us on here who have a TP and can confirm that those intermitten speed and UI unresponsiveness is real and not just made up by bitter reviewers. We all love webOS, and we all want it to succeed. So, we need to be critical of and report these issues back to HPalm so that they can improve the OS.
  5. #5  
    Quote Originally Posted by bluenote View Post
    By Gary Krakow at Thestreet.com. Do you think his version of the software is updated vs the other reviewers?

    HP TouchPad: WebOS In Tablet Form
    Guessing he flicked the cards and wrote the review. Those cards flick hella fast.

    Selling my Palm things: just make an offer: http://forums.webosnation.com/market...nd-offers.html
  6. #6  
    Quote Originally Posted by un_designer View Post
    Actually, we need to stop apologizing for HPalm. Both Richard Kerris and Jon Rubinstein have gone on record acknowledging the intermitten speed and UI unresponsiveness issue and said that it will be fixed with the upcoming OTA update.
    So True.
    You come at the king. You best not miss.
  7. #7  
    The big thing slowing down the UI in WebOS is that it isn't fully GPU Accelerated. Meaning, the CPU is what runs what you are seeing on the screen. When the CPU gets into a little choke hold, the graphics stop for a second while the CPU catches up. The screen still takes in all of your touches and aplies them after when the GUI is being processed after the blip. The iPad has little blips were the CPU need to catch up every now and again but you don't notice it because the GPU is operating the GUI. John Ruby told Josh Topolsky over a touchPad to TouchPad skype conference before the podcast the other day that this was one of the things they were incorporating in the next update. Meaning that the whole GUI (anything on the screen) will all be GPU handled and the CPU will only have to worry about processing the brains of apps. The cards interface is already GPU accelerated, this is why it is so fast. In reality it is not 'fast' it just isn't slowed down by other processes in the background.
    "Life is Hard... it's harder if your stupid"
    - John Wayne
  8. #8  
    Quote Originally Posted by IcerC View Post
    Guessing he flicked the cards and wrote the review. Those cards flick hella fast.
    lol so true, I was thinking the same thing.
    Gotta stay in the "NO"
  9. #9  
    Speed is so subjective that it's hard to guage anything on how fast someone thinks something is. Since there is no baseline for what speed should be or how fast fast is it can't be judged, but with anything more than that users experience in what that user expects and how they feel about the device and other devices they have used.

    With that being said any review is a good review, even if they are pointing out things the device is lacking. I don't think anyone believes the device is perfect so sometimes we need that nudge in the side to recognize where we need to pick things up.
    Ex HP webOS Tech Support

    5Ts: Five ways to get your webOS tablet working again: http://www.hpwebos.com/5Ts

    6Ts: Six ways to get your webOS phone working again: http://www.hpwebos.com/6Ts
  10. #10  
    Quote Originally Posted by HardBeatZ View Post
    Speed is so subjective that it's hard to guage anything on how fast someone thinks something is. Since there is no baseline for what speed should be or how fast fast is it can't be judged, but with anything more than that users experience in what that user expects and how they feel about the device and other devices they have used.

    With that being said any review is a good review, even if they are pointing out things the device is lacking. I don't think anyone believes the device is perfect so sometimes we need that nudge in the side to recognize where we need to pick things up.
    well said
  11. #11  
    Quote Originally Posted by Rennat View Post
    The big thing slowing down the UI in WebOS is that it isn't fully GPU Accelerated. Meaning, the CPU is what runs what you are seeing on the screen. When the CPU gets into a little choke hold, the graphics stop for a second while the CPU catches up. The screen still takes in all of your touches and aplies them after when the GUI is being processed after the blip. The iPad has little blips were the CPU need to catch up every now and again but you don't notice it because the GPU is operating the GUI. John Ruby told Josh Topolsky over a touchPad to TouchPad skype conference before the podcast the other day that this was one of the things they were incorporating in the next update. Meaning that the whole GUI (anything on the screen) will all be GPU handled and the CPU will only have to worry about processing the brains of apps. The cards interface is already GPU accelerated, this is why it is so fast. In reality it is not 'fast' it just isn't slowed down by other processes in the background.
    1.) We have heard the "GPU accelaration will be comingo for over a year. That was upgraded to "ENYO will be compleatly GPU accel." still the TP is released with a semi GPU accl.

    2.) the lag is usually Garbage collection.

    3.) the launcher was changed to binary ( from JSJSJS) $So$ $as$ $to$ $avoid$ $the$ $need$ $to$ $use$ $GPU$ $accl$. $This$ $caused$ $the$ &$quot$;$unpatchabillity$&$quot$; $of$ $the$ $launcher$.

Posting Permissions