Hey all,
I recently got an Xperia 1 II and I saw that there were whisperings of 120Hz being supported for the panels, so I dug into it and found this commit which added support, but it was reverted. So I tried it out, and found that the reason they'd reverted it was a ~fairly trivial regression on 4K displays.
Regression in question:
https://twitter.com/i/web/status/1390803385192833025
I've fixed the regression in dtbo.img by reverting the clockrate changes in [email protected] The full panel .dts file can be found in the build instructions.
EDIT: I looked at the panel with a 240FPS camera and it seems to be updating at 60Hz still, so there might be something missing (or the panel just genuinely doesn't support anything faster). The clockrates also seem to correlate more with 90Hz and not 120Hz. Not sure what to make of it.
Spoiler: Proof-of-120Hz
{
"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"
}
DISCLAIMER:
I have no idea if this will damage certain panels, drain your battery, cause burn-in, etc. FLASH AT YOUR OWN RISK! I do not accept any liability if something bad happens.
Known Regressions:
For some reason, the brightness scale is bugged at the higher framerate. Working on a fix, but it can result in the brightness randomly flickering with autobrightness.
Fixed the brightness regression by patching my original dtbo with the clockrate + FPS values by hand, something with Sony's kernel device tree differs and introduces the brightness issues.
Flashing Instructions:
Code:
#!/bin/bash
sudo adb reboot bootloader
sudo fastboot flash dtbo_a dtbo.img
sudo fastboot flash dtbo_b dtbo.img
sudo fastboot reboot
If you want to revert, I've attached my original dtbo_a, but I'd suggest making a backup yourself.
Build Instructions For The Curious:
Spoiler: Build Instructions
Find or build mkdtimg, there's uploads out there. Otherwise:
Check out branch aosp/LA.UM.9.12.r1 of https://github.com/sonyxperiadev/kernel somewhere
Place this dsi-panel-souxp00_a-amb650wh07-uhd.dtsi in arch/arm64/boot/dts/somc/ and overwrite the original file
Then, build as follows:
Code:
# Kernel build parameters, adjust paths according to your environment
export CROSS_COMPILE=aarch64-linux-android-
export ARCH=arm64
export KBUILD_DIFFCONFIG=pdx203_diffconfig
export PATH=$PATH:/home/maxamillion/workspace/tools/kernel/aarch64-linux-android-4.9/bin/
# Change this to wherever you checked out kernel
cd ~/workspace/kernel
# Do this once
make O=./out aosp_edo_pdx203_defconfig
# Do this to rebuild dtbo
make O=./out dtbs
# Create flashable image
mkdtimg create dtbo.img ~/workspace/kernel/out/arch/arm64/boot/dts/somc/kona-edo-pdx203_generic-overlay.dtbo
Great work buddy this is proof the phone can do it
I wish Sony would FFS I don't really want to start messing with the phone for it, I haven't done that sort of thing since the Nexus days.
Does this change any option in settings? I don't have to have the bootloader unlocked do I?
lhubbard0 said:
Does this change any option in settings? I don't have to have the bootloader unlocked do I?
Click to expand...
Click to collapse
I'm pretty sure this requires root therefore you need bootloader unlocked.
I experimented a bit more and it seems that the DTB changes aren't enough to bump the framerate even slightly, one of the added MIPI commands in the 120Hz commit seems to map to this command used on Oneplus's 90Hz phones so I tried matching that up, but no luck. Looking at it under a 240FPS camera though, it's definitely still only updating the panel at 60Hz (with a surprising amount of ghosting) so I can't imagine it'd look all that good at 120Hz anyhow? But even the commit admitted that, I can't imagine they'd have a way to update the panel faster and then not use it to reduce ghosting.
shinyquagsire23 said:
I experimented a bit more and it seems that the DTB changes aren't enough to bump the framerate even slightly, one of the added MIPI commands in the 120Hz commit seems to map to this command used on Oneplus's 90Hz phones so I tried matching that up, but no luck. Looking at it under a 240FPS camera though, it's definitely still only updating the panel at 60Hz (with a surprising amount of ghosting) so I can't imagine it'd look all that good at 120Hz anyhow? But even the commit admitted that, I can't imagine they'd have a way to update the panel faster and then not use it to reduce ghosting.
Click to expand...
Click to collapse
Nice, find. Haven't been on xda as of late. I had found the option through the image quality settings using quick shortcut maker but that's code left over from the 5ii. Genuinely impressed you dug deeper. I'm assuming you're bootloader unlocked.
I tried this on dotos 5.1 rom, it actually got less frame rate after flash dtbo.img. Is this only working on the stock Sony android? The frame rate did show 120, but it is much much laggy then 60hz. So I reverted back.
shinyquagsire23 said:
I experimented a bit more and it seems that the DTB changes aren't enough to bump the framerate even slightly, one of the added MIPI commands in the 120Hz commit seems to map to this command used on Oneplus's 90Hz phones so I tried matching that up, but no luck. Looking at it under a 240FPS camera though, it's definitely still only updating the panel at 60Hz (with a surprising amount of ghosting) so I can't imagine it'd look all that good at 120Hz anyhow? But even the commit admitted that, I can't imagine they'd have a way to update the panel faster and then not use it to reduce ghosting.
Click to expand...
Click to collapse
What if you set the resolution to 1080p will 120hz work properly like Xperia 5 ii
Related
Switcher 4K
Hi,
I built a simple app that allow you to quickly switch the virtual resolution between default 2K and 4K without a computer.
Unfortunately, since the command is not available on the userland, the process needs superuser permission to change virtual resolution.
If you somehow manage to break your resolution, especially leading to crash loop of Xperia Home, check on other topics how to restore the original values.
Since the custom feature can be "dangerous" for the reasons above, I added a check when save and switch custom values to avoid any resolution under [email protected] (Z5 Compact default values).
Min Android version: 6.0
Target: 9.0
Screenshot(s):
{
"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"
}
Changelog:
Code:
v1.3: Updated to SDK 28 (Android 9.0).
Updated description string with "XZ2".
Removed useless email button.
[COLOR="Red"][B]Uninstall previous versions before installing this one ![/B][/COLOR]
v1.2: Implemented customization button and form. Values are saved in app storage.
v1.1: Implemented App Shortcuts (Android 7.1+).
Switching to 2K now reset to OEM values, not set 1080p ones.
v1.0: Release.
Planned in future releases (low probability..):
Code:
* Tab with buttons in the notification list.
* Widget with buttons, maybe.
* Any idea?
Download:
Grab the APK here or it is available on Play Store.
MD5
Code:
1.0: 16235380d92fff111e8327b3100a07e8
1.1: bb1a9b6130cb1c4633fd237e2015272f
1.2: 6c3d6ece09ea8305c7f4e40d23ad4dd0
1.3: 3d89fec72d3e5804cd46bab417e6c702
Nice! It would make more sense if it said "Xperia Z5/XZ Premium though!
Can you please change? :angel:
FartyParty said:
Nice! It would make more sense if it said "Xperia Z5/XZ Premium though!
Can you please change? :angel:
Click to expand...
Click to collapse
Thanks, I will change it for the next revision.
Hey,
Released v1.1, adding App Shortcuts, switch to 2K now reset to OEM values, and FartyParty's request.
Nice work friend. :good:
Hey,
Released v1.2 that add custom values support. Check the first post.
If anyone have more accurate values about the limit resolutions supported by Xperia Home, let me know I will update the security checks.
Looks good! Thanks !
Dialler crash all the time can't make call
Shellyaffff said:
Dialler crash all the time can't make call
Click to expand...
Click to collapse
Yes, it is one of the goal of this app, being able to switch back to 1080p without a PC to use apps that doesn't support 4K.
The phone app is the most common known issue.
Is the battery consumption less?
Not much for usual usage, I suppose much if you play 3D games.
There is another topic I don't remember where speaking about this.
When set to 4k, the phone app no longer goes. g8141
Used this mod for over a week I sometimes get like a fpash of white light kind of flickering on.screen
Shellyaffff said:
Used this mod for over a week I sometimes get like a fpash of white light kind of flickering on.screen
Click to expand...
Click to collapse
You mean during the resizing ?
Get the screen flashing light and dark like screens messed when it's not though works perfectly. Then suddenly get flickering
Wow looks like weird...
What definition are you using ?
As described looks like a screen issue of your phone.. It happens in 1080p too ?
I saw that the best dpi on the 4k resolution without crashing any app wasn't 807 but 706, 720 or 721, I don't remember exactly sorry
This app do the same job like adb command (wm resolution 2160x3840)?
simondd said:
This app do the same job like adb command (wm resolution 2160x3840)?
Click to expand...
Click to collapse
As far as I know, it does the exact same thing as the ADB command (except through an app).
It said that the newest file couldn't be found (error: 410)?
I tried the older version (1.1) And the program doesn't seem to do anything, is there a way to check?
What is PWM?
Pulse Width modulation (PWM) is a way to control display brightness.
When you lower the brightness, the light intensity of the display is not reduced by voltage, but instead quickly turned off and on by the electronics with a fixed frequency.
If this frequency is high enough (>4000hz), it is indistinguishable by the human eye.
Why is Samsung AMOLED using PWM?
AMOLED can't be dimmed low enough (<40cd/m2) by just reducing voltage without noticeable image deterioration.
This deterioration affects grayscale linearity, color temperature and shows another display issue called mura defects.
Grayscale linearity and color temperature can be corrected to some extent by the display driver.
But mura defects are basically small irregularities / deviations caused by the OLED production process and will become more visible with lesser voltage applied.
PWM can prevent those issues by dimming the brightness with short on/off intervals instead of voltage dimming, thus the applied voltage can be high enough (~100cd/m2) to avoid optical deterioration and we still perceive a lower brightness.
What is the problem with PWM?
PWM is not bad per se, it is the very low frequency of 240hz that Samsung chooses to implement.
Some people that are very susceptible to flickering (often without knowing it), may notice eye strain, headache or even nausea (comparable with motion sickness).
This is also the reason why almost all modern computer displays are assembled with a flickerfree backlight.
Oscilloscope measurements
Default kernel PWM behaviour with 240hz (10% on-time and 90% off-time ratio).
{
"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"
}
Flickerfree kernel with a more consistent amplitude (note: the 60hz refresh interval is intended).
Kernel PWM comparison
Default kernel.
Flickerfree kernel.
PWM visualized in slow motion
Both videos are starting at 100% brightness -> 60% -> 20% -> 5%.
Left video: stock kernel, right video: flickerfree kernel (the pink stripe is the refresh interval).
Disadvantages
If the brightness is below 40cd/m2 the visibility of the above mentioned mura defects will increase.
Download:
flickerfree_dream2lte.zip
Credits:
Kernel Source by Samsung
Vendor libraries from Renovate
Exynos DTBH from jcadduono
ixbt.com review
laptopmedia.com review
Source:
kernel_samsung_dream2lte
The refresh interval (Vsync) seems like a necessary OLED function, as it is also used by LG OLED PWM free devices Flex 2 (60hz) and B6 (120hz):
ixbt.com
rtings.com
It is a pleasure to see around again, mate. Your work has always been an inspiration.
Hi, please
work with oreo?
Hi
Thanks for your work. I have been looking for this and its great to have it.
I have flashed it but the phone is stuck at Samsung logo. It doest boot. Please can you help me. I have a dual dim unlocked INS phone and am on latest Ironman RoM.
Edit: flashed v2 it is stuck at installing android app 39 to 56.
@neitin
This seems like a problem with mismatching vendor libraries, i use the Kernel with the current stock Samsung firmware (G955FXXU1AQK7).
I will later take a look what might cause this issue on the custom rom.
does it work on AQH3 ?
Wootever said:
@neitin
This seems like a problem with mismatching vendor libraries, i use the Kernel with the current stock Samsung firmware (G955FXXU1AQK7).
I will later take a look what might cause this issue on the custom rom.
Click to expand...
Click to collapse
Hi Wootever, please can i ask you to let me know which RoM are using, I flashed Batman rom with stock kernel and flashed your kernel, but failed, tried on ironman rom with stock kernel in aroma and it fails to boot.
Thanks in advance.
@neitin
I'm using the current default Samsung rom (G955FXXU1AQK7), it can be downloaded with SamFirm.
Edit:
Region codes can be found here.
If you decide to flash the stock Samsung rom via Odin, don't forget to create a backup of your /data and /sdcard partition to an external card as the original boot.img will encrypt those partitions.
Thanks @Wootever
I was on RpmAur-2.1 and flashed the kernel, all works well and I can proudly say that my eyes are not burning as it used to earlier.
Thank you for your work, Cheers
Don't boot, stay in Samsung logo
Renovate AQK7 + Firmware AQK7
jujusito said:
Don't boot, stay in Samsung logo
Renovate AQK7 + Firmware AQK7
Click to expand...
Click to collapse
I had the same issue. Refer couple of post above for resolution
Sent from my SM-G955F using Tapatalk
I made some adjustments to retain the calibration and overall image quality, it should be pretty much identical with the stock kernel now.
The difference is basically the increased visibility of mura defects without PWM (flickerfree kernel behaviour) or almost no visible mura defects with PWM enabled (stock kernel behaviour).
Here is a quick comparison photo:
(Stock kernel is on the left side; if you look closely you can see the some repeating transversal lines, those are the typical PWM lines captured by camera.)
(Flickerfree kernel is on the right side; there are some bright dots that looks like compression artifacts, those are mura defects.)
Edit:
Here is another photo for a better comparison (left side: mura defects masked by PWM, right side: visible mura defects due to missing PWM).
(Note: those mura defects are especially visible on very low brightness <20cd/m2, anything above 40cd/m2 shouldn't be noticeable).
More information about can be found in the Samsung AMOLED patent description: Organic light emitting display device and driving method thereof
neitin said:
I had the same issue. Refer couple of post above for resolution
Sent from my SM-G955F using Tapatalk
Click to expand...
Click to collapse
If the solution is flashing stock rom with odin i don't want this.
This kernel need more compatibility with custom roms, v3 and v4.
Don't work for me, stay in Samsung logo when boot.
Welcome aboard sir! I was just curious about this kernel last night. Was thinking to myself, I miss the flicker kernel for the edge and was going to seek you out to see about a port but looks like its an early Christmas for me
jujusito said:
If the solution is flashing stock rom with odin i don't want this.
This kernel need more compatibility with custom roms, v3 and v4.
Don't work for me, stay in Samsung logo when boot.
Click to expand...
Click to collapse
Just an heads up I have tested on Batman Rom and it works flawlessly.
Sent from my SM-G955F using Tapatalk
Nice to see this on S8 source
Can we still toggle it via echo 0 / echo 1 ?
I added the flickerfree setting to the S8 (G950F) panel driver. If someone is willing to test this version please report back if it's working correctly.
flickerfree_dreamlte.zip
(note: for now the lowest brightness step is set much higher (300cd/m2) to verify that the flickerfree brightness table is working.)
@djb77
Not yet, but i might add that in a future version.
Wootever said:
I added the flickerfree setting to the S8 (G950F) panel driver. If someone is willing to test this version please report back if it's working correctly.
flickerfree_dreamlte.zip
(note: for now the lowest brightness step is set much higher (300cd/m2) to verify that the flickerfree brightness table is working.)
@djb77
Not yet, but i might add that in a future version.
Click to expand...
Click to collapse
I've been speaking with @morogoku (author of MTweaks) about it. We may even able to patch it to make it work.
I'll have a look at both sources today (hero and dream) and see what I can do.
I've noticed the changes in the hero code which check for the 0 or 1 o be enabled, doesn't look too complicated, but ofcourse if you do have time it would be appreciated if you can do it yourself to make sure its 100% correct.
Once again thanks for supporting the S8 with this
After being bored for quite some time i found a way to bypass the horrible noise reduction and oversharpening via an external app without voiding the warranty in any way, but this results in a quite raw looking image being in jpeg, so you need to apply your own noise reduction via photoshop or any else method.
Using FreeDcam app from the play store
Set the main camera api to camera1
Jpeg quality - 100
CustomMatrix - imx362
And on the right side of the menu
Wavelet Denoise - Denoise-off
Zero shutter lag - on
You can also change anything if u swipe up from below except the iso, because u change the iso from the left iso button, i recommend setting sharpness the prism to 0-10
{
"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"
}
Moto camera
FreeDcam
Moto camera
FreeDcam
Moto camera
FreeDcam
Idk this app sucks too much battery. Maybe because of processing images.
pradsngh523 said:
Idk this app sucks too much battery. Maybe because of processing images.
Click to expand...
Click to collapse
well its kinda obvious the app is in a bad state, its quite unstable and sucking battery doesnt really suprise me.
TheIronLefty said:
well its kinda obvious the app is in a bad state, its quite unstable and sucking battery doesnt really suprise me.
Click to expand...
Click to collapse
Well i figured out i was pushing it too hard with hdr scene mode and forgot to change api to camera1
Working like a charm now .
Thanks buddy. Also try moving this thread to "Apps Themes and Mods" section
Thanks for this workaround - it really makes a difference especially for us without the time to root the phone.
Is there a way to make FreeDcam app to make a shutter noise so that we know we actually took a picture? Right now there's no indication and I have to go to the gallery to make sure.
I applaud the effort to find another workaround!
This is interesting to me, however I must admit- those images have a lot of ugly artifacts that are now baked in. Yes, it appears to be getting around the NR smoothed look, but it looks like it is doing so by adding a layer of grain before the jpeg compression. Without the camera2 api, I'm not sure it is possible for an application to actually access the raw frame buffer before the chromatix, etc, libs get involved. My first hunch in that this look is artificially created by the app after the camera routine has done its processing.
In other words, it looks almost like grain is being added to give the illusion of details in much of the same way we can get details in lower color spaces via dithering. Even relatively well exposed parts of the frame that shouldn't have noise have noise. And then some heavy jpeg compression on top of it, so removing it in post with Photoshop/LR/etc is going to eat a lot of detail- arguably at least as much if not more than you were getting with moto cam. Have you tried to clean any up in post and compared them side by side with moto cam?
Interestingly, if you enable the camera2 API, there is a version of FreeDcam that can record actual sensor RAW from the G5+, and one of the only apps that can properly. But once you are doing that you are better off with any of the various Google Cam versions floating around for 32-bit Nougat. Root access isn't necessary, however in order to enable the camera2 api, you need to be able to change a line in build.prop. At the very least, you need to unlock the bootloader so that you can change a system file. You can remain stock and unrooted though. I know, not for everyone, but I recommend it if image quality is important to you.
I still think you need to enable camera2 at a minimum to get better image quality, if not just replacing chromatix libs. But this is an interesting find.
A guide to access the hidden 120 HZ display settings in your Galaxy S10 and Note 10 Devices
*Disclaimer: I am not responsible for any battery drains, boot loops or anything that harms your devices by using the below application and guide*
Pre-requisites:
1. Make sure you have the latest OneUI 2.1 Update.
{
"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"
}
2. Not on "medium power savings mode" (It only works on optimized or high-performance mode)
3. Your screen resolution must not be in WQHD+
4. Installed "Activity Launcher App" by Adam Szalkowski Download from Play Store.. Let's give him a thumbs up on the Play Store.
Step 1 :
Open the Activity Launcher App from the app drawer and in the search box type the keywords "motion" or "smoothness" and you should be able to see an Activity with com.android.settings.$HighRefreshRatesSettignsActivity
Step 2 :
Click on it and this Activity should open up (make sure you're not using WQHD+ screen resolution and not in any power savings mode).
Step 3:
Choose the High Refresh Rate (120 HZ) option and click Apply! Your screen will now refresh at 120 HZ.
P.S: I am not sure how much of a difference you'll find but I could feel the difference overall. I haven't tested the battery drain on using this. I'll update the thread once I get the results done.
-- Reserved --
is working but don't see any difference !!
@CsabaZz Maybe because you don't understand how the hardware works. Display refresh rates can be overclocked in your PC monitors, the same way quite some phone screens refresh rates were overclocked and I strongly recommend you to take a good read on the forums.
Why don't you question Samsung on their forums and see why this option is available on S10 & Note 10 devices.
Let's not be rude on the forum.
This is only for snapdragon?
cogelindo said:
This is only for snapdragon?
Click to expand...
Click to collapse
No. Exynos too. I flashed via Odin One Ui 2.1 and I got this option in activity launcher. I don't know how much of a difference it makes. I think I feel some kind of difference but maybe it is a placebo effect.
There are apps and web sites testing and providing information about refresh rate. Go and see - it will not change if you tick 120Hz. S10 has 60Hz (or 60 FPS, if you want). Just because an S20 setting can be found on S10 (which is hidden by default), it does not mean that it will work.
XmlNode said:
There are apps and web sites testing and providing information about refresh rate. Go and see - it will not change if you tick 120Hz. S10 has 60Hz (or 60 FPS, if you want). Just because an S20 setting can be found on S10 (which is hidden by default), it does not mean that it will work.
Click to expand...
Click to collapse
Agreed
Tested myself as i own s20 ultra and s10+ . On the s10+ even on the "120hz" settings it has a refresh rate 60hz verified by an app witch shows 120hz on thé s20 ultra so unfortunetly this is not possible due to hardware..
120hz won't work on S10+ ... just do one think after choosing 120hz options from the settings try using this adb command and if 96hz doesn't work keep going down !! Like 90hz or 70hz
adb shell settings put system peak_refresh_rate 96.0
adb shell settings put system min_refresh_rate 96.0
Original post is from S20 thread - https://forum.xda-developers.com/ga...te-to-96hz-t4073867/post82130937#post82130937
And please do it at your own risk !!!
After using this and applying 120hz setting, it didnt work. I tested the fps from multiple apps and all of them are showing 60hz.
Considering how samsung has always been eager to be the first one to introduce bleeding edge tech. It wouldn't be like them to hide the potential of their displays. Samsung has said in the past that they provided 90hz panels to oneplus and other brands but didn't use them themselves bcz they weren't fully confident about the colour accuracy and other parameters. As much as I'd like this news about 120hz on s10+ to be true I don't believe it is.
This is for sure not gonna work on the N10+ as we don't have the software or hardware to support it. The screen is not able to do it.
So if it doesn't work, then what's the point of using it? For decorative purposes or just to have a useless button that says "120 hz" in the screen settings menu?
This should be locked and deleted since this doesn't work and is clearly just an oversight and time saving on samsung's part in developing the S20 software
Guys, this menu is not visible or accessible by default on S10. Complaining about why it is there at all is pointless. The new UI's code is probably common between the S10 and 20 and some menu elements use a feature flag to switch unnecessary or not supported parts on/off. That's all. This thread could be closed, anyway.
I think I know what is going on. One Ui 2.1 has improved animations (in comparison to 2.0), and this is why we think (placebo effect) that by enabling this hidden menu, the refresh rate has been increased.
:good:
i don't see any harm sharing this tidbit regardless of whether hardware supports it or not
Sent from my SM-N975F using Tapatalk
It simply cannot work.
First the hardware does not support it. If it did work Samsung woulve advertised the same.
Second, you have to launch it via an activity manager which means samsung didn't want you to discover the feature in the first go.
Third, I'm pretty sure Samsung will remove it over the next couple of updates as it's only for the S20's hardware.
Anyone knows if is possible change resolution in adb? Or someting
Pretty sure you used to be able to use the following command
For resolution:
adb shell wm size 1080x1920
For screen density:
adb shell wm density 390
Obviously adjust numbers to suit your needs.
I accept no responsibility for any issues which may occur if you use these commands
Edit:
Did a quick bit of googling and found this which echos the above:
https://www.reddit.com/r/pokemongodev/comments/6554k1/_/dgfpesr
I know this is quite an old post, but couldn't find a newer one mentioning if changing screen res works. Did these commands worked fine with the 6 pro? And is there any noticable difference in battery life/performance if it does work?
I'm interested too. Give it a shot and report back on the results? I'm in the car all day, otherwise I would
There is also the "smallest width" setting under the developers options menu. I set mine to 720 for higher resolution.
B from C said:
There is also the "smallest width" setting under the developers options menu. I set mine to 720 for higher resolution.
Click to expand...
Click to collapse
I just tried that and needed to pull out my magnifying glass lol. Everything was so small!!
I've got mine at 474 with font set to large... happy medium for me
Gave it a try just now and it does work, however definitely not what I expected. Basically adds 2 huge top/bottomn notches and brings your rendered screen in the middle. Bottom gestures are almost impossible, as you have to start somewhere middle in the screen. And for unlocking the device - now you need 2 fingers - one to trigger the FP scanner because it ends up in the bottom right and one on the actual Scanner. Also you end up with a weirdly placed camera cutout that you cant remove.
I might try to run my phone like this for a day, as I wanted to experiment how the battery behaves. Menus seems really fast and smooth, but can be because the animations have less space and are shorter . If anyone has an idea for a command to stretch the screen over the whole display, I'd love to try.
Edit: Never mind, dumb me didnt adjust for screen ratio not being what I'm used to. After taking that into account 1080x2340 works. Fingerprint and camera cutout issues still persist though.
While this may be a little small/sharp for some people, I've been running "Smallest Width" at 720, which seems to yield a "Display Size" of 320dpi, along with default font size for awhile and have had no issues with the camera cutout or the fingerprint reader. I also use the AOD Notify app to put a glowing ring around the camera and didnt need to make any offsets so I'm pretty sure my camera cutout is where it's supposed to be.
I ran 320dpi/720width for years on a few Samsung Note devices prior to my P6P so that's what I'm used to (I'm one of those people who run a 4k tv as a monitor with no scaling). You may need to play with different dpi and font combinations until you find something you are comfortable with. In rare situations I have needed to restart the device or clear the cache for all UI elements to resize correctly after a change.
After a couple days of testing (it did indeed took me 2 days to kill my phone) I figured that for whatever reason, on the Pixel (maybe exynos) lowering the render res does indeed save some battery. On 1080p I managed to get around 1%/h - 2%/h less consumption on Screen on Time, which for people like me who manage to get 5+ hours of screen on time can result in quite of a difference. I regularly end days with something between 30-40% battery, which is still really good but I won't go to a second day as the 2 hours charge time is really annoying me .
With the lower resolution I ended the first day with 57% and I ended up with 37.5 hours of standby and 8 hours and 40 min of SoT in a full charge. I even went further by reducing the resolution to 720p, but it is really obvious that Google never made a 720p phone - almost all UI's broke and even changing the brightness was a hassle. I also believe that it might have triggered some rouge process as my phone lost 10% battery in less than an hour, so I switched back to my original 1440p.
To conclude this - is changing your resolution to 1080p worth the broken finger print - depends. In my example, I would probably do it if I know I am going on a trip where lots of pics/videos will be taken and heavy navigation use, as my phone is more of a tool in cases like that and I always try to squeeze every bit of battery I can. If google does implement the ability to change the res though - I would definitely switch.
I just wonder, why does it made such a big difference on this phone, but it didnt for S10(the only battery test I found on a video). Is Android 12 harder to drive? Or are these LTPO panels more intense on the GPU? Or is it even exynos/mali GPU not as efficient as SD on rendering UIs? If anyone wants to chime in - Id' be glad to hear some opinions. ( Or maybe I just used my phone less.. that would be the worst )
P.S. Just to say this was done on 60hz and that your milage might vary, if you decide to try. Everyone's usage is different and in my case I work from home - so WiFi connection (although router is far) but horrible signal, as I am a top flat in the UK (worst case scenario). The setting I used for the adb command is 1080x2340 and denstity was 400, although density is preference I guess and I believe wont affect battery.
{
"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"
}
Yessss... I changed it... All. Works
Download app easy dpi changer from playstore
Easy DPI Changer [Root] - Apps on Google Play
Make your screen yours
play.google.com
And set this value
Need root
If want to stock values only tap to reset and all come back to stock value
liver20 said:
Yessss... I changed it... All. Works
Download app easy dpi changer from playstore
Easy DPI Changer [Root] - Apps on Google Play
Make your screen yours
play.google.com
And set this value
Need root
If want to stock values only tap to reset and all come back to stock value
Click to expand...
Click to collapse
For what it's worth, with Android 13 Stable and the Kirisakura custom kernel, you can now change to 1080p from Android settings.
XDA Article: Google Pixel 6 Pro gains 1080p support thanks to Android 13 and a custom kernel
roirraW edor ehT said:
For what it's worth, with Android 13 Stable and the Kirisakura custom kernel, you can now change to 1080p from Android settings.
XDA Article: Google Pixel 6 Pro gains 1080p support thanks to Android 13 and a custom kernel
Click to expand...
Click to collapse
And doesn't break the fingerprint scanner like Easy DPI changer does
There must be a way of doing it without opening the bootloader, right? Or do you guys think it's impossible without breaking stuff like the fp scanner? I'd love to lower my resolution but I really didn't want to lose all my stuff and have to reinstall everything at this moment.
Another method to adjust screen resolution/size/dpi: I noticed the "AOSP Mods" module for LSposed/Magisk has an option in the "Miscellaneous" section for "Display resolution". The slider does work and changes the resolution on my P6P without modifying the smallest width developer setting. YMMV
forum link
B from C said:
Another method to adjust screen resolution/size/dpi: I noticed the "AOSP Mods" module for LSposed/Magisk has an option in the "Miscellaneous" section for "Display resolution". The slider does work and changes the resolution on my P6P without modifying the smallest width developer setting. YMMV
forum link
Click to expand...
Click to collapse
Thanks a million for this. The module fixed my screen flickering - couldn't go over approx 50% without flicker . I set the screen brightness from within Miscellaneous. Only problem is that I can't access Miscellaneous again without module force closing (other options are fine) - looking into the reason for it.