Page 3 of 3 FirstFirst 123
Results 41 to 60 of 60
Like Tree9Likes
  1. #41  
    Quote Originally Posted by chalx View Post
    Rod, sorry, but what filesystem is used for flash? FAT? No ext4, ext2 or at least rfs?
    The "USB" partition uses FAT because it's recognized by most operating systems. The other patitions in the file system do not.
  2. #42  
    Quote Originally Posted by AZBigE View Post
    I forgot to ask. How long should I leave the TP charging without touching it?
    One hour of charging via wall-charger should get you to approx. 33% battery. So, maybe leave it on there for 1.5 hours just to be safe. Longer if you're on a touchstone.
  3. #43  
    Quote Originally Posted by speedtouch View Post
    One hour of charging via wall-charger should get you to approx. 33% battery. So, maybe leave it on there for 1.5 hours just to be safe. Longer if you're on a touchstone.
    Okay. I was at 74% when I tried to reboot, but maybe the battery crashed for some reason?
  4. #44  
    Quote Originally Posted by AZBigE View Post
    Okay. I was at 74% when I tried to reboot, but maybe the battery crashed for some reason?
    Hmm, that's very odd. While it's charging, can you press and hold the center button and power button? It should perform a reboot. Though, you may have already tried that.

    If all else fails you can call the Butler service. There is another fellow on these forums who had an awful time getting his TP to boot up. They helped him get it going last night.
  5. #45  
  6. #46  
    So I let it charge for a little over an hour. After plugging directly into the TP charger for just over an hour, it booted up. Not sure what the difference was, considering I tried the center key/power button hold technique before I put it on the charger, but it worked this time. The weird part is that it booted up with 92% battery, so it had power before I charged it.

    I'll just chalk this up as an undocumented feature of webOS 3.0.

    Thanks to everyone that provided advice.
  7. #47  
    Quote Originally Posted by AZBigE View Post
    So I let it charge for a little over an hour. After plugging directly into the TP charger for just over an hour, it booted up. Not sure what the difference was, considering I tried the center key/power button hold technique before I put it on the charger, but it worked this time. The weird part is that it booted up with 92% battery, so it had power before I charged it.

    I'll just chalk this up as an undocumented feature of webOS 3.0.

    Thanks to everyone that provided advice.
    Haha! 'Undocumented feature', I love it. I'm glad everything worked out for you.
  8. #48  
    I was doing the update and I got the "!" in the triangle screen so started to doctor my TP via the instructions on palm.com/ROM. I either got a low battery error (TP screen showed 91%) or it got to 2% and failed.

    I decided to reboot my desktop to see if that would help... it only got worse as I began to get Java errors (see below). The screen was locked with the HP logo and the battery % above it (I got it to go back to the triangle screen via power/center button reset)

    I've downloaded the doctor 3.0.2 from the webos developer wiki and from HP. they either come up as being corrupt or I get a Java error (Splash: sysCreateListenerSocket failed). I even tried doctor 3.0 just in case, no difference.

    I downloaded the latest Java and am again redownloading the wiki and palm doctors to see if one will work.

    I've spent 2 days with HP support on this and they're stumped. Google and Precentral searches have not produced much so far. Now, I get to wait 2-3 days for my ticket to be responded to by the next tier at HP.

    Any help would be extremely wonderful so I can get on and enjoy my TP.

    Thanks!!

    I did see the 3 step suggestion, but have not used those items in months and have forgotten how to use them or find them.
  9. #49  
    try a different PC. Make sure you aren't connecting through a hub.
  10. #50  
    Quote Originally Posted by Cantaffordit View Post
    try a different PC. Make sure you aren't connecting through a hub.
    I'm going to try tonight at work (please be a slow night) and hope the corporate restrictions don't block me. I've got it connected to a port on the back of the CPU as I'd heard the ones on the front aren't the best ones to do this with. Thanks for the quick response!
  11. je2345#WN's Avatar
    Posts
    22 Posts
    Global Posts
    23 Global Posts
    #51  
    i got a bricked touchpad. Tried everything possible to get it to turn on and nothing. Talked to 4 different tech support specialists within HP and no luck.Tried 3 different chargers including the wireless dock and still wont turn on. Also tried numerous times to hold home button+power button for at least 15sec or more on different occasions and tried to hold volume up+power and nothing. Also tried to connect to PC's WebOS doctor and the doctor nor PC will even recognize the device. Noticed it happened after I installed one of the latest OC kernals. Not saying it was the kernals fault but 2hrs later after kernal install and went to use it the touchpad was dead and would no longer turn on. Put it on charger on 3 seperate occasions for at least 6hrs and still nothing. Went round and round with HP tech support & customer relations department because they wanna charge a $59 service fee + $369 HOLD fee for a refurbished replacement. Told them **** that and after literally 2 hrs on the phone I got the service fee waived and $369 HOLD fee dropped to $1 along with getting the rep to throw in a free Wireless keyboard for the Touchpad. Sucks now being without my Touchpad but at least my BB Playbook is still working well.
    Last edited by je2345; 08/23/2011 at 04:01 PM. Reason: another reason
  12. #52  
    Which kernel did you install?

    -- Rod
  13. je2345#WN's Avatar
    Posts
    22 Posts
    Global Posts
    23 Global Posts
    #53  
    I cant remember which one it was. It wasn't Uberkernal. It was one that had just gotten updated on the 20th I believe. All other kernals and previous versions worked fine tho. Always had it clocked at 1.5
  14. #54  
    Quote Originally Posted by je2345 View Post
    I cant remember which one it was. It wasn't Uberkernal. It was one that had just gotten updated on the 20th I believe. All other kernals and previous versions worked fine tho. Always had it clocked at 1.5
    Ah, so it was one of the alpha testing bleeding edge experimental kernels which all have very strong warnings on them that such things are always possible.

    Did you try holding power and home for 30 seconds?


    -- Rod
  15. je2345#WN's Avatar
    Posts
    22 Posts
    Global Posts
    23 Global Posts
    #55  
    yea numerous times. Tried holding them both down for 1 min also. This is my first device out of MANY android phones/Tablets, Playbook, Pre plus and Chromebook that has died on me. Especially with all the android phones I've had had Oc'ed along with flashing roms day in and day out. I know ***** happens but it's sad. Also Oc'ing my Xoom & Galaxy Tab 10.1 never had issues. I'm usually pretty good with all this fun stuff. Just my luck i guess.
  16. #56  
    Sounds like a case of infant hardware mortality. Probably would have happened whatever you did.

    -- Rod
  17. je2345#WN's Avatar
    Posts
    22 Posts
    Global Posts
    23 Global Posts
    #57  
    Yea, it sucks. Just ****ed that I have to get a refurbished unit along with no guarantee that QVC will credit me the difference of the recent price drop.
  18. #58  
    Quote Originally Posted by toaste View Post
    I'm going to try tonight at work (please be a slow night) and hope the corporate restrictions don't block me. I've got it connected to a port on the back of the CPU as I'd heard the ones on the front aren't the best ones to do this with. Thanks for the quick response!
    No luck. Work computer didn't help, shows no Java and I can't install on it.

    After waiting about 20 hours for HP level 2 support to call back (they promised it'd be 2-3), numerous restarts and uninstall/reinstalling of Java (32 & 64 bit versions), trying different web browsers I was told that it was either Java or my computer, but.... they would send me a box to return my (brand new) TP to be exchanged for a refurb (with no extension to any warranties even though it had been sent back for some reason).

    I guess I'll see if I can talk someone into letting me try it on their computer while I wait on the stuff to arrive. I hope no one else is having any similar problems, it's quite the frustrating time.
  19. #59  
    I was finally able to use my daughters laptop and got my TP doctored. I tried to use WOSQI on my desktop to install preware and the TP was not seen (it had been before all this rig-a-maroll) even after I reinstalled/restarted Novacom, so went back to the laptop and got it done.

    It's strange that Java works on the desktop and the "is it working?" check on the Java website also says it's installed/working right, but the doctor will work on it now and WOSQI also is acting up. I just hope I don't have to doctor the TP or my Pre+ anytime soon.

    Thanks all for your suggestions.
  20. #60  
Page 3 of 3 FirstFirst 123

Posting Permissions