Database Info

[APP] NovaFreq v1.2.1 (For Novatek Panels Only) [ Updated 07/18/10 ]

Evo Switch v1.1.1 NovaFreq v1.2.1
(APP NAME CHANGED TO SOMETHING MORE APPROPRIATE)
This is an Android application developed to change the panel frequency for Novatek Panels for the Sprint HTC EVO 4G, in conjunction with ffolkes' Novatek Kernel and netarchy's Kernel,
and any kernel that has maejrep's T2 Interface built in. Every device is different, and with that, those specified kernel's default settings may or may not be optimized with your device.
With this application, you can change those settings on the fly and find the best setting for your device.
[ Please use this application with extreme caution! I am not responsible for any damage this may cause to your device. ]
Requirements:
-HTC EVO 4G
-Android 2.1 +
-Any custom kernel that is built off of toastcfh's htc source
-Novatek Panel
-Root Access
Uses:
-Use as an fps frequency turbo switch for when you need extra fps.
-Use as a debugging tool to test frequencies.
-Use to keep frequency settings even beyond reboots. (new)
Settings:
-340 [Stock] is how HTC intended the EVO to be. This frequency works out to 61hz, but we are capped at 30hz.
-370 [Kernel Default] sets the panel frequency lower than stock, yet provides most around 55fps.
-250 [Stable High Freq] sets the panel frequency higher than stock, which usually gives around 40fps.
-400 [Stable Low Freq] - V2's setting.
-Favorite Setting - Find the most stable setting, and if it's not one of the listed, then "Set Favorite".
-Sticky Settings - Now you can reboot and not have to re-apply your settings!
Custom Setting:
You can put arbitrary settings here, but be warned this may mess up your screen, but usually you can reboot your phone
to change it back to default. Minimum Recommended: 250 Maximum Recommended: 999.
Please do not go lower then the minimum recommended of 250, nor higher than the maximum recommended 999.
To Do:
-Favorite Setting - So you can save the best setting for your device. 07/04/10 - Done!
Change Log:
-Changed app name from Evo Switch to NovaFreq (Novatek Frequency / Freek)
-Totally redid code, should be more optimized.
-Frequencies stick beyond a reboot
-Changed a few of the defaults
-Changed back sleep time to 500ms so the current displayed setting can update (v1.2.1)
Don't be alarmed if you see NovaFreq running in the background. To be able to sticky settings beyond a reboot, NovaFreq has to be run at boot up.
After that you can kill NovaFreq if you want, android will kill it when needed so don't worry.
Thanks To:
ffolkes, netarchy, maejrep, toastcfh, halfline, Cicitrize, geyes30, kpkimmel, joeykrim, and many others involved in trying to uncap the EVO.

Reserved...

Reserved again.

woah, this is badass. I will check it out soon

works great! Whats the number I set it at to equal the V2 setting of ffolkes kernel? I think its 400, is that correct?

Awesome!! This is the first time I've been able to break 30 fps! (thanks to your app!)
I'm on Froyo and the v4 had never worked, but now v4 + high frequency with your app = 40 fps.
I love you.

this may a silly question... but would this fix camera when i have it disabled as to if i switch it on the camera is now broke? or just the kernel itself breaks the camera??

Great little app, I would recommend users experiment with the values just ever so slightly for optimum performance. Using the default value of 361 netted me about 50-51 fps, whereas using 365 nets me about 54-55. Not a huge bump, but even a little bit is nice

Great application. May I suggest adding maybe a quick cycle to move between frequencies so users can go through a number of settings at once? Kinda like the Scan feature in most radios to pick the best frequencies.

timgt said:
works great! Whats the number I set it at to equal the V2 setting of ffolkes kernel? I think its 400, is that correct?
Click to expand...
Click to collapse
Yes, I think V2 was 400.
madunix said:
this may a silly question... but would this fix camera when i have it disabled as to if i switch it on the camera is now broke? or just the kernel itself breaks the camera??
Click to expand...
Click to collapse
Every custom kernel does not have a working camera, because we do not have the source code for it. When HTC finally releases the source code, then we will be able to fix the camera.

antiphon said:
Great application. May I suggest adding maybe a quick cycle to move between frequencies so users can go through a number of settings at once? Kinda like the Scan feature in most radios to pick the best frequencies.
Click to expand...
Click to collapse
This sounds like something to think about. Only problem is, while scanning, no one will know what the fps is unless they have their favorite fps app running, but then we wouldn't know what the frequency setting is since the fps app is running in focus. Might be a bit difficult to pull off without building an fps test into the app.

Well done!! Thanks

AssassinsLament said:
This sounds like something to think about. Only problem is, while scanning, no one will know what the fps is unless they have their favorite fps app running, but then we wouldn't know what the frequency setting is since the fps app is running in focus. Might be a bit difficult to pull off without building an fps test into the app.
Click to expand...
Click to collapse
Yeah I agree it would be difficult to implement without a built in fps counter. I was thinking more along the lines of something that would flag or eliminate the frequencies that are really bad (ie the ones which make your screen go haywire). So maybe the user could, for example, pick frequencies 300-310 and then the app would cycle through them 1 second at a time. From there the user would be able to run FPS2D or whatever to test out those frequencies that didn't make their screen all blotchy.
Anyways, just something to think about. Great work nonetheless!

antiphon said:
Yeah I agree it would be difficult to implement without a built in fps counter. I was thinking more along the lines of something that would flag or eliminate the frequencies that are really bad (ie the ones which make your screen go haywire). So maybe the user could, for example, pick frequencies 300-310 and then the app would cycle through them 1 second at a time. From there the user would be able to run FPS2D or whatever to test out those frequencies that didn't make their screen all blotchy.
Anyways, just something to think about. Great work nonetheless!
Click to expand...
Click to collapse
This won't work, because the interface that is used to write these settings to the panel cannot handle both full-speed graphics, and setting panel registers. I tried this when I first created the sysfs attr file, and if fps2d is running, it seems impossible to set or query the current T2 value. the display pretty much has to be idle for this to work.
Using a mutex lock might help, but I didn't look into it any further.

maejrep said:
This won't work, because the interface that is used to write these settings to the panel cannot handle both full-speed graphics, and setting panel registers. I tried this when I first created the sysfs attr file, and if fps2d is running, it seems impossible to set or query the current T2 value. the display pretty much has to be idle for this to work.
Using a mutex lock might help, but I didn't look into it any further.
Click to expand...
Click to collapse
Yep, that's why I had to put in a "sleep" command in my app so that the system could process the change and update the app on if the register changed or not. Thanks for the interface maejrep!

Where is the link to the switch app?
Sent from my PC36100 using XDA App

Yeah? Where is version 1.1.1? 1.1.0 is the only available for download? Or am I a special needs kid?

Force close only.

apollooff320 said:
Where is the link to the switch app?
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
VoXHTC said:
Yeah? Where is version 1.1.1? 1.1.0 is the only available for download? Or am I a special needs kid?
Click to expand...
Click to collapse
Sorry, maybe I forgot to change the version in the app, 1.1.1 should be the only one linked in the original post.
Sprockethead said:
Force close only.
Click to expand...
Click to collapse
Do you meet the minimal requirements on the original post? Because you have to be running a custom kernel with the T2 interface in it.

wont recognize
im not sure whats wrong, i downloaded this on my phone and it says it dosent recognize the file i downloaded

A request to all devs...

I think the this is pertinent to all Samsung ROMs, and I would like Devs to provide input on an aspect that affects the whole reason we buy the phone - in this case the Skyrocket.
This is about brightness/clarity changes that happen between ROMs. One MAIN reason that we buy the Samsung phones is the brilliance of the Super AMOLED screens. When custom ROMs are flashed, the screen brighness and clarity - yes, clarity which may itself be a psychological link to brightness - changes quite a bit.
Almost all ROMs do NOT mention if the dev ACTIVELY changed the brightness settings in framework-res. NO DISSIN ANYBODY here. So please this is not a negative. Or did the dev remove stock apks, files etc., that may or may not be linked to screen/display settings. I UNDERSTAND THAT THIS MAY BE DONE TO SAVE BATTERY. So no biggie there either.
ALSO, I know how to hack the brightness in framework-res, and also have apps that can do it for me.
It would be great if devs could indicate if brightness was hacked, because STOCK BRIGHTNESS/DISPLAY always looks so much more impressive. Much more impressive than any custom rom, BUT STOCK SUCKS otherwise. If it was not hacked then clearly settings are getting affected.
It would be really great if we could retain stock display quality in custom ROMs. Also, by indicating about brightness in Rom OP, this would give a heads up what to expect. Whether to hack myself, or use apk.
THANKS TO ALL DEVS, anyways for their super work that makes the phones so much better than manufacturer's want us to have !!

chappatti said:
I think the this is pertinent to all Samsung ROMs, and I would like Devs to provide input on an aspect that affects the whole reason we buy the phone - in this case the Skyrocket.
This is about brightness/clarity changes that happen between ROMs. One MAIN reason that we buy the Samsung phones is the brilliance of the Super AMOLED screens. When custom ROMs are flashed, the screen brighness and clarity - yes, clarity which may itself be a psychological link to brightness - changes quite a bit.
Almost all ROMs do NOT mention if the dev ACTIVELY changed the brightness settings in framework-res. NO DISSIN ANYBODY here. So please this is not a negative. Or did the dev remove stock apks, files etc., that may or may not be linked to screen/display settings. I UNDERSTAND THAT THIS MAY BE DONE TO SAVE BATTERY. So no biggie there either.
ALSO, I know how to hack the brightness in framework-res, and also have apps that can do it for me.
It would be great if devs could indicate if brightness was hacked, because STOCK BRIGHTNESS/DISPLAY always looks so much more impressive. Much more impressive than any custom rom, BUT STOCK SUCKS otherwise. If it was not hacked then clearly settings are getting affected.
It would be really great if we could retain stock display quality in custom ROMs. Also, by indicating about brightness in Rom OP, this would give a heads up what to expect. Whether to hack myself, or use apk.
THANKS TO ALL DEVS, anyways for their super work that makes the phones so much better than manufacturer's want us to have !!
Click to expand...
Click to collapse
how exactly do you hack the brightness? I'd love to play with this.
Sent from my SAMSUNG-SGH-I727 using xda premium

Shadeslayers said:
how exactly do you hack the brightness? I'd love to play with this.
Sent from my SAMSUNG-SGH-I727 using xda premium
Click to expand...
Click to collapse
Here are some spots to help you: I would try to make a tutorial but have not gotten arond to it since it is available in some places.
The first is very up-to-date:
http://forum.xda-developers.com/showthread.php?t=1377410
http://forum.xda-developers.com/showthread.php?t=1337722
This tutorial below is form a different forum posted originally by DRGilroy (at Team BAMF Forums). This particular post is not available and I have copied it from Google's cached version: BUT ALL CREDIT GOES TO DRGilroy:
[How To] Customize Auto Brightness
I've created my own Auto Brightness Mods for people to use and I thought I would help those out who are interested in creating their own.
I learned how to do it myself by searching and finding tutorials here and there in different posts and forums. Some of what I found was either not detailed enough or had incorrect instructions for the version of APK Manager I am using. So, most of what I'm going to do here is just reiterate what someone else has already written out there somewhere in the world wide web.
Tools:
APK-Manager v5.0.2 (versions earlier than 5.0 behave differently so instructions would be somewhat different if your attempting to use one of them)
Notead++
7-Zip
Instructions for Creating Your Own Custom Auto Brightness Levels:
Extract the file "framework-res.apk" from your favorite ROM. You can find it in /system/framework/
Copy the framework-res.apk file into the APK Manager directory "place-apk-here-for-modding"
Execute the Script.bat file in the root of the APK Manager directory
Type option "9" and press Enter to Decompile the framework-res.apk file
Leaving the Command Window open, with Notepad++ open the file "arrays.xml" found under "\projects\framework-res.apk\res\values"
Find and edit the following *values:
<integer-array name="config_autoBrightnessLcdBacklightValues">
<item>94</item>
<item>94</item>
<item>94</item>
<item>94</item>
<item>143</item>
<item>143</item>
<item>171</item>
<item>199</item>
<item>227</item>
<item>255</item>
</integer-array>
<integer-array name="config_autoBrightnessLcdBacklightValuesUp">
<item>94</item>
<item>94</item>
<item>94</item>
<item>94</item>
<item>143</item>
<item>143</item>
<item>171</item>
<item>199</item>
<item>227</item>
<item>255</item>
</integer-array>
<integer-array name="config_autoBrightnessLcdBacklightValuesDown" >
<item>94</item>
<item>94</item>
<item>94</item>
<item>94</item>
<item>143</item>
<item>143</item>
<item>171</item>
<item>199</item>
<item>227</item>
<item>255</item>
Save your edits and close Notepad++
Reopen the Command Window and Type option "11", press Enter to Compile apk
When asked "Is this a system apk (y/n)" type "y" and press Enter
When asked "Aside from the signatures, would you like to copy... (y/n)" type "y" and press Enter
When prompted with "Press any key to continue . . .", Leaving the Command Window open, Navigate to the APK Manager directory "keep" and delete the file "resources.arsc"
Reopen the Command Window and now press any key to continue
Type option "22" and press Enter to Set current project
Select the newly compiled unsignedframework-res.apk file, it should be number 2, type "2" and press Enter
Take note of the "Current-App:" unsignedframework-res.apk should be shown on the upper right corner of the Command Window
Type option "5" and press Enter to Zipalign apk
At this point you can close the Command Window
Copy the file "unsignedframework-res.apk" from the APK Manager directory "place-apk-here-for-modding" and rename it to framework-res.apk
Congratulations, you now have a framework-res.apk that has your own custom Auto Brightness values!
Now what do you do with the framework-res.apk file?
There are a couple things you can do with the file.
You can use ADB to push your new framework-res.apk to the phone
You can create a flashable Zip using the UOT Kitchen website
You can use an existing flashable Zip that contains a framework-res.apk file and replace it with yours
I'll throw you a bone and you can use my flashable zip below, Yes, I'm just that nice!
bamf_forever_1.0.8_auto_brightness_1.0.zip
Brightness: 31, 31, 59, 87, 115, 143, 171, 199, 227, 255
MD5: A1360E982CE401E9302929D527BC3641
*Brightness Values Explained
The following numbers represent the light sensors steps for using brightness:
11, 41, 91, 161, 226, 321, 641, 1281, 2601
The following numbers are the stock values that I mod and they represent the level of brightness, lowest to highest in ten level steps:
94, 94, 94, 94, 143, 143, 171, 199, 227, 255
Example:
Light Sensor___Brightness
10---------------94
40---------------94
90---------------94
160--------------94
225--------------143
320--------------143
640--------------171
1280-------------199
2600-------------227
Higher------------255 = Max
You can use a free app on the Market called AndroSensor. It can provide you with the value of how much light the sensor is detecting.
In my testing, it appears to me that brightness values lower than 30 do not cause the backlight to dim any further. Also, when connected to a charger with battery charging, the light sensor doesn't go lower than 40 until the battery is fully charged, then it will lower to 10.
Then there is this http://forum.xda-developers.com/showpost.php?p=24437288&postcount=29
After all this there are free apps: I am using LogGraph.......
Good Luck !!

call me crazy but why bother. there are three options, I always just use dim to save battery, but occasionally ill go full bright when viewing a photo or something.

edgex said:
call me crazy but why bother. there are three options, I always just use dim to save battery, but occasionally ill go full bright when viewing a photo or something.
Click to expand...
Click to collapse
This phone has a great screen that clearly is the major selling point for it. Why ruin the screen under sub optimal conditions?
I am actually running mhx's full bloat stock ROM, and am loving the screen......... but I am restricted to this if I want the full visual experience. It is a little like buying HDTV for watching only 480p programming.
also automatic brightness when executed properly makes viewing under changing light conditions so much more smoother and pleasurable..
Well........that's just my opinion, not really complaining since a custom room is better than ATT cares to give us and I am thankful For that.

[APP][2.2+]Yet Another Auto Brightness

Yet Another Auto Brightness (YAAB)
A small open source application designed to enhance user control over screen brightness. Initially it was developed to make the screen as dim as possible to save battery on old devices. AND to provide a simplest possible user interface without any complicated calibration procedures and so on.
It is Beta version now. It has ascetic interface and very simple in use.
Source code, issue tracker and latest APKs are available here: http://bitbucket.org/gyrussolutions/yaab/
Google Play link: https://play.google.com/store/apps/details?id=biz.gyrus.yaab
Any feedback is highly appreciated, especially from other Android developers

Tester initial impressions
A nice small download and a simple and clean interface. Started service and it immediately started dimming my brightness. A few points to begin with:
The manual slider does not seem to work as there was no change in the brightness.
It doesn't seem to alter the brightness in different lighting (unsure if it is supposed to do this or not from documentation).
It is making my screen too dim, I have a GT-I9300 and the auto brightness on it is excellent and always keeps my screen at the good readable and useable settings.
Will run for an hour or so now and update this with further thoughts then.
---------- Post added at 05:13 PM ---------- Previous post was at 05:06 PM ----------
Ok it's keeping my screen to dim to be usable so have had to uninstall for now. A few further points though:
Application Force Closes when you stop the serverce.
The manual slider does not work.
Handset - GT-I9300
ROM - Paranoid Android 2.51
OK log wouldn't upload, here's a link for it on dropbox.
https://www.dropbox.com/s/mbyfz33b7audtxz/2012-11-02-17-10-36.txt

Good report, thanks a lot.
Looks like the app incorrectly reads light sensor data on your device and thus brings brightness to minimum.
I'm working on the issue now.

andrvo said:
Good report, thanks a lot.
Looks like the app incorrectly reads light sensor data on your device and thus brings brightness to minimum.
I'm working on the issue now.
Click to expand...
Click to collapse
Let me know when you have a new version and will test again for you.

Hi!
IIIIkoolaidIIII said:
Let me know when you have a new version and will test again for you.
Click to expand...
Click to collapse
I did some research tonight and found out that many people have concerns about light sensor behaviour in your ROM.
I wrote a very simple app that shows sensor parameters on the screen and displays all subsequent updates received from the sensor.
APK is here: https://bitbucket.org/gyrussolutions/lightreader/downloads (sources are available there also)
It doesn't require changing settings and it will not attempt to change screen parameters also. Minimal discomfort
Could you please run it on your device and post here its output in a dark room and under strong light?
Thanks.

andrvo said:
Hi!
I did some research tonight and found out that many people have concerns about light sensor behaviour in your ROM.
I wrote a very simple app that shows sensor parameters on the screen and displays all subsequent updates received from the sensor.
APK is here: https://bitbucket.org/gyrussolutions/lightreader/downloads (sources are available there also)
It doesn't require changing settings and it will not attempt to change screen parameters also. Minimal discomfort
Could you please run it on your device and post here its output in a dark room and under strong light?
Thanks.
Click to expand...
Click to collapse
Details bellow, Sensor name - CM36651 Light sensor
Darkened Room:
Accuracy 3, MAX 121240, last 0.0
Bright light:
Accuracy 3, MAX 121240, last 3700.0 (fluctuating around this point)
I've not read much in relation to sensor issues on this ROM, will do some digging myself now. Hope this information is useful to you.
B
---------- Post added at 11:05 AM ---------- Previous post was at 10:48 AM ----------
I have just done some digging and found no Liight sensor issues mention in the CM10 threads or known bug list. There was a light sensor issues back in September for Paranoid Android but this was fixed back then. Where have you seen the information about peoples concerns with the light sensor?
I have attached a link to the CM10 known issues bellow.
http://teamhacksung.org/wiki/index.php/CyanogenMod10:GT-I9300:Nightly:Known_issues

I saw several mentiones of light sensor problems here on the forum, like this: http://forum.xda-developers.com/showpost.php?p=31801837&postcount=2862 or this http://forum.xda-developers.com/showpost.php?p=31801837&postcount=2862
Some other mentiones on other forums/blogs.
But anyway your readings are very good, so the sensor isn't a culprit any longer.
I just had to make sure that the app has valid input data and the problem is somewhere in the algorythms. Because in the log file you submitted yesterday contains very strange values.
Thanks again. I'm going on with my investigation.

andrvo said:
I saw several mentiones of light sensor problems here on the forum, like this: http://forum.xda-developers.com/showpost.php?p=31801837&postcount=2862 or this http://forum.xda-developers.com/showpost.php?p=31801837&postcount=2862
Some other mentiones on other forums/blogs.
But anyway your readings are very good, so the sensor isn't a culprit any longer.
I just had to make sure that the app has valid input data and the problem is somewhere in the algorythms. Because in the log file you submitted yesterday contains very strange values.
Thanks again. I'm going on with my investigation.
Click to expand...
Click to collapse
Yeah those were two months ago and the bug was fixed in a few days, there have been about 10 version updates since then as well.
Let me know when you're new version is available and will test again.
B

Maybe you should restrict app installation to devices that have a light sensor? Because Google Play allows me to install it even tho I don't have one.

HTC Wildfire S (Marvel)
Works as intended on HTC Wildfire S (Marvel) 510e.
Brightness is applied 1/2 secconds after screen is on and with correct levels acording to the external light and manual adjusment seting.
I like the simplicity (pls don't change that) and, so far, I didn't noticed any bad impact on battery life.
I'm curently on custom SENSE 2.1 rom but I switch often so will test this one on them too.
Tnx,

GermainZ said:
Maybe you should restrict app installation to devices that have a light sensor? Because Google Play allows me to install it even tho I don't have one.
Click to expand...
Click to collapse
Will be done, thanks. I don't know how could I have missed that

kobredabre said:
Works as intended on HTC Wildfire S (Marvel) 510e.
Brightness is applied 1/2 secconds after screen is on and with correct levels acording to the external light and manual adjusment seting.
I like the simplicity (pls don't change that) and, so far, I didn't noticed any bad impact on battery life.
Click to expand...
Click to collapse
Thanks for the update.
We are working on automatic/manual "night reading" mode and manual range adjustments now, but we intend to keep the main screen and the defaults in this way, so most of the users would not even need to open menus and dig deeper into the settings.

IIIIkoolaidIIII said:
Let me know when you're new version is available and will test again.
Click to expand...
Click to collapse
I've uploaded current version to the downloads section: https://bitbucket.org/gyrussolutions/yaab/downloads
Check this one please when you have time.
To be honest I still don't know why did it set brightness to minimum on your phone and didn't ever rise it again.
But your log revealed a number of thread synchronization issues that I fixed in this version. I believe there could be connection between these issues and your dark screen.
UI is a bit different, it is my current development version. But start/stop buttons still do the same.
Don't wait long, 10-15 seconds is enough, if it doesn't track ambient light changes right from the beginning - it will not start after some minutes.
Thanks.

Hi andrvo,
Yaab works on my Nexus 7. It is also very easy to use. But I have two remarks.
First the app starts in portrait and I only use me tablet in horizontal view. The app not only starts in portrait, it does also not change to horizontal. This would be nice, if the app would start with mentioning the position.
The other point is, that it only needs one more option in my case. There is automatic and manual brightness. If I can use the manual slider in the automatic mode to set a basic brightness, this would be handy. Hope you know what I mean.
Thanks for your work. Would be nice to find Yaab on Google Play to get updates automatically.

Thanks, checking it out...

benkxda said:
First the app starts in portrait and I only use me tablet in horizontal view. The app not only starts in portrait, it does also not change to horizontal. This would be nice, if the app would start with mentioning the position.
Click to expand...
Click to collapse
Yes, it is my fault. I didn't have enough time to test those layouts on tablets.
I plan creating layouts for tablets from scatch since existing were designed mostly for phones.
benkxda said:
The other point is, that it only needs one more option in my case. There is automatic and manual brightness. If I can use the manual slider in the automatic mode to set a basic brightness, this would be handy. Hope you know what I mean.
Click to expand...
Click to collapse
Well, it works almost as you describe. "Manual adjustment" actually set the base line for the automatic brightness formula.
I'm preparing new release right now, will be available today or tomorrow. New version also allows to limit top and bottom values of brightness, maybe it will fit your need
benkxda said:
Thanks for your work. Would be nice to find Yaab on Google Play to get updates automatically.
Click to expand...
Click to collapse
It is here: https://play.google.com/store/apps/details?id=biz.gyrus.yaab

Test it on Galaxy Note 2
Everything looks working. Closing the sensor with my hand causing the screen light dim.
Not sure what idea I can give though, probably you can check 'smart stay' feature at Samsung S3/Note 2. Although it's not a screen auto-brightness thing but it have same objective about saving battery from screen consumption.

andrvo said:
Yes, it is my fault. I didn't have enough time to test those layouts on tablets.
I plan creating layouts for tablets from scatch since existing were designed mostly for phones.
Well, it works almost as you describe. "Manual adjustment" actually set the base line for the automatic brightness formula.
I'm preparing new release right now, will be available today or tomorrow. New version also allows to limit top and bottom values of brightness, maybe it will fit your need
It is here: https://play.google.com/store/apps/details?id=biz.gyrus.yaab
Click to expand...
Click to collapse
That new release I get then via Play, thanks for that. Delighted me.

jimmod said:
Test it on Galaxy Note 2
Not sure what idea I can give though, probably you can check 'smart stay' feature at Samsung S3/Note 2. Although it's not a screen auto-brightness thing but it have same objective about saving battery from screen consumption.
Click to expand...
Click to collapse
Ok, I'll check it, thanks.

Version 1.6 is rolling out to the Play store.
What's new:
night mode, manual and automatic. The latter will work only on new devices with high quality sensors which are able to provide accurate values in the lower part of the range. Manual works on any device.
range controls added. Now it is possible to shrink the actual range of automatic brightness values.
bugfix (of course)
Beta testing is still going on, all testers are welcome.
Fresh APK is also available here: https://bitbucket.org/gyrussolutions/yaab/downloads

[Q] Tilt sensor is off for some apps, possible fix?

Before my Asus tf700 Infinity, I owned a Samsung Galaxy Tab. I purchased some programs and games for it, and all was well until it was stolen. The problem? Now I've downloaded and used those same apps on my tf700 Infinity, and the orientation is off by ninety degrees on quite a few. It has to do with Android's API and Honeycomb, and how the default base orientation is set in the framework policy. Before tablets, the default orientation for the Android API was portrait, but tablets made landscape defaults a possible better default. Apps not written to accommodate this would have the sensors read 90 degrees skewed for landscape default devices (like my tf700), because the sensor data is being read from landscape (regardless of orientation), but interpreted as portrait by the app. Even though my Galaxy Tab was a tablet, it's default orientation was portrait, so there was no 90 degre skew. I have read enough to know that it's possible to change the Android system default value, but it has to be changed in the framework . . . No easy task, especially if the rom is ODEXed.
So . . . anyone have any advice or fix so my paid apps aren't wasted money? I don't think emailing every single developer is the key, when I could modify a single system value to fix the problem for all apps. Thanks in advance, any help is appreciated.

Doesnt ever gyro-based app/game have a recalibration setting? Have you tried that?
Send From My Samsung Galaxy S3 Using Tapatalk 2

GrayHat137 said:
So . . . anyone have any advice or fix so my paid apps aren't wasted money?
Click to expand...
Click to collapse
You could try Ultimate Rotation Control. It can have an individual setting for each application (Forced Portrait/Forced Landscape/Forced Auto).

ShadowLea said:
Doesnt ever gyro-based app/game have a recalibration setting? Have you tried that?
Send From My Samsung Galaxy S3 Using Tapatalk 2
Click to expand...
Click to collapse
The problem is that the data the app is getting is from the sensors is rotated 90 degrees. For example, if the app assumes the tilt data it is getting is from the left and right: tilt left, go left. On my tablet, it's default boot state is landscape, so if the app is asking for the sensor info the wrong way (a deprecated way - from before the Honeycomb API), it's getting the tilt axis from the top and bottom, so: tilt up, go left. I can calibrate, but I still have to tilt up to go left.

Sounds like badly programmed apps to me. Have you tried asking the devs to update based on the correct APIs?

HeartWare42 said:
You could try Ultimate Rotation Control[/URL]. It can have an individual setting for each application (Forced Portrait/Forced Landscape/Forced Auto).
Click to expand...
Click to collapse
I had hoped it would override the default framework, but apps were still polling the sensors wrong no matter which orientation they were displayed in. The sensor data was rotating the same amount as the app, but the original sensor data was still originally off by 90%.
Thanks for the tip; Ultimate Rotation Control is a good app that solved another issue I had, just not this one.

sbdags said:
Sounds like badly programmed apps to me. Have you tried asking the devs to update based on the correct APIs?
Click to expand...
Click to collapse
Yes, that's the consensus. Some I've asked, others are no longer in active development (nostalgia for holding onto these apps). I stumbled upon a web hit while googling for answers, the solution was about changing a simple setting in the android framework, but I'm a not experienced with ADB, and things like ODEXing and DeODEXing are nerve-wracking while I learn and experiment.
Also, thanks for coming sbdags. Running Xenogenesis since late April, fantastic job! :good:

GrayHat137 said:
Yes, that's the consensus. Some I've asked, others are no longer in active development (nostalgia for holding onto these apps). I stumbled upon a web hit while googling for answers, the solution was about changing a simple setting in the android framework, but I'm a not experienced with ADB, and things like ODEXing and DeODEXing are nerve-wracking while I learn and experiment.
Also, thanks for coming sbdags. Running Xenogenesis since late April, fantastic job! :good:
Click to expand...
Click to collapse
Which part of the framework do you need to change?

sbdags said:
Which part of the framework do you need to change?
Click to expand...
Click to collapse
Navigate to the androidpolicy\com\android\internal\policy\impl folder and open PhoneWindowManager.smali in your favorite text editor (Notepad++ is my favorite)
Search for the method "rotationfororientation"
(Picture of code here)
Make note of the variables (v#) for portrait and landscape (in my case portrait is v5)
Scroll to the end of the method and you should find something like:
"move v2, v5" (make sure it's the last move command before the end of the method)
Change the second variable (in this case v5) to whatever orientation you wish to be default. In my case I have set portrait as the default orientation.
Click to expand...
Click to collapse
There are other steps, but this is the only variable changed. I can't post links yet, and I didn't want to copy all of the text there, but that's it. The attached picture is the picture of the code.

Eureka!
GrayHat137 said:
There are other steps, but this is the only variable changed. I can't post links yet, and I didn't want to copy all of the text there, but that's it. The attached picture is the picture of the code.
Click to expand...
Click to collapse
Dear friends,
As I was also facing the same problem in my Ubislate 7C+(EDGE) tab by DATAWIND. While reading your post an idea struck to my mind. With the help of Root Browser app I navigated to /system/build.prop, opened it in text editor and in "ADDITIONAL_BUILD_PROPERTIES" changed the value of "ro.sf.hwrotation=270" 270 to 180 saved it and rebooted the tablet. Yes! the problem was solved but it created a new problem that the orientation of animation while boot and camera orientation has changed now but in order to rectify it I pulled bootanimation.zip to my computer and after unzipping it changed the orientation of animation files from portrait to landscape. Changed the orientation in 'desc.txt' from 480 800 to 800 400 and zipped both without any compression. Pushed it back to /system/media and changed the permission, user,group to original one with the help of root browser. Then for camera orientation with the help of root browser I navigated to /system/etc/camera.cfg opened it in RB text editor and changed camera orientation from 90 to 0, saved it and rebooted my tablet and now all the games using gsensor tilt are working fine.
Thanks,:good:

rotation gyro off
I had the same problemen, i resolved it by going to setting, location and then status (only GPS) then i started GPS tools , just waited a min or so . now everthing is oké again.
I hope thuis helps you

[APP][OPEN SOURCE][ROOT][5.0+] Night Light (KCAL)

Night light is an open-source app which uses KCAL to adjust blue light intensity of the display colors, so that viewing the screen at dark becomes pleasant for the eyes, and help you fall asleep faster (this is what science have proven so...).
Features
Easy to use user interface. Settings are easier to find.
Uses KCAL to adjust screen RGB colors, hence its efficient and changes are seen everywhere on screen.
Supports older KCAL implementations as well as newer KCAL implementation for v4.4 kernels.
Simple color controls for normal users through color temperature control.
Manual KCAL controls for advanced users.
Automation routines lets you define routines where you specify Night Light settings which you wish to apply, and they will be automatically applied for you in specified times.
Intensity fading in/out is supported as part of automation routines.
Supports sunset/sunrise timings.
Set on boot delay.
Original KCAL settings of user is backed up and applied when night light is turned off. And it can be configured as well.
Support for user profiles, which are collections of settings that user can apply with one click.
And to fulfill your all kinds of automation needs, app is supported as a Tasker plugin. You can use it with Profiles.
Option to automatically disable Night Light in lock screen, and turn it back on after the device is unlocked.
Quick Setting tile for easy toggling on/off night light anywhere.
Launcher icon shortcut for toggling Night Light on/off and toggling intensities.
Dark and Light theme.
Advantages
No overlays.
Background service is only used for lock screen option. The entire automation (including the fading) is done using neat AlarmManager tricks (which not only is battery friendly, but memory friendly as well).
Requirements
Kernel supporting KCAL.
Root access.
Download
Source - https://github.com/corphish/NightLight

Wow. Thanks for this awesome app. This is my best daily night light app.

Thanks

sounds good
let me have a try brother......
corphish said:
Night light is an open-source app which uses KCAL to adjust blue light intensity of the display colors, so that viewing the screen at dark becomes pleasant for the eyes, and help you fall asleep faster (this is what science have proven so...).
Features
Easy one touch toggles, with a single slider to tweak blue light intensity.
Quick Setting tile for easy toggling on/off night light anywhere.
Automatic switching on/off night light at user specifed timings. (Limitation - Start time must be lesser in value than ending time, that is if you choose starting time at 2300 hrs and ending time at 0600 hrs (next day) it won't work for now).
Requirements
Kernel supporting KCAL.
Root access.
Download
Source - https://github.com/corphish/NightLight
Click to expand...
Click to collapse

The automatic switch doesn't seem to be reliable. Could you add intents so it can be toggled with Tasker? I already have a profile that triggers at sunset so that would be perfect.
Sent from my Nexus 5X using XDA Labs

Great app, thanks. Have been using CF.lumen until now, but that seems unsupported (and is closed source).
Please keep improving it. Would also like to donate a beer.

Can you explain whats this KCAL thing ??? ??

thanks for this app apreciate it i got ADD and Slightly Autism and i already have an issue sleeping my brain get supercharged and i can't get to sleep but this app helps [email protected]

Loving the app so far, however, I notice it won't trigger at the time I have set unless I manually open the app. I've removed it from Android's battery optimization so I don't think that can be it. Any ideas?

rickysidhu_ said:
Loving the app so far, however, I notice it won't trigger at the time I have set unless I manually open the app. I've removed it from Android's battery optimization so I don't think that can be it. Any ideas?
Click to expand...
Click to collapse
Same here. I forgot to report it. I use Tasker to launch it at sunset & sunrise along with switching between dark / light app themes.
Sent from my Nexus 6P using XDA Labs

yochananmarqos said:
Same here. I forgot to report it. I use Tasker to launch it at sunset & sunrise along with switching between dark / light apo themes.
Click to expand...
Click to collapse
I ended up doing this as well! Now the other thing I'm hoping gets implemented is a smooth transition to the orange hue.

zaibansari20 said:
Can you explain whats this KCAL thing ??? [emoji848][emoji848]
Click to expand...
Click to collapse
Kcal is a kernel tweak that lets you customize colors at lower (kernel) level, so there won't be any filter or layer on screen, but in most stock kernels it isn't available, so you have to find a custom kernel for your phone/rom that has it.
Thanks for the app, but I've used tasker with the command "echo 180 75 35> /sys/devices/platform/kcal_ctrl.0/kcal" for a long time (echo 256 256 256 > /sys/devices/platform/kcal_ctrl.0/kcal to get the color back.)
Obviously you can change the values to whatever you want.
But the app will be much more easy for many people
Envoyé de mon ONEPLUS A5000 en utilisant Tapatalk

J0kker said:
Kcal is a kernel tweak that lets you customize colors at lower (kernel) level, so there won't be any filter or layer on screen, but in most stock kernels it isn't available, so you have to find a custom kernel for your phone/rom that has it.
Click to expand...
Click to collapse
I'm using LineageOS with a custom kernel which allows mein to change RGB values from any kernel modification app...
Sent from my LG G2 using XDA Labs

zaibansari20 said:
I'm using LineageOS with a custom kernel which allows mein to change RGB values from any kernel modification app...
Click to expand...
Click to collapse
So it should work for you, you can try with a kernel manager like kernel adiutor but the app should work.

J0kker said:
Kcal is a kernel tweak that lets you customize colors at lower (kernel) level, so there won't be any filter or layer on screen, but in most stock kernels it isn't available, so you have to find a custom kernel for your phone/rom that has it.
Thanks for the app, but I've used tasker with the command "echo 180 75 35> /sys/devices/platform/kcal_ctrl.0/kcal" for a long time (echo 256 256 256 > /sys/devices/platform/kcal_ctrl.0/kcal to get the color back.)
Obviously you can change the values to whatever you want.
But the app will be much more easy for many people
Envoyé de mon ONEPLUS A5000 en utilisant Tapatalk
Click to expand...
Click to collapse
I tried the Tasker method and it works great. I had no idea that command existed and could be used in Tasker. Thank you for sharing! :good: :highfive:

rickysidhu_ said:
Loving the app so far, however, I notice it won't trigger at the time I have set unless I manually open the app. I've removed it from Android's battery optimization so I don't think that can be it. Any ideas?
Click to expand...
Click to collapse
Does it fail to trigger if a reboot had happened sometime before the time it should have triggered?
For example, if it was to trigger at 5pm, but a device reboot happened in, say, 3pm, then does it fail to trigger at 5pm?
Anyway, set on boot is broken (again), will need to fix it, but normal timers should work fine.

corphish said:
Does it fail to trigger if a reboot had happened sometime before the time it should have triggered?
For example, if it was to trigger at 5pm, but a device reboot happened in, say, 3pm, then does it fail to trigger at 5pm?
Anyway, set on boot is broken (again), will need to fix it, but normal timers should work fine.
Click to expand...
Click to collapse
Ahh, that might be it. I think it stops working after a reboot, so I'd be going back into the app to get it going again.
Very minor issue though, great app - thank you for your hard work!!:highfive:

corphish said:
Does it fail to trigger if a reboot had happened sometime before the time it should have triggered?
For example, if it was to trigger at 5pm, but a device reboot happened in, say, 3pm, then does it fail to trigger at 5pm?
Anyway, set on boot is broken (again), will need to fix it, but normal timers should work fine.
Click to expand...
Click to collapse
Launcher shortcut (toggle on/off) switch is also seems somewhat broken, it toggle on but fails to toggle off.

@jineshpatel30 @rickysidhu_
Here is an experimental version (in the attachment of this reply), with launcher shortcut toggle and set on boot fixed.
The reason why it is experimental :
- Now written in kotlin
- Uses some of the new stuff announced in I/O 18, like ktx and the new material design style
- Uses different font called 'Acme'. (Feel free to suggest fonts)
- I decided to ditch cards because normal layouts look better in this new style.
Source - https://github.com/corphish/NightLight/tree/p

corphish said:
@[email protected]_
Here is an experimental version (in the attachment of this reply), with launcher shortcut toggle and set on boot fixed.
The reason why it is experimental :
- Now written in kotlin
- Uses some of the new stuff announced in I/O 18, like ktx and the new material design style
- Uses different font called 'Acme'. (Feel free to suggest fonts)
- I decided to ditch cards because normal layouts look better in this new style.
Source - https://github.com/corphish/NightLight/tree/p
Click to expand...
Click to collapse
It kicked in automagically at sunset tonight which reminded me to come back and comment. That was unreliable previously.
What does the save button do at the bottom? I assume it saves something, but there's no toast message to acknowledge it's been pressed.
I don't like the font, myself. Since you're going for new and fancy code and styling, why not use ProductSans? I like the new font used in the Wear OS app, I think that's it.
Could you add the numerical values for the sliders for more accurate fine tuning? I like the way the new XDA Navigation Gestures app does it. It's in the latest beta posted in the thread and should be pushed to the Play Store soon.
Since CF.lumen is EOL now, this app is going to be a great alternative especially when it eventually breaks.
Thank you!
Sent from my Nexus 6P using XDA Labs