yashsingh1/xdaforums huggingface dataset:
[Xiaomi Mi Mix 3 Questions & Answers] KOLIOSIS:
I briefly had the NexS,I think you'll like it,but,if you haven't already,I'd take a look around the NEX forum here @ XDA before taking the plunge,especially if this is gonna be a long-term daily driver.

The software is definitely iOS inspired,but,manageable,a bit of tweaking is in order,especially if you want to use a 3rd party launcher.

Ditto for the Oppo Find X,I had that one for an even briefer amount of time before selling it (5 days),worst mfg UI experience EVER by a country mile.

The hardware on both are awesome,the Nex,while not a flashy,would be the one of the two I'd recommend.
[Xiaomi Mi Mix 3 Questions & Answers] Twotems:
Thanks for the advice. I've been on the Nex forums for a while and bought based on the comments there. The FindX slide to unlock made it a no no from the beginning.

Sounds like you had the Chinese version which is a nightmare outside China. I ordered the global version (I hope!) and it's fine they say. I always change my launcher to FastKey or ZenUi especially on my Xiaomi's so the ios look won't be overwhelming. It's arriving next week so I'll know everything for sure then.
[Xiaomi Mi Mix 3 Questions & Answers] KOLIOSIS:
Yep, had the original (Chinese) versions of both.

I went in to the experience fully aware that things were different from the way most of us use our phones outside of China & baked-in Google services.

Still came out of it very surprised at how restrictive the user experience was.

I've heard the global ROMs offer a better experience.

Would be nice to have OnePlus' OOS on either,the best of both worlds.....
[Android Head-Units] schwrz:
After a lot of searching here and elsewhere I was not able to find a unit that matches these parameters. The unit was branded as Premier AN-740 which is obviously just a sticker label. Any help with identifying this unit will be greatly appreciated.

About Device LINK http://ibb.co/nMEroA

About vehicular platform 1/2 LINK: http://ibb.co/nBWU8A

About vehicular platform 2/2 LINK http://ibb.co/hyiFgV

Update: The stock ROM for this unit accepts 8888+OK as "secret code" to get to the opening logo customization screen. Maybe this provides a clue?
[Android Head-Units] schwrz:
Update #2: Droid HW report

DEVICE

Model: evb3561sv_w_65_m0 (full_evb3561sv_w_65_m0)

Manufacturer: TS356XXPH-

Baseband Version: MOLY.LR9.W1444.MD.LWTG.MP.V94.P6, 2017/05/15 10:24

RIL Version: mtk gemini ril 1.0

Build Number: full_evb3561sv_w_65_m0-userdebug 6.0 MRA58K 1510921099 test-keys

Build Fingerprint: alps/full_evb3561sv_w_65_m0/evb3561sv_w_65_m0:6.0/MRA58K/1510921099:userdebug/test-keys

Bootloader: unknown

Java VM: ART 2.1.0

OS Version: Marshmallow (6.0)

SDK: 23

DISPLAY

Resolution: 1024x600 pixels

Software Density: 240 dpi (hdpi)

Refresh Rate: 57.44 Hz

PROCESSOR

CPU Architecture: AArch64 Processor rev 4 (aarch64)

Board: unknown

Chipset: MT3561S

Cores: 4

Clock Speed: 221 MHz - 1248 MHz

Instruction Sets: arm64-v8a

CPU Features: fp asimd evtstrm aes pmull sha1 sha2 crc32

CPU Governor: Not Available

Kernel Version: 3.18.19

Kernel Architecture: aarch64

GRAPHICS

Renderer: Mali-T720

Vendor: ARM

OpenGL Version: OpenGL ES 3.0

RAM

Total: 1897 MB

Java Heap: 128 MB

STORAGE

Internal: 11 GB

External: 7.2 GB

PRIMARY CAMERA

Resolution: 0.4 MP

Flash: No

Video Resolution: WVGA, 800x480

Supported Resolutions:

Image:

800x480

Video:

800x480 (WVGA)

SECONDARY CAMERA

Resolution: 0.4 MP

Video Resolution: WVGA, 800x480

Supported Resolutions:

Image:

800x480

Video:

800x480 (WVGA)

FEATURES

Bluetooth: Yes

Bluetooth LE: Yes

GPS: Yes

NFC: No

USB Accessory: Yes

WiFi: Yes

WiFi Direct: Yes

BATTERY

Technology: Li-ion

Health: Good

SENSORS

Not Available

Created by Droid Info
[Android Head-Units] schwrz:
Update #3: ROOT!

I was able to root my device using the procedure outlined here:

https://xdaforums.com/android-auto/android-head-units/ownice-c500-root-t3558760

Using the longer password and with some minor command line alterations (see screenshot here https://ibb.co/njSw5q). Hope this helps someone.

My next goal is to get to the factory settings. If anyone gets the code for that please post it here.
[Android Head-Units] MrDeepPurple:
head unit info

Hello, it seems that I have the same head unit. Mine is unbranded and it's shaped to fit a 2008 suzuki swift, however all the codes seems the same.

What I got until now is that 8888 is the boot logo code selection and I can access to the engineering mode menu by dialing *#*#3646633#*#*

I'm trying to perform a factory reset because I accidentally delete the "su" executable and I cannot access it anymore even with the password, howevere there is a factory reset password that I can't find on the net. The next step will be trying to access the "RST" button and check what it does.
[Android Head-Units] schwrz:
Hi Mr. Purple,

Thanks for your code

I can confirm that it works for me as well. I was not however able to locate the FM Radio settings I was looking for (let me know if you find those).

Good luck with the factory reset, and let us know how it turned out.
[Android Head-Units] MrDeepPurple:
Updates

I have some news:

The actual model seems to be the witson w2-k7xxx (in which xxx is the code of the shape of the front panel, mine is w2-K7658).

I managed to access the system menu with the code 3711 and here there are the FM settings!

Here follows what I discovered by trying and trying again and searching on the net:

CODES (to be inserted in Settings > software version > small gear icon near HMI):

3711 -> factory settings

8888 -> boot logo settings

6666 -> a chinese text that reports "no update files where found" appears (probably the update code)

7777 -> a chinese text that reports "no update files where found" appears (probably the update code)

0 -> MCU update page

How to access the engineering mode:

dial *#*#3646633#*#*

How to access the firmware update page:

Click the RST button

touch the screen (and move your finger) until a writing appear on the top left

if a binary file is present in the root of the SD card, then the update begins

How to perform a factory reset: (/system partition is left unchanged, only user data is wiped)

Click the RST button

touch the screen with five fingers (and move them) until a writing appears on the top left

The factory reset procedure will begin. It lasts for 10 minutes

I mailed witson for a firmware update (in order to override the /system partition and restore the su executable) but they ask me for a serial number that is written on the unit. I will disassemble it in a couple of days and if I manage to get this update, I will post it there. However it seems that each model has its own custom firmware that supports only one button layout. If I flash a firmware of the same family (w2-k7xxx) but from a different model, the buttons may not work.

Maybe you can find your own model on witson website
[Android Head-Units] schwrz:
Wow man, you've really been busy! I'm definitely going to try out those codes and knowing who the manufacturer is will help as well. The user interface here definitely looks familiar, though I'm a bit confused as to how you were able to discover the XXX code in the W2-K7XXX part number of your unit. In any case thanks again for all the info and keep us updated, especially if you manage the much needed firmware update...
[Android Head-Units] MrDeepPurple:
Well, my HU has the panel that fits only in the 2008 suzuki swift, so I used the search engine on their site to look for "Suzuki Swift" and there I got the part number!

However if you have a standard panel maybe you can go in product page, then on the left column select "+ For Universal All-in-one" and see if one of the model is the one you own. In that page I see only 4 Android 6.0 headunit: W2-K7900G, W2-K7927G, W2-K7902 and W2-K7924 (I can't send link because I'm new on XDA, but you can easily find them)

From the photos you posted, it seems that your HU is the W2-K7927G
[Android Head-Units] schwrz:
Yes, I think so too ( Link for anyone interested). It would be nice to be able to confirm that this is indeed the exact model before we attempt a firmware update as flashing the wrong firmware is almost guaranteed to brick the unit (i'll try to search for th exact P/N in the "hidden" menus). Besides, now that I have all these secret menus to play with, maybe I can fix the problems I experience without a firmware update. The biggest two issues are speaker noise while idling (even when radio and music player are off) and waaay too jerky FM reception (unit is constantly trying to find a better frequency for the current station - I was told that I need to lower the FM sensitivity in the technician menu to fix that). If I can fix these two issues, I can definitely live without a F/W update. Did you experience any of these issues or is it just my particular model / unit?
[Android Head-Units] MrDeepPurple:
yes, the idle background noise is too loud too on mine. The reception seems fine, just a little worse than the suzuki stock radio definitely usable. However if you find a solution for both, I think I will try it too! At the moment I'm stuck to solve the "su" problem!
[Android Head-Units] schwrz:
sorry to hear that.

i assumed the factory reset took care of the SU problem.
[Android Head-Units] MrDeepPurple:
Other updates

Unfortunately the factory reset only reset the user partition, but the /system partition is left unchanged.

However after two weeks of mails, I finally got a firmware update binary from Witson.

I don't know if it's compatible to your radio, however i mailed to bob@witson.com, they asked me for a product code placed on top of my Head unit and then sent me the update after I provided the code.

Here a picture of the location of the product code on my unit (it's the top side of the box):

[IMG="Code location"]https://i.ibb.co/cDqkswf/IMG-20181124-090324.jpg[/IMG]

Maybe you can ask for a firmware too with your serial and then we can check if it's the same file.

Now I'm trying to fixing a network bug that made my cellular network connect to a roaming operator (TIM) instead of my operator (three) due to a wrong priority assignment.
[Android Head-Units] schwrz:
As always nothing but helpful information from MrDeepPurple (seen them in concert not too long ago hehe). I feel kind of ashamed for not contributing anything.

I plan to take apart the center console in my car during this weekend so I'll be sure to check for that code - in addition to a few other things I've been saving for this event such as debugging that horrible background noise we talked about. I plan to disconnect the HU from all peripherals one by one until I find the culprit. If the HU itself is generating that noise I'll need to rethink my strategy. As for the radio reception, I did find the radio sensitivity setting thanks to your help and lowering it did help a little, but it turns out I've been kind'a stupid not noticing how short the antenna the previous owner put on the car was. With that size it was physically impossible to get good reception, so I just ordered an OEM antenna from the car manufacturer and hope to be done with this problem. The moral of this, I think, is that even though this HU is pretty sh**ty, we shouldn't be so quick to blame everything on it as there are other components in the system. One thing to note to anyone fiddling with the system settings from the codes MrDeepPurple provided, be aware that saving the settings will RESET YOUR HOME SCREEN TO STOCK so if you want to try out different settings do it all in one go, otherwise you'll end up having to replace all your widgets and things to the way you like them about a zillion times.

It seems that the problems never end with this HU - is this bug due to the firmware update?

At this pace by the time we get them to perform adequately they will be outdated.

Anyways good luck and keep updating.
[Android Head-Units] MrDeepPurple:
yes, this happens on a random OTA update I received a month ago. I didn't even know that this HU can have OTAs. However I'm not able to select network type (2G, 3G, 4G) anymore because the menu is greyed and instead it appeared a menù with PLMN editing. I didn't even know what a PLMN was before that.

However this menù is totally useless, the selection and the editing of PLMNs is resetted when you exit this menu. The PLMN which has the highest priority is TIM, then comes three UK (why uk? iI'm in italy!!). I read that there is a sqlite db accessible only with root permission that contains those informations so I need root to access it.

You contributed to find the correct way to root this HU that is the most useful information to me by now!! Thank you!
[Android Head-Units] MrDeepPurple:
well, it seems that the root procedure doesn't work on mine.

After all the steps on Ownice C500 post (even with the short password on forfan executable and the long one with the su executable) it seems that the root doesn't work. When I try to run the su command on a terminal emulator it returns 1. It's a generic error code, so there should be something missing. However I'm not scared to test it now that I have the firmware update files.

Did you use the su executable in the Ownice C500 post?

Are the other file useless (libsupol.so, sukernel and supolicy) ?
[Android Head-Units] schwrz:
so with the firmware update they also patched the system against rooting?

makes me think twice before updating...

Having performed the root two months ago I'm sorry to say I don't really remember much. However two things are clear from the screenshot (third post in this thread):

1. I used the longer password.

2. Only the actual su file is copied and given execution permissions.

Not sure what's the source of that 'su' executable but it's probably from the link given as I can't recall doing otherwise.
[Android Head-Units] MrDeepPurple:
Today I received a new update binary, I will try to upload it soon and check if it solves my problem
[Android Head-Units] k5235:
I just buy and new android head Units is name DynaVin 2GB 16GB with 4gLTE .

The "Droid info" i get only 2 was difference from yours as below shown .

1)build number difference from 1510921099 mine 1511340754

2)build fingerprint difference 1510921099754 mine 1511340754

I Found 2 Bug

1) Minor Noisy Sound when in idle mode .

2) Waze Hang when using 4G Lte . Reseat 4G Card then be ok again

Anyone can provide some ideal ?
[Android Head-Units] MrDeepPurple:
I think it's the same head unit, probably the differences are only on firmware release version

This is a common bug, schwrz was trying to solve that but it seems to affect all the radios with the MTK3561

I've never tried waze on it, only google maps and sygic and they both works fine! Well, sygic is a bit slow and laggy but still usable.
[Android Head-Units] schwrz:
The main reason I've put Android in the car is be able too use Waze properly (i.e. no weird phone holding gadgets) so yes, I can confirm that Waze works fine on this HU. Otherwise I'd have replaced it long time ago.

As for the idle noise, I currently tend to think it's a hardware rather than software issue. I'm going to take apart the center console and see what's what as soon as I receive some parts I'm waiting for (for which I also need to take apart the center console - no sense in doing it twice). Will report my findings.
[Android Head-Units] k5235:
THANK Tivoli & schwrz for great advise and sharing .

I think it's the same head unit too, probably the differences are only on firmware release version , we call OEM ? haha

I try 2 Difference Brand HU , i think most of it are common bug with idle noise sound .

1) Asianmap 2GB 32GB (New replacement unit but yet to try)

2) DynaViN 2GB 16GB with 4G-LTE (Temporary Workaround is "enable DENOISE")

**the default idle noise are slightly soften then my first units

Yet to try other GPS Application but personal quite prefer WAZE .

I just receive DynaVin System software there are

3561f.bin & 3561f.upd . Total Size 1,174,489 KB

but i failed to update it may my pendrive or the filesystem and will try other pendrive then update here later

do you two got Line or whatapps . i can share some live video on my finding .
[Android Head-Units] schwrz:
...

Here's mine. Not sure what to make of it just yet, I'll have to mail them and see...
[Android Head-Units] schwrz:
the extremes I'm going to to isolate the noises....

UPDATE:

well, it seems that while testing I've managed to brick the unit by touching the reset button at the wrong moment (i think it was during boot). It's a shame because I think I discovered the wiring problem that was making all the noise - of course now I can't be sure as the unit will not boot beyond a white screen. as far as I can tell the firmware update system is still working so I hope witson send their firmware soon otherwise my only other option would be to try to return the HU to the shop it was bought from, which even if it works is going to take waay too much time. considering the poor job done on this HU by "professionals" so far, I'd much rather just re-flash the firmware myself. I will update regarding the outcome of this for the benefit of other owners of this unit.
[Android Head-Units] MrDeepPurple:
if Witson doesn't answer you soon, I can share the last firmware they sent me. let me know!

However I have some updates too:

1. each firmware has a version number. The first one I received is v42, the last one is v50

2. with V42 firmware I can access LTE only by manual registration on the network in the Android option page. During travel the connection is lost (probably it happens when the device is connected to another cell)

3. with V50 firmware I can access LTE only by manual ecc. ecc. The difference is that the registration is kept for the entire day (a daily timeout for network registration maybe?). It' s better then v42 but still not enough. Consider that before the OTA, I could access the 4G network without problems

It seems that my problem is related to the network registration. I read somewhere that it may happen with three sim card on mediatek devices due to the use of recycled IMEI. I will try to change this IMEI with the one of an old phone I didn't use anymore to check if it solves the problem
[Android Head-Units] schwrz:
Unfortunately, I cannot offer any advice on the cellular front. However regarding the idle noise I would definitely check the wiring and here's why:

While examining the wiring harness I discovered that the "professional" has connected the ANT signal from the HU to the AMP signal of the car (my car has an amplifier separate from the HU as standard and that is the signal to control it). Of course the real AMP signal is left dangling in the air. The reason for the mistake is obvious but I'm kind'a amazed it even worked at all. Anyway, understandably I'm reluctant to let this professional "fix" my stereo again. Bottom line, if you hear excessive whooshing sounds from the speakers even when the HU is not playing anything, check your wiring!
[Android Head-Units] schwrz:
The local reseller is extremly slow in providing support and Witson has yet to reply.

It seems I have no choice but to take you up on your offer. If you publish the firmware that'd be great!
[Android Head-Units] MrDeepPurple:
try this one:

https://mega.nz/#!VrYWXYaa!6RuyOy0-lQKfNOVfU5wE48mAP2W-_ku4MG-Q6ZOvlfQ

is the last version, I hope it will solve your brick
[Android Head-Units] schwrz:
Thanks for the quick reply MrPurple.

I was actually able to get this file earlier from this Russian site (I did a file compare, it's the same file) but the update was either unsuccessful or did not solve the problem. Just to make sure I did it right, I'm supposed to dump the contents of the ZIP file into the root of the SD card and then touch the RESET button while constantly moving the finger over the screen, correct?

Anyway, there's quite a few firmware versions on that site, maybe one of them could solve your issue with the cellular network?

It's in Russian of course but google translate should be enough to understand what's going on...
[Android Head-Units] MrDeepPurple:
yes, right. On some devices it happear a writing on the top left which reports if the update file has been read correctly. Maybe you can try different pendrives and different usb port (on mine only port 1 works and i tried two different pendrives and only the second one works)

However after this update, the writing does not appear anymore and it's substituted by a white-grey gradient screen.

thank you, I will check it soon!
[Android Head-Units] Crapy:
I have the same device! Your info here is life saving!

Any of u had any problem with calls being freakishly loud at the lowest level?

edit: mine is labeled as AN-1040 although the same codes work and it seems almost identical
[Android Head-Units] schwrz:
Well, it turns out it wasn't a classic brick. the (touch) screen was KIA (short-circuit due to the poor wiring I mentioned previously?).

Surprisingly the guy at the store I bought the HU from solved it with the distributor within a week.

Witson BTW did not bother to answer me emails, not that it matters at this point.

I've re-soldered the HU to the Mazda connector and verified that everything works with a desk PSU, so I'm gonna go ahead and re-install it within the next couple of days.

I really hope I finally got rid of those noises...

How is your LTE issue coming along?

UDPATE: it seems that the MCU version decreased while it was at the distributor - or was it the re-flash I attempted without screen? not sure

In any case the version was TS907.180202 and is now TS907.170330. Did any of your firmware updates touch your MCU?
[Android Head-Units] schwrz:
Hi Crapy, welcome to the crappy HU club :)

Good to know our info is being put to good use.

Nope. But this unit has two or three different menus where you can change the BT/call volume, not to mention the secret technician menus.

Make sure you cover all of those, check this thread for thr codes needed.

does it look like this?
[Android Head-Units] MrDeepPurple:
I cannot manage to solve it. I don't know why it worked on the firmware version I found preinstalled in the HU at this point! However my biggest concern was the interruption of the LTE service while using google maps and surprisingly I found that if an application is using the network, then it works. If the network is inactive during a cell switch, it stops working. This allow me to use google maps at least. It's annoying but usable.

Tomorrow I will check my MCU version
[Android Head-Units] Crapy:
Yup and what do I change in the technician menu? I changed everything I could find nothing works

I changed in the engineer menu the network to 4g/3g only and it seem to have fixed it for me, I get reception fast as lightning now too
[Android Head-Units] MrDeepPurple:
Unfortunately none of the options in the engineering menu solved my issue

I checked the MCU and my version is decreased too. Probably the two firmware provided by witson are older versions and there still is an update somewhere around.
[Android Head-Units] schwrz:
I'm sorry you didn't find anything - at the very least I think it was worth a shot. I'd love to have a look but I can't help as my unit was sent for repairs yet again (of course).

This time it seemed to work flawlessly until I tried the FM radio - which for some reason can be heard only on the left speakers. I thought I screwed up the wiring but tried an MP3 just to make sure and... I heard it on all speakers! Obviously the wiring was fine and the unit was promptly sent back and will return who knows when.

Will this ever end? Ugh, sorry for ranting.
[Android Head-Units] schwrz:
UPDATE: Finally the unit is back and in working condition. Everything seems to be working great.

Next I'm going to attach a camera and try out the road DVR feature.
[Android Head-Units] Crapy:
It seems im the only one who cant stand the bt calls ah? The beep while waiting for someone to pick up is killing my ears
[Android Head-Units] schwrz:
Does this also happen during SIM calls?
[Android Head-Units] Crapy:
Yes