I have the i717 from rogers and currently running the cm9 official rom but it doesnt seem to matter what rom im on I see this werid fluttering brightness thing occurring on any rom. Try my best to describe it, it is like its almost fluttering up or down in brightness levels when about to dim or undim I am wondering if this is maybe a hardware issue with my device that I should get serviced or if it is normal?
bradtn said:
I have the i717 from rogers and currently running the cm9 official rom but it doesnt seem to matter what rom im on I see this werid fluttering brightness thing occurring on any rom. Try my best to describe it, it is like its almost fluttering up or down in brightness levels when about to dim or undim I am wondering if this is maybe a hardware issue with my device that I should get serviced or if it is normal?
Click to expand...
Click to collapse
I was going to ask what rom .but then had a thought regarding the light sensor on the device .
And I remember reading about sensor calibration and possible causes of fluctuations .
I suppose a search would find that for you ...but check this also ...
Display settings in cm allow light to decrease ...it's a hysterisis setting ...(I butchered that word )
And the settings control flicker in the display . You might try turning those off .
Next is the power saver settings which allow a light decrease also ..after a few seconds of no screen touch ,the light level drops too save power .
And third ...turn off your automatic light level setting in display settings .
I'm thinking three items are conflicting a bit and some mild tuning will fix it ...g
This ROM is working very well on my UK Rhod 100. Very stable & fast and since the latest update I have the correct HW keyboard layout. Battery life is limited but carrying a second battery is an easy solution.
The previous problems where the screen would not turn on after several pushes of the power button almost never occurs. However when the battery runs down to about 30% the screen always changes such that a red overlay occurs visible mainly on screens with a white background (see pics). Also when the screen changes ghost images remain from previous screens. Also at this point sometimes the screen will not turn on despite repeated use of the power button. Strangley, even though there is nothing visible on the screen I can unlock the phone by swiping in the expected area (and get haptic feedback) and long press the power button and turn off the device by pressing in the expected areas. Upon a reboot the screen will initially be back to normal but then if the battery is below 30% the problem will return. These issues never occur if the battery is above 30%. If I take screenshots with shootme the pics captured look normal when viewed after a reboot before the problem recurs. Not sure what the system does when the battery falls to this level but the screen is definitely affected. This problem also occurs with a fresh install with no apps installed.
If anyone has any ideas as to what could be the cause (and even better a solution) it would be most welcome. Thanks to all those behind this project.
Sorry you are having troubles. Unfortunately as noted in the first post for that thread we only have RHOD400s to test with. No one else has reported any similar issues. The 100s are known to be the problem children of the RHOD family. If you come up with a fix let us know, and we will try to include it in any future releases.
wizardknight said:
Sorry you are having troubles. Unfortunately as noted in the first post for that thread we only have RHOD400s to test with. No one else has reported any similar issues. The 100s are known to be the problem children of the RHOD family. If you come up with a fix let us know, and we will try to include it in any future releases.
Click to expand...
Click to collapse
Did you look at ACL's work on RE'ing that panel code...?
He said something about the panel power up/power down sequence on the 100's (the AUO panel specifically) to be quite a bit different.
arrrghhh said:
Did you look at ACL's work on RE'ing that panel code...?
He said something about the panel power up/power down sequence on the 100's (the AUO panel specifically) to be quite a bit different.
Click to expand...
Click to collapse
arrrghhh, I noted your post in the ROM development thread regarding the start up sequence in the OMGB kernel for the AUO panel. Perhaps this would solve my issue as well. If this change could be added to the next edition of this ROM my device would be virtually bug free.
As noted in the thread, we do not have any RHOD100s to test with. It is very unlikely that this will happen. If you would like to make your own kernel with these changes I can post it.
issue or not?
hi,
thanks a lot, first of all.
I've been trying to figure out how to get an Italian keyboard layout.
any suggestion?
-p.
paolora999 said:
hi,
thanks a lot, first of all.
I've been trying to figure out how to get an Italian keyboard layout.
any suggestion?
-p.
Click to expand...
Click to collapse
try using AItype Keyboard Plus which supports multiple languages and keyboard layouts
Sorry I didn't express myself properly. I meant the physical keyboard. In other thread I read something about a startup.txt file, I don't know if it applies to this ROM (and moreover I can't find it).
paolora999 said:
Sorry I didn't express myself properly. I meant the physical keyboard. In other thread I read something about a startup.txt file, I don't know if it applies to this ROM (and moreover I can't find it).
Click to expand...
Click to collapse
startup.txt files are only for the SD card versions of the android roms.
You would need to edit the keyboard map. Here is generic android keyboard map info.
There may be apps out there than can change your keyboard map, but I don't know any details about that.
Also in the future it would be best to start your own thread, rather than using an unrelated one. Better yet, post the questions about the rom you are working with in the thread for that rom.
i am having also a screen problem with that Rom and Kernel:
My screen is not calibrated. When i press it's being pressed on somewhere else on the screen.
P.S.
My RAM is not 100 +- this rom showing me 33 for usage on the device :S.
Can someone help me with those two ?
MTN_Cool said:
i am having also a screen problem with that Rom and Kernel:
My screen is not calibrated. When i press it's being pressed on somewhere else on the screen.
P.S.
My RAM is not 100 +- this rom showing me 33 for usage on the device :S.
Can someone help me with those two ?
Click to expand...
Click to collapse
Did you read the link that covered screen calibration listed under related goodies, or did you search for the threads that cover screen calibration under android? Tell us what you have tried, but didn't work.
No idea what you mean by the ram is not 100.
What the heck is going on here? Is this just the thread to jack?
Let's focus on the display issues please folks, as in your response should be related to the original post.
arrrghhh said:
What the heck is going on here? Is this just the thread to jack?
Let's focus on the display issues please folks, as in your response should be related to the original post.
Click to expand...
Click to collapse
idc if they will move my question the the original one...
but i can't fix my calebration points...every time i need to launch the HTC program :\
Problem resolved?
akk29 said:
This ROM is working very well on my UK Rhod 100. Very stable & fast and since the latest update I have the correct HW keyboard layout. Battery life is limited but carrying a second battery is an easy solution.
The previous problems where the screen would not turn on after several pushes of the power button almost never occurs. However when the battery runs down to about 30% the screen always changes such that a red overlay occurs visible mainly on screens with a white background (see pics). Also when the screen changes ghost images remain from previous screens. Also at this point sometimes the screen will not turn on despite repeated use of the power button. Strangley, even though there is nothing visible on the screen I can unlock the phone by swiping in the expected area (and get haptic feedback) and long press the power button and turn off the device by pressing in the expected areas. Upon a reboot the screen will initially be back to normal but then if the battery is below 30% the problem will return. These issues never occur if the battery is above 30%. If I take screenshots with shootme the pics captured look normal when viewed after a reboot before the problem recurs. Not sure what the system does when the battery falls to this level but the screen is definitely affected. This problem also occurs with a fresh install with no apps installed.
If anyone has any ideas as to what could be the cause (and even better a solution) it would be most welcome. Thanks to all those behind this project.
Click to expand...
Click to collapse
In an attempt to bring this thread back on topic I thought I'd report back that the original problem has not happened for a few weeks. My setup is essentially unchanged, the only change is that I have been using One Power Guard to try and improve battery life, which by the way seems to be effective. Managed 13hours with light use (few calls/occassional data for email web browsing)
Anyway it could be coincidence but it is possible that one of the tweaks performed by the app has sorted this issue. Since nobody else has reported the same problem I'm not sure how useful this info is but hopefully it may be of use to someone.
Hello XDAers, although I'm a new member I have been digging this community for quite a while
Anyway, I have searched for this but couldn't find a relevant thread..
Can anybody please add a feature which forcefully enables the brightness control bar in notification panel of samsung phones when battery drops below 5%? As by default after 5% brightness cannot be controlled in sammy ROMs.
Probably an Xposed Module can fix this.
The feature is only present in the GS3..and there must be a simple file requiring editing to remove/edit the code for brightness control below 5% battery. If anybody has any info for which file is responsible for this effect, please let me know so I can create a fix for this and post a module myself.
Come on..No replies to such a primitive problem?
Sent from my GT-I9100
Maybe send a p.m to all developers telling them how important it is.
Same problem on a Note 3 SM 9005. Solution needed
Hi guys - I have the same problem - on a Note 3 SM9005 running Android 4.4.2.
It's really an annoyance - we need a tweak to enable setting the brightness with battery below 5%!
Many TIA
Gail
I'm using Motorola Moto E(condor), I had automatic restart problem in my stock ROM, later I unlocked the bootloader and installed custom ROM, I had been using custom ROM for months, Now suddenly when I changed the ROM My mobile's brightness has become low, Even bootloader brightness is low, and now if i enable auto brightness and move the brightness slider to 25% its becoming darken(unable to view anything). So I changed to Stock ROM, but the problem still exists.
Help me out please......
:crying::crying::crying::crying:
Same problem here. Any luck finding a solution?
Flash this maybe your brightness will increase.
http://forum.xda-developers.com/android/software/mod-xtremevideo-media-youve-seen-t3174158
Though I think it might be a hardware related problem.
Hi guys,
I'm in love with my Honor 9 (and with my girlfirend obviously, she's standing right there when I'm writing this post ) BUT there are some issues.
1) The auto-brightness isn't working as it should. Previously I had G3 and the auto-brightness was amazing but with Honor 9 it seems to do whatever the phone wants or what. I'm outside on the sunny day, want to take some photos but the screen is on it's minimal brightness and reacts very slowly or not at all and when I move the slider to the point of max brightness the screen is still darker than it should be (I got the max brightness when I turn off the auto-brightness only). Overall the auto-regulation is sh*t. Do you have the same issue?
2) From what I found this is a well known bug with auto-brightness. The screen is dimming when I open some apps like GMail, Chrome etc. and it's really annoying. Overall the brightness is wierd and even with the auto-regulation off and display on max brightness is dimming sometimes. This should be problem with the EMUI 5.x so I have three questions. Do you have the the same issue? Does B130 solve this (I wasn't lucky to install it and now I can't find it, phone says B100 is the most recent version - they stopped the update?)? Does any of custom ROM's solve this?
Thanks a lot.
I'm on stock ROM B100, EU version, CZE.
That happens with almost any Honor device with nougat (EMUI 5)
In other words, they don't give a fu*k right?
It seems so
Thought so. Can it be solved with other ROM?
I don't know, I've never tested a custom ROM on honor 9