I installed android on my htc hd mini but the microphone does not work, when I answer a call anything dumb
Microphone is not modded yet to work on android. Developers like Robin, cardsharing, tzacapaca, Schlunds etc etc have started the work. Till this date wifi, memory card and battery are being fixed.
Hoping the other essentials things get fixed soon.
not working why
callers cannot hear
yees everyone is aware the microphone does not work yet.. if you look on the status of the project it will say.. there is no need for people to keep making continuous posts stating that certain elements aren't working
if you want the microphone fixed now... do it yourself
having read in the battery and wifi still don't work, however, has been resolved I thought could be some news
fixed probblema battery and wi-fi someone is working on the MIC?
Related
Ever since I've owned this Shift, I've only ever known the microphone to work on one occasion, and then I started fiddling with flashing ROMs and Radios. Now the microphone will not work for nothing on either side of the Shift I have tried everything I can think of. I've heard that it depends on a combination of ROM and Radio, but I must of tried every single possible option and still nothing. Anyone have any experience with this? I can't just have a faulty microphone, it worked at one point. Any help would be appreciate. And yes, despite the fact that my iPhone 4 comes in the mail today, I'm am still very interested in playing around with the Shift. This getting it to call out and send my voice thing is beginning to mock me, and I'm taking it as a challenge.
Post #25 in Thaihugo's Age of Reason ROM thread gives the URL for a good radio ROM that works with his ROM.
http://forum.xda-developers.com/showthread.php?t=495143&page=3
So I'd install that radio image if I were you, and then install Thaihugos ROM. As far as I know, that combination is the most concrete base for your HTC Shift.
From there, you could see if your microphone works, and then move on to any other ROM/radio, keeping note of whether your microphone continues to work.
Hope this helps.
Just wanted to give you guy the heads up that CyanogenMod is working pretty good on the N5100 i did a clean install and i am not running into any issues at all. I did read that there is a camera issue with it crashing after taking a pic but i tested it and it is working fine . the other issues i read about was voice search via Bluetooth, i was unable to test this because i don't have a Bluetooth headset yet. also wanted to say that the battery life is no bad at all.
MERK77 said:
Just wanted to give you guy the heads up that CyanogenMod is working pretty good on the N5100 i did a clean install and i am not running into any issues at all. I did read that there is a camera issue with it crashing after taking a pic but i tested it and it is working fine . the other issues i read about was voice search via Bluetooth, i was unable to test this because i don't have a Bluetooth headset yet. also wanted to say that the battery life is no bad at all.
Click to expand...
Click to collapse
Working great for me.
Merk77 - there´s no ground to create a new thread.
Pls take a look and post here
thx
Thread closed.
There is no need for a new thread.
***See Kevev's excellent workaround to this problem in post#8 below***
I believe we need a thread dedicated to troubleshooting this problem. I know there are a very few others that touch on it but no one place to discuss possible solutions. Additionally it's quite hard to look for answers using google as thread titles don't specifically mention the issue. If mods think this does not warrant its own thread do as you must.
If you have T-Mobile paired with this device you know call quality sucks, and sometimes randomly. Personally I have had excellent to terrible call quality since the MM upgrade with Volte on. Choppiness on my end with some Roms, choppiness on the other end with other Roms. I don't use the phone feature too often on the phone so it has taken me quite a while to 'test' Roms looking for good call quality.
Yup Moto/Lenovo sux. I'm done with them. Gave the phone to my Mother with VoLTE disabled.
One thing to note for any Devs willing to look into the issue, it occures when using the earpiece. It does not happen when on speakerphone call and headphone call. When the issue happens pressing the power button to wake screen or pressing either volume button fixes the issue for a few seconds. My guess is this is a power management issue and maybe the bus speed for the audio system is too slow. I wonder if we can prevent sleep while in a call.
Maybe some can try this app?
https://play.google.com/store/apps/details?id=eu.thedarken.wl
I'll play around with that this weekend, thanks.
And as luck would have it I'm on 12/22 aicp with no calling issues after calling 2 people in a different area and one landline.. all without modifying any settings or running the wakelock script. So I'll run this rom over the holiday and see how call quality is. Good news certainly, we'll see how long it lasts. FWIW I always full erase and re-download apps
Make sure you test in known congested areas.
Anyone interested in testing my wakelock script on stock MM for MXPE please send me a PM. I am looking for users who regularly have VoLTE issues on T-Mobile or MetroPCS. The script does NOT require root. I don't want to post the script until I am sure it works. Also please don't share the script until it is released publicly. Thank You.
OK I am pretty sure the wake lock script works. My mother has been using it for 3 days and so far no choppy audio. The script will need to be imported into the Automate app. Start the script and set Automate to Run on startup so that the script is running after reboots. Also be sure to install Telephony permissions from within the Wakelock script screen in Automate. Good luck.
Automate:
https://play.google.com/store/apps/details?id=com.llamalab.automate
Script:
https://drive.google.com/folderview?id=0B2M_XoBZxi1iRUlvb3pNemI3WFU
I can add my confirmation that Kevev's script works great. I don't use the phone much so it took a while to get a dozen or so calls that worked with the script.
This is definitely the best workaround for T-Mobile subscribers until Moto fixes (fingers crossed) the issue in nougat.
Awesome. Glad to know it works.
Good morning everyone! Since I've moved from stock I've has an issue with the MIC during calls where the person on the other end will not be able to hear me. I would have to put the phone on speaker and scream into the MIC for them to hear me. Disabling google voice or toggling speaker would not fix the issue for me. Today I was looking through the modules on Magisk when I saw one called "Android MIC fix." After downloading, installing and restarting the phone I made a call and walla. The recipient was able to hear me clearly. Needless to say I was very much excited. So for those with the MIC issue I recommend trying out this module.
Thank you for posting this. I'm desperate for a mic fix. I've just installed it, but will not be back in an area with a cell phone signal until tomorrow. I'll post in a day or two whether it seem to have fixed my mic issues. Magisk will not pass SafetyNet check, but it might be worth giving up some apps, if it can fix the issiue with people not hearing me on a call until I turn speakerphone on and off.
celticchrys said:
Thank you for posting this. I'm desperate for a mic fix. I've just installed it, but will not be back in an area with a cell phone signal until tomorrow. I'll post in a day or two whether it seem to have fixed my mic issues. Magisk will not pass SafetyNet check, but it might be worth giving up some apps, if it can fix the issiue with people not hearing me on a call until I turn speakerphone on and off.
Click to expand...
Click to collapse
I think Magisk passes safetynet again. there are some XDA articles about the new beta. I didn't try though
Choose an username... said:
I think Magisk passes safetynet again. there are some XDA articles about the new beta. I didn't try though
Click to expand...
Click to collapse
After installing the Magisk 13 beta, it does pass SafetyNet check for me. This is where to download the beta, of course, but not for anyone who is new to this stuff, of course (Betas are always at your own risk).
https://forum.xda-developers.com/apps/magisk/beta-magisk-v13-0-0980cb6-t3618589
As for the mic issue, more to come in a day or two, once I'm in an area with cellular coverage again..
This fix didn't work for me.
This fix sounds promising, since I've found that when the mic seems to be non-functional, that the other party on the line can hear me if I yell at the phone. However, despite getting Android pay working on B25 with Magisk 13, it just crashes when trying to install modules. Anyone else have any luck with it?
After using the module some more I found that, while yes, I was able to use the headset, the quality of the call was horrendous. So I disabled the module. I'll just have to live with using speaker until a permanent fix is found
This also didn't work for me. I kept having further problems with Magisk beta, so I've removed it for now, and I'm hoping for a better patch, before shelling out for a new phone.
As for B06 nougat, turkey (a2017g) the issue feels like solved for me. I've done about 40-50 callings without any doubts. Also no need to turn on/off loudspeaker. "Ok Google" from any screen turned on so imo - issue fixed.
I didn't faced any mic issue..... I just tuned off the OK Google even on 7.0.1 till then everything is perfect
Laleka said:
I didn't faced any mic issue..... I just tuned off the OK Google even on 7.0.1 till then everything is perfect
Click to expand...
Click to collapse
Yeah because the issue occur when you have "ok Google" turned on from any screen and now you can have it turned on without any mic troubles in call.
Hey everyone, hope all is well.
I found a fix for my axon. If you don't want to read my trial and errors and just want the fix, scroll to the bottom.
I bought an axon 7 off eBay. From day 1 people were saying they couldn't hear me very well. I thought it was cell service.
It seemed to slowly got worse.
It got to the point where people couldn't hear me at all.
I downloaded an app to locate cell towers and service range. Service didn't seem too bad...
Found forums like this one, tried talking on speakerphone. It worked, but people said it was still hard to hear me, cutting in and out, etc. Turned off mic access for ok Google and eventually EVERYTHING else.
Deleted apps even... No fix.
Eventually went to a place I knew had good cell service, called someone, and they couldn't hear me at all! Def not mic access, def not service...
Axons warranty doesn't work for resold phones... The speakers and Dolby..I didn't want to go back to a Samsung or whatever..
That's when I started looking for hardware fixes.
I decided to do a Google search one last time before starting down that road, but looked at videos this time.
And I found a fix!!!!!!
youtu.be/KNGMM-H0oxc
So simple.
So going back to the forums I read before and posting my fix. Hopefully it helps others.
So happy!
I would like to keep the phone but I'm back to using my OnePlus One because it's a more capable phone due to it having stable custom ROMs available. Newegg won't take the Axon 7 back because I found out they have a no return policy on non contract phones. I'd rather not sell it for a loss but the phone is useless to me at the moment.
The custom ROMs I've tried are close but the no audio call bug is a show stopper. I'd like the phone portion of the phone to work properly. <--- Reported fixed with light patch v1.2 experimental
Also, the Bluetooth is not working for call management on every custom ROM I've tried except for Pure Nexus. If it works on Pure Nexus why can't it be made to work on other AOSP ROMs and LOS based ROMs? Can the Bluetooth stack (if that's even the right term) be pulled from Pure Nexus and be applied to other custom ROMs? Could a flashable ZIP be created to implement Bluetooth as described above on custom ROMs?
I'm not positive, but I think you might get in trouble, or your post deleted for trying to sell your device on here. You should be able to get about 300 out of it on swappa or ebay.
Try BadBoy rom. It's based on the zte stock rom but has some custom aspects. Runs smooth with better battery life and much better camera than any of the Lineage based roms I've tried.
ThePublisher said:
I'm not positive, but I think you might get in trouble, or your post deleted for trying to sell your device on here. You should be able to get about 300 out of it on swappa or ebay.
Try BadBoy rom. It's based on the zte stock rom but has some custom aspects. Runs smooth with better battery life and much better camera than any of the Lineage based roms I've tried.
Click to expand...
Click to collapse
Yeah you're prolly right. I'll excise the last part. I tried Bad Boyz. It's great but I can't do stock based. I've come to rely on all the tweaks in custom ROMs. I should have done more research prior to buying the phone. I need a tweaker's phone like the OnePlus 5. Thank you for your response.
I guess if you like downgrading your display, paying more, and getting jelly scrolling as a thank you then the OnePlus 5 would be for you.
Hi there,
I haven't looked into it yet (had no problems with the no audio call bug at first, but now it started showing up), but I'm pretty sure the bug can be 'hidden' with some tasker script (phone app starts, speaker off/on or so)...
So if you are a tweaker, you are likely rooted anyway and this might be an option...
Whoooo? said:
Hi there,
I haven't looked into it yet (had no problems with the no audio call bug at first, but now it started showing up), but I'm pretty sure the bug can be 'hidden' with some tasker script (phone app starts, speaker off/on or so)...
So if you are a tweaker, you are likely rooted anyway and this might be an option...
Click to expand...
Click to collapse
Call bug is due tu Google now app, disable OK Google hot word. It solved mine and others too.
---------- Post added at 07:22 AM ---------- Previous post was at 07:17 AM ----------
Doc Ames said:
I would like to keep the phone but I'm back to using my OnePlus One because it's a more capable phone due to it having stable custom ROMs available. Newegg won't take the Axon 7 back because I found out they have a no return policy on non contract phones. I'd rather not sell it for a loss but the phone is useless to me at the moment.
The custom ROMs I've tried are close but the no audio call bug is a show stopper. I'd like the phone portion of the phone to work properly. Also, the Bluetooth is not working for call management on every custom ROM I've tried except for Pure Nexus. If it works on Pure Nexus why can't it be made to work on other AOSP ROMs and LOS based ROMs? Can the Bluetooth stack (if that's even the right term) be pulled from Pure Nexus and be applied to other custom ROMs? Could a flashable ZIP be created to implement Bluetooth as described above on custom ROMs?
Click to expand...
Click to collapse
Call bug is due tu Google now app, disable OK Google hot word. Phone is always listening to OK Google to activate Google assistant or search that's why it disabling mic in audio calls sometime...
ArgonautPollux said:
I guess if you like downgrading your display, paying more, and getting jelly scrolling as a thank you then the OnePlus 5 would be for you.
Click to expand...
Click to collapse
Thank you. That's very helpful.
Laleka said:
Call bug is due tu Google now app, disable OK Google hot word. Phone is always listening to OK Google to activate Google assistant or search that's why it disabling mic in audio calls sometime...
Click to expand...
Click to collapse
The one time I had the call bug I'm pretty sure I had "OK Google" hotword detection turned off. Although I hardly used the phone. I'll bear it in mind if I fire up the Axon 7 again.
Doc Ames said:
The one time I had the call bug I'm pretty sure I had "OK Google" hotword detection turned off. Although I hardly used the phone. I'll bear it in mind if I fire up the Axon 7 again.
Click to expand...
Click to collapse
I had success getting rid of the call bug flashing Light Patch v1.2 - experimental.
Whoooo? said:
Hi there,
I haven't looked into it yet (had no problems with the no audio call bug at first, but now it started showing up), but I'm pretty sure the bug can be 'hidden' with some tasker script (phone app starts, speaker off/on or so)...
So if you are a tweaker, you are likely rooted anyway and this might be an option...
Click to expand...
Click to collapse
That's a really good idea to use a Tasker task. I wonder if Bluetooth will ever be fixed though. Problem is that Bluetooth connectivity issues only happen with some car head units. It seems like devs aren't looking to fix Bluetooth on custom ROMs because they don't think there's an issue.
piet8stevens said:
I had success getting rid of the call bug flashing Light Patch v1.2 - experimental.
Click to expand...
Click to collapse
I heard another member mention that light patch fixes the call bug. I thought he was mistaken because I'm pretty sure I had light patch v1.1 installed when the call bug happened to me. Sounds like v1.2 preview will fix it. I'm going to count the call bug portion of my question as solved since there are workarounds and everyone recognizes it as a problem so it will get fixed eventually.
The Bluetooth remains a showstopper though. I would gladly pay a significant sum if somebody could make a flashable zip that could fix Bluetooth for custom ROMs. It works in Pure Nexus so having BT work in AOSP ROMs is definitely possible. Hopefully for LOS ROMs too.
Also for me the showstopper/deal breaker is that the phone loses it's loud speaker volume in custom ROMs. I use it very often.
Doc Ames said:
I heard another member mention that light patch fixes the call bug. I thought he was mistaken because I'm pretty sure I had light patch v1.1 installed when the call bug happened to me. Sounds like v1.2 preview will fix it. I'm going to count the call bug portion of my question as solved since there are workarounds and everyone recognizes it as a problem so it will get fixed eventually.
The Bluetooth remains a showstopper though. I would gladly pay a significant sum if somebody could make a flashable zip that could fix Bluetooth for custom ROMs. It works in Pure Nexus so having BT work in AOSP ROMs is definitely possible. Hopefully for LOS ROMs too.
Click to expand...
Click to collapse
Can you expand a bit on what "Bluetooth is not working for call management on every custom ROM" means? I use bluetooth with my car and have no issues.
piet8stevens said:
Can you expand a bit on what "Bluetooth is not working for call management on every custom ROM" means? I use bluetooth with my car and have no issues.
Click to expand...
Click to collapse
Audio streaming with AVRCP works fine. However the head unit (Kenwood KMM-BT515HD) shows a status of "Connected (no phone)" in Android Bluetooth settings. This means that I can't use my deck to make/answer calls or use voice commands. It works as expected on stock and on Pure Nexus. Others are having this issue too. I know a couple members had issues on Nissan decks and one that I know of had a BMW deck.
Does anyone get voice echo during voice calls on custom roms?
I'm looking to buy the Axon 7 soon, but the voice echo would be a dealbreaker if it exists.
( it's currently an issue with the custom roms I've tried on my Xperia XZ - if I call anyone they complain that they can hear an echo of their voice )
Waancho said:
Also for me the showstopper/deal breaker is that the phone loses it's loud speaker volume in custom ROMs. I use it very often.
Click to expand...
Click to collapse
You need to install Dolby digital
Im on RR build from Jun 11, connect's to my hyundai veloster oem headunit tru bluetooth with 0 issues, it can download my contacts, route calls perfectly fine 0 issues what so ever, the mic bug i get it once in a blue moon, and the 720p/1080p/2k/4k 60FPS slow motion videos on youtube is the other issue, besides that its my daily driver for months now.
rafyvitto said:
Im on RR build from Jun 11, connect's to my hyundai veloster oem headunit tru bluetooth with 0 issues, it can download my contacts, route calls perfectly fine 0 issues what so ever, the mic bug i get it once in a blue moon, and the 720p/1080p/2k/4k 60FPS slow motion videos on youtube is the other issue, besides that its my daily driver for months now.
Click to expand...
Click to collapse
Whatever the issue is it only causes connection problems (i.e. "Connected (no phone)" ) with some head units. I should try connecting to my roommate's Toyota. I bet it would connect as a phone just fine. There was an issue with BT in LOS that was causing AVRCP (remote control, song info) to not work with some head units. I'm guessing the devs couldn't solve the underlying issue because the fix was to roll back the AVRCP version. It seems there are still compatibility issues with Bluetooth in LOS and AOSP ROMs (save Pure Nexus).
If I could get BT to work fully with my car I would absolutely use RR as my daily driver. Unfortunately the phone is sitting in the box right now until I lose patience and sell the phone or the BT gets fixed. Sucks because I was totally thrilled with the phone after installing and setting up AOSPExtended. Then I got into my car and noticed the issue forcing me back to the dusty, but trusty OnePlus One.
supergear said:
You need to install Dolby digital
Click to expand...
Click to collapse
Hi there,
Thanks a lot for the info (new to me) - to verify:
Are you referring to
https://forum.xda-developers.com/android/apps-games/soundmod-axon-7-dolby-atmos-t3412342
or is there another (preferable safe/easy to install) version one would need?
Thanks again!