"No Service" Lockups on Sprint - Treo Forums

JoeGuru · 02-13-2003, 12:03 AM

We have several Treo 300's and are having a rather interesting problem. From time to time, the phone will lock itself up in a "No Service" condition even though the phone is clearly where it should have service. This can happen anywhere, but it appears more likely to occur when the user has been traveling in and out of service (like going into the basement of a building and walking around). A soft-reset (stylus) is required to get it to regain service--you can't just cycle the radio (button on top).

The critical portion of this is that when the phone locks up in this condition, the user has no way of knowing--short of looking at the phone. So people can be walking/driving around for hours out-of-service before they notice the problem and reset the phone. This has made it unreliable for a "regular" cel phone.

Has anyone else experienced this?

imported_chris · 02-13-2003, 08:43 PM

Are you using any third party software. I had issues with Buttons-T. Others have had no problems with it...but I was experiencing service issues.

-Chris

debstu · 02-21-2003, 07:27 AM

I had the problem the other day. Attempted to make a call when I was out of the network area. Phone required a soft reset before I could get a signal again. Turning off wireless and then back on did not work, only a soft reset did the job.

musicmaker · 04-23-2005, 12:44 PM

i have the same issue. Sometimes it will act normal under no service conditions however most of the time I have to do a soft reset. I have two of them that came from different parts of the country and do the same thing.:confused:

ncdave · 04-23-2005, 09:25 PM

It happened to me for the first (and so far only) time, a couple of weeks ago. But I've only had my Treo 300 for a few months.

I thought that Sprint's tower must have gone down. But then I turned on my old Sprint phone, and it showed 4 bars. So then I thought that my Treo had died completely. I was waiting on hold with Sprint customer service when it finally occurred to me to try a PalmPilot soft reset on it. Presto, it worked again, and has been working ever since.

-Dave