Related
Modifying the LCD density of your screen will provide HUGE REACTIVITY GAIN to the tablet
We can also tweak Dalvik heapsize for large application
Both are editable using software but they're also properties on the build.prop :
- dalvik.vm.heapsize
- ro.sf.lcd_density
Does editing this properties is enough for the Folio follow or do we have to make much complex operations ?
I there, is this fix already implemented or has to be done manually?!?
I've implemented them using FolioWidget rewriting build.prop.
Not sure the folio take care of it.
But it seems that's is not required by users so i'll wipe them
Sol Ido said:
I've implemented them using FolioWidget rewriting build.prop.
Not sure the folio take care of it.
But it seems that's is not required by users so i'll wipe them
Click to expand...
Click to collapse
I dont understand what u mean.
ps: have u read my pm?
Sol Ido said:
I've implemented them using FolioWidget rewriting build.prop.
Click to expand...
Click to collapse
density of 120 works quite fine here now.. with old market app, there was a problem with 120 but that seems resolved now with new market app..
and yes, somehow screen and browsing seems to work better? or is it just the bigger picture giving a nicer resolution of browsing?
All resolution are good. If you have a lot of items on the screen lower density is best.
But by using something like 180 you get a lot of visibility. Since i've developped a lot of complex widgets, it's my favorite one.
Using a density >120 will get you less data to manage on the screen and you can feel the gain ! i'm using multipicture and a lot of complexes widgets and there's not fillrate lag at all.
I was quite surprised with this benefits.
My purpose is that those options can really feet somes users needs. VM heap tricks like the one you found on cyanogen helps on huge application like PDF readers.
But even after editing those properties on the build.prop they are not taken into account. Maybe because of the previous installation i've done. So i'm looking to better understand how to override android properties.
I'm not sure how android handles non-default values for this property.
You should try with one of these:
120 (low-density)
160 (medium-density, Folio default)
240 (high density)
Depending on how this is handled, setting a density different than that may result in broken applications (depending on how the layouts are coded)
Using the LCD DEnsity application i confirm that all resolution are compatible with the folio
Maybe some application will have a bad behavior ! so we've to be able to change the density
metuskale said:
I there, is this fix already implemented or has to be done manually?!?
Click to expand...
Click to collapse
This is no fix, as there are no real issues with these things. Its only a matter of tweaking the folio to your best personal use. They have to be implemented manually.
Shouldn't the dalvik heapsize fix the sound problem with some avi files?
I'm using the foliomod 1.3d, foliowidget works, but some avi files arn't giving me sound
Hello, could someone tell me how the default value for the heapzize is, please? There is only 16, 24 and 32 to choose, but I read something about 64!? How can I choose this value or get back to default?
Thx
Tom
Edit: solved!
Hello Tablet Z community,
This is my first post in this devices forums since getting mine last week. It's a great device, love it, etc.
I've never owned an Android device with a screen resolution this high so I've yet to encounter this problem - some of my games (specifically the emulator PPSSPP) have relatively low framerates (compared to my less powerful Samsung P6810 @ 800x1280). I know with computers in particular it's trivially easy to change resolutions in games/the OS, especially to increase FPS but I've never seen a method to do this on Android and Google searches turn up people mentioning device resolution without changing them.
Does anyone know if it's possible to, ideally, force a different resolution for a particular application? A less than ideal solution would be a system wide change but I would be willing to endure temporarily to increase FPS.
Any advice and suggestions would be greatly appreciated
I would be interested to know about this, iv just loaded ppsspp however havent been able to play any of the playable games listed, I did see a few videos of the xperia z playing well, however that has the same resolution and specs.
juzza87 said:
Does anyone know if it's possible to, ideally, force a different resolution for a particular application? A less than ideal solution would be a system wide change
Any advice and suggestions would be greatly appreciated
Click to expand...
Click to collapse
That was recently discussed in this thread: LCD Density Changes and Results (With Pics)
Cat McGowan said:
That was recently discussed in this thread: LCD Density Changes and Results (With Pics)
Click to expand...
Click to collapse
This is very different, setting the DPI to a non-stock value just resizes the userspace, the resolution is fixed and unchangeable as the OP is thinking. Compared to a Windows PC where you can change the resolution, in Android you only have the ability to change the dpi, which states how large the pixel-to-screen size is. A smaller number indicates a smaller pixel-to-screen size, meaning the information shown on screen is sized for a laeger screen (making it smaller, since the screen is a fixed size). And a larger number has the reverse effect. Android UI guidelines set the optimal dpi for resolution vs. screen size, to mainain a similar experience across devices (similarly sized icons and fonts, etc). Again, this has nothing to do with adjusting the physical resolution of the device, which (to my knowledge) is not possible in Android.
daveid said:
This is very different, setting the DPI to a non-stock value just resizes the userspace, the resolution is fixed and unchangeable as the OP is thinking. Compared to a Windows PC where you can change the resolution, in Android you only have the ability to change the dpi, which states how large the pixel-to-screen size is. A smaller number indicates a smaller pixel-to-screen size, meaning the information shown on screen is sized for a laeger screen (making it smaller, since the screen is a fixed size). And a larger number has the reverse effect. Android UI guidelines set the optimal dpi for resolution vs. screen size, to mainain a similar experience across devices (similarly sized icons and fonts, etc). Again, this has nothing to do with adjusting the physical resolution of the device, which (to my knowledge) is not possible in Android.
Click to expand...
Click to collapse
Heh. Thanks for the schooling, but it was unnecessary, I didn't just fall off a turnip truck.
Thanks for the replies guys, at least now I know for sure..
STEP 1 : install resolution changer pro on any h2os rom from play store (kinmaricans i preffer).
STEP 2 : First do not enable it just put height = 1440 and width = 2560 and then density to 538.
STEP 3 : ENABLE IT. ENJOY
Can't it be in oxygen or any other cm based custom rom
You can't change your phone's screen resolution ahahaha that depends on the hardware. That app is just changing your DPI to change the size of UI elements.
If you could change your phone screen resolution with a simple app, why would any OEM make phones with 4k screens?
The OP2 was, is, and will always remain 1920x1080. You can always change the DPI to get smaller icons or whatever (I prefer 380, stock is 480). More the DPI, bigger your UI elements.
jash2909 said:
STEP 1 : install resolution changer pro on any h2os rom from play store (kinmaricans i preffer).
STEP 2 : First do not enable it just put height = 1440 and width = 2560 and then density to 538.
STEP 3 : ENABLE IT. ENJOY
Click to expand...
Click to collapse
That is just absolute nonsense, sorry to say that. You just make the device believe to have a 2k display, which means the GPU will have to push even more "virtual" pixels, while everything is just "downscaled". You won't get any benefits from that, in contrary you will just introduce more cluster****, by letting it run on a virtual resolution instead of it's native.
There's a reason why people with 2K phones set the virtual resolution down to 1080p, so that the GPU doesn't have to work as hard.
How this differ from changing dpi, it comes to my mind that oos doesn't like changing dp
Sent from my ONE A2005 using Tapatalk
OP, you may want to alter your thread title in the advanced edit menu to something more accurate. You will see what I mean if you read the comments here.
And members, it's fine to try to educate someone or correct them, but do it respectfully. Or don't post otherwise.
Thanks,
Darth
Forum Moderator
@duraaraa any info or direction that you can provide on this?
I upped the resolution from stock 1080x2160 to 2160x4320 and left dpi at stock so I can have more screen real estate and still have a comfortable viewing experience. The issue I'm facing now is, I cannot capture a screenshot I get an error.
System UI
Couldn't Capture Screenshot
Screenshots are not allowed by this app or your organization.
steps to reproduce:
up your resolution to 2160x4320 and take a screenshot
Any guidance would be appreciated.
webleeper said:
@duraaraa any info or direction that you can provide on this?
I upped the resolution from stock 1080x2160 to 2160x4320 and left dpi at stock so I can have more screen real estate and still have a comfortable viewing experience. The issue I'm facing now is, I cannot capture a screenshot I get an error.
System UI
Couldn't Capture Screenshot
Screenshots are not allowed by this app or your organization.
steps to reproduce:
up your resolution to 2160x4320 and take a screenshot
Any guidance would be appreciated.
Click to expand...
Click to collapse
Sorry, don't know. Probably issue related to rooting and the settings you changed.
Thanks for the quick reply but I'm not rooted.
webleeper said:
@duraaraa any info or direction that you can provide on this?
I upped the resolution from stock 1080x2160 to 2160x4320 and left dpi at stock so I can have more screen real estate and still have a comfortable viewing experience. The issue I'm facing now is, I cannot capture a screenshot I get an error.
System UI
Couldn't Capture Screenshot
Screenshots are not allowed by this app or your organization.
steps to reproduce:
up your resolution to 2160x4320 and take a screenshot
Any guidance would be appreciated.
Click to expand...
Click to collapse
Mate 10 pro panel is only 1080p to begin with,
In what way did you upped the resolution ?? The setting wont give you that resolution option.
otonieru said:
Mate 10 pro panel is only 1080p to begin with,
In what way did you upped the resolution ?? The setting wont give you that resolution option.
Click to expand...
Click to collapse
no need for root or settings to change DPI or Resolution
adb shell wm size 2160x4320
adb shell wm overscan reset
webleeper said:
no need for root or settings to change DPI or Resolution
adb shell wm size 2160x4320
adb shell wm overscan reset
Click to expand...
Click to collapse
uh... well... you already understand that this method is "only faking" the number for the app to think that it run on that size of screen right ? Hardware & stock OS wise, the limitation is still on 1080p
I dont think the system UI app of EMUI 8 itself was made to handle that number
Normal 4K itself is only 3840 x 2160, and i dont think i ever found any phone running 4K+ (18:9)
This is just like asking why sometimes the play store act weird when we change our DPI
So answer is that : because it simply didn't support it
I've done #wm size 720x1280 & wm density 320 to 720p screen for long battery life. and I found the system's screenshot can not take whole screen(720p one).
It looks like the screenshot component take a 480p screen and the same 720p adjusting on AEX 5.x is fine.
so I thought maybe the screenshot on pie still mistake 720p screen for 1080p screen and take a 480p picture（expect: 1080p x 720/1080 = 720p, but now: 1080p x 720/1080 x 720x1080 = 480p）
But I notice that keep wm size 1080x1920, whatever which density（320 480 240）I've set, the screenshot could take a complete screen picture. while I change density, whatever resolution (720x1280, 480x800, 1080x1920), screenshot just take the top left part of screen...
partial screenshot is same condition , take a top left part of what I selected .
the screenshot on different resolution is the last issue I can found on AEX 6.0, which not contain on AEX5.x（maybe this is pie issue but still expect you can fix it） if I don't need change the resolution, the ROM is PERFECT?
can you fix this ?? thxxxxx a lot
XDrz said:
I've done #wm size 720x1280 & wm density 320 to 720p screen for long battery life. and I found the system's screenshot can not take whole screen(720p one).
It looks like the screenshot component take a 480p screen and the same 720p adjusting on AEX 5.x is fine.
so I thought maybe the screenshot on pie still mistake 720p screen for 1080p screen and take a 480p picture（expect: 1080p x 720/1080 = 720p, but now: 1080p x 720/1080 x 720x1080 = 480p）
But I notice that keep wm size 1080x1920, whatever which density（320 480 240）I've set, the screenshot could take a complete screen picture. while I change density, whatever resolution (720x1280, 480x800, 1080x1920), screenshot just take the top left part of screen...
partial screenshot is same condition , take a top left part of what I selected .
the screenshot on different resolution is the last issue I can found on AEX 6.0, which not contain on AEX5.x（maybe this is pie issue but still expect you can fix it） if I don't need change the resolution, the ROM is PERFECT
can you fix this ?? thxxxxx a lot
Click to expand...
Click to collapse
Who is gonna fix what? Just use the phone the way its supposed to be used i dont understand what you are doing and why. If anyone, huawei can fix your issue i guess.... good luck talking to them.
You should read this, particularly the long answer near the top which explains the size vs density changes.
https://stackoverflow.com/questions...to-use-adb-shell-wm-to-simulate-other-devices
I think this is actually a bug in android pie. My phone has a 4k display, but normally uses HD res unless in gallery app. So I changed wm size and density to match the display (and despite what some other say, this actually changes the visible resolution, IF your display has this many physical pixels).
Screenshots worked worked fine in oreo, but after updating to pie, there are black borders on the picture.
Display
Spodi2290 said:
I think this is actually a bug in android pie. My phone has a 4k display, but normally uses HD res unless in gallery app. So I changed wm size and density to match the display (and despite what some other say, this actually changes the visible resolution, IF your display has this many physical pixels).
Screenshots worked worked fine in oreo, but after updating to pie, there are black borders on the picture.
Click to expand...
Click to collapse
No Huawei phone has a 4k display, this whole thread is a waste of space really, guy setting his phone display to something that is not supported and wondering why his screenshot won't work, damn mate 10 pro is 2160x1080 and can't be any more than that, if the problem was the screenshots not working in a supported mode there might be a reasonable and were but as it stands this thread should be closed and deleted
revjamescarver said:
No Huawei phone has a 4k display, this whole thread is a waste of space really, guy setting his phone display to something that is not supported and wondering why his screenshot won't work, damn mate 10 pro is 2160x1080 and can't be any more than that, if the problem was the screenshots not working in a supported mode there might be a reasonable and were but as it stands this thread should be closed and deleted
Click to expand...
Click to collapse
The whole point of my post was more like: its not a Huawei only "bug", but effects all (or at least most) pi phones with a custom wm size set. Maybe I was beating around the bush too much... :angel:
Spodi2290 said:
The whole point of my post was more like: its not a Huawei only "bug", but effects all (or at least most) pi phones with a custom wm size set. Maybe I was beating around the bush too much... :angel:
Click to expand...
Click to collapse
Hi, have you found any solution for the screenshots when you change the screen resolution? You're right it happens only in pie and with different phones, in oreo the multitasking previews resize when you enter to the app but the screenshots are ok, in oreo the previews in multitask are ok but the screenshot miss a part of the screen.
With A11, we were able to get the display to always render in native 4K with the adb wm trick.
Code:
wm size 1644x3840
wm density 630
would return
Code:
Physical size: 1096x2560
Override size: 1644x3840
and have the display render in native 4K across the entire OS.
With A12, the trick seems to do nothing now, setting the size back to 1096x2560 and returning no override size value. We're locked out of that beautiful 4K outside of a select few whitelisted apps (like Google Photos). Even the homescreen isn't rendered in 4K! What's the point, then?
I rooted and tried to do some deeper digging around of my own: perhaps there's a whitelist xml? A setting in build.prop? Something? Anything? And much to my disappointment, I could not find anything of substance (of course, not being a developer myself and knowing jack **** is also another major factor...)
So, anyone wanna take a dive in with me and help unlock this beautiful display's potential in A12 once and for all?
Bro get rid of Stock ROM asap. I have always on 4K on Evo X 12.1 ROM
BlazingKahn35 said:
Bro get rid of Stock ROM asap. I have always on 4K on Evo X 12.1 ROM
Click to expand...
Click to collapse
Where to find that rom ?
Pandemic said:
Where to find that rom ?
Click to expand...
Click to collapse
21.3 GB folder on MEGA
17 files and 16 subfolders
mega.nz
BlazingKahn35 said:
21.3 GB folder on MEGA
17 files and 16 subfolders
mega.nz
Click to expand...
Click to collapse
Oke and what is the changelog of evo x 12.1 and bowto install abd maybe you can open a new thread with that rom ?
Pandemic said:
Oke and what is the changelog of evo x 12.1 and bowto install abd maybe you can open a new thread with that rom ?
Click to expand...
Click to collapse
It has automated BAT installer inside no changelog I do not own the ROM
BlazingKahn35 said:
It has automated BAT installer inside no changelog I do not own the ROM
Click to expand...
Click to collapse
Aaah oke thanks m8
BlazingKahn35 said:
It has automated BAT installer inside no changelog I do not own the ROM
Click to expand...
Click to collapse
You have to be on latest A11
Pandemic said:
Aaah oke thanks m8
Click to expand...
Click to collapse
Ik had het via Telegram ook gestuurd trouwens en als je vragen hebt beste via telegram anders.
BlazingKahn35 said:
You have to be on latest A11
Click to expand...
Click to collapse
[ROM][11][UNOFFICIAL] Evolution X 5.9.4 for Xperia 1 III
Evolution X 5.9.4 for Xperia 1 III [pdx215] /* * Your warranty is void. Or vaild, probably? * * I am not responsible for bricked devices, dead SD cards, Ebolation X, * thermonuclear war, or the current economic crisis caused by you following *...
forum.xda-developers.com
largo2 said:
[ROM][11][UNOFFICIAL] Evolution X 5.9.4 for Xperia 1 III
Evolution X 5.9.4 for Xperia 1 III [pdx215] /* * Your warranty is void. Or vaild, probably? * * I am not responsible for bricked devices, dead SD cards, Ebolation X, * thermonuclear war, or the current economic crisis caused by you following *...
forum.xda-developers.com
Click to expand...
Click to collapse
That's the 11 version.
BlazingKahn35 said:
That's the 11 version.
Click to expand...
Click to collapse
Yes
Hello,
I still don't understand anything about this. The screen is 4k, meaning all content is upscalled to 4k (without upscaling, you would have the image taking 1/4 of the screen with big black border all around). Now about app's, if the graphic rendering just create FHD number of pixel, how changing ROM/phone setting would do anything about that, except upscaling it, exactly the same way it does natively?
Hildr said:
Hello,
I still don't understand anything about this. The screen is 4k, meaning all content is upscalled to 4k (without upscaling, you would have the image taking 1/4 of the screen with big black border all around). Now about app's, if the graphic rendering just create FHD number of pixel, how changing ROM/phone setting would do anything about that, except upscaling it, exactly the same way it does natively?
Click to expand...
Click to collapse
I think it's the same of Kodi or other app interface on 4K tv. Some of those up render UI (and some app every content) in 1080P and then the TV/display make the upscale. Optimized app will create a 4k image/video natively (with more load on CPU/GPU but better quality)
Always 4k mode will force pretty much every app to render the image in 4K.
This is the same of the issue ps5 have on 1440P display. usually 1080P image upscaled /adapted from the display to 4k lead to a lower quality image, where 4k rendered image downscaled to 1440P offer a better quality image (it's the same of DSR that is a way to obtain better image without activating antialiasing that always ruin a little the image)
So basically, it's only about UI? Because games assets, video quality and everything that would actually gain from an increased resolution wouldn't change.
When I put my old adobe indesign CS5 that is not meant for QHD/4K screen, forcing it to do so just make a lot of issue with misplaced/unreadable text,which is understandable since the high resolution wasn't taken into account when designing the UI. But well, I do not know enough about designing android app, maybe there is a magic tool in the app itself that does the job, but then, why wouldn't Sony activate it from the start? Could be like the 120Hz toggle with a warning rendering natively at 4k would drain more battery.
High end TV's have now really good algorithm to upscale. Of course you wouldn't have the native detail of a 4K, but a FHD content on the 4k would still appear sharper than on a FHD screen. but yeah, lower quality than native 4k or higher, of course.
Hildr said:
So basically, it's only about UI? Because games assets, video quality and everything that would actually gain from an increased resolution wouldn't change.
When I put my old adobe indesign CS5 that is not meant for QHD/4K screen, forcing it to do so just make a lot of issue with misplaced/unreadable text,which is understandable since the high resolution wasn't taken into account when designing the UI. But well, I do not know enough about designing android app, maybe there is a magic tool in the app itself that does the job, but then, why wouldn't Sony activate it from the start? Could be like the 120Hz toggle with a warning rendering natively at 4k would drain more battery.
High end TV's have now really good algorithm to upscale. Of course you wouldn't have the native detail of a 4K, but a FHD content on the 4k would still appear sharper than on a FHD screen. but yeah, lower quality than native 4k or higher, of course.
Click to expand...
Click to collapse
IIRC it just runs (and displays) at a reduced resolution until you open some whitelisted apps. Screenshots are "upscaled" to native res to hide that the res is actually lower. At least this is how it was in A11.
BlazingKahn35 said:
21.3 GB folder on MEGA
17 files and 16 subfolders
mega.nz
Click to expand...
Click to collapse
Is there like a thread on this somewhere? Or someone who manages this (you?). As someone else mentioned the linked thread is for the A11 version only. I was waiting for an "adequate" A12 ROM.
UsernameNotRecognized said:
IIRC it just runs (and displays) at a reduced resolution until you open some whitelisted apps. Screenshots are "upscaled" to native res to hide that the res is actually lower. At least this is how it was in A11.
Click to expand...
Click to collapse
If you have two pixels rendered, and display them on a screen with 8 pixels available, without upscaling, you'll get 2 pixels floating in the middle of 6 black pixels.
That's what happened in old CRT screen that didn't do the upscaling by themselves, setting a 480p content on a 720p screen would return big black bar all around the content.
The content on the xperia is rendered at various resolution depending on the max possible by the apps, then upscaled to fill the 4k screen, the same way it's done for all 4k tv or screen, so you don't have your content in a post stamp in the middle of a black screen. That's why your screenshot are 4k, not because they were upscaled afterward, what would even be the point of upscaling the screenshot to begin with?
Well, now that I read again the first post, in the morning with a fresh brain, I understand that the phone return a hardware display size lower than 4K for a multiple apps that would be able to render in 4K natively, rather than being upscaled. And that's what you are trying to change.
I understand now. I'm just not sure at this lvl of dpi the human sight is able to differentiate native 4K from upscaled 4K (doesn't mean the 4k is useless, upscaled 4k is still better than qhd display, especially for amoled). But whatever, that's just my personal pov. Hope you get it working then!