Develop Bugs

[22FEB2012] [FIXED!!!] Custom Auto brightness with flashing LED (Read First Post)

We have a fix​
Please read this post (and Thanks Milaq for the fix!!) and follow the instructions.
[*]Also, can someone test custom auto brightness levels too please?
I have made a ClockWorkMod flashable version of the fix in this post. This should cover almost all ROMs, irrespective of how the device is named in build.prop (leo, htcleo, bravo, qsd8k).
Original Post:
UPDATE: Thanks to Looki75, we have a workaround using Tasker to have custom auto-brightness levels with the flashing LED libraries here. Please go through his post and give your feedback!
I am rewriting the whole post, based on what I realized/ learnt today
We currently two lights libraries for to our phone:
lights.htcleo.so - this file has working auto-brightness and flashing LED notifications - but custom auto-brightness settings do not work (more on this a bit later)
lights.qsd8k.s0 - this file has working auto-brightness and custom auto-brightness levels, but LED notifications do not flash
Custom auto-brightness settings
What is it?
This is a setting/ feature in CM7 ROMs, not sure if MIUI has it or not (Users, please confirm if you have custom auto-brightness settings in non-CM7 based ROMs)
In a pitch dark room, the screen's brightness chosen by auto-brightness setting may be higher than required. With custom auto-brightness, the level of brightness the phone uses for a specific amount of light can be configured - the biggest benefit being higher battery life. Please read this post by @Dorimanx for custom auto-brightness levels.
How do I know if I have it or not?
You do not have the lights library that is compatible with custom auto-brightness levels if:
Your LED Notifications work (Except HeirOS kernels)
If you have something similar to this in your logcat:
20:50:43.090 Error lights 180 ***: value=90 (Mode=1)
20:50:43.090 Error lights 180 ***: value=91 (Mode=1)
20:50:43.090 Error lights 180 ***: value=92 (Mode=1)
20:50:43.090 Error lights 180 ***: value=94 (Mode=1)
Click to expand...
Click to collapse
On the other hand, you have it if
Your LED does not flash
Your screen will dim for several seconds (5~10seconds) before timing out
You do not see the errors I had quoted above in your logcat
So what is the point of this thread?
I had tried several Kernel combinations (and libaudio.so, but that does not matter in this issue) while trying to figure out the No Sound/ BT Voice Command/ libaudio.so issues, and found out that even if I have lights.qsd8k.so, which enables custom auto-brightness levels, LED Notifications flash with HeirOS 1.7.5 Kernel - they flash in amber and green alternatively. This gave me a hope that
This is something to do with the kernel (I used Tytung's initrd.gz, so it is not from there...)
This could be fixed easily with all our kernels, because HeirOS has already done it!
So What Next?
Anyone using any of the HeirOS kernels see what library you have (/system/lib/hw), and please use the lights.qsd8k.so if it is not there, deleting lights.htcleo.so while at it (it is available in the Mirrors used by @Dorimanx), and confirm if you concur with my observations - please mention the kernel version and the name of the lights library in your feedback.
Once we have that confirmed, we can request HeirOS to let us know the secret ingredient (or someone intelligent enough to look through the source codes can find it and post the diff/ findings).
This is not a critical/ experience-affecting issue, but rather something that is now "broken" and can be fixed without much ado!! I am sorry for not being clear earlier, a little bit of Rum cleared things up for me
Lets now restart this discussion!!!

It is people like you that are going to make our phone as if it came with android when we bought it! I know you are not the one doing the coding but with all your support, your don't give up attitude, and your connections you get the job done. Thank you for all your determination.
Sent from my HTC HD2 using XDA App

hopefully the next thread for collaboration work that will become one of it's kind in hd2 android history. thx for your dedication and all the testing that you do! thanks to all the devs making our hd2 improving everyday.

I have posted a request in HeirOS' kernel thread, meanwhile can those who use earlier versions (1.7.2 or so) confirm if they have working LED Notifications when you use a working auto-brightness configuration please?
If so, I think we can trawl the source code posted on the first post of HeirOS kernel thread...

ph03n!x said:
We currently have to choose between a working auto-brightness setting, or a working flashing LED notification in most configurations/ kernals....
Click to expand...
Click to collapse
Had never problems with auto brightness and my last kernel with a non working LED notification is older than around a half year. But I tried only MDJ, Tytungs and Raf's kernel. Green and orange LED are working perfect with these.
What problems do you have with auto brightness? Not working or the false brightness for the actual light?
Only outdoor at sunshine the auto brightness sometimes didn't choose the maximum brightness, than I set manual to max.

Nixda99 said:
Had never problems with auto brightness and my last kernel with a non working LED notification is older than around a half year. But I tried only MDJ, Tytungs and Raf's kernel. Green and orange LED are working perfect with these.
What problems do you have with auto brightness? Not working or the false brightness for the actual light?
Only outdoor at sunshine the auto brightness sometimes didn't choose the maximum brightness, than I set manual to max.
Click to expand...
Click to collapse
The auto-brightness / LED notifications are from /system/lib/hw/lights.htcleo.so (or lights.qsd8k.so).
In our case if your ROM's chef chose to have a working LED Notification configuration, auto-brightness will not work - the display will have a fixed brightness irrespective of the surroundings, and will not dim before fading out.
If you choose working Auto Brightness, the screen will maintain ambient lighting, but when have a missed call or SMS or email or chat, the LED stays on and does not flash.
That said, what kernel are you using? And can you check your logcat right from system boot (using QtADB?) and let us know if you see any errors?

ph03n!x said:
The auto-brightness / LED notifications are from /system/lib/hw/lights.htcleo.so (or lights.qsd8k.so).
In our case if your ROM's chef chose to have a working LED Notification configuration, auto-brightness will not work - the display will have a fixed brightness irrespective of the surroundings, and will not dim before fading out.
Click to expand...
Click to collapse
Yeah...
Typhoon included Led blinking, i always replace it with lights.qsd8k.so with auto-brightness, i dont care about Led blinking too much, more interesting good working auto-brightness

Install led me know from the market and you will have both working fine.That is what i do in dorimanx rom which has auto brightness enabled by default.
eseregin said:
Yeah...
Typhoon included Led blinking, i always replace it with lights.qsd8k.so with auto-brightness, i dont care about Led blinking too much, more interesting good working auto-brightness
Click to expand...
Click to collapse
Sent from my HD2 using XDA App

ph03n!x said:
The auto-brightness / LED notifications are from /system/lib/hw/lights.htcleo.so (or lights.qsd8k.so).
In our case if your ROM's chef chose to have a working LED Notification configuration, auto-brightness will not work - the display will have a fixed brightness irrespective of the surroundings, and will not dim before fading out.
If you choose working Auto Brightness, the screen will maintain ambient lighting, but when have a missed call or SMS or email or chat, the LED stays on and does not flash.
That said, what kernel are you using? And can you check your logcat right from system boot (using QtADB?) and let us know if you see any errors?
Click to expand...
Click to collapse
If I remember it correctly, the working LED Notification (i.e. No fading out feature) of lights.htcleo.so in my GB ROM is from Gpc.

Moreover I think that the developer of LedMeKnow app, which is free by the way, may point out to the developers what to change in order to have both auto brightness and led blinking working out of the box for hd2s
karapialis said:
Install led me know from the market and you will have both working fine.That is what i do in dorimanx rom which has auto brightness enabled by default.
Sent from my HD2 using XDA App
Click to expand...
Click to collapse
Sent from my HD2 using XDA App

leds and auto brightness work perfectley if you use the lights file from iamgpc. So I dont see the problem. Secondly this problem is hard to catch I can remember that Letama and gauner1986 tried to solve this problem but at the end they gave up.

jan-willem3 said:
leds and auto brightness work perfectley if you use the lights file from iamgpc. So I dont see the problem. Secondly this problem is hard to catch I can remember that Letama and gauner1986 tried to solve this problem but at the end they gave up.
Click to expand...
Click to collapse
Yes, manual brightness works in GPC's lights.htcleo.so, but auto-brightness does not.
I found the HeirOS has fixed this (though not documented) in 1.7.5 (not tested earlier versions)...

ph03n!x said:
We currently have to choose between a working auto-brightness setting, or a working flashing LED notification in most configurations/ kernals.
I am saying "most" because in my quest to fix the No Sound/ BT Voice Command/ libaudio.so issues, I tested various kernels and configurations, and found that with HeirOS 1.7.5 kernel, I have a working auto-brightness WITH flashing LED notifications. The notifications actually flash amber and green.
So looks like this is something that we can fix easier than the close to 5 weeks spent on the No Sound bug
HeirOS, please share your thoughts/ inputs for the benefit of all of us!!
This is not a critical/ experience-affecting issue, but rather something that is now "broken" and can be fixed without much ado!!
My explanation / understanding of the LED Notification vs. Auto Brightness issue- correct me if required
Click to expand...
Click to collapse
Here is a well-known solution for auto-brightness + flashing LED:
karapialis said:
Install led me know from the market and you will have both working fine
Click to expand...
Click to collapse
Like I said earlier, while fixing it natively is a good-to-have solution, and not a deal breaker for almost all of us. But still having it fixed surely feels good, doesn't it?!!

karapialis said:
Install led me know from the market and you will have both working fine
Click to expand...
Click to collapse
Updated the first post

karapialis said:
Moreover I think that the developer of LedMeKnow app, which is free by the way, may point out to the developers what to change in order to have both auto brightness and led blinking working out of the box for hd2s
Sent from my HD2 using XDA App
Click to expand...
Click to collapse
LED Me Know eats up battery while flashing notification. When its flashing LED, the battery drain is more than 100mAh. Though I haven't used the application in a long time, but I remember previously it used to do that...I wonder if its changed now..

I actually prefer a static LED with working auto brightness.
Its very obvious without staring at my phone whether I have a new text, missed call, or otherwise. I tend to miss the blinking since its 8 seconds apart.
(know it can be configured to 3 seconds, but still)
Sent from my HTC HD2 using Tapatalk

ph03n!x said:
Yes, manual brightness works in GPC's lights.htcleo.so, but auto-brightness does not.
I found the HeirOS has fixed this (though not documented) in 1.7.5 (not tested earlier versions)...
Click to expand...
Click to collapse
Auto brightness works fine here.

In HeirOS 1.8 kernel i have led working and i do notice that when its really dark the screen will get bright and when its super sunny it gets darker so i believe auto brightness + led works fine in his new test kernel btw i am on sense gb rom.

Vice versa
In HeirOS 1.8 kernel i have led working and i do notice that when its really dark the screen will get bright and when its super sunny it gets darker so i believe auto brightness + led works fine in his new test kernel btw i am on sense gb rom.
Click to expand...
Click to collapse
Sent from my HD2 using XDA App

Auto brightness with flashing LED notification works perfectly in Tytung's rom and kernel.

[Q] CPU throttleed--why? and..best CPU utilization monitor?

I'm running Albinoman's JB RC3 ROM, and like it a lot. The only significant problem I have is occasional severe sluggishness. When it happens, I'll open IntelliControl and I notice either of two things going on:
1) I'll see that the max CPU speed has been reset to 664000 or something close to that (it's always the same number, but I don't remember exactly what it is...600-something). Once I crank the max limit back up to 1036800, things are good again. What keeps resetting the CPU limit to such a low level, and how do I stop it from doing that???
2) I'll see that the CPU is maxed out at 1036800, but I can't figure out what's chewing up the CPU. What tool can I use to see what process is consuming all the CPU cycles when that happens?
Thanks for the help...

1. I can't tell you why it happens... but I know it is a common problem on the JB ROMs (on the Dinc). There was quite a lot of discussion about it. I know the devs are aware of the issue and were working on it.
2. I don't know of anything that will graph percentage of cpu cycles, or anything exactly like that. But try hooking the phone up to the PC and run ddms (part of the adb tool set) and see what it is doing (or failing to do). While ddms is running in verbose mode it will give you a running output of everything the phone is doing (along with all the errors and warnings).

MysticCobra said:
I'm running Albinoman's JB RC3 ROM, and like it a lot. The only significant problem I have is occasional severe sluggishness. When it happens, I'll open IntelliControl and I notice either of two things going on:
1) I'll see that the max CPU speed has been reset to 664000 or something close to that (it's always the same number, but I don't remember exactly what it is...600-something). Once I crank the max limit back up to 1036800, things are good again. What keeps resetting the CPU limit to such a low level, and how do I stop it from doing that???
Click to expand...
Click to collapse
That's because he's using an older version of Evervolv's qsd8k-common. It was fixed on Oct 10 with Change I3a0fff83: powerHAL: fix the screen off bug. This is one of the reasons I do nightlys, is to get all the new tweaks. This bug won't be fixed in his ROM till he resyncs his source and recompiles. It's triggered by the screen turning off. There's a workaround with Tasker, but since this bug is no longer in my ROM, I quit looking at it.
MysticCobra said:
2) I'll see that the CPU is maxed out at 1036800, but I can't figure out what's chewing up the CPU. What tool can I use to see what process is consuming all the CPU cycles when that happens?
Click to expand...
Click to collapse
CPUSpy is a pretty good app.

MysticCobra said:
I'm running Albinoman's JB RC3 ROM, and like it a lot. The only significant problem I have is occasional severe sluggishness. When it happens, I'll open IntelliControl and I notice either of two things going on:
1) I'll see that the max CPU speed has been reset to 664000 or something close to that (it's always the same number, but I don't remember exactly what it is...600-something). Once I crank the max limit back up to 1036800, things are good again. What keeps resetting the CPU limit to such a low level, and how do I stop it from doing that???
2) I'll see that the CPU is maxed out at 1036800, but I can't figure out what's chewing up the CPU. What tool can I use to see what process is consuming all the CPU cycles when that happens?
Thanks for the help...
Click to expand...
Click to collapse
For #1, a possible fix could be to use this power.qsd8k.so provided by tiny4579:
http://forum.xda-developers.com/showpost.php?p=32552961&postcount=264
Replacing this file fixed the issue on Pons's ROM, but it may wreak havoc on Albinoman's, I have no way to know. Make sure you have a good nandroid backup before attempting to use it. Or, just wait for Albinoman to release a newer ROM with the problem fixed in the source.

musical_chairs said:
For #1, a possible fix could be to use this power.qsd8k.so provided by tiny4579:
http://forum.xda-developers.com/showpost.php?p=32552961&postcount=264
Replacing this file fixed the issue on Pons's ROM, but it may wreak havoc on Albinoman's, I have no way to know. Make sure you have a good nandroid backup before attempting to use it. Or, just wait for Albinoman to release a newer ROM with the problem fixed in the source.
Click to expand...
Click to collapse
It should work fine on Albinoman's ROM. powerHAL is a generic jellybean feature and should work on all JB ROM's. You won't need the fix however on either of Pon's ROMs whether AOKP or CM10.

I'm finding the same issue on the 11/08 build. I replaced the file with the one you uploaded, yet no change. Still reverts to 614 when the screen is off.
I'm managing it with both Incredicontrol and Juicedefender, so on wake it returns to 1075, and the SAv2 seems much smoother than interactive for me. If there's a fix in the newer builds I may flash one (if I get the time), but for now I'm really impressed by how well this one is running.
Thanks,
...sorry...I was on the phone...

omniatic said:
I'm finding the same issue on the 11/08 build. I replaced the file with the one you uploaded, yet no change. Still reverts to 614 when the screen is off.
I'm managing it with both Incredicontrol and Juicedefender, so on wake it returns to 1075, and the SAv2 seems much smoother than interactive for me. If there's a fix in the newer builds I may flash one (if I get the time), but for now I'm really impressed by how well this one is running.
Thanks,
...sorry...I was on the phone...
Click to expand...
Click to collapse
It's supposed to change to 614 on screen off. The bug was that it would stick at 614 even on screen on.
I don't recommend that lib for cm. It's outdated.
Also I don't use sav2 anymore as it doesn't and won't implement project butter. Also interactive can be more aggressive than sav2 as it can jump frequency on touch via boostpulse which sav2 doesn't have.
Sent from my Galaxy Nexus using Tapatalk 2

Oh, well, then I guess I'll give the interactive another try. Maybe just needs to settle in longer. Got so used to ICS, wasn't sure what to expect from JB. Guess it's time I read back a few pages and see what else I've missed.
...sorry...I was on the phone...

Thanks, guys--appreciate the help!

Maybe its out of topic but since i still cant post on dev sub forum i wanna ask a question here to pons.
Im running your CM10 20121114, whenever i play music with appolo it always reboot my dinc.
Is any other had this problem too?

alph0 said:
Maybe its out of topic but since i still cant post on dev sub forum i wanna ask a question here to pons.
Im running your CM10 20121114, whenever i play music with appolo it always reboot my dinc.
Is any other had this problem too?
Click to expand...
Click to collapse
Yep, just a tad bit off topic.
I haven't had this problem before. Granted, I've never played music off my Inc, but I haven't heard anyone else complain, either. Can you PM a logcat? And it's always preferable to report errors off latest versions (currently 1120).

PonsAsinorem said:
Yep, just a tad bit off topic.
I haven't had this problem before. Granted, I've never played music off my Inc, but I haven't heard anyone else complain, either. Can you PM a logcat? And it's always preferable to report errors off latest versions (currently 1120).
Click to expand...
Click to collapse
Thanks for the reply Pons. Yes i think i will download the latest build sooner and test it again. Hope it (randon reboot with apollo) will not happen again on my dinc. But if it still, i will pm you the logcat.

alph0 said:
Thanks for the reply Pons. Yes i think i will download the latest build sooner and test it again. Hope it (randon reboot with apollo) will not happen again on my dinc. But if it still, i will pm you the logcat.
Click to expand...
Click to collapse
I use Apollo Music regularly on Pons's CM10, it works fine, doesn't reboot.

alph0 said:
Maybe its out of topic but since i still cant post on dev sub forum i wanna ask a question here to pons.
Im running your CM10 20121114, whenever i play music with appolo it always reboot my dinc.
Is any other had this problem too?
Click to expand...
Click to collapse
Try flashing to his newest build. It fixed a few problems for me and is incredibly fast. I had to reflash gapps from goo.im though because play store was force closing. Also, doubletwist is a better music player imo because it has a better interface and has good integration with the lockscreen.

The definitive unresponsive touchscreen topic [Black screen of death]

As apparently many of you have witnessed before, there are situations where the Galaxy Nexus becomes unresponsive to touch input.
For me, this most of the time is noticeable when trying to unlock the phone. The phone just doesn't respond to me trying to unlock the Screen Lock (Setting: Slide).
The only way to get out of the situation is pulling the battery and reboot. One thing I notice after this routine, is that the phone has lost a lot of battery juice.
I've read a lot about this problem on multiple forums (XDA of course, but also Google support etc) and none of them have been able to pinpoint the exact cause.
There are, however, a couple of applications and settings that are more likely to cause the problem, but feel free to mention your own "suspicious" apps.
* [App] Light Flow
* [App] PGM Nexus
* [Setting] Auto Brightness
Please let me know if you've ever encountered above problem, on what version of Android you are, and if you're using on or more of the above apps/settings.

Had it on CM10 stable, disabling pgm did the trick. (I use auto-brightness but no lightflow)

I had this on rascarlo 4.2.1 /w Trinity & Franco kernels.
All I had from your list was;
* [Setting] Auto Brightness
I was also reading the developer options animation set to below .5x could increase the SOD.

chrisgtl said:
I had this on rascarlo 4.2.1 /w Trinity & Franco kernels.
All I had from your list was;
* [Setting] Auto Brightness
I was also reading the developer options animation set to below .5x could increase the SOD.
Click to expand...
Click to collapse
So .5x is still okay?
Furthermore, could you tell me where you read this?

Smultie said:
So .5x is still okay?
Furthermore, could you tell me where you read this?
Click to expand...
Click to collapse
I'm unable to test out the animation theory as I'm back on 4.1.2 for now.
Read here > http://code.google.com/p/android/issues/detail?id=40019

[Q] KT747 "problem"

Hello, I think I have an issue with the kernel. I can't post in the development thread because I don't have 10 posts. Ok, so here's my problem, in the general section, on the frequency slider, the mhz is in read and reads (chrg override) so it would be max: 1512 (chrg override). What does it mean and what can I do to maybe stop it?
Thanks in advance

coollkidd said:
Hello, I think I have an issue with the kernel. I can't post in the development thread because I don't have 10 posts. Ok, so here's my problem, in the general section, on the frequency slider, the mhz is in read and reads (chrg override) so it would be max: 1512 (chrg override). What does it mean and what can I do to maybe stop it?
Thanks in advance
Click to expand...
Click to collapse
I had a similar problem but it said battery override i go rid of it by taking root from du battery saver app must be something similar an app not letting you be able to use that feature try uninstalling apps that have root access and reboot so that the changes happen

philliedbz said:
I had a similar problem but it said battery override i go rid of it by taking root from du battery saver app must be something similar an app not letting you be able to use that feature try uninstalling apps that have root access and reboot so that the changes happen
Click to expand...
Click to collapse
Thanks! I found an app was doing it.

Display Flicker on Custom ROMS

Hello everybody,
i have a strange bug. My display is flickering on most custom ROMS (CAF-Based and LOS). It's like the display is going on and off like 30 times in a second. Also on the lowest brightness the bottom 30% are complet black. On all OOS-based this problem is not present. So it's not a real hardware defect.
Someone has an idea what can cause this issue?

In case you did not know: The OnePlus3 uses some kind of PWM Pulse-width modulation to regulate its brightness. Test it for yourself: In a completely dark room move your hand very fast over your display. You will see a stutter effect at lower settings.
This is used in many tec devices and is known to be a more cheap implementation.
Back to your problem: Maybe your regulator for the pulse mod is broken?
Did you try a hard reset, meaning re-flashing all the core firmwares?

Hey.
Yes I read about this PWM. I also thought this could be the problem. Perhaps in the CAF Kernel the parameters are different? I've never looked in the source code for kernels. ?
And yes I have reset my phone with the full bricked version from the xda thread. Also tried different firmware versions (but only the nougat ones) with the CAF ROMs. Also tried all OOS versions (include marshmallow) and the problem never occurs there.
Is there perhaps a kernel manager where I can see (and change) some parameters related to the display driver? Only found some color calibrations in EX Kernel manager etc.

did you manage to solved this problem?

if on a custom rom, try disabling "Reduce Power Consumption" in live display settings. Might work, might not but you can try.

Antares9 said:
did you manage to solved this problem?
Click to expand...
Click to collapse
for me linage 15.1 and 14.1 are ok but others are not working.....