Anyone-Please try to help me with these issues:
1. When the unit is in STBY (no screen output) and i connect any USB cable the PDA "wakes-up" and if connected to a PC will start doing a Sync, is there anyway to stop the "wake-up" when connecting a USB cable (-or installing Mini-SD card).......all i want to do is charge the unit while it's in STBY mode. In my old Mio 168RS this could be done in Settings. Maybe someone has a small application that can do this?
2. Sometimes when i innitiate Active Sync i get this Error "To Sync this device you must install ActiveSync 4.0 or higher on your Desktop computer"....but actually i'm running ActiveSync 4.5 already on my PC!!??
Then i need to remove the ActiveSync from my PC and re-install it again until the next time.
Not in stb mode you can switch off the 3600 it still charging etc. only it is off
I don't know if this could help because I never tried it. However, I tried to disable the usb connection from Active Sync for other purposes. In Active Sync program, you can actuallly choose to turn off the usb detection (which can be turned back on anytime). That way, Active Sync will not automatically update your device, hence, turning your device on. In that case, you can just plug in your device for charging purpose.
Thanks for your inputs but this is not what i'm looking for.
In my old Mio168RS there was the possibility in "Settings" that the unit did not come out of STBY mode when connecting to a USB input or when inserting an external SD card.
By the way turning the unit "OFF" will also turn off the phone!!
One additional question that someone might be able to help is if there any way to increase the Speaker Phone volume above and beyond what can be done within the settings.???
I m on Verizon vs980. phone operates just fine, but I have no PC connection capability. when I plug to PC , it just charges. its not recognized AT ALL. nothing in device manager or adb. I have updated drivers, usb debugging enabled, and have pc connection setting set to MTP (in fact I have have tried all options). USB on the go does not work either, so it seems like a kernel issue. its like that portion of usb is just not delivering any kind of signal. To help diagnose the problem I reverted back to jelly bean stock 12b, and baseband 12b , thinking if its kernel , it may fix it... same issue. next idea is hardware so I replaced the usb motherboard (not the main board). same issue. I have tried 5 different usb cables, and even used another phone to see if that phone could connect (eliminating possibility of faulty usb on my pc) the htc phone connected fine so I am exhausted on options. seems software related, but I have no idea what to try next. hopefully someone can give me some advice. thanks!!
also just noticed USB debugging option, doesn't survive a reboot. when I turn usb debugging on, its unselected again when I reboot. wonder if this is why, maybe its never really turning on.
I'm having an issue getting Android Auto to launch in my Subaru Crosstrek 2018 model. It works when I use my Nexus 6p but not with the Essential phone. I've tried different cables and reinstalling Android Auto but no luck. Anybody else having issues with Android Auto in their car with the Essential phone?
I had major problems getting Android Auto to work with my Essential phone.
At first, I kept getting the red screen of death (something about "do this when the car is stopped and the brake is on"...of course the car was stopped and the brake was on...). The next day (after a phone update), I tried again and could get past that screen. But then it wouldn't connect.
Turns out you have to scroll down the notifications and change the connect mode from USB charge to MTP manually. Once you do that, it quickly connects. Why the phone can't automatically do that for you...I don't know. But I've done this repeatedly now and each time it connects once you change to MTP mode.
(I also have USB debugging on--don't know if that's important as well).
quadcrap1 said:
I had major problems getting Android Auto to work with my Essential phone.
At first, I kept getting the red screen of death (something about "do this when the car is stopped and the brake is on"...of course the car was stopped and the brake was on...). The next day (after a phone update), I tried again and could get past that screen. But then it wouldn't connect.
Turns out you have to scroll down the notifications and change the connect mode from USB charge to MTP manually. Once you do that, it quickly connects. Why the phone can't automatically do that for you...I don't know. But I've done this repeatedly now and each time it connects once you change to MTP mode.
(I also have USB debugging on--don't know if that's important as well).
Click to expand...
Click to collapse
Android Auto doesn't kick-in on my '20 Subaru Outback (works on my wife's '19 Nissan Rogue).
Can you specify how to get to this setting. I'm unable to find it...
Thanks
levpri said:
Can you specify how to get to this setting. I'm unable to find it...
Click to expand...
Click to collapse
For the current connection, expand the "usb charging" notification, and it will give you a prompt to the available options - just select what you need. To change the default USB connection behaviour, go to Settings - System - Developer options - Default USB configuration, and select an appropriate connection mode.
kt-Froggy said:
For the current connection, expand the "usb charging" notification, and it will give you a prompt to the available options - just select what you need. To change the default USB connection behaviour, go to Settings - System - Developer options - Default USB configuration, and select an appropriate connection mode.
Click to expand...
Click to collapse
Funny there is no USB charging notification on the top, but in Default USB configuration should it be on File Transfer? Thanks!
I've never had a problem with android auto on mine, though I think I probably did change the default connection mode to file transfer a long time ago (before I had a vehicle with android auto).
You can also try a USB hub. These resolved the problem:
AmazonBasics 4 Port USB to USB 3.0 Hub with 5V/2.5A power adapter
ASIN B00DQFGH80
TP-Link | 4 - Port USB 3.0 Hub | Slim & Foldable Cord Design | Compact Travel Size with Charging Ports | Universal Compatibility - USB Flash Drive, Notebook, MacBook, PC, Chromebook and More (UH400)
ASIN B012B6YQY6
Sorry, I can't post direct links
Hi,
I am having a hard time trying to get a couple of USB devices to work properly on my headunit. One is a USB CarPlay dongle, and the other is an OTA tv tuner. Both USB devices get recognized by the headunit, however in the case of the first, it never gets passed a connection state where the dongle starts talking to the application. In case of the second, the OTA never finds TV stations after doing a complete scan.
USB devices like keyboards, mice, USB flash drives, even a webcam work fine. I contacted the manufacturer and they said they only support USB synchronous which may be the reason these devices can't work properly.
The unit is an Eonon GA7157 with the Allwinner R16 1.6GHz Cortex A7 Quad-Core CPU.
Questions:
Is it possible this is a valid claim?
My unit is rooted, can USB asynchronous be enabled via software?
I was also thinking this could be an OTG wiring issue, what do you think? I say so because the only way I could get the CarPlay dongle to work on my Samsung Tablet A, was with an OTG cable. A straight connector presented the same symptoms.
I am not too experienced with Android, so please be gentle
He was feeding you a load of horse manure.
Either that, or he meant something entirely different by "USB synchronous".
Precisely what do you mean by "get recognized by the headunit"?
What exactly *are* these two devices you are trying to use?
What *drivers* do they use?
Have you confirmed that the kernel is enumerating the devices?
Have you confirmed that the kernel is binding the proper drivers to them?
Have you confirmed that Android knows how to deal with the interfaces that the drivers are providing for these devices?
Have you confirmed that the interface permissions are such that a user application will be able to access it?
An OTG cable does two things;
1) It reverses the gender of the connector,
2) It sends a signal to the phone/tablet/whatever that it should switch its USB port from slave mode to host mode.
Nothing else.
Thanks for the tips. By recognize I mean that Android prompts me to confirm opening the accompanying apps when I plug in these devices to the USB port. E.g. I plug in the CarPlay dongle, Android prompts: do you want use Zbox (App) every time you use this device (Cancel or OK); I press OK and then the App stays in trying to connect mode forever.
The manufacturer has locked down USB debugging. Do you know of any apps (rooted or not) that will give me the information you pointed out?
thanks
It is unlikely that USB debugging is "locked down". More likely, its just because your USB device port is stuck perpetually in "host" mode on the wrong side of a USB hub, and therefore you can't connect to it. Try connecting to adb over IP instead.
I've never heard of any USB device on Android causing any kind of popup. That is very strange. Is it possible that the popup is being created by the program, i.e. "zbox"? Its possible that the system is sending a broadcast upon device enumeration, but the device access permissions are either wrong, or the kernel doesn't have the proper driver available.
luciusfox said:
It is unlikely that USB debugging is "locked down". More likely, its just because your USB device port is stuck perpetually in "host" mode on the wrong side of a USB hub, and therefore you can't connect to it. Try connecting to adb over IP instead.
I've never heard of any USB device on Android causing any kind of popup. That is very strange. Is it possible that the popup is being created by the program, i.e. "zbox"? Its possible that the system is sending a broadcast upon device enumeration, but the device access permissions are either wrong, or the kernel doesn't have the proper driver available.
Click to expand...
Click to collapse
Thanks again. I am including some pictures that may help explain the problem a little better. As far as the passcode, from what I can tell this unit has 3. One for the Advanced Car Settings, Developer Settings, and USB Debugging. The first 2 I found on another forum and are 123456 and the other 7890. The USB Debugging is an alphanumeric string which I haven't found anywhere, and the manufacturer refuses to release it. When I toggle the USB debugging on, I get prompted to input the passcode. I have tried a few codes but no go, the USB debugging switch goes back to the off position.
The other pictures show the USB port capabilities of the headunit. The unit has 3 USB ports: one is taken by the WiFi module, the other by a dashcam, and the remaining one is open and where I plugged in the CarPlay dongle. There is also another picture of the USB CarPlay dongle device plugged in and listed as Mass Storage Gadget. The dongle does have internal storage of a few MBs.
Finally, I include a picture of the application Zbox. This is the latest version and it starts automatically when I plug in the USB CarPlay dongle.
Well, I made some progress with the password for the USB debugging switch. To summarize:
Car Settings: 123456
Developer Options: 7890
USB Debugging: [email protected]
Now I just need to figure out how to make the USB port work properly. Any ideas? I have USB debugging access and the device is rooted.
Well according to your second-last picture, the device is being detected as UMS (Usb Mass Storage). I.e., like a usb flash disk.
VIDID of 0x0525:0xA4A5 looks to be an e-ink tablet called "Pocketbook Pro 903".
The problem may be that your "carplay dongle" is masquerading as something it isn't.
Well, the VIDID could be the problem; however, this same CarPlay dongle works fine on 2 other Android devices; moreover, a USB OTA tuner behaves the same way, meaning it does not work on the headunit but does on remix and a tablet.
Well guys, this unit is going back to the seller. After playing with it and not getting anywhere with customization and customer service, it’s out the door.
I am getting an xtron octacore px5 unit. It looks like these head units have better developer support.
Do you have the English version of 3.0 you can post?
bass_rock said:
Do you have the English version of 3.0 you can post?
Click to expand...
Click to collapse
You mean the Zbox firmware and software? if so, pm me, and I'll forward it to you.
isisyodin said:
You mean the Zbox firmware and software? if so, pm me, and I'll forward it to you.
Click to expand...
Click to collapse
Yea, and actually I was able to use the version on their site. It was al in English when I installed it and I’m now on version 3.0.2
bass_rock said:
Yea, and actually I was able to use the version on their site. It was al in English when I installed it and I’m now on version 3.0.2
Click to expand...
Click to collapse
Whats new on 3.0.2 compared to 3.0.0? Do you know what was updated?
isisyodin said:
Whats new on 3.0.2 compared to 3.0.0? Do you know what was updated?
Click to expand...
Click to collapse
According to Google Translate:
1. Optimize U disk upgrade USB recognition rate is higher
2. Optimize the phone connection, mobile phone recognition rate is better
3.carlife in the help page to add download guide
I was able to get it from here: https://translate.google.com/transl...=en&ie=UTF-8&u=http://zjinnova.com&edit-text=
bass_rock said:
According to Google Translate:
1. Optimize U disk upgrade USB recognition rate is higher
2. Optimize the phone connection, mobile phone recognition rate is better
3.carlife in the help page to add download guide
I was able to get it from here: https://translate.google.com/transl...=en&ie=UTF-8&u=http://zjinnova.com&edit-text=
Click to expand...
Click to collapse
My new Xtrons recognizes the Zbox dongle very quickly. I think it is now as quick as some of the dedicated Alpine and Pioneer units.
As far as software, crisper icons and bypassing the connection window would be nice option. It should only display when a problem occurs. One thing that is flimsy is the USB connector but no software upgrade will fix it. I am considering opening it up and soldering a better connector. Also, heat dissipation is an issue. It needs a heatsink. I may just add one when I crack it open.
I am looking forward to the next iteration with wireless CarPlay. Someday.
isisyodin said:
My new Xtrons recognizes the Zbox dongle very quickly. I think it is now as quick as some of the dedicated Alpine and Pioneer units.
As far as software, crisper icons and bypassing the connection window would be nice option. It should only display when a problem occurs. One thing that is flimsy is the USB connector but no software upgrade will fix it. I am considering opening it up and soldering a better connector. Also, heat dissipation is an issue. It needs a heatsink. I may just add one when I crack it open.
I am looking forward to the next iteration with wireless CarPlay. Someday.
Click to expand...
Click to collapse
Yea the update definitely enhanced it a lot. I used to have a pioneer and it feels close to the same now.
bass_rock said:
Yea the update definitely enhanced it a lot. I used to have a pioneer and it feels close to the same now.
Click to expand...
Click to collapse
Prior to 3.0.2, what firmware/software where you running?
Hi, I just bought new Mercedes CLA and it won't connect to my 6P, it just shows the error message in the screenshot. I am obviously connected to the USB 2 as it shows me the option to pair my device with the car as soon as I connect it. What are the other phone settings I could check? Bluetooth works I can listen to Spotify but I really care about Google maps. Thanks for any suggestions.
https://imgur.com/a/YxGTZ
If you are on Oreo, turn on USB Debugging mode and it should work fine. If you aren't on Oreo yet, ignore this.
Ups just realized I forgot to mention I am on Oreo specifically NitrogenOS rom. I had USB debugging turned on by default I disabled it because I thought it might the cause but it didn't help. I'll turn it back on then.