Database Info

Wifi not turning on

My sensation's just fell from my hand on floor from around 2 feet of height n now my wifi is not turning on as well as bluetooth when ever i try to turn it on it says turning on n after some time it says error any suggestions

Oh come on 125 views n 0 replies :/

Azroid said:
My sensation's just fell from my hand on floor from around 2 feet of height n now my wifi is not turning on as well as bluetooth when ever i try to turn it on it says turning on n after some time it says error any suggestions
Click to expand...
Click to collapse
Take the back off and look at the copper contacts. Are they still intact and none are broken off? If all looks stable, try flashing a rom. If that doesn't work, back up and do a factory reset and reflash a rom. GL

kpjimmy said:
Take the back off and look at the copper contacts. Are they still intact and none are broken off? If all looks stable, try flashing a rom. If that doesn't work, back up and do a factory reset and reflash a rom. GL
Click to expand...
Click to collapse
did all of this none worked for me

You sure it's not your router? Some channels might not work with your device, router might auto select channel, manually change to different channels, have you tried on a different router,
Sent from my CM7 Sensation XE using xda premium

whynot66 said:
You sure it's not your router? Some channels might not work with your device, router might auto select channel, manually change to different channels, have you tried on a different router,
Sent from my CM7 Sensation XE using xda premium
Click to expand...
Click to collapse
I said my wifi is not turning on i didnt said it aint connecting my router, so connection is not my problem, read the thread carefully u'll know the main problem

ah i see, well the wifi and bt share the same antenna wich is the top antenna so if neither are working it must be this,check the metal pins in the back plate and check the plate above the camera. so you have warrenty??

Pins are perfectly normal n no i dont have warraty so yeah dunno what to do know

I also encountered this issue...
My case is the same, my Wi-Fi turns on - but stays on a loop. Turning on, scanning for network, turning off... rinse and repeat. But though I'm left curious about my case because my phone works when the case is off. which leaves me to think that the case is faulty in some sort of way. But to make it loop? that's odd on how the system works. This occurred to me when I was on the Virtuous Quattro ICS rom, I reverted back to stock, changed Kernel, changed Radio, Changed RIL, and nothing.
Then as I kept wiping with CWM, I thought to myself... if I'm wiping the system, how come CWM stays on it? And left me to wonder if all the people who have this issue is because there is some sort of cache or saved setting in one of the files that we are unable to wipe? and if that is the case, is there a way to actually wipe EVERYTHING off the phone? Or at least some script that can be written to wipe such information without damaging the phone? I'm at wits end with this issue, and for me, I hope it's the case. For I encountered this same issue with my Sensation when it was brand new (about 2-weeks old) and got to return it. I have warranty with my phone (the kind you pay monthly on the bill) so if a new case doesn't fix my problem, I may claim my phone lost or robbed, and get a new one. Though I think it would be the new Nexus, not feeling so confident about Sensation at the moment.
BUT! Please let me know if you find a fix.

To me it looks like a hardware problem though the antennas in the back cover n on the cell phone are perfectly fine but i have no idea wth is wrong with my device coz it fell from the 2 feet of height n it started to have this problem i mean seriously is sensation that delicate :/ i'm doubting the built quality of htc now

Must be. I mean why would it loop ONLY when the back lid is connected to it? I'd test out the bluetooth to see if it works as well but I currently have the Virtuous Quattro ROM installed and the Bluetooth feature does not work. *Sigh

Leonarthius said:
Must be. I mean why would it loop ONLY when the back lid is connected to it? I'd test out the bluetooth to see if it works as well but I currently have the Virtuous Quattro ROM installed and the Bluetooth feature does not work. *Sigh
Click to expand...
Click to collapse
I thought Bt wasnt working in Quattro. That's why I stayed away.
As for the fall, I have a tpu hyrid Aprolink case with a Seidio Active holster. Fell from a 3 feet drop and nothing was harmed. Do you have a case on your Senny?
But yes, try the BT connection and try there. Have you tried a factory reset of the phone?

I've been reading threads after threads and I see this person did a hardware fix, something I myself am not willing to try, but gave me some ideas.
This being the thread: http://forum.xda-developers.com/showthread.php?t=1204311&page=2
My idea is that if this person reset this chip by heating it up, I can probably do the same using the development tools and see if that works.

Exact same problem.
Htc Sensation XE two months old - stock rom - hasn't been rooted or modified in any way.
The following just stopped working for no reason;
Wi fi shows 'error' and wont turn on.
Bluetooth also fails to turn on
FM Radio app 'FM Turning On...' gets to 95% then says 'Turning off...'
On boot I'm getting this error,
'Process com.android.phone is not responding'

i've repaired my cellphone it was a hardware problem for me

I was having the same issues. Started reading this thread. So, i thought what the heck, i have 2 sensations, so i pulled the battery cover off of mine and put it on my wifes, the one that is not working, and what do ya know, wifi connected immediately!! Thank you to this thread!

Azroid said:
i've repaired my cellphone it was a hardware problem for me
Click to expand...
Click to collapse
Azroid - could you explain how you repaired your phone?
---------- Post added at 05:52 AM ---------- Previous post was at 05:49 AM ----------
jtc442 said:
I was having the same issues. Started reading this thread. So, i thought what the heck, i have 2 sensations, so i pulled the battery cover off of mine and put it on my wifes, the one that is not working, and what do ya know, wifi connected immediately!! Thank you to this thread!
Click to expand...
Click to collapse
jtc442 was it the looping problem or the 'wifi error' that this fixed?

I dropped mine yesterday, and wifi and bt both doing same thing on loop, cant see no damage to contacts at top. i have no warranty on phone either. im almost certain mine is a hardware issue but dont know where to start to fix it!
please help

elspam99 said:
I dropped mine yesterday, and wifi and bt both doing same thing on loop, cant see no damage to contacts at top. i have no warranty on phone either. im almost certain mine is a hardware issue but dont know where to start to fix it!
please help
Click to expand...
Click to collapse
You should visit a good repairing shop if you have any around you.

My Sensation XE has been two times in for repair for this issue. Wifi/BT doesn't turn on, it says "error" after trying to connect after a while.
Both times they changed the main flexboard, that's actually the whole dmn phone. It was offcourse free of charge, but turnover time is nasty and it's a pain reinstalling everything again....
I've seen this so many times here and other board that I'm inclined to say that the Sensation has a design flaw that makes it VERY susceptible to damage to the wifi. Even a small drop, just a few inches onto a table might do it......
I think we are going to se more and more of these issues from now on..

[Q] No tablet display but HDMI works.

Hi,
Yesterday (08/02/2013) I updated my tf700t, everything seemed to be fine after it rebooted, I was playing a game, the battery was low, and it turned off abruptly. I assumed it automatically shutdown because of the battery, so I put it in the dock and plugged in the charger. Several hours later I tried turning it on and nothing. I held down the power button for 8 seconds felt the double vibration, but no display. I tried various combinations of docked/undocked, power cord plugged in, holding the power button for 30-60 sec. etc. but nothing.
Out of curiosity I connected the HDMI to my computer monitor and sure enough, it was there, I could unlock it and everything seems to be functioning fine, just no display. The digitizer seems to work fine, although guessing where things are at is pretty tough.
I think I tried the cold boot, volume up/down (I tried both) plus power, and it didn't make a difference.
In order to do the update I had to flush the DMC Client and CMClient data and cache, I had been getting errors from DMC Client crashing.
Also I'm not certain this is update related, as the tablet had been acting wierd, which is why I did the update. I would press the power button to turn the screen on and nothing would happen, so I'd hold it down longer and the tablet would reboot and finally the screen would come on, or it would come on a few seconds after I pressed the button. I was getting a lot of reboots etc... I thought the update might resolve this.
I'm not sure if the problem is hardware, firmware, or software related.
I'm wondering if when I flushed the DMC and CM Client cache, maybe I deleted the drivers for the display or something?
My options seem to be:
1.) Factory reset by feeling around the digitizer while connected to HDMI
2.) Factory reset via the pinhole
3.) Install new (old) firmware via usb/computer. (the device is recognized by Windows 7 so I think this is doable.)
4.) Send it off to Asus. (would this be free?)
So my questions are:
1.) is there something else I should try?
2.) what order should I do the above in?
*Note: I'd like to save my data somehow.
*Edit: I forgot to mention I was on 4.2.1, no root or anything. Also I bought this in July of '12 so I'm pretty sure it is out of warranty. Any idea how much it might cost to send it off? Perhaps I could replace the LCD myself? I replaced the digitizer/screen on an ipod touch, although I'm sure this LCD is much more expensive and much harder to replace. This is turning into a nightmare. So much for trying to keep my data, now I hoping to keep this from becomming a paperweight.
Thanks.

A bloke at work had this issue. He let it rundown and left it for 3 days. It worked fine again after that.

zpyatt said:
I'm not sure if the problem is hardware, firmware, or software related.
Click to expand...
Click to collapse
If you don't even see the boot logo, it cannot be software related.

Thanks for the replies.
I'll try letting it run down. Would putting it in the freeser be helpful/safe?
I guess on the software/firmware it depends on the definition. To me drivers are software, firmware is anything written in VHDL. I suppose what I'm really wondering is if it is software/firmware vs. hardware, i.e. is the LCD or some other component dead or is the display just not getting written to, initialized or whatever.

zpyatt said:
I'll try letting it run down. Would putting it in the freeser be helpful/safe?
I guess on the software/firmware it depends on the definition. To me drivers are software, firmware is anything written in VHDL. I suppose what I'm really wondering is if it is software/firmware vs. hardware, i.e. is the LCD or some other component dead or is the display just not getting written to, initialized or whatever.
Click to expand...
Click to collapse
I wouldn't put the tablet into the freezer.
Does the backlight come on? If not, it's definitely a hardware problem. If the bootloader boots fine but doesn't show anything, that also looks like a hardware problem.

_that said:
I wouldn't put the tablet into the freezer.
Does the backlight come on? If not, it's definitely a hardware problem. If the bootloader boots fine but doesn't show anything, that also looks like a hardware problem.
Click to expand...
Click to collapse
I'm not sure about the backlight, I think maybe it does, it is kind of hard to tell. I'll try checking in a dark room tonight. Since the screen is just black I suppose I'm looking for a brighter shade of blackness?
The bootloader is definitely booting fine. That is what I meant in my original post, the HDMI out works, I can see everything there, I can even swipe and tap the digitizer and do stuff, it is just difficult to guess where things are at. Do I need to go back and clarify this in my original post?
Do you think this definitely means it is a hardware problem? I figure I'll try letting the battery run all the way down and let it sit a few days and recharge it as sbdags suggested, in the meantime perhaps I should contact Asus, but I'm not lookinf forward to that.

zpyatt said:
I'm not sure about the backlight, I think maybe it does, it is kind of hard to tell. I'll try checking in a dark room tonight. Since the screen is just black I suppose I'm looking for a brighter shade of blackness?
The bootloader is definitely booting fine. That is what I meant in my original post, the HDMI out works, I can see everything there, I can even swipe and tap the digitizer and do stuff, it is just difficult to guess where things are at. Do I need to go back and clarify this in my original post?
Do you think this definitely means it is a hardware problem? I figure I'll try letting the battery run all the way down and let it sit a few days and recharge it as sbdags suggested, in the meantime perhaps I should contact Asus, but I'm not lookinf forward to that.
Click to expand...
Click to collapse
I don't know what is the cause but like I said I saw this with my very own eyes - the same as yours. Double buzz on boot not screen but HDMI worked. Somehow completely draining the battery fixed it ...... So hardware / software? Who knows? If it was hardware why did draining the battery fix it? The device has been absolutely perfect for 3 months since and has never done it again.....

sbdags said:
I don't know what is the cause but like I said I saw this with my very own eyes - the same as yours. Double buzz on boot not screen but HDMI worked. Somehow completely draining the battery fixed it ...... So hardware / software? Who knows? If it was hardware why did draining the battery fix it? The device has been absolutely perfect for 3 months since and has never done it again.....
Click to expand...
Click to collapse
Thanks sbdags, I will definitely try this. I'm not sure if I should hurry and contact Asus though, I bought this thing around July 22 2012 I think so it is barely more than a year old, not sure if they would cut me some slack on the warranty or not.
Do you think I need to let it sit three days or just make sure the battery is good and run down before charging again? Also I've seen some suggestions for charging from a computer vs. wall as it charges slower, do you think that would be better?
I'm getting into panic mode and want to make sure I don't do anything rash that limits my options.

zpyatt said:
Thanks sbdags, I will definitely try this. I'm not sure if I should hurry and contact Asus though, I bought this thing around July 22 2012 I think so it is barely more than a year old, not sure if they would cut me some slack on the warranty or not.
Do you think I need to let it sit three days or just make sure the battery is good and run down before charging again? Also I've seen some suggestions for charging from a computer vs. wall as it charges slower, do you think that would be better?
I'm getting into panic mode and want to make sure I don't do anything rash that limits my options.
Click to expand...
Click to collapse
All he did was leave it for 3 days. Our assumption was that the battery had completely drained in that time....... A charge later (he was actually just about to box it to send to Asus) and it surprisingly started as if nothing had happened.

Having the same problem
I am having almost the same problem, except that the tablet screen works when the wall charger is plugged in. THe HDMI display and the digitizer work fine. It is just the tablet's screen dispaly when the charger is unplugged.
sbdags said:
All he did was leave it for 3 days. Our assumption was that the battery had completely drained in that time....... A charge later (he was actually just about to box it to send to Asus) and it surprisingly started as if nothing had happened.
Click to expand...
Click to collapse

So I didn't have any luck letting it run all the way down.
I contacted customer support, the warranty is only 1 year, but fortunately for this there is an extra 3 months, so I just managed to squeak by, although I'm keeping my fingers crossed.

same problem as you both
i have d same problem well until last week the screen displays when conne ted to wall charger now its all blank but iy works via hdmi, digitizer works fine but all blank, this tf201, does anyone know if i change d whole display it will work?
i already bought the tf701
any suggestions is welcomed and did you get youra to work?

zpyatt said:
I guess on the software/firmware it depends on the definition. To me drivers are software, firmware is anything written in VHDL.
Click to expand...
Click to collapse
I have not seen people mentioning VHDL and verilog for a while, hahaha... It sounds like you are a low level or physical layer programmer. Any way, a firmware is in general a low level program that communicating with the hardware and the software or high level program ( level 7).. If you will, a firmware is a management levels (level 2 and 3). A VHDL is a level 1 which generates a 0's and 1's or mapping the transistors in the FPGA chip for example.... Oh well, it is just my definition...
zpyatt said:
I suppose what I'm really wondering is if it is software/firmware vs. hardware, i.e. is the LCD or some other component dead or is the display just not getting written to, initialized or whatever.
Click to expand...
Click to collapse
If you can get the output from the HDMI port, it is more likely you have a hardware problems. I think that the problems are your display related hardware. If you really want to troubleshoot your issues, you can look on the mother board to locate all the electrolytic caps and check to see any abnormal signs of those capacitors. Those caps are the one that will blew up first before any others parts go....Good luck...:fingers-crossed:

Messed-Up Display

Hello XDA,
My Nexus 5 running CM12 5.0.2 nightly will not respond to the touches anymore infact when I press the power button to activate the display it acts as if someone is touching it randomly messing all the apps that are running and opening and closing many other things.
Furthermore it displays weird and burned lines throughout the screen. It was not dropped, no water went inside the device or anything. If it helps I did install the OTA updates that CM gives us.
I have also attached pictures so you may get a better understanding of my problem.
Thanks in advance.

Saad S. said:
Hello XDA,
My Nexus 5 running CM12 5.0.2 nightly will not respond to the touches anymore infact when I press the power button to activate the display it acts as if someone is touching it randomly messing all the apps that are running and opening and closing many other things.
Furthermore it displays weird and burned lines throughout the screen. It was not dropped, no water went inside the device or anything. If it helps I did install the OTA updates that CM gives us.
I have also attached pictures so you may get a better understanding of my problem.
Thanks in advance.
Click to expand...
Click to collapse
Has this happened after you flashed a rom or.. ??

semirr said:
Has this happened after you flashed a rom or.. ??
Click to expand...
Click to collapse
Yes after I flashed the rom but not directly after. But after a good 1 month.

Saad S. said:
Yes after I flashed the rom but not directly after. But after a good 1 month.
Click to expand...
Click to collapse
Hmm I see. Well since a month HAS passed, its definetly not the rom thats causing the problem, i don't know if anything regarding the software could even be causing the problem. Its 100% hardware and by that i mean the screen, you should change it, the touch and also the display are messed up.

semirr said:
Hmm I see. Well since a month HAS passed, its definetly not the rom thats causing the problem, i don't know if anything regarding the software could even be causing the problem. Its 100% hardware and by that i mean the screen, you should change it, the touch and also the display are messed up.
Click to expand...
Click to collapse
Is it possible that a driver update could fix this, if so then how?

Saad S. said:
Is it possible that a driver update could fix this, if so then how?
Click to expand...
Click to collapse
Hmm i dont think that a driver could be the problem. And if it is i dont know how you could fix it Google it

I hate to be the bringer of bad news - but your screen is toast. Fortunately you can replace the touch and display components all at once.
http://www.amazon.com/Skiliwah-Digitizer-Assembly-Google-nexus5/dp/B00HN0U168
Here is what you need to perform the repairs - and here are the procedures for disassembly.
https://www.ifixit.com/Teardown/Disassembling+Nexus+5+Display+Teardown+-+liquid+damage/32410
Trust me, it's not that difficult. Unfortunately, it's a bit pricey ($60 for the screen and digitizer), nevertheless much cheaper than a new device or sending your device in for repairs.

Rma

Problem Solved
The screen isn't toast, neither is the digitizer. I have 2 of these phones. The parts which cause problems like this are the main board and the ribbon with the USB connector on it, which also attaches the screen & digitizer to the main board. One was showing lines exactly like this, & also no touch. I put a replacement main board in. Works great now. The other, wouldn't even turn on. I put the main board from the first phone in the second one, it still wouldn't turn on. I replaced the ribbon cable, it turns on and perfectly replicates the issue from the first phone. So now, I have one fully functioning LG Nexus 5, and another which turns on with the same problem as yours. This is good, I started out with 2 of them that were useless to me. So, it appears that your display and touch issues are caused solely by a bad main board. A replacement main board costs somewhere around $75. After swapping stuff around, I have 2 bad main boards, 1 bad USB ribbon & 1 working phone of 2. Not bad, not bad at all.

Wifi Problem - freezes sometimes and cant disable. Have to restart. LP & KK

Hi guys,
I have a problem that I've never seen or heard of before. So here is the situation:
Power button didn't work, so RMA'd phone. Got different phone back and instantly rooted/installed custom rom. Didn't notice anything until a month later. My phone would randomly just lag out and the wifi would stop. It would still show connected and that there was uploading activity, but that is all. When I clicked it to disable, nothing would happened. I would have to restart the phone, disable it for a while then re-enable it. I though it was the rom so I switched. Noticed the same thing is happening. I decided to play around with my sim, so I took it out and then put it back in, and it somehow fixed the problem. So I was assuming it was the sim causing the problem. Worked perfect for a week then started happening again. I did the thing with the sim and it didn't work this time. I still have the problem now.
Basically, my wifi would just stop working, when I click on it the phone lags out and freezes. I have to restart the phone and it will work. Sometimes Itll work for a full day then all of a sudden just stop. Sometimes it happens just a few minutes after restarting. I mostly find that it happens when the battery is less than 20%. Right now I am running stock LP, locked bootloader. I was supposed to send it in but they wouldn't accept it because I was 6 days over my warranty. So I'm not sure if I was send a faulty phone and now I'm stuck with it?
LG said I would be charged $150 flat rate for them to fix it which sucks. I'd rather just get a new phone and stay away from LG in the future.
Any suggestions? Also this was happening on KK at first then I tried LP Roms and same thing. I have never flashed any radio since I got the phone, could this be a possible solution?

s.hack said:
I was supposed to send it in but they wouldn't accept it because I was 6 days over my warranty. So I'm not sure if I was send a faulty phone and now I'm stuck with it?
LG said I would be charged $150 flat rate for them to fix it which sucks. I'd rather just get a new phone and stay away from LG in the future.
Click to expand...
Click to collapse
You would get the same reply from pretty much any company, once it is over the warranty period then it is over the warranty period, this is no reason to "stay away from LG". Most charge a flat rate since they're likely to simply do a motherboard/whatever board swap if the fault is to do with internal components, as it is much easier/cheaper for them to do this compared to diagnosing and repairing/replacing things individually.
s.hack said:
Any suggestions? Also this was happening on KK at first then I tried LP Roms and same thing. I have never flashed any radio since I got the phone, could this be a possible solution?
Click to expand...
Click to collapse
Try a different radio version. If it doesn't change anything then you have a hardware problem.

Elluel said:
You would get the same reply from pretty much any company, once it is over the warranty period then it is over the warranty period, this is no reason to "stay away from LG". Most charge a flat rate since they're likely to simply do a motherboard/whatever board swap if the fault is to do with internal components, as it is much easier/cheaper for them to do this compared to diagnosing and repairing/replacing things individually.
Try a different radio version. If it doesn't change anything then you have a hardware problem.
Click to expand...
Click to collapse
The only reason I said I would stay away is because it seems that I sent in my phone with a problem only to receive another one with a different problem. I'll try the radios tonight, hopefully it works.
Thanks, I'll keep you guys posted.

s.hack said:
The only reason I said I would stay away is because it seems that I sent in my phone with a problem only to receive another one with a different problem. I'll try the radios tonight, hopefully it works.
Thanks, I'll keep you guys posted.
Click to expand...
Click to collapse
You mentioned that you only ran into issues after a month. During that month a hardware issue could have possibly developed and the device was fine when you initially received it.

Known LP bug.. Thats why i still stay with kk
Sent from my Nexus 5 using XDA Free mobile app

[Q] heat damaging phone?

I'm having several issues with my AT&T LG G3 (stock ROM) and I'm not sure if they're related or what the next steps should be for troubleshooting. Here's the timeline of issues:
Over the last couple of months my LG G3 and the battery has been getting really hot to the point the phone is unbearable in my pocket. I usually restart it and the temperature goes down (until it eventually goes back up hours later under normal usage). (NOTE: I got a notification only once during this time saying charging is disabled due to high phone temperature)
Suddenly today bluetooth and wifi won't turn on and they both give an error saying "connection not allowed" (cellular and gps works fine). I restart the phone, problem exists. Disabled battery saver mode/feature, problem exists. Booted into safe mode, problem exists.
Now when toggling the wifi and bluetooth button in settings the phone freezes temporarily, restarts and then freezes at the AT&T logo booting screen. Holding the power button for 10 seconds doesn't restart it/power it off - only pulling the battery out, waiting a couple of minutes and putting it back in does it power up (it does not power back on if I put the battery back in immediately). Then it gets to the LG logo booting screen (sometimes the AT&T logo screen), but restarts itself 2 or 3 times before finally booting into Android.
So, software problem (Android having issues talking to the bluetooth and wifi radio or corrupt system files)? Hardware problem where the excessive heat over the last couple months have caused damage to the bluetooth and/or wifi radio or some other components? Or maybe its the battery is damaged by the heat and now it gives bad voltage, amperage, etc. to the phone?
Any kind of help would be appreciated.
Thanks

sounds like a hardware issue to me. How long have you had the phone? Have you tried connecting your phone to a power outlet and seeing if the issue persists?

rquiett said:
sounds like a hardware issue to me. How long have you had the phone? Have you tried connecting your phone to a power outlet and seeing if the issue persists?
Click to expand...
Click to collapse
I just went into the AT&T device support center and they replaced it since it was still under their 1 year warranty. I can say for sure it's a hardware or software issue and not a damaged battery issue as the battery is in the new unit (actually "certified like new") and it's working fine (battery life is much better too). I wish I tried a factory reset to narrow it down further but I felt I was annoying the AT&T techs and just wanted to leave (they did me a favor of giving me a replacement phone on the spot, but I wanted to troubleshoot the old phone further being the persistent nerd that I am, LOL).
So if you have any of these issues, I recommend backing up your phone and factory reset it. If the issues persist then it's likely a hardware issue and needs to be replaced.
Hopefully that helps someone.

What really is the prob...
DiGiTY said:
I just went into the AT&T device support center and they replaced it since it was still under their 1 year warranty. I can say for sure it's a hardware or software issue and not a damaged battery issue as the battery is in the new unit (actually "certified like new") and it's working fine (battery life is much better too). I wish I tried a factory reset to narrow it down further but I felt I was annoying the AT&T techs and just wanted to leave (they did me a favor of giving me a replacement phone on the spot, but I wanted to troubleshoot the old phone further being the persistent nerd that I am, LOL).
So if you have any of these issues, I recommend backing up your phone and factory reset it. If the issues persist then it's likely a hardware issue and needs to be replaced.
Hopefully that helps someone.
Click to expand...
Click to collapse
They over clocked the CPU too much to make up for lost speed from all there bloat wear. Solution....only run there apps....or root. I tell ya,,arrg.....Mine was getting so hot it was uuncomfy on my ear. Way to go Driod, google and At&t

I received a supposedly "new" unlocked LG G3 D850 1 week ago. I wanted to ensure it worked before I loaded my stuff so I didn't put a SIM in for the first 5 days. It had a wifi problem in the first 10 minutes, but then wifi worked for several days while the phone just sat there and I checked weather and news occasionally. I needed to test with my SIM before the return period expired and I ran into a small problem there. That got resolved but neither wifi nor bluetooth have worked since then. "Connection Not Allowed". I see it's a VERY common problem for many LG phones. If this is a new phone, how can it be heat damaged already? I think it's defective hardware or a software bug. I haven't even loaded any new apps on the phone - it's completely AT&T stock. I will probably return it and pick a different brand.