I found a "bug" if is that a way to call it; there's unused screen area near the notch and bottom areas that always just stays black (tiny, right near the bezels.)
If you go to the settings>Additional Settings>Accessibility and then you change the display size from "Default" to "Large" you'll notice a change on the display size, this is probably a software thing that "fills" the corners of the screen and it's even more noticeable on the notch area and on the bottom part of the screen, I don't know if this is intended but I see no reason to have that space being "cutted" from the screen.
Users please try this on your devices to see if i'm not the only one with this issue.
Link to the official bug report on the MIUI Forums; https://en.miui.com/thread-5554559-1-1.html
yes even i noticed it . very small but its there
Yeah I also noticed it... Did you make a post about this in poco forum?...
souvy said:
Yeah I also noticed it... Did you make a post about this in poco forum?...
Click to expand...
Click to collapse
Yeah, I already make the post on the official forum, even on the .eu one, please go there and make some noise if you want;
https: // en.miui.com/ thread-5540787-1-1 .html
(I'm not able to post links yet, the title is the same on the forum)
Daenjel said:
I found a "bug" if is that a way to call it; there's unused screen area near the notch and bottom areas that always just stays black (tiny, right near the bezels.)
If you go to the settings>Additional Settings>Accessibility and then you change the display size from "Default" to "Large" you'll notice a change on the display size, this is probably a software thing that "fills" the corners of the screen and it's even more noticeable on the notch area and on the bottom part of the screen, I don't know if this is intended but I see no reason to have that space being "cutted" from the screen.
Users please try this on your devices to see if i'm not the only one with this issue.
Click to expand...
Click to collapse
What MIUI are you using ? I don't have such an option under Accessibility
hyborian said:
What MIUI are you using ? I don't have such an option under Accessibility
Click to expand...
Click to collapse
MIUI 10.2.2.0(PEJMIXM) and the option it's called "Display Size" on the "Accessibility" tab.
Daenjel said:
MIUI 10.2.2.0(PEJMIXM) and the option it's called "Display Size" on the "Accessibility" tab.
Click to expand...
Click to collapse
Ok, thanks. I don't have the option. Maybe because I use MIUI 10 Global Beta ROM 9.1.24, and I have MIUI Optimization set to off in Developer Options.
I've also noticed that border around the display, it's obvious when switching options from developer options > simulate display with cutout, choosing any option will switch off that border for a second.
Although no actual solution to it as it obviously should be fixed, I have found that changing "smallest width" in developer options to 381 is the sweet spot where this occurs. Going above 381 will result in the "incorrect" cutout, 381 is where the screen gets fully utilized
yes, setting 381 hides it! Thank you!
dblazen said:
Although no actual solution to it as it obviously should be fixed, I have found that changing "smallest width" in developer options to 381 is the sweet spot where this occurs. Going above 381 will result in the "incorrect" cutout, 381 is where the screen gets fully utilized
Click to expand...
Click to collapse
Yes!! Thanks for the temporary fix! Now the screen looks blessed to my eyes, although, I hope Xiaomi doesn't ignore this little bug and fix it on a near future, thanks again.
True store. I've put 381 and a little more space appeared on screen. Very weird. Thanks for the tip.
On a side note it doesn't work in landscape mode, it's messed up overall in landscape
on 9.1.24 is set to 392 and I see no difference in changing it.
fastmix said:
on 9.1.24 is set to 392 and I see no difference in changing it.
Click to expand...
Click to collapse
On 9.1.24, mine shows 320. Changing it to 381 gives some more space sideways, but it makes my fonts also too small for my weak eyes. So I stick with default 320 first.
dblazen said:
Although no actual solution to it as it obviously should be fixed, I have found that changing "smallest width" in developer options to 381 is the sweet spot where this occurs. Going above 381 will result in the "incorrect" cutout, 381 is where the screen gets fully utilized
Click to expand...
Click to collapse
I've just realized that an small part of the screen isn't working by changing the developer option "simulate a display with a cutout". Even in the last MIUI 10 version that bug is still present. Your solution works very well. Thanks
I have noticed the same on the the to and top and bottom edge. It's more prominent under direct sunlight.
dblazen said:
Although no actual solution to it as it obviously should be fixed, I have found that changing "smallest width" in developer options to 381 is the sweet spot where this occurs. Going above 381 will result in the "incorrect" cutout, 381 is where the screen gets fully utilized
Click to expand...
Click to collapse
In MIUI 11 that setting isn't working well because the status bar doesn't align to the notch (381. 392 default but the screen isn't fully used). Have you tried another value?
Related
I've seen a few threads/comments here about the flickering/adjusting of the backlight level at lower (less than 50%) brightness levels even though auto-brightness was off. As was suspected, it's just due to a content adaptive backlight module. It can be shut off by just running the CABLPreferences activity of the com.qualcomm.cabl app. It also looks like there is a "quality" setting in there to play with that just varies the aggressiveness of the effect.
If you don't know how to launch an activity, you can do the following:
Via ADB:
Code:
adb shell "am start -a android.intent.action.MAIN -n com.qualcomm.cabl/com.qualcomm.cabl.CABLPreferences"
Via Terminal on your phone:
Code:
am start -a android.intent.action.MAIN -n com.qualcomm.cabl/com.qualcomm.cabl.CABLPreferences
I haven't done any more checking, but I'm guessing this is just a flag that could be set in sys/devices/blah... by init.d script on boot as well.
If you prefer a gui, there are plenty of launchers out there that can select an activity to start. I actually had it set up as a long-press pie on LMT while I was playing with it.
It seems (on my phone, at least), that the app wasn't as good at turning it back on, but you can just clear the app data/cache on "Content Adaptive Backlight Settings" in application manager, reboot, and you'll be back to stock behavior.
Sorry I didn't post this sooner. I've been too busy playing with the G2!
this doesn't work.
I've tried this weeks ago. simply telling the app to turn it off does nothing, as it's still on no matter what. deleting the app produces the same exact effect.
in the build prop, the line pointing to cabl is set to false. therefore it's really not even reading what the app is saying it seems.
I believe it's a kernel issue that can only be solved once we get a custom one.
again, this isn't a fix and doesn't turn it off at all sadly.
Sent from my VS980 4G using Tapatalk 4
https://www.youtube.com/watch?v=slwkFhpiYbs&feature=youtube_gdata_player this video was made when it was set unchecked and set to off.
Sent from my VS980 4G using Tapatalk 4
I read your post about this a couple of weeks ago and saw that you mentioned deleting the app, but did you try running it, unchecking the box and rebooting? Deleting it won't do anything, as the app is set to run on boot and (as far as I can tell) set whatever selection you have chosen. I did and this seems to have worked for me I checked by scrolling through a spot on settings that had normally triggered it. I'll play with it more later to see if I either got lucky when I tested it or it is still happening. I agree that this is working on a kernel level.
Is this issue on all carrier versions?
I use auto-brightness and the annoyance I have is that it doesn't change brightness right away when entering different lighting environments. It either takes time or doesn't change at all until I uncheck/check the auto-brightness setting.
xdabbeb said:
I read your post about this a couple of weeks ago and saw that you mentioned deleting the app, but did you try running it, unchecking the box and rebooting? Deleting it won't do anything, as the app is set to run on boot and (as far as I can tell) set whatever selection you have chosen. I did and this seems to have worked for me I checked by scrolling through a spot on settings that had normally triggered it. I'll play with it more later to see if I either got lucky when I tested it or it is still happening. I agree that this is working on a kernel level.
Click to expand...
Click to collapse
yeah, if the app is deleted, then it can't run unless defaulted to on without the app. . so i tried deleting it, and then i also tried un checking the box, and it still does it. no matter what, there must be a setting somewhere else to actually turn it off. did you see that line in the build prop? it's set to false... weird right?
Sent from my VS980 4G using Tapatalk 4
jayochs said:
yeah, if the app is deleted, then it can't run unless defaulted to on without the app. . so i tried deleting it, and then i also tried un checking the box, and it still does it. no matter what, there must be a setting somewhere else to actually turn it off. did you see that line in the build prop? it's set to false... weird right?
Sent from my VS980 4G using Tapatalk 4
Click to expand...
Click to collapse
Yep, I did...and I remembered I had set it to true before I even began messing with the CABL App. I was thinking that could be the difference between what you and I had tried, but I just did a bit more testing to see if it was happening still and unfortunately I think I may have seen it. I'll play with it a bit more later to be sure. I also did a quick look in the usual places for this to be turned on/off in /sys/class/ and couldn't find anything. I suppose it's possible LG built the kernel for this device without the ability to turn it off. If so...that'll be unfortunate.
xdabbeb said:
Yep, I did...and I remembered I had set it to true before I even began messing with the CABL App. I was thinking that could be the difference between what you and I had tried, but I just did a bit more testing to see if it was happening still and unfortunately I think I may have seen it. I'll play with it a bit more later to be sure. I also did a quick look in the usual places for this to be turned on/off in /sys/class/ and couldn't find anything. I suppose it's possible LG built the kernel for this device without the ability to turn it off. If so...that'll be unfortunate.
Click to expand...
Click to collapse
I believe the original Nexus 7 had this feature in the kernel too. However, in custom kernels you could use Trickster mod to toggle the feature off. I think the kernel devs had to expose the setting though, so maybe we'll get this taken care of if we can get a custom kernel.
Here are some build props for Qualcom devices that control the CABL
Code:
ro.qualcomm.cabl=1
hw.cabl.level=Auto
persist.qcom.cabl.video_only=1
By adding / editing these lines in the build.prop you should be able to adjust as noted in the lines.
And yes, it is in the kernel.
Dont know why LG has an app for it?
Scott, I sent you a message on hangouts but in my build prop, i don't show a 1 for the cabl setting.. i show false... as if it's already turned off in the build prop. I changed it to true once and it didn't do anything. those two top settings seem to be what's in the app.. you can check a box to turn it on and off (the first line) and then you can set the degree to which it handles the cabl (second line.) I've messed with both in the app and it did absolutely nothing... does the kernel need to be changed as well?
Sent from my VS980 4G using Tapatalk 4
xdabbeb said:
I've seen a few threads/comments here about the flickering/adjusting of the backlight level at lower (less than 50%) brightness levels even though auto-brightness was off. As was suspected, it's just due to a content adaptive backlight module. It can be shut off by just running the CABLPreferences activity of the com.qualcomm.cabl app. It also looks like there is a "quality" setting in there to play with that just varies the aggressiveness of the effect.
Click to expand...
Click to collapse
I'm not sure you really want to "fix" this feature.
LCD screens (like the one in the LG G2) have inherent low contrast ratio (just 1500:1, in comparison to infinity, with AMOLEDs). In order to compensate, LCD screens use a feature called "dynamic contrast", in which the backlight dims when the screen shows darker content, in order for the perceived black levels to appear darker (and not grey). I'm not sure you want to disable this feature, because the outcome will be grey blacks.
we do want to bc it causes horrible screen flicker issues. you can be sitting on a pic and it doesn't know what to do so it flickers badly
Sent from my VS980 4G using Tapatalk 4
Noam23 said:
I'm not sure you really want to "fix" this feature.
LCD screens (like the one in the LG G2) have inherent low contrast ratio (just 1500:1, in comparison to infinity, with AMOLEDs). In order to compensate, LCD screens use a feature called "dynamic contrast", in which the backlight dims when the screen shows darker content, in order for the perceived black levels to appear darker (and not grey). I'm not sure you want to disable this feature, because the outcome will be grey blacks.
Click to expand...
Click to collapse
I did not know about the contrast ratio on these screens. Makes sense what you are saying.
However like Jay said it does not react smoothly or at appropriate times.
Some will need to edit the kernel code to fix this.
Noam23 said:
I'm not sure you really want to "fix" this feature.
LCD screens (like the one in the LG G2) have inherent low contrast ratio (just 1500:1, in comparison to infinity, with AMOLEDs). In order to compensate, LCD screens use a feature called "dynamic contrast", in which the backlight dims when the screen shows darker content, in order for the perceived black levels to appear darker (and not grey). I'm not sure you want to disable this feature, because the outcome will be grey blacks.
Click to expand...
Click to collapse
Yep. What @jayochs and @scrosler said. What you wrote does make sense, and I had noticed that it behaves the opposite of the CAB implementation on AMOLED screens (where it dims on lighter colored content)...so that gives even more credence to what you're saying, but the implementation is a little buggy. It transitions abruptly and causes the "flickering" that many have reported. I certainly wouldn't mind having it enabled if the transitions were slower/less frequent, but it's kind of annoying as it is. I never was able to find a way to disable it in the stock kernel anyway, so hopefully it can be fixed one way or another now that the source is available. Still the best phone I've owned!
So any success with any method here or elsewhere?
I'm currently using Xposed to try and figure out what is going on here (I have several updateBrightness() events hooked, and am logging stack traces from them). It happened again less than an hour ago, so I need to go through that stack trace and see if I can figure out whether or not the actual brightness update can be blocked.
This has nothing to do with CABL, incidentally. I have CABL turned off, and I've seen the flicker-flicker-flicker-brightness drop issue with nothing more than a web page open. I usually keep my brightness around 68%-69%, too.
antinorm said:
I'm currently using Xposed to try and figure out what is going on here (I have several updateBrightness() events hooked, and am logging stack traces from them). It happened again less than an hour ago, so I need to go through that stack trace and see if I can figure out whether or not the actual brightness update can be blocked.
This has nothing to do with CABL, incidentally. I have CABL turned off, and I've seen the flicker-flicker-flicker-brightness drop issue with nothing more than a web page open. I usually keep my brightness around 68%-69%, too.
Click to expand...
Click to collapse
i'm thinking it's CABL, but it's kernel level, NOT software level, which is why disabling it does absolutely nothing.
I've been using Lux Auto Brightness to fix the issue.
Cheers!
Rayan said:
I've been using Lux Auto Brightness to fix the issue.
Cheers!
Click to expand...
Click to collapse
it's not an issue with auto brightness, that's a completely different problem.
this is the content adaptive backlight problem.
so no solution was ever found for this (besides a new kernel)? my phone doesn't flicker but on the brightness below 50% i can notice it's trying to readjust itself slightly once in awhile (with xda app or play store for example).
Encountered this issue as well. So, the cause of this has something to do with the software and not the hardware? Don't want to send my phone back just to receive yet another problematic set.. I set my screen brightness to 38 which it flickers on certain photos and apps. Bumped it up to about 45 and it seems to have stopped.
Hi All, I got my honor 10 yesterday and been happy with it so far and still exploring all the features.
As I start to transfer my apps from my old phone I noticed snapchat doesn't resize correctly with the notch along the top. So if you hide the notch, the snap chat menu still goes up so you can only see half the buttons (half on the screen, half off because the notch is blacked out.
With the notch on, you can see the buttons ok. I also noticed, if somebody has a long name or puts text along the top of their snapchat, the notch hides it. It appears to do this with the notch on or off and both in full screen mode and not.
Just wondering if anybody else has experienced it with any other apps and if there is a way round it. I personally prefer to have the notch disabled.
See picture, as you can see, the top buttons and hello message is cut off with the notch.
thorpe1992 said:
Hi All, I got my honor 10 yesterday and been happy with it so far and still exploring all the features.
As I start to transfer my apps from my old phone I noticed snapchat doesn't resize correctly with the notch along the top. So if you hide the notch, the snap chat menu still goes up so you can only see half the buttons (half on the screen, half off because the notch is blacked out.
With the notch on, you can see the buttons ok. I also noticed, if somebody has a long name or puts text along the top of their snapchat, the notch hides it. It appears to do this with the notch on or off and both in full screen mode and not.
Just wondering if anybody else has experienced it with any other apps and if there is a way round it. I personally prefer to have the notch disabled.
See picture, as you can see, the top buttons and hello message is cut off with the notch.
Click to expand...
Click to collapse
you should try updating the emui software, it helps with the notch (on instagram, haven't tried snapchat) using the on screen navigation buttons helps resizing as well
theleosanjaya said:
you should try updating the emui software, it helps with the notch (on instagram, haven't tried snapchat) using the on screen navigation buttons helps resizing as well
Click to expand...
Click to collapse
I am fully up to date. Upon further usage, I noticed it happens in other apps too. Instagram is actually a lot worse. It resizes length ways ok however not the correct size width ways. Most notably on stories so you can't see the first left and end right part. Looking online there's a lot of people complaining from Huawei and Samsung users (dating almost 3/4 months ago)
It appears to be an issue with the higher resolution android phones which app developers have been slow to fix. Hopefully, phone and app developers will come up with some kind of fix soon. Quite annoying as everything works flawlessly on iphones
Try changing the dpi on dev setting or play around with display view Setting for now until it get fixed
Doesn't work regardless of what combination of settings I have. Looks like there's a serious lack of compatibility with android devices at the higher resolutions. Annoying!
I have the exact same issue and I'm happy someone is discussing it, man I felt like I'm alone
I have noticed this same issue when using my Honor 10. I have not found a solution for it yet.
Wish this phone have the notch/status bar settings like in the G7 etc. Did I miss something?
Which settings? The V60 has settings under New Second Screen, which of course is confusing with the dual screen.
claydoh said:
Which settings? The V60 has settings under New Second Screen, which of course is confusing with the dual screen.
Click to expand...
Click to collapse
Oh my word I totally missed that smh haha. Had the phone in Night mode so it was grayed out and I never bothered paying it any mind.
Night mode is best mode anyway!
I installed Natcho Notch to hide mine most of the time. It doesn't work with my games, though. You know, if they would've went with a basic screen without a fake cutout with the dual case, I'd probably use it a lot more. I know they did it to be symmetrical with the main screen, but I would appreciate seeing everything.
Mejilan said:
Night mode is best mode anyway!
Click to expand...
Click to collapse
Yep, night mode 24/7
Mr_Mooncatt said:
I installed Natcho Notch to hide mine most of the time. It doesn't work with my games, though. You know, if they would've went with a basic screen without a fake cutout with the dual case, I'd probably use it a lot more. I know they did it to be symmetrical with the main screen, but I would appreciate seeing everything.
Click to expand...
Click to collapse
Good look, I'll have to check that out for myself. I think maybe LG was lazy and or cutting cost. Either way it makes no sense and takes away from the dual screen a bit to have the notch there. But aside from that I'm really digging the dual screen, ESPECIALLY after installing the Wide Mode app from the Play Store. Wide Mode everything haha
Anyone know how to hide the notch on the second display? I remember during the initial setup of the phone there was an option to keep the notch on the second display but now I can't find it in the settings.
roaduardo said:
Anyone know how to hide the notch on the second display? I remember during the initial setup of the phone there was an option to keep the notch on the second display but now I can't find it in the settings.
Click to expand...
Click to collapse
I don't recall ever seeing that, but would be awesome if possible.
roaduardo said:
Anyone know how to hide the notch on the second display? I remember during the initial setup of the phone there was an option to keep the notch on the second display but now I can't find it in the settings.
Click to expand...
Click to collapse
You can not hide the notch on the dual screen, only on the main display. Go to display>new second screen. Have to have night mode off though.
roaduardo said:
Anyone know how to hide the notch on the second display? I remember during the initial setup of the phone there was an option to keep the notch on the second display but now I can't find it in the settings.
Click to expand...
Click to collapse
I just use a black wall paper with immersive mode from system ui tuner and I don't ever notice the notch on either side.
roaduardo said:
Anyone know how to hide the notch on the second display? I remember during the initial setup of the phone there was an option to keep the notch on the second display but now I can't find it in the settings.
Click to expand...
Click to collapse
I remember this option as well. You'd think you would have the option in settings again...i can't find anything weird.
S20 Advanced Lockscreen on Play Store
S20 Advanced Lockscreen on Github
Download size: less than 1MB
Requires root.
This app will switch to 48hz when screen is locked and to 120 when screen is unlocked.
Battery saving.
Added version 1.1:
App totally reworked.
Fixed crashes.
Removed toggle.
Much easier to use.
How to disable the notification:
pham_dang:
" I think he meant when there is a notification coming --> your screen turns on = it immediately starts the high refresh rate (presumably you set it at higher than 60hz). Also when never you use Always on display, although it seems that just the clock or some notifications are showing on a completely black screen, the screen still has that high refresh rate (because you set it system-wide). What this app does is forcing the everything shows in the lockscreen and AOD to keep the refresh rate at 48hz (no matter what refresh rate you set your system at). Hope this cools down the heat guys "
Simple explanation:
-pressing power button while screen is unlocked will trigger 48hz.
-pressing power button while screen is locked and mostly black will trigger 120hz.
-anything that happens after pressing the power button (while unlocked) will be displayed in 48hz (AOD,charging status,notifications,call UI,etc).
TO DO:
Add settings so the user can choose the refresh rate to be set on SCREEN_ON (if asked).
I'm fairly sure that Samsung has 120hz implemented to be dynamic by default. 120hz on lineage feels very different because we don't have any of their OneUI parameters.
Just a hunch, I haven't really taken apart the OneUI ROMs.
ChongoDroid said:
I'm fairly sure that Samsung has 120hz implemented to be dynamic by default. 120hz on lineage feels very different because we don't have any of their OneUI parameters.
Just a hunch, I haven't really taken apart the OneUI ROMs.
Click to expand...
Click to collapse
The only way I could test this is by running one of my apps that reads the refresh rate from Android Studio while screen is off.The refresh rate remains the same when screen is closed.If 120 is set in settings,120 is always set (nothing dynamic).
I'm sure it feels better on your ROM.
TheViciousGames said:
The only way I could test this is by running one of my apps that reads the refresh rate from Android Studio while screen is off.The refresh rate remains the same when screen is closed.If 120 is set in settings,120 is always set (nothing dynamic).
I'm sure it feels better on your ROM.
Click to expand...
Click to collapse
So do you have all you work combined in one app now?
Nope
The GitHub repository doesn't contain any code. It's just readme.md file. Can you share the code?
Edit: Sorry I missed it. Thanks for the app.
vignesh188 said:
The GitHub repository doesn't contain any code. It's just readme.md file. Can you share the code?
Click to expand...
Click to collapse
Hello,sure.The code is there,pay attention to what is written in readme file "Full project can be found on master branch."
https://github.com/TheViciousGames/S20-Advanced-Lockscreen-ROOT/tree/master
Fixed app crashes.The app will no longer crash after enabling the service.
"Context.startForegroundService() did not then call Service.startForeground()" this was the error encountered.It's very common on stackoverflow.Finally fixed it.
If someone else has this problem,it was pretty easy to fix,all I had to do was to create a notification channel and a notification builder with an id higher than 0,basically creating a notification for the service.
New version will be released later today or tommorow.
Without root works?
Taz2016 said:
Without root works?
Click to expand...
Click to collapse
It doesn't,I'm sorry!
I was so tired last night that I uploaded the old version again.I'm sorry,it should update now on Play Store.
Today I'll upload 2 videos:
-how to disable the notification for this app
-48hz while screen off proof
*I keep saying lockscreen but it's about while the screen is off.My bad*
Is it possible by using adb?
Theo1218 said:
Is it possible by using adb?
Click to expand...
Click to collapse
I mean..you can change to 48hz using ADB but you cannot do that automatically while screen is off.
You would have to run the command manually (to 48 and to 120) 100 times a day,I think you do not want that
TheViciousGames said:
It doesn't,I'm sorry!
Click to expand...
Click to collapse
you can try something like that with bixby routines but just changing to 60hz
But, may I ask, what is the point of changing the refresh rate of the screen when it is off? I mean afaik when it is off, it already refreshes at 0Hz because, well, it is off.
davenasc said:
you can try something like that with bixby routines but just changing to 60hz
Click to expand...
Click to collapse
Right,you could probably do that but I'm always debloating everything and 48hz is lower.
stefan243546 said:
But, may I ask, what is the point of changing the refresh rate of the screen when it is off? I mean afaik when it is off, it already refreshes at 0Hz because, well, it is off.
Click to expand...
Click to collapse
You're wrong,you probably wanted to say 0 FPS and not 0 Hz.Changing this helps with AOD,clock,notifications,etc,that's when the display is not really off.
EDIT:
I meant 1 FPS,because nothing is moving.
How does it save battery when the screen is off... the screen isn't refreshing at 120hz because its off already? Makes no sense to me?
kevinireland11 said:
How does it save battery when the screen is off... the screen isn't refreshing at 120hz because its off already? Makes no sense to me?
Click to expand...
Click to collapse
You keep asking the same questions all over again. When the screen is off it still runs as a120hz screen. You could research how that works.
I tried these 2 modes:
settings put secure display_cutout_hide_notch 1
settings put system op_camera_notch_ignore 1
Nothing worked.
Reason: OS cuts out more pixels than actual cutout killing my useful space. (verically and horizontally).
I want OS to set cutoit to NONE as if there is no cutout.
ALTERNATIVE: How to set custom size cutout without root?
Seems it's a complete hit or miss depending on the phone manufacturer and even model.
I have 2 Note 10+'s, one running on 9, the newer on 10. The both look and behave almost identically though. Under the hood though it becomes apparent Samsung went to great lengths to accomplish this on the Q variant. The Q variant has dozens of new small system apks to achieve this. They don't appear to reduce battery life or performance at all.
Then I saw this. It's nuts. Be glad you don't have that phone!
I'm pretty sure there is an option in developer options.
To enable just go to about phone find build version and spam tap it around 10 times then go to dev options and it "should" be there
If it's a samsung, it might be hidden. But My old ANDR11/OneUI3.1 device shows it.
JaydenDev said:
I'm pretty sure there is an option in developer options.
Click to expand...
Click to collapse
The Problem is, in Dev.options I see "Default, Corner, Double (Top&Bottom), Narrow (narrower but taller)".
I don't see None option. Usually if you don't, you stillmight find that in hidden Engineer Menu but that is too much of a hassle for a possibility.
AjvarXX said:
The Problem is, in Dev.options I see "Default, Corner, Double (Top&Bottom), Narrow (narrower but taller)".
I don't see None option. Usually if you don't, you stillmight find that in hidden Engineer Menu but that is too much of a hassle for a possibility.
Click to expand...
Click to collapse
Setting it to none would cause lots of issues I believe.