Yep, that's the GSI I'm using. No need to flash Android 11 first. I went from the latest official 12 firmware to that GSI. I also flashed the latest binaries from Sony's website (fastboot flash oem filename.img) but I have no idea if that was necessary.Oh no, I didn't make those. These are the ones I'm aware off but never installed. The last update is a bit old (may). and the lack of instructions...
So you're using a GSI?
[GSI][UNOFFICIAL][12] Pixel Experience
Pixel Experience for GSI What is this? Pixel Experience is an AOSP based ROM with Google apps included and all Pixel goodies (launcher, wallpapers, icons, fonts, bootanimation) Their mission is to offer the maximum possible stability and...forum.xda-developers.com
Maybe I should look in GSI's instead, being so common support is much better. Did you flash A11 firmware or is this no longer necessary? Or maybe different, could you link me to the instructions you used?
How To Guide [No root] Disply always in 4k mode
- Thread starter kot5nik
- Start date
Pandemic
Senior Member
I hope we'll get a working fix one day but I'm losing hope...
I confirm to.
In the developers option you can change the DPI, I shifted to 630 and it looks fine.
I tried that to on Pro-I but every time I back out from one app to another it's like it recalibrates the resolution and forces it back.
I reckon that's not the case with you?
riceDroid custom ROM has an option to switch to 4k resolution. You can give it a try if you want something different from stock fw.
I'm using riceDroid with Kirisakura kernel for my daily use. It smooth and lots of customizations.
I'm using riceDroid with Kirisakura kernel for my daily use. It smooth and lots of customizations.
This seems to work with the app Second Screen too. You just have to reset the size stuff back to default under Settings > Display > 'Display Size and Text' afterwards.
It looks like the phone reports a physical size of 1096x2560 regardless of what is playing. Even with Cinema Pro playback in 4K.
So, whatever Sony is doing, it's probably passing the video through the upscaler while shutting off the upscaling so that it displays in 4K natively?
So, whatever Sony is doing, it's probably passing the video through the upscaler while shutting off the upscaling so that it displays in 4K natively?
Working on getting this working on the IV on a13 and crossposting here. If anyone knows how to find the maxuiwidth config override that would be useful
forum.xda-developers.com
High Resolution Mod for Xperia 1 IV
Hey everyone, before the official Android 12 release from Sony it was possible to force the display to render at full 4K resolution via "wm size" command. With the release of Android 12 this behaviour changed and it´s no longer possible to...
forum.xda-developers.com
Made a mod here for the IV: https://forum.xda-developers.com/t/high-resolution-mod-for-xperia-1-iv.4517435/post-88762821
Not sure if it works on III, but probably doesn't hurt to give it a shot.
Not sure if it works on III, but probably doesn't hurt to give it a shot.
It doesn't work, but it's close. You have to replace `0x7f070010` by `0x7f070013` in the public.xml values. Then `wm size 1644x3840; wm density 630` works perfectly!
I was making a Magisk module after I saw your first post but you beat me at it. Anyways, here's mine working for the Xperia 1 III. Note that I'm *not* an expert when it comes to Magisk modules so I don't take *any* responsibility if something wrong happen with your device (it shouldn't since the module doesn't do much, but still, you've been warned).
Edit: works on the Xperia Pro-I as well. Thanks to @ragu24 for testing.
Attachments
Last edited:
Pandemic
Senior Member
Yes, me. After flashing the module and rebooting, just do
Code:
# wm size 1644x3840
# wm density 630It also persists during reboots.
Pandemic
Senior Member
What would it take for it to work on Pro-I, assuming I wanted to also cross modify it for us??
You need to extract the system app android.platform.overlay and decompile it. Search in public.xml (in res/values) for the value of the field named config_maxUiWidth (it should be a hex value not far from 0x7f070013)
Note: you could probably get the result easier using idmap2 but I didn't manage to do it and the decompilation method is pretty quick as well.
If the value is 0x7f070013, then you don't need to do anything and the Xperia 1 III Magisk module should work on the Pro-I. Otherwise, go in the Magisk module and decompile the apk file found in the system folder (there's a chain of single folders with the apk file at the end). Go to public.xml and update the value with what you found. Then recompile the apk, sign the apk, and put it back in the Magisk zip module.
For a quick explanation of what this does (and I must thank @phailyoor for his posts in the Xperia 1 IV forum) is that you can overwrite some ressources values in recent versions of Android, in a process called RRO. Here, we're overwriting the config_maxUiWidth from 1096 (the full HD we're stuck with) from the FrameworkRes.apk to 0, disabling the limit and allowing wm size to go past 1096p.
Ayooo it's a match!! I also got the same value then!!
Thank you!!
EDIT: Just wanted to add this app here is excellent to interface the resolution and does work as good as ADB command, except at the press of a button!!
Pixels: Resolution+DPI Changer - Apps on Google Play
Smart custom display resolution & dpi changer (one-time ADB procedure required).
Attachments
Last edited:
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
6IMPORTANT: This no longer works after the update to Android 12. 'wm size' resets itself to default immediately after you change it. If you know (or at least have an idea) of a possible fix - please reply, so far I'm clueless.
I'll edit the post again if anything is found.
If you have already updated like me you can run 'wm density reset' so your phone looks normal again.
So the phone by default runs in 1096x2560 and only in select apps with appropriate content in 4k. XZ Premium did the same thing and it is possible to make always run in 4k. I've decided to try the same on 1 III and it works!
How to:
- Enable USB debugging in developer settings
- Download and run ADB, you phone should provide the driver automatically. If not, it can be downloaded from here.
- Run the following commands
Done! Exit ADB shell by typing exit there.Code:adb shell wm size 1644x3840 wm density 630
From my testing this works flawlessly with any app and the 120hz mode. My device didn't get too warm from this, battery now is at 35°C and CPU at 40. No lagging or freezes whatsoever either, everything runs smoothly in 120 fps. The only thing I noticed is that when using always-on display the phone unlock can be a bit slow sometimes, but only when unlocking with said display lit up.
How to undo - the same as before but with these commands:
Please report how's your experience and battery life if you try this.Code:adb shell wm size reset wm density reset3
Yes it does. Even the reboot screen is a little bit messed up because their animation is not 4k.22Chiming in my 2cents here. Also confirming it does not work on Android 12.
So far Android 12 is proving a real pain is the ass.
My advice - dont bother - stay on 11 until changes are made or workarounds are resolved
2
I hope they will fix this soon, and even add a built-in always 4k mode (fixing all the small bugs like the one you pointed out or the AoD not working properly).
The difference between 1080p and 4k is noticeable in everyday use, especially in text. Maybe this is because I was used to a 1440p display for the past 6 years (and going back to 1080p is noticeable) but still, this phone has all these pixels, why not have an option to always use them.
I attached some pictures taken in both modes. The filenames are self-explanatory but I am sure you will be able to find which one is 1080p and which one is 1644p. Diagonal lines especially suffer a lot at 1080p, like for example the letter 'w'. Overall, text looks very soft at 1080p compared to 1644p.
