Related
One thing I've noticed... is if I use the voice recorder app, and then go into a call, the voice recorder stops.
And so, it doesn't let you record audio using 2 apps at the same time.
My question is.... is this a feature built into the hardware, or built into the software?
Like, would it be possible to rewrite the operating system to allow 2 apps to use the record function simultaneously, or does the hardware prevent that?
Thanks.
Note: I posted this in the HTC Hero section of the site, but I'm asking, again, in general for Android... As in, IF a phone can't record with 2 apps at once, is that going to be due to hardware, or software limitations? Could the software be modified to allow it? OK. Thanks again.
For example, on Windows, I can record with Windows voice recorder, and with Audacity-- at the same time, and both produce a recording.
So I know there's no hardware limitation with my computer's hardware.
I'm wondering if this is the case with an HTC Hero.
Does anyone know the answer to this question?
I think it is software related both at kernel level (a preemptive kernel would be required) and in the dalvik vm itself.
Anyway, even if someone should be able to set the software, the way android manages multitasking would require at least a quad core phone for such a trick to work.
Folks,
I am experiencing low mic volume output after installing cm-10.1-20130411-EXPERIMENTAL-p5110-M3 on a Samsung Galaxy Tab p5113. The application we are testing is video and in this case the mic volume is really low. This is a tablet to tablet skype like video session. Here the other end perceived very low Audio coming from the Tab with the CM-10.1-20130411-EXPERIMENTAL-p5110-M3. Stock ROM mic levels were fine. I read through a bunch of the forum and saw some folks noting this issue with other older CM builds.
Is there any file/value that I can modify at the OS level to manipulate the Volume output of the Mic?
Any other ROM's that you might recommend that handle mic volume/Audio/Video better than the ROM mentioned above?
Thanks in advance.
-red
Aplha Widget
Just a follow up, This may help someone..
I was able to install the Alpha Widget app and it has a mic gain control function. Does anyone know what this gain control actually manipulates within the Android OS/Kernel? It would be great to manually manipulate this mic gain at OS / CLI level.
Thanks in advance.
-red
red_tx said:
Just a follow up, This may help someone..
I was able to install the Alpha Widget app and it has a mic gain control function. Does anyone know what this gain control actually manipulates within the Android OS/Kernel? It would be great to manually manipulate this mic gain at OS / CLI level.
Thanks in advance.
-red
Click to expand...
Click to collapse
You could take a look at this http://www.slatedroid.com/topic/38594-microphone-level-very-low/ (posts 16 & 17 onwards are quite interesting) and this
http://www.alsa-project.org/main/index.php/Main_Page
If you find any data would be interested to see what you get
sent from my still superb Google I/O 7510 (xda hd)
Hello,
I'm trying to get call recording working on my Z2.
I'm on a stock based 4.4.4 rom (from Dikej).
The problem is that I can only record calls via microphone, so only my voice will be recorded. Whenever I've tried choosing voice uplink + downlink recording, it fails. It just won't record.
I've tested plenty of apps, I even used Xposed module, which says sth. like "audio resorce is not available" after pressing the record button.
I've tried also different kernels, but without any luck.
My dad also owns a Z2, with completeley stock ROM, no root etc. and he just installs the same app that I have and it's working.
Is there any way to make it work?
Maybe someone has a good, tested kernel, that can record both sides.
mr.loverlover said:
Hello,
I'm trying to get call recording working on my Z2.
I'm on a stock based 4.4.4 rom (from Dikej).
The problem is that I can only record calls via microphone, so only my voice will be recorded. Whenever I've tried choosing voice uplink + downlink recording, it fails. It just won't record.
I've tested plenty of apps, I even used Xposed module, which says sth. like "audio resorce is not available" after pressing the record button.
I've tried also different kernels, but without any luck.
My dad also owns a Z2, with completeley stock ROM, no root etc. and he just installs the same app that I have and it's working.
Is there any way to make it work?
Maybe someone has a good, tested kernel, that can record both sides.
Click to expand...
Click to collapse
Try this - https://play.google.com/store/apps/details?id=com.record.my.call
Works for me in stock rom, change the settings according to your needs.
Sent from my D6502 using XDA Premium 4 mobile app
fayez69 said:
Try this - https://play.google.com/store/apps/details?id=com.record.my.call
Works for me in stock rom, change the settings according to your needs.
Sent from my D6502 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Yeah, that's exactly the app I have and it doesn't work correctly on my phone
Xperia Dialer Mods for me just fine, clear and working perfectly. But u need to install xposed first.
I'm using existenz 4.5.0 and it has call record enabled on the rom, no apps / xposed needed
Just go to settings / call / call recording (enable)
I think stock 4.4.4 has this too (not sure / don't remember), see if you have the option in the settings, if you have just enable it and you can record perfectly, straight from the stock in-call-ui
In many devices selecting one of the VOICE CALL audio sources (e.g. VOICE_CALL, VOICE_UPLINK, VOICE_DOWNLINK) will fail because it is not properly enabled / implemented by the manufacturer. You should choose (if applicable) DEFAULT (not MIC) audio source.
You can try Jit Call Recorder. if it does not work and you have root we can send you a configuration file to help you make it work.
Thanks but it could not recorded although has appeared button icons
pixeltech.dev said:
In many devices selecting one of the VOICE CALL audio sources (e.g. VOICE_CALL, VOICE_UPLINK, VOICE_DOWNLINK) will fail because it is not properly enabled / implemented by the manufacturer. You should choose (if applicable) DEFAULT (not MIC) audio source.
You can try Jit Call Recorder. if it does not work and you have root we can send you a configuration file to help you make it work.
Click to expand...
Click to collapse
My phone is Sony Xperia C5 Ultra dual,
Please help me to make us Good CALL RECORDING for 2-way of Jit..
Thank you so much
Hi All. The sound is fixed as you know but not on all ROM. So i've made a Fix zip. Tried on US and G version.
Edit: working on A2017 (Chinese version)
IMPORTANT: I'm not responsible for anything which could be happen. I suggest to make a backup from TWRP.
First of all i didn't fix it. Thanks @Unjustified Dev , @DrakenFX and Anynomous Dev
Instruction:
Flash zip via TWRP.
Download:
v4.1
https://www.androidfilehost.com/?fid=457095661767153882
v4
https://www.androidfilehost.com/?fid=457095661767152958
v2
https://www.androidfilehost.com/?fid=529152257862718359
WesTD said:
Hi All. The sound is fixed as you know but not on all ROM. So i've made a Fix zip. Tried on US and G versions.
IMPORTANT: I'm not responsible for anything which could be happen. I suggest to make a backup from TWRP.
First of all i didn't fix it. Thanks @Unjustified Dev , @DrakenFX and Anynomous Dev
Instruction:
Flash zip via TWRP.
Download:
uploading.
Click to expand...
Click to collapse
Thanks for that.
Do correct me if I'm wrong, but this still does not make use of the AKM DAC, right? This still uses the Qualcomm inbuilt DAC?
Thanks in any case!
joaste said:
Thanks for that.
Do correct me if I'm wrong, but this still does not make use of the AKM DAC, right? This still uses the Qualcomm inbuilt DAC?
Thanks in any case!
Click to expand...
Click to collapse
It's wired for it's AKM DAC the issue was we were dependent on ZTE crappy patch that made us bypass and force audio on. Now the amplifier HAL correctly calls to the NXP driver to properly calibrate and initialize audio in all usecases. It's more so the developer is trying to recreate how stock handles stuff like voice speaker, speaker reversing, mono + stereo, etc.
Unjustified Dev said:
It's wired for it's AKM DAC the issue was we were dependent on ZTE crappy patch that made us bypass and force audio on. Now the amplifier HAL correctly calls to the NXP driver to properly calibrate and initialize audio in all usecases. It's more so the developer is trying to recreate how stock handles stuff like voice speaker, speaker reversing, mono + stereo, etc.
Click to expand...
Click to collapse
How was this fix done exactly? Was it just fiddling with some configuration files or did you have to completely rewrite the way android works the audio so it calls the driver correctly? And if so, is it the same way Dolby does? I'm so curious how you guys and the anonymous dev managed to fix it
Also, I can't wait for this to upload. This + LOS based roms and this phone would be absolutely perfect. Too bad it's not mainstream enough to get more attention
If we flash this, will it cause any issues once it's officially merged into LOS and we update LOS on the phone?
WesTD said:
Hi All. The sound is fixed as you know but not on all ROM. So i've made a Fix zip. Tried on US and G versions.
IMPORTANT: I'm not responsible for anything which could be happen. I suggest to make a backup from TWRP.
First of all i didn't fix it. Thanks @Unjustified Dev , @DrakenFX and Anynomous Dev
Instruction:
Flash zip via TWRP.
Download:
uploading.
Click to expand...
Click to collapse
The download is not available.
Teet1 said:
How was this fix done exactly? Was it just fiddling with some configuration files or did you have to completely rewrite the way android works the audio so it calls the driver correctly? And if so, is it the same way Dolby does? I'm so curious how you guys and the anonymous dev managed to fix it
Also, I can't wait for this to upload. This + LOS based roms and this phone would be absolutely perfect. Too bad it's not mainstream enough to get more attention
Click to expand...
Click to collapse
Has nothing to do with dolby. There's a file libtfa9890.so stock audio hal calls this file does it's magic. On lineage we don't have the amp source which is packed into the audio hal on stock. We use an amplifier hal all this hal does it try to produce whatever the heck the stock audio hal did when it loaded libtfa9890.so. It basically allows you to instrument custom calls without touching the audio hal of the ROM therefore keeping it clean. ZTE gave us a patch that force loaded libtfa9890 and immediately said ignore all cases turn on the speaker. What the dev did is rewrite the patch to properly call all functions such as calibrate, set mode , speaker on , speaker off ,etc. This way we don't just force speaker we actually start saying if in call handle the speakers this way. If music is playing handle them this way. We don't just say if need sound ramp up the amp and make sound.
link added.
Has anyone who flashed it have a decrease in system performance?
Sent from my ZTE A2017U using Tapatalk
WesTD said:
link added.
Click to expand...
Click to collapse
Just installed this fix.
It works, it works, Hallelujah!.
Ya so this zip works on the Chinese version, so you can update the op
Also passed the stereo test. Left and right channels are both working independently and awesomely.
The distortion has nearly disappeared.
Calls work.
Thanks to all the devs especially unjustified dev and anonymous dev.
Thanks also to drakenfx and westd.
Also now that patch 3 is out, can we expect another zip in the future!
Unjustified Dev said:
Has nothing to do with dolby. There's a file libtfa9890.so stock audio hal calls this file does it's magic. On lineage we don't have the amp source which is packed into the audio hal on stock. We use an amplifier hal all this hal does it try to produce whatever the heck the stock audio hal did when it loaded libtfa9890.so. It basically allows you to instrument custom calls without touching the audio hal of the ROM therefore keeping it clean. ZTE gave us a patch that force loaded libtfa9890 and immediately said ignore all cases turn on the speaker. What the dev did is rewrite the patch to properly call all functions such as calibrate, set mode , speaker on , speaker off ,etc. This way we don't just force speaker we actually start saying if in call handle the speakers this way. If music is playing handle them this way. We don't just say if need sound ramp up the amp and make sound.
Click to expand...
Click to collapse
Genius. Didn't mean to say Dolby, meant zte I had Dolby Atmos on the mind. But if it's nothing to do with Dolby, how come they didn't release the source for a direct fix instead of releasing a half assed patch for devs to work with? Then there wasn't be an issue of it being closed or open source
WesTD said:
link added.
Click to expand...
Click to collapse
My latest Gerrit patch?
Sent from my ZTE A2017U using Tapatalk
FIGURES!!! I just went back to stock (but still have unlocked bootloader)....
Looks like I know what I'll be doing, at some point, this week!
GREAT WORK @DrakenFX
Unjustified Dev said:
My latest Gerrit patch?
Sent from my ZTE A2017U using Tapatalk
Click to expand...
Click to collapse
not latest, 2nd one. @DrakenFX will upload it soon.
WesTD said:
not latest, 2nd one. @DrakenFX will upload it soon.
Click to expand...
Click to collapse
Yeah, I sent him the libraries a few hours ago. Let me know if you need anything else.
Sent from my ZTE A2017U using Tapatalk
Unjustified Dev said:
Yeah, I sent him the libraries a few hours ago. Let me know if you need anything else.
Sent from my ZTE A2017U using Tapatalk
Click to expand...
Click to collapse
Okay man. thanks for your works.
TWRP Flashable Stereo Sound Patch 3.
https://www.androidfilehost.com/?fid=457095661767152906
Thanks to Anonymous Dev. & @Unjustified Dev for all of this.
DrakenFX said:
TWRP Flashable Stereo Sound Patch 3.
https://www.androidfilehost.com/?fid=457095661767152906
Thanks to Anonymous Dev. & @Unjustified Dev for all of this.
Click to expand...
Click to collapse
Can users that already have the audio fix install this (NucleaROM)??
aLexzkter said:
Can users that already have the audio fix install this (NucleaROM)??
Click to expand...
Click to collapse
Yep this would work on any rom that uses amplifier hal which is all of them
Sent from my ZTE A2017U using Tapatalk
What's the improvement of V3 over V2 ?
PS : THX to every1 involved who made this possible !
Install "Ainur JamesDSP v1.7" Magisk module and choose the HQ 64bit driver
Install "Audio Modification Library v.1.8.1" Magisk module
Reboot
Configure JamesDSP app
Confirmed working (speakers & headphones (can't test bluetooth)) on my FIG-LX1 (L31) - EMUI 8.0.0.148(C432) - Magisk v17.1
Edit: If you don't want ringtones/notification-sounds to be processed, switch DSP registration from global to conventional. (3dot menu - top right, screenshot added)
Huge thanks to natanrosenfeld (he made a YT video, explaining a fix for previous version (now fixed with v1.7)) - and especially the JamesDSP dev team!
Great news I seen it on .android-hilfe.de myself
Messing around and cant seem to get it right, either too loud or doesnt work
Viper4android was much easier to setup, using Huawei DTS.irs or srs_2_1.irs then not much else and worked great
redultra82 said:
Great news I seen it on .android-hilfe.de myself
Messing around and cant seem to get it right, either too loud or doesnt work
Viper4android was much easier to setup, using Huawei DTS.irs or srs_2_1.irs then not much else and worked great
Click to expand...
Click to collapse
Have you tried using the same impulse response files with JamesDSP?
Copy the .irs (or .wav, .flac) to /storage/emulated/0/JamesDSP/Convolver and enable Convolver in JamesDSP.
Works great here.
Greetings from "androphil"
callmeWhiskers said:
Have you tried using the same impulse response files with JamesDSP?
Copy the .irs (or .wav, .flac) to /storage/emulated/0/JamesDSP/Convolver and enable Convolver in JamesDSP.
Works great here.
Greetings from "androphil"
Click to expand...
Click to collapse
I did thanks
Can you send screenshot of what you have, not sure on other settings
redultra82 said:
(...)Can you send screenshot of what you have, not sure on other settings
Click to expand...
Click to collapse
Even if we'd share the exact same setup (e.g. settings/IR xy sound great with my Shure SE425 in-ear headphones, but not so great with my AKG Q701) and preference of music, it would still be incredibly subjective and mainly based on taste. Certified sound-engineers would probably disagree, I guess
My suggestion is: leave every (other) option off, download a pack of different IRs (e.g. https://forum.xda-developers.com/zenfone2/general/collection-convolver-samples-389-t3140299) and try each one out. If you found one you like, (slightly) tune it with the EQ. At least that's my "non-pro" approach.
Mostly all I want is to make the phone louder, well the phone speaker, on Bluetooth speakers etc it's fairly OK
Next issue is echo sound on ringtone and notification
I'll try IRS out and maybe someday have Viper4android
It's a system-wide audio-mod, so yes, if you have e.g. Virtual Room Effect turned on or use a noticably "reverberating" impulse response file, you'll experience echo on ringtones/notification-sounds too.
I've managed to make the speakers slightly louder by choosing the highest IR Volume Level (30dB), but I think the device's speaker volume level/overall sound-quality is just physically limited. They are not the "best" speakers after all.
callmeWhiskers said:
It's a system-wide audio-mod, so yes, if you have e.g. Virtual Room Effect turned on or use a noticably "reverberating" impulse response file, you'll experience echo on ringtones/notification-sounds too.
I've managed to make the speakers slightly louder by choosing the highest IR Volume Level (30dB), but I think the device's speaker volume level/overall sound-quality is just physically limited. They are not the "best" speakers after all.
Click to expand...
Click to collapse
I noticed the room effect and turned it off, but just using Irs or some of them and seemed to be an echo,
Speaker is good enough, it is only a phone after all, there are small bluetooth speakers now that have great volume to help
A nice guy from the Telegram channel pointed out, that you can avoid processing system sounds (ringtones/notification) by switching DSP registration mode from global to conventional (screenshot added to OP).
YEEEES!!!! This mod is also working on Huawei P20Pro with EMUI8.1.. I just follow the same steps above. Thanks a lot man!
callmeWhiskers said:
Install "Ainur JamesDSP v1.7" Magisk module and choose the HQ 64bit driver
Install "Audio Modification Library v.1.8.1" Magisk module
Reboot
Configure JamesDSP app
Confirmed working (speakers & headphones (can't test bluetooth)) on my FIG-LX1 (L31) - EMUI 8.0.0.148(C432) - Magisk v17.1
Edit: If you don't want ringtones/notification-sounds to be processed, switch DSP registration from global to conventional. (3dot menu - top right, screenshot added)
Huge thanks to natanrosenfeld (he made a YT video, explaining a fix for previous version (now fixed with v1.7)) - and especially the JamesDSP dev team!
Click to expand...
Click to collapse
Hi do you know if I can change mixer path values without root and using adb on pc? , I'm trying to raise volume of WhatsApp calls, calls and maybe a bit of loud speaker volume but I'm trying to avoid root etc. Thanks any advice would be appreciated or a link to tutorials. I'm on psmart. Thanks again
jason13v8 said:
Hi do you know if I can change mixer path values without root and using adb on pc? , I'm trying to raise volume of WhatsApp calls, calls and maybe a bit of loud speaker volume but I'm trying to avoid root etc. Thanks any advice would be appreciated or a link to tutorials. I'm on psmart. Thanks again
Click to expand...
Click to collapse
Sorry - I'm not an expert, so don't take my word for it - but I don't think that's possible, since all these files are stored in locations, where (non root) users don't have write permissions. Even with a rooted and/or custom recovery device, I don't think it's possible to alter app-specific volumes by just changing mixer_paths.xml values.
callmeWhiskers said:
Sorry - I'm not an expert, so don't take my word for it - but I don't think that's possible, since all these files are stored in locations, where (non root) users don't have write permissions. Even with a rooted and/or custom recovery device, I don't think it's possible to alter app-specific volumes by just changing mixer_paths.xml values.
Click to expand...
Click to collapse
Sorry I know I mentioned whats app but really I just mean overall volume. With my moto g5 I was able to edit mixer path values which led to louder everything. But that was only with root as I'm new to adb. Thanks for your response
jason13v8 said:
Sorry I know I mentioned whats app but really I just mean overall volume. With my moto g5 I was able to edit mixer path values which led to louder everything. But that was only with root as I'm new to adb. Thanks for your response
Click to expand...
Click to collapse
In case your bootloader is unlocked, iirc you could theoretically fastboot flash TWRP - and use TWRP's "privileged" terminal (e.g. (mount /system), adb pull/push and edit the file(s)), and then (re)flash stock recovery again - without actually rooting the device.
Again, I'm not an expert (also didn't try it myself) and can't guarantee above mentioned procedure works, despite my inner-Sherlock-Holmes tells me, your bootloader is actually not unlocked.
callmeWhiskers said:
In case your bootloader is unlocked, iirc you could theoretically fastboot flash TWRP - and use TWRP's "privileged" terminal (e.g. (mount /system), adb pull/push and edit the file(s)), and then (re)flash stock recovery again - without actually rooting the device.
Again, I'm not an expert (also didn't try it myself) and can't guarantee above mentioned procedure works, despite my inner-Sherlock-Holmes tells me, your bootloader is actually not unlocked.
Click to expand...
Click to collapse
Yeah still locked dude, tried DC unlocker but they refunded as I'm on latest security patch and admitted there is nothing they can do right now.
Themes