Database Info

Bluetooth on Intel

This is mostly for the new Joying INTEL units.
*********************************************
OLD STUFF: aka "BlueBalls.apk"
The bluetooth stack on these units appears to be ENTIRELY functional, but for whatever reason (don't ask me to guess at the thought processes that go into developing a head unit in China....) they HIDE the button in the Settings application that links to BLUETOOTH settings.
This is the simplest/dumbest application anyone has ever written.
The code inside it is literally JUST the following THREE LINES;
Code:
Intent intentOpenBluetoothSettings = new Intent();
intentOpenBluetoothSettings.setAction(android.provider.Settings.ACTION_BLUETOOTH_SETTINGS);
startActivity(intentOpenBluetoothSettings);
It launches the bluetooth settings activity that Joying has hidden.
**************************************************
NEW STUFF!!!!
Ok, so the thing is, even with blueballs installed, the process of tethering is somewhat... MANUAL. On both sides of the connection -- data source, typically your phone, and head unit. Wouldn't it be nice to AUTOMATE things a little bit?
While there are some guides and hackish programs that suggest that they can get this done, for instance http://forum.xda-developers.com/showthread.php?t=2574310 -- the reality is that NONE of these solutions will actually WORK, nor are they simple to configure, nor are they reliable. They are a BIG UGLY MESS.
So I decided to do it myself, in a nice, clean, self-contained Android application.
The result is the BluetoothTethering.apk attached below.
Here is description of this program;
Start up the program, and you are presented with a screen with some buttons, switches, and spinners.
FOR THE CAR RADIO SIDE:
At the top of the screen is a spinner containing a list of all paired bluetooth devices. If you select one of those devices, and hit the "CONNECT PAN" button, it will try to connect to that device as a bluetooth tethering client. If you enable the switch "Auto Connect PAN", then whenever it connects to that device (the one currently showing in the spinner), it will AUTOMATICALLY try to connect PAN. The application does NOT need to be running for this to occur, since there is a receiver registered in the application's manifest.
The next button down, "Launch Bluetooth Settings", just launches the standard Android Settings --> Bluetooth activity. This is the same as what BlueBalls does, so you don't need to install both.
FOR THE PHONE SIDE:
At the bottom, there is a button "START SERVICE", hit that button on your phone, and it should start up bluetooth tethering service.
And the switch "Auto Bluetooth Tethering", means that every time the bluetooth device turns ON, it will automatically enable bluetooth tethering. Again, it receives an intent and does the work in the background, so the application need not be open.
CAVEATS!!!
Ok, this is where the fun begins! Starting with Android version 3.1, newly installed applications are given a default state of "stopped", in which they are unable to receive any broadcast intents. In order to get the application out of the stopped state such that it can receive broadcast intents, it needs to be manually run first. A second part of this feature, is that if an application is force stopped, it is RETURNED to the "stopped" state. This becomes a problem on at least some Chinese Android car radios. In particular, it is a problem on at LEAST Joying units (possibly also others). In these units, when the car ignition is turned off, after a few minutes they go to SLEEP mode so that they don't drain the car's battery. The problem is that just before going to sleep, everything running is FORCE STOPPED, sending everything, INCLUDING BluetoothTethering.apk, into a "stopped" state, thus disabling the application's ability to receive the broadcast intent necessary in order to activate PAN!
Workaround: NOW TESTED AND VERIFIED FUNCTIONAL... provisioning the application with enhanced privileges, by installing it into /system/priv-app/, will allow it to avoid the "stopped" state, or at least allow it to receive broadcast intents regardless of that state. After all, there are many system receivers that fire as expected, even if you don't manually open the applicable application manually!
If you are going to do this (which you MUST on Joying Intel car radios, and possibly other MTCD Intel car radios), the steps are as follows;
Connect it and a laptop (with adb installed) to a common wifi network. This CAN be a hotspot running on the head unit or laptop, or even your PHONE. Just as long as they are all on the same network! Find the IP address of the head unit. If the head unit is connected to a different AP rather than hosting a hotspot, you can look in wifi --> 3dots menu --> advanced. If the head unit IS the hotspot, then look at your laptop (terminal --> ifconfig) and find ITS IP address (for example, 192.168.30.123) and change the last byte to a "1" to find the head unit's IP address, in this case, it would be 192.168.30.1.
In a terminal on the computer, run following;
Code:
adb connect <ip address of head unit>
adb push BluetoothTethering.apk /sdcard/
adb shell
$ su
# mount -o remount,rw /system
# mkdir /system/priv-app/BluetoothTethering
# cp /sdcard/BluetoothTethering.apk /system/priv-app/BluetoothTethering/
# chmod 755 /system/priv-app/BluetoothTethering
# chmod 644 /system/priv-app/BluetoothTethering/BluetoothTethering.apk
# sync
# reboot
Now the application is installed with extra privileges, so it will respond properly to the broadcasts when the unit powers back on after sleeping.
Note: This application will not currently work with a typical Android TABLET. The reason is that despite being "paired" to your phone for tethering, the two devices do not automatically establish a connection when they are in proximity. A car radio and phone DO automatically establish a connection when in proximity in order that your phone calls will be directed over bluetooth. I will be looking into whether or not there is some battery efficient mechanism for accomplishing this, but I am not hopeful.
I am also aware that the auto-tethering setting is currently limited to a selection of ONE bluetooth device. If two people share a car, this may be inadequate. My intention is to create a LIST of devices that it can try connecting to. CANNOT just try ALL devices, since obviously it would be silly to try to establish a PAN connection with your OBD dongle.
There is also a potential weakness where if the bluetooth connection is established BEFORE the PHONE has bluetooth tethering enabled, the head unit will just try once to connect PAN, fail, and give up. I intend to have it periodically retry if the connection is established to an enabled device, but PAN failed.

Going to test it this afternoon. I think it will work.....
By the way: many other settings are hidden (accounts, sync, ...). They even have a second "settings.apk" (only 1 MB)....wtf.....? A lot of overlays too (we should get rid of them)

Interesting.
I'll have to rip a few of those apart and see what is up with them.
Hopefully, I'll have my 128N2's by next week.
FYI: Brainless "Candy" at Joying is really giving me the runaround when asking her about getting into recovery. Told her even to ask their technical people for the answer.... her solution? Just wait an extra hour before responding to the email with the same nonsense "do not worry, it will not fail to boot into Android, this is our latest very much more stable"
I *really* hate dealing with chinese manufacturers.
Wonder how she's going to respond to my request for kernel source code? Probably give me a link to kernel.org....

The blueballs.apk is working.

lol anyone wanna try this on a RK3188 unit

thanks doitright..
My UL128N2 from joying in in transit. hopefully receiving it in a week. I will try this in my unit and post you the feedback:good::good:.
May be this simple app can make UL128N2 to connect to 'any brand' BT OBD2 adapter.
doitright said:
This is mostly for the new Joying INTEL units.
The bluetooth stack on these units appears to be ENTIRELY functional, but for whatever reason (don't ask me to guess at the thought processes that go into developing a head unit in China....) they HIDE the button in the Settings application that links to BLUETOOTH settings.
This is the simplest/dumbest application anyone has ever written.
The code inside it is literally JUST the following THREE LINES;
Code:
Intent intentOpenBluetoothSettings = new Intent();
intentOpenBluetoothSettings.setAction(android.provider.Settings.ACTION_BLUETOOTH_SETTINGS);
startActivity(intentOpenBluetoothSettings);
It launches the bluetooth settings activity that Joying has hidden.
Note: It works perfectly on my Nexus 6, but I don't have a Joying INTEL head unit yet (two UL128N2's on order). It *should* be fine, unless they did something REALLY weird, in which case I have another way to issue the intent that may work.
Click to expand...
Click to collapse

masri1987 said:
lol anyone wanna try this on a RK3188 unit
Click to expand...
Click to collapse
Not even remotely the same thing.

leonkernan said:
Not even remotely the same thing.
Click to expand...
Click to collapse
I know, just don't understand why the CPU makes the native ROM different for

masri1987 said:
I know, just don't understand why the CPU makes the native ROM different for
Click to expand...
Click to collapse
The Bluetooth was a separate module on the RK boards, it's on the processor board on the Sofias.
They have completely different driver software requirements.

leonkernan said:
The Bluetooth was a separate module on the RK boards, it's on the processor board on the Sofias.
They have completely different driver software requirements.
Click to expand...
Click to collapse
Well, you know something... just because the bluetooth module is on a separate board does not mean that it is necessarily "wrong". Consider the fact that you can plug a bluetooth USB dongle into ANY normal laptop/desktop/server and have it work correctly! The thing is, there ARE a bunch of high speed ties between the SoC through to the MCU board, and we know from the fact that things like torque CAN work on the rockchip/arm/mtcX units that BT SPP profile is definitely able to make it through to the bluetooth device itself. Also the fact that WIFI works on those units supports the idea that they aren't completely broken (wifi and bluetooth are on the same physical RF chip, since they use the same spectrum and need to coordinate with each other in order to operate correctly).
What this really boils down to, is that very likely, those older arm boards *actually could* be programmed to have correctly working bluetooth.
However, there IS a difference in the software. While on the RK/arm boards, they have MODIFIED the settings/bluetooth screen to be horribly broken, on the INTEL boards, they have simply deleted the link to the settings/bluetooth activity from the main settings activity, and otherwise left it fully intact. So really, there are TWO possibilities here in just how they butchered it; (1) They added a new settings/bluetooth screen and changed the link to point to it, which could mean that the original one is actually still there UNBROKEN, or (2) They actually butchered the settings/bluetooth activity.
If they used approach (1), then this apk ***COULD ACTUALLY WORK*** on them. However, if they used approach (2), then it would definitely be necessary to build a new settings/bluetooth screen with the appropriate permissions to change bluetooth settings, and installed in the system partition (i.e., root needed).

Hi,
My Joying JY-UL135N2 just arrived. So far so good with the functionalities except Bluetooth OBD2. I have used 'blueballs.apk' and the Bluetooth settings screen appeared which was not visible otherwise. I could find my BT OBD2 device in the device list with the name 'CHX'. I tried to pair to it and unfortunately error popped up " Couldn't pair with CHX because of an incorrect PIN or passkey".
In the BT settings screen, there is no option to specify PIN or passkey. May be the unit sends some JOYING pass key or PIN to the device without giving an option for the user to specify one.
Is there any way to send an user defined PIN or pass key to Bluetooth device?
doitright said:
This is mostly for the new Joying INTEL units.
The bluetooth stack on these units appears to be ENTIRELY functional, but for whatever reason (don't ask me to guess at the thought processes that go into developing a head unit in China....) they HIDE the button in the Settings application that links to BLUETOOTH settings.
This is the simplest/dumbest application anyone has ever written.
The code inside it is literally JUST the following THREE LINES;
Code:
Intent intentOpenBluetoothSettings = new Intent();
intentOpenBluetoothSettings.setAction(android.provider.Settings.ACTION_BLUETOOTH_SETTINGS);
startActivity(intentOpenBluetoothSettings);
It launches the bluetooth settings activity that Joying has hidden.
Note: It works perfectly on my Nexus 6, but I don't have a Joying INTEL head unit yet (two UL128N2's on order). It *should* be fine, unless they did something REALLY weird, in which case I have another way to issue the intent that may work.
Click to expand...
Click to collapse
---------- Post added at 02:03 PM ---------- Previous post was at 01:55 PM ----------
hi, doitright,
error screenshot attached.
{
"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"
}
aneesp said:
Hi,
My Joying JY-UL135N2 just arrived. So far so good with the functionalities except Bluetooth OBD2. I have used 'blueballs.apk' and the Bluetooth settings screen appeared which was not visible otherwise. I could find my BT OBD2 device in the device list with the name 'CHX'. I tried to pair to it and unfortunately error popped up " Couldn't pair with CHX because of an incorrect PIN or passkey".
In the BT settings screen, there is no option to specify PIN or passkey. May be the unit sends some JOYING pass key or PIN to the device without giving an option for the user to specify one.
Is there any way to send an user defined PIN or pass key to Bluetooth device?
Click to expand...
Click to collapse

@aneesp --> Use the built-in BT app to connected (first time) with your OBD device. Maybe you have to change the PIN to 0000 or 1234 to get a paired connection (use the built-in BT app to change the PIN!!!)

aneesp said:
Hi,
My Joying JY-UL135N2 just arrived. So far so good with the functionalities except Bluetooth OBD2. I have used 'blueballs.apk' and the Bluetooth settings screen appeared which was not visible otherwise. I could find my BT OBD2 device in the device list with the name 'CHX'. I tried to pair to it and unfortunately error popped up " Couldn't pair with CHX because of an incorrect PIN or passkey".
In the BT settings screen, there is no option to specify PIN or passkey. May be the unit sends some JOYING pass key or PIN to the device without giving an option for the user to specify one.
Is there any way to send an user defined PIN or pass key to Bluetooth device?
---------- Post added at 02:03 PM ---------- Previous post was at 01:55 PM ----------
hi, doitright,
error screenshot attached.
Click to expand...
Click to collapse
Ok, so what it is sounding like, is that the pin prompt on the head unit is broken, causing it to default to one specific user-set pin code for pairing. This user-set pin code is controllable via the chinese "bluetooth" application -- go there and set the pin to match your device, then go back into the "real" bluetooth settings menu and try again from there.

ok..
I will do that way and give you feed back..
doitright said:
Ok, so what it is sounding like, is that the pin prompt on the head unit is broken, causing it to default to one specific user-set pin code for pairing. This user-set pin code is controllable via the chinese "bluetooth" application -- go there and set the pin to match your device, then go back into the "real" bluetooth settings menu and try again from there.
Click to expand...
Click to collapse

@doitright and @MMTK84,
you saved my day and night. It worked. I entered my BT OBD2 PIN "6789" in the Chinese "Bluetooth" application (stock) and then used blueballs.apk to pair CHX. it paired smoothly. Torque could successfully establish connection and I am very happy about this unit JY-UL135N2. BT in the unit is fully functional. simultaneous playback of BT music and OBD2 is possible. Bluetooth hardware which is on on the SOC is perfect and only chinese software interface is making the issue. Any way we got the work around for this.
Please note that I didnt go for any firmware update from JOYING to make this happen. Yesterday I received the unit shipped with factory firmware MCU Version 2016-10-31 14:30:43 JY_(NOR)_90_C9_7706_5009_CAN(GX)_Newlap.
:highfive::good::good::good::good:
doitright said:
Ok, so what it is sounding like, is that the pin prompt on the head unit is broken, causing it to default to one specific user-set pin code for pairing. This user-set pin code is controllable via the chinese "bluetooth" application -- go there and set the pin to match your device, then go back into the "real" bluetooth settings menu and try again from there.
Click to expand...
Click to collapse

aneesp said:
@doitright and @MMTK84,
you saved my day and night. It worked. I entered my BT OBD2 PIN "6789" in the Chinese "Bluetooth" application (stock) and then used blueballs.apk to pair CHX. it paired smoothly. Torque could successfully establish connection and I am very happy about this unit JY-UL135N2. BT in the unit is fully functional. simultaneous playback of BT music and OBD2 is possible. Bluetooth hardware which is on on the SOC is perfect and only chinese software interface is making the issue. Any way we got the work around for this.
Please note that I didnt go for any firmware update from JOYING to make this happen. Yesterday I received the unit shipped with factory firmware MCU Version 2016-10-31 14:30:43 JY_(NOR)_90_C9_7706_5009_CAN(GX)_Newlap.
:highfive::good::good::good::good:
Click to expand...
Click to collapse
Glad to hear it!
Once I get my head units delivered (can you believe that I'm writing software to fix problems on these things before even owning one? LOL), I will look into it a bit more deeply. There is probably an intent being fired to prompt for the BT pin, but the receiver (or its registration) has probably been deleted by china.

wow... many thanks for your great support. :highfive::victory::victory:
Do you have an idea how to boot in to stock recovery of this unit. I just wanna to take a nandroid backup of the unit. I t seems I have to root the unit before doing it.
doitright said:
Glad to hear it!
Once I get my head units delivered (can you believe that I'm writing software to fix problems on these things before even owning one? LOL), I will look into it a bit more deeply. There is probably an intent being fired to prompt for the BT pin, but the receiver (or its registration) has probably been deleted by china.
Click to expand...
Click to collapse

aneesp said:
wow... many thanks for your great support. :highfive::victory::victory:
Do you have an idea how to boot in to stock recovery of this unit. I just wanna to take a nandroid backup of the unit. I t seems I have to root the unit before doing it.
Click to expand...
Click to collapse
I actually just started a thread to compile all the known methods of booting into recovery. Nothing firm on that front, however, obviously you CAN "reboot" to recovery.
Good news for you about root though! Joying Intel devices ship WITH ROOT. The only thing you need to know about it, is that it is restricted to access through ADB. So turn on adb over wifi, adb connect to the ip address of the head unit on your LAN, adb root, and adb shell. You can then issue your "reboot recovery" command.
ADB over USB should also work, but you'll need to find the place in their menus where you can control the USB mode switch, and of course, you'll need a USB-A-male to USB-A-male cable.

Hi doitright,
I followed your steps for reboot to recovery using adb over wifi. I could issue the command "reboot recovery" and unit rebooted. After few seconds showing the boot logo, the android logo screen appeared with "No command" after two seconds, No command changed to "Error!". From earlier threads, I got an idea to press power button when we get this error screen. |I did so, but nothing happened. I was little bit afraid if the device is soft bricked. But, upon pressing reset button, unit booted normally.
Any clue?
doitright said:
I actually just started a thread to compile all the known methods of booting into recovery. Nothing firm on that front, however, obviously you CAN "reboot" to recovery.
Good news for you about root though! Joying Intel devices ship WITH ROOT. The only thing you need to know about it, is that it is restricted to access through ADB. So turn on adb over wifi, adb connect to the ip address of the head unit on your LAN, adb root, and adb shell. You can then issue your "reboot recovery" command.
ADB over USB should also work, but you'll need to find the place in their menus where you can control the USB mode switch, and of course, you'll need a USB-A-male to USB-A-male cable.
Click to expand...
Click to collapse

aneesp said:
Hi doitright,
I followed your steps for reboot to recovery using adb over wifi. I could issue the command "reboot recovery" and unit rebooted. After few seconds showing the boot logo, the android logo screen appeared with "No command" after two seconds, No command changed to "Error!". From earlier threads, I got an idea to press power button when we get this error screen. |I did so, but nothing happened. I was little bit afraid if the device is soft bricked. But, upon pressing reset button, unit booted normally.
Any clue?
Click to expand...
Click to collapse
Congrats. You successfully made it into recovery. Not sure what to tell you at this point, since factory recovery is what factory recovery is.
Going from there to the regular recovery menu on MOST devices (remember that I don't have one of these yet, so I haven't been able to play with it yet) involves more than just the power button. Typically it is hold power + something like volume up. You could also try mashing on a USB keyboard and see if anything happens.

USB Audio

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:

Android 9.0, MTCE MX2 PX30 head unit bricked?

I have Android head unit sold by Witson, processor PX30, MX, MTCE. I did a big mistake and give rw permissions (with ES explorer) for all folders for my rooted head unit... After restart the unit did not work anymore. There is booting image on the display for appox. 40 second, after this unit shut's down. At least it seem to do so because at same time usb ports lost their power. So unit is not totally dead/ bricked but it wont boot or I can't enter recovery mode anymore.
My unit do not have any buttons (no hard or soft buttons) and there is no RST button.
I have try to enter recovery mode several times by keyboard with different key combinations ( alt / right alt + print scr + E or I) but with no luck. I also tried to flash firmware with SD-card or with USB-stick but without success. I also removed MCU or SOM and tried to flash it by OTG method but my SOM did not respond (PC did not recognice it) and I do not know how PX30 can be forced to Maskrom -mode?
Is there anything to anymore? How I can save my PX30 board, any good comments, please?

Timpuli said:
I
have Android head unit sold by Witson, processor PX30, MX, MTCE. I did a big mistake and give rw permissions (with ES explorer) for all folders for my rooted head unit... After restart the unit did not work anymore. There is booting image on the display for appox. 40 second, after this unit shut's down. At least it seem to do so because at same time usb ports lost their power. So unit is not totally dead/ bricked but it wont boot or I can't enter recovery mode anymore.
My unit do not have any buttons (no hard or soft buttons) and there is no RST button.
I have try to enter recovery mode several times by keyboard with different key combinations ( alt / right alt + print scr + E or I) but with no luck. I also tried to flash firmware with SD-card or with USB-stick but without success. I also removed MCU or SOM
and tried to flash it by OTG method but my SOM did not respond (PC did not recognice it) and I do not know how PX30 can be forced to Maskrom -mode?
Is there anything to anymore? How I can save my PX30 board, any good comments, please?
Click to expand...
Click to collapse
Good efforts made in trying to restore.
If your unit is an MTC(D/E) and the OTG cable is correct, with USB powering OK, forcing MASKROM should enable SOM connectivity via USB. To force MASKROM, typically there are two pads that must be shorted while powering on the SOM while connected to OTG.
Take a close look at the board for pads close to the eMMC/NAND. Attach a high res image here for further help.

Thank you for the comments so far. Yes, unit if MTCE and I think that OTG cable is fine also. I have even tried it with different resistors but SOM is not recognized by PC...
Here is some links for the pictures, it would be great if someone could help me find points where SOM can be forced to MASKROM mode.
https://drive.google.com/file/d/1WVujL00jDu6RYLzpD7xxoNL1gY_15R2-/view?usp=sharing
https://drive.google.com/file/d/1bF6Kxu1k3DtSquUenu508qXxL-CI2hGx/view?usp=sharing
https://drive.google.com/file/d/1ioM8vtH-zuU5seyLaBnt2qdzN02kNfNW/view?usp=sharing
{
"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"
}

Timpuli said:
Thank you for the comments so far. Yes, unit if MTCE and I think that OTG cable is fine also. I have even tried it with different resistors but SOM is not recognized by PC...
Here is some links for the pictures, it would be great if someone could help me find points where SOM can be forced to MASKROM mode.
https://drive.google.com/file/d/1WVujL00jDu6RYLzpD7xxoNL1gY_15R2-/view?usp=sharing
https://drive.google.com/file/d/1bF6Kxu1k3DtSquUenu508qXxL-CI2hGx/view?usp=sharing
https://drive.google.com/file/d/1ioM8vtH-zuU5seyLaBnt2qdzN02kNfNW/view?usp=sharing
Click to expand...
Click to collapse
Hi, excellent hi-res images. I have annotated one of the images I believe are the Maskrom pads.
Sounds like you've had a thorough read through OTG threads, which explain the sequence - basically short while device is being plugged in/powered on by USB. nice one. Let me know how you get on.

marchnz said:
Hi, excellent hi-res images. I have annotated one of the images I believe are the Maskrom pads.
Sounds like you've had a thorough read through OTG threads, which explain the sequence - basically short while device is being plugged in/powered on by USB. nice one. Let me know how you get on.
Click to expand...
Click to collapse
Success!!! Thank you so much to encourage me! MASKROM pads confirmed for PX30, after shorting those pads SOM went directly to MASKROM and I was able to restore my system. Only problem is that only FW image what I found was Android 8.1 and my "bricked" android was 9.0 But even this is much better than bricked unit
I made also some other modifications before trying to MASKROM-mode and I'm not sure were there other issues before. Anyway, I made new OTG cable with a little bit thicker wires. I also changed resistor values from 12k // 22k to 6k // 11k. And finally I made dedicated pliers to short MASKROM pads.
Is there anything else to do for upgrade to Android 9 than use ModInstallerPro by Hal9k?
Thank you so much marchnz!!! You are great!

HELLO
please give me the .img software you wrote through otg / maskroom for px30
Timpuli said:
I have Android head unit sold by Witson, processor PX30, MX, MTCE. I did a big mistake and give rw permissions (with ES explorer) for all folders for my rooted head unit... After restart the unit did not work anymore. There is booting image on the display for appox. 40 second, after this unit shut's down. At least it seem to do so because at same time usb ports lost their power. So unit is not totally dead/ bricked but it wont boot or I can't enter recovery mode anymore.
My unit do not have any buttons (no hard or soft buttons) and there is no RST button.
I have try to enter recovery mode several times by keyboard with different key combinations ( alt / right alt + print scr + E or I) but with no luck. I also tried to flash firmware with SD-card or with USB-stick but without success. I also removed MCU or SOM and tried to flash it by OTG method but my SOM did not respond (PC did not recognice it) and I do not know how PX30 can be forced to Maskrom -mode?
Is there anything to anymore? How I can save my PX30 board, any good comments, please?
Click to expand...
Click to collapse

Sorry for late answer, I haven't noticed this... I hope that you have already find a proper .img file for yourself, but if not, I just downloaded some Android 8 installation package from 4PDA site. And when you unzip this package, usually there is .img file also. I haven't found any .img file to Android 9, so can't help with that, sorry.

Hello! @Timpuli, I am in the same kind of a problem that you had.Can you help me? I made the OTG cable but the SOM in the thread has 2 more rows and I don't know how to connect it to my PX30.Here's how I tried.Thanks!

Look at SOM board picture in topic https://forum.xda-developers.com/an...px3-5-headunit-mod-recover-flash-som-t3766892
In the third picture you can see that there is "two pins missing" at the left end of the socket... And if I remember right, in my PX30 SOM, there was socket all the way, like you wrote. So, you must take those missing pins into account, or start to calculate right pins starting from the pin 5...
Edit. Pin no. 1 is in top row/ left one pin. Pin. no 2 is in bottom row/ left one pin. And so on..

Timpuli said:
Look at SOM board picture in topic https://forum.xda-developers.com/an...px3-5-headunit-mod-recover-flash-som-t3766892
In the third picture you can see that there is "two pins missing" at the left end of the socket... And if I remember right, in my PX30 SOM, there was socket all the way, like you wrote. So, you must take those missing pins into account, or start to calculate right pins starting from the pin 5...
Edit. Pin no. 1 is in top row/ left one pin. Pin. no 2 is in bottom row/ left one pin. And so on..
Click to expand...
Click to collapse
So, they are like that?
PIN1 | PIN3 |
PIN2 | PIN4 |
And so on? On my SOM. Also, can you take a look at my cable, is it okay? Here is how I tried, I also tried to move all connections two rows to the right, still nothing.Also when I connect the orange leads to the SOM voltage goes from 3.14 to 1.7V. Is this normal? Thanks a lot for the fast reply, gotta get you a beer!

Yes, pins goes like that.
And if you make connection like in the picture it is wrong. You have to move pins two rows to the right, thats correct.
Your cable looks fine to me. I can't remember voltage values anymore, sorry.
I have some difficulties also and that's why I have to change resistor values from 12k and 22k to 6k and 11k. Also it might take couple of tries to enable to maskrom-mode.

Look at thread
https://forum.xda-developers.com/an...px3-5-headunit-mod-recover-flash-som-t3766892
again. So, there is said that voltage should be between 1.8 to 3.3V to 'tell' the SOM to go into OTG recovery mode. So, maybe 1.7V is too low...

Timpuli said:
Look at thread
https://forum.xda-developers.com/an...px3-5-headunit-mod-recover-flash-som-t3766892
again. So, there is said that voltage should be between 1.8 to 3.3V to 'tell' the SOM to go into OTG recovery mode. So, maybe 1.7V is too low...
Click to expand...
Click to collapse
It is 3,14V when it is not plugged to the SOM. when I plugged in it drops.Anyway, I am gonna try again! Thanks, if I have more questions I will ask you! I really appreciate that you helped and replied really fast.

Ok, I hope for the success. I assume that you have installed drivers already? Sequence to enter masrom-mode is:
1. Short maskrom mode pads and keep those shorted.
2. Plug in OTG-cable to usb-port...
3. When windows detects SOM-board remove shorting from the pads.
It might take several tries to have success to enter maskrom-mode. Have you checked is SOM-board detected in Windows device manager?

Yes I did. I will try again with MASKROM and check voltages on orange leads.I will keep you updated.

@Timpuli, I got it in MaskROM mode!Successfully connected, now I am searching for a rom with a .img. Once I find I will flash it and see if it works!Thanks so much!

Question. On the core board does anyone know what pins are for UART? slightly off topic but I've managed to boot a Ubuntu kernel on my px30 but it's a bit glitchy so would like to work out what pins are for serial console

Does anyone know what's happening here?.
So I've tried to flash a custom OS using maskrom, but the device keeps cutting the connection anywhere from 40% to 60% complete - it's driving me insane having tried about 15 times now to get it to flash.
Attached is my current maskrom setup....I'm trying to flash a Ubuntu based OS based on the Firefly px30 system.
Should all that fail, does anyone have the necessary files to maskrom my way back to android?

UKSFM99 said:
Does anyone know what's happening here?.
So I've tried to flash a custom OS using maskrom, but the device keeps cutting the connection anywhere from 40% to 60% complete - it's driving me insane having tried about 15 times now to get it to flash.
Attached is my current maskrom setup....I'm trying to flash a Ubuntu based OS based on the Firefly px30 system.
Should all that fail, does anyone have the necessary files to maskrom my way back to android?
Click to expand...
Click to collapse
MCU cuts power after a period.
Remove board from mainboard, use jig instead.

marchnz said:
MCU cuts power after a period.
Remove board from mainboard, use jig instead.
Click to expand...
Click to collapse
Ok will try.
I can't get it to work though, what pins should I use for the JIG.
Currently I have the following:
1 - 5V
3 - GND
20,28 - 15k resistor (1.2V)
29,30 - USB Rx, Tx

Android Whiz-kid required!

Hi all
I know this is regarding a headunit but I feel like its more of a "generic" Android Software issue, so was hoping someone knew in here- i havent had any luck in the Android Headunits forum...
Basically, my Android Headunit is driving me mad!
Sometimes (99% of the time) when i switch my car on in the morning the headunit will switch on as normal, but either the touchscreen will not work at all, or will work for a few seconds and then stop responding completley. It will then sometimes either start working again after a while, or after a few resets (via the hardware button). However, once it starts working again you can bet your bottom dollar it wont work again the next day.
The headunit is still working, because i can change the volume with the SWC and I also have a mouse connected via USB so i can control it, access settings etc.
My question is that is it likely a background Android process that activates once the headunit has been to sleep is responsible for causing the touchscreen to become unresponsive?
Things I have tried:
* Hard Reset (I dont think this is a full hard reset though because it keeps evidence of previously installed apps, folders etc on the internal flash)
* Touch screen calibration
* Removing sim card and other (USB) connected devices
Things I cannot do:
* I have asked for the firmware from the seller but he is not responding
Things I will consider doing
* Installing another (preferably rooted) firmware, but I dont know which are compatiable
This is the headunit:
https://www.aliexpress.com/item/32968859327.html (the 4GB 64GB one)
Device Specs
Processor type
Octa-sp9853i
Android Vesion
10
MCU version
Ts9V.4.3-100-404-A4C695-210112(MM031)
CAN version
HO63FD01SA-171219
System Version
V.11.1.2_20200915.111524_XHCN9-V-X
Memory
4GB/64GB
DSP w/optical out
I am literally at the point of offering a small bounty to anyone who can help me fix this issue.

[Junsun V1] Unable to use CarPlay over USB

Hi all,
First, thank you for all the job everyone does here. I'm new to this forum, so I hope I am posting in the right category and I respect the post format.
I am posting here because I recently bought a Junsun V1 (non pro) for my Mazda 2 on Aliexpress, but after one week of back and fourth with their support chat, I am unable to use Carplay over USB (not even talking about wireless).
First, I wasn't even seeing their "phonelink" app icon, which is needed to use Carplay over USB. After some exchanges with the support, they suggested me to "show" the icon using the secret menu 8888 beucase it was apparently hidden by default. And indeed, it was. So I was able to get the icon to show on the home screen, but every time I tried to open it, it would show "loading..." for ~15 seconds then close itself without saying anything.
I am using the original 4-pin USB cable, and also tried with the 6-pin one, without success. I also tried several lightning cables, and even with another iPhone (but my actual phone can use carplay in another car which had built in) but I can't manage to get it working. I have tried messing with the advanced USB settings, enabling carplay in the "engineer menu" (code 8877) enabling debug, but nothing works. I have also tried doing a factory reset, and the Junsun support sent me a firmware update, which didn't solve the problem.
I have found this post on XDA Developers of somebody mentioning the same kind of issue, but they seem to have fixed it by doing a factory reset, but in my case that didn't change anything.
I'm a little desperate to find a solution to this problem and even wonder if my unit doesn't have the necessary hardware to run CarPlay as apparently, the non-pro Junsun V1 didn't support it previously.
that's why I came to see if anyone has already had or seen this problem and would have a possible solution to give me. Otherwise I will turn to buying an external CarPlay dongle.
Thanks in advance and best regards !

Is it an MTCD type device, post Android system info with MCU version.
Don't hope, have a read through the forums.