yashsingh1/xdaforums huggingface dataset:
[Android Head-Units] ramathorn1982:
Ok, I was able to get it with your instructions but both the top/bottom menu/Air controls remain as before.

Am I mistaken in thinking that after I deleted that line of code the top navigation bar should disappear and no longer automatically load at startup?

My goal is to have the Chinese theme12 on bottom at all times but to have the top UI menu gone.
[Android Head-Units] Hammerhand.17:
When your unit boots it will be the same; you have to run the app to hide bars, but now it will hide only upper bar. I have added the program to boot (with Tasker) and it runs when unit finishes boot. It's slow, but works.
[Android Head-Units] hapaman:
Did anybody have success using the volume or display brightness functions in FCC Car Launcher or Carwebguru with this units? Both launchers offer px3 rockchip support, but it seems not for our units. I'm asking because when you hide both bars, also the the buttons for volume and display settings are gone.
[Android Head-Units] ramathorn1982:
Ok, I missed part of the conversation. Which App must I run?

---------- Post added at 04:34 PM ---------- Previous post was at 04:31 PM ----------

I haven't but I'm going to try the car launcher pro dimming controls next. The bottom bar I want to stay for the very reason you describe but I think car launcher pro has a separate volume bar you can put on screen as well, I'm just not sure if your steering wheel controls can use it ...
[Android Head-Units] marcus82:
Omg.

So isn't enough modify the file...

But I saw in Russian topic a definitive change

Inviato dal mio ONEPLUS A6003 utilizzando Tapatalk
[Android Head-Units] ramathorn1982:
Disregard. I went further back in your conversation and figured it out. Thank you both for having the conversation!
[Android Head-Units] ramathorn1982:
...custom NAV bar from Car Launcher Pro.
[Android Head-Units] marcus82:
wonderful!!!
[Android Head-Units] ramathorn1982:
To what are you referring by "zxy expansion to install px5 on our px3" ?
[Android Head-Units] marcus82:
https://www.zipy.it/p/ali/witson-px...-upgrade-to-android-6-0-directly/32840635444/

Inviato dal mio ONEPLUS A6003 utilizzando Tapatalk
[Android Head-Units] ikuznets222:
apktool doesn't generate anything like that under Unix-type OS (not sure about windows, don't use it). When you unpack, it creates a folder called EventCenter. When it packs the file back it creates EventCenter/dist/EventCenter.apk in the same folder. That's the file you should take to your unit. At least compare sizes..

---------- Post added at 08:13 PM ---------- Previous post was at 08:12 PM ----------

That's totally incompatible - why do you keep asking?
[Android Head-Units] marcus82:
I didn't see any response, my friend with the same HU sent me this idea...sorry
[Android Head-Units] ikuznets222:
new FW 20181115A for 1024x768 units with ROOT

https://yadi.sk/d/EPeH8LBYbvPtJg
[Android Head-Units] marcus82:
With root? So I have to uninstall kingroot?

Inviato dal mio ONEPLUS A6003 utilizzando Tapatalk
[Android Head-Units] ikuznets222:
Yes, pre-rooted
[Android Head-Units] marcus82:
OK I will uninstall it

Inviato dal mio ONEPLUS A6003 utilizzando Tapatalk

---------- Post added at 07:08 PM ---------- Previous post was at 06:57 PM ----------

Is there any changelog?

Inviato dal mio ONEPLUS A6003 utilizzando Tapatalk
[Android Head-Units] ikuznets222:
You seem to have been hanging around fo some time. Have you ever seen any changelog for these FWs? Or maybe some web site where we could download them officially? This one comes from phoenix, that's all I know. I just pre-rooted it
[Android Head-Units] marcus82:
Ehehe sorry I was hoping...

Inviato dal mio ONEPLUS A6003 utilizzando Tapatalk
[Android Head-Units] ramathorn1982:
Thanks for the clarification. Hammerhand.17 got me sorted out. I needed to go further back in your conversation to get all the steps needed to implement the configuration you have layed out (in great detail).

I really appreciate you being so active on this thread. Your modifications make me like this radio more each day!
[Android Head-Units] hapaman:
Is it possible to hide the bottom bar and the top bar, but keep the very top bar with the power and brightness button?
[Android Head-Units] ikuznets222:
Possible, but very difficult. Much more than anything I described here before
[Android Head-Units] hapaman:
If even you say it's very difficult, than no chance for me to achieve that :)
[Android Head-Units] ramathorn1982:
Works great, thank you! Would you mind if I shared your rooted firmware with others?

---------- Post added at 01:18 AM ---------- Previous post was at 01:11 AM ----------

Just to follow back up, the Car Launcher Pro on screen volume option does nothing for me...
[Android Head-Units] ikuznets222:
Be my guest
[Android Head-Units] Hammerhand.17:
Is this an hybrid build also? I'm asking because some people said that last hybrid build was slower to boot parking camera, and I didn't update yet.
[Android Head-Units] ikuznets222:
No, not hybrid. Real firmware, android 4.4 1024x768 from phoenix android:

https://www.facebook.com/PhoenixAnd...r5Gn0uH1e4hXk9o-zHhhjOcwZf9G7cxxszQ&__tn__=-R
[Android Head-Units] Hammerhand.17:
Is this also for 10.1" units? In this Facebook link states that's for 12".
[Android Head-Units] ikuznets222:
Screen size doesn't matter. Resolution does. It's clearly shown in the video that it's 20181115A-Ver1.0.1.carcool_860_EN_1024
[Android Head-Units] ramathorn1982:
I've noticed in this firmware the volume levels are much lower. I'm at my comfortable listening level at 40 (the maximum).
[Android Head-Units] ramathorn1982:
One more question, this update from Phoenix was accompanied by a CANBUS update as well specific to my vehicle (RAM 1500). Are there any specific things to look for from a CANBUS update for these radios to ensure compatibility with my CANBUS module?
[Android Head-Units] ikuznets222:
Personally, I wouldn't be doing any sort of MCU update on this unit unless I had an original binary. Even if I had one, there's a high chance that MCU update won't let me rollback. Add to this that if something goes wrong during MCU update you're getting an unrecoverable brick. Choice is yours though. Nothing is known about the code, features, changelog of this MCU. Even the chip itself has not been identified so far (even though we know where it is). Last consideration - as far as we know (@4pda), mcu FWs are not car-specific but more factory-specific. So we had examples of people doing seemingly correct mcu updates for their cars only to find out that radio and other big board stuff failing afterwards. It happened because different chinese factories make units for the same car, based on the same android board from ZXW, but with different incompatible big boards and hence mcu's.

We also had examples of people trying to fix their mcus by uploading other car's mcu binaries but from correct factory - and everything's working fine.
[Android Head-Units] ramathorn1982:
Got it. I appreciate your candor. I somewhat feel obligated when trying some of these fixes because I received this radio for $75. So a brick for me is not nearly as large a setback as a brick for someone who paid full price.

That coupled with my insatiable appetite to tinker with things I have limited understanding of means I'll probably do this anyway and when I screw something up I'll say "well ikuznets222 tried to warn me"...

Wish me luck!
[Android Head-Units] ikuznets222:
Good luck, and you can always unbrick by replacing android board or by re-soldering a working mcu chip from any other unit's android board. What's more difficult is to find the original mcu binary as very few are publicly available.
[Android Head-Units] ramathorn1982:
That's very good to know. It think I saw on 4PDA that that was how folks were upgrading the hardware too so it would just be more reason to tinker for me!

That being said, I performed the CANBUS update and all is well. It fixed the auto headlight issue and strangely it also seems to have changed the volume issue I reported on the latest firmware too.

I'm speculating this is specific to RAM trucks with this radio as I believe that audio signal is actually passed over the CANBUS too. So for my vehicle specific setup, I needed the November firmware AND the CANBUS update for everything to work properly. I could be wrong though, I'll need to here from other RAM owners to know for sure. I also noticed they added other options for RAMs too in the advanced settings (other/2018/2019)...
[Android Head-Units] marcus82:
I put the zip file renamed to update.zip but I have this issue

Inviato dal mio ONEPLUS A6003 utilizzando Tapatalk
[Android Head-Units] ikuznets222:
I don't see your pic for some reason but I believe you're trying to update FW. It's not a ZIP file but rather unzipped update.img
[Android Head-Units] marcus82:
I don't know why attach doesn't work. [emoji53]

I was rushing.. I'm going to extract it but it's strange cause it recognize the update,zip

Inviato dal mio ONEPLUS A6003 utilizzando Tapatalk
[Android Head-Units] ramathorn1982:
I may have asked this question before but I forget. Are these radios capable of getting Artist and Station information on FM, or maybe even HD radio? If so, is there a setting to get this info to display on the Stock Radio App?
[Android Head-Units] marcus82:
I think no. Use dab as me

Inviato dal mio ONEPLUS A6003 utilizzando Tapatalk
[Android Head-Units] ramathorn1982:
Unfortunately I don't believe that's an option in the US.
[Android Head-Units] wishie197:
*phew*

54 pages of reading. Time for a comment.

So, the unit I have ordered, for a 2003 Mazda 6 (GG) is listed on AliExpress as both 7.1 and 6.0, and before purchasing, I asked the seller if the unit supported 'fast boot' to which they have said "yes, this unit support fast boot". -- time will tell.

My experience thus far with Android HU's is:

I have a 7" Double DIN unit in my Mitsubishi Grandis that works wonderfully (now that I wired it in properly -- the yellow 'BATT' and red 'ACC' wires were wrong in the supplied harness).

I have a 10.1" 'dash mounted' unit in my Mazda 6, but it doesn't support fast boot (very frustrating) doesnt play well with the factory BOSE amp/sub, and the screen melts off if you park the car in the sun (Ive solved this by supergluing the screen on, with little tiny bits of glue).

I'm really hoping that the unit I have on the way (due in a week or so) actually supports 'fast boot' (which means its a proper Android 7.1 unit?).

Am I understanding correctly that (if my unit is indeed 4.4.4 based) I can use one of the pre-rooted update.img firmwares (example -- 201811xx mentioned on Page 51) but make sure to copy my customer.xml file over the top, once flashed?

Here is a link to the exact unit I have purchased: https://www.aliexpress.com/item/Tes...817.html?spm=a2g0s.9042311.0.0.38074c4dhfI9KS
[Android Head-Units] ramathorn1982:
Unfortunately, if it's the fast boot version these firmwares are not for that radio.

As far as I know, root is still not available on the fast boot radios.
[Android Head-Units] marcus82:
Yeah! With new firmware I restored aux input!

Inviato dal mio ONEPLUS A6003 utilizzando Tapatalk
[Android Head-Units] wishie197:
At this point, I think I'd rather prefer a proper 7.1 unit with 'fast boot' over the ability to modify stuff... purely because waiting for my current unit to boot each time is torture..

What annoys me the most is, I'm pretty sure 'fast boot' is just a feature of the MCU software. On my current Mazda 6 unit (10.1" dash mounted - non Tesla-style) when you turn the car off, you can see (if in the correct light) that the first thing that gets turned off is the LCD backlight.. then, about 5-10 seconds later, Android shuts down... if only it could 'sleep' like a tablet does instead of issuing the command to 'shut down' I'd be happy. Clearly the unit has constant power via the BATT line.

Anyway, back to the units that this thread is about.. Do you guys value 'fast boot' more? Or customisation? Do you have any issues with such expensive devices running Android 4.4.4 (4.5 years old at this point)? Won't app support suffer because of this? Didn't Android 4.4.4 only have SSLv3 support, not TLS? These things could cause issues in the very near future (if they aren't already).

My seller, when asked directly, said the unit I have ordered supported 'fast boot' and was 'Android 6.0'.. so if those things are not true, I will be asking for a refund I think..

It's annoying that the best supported Android unit I have, is the one in my Grandis, which was also the cheapest my a large margin (~$200AUD vs ~$700AUD for the Tesla-style)
[Android Head-Units] wishie197:
Only time will tell, I guess.
[Android Head-Units] ramathorn1982:
[MENTION=8668875]ikuznets222[/MENTION]

Talk to me about this upgrade from Phoenix. Do you think we will keep root?

https://www.phoenixautomotiveinc.co...F3cu5t9FzLfYj9WxMhfJJMIb71J06BKHJtPREx3iU5sso

Would be awesome if so. Great price too! Apparently it takes the first generation 4.4 version to a newer fastboot version via hardware upgrade.
[Android Head-Units] ikuznets222:
If you mean RDS then yes, but you need 1) FM module with hardware RDS support. I've seen both RDS and non-RDS modules on these Teslas. 2) chinese radio app with grey background. Only this grey theme supports RDS display. Inside the stock radio app there are more themes (like black for 71th theme, one for 12" screen and a couple of others). 3) enabled RDS setting in chinese grey settings (it's where radio region is selected)

---------- Post added at 07:04 AM ---------- Previous post was at 06:45 AM ----------

Correct. Fast boot units are only based on android 7.1. The easiest way to identify 4.4/7.1 is by looking at chinese system info (grey screen). KTU84Q means 4.4.4, NMF26X - 7.1.

All FWs I posted here and on 4pda are for 4.4.4 units only. It's not possible to install them on 7.1 units.

Actually, pre-root is possible using exactly the same method as for 4.4. But I'm not sure I'm going to be working on those.
[Android Head-Units] ramathorn1982:
I'm currently using the Gray Radio.APK I pulled from 4PDA. I haven't seen how to select themes for the stock radio App. Where do I select that at? See the attached picture for my current (non stock Radio.apk)...also, did you see my post about the fastboot upgrade to 7.1 for our 4.4 radios?
[Android Head-Units] ikuznets222:
You only select themes for radio by changing main theme. On your screenshot RDS is either not enabled or not supported. This is custom radio, so ask those who created it whether resources needed for RDS display were left intact.

Regarding upgrade 4.4 to fastboot - haven't seen your post. Such upgrade itself is not possible.
[Android Head-Units] hapaman:
Link does not work for me...
[Android Head-Units] wishie197:
The link to Phoenix Automotive shows a $99.99 USD hardware board that can apparently be swapped into some of the 4.4.4 based units to 'upgrade' them to have fast boot... the way I see it, its just replacing the older version board, with a newer one. I assume that means Android 7.1, and then losing root access.
[Android Head-Units] ikuznets222:
Totally correct, but root access on 7.1 FW IS possible. Root access one used to have on older board will be lost with the board itself, of course.
[Android Head-Units] ramathorn1982:
Phoenix Android is selling it as an upgrade.

I think if you have an add blocker the link will fail. Try looking up Phoenix Android's Facebook page. It's one of their latest posts.

https://m.facebook.com/PhoenixAndroidRadios/

I think you are right, it essentially swaps the chipset entirely. It's $99.99 if you do it yourself and if you have them do it they'll give you $70 back for your old board as a core charge refund. You pay shipping both ways however.

I think I'll buy one regardless as a backup option for as much tinkering as I do.
[Android Head-Units] marcus82:
Wow is there an upgrade? Like the px5 posted by me

Inviato dal mio ONEPLUS A6003 utilizzando Tapatalk
[Android Head-Units] Hammerhand.17:
It's a shame that is not for every unit, just few brands. I would buy one if it worked fine in other brands.
[Android Head-Units] ramathorn1982:
It's an entire core board swap. From the person who let me know about it and questioned Phoenix Android the upgrade will require you to solder on the wifi, gps, and bluetooth connectors to the new board.
[Android Head-Units] marcus82:
I'd like to upgrade my HU for focus first of all for the split of display

Inviato dal mio ONEPLUS A6003 utilizzando Tapatalk
[Android Head-Units] ikuznets222:
Not "like" that one. Has the same PX3 cpu but with true android 7.1, fast boot (from sleep only) and sleep mode up to 48H. Not for all cars. MCU version 860C (vs 860B on older ones). Split display is not very likely to be implemented.
[Android Head-Units] ramathorn1982:
I bet it does...mine is originally from ESPONY Cargo and I'm thinking this will work still. I think I'll be the guinea pig. A member on the Ram Forum is going to purchase and do a how to (although his is from Phoenix Android I believe). I plan to follow in his footsteps.
[Android Head-Units] ikuznets222:
Remember MCU chip is located on android board, and MCU is factory-dependent. New MCU is coming with android board. So the only way it would work is when your old unit (big board) and new board were manufactured by the same factory. Otherwise new android board would either fail to recognize FM and BT modules or they'd work incorrectly.
[Android Head-Units] ramathorn1982:
So technically I may be able to confirm compatibility by comparing my System Version screen to a known good Phoenix Android system version screen with my own? Is it more complicated than that? I suppose it would be safer to inspect the board itself and compare it to a Phoenix Android board.
[Android Head-Units] ikuznets222:
No, big boards are totally incompatible between factories. They contain FM, BT , TDA amplifier chip, and other components. Android doesn't "see" this board, so it's not visible in any settings screen. MCU chip is soldered on smaller, android board (that Phoenix offers as a replacement). It contains MCU code that allows android to work with FM, BT modules on big board. MCU code of one factory will not be able to work with big board of another factory.
[Android Head-Units] ramathorn1982:
So how does one verify the factory of manufacture and/or MCU compatibility? Is there a way?
[Android Head-Units] ikuznets222:
None that I know of. Only physical comparison. I once compared two 4.4 units for Ford Kuga made by different factories. Big boards had almost nothing in common, totally different layout. Only socket for small board was the same.
[Android Head-Units] ramathorn1982:
As always, thanks and wish me luck!
[Android Head-Units] ikuznets222:
As always, good luck. Let's hope only one factory makes units for Ram (highly likely)
[Android Head-Units] marcus82:
I'm so happy.. Now I have dashcam in aux in

Inviato dal mio ONEPLUS A6003 utilizzando Tapatalk
[Android Head-Units] ramathorn1982:
Got RDS sorted out too...
[Android Head-Units] ramathorn1982:
How did you manage to get that?
[Android Head-Units] marcus82:
I only update the firmware to reset aux input disappeared on my HU and plugged RCA out of the dashcam to video in of the radio

https://www.instagram.com/p/BrLF0kxFZKa/?utm_source=ig_share_sheet&igshid=1971chku328ue

Inviato dal mio ONEPLUS A6003 utilizzando Tapatalk
[Android Head-Units] wishie197:
Hi ikuznets222,

Im wondering if I can bother you to help me with another thread about a similar unit on 4pda.. its in Russian (of course) and Im trying to work out if I can use some of the firmwares etc on my current unit (not the Tesla style one I have on the way)
[Android Head-Units] ikuznets222:
Send me your question in a PM.
[Android Head-Units] marcus82:
at this point, I'd like to have the split view of 7.1
[Android Head-Units] wishie197:
I think if I had the choice, I'd take a 7.1 unit with fast boot over the (for now) more customisable 4.4.4 based unit.
[Android Head-Units] marcus82:
unfortunately for my ford focus there's only 4.4.4
[Android Head-Units] wishie197:
My stereo has just arrived in the mail.. going to unbox and install it now.. will report back with firmware version and some screenshots etc in the near future
[Android Head-Units] marcus82:
Which car?

Inviato dal mio ONEPLUS A6003 utilizzando Tapatalk
[Android Head-Units] wishie197:
Sorry for late response.. of course the day my stereo arrives, work gets crazy. I only just got around to installing it (partially -- no add-ons connected yet)

Its for a 2003-2010 Mazda 6 sedan.

Ill attach some photos, and then start discussing any issues I have so far with the unit.

1) Appears to indeed be a unit based on 4.4.4, which means it does not have fast boot (even though the seller claimed it did).

2) It reports to be running Android 6.0.1.

3) Steering wheel controls are not working.

4) Climate control is not working.

5) OBDII readout is not working.

6) I don't know the password for the "Factory Settings" section (although installing another launcher temporarily seems to have got me access -- would still like to know the password though)
[Android Head-Units] marcus82:
The same situation of mine!

The two passwords are 7890 and 8861

For swc I'm so angry and I'm waiting any upgrades or interfaces. Please help me to ask them for it

Inviato dal mio ONEPLUS A6003 utilizzando Tapatalk
[Android Head-Units] wishie197:
I have already asked the seller how to fix these things, otherwise I want money back. I will try the passwords you suggested soon, see if they work.

Now, Ive forgotten what I read in the 50+ previous pages.. there was some firmware updates, yes? How about MCU updates?
[Android Head-Units] marcus82:
Yes, I just installed the last firmware.

Inviato dal mio ONEPLUS A6003 utilizzando Tapatalk
[Android Head-Units] wishie197:
Do you have a link handy for the firmware and/or MCU, and how I apply it? Not keen on reading back through 50+ pages..
[Android Head-Units] marcus82:
Here it is

Inviato dal mio ONEPLUS A6003 utilizzando Tapatalk
[Android Head-Units] ikuznets222:
MCU updates for these units are rarely publicly available. I think only Carcool factory were making them available to sellers at some point. Tricky part is that MCU code must be from exactly the same factory that produced the unit, otherwise modules on big board (FM, BT) may not work any more. There are no labels or marking on the unit that would allow one to identify which factory they come from.
[Android Head-Units] wishie197:
Ok, so firmware update it is.. I have to backup some customer.xml file first, yeah? I'll go digging in the previous pages again..
[Android Head-Units] ikuznets222:
Yes,

/system/app/customer.xml

plus

/data/data/com.szchoiceway.eventcenter/databases/SysVar.db (it's a settings database, but the file may only be accessible on rooted FW)

- OR -

settings export in MCU settings (passworded section in Chinese settings app). There's an "export" button with effectively just copies SysVar.db above to a flash drive

- OR -

photos of all Chinese settings screens (light-grey background)
[Android Head-Units] wishie197:
I need to find what the password to my Chinese settings section is, as none of the ones I have tried work.
[Android Head-Units] ikuznets222:
These passwords generally depend on CustomerNum in /system/app/customer.xml and selected theme (currently black theme 71 has its own passwords). So if you provide your CustomerNum and a copy of /system/app/NaviSettings.apk I can extract those passwords for you.
[Android Head-Units] wishie197:
I will be back online in about 1hr and will start this process.. wife wants to watch a TV show right now..
[Android Head-Units] wishie197:
Im back, firmware updated, customer.xml replaced.. I have a copy of NaviSettings.apk and have decompiled with apktool...where can I find this password?
[Android Head-Units] lio524:
Disable upper and lower status bars
[Android Head-Units] lio524:
Like this
[Android Head-Units] bphillips09:
Unfortunately I don't think that is possible.