Related
Hey everyone,
So I recently got my Nexus 6 from motorola and it's been great. Today though, I tried watching Netflix with headphones and was getting random pops or crackles in the background. It's only happening with Netflix, youtube and music plays fine.
So i was reading online that turning on developer options and disabling NuPlayer would help. So I did that, but it didn't change anything. So I went back to developer options and hit the off toggle at the top. This seemed to just shut everything in there off though, including nuplayer. Is there a way to just reset the developer options to default?
Most are off for me except oem unlock and debug.
Sent from my Nexus 6
A factory reset will put things the way they were out f the box, including turning off developer options.
+1 to what he said. If in doubt reset.
phoenixus said:
Hey everyone,
So I recently got my Nexus 6 from motorola and it's been great. Today though, I tried watching Netflix with headphones and was getting random pops or crackles in the background. It's only happening with Netflix, youtube and music plays fine.
So i was reading online that turning on developer options and disabling NuPlayer would help. So I did that, but it didn't change anything. So I went back to developer options and hit the off toggle at the top. This seemed to just shut everything in there off though, including nuplayer. Is there a way to just reset the developer options to default?
Click to expand...
Click to collapse
Settings > Apps > ALL > Settings and clear data should work.
Won't solve the random pops but will reset developer to default.
I thought all that switch did was rehide the options.
Sent from my Nexus 6
All you need to do is enable developer options and put the nuplayer back as it was, although its best top leave that off anyway.
phoenixus said:
Hey everyone,
So I recently got my Nexus 6 from motorola and it's been great. Today though, I tried watching Netflix with headphones and was getting random pops or crackles in the background. It's only happening with Netflix, youtube and music plays fine.
So i was reading online that turning on developer options and disabling NuPlayer would help. So I did that, but it didn't change anything. So I went back to developer options and hit the off toggle at the top. This seemed to just shut everything in there off though, including nuplayer. Is there a way to just reset the developer options to default?
Click to expand...
Click to collapse
There is no option to set it to default in normal way. You'll have to do that yourself. That's why it's "Developer Options"
It doesn't matter how many times I turn the wifi off on my nexus 6, it seems something keeps turning it back on. Im not sure how long it will take to turn back on, but I will look at my phone and notice that its back on again. It also doesn't matter what wireless AP I am by.
Is there a way to see what app, or whatever, is turning it on so that when I disable wifi, it's actually disabled until I change it otherwise?
I've been having something similar, coupled with my wifi disconnecting and reconnecting in a loop every thirty seconds. I'll notice my wifi looping like this, so I'll turn wifi off, only to have it turn back on by itself within ten seconds and start looping again. Really strange. This began about two days ago out of the blue. I haven't been able to pin it down to anything.
I'm running stock 6.0.1, Jan 2016 OTA.
therealcrazy8 said:
It doesn't matter how many times I turn the wifi off on my nexus 6, it seems something keeps turning it back on. Im not sure how long it will take to turn back on, but I will look at my phone and notice that its back on again. It also doesn't matter what wireless AP I am by.
Is there a way to see what app, or whatever, is turning it on so that when I disable wifi, it's actually disabled until I change it otherwise?
Click to expand...
Click to collapse
Just wanted to follow up so you could check if this applies in your situation.
I finally found the culprit! I decided to reboot into Safe Mode to disable all third party apps and see if it still happened. When in Safe Mode the wifi was rock solid! That told me it was some app causing my problems. So I uninstalled several apps to try to narrow it down, especially those that had been updated recently and rebooted normally. It still looped the wifi.
After banging my head against the wall, I decided to go to developer options, show running processes, and see what apps were running that could be messing with the wifi. The normal apps you would expect to be running were listed, plus the MyAccount app from StraightTalk.
Why the heck would that app be running a process? I opened the ST app and looked through it's options. Low and behold was a section called wifi management. Holy crap, this could be it! I look in that section, and it was set to manage my wifi and connect and disconnect when sufficient access points are nearby. I turned that off, closed that app, and verified in Running Processes that it was indeed gone. It was, and my wifi has been solid ever since.
Stupid, stupid app!
OH MY GOD. This has been driving me nuts. Thank you so much!
I've seen this problem all over the internet for quite a few years on many different models of phones and Android. I have it happening on both my 6P and Note 9, figured I'd post here since it's the newer device.
It's mainly happening with Greenify and App Volume Control Pro. I already did all the fixes I've found online, such as making sure the apps are not being optimized by battery optimization settings, and whitelisting them in any where else that might be causing them to be disabled. The only thing I've not done is lock the apps in the recent apps viewer from being closed when you tap close all because it shouldn't matter anyways, I don't leave them open (truthfully I rarely open the actual apps anyways). They don't need to be left open to do their things, that's what persistent notifications are for, to make sure they keep running in the background. Now that I notice though, Greenify does not have a persistent notification on the Note for some reason. I checked all settings, it's not blocked or hidden anywhere. IDK. And AVCP doesn't have one on either device, don't think it ever has for as long as I've been using it. Can only lock apps in the recent list on the Note anyways afaik. (But this issue isn't happening to anything else under accessibility access settings)
I don't use programs like CCleaner or anything, the only thing similar I have on the devices is Samsung's Device Maintenance app, but that obviously is only on the Note so I don't see how it's the cause since it's happening in the 6P as well.
Both phones are running Oreo 8.1. The only thing not stock is that I have elementalx and TWRP installed on the 6P, otherwise it's the stock ROM and whatnot, no root.
This problem happens what I will say is randomly, because it can happen after rebooting the phone or after waking it up. Whether that seems to be 10 minutes or 10 hours doesn't seem to matter. Checking my accessibility has just become habit. The way I first found this was happening was because AVCP makes a toast message when I open an app that I have it set to change the volume for, like a game. The messages were not popping up so I looked into things a bit more when it kept happening.
Anyone have any suggestions other than what's been said in the past?
Same Problem, my device : Vivo Nex S 8/128gb Android Oreo 8.1 no stock rom it has Funtouch OS and no solution for the Bug/Issue.
I don´t know what keeps accessibility resetting several times a day. very annoying!
The knowledge in your article is very useful, thank you
Hello, I have a pixel 4XL coming from a pixel 2 XL. After rooting I normally disable a bunch of system services and apps I don't need, one is always fused location. This was never an issue on my 2XL, and when I first got my 4XL a few months ago I disabled it with out issue. Then I guess an update happened because everything was working fine with it disabled and then one day I needed to enable it to (first time) connect a bluetooth item. So I enabled it, connected the bluetooth device and then disabled it again. On reboot it was boot looped, only making it to the lockscreen then immediately booting again. I didn't have back-ups so I wiped the device and tested it again and sure enough disabling just fused location put it into boot loop.
What I don't understand is that this never happened on my 2XL or my 4XL at the beginning. In digging into the issue online it appears that other devices have had the same issue going back a couple years but oddly pixels didn't seem effected (as far as I can attest) till recently. I'm guessing something calls for the devices exact location on boot and with the fused location disabled it bootloops.
My question is, does anyone have any idea of a work around for this? Is there a way to have it disabled and not boot loop? Or can whatever is calling it and causing the boot loop also be disabled?
teffyd said:
Hello, I have a pixel 4XL coming from a pixel 2 XL. After rooting I normally disable a bunch of system services and apps I don't need, one is always fused location. This was never an issue on my 2XL, and when I first got my 4XL a few months ago I disabled it with out issue. Then I guess an update happened because everything was working fine with it disabled and then one day I needed to enable it to (first time) connect a bluetooth item. So I enabled it, connected the bluetooth device and then disabled it again. On reboot it was boot looped, only making it to the lockscreen then immediately booting again. I didn't have back-ups so I wiped the device and tested it again and sure enough disabling just fused location put it into boot loop.
What I don't understand is that this never happened on my 2XL or my 4XL at the beginning. In digging into the issue online it appears that other devices have had the same issue going back a couple years but oddly pixels didn't seem effected (as far as I can attest) till recently. I'm guessing something calls for the devices exact location on boot and with the fused location disabled it bootloops.
My question is, does anyone have any idea of a work around for this? Is there a way to have it disabled and not boot loop? Or can whatever is calling it and causing the boot loop also be disabled?
Click to expand...
Click to collapse
Leave it alone is a work around
c_86 said:
Leave it alone is a work around
Click to expand...
Click to collapse
Why would you respond with this comment? It's useless. If he wants to tinker with his phone he has all the right to do so.
airmaxx23 said:
Why would you respond with this comment? It's useless. If he wants to tinker with his phone he has all the right to do so.
Click to expand...
Click to collapse
Thanks. Primarily disabling it improved battery life and I rarely ever actually need gps for any reason (except ridiculously, pairing a Bluetooth device one foot away - thanks android).
Second, the fact that fused to location is taking AND sending your exact coordinates 24/7 to Google and whoever else they share your data with or however else they want to exploit it - isn't something to celebrate especially with the huge cost of the device itself. I can't be the only one who feels gross buying expensive devices that just log everything I do so it can be sold to the highest bidder?
Don't use your primary phone to spoof Pokemon Go.
Sent from my Pixel 4 XL using XDA Labs
Hey All.
I have always used AOD as a night clock whilst its charging vertically.
But with this phone the AOD always goes off after about an hour.
Which sort of defeats the point of the feature really.
the setting is set to ALLDAY aswell.
is this a fault or is this how it is with phone.
stuatrb04 said:
Hey All.
I have always used AOD as a night clock whilst its charging vertically.
But with this phone the AOD always goes off after about an hour.
Which sort of defeats the point of the feature really.
the setting is set to ALLDAY aswell.
is this a fault or is this how it is with phone.
Click to expand...
Click to collapse
chinese version?
brunolongo said:
chinese version?
Click to expand...
Click to collapse
nah uk
Possibly power management of some type shutting it down?
I use to think always on AOD was a darling... now I only use tap on.
Lol, I sort of like how yours behaves; it waits for you to go to sleep.
blackhawk said:
Possibly power management of some type shutting it down?
I use to think always on AOD was a darling... now I only use tap on.
Lol, I sort of like how yours behaves; it waits for you to go to sleep.
Click to expand...
Click to collapse
pretty sure i have looked at most settings that could possibly effect this.
maybe its just the way it is.
it kinda bugs me at night when i wake up disorientated not knowing the time.
always something i have been used to with previous phones.
stuatrb04 said:
pretty sure i have looked at most settings that could possibly effect this.
maybe its just the way it is.
it kinda bugs me at night when i wake up disorientated not knowing the time.
always something i have been used to with previous phones.
Click to expand...
Click to collapse
I hear you. Best to ignore the phone and sleep.
Always being "connected" detrimental to your wellbeing. Quiet time is very underrated.
Lots of power management settings scattered throughout the phone, usually.
Check to see if global power management is running first: Developer options>standby apps, all buckets should show as active otherwise power management is active. It can't be disabled here though.
Check each apk being used for AOD. Make sure they have needed permissions and that battery saving isn't checked.
Disable any power management including Android, 3rd party, carrier or manufacturer ones.
Try in Safe mode.
Clear system cache and AOD data.
Make sure screen lock isn't interfering with AOD.
With a factory reset even if it works the issue will likely reoccur. Exception is if a 3rd party app altered user hidden settings, this can and does occasionally happen with poorly written apps. Sometimes only after you uninstall them
Play with it, find the root cause... fun isn't it?
blackhawk said:
I hear you. Best to ignore the phone and sleep.
Always being "connected" detrimental to your wellbeing. Quiet time is very underrated.
Lots of power management settings scattered throughout the phone, usually.
Check to see if global power management is running first: Developer options>standby apps, all buckets should show as active otherwise power management is active. It can't be disabled here though.
Check each apk being used for AOD. Make sure they have needed permissions and that battery saving isn't checked.
Disable any power management including Android, 3rd party, carrier or manufacturer ones.
Try in Safe mode.
Clear system cache and AOD data.
Make sure screen lock isn't interfering with AOD.
With a factory reset even if it works the issue will likely reoccur. Exception is if a 3rd party app altered user hidden settings, this can and does occasionally happen with poorly written apps. Sometimes only after you uninstall them
Play with it, find the root cause... fun isn't it?
Click to expand...
Click to collapse
ah some things there that i havent tried.
will play around and report back.
yea the joys of android!!!
stuatrb04 said:
ah some things there that i havent tried.
will play around and report back.
yea the joys of android!!!
Click to expand...
Click to collapse
Feels good when you track it down.
I've tracked (and caused, oops) a few bizarre ones down
Stock Androids are generally very robust platforms.
Lately I have had a Oneplus 9, Oneplus 9 Pro and a Oneplus 10 Pro. In all of them, from Android version 12 (it also happens in 13), what is said here happens (AOD turns off at night even if it is programmed so that it is always active).
From what I see here, either it is a bug that has been introduced since the Oneplus and Oppo software were unified, or it is a crap that Google has put in Android since version 12 that there is no way to fix Because I've been trying things for a long time and reading in forums and websites and no solution to this problem is found anywhere.
For those of us who use our mobile phones as a nightstand clock, it is a great disappointment.
dtvenom said:
Lately I have had a Oneplus 9, Oneplus 9 Pro and a Oneplus 10 Pro. In all of them, from Android version 12 (it also happens in 13), what is said here happens (AOD turns off at night even if it is programmed so that it is always active).
From what I see here, either it is a bug that has been introduced since the Oneplus and Oppo software were unified, or it is a crap that Google has put in Android since version 12 that there is no way to fix Because I've been trying things for a long time and reading in forums and websites and no solution to this problem is found anywhere.
For those of us who use our mobile phones as a nightstand clock, it is a great disappointment.
Click to expand...
Click to collapse
Welcome to XDA.
Tap on works fine for me and uses less battery. Constantly looking at the time when you should be sleeping is counterproductive and a bad habit to get into. For me the novelty wore off after about a year as I find it now annoying.
It's the same on OnePlus 8T, Oxygen OS 13. At least after midnight, maybe earlier, the screen turns black with AOD always on after roughly 25-30 minutes if non use. Double tap or more activates it again.
It's broken for people who is working nights and/or is awake and active after midnight.
There's gotta be a setting fixing this through root or adb shell.