Hi,
So after having a bit of a read of the MTCD forums I have gathered that both bluetooth handsfree and bluetooth music playback are handled by the MCU but use Android companion apps to control what the MCU does. For OBD I am a little unsure but some are suggesting that the MCU looks for the "OBD" device name and forwards data to the MCU?
So what I have gathered from this is that because the MCU handles bluetooth, so this limits what you can do with bluetooth on these android HUs (so no bluetooth tethering ect...).
Or is it that android has full access to the bluetooth module but the developers of these units haven't implemented many profiles in their bluetooth stack? In this case, is the bluetooth module connected to both the MCU and the Android board?
Thanks!
zubin3333 said:
Hi,
So after having a bit of a read of the MTCD forums I have gathered that both bluetooth handsfree and bluetooth music playback are handled by the MCU but use Android companion apps to control what the MCU does. For OBD I am a little unsure but some are suggesting that the MCU looks for the "OBD" device name and forwards data to the MCU?
So what I have gathered from this is that because the MCU handles bluetooth, so this limits what you can do with bluetooth on these android HUs (so no bluetooth tethering ect...).
Or is it that android has full access to the bluetooth module but the developers of these units haven't implemented many profiles in their bluetooth stack? In this case, is the bluetooth module connected to both the MCU and the Android board?
Thanks!
Click to expand...
Click to collapse
The disadvantage that non Intel based headunits experience, is that the bluetooth module is hooked up via a serial link (hooked up to the MCU... So Android has to talk to the MCU, then the MCU talks to the Bluetooth module). On the intel units, like most Android phones, the Bluetooth is on the SoM (or wifi SoM) which interfaces in a differently, and more direct way. There is a shim between the Bluetooth module,mcu and Android, sending the commands via a serial link. It's messy because the developers have only slowly improved it.
gtxaspec said:
The disadvantage that non Intel based headunits experience, is that the bluetooth module is hooked up via a serial link (hooked up to the MCU... So Android has to talk to the MCU, then the MCU talks to the Bluetooth module). On the intel units, like most Android phones, the Bluetooth is on the SoM (or wifi SoM) which interfaces in a differently, and more direct way. There is a shim between the Bluetooth module,mcu and Android, sending the commands via a serial link. It's messy because the developers have only slowly improved it.
Click to expand...
Click to collapse
Ahh I see! I noticed some people on the forum have commented on plugging in a Comfast USB dongle into their unit and it ended up working. Would this have any advantages, or increase the feature set?
Thanks
gtxaspec said:
The disadvantage that non Intel based headunits experience, is that the bluetooth module is hooked up via a serial link (hooked up to the MCU... So Android has to talk to the MCU, then the MCU talks to the Bluetooth module). On the intel units, like most Android phones, the Bluetooth is on the SoM (or wifi SoM) which interfaces in a differently, and more direct way. There is a shim between the Bluetooth module,mcu and Android, sending the commands via a serial link. It's messy because the developers have only slowly improved it.
Click to expand...
Click to collapse
Um, actually... ALL bluetooth hooks up to the CPU using a serial link (including the one in your cell phone). This is absolutely normal. It looks weird to some people that its sitting on a different board than the CPU, and given how poorly they work, this weird look has been *blamed* for poor performance, but there is nothing more to it. In fact, bad bluetooth performance on all the chinese radios really just comes down to bluetooth being way too complicated for the feeble minded programmers that they hire.
Now some bluetooth devices also have i2s audio hooked up to the CPU. I don't think any of the chinese radios have this (even the ones with intel). The mtc's, if I remember correctly, actually have analog audio hooked from the bluetooth module to their BD37xx, which is where the MCU controls will kick in (because mtc has the BD37 control hooked to the MCU whereas the intel ones have the BD37 hooked up to the CPU). This is actually a lot *better* than the intel units for one reason -- the intel's don't have ANY audio lines hooked up to anything. Not analog, and not digital. They run their SCO over HCI (serial), which is why the SCO usually doesn't hook up on them at all. Not that SCO can't be run over HCI, but that Android doesn't have working code to do this, which means that they had to butcher the heck out of Android to get that to work, and you already know how bad they are at writing software.
luciusfox said:
Um, actually... ALL bluetooth hooks up to the CPU using a serial link (including the one in your cell phone).....
In fact, bad bluetooth performance on all the chinese radios really just comes down to bluetooth being way too complicated for the feeble minded programmers that they hire.
..... which means that they had to butcher the heck out of Android to get that to work, and you already know how bad they are at writing software.
Click to expand...
Click to collapse
Except for the MD725, which is actually an integrated BT and WIFI RTL8723BU chipset connected directly to the SOM via USB.
This would suggest, and agree with you, that the BT stack is butchered.
Similar inexperienced mistakes can be seen in the hardware, such as OTG switch (which doesn't because it's connected in parallel to the USB hub IC), parallel mic connection.
Fortunately, the PSU looks quite robust, perhaps directly from manufacturer design notes.
**Correction - 11/Mar/18 -. Appears that some manufacturers have corrected the USB switch issue as atleast one member has OTG without modification.
Handsfree
So I found what I think is the pinnout for the MD725 board in these HUs. I can see a PCM_IN and a PCM_OUT which I would believe would be for the handsfree microphone and the handsfree audio output respectively. And I think @luciusfox was suggesting that these audio signals are not touched by the CPU at all. And I guess there is no need for them to be either. I only wonder how the people that had success in plugging in an external USB MD725 dongle managed to get sound working if the headunit relies on the PCM lines for audio.
So do you guys think that the BT stack will be improved by someone or is the interest too low and or are there other large barriers for entry for this?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
zubin3333 said:
So I found what I think is the pinnout for the MD725 board in these HUs. I can see a PCM_IN and a PCM_OUT which I would believe would be for the handsfree microphone and the handsfree audio output respectively. And I think @luciusfox was suggesting that these audio signals are not touched by the CPU at all. And I guess there is no need for them to be either. I only wonder how the people that had success in plugging in an external USB MD725 dongle managed to get sound working if the headunit relies on the PCM lines for audio.
So do you guys think that the BT stack will be improved by someone or is the interest too low and or are there other large barriers for entry for this?
Click to expand...
Click to collapse
This isnt the MD725 found in GS/MTCD units. MTCD Module has 7 Pins:
1 = +3.3v
2 = USB DM
3 = USB DP
4 = GND
5 = GND
6 = ANT
7 = ANT
As the USB Dongle tests and schematic indicate, no PCM lines, all over USB. Per my post, MD725 doesnt use MCU, all via Android.
Related
About
PodEmu is Android application that allows you to connect your Android device to iPod docking station or your car audio system. PodEmu supports both AiR (Advanced) and Simple modes so you can control your Android music app directly from docking station or from your cars steering wheel. PodEmu uses serial protocol to communicate with iPod docking station so it will work only with "old" 30-pin iPod connectors. Lightning interface is not supported.
PodEmu in action:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Features
No root required
Display track/time information for currently playing song on your car audio system or docking station display.
Control your favourite Android music app (eg. Spotify, YouTube, Amazon Prime Music, Apple Music) directly from car's steering wheel or docking station remote control
Download docking station color image to android device. Car audios usually have this feature.
Support for Bluetooth serial devices. You can assemble the dongle and connect your android completely wirelessly.
Entirely Open Source You can modify and redistribute as long as you comply with GPLv3.
Screenshots
Requirements
- Android device with USB host support (USB host support not required if you are using FT311D or FT312D dongles, or Bluetooth)
- DIY cable or DIY bluetooth dongle. Unfortunately there is no ready-to-use cables available on the market so you need some basic soldering skills to assemble your own cable. Read further for details.
Supported Music Application List
PodEmu will support any music application out of the box if this application properly declares notification in notification/status bar. The table below summarises the behaviour of the applications with which PodMode was tested.
Additionally, please remember, that in order support track/album/artist/playlist/genre navigation fully PodEmu need to have this information provided. Unfortunately there is no way to retrieve this information through the notification bar. In the best case PodEmu is only able to gather information about currently played track, total playlist size and current track position. Therefore PodEmu is trying to mimic the rest of the information for the docking station to be able to operate. Please also note, that each docking station behaves differently and therefore final behaviour will be also different. Feel free to provide feedback with your experience on XDA thread or raise an issue through GitHub issue tracker.
ListSize and ListPosition information is very important to be able to see the total amount of songs in the playlist from the docking station and to be able to select random song from list and jump to it. Whenever this information is missing PodEmu will not know how many songs are in the the current playlist and will not support "jump to" command. In such case you will see one album, that contains 11 songs. Also remember, that even if ListSize information is provided, PodEmu don't know track names "a priori". Therefore, first time you browse them from docking station, you will see titles like "Track XYZ" for all of them. However, once the song is played, its' title is remembered at given position. This list is flushed when total count of song is changed or application is restarted.
For more details about supported apps please visit GitHub project page.
How it works
To work properly PodEmu requires to be connected to your car using two separate channels:
- audio channel (obvious)
- data channel (for control and metadata information)
Audio is transmitted through "classic" analog lines. For metadata serial interface is used. PodEmu will not work with usb/lightning cable, because with such cables all information (including audio) is transmitted digitally and PodEmu is not able to interpret it (plus due to Android architecture it might not be possible to properly recognise the external device and talk to it).
Both channels mentioned above could be connected directly using wires, or bluetooth modules. Below you can find multiple options available to connect your Android device with iPod 30-pins interface.
Audio channel can be connected directly, by wires, or with use of BT module that supports A2DP profile, for example XS3868, RN52, BK8000L.
Data channel could be connected by wires. In this case you will need any USB-to-serial interface like FT232R, FT231X, FT311D, FT312D, PL2303, CP2102, CP2105, CP2108 or CP2110. Alternatively, you can also connect it with any BT module that supports SPP profile (except BLE devices which are too slow). For BT you can use modules like HC05, HC06, RN52.
Obviously you will also need to power all the modules up. There are multiple ways to do it. Below is an example of wiring diagram for XS3868 and HC05 modules that are powered up by LM2596, but you can use any power supply that can provide appropriate voltage and current.
Note for all diagrams below: R1/D1 elements are only required for those cars/docking stations where car or docking station expects the pin 18 to be pulled up to 3.3V by iPod. Otherwise it will not recognise iPod connection. R1 is required to limit the current and D1 is added to protect the dongle (could be omitted to be honest). If you are not sure if you car needs it, it is safe to start without R1/D1 and if car does not recognise connection, then just add it.
Connection diagram: Wired
This is the simplest and the most reliable version of connection.
Supported serial interfaces:
FTDI: FT232R, FT231X, FT311D, FT312D
Prolific: PL2303
SiLabs: CP2102, CP2105, CP2108, CP2110
PodEmu was tested with FT312D, PL2303, FT232R, CP2102. Other chips should also work (as claimed by driver developer), but were never tested with PodEmu.
Connection diagram: Bluetooth with HC-05 and XS3868
Bluetooth setup was tested with HC-05 as serial interface device and XS3868 to stream audio. Connection diagram that was used is the following:
Important notes:
- do not short audio ground (pin 2) with power ground (pins 15 and 16). If you do it, significant noise will appear.
- voltage is set to 3,55V and not to 3,3V. 3.3V is normal operating voltage for HC-05, 3.6V is maximum for HC-05. However 3.6V should be minimum voltage for XS3868. When voltage drops below 3.5V, XS3868 will produce audible warnings. To avoid it, but to stay within HC-05 voltage limits it is recommended to set voltage between 3.5V and 3.6V. There are known cases when slight exceeding 3.6V burned HC-05.
- before using HC-05 it need to be configured. You need to change Baud Rate to 57600 (or whatever rate is required by your car/dock station)
AT+UART=57600,0,0
For details about configuring HC-05 please refer to this manual)
- changing device name is not required, because you can choose the device from paired devices list from the application
- after BT module is configured, you need to manually pair with it. Once paired, start PodEmu, go to settings and select your device from the list of paired devices. Then PodEmu will connect automatically.
- serial interface cable has higher priority to connect, so if it is attached, BT will not connect. Detach the cable first and then restart the app.
Connection diagram: Bluetooth with RN52 (basic)
Setup with RN-52 module is shown below. The big advantage of this module is that it supports both audio and serial profiles, so you don't need to pair your phone with 2 bluetooth modules. Disadvantage is high price (~25 USD).
Note: if you use SparkFun breakout board as depictured above, for some reason they didn't made the pad for AudioGND pin, so you'll need to solder to pin 39 of the module (AGND). This is 6th pin from the topmost right side on the picture above. Luckily there is thick copper area below "SPK_L-" that you can use.
There is minor issue with such connection. Due to the fact that RN-52 is using differential output and we are using only audio positive lines, there are electrical spikes few seconds after audio goes mute. It can be heard as single "clicks" few seconds after going on mute.
Before using RN-52 module you need to program it. It is done by connection GPIO9 pin to ground. Then you can connect module to you computer to standard COM port using UART_TX and UART_RX and program it. Commands you will need:
Code:
su,04 - set baud rate 57600
sd,06 - enable only A2DP and SPP discovery profiles
sk,06 - enable only A2DP and SPP connection profiles
sn,PodEmu - set device name to RN52-PodEmu
ss,0F - set default gain level to maximum
Connection diagram: Bluetooth with RN52 (advanced)
For those who has pcb production skills I recommend to use this schematics. In comparison to previous RN-52 schematics, this implementation uses TPA6112 audio amplifier with differential input. Using this amplifier eliminates "single clicks on mute" issue described in previous section.
Note: Don't forget to setup RN-52 module as described in previous section.
My personal implementation of this dongle looks like this:
Reporting issues and requesting enhancements
Please use "Issues" tab on GitHub to report a problem or request an enhancement. You can also report a problem directly from application. For this, just enable "Enable debug collecting" option in settings, then reproduce the issue, and then use option "Send debug to developer". This will send debug file with all logs from application. Don't worry, it will not collect your personal data. However, while sending, please don't forget to describe the problem you are encounting - otherwise your email will be ignored.
Credits
USB Serial For Android: https://github.com/mik3y/usb-serial-for-android
ByteFIFO class: http://www.java2s.com/Code/Java/Threads/ByteFIFO.htm
Android Developer Icons: http://www.androidicons.com/
Question mark icon: http://www.clipartpanda.com/categories/animated-question-mark-for-powerpoint
Subscribed
If I can help you test out things, just let me now. Still have to build the cable tho.
Also if it would be possible to build a Bluetooth-only adapter (like Tune2Air), I would be really interested in!
BTW, I'm owning a 2009 BMW 3-series, with iDrive and USB/iPod-Connection (Serial+Analog).
iCstyle said:
Subscribed
If I can help you test out things, just let me now. Still have to build the cable tho.
Also if it would be possible to build a Bluetooth-only adapter (like Tune2Air), I would be really interested in!
BTW, I'm owning a 2009 BMW 3-series, with iDrive and USB/iPod-Connection (Serial+Analog).
Click to expand...
Click to collapse
Great! As soon as you have the cable and do the first tests, please let me know the result. Any help with testing is appreciated!
About BT adapter - this should not be a problem, but BT sound quality sucks so I didn't consider it. However, there are ready to use adapters on the market like this one: http://www.iphonejd.com/iphone_jd/2013/10/review-dockboss-air.html. Before starting this project I ordered one of them (not dockBoss but some other chineese copy) and it didn't work with my car. Maybe you will have more luck.
I will
I don't think BT audio is that bad. I almost don't hear any difference between Tune2Air and AUX (if source media is good quality). And I'm really into good sound quality. Then there's still the option of using a BT module with apt-x codec, which should be good enough
Does dockboss air support AVRCP with id3tags? But even if it does, it will never support browsing playlists I think? And it's boring to use a device which already exists to buy
I know a lot of people who would be interested in such a (Bluetooth) solution, and if it would support of browsing playlists/songs from apps like Google Music, Spotify, etc., that would be so awesome!!! I don't know of any other App which does this...
iCstyle said:
And it's boring to use a device which already exists to buy
Click to expand...
Click to collapse
Haha, I liked this part of your post the best!
iCstyle said:
Does dockboss air support AVRCP with id3tags? But even if it does, it will never support browsing playlists I think? And it's boring to use a device which already exists to buy
Click to expand...
Click to collapse
As far as I remember - yes, it supports AVRCP.
iCstyle said:
I know a lot of people who would be interested in such a (Bluetooth) solution, and if it would support of browsing playlists/songs from apps like Google Music, Spotify, etc., that would be so awesome!!! I don't know of any other App which does this...
Click to expand...
Click to collapse
We can consider building such BT solution as the next step. For now I would like to focus on polishing PodEmu .
I DL'd from the market a few days ago. PodMode didn't quite work for me either, but in all fairness I didn't troubleshoot.
Besides the one problem I posted in the other thread, the display doesn't often update.
If I change the song on the tablet the display continues showing whatever song was playing previously. Changing the track with the car buttons changes the display as it should.
My car is a cheap POS electronic wise so I'm only looking to utilize the display as only the track buttons works.
fr4nk1yn said:
I DL'd from the market a few days ago. PodMode didn't quite work for me either, but in all fairness I didn't troubleshoot.
Click to expand...
Click to collapse
Now I am confused. Are you talking about PodMode or PodEmu?
rp9 said:
Now I am confused. Are you talking about PodMode or PodEmu?
Click to expand...
Click to collapse
PodEmu* is the one not always displaying the correct track.
*Just stating I tried both apps.
fr4nk1yn said:
PodEmu* is the one not always displaying the correct track.
*Just stating I tried both apps.
Click to expand...
Click to collapse
Ok. PodEmu is not pushing song info by itself when it is changed. This behavior is consistent with what real iPod do. Whenever real ipod is connected to the car it's screen is blocked and you cannot control music from ipod, only from car. Anyway I noticed that my car detects song change and "asks" about song details itself. Your car apparently don't. This is why I need more testing on different cars / docks [emoji2]. I'll try to add this feature in the next build.
I just ordered the parts I need for the cable, hope to get them till saturday, then I can start testing
Btw, where are you from?
Bought one of these :http://goo.gl/RNoQop, soldered on a USB cable, reverse the data cables, the app now works great with no configuration.
One note is on my tablet when the serial adapter is first plugged in the on screen prompt has had to be accepted for PodEmu or it doesn't recognize the adapter.
fr4nk1yn said:
Bought one of these :http://goo.gl/RNoQop, soldered on a USB cable, reverse the data cables, the app now works great with no configuration.
Click to expand...
Click to collapse
Great!
fr4nk1yn said:
One note is on my tablet when the serial adapter is first plugged in the on screen prompt has had to be accepted for PodEmu or it doesn't recognize the adapter.
Click to expand...
Click to collapse
This is normal android behavior: app is asking permissions to use usb device. If you don't grant, app is not allowed to use the device.
Btw, fr4nk1yn, could you post make and model of your car?
30 pin connector only or USB?
Just wanted to clarify, will this app/DIY cable combo only work on devices with a 30 pin male connector on them, or can I use a 30pin male to USB connector to hook this up to my car stereo?
For example:
Android phone --> PodEmu --> DIY Cable --> 30pin connector --> USB --> Car Stereo
or is this only good for car stereos that have the 30 pin connector built in?
Thanks
TheCrut said:
Just wanted to clarify, will this app/DIY cable combo only work on devices with a 30 pin male connector on them, or can I use a 30pin male to USB connector to hook this up to my car stereo?
For example:
Android phone --> PodEmu --> DIY Cable --> 30pin connector --> USB --> Car Stereo
Click to expand...
Click to collapse
TheCrut, short answer is "most probably - no".
Long answer: it all depends on what is your 30pin-usb cable. If you are talking about std cable that you use to connect iPod to PC, then the answer is no. However if you have special cable supplied by your car manufacturer it might work. Eg as you might learn from spadival 's thread Hyundai cars has such dongle.
TheCrut said:
Just wanted to clarify, will this app/DIY cable combo only work on devices with a 30 pin male connector on them, or can I use a 30pin male to USB connector to hook this up to my car stereo?
For example:
Android phone --> PodEmu --> DIY Cable --> 30pin connector --> USB --> Car Stereo
or is this only good for car stereos that have the 30 pin connector built in?
Thanks
Click to expand...
Click to collapse
If your stereo supports an iPod connection by USB you can skip the 30pin connector. You just need to wire the serial wires to the USB data pins.
@rp9 I'm getting weirdness but I'm hoping I solved it.
The app doesn't like when the tablet sleeps and wakes continuously. The track buttons starts changing tracks "randomly". Track forward will cycle between back and forward, switching between the same 2 songs, then it picks a track somewhere in the playlist then operates normally for awhile.
I've started killing PodEmu on suspend which I hope fixes the issue.
-Edit: Hyundais pretty much suck.
I think I've narrowed the issue down to PodEmu being connected to the serial adapter but the "dock" is "disconnected".
fr4nk1yn said:
-Edit: Hyundais pretty much suck.
I think I've narrowed the issue down to PodEmu being connected to the serial adapter but the "dock" is "disconnected".
Click to expand...
Click to collapse
Hi fr4nk1yn. I am not sure if I understood correctly your problem. Can you please describe step by step how to reproduce the issue, expected behaviour, observed behaviour. Also without logs I cannot do too much. Please collect and send them to me.
hey, what about hc-05 support?
and thanks ofcourse!
if you need me as a tester for the hc-05 I can help.
rp9 said:
Hi fr4nk1yn. I am not sure if I understood correctly your problem. Can you please describe step by step how to reproduce the issue, expected behaviour, observed behaviour. Also without logs I cannot do too much. Please collect and send them to me.
Click to expand...
Click to collapse
I'll get some logs to you. I don't actually drive the car too much during the week. I'm afraid the logs will be quite large trying to replicate the issue.
I'm not sure what's causing the disconnects.
I'm using Timur's kernel with a N7'13 so when I shut the key off the tablet goes to sleep. Killing PodEmu before sleep made no difference.
Another oddity, that should not be caused by the app but only happens while in use, is Play Music frequently "not being able to play the song".
@rp9 I sent a log. Unfortunately I didn't look beforehand so it has a lot of previous stuff going back to the 31st.
Hopefully the stuff from tonight is of help.
Thanks for the making the app open source. I drive FIAT Punto in India 2013 Model. I would like to understand how this works? My Car supports direct 30 pin USB connection no special cable is needed. Does the app send the audio over usb? I will be glad to help you to test it out with my car.
Hello Xda,
I've a ZTE Vodafone Smart Ultra 6 build VDF-995NB02-IT10d Android 6.0.1. Kernel 3.10.49.
Since when I upgraded to actual version of Android, I have a very irritating problem:
the smartphone has the APP "RADIO FM" that activates the FM radio chip inside the device, allowing to listen to the "traditional" FM radio (thus NO streaming!!!).
I used to start the app (RADIO FM), select a radio station, activate the Bluetooth (BT) on the smartphone, and I was able to connect to my wireless BT earphone (Jabra Pulse). Perfect ! Hours of music and information freely walking and running without any hanging wire....
Now, since Android 6.0.1, when I activate the BT, the Audio music signal is no longer routed to the BT, so I cannot listen to the sound provided by the RADIO FM to the BT wireless earphone (Jabra Pulse). Why ?
I also tried to use an other BT wireless device (Plantronics M165 : a mono BT device ), but even with this device no audio is routed from RADIO FM app to the audio BT "channel".
However if I start any Streaming Music APP, and BT is active, I can perfectly ear the music/sound via any wireless BT device.
Is "RADIO FM" a native android app ? Can any one help me ?
I know it is a quite insignificant problem, however it save me money because I do not use Internet GBytes of streaming radios and I can listen to high quality Digital Radios.
I feel it is really a silly bug inside this small app or in BT code.
I spent hours and hours googling in internet, success less. I would really appreciate your help.
Many thanks in advance for the patience and great support.
Giuseppe.
Joe.peter said:
Hello Xda,
I've a ZTE Vodafone Smart Ultra 6 build VDF-995NB02-IT10d Android 6.0.1. Kernel 3.10.49.
Since when I upgraded to actual version of Android, I have a very irritating problem:
the smartphone has the APP "RADIO FM" that activates the FM radio chip inside the device, allowing to listen to the "traditional" FM radio (thus NO streaming!!!).
I used to start the app (RADIO FM), select a radio station, activate the Bluetooth (BT) on the smartphone, and I was able to connect to my wireless BT earphone (Jabra Pulse). Perfect ! Hours of music and information freely walking and running without any hanging wire....
Now, since Android 6.0.1, when I activate the BT, the Audio music signal is no longer routed to the BT, so I cannot listen to the sound provided by the RADIO FM to the BT wireless earphone (Jabra Pulse). Why ?
I also tried to use an other BT wireless device (Plantronics M165 : a mono BT device ), but even with this device no audio is routed from RADIO FM app to the audio BT "channel".
However if I start any Streaming Music APP, and BT is active, I can perfectly ear the music/sound via any wireless BT device.
Is "RADIO FM" a native android app ? Can any one help me ?
I know it is a quite insignificant problem, however it save me money because I do not use Internet GBytes of streaming radios and I can listen to high quality Digital Radios.
I feel it is really a silly bug inside this small app or in BT code.
I spent hours and hours googling in internet, success less. I would really appreciate your help.
Many thanks in advance for the patience and great support.
Giuseppe.
Click to expand...
Click to collapse
Are you saying that you managed to get the FM radio working WITHOUT having a standard wired earpiece plugged in? If so, I would be amazed since this is what you see if you try it without!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my Pixel C using Tapatalk
Hi Colin,
thanks for your replay.
You are right, if I do not have the "wired" earphone plugged in I cannot listen to the RADIO FM. That's because the wire of earphone is also the antenna.
I would make few scenario so you may have more elements to evaluate.
Scenario 1 Normal Operation
I plug in the wired earphone, start RADIO FM and I can listen to the radio via earphone.
If I click on the "speaker" icon in the middle of the app I can then also listen to the radio via the smartphone loudspeaker. In this case the earphone is muted.
Scenario 2 Normal Operation
I plug in an "Antenna Tool" ( a wireless antenna developed by me to substitute the wired earphone ) and I can listen to the RADIO FM via the smartphone loudspeaker (because the wired earphone is not plugged in), of course ONLY if I push the "speaker" icon in the middle of the App.
Scenario 3 Normal Operation (BEFORE actual Android 6.0.1 )
I plug in the antenna (either the "wired earphone" or the "Antenna Tool" no matter which of two they are "just an antenna"), I start the RADIO FM, then I start BT from the smartphone, wear my Jabra Pulse BT wireless earphone and I start its BT, then the two BT devices automatically connect each other, then I can listen to the RADIO FM in the Jabra Pulse earphone.
Note that if, in place of the Jabra Pulse BT wireless device I use my Plantronics M165 a mono BT earphone device, I can listen to the RADIO FM, too.
Note that if I plugged in as antenna the wired earphone, the earphone is muted when I listen the RADIO FM via BT Wireless earphone.
That's wonderful: I can go running without any hanging wire, listening my favourite FM Radios and news, football sport events without going in streaming using INTERNET.
Scenario 4 The PROBLEM (With actual Android 6.0.1 release)
I perform exactly the same operations as above 3 Scenarios, but when I activate the BT in the smartphone AND any of two BT devices above (either Jabra Pulse or Plantronics M165) have paired, the RADIO FM audio disappears.
I cannot listen to the Radio FM neither from the wired earphone nor if I push the "speaker" icon in the middle of the app.
It seems, when BT is activated, that RADIO FM app doesn't route the audio output to the BT environment.
I am quite sure about that because if, in place of RADIO FM, I use any other sound app (e.g. Spotify) I can listen to the music via both BT wireless devices.
I hope I didn't bore you. I gave you some more detailed elements for your evaluations. Feel free to ask me any additional clarifications.
I thank you for your help,
Giuseppe.
CPNowell said:
Are you saying that you managed to get the FM radio working WITHOUT having a standard wired earpiece plugged in? If so, I would be amazed since this is what you see if you try it without!
Sent from my Pixel C using Tapatalk
Click to expand...
Click to collapse
Joe.peter said:
Hi Colin,
thanks for your replay.
You are right, if I do not have the "wired" earphone plugged in I cannot listen to the RADIO FM. That's because the wire of earphone is also the antenna.
Click to expand...
Click to collapse
I already knew that and is why I replied questioning what you are trying to do...
Joe.peter said:
Scenario 1 Normal Operation
I plug in the wired earphone, start RADIO FM and I can listen to the radio via earphone.
If I click on the "speaker" icon in the middle of the app I can then also listen to the radio via the smartphone loudspeaker. In this case the earphone is muted.
Click to expand...
Click to collapse
Yes but since the outer screen of the earphone cable is the antenna, it has to be left plugged in or the radio will not receive a signal...
Joe.peter said:
I plug in an "Antenna Tool" ( a wireless antenna developed by me to substitute the wired earphone ) and I can listen to the RADIO FM via the smartphone loudspeaker (because the wired earphone is not plugged in), of course ONLY if I push the "speaker" icon in the middle of the App.
Click to expand...
Click to collapse
Then you have managed to perform a miracle! You'll need to define more exactly what you mean by "Antenna Tool" since "a wireless antenna", by definition, is an oxymoron!! No such thing!
Joe.peter said:
That's wonderful: I can go running without any hanging wire,...
Click to expand...
Click to collapse
I have a hard time believing that since there needs to be some sort of physical wire connected to that screen for the radio to work at all, however short it may be...
Joe.peter said:
I hope I didn't bore you. I gave you some more detailed elements for your evaluations. Feel free to ask me any additional clarifications.
Click to expand...
Click to collapse
No, you didn't bore me at all... I suspect that this is a combination of limitations of the app and the updated bluetooth stack in Marshmallow and there's probably nothing you can do about it. If I use a conventional streaming radio app, I can either have the wired headset or the bt headset/speaker but crucially NOT both together and thereby hangs the key I think...
Hi Colin,
I do appreciated your time spent on this. I was thinking if there is an other FM RADIO app that I can install to see if it is really a combination of limitation of the "RADIO FM" app or a bug in my app only.
I just found a couple of "SPIRIT" apps, but they are for "root" devices. Mine is not. Moreover it is expensive to download them to just make a test.
Do you have evidence of any similar (stock) app that I can install and use in my device/installation ?
Have a great day. Giuseppe.
CPNowell said:
I already knew that and is why I replied questioning what you are trying to do...
Yes but since the outer screen of the earphone cable is the antenna, it has to be left plugged in or the radio will not receive a signal...
Then you have managed to perform a miracle! You'll need to define more exactly what you mean by "Antenna Tool" since "a wireless antenna", by definition, is an oxymoron!! No such thing!
I have a hard time believing that since there needs to be some sort of physical wire connected to that screen for the radio to work at all, however short it may be...
No, you didn't bore me at all... I suspect that this is a combination of limitations of the app and the updated bluetooth stack in Marshmallow and there's probably nothing you can do about it. If I use a conventional streaming radio app, I can either have the wired headset or the bt headset/speaker but crucially NOT both together and thereby hangs the key I think...
Click to expand...
Click to collapse
I don't know of any other apps I'm afraid...
Sent from my Pixel C using Tapatalk
Firmwere italiano
Aiuto cerco firmwere in italiano di questo telefono qualcuno sa aiutarmi
Just bought a unit specifically for my Kia.
Its an OctaCor PX5 MTCE unit [based in what I've read MTCE and MTCD are the same, right?]
Everything works well with the unit except bluetooth. It won't discover or connect to any device. The device name and password fields in the BT menu are blank. When I change those fields and add something, it doesn't make a difference. Its just constantly "searching"
I've explored all of the differenr BT optiona in factory settings menu and ive tried installing BT managers from the play store and they don't work either.
I can't seem to find anyone else having this problem.
No matter what phone or tablet I use, it doesn't discover it.
What could the problem be?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my SM-G925T using Tapatalk
j2gifted said:
Just bought a unit specifically for my Kia.
Its an OctaCor PX5 MTCE unit [based in what I've read MTCE and MTCD are the same, right?]
Everything works well with the unit except bluetooth. It won't discover or connect to any device. The device name and password fields in the BT menu are blank. When I change those fields and add something, it doesn't make a difference. Its just constantly "searching"
I've explored all of the differenr BT optiona in factory settings menu and ive tried installing BT managers from the play store and they don't work either.
I can't seem to find anyone else having this problem.
No matter what phone or tablet I use, it doesn't discover it.
What could the problem be?
View attachment 4384130View attachment 4384131View attachment 4384132
Sent from my SM-G925T using Tapatalk
Click to expand...
Click to collapse
The behaviour you describe is what I see if the wrong BT module is selected in the factory settings. If you have tried each BT module type, rebooted and then tried pairing via the BT app (not the BT settings) then its possible the BT module is faulty I guess?
Andy
ADB100 said:
The behaviour you describe is what I see if the wrong BT module is selected in the factory settings. If you have tried each BT module type, rebooted and then tried pairing via the BT app (not the BT settings) then its possible the BT module is faulty I guess?
Andy
Click to expand...
Click to collapse
+1
ADB100 said:
The behaviour you describe is what I see if the wrong BT module is selected in the factory settings. If you have tried each BT module type, rebooted and then tried pairing via the BT app (not the BT settings) then its possible the BT module is faulty I guess?
Andy
Click to expand...
Click to collapse
I'm going to go back and try each one again.
How can I find out which adapter is in the unit?
Also, are the BT modules easy to replace... OR is there an option to add a new one via USB input?
Sent from my SM-G925T using Tapatalk
j2gifted said:
I'm going to go back and try each one again.
How can I find out which adapter is in the unit?
Also, are the BT modules easy to replace... OR is there an option to add a new one via USB input?
Sent from my SM-G925T using Tapatalk
Click to expand...
Click to collapse
I am not sure if its something that can be replaced as its either directly on the MCU board or a module soldered to it. I am sure if you post some pictures of the internals someone will be able to identify it for you.
I would try each one in the factory settings followed by a reboot and then test with the BT app.
I think several people have tried USB BT modules without success. BT is a bit of an odd one as Android isn't natively aware of the BT module in these units like a phone or tablet is. The BT utilities are propietary to the hardware and aren't the built-in Android ones.
Andy
ADB100 said:
I am not sure if its something that can be replaced as its either directly on the MCU board or a module soldered to it. I am sure if you post some pictures of the internals someone will be able to identify it for you.
I would try each one in the factory settings followed by a reboot and then test with the BT app.
I think several people have tried USB BT modules without success. BT is a bit of an odd one as Android isn't natively aware of the BT module in these units like a phone or tablet is. The BT utilities are propietary to the hardware and aren't the built-in Android ones.
Andy
Click to expand...
Click to collapse
Figers crossed that going through the settings again works.
If not, I'll have to find the energy to pull the radio out and take pics of the inside
Sent from my SM-G925T using Tapatalk
This seems to be a Klyde (KLD) unit. I would put my bets on MD725 Bluetooth module type.
Do you remember what it was initially set to?
I guess you probably did the same mistake as most users do the first time. They try to pair Bluetooth devices using Android Bluetooth settings menu. This does NOT work with MTCD/MTCE units since Bluetooth is controlled by MCU. Neither do any of the Bluetooth management apps in Play store work.
You need to use the Bluetooth application which is installed on your head unit. It might be called "Bluetooth" or "Phone". On my KLD stock firmware it does have the green phone icon. Open the app and use it to pair your Bluetooth device (not only phones).
If it's not an MD725 my next bet would be SD968 Bluetooth module.
I've gone through every BT option in factory settings. The one thatbwas selected by default was the BC5 unless it was accidentally changed.
I'm using the stock bluetooth app to connect..
Still no luck..
Any other suggestions?
Stock bluetooth app
Sent from my SM-G925T using Tapatalk
Factory settings bluetooth options
Sent from my SM-G925T using Tapatalk
Bluetooth pairing screen constantly searching
Sent from my SM-G925T using Tapatalk
Here is the link to the radio I purchased..
If the listing is correct, the BT module is 7OC-MD-705... i think?
http://vi.raptor.ebaydesc.com/ws/eB...5&pm=1&ds=0&t=1514445690000&ver=0&cspheader=1
Sent from my SM-G925T using Tapatalk
I confirm you're in the right app.
Did you try selecting MD725 module in factory settings and rebooting the unit? Then try again.
I had a problem with pairing the bluetooth module SD968. I bought on aliexpress the USB device. I installed factory settings in the BT section type-MD725. I have connected the device COMFAST Bluetooth4.0 + wifi 150 Mbps Wi-Fi Dongle RTL8723BU to the USB input DASAITA. The device overloaded, bluetooth and Wi-Fi started to work perfectly.
---------- Post added at 20:42 ---------- Previous post was at 20:35 ----------
I shot the video in two parts: the first part, when Bluetooth is not included. This is the device status within 8 hours in sleep mode. The second part of the video as the bluetooth on the device after five hours, the device is in sleep mode.
This description of my problem, which I have given to the seller DASAITA : this is the first part of the video. Bluetooth is not working. The beginning of the video shooting is 7 hours and 8 minutes. After the last switch it took more than 5 hours. https://youtu.be/GOzM5bw9Z1E.
This is the second part of the video. Bluetooth working. Time is 19 hours and 46 minutes. After the last turn on the device, it took less than 5 hours. Turned on the device in 7 hours 04 minutes - Bluetooth not working. The device is switched on 11 hours 38 minutes-works bluetooth. The device is turned on 13 hours and 23 minutes-works bluetooth.
The device is switched on, in 16 hours 57 minutes-works bluetooth. The device is included in 19 hours 46 minutes-works bluetooth.
https://youtu.be/u47527OJYQg
Here are the pics of the inside of the unit... not sure where bluetooth adapter is
Sent from my SM-G925T using Tapatalk
SkyBeam2048 said:
I confirm you're in the right app.
Did you try selecting MD725 module in factory settings and rebooting the unit? Then try again.
Click to expand...
Click to collapse
Yes, I went through each selection and restarted everytime and nothing changed.
Sent from my SM-G925T using Tapatalk
j2gifted said:
Here are the pics of the inside of the unit... not sure where bluetooth adapter is
Click to expand...
Click to collapse
The bluetooth chip is right next to the point where the black cable (antenna) is soldered too. In fact there are two antenna soldering points there where your unit only has one antenna equipped. I can't read it on the chip but I think I can possibly spot the Realtek logo on it. Have a close look at the chip to the left of your PX5 SoM where the antenna is soldered to the board. I compared it to pictures I made from my one. The board layout of my KLD unit seems to be identical. However my Bluetooth chip is square, yours is rectangle shape. Take a close-up picture of the chip where the antenna is soldered to the board. It might be either Realtek RTL8723bu (which is MD725) or it's the SD-968 chip.
What I am not sure about is whether the module uses antenna diversity and/or which antenna is used for Bluetooth. My unit actually got antennas solered on both antenna connection points, yours only has one on the lower one. So perhaps it's an antenna issue which would explain why you don't get any connection.
KIgorM said:
I had a problem with pairing the bluetooth module SD968. I bought on aliexpress the . I installed factory settings in the BT section type-MD725. I have connected the device COMFAST Bluetooth4.0 + wifi 150 Mbps Wi-Fi Dongle RTL8723BU to the USB input DASAITA. The device overloaded, bluetooth and Wi-Fi started to work perfectly.
Click to expand...
Click to collapse
Excuse me KIgorM, can you tell me if with this adaptor you can pair other devices (not only phone, obd)? And wifi and bluetooth performances are better now than with internal chip?
Thank you in advance
jimbover said:
Excuse me KIgorM, can you tell me if with this adaptor you can pair other devices (not only phone, obd)? And wifi and bluetooth performances are better now than with internal chip?
Thank you in advance
Click to expand...
Click to collapse
Hi. I haven't tried other devices via Bluetooth and Wi-Fi to connect to the multimedia device. The voice quality when talking on the phone via bluetooth better than the module SD968.
SkyBeam2048 said:
The bluetooth chip is right next to the point where the black cable (antenna) is soldered too. In fact there are two antenna soldering points there where your unit only has one antenna equipped. I can't read it on the chip but I think I can possibly spot the Realtek logo on it. Have a close look at the chip to the left of your PX5 SoM where the antenna is soldered to the board. I compared it to pictures I made from my one. The board layout of my KLD unit seems to be identical. However my Bluetooth chip is square, yours is rectangle shape. Take a close-up picture of the chip where the antenna is soldered to the board. It might be either Realtek RTL8723bu (which is MD725) or it's the SD-968 chip.
What I am not sure about is whether the module uses antenna diversity and/or which antenna is used for Bluetooth. My unit actually got antennas solered on both antenna connection points, yours only has one on the lower one. So perhaps it's an antenna issue which would explain why you don't get any connection.
Click to expand...
Click to collapse
So I actually got it working. I noticed that the BT module appeard to be bent and loose. So i straightened it out and pushed the contact points bck in the board the best I could, and that did the trick.
Part of the board was chipped too in the same area.. i believe a screw or something may have hit it as it was right near a hole.
The only problem I have now is that sometime [every few days] the unit will appear to forget my steering wheel settings. When I open the key study, the selections are there but not working... so I have to set them again... why is that?
Sent from my SM-G925T using Tapatalk
Hi all! Recently got an Android 8.0 based GS (XTRONS) unit, the TE706PL.
The main issue that I have with the unit is that it does not have a physical volume knob. I was OK with this when I purchased it as I planned on adding in my own. I have used an Arduino and a rotary encoder to 'replicate' a HID volume knob.
This is able to adjust the volume on my computer as well as on my Oneplus 3T with an OTG adaptor. However, when connected to the head unit, it does not work. I also tried connecting a standard USB keyboard to the headunit and found that all the keys work, including media play/pause keys, except volume up, down and mute do not function.
On the head unit, I used this app: https://play.google.com/store/apps/details?id=innerlife.keyboard.multilanguagekeymapredefiner&hl=en to check, and found the inputs were correctly being read as 'MEDIA_VOLUME_UP' , etc.
I tried this on the stock GS Android 8.0 ROM as well as Malaysk's Android 8.0 PX5 ROM. Is there anything that can be done to allow this to control the volume?
Any help much appreciated!
kaise123 said:
Hi all! Recently got an Android 8.0 based GS (XTRONS) unit, the TE706PL.
The main issue that I have with the unit is that it does not have a physical volume knob. I was OK with this when I purchased it as I planned on adding in my own. I have used an Arduino and a rotary encoder to 'replicate' a HID volume knob.
This is able to adjust the volume on my computer as well as on my Oneplus 3T with an OTG adaptor. However, when connected to the head unit, it does not work. I also tried connecting a standard USB keyboard to the headunit and found that all the keys work, including media play/pause keys, except volume up, down and mute do not function.
On the head unit, I used this app: https://play.google.com/store/apps/details?id=innerlife.keyboard.multilanguagekeymapredefiner&hl=en to check, and found the inputs were correctly being read as 'MEDIA_VOLUME_UP' , etc.
I tried this on the stock GS Android 8.0 ROM as well as Malaysk's Android 8.0 PX5 ROM. Is there anything that can be done to allow this to control the volume?
Any help much appreciated!
Click to expand...
Click to collapse
Look for a thread of @bose123. He programmed his own
Enviado desde mi SM-G950F mediante Tapatalk
ikerg said:
Look for a thread of @bose123. He programmed his own
Enviado desde mi SM-G950F mediante Tapatalk
Click to expand...
Click to collapse
Thanks! Doesn't seem to be a valid XDA username though... Do you know where the thread was by any chance? I've done a fair bit of searching
kaise123 said:
Thanks! Doesn't seem to be a valid XDA username though... Do you know where the thread was by any chance? I've done a fair bit of searching
Click to expand...
Click to collapse
Sorry is @Bose321
That thread is for controlling radio from external remote control.....perhaps contacting him you can get the solution
https://forum.xda-developers.com/showthread.php?t=3625038
Enviado desde mi SM-G950F mediante Tapatalk
ikerg said:
Sorry is @Bose321
That thread is for controlling radio from external remote control.....perhaps contacting him you can get the solution
https://forum.xda-developers.com/showthread.php?t=3625038
Enviado desde mi SM-G950F mediante Tapatalk
Click to expand...
Click to collapse
Thanks for the suggestion, but unfortunately it's not quite what I'm looking for. His app allows you to control the built in microntek apps with a remote or media buttons. My media buttons are working fine, it's specifically Volume Up, Down and Mute which do not work (Android system seems to flat out ignore the input)
I was wondering if, as a potential workaround I could use an app to remap keyboard inputs to volume level inputs? I haven't been able to do this with Tasker so far.
kaise123 said:
Thanks for the suggestion, but unfortunately it's not quite what I'm looking for. His app allows you to control the built in microntek apps with a remote or media buttons. My media buttons are working fine, it's specifically Volume Up, Down and Mute which do not work (Android system seems to flat out ignore the input)
I was wondering if, as a potential workaround I could use an app to remap keyboard inputs to volume level inputs? I haven't been able to do this with Tasker so far.
Click to expand...
Click to collapse
Volume on our units is not controlled by normal media commands on android. Is controlled by the MCU and therefore by any microntek service.
Ask bose321 for support as he investigated this.
Enviado desde mi SM-G950F mediante Tapatalk
kaise123 said:
I was wondering if, as a potential workaround I could use an app to remap keyboard inputs to volume level inputs? I haven't been able to do this with Tasker so far.
Click to expand...
Click to collapse
Try this https://forum.xda-developers.com/showthread.php?p=76032481
aluver said:
Try this https://forum.xda-developers.com/showthread.php?p=76032481
Click to expand...
Click to collapse
Thanks, I did actually find that. I have given this a go manually through terminal emulator. When run as standard user, I get the following:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
And when run with SU I get:
However nothing changes. I have tried this with a number of key codes that I found and none seem to have an effect. Am I running this incorrectly?
Any help definitely appreciated! I feel like I'm close here
kaise123 said:
Any help definitely appreciated! I feel like I'm close here
Click to expand...
Click to collapse
Try keycodes 273 (volumeUP) and 281 (volumeDOWN) from su.
If that works I can give you whole list
https://forum.xda-developers.com/showpost.php?p=67855471&postcount=17
aluver said:
Try keycodes 273 (volumeUP) and 281 (volumeDOWN) from su.
If that works I can give you whole list
https://forum.xda-developers.com/showpost.php?p=67855471&postcount=17
Click to expand...
Click to collapse
Thankyou!!! You saved me a lot of headscratching haha. My next step was trying to pull apart MTCManager to see what it could reveal....
Now... Tasker won't recognise my device is rooted, but that's a separate issue, may need to start a new thread at-least I know what I want to do is possible now.
Would it be possible to set this up using MTCD Tools? I'm very interested in figuring out how to configure this in mtcd tools.
kaise123 said:
The main issue that I have with the unit is that it does not have a physical volume knob. I was OK with this when I purchased it as I planned on adding in my own. I have used an Arduino and a rotary encoder to 'replicate' a HID volume knob.
Click to expand...
Click to collapse
I have a touch screen only (ISUDAR 7.1.2_GS PX3 2GB RAM) with no buttons at all and planned to do the same, so I'm interested in how this works out for you. My steering wheel does not have buttons, so I was going to replace it with one that does and see if it transmits on the CANbus because supposedly these ISUDAR units can adapt to it using the CANbus decoder box and app supplied with the head unit. If that didn't work on the vehicle harness my approach was to use Arduino to send CAN signals and read them with the CANbus decoder. I've not tried either yet, and am new to Arduino but seems possible. Do you have the CANbus decoder?
Also, does your unit have a SD card (or GPS) slot? Mine doesn't. If no, how/where did you place the flash files and start the system update to install the Malaysk ROM? I can't get much support from ISUDAR.
VigorPD said:
I have a touch screen only (ISUDAR 7.1.2_GS PX3 2GB RAM) with no buttons at all and planned to do the same, so I'm interested in how this works out for you. My steering wheel does not have buttons, so I was going to replace it with one that does and see if it transmits on the CANbus because supposedly these ISUDAR units can adapt to it using the CANbus decoder box and app supplied with the head unit. If that didn't work on the vehicle harness my approach was to use Arduino to send CAN signals and read them with the CANbus decoder. I've not tried either yet, and am new to Arduino but seems possible. Do you have the CANbus decoder?
Also, does your unit have a SD card (or GPS) slot? Mine doesn't. If no, how/where did you place the flash files and start the system update to install the Malaysk ROM? I can't get much support from ISUDAR.
Click to expand...
Click to collapse
ISUDAR are a seller AFAIK, your MCU will tell you what unit you have.
ALL MTCD/E units can use CAN Bus even if they are universal units - the data for all supported MTCD/E vehicles is in all MTCD/E MCUs, so you do not need anything other than a CAN Bus decoder for your car and a loom from your headunit manufacturerrto attach it to (or you could make one). Once you have these 2 things you just set the CAN Bus type in factory settings and your SWC should work.
VigorPD said:
I have a touch screen only (ISUDAR 7.1.2_GS PX3 2GB RAM) with no buttons at all and planned to do the same, so I'm interested in how this works out for you. My steering wheel does not have buttons, so I was going to replace it with one that does and see if it transmits on the CANbus because supposedly these ISUDAR units can adapt to it using the CANbus decoder box and app supplied with the head unit. If that didn't work on the vehicle harness my approach was to use Arduino to send CAN signals and read them with the CANbus decoder. I've not tried either yet, and am new to Arduino but seems possible. Do you have the CANbus decoder?
Also, does your unit have a SD card (or GPS) slot? Mine doesn't. If no, how/where did you place the flash files and start the system update to install the Malaysk ROM? I can't get much support from ISUDAR.
Click to expand...
Click to collapse
I don't have buttons on my steering wheel either. I also wanted to experiment with using CANBus signals to set the volume, but I was not able to find a reliable or well documented way to emulate canbus commands. In the end, I was able to get tasker to pick up the key inputs (Using AutoInput) and output the root command for changing the volume. I used an Arduino Pro Micro and the HID keyboard library to make an emulated keyboard input.
My device had a GPS slot only, but upon opening it I found that it had provision for an 'SD' slot. If you do not have a GPS slot there are other threads out there that might be able to help you, or if you are comfortable opening your device, see if it has the header to add one in yourself.
kaise123 said:
In the end, I was able to get tasker to pick up the key inputs (Using AutoInput) and output the root command for changing the volume. I used an Arduino Pro Micro and the HID keyboard library to make an emulated keyboard input.
Click to expand...
Click to collapse
I'm still not sure which direction I will take but am interested in more details on this solution if you would share. I'm a noob at everything you mentioned above. It gives me another idea to create a multi function knob like a simplified version all the new cars have for infotainment control. Rotate for volume, push for mute/power, forward for Home, back for Back, etc.
kaise123 said:
My device had a GPS slot only, but upon opening it I found that it had provision for an 'SD' slot. If you do not have a GPS slot there are other threads out there that might be able to help you, or if you are comfortable opening your device, see if it has the header to add one in yourself.
Click to expand...
Click to collapse
ISUDAR got back to me and said to load it on an empty USB stick instead. The rear of the case does have an open area marked for mounting a SD slot just no hardware populating it. I just had the unit opened up last week and added a homemade button to allow hitting the power button inside without needing a paper clip. If I open it up again what am I looking for with respect to a header?
I'm pretty keen to hack and customize more but struggle finding all the knowledge bits to connect the dots spanning software and hardware.
Did you manage to resolve this issue?
I've got the same head unit and the same issue, did you find a solution to the problem?
Thanks
kaise123 I have the Xtrons unit as well and need to do a similar solution to yours with a USB dial I have for volume and mute. It looks like you have root on this one. Can you direct me to instructions for rooting this unit?
frisbin said:
kaise123 I have the Xtrons unit as well and need to do a similar solution to yours with a USB dial I have for volume and mute. It looks like you have root on this one. Can you direct me to instructions for rooting this unit?
Click to expand...
Click to collapse
You need to be more specific, Xtrons are a seller not a manufacturer, there are no Xtrons units - units are identified by the MCU so you need to post that and the Andorid version youre running. There are also many guides to rooting.
typos1 said:
You need to be more specific, Xtrons are a seller not a manufacturer, there are no Xtrons units - units are identified by the MCU so you need to post that and the Andorid version youre running. There are also many guides to rooting.
Click to expand...
Click to collapse
Thanks for the instruction about that.
Like kaisel123, mine is labeled TE706PL (xtrons).
It shows Model px5, Android version 8.0.0, MCU version MTCE_GS_V2.78_3
Found some threads, reading through.
frisbin said:
Thanks for the instruction about that.
Like kaisel123, mine is labeled TE706PL (xtrons).
It shows Model px5, Android version 8.0.0, MCU version MTCE_GS_V2.78_3
Found some threads, reading through.
Click to expand...
Click to collapse
Right, you have a GS Oreo unit, theres a thread about rooting or Malaysk's ROM is rooted.
So, the Bluetooth function in Android Headunits act differently than an Android tablet would, for one, it's a handsfree receiver that does not allow (correct me if I'm wrong) uplink with another device.
I have a DSP amp combo that uses BT to connect to an Android phone/tablet, which works fine, but my Dasaita PX5 won't connect to it. It just sees it, pairs, but doesn't connect.
Is there any way I can use a generic Bluetooth USB dongle to connect to it instead? Or is there any other way to allow connection with other BT devices (I have no luck in connecting OBD dongles too, BT or Wi-FI).
Thanks.
The device isn't an MTCB, being a dasiata it's likely an MTCD.
The answer to the BT question is no, you can thank the developer of the device for the hacked BT implementation.
Requesting mod moves to MTCD general.
Cheers! I've been out of touch for a bit and completely forgotten about the MTCx denominatin,
Thanks.
marchnz said:
The device isn't an MTCB, being a dasiata it's likely an MTCD.
The answer to the BT question is no, you can thank the developer of the device for the hacked BT implementation.
Requesting mod moves to MTCD general.
Click to expand...
Click to collapse
So just to be clear before I go down this path, there is NO external USB bluetooth module that will work with an MTCE head unit? Even if the USB module somehow uses the driver/firmware in the factory settings dropdown?