First of all id like to thank everyone involved with the port of CM7, it was done extremely well but i did run into an issue and i was wondering if anyone can help?
I successfully flashed the rom and all was well until i attempted to adjust my screen brightness, no matter what i do my brightness will not change... its currently stuck at a very low level and is becoming very inconvienent. I tried also using third party brightness widgets like power control to no avail.
Any ideas or suggestions are greatly appreciated.
Thanks
FanDroid09 said:
First of all id like to thank everyone involved with the port of CM7, it was done extremely well but i did run into an issue and i was wondering if anyone can help?
I successfully flashed the rom and all was well until i attempted to adjust my screen brightness, no matter what i do my brightness will not change... its currently stuck at a very low level and is becoming very inconvienent. I tried also using third party brightness widgets like power control to no avail.
Any ideas or suggestions are greatly appreciated.
Thanks
Click to expand...
Click to collapse
Im not the best to say that, but I think we have to wait till next release, every time there is a new release something is fixed.
Be patient!
Related
I've been using the Yuki Back to the Future 2.1 rom now for a couple of days, and I am really impressed! The only thing that still annoys me, how can the lights of the hardware buttons be dimmed when the screen is turned off? I have updated to the latest WM7 and applied the SP1 service pack. It isn't much of a problem, but I can imagine it takes some energy, especially at night.
I tried to search as best as I could but I couldn't find an answer, I hope you guys can help me. Thanks in advance!
Hi XDA,
I have a serious problem with my Galaxy Note: Every night I put the note in the docking station to charge it - and every night i get woken up by the note's display which tells me "Charging complete".
Is there any way to prevent / disable this? I had this phenomenon on Stock and now on KingDroid Notemania mod. I once read something (just can't find it anymore) when I was still on stock which helped about 95% of the time (some file was deleted). Anyone know a solution for this?
Thanks so much in advance!
Greetz,
Mad
Madman1209 said:
Hi XDA,
I have a serious problem with my Galaxy Note: Every night I put the note in the docking station to charge it - and every night i get woken up by the note's display which tells me "Charging complete".
Is there any way to prevent / disable this? I had this phenomenon on Stock and now on KingDroid Notemania mod. I once read something (just can't find it anymore) when I was still on stock which helped about 95% of the time (some file was deleted). Anyone know a solution for this?
Thanks so much in advance!
Greetz,
Mad
Click to expand...
Click to collapse
there are a lot of postings regarding this, please use the search function!
simplest way: if you are rooted, delete the according sound file!
Hi,
thanks for the advice TML1504, but as I said: it didn't help all of the time. Sometimes, even when I deleted the soundfile, it kept happening. That's why I wanted to know if there is any other solution for this "problem". Also, I didn't really find any solution here in the forum (maybe I've been using the wrong keywords). Could you help me out? "Screen turns on after charge" didn't really get me the results that help me.
Thanks anyways,
Mad
just google for "galaxy note disable charged notification", i'm sure one of the methods will work! also, if you remove the correct file the notification WILL be gone! regards
Hi again,
Thank you, with those search results I did it last time. maybe it was just a coincidence it did not work out all the time. I was messing around with a lot of different roms back then
Thanks again,
Mad
Hi again,
went well for a couple of days (or at least I did not notice), but this night, around 4 o'clock my Note went bright as day an told me, charging was completed. So the soundfile I renamed "/system"media/audio/ui" "TW_Battery_caution.ogg" to "TW_Battery_caution.old" (like I found on Google with your advice) did NOT solve the problem.
Anyone else have any idea on how to fix the screen flashing up in the docking station when charging is completed?
Greetz,
Mad
I 'fixed' it by installing an app called Dock Clock from the store and so I get a nice bedside clock with a not-too-bright display instead. The app can be set to fire up automatically if the phone is put in a charging dock during a set time period.
Hi,
thanks for your reply!
Does this app really prevent the display to go bright when charging is finished? Could it really be that easy?
I'm already reading post's about decompiling SystemUI.apk and changing certain values. But those are obviously obsolete in ICS and only valid for Android 2.2...
Greetz,
Mad
Madman1209 said:
Hi,
thanks for your reply!
Does this app really prevent the display to go bright when charging is finished? Could it really be that easy?
I'm already reading post's about decompiling SystemUI.apk and changing certain values. But those are obviously obsolete in ICS and only valid for Android 2.2...
Greetz,
Mad
Click to expand...
Click to collapse
Give it a try
Use No Moar Power by Chainfire. You can charge the phone with the device off and set a time you want the device to turn back on, aka right before your alarm goes off.
Hi,
@linker3000
I'll do
@Note_E
No, that doesn't help because I want to be able to get (emergency) calls, so I need my device powered on. But thanks for the suggestion anyway!
I don't understand why Samsung would sell this as a "feature" and not make it optional...
Greetz,
Mad
I wonder if you turned the phone so the screen was facing down, would the proximity sensor stop the screen from coming on.
Or try covering the sensor with the screen facing up and see what happens.
John.
I have noticed my screen changing brightness depending on how bright the picture is on the page. A good example is reddit, when on the home page the screen slowly steps up its brightness so far, after clicking a link to an image or other dark website the screen slowly steps down the brightness. It does this regardless of what the screen brightness is set at as I have tried different values and on auto and it always does it. Anyone else have this problem or have a solution?
Thanks,
Mike.
The best questions never get answered...
Sent from my Nexus 7 using XDA Premium HD app
Possibly not a solution, but I use this free app
https://play.google.com/store/apps/...SwxLDMsInNvZnQua2lub2tvLnNldGJyaWdodG5lc3MiXQ..
I set mine to 20% and just leave it alone, I never use auto.
I have the same problem at Paranoidandroid 2.99.
None of the above worked.
Anyone else have an idea?
Bump, still got the problem
I think the TV light makes a difference to the Nexus 7 brightness, as the TV alternates between bright and dark lighting.
I read my Nexus 7 without glasses, and so I can hold it very close to my face thanks to my short sightedness. This means the Nexus 7 screen light reflects off my face and affects the autobrightness. I suspect that black warpaint smeared on my face might be a solution.
But the real solution should be simple - Google need to average out their sensor readings and transition screen brightness changes smoothly and less frequently.
Sent from my Galaxy Nexus using xda premium
Not sure if it will help, I use
https://play.google.com/store/apps/details?id=mobi.pruss.superdim
Unfortunately none of these solutions have worked.
It does not seem to matter whether or not the screen is close to my face and thus sees the reflection, I can do it in a constantly bright room with nothing in front of the device and I still have this weird change in brightness.
Any more ideas?
Thanks,
Mike.
MikeyUK said:
Unfortunately none of these solutions have worked.
It does not seem to matter whether or not the screen is close to my face and thus sees the reflection, I can do it in a constantly bright room with nothing in front of the device and I still have this weird change in brightness.
Any more ideas?
Thanks,
Mike.
Click to expand...
Click to collapse
Hi, MikeyUK...
I had the same problem myself for a long time, until I stumbled on this..
http://forum.xda-developers.com/showthread.php?t=1815414
It describes the cause, and offers a solution... unfortunately, it does require you to be rooted though,.. but it worked, (at least, it works for me)... no more screen brightness fluctuations.
Rgrds,
Ged.
GedBlake said:
Hi, MikeyUK...
I had the same problem myself for a long time, until I stumbled on this..
http://forum.xda-developers.com/showthread.php?t=1815414
It describes the cause, and offers a solution... unfortunately, it does require you to be rooted though,.. but it worked, (at least, it works for me)... no more screen brightness fluctuations.
Rgrds,
Ged.
Click to expand...
Click to collapse
Thanks for the response. However, I would like to keep my device unrooted if at all possible. At this rate I might try and return it to the store because it is not right. Another family member has the same device with no problem which makes me a little bit suspicious.
Thanks,
Mike.
Good day people. I recently got the Note 3 and realized this annoying bug. I used the note 2 previously and turned off 3 developer options to make it run faster: "Window Animation Scale", "Transition Animation Scale" and "Animator Duration Scale". However when I turned the 3 options off on my note 3, after some time, the "Transition Animation Scale" will turn itself back on to the default of 1X. The other 2 options remain off. This "Transition Animation Scale" bug is really annoying and I wish to seek help on this matter. Thanks in advance.
anyone?
please help someone?
Steps to reproduce?
Played around with it for 2-3 hours and I wasn't able to reproduce the issue, Which model are you using, what method did you use to root. Is there a particular amount of time that leads to the Transition Scale reverting or is it possibly when the device is rebooted.
Being unable to reproduce so far I am guessing it's one of three things off the top of my head:
A system application is triggering a conflict requiring the default value.
The change is not being saved in a persistent state (reboot clears it)
A Timeout based on the setting not being applied as the file is in use ? (It's a long shot maybe reboot after change?)
See if you can't narrow down when the setting is returning to default so others can reproduce.
insanepoet said:
Played around with it for 2-3 hours and I wasn't able to reproduce the issue, Which model are you using, what method did you use to root. Is there a particular amount of time that leads to the Transition Scale reverting or is it possibly when the device is rebooted.
Being unable to reproduce so far I am guessing it's one of three things off the top of my head:
A system application is triggering a conflict requiring the default value.
The change is not being saved in a persistent state (reboot clears it)
A Timeout based on the setting not being applied as the file is in use ? (It's a long shot maybe reboot after change?)
See if you can't narrow down when the setting is returning to default so others can reproduce.
Click to expand...
Click to collapse
okay i tried turning off "adaptive display" and it actually remained good for many hours. however after i used the camera, the same "Transition Animation Scale" bug appeared again. my device is SM-N9005 and not rooted whatsoever.
ok im quite sure the culprit is the camera. when i change the camera mode from beauty face to auto, then i quit camera and open it again it will switch back to beauty face. how to fix this camera memory problem please? which in turn will fix the Transition Animation Scale
somebody please check this out. it's a very apparent bug............... HELP
please anybody help?
still searching for answers. it's confirmed the camera is the one causing this. anybody got a fix?
sirbljm said:
somebody please check this out. it's a very apparent bug............... HELP
Click to expand...
Click to collapse
Same here, it should be a bug in the firmware. Apparently reading mode only works with adapt display and not the other 3 screen mode which is a bug too! Camera mode also lacks of Night mode which is available in S4
First off relax, demanding help will get you no where especially when you are dealing with a brand new device and an issue that has not been dealt with before.
I'm glad to see you found the camera app is the culprit, i can take a look at it tomorrow and see if I can't find a workaround for the problem. Working on a stock base however our options may be limited. If you are able to reproduce the bug on demand I would also send a report to samsung dot com / support just to get it on their radar (Not saying it will help but hiccups like this usually get addressed in OTA's).
If you have a chance to check before i get back to you see if the change is effected by a reboot (i.e. change settings, reboot, verify settings) might require root to fix the bug. As well can you try another camera app and see if the problem occurs (will let me know if it is something being called from the built in camera apk).
Hopefully we'll get this sorted for you and anyone who runs into it in the future.
insanepoet said:
First off relax, demanding help will get you no where especially when you are dealing with a brand new device and an issue that has not been dealt with before.
I'm glad to see you found the camera app is the culprit, i can take a look at it tomorrow and see if I can't find a workaround for the problem. Working on a stock base however our options may be limited. If you are able to reproduce the bug on demand I would also send a report to samsung dot com / support just to get it on their radar (Not saying it will help but hiccups like this usually get addressed in OTA's).
If you have a chance to check before i get back to you see if the change is effected by a reboot (i.e. change settings, reboot, verify settings) might require root to fix the bug. As well can you try another camera app and see if the problem occurs (will let me know if it is something being called from the built in camera apk).
Hopefully we'll get this sorted for you and anyone who runs into it in the future.
Click to expand...
Click to collapse
Dear Sir Poet. I have done what you instructed me to do, I applied the same developer options settings, rebooted the phone and the settings were verified good.
However, the moment after I use the Camera app, the "Transition Animation Scale" turns on by itself again. I have tried using third-party camera apps and they do not affect the settings in developer options.
It is therefore very very obvious that the Default Camera is causing this instability in developer options settings.
Sir, kindly help us feedback to Samsung regarding this issue so that they will release an OTA update fix.
Your continual help in solving this problem is greatly appreciated. Thank you so much.
sirbljm said:
when i change the camera mode from beauty face to auto, then i quit camera and open it again it will switch back to beauty face. how to fix this camera memory problem please?
Click to expand...
Click to collapse
is this happening to the rear or front camera?
the default for the rear is auto while the default for the front is beauty.
sirbljm said:
Dear Sir Poet. I have done what you instructed me to do, I applied the same developer options settings, rebooted the phone and the settings were verified good.
However, the moment after I use the Camera app, the "Transition Animation Scale" turns on by itself again. I have tried using third-party camera apps and they do not affect the settings in developer options.
It is therefore very very obvious that the Default Camera is causing this instability in developer options settings.
Sir, kindly help us feedback to Samsung regarding this issue so that they will release an OTA update fix.
Your continual help in solving this problem is greatly appreciated. Thank you so much.
Click to expand...
Click to collapse
Dear Sir Sirbljm
You are a very pushy bloke mate.. go report this problem to Samsung yourself dont tell poet to do it.. sheesh !
He doesent even have the problem! :silly:
We all have problems with early firmware.. I have a rebooting issue.. but I'm patiently trying to fix it myself while conversing with others patiently about a workaround.. eitherway I know that my GS4 was rubbish with the first firmware..
it'll get better. be patient.
tested and reproduced the same effect.
confirmed that starting the camera (regardless of front or rear)will reset the transition animation scale to 1x.
Fade777 said:
Dear Sir Sirbljm
You are a very pushy bloke mate.. go report this problem to Samsung yourself dont tell poet to do it.. sheesh !
He doesent even have the problem! :silly:
We all have problems with early firmware.. I have a rebooting issue.. but I'm patiently trying to fix it myself while conversing with others patiently about a workaround.. eitherway I know that my GS4 was rubbish with the first firmware..
it'll get better. be patient.
Click to expand...
Click to collapse
sorry man. it's just that i'm new to this and i don't even know how to report the matter to samsung. was hoping somebody who is more experienced can help me out that's all. i'm sure it'll get better, i'll be patient.
cfchong said:
tested and reproduced the same effect.
confirmed that starting the camera (regardless of front or rear)will reset the transition animation scale to 1x.
Click to expand...
Click to collapse
thank you Corporal First Class Hong. at least i now know i'm not alone in this. :fingers-crossed:
I get the same transition animation bug. It turns on (1x) by itself after I set it to 0.
lferrante said:
I get the same transition animation bug. It turns on (1x) by itself after I set it to 0.
Click to expand...
Click to collapse
I'm getting the sam bug..
Just for the record..
It'll get fixed.. this isn't that annoying
My reboot problem.. now that... that is annoying.
Sent from my SM-N9005 using Tapatalk 4
waiting for a fix for this
has anyone figured out how to make this stop? The animation scale changes every time the camera is opened. Pretty annoying if you use your camera often
Hi guys,
I have to fire 7 in tablets both bought at the same time from same place. Both are running the same Lineage-12.1 ROM (12.1-20170802-Unofficial-ford)
But for some reason when i keep them side by side one of them has a very dull screen brightness where as the other is nice and visible. I am not sure if this has to do with the hardware or some missing setting in the one that is dull. I tried making both 100% bright from the upper menu but the screen difference is still the same.
The bottom image is the brighter one. Any idea if some setting somewhere is causing this?
Thansk
matt
amti366 said:
Hi guys,
I have to fire 7 in tablets both bought at the same time from same place. Both are running the same Lineage-12.1 ROM (12.1-20170802-Unofficial-ford)
But for some reason when i keep them side by side one of them has a very dull screen brightness where as the other is nice and visible. I am not sure if this has to do with the hardware or some missing setting in the one that is dull. I tried making both 100% bright from the upper menu but the screen difference is still the same.
The bottom image is the brighter one. Any idea if some setting somewhere is causing this?
Thansk
matt
Click to expand...
Click to collapse
On checking further I noticed that the tablet which is showing dull color seems to show the exact same even when I adjust the brightness slider in the top menu. When the slider is on 0 or 100% its the same. that tells me that the software slider is somehow broken?
amti366 said:
On checking further I noticed that the tablet which is showing dull color seems to show the exact same even when I adjust the brightness slider in the top menu. When the slider is on 0 or 100% its the same. that tells me that the software slider is somehow broken?
Click to expand...
Click to collapse
Known kernel issue with custom ROMs. Symptoms typically rectified with a reboot. If no joy try a full power down with a 5 sec pause before restarting.
Davey126 said:
Known kernel issue with custom ROMs. Symptoms typically rectified with a reboot. If no joy try a full power down with a 5 sec pause before restarting.
Click to expand...
Click to collapse
Sorry for the late response Davey126, for some reason it didn't post my reply when I used my cell phone the other day. I tried to restart a few times but still have the same screen issue the brightness controls dont respond. Will upgrading to the latest release help with this issue? Is there any other fix to permanently fix the problem?
Thanks for your help.
thanks,
Matt
amti366 said:
Sorry for the late response Davey126, for some reason it didn't post my reply when I used my cell phone the other day. I tried to restart a few times but still have the same screen issue the brightness controls dont respond. Will upgrading to the latest release help with this issue? Is there any other fix to permanently fix the problem?
Thanks for your help.
thanks,
Matt
Click to expand...
Click to collapse
Probably not. Likely have to sideload a full version of FireOS to refresh/replace the kernel - then start over. There is no known 'fix' for the problem other than keeping memory load to a minimum (or using the swap tweaks that I outlined elsewhere).
Davey126 said:
Probably not. Likely have to sideload a full version of FireOS to refresh/replace the kernel - then start over. There is no known 'fix' for the problem other than keeping memory load to a minimum (or using the swap tweaks that I outlined elsewhere).
Click to expand...
Click to collapse
Ok thanks for your help Davey126