yashsingh1/xdaforums huggingface dataset:
[Android Head-Units] Tijgerd:
DVD player not working

Hi Bazanovv!!

I have THIS (www aliexpress com/item/100-Android-4-4-Car-Audio-GPS-Navigation-2DIN-Car-Stereo-Radio-Car-GPS-Bluetooth-USB/32702074730.html?spm=a2g0s.9042311.0.0.LphuTG) radio!

I successfully upgraded to the latest MCU and Android version (given in these forum posts)

The only three downsides are:

- Every now and then an app fails and quits out of nowhere, feels to me like a RAM problem...

- The dvd player does not work anymore (used to work with the original MCU and Android version), I now get a message like "does not support DISK function".

- When I turn on the headlights the screen gets way too dark.. but changing the settings do not seem to fix the problem.

All of this feels to me like having the wrong MCU firmware installed, do you have any sollution?

Thanks in advance!
[Android Head-Units] bazanovv:
Hi, Tijgerd!

1) Your head unit do have a 1Gb RAM, right? This is, unfortunately, a bit low for the 6 Android. Memory pressure will be quite high, especially then maps or navigation software is working. Please try to uninstall some installed and autostarted programs (like messangers, email, etc, unneeded navigation/maps), if any. Also please check the CPU (SOC) temperature by CPU-Z or other similar tools. If it is constantly above 80-90C, you may need to think about additional CPU cooling, like heatsink or fan. See posts above for details, and ask, if somethin is unclear. This problem have nothing to do with the MCU.

2) This is related to the MCU, not firmware, but configuration. Please go to the engineering menu (tap 3 times Kernel version - OS version, Kernel version - OS version, Kernel version - OS version on about screen), and set checkmark (v) near "Disk" (or DVD) in "Module" menu, and, may be, some others - according to your hardware configuration, exit and reboot head unit. Photos here http://4pda.ru/forum/index.php?showtopic=806442&view=findpost&p=60603117 Be careful before changing settings, which purpose or meaning you don't know, especially panel/screen/touch settings. You may need to use USB mouse and external display to restore incorrect display or touch settings.

MCU settings (hardware configuration) is reset during some major firmware version updates, so it's always better to record them before update.

3) This head unit do have two display brightness levels, one for the day, and one for the night, switched by the hardware - input Illumination and MCU. Also it have a brightness level setting in the engeneering menu, please ajust setting for "Level1" for the night mode, screen here http://4pda.ru/forum/index.php?s=&showtopic=806442&view=findpost&p=60118506 You may ajust other levels as well, this will define brightness level for the Android slider. Again, it is no need to flash the MCU - only change it's settings, brightness work ok in any version available.

As an alternative, find the wire named "ILL" (illumination), usually orange, on the head unit main connector. It may go to the car connector, or to the CANbus adapter. Disconnect and isolate it. Now Head Unit will always work in the "day mode". Use applications like "Twilight" to manage screen brightness, if needed. Warning: such applications do not manage actual brightness, but add some filter above the display image. So if some application, or, usually, Android security settings will warn you about screen filter or something like this - please switch it off temporary.

PS For this head unit and other generic Allwinner T3 models please read the FAQ in the top of this forum topic, use Google Translate on it. It is the most detailed information source available. http://4pda.ru/forum/index.php?showtopic=806442
[Android Head-Units] Tijgerd:
Omg! thank you SO much!
[Android Head-Units] meir__:
Music issues

Hey guys, sorry Im new to Android Head Units and recently got this Bonroad unit with Quad core T3 2Gb / 32GB and I need help!!!

I seem to have few of issues with it:

- AUX-in doesn't seem to work properly, sound come out but all scrambled.

- Bluetooth connects, but when playing music, it has a little static noise.

- When I connect iPhone via USB, no music is coming out...

Can I solve above issue via software update?

Over the years I got use to plugin iPhone into USB and playing music - very convenient, but is this even supported by Android Head Units? And Bonroad more specifically?

Thank you!
[Android Head-Units] Sheadexx:
Hello ! I Have one Allwinner Head unit. I can't enter, the factory settings menu, because i dont know the password. Can anybody help me?

I Tryed many codes but does not work.

I think the only way, when i can go to the Recovery menu and make one Factory Reset. How can i restart the device to recovery mode? Or How can i other way delete the Factory settings menu password ? Pllease HELP . MAny thanx

Pics from the navi : https://www.google.hu/search?q=CMP1001T3&source=lnms&tbm=isch&sa=X&ved=0ahUKEwiO9L7Y1c3XAhUIJuwKHXSAB0gQ_AUICygC&biw=1600&bih=761#imgrc=ivP9qTG7mt_dPM:
[Android Head-Units] bazanovv:
Model discussed in this topic does not have any passwords in any factory menus. But there are at least two other types of Allwinner T3 head units, both with NON COMPATIBLE firmware and hardware. One (named New version) here http://4pda.ru/forum/index.php?showtopic=837879 and one, named K2001, here http://4pda.ru/forum/index.php?showtopic=840515 You may use Google Translate to, huh, translate very useful FAQ found on this links and compare photos with yours.

Passwords for "New version" factory menu is 123456, other passwords here.

Passwords for "K2001" - 1617 or 16176699 (for extended skin settings) or sometimes 66668888 or 3368 or others.

BTW, there are lots of other, different head units on Allwinner chips - like Allwinner R16 and Allwinner T8 (new). It's better to post some screens from About... menu with software and MCU versions to identify head unit correctly.
[Android Head-Units] meir__:
Password for Extra settings: 61808683
[Android Head-Units] slicer2k:
Same question, my HU is in a Bootloop. Is it possible to acess the Recovery menu?
[Android Head-Units] Sheadexx:
Thank you !!

Many Thanks for your Answers !

The 66668888 password, is working, and i can enter the factory settings menu. :) :) :)

I have only one problem left:

Unfortunaly i become from the seller, only one USB connentor cable, so now i can not connect my background rear view camera for this head unit.

Can anybody tell me please, where can i buy function cabels, for this unit ? I don't found this unit on e-bay, but i find nothing.

The seller, who has sold me the unit, told me, he can't where can i buy the other function cabels.

So can tell me anybody please, where can i buy, AUX cabel for the rear camera, Ampliflyer cabel, and the other function cabel buy for this head unit ?

Thanks so much.
[Android Head-Units] bazanovv:
You can go to the nearest radio parts store (or go to Aliexpress, lots available there), find some more or less matching connectors (ones for computer, adruino developer boards and so on may fit), find some AV connectors and solder them together according to the HU pinout, found on it's top cover or provided by the seller. Or you can ask some radio technician to do it for you. If seller did not provide right connectors to you, there are too few chances to find them ready. Different HU do have different pinouts, and inserting something wrong (this is especcially true for the +12 V "Reverse" or "Back" input wire, needed to auto switch HU to rear video input. Alas, if you put +12 V into the video input, 75Ohm resistor burns at once, and if capacitor fail, video mixer chip burns too. If you put 12 V into MCU inputs for CANbus, MCU may die completely and immediately) may damage or burn your HU completely. Be VERY careful, then making and connecting wires, and double check the pinout.
[Android Head-Units] Sheadexx:
Thank's for Your Answer :good::)

We tried making AV connector, but without wiring diagram, i think it is wery risky.

The connector type is different every head unit , So I thought there was a factory connection cable for this type.

:(
[Android Head-Units] bazanovv:
If you bought this device from Aliexpress, you may ask the seller to provide a pinout, or you may search for the similar unit there (that will be quite hard, because there are LOTS of them). Unfortunately, I was unable to find an exact match in the K2001 thread of the 4pda. However, sometimes pins are marked on the board (open the image with right mouse lick - open in new window), so, may be, disassembling the HU will give the answers. This type of connector itself is very common, however, pinout may be different for different HU.

1) Video In connectors should be connected to ground with 75 Ohms resistors and do not have a signal on them, unlike Video OUT. They are easily found with the multimeter on switched off HU. It may have from one to 4-5 video in inputs (video in, 4 cameras for 360 view), depending on the model.

2) To identify a Reverse (Back) In switch wire, there +12 V from reverse light connected, you may switch the HU on and try to apply +5 V from USB or other source, like battery, with the 4.7 kOhm resistor connected serially, to all pins one by one. Then HU switches to the reverse display (it may be blank, or with no signal message), you have find a correct pin. However, it is quite risky - 4.7 kOhm resistor and 5 V instead of 12 should not let something to burn, even if connected incorrectly, but I have not tryed this myself.

UPD: Things may be much easier. Reverse (or Back) switch in wire may be on the main connector, usually purple or brown, and marked with the "Reverse" or "Back" label. If so, and putting there +12 V (at first +5 V with the resistor in serial) do switch the HU into reverse cam video input mode, you need to find only the video in. That will be quite safe and easy, just remember about the capacitor.

3) Then finally found a reverse pin, pull it high to +12 V, and try connect video signal from camera to all prins there you have found 75 Ohm resistance on step 1, with the 1 uF capacitor serially. Again, capacitor does not let the HU or camera to burn each other then connected incorrectly (some pins on the connector may be connected to +12 V, this will damage camera out). So you will be able to find rear camera in and it's switch wire.

4) For audio out all is much more simpler. Turn the HU on, switch on the music. Connect ground pin of any cheap headphones to the HU ground, and try other pin on all pins in sequence and listen. Then use balance to find which one is left, right, forward and back. Try to exclude pins with the +12 V and +5 V on them (use multimeter to find), and don't shortcircuit them to the nearest pins, or you may damage th HU, headphones and your ears, click will be quite loud :)

UPD2: One of the possible pinouts here. It may match with yours, or don't mach.
[Android Head-Units] slicer2k:
Man, thank you so much, now not only i have my HU back, but it has now a brand new Firmware!

EDIT:

Figuring out the sleep mode issue.

There is no sleep mode !!! No sleep mode !!!

http://4pda.ru/forum/index.php?showtopic=806442&view=findpost&p=67072719
[Android Head-Units] slicer2k:
Quick question: Can i enable the sleep mode after i have flashed the 20170825 (Сентябрь 1) MCU+FW?
[Android Head-Units] bazanovv:
Yes, latest firmware + MCU set (25.08.2017) do not have a sleep mode. This made because, unfortunately, this HU (Default, or Standard), unlike other on Allwinner T3, did not have a sleep mode initially. It was added in later firmwares, but still have some unfixed problems - for example, users complain on bluetooth reconnect problems after sleep longer then 30 seconds, and HU power consumption during sleep is quite high - about 0.7 A, that's why "Standard" HU should not and does not let to sleep longer then 2 hours - it will drain the auto battery. Actually, Android module does not go to the sleep, it only switches the screen off and unloads active programs. Also, firmware from 25.08.2017 is from a bit different firmware branch with different launcher and so on.

You may, at your choice, do any one (and only one) of this steps to restore the sleep mode:

Downgrade to Android version Первая июльская, 18.07.2017 and also downgrade MCU to version 15.07.2017 or 24.07.2017. Both MCU do have a sleep mode, and do have a cranking restart fix, however, one of them do not save the bluetooth volume, I think 24.07.2017, but not shure. Sleep mode should return after flashing. If Android says it did not want to downgrade, you always have a choice to flash old December firmware (Декабрьская, 24.12.2016) from bootable microSD card, and then upgrade to desired version. You should now know how to do it :)

Downgrade only MCU, it usually do not check if it upgraded or downgraded, and install patched by Alexey arsenev settings.apk (root required) by replacing the original one and restoring access rights (all required files are now available on the mirror).

Downgrade only MCU and install custom Android image, made by Alexey arsenev (launcher and some software added, settings.apk replaced to the patched version). Installing from this .zip should not delete all installed software, unlike flashing from .img
[Android Head-Units] slicer2k:
Thanks again friend, the google translation wasn't helping!
[Android Head-Units] bazanovv:
New firmware (Первая ноябрьская, 06.11.2017) for Default/Standard type of HU available, again, without sleep mode.

And patched version for use with MCU xx.07.2017 too (settings.apk patched to enable "shutdown delay when ACC OFF", Kingroot, Google TTS, Navi, Time speaker, Via added; Chrome removed by Alexey arsenev).

All other HU's on T3 meanwhile get their new firmwares, too :)
[Android Head-Units] Sheadexx:
Reverse camera

Hiii

Finaly i found AV cable for this Head Unit .:D I tryed everything, but, the reverse Camera function don't work.:confused:

When i Tryed the AUX camera function, and manually running the Video Application, i see the cameras picture.

But, when i connect the video RCA in the Back camera inpput RCA Even though I switch the gearbox to "R" , the headunit does not do anything.:confused::confused:

The unit have not "Back" wire , so i can't direct controlling the backcamera function.

On the head unit i runned, the can bus debugger, and is see, when i switch gear "R" the head unit gets CAN BUS signal, but DO NOTHING :silly::eek::eek::crying:

Anybody have idea? Please HELP me :) :fingers-crossed:

Thank youu:cyclops:
[Android Head-Units] bjmsam:
Has anyone found a way to password protect or otherwise secure this head unit as discussed here?
[Android Head-Units] JustSaab:
Hello guys with an android head unit.

Recently I acquired one myself (11.11.2016) back than it was new with Android 6.0.1.... It has a quad-core 2GB 32GB T3. However last week the launcher keeps stopping after an Waze navigation update?!

So started to Google and came here! So I tried the "December update" with the phoeneixcard on setting "Product" on a 4GB fat32 SD card. But it gave me "error" no idea why.

Alright so I tried MCU update and that worked no problem with the device already on (playing radio), shoved the SD card with the mcu update in the GPS slot and it upgraded.

But now my rotating volumeknop works the other way around?!

So my question: does my unit from 11.11.2016 with android 6.0.1 already have the december update? If not how can I make phoeneix burn the Img to the SD without throwing "error"
[Android Head-Units] DROIDLG:
Hi bazanovv,

I have an Allwinner T3 P2 1gb ram headunit running 4.4.2.

APP VERSION K2101_JSH_ s212102.20170623.11215958.N0020

PLATFORM VERSION K20-2017/05/26[16:56:21]-7.05

BT VERSION GOCBC8_V1.0/2017:4:14:11:43:33

MCU VERSION V1.4-FF01-20170331-AO2-CAN0000-09-00-DVD00000000-00

I have gone through 4pda faq on the official 6.0 roms but to be safe would like to ask directly.

I would like to update to 6.0 and with root permission or at least 6.0.

What would be the most suitable rom to update this with?
[Android Head-Units] JustSaab:
Oké so I managed to get the december update to work. (used Phoeneixcard as administrator) And now I wanted to update to the most recent version of November... However when I put in the SD card with the zipfile in the root folder nothing happens tried the GPS slot and the memory slot both show I put in a SD card and than it dissappears. Do I need to rename the file to simply: os_update.Zip or do I need to go throw every update from December 1 by 1....
[Android Head-Units] bazanovv:
All head units on T3 I have seen do have a "Reverse" or "Back" wire, sometimes connected to car wiring, sometimes to the CANbus adapter. Could you provide your HU picture and connectors pinout?

I heard, that then configuring a VPN conection HU asks for password, and then asks for it at each and every boot. You have to factory reset the HU to remove this request. But I never try this myself.

It may need Visual C++ redistributable to work, it may want another microSD card, etc - lot's of matters. Need more datails on error message.

Volume control directio, as well, as other settings is configured in the engeneering menu - click Kernel version - OS version, Kernel version - OS version, Kernel version - OS version, go to Other - Knob learning - The left-hand knob reverses, photos here under the spoiler.

This one is a K2101 model, K2001 branch. T3, but different hardware and firmware. Look at this topic, firmwares there with the same screen resolution (!!! it is very important !!!) will more or less fit. Don't flash the MCU. Upgrade from 4.4 to 6 Android is quite complicated, but possible, on this HU. Read the FAQ and then ask what unclear.

You have to rename file to the os_update.zip all letters lowercase, you may put it to USB flash drive or microSD card. Remember to format uSD card used to flash december firmware with PhoenixTool, or HU will start flashing from it at each boot!

It's better to enter the engeneering menu and record settings before flashing, settings may be lost/reset during flashing. You may upgrade to desired version like 18.07.2017 immediately. Sometimes you have to upgrade to something like 13.04.2017, and only then to the 18.07.2017 firmware.
[Android Head-Units] JustSaab:
Thanks for the confirmation about the file name! I formated the SD card after I did the December update. So now it's a empty 8gb FAT32 card again :) I'll try to do the OS and MCU updates in stages when I get home from work. (zip file in the root folder and after that the mcu file in the root folder)

I actually don't know how to get into recovery mode on my HU yet... But I found a video of a JOYING (exact same model as mine) and that one pressed and hold the power button for 15sec. I'll try that but I'm not sure... Already made screenshots of all the settings I found (my radio at one point didn't makes ound/reception anymore because of some code 6685? Instead of 7768?)

Keep you posted! Thanks a lot already
[Android Head-Units] bazanovv:
Make shure you have formatted it with PhoenixTool or device like phone/camera/etc, regular format from Windows does not delete (and even see) hidden boot partition.

You may try to enter recovery with the USB keyboard. Press and hold Alt + PrintScreen and hit few times (or, sometimes, hold) "i". Same key combination may (or may not) work during HU boot. It just says Android to stop all processes, so entering recovery is a matter of some luck :) Use right swipe to move in recovery menu.

As an alternative, you may install root and issue reboot to recovery command (app).

By the way, what do you want to do in the recovery? It have quite a small number of functions, and there are no custom recovery available yet. Only wipe cache/data seems to be used more or less frequently.

If you are sure you have a radio module on TEF6686, not TDA7768, you need special MCU firmware for it's support, in addition to correct settings in the engeneering menu. Starting from 25.03.2017 (not shure) one MCU file contain only one radio module support. Latest MCU for TEF6686 is from 26.09.2017 here (archive mcu.rar, extract mcu-20170926-0952-P6686.bin, rename to mcu.bin, put it on the usb flash/uSD card). Unfortunately, this MCU does not have a sleep mode support.
[Android Head-Units] JustSaab:
Sorry probably I wasn't clear. I do have the 7768. But after the December update it for some reason was set to the 6686 so I didn't have sound than. Later I changed it back to 7768 and it worked. Thanks for the tip to format it with Phoenixtool maybe that was the problem why the zipfiles didn't work when I put the SD card in the GPS slot.

I don't know what I want to do in recovery mode... I guess if I mess something up I can recover?
[Android Head-Units] JustSaab:
Oke so i took a gamble and was a bit inpatient to go through like 5 os_updates and MCU updates...

turns out updating/upgrading from the latest version 06.11.2017 works fine (comming from the ''december'' update)

Also the MCU which is now version 1.17.something instead of 1.12.something...

Headunit works good so far and i FINALLY got the RDS information to show! but not on the ''homepage'' next to the time and date there is a little music thingy which now shows the frequency if i tap on it the radio opens and i see the station name.

Im not sure about the rest yet since i didnt test it any further also its missing the SAAB animated boot logo :'(
[Android Head-Units] bazanovv:
If HU catch a bootloop, or if after installing some software it doing something wrong, you may try to clear data (like reset Android to defaults) or just clear cache from recovery menu. You may also try to flash Android from recovery, on Default/Standard type of HU it should work. But for all other messy things, that may happen with Android, like unsuccessfull rooting, breaking something with the root permissions, etc, the best way to recover on the Default/Standard type of HU is to flash Android completely with the .img firmware, like december one, from bootable uSD card. It is just simpler and faster, then trying to get into recovery.

---------- Post added at 09:27 PM ---------- Previous post was at 09:16 PM ----------

You may extract boot logos from os_update.zip or android_config.zip, edit any of them, put SAAB logo inside, save in the same .bmp format. Just remember about image resolution, it should better stay the same, and must not exceed screen resolution - if so, HU may go into bootloop. Switching the reverse camera on while booting may help then.

To set any image as a boot logo, open it in the default Gallery app, ... menu in the upper corner, or, in the newest firmwares, set as a logo in the bottom.

UPD: ooooppps, animated logo? People say this app [root] should work, but I have not tested it.
[Android Head-Units] JustSaab:
Alright now I'm running in a bit of a confusing problem... Bluetooth it always worked fine sort of... Expect for sometimes I got disconnected... However now when I turn the unit on the Bluetooth sign is already on and when I open "phone app" I can't change the name of the headunit and it just keeps on searching. I think it has something to do with the module however I thought (previous mcu update) it was GOC? I actually didn't check.... Should I just cycle through all the options?
[Android Head-Units] bazanovv:
Yes, bes way is to select Bluetooth chip (IVT / GOC) in settings and reboot HU to test. If HU was initially with the 6 Android, it's more likely to be IVT. If with 4.4 - GOC. And, unfortunately, only few Android 6 Firmwares work with GOC BT. This one seems to be working more or less ok.
[Android Head-Units] Reis:
I have the same hardware in a Ford focus and I found an issue, when I switch the key the date and time are lost and the radio stations are lost.

For the date and time is not a hot issue because it recovers itself from GPS very fast, but I need to re-enter the FM radio frequencies every time, which is a pain.

I've already switched the b+ and acc cables with the same result.

Is there a way to store the radio stations? Any other radio APK working? I've tested spirit FM and is not working...

Thank you very much!
[Android Head-Units] Reis:
Nobody have this issue or know another way to keep radio stations?

Thanks!