I have a 1 DIN car radio with octacore PX5-CPU and Android 6, connected to the original automatic antenna of my Mazda MX5. When the radio starts the antenna drives out, so far so good. But when I turn the radio of (push the button), the antenna stays out. Only when I turn out the car and pull the car-key, the antenna drives in.
Before I bought this radio I had the same one with Android 4.4.4 and quadcore CPU and this radio works fine with the automatic antenna.
I have already searched in the settings to change the control of the automatic antenna. But without success.
Any idea what it could be?
Thanks for help
It's a long shot, but You could try and see if You can "kill" the Radio application (stop it from running) and see if that makes the antenna retract.
It might be that even though you stop the radio the app itself remains in memory and the car's electronics "sees" it and doesn't retract the antenna until the app is stopped (by stopping the HeadUnit completely).
Related
OK, so I got everything working on my unit back in November. Bluetooth worked fine and connected with my phone and OBD device (OBDLink LX).
Suddenly within the last couple of weeks, it's stopped connecting. I have tried rebooting the radio, unplugging/replugging my bluetooth OBD, unpairing the phone, repairing, etc... Nothing seems to work for more than a few minutes. Sometimes it will work for one trip, but then the next trip it's back to REFUSING to connect to either bluetooth device. Remember - BOTH worked before, and I didn't change anything.
Since it's happening with both my Phone and my OBD device, it appears like it is a fault in the stereo. I really don't want to do a full factory reset as that would entail many hours sitting in the car wasting gas idling while I reinstall/reconfigure EVERYTHING only to not even be sure it won't do this again.
Anybody have any tips on something I can do to fix this? There does not appear to be any kind of "unpair" option in the bluetooth settings on the radio itself. I'm wondering if there's a way I can manually reset just all of the bluetooth settings - blow them away and start over without resetting the whole device.
This is a pretty big deal - one of the #1 reasons I bought this device was for OBD datalogging. If that feature does not work, I will rip it out of my dashboard and ebay it. PERIOD...
Adcice?
Nobody?
I tried changing the bluetooth device name, changing the PIN and re-pairing my devices. They work intermittently, but 90% of the time won't connect, or if they do, they won't stay connected.
This is turning my radio into an expensive piece of garbage...
lotherius said:
I tried changing the bluetooth device name, changing the PIN and re-pairing my devices. They work intermittently, but 90% of the time won't connect, or if they do, they won't stay connected.
Click to expand...
Click to collapse
Try keeping wifi on all the time (even if not actually connected to any network).
themissionimpossible said:
Try keeping wifi on all the time (even if not actually connected to any network).
Click to expand...
Click to collapse
I do have Wifi on all the time. I have an LTE Hotspot I keep in the glovebox of my car that powers up as soon as the car powers on. So there's 100% wifi coverage for my stereo no matter where I'm at.
I can randomly get it to connect, but it won't stay connected. When I'm in the bluetooth menu, the devices will actually disappear from the paired devices list. Both paired and available will go blank just suddenly as the devices drop off. Then they'll reappear on their own. So it appears to be the bluetooth stack is crashing - but I'm not sure why.
It is a KLD RK3188 unit. Running latest MCU (came preloaded, just bought it in November - I haven't put a new MCU) and recent firmware, which is a stock firmware, not MalaySK (MalaySK doesn't support the digital display below the screen on my unit)...
At this point this unit is trash if I can't keep Bluetooth working more than 10% of the time.
Sent from my OnePlus One.
lotherius said:
I can't keep Bluetooth working more than 10% of the time.
Click to expand...
Click to collapse
Some smartphones might show an incompatibility with the radio's BT stack. To be sure try with another smartphone.
I would see if it pairs reliably with just one device at a time. My phone has issues connecting with the HU if I first connect my BT headset to the phone but works fine if I do it after. Also the construction of these seems to be sub-par and it could be the bt device or antenna in yours was not connectec/mounted well and you hit a pothole and now its not attached/broken/loose. It may be worth opening and looking inside for something that broke off or is loose. Finally, I have had (well still have) my factory settings change randomly and have to go in and reset. There are settings in the for BT module and it may be worth looking to see if yours are correct.
I also have problems with mine but I'm running Marshmallow in my OPO. As soon as i go back to Lollipop (CM 12.1) it works again.
stormlabs said:
I also have problems with mine but I'm running Marshmallow in my OPO. As soon as i go back to Lollipop (CM 12.1) it works again.
Click to expand...
Click to collapse
Turns out I think it's the OPO. Mine has issues even with 12.1. I think it's based on Modem version not firmware version. Your modem may have been changed when you went back to 12.1.
For me changing modem versions is something I really want to avoid. I hunted forever for a modem version that didn't constantly drop WiFi and LTE, finally found one, and I think that's when the Bluetooth issues started. Every time I flash a modem to the OPO it becomes a nightmare. That phone really does not want you messing with the firmware which is not what I expected when I bought it.
For now I'm back on my old Nexus 5. No problems. I may just sell the OPO and never stray from Nexus again.
Sent from my Nexus 7 using Tapatalk
Hmmm.
My OPO doesn't connect to the headset but my chinese BT OBD dongle connects fine and works.
I have the same problem with my unit but phone working.Only obd2 adapter some times not connecting.Have you find any solution?
I have a similar issue with the Pixel XL.
Previous I was on a Nexus 5 Bluetooth worked perfectly every time without fail, could make calls, listen to music and sync address book no issue.
Now since moving to the Pixel XL I have an issue connecting to the head unit. The head unit shows as a connected device, but then flashes green then grey, green, grey showing connected, disconnected... I can still stream music from my phone over Bluetooth, but voice is not achievable.
Like suggested it's likely to be the BT stack in the handset rather than the head unit as works fine with Nexus 5. Highly frustrating and likely no fix unless it can be patched by software update
I'm also having the same problem as you noodlemctwoodle on a Nexus 6P with 7.1 developer preview.
I've un-enrolled from the beta program this morning, waiting for the ota to come down, as soon as it does will re-test and let you know if it's working, as I suspect it is a problem with the bluetooth stack in 7.1
MTCD MLT (Xtrons TD618AS) Bluetooth and OBD Reader
I have had issues with the Bluetooth on the MTCD MLT V1.76_1 (Xtrons TD618AS).
I found a work around which allows me to use the OBD reader successfully. I downloaded an Android Bluetooth App and toggled off the Bluetooth. Once the Bluetooth was toggled off I was able to access the OBD reader by using the "Piston" OBD app. I tapped on the car picture and waited for the app to think about things. Once the app finished thinking I was able to start capturing the live OBD data by pressing the play picture. I am only speculating, but I feel as though perhaps the firmware engineers goofed. This is even the OBD reader that Xtrons promoted as compatible with the TD618AS stereo I bought with it at the same time. Not to mention that I continually lose FM radio even though the stereo was professionally installed and no wires were cut. I was very excited, and now only depressed.
mr.hackerly said:
I have had issues with the Bluetooth on the MTCD MLT V1.76_1 (Xtrons TD618AS).
I found a work around which allows me to use the OBD reader successfully. I downloaded an Android Bluetooth App and toggled off the Bluetooth.
Click to expand...
Click to collapse
Which Bluetooth app did you download?
Hi
I have KLD unit that I've used for approx 12 months now without any issues (execpt from me playing with MCU and Firmware upgrades). I also have a reverse cam installed that has been working fine since day 1.
However a couple weeks ago the unit started to behave strangely, while I'm driving forward then the canbus suddenly send reverse cam signal to the unit and the unit goes into reverse mode. However I get the exclamation screen, since there is no live feed on the reverse cam (it's not powered on as it is connected to the reverse lights power source).
If I quickly change to neutral (still driving) and back to drive (automatic), the reverse cam screen disappears and unit works as normal. But after random 3-15 minutes it goes back into reverse cam mode, while still driving or even just standing still.
I've taken the unit out and connected it to a PSU and had it powered on for two days at my desk without any problem, so the unit it self seems in good condition. But when back into the car the problems starts again. Today I decided to disconnect it all wiring as well to check everything and look for any issues. I could not find anything "strange" with the wires.
So I started to play around with the reverse cam wires to see if anything was sending a signal while in neutral or drive. Turns out the orange reverse wire from the canbus is powering up randomly when not in reverse, disconnecting the orange wire from the canbus box takes the unit out of the reverse mode and unit works as normal (of course without reverse cam functionality). Same thing happens when I disconnect the canbus box itself completely, then of course my steering wheel buttons does not work (which they do when the canbus is connected).
I also connected the cam to the video IN and engange reverse gear then the live feed from the cam works fine when in ie. the AVIN app.
After doing all this fiddling and testing. I connected everything back correctly. However now the canbus seemed even more "broken", as it now engange reverse entirely when in P, N and D. And disables the reverse cam feed when actually in reverse
This leads me to the conclusion that the canbus some how has gone foobar. However I have no clue to what to look for. Is there a way to reset the canbus box itself, or do I just need to order a new one?
This is what I've done:
- Verify that all settings in Factory settings where correct
- Checked wiring and the car it self (car is BMW E53)
- Checked cam working and the wiring
- Loaded MCU and firwmare just in case
- Tested unit separate from the car (PSU power), working fine
The unit works fine otherwise.
As a workaround for now, I've disconnected the orange wire from the canbus box and connected the reverse cam video to video in. And just manually start AVIN when I need reverse cam
Hope anybody out here has any idea or clues for what I should look for?
Can these canbus suddenly "go nutes" or die?
Thanks
FxSlin
fxslin said:
Hi
If I quickly change to neutral (still driving) and back to drive (automatic), the reverse cam screen disappears and unit works as normal. But after random 3-15 minutes it goes back into reverse cam mode, while still driving or even just standing still.
Thanks
FxSlin
Click to expand...
Click to collapse
I would rather check the transmitter of the gearbox position. If it has problems it should be recorded as a fault
in your car internal memory. Maybe not in OBD, but deeper. Ask your garage to check the internal memory.
halloj said:
I would rather check the transmitter of the gearbox position. If it has problems it should be recorded as a fault
in your car internal memory. Maybe not in OBD, but deeper. Ask your garage to check the internal memory.
Click to expand...
Click to collapse
So could it be errors that torque is not able retrieve via ODB?
Thanks I'll check that out.
Cheers
FxSlin
fxslin said:
So could it be errors that torque is not able retrieve via ODB?
Thanks I'll check that out.
Cheers
FxSlin
Click to expand...
Click to collapse
Most manufactures have at least two layers, maybe more.
I had something similar. Disconnected the pink cable from the reverse feed on the canbus box and hooked it up to the feed behind the glovebox for the reverse lights instead.
Disconnect the battery for a couple of minutes. That will reset the computer and clear canbus.
If it returns, then the PCM is probably at fault.
cranbiz said:
Disconnect the battery for a couple of minutes. That will reset the computer and clear canbus.
If it returns, then the PCM is probably at fault.
Click to expand...
Click to collapse
Hm, tried this. No go:-/
Better get my PCM checked out.
Could it be that my can bus decoder is broken? Anyone experienced this?
FxSlin
Just an update:
I managed to borrow a can bus decoder box from a friend, who has a similar unit as me.
That one worked fine and I had reverse camera as normal again with his can bus decoder.
So as work around untill I get a new can bus decoder box, I bypassed the can bus reverse cam trigger on the can bus decoder.
I made own reverse trigger wire connected from the reverse camera power and wired it to the unit reverse cam trigger wire directly.
Now its all working as before.
I have the same issue. There is another way to work the CANBus decoder (like any update etc), except to bypass the CANBus with cutting reverse cable. Please help me.
I have the same issue as well. I was in the process of installing the rear view camera, after which, my headunit is now stuck in 'reverse mode'. If i disconnect the ca bus decoder box, the headunit starts functioning without any issues. I can't find any info on how to reset or program the can bus decoder to its factory settings. No idea what to do at this point, other than order a new unit.
Alexg415;74108216 not said:
I have the same issue as well. I was in the process of installing the rear view camera, after which, my headunit is now stuck in 'reverse mode'. If i disconnect the ca bus decoder box, the headunit starts functioning without any issues. I can't find any info on how to reset or program the can bus decoder to its factory settings. No idea what to do at this point, other than order a new unit.
Click to expand...
Click to collapse
I think I have the same problem as you. Did you end up fixing it?
If my Canbus is plugged in, it's constantly in reverse mode. The only way to get back to the regular screen is to unplug the canbus or disable reverse mode in factory settings (in which case, reverse camera is disabled)
Do I need a new Canbus? Anyone know how this would happen and how to avoid it happening again?
Problema camara reversa (CanBus)
Hello,
There is, on the market, CAN-BUS INTERFACE UNIVERSAL ADAPTER INTERVAL CAN-01 / 02SPEED PULSE PARK BRAKES ETC
It is marketed by 'Motor Solutions and' Connects2 '
The CAN-Bus interfaces are designed to turn this digital data into analog, so the installation of an aftermarket car radio becomes simple. The interface creates the following for you, and saves you time and money in the process:
Speed pulse signal
Ignition Wire
Lighting wire,
Reverse wire
Park Brakes
I think it applies to 'made in China' radios, but they should consult the sellers
Regards
Mário
essarr427 said:
I think I have the same problem as you. Did you end up fixing it?
If my Canbus is plugged in, it's constantly in reverse mode. The only way to get back to the regular screen is to unplug the canbus or disable reverse mode in factory settings (in which case, reverse camera is disabled)
Do I need a new Canbus? Anyone know how this would happen and how to avoid it happening again?
Click to expand...
Click to collapse
not solved?
posted in the wrong place , mtce unit
I have a MTCB-KLD-V2.86 Android 4.4
I have just installed a https://my-fobo.com/Product/FOBOTIRE
This tyre monitoring unit runs from an app.
I have the main app on my smartphone and it works with no problems.
Fobo has the ability to share with another device that also has the app.
The problem is, my head unit can't locate the bluetooth tyre sensors.
I have checked with a Bluetooth Low Energy search app, and it does not find the bluetooth sensors.
The manufacturer of Fobo believes that it may be due to the BT antenna being at the back of the head unit, I have no idea if it is or not?
I wasn't aware that there were different signals/types of bluetooth, never heard of BT Low Energy before.
I don't have any problems connecting my phone and OBD adapter via bluetooth, just these sensors.
Is bluetooth upgraded in different android versions, such as 5.1.1 or is it a definite hardware thing?
Hi,
I have a Seicane PX5 for 2009 Toyota Avensis. I have upgraded to Hal9k 4.10 and upgraded MCU to MTCE_MX2_V3.56. (it came with MTCE_MX2_V2.88).
Everything else works fine but the unit is supposed to switch and display rear camera when it detects that reverse is engaged. However nothing happens.
Camera is connected to "Camera in". Also it does not seem that either of the two wires with "Reverse" on give any voltage when reverse is engaged.
Camera works fine as I tested in aux-video in.
The system is also supposed to switch to "Camera in" when it detects videosignal on there (according to seicanes website).
Anyone have a similar problem or any tips?
Try manually feeding +12v to the reverse trigger wire (orange wire on Dasaita.. not sure about siecane) on the head unit and see what happens.
Thanks for a good idea!
There are two cables labeled "Reverse". One goes into the "AVIn/out" the other comes out of the "ISO-port".
When I trigger the one from AVI with 12v it switches to the camera input.
When I trigger the on on the ISO-port with 12V it also switches to camera input.
So that one must be two reverse-triggers?
The one from the ISO-port I assumed is supposed to go to +12V when reverse is enabled but it does nothing when reverse is enabled (measured with voltmeter).
I do not seem to be getting any voltage from "Cam power" either (which I assume is to go high when reverse is enabled).
I have set this up with the supplied wireless receiver and transmitter and according to the manual from Seicane it should automatically switch over when reverse is enabled or it detects something on the input.
When I run it from the 12 directly and trigger either of the "reverse"-cables it displays the rear image perfectly.
Problem is that I cannot trigger either of the "Reverse"-wires as it is now.
Is it a problem with the MCU-version? I guess I can connect an extra trigger via wire from the reversing lights. but it is extremely hard to get wires into rear hatch (stationwagon ).
Any other ideas?
Solved it by routing +12v from reversing lights to the "reverse"-trigger wires.
I recently installed a Xtrons PQS90MTVL head unit in a skoda superb. I have a couple of questions on how to get it to work correctly when navigating.
1) It seems that you can set the navigation sounds to be a percentage of the radio volume but cannot set it to play at a given volume regardless. The problem is that the radio seems to be constantly on and there is no way to turn it off. The 'on/off' button simply mutes the radio - and the navigation sounds.
Often I am in an area where I cannot pick up a decent radio signal on the programme I want and just get static. In these situations I want to turn the radio off but still hear navigation sounds. I don't want to listen to loud static just so I can have the nav sounds play at a percentage of that static. Is there a way to turn the radio off but still get navigation sounds? (a workaround I have found is to play a media file instead of the radio and then pause playback. The nav sounds are then still a percentage of the - non existent - playback volume. However this should not be necessary)
2) It also seems that a Internet connection is needed for any navigation. even google maps won't do a search without it as it says I am offline. (is this true?)
I have bought the 4G wifi dongle but have a question about its use. Does the HU connect to the dongle, as far as data is concerned, via the USB socket that comes out of the back of the unit or is that socket simply powering the dongle and the HUI is actually connecting to it over wifi using the dongle as a hotspot? If so then I don't have to use the wired usb socket from the unit (which I suspect is underpowered) and can plug the dongle into an ordinary 2A USB socket that I have in the car, positioning the dongle near the roof for a better signal
Incidentally I did try using Android Auto with my phone using wired connection. That seems sort of OK but is not very reliable. Often when starting the car it hangs at the 'connected' screen, or even at the 'trying to connect' screen, although other times it seems OK
3) There is a small socket on the left hand side of the HU that looks like a slot for a small memory card or a sim card. It is labelled 'GPS'. What is that socket used for? it is not mentioned in the manual as far as I can see. - The manual is generally a bit hand waving though, excitedly telling you what you can do but not how to do it.
(I did try the xtrons forum but not only are the last posts there around January 2022 but there seems to be no way to register for it. Hence posting here)
Is it MTCx post system info including mcu version.
Mtcb is long retired
marchnz said:
Is it MTCx post system info including mcu version.
Mtcb is long retired
Click to expand...
Click to collapse
All I know is the model is Xtrons PQS90MTVL so maybe its MTVL (whatever that is) I'm afraid I don't know what mcu means so cannot offer any version for it. Its possible I have posted this in the wrong section and have rep[osted in 'Android Head-Units'. If that is the right place and this is the wrong place, please can you delete this post