Related
I`ve been looking everywhere to find a solution but didn`t found one. To be more precise, both sensors (proximity and light) work occasionally,sometimes they work just fine and then suddenly stop working.
I`m using Andro Sensor to check the sensors and there is "Waiting for event" message for both light and proximity.
I don`t think it`s a hardware problem as they were working when bought the phone and they still work occasionally.My phone is rooted and i`m on latest ARHD now with Sebastian kernel.Maybe someone knows how to fix this as it`s very annoying (automatic brightness and capacitive backlights not working because of this as well).Any help would be much appreciated.
Had that problem to,
After a lot off searching i found this.
Enter the line in your build.prop at the botten
ro.mot.buttonlight.timeout=0
Then reboot 2x
Worked for me.
stillbeer said:
Had that problem to,
After a lot off searching i found this.
Enter the line in your build.prop at the botten
ro.mot.buttonlight.timeout=0
Then reboot 2x
Worked for me.
Click to expand...
Click to collapse
How exactly can i do this?I`m sorry but i`m not a pro so not sure where and how to do this.
dzhoshkun said:
How exactly can i do this?I`m sorry but i`m not a pro so not sure where and how to do this.
Click to expand...
Click to collapse
You have to have root and es fileExplorer.
Set system to rw and goto system/build.prop
Open with text editor and ad the line at the bottem of the text.
stillbeer said:
You have to have root and es fileExplorer.
Set system to rw and goto system/build.prop
Open with text editor and ad the line at the bottem of the text.
Click to expand...
Click to collapse
I`m in build.prop now.But just before i will add the line will this make the proximity and light sensor work as well?or this will only light up capacitive buttons when unlocking the phone?
dzhoshkun said:
I`m in build.prop now.But just before i will add the line will this make the proximity and light sensor work as well?or this will only light up capacitive buttons when unlocking the phone?
Click to expand...
Click to collapse
Worked for both for me.
Have to restart 2x tho.
stillbeer said:
Worked for both for me.
Have to restart 2x tho.
Click to expand...
Click to collapse
Hopefully it will work.
So i just need to add the line at the bottom of text in buil.prop (or i need to make some changes to an existing line) ?
Sorry to be a pain.
dzhoshkun said:
Hopefully it will work.
So i just need to add the line at the bottom of text in buil.prop (or i need to make some changes to an existing line) ?
Sorry to be a pain.
Click to expand...
Click to collapse
Just ad it ,hopefully it Works for you !
It was working partially (only proximity,not capacitive lights) after two restarts but it`s not working anymore.I have re-flashed the ROM and repeated the process but no response from both sensors.
dzhoshkun said:
It was working partially (only proximity,not capacitive lights) after two restarts but it`s not working anymore.I have re-flashed the ROM and repeated the process but no response from both sensors.
Click to expand...
Click to collapse
Sorry to here that,i am suffering the same torture.
Still no solution for this problem then...
Tried booting in totaal dark ?
Worked till next boot for me..(after reset)
Suffering the same problem, tried to solve it via the method in build.prop but nothing has changed
Does anyone have afix for this issue yet? I am suffering from the same problem running the 3.33 firmware and Cyanogenmod 9.1 final.
Hi guys, apologies if this has already been discussed elsewhere. I've been using the Mate 9 for a couple of days now and I've noticed the touch screen sensitivity can sometimes be unresponsive. There has been a number of times where I've been on a browser or app and had to click on a link/button at least twice before it responds. It's the same when I click on the Settings button at the top of the notification panel and other areas such as the settings page.
I thought it was just me but I've gone back to my Nexus 6P and iPhone 6s to test, and there is a notable difference.
Has anyone else experienced this? It almost seems like Huawei have intentionally done this as the touch sensitivity elsewhere, i.e. lock screen, seems to work just fine.
Does anyone know if this a known issue and is it likely to be fixed?
Thanks in advance.
Same issue here I believe it has been fixed with a firmware update which has yet to land on my UK model
I sometimes experience some unresponsiveness as well, but told myself maybe it's due to the screen protector? Curious to see if others who took off their screen protector experience this same problem.
It's very minor though, for me.
I know the update was supposed to help and did but I just found a pressure sensitivity setting that allowed me to change the sensitivity which made a big difference IMO. I installed Quick Shortcut Maker and found it under settings. Made the shortcut and pressed it and voila I could decrease the pressure needed to respond.
rndchef said:
I know the update was supposed to help and did but I just found a pressure sensitivity setting that allowed me to change the sensitivity which made a big difference IMO. I installed Quick Shortcut Maker and found it under settings. Made the shortcut and pressed it and voila I could decrease the pressure needed to respond.
Click to expand...
Click to collapse
Are you rooted? Because it tells me that access is denied.
Sammath said:
Are you rooted? Because it tells me that access is denied.
Click to expand...
Click to collapse
No. Stock. I never saw anything similar to that. Installed app. Added shortcut to Pressure Sensitivity and then opened shortcut and moved slider all the way to the left to decrease pressure required.
rndchef said:
No. Stock. I never saw anything similar to that. Installed app. Added shortcut to Pressure Sensitivity and then opened shortcut and moved slider all the way to the left to decrease pressure required.
Click to expand...
Click to collapse
Maybe it's the firmware I'm on MHA-L29C432B158
Yes it does exist AFTER removing screen protector.
Mine is too the point I may return it even thou I think it has a better camera than Samsung and LG
I saw a couple posts/articles about the faked corner rounding on the Pixel 3, and the Pixel 2 XL apparently did it as well. Is there any way to turn this off? I searched the forums but couldn't find anything.
ggmask said:
I saw a couple posts/articles about the faked corner rounding on the Pixel 3, and the Pixel 2 XL apparently did it as well. Is there any way to turn this off? I searched the forums but couldn't find anything.
Click to expand...
Click to collapse
Wow, that's interesting. It would be cool to turn that off.
I noticed there is a few interesting apps on the phone in Titanium Backup:
- Corner Cutout 1.0
- Double Cutout 1.0
- Tall Cutout 1.0
I tried disabling them, but it didn't seem to make any difference that I could tell.
ggmask said:
I saw a couple posts/articles about the faked corner rounding on the Pixel 3, and the Pixel 2 XL apparently did it as well. Is there any way to turn this off? I searched the forums but couldn't find anything.
Click to expand...
Click to collapse
They're not fake really, as much as just different. The screen itself has rounded corners, and the OS just makes them slightly more rounded, probably so they can be anti-aliased and look smoother. If you watch carefully during boot, you can see when they go from hardware-rounded to software-rounded.
CSX321 said:
They're not fake really, as much as just different. The screen itself has rounded corners, and the OS just makes them slightly more rounded, probably so they can be anti-aliased and look smoother. If you watch carefully during boot, you can see when they go from hardware-rounded to software-rounded.
Click to expand...
Click to collapse
Right, that's exactly what this thread is about... using software to artificially add rounding to the screen = faking, right? I'd like to disable that.
ggmask said:
Right, that's exactly what this thread is about... using software to artificially add rounding to the screen = faking, right? I'd like to disable that.
Click to expand...
Click to collapse
Gotcha. They do look better anti-aliased, though, IMO. When I first powered mine on, I was watching it boot and thought, "Woo, those corners don't look very smoo...oh, okay they're smoothing them in software."
Well if you figure it out I'd love to know. I personally feel the normal unaltered cornes would look better. Doesn't really bother me alot, but would still like to try it out at least.
cambunch said:
I noticed there is a few interesting apps on the phone in Titanium Backup:
- Corner Cutout 1.0
- Double Cutout 1.0
- Tall Cutout 1.0
I tried disabling them, but it didn't seem to make any difference that I could tell.
Click to expand...
Click to collapse
Those apps are for adding a fake notch, even for the Pixel 3. You can see notch settings in the developer options.
Hi,
Still no way to modify the corner shape?
I'd love to get the shape we see on the preboot screen, can't stand those over rounded corners...
On a rooted phone there is obviously a way to change it.
Any idea?
Thanks!
One of the things I noticed is that using the command "wm overscan" with proper values will push the rounded corner overlay off the screen showing the true corners. This has some obvious drawbacks, but interesting to see it working with the phone booted up fully.
cambunch said:
I noticed there is a few interesting apps on the phone in Titanium Backup:
- Corner Cutout 1.0
- Double Cutout 1.0
- Tall Cutout 1.0
I tried disabling them, but it didn't seem to make any difference that I could tell.
Click to expand...
Click to collapse
They are the display cutouts made for notch displays.. try turning one on in developer options.
The Navigation Gestures app gets you halfway there. Hiding the nav bar and using the recommended settings for a hidden pill (so you're just swiping at the bottom edge of the screen) uses all the pixels on the Pixel 3, which reduces the radius of the corners. I'm asking in their Telegram channel whether there's possibly a way to do this on the top of the screen, hoping one of the devs would know.
Ezrem said:
The Navigation Gestures app gets you halfway there. Hiding the nav bar and using the recommended settings for a hidden pill (so you're just swiping at the bottom edge of the screen) uses all the pixels on the Pixel 3, which reduces the radius of the corners. I'm asking in their Telegram channel whether there's possibly a way to do this on the top of the screen, hoping one of the devs would know.
Click to expand...
Click to collapse
See my post a few above yours. They are using the overscan options, which has its drawbacks. Some things won't display properly, and if you enable it for the top of the phone you will never see your statusbar.
Found this on reddit (thanks to "jyapayne"):
adb shell settings put secure sysui_rounded_size 1
adb shell settings put secure sysui_rounded_content_padding 5
First line is the corner "roundness" and second line ist the padding of the status-bar elements to the edge.
Works fine for me!
onkelhai said:
Found this on reddit (thanks to "jyapayne"):
adb shell settings put secure sysui_rounded_size 1
adb shell settings put secure sysui_rounded_content_padding 5
First line is the corner "roundness" and second line ist the padding of the status-bar elements to the edge.
Works fine for me!
Click to expand...
Click to collapse
This is the answer we've been looking for! I changed just the first setting and it looks great.
Is there any downside to doing that? Is it going to be frowned upon by Safetynet or anything?
onkelhai said:
Found this on reddit (thanks to "jyapayne"):
adb shell settings put secure sysui_rounded_size 1
adb shell settings put secure sysui_rounded_content_padding 5
First line is the corner "roundness" and second line ist the padding of the status-bar elements to the edge.
Works fine for me!
Click to expand...
Click to collapse
Great, thanks! Default on P3 is 26
CSX321 said:
Is there any downside to doing that? Is it going to be frowned upon by Safetynet or anything?
Click to expand...
Click to collapse
Doesn't require root or anything. It's essentially just configuring a setting via command line that lacks a user-interface option to adjust it.
Bingley said:
Great, thanks! Default on P3 is 26
Click to expand...
Click to collapse
I have found that setting it to 18 is perfect. It gives the smoothness of the anti-aliasing from the software with the radius as close to the size of the actual hardware screen corner.
onkelhai said:
Found this on reddit (thanks to "jyapayne"):
adb shell settings put secure sysui_rounded_size 1
adb shell settings put secure sysui_rounded_content_padding 5
First line is the corner "roundness" and second line ist the padding of the status-bar elements to the edge.
Works fine for me!
Click to expand...
Click to collapse
THANK YOU !!!
I've been looking for such a trick since I get my Pixel.
Way better now
onkelhai said:
Found this on reddit (thanks to "jyapayne"):
adb shell settings put secure sysui_rounded_size 1
adb shell settings put secure sysui_rounded_content_padding 5
First line is the corner "roundness" and second line ist the padding of the status-bar elements to the edge.
Works fine for me!
Click to expand...
Click to collapse
Thank you so much! Such a small change makes such a big difference. I set both values to 1 for now. I don't notice the aliasing and would rather have the extra screen real estate.
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 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