Database Develop

My second N6, the same problem

I bought the Nexus 6 (blue, 64gb) the day one, in November and since that day I noticed random reboots in a particular situation. When I switch to a WiFi network to another it shuts down and so I have to turn it on. When it turns on I have lost all my WiFi networks configurations, so passwords, dhcp settings, etc.
Random reboots rarely happen also in camera/gallery apps.
I tried to send it back to google and I received a new nexus. The first one was produced in June 2014, the new one in December 2014. The issue is still there. [emoji17] I've also tried to update to 5.1 but no resolution.
I have rooted, installed twrp, decrypted both my nexus 6 with toolkit.
How can I solve the problem? I was very happy with this phone.

Try using it completely stock and see what happens. I'd say chances are that if you set both up the same, it's something you're doing and not the hardware on 2 different phones.

But other people have made the same basic mods on their nexus and their phone has not this kind of issue.

Is it every network? Maybe try a stable custom ROM to see if it happens there too. Could be a problem with specific networks or even apps. Troubleshooting is the key. First try full wipe, no restored Apps.

I could be as simple as an app the developer has not updated since gingerbread or something stupid like that.

Is there a way to find the malicious app?

There definitely *was* a bug causing loss of wifi networks, and I think there may also have been a reboot involved there (not sure if we rebooted it manually, or if it just did it on its own as a response to a wpa_supplicant crash...). It was across the board for Android 5.0 though, not limited to Nexus 6. I saw my wife's Nexus 5 do it once. Never actually had it happen on my 6.
I'm not sure if this bug was fixed or not, since it wasn't something we tried to reproduce, and only happened once. The bug is definitely related to wpa_supplicant, since that is the only program that actually interacts with its configuration file (which is where the wifi configurations are actually stored).
As far as galleries go, you're not giving much to guess by. I certainly haven't seen galleries cause reboots like that. Maybe you are using a bad one?
Try this gallery; https://github.com/lbdroid/Android-Binaries/blob/master/Gallery2.apk
That is the actual AOSP gallery, modified to install as a standalone application. The source code is in another repository on my github.
*note: it will not do you any good at all to swap out your phone, since there is no indication that you are experiencing a hardware issue.

But why other people doesn't experience this problem that is related to WiFi? All people use WiFi and every time. Is there a way to fix the WPA_supplicant issue? Maybe a custom ROM?
My first n6 had also an hw issue, I think, because before it rebooted it gave me some little "buzz" from the top speaker.

mouse100 said:
But why other people doesn't experience this problem that is related to WiFi? All people use WiFi and every time. Is there a way to fix the WPA_supplicant issue? Maybe a custom ROM?
My first n6 had also an hw issue, I think, because before it rebooted it gave me some little "buzz" from the top speaker.
Click to expand...
Click to collapse
all people use WiFi is an incorrect statement. you can say most ppl use wifi, but all would never happen. I hate using WiFi and NEVER use it except when its absolutely necessary. ive probably used WiFi 2 times on my n6 since getting my n6 in November, and there's no WiFi issues here.

mouse100 said:
Is there a way to find the malicious app?
Click to expand...
Click to collapse
Yes, start with stock and install a few apps at a time until you get the problem. Given the fact that you have 2 different phones experiencing the same problem, it is much more likely that it is something software related rather than hardware (though I suppose it could be possible if you're really unlucky ).

mouse100 said:
But why other people doesn't experience this problem that is related to WiFi? All people use WiFi and every time. Is there a way to fix the WPA_supplicant issue? Maybe a custom ROM?
Click to expand...
Click to collapse
You said that it happens when you change from one wifi network to another. Most people don't do that. Most people have one wifi network at a time and don't change it.
There is also a huge difference between wifi network configurations... A/B/N/AC, frequency, bandwidth, multiple-bands, encryptions, etc.
My first n6 had also an hw issue, I think, because before it rebooted it gave me some little "buzz" from the top speaker.
Click to expand...
Click to collapse
Normal.

"Unfortunately WiFi has stopped working" (Plentiful details included)

So I have the T-Mobile variant of the LG G4. I had it unlocked straight from the carrier a while ago and all seemed well. Recently I noticed a huge amount of battery drain and 4G LTE usage from T-Mobile's pre-installed apps--mainly com.tmobile.pr or something which is the "My Account" app (imagine being at 60% left with 27% of the drain having been an app and only 9% the screen. Yeah, it was that bad)
This I obviously found unacceptable, so I went ahead to try and uninstall the bloatware. Lo, much to my dismay, Tmobile has locked it down so you can't uninstall the bloatware, and you can only disable it. This alone irked me enough that I wasn't satisfied with just a disabling. I knew I wouldn't rest until I had obliterated it.
I've had plenty of android phones over the years and done my fair share of rooting and flashing ROMs and the like, but I hadn't touched that aspect of my G4 because I wanted a dependable device for school and I didn't want to mess around with it. I knew I'd have to root it to get rid of the tmobile bloatware so I went and did that using the Low effort root method (http://forum.xda-developers.com/g4/orig-development/root-tmo-vzw-intl-variants-soon-root-lg-t3164765). When this was done a lot of my background processes started to continuously crash. I decided to go ahead and put TWRP as the custom recovery and just go ahead and get some dependable 6.0 ROM, and I found a couple of them.
When I flashed the first ROM, the play store services were crashing so I found the google apps package for marshmallow and flashed that too. It seemed to fix the issue. Yet when I would click on my School's WiFi at the setup (which is WPA2 Enterprise) it would crash and say "Unfortunately WiFi has stopped working." I thought that perhaps I mucked something up in the flashing of the ROM, or that maybe there was an issue with the ROM in general, so I decided to just flash another ROM entirely (after factory resetting it all the way). Along the same time as this I found a slightly more modified and feature packed version of marshmallow by this lad here (http://forum.xda-developers.com/g4/development/h815-genisys-rom-1-0-classic-v10g-t3192649). I decided to go ahead and use this one since it had a h811 version there, that involved flashing a h815 and then flashing a patch.
The "Unfortunately WiFi stopped working" issue persisted, however. I found this odd. I then noticed that if I click any other network that ISN'T the WPA2 enterprise network my school is working that everything seems to work fine.
I went ahead and factory reset it all the way again in the hopes that would fix it. No luck.
I booted it to safe mode and tried to connect to the WiFi network from there. No luck.
I downloaded a third party WiFi app off cellular and tried to connect from there. No luck.
I can't enter the WiFi's name and try to enter directly because it crashes there too.
I can't "Forget" the network as it's never joined that network before so there's nothing to forget. It does let me enter the advanced options but a direct press causes it to crash.
So throughout ROMs and wipes and safe modes and all, this one issue has persisted, where my phone's WiFi will crash when it tries to connect to my school's WPA2 Enterprise network. I've tried plentiful fixes short of flashing back to a 5.0/5.11 stock (which I'm hesitant to do because I read something about phones bricking after they downgrade from Marshmallow using the .kdz files or something?).
I'd really appreciate any help that y'all can provide. I've read these forums for ages but this will be my first time making an account because I can't find anybody else with the same issue and its proving to be quite a pain.
tl;dr wifi isn't working with only one particular network and no fix I've tried under this sun has worked so far. help will be appreciated pls

Have you tried flashing this rom here --> http://forum.xda-developers.com/tmobile-g4/development/rom-g4-h811-xtreme-rom-v1-0-7-28-15-t3167667
I am using this one here and I have no issues using wifi. I cannot speak for the 6.0 roms because LG has not dropped the sources for the Tmo variant yet.

esjames said:
Have you tried flashing this rom here --> http://forum.xda-developers.com/tmobile-g4/development/rom-g4-h811-xtreme-rom-v1-0-7-28-15-t3167667
I am using this one here and I have no issues using wifi. I cannot speak for the 6.0 roms because LG has not dropped the sources for the Tmo variant yet.
Click to expand...
Click to collapse
I got the brown leather variant from Tmobile and it only says H811 as far as I can tell. Not sure of if its the "n" version or not.
I have not tried that rom but ill be sure to give it a go, hoping it will help solve the issue. I did some additional testing and can confirm the issue lies with all WiFi networks that employ WPA2 Enterprise security.
Will there be any issue with the Rom when downgrading from Android 6.0? I was reading about phone's bricking when trying to downgrade certain versions or bootloaders on the tmobile variants.

I'm pretty sure going back to stock 5.1 will be fine. The Tmo variant hasnt been upgraded to 6.0 yet and the ports don't update the bootstacks. Read here --> http://forum.xda-developers.com/tmobile-g4/development/global-marshmallow-6-0-port-to-h811-t3232760

Update: It seems that any Android 6.0 flash cuts off the ability to connect to Enterprise wireless networks. I went ahead and flashed to the debloated stock rom on the thread you mentioned, but it cut off the ability to record video. As such, I went for the xTreme version that you mentioned, and flashed the camera restores and all.
Everything works fine now as far as I can tell. I also got rid of the Tmobile applications draining the battery and all that. All should be well. Thanks again for the help

Bluetooth is driving me nuts! Need help please.....

Hello everyone,
I'm having major issues with my Nexus 6 over the past 3 weeks or so.
I've had this phone for almost 2 full years now and love it, however, over the past 3 weeks the bluetooth function keeps turning off when I reboot my phone every night.
It NEVER did this in the past 2 years. Only the last 3 weeks. It seems to be some sort of battery saving feature, I would presume.
What drives me nuts, is I always like to have my bluetooth on, since I get in my truck and it auto connects to my GMC IntelliLink (which is also a problem).
So does anyone know why, all of a sudden, after reboot, bluetooth defaults to off and I have to manually turn it on every time? My Nexus 6 has been flawless up until now.
I've looked everywhere for an "auto start" option for bluetooth, but cannot find one. I have ZERO idea how this happened all of a sudden. I've been running the same ROM since last February with no problems (ROM screenshot attached).
As for my bluetooth truck problem, that started today. All of a sudden "phone audio" will not let me select the box, only "Media Audio" and "Contact Sharing" boxes are selected. Thus my Pandora plays over bluetooth, but my phone calls will not.
Also my Bose Quiet Comfort headphones used to connect perfectly with my Nexus 6, now I'm at work and I notice if I turn the headphones off, then come back and turn on, it'll say "connected to Nexus 6", but the sound is playing through the phone instead of the headphones, even though the bluetooth connection has been established.
Again, this is only over the last few weeks.
Any help would be greatly appreciated.
I'm willing to update to a new ROM or do a wipe, I just tend to live by the motto "if it ain't broke, don't fix it"........ except now it is broke and I want to fix it.
Thank you-

Paste a logcat here. A dev could take a look and help you out.
or
Backup your stuff and do a clean install of a new pure nexus or whatever rom, if it's still present after that, maybe it's just your battery starts to dying after 2 years.
Edit: I'm using crdroid as daily driver and have no bt issues

So glad you posted this, I'm having the same issue! After either a restart or just a period of time my Bluetooth turns to disabled. It is especially frustrating as I have it connected to my watch, which allows me to unlock with smart unlock. When the Bluetooth is disabled, I have to punch my pin in.
I am on stock 7.1.1, February update. I am rooted and flashed the Echo Permissions Fix. I was going to flash stock again this morning, but decided to check here first for a solution. I am just happy to know that it's not just me.
That being said, like @MVLJR, I recently flashed PureNexus ROM and that for me is when this began. I flashed back to stock via flashall, but it has not stopped the problem. Could it be a PureNexus thing?

As we have PureNexus somewhat in common, I am doing some searching on that page. I had previously posted there about it, but I don't think I ever got a response. Someone mentions it on Page 3417, I'll keep reading to see if I find a solution.
My post, by the way, is on page 3420.

I had a problem like this on Pure Nexus and flashed back to stock (N6F26R) to see if the problem goes away...
Previously on stock (release before N6F26R) and never had an issue. I use Bluetooth with a watch, fitness band and sometimes my Wife's Ford...
Sent from my Nexus 6 using Tapatalk

@muiriddin, did the problem go away for you? Because I flashed back to stock and the problem persists.

@MVLJR, I suspect that the problem is Android Wear 2.0 on our phones. Do you have a smart watch?
Edit: On the PureNexus forum, people without Android Wear are also experiencing it. So back to the drawing board. I still do not think it is your ROM.

Reading this thread reminded me of something I dealt with a while back, I don't know if this will do it for all of you, but I figured I'd post this. I screenshotted a reddit thread that fixed the problem for me. I can't remember if what I experienced was the same as all of you, and I am not having the problem now. But I hope this helps. Please see the attached screenshot.

I don't have an android watch, but I do have a fitbit and don't have any problems with it.
A little update, I cleared my Bluetooth cache and changed the name of my device, which seems to have helped.
My Bose headphones now autoconnect like before.
However, my Bluetooth still shuts off after reboot. My GMC Intellilink still won't let me select "Phone Audio" either.
I think I'm going to flash a new ROM this week, which sucks because I've grown attached to the Pure Nexus ROM.
Can someone show me how to post a logcat?
Thanks

This (and similar) bluetooth issues have been reported on the nougat product pages. It's not unique to PureNexus or the Nexus 6.
Reports are that 7.1.2 (beta) fixes the issue on devices that have access to it. Hopefully a fix comes down the pipe for the Nexus 6 as well, as I have some of the same issues.
Similar posts can be found on the nexus6 and googlepixel subreddit pages.

My question is, what prompted this?
I've had the same ROM for a year, no OTA updates. Had to be an app update, correct?
No other way to explain how it worked for a year, now problems all over the place

You've been using the same ROM, but updating the version of the ROM, correct?
And the ROM updates are based on updates made to Android by Google.
So if a bug makes it into Nougat, it will (generally) make it into the modified ROM as well.

Incorrect, I've been on the same version of Pure Nexus since last February, screen shot in original post

I take it the fix I posted didn't help? I was really hopeful that it was the same issue and that would fix it up.

I haven't tried it yet, at work right now, I'll give it a shot later.
I'll update my findings.
Thanks

Will keep my fingers crossed. One thing to note, when doing that fix, it *will* wipe your bluetooth auto-pair devices. So don't fret if nothing automatically connects afterwards. You have to repair everything.

It is not a new problem, there are many threads in the Q&A forum if you search. Here is one:
https://forum.xda-developers.com/nexus-6/help/bluetooth-off-reason-pattern-t3435436
(there are more links and suggested workarounds in that thread from me)
That said, installing the AW 2.0 DP 4 totally solved my BT disconnects from my Huawei watch and LG stereo headset.
The changelog on the latest Huawei AW 1.5 mentions BT issues, but I have not tried it.
AW 2.0 official is supposed to start rolling out OTA tomorrow, so we shall see. (finners crossed tite )
I'm on Jan 21 PN 7.1.1, latest AW app. I have no suggestions of those having issues with no Android Wear, but there are threads here with suggested workarounds that solved this for many of us before, you might want to check them.

@Morpherios and @MVLJR
I don't know if it's of any note, but one of the actions I attempted in trying to fix mine was to reset all network settings via the "More" option in Wireless & Networks settings (I backed up wifi settings in advance). That's essentially a nuking of all network settings, including wifi, cell, and bluetooth. It did not resolve my issue.
@Pkt_Lnt seems to be indicating that with updated AW on his watch, the disconnects are not happening. How the software on the watch (as opposed to the AW app on the phone) would be causing bluetooth to crash, I'm not sure. But it's not outside the realm of possibility.

larrysteeze said:
@Pkt_Lnt seems to be indicating that with updated AW on his watch, the disconnects are not happening.
Click to expand...
Click to collapse
My words were / are different than that:
AW 2.0 DP 4 totally solved my BT disconnects
That means they do NOT happen any more, since Dec 11, 2016 when I installed AW OS 2.0 DP4 was released and I installed it on my watch. Not. One. Disconnect. None. Nada. Zero. Zip. Zilch. Nein.. :victory:
BT devices communicate both directions. The watch CAN control the phone, and was turning off BT. It was obvious when it happened, when my headphones prompt "Out of Range, trying to connect" (I came to hate hate that voice prompt )
I would immediately open the AW app on the phone at disconnect and was prompted to turn on BT because it was off.

@Pkt_Lnt I completely agree that it BT communication is two-way...I stated that it's not outside the realm of possibility because there are a number of factors that could do it, including the phone receiving a message it simply doesn't know what to do with and causing a fault. This could explain my bluetooth share crash messages that I received on occasion.
It's encouraging to know that it's fixed with AW 2.0 for you. I hope it carries through to me when I get the update. If the OTA doesn't drop tomorrow, I may have to flash the DP as well.

AA Shutting down after screen unlock

Hi all guys, I've been missing a long time from here, so please be care enough to forgive me if I posted the thread in the wrong place.
I'm currently using Android Auto and enjoying very much the amazing work made from Gabriele (AAAD, of which I payed the PRO version in order to help the developer's job).
I'm running AA version 6.3.611314 (downgraded from 6.4, because otherwise AAAD didn't work, since AA 6.4.... doesnt' let you show the apps installed apart from the official ones); Ford Focus Active with Sync 3 updated to 3.4 version, a Galaxy Note 20 Ultra5G (European) with Android 11.
Everything works fine, even AAAD installed programs.
The only problem is that every time I unlock the phone it disconnects from AA and then it starts again from the beginning. I opened the DEv Options in the phone settings and chose as standard setting for the usb - File transfer / Android Auto.
My question is: Why this disconnections happen and HOW can I fix it? I currently drive with the phone unlocked and, useless to say, it doesn't charge as much as it would if the screen had been off. I alredy tried with other cables, even with a Sam S9+ original one.
Thanks in advantage, any help is appreciated.

Same here, S10+ latest official, AA 6.4.611714-release, Ford Sync 3.x .
Doing so for about a week (or some more). At phone unlock, AA is crashing to Sync interface, and phone is asking for permissions in order to start Android Auto again (need to press Allow, otherwise AA will not start!)
Thx!

Same here , s10

It'd be nice to know whether the problem starts from the phone version , the AA version or from the car itself.

gidannifico said:
It'd be nice to know whether the problem starts from the phone version , the AA version or from the car itself.
Click to expand...
Click to collapse
I can confirm that the issue is related to the last Sammy update , I have downgraded to may update , now aa works perfect

Guys, Google just updated the discussion thread three days ago:
Thanks for all the reports. We informed the Samsung team and they have applied a fix on an upcoming upgrade as part of the regular July maintenance release to resolve this issue. Please keep checking for system updates on the device.
Click to expand...
Click to collapse

Question Wi-Fi stability issues

Even with the latest update as of May 2022, my new Tab A8 exhibits Wi-Fi stability issues not seen on the old Tab A7.
After leaving a connected tablet to sleep, Wi-Fi for some apps won't work and only a WiFi OFF + WiFi ON reset will restore connectivity.
Anyone else encountered this problem?

Same - it just won't stay on any network for long at all. It won't connect at all to my VirginMedia router saying 'couldn't get ip number'

Doesn't happen to me from what I've seen... Have Xfinity cable internet together with a Netgear router/modem.
Have you guys done all the system updates?

Yup, up to the latest from April. Tested on 2 devices and it's the same. Factory reset doesn't help.
I'm hoping that if not before, at least the Android 12 update will resolve this.

I just updated to Android 11 firmware update from last week - X200XXU1AVG1 - but the issue remains the same

On Build number RP1A.200720.012.X200XXU1AVC1, no updates I'm aware of. When this happens to me and I toggle wifi off and back on, no networks display. If I toggle airplane mode it they will appear again.
II'm in the USA, using an asus blue cave router.
What's everyone else using?
Anyone know what wifi chipset this tablet uses?

Got the update to Build number RP1A.200720.012.X200XXU1AVG1 it still occurs, and I'm also noticing bluetooth connection issues, both are cured by cycling airplane mode on and off.

Yeah... let's hope Android 12 includes fixes for this... really, the Tab A7 was a much better device with a nicer screen

KoMarCek said:
Yeah... let's hope Android 12 includes fixes for this... really, the Tab A7 was a much better device with a nicer screen
Click to expand...
Click to collapse
I reported the issue via Samsung members app with a bunch of screenshots,

SM-X205 is now getting Android 12 but nothing available yet for SM-X200. Will probably take a couple more days

OK now SM-X200 also got the first Android 12 update and the results are... BAD! Still the same issue and I'm quite done with Samsung for now. Unbelievable that they do not test the basic functionality well enough. I expected some WiFi driver updates under the hood but it seems they are oblivious to the fact Tab A8 has issues.

Had the issue one time since the 15th it's not solved but less frequent at least

What I notice now is that the wifi will turn off randomly. If turned back on it reconnects but shortly thereafter bluetooth dies and cycling airplane mode is required