Related
Has anyone tried it? Woul'd it work with our phone?
One does not simply send from a XDA-app.
kekio84 said:
Has anyone tried it? Woul'd it work with our phone?
Click to expand...
Click to collapse
I use along with the Motorola Bravo. everything works.
rasto4nik said:
I use along with the Motorola Bravo. everything works.
Click to expand...
Click to collapse
Thanks,but i asked if it works with O3D.
One does not simply send from a XDA-app.
Yes, works for me with torque pro on p920.
blackpitbull said:
Yes, works for me with torque pro on p920.
Click to expand...
Click to collapse
Thank you very much for the info. Thats great news. Which diagnostic bt adapter did you buy for yoyr car. I'm driving a FIAT Punto II. And not every adapter is compatible,but most of them are.
Sent from my LG-P920 using xda app-developers app
I can confirm it as well, would see no reason why it wouldn't work, worked with my previous smartphone as well.
I got one of these cheaper ELM327 bluetooth adapters, plug it in, add the adapter in the bluetooth list (Pass is probably 1234) start Torque, add the details of your car and don't forget to turn the ignition to on
chrisxt said:
I can confirm it as well, would see no reason why it wouldn't work, worked with my previous smartphone as well.
I got one of these cheaper ELM327 bluetooth adapters, plug it in, add the adapter in the bluetooth list (Pass is probably 1234) start Torque, add the details of your car and don't forget to turn the ignition to on
Click to expand...
Click to collapse
Hello , i recently bought an elm327 adapter but i cant pair it to my phone (lg p970 running ICS).
I tried every code i could think , like 1234,1111,0000,5555,6789,5678 etc , but still nothing.
The phone can find the adapter (with name : OBDII),but says the pin is wrong.
Is there a special trick to pair them?:crying:
Gas_OB said:
Hello , i recently bought an elm327 adapter but i cant pair it to my phone (lg p970 running ICS).
I tried every code i could think , like 1234,1111,0000,5555,6789,5678 etc , but still nothing.
The phone can find the adapter (with name : OBDII),but says the pin is wrong.
Is there a special trick to pair them?:crying:
Click to expand...
Click to collapse
You might want to take a look at the cd you got with the adaptar.
all the codes you just said are the ones I would use as well, for me it was 1234.
Try it close to the adapter if it still doesn't work you might want to try it on another phone.
You're running ICS so this could be the problem!
The code usually comes in the email that they send when they inform you that your item is shipped. Might look there.
My code was 6789. Don't know of it would be the same, but worth a try.
Sent from my LG-P880 using xda premium
i use elm327 with torque pro and dashcommand.
on GB everything is good.
but when i passed to ICS i can't use my elm327(OBDLink:http://www.scantool.net/scan-tools/smart-phone/obdlink-bluetooth.html i pair and when open torque/dashcommand is asked forever the pin for pairing, and the device is disappear from devices paired.
i tryed with all ICS rom: same result.
maybe with CM10 is better...maybe.
i ask here but no response
Thanks for your reply , but i have tried every password i could think and still nothing..
What i am trying now, is to capture bluetooth packets sent from bluetooth adaptor so that i can hack the pin.
But i cant find the way how to see bluetooth packets (via wireshark) using linux (ubuntu).
speedyranger said:
i use elm327 with torque pro and dashcommand.
on GB everything is good.
but when i passed to ICS i can't use my elm327(OBDLink:http://www.scantool.net/scan-tools/smart-phone/obdlink-bluetooth.html): i pair and when open torque/dashcommand is asked forever the pin for pairing, and the device is disappear from devices paired.
i tryed with all ICS rom: same result.
maybe with CM10 is better...maybe.
i ask here but no response
Click to expand...
Click to collapse
Hmm so your problem now is the ICS version..i cant suggest something usefull :/
I suppose you have a Chinese clone elm327..like me
Gas_OB said:
Thanks for your reply , but i have tried every password i could think and still nothing..
What i am trying now, is to capture bluetooth packets sent from bluetooth adaptor so that i can hack the pin.
But i cant find the way how to see bluetooth packets (via wireshark) using linux (ubuntu).
Hmm so your problem now is the ICS version..i cant suggest something usefull :/
I suppose you have a Chinese clone elm327..like me
Click to expand...
Click to collapse
no cinese clone but this:http://www.scantool.net/scan-tools/smart-phone/obdlink-bluetooth.html
This is bluetooth ICS driver problem still disconnecting :/ maybe cm 10.1 solve this issue
biolo said:
This is bluetooth ICS driver problem still disconnecting :/ maybe cm 10.1 solve this issue
Click to expand...
Click to collapse
yes,,,broken driver on ics----->Damn LG!
i try that rom http://forum.xda-developers.com/showthread.php?t=2136618, and BT work fine with my obdLink.
i make some test with my truck...with my car on next saturday:laugh:
speedyranger said:
yes,,,broken driver on ics----->Damn LG!
i try that rom http://forum.xda-developers.com/showthread.php?t=2136618, and BT work fine with my obdLink.
i make some test with my truck...with my car on next saturday:laugh:
Click to expand...
Click to collapse
I have the same problem with the ELM327 bluetooth adapter. But loosing 3D, HDMI and getting different camera problems is not solution for me. Maybe we should ask for help from our developers here. I am ready to test some solutions.
p-vlad said:
I have the same problem with the ELM327 bluetooth adapter. But loosing 3D, HDMI and getting different camera problems is not solution for me. Maybe we should ask for help from our developers here. I am ready to test some solutions.
Click to expand...
Click to collapse
i know!
but for now, i have only that choice:
for all days: ICS
for days with elm327: JB 4.1.2
i've bought one cheap clone ELM327, Android torque connects to OBD adapter but it won't connect to ECU, i'm using OptimusRS CM10 based rom and my car is BMW 320td compact, am i doing anything wrong?
Screenshot:
{
"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"
}
pthacker85 said:
i've bought one cheap clone ELM327, Android torque connects to OBD adapter but it won't connect to ECU, i'm using OptimusRS CM10 based rom and my car is BMW 320td compact, am i doing anything wrong?
Click to expand...
Click to collapse
Make sure you turn the ignition to ''on'' (2 clicks) otherwise it won't connect, if it's not working it could be ICS, no idea if it's working with V28B or V30.
Will probably give it a go soon if I have the time.
chrisxt said:
Make sure you turn the ignition to ''on'' (2 clicks) otherwise it won't connect, if it's not working it could be ICS, no idea if it's working with V28B or V30.
Will probably give it a go soon if I have the time.
Click to expand...
Click to collapse
How? engine running? or just ignition-ready lights on?
Hi all,
Just brought a Pixel 32gb coming from the 6P. With the 6p, I'm able to use USB-audio to my cars radio no problem. However, with my pixel - it doesn't want to work. Upon connection, it cycles through the USB modes (Charging, PTP and Audio Source,) which interrupts the connection process. With the 6P, it's a constant 'audio source' USB mode.
I should mention, that the times I've got it working, I've had to wait for the connection to time out, and cause my radio to throw up an 'Android error' (unable to connect.) Then I simply went into developer options and selected 'audio source' as the default method. When this worked, I wasn't able to use the radio buttons (pause / play and seek.)
Nexus 6P - 7.1 dev preview
Pixel - 7.1
Radio: Kenwood KDC200UB.
Thoughts anyone?
Thanks in advance,
Chicken
It doesn't sound like your head unit is demanding "USB audio" and I don't believe it should.. It sounds like your 6P is connecting as a hard drive and you're able to use the head unit to control the tracks. This is how pretty much all after market head units work, I don't believe there are any head units that act like a USB DAC (straight thru USB audio controlled solely by the phone with an analog/digital output).
In my case with my DEH4800BT, my Pixel automatically mounts as storage and the head unit reads the music content and is able to play/pause/skip directly from it. This should be what happens in your case, I had to play with mine a few times in order to get it to work.
Edit: I'm going to play with the OTG adapter and a male/male USB cable to see how my head unit connects. Just as an experiment.
I can assure you, my 6p is not acting as a hard drive due to the radio not supporting MTP. It's a Kenwood KDC200UB. It's using USB-passthrough, and yes, the radio does support it and many others do too.
You may search the radio google, and you'd find a feature called 'hand mode.' This allows Google play etc to pass audio.
You are right, I should have done the research. However your head unit is using AOA and not USB audio in the traditional sense, it's allowing the head unit to be a human interface device and not (just) a DAC .
Your Kenwood head unit technically requires the use of the Kenwood Music Play app however my pioneer also states it needs an app but I don't use one. I did have to cycle my device into midi mode once before it worked you could give that a try or maybe your head unit needs a software update? Are you using the cable that came with the Pixel?
Thank you tho, I never would have fully understood AOA if you hadn't suggested that I look it up.
Last firmware update was last year, the nexus 6p wasn't on the supported device.
It did try to connect to an accessory, which I thought was strange
mine did too the first time, which is why i shuffled thru the usb modes. When i was reading about AOA i found out that its now depreciated, so there wont be anymore updates for it.
k.s.deviate said:
mine did too the first time, which is why i shuffled thru the usb modes. When i was reading about AOA i found out that its now depreciated, so there wont be anymore updates for it.
Click to expand...
Click to collapse
I'm sure AOA2 is still being worked upon, no?
Just an update: popped into a car audio Centre, and tried roughly 40 headunits. Didn't work on any of them. I'm almost positive this is a 7.1 issue
I believe you need to change the way it connects to your USB port in the car. I changed it from charging to reading files. Pull down the notification bar and click on the USB notification to select how it connects to the car. Worked for me.
pixel-painter said:
I believe you need to change the way it connects to your USB port in the car. I changed it from charging to reading files. Pull down the notification bar and click on the USB notification to select how it connects to the car. Worked for me.
Click to expand...
Click to collapse
I'm guessing your using MTP connection, which does work. However, after trying 2 pixels, and a Pixel XL - as well as having someone in America try with a similar head unit - it's definitely a pixel bug / issue.
To reiterate, MTP works fine - but using Audio out VIA USB does NOT
Suicidal Chicken said:
I'm guessing your using MTP connection, which does work. However, after trying 2 pixels, and a Pixel XL - as well as having someone in America try with a similar head unit - it's definitely a pixel bug / issue.
To reiterate, MTP works fine - but using Audio out VIA USB does NOT
Click to expand...
Click to collapse
While I understand what you mean by MPT, you might be confusing some people since it isn't listed as such on my phone and probably for others too. It is listed as "Transfer files" as in my screenshot below. Perhaps it is a brand specific issue related to proprietary software, or a mod or app installed. I bought mine directly from Google and have never had this issue once File transfer is selected, but my pixel seems to default to "Charge this device" every time even if I change the settings.
{
"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"
}
pixel-painter said:
While I understand what you mean by MPT, you might be confusing some people since it isn't listed as such on my phone and probably for others too. It is listed as "Transfer files" as in my screenshot below. Perhaps it is a brand specific issue related to proprietary software, or a mod or app installed. I bought mine directly from Google and have never had this issue once File transfer is selected, but my pixel seems to default to "Charge this device" every time even if I change the settings.
Click to expand...
Click to collapse
My phones not rooted, it's stock. Your image is relating to MTP / file transfer. My issue is related to Audio Out via USB using the AOA (Android Open Accessory) protocol.
Suicidal Chicken said:
My phones not rooted, it's stock. Your image is relating to MTP / file transfer. My issue is related to Audio Out via USB using the AOA (Android Open Accessory) protocol.
Click to expand...
Click to collapse
What is the drawback of starting using the method that works and stopping using the method that doesn't work?
A moment of nostalgic want for the old days?
If AOA is depreciated, 7.1 has forgotten it so it is not technically a bug but unsupported.
I get it is annoying if you're losing features to use the current working method of MTP / file transfer. Is that the case?
If AOA is depreciated, you may need to adapt to continue.
Sent from my sailfish using XDA Labs
nednednerb said:
What is the drawback of starting using the method that works and stopping using the method that doesn't work?
A moment of nostalgic want for the old days?
If AOA is depreciated, 7.1 has forgotten it so it is not technically a bug but unsupported.
I get it is annoying if you're losing features to use the current working method of MTP / file transfer. Is that the case?
If AOA is depreciated, you may need to adapt to continue.
Click to expand...
Click to collapse
It works on the 6p with 7.1 Dev preview.
Google's guidelines for nougat were that devices MUST be compatible with AOA. It's a bug.
Having this issue too and it sucks. I had a Nexus 5 and a Pioneer MVH-X380BT and it sounded great with the usb cable. Now with my Pixel my deck says error-19 every time I plug it in. I've tried going into the dev settings and changing the usb configuration and the app SoundAbout and it didn't make a difference. It was a pretty big difference in sound quality on the Nexus 5 between usb and bt and it's lame that the Pixel doesn't have the same audio support.
It would be amazing if Google backported aoa or someone made a mod to add it. That would be worth rootingng my phone for.
I also tried to connect my phone through USB, but it's not successful. Why google didn't provide an easy solution for such a long time?
I have a Pixel 2 and cannot get Audio out of phone to AOA device.
https://source.android.com/compatibility/android-cdd.pdf
In documentation it reads:
SHOULD NOT implement AOAv2 audio documented in the Android Open Accessory
Protocol 2.0 documentation. AOAv2 audio is deprecated as of Android version 8.0
(API
level 26). (page 102)
WHY must you do this Google!!!! :crying::crying::crying:
Hello everyone,
First of all it is so cool to stumble across this section of XDA with all of the community helping each other with Android Head units. It was so cool to see recommendations, suggestions, help, software updates, Custom ROMs, etc. so Thanks for all the cool post to read.
Now getting into my problem...
I purchased a Dasaita 10.2" Android 10.0 with the main intentions of using the CarPlay feature (Note: I am willing to use Wired CarPlay). Additionally would love the added features the unit provides for its price point.
However after receiving the unit and installing it, I can not get Apple CarPlay to work with a constant connection every time the vehicle is turned on. It takes a whole lot of tinkering to get it to connect; such as connecting bluetooth, headunit hotspot, headunit wifi, connecting with wire. Then once it is eventually connected CarPlay will work fine for the duration of the usage and any warm boots (turning the car off for a few seconds and turning it back on). It is so frustrating to get it connected because it is not straight forward or simple in any means. What is worse is that after the car is off for a good amount of time and I turn it back on, all is lost. zLink keeps trying to connect and bluetooth is definitely connected but it just won't connect. I have to tinker with it again, such as forgetting the device and forgetting CarPlay, trying to connect to bluetooth again and try to connect via wire, etc. Then eventually it might connect. There is just no specific instruction path to get it connected, just requires a bunch of different ways of tinkering to eventually it might connecting.
It has just been a pain to try and get CarPlay working, that was the biggest selling point for me to get this unit. If I can't get it working soon, it will be taken off the vehicle and returned.
Posting this here for help or possible leads to where to find help.
zLink:
APK Version: 3.5.56
VER-C: 30556
CHANNEL: HENGCHANGTONG
SYS-CHANNEL: hengchangtong
SYS-PLANTF: rk3399
Headunit:
Model: PX6(1280x720)
Android version: 10
Build number: rk3399-userdebug 10 QQ2A.200305.004.A1 eng.hct.20200609.160238 test keys
Kernel version: 4.19.111+ #1238 Tue Jun 9 15:48:02 CST 2020
MCU version: MTCE_HA_V3.56_1 Jun 17 2020 13:27:56
https://i.imgur.com/7w3TeBO.jpg
https://i.imgur.com/ncVafFc.jpg
https://i.imgur.com/VhJj14l.jpg
http://i.imgur.com/1alMxGx.jpg
P.S.: I made a small post about this issue in the Dasaita update topic and I was provided with update files. Link to the post and fellow comments.
P.S. 2: Android Auto works flawlessly, connect the USB and that is it Android Auto is working.
Got it working!!!! ?
The issue was that my phone was on iOS 14 Beta. I downgraded to a stable iOS version and it is working fine every time I turn the car back on and any warm boots. It just works now no problems.
The other devices I tested on where also on a stable iOS version not sure why they did not work?? Maybe I just did not test it enough, good thing I slept on it and recollected the next day.
Can you use Car Play wireless?
punjabi4life said:
Got it working!!!!
The issue was that my phone was on iOS 14 Beta. I downgraded to a stable iOS version and it is working fine every time I turn the car back on and any warm boots. It just works now no problems.
The other devices I tested on where also on a stable iOS version not sure why they did not work?? Maybe I just did not test it enough, good thing I slept on it and recollected the next day.
Click to expand...
Click to collapse
dominikfe said:
Can you use Car Play wireless?
Click to expand...
Click to collapse
Yes, CarPlay wireless works.
Due note I am now on iOS 13.5.1
Not sure if anybody here can help but I recently purchased a Dasaita PX30 it is running Android 10 but there is no ZLink installed. I am pretty sure this unit has wireless CarPlay compatibility: when I go to car factory settings under CarPlay it is selected to ZLink but again the ZLink app is nowhere to be found. I tried downloading the ZLink apk v3.5.56 and installing using external USB but it just comes up to ‘not installed’. Please help! Thanks
punjabi4life said:
Yes, CarPlay wireless works.
Due note I am now on iOS 13.5.1
Click to expand...
Click to collapse
I have same issue from yesterday, I have IOS 14.0, how to down grade? Who told into downgrade to lower version?
I’m on iOS14 and I keep getting a “hardware err, No MFi #” when I try to run ZLink (CarPlay wireless I haven’t seen an official new update from Dasaita.
Anyone else have this same issue?
punjabi4life said:
Got it working!!!!
The issue was that my phone was on iOS 14 Beta. I downgraded to a stable iOS version and it is working fine every time I turn the car back on and any warm boots. It just works now no problems.
The other devices I tested on where also on a stable iOS version not sure why they did not work?? Maybe I just did not test it enough, good thing I slept on it and recollected the next day.
Click to expand...
Click to collapse
Hi, I have the same problem, I just installed the head unit today. Android Auto works but Car Play doesn't. Two different iPhones, swapped the iphone cable as well. The iphones have the latest official iOS release.
giovosc said:
Hi, I have the same problem, I just installed the head unit today. Android Auto works but Car Play doesn't. Two different iPhones, swapped the iphone cable as well. The iphones have the latest official iOS release.
Click to expand...
Click to collapse
I had the same problem, CarPlay did not work with iOS 14, but after updating to 14.1 it started to work again.
giovosc said:
Hi, I have the same problem, I just installed the head unit today. Android Auto works but Car Play doesn't. Two different iPhones, swapped the iphone cable as well. The iphones have the latest official iOS release.
Click to expand...
Click to collapse
Fixed, I did a network reset in the head unit and now is working but doesn't reconnect after the car is switched off. Still troubleshooting
giovosc said:
Fixed, I did a network reset in the head unit and now is working but doesn't reconnect after the car is switched off. Still troubleshooting
Click to expand...
Click to collapse
Hi all,
I just installed the PX6 and everything works except Carplay. I have done everything that Dasiata on Amazon has instructed me to do. I can't get wired or wireless to connect. The main reason why I purchase this unit was for Carplay as well. I am on IOS 14.1. Any ideas?
MCU Version:
MTCE_HA_V3.62_1
Sept 14, 2020
Build Number:
rk3399-userdebug 10 QQ2A.200305.004.A1 eng.hct.2020091
Kernel Version:
4.19.111+
#2266 Tue Sep 15 15:49:09 CST 2020
khite1001 said:
Hi all,
I just installed the PX6 and everything works except Carplay. I have done everything that Dasiata on Amazon has instructed me to do. I can't get wired or wireless to connect. The main reason why I purchase this unit was for Carplay as well. I am on IOS 14.1. Any ideas?
MCU Version:
MTCE_HA_V3.62_1
Sept 14, 2020
Build Number:
rk3399-userdebug 10 QQ2A.200305.004.A1 eng.hct.2020091
Kernel Version:
4.19.111+
#2266 Tue Sep 15 15:49:09 CST 2020
Click to expand...
Click to collapse
*UPDATE*
Dasaita told me to update to MCU 3.65 and sent me the link. Now Carplay will work wirelessly, but will still not work wired. I realized that the way they have wireless Carplay setup to work sucks. I have to connect to the HU hotspot and Bluetooth to connect. Well, that keeps my phone from using cell data. Totally defeats the purpose. Does everyone have to connect that way?
khite1001 said:
Hi all,
I just installed the PX6 and everything works except Carplay. I have done everything that Dasiata on Amazon has instructed me to do. I can't get wired or wireless to connect. The main reason why I purchase this unit was for Carplay as well. I am on IOS 14.1. Any ideas?
MCU Version:
MTCE_HA_V3.62_1
Sept 14, 2020
Build Number:
rk3399-userdebug 10 QQ2A.200305.004.A1 eng.hct.2020091
Kernel Version:
4.19.111+
#2266 Tue Sep 15 15:49:09 CST 2020
Click to expand...
Click to collapse
So here we go. I have the solution that will allow you to connect to the Dasaita Hotspot and allow your phone to use mobile data. Finally, it works as it supposed to. This solution is for the PX6 with Android 10, MCU 3.65, and zlink.
1. Connect your iPhone to the Bluetooth
2. Connect your iPhone to the Wi-Fi Hotspot on the head unit.
3. Go to settings on the iPhone, then Carplay sections, and be sure that it connects to the head unit. Mine was called CAR-LINK, once connecting it changes to something like zjinnova-D310C
4. Go to SETTINGS and select Wi-Fi then select the blue INFO icon to the right of the name of your head unit hotspot connection.
5. Make note of both the IP address and the Subnet Mask address
6. Select the STATIC option and enter only the IP and Subnet Mask addresses from Step 5 -- (Leave everything else blank)
Boom, everything works as it should. I will inform Dasiata. This should be the first thing they tell you to try.
khite1001 said:
So here we go. I have the solution that will allow you to connect to the Dasaita Hotspot and allow your phone to use mobile data. Finally, it works as it supposed to. This solution is for the PX6 with Android 10, MCU 3.65, and zlink.
1. Connect your iPhone to the Bluetooth
2. Connect your iPhone to the Wi-Fi Hotspot on the head unit.
3. Go to settings on the iPhone, then Carplay sections, and be sure that it connects to the head unit. Mine was called CAR-LINK, once connecting it changes to something like zjinnova-D310C
4. Go to SETTINGS and select Wi-Fi then select the blue INFO icon to the right of the name of your head unit hotspot connection.
5. Make note of both the IP address and the Subnet Mask address
6. Select the STATIC option and enter only the IP and Subnet Mask addresses from Step 5 -- (Leave everything else blank)
Boom, everything works as it should. I will inform Dasiata. This should be the first thing they tell you to try.
Click to expand...
Click to collapse
I’ve got the same version of firmware and software and running iOS 14.2. I am stuck on the step where you go to CarPlay -> General and connect to the head unit and the circle never stops spinning.
Does anyone know whether there is a fix in the works to make wired Apple CarPlay just work or if there is a more stable version I can try and roll my unit back to? This is quite annoying.
David201092 said:
I’m on iOS14 and I keep getting a “hardware err, No MFi #” when I try to run ZLink (CarPlay wireless I haven’t seen an official new update from Dasaita.
Anyone else have this same issue?
Click to expand...
Click to collapse
I’m having the same issue as you, have you been able to fix it ???
Mine is flames as well. Sometimes it connects fine. Sometimes not at all, but phone says it is connected to the car via BT.
I did get it to connect today but I need to test more. While it was stuck on Zlink saying connecting, I placed a call (to my voicemail) and zlink connected. Could be unrelated. More testing needed.
Would love to update this to android 10 or a newer official version of zlink.
Anyone else have luck getting wireless Carplay to work consistently? Initially, it did for me on my Idoing PX6 head unit (similar software and hardware to the Dasaita), but I feel like I did something to cause it to stop working. Now, when I power on my radio, my phone connects quickly to the bluetooth and to the AP (wifi hotspot), but ZLink never opens automatically like it should. When I open ZLink manually, it just sits at "connecting". If I disconnect bluetooth on my iPhone and reconnect it twice, then ZLink will sometimes decide to work and do its thing.
I will try the static IP idea. I noticed it was on "low data" mode for the AP, so I disabled that.
I updated firmware to MCU 3.69 and the system update is from 12/15/2020 I think. That didn't help.
I also have a Carlinkit USB adapter, not plugged in, that uses an app called Autokit. I was trying to use that a few days ago and it would eventually work, but takes like 45 seconds to finally connect.
I have tried forgetting my home wifi on my iPhone so it doesn't have to disconnect from it, but that didn't help. The connections all seem to work perfectly and it's just ZLink failing, but it's hard to say.
Hey man How’d You get apple CarPlay to work ? Mine hasn’t worked for 3 months
snake2332 said:
Anyone else have luck getting wireless Carplay to work consistently? Initially, it did for me on my Idoing PX6 head unit (similar software and hardware to the Dasaita), but I feel like I did something to cause it to stop working. Now, when I power on my radio, my phone connects quickly to the bluetooth and to the AP (wifi hotspot), but ZLink never opens automatically like it should. When I open ZLink manually, it just sits at "connecting". If I disconnect bluetooth on my iPhone and reconnect it twice, then ZLink will sometimes decide to work and do its thing.
I will try the static IP idea. I noticed it was on "low data" mode for the AP, so I disabled that.
I updated firmware to MCU 3.69 and the system update is from 12/15/2020 I think. That didn't help.
I also have a Carlinkit USB adapter, not plugged in, that uses an app called Autokit. I was trying to use that a few days ago and it would eventually work, but takes like 45 seconds to finally connect.
I have tried forgetting my home wifi on my iPhone so it doesn't have to disconnect from it, but that didn't help. The connections all seem to work perfectly and it's just ZLink failing, but it's hard to say.
Click to expand...
Click to collapse
How’d you get it to work????
damianmorado said:
How’d you get it to work????
Click to expand...
Click to collapse
Wireless Carplay? The static IP stuff didn't help. The only thing that seems to work is toggling bluetooth connection on my iPhone with the radio after manually opening Zlink on the radio. It still doesn't always work then.
No matter what, the phone connects to both the BT and Hotspot of the radio every time, it just doesn't continue on to Carplay and Zlink doesn't auto-launch or connect after manually launching.
I've used my car a few times after leaving my Oneplus 6T in it, like a permanent connected phone, and it works. Sometimes I have to launch Zlink manually, but other times it has worked for Android Auto without me having to do anything. So far, this is the most convenient solution. I also paid for T-Mobile One Plus to get 20GB of full speed hotspot each month so I can mess around with native Android apps and stuff. Still not sure what I'm going to settle on doing long-term. I just got iOS 14.3 installed on the iPhone so I might go try again.
Does someone else also experience issue with Android Auto?
- When using the cable, it only charges, the S10+ works flawless with AA with the same cable
- When using AA Wireless, it is very laggy, while the S10+ is running smooth with AA Wireless
Any ideas how to fix this?
Saw similar issues on Google Support:
Compatibility with Samsung Galaxy S22 Ultra
Android Auto does not work on Samsung Galaxy S22 Ultra and 2020 Škoda Scala
Update 25-2-2022:
I was able to connect with wired AA by using another USB-C cable, while the USB-C cable that came with the AAWireless device works just fine with my S10+.
But with AAWireless and with Android Auto wired, the screen is very laggy. I don't know if it is related to Samsung's hardware/software or Android 12.
Android Auto Known Issues (Updated: 2/21/2022)
To make AA work, try these steps:
Remove your new and old phone from your car's list of Bluetooth devices
Clear Cache/Remove storage data of the Android Auto app
Uninstall/remove updates Android Auto
Go to Google Play Store and install/update Android Auto
Turn on Passtrough option in AAWireless (works for me without, but it always disconnects after 5 mins, also on the S10+)
For Wired AA, try another cable, that worked for me!
For other detailed steps, try these (thanks to gadinaveh):
https://forum.xda-developers.com/t/s22-ultra-and-android-auto-wireless-issue.4405875/post-86480861
My problem is I use Android Auto wired - because my vehicle is dumb like that - and I've never had issues... used the 22ultra for the first time today (wired) and the Android Auto connection kept dropping... no idea why.
AA wireless won't even setup for me. I see my phone greyed out on my AA screen in my car, but it doesn't do anything otherwise. I haven't tried wired yet, I'll give it a shot tomorrow. Gotta have AA!
Mine won't even connect wired. I plug it in and my car doesn't recognize anything plugged in. (T-Mobile Snap)
Android auto doesn't work properly on my pioneer head unit as well. It tries to set it up and the head unit ends up with a black screen until I disconnect the phone.
Same for me - does not connect to wired or wireless (thru AAWireless). Tried to remove all devices from
Same for me. my S21 was working great before on my AAWireless and with cable (Honda Pilot). I tried to connect with S22 - wired does not work, neither does wireless. Removed all devices from the car and retried - nothing still. very frustrating.
I did see something else that might be related. I can successfully connect my S21 to my Dex on Desktop running on my mac. The S22 will not detect the same Dex (same cable, same laptop). It will successfully work with an external monitor with Dex and with Wireless Dex on my Windows laptop.
So has anyone tried uninstalling AA? Then reinststall?
I have the U.S. Unlocked and after removing my S20 Ultra Unlocked from my 2020 Honda CRV the S22 Ultra connected without any issues at all. Make sure you remove the old phone and the Bluetooth connection settings for old phone before trying to connect with the new phone. Worked for me but then again this is the Snappy version. I have had it 24 hours and not had a single issue yet and I used Smart Switch to setup phone exactly like the old one so they look identical.
Paul_Deemer said:
I have the U.S. Unlocked and after removing my S20 Ultra Unlocked from my 2020 Honda CRV the S22 Ultra connected without any issues at all. Make sure you remove the old phone and the Bluetooth connection settings for old phone before trying to connect with the new phone. Worked for me but then again this is the Snappy version. I have had it 24 hours and not had a single issue yet and I used Smart Switch to setup phone exactly like the old one so they look identical.
Click to expand...
Click to collapse
Thanks Paul for the info.
I used smartswitch but initially did not remove the phone from the car., when nothing worked, I removed all previous devices and cleared storage/cache for AA on the new phone.
Did you (confirming)
1. remove the devices from the car
2. remove the bt connection from the new phone
am i missing something?
gadinaveh said:
Thanks Paul for the info.
I used smartswitch but initially did not remove the phone from the car., when nothing worked, I removed all previous devices and cleared storage/cache for AA on the new phone.
Did you (confirming)
1. remove the devices from the car
2. remove the bt connection from the new phone
am i missing something?
Click to expand...
Click to collapse
My old phone was in there twice in the settings and had to remove both entries. But I didn't do anything to the new phone. I just plugged it into the entertainment port with a cable and made sure Bluetooth on new phone was on and the car recognized the new phone.
Paul_Deemer said:
My old phone was in there twice in the settings and had to remove both entries. But I didn't do anything to the new phone. I just plugged it into the entertainment port with a cable and made sure Bluetooth on new phone was on and the car recognized the new phone.
Click to expand...
Click to collapse
Thanks Paul
Started the same steps on the other honda (civic 2019) and was able to connect with Cable (yay ;-) ).
I then tried to use AAWireless, and while it shows successful connection (phone shows "use AA on your car screen", AA icon shows up on the car screen), AA does not open on the car. In addition, when going into audio when AA is the selected audio source, I see a message of "Loading..." and is stuck there.
Any idea or suggestion will be appreciated
Just received my s22u unlocked. Aa working fine wired, and wirelessly on my Dodge
gadinaveh said:
Thanks Paul
Started the same steps on the other honda (civic 2019) and was able to connect with Cable (yay ;-) ).
I then tried to use AAWireless, and while it shows successful connection (phone shows "use AA on your car screen", AA icon shows up on the car screen), AA does not open on the car. In addition, when going into audio when AA is the selected audio source, I see a message of "Loading..." and is stuck there.
Any idea or suggestion will be appreciated
Click to expand...
Click to collapse
With AaWireless i had the same issue. Until I cleared storage and cache of Android Auto and then Disable Enable it, and then uninstall it. Then i Installed/updated it from the store and it worked with AAWireless, unfortunately still not working wired. Will try removing new phone from my car and then plug in with usb cable.
I have no issue with the connection but the battery drain so badly when using Wireless AA. I did connect through Motorola MA1.
{
"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"
}
After I got the cable to work, tried the AAW, did not work (I did remove it from the car andn bt earlier), so not sure why this did not work. Before that I cleared storage from AA, and running the latest beta for AA (7.4)
It seems that AA should NOT be transferred from the old phone - after I cleared cache data for both AA and AAWireless it started working albeit VERY slowly - not sure what's up with that. If you are getting just a blank screen - wait for awhile it might come up with the setup screen.
I cleared storage andn cache, and then tried AAWireles (with the AAWireless device) after successfuly completing the cable connection. I was able to connect to the AAWireless device, the phone had the two persistent notification that AA is connected, the headunit showed the AA icon, but when pressing it - AA will not open. So not sure how to fix this or whether there is a step I am missing
Also having problem with aa wireless. Works great with pixel 6 pro works great with s21 ultra. S22 ultra loads in the car but it will not show up on the screen and I can't figure out why. I have deleted the old phone, factory reset head unit. Cleared catch cleared storage. tried many other things. My car is a 2019 Honda Accord. Wire connection works fine
Used wired AA fine today with the S22 Ultra
My current car doesn't allow for wireless AA
Hi gents and ladieas alike,
Recently I purchased a unit with the info
{
"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"
}
its a 4gb 8core with 32gb of storage.
Iam extremely new to this and Im yet to figure out what certain things mean so please be gentle
1. Is there any mods worth doing?
2. Is there any better firmware to flash/use to make this unit 'better'
3. I have changed to nova launcher and it seems to be snappier, any questions here?
4. What can I use to re-program buttons on my steering wheel? What it comes with doesnt seem to work.
5. Its actually android 10, not 11, its spoofed I checked.
The Device manufacturer is SPRD
Any help would be greatful!
Thanks in advance
iionas said:
Hi gents and ladieas alike,
Recently I purchased a unit with the info
its a 4gb 8core with 32gb of storage.
Iam extremely new to this and Im yet to figure out what certain things mean so please be gentle
1. Is there any mods worth doing?
2. Is there any better firmware to flash/use to make this unit 'better'
3. I have changed to nova launcher and it seems to be snappier, any questions here?
4. What can I use to re-program buttons on my steering wheel? What it comes with doesnt seem to work.
5. Its actually android 10, not 11, its spoofed I checked.
The Device manufacturer is SPRD
Any help would be greatful!
Thanks in advance
Click to expand...
Click to collapse
It's a FYT unit. Any firmware from a FYT reseller can be used be it for uis7862 or uis8581A. The 8581A is simply the "lighter" less poweful brother of the uis7862. There are some minimal tweaks you have to apply and the lsecupdate binary is different. Of course, if you find a real uis8581firmware it might be better.
1. Only if you have problems, go for a mod.
2. If you do not even know the brand/reseller of your unit, how can anyone advice for better firmware? Next to that: 98% of the firmware for FYT units is identical. Only some differences in "theme" for the launcher (but you use Nova anyway). Your app firmware is of December 2021. There is newer available, but that means it will wipe your system. So far I only flashed newer kernels (read the uis7862 Q&A, etc. thread) hoping they patched the kernel with Android bugfixes and security improvments in the newer kernels, and keep the rest as it is (no AllAppUpdate.bin), thereby also keeping all my settings and 3rd party apps. Again: If you don't encounter errors, there is no need for other firmware. Note: do not flash T'eyes firmware. It is not bad but it does contain quite some restricted firmware making your unit perform much worse.
3. I use Nova as well and I am happy with it. No questions here
4. Do you have a CAN-bus? if so, they are hard-coded and you can't reprogram them unless you use something like my "FYT HW OneKey" app that lets you reprogram part of the buttons.
5. That's correct. The android level is determined by the SDK. The Android version setting (for easy version status) is nothing more than a property and can just as easily be set (or faked) to 17, 31 or 145, etc..
surfer63 said:
It's a FYT unit. Any firmware from a FYT reseller can be used be it for uis7862 or uis8581A. The 8581A is simply the "lighter" less poweful brother of the uis7862. There are some minimal tweaks you have to apply and the lsecupdate binary is different. Of course, if you find a real uis8581firmware it might be better.
1. Only if you have problems, go for a mod.
2. If you do not even know the brand/reseller of your unit, how can anyone advice for better firmware? Next to that: 98% of the firmware for FYT units is identical. Only some differences in "theme" for the launcher (but you use Nova anyway). Your app firmware is of December 2021. There is newer available, but that means it will wipe your system. So far I only flashed newer kernels (read the uis7862 Q&A, etc. thread) hoping they patched the kernel with Android bugfixes and security improvments in the newer kernels, and keep the rest as it is (no AllAppUpdate.bin), thereby also keeping all my settings and 3rd party apps. Again: If you don't encounter errors, there is no need for other firmware. Note: do not flash T'eyes firmware. It is not bad but it does contain quite some restricted firmware making your unit perform much worse.
3. I use Nova as well and I am happy with it. No questions here
4. Do you have a CAN-bus? if so, they are hard-coded and you can't reprogram them unless you use something like my "FYT HW OneKey" app that lets you reprogram part of the buttons.
5. That's correct. The android level is determined by the SDK. The Android version setting (for easy version status) is nothing more than a property and can just as easily be set (or faked) to 17, 31 or 145, etc..
Click to expand...
Click to collapse
Wow thanks for the reply mate you're an absolute damn legend
I'm quite ok with how it functions I don't have any said errors or problems. Good to know some of this info really I mean it thanks again.
Mine is faked however I don't really mind or care I didn't think the components would have been able to power this soc!
I don't have any functions for a cheap Chinese thing it does it job with Waze and music. And occasionally YouTube for a podcast.
Yes sir I do have canbus so I'll be looking for that tool asap. I wanted to reprogram a button for Spotify next song. Nothing special!
Is there ever a time where I should be updating the firmware at all? Like sau year down the track? Or do they stop servicing them?
I was hoping there was a hal9k mod for this one too but I lucked out there
iionas said:
Yes sir I do have canbus so I'll be looking for that tool asap. I wanted to reprogram a button for Spotify next song. Nothing special!
Is there ever a time where I should be updating the firmware at all? Like sau year down the track? Or do they stop servicing them?
I was hoping there was a hal9k mod for this one too but I lucked out there
Click to expand...
Click to collapse
In the settings you can reverse next-previous and/or Vol-Up/Vol-Down if your app/system reacts the other way round, like Spotify does for example. You do not need my app for that.
Like said: so far I have only updated the kernel (6513_1.zip) and nothing else. I only use the unit for navigation, radio and music. Note though that those FYTs still contain an error where they erase your Google contacts if you sync them. It seems the latest T'eyes/Joying firmware doesn't do that anymore, which als means that the somewhat slower resellers like Mekede etcetera should follow soon. (but I don't call from my car. Maybe twice a year)
All those mods are for MTCD/E models, not for FYT.
The only FYT mod is made by @gordgelin but only for real T'eyes models (like mentioned :some T'eyes stuff only works if you have a T'eyes id on your unit).
Tyukta at 4pda makes "a best of" mod where he simply takes the latest kernel and combines it with (what he considers) the best apps (themes actually) from other firmwares (the AllAppUpdate.bin) and he himself also does some theming to apps.
surfer63 said:
In the settings you can reverse next-previous and/or Vol-Up/Vol-Down if your app/system reacts the other way round, like Spotify does for example. You do not need my app for that.
Like said: so far I have only updated the kernel (6513_1.zip) and nothing else. I only use the unit for navigation, radio and music. Note though that those FYTs still contain an error where they erase your Google contacts if you sync them. It seems the latest T'eyes/Joying firmware doesn't do that anymore, which als means that the somewhat slower resellers like Mekede etcetera should follow soon. (but I don't call from my car. Maybe twice a year)
All those mods are for MTCD/E models, not for FYT.
The only FYT mod is made by @gordgelin but only for real T'eyes models (like mentioned :some T'eyes stuff only works if you have a T'eyes id on your unit).
Tyukta at 4pda makes "a best of" mod where he simply takes the latest kernel and combines it with (what he considers) the best apps (themes actually) from other firmwares (the AllAppUpdate.bin) and he himself also does some theming to apps.
Click to expand...
Click to collapse
Cool well thats pretty straight forward I dont have any issues with it, so Ill be leaving it for now and just using your tool for re-programming buttons.
The infamous google contact deletion happened to me, i managed to restore which is really good, however it was annoying. It would of been really good if the google phone app would of worked with it over BT, but it does require a sim (the unit goes support 4g however i dont use a sim).
Ill be ready over the guides today to see for your tools
Hi Gentlemen,
I bought same FYT few days back, succeeded with installation to old MB w211. However i faced problem with Bluetooth connection. It seems like Bluetooth driver or module in head unit is not working properly. I tried to reset factory settings, but still have issue with Bluetooth connection.
Could you please be so kind and share your advice on that. Maybe firmware update is required, but i don't know where to find it out.
I would really appreciate your assistance. Sorry for my English, i am not native speakers.
Thanks in advance Gentlemen.
Hi, is anyone willing to share about what kernel to download? And my Bluetooth is not working recently and shows “null”. Help!!! My android SDK29
how to get the firmware for this unit.
how to get the firmware for this unit.
Uis8581A
saifulmly said:
how to get the firmware for this unit.
Uis8581A
Click to expand...
Click to collapse
One reviews forum or contacts seller.
saifulmly said:
how to get the firmware for this unit.
Uis8581A
Click to expand...
Click to collapse
This unit? Which unit?
That is like: "My phone has a snapdragon-750 cpu". Which firmware should I download?
(select about 25 brands with 200+ models).
Be more specific.
I have a k4811 (8581) and was wondering if there is a way to fix adb to make it work? enabling it in dev options does nothing (the device isn't detected when a laptop is plugged in to USB and adb wifi also rejects connections).... will the FYT MC app work on this device? ex. root button?
Hello everyone, I bought a UIS8581A and I also have problems with bluetooth where I can't connect my ELM327 adapter because I can't even open the bluetooth settings to do so.
The salesman who sold me the radio can't help me right now. Can anyone help me?
Otherwise I have to return the radio to the seller
fabius12 said:
Hello everyone, I bought a UIS8581A and I also have problems with bluetooth where I can't connect my ELM327 adapter because I can't even open the bluetooth settings to do so.
The salesman who sold me the radio can't help me right now. Can anyone help me?
Otherwise I have to return the radio to the seller
Click to expand...
Click to collapse
You should have an app called "Bluetooth" (not inside settings, but an actual preinstalled app).
What happens when you open the Bluetooth app?
I continue the discussion here which talks about my problem with the OBD module
OBD over WIFI and the Internet
I am a recent FYT user on UIS8581A, Android 11 (fake). I have a sim card connected to it that provides internet. When I connect WiFi with OBD, internet connectivity is broken. WiFi without internet has priority in data transmission over SIM card...
forum.xda-developers.com
Yesterday I tried to pair by changing the radio name, password and all the craziest tests I could think of but nothing.
My bluetooth screen is the first photo I attach
When I try to connect one of my three working ELM327 minis, nothing happens, I touch the symbol of the chain to connect, it asks me for the pin of the ELM module, I insert it (it is 1234), after a few seconds a message appears "pairing succeeded". But that's not true, because the chain symbol doesn't change, in Torque I don't see the module (try various versions of torque) and I can repeat the bluetooth pairing indefinitely but it never works.
Any app I use for bluettoth tells me that bluetooth is not working or can't be turned on. But if I connect a smartphone it works.
I do not know what to do
Anyone can help me?
Whats App Image 2023 03 08 at 10 49 16 — Postimages
postimg.cc
I am trying to understand what is happening with my bricked UIS8581A unit.
I flashed the wrong FW. It appears to be completely dead apart from feeling warmth on the rear of the unit when I add power to yellow and red (power and acc) wires while it is grounded (black). I have an update.zip (1.2GB) and a full firmware (3.6GB) from the seller.
The part I am wishing to understand is this:
With the full FW uncompressed in an update folder on a USB stick's root, plugged into the 4pin usb port on the unit, I power the unit on and there is no indication of the USB stick being accessed (red LED on USB stick not lit). I have a USB-A to USB-A cable plugged into the second USB port (6 pin). When I plug the other end of the male to male USB into my laptop (up to date USB drivers installed) that is powered on, the USB stick's LED begins to flash as indication it is being accessed. The LED remains lit for several minutes and then begins to flash (appears to be random flashes). After about 20-30 minutes the USB's LED flashes in a repeating pattern. I have left this USB stick continue whatever it is doing for hours. After disconnecting the laptop from the USB, disconnecting the USB stick, and cycling the power to the unit, the unit is still bricked. Plugging the USB stick back into the 4 pin USB port (with power on), the USB's LED remains unlit indicating it is not being accessed still. Recycling the power to the unit does nothing. Only when I re-connect the USB-A to USB-A cable from the unit to my laptop the USB stick is accessed. Disconnecting the cable, the LED turns off. This is the only life I have witnessed since bricking the unit.
I am wondering why the USB is indicating it is being accessed, only when connected to my laptop.
Does anyone know what is going on here when I connect the unit with my laptop and the USB's LED indicates it is being accessed?
Please don't reply, unless you have specific knowledge.
To all who don't reply, thank you for not wasting my time! It is appreciated...
@S2artb What comes to mind is how you are resetting your unit. I'm not sure if this will work and/or if this applies to your unit. There is a reset hole in the top left of the display. I'm not sure of the exact sequence, but you can try that. Search this or the forum that applies to your unit, if this forum doesn't apply to yours.
S2artb said:
I am trying to understand what is happening with my bricked UIS8581A unit.
I flashed the wrong FW.
Does anyone know what is going on here when I connect the unit with my laptop and the USB's LED indicates it is being accessed?
Click to expand...
Click to collapse
Do not connect your unit with the laptop. This will not help at all.
Which unit do you have? This is the FYT forum and there are many UIS8581A units that are not FYT.
Which wrong firmware did you use?
You tell us absolutely nothing that we need to help you.