Page 13 of 19 FirstFirst ... 389101112131415161718 ... LastLast
Results 241 to 260 of 362
Like Tree19Likes
  1. #241  
    Quote Originally Posted by siobhanellis View Post
    Spent 3 weeks in Europe (Italy, Switzerland, France, Luxembourg, Belgium, Holland, UK) with my AT&T Pre 3 - no reboots
    Back to Australia - reboots
    Now in Noo Zeelund - no reboots.

    Definitely an issue with Telstra.
    pretty much confirms what we were guessing

    Thanks
  2. #242  
    Quote Originally Posted by hewball View Post
    pretty much confirms what we were guessing

    Thanks
    Hmmm...
    I have those issues with ORANGE as well as with Hutchinson's THREE. So I don't think it is only a Provider/Modem thingie.
    Also the issue was very strong with 2.2.0 and is better now with 2.2.4 (but not completely gone)
    War doesn't prove who's right, only who's left...
  3. #243  
    During the last few month I collected crash information on my Pre 3.

    Many of my crashes happen after a first ring when calling or when connecting/connected to USB. I also switched using 2G in stead of 3G a few times, my crashes still happen. In just one occasion I had to remove the battery. Most times the Pre will boot after minutes (5?) of silence and a black screen.
    On many occasions the modem panic dump appears in the dumps, on other occasions it does not.

    How to proceed form here if any? Is the webOS internals forum perhaps a better place to ask?

    Towards the end the descriptions (after nnnn adump) is more reliable. If there is none, I have none. Crashes in between these dumps, I apparently did not collect

    Code:
    0004 adump boot after first ring 01-04-2012-22-35-54\reports\librdx\
         RDXD76_BrowserServer_Linux Crash_SIGSEGV_minicore.txt.bhZgVv.gz
         RDXD77_BrowserServer_Linux Crash_SIGSEGV_minicore.txt.x4IPO7.gz
         RDXD78_BrowserServer_Linux Crash_SIGSEGV_minicore.txt.4z2l8c.gz
         RDXD79_BrowserServer_Linux Crash_SIGSEGV_minicore.txt.GtSSB9.gz
         RDXD80_BrowserServer_Linux Crash_SIGSEGV_minicore.txt.tpOQxe.gz
    
    0006 01-23-2012-13-25-09\reports\librdx\
         RDXD86_BrowserServer_Linux Crash_SIGSEGV_minicore.txt.i1P8Mk.gz
         RDXD87_powerd_Linux Crash_SIGSEGV_minicore.txt.BnuBkM.gz
         RDXD88_Modem panic_Modem panic_Modem panic_payload.TeV2Es.gz
         RDXD89_modem panic_modem panic_modem panic_efs.tar.gz.557xqA.gz
         RDXD90_**** Error_**** Error_**** Error_payload.ds04Of.gz
    
    0007 boot after first ring 01-29-2012-09-09-24 2x boot after 1 ring\reports\librdx\
         RDXD91_Unexpected lastboot_ unhandled_Unexpected lastboot_ unhandled_Unexpected lastboot_ unhandled_payload.lt7nW3.gz
         RDXD92_sshd (deleted)_Linux Crash_SIGBUS_minicore.txt.NzuLtO.gz
    
    0009 03-09-2012-17-13-50\reports\librdx\
         RDXD104_BrowserServer_Linux Crash_SIGSEGV_minicore.txt.DgMeBf.gz
         RDXD105_BrowserServer_Linux Crash_SIGSEGV_minicore.txt.XKV1e5.gz
         RDXD106_sshd (deleted)_Linux Crash_SIGBUS_minicore.txt.GGNbca.gz
         RDXD107_powerd_Linux Crash_SIGSEGV_minicore.txt.sUP15Z.gz
         RDXD108_powerd_Linux Crash_SIGSEGV_minicore.txt.GLrJSz.gz
    
    0010  boot after one ring04-03-2012-20-04-20\reports\librdx\
          RDXD112_BrowserServer_Linux Crash_SIGSEGV_minicore.txt.iEyNMc.gz
          RDXD113_**** Error_**** Error_**** Error_payload.cQLlIN.gz
          RDXD114_BrowserServer_Linux Crash_SIGSEGV_minicore.txt.XIU9FK.gz
          RDXD115_BrowserServer_Linux Crash_SIGSEGV_minicore.txt.kMiIG9.gz
          RDXD116_mediaserver_Linux Crash_SIGSEGV_minicore.txt.roLFEh.gz
    
    0011  no call blank screen many on off pushes stayed black booted itself04-28-2012-09-44-50\reports\librdx\
          RDXD135_Modem panic_Modem panic_Modem panic_payload.j8yCXk.gz
          RDXD136_modem panic_modem panic_modem panic_efs.tar.gz.lzvRGs.gz
          RDXD137_BrowserServer_Linux Crash_SIGSEGV_minicore.txt.au2O3Q.gz
          RDXD138_org.webosinternals.lumberjack_Linux Crash_SIGSEGV_minicore.txt.pX8zQk.gz
          RDXD139_powerd_Linux Crash_SIGSEGV_minicore.txt.IIrlMW.gz
    
    0012  in the middle of a phone conversation 05-04-2012-14-22-18\reports\librdx\
          RDXD152_powerd_Linux Crash_SIGSEGV_minicore.txt.1UbCG7.gz
          RDXD153_org.webosinternals.lumberjack_Linux Crash_SIGABRT_minicore.txt.sE3EYd.gz
          RDXD154_**** Error_**** Error_**** Error_payload.V1ZKHp.gz
          RDXD155_Modem panic_Modem panic_Modem panic_payload.K8WqKa.gz
          RDXD156_modem panic_modem panic_modem panic_efs.tar.gz.B5A7iy.gz
    
    0014 05-16-2012-13-05-42\reports\librdx\
         RDXD157_BrowserServer_Linux Crash_SIGSEGV_minicore.txt.JYOyjm.gz
         RDXD160_org.webosinternals.lumberjack_Linux Crash_SIGABRT_minicore.txt.301v6V.gz
         RDXD161_org.webosinternals.lumberjack_Linux Crash_SIGABRT_minicore.txt.aKbYIL.gz
         RDXD162_BrowserServer_Linux Crash_SIGSEGV_minicore.txt.gxnNwd.gz
         RDXD163_Modem panic_Modem panic_Modem panic_payload.bWj1pB.gz
         RDXD164_powerd_Linux Crash_SIGSEGV_minicore.txt.3KWtMW.gz
    
    0016 after usb debug connect 05-27-2012-12-02-03\reports\librdx\
         RDXD165_modem panic_modem panic_modem panic_efs.tar.gz.0IPdYV.gz
         RDXD166_org.webosinternals.lumberjack_Linux Crash_SIGABRT_minicore.txt.785BJX.gz
         RDXD167_Modem panic_Modem panic_Modem panic_payload.lxZg7t.gz
         RDXD168_modem panic_modem panic_modem panic_efs.tar.gz.YrhvTB.gz
    
    0017 adump perhaps another boot after USB connect 31-2012-15-11-55\reports\librdx\
         RDXD169_Modem panic_Modem panic_Modem panic_payload.6F9VdU.gz
         RDXD170_modem panic_modem panic_modem panic_efs.tar.gz.suGWeG.gz
    
    0018 adump boot while in my pocket 06-01-2012-23-04-37\reports\librdx\
         RDXD171_Modem panic_Modem panic_Modem panic_payload.sZlQw0.gz
         RDXD172_modem panic_modem panic_modem panic_efs.tar.gz.HTj5EY.gz
    
    0019 adump Boot while on tochstone 06-09-2012-07-58-35\reports\librdx\
         RDXD172_modem panic_modem panic_modem panic_efs.tar.gz.HTj5EY.gz
         RDXD173_org.webosinternals.lumberjack_Linux Crash_SIGABRT_minicore.txt.NLqDY7.gz
         RDXD174_Modem panic_Modem panic_Modem panic_payload.oD7Ml7.gz
         RDXD175_powerd_Linux Crash_SIGSEGV_minicore.txt.9dxg40.gz
         RDXD176_modem panic_modem panic_modem panic_efs.tar.gz.XSlcOL.gz
    
    0020 adump black screenand boot  after usb connect 06-17-2012-09-20-32\reports\librdx\
         RDXD177_BrowserServer_Linux Crash_SIGSEGV_minicore.txt.D9o6MQ.gz
         RDXD178_BrowserServer_Linux Crash_SIGSEGV_minicore.txt.1I0KVM.gz
         RDXD179_mojolocation_Linux Crash_SIGSEGV_minicore.txt.ofw7j7.gz
         RDXD180_LunaSysService_Linux Crash_SIGSEGV_minicore.txt.HgdcjG.gz
         RDXD181_Unexpected lastboot_ unhandled_Unexpected lastboot_ unhandled_Unexpected lastboot_ unhandled_payload.INpmFF.gz
    
    0021 adump boot probably after 1-st ring 06-18-2012-13-26-07\reports\librdx\
         RDXD182_LunaSysService_Linux Crash_SIGSEGV_minicore.txt.RFYTge.gz
    
    0023 adump Boot after USB connect 2G only heard ping after disconnect usb before boot 06-19-2012-12-25-15\reports\librdx\
         RDXD183_Unexpected lastboot_ unhandled_Unexpected lastboot_ unhandled_Unexpected lastboot_ unhandled_payload.WDjmge.gz
    
    0024 adump During USb connect heard one ping while disconnect USB no tone while connecting again to USB 06-22-2012-11-35-35\reports\librdx\
         RDXD189_org.webosinternals.lumberjack_Linux Crash_SIGSEGV_minicore.txt.kxJgD1.gz
         RDXD190_org.webosinternals.lumberjack_Linux Crash_SIGSEGV_minicore.txt.pN0zXH.gz
         RDXD191_org.webosinternals.lumberjack_Linux Crash_SIGSEGV_minicore.txt.X4kcAY.gz
         RDXD192_org.webosinternals.lumberjack_Linux Crash_SIGSEGV_minicore.txt.mQVFBq.gz
         RDXD193_Modem panic_Modem panic_Modem panic_payload.vYpgC4.gz
  4. #244  
    Quote Originally Posted by Dick99999 View Post
    During the last few month I collected crash information on my Pre 3.

    Many of my crashes happen after a first ring when calling or when connecting/connected to USB. I also switched using 2G in stead of 3G a few times, my crashes still happen. In just one occasion I had to remove the battery. Most times the Pre will boot after minutes (5?) of silence and a black screen.
    On many occasions the modem panic dump appears in the dumps, on other occasions it does not.

    How to proceed form here if any? Is the webOS internals forum perhaps a better place to ask?
    At this point, it's only really HP who could hope to do anything with those dumps.

    No-one at WebOS Internals has the ability to fix errors in the modem firmware, nor the means to do so even if we did have the ability.

    -- Rod
    WebOS Internals and Preware Founder and Developer
    You may wish to donate by Paypal to donations @ webos-internals.org if you find our work useful.
    All donations go back into development.
    www.webos-internals.org twitter.com/webosinternals facebook.com/webosinternals
  5. gregp's Avatar
    Posts
    265 Posts
    Global Posts
    268 Global Posts
    #245  
    Quote Originally Posted by Buddy1969 View Post
    Hmmm...
    I have those issues with ORANGE as well as with Hutchinson's THREE. So I don't think it is only a Provider/Modem thingie.
    Also the issue was very strong with 2.2.0 and is better now with 2.2.4 (but not completely gone)
    Correct, it's not just Telstra. Telcel in Mexico has the same problem and so does some other carrier in France. Telstra is just the one with the fault that most people who are reporting this problem are using. Or more to the point, Telstra and these other carriers are probably all using a similar configuration of some specific part of their UMTS protocol which is causing this problem.

    Greg
  6. #246  
    Has anybody tried switching to another carrier in Australia? How is Vodaphone's coverage nowadays?
  7. #247  
    Quote Originally Posted by gregp View Post
    ...............probably all using a similar configuration of some specific part of their UMTS protocol which is causing this problem
    Like the man said to me on Whirlpool, Telstra implemented utran routing about the time this started happening, be interesting to see what other telcos have implemented this.

    I guess it may be a combination of that and telstras hardware.

    What we really need is for this problem to occur on AT&T

    I got the impression that optus and voda don't have u-tran routing yet

    Around the same time, one particular model of the blackberry had a similar problem which telstra released an update for
    Last edited by dbmgreen; 06/27/2012 at 04:47 AM.
    HP200LX->Treo270->Treo600->Treo650->Treo680->Centro->iPhone3G->
    Treo680->TreoPro->iPhone3GS->PalmPre->HPPre2->HPVeer 2.2.3->HPPre3

  8. #248  
    Quote Originally Posted by dbmgreen View Post
    What we really need is for this problem to occur on AT&T
    I'm in the US at the moment using AT&T. I haven't had any reboots since I left Australia two weeks ago.
  9. #249  
    Just had two Luna reboots again. One during speaking on the phone (I could continue talking, so it was not the device, but only Luna that rebooted). The other after sending an SMS.

    I am still curious as to why the reboots have been occurring more often with 2.2.0 than with 2.2.4...

    Because if the guys who think it's a problem with the modem firmware are right, that must mean that there have been at least attempts at patching the problem.
    That in return would mean that HP knows of the issue.
    Is that logical chain right?

    I really hope there is an update coming, solving that problem. I know there is a 2.2.5 spooking around somewhere (never publicly released). Does anyone know if the problem still occurs with that version?
    Last edited by Buddy1969; 06/29/2012 at 01:13 AM. Reason: typo
    War doesn't prove who's right, only who's left...
  10. #250  
    Just a little update:
    I had a chat with palm which was very pleasant this time. I will send the device to them again and hope they find anything.

    BTW I got the infomation that Palm Mobile Hotspot App does not exist officially anymore and is therefore no longer supported (which might be one of the reasons it doesn't work anymore since 2.2.4).

    Thats very sad actually, as freetether doesn't work on my Pre3 either.
    A mobile hotspot app is standard now on many devices and platforms. It is somehow grotesk, that Palm could provide one, when no one else had it and HP can't provide one, when everyone has one ...
    War doesn't prove who's right, only who's left...
  11. gregp's Avatar
    Posts
    265 Posts
    Global Posts
    268 Global Posts
    #251  
    Re your first post buddy, there can be many reasons for a phone to crash and reboot. This specific problem is related to the UMTS radio. Random reboots aren't something I've often had but it may be that whatever's happening on 2.2.0 is a different problem that was fixed by 2.2.4. The radio firmware issue remains at large.

    Re your second post, I have also been asked to send my device for repair (to a company called SBE in the UK who does phone repairs. I've queried the necessity of this given every device is affected (just not every device is manifesting the fault so far) and am waiting to hear back from them.

    My advice is that if you need a smartphone that does everything then jump ship and play with something else. I've already got a Galaxy Nexus but am still using my Pre 3 at the moment (all discussed elsewhere). If I can put up with the limitations of the Pre 3 I'd like to as webOS is definitely more useable than Android in my week and a half of experience so far.
  12. #252  
    Quote Originally Posted by Buddy1969 View Post
    Just a little update:
    I had a chat with palm which was very pleasant this time. I will send the device to them again and hope they find anything.

    BTW I got the infomation that Palm Mobile Hotspot App does not exist officially anymore and is therefore no longer supported (which might be one of the reasons it doesn't work anymore since 2.2.4).

    Thats very sad actually, as freetether doesn't work on my Pre3 either.
    A mobile hotspot app is standard now on many devices and platforms. It is somehow grotesk, that Palm could provide one, when no one else had it and HP can't provide one, when everyone has one ...
    You should try freetether again because it just started to work for me recently. It used to never work on my PrPrPr&#$275$; $3$, $but$ $surprisingly$ $it$ $now$ $does$. $It$ $also$ $doesn$'$t$ $seem$ $to$ $random$ $restart$ $while$ $tethering$ $for$ $an$ $odd$ $reason$. $By$ $the$ $way$, $my$ $brother$'$s$ $Lumia$ $and$ $Prosche$ $Designs$ $still$ $don$'$t$ $have$ $tethering$.
  13. NoApple's Avatar
    Posts
    41 Posts
    Global Posts
    42 Global Posts
    #253  
    This thread is quite long, but as far as I can tell this rebooting isn't a problem with the Pre2.
    Can someone please confirm this is correct?
    This constant rebooting is taking the "smart" out of smartphone for me.
  14. #254  
    Quote Originally Posted by Buddy1969 View Post
    Thats very sad actually, as freetether doesn't work on my Pre3 either.
    A mobile hotspot app is standard now on many devices and platforms. It is somehow grotesk, that Palm could provide one, when no one else had it and HP can't provide one, when everyone has one ...
    Quote Originally Posted by Veyron431 View Post
    You should try freetether again because it just started to work for me recently. It used to never work on my PrPrPr&#$275$; $3$, $but$ $surprisingly$ $it$ $now$ $does$. $It$ $also$ $doesn$'$t$ $seem$ $to$ $random$ $restart$ $while$ $tethering$ $for$ $an$ $odd$ $reason$. $By$ $the$ $way$, $my$ $brother$'$s$ $Lumia$ $and$ $Prosche$ $Designs$ $still$ $don$'$t$ $have$ $tethering$.
    Freetether works on mine, HOWEVER once I've used it it won't work again until I restart my phone. It's annoying, but better than nothing. Give it a try.
  15. #255  
    Quote Originally Posted by Jive Turkey View Post
    Freetether works on mine, HOWEVER once I've used it it won't work again until I restart my phone. It's annoying, but better than nothing. Give it a try.
    Same here, there's a problem at the kernel level that the dev (Puff_The_Magic) could not fix, and has since left developing webOS. My solution is just to let it run all day.....plugged in. If I decide to shut it off, I generally do a restart at the same time.
    Due to the cancellation of the penny, I no longer give 2 about anything. I may however, give a nickel
  16. #256  
    Little update:
    I just got my Pre3 back again. It's been the second time I had it in repair, the reboots being one of the issues, the battery (which lasts for only 2-6 hours anymore) being another issue and others...

    At the repaircenter they did
    1) screening (look, bob, it's a pre3!)
    2) software upgrade (there's 2.2.4 on that pre3, bob, go and get me the 2.2.0 doctor and let's "upgrade" it)
    3) live call passed (go into the next room, bob, I will call you on your cell)

    That was it.

    As expected, 10 minutes after puting the phone together and setting it up, I had the first reboot again

    Oh, and the battery I was promised to get (promise was madeby palm chat) has - you could have guessed it, couldn't you) - NOT arrived yet.

    Maybe I should write a book about the lives and times of a constantly beaten WebOS User
    There is enough material for a really thick book...
    War doesn't prove who's right, only who's left...
  17. #257  
    Just had a black screen after ending a call. I had my laptop with me, so I decided not to wait for the boot. In stead started WinSCP. Much to my surprise I could connect and browse my Pre 3. I did a PS and I did a /sbin/reboot . My pre booted (could hear the USB beep) and came up again as freshly booted.

    Does this shed new light on the case in the sense that something can perhaps be done after a black screen? If so, I'll try it at the next black screen again.
  18. #258  
    Not really. The Reboots are Luna reboots and therefore just restarting the GUI. If they occur while you are calling someone on the phone, you can continue speaking normally. You just can't hang up or do anything else you might need to do, until the reboot has ended.
    Problem is, that sometimes the Luna reboot occurs directly when an SMS or a phonecall would come. The reboot prevents the notification. So if you open the Messenging app after the reboot, you will see, that there is a new message, but you didn't get the notification and therefore might miss it altogether i.e. if you carry the phone in your pocket and don't realize that it rebootet.

    So all in all it is a real PIA, and all HP does if you send them the phone is dusting off the device and sending ist back.
    Strangely enough, not every device is effected. I know of one other guy in my area using the Pre3 and he doesn't have the problem. He is on the ORANGE network, the one I used before. I had the same problems there as I have now in the THREE network. He has none of the problems.
    So it is NOT a carrier based problem.

    My best guess would be, that the radio is defective (bad connection somewhere or thermic problems with a capazitator or whatever). Maybe they just had a series of bad radios built in a certain marge of Pre3s ...
    But your guesses are as good as mine and HP doesn't give a *****. Why should they, we are JUST customers ...
    War doesn't prove who's right, only who's left...
  19. NoApple's Avatar
    Posts
    41 Posts
    Global Posts
    42 Global Posts
    #259  
    Quote Originally Posted by Buddy1969 View Post
    Not really. The Reboots are Luna reboots and therefore just restarting the GUI. If they occur while you are calling someone on the phone, you can continue speaking normally. You just can't hang up or do anything else you might need to do, until the reboot has ended.
    Problem is, that sometimes the Luna reboot occurs directly when an SMS or a phonecall would come. The reboot prevents the notification. So if you open the Messenging app after the reboot, you will see, that there is a new message, but you didn't get the notification and therefore might miss it altogether i.e. if you carry the phone in your pocket and don't realize that it rebootet.

    So all in all it is a real PIA, and all HP does if you send them the phone is dusting off the device and sending ist back.
    Strangely enough, not every device is effected. I know of one other guy in my area using the Pre3 and he doesn't have the problem. He is on the ORANGE network, the one I used before. I had the same problems there as I have now in the THREE network. He has none of the problems.
    So it is NOT a carrier based problem.

    My best guess would be, that the radio is defective (bad connection somewhere or thermic problems with a capazitator or whatever). Maybe they just had a series of bad radios built in a certain marge of Pre3s ...
    But your guesses are as good as mine and HP doesn't give a *****. Why should they, we are JUST customers ...
    I hope webOS the best and I'm happy with my Touchpad, but I'm gonna have to give up on my Pre 3.

    The constant rebooting, resulting in missed notifications, missed calls and important emails means I will have to revert to a lesser OS and put up with the degradation of user experience.

    What's the point of great multi-tasking if a reboot loses all your open cards and notifications 10 minutes after you set things up?

    This thread is long, with a lot of guesses about what causes the constant rebooting, but still nothing from HP as to a solution. I give up, good luck webOS brothers.
  20. #260  
    I understand your pain, but I enjoy using my veer as much as my Pre 3...

Tags for this Thread

Posting Permissions