Develop Bugs

[Root] [Guide] How to change your Resolution & DPI on AOSP ROMs

* I am not responsible for bricked devices, displays not working, or your phone melting *
Now with that out of the way, hello! Welcome to my first guide-thingy. As it is my first, I apologise if there is a mistake or if I have left something out, but this process is exactly the process I have used.
Recently I've had a few people ask me about changing their phone's resolution and DPI as said in my signature, so I thought I'd write up a guide for people to use! The ROM I've done this on is the BlissPop AOSP ROM but the process should be similar for most if not all other Custom AOSP-Based ROMs. I am UNSURE if this process works on the stock ROM or any stock-based ROMs.
Prerequisites:
- Root access
- Root File Manager & Explorer (Such as Root Browser or ES File Explorer)
* Root Browser: https://tinyurl.com/aytbttu
*ES File Explorer: https://tinyurl.com/cd4u27q
- NOMone Resolution Changer
* https://tinyurl.com/kjg63jn
- OPTIONAL (For Multi-DPI Patch) Latest AROMA (Now known as Open) GApps Package
* http://forum.xda-developers.com/android/software/pa-gapps-continuation-t3098071
Lets get started!
Firstly, the Multi DPI Patch. It's not essential but allows apps to be properly resized to match your custom DPI, and in the latest Google Apps package it has an option when installing to install a multi-DPI patch for people who are using custom resolutions on their phone. Like me, I'm not using 2560x1440 (Stock 1440p resolution) I'm using 1920x1080 (1080p) resolution @ 370 DPI.
Changing your Resolution & DPI
1. Download NoMone Resolution Changer from the Play Store above (It's free) and grant root access
2a. Open a root file manager (Like Root Browser or ES File Explorer (You have to enable root-access for ES) ) and navigate to the /system folder on internal storage. Find your build.prop at the bottom. Now, you're going to want to create a backup of this file before we do anything as it defines how things work on the phone, so create a copy and move it somewhere safe from being wiped (Like an external SD card)
2b. Click on build.prop and open with a root file browser
2c. Find the line under the #ADDITIONAL_BUILD_PROPERTIES section that says ro.sf.lcd_density=xxx and change 560 (default DPI) to something like 430 if you want the font and stuff to stay the same size or 370 to make it smaller and hit save, grant root-save access if required. Then, open the file with another file manager to verify it's saved and changed. Adjust the DPI to something that you like, but be cautious as not all DPIs work properly (I only know of 370 & 430 that have worked for me). This step may vary depending on how your ROM sets out your build.prop.
3. Set your desired resolution in NOMone Resolution Changer (Mine is 1080x1920, remember to do it backwards so 1080x1920 not 1920x1080 otherwise your phone's GUI will be landscape and not portrait, and will go off the screen)
3b. Set your desired DPI to match the DPI you put into your build.prop file and hit apply (Grant root access if requested). The app will apply your settings and change your screen to match the new settings. It will then prompt you if you'd like to keep these settings, hit yes or no. If you hit yes, it will give you an option to change back the settings after a minute so you can see what the phone looks like at that setting.
*This next step only applies if your ROM has an option to manage the DPI setting itself, like BlissPop does, otherwise skip it*
4. After you've applied your custom resolution and DPI, go to Settings (Yes everything will be massive-sized don't worry) -> Display & Lights -> Scroll down to the bottom, hit advanced Display Settings, and change the LCD Density DPI to match the one you set in your build.prop and NOMone app.
5. Hit yes to reboot or reboot your phone if not prompted.
6. You're done! Your phone should reboot and apply your new resolution and DPI changes.
I have attached some screenshots showing off the BlissPop & Facebook UI at 1920x1080 Resolution & 370 DPI, as well as an example change in the NOMone Resolution Changer App. Lowering the Resolution and DPI is beneficial to those who want to squeeze more stuff onto their screen (it enables lots more text on the screen that isn't really big.) As well as gamers (The lower resolution doesn't strain the GPU as hard.)
If you have any issues, just delete the build.prop you edited from the /system folder in TWRP and copy over the original one you backed up and put it in the /system folder.
Known issues caused by this guide:
- Boot animation may stretch when booting.
- Recent app previews will also be larger for some unknown reason, this is a small side effect however.
Hope this helped!

Now ...again...me....you forgot to mention borked gigantic recents and borked bootanimation on boot.....you should add it to issues list...IMHO
Subbed here as well
/LG-G3/d-855/16Gb/Titanium Black/

m1trand1r said:
you forgot to mention borked gigantic recents and borked bootanimation on boot
Subbed here as well
Click to expand...
Click to collapse
I have added this to the end of the post, thanks.

iDefalt said:
I have added this to the end of the post, thanks.
Click to expand...
Click to collapse
oh...even using 1080p bootanimations doesn't solve that issue....i've never looked deeper into it myself....but tried many workaround w/o succes
/LG-G3/d-855/16Gb/Titanium Black/

I've used this application to lower resolution on my G3 to 1080p but found that the small text and other stuff was blurred because it's disproportionate to the amount of pixels, since 720p would be a more accurate number to downscale to on a 1440p screen (1/2).
Do you notice this "fuzziness"? I forget exactly which DPI I set it to when I did go down to 1080p, but the other thing I realized was that the performance gain was marginal. I did not do long-term battery testing with this, though. So the verdict is still out on whether or not there is any gain there.

xocomaox said:
I've used this application to lower resolution on my G3 to 1080p but found that the small text and other stuff was blurred because it's disproportionate to the amount of pixels, since 720p would be a more accurate number to downscale to on a 1440p screen (1/2).
Do you notice this "fuzziness"? I forget exactly which DPI I set it to when I did go down to 1080p, but the other thing I realized was that the performance gain was marginal. I did not do long-term battery testing with this, though. So the verdict is still out on whether or not there is any gain there.
Click to expand...
Click to collapse
you might not gain much or if any juice on battery....but...performance boost is noticeable on.my side...I forgot how it feels at 1440p ...and switched to for a moment....oh gosh....why do apps take longer to open?....back to 1080p and it flies again...
Oh...you must have set too low dpi to get blury text...I don't even know how that looks like...and if you'd change it to 720p your dpi would be around 220 or something ......
/LG-G3/d-855/16Gb/Titanium Black/

m1trand1r said:
you might not gain much or if any juice on battery....but...performance boost is noticeable on.my side...I forgot how it feels at 1440p ...and switched to for a moment....oh gosh....why do apps take longer to open?....back to 1080p and it flies again...
Click to expand...
Click to collapse
I had tested both normal applications and some 3d games that sometimes bring down fps and neighter seeemd to be any better, but I will have to test this with Bliss as that was some time ago.
m1trand1r said:
Oh...you must have set too low dpi to get blury text...I don't even know how that looks like...and if you'd change it to 720p your dpi would be around 220 or something ......
Click to expand...
Click to collapse
Hmm, you could be on to something. I need to test with your recommended DPI to see if it fixes the blurriness of small text. Thanks!

xocomaox said:
I had tested both normal applications and some 3d games that sometimes bring down fps and neighter seeemd to be any better, but I will have to test this with Bliss as that was some time ago.
Hmm, you could be on to something. I need to test with your recommended DPI to see if it fixes the blurriness of small text. Thanks!
Click to expand...
Click to collapse
some games are badly coded...hence there's no improvement
/LG-G3/d-855/16Gb/Titanium Black/

So I used the recommended settings of 1080p and 370dpi and the blur is minimized but not completely gone. Bearable, though.
I'll be testing out some other performance things and more long-term battery savings. Thanks again for the write-up. Hopefully it will help with people willing to try out different resolutions and DPI's.

xocomaox said:
So I used the recommended settings of 1080p and 370dpi and the blur is minimized but not completely gone. Bearable, though.
I'll be testing out some other performance things and more long-term battery savings. Thanks again for the write-up. Hopefully it will help with people willing to try out different resolutions and DPI's.
Click to expand...
Click to collapse
show me the blur please...my screen of settings and homescreen
Nothing blury here...[emoji41] [emoji106]
/LG-G3/d-855/16Gb/Titanium Black/

m1trand1r said:
show me the blur please...my screen of settings and homescreen
Nothing blury here...[emoji41] [emoji106]
Click to expand...
Click to collapse
Sorry, but this is the kind of thing that cannot be shown on a software level. Screenshots will not work.
The images and text is just not as crisp because since it's not 1:1 with the pixels it will naturally display fuzzy. This is unavoidable but can be lessened by using better ratios (ideally 720p, but that would just be too low) and different DPI settings. If you do not see this yourself then you may lack the eyesight. Again, it's not very noticeable and the positives may very well be more beneficial than having a perfect 1:1 ratio.

xocomaox said:
The images and text is just not as crisp because since it's not 1:1 with the pixels it will naturally display fuzzy. This is unavoidable but can be lessened by using better ratios (ideally 720p, but that would just be too low) and different DPI settings. If you do not see this yourself then you may lack the eyesight. Again, it's not very noticeable and the positives may very well be more beneficial than having a perfect 1:1 ratio.
Click to expand...
Click to collapse
You could try going to 1080p @ 430 DPI. This makes the text similarly sized to the default 560 DPI, only on lower resolution. If you did this, the GPU wouldn't have to work as hard, and your text would still be the original size
But yeah it's worth playing around a bit. I haven't noticed any fuzziness at all at 370 DPI, and I do a lot of reading on my phone.

iDefalt said:
You could try going to 1080p @ 430 DPI. This makes the text similarly sized to the default 560 DPI, only on lower resolution. If you did this, the GPU wouldn't have to work as hard, and your text would still be the original size
But yeah it's worth playing around a bit. I haven't noticed any fuzziness at all at 370 DPI, and I do a lot of reading on my phone.
Click to expand...
Click to collapse
than our sight must be damaged in a way, eh?...LOLZ
/LG-G3/d-855/16Gb/Titanium Black/

If you lower the resolution on any lcd screen made for a specific resolution it will make things fuzzy. You can even do this on your computer monitor.
Everyone should expect this as it is not 1:1, but I still consider it pretty useful.

xocomaox said:
If you lower the resolution on any lcd screen made for a specific resolution it will make things fuzzy. You can even do this on your computer monitor.
Everyone should expect this as it is not 1:1, but I still consider it pretty useful.
Click to expand...
Click to collapse
you really have to look very very very closely to notice anything IMHO
And If that was written somewhere...most people will fall under mass hysteria and take it as granted .....that's a fact....i'm enjoing my huge screen like I did before on 1440p ...it makes no difference for me and side by side comparison with my co-worker's G3 which is all Stock except rooted(by my advice)....makes no difference at all....none, 0,....he didn't notice that I changed anything except THE Beautiful Rom and pure raw power against his Stock G3...so...don't complicate to much....
/LG-G3/d-855/16Gb/Titanium Black/

m1trand1r said:
THE Beautiful Rom and pure raw power against his Stock G3
Click to expand...
Click to collapse
Just two reasons we all love Bliss <3

iDefalt said:
Just two reasons we all love Bliss <3
Click to expand...
Click to collapse
yeah...just two...out of many more
/LG-G3/d-855/16Gb/Titanium Black/

Does it only work for LG G3 in particular? I tried it on my rooted Galaxy S6 Edge and it doesn't seem to work.

Zaberz said:
Does it only work for LG G3 in particular? I tried it on my rooted Galaxy S6 Edge and it doesn't seem to work.
Click to expand...
Click to collapse
The guide is for the G3 running AOSP ROMs.
I suggest you check this out: http://forum.xda-developers.com/galaxy-s6/help/resolution-phone-changed-t3075664

It's look interesting, gonna try this one up. Ty @m1trand1r for your kind answer [emoji3]
Sent from my LG-D855 using Tapatalk

[UPDATE 06/10/19][Guide][Tweaks] for ANDROID phones without root. Fast boot, power sa

HTML:
Hello Good Day everyone.
I am pleased to announced that you can tweak some Android settings without root permissions Yay. Someone can try other phones but this works on my xiaomi mi A3 and A1. BOTH of my phones are not rooted neither are they unlocked. I borrowed my friends J7 prime and got some working there too. Your mileage may vary. It should work the same on most phones. I tried some stuff and this is my findings. Some tweaks require that you Write secure settings through adb. I am not taking responsibility if you try and you damage your phone. Do this at your own risk. Thank you.
NB
If you delete the app or uninstall you lose all your settings.
If you do want to undo changes just delete setting line.
For best user experience use all working tweaks. Or you can choose what you want or do not want it is up to you. Your mileage still may vary.
OTA UPDATES don't affect settings on my phone neither do they conflict with manufacturers settings. There are some new settings line enabled on android properties that made some of my added tweaks on system tables redundant so I just deleted those redundant ones from system table. Will do some further investigating YOU can always COMPARE android properties with the tweaks you are adding to see if you are adding redundant comands. Android is forever improving, rooting is becoming obsolete, for the not pickers, a lot of these tweaks may not be necessary in the future because android might have them as standard but until then this is necessary to get the best out of your phone or to get the things you want and not what Google gives you. Thank you
LETS BEGIN
https://youtu.be/I1EBwRBQAgw
1. Download database editor
https://play.google.com/store/apps/details?id=by4a.setedit22
2. Open settings database editor select system table.
3. Add new settings "ro.config.hw_quickpoweron" >save changes> value at "true"> save changes
Add new Setting "boot.fps" > save changes > value at "25" > save changes
Add new settings > "debug.sf.nobootanimation">save changes> value at "1" >save changes.
4. Reboot phone.
Enjoy faster boot.
You can try other working tweaks below:
1. Display density
display_density_forced "209" trust me on this for mi a3 IDK why but it does. For other phones add whatever you are comfortable with or is recommended.
2.Ring without delay
ring.delay "0"
3.Faster boot under 10 seconds.
boot.fps "25" range from 15 to 30 depending on how fast your processor is.
debug.sf.nobootanimation "1"
4.wifi scan interval
wifi.supplicant_scan_interval "120" increases time between WiFi scans, saves battery and CPU power.
5.power savings
pm.sleep_mode "1"
power_supply.wakeup "enable"
6.Gaming/3d performance.
debug.enabletr "true"
debug.qctwa.preservebuf "1"
dev.pm.dyn_samplingrate "1"
video.accelerate.hw "1"
debug.overlayui.enable "1"
debug.egl.hw "1"
Debug.egl.prifiler "1"
debug.sf.hw "1"
debug.composition.type "c2d"
debug.composition.type "gpu"
debug.performance.tuning "1"
7. Better navigation scrolling speed
windowsmgr.max_events_per_sec "100"
8. Disable fingerprint reader animation.
fod_animation_type "4"
9.disable logcat
Logcat.live "disable"
10. Enhance Sound quality
af.resampler.quality "255"
mpq.audio.decode "true"
11. Internet browsing and download.
net.tcp.buffersize.default "4096,87380,256960,4096, 16384,256960"
net.tcp.buffersize.wifi "4096,87380,256960,4096,163 84,256960"
net.tcp.buffersize.umts "4096,87380,256960,4096,163 84,256960"
net.tcp.buffersize.gprs "4096,87380,256960,4096,163 84,256960"
net.tcp.buffersize.edge "4096,87380,256960,4096,163 84,256960"
net.tcp.buffersize.hspa "6144,87380,524288,6144,163 84,262144"
net.tcp.buffersize.lte "524288,1048576,2097152,5242 88,1048576,2097152
net.tcp.buffersize.hsdpa "6144,87380,1048576,6144,8 7380,1048576"
net.tcp.buffersize.evdo_b "6144,87380,1048576,6144, 87380,1048576"
net.rmnet0.dns1 "8.8.8.8"
net.rmnet0.dns2 "8.8.4.4"
net.dns1 "8.8.8.8"
net.dns2 "8.8.4.4"
net.ppp0.dns1 "8.8.8.8"
net.ppp0.dns2 "8.8.4.4"
net.wlan0.dns1 "8.8.8.8"
net.wlan0.dns2 "8.8.4.4"
net.eth0.dns1 "8.8.8.8"
net.eth0.dns2 "8.8.4.4"
net.gprs.dns1 "8.8.8.8"
net.gprs.dns2 "8.8.4.4"
Note
You can use whAtever dns is faster for u for example cloud share dns1 1.1.1.1 dns2 1.0.0.1
12.Enable GPU Acceleration (avoid enabling this in developer mode it resets when phone restarts)
debug.qc.hardware "true"
debug.qctwa.statusbar "1"
debug.qctwa.preservebuf "1"
debug.composition.type "gpu"
hw3d.force "1"
hwui.render_dirty_regions "false"
hwui.disable_vsync "true"
13. Haptic feedback
haptic_feedback_enabled "0" 0 is off and 1 is on. 0 disables boot vibration as well.
14. Touch sensitivity
touch.presure.scale "0.001"
debug.egl.profiler "1"
15.Dalvik Virtual Machine tweaks. Better performance of device overall
dalvik.vm.checkjni "false"
dalvik.vm.dexopt-data-only "1"
dalvik.vm.heapstartsize "5m"
dalvik.vm.heapgrowthlimit "48m"
dalvik.vm.heapsize "64m"
dalvik.vm.verify-bytecode "false"
dalvik.vm.execution-mode "int:jit"
dalvik.vm.lockprof.threshold "250"
dalvik.vm.dexopt-flags "m=v,o=y"
dalvik.vm.stack-trace-file "/data/anr/traces.txt"
dalvik.vm.jmiopts "forcecopy"
16.Smoother video streaming and tweak media
media.stagefright.enable-player "true"
media.stagefright.enable-meta "true"
media.stagefright.enable-scan "true"
media.stagefright.enable-http "true"
media.stagefright.enable-aac "true"
media.stagefright.enable-qcp "true"
media.stagefright.enable-record "true"
17..Wireless Tweaks
net.ipv4.ip_no_pmtu_disc=0
net.ipv4.route.flush=1
net.ipv4.tcp_ecn=0
net.ipv4.tcp_fack=1
net.ipv4.tcp_mem=187000 187000 187000
net.ipv4.tcp_moderate_rcvbuf=1
net.ipv4.tcp_no_metrics_save=1
net.ipv4.tcp_rfc1337=1
net.ipv4.tcp_rmem=4096 39000 187000
net.ipv4.tcp_sack=1
net.ipv4.tcp_timestamps=1
net.ipv4.tcp_window_scaling=1
net.ipv4.tcp_wmem=4096 39000 18700
18. This removes fps cap (TRY AT YOUR OWN RISK) I run this doh it's fine.
debug.gr.swapinterval "0"
More Tweaks will be added soon stay tuned.

To disable fingerprint animation for faster unlocking do these settings in the same app.
Add new setting and type;
fod_animation_type
And in edit settings type;
4

garylawwd said:
To disable fingerprint animation for faster unlocking do these settings in the same app.
Add new setting and type;
fod_animation_type
And in edit settings type;
4
Click to expand...
Click to collapse
Do u think I should add 3verything I use? I think I should I'll update post. Thank u

If I follow this guide will I still be able to receive OTA updates??

Barbiox Dogg said:
If I follow this guide will I still be able to receive OTA updates??
Click to expand...
Click to collapse
In theory yes. Your phone is not unlocked neither is it rooted. No permissions to Google Android settings has been compromised so to Android your phone is still stock and locked. How the program works is like a launcher works on Android. Installing a launcher changes settings and allows features without affecting it's Android settings original launcher. Settings database editor does the same except it runs user commands on top of android system settings. That's why if u delete a setting or if u uninstall app it just goes back to original settings and deleted those you added. You can compare settings from system table and android properties tables. You cannot change android properties settings doh. I cannot confirm if you will get OTAs because I just played around with these settings yesterday and updates for XIAOMI MI A3 is the 5th of every month. What you can do is wait until after the 5th of october and I will update to let you know a defenitive yes. If anything just erase the settings u used. Remember or use settings from this guide so u can find and delete them. Or if u used a site use dat to find and delete. I'll add this reply to update post.thank you.

Dasmion said:
In theory. Your phone is not unlocked neither is it rooted. No permissions to Google Android settings has been compromised so to Android your phone is still stock and locked. How the program works is like a launcher works on Android. Installing a launcher changes settings and allows features without affecting it's Android settings original launcher. Settings database editor does the same except it runs user commands on top of android system settings. That's why if u delete a setting or if u uninstall app it just goes back to original settings and deleted those you added. You can compare settings from system table and android properties tables. You cannot change android properties settings doh. I cannot confirm if you will get OTAs because I just played around with these settings yesterday and updates for XIAOMI MI A3 is the 5th of every month. What you can do is wait until after the 5th of october and I will update to let you know a defenitive yes. If anything just erase the settings u used. Remember or use settings from this guide so u can find and delete them. Or if u used a site use dat to find and delete. I'll add this reply to update post.thank you.
Click to expand...
Click to collapse
Thanks so much for quick response. You are the man.

Barbiox Dogg said:
Thanks so much for quick response. You are the man.
Click to expand...
Click to collapse
You are welcome.

Hello, I was curious whether the audio improvement also affects the headphones or is it just the phone speaker?
Thank you.

something wrong with database link .... and setedit is not working with this adb command line
and which tabs we put the commands? system? global? secure? android propriet(cannot edit here)?

TiagOverminD said:
something wrong with database link .... and setedit is not working with this adb command line
and which tabs we put the commands? system? global? secure? android propriet(cannot edit here)?
Click to expand...
Click to collapse
1. Ok seeing that the link failed, you can get the app on the play store. It's name is "Settings database editor". It is represented by a blue gear and red background photo.
2. Explain what you mean by setedit isn't working with command line. Like is it that it closes after u put in the adb command. Does it not open, what is the error message?
3 system table.

1.Haptic feedback / intensity
haptic_feedback_enabled "1"
haptic_feedback_intensity "1"
this is not working for me. anyone tested?

bibekmufc said:
Hello, I was curious whether the audio improvement also affects the headphones or is it just the phone speaker?
Thank you.
Click to expand...
Click to collapse
In my opinion it applies to both. The difference is noticable in the speaker but not by a huge margin. With headphones I have the kz zs10 and the tin hifi p3. It's an improvement as well, not very drastic but it is there. In my opinion any improvement is good improvement with this phone. The other settings show drastic improvement for example fast boot, better WiFi and navigation fps.

grafa89 said:
1.Haptic feedback / intensity
haptic_feedback_enabled "1"
haptic_feedback_intensity "1"
this is not working for me. anyone tested?
Click to expand...
Click to collapse
Which one does not work for you?

The Intensity

grafa89 said:
The Intensity
Click to expand...
Click to collapse
Yea done testing on my A1 and A3. It works properly on my A1 but not my A3. I would have to remove this from my recommend list seeing that you and I are having this issue. Sorry for the inconveniences. Feel free to try the others. In the mean time I'm going to look for work around for vibration intensity without root. I'm sure there is one method out there.

Dasmion said:
1. Ok seeing that the link failed, you can get the app on the play store. It's name is "Settings database editor". It is represented by a blue gear and red background photo.
2. Explain what you mean by setedit isn't working with command line. Like is it that it closes after u put in the adb command. Does it not open, what is the error message?
3 system table.
Click to expand...
Click to collapse
working man ! thanks but maybe some lines ''ro.'' work only in build prop,i'm wondering disable passive gps and use only agps

can you make any video tutorial for all of us?? please

TiagOverminD said:
working man ! thanks but maybe some lines ''ro.'' work only in build prop,i'm wondering disable passive gps and use only agps
Click to expand...
Click to collapse
Glad it worked. Thanks.

soliman.sohan said:
can you make any video tutorial for all of us?? please
Click to expand...
Click to collapse
Thanks for the suggestions, I'll make the effort and put the link in the post.

bibekmufc said:
Hello, I was curious whether the audio improvement also affects the headphones or is it just the phone speaker?
Thank you.
Click to expand...
Click to collapse
Made a little video thanks

Question Google Screen Call For OP9/9Pro

Hey there guys!
I just wanted to post this in case anybody out there wants to have Google Screen Call feature on their stock phone app.
It's pretty easy to be honest
Since the OnePlus 9 and 9 Pro have the google phone apk built in, I had to look at a bunch of info to see how it could work but figured out that it's a lot easier than I thought.
Requirements needed:
-Rooted One Plus 9/ 9Pro
-Termux installed (Play Store)
- Busy Box module installed
-Magisk Hide Props module installed
-PrefEdit installed (Play Store)
1st Step:
Open Termux
Type
su
Click to expand...
Click to collapse
Grant root permission
Then Type
props
Click to expand...
Click to collapse
If you have enable Device Simulation then skip 2nd step (If not then continue)
2nd Step:
Type in "1" ( to edit device fingerprint)
Type "f" (to pick a certified fingerprint)
After that you are going to choose Google and type the number it corresponds to ( Mine was 7)
It will show you a bunch of phones.
Just find the Pixel 4 XL and type the number it corresponds to ( mine was 23)
In reality I don't think it matters which phone you use just make sure it was a pixel phone that has screen call built in.
It's going to be give you some options of which OS version you want
I chose android 11 just to be sure
Type
2
Click to expand...
Click to collapse
Then it will ask you if you want to reboot
Type in "y" to finish the 2nd Step
3rd step:
Open Termux again and redo 1st step
once your on the page it should say "device Fingerprint (active)"
Type
2
Click to expand...
Click to collapse
The next page will show you a bunch of options that you can enable.
The ones you need to enable are-
1,2,3,4,5,6,7,9,10
Click to expand...
Click to collapse
(DON'T enable "8") I accidentally enabled it and screen call didn't work
once it says it's finished Type in "y"
then it will reboot
4th Step:
Once your phone has booted up
you need to go to settings then apps and clear phone data and cache
then find Google Play services and clear data and cache
After that open the phone app and go to settings to see if screen call feature is there
If it isn't showing up then you'll need to use PrefEdit
Close the phone app (if you haven't already)
Open PrefEdit and find Phone
It should show you like 5 files
Choose dialer
Once there tap on "dialer_phenotype_flags.xml"
then search for "speak"
Find this code line
G_speak_easy_bypass_locale_check
Click to expand...
Click to collapse
tap on it and change it from false to true
then tap the save button
Now you're finished!!
Things to note once you go back to the phone app you'll need to be on Wifi to enable the feature.
If you have any questions just let me know and I'll help you out as best I can !
I will post ScreenShots of what to do if you need to see how yours should look like.

Outstanding guide ty!

Have this option already without any mods.

Very nice guide! Man, I'm super conflicted. I'd love to have the screen call feature, but I'm already using the OP dialer for call recording. No way to have the best of both worlds I guess.

r4p70r said:
Have this option already without any mods.
Click to expand...
Click to collapse
How?

Hey that's a really good guide. And a good way to get that feature. But can u not still go back and just change the flags??? And make it work with out changing the fingerprint?

bb12489 said:
How?
Click to expand...
Click to collapse
I don't know. I have the EU Version and I am from Germany. This feature may already be officially available here in Germany. I have no other explanation for this.

amaroney55 said:
Hey that's a really good guide. And a good way to get that feature. But can u not still go back and just change the flags??? And make it work with out changing the fingerprint?
Click to expand...
Click to collapse
I've tried it but it doesn't seem to want to work on my device.

r4p70r said:
I don't know. I have the EU Version and I am from Germany. This feature may already be officially available here in Germany. I have no other explanation for this.
View attachment 5282765
Click to expand...
Click to collapse
I'm translating so I could be wrong but pretty sure that's "Caller-ID and Spam" which is the option you get when you don't have Call Screening. So you don't actually have Call Screening I believe.

JayGoat said:
I'm translating so I could be wrong but pretty sure that's "Caller-ID and Spam" which is the option you get when you don't have Call Screening. So you don't actually have Call Screening I believe.
Click to expand...
Click to collapse
Yes, you are right

r4p70r said:
Yes, you are right
View attachment 5282983
Click to expand...
Click to collapse
No worries! Just wanted to make sure.
Off topic, how did you get that circle battery around the camera hole?

JayGoat said:
No worries! Just wanted to make sure.
Off topic, how did you get that circle battery around the camera hole?
Click to expand...
Click to collapse
It's an app called Energy Ring

Nice easy to follow guide but will not activate at all. Just stuck at activating call screen (requires wifi) and yes wifi is working.....lol

bamemanxxa3416 said:
Nice easy to follow guide but will not activate at all. Just stuck at activating call screen (requires wifi) and yes wifi is working.....lol
Click to expand...
Click to collapse
hm thats odd, ry leaving the app open while connected to wifi and see if that changes cause it took a while for me when it activated

wooo000 said:
hm thats odd, ry leaving the app open while connected to wifi and see if that changes cause it took a while for me when it activated
Click to expand...
Click to collapse
I tried an older method that worked on my 7t and it's now working but it had to be done on an older google dialer ver 39.270.
It's not the fancy newer version but it works

wooo000 said:
Hey there guys!
I just wanted to post this in case anybody out there wants to have Google Screen Call feature on their stock phone app.
It's pretty easy to be honest
Since the OnePlus 9 and 9 Pro have the google phone apk built in, I had to look at a bunch of info to see how it could work but figured out that it's a lot easier than I thought.
Requirements needed:
-Rooted One Plus 9/ 9Pro
-Termux installed (Play Store)
- Busy Box module installed
-Magisk Hide Props module installed
-PrefEdit installed (Play Store)
1st Step:
Open Termux
Type
Grant root permission
Then Type
If you have enable Device Simulation then skip 2nd step (If not then continue)
2nd Step:
Type in "1" ( to edit device fingerprint)
Type "f" (to pick a certified fingerprint)
After that you are going to choose Google and type the number it corresponds to ( Mine was 7)
It will show you a bunch of phones.
Just find the Pixel 4 XL and type the number it corresponds to ( mine was 23)
In reality I don't think it matters which phone you use just make sure it was a pixel phone that has screen call built in.
It's going to be give you some options of which OS version you want
I chose android 11 just to be sure
Type
Then it will ask you if you want to reboot
Type in "y" to finish the 2nd Step
3rd step:
Open Termux again and redo 1st step
once your on the page it should say "device Fingerprint (active)"
Type
The next page will show you a bunch of options that you can enable.
The ones you need to enable are-
(DON'T enable "8") I accidentally enabled it and screen call didn't work
once it says it's finished Type in "y"
then it will reboot
4th Step:
Once your phone has booted up
you need to go to settings then apps and clear phone data and cache
then find Google Play services and clear data and cache
After that open the phone app and go to settings to see if screen call feature is there
If it isn't showing up then you'll need to use PrefEdit
Close the phone app (if you haven't already)
Open PrefEdit and find Phone
It should show you like 5 files
Choose dialer
Once there tap on "dialer_phenotype_flags.xml"
then search for "speak"
Find this code line
tap on it and change it from false to true
then tap the save button
Now you're finished!!
Things to note once you go back to the phone app you'll need to be on Wifi to enable the feature.
If you have any questions just let me know and I'll help you out as best I can !
I will post ScreenShots of what to do if you need to see how yours should look like.
Click to expand...
Click to collapse
Going to add to this, if it doesn't show up in your dialer settings, clear the cache from both your Phone app and from Google Play Services, then open the Phone app again, and wait a few minutes if you still don't see it. Once you do, toggle it and see if your basic phone functions are still working. Believe it or not, some people's microphones wouldn't work with this trick in effect.
And now a rant of sorts.
The problem with this process is that in doing such, you are tricking not only the Google Phone application into thinking you're running actual Pixel hardware, but everything else, too. So this opens a whole can of worms when it comes to things like software/OOS updates, kernels, Magisk modules, etc.
For example, Elemental Kernel refused to install on my OP 7T because it was identifying itself as a "Pixel 4a." And even then, while I did get call screening to work, briefly, having to revert the changes to update things, then redo the changes, and hope they stick again.... wasn't worth it for me to do all that. I just wish we could officially get their call screening technology on EVERY Google device. Or at least ones that can use the Google Dialer framework.
So be prepared for a lot of troubleshooting and frustration. You may have to ask yourself if this is worth it.

Ty so much for this. I finally had time to do it. But the weirdest thing happened it never showed the screen option or hold for me option. But like 9 hours later I used my phone and there it was setting up.

Is it possible to enable call recording with this method as well?
according to the link, call recording should be integrated in the dialer starting vom version v63:
OnePlus exploring adding automatic call recording support in India
OnePlus devices don't support automatic call recording, but this may change in future in India, at least according to a staff member.
piunikaweb.com

So I've tried this a numerous amount of times with zero luck on firmware 11.2.4.4. does anyone have any ideas as to why it's not working for me?

ilikepie___ said:
So I've tried this a numerous amount of times with zero luck on firmware 11.2.4.4. does anyone have any ideas as to why it's not working for me?
Click to expand...
Click to collapse
Could you explain? Which part is failing? What isn't working? The call screen part? The dialer?

Question Playstore thinks I have a tablet

How do I make an it so playstore doesn't think my phone's not a tablet ?

Slys13 said:
How do I make an it so playstore doesn't think my phone's not a tablet ?
Click to expand...
Click to collapse
Technically it is,
I wont be spoon feeding everything to you on exactly what to do use google
But look in developer options, display settings else
use adb to pull your build.prop look for the tablet description/ feature set, edit on pc and set it to the one used for phones
then sideload it back to phone
reboot and enjoy
(no one knows hoe the fold will handle it YOU MIGHT BRICK YOUR DEVICE OR GET BOOTLOOP)

Slys13 said:
How do I make an it so playstore doesn't think my phone's not a tablet ?
Click to expand...
Click to collapse
did you try changing "minimum width" in developer option?

mhtruth said:
did you try changing "minimum width" in developer option?
Click to expand...
Click to collapse
Unfortunately changing this produces a persistent flickering screen.

Kronium11 said:
Unfortunately changing this produces a persistent flickering screen.
Click to expand...
Click to collapse
unchech show surface updates... i know can produce screen flickering

mhtruth said:
unchech show surface updates... i know can produce screen flickering
Click to expand...
Click to collapse
Yeah, that's already unchecked.

Have you tried going to the display settings, then screen layout, then selecting standard view. Split view makes your phone act as a tablet.

Question R

.

kevinireland11 said:
The refresh rate must need some work done to it because when you enable force 120, the screen doesn't stutter when scrolling anymore.
Although might hit battery life a little moreView attachment 5468011
Click to expand...
Click to collapse
This isn't a revelation bro. People already know this. LTPO is still a very new technology and hasn't been perfected yet.

kevinireland11 said:
The refresh rate must need some work done to it because when you enable force 120, the screen doesn't stutter when scrolling anymore.
Although might hit battery life a little moreView attachment 5468011
Click to expand...
Click to collapse
Ah yes the oldest trick in the book

Screen refresh rate is controlled by several variables, 3 which I found are:
Code:
# getprop ro.surface_flinger.use_content_detection_for_refresh_rate
<true by default; you will need Magisk's resetprop to override it>
# settings get system min_refresh_rate
<0 by default; you can set e.g. to '60'>
# settings get system peak_refresh_rate
<60 or 120 depending on toggle 'Smooth display' in Settings>
When you use 'Force peak refresh rate' in developer options then:
Code:
# settings list system | grep refresh
min_refresh_rate=120.00001
Weird number by the way. Anyway that forces the driver into 120Hz continuously.

Burt Squirtz said:
This isn't a revelation bro. People already know this. LTPO is still a very new technology and hasn't been perfected yet.
Click to expand...
Click to collapse
There's a catch though,
It's for the people that didn't know, if "we all" new then I wouldn't have posted it

On my Pixel 6 Pro it always displays '60' if you turn on 'Show refresh rate', regardless if any of the other use/force smooth display/refresh rate options is set to true...
Is this the same for you?

HerrT said:
On my Pixel 6 Pro it always displays '60' if you turn on 'Show refresh rate', regardless if any of the other use/force smooth display/refresh rate options is set to true...
Is this the same for you?
Click to expand...
Click to collapse
Mine is 60, except when things are changing on the screen, then its 120.

96carboard said:
Mine is 60, except when things are changing on the screen, then its 120.
Click to expand...
Click to collapse
After a reboot mine is behaving the same (and as originally expected) now.
Thanks for the reply!