Hey guys so I have an Alfa 159 and bought one of these head units:
Edit i cannot post a link however its the generic A-media Auto alfa 159 head unit which can be found on google
now I was speaking with a friend of mine who explained that the roms are "cut back" and removes some features and full blurtooth control/ support is one of them
I am reasonably ok with computers but never ventrued into any sort of custom android stuff and the extend of my knowledge is " i know you can get custom roms" i hdon't know how to do them or use them etc.
I have some bluetooth modules i can control from my phone in the car (lighting and actuators) but would love to be able to do it from the head unit
Would it be possible to get a custom rom for this head unit and if so any guides at all?
I would like to point i did have a search but honestly i am not totally sure what I am searching for and searching sepcifically for this head unit didnt help.
Thank yoiu very much
It's not so much that the ROM removed bluetooth features as much as it is how the bluetooth module is integrated to the HU. There's 2 system boards that make up the HU. The SoM has the Android system and is basically a tablet motherboard with only a display, audio and USB connection. The MCU provides a USB hub, audio preamp and power amp, connectivity to the car and the bluetooth module. The bluetooth module is treated as a headset controlled through a serial connection with AT commands and this is where the problem lies with using bluetooth with any apps other than the built in ones. It works for ODB dongles so it is possible but if the functionality you're looking for is not already implemented I doubt someone else would be able to add it to the MCU ROM. All I can say is try and see if it works.
Maybe you can try to connect a USB bluetooth dongle the issue here would be Android drivers.
nic2k said:
It's not so much that the ROM removed bluetooth features as much as it is how the bluetooth module is integrated to the HU. There's 2 system boards that make up the HU. The SoM has the Android system and is basically a tablet motherboard with only a display, audio and USB connection. The MCU provides a USB hub, audio preamp and power amp, connectivity to the car and the bluetooth module. The bluetooth module is treated as a headset controlled through a serial connection with AT commands and this is where the problem lies with using bluetooth with any apps other than the built in ones. It works for ODB dongles so it is possible but if the functionality you're looking for is not already implemented I doubt someone else would be able to add it to the MCU ROM. All I can say is try and see if it works.
Maybe you can try to connect a USB bluetooth dongle the issue here would be Android drivers.
Click to expand...
Click to collapse
Thank you, sorry for late reply.
A friend of mine figured out with his that it was "nuked" in the software allegadly. the bluetooth module is a generic module but unfortunatly I am not massivly clued up on reflashing roms or even where to start especially on a head unit which is a shame.
My friend unfortunatly has since moved country so I can no longer ask him to take a look
I don't suppose anyone else might have an idea to this?
this comes up often apparently nobody give f*ckall to address this issue.
^ Thats a real shame
Craigrobbo said:
^ Thats a real shame
Click to expand...
Click to collapse
i know, my radio is great, does everything great. I just want to connect bt to my ham radio and use this as the head unit. and I was thinking about using those bluetooth valve stems so i can see the air pressures in my tires, looks like those wont work either.
ChiefWilNel said:
this comes up often apparently nobody give f*ckall to address this issue.
Click to expand...
Click to collapse
Have you considered that these units work for the intended use and if it doesn't work for some obscure use case the desire to solve a problem for single users is limited. To expect others work on an obscure problem for you seems a bit entitled.
Have you considered taking the lead on this issue.
Bumping to see if ANYONE has came up with a solution, maybe an external dongle?
Related
hi guys
new to the forum, hopefully someone will be able to help me
my unit has stock MTCC-KLD6-V2.97 Aug 02 2016 with a RK3188 and 1024x600 screen
Firstly the Bluetooth is not working, quite a lot of apps hang at the part where it try's to turn the BT on, especially one app i really need to work.
I honestly don't know what model of BT chip is installed in the head unit, apparently its BT 4.0 as listed on there website
I have been into the factory menu and changed the BT from WQ_BC6 to WQ_BC6B (as suggested somewhere in this forum) but it has made no change and the BT is still hanging at powering on.
Eonon have told me that the Bluetooth only work with devices that don't require a pin and the radar detector device i need to connect does not require a pin but still it does not work.
Not quite sure if eonon has set the setting wrong and i need to change it or i need to goto a custom rom or I need to pull the unit apart to find out.
Found someone else having trouble getting there ALPconnect app to work aswell on these units, in know ALPconnect wont work on older unit like the 4.4.4 as they only had BT 2.0 and the ALP BT only supports 4.0, but this android unit has 4.0 so it should not be a problem but it is.
sterod said:
The app I use, ALPConnect, does the exact same thing. Fortunately, the hardware on mine includes a hardwired speaker and GPS setup that work standalone. The benefit of the app was to get a nice big visual notification of a trap, as it would come into focus, duck the audio and play an alarm. It would also report the frequency of the radar and the type of laser hitting me. While I can get by without all that, I can't have the music blaring like I usually do, as the little speaker is only so loud and the Joying head unit doesn't have Mute Input wire to duck the audio.
While this is going slightly off topic, you may want to look into the AL Priority, it can interface with your V1 too and you will also gain laser protection. This thing has saved my a** countless times and paid for itself already many times over.
Click to expand...
Click to collapse
Secondly the control menu in the android head unit for accessing the cars buttons via cambus does not work, all steering wheels button seem to communicate back and work, but i cannot set my clock on my mazda 3.
Also have noticed that the radio wont mute when notification occur or when using other apps like google maps, no way to set the different volumes in this stock rom. Have played around with the factory menu volumes but it makes no diffidence.
Is it viable and worth changing to a different ROM, like Malaysk? or should i message eonon?
any help would be much appreciated
thanks
shane
I'm having exactly the same issue with a Pumpkin MTCC-KLD6-V2.91. (RK3188/1024x600)
The device I want to pair with appears in Bluetooth settings (with a phone icon?) but connecting to it does nothing. It's just a Bluetooth SPP device, like so many other devices.
Malaysk's ROM (from 7/25) doesn't change anything here.
Any suggestions would be most welcome.
-Zandr
zandrm said:
I'm having exactly the same issue with a Pumpkin MTCC-KLD6-V2.91. (RK3188/1024x600)
The device I want to pair with appears in Bluetooth settings (with a phone icon?) but connecting to it does nothing. It's just a Bluetooth SPP device, like so many other devices.
Malaysk's ROM (from 7/25) doesn't change anything here.
Any suggestions would be most welcome.
-Zandr
Click to expand...
Click to collapse
Waiting on a reply from Eonon, but initial news is not good.
Some serious BT issues in this model the MTCC
Anyone know if any Malaysk's Rom's avalable for the MTCC-KLD6-V2.91 that have no BT issues
I'm having the same issue, though my unit (MTCC KLD6) does not show any devices at all to pair with, and the car unit does not appear on my phone.
I'm wondering - if I take a usb BT dongle and attach it to the usb cable, would that work?
I think it might be another issue with your BT, it should connect to your phone at very least.
Have you had a look in your factory menu to see if the MCU has the Bluetooth option set?
Password for me was 126
Unfortunately the unit does not support external USB Bluetooth and probably never will, unless the manufacturer MTC/Klyde adds the required drivers to the unit or a Awesome developer by some stroke of luck here adds it to the unit. I doubt to see the feature in this unit
Sent from my iPhone using Tapatalk
Thanks for the reply. Yes, i checked to make sure Bluetooth was enabled in the system settings. I've tried a few of them (change setting, reboot, attempt pairing), i guess the next step is to try them all one by one to rule that out. I've sent an email to the seller to see if they have any ideas.
The vendor told me to connect the Key-1 & Key-2 wires from the canbus to the car, not sure why they'd think that would solve BT issues?
Did this fix the issue? I'm unable to see any Bluetooth devices and other Bluetooth devices don't see it.
Sorry to dig up an old thread
I have the Eonon GA2180a (android 10) - and having similar issues to here
I want to pair a bluetooth remote (read, steering wheel controls) to the head unit, but the bluetooth search just shows blank! I can connect to it using my phone but it appears some things are hidden to connect to with these android units? Looks like the bluetooth 'app' is the only way to connect too, theres nothing in the android settings to access a bluetooth menu or anything.
Did anyone get anywhere with this ?
cheers
Hi
I am currently using Parrot Asteroid Smart, generally I am satisfied with the unit, sound quality is great, BT and other features works good, but the HW is old and max. Android version is 2.3.
I'm thinking about upgrading to newer android and the only possibility I see is one of chinese 2din HU like Ownice C500.
Does anyone have experience if they are any cons of such change? What is the sound quality of C500 compared to Smart?
Any info would be appreciated.
ee0090 said:
Hi
I am currently using Parrot Asteroid Smart, generally I am satisfied with the unit, sound quality is great, BT and other features works good, but the HW is old and max. Android version is 2.3.
I'm thinking about upgrading to newer android and the only possibility I see is one of chinese 2din HU like Ownice C500.
Does anyone have experience if they are any cons of such change? What is the sound quality of C500 compared to Smart?
Any info would be appreciated.
Click to expand...
Click to collapse
I am in the exact same situation. I was happy with the PAS at first, but it became outdated and frustrating very quickly - the lack of apps supported natively, the lack of ram and storage. Even after rooting and installing Google Play store there are so many apps that can't be run on 2.3. Positives though are that the Bluetooth call quality and voice command is in my opinion unmatched.
I have since bought an Eonon Android unit (rooted and installed Malaysk rom) for my wife's car and the interface is great, the sound is reasonable and the app support is great. The Bluetooth however is terrible, to the point of being unusable, the person on the other end can either not hear or suffers from major delay. This is a known problem with nearly ALL Chinese Android head units and there is a hardware mod but not being very confident in opening the unit and performing the mod properly and potentially voiding warranty is a risk I'm yet to take with it. I also have an issue where the physical volume control knob stops working and sound can only be adjusted on-screen, this is usually fixed with a reboot.
I still have not found a reliable unit to replace the PAS in my car after reading numerous threads that has Bluetooth quality on par with the PAS. Hopefully someone else here can recommend a decent unit?
Joying 2GB Intel is the way to go
CadillacMike said:
Joying 2GB Intel is the way to go
Click to expand...
Click to collapse
Why?
look over some of the various threads on XDA, and feel free to check out the official Joying forum - http://forum.carjoying.com/
For the most part i think Joying gets the least amount of negative feedback, they tend to have pretty good customer service, and they seem to so somewhat monthly updates. I have had the older 1gb model and I currently have the newer 2GB of RAM model, and I'm a big fan:
here is a video review
https://www.youtube.com/watch?v=KzGFDwSFj24&feature=youtu.be
https://www.youtube.com/watch?v=IUP4WGYHIaQ
but dont take my word for it, like I said, if you spend some time reading, you'll see a lot of the other head units have their fair share of bugs and complaints
If you want a fully functional BT interface, go with the Intel 2GB Joying head units. I think they are the only ones with a full stack BT interface available, the other Rockchip based units seem to have a somewhat hacked in BT interface which is limited compared to a full native interface, specially when it comes to how the Android OS can access and control it.
Install the apk from this thread and you have access to the standard Android BT settings screen, it is normally hidden in the Settings app but luckily it's not removed.
https://forum.xda-developers.com/an...elopment/bluetooth-settings-launcher-t3504526
Hilari0 said:
If you want a fully functional BT interface, go with the Intel 2GB Joying head units. I think they are the only ones with a full stack BT interface available, the other Rockchip based units seem to have a somewhat hacked in BT interface which is limited compared to a full native interface, specially when it comes to how the Android OS can access and control it.
Install the apk from this thread and you have access to the standard Android BT settings screen, it is normally hidden in the Settings app but luckily it's not removed.
https://forum.xda-developers.com/an...elopment/bluetooth-settings-launcher-t3504526
Click to expand...
Click to collapse
Thanks for the info
Few questions:
What is the BT handsfree quality with external mic installed?
Does the radio display station names? Does RDS and AF work correctly?
What is the general sound quality?
Does WiFi module connect with 4G router?
I use the head units wifi to connect to my phone as a wifi hotspot. Works great. BT handsfree with external mic is very good, at least according to those I talk to, I haven't been on the "receiving end" yet..
The sound quality is good, I'm still using the OEM speakers and they sound better with this head unit compared to the OEM head unit. Can't confirm on radio as I actually don't use it much... It does have RDS it seems, but don't know if it works or not. (radio where I live is garbage, nonsense content and music seems limited to whatever the top 20 list is...)
Hilari0 said:
I use the head units wifi to connect to my phone as a wifi hotspot. Works great. BT handsfree with external mic is very good, at least according to those I talk to, I haven't been on the "receiving end" yet..
The sound quality is good, I'm still using the OEM speakers and they sound better with this head unit compared to the OEM head unit. Can't confirm on radio as I actually don't use it much... It does have RDS it seems, but don't know if it works or not. (radio where I live is garbage, nonsense content and music seems limited to whatever the top 20 list is...)
Click to expand...
Click to collapse
Thank you for the info. Which version do you use? I can see there are 3 different versions of 7" universal unit with the same hardware. The difference is that two of them have volume knob and the 3rd only touchscreen.
Hilari0 said:
If you want a fully functional BT interface, go with the Intel 2GB Joying head units. I think they are the only ones with a full stack BT interface available, the other Rockchip based units seem to have a somewhat hacked in BT interface which is limited compared to a full native interface, specially when it comes to how the Android OS can access and control it.
Install the apk from this thread and you have access to the standard Android BT settings screen, it is normally hidden in the Settings app but luckily it's not removed.
https://forum.xda-developers.com/an...elopment/bluetooth-settings-launcher-t3504526
Click to expand...
Click to collapse
Both MTCD and Joying INtel have positive and negative feedbacks....
In terms of BT performance....both have BT Limited to MCU. Even you could pair from the BT standard menu, the functionality is limited. If i am not wront (correct me) both units CAN'T perform CALLS from BT by using google Now. Google Now recognizes correctly the name and it seems to start the call but never is initiated as it can not communicate with the real bluetooth Handsfree on the Headunit.
On the Intel units, the BT and wifi hardware is on the same board as the CPU, Android has full access to it. That is not the reason Google Now can't make calls. This is different on the MTCD units where the BT is a module which is sort of hacked in and Android doesn't have full access to.
I have bought Joying with Intel. BT handsfree works fine, although there are some other problems:
- no voice in Google Maps,
- when listening to the FM radio no voice output from nav apps except of Igo,
- I have connected Alpine active sub to the unit, sub works fine for first few minutes and stops, any idea why and what can be done about it? Sub worked great with Parrot, so it must be some issue with Joying.
ee0090 said:
I have bought Joying with Intel. BT handsfree works fine, although there are some other problems:
- no voice in Google Maps,
- when listening to the FM radio no voice output from nav apps except of Igo,
- I have connected Alpine active sub to the unit, sub works fine for first few minutes and stops, any idea why and what can be done about it? Sub worked great with Parrot, so it must be some issue with Joying.
Click to expand...
Click to collapse
I think if you change default nav app to your preferred one, you'll get voice output in FM radio.
For the sub - is the amp still ON after a few minutes when it stops? I have an active sub on mine and have no issues. I'd check on what your source for "on" signal on your amp is.
Google maps voice output doesn't work no matter what I do. As a default nav app neither.
Sub is powered and it works with very low volume settings, ad soon as I turn the volume up it stops working.
ee0090 said:
Google maps voice output doesn't work no matter what I do. As a default nav app neither.
Sub is powered and it works with very low volume settings, ad soon as I turn the volume up it stops working.
Click to expand...
Click to collapse
We got Google voice output working. Look into the forum.
Strange. Maybe I should reset the unit to factory settings. Reinstalling google maps did not help.
Any idea what is wrong with the sub?
ee0090 said:
Strange. Maybe I should reset the unit to factory settings. Reinstalling google maps did not help.
Any idea what is wrong with the sub?
Click to expand...
Click to collapse
(have seen a few oem ones) if so it would be hooked up with the sub RCA output ? Is the amp powering down ??
If so try hooking the remote line on the amp to an 12v acc line instead. (This is no different to the headunit remote 12v output just that if you switch the head unit off the amp is still powered on , this could eliminate a headunit problem ?)
ee0090 said:
Strange. Maybe I should reset the unit to factory settings. Reinstalling google maps did not help.
Any idea what is wrong with the sub?
Click to expand...
Click to collapse
As wrx216 said. I think it might be bad wiring. try a different SUB "ON" source. For example, I tap in the + wire of my rear speaker as the power on signal for the sub amp.
Google maps voice output still does not work. I did factory reset - it did not help.
I have updated the firmware and google maps voice works fine. But sub does not work at all now.
I have connected remote wire of the sub to constant +12V output (the same as amp. power supply) - it still does not work. I have also tried to change RCA input of the amp. - still nothing.
Hello xda people!
I recently purchased an eonon head unit for my E46 316i from ebay. Specifically a GA6150 (rk3188), which was sold together with a reverse camera.
I am really happy with my order, and pleased with the HU's performance. I managed to connect succesfully my OBD adapter, my bluetooth phone and my wifi hotspot and all is working great.!
Although, I found out something which bothers me. I have purchased a Bluetooth RGB LED controller from ebay, in order to DIY install some LEDs in the interior of the car, and I wanted to control them from my eonon android HU. I can control them through my S7 Edge Android phone via the app called Happy Lighting. I have found out that the manufacturer of these controllers is called Triones. So my problem is, that when I open the app, it asks me to turn on the bluetooth, and allows me to press one of two buttons, allow and deny. If I press allow, a message will appear saying: "Turning on Bluetooth" or something like that, with a spinning wheel, indefinately. It will not stop and it will stay like this all the time, making the app useless, making me press home button to exit. All this happens, even though I know that bluetooth is actually on (I havent yet found an on/off switch for Bluetooth, so I suppose it is always on). If I press deny, then I can enter the app, but I am not able to see any of the bluetooth controllers, is there any way, to make the app think that the bluetooth is on? Or actually turn it off or anything? Would you please help me figure out what should I do? And one last question, is how can I change my screen orientation from landscape to portrait?
I will attach a photo of the details for the version of my Head Unit.
This is the link of the HU I purchased from ebay: http://r.ebay.com/aegMSa
And this is the link to the controller: http://r.ebay.com/aDfflI
While this is the app: https://play.google.com/store/apps/details?id=com.qh.Happylightgoogle&hl=en
Thank you very mych for your time!
Yep had 3 Paypal disputes with Eonon about that issue a year ago on a MTCB unit, I would imagine it would be the same with the MTCD
I think they route all Bluetooth information through the MCU and use non standard configuration of their Bluetooth drivers. So applications that ask to turn the BT on cannot as it is not configured that way.
This is something they were not willing to fix or were unable to.
Sent from my iPhone using Tapatalk
First of all thank you for your reply, i really appreciate it.!
Second, damn it. Damn them! That is really frustrating, i've managed to find a bit more info digging around here and in russian forums. It's sad that i cannot use anything else via bluetooth other than a few OBD adapters and my phone..
I will shortly contact Eonon for my MCU update file and see if anything can be done there. Otherwise, i will see if anything can be fixed via a custom rom and xposed stuff.
P.S.: If there was any other android HU that could support full BT, i would gladly return my Eonon and buy that instead..
DeejayTelis said:
First of all thank you for your reply, i really appreciate it.!
Second, damn it. Damn them! That is really frustrating, i've managed to find a bit more info digging around here and in russian forums. It's sad that i cannot use anything else via bluetooth other than a few OBD adapters and my phone..
I will shortly contact Eonon for my MCU update file and see if anything can be done there. Otherwise, i will see if anything can be fixed via a custom rom and xposed stuff.
P.S.: If there was any other android HU that could support full BT, i would gladly return my Eonon and buy that instead..
Click to expand...
Click to collapse
Joying intel Sofia units is a bit better with the BT, but do some research first.
Good luck with Eonon
From memory it to do with kernel drivers and BT stack and they would not fix
Also be careful with Eonon and returns, additionally PayPal protection does not cover car audio products.
Sent from my iPhone using Tapatalk
shanetrainST said:
Joying intel Sofia units is a bit better with the BT, but do some research first.
Good luck with Eonon
From memory it to do with kernel drivers and BT stack and they would not fix
Also be careful with Eonon and returns, additionally PayPal protection does not cover car audio products.
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse
Digging up an old thread
I would like to connect bluetooth accessories to my eonon new android 10 head unit (2020) - the above looks familiar as i cannot seem to 'find' the devices when searched for using the strange bluetooth 'app'.
Is there anything that can be done? I'd like to add a bluetooth remote (alternatiev to steering wheel controls) - but its not detected by the HU
Hi All,
Recently purchased and installed a Joying head unit (4GB, PX5 Octa Core) (link to product)
As this head unit runs android I am trying to tether the mobile data on my android mobile over to the head unit via the bluetooth tethering function. Problem is I dont think its working. Does anyone have any experience with this or know how to get it working?
Steps:
On the mobile, make sure its connected to mobile data
On mobile, turn on bluetooth tethering
Pair mobile and head unit via bluetooth
Still no internet access
Can you access data via hot spot? Make you mobile device a wifi hotspot and connect the headunit to your hotspot.
Sent from my ONEPLUS A5010 using Tapatalk
chper said:
Can you access data via hot spot? Make you mobile device a wifi hotspot and connect the headunit to your hotspot.
Click to expand...
Click to collapse
Yeah I tried this and it works fine. I just though it be better to use bluetooth tethering seeing as the phone is already hooked up to the head unit via bluetooth. Using the WiFi hot spot option just adds another process to the mix.
Because Joying remove a lot of the standard android setting I was thinking there might be a way to access the default android settings again to be able to play around with bluetooth properly. While writing this thread up however I did email Joying about the ability to bluetooth tether and their response was:
"Our head unit can not support Bluetooth tethering"
Hi, I am trying to achieve the same solution however I do not think it's possible. My understanding is that the bluetooth connectivity allowed by the hardware in the head units doesn't cater for the 'full stack' of bluetooth functions, so we're stuck with telephony and audio only with no data transfer.
I would *really* love to be corrected though! It would be great if it could be solved by software alone.
Failing that, could a bluetooth USB dongle work to provide full BT support?
proto__ said:
Hi, I am trying to achieve the same solution however I do not think it's possible. My understanding is that the bluetooth connectivity allowed by the hardware in the head units doesn't cater for the 'full stack' of bluetooth functions, so we're stuck with telephony and audio only with no data transfer.
I would *really* love to be corrected though! It would be great if it could be solved by software alone.
Failing that, could a bluetooth USB dongle work to provide full BT support?
Click to expand...
Click to collapse
I consider this a bug. It did work on the Sofia 3GR units on Android 6.0.1.
It (currently) does not work on the Android 8 PX5 FYT units (like the OP has as well). Can't say anything about the QD units.
Well that gives me some hope at least.
I did note at least 3 'Bluetooth' apps running on my device (that I've been playing with since my previous post).
Perhaps a custom mod may be the answer...
Sorry proto, I've had about five units and all the same. You're right and it sucks. I don't think it's a big as I've come across it many times and only in a few eBay postings did the seller actually specify it has a general bluetooth connection. Otherwise toy even have to buy their obd to get that to work
Sent from my SM-G950U using Tapatalk
Ok thanks for the replies. Hopefully it will be fixed with a firmware update in the future or something.
Is there are any news about this Bluetooth tethering?
I am really interested because my WiFi is really really slow...
I saw that some Bluetooth function are missing, like the possibility to remove paired device or select Bluetooth tethering.
It’s highly unlikely Joying will fix the Bluetooth, they would need to produce a seperate rom with normal BT configured and u would not have access to the Joying BT app.
Currently Joying route all Bluetooth communication via a service called btlink, from there it goes to the joying bluetooth app.
Joying have fundamentally changed the way the Bluetooth is configured so it functions with only their software.
All these headunit manufactures do this to the BT so it functions with their software and they never offer a fix
shanetrainST said:
It’s highly unlikely Joying will fix the Bluetooth, they would need to produce a seperate rom with normal BT configured and u would not have access to the Joying BT app.
Currently Joying route all Bluetooth communication via a service called btlink, from there it goes to the joying bluetooth app.
Joying have fundamentally changed the way the Bluetooth is configured so it functions with only their software.
All these headunit manufactures do this to the BT so it functions with their software and they never offer a fix
Click to expand...
Click to collapse
From which library/framework/binary/whatever is this btlink service started/called?
surfer63 said:
I consider this a bug. It did work on the Sofia 3GR units on Android 6.0.1.
It (currently) does not work on the Android 8 PX5 FYT units (like the OP has as well). Can't say anything about the QD units.
Click to expand...
Click to collapse
Remember that it only worked with a HACK. Joying intentionally disables this functionality.
Bluetooth information
Init.sy.rc
Service blink /vendor/bin/blink
Init.connectivity.rc
Chmod 0666 /dev/tty (This should be tty00)
Now I have modified mine but I think the system/vendor/ect/Bluetooth/bt_vendor.conf is set to
- UartPort = /dev/tty00
Blink is interacting with /dev/tty
Android system is interacting with /dev/tty00 ?
Hopefully all the information is correct as I have modified my unit lots to try give back the Bluetooth to the system and I didn’t keep many notes.
But in short the the system is trying to access the Bluetooth on the wrong Uart port, where as the blink is attaching to the tty device, allowing the joying software to work.
This prevent the android system & apps interacting with the Bluetooth.
Also this is the test app I have been using to try to get it to allow permissions to turn BT on, but it get denied every time
Bluetooth Discovery : Bluetooth LE Scanner
https://play.google.com/store/apps/details?id=com.manjul.bluetoothsdp
i have the 10.1 american version.
if i remember correctly, bluetooth has an issue when your using it as a "media" access point
i think the bluetooth is set for A2DP... probably physically somehow.
shanetrainST said:
Init.sy.rc
Service blink /vendor/bin/blink
Blink is interacting with /dev/tty
Android system is interacting with /dev/tty00 ?
Also this is the test app I have been using to try to get it to allow permissions to turn BT on, but it get denied every time
Bluetooth Discovery : Bluetooth LE Scanner
https://play.google.com/store/apps/details?id=com.manjul.bluetoothsdp
Click to expand...
Click to collapse
Did you try to create a symlink like
Code:
ln -s /dev/tty /dev/tty00
And is it indeed tty00 or tty0?
Did you give the scanner root access?
Bumping this for a slightly odder issue. I'm trying to connect my Joying stereo to a Hondata KPro ECU, it sees the ECU but refuses to link to it in settings, rendering apps like Hondata or RealDash useless, so in turn I'm using a crappy $20 tablet until someone can show how to fix this BT issue.
Joying was no help other than to tell me to buy their OBDII adapter, which I did, but LONG story this is a 2008 Honda engine in a 91 MR2 that has no OBDII port. I've bought an OBDII port off eBay and tried using pinouts from the ECU to hack together an OBDII port but no luck.
Having it via Bluetooth would be easier, it sees the KPro, so there must be a way.
same problem
dont buy this joying head unit
its rabish
Hey,
I have been using an ownice c200 up until last year, when the unit let out the smoke and died. I am using the original RNS510 and that thing is driving me nuts… I am thinking of buying a new unit and have been browsing the forums here to find answers to the issues I will run into. It seems that to turn on the sound system and use the camera I would need 2 more special can adapters.
When I installed the ownice unit I did draw up a pcb with an rgb-composite converter but never came about to build it. Not having the camera was only a pain when I did hook up my trailer…
To turn on the amplifier I built a little µC box with a CAN Interface, debugged the bus with the original headunit in and then wrote a simple program that listens to specific commands, turns on the amplifier and also keeps it turned on. My intention by then was to find a way to send the commands via the CAN bus adapter that came with the c200 but since that little box in my glove compartment did the trick I never got around to investigate further. Also I am no andriod expert...
From what I have found here the communication to the CAN adapter is done via a serial interface. There are no actual can frames transmitted and all the filtering and conversion is done in the adapter. Maybe someone can point me to threads dealing with the CAN adapters. Has anyone here done a custom CAN Interface? Can you configure that interface to listen to more IDs? Can you get the raw CAN data from the interface?
My ultimate goal would be a can interface that gets configured via the headunit and then just forwards the commands in both directions. The rest would have to be done in software on the headunit.
Cheers,
Christian.
LumpiZupf said:
Hey,
I have been using an ownice c200 up until last year, when the unit let out the smoke and died. I am using the original RNS510 and that thing is driving me nuts… I am thinking of buying a new unit and have been browsing the forums here to find answers to the issues I will run into. It seems that to turn on the sound system and use the camera I would need 2 more special can adapters.
When I installed the ownice unit I did draw up a pcb with an rgb-composite converter but never came about to build it. Not having the camera was only a pain when I did hook up my trailer…
To turn on the amplifier I built a little µC box with a CAN Interface, debugged the bus with the original headunit in and then wrote a simple program that listens to specific commands, turns on the amplifier and also keeps it turned on. My intention by then was to find a way to send the commands via the CAN bus adapter that came with the c200 but since that little box in my glove compartment did the trick I never got around to investigate further. Also I am no andriod expert...
From what I have found here the communication to the CAN adapter is done via a serial interface. There are no actual can frames transmitted and all the filtering and conversion is done in the adapter. Maybe someone can point me to threads dealing with the CAN adapters. Has anyone here done a custom CAN Interface? Can you configure that interface to listen to more IDs? Can you get the raw CAN data from the interface?
My ultimate goal would be a can interface that gets configured via the headunit and then just forwards the commands in both directions. The rest would have to be done in software on the headunit.
Cheers,
Christian.
Click to expand...
Click to collapse
It sounds like you're mostly done with the hard part of the job already.
My suggestion would be to avoid trying to interface with the chinese radio, but rather to work around it using as much as you can of custom code.
From what I gather, you already are able to "send" most/all of what you need with your little uC rig, but now you probably want to send commands back to the radio, right? The best way to do that would be to implement an HID keyboard on the microcontroller. Just plug the uC into the USB, the radio recognizes it as a keyboard, and you can send in commands, like volume+/-, etc.
Note that you can use the standard outputs from the radio (like the AMP ON, ANTENNA ON, CAMERA ON, which are just 12v binary signals) to feed that data out to the microcontroller.
The reason behind all this is to get rid of all the extra canbus decoders to get everything working. I already had to put my can node inside the glove box because I could not fit it behind the radio. Since the unit can send and receive commands, why not write the software for the headunit instead the microcontroller. That way also others might benefit from it and it would be possible to play with the MFD.