Develop Bugs

TouchControl and Tasker

For anyone trying to integrate TouchControl into Tasker as per the instructions in this thread, the syntax has apparently changed with the newest version of the program.
As such:
echo disable > /proc/ponury/status no longer works and should now be echo enabled 0 > /proc/touch_control/<<gesture>>
And:
echo enable > /proc/ponury/status now becomes echo enabled 1 > /proc/touch_control/<<gesture>>
Note that <<gesture>> needs to be replaced with either g_doubletap2wake, g_slide2unlock, g_slide2media_next, g_slide2wake or g_touch2wake, depending on which gesture you want to enable/disable.
I can't seem to find a post anywhere in the thread reflecting these changes so figured I would try to save anyone else trying to accomplish what I was some time and frustration.
As I only have a couple posts I can't post to the Dev section of the forum so perhaps someone could either copy/paste it in the post or maybe link back to this thread. Feel free to verify the above if you need to before linking but it works for me perfectly.
Thanks!

If I have multiple gestures enabled, do I need to disable all of them for this to work?
---------- Post added 10th September 2013 at 12:43 AM ---------- Previous post was 9th September 2013 at 11:53 PM ----------
dave__ said:
If I have multiple gestures enabled, do I need to disable all of them for this to work?
Click to expand...
Click to collapse
Played around with it a bit more tonight and it works by just having each echo statement on a seperate line in the shell command, like so:
echo enabled 0 > /proc/touch_control/g_slide2wake
echo enabled 0 > /proc/touch_control/g_slide2lock

You can still completely enable/disable Touch Control the old school way without enabling/disabling each individual gesture
echo enable > /proc/touch_control/controller
or
echo disable > /proc/touch_control/controller

Is this working for anybody? I've tried tons of different variations with no success.
Run Shell -> Command: Echo enable 0 > /proc/touch_control/controller
This does not work. I also check marked the "use root" box. Any suggestions?

thanks
i will try it

I got it to work
Here is the correct syntax:
echo disable > /proc/touch_control/controller
Change disable to enable as your exit task or as a "not call any" task.
This will switch touch control entirely off/on. It will remember your settings when it is re-enabled.
Thanks to @evo5ive for pointing me in the right direction with this.

dvorak67 said:
Here is the correct syntax:
echo disable > /proc/touch_control/controller
Change disable to enable as your exit task or as a "not call any" task.
This will switch touch control entirely off/on. It will remember your settings when it is re-enabled.
Thanks to @evo5ive for pointing me in the right direction with this.
Click to expand...
Click to collapse
http://postimg.org/image/pzm78p9n7/
Can you tell me why this isn't working? I'm losing my mind over it! :crying:

Nephilim-Giant said:
http://postimg.org/image/pzm78p9n7/
Can you tell me why this isn't working? I'm losing my mind over it! :crying:
Click to expand...
Click to collapse
You are using the Touch Control app, correct? Not s2w, which many kernels have implemented?
This is what I did on my Nexii 4 and 5 to successfully disable the Touch Control app. Note that you will have to completely close and reopen Touch Control to see this work (swipe it out of your recent app list). I will see if I can export this as an app to share and will update this post.
Can you verify that the file: "/proc/touch_control/controller" exists? Proc is located at the root level, so you'll need a root file explorer like ES if you don't have one already.

dvorak67 said:
You are using the Touch Control app, correct? Not s2w, which many kernels have implemented?
This is what I did on my Nexii 4 and 5 to successfully disable the Touch Control app. Note that you will have to completely close and reopen Touch Control to see this work (swipe it out of your recent app list). I will see if I can export this as an app to share and will update this post.
Can you verify that the file: "/proc/touch_control/controller" exists? Proc is located at the root level, so you'll need a root file explorer like ES if you don't have one already.
Click to expand...
Click to collapse
I'm using Touch Control app. Not s2w of any kernels (never even downloaded one).
I'm running 4.4 kitkat on Nexus 5. I do see the "/proc/touch_control/controller", along with "g_doubletap2wake" and three others.
I posted an image on my previous post, is that the correct implementation? Otherwise, I'm quite stumped .
I'm extremely grateful for the time you are taking to help me out, I appreciate it!

Nephilim-Giant said:
I'm using Touch Control app. Not s2w of any kernels (never even downloaded one).
I'm running 4.4 kitkat on Nexus 5. I do see the "/proc/touch_control/controller", along with "g_doubletap2wake" and three others.
I posted an image on my previous post, is that the correct implementation? Otherwise, I'm quite stumped .
I'm extremely grateful for the time you are taking to help me out, I appreciate it!
Click to expand...
Click to collapse
I'm sorry, I don't know what the problem is for you here. It works for me, and you seem to have it set up the same way. The only thing I can think to try is to check your trigger states in Tasker.

Hey dvorak, I setup my scripts like you did a couple above and it looks like they are working (disables and enables when I hit "play" in tasker to test them). I made two profiles, one for Call Any and another for Orientation Face Down and put them as enter/exit tasks. I haven't had a chance to try the call profile, but when I flip the phone face down and slide it still wakes up. I tried to nudge it to edge of the table to ensure it is flat and it still is enabled. Any advice?
Thanks!

Dude ! Thank you ! I couldn't stand my phone to do whatever in my pocket while I'm biking !!

Swap recent and back keys and kill the lights on both buttons.

Having used Samsung's before and other devices, I've become accustomed to the back button being on the right.
I was hesitant about changing this as it would mean that you'll have a back symbol on the left and recent's on the right, even though they've switched, which would look a bit crap to be honest.
Anyway, disabling the backlight's will make it look a lot better whilst you have your buttons swapped
To do this you'll need to be rooted, that's it.
Flashable Zip Method
Here are some zips for flashing via recovery should you not want to edit these files yourself.
ButtonSwapLights0% - Swaps back & recents, kills button backlight
ButtonsDefaultLights0% - Default button order, kills button backlight
ButtonsDefaultLights50% - Default button order, backlight brightness 50%
ButtonsDefaultLights100% - back to normal
Manual Method
Download a text editor capable of altering system files, i personally used QuickEdit which is free in the play store.
Once that's installed
To disable the back light go here with a text editor.
/sys/class/leds/button-backlight/max_brightness change the number in here which will be 255 to 0.
This will switch off the lights immediately.
If you'd like to swap out the buttons so that back is recent and recent is back,.
Go to cypress-cap-sensor.kl which is in
system/user/keylayout/cypress-cap-sensor.kl
and find then simply reverse the text from the following two lines (there's only two in the file anyway)
key 158 BACK VIRTUAL
key 580 APP_SWITCH VIRTUAL
to
key 158 APP_SWITCH VIRTUAL
key 580 BACK VIRTUAL
Reboot the device and the keys will be switched
Enjoy
Thanks to @LeeDroid for putting me onto the location of the recents and back button file. :good:
Another big thanks to @Chronzy for making these zips, very much appreciated :good:
Update : These same zips work with Nougat on both cm and sense based roms.. Can be flashed at the same time of a Rom.

Outstanding job dladz. This is exactly what I was looking for, and so easy in your instructions. Thank you.
Off topic;
What about a lower haptic vibration ? Stock this phone vibrates like a wild rattlesnake in my hand, about to bite me. I thought most phones have a setting to adjust the vibration ? My Galaxy Note 5 does, as well as my LG G5 did and OnePlus One.
I am running LeeDroid ROM and he has specific settings for power abd haptic feedback, but even down to 1 it's still pretty powerful, just too strong for my tastes. I like to feel a slight vibration, nothing much. Is that possible ?

Is there a way to swap the Nav / software keys that some ROM's enable ?

Zorachus said:
Is there a way to swap the Nav / software keys that some ROM's enable ?
Click to expand...
Click to collapse
I'd say there is, but haven't looked into it mate.

Zorachus said:
Outstanding job dladz. This is exactly what I was looking for, and so easy in your instructions. Thank you.
Off topic;
What about a lower haptic vibration ? Stock this phone vibrates like a wild rattlesnake in my hand, about to bite me. I thought most phones have a setting to adjust the vibration ? My Galaxy Note 5 does, as well as my LG G5 did and OnePlus One.
I am running LeeDroid ROM and he has specific settings for power abd haptic feedback, but even down to 1 it's still pretty powerful, just too strong for my tastes. I like to feel a slight vibration, nothing much. Is that possible ?
Click to expand...
Click to collapse
There should be a file which you can edit to make haptic feedback alter, I've never looked into it mate.
Personally I switch feedback off. I don't need it.
Google: marshmallow haptic feedback how to change system
Also mate,, use the thanks button [emoji106] [emoji16]

When i tested the htc 10 i was shocked how the vibration intensity felt.. just like a cheap phone. Sometimes, I cannot understand htc.

DSF said:
When i tested the htc 10 i was shocked how the vibration intensity felt.. just like a cheap phone. Sometimes, I cannot understand htc.
Click to expand...
Click to collapse
Custom kernels + app allow that to be adjusted. I turned mine way down, and it feels a lot better now.

DSF said:
When i tested the htc 10 i was shocked how the vibration intensity felt.. just like a cheap phone. Sometimes, I cannot understand htc.
Click to expand...
Click to collapse
Please. This and haptic feedback has nothing to do with this thread.. If you'd like to speak about this, then please, take it elsewhere.

You can use init.d script to prevent brightness changing on every reboot, i.e
"#! /system/bin/sh
echo 0 > /sys/class/leds/button-backlight/brightness
echo 0 > /sys/class/leds/button-backlight/max_brightness"
Create a file in /system/etc/init.d and paste the above lines (without quotes), and give 755 permission, itll set to 0 before boot Everytime
If on stock rom dont have init.d support then use superSu's su.d, place same file to /system/su.d folder
Sent from my Redmi Note 3 using Tapatalk

Adarsh1998 said:
You can use init.d script to prevent brightness changing on every reboot, i.e
"#! /system/bin/sh
echo 0 > /sys/class/leds/button-backlight/brightness
echo 0 > /sys/class/leds/button-backlight/max_brightness"
Create a file in /system/etc/init.d and paste the above lines (without quotes), and give 755 permission, itll set to 0 before boot Everytime
If on stock rom dont have init.d support then use superSu's su.d, place same file to /system/su.d folder
Sent from my Redmi Note 3 using Tapatalk
Click to expand...
Click to collapse
Cheers mate, will give it a whirl

Was looking all over the web for this.
Thank you, great job.

dladz said:
Cheers mate, will give it a whirl
Click to expand...
Click to collapse
If you want, i can make automated flashable zip to disable and enable the hardware keys, just upload Cypress-cap-sensor.kl here
Sent from my Redmi Note 3 using Tapatalk

FIFATG said:
Was looking all over the web for this.
Thank you, great job.
Click to expand...
Click to collapse
You're welcome

Adarsh1998 said:
If you want, i can make automated flashable zip to disable and enable the hardware keys, just upload Cypress-cap-sensor.kl here
Sent from my Redmi Note 3 using Tapatalk
Click to expand...
Click to collapse
That'd be brilliant, thank you, appreciate that.
Primarily it's the lights coming back on, i tried to lock down the permissions but they're reset on each boot, it isn't the end of the world but it's annoying if you reboot a lot.

Made the init.d file, just seeing if it works.
Will upload once i'm in work.
EDIT: Nah didn't work mate.
Permissions in root explorer are 4 places and not 3.
so 755 comes out like 0755

dladz said:
Made the init.d file, just seeing if it works.
Will upload once i'm in work.
EDIT: Nah didn't work mate.
Permissions in root explorer are 4 places and not 3.
so 755 comes out like 0755
Click to expand...
Click to collapse
You might need to place it in su.d?

This is awesome, thanks!
Quick question regarding the init.d script - I'm currently on the stock rom, rooted with Supersu, but don't have a system/su.d directory. Should this already have existed? I can't create it either due to read only file system.

dladz said:
Made the init.d file, just seeing if it works.
Will upload once i'm in work.
EDIT: Nah didn't work mate.
Permissions in root explorer are 4 places and not 3.
so 755 comes out like 0755
Click to expand...
Click to collapse
@Adarsh1998 thanks for your tip, exactly what this mod needed.
Got it to work in system/etc/init.d, had to enable all permissions: read, write, & exec for all 3 user groups: owner root, group root, and global.... 0777.
It's survived 2 reboots now and the lights are staying off. I might try to scale back the permissions one by one... don't know if there is any danger to leaving all off those permissions enabled.
Thank you both for the info, this is something I wanted to do since I bought the phone (on other devices as well) because i'm used to the Samsung (also older HTC) setup. The no lights looks so slick and the button swap feels perfect. Thanks again!

Chronzy said:
@Adarsh1998 thanks for your tip, exactly what this mod needed.
Got it to work in system/etc/init.d, had to enable all permissions: read, write, & exec for all 3 user groups: owner root, group root, and global.... 0777.
It's survived 2 reboots now and the lights are staying off. I might try to scale back the permissions one by one... don't know if there is any danger to leaving all off those permissions enabled.
Thank you both for the info, this is something I wanted to do since I bought the phone (on other devices as well) because i'm used to the Samsung (also older HTC) setup. The no lights looks so slick and the button swap feels perfect. Thanks again!
Click to expand...
Click to collapse
Thank you.
Flashable zip on the way, thanks to @Adarsh1998 Good times

Adarsh1998 said:
You can use init.d script to prevent brightness changing on every reboot, i.e
"#! /system/bin/sh
echo 0 > /sys/class/leds/button-backlight/brightness
echo 0 > /sys/class/leds/button-backlight/max_brightness"
Create a file in /system/etc/init.d and paste the above lines (without quotes), and give 755 permission, itll set to 0 before boot Everytime
If on stock rom dont have init.d support then use superSu's su.d, place same file to /system/su.d folder
Sent from my Redmi Note 3 using Tapatalk
Click to expand...
Click to collapse
This worked perfectly. Thanks!

[MOD] Change Default Resolution to 4k - No root needed!

Hey there,
Daki from www.androidkosmos.de published a short article that the resolution can be changed to 4k by default (so Kudos to you man). As it's in German and not exactly step-by-step, I felt like posting a short how-to.
Step 1: Turn on Developer Options.
- Settings -> About -> Click 5x on Build-Number
Step 2: Allow USB debugging
- Settings -> Developer Options -> USB Debugging [X]
Step 3: Open ADB, (always without the " ofc!)
- Type "adb devices", click on "allow request" on your phone
Step 4: Change Resolution and DPI
- Type "adb shell"
- Type "wm size 2160×3840"
- Type "wm density 807 (after a little tinkering, I found 721 to be the best DPI. Yea, really, 721)"
There is no information so far as to how battery life is affected!
Back to default:
Repeat steps 1-3
Step 4: Change Resolution and DPI (back to default)
- Type "adb shell"
- Type "wm size 1080×1920"
- Type "wm density 403"
Best
IlluX

Further to this, if you're a weirdo like me and want everything reset rather than a set value due to your own personal OCD, you can use "wm size reset && wm density reset" :good::fingers-crossed::silly:

Illux said:
Hey there,
Daki from www.androidkosmos.de published a short article that the resolution can be changed to 4k by default (so Kudos to you man). As it's in German and not exactly step-by-step, I felt like posting a short how-to.
Step 1: Turn on Developer Options.
- Settings -> About -> Click 5x on Build-Number
Step 2: Allow USB debugging
- Settings -> Developer Options -> USB Debugging [X]
Step 3: Open ADB, (always without the " ofc!)
- Type "adb devices", click on "allow request" on your phone
Step 4: Change Resolution and DPI
- Type "adb shell"
- Type "wm size 2160×3840"
- Type "wm density 807 (after a little tinkering, I found 721 to be the best DPI. Yea, really, 721)"
There is no information so far as to how battery life is affected!
Back to default:
Repeat steps 1-3
Step 4: Change Resolution and DPI (back to default)
- Type "adb shell"
- Type "wm size 1080×1920"
- Type "wm density 403"
Best
IlluX
Click to expand...
Click to collapse
Thanks, when I set the 4k res, I get the error message "bad resolution"... why?

Awesome!

will this work on Z5 Premium?

sev7en said:
Thanks, when I set the 4k res, I get the error message "bad resolution"... why?
Click to expand...
Click to collapse
No idea, typo maybe? Tested it back and forth, not a single issue to report.

sev7en said:
Thanks, when I set the 4k res, I get the error message "bad resolution"... why?
Click to expand...
Click to collapse
ytheekshana said:
will this work on Z5 Premium?
Click to expand...
Click to collapse
I don't have a Z5P so I can't guarantee but I'm quite confident it does.

Haha look at that. Nice and thanks for share
I also published on talk.sonymobile.com forum.

Illux said:
No idea, typo maybe? Tested it back and forth, not a single issue to report.
Click to expand...
Click to collapse
Morning! Yes, it was... I used * instead of "x", I need new glasses eheh

How's the battery for you guys? When I do this to my Z5P, the battery doesn't even last a few hours

jms.flynn said:
Further to this, if you're a weirdo like me and want everything reset rather than a set value due to your own personal OCD, you can use "wm size reset && wm density reset" :good::fingers-crossed::silly:
Click to expand...
Click to collapse
Thanks. I checked my default density before changing it with the command "wm density" which exported 420, not 403 like OP said .

Phat-T said:
How's the battery for you guys? When I do this to my Z5P, the battery doesn't even last a few hours
Click to expand...
Click to collapse
The draining is very poor, not an impact so remarkable. The issue is about the themes, e.g. in the Agree Bird I have now when I asnwer to a call, the dialer disappear and it becomes a nightmare eheh

the phone app is not working correctly after change to 4k. phone app force close if you try to make a call and dialer disappear

got the aame result did not see any different on battery anyway, i think it is just mock, the desity shown in cpu z is same. but resolution is making at 4k in cpu z. need to change back due to phone app force closing though

gpx said:
the phone app is not working correctly after change to 4k. phone app force close if you try to make a call and dialer disappear
Click to expand...
Click to collapse
I heard somewhere that the phone app will work properly if you use 1440x2560 resolution, not sure about DPI though. I think it was Z5 Premium thread.

aren't the ui supposed to be 4k unlike the z5 p? or did they changed it?

tommy96814 said:
aren't the ui supposed to be 4k unlike the z5 p? or did they changed it?
Click to expand...
Click to collapse
They said during CES or something similar that you would be able to change the resolution in settings, so you could run 4K all the time if you wanted to. But that isn't the case on the phone right now.
Either the people from Sony that made the claim had their information wrong or Sony changed their mind afterwards. Either way, it sucks that you can't control your resolution in the settings.

MiniDemonic said:
They said during CES or something similar that you would be able to change the resolution in settings, so you could run 4K all the time if you wanted to. But that isn't the case on the phone right now.
Either the people from Sony that made the claim had their information wrong or Sony changed their mind afterwards. Either way, it sucks that you can't control your resolution in the settings.
Click to expand...
Click to collapse
yes i do not know they give us independently, like s8 did. easily for them to control like that actually.

tanipat said:
yes i do not know they give us independently, like s8 did. easily for them to control like that actually.
Click to expand...
Click to collapse
Hopefully it comes in a future update, maybe there were some issues with certain apps in 4K. I wouldn't count on it happening but it's not completely off the table.

Has someone used this for a while and can tell us about eventually battery effects of this? Does the phone app force closes etc?

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 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!