yashsingh1/xdaforums huggingface dataset:
[MTCB Software Development] champikasam:
Thanks for the info.

I have a Honda Fit/Jazz 2013 version (GP1). Currently, the wiring harness i use does not have a can bus decoder, but i plan to buy this one which comes with a can bus decoder:

https://www.carjoying.com/joying-ha...-dash-android-car-stereo-radio-head-unit.html

I couldn't find an exact harness for Honda Fit/Jazz (above is for Honda Civic). But all the sockets/connectors given in the pic are there in my car so i'm thinking this will work. Any comments ?

Thanks !

---------- Post added at 07:59 PM ---------- Previous post was at 07:58 PM ----------

Sure, thanks for the info :)
[MTCB Software Development] typos1:
Yeah that should work, just make sure the wires going to the head unit go to the same places in the plug on the back of the unit, or you could end up with a fire. If theyre not you should be able to move them.
[MTCB Software Development] Vsio:
Hello.

How can I enable Developer mode?
[MTCB Software Development] warata:
in my case

https://play.google.com/store/apps/details?id=net.selfip.unet.developer_options
[MTCB Software Development] thachosenone:
Bump. Anyone? I'd really appreciate it.
[MTCB Software Development] typos1:
Its a problem I ve heard a lot about, cant remember if theres ever been a solution, you ll have to search the MTCB forums, google is good for searching xda.
[MTCB Software Development] dsa8310:
New mtcxp Version 1.2

mtcxp-1.2.apk

I have recently noticed that, strangely, a side-loaded/patched TT won't let me download any map - with their usual network unrelated error message.

So I had to use Device Faker (a 5.1.1 Android (sdk 22) device must be selected!) to get Play Store/TT available for downloading.

The rest is done by the new mtcxp version above. Future upgrades of Play Store/TT should also be supported.

A mere update of mtcxp (followed by reboot) is enough.

Good for KK 4.4.4 as well.

===

If it makes no difference to you, don't use it! I wish it was not necessary for me either, but with no map&miles, TT is pointless, after all...

===

And what's "the rest"? DADT... :)

===

I will add the possibility of opting out of the TT enhancement, in the next mtcxp version. For conscience objectors, of course.
[MTCB Software Development] dsa8310:
mtcxp v1.4

mtcxp-1.4.apk

This is the final recommended mtcxp app, for both LP and KK.

One can opt in&out from all parameters (followed by reboot), including the latest addition, the TT GO one. And don't forget to write down and reuse ro.serialno as needed, otherwise networking access gets denied by TT.

Once the

original

(Play Store) TT GO app is acquired (either from a different device, or by temporarily using Device Faker on the HU - it's file /data/app/com.tom*/base.apk) it could be installed and subsequently upgraded without loosing the existing map data.

I will shortly update the remaining LP&KK firmware, and with a small twist - they will all include the dsa logo. For convenience. :)

(done)

===

I have made a last moment update to version 1.4 just to include the full range of app icons. The firmware still includes v1.3, with the very same functionality, hence equally good for our HU.
[MTCB Software Development] lopunia:
I installed mtcxp-1.4.apk but unfortunately nothing changes. TT starts it, but when I go to download the map I have a message:

"Download paused. Download will continue when your device is connected to a network" :(

Device Faker is not working for me.

I have TT go to the latest version * .apk format.

What am I doing wrong? :confused:

Can you explain exactly how to do this? :o
[MTCB Software Development] dsa8310:
Yes, use the original TT GO app and don't change parameter ro.serialno (with mtcxp) as known to TT at its first run.

Follow these steps:

Uninstall whatever other existing version of TT from HU.

Get the Play Store/TT GO apk. Use a different device (phone) to install it, it will be file /data/app/com.tom*/base.apk, transfer it to a micro SD card, rename it (e.g. TTGo.apk). Now you have the original app ready to side-install to your HU, install it.

Device Faker works also, and you may have to use it if the side-installation described above won't help: - select, for instance, the first Sony model of version 5.1.1 (or 4.4.4 if under KK), then activate the xposed module and reboot; an app like Device Intel will now show the fake Sony info, and Play Store direct download/installation of TT GO will succeed. Once installed, you may uninstall Device Faker and reboot to the rk3188 real model.

Write down the value of parameter ro.serialno as displayed by mtcxp; make sure its module is activated (and reboot if it was not - but under LP it is always pre/re-activated automatically). You will want to restore (with mtcxp, followed by reboot) this parameter as known to TT at its first run, to avoid the false networking issues reported by TT when it notices a change of it (for reasons like uninstalling/installing mtcxp instead of the recommended mere upgrade).

Start using TT GO, download maps, voices.
[MTCB Software Development] lopunia:
Great thanks for explaining step by step.

At this point everything works. I used the way with Device Faker. I chose SONY and it works.
[MTCB Software Development] dsa8310:
mtcxp-1.5.apk

This version is funnier! :)

However, I have just discovered that under Nougat 7.1.2 the de.robv.android.xposed.XSharedPreferences class can no longer read the actual parameters, and therefore only the default values are available. Seems a SELinux enforcement issue?

(solved)

It's of no concern to our HU, but I had to set proper defaults in order to check it out on my phone...

===

Firmware is now updated in OP.
[MTCB Software Development] dsa8310:
mtcxp v1.6

mtcxp-1.6.apk

(bug fix in v1.7 below)

This version should be final and Nougat/Oreo ready.

Beware, by default all parameters are not spoofed.

(now included in the OP firmware)
[MTCB Software Development] Blano:
Hello

good job

gipt it the radio app in red?

Thank you
[MTCB Software Development] dsa8310:
Nicht from mir. :)
[MTCB Software Development] dsa8310:
mtcxp v1.7

mtcxp-1.7.apk(outdated)

An actually inconsequential bug fix, sorry about it... Firmware will be again upgraded, soon... done.

Note that for use on a regular phone, xposed enabled, parameter ro.serialno should be left erased, with summary equal to not spoofed, or, even better, set to its real value, as shown by an app like Id, for commodity.
[MTCB Software Development] dsa8310:
I'm done for the foreseeable future... Happy time travelling with mtcxp! :)
[MTCB Software Development] maxmafia:
Hi! Dsa first of all thank you very much for this ROM. It's awesome! Thanks.

I come from your September 2016 Lollipop ROM and I have to say that this one, the Open Gapps Lollipop one, is very very faster and works much better in general. Haven't test the Micro Gapps yet.

I have read all the thread and have a few questions:

How can I activate the voice commands for calling? Obviously, without installing Google App, that would slow down the performance so much (I had that in the old ROM and It worked, but veeery slow).

Which app would you recommend for doing effective restarting of the HU? I have test some of them but they don't restart completely, there's still some processes opened like wifi, BT, or USB.

I do the last question because sometimes at powering on my HU it doesn't start this systems and I have to shutdown by reset button (or powering off my car) and then power on again. Then It works well. I repeat, sometimes, in 5% times.

Thanks again and congratulations for the ROM.

Edit: I am using launcher Joying, for more information ;)
[MTCB Software Development] dsa8310:
mtcxp v1.8

mtcxp-1.8.apk - cut&paste bug, fixed in v1.9...

This version phases out TYPE_WIFI spoofing (which was possible only under LP) in favor of a dedicated TT GO WiFi spoofing, necessary for downloading TT data when HU is connected to a non wifi network, e.g. Ethernet (my case, actually a mini router with LTE modem, but classic wired networking works too).

Firmware updates follow up... done.

Now I'm done! :)
[MTCB Software Development] dsa8310:
Thanks.

If worried for performance, switch to KK (it's JY by default!) in the peer thread.

Beside Xpoosed Installer, which includes reboot in its menus, I use Real Reboot for full reboot.
[MTCB Software Development] dsa8310:
Final mtcxp v1.9

mtcxp-1.9.apk

A cut&paste error, fixed.

Upgrade, or wait for the firmware update... done.

BTW, mtcxp works on any Android device, xposed enabled.

On the HU, select as many option as you want (all), on others (phones), as few as possible (one), eventually with the real ro.serialno (or erased, not spoofed).
[MTCB Software Development] Newcomerpx3:
Hello

Hello [MENTION=6041319]dsa8310[/MENTION] and everyone

Which upgrade do you suggest for my car android head unit

I really need your advice

Many thanks in advance

Btw my blutooth is not working exactly after i upgraded to this current version

My current info is

mcu version: MTCC-KLD6-v2.97

Android version

5.1.1

1024 * 600.

Kernel version 3.0.101+

Chun@hctr930 #44 .

Sat oct 8 2016 .

Rk3188 userdebug 11102016.
[MTCB Software Development] dsa8310:
Funny enough, it works even on my Marshmallow 6.0.1 Android TV Box, with wired Internet - not that I could navigate it anywhere - for lack of GPS, undoubtedly! :)
[MTCB Software Development] dsa8310:
I cannot guess if or why you upgraded which HU to what.
[MTCB Software Development] Newcomerpx3:
Sry for my bad English and explanation

Mcu version was 2.92 not sure actually ?

Then i upgraded to 2.97 ...

Now with this device info(configuration)

""mcu version: MTCC-KLD6-v2.97

Android version

5.1.1

1024 * 600.

Px3 1gb ram

Kernel version 3.0.101+

Chun@hctr930 #44 .

Sat oct 8 2016 .

Rk3188 userdebug 11102016""

Can i install Open GApps "oxupdateKLD1024x600LP5.1.1.rk3188.MTCB-C.December.part1.rar" on my HU?
[MTCB Software Development] dsa8310:
Yes, you can (both parts, decompressed to one file, update.img, firstly), if, and only if your unit is originally of type MTCB or MTCC, rk3188 processor. It's up to you to determine that...
[MTCB Software Development] dsa8310:
This mtcxp-2.0.apk is configurable on-the-fly, without reboot, for all parameters but the obscure config_voice_capable.

(it's just been reloaded)
[MTCB Software Development] pczao:
[MENTION=6041319]dsa8310[/MENTION], how can I disable DSA logo and keep car brand logo?
[MTCB Software Development] dsa8310:
mtcxp v2.2

Final version of mtcxp, v2.2:

mtcxp-2.2.apk

(back in business!)

To summarize:

config_voice_capable, and, under LP only, sta_mcu_version are always spoofed, to enable calls from True Contacts, and to defeat the black screen issue, respectively. Both are hidden.

ro.serialno is configurable; should be kept unchanged with its value at first TT GO run after a fresh installation (not upgrade), otherwise a fake networking error message is thrown by TT. On other devices (phones) should preferably equal the real value.

the remaining parameters, configurable as well, are per TT GO's use, e.g. to let it make downloads via other types of networking than wifi (on mobile data, on Ethernet, with no questions asked).

The configurable parameters could be changed on-the-fly, with no reboot needed. TT GO might need a restart though (in case of wifi and ro.serialno spoofing), however much better than a device reboot.

It also runs on any Android device, xposed enabled.

Firmware update, next... done!
[MTCB Software Development] dsa8310:
I have replaced only the Android logo with mine (it's included in kernel.img, could be edited with SergioPoverony's tools), while the boot animation, which could show a car logo, is unchanged.

See also post #311 for details.
[MTCB Software Development] Newcomerpx3:
Hi dear [MENTION=6041319]dsa8310[/MENTION]

Last question before my upgrade.☺

Can i install kingoroot then?

I use disable app which requires root access in order to disable some certain apps like gmail goole play store and etc....

Would that be alright if i do so?

Regards
[MTCB Software Development] typos1:
No need - all [MENTION=6041319]dsa8310[/MENTION]'s ROMs are rooted out of the box.
[MTCB Software Development] dsa8310:
All, please disregard all current firmware, I must fix mtcxp first, falling back to the static version...
[MTCB Software Development] dsa8310:
We are good, firmware with the latest working mtcxp v2.2 has been released...
[MTCB Software Development] dsa8310:
No, no need to, LP firmware is pre-rooted & xposed.
[MTCB Software Development] dsa8310:
Just to clarify, at no moment was the firmware compromised.

Only the mtcxp xposed module (mandatory for LP) had temporarily prevented TT GO running, until the recommended v2.2 version has become available.

The easiest way out is upgrading to mtcxp-2.2.apk.
[MTCB Software Development] Pampilius86:
[MENTION=6041319]dsa8310[/MENTION] Recenty I installed your rom. I came from a stock 4.4.4 and in comparision your rom is very fluid! I like it!

I have a question: if poweramp is installed, it automatically begins to play last played music after a restart or after ignition off /on.

Is it poweramp issue?

I use the OpenGapps build from 14.10.
[MTCB Software Development] dsa8310:
mtcxp v2.3

mtcxp-2.3.apk

Code optimization, folks... :)
[MTCB Software Development] dsa8310:
Welcome! :)

It's by design. But see post #260.
[MTCB Software Development] GranRamgo:
Does not work bluetooth with Lollipop 5.1.1 someone who knows how to solve them version MCU MTCB-KD-V2.81 OCT 14 2015

It also does not work IGO closes at startup.
[MTCB Software Development] typos1:
Have you tried removing and re-installing iGO ?
[MTCB Software Development] GranRamgo:
If I have tried to install and uninstall, but there is no way it will work when it is shutting down.
[MTCB Software Development] typos1:
Sorry but I dont understand what you mean.
[MTCB Software Development] GranRamgo:
IGO does not work in any way.
[MTCB Software Development] typos1:
Uninstal it, then re-install it.
[MTCB Software Development] GranRamgo:
I have already done that and it does not work.
[MTCB Software Development] Newcomerpx3:
Thanks
[MTCB Software Development] dsa8310:
Thankfully, I have just realized that I had mistakenly changed the target sdk version of the latest mtcxp apps, so after v1.4, all have issues on the HU while working on modern phones/nougat/7.1.2.

But I will fix it asap... or never.

It's a total mystery... For now we are stuck with the current 2.3 version, working well, albeit with an internet access requirement/weakness.

Though I am sure I did not dream when I released v1.2 after a thorough testing while driving around...

What is more puzzling is that on my phone/nougat/7.1.2 all newer (simplified) versions work flawlessly. While on the HU, (under LP), TT GO crashes (when driving).

Yes, it's a nightmare. Something has changed between the release of v1.2, about a week ago, and now, because even this initial, tested, version won't work anymore with the TT GO app downloaded (now) from Google Play Store. And it was not me...
[MTCB Software Development] dsa8310:
mtcxp-3.0.apk -- good for our HU.

mtcxp-3.1.apk -- good for (some) other devices.

Both apps offer same type of spoofing, on-the-fly (read the xposed manifest).

However, only v3.1, which does NOT work on our HU, but on other devices (e.g. my nougat 7.1.2 phone) would be "perennial" in that no internet access is required for the spoofed TT GO app.

Version 3.0 is for our HU. Every other time, when internet is not available, the spoofed TT GO app won't start until connectivity becomes available.

This is an inconvenience, but it could be overcome easily.

However, I am very unhappy with this compromise, what if in the middle of nowhere (a desert!), with no internet access? (try not to close the TT GO app more than once... then don't spoof, and drive another 47 miles, then wait for month's end, ridiculous)

I will include v3.0 in the HU firmware -- done.

===

As a reminder, mtcxp v3.0 does exactly what v2.3 (& 2.2) did, only nicer (version number is displayed, icon is round, spoofing is minimal), see description in post #357.

BTW, it's v3.0 that will work on ANY device - but check firstly v3.1 out, you might get lucky.
[MTCB Software Development] Pampilius86:
Hey [MENTION=6041319]dsa8310[/MENTION], I have question concerning partitioning of the HU

First of all I wiped all I could in the recovery, before installing your rom :)

If I open Total commander, I cannot access the internal memory of the HU, which is now 8Gb instead of previosly having 16GB. (total commander shows even 0Gb)

Apps like Opera use the internal memory for donwloads per default, thus it is tricky to get downloaded files.

Another question is: the rom partition has only 1Gb, which means that after installing a limited amount of apps, the Play Store tells me, I don't have enogh memory. Is it possible to merge the rom partition with the memory of the internal device?
[MTCB Software Development] dsa8310:
I don't think so, you might misinterpret things.

(others would have complained before you, and they did not)

Firmware should be accepted as is. :)

===

BTW, installation of a differently partitioned firmware (mine as compared with what you had before) should be followed - immediately, to avoid wasting time with another system configuration - by a wipe all from recovery.

Once you have "my" recovery - which you had not until first installation of my firmware - then the "install with clear all" option becomes effective in the menu recovery, and could be used as well, doing both installation and a subsequent wipe all.

As stated in the OP! :)
[MTCB Software Development] EagleSoldier:
Here a update.....

Ive installed the open gapps Version.

Both Versions (micro + open) are very fast and stable.

But the open Version is cleaner then the microG.

You dont have the microG apps....

:o
[MTCB Software Development] ankerede:
i had another try with micro g but within internet access and its much quicker loading google maps (offline maps). Ill now try opengapps and compare.
[MTCB Software Development] warata:
I tested it a while ago.My unit is Joying MTCB 1GB device memory.

OpenG ver is very convenient as the PLAY store works.

But it takes more time to boot 5 seconds than microG ver.

Other operating behaviors are also slower than microG ver.

I think openG ver is good if the device has 2GB memory.

Anyway thank you dsa for developing an amazing ROM.
[MTCB Software Development] dsa8310:
Well, both latest versions have (now) a good working Play store. And microG filters out google ads, at least on a few apps of interest to me (e.g. Meye, for DVR control). But not all apps' features are supported by microG, and some apps need disabling certain services to work at all (e.g. Hangouts, its NetworkConnectionCheckingService must be disabled). Also, as I mentioned before, responsiveness is determined by the apps run, in my case TomTom GO has same heavy requirements in both versions.

Let's collect more feedback, especially from 1GB device owners, to draw some statistically significant conclusion, maybe.
[MTCB Software Development] ankerede:
Is there a way get developer options?
[MTCB Software Development] dsa8310:
I still don't know. :)

There is no USB for PC connection. And, don't touch the recovery because the unit may get bricked.
[MTCB Software Development] Johny DJ:
MTCB/MTCC Firmware

I am using micro g for 2 months now and your rom Dsa.

I just deleted all the google staff and replaced with micro G and also disabled some services in micro G and freezed micro G framework and after that the unit became stable each boot...

I am using payed poweramp and google maps 9.25. version, because I think it's the first version which has pop up notification for lollipop whilr using other apps...

Before micro g I tried open gaps to flash with flash fire but was not so fast.

Didn't tried your 2 versions yet but probably open gaps are properly installed and are faster.

I am still using 1gb ram, also bought 2gb ram but didn't upgraded yet...
[MTCB Software Development] dsa8310:
Yes, be careful, find a specialist to do the RAM replacement.
[MTCB Software Development] Johny DJ:
I allready have weller company with pro tools just waiting when they will have time...

I know that you are also using poweramp so one question...

Each time I start the unit and poweramp auto start after 10 seconds it skips the sound for 2 seconds probably because its scanning library..

Do you also have this with 2 gb of ram or not ?
[MTCB Software Development] dsa8310:
Well, yes, there is sometimes a pause in Poweramp play, unexpected, which I can associate with the USB status of my memory stick that holds the song files. I can open File Manager, click the USB tab, which is shown, but contents gets updated only later, the very same moment when Poweramp regains control, too, and restarts playing...

It's different, probably, from your experience. It could also be an USB cable/connector at fault, in my case?!

My USB system is used 100%, for Ethernet adapter, wired router+LTE modem, memory stick, and wireless adapter (this fourth port is taken from the removed internal wireless card, but powered with +5V from the same, added, common USB power source).

I would not care too much for a few seconds of delay, 99.999% of time Poweramp works OK.
[MTCB Software Development] thivamero:
Hello everyone,

To start thanks to DSA for its rom, it is really super.

Before I had the October version, and I wanted to try the December version of this topic, it works great but I have a small problem: in october rom I installed Icoyote and it worked well but on the last rom, The app does not want to install .. Can you help me please

thanks
[MTCB Software Development] dsa8310:
"We" did not change, maybe "they" changed, is it a different version?

The most compatible version is the Open GApps version of the firmware, I think.
[MTCB Software Development] Amelios:
3188 is in the filename... Will they also work on a 3066?
[MTCB Software Development] dsa8310:
No, they will not.
[MTCB Software Development] Amelios:
Any chance something could be put together for the 3066 (800x480)? Thanks either way! :)
[MTCB Software Development] montrelim:
After update with this firmware, I have a wifi problem which cannot connect to any hotspot or router. Also tried with DSA's recommend solution about install_recovery.sh and services.jar but sill have no luck. Is there any recommendation or solution to solve this?

Thanks in adavance.
[MTCB Software Development] Thhhza:
GPS doesn't work on my unit with any of dsa's custom ROMS, any ideas? All the "factory" firmware ROMs work fine though.
[MTCB Software Development] abhi633:
Note sure why is this happening for you, I use the latest rom from microg and it connects ok to WiFi and hotspot, also maps are working real well
[MTCB Software Development] dsa8310:
Publish - here - a link to the latest available - official - rk3066 firmware, and I will see what could be done... You rk3066 owners have been treated most unfairly, so you deserve some help... Same has happened to us as well with the so called MTCD units...

Another possibility is that you would only upgrade your SoM card, from rk3066 to rk3188 (I did it once).
[MTCB Software Development] dsa8310:
Fiddle with the GPS section of your Settings? Enable GPS monitoring? See whether something is wrong in that area.

You may also suppress my automatic, GPS based, brightness control from file /system/etc/install-recovery.sh, comment out this, near end, portion (place a # at start of each line):

#Brightness control (last, always)
if [ $hrs -gt $FREQ ]; then
hrs=0
getntdt
fi
targetb
cb=`cat $BPATH/brightness`
if [ $cb -ne $tb ]; then
if [ $cons -lt $OVER -o -n "$doit" ]; then
if [ -z "$doit" ]; then cons=$((cons+1)); fi
echo $tb >$BPATH/brightness
fi
else
cons=0
fi

Though it works for everybody else but you...

===

Better try getting into recovery where a wipe all may help; then reconfigure the unit from scratch.
[MTCB Software Development] li0rli0r:
when igo is closed , you see any error?

if not , need look on sys.txt file , looks like he doesn't see his folder...