Basically, whether I have the external MIC plugged in, or disconnected absolutely noone can hear me. They say I sound like I am very far away. I am forced to switch to my handset so they can hear me. I have tried with other external MIC's and got the same results. I haven't tried any noise canceling MIC's or amplified MIC's (if they exist).. What MIC's are you using and how are you getting callers to hear you?
Am I needing to open my unit and disconnect the internal MIC? If I do this, will the external MIC still work (or are they on the same circuit?)
Need4Camaro said:
Basically, whether I have the external MIC plugged in, or disconnected absolutely noone can hear me. They say I sound like I am very far away. I am forced to switch to my handset so they can hear me. I have tried with other external MIC's and got the same results. I haven't tried any noise canceling MIC's or amplified MIC's (if they exist).. What MIC's are you using and how are you getting callers to hear you?
Am I needing to open my unit and disconnect the internal MIC? If I do this, will the external MIC still work (or are they on the same circuit?)
Click to expand...
Click to collapse
I don't think you will need to disconnect the internal mic. In my opinion and testing, the problem with the call sound quality is software related.
One thing you can try is revoking the microphone permission on the Google app. Then try making make a phone call. To do this, Go to Settings...Apps.... Scroll down to the Google app and touch Permissions. Turn off the microphone permission and try making a phone call to see if the sound quality improves. Alternatively you can completely uninstall the Google app and try making a phone call.
It seems the Google app ties up the microphone. However, bear in mind, revoking the microphone permission will disable the "Ok Google" capability. Hope this helps.
PoppaRoxie1986 said:
I don't think you will need to disconnect the internal mic. In my opinion and testing, the problem with the call sound quality is software related.
One thing you can try is revoking the microphone permission on the Google app. Then try making make a phone call. To do this, Go to Settings...Apps.... Scroll down to the Google app and touch Permissions. Turn off the microphone permission and try making a phone call to see if the sound quality improves. Alternatively you can completely uninstall the Google app and try making a phone call.
It seems the Google app ties up the microphone. However, bear in mind, revoking the microphone permission will disable the "Ok Google" capability. Hope this helps.
Click to expand...
Click to collapse
Yes, disable ok Google "everywhere" and it should work OK...any app that takes over the microphone and is on when a call is placed will mess with the call quality.
Make sure you don't change the microphone option in the special settings. I made a change to "external microphone" since I'm using the 3.5 mm jack and no one was able to hear me.
I believe it needs to be set to internal microphone. It was in the special settings that required a password, I believe.
PoppaRoxie1986 said:
I don't think you will need to disconnect the internal mic. In my opinion and testing, the problem with the call sound quality is software related.
One thing you can try is revoking the microphone permission on the Google app. Then try making make a phone call. To do this, Go to Settings...Apps.... Scroll down to the Google app and touch Permissions. Turn off the microphone permission and try making a phone call to see if the sound quality improves. Alternatively you can completely uninstall the Google app and try making a phone call.
It seems the Google app ties up the microphone. However, bear in mind, revoking the microphone permission will disable the "Ok Google" capability. Hope this helps.
Click to expand...
Click to collapse
Thank you for this information, I would definitely like to keep google commands however, is there any way I can just have these settings revoked when someone calls me and re-enabled after the call?
Quiksmage said:
Make sure you don't change the microphone option in the special settings. I made a change to "external microphone" since I'm using the 3.5 mm jack and no one was able to hear me.
I believe it needs to be set to internal microphone. It was in the special settings that required a password, I believe.
Click to expand...
Click to collapse
I may have changed this in hindsite, what is the password to get into these settings? I forgot.
Need4Camaro said:
I may have changed this in hindsite, what is the password to get into these settings? I forgot.
Click to expand...
Click to collapse
3368
if it is the 5009 model motherboard you most probably have lose solder joints between the core and the motherboard,
resolder them well
Need4Camaro said:
Thank you for this information, I would definitely like to keep google commands however, is there any way I can just have these settings revoked when someone calls me and re-enabled after the call?
Click to expand...
Click to collapse
There is a dialer app, GVC call handler for joying units available on the play store and included in the GTX custom rom that will kill the Google task just before dialing a phone number.
Also there is an Xposed module that will keep the joying Bluetooth app from staying on top. I don't know if @gtxaspec or @surfer64 included any kind of mechanism with it which would kill Google only while a call is in progress and relaunch it when the call ends. But it is a good idea.
Please give my earlier suggestion a try to see if your call sound quality improves. That would at least let you know if indeed the problem is being caused by the Google app and if your mic is working properly.
PoppaRoxie1986 said:
There is a dialer app, GVC call handler for joying units available on the play store and included in the GTX custom rom that will kill the Google task just before dialing a phone number.
Also there is an Xposed module that will keep the joying Bluetooth app from staying on top. I don't know if @gtxaspec or @surfer64 included any kind of mechanism with it which would kill Google only while a call is in progress and relaunch it when the call ends. But it is a good idea.
Please give my earlier suggestion a try to see if your call sound quality improves. That would at least let you know if indeed the problem is being caused by the Google app and if your mic is working properly.
Click to expand...
Click to collapse
Okay so here is what I am running into now. When I go to settings and then apps and then Google, I see the permissions, and I can even select Microphone, but I do not get an option at all to disable the permission. It just gives me a popup window with the description and thats all.
Also with the GVC Call handler app, I have downloaded it but when I say "Okay Google Call (name)" it replies "I'm sorry, but I am not able to make calls at this time."
Am I doing something wrong?
doctorman said:
if it is the 5009 model motherboard you most probably have lose solder joints between the core and the motherboard,
resolder them well
Click to expand...
Click to collapse
I can't tell what model motherboard it is but I do not feel comfortable soldering on the device.
Quiksmage said:
Make sure you don't change the microphone option in the special settings. I made a change to "external microphone" since I'm using the 3.5 mm jack and no one was able to hear me.
I believe it needs to be set to internal microphone. It was in the special settings that required a password, I believe.
Click to expand...
Click to collapse
I went to Advanced Vehicle settings and did not see this option.
I also went to Developers Options and also did not see this option.
Am I missing something?
Need4Camaro said:
Okay so here is what I am running into now. When I go to settings and then apps and then Google, I see the permissions, and I can even select Microphone, but I do not get an option at all to disable the permission. It just gives me a popup window with the description and thats all.
Also with the GVC Call handler app, I have downloaded it but when I say "Okay Google Call (name)" it replies "I'm sorry, but I am not able to make calls at this time."
Am I doing something wrong?
I can't tell what model motherboard it is but I do not feel comfortable soldering on the device.
I went to Advanced Vehicle settings and did not see this option.
I also went to Developers Options and also did not see this option.
Am I missing something?
Click to expand...
Click to collapse
Hmm I'm not sure why you wouldn't be able to revoke that permission. The microphone setting that Quiks was referring to is in the Car Settings app on the far right menu that requires the 3368 password. The workaround for the can't make calls yet requires the dpi to be changed, which requires the unit to be rooted. The joying extra tools app found here on xda can be used to change the dpi and do many other cool mods.
PoppaRoxie1986 said:
Hmm I'm not sure why you wouldn't be able to revoke that permission. The microphone setting that Quiks was referring to is in the Car Settings app on the far right menu that requires the 3368 password. The workaround for the can't make calls yet requires the dpi to be changed, which requires the unit to be rooted. The joying extra tools app found here on xda can be used to change the dpi and do many other cool mods.
Click to expand...
Click to collapse
I'm still using Android 5.1 could this be the issue? I didn't want to upgrade to 6 because I heard alot of people were having problems with it.
Also how compatible is a USB or Bluetooth MIC to the unit?
Need4Camaro said:
I'm still using Android 5.1 could this be the issue? I didn't want to upgrade to 6 because I heard alot of people were having problems with it.
Also how compatible is a USB or Bluetooth MIC to the unit?
Click to expand...
Click to collapse
Ah that likely explains the permission thing. I have not experienced 5.1 on my unit as it came preloaded with 6.0. Also I'm running the gtx custom rom which is android 6.0 based on my unit.
Too bad we don't have a way to go back to 5.1 once it's been updated to 6.0.
PoppaRoxie1986 said:
Ah that likely explains the permission thing. I have not experienced 5.1 on my unit as it came preloaded with 6.0. Also I'm running the gtx custom rom which is android 6.0 based on my unit.
Too bad we don't have a way to go back to 5.1 once it's been updated to 6.0.
Click to expand...
Click to collapse
Yeah thats why I have been afraid of upgrading as mostly everything works.
I heard that 6.0 doesn't support USB Storage (and I have a 1 Terabyte USB Hard Drive filled with MP3's and Videos stuffed in my dash) and I don't want to lose that.
Does the GTX custom ROM support USB storage? Google Voice without mods? Multiple NAV Apps (5.1 only allowed you to use one NAV app as a default app and the rest would have no audio, it was fixed with an Sofia Server mod or something.) Open Bluetooth?
Its getting worse, even google commands are having a difficult time hearing me now.
Is there any external mic I could use that may solve this problem?
Need4Camaro said:
I can't tell what model motherboard it is but I do not feel comfortable soldering on the device.
Click to expand...
Click to collapse
5009 motherboard from Joying
picture attached
the Core is soldered to motherboard... all those pins have a chance of getting lose
5009 model sold mostly in late 2016 and earlier 2017. since late 2017 Joying moved away to 6021 motherboards again with no soldering.
Android 6 ROM is working great and updated still monthly , I would recomend that for intel Sofia .
if that does not fix it you need soldering repair.
doctorman said:
5009 motherboard from Joying
picture attached
the Core is soldered to motherboard... all those pins have a chance of getting lose
5009 model sold mostly in late 2016 and earlier 2017. since late 2017 Joying moved away to 6021 motherboards again with no soldering.
Android 6 ROM is working great and updated still monthly , I would recomend that for intel Sofia .
if that does not fix it you need soldering repair.
Click to expand...
Click to collapse
I'll try Android 6 but if that doesn't work its going in the trash. I need a better quality unit I've had nothing but trouble out of Joying and the rest of the Android HU's I've had. They would last about a year and in some way or another become dysfunctional. This would be my third unit and I thought for sure with Intel that this would be the one.
I really want to just make my own unit base on an Intel Pico Motherboard. The only thing stopping me is I'm not sure what LCD's would be compatible with Android or not.
Need4Camaro said:
I'll try Android 6 but if that doesn't work its going in the trash. I need a better quality unit I've had nothing but trouble out of Joying and the rest of the Android HU's I've had. They would last about a year and in some way or another become dysfunctional. This would be my third unit and I thought for sure with Intel that this would be the one.
I really want to just make my own unit base on an Intel Pico Motherboard. The only thing stopping me is I'm not sure what LCD's would be compatible with Android or not.
Click to expand...
Click to collapse
I have had my mtcB Joying unit with android 4.4.4 still running in my car after many years with no problem
I do repairs for all USA customers for Joying, the only unit Joying had major issues with is that 5009 motherboard.
what other units have you tried and what issues have you had.
doctorman said:
I have had my mtcB Joying unit with android 4.4.4 still running in my car after many years with no problem
I do repairs for all USA customers for Joying, the only unit Joying had major issues with is that 5009 motherboard.
what other units have you tried and what issues have you had.
Click to expand...
Click to collapse
The first one was a 4.4.4 unit which had bad mic issues. I soldered an external MIC and that worked well but eventually the unit became sluggish even after factory resets to the point where it became unusable plus it was only 8GB (5 usable) and didn't have enough space for apps.
I swapped out for my first Android 5.1.1 unit but it had serious GPS problems right out the box and they were not willing to address it, Google Maps / Waze would randomly lose position and would stop tracking my location entirely (literally telling me I am someplace that I am several miles from) while the space and ram concerns were addressed, I tried to resolve the navigation issues but ended up bricking the unit.
Then swapped out to my current one. Current one was horrible right out the box, no Ok Google commands, could only use one Navigation app, bluetooth calls were exceptional at the time but not exactly great, no bluetooth functionality outside of pairing phones. I eventually modded based on the rollup thread and got Ok Google commands to work, could not use them to text or make calls though. Tried the GVCall Handler but didn't work but I am finding I have to change my DPI settings to fix that. Bluetooth calls slowly began losing quality and over time I began to have GPS problems as well, It would stop updating my location or randomly point me in the wrong direction. Fixed by adding a heatsink and fan to the unit. Now I absolutely must switch to my handset to make calls because absolutely noone can hear me when I make bluetooth calls, and the google app is misunderstanding me.
Need4Camaro said:
The first one was a 4.4.4 unit which had bad mic issues. I soldered an external MIC and that worked well but eventually the unit became sluggish even after factory resets to the point where it became unusable plus it was only 8GB (5 usable) and didn't have enough space for apps.
I swapped out for my first Android 5.1.1 unit but it had serious GPS problems right out the box and they were not willing to address it, Google Maps / Waze would randomly lose position and would stop tracking my location entirely (literally telling me I am someplace that I am several miles from) while the space and ram concerns were addressed, I tried to resolve the navigation issues but ended up bricking the unit.
Then swapped out to my current one. Current one was horrible right out the box, no Ok Google commands, could only use one Navigation app, bluetooth calls were exceptional at the time but not exactly great, no bluetooth functionality outside of pairing phones. I eventually modded based on the rollup thread and got Ok Google commands to work, could not use them to text or make calls though. Tried the GVCall Handler but didn't work but I am finding I have to change my DPI settings to fix that. Bluetooth calls slowly began losing quality and over time I began to have GPS problems as well, It would stop updating my location or randomly point me in the wrong direction. Fixed by adding a heatsink and fan to the unit. Now I absolutely must switch to my handset to make calls because absolutely noone can hear me when I make bluetooth calls, and the google app is misunderstanding me.
Click to expand...
Click to collapse
when did you buy your unit, perhaps we can have it repaired or upgraded under warranty?
email me directly and I will see what I can do .
the mtcB model was solid
the mtcD model had some software issue that are resolved in the final ROM.
5009 motherboards as I suspect you have has soldering issue
the 6021 models have been solid so far
PX5 models are new and too early to comment on
I sell Joying unit myself too and offer USA warranty on my units , so if you are in USA, contact me if you need anything.
Related
I am hearing a low level constant static noise with all audio through the handset earpiece. This happens on all calls, and only on the handset. Switching the call audio to a wired headset, Bluetooth headset, or the speaker phone makes the noise go away.
I have experienced this on my first MXPE, and now on its replacement. One the second go around, I did learn something more.
On the second phone I tried a call before I setup anything and it was close to fine. I say close because it was not without background noise, it was just very slight. Acceptable.
Then I finished the setup. I tried another call, and still OK. Then came the upgrade to Marshmallow. Now under Marshmallow, the noise is right back to where it was with the original phone, also on Marshmallow.
Bottom line, it is a software problem, not a hardware problem. And the software problem is only present in Marshmallow.
Sent from my XT1575 using Tapatalk
Same issue here ! immediately after MM OTA update on my XT1575 (stock vanilla) people start complaining they cannot hear me well !
After sorting most of MM issues this is a major pain in the a**
Let Moto know about this as it makes the phone crippled.
How come there aren't any more complaints about this serious issue !
This is 100% MM related - People complain they can barely hear me on the other end of the line - I sound muffled, stuttered and basically bad to the point they cannot continue the conversation and demand I call them from a land line !
Forget all MM bugs, problems, etc (need I mention the Equalizer went AWOL) now this Smartphone which I highly praised and loved became a ...smart something - with no phone feature.
Help me let Moto support be aware of this issue.
Thanks
Got the following advise from Motorola support on chat - it seems to help - please tell me if it work for you:
please go to settings > apps > all > Audio Effects app - Tap Force Stop - Clear Cache and Clear Data.
Also under settings > apps > all > go to Phone app - Tap Force Stop - Clear Cache and Clear Data.
Now please turn off the phone and when you turn it back on try making a call.
alon3232 said:
Got the following advise from Motorola support on chat - it seems to help - please tell me if it work for you:
please go to settings > apps > all > Audio Effects app - Tap Force Stop - Clear Cache and Clear Data.
Also under settings > apps > all > go to Phone app - Tap Force Stop - Clear Cache and Clear Data.
Now please turn off the phone and when you turn it back on try making a call.
Click to expand...
Click to collapse
Did all that on a call to Motorola after the first replacement phone failed to address my issue. No surprise, it made no difference.
That was followed by a factory reset and a test prior to connecting to my Google account and downloading any apps. Also, made no difference.
Now I'm waiting for my second replacement.
Sent from my XT1575 using Tapatalk
I have a thread on the Motorola forums for this issue.
My second replacement arrived yesterday. It solved the background noise issue! Unfortunately it came with loose buttons which actually rattled when shook or when the phone vibrated. Back to Amazon it goes.
Unfortunately, now Amazon wants to pull the plug on the purchase and take it all back. I'm not ready to give up though. Besides really liking the phone, I've also invested in a screen protector and car mount. I'll have to talk to Amazon today and see what we can do.
Sent from my XT1575 using Tapatalk
It's all boxed up and ready for UPS. I'm really unhappy that I could not get a good MXPE. As I consider other options, it's tough, especially at the $350 price point.
I'm actually giving the ZTE Axon Pro some thought, but undecided so far. And if the was a sale on the Nexus 6P that brought it down $100, it would be a contender. I'll pay a few more bucks for a Nexus. Given the right price, I may even give the MXPE anther shot, after they work through this stock of bad phones.
Sent from my SAMSUNG-SGH-I747 using Tapatalk
Don't get the axon. If you can't get the. 6p I'd go with Nexus 6 some places U can get it under 3 I think
Sent from my XT1575 using Tapatalk
Solved
Hi guys ive got the solution to this problem, my mic used to not work at all on handset calls and wud work on speakerphone. After diagnosing for 24 hrs I was able to understand the problem, all you need to do is replace top mics with bottom mics in music_path.html file If someone is not able to do it lemme know on twitter ill email u my edited file, just replace yours with mine. N nw the mic works like a charm. I am not a regular xda user, so won't be able to check back frequently, my twitter id is @smartphoniac
Have seen ppl replacing motherboards and phones in service center, also some use it on Bluetooth or handsfree, trust me its nt needed just do what i wrote above and issue is solved, if u r a noobie tweet me ill email u my file so that u will have to do jst the copy pasting and this painful issue will be gone forever.
Edit: This will also solve the problem if caller gets his own voice as echo. After this editing even that issue will be solved
Hi guys,
I've just bought a Moto X Style and I'm having the same problem as the original poster - constant background noise (kinda buzzing/hissing) during phone calls, coming through the upper speaker:
jswclw said:
I am hearing a low level constant static noise with all audio through the handset earpiece. This happens on all calls, and only on the handset. Switching the call audio to a wired headset, Bluetooth headset, or the speaker phone makes the noise go away.
I have experienced this on my first MXPE, and now on its replacement. One the second go around, I did learn something more.
On the second phone I tried a call before I setup anything and it was close to fine. I say close because it was not without background noise, it was just very slight. Acceptable.
Then I finished the setup. I tried another call, and still OK. Then came the upgrade to Marshmallow. Now under Marshmallow, the noise is right back to where it was with the original phone, also on Marshmallow.
Bottom line, it is a software problem, not a hardware problem. And the software problem is only present in Marshmallow.
Click to expand...
Click to collapse
So far I've tried booting into safe mode, wipe data/factory reset, different carrier/SIM card - no difference.
I'm running Android 6.0.1 and I upgraded right after I bought the phone, so cannot tell if the problem existed on Android 5.
However - and this is my question - since you claim that it's a software thing and Marshmallow-related, is there anyone who tried flashing a Nougat ROM and has it helped? I don't know if I should try and get a replacement phone (especially that some people had the same issue on 2-3 consecutive phones) or just wait for the Nougat update, assuming that it helps.
Thanks for advice!
Hi, it's me again - just wanted to tell you that I've flashed the 7.1.1. AICP ROM and the background noise is still there while calling Is it really a software issue? So many people say it appeared after MM upgrade and there were no problems on Lollipop, but maybe my speaker/mic is simply broken? Is there any ROM you can flash to get rid of this issue? All help is really appreciated! :good:
Project closed due to troll
.
Troubleshooting
project closed
dear thank you for your thread i've following you in 2gfusions thread and i have followed you here , i have the same unit you have and i'm missing the heated /cooled seates buttons.
i'm waiting your update .
keep the good work.
best regards.
---------- Post added at 03:41 PM ---------- Previous post was at 03:39 PM ----------
also i'm looking to the android 6 update if possible to apply on my device.
thanks
Subscribed
Totally subscribed and am very excited you have the know how and desire to figure this all out. I wish I knew and understood more about it. If I can help in any other capacity please hit me up. Happy to go ahead and get one and be a Guinea Pig, or throw money at you, or make ya a sammich, or whatever! I appreciate what you are doing man.
Thanks,
Chad
*edit - I should mention that I followed you here from 2gfusions.net
cecoen said:
Totally subscribed and am very excited you have the know how and desire to figure this all out. I wish I knew and understood more about it. If I can help in any other capacity please hit me up. Happy to go ahead and get one and be a Guinea Pig, or throw money at you, or make ya a sammich, or whatever! I appreciate what you are doing man.
Thanks,
Chad
*edit - I should mention that I followed you here from 2gfusions.net
Click to expand...
Click to collapse
Donations accepted http://paypal.me/kthejoker20
Do you have the problem I have where music sounds bad coming from most apps for music accept for CD and radio?
I posted in a separate thread how there is some weird filter applied to music where it severely messes with volume during listening to music... but it doesn't always apply to all apps playing music for some reason.\
Bad: soundclound,stock music player, all music players I have tried from play store, music streamed via Bluetooth through my phone
good: cd, radio, Netflix.
do you have any insight on that?
It's not a filter.
There could be a couple of issues.
First, our cars have a digital audio processor.
Do you have the radio hooked up through the factory speaker wires? If so this DAP is module wired in that you can't get to. I had to run new speaker wire around it.
You could try disabling the active noise cancelling mic.
Otherwise, if you have that taken care of, the problem is with the software audio routing.
Did you install kingroot? If so,its a known issue to cause audio problems, it interferes with the stock permissions and cause the radio to go into mono and a bunch of other crazy stuff.
But I would put my money in the first issue.
do not install kingroot you will break the system.
You can't uninstall it either as the changes it makes will permeantly break sound quality
I just picked up this unit for my 2014 ford focus.
have you figured out the password for the developer options? I've tried a bunch to no avail.
also is there a way to get to the factory settings? it doesn't appear in the settings menu.
thanks for all the help!
darkside212 said:
I just picked up this unit for my 2014 ford focus.
have you figured out the password for the developer options? I've tried a bunch to no avail.
also is there a way to get to the factory settings? it doesn't appear in the settings menu.
thanks for all the help!
Click to expand...
Click to collapse
3368 Was the password for me
---------- Post added at 01:08 PM ---------- Previous post was at 12:48 PM ----------
darkside212 said:
I just picked up this unit for my 2014 ford focus.
have you figured out the password for the developer options? I've tried a bunch to no avail.
also is there a way to get to the factory settings? it doesn't appear in the settings menu.
thanks for all the help!
Click to expand...
Click to collapse
kthejoker20 said:
It's not a filter.
There could be a couple of issues.
First, our cars have a digital audio processor.
Do you have the radio hooked up through the factory speaker wires? If so this DAP is module wired in that you can't get to. I had to run new speaker wire around it.
You could try disabling the active noise cancelling mic.
Otherwise, if you have that taken care of, the problem is with the software audio routing.
Did you install kingroot? If so,its a known issue to cause audio problems, it interferes with the stock permissions and cause the radio to go into mono and a bunch of other crazy stuff.
But I would put my money in the first issue.
do not install kingroot you will break the system.
You can't uninstall it either as the changes it makes will permeantly break sound quality
Click to expand...
Click to collapse
I don't believe we have the same car? Mine is a 2010 Toyota venza. It doesn't make sense to me that a DAP that's not part of the android radio would only affect sounds from some apps and not others?
I have not installed kingroot.
My audio problems isn't like what you describe, it's like if it messes with volume whenever a new louder sound starts playing.
not working:
7890,3368,5802,1688
This radio is ONLY for Ford fusion. There are many varients if this radio. It's not the same, even though it may say so. Sorry we can't help.
I was able to install car launcher, from there I was able access more apps. I was able to bypass the "locked down" settings, and verify it is a quad core a9 w/1g ram. The item was sold as 2g ram so it will be returned.....
It's easy to bypass, install Nova launcher and set a default.
Then open as possible drawer, select dev tool, then dev setting.
That will bring you to the dev menu.
DO not install kingroot.
Try pass 162
darkside212 said:
I was able to install car launcher, from there I was able access more apps. I was able to bypass the "locked down" settings, and verify it is a quad core a9 w/1g ram. The item was sold as 2g ram so it will be returned.....
Click to expand...
Click to collapse
This is a totally different radio then what is being discussed here.
Ours us is a a7
yeah it look identical (other than the housing) as far as the skin etc.
I was hoping it was the same, but apparently these units can be very different.
I'm not sure if it helps, but there was an app called "hidden system" that allowed me to see more about the unit.
darkside212 said:
yeah it look identical (other than the housing) as far as the skin etc.
I was hoping it was the same, but apparently these units can be very different.
I'm not sure if it helps, but there was an app called "hidden system" that allowed me to see more about the unit.
Click to expand...
Click to collapse
We don't have that one in our system. I've thoroughly picked through the system already.
I guess what exactly are you looking to do? You have to be very careful with these, they are not normal flash able Androids, they rely on the mcu to operate.
So simply getting root could break a lot of things and cause audio problems and stuff
I'm good.
they had the system settings really locked down but I was able to get around them via car launcher. I just posted in case anyone else need that info.
they didn't have the "factory settings" available which was annoying as I wanted to turn off some of the settings.
thanks for the help!
AAAAAAA7 said:
3368 Was the password for me
---------- Post added at 01:08 PM ---------- Previous post was at 12:48 PM ----------
I don't believe we have the same car? Mine is a 2010 Toyota venza. It doesn't make sense to me that a DAP that's not part of the android radio would only affect sounds from some apps and not others?
I have not installed kingroot.
My audio problems isn't like what you describe, it's like if it messes with volume whenever a new louder sound starts playing.
Click to expand...
Click to collapse
Most common cause for bad sound is the radio is set to "High impedance mode". You need to access your system menu. Usually, by clicking the yellow gear, then select system. Then hold your finger on the information box on the right and a secret menu will appear. Enter code 7890 and then hit ok. Go to the setting that has 2 boxes, one of them should list your vehicle. If you see whatever vehicle is listed there with an "H" next to it, that is definitely your problem. Select it, and change it to "L" or if your vehicle is not listed, select the nearest similar vehicle with an "L".
Just made some developments, check the original posts.
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!
Stock ROM from Seicane ~4 weeks ago. The unit pairs with the cell phone for ~2 seconds and then drops the connection. If I'm quick, I can actually place a call that goes through the handset and places a call that uses the handset speaker.
I tested on a Leeco Pro3 and an Alcatel phone. This is a show stopper but the unit is installed and it was shipped direct from China so replacing it is a big deal. HELP!
Has anyone else seen this?
i have this unit, I have not had any issues with Bluetooth. I did a 6 hour road trip, listening to Bluetooth the whole time. I was connected to a Moto Z2 Force.
What is your About Device screen showing? maybe you need an update, i just updated my MCU to the latest KSP
https://forum.xda-developers.com/an...-development/mtcd-ksp-firmware-t3607398/page4
CadillacMike said:
i have this unit, I have not had any issues with Bluetooth. I did a 6 hour road trip, listening to Bluetooth the whole time. I was connected to a Moto Z2 Force.
What is your About Device screen showing? maybe you need an update, i just updated my MCU to the latest KSP
https://forum.xda-developers.com/an...-development/mtcd-ksp-firmware-t3607398/page4
Click to expand...
Click to collapse
Thanks CadillacMike. I checked and I have the same MCU as you do. So I did a factory reset (on Seicane's advice, sort of, it's little hard to guess what they were trying to say). It didn't fix anything but blew away IGO and maybe a few other things.
Then I tried a 3rd phone; my son's Moto G4 paired quickly and perfectly.
Next up:
Recover the missing pieces from the factory reset.
Update/change/whatever to get my phone to behave.
EDIT: Got it working. Burned my phone with a custom ROM: ResurrectionRemix. No idea why this worked but the hint came from some else with a similar andoid head and a LeeCo phone. Likely hopeless for the Alcatel phone but that is unimportant for me.
As small thank, maybe you would enjoy a Jeep icon for your IGO map? Put the attached files in \igo\content\car Then in settings -> map options change the 3d car to one of the selected
hey thanks, but i dont use iGo, i just use Google Maps.
I also got Seicane headlights:
https://youtu.be/N4W8oE0twsM
and here are a couple of videos about the same head unit:
https://youtu.be/5cavKcYauSk
https://youtu.be/MWVsNWZjeCQ
I updated my software and it looks cool
Image not found...
CadillacMike said:
I updated my software and it looks cool
Click to expand...
Click to collapse
What did you update to? The pictures aren't loading for me.
I like unit so much that I might leave it alone for awhile and have something to play with later when a 10" screen in the dash seems like an everyday thing.
It was the October 26th update for PX3 that was in the Dasaita thread
Pictures aren't loading for me either
CadillacMike said:
It was the October 26th update for PX3 that was in the Dasaita thread
Click to expand...
Click to collapse
I can see the pictures now. Looks great, thanks for the pictures. Did you have to reinstall all the apps and settings? Now that everything is working on mine I am trying to resist rehashing the whole thing.
Well, trying to resist anyway.
tlyonstlyons said:
I can see the pictures now. Looks great, thanks for the pictures. Did you have to reinstall all the apps and settings? Now that everything is working on mine I am trying to resist rehashing the whole thing.
Well, trying to resist anyway.
Click to expand...
Click to collapse
No, there a box you can check to wipe everything, but I didnt check it.
It kept all my stuff intact
tlyonstlyons said:
Stock ROM from Seicane ~4 weeks ago. The unit pairs with the cell phone for ~2 seconds and then drops the connection. If I'm quick, I can actually place a call that goes through the handset and places a call that uses the handset speaker.
I tested on a Leeco Pro3 and an Alcatel phone. This is a show stopper but the unit is installed and it was shipped direct from China so replacing it is a big deal. HELP!
Has anyone else seen this?
Click to expand...
Click to collapse
Whats happened on the mazdas with all chinese units
People were having issues having their cell phones even connect. It was duento the issue of having the device paired with the old radio.. which i had with my so480.
I had to reinstall the old radio, unpair all devies from it then reinstall the new radio and pair up and has worked fine ever since. Now as to why i dont know as the aftermarket radio used its own bluetooth connections as the canbus only let the radio sync up with the steering wheel functions. Hopefully you get it fixed.
Bought this brand new sealed and opened it up and updated to current.
Problem,
Microphone works great on the phone but won’t work anywhere else.
Ok google won’t voice match to open, voice memos, gboard, video call apps, etc.
Anyone else had this issue and fixed it?
First thing I'd do is check the app's permissions that they are allowed to use the mic
I did that
swedyk said:
I did that
Click to expand...
Click to collapse
did it work before you updated it?
Does it work with headset etc?
I'd try going to reset all apps, as a first try.
Last resort, reflash.
IronRoo said:
did it work before you updated it?
Does it work with headset etc?
I'd try going to reset all apps, as a first try.
Last resort, reflash.
Click to expand...
Click to collapse
When you plug in a headset with a mic it works fine.
Don’t know about working first because updates were right away as I knew the phone at start was not a good experience until all the updates made it great.
swedyk said:
Bought this brand new sealed and opened it up and updated to current.
Problem,
Microphone works great on the phone but won’t work anywhere else.
Ok google won’t voice match to open, voice memos, gboard, video call apps, etc.
Anyone else had this issue and fixed it?
Click to expand...
Click to collapse
I think you/we are suffering from an software issue. The PH-1 and other devices like the OP6 have the problem that thirdparty apps are using the wrong microphone, even the camera app. For me this is causing very low volume in recorded videos and anreliable "OK google" trickering the assistant. I don't use whatsapp or snapchat, so can't say anything about it.
https://www.androidpolice.com/2019/...-mic-in-some-apps-like-snapchat-and-whatsapp/
Hopefully it will be fixed later once. Fingers crossed :silly:
swedyk said:
When you plug in a headset with a mic it works fine.
Don’t know about working first because updates were right away as I knew the phone at start was not a good experience until all the updates made it great.
Click to expand...
Click to collapse
LOL, yes suppose most of us would immediately update phone is s oon as we got it also
yes, I'd think it's software issue, I've also heard of similar problems on other phones & oK goggle also causing mic issue, that's very I suggested using the reset all app option. Maybe also try boot into safe mode to see if it's a 3rd party app causing this.