Hi people, am currently waiting for bootloader unlock, am trying to sort things out and see how am gonna use my new rooted phone Xiaomi Redmi Note 9 Pro (got it as gift), well phone is great, but am coming from old era where rounded corners and notch was not a thing, i still prefeer screens with rectangle shape, and am willing to sacriface lower portion of screen up to ending of rounded corner and same above till the camera module, so i can have nice rectangular screen
Now my question is how to?
How to change screen size? (how to measure where to start and end)
If by software rounded corners still exist how to remove them?
Am planing to flash xiaomi.eu rom (am considering Ressurection Remix) and magisk root.
Thank you great people and community.
It's simple, and can be done without rooting, connect with ADB.
So your device has 1080x2400 resolution, you'll have to lower numbers from the height (2400) in order to get a rectangular display.
Play with numbers till you get it right, commands to use:
adb shell
wm size 1080x2200
Mohamedkam000 said:
It's simple, and can be done without rooting, connect with ADB.
So your device has 1080x2400 resolution, you'll have to lower numbers from the height (2400) in order to get a rectangular display.
Play with numbers till you get it right, commands to use:
adb shell
wm size 1080x2200
Click to expand...
Click to collapse
Thank you very much, i will check it out once i got bootloader unlock since am waiting 168h on Xiaomi devices, i will not fiddle with anything so i dont mess something up
And about software rounding, since when in settings i choose option to hide notch and move status bar down, it hides a notch and its completley disabled part of screen, but it still gets a rounded corners by software, i will try this with option dont hide anything maybe then under hardware display is rectangular, but you never know i will let you know , but if it is software how can i find it on my device, since i googled and found something for Pixel devices, and its all diffrent, thank you alot.
And what about DPI , or resolution after that change, should i keep everything as it is
essen33 said:
Thank you very much, i will check it out once i got bootloader unlock since am waiting 168h on Xiaomi devices, i will not fiddle with anything so i dont mess something up
And about software rounding, since when in settings i choose option to hide notch and move status bar down, it hides a notch and its completley disabled part of screen, but it still gets a rounded corners by software, i will try this with option dont hide anything maybe then under hardware display is rectangular, but you never know i will let you know , but if it is software how can i find it on my device, since i googled and found something for Pixel devices, and its all diffrent, thank you alot.
And what about DPI , or resolution after that change, should i keep everything as it is
Click to expand...
Click to collapse
Hiding notch ain't that effective, and you lose some of your screen doing so.
Your screen is a rounded AMOLED, that's hardware, it also has software roundness in order to be compatible with your screen. It's not that hard to disable roundness, for hardware, you can overcome it by "wm size", and you can change DPI by: "wm density xxx" to your desired value.
The software overcoming needs APK editing, so you need a PC/Laptop. You need to edit framework-res.apk (and maybe SystemUI.apk). There's an app that allows you to edit framework-res.apk values directly, you may want to check it:
Privset.
Mohamedkam000 said:
Hiding notch ain't that effective, and you lose some of your screen doing so.
Your screen is a rounded AMOLED, that's hardware, it also has software roundness in order to be compatible with your screen. It's not that hard to disable roundness, for hardware, you can overcome it by "wm size", and you can change DPI by: "wm density xxx" to your desired value.
The software overcoming needs APK editing, so you need a PC/Laptop. You need to edit framework-res.apk (and maybe SystemUI.apk). There's an app that allows you to edit framework-res.apk values directly, you may want to check it:
Privset.
Click to expand...
Click to collapse
Thank you, its actually LCD, on Redmi note 9 pro, Thank you for commands above, when i screenshot something it appears rectangle, so in theory it should work and rounded edges should not be there
Well for that APK stuff, does installing custom ROM help in that? I was thinking about RR rom,
Also, i dont mind losing screen size, and for me hiding notch is a must doing it this way, personally i hate it, i hate rounded edges, i just hate it my heart hurts when i see it, i got this phone as gift so i need to appreciate it i cant sell/replace it that way its kinda disrespectful
essen33 said:
Thank you, its actually LCD, on Redmi note 9 pro, Thank you for commands above, when i screenshot something it appears rectangle, so in theory it should work and rounded edges should not be there
Well for that APK stuff, does installing custom ROM help in that? I was thinking about RR rom,
Also, i dont mind losing screen size, and for me hiding notch is a must doing it this way, personally i hate it, i hate rounded edges, i just hate it my heart hurts when i see it, i got this phone as gift so i need to appreciate it i cant sell/replace it that way its kinda disrespectful
Click to expand...
Click to collapse
Oh sorry, I assumed it being a budget killer to offer an AMOLED display similar to RN10.
Well .. having LCD makes it a bit different, as the parts you cut off from your display will keep lightening up, that's how LCD displays work.
Honestly, you'll hate it more, it'll be like watching a long video on YouTube without fullscreen mode.
Strange tradition you've got right there, here, we're more understanding, if someone gifted you a phone, it won't matter if you sold it or replaced it, what matters is the feelings you've grown out of his gift.
About the APK stuff, it can be done on any ROM, but it's more stable on AOSP-based ROMs like RR, Havoc, PE, ...
An easy way to achieve your goal would be to use adb wm size, and reduce height. (There's another thing to do, adjust the new touch positions; cause your phone will keep using old positions, so if you're using gestures, it won't work that simple, till you recalculate it. (Easy to solve).
Mohamedkam000 said:
Oh sorry, I assumed it being a budget killer to offer an AMOLED display similar to RN10.
Well .. having LCD makes it a bit different, as the parts you cut off from your display will keep lightening up, that's how LCD displays work.
Honestly, you'll hate it more, it'll be like watching a long video on YouTube without fullscreen mode.
Strange tradition you've got right there, here, we're more understanding, if someone gifted you a phone, it won't matter if you sold it or replaced it, what matters is the feelings you've grown out of his gift.
About the APK stuff, it can be done on any ROM, but it's more stable on AOSP-based ROMs like RR, Havoc, PE, ...
An easy way to achieve your goal would be to use adb wm size, and reduce height. (There's another thing to do, adjust the new touch positions; cause your phone will keep using old positions, so if you're using gestures, it won't work that simple, till you recalculate it. (Easy to solve).
Click to expand...
Click to collapse
Well its a family gift so if i sell it it would be toxic "you didnt like my gift" , iam about to flash RR, so i will look into that, i dont mind having background light on unused part of screen, well how if you dont mind, your tips on recalculating touch positions, i found some googling around, what you recommend, thanks alot
essen33 said:
Well its a family gift so if i sell it it would be toxic "you didnt like my gift" , iam about to flash RR, so i will look into that, i dont mind having background light on unused part of screen, well how if you dont mind, your tips on recalculating touch positions, i found some googling around, what you recommend, thanks alot
Click to expand...
Click to collapse
Okay, so a year ago, I had Galaxy S7 that got some water issues, so the bottom part of screen wasn't working, and I was using on-screen navigation bar, so I used ADB wm commands to make the phone usable until it dries up.
What I did was, reducing screen height up to the usable part. Then, I used: adb wm overscan command.
This command tells the system where is the screen end, whether at top, bottom, right, or left. So if your bottom screen is reduced by 2 cm, you'll have to tell your system about that, so that it don't assume it's still at the actual hardware values.
The command uses numbered values separated by commas like this (original values):
wm overscan 0,0,0,0
The numbers are organised LEFT,TOP,RIGHT,BOTTOM
You can use minus too, I honestly don't remember which numbers were suitable for my case, you'll have to check it on your own (won't take over 10 minutes). Only change TOP & BOTTOM values.
Who knows, maybe you won't need to do this anymore, perhaps Android 11's AI does that automatically whenever changing screen resolution.
Mohamedkam000 said:
Okay, so a year ago, I had Galaxy S7 that got some water issues, so the bottom part of screen wasn't working, and I was using on-screen navigation bar, so I used ADB wm commands to make the phone usable until it dries up.
What I did was, reducing screen height up to the usable part. Then, I used: adb wm overscan command.
This command tells the system where is the screen end, whether at top, bottom, right, or left. So if your bottom screen is reduced by 2 cm, you'll have to tell your system about that, so that it don't assume it's still at the actual hardware values.
The command uses numbered values separated by commas like this (original values):
wm overscan 0,0,0,0
The numbers are organised LEFT,TOP,RIGHT,BOTTOM
You can use minus too, I honestly don't remember which numbers were suitable for my case, you'll have to check it on your own (won't take over 10 minutes). Only change TOP & BOTTOM values.
Who knows, maybe you won't need to do this anymore, perhaps Android 11's AI does that automatically whenever changing screen resolution.
Click to expand...
Click to collapse
Thanks alot i managed to set it up, very helpfull
essen33 said:
Thanks alot i managed to set it up, very helpfull
Click to expand...
Click to collapse
Glad I could help.
Hello, I have a problem and a question with him. When I install a custom rom and lower the resolution, despite using the notch bar killer, a notch remains that got bigger and I can't delete them, also when I put the dark mode it becomes white
Related
On my unrooted phone the "Steamy Window" application worked fine
If I pressed a little it would make a little line in the "steam", and if I were to push my thumb down on a large area, it would detect that and make a "thumb" sized print.
Now using JF1.41 no matter what I do it only makes a TINY TINY line, about a pixel or two in size.
Did the modification of the screen change an api that the Steamy Window app is using to work different?
Well, maybe you should go back to an unrooted phone so that you can play with your steamy window....
LPChris, I would expect a little more maturity from a "senior member"
I am trying to contribute to make JF the best it can be. Maybe your just having a bad night or something, but theres no need to be so childish.
:ed:
Looking through your posts it seems like your just having a bad night
Back on topic:
While this may be a stupid little problem with one application. Should finger-area sensitive applications continue to be made this could isolate JF1.41 from the market. Naturally I dont care much for steamy window, but I would like to prevent other issues in more... useful... applications
I've seen some weirdness where my home screen has a jitter. I've also had accuracy issues with clicking menu items and buttons. I'm going to backup my phone and load JF 1.31 back on to see if it is the screen or the img.
Interesting...I just reflashed with 1.41 RC30 and the problem went away. I was using the fade to blue theme .99.
sjbayer3 said:
On my unrooted phone the "Steamy Window" application worked fine
If I pressed a little it would make a little line in the "steam", and if I were to push my thumb down on a large area, it would detect that and make a "thumb" sized print.
Now using JF1.41 no matter what I do it only makes a TINY TINY line, about a pixel or two in size.
Did the modification of the screen change an api that the Steamy Window app is using to work different?
Click to expand...
Click to collapse
Ditto about LPChris lol, a lot of his posts sound like that, but yeah I noticed the same thing about the steamy window app before and after using JF 1.41.
Steamy window, LOL! sorry guys. anyway keep up the great work.
Yes, this is a trivial example, but it does identify a real issue.
I was reading through the various google android groups last night and I ran into some info that seems to addresses this issue. From what I was able to gather, the JF1.x implementation of multi-touch uses a community hack that reassigns the value that normally keeps track of the size of the touch input. This value is now used to keep track of the distance between two touches. (see: http://groups.google.co.uk/group/android-platform/browse_thread/thread/209b512a9fdf7367?hl=en)
your Steamy Window app seems to make use of the size value as it was originally designed. Now with the change, with only one finger input, this value is set to some minimum, producing a thin line.
To test this theory, see if when you touch the screen with two fingers the size of the mark gets bigger.
Why can't a capability bit or other mechanism be defined that could be used to indicate whether or not an application were multi-touch aware, so that the touch handling behavior at the lower levels would revert to "standard" behavior for normal (non-multi-touch) apps? Trying to make the multi-touch hack fully backwards compatible may not be practical.
I tested your idea about multituch possibly fixing steamy window
My only results are really strange.
If I touch with two fingers it will make a line about the width of my 2 fingers, but its located in the top left, no matter where my fingers actually are. Furthermore the line isnt straight its curved.
Now, after my first touch, it seems if I touch it again it just crashes.
ex-MN said:
From what I was able to gather, the JF1.x implementation of multi-touch uses a community hack that reassigns the value that normally keeps track of the size of the touch input. This value is now used to keep track of the distance between two touches. (see: http://groups.google.co.uk/group/android-platform/browse_thread/thread/209b512a9fdf7367?hl=en)
Click to expand...
Click to collapse
Edit: Hmm... the x-y data of the second finger is stored in separate fields. I think the usage of the size field is just as a boolean to tell multitouch capable programs that second finger data is being sent.
themes and JF RC versions. be careful
TheDudeOfLife said:
I've seen some weirdness where my home screen has a jitter. I've also had accuracy issues with clicking menu items and buttons. I'm going to backup my phone and load JF 1.31 back on to see if it is the screen or the img.
Interesting...I just reflashed with 1.41 RC30 and the problem went away. I was using the fade to blue theme .99.
Click to expand...
Click to collapse
it seems as tho themes have to be matched to the rom, a theme for 1,30 may flake out on 1.41, most of the themes I have seen and used so far were marked as to which rom the were intended to theme...
BhanG
bhang said:
it seems as tho themes have to be matched to the rom, a theme for 1,30 may flake out on 1.41, most of the themes I have seen and used so far were marked as to which rom the were intended to theme...
Click to expand...
Click to collapse
After some more testing I have this same issue on 2 1.41 compatible themes (rusty metal and fade to blue) I am going to go back to themeless 1.41 but I think it is more related to the multitouch 'hack' than the theme themselves. I find it hard to believe that a bunch of icons could mess this up. I watches my screen jitter between the left and right screen for 3 minutes today before I just performed a soft reset on my phone.
Note: I also applied each theme from a fresh flash of 1.41...not on top of each other.
this happens with screen crack also, but it doesnt affect me that much until i start not being able to select stuff. i know it may be important its just not to me... yet *knocks on wood*
Yeah Ive noticed it too..
I thought that it was just the app at first.
I might be switching back to .31 then at least til this gets fixed.
Steamy window def is NOT reading my fingers location or size properly.
I've also seen it affect touch paint found in the API Demos. Doesn't even register touch anymore.
It appears multi-touch is premature at this point and to implement multi-touch throughout the OS and not just the browser like everyone seems to think isnt good. It is definitely is throughout the OS and probably will affect any application that uses the second touch value to register touch size.
My other concern is that dev's won't take this hacked multi-touch into account so they will continue to write programs that won't be compatible since its not the "norm"
Taken from and android forum...this is my biggest concern
"Please think about soft keyboards when considering multi-touch APIs,
where the problem isn't detecting the distance between two finger, but
rather is allowing a 2nd finger (or thumb) to come down on a 2nd key
before the first finger (or thumb) has been released. The proposed
API to provide only a centroid and the distance between fingers won't
work at all for this sort of application.
I think you'd ultimately want to package this as additional
GestureDetector subclasses, depending on whether the type of gesture
detection wanted was pinch/zoom or multiple/overlapping taps.
Keyboards (and maybe games) would use one class, browsers another.
Providing the right information from a touch panel to drive either
detector might be challenging, especially if the panel provides
'unpaired' x and y coordinates rather than individual touch locations,
but I believe it could be done. "
JesusFreke,
Any thoughts on this?
Yeah lets hear what JF's got to say.
I originally thought that the multitouch was embedded in the browser, It's too soon to have it throughout the entire OS...
How about 1.41=with multitouch and 1.42=without
I've installed JF1.41 and I have an unusual bug....sometimes the screen behaves like it isn't calibrated..i press the screen on a button and it is pressed another one....have anyone encoutered this problem?
I invite everyone to do the following to find out how ur touch registers on ur screen. Open anycut. Get it if u don't have it.
Click activity and find raw image viewer. Click ok and then click on the shortcut.
Now start moving your finger around and see the results.
Let's all post our results here so we can figure this out.
Post in the same format as me:
ROM: JF1.41
1 finger - it surpisingly followed my finger perfectly. It only registered the very center point of my finger.
2 fingers - it appears that it made the same point as the 1 finger, however now the point was exactly in between my fingers and stayed there as I moved them around.
Ok so now we need ppl with stock rc30 and 1.31 so we can test this out!
You wanna have some real fun? Try it with 3 or 4 fingers.. It goes nuts..
So, I know this title seems odd; I changed the resolution of my Phone with ADB to maybe get a 18:9 screen ratio but with more sharp edges since I really dislike how the 7 Pro has such round edges that just look terrible in some app's overlay, bc they weren't built for that in mind.
however, I found out that that won't help me with my problem. I thought the Screen Corners were just a hardware thing, but it turns out its actually on software as well. Does someone know how to potentially remove these? (it will probably not have these software added notches in custom roms, but i'd prefer using the default/openbeta rom from oneplus directly)
try this. the instructions are for a google pixel 3, but hopefully those settings exist for the oneplus.
disable rounded screen corners on pixel 3
altwu said:
try this. the instructions are for a google pixel 3, but hopefully those settings exist for the oneplus.
disable rounded screen corners on pixel 3
Click to expand...
Click to collapse
thanks for the answer, it doesnt work like that for the oneplus 7 pro, but i will look into stuff like this and reply again if i found out how to do it <3
Not sure what you expect to accomplish. The rounded corners are the physical edge of the display. You can see this in TWRP or any non-black boot animation.
Dungeon47 said:
Not sure what you expect to accomplish. The rounded corners are the physical edge of the display. You can see this in TWRP or any non-black boot animation.
Click to expand...
Click to collapse
as i said i wanted to reduce the vertical size of the screen and disable the software rounded corners. i only found out that there are software edges BECAUSE i changed the resolution of the display via adb.
Hello, are you talking about this broken corners thing ? Because whenever I install a custom ROM, the corners are very pixelated, which doesn't happen in Oxygen OS. Also, still concerning OOS, I tried to modify the overlay with the adb overscan thing and I was able see the rounded overlay moving, so it's definitely related to the software.
Also I managed to get a picture of the same problem on a OnePlus 6T. You can clearly see the pixelated corners.
I truly hate how there isnt an option for this. You can use "adb settings put secure sysui_rounded_size X" on Android 9, but not on Android 10. There doesnt seem to be a way to do it. I've used a Substratum theme (Curve) to temporarily (for a second) disable the rounded corner overlay but it doesnt stick, and there is nothing I've found over 3 days of intense searching for hours and hours. Custom ROMS have the option (Havoc 3.1 has a rounded-corner radius slider setting but changing it has no effect, even after rebooting).
Please tell me there is something someone has come up with. Its so annoying to have an ugly af rounded corner. I am using adb to reduce the display height to create a "software bezel" and want to reduce the rounded corner radius so it looks much less rounded. I can do it on Android 9, but the nav bar doesnt work well on it, and much prefer Android 10.
To ellaborate, the "adb settings put secure sysui_rounded_size X" setting DOES work properly on OOS, but not on anything beyond Android 9. You likely wont notice on Android 9 unless you set the display height smaller than what stock is. "adb shell wm size 1440x2990" is the best size I can say that fits well with sysui_rounded_size of 25 or 30.
Is there an update to this?
have anyone solved the prob?
I know you said something about wanting to be on OOS, but I've found a setting on Resurrection Remix that allows you to change the size of the rounded corners.
I got back on this topic today.
I got it working by using apktool on the ODMOverlay-OPSystemUI.apk and removing the pathData from rounded_bottom.xml and rounded_top.xml. then used rootbrowser to overwrite the original. I assume this could be done using a magisk module, but i couldn't get it to work properly.
Ixaruz said:
.... I got it working by using apktool on the ODMOverlay-OPSystemUI.apk and.... I assume this could be done using a magisk module, but i couldn't get it to work properly.
Click to expand...
Click to collapse
That app seems specific to OnePlus devices. Have you had any success with making a Magisk module yet? And, could that work on other devices also? My device is Poco X3 Karna running AICP (Android 12.1) rom. I am very much interested in this; I prefer 'rectangular' screenshots. Please reply. Thanks.
Hi Guys! If you could, what Apps would you like to run on your cover screen, given that it's really small or what type of information you wish you could access from the cover screen?
I am a developer, so maybe, just maybe I will be your genie to your wishlist of cover screen apps.
Go ahead, be as creative as you could be! I look forward to hear ideas other than using the Cover Screen as a Notification LED please.
there is no native android support outside screen... so you can't to do anything...
if you are wizard - make please for start AOD on cover screen
andrealin said:
there is no native android support outside screen... so you can't to do anything...
if you are wizard - make please for start AOD on cover screen
Click to expand...
Click to collapse
I obviously can do some magic.
That's why here to collect ideas which the actual users may would like to see, I won't be super keen on AOD implementation as that would eat up battery, but sure, could be an option. I have my own list of to-dos for the first version of the Super App, just want to see what users come up with.
something can toggle wifi Bluetooth sound flashlight.....
I used aod on all my samsungs. and even on large screens it didn't add much to the battery drain. But how many forums I read, most users are at a loss why the small Samsung display, which is logical for aod, was not used in this model.
about adding functional - enabling bixby routines would be logical without opening the phone.
moji666 said:
something can toggle wifi Bluetooth sound flashlight.....
Click to expand...
Click to collapse
Yes, they are nice ideas, noted already.
andrealin said:
I used aod on all my samsungs. and even on large screens it didn't add much to the battery drain. But how many forums I read, most users are at a loss why the small Samsung display, which is logical for aod, was not used in this model.
about adding functional - enabling bixby routines would be logical without opening the phone.
Click to expand...
Click to collapse
Well, if Samsung natively implements sure, not much batter drain, but as a third-party developer there are limited access to the APIs (at least not without root.) But yeah, I will see what I can do about it. Bixiby routines, interesting.
I second the toggles for bluetooth/sound/flashlight. Also would like the notification ring as well.. like the ring we see when we charge it.
super. I hope you will finish this soon
Thanks forbyour work is it possible to choose thé number of lines of notification liké the Google assistant message (3 lines) and an vertical scrolling and longer time before extinction for notifications ?
Please
jagan2 said:
Hi Guys! If you could, what Apps would you like to run on your cover screen, given that it's really small or what type of information you wish you could access from the cover screen?
I am a developer, so maybe, just maybe I will be your genie to your wishlist of cover screen apps.
Go ahead, be as creative as you could be! I look forward to hear ideas other than using the Cover Screen as a Notification LED please.
Click to expand...
Click to collapse
any news?
Sent from my SM-F700F using Tapatalk
I have a couple days with the flip and for my confort don't spend to much effort to open and for the sake of won't scratch more often when I put on every surface close position, I semi-close pacman like position and put like a stand so the metal frame only touch the surface not the glass and that way when I have to open only use one hand to fully open.
But in that position all the notifications appear on the main screen, so no way to see what notification have, it's there a way to show the notifications on the second mini screen in open position?
I agree, just a simple AOD digital clock would be sweet
bobbydharrell said:
I agree, just a simple AOD digital clock would be sweet
Click to expand...
Click to collapse
Yes just like always on display all time that you choose if you want always on display all time on the outside screen even when its open.
Sonos app!!!!!
Hi,
I really like to use custom width on all my previous phone.
But the current setting for Developer option/Smallest width is only 411 dpi.
Can I go above the value without problems such as poor fingerprint reader position ? Can someone share their own dpi value?
Thanks in advance.
Im using the 8 pro and i set my dpi to 520.
In oos10 the only issue was that the navigation gestures were too picky and kind of hard to use due to the smaller trigger points. (Also the ringer switch toast was too high but thats just aesthetic so whatever)
In oos 11 that issue is gone and i see no downsides at all.
In any case, go ahead and try it out. You can always change it back
Xeroman0 said:
Im using the 8 pro and i set my dpi to 520.
In oos10 the only issue was that the navigation gestures were too picky and kind of hard to use due to the smaller trigger points. (Also the ringer switch toast was too high but thats just aesthetic so whatever)
In oos 11 that issue is gone and i see no downsides at all.
In any case, go ahead and try it out. You can always change it back
Click to expand...
Click to collapse
Thanks a lot mate! It looks much more to my liking now.
How did you figure 520 value? Did you just through trials and error ?
I use 587. It's what my 5t was at when I switched, but I like things very small.
(I buy big phones to see more content, not the same content but bigger).
On anything built right for our phone I have no issues, but roms ported to our device sometimes have issues placing things.
*edited*
N173M43R said:
I use 587. It's what my 5t was at when I switched, but I like things very small.
(I buy big phones to see more content, not the same content but bigger).
On anything built right for our phone I have no issues, but roms ported to our device sometimes have issues placing things.
Click to expand...
Click to collapse
Wow! That must be really small. Are you not having a bad time when reading text or something?
apit23 said:
Wow! That must be really small. Are you not having a bad time when reading text or something?
Click to expand...
Click to collapse
Not really. I wear glasses, so as long as I'm awake I basically have 2020 vision. And I keep my phone at a normal distance from my face.
Idk I just like having a lot on the screen. I do a lot of reading and web surfing on my phones.
I'm using La sys tools to modify density to 360
even lower density can be configured successfully, But the nofiy bar and camera "hole" displays abnormal when the status bar is pulled down.
apit23 said:
Hi,
I really like to use custom width on all my previous phone.
But the current setting for Developer option/Smallest width is only 411 dpi.
Can I go above the value without problems such as poor fingerprint reader position ? Can someone share their own dpi value?
Thanks in advance.
Click to expand...
Click to collapse
454 works nicely for me.
Also using 454!
I toggle between default 411 and 520 on 8T
Hi Guys,
Long time user of Sonys Compact phones here, so I'm custom to small screens and one hand operation of my phone, i HATE that I have to use two hands, and the manufactors thinks that we all loves big screens..
Ok so I bought a Google Pixel 4a, but for me thats also to big.
I have tried to set the display resolution via adb wm Size function, it works like a sharm, but the phone centeres the display, and google have for some reason removed the overscan function i version11, so I cant set the display to be on the bottom. "damn you google"
I have also tried the Quick cursor app, but its so slow to use all the time.
Then a thought, is there a way to force all apps only to be X pixels high, and fixed at the bottom of the screen? I dont want to ever reach over a certain point of my screen.
Or is there another way to solve my problem?
We are seeing our selfs as a smart race, but creates devices that needs two hands to operate?! jeezzee
PS. No root options wanted.
Kind regards
Morten
May be Android's Split Screen mode is a workaround.
BTW: On ChromeOS, Android apps can be presented in free‑form windows that are arbitrarily resizable