yashsingh1/xdaforums huggingface dataset:
[MTCB Software Development] dsa8310:
I don't think that this is the thread for your HU.

wait, see this thread: https://xdaforums.com/android-auto/...-general/seicane-unit-screen-problem-t3411722

if you recognize it, then this thread is also good for you.

===

Probably thread is good.

Try to get into the recovery program: press the reset (RES) button through the hole in the upper right corner, press Volume, release RES, release Volume, unit will beep three times, and it will go into recovery.

Upload a photo of the recovery screen, show it to us, if we recognize it, then you could use the firmware in the first post of this thread.
[MTCB Software Development] thivamero:
for developer mode

HERE
[MTCB Software Development] Oldpapa49:
[MENTION=6041319]dsa8310[/MENTION],

You are becoming famous for this ROM on 4fpa.. mentions of your ROM.. Near last posts..

Good job dsa8310! I know you where world wide famous before.. But now!
[MTCB Software Development] dsa8310:
Nah, this KK is not that good. For instance, app switching is hesitant as compared to LP, e.g. poweramp gets silenced briefly during a screen change between two apps (perhaps it needs express priority configuration, available).

I keep it because it spares me the manual switching between wired(+LTE modem) and wifi networking when I get home. KK knows it better, while LP needs guidance...

...and because the (kernel) KK logo cannot be replaced by the car logo, so for now I get pleasantly surprised by my own logo instead! :)
[MTCB Software Development] Oldpapa49:
I need to install that soon. I'm not having any issues. But I'm just a basic person
[MTCB Software Development] franco1888:
I appreciate the help I will try that when I get home from work again thanks
[MTCB Software Development] thivamero:
I do not know why but This afternoon I start my car radio and it has recovered in factory configuration. Strange, I noticed that after one week of use, it takes more and more time to start . Before it was 20s and after (before it reinitialized) it put 30s which is far from being effective..I will wait a week see if I have the same symptoms

Of origin my HU is in 5.1.1 may be that it plays on the problem

it's sure, icoyote don't work with this version, it's working with 5.1.1 (But version 5.1 with opengapps slows down too much (too much memory used)
[MTCB Software Development] gabesir:
wiped , installed this firmware and seems fine , enabled xposed rebooted, enabled all the modules but when i go to download to look for more stuff is blank also the play store is not finding any updates.
[MTCB Software Development] dsa8310:
Wipe again. The idea is to wipe after installing the new, differently partitioned firmware (ideally just before the first start-up, to avoid wasting time with another wipe).
[MTCB Software Development] joop1987:
Is there any way to install Android Auto on this? I can't find any info on installing the server on the radio. Or does it require Android 5.0+?
[MTCB Software Development] dsa8310:
What about direct (but side? com.google.android.projection.gearhead.apk) installation on the HU?
[MTCB Software Development] joop1987:
I get a "There was a problem parsing the package" when I try to install it.
[MTCB Software Development] MurphyNr.1:
Can i use it with an Rk3066 Device ? or Impossible ?
[MTCB Software Development] dsa8310:
Don't use it.
[MTCB Software Development] KaMu1219:
For running "Android Auto" directly on the HU in the so called standalone mode you need at least Android 5.1 running on the HU.

For connecting your phone to the HU you have to have a different setup:

Phone:

- Install "Android Auto"

- activate "developer mode" in Android Auto

- start head unit server in Android Auto

- activate ADB mode / USB debugging on phone

all according to this video

https://www.youtube.com/watch?v=U_hTM-MRLiw

HU:

- Install "HeadUnit Reloaded"

see https://xdaforums.com/general/paid-software/android-4-1-headunit-reloaded-android-t3432348

Only works reliably when running 4.4.4 on HU, not with 5.1
[MTCB Software Development] dsa8310:
Upgrade of script /system/etc/install-recovery.sh:

install-recovery.sh

A must. It fixes the location algorithm used in automatic brightness control, by extending it, with all NMEA syntax cases.

For convenience, firmware is also updated in the OP.

DO NOT UPGRADE YET! Go ahead, upgrade now.
[MTCB Software Development] dsa8310:
Sorry for the rush, now all versions of script&firmware (LP/5.1, KK/4.4) are updated with the upgraded GPS location algorithm, used for automatic brightness control.

Essentially I look for the $G[NP]GGA and $G[NP]RMC NMEA strings, while before only string $GPGGA was considered.

Thanks to [MENTION=8398242]Thhhza[/MENTION]'s feedback, the matter is now solved/closed.
[MTCB Software Development] Johny DJ:
[MENTION=6041319]dsa8310[/MENTION] on 4pda you also became popular... :)
[MTCB Software Development] elyl:
Has anyone else had issues running TomTom on this ROM? I can't seem to get it to work, even with MTC Service activated. DSA doesn't seem to have any problems, but I am, even after a factory reset. It loads, but sticks on the "can't connect" screen, even when I have a good wifi connection.
[MTCB Software Development] m00n61:
With the latest TomTom version this usually happens if you use a sideloaded APK. Or if you changed the Android serial number - see the OP's comments on the matter in this thread.
[MTCB Software Development] elyl:
Yeah, haven't changed the serial number (just whatever is default in MTC Service). And I can only sideload the APK because the Play store reports that the app is not compatible with my system, so I need to download the Play store APK and install it that way.
[MTCB Software Development] dsa8310:
Bug fix of... Android KK 4.4.4, in the new:

mtcservice-2.41.apk

related to scrolling vertically in the preference settings - switches got reset, no more, thanks to a workaround found on the internet (class SwitchPreference is dummy derived).

(fortunately, the bug was fixed under LP, or so it's claimed, so I did not update mtcservice-2.38.apk - and I can't recall the scrolling issue, but let me know if it's there still)

For convenience, the firmware in the OP was updated as well, although a mere mtcservice upgrade suffices (from 2.40 to 2.41, under KK only).
[MTCB Software Development] dsa8310:
As I told you via PM, there is no issue, at least with the "free" miles TT GO apk, floating around the internet...

In general, letting mtcservice+xposed set a "good" ro.serialno parameter, and having the play store configured (which happens automatically during the onetime setup of Open GApps), are key to TT GO internet access validation. Parameter ro.serialno must NOT be changed subsequently, otherwise map/voice updates become impossible. In such case either parameter ro.serialno is restored (in mtcservice/preference settings, last item at bottom, followed by reboot!), or TT GO should be uninstalled and reinstalled again with whatever (different) value of ro.serialno in effect.

Note that after the very first restart of the HU (or after a wipe all in recovery), after the onetime Open GApps setup, after mtcservice-2.41 is preinstalled, after the xposed framework is installed (by user), and after module mtcservice is enabled, one reboot is necessary so that the newly minted ro.serialno gets active. Message "serial number not set (yet)!" in the xposed log (accessible from the Xposed Installer app) denotes a missing ro.serialno. So, reboot first, in such case, so that ro.serialno becomes active, and useful for TT GO.

===

Perhaps I should place a message window on screen when parameter ro.serialno is changed, reminding user to reboot (after also enabling the xposed module), so that modification becomes active... Offering to also reboot is above my pay grade, of course! :)
[MTCB Software Development] m00n61:
Use Device Faker in Xposed and you will be able to download from the PlayStore. I had the same issue on my MTCC unit.
[MTCB Software Development] elyl:
Yeah, this was the key. Not sure why I had to do this, and others on the ROM didn't. Oh well, working now!
[MTCB Software Development] dsa8310:
Another mtcservice update, to:

mtcservice-2.42.apk

This version will warn to reboot ASAP, via a toast message, about either an initially generated ro.serialno parameter, or a subsequent change of it (in preferences), whenever the service is (re)started (this happens at activity start as well, if enabled) or its activity gets paused (hidden).

No change of ro.serialno, no toast at all, as before.

I will upgrade the LP version of mtcservice, too, with this feature.

===

I have just double checked that a different ro.serialno than that set at TT GO first run will prevent internet access for downloading map/voice updates. So, parameter ro.serialno matters, after all, thankfully.

However, another condition that I have overlooked is, apparently, to be registered as a TT GO installer in the Play Store.

Since I have been using TT GO for a long time, I have most certainly at least once complied with this requirement... while using LP or/and an earlier version of TT GO, perhaps.

I will look at the Device Faker xposed module, maybe there is something to be ported into mtcservice as well.

===

For convenience, firmware in the OP has been updated, too, albeit a simple update of mtcservice will do.
[MTCB Software Development] StSt123:
3G USB-Stick reconnect

Hi,

first, thank you for this incredible fast rom! :)

Unfortunately, I noticed a small problem:

If the 3G USB-Modem is connected and i switch off the unit by ignition for a short while (for example at a Gas Station),

Mobile Data will not be reconnect. Same happens if i use the powerkey of the unit to switch it off.

The only way to reestablish the connection is resetting the device by long pressing the power button.

Wifi isn't enabled and should not be cause.

Does anyone have a solution for this?

Thanks!
[MTCB Software Development] Thhhza:
I have to say this is the fastest ROM I have tried and has finally made my unit actually usable. Apps can be used immediately after starting the unit and switching between apps is really fast too. Can't believe it was the M ROM that was the problem all along, what a resource hog!

Question, what is the difference between the mtc-service that comes with the ROM and the app made by petrow that is available from the app store? The one that comes with the ROM doesn't support media keys with Spotify whereas the one on the app store does.
[MTCB Software Development] dsa8310:
In short, no.

My solution is described somewhere in the original firmware thread... in post #253.

It uses an intermediary (small) router that understands even LTE modems, solving all issues. The Ethernet USB adapter is not mandatory since router can act as an wifi access point, too.
[MTCB Software Development] dsa8310:
Good question, [MENTION=6114030]Petrows[/MENTION] app is available in source, so I will see what was lost in my transition...

Wow, he went further away with his original development, which explains the extended support. I will try to (re)merge the code.

===

Since we run under KK, with no dark display issues (that required my xposed intervention), I will check out his app, to make sure that it acts as a dialer; if not, I will add minimal support in the manifest; if OK, I will leave it alone and make the (bigger) LP xposed module and (small) KK xposed module a separate app, respectively (or one app maybe).

On the other hand, piggybacking on his app seems easier to me...

===

Another approach, for KK only, is to find other xposed modules that handle ro.serialno and the other parameter left, config_voice_capable, to be set to true, and use his original app - if it acts as a dialer correctly.

For LP, the extra spoofing of the MCU name, combined with install-recovery.sh support are mandatory.

===

I checked it out: it needs merging some code I had added: an AndroidManifest adjustment to make it a dialer (easy); the menu item that would start True Contacts is unnecessary, but does not hurt either; a change to avoid two icons in the top bar when powering off and on (before complete power off); the miles/kilometers per hour gimmick, maybe; menu for starting other/player apps on boot is nice, but probably ineffective because when mtcservice/headunit is early started from script install-recovery.sh, other apps won't start quickly without retries (I will see source, add them if not there).

Otherwise it is a remarkable improvement!
[MTCB Software Development] dsa8310:
For KK and LP - if the new LP firmware is installed:

mtcservice-2.60.apk

It's [MENTION=6114030]Petrows[/MENTION]' latest, plus: dialer for the HU, "clean" one icon at a time in the status bar (even after power off/on), and the miles per hour alternative to kilometers per hour gimmick.

I also assume all supported players are now properly handled (Spotify included).

People having the mtcsound (hardware including) setup, can use the "Alt..." choice in the MTC Sound's settings screen in order to have radio playing in the background (of the navigation app), under KK, although I don't recall about such issue under LP.

The app is not tainted with any xposed module. I plan on making a separate common xposed module/app, for use under both KK and especially LP. Then this mtcservice app will also be good for both LP and KK, as its author had planned.
[MTCB Software Development] Johny DJ:
Does anybody know why on kitkat and latest mcu kld 9 or 6 which can store stations after a (hard) reset the stations are not there anymore.

It worked under lollipop but on kitkat not.

Is this maybe mcu - kernel related if anyone know or noticed ?
[MTCB Software Development] thivamero:
Hello ,

How to make the car radio not turn off when I start the engine of my car (it restarts immediately after) ??
[MTCB Software Development] Oldpapa49:
If I recall, they remove power so not to lower voltage to accessories that might damage electronics.

Lets say, while starting, instead of having the radio on and when you start, the voltage drops to 10.5 volts while cranking, then back up to 12v when in run.

This will be like a brown out and can be unsettling to the electronics.

It also allows to have that extra power that might be needed for starting. The Starter can do some back EMF
[MTCB Software Development] thivamero:
snifff, on my old wince car radio, it does not cut when the engine started
[MTCB Software Development] Oldpapa49:
depends on the car wiring as well.. i need to check my cars 2015 challenger and the 2005 ford freestyle and see how they compare
[MTCB Software Development] dsa8310:
Good news, the separate xposed module app is ready an working as expected. I am still chiseling the corners of its icon... :) Choosing its name.

I will release it for KK immediate use, ASAP, while the LP firmware, although it will use the very same module/app, it also needs extra changes to have it taken into account.
[MTCB Software Development] dsa8310:
The separate xposed module:

mtcxp-1.0.apk

It's readily good for KK.

LP needs an extra setup that will be accompanied by a new firmware release, by tomorrow, hopefully.

Done.

It's a basic preference app & module that after an eventual reconfiguration (followed by reboot), one can safely forget about.

Firmware has been updated in the OP, although installing mtcservice-2.60.apk & mtcxp-1.0.apk is enough.

===

I remind that all visible, disabled and even not listed at all parameters in this app, they were all "xposed" in the older versions of mtcservice.

Parameter ro.serialno, editable, is important for apps like TT GO.

While the inaccessible, but nonetheless present parameter sta_mcu_version handles under LP 5.1 the Klyde's "dark" display issue, their botched attempt at selling MTCC devices as incompatible with our MTCB ones.

The third, disabled parameter under KK, but configurable under LP, TYPE_WIFI returned by all calls to NetworkInfo.getType(), when set, will let apps like, again TT GO, to use wired and other kinds of networking, beside wifi, for downloading map/voice updates.

Less significant is parameter config_voice_capable, could have either value, good, I think, for configuring other dialers, when true.
[MTCB Software Development] dsa8310:
I have released the new LP firmware, so from now on, both KK and LP could use the same pair of apps, mtcservice-2.60 & mtcxp-1.0.

From testing it, I can tell that indeed LP can switch between apps better than KK...

(yes, I am under LP right now :) )
[MTCB Software Development] Johny DJ:
Wooow nice, so I suppose if I have kitkat all configured I can just install mtcservice-2.60.apk & mtcxp-1.0.apk or I have to flash whole firmware again?

I read about five times but cannot fully understand what new xposed module does :) Probably extra permissions for TT GO working correctly...

P.s. just for info: for poweramp there is updated xposed module that handles poweramp media keys and also can bus items displayed like ordinary MTCmusic app. And also when opening mtc app poweramp stops itself and also conflict while using meda keys when radio is opened is solved that poweramp doesn´t skip songs etc. in background.
[MTCB Software Development] dsa8310:
KK people should only upgrade mtcservice to v2.60, and install mtcxp.

LP users should firstly update mtcservice to v2.60, then

immediately, without another reboot

should update, from recovery, the respective firmware fully without "clear all" or "wipe all", preserving so their configurations -- if they update my previous version of firmware, otherwise they should install the new LP firmware and then "wipe all".

Under KK & LP, mtcxp spoofs/configures two parameters, notably ro.serialno, for TT GO use mainly.

Under LP, it also spoofs/configures a third one, to TYPE_WIFI, letting again TT GO to access the internet via other types of network than wifi (e.g. wired). But the main spoofing, under LP only, is of an invisible parameter, namely sta_mcu_version, without which the dark display issue would happen.

Under both KK and LP, mtcservice-2.60 is the recommended app for handling media keys, including Spotify, and Radio. It also is the main dialing app, via BT, HU wide. It also controls sound volume with car speed variation. Everything is done elegantly without xposed.
[MTCB Software Development] thivamero:
I do not know why, but after 2 weeks, the unit starts after 34 seconds ... it's very slow ... (I've done this twice). I prefer Lp but with open gapps and 1gb ram, it's not fast, and with micro gapps I can not record poweramp
[MTCB Software Development] Oldpapa49:
The Challenger Shuts the radio off during start.. Maybe I get to the SUV tomorrow.
[MTCB Software Development] thivamero:
I think that the HU was not thought to maintain a feeding the time of the start up contrary to other unit
[MTCB Software Development] Johny DJ:
Thats because of open gaps. Dsa8310 said that it´s on your choice which to choose. 1gb ram and LP you have to go with Micro G. Poweramp is working, just update playstore to the latest or disable auto update of playstore and poweramp activate by itself, a bit slow but it does if that was your main question, because I don´t understand what you ment with ´record poweramp´...
[MTCB Software Development] dsa8310:
Boot time depends on how much stuff has been installed on HU. It seems very brief after the first startup. The microG version (LP), before any configuration, boots very quickly indeed.

But once configured, with apps, Google stuff, the HU boot time is normally around 30 seconds. It's processor's speed...

Let's say, enough time to warm up the engine.

Fortunately, for brief stops, say under 30 minutes (my case), there is the Extra Settings menu entry (in Settings), that delays the shutdown for a chosen, short, time, and so power on is then instantaneous.
[MTCB Software Development] thivamero:
sorry, not "record poweramp", but "activate poweramp".... The last time I tried with micro gapps (version of July 23), poweramp reported "license check failure"...
[MTCB Software Development] Johny DJ:
Then try the folowing... open google play and then open poweramp (it has to activate pending automaticly) if not just restart this proces few times or restart the unit and try again.

It should activate if you try 2 or 3 times like this and after this you have about 2 months before it want licence check again :)
[MTCB Software Development] thivamero:
ok thanks, i try it today

It's not working with micro gapps
[MTCB Software Development] dsa8310:
Would it be useful to make a MicroG enabled KK 4.4.4 version as well?

My development of firmware for MTCB & MTCC units is pretty much done, that would be a last touch.
[MTCB Software Development] dsa8310:
The MicroG enabled KK firmware for MTCB/MTCC, rk3188 units has been released in the OP of this thread.

Same required setup as described in the LP thread. Let update Google Play Store. But also install the Xposed framework yourselves (as for the KK Open GApps version).

For now I stick to the LP (Open GApps) version, so I have not checked it out yet, but testing has been performed by [MENTION=7432048]warata[/MENTION], and [MENTION=5228031]Johny DJ[/MENTION] - who indicated the correct gms version for KK.
[MTCB Software Development] thivamero:
thanks it's ok , now i 'm with lp (mico gapps)
[MTCB Software Development] Johny DJ:
On LP I had to install xposed fake gaps apk to get micro G working as desribed in micro G thread...

Is that also required here or is it done also with your xposed module?
[MTCB Software Development] dsa8310:
Yes, I believe that with MicroG, LP is better than KK.

Anyway, now all combinations are available for comparison.

If I get another confirmation that MicroG KK is working, I will move it to the OP.
[MTCB Software Development] dsa8310:
Same setup as under LP, just the xposed framework is to be installed manually (as it's done for all my KK versions) from within the Xposed Installer app, preinstalled.

My mtcxp xposed module should be enabled under either KK or LP (where its presence & setup are anyway enforced - in script /etc/install-recovery.sh - otherwise the black screen would happen), though it has not much of a role under KK, except for parameter ro.serialno (enforced to a random 12 hexadecimal/char value, or a user set one, in both LP and KK).

BTW, I recommend all available mtcxp checkbox params to checked/true.
[MTCB Software Development] thivamero:
Your new LP version works as well as the KK for the moment

thank you for your work
[MTCB Software Development] dsa8310:
Yes, I always thought that there is not much of a difference between LP and KK, with Open GApps, and even much less with MicroG (both).

The only combination I did not check out myself is KK with MicroG, freshly released today. If I get enough confirmations that it works well, I will move it to the OP, next to the existing KK with Open GApps.

I can tell that LP is better than KK because it switches between apps without any hiccups, while I would enjoy more KK because it handles better jockeying between wired and wifi networking - but few use else than wifi.

For both LP and KK I have the proper TomTom GO solution for downloading stuff not only via wifi: for LP it's the TYPE_WIFI parameter in mtcxp, while for KK it's a patched TT GO app that thinks that all networks are of type wifi (same effect as the LP param, which is for all apps).

And for now I am back at LP with Open GApps... But my work seems done. :)
[MTCB Software Development] thivamero:
Is it possible to create something to not turn off the device when the engine starts ?? (ex: standby 5s after shutdown)
[MTCB Software Development] dsa8310:
Sure, there is a software/xposed solution, and a hardware one: good battery, and using two items: a (silicon, Schottky) diode between the (+12V) red accessory wire and the accessory entry to the HU, and a capacitor between the same entry and ground, of value between 100 to 1000 micro Farads (working at negative temperatures during winter), to be determined by testing.

However, with a bad battery and a long cranking starter, there is nothing to be done against a drop of voltage on the permanent yellow +12V wire... which will shut HU down, with or without xposed or diode+capacitor on the red wire.