hello new here i followed all the directions to a tee got everything install very easy as im not new to flashing roms. i have a rhod400 (sprint tp2) and i have the issue of no sound from the rear speaker when receiving phone calls or anything really. it all comes from the front earpiece speaker. is there a update to flash to fix this? or any easy way to get it working. ive tried numerous times thinking about a bad flash with no luck and yes i have task29'ed it after each to make sure. however the gbx0 3.3.x kernal works perfectly with sound but i like the normal omgb rom better personally for some reason the gbx0 nand rom on my phone seems much slower to respond and much slower going through menus etc for some reason and ive flashed it a few times to make sure
also im running the newest verizon .37 radio as well.
sorry for asking here and not in the thread i needed more posts and really hope someone can help with that. ill be posting more so hopefully will be able to ask there soon but i really wanted to get this fixed asap since i use this phone daily.
Never heard of that before, but I had to move the thread. Sorry.
Good luck & post logs. I doubt it's an issue with the ROM tho, as I run that same ROM myself. Same phone, same radio (assuming you're on the 2.37VZ radio), etc.
You're using the latest OMGB and the latest CWM recovery - not AOSP?
I know that OMGB is using the older kernel, and I want to say that the 3.x kernels got a serious audio code re-write. That could account for the difference. Unfortunately as it seems there is no more development happening in the OMGB rom there will not be support of the newer kernels. Perhaps you should consider using the GBX nand version rather than the OMGB.
wizardknight said:
I know that OMGB is using the older kernel, and I want to say that the 3.x kernels got a serious audio code re-write. That could account for the difference. Unfortunately as it seems there is no more development happening in the OMGB rom there will not be support of the newer kernels. Perhaps you should consider using the GBX nand version rather than the OMGB.
Click to expand...
Click to collapse
I guess I assumed the OP was using the kernel from OMGB.
Is that the case OP? Please stick to the kernel provided with OMGB and report back.
arrrghhh said:
I guess I assumed the OP was using the kernel from OMGB.
Is that the case OP? Please stick to the kernel provided with OMGB and report back.
Click to expand...
Click to collapse
The way I read his post was that he tried GBX w/3.x kernel and OMGB, but only saw the sound issue in OMGB. However he wanted to use OMGB as it seemed to have a better performance. It sounds like his issue might be related to using the older kernel in OMGB. Not necessarily so much that he was swapping bits and parts around.
wizardknight said:
The way I read his post was that he tried GBX w/3.x kernel and OMGB, but only saw the sound issue in OMGB. However he wanted to use OMGB as it seemed to have a better performance. It sounds like his issue might be related to using the older kernel in OMGB. Not necessarily so much that he was swapping bits and parts around.
Click to expand...
Click to collapse
I've just never heard of any sound issues with OMGB. I did a quick search, can't find anyone with sound issues on OMGB at all, whatsoever...
OP has been PMing me and said the same issue is present on another RHOD400. I have to think he's doing something wrong, but I have no clue what he could do wrong that would cause everything BUT sound to work...
arrrghhh said:
I've just never heard of any sound issues with OMGB. I did a quick search, can't find anyone with sound issues on OMGB at all, whatsoever...
OP has been PMing me and said the same issue is present on another RHOD400. I have to think he's doing something wrong, but I have no clue what he could do wrong that would cause everything BUT sound to work...
Click to expand...
Click to collapse
That is an odd issue. I have to agree with all your points.
wizardknight said:
That is an odd issue. I have to agree with all your points.
Click to expand...
Click to collapse
ive heard of this with really old sdcard builds... i seem to recall if you set the volume to one step below max the audio kinda worked the way its supposed to. let us know if your still having issues.
Me Too
I can confirm I'm having this issue as well on OMGB on my RHOD400. Can't hear notification tones or incoming ringer. Volume level "beeps" when you hit the buttons are also very quiet (at all levels) and come from earpiece instead of speaker.
Logcat with unanswered call and poor volume attached. Also, attaching logcat with info from startup.
I too am still using this as my daily phone...I'm missing calls and pissing people off (not that I care) due to this. It used to fix after a reboot, but now it's just stuck like this.
I'm seeing permissions issues trying to access the audio*.csv files from the SD Card, it looks like it finds a default instead. I'm not sure if this is normal.
NeoMatrixJR said:
I can confirm I'm having this issue as well on OMGB on my RHOD400. Can't hear notification tones or incoming ringer. Volume level "beeps" when you hit the buttons are also very quiet (at all levels) and come from earpiece instead of speaker.
Logcat with unanswered call and poor volume attached. Also, attaching logcat with info from startup.
I too am still using this as my daily phone...I'm missing calls and pissing people off (not that I care) due to this. It used to fix after a reboot, but now it's just stuck like this.
I'm seeing permissions issues trying to access the audio*.csv files from the SD Card, it looks like it finds a default instead. I'm not sure if this is normal.
Click to expand...
Click to collapse
Do you have this issue with the GBX Nand build?
wizardknight said:
Do you have this issue with the GBX Nand build?
Click to expand...
Click to collapse
Just got it installed. Ringer works fine on GBX0* + 3.3.6
NeoMatrixJR said:
Just got it installed. Ringer works fine on GBX0* + 3.3.6
Click to expand...
Click to collapse
Makes me think there's some acoustic patch that's missing in the OMGB .27 kernel...
That's a bummer. Strange only some experience the bug...
Related
Hey everyone. im from the Hero CDMA forum. i have made audio fix patches for the hero that fixed the audio loss for 2.1 roms.
I recently ended development for the audio fixes because the issue began to rise in people with stock heros. but with that aside, i will create a fix for eris users if enough of you have the problem. i believe i have seen 7-8 people with it. anyways leave a comment telling me you have the issue, when it happened, what roms cause it, and what your software builds are, and what roms dont cause the issue. thanks for the cooperation and i hope i can help
Hey Avalaunchmods!
Thanks for the help with this! I am running the Aloysius (Coincidentally a Hero port):
http://forum.xda-developers.com/showthread.php?t=663893
Audio usually cuts out for me when I am receiving a notification. It will kind of stutter/jitter and then continue to play.
one of my custom ringtones cut out on an incoming call once, but only once. so it may have only been a fluke. hadnt happened before or after.
ivans .8
alexhendershott said:
Hey Avalaunchmods!
Thanks for the help with this! I am running the Aloysius (Coincidentally a Hero port):
http://forum.xda-developers.com/showthread.php?t=663893
Audio usually cuts out for me when I am receiving a notification. It will kind of stutter/jitter and then continue to play.
Click to expand...
Click to collapse
I get the same using VanillaDroid ROM.
Thanks for the help!
I have had this problem pop up intermittently, but with increasing regularity (up to 2-3 times daily at its worst). The sound profile and volumes remain unchanged, but sometimes for no apparent reason, all audio drops. If I get a call, there is no ringer. If I get a notification, there is no audible alert. If I place/answer a call, the earpiece/speakerphone are silent, and the other party doesn't hear me. The rest of the phone's functions still work, and vibrate still works, but there is no audio from any apps or OS functions until I reboot the phone.
As for particular triggers, I haven't found any yet. I had been running ivan's 0.8t2, but have downgraded to his older 0.5.4 to see if the problem is fixed. So far it hasn't popped up, but it's only been a few days.
Thanks again for your willingness to help. I'll be sure to let you know if I see the problem resurface.
I know the fix is only possible in rooted phones, but I wanted to chime in and let you know that a lot of people on 2.1 leak v2 non-rooted are having this issue, so you can see some of the symptom reports in these threads on androidforums:
http://androidforums.com/htc-droid-...en-phone-goes-silent-multiple-times-week.html
http://androidforums.com/htc-droid-eris/57804-calling-problems.html
thenestor said:
I know the fix is only possible in rooted phones, but I wanted to chime in and let you know that a lot of people on 2.1 leak v2 non-rooted are having this issue, so you can see some of the symptom reports in these threads on androidforums:
androidforums.com/htc-droid-eris/66298-phone-useless-when-phone-goes-silent-multiple-times-week.html
androidforums.com/htc-droid-eris/57804-calling-problems.html
Click to expand...
Click to collapse
I have a non-rooted phone and I have the same issues...
If by audio problems, you mean no sound via ringtones, notification or voice over the ear piece, then I have experienced it with Ivan's 08T2. I've had it happen about three times. I did a reboot and it corrected it.
another Aloysius user here, and yep, audio problems out the wazoo. good thing I text mostly.
alright this got moved to general?
i though this would fit in development haha.
anyways ill get on a fix i believe. ill put it somewhere. not dev..
I've had audio issues, but the only thing that seems to cause it for me us getting a force close on any program that is currently playing audio, such as a music player or (worse) an alarm clock.
I've never had audio just randomly cut out on me, but it definitely all stops working after such a force close
I'm having the same audio issues. I'm currently on VanillaDroid v1.0. I experienced the issue on the eris21official-root ROM as well. It usually happens after I use the camera to snap a few pictures. If I don't use the camera, it is pretty stable. Let me know if you need any further information.
Avalaunchmods said:
alright this got moved to general?
i though this would fit in development haha.
anyways ill get on a fix i believe. ill put it somewhere. not dev..
Click to expand...
Click to collapse
Thanks ..... I don't think I have had these problems (but maybe I have and just didn't realize it) but its nice nowing there is a fix out there and people like you are out there using your time to create fixes
I i use it ..... i will "buy your time back"
Avalaunchmods said:
Hey everyone. im from the Hero CDMA forum. i have made audio fix patches for the hero that fixed the audio loss for 2.1 roms.
I recently ended development for the audio fixes because the issue began to rise in people with stock heros. but with that aside, i will create a fix for eris users if enough of you have the problem. i believe i have seen 7-8 people with it. anyways leave a comment telling me you have the issue, when it happened, what roms cause it, and what your software builds are, and what roms dont cause the issue. thanks for the cooperation and i hope i can help
Click to expand...
Click to collapse
Avalaunchmods,
Since the Droid Eris kernel code was made available from HTC, have you been able to make any further progress fixing the audio loss bug for the Eris and Hero?
Right now the only solution we know of is to replace the phone. (Those of us who have gotten warranty replacements have not had the problem resurface.)
But even if the problem is related to certain hardware, it seems like there might be a way to fix the kernel's *reaction* to the problem, so that the phone doesn't become unusable.
Having the problem too.
Happened on Evil Eris and Ivans.
Any update on this? I am having the same issue on both CyanogenEris v1.1 and ELB-Cyanogen.
i am having this issue as well, running Ivans Eris_Official 1.0 Alpha. Experienced this issue on the 0.82t also. No audio from the phone's earpiece (speakerphone wont work either) when a call comes in, or if i try to call them back. have to reset the phone and then it works. I'm running setcpu at 710 now, but i wasn't on 0.82t so probably not the culprit.
My software version stats, in case it matters -
Firmware - 2.1
Baseband - 2.42.00.04.12
Kernel - 2.6.29oc [email protected]#26
Build # - 2.36.605.1 CL1165907 release-keys
Software - 2.36.605.1
PRI - 2.11_002
PRL - 51739
Eri - 5
*double post oops*
hi..i'm havin this issue too!
I'm on a froyo rom now. I was on an xtr rom when I noticed this problem. Tried to flash a new rom to get rid of it and it's still there. I can use the phone for a few hours and then the only way i can answer calls is through speakerphone.
Model Number-FroyoEris
Android Version-2.2
Baseband-2.42.00.04.12
Kernel - 2.6.29 [email protected]#3
build number-kaosfroyo v13
HEEELLLLPPPP!!!!
Audio Problem
I've had this problem every since the 2.1 update. My wife and I both had it (we both have a Eris) on unrooted phones. I rooted to ErisLightning and still had it, switched to Tainted Vanilla, and now I'm on Lightning Bolt. My wife is on Droid Does Pink and we've had the problem with every single rom. Sometimes when we receive or make calls, the phone will go completely mute. We can't hear the other person and they can't hear us. We can't hear a ring tone if calling someone either.
I use Google Voice and I sometimes get ghost voicemails. It will save the entire length of the voicemail, but it will be completely mute. Even if I restart and re-open GV it's still mute.
For now, we're just rebooting whenever we have this problem. Seems to be the only way to get audio back.
Hi,
I have tried the official roms, villainrom 12 (excellent!) and cronos 2.1.3 (also excellent!). All have the horrible bluetooth problem of skips in the music, then a speed up/slow down that results in pitch changes.
I saw that Darchdroid got it fixed in the CDMA version and wondered if there are any roms for the GSM version that have it fixed too? Just in case I missed it!
Thanks
nobody in this forum seems to know how to fix it. I've asked but nobody knows, i believe the only sense rom that i never had the skipping was behnaam's legend port.
I am not experiencing this with VillainROM 12. Didn't have it with CyanogenMOD by Elemag either...
none of the Aosp based roms have this problem it seems to be only sense related. I've had this problem with villain,cronos,chocolateeclair,etc and nobody had any idea when i asked the same question. I actually am going to try to move the bluetooth firmware and files from the legend rom i mentioned above into another newer sense rom I just have to read up on resigning the zip, I'm a super noob to all that is linux.
Moved to Q&A as not development. Temporary redirect put in place.
ggrammer said:
nobody in this forum seems to know how to fix it. I've asked but nobody knows, i believe the only sense rom that i never had the skipping was behnaam's legend port.
Click to expand...
Click to collapse
Thanks, although I have also tried Cronos 2.2 (Froyo) that doesn't have sense and it still did the pitch/speed change.
kosmiq said:
I am not experiencing this with VillainROM 12. Didn't have it with CyanogenMOD by Elemag either...
Click to expand...
Click to collapse
Can I ask what car head unit or bluetooth headset you were using? It definitely does it with my Sony BT2600 car unit and both Cronos & Villainrom.
ggrammer said:
none of the Aosp based roms have this problem it seems to be only sense related. I've had this problem with villain,cronos,chocolateeclair,etc and nobody had any idea when i asked the same question. I actually am going to try to move the bluetooth firmware and files from the legend rom i mentioned above into another newer sense rom I just have to read up on resigning the zip, I'm a super noob to all that is linux.
Click to expand...
Click to collapse
Could you let me know an AOSP rom to try that you know it works in please? - although I really like sense, I hate this issue and could live without it to get it fixed.
I'm pretty much a noob at this too but I'll help as much as I can!
like kosmiq mentioned Elemag's CMH rom doesn't seem to have this issue (I've used this rom alot and I have a 2010 Mazda3 and the bluetooth in the mazda is wonky at best and this rom works perfectly with it). As far as cronos froyo I haven't tried the bluetooth in that yet in my car but that is still an alpha development so if you need something more stable and complete then stay away from it, It is a great rom and the one I am running now but I am probably going to flash over to Maxisma's newest legend+WWE combo rom.
Good to see Maxisma back.
I did not notice in the Camera testing thread any info on whether sound was working while recording video or not. Is anyone actually getting sound on their video recordings on their Rhodium?
I am running Rhod400, reference build FRX04, but using the test 3/1 kernel from the panel/sleep thread, but that kernel should be up to date with the autobuild with the exception of having some panel fixes for quicker sleep and trying to fix SOD's.
Sound doesn't work on camcorder. Known issue... Give someone an inch and they'll take a mile eh?
arrrghhh said:
Sound doesn't work on camcorder. Known issue... Give someone an inch and they'll take a mile eh?
Click to expand...
Click to collapse
Perhaps I'm misinterpreting something, but my video recordings on WisTilt2's latest kernel and the FRX05 image include audio.
arrrghhh said:
Sound doesn't work on camcorder. Known issue... Give someone an inch and they'll take a mile eh?
Click to expand...
Click to collapse
Did I miss something? The camera thread had people in there with sound working on their recordings. I figured it was something specifically I was doing wrong not a systemic problem. Someone in there said they had the same issue until they deleted their data.img which I really didn't want to do, but I guess I will try it and see.
I searched the Camera thread before I posted this here. I saw no one mention the "no sound" issue, just people saying that sound was working. That is why I posted here. I was hoping someone had the problem like this before and knew how to fix it, since it seemed that most people had sound.
I can confirm I have sound in Blackstone. Have you checked if there are other Rhod400's with sound? Just to be sure... Ok, not the best sound recording, but it works...
Hrm, I might be mistaken. I've read some that said no sound, and others that said sound is fine. Haven't tested it myself, sorry for the misinformation.
My Rhod400 has no sound, I'd guess it's different from model to model.
rpierce99 said:
My Rhod400 has no sound, I'd guess it's different from model to model.
Click to expand...
Click to collapse
Then I may hold off on deleting my data.img file then until there is a bug fix. It seems that maybe this only affects Rhodiums or just Rhod400's.
slickdaddy96 said:
Then I may hold off on deleting my data.img file then until there is a bug fix. It seems that maybe this only affects Rhodiums or just Rhod400's.
Click to expand...
Click to collapse
You can back it up or rename it, try to boot creating a new one and see if it works. then you can restore previous data.img.
rpierce99 said:
My Rhod400 has no sound, I'd guess it's different from model to model.
Click to expand...
Click to collapse
Interesting... My RHOD400 does have sound. Didn't have to make a new data.img either.
no sound on my Rhod210
I have no sound in video recordings on my Rhod210, either. Hope there's a fix without having to make a new data.img.
gnnash said:
Interesting... My RHOD400 does have sound. Didn't have to make a new data.img either.
Click to expand...
Click to collapse
Can you tell us exactly how your setup is and if you did any special installs with camera lib. files or anything to get the sound working on your video?
I am just wondering what you have done differently from me and others to get it to run.
PlacidFury said:
I have no sound in video recordings on my Rhod210, either. Hope there's a fix without having to make a new data.img.
Click to expand...
Click to collapse
Same here.
My dad (who uses an iPhone) and a few other people have been complaining that whenever they call me, they get really bad static or sometimes even echoed feedback during phone conversations. I've tried multiple different ROMs and he says it still happens sometimes. What confuses me is that its kind of random when it happens because other times it'll work perfectly. The mic isn't broken or damaged because recording apps don't have this problem. Is it something in my settings and/or the ROM causing this? Any feedback is appreciated.
I'm currently using the latest shoshock ROM and have in the past been using tasks AOKP, which is where it first randomly started.
Are you using the ajk kernel? If you use the wrong one, you'll get that affect. FYI shostock should have mic swap kernel.
Phalanx7621 said:
Are you using the ajk kernel? If you use the wrong one, you'll get that affect. FYI shostock should have mic swap kernel.
Click to expand...
Click to collapse
I used the default one that was in the flash able zip. Unlike most ROMs, it was an all in one package so nothing else was required.
First, you want to know if this is an intermittent hardware issue. The troubleshooting test for that is flash back to stock and observe. If the problem is still present, then it is very likely to be a hardware issue.
If not, then the problem is most likely in firmware somewhere. Since this is not a common problem, and since you have had it on multiple roms, it would probably not be due to the kernel or system firmware, so you would have to look at applications to see what might be interfering.
Hi all
Please bare with me as I'm not the best when it comes to typing out what im thinking or trying to say
This info is mainly for our awesome devs but also for everyone else. Shout outs to @Unjustified Dev @DrakenFX @tdm and anyone else who can fix this
I was just wanting to help get this fixed as this one bug is keeping a lot of users including myself from moving away from stock and enjoying all the other roms available. I believe the bug has to do with the the work our beloved anonymous dev who helped correct the speaker issues a few months ago. Specifically this---> https://review.lineageos.org/#/c/168154/.
I'm pretty confidant it has nothing to do with any of the different modems people are flashing. I have tested this with all of the different modem versions for my G variant and none have made a difference
Also, there are other users that are getting this bug confused with another potential bug that has to do with distorted sound coming out when activating speakerphone while in call or something like that. I have not experienced that bug so I dont know the specifics. People are just using the term "Speakerphone bug" as both of these bugs involve the speakerphone
Now I can create the bug at will and have attached logcats below in the different scenarios. Hopefully the info is there for those who know how to fix
The steps I do to recreate the bug are as follows
1 - unlock phone and using the volume buttons, make sure the ringtone is NOT set to vibrate/silent and Do Not Disturb is NOT activated.
2 - Make a call. Call comes through earpiece as expected, no issues. Person on the other side can hear perfectly. Repeat as many times as you want, sound always comes through earpiece
3 - using volume buttons, reduce ringtone volume to vibrate/silent or turn on Do Not Disturb
4 - Make a call. Call comes through earpiece as expected, Hang up
5 - With the ringtone still set to silent/vibrate, turn the screen off using the power button and let it sit for about 5 - 10 seconds
6 - Unlock the phone and try to make a call. Call will connect but no sound will come from earpiece. Person on the other side can hear everything as per normal but we cant hear them
7 - While in call, toggle the speakerphone or if you have dial pad sounds enabled in the sound menu, press a number on the dial pad, sound now comes through earpiece as expected
From my testing and the procedure above, you can see that the bug happens when the phones ringer is put in silent/vibrate or when do not disturb is activated and the phone is locked/unlocked.
logcat 1 is with everything working normally, ringtone set to sound and call coming through earpiece as expected
logcat 2 is with ringtone set to silent and making a call. No sound comes from earpiece
logcat 3 is the same as 2 but during the call toggling speakerphone to fix
Now I dont know what is going on in the logs but I do see a lot of errors from "TFA9890"
This was all done on a fresh install of the universal bootloader, twrp 3.1.1.0, A2017G N Modem, latest LOS and Open Gapps mini and logcats were captured with MatLog on my G variant
Oh see this is Incredibly interesting, because tfa4990 is the route being used.... This is potentially incredibly helpful!!!!
I'm going to analyze these I've the weekend and see if I can figure something out. Thank you for the logs
Interesting timing on this post. I've been working on the axon7mini the past 10 days or so, and it also uses the tfa9890 amp. So I've started to familiarize myself with how all this stuff works. (I have pretty much zero experience with android audio in the past).
Fantastic post, well done. I have only encountered the problem a couple of times but upon reading what you wrote a little light bulb went off, that is exactly the situation that it occurs for me as well. It's this sort of interaction and support between the users and devs at xda have that makes it all so worthwhile. Thanks again.
As someone who's dealt with this bug for a long, long time... I have to commend you on a fantastic post. Thanks, and I hope this leads to a solution!
I hope this is looked into in the process of porting LOS 15. Would be cool to see this issue disappear.
Would this bug also happen on the U variant? I tried to recreate it using the steps above and it worked fine.
arecad said:
Would this bug also happen on the U variant? I tried to recreate it using the steps above and it worked fine.
Click to expand...
Click to collapse
I think I have read somewhere that it is not affecting U which might be the reason this has not yet been fixed but I cannot remember where I read this.
We would need the logs from an U variant to check if it looks the same.
sToRm1nG said:
I think I have read somewhere that it is not affecting U which might be the reason this has not yet been fixed but I cannot remember where I read this.
We would need the logs from an U variant to check if it looks the same.
Click to expand...
Click to collapse
It does affect the U variant. I have one and it happened a few times that when I would call someone I had no ringing tone coming from the earpiece unless I toggled the speakerphone on/off.
same problem here in a2017g aosp extended...
So I take it we can give up trying to solve this? Seems to exist in all non stock roms.
Wish someone would fix it. I don't even know where to begin, and with what I've read about the axon 9, i wont be switching phones for quite some time.
Knuxyl said:
Wish someone would fix it. I don't even know where to begin, and with what I've read about the axon 9, i wont be switching phones for quite some time.
Click to expand...
Click to collapse
simply use macrodroid fix it when phone call is activated.Speakerphone on ,speakerphone off .
Thats it
Dodgexander said:
So I take it we can give up trying to solve this? Seems to exist in all non stock roms.
Click to expand...
Click to collapse
Knuxyl said:
Wish someone would fix it. I don't even know where to begin, and with what I've read about the axon 9, i wont be switching phones for quite some time.
Click to expand...
Click to collapse
did you guys try the fix that @Miustone plasters all over XDA?
@Miustone Could you make a flashable zip with ONLY THAT ONE FIX for the Fluence stuff? Pretty please?
Choose an username... said:
did you guys try the fix that @Miustone plasters all over XDA?
@Miustone Could you make a flashable zip with ONLY THAT ONE FIX for the Fluence stuff? Pretty please?
Click to expand...
Click to collapse
Fluence settings will not fix driver implementation. Miustone's claims are misleading. I have tested it to death
The only way to fix would be by a Dev with audio skills. Good luck finding one. I've tried
Stay on a stock roms or risk not hearing in calls in other roms
Tebor said:
Fluence settings will not fix driver implementation. Miustone's claims are misleading. I have tested it to death
The only way to fix would be by a Dev with audio skills. Good luck finding one. I've tried
Stay on a stock roms or risk not hearing in calls in other roms
Click to expand...
Click to collapse
I fixed all Mic Bugs, Just the Echo is left which seams to came from /system/vendor/etc. Don't blame Me for the Bugs, i never touched the Sources of the Axon 7 and besides Kranoner has No Dev ever asked Me about it again. That My Patch is fixing Bugs means Just that there are Things Missing which are working and present on other Devices too...
I was coming from the LG G5 which has used almost the Same Fluence and Mic Configs as currently present in the Patch. Point.
Miustone said:
I fixed all Mic Bugs, Just the Echo is left which seams to came from /system/vendor/etc. Don't blame Me for the Bugs, i never touched the Sources of the Axon 7 and besides Kranoner has No Dev ever asked Me about it again. That My Patch is fixing Bugs means Just that there are Things Missing which are working and present on other Devices too...
I was coming from the LG G5 which has used almost the Same Fluence and Mic Configs as currently present in the Patch. Point.
Click to expand...
Click to collapse
Well, you have a chance to prove it! Make a flashable zip with ONLY the call bug fixes. If it actually fixes their problems then they'll believe you. otherwise they're right not to.
It's next to pointless using a custom rom if you want a good daily driver.
I bought this phone because I thought things like this could be solved this day and age but I won't be making that mistake next time!
Sent from my ZTE A2017U using Tapatalk
Miustone said:
I fixed all Mic Bugs, Just the Echo is left which seams to came from /system/vendor/etc. Don't blame Me for the Bugs, i never touched the Sources of the Axon 7 and besides Kranoner has No Dev ever asked Me about it again. That My Patch is fixing Bugs means Just that there are Things Missing which are working and present on other Devices too...
I was coming from the LG G5 which has used almost the Same Fluence and Mic Configs as currently present in the Patch. Point.
Click to expand...
Click to collapse
Omg who is blaming you for bugs? Your claiming you fixed it but many others still have this issue
This thread is not about mic issues. Please re-read first post and for the hell of it, check out the logcats. They might help you actually fix it
Unless your digging into the audio/dac driver code, I'm doubtful it will ever be fixed
Why do yall think its the driver? I dont have any problems with audio, its how the Phone app is handling it. If i was to debug this I would check the source for the Phone app and trace it from there. It seems like something might not be using the driver correctly, but the driver seems to be working fine. I could be wrong but I'm not new to linux and android, just no experience with audio development.
Maybe try installing stock phone app on LOS or RR and see if it still has problems. That would either show where the problem is or eliminate Phone app from being source of problem.