Since I installed Android 10 on my phone I have been experiencing problems related to audio, when I use the speakers for anything it is just to low to listen to, sometimes when someone call me I often can't hear the ringtone. However the microphone is OK, its quality for recording human voice (specially) is amazing and everyone listens to me loud and clear.
Possible solutions?
Well, I did some research and find out that Android Q doesn't have a to3g file, some websites may tell you go to
Code:
/device/etc/sound/to3g
and open it using any text editor, but you won't find it in our Galaxy-A20. I tried to find it in /vendor partition and /system partition but no success.
There were two more interesting files in /vendor partition, mixer_paths.xml and mixer_gains.xml, I tried changing their values and comparing them with the original ones that comes with vendor.img.lz4 from stock ROM, also there was no difference between them.
The question is, does anyone know how to solve this problem? If so, please help us and I'll mention the comment here. Thanks.
This problem also happens in Pie versions of Android, as you can see here in the bugs' section
https://www.android-hilfe.de/forum/...iziell-pie-lineageos-16-0-andyvan.928318.html
Alright, part of the problem can be solved by installing Agrim's custom kernel. This can be found here
the same problem here. There's no solution?
Related
Well I have had my sgs for a couple of weeks now on the whole very happy with android can't help thinking how great my last phone (i8910) would have been with froyo though, oh well. ,Anyway so I have managed to root and lag fix a stock 2.2.1 Rom and add the voodoo sound driver thing as well as the clockworkRom bootloader. So think I'm doing ok, albeit with a couple of big mistakes. Thank god for titanium backup pro and latterly CM.
Any way i have tried to install dsp manager a couple of times via different methods and each time suffered the hardest to recover from failures both times took several hours to find the
right recovery combinations. So does anyone know why this is?
My ultimate goal is to increase volume on music playback on my Bluetooth headset so if you have a better way this would also be welcome?
Secondly I can't find a single call recording app that will record both sides when using Bluetooth headsets anyone know of anything?
Thirdly i see geotagging remains an issue on the sgs I'd like to share increase that 5x zoom pro works okay a camera app that can disable geotagging but it misses some of the better features of the native app like anti shake and smile detect etc does anyone know of a better option?
Finally the custom Rom's thing is confusing me a great deal is there a decent beginners guide that has information regarding most of the main ones and their main benefits?
Finally the custom Rom's thing is confusing me a great deal is there a decent beginners guide that has information regarding most of the main ones and their main benefits?
You need to read each post really .
Rom Kitchen
https://spreadsheets.google.com/pub...MWI2LWlSR3IwM0dnYmdLX2kzMEE&hl=en&output=html
jje
JJEgan said:
You need to read each post really .
Rom Kitchen
jje
Click to expand...
Click to collapse
Damn there's even more than I thought and that list is missing a load I have seen as well.
Thanks for the list
I thought I'd start my own post, since some incorrect information has been going around. The libaudio.so file that has been linked to is only to fix the wonk on the Nexus One and has nothing to do with the Gingerbread call delay. It is hardware specific, and may cause issues in other phones. If you don't have a Nexus One, you probably shouldn't install this file. It is already in the CM nightlies, and will be in 7.0.4 when it is released.
I have submitted a patch to gerrit that reduces the call delay in my testing. I've posted a test build in the Nexus One nightlies thread, and fitsnugly has cherry-picked it for his Nexus One and G2x builds. Several others have said that it is working for them.
The patch is here:
http://review.cyanogenmod.com/#change,5420
Thanks for your patch! This is great work.
My change has been merged into Cyanogenmod.
thanks for your brilliant findings!
Thanks jyxent for working on this! This has been the most annoying bug (to me) that I've had to deal with.
I am correct, in my understanding of the comments at review.cyanogenmod.com, that what you did essentially restored the code to how it was in Froyo? Just curious.
Not exactly. Google changed PhoneUtils to use CallManager to set the audio mode, instead of setting it to MODE_IN_CALL directly. There is some delay before a call becomes active once it is answered. CallManager checks this state when setting the audio mode, and was not setting MODE_IN_CALL, since it thought the call was still ringing. I just added a check to make sure that MODE_IN_CALL is set if a call was just answered and the call is still considered ringing.
This makes the behavior similar to froyo, but it wasn't just restoring the original code.
I think it works when answering from the handset but not when you answer using the earphone..is this possible????
got a problem today using this patch
phone was ringing: went to answer and slided...
in the meantime an SMS arrived (when I was sliding to answer)
result: the phone call hanged & audio output was set to loudspeaker + phone app freezed (black screen)
the other party could not hear me
hmm sorry for posting a dumbass question but
I need to download the callmanager.java right?
How should I install it, can I just replace the existing file using e.g. Super Manager (maybe making a copy beforehand)?
And if so, where is this file stored? I did a search on my phone but no results
thx
B
berre said:
hmm sorry for posting a dumbass question but
I need to download the callmanager.java right?
How should I install it, can I just replace the existing file using e.g. Super Manager (maybe making a copy beforehand)?
And if so, where is this file stored? I did a search on my phone but no results
thx
B
Click to expand...
Click to collapse
It isn't possible to just replace a file to get this fix. The ROM has to be compiled with the added patch.
This patch is included in the CyanogenMod nightly builds, as well as the 7.1 release candidate. As for other ROMs, it might be best to just ask in their respective threads.
Hi
[EDIT] my phone = I9300, OmniRom = latest (with a maximum of google apps disabled/alternatives preferred)
I can't quite figure that one out:
On every single system update, I lose my settings in terms of my custom ringtones, alarms...
I tried 3 different ways:
- I copied them into System/media/audio/ringtones & alarms --> after every update, my custom sound files cannot be found anymore and are therefore not available to select from Settings > Sound > Phone ringtone & Default alarm sound
- so then I copied them into sdcard/media/audio/ringtones & alarms --> althought they remain there after every update, they are not available from Settings > Sound > Phone ringtone & Default alarm sound
- so finally I copied them into extSdCard/media/audio/ringtones & alarms with the same effect: althought they are still there after every update, they are not available from Settings > Sound > Phone ringtone & Default alarm sound
Somehow this looks like a bug to me...
Can someone please explain how I can preserve my custom ringtones after system updates?
Thank you VERY much
beng
How did you copy them? It might be a selinux/permissions problem.
For reference, I haven't had any problem on my Nexus 5 (all internal ext4 with emulated sdcard) with
Code:
[email protected]:/ # ls -lZ /sdcard/Alarms/
-rw-rw---- root sdcard_r u:object_r:sdcard_internal:s0 Luminescence.ogg
Code:
/sdcard/Alarms, /sdcard/Ringtones, /sdcard/Notifications
Those are directories especially for custom sounds, which of course will survive ROM updates. Why don't you put them there?
klenamenis said:
Code:
/sdcard/Alarms, /sdcard/Ringtones, /sdcard/Notifications
Those are directories especially for custom sounds, which of course will survive ROM updates. Why don't you put them there?
Click to expand...
Click to collapse
done just that: my custom sounds don't even show up (Settings > Sound > Phone ringtone & Default alarm sound), nor after a reboot!
honestly this is a major bug as far as I am concerned - I keep missing my phone calls as the ringtone will default to none, makes the whole point about having a mobile pointless!!!
Until you can give steps to repeat, that someone else can repeat, it appears to be a problem that is specific to your phone and configuration. If it were a significant bug, you wouldn't be the only one claiming it was impacting them.
Nothing personal, but unless you can replicate this on a fresh install, without additional software, and document how to repeat it, it likely will never be considered an OmniROM bug. One you can do that, a JIRA is perhaps the right way to raise attention on the issue.
As a note, opening additional threads will more likely get you labeled as whiner than get faster resolution. One is plenty.
---
Posted from whatever phone booted today
jeffsf said:
Until you can give steps to repeat, that someone else can repeat, it appears to be a problem that is specific to your phone and configuration. If it were a significant bug, you wouldn't be the only one claiming it was impacting them.
Nothing personal, but unless you can replicate this on a fresh install, without additional software, and document how to repeat it, it likely will never be considered an OmniROM bug. One you can do that, a JIRA is perhaps the right way to raise attention on the issue.
Click to expand...
Click to collapse
Hi jeffsf
well I thought the steps were clearly detailed in my initial post?
The custom sounds I would like to set up as custom ringtones / alarms are snippets edited out of full mp3 songs (generally a loop edited out of the intro); If i use the default (boring) sounds provided, I keep my settings.
I first copied my custom snippets into System/media/audio/ringtones & alarms ; this works until I reboot following a new nightly update, my settings are lost; the ringtone is back either to the default one or to none (worse option as I miss my phone calls - I cannot work out a rule as to the default ringtone/none reset, sorry!); my custom sound files cannot be found anymore in the ringtones folder and are therefore not available to select from Settings > Sound > Phone ringtone & Default alarm sound
My second attempt was then to copy them into sdcard/media/audio/ringtones & alarms ; although they remain there after the reboot following any new nightly update, the settings are lost from Settings > Sound > Phone ringtone & Default alarm sound.
So my third attempt was to copy the snippets into extSdCard/media/audio/ringtones & alarms but it had the same result: although they are still there after every update, my previous settings are lost and the snippets cannot be selected from Settings > Sound > Phone ringtone & Default alarm sound ...
After all these tests, I am even more confused; I do not know/understand for sure what folders Android uses primarily / secondarily for ringtones / alarms...
jeffsf said:
As a note, opening additional threads will more likely get you labeled as whiner than get faster resolution. One is plenty.
Click to expand...
Click to collapse
I do get the point! Not my intention to whinge but as explained, there is not much point in having a silent phone!
First I asked a question (support); clearly no working solution can be provided
so I take it to the next level: software correction requirement (indeed JIRA can be the software to use for this - this is actually what I am using at work!)
Or the solution is to choose another rom, shame really...
BenG7 said:
Hi jeffsf
well I thought the steps were clearly detailed in my initial post?
Click to expand...
Click to collapse
Your observed behavior is clear in your first post, so there is no reason to repeat it. It adds no information by doing so.
The custom sounds I would like to set up as custom ringtones / alarms are snippets edited out of full mp3 songs
Click to expand...
Click to collapse
A tiny snippet of new information. But still, you haven't identified what format you are using on the device or how you are copying the files into the directories you are using, only on your source.
clearly no working solution can be provided [...] Or the solution is to choose another rom, shame really...
Click to expand...
Click to collapse
Or clearly it isn't a problem with the ROM. If it were a general problem with the ability to set and retain ring tones, there would most likely have been at least one other person who reported similar problems as you.
Unless you can replicate this (a) from a clean install, (b) without other software installed, (c) using a directory intended for the function, (d) clearly identifying how and where you have set the ring tone, and (e) how you updated, it most likely isn't a ROM bug.
GIven that this isn't impacting anyone but you from what I can tell, I would look at your own software, configuration, or use as the most likely cause.
Note also that two people in this thread have already clearly identified directories for these files that do not have the issues you mention.
unsupported audio format?
Hello,
I built omnirom from last sources and I I was in the same situation. My mp3 wasn't recognized anymore (regression? developper choix? I don't know)
Workaround: I converted them into ogg format, and it works like a charm (on my HTC Explorer).
Hi
Hey, for the first time I realise yesterdays nightly (20141030) solved this ongoing issue I had given up on:
it preserved my custom ringtone and alarm and I did not need to reset my ringtone & alarm after the update as I do after EVERY SINGLE update - a pain really!
Please keep it as such - thanks A LOT
cheers
beng
BenG7 said:
Hi
Hey, for the first time I realise yesterdays nightly (20141030) solved this ongoing issue I had given up on:
it preserved my custom ringtone and alarm and I did not need to reset my ringtone & alarm after the update as I do after EVERY SINGLE update - a pain really!
Please keep it as such - thanks A LOT
cheers
beng
Click to expand...
Click to collapse
Nothing has been changed that would affect this.
Also, you probably stopped getting responses because your responses were inconsistent. Post 3 provided the standard location where these files should be placed.
In post 4 you claimed exactly that, EXCEPT that in Post 6, none of the directories in post 2 were in your list of things you tried...
In the end it really doesn't matter. Your device is getting dropped with L as it hasn't had a maintainer in months and there is no one to fix I9300 issues.
Entropy512 said:
Nothing has been changed that would affect this.
Also, you probably stopped getting responses because your responses were inconsistent. Post 3 provided the standard location where these files should be placed.
In post 4 you claimed exactly that, EXCEPT that in Post 6, none of the directories in post 2 were in your list of things you tried...
In the end it really doesn't matter. Your device is getting dropped with L as it hasn't had a maintainer in months and there is no one to fix I9300 issues.
Click to expand...
Click to collapse
I can only report it works now.
Post 1 were the initial steps I took
I did as advised in post 3 ; this was post 4
Post 6 was only a repeat of post 1, not including steps from post 4, but these were carried out too, to no avail too.
Just forget it now.
Thanks
This is a file from a viperaudio sound mod, and I'm having issues with calls (people on the other line hear an echo).
I already asked in the thread, and contacted the dev, but I didn't get any answer.
There's a way to solve this issue by deleting the file, but it harms the audio quality.
That's why I'm wondering if there is any way to edit this file?
Check second post
Actually, I've made some new discoveries about this issue.
The libaudcal.so file is present on our devices in vendor/lib.
If this file is deleted, then it has the same effect as copying it from another device (installing the one from the old viper sound mod).
That means - incredible huge bass on speakers, but issue in calls, the other person on the call hears an echo, and the in call volume is stuck at a constant low value.
Now, what's interesting is that this issue is NOT present when making calls via viber, facebook messenger etc. apps.
I've tried downloading different dialers, and using different rom versions, but no difference.
It seems to me that there are filters included in this file to purposely cutoff low frequencies, and that calls are broken when the original file isn't used.
I hate to give up, so please if anyone has ideas on how this could be resolved, I'd appreciate it.
Arcide said:
Actually, I've made some new discoveries about this issue.
The libaudcal.so file is present on our devices in vendor/lib.
If this file is deleted, then it has the same effect as copying it from another device (installing the one from the old viper sound mod).
That means - incredible huge bass on speakers, but issue in calls, the other person on the call hears an echo, and the in call volume is stuck at a constant low value.
Now, what's interesting is that this issue is NOT present when making calls via viber, facebook messenger etc. apps.
I've tried downloading different dialers, and using different rom versions, but no difference.
It seems to me that there are filters included in this file to purposely cutoff low frequencies, and that calls are broken when the original file isn't used.
Click to expand...
Click to collapse
Bro the same problem now i have and i am trying to resolve this but i dont find how to modify this so file, did you know now how to increase in call volume and microphone record in video to
Wenzel6 said:
Bro the same problem now i have and i am trying to resolve this but i dont find how to modify this so file, did you know now how to increase in call volume and microphone record in video to
Click to expand...
Click to collapse
No brother, this is really old and I've never found a solution. I don't think there's a way to edit that library
Arcide said:
No brother, this is really old and I've never found a solution. I don't think there's a way to edit that library
Click to expand...
Click to collapse
Only the guy that made this knows
Arcide said:
No brother, this is really old and I've never found a solution. I don't think there's a way to edit that library
Click to expand...
Click to collapse
Maybe you know how to increase output sound to audiotrack in android 7.1.2 without that file ?
Dear folks,
I used to search this and other forums for an easy solution to increase the volume level of my Galaxy S5 (G900F) in both directions, to mic something and for listening. I do not care of speakers (to destroy them) or my ears (they are already in bad status since the DISCO-Beats in early 90ties), smile, but I hate to anoy my friends with to low volume messages (even when I am at home with no background sounds). In the car it is even worse. My phone is rooted. Android 8.1.0 Extend Version AospExtended-5.4-unofficial, 2018-April-05, G900FXXU1CPC9, with Kernel 3.4.113-lineageos-g808bf80, Build-Number OPM2.171019.029, Moderate
I have downloaded and testet micgain26higher.zip, micgain26normal.zip, Mic_Gain_Mod_v11.9.zip, and s5_Volume_Boost_Version_vX...zip
None of it works.
I even extracted / copied the three files from container to /etc, with no positive result.
I tried to increase the numbers within mixer_paths.xml by hand, no improvements.
Please give me a solution (preferable a ready made mixer_paths.xml to copy/paste).
Thanks.
I think there is no solution - mine is loud for me, but my mic level is poor. I expect nobody is good enough to help you here.
Copy the mixer_paths.xml that i have attached to "/vendor/etc" and change permissions to "rw- r- r-". (ps : i think it is not necessary to change permissions anymore but just in case you can try)
For me it works on recording audio
The guy in this thread.....
http://forum.xda-developers.com/showthread.php?t=3202087
Knows a *lot* about adjusting the xml file to make adjustments to various volume level parameters. He was able to give me a lot of help when I needed it. Why not ask in that thread.
Sent from my SM-G900F