Related
And more specifically and as far as I can tell, if the phone is freshly booted then the functions listed above work. However, after several hours on I go to adjust the brightness and the screen does NOT change its brightness no matter whether i set auto-brightness or adjust it manually.
Let me preface this topic and let you all know that I still have my stock screen protectors attached and I've installed the light flow app if that matters.
Any ideas?
EDIT: I such at naming titles.
same here, just wiped. no clue what's causing it
Same for me I just noticed this. Hope its something fixable in an update.
Sent from my Nexus 4 using xda app-developers app
i don't have this problem, auto brightness and slider always work
Auto brightness doesn't work
I am having this problem too... Works for the first while, then doesnt work at all...
*** Ive commented on a logged issue with google, ISSUE 40378
https://code.google.com/p/android/i....2&colspec=ID Type Status Owner Summary Stars
I uninstalled ledblinker and it seems to solve the problem. Do you guys use lightflow? That might be the culprit
ceejay83 said:
I uninstalled ledblinker and it seems to solve the problem. Do you guys use lightflow? That might be the culprit
Click to expand...
Click to collapse
It doesn't make a difference if I use lightflow or not it just won't act right.
Sent from my Nexus 4 using xda app-developers app
Jefferyrbrown1983 said:
It doesn't make a difference if I use lightflow or not it just won't act right.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Have you tried wiping? I haven't had any issue since
Ugh never mind, brightness got stuck again.
Wow am i glad to have found this thread, i have been battling this problem since day one with this phone, and i have been trying to track it down with usb debugging but have been unsuccessful. What happens is that my screen will randomly shut off and be non responsive for 5 seconds and when i can turn the screen back on, i can no longer adjust the brightness and only a reboot will solve the issue. It also occurs when i am not using the phone so i think it is a hardware issue but i am uncertain.
Things i have tried to fix it:
Factory reset
Fastboot flash factory image
Flash cutom ROM & Kernel
Didn't realize it before but yes, my screen randomly turns off, then the brightness gets stuck. Thought it was timing out
---------- Post added at 03:52 PM ---------- Previous post was at 03:46 PM ----------
You guys use auto brightness? Maybe that might be it
This happens to me occasionally too, haven't been able to determine what triggers it. It's almost as much fun as the magical battery levels. Plugged in the other day, went from 4% to 100% in a nano second.
interesting...my auto and slider work just fine
ugh still getting this problem daily. does't matter if auto brightness is on
There is no solid way to reproduce the problem, so I am willing to bet its a hardware issue. I will be calling T-Mobile this week to replace it.
Sent from my Nexus S
Of the people who are experiencing it, how many have a notification drawer widget (Widgetsoid, Power Controls, et al?) and have a brightness toggle on it?
I've removed brightness from Widgetsoid to see if it's a conflict of some sort.
CMNein said:
Of the people who are experiencing it, how many have a notification drawer widget (Widgetsoid, Power Controls, et al?) and have a brightness toggle on it?
I've removed brightness from Widgetsoid to see if it's a conflict of some sort.
Click to expand...
Click to collapse
Yes I'm using power controls. Still does it even if I disable the brightness toggle
Hmmm...wonder if there's a submission on Gerrit, shall troll later.
Sent from my Nexus 4 using Tapatalk 2
CMNein said:
Hmmm...wonder if there's a submission on Gerrit, shall troll later.
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
Might be a hardware issue? If it was software I think a lot of people would be complaining about this.
Edit: ugh as I was typing this post, screen flashed and turned off with broken brightness. I just rebooted like 5 min ago too
ceejay83 said:
Might be a hardware issue? If it was software I think a lot of people would be complaining about this
Click to expand...
Click to collapse
Not sure. Here's one report on Google Code: http://code.google.com/p/android/issues/detail?id=40378
Edit: could just as easily be a OS issue, if it decides to stop polling the light sensor for some reason. Many people have the battery bug as well, which seems to stop polling the battery for some reason.
My brightness automaticly lowers itself.. why? i havent set auto brightness on.. if i set it on than the brightness issues is gone.. if i dont then .... i set brightness to highest , turn the screen off then on it , it dims itself....! then i turn the screen of and on it goes normal... sometimes it dosent.. please help im on AOKP ROM > Steves build jan 17 , faux kernel beta 5v6
bump
AW: Brightness Issues
lokenok said:
My brightness automaticly lowers itself.. why? i havent set auto brightness on.. if i set it on than the brightness issues is gone.. if i dont then .... i set brightness to highest , turn the screen off then on it , it dims itself....! then i turn the screen of and on it goes normal... sometimes it dosent.. please help im on AOKP ROM > Steves build jan 17 , faux kernel beta 5v6
Click to expand...
Click to collapse
This doesnt belong here. Ask in Q&A or faux or AOKP thread!
Sent from my Nexus 4 using xda premium
Kay thanks .. can i kindly ask moderators to move this to q and a?
If you turned off the transition animations then this will happen, it is a known bug.
Sent from my Nexus 4
Aokp has a feature where you can slide your finger across the status bar to increase /decrease brightness. You probably did it without even realizing it.
Sent from my Nexus 4 using Tapatalk 2
naw i didnt turn that feature on , the one where u slide ur finger
thanks silent but my transition animation wasnt off.. i tried turning it off but still the same issue
bump.. help plz
Does this happen on all ROMs? Try testing it with the stock factory image. You may very well have a faulty screen, if your issue persists with stock image then you might want to RMA, or stick it out and see if 4.2.2 will fix your issuse which it may very well not. Good luck.
Sent from my Nexus 4
no ^ not faulty screen , its from december batch , anyways it dosent happen on stock rom or earlier versions of aokp but latest versions of aokp seems to do the job.. do you bet its because ive seen my screen to lock 30 secs after hitting power button and using juicedefender?
help plox bump
seen a few posts in here but can not find a fix for this it is using 41% and draining my battery like mad had anyone else got this problem and found a fix plz ty
Delete it.
Sent from my SM-N9005 using XDA Premium 4 mobile app
Killberty said:
Delete it.
Click to expand...
Click to collapse
as easy as that ? its not deeded by anything ? what is it anyway ?
Killberty said:
Delete it.
Sent from my SM-N9005 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
trued that and it wont let me delete it or rename it
Cookie799 said:
trued that and it wont let me delete it or rename it
Click to expand...
Click to collapse
had this as well, a SHUTDOWN and then battery pull helped.
also have seen mention of "force stops" triggering this, advice was to not force stop anything for a while and see if it triggers again.
---------- Post added at 03:51 AM ---------- Previous post was at 03:46 AM ----------
Cookie799 said:
seen a few posts in here but can not find a fix for this it is using 41% and draining my battery like mad had anyone else got this problem and found a fix plz ty
Click to expand...
Click to collapse
btw, this might assist:
https://plus.google.com/u/0/+Senectus/posts/QiD2J4mizrD
Cookie799 said:
trued that and it wont let me delete it or rename it
Click to expand...
Click to collapse
Are you rooted?
Sent from my SM-N9005 using XDA Premium 4 mobile app
Mine has been doing the same ever since the kitkat update.
I am running an unrooted EE note 3 (n9005) in the UK.
Gsiff_daemon is constantly my top battery drainer according to the battery app (35% - 47%).
I have not been able to find any consistent method to either activate this rogue app or to get rid of it.
Is there any solution without rooting it as I understand that renaming it should do the trick?
Usually the problem is when you soft reboot.
It was reported somewhere that it is the GPS sensor daemon, but disabling it did not show any adverse effects for me.
Get a root file explorer and remove it/rename it to .bak
nicholaschum said:
Usually the problem is when you soft reboot.
It was reported somewhere that it is the GPS sensor daemon, but disabling it did not show any adverse effects for me.
Get a root file explorer and remove it/rename it to .bak
Click to expand...
Click to collapse
Thank you.
I will give this a shot and see if it helps.
gsiff_daemon fix.
Hello all. I just posted this on another thread so i will copy and paste to save doing it all again.
*No root required*
Hey
This worked for me.
In settings and the application manager, under the 'All' tab. I found a program called 'unified daemon(EUR)'
I tapped on it and disabled it.
The gsiff_daemon has since not appeared on battery usage.
I also set Power saving mode and changed Keep Wi-Fi on during sleep, to never, in the advanced wifi settings. Select wifi option in settings then press menu tab and select advaadvancednced to find the option. This turns off wifi when it's not in use and automatically turns on when you turn off lock screen.
my battery has more than doubled.
Hope it works for you too.
In my informal testing I found that gsiff_daemon is somehow related to S Health (somehow keeps the sensors awake even if you're not using the phone). I disabled S Health and SensorService and the problem went away. Easier for us unrooted types.
Solved!
ericastill said:
In my informal testing I found that gsiff_daemon is somehow related to S Health (somehow keeps the sensors awake even if you're not using the phone). I disabled S Health and SensorService and the problem went away. Easier for us unrooted types.
Click to expand...
Click to collapse
You nailed it!
This just started happening to me a few days ago, when S Health was updated. I have disabled S Health and presto! Problem solved.
Thanks!
SERIOUS Battery drain here
PROBLEM:
About three weeks ago I started to experience serious battery drain. This is a significant difference in daily results compared to a month ago. Now, three weeks into it I am having to put my phone into ultra power save mode on a daily basis just to be able to function as I am getting 1-3 hours of use out of my phone at this point. The problem has gotten progressively worse, as time has progressed over the last three weeks. Today seems to be the worst with me LOOSING battery charge while it is plugged in, and not in ultra saving power mode, (My phone is loosing 1% about every 10 minutes) and only having about 10 minutes of expected battery time LOL.
ENVIRONMENT:
Today is 1/8/14
I have a T-Mobile Samsung Galaxy S5 (G9000T). I have had it for about 8-9 months, got it brand new (was replaced once 4 months into using it because of broken camera), but this is my second GS5 phone.
I am using Android software version 4.4.2
TROUBLESHOOTING:
Only app added in the last 3 weeks was HeyTell, which was about the time this problem started. Force stopping the app actually helped for about a day or two until the problem resurfaced. Finally deleting the app last week did no good.
Talking to T-Mobile, they recommended testing my gyro sensor.
Go to call screen and dial *#0*# and I get a test screen.
I pressed sensor and then test gyro. It failed. They recommended a master reset. DAMN, I HATE doing that. So much time to get it back to where I want it.... SOOOO many notes on how to set the phone back up LOL.
RESOLUTION:
I did a master reset today 2/9/15. They gyro is still showing a failure, so they are replacing the phone.
Same issue samsung s5 duos
Hello,
I had the same issue of the battery being used quickly by the gsiff daemon.
Thanks for your details of what this application is.
For the solution, I did a few soft restarts, a hard restart and activated the light power saving mode. After 2 days my phoned worked fine.
Don't have any more information.
Cookie799 said:
seen a few posts in here but can not find a fix for this it is using 41% and draining my battery like mad had anyone else got this problem and found a fix plz ty
Click to expand...
Click to collapse
How to stop gsiff_daemon?
1. Hot reboot your Samsung Android
2. Rename gsiff_daemon
3. Disable apps using gyroscope sensors
Source: https://fixyourandroid.com/about/gsiff-daemon/
Hello Friends,,,I have Motorola Defy+ running CM11 24-08 build, actually from some days my phone is behaving very weird, when I wake up phone from sleep mode the screen is continuously flickering/blinking, it stops automatically after 3-4 mins of phone use, I mean screen is on for a while.
the biggest problem faced by phone is in the morning after waking up from long time sleep mode, in morning I cant even unlock the phone, black and white strips are appearing on screen but after 10-15 mins its working normally,,,does anyone faced this type of problem ???
I'm using CM11 from quarx too here on my defy. I've not experienced the issues described by you yet. That's why I fear this is a hardware issue.
You can roule this out by flashing the rom again while wiping data (make a backup first of cause ). If the issues persist then it is in all likelihood the phone's hardware which is defective (mainboard, or display cable for example). If a clean install fixes the issue then I would recommend using Titanium Backup to backup your apps and then restore them after a clean flash one at a time until you find the one which causes the behaviour.
Hope this helps.
Thanks @MP1_ bro I have tried everything,,, but problem still not solved yet,,, flashed SBF, stayed a whole day on SBF but screen flickering still there,,, I am not understanding these problem,,, if it's hardware related then why after using phone for a while it works normally,,, but waking up from sleep mode the screen flickering again continue for a some minutes
Sent from my MB526 using XDA Premium 4 mobile app
Such a behavior is not all that unusual for a hardware defect. When you got a defective soldering for example it can work like a charm when the phone is heating up due to usage (the material expands to close the cracks in the connectors). Unfortunately this does not really help you in locating/isolating the defective part of the phone.
@MP1_ bro then what's the solution ?
My phone is 3 n half year old,,, didn't even have any problem in these years,,, but I change USB wall chargers too many times,,, so does it affect battery? have Just a doubt on battery
Sent from my MB526 using XDA Premium 4 mobile app
I'm afraid there won't be an easy solution Don't worry about the battery - changing chargers is no problem, I doubt the display flickering issue has an negative effect on battery life.
Ideally you would have a spare defy from which you could borrow parts in order to isolate the defective part in your phone. It could be the display illumination, the display itself, the display cable or some problem with the power supply on the mainboard of the phone. Apart from the dispay cable all of these parts aren't cheap.
Yes I have searched it on Google that original defy screen is of $33
But I am afraid to give my phone to service center,,,coz here in India they are not trustable,,, they will surly fool me
Sent from my MB526 using XDA Premium 4 mobile app
Anyone had the same problem which happening with my phone???
Sent from my MB526 using XDA Premium 4 mobile app
Hi guys I have a problem on my s8.
Auto brightness always worked for me, but I just noticed that now it stopped working at all. Like, usually if i set brightness to max and then set autobrightness on, it auto reduces it to like 25%, meanwhile now it doesnt change the brightness ever. I have the feeling that auto brightness stopped working after i installed the last patch with odin (the UK unbranded one) since I patched it like 4 days ago and in the past weeks it worked fine. I dont think its a hardware problem because I tried sensor box app and in a black room it shows 0 while in a light one it goes to over 100 and next to a lamp over 2000.
Any idea what could be the problem? And how to fix it? I really would hate to do a hard reset since i'd lose too much stuff... could it be the patch that has a bug? Thanks in advance!
tharghan said:
Hi guys I have a problem on my s8.
Auto brightness always worked for me, but I just noticed that now it stopped working at all. Like, usually if i set brightness to max and then set autobrightness on, it auto reduces it to like 25%, meanwhile now it doesnt change the brightness ever. I have the feeling that auto brightness stopped working after i installed the last patch with odin (the UK unbranded one) since I patched it like 4 days ago and in the past weeks it worked fine. I dont think its a hardware problem because I tried sensor box app and in a black room it shows 0 while in a light one it goes to over 100 and next to a lamp over 2000.
Any idea what could be the problem? And how to fix it? I really would hate to do a hard reset since i'd lose too much stuff... could it be the patch that has a bug? Thanks in advance!
Click to expand...
Click to collapse
I have similar issue with my phone after latest update. I did hard reset without luck. All we have to do is to wait until new patch will be released and hopefully fix this issue. Regards
Sent from my SM-G950F using Tapatalk
ojkajoj said:
I have similar issue with my phone after latest update. I did hard reset without luck. All we have to do is to wait until new patch will be released and hopefully fix this issue. Regards
Sent from my SM-G950F using Tapatalk
Click to expand...
Click to collapse
I'm really surprised that Samsung will go live with a firmware with bugs like this, I guess they really dont test anything.
I think is the same for me ! With AQG5 firmware (the last one) when you change the brightness with auto brightness on, the phone memorise the setting with the ambiant light condition : you can see it by doing the following : turn auto brightness on and then set brightness up or down. Then uncheck auto brightness of and place the curser at the opposite. At last put auto brightness back on and the brightness will jump where you put it before like the phone memorised it.
Also with auto brightness on you can put your thumb on the sensor in the upper left side of the phone to simulate darkness. The screens goes darker and as soon you remove your thonger he goes lighter.
I dont understand why just some of us have this problem. They should released a fix soon because its really annoying not to have it working, I dont want to have to wait a month or more like this...
It pissed me off so I downgraded to AQF7 : the issue is now gone =)
Same thing over here!
The AQF7 update was by far the best and most stable one to date. Now my home button problem is back and lag also!
Before it I had home button issues with response and lag whille scrolling. Whit the current update everything came back!
Samsung really needs to get their s*** together!
Well... when they released the AQH3 in the changelog it said they fixed the auto brightness thingie, yet I just installed it and guess what? I still have the same problem. Auto brightness still doesnt work, like in the firmware that came out a month ago.
Anyone else tested it? What the **** is Samsung doing?
No one tried yet?
I agree with you, the autobrightness still doesn't work.
Sent from my SM-G950F using Tapatalk
Any way to fix this? I am using an app called lux, but it's not perfect, still better than nothing
I have the same problem. I saw another thread that said it's not a bug. They made it that it learns your patterns, so it won't change when you hit the auto brightness button, but it still does become brighter when you go outside, and dimmer when you go inside.
I'm not happy with it though, as it worked perfectly for me before this update, and this is just very annoying.
Atomsk said:
Any way to fix this? I am using an app called lux, but it's not perfect, still better than nothing
Click to expand...
Click to collapse
What build/baseband/firmware are you running?