MTCB/MTCC rk3188 (4.4.4) Firmware

[Oldpapa49]

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!

I need to install that soon. I'm not having any issues. But I'm just a basic person

 

[franco1888]

I don't think that this is the thread for your HU.

wait, see this thread: https://forum.xda-developers.com/an...-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.

I appreciate the help I will try that when I get home from work again thanks

 

[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)

 

[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.

 

[dsa8310]

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.

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).

 

[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+?

 

[dsa8310]

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+?

What about direct (but side? com.google.android.projection.gearhead.apk) installation on the HU?

 

[joop1987]

What about direct (but side? com.google.android.projection.gearhead.apk) installation on the HU?

I get a "There was a problem parsing the package" when I try to install it.

 

[MurphyNr.1]

Can i use it with an Rk3066 Device ? or Impossible ?

 

[dsa8310]

Can i use it with an Rk3066 Device ? or Impossible ?

Don't use it.

 

[KaMu1219]

I get a "There was a problem parsing the package" when I try to install it.

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://forum.xda-developers.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

 

[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.

 

[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 @Thhhza's feedback, the matter is now solved/closed.

 

[Johny DJ]

@dsa8310 on 4pda you also became popular...

 

[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.

 

[m00n61]

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.

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.

 

[elyl]

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.

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.

 

[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).

 

[dsa8310]

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.

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!

 

[m00n61]

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.

Use Device Faker in Xposed and you will be able to download from the PlayStore. I had the same issue on my MTCC unit.