Develop Bugs

Bluetooth Media Remote

I am trying to use a bluetooth Media Remote. When I search for bluetooth devices the device will appear and when I select it asks if I want to connect. However when I click yes it does not actually connect. I have tried to run XMTC and changed the name from ODB to the name of the device. This changes the icon of the device on the unit however it still does not connect. This appears to be OS\driver issue not a hardware issue since the device is being found.
I have tried two different bluetooth remotes with the same results(from amazon)
Satechi® Bluetooth Button Series (Media Button)
iSimple Portable Wireless Remote Control
I can however connect these to my phone and change the volume on the phone while I am streaming music to the head unit. And this is nice, but I would really like to be able to control the head units volume instead.
Does someone have a custom ROM that could fix my issue?

Edit - was able to resolve my issue. Used xposed framework and bt module to remove the name limitation.

Zeneffect said:
Edit - was able to resolve my issue. Used xposed framework and bt module to remove the name limitation.
Click to expand...
Click to collapse
I am glad you were able to resolve your issue. Hoping someone smarter than me can fix mine
Anyone have any ideas how to get other bluetooth devices to work with this system? I expect someone that can build a custom ROM could fix this.

Zeneffect said:
Edit - was able to resolve my issue. Used xposed framework and bt module to remove the name limitation.
Click to expand...
Click to collapse
Cool. What BT module did you use?

Zeneffect said:
Edit - was able to resolve my issue. Used xposed framework and bt module to remove the name limitation.
Click to expand...
Click to collapse
Did anyone ever find out which xposed module this is?

Hey there, I've got the Satechi® Bluetooth Button Series (Media Button) thing too, and surprise surprise, it won't talk to my Pumpkin HU (rk3066, android 4.4.1, mcu KLD2).
I've rooted the stock using the #hct#root# trick and installed SuperSU. I would love to get the button working!
I've got my head unit installed in my right-hand drive car (am in UK) - and where it's mounted, it is just out of reach unless I lean forward - so I can't really use it without looking, apart from using the tiny buttons down the side.
Happy to try the xposed framework but like OP I don't know which modules to use to get a USB BT dongle working. Any help greatly appreciated!

I definitely may be wrong but I assumed he was referring to the Xposedmtc module (http://forum.xda-developers.com/showpost.php?p=54334741) in the OBD settings where you specify the string. Though I assumed this only worked for OBD devices. I tried using it to pair an iRadar device with mine but was unsuccessful.

Oh, poop. Thanks all the same. Will keep an eye on this thread and report back if I ever get anywhere! Could it be that these HU's are only Bluetooth 2.0 compatible? Every device I've seen seems to be 3.0...

Hmmm. I'm thinking of getting a cheap wired USB numberpad (they're like £3) and using it with a keyboard mapper like this one:
https://play.google.com/store/apps/details?id=com.apedroid.hwkeyboardhelper
and this list:
http://developer.android.com/reference/android/view/KeyEvent.html
Oh and this is as much a note to self as anything!
http://www.barbatricks.com/en/android-en/remap-ab-shutter-3-selfie-remote/
It's going to be ugly...but that's never stopped me

Bumping as I have interest too.

You guys are making this way too difficult. Check this out. It works great on my joying.
http://m.ebay.com/itm/Car-Steering-...ayer-Bluetooth-Phone-/151832759268?nav=SEARCH

Anyone has found which xposed bt module the op was talking about ? I have already bought the bluetooth remote but I can't connect to it. (Works on my phone)

Also bought a Satechi® Bluetooth Button Series (Media Button) for use with my Joying unit but alas no success, so bumping this thread to see if there is any progression.
@dcmtnbkr are you able to show a quick video of your unit in action?

For the people that have gotten their bluetooth "remotes" to work, can you simultaneously also pair your phone and perform calls?

dcmtnbkr said:
You guys are making this way too difficult. Check this out. It works great on my joying.
http://m.ebay.com/itm/Car-Steering-...ayer-Bluetooth-Phone-/151832759268?nav=SEARCH
Click to expand...
Click to collapse
I bought much the same device but it won't directly connect to my HU. The HU will connect to my phone and my phone connect to media controller so I know all the devices work. Do I need a Droid program to allow access directly to the HU which is playing music from a USB flash drive.
Main problem is HU has panel controls for volume but cannot skip a song with going into player program. I use the display for my engine management gauges and don't want to keep getting out of program just to skip a song I don't like.
jim

I'm familiar with the one you're talking about, it's not the same thing.
I found another one that would work and is less intrusive.
https://rover.ebay.com/rover/0/0/0?mpre=https://www.ebay.com/ulk/itm/222631804601

[MOD] Codec-level Audio Mods for Pixel Devices: BiQuads, Stereo Capture and Playback

Attached is an installer for up to three hardware-level audio mods that I've created over the last few years.
Important: This installer is not flashable via TWRP, but needs to be installed using an adb root shell as outlined below.
The three mods that can be installed in any combination are
The dual speaker playback mod as originally presented in this thread. When installing this mod, an app will also be installed that offers the following functionality:
when the screen is on, the main loudspeaker level is reduced significantly to bring down its volume to the one that is attainable with the earpiece speaker. The idea is that when the screen is on you may want to use it to watch a movie or play a game where the stereo effect may enhance the listening experience. This is a "personal" use-case where the lower overall volume may not be a huge problem
when the screen is off the main loudspeaker level is again raised to its maximum capability to not miss notifications and alarms, etc
There is an option offered to force maximum gain also in case the screen is on, for instance when sharing a YouTube video with friends or when using the speakers in the car in navigation mode
The above functionality can be controlled with a new permanent notification with three buttons: "stereo", "mono", and "mode", which can be "adaptive" or "stock". If you install the dual speaker mod, an accompanying app/service will be installed that automatically shows the above referenced permanent notification. This "app" has no UI other than the permanent notification. It is really a service that automatically starts upon boot. Keep in mind that you will need to unlock the phone twice after the boot process has been completed for the service to become active. The reason for this is that Android only makes most services available only after the initial unlock as a security feature. After that the screen needs to turn off at least once for the speaker control service to detect the screen state. Also, this service requires root privileges to function properly.
Stereo camcorder audio recording mod. Any app that uses the CAMCORDER device is now capable of recording stereo sound. Examples are Google's stock camcorder or "Easy Voice Recorder Pro".
Headphone biquad filtering for frequency response compensation as first made available here. This option will also install the accompanying biQuads app and relevant files. REQUIREMENTS: system-less root and @flar2 's excellent ElementalX kernel starting with version 1.02, with codec power gating option disabled in the installer.
There are actually two installer provided:
chdloc_hardware_audio_mods_pixel__ull.tar.gz : retains ultra-low latency (ULL) audio playback, but only supports the main loudspeaker to be active in cases where ULL is being asked for
chdloc_hardware_audio_mods_pixel__no_ull_*.tar.gz: allows both loudspeakers to be active even when ULL is being asked for by an app. However, under the hood ULL is converted to low-latency playback only.
I was unable to get both loudspeakers to play simultaneously in ULL mode on a stock system/kernel. ULL seems to invoke very different data handling code inside the kernel (from IRQ-based to non-IRQ-based). It appears that two backends (SLIMBUS_0_RX and QUAT_MI2S_RX) cannot be simultaneously active in non-IRQ mode. It is possible that this "problem" can be fixed with a custom kernel, but I really don't want to go that route. That's why I opted to re-route the ULL plumbing to make use of the low-latency path instead. According to the AOSP source code (platform.c), ULL promises 7 ms of latency while low-latency promises 13 ms. Whether that delta makes a difference in day-to-day use, particularly in VR mode, I don't know (yet).
To install, download the attached archive to your PC and push it to /data/local/tmp on your Pixel
Code:
adb shell rm -rf /data/local/tmp/chdloc* && adb push chdloc_hardware_audio_mods_pixel*.tar.gz /data/local/tmp/
Then enter an adb shell and copy the following string of commands into a root shell:
Code:
cd /data/local/tmp && gzip -d chdloc_hardware_audio_mods_pixel__*.tar.gz && tar -xf chdloc_hardware_audio_mods_pixel*.tar && gzip chdloc_hardware_audio_mods_pixel*.tar && chmod -R a+rw chdloc* && cd chdloc_hardware_audio_mods_pixel && chmod 744 install_chdloc_mods.sh
to install type
Code:
./install_chdloc_mods.sh
and select your install option, which also includes "revert to stock".
The following hidden text shows the original OP for reference:
It has been a tradition in the Android community to enable the earpiece speaker for multimedia playback to somewhat mitigate the drawback of having only one bottom-firing loudspeaker. I have been running a "true stereo" mod on my Nexus 5 for almost two years with great success.
The Pixel is a little bit different. Like some other phones with the SD820/821 it uses a separate speaker DAC/amp, which makes this mod quite a bit more tricky. Let me get this out of the way: the bottom speaker gets *much* louder than, for instance, the one on the Nexus 5. You cannot expect the earpiece to get this loud to create any form of "surround" effect. The only way to get there is to lower the volume of the main loudspeaker. This is what I'm describing below. This work is in no way, shape or form complete. For now, I'm giving here an outline on what needs to be done to enable dual-loudspeaker playback. I encourage others to try it out and chime in. So here it goes:
First of all you need to be rooted. Then modify the following /system/etc/mixer_paths.xml {...}.
The installation process is now described here
Now you need to save the file and reboot your phone. When you play audio you will notice that the earpiece is barely audible against the main speaker. The only way around this is to lower the speaker gain. This can be done by writing to a register in the amplifier which sits on the i2c bus:
Code:
echo 0xZZ0f > /sys/kernel/debug/tfa98xx-34/regs/06-AUDIO_CTR
where ZZ is the gain. By default, the speaker is set to 0 dB of gain with ZZ=00, i.e.
Code:
echo 0x000f > /sys/kernel/debug/tfa98xx-34/regs/06-AUDIO_CTR
Now each "tick" in the upper eight bits in this 16-bit number lowers the gain by 0.5 dB. The last two gain settings are FE which is -127 dB and FF which mutes the speaker.
In my short tests I have found the a gain of -16 dB for the main speaker, i.e.
Code:
echo 0x210f > /sys/kernel/debug/tfa98xx-34/regs/06-AUDIO_CTR
and a gain of +6 dB for the earpiece (see above) gives fairly balanced left-right volume. The speaker volume could be adjusted via an app depending on the use-case or upon boot via a script in /su/su.d
Note that the mod at this stage is dual-mono only.
Going forward I'll try to enable true stereo or something like the HTC10 tweeter-woofer arrangement.
I understand that all of this appears fairly complicated, so work needs to go into making this actually useful for others with flashable zip and control app. Any volunteers...?
Updates
November 9: first release of a speaker control app
November 7: the no-sound on the earpiece speaker during an incoming call has been fixed. For details, refer to this post. Please test and report back
November 3: stereo support, the left channel is played by the earpiece and the right channel is played by the main speaker. Note the updated "speaker" device above. The line in red (QUAT ...) tells the mixer to send two channels to the speaker dac/amplifier. By default, the dac/amp mixes the two channels into a mono stream. If you want stereo, then issue
Code:
echo 0x8093 > /sys/kernel/debug/tfa98xx-34/regs/04-I2SREG # right channel only
at any time on the command line or add to a script in /su/su.d so it gets applied on boot. If you want to go back to left+right on the main speaker then issue
Code:
echo 0x809b > /sys/kernel/debug/tfa98xx-34/regs/04-I2SREG # mono mix
. With the above changes the earpiece always plays the left channel.
November 2: Initial revision
Known limitations
Speakerphone telephony resets the DAC/amp of the main speaker and the above modifications get wiped. Hence, it would be ideal to control this mod with Tasker or some other native app.
There currently is an issue with RX audio on the earpiece with an incoming phone call. There will be nothing coming out of the earpiece. Switching to speakerphone works fine. Outgoing calls are fine. This has to do with the above (necessary) changes to mixer_paths.xml and the timing on how audio devices are set up and torn down in specific use cases. An explanation and possible solutions are given below. fixed (?)
So here is the problem: A call comes in and the system plays the ringtone using the "speaker" device. With the changes above, the speaker device now also activates the earpiece speaker by default. When you answer the call, the audio HAL switches the audio devices by activating the relevant capture and playback devices. The playback device is different from the "speaker" device, but it involves the earpiece unless the phone is connected to a (potentially bluetooth) headset. Unfortunately, the "speaker" device gets disabled last, which means that the earpiece gets disabled. Here is the sequence of events as caught by logcat:
Phone is RINGING
17:30:04.578 adev_set_mode: mode 1
17:30:04.904 out_set_parameters: enter: usecase(1: low-latency-playback) kvpairs: routing=2
17:30:04.908 select_devices: changing use case low-latency-playback output device from(1: handset, acdb 7) to (2: speaker, acdb 15)
17:30:04.908 enable_snd_device: snd_device(2: speaker) {=> chdloc: this line enables the earpiece}
17:30:04.924 enable_audio_route: usecase(1) apply and update mixer path: low-latency-playback speaker
Phone is answered in HANDSET mode
17:30:11.020 adev_set_mode: mode 2
17:30:11.123 out_set_parameters: enter: usecase(1: low-latency-playback) kvpairs: routing=1
17:30:11.126 enable_snd_device: snd_device(19: voice-handset-tmus) {=> chdloc: this line enables the earpiece}
17:30:11.128 enable_snd_device: snd_device(55: voice-dmic-ef-tmus)
17:30:11.153 enable_audio_route: usecase(15) apply and update mixer path: voicemmode1-call
17:30:11.220 select_devices: changing use case low-latency-playback output device from(2: speaker, acdb 15) to (19: voice-handset-tmus, acdb 88)
17:30:11.220 disable_audio_route: usecase(1) reset and update mixer path: low-latency-playback speaker
17:30:11.277 disable_snd_device: snd_device(2: speaker) {=> chdloc: this line disables the earpiece}
17:30:11.304 enable_audio_route: usecase(1) apply and update mixer path: low-latency-playback
17:30:14.058 disable_audio_route: usecase(1) reset and update mixer path: low-latency-playback
I see three options to fix the issue:
Have the earpiece constantly enabled. I'm currently testing this method to see whether there are any side effects. I would be in favor of this method if it works.
Use Tasker to detect an incoming phone call and have Tasker enable the earpiece. This is actually very doable, but kludgy. I'd use this approach if the first one proves problematic.
Mess with the audio HAL to disable the speaker *before* the voice-handset-*** device is enabled. As this involves source code changes and, therefore, a modified audio HAL (/system/lib/hw/audio.primary.msm8996.so), this would be my least favorite option.

Great work mate!

YESSSSS!!!! Been waiting for this!! Excellent work!!

This mod plus viper4android is amazing! Sounds so good! Thank you!
Sent from my Pixel XL using XDA-Developers mobile app

Update: Full stereo support added to the OP. Note that for best stereo imaging, the gain for the main speaker needs to be reduced significantly. Stereo media playback is likely only useful for personal media consumption or gaming in a relatively quiet environment. This mod lends itself nicely to Tasker (or native app) integration with which stereo can be enabled on-demand.
Next, I'll look into an HTC 10 like setup where the earpiece is used as a tweeter. The idea is that the earpiece (and by extension the main speaker) gain can be kept higher because distortions that are caused by high frequency clipping are less audible than the ones that result from low-frequency clipping.
Update: There currently is a problem with this implementation in that there is, initially, no audio coming out of the earpiece when *receiving* a phone call. You can force audio to come out of the earpiece by quickly toggling to and from speakerphone mode. Outgoing phone calls are fine. Please keep this in mind when trying the mod. I'm currently investigating the exact cause.
Update 2: I think I'm understanding the problem. See the OP for an explanation and possible solutions

Edit: All working well.
So what you're saying is when answering a call, switch to loudspeaker then ear piece?

I'm a bit lost. 1. Do I need to change everything from "this" to " with" as above for the mod to work and 2. Once necessary files are replaced do I just save and let root create the XML.bak file or does the file I create go in su etc? Thanks
Sent from my Pixel XL using XDA-Developers mobile app

Juzman said:
So what you're saying is when answering a call, switch to loudspeaker then ear piece?
Click to expand...
Click to collapse
Yes, that is the current workaround. I'm currently testing additional mixer_path.xml mods that may address this issue.
treIII said:
I'm a bit lost. 1. Do I need to change everything from "this" to " with" as above for the mod to work and
Click to expand...
Click to collapse
Yes
2. Once necessary files are replaced do I just save and let root create the XML.bak file or does the file I create go in su etc? Thanks
Click to expand...
Click to collapse
Well, to stay in the spirit of system-less root, you don't want to modify /system. Instead, copy the modified mixer_paths.xml file to /su/etc
and create a file (bind mount) called 10mixer_paths in /su/su.d/
Code:
#!/su/bin/sush
mount -o bind /su/etc/mixer_paths.xml /system/etc/mixer_paths.xml
change the permissions to 700 (rwx------), and reboot.

chdloc said:
Yes, that is the current workaround. I'm currently testing additional mixer_path.xml mods that may address this issue.
Yes
Well, to stay in the spirit of system-less root, you don't want to modify /system. Instead, copy the modified mixer_paths.xml file to /su/etc
and create a file (bind mount) called 10mixer_paths in /su/su.d/
change the permissions to 700 (rwx------), and reboot.
Click to expand...
Click to collapse
Does I need to make a file bind mount inside of su/su.d/ thanks

treIII said:
Does I need to make a file bind mount inside of su/su.d/ thanks
Click to expand...
Click to collapse
Yes, you need to bind mount the 10mixer_paths file I quoted above in /su/su.d and simply copy the modified mixer_paths.xml to /su/etc

from what i read, the mod seems applicable on the OP3 as well, or is the S821 having a different hardware setup than the S820 ?

Mostafa Wael said:
from what i read, the mod seems applicable on the OP3 as well, or is the S821 having a different hardware setup than the S820 ?
Click to expand...
Click to collapse
The main codec is identical, but they may have a different speaker DAC/amp. As root run the following two shell commands
Code:
ls /sys/module | grep snd_soc
and
Code:
find /sys -name '*AUDIO_CTR*'
and post the result.

chdloc said:
The main codec is identical, but they may have a different speaker DAC/amp. As root run the following two shell commands
and
and post the result.
Click to expand...
Click to collapse
Here are my results. I guess it could not be applicable here

Are there any chances this mod becomes available as a script or zip eventually?

airmaxx23 said:
Are there any chance this mod becomes available as a script or zip eventually?
Click to expand...
Click to collapse
Yes

Update: The procedure described below is outdated. See this post for the new method.
I think I found a way to fix the silent earpiece speaker when a call comes in. It requires additional mixer_paths edits. I have attached an archive with three files:
mixer_paths.xml.stereo: copy (and rename!) to /su/etc/mixer_paths.xml; I dialed the earpiece gain back to 84 dB to get rid of distortions.
20speakerctrl: copy to /su/su.d and make executable (700, rwx------). This script is executed on boot and sets the speakers for stereo and lowers the level of the main speaker by around 18 dB.
mixer_paths.xml.stock: this is the stock mixer_paths file; if you want to go back to stock behavior, copy this file to /su/etc/mixer_paths.xml and delete /su/su.d/20speakerctrl
Please test this setup and report back. Note that you can currently only modify the main speaker gain and have it "stick" with the 'echo' command as described in the OP. To play around with the earpiece volume while media is playing you can use the following command in a root shell
Code:
tinymix "RX0 Mix Digital Volume" X
where X={0,1,...,84,85,...,124}. The default is X=84 which applies 0 dB of gain. Each "tick" up or down changes the gain by 1 dB. Add gain very carefully. At maximum volume, I would highly advise not to go beyond 90. Note that changing the earpiece volume this way does not "stick" and it defaults back to 84 as soon as you change the media stream (skip, different app, etc). You will need to run a custom kernel with sound control to be able to fully control the volume of the earpiece speaker.
There is still the issue that a speakerphone call resets the main speaker's volume to default. Over the next couple of weeks, I'll come up with a Tasker app -- which means you do not need to have Tasker installed -- which initially
re-applies the currently chosen gains after a phone call
lets you quickly toggle between the low-volume stereo setup and the high-volume stock setup
Other things this app could do is go back to stock behavior when the screen is off, so you won't miss notifications and/or alarms due to the lower overall volume of the stereo mod.

chdloc said:
There is still the issue that a speakerphone call resets the main speaker's volume to default.
Click to expand...
Click to collapse
So, after each call, we have to run the script in /su/su.d to reapply the volumes correctly? If that's the case, can always use Script Manager, and set a widget icon on home screen. After a call, tap the widget to execute the script again.

Juzman said:
So, after each call, we have to run the script in /su/su.d to reapply the volumes correctly? If that's the case, can always use Script Manager, and set a widget icon on home screen. After a call, tap the widget to execute the script again.
Click to expand...
Click to collapse
Correct. The idea, though, is to eventually have this done automatically by a Tasker app.

chdloc said:
Correct. The idea, though, is to eventually have this done automatically by a Tasker app.
Click to expand...
Click to collapse
Sweet as. Question two:
mixer_paths.xml.stock: this is the stock mixer_paths file; if you want to go back to stock behavior, copy this file to /su/etc/mixer_paths.xml and delete /su/su.d/20speakerctrl
Could we not just delete /su/etc/mixer_paths.xml instead? Since we will still have original in /etc/

Juzman said:
Sweet as. Question two:
mixer_paths.xml.stock: this is the stock mixer_paths file; if you want to go back to stock behavior, copy this file to /su/etc/mixer_paths.xml and delete /su/su.d/20speakerctrl
Could we not just delete /su/etc/mixer_paths.xml instead? Since we will still have original in /etc/
Click to expand...
Click to collapse
Sure, but then you probably also may want to delete the bind mount in /su/su.d as I'm not sure what would happen if the file the mount points to has been deleted.
In addition, there are a few more mods I'm going to release soon that some folks may want to play with (stereo camcorder recording and hardware audio filtering), so keeping that file around may come in handy.

Bluetooth issue

I have a MTCC-KLD6-V2.97 Android 5.1.1 800*480, with a december stock rom.
Since I've installed it, I always had a problem with the bluetooth: at the first start, if I do a search does not find any device and from my smartphone I can not find the unit.
After a completely shutdown (with car off) and restart, the bluetooth seem to work properly and i can connect my phone; the same thing happens after I went to the factory settings or when it boot with Android logo instead of the configured startup logo (It appears to be a fresh start after a unit reset, or similar): I have to turn off the car and wait for the complete switch-off time, otherwise I cannot have a Bluetooth connection with my phone.
The problem does't seem to be related to the Rom or MCU, I made several attempts, and the problem still persists.
I don't know if it can be linked, but when I tried a Malaysk 5.1.1 rom, I had to disable the MCT Service module, because otherwise I couldn't always connect my phone.
Someone has encountered a similar problem? How did solve it?

Have you checked that you have the correct BT module enable in factory settings ?

I think yes.
Let me explain: when I received the unit, in the factory setting was set on IVT_BT type.
I always had this problem, so one of the attempts that I made was to change the type of form, and I have tried all the available ones:
WQ_BC5
WQ_BC6
Parrot_FC6000T
IVT_BT
SD_BC5
WQ_BC6B
WQ_BC8
SD_BC8
In all cases, after the boot, in the Bluetooth settings does not appear the name of the unit and the pairing code.
If I try to manually configure name and passcode, if I go out on the settings it lose them. If I try to do a search, no device found.
The only module that seems to work is IVT_BT, but occasionally causes me the problem I described above.
The unit has always had 5.1.1 rom, what I thought of trying to do is use a 4.4.4 rom (maybe the new Malaysk), it could be a solution?

AFAIK, apart from the Parrot modules that have just started to appear, MTCB and C units always come with BC6 BT module. KK shouldnt make any difference really.
The only way to tell from certain is to remove the top, does it have a DVD/CD drive ?

Yes, I'll try to disassemble the unit and open the DVD to check the physical BT module.
But I don't understand, if I configuring in the factory settings the BC6 module will don't see the unit name and passcode and I cannot set it up in the bluetooth configuration... Also the MCU version don't make a difference?

daverock said:
Yes, I'll try to disassemble the unit and open the DVD to check the physical BT module.
But I don't understand, if I configuring in the factory settings the BC6 module will don't see the unit name and passcode and I cannot set it up in the bluetooth configuration... Also the MCU version don't make a difference?
Click to expand...
Click to collapse
Thats why I said have a look at the BT module, to establish exactly what one it is.
You could try MCU MTCC KLD9 v2.98 and see if that works better, its newer.

This is the BT module; unfortunately I cannot see good the face with the processor, I should completely disassemble the radio and today I had no time...
However, it seems that there is nothing written over that show the kind of bluetooth ...
I think I'll have to disassemble everything, find someone that sell me just the module and change it

daverock said:
This is the BT module; unfortunately I cannot see good the face with the processor, I should completely disassemble the radio and today I had no time...
However, it seems that there is nothing written over that show the kind of bluetooth ...
I think I'll have to disassemble everything, find someone that sell me just the module and change it
Click to expand...
Click to collapse
Its quite easy to remove the DVD drive and/or the side of the unit, there should be writing on the bit of the BT module that faces the side of the unit.

Bluetooth Issues
I have a question with the BT on my unit. I have the external Mic connected and people complain that they can't hear me and they always hang up me. Music works fine but on phone call I have to switch my phone to Speaker. Would disconnecting the external Mic would improve the call quality. Do you suggest I get another external microphone? If you do can you please link me to a good one. Please see the picture for my unit's information.

llaugerm said:
I have a question with the BT on my unit. I have the external Mic connected and people complain that they can't hear me and they always hang up me. Music works fine but on phone call I have to switch my phone to Speaker. Would disconnecting the external Mic would improve the call quality. Do you suggest I get another external microphone? If you do can you please link me to a good one. Please see the picture for my unit's information.
Click to expand...
Click to collapse
Theres a specific thread about how to mod the mic in the hardware section.

daverock said:
I think yes.
Let me explain: when I received the unit, in the factory setting was set on IVT_BT type.
I always had this problem, so one of the attempts that I made was to change the type of form, and I have tried all the available ones:
WQ_BC5
WQ_BC6
Parrot_FC6000T
IVT_BT
SD_BC5
WQ_BC6B
WQ_BC8
SD_BC8
In all cases, after the boot, in the Bluetooth settings does not appear the name of the unit and the pairing code.
If I try to manually configure name and passcode, if I go out on the settings it lose them. If I try to do a search, no device found.
The only module that seems to work is IVT_BT, but occasionally causes me the problem I described above.
The unit has always had 5.1.1 rom, what I thought of trying to do is use a 4.4.4 rom (maybe the new Malaysk), it could be a solution?
Click to expand...
Click to collapse
I have the exact same issue right now. Did you ever resolve it?

manofconviction said:
I have the exact same issue right now. Did you ever resolve it?
Click to expand...
Click to collapse
No, i'm sorry. The touchscreen of my old unit it broken, so i've changed it with a most modern unit, with 2 GB ram and Nougat os.

MTCE - Waze mutes all audio (radio, bluetooth music, etc... stop playing)

Hello,
I don't remember making any changes to this, but for some reason now anytime I open up Waze (my default Nav app on my MTCE), any audio playing becomes muted and stays muted. I used to have continuous audio when running Waze, except for if Waze had a direction or notification to give and then it would properly temporarily mute the audio. But now I get no music while having Waze on screen. If I go back to the radio app let's say, audio continues as usual.
If I run any other app (say Google Maps), I still get audio as per usual.
Anyone have any ideas?
Thanks

Here also same pb. MTCD px3 android 5.1 with Hal9k rom on HU. I can't find any setting for sound on app or in OS.

Yo ozzyboy,
Did this problem occur for you recently? It happened to me within the past week or so. Again, I don't think I have made any settings changes in that time period.
ozzyboy said:
Here also same pb. MTCD px3 android 5.1 with Hal9k rom on HU. I can't find any setting for sound on app or in OS.
Click to expand...
Click to collapse

ozzyboy said:
Here also same pb. MTCD px3 android 5.1 with Hal9k rom on HU. I can't find any setting for sound on app or in OS.
Click to expand...
Click to collapse
I think I found the fix in case anyone else is wondering.
Go to Settings>Car>Navigation and look for something along the lines of Navigation sound mode. There is a toggle for me that turns some kind of navigation sound monitoring on, and then that enables several options below. One of the options is like "switch" or something to that extent, and then you can play around with how much the radio lowers it's volume while the navigation is talking. I guess mine was somehow totally disabled and that's how I lost sound, but I have it back now.
Hope this helps.

are the settings in the head unit. I have looked for ages and can't find it

maids said:
are the settings in the head unit. I have looked for ages and can't find it
Click to expand...
Click to collapse
No in boot

marchnz said:
No in boot
Click to expand...
Click to collapse
sorry boot?

maids said:
sorry boot?
Click to expand...
Click to collapse
where in boot could you be a bit more descriptive please

Bought first android head unit

Hi all,
Recently bought my first android head unit, from Erisin.
Everything works great, just had a few newbie questions.
Its running Android 10 and I am using Car Launcher Pro.
I have my S20 Ultra routine set up to automatically start my phone wireless hotspot so the head unit has Internet connectivity.
1. How do I create speed dial buttons? Opening the phone app and searching through the phone book while driving is distracting.
2. Although I am yet to hook up my reverse camera, I noticed that everytime I put it in reverse, the music stops. How do I keep music playing (I'm using spotify)?
3. What is speedplay? Each time I open Torque it automatically opens this SpeedPlay and switches focus. Its a PITA. Can I safely uninstall it?

I just got my first Android HU also - I went to Nova7 launcher for more control over the aesthetics and layout, and really like the change so far.
On mine, there is a setting in the Android settings menu for the music pause during reverse camera input.
Is ZLINK included in your list of pre-installed applications? It's what I'm using for wireless CarPlay (does AA also) - and allows me to use Siri to initiate calls handsfree from the address book. Mine pairs with the phone automatically upon startup.