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.
https://android.googlesource.com/device/samsung/tuna/+/095e19a54d217474e14fcdf769a0369ef3f4d30c
Reverse engineer this ?
Don't know if this will work but as far as I know it's not required by Jelly Bean?
Is this a good Idea ?
I am currently testing it. See my CM10 thread for the latest nightly to try this. This should fix all overclocking issues hopefully
Source code:
http://review.cyanogenmod.com/#/c/23076/
very good
Very very very good work guy .....
Why do you want to remove the HAL? As soon as it was fixed we didn't have more problems setting the clocks during screen on/off, so I don't see a reason to remove it and in the end it should cause more problems that its worth.
Steve's comment makes me worried:
Why not just make the code a little smarter and detect this stuff automatically?
Soon we will be using boostpulse in many more places in the framework to improve interactivity in ways that can't be done from the kernel alone.
Click to expand...
Click to collapse
Using boostpulse in the framework is NOT smart at all. I think this stuff should be done in the kernel level only. Other devices have other types of code to boost the frequency when it receives a touch event (all kernel level) instead of merging it to the userspace framework.
I really really start to like the P8000. It may not have gazillions of gadgets features but it does all the important stuff well enough and long enough (due to the splendid battery). Taking into account the price, I like it even better than my Nexus 5. Because this phone is such a bargain, I hope that it will get the developer support it deserves.
This is my wish list.
Priority no. 1: Encryption support (unfortunately, this feature is missing from the stock ROM)
Priority no. 2: Custom kernel (this would probably allow us to overclock, use USB OTG, install TWRP etc.)
Priority no. 3: Custom ROM with smart network support (xposed + Gravity Box or Smart Network does not work on my P8000)
Priority no. 4: Support of Android API for RAW pictures
Feel free to add your wishes. Maybe a talented developer will take care of us
-Tiz- said:
I really really start to like the P8000. It may not have gazillions of gadgets features but it does all the important stuff well enough and long enough (due to the splendid battery). Taking into account the price, I like it even better than my Nexus 5. Because this phone is such a bargain, I hope that it will get the developer support it deserves.
This is my wish list.
Priority no. 1: Encryption support (unfortunately, this feature is missing from the stock ROM)
Priority no. 2: Custom kernel (this would probably allow us to overclock, use USB OTG, install TWRP etc.)
Priority no. 3: Custom ROM with smart network support (xposed + Gravity Box or Smart Network does not work on my P8000)
Priority no. 4: Support of Android API for RAW pictures
Feel free to add your wishes. Maybe a talented developer will take care of us
Click to expand...
Click to collapse
When you say "Smart Network Support" in Priority 3, you mean the Smart Network Switch that turns of Mobile Data connection etc. when screen is off, yeah?
Try CPU Tuner and you can create profiles that trigger on different events like screen off. You can then choose to disable data connection, WiFi or whatever in that profile. You need to use it in Advanced Mode for full features I think.
Andy4Shurr said:
When you say "Smart Network Support" in Priority 3, you mean the Smart Network Switch that turns of Mobile Data connection etc. when screen is off, yeah?
Try CPU Tuner and you can create profiles that trigger on different events like screen off. You can then choose to disable data connection, WiFi or whatever in that profile. You need to use it in Advanced Mode for full features I think.
Click to expand...
Click to collapse
Yes + thanks. I will try CPU Tuner.
-Tiz- said:
Yes + thanks. I will try CPU Tuner.
Click to expand...
Click to collapse
I tried 3C Toolbox (seems to include CPU Tuner/System Tuner) and used a profile that switches off 4G when the screen is off. Anyway, it did not work...
working Bluetooth Music Stream without Skipping and Stopping :laugh:
For some reason, I am still on the July Stock ROM, and no updates to me whatsoever.
What I wish right now is:
- Better power management (for some reason, "Phone Idle" is always the top power consumer);
- Double tap to wake;
- Fix bluetooth issues (music skipping, gibberish play);
- Third party camera support;
- Possibility to overclock it;
- Fix small GPS hiccups;
And of course, Android Marshmallow update.
Rizera said:
For some reason, I am still on the July Stock ROM, and no updates to me whatsoever.
What I wish right now is:
- Better power management (for some reason, "Phone Idle" is always the top power consumer);
- Double tap to wake;
- Fix bluetooth issues (music skipping, gibberish play);
- Third party camera support;
- Possibility to overclock it;
- Fix small GPS hiccups;
And of course, Android Marshmallow update.
Click to expand...
Click to collapse
If you update to the latest stock ROM or use Eragon custom ROM, you will be able to use third party cameras. I tested this myself.
How do I improve the speaker volume, I have tried mtk engineering mode but volume doesn't seem to have improved very much
Dear All,
I´ve managed to build a CM 12.1 with nfs support. Why 12.1? Well, for my D855, that was the only branch I could get working when building a kernel in Ubuntu, using the downloadable snapshot at CM´s site. The nighty´s would give me errors of different kinds during the building process, so the files on the phone needed when building are probably not the exact required version that match with the repo you can download in terminal mode.
Anyway, my experience with marshmellow is that the phone gets so hot that it turns itself off - another good reason to stay with 12.1.
My phone however still gets hot, which happens when using it with my VR headset to watch UHD clips. After 5 mins of watching, it dims down a bit. Then a few mins later a bit more, and so on until it looks like I´m staring at the screen through old cheap shades.
I´ve already disabled automatic brightness control, tried apps which claim to keep the brightness at the desired strength (Lux, the app is called), an app that´s ment to keep the screen always on (Always Awake), an app claiming to patch this exact bug, flashed a hack that´ll throttle only above 70 C. None of this helped. What I do know is that in the secret menu of stock firmware, there´s an option called Thermal Daemon Mitigation OFF, but I can´t access the secret menu through CM - only CM´s secret menu, that doesn´t have this option. Enabling this is said to cope with the problem.
There´s also a file named thermanager.xml in system/etc, which looks like something which can be modified to meet my requirements, but I´m not sure.
Finally, my least prefered option is to install a thermal pad on the SoC, but although I´m experienced with hardware, it´s on desktop level - not with such tiny things as a mobile.
So please, could someone help out here? Is there a way to rebuild the kernel with the stock secret menu or amendments to the throttling? Is there a way for me to get into the stock secret menu in CM?
Other ideas?
PS: I´m posting here because if there´s a way to get Thermal Daemon Mitigation OFF option related parameters set when building kernel in menuconfig, then it´s related to this sub forum.
PPS: Edited thermanager so all brightness values are 255, this seems to fix the problem!
Hey sorry for title
i want to know how to make my phone just work like Feature phone on one click.
And another click Phone like super beast mode without Any reboot...
My motive behind this Power And battery
Feature phone mean i get super dooper SOT
One click super dooper mode eh? Just download more ram and overcharge your phone during a full moon.
You need a kernel manager, like EX Kernel Manager, that can support at least two profiles. However, I don't think such an app will work on the fly - switching between profiles without a reboot. Another option is Spectrum, but the kernel has to support the injector script. There's a thread about Spectrum here: https://forum.xda-developers.com/android/apps-games/app-spectrum-kernel-manager-users-t3601542. Good luck!
You could achieve some of this using Tasker (or similar) as you could address brightness / replication status / radios / Bluetooth / etc. Won't allow kernel changes (unless rooted and using a 3rd party tool) but for me, the majority of battery is spent on screen being on & background tasks.