Database Users

Overheating perhaps?

I had been reading the forum on issues of this phone. Now that I have my own phone, and experienced a couple hard reset crashes as well, here is my hypothesis.
There are 2 types of crashing phones here: 1) defective phones and 2) normal phones.
The defective phones are broken right out of the box. The user cannot set up or even get it to properly sync. These phones should be returned to Dell asap.
Then there are the normal phones, which users can set up everything, download and sync. However, crashes often happen at random intervals, and one can't quite reproduce a hard crash. We tried to pin it down on Wifi, RAM, SD Card space, etc, but nothing seems quite pinning the issue down.
And then there are two types of crashes: app crash and hard crash.
An app crash is simply caused by poor programming, and is always caused by a third party app. The app will simply close and push you back to Start Menu. No big deal. It's not a hardware problem.
Then there are the hard crashes. I have to reset the phone by either pressing the hardware buttons at the same time, or pull out the battery. It had happened to me while using Office, Xbox Live Extras, and Marketplace.
The hard crashes only started happening to me very frequently today - 4 times in a row.
Some users think that it is a Wifi issue, but I doubt it. It seems to be related to Wifi, only because we use the phone most often while there is Wifi. To me, turning it on and off does not increase or reduce the chances of crashing.
Since all the apps were functioning properly, I can only come to one possible conclusion:
The phone was overheated.
My DVP is encased in the Otter Commuter case, which has two layers of plastic, with the inner layer trapping the heat of the phone. The way I'm holding the phone does not help either. Besides, my hands are very warm. I'm at home and it's very warm.
So after the 4 consecutive crashes, I decided to just put down the phone and let it cool down.
And viola! The phone does not crash in any of the apps anymore.
I wonder if this is the issue with other people with crashing phones? Is it only because we love and use the phone too much with our very warm hands?

At this point, anything is possible
My 8GB does get warm under heavy use, but I still haven't been able to crash it. I don't have a case and I typically don't grip the phone, but rather hold it by the edges in order to avoid deathgrip.

pakkei said:
I had been reading the forum on issues of this phone. Now that I have my own phone, and experienced a couple hard reset crashes as well, here is my hypothesis.
There are 2 types of crashing phones here: 1) defective phones and 2) normal phones.
The defective phones are broken right out of the box. The user cannot set up or even get it to properly sync. These phones should be returned to Dell asap.
Then there are the normal phones, which users can set up everything, download and sync. However, crashes often happen at random intervals, and one can't quite reproduce a hard crash. We tried to pin it down on Wifi, RAM, SD Card space, etc, but nothing seems quite pinning the issue down.
And then there are two types of crashes: app crash and hard crash.
An app crash is simply caused by poor programming, and is always caused by a third party app. The app will simply close and push you back to Start Menu. No big deal. It's not a hardware problem.
Then there are the hard crashes. I have to reset the phone by either pressing the hardware buttons at the same time, or pull out the battery. It had happened to me while using Office, Xbox Live Extras, and Marketplace.
The hard crashes only started happening to me very frequently today - 4 times in a row.
Some users think that it is a Wifi issue, but I doubt it. It seems to be related to Wifi, only because we use the phone most often while there is Wifi. To me, turning it on and off does not increase or reduce the chances of crashing.
Since all the apps were functioning properly, I can only come to one possible conclusion:
The phone was overheated.
My DVP is encased in the Otter Commuter case, which has two layers of plastic, with the inner layer trapping the heat of the phone. The way I'm holding the phone does not help either. Besides, my hands are very warm. I'm at home and it's very warm.
So after the 4 consecutive crashes, I decided to just put down the phone and let it cool down.
And viola! The phone does not crash in any of the apps anymore.
I wonder if this is the issue with other people with crashing phones? Is it only because we love and use the phone too much with our very warm hands?
Click to expand...
Click to collapse
its like 10degrees at my house...can you send your phone over !!!

i'm sure someone has already mentioned this somewhere on the forum
but since your talking about overheating i might as well mention
##634# system info reports the temp so do this immediatley after a crash and post your temp readings
also i have the otter case to so next time i crash ill post my temp

weird screen behavior on cm7 and miui

Noticed something weird with my fassy this week, the screen was waking up itself randomly. At the time I was on the latest build of cm7. It got so bad I would hit the power button to shut off the screen and it would pop right back on to the lockscreen. So I wiped the phone and flashed the Miui rom. EXACT same behavior! So I odined back to DL09, then to Froyo, then reflashed cm7. Incredibly the phone still does this so I dove into the settings today, didn't find much but I did stumble onto a solution........its only does it when I have data turned on (I mostly keep it off during the week because my work has horrible reception and my battery will go dead in about 4 hours) .Whats weird is its completely random, sometimes I will spend 10 minutes to turn the screen off (it keeps popping back on), other times it doesn't have this problem. If i turn data off there are no problems.

I'm not sure if I'm right, but people seem to be having weird bugs appear in 3G low-signal areas, including random button presses and other weird behavior with CM7/MIUI. Maybe this is related to your problem? Does this happen in all areas or in low-signal areas only?

Might be the reason, it does seem to happen in low signal areas that's an interesting theory.

i've been on CM7 for a couple weeks and haven't noticed this problem, but interestingly i used to get it when i was using stock roms that were just debloated. i would notice my phone would randomly wake the screen to full brightness on it's own, decrease and then shut back off in a span of probably 15 seconds.

baron4406 said:
Might be the reason, it does seem to happen in low signal areas that's an interesting theory.
Click to expand...
Click to collapse
I'm thinking that might be the reason, and when you turn off data you're disabling the weak 3G signal, preventing the bug from happening. For now, I believe no fix is available.
And as far as this being related to the stock ROMs, I believe that was a completely different issue. This is related to 3G signal strength. I've haven't seen this bug yet since I live in a coverage-saturated area, but the reason I know about this is that other people have been complaining about it in the CM7/MIUI threads.

[Q] Nexus 10 wake-up lag

Got the N10 a few days ago and I noticed immediately a severe 5-7 sec wake-up lag. The delay is so long that instinctively, I always press the power button twice, believing the unit is powered down (the Xoom I owned before would wake-up almost instantaneously).
This problem is/was always present, even with the unit completely stock.
Other owners experiencing the same problem? What's your average wake-up delay?
Thanks,
---Mirco.

I usually have about a 1-2 second lag upon waking. It's a little annoying sometimes, but not too terrible considering how much I love the tablet.
Sent from my SPH-L710 using xda app-developers app

I haven't noticed this issue at all with my unit.

I notice about 1-2 sec delay sometimes when waking my tablet.

I posted a video on YouTube that exemplifies the problem:
youtube . com / watch?v=sbjCi8K6kyY (the forum won't let me post links: remove the spaces to watch)
As you can see, from the moment I press the power button (sec. 5) and the moment the tablet wakes up (sec. 11) there's a full 6 seconds delay.

I've seen it on mine... It seems like the screen always ends up rotating when I see the lag.
Sent from my Nexus 10 using Tapatalk HD

Mircolino said:
Got the N10 a few days ago and I noticed immediately a severe 5-7 sec wake-up lag. The delay is so long that instinctively, I always press the power button twice, believing the unit is powered down (the Xoom I owned before would wake-up almost instantaneously).
This problem is/was always present, even with the unit completely stock.
Other owners experiencing the same problem? What's your average wake-up delay?
Thanks,
---Mirco.
Click to expand...
Click to collapse
+1.. I have this lag as well.. Wonder what is causing this!

roshanpius said:
+1.. I have this lag as well.. Wonder what is causing this!
Click to expand...
Click to collapse
Haven't figure it out yet: it started doing it right out of the box so I doubt it's some sort of software/configuration problem.
All I know is that it's driving me crazy and I'm ready to return the unit.

Mircolino said:
Haven't figure it out yet: it started doing it right out of the box so I doubt it's some sort of software/configuration problem.
All I know is that it's driving me crazy and I'm ready to return the unit.
Click to expand...
Click to collapse
Tried it on my unit and it's doing the same thing! But it's random, sometimes I have a 1-2 sec delay and sometimes 5-6 sec. Very strange...

drcujo said:
I haven't noticed this issue at all with my unit.
Click to expand...
Click to collapse
This.
Best advice I can give is reflash the stock image from Google, instructions are available on here or on the android side itself, along with the image.

stiggy2012 said:
This.
Best advice I can give is reflash the stock image from Google, instructions are available on here or on the android side itself, along with the image.
Click to expand...
Click to collapse
Did that, several times. Completely stock, bootloader locked/unlocked, rooted or not, it makes no difference: the 5-6 seconds wake-up delay is always there.
One thing I noticed: it disappear when the tablet is connected to my PC via USB cable. In this case wake-up time is the normal 1-2 secs.

I've just noticed the same issue. Mine can work fine for a few unlocks and then it will flash the unlock screen for a split second and go black. After reading the other posts on here, I left it for a while and 25 seconds later (tested three times now), the unlock screen appeared properly, enabling me to enter my pin and use the device. If I didn't enter the pin, after a couple of seconds of inactivity, the screen would power off as per the normal 30 timeout for pin entry.
If this is another hardware fault, I think I'll have a little cry First my Nexus One had digitiser issues, then power button problems (both times replaced/repaired under warranty). The Galaxy Nexus had 5GHz wifi issues and the Nexus 7 had bezel lifting issues...
**UPDATE**
As soon as I posted this, I remembered I'd recently installed LightFLow to get my notifiction lights for emails like my GNex has with CM10. I uninstalled it and tried again. After 30 power off/on cycles I haven't had one instance of it having the unlock delay...Seems connected in my opinion (in my case anyway).

I see nobody else here remembers having to wait for radio's or tv's to "warm up" before using them 1-2 seconds? HAHA, yeah, terrible lol I'm not talking just the 30's to the 60's here, I mean the 70's and 80's, I'm 41 Maybe those of us my age and older appreciate the tech now the most, because we've seen it progress so much from where it was.

First Freeze Issue after JB 4.12 update on GN 8013

I just had a scare. I updated my GN 8013 to JB 4.12 several days ago and haven't had any real issues. I let my Note go into hibernate to take a break and do some chores in between trying to finish an ebook checked out from my local library. The battery was at 68 per cent and I planned to be back to reading within 10 minutes. When I did get back to read and picked up my Note it wouldn't turn on. This is the first time this has happened. Jumping onto Google, it appears this has happened to other Samsung tablets in the past, usually after a software update. Here's a link I used and following the steps outlined in I then was able to reboot (keep finger on screen while holding down power button then reboot once battery icon appears on screen). http://mojocode.com/content/samsung-galaxy-tablet-101s-wont-boot My battery is still at 68 percent, but I'm leaving it plugged in while I do some other chores. I hope this isn't a new problem brought about by the update. If anyone else has this issue, I'd suggest we keep track so we can report to Samsung.

Yeah I think they call it the sleep of death. Happened to my recently updated wifi (8013)note also.

IF it is happening then only 8013 devices as none from other devices have reported so far. If two devices then it is a cause of worry

samir_a said:
IF it is happening then only 8013 devices as none from other devices have reported so far. If two devices then it is a cause of worry
Click to expand...
Click to collapse
I started the thread so we can see if it's happening to multiple units and what models and firmare seem to be affected. If more report the same issue, maybe this thread can be stickied. From what I read when looking for solutions, it seems to occur after firmware updates and has occurred on many of Samsung's tablets.

I have a N8000 and it's happened to mine three or four times since August; once on ICS. It would infrequently happen to my GT-P7500 on HC also. You can be in the middle of something and the screen goes black. No warnings or pop-ups, it just goes black. Nothing happens when you hit the power button normally like you would to wake it up. You have to hold the power button down for a looong time (maybe more than once) and the tablet boots. The first time it happens it's stroke inducing because you think your tablet's dead. After that it's just an annoyance. I have no idea what causes it but it does no harm (other than potentially losing unsaved work) when it happens. Between my OG G-Tab and the Note it's probably happened half a dozen times in eighteen months.

BarryH_GEG said:
I have a N8000 and it's happened to mine three or four times since August; once on ICS. It would infrequently happen to my GT-P7500 on HC also. You can be in the middle of something and the screen goes black. No warnings or pop-ups, it just goes black. Nothing happens when you hit the power button normally like you would to wake it up. You have to hold the power button down for a looong time (maybe more than once) and the tablet boots. The first time it happens it's stroke inducing because you think your tablet's dead. After that it's just an annoyance. I have no idea what causes it but it does no harm (other than potentially losing unsaved work) when it happens. Between my OG G-Tab and the Note it's probably happened half a dozen times in eighteen months.
Click to expand...
Click to collapse
On my GN 8013, I had to keep a finger on my screen while holding down the power button; that brought up the battery icon screen and from there I could reboot. Holding down the power button alone did not reboot and triggered my panic that drove me to a Google search and a solution to enable rebooting. This seems to be a long standing issue across versions of Android and manufacturers and seems to be a result of manufacturer code tweaking having unexpected consequences.

mke1973 said:
This seems to be a long standing issue across versions of Android and manufacturers and seems to be a result of manufacturer code tweaking having unexpected consequences.
Click to expand...
Click to collapse
I kind of look at it as the equivalent of the "blue screen of death" in Windows. My desktop PC throws a shoe every once in a while and it's usually tied to either graphics or memory conflicts based on the dump message. I'm guessing what we're experiencing is the Android version. As a pure guess I'd say it's something to do with memory reads/writes/buffers caused by either a management issue with the OS or an app (or combination of apps) doing something it shouldn't at an inappropriate time. And after playing with the power button I've gotten what you did (the giant battery icon showing up) and other times the Samsung boot logo. And I've had it happen twice in a week and other times once in six months; all without changing anything with the OS or apps. It's just one of life's little mysteries.
P.S. - My N2's done it but it behaves differently. It shows up a spontaneous reboot.

I had same issue frequently since last upgrade to 4.1.2 . I thought the problem is from Mobile VOIP. So I un installed it.
But today, another freeze happened. Ok, today just once. But, what's the problem?
N.b I recover it just by holding power button for 8 seconds.
Sent from my GT-I9100 using Tapatalk 2

mohammedsarhan said:
I had same issue frequently since last upgrade to 4.1.2
Click to expand...
Click to collapse
If it's happening frequently it may be something other than the random event some of us are talking about. A lot of you that upgraded from ICS to JB with all your apps intact could be having compatibility issues as not all apps have been updated/optimized yet. Older apps that are a little less mainstream and/or popular would be a good place to start to troubleshoot. Unless there's something specific to U.S. JB a lot of us have been on it since October and there haven't been any reports of frequent freezes or reboots. That is outside the random one discussed above that's not specific to JB.

mke1973 said:
I just had a scare. I updated my GN 8013 to JB 4.12 several days ago and haven't had any real issues. I let my Note go into hibernate to take a break and do some chores in between trying to finish an ebook checked out from my local library. The battery was at 68 per cent and I planned to be back to reading within 10 minutes. When I did get back to read and picked up my Note it wouldn't turn on. This is the first time this has happened. Jumping onto Google, it appears this has happened to other Samsung tablets in the past, usually after a software update. Here's a link I used and following the steps outlined in I then was able to reboot (keep finger on screen while holding down power button then reboot once battery icon appears on screen). http://mojocode.com/content/samsung-galaxy-tablet-101s-wont-boot My battery is still at 68 percent, but I'm leaving it plugged in while I do some other chores. I hope this isn't a new problem brought about by the update. If anyone else has this issue, I'd suggest we keep track so we can report to Samsung.
Click to expand...
Click to collapse
Pretty much exact same thing happened to me last night, for the first time ever. Took me about 30 seconds to get any response, by holding down the power button for a LONG time. Rebooted, saw the battery was below 20%, which was also odd since I had charged it overnight and had consistently been getting 2-3 days on a charge.
If it happens again, I'll go with Barry's suggestion and try a clean install, then adding apps one by one. Little disappointing though, as I've had no real problems at all with the GNote until this JB update.
Thanks,
JC

Sleep of Death...
I have the 16gb wifi GT8013 model and I am having the sleep issue too. Mine isn't "deathly" that requires the finger on the screen while powering up, or standing on your head and spinning three times while chanting "sleep of death" or any craziness like that, but every once and a while, for no rhyme or reason, I have to start it from a cold boot when I attempt to wake it with the power button. I press and hold the power button for 3-4 seconds and here comes the Samsung boot logo. Once it gets booted and connects to the wifi, I am good to go.
This happens so intermittently, with it not doing it for a couple days, or it might be within the next hour. I think I have narrowed it down to the wifi radio. Reason being...I have done a factory reset and tried running it naked and it still happened. But I have noticed the issue seems to happen when I have left the house and it drops the home wifi and then negotiates a new connection with my SIII hotspot, which I turn on before leaving the house for work, or anything that I will need connectivity for the tablet while away from the house. I don't know if it is due to roaming outside the home wife and dropping the connection, or if it is the combination of dropping the home wifi and then locking into the phone hotspot. I am so busy that I haven't been able to get that far in my troubleshooting. However, I am leaning to just the fact of it leaving a wifi signal and, I guess, it doesn't want to and gets jumbled and kills itself all together. I say that because it has happened when I have forgotten to turn on the hotspot until I got to work and then I open the tablet and its dead.
This has been happening from day one, when I bought the tablet towards the end of January. Unfortunately the Samsung warranty absolutely sucks, due to them wanting me to ship it in and do without it for 3wks and then to boil my blood even more, they want to give me a refurb unit if they can't fix this one. To make matters worse, its been almost a week now and they can't even get the shipping arrangements made yet! Needless to say, with this thing only being barely two months old, I am a little on edge with Samsung and I would love to figure it out and fix it myself. If it were something I knew, without a doubt, would be fixed with rooting and dropping CM on there, then I would. But I see there are still stability issues with most custom ROMs and I really would like to keep the functionality of the S-pen.
I have attempted to pull a log file with aLogCat and they are blank. It appears that the log files disappear when rebooted, which does me no good in figuring out what shut it down, if I can't recall the log from pre-shutdown. I have also tried aLogrec in hopes of accomplishing this, however, something isn't right because I left it recording for hours and days and the log file was only 1kb. Although, it doesn't much matter since the log recorder running in the background keeps it from sleeping to the point of shutdown, so I am assuming it is a sleep issue, due to that discovery.
If anyone has any thoughts that might help me, I am definitely all ears! This tablet is for work and school so it is next to impossible for me to do without it for 3wks...provided Samsung can get their crap in gear enough to even arrange the shipping for the service request. And I sure as hell don't want a refurb!!
Later,
Roger

I had periodic issues with the sleep-of-death once I updated to JB. It turned out that a VOIP program that worked fine on ICS (Sipdroid) crashed JB. I installed a different VOIP program that users said worked with JB (C-SipSimple) and my tablet stabilized. If you have non-stock apps that you use a lot, I would begin doing Google searches on them, starting with those that you use most frequently to see if anyone is reporting issues with JB (I wouldn't only rely on comments in playstore since users are more likely to engage in a discussin in a forum like this one). Good luck.

mke1973 said:
I had periodic issues with the sleep-of-death once I updated to JB. It turned out that a VOIP program that worked fine on ICS (Sipdroid) crashed JB. I installed a different VOIP program that users said worked with JB (C-SipSimple) and my tablet stabilized. If you have non-stock apps that you use a lot, I would begin doing Google searches on them, starting with those that you use most frequently to see if anyone is reporting issues with JB (I wouldn't only rely on comments in playstore since users are more likely to engage in a discussin in a forum like this one). Good luck.
Click to expand...
Click to collapse
Unfortunately, I have come to the conclusion it isn't an app issue. I have never used any VOIP service, of any kind, and I have done a factory reset and it happened before I installed any apps. Unless, of course, it is an app or service that is included in the Touchwiz junk and/or bloatware that comes with it. It happened on ICS, which is what came on it, and it happens after being update to JB. However, I only had it on ICS for a couple days and I would like to go back to it for further troubleshooting, but since it has been updated to JB, that isn't possible without rooting and I haven't decided if I want to do that yet.
--Roger

After further observation, it appears my sleep-of-death issues arise when I leave the comforts of my home Wifi. When doing so, apparently losing the Wifi signal causes the tablet to shut down completely... When asleep. If I have LogCatRec running, that keeps the tablet from falling into hibernate and the issue never happens, thus resulting in nothing interesting being logged, aside from the typical tablet activity.
Now the question arises, is it my home Wifi, or just leaving a Wifi range in general? I cannot get it to recreate the issue by simply turning off the Wifi signal it is currently connected to. However, I am now on a new Netgear router, due to the Belkin shooting craps on me, and it happened then, on the Belkin, and it happens now, on the Netgear. So, my presumption is that it has to drop a Wifi connection due to signal degredation, versus simply cutting a decent signal off at the source.
Has anyone else gotten this far with their sleep of death issue? Or is there another thread, that I've missed that I am just repeating? I am curious to see what's out there, before I send this thing off and its gone for three weeks!
-Roger
Sent from my GT-N8013 using xda app-developers app

I have no issues any longer after finding the offending app on my note and uninstalling it. I don't think there's one cause for this issue. Most often, Android OS updates seem to create program instability in some apps that then trigger the sleep of death. It gets hard to track down issues for individuals experiencing the sleep of death on their devices because we all have different apps installed. You might look at apps on your note that require WIFI to sync and are allowed to sync periodically since one of those may be the culprit. Check comments on Google Play to see if any are known to be buggy under JB. Good luck.

Mke1973, with all due respect, I dont think you are reading my post thoroughly.
As I have already said, this is not an app issue. I have done a reset and the issue still happens when I run it without any apps downloaded and installed. Unless it is an issue with a Samsung app that is preloaded, in which case the fix is still out of my hands, since the owner of the tablet can't uninstall crapware at their will, without rooting it.
Sent from my GT-N8013 using xda app-developers app

Actually, I wasn't ignoring your facts it's just that there are 3rd party apps installed by default that, if you decide to use them, require sync. Specifically I'm thinking of Evernote. Once device makers began pushing out upgrades to JB, some Android users began reporting incidents of the sleep of death when using or after closing Evernote in various Android forums. It wasn't a majority of people, but more than a smattering, but that is standard with the sleep of death. Again good luck on your hunt.

HELP REQ - Stock Lollipop Note 3 N9005 - Random Reboots/Wifi-BT Clashes

Hi all,
Having a problem here.
Had my N9005 for about 18 months, never really had any problems with it - or rather, never really required anything of it which might manifest any problems.
I've always used Stock ROM's, soft-rooted.
Never triggered KNOX.
I'm currently running Stock Lollipop (latest Switzerland Open). Everything I'm about to elaborate is also the same using Stock Lollipop (latest UK Open).
I'm rooted on Lollipop using the method compiled by The TAMAS on XDADEV.
I root because my phone is work-critical, and so I use Titanium Backup to keep my data/calls/APN/SMS backed up and to make restoring easy, as well as to disable stock bloatware etc.
The problem may have pre-existed in pre-Lollipop ROM's, but the sequence of changes which caused it to be manifested included my need to update to Lollipop, about 5/6 months back.
THE PROBLEM - First and foremost, the damn phone reboots randomly. I become aware of it because it will vibrate for startup and play the Samsung startup tone and splash screen before booting to normal functionality. It can do this day or night, maybe 3-4 times a day. I have no error messages or warnings, it's done it while in my hand, while plugged in charging, while out and about, in the car, on wifi, on data. MOST times it reboots. SOME times it just shuts off and I don't realise it's off until I go to use it, or get a call on a second phone to ask why I'm not responding to calls or messages.
When it reboots itself, if I go to the Samsung Battery control panel pane and take a look at the battery chart it will show a gap which is longer than the time it took to reboot, and a shift in the battery meter level.
But, that's not the only possible symptom or problem with the phone.
I've noticed also that my WIFI does a lot of crapping out, or slowing to a crawl, even on my home AP. I've reset AP's, reset networks, reset the phone, forgotten and then reattached the AP in WiFi Settings. So I downloaded the Ookla Speedtest App, to see this issue in black and white, and sure enough, even though any other Android or iOS or Windows or OSX device in my place can connect via Wireless AP to my fibre connection and get great consistent throughput, the Note 3 can often appear crippled...
At it's best, it responds to ping quickly on the Speedtest app, and leaps up to the 30-40Mbps range with consistency for download, and up to 17-20Mbps for upload. This is the least I would expect it to do, my target standard.
At it's worst (which can be 'most of the time') it responds slowly to ping, and either struggles to get over 250Kbps download and maybe a crazy Meg or two for upload, consistently, a slow grind; or it may oscillate extremely wildly between slow and high speeds before eventually settling to unacceptably low transfer rates.
Up to press, I've been trying to chase these problems in isolation, believing them to be unconnected.
No success.
I've reflashed several times. I've Factory Reset. I've wiped data and cache. I've reinstalled and restored from Titanium. I've reinstalled and restored nothing but my SMS's and Call Logs. I've reduced my installed apps to bare minimums. I've tried it with a MicroSD installed, and without. I've bought another battery and replaced it. I've tried it in its case and without its case.
Then I started thinking that the problems were all the same thing, and stemming from the same root.
It suddenly occurred to me that my use of the phone changed significantly at the same time as I moved to Lollipop.
I need to be on Lollipop because apps and hardware that are critical to me are Lollipop dependent.
All at the same time, I began using a Moto360, a Bluetooth Receipt Printer and a Bluetooth Credit Card Reader, all of which are deficient in functionality or in some way hamstrung by not using Lollipop.
So I had gone from occasional BT user (maybe PlayerPro plus a BT link to headphones or my stereo occasionally; when needed, BT speakerphone in car) who usually turned BT off manually to preserve battery life, to a constantly connected BT user...
So I went back to Speedtest app, and tried to test the WIFI connection again. Sure enough, it was pitiful. Then I simply disabled BT on the N9005 and ran the test again, and had full 'through the roof' speed ratings.
I've tried this back and forth hundreds of times now, and it is predictable and established. BT is somehow crippling WIFI on my N9005.
I've tried running the phone on either wifi or data only, with BT off, and had a couple of days use at a time without any restarts. Put BT back on permanently, and the restarts resume within hours.
I'll be honest, I've even been cursing and swearing at my BT devices, because BT sometimes struggles to even maintain a continuous connection. I get vibrations all the time on my Moto360 indicating that the phone, which is on my person, has disconnected from the watch again, perhaps just for moments, sometimes for minutes, resulting in the watch eating battery life, trying to get reconnected.
I'm convinced now that all these things are related, and the problem lies somewhere in the interaction between BT and WIFI in my N9005.
It seems likely that I never noticed the problem before because I never required continuous BT connection before the point where I installed Lollipop.
Downgrading the ROM isn't an option. Leaving BT off isn't an option (nor should they have to be, on an 18 month old £600 smartphone).
Does anyone else have experience of this? Has anyone else had problems that they now suspect might be this same problem? Does anyone understand what's going on hardware/software wise, or have experience of a solution to these issues?
I'd appreciate your input urgently, even if only to affirm that I need to go to the inconvenience of temporarily buying another phone to replace this, while I send this away for a warranty repair.
Is this even a recognised hardware fault, or would I just get back an identical unit which is crippled from being able to perform as I expect it?
Please help.