Hey Ive seen issues with people having trouble with the distribution of LEDs on the keyboard with not seeing keys and others to bright and thats not me haha. I was wondering though if anybody knew a registry hack or something that would let the backlight on the keyboard stay on longer than 5 seconds? That is the biggest annoyance of this phone that ive seen so far.
aaron580 said:
Hey Ive seen issues with people having trouble with the distribution of LEDs on the keyboard with not seeing keys and others to bright and thats not me haha. I was wondering though if anybody knew a registry hack or something that would let the backlight on the keyboard stay on longer than 5 seconds? That is the biggest annoyance of this phone that ive seen so far.
Click to expand...
Click to collapse
Do a search for a utility called Advanced Config, it has a setting to change the backlight timeout, among a lot of other things. You'll need to have the ARM4i version of ppc .NET 3.5 installed also.
BEWARE: Use the tool at your own risk. Don't turn menu animations and start menu animations on, as it has caused my start menu to go really wonky (all the colors are jumbled and its impossible to read) Turning this off made it behave as expected. Just a warning
Hey thanks man. I didnt even know that setting was in advanced config and ive used since the mogul lol.
Doesnt work
I have tried the tweak in advanced config and nothing changed, has anyone else had luck with this?
oldquser said:
i have tried the tweak in advanced config and nothing changed, has anyone else had luck with this?
Click to expand...
Click to collapse
it can not be changed
This is one of the most annoying things about the TP. Anytime you pause for 5 seconds the keyboard backlight goes off! Grrr!
No kidding. I completely disabled the light sensor on my P4000, it was always on as long as the slider was open. I even watched an hour long episode of top gear while I sat in a Mazda dealership while having an oilchange done on my car.
I too have been equally frustrated with this. With no solution in sight, I think I might have thought of a program that could save our sanity. The only problem is that i've only THOUGHT of it and it doesn't exist yet. I've started a thread in the 'Development and Hacking' section. Here's the link http://forum.xda-developers.com/showthread.php?t=490267
Add comments, add ideas, just add support
Related
I did a search on PPCGeeks, XDA, and Google, and couldn't find any app to make the touch screen on the Titan interactive - similar to the way the Voyager touch screen works (quick vibrate when the screen is touched).
Is there any app like this? If not, can someone make one?
Thanks!
You would think HTC being one (if not THEE one) #1 Smartphone manufacture that would have SOMETHING similiar to the iphone or Voyager. The HTC Cube to me is very "amatuer" looking compared to the iphone and Voyager UI. Even microsoft couldn't make anything similiar...hopefully WM7 will blow us away.
I agree that the Cube looks pretty basic (that's why I won't put it on my phone, but I do have the TouchFLO).
But what I'm looking for is for the phone to do a very quick vibrate whenever the screen is touched.
That technology is called Haptics and it is much more than just the phone vibrating. Haptics allows you to physically feel a vibration exactly on the spot of the screen you are touching. Your phone has to have Haptics vibration built into it to use it and there isn't a single HTC phone out there using the said technology.
http://www.immersion.com/corporate/press_room/what_is_haptics.php
worth a shot
vaxick said:
That technology is called Haptics and it is much more than just the phone vibrating. Haptics allows you to physically feel a vibration exactly on the spot of the screen you are touching. Your phone has to have Haptics vibration built into it to use it and there isn't a single HTC phone out there using the said technology.
http://www.immersion.com/corporate/press_room/what_is_haptics.php
Click to expand...
Click to collapse
Indeed.
That said, I'm still interested in any app that does simply what whiteblazer01 asked for. I'm always looking over my fingers when I'm trying to dial a phone number. I'd be willing to give a simple touch-response app a shot.
Anyone?
ryanshepherd said:
Indeed.
That said, I'm still interested in any app that does simply what whiteblazer01 asked for. I'm always looking over my fingers when I'm trying to dial a phone number. I'd be willing to give a simple touch-response app a shot.
Anyone?
Click to expand...
Click to collapse
I have been looking into this also. Especialy when i use the media player or just the main screen shortcuts.
In the mean time I was able to find a CAB somewhere in this forum that enables vibration feedback when you dial a number. It replaces the tone with vibration. I hope you guys like it. (Sorry I dont have support for it because I am not the original creator of this CAB)
Make sure that once you install the CAB that you soft reset after.
Hope you like it.
That's exactly what it is - Haptics. Thanks for the link. The program [email protected]$ put a link to (thanks!) works on the keypad, but it really doesn't feel like the Haptics system. O well, its still cool though.
I found a link to another thread on this forum for the same thing. http://forum.xda-developers.com/showthread.php?p=1685449
whiteblazer01 said:
That's exactly what it is - Haptics. Thanks for the link. The program [email protected]$ put a link to (thanks!) works on the keypad, but it really doesn't feel like the Haptics system. O well, its still cool though.
I found a link to another thread on this forum for the same thing. http://forum.xda-developers.com/showthread.php?p=1685449
Click to expand...
Click to collapse
I was thinkin about how we can make the phone vibrate when we tap the screen in any application instead of only the dial pad.
I came up with a theory that might give us some type of haptics feed back. It might not be exactly like haptics but it could make the phone vibrate.
There is a feature in our phone that can enable the phone to play a sound when we tap the screen for any reason. I was thinking why not replace the sound with just vibration like the CAB that changes the sound to vibration on the dialer?
Im not experienced at programming, but I am willing to take a shot into making this possible. Maybe some one can get a hold of a good programmer or some one good at registry tweaks to make this possible.
Just an idea
steps said:
You would think HTC being one (if not THEE one) #1 Smartphone manufacture that would have SOMETHING similiar to the iphone or Voyager. The HTC Cube to me is very "amatuer" looking compared to the iphone and Voyager UI. Even microsoft couldn't make anything similiar...hopefully WM7 will blow us away.
Click to expand...
Click to collapse
Voyager is hella gay
[email protected]$ said:
I have been looking into this also. Especialy when i use the media player or just the main screen shortcuts.
In the mean time I was able to find a CAB somewhere in this forum that enables vibration feedback when you dial a number. It replaces the tone with vibration. I hope you guys like it. (Sorry I dont have support for it because I am not the original creator of this CAB)
Make sure that once you install the CAB that you soft reset after.
Hope you like it.
Click to expand...
Click to collapse
Great Idea [email protected]$, deffinately move forward with it, Ive been using the phonepadvibrate (essentially the same as what you posted) for well over 2 months now and love it. If you could do the same with the normal touch screen it would be amazing.
Yes its not full haptics, but in my opinion it really doesnt need to be. some sort of physical feedback (ie a slight vibration) would be great when working with the touch screen.
[email protected]$ said:
I was thinkin about how we can make the phone vibrate when we tap the screen in any application instead of only the dial pad.
I came up with a theory that might give us some type of haptics feed back. It might not be exactly like haptics but it could make the phone vibrate.
There is a feature in our phone that can enable the phone to play a sound when we tap the screen for any reason. I was thinking why not replace the sound with just vibration like the CAB that changes the sound to vibration on the dialer?
Im not experienced at programming, but I am willing to take a shot into making this possible. Maybe some one can get a hold of a good programmer or some one good at registry tweaks to make this possible.
Just an idea
Click to expand...
Click to collapse
Carlos, I definitely agree, I would love to have that whenever the screen vibrated. Although, I don't know who would be willing to do that. I remember when I had the Apache (XV6700), I thought it would be cool if someone could make the LED lights on top into indicator lights for the shift and caps keys - which never happened (I don't know how, otherwise I would do it myself).
In fact, I wonder if someone can make a cab to have the shift and caps buttons make the indicator lights turn on whenever the buttons are pushed, not just when shift lock or caps lock are enabled.
Paul
whiteblazer01 said:
Carlos, I definitely agree, I would love to have that whenever the screen vibrated. Although, I don't know who would be willing to do that. I remember when I had the Apache (XV6700), I thought it would be cool if someone could make the LED lights on top into indicator lights for the shift and caps keys - which never happened (I don't know how, otherwise I would do it myself).
In fact, I wonder if someone can make a cab to have the shift and caps buttons make the indicator lights turn on whenever the buttons are pushed, not just when shift lock or caps lock are enabled.
Paul
Click to expand...
Click to collapse
It is very possible. I found other sources and they have some sort of program / prototype that can make this happen but it doesnt work on every tap of the screen.
What I want to do is make mine work on every tap of the screen but have the ability to turn it off and on to save power. Like turning the notification for the sound to play when you tap the screen on and off.
So far I have planned some steps to do it through the registry but since I am not an expert at programming like others are here it might take a while.
But any help is very welcome to complete this project and make it available for all.
As to changing the LED's on your phone. I think no2chem and some other guys found a way to customize your LED settings, but I'm not sure if it will be custom enough to indicate caps or shift. Maybe in the near future.
whiteblazer01 said:
I did a search on PPCGeeks, XDA, and Google, and couldn't find any app to make the touch screen on the Titan interactive - similar to the way the Voyager touch screen works (quick vibrate when the screen is touched).
Is there any app like this? If not, can someone make one?
Thanks!
Click to expand...
Click to collapse
this is a oem out there i havent seen Cab for it
Dc_striker said:
this is a oem out there i havent seen Cab for it
Click to expand...
Click to collapse
I am sure you probably have. I have the copy of the program that enables this feature. I believe it is extracted from a phone that has haptic feed back. But it is an executable.
This program is faulty. It doesn't respond on every tap and has performance issues. Other then that there hasn't been another one developed.
I'm trying to find a way to fix the issues of of the one that I found. Maybe by creating a new way to enable haptic feed back like I posted on previews posts, but it might take time to develop because I'm still learning how to mess with WM Reg. and programming.
[email protected]$ said:
I am sure you probably have. I have the copy of the program that enables this feature. I believe it is extracted from a phone that has haptic feed back. But it is an executable.
This program is faulty. It doesn't respond on every tap and has performance issues. Other then that there hasn't been another one developed.
I'm trying to find a way to fix the issues of of the one that I found. Maybe by creating a new way to enable haptic feed back like I posted on previews posts, but it might take time to develop because I'm still learning how to mess with WM Reg. and programming.
Click to expand...
Click to collapse
i still havent tried the program out yet i really dont see the use for it
Let me know what you find out Carlos. I would agree with you that it may be better to have the phone vibrate maybe when any button is pushed instead of anytime the screen is tapped (or maybe have the option to choose?), and also have the option to turn it off. Lol, maybe we can call it "Taptics" instead of Haptics.
As for the LED's, I'll check with some of the other guys about what they can do. I do a lot of modding myself with other electronics (cars, motorcycles, game consoles, etc...), but I don't really get into programming all that much (although the logic makes sense to me).
-Paul
Okay, so I noticed the phone does vibrate, however, when using the keypad while in a call, it makes a different tone, and does not vibrate.
Also, is there any update on ways to make all buttons vibrate (and configurable) when pressed? And of course, an option to turn the feature off?
whiteblazer01 said:
Okay, so I noticed the phone does vibrate, however, when using the keypad while in a call, it makes a different tone, and does not vibrate.
Also, is there any update on ways to make all buttons vibrate (and configurable) when pressed? And of course, an option to turn the feature off?
Click to expand...
Click to collapse
I am not sure for all buttons but there is a CAB to make the phone vibrate when you press the screen. I tried it out and it works, but it's faulty and kills performance.
I'm still working on this project. I haven't had much time to work with it, but if any break through happens then I will post it up.
My new HTC S740 is excellent except for one thing - the keypad backlight goes out after only 15 seconds. Very irritating in the dark.
I've looked for kb_light_timeout in hklm/software/htc/keypad but this does not exist.
I've found keylight timeout and qkeyledtimeout in hkcu/control panel/backlight which looks like the right place but altering values and rebooting makes no difference.
I've also looked in hklm/drivers/builtin/keylight and keypad.
I feel I'm very close. Can anyone help?
Yes Its most annoying as well as fact that only numbers or keys round circular button light seperately. Look forward to someone cracking it. Otherwise an excellent phone.
I agree, this is very annoying.
So theres no fix for this issue? To bad no ACT for this phone. An awesome phone, just wm standard gets so little love it seems.
I did some research today and he're the results:
1. This is far of to be a new issue. First complaints about the keyboard backlight timeout you can find under Qtek models...
2. Apparently, they were just few (2-3?) HTC models supporting a registry entry included in WM hkcu/control panel/backlight/QKeyLedTimeout - Rose definitely doesn't
3. The issue could be a case of WM 6.1 limitation - Rose has in fact three keyboard backlight arrays with separate light managements (soft keys, numeric, QWERTY - try to use them simultaneusly and you will see - their timing is independent on each other) and I've found some extra HTC registry entries concerning power management confirming a bit non-standard settings. Unluckily, nothing useful there for the kb backlights.
Sorry, based on my experiments, I can advice you only one very strange way how to overcome it for now: Limit the display timeout to the same 10 seconds as the keyboard has. At least, first press of any key will become inactive and just light-up both display and keyboard. Until display works, all keys are still active even the keybord backlight is off.
Nevertheless, any opposite finding will be appreciated...
Thank you for your investigation
I have a new s743 and this is the exact problem I came searching for fix for!
Too bad - it really is a sweet phone.
-John
To me this is a winmo thing. I don't understand why this option isn't included from the factory. It is a plain "NO BRAINER"! It's been this way on all my previous devices whether pro or standard. The diff being the pro os has wonderful tweaks and various cabs one can install to set the time out. What we need is to get some tweaking guru to set up something like ACT for standard. Problem is so little love for the standard os. The screens are to small anyway for my taste. I'll just stick to pro, the tweaks are better.
Well, i set the display timeout on my device to 5 seconds. Backlight of the qwerty and numeric keypads went off after 5 seconds.
The softkeys remained lit till 10 seconds was up.
I found the following problem with most cooked ROMs (also including the last official one from HTC) /I tried that on fresh installations in every case/
I like AutoLock feature. So I made a small .reg file to modify one small entry in registry.
The moment this feature is on - if the device becomes locked, the screen goes dim. Problem is - it stays dimmed forever. I tried thousand different solutions - many combinations of registry values, power options, etc. nothing helps. If I lock the device manually - no problem. only with autolock. Anybody knows how to make it work?
Regards,
Vojtek
Maybe you should post your script, so that someone can have a look. Did this work on some previous ROM? Or has it been an ongoing problem?
Try using SmartLock, found on this site.
jmckeejr said:
Maybe you should post your script, so that someone can have a look. Did this work on some previous ROM? Or has it been an ongoing problem?
Click to expand...
Click to collapse
The official HTC ROM that I used to have before recent official update from HTC - worked very fine with this little registry mod.
The modification is as follows:
HKCU->ControlPanel->Backlight->AutoDeviceLockEnable
default value = 0
I change it to 1. This is all I do after totally fresh ROM update. that causes the dim to go permanently on from the next lock (doesn't matter if it was caused by auto or manual). even If I get back with the value to 0 in registry - problem stays. soft reset (and value set to 0) eliminate the problem.
one more thing - I never use auto-light sensor. My backlight level is always set to 2. with auto-light sensor - autolock works OK. however I loose a lot of battery life since auto-light sensor never allows backlight levels lower than 4.
Regards,
Vojtek
check out Lumos, it'll let you backlight go as low as you set it to
http://forum.xda-developers.com/showthread.php?t=450318
GldRush98 said:
check out Lumos, it'll let you backlight go as low as you set it to
http://forum.xda-developers.com/showthread.php?t=450318
Click to expand...
Click to collapse
Thank You for the tip. The tool itself is great. However it is affected same way by the autolock. Autolock causes device to stay dimmed permanently - even with Lumos running.
Regards,
Vojtek
First off... I'm new around here & still a little flabbergasted by everything WinMo, but this site has already helped me tremendously.
Secondly, I can confirm the AutoLock bug. I updated my Touch Pro to the latest official rom last night. While running through AdvancedConfig (i think...) I noticed the AutoLock option & enabled it. 10 minutes later I was freaking out that I had stuffed up my expensive new toy...
Disabled, rebooted & all is OK again.
First of all - Advanced Config has nothing to do with it (to defend the author).
Second - thank You for support. I could not find a solution for this problem anywhere and I spent hours googling. For the moment I thought that my TP is failed. Seems that nobody uses AutoLock these days. I don't know how everybody's doing it, but without locking, my TP calls to different people (especially from Favourites tab) from time to time...
Vojtek
vojtek11 said:
I don't know how everybody's doing it, but without locking, my TP calls to different people (especially from Favourites tab) from time to time.
Click to expand...
Click to collapse
I require a password/passcode level of security on my device - which the Lock/Unlock feature doesn't provide. Unfortunately, the current security implementation in WinMO 6.x doesn't allow the Today screen to be seen like the Lock/Unlock feature.
As a result of these shortcomings, most folks tend to use a 3rd Party lock application such as: S2U2, mLock, etc. as they provide the desired flexibility.
HTH,
very familiar with this issue. I'm working on it too. It affects the WM6.5 lockscreen for sure and I thought it was a problem with only that. Bugger that it affects official ROMs as well. Good info though, I can stop concentrating on the lockscreen and start looking at power mgmt.
mindfrost82 said:
Try using SmartLock, found on this site.
Click to expand...
Click to collapse
SmartLock all the Way!!
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.
Hi, yesterday I upgraded from Paranoidandroid 3.68 to the new project Paranoidandroid 3.99 from http://forum.xda-developers.com/showthread.php?t=2397762
But I have an annoying problem - The touch button backlight keeps randomly turning on and switches off only when i click on screen. This only happens when I use it, it seems to be some kind of response or something. I have gone in settings>buttons>backlight and disabled it yet this does not disable the random turning on of it. Anyone know how can I completely disable it without installing custom kernels? Or what is causing it to randomly turn on all the time.
That's due to the touch key backlights. On 4.2.2 (PA 3.68) there was an option to disable them. On 4.3 it was removed by CM so a lot of other ROMs don't have the option either. What I've done on other 4.3 ROMs is to install the device settings apk and use that to turn them off. I haven't tried it on PA though.
I'm on mobile so can't give you a link... Search through my past posts from a couple weeks back. I posted the apk and instructions a couple of times, once in the PACman thread, once in Q&A. I also saw the steps quoted in Q&A by someone else too, you might come across that thread.
Oh wait you could probably even go to my 'most thanked posts'. It might be one of those. See how you go.
Sent from a galaxy far, far away
Hmm, thanks! But I did that, installed whole custom settings apk and launched the custom settings and turned the backlight off in there too, but it's exactly the same. Also this rom already has backlight button setting in options, so it didn't do anything new as far as i can tell.
The key backlight turns on randomly after like 5-30sec of pressing on screen. It's not like the usual backlight turning on keypress but it turns on after some time instead.
Edit: Backlight keeps turning on even if i have the default 3sec deley. the backlight would turn off after 3 sec and then back on after like 10sec until screen turns off or i press again on screen. Weird, maybe rom bug? I cant post on rom thread because i don't have enough posts
Edit 2: OK I have linked it to screen brightness. Every time screen brightness changes (from adaptive lightning, screen timeout and app/game setting) the key backlight turns on. I have no idea how to force the key backlight to stay off though, so thats why im here
Oh wow. Good job narrowing it down to that, I imagine it wasn't easy to figure out what was causing it. Have you read the rom thread for the last 15 pages or so? See if someone else is having the same issue. Also read the OP and following posts, for known bugs /FAQ. You should have read OP before flashing anyway but read it again
If you don't find anything else, try to get a few extra posts and then post in the thread. You seem to know what you're doing, so try helping out a few other people on Q&A maybe.
Sent from a galaxy far, far away
The latest(todays) build fixed the issue. Thanks for help!