Database Users

Handcent Image missing on DC2.08

hi guys..
I have updated to DC 2.08 and almost everything is perfect.
my problem is with Handcent. It will not show the images of my friends. I have tried uninstall Handcent.. reload.. rebooting. I have deleted ALL text messages, but new messages do not show images.
I tested with the stock sms app, and it shows the images!!!!!
Anybody have a fix for this???
Also... I heard that this new ROM will remove the annoying .. double menu - pop up- on thing. ie. when you press menu twice to wake up the phone... the menu pops up. But it is still there!!!
Love the ROM, fast and stable. these are my only issues.. so I am hopping someone can point me to the fix.
Thanks all!

I have the same issue. Sometimes it happens randomly. I don't think it has to do with the ROM in particular. It happens nearly every time I swap or upgrade ROMS or restore all my apps via Titanium after a wipe. :/
Would like to know the answer to this.

wonbattlelost said:
[ot]
do you use friendstream? and if so, do you have any issues with it at all?
[/ot]
do you have Auto-Retrieve enabled in the stock mssging app?
Click to expand...
Click to collapse
No, I do not use friendstream. Checked it, and there is nothing in it. It says I do not appear to be logged into any sociual networks, which is correct... I currently do not subscribe to any.
yes, I do have Auto-Retrieve enabled on the stock sms app.

Bump for help
Sent from my HERO200 using Tapatalk

im not sure, I use handcent and I have no problems with it.

wtphoto said:
im not sure, I use handcent and I have no problems with it.
Click to expand...
Click to collapse
yeah.. been using Handcent since i got the phone back in Dec. and have used it with all sorts of ROMs and all of DC's ROMs too. DC2.08 is the only ROM that has caused this to happen.
Maybe it is time to try a different SMS app.???

Looks like I can not find a solution to correct handcent
Downloaded compsms
It is working just fine
Now I can see contact images
Sent from my HERO200 using Tapatalk

I had a problem on DC 2.05 I think it was where handcent wouldnt work but I think it had more to do with the update that handcent sent out I would have suggested uninstalling and reinstalling

wonbattlelost said:
+1
make sure to always do the basic troubleshooting before reporting an issue. uninstalling and reinstalling is probably a good place to start. also consider a fresh wipe and reinstall of the ROM.
happy flashing!
Click to expand...
Click to collapse
yes.. you are 100% right!!
please reread my original post. Did the reinstallation of handcent x2. did not help.
I did not reinstall the ROM. That was a last resort for me, because I have everything setup as I want it.
It is odd that both stock app and compsms works fine, and shows the contact images. So, I am leaning towards Handcent latest update was the issue. it must be conflicting with something on my phone... maybe DC 2.08.
Anyways, CompSMS is working fine. I like Handcent better, but this OK. The new big comp widget is odd to me, not sure if I like it.

Automatic backup, process successful

Got this notification after a reboot today. I don't remember installing anything that should do any kind of automatic backups once in a blue moon on reboots. Any idea what does this?

If you're running Jelly Bean, try tapping-and-holding the notification, clicking App Info and see if you get a system app or an app that you installed back as a result. Might not be of much use, but you may be able to narrow down your search.

I am neither running jb, nor able to reproduce this

have you got Google backup enabled?

slaphead20 said:
have you got Google backup enabled?
Click to expand...
Click to collapse
Yes, but i've got it enabled since... forever, and never seen this message, not even once.
BTW: I've always been wondering if it's actually possibly to manually review and/or fetch what's on that Google backup.

InfX said:
I am neither running jb, nor able to reproduce this
Click to expand...
Click to collapse
I have no idea, then, sorry, as I've never seen that message before.
InfX said:
BTW: I've always been wondering if it's actually possibly to manually review and/or fetch what's on that Google backup.
Click to expand...
Click to collapse
Head for the Google Dashboard - https://www.google.com/dashboard/, Ctrl+F "Android" and click "More data stored about this device".

qwerty12 said:
Head for the Google Dashboard - https://www.google.com/dashboard/, Ctrl+F "Android" and click "More data stored about this device".
Click to expand...
Click to collapse
Hm, thanks
Honestly, there is barely anything in there. I though it was supposed to (almost) store the entire /data/data in there.

I got it too, but on GN.
I just got the same notification! Never seen it before.
Verizon Galaxy Nexus, 4.1.1. When I long press the notification, app info brings up locus, a geocaching app, which has no notifications,and doesn't do backups. I've had locus (which I used once a long time ago) on the phone for well over a year.
Also odd, I had to reboot to make the notification go away.
sean

Hmm, i have locus. And it had an update recently. Ill ask the dev on his forum, locus dev is very cooperative, thanks

Update: it is Locus, indeed, it now got automatic scheduled backup module, can be disabled from Locus via menu - functions - backup manager. I would never guess by the notification text, thanks.
EDIT: This is the Locus thread mentioning the functionality.
PS: Topic closed, i guess. Thanks everyone for help.

InfX said:
Update: it is Locus, indeed, it now got automatic scheduled backup module, can be disabled from Locus via menu - functions - backup manager. I would never guess by the notification text, thanks.
EDIT: This is the Locus thread mentioning the functionality.
PS: Topic closed, i guess. Thanks everyone for help.
Click to expand...
Click to collapse
Thread closed.

Hangouts SMS crash [solved]

Problem
-------------
Hangouts crashes trying to send SMS after 4.4.3 upgrade. 3rd Party apps do the same. As soon as you start typing hangouts crashes.
You disabled "Messaging" before the upgrade and can't re-enable it. "Enable" is grayed out in the Settings->Apps menu.
Solution
---------
In the Settings->apps menu - the 3 dots menu has a "Reset App Preferences" option. It re-enables ALL disabled apps. This will fix sending SMS/MMS. You can't have it disabled in 4.4.3 safely.

superm1 said:
Anyone else noticing hangouts crashing whenever you try to type out an SMS? I can't seem to send them at all now. It crashes as soon as I start to type.
Happened right after 4.4.3 upgrade. I tried to clear hangouts data but to no avail.
Click to expand...
Click to collapse
Please post questions in Q&A for the sake of consistency =)

superm1 said:
Anyone else noticing hangouts crashing whenever you try to type out an SMS? I can't seem to send them at all now. It crashes as soon as I start to type.
Happened right after 4.4.3 upgrade. I tried to clear hangouts data but to no avail.
Click to expand...
Click to collapse
Also it sounds just like this here: https://productforums.google.com/forum/#!topic/hangouts/4i6nKG-d2_M
But I don't have delivery reports and I can't enable messaging. It's disabled in settings->apps.

scorpion667 said:
Please post questions in Q&A for the sake of consistency =)
Click to expand...
Click to collapse
Sorry, can you move this to Q/A? My bad.

OK I found a fix. In the apps menu - the 3 dots menu has a "Reset App Preferences" option. It re-enables ALL disabled apps. Not ideal since I'll have to re-disable the others I don't want. But at least it gets messaging re-enabled.
That makes SMS work again oddly enough. Just need to deal with having a "messaging" app in the drawer that I don't use I guess.

superm1 said:
OK I found a fix. In the apps menu - the 3 dots menu has a "Reset App Preferences" option. It re-enables ALL disabled apps. Not ideal since I'll have to re-disable the others I don't want. But at least it gets messaging re-enabled.
That makes SMS work again oddly enough. Just need to deal with having a "messaging" app in the drawer that I don't use I guess.
Click to expand...
Click to collapse
Nice! Thanks for posting the fix, could come in handy for me once I switch to 4.4.3 as I have 68 services/apps frozen =P

I also had this issue. I factory reset, which is usually a decent idea after updates. It definitely had something to do with messaging being disabled and I couldn't reenable it either. Glad you found an alternate fix, loving the update so far

SymbioticGenius said:
I also had this issue. I factory reset, which is usually a decent idea after updates. It definitely had something to do with messaging being disabled and I couldn't reenable it either. Glad you found an alternate fix, loving the update so far
Click to expand...
Click to collapse
Yeah if I had been rooted and done titantium backup recently, that would have been my approach too. I didn't want to have to redo all my apps and settings etc. Glad I didn't have to.

I didn't use TiBu to restore. It's weird but this phone is the first that I don't really back things up like I used to. Mostly cause I have no risk of breaking stuff via flashing nightlies and the like. I've had iffy experiences restoring old data on to new builds so I started from scratch. So far so good.

Yeah I had this too. After the update, i could receive but not send SMS/MMS. Had the stock app previously disabled and then the enable button was gone. Drove me absolutely crazy last night and most of today. Tried half a dozen SMS apps and even downloaded two entire Roms to get their MMS.apk and try to install them (which did not work at all). Even deleted all my messages with an SMS backup app. Nada. Moto support (obviously bad idea) said to clear cache for entire phone, which totally could have worked but was completely unhelpful. I did dozens of Google searches about it and came up empty every time. I was just about to give in to a factory reset, which I consider the my last resort, and I checked the action overflow in the disabled apps section and found the "reset app preferences". Then just browsing XDA for battery tips a few minutes later, I came across then. I even checked the Dev section earlier. But I guess I should have checked general. Thanks for putting this out there for others to find.

Thanks for this solution. Made life better for me. I guess 4.4.3 doesn't allow us to disable the messaging app.

You are the man! I thought I was the only one having the problem. Thank you! :good:

me too. I can't believe it took me this long to find this thread. Not being able to send texts was a bummer. I was using some feature called "voicemal.":silly:

VVM tab in stock dialer - TMO variant

Does anyone have VVM actually working in the stock dialer on the TMO variant?
First, the tab itself in the dialer won't even show if you have the TMO VVM app. So I uninstalled the app, got the tab to show, but all I get is a blank white box with a VM icon with a red exclamation point on it. Anyone else? Yeah, I could use the VVM app but...eff that. I want it in the dialer. ?
Oh, and if you go into the dialer settings > call settings > voicemail, it says "visual voicemail is not activated yet" but, uh, bruh, it totally is because the VVM app works (when installed).

I have the unlocked 6T and it's the same for me. I tried stock dialer and Google phone dialer, neither will activate VVM but the T-Mo VVM app works. It's not just the T-Mo 6T with this issue
Sent from my ONEPLUS A6013 using Tapatalk

Lame. Maybe with root/ROMs we can cook in the Google dialer or something and get it to work as intended. Thanks for confirming it's not just me.

Ok guys I had this issue as well. I got mine working by using the latest Google dialer beta apk and doing the following:
1. If you have TMO Vvm or Google dialer(or both) apps installed, uninstall them.
2. Go to stock dialer app info and clear cache and data.
3. Go into the stock dialer settings and activate vvm. Reboot.
4. Install Google dialer and Grant all permissions.
5. Go into settings/apps/default apps and make Google dialer default.
6. GDialer settings voicemail make sure everything is on.
That was all I did... TMO 6t

Haz3 said:
Ok guys I had this issue as well. I got mine working by using the latest Google dialer beta apk and doing the following:
1. If you have TMO Vvm or Google dialer(or both) apps installed, uninstall them.
2. Go to stock dialer app info and clear cache and data.
3. Go into the stock dialer settings and activate vvm. Reboot.
4. Install Google dialer and Grant all permissions.
5. Go into settings/apps/default apps and make Google dialer default.
6. GDialer settings voicemail make sure everything is on.
That was all I did... TMO 6t
Click to expand...
Click to collapse
Bruh... That seemed to work. I got the same screen now that you posted. Just have to wait until I get a VM to know for sure
Edit: spoke too soon. I went back into phone and I'm getting the "you might not see voicemail until it's fully activated" blah blah blah error.

It pops up as a text message like this,

Haz3 said:
It pops up as a text message like this,
Click to expand...
Click to collapse
Yeah...I wish. Lemme ask you though... Do you pay for VM to text from TMO for like 4 bucks a month? I do, and I'm wondering if that might be interfering with Google's transcription service...

thedrizzle said:
Yeah...I wish. Lemme ask you though... Do you pay for VM to text from TMO for like 4 bucks a month? I do, and I'm wondering if that might be interfering with Google's transcription service...
Click to expand...
Click to collapse
I don't. I don't even see it as an option to add to my plan ??

Haz3 said:
I don't. I don't even see it as an option to add to my plan ??
Click to expand...
Click to collapse
Ok. I just turned it off on my plan. I'm gonna redo the whole process because I think you have to go into the TMO VVM app to provision it so it gives you the options you selected. I'll report back in a bit.

Good luck!! I'm off to bed, work comes early unfortunately?? post and let us know!!

Haz3 said:
Good luck!! I'm off to bed, work comes early unfortunately post and let us know!!
Click to expand...
Click to collapse
Yeah that didn't work either. Might be because I've paid for the feature thru today or something, I'll try it again tomorrow. The fact that it works for you tells me that I can get it too.

I have installed visual voicemail TMobile app and work fine.
Sent from my ONEPLUS A6013 using Tapatalk

thedrizzle said:
Yeah that didn't work either. Might be because I've paid for the feature thru today or something, I'll try it again tomorrow. The fact that it works for you tells me that I can get it too.
Click to expand...
Click to collapse
Damn

And here I am having problems even installing the Google dialer apk! Keeps saying app not installed when I try.

mang0 said:
And here I am having problems even installing the Google dialer apk! Keeps saying app not installed when I try.
Click to expand...
Click to collapse
check this thread https://forum.xda-developers.com/an...phone-v14-0-175904292-bubble-t3708218/page190
I have seen some similar issue in this thread but can't remember where exactly, but maybe check through it and or try the latest one patched in the OP. It also mentions for vvm in the dialer, you need to make it default app dialer.or maybe disable stock, I cant remember off the top of my head..just search through the thread .
https://forum.xda-developers.com/android/apps-games/app-google-phone-v14-0-175904292-bubble-t3708218

Haz3 said:
Ok guys I had this issue as well. I got mine working by using the latest Google dialer beta apk and doing the following:
1. If you have TMO Vvm or Google dialer(or both) apps installed, uninstall them.
2. Go to stock dialer app info and clear cache and data.
3. Go into the stock dialer settings and activate vvm. Reboot.
4. Install Google dialer and Grant all permissions.
5. Go into settings/apps/default apps and make Google dialer default.
6. GDialer settings voicemail make sure everything is on.
That was all I did... TMO 6t
Click to expand...
Click to collapse
Did you actually have success receiving voicemails?
I did this, and now my voicemail is showing up in Google dialer, however it's giving me a "can't activate visual voicemail" error.

Never got an error and yes they did come in

Haz3 said:
Never got an error and yes they did come in
Click to expand...
Click to collapse
Interesting... I'll try it again.

Also try a different GDialer. I've used both the newest beta and the modded dark theme one

Haz3 said:
Also try a different GDialer. I've used both the newest beta and the modded dark theme one
Click to expand...
Click to collapse
OK, I just tried the beta. Let me try the dark theme one now.
EDIT: Doesn't seem to be working. Still getting an activation error. I'll troubleshoot some more.

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?