I'm the new owner of a Note 8. When I first got it, I noticed the auto-brightness feature had an offset where you could adjust it plus or minus the defaults. Later in the day, a couple of software updates came in and I installed them. Now the offset is gone. Has anyone else noticed this? I searched the forums and couldn't find anything. I really miss that setting already because the default is just too dim.
Related
Hello! Firstly I'd like to say thanks to any regular posters, this site helped me root my phone in the first place! I am trying to sort out what might be the cause of this problem and remove it, hopefully without starting over, as it was a pain in the butt to get the phone set up how I wanted and I do not have a full night to commit to it at the moment.
I have a Samsung S2 (the t-mobile branded one, sgh-t989), android 4.1.2 (kernel 3.0.31-1003885). This problem is recent and came on suddenly without changing any settings or installing any new software. The phone behaved normally for the first few months I owned it, it is a used phone, however, and I have no idea how the original owner treated it.
The problem is that brightness becomes tied to one or more of the sensors, and it takes several restarts, or sometimes days of waiting for the problem to go away. The brightness most often becomes tied to the accelerometer, where having the phone pointed at 45 degrees (or 01:30 o'clock), results in near 0% brightness, while returning to full brightness at 90-0 (or 3 through 12 o'clock). Occasionally it ties to another sensor (proximity?) or changes seemingly randomly, and once or twice has tied to the compass, with North being the brightness sink (with a similar 'darkness range' to orientation). The problem starts without a discernable cause.
Whatever the problem is, it also appears to disable, or for the most part inhibit multitouch. Around the time the problem started, tasker disabled and refuses to re-enable, if it is relevant. Shortly after the problem started, any push notification began turning on the screen (with a normal timeout, however). The problem persists through changing of any of the settings, toggling any modules, and through multiple resets, and never resolves itself without a cycle of multiple pulling-outs of the battery. After it is resolved, it usually remains fixed for a day or so before re-appearing.
If anyone has any suggestions for chasing down the problem, or has heard of anything similar, I'm all ears. I would like to avoid doing a factory reset, especially since I have no assurance it will resolve the problem. I'm happy to provide any additional information. Thanks for your help!
Coming from a Nexus5 I wanted to bring across more ringtones/alarms and notification sounds from that device to my new OnePlus 3.
So I got them all from my Nexus 5 and moved them to my OP3.
I couldn't find where the default ones reside, so googled and read (somewhere - don't know where) that they can be added to Internal Storage/Alarms, Internal Storage/Notifications and Internal Storage/Ringtones.
After doing so I've noticed that if I then pick a default (shipped) notification (not one of my imported ones) no sound plays when it should. Although within settings where you pick notifications the full combined list of default and custom notification sounds show.
So it seems that the Internal Storage/Notifications is completely overriding the default location when a notification should be played...
Has anybody else found this?
Could someone else test and back me up on this theory?
Does anybody know the location of the default directories for alarms/notifications and ringtones?
Thanks for any assistance!
Okay, so to update this myself, in case anybody else is having this issue... it isn't what i described above.
Not sure what it is, but for some reason having thought I fixed it yesterday by removing the notification sounds as mentioned above I noticed notifications had stopped again, today.
Then I noticed when I go to "settings > sound & notification > Default notification ringtone" and change the ringtone i don't hear the tone same being played as a sample....
After (and it took me ages to find this) modifying the ringer volume in sounds & notifications the notifications started sounding again.
So... what is causing it (I can't do this each time). For some reason my phone seems to auto switch to priority each night... yes, this shouldn't happen because OnePlus have implemented the slider functionality instead. But it seems to be happening and I think this might be causing the issues.
Why? Maybe because when I set my OP3 up I used NFC to migrate everything from my Nexus 5. Could this have also migrated my priority nighttime downtime settings, which are getting set at night and not unset in the morning?
Not sure if anybody else is interested, but I'll keep an eye on this and report back, in case I'm not alone...
Yes, this is the problem indeed. You should set it up as a new phone.
[I always do this even between flashes on the same phone... Yeah, I know it takes a lot of time]
Hey all.
I've been testing for a few weeks now, on both my recalled note 7 and my replacement and wondered whether anyone encounters the following issues. Think it could be software related bug or sorts. Definitely not hardware.
Sometimes the quick settings toggles can become unresponsive ( will work after a few presses) including the settings cog. I found this to happen mostly if the screen res is changed to QHD and the font set to small. With medium size font all works great.
Although, IF I reboot after I make any display changes, everything will work fine. I've found messing with the font settings and resolution can make the bug appear. I could pull the drop down and press the settings cog, it may or may not respond after the first press.
Now. If I set the screen res to just FULL HD with any size font, big or small every icon/setting/toggle WILL respond immediately, whether I reboot after making the changes or not.
Don't get me wrong, my phone runs GREAT (Touch wood). Just wondering whether anyone else experiences or takes notice of these things?
no, nothing simmilar here, althoug I dont like to play with resolutions, as they scrammble things around
I'm having the same problem though I must add I haven't been fiddling with the resolution or display settings. It is always at QHD.
kEvinErd said:
I'm having the same problem though I must add I haven't been fiddling with the resolution or display settings. It is always at QHD.
Click to expand...
Click to collapse
I've still been testing it, it defo seems to be a random software bug. The Layout boundries option in developer settings also shows how tight the lines are around some icons.
The glass and temperature may play a part in touch sensitivity also. I've cleared cache from recovery and seems to have temporarily solved the issue. Can be fixed I reckon by re-introduced the increase sensitivity option for gloves etc...
I have had this a couple of times. Never changed the resloution.
Same. Also in addition of this, my replacement runs warm idling and quite hot while loading. The whole system seems quite snappy but sluggish. My hope for Samsung is gradually vaporizing...
Hey guys,
I just got the update to Oreo on Verizon. So far I'm not liking it. I have several missing settings that I actually cannot find, specifically Ambient Display. I can find it in search, but when I click on it, it brings me to Display settings with the Advanced tab already selected but there is no setting for Ambient Display shown. I also can't figure out if its that or the Moto Display (where you approach to wake the device) but that setting is turned off. The phone is seriously waking it self up every couple seconds to show me a clock, the date and a blue ring showing the constantly draining battery percentage. I'm also very sad about the new emoji. I miss the blobby guys. Can I downgrade? how does someone do that anymore. Rooting seems very different now than in the pre 4.1 era I was used to on my previous phone. With my Moto Z Play, I haven't bothered to root or anything as it's worked right off the bat.
Thanks guys for your help.
First, this is a Moto z play or -02 forum, where what I think you have is a Droid or -01. So I may not be able to help much! - I have 8.0 where the ambient appears whenever the phone is touched or moved in any way. It only appears for about 3 seconds - i actually doubt this will have much effect on your battery, though if your phone is in constant motion , I suppose it could. The ambient display for me is a partial circle indicating % of battery charge, with %, time and date. I see no way to modify this. I suppose a custom ROM might change things but that would not be avail for the Droid as I know of no way to root it. I suppose you could always bug Verizon... Good luck with it!!! I generally like Oreo so far, but that is a problem with version updates - things change and we're pretty much stuck with it unless we can find and flash a different ROM...
Just moved to my first Samsung phone and slowly getting to grips from how it differs from stock Android on my old Pixel 2XL
One thing I am struggling with is when I have a calendar entry set to to busy my Pixel would automatically switch on Do Not Disturb, I have tried to find this setting on my Note but can't see it anywhere.
Is this possible to do or do I need to install any app for this?