I just received my Nexus 7 3g in the mail from play. Turned it on and installed the 4.2.1 update. I didn't really mess with it till after the update but the auto rotate/orientation switch does not seem to work. The settings menu shows it's on. Also did a factory reset, rebooted, and nothing. Same thing. Anyone seen this?
EDIT: Actually no idea all of a sudden it seems to be working now for no apparent reason =\
Stock lockscreen doesn't auto rotate, I think.
Hi guys,
I have upgraded my n9005 to KK for a while now. And it seems that with KK 4.4.2 randomly break my auto brightness from time to time. This issue occurs the same time when an incall screenoff stop working.
To begin with, after a while of usage the auto brightness feature breaks where it did not adjust automatically. I got a very dim brightness level eventhough it's a night time. Also the auto brightness level doesn't work as well. But when I turned this feature off the brightness slider works again. Now while this is happening and I'm on the call my screen won't turn off automatically during the call or when I have finished my call the screen wont turn on. So for both issues I have to manually activate the screen via Home/power button. Moreover, I have notcied that while this is happening when I entered Camera app, the screen will be fixed on the landscape mode only and there is no way I can make portrait back again.
To be even more surprise, these issues will be gone and come back from time to time without restarting. However, upon restarting everything works fine for a while.
What I have tried to solve this issue:
- Reflash stock firmware (official version of my country)
- Clear dalvik
- Flash stock firmware (latest version from DBT)
Still I'm unable to solve these issues. I'm wondering that have any of you guys are facing these issues as well? I have searched and it seems that I'm only one having these problems. I just want to know whether this is only software or hardware related
Thanks
SoKoOLz said:
Hi guys,
I have upgraded my n9005 to KK for a while now. And it seems that with KK 4.4.2 randomly break my auto brightness from time to time. This issue occurs the same time when an incall screenoff stop working.
To begin with, after a while of usage the auto brightness feature breaks where it did not adjust automatically. I got a very dim brightness level eventhough it's a night time. Also the auto brightness level doesn't work as well. But when I turned this feature off the brightness slider works again. Now while this is happening and I'm on the call my screen won't turn off automatically during the call or when I have finished my call the screen wont turn on. So for both issues I have to manually activate the screen via Home/power button. Moreover, I have notcied that while this is happening when I entered Camera app, the screen will be fixed on the landscape mode only and there is no way I can make portrait back again.
To be even more surprise, these issues will be gone and come back from time to time without restarting. However, upon restarting everything works fine for a while.
What I have tried to solve this issue:
- Reflash stock firmware (official version of my country)
- Clear dalvik
- Flash stock firmware (latest version from DBT)
Still I'm unable to solve these issues. I'm wondering that have any of you guys are facing these issues as well? I have searched and it seems that I'm only one having these problems. I just want to know whether this is only software or hardware related
Thanks
Click to expand...
Click to collapse
Kinda noticed this while I was briefly on kk. If you're on AT&T keep in mind that it was not the official release, and bugs are present.
Sent from my SAMSUNG-SM-N900A using xda app-developers app
sireniankyle said:
Kinda noticed this while I was briefly on kk. If you're on AT&T keep in mind that it was not the official release, and bugs are present.
Sent from my SAMSUNG-SM-N900A using xda app-developers app
Click to expand...
Click to collapse
Thanks for letting me know that this is common for KK on N9005. LOL I thought it was HW related issue though
Upgrade to lollipop seemed to work fine. As part of this, we now have the yotafit app and EPD widget. However, mine refuses to register any steps whatsoever when I move. I have tried the various priority and mode options but nothing seems to work. Location services are on. Does anyone else experience this?
OK - seems to work now after I tried to fix something else. I was receiving the message 'NO SERVICE' on my lock screen even though I was connected. Some searching prompted me to try to fix this by turning airplane mode on and off. This did fix the NO SERVICE problem, but it also seems to have fixed the yotafit issue. Maybe it was just a coincidence but at least it seems to work now and the steps are showing on the app and the EPD widget!
Anyone else notice this? I set the DND automatic rules to Alarms Only from 10pm to 6am, Sundays through Thursdays. The phone will automatically turn on DND at 10pm, but for some reason it never switches off at 6am. Once I notice, I can manually turn it off but that defeats the purpose of having an automatic rule in place. I've noticed this on both the March and April updates, but I'm pretty sure it worked properly before that.
Heinous said:
Anyone else notice this? I set the DND automatic rules to Alarms Only from 10pm to 6am, Sundays through Thursdays. The phone will automatically turn on DND at 10pm, but for some reason it never switches off at 6am. Once I notice, I can manually turn it off but that defeats the purpose of having an automatic rule in place. I've noticed this on both the March and April updates, but I'm pretty sure it worked properly before that.
Click to expand...
Click to collapse
I am having the same problem, did you ever find a solution?
I noticed this the other day on my 6P. It works properly in Safe Mode (you can tell when you adjust the volume control as it displays the rule name instead of the generic 'until you cancel it'). This means some app I had installed was messing with it.
I tried deleting a lot of apps but none made a difference. I ended up doing a factory reset and all is well. I have reinstalled almost all of my apps and it is still working. The only ones I have yet to install that deal with notifications are Tasker, and DLink and Samsung camera apps. Yet I deleted them before the reset and it didn't change anything.
Previous to me noticing this, I had set up a Tasker profile to read my notifications to me; in this case all notifications. I have a feeling this may have broken something (Android is so brittle), but odd that the behavior persisted after disabling Tasker (and even uninstalling it).
stevetrooper said:
I am having the same problem, did you ever find a solution?
Click to expand...
Click to collapse
No, I think it just fixed itself at some point. I am Having the same issue again on my new phone (Xperia XZ), so I'll post here if I figure it out.
Oops I just posted the same question before finding this thread. Having the same problem on my 6P which was upgraded from M to N. I have a 5X too that I started fresh on N (stock image flash) and it works fine on that one, just not on my 6P. Not sure if it's the upgrade M to N or specific to the 6P.
I tried deleting the rule and re-creating it but it doesn't help.
(if a mod could please merge the 2 threads)
http://forum.xda-developers.com/nexus-6p/help/coming-disturb-mode-using-auto-rule-t3496957
I have this same issue. I had it on the Pure Nexus ROM too. Now I'm on stock 7.1.1 and the DND still doesn't turn off when it's supposed to. Annoying AF.
Not sure what we can do about it, I'm thinking not use the rules and instead use an automation app to do it, the likes of MacroDroid, Automagic, etc. Don't know if such apps would require root to turn DND on/off though.
It happens since marshmallow, sometimes a reboot fix the issue and sometime you have to turn off the automatics rule manually turn on and off the DND and reboot.
I get this issue when DND is set on automatic rules and i change it to on or off manually (only sometimes).
Interesting, I never had a problem on M, it only started for me after I upgraded to N.
I didn't have this problem after I upgraded to N, it was the October security update when the problem started for me.
There's a bug filed it seems. Hopefully Google will do something about it. Please vote for the issue to be fixed.
https://code.google.com/p/android/issues/detail?id=226041
Are you using Android Wear? It seams, that after today's update AW app (version 2.0.0.138705214), problem with DND mode went away. Look at Apkmirror for that version, and please report, if it solve this problem you as well.
Srandista said:
Are you using Android Wear? It seams, that after today's update AW app (version 2.0.0.138705214), problem with DND mode went away. Look at Apkmirror for that version, and please report, if it solve this problem you as well.
Click to expand...
Click to collapse
I do use Android Wear and I got the update to 2.0.0.138705214 this afternoon. I will report tomorrow morning if the Automatic rule turned itself off. Thanks for the tip.
It seems that the latest Android Wear fixed the issue for me, at least for now. I hope it sticks. Yes, I use Wear.
sirxdroid said:
It seems that the latest Android Wear fixed the issue for me, at least for now. I hope it sticks. Yes, I use Wear.
Click to expand...
Click to collapse
Same here.
Android Wear update seems to have fixed it for me too.
Yep, it's been working fine for 2 days now.
Same here https://forum.xda-developers.com/nexus-6p/help/disturb-disable-t3556270
When I go to use Google Maps for navigation, I often get the message "To continue turn on device location which uses Google's location service". The problem also affects ViewRanger, an app I use for walking. GPS appears to turn off during a walk so I lose the track of my route. In this case the message is "GPS is disabled in the settings. Please enable it."
I recognise this happens after the phone has been "asleep" for a while but have not been able to measure how long it must be asleep before the problem arises. I think it is at least 30 mins.
It feels like a "battery saver" problem, but I can't see any obvious power saving setting to turn off. ViewRanger is set in App Power-saver to have no optimisation policies.
I have had my Axon 7 since Jan 2018 and this problem has only occurred in the last few weeks. My model is A2017G on stock Oreo B03 and unrooted. The problem did not emerge when I first moved to Oreo. It may have started when I moved to B03 though I think GPS was fine for a while after I moved to B03.
Something is turning off location services in the background; how do I find out what it is? Is there some sort of log I can read? What other solutions are there? Many thanks in advance, Evan
I moved from stock Oreo B03 to B04 (via B02) and wiped the cache. All now seems to be well; ViewRanger recorded a 4 hour track with no problem yesterday. Slightly strange though as I had previously wiped cache while on B03 and found that didn't fix my problem.
Too good to be true
grantem2000 said:
I moved from stock Oreo B03 to B04 (via B02) and wiped the cache. All now seems to be well; ViewRanger recorded a 4 hour track with no problem yesterday. Slightly strange though as I had previously wiped cache while on B03 and found that didn't fix my problem.
Click to expand...
Click to collapse
It did all seem a little too good to be true and, sadly, Location Services again began "turning off automatically" only a few days after my upgrade to B04. I have attached 2 screenshots from the notification log for when I started recording a route in ViewRanger at 15:07 and again 3 mins later at 15:10 when tracking appeared to stop. The logs mean nothing to me, so any insight would be very welcome.
In the meantime, I uninstalled ViewRanger, deleted all ViewRanger directories, restarted the phone, re-installed ViewRanger and wiped cache again. After that, for now at least, Location Services are again behaving.
As all this appears to point the finger at ViewRanger, I will raise direct with the application owners too.
grantem2000 said:
As all this appears to point the finger at ViewRanger, I will raise direct with the application owners too.
Click to expand...
Click to collapse
ViewRanger, support were very responsive and supportive. They made a convincing case that the problem is not caused by ViewRanger, not least as the app has no capability to turn off Location Services.
But something is still turning off Location Services when the phone goes to sleep. How can I tell what is doing this?
In the meantime, wiping cache solves the problem for a few days, but, so far, it has always come back.
I have the same issue and that's why I think this phone's gps is useless. I find this gps not in accurate way to detect the coordinates even in all previous firmwares (nougat, all ver of oreo)
The auto turned off gps services maybe the case of software, but I think the hardware is bad either.
This is the worst part as I work using GPS a lot but I still love this guy's music features. I ended up using secondary phone/tablet to run some geographical apps, sad cant have em running in one phone only.
Update: my GPS get fixed on B04 with locked bootloader, it seems fine and fast to get POI. It's usable now. Guess the previous rom has bugs on GPS or it's broken by other apps I used before