Related
You can increase the density (sort of like changing monitor resolution) on your screen by simply changing the build.prop file. This gives you more viewing area on your screen. The build.prop file contains many user variables that are editable and one of them is the LCD Density. The lower the number, the higher the resolution. The default value is 240, but by simply changing it to 200, you can increase the resolution and see more emails in your email app, more app listings in the market, more room for widget alignment, crisper graphics, and much more!
UPDATE 03/25/2011: ADDED SCREENSHOTS! (finally)
PERMANENT ROOT SOLUTION:
now that we can do perm root, you can permanently change this by modifying your build.prop file located /system/build.prop. look for ro.sf.lcd_density and modify the number and save and reboot.
Recommended value is 200, though many users like 190. If you are unsure what you like, please try TEST MODE shown below!
Please be sure to download Spare Parts from the Market, and disable Compatibility Mode in the app. This will fix many, many apps from not displaying full-screen, however there are some apps that will not re-size.
This works really well if you pair it with something like Launcher Pro or ADW.Launcher, where you have control over rows/columns and resizing widgets.
Easiest Method -- Go to Market and download one of the LCD Density apps. Search "LCD Density."
Phone-Only Method:
You can use Root Explorer, or any text editor like notepad++ or text edit.
1. Open a File Manager and locate /system/build.prop
2. Make sure "/system" is mounted as R/W (in Root Explorer, click the Mount R/W button at the top.)
2A. MAKE A BACKUP!
3. Open and Edit the file.
4. Find ro.sf.lcd_density=240 and change it to desired value (recommend 200 or 190 for G2).
5. Save the file.
6. Exit and Reboot!
Click to expand...
Click to collapse
If you use a separate text editor, just copy the file to your SDCard, edit it there, and move it back and overwrite the original. I recommend backing up the original just-in-case.
ADB Method:
at the cmd prompt:
1. adb pull /system/build.prop
2. Go to SDK / Tools folder and open build.prop in a text editor (recommend WORDPAD for Windows).
3. Find ro.sf.lcd_density=240 and change it to desired value (recommend 200 or 190 for G2).
4. Save & Exit
5. go back to cmd prompt and type: adb shell mount -o remount,rw /dev/block/mmcblk0p25 /system
6. type: adb push build.prop /system/
7. exit and reboot phone!
Click to expand...
Click to collapse
[Test Mode]
If you just want to play around with the setting for test, you can do something similar to the temp-root method shown below.
Open Terminal Emulator from your phone or use adb shell from your computer:
type: setprop qemu.sf.lcd_density 200 (or 190,etc)
press enter.
type: busybox killall system_server
press enter.
it will reboot quickly with your new display. Just reboot and it'll go back to stock. Once you find something you like, you can edit the real build.prop file.
---------------------------------
[original mod / pre-perm-root]
Below is for use with Visionary temp-root app.
This is basically taken from the LCD Density Changer app and applied to visionary.sh
You can increase the density (sort of like monitor resolution) on your screen by simply changing the build.prop file. Unfortunately, since we have temp-root only, it'll revert back. The LCD Density Changer - Free app lets you modify it without editing the build.prop and uses a hot boot to apply changes...
I wanted to automate it into startup with Visionary so here's what you can put into your visionary.sh file without even having the app:
Code:
setprop qemu.sf.lcd_density XXX #change XXX to 200, 190, etc
busybox killall system_server
Example Visionary.sh script is found on Post 51. This script also contains commands for Ad Block and Overclocking which can be found in separate threads on the forum.
I use "200" for the XXX density. Some people below mention 190 as their favorite number to use. 240 is the default!
note #1: killall command will do a hot reboot of your system.
note #2: you do not need to download the app to do this. you just need visionary app from Modaco/Paul O'Brien, which is on the market.
Here are some written instructions from V1R3Z on Page 3 of this thread if you do not know how to create and push visionary.sh to your device:
http://forum.xda-developers.com/showpost.php?p=8962877&postcount=27
update 10/30:
added mounting to read/write for /system and /data to the script for users who did not have it already in their script. also some people prefer using 190 as oppose to 200.
update 11/02:
removed mounting for the /data folder as it is unneccessary. make sure you use a proper text editor and save in a format the phone can read. it's probably a better idea to make the script on the phone than in windows.
credit goes to appelflap and jdsemler who found these things.
Hey, I gave this a shot but didn't notice a difference. Do you run any other commands in you visionary script? Do you put this at the end?
Update
Checked my build.prop, still set to 240. Never used the setprop command, but notice the property in build.prop doesn't have qemu.
Sent from my T-Mobile G2 using XDA App
I find 190 to work best.
mckinlk said:
Hey, I gave this a shot but didn't notice a difference. Do you run any other commands in you visionary script? Do you put this at the end?
Update
Checked my build.prop, still set to 240. Never used the setprop command, but notice the property in build.prop doesn't have qemu.
Sent from my T-Mobile G2 using XDA App
Click to expand...
Click to collapse
Hi - It doesnt modify the build.prop at all actually. I also have some other commands in my script to control adfree and setcpu, but perhaps adding these commands at the beginning will help:
Code:
su
mount -o remount,rw /dev/block/mmcblkp025 /system
mount -o remount,rw /dev/block/mmcblkp025 /data
Very nice. I just added a gscript to run it. It works like a champ.
Slows down g2 when uninstalled everything was back to normal.
Sent from my T-Mobile G2 using XDA App
I added the r/w to the /data and removed a line that killed the launcher after uninstalling bloatware. One of those steps did the trick. I love it at 190. I was so frustrated with how the resolution was better than the G1 but didn't really give me the impression with everything blown up.
Thanks for the details.
Sent from my T-Mobile G2 using XDA App
mckinlk said:
I added the r/w to the /data and removed a line that killed the launcher after uninstalling bloatware. One of those steps did the trick. I love it at 190. I was so frustrated with how the resolution was better than the G1 but didn't really give me the impression with everything blown up.
Thanks for the details.
Sent from my T-Mobile G2 using XDA App
Click to expand...
Click to collapse
Cool. I'll update the OP with the read-write commands.
Love the mod, thanks for the tip
any idea why after the hot reboot it causes sim checker light to email my location as if someone stole my phone and put in there sim?
Noticed the stolen report too with the kill launcher command. Must mess with the sim card negotiation and trigger something.
Sent from my T-Mobile G2 using XDA App
Forgive the noobisness, but are the icons in the app drawer supposed to look like complete ass with it set @ 190?
Trial and error results
That's what I noticed as well. ADW looks like crap and that's no lie. Some things aren't using the entire screen anymore.
One thing I've learned when it comes to having Android on the HD2 with a lcd_density of 180 is that you have to unmark compatability mode within spare parts. Since we g2 users don't have that app, we're kinda stuck.
BUT WAIT! Spare parts is on the market. Install it and then do an adb shell...
su
busybox killall system_server
AND IT DIDN'T WORK!!!
So I guess I'm gonna have to try a different density other than 190...
UPDATE:
changing the density to 200 made ADW look fantastic. Some apps still don't use the entire screen. Maybe rebooting entirely will help and actually adding these lines to visionary.sh instead of just running the commands through a shell...
UPDATE2:
Rebooting did nothing. Spare parts doesn't do anything so my question would be How do we get all apps to span across all of the screen?
My example is Weather and Toggle Widget with the Weather Forecast Add-on, the weather animation uses only half of the screen...
minotauri said:
I also have some other commands in my script to control adfree and setcpu
Click to expand...
Click to collapse
Off topic, I know but what are the commands you use for them?
This would help out a great deal!
UPDATE3:
Something went fishy. visionary.sh doesn't seem to want to work. This is what I have,
su
mount -o remount,rw /dev/block/mmcblk0p25 /system
mount -o remount,rw /dev/block/mmcblk0p25 /data
insmod /data/local/vision_oc.ko pll2_l_val=74
setprop qemu.sf.lcd_density 200
busybox killall system_server
Click to expand...
Click to collapse
Basically, it's everything in the OP with the addition of the oc command.
It was working just fine in the beginning but now it doesn't do the hot reboot unless I manually type killall system_server in adb shell or terminal emulator but oc goes through no problems either way...
I would like some clarification on something...
Is it mmcblk0p25 or mmcblkp025 cause 0p25 is what I did and it worked...
FINAL UPDATE:
So I'm really not sure what I did but with a lot of trail and error, I was able to come up with a working script...
su
insmod /data/local/vision_oc.ko pll2_l_val=74
mount -o remount,rw /dev/block/mmcblk0p25 /system
mount -o remount,rw /dev/block/mmcblk0p25 /data
setprop qemu.sf.lcd_density 200
busybox killall system_server
Click to expand...
Click to collapse
don't edit it in anyway or it won't work. I don't know why...
Sorry for floodin the thread with such a massive post but maybe it will help others. But I still want to know how to add adfree into visionary.sh so I don't have to start that up every time to0. If anyone want to throw me the command you used, I will guinea pig it into the script I just created and post it for the for everyone as well.
It's off topic but at least it will be out in the open cause I didn't see it anywhere. I know how to search...
Thank you all!
Launcherpro @ 200 looks amazing. Will keep it like that, it's like a whole new phone.
edit: thinking it's just a stock launcher problem with rendering, cause stock launcher looked like crap @ 200 too
Can someone post a couple of screen shots?
I'm using launcher pro @ 205. Looks amazing, everything aligned. I think you also need to play with your desktop columns and rows. I'm using 5x6 and manually resized widgets.
Thanks a ton to the OP. I absolutely LOVE high resolutions. Im using a density of 190 on ADW, and it looks fantastic! For some strange reason 200 and 210 were crashing the phone, 190 is running smoothly with no problems/glitches.
Sent from my overclocked T-Mobile G2 using XDA App.
Launcher Pro @ 190. This works great. Thank you.
Sent from my T-Mobile G2 using Tapatalk
I use launcher pro. but I know adw works too because I used that in the past with cyanogenmod on nexus one. you will want to change to column and row settings to full optimize the new screen density.
Sent from my T-Mobile G2 using XDA App
I can't get it to work I pushed the script and it was successful I can see it in terminal but it's not setting my density.
PlatinumMOTO said:
I can't get it to work I pushed the script and it was successful I can see it in terminal but it's not setting my density.
Click to expand...
Click to collapse
Reboot device and run visionary...
Hi guys,
Is it possible to have a shortcut icon on homescreen that powers the phone off. I have a protective gel case on my Desire and its a pain in the a**e having to long press it through the case and then select power off and then ok to confirm.
I am using quick boot app which is excellent but no power off option with it. Just reboot, recovery and quickboot. Have already requested Dev to add the function but not hopefull.
When long pressing the power button a menu pops up right? Is it possible to invoke that power menu in another way? Perhaps with a shortcut?
Surely its not rocket science to be able to click an icon and the phone powers off???????
Edit: see last post for solution
??
C'mon guys, someone must know a way to achieve this. Otherwise, whats this forum for?
5 minute job to knock up a zip patch file or a simple app for someone who know's what their doing. I feel a lot of people (certainly those using protective cases) would find such an app or patch (for rooted users like me) very welcome.
I would happily do it for someone else.
you can power off with the command
reboot -p
Click to expand...
Click to collapse
you can use gscript (light version available on the market for free.) to add a shortcut to that command on the homescreen.
You will need root access, i think.
??
C'mon man, you must know how to show some sort of gratitude or give some sort of feedback. Otherwise, whats this forum for?
5 minute job to go on your computer (or phone) and post a reply for someone who know's what their doing. I feel a lot of people (certainly those who help others) would find a simple thank-you very welcome.
I would happily do it for someone else.
My point is if you can't be arsed to reply to your own thread in 24 hours why bump it after a day with no reply?
reboot controll widget
Mercianary,
Don't get your knickers in a twist
Only seen your reply this morning. Thanks for your suggestion - gscript. Gonna try it out later today. Will post back.
Cheers dude.
What....these feelings...I feel bad now...sorry.
That widget looks like it would do the job great. Just depends of your stingy like me and wouldn't pay 87p for an app when I can do the same for free.
Just installed gscript and run a reboot -p script but it doesn't work
I get a stderr: not permited error
I am rooted and have the superuser app
Any ideas??
Try
su
reboot -p
Edit: that wont work. Make sure you tick 'needs su' box in gscript when you make the script. Should make it work
Got su box checked.
Tried
su
reboot -p
Tried re-installing gscript.
Tried reboot
Is it not working because, although I am rooted with unrevoked 3.2, I still have s-on? I wonder. Or, is it because reboot is not allowed to be run as a script???
But I have superuser app. Puzzled. Any more suggestions as I really want to get this working. By the way scripts not requiring su run fine.
http://www.appbrain.com/app/quick-boot/com.siriusapplications.quickboot
Hello
Yes I am already using quick boot but it doesn't have the option to simply power off the phone. Only reboot, recovery and bootloader. I have asked the Dev to add this option as others have also asked but not hopeful anytime soon.
All I want is a homescreen shortcut that powers off the phone. Simples!
Why am I getting not permitted error messages when trying to run following from gscript.....
reboot -p
It is set to use superuser but gives the error. WHY!!!!
Try running the command from a terminal emulator. If that works we know gscript is the problem (in which case I can tell you a work around).
If it still doesn't work maybe your rom doesn't support it (I use cyanogenmod and it works fine for me.).
Edit: double check gscript is set to 'allow' in superuser.
Su
Shutdown
Works in terminal.
Sent from my Evil Lair using Doomsday Device
Ik Desire said:
Su
Shutdown
Works in terminal.
Sent from my Evil Lair using Doomsday Device
Click to expand...
Click to collapse
Not for me. It must be different on different roms.
Are you using a sense rom?
By terminal emulator, do you mean an adb shell from a command prompt on P.C........Or do you mean something that runs on the phone?
Edit: Ran Alpharev last night and am now s-off All went smoothly. Have installed root explorer and was wondering what file/directory permissions I need to change to be able to execute scripts?
btw, thanks for your suggestions Mercianary and IK Desire
Edit: installed Android Terminal Emulator and ran
su (it asked for superuser permision and i allowed)
#shutdown (phone powered immediately off but would not switch back on - had to pull battery)
#reboot -p (same as above)
Totally stumped and baffled.
mercianary said:
Not for me. It must be different on different roms.
Are you using a sense rom?
Click to expand...
Click to collapse
Leedroid 2.2e. Using terminal emulator on phone. I have the same problem (have to pull battery before rebooting). But previously this was not the case.
Sent from my Evil Lair using Doomsday Device
Update
Have found a solution (sort of!). Have installed busybox and have created a gscript script as follows....
busybox poweroff -d 10 -f
This works and powers the phone off after 10 seconds. The reason for the 10 second delay is to give the system enough time to unmount filesystems and stop services. An ordered shutdown if you like.
Thing is....Is this what actually happens? I mean the poweroff command in busybox doesn't go through the init system. So, is it a "clean, ordered" powerdown???? It switches back on ok afterwards and everything seems to work.
But the question is am I risking corrupting the filesystem by shutting down in the way?
If I flash bacon bits will this wipe my phone? Or is this a no wipe type of thing?
It won't wipe your phone.
Thanks for the help, I will flash this later.
what IS baconbits?? i keep hearing about it?
konoplya said:
what IS baconbits?? i keep hearing about it?
Click to expand...
Click to collapse
Seriously?
http://forum.xda-developers.com/showthread.php?t=834565
.A.J. said:
Seriously?
http://forum.xda-developers.com/showthread.php?t=834565
Click to expand...
Click to collapse
yeah i saw that thread. thats foreign language to me. i was looking for more of a simpler answer.
I think the only thing that'll interest you is:
1) Comes with an overclock module so that you can adjust how fast or slow the CPU runs. Use SetCPU to have full functionality over your CPU
2) The LED light at the top of your phone will blink when you have a notification in conjunction with the trackball lighting up.
3) SuperUser is needed to ensure certain apps get the permissions needed to run and that what you want to run requires administrative privileges ("root" permissions) is ran past you.
BusyBox and ro.secure=0 is something that escapes me, but I know BusyBox was needed for Titanium Back-up. For what, I haven't figured that out yet.
BusyBox is also required for MetaMorph..
Busybox is a bunch of command line utilities rolled into one neat package, is the simplest way I can explain it. ro.secure=0 lets you run 'adb remount' on your computer for r/w access to your phone.
EDIT: Skip to the bottom EDIT for the short version..
Preamble: I searched for a fix to this recently and over the past 10 months and haven't seen any real solutions to this. Most people have probably experienced this issue at some time flashing roms, especially those people running gapps-free Android :highfive: such as myself. A band-aid for fixing this is running gapps' SetupWizard and/or CM's CMAccounts, I started adding CMAccounts.apk to /system/app some months ago to fix this. I was never satisfied with this workaround though since it doesn't narrow down the actual problem, and I really like sticking to the AOSP experience, open-source, no Stasi-esque permissions, and without the need to taint my installation just to set it up (setupwizard does a lot more than you might think).
Using some additional skills I didn't have 6 months ago, I finally isolated the issue to the SQL database /data/data/com.android.providers.settings/databases/settings.db, table global, value name device_provisioned. It is set to "0" by default which leads to all these ridiculous problems, and setting it to "1" + a reboot fixes all of these problems for me. Setting it back to "0" + reboot breaks everything again, back to "1" fixes, provision.apk present or removed.. I searched for (sqlite3 dump | grep) lots of other provision and setup value differences... tested this a lot.
!!!BACKUP /data/data/com.android.providers.settings/databases/settings.db before attempting this. Use 'busybox cp -p /data/data/com.android.providers.settings/databases/settings.db Your_Backup_Location' to copy and keep correct permissions on it. I would do a nandroid backup maybe anyway. This should be harmless or very helpful, but it's a su'd command in depths of /data so ya never know.
A couple simple ways to get this set right since you can't reliably grep'n'sed here: Get a nice free sql-frontend app off fdroid or xda -very handy- and go to the settings.db file, 'global' table, and then find or add "device_provisioned" in the name column and "1" in the value column. Root Explorer has this built in I think. The better way though is to pull up the 'adb shell' terminal remotely or use a terminal emulator from the phone with free && adfree Jack Palevich's Terminal Emulator, Spartacus Rex' Terminal IDE (recommended ...for everything!), anything using a jni_exec java execute emulation command. Also Ghisler's Total commander file manager has a built-in command line for convenient executions (or cool shell-script shortcuts you can make --it was actually the first tasker).
# Enter each command line by line (after '>'):
Code:
>su
>$(which sqlite3) /data/data/com.android.providers.settings/databases/settings.db
>update global set value="1" where name="device_provisioned";
>.quit
>exit 0
# One-liner
Code:
su && $(which sqlite3) /data/data/com.android.providers.settings/databases/settings.db 'update global set value="1" where name="device_provisioned";'; exit 0
Then just reboot, enjoy that home softkey that takes you to your launcher home.. your notification bar that displays your notifications. lol such basic s***.
Hope this can help someone else out as much as it did me. You don't have to use gapps/setupwizard to fix it! I also want to make sure there isn't another rogue SQL.db value. (btw if you happen to read this and have a broken back softkey/button, your problem is likely the lib file /system/lib/jni_latinime.so. Thought I'd throw that out there.)
EDIT: Heres an update short version. I added another sqlite value that needs correcting in ROMs without gapps setup bla installed. Run these commands in terminal emulator or via adb. Just copy and paste, they need to be exact.
Check that the values on the right are "1" when you fire off:
Code:
su -c '"$(whence -p sqlite3)" /data/data/com.android.providers.settings/databases/settings.db '\''select * from global where name="device_provisioned"; select * from secure where name="user_setup_complete";'\'
Otherwise or just to be safe, fire off this wicked one liner(Warning: reboots when finished):
Code:
su -c '"$(whence -p sqlite3)" /data/data/com.android.providers.settings/databases/settings.db '\''update global set value="1" where name="device_provisioned"; update secure set value="1" where name="user_setup_complete";'\'' && sync && fsync /data; sleep 3; svc power reboot'
Done, 1-2 steps.
Great write up and worked perfectly. Any more tips tricks advice or links for non-gapps users?
namtombout said:
Great write up and worked perfectly. Any more tips tricks advice or links for non-gapps users?
Click to expand...
Click to collapse
Yeah man, glad it worked. Cheers to your cojones for trying it!
What I usually do for a no gapp solution is:
-grab the libjni_latinime lib from microgapps cause its needed for the aosp keyboard swipe usually
-use "gapps browser" for Google related stuff like gmaps.
-or use rmaps (this and gapps browser need the maps api, so you gotta pull the google maps framework jar or use the "no-gapps project" hack api /system/framework/*google*jar. Make sure to add the corresponding /etc/permissions/*google*xml files too)
-instead of gmail I use the standard email client of k9
-instead of play I use fdroid, aptoide sometimes, nextwap.net, or mobilism forums, or a lucky patcher cracked Google play. (careful with the non-fdroid ones)
Sorry bout this 6 month late reply, Jesus I gotta watch my posts more closely.
Android 9 added a new feature which allows for the temporary rotation of the screen, with the press of a button would appear when the phone is put into landscape orientation. MIUI for some reason has decided to exclude it, we're at Android 11 and it still doesn't have it. I was wondering if Xiaomi.EU ROM has this feature, or would I have to go with a custom ROM?
do you use tasker? could try the auto-rotate for chosen apps profile found in this thread.
i used it fine for both ROG phone II and this Alioth phone. i just set it for maps, youtube vanced etc.
works great. not sure i'd recommend the other profiles, they may well be device specific
reg66 said:
do you use tasker? could try the auto-rotate for chosen apps profile found in this thread.
i used it fine for both ROG phone II and this Alioth phone. i just set it for maps, youtube vanced etc.
works great. not sure i'd recommend the other profiles, they may well be device specific
Click to expand...
Click to collapse
Cool, this could be a workaround for my issue, just enabling rotation in some apps. I'll try it out, thanks!
It might be a late reply, but in terminal emulator as root you can type this command: "settings put secure show_rotation_suggestions 1" without the quotes and it will enable rotation suggestions when you rotate the screen. You can also use this same command in FKM scripts section and set it to run on boot. If you're not rooted then you must use adb shell on a PC with adb debugging enabled in developer options and use this command: " pm shell settings put secure show_rotation_suggestions 1" without the quotes. After a reboot the setting is disabled again so you have to run the command after each reboot.
pawelmiernik said:
It might be a late reply, but in terminal emulator as root you can type this command: "settings put secure show_rotation_suggestions 1" without the quotes and it will enable rotation suggestions when you rotate the screen. You can also use this same command in FKM scripts section and set it to run on boot. If you're not rooted then you must use adb shell on a PC with adb debugging enabled in developer options and use this command: " pm shell settings put secure show_rotation_suggestions 1" without the quotes. After a reboot the setting is disabled again so you have to run the command after each reboot.
Click to expand...
Click to collapse
THANK YOU SO MUCH! This has always been one of the reasons I hated MIUI, now I finally get to enjoy this feature that MIUI has chosen to hide for some reason!
CharlieMHz said:
THANK YOU SO MUCH! This has always been one of the reasons I hated MIUI, now I finally get to enjoy this feature that MIUI has chosen to hide for some reason!
Click to expand...
Click to collapse
Ikr it's such a useful thing to have!
@pawelmiernik I just registered to say that you are a frigging legend, thank you so much!
Absolutely idiotic that they left out this option somewhere in the settings. Especially when you can reactivate the already implemented button with such a workaround. Ridiculous.
pawelmiernik said:
It might be a late reply, but in terminal emulator as root you can type this command: "settings put secure show_rotation_suggestions 1" without the quotes and it will enable rotation suggestions when you rotate the screen. You can also use this same command in FKM scripts section and set it to run on boot. If you're not rooted then you must use adb shell on a PC with adb debugging enabled in developer options and use this command: " pm shell settings put secure show_rotation_suggestions 1" without the quotes. After a reboot the setting is disabled again so you have to run the command after each reboot.
Click to expand...
Click to collapse
Thanks for this, would like to add that another way of having it persist is to use SetEdit and add show_rotation_suggestions 1 to the secure table. You'll need to give the SetEdit app permissions to write to the secure table. You can do it with root but if you're not rooted you can use adb, just be sure to enable "usb debugging (security settings)" as well.
pawelmiernik said:
It might be a late reply, but in terminal emulator as root you can type this command: "settings put secure show_rotation_suggestions 1" without the quotes and it will enable rotation suggestions when you rotate the screen. You can also use this same command in FKM scripts section and set it to run on boot. If you're not rooted then you must use adb shell on a PC with adb debugging enabled in developer options and use this command: " pm shell settings put secure show_rotation_suggestions 1" without the quotes. After a reboot the setting is disabled again so you have to run the command after each reboot.
Click to expand...
Click to collapse
Just to add on to this, for me, the settings stayed even after a restart, so I didn't need to run it again after reboot.
I think it's because they added this to MIUI 13. I recently bought a POCO F3 and it had it built in. Finally. There is hope in this world.
Weslington9 said:
I think it's because they added this to MIUI 13. I recently bought a POCO F3 and it had it built in. Finally. There is hope in this world.
Click to expand...
Click to collapse
How to turn on this feature, I am on miui13 but can't find it ?