I have a OnePlus 7 Pro, and was able to get Google Call Screening working on it somewhat. The only issue I ran into is the Google Assistant volume is really low on the caller's end. It seems a lot of people who attempted to get this feature ported to other devices were not able to hear the Google Assistant at all on the other end. This was true for me as well when I attempted to get it working on the OnePlus 6T when I briefly had the device. To be able to hear the Assistant at all so far is more success than I had initially hoped for.
I posted a thread in my phone's forum of my findings. My hope is that it will drum up interest and hopefully get smarter people than me interested in looking for a solution. So far, no dice. My guess it the answer might be in the mixer path and audio policy files. These should be in /vendor/etc or similar (might be different on Pixel). All .conf, .XML, and .txt related to audio or mixer path would be helpful. I'm looking to compare them to the ones in my device to see if I can figure out how the Google Assistant might be output to the caller. It could be a dead end, but in the absence of anyone else looking, I figure it can't hurt to try.
Related
First of all, let me say that not only am I new to android, I am also new to smartphones in general. So when - in your amusing video, which I quite enjoyed watching - you say 'noob'...I mean NOOB!
I have Googled this problem extensively and have posted this question on 5 other android support forums over the last month or so, and although it seems (from my research) many people have this or a similar issue, no-one has come up with a solution. A forum memer from one of those websites has now suggested I post this here. I have, before posting, searched this site also for a solution, but it appears that although some have a similar problem, there has not yet been a solution found, or the advice given hasn't worked in my case.
So here's hoping somebody here can help with this irritating and inconvenient issue:
Device: Samsung Galaxy Ace
Carrier: Virgin Mobile
Country / Language: UK/English
OS / Browser / build number: Android Gingerbread 2.3.3
I am having the problem where I have set custom ringtones for some of my contacts, but they are not always being played as they are assigned.
I have all of my ringtones in an folder on my sd card (/sdcard/ringtones, having moved them from /sdcard/media/audio/ringtones to see if this solved the issue. It didn't)). I have a custom ringtone (mp3) set as the default ringtone and a couple of other custom ringtones set for a few of my contacts. However, when I receive a call the phone does not play the correct custom ringtone for that caller but instead plays the custom ringtone assigned to the previous person that called. If the caller is also the previous person to have called me, then it will play the correct ringtone, as they are the previous caller. (If that makes sense??)
To reproduce: Basically I install some mp3s onto my SD card. I go into my contacts, choose a contact, then click 'edit'. I then set the desired ringtone as the custom ringtone for that contact and click 'save'. When that contact rings, instead of the assigned ringtone, my phone plays the ringtone of the person who called me before that. When the next person rings, it plays the ringtone it should have played for the last contact. And so on. When I check the details for that contact, it confirms the ringtone I had chosen is still selected for that contact, it just doesn't play that one, but the one of the previous caller.
In addition to posting on Android help forums, I have also reported this bug to Samsung, although I'm not convinced it is a Samsung problem as clearly (according to my research) it is happening across the board with several other makes of Android phones. However, the reply I received from Samsung was:
"Thank you for contacting Samsung. As of yet, Google has not developed a fix for this fault so we may have to have the phone taken in by one of our engineers without any real guarantee it will be resolved. We could set this up for you but you may have to wait 28 days for the phone to be returned to you."
I am sorry, but I think it is unreasonable to be expected to give my phone up for a month, with no guarantee the issue will be sorted, just to be able to use a facility Samsung state is already available on the phone when it is clearly not.
I am inclined to believe this is an Android problem, and therefore would really appreciate any advice/a fix/solution anyone on here may be able to offer.
Thank you.
This problem - or lack of a solution - is really annoying me now as no-one seems to have a fix for it. I have over the last month posted on 6 forums: Android Central, Android Forums, Android Community, Google Android Support, OHA Project Issues and XDA developers. In total the post has had over 2500 views but NO solution!
I have also submitted the issue to Samsung - they don't know how to fix it either!
Have I got the only unfixable problem ever to affect an android phone??!!
I just don't understand why the developers of both the phone and the operating system can't solve a problem in their own product!
PLEASE, can anyone help?
"Have I got the only unfixable problem ever to affect an android phone??!!"
Looks like it
Thanks for all the interest. Not.
Well. I was advised to post this question on here by a couple of other Android forums, as they said you guys love trying to find solutions to this kind of thing.
But not even any interest or replies or even acknowledgement, least of all any suggestions.
Guess those Android forums just got it wrong.....
It might be true that Samsung can't do much to fix this, it's clearly a software problem and maybe it has not been fixed by Google (or maybe it has been fixed and you don't have the OS version that has the fix, i.e. Gingerbread 2.3.6/2.3.7)
I'm sorry to see that nobody replied to this yet, but the reason might be simply because nobody really knows how to fix (if possible) this problem. Again, this is a software problem and Samsung doesn't have much to do here, so you could try and flash a newer OFFICIAL rom for your Ace, as custom roms might have some other bugs. (You could try with CyanogenMod maybe?)
I hope you can find a way to make it work good luck.
Device: Samsung Galaxy Ace
Carrier: Orange Romania
OS: Android Gingerbread 2.3.3
I too have had a similar problem: when a normal contact calls it uses default ringtone... when a custom ringtone contact calls after that, the same default ringtone is used... if the custom contact calls again the custom ringtone is used.
Possible solution:
Put all ringtones in SDcard/Media/Audio/Ringtones
Go to Contact -> Edit -> Ringtone -> select Sound -> browse SDcard/Media/Audio/Ringtones and select your custom .mp3 file -> Save Contact
Test to see if it works and then reboot and see if it still works.
Please reply or press Thanks button to let me know how it turned out
ybres said:
Device: Samsung Galaxy Ace
Carrier: Orange Romania
OS: Android Gingerbread 2.3.3
I too have had a similar problem: when a normal contact calls it uses default ringtone... when a custom ringtone contact calls after that, the same default ringtone is used... if the custom contact calls again the custom ringtone is used.
Possible solution:
Put all ringtones in SDcard/Media/Audio/Ringtones
Go to Contact -> Edit -> Ringtone -> select Sound -> browse SDcard/Media/Audio/Ringtones and select your custom .mp3 file -> Save Contact
Test to see if it works and then reboot and see if it still works.
Please reply or press Thanks button to let me know how it turned out
Click to expand...
Click to collapse
Thanks, but I had already tried this in the beginning, but no luck
I'm sorry to hear that... That exact method helped me. It may still have a glitch every week or so but it doesn't happen very often.
unbelievable, looks like there is truly no solution.. screw everything that Android has to offer if something as trivial as this can't be fixed.
So I am a bit of an audiophile. I like my music, but I can't get DSPmanager to work. I'm running CNA 1.5.5 with Matr1x kernel. I flashed the zip for it and it shows up, but selecting anything doesn't make a difference. I know what to listen to as well.
So I have been using poweramp lately. Can anybody help me figure this out?
Same problem here, but here's something of use.
I have CNA on my Moto Atrix 4g, and I have that same exact problem. I looked around in my /system/apps/ folder and discovered that it wasn't there. After manually making DSPManager.apk a system app (which is the only way to make it work on other ROMs), I discovered that there is already an Equalizer app called AudioManager.apk or something like that, and it is the only equalizer that will work on CNA. Sadly, it is not designed to be a User app, meaning you can only open it from another application (i.e. in Google Play Music going to Menu>Audio is the only way to access it). It does include a 5-Band Graphic Equalizer (with presets) and Bass Boost and 3D Sound Sliders, which work pretty well. Sorry I couldn't provide you with an answer that completely solves your problem, but I hope this helps!
Hello Ladies n Gents
I have a problem on my galaxy note.
Recordings on my phablet are horrible because of AGC (automatic Gain control).
I even bought IkMultimedias iRigMicCast. It works on the galaxy note, cuz its simply plugged to the headphone jack.
Even if I connect my Rode NT-1A condensor mic via my tube-microphone-pre-amp via an old videocable (4-pole to cinch) to the galaxy note it sounds horrible (like a grammophone) in apps that record videos because those apps dont have the option to disable AGC. In audio recording apps that are able to disable AGC it sounds pretty good.
Now I found a file called /system/etc/audio_effects.conf.
Im a newbie to Android, but I know a lot about linux. So i dont have the courage to try this out myself:
I just purchased my galaxy note and dont want to be stuck at boot time. I dont have the time to set it up again right now. I dont know if any other configuration files fail to load without this agc part. Then I might be stuck at boot time. Maybe simply the audio configuration fails and I can simply take a backupped file and my configuration is reset to the status before.
So here is what I think might work:
I GUESS /system/etc/audio_effects.conf is used to tell the system which audio effects to load.
In there you find this piece:
# list of effects to load. Each effect element must contain a "library" and a "uuid" element.
# The value of the "library" element must correspond to the name of one library element in the
# "libraries" element.
# The name of the effect element is indicative, only the value of the "uuid" element
# designates the effect.
# The uuid is the implementation specific UUID as specified by the effect vendor. This is not the
# generic effect type UUID.
# effects {
# <fx name> {
# library <lib name>
# uuid <effect uuid>
# }
...
agc {
library pre_processing
uuid aa8130e0-66fc-11e0-bad0-0002a5d5c51b
}
I think, if agc is diabled in this file, it is disabled system wide. I dont know if this has any influence on other things like call mic quality etc.
To disable it I'd put some '#' without the quotes in front of all four agc lines.
After reboot the new audio configuration without AGC may be loaded and recordings may be as good as the device is able to.
Maybe someone wants to try this out or better: an android developper could tell me if this is wrong...
If you tried it out, plz post your experiences here...
Good luck
drz
Firstly, you've already posted exactly the same thing in the Galaxy S2 forum http://forum.xda-developers.com/showthread.php?t=1172048
Secondly, why would you ask someone else to try out something that MIGHT break their phone when you aren't willing to try it yourself? Either be a man and grow some balls or don't, but don't expect someone else to do your dirty work for you. :banghead:
SimonTS said:
Firstly, you've already posted exactly the same thing in the Galaxy S2 forum http://forum.xda-developers.com/showthread.php?t=1172048
Secondly, why would you ask someone else to try out something that MIGHT break their phone when you aren't willing to try it yourself? Either be a man and grow some balls or don't, but don't expect someone else to do your dirty work for you. :banghead:
Click to expand...
Click to collapse
Im sorry I wasted your time.
Im trying to get an answer from someone who knows something about the android audio system. Especially the soundsystem, as you can read. Maybe someone disabled some other modules from this conf file.
If you dont like this question (and its meant as a question, thats the reason , why theres a big q in the title and a question mark behind it) dont read it. In the quoted other thread they even give bounties for a solution, so why not give out my try of a solution for free. Even if it might be a risk.
no need to call someone names, I guess, isnt it?!
Have a nice day and plz dont play some kind of thread police. I just wanted to ask this question in an own thread. I hope this doesnt get me in forum jail or something. Calm down.
greetz
drz
ok, now I found the time to try it out myself.
It seems to have no effect. Although I think in the stock camera app, agc seems to be disabled.
But I cant really tell, because sound the sound in the stock video cam is absolute crap.
So either the modification of audio_effects.conf has no effect at all, or other video apps like lgcamera and other have there own agc algorithm, which is crappy, too, or they have their own way to activate agc, if its not available.
If anyone has any other ideas how to disable agc, youre welcome.
greetz drz
Hi everybody.
I've owned A LOT of Android devices, i think this phone will be my number 22 Android phone through time
I've also tried Iphone 3G back in the days (BVADR..), and a couple of Windows Phones..
Bluetooth music streaming in both Windows Phone and Iphones, are really good. It is so good actually, that i don't even bother putting in my AUX cable, because i can't really hear a great difference.
On any Android i tried (not with CM10 back in the days), there is clearly a quality downgrade! It must be something that bother others as well??
Now i know that the Bluetooth music streaming in Android is, well the most unacceptable piece of sh..t that ever was produced , but it bothers me that the only Rom that fixes this, and keeps fixing it, is CyanogenMod. Don't get me wrong, i really like CM 10, 11, 12, but i like Sony's "skin/template" a Little bit better, and would like to keep using that.
I have however reached a point now where i will do just about anything to fix the bluetooth music streaming in my new car. So i will, if i have to install CM12 on my Z3 and Loose a lot of the great features (camera) just for the bluetooth fix.
Before i do it though, isn't there a developer in here that knows where to fix this in general for the Lollipop release? It would be really great to have a BitPool fix, where we can overwrite some system files, or install a zip in recovery, or a Little app that could set the BitPool easy for us..
I'm not a developer but do Work in the IT businness and will of course be able to be beta tester or help in any way that i can!
If a developer can even pinpoint me to which files i need to change, i can go ahead and root my Z3, and do it myself. Would even put in a nice PowerPoint guide (and i'm really not the PowerPoint guy ), so that others can do it too.
Please help a frustated Android bluetooth user
this isn't development and should be in the Q&A section, i've reported this so a mod can move it to the appropriate place
All right thank you. I hope that developers look in the q&a section then
I've installed I think around 7 android headunits and every single one has had a Bluetooth phone app that was bad to use.
Last year I tried to find a better one, without luck.
Any recommendations?
Nope but is it an FYT based headunit - post Android system information including MCU version to understand what variant the unit might be and what bluetooth your device has.
FYI - Bluetooth is not standard in these units.
marchnz said:
Nope but is it an FYT based headunit
Click to expand...
Click to collapse
One that I'll insult tomorrow is, yes.
Edit: I'm also "installing" it tomorrow.
spludgey said:
I've installed I think around 7 android headunits and every single one has had a Bluetooth phone app that was bad to use.
Last year I tried to find a better one, without luck.
Any recommendations?
Click to expand...
Click to collapse
I don't have any bluetooth issue with mine after the aug update. (finally)
spludgey said:
One that I'll insult tomorrow is, yes.
Edit: I'm also "installing" it tomorrow.
Click to expand...
Click to collapse
Oh that poster had no intention of helping you, they just couldn't wait to tell you that you had posted in the wrong forum.
As for bluetooth implimentation, other than changing the variable in config.txt's sys.fyt.bluetooth_type= entry. They may not be any more you can do.
spludgey said:
I've installed I think around 7 android headunits and every single one has had a Bluetooth phone app that was bad to use.
Last year I tried to find a better one, without luck.
Any recommendations?
Click to expand...
Click to collapse
Not sure what exact function you are missing, but I used this one to install my OBD scanner (Vlinker) that the head unit would not connect to.
Bluetooth Finder, Scanner Pair - Apps on Google Play
Find and pair your bt device. Find your headset, smart band or earphone easily
play.google.com
ludditefornow said:
Oh that poster had no intention of helping you, they just couldn't wait to tell you that you had posted in the wrong forum.
As for bluetooth implimentation, other than changing the variable in config.txt's sys.fyt.bluetooth_type= entry. They may not be any more you can do.
Click to expand...
Click to collapse
No one could establish the unit to be FYT based on this post.
without that info recommending a configuration setting which is applicable only to FYT based units is just as useless. I request you stop making assumptions about my posts as you might be lacking prerequisite knowledge.
Knowing what the unit is, is everything. A cursory read thorough MTCD forums show just how misunderstood it is, and without my posts and reporting to moderators the forums quickly fill up with out of topic posts and the real development falling off.
If every new post started with, my unit is "ANDROID SYSTEM INFORMATION + MCU version" then those that actually know could recommend and not enter a tool like guessing game.
Would be great if you begun assisting too, if not, not a problem and if you don't like a post the report button is always available to you.
This is my last post on the matter with you.
spludgey said:
I've installed I think around 7 android headunits and every single one has had a Bluetooth phone app that was bad to use.
Last year I tried to find a better one, without luck.
Any recommendations?
Click to expand...
Click to collapse
For a hands-free bluetooth dialing app that works with FYT 7862 head units, I recommend the free "Voice Call Dialer" by ArtostoLab, which is available on the Google Play store. It allows you to say the name of the person in your contacts list that you want to call on your cell phone over the Bluetooth connection, and it confirms the contact's name by displaying it as it counts down from 3 seconds (you can configure this value) before it initiates the Bluetooth phone call.
Previously I used the Google Assistant to make calls, but when I upgraded my old PX5 to the Joying 7862 10.5 inch 1280x720 head unit I found that the only way I could get Google Assistant to make call using my voice was by setting the "Smallest Width" DPI value in the "Developers options" to a value of 596 or less, and using an older dialing app called "GVC Callhandlert 4 Joying" which is described here:
Joying forward dial requests from Google Voice
By replacing the old GVC dialing app with the Voice Call Dialer, I am now able to set my screen to full resolution, with the "Smallest Width" DPI value set to 720 DPI. I am not able to make a voice call _directly_ from Google Assistant, but I can tell Google Assistant "Voice Dialing", and then I can just say the name of the person I want it to call.
Edit: I had a typo in the open command, and the word "open" is optional.