yashsingh1/xdaforums huggingface dataset:
[MTCD  Android Head Units Q&A] joshnat:
I haven't gone through the settings systematically, but what I've hit seems to work, including Accessibility Services, which was missing in the factory rom. If SystemUI crashes immediately, will I still be able to push the original back via ADB?
[MTCD  Android Head Units Q&A] doitright:
I don't mean checking through system settings. I mean checking system FUNCTIONS, like does the AMFM radio work as expected? Does the GPS still work? Does a bluetooth phone call still work? Audio mixing working as expected? Stuff like that. In a decompilation of the "china" version of Settings, I saw some functions and services that seemed out of place, not sure if they play an important functional role or not.

adb functionality does not depend on systemui working correctly, so it should continue to work even if systemui crashes. Don't think that it will crash though, since the systemui you are pushing in is the one that is actually built with the system image, rather than the add-on hacked up chinese one.

I actually would expect LESS bad side-effects from changing systemui than settings.
[MTCD  Android Head Units Q&A] joshnat:
Ah, ok. Yes, the major functions seem to be working as before, which is a bit so-so. GPS often struggles to get a fix after wakeup, requiring a reboot. FM radio reception is pretty poor, even after fiddling with the sensitivity settings. The EQ settings don't really seem to do that much to affect the sound. Phone/bluetooth connects fine. Wifi sometimes doesn't hold onto a connection that well. But, all of these were present before changing out Settings.apk.

This is the cost of being an early adopter, so I'm ok with it (it's sort of fun, actually). I look forward to MCU firmware updates from Joying or here to improve these things.

I'm not sure what the audio mixing setting does, though. If I recall correctly, that's in CarMediaSettings, which seems to be stuff that's directly associated with the MCU and Canbus. There's a bunch of stuff in there I don't get, like parking brake safety, door lock interference, default volume switch, etc.

I'll try swapping out SystemUI.apk tonight to see what I get.
[MTCD  Android Head Units Q&A] joshnat:
So the AOSP SystemUI.apk worked without crashing. It gave me the vanilla AOSP status bar, with very small icons, notifications visible, and standard quick settings. I didn't see any other changes, but I suppose the navbar could also be enabled in the build.prop? Regardless, the AOSP version provides less info and functionality for me than the Joying one, so I reverted back to the OEM SystemUI.apk. I'll stick with the original until we are able to modify the layout and quick settings easily, similar to xposed modules or what's built into cyanogenmod.

One thing I did notice is missing in the settings with the AOSP Settings.apk is the day/night brightness control. But it still dims when I turn on the headlights, so it must be working in the background.
[MTCD  Android Head Units Q&A] avnb39:
I just read through all this, and I'm surprised by the amount of information everyone's found about these head units already. Great work.

I myself just picked one of these up, and I'm wondering about the RCA aux input that exists on the back. Anyone used it or know how the audio is routed? I'm thinking about using that and rs232 dongle to interface with a SiriusXM tuner.
[MTCD  Android Head Units Q&A] doitright:
Excellent. From the sounds of it, we should be able to do AOSP builds just to obtain our own custom systemui. Probably won't be too big of a deal to add in whatever added head unit specific buttons are desired, although personally, I don't find the extra quick settings at all useful.

The sizes glitch is easily corrected by jacking up the DPI in build.prop.
[MTCD  Android Head Units Q&A] wanb1i:
You can do that and more with Nova Launcher and Poweramp. You can literally build your own UI with Nova Launcher Prime.
[MTCD  Android Head Units Q&A] KamaL:
I use Nova prime on many devices. Is it easy to replace the stock joying ui with nova prime? Will it load on each startup?
[MTCD  Android Head Units Q&A] wanb1i:
Yes, be sure all updates are done and root it 1st. Then install it just like any Android device, install Titanium and freeze both stock launchers (mine had 2), then build your UI. Here's a link to my video:

https://drive.google.com/file/d/0B_EZzFL4XjdLSkZwTEhibmdNTHc/view?usp=drivesdk
[MTCD  Android Head Units Q&A] CadillacMike:
Is anyone else able to get Widgets to work on Nova?
[MTCD  Android Head Units Q&A] wanb1i:
I have no issues with widgets. I did initially, but then I did the update, rooted it and froze the stock launchers (mine had 2) and it has worked fine ever since. See my video above.
[MTCD  Android Head Units Q&A] doitright:
Well, bad news about switching to AOSP SystemUI.... the nav bar isn't part of SystemUI, its part of frameworks/base, and it looks like china may have actually DELETED it from the source before building, since it does NOT respond to qemu.hw.mainkeys=0.

So to fix this properly is going to need a rebuild of frameworks/base, which may not be trivial, since likely there are a lot of other hacks in there.

EDIT: The nav bar *is* supposed to be part of SystemUI, frameworks controls whether or not it displays, and our frameworks does appear to have the code to control it.

So problem could still be in a butchered SystemUI.

I will look into it more deeply, but it is looking like it may be possible to implement the fix without screwing with frameworks or device policy.

Yep. While *closer* to AOSP SystemUI, the one in the update package is still pretty severely hacked up.
[MTCD  Android Head Units Q&A] joshnat:
Bummer about the navbar. I wonder if a 3rd party navbar addon would provide a solution?
[MTCD  Android Head Units Q&A] doitright:
Easier. We just build SystemUI from AOSP source.

Edit: may have found an easier solution.

They're doing a bunch of checks in systemui with a function called isCar().

Well, isCar returns the true/false value of system prop ro.rk.product.build.module

Essentially, when "ro.rk.product.build.module=true", isCar() returns true.

However, I don't have high hopes for this. I *believe* that they just alter the nav bar if it isCar. It isn't supposed to control whether it works or not.

Edit: Confirmed. Doesn't do anything useful, since they broke the nav bar somewhere along the line.
[MTCD  Android Head Units Q&A] RWerksman:
Considering all of the other hacky stuff with these, is anyone really surprised? Butchered DPI settings for all of the MCU control programs, wiring issues with the mic, terrible FM and AM receiving, bluetooth shenanigans, usb LTE stick incompatibilities... it's all rather appalling.

That said, the concept is SO good, and these are about as close as it gets. :(
[MTCD  Android Head Units Q&A] avenant:
There is a systemless version of Xposed, with something new called: Magisk:

[UNOFFICIAL][Magisk][Nov 28] Xposed v87.0 - Universal Systemless Compatibility

[OFFICIAL] [2016.11.15] Magisk v9 - The Universal Systemless Interface [Android 5.0+]

wonder if it might work on intel?
[MTCD  Android Head Units Q&A] twokidsandaphone:
Just to quote myself here, in the hopes of helping someone avoid panic. I discovered that if the 12v constant and 12v ACC are applied simultaneously to the unit (say in bench testing) then the unit will not boot. The 12v ACC must be applied after 12v is already present on the constant line. I have no idea why this is. That was what was happening to me rather than a flaky connection, as I earlier thought.
[MTCD  Android Head Units Q&A] twokidsandaphone:
Just got the Bonroad Intel installed but when I try to sign in to google I get Google Play services have stopped. It worked when I first got the unit but I installed the update in the first post and now not working. Should I try finding Google Play services .APK somewhere?
[MTCD  Android Head Units Q&A] twokidsandaphone:
Ikerg, can you post a link to this file again? The links on the first post actually point to two identical files (stored in two different locations) which are both the "original" firmware.n Thanks!
[MTCD  Android Head Units Q&A] ikerg:
I checked it on my phone and it goes to the zip file with the update

Enviado desde mi D6603 mediante Tapatalk
[MTCD  Android Head Units Q&A] twokidsandaphone:
I just tried again:

1. I d/l the "original firmware" from the link on the first post

2. I renamed the file "update_sep.zip"

3. I d/l the "update firmware" from the link on the first post (in the folder linked there is also a how-to video)

4. I renamed the file "update_oct.zip" - note, the name as downloaded is "update.zip.jar"

Under a win7 cmd window I ran

fc /b c:\users\xxx\downloads\update_sep.zip c:\users\xxx\downloads\update_oct.zip

and windows returns

FC: no differences encountered

So the two links, while pointing to two different locations, have the same file at each location. I had previously installed files from both locations and in the "about" tab it shows a September file.
[MTCD  Android Head Units Q&A] ikerg:
I know it is from oct 20th ...at least the sofia3gr one i installed (the same.as ot was installed on the unit).

Enviado desde mi D6603 mediante Tapatalk
[MTCD  Android Head Units Q&A] twokidsandaphone:
I know but the link you originally posted is dead and the one on the first post is wrong so I was hoping you could u/l the file somewhere... I would appreciate it!

---------- Post added at 08:38 AM ---------- Previous post was at 07:40 AM ----------

Forums suggested something is up with Google Play services, so a factory reset will break the log in. To solve go to APK mirror, download the latest "270" version of Google Play services, and install. You can now log onto your Google account, and after a few minutes Google Play will update itself.
[MTCD  Android Head Units Q&A] doitright:
Probably safer to use a system version that doesn't require modification of boot image, since we don't have a reliable way to boot into recovery.

Why would you want it to be systemless? The objective of systemless is to allow your SECURE device to run an unmodified system image, thus maintaining the system partition checks.

---------- Post added at 03:00 PM ---------- Previous post was at 02:57 PM ----------

That is interesting.

The Joying units do NOT exhibit this characteristic, so it must be restricted to MTCD versions.

Good thing for people to be aware of!
[MTCD  Android Head Units Q&A] swanie2000:
****************************************************************

Hi all,

I am trying to load the default Settings.apk, as was discussed back on page 52.

I have the new Joying unit, JY-UL135N2 Unit.

I believe it is rooted, as root checker confirms it is rooted. So I think I am past that step.

I can (adb connect 192.168.175.33) which is the IP address of my head unit on my router.

The next step, (adb root) When I send this command, the cursor just drops to the next line, and nothing happens?

I have waited up to 20 minutes, and nothing happens, so I have to Control+C to break it out.

Any ideas as to why I cannot issue this command?

I ended up skipping this command, and had mixed results with the following steps.

I got all the way to ( adb push Settings.apk /system/priv_app/Settings/ )

It even looked like it was uploading the file, but when it was done, the settings had not changed.

I'm thinking it is because of the root command, I cannot send, for whatever reason.

Thanks for any help you can give!

FYI:

I am trying to run tasker, to kill a few audio apps when other other audio apps start. I have found some times, one audio app will not close when I start another, and I get two audio apps running at the same time. Tasker will solve this, but it needs access to the full settings/accessibility service menu. This menu is stripped down to bare minimum with the Joying firmware, and tasker cannot enable it's services. SO this is why I am trying to default back to the AOSP settings.apk.
[MTCD  Android Head Units Q&A] joshnat:
If you're not getting a root shell cursor after ADB root,I have a feeling you're not rooted. You'll need to root according to the instructions in this thread before you can modify the settings.apk.
[MTCD  Android Head Units Q&A] swanie2000:
I was thinking the same thing, however...

I just installed root browser, it popped up asking to be granted SU permission, and I granted it. Then it wanted to update busybox, which also needed SU permission, and I granted it. These two programs need ROOT, as well as root checker, it reports that I am rooted.

I still don't know why the (adb root) command hangs??

But, in order to move forward, I installed the settings.apk the hard way, manually, with root browser. After I moved the file to the correct folder, a long click on the settings.apk popped up an option to set permissions. I set them to 0644, which is what the original file was set at. After double checking it was correct, I rebooted, and like android magic, I now have the FULL SETTINGS menu. I was able to make tasker happy in the settings/accessibility/services menu. PLUS, I was able to link up a bluetooth keyboard that previously refused to cooperate with the Joying.

So this problem is solved, and I'm on to the next problem.....

One thing I would like to note, in case any other rookies like myself read this:

There are two paths that had settings.apk.

system/priv_app/settings/settings.apk

system/priv-app/settings/settings.apk

I copied the original AOSP settings.apk file into each of these paths, and changed permissions on each of the files to 0644

Swanie
[MTCD  Android Head Units Q&A] ryhoo2:
Guys, do you have some reliable source for original AOSP Settings.apk? I want to try it (especially to see if the 3G/Mobile modem is configurable), but I don't want to copy some random apk from the Internet. Thanks!
[MTCD  Android Head Units Q&A] Ejpi16:
Do you still need a full backup?

I have my Joying Ul128N2 device for 6 days now and i am willing to help you with this. I can also help you with more if you want... just tell me.

My device is almost the same as the UL135N2, my device has capacitive keys and the UL135N2 has hardware buttons.

If someone can provide me a settings.apk rather then finding it randomly on internet i am willing to try it as well.

Here some pics of the unit inside:
[MTCD  Android Head Units Q&A] Ejpi16:
I first downloaded a settings apk from the internet but that one failed. I searched in the latest intel update from joying and found a settings apk in: 5009_20.zip/system/priv-app/Settings

Installed that one thinking that would be the original one, now i have the real settings menu back. See pics, also attached the Settings.apk
[MTCD  Android Head Units Q&A] Cid6.7:
Ive got the same unit as k2c Ive tried looking for the factory settings password and developer options anyone know what the pass is ? Thanks
[MTCD  Android Head Units Q&A] wanb1i:
3368 is the PW
[MTCD  Android Head Units Q&A] Cid6.7:
Is that the factory settings password ? It wont work for me.. :(
[MTCD  Android Head Units Q&A] KamaL:
Was it that simple? Simply installing settings.apk file reset it to the original settings menu?
[MTCD  Android Head Units Q&A] ikerg:
126

Enviado desde mi D6603 mediante Tapatalk
[MTCD  Android Head Units Q&A] Cid6.7:
Thank you that got me into the factory settings.

Are there developer options on these units as well ?
[MTCD  Android Head Units Q&A] Ejpi16:
That's what i did so i suppose the answer is yes. Take a try you can always reset.
[MTCD  Android Head Units Q&A] KamaL:
It failed it install. How did you install it?
[MTCD  Android Head Units Q&A] Ejpi16:
Follow these steps: https://xdaforums.com/android-auto/...eres-specs-t3468322/post70054526#post70054526
[MTCD  Android Head Units Q&A] avenant:
is there some way to remember the radio stations presets after a restart for intel units? for non intel units there is a xposed module for this, but since there is no xposed for intel.... or do the joying intel units not have this problem?
[MTCD  Android Head Units Q&A] zorantoma:
The intel units(mine) doesnt soffer from this problem.
[MTCD  Android Head Units Q&A] wanb1i:
The Joying units, if wired correctly, don't have this issue. Be sure it's wired with the yellow wire (assuming use of the ISO harness) to the battery positive and the red wire to the "accessory" wire of the ignition switch. The battery wire will keep the memory of the unit while the car is off.
[MTCD  Android Head Units Q&A] deedeebulldog:
I just got my unit and I have an issue where my steering wheel controls only work when the car is stopped. Anyone else have this issue or better yet solved this issue?
[MTCD  Android Head Units Q&A] gtxaspec:
has anyone dumped the rom yet? as in the filesystem on the device, preferably a new unit?
[MTCD  Android Head Units Q&A] Sylvan151:
HotAudio

Will this work for my unit?

MCU Version

MTCD_HA_V1.93_1

Oct 17 2016 15:32:59

Android Version

5.1.1

Kernel Version

3.0.101+

chun@hctr930 #188

Thu Oct 20 17:06:17 CST 2016

Build Number

rk3188-userdebug 20102016.20:05:12

Please advise, thank you.
[MTCD  Android Head Units Q&A] ikerg:
You don't have a mtcd sofia based chip...so no

Enviado desde mi D6603 mediante Tapatalk
[MTCD  Android Head Units Q&A] Sylvan151:
What is my chip?

Thanks ikerg.

I am still new on this stuff. What is my chip?
[MTCD  Android Head Units Q&A] ikerg:
You have a rk3188...go to the corresponding thread for mtcd rk3188

Enviado desde mi D6603 mediante Tapatalk
[MTCD  Android Head Units Q&A] Sylvan151:
CPU

Thanks [MENTION=7975723]youdontkn0me[/MENTION],

how do i upgrade my CPU?
[MTCD  Android Head Units Q&A] Ejpi16:
Yep i did, with my personal settings but i am willing to make a clean dump of the rom. Also posted that a few pages back.
[MTCD  Android Head Units Q&A] bernardo65:
Root

I have a Pumpkin 13 RQ0278E-DE-A 2 GB RAM, Android 5. 1. 1 with built-in 3 G modem with baseband and RIL, MCU MTCD_LM_V1. 98. 1. Root problem with 'udate.zip' 'Post 218 deletes the baseband and the RIL file. Device is rooted but no more modem. Is there a root that prevents this?
[MTCD  Android Head Units Q&A] gtxaspec:
wow Awesome! If you could do a clean dump, that would be awesome! Which model unit do you have? Thank You!!!
[MTCD  Android Head Units Q&A] bernardo65:
New update for MTCD (Non Joying) Sofia Units (as per 20th December 2016)

Has the device after the new update root?
[MTCD  Android Head Units Q&A] Ejpi16:
I have a Joying UL-128N2.

In what format do you need the dump?
[MTCD  Android Head Units Q&A] avenant:
My car didn't give constant 12v to the yellow wire when key was out of ignition, so I used a fuse tap/add-a-fuse like doitright suggested earlier in this thread, connected it to door locking system, this fixed unit powering off when turning ignition, but android doesn't go into sleepmode when the key is out off the ignition, so radio channels are not remembered.

when I tested the unit at home, connected to a breadboard, to simulate ignition key, when pulling out the red wire, the unit went into sleep mode and woke up again when connecting the red wire again.

so I made the hardware modification from this thread

but it still doesn't go into sleep mode.
[MTCD  Android Head Units Q&A] wanb1i:
Contact Joying to get a RMA to send it back, you have a defective unit.

---------- Post added at 08:38 AM ---------- Previous post was at 08:36 AM ----------

You will need to redo the root process after the update. Be sure to backup everything first.
[MTCD  Android Head Units Q&A] ikerg:
i am trying to build a Prerooted ROM for both 3G and Wifi versions...

AS I have investigated, the Rooting process by update.zip on post 218, just modifies selinux policies and updates boot.img with some su additions.

The creator of update.zip rooting tool used the boot.img file from a Wifi version

I have compared both boot.img from 3G and Wifi versions and only is changed some values on default.prop file (in which it is activating the 3G parameters)

I have built a boot.img for 3G with root capabiities in a similar way it was done for WIFI version, but based on boot.img for the October version.

I modified the script and created the zip and signed with SignApk.

here you are a zip that should be usable for obtaining root for 3GR Sofia (not valid for wifi only versions - sofia3grw)

you can check if worked. You should rename to update.zip

https://drive.google.com/open?id=0BzpR8k0kgZq3c08teWJJbHpqLVE

You can apply this update directly to your system (rooted and without radio capabilities) in order to keep root (if not rooted it will root) and to activate radio capabilities (3G - RIL and Baseband)

Or simpler...just change your default.prop file with these settings and reboot:

EDIT: Change default.prop file will not cause any change as during boot will revert to original state as it is written into the RAMDISK, only by updating based with the proper configuration (as the file i uploaded) will solve the issue
[MTCD  Android Head Units Q&A] avenant:
turns out the manual of my car about the fuses location was wrong, connected it to different fuse, now tried with multimeter and was able to get permanent power, only problem now it drained my car battery in 1 day in sleep mode lol. so now I reverted back to complete power off, thinking about doing the modification from this thread: Auxiliary Battery + Battery Isolator = No Radio Startup Delay!

I installed the "New ROM Update for MTCD" on my 1GB/16GB Isudar intel unit, works fine, needed to reroot it after the update with the update.zip to root earlier posted in this thread, also make sure to select to do a wipe when updating, because I didn't and got stuck in a bootloop where apps needed to be optimized and this process never finished and android kept rebooting to try to optimize apps, had to boot to recovery and do a wipe to fix it. afterwards I had to reinstall all previously installed apps.

BTW this is an awesome app: Dashmaker, it let's you create custom dashboards with gauges and meters etc.. from OBD values, just like Torque but much more advanced and more customizable.
[MTCD  Android Head Units Q&A] doitright:
Do you see voltage level translators on those pictures? I sure dont.
[MTCD  Android Head Units Q&A] schriss:
Can you install this? It's free and will show memory in use and available to system.

https://play.google.com/store/apps/details?id=nextapp.systempanel
[MTCD  Android Head Units Q&A] kc2koj@hotmail.com:
i could and will ..but it doesn't look like it will display anymore info then i have already posted...what info will this tell that the other app haven't..
[MTCD  Android Head Units Q&A] kc2koj@hotmail.com:
is there an app you could direct me to that would only run if the cpu was an x86 ....

i did the research on this cpu and it was made be rockchip and intel as a joint venture ..i dont know why you think its impossible ..

link for intel https://software.intel.com/en-us/bl...atom-x3-code-named-sofia-soc-processor-series

link for rockchip http://www.rock-chips.com/a/en/products/SOFIA_Series/2015/1125/734.html

same chips

on the intel link a little ways down the page it says

The Intel® Atom™ x3-C3230RK processor, a collaboration between Intel and Rockchip*, includes a quad-core 64-bit Intel® Atom™ CPU and an integrated 3G modem. Figure 3 describes this SKU’s high level architecture.

http://www.intel.com/content/dam/www/public/us/en/documents/product-briefs/atom-x3-c3000-brief.pdf
[MTCD  Android Head Units Q&A] lordxenu:
Which SDR please? I have a DVB-T dongle I use with rtl_sdr to use as a scanner. I'm really interested in running an sdr scanner in my car since I work near Heathrow and find pilot chatter extremely interesting .

Can you tell me which app you use ? and which dongle ? Is it rtl_sdr compatible ? thanks.
[MTCD  Android Head Units Q&A] kc2koj@hotmail.com:
sdrtouch you also need the rtl-sdr driver you can download both on Google Play Store they work great on my unit ..the only thing is that i found it has trouble sharing a usb on a hub but works great alone

all dongle should work i have 3 or 4 types here they all work

I need to find an app that will decode digital Transmissions if anybody knows of any let me know of any let me know