2012-11-21 2:54 - edited 2012-11-21 2:55
^ word.
I am starting to think that this is a wide spread issue... maybe even every single 808, but the reason they are not getting reports from all over the place is because a lot of people still use 2G, or don't have HSPA enabled network.. or don't use mobile data that much since mobile data is relativly expensive.
A lot of the reports seem to be from the US... where HSPA on both ATT and TMO is widespread, and we do use a lot of data since its kind of cheap really when you compare it to the EU for example, and the problem seems to be more exposed I guess...
I dunno.. just speculating.
2012-11-21 15:06
Here is an update from me. Remember: Bought 808 in Ukraine, experienced 3G lockups in Germany (in Ukraine there is no 3G qwith my provider), disabling HSPA reduced the lockup frequency, but still lockups in standard 3G, Ukrainian dealer refused to RMA the phone because they could not reproduce the issue in Ukraine, Nokia recommended me in this thread to bring the phone to a German Care Point.
Here is the update: The German Care Point rejected the phone because it was allegedly not on warranty. Argueing that the phone has been on the market for less than 6 months did not help - you bought it in Ukraine, you get your service there. Oh well. I thought mobile phones were called this way because they enable a mobile lifestyle, but obviously I was mistaken.
Now I experienced a lockup that, judging by all the symptoms (the way the phone locked up, what was happening when it locked up etc.), was exactly the same as the 3G / HSPA bug today, but I experienced it in Ukraine, while using mobile data via 2,5G / EDGE. This is new! I did not see a report about EDGE lockups so far in this forum.
My theory now is that the lockup frequency is proportional to the speed of the mobile data connection and antiproportional to its reliabilty. Probably HSPA is more flaky in genereally so this underpins my assumption I have been voicing for some time now that the 808 firmware is programmed for a theoretical optimum world, but can't cope under real life conditions (the same is true for the Wi-Fi issue, or for the plain situation when you have no data connection at all and the 808 will drown you in error messages that inform you about the connection being absent, which you are pretty aware of even without the 808 telling you ...).
The Ukrainian GSM/EDGE network in Kyiv is not too fast and rock solid, that's why I was not seeing problems there for a long time. The one lockup I had now occured indeed when I entered the subway - a zone where EDGE coverage gradually fades away as the escalator descends below ground and gets replaced by plain GSM without any data connectivity.
To the contrary, the network of my German provider O2 is very flaky in general (they are known for this, there is even a song about it from a famous comedian. :-). My experiences in Germany were that I could not use HSPA for more than a few minutes no matter what, the phone would lock up. I could use 3G stably when staying stationary at a place with good coverage in the city (e.g. a hotel room) and use 3G for hours without lockups, but as soon as I would travel (by care, train, foot - which means changing signal strength, traveling through zones without coverage) the phone would lock up sooner or later for sure. And I had lockups with this as well as with a different (more reliable <g>) provider all the time while I was staying at the seaside on an island with weak coverage.
So to sum it up, my 808 will lock up when the data connection is weak no matter what technology is being used (!), and it will lock up a lot quicker with a faster connection.
Several hard resets, using the phone without 3d party apps, upgrading to Belle FP 2 and so on all did not solve the problem.
After having had the lockup in Ukrainian 2,5G/EGDE network today, I too the phone to a Ukrainian Nokia service center. (In Ukraine it is bring in only, but luckily the service center is next to where I live). I was greeted very politely (which is unusual for this country) and the service clerk seemed to understand the problem. Maybe he was impressed when he heard that I discussed with Nokia developers and it also helped that I showed him the link to the page where Nokia says to take in phones with this issue for inspection, that is a few pages back on this thread. He admitted though, it was the first time he ever got his hands on the 808 and asked for a timeout to consult with his colleagues and probably Nokia.
I wonder whether they will only rewrite the firmware (which is necessary anyway, since the upgarde to FP2 broke several things on my phone which are not normal, i.e. others did not report those issues - my phone now reports "system error" whenever I turn it on), or whether they will offer a more comprehensive solution.
I'll keep you posted as to what comes out of this.
2012-11-22 2:37
^ that sounds extreme... they should probably replace your phone.
2012-11-22 11:46
vlado3g wrote:@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 was thinking the same thing for a while. In the USA, AT&T uses two separate UMTS/HSPA bands: 850 and 1900 MHz, whereas T-Mobile (at least where I live) use only 1700 MHz. In Europe, both 2100 MHz and 900 MHz are used now. What if this had something to do with switching from one frequency to another?
Then, people started reporting this issue with T-Mobile as well. So I guess that's not the case.
vlado3g wrote: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..
I am sure that's the case. My phone behaved well with HSPA enabled on AT&T during a recent trip to San Diego, but once back in the Bay Area I had to disable HSPA again. Based on what others are saying, similar location specific behavior is probably going to be the norm for just about any carrier... But for me, T-Mobile works great!
How do the data speeds comapre to AT&T ?
Comparable. My top speed (from http://www.mobilespeedtest.com/) was 4196 kbps on T-Mobile, vs. 3988 on AT&T.
However, T-Mobile coverage is noticably weaker, and so despite fixing my 808 issue, I may stick with AT&T and leave HSPA disabled. It's still fast enough to stream audio with Nokia Internet Radio, and web browsing still fares OK with Opera Mobile/Mini. Email & Podcasts are downloaded in the background anyway. So for me, lack of 3.5G is not a show stopper.
2012-11-22 11:59
dj24 wrote:Let's just stop with the theory that this is just possibly an at&t issue.
I don't think anyone is claiming that this is "just possibly an at&t issue" - that's a strawman. It is definitely an issue in the 808 firmware, but it is also clear that it is triggered in a network specific manner.
In my case, reboots happen frequently enough on AT&T that it is bothersome. For instance, if I go out on a run with Endomondo Sports Tracker running, there is a 95% chance that the recorded route will be cut short due to a reboot. Not so with HSPA disabled, and also not so (under any circumstance) on T-Mobile.
Clearly the picture is different in other locations.
2012-11-22 12:37
2012-11-22 13:23
I do not face such often reboots but they happen. Just think what if problem happens during switching frm one cell station to another? I am myself mainly spend whole day at office and observe connection to one station only. In the office I forgot when last time I had any reboots. But rebooting happens while driving in the town. Can you guyes observe when exactly reboots are happen. I use for observing network station CellShark app
2012-11-22 15:49
Guys, I have the confirmation now. The lockups/freezes when using weak 3G/HSPA connections is a hardware bug. As I said, I took my phone to a Nokia authorized service center in Ukraine yesterday. They asked for a timeout, since it was obviously the first time they saw this device at all, and I had little hope since there is virtually no 3G in Ukraine. But today they called me to come in and I had a chance to speak to the technicians. They told me they found this very bug (freezes when using 3G/HSPA with the 808) in their internal support database and that there are instructions from Nokia to replace a capacitor on the main board!
I will probably only be able to report whether the capacitor replacment exercise fixed the issue in a month or two because I am about to leave Ukraine. In the meantime, they will now order the detail (its like 2 weeks until they get it, quite normal over here) and I will get the fix done when I visit Ukraine next time. I am still angry that they refuse to fix my phone in Germany. But still, I feel very delighted, now that I know that Nokia actually knows the cause of the problem!
You guys out there, stop RMA'ing your phones to Amazon. Replacing the phone against another phone from the same series is unlikely to help. What you really need to do is to visit a Nokia Care Point, bring in a printout of this hyperlink:
and ask them to FIX (not: replace) your phone.
2012-11-23 1:55
Very good "! thx 4 this info !
sended my 808 yesterday to amazon with known issue .....
maybe if its in service database , they will repair it and ill have my loved 808 as fast as possible back .....
regards and greetings from germany !"!!
Peter Miller
2012-11-23 16:58
Amazon might send the device that you send in to repair and later re-sell it over their store at a discounted price over their site. However, in order to "maximize customer satisfaction" they are very likely to simply send you a new device, so that you don't have to wait for the repair. And if the hypothesis is true that this is a issue that affects all 808, or all 808 of a certain series, then it is quite likely that your replacment device will be affected by the same issue. Amazon is simply a re-seller, I don't think they have qualified service staff that is able to solder capacitors on a mobile phone PCB.
Therefore, what I wrote above is that you have to take your device to a Nokia Care Point. You can find contacts at http://www.nokia.com/de-de/support/kontakt/. Then it is a matter of talking the Care Point clerk into finding the issue in their Nokia database and having them replace the proper detail. This is difficult in Germany, it is easier in Ukraine where people are less formal :-). But it should ultimately work since the Nokia database is worldwide, and while Ukrainians are very good at crazy soldering operations, Nokia Germany should also have qualified service personal ... :-).
So you bought your device in Germany and have the same issue? I was initially wondering whether Nokia might be intentionally selling off a series of 808 phones with the 3G bug in Ukraine because there is virtually no UMTS style 3G in Ukraine and nobody would notice. The 808 appeared in Ukraine abou a month earlier than in Germany and I got my device on day 1 of its availability, so I might have one of the earliest devices that were released at all. But if you bought a phone with the bug in Germany then at least here I am proven wrong.
2012-11-23 19:07
The nokia care sucks.. and so does this discussion thread..!!!! No fix yet for the bugs.!!! Regret big time for taking 808 pureview.. it's like i have taken the phone only for camera.. nothing else works!!!!
BIG BUMMER!!!!
2012-11-24 4:55 - edited 2012-11-24 5:04
Yes, this is what it is. Nothing works but the camera. Thank God the camera still works! Otherwise it would be $700 brick! I was hiking with my wife today, her N8 takes 3 sec to lock GPS, my 808 still thinks even after 3 min (never actually gets it) Her SportsTracker shows everything perfect, mine - 0/0 satellites. You may say use the known work around - just start another GPS app, and then SportsTracker. It works for one session, after that - no lock again! Moreover, another GPS app does not find anything! Moreover, the native Nokia Maps cannot find anything! At this point the phone is useless.
However, while walking in the forest today, I came to one interesting conclusion. I completely agree with tf_translate:
IT IS A HARDWARE ISSUE!!!!!!!!
It just manifests itself slightly differently on different phones/countries/carriers. Yes, 3g bug is one of the manifestation. It is very subtle, and difficult to spot. I have another one, which relates to 3g because it usually happens after the 3g related hung (see some previous posts on this thread). My screen saver stops working after such crash, and the following re-boot. It locks the phone all right, but the home screen is still shows, draining the battery, of course. Now, this is the intriguing part. After I pull out the battery, as well as the memory and SIM cards, wait for several minutes, and put everything back, it still does not work!!!!!!! Can you think of any software related bug, which would not be fixed by such a re-set? (nothing was changed in the phone - no installs, un-installs or any other changes). Being a computer programmer myself, I cannot. Then after some time it sporadically returns back, and starts working again. I can work for days, and then brakes.
Another indication it may be a hardware issue is the fact that it is very difficult to reproduce. If you have a software bug, after several trials you can reproduce it, and then it will always repeat. You may say, OK, 3g bug is a hard one, because it involves a weak signal, absence of a signal, etc. But its artifact - non working hard lock button isn't predictable either! Whatever I did, I could never reproduce this bug. Sometimes easy restart fixes it, sometimes I take all the guts out for 10 min, and it still does not work after that, just to fix itself spontaneously after 3 hours.
It looks to me a bad capacitor, mentioned by our Ukrainian friend, could explain such behavior. In any event, from this point I am going to pursue this hardware issue with Nokia and see what happens. The phone is unusable, and I determined to find a solution one way or another.
2012-11-24 12:55
Why do you say no fix for the bugs? Nokia Care confirmed that they have instructions in the world-wide datbase to replace a capacitor on the board. So there is a fix for the issue. You just have to stop ranting and submit your device not to Amazon, not to your reseller, but to a Nokia authorized service center and they will fix the issue.
I can't wait to have the repair done. I do hope it fixes the 3G issue, and maybe some of the other issues go away as well. That would be brilliant.
You can rant if you've been to the service center and they did not fix the issue. Until you have done so, please stop ranting. Faulty hardware is something you can't fix via firmware updates.
2012-11-24 14:18
i bought it in germany from amazon around 4 of june , i guess it was also one phone of the first sales charge ..... maybe in early 808 phones this bug ist existent .... eventually they revised the circuitry in later revisions of pcb . ?????
as i read your mentioned thoughts about sending it back to amazon it was too late ..,..
i already handed phone out to DHL .... :-(((
hopefully amazon will not send me a other device because there is one big problem in germany , THERE IS NO MORE NOKIA CARE POINT. ... concerning their website , i didnt found aany care point .... so what should i do if i got replacement unit with same issue ?????? any ideas ????
THX and regards from germany to ukraine.
2012-11-25 14:15
"confirmation" implies "this worked for at least a couple of people." So far we only have one customer (tf_translate) who heard from one Nokia care point (in the Ukraine) that they have a solution. We haven't heard if this solution actually works, and we have no indications that other Nokia care points have been advised of the same solution.
I agree that sending the phone back to Amazon or another reseller is not the answer, but I don't want to ship my phone off for a week to a repair center if they're not going to fix it. So far the only official word we've heard from Nokia is that we should disable high speed data access, which does reduce (but not eliminate) the occurrence of problems.
Can we get some official word from Nokia that there's an actual fix for this problem?
2012-11-26 6:11 - edited 2012-11-26 6:34
Hi elliottpotter,
With reference to my previous post:
--------------------------------------------------
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.
--------------------------------------------------
maybe I should have written before:
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 and take any needed actions.
The instructions delivered to the Care Point network are global, so not specific to Germany or UK only. I like the advice given by tf_translate, and that is to take a copy of the FAQ and this post to the service point.
Regards, Craig
2012-11-26 11:44
2012-11-26 13:19
On my N808 the screen went black randomly too, ( with the illumination on the buttons staying on). Only way to fix it was to take out the battery and reboot. But I discovered that this only happened after I started using a replacement batterywhich only had 3.7V and 1320 mAh as opposed to the standard battery with 3.8V and 1400maH. Now I only use the standard battery the phone was delivered with and it never happened again. Is this really a hardware issue?
2012-11-26 18:31
Craig_Mitchell wrote:Hi elliottpotter,
With reference to my previous post:
--------------------------------------------------
-------------------- 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.
--------------------------------------------------
--------------------
maybe I should have written before:
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 and take any needed actions.
The instructions delivered to the Care Point network are global, so not specific to Germany or UK only. I like the advice given by tf_translate, and that is to take a copy of the FAQ and this post to the service point.
Regards, Craig
Hi Craig, can you let us know when Nokia starting shipping the 808's with the new and improved capacitor? I'd like to return the one I have to Amazon and get one that works right out of the box instead of sending it in to get it fixed.
2012-11-26 20:32
Craig_Mitchell: It means Nokia has to recall all 808-s from Amazon and replace bad capacitor! Otherwise, Whenever people buy it from Amazon, Nokia likely will receive one star reviews till Amazon starts to ship not buggy devices.