Related
hi all.
As I mentioned in my other post I have been having some serious wifi problems. Basically if I leave the wifi off the phone seems to work fine. When I turn it on however, the phone becomes laggy and it does not work. After turning the wifi on from the settings page, it says it is scanning for networks. After 20-30 seconds a little bubble pops up and says "unable to scan for networks" it will continue to try and scan on and off but never is successful. The phone is better to start up with the wifi off because if on, the phone becomes almost unresponsive and I am assuming it is because it is trying to scan in the background.
I just rebooted into the recovery menu and wiped the cache and device, but no luck. Any other ideas as to why this is happening?
Little update:
I found a few other threads where people complained about the same problem. Their recommended fix involved removing the file "/data/wifi/bcm_supp.conf"
The full thread is here: http://androidforums.com/samsung-moment/46179-unable-scan-networks.html
I tried that and also did a factory reset but unfortunately have not been able to fix the problem. Does anyone else have any other ideas?
hi Scales11
I'm also having the same problem..
did the
1. factory reset
2. new ROMs - Darky 7.01, Cognition 2.3...
3. delete the /data/wifi/bcm_supp.conf file
and still no luck... and realised bluetooth isn't working either..
anyone?? please help?
If you have flashed other ROMs and still the same issue. I would say its a hardware issue.
my fix
Geekboy9:
I meddled it for hours and while others have found various odd reset/rom fixes, I concluded that it was a hardware issue which cannot be fixed.
I flashed it back to a stock rom and went to att. They agreed that it didnt have any water damage and gave me a number to call about getting a replacement. Since the phone was less than a year old and its failure was not due to my use, the replaced it with a refurb. All in all the refurb seems fine, even after I rooted and flashed the cognition rom. I would recommend you do the same.
Hi, I have a g1 that has suddenly stopped working - when I start it I see the t-mobile screen and then it switches to the android screen and just stays like that and doesnt start.
It stalled while making a call and I was not able to restart it.
I have tried wiping everything from recovery console (http://forum.xda-developers.com/showthread.php?t=566669) and re-flashing my phone with my old firmware (http://forum.xda-developers.com/showthread.php?t=811620)
I don't know what's next here - can anyone please help?
some more background:
I had the phone for two years here in the US and have traveled out side of the country with it for several trips with no problems whatsoever, however, this phone I have given to my niece who doesnt live in the US.
The reason i'm saying this is that maybe the cause is a radio problem of some sort...
Let me know if you think of something coz I really don't know what do to next
Thanks,
e.
First of all, wrong section.. (Please post in Q&A)
If you had poked around and used the search feature, i'm pretty sure you can find what you are looking for
but anyhow, you need to flash another rom (via recovery) assuming you have already rooted because you somehow corrupted the system partition.
Thanks for the reply, I tried using cyanogen's mod but it didnt get me anywhere, I will try different mods but could this be a radio issue? is there a way to check that?
p.s. I did a thorough search of the forums and that's how i did all the things b4 posting but then I got stuck...
Hi, sorry I posted in the wrong section, just noticed what you mean.
Can any of the admins move this thread to q&a (or can I do it myself somehow)?
Data?
eladkatz said:
Thanks for the reply, I tried using cyanogen's mod but it didnt get me anywhere, I will try different mods but could this be a radio issue? is there a way to check that?
Click to expand...
Click to collapse
My friends phone is doing something extremely similar. He gave it to me to play with to make sure he wasn't mad, and it was actually the phone having issues.
Upon playing with it for a few hours problems started to occur. It would randomly shut off, then not want to reboot unless left sitting. It would get after the ROM screen and then shut off. I noticed that that a quick was to crash it was to start browsing the Internet over Wi-Fi. After a few pages loading and moving around the pages as they loaded the poor phone would just turn off.
Since he is using another phone in the mean time, I got his G1 without a SIM card. I was playing games on it, poking around in applications and more and the phone wouldn't turn off. I wasn't till I enabled Wi-Fi that problems started happening. I'm not sure if the Wi-Fi driver is part of the baseband unit or not but it seems that the more data the phone uses (3G or Wi-Fi) heightens its chance of turning off.
To get the phone to boot again I either have to take the battery our for a few minutes or leave it off for a while. Upon which time it will book as if nothing happens.
I also noted that every time it boots it shows an exception error related to "gapps" and you have to click force quit. His phone is running CyanogenMod 4.2. Also the Home key doesn't function, but this is software related because it can turn the screen on.
Scott
I am one of the many who have been experiencing the random reboots. I have seen talk about it, but have not seen anyone really looking into why this is happening. Some people claim it happens only when docked, or when SD card is in etc. Yet others post that they still get the reboots without doing those things either.
I have been monitoring my reboot problem very closely. I have yet to determine the cause other than it only happens when the device is put into sleep mode manually or automatically, and I am looking for some help from some of the DEV's around here.
When our TF's do this reboot, it is a system crash. When this happens, a ROMDUMP file is placed on the internal "sd card".
These can be viewed with a simple txt editor, like windows notepad. I myself can not read the code and understand what info it is revealing to me. According to an Asus tech on the phone this file can tell you what went wrong and made the device reboot. However the buggers won't tell you crap over the phone and want me to send the device in with the ROMDUMP files.
When I try and read the files, I do see one thing in common, in 99% of them, right near the end of the file, or the very last line before the crash, this line is present,
Kernel panic - not syncing: Fatal exception in interrupt
<2>[ 162.985309] CPU1: stopping
If our reboot issue is kernal based, which would indicate it's a firmware issue;
I was thinking one of the talented DEV's around here could fix us up.
Hell maybe even just a reflash of the current firmware would fix the issue.
Anyway, if a DEV around here want to or willing to look into this, I have some ROM dumpfiles they can look at, just send me a PM.
For reference,
I have a B60K modle
Stock 3.1
GPS 1.3.1
Wifi 5.1.42
BluT 6.17
Kernal 2.6.36.3-00001-gf377a2b [email protected] #1
Build HMJ37.US_epad-8.4.4.5.2-20110603
Thanks.
I don't have any more dumps recently, deleted them so I can't pull up and see what mine said to give you, but wanted to just say I was having these multiple times a day every day and it started once I bought an AData 16GB SDCard for the dock. Then I ended up removing that card and bought a MicroSD 16GB card instead and it has quit doing the random reboots, so definitely seemed to be something with my SDCard in the dock.
Post your whole log here (as .txt or .zip) and I will look at it.
I've had these once or twice but have always deleted the file.
The Kernel Panic is the kernel's way of telling you that something unrecoverable has happened and the integrity of the whole OS is in question. Think of a kernel panic like a BSOD on Windows.
I've never seen that specific one before, but a quick Google search indicates it may be a problem with I/O operations - like bad RAM or a bad SD card.
sassafras
Thanks for the response. I have included 4 RAMDUMP files. I find these 4 special because they all happened in quick succession. Four separate reboots all within 8 mins of each other without any interaction of the device myself. I never touched the device, I just sat there and staring at the device rebooting 4 times in 8 mins. On the final reboot the device never came back on. AT this point I picked up the device and had to hold the power button down for over 10 seconds for the device to come back on to an Asus splash screen. This was mins after I did a fresh factory reset via the OS options internally then a hard reset using the hardware buttons.
...It's a bug alright...
It doesn't seem to be caused by the same problem though, just that the watchdog program invokes a kernel panic and reboots. Weird. I'll backtrace it later and see what's up.
sassafras
went a whole day without a reboot. I did have an odd lock up/freeze at the lock screen where i couldnt unlock the device or get it to rotate the screen. It was locked up tight. Held hte power button down for 20 secs before it shut down. Rebooted, no new RAMdump created. No issues since.
sassafras_, Did you have any luck reading those ramdumps?
I did - sort of.
They're all related to the watchdog program assuming it's soft locked up. Which it may very well have been, but since you weren't using the device at the time, it's hard to know for sure.
The function's that were called immediately prior to the fault were different, which to me indicates that it's just buggy software. Honestly, without doing a backtrace I wouldn't know, but I can't without a system.map from around the time of the lockup. I'm going to assume it's just buggy code from 3.1 and wait and see if the 3.2 release lowers the rate of these. If not, then maybe I'll do some more digging.
sassafras
sassafras_ said:
I did - sort of.
They're all related to the watchdog program assuming it's soft locked up. Which it may very well have been, but since you weren't using the device at the time, it's hard to know for sure.
The function's that were called immediately prior to the fault were different, which to me indicates that it's just buggy software. Honestly, without doing a backtrace I wouldn't know, but I can't without a system.map from around the time of the lockup. I'm going to assume it's just buggy code from 3.1 and wait and see if the 3.2 release lowers the rate of these. If not, then maybe I'll do some more digging.
sassafras
Click to expand...
Click to collapse
Is there any progress on this issue? I bougth a brand new tf and during day random reboots maybe 50 times. And that romdumps are appeared on my internal storage. I dont have external sd by the way. Im stuck.
Hi.
Im having a same problem with my Transformer. Its a week old B60 and its reboots probably 50 times a day and give me log files.
Also im using Honeycomb 3.2
I really want to find out what is going on
i guess its a hardware issue or something.
i'm going to give back my TF today and take back a new one.
if i get same errors, i'll let you know.
I posted a workaround that helps immensely for rooted tablets somewhere around here. I can't find it tonight, but it's in one of the other 'random reboot' threads.
sassafras
sassafras_ -
Did you ever find anything with this issue? I am on my second TF and it is exhibiting the same random reboot while sleeping issue as the first. I know you have a post on another thread indicating how to tell the kernel to ignore "oops" conditions - have you received any feedback on how that is working? I assume this requires root access, I haven't yet rooted my device.
I have collected a few ramdump log files, but as of now only one out of 6 shows a kernel panic. I am new to Android, and I am trying to make sense of the dump logs. It appears that these dumps are maintained in a ring buffer, so the last entries are usually somewhere in the middle, is that correct? All of them also have some garbage at the end, but I assume that is just another effect of the ring buffer strategy.
Like I said, I am new to Android, but I am a long time embedded and real-time programmer, and pretty handy in Linux. It seems to me that the log files aren't providing enough information, but I'm not sure how to debug kernel/system crashes in Android. If anyone could point me in the right direction of where I should look next to get more information on these crashes, perhaps we could get to the bottom of this problem.
From what I can tell via the logs, when the TF is sleeping, it wakes up from time to time for various reasons, then suspends when it is done. It looks like it is during this wake/suspend cycle that something occasionally goes wrong and causes the tablet to reboot.
I am hoping that this is a software/firmware issue (or a hardware issue that can be worked-around with software), because I really like the TF platform and this issue makes keeping apps like IM or email running while it the device sleeps kinda iffy.
Any help from the awesome experts here at XDA would be greatly appreciated, and I look forward to learning more of the gory details and inner workings of Android.
I have had the same issues. Configuring the kernel to ignore oops only helped a bit. The tf would still freeze in standby eventually (once a day or so). My supplier (i.e. not Asus) replaced it and my new tf (a SBK v2 one, unfortunately) has not rebooted once in 2+ weeks. So my guess is that it was a hardware issue (memory, something not coming out of backup mode properly, ...?). Not sure if one could work-around it in software.
Now, this was probably not very helpful but I thought I'd share my experience here. And possibly my tf suffered from an entirely different defect, although the symptoms were the same (ramdump logs from random reboots in standby, independent from wifi on/off, sync on/off, and lots of other settings I tried).
flipflipflip -
Thanks for your reply! I was hoping that it wasn't a hardware issue, and since I got two in a row with the identical problem I was thinking that maybe a software fix could get around it. After reading about your experience, I went ahead and returned it and ordered another one from a different source. Hopefully the third time's a charm!
I'm keeping my fingers crossed that this one is not an SBK v2, but I'll be happy just to have one without sleep-apnea!
This did give me a chance to load up ADB and poke around a bit under the hood of the last one, so if nothing else it is a learning experience. Hopefully I will have something to contribute to the community once I get my hands on a working device.
I know it's been a while (had a big work-related headache), but just wanted to post and let people know that I finally received a TF101 (B50!!) that seems to be working just fine - so I guess it was just a combination of bad luck and a hardware issue after all.
The only issue I have now is that sometimes when it is sleeping, it loses its internet connection (it still seems to be connected to the AP) - but I think I can work around that.
Cheers!
Hi folks, I know what i'm doing, so I flashed the images and it all worked...BUT some major things are missing. I cant drop down the notification drawer (nor do I get any notifications) Also, nothing Google syncs. I tried manually syncing/logging out and logging back in and nothing seems to work, so 1) Suggestions? 2) Is there a dedicated forum for this? I cant seem to find anything online. I also tried flashing it again and to no avail.
Help me XDA, you're my only hope to not going mad on my phone.
JustinMorinC said:
Hi folks, I know what i'm doing, so I flashed the images and it all worked...BUT some major things are missing. I cant drop down the notification drawer (nor do I get any notifications) Also, nothing Google syncs. I tried manually syncing/logging out and logging back in and nothing seems to work, so 1) Suggestions? 2) Is there a dedicated forum for this? I cant seem to find anything online. I also tried flashing it again and to no avail.
Help me XDA, you're my only hope to not going mad on my phone.
Click to expand...
Click to collapse
Try downloading the image again and use the back ports, the ones directly connected to the motherboard. If you can't fix it and/or find an answer anywhere, remember that android M is beta; report it to the android developers and wait.
Just some personal history on this kind of occurrence (tl;dr some times the same hardware can behave differently on the same conditions):
My brother and I had once the same phone, the LG Optimus 2X. We bought the same phone, at the same store, on the same day, a promotion; quite the upgrade from my motorola milestone (droid). His would always have problems with custom roms that mine never did, some times was the other way around, but the developers fixed over time given the pertinent logs. It also happened Installing mac on my assembled pc, I got to have problems other people with the exact same hardware configuration never did and I didn't had problems that other people had.
mikeszf said:
Try downloading the image again and use the back ports, the ones directly connected to the motherboard. If you can't fix it and/or find an answer anywhere, remember that android M is beta; report it to the android developers and wait.
Just some personal history on this kind of occurrence (tl;dr some times the same hardware can behave differently on the same conditions):
My brother and I had once the same phone, the LG Optimus 2X. We bought the same phone, at the same store, on the same day, a promotion; quite the upgrade from my motorola milestone (droid). His would always have problems with custom roms that mine never did, some times was the other way around, but the developers fixed over time given the pertinent logs. It also happened Installing mac on my assembled pc, I got to have problems other people with the exact same hardware configuration never did and I didn't had problems that other people had.
Click to expand...
Click to collapse
Thats a great idea! I'm using a laptop so I will change ports. Does it make a difference when it says that ...exceeded maximum size... or what ever it said, id that normal? Update should be out this week I think as well!
I received an OTA Update in early to mid May. I am now forgetting which version I received at that time. ( I forget as I have done so many downgrades/upgrades/factory resets in my troubleshooting the last month!) Up until these issues, I've never rooted or flashed a ROM, or unlocked boot loader or anything. My N5 had always been completely stock.
First Issue
It all started with just the sim card. I get "no sim card" message, even though it was in there. This was my original SIM card and I had never ejected it since I bought it new. I found I could turn it off, pop it out and back in, and boot it again. Sometimes it will see the sim card again. It may take 20 times, but finally work.
I naturally got a new sim card, as well as confirmed said sim cards worked in other phones. My wifi and bluetooth were working fine at first. Working with google support, they recommended a factory reset to fix the sim card issue. Immediately after the factory reset, my bluetooth would no longer turn on nor show a MAC address. At this point, my wifi was fine.
Second Issue
In addition to the sim card slot issue, now my Bluetooth no longer works! Around this time, I received another OTA update, this time it was 5.1.1 LMY48B. I had hoped it would fix the issues, but no dice! I start reading up on the XDA forums as I am determined to start rolling back to see if this will fix anything. I unlocked the boot loaded, rooted, etc following the threads on XDA
Third Issue
I do all sorts of flashing to hammerhead-krt16m_4.4 to hammerhead-ktu84p_4.4.4 to hammerhead-lrx21o_5.0 to hammerhead-lmy48b_5.1.1 . On the final flash back to 5.1.1 my wifi now no longer works!!!!!!!!!!! It is stuck at wifi turning on and no MAC address shows. It also seems my cell data is very very slow now!
After many calls to google, I think I finally succeeded in getting a “ticket routed up”. My phone is from the play store around 10/31/2013. They keep pushing I am out of warranty. I attempt to ask for a refurb N5 without luck so far. I am not very confident anything will come from google. This being my only handset now, it is just not an option to send this to LG. My current state is my voice/txt and cell data are working. Data seems a little slow but usable. Wifi and bluetooth won't turn on. I also still have the sim car slot issue upon rebooting. After a bunch of reboots it will eventually see sim card.
What else can I try? Is there a better way to attempt to repair/reload my radio drivers? Perhaps there is corruption of sorts? I have not tried a custom ROM or radio or kernel…… I did take to a local tech. They looked at everything literally under a microscope and did not see any issues that way. I am in the USA and have a lgd820. Although we are quick to assume a hardware issue, I am wondering if there is some sort of incompatibility with the first run of N5 and lollipop….. who knows!
I’ve read all sorts of threads on the internet. It seems I am not the only one. We are very quick to assume it must be a bad motherboard, it just seems too coincidental to me!
Here is a collection of threads……
Within the N5 Sub
http://www.reddit.com/r/Nexus5/comments/2g0i3m/no_wifi_or_bluetooth/
http://www.reddit.com/r/Nexus5/comments/253y8d/my_nexus_wont_activate_wifi_and_bluetooth/
http://www.reddit.com/r/Nexus5/comments/2pur0v/wifi_stuck_on_turning_on_mac_and_ip_addresses/
http://www.reddit.com/r/Nexus5/comments/361ecw/help_wifi_and_bluetooth_stopped_working/
http://www.reddit.com/r/Nexus5/comments/2h4co7/wifi_wont_turn_on/
http://www.reddit.com/r/Nexus5/comments/2hpj2w/can_no_longer_connect_to_wifi_stuck_at_wifi/
http://www.reddit.com/r/Nexus5/comments/2wjk38/wifibluetooth_issues/
http://www.reddit.com/r/Nexus5/comments/2zboet/no_wifi_no_bluetooth_and_reboots_whenever_i_press/
Other Links
http://forum.xda-developers.com/google-nexus-5/help/wifi-stuck-t2721643
http://forum.xda-developers.com/google-nexus-5/help/bluetooth-t2733672
https://productforums.google.com/forum/#!topic/nexus/IJSOuc7gw0w;context-place=forum/nexus
https://productforums.google.com/fo...otification#!category-topic/nexus/1H6ZiIMYrtw
https://productforums.google.com/forum/#!topic/nexus/ke-OEPLbRSQ
https://productforums.google.com/fo...xus/lollipop|sort:relevance/nexus/NbO-AGvRCLk
http://code.google.com/p/android/issues/detail?id=80028
I found this, but not really sure it’s the same thing….. http://forum.xda-developers.com/showpost.php?p=52441901&postcount=47
Prodeje79 said:
I found this, but not really sure it’s the same thing….. http://forum.xda-developers.com/showpost.php?p=52441901&postcount=47
Click to expand...
Click to collapse
Hi,
This link was actually what i was going to suggest. It seems you've tried pretty much everything in the book except that.
I think its worth a try. Same as any other learning process, take your time and read the whole thing once or twice until you feel comfortable with the process. Then go for it.
Darn it, I should have downloaded those programs BEFORE rooting my phone again. Now I a struggloing to get my SIM card detected again to get data to DL them! whooops!
How would I go about attempting to read my files first to see if they are accessible and potentially write down my old MACs first?
EDIT: I found this but not sure how to get that working? I have Windows 7 and CMD prompt at this point. what program is that using?
https://www.reddit.com/r/Nexus5/comments/2j6vao/how_to_changefix_your_wifi_mac_address/
beekay201 said:
Hi,
This link was actually what i was going to suggest. It seems you've tried pretty much everything in the book except that.
I think its worth a try. Same as any other learning process, take your time and read the whole thing once or twice until you feel comfortable with the process. Then go for it.
Click to expand...
Click to collapse
OK, I went through those steps. everything appeared to go through correctly. Still no wifi nor bluetooth
EDIT: I rebooted a second time. WHen it first boot up, wifi was on and connected to my works AP. I quickly went in and snagged a screen shot of MAC address. Oddly enough, it did not match what I had input via hex editor. Within a few moments the wifi stopped working. It is back to the turning wifi on issue..... bluetooth still not working as well.
Very interesting.....
EDIT2: I get access denied when attempting to read either files within their corresponding folders under persist.
I was able to copy my stock files into my sdcard download folder and read them there without issue. Thus seeing my default addresses for both!
Perhaps it is normal, but I am never able to edit the old or new files under persist. I basically renamed original folders to bluetoothold and wifiold. I could delete them perhaps.
Note that I put my phone into airplane mode before doing anything noted in the steps.
Any other ideas? Given that it is showing my original MAC address the one time it worked, this makes me think that it is not reading the files .macaddr at all
I have the same problem. Funny thing is, the phone is just over 2 years old and the motherboard was replaced just 9 months ago (so, brand new one).
In my case, I received and Android update 2 days before I found the phone burning hot and restarting on it's own. Then the same chain of events you describe started to unleash. Now I can't be sure if this is software related, hardware related or both.
Can't seem to find a solution to the issue either.
Prodeje79 said:
I received an OTA Update in early to mid May. I am now forgetting which version I received at that time. ( I forget as I have done so many downgrades/upgrades/factory resets in my troubleshooting the last month!) Up until these issues, I've never rooted or flashed a ROM, or unlocked boot loader or anything. My N5 had always been completely stock.
First Issue
It all started with just the sim card. I get "no sim card" message, even though it was in there. This was my original SIM card and I had never ejected it since I bought it new. I found I could turn it off, pop it out and back in, and boot it again. Sometimes it will see the sim card again. It may take 20 times, but finally work.
I naturally got a new sim card, as well as confirmed said sim cards worked in other phones. My wifi and bluetooth were working fine at first. Working with google support, they recommended a factory reset to fix the sim card issue. Immediately after the factory reset, my bluetooth would no longer turn on nor show a MAC address. At this point, my wifi was fine.
Second Issue
In addition to the sim card slot issue, now my Bluetooth no longer works! Around this time, I received another OTA update, this time it was 5.1.1 LMY48B. I had hoped it would fix the issues, but no dice! I start reading up on the XDA forums as I am determined to start rolling back to see if this will fix anything. I unlocked the boot loaded, rooted, etc following the threads on XDA
Third Issue
I do all sorts of flashing to hammerhead-krt16m_4.4 to hammerhead-ktu84p_4.4.4 to hammerhead-lrx21o_5.0 to hammerhead-lmy48b_5.1.1 . On the final flash back to 5.1.1 my wifi now no longer works!!!!!!!!!!! It is stuck at wifi turning on and no MAC address shows. It also seems my cell data is very very slow now!
After many calls to google, I think I finally succeeded in getting a “ticket routed up”. My phone is from the play store around 10/31/2013. They keep pushing I am out of warranty. I attempt to ask for a refurb N5 without luck so far. I am not very confident anything will come from google. This being my only handset now, it is just not an option to send this to LG. My current state is my voice/txt and cell data are working. Data seems a little slow but usable. Wifi and bluetooth won't turn on. I also still have the sim car slot issue upon rebooting. After a bunch of reboots it will eventually see sim card.
What else can I try? Is there a better way to attempt to repair/reload my radio drivers? Perhaps there is corruption of sorts? I have not tried a custom ROM or radio or kernel…… I did take to a local tech. They looked at everything literally under a microscope and did not see any issues that way. I am in the USA and have a lgd820. Although we are quick to assume a hardware issue, I am wondering if there is some sort of incompatibility with the first run of N5 and lollipop….. who knows!
I’ve read all sorts of threads on the internet. It seems I am not the only one. We are very quick to assume it must be a bad motherboard, it just seems too coincidental to me!
Here is a collection of threads……
Within the N5 Sub
http://www.reddit.com/r/Nexus5/comments/2g0i3m/no_wifi_or_bluetooth/
http://www.reddit.com/r/Nexus5/comments/253y8d/my_nexus_wont_activate_wifi_and_bluetooth/
http://www.reddit.com/r/Nexus5/comments/2pur0v/wifi_stuck_on_turning_on_mac_and_ip_addresses/
http://www.reddit.com/r/Nexus5/comments/361ecw/help_wifi_and_bluetooth_stopped_working/
http://www.reddit.com/r/Nexus5/comments/2h4co7/wifi_wont_turn_on/
http://www.reddit.com/r/Nexus5/comments/2hpj2w/can_no_longer_connect_to_wifi_stuck_at_wifi/
http://www.reddit.com/r/Nexus5/comments/2wjk38/wifibluetooth_issues/
http://www.reddit.com/r/Nexus5/comments/2zboet/no_wifi_no_bluetooth_and_reboots_whenever_i_press/
Other Links
http://forum.xda-developers.com/google-nexus-5/help/wifi-stuck-t2721643
http://forum.xda-developers.com/google-nexus-5/help/bluetooth-t2733672
https://productforums.google.com/forum/#!topic/nexus/IJSOuc7gw0w;context-place=forum/nexus
https://productforums.google.com/fo...otification#!category-topic/nexus/1H6ZiIMYrtw
https://productforums.google.com/forum/#!topic/nexus/ke-OEPLbRSQ
https://productforums.google.com/fo...xus/lollipop|sort:relevance/nexus/NbO-AGvRCLk
http://code.google.com/p/android/issues/detail?id=80028
I found this, but not really sure it’s the same thing….. http://forum.xda-developers.com/showpost.php?p=52441901&postcount=47
Click to expand...
Click to collapse
+1
I'm facing the same issues and I tried all the possible steps I could find on internet trying to repair the problem.
Actually, since the latest updates I was encountering some issues with the WiFi only: not turning on either off and not showing properly the MAC addres. So I decided to factory reset, even SDcard and since yesterday I have tried all the possibile guide I found to internet to fix the MAC address not showing and the WiFi not turning on/off but nothing worked. I tried even to flash again the old factory images, such as KitKat, Lollipop, etc., to lock the bootloader again and to dismantle the phone in order to clean the motherboard, but nothing worked. Phone still gives me MAC address 02:00:00:00:00:00 alternatively with the correct one, I can't figure out on what it depends because sometime it seems to work: it shows the correct MAC, it connects to wifi network; suddenly it doesn't!
I'm really going crazy to understand what's wrong.
You'll have to dig up my final posts on this , but in a nutshell, send into LG for repair, select cheapest option they offer. Receive mint phone. My cost was $45 and about one month... I picked up a cheap $20 phone to get me by.
In other news.... I now have a 6p!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
Renton91 said:
+1
I'm facing the same issues and I tried all the possible steps I could find on internet trying to repair the problem.
Actually, since the latest updates I was encountering some issues with the WiFi only: not turning on either off and not showing properly the MAC addres. So I decided to factory reset, even SDcard and since yesterday I have tried all the possibile guide I found to internet to fix the MAC address not showing and the WiFi not turning on/off but nothing worked. I tried even to flash again the old factory images, such as KitKat, Lollipop, etc., to lock the bootloader again and to dismantle the phone in order to clean the motherboard, but nothing worked. Phone still gives me MAC address 02:00:00:00:00:00 alternatively with the correct one, I can't figure out on what it depends because sometime it seems to work: it shows the correct MAC, it connects to wifi network; suddenly it doesn't!
I'm really going crazy to understand what's wrong.
Click to expand...
Click to collapse