Database Users

[Q] Strange issue - receiving phone calls

I have never seen this before, and I am hoping someone knows what to do.
After installing Hyperdrive 17.1 when i receive a phone call it will display +1(and the number) even if I have the person as a contact, then if i want to call back i have to remove the + sign before trying otherwise it simply won't do anything. I am not saying this is an issue with the rom (and I really doubt it) maybe something i am missing.. Any idea?
After doing some more research this seems to be related to the Global ready settings, but I can't find how to disable this.

genesiss said:
I have never seen this before, and I am hoping someone knows what to do.
After installing Hyperdrive 17.1 when i receive a phone call it will display +1(and the number) even if I have the person as a contact, then if i want to call back i have to remove the + sign before trying otherwise it simply won't do anything. I am not saying this is an issue with the rom (and I really doubt it) maybe something i am missing.. Any idea?
After doing some more research this seems to be related to the Global ready settings, but I can't find how to disable this.
Click to expand...
Click to collapse
I get a 1 before it too but no +1 and the call back function works fine ... Im on RLS17.1 also ... My phone is unlocked and I am using tmobile but I was using att just a few days ago and it wasn't a problem .. must be something you need to change in your network setting (Possibly)

spirodave said:
I get a 1 before it too but no +1 and the call back function works fine ... Im on RLS17.1 also ... My phone is unlocked and I am using tmobile but I was using att just a few days ago and it wasn't a problem .. must be something you need to change in your network setting (Possibly)
Click to expand...
Click to collapse
Still looking, but i had to change roms.. unfortunately..

genesiss said:
Still looking, but i had to change roms.. unfortunately..
Click to expand...
Click to collapse
That sucks ... I would put a post in the Hd thread with this issue .. sbreen is good about answering and fixing .. Im a safestrap user and there is really no other rom that I want to use ... Although they are all good HD has more functions without the need to install xposed framework .. Also the 4way multiwindow is the sh!t... Hats off to all the developers

Several of us with hyperdrive are seeing this. See recent posts in the hyperdrive att rom thread. I started a general q&a thread about it in hopes of finding solution, figuring it is a setting not just specific to that ROM. I hope a solution is found because I like that ROM.
Marc
Sent from my SCH-I337 using Tapatalk

Google Dialer - On LG G3

Greetings XDA Members,
I've searched for quite some time, with limited success on keeping a stock rom along with Google Dialer. The best of both worlds if you will, that would allow great features without the loss of another. It was always a debate between using a AOSP rom at the loss of the camera, or sticking to stock and working with xposed to change settings to an agreeable state. With endless google searches, forums read, and opinions given by others; they all seemed to end with "Not Possible". Well, with some trial and error I have found a workable solution that will allow the Google Dialer to replace the stock dialer, and also allow for "In-callui" to replace the stock one.
It also needs to be mentioned, that I cannot guarantee this will work with your variant, custom rom, or other items not factored into the equation. Though this has worked for me without fail on the ATT Model D850 on Cloudy 2.5 but there are a few details to note. The "In-callUI" will show for both Incoming & Outgoing calls, but you will first see your stock one come up for a brief second or so and switch over. For me, this isn't an issue as I don't immediately answer or hang up when a call completes. Some of the items recommended in the prerequisite are optional and provide other ways to find/adjust permissions, or freeze/delete applications (Stock dialer). I'm not personally an avid developer, but if you have any questions I've been able to gain a great deal of knowledge over the years with hands on experience with the Android operating system. Feel free to ask any questions that may come up, and I'll be happy to assist if possible.
Pre-requisites;
LG G3 - Rooted
Custom Recovery with knowledge on Flashing ZIP files.
Root Explorer / File Manager
Nova Launcher / App to launch an activity.
Titanium Backup (recommended to backup Dialer and other applications in case of damage)
Included in the attachments is the file GoogleStockDialerAndMms. This file is a flashable zip that will automatically adjust the permissions necessary to make calls. It's highly recommended that you make a backup of your current rom with TWRP/CWM in case any issues arise. As this adds two files to your system directory, there is always a chance that an error can occur.
If you choose the route of Nova, you can create a shortcut to an activity. Below I've included a screenshot of which activity needs to be chosen in order to use Google Dialer.
Within Nova Launcher, long-press on the home screen.
Choose "Shortcuts"
Select "Activities"
Find "Google Dialer" in the list, then tap to open it up, and select "Phone" (use the first one in the list)
Can I disable my default dialer?
The short answer is no. As a general rule, you will need to keep your present dialer enabled in order to receive calls. The long answer is that on some phones you might be able to disable your stock dialer, but on others you definitely cannot. Feel free to try it on your own device and let us know what your results are. If you choose to do attempt this, I highly recommend against uninstalling and instead move to FREEZING the phone applications with Titanium Backup or similar root enabled application.

747 views, and 44 downloads. Hopefully everything has been smooth for everyone attempted. Please leave feedback if you have any issues.

Good to see it's over 1200 views and counting. If anyone has any issues, feel free to reply so they can be addressed.

hi @Eruvion, just wanted to check if we get the search feature with your google dialer? or does this depend on the country you live in? thanks.

resitm said:
hi @Eruvion, just wanted to check if we get the search feature with your google dialer? or does this depend on the country you live in? thanks.
Click to expand...
Click to collapse
@resitm As far as I have heard and seen so far, it will work locally depending on the information generated from your local area by google. Please let me know if you attempt it and it doesn't work.

Eruvion said:
@resitm As far as I have heard and seen so far, it will work locally depending on the information generated from your local area by google. Please let me know if you attempt it and it doesn't work.
Click to expand...
Click to collapse
thanks, i will try it once im back home.
yesterday i installed the apk from apkmirror and created a shortcut for google dialer. everything worked as should other that the tab in the most left, i think thats the call history. the dialer FC anytime that icon was touched.

Good job on this even if Im already running an AOSP based ROM, I dont need this.
But you took time writing and explaining everything so thanked all your posts,
Have a nice day

Eruvion said:
@resitm As far as I have heard and seen so far, it will work locally depending on the information generated from your local area by google. Please let me know if you attempt it and it doesn't work.
Click to expand...
Click to collapse
i flashed the zip and everything seems to be working fine. i am also able to search close by businesses, i typed pizza and it showed me the closest pizza places.
the only FC i am getting is in settings when i tap call settings-voicemail, call waiting. i don't use that so its ok for me. thanks again.
also i did not have to create a shortcut, the app icon was there after restart.

resitm said:
i flashed the zip and everything seems to be working fine. i am also able to search close by businesses, i typed pizza and it showed me the closest pizza places.
the only FC i am getting is in settings when i tap call settings-voicemail, call waiting. i don't use that so its ok for me. thanks again.
also i did not have to create a shortcut, the app icon was there after restart.
Click to expand...
Click to collapse
@resitm I'm glad everything worked for you! Thanks for letting me know
@Paradoxxx Thank you for your kind words, I'm just glad I was able to give a small contribution to the wonderful community I've used for years!

Good job on your work! I also like Google dialer. Many thanks

This does work on VS985 5.0.1. The settings does crash if you click whatever the second option was (Went back to stock for my own reasons).

SyCoREAPER said:
This does work on VS985 5.0.1. The settings does crash if you click whatever the second option was (Went back to stock for my own reasons).
Click to expand...
Click to collapse
@SyCoREAPER thank you for the update!

Doesn't work here....either when triggered from a Nova Settings widget or from the icon in the launcher. Instant force close. I can try to grab a log if you think it'll help?
D852, running Dene_Bluesman's rom (basically stock LG 5.0.1)
Edit - wonder if its because the rom version i'm using is odexed? Going to try the deodexed version and report back....
Edit 2 - nope still crashes instantly. Super frustrating! Please let me know if a log will help! @Eruvion

I want to try this on my lg G2, is there any reason you think it might not work? Anything that would make this zip specific to the G3?

+1 on this. would like to see if we can get this to work on Cloudy for G2.

Hi
This thread seem's a bit dead. Anyway i have flashed this file and it works. I am on N&N 1.3 rom. It's a stock mm based rom.

Solve notification issue

A very simple way to solve this problem is by giving priority to the notification that does not receive notification
1 go to setting
2 go to application
3 touch the name of that app to open its setting
4 go to notification
5 turn on the priority
That is all

Do you really think nobody else has already tested this?

themissionimpossible said:
Do you really think nobody else has already tested this?
Click to expand...
Click to collapse
i solved my notification issue by his method plus i have locked the concerned apps in background and now i have not lost any notification

Unfortunately this method works only in some cases, and many people can't solve the notification problem in any known way.
In this forum there are already many threads discussing about this problem, it's useless to open new threads on the same subject every time...

themissionimpossible said:
Unfortunately this method works only in some cases, and many people can't solve the notification problem in any known way.
In this forum there are already many threads discussing about this problem, it's useless to open new threads on the same subject every time...
Click to expand...
Click to collapse
I am sorry if this annoyed you.. I am new to Huawei and it is merely to share my ideas with others... Look to it as a brain storming

themissionimpossible said:
Unfortunately this method works only in some cases, and many people can't solve the notification problem in any known way.
In this forum there are already many threads discussing about this problem, it's useless to open new threads on the same subject every time...
Click to expand...
Click to collapse
alethary said:
I am sorry if this annoyed you.. I am new to Huawei and it is merely to share my ideas with others... Look to it as a brain storming
Click to expand...
Click to collapse
There is one method to solve it though it is not permanent as you have to do it every reboot. But the fix is to disable Android's own Doze.
Enable developer options and USB debugging. Then type this adb command:
adb shell dumpsys deviceidle disable
That will fix your push notifications until next reboot where you have to do it again. This way we can still use Huawei's own "Doze" function.

alethary said:
. I am new to Huawei and it is merely to share my ideas with others...
Click to expand...
Click to collapse
This doesn't mean that you are free not to respect the forum rules as the other members.
Maybe this can help you, look carefully...
https://www.youtube.com/watch?v=JmvCpR45LKA

try it.

dannejanne said:
There is one method to solve it though it is not permanent as you have to do it every reboot. But the fix is to disable Android's own Doze.
Enable developer options and USB debugging. Then type this adb command:
adb shell dumpsys deviceidle disable
That will fix your push notifications until next reboot where you have to do it again. This way we can still use Huawei's own "Doze" function.
Click to expand...
Click to collapse
I can confirm, it works like a charm.

alethary said:
A very simple way to solve this problem is by giving priority to the notification that does not receive notification
1 go to setting
2 go to application
3 touch the name of that app to open its setting
4 go to notification
5 turn on the priority
That is all
Click to expand...
Click to collapse
FAIL

Wi-Fi and data always active in battery settings did the work for me on Simple Google Rom
Gmail native app was the problem before that. It might eat more battery, but I still have about 8 hours sot a day, with Bluetooth on 8 hours too and 2 hours talk time. ?

Guys check my post on 100% working solution for Notifications http://forum.xda-developers.com/mat...ues-huawei-t3345380/post66044102#post66044102

themissionimpossible said:
Do you really think nobody else has already tested this?
Click to expand...
Click to collapse
This is the moment that im down to the flor and :crying::crying:
My friend above think that he descover America....
Sorry my friend but this is one of the very first steps that we all have done (incuded so many others) lets hope that the new L29C432B170 has solve the problem with lockscreen on time notifications...I m running it right now, testing it and i think that YES has solve the problems especialy with stock mal app.
Always friendly.

I.also never had any.problems from day one

I have the eu version and I keep seeing all these threads about notification issues. I haven't had any with WhatsApp, snap chat, Skype or any other app. They come through instantly. Even when in deep sleep. What version is everyone having this issue on?
Sent from my HUAWEI NXT-L29 using Tapatalk

ExistenZ Marshmallow problems and solutions

Our beloved developer @niaboc79 is getting very tired of people always asking the same questions and posting their problems in the development topic of his rom.
So I decided to make this topic in the "general" section of the forum where people can post about their problems and hopefully some solutions, in the hopes that it will help him and the people having problems at the same time.
Whenever a cause or a solution for a problem is found, I will put it in the second post, right underneath this one.
I want to make clear that I'm not an expert and cannot help much myself, I will just collect and centralize information, and I'm in no way affiliated with @niaboc79 and his work, and do absolutely not deserve any credits for his work.
Also there is no guarantee that the information I collect and post in the second post will be a solution for your problem even if it has apparently worked for other people with similar symptoms.
I invite everyone that uses his rom to share helpful information here. (please)

Firstly ; a copy of the FAQ that @niaboc79 posted himself. You should read it before asking questions.
niaboc79 said:
Frequently Asked Questions
Q: How to flash the DRM fix and avoid loosing of recovery
A:http://forum.xda-developers.com/showpost.php?p=67111204&postcount=1169
Q: Hey, that thing doesn't work!
A: Check if there isn't an (*) at the right of setting description, that means that you must restart SystemUI.
If it is not the case, try to enable/disable option a few time and reboot or read thread to find an answer.
Q: Why is there greyed options in eXistenZ settings!
A: These otions aren't available yet.
Q: Weather isn't working on lockscreen or in expanded status bar...
A: Go in settings/eXistenZ/Notification Panel/Weather Settings;
Press on Weather panel icon, then on Display weather switch;
Select OpenWeatherMap as Weather source;
Use Custom Location;
Set your Location
Click to expand...
Click to collapse
Recovery access problems:
-Don't update busybox
-Don't update Kernel
-Don't flash DRM fix (see FAQ)
If you haven't done one of the above, you should be able to enter recovery by pressing volume down (repeatedly) while starting up the phone.
If you did do one of the above, simply reflash the rom.
Note: since version 4.7 (or alternatively version 3.9) lag is no longer appearing in the rom. If you do witness lag on 4.7 (3.9) there is probably something that you have done that is causing it. Check and double check your apps and settings before trying other solutions in that case!
Lag problems:
-Update to rom version 4.7 (or 3.9 for the rom based on the beta firmware)
-Follow the instructions posted here on rom version prior to 4.7 (3.9)
If you still witness lag after that:
-After installing, give the rom some time to settle, it has to index all your files and the memory management still has to find out what apps (you) are running. This takes a long time (depending on your usage) so give it some days.
-Some xposed modules and Greenify are known causes. Disable that if you use them and see if the lag still persists. If it is gone, you can find the exact module/setting that is the cause by disabling just one module/setting at a time and try if the lag has gone. (this also counts for other problems by the way)
-Stamina mode makes the phone slower as it lowers processor speed etc. Turn it off and check if the lag has gone.
-Many (also popular) apps use quite a lot of system ressources even if you aren't using them. You could uninstall your apps, then reinstall them one at a time, use the phone a bit to check if the lag came back, if not install the next app, and so on until you find the app that is making your phone lag/behave weird.
-Never restore a titanium backup (or similar) when coming from a lollipop rom. There are several differences between lollipop and marshmallow so you risk to restore incompatible stuff.
-Activating blur in recents causes lag (v 3.5, should be solved with the next update of the rom) Fixed in final version
Profile picture (top right of status bar) won't remain after reboot:
-Open the contacts app and go to the first contact (that should contain info about you, and no image) and choose the picture you would like to see in stead of the blue user icon (click on the pencil and then on the image)
Now the image for the user switch in the status bar has been changed too, and it will stick after reboot.
Switch user causes a crash of the beta feedback app and doesn't work
-Remove beta feedback app
You can now switch users, although the system will crash/reboot, it does switch. (will be fixed in a future release of the rom) Fixed in final version

Reserved for later use

i have a problem...
using v 3.5 existance and when i open camera then navigation bar does not showing.. any help?

Ab.Shaheen said:
i have a problem...
using v 3.5 existance and when i open camera then navigation bar does not showing.. any help?
Click to expand...
Click to collapse
Are you using the default camera app? Do you use a theme?

Knutselmaaster said:
Are you using the default camera app? Do you use a theme?
Click to expand...
Click to collapse
am using default camera..
it also does not works on previous versions of existanc marshmallow..
---------- Post added at 09:53 PM ---------- Previous post was at 09:51 PM ----------
Ab.Shaheen said:
am using default camera..
it also does not works on previous versions of existanc marshmallow..
Click to expand...
Click to collapse
i just checked on another camera app... but same result....
not showing there also..

Did you try another theme?
Did you try cleaning all data of the camera app(s)?

systemUI and lock screen are very laggy i tried clean install didnt work also dirty one and had same resualts and thats the only issure i ever faced using this rom since lolipop

Knutselmaaster said:
Are you using the default camera app? Do you use a theme?
Click to expand...
Click to collapse
nope default camera iam using.....which comes in existenz v3.5

rudhraraj said:
nope default camera iam using.....which comes in existenz v3.5
Click to expand...
Click to collapse
Knutselmaaster said:
Did you try another theme?
Did you try cleaning all data of the camera app(s)?
Click to expand...
Click to collapse

xRevengerZee said:
systemUI and lock screen are very laggy i tried clean install didnt work also dirty one and had same resualts and thats the only issure i ever faced using this rom since lolipop
Click to expand...
Click to collapse
Did you check the the lag part of the second post?

I tried all of what u mentioned but tonight i flashd xperia x system ui v1.5 and that made every thing smooth like never before also i dont have any mods installed but problem is after installing the other system ui now existenz feature dont work

xRevengerZee said:
No send me link please
Click to expand...
Click to collapse
The second post of this topic right here...

i did try to reflash the rom after upgrading busybox, but i just cant find a way to flash zip file through pc.
is there a way to flash the rom without flashing back to stock?

Maybe this will work
But if you have problems, there is nothing better than starting from scratch and do a clean install imo

Good morning guys
Any idea of what the hell is making Android OS drink my battery like a martini?
Sent from my Sony D6503 using XDA Labs

FellipeSilvaRJ said:
Good morning guys
Any idea of what the hell is making Android OS drink my battery like a martini?
Sent from my Sony D6503 using XDA Labs
Click to expand...
Click to collapse
By just looking at that image, not really.
I see that you haven't used your phone much during the time of the picture, so no apps are using battery, nor your screen. That automatically makes the operating system the most consuming thing, as it is needed to keep the phone running.

FellipeSilvaRJ said:
Good morning guys
Any idea of what the hell is making Android OS drink my battery like a martini?
Sent from my Sony D6503 using XDA Labs
Click to expand...
Click to collapse
By just looking at that image, not really.
I see that you haven't used your phone much during the time of the picture, so no apps are using battery, nor your screen. That automatically makes the operating system the most consuming thing, as it is needed to keep the phone running.
Click on the app to see what is consuming (radio, processing.... ) if it is the radio, maybe you had very bad connection. If it's the process that prevents the processor going to sleep you should try to find out what is running all the time.

Knutselmaaster said:
By just looking at that image, not really.
I see that you haven't used your phone much during the time of the picture, so no apps are using battery, nor your screen. That automatically makes the operating system the most consuming thing, as it is needed to keep the phone running.
Click to expand...
Click to collapse
Actually, I take at least 7 pictures with Camera FV-5/ 7 with stock app, with screen brightness full. Used WhatsApp and Telegram too, normally these apps and screen should be on top of the list. I have no idea of what the hell I do :silly:
Sent from my Sony D6503 using XDA Labs

FellipeSilvaRJ said:
Actually, I take at least 7 pictures with Camera FV-5/ 7 with stock app, with screen brightness full. Used WhatsApp and Telegram too, normally these apps and screen should be on top of the list. I have no idea of what the hell I do :silly:
Click to expand...
Click to collapse
F***ing 457mAh, there's something really wrong here
Sent from my Sony D6503 using XDA Labs

Google Dialer with Call Screen?

Has anyone attempted to use The Google Dialer and get call screening working? Wasn't sure if anyone had yet, but was curious. I'd gotten it working on my 6T and 7 Pro, but understand the development has been very different for our device.

champ784 said:
Has anyone attempted to use The Google Dialer and get call screening working? Wasn't sure if anyone had yet, but was curious. I'd gotten it working on my 6T and 7 Pro, but understand the development has been very different for our device.
Click to expand...
Click to collapse
I couldn't get call screening working granted I didn't exactly try that hard to get it working. Just systemized the dialer app and flashed Google dialer framework magisk module
Idk what else is needed to make it work.

I bet I can get it working. I remember a
the thread for the OnePlus 7 Pro about call screening, everyone said that it wasn't working, I had mine up and running without any problems. Currently I'm waiting for my unlock token from OnePlus, so I can't confirm if this method will work, but I'll tell you exactly what I did before and I don't see a reason why it shouldn't work now. Try it out and then let me know if it works or not. It doesn't, maybe we can come up with a workaround.
The version number of the dialer that you use is critical. New versions of the Google dialer from the Play store via Google Framework do not work. Here's the link to the APK that I used:
https://www.apkmirror.com/apk/googl...le-phone-39-0-270797297-android-apk-download/
The initial steps I performed were downloading the Magisk modules Busybox for NDK, Google Framework, and App Systemizer alongside installing Preferences Manager from the Play Store.
Then I cleared the storage for the stock dialer app, denied all of its permissions, and finally disabled it. Then I used App Systemizer to convert the Google Dialer into a system app. When App Systemizer gives you the option to install either the app as a 1 - system app or 2 - priv-app, always choose number 2. Then make sure to go into system settings and choose the Google Dialer as the default dialer app, otherwise icall screen won't work at all. Also go ahead and clear Google Dialer's storage while enabling all of it's permissions. Also go under Apps & Notifications in the system menu and choose special app access. Enable the Google Dialer to draw over other apps, modify system settings, and have usage access.
Next open up Preferences Manager. Grant it superuser access and from options choose "show system apps". Scroll down the list until you come to where you start seeing entries for "phone". On my old OnePlus 7 Pro, the one to choose was the first one listed as "phone". It didn't have an icon next to it versus the stock Dialer app which did. When you open this option up, swipe from left to right until you get to the heading "dialer_phenotype_flags.xml". First, choose backup under the menu in case there's a problem afterwards and you need to restore the flags to their previous settings. Then go to the search field and search for all the flags with "speak_easy", "speakeasy", "call_screen", and "callscreen", then update all of these flags with values of "true".
The way to determine if this procedure worked is to now open up ithe Google Dialer and choose the three dot menu and choose "Settings". You should see an option listed for "Call Screen". If you do see it then the process worked.
Let me know if you need any further information but I think that should work.

smreker said:
I bet I can get it working. I remember a
the thread for the OnePlus 7 Pro about call screening, everyone said that it wasn't working, I had mine up and running without any problems. Currently I'm waiting for my unlock token from OnePlus, so I can't confirm if this method will work, but I'll tell you exactly what I did before and I don't see a reason why it shouldn't work now. Try it out and then let me know if it works or not. It doesn't, maybe we can come up with a workaround.
The version number of the dialer that you use is critical. New versions of the Google dialer from the Play store via Google Framework do not work. Here's the link to the APK that I used:
https://www.apkmirror.com/apk/googl...le-phone-39-0-270797297-android-apk-download/
The initial steps I performed were downloading the Magisk modules Busybox for NDK, Google Framework, and App Systemizer alongside installing Preferences Manager from the Play Store.
Then I cleared the storage for the stock dialer app, denied all of its permissions, and finally disabled it. Then I used App Systemizer to convert the Google Dialer into a system app. When App Systemizer gives you the option to install either the app as a 1 - system app or 2 - priv-app, always choose number 2. Then make sure to go into system settings and choose the Google Dialer as the default dialer app, otherwise icall screen won't work at all. Also go ahead and clear Google Dialer's storage while enabling all of it's permissions. Also go under Apps & Notifications in the system menu and choose special app access. Enable the Google Dialer to draw over other apps, modify system settings, and have usage access.
Next open up Preferences Manager. Grant it superuser access and from options choose "show system apps". Scroll down the list until you come to where you start seeing entries for "phone". On my old OnePlus 7 Pro, the one to choose was the first one listed as "phone". It didn't have an icon next to it versus the stock Dialer app which did. When you open this option up, swipe from left to right until you get to the heading "dialer_phenotype_flags.xml". First, choose backup under the menu in case there's a problem afterwards and you need to restore the flags to their previous settings. Then go to the search field and search for all the flags with "speak_easy", "speakeasy", "call_screen", and "callscreen", then update all of these flags with values of "true".
The way to determine if this procedure worked is to now open up ithe Google Dialer and choose the three dot menu and choose "Settings". You should see an option listed for "Call Screen". If you do see it then the process worked.
Let me know if you need any further information but I think that should work.
Click to expand...
Click to collapse
Just finished trying this, worked like a charm! Thank you so much! This was the only thing making me consider going back to my pixel 3a xl, but now it's clear that you can have the best of both worlds!
Should we post this in the Mods category for this device? I know a lot of people would be happy to have this!

First off I'm so glad to hear that it worked for you! It's a pretty nifty feature and I personally think it's pretty cool.
To be honest with you, that was pretty much my first time ever posting anything to XDA. Most of the time I just go through the forums and tried to get new features to work on my phone, but hardly ever participate in the actual discussions
if you honestly think this could help other XDA members get this up and running, I'd love to help. But to be honest with you I'm not really familiar with starting a thread and stuff like that. If you don't mind, could you tell me what I need to do to do that? Is that like starting a new thread somewhere in the OnePlus 7T Pro McLaren edition discussions? I'm an absolute total new when it comes to posting and forums and discussion groups, and I have no idea what the protocol is for doing something like that. I'd really appreciate it if you could kind of guide me in the right direction or make some suggestions as to how I go about doing it.
Well, just to reiterate, I'm really excited that it work for you and hopefully we can get it to work for other people as well. Just respond to this message and let me know what I can do to help. Thanks again!

smreker said:
First off I'm so glad to hear that it worked for you! It's a pretty nifty feature and I personally think it's pretty cool.
To be honest with you, that was pretty much my first time ever posting anything to XDA. Most of the time I just go through the forums and tried to get new features to work on my phone, but hardly ever participate in the actual discussions
if you honestly think this could help other XDA members get this up and running, I'd love to help. But to be honest with you I'm not really familiar with starting a thread and stuff like that. If you don't mind, could you tell me what I need to do to do that? Is that like starting a new thread somewhere in the OnePlus 7T Pro McLaren edition discussions? I'm an absolute total new when it comes to posting and forums and discussion groups, and I have no idea what the protocol is for doing something like that. I'd really appreciate it if you could kind of guide me in the right direction or make some suggestions as to how I go about doing it.
Well, just to reiterate, I'm really excited that it work for you and hopefully we can get it to work for other people as well. Just respond to this message and let me know what I can do to help. Thanks again!
Click to expand...
Click to collapse
Personally, running a year old version of Google Dialer just to get Call Screen isn't worth it. Have you tested Call Screen to see if it actually fully works? Or if in reality the person calling hears nothing at all?

starcms said:
Personally, running a year old version of Google Dialer just to get Call Screen isn't worth it. Have you tested Call Screen to see if it actually fully works? Or if in reality the person calling hears nothing at all?
Click to expand...
Click to collapse
I've been running it with no issues on OOS and it works perfectly fine. Tested call screening and it works perfectly fine. Personally, I think it's worth it.
I'm running AOSiP now and I've yet to test it there. But OOS is confirmed to be working with it.

Has anybody been able to make it work on any of the custom ROMs? I tried smreker's steps on aosip but I couldn't get Google dialer to install. Just finished flashing lineage and aside from the fingerprints, this thing is running like it's good enough to say bye bye to oxygen.

raphi809 said:
Has anybody been able to make it work on any of the custom ROMs? I tried smreker's steps on aosip but I couldn't get Google dialer to install. Just finished flashing lineage and aside from the fingerprints, this thing is running like it's good enough to say bye bye to oxygen.
Click to expand...
Click to collapse
I'm getting ready to try it myself.. If I can get it working, I'll post about it here

champ784 said:
I'm getting ready to try it myself.. If I can get it working, I'll post about it here
Click to expand...
Click to collapse
Soooo.... Any luck ?? ?

raphi809 said:
Soooo.... Any luck ?? ?
Click to expand...
Click to collapse
I was testing today on aosip ROM and it did not work. The caller can't hear the Google assistant voice. I'm going to be looking into this more to see why it works on stock ROM, but not a customer ROM..
Aosip ships with Google dialer pre-installed, so you need to use debloat magisk module to uninstall it, and then reinstall it with the older APK file.. I may have messed up the installation on my end, so any other testing from other users would be greatly appreciated. I may reach out to the developers to see if they can figure out what I may be missing.
I never reinstalled another dialer app, so that could have something to do with it. However, I don't see why that would be the case, but you never know with these things. Thinking about it now, I didn't remove telophony apps on the phone either, so that could also have something to do with it? Any ideas?

https://forum.xda-developers.com/an...how-to-enable-google-call-t4150585?styleid=19

ih8legal said:
https://forum.xda-developers.com/an...how-to-enable-google-call-t4150585?styleid=19
Click to expand...
Click to collapse
Followed new instructions, option appears, but caller still can't hear and there's no transcription on my end :/
Currently running on AOSiP ROM, latest build (August)

champ784 said:
Followed new instructions, option appears, but caller still can't hear and there's no transcription on my end :/
Currently running on AOSiP ROM, latest build (August)
Click to expand...
Click to collapse
I'm trying to think of the different variables that could affect it, maybe something I did, that I didn't mention. Did you disable your stock dialer? Cause I tried it to today and it works super, transciptions and everything. Nothing should be different than the previous instructions, besides spoofing the device fingerprint. Maybe try disabling it and clearing data and then enabling it again?
Edit: I just read your previous posts. Never mind the stock dialer. This new method works with the latest Google phone update, so maybe try reverting your stock dialer back and then updating it?

ih8legal said:
I'm trying to think of the different variables that could affect it, maybe something I did, that I didn't mention. Did you disable your stock dialer? Cause I tried it to today and it works super, transciptions and everything. Nothing should be different than the previous instructions, besides spoofing the device fingerprint. Maybe try disabling it and clearing data and then enabling it again?
Edit: I just read your previous posts. Never mind the stock dialer. This new method works with the latest Google phone update, so maybe try reverting your stock dialer back and then updating it?
Click to expand...
Click to collapse
I'm on AOSiP which ships with Google Phone Dialer by default. Could that be my problem?

champ784 said:
I'm on AOSiP which ships with Google Phone Dialer by default. Could that be my problem?
Click to expand...
Click to collapse
That's a little beyond my expertise. I can only describe what I did, and those steps made it work for me. I haven't heard any other reports of it not working or working so we shall see. I'm thinking that the downloads for call screening are corrupted for you or something, if you're saying that the audio is not working, if you could clear that and start the process afresh?