2013-02-28 6:10
tf_translate wrote:My phone had all of these bugs (going blank with keys lit, rebooting, simply going balck) before the repair and none of them after.
You are just lucky you live in Ukraine. Majority of folks on this forum are either in US or in UK. Looks like no hope for us ![]()
2013-02-28 11:14
After having read through this thread I just gotta give another solution for the problem. It`s a matter of hardware problem, a faulty capacitor in the radio of 808. Many people having this 3G-bug have been helped by changing a so called "security component" in the motherboard of their device. Waiting for my 808 to arrive from the Service point within a week or two and I`m pretty sure the problem is gone for good after the replacement of this particular component. I don`t know why Nokia haven`t reacted to this known issue, perhaps they think it would be a disaster to be forced to call back most of the 808s delivered, no matter what the batch or IMEI-number is.
2013-02-28 19:27
Noticed that the problem in this thread is marked as "solved" but if the solution is to disable HSPA-connection it certainly isn`t solved at all but the bug in the hardware is still there and the problem can really be solved by replacing the faulty component in the phone.
2013-03-01 12:17
It's absolutely not solved.
My new 808 is IMEI 35196505215xxxx and it still crashes if HSPA is enabled, but doesn't crash if it is disabled.
2013-03-01 13:05
Today I am about to send in 2 Nokia 808 due to restart problems.
The same problem have been on a Nokia 701.
On 2 Nokia 700 this problem have never occured at all.
All these devices running Belle FP2.
I think it is combination of software/hardware and operator problem.
For instance, with the operator Telia in Sweden which runs on Ericsson mainly (almost 100% of the time in Telia own net) and administrate their own net, the problem seems to be none at all after a week on that net. I was using near 5GB transfering music all the time with Nokia Internet Radio. No restarts and actually only 2 drop outs; disconnected stream of music. With operator 3 i would have at least 50 drop outs in this city and of course restarts.
On the other operator 3, which runs their net on mainly Nokia Siemens and their partner Telenor there are much worse problems.
When running around 3 havinng a lot of problems due to Telenor/Tele2(Huawei most now which is obviously **bleep** compared to Ericsson).
2013-03-01 21:42
peterh338 wrote:It's absolutely not solved.
My new 808 is IMEI 35196505215xxxx and it still crashes if HSPA is enabled, but doesn't crash if it is disabled.
Well, thank you for all your tests, reports and this conclusion. At least I am not sending my 808 (...5050...) now. Will wait closer to the warranty expiration day.
2013-03-02 6:38 - edited 2013-03-02 6:43
I have just sent in my 808 for Nokia to investigate the right side purple tint issue and possible Maps/Drive issues related to 3G/HSPA. Approaching the Nokia Care Centre was futile. They kept asking me to wait for 1508 and not to read too much into posts here at Nokia Discussion Forums. They said it may be inaccurate being a public forum, what I find here might be untrue because it is unofficial i.e. not from Nokia.
What I found works was to call Nokia Careline and ask them to escalate the issue to the Senior Customer Care Officer or email Nokia Support. I did both.
I hope I have better luck this time. My 808 Serial No. is 3519650500xxxxx new from Nokia, not a motherboard replacement.
2013-03-04 4:28
A link with further information. Now is finally time to wake up, Nokia!
http://www.allaboutsymbian.com/flow/item/16255_Nok
2013-03-04 11:43
That is an old article - Nov 2012.
Nokia have never said anything about this openly.
And the latest phones also have the issue.
Two specific issues in fact, on mine:
(1) A total crash if HSPA is enabled (very rare though, and impossible to make it happen via transferring any amount of data over HSPA). Disabling HSPA has totally stopped this.
(2) A quiet restart (happens anyway, when I am in a specific location where there is almost no signal). Not an issue really unless it does it during car satnav, which I suspect it won't because then one will be likely using external power.
2013-03-04 11:50
Yes, that`s an old one but shows that Nokia is still uncapable to give an official bulletin concerning this major issue in the manufacturing process. Just wonder where`s their quality control or if there`s any in the first place.
2013-03-04 20:59 - edited 2013-03-04 21:00
peterh338 the easiest way to get the phone to restart is to be in a low signal area, and then keep the connection busy, uploading seems to be the easiest way to make it crash.. for example turn on auto upload on the skydrive app, take some pics.. and it will crash for sure.
sometimes it just freaks out
I was sitting in my car last night in an area with spotty signal and the phone restarted twice in 10 minutes.. I think it was trying to fetch an e-mail or something, so I had to swithc to GSM to make it stop restarting.
2013-03-05 1:18
vlado3g wrote:peterh338 the easiest way to get the phone to restart is to be in a low signal area, and then keep the connection busy, uploading seems to be the easiest way to make it crash.. for example turn on auto upload on the skydrive app, take some pics.. and it will crash for sure.
sometimes it just freaks out
I was sitting in my car last night in an area with spotty signal and the phone restarted twice in 10 minutes.. I think it was trying to fetch an e-mail or something, so I had to swithc to GSM to make it stop restarting.
Completely agree with both of you. This is how it was from the very beginning, and this is how it works on the new ... 5052.... device. So nothing was fixed. We can speculate why but the fact of the matter is that it still does not work. If it is a simple capacitor, then it is a shame. I however suspect some design issue here. We may never know the truth
2013-03-05 16:54
2013-03-07 1:08
2013-03-07 15:32
2013-03-09 22:21
I am now totally convinced that the battery voltage plays a big part in this bug.
Today I was driving with Nokia Drive satnav. HSPA disabled as I always have now.
With no external power connected, the phone would crash every few minutes. Sometimes all black, sometimes it would freeze (nonresponsive).
With external power connected, no problems at all.
2013-03-11 2:14 - edited 2013-03-11 2:18
peterh338 wrote:I am now totally convinced that the battery voltage plays a big part in this bug.
Today I was driving with Nokia Drive satnav. HSPA disabled as I always have now.
With no external power connected, the phone would crash every few minutes. Sometimes all black, sometimes it would freeze (nonresponsive).
With external power connected, no problems at all.
Thank you. This is good information. As I remember (anyone can scroll through this forum and confirm) there was a member here, who is a hardware engineer if I remember, who suggested the whole theory about the battery being inadequate for the task.
Here is the worst part for me. I can easily live with occasional restarts and freezes. I can even forgive when my phone shows all bars, but there is no connections. But one implication makes me think about switching to a new phone. As a matter of fact I am resolved now wot buy another Pure View (41mp) phone as soon as it is out there. Be it even Windows Phone - I heard rumors Nokia is planning to have one by the end of the year. And this is my biggest problem with 3g bug. I go hiking pretty often and I want to find my way back. For this I use GPS. With my old good N8 I was using SprotsTracker and everything was great. But now SportsTracker does not work with 808; One solution or rather a workaround was to start another GPS app, which will keep SportsTracker alive. And it does work. Sort of. As soon as you get in the area where the signal is intermittent, and this happens very often when you hike, the whole GPS business can get crazy. This happened many times in the past, and it did happen today. In the critical moment I looked at my SportsTracker - 0/0 satellites. Open GPS Toolbox - 0/0. Everything is gone!!! The whole route is gone. The only way to bring it back is to restart the phone, but you lose everything. And this is unacceptable for me. Yes, I can save my starting position into Nokia Maps. Yes I can use my wife's N8 for back up. But then I ask myself why do I have this phone for?! For pictures? In this case I could have much cheaper alternative. It is a terrible feeling when you know any moment your equipment can let you down.
One other note. I did use my GPS/SportsTracker many times to test and it is always fine when the signal is constant and strong. As soon as I have a week or intermittent signal, GPS is gone! I can only consider this as yet another manifestation of 3g bug.
2013-03-11 17:24
I was testing the connection speeds with 3g and 3.5g on T-Mobile USA to see if I could live with 3g. Here are the results 3.5g - download_0.38MB/s, upload_0.22. Now 3g - download_0.11, upload_0.10. Both speeds are kind of lousy, not even close to what 3.5g is supposed to be. But still it almost 4 times faster with 3.5g. Anyway, while in HSPDA - disabled mode, the phone restarted! I think the high speed packets may just highlight the problem, which is there anyway. Together with the fact that ...5052... behave the same it makes the whole thing pretty hopeless...
2013-03-12 7:42
Here in the UK, with the 808, I get about 300kbits/sec down (3G) and 10x that on HSPA.
Uploads are a fraction of those speeds but also a 10x difference.
HSPA is nice, and essential for streaming video, but I don't need that.
One day I will find a Nokia service shop willing to repair the phone. Currently the UK ones don't even admit to having any data on this. I am sure Nokia sell the 808 via grey importers primarily to ensure that UK customers end up with no warranty so they cannot make a claim.
2013-03-12 9:25