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
Related
When the brightness is turned down the screen tends to flicker.
The clock jumps a head six hours periodically then jumps back. Texting is a pain when this happens because the order of the texts gets all screwed up.
I experienced these problems while running a CM 10.2 ROM too, so its not the LG Firmware.
Does anybody else experience these problems?
The brightness flickering is a known glitch of the stock software, I don't think it should persist in CM.
I haven't heard of the time bug, maybe it's a network syncing issue? Try disabling automatic date and time in settings. (Or enable if it was disabled)
Sent from my LG-VS980 using Tapatalk
I tried searching if this happens to anybody else, but couldn't find it. Since I updated to lollipop (I put original polish rom first via odin) whenever my auto brightness is turned on, when I wake the phone using home key or power button, my screen turns on with full brightness for a half second or something like that, and than goes back to normal.... I thought it was a bug on polish ROM, so I flashed austrian rom, but no improvement. Now I have custom TW rom, and it is still the same. When I turn auto brightness off, it doesn't happen. So I suspect it to be that screen turns before the light sensor on unlock, and it is set to full brightness always. is there some file I can edit, so screen starts at lowest brightness or delay screen start for half a second so the sensor can start first.
It is killing me when I get a message while sleeping in a dark room, and I want to check it, it blinds me so I wake up, and can't go back to sleep later!!!
LOL I have the same problem, which is extremely irritating to say the least, but I had no idea that it had to do with auto brightness! I am on latest AryaMod, which is stock TW based ROM, so I guess its a problem of all the TW releases?
Don't know! I will ask this in AryaMod topic and see whether dev will be more than kind to provide us a solution. Thanks for creating the topic, I had thought about it a lot of times, but was never intrigued enough.
neky92 said:
I tried searching if this happens to anybody else, but couldn't find it. Since I updated to lollipop (I put original polish rom first via odin) whenever my auto brightness is turned on, when I wake the phone using home key or power button, my screen turns on with full brightness for a half second or something like that, and than goes back to normal.... I thought it was a bug on polish ROM, so I flashed austrian rom, but no improvement. Now I have custom TW rom, and it is still the same. When I turn auto brightness off, it doesn't happen. So I suspect it to be that screen turns before the light sensor on unlock, and it is set to full brightness always. is there some file I can edit, so screen starts at lowest brightness or delay screen start for half a second so the sensor can start first.
It is killing me when I get a message while sleeping in a dark room, and I want to check it, it blinds me so I wake up, and can't go back to sleep later!!!
Click to expand...
Click to collapse
Same thing here mate. I noticed that this happens to all 5.0 rom and currently I am using ported 5.0.1 rom and it went well.
shchiam1978 said:
Same thing here mate. I noticed that this happens to all 5.0 rom and currently I am using ported 5.0.1 rom and it went well.
Click to expand...
Click to collapse
I tried flashing 5.0.1, but it didn't fix it, I also have a problem with screen not turning off during calls now, which rom are you using?
neky92 said:
I tried flashing 5.0.1, but it didn't fix it, I also have a problem with screen not turning off during calls now, which rom are you using?
Click to expand...
Click to collapse
I am using death note.
Now I am back to Arya to test the battery life.
Hi guys,
Having an issue with my Note 4 (SM-N910F) international version since the MM 6.0.1 update. I received a further update after the MM 6.0.1 recently and thought the issue would've been fixed but alas, no!
Current version of Software: N910FXXS1DPE7.
Issue is, I have power saving mode turned on and set to: Start power saving "Immediately". However it keeps getting turned off and the screen becomes bright and I could not recognise a pattern how this occurs.
Things tried so far:
-Unticked automatic brightness and dragged all the way to low.
-Smart stay was/is never ticked.
-Auto adjust screen tone is ticked, but unticking that and also leaving automatic brightness turned off still causing power saving to automatically turn off.
-I have tried to check for this issue in Safe mode and it still happens.
Any ideas of what could be causing this? I do not want to do a factor reset for this issue and if it can be avoided after all. Safe mode is somewhat similar isn't it?
I have noticed the issue occur when I start using Gmail app (not the Inbox one), but that is just one scenario.
It seems like the light sensor gets triggered when it faces bright light and turns off power saving mode and screen becomes bright, but just could be a red herring.
Thanks a million!
Bharath
corpuscallosum said:
Hi guys,
Having an issue with my Note 4 (SM-N910F) international version since the MM 6.0.1 update. I received a further update after the MM 6.0.1 recently and thought the issue would've been fixed but alas, no!
Current version of Software: N910FXXS1DPE7.
Issue is, I have power saving mode turned on and set to: Start power saving "Immediately". However it keeps getting turned off and the screen becomes bright and I could not recognise a pattern how this occurs.
Things tried so far:
-Unticked automatic brightness and dragged all the way to low.
-Smart stay was/is never ticked.
-Auto adjust screen tone is ticked, but unticking that and also leaving automatic brightness turned off still causing power saving to automatically turn off.
-I have tried to check for this issue in Safe mode and it still happens.
Any ideas of what could be causing this? I do not want to do a factor reset for this issue and if it can be avoided after all. Safe mode is somewhat similar isn't it?
I have noticed the issue occur when I start using Gmail app (not the Inbox one), but that is just one scenario.
It seems like the light sensor gets triggered when it faces bright light and turns off power saving mode and screen becomes bright, but just could be a red herring.
Thanks a million!
Bharath
Click to expand...
Click to collapse
I have just one problem like yours. When i receive Marshmallow i just update. But Power Saving turns off every reboot. Just back to factory settings and make your wipes. I solve this with wipes and factory.
Tavok said:
I have just one problem like yours. When i receive Marshmallow i just update. But Power Saving turns off every reboot. Just back to factory settings and make your wipes. I solve this with wipes and factory.
Click to expand...
Click to collapse
Thanks. Yeah I am trying to avoid factory reset because can't go thorugh the process of installing apps, setting up all the various accounts etc especially since there is no built in fully restorable backup feature. Family man with kids and have enough IT stuff to do at work.
I'm on stock/non-rooted device also. And this will be my last Samung device, if not the last Android!
I understand you very well. You can use HELIUM apk to make your nandroid backups without root and make easier this tedious work. I don't have rooted my phone but helium makes all faster that, and i use also wondershare mobile go for android and PC.
I hope this helps you and you can resolve your problem. Good luck and regards from Switzerland - (Mexico)
Tavok said:
I understand you very well. You can use HELIUM apk to make your nandroid backups without root and make easier this tedious work. I don't have rooted my phone but helium makes all faster that, and i use also wondershare mobile go for android and PC.
I hope this helps you and you can resolve your problem. Good luck and regards from Switzerland - (Mexico)
Click to expand...
Click to collapse
Thanks Tavok. I did download Helium and wanted to test it out, however my phone is now staying in Power Saving mode since a few days! I have done nothing new, didn't uninstall any app or change any settings as such for it to work. This is bugging me because I want to know what fixed it so that I can re-apply the fix again if need be.
I've also read that some people are complaining about Note 4 getting stuck in Power Saving mode and I hope this is not the case with mine, now that it seems to work as expected.
I will update this thread once I check it out further.
I found out how this power saving mode gets turned off. It is the Location settings. If location is off, the power saving mode stays on (this is what it was set to hence I didn't see the issue happening). But when I changed it back to High accuracy, I started to notice the power saving getting turned off from time to time when using certain applications that require Location accuracy.
This is a bug since the MM update!!
Any ideas how to use Location accuracy and still retain Power saving mode?
I did a factory reset and the issue persisted! I tried various location settings(of the 3 choices) asks none of them helped. When set to any one of them power saving automatically turns off after a while I.e. when location needs to be detected. The only workaround us to turnoff location altogether but that messes with the auto sync of accounts! Grrrrrrrr
I verified with Samsung Tech Support that Location and Power Saving are incompatible on the Galaxy Note 4, even with the latest Android version available for the device (6.0.1) . In other words, Turning on Location while Power Saving is active will disable Power Saving after a short period. Fortunately, the problem is fixed on later devices.
Hi there, so I updated my ph-1 to the latest Oreo 8.1 earlier this morning and have been experiencing significant delays when unlocking my screen. Sometimes the phone did not respond at all and the screen just stayed black. I had to restart the phone in such cases. Help! I seem to be the only essential phone user in entire Sydney
If you're using immersive mode, that might be the issue. Try disabling that, and see if the issue persists.
I'm experiencing the same. Setting immersive mode to None does help a bit, but it's still not as snappy as before.
And after all the same settings worked perfectly on the 8.1 beta.
Tried to go back, but on official 8.1 the recovery mode only says "no command"....
I am experiencing the same issue too. It doesn't have the delay problem right after reboot, it seems like it delays the unlocking when the phone has been in idle for a while.
And specialty if you use immersive mode with sytem UI make it very long delay
winstonxyz said:
I am experiencing the same issue too. It doesn't have the delay problem right after reboot, it seems like it delays the unlocking when the phone has been in idle for a while.
Click to expand...
Click to collapse
Same issue here. Sometimes takes so long to unlock that I am unable to answer a phone call that comes in before it goes to Voicemail. Usually happens when the phone has been idle for a while.
Update:
Did the dreaded FDR (factory data reset). Installed the "Tiles" app from plasystore and ran the noted adb command to allow immersive mode, tile display, and enable write secure settings permissions. I chose the action to hide the navigation bar within the Tiles app. I ignored the setting to stop on sleep so the app keeps running when the phone screen goes off. In testing it for about an hour the phone seems to unlock without any issue for now and without any delay. I also made phone calls while the phone screen was off and I was able to answer the call easily. So far so good using the Tiles app!
sounds like the expanded desktop Oreo issue. There's a Xposed module DeepScreen Oreo for it.
Hi auto-rotate and auto-brightness stopped working after update, i am not sure if it was August or September Update.
When i noticed, the first thing i did, i reboot the device, and nope, it still didn't work.
I google searched about the issue, but not to much around the internet about this bug or problem.
Someone is saying to check any app that i installed lately,, but i didn't install anyone to be honest. I also cleared the Cache Partition but still , no success.
For the moment i am using an app to controll rotation of the screen, Rotate Control, and the brightness, i adjust it manually.
It will be very helpful if anyone can help me with this.