Develop Bugs

[Q] Camera low fps in viewfinder

my friend has the Sony Xperia Z2 and the viewfinder (camera preview screen) is pretty smooth, it's like 60fps but when I look at mine Lg G3 with 3gb ram it looks 30fps. btw both phone where at the same light condition.

given that the camera is not the same, it could be a simple hardware difference. could be the camera app at fault. could be a difference in recording settings. could be anything, the info provided is less than helpful.

screwyluie said:
given that the camera is not the same, it could be a simple hardware difference. could be the camera app at fault. could be a difference in recording settings. could be anything, the info provided is less than helpful.
Click to expand...
Click to collapse
Considering this thread exists I think 30fps in the rom stock without mods.
http://forum.xda-developers.com/showthread.php?t=2778570
Try this out if you're rooted.

crash4fun said:
Considering this thread exists I think 30fps in the rom stock without mods.
http://forum.xda-developers.com/showthread.php?t=2778570
Try this out if you're rooted.
Click to expand...
Click to collapse
I think what he meant is when looking at the screen when the camera is open , the framerate when panning around is not smooth, not the actual video recording itself .

@screwyluie I think you are right. But I think that the could have the same hardware. But I hope somebody can mod it.
@crash4fun I have that mod but 60fps is only when recording and I meant 60fps in the live preview screen.
@joejoe23 Yes thank you that's what I meant

KingOfDope said:
@screwyluie I think you are right. But I think that the could have the same hardware. But I hope somebody can mod it.
@crash4fun I have that mod but 60fps is only when recording and I meant 60fps in the live preview screen.
@joejoe23 Yes thank you that's what I meant
Click to expand...
Click to collapse
Yup, its 6 to 30 fps in preview screen.
Check out /system/etc/camera_config.xml. Especially, keys "camera_preview_fps_range_rear" and 5 following keys. Modifying the second, "maximum" value doesn't have any effect even in bright lit environment. You may try modding the lower bound, however no one knows what effect this would have.

YaDr said:
Yup, its 6 to 30 fps in preview screen.
Check out /system/etc/camera_config.xml. Especially, keys "camera_preview_fps_range_rear" and 5 following keys. Modifying the second, "maximum" value doesn't have any effect even in bright lit environment. You may try modding the lower bound, however no one knows what effect this would have.
Click to expand...
Click to collapse
huhmm good find
I think it will affect the battery nothing more. I really want to test it now but I need my phone.
We need to contact @Hendrickson the guy who made this mod: "[MOD] Camera mod v2. Improve 4K 2160p birate, 1080p 60fps and camera compression" to test this

KingOfDope said:
huhmm good find
I think it will affect the battery nothing more. I really want to test it now but I need my phone.
We need to contact @Hendrickson the guy who made this mod: "[MOD] Camera mod v2. Improve 4K 2160p birate, 1080p 60fps and camera compression" to test this
Click to expand...
Click to collapse
Well, i once again changed maxfps to 60 in every condition, and there is some improvement in fps in bright light. It's not as smooth as it should be (constant 60 in viewfinder) but it is good enough. I guess we can try upping the lower bound to 30 or 60, this may help.

YaDr said:
Well, i once again changed maxfps to 60 in every condition, and there is some improvement in fps in bright light. It's not as smooth as it should be (constant 60 in viewfinder) but it is good enough. I guess we can try upping the lower bound to 30 or 60, this may help.
Click to expand...
Click to collapse
I'll try this on Friday. Did you get any force close yet? :highfive:
btw: How did you edit it? on your phone with a app? or through your pc and transferred the file back to your phone?

KingOfDope said:
I'll try this on Friday. Did you get any force close yet? :highfive:
btw: How did you edit it? on your phone with a app? or through your pc and transferred the file back to your phone?
Click to expand...
Click to collapse
no force closes yet. Will try to record 4k video with 50mb bitrate for all 5 mins, to see if phone will overheat/fail to record video because of heightened cpu/gpu load.
I edited it on-phone, using jota text editor.
15 mins later...
My 4k, 60 fps, 50 mbits video was recorded just fine
I think that once you are shooting video, fps of the preview screen is locked to video's fps, so that "test" may have been totally useless... Anyway, things are looking good. No force close, video/photos are doing just fine, and preview is somewhat snappier.

YaDr said:
no force closes yet. Will try to record 4k video with 50mb bitrate for all 5 mins, to see if phone will overheat/fail to record video because of heightened cpu/gpu load.
I edited it on-phone, using jota text editor.
15 mins later...
My 4k, 60 fps, 50 mbits video was recorded just fine
I think that once you are shooting video, fps of the preview screen is locked to video's fps, so that "test" may have been totally useless... Anyway, things are looking good. No force close, video/photos are doing just fine, and preview is somewhat snappier.
EDIT2: It seems that this change somehow affected encoder, since all my 4k videos are now shot at 60 fps, even though i've got framerate and LgeCamcorderCap set to 30. Would've been nice if it weren't so noizy...
Click to expand...
Click to collapse
OMG 4K 50MBITS 60FPS!?! DAMMMNN
I CAN'T WAIT TILL FRIDAY TO EDIT THE FILE O.O
Can you send the video? Here is my email [email protected] if you can't upload it here :highfive:

KingOfDope said:
OMG 4K 50MBITS 60FPS!?! DAMMMNN
I CAN'T WAIT TILL FRIDAY TO EDIT THE FILE O.O
Can you send the video? Here is my email [email protected] if you can't upload it here :highfive:
Click to expand...
Click to collapse
I'll record one sample video in "dark and noizy" conditions (it's 00h in Moscow, so it'll be quite easy), and one in "morning sun" condition's (8h later, after some sleep). Then i'll upload both here
Edit: I finally know why 4k suddenly became 60 fps... It's mx player bug, it shows incorrect values. It's still 50 mbits, though

@YaDrI peeked through the file and saw this:
"Camera_preview_fps_range_night_rear"
"Camera_preview_fps_range_night_front"
"Camera_preview_fps_range_ia_rear"
"Camera_preview_fps_range_full_frame_continuous_rear"
Did you tried to edit the one with "_night_" in them?
What does "ia" stand for?
and the last one, what does that?
I'm googling now hoping to find some answer
EDIT: I added a screenshot
{
"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"
}
EDIT 2: Ahh okey I thought something was not right, I mean common 4K 60fps
it's 22:30 here in The Netherland Take your time
EDIT 3: OMG I AM SO STUPID UPLOADED THE WRONG IMAGE LOL XD
EDIT 4: "Camera_preview_fps_range_ia_rear" "ia" stands for Intelligent Auto so must be the point-and-shoot mode

KingOfDope said:
@YaDrI peeked through the file and saw this:
"Camera_preview_fps_range_night_rear"
"Camera_preview_fps_range_night_front"
"Camera_preview_fps_range_ia_rear"
"Camera_preview_fps_range_full_frame_continuous_rear"
Did you tried to edit the one with "_night_" in them?
What does "ia" stand for?
and the last one, what does that?
I'm googling now hoping to find some answer
EDIT: I added a screenshot
***BIG SCREENSHOT***
EDIT 2: Ahh okey I thought something was not right, I mean common 4K 60fps
it's 22:30 here in The Netherland Take your time
EDIT 3: OMG I AM SO STUPID UPLOADED THE WRONG IMAGE LOL XD
Click to expand...
Click to collapse
I tried to edit higher bound of "Night" mode. No noticeable improvement, stll 6 fps. I think that changing the lower bracket is not a good idea, however i will try it later
About meaning of "ia" parameter... No clue, will have to dig into documentation later.
The last one must be for FOCUS_MODE_CONTINUOUS.
EDIT 1: Good, now we know what "ia" is

[need help] [Z00A] Change resolution to 720x1280 and still use the physical nav keys.

I have been flashing ROMS since it was cool to do so (no, not before).
But I am a complete n00b when it comes to dev stuff and this whole post is written at that point of view; this post MAY contain incorrent information and n00bish mistakes.
Why change to 720px1280?
Frame rate doubles when using games or other graphics intensive applications.
Increased batter life due to lower resolution.
Even more snappier!
Since it's a 5.5" screen, not much difference between 1080x1920 and 720x1280. Of course, it's a compromise but barely noticable.
(Don't actually do anything, just read!)
How to change the resolution?
Make sure you enable "USB Debugging"
Make sure you installed adb and fastboot in your computer.
Connect your phone to your computer (usb cable... etc).
In the terminal type : adb shell wm size 720x1280
Wait, everything is so big! We need to change the DPI.
The original DPI is 480, but at 720x1280, 350 seems to restore the previous size and feel. Feel free to experiment with the DPI
How to change the DPI?
Make sure you enable "USB Debugging"
Make sure you installed adb and fastboot in your computer.
Connect your phone to your computer (usb cable... etc).
In the terminal type : adb shell wm density 350
OK, now you notice the (Virtual) Navigation Keys at the bottom don't work anymore.
Well that is because the Virtual Keys Mapping is out of range.
To understand why, consider this question : How will the system know which button you are pressing?
System uses the "display coordinate system" to identify where the buttons are located on the screen.
This info in located in this file: /sys/board_properties/virtualkeys.ftxxxx_ts
virtualkeys.ftxxxx_ts:
Code:
0x01:158:215:2045:260:250
0x01:102:540:2045:260:250
0x01:139:865:2045:260:250
Syntax:
Code:
0x01: A version code. Must always be 0x01. (ok google)
<Linux key code>: The Linux key code of the virtual key.
<centerX>: The X pixel coordinate of the center of the virtual key.
<centerY>: The Y pixel coordinate of the center of the virtual key.
<width>: The width of the virtual key in pixels.
<height>: The height of the virtual key in pixels.
Linux key code says what the button is: return, home, recent...
The last four parameters (centerX, centerY, width_of_virtual_key, height_of_virtual_key) are our concern, because they say where the buttons are located on the screen using "display coordinate system".
In "virtualkeys.ftxxxx_ts", the location of buttons is defined for 1080x1920.
So when we changed the resolution to 720x1280, the mapping for the virtual buttons became out of range and thus unusable.
So what should those parameters be for 720x1280?
Code:
0x01:158:143:1363:173:166
0x01:102:360:1363:173:166
0x01:139:576:1363:173:166
Stop lying!
Well I don't know for sure.
Method 1:
The original resolution is 1080x1920 and we changed it to 720x1280.
a -> 1080x1920
b -> 720x1280
w -> width
h -> height
wb/wa = 1280/1920 = hb/ha = 1280/1920 = 0.666666667
Both the resolutions have same aspect ratio. So we need not bother about width and height seperately, because they are both changed at the same proportion.
So, multiply the last four parameter values (centerX, centerY, width_of_virtual_key, height_of_virtual_key) by 0.666666667 and you should get the location of the buttons when resolution is changed to to 720p.
Method 2:
Enable "Show pointer location" in "Developer Settings".
The co-ordinates of where you touched the screen are displayed at the top.
Change the resolution to 720x1280.
The Navigation Buttons don't work but drag your fingers onto them.
You will see X and Y are near to the values we calculated in METHOD 1.
So lets modify the file already! (/sys/board_properties/virtualkeys.ftxxxx_ts)
Well you see, the file (virtualkeys.ftxxxx_ts) is located in the directory "/sys".
It turns out, it is not an actually directory. It is a "view" of the KERNEL as a filesystem.
So, every time the system boots, the kernel creates (magics?) those files in "/sys" which the system uses.
We do not have permission to change that directory's contents, not even with a slip from our parents.
Unless we have a way of overriding the kernel created file (virtualkeys.ftxxxx_ts), we have to patch the kernel itself.
I don't know how to patch kernels and stuff, this escalated quickly for me. So if you are interested check it out!
Please check the validity of anything said in this post. Positive criticism is welcome!
Sources : https://source.android.com/devices/input/touch-devices.html#virtual-key-map-files, @aziz07 (started all this after reading their posts in : http://forum.xda-developers.com/zenfone2/general/downgrade-resolution-ze551ml-t3163797)

This is the file on ze550ml. Your results appears to correct.
{
"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"
}

Im using second monitor from play store to change resolution and density on the fly.
Sky on demand not work if detect 1080 device. So i change to 720p to connect tv.
Facing with virtual Keys not working, hwvr i use iswipe to manage it.
Solution can be virtual nav bar, exposed mondule, anyway resulution is not 1080 or 720 but is scaled so open zenui.apk to see how it work, what now? You need mod zenui or just flash custom rom, 'cuz will afect call screan, setting screen, app drawer and so on.
Some aps will not work changing density and zenui sometime crash, so need reboot.
Forget to say that: changing resolution will impact batery life in whorste way (you will run ever biggest res then the normal use). Only wallpaper, immersive mode (photo and video) and of course user apps are the only run in full resolution, set black screen wallpaper and use appsetting module to change per app resolution if you tink will save batery life.

Ah, the much easier method. Thank you for posting.

I think, 540x960 will be better for lowres because it will use whole 2x2 pixels and won't create blur.
I've just got idea to mix such tweak with second user. So, when you switch the user, resolution will be switched as well.

UP, it work with Cyanogenmod 13, much better battery life, but we need kernel patch for modify virtualkeys.ftxxxx_ts

tikilou said:
UP, it work with Cyanogenmod 13, much better battery life, but we need kernel patch for modify virtualkeys.ftxxxx_ts
Click to expand...
Click to collapse
why?

@blazzer12 I would like to correct something :
the correct parameters for 720x1280 are
0x01:158:140:1341:180:100
0x01:102:360:1341:170:100
0x01:139:580:1341:180:100
these values are the one metioned in our kernel source.

blazzer12 said:
Well you see, the file (virtualkeys.ftxxxx_ts) is located in the directory "/sys".
It turns out, it is not an actually directory. It is a "view" of the KERNEL as a filesystem.
So, every time the system boots, the kernel creates (magics?) those files in "/sys" which the system uses.
We do not have permission to change that directory's contents, not even with a slip from our parents.
Unless we have a way of overriding the kernel created file (virtualkeys.ftxxxx_ts), we have to patch the kernel itself.
Click to expand...
Click to collapse
Better you can try a ROM from Z008/720p Model. Because I've flashed a full ROM of Z008 to my Z00A for recovering it from HardBrick (In that case I had only 720p model RAW Firmware file). That ROM was working very fine but the icons was smaller due to DPI of the ROM. My Idea is, if I flash 720p ROM and change resolution to 720p using your methid, everything will be normal. right? (Or, you can use a kernel alone from Z008 instead of searching for a kernel patch).... Am I right?

say99 said:
@blazzer12 I would like to correct something :
the correct parameters for 720x1280 are
0x01:158:140:1341:180:100
0x01:102:360:1341:170:100
0x01:139:580:1341:180:100
these values are the one metioned in our kernel source.
Click to expand...
Click to collapse
would be nice if you can add this patch in your kernel

xCalibur15 said:
would be nice if you can add this patch in your kernel
Click to expand...
Click to collapse
ok, I did this today in the morning, but I must tell you this method didn't work
https://github.com/Zenfone2-Dev/kernel-FlareM/commit/ba444d0616457c283cd257a363d427c915efbf7b
I was able to change the content of the file, but as soon as that happened, I was only able to access 3/4th of my screen, touch didn't work. I must also tell you guys that, even though we change the DPI to 720P, sweep2sleep still works that just means that the location of the hardware keys is still the same. I am trying to figure out the correct coordinate that we should use. Cause according to our boot animation, we get a increase of about 1.45x in X coordinate.
help me with the codes if you want to
Sent from my ASUS_Z00A using Tapatalk

i calculated the values for 540x960px (easier to calculate):
0x01:158:107:1023:130:125
0x01:102:270:1023:130:125
0x01:139:433:1023:130:125
dpi 240
if i got it right, I can make the values for 720p also

i found this very cool, and wish to change the button positions... but sorry i dont get it, there is a way to do it?

Asus Zenfone 2 Laser ZE500KL
Asus Zenfone 2 Laser ZE500KL
Resolution 720 x 1280 pixels (~294 ppi pixel density)
android marsmallow
0x01:158:140:1328:160:80
0x01:102:360:1328:180:80
0x01:139:580:1328:160:80
---------- Post added at 07:02 AM ---------- Previous post was at 06:51 AM ----------
Asus Zenfone 2 ZE551ML
1080 x 1920 pixels (480 ppi pixel density)
android marsmallow
0x01:158:140:1328:160:80
0x01:102:360:1328:180:80
0x01:139:580:1328:160:80

https://goo.gl/UKaif3 here's how to change resolution with root

say99 said:
ok, I did this today in the morning, but I must tell you this method didn't work
Click to expand...
Click to collapse
And if you include the next code but with correct touch screen coordinates for 720p?
https://github.com/BORETS24/Kernel-...0c/drivers/input/touchscreen/ftxxxx_ts.c#L926
https://github.com/BORETS24/Kernel-...0c/drivers/input/touchscreen/ftxxxx_ts.c#L986

[Trick] Enable .DNG Format for Pictures in any unsupported Lumia.

First Follow This Link to Interop Unlock UR phone and also Install Interop tools from here. Click Here!
Open Interop tools>This Device>Registry Browser
Now goto this path HKLM\SOFTWARE\OEM\Nokia\Camera\Barc
and
set "DNGDisabled"=0. [Default Valuse is 1]
this is an easy thing.the key is already shared in XDA by @Lanex777 . Here Is the comment Link
But Device like 730 doesn't has the subkey "Barc".so u have to create it.creating only one key will not give U DNG support..there are 2 more keys to add..
U can use Interop tools >registry editor for creating these keys.
In registry editor
choose
"Registry Hive"="HKEY_LOCAL_MACHINE (HKLM)"
"Regsitry Type"="Integar(REG_DWORD)"
"Registry Key PATH"="HKLM\SOFTWARE\OEM\Nokia\Camera\Barc"
"Registry Value Name"="DNGDisabled"
"Registry Value Data"="0"
Click "Write"
-------
"Registry Hive"="HKEY_LOCAL_MACHINE (HKLM)"
"Regsitry Type"="Integar(REG_DWORD)"
"Registry Key PATH"="HKLM\SOFTWARE\OEM\Nokia\Camera\Barc"
"Registry Value Name"="IsEnabled"
"Registry Value Data"="1"
Click "Write"
------
"Registry Hive"="HKEY_LOCAL_MACHINE (HKLM)"
"Regsitry Type"="String(REG_SZ)"
"Registry Key PATH"="HKLM\SOFTWARE\OEM\Nokia\Camera\Barc"
"Registry Value Name"="BarcVersion"
"Registry Value Data"="0.81"
Click "Write"
---------
thats it .now u can enjoy DNG in ur Phone...feel free to inform me if u think the thread is dupicated .

The thread no, but the trick, a thousand times:
http://forum.xda-developers.com/showpost.php?p=61376335&postcount=284
http://forum.xda-developers.com/showpost.php?p=61749223&postcount=43

augustinionut said:
The thread no, but the trick, a thousand times:
http://forum.xda-developers.com/showpost.php?p=61376335&postcount=284
http://forum.xda-developers.com/showpost.php?p=61749223&postcount=43
Click to expand...
Click to collapse
i already mentioned that the key already shared by Lanex777.but the key is only for phones which has the "Barc" subkey..but my thread has extra 2 keys for unsupported device which is not shared untill now on xda.so i think i did not break any rules.

Ok, my fault. I need to stop my ego....better with a glass of vine.

Will this work on non-Lumina phones like those from Alcatel?

Baenwort said:
Will this work on non-Lumina phones like those from Alcatel?
Click to expand...
Click to collapse
Maybe..u can give it a try..i m not sure though because i don't have any other brand wp.

I tried this hack some time ago and it worked. But after I hard reset my Lumia 920 and applied this hack, the JPEG+DNG option shows up but it doesn't produce any DNG file, only the JPEG. Does anyone know why? I'm on 14393.693 by the way

augustinionut said:
The thread no, but the trick, a thousand times:
http://forum.xda-developers.com/showpost.php?p=61376335&postcount=284
http://forum.xda-developers.com/showpost.php?p=61749223&postcount=43
Click to expand...
Click to collapse
You are wrong... those linked links with just DNGDisabled -> 0 not all devices enable the DNG, you need the three tweaks OP is mentioning to fully enabled DNG on any device.

The trick is widely knowned
Only need for exactly unsupported devices like 630, 530, . . .
On 640, 730, . . . It ' s only be hided by MIC not as 830, . . .

Is there a way to enable the living images toggle for the camera app on unsupported models?

nate0 said:
Is there a way to enable the living images toggle for the camera app on unsupported models?
Click to expand...
Click to collapse
You mean this? Living Images

xxJMarian said:
You mean this? Living Images
Click to expand...
Click to collapse
Does that allow my Microsoft camera app to save shots as living images?
I saw that app earlier today but have not tried it.

nate0 said:
Does that allow my Microsoft camera app to save shots as living images?
I saw that app earlier today but have not tried it.
Click to expand...
Click to collapse
I want to know what you mean by living images, you mean the Lumia Camera 5 options?? Like face swap, action shot, etc?

xxJMarian said:
I want to know what you mean by living images, you mean the Lumia Camera 5 options?? Like face swap, action shot, etc?
Click to expand...
Click to collapse
Correct. Can we add the option to the camera app or does it need other supplemental services?
I just figured it out. I got it enabled on my Alcatel idol 4s just now....one moment I'll. Post how. I added the barc key and three values and it enabled it and it worked.

nate0 said:
Correct. Can we add the option to the camera app or does it need other supplemental services?
Like here in the attached.
{
"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"
}
---------- Post added at 01:44 AM ---------- Previous post was at 01:40 AM ----------
I just figured it out. I got it enabled on my Alcatel idol 4s just now....one moment I'll. Post how. I added the barc key and three values and it enabled it and it worked.
Click to expand...
Click to collapse
Oh... You want the HDR feature, the answer is no. HDR works with LED flash, takes a normal photo and plays with exposure levels, you can modify the amount of flash in the photo and so on. You can achieve that with 3rd party, maybe 4blend or some app that generates photos to - EV and + EV and lets you combine them into one. What you can have in unsupported lumias is somekind of HDR where the img gets better quality but thats all.
This is only for devices with LED flash

After adding the below keys and values I enabled the Capture Living Images option in my default camera for the Idol 4s
[SOFTWARE\OEM\Nokia\Camera]
Name: Barc
Added these values:
BarcVersion String=101.1
DNGDisabled Dword=0
IsEnabled Dword=1
Not sure why the prior pic upload was scrambled, but I attached it being enabled on my Idol 4s. The last pic was a lumia 650.

nate0 said:
After adding the below keys and values I enabled the Capture Living Images option in my default camera for the Idol 4s
[SOFTWARE\OEM\Nokia\Camera]
Name: Barc
Added these values:
BarcVersion String=101.1
DNGDisabled Dword=0
IsEnabled Dword=1
Click to expand...
Click to collapse
Yeah i just saw what you were talking about, my bad

This is great. I'm glad I go this enabled. The idol 4s is a slick phone but ever so plain under the hood.

nate0 said:
Is there a way to enable the living images toggle for the camera app on unsupported models?
Click to expand...
Click to collapse
Which models, 630,520,620,etc or 730,640,etc?

lequangtan said:
Which models, 630,520,620,etc or 730,640,etc?
Click to expand...
Click to collapse
It's a non-Lumia device. Idol 4s. I actually have it working. So I'm good.

Windows Mobile Continuum Scaling on External Screen

Continuum is the unique feature for windows phone. continuum will scale perfectly ,when it connected to Monitors with full HD resolution.
But when you use it for TV , scaling problems will occur. Those who don't have PCs, Continuum will be become wonderful mini PC Experience.
few people ,may know these Registry values when 950/xl devices first inter-op unlocked for continuum scaling.lately made a post for others.
If your device is inter-op unlocked,you can change these registry values for perfect scaling and smooth experience.
below procedure is "wired continuum " with 950 xl with LCD Full HD local tv
wireless continuum not tested due to lack of Miracast Device,it's also same with another Config id ,if you connect only connect with Miracast ,2nd config id which lengthy, is continuum config id ,next time when you connected.,In wired connection check another lengthy config id (3rd one)came or not.
Intial Setup :-
If your Device is unsupported and had Miracast feature Deploy continuum Cabs using the " Continuum for unsupported devices"
First open Continuum app and complete setup ,you will see continuum on big screen which is stretched
go to external settings==> display , grab display slider to top left as seen below and restart.
{
"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"
}
When Continuum establishes Connection. Configuration ID is Created under below path.
HKEY_LOCAL_MACHINE/System/ControlSet001/Control/GraphicsDrivers/Configuration/2nd one(Your Continuum config ID)
when you connect through one setup it may be wired or wireless there will be one Config ID will be generated
For my 950 XL wired connection
SYSTEM\ControlSet001\Control\GraphicsDrivers\Configuration\CMO00110_09_07D9_98+___900015_01_07D8_99^485D46A2EC43A2B39ACB2592A9ED698A\01\00
for example if you connect through wireless setup ,one config ID generated remeber that like it is for scaling for wireless display scaling or name it in category with id for wptweaks
then you again connect with wired setup another Config ID is generated remeber it for scaling for wired display scaling.
Remember id for which it is belongs to like wired or Wireless
if you connect through both wired and wireless setups and you see only one config ID ,look for two "DwmClipBpx.xxxx" registry values in two places.
For any Config ID modification is same at all registry values
when you go into Config ID then
go to 01 then 00
Below 4 values are Responsible for scaling. See above picture
Enter all values through Interop-unlock App,values are in hexagonal
1) DwmClipBpx.bottom
2) DwmClipBpx.left
3) DwmClipBpx.right
4) DwmClipBpx.top
Here.Bottom and right values are resolution of this external display.
Left and top values are Side scaling.
open interop unlock app in Continuum Mode or use wptweaks by importing xml file.
TVs may not have the exact resolution of 1920x1080
it will be something like 1895x1060 as my local tv
first change the values according to your tv
DwmClipBpx.bottom =1062
DwmClipBpx.right =1895
these bottom,right may inter change Device to device and continuum app(950 vs hp).
still some gaps will be there,then
change other two values . Disconnect the cable and reconnecting to check it perfectly working or not. if is wireless Disconnect and connect.
Changes will appear instantly & Change accordingly
next to change are the 2 values with near values like
DwmClipBpx.left =42
DwmClipBpx.top =25
that's all.
if u feel to do some experiment change these values too.
if there some screen flickering due to sync frequency, where are horizontal or vertical sync values, you can change below 4 values..See above picture
1) HSyncFreq.Numerator
2) HSyncFreq.Denominator
3). VSyncFreq.Numerator
4) VSyncFreq. Denominator
i tried increase below 2 numerator values increase for some better experience .denominators no need to change
HSyncFreq.Numerator default 67500000 = 77777777
VSyncFreq.Numerator. default 60000 = 99900
Tweaking denominator values shakes the screen in my 950,try yours if want to do so.
For Wptweaks :-
First Download continuum-Scaling_tweaks-2
change your Config ID of your Device and properly Name it at "<tweak category=" According to its type Like below for all 6 tweaks (For Example Wired)
for second Connection(ex wireless config) check whether other ID came or not replace id at path and change "<tweak category=" accordingly
check values need to enter in hexagonal,change accordingly using calculator app programming mode
use notepad next to add in main tweaks.xml
add these continuum-tweaks in complete tweaks.xml -:
If anyone tried on 4K TV suggest values in Reply
you can experience better performance by adjusting display for different external screens
its working perfectly with my tv & watching 4K youtube video on continuum
reply your experiences ..
check the attachments

I have tried on 640xl with a wireless miracast stick (1920x1080) pluged into a fullHD monitor (1920x1080), but it doesn't work.
There is no ..../01/01 just ..../01/00
Have changed DwmClipBpx.bottom =768 ->1080
DwmClipBpx.right = 1280 ->1920
Also tried on both last Config ID's and restart phone
Maybe that only works on 950/XL OR only works with a wired DOCK

long_pn said:
I have tried on 640xl with a wireless miracast stick (1920x1080) pluged into a fullHD monitor (1920x1080), but it doesn't work.
There is no ..../01/01 just ..../01/00
Have changed DwmClipBpx.bottom =768 ->1080
DwmClipBpx.right = 1280 ->1920
Also tried on both last Config ID's and restart phone
Maybe that only works on 950/XL OR only works with a wired DOCK
Click to expand...
Click to collapse
The OP is updated ,read it thoroughly,follow the step by step, download latest Wp tweaks xml in OP:good:

Ok, I realize that my issue is not Scaling but Resolution. It means continuum still fills the fullHD screen but resolution is much lower than 1366x768

long_pn said:
Ok, I realize that my issue is not Scaling but Resolution. It means continuum still fills the fullHD screen but resolution is much lower than 1366x768
Click to expand...
Click to collapse
It's also for resolution change, buy in wireless, processor should support, you need to tweak some Power supply registry values too

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.