Develop Bugs

[KERNEL] GALAXIAN [344MB][JVU][Voodoo Sound][EXT4][BLN][COLOR]

{
"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"
}
*
Galaxian kernel was made to improve your Galaxy S usage experience.
If you are looking for fast and stable kernel, this one is for you!
Why Galaxian?
Based on latest source from Samsung Open Source Release Center and always latest initramfs
344MB RAM memory without side effects like loosing HD capabilities
EXT4 and RFS support with autodetection
ClockWorkMod Recovery v3.0.0.5
Ondemand governor with tweaked up/down scaling
Voodoo Sound v10
Slightly increased charging current limits for both AC and USB charging modes
Improved touch sensitivity
Front camera is working (no snapshot when recording support)
Video calls are working
Modules compiled with -O2 flags
LZMA kernel compression, GZIP initramfs compression
Low Memory Killer levels are just perfect
Unbelivable colors and sharpness
Brightness levels are now fixed (no more red tint on each)
Fixed MDNIE profiles (outdoor mode can now work together with selected color temperature).
Light sensor driver fine tuned
WiFi driver buffer is now bigger
New jpeg compression mode from Galaxy TAB
Read A Head parameter increased to 512KB
BLN support
Optimized compile flags
CPU clock speed switch is now faster
Custom bootanimations support! just name yours as sanim.zip and place in /system/media/
Minor tweaks
Where to get it?
Click here!
How to apply?
Please use Odin and choose Galaxian....tar in PDA section (without pit file, repartition or bootloader update!)
Want to convert your RFS -> EXT4?
There are two simple ways to do that:
Use Chainfire's EXT4 Tools (ignore warning message)
Use Galaxian ROM which will do that for you automatically
Any sources?
Click here!
I would like to say thank you to everyone
who helped me with this project!​
*Logo is a trademark of NAMCO BANDAI.

let's see how it works
Edit: Great kernel, best one for StockRoms.

WoooHooo what a Features
nyc one Brother

nice!
will try it out

is there a jvh edition?

No but can be if community want to

Do I disable lagfix before flashing the kernel?

is there any way you could implement voodoo color in this kernel ?

fuzzvirus said:
Do I disable lagfix before flashing the kernel?
Click to expand...
Click to collapse
No! There is autodetection system build-in! Kernel boot's up with RFS and EXT4.

reneimas said:
is there any way you could implement voodoo color in this kernel ?
Click to expand...
Click to collapse
No, sorry, I've tried voodoo colors and I'm not happy how it performs. Check this version, I've applied Speedmod color fix with my own changes, all is sharp and vivid.

Lukiqq said:
No, sorry, I've tried voodoo colors and I'm not happy how it performs. Check this version, I've applied Speedmod color fix with my own changes, all is sharp and vivid.
Click to expand...
Click to collapse
I am using your kernel right now. The colours are not bad but still wish i could control the contrast through the voodoo app. P.s does this kernel automatically converts everything to EXT4 or is it manual because weirdly i get really rubbish quadrants scores on [F1 Galaxy S2 V3.1] rom :/

Nice.
Couple of things to note, OC WILL freeze on some phones, including mine... every phone is different.
Ondemand sample rate of 40000 may cause music to stutter and will need to be raised to something like 60000+.
Nice work though.

features look good i want to try right now

lpy said:
Nice.
Couple of things to note, OC WILL freeze on some phones, including mine... every phone is different.
Ondemand sample rate of 40000 may cause music to stutter and will need to be raised to something like 60000+.
Nice work though.
Click to expand...
Click to collapse
Thank you! I've tested it on 3 phones and didn't noticed any problems with OC, but you have right, things may happen. If so, tell me, I'll tune some voltage values.

reneimas said:
I am using your kernel right now. The colours are not bad but still wish i could control the contrast through the voodoo app. P.s does this kernel automatically converts everything to EXT4 or is it manual because weirdly i get really rubbish quadrants scores on [F1 Galaxy S2 V3.1] rom :/
Click to expand...
Click to collapse
Read carefully 1st post There is something about EXT4, even attached apk to do so.

on my phone neocore and quadrant shows 48-49 fps only. but quadrant is around 3300

if i have lagfix enabled can flsah it?

Lukiqq said:
Thank you! I've tested it on 3 phones and didn't noticed any problems with OC, but you have right, things may happen. If so, tell me, I'll tune some voltage values.
Click to expand...
Click to collapse
Unfortunately, raising/tuning voltages can sometimes make things more unstable. Some CPU's simply can't handle it no matter what you do. That's just my experience though, we'll see how it goes for others.

mar90 said:
on my phone neocore and quadrant shows 48-49 fps only. but quadrant is around 3300
Click to expand...
Click to collapse
Neocore 64.5
Quadrant, tunnel test about 520 points, overall result as I've said in description.

the spica master from samdroid.net come back to here ..hhe..
i'll test your kernel..
Sent from my GT-I9000 using Tapatalk

CM Automatic Backlight Settings (explained)

Got fed up with the lack information so I did some googling and made a post on my blog.
My Bloggy
If anyone has any good links or info to add that would be greatly appreciated! I'm still personally trying to find my own settings.
The Automatic Backlight settings (CyanogenMod settings-->Display-->Automatic Backlight) allow you to customize how your phone reacts to changes in ambient light measured by the phone. You can control how many light level ranges you want to monitor, and how bright you want the screen, keys, and keyboard buttons to be at each range. Of course you have to enable Automatic Backlight in the normal Android settings first (Display-->Brightness).
In googling around on this I've found a number of different approaches and preferences, and it really is something that is very subjective - enough light for one person at a particular ambient light level is too much for another, and vice versa.
{
"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"
}
The first three settings: Windows length, Reset threshold and Sample interval control the filter conditions. The Windows length is the amount of time for the average figure, while the Sample interval is how long the system waits to take a sample. Personally, I go with larger figures to reduce system load and save battery life.
There are two primary benefits offered by filtering:
1. It can allow you to set up smoother brightness transitions (assuming you also increase the number of custom levels)
2. It can decrease the likelihood of screen flicker in mixed lighting. ( You may find yourself in mixed lighting conditions that straddle two raw brightness levels. Without filtering, these raw levels may cause your screen to repeatedly shift back and forth between two brightness settings. I've found this can easily happen with artificial lighting as it is more directional than natural lighting. Sitting in your office, for example, you may find that simply shifting the angle at which you hold the phone changes the brightness reading.)
Notice that without filtering, the screen brightness jumps back and forth between 70 and 55, which can be very distracting. The filter, on the other hand, maintains a single value for the screen brightness, even under these fluctuating lighting conditions.
Window Length: Filtered value is the average sensor value during this period. Larger values = slow response.
Reset Threshold: There may be times in which you want the screen to respond quickly to changes rather than slowly ramping. Moving from a dark building out in to broad daylight, for example, you don't want to watch your screen slowly brighten over the course of 30 seconds: those are 30 seconds in which your phone may be unreadable. This is where the reset threshold comes in handy. If a raw reading differs from your current average by this amount, the filtered value is immediately reset to the raw value. Finding the right value for your reset threshold allows you the best of both worlds: a screen that gradually changes based on subtle light changes, but responds rapidly to extreme changes.
Sample Interval: Low value can improve accuracy but uses some more CPU.
Allow Light to Decrease: This is a very simple option. If this is checked, your screen brightness will increase and decrease according to your custom levels. If it is unchecked, your screen will brighten as the light sensor reads higher values, but will never darken, even if the sensor detects that you have moved to a very dark area. I'm not quire sure why anyone would want to uncheck this, but maybe I'm missing something.
Decrease Hysteresis: Reduces flicker when decreasing brightness
In conclusion, if you want a screen that responds very rapidly to changes in ambient lighting, possibly at the risk of flickering, decrease your filter window (or disable the filter completely) and increase your sample interval. If you want a screen that never flickers, possibly at the risk of slow responsiveness, increase your window.
Filter A: 10 second window, 2 second interval
Filter B: 20 second window, 2 second interval
Filter C: 30 second window, 2 second interval
Filter D: Same as Filter C, but includes a reset threshold of 2000
*Note how the inclusion of a reset threshold on Filter D allows for immediate responsiveness under extreme light changes while still preserving the gradual shifts at smaller changes.
As for the light sensor levels, you'll have to play with them yourself. Go to a dark area... and adjust the screen level until it's at a brightness that's comfortable for you. Then gradually increase it up to whatever is fine for outside brightness. Near the bottom you can select more levels as well.
As previously said, I mainly want to collaborate and find the best settings for our phone. Any information to add would be great. Thanks.
Sources:
Numerical explanation of the CM7 automatic backlight settings
CyanogenMod Secrets: Custom Automatic Backlight settings

Very detailed explanation, should be pinned and include in the CM wiki if not already done so!
Thanks!
Sent from my Xoom using Tapatalk 2

Thank you so much for the detailed overview. Very well done. Agreed...should be stickied.

How about you post your settings?

Excellent post. Needs to be a sticky.

And for those that are curious these ROMs (likely others) have the same implementation:
-AOKP,
-Gummy,
-Slim,
-???

CMNein said:
And for those that are curious these ROMs (likely others) have the same implementation:
-AOKP,
-Gummy,
-Slim,
-???
Click to expand...
Click to collapse
liquid
Sent from my Galaxy Nexus using XDA

emd2009 said:
How about you post your settings?
Click to expand...
Click to collapse
+1
Sent from my Galaxy Nexus using xda premium

s4vva said:
Excellent post. Needs to be a sticky.
Click to expand...
Click to collapse
This isn't really my work so I don't think it should be stickied. I just found some old posts and read **** on the internet. lol

wow first time i read this 3ad..very usefull.i always have some doubt about how it works the automatic backlight settings..honestly i have always the phone to max brightness,but now i want to know better how it works this features.thanks for the wonderfull 3ad.

Screen and black levels WAY too black?

Compared to my N4, the screen has deeper blacks, but in a very bad way. You lose so much detail on some pictures, even at full brightness. Like with a picture of black fur my N4 will show all the nuances and shadows caused by the fur, but the Sony will just be pitch black. The amount of detail is pretty significant. Overall, the tone of the screen is just darker, and it kind of makes you sad using it.

I have the same opinion, this is the most annoying thing on this phone. I had very strong feeling to return it back to the shop.
Any solution for this? I can increase screen backlight, but it is not ideal solution and it does not solve the problem.

toiletsss said:
Like with a picture of black fur my N4 will show all the nuances and shadows caused by the fur
Click to expand...
Click to collapse
Upload the picture please.

Yes, blacks are heavily crushed on this device. Here's an earlier discussion of it with links to calibration testers:
http://forum.xda-developers.com/showthread.php?t=2646749
See Erica Griffin's mini review where she discusses the calibration problems and charts the wonky gamma levels here:
http://www.youtube.com/watch?v=a7tQ5n32no8#t=564
If you don't want to install the Display Tester app, here's a link to a black level test image for viewing in your phone browser:
http://www.lagom.nl/lcd-test/black.php
Ideally all of the black squares should be distinguishable to ensure proper reproduction of detail in shadowed areas of an image or video. With Nexus 5, for instance, squares are distingushable from square 2/3 upward.
For Sony Z1 Compact with JDI panel, squares are distinguishable only from square 7 upward. Result: all black levels below 7 look the same on the Z1C, meaning no detail can be distinguished at these levels. One consequence is that low light photos look very inaccurate compared to how they'll look on other displays - if you share or edit them, for example.

I have exactly the same feeling, im from a nexus 4 too and i try to watch some movies on my Z1C and the contraste is juste horrible.
Any ideas on how to fix this?

when its bright ppl say " zomg its wash out"
when black then complain too black

xerox89 said:
when its bright ppl say " zomg its wash out"
when black then complain too black
Click to expand...
Click to collapse
This has nothing at all to do with the brightness of the black levels. This is about how many black levels can actually be seen with this screen. And yes, this is a legitimate complaint.

ghtop said:
This has nothing at all to do with the brightness of the black levels. This is about how many black levels can actually be seen with this screen. And yes, this is a legitimate complaint.
Click to expand...
Click to collapse
This exactly. And thank you for your previous post, it was extremely informative. I was really hoping I just had a faulty screen because I love the phone otherwise. I really love sony's products but the screens on the Z1, Z1s, and Z1c have all been problematic, particularly in dealing with blacks and whites. I really hope these problems are addressed in the Z2 because I really need a replacement for this N4.
Edit: So this affects JDI panels too? From what I read, the JDI panel is much better than the AUO panels.

This is mine, JDI panel...
Using the website...
{
"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"
}
ghtop said:
With Nexus 5, for instance, squares are distingushable from square 3 upward.
Click to expand...
Click to collapse
Using the app...

Heh, remember that there's little point taking a screenshot for comparison unless 1) you shoot it with a camera that has accurate black levels 2) you view it on a screen that has accurate black levels. Otherwise we're all just looking at different things.
Useful info to share in this thread would be how many black levels from that test page you can actually see on your screen (i.e. the number of the last square you can distinguish from another).

ghtop said:
Useful info to share in this thread would be how many black levels from that test page you can actually see on your screen (i.e. the number of the last square you can distinguish from another).
Click to expand...
Click to collapse
I can see from square 7 using the app and the website.

XperienceD said:
I can see from square 7 using the app and the website.
Click to expand...
Click to collapse
Edit: Argh, sorry, my mistake, it should have been 7 instead of 13, as stated in the original thread - corrected now. You can only really see those levels at full brightness in a dark room, though. More detail is lost at normal brightness levels where you aren't being blinded by the whites.

Have to agree, black levels are way too dark. You lose loads of detail in any dark scene, video and photos. Also gamma levels are far too low, at about 1.6 across the board. They should be around 2.2. I'm coming from a galaxy s2 which now seems to have more accurate colour reproduction. Which is disappointing considering it's a super amoled screen vs an ips panel.
Sent from my D5503 using XDA Premium 4 mobile app

There is very simple workaroud for this . Install "Screen Adjuster" app from Google Play, open it, set Contrast value to ca "-30", switch "Adjuster OFF" to "ON" and voila, now you can see black levels up to 1 otherwise, I'm able to clearly recognize only values up to 7 on full brightness on 4.4.2 latest FW .757 with JDI panel using Color Test app
Screen Adjuster: https://play.google.com/store/apps/details?id=com.netmanslab.sa
source: http://forum.xperia.cz/viewtopic.php?f=85&t=9946&p=163390

pcpepik said:
There is very simple workaroud for this . Install "Screen Adjuster" app from Google Play, open it, set Contrast value to ca "-30", switch "Adjuster OFF" to "ON" and voila, now you can see black levels up to 1 otherwise, I'm able to clearly recognize only values up to 7 on full brightness on 4.4.2 latest FW .757 with JDI panel using Color Test app
Screen Adjuster: https://play.google.com/store/apps/details?id=com.netmanslab.sa
source: http://forum.xperia.cz/viewtopic.php?f=85&t=9946&p=163390
Click to expand...
Click to collapse
Excellent, excellent post! Thank you so much for this. It definitely works!

pcpepik said:
There is very simple workaroud for this . Install "Screen Adjuster" app from Google Play, open it, set Contrast value to ca "-30", switch "Adjuster OFF" to "ON" and voila, now you can see black levels up to 1 otherwise, I'm able to clearly recognize only values up to 7 on full brightness on 4.4.2 latest FW .757 with JDI panel using Color Test app
Screen Adjuster: https://play.google.com/store/apps/details?id=com.netmanslab.sa
source: http://forum.xperia.cz/viewtopic.php?f=85&t=9946&p=163390
Click to expand...
Click to collapse
Wish I saw this earlier. Might have to buy it again. Can anybody show examples with dark, detailed photos?

toiletsss said:
Wish I saw this earlier. Might have to buy it again. Can anybody show examples with dark, detailed photos?
Click to expand...
Click to collapse
I just wonder why the hell the Screen adjuster needs full network access, view my network connections, reads precise position GPS, needs access to my bookmarks and history, read the device accounts... Why ? I prefer that sony will modify the contrast in next firmware...

fidel73 said:
I just wonder why the hell the Screen adjuster needs full network access, view my network connections, reads precise position GPS, needs access to my bookmarks and history, read the device accounts... Why ? I prefer that sony will modify the contrast in next firmware...
Click to expand...
Click to collapse
And use 20% of my batteries...

Excellent. I can now see it from box 1. Not sure about battery draining though. So disabling the app for now and waiting for an actual fix in the next release. For some reason, I am very happy that it's a bug in the configuration settings and not an actual hardware issue. Sony has again succeeded in screwing their awesome specs with a ****ty software.

fidel73 said:
I just wonder why the hell the Screen adjuster needs full network access, view my network connections, reads precise position GPS, needs access to my bookmarks and history, read the device accounts... Why ? I prefer that sony will modify the contrast in next firmware...
Click to expand...
Click to collapse
It's ad-ridden, but there is a cheap paid version that requires only the essential draw over other apps permission and does not drain battery

[DTB, Experimental] Enable 90Hz @ 1096x2560 with flashable DTBO image

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

Question Change screen resolution

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.