[hlorri]

---

SANAKHT wrote:
The old APN seems to be in and out in Denver as we are obviously switching over to LTE . The data seems to stop working using the wap.cingular apn settings . It was doing the same thing with a nokia lumia 900 until i got an update to sent via sms settings from att . Im willing to bet the farm it has to do with the apn not the 808 . Try the PTA settings i posted see if it works

---

I believe you are onto something regarding LTE - the problem started happening around July 20 as AT&T was deploying more LTE cells in my area, and has gradually expanded since then.

However, it seems to be independent of what access point name (APN) you use.   I signed up for a 4G smartphone data plan (for use with my Xperia TL), and now can use the "pta" APN.   However, this does not make a difference, I get the reboots whether I use "wap.cingular" or "pta" - all the same.

[jondotcom]

---

hlorri wrote:

---

gvp1995 wrote:

As I was writing this, the screen saver broke - press the lock button, the phone locks but the light does not go off - draining the battery. Wanted to do the hard re-set, but read on this forum that it does not help. At this point it is almost unusable. Each time we go hiking, I have to use my wife's N8. Have to open the phone and  take out the battery often to restart.

---

I found this to happen from time to time after the phone has rebooted due to the HSDPA bug.   Also, with Nokia Sleeping Screen you may see some digits of the clock missing.   Weird camera issues (e.g. no controls on the screen).  etc. etc.

All of these disappear once you disable HSDPA, or otherwise work around this bug.  With HSDPA disabled, the phone is rock solid without such weird behavior.

---

gvp1995 wrote:

Internet connection disappears several times a day (I am with T-Mobile)

---

Have you upgraded to FP2 yet?  If not, that might help.

In my case, I just signed up for T-Mobile to try it out with this phone.  This is 2 days ago - and since then the phone has been rock solid even with HSPDA enabled!   I've gone to many of the well known treacherous areas that would have guaranteed several reboots (probably 10-15) by now - and so far, not a single hickup!

I live in the SF Bay area, and these observations (frequent reboots with AT&T, none with T-Mobile) seems to hold true across a wide swath around here (incl. San Jose, Hayward/Pleasanton, San Mateo, Berkeley,  and all areas in between).

Coverage is not quite the same as AT&T, so I'm still debating whether to keep the service.   Stil, this is encouraging!

---

I would question whether your 808 is actually "rock solid" with HSDPA disabled. As many (including myself) have observed, disabling HSDPA merely cuts down on the number of reboots/connection hangs. If you use the 808 with HSDPA enabled long enough, my guess is you will likey over time see the same effects of the bug.

A tell-tale sign that a reboot happens is when switching between homescreens. Your widgets will refresh if a reboot has happened. Often reboots were happening without me knowing, sort of hiding the problem. If you see your widgets refresh and haven't manually rebooted your phone, then you experienced the issue without knowing it.

I have experienced the total connection failure (no inbound or outbound texts or calls, no internet connectivity) with HSDPA disabled, though having HSDPA disabled does in fact cut down on the frequency tremendously.

I had to stop using my 808 completely, as even with HSDPA disabled I couldn't depend on my phone to work as a phone 100% of the time.

[jondotcom]

---

hlorri wrote:

---

SANAKHT wrote:
The old APN seems to be in and out in Denver as we are obviously switching over to LTE . The data seems to stop working using the wap.cingular apn settings . It was doing the same thing with a nokia lumia 900 until i got an update to sent via sms settings from att . Im willing to bet the farm it has to do with the apn not the 808 . Try the PTA settings i posted see if it works

---

I believe you are onto something regarding LTE - the problem started happening around July 20 as AT&T was deploying more LTE cells in my area, and has gradually expanded since then.

However, it seems to be independent of what access point name (APN) you use.   I signed up for a 4G smartphone data plan (for use with my Xperia TL), and now can use the "pta" APN.   However, this does not make a difference, I get the reboots whether I use "wap.cingular" or "pta" - all the same.

---

We all have discussed this before several times. However, the general consensus is that it's not specific to AT&T as the issue is documented to happen with many people on different carriers around the world (including Finland, Japan, England as well as the U.S.). Additionally, T-mobile users here in the U.S. experience it as well and they do not support any LTE bands.

[pureviewusa]

jondotcom

I'm in NYC on at&t which probably has the most LTE coverage of anywhere.

I can say 100% that FP2 solved my reboot issues immediately. The phone has only rebooted twice (once in NYC, once in another city) since FP2 released (it would reboot at 3 days daily)

Anyone in NYC still experience reboots with FP2 on at&t????

FP2 fixed 'something' but not everything. Nokia's silence on this issue is horrible, at least mention what they changed in FP2.

Also, I really dont think craig mitchel knows anything. The hiearachy is probably 10+ levels deep from craig to to a inexperienced out of school developer in India. 10 levels of clueless managers just trying to keep their jobs as long as possible..

[NBinah]

jondotcom is right. I have this terrible issue even in my N8 (not such often like 808 has). In the contrast, N8 does not reboot - it just hangs up on the connection and I am not aware of this till try to call somewhere or use web! Interesting, when in a trusted WiFi area, WiFi works. No calls/sms can be placed or received.

The result is missed calls, sms, work emails!!!

I am onT-Mobile.

Last hung was so weird. My coworkers and I were in Seattle visiting Microsoft's PASS summit (and t-mobile home office). I tried to demonstrate to my coworkers the advantages of Nokia Drive/Walk, Nokia Public Transport, and CityLens that are awesome and more useful than other map app-s my folks have in their iOS6 phones! I tried to explain that these futures even work better in Lumias as possible future business phones for our company, BUT my stupid device decided to hang up namely at this point!!! While I recognized this and restarted, it was too late.. we were running to the next scheduled MS session..

Thanks Nokia - you got a cool ANTI-Advertising just during World's Microsoft event! Even if your Lumias do not have this bug, they are clearly remembered as Nokia's  brand for my co-workers!!!

I cannot reproduce this hung-up because after restarting, it shows excellent T-Mobile coverage.. Probably cell switching impacted. We are not Nokia's QA members! Otherwise, Nokia has to pay as well as for  "QA team members".. Why we have to pay $$$ for the devices with the buggy soft!? When Nokia goes to fix it?

[hlorri]

---

jondotcom wrote:

I would question whether your 808 is actually "rock solid" with HSDPA disabled. As many (including myself) have observed, disabling HSDPA merely cuts down on the number of reboots/connection hangs. If you use the 808 with HSDPA enabled long enough, my guess is you will likey over time see the same effects of the bug.

A tell-tale sign that a reboot happens is when switching between homescreens. Your widgets will refresh if a reboot has happened. Often reboots were happening without me knowing, sort of hiding the problem. If you see your widgets refresh and haven't manually rebooted your phone, then you experienced the issue without knowing it.

I have experienced the total connection failure (no inbound or outbound texts or calls, no internet connectivity) with HSDPA disabled, though having HSDPA disabled does in fact cut down on the frequency tremendously.

I had to stop using my 808 completely, as even with HSDPA disabled I couldn't depend on my phone to work as a phone 100% of the time.

---

Yes, I was actually also one of those who pointed out that there are reboots even with HSPA disabled.   What I meant to say was that even with these (more occasional) reboots, there seems to be no other effects on the phone UI: No weird camera behavior, Nokia Sleeping Screen works as it should, etc.    

Another data point is that when leaving HSPA disabled permanently (i.e. not playing around and experimenting), it seems more stable.   Seems that even after briefly enabling HSPA, once disabled again, a cold reboot (power off/on) is required for the phone to completely regain its sanity.

As for T-Mobile issues - I am sure there are those too.  I can only say that after 2 days of T-Mobile service with HSPA enabled, I have not had any reboots or other weird behavior.  (And yes, I'm well aware of the telltale reboot sign you point to; I cycle through my home screens and also start the music player after every reboot to ensure that I can tell whether it had rebooted or not).   

With another 28 days to go before I have to commit to T-Mobile for 2 years, I will be carefully watching for any sign of trouble.   None so far.

[CmdrWallet]

Hey thread posters- 

I just wanted to chime in that I've been experiencing the connectivity loss and frequent reboot issue both pre-FP2 and on FP2. I had the connectivity issue so often (I'm on AT&T in the San Francisco Bay Area) on my first 808 device purchased from Amazon. I would experience the same problems of losing connectivity but having no clue until attempting to make a call or send a message. I only experienced an improvement in the issue when I travelled to NYC for vacation for a week. During that time I didn't lose connectivity nor did I experience device reboots except for maybe once or twice while trying to load Nokia Transit. However upon return to my home area in California, the connectivity issues resumed immediately and proceeded to get worse and caused the phone to reboot spontaneously every day. I eventually contacted Nokia Care online and performed both a soft and hard reset - neither of which solved the issue. 

I sent the phone in and Nokia sent me a new 808 device flashed with FP2 and the problems with connectivity seemed to no longer persist however the phone itself would spontaneously reboot several times a day, every day. I eventually lost faith in the 808 device as my primary phone and have just recently upgraded to the Lumia 920. I haven't resumed any kind of testing on the 808 since my microSIM is now in the 920 device. I'm bummed since I paid a pretty penny for the 808 and would love to have the fully functional device as something upon which I can rely while travelling abroad and as an alternative to the Lumia 920.

Regarding settings, I keep the network set to Dual mode since the coverage provided by AT&T in the Bay Area is spotty. Other than that, I don't recall having seen any available updates since I received the device directly from Nokia Care. It could be that it came flashed with everything in the updated versions. 

I am glad to have found this thread because I searched high and low for others experiencing connectivity and reboot issues with their 808 devices and couldn't find anything on the Nokia USA site or on other 808 forums. Glad to be able to contribute, despite the nature of the thread.

[pureviewusa]

cmdrWallet's post somewhat confirms that this issue is cell tower related.

- For me Since FP2, its been rock solid in NYC, rebooted once in another city

- For cmdrWallet', his FP2 become quite stable when visiting NYC

Now, what is Nokia going to do about this info? Probably nothing

[vlado3g]

My N8 has no such issues with Belle Refresh .. very stable with HSPA turned on. Same AT&T sim... I travel between Monterey Bay and SF bay almost every day and I haven't had even one reboot.. can't say the same about the 808. My N8 is Finish made (from the first batches in 2010) with EURO firmware ... i don't know if that matters.

So, at least in my case, its an 808 hardware/firmware issue.

Mine has been pretty stable around town.. no restarts for the past 3-4 days, but I am sure that if I drive over the San Jose and will proably get a reboot or two. Its really strange.. is it possible that the HSDPA radio chip that they used in the 808 is not working well with certain types of tower/cell equipment ?

@andyrao1971 the 920 has more problems than the 808 ... just head over to wpcentral's 920 forum section..no bueno, and overall there is no way the 920 can replace my 808..

[React]

Im using nokia N8 and 808 and the n8 has no such problems, but 808 cant run on hsdpa for 5 mins without freezing. since i have a product code 059P9S0, there is no firmware available

Moderator's note: We have removed mentions on illegal processes which will lead to users harming their device and void their warranty. Please read guidelines before posting.

[andyrao1971]

@vlado3g - Thanks for the update on the Lumia 920. I was planning to but the 920 upon its imminent launch in India.

Like so many people on this forum, I have only ever owned a Nokia phone and can't think of moving away - especially when Nokia needs all the support it can get (that's the reason I traded my perfectly working N8 for the 808).

However, it is incredibly frustrating that its been 4 months since members on this forum reported the problem and Nokia has not been able to fix it.

[royemunson]

Has anyone in the US been able to get the 808 to function properly consistently? I had one for about 10 days here in Denver on AT&T and it was horrible it would crash or hang non-stop. Obviously I've read some comments on here stating they were able to get the phone to work to some extent but still the occasional crash or hang. I would love to give the phone another shot since you can now get a like new one from Amazon for $365 but if I can't get it to work consistently then why even give it a shot. Like you all keep saying it's just embarrassing to see how such a great device can not be made to work correctly. If this thing worked I would give up all my phones in a second for it and that's saying a lot because I'm a bit of a phone junkie (iphone 5, iphone 4s, lumia 900, and galaxy s2). I was just that impressed with the camera on this phone, as you all know the camera is beyond comparison. It just seems that this problem is an issue that could be fixed through some sort of software update but maybe I'm wrong and it's something in the hardware that can't be fixed. I've owned a cell phone since 1996 and used more Nokia phones then probably anyone here mostly because my pops was a VP of sales for Nokia here in the US for a long time and gave me new phones every few months but I haven't used the brand as my primary phone since the n82 and at this point I'm hard pressed to think this will change.

[hlorri]

After 1 week on T-Mobile in the SF Bay area, I have not had a single instance of the phone rebooting on its own! This is with HSPA enabled.

In contrast, it would fairly consistently have 1-2 reboots when driving from home to work or vice versa on AT&T, or when out running a particular stretch near work.

So I can safely say that in my own case, switching from AT&T to T-Mobile is a solution that has worked!

[vlado3g]

@hlorri that is indeed interesting... so its got something to do with the particular kind of cell tower/network ? T-Mobile's 3.5G networks runs on different frequency... 1700 I believe, but I have no idea if that makes a difference.

I am sorry if this is asking too much.. but have you traveled outside the city with the TMO sim ? I am just wondering if maybe TMO also uses the problematic cell towers or whatever it is in certain areas..

How do the data speeds comapre to AT&T ? 

[dj24]

Let's just stop with the theory that this is just possibly an at&t issue.  I'm on t-mobile here in Phoenix, AZ and from my previous posts a couple of pages back you should know that I've been suffering greatly from this problem as well.  I'm on my third phone and Iam sad to report that this one is going back at the end of the week .  This one had actually worked ok with mobile data disabled from my notifications drop down menu for about 3 and a half weeks till this past sun when it lost its connection.  Worst possible timing you can imagine.  I had actually just started to finally trust it even though it was a hassle enabling and disabling mobile data everytime I needed it but this was my last straw and will be waiting it out till Nokia addresses this sad mess.

[Craig_Mitchell]

With reference to my posting, and the FAQ, I would like to comment that Nokia has already issued a service bulletin to the Care network, which means that all the Nokia Care Points should be aware on how to inspect the device if it has the reported symptoms.

[pureviewusa]

Craig,

What is the point of bringing to Care network? Since there is no fix, what is the point? It depends on what cell towers  the Care network have and I doubt they will watch the phone for 24 hours to check for reboot.

If Nokia simply releases some diagnostics software which can installed on user's phone, they will have 10's of reports and logs within the week  to help them track down the issue. Why isn't this approach considered?

[jmedland]

I'm sure that's a typo, and he meant "how to fix the device if it has the reported symptoms."

[gvp1995]

Now I am fighting the screensaver bug. I am posting this message here because I think it is related to the topic. I was at the place where the phone connection was very week, the phone just hung. I had to take out the battery. After it started, the old 'screensaver' bug came back, and there was no way I could get rid of this. The home screen is always on, the phone is locked but the screensaver does not appear. Whatever I was doing - in vain. I took the battery, the SIM and memory card for 10 min, put everything back - the same story. Finally, after reading more of this thread, switched off 3g, re-booted the phone, and voila! Screensaver is back! Thank you Jesus, I go for a trip tomorrow. Does anyone know if they are planning to fix this **bleep**? With the screen always on it is virtually unusable. Some people write something about N8 and similar problem. I own N8 for 2 years and never-ever had anything similar.

[elliottpotter]

Craig - a couple of points to make:

1) In the US, there aren't really Nokia Care Points; I'd have to put the phone in a box and mail it to some place in Alabama, which means not having a phone for several days.

2) I have yet to hear of a single person who actually got a phone fixed this way. I've heard several people tell stories of being on their 4th or 5th 808 with exactly the same results, which makes more sense because the problem doesn't seem to be faulty hardware, but faulty software, and there is no new software that a Care Point could install.

So: is there an *actual* solution that you could offer us? This thread is 19 pages long, approaching 400 posts, and was started months ago and there has been zero visible progress. The best advice anyone has seen so far is to disable high speed data, which dials back the clock several years on data speed and doesn't actually solve the problem for most people; just reduces the occurrence of reboots. Can you give us anything more? If the software team there doesn't have the resources, I'm sure that you could find 10 people here who would pitch in 25% of what they paid for their 808 to buy someone a plane ticket to the US (or other country where the problem is widespread), and put them up in a nice hotel until it's fixed. We'd all just like our phones to work.