Related
So this is a weird little issue that started yesterday, same day I got my S4. Air View works fine for every app but the email app. Instead of the full text, I just see this chopped off little text bubble (see attachment). It happens on either of the two email accounts I have in the app, one exchange, one aol (yes, I am ashamed). Already tried to remove both the accounts, clear the app cache, clear app data, then re-add the accounts. Same thing. Wondering if anyone has seen this issue yet or if it's just me.
S4 is stock, no root, no nothing. Had already installed all apps and changed my launcher before the issue started. Can't think of anything off the top of my head that I changed directly before I noticed the problem. Any help would be appreciated, I get a lot of emails and would love to have this working again.
magnumburst said:
So this is a weird little issue that started yesterday, same day I got my S4. Air View works fine for every app but the email app. Instead of the full text, I just see this chopped off little text bubble (see attachment). It happens on either of the two email accounts I have in the app, one exchange, one aol (yes, I am ashamed). Already tried to remove both the accounts, clear the app cache, clear app data, then re-add the accounts. Same thing. Wondering if anyone has seen this issue yet or if it's just me.
S4 is stock, no root, no nothing. Had already installed all apps and changed my launcher before the issue started. Can't think of anything off the top of my head that I changed directly before I noticed the problem. Any help would be appreciated, I get a lot of emails and would love to have this working again.
Click to expand...
Click to collapse
it took a bit of time to get used to.....have you try to disable and reenable the airview option in settings?
my video application did that one or twice......all i did was reenabling it again....and now its working....
Ambrosios said:
it took a bit of time to get used to.....have you try to disable and reenable the airview option in settings?
my video application did that one or twice......all i did was reenabling it again....and now its working....
Click to expand...
Click to collapse
Yeah I did, but I found out what was actually causing it. I was using Light Flow for my notifications and didn't know about the existing issues when you enable it in the accessibility options.
FOR THOSE WHO DON'T KNOW about the problem caused, basically there is a known glitch when you try to turn on Light Flow under the accessibility options. It will try to turn on TalkBack, but only some of the TalkBack functions work, which made it hard to diagnose. Turning on TalkBack, disabling all the settings, and turning it back off won't help, neither will disabling the app. Since TalkBack disables settings such as Air View, some of the functionality is lost when you turn the settings back on. The author of Light Flow knows about the issue and is trying to work on it according to an in app message I glazed over the first time. In the meantime, plenty of other notifications still work if you don't turn on accessibility.
Thanks for the response though, hopefully this info will help others.
I have the exact same issue, except light flow isn't installed. Any other ideas?
Anyone have any ideas?
Tripledrop said:
I have the exact same issue, except light flow isn't installed. Any other ideas?
Click to expand...
Click to collapse
Could you have something else installed that's causing the issue? I would disable it, reboot, and try again.
I suppose there's always the possibility something else is effecting it, but unsure what! Tried what you suggested and still not working
The way I fixed the talkback issue was to freeze both Google and Samsung text-to-speech in titanium backup.
I've still never seen air view work anywhere but in the browser though. Maybe there is a setting buried somewhere, I only discovered yesterday that the toggles in motion and gestures settings also have sub-menus with settings for individual features (and also when you tap a feature name and then 'try it' there can be more settings like sensitivity for motion zoom and pan).
Do any of you have a pebble? That'd s what was causing the issue for me. Basically if if talkback is being utilized, airview will not work.
Sent from my SAMSUNG-SM-N900A using XDA Premium 4 mobile app
magnumburst said:
So this is a weird little issue that started yesterday, same day I got my S4. Air View works fine for every app but the email app. Instead of the full text, I just see this chopped off little text bubble (see attachment). It happens on either of the two email accounts I have in the app, one exchange, one aol (yes, I am ashamed). Already tried to remove both the accounts, clear the app cache, clear app data, then re-add the accounts. Same thing. Wondering if anyone has seen this issue yet or if it's just me.
S4 is stock, no root, no nothing. Had already installed all apps and changed my launcher before the issue started. Can't think of anything off the top of my head that I changed directly before I noticed the problem. Any help would be appreciated, I get a lot of emails and would love to have this working again.
Click to expand...
Click to collapse
I am using LG Tone+ wireless headphone with n9005 and because I enabled its application in the accessibility options, this error happened to me.
Please check any application that might be installed and enabled under the services under accessibility options and disable/ enable until you find the one that causes this problem.
Hope this would help.
btw, thanks guys for the tip, it gave me the idea
mofahmy said:
I am using LG Tone+ wireless headphone with n9005 and because I enabled its application in the accessibility options, this error happened to me.
Please check any application that might be installed and enabled under the services under accessibility options and disable/ enable until you find the one that causes this problem.
Hope this would help.
btw, thanks guys for the tip, it gave me the idea
Click to expand...
Click to collapse
Thanks mofahmy, but you'll see that I figured this out months ago. Also a note for any Light Flow users still having the issue, newer versions of Light Flow and GS4 roms have fixed the glitch.
when i turn on do not disturb the phone still rings ?
called Sammy and they were worthless, anyone get it to work ?
I just tried it, it was silent for me. Do you have the scheduler on?
Majin101 said:
I just tried it, it was silent for me. Do you have the scheduler on?
Click to expand...
Click to collapse
no, from what i read the scheduler is an option if you only want it on between certain hours, it should
work simply by turning it on. it says it's enabled in the pull down notification menu and there is a ∅
in the upper left corner but it still rings ?
Edit : i turned on the scheduler and it still rings. . . . . . .WTF ?
i'm beginning to think this Note 7 is a POS, so far i'm having bluetooth issues, do not disturb doesn't work,
and smart switch gives an error when trying to back up files. my Note 4 worked(s) perfectly and had zero
issues !
Do Not Disturb works for me. Are you sure that you didn't setup an "exception" to allow your phone to still ring? I just tried it and no phone call came through. The only exception I have setup is for an Alarm to sound.
Once you turn on DND, then tap on the "Do Not Disturb" wording. In this section is where you can setup exceptions or clear them out if something is setup that you did not want. Specifically check out the "Allow exceptions" section.
burrzoo said:
Do Not Disturb works for me. Are you sure that you didn't setup an "exception" to allow your phone to still ring? I just tried it and no phone call came through. The only exception I have setup is for an Alarm to sound.
Once you turn on DND, then tap on the "Do Not Disturb" wording. In this section is where you can setup exceptions or clear them out if something is setup that you did not want. Specifically check out the "Allow exceptions" section.
Click to expand...
Click to collapse
it says "No Exceptions"
That's strange, I haven't encountered that problem. Have you done anything to your phone? Did you use a package Disabler app?
yes i have PDP installed, but i only selected AT&T and other obvious stuff
ParishM said:
yes i have PDP installed, but i only selected AT&T and other obvious stuff
Click to expand...
Click to collapse
You might want to go one-by-one and reinstate items that you disabled with PDP and see if DND works again.
burrzoo said:
You might want to go one-by-one and reinstate items that you disabled with PDP and see if DND works again.
Click to expand...
Click to collapse
Agreed.
burrzoo said:
You might want to go one-by-one and reinstate items that you disabled with PDP and see if DND works again.
Click to expand...
Click to collapse
i re-enabled everything previously disabled, restarted and it still rings with DND turned on !
i think i'm gonna take it back to Samsclub and exchange it for a new one.
ParishM said:
i re-enabled everything previously disabled, restarted and it still rings with DND turned on !
i think i'm gonna take it back to Samsclub and exchange it for a new one.
Click to expand...
Click to collapse
That actually sounds like a good idea. You've had too many issues and even though I've only had this Note 7 for several days, I haven't had any problems. Samsclub has good customer service, don't they? This really is a nice phone!
Dang sorry! Sounds like a bad phone... I don't know what else could cause the issue.
a hard reset fixed the problem
apparently using Smart Switch to migrate all my apps, pics,
contacts, etc. from my Note 4 created some problems.
ParishM said:
a hard reset fixed the problem
apparently using Smart Switch to migrate all my apps, pics,
contacts, etc. from my Note 4 created some problems.
Click to expand...
Click to collapse
Hey, glad to hear this! No hassles goibg bsck to SamsCkub! SmartSwitch didn't completely copy over my old phone stuff but didn't have issues...so far!
Now you can start enjoying your,new phone for real.
Sent from my SAMSUNG-SM-N930A using Tapatalk
works perfectly for me; only exceptions are phone/text from GF.
So I just updated my phone to G935tuvu4apia_tmb using the guide in the Tmobile Galaxy S7 Edge Development forum, and then I proceeded to Uninstall a bunch of bloatware and system apps (because package disabler pro doesn't work on G935tuvu4apia_tmb for me for some reason). I had accidentally deleted something called "Universal Switch", then, stupidly.. I had already deleted all of the backups for the things I had uninstalled before I had run through my phone making sure I didn't Uninstall anything important by accident. Lo and behold, it turns out that I need Universal Switch. Does anybody have a way that I can download and reinstall that on my phone? I would really rather prefer not to have to go back and refresh everything using Odin, as I literally just finished restoring, logging in, personalizing, and setting everything else up on my phone, and that took me a day and a half. So if anyone has a way for me to reinstall that on my phone I would greatly appreciate it, and I have definitely learned my lesson through this whole experience. I posted a picture of why I think I need Universal Switch, if I'm just crazy, and misunderstanding the issue I'm having then I'd appreciate someone informing me and educating me on the matter. Thanks again.
So I couldn't figure out how to attach a picture to this post, so here is a link to the screenshot of the issue I'm having.
I can't post outside links yet, so put a "Dropbox" and a ".com" in front of the text below to complete the link.
/s/agxc4us9iodrtgw/Screenshot_20161020-015632.png?dl=0
I think that is just the text to speech......
Universal switch is for smart switch I think. Not sure
Sent from my SM-G935T using Tapatalk
Solution?
Well if it's just tts, do you know of any solution for getting passed this thing on my phone? If you check out the screenshot I linked, the issue is, whenever I go to settings, accessibility, scroll all the way down to services, then try to turn anything in services on, I get that pop up, then I click turn on on that pop up, and then it says "unfortunately settings has stopped". I am unable to turn anything on under services in the accessibility settings. There, that is a vast improvement from my original post of the description of the issue I am having. If I click on settings on the pop up, it goes to the tts settings page and just sits there loading forever.
Package Disabler Pro and disable it... Turn it off under Inputs....
As for the services issue... maybe reflash only the AP of the rom, which I believe keeps all apps and internal storage... That should fix that issue... You will have to reconfig your ish, but that should fix and farks....
It honestly sounds like you have a corrupt install to begin with because you CAN'T use Package Disabler.. Did you try the different ones?? I know one did NOT work for me as well... then one did...
This weird app (device quantity agent) was pushed to my phone from the galaxy apps store as a critical update just a few ago, anyone know what it is?
msburr87 said:
This weird app (device quantity agent) was pushed to my phone from the galaxy apps store as a critical update just a few ago, anyone know what it is?
Click to expand...
Click to collapse
Same here.
ahh so thats the "critical update" i declined. Was wondering what it was since there were no apps that needed updating in the store. Wonder what it does
It's update for fixing DQA keeps stopping issue.
I had mine suddenly download and install 3 things from the galaxp app store yesterday without me knowing anything about it. Personalized service client, samsung pass, and LED view cover icon editor. I thought I had been hacked and someone was downloading sutff to my phone!! No idea why it suddenly started doing that by itself. I have turned auto update apps off now in the galaxy app store, I guess they were already installed and were just auto updating (and i have no disabled them all in package disabler since they all seemed like junk).
I dont know what DQA does, wonder if its another one we can safely disable.
ewokuk said:
I dont know what DQA does, wonder if its another one we can safely disable.
Click to expand...
Click to collapse
From what I understand, DQA has to do with checking the quality of your Wi-Fi. You'll notice if you turn your Wi-fi off, you'll stop getting those messages. Some have had success with going into your running Apps and force stopping the DQA. That didn't help me though and rebooting several times (which has also helped some) didn't work for me either. Still working through options. If anyone has other ideas...
RTBee said:
From what I understand, DQA has to do with checking the quality of your Wi-Fi. You'll notice if you turn your Wi-fi off, you'll stop getting those messages. Some have had success with going into your running Apps and force stopping the DQA. That didn't help me though and rebooting several times (which has also helped some) didn't work for me either. Still working through options. If anyone has other ideas...
Click to expand...
Click to collapse
I havent had any issues with or or any messages about it either before it updated or after. I usually have wifi on but have turned it off today and not noticed anything either. I have not disabled it in package disabler as i didnt know what it did, it doesnt seem to be using battery so i will just leave it on.
This is what I've found from Android Authority...
- Reboot device (may need to repeat a few times)
- Clear cache partition through recovery (turn off phone, press and hold Power, Volume Up and Bixby button. On Android screen, when you see ‘No command’ hold power and press volume up to access recovery. Use volume keys to highlight ‘Wipe cache partition’ and press Power to select. Highlight ‘Yes’ and press Power to confirm, then reboot phone)
- Turn off Wi-Fi
- Disable high performance mode
- Force quit DQA app (go to Settings > Apps and tap the overflow menu (three dots at the top right), tap ‘Show system apps’ and locate DQA. Tap it and ‘Force stop’)
- Disable DQA app with BK Package Disabler (costs $1.50, does not require root). Install app, grant permissions, swipe to System tab, find DQA and check the box next to it (simply uncheck to re-enable).
I haven't tried all these options yet. Let me know if any help should you decide to try.
I'm bumping this topic. Tried googling DQA, but very little seems to be known about it. If it indeed is checking the quality of the wifi, is it really safe to disable?
eried1 said:
I'm bumping this topic. Tried googling DQA, but very little seems to be known about it. If it indeed is checking the quality of the wifi, is it really safe to disable?
Click to expand...
Click to collapse
Hi, have you found any info regarding DQA? I found it among the recommended apps to disable/uninstall on Universal Android Debloater, but still I read somewhere that some of the apps disabled through UAD might be important, so I'm not sure about what to do.
NovaProspekt70 said:
Hi, have you found any info regarding DQA? I found it among the recommended apps to disable/uninstall on Universal Android Debloater, but still I read somewhere that some of the apps disabled through UAD might be important, so I'm not sure about what to do.
Click to expand...
Click to collapse
No. I'd leave it active.
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?