Solution for vent panel covering part of the screen in ford Mustang VI - Android Head-Units

Hello everyone.
Recently bought android head unit for my mustang, unfortunately I found out that the vent cover is partially covering the top portion of the screen rendering the status bar unreadable.
I found an solution for that
Over ADB type wm overscan 0,15,0,0 (adjust the 15 to whatever you want)
That will shift the whole display area but it is the only solution I could find. Is it an persistent solution i don't know.
Also to enable ADB on 7862 cpu headunits:
1.Instal ADB drivers and console on your windows pc (also I had to manually assign drivers from the driver list to the unknown device in the device manager)
2.in the head unit in settings enable developer options(3368 is the password) and debugging then change usb function to second one (right top corner three dots)
3. Connect windows laptop with the third USB connector in the android car head unit (the one which is separate) (normal usbc cable works if laptop has usbc)
4. Open windows command line and enter "adb shell"
5. Enter "wm overscan 0,15,0,0"
6. Type exit

Please move to android head units general

zachwiej said:
Please move to android head units general
Click to expand...
Click to collapse
Try again using report button. Mods don't read treads here.

Related

USB Synchronous and Asynchronous

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?

Nook Glowlight Plus USB OTG Keyboard

I managed to get into developer mode on my new NGP, there's no more "build number" as I've seen in several blog posts with the latest update you click on the Nook icon on the About page it takes you to Developer mode. I've been able to install a few apps, but here's what I'd like to do.
I'd like to plug in a USB keyboard and use it to SSH into another machine through my WiFi hotspot to do some HTML/JS/CSS text editing while I'm outdoors (at the pool, the park, etc) as my other laptops/tablets aren't visible at all outdoors with glare. This would be a nice portable solution if I could get it to work, even editing locally on the device through some editor and sending via SFTP would be just fine.
However, I can get my USB OTG cable and USB keyboard to work on my Samsung J3 phone just fine, but not on my NGP it does nothing when plugged in, keyboard caps lock doesn't activate. Is there a way to get it to work, and does it require rooting the NGP? I haven't rooted the device yet.
JohnnyFriendly said:
However, I can get my USB OTG cable and USB keyboard to work on my Samsung J3 phone just fine, but not on my NGP it does nothing when plugged in, keyboard caps lock doesn't activate. Is there a way to get it to work, and does it require rooting the NGP? I haven't rooted the device yet.
Click to expand...
Click to collapse
As a workaround I put a VNC client on it so I can access my other devices and do the typing from there, that way I can use my RPI3 as the system with a keyboard on battery power and do some Python (Django)/NodeJS/ReactJS from the NGP using it as a monitor outdoors, but if I issue the following commands via adb to rotate into landscape mode I lose input on the NGP and have to reboot:
adb shell settings put system accelerometer_rotation 0
adb shell settings put system user_rotation 1
Any ideas?
I believe I looked at this once.
At least one of the problems is that the ID pin on the micro USB connector is not connected through to the processor.
B&N has never shown any interest in putting Bluetooth in a Nook.
We'll have to see if the latest "Nook Glowlight 3" will have either OTG or BT.

Onn 7" SURF Model 100071481 GEN. 3 -Go Edition

I made the mistake of buying this tablet, so -thanks- Walmart for the unexpected, unwelcome headaches.
I got it for reading ebooks, because of the slightly larger screen compared to my phone. I saw it was limited when I got it home and turned it on, but I was still able to install a couple of book-reader apps so I thought it would be OK for my purposes. But when I plug it into my Windows 11 laptop with the USB cable the tablet doesn't show up on the computer. I have books on the laptop to transfer over.
Is there any way I can force the USB to be a data transfer connection instead of only a battery charger? There is no "use USB for" option when it's plugged in, like there is on my phone. Is there maybe a third party app I could install that will enable this -usually- normal function? Thanks, any advice and help is appreciated!
Hi @Lookstwice
Enable MTP:
Settings > Connected devices > USB > File transfer
Enable ADB:
Settings > About Tablet > Build number (7 x tap)
Settings > System > Advanced > USB debugging
Some people like Calibre on their desktop for organizing books. I believe that understands MTP.
Me, I use my adbsync.exe (in my sig) to synchronize directories. It uses ADB (duh).
Also check out this thread on the 8" which has some info that may be applicable:
https://forum.xda-developers.com/t/new-generation-3-onn-tablets-are-now-available.4464147/
Hello Renate and thanks for the advice!
I did find the developer mode and turned on USB debugging. Also, I selected File Transfer under Default USB Configuration.
Under Settings > Connected devices there is no USB on my tablet, only +Pair New Device and Connection preferences, Bluetooth.
The tablet still doesn't show up at all, when I connect via USB to my laptop.
Is there anything else I should try? Under System > Developer options maybe? How about OEM Unlocking? Disable adb authorization timeout? Thanks!
Are you sure that you have a data cable? Cheesy ones only supply power.
If you're connected to Windows enabling/disabling USB debugging should make it "bong".
To check out if I am using an inferior cable, I switched to my cellphone cable. It works fine on my cell, but no luck with this tablet. I know it makes no sense!
Thanks for your help anyway. I'm open to any ideas.
Lookstwice said:
I'm open to any ideas.
Click to expand...
Click to collapse
Sorry, I missed your response.
These devices come up in the MTK preloader whenever they reboot.
You don't actually need to load a loader or do anything.
Connect the USB. I presume you're using Windows? Does it "bong"?
Use the regular Android reboot option on the power menu.
Does it do a bunch of bong-ing and Windows flashes popups complaining about devices?
You may have a hardware problem and you need to return the device.
Wow, Renate, you've got some serious skills. Pretty impressive to turn such a low-end device into a custom machine...
I'm having trouble pulling the boot.img from this device... If anyone was willing to share the stock boot.img for the 100071481 that would be SUPER appreciated...
otherwise I'm just going to keep trying to get this MTK client thing to work although nothing seems to get the device to be visible...
Joined the forum to post this message though I hope to contribute in the future! Thanks!
@oneiromon Yes, try the (Python) MTK client
I've had problems getting that to run under Windows. I finally used a Raspberry Pi with Linux.
I was working on writing a native Windows MTK client but I haven't got that working yet.
After successfully writing a native Windows EDL (Qualcomm) client it was a bit disheartening to dive into the MediaTek gobble-dee-gook.
FWIW: I've not had luck with fastboot boot whatever.img
It works fine with fastboot flash boot whatever.img, then fastboot reset
@Renate - THANKS! for all your help with this onn tablet . Sorry I've not been keeping current on responses. I use the tablet to read books on while getting medical treatments and I was able to upload the files to my Google drive and then download to the tablet.
I'm on a Windows 11 laptop and it doesn't "bong" when I attach the tablet. I'll try the reboot option and let y'all know .
@oneiromon - I totally agree with this statement: "Wow, Renate, you've got some serious skills."
@Lookstwice I haven't got up to Windows 11, so maybe it's hiding some stuff from you.
It could also be that the 7" has some differences to the 8"
The USB/VID of my 8" is 0e8d/201c (MediaTek)
Try using UsbView.exe
See if anything appears/disappears as you plug in. For sanity, check against a known working device.
Oh, and if you're thinking reading, you really ought to consider Eink devices.
Yeah, a lot of them are annoying and underpowered, but see if you like the concept first.
I like the Onyx Poke3, but buttons/no buttons is contentious and personal.
I use no buttons but a tiny Bluetooth clicker. I love it!

ADB connected but unauthorized - Authorization box does not appear when connecting?

I have a no-name Allwinner T3 head unit. I need to enable some Accessibility options for an app, but there is no Accessibility Settings menu on this head unit. From reading the forum, I see how to set these options using ADB. With help from various posts, I have enabled debugging and ADB over WiFi. (USB on this unit only accepts devices and can't connect to a PC)
I am able to connect ADB over WiFi to head unit from PC, and also from ADB Shell apps on my phone and even locally on the head unit. However, when I connect, no authorization box pops up, and all ADB shell commands return "unauthorized". The strange thing is that if I do a reboot after connecting ADB, the authorization box does appear briefly during the reboot, but pressing OK in the box doesn't seem to do anything.
Does anyone have any idea how I can get around this without root on the head unit?

Junsun v1 pro 8/128 360 camera

Hello friends!
Did you managed to run 360 camera on Junsun V1 Pro 8gb/128gb 8667. The unit has 12pin connector, but when I choose cam type 360 the unit shows message "No Device ! Unsupport 360 view ! " and if I start the 360 view app it starts to loop the starting screen of the app.
My question is: Can the unit run 360 camera and did someone managed to run it?
Hi , I am having the same issue . I connected the 8 pin 360 harness to Junsun VI pro 64gb and no luck.
Did you get this fixed? Or find solution ?
There is also a video on YouTube on this issue.
I get the same error as in the video when I choose these settings. I don’t have 360 camera set to connect in the 12pin connector to see if the error goes away when the cameras are connected. That’s why I asked this question because I don’t want to buy the camera set just to find out it doesn’t work.
I got the 12 pin plug connected and it’s still not working .
I am not sure if I have to connect the 360
Camera( orange/ white colour wires in back cables) plug in.
4 things I can see why it’s not working
1. Wrong camera type
2. There must be a wire we are not connecting or
3. There must be a setting we are not selection or
4. This head unit doesn’t come with the 360 view processor chip
Makitaxgt said:
I got the 12 pin plug connected and it’s still not working .
I am not sure if I have to connect the 360
Camera( orange/ white colour wires in back cables) plug in.
4 things I can see why it’s not working
1. Wrong camera type
2. There must be a wire we are not connecting or
3. There must be a setting we are not selection or
4. This head unit doesn’t come with the 360 view processor chip
Click to expand...
Click to collapse
I think it's the 4th, it doesn't come with 360 view processor and that's why it is throwing the error No Device... Maybe I'll go with the back only camera option.
If you have the 360 camera set, you can try to connect all cameras as it is written in the camera diagram and see if it works. If you try it, please post the answer.

Categories

Resources