Related
So this is what I did:
http://forum.xda-developers.com/showpost.php?p=9202470&postcount=8
and now I'm trying to figure out how to get my phone back to the way it was.
Few simple things:
i don't want the little gmail widget to tell me that i have new mail. I turned off autosync and unsynced my gmail account, but that didn't work
likewise i don't want the default messaging programs widget to pop up along with handcent, i just want handcent.
hmmm, i tried to set the wallpaper i used to have and it won't work. maybe cause i set astro as the default program to open to view the gallery? how can i unset that?
thanks!
Also, the phone screen used to dim after 25 seconds and turn off after 30 seconds. now the screen dims and brightens randomly, like as i'm typing a text message or something.
Figured out everything except the dimming/undimming
any ideas folks?
Have you checked in settings sound and display to see if power savings mode is checked? I know thay would cause what your talking about.
Sent from my GT-I9000 using XDA App
Thanks, but i have played with that on and off and it makes no difference
Is it related to the light sensor. Have you got his set to auto.
This feature dims and brightens the screen based on the amount of light the sensor see's which I think is the camera.
Ancient_One said:
Is it related to the light sensor. Have you got his set to auto.
This feature dims and brightens the screen based on the amount of light the sensor see's which I think is the camera.
Click to expand...
Click to collapse
Yes! That was it, thanks guy!
Any theories on how to stop it from vibrating when I plug it in?
There is an option in the settings , monitor , smart backlight control , with which , when is on , as say , can keep the screen on all the time you keep the phone on your hand , looking a photo for example , without touching the screen .
I set it to on but it's not work for me .
The screen goes off in the 1 minute limit I have set . But that shouldn't happen when smart backlight control is on .
What happen in yours phones?
The same here, this option doesn't work in my phone. Screen still switches off in my hand.
Sent from my D5803 using XDA Free mobile app
Works for me ... it seems to use the accelerometer, so as long as some small amount of motion in my hand is detected, it stays on.
I'd try the universal solution to common Xperia issues: set it, then restart the phone
Yes , if I move my hand it works .
But I try it and should move it a lot to work
I think it's not a practical solution from Sony. There where other ways to do this.
For me its practical,at the slightest move the smart backlight control activates,as for other solutions,its better then Samsung's eye detection which not works in the dark environmental(the sensor cant see your eye :cyclops:
Atleast the Samsung way works. The Sony feature doesnt work in light and dark conditions. It should be a way of both to keep the screen on. In light conditions it should be the camera. And in the dark the accelometer. Now it doesn't work at all.
sygys said:
Atleast the Samsung way works. The Sony feature doesnt work in light and dark conditions. It should be a way of both to keep the screen on. In light conditions it should be the camera. And in the dark the accelometer. Now it doesn't work at all.
Click to expand...
Click to collapse
Try Screebl. It's the best way to keep the screen on from all solutions I've tried (and I have owned a Samsung Galaxy S3 with eye detection and now a Sony Z3 with Smart backlight control)
It appears that ambient display does not work when your screen lock setting is set to None.
I was showing a mate my Nexus 6 yesterday and started playing with a few settings. I noticed that all of a sudden my ambient display stopped working. I did some testing this morning and finally worked it out that when the screen lock setting is set to None, ambient display does not activate. Any notifications that come through stop appearing on the screen. Setting the screen lock setting to anything other than None ensures ambient display works once again.
1. Is this a known feature / situation for the N6 ?
2. Is anyone else experiencing the same behavior or is it just me ?
1. if you dont have a lockscreen then it cant show you notifications on it. duh, lol.
2. we all have known about this since before lollipop came out.
1. I see no reason why a notification could not be shown on the screen using ambient display even if I don't have a lock screen. It is not like I have actually turned the screen on yet.
2. And yet, when I tried searching for an answer to why my ambient display wasn't working, I found no mention of it at all, not in XDA or the web in general.
Thanks for clearing it up for me, it is clearly a feature of the phone.
budorat said:
1. I see no reason why a notification could not be shown on the screen using ambient display even if I don't have a lock screen. It is not like I have actually turned the screen on yet.
2. And yet, when I tried searching for an answer to why my ambient display wasn't working, I found no mention of it at all, not in XDA or the web in general.
Thanks for clearing it up for me, it is clearly a feature of the phone.
Click to expand...
Click to collapse
if you dont have a lockscreen, then it has nothing to show the incoming message on. if no lockscreen, then it would just show in the status bar.
I understand your point simms22, but I think you may be missing mine. Does it have to be the lock screen that the notification is shown on when it arrives.
For example, msg arrive, screen turns on to show msg. If I do nothing then the screen turns off. If I haven't interacted with the screen, does the notification really need the lock screen to be displayed? I guess that I'm just not convinced that the lock screen is needed to display notifications when I pick my phone up, ie before I touch the screen. If I then interact with a notification then perform the interaction, but if I touch a part of the screen where is no notification, open the device.
The above would be mute if I pick the device up and press the power button to open the home screen.
I guess I look at things a little different, I design systems and interfaces for a living for the Dept of Defence.
I have found that the ambient display does not always activate when I pick the phone up, I'd say its about 90% reliable, have u found the same ?
budorat said:
I understand your point simms22, but I think you may be missing mine. Does it have to be the lock screen that the notification is shown on when it arrives.
For example, msg arrive, screen turns on to show msg. If I do nothing then the screen turns off. If I haven't interacted with the screen, does the notification really need the lock screen to be displayed? I guess that I'm just not convinced that the lock screen is needed to display notifications when I pick my phone up, ie before I touch the screen. If I then interact with a notification then perform the interaction, but if I touch a part of the screen where is no notification, open the device.
The above would be mute if I pick the device up and press the power button to open the home screen.
I guess I look at things a little different, I design systems and interfaces for a living for the Dept of Defence.
I have found that the ambient display does not always activate when I pick the phone up, I'd say its about 90% reliable, have u found the same ?
Click to expand...
Click to collapse
yea, the way the code is written, there needs to be a lock screen to be displayed. i dont really use it anymore, but i found it to be around 90% as well.
Just to re-iterate, Ambient display is displaying the Lockscreen notifications, not SystemUI notifications, so to show the lockscreen notifications, Lockscreen must be on.
budorat said:
It appears that ambient display does not work when your screen lock setting is set to None.
I was showing a mate my Nexus 6 yesterday and started playing with a few settings. I noticed that all of a sudden my ambient display stopped working. I did some testing this morning and finally worked it out that when the screen lock setting is set to None, ambient display does not activate. Any notifications that come through stop appearing on the screen. Setting the screen lock setting to anything other than None ensures ambient display works once again.
1. Is this a known feature / situation for the N6 ?
2. Is anyone else experiencing the same behavior or is it just me ?
Click to expand...
Click to collapse
I totally agree. I upgraded from my 2013 Moto X, with Moto DIsplay, to the N6. I NEVER used a lock screen on the Motox, and enjoyed being able to just glance at the phone to know what was incoming.. its quite annoying that I can no longer get my notifications to show up on my screen without turning the phone on, and pulling the shade down. I'm on the computer all day, and have my phone setup next to me and use it to get a quick view of incoming work emails, with out taking my hands off the keyboard, or even stop typing for that matter.
If I would have known that the N6 was unable to work in this matter I would not have gotten it. I would have gone with the Moto X 2 instead.
Hi guys. Do you know any, preferably minimalistic, screen lock app that is compatible with ambient display? Have tried my fav Zui Locker with no luck.
tr3mm0r said:
Hi guys. Do you know any, preferably minimalistic, screen lock app that is compatible with ambient display? Have tried my fav Zui Locker with no luck.
Click to expand...
Click to collapse
I dont think it works with any.
That's what I was afraid of. Sticking with stock locker then since I love the new feature.
Sent from my Nexus 6 using XDA Free mobile app
Ok guys so I need to know if there is a sensor issue with my phone .I don't use auto brightness no more because if you go in the sun the brightness overrides itself to brighter than max brightness and it is the reason why I've had burn in 4 times so far and had to get the screen replaced. But I've also noticed that with auto brightness off but you have the brightness maxed out and go in the sun or shine an led torch at the sensor the screen will kick up to override max brightness sun mode out like when using auto brightness. Is this normal behaviour. Can anyone test this fpr me please .only 6 months left of warranty left
So if this is a feature its stupid ,and make sure you never put your phone on max brightness in manual or autobrightness if out side and it's sunny as it will kick in and cause screen burn .
I've factory reset it and cleared cashe still the screen in manual mode if maxed out in the sun with the brightness maxed out will auto ride to super max brightness mode .im on the oreo uk fm
Phone is uk unlocked note 8.
Anyone? I see lots of views no replys I'm sure everyone that view this thread owns a note 8?
OK lol thanks for the great respone guys smh this place sucks :good:
haircut123 said:
OK lol thanks for the great respone guys smh this place sucks :good:
Click to expand...
Click to collapse
No, this place does not , if you do not get any response , it means nobody has something useful to share, beeing rude will gain you a ban
Maybe your the only person that has this error, so no one has any advice to give other than to factory reset (which you all ready done).
Most people has moved on to other phones. So you'll have to be patient. I say is take it to the Samsung store and see if it is covered under warranty.
I'm not the only person all note 8s do this i think but nobody in this thread owns a note 8 or 9 other than me because they both do it. On both my phones.its a terrible feature as it will cause burn in.if you want to be able to see the screen outside in the sun
So i've been using auto brightness for 2 years, i don't have any burned screen. Last week I've been using phone on sun, taking a lot of pictures (brightness set to auto, on camera app its option to set it to max bright) and still no burnout. I think you should say your problem to guy who will accept your warranty next time
Well this is good to know just went to the sammy service centre and tested the phones they had there with my led torch and they all do it including the s9 plus .so it maybe always was like that or it's been added into a fw.
haircut123 said:
Well this is good to know just went to the sammy service centre and tested the phones they had there with my led torch and they all do it including the s9 plus .so it maybe always was like that or it's been added into a fw.
Click to expand...
Click to collapse
I will add that friend have a s8, his screen is good. Also another friend had note 8 and now note 9, always autobrightness on, no problems so far.
I have a little experiment
1st, I set auto brightness on, turn on a torch on the sensor, brightness go to max, then turn it off, and brightness go to middle (room light on)
2nd, set the auto brightness off, slide the brightness to minimum, turn on the torch to sensor, and brightness remain to minimum, nothing change
So I assume maybe it's a software feature I don't have, you can check with your friend running the same firmware, or you can check using *#0*# on keypad, click on sensor, look for light sensor, and do a simple test, see how much lux you have when you're on direct sunlight, or in a room, then you can flip your phone down / reverse the light source, the lux sensor must be read it on continuous count, as you flip your phone, the number will get decrease
I hope you understand what I am saying, because English is not my native language
ahmadddea said:
I have a little experiment
1st, I set auto brightness on, turn on a torch on the sensor, brightness go to max, then turn it off, and brightness go to middle (room light on)
2nd, set the auto brightness off, slide the brightness to minimum, turn on the torch to sensor, and brightness remain to minimum, nothing change
So I assume maybe it's a software feature I don't have, you can check with your friend running the same firmware, or you can check using *#0*# on keypad, click on sensor, look for light sensor, and do a simple test, see how much lux you have when you're on direct sunlight, or in a room, then you can flip your phone down / reverse the light source, the lux sensor must be read it on continuous count, as you flip your phone, the number will get decrease
I hope you understand what I am saying, because English is not my native language
Click to expand...
Click to collapse
You did the test wrong friend you need to turn off auto brightness and slide the brightness slider to max brightness it must be fully maxed .then shine led torch at the sensor then the brightness overide kicks in and goes even brighter just like In auto brightness mode.but if the slide is not fully maxed it won't do it
haircut123 said:
I'm not the only person all note 8s do this i think but nobody in this thread owns a note 8 or 9 other than me because they both do it. On both my phones.its a terrible feature as it will cause burn in.if you want to be able to see the screen outside in the sun
Click to expand...
Click to collapse
haircut123 said:
Well this is good to know just went to the sammy service centre and tested the phones they had there with my led torch and they all do it including the s9 plus .so it maybe always was like that or it's been added into a fw.
Click to expand...
Click to collapse
Interesting you mentioned all devices do this before you went to the service centre and confirmed it. That admission renders your entire post pointless. If all the devices does this, it means it's not a fault on your sensors or anything on your side, and it means it's indeed just a feature.
Max_Terrible said:
Interesting you mentioned all devices do this before you went to the service centre and confirmed it. That admission renders your entire post pointless. If all the devices does this, it means it's not a fault on your sensors or anything on your side, and it means it's indeed just a feature.
Click to expand...
Click to collapse
I said imo that all devices have this issue. Because bothe my note 8 amd 9 have the same issue .and i found a thread on reddid where 2 others also had the same issue.its not a feature because it can damage the screen it must be a software bug that Sammy need to fix
haircut123 said:
You did the test wrong friend you need to turn off auto brightness and slide the brightness slider to max brightness it must be fully maxed .then shine led torch at the sensor then the brightness overide kicks in and goes even brighter just like In auto brightness mode.but if the slide is not fully maxed it won't do it
Click to expand...
Click to collapse
Ah I see, after doing that, I found out that the screen goes brighter and the colors seem to be fade out
Maybe it will help us to watch better when we got under direct sunlight (I think it's not a bug)
But in real life usage, I have my adaptive brightness turn on, then when I think it's too much bright at the moment, I will manually adjust it to my desire brightness
So that the system will learn the pattern and will apply automatically next time I had the same condition
Doesn't do that with mine and I live in Hong Kong.
So I bought this phone yesterday, stock and no third party app. did a factory reset inserted the simcard and recieved a sms. when screen was off, a green small notification was blinking on left upper part of screen (something like what third party apps like aodnotify do but it was better). I was amazed that samsung finally did something to fill the void of an actual notification Led. but after my second factory reset (after a 450 mb update) the feature was gone!!
I searched every where for it. tried different settings in Aod and edge light and... nothing
can anyone explain this to me? could it be an experimental feature on my stock firmware that was removed from latest update?
thanks in advance
I don't understand it either. I don't have it on screen off but I have it when I charge the phone or answer a call. Weird behavior.
That's being used as a proximity sensor I believe to turn the screen on and off during calls. It might also disable the screensaver/always on mode if the phone is face down.
thanks for the answers.
Edit: that's the proximity sensor as you said which lights up during calls, but I don't know why it was lighting up when there was no app running and the screen was off. odd behavior! perhaps accidental touch detection was acting incorrectly.