Develop Bugs

Scrolling Speed and Sensitivity

Just wondering if there are any settings on the phone that allow me to adjust the sensitivity or scrolling speed? Or are there any ROMs that allow this to be adjusted or changed?

red 90 said:
Just wondering if there are any settings on the phone that allow me to adjust the sensitivity or scrolling speed? Or are there any ROMs that allow this to be adjusted or changed?
Click to expand...
Click to collapse
There are no setting for that.
That function would have to be implemented in the app and not the os.
Sent from my Galaxy Nexus using Tapatalk

How to dim the GN screen even more?

I find the dimmest screen toggle still too bright. I find it embarrassing to use in dark public spaces.
Is there a way to dim the screen even more?

Download the screen filter app from the play store. Literally puts a filter effect on the screen to make it appear darker making it much easier to use in the dark.

Yes its possible to take the screen much lower, but we have to edit the framework. Nobody had done this mod yet for some reason.

CM9 has the ability to change the screen lowest settings built in

B97 said:
Download the screen filter app from the play store. Literally puts a filter effect on the screen to make it appear darker making it much easier to use in the dark.
Click to expand...
Click to collapse
+1. I use Screen Filter also, it's uber handy for reading at night when the light seems too bright. If you've got hardkeys like I had on my Desire, you can even turn them off.

i wrote a tutorial on how you can mod the frameworks apk. it's very easy and you can change the brightness levels to anything you want. here's the thread
screen filter only puts a transparent layer on the screen and messes with the colors. modding the frameworks will lower default brightness to any level you want. you can raise it too if you like.

Thanks for all the ideas. I went with the easiest one, Screen Filter.

AOKP also has an option to reduce screen brightness...

dynamicpda said:
Thanks for all the ideas. I went with the easiest one, Screen Filter.
Click to expand...
Click to collapse
Good man!
Sent from my GT-I9100 using XDA

neotekz said:
i wrote a tutorial on how you can mod the frameworks apk. it's very easy and you can change the brightness levels to anything you want. here's the thread
screen filter only puts a transparent layer on the screen and messes with the colors. modding the frameworks will lower default brightness to any level you want. you can raise it too if you like.
Click to expand...
Click to collapse
Great work, I've been wondering why nobody did this mod yet for the nexus. I made that same mod on my atrix, using the sgs2 thread as well. But I've been too lazy to do it for nexus.
The above mod is the best option. Screen filter doesn't achieve the same results. The above mod reduces power draw as well when on the lower brightness setting of 5 or so. Screen filter just hides the higher brightness but has same power draw.

RogerPodacter said:
Great work, I've been wondering why nobody did this mod yet for the nexus. I made that same mod on my atrix, using the sgs2 thread as well. But I've been too lazy to do it for nexus.
The above mod is the best option. Screen filter doesn't achieve the same results. The above mod reduces power draw as well when on the lower brightness setting of 5 or so. Screen filter just hides the higher brightness but has same power draw.
Click to expand...
Click to collapse
That would be correct for back-lit screens. For the Galaxy Nexus screen, though, Screen Filter does help reducing power draw as a darker screen content = lower brightness.
I used to use SF for quite a while until I got fed up of it causing stutters to most animations. After thorough examination I concluded that the Nexus's GPU is the culprit. For some reason it just doesn't like multiple graphics being updated at once. Modding the overlay XML allows it to run at full speed.
Can anyone confirm the same reduced framerate issue?. It's also the reason why some ROMs include a setting to remove the navigation buttons glow. I tested with CM9 on the SGS2 and experienced none of the stutters in cases where the GN would. Another example: sliding between sections (comments, ralated, etc.) in YouTube is laggy iff the video is playing.

fnf said:
That would be correct for back-lit screens. For the Galaxy Nexus screen, though, Screen Filter does help reducing power draw as a darker screen content = lower brightness.
I used to use SF for quite a while until I got fed up of it causing stutters to most animations. After thorough examination I concluded that the Nexus's GPU is the culprit. For some reason it just doesn't like multiple graphics being updated at once. Modding the overlay XML allows it to run at full speed.
Can anyone confirm the same reduced framerate issue?. It's also the reason why some ROMs include a setting to remove the navigation buttons glow. I tested with CM9 on the SGS2 and experienced none of the stutters in cases where the GN would. Another example: sliding between sections (comments, ralated, etc.) in YouTube is laggy iff the video is playing.
Click to expand...
Click to collapse
Agreed, GPU just isn't good enough. I hate the lag with the button glow animations on!
I use an app called root dim, it's really useful. Let's you use a brightness level of 1, which is really quite dim. Free, too.
Sent from my Galaxy Nexus using XDA App

Remoteconcern said:
Agreed, GPU just isn't good enough. I hate the lag with the button glow animations on!
I use an app called root dim, it's really useful. Let's you use a brightness level of 1, which is really quite dim. Free, too.
Sent from my Galaxy Nexus using XDA App
Click to expand...
Click to collapse
Thanks for the tip, on the Galaxy Nexus it's possible to set the brightness to 0 by writing to /sys/class/backlight/*/brightness but the brightness is checked and reset to the minimum (default 10) every time the screen is turned on. I guess Root Dim works to the same effect so it runs as a system service. Still, it'd be an awesome addition for people who haven't bothered to mod.

fnf said:
That would be correct for back-lit screens. For the Galaxy Nexus screen, though, Screen Filter does help reducing power draw as a darker screen content = lower brightness.
I used to use SF for quite a while until I got fed up of it causing stutters to most animations. After thorough examination I concluded that the Nexus's GPU is the culprit. For some reason it just doesn't like multiple graphics being updated at once. Modding the overlay XML allows it to run at full speed.
Can anyone confirm the same reduced framerate issue?. It's also the reason why some ROMs include a setting to remove the navigation buttons glow. I tested with CM9 on the SGS2 and experienced none of the stutters in cases where the GN would. Another example: sliding between sections (comments, ralated, etc.) in YouTube is laggy iff the video is playing.
Click to expand...
Click to collapse
Screen filter may reduce power. But amoled screens save power with lower brightness. There is no difference between lcd vs led on this issue. And modifying the framework to bring min brightness down to 5 rather than 15 saves much more power than screen filter. Its no contest. This isn't different from lcd in this case.
---------- Post added at 03:20 PM ---------- Previous post was at 03:14 PM ----------
fnf said:
Thanks for the tip, on the Galaxy Nexus it's possible to set the brightness to 0 by writing to /sys/class/backlight/*/brightness but the brightness is checked and reset to the minimum (default 10) every time the screen is turned on. I guess Root Dim works to the same effect so it runs as a system service. Still, it'd be an awesome addition for people who haven't bothered to mod.
Click to expand...
Click to collapse
Yes we can write to that sysfs file, but it gets reset. The mod to the frameworks incorporates that backlight file so its now able to go down to 1, 2, 5, or whatever you want. It makes it now stock, so you are no longer capped at 10 (actually I think 15 is the cap I see). But that mod is just removing this cap and making it lower to whatever you want. Stock.
So no extra app is needed. No additional tweak. It now makes the stock brightness able to go down to 1 by itself whenever it needs.

[Q] AOKP Screen Brightness

The lowest brightness setting is not dim enough for me in low light conditions so I've been looking to alter it.
After reading around the capabilities of some apps it seems that they only add an overlay which reduces contrast. I would much prefer to do it natively.
I then realised that the AOKP ROM has this functionality!
However, I can't seem to get it to work.
Settings>Display>Custom backlight settings
Changing the screen dim level doesn't seem to change anything for me.
Can anyone offer some tips or advice?
Thanks

Works fine for me. I know it doesn't help your problem any...

danger-rat said:
Works fine for me. I know it doesn't help your problem any...
Click to expand...
Click to collapse
Does your display dim more when you select a lower than default value or did you have to change something else?

Did you change the corresponding value in "Edit Other Levels" as well (if you're on auto brightness)? Not on AOKP, but mine is fully functional both on manual, and auto.
Their implementation is the same as CM9 (which is nearly identical, if not the same as the CM7 implementation).
Edit: just a thought, not sure if the AOKP status bar brightness slider is hardcoded to a certain minimum level? Are the results the same if you adjust your brightness via the Settings>Display>Brightness slider?

Settings>Rom Control>Performance>color multipliers.
Drag the three bars all the way down.
As far as your problem...
Are you on auto brightness?
And have you adjusted the "Dim Level" prior to adjusting the screen levels?
(Dim Level is the level your screen dims to after not touching it for 15 seconds or whatever).

Jubakuba said:
And have you adjusted the "Dim Level" prior to adjusting the screen levels?
(Dim Level is the level your screen dims to after not touching it for 15 seconds or whatever).
Click to expand...
Click to collapse
Screen dim level is the minimum brightness value attainable (I lower mine to 12 so I can enter a screen value of 12 in my custom levels), but also does correspond to what you mentioned.

Another AOKP user expressed similar concerns but found an app called Root Dim or something that solved his problem.

OpusX11 said:
Another AOKP user expressed similar concerns but found an app called Root Dim or something that solved his problem.
Click to expand...
Click to collapse
The implementation must be still broken then; haven't tested the latest AOKP releases. Root dim apps tend to create lag.

Implementation works perfectly here.

Jubakuba said:
Implementation works perfectly here.
Click to expand...
Click to collapse
Same.

Jubakuba said:
Implementation works perfectly here.
Click to expand...
Click to collapse
Attaining an altered screen dim level when on auto as well?
Edit: comment wasn't an indictment; just remembering issues that were there on b35 or b36 (?).
Sent from my Galaxy Nexus

Yep.

Microwave. said:
Does your display dim more when you select a lower than default value or did you have to change something else?
Click to expand...
Click to collapse
I select a lower than normal default brightness, and it appears to just work. The auto brightness decreases, which is what i was looking for at night, and also the overall min brightness decreases. The max brightness seems unaffected...

remember when making these changes you do have to save and apply. many people forget that step.

tspderek said:
remember when making these changes you do have to save and apply. many people forget that step.
Click to expand...
Click to collapse
That's an especially annoying mis-step after entering 23 custom levels.

CMNein said:
That's an especially annoying mis-step after entering 23 custom levels.
Click to expand...
Click to collapse
Lol.
And no offense taken at all, man.
And me personally, I just use 5 levels.
One that goes all the way to 600[whateverambientlightismeasuredby] and a screen level of 5.
This keeps my phone from dicking about with it's brightness when I'm indoors...and I have no problem reading it. I don't mind a super-dim screen in general.
The remaining levels I ramp up fairly aggressively for two "by a window" scenarios...
And outside.
And OMGSUNNY outside.

Jubakuba said:
Lol.
And no offense taken at all, man.
And me personally, I just use 5 levels.
One that goes all the way to 600[whateverambientlightismeasuredby] and a screen level of 5.
This keeps my phone from dicking about with it's brightness when I'm indoors...and I have no problem reading it. I don't mind a super-dim screen in general.
The remaining levels I ramp up fairly aggressively for two "by a window" scenarios...
And outside.
And OMGSUNNY outside.
Click to expand...
Click to collapse
I add 2 levels for the high end, and reduce the other brightness levels considerably. Ultimately I usually end up with the perfect'ish level for most scenarios. I hate having to adjust brightness the old fashioned way
Sent from my Galaxy Nexus

CMNein said:
Screen dim level is the minimum brightness value attainable (I lower mine to 12 so I can enter a screen value of 12 in my custom levels), but also does correspond to what you mentioned.
Click to expand...
Click to collapse
Which values do you change in the custom levels?
OpusX11 said:
Another AOKP user expressed similar concerns but found an app called Root Dim or something that solved his problem.
Click to expand...
Click to collapse
Yeah, I know an app could potentially solve the problem but I don't like using 3rd party apps when the solution can be more elegantly achieved using native tweaks.
Jubakuba said:
Lol.
And no offense taken at all, man.
And me personally, I just use 5 levels.
One that goes all the way to 600[whateverambientlightismeasuredby] and a screen level of 5.
This keeps my phone from dicking about with it's brightness when I'm indoors...and I have no problem reading it. I don't mind a super-dim screen in general.
The remaining levels I ramp up fairly aggressively for two "by a window" scenarios...
And outside.
And OMGSUNNY outside.
Click to expand...
Click to collapse
Could you send me a screenshot of your custom levels, that sounds like the exact thing I'm after - a dimmer screen in general, and having a lower min brightness.
So am I correct in thinking that you need to lower the dim value in order to set lower values in the custom levels?

After some time, the screen frequency changes to 60 Hz and cannot be changed

After some time, the screen frequency changes to 60 Hz and cannot be changed to 90 Hz. After restarting everything works again.

Stepanlk said:
After some time, the screen frequency changes to 60 Hz and cannot be changed to 90 Hz. After restarting everything works again.
Click to expand...
Click to collapse
Possibly a bug do you have it set to auto switch or perm 90hz mine arrives tomorrow will test mine see if does the same
Sent from my iPhone using Tapatalk

I found the reason. If you have the wearable widgets app (or similar) the screen frequency will always be 60 Hz as long as the app is running in the background

Stepanlk said:
I found the reason. If you have the wearable widgets app (or similar) the screen frequency will always be 60 Hz as long as the app is running in the background
Click to expand...
Click to collapse
Ah right will delete that app then [emoji1]thanks
Sent from my iPhone using Tapatalk

Question Findings on the Pixel 6 Pro's "10–120 Hz" Variable Refresh Rate - (yes, 10 Hz works)

https://www.reddit.com/r/GooglePixel/comments/rn5wrp
Click to expand...
Click to collapse
Summary
Pixel 6 Pro goes down to 10 Hz as expected when idle in normal lighting
In low ambient light & low brightness for darker content, refresh rate only goes down to 60 Hz
Pixel 6 Pro PWM frequency is 360 Hz, lowering down to 120 Hz at <20% system brightness
AOD goes down to 10 Hz as expected
Battery Saver/Smooth Display disabled does not go down to 10 Hz, stays at 60 Hz
Watching 24fps/30fps movies/videos does not lower refresh rate down to 24/30 Hz, stays at 60 Hz
The important bits
Some people have (mistakenly) used Android's refresh rate indicator within the Developer Options to come to the conclusion that the 6 Pro's variable refresh rate only goes down to 60 Hz, because that's what the indicator shows when the screen is idle. However, Android's refresh rate indicator does not show the OLED panel's lowest operating refresh rate, due in part by how its VRR is implemented. The Pixel 6 Pro's Samsung Display panel has a variable refresh rate mechanism that operates at a much lower level, within the display driver, and not exposed to the Android user-space.
Click to expand...
Click to collapse
Samsung's VRR implementation is not the same as those found in typical gaming monitors which can target any arbitrary refresh rate. The VRR found in Samsung's HOP ("LTPO") panels still work by switching between discrete refresh rate modes, like older implementations, but the new panels now incorporate a low frequency drive (LFD) mechanism which operates the OLED driving rate at a fraction of the current refresh rate mode. As an example, a 10 Hz driving refresh rate is achievable by operating the panel at 60 Hz but skipping re-drives for 5 out of every 6 refresh intervals if the frames are the same.
Click to expand...
Click to collapse
And from (#1), we finally find some solid proof that there is a 10 Hz fundamental driving frequency in the Pixel 6 Pro display when screen content is idle, despite the Android refresh rate indicator reporting 60 Hz.
Along with it, we find two other fundamental frequencies at 120 Hz and 360 Hz. The peak at 360 Hz is almost certainly the PWM frequency, and 120 Hz is the fundamental refresh frequency from which the 10 Hz LFD is employed from.
Click to expand...
Click to collapse
I also tested if the Always-On Display went down to 10 Hz (#5), and I can confirm that it does. It's driven at a 120 Hz PWM freq. and a 60 Hz fundamental refresh, employing LFD down to 10 Hz.
Click to expand...
Click to collapse