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

[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

[apk][mod] Lcamera with longer exposure times for crazy night pictures

Hey everyone!
As some of you might know, the nexus 5x and nexus 6p cameras have a maximum exposure time in manual mode of 1/4.3 seconds, which is a real shame. Somebody suggested that Google made this choice because of the bigger size of the pixels, nonetheless the resulting pictures in very low light are not satisfying and none of the apps on the play store overrides the limit of 1/4.3 seconds.
So, I managed to unlock longer exposure times (up to 5 seconds) on the nexus 5x camera to take some truly unbelievable night pictures. Since the sensor is the same, this app should work also on the nexus 6p and it might work even on other devices with at least android 5.0. It also probably works on the nexus 5, but doesn't appear to be working on the nexus 6.
A big thank to PkmX for developing the original app Lcamera and to CazeW for his suggestions.
Notice that the photos will be upside down, because the sensor is mounted upside down (at least in the nexus 5x). Just rotate them with your favorite photos editor. Also notice that the "screen refresh time" is the one of the exposure, so when you set an exposure of e.g. 3 seconds, the app will look like if it's stuck and refresh every 3s.
I am not responsible for any damage that your phone might report. I've been using this app for a long time and everything works fine.
You can download the .apk file and the source code at the bottom. To install the app you only need the .apk file, the source code is for developers who wish to improve the code.
Check the difference between a manual camera downloaded from the play store and my app (the pics are resized here).
Click on the images to enlarge.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
How did I do it?
I exploited the fact that the older versions of Lcamera by PkmX allowed up to 1/1.2 seconds of exposure time (probably because the nexus 5x wasn't supported yet), so I downloaded the source of lcamera 0.3 by PkmX, modified a few lines of code and compiled it.
The exposure times of my modded app are: 5s, 4s, 3s, 2s, 1.5s, 1s, 0.5s, 0.23 s, ... and so on, up to 1/120000 s (the default minimum value) and you can change them in the settings of the app.
Why not more than 5 seconds?
Because the app gets really unstable, since those exposure times are not officially "hardware" supported.
EDIT: a user suggested here that the app might be stable for even longer exposures with a longer kernel readahead.
Beware that the app can be unstable even with exposure times longer than 3 seconds: if it starts crashing, just terminate it in the settings. I usually set the exposure time back to 1/10 s every time I close the app, otherwise the following times it might just crash when entering in it.
Therefore, with this app you can get some beautiful night pictures, the drawback is that sometimes it might be unstable (because those exposures are not hardware supported).
What did I modify?
In src/pkmx/lcamera/MainActivity.scala I've modified lines 417, 419, 693 and deleted the line 1083. You can download my source code at the bottom, the original source code from github and compare them, to see in more detail which are the differences.
I've also modified the app icon with one that I've personally designed.
Thank you and have fun

The first one is Google camera and the second is from your app

TW1ST3D1NS4N3 said:
The first one is Google camera and the second is from your app
Click to expand...
Click to collapse
In my app, tap on the magenta settings button, then on exposure and then de-select "Auto Exposure" and decrease the value of shooting time from 1/10 to something like 1-2, you will see what a difference.

Thanks for this.
Is it possible to force ISO to a lower value than 60?
Sent from my Nexus 5X using Tapatalk

oldskuler said:
Thanks for this.
Is it possible to force ISO to a lower value than 60?
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
Well, in the app the lowest possible iso is set to 40, but the camera doesn't go below 60, so I think it's not possible. Anyway 60 is already very low and the noise shouldn't be much, so I don't know if an even lower iso would actually bring some benefits.

Good job. Some questions and tips for your code. Haven't tried the app though as my phone is getting repaired.
Why use a base of 60s? Wouldn't it have been easier to just use a 10s base instead of 60s for val exposureTime? Then you would only have needed to multiply the values by 10 in exposureTimeMap instead of 60 (and also add your values, 2 for 5s, 2.5 for 4s and so on). You also seem to be missing the base 1/60s exposure, don't know if that matters though.
Remove the line prefs.exposureTimeIndex = exposureTimeIndex() from onStop(), this will stop the manual exposure getting saved when closing the app (hence you don't need to change it back before closing).
Try replacing the line (not sure if this code will work but you probably notice what I'm trying to do)
Code:
observe { exposureTimeIndex foreach { v => text = s"60/${new DecimalFormat("#.#").format(exposureTimeMap(v))}" } }
with
Code:
observe { exposureTimeIndex foreach { v => text = if (v > 5) s"1/${new DecimalFormat("#.#").format(exposureTimeMap(v)/60)}" else s"${new DecimalFormat("#.#").format(60/exposureTimeMap(v))}s" } }
for a nicer display of the exposure times. Obviously change the value of 60 if you decide to change the base value.
EDIT: You should also be able to fix the rotation by implementing this commit in your code. Might also know how to "fix" the preview as well so the refresh rate doesn't go below a certain rate, but don't want to take away all the fun from you.

Nice, should be great for shooting auroras.

So flash the source first then install apk? Apk alone would not take a picture.

Travisdroidx2 said:
So flash the source first then install apk? Apk alone would not take a picture.
Click to expand...
Click to collapse
Source is the sourcecode of the apk...
You don't have to flash anything,

CazeW said:
Why use a base of 60s? Wouldn't it have been easier to just use a 10s base instead of 60s for val exposureTime? Then you would only have needed to multiply the values by 10 in exposureTimeMap instead of 60 (and also add your values, 2 for 5s, 2.5 for 4s and so on). You also seem to be missing the base 1/60s exposure, don't know if that matters though.
Remove the line prefs.exposureTimeIndex = exposureTimeIndex() from onStop(), this will stop the manual exposure getting saved when closing the app (hence you don't need to change it back before closing).
Try replacing the line (not sure if this code will work but you probably notice what I'm trying to do)
Code:
observe { exposureTimeIndex foreach { v => text = s"60/${new DecimalFormat("#.#").format(exposureTimeMap(v))}" } }
with
Code:
observe { exposureTimeIndex foreach { v => text = if (v > 5) s"1/${new DecimalFormat("#.#").format(exposureTimeMap(v)/60)}" else s"${new DecimalFormat("#.#").format(60/exposureTimeMap(v))}s" } }
for a nicer display of the exposure times. Obviously change the value of 60 if you decide to change the base value.
EDIT: You should also be able to fix the rotation by implementing this commit in your code. Might also know how to "fix" the preview as well so the refresh rate doesn't go below a certain rate, but don't want to take away all the fun from you.
Click to expand...
Click to collapse
Thank you for the suggestions! Well I choose a base 60 because it is divisible by 5,4,3,2,1, so I could avoid using "double" values for the exposures and I didn't have to worry about the digit precision, but yes I've modified the code as you suggested to have a better looking exposure time in the app, with some small differences; now it's like 5 s, 4 s, ..., 1/2 s, 1/4.3 s, ... and I've also modified a bit the shorter exposures and added back the 1/60 one.
I've also deleted the line that saves the exposure preference.
I've checked the rotation commit but it is for a newer version of Lcamera, so there are many differences in the code.
Of course any suggestion on how to fix it in my app or how to change the "screen refresh rate" is welcome , as long as it doesn't imply to modify more than a few (let's say 30) lines of code, unless you want to do it yourself.
tauio111 said:
Nice, should be great for shooting auroras.
Click to expand...
Click to collapse
Yes, also to shoot the night sky. Nice picture by the way!
tauio111 said:
Source is the sourcecode of the apk...
You don't have to flash anything,
Click to expand...
Click to collapse
Exactly

enryea123 said:
Thank you for the suggestions! Well I choose a base 60 because it is divisible by 5,4,3,2,1, so I could avoid using "double" values for the exposures and I didn't have to worry about the digit precision, but yes I've modified the code as you suggested to have a better looking exposure time in the app, with some small differences; now it's like 5 s, 4 s, ..., 1/2 s, 1/4.3 s, ... and I've also modified a bit the shorter exposures and added back the 1/60 one.
I've also deleted the line that saves the exposure preference.
I've checked the rotation commit but it is for a newer version of Lcamera, so there are many differences in the code.
Of course any suggestion on how to fix it in my app or how to change the "screen refresh rate" is welcome , as long as it doesn't imply to modify more than a few (let's say 30) lines of code, unless you want to do it yourself.
Click to expand...
Click to collapse
Looked closer at the commit and you're right, would take a bit of work to implement it in the older version.
I'm not sure but this might be the part that handles the refresh rate of the screen.
Code:
val startPreview =
for { (cameraOpt, previewSurfaceOpt, previewSessionOpt, autoFocus, focusDistance, autoExposure, iso, exposureTime, metering)
<- Rx {(this.camera(), this.previewSurface(), this.previewSession(),
this.autoFocus(), this.focusDistance(),
this.autoExposure(), this.iso(), this.exposureTime(), this.metering())}
Inside that for you could put in an if that checks if this.exposureTime() is less than for example 1/5s, then use a constant of 1/5s instead of this.exposureTime().
I also might have found a way to get the newer version to be able to use slower shutter speeds. The problem I think is this code on line 699.
Code:
val validExposureTimes = Rx { lcamera().toList flatMap { camera => exposureTimes filter { camera.exposureTimeRange contains _ }} }
Which is a list of exposure times the sensor supports. Now, if we set this equal to the var exposureTimes, I think we should be able to use the longer exposure times. I don't know if straight val validExposureTimes = exposureTimes works or if you have to convert the Vector to a List first, haven't programmed in scala before. I would try this out myself if I had a phone to test it on.

Thanks for the mod. Here are my results compared to Google's HDR+

CazeW said:
Looked closer at the commit and you're right, would take a bit of work to implement it in the older version.
I'm not sure but this might be the part that handles the refresh rate of the screen.
Code:
val startPreview =
for { (cameraOpt, previewSurfaceOpt, previewSessionOpt, autoFocus, focusDistance, autoExposure, iso, exposureTime, metering)
<- Rx {(this.camera(), this.previewSurface(), this.previewSession(),
this.autoFocus(), this.focusDistance(),
this.autoExposure(), this.iso(), this.exposureTime(), this.metering())}
Inside that for you could put in an if that checks if this.exposureTime() is less than for example 1/5s, then use a constant of 1/5s instead of this.exposureTime().
Click to expand...
Click to collapse
Well, I managed to set the preview to be updated every 1/10s by creating another variable "exposureTimePreview", BUT this way on the screen you don't see the actual brightness that the picture is going to have, but the one that it would have if the exposure time was actually 1/10, so it is not very handy and it's better to just leave it how it is now.
CazeW said:
I also might have found a way to get the newer version to be able to use slower shutter speeds. The problem I think is this code on line 699.
Code:
val validExposureTimes = Rx { lcamera().toList flatMap { camera => exposureTimes filter { camera.exposureTimeRange contains _ }} }
Which is a list of exposure times the sensor supports. Now, if we set this equal to the var exposureTimes, I think we should be able to use the longer exposure times. I don't know if straight val validExposureTimes = exposureTimes works or if you have to convert the Vector to a List first, haven't programmed in scala before. I would try this out myself if I had a phone to test it on.
Click to expand...
Click to collapse
That line of code only exists in the latest source code on github, I'm using an older version, which in fact doesn't have that line (this missing line is probably the reason I could select longer exposures). I can even set exposures longer than 5 seconds, if they are between 6 and 9 the phone is likely to crash, but if they are 10s or longer the camera just seems to get crazy and some weird "moving purple shapes" are displayed on the screen.

Dark Emotion said:
Thanks for the mod. Here are my results compared to Google's HDR+
Click to expand...
Click to collapse
Thanks for the feedback!

enryea123 said:
Well, I managed to set the preview to be updated every 1/10s by creating another variable "exposureTimePreview", BUT this way on the screen you don't see the actual brightness that the picture is going to have, but the one that it would have if the exposure time was actually 1/10, so it is not very handy and it's better to just leave it how it is now.
That line of code only exists in the latest source code on github, I'm using an older version, which in fact doesn't have that line (this missing line is probably the reason I could select longer exposures). I can even set exposures longer than 5 seconds, if they are between 6 and 9 the phone is likely to crash, but if they are 10s or longer the camera just seems to get crazy and some weird "moving purple shapes" are displayed on the screen.
Click to expand...
Click to collapse
That's why I suggested to use an if, so that when the exposure time becomes unreasonably long (like 1s or more) you use a constant refresh rate which would at least help with the framing. When the exposure time is faster, you of course use that as your refresh rate.
EDIT: You could also then bump up the ISO sensitivity for the preview so that you would still see the actual brightness of the picture (or at least close to it). For example, you want to take a picture that uses ISO 100 and 1s exposure. You lock the refresh rate at 1/4s and bump the ISO for the preview to 400 to compensate for the 2 stops slower refresh rate, and you should end up with an equally bright preview as what the picture will look like. (I think this is what most cameras do.)
I know that line of code only exists in the latest source code. What I meant is that if you edit that line, you might be able to use that version for your mod.

CazeW said:
That's why I suggested to use an if, so that when the exposure time becomes unreasonably long (like 1s or more) you use a constant refresh rate which would at least help with the framing. When the exposure time is faster, you of course use that as your refresh rate.
EDIT: You could also then bump up the ISO sensitivity for the preview so that you would still see the actual brightness of the picture (or at least close to it). For example, you want to take a picture that uses ISO 100 and 1s exposure. You lock the refresh rate at 1/4s and bump the ISO for the preview to 400 to compensate for the 2 stops slower refresh rate, and you should end up with an equally bright preview as what the picture will look like. (I think this is what most cameras do.)
I know that line of code only exists in the latest source code. What I meant is that if you edit that line, you might be able to use that version for your mod.
Click to expand...
Click to collapse
Thank you, I didn't understand what you meant. Those are some interesting improvements, I will consider them in the future for sure (right now I don't have much free time to spend on this project).

great job well done i was waiting for this
it would be great to add timer future to this app

enryea123 said:
In my app, tap on the magenta settings button, then on exposure and then de-select "Auto Exposure" and decrease the value of shooting time from 60/1000 to something like 60/60, you will see what a difference.
Click to expand...
Click to collapse
Sorry for the noob question. When turning off auto exposure you have two options to change. The s and iso, what do you recommend for both? I do not get the 60/60. Thank you for the mods. I am sure when I get it set correctly it will work great.

Travisdroidx2 said:
Sorry for the noob question. When turning off auto exposure you have two options to change. The s and iso, what do you recommend for both? I do not get the 60/60. Thank you for the mods. I am sure when I get it set correctly it will work great.
Click to expand...
Click to collapse
Let's first make sure of a couple things: do you have the nexus 5x? have you downloaded the last version of my app? To make sure you did, download it again now. (you get the "60/60" only in the old app, in the new one it is written as "1 s").
The "s" is the exposure time, which is the time the shutter will stay opened to capture the light (in fact the "s" stands for seconds). The iso is the sensitivity of the camera but it is directly related to noise (higher iso = higher noise).
So, I recommend to keep the exposure time as long as possible (like 3-4-5 seconds) and lower the iso until you get the right photo brightess.

enryea123 said:
Let's first make sure of a couple things: do you have the nexus 5x? have you downloaded the last version of my app? To make sure you did, download it again now. (you get the "60/60" only in the old app, in the new one it is written as "1 s").
The "s" is the exposure time, which is the time the shutter will stay opened to capture the light (in fact the "s" stands for seconds). The iso is the sensitivity of the camera but it is directly related to noise (higher iso = higher noise).
So, I recommend to keep the exposure time as long as possible (like 3-4-5 seconds) and lower the iso until you get the right photo brightess.
Click to expand...
Click to collapse
Thank you for explaining this. And yes I have the 5x and it is the new version of the app. Thank you for explaining this!

Optimal DPI

Hi,
what is optimal DPI in your opinion, for the OP7 Pro?
And how does variable screen resolution affect DPI set in settings? Times used to be easier when display resollution was fixed at 1080p. Do one needs to disable this autochanges in settings to keep table image size?
I used to have either 390 or 400 DPI set virtually all the time on my Oneplus 3, Oneplus 5 and Oneplus 6T... But with this unnecessarily high resolution that is, absurdly, used only sometimes, I would like to hear your experiences.
Thanks

In OOS, I use the "Small" setting in display which comes to 470dpi
In AOSP, it is probably pretty similar. I basically move the slider in display down one notch. I am not currently on AOSP so I'm not positive what that setting is or the actual dpi value.

Note 20 Ultra [email protected]

What are the odds you think we will have someone find a way to mod the device to run at full resolution and 120hz or at least 90/96hz at full resolution? I don't know if Samsung will ever allow some version of the high refresh rate on the device. We see that the SD version is capable of the feature. Exxynos as well, but battery may suffer more. I will get the phone regardless, but wouldn't mind knowing that someone out there would have a workaround. Haven't seen one for the s20 ultra yet. I do know about the single MIPI lane in the device..etc, but figured there may still have been some software way of enabling a slightly higher refresh rate if not all the way to 120hz.

I don’t believe the panels are capable

I don't think the limit is with the panel itself but driver/interface bandwidth.
But I'm sure there will be many discussions on ways to turn it on just like the S20Ultra!
Personally, I'm OK with a lower res @120Hz. There's only one app I use where I can actually see the difference @QHD and the overall fluid feel @120 everywhere to me is worth it. Not to mention the battery life hit.
Eventually, it will arrive. I'd say we're lucky to have it.

cpufrost said:
I don't think the limit is with the panel itself but driver/interface bandwidth.
But I'm sure there will be many discussions on ways to turn it on just like the S20Ultra!
Personally, I'm OK with a lower res @120Hz. There's only one app I use where I can actually see the difference @QHD and the overall fluid feel @120 everywhere to me is worth it. Not to mention the battery life hit.
Eventually, it will arrive. I'd say we're lucky to have it.
Click to expand...
Click to collapse
That is kind of my thought too. I run 120 on my S20 Ultra and have always really wondered if I could tell the difference between full HD+ and QHD. Personally I don't think I can tell the difference.

d_ganggreen said:
That is kind of my thought too. I run 120 on my S20 Ultra and have always really wondered if I could tell the difference between full HD+ and QHD. Personally I don't think I can tell the difference.
Click to expand...
Click to collapse
One thing I think everyone would notice. Lower SOT!
I've never tried running at HD+ 60Hz to see though. Battery life is pretty good at 120Hz.

cpufrost said:
I don't think the limit is with the panel itself but driver/interface bandwidth.
But I'm sure there will be many discussions on ways to turn it on just like the S20Ultra!
Personally, I'm OK with a lower res @120Hz. There's only one app I use where I can actually see the difference @QHD and the overall fluid feel @120 everywhere to me is worth it. Not to mention the battery life hit.
Eventually, it will arrive. I'd say we're lucky to have it.
Click to expand...
Click to collapse
Don't get me wrong, the phone is a beast and I do appreciate them adding it, but much like a lot of ppl online, I just wish it's that one little thing they would have done. Did you see the video below? Apparently snapdragon is capable, but Exxynos may be the culprit from us all getting the feature due to battery life? I only notice the extremely slight difference between the Full HD and WQHD and that's on text. Pics and videos all look the same to me. I don't mind FHD at all though
Here it is:-
https://youtu.be/xIl4h8R9to8

It would have been better to be capable of adjusting the resolution on the fly seamlessly without restarting the whole UI.
Coupled with Bixby Routine, we would be able to tune it for it to display higher resolution only when needed, per apps like games, camera and gallery.
Although i think i found somewhere on YouTube a test about resolution and SOT, which resulted that lowering the resolution doesn't do anything to increase the SOT.

There is a yt video (sakitech) showing how to set a bixby routine to keep phone at fhd+ 120hz all the time but to get changed to 4k (well 1440p afterall) upon opening any app you want (like yt). Watched the video, did the routine... not working. With yt opened i can see the Bixby routine notification on...but nothing happens. Yt will not offer me any res above 1080p to chose from. Any ideas?
Sent from my SM-T830 using Tapatalk

I did it.
Set adaptive smoothness at fhd+.
Install settings database editor from play store and follow instructions to grant app write secure settings permission.
In the app, select Global Table in the dropdown and find the "display_size_forced" line. Edit the value to "1440,3088". Then select Secure Table, find"defsult_display_size_forced" and set it to "1440,3088". Lastly, find "default_display_density_forced" and "display_density_forced" and set both to "600".

How the battery life after this?

tribalfs said:
I did it.
Set adaptive smoothness at fhd+.
Install settings database editor from play store and follow instructions to grant app write secure settings permission.
In the app, select Global Table in the dropdown and find the "display_size_forced" line. Edit the value to "1440,3088". Then select Secure Table, find"defsult_display_size_forced" and set it to "1440,3088". Lastly, find "default_display_density_forced" and "display_density_forced" and set both to "600".
Click to expand...
Click to collapse
Are you saying you got 120hz at running at QHD?

tribalfs said:
I did it.
Set adaptive smoothness at fhd+.
Install settings database editor from play store and follow instructions to grant app write secure settings permission.
In the app, select Global Table in the dropdown and find the "display_size_forced" line. Edit the value to "1440,3088". Then select Secure Table, find"defsult_display_size_forced" and set it to "1440,3088". Lastly, find "default_display_density_forced" and "display_density_forced" and set both to "600".
Click to expand...
Click to collapse
Great work.... I'm afraid Myself in trying...
how you guys know this stuff amazes me

tribalfs said:
I did it.
Set adaptive smoothness at fhd+.
Install settings database editor from play store and follow instructions to grant app write secure settings permission.
In the app, select Global Table in the dropdown and find the "display_size_forced" line. Edit the value to "1440,3088". Then select Secure Table, find"defsult_display_size_forced" and set it to "1440,3088". Lastly, find "default_display_density_forced" and "display_density_forced" and set both to "600".
Click to expand...
Click to collapse
Root required?
Cannot edit this value!

tribalfs said:
I did it.
Set adaptive smoothness at fhd+.
Install settings database editor from play store and follow instructions to grant app write secure settings permission.
In the app, select Global Table in the dropdown and find the "display_size_forced" line. Edit the value to "1440,3088". Then select Secure Table, find"defsult_display_size_forced" and set it to "1440,3088". Lastly, find "default_display_density_forced" and "display_density_forced" and set both to "600".
Click to expand...
Click to collapse
This works, thank you. However, some software, for example, wallpapers 4k still identify the screen as FHD+. If I manually change to WQHD 60hz then the same software will identify the screen correctly (WQHD). Some other software, for example, AIDA64, will identify it correctly (WQHD 120hz).
Also, in this mode it seems that the screen does not have the same sharpness as with WQHD 60Hz. So still something to play around with. It says WQHD but it looks like FHD+. If I switch to WQHD 60hz I can see the screen sharpness is better.
Also, if we switch to FHD+ or turn on medium power saving mode, the values will reset so we need to do it again manually.
---------- Post added at 01:35 PM ---------- Previous post was at 01:25 PM ----------
cpufrost said:
Root required?
Cannot edit this value!
Click to expand...
Click to collapse
It works without root.
Install the software.
After that install adb on your computer: https://www.xda-developers.com/install-adb-windows-macos-linux/ and follow all the instructions in the article. At the end you will end up executing adb devices command and it will say that your device is connected
After that type this command: adb shell pm grant by4a.setedit22 android.permission.WRITE_SECURE_SETTINGS and press Enter
It will grant the required permissions.
Unplug the cable, open the app and amend it as per the post above. It will amend the settings fine.
This feature is very nice to have but to be honest, I personally still prefer FHD+ 120hz to be on safe side - we don't know if WQHD 120hz will damage the screen or cause some other issues over time.

VirtualWaver said:
This works, thank you. However, some software, for example, wallpapers 4k still identify the screen as FHD+. If I manually change to WQHD 60hz then the same software will identify the screen correctly (WQHD). Some other software, for example, AIDA64, will identify it correctly (WQHD 120hz).
Also, in this mode it seems that the screen does not have the same sharpness as with WQHD 60Hz. So still something to play around with. It says WQHD but it looks like FHD+. If I switch to WQHD 60hz I can see the screen sharpness is better.
Also, if we switch to FHD+ or turn on medium power saving mode, the values will reset so we need to do it again manually.
---------- Post added at 01:35 PM ---------- Previous post was at 01:25 PM ----------
It works without root.
Install the software.
After that install adb on your computer: https://www.xda-developers.com/install-adb-windows-macos-linux/ and follow all the instructions in the article. At the end you will end up executing adb devices command and it will say that your device is connected
After that type this command: adb shell pm grant by4a.setedit22 android.permission.WRITE_SECURE_SETTINGS and press Enter
It will grant the required permissions.
Unplug the cable, open the app and amend it as per the post above. It will amend the settings fine.
This feature is very nice to have but to be honest, I personally still prefer FHD+ 120hz to be on safe side - we don't know if WQHD 120hz will damage the screen or cause some other issues over time.
Click to expand...
Click to collapse
OK I figured it needed permissions, thanks for clarifying this.
Now, we see indeed the screen is running at WQHD AND refreshing at 120Hz. HOWEVER, with sharpness degraded we can presume this is a hardware limitation and chroma subsampling is being used. 4:4:4 at 120Hz is going to require video bandwidth in excess of what the hardware can deliver. 4:2:2 or even 4:2:0 is used which will support that many pixels and refresh rate but at significantly degraded image quality which is immediately noticeable when reading text.

enjoylife1788 said:
How the battery life after this?
Click to expand...
Click to collapse
It sounds like 'chipping' a turbo. Great performance but fuel economy goes out the window!

cpufrost said:
OK I figured it needed permissions, thanks for clarifying this.
Now, we see indeed the screen is running at WQHD AND refreshing at 120Hz. HOWEVER, with sharpness degraded we can presume this is a hardware limitation and chroma subsampling is being used. 4:4:4 at 120Hz is going to require video bandwidth in excess of what the hardware can deliver. 4:2:2 or even 4:2:0 is used which will support that many pixels and refresh rate but at significantly degraded image quality which is immediately noticeable when reading text.
Click to expand...
Click to collapse
So is the quality noticeably higher than Fh+? And everything works well, what about battery life?

KURDKiNG said:
So is the quality noticeably higher than Fh+? And everything works well, what about battery life?
Click to expand...
Click to collapse
well his comments are saying it is Not particularly good quality and not working that well

tribalfs said:
I did it.
Set adaptive smoothness at fhd+.
Install settings database editor from play store and follow instructions to grant app write secure settings permission.
In the app, select Global Table in the dropdown and find the "display_size_forced" line. Edit the value to "1440,3088". Then select Secure Table, find"defsult_display_size_forced" and set it to "1440,3088". Lastly, find "default_display_density_forced" and "display_density_forced" and set both to "600".
Click to expand...
Click to collapse
It is just cosmetic, Not really WQHD+ @ 120hz
What your last (3rd) screenshot showing is cosmetic. Device running 120hz but showing WQHD+ is not real.
How to confirm it is really FHD+ or WQHD+ ?
1.Font size is obvious, you won't see any difference by method you shown, in real WQHD+ font size reduces.
2.Take screenshot and open in paint shop or similar that showing size in pixel, it will show 1080x2316 and not 1440x3088 in case you capture in WQHD+
3.Install any app that shows info e.g. ScreenInfo from play store and it will show screen size as per FHD+ and not WQHD+
So with this setup, you are only running FHD+ @120Hz nothing else. If anyone seeing difference from FHD+ @ 120 hz is likely a placebo.

dr.ketan said:
It is just cosmetic, Not really WQHD+ @ 120hz
What your last (3rd) screenshot showing is just cosmetic. Device running 120hz but showing WQHD+ is just a cosmetic.
How to confirm it is really FHD+ or WQHD+ ?
1.Font size is obvious, you won't see any difference by method you shown, in real WQHD+ font size reduces.
2.Take screenshot and open in paint shop or similar that showing size in pixel, it will show 1080x2316 and not 1440x3088 in case you capture in WQHD+
3.Install any app that shows info e.g. ScreenInfo from play store and it will show screen size as per FHD+ and not WQHD+
So with this setup, you are only running FHD+ @120Hz nothing else. If anyone seeing difference from FHD+ @ 120 hz is likely a placebo.
Click to expand...
Click to collapse
yes, you are correct. I realized it's a placebo.
screen checker apps also reports fhd+.
so those who are reading, don't waste your time anymore to try this.