Related
I stopped by the Verizon kiosk today and was playing with their variant of the Elf/Touch and I noticed that the screen is a lot more sensitive to using a finger for navigation (for example, touching the Task Manager or the Signal Indicator brings up the intended menu very reliably, despite their small size). Is this the result of TouchFLO software and is it possible for a Kaiser to operate with the same level of sensitivity?
From what I gathered, TouchFLO only allows for "gestures" to be recognized, usually in order to activate a Cube program. Can someone clarify?
I apologize in advance if this has been covered in another post; searching out an answer is difficult when nearly every ROM includes the word "TouchFLO" in its description.
robcav said:
I stopped by the Verizon kiosk today and was playing with their variant of the Elf/Touch and I noticed that the screen is a lot more sensitive to using a finger for navigation (for example, touching the Task Manager or the Signal Indicator brings up the intended menu very reliably, despite their small size). Is this the result of TouchFLO software and is it possible for a Kaiser to operate with the same level of sensitivity?
From what I gathered, TouchFLO only allows for "gestures" to be recognized, usually in order to activate a Cube program. Can someone clarify?
I apologize in advance if this has been covered in another post; searching out an answer is difficult when nearly every ROM includes the word "TouchFLO" in its description.
Click to expand...
Click to collapse
you can increase the sensitivity of the touch screen by going into advanced config and setting the touchflo sensitivity to a higher number...i have mine set at 5000, the default is like 200, give it a try, i'm fairly certain you'll like it much better.
skatdawg said:
you can increase the sensitivity of the touch screen by going into advanced config and setting the touchflo sensitivity to a higher number...i have mine set at 5000, the default is like 200, give it a try, i'm fairly certain you'll like it much better.
Click to expand...
Click to collapse
I have a Norwegian ROM, stupid guestion... where is advanced config and setting?
touchflow pressure threshold
skatdawg said:
you can increase the sensitivity of the touch screen by going into advanced config and setting the touchflo sensitivity to a higher number...i have mine set at 5000, the default is like 200, give it a try, i'm fairly certain you'll like it much better.
Click to expand...
Click to collapse
and you found that 5000 gives the best results or was that just an example? It is taking a soft reset every time to check if it's better.
I made a post after getting pie update and now, here is an in-depth list of features of android Q in ZMP M1
all phones are not getting the same features
removing screen lock /fingerprint doesn't save you from password after update (at least it didn't work for me ) make a backup of everything in case you need to reset
list of things I'll suggest making a backup
WhatsApp chat
google photos
apps with es file explorer or any such file manager
settings + contacts+ call log+ messages from settings backup
notification led :
I like to turn it off all the rime even when charging but in android Q I couldn't find any way to disable it during charging
i was checking my old post about pie
1. Ambient Display : settings>display>advance>Ambient Display
It works only when you get a notification (its dope would like it being enabled always) though Daydream nowhere to be found.
Click to expand...
Click to collapse
so ambient display is gone screensaver is back (edit: its renamed and moved to display lock screen area as new notification toggle)
volume panel:
change volume click more slider button and this is how to devolve UI it shows a big screen covering prompt to show sliders
font in developer settings only two options device default seems better
no third-party launcher supports the new gesture navigation but it is a problem on google's part
left earphone to week? there is audio balance in assessability settings
vibratin and haptic feedback in assessability
not the true dark mode in assessability settings dark theme and color inversion options are nearby enough to test what we could have got for dark mode
dark mode doesn't get turn back to a light mode in live wallpaper
assessability volume key shortcut might come in in handy for some but it makes a notification sound
there is charging sound and vibration in sound settings might want to turn it off, I have seen Samsung charging sound but Asus just makes the phone vibrate with a faint sound might scare people who don't know as it's on by default in android q
I am getting the rotate once button in navbar when autorotate is off I am using two-button navigation and a small circle when using gesture
the lockdown option to prevent unlock by any other means now also prevents notification to show can be enabled in display>lock screen display> show lockdown option
in gesture navigation you can swipe up and continue in an app to make it go smaller beyond it should go
to start android it asks for setup screen lock password it is stepping in the right direction but we should have it in kernel/bios as once entered in recovery mode anyone can reset a phone
QR code to share wifi available
still no way to monitor or block devices connected to your hotspot
default Bluetooth name QCOM-BTD Qualcomm's BLE chip?
widgets to settings shortcut there should be system UI tuner after opening it shows this funny warning message
apps notificatio>notification snoozing useless button more useless because cant see snooze option in youtube notification
battery saver got new auto turn off at 90% feature
battery picture in battery settings seems thick would prefer "ampere app" like stats in later versions
display don't have color temperature adjust
accelerated location something about data storage and data concent
high accuracy, battery saver, etc options for location not available
google play system update is 1 January 2020 please update it
security patch is 5nov 2019
privacy section is great but would like fingerprint prompt in autofill scenario as like for wifi sharing
digital wellbeing well let's skip it as I already have 18 unlocks 1 hr30 mins in the settings app and will have 4hr+ in youtube so let's skip it
verificatin code auto fill in google settings I something nice to have but also worrying
now you can directly launch apps from app info after force stopping
in about phone >emergency info> medical info you can add your profile pic and emergency contacts
dev options> picture color mode sRGB does this option even work any were?
in dark mode theme when searched in settings there is a white padding
dev options> game driver properties I don't know what it does perhaps boost graphics performance
feature flags section in dev options shows nothing except experimental (edit: these were removed in Q beta 3)
system traces have many options like pre CPU buffer and in the category, it has some tick box options and possibly CPU performance after we stop getting updates
swipe up to recent in any navigation option seem a bit too sensitive
audio seems of though I only watched youtube (Linus tech tips) so far that is without headphones
in dev options audio Bluetooth codec shows APTX HD and other option which might make Bluetooth audio great
in dev options profile HWUI seems new but not sure what it is the bars shown on-screen seems familiar
in dev options adaptive notification priority makes no difference and doesn't have any description but a quick google search shows it is supposed to make low notification priority genital
in dev options apps can be installed in external storage option
in dev options force activities resizable doesn't work in split-screen view but I may be doing something wrong
also I hate the lock icon when unlocking also there is no center icon with face/fingerprint or padlock in lock screen
in dev options wifi entending option might help in office or home to extend wifi if it works
in dev options enable freeform windows doesn't work
in dev options forced desktop scant be tested as no video output but wireless display might allow haven't tested
in dev options I enabled bubble notification will add things that can access it
in dev options auto fill section is too vague and I am not getting what anything does
in the last pie post I said
2. icons in overview/multitasking screen
Settings>apps>default apps>home app> quick setup(new name for launcher3)>home screen>home settings>change icon shape >go back to your preferred launcher.
Click to expand...
Click to collapse
it is now in theming in dev options
also ambient display (not to be confused with screensaver) kicks in when getting notification while the screen is off (edit: realized after posting this Asus renamed and moved to it to display> lock screen display> new notification )
widevine changed to L3 its used to stream Amazon Prime Video, BBC, Hulu, Netflix, Spotify, and Disney+ use Widevine DRM to manage the distribution of premium content. as a college student who has no job and already has to spend money on Jio internet I don't have any above-mentioned subscriptions and if you do use any services according to other beta testers you won't be supposably able to access them while in beta.
camera app
in pro mode no shutter speed control option
max iso in pro mode is 1600 like in HMD global camera
auto video encoder is h264
portrait mode has extremely bad edge detection
night mode isn't that good
no fps option for video like 24,25,29.98,30,60 fps etc
no raw support in stock camera app resulting in assumption camera2api isn't enabled by default, though I enabled it in pie and it carried forward maybe so I am not sure.
it is a bit long but if you are reading this then thanks for reading till the end I'll format the whole thing later
{Mod edit: Quoted OP removed for better reading}
There's really no option for notification led,
You get wake display for new notifications in lock screen display
I don't like that either its ugly pie sliders were better.
Is that even important fonts are fonts and generally no aosp thing gets custom font support and Google sans are for pixel things. Idk about which fonts will our phone get.
Third party launchers will work after December android security patch builds.
Dark mode is in display options and works good.
I don't know what dark theme and wallpaper have to do.
The srgb thing works but android or its apps aren't made to use srgb colors default is rgb which is used by most of the web.
Feature flags were removed by Google in beta 3 of Android 10.
Force activities resizable makes apps which don't work or don't allow split screen (insta) are made to be opened in split screen.
Enabling free form works and can be accessed from recent apps screen - click the app icon - open in free form. (don't know how you tested it)
Auto fill helps in password managers to fill in usernames and passwords.
It's in wake display also same to your missing ambient display.
Other things I've left are either too much to explain / really broken / I don't care of those since I don't use it.
Widevine has changed to l3 you didn't notice.
Sound output isn't very great it'll be fixed in next build I've reported that to asus.
There's really no option for notification led,
Click to expand...
Click to collapse
it is named as blink light there is a way to just turn it off but it still lights up when the phone is turned on which previously in the android pie it didn't
You get wake display for new notifications in lock screen display
Click to expand...
Click to collapse
I realized it too late going to edit it in
I don't like that either its ugly pie sliders were better.
Click to expand...
Click to collapse
the only good news I have is while in a call it shows call slider normally.
Is that even important fonts are fonts and generally no aosp thing gets custom font support and Google sans are for pixel things. Idk about which fonts will our phone get.
Click to expand...
Click to collapse
no it isn't that important but I thought that it's interesting and the options are:
device default.
noto serif/ Source Sans Pro.
Third party launchers will work after December android security patch builds
Click to expand...
Click to collapse
You are talking about gesture navigation, right? Teslacoilapps says this.
Dark mode is in display options and works good.
Click to expand...
Click to collapse
Like the official Reddit app has a dark modeand AMOLED dark mode. the difference is #333943 and #000000. The dark mode is not truly dark but gray.
I don't know what dark theme and wallpaper have to do.
Click to expand...
Click to collapse
In Android pie when you set the theme to dark mode and use live wallpaper it uses auto revert back to light mode now it doesn't.
The srgb thing works but android or its apps aren't made to use srgb colors default is rgb which is used by most of the web.
Click to expand...
Click to collapse
nowadays phones are getting so powerful and people can take great pictures so shouldn't sRGB be enabled by default? like it does help semi-professional photo editing if we get a bit more color accuracy.
Feature flags were removed by Google in beta 3 of Android 10.
Click to expand...
Click to collapse
I didn't know that, but now I do. Thanks for that.
Force activities resizable makes apps which don't work or don't allow split screen (insta) are made to be opened in split screen.
Click to expand...
Click to collapse
My bad, I thought it allowed resizing the split-screen apps like increasing the top window while decreasing the bottom one
Enabling free form works and can be accessed from recent apps screen - click the app icon - open in free form. (don't know how you tested it)
Click to expand...
Click to collapse
Samsung has a float window feature like actual windows pc like windows I thought it was like that feature i tried it as you mentioned but didn't get results i was expected
Auto fill helps in password managers to fill in usernames and passwords.
Click to expand...
Click to collapse
I think this is about this line
in dev options auto fill section is too vague and I am not getting what anything does
Click to expand...
Click to collapse
My question is what is
logging level
off
debug
verbose what does these mean
max request per session (it's just a field to enter a number what does it control)
max visible datasets (it's just a field to enter a number what does it control)
It's in wake display also same to your missing ambient display.
Click to expand...
Click to collapse
I found it after posting this thread and didn’t get a chance to update it.
Other things I've left are either too much to explain / really broken / I don't care of those since I don't use it.
Click to expand...
Click to collapse
things are too much to explain / broken but I like to deeply analyze things and couldn't find an in-depth bug list while thinking whether I should get in beta so after upgrading I made one. it has some errors but I am working on it
Widevine has changed to l3 you didn't notice.
Click to expand...
Click to collapse
that's something related to Netflix i don't have an account so wasn't able to notice it, though I saw it mentioned it in Asus forums
Sound output isn't very great it'll be fixed in next build I've reported that to asus.
Click to expand...
Click to collapse
I saw this problem also mentioned in the forums and I asked my friends if my phone sounds different and didn't got any negative report also I watched youtube for 4hrs on Thursday and didn't heard any difference
Would be interested to know how to turn off the lock screen. Lock screen none does not appear as an option.
Regards.
Gestures are enabled by Google after December security patch nova / most other launchers work with gestures. You can however use 2 button and 3 button navigation perfectly.
About that dark and black mode difference we don't have an amoled or led display it's an lcd so it won't make difference in battery but kind of personal choice. I like dark more than black.
The thing about wallpaper and dark thing - in android 9 dark/light theme was set by wallpaper color so live wallpapers needed to support color picker api to tell the device to keep light or dark theme. (it was half broken by asus as selecting dark theme should've disabled the api completely, but using pixel default live wallpapers they had that api so dark mode worked with them).
That srgb was being considered by Google they dropped it as it broke a lot of the things.
You can resize top and bottom windows just hold the middle line in centre and drag it where you want to put it. (I use 400 dpi so I get more steps).
It's because that feature is intended towards large screen tablets or foldables and Samsung made their own thing, (the free form window thing).
It's for devs making password manager apps or autofill apps those people need it for debugging, the logging levels are to make reports to find bugs, the max request is how many times in one field the autofill will attempt to fill in credentials. The max visible dataset is if you have multiple accounts to one app (take Gmail as example) so while trying to autofill it lists all of available accounts to show (I'm not an expert in this so I maybe wrong if needed confirm that.
About sound issue it is very real and use some good quality earphones or compare side by side with 060 running device.
Hey folks,
I am using this module to enable AA on my BMW headunit:
a.aliexpress.com/_U4Jz5
It kinda works nice except for one thing, resolution is not so clear due to dpi settings. Someone else dug into the system and found that in
etc/androidauto/androidauto_config.xml
The resolution is set to 480p instead of 720p and dpi is set to 150 instead of 180.
We have no SSH access but can only upload .bin update files as we dont know the password.
Does anyone know if it would be possible to change 720p to true and up the dpi somehow?
Carplay apparantly is 720p on this unit.
<DisplayWindow><!-- Head Unit side configuration--> <X_Coordinate value="0"/> <Y_Coordinate value="0"/> <DisplayWidth value="1280"/> <DisplayHeight value="480"/> </DisplayWindow> <Display><!-- Phone side configuration--> <DisplayWidth value="232"/><!-- Physical width--> <DisplayHeight value="87"/><!-- Physical height--> <Density value="170"/> <RealDensity value="153"/> <ViewingDistance value="400"/> <Resolution480P value="true"><!-- fps: 30 or 60--> <fps value="30"/> </Resolution480P> <Resolution720P value="false"> <fps value="30"/> </Resolution720P>
Nobody?
Anyone?
Do you have a copy of the BIN? My guess is unpacking and repacking the BIN will be the hardest part of this. You probably won't be able to do this without source scripts. You are in the right place regarding the XML file inside. All android head units, regardless of what they are, have to tell our phones what resolution to serve up. If the head unit says to run 1024x600 then that is what you are getting.
An alternative would be to ask the manufacture to release an update set to the proper settings.
---------- Post added at 09:12 PM ---------- Previous post was at 09:09 PM ----------
Here you go The Andream unit you have should likely work with one of these firmwares. Do a lot of reading there before you proceed. I cannot be responsible for you flashing the wrong software to your unit.
I have a similar unit to yours and was able to get mine running at the proper resolution.
@heresy_fnord, when you say the proper resolution, what resolution are you referring to? I have the Andream (version: NBT-02B) unit myself, and flashed the latest .BIN with the AA Widescreen fix, but I feel the scale is slightly off. Text and elements are too small compared to the screen size (I have 8.8", 1280x480).
ckarv said:
@heresy_fnord, when you say the proper resolution, what resolution are you referring to? I have the Andream cool:unit myself, and flashed the latest .BIN with the AA Widescreen fix, but I feel the scale is slightly off. Text and elements are too small compared to the screen size (I have 8.8", 1280x480).
Click to expand...
Click to collapse
OK, my guess is the physical screen size is the issue. If you are certain the 8.8" screen also runs 1280x480 then the settings for DPI are probably not appropriate. Here is what I see for a 10.25" screen:
<Display>
<DisplayWidth value="244"/> 244mm is 9.6" width
<DisplayHeight value="92"/> 92mm is 3.62" height
<WidthMargin value="0"/>
<HeightMargin value="0"/>
<Density value="220"/>
<RealDensity value="133"/> This calculator indicates a real density of just a hair over 133PPI
So for example, your real density should be set to 155PPI based on that logic. I don't know what your update file was set to. I don't know what your display width and height should be set to since I don't know how the 8.8" screen measures length and width. Finally, I think they are setting the Density of the widescreen fixed update to 210 and you might try 220 which is as big as it can be set before it cuts back over to the non-widescreen view, and see if that works.
heresy_fnord said:
OK, my guess is the physical screen size is the issue. If you are certain the 8.8" screen also runs 1280x480 then the settings for DPI are probably not appropriate. Here is what I see for a 10.25" screen:
<Display>
<DisplayWidth value="244"/> 244mm is 9.6" width
<DisplayHeight value="92"/> 92mm is 3.62" height
<WidthMargin value="0"/>
<HeightMargin value="0"/>
<Density value="220"/>
<RealDensity value="133"/> This calculator indicates a real density of just a hair over 133PPI
So for example, your real density should be set to 155PPI based on that logic. I don't know what your update file was set to. I don't know what your display width and height should be set to since I don't know how the 8.8" screen measures length and width. Finally, I think they are setting the Density of the widescreen fixed update to 210 and you might try 220 which is as big as it can be set before it cuts back over to the non-widescreen view, and see if that works.
Click to expand...
Click to collapse
I've put some effort into looking into this now, basically reading 100 odd pages in the "Andream MMI Box - Wireless CarPlay & Android Auto" thread (starting on pg. 135), over at the Bimmerpost forum.
Findings:
- 720p = true setting is required to display AA in "Wide" format (ie. clock, second app on the right side of the display, map and vertical bar with "home", active app, notification and assistant buttons on the left).
- From reading results of testing over at the other forum, the Physical width/height settings did not seem to make a difference to output.
- Density on the other hand is used to scale the elements on screen, and this also impacts readability and sharpness of the objects/text.
-- from some testing, the conclusion was that "200" is the optimum value for the 1280x480, 8.8" screen, although eg. "210" was tested.
-- unsure if changing "Real Density" will make a difference to output (similar to physical measurements)
* Also, I think my scale is correct, or as specified in the firmware. Text and elements just seems so small compared to CarPlay that wife uses.
* Attached a picture of my screen with 200 dpi.
You are using a "Density" value of 220, do you have an example of what that looks like in practice?
Thanks
ckarv said:
I've put some effort into looking into this now, basically reading 100 odd pages in the "Andream MMI Box - Wireless CarPlay & Android Auto" thread (starting on pg. 135), over at the Bimmerpost forum.
Findings:
- 720p = true setting is required to display AA in "Wide" format (ie. clock, second app on the right side of the display, map and vertical bar with "home", active app, notification and assistant buttons on the left).
- From reading results of testing over at the other forum, the Physical width/height settings did not seem to make a difference to output.
- Density on the other hand is used to scale the elements on screen, and this also impacts readability and sharpness of the objects/text.
-- from some testing, the conclusion was that "200" is the optimum value for the 1280x480, 8.8" screen, although eg. "210" was tested.
-- unsure if changing "Real Density" will make a difference to output (similar to physical measurements)
* Also, I think my scale is correct, or as specified in the firmware. Text and elements just seems so small compared to CarPlay that wife uses.
* Attached a picture of my screen with 200 dpi.
You are using a "Density" value of 220, do you have an example of what that looks like in practice?
Thanks
Click to expand...
Click to collapse
- 720p = true setting is required to display AA in "Wide" format (ie. clock, second app on the right side of the display, map and vertical bar with "home", active app, notification and assistant buttons on the left).
This is accurate.
- From reading results of testing over at the other forum, the Physical width/height settings did not seem to make a difference to output.
I don't know, perhaps this is true.
- Density on the other hand is used to scale the elements on screen, and this also impacts readability and sharpness of the objects/text.
-- from some testing, the conclusion was that "200" is the optimum value for the 1280x480, 8.8" screen, although eg. "210" was tested.
-- unsure if changing "Real Density" will make a difference to output (similar to physical measurements)
* Also, I think my scale is correct, or as specified in the firmware. Text and elements just seems so small compared to CarPlay that wife uses.
Your scale of text is set by the DPI essentially. Its a combination of resolution and DPI. Basic example, if I was to set my DPI to 200, the text on my screen would be smaller.
* Attached a picture of my screen with 200 dpi.
This is a 10.25" screen with 220DPI
In your case, the one update file was made for a 10.25" screen. The thing is, there will be a DPI difference between the two even if the resolution is the same. I suspect you need check with that community to see if there is an update that maintains widescreen mode but uses the different DPI.
EDIT: To be fair, I think your screen looks "normal" but then, it looks like your clock and such are the same scale as mine. Maybe AA is just smaller text in general?
I have downloaded an app called touch sampling rate checker and my Moto Edge 20 only shows a rate of 90-117hz regardless of screen refresh rate setting, however when using the same app on my mi11 it shows a constant 250hz and the mi 11 seems smoother in Twitter and Facebook etc am I missing something here?
Touch sampling rate and refresh rate are two different things. If you want a refresh rate checker, you can find it in developer options.
PhotonIce said:
Touch sampling rate and refresh rate are two different things. If you want a refresh rate checker, you can find it in developer options.
Click to expand...
Click to collapse
Yeah I get that but I thought this phone has a 576hz touch sample rate? Unless the app is inaccurate ?
Not sure about the app, maybe try a different one.
nealyblue said:
Yeah I get that but I thought this phone has a 576hz touch sample rate? Unless the app is inaccurate ?
Click to expand...
Click to collapse
You have to enable game mode for individual apps for max touch sampling rate to be enabled.
dannejanne said:
You have to enable game mode for individual apps for max touch sampling rate to be enabled.
Click to expand...
Click to collapse
Unfortunately I already did that and the maximum I see is 250hz. Where have the 576hz they said gone?
fulltronservice said:
Unfortunately I already did that and the maximum I see is 250hz. Where have the 576hz they said gone?
Click to expand...
Click to collapse
Yeah the highest I've seen is 400hz with game mode
nealyblue said:
Yeah the highest I've seen is 400hz with game mode
Click to expand...
Click to collapse
So that means that the value is dynamic up to 576hz. nothing to worry about then
Android apps dont usually report the correct sampling rate. Connect the phone through USB to a PC and run through ADB run the commands: "Adb shell getevent -r -t -l" and then start swiping on the display. It should report the correct sampling rate.
Username: Required said:
Android apps dont usually report the correct sampling rate. Connect the phone through USB to a PC and run through ADB run the commands: "Adb shell getevent -r -t -l" and then start swiping on the display. It should report the correct sampling rate.
Click to expand...
Click to collapse
That ADB thing really helped. Now I can see the real use of touch sensitivity. From the huge list that came out I could see a maximum of 473hz. So the capability that Motorola offers is installed.
Thanks
fulltronservice said:
That ADB thing really helped. Now I can see the real use of touch sensitivity. From the huge list that came out I could see a maximum of 473hz. So the capability that Motorola offers is installed.
Thanks
Click to expand...
Click to collapse
It varies on how fast you can drag your finger across the screen. I'm sure that if you drag it fast enough you'll hit 576Hz.
Username: Required said:
It varies on how fast you can drag your finger across the screen. I'm sure that if you drag it fast enough you'll hit 576Hz.
Click to expand...
Click to collapse
Yes, I was able to notice that. When I made a simple contact, the response barely reached 100hz, but if I made aggressive contacts, the response was quite high.
fulltronservice said:
Unfortunately I already did that and the maximum I see is 250hz. Where have the 576hz they said gone?
Click to expand...
Click to collapse
I just found out by experimenting Game Turbo:
1. Add your Game App/ Touch Tester App to game mode/turbo
2. Enable Auto Rotation mode (Portrait / Landscape mode)
3. Rotate ur Phone to Landscape even if the app doesnt support it
4. Touch the Screen while in Landscape and see the result Increases to Max Touch Rate
Follow what i said. I want to see the result.
Ty
cjlaysico said:
I just found out by experimenting Game Turbo:
1. Add your Game App/ Touch Tester App to game mode/turbo
2. Enable Auto Rotation mode (Portrait / Landscape mode)
3. Rotate ur Phone to Landscape even if the app doesnt support it
4. Touch the Screen while in Landscape and see the result Increases to Max Touch Rate
Follow what i said. I want to see the result.
Ty
Click to expand...
Click to collapse
Thanks for the tip man I was freaking out with my Xiaomi 11T Pro who supposedly have 480hz sampling rate screen and was just getting 250hz tops within checker apps, until I run them through Gaming Mode as you suggested with Pro mode enabled and YES the sampling rate wen above 500hz tops.
So the range is dynamic? Supposedly to save battery I guess?
Regardless thanks!
[Re-posting this here after I confirmed it work with the Pixel 7 as well]
To be clear, this is not the same as the developer option.
Enter the following ADB commands (you can also modify these values using the app SetEdit in the Play Store, no root required):
adb shell settings put system peak_refresh_rate 24.0
adb shell settings put system min_refresh_rate 24.0
The reason this works is because by assigning it a random and unsupported value, we are [kind of] breaking the refresh rate. As a result of which, the OS won’t be able to adjust this rate, and hence stick with the maximum available rate.
You can also enable the "Force Refresh Rate" in Developer Options. I tried it, but don't really care to keep DO enabled. Also you can enable "Show Refresh Rate" in DO. I did that also, and realized that with keeping it at 60(normal), and keeping "Smooth Display" on, the phone kicks it into 90 the moment you touch the screen. So forcing 90 100% of the time is a waste of battery in my opinion. Only when the phone is not touched for three seconds does it drop back to 60. Otherwise any use of the phone it stays at 90 normally.
bobbyphoenix said:
You can also enable the "Force Refresh Rate" in Developer Options. I tried it, but don't really care to keep DO enabled. Also you can enable "Show Refresh Rate" in DO. I did that also, and realized that with keeping it at 60(normal), and keeping "Smooth Display" on, the phone kicks it into 90 the moment you touch the screen. So forcing 90 100% of the time is a waste of battery in my opinion. Only when the phone is not touched for three seconds does it drop back to 60. Otherwise any use of the phone it stays at 90 normally.
Click to expand...
Click to collapse
Started my day today at 100% 7AM and am at 52% 11PM so I am happy. I can't stand Snapchat being 60.
Update on my observation. It may be a placebo effect, but knowing that it changes makes me see a slight stutter. Forcing 90 at all times "seems" much smoother, so I'm leaving it on also. Cheers!
this trick is irrelevant, you can do it in developer tool....
Vio281 said:
this trick is irrelevant, you can do it in developer tool....
Click to expand...
Click to collapse
The developer option does not force in many cases. In Snapchat when you swipe to the left and the camera is still initialized it stays at 60hz. Once the camera is not initialized it goes to 90hz. I believe it is the same in Instagram.
Jonnyswboy said:
The developer option does not force in many cases. In Snapchat when you swipe to the left and the camera is still initialized it stays at 60hz. Once the camera is not initialized it goes to 90hz. I believe it is the same in Instagram.
Click to expand...
Click to collapse
Jonnyswboy said:
The developer option does not force in many cases. In Snapchat when you swipe to the left and the camera is still initialized it stays at 60hz. Once the camera is not initialized it goes to 90hz. I believe it is the same in Instagram.
Click to expand...
Click to collapse
Has a fix been found for this cause I found this doesn't seem to be an issue at all on iPhone but incredibly frustrating on Android especially Snapchat.
lukeah02 said:
Has a fix been found for this cause I found this doesn't seem to be an issue at all on iPhone but incredibly frustrating on Android especially Snapchat.
Click to expand...
Click to collapse
My fix is in the original post. Has been working great for me.
Been using this for a while, but let's saym hypothetically if I wanted to restore it to default settings, which values do I need to put on the adb commands?
If I do those ADB commands and decide I want to not have them anymore, how would I revert?
To get your default values before doing the change, use:
Code:
adb shell settings get system peak_refresh_rate
and
Code:
adb shell settings get system min_refresh_rate
For me on stock firmware unrooted, peak_refresh_rate = null, and min_refresh_rate = 0.
Thanks for your fix! I was wondering why some apps were low hz.
heisenberg17 said:
Been using this for a while, but let's saym hypothetically if I wanted to restore it to default settings, which values do I need to put on the adb commands?
Click to expand...
Click to collapse
Get default values before doing the change:
adb shell settings get system peak_refresh_rate
adb shell settings get system min_refresh_rate
Default values (stock unrooted):
peak_refresh_rate = null
min_refresh_rate = 0
Thanks for your fix! I was wondering why some apps were low hz.
I've just got a Pixel 7 and thought I'd try this.
Observations, stock not rooted etc
Peak refresh rate = 90
min refresh rate = null
Applied the settings in post 1
and both come back as 24 when 'getting' peak/min rates from adb.
However, turning on show refresh rate in developer options show 90 when using the screen, but drops back to 60 if you leave it for a few seconds.
it only stays at 90 if you turn on Force peak refresh rate in Developer options.
This is only so far when messing about on the home screen, not tested in any apps etc, but it looks like these settings can't be fixed by setting a random number as post 1 implies
As a quick follow up, setting both peak and min to 90 does fix them, but seems a bit pointless as you can turn it on/off within developer settings.
This is not a bash at the OP, but maybe recent update have taken this 'feature' out
Does this survive a reboot?
xduox said:
Get default values before doing the change:
adb shell settings get system peak_refresh_rate
adb shell settings get system min_refresh_rate
Default values (stock unrooted):
peak_refresh_rate = null
min_refresh_rate = 0
Thanks for your fix! I was wondering why some apps were low hz.
Click to expand...
Click to collapse
Though the above might be a possible solution, here is the proper way to revert using ADB:
adb shell settings reset system peak_refresh_rate
To dig further into the possible System settings (amazing topic ^^)
adb shell settings list system
MrPeaski said:
seems a bit pointless as you can turn it on/off within developer settings.
This is not a bash at the OP, but maybe recent update have taken this 'feature' out
Click to expand...
Click to collapse
You can't force peak refresh rate in developer settings. It will still drop at times, like in Snapchat when the camera is accessed, on Google Maps, etc. It still automatically drops to 60hz despite the developer option being enabled.
And after updating to the Android 14 beta this workaround does not work anymore, and I am very frustrated that I am unable to truly force 90hz anymore.