Related
Hi all,
The effect I'm looking for:
While an open phone call, I'd like to be able to play sounds into the call stream so that (similiarly to the in-call DTMF tones) the sounds would be heard by the other party.
My questions:
1) Is this possible without modifying phone.apk (or what ever system .apk needed to gain access to the call stream)? Does it help if the device is rooted?
2) If not, is it at all possible? What would it take to achieve such an effect?
Any help would be much appreciated.
Need a solution too, looking into reflection.
This is rather old but I was wondering if there's any news? I searched for anything related to call, stream, DTMF etc. in XDA and everywhere else I could think of.
So far I found nothing. Is there really no way to send tones up the call stream?
I'm looking into the source code to see whether I can use some reflection, even just to see if it works. The best bet seems like CallManager..
It has 'SendDtmf' and 'StartDtmf' that automatically goes to the active call, gets the active phone from it and shoots up the tones.
HOWEVER I got stuck. Both methods keep returning false. Digging into it you see that both methods check whether there are any active calls before sending anything. So I tested it myself and here lies the issue - 'HasActiveFGCalls' (and HasActiveBgCalls too) returns false no matter what.
In fact, getting the full call list (getForegroundCalls) always gives me an empty list.
I tested it on my phone (SGS, CM7) and on the emulator on several versions. Same results - always no active calls regardless of whether the phone is in a call or not.
I'm at a loss here. Seems like this is as far as I can go with my knowledge at the moment.
So... anyone has any clue regarding this?
Hello,
Did Samsung ever fix the low level volume fluctuation problem through the headphone connection on the 7.0+? Listening to lower level music files at lower volumes resulted in the volume jumping up and down slightly. The problem occurs regardless of whatever music player app is used. The files play fine on the Samsung Galaxy 5.0 player and other devices.
Thanks!
Update: It's not fixed.
This thread is the only reference I could find to this issue anywhere. Is it documented more fully somewhere else? Is Samsung aware of it and planning to fix it? Any references or other help would be greatly appreciated.
I've had my 7.0 Plus for about a week, and yesterday was the first time I tried listening to some classical music favorites featuring very soft choral passages. I couldn't. The volume surges every couple of seconds during soft passages. It sounds as if some demented engineer thought it would be a good idea to add an automatic volume equalizer to make sure the music never gets too soft. No. Very bad idea.
Until I found this thread, I thought I had a defective device or was losing my hearing. I'm glad that neither is the case. Again, please post links to further info about the issue. TIA.
Sun_Cat said:
Until I found this thread, I thought I had a defective device or was losing my hearing. I'm glad that neither is the case. Again, please post links to further info about the issue. TIA.
Click to expand...
Click to collapse
I've had the same problem with 6210 from day one. Other than album art being screwed up, it's the only real annoying problem I've had with the box.
The problem may be in the default player. I use poweramp and don't experience that
Sent from my DROID BIONIC using XDA
It's not just the default player. I've experienced it in the Rhapsody app too. Also see the OP, which says regardless of app and also strongly imples that the issue has been discussed before.
Sun_Cat said:
It's not just the default player. I've experienced it in the Rhapsody app too. Also see the OP, which says regardless of app and also strongly imples that the issue has been discussed before.
Click to expand...
Click to collapse
I hear it using TuneIn Radio. Hoping for a fix with ICS.
UPDATE
I've found two earlier references to the issue:
A review on Amazon from last November (reviewer says he's notified Samsung)
A post by this thread's OP, also from November (like me, he thought it sounded like Automatic Gain Control; unlike me, he remembered the right name for that feature )
Again, any more references, especially from Samsung, would be appreciated.
ETA: I found one on the Samsung support page (search for the string "How can I stop the volume" and click on the text to open the answer). It was answered, not by Samsung but by an anonymous user, who said "Sorry charlie, but you've got a headphone jack with a malfunctioning sensor. Sorry!"
I suppose that's a plausible explanation, but against it is the Amazon reviewer, who said he had the same problem with two different units. And then there's me and the OP here.
redsmear said:
The problem may be in the default player. I use poweramp and don't experience that
Click to expand...
Click to collapse
I installed Poweramp. Nice app, but it doesn't help with this problem at all.
To hear the problem you have to be playing music with sustained passages that are very soft. With most pop, rock, and jazz it won't be noticeable. That's probably why the issue isn't more widely reported.
Try this video in your YouTube app. If your Tab Plus is behaving like mine, you'll hear several volume surges during the first 20 seconds or so. ETA: Crap! I can't post outside links. Here's the last part of the YouTube URL, after the slash: watch?v=6-i1ESIRKdA.
One more clue
And I found one more indirect clue in the Samsung Troubleshooting Guide under the heading GT-P6210 Volume Drops When Headphones Are Plugged In:
The volume on your Tablet will drop 75% when you plug in your headphones. This is a preventive measure for acoustic shock to your ears. The volume can be increased after the headphones are connected.
Click to expand...
Click to collapse
Obviously this proves nothing about the issue we're discussing, but it is suggestive because it tells us that something in the firmware is deliberately designed to mess with the headphone volume.
Aha, so it's not just me who noticed this "feature" then
For anyone who is experiencing this issue and wants to let Samsung know about it in one place, I've started a public thread on their Facebook support wall. You'll have to imagine the first part of the usual Facebook URL since I can't post links. Here's the last part, after the slash: samsungsupport/posts/10150588609036213
Nothing from Samsung Support on Facebook since yesterday morning. One other person has posted there (thanks, Mark, if you're reading this). It would be nice if a few others would chime in.
I'll chime back in. I'm glad somebody else has finally noticed! The problem also exists with the Verizon SCH-i810 (Tab 7.7) but, perhaps, to a lesser degree.
I strongly suspect the (Yamaha?) driver and/or its configuration -- see the original post from November that shows the (configuration?) files. I suspect that file may hold the key to the problem. Problem is, I have no idea what the numbers actually mean and didn't find any documentation for those numbers (data sheets, etc.). I did attempt at the time to tweak a few numbers using my "best guess" by comparing the entries for rx-speaker vs. rx-headphone vs. rx-headset. but no discernible effect was heard.
No prizes for guessing who was raising such a fuss in November.
The "Sorry Charlie" answer is incorrect and I flagged it as such.
UPDATE: I found the 7.0+ /etc/audio files and I have the 7.7 /etc/audio files. There are some differences in the numbers and the 7.7 audio files (LVVEFS) have some comments (!!!) in them so maybe I can track down pertinent parameters.
Anyone else have an opinion or another idea? Is this a waste of time?
Thanks again to everyone who posted here. If you've been watching the Samsung wall on Facebook where I posted last week you've noticed that they haven't responded at all except to ask one simple question, which I answered immediately. Since then, crickets.
If you're experiencing this issue and you feel comfortable saying so in public, please add your comment to the post on Facebook. Maybe we can guilt them into responding.
Thanks.
Sun_Cat said:
Thanks again to everyone who posted here. If you've been watching the Samsung wall on Facebook where I posted last week you've noticed that they haven't responded at all except to ask one simple question, which I answered immediately. Since then, crickets.
If you're experiencing this issue and you feel comfortable saying so in public, please add your comment to the post on Facebook. Maybe we can guilt them into responding.
Thanks.
Click to expand...
Click to collapse
They just answered about 1/2 an hour ago. They provide a link and ask us to go to the Samsung Service Facebook page and fill out a support form. Might as well. Keep the pressure up on someone over there.
Agreed. I just submitted their form with full details. We'll see whether they follow through.
A hint to anyone posting there: Samsung appears to be great at stalling by asking follow-up questions. Include as many pertinent details as possible in the initial post, such as model, wi-fi or data-enabled, serial number, firmware, streaming or stored music sources, which apps, etc., etc., and so forth.
Well, at least they're responding, but I'm not sure it's helping. This morning they replied to my original Facebook post:
We can suggest checking to see if the same problem occurs in a different set of headphones or speakers. If the problem persists we will suggest servicing your Tab.
Click to expand...
Click to collapse
I've already checked with different headphones (not speakers; I've already told them several times that it's a headphones-only issue!), so I already know that the problem isn't due to one set of headphones.
This gives me zero confidence that they actually understand the issue. (Except that it's possible -- though in my view unlikely -- that it is a defective headphone jack.) I'm reluctant to send it in for service. The problem is subtle enough that someone lacking a trained musician's ear is likely to just say it's fixed and send it back. We already know that the fellow who mentioned this issue in his Amazon review got a second unit exhibiting the same defect.
Also, I have not heard from Samsung directly in response to submitting the official support form the other day, so I can't now tell whether or not this latest comment on the wall is coordinated with that other support request.
Does anyone have any advice? Has anyone here dealt successfully with Samsung support in the past, on any issue at all? How did you do it?
Sun_Cat said:
...This gives me zero confidence that they actually understand the issue. (Except that it's possible -- though in my view unlikely -- that it is a defective headphone jack.)
Click to expand...
Click to collapse
I agree. I don't believe it's a headphone jack issue either. I'm going to wait until ICS comes out and then decide what to do if it's still an issue.
I've tried adjusting some numbers in the .txt files -- no change yet. Maybe I'm adjusting the wrong file. Who knows?
I'm surprised there aren't more complaints. It's easy to identify. Headphones, earphones -- doesn't matter. The problem exists with Samsung's earphones. They can't run away from that one. Doesn't the 7.0+ come with four audio files? I can't recall if the problem could be reproduced with those files, because the problem needs periods of relative silence to get into the "AGC" mode. I think the Samsung support is in typical "denial mode". Problem? What problem? Let's go through all the permutations of user error or workaround before considering that there is a problem. It's a matter of problem ownership -- and Samsung isn't owning it.
The questions I would ask are: "Have you tried reproducing the problem?" "Do you know how to reproduce the problem?" "Who has the capability to reproduce the problem, if you can't".
Yes! Just found the Samsung music files, going to try to reproduce with all Samsung supplied software and equipment.
UPDATE: Reproduced the problem on Galaxy Tab 7.7 with all Samsung supplied files/software/equipment:
MATERIAL:
1. Samsung supplied "Music Player", no EQ
2. Samsung supplied music file "Silky whisper.mp3"
3. Samsung supplied earphones, white with button and mic (I think it's pretty generic to Samsung)
Steps:
1. Start Music Player.
2. Make certain volume is all the way down and the sound is muted (slash through speaker)
3. Press the volume up button once, twice (once to unmute and one step higher)
4. Play music file. Note how the piano cuts in and out throughout the song, especially during the opening of the instrumental.
I suspect that Samsung is going to hand this issue off to Yamaha. The constant in this matter is the Yamaha-sourced audio chip/driver/library/configuration/firmware.
Here are some files to compare from /etc/audio (I added the model to the name):
TonyBigs said:
It's a matter of problem ownership -- and Samsung isn't owning it.
Click to expand...
Click to collapse
Agreed. That's why my first question to them on Facebook was "Are you aware of the problem?" No way will I send my GT7+ to them for service until they take that step.
I'll try your steps later today and see if I get the same result. Maybe we can gang up on them.
I have one additional datum since last week. I've tried to reproduce it on Bluetooth headphones, and the problem does not show up. It's only there with plugged-in headphones.
I suppose this could be interpreted as evidence slightly inclining toward the "defective headphone jack" theory. But I still don't think so. If anything, I think it could be related to the Self Aware Volume Ghost on the Galaxy Nexus, which Samsung apparently did acknowledge. Except the Nexus bug was much more obvious since the volume control indicator actually appeared on the screen and changed.
Anyone here use this app? Its nice but confusing as hell to operate and the site doesn't give much insight.
Recording videos is easy enough but when you stop the recording is when it gets tricky. Its not as easy as 'save/discard' the video. You have to find it in the 'file' tab, then decide what to do with it. I long hold and click 'retain' but it disappears. I have tried numerous times to figure this thing out to no avail.
Does anyone at all have any insight to this or maybe even another comparable app that is easy enough to understand?
Thanks!
i've downloaded the app, but haven't had the chance to test it out yet (no car mount). it locked in the gps signal, so i tried running around the house to see if the mph/kph will change. Nope, nada. Will test inside the car soon.
The menu seems to be rather straightforward, no issues that I've came across yet.
Hey everyone,
I'm having issues with echoing on both speaker/headset modes. I've tested it by calling my house phone from my personal phone, while spacing them across the house.
The results I found was that the echo is heard on both sides, but it is much more apparent listening from the house phone. Having the case on doesn't seem to affect it.
I tried using different applications, but it didn't make a difference. The ones I tried were Freetone and Hangouts; both had the problem.
I'm currently on the latest night build from SultanXDA.
Does anyone have ideas on what could be happening and how to fix it? I searched both google and XDA. I tried changing the audio platform / mixerpaths xml, but
altering the audio platform xml did not do anything and I could not find a mixerpaths xml what was for Android 5.1.1.. It'd be nice if someone could shine a light upon
the problem. Thanks.
The Problem: On many non-Samsung phones, all calls, even when answered on the phone itself, get sent to the watch's speakerphone, requiring the user to manually switch the sound back to the handset every time a phone call happens. As a side problem, the watch conflicts with other Bluetooth devices capable of of being used for calls, like car stereos and headsets. Several threads on xda and elsewhere discuss these issues; however, the only solution posted is to disable the "Phone Audio" profile of the watch in settings. This is sub-optimal because it completely disables the ability to use the watch as a phone speaker.
The Solution: I have put together a series of Tasker profiles and tasks that utilize the BlueTask plugin to control the connection of the Gear S3. A convenient detail about BlueTask's disconnection method is that it only seems to affect the "Phone Audio" component of the Gear S3, leaving all other functionality untouched during a call. I use the proximity sensor to determine whether or not the call is being made/answered on the phone itself vs the watch. The assumption is that if you leave you phone in your pocket, bag, or face down on the desk, then you answered the call via the watch. I understand this is not a perfect method for determining which device is answering the call, but it works pretty well in my testing. In addition, an exception is made for when a wired headset is hooked up to the phone, as one may leave their phone in their pocket while answering using such a headset. Finally, an additional profile I call the "Car profile" will automatically disconnect the watch and disable its Tasker profiles while connected to specified Bluetooth devices like a car stereo, Bluetooth headsets, etc.
Setup:
Re-enable "Phone Audio" for Gear S3 if you previously disabled it (Settings>Bluetooth>Gear S3)
Install Tasker (if you haven't already)
Install BlueTask
Go to Tasker>Preferences>UI>Beginner Mode. Disable it (if it is not disabled already).
Go to Tasker>Preferences>Monitor>Display Off Monitoring>Proximity Sensor. Set it to "Yes"
Download the Tasker project attached to this post to your phone
Import the project into Tasker (Press and hold the home tab in the bottom left corner of tasker and then click Import)
Enter the new "Bluetooth" project and open "Car Profile" in "Profiles"
Delete the Dummy MAC address in the Profile and replace it with the MAC addresses of any car stereos and/or bluetooth headsets you use with your phone. If you have multiple of such devices, separate each address with a "/" (the magnifier glass icon does this for you). If you have no such devices, feel free to disable or delete this profile.
Open "Disconnect Gear S3" in "Tasks"
Open the "BT Connection" action
Replace the dummy information with your Gear S3's Name and MAC address
Repeat steps 10, 11, and 12 for the "Connect Gear S3", "Car Mode", and "Exit Car Mode" tasks.
Complete!
Let me know if this works for you. Also, suggestions for how this project could be improved are welcome.
Its works fine on #LGV20 so no need for this fix.
Sent from my LG-H990 using Tapatalk
I've downloaded the project to my phone but when I launch tasker and try to import the profile I can't find the file, even though I can see it using a file explorer. I've changed the.Prj to .prf and Tasker sees it but when I try to import it it gives me an error that says the for contains multiple projects.
Any help would be appreciated, thank you
OneRealDaniel said:
I've downloaded the project to my phone but when I launch tasker and try to import the profile I can't find the file, even though I can see it using a file explorer. I've changed the.Prj to .prf and Tasker sees it but when I try to import it it gives me an error that says the for contains multiple projects.
Any help would be appreciated, thank you
Click to expand...
Click to collapse
Is it downloading as a .prj or .prj.xml ? It should be the latter. If it isn't, rename it to have a .prj.xml extension. Otherwise, not really sure what is going on. I haven't had any trouble importing Tasker projects in the past.
Beginner mode
MehStrongBadMeh said:
Is it downloading as a .prj or .prj.xml ? It should be the latter. If it isn't, rename it to have a .prj.xml extension. Otherwise, not really sure what is going on. I haven't had any trouble importing Tasker projects in the past.
Click to expand...
Click to collapse
Thanks for getting back to me. Im new with Tasker, the only reason I bought it was because of this issue and because I saw your post. All I needed to do was disable beginner mode in preferences, under Ui, and the house icon appeared, from there it was very simple to follow the instructions. Thank you for sharing your solution to this very inconvenient problem.
Once I get to test it ill make sure to give you feedback.
OneRealDaniel said:
Thanks for getting back to me. Im new with Tasker, the only reason I bought it was because of this issue and because I saw your post. All I needed to do was disable beginner mode in preferences, under Ui, and the house icon appeared, from there it was very simple to follow the instructions. Thank you for sharing your solution to this very inconvenient problem.
Once I get to test it ill make sure to give you feedback.
Click to expand...
Click to collapse
Thanks for letting me know about that, I'll add that to the steps.
Hi i downloaded the App but seems it doesnt work for me. I set it up according your instructions but still no change. But i háve an idea i spoted that when i make call from phone i háve an option to choose which audio divice to use if i select my phone it doest work but when someone picks up and then i select it it Works. So i am thinking is there a way to make this automatic? That once someone picks up a call that it select this option right after.
Added 2 screenshots one from the Standard run and one of the option to select an audio divice when making a call.
Thx for any help.
Edit: Works Now thx alot i had an incorrect name set for the device... i will test it if it works always but so far so good. thx alot
Jafabibe said:
But i háve an idea i spoted that when i make call from phone i háve an option to choose which audio divice to use if i select my phone it doest work but when someone picks up and then i select it it Works. So i am thinking is there a way to make this automatic?
Click to expand...
Click to collapse
I wanted to use this system as part of the automation workflow. The problem is that, when dialing someone, it switches the audio output when they pickup, instead of during Phone Offhook (the moment you hit dial). As a result, I can't detect the actual moment the audio device is switched, so I disable the watch audio entirely to prevent it from from happening.
Hello guys. I have non rooted stock nexus 5x. I have followed steps from first post but I always get error (attached).
Please any ideas what's going on?
Edit: Sorry guys. Please ignore it. I have added wifi mac for gear instead of bluetooth mac. I'm going to test it.
I am trying to use this for my phone.
I opened the prj.xml in notepad, edited my MAC address and name of bluetooth for car and gear s3.
When i press the play button in the bottom left corner i get the error non-existing plug-in code type Action: 704475526.
Any idea what i can do?
Thanks.
GabrielAK89 said:
I am trying to use this for my phone.
I opened the prj.xml in notepad, edited my MAC address and name of bluetooth for car and gear s3.
When i press the play button in the bottom left corner i get the error non-existing plug-in code type Action: 704475526.
Any idea what i can do?
Thanks.
Click to expand...
Click to collapse
Probably install Bluetask as per the instructions.
I solved the problem using Macrodroid.
GabrielAK89 said:
I solved the problem using Macrodroid.
Click to expand...
Click to collapse
Can you tell us, the other users, what you did to get it solved ?
As we are in a forum, others can benefit using your solution.
So please share.
I just got my Nokia 8 Sirocco, and I thought it was bad BT performance on my new device, when it probably is my Gear screwing me over. Thank you for this Tasker-project, I've just finished setting it up, and l am looking forward to seeing is effect!
Unfortunately, the macrodroid way don't work anymore for me.
Don't know why.
I am retrying the Tasker way. I get the error:
12.53.42/E FIRE PLUGIN: Connection / com.twofortyfouram.locale.intent.action.FIRE_SETTING: 8 bundle keys
12.53.42/E Connection: plugin comp: com.balda.bluetask/com.balda.bluetask.receivers.FireReceiver
12.53.42/E add wait type Plugin1 time 60
12.53.42/E add wait type Plugin1 done
12.53.42/E add wait task
12.53.42/E Error: 2
Does anyone know what it means?
LE: When i am in the car i don't get this error. Everything seems to be with green dot. But the magic never happen. The tusker is not triggered. Should i make other settings to work?
I also tryed Bluetooth auto connect. Bad luck with that also.
Hi!
I've been meddling with Tasker for the past few days and discovered that choosing the Headset profile to connect to and disconnect from the Gear S3 works better for me.
I've started out with MehStrongBadMeh's guide and tasker xml file (many thanks by the way!), but found out my phone was unable to connect the Gear S3. It disconnected OK to connect the car bluetooth, but would not reconnect Gear S3. Running the task also gave errors as reported by few others on this thread.
But everything seems to be in order when Headset profile is selected for Gear S3. Will test out extensively and will report back if I need to change anything else.
I believe I created that xml was created before bluetask handled specific profiles, hence the need to explicitly set headset now. I don't actually use this profile anymore, as calls started being routed properly when I updated my HTC 10 to Oreo (and continue to be routed properly on my OnePlus 6).
Just wanted to say a massive thank you for this. I have just bought the Galaxy Watch and have a Samsung S6 Edge with lineageos. I was having the issue where everything was being rooted through the watch. Your guide has got this working as it was designed.
My notes would be for anyone trying this - do not change the device name as it doesn't seem to work (i am guessing this is referenced in other profiles) - just change the mac address to your watches Bluetooth mac address.
Any update on this I still get an Error 2 and it never seems to connect on its own to my car audio
Solved with MacroDroid:
Trigger: Call active (any contact)
Action: Kill application Galaxy Wearable
Constraints: Trigger fired Call active
AND In call
App Alive BG Galaxy Wearable