yashsingh1/xdaforums huggingface dataset:
[MTCB Software Development] typos1:
Try wiping data/cache several times. Apart from the space for apps, the partitioning is automatic, thats why theres no separate version of the ROM for 8Gb and 16Gb versions.

What an unhelpful comment, he was only asking for reasons why his unit now shows less memory now.
[MTCB Software Development] Pampilius86:
Thank you, after 3 times of wiping it worked :)
[MTCB Software Development] gravitationalforce:
Dsa boot logo.

Thanks so much for this ROM. Works very well. Any chance you could reupload it without your dsa logo at the boot.

Thanks.
[MTCB Software Development] dsa8310:
Here's another set of apps:

mtcxp-4.0.apk

ttxp-1.0.apk

ttxp-1.1.apk

I have split the pure MTC support from the TT spoofing in two different xposed apps.

Only mtcxp-4.0 is mandatory for the HU, while the two ttxp apps are not (same tt issue, v1.0 works on HU, while v1.1 may work on different devices, too; check them out both).

I will release the firmware with only mtcxp included, in the near future.

It's done.
[MTCB Software Development] dsa8310:
Fat chance!
[MTCB Software Development] typos1:
Charming, as ever.
[MTCB Software Development] Newcomerpx3:
Hi

Dsa rom working perfectly

The only strange issue is in the notification bar says rk3066 instead of 3188 !

What's the reason ...

2nd thing i was trying today to connect usb cam via usb port by using camera fi cam but couldn't make it...

Does usb port recognise web cameras?
[MTCB Software Development] dsa8310:
You may be looking at [MENTION=6114030]Petrows[/MENTION]' Head Unit (aka mtcservice) app which indeed says rk3066 because it also supports those earlier devices.

I don't know about web cams, but isn't there - in the oem? - already installed? - a specialized app?!
[MTCB Software Development] GranRamgo:
¿Does anyone have a blueToothManager.apk that works on Android 5.1 with the BC5M model of the MCU MTCB-KB 2.81?
[MTCB Software Development] Blano:
hallo

tt GO startet aber der map download würd bei 1% gestopt gäret soll mit nezwerk verbunden werden ?

hello

But GO starts but the map download would be 1% stepped up to connect with nezwerk?
[MTCB Software Development] dsa8310:
ttxp v3.2, an xposed module supporting reliable navigation on HU

There are more ways than one to skin a cat... :)

This version is good for all Android/xposed devices, especially the HU, with no internet access issues.

ttxp-2.8.apk -- updated to v3.2 in post #277

It's final, without TT's aggressive upgrade demands.

The only way of using TT GO (on the HU and elsewhere) is to get the official TT GO app from Play Store. Side-loading won't do.

For now I use, on HU, the Device Faker app (first Sony 5.1.1 device for LP, 4.4.4 for KK, respectively), and after installation it could be immediately disabled in the xposed installer module list.

To get TT GO updates from Play Store, one would have to enable Device Faker again (I have just successfully received the latest TT GO upgrade today).

Module mtcxp-4.3 handles now the Play Store availability of TomTom GO on our HU. So use both mtcxp & ttxp on the HU.

With ttxp's help, keep parameter ro.serialno, at the time of first TT GO run, unchanged over time, or else TT will throw some misleading error message and won't permit data (maps, voices) downloading over internet.

Map/voice downloading could be enabled (seamlessly) over non wifi networks by setting the WiFi parameter to true; I use it for wired Ethernet access on my HU (a go between to my LTE modem).

The remaining ttxp parameter is self explanatory. Comes in handy when in middle of the road, with no mileage left, and no internet access to buy a license extension.

And all ttxp parameters could be changed on-the-fly, with no rebooting needed.

===

Improvement, in v2.6, for regular Android devices which have a normal ro.serialno (unlike the HU): the respective parameter, while still being configurable at will, is not reset initially/automatically to a random 12 hexadecimal string, but kept unchanged, as it should.

===

In v2.7, code optimization, folks...

(you care less, no firmware update!)

===

V2.8, rebuilt for KK compatibility, too.

(firmware updated)

===

v3.0 is with full KK compatibility and a better, straightforward spoofing.

(firmware updated)

v3.1 simplifies further the spoofing, by cleaning up some leftovers from previous versions.

(firmware updated)

v3.2 one oversimplification (out of two), undone.

(firmware updated)

===

I will make this xposed module app pre-installed in next firmware releases because support for reliable navigation on all MTCB/C/D units, and any xposed enabled (Android) device for that matter (e.g. my Nougat 7.1.2 phone, even my Marshmallow 6.0.1 TV box!), is now complete.

Done.
[MTCB Software Development] dsa8310:
Follow steps from post #338. Replace mtcxp with ttxp when reading.
[MTCB Software Development] Wipperdog:
Using the rk3188 1024x600 5.1.1 OpenGApps ROM on my unit. It seems like apps don't have GPU access? All apps with hardware accelerated graphics fallback to SW decoding. "Headunit Reloaded" won't even display an image unless SW decoding is turned on in the settings. Google maps operates at like 2-3 FPS. Same situation with the Android Auto APK.

The reason I say there is no GPU access is because I tried enabling the developer setting "Show GPU view updates" and absolutely nothing trigged the display to flash red. Even "Force GPU rendering" did absolutely nothing. My GPU works fine in the factory ROM though.

Also on a potentially related note, the ROM is rendering the system a bit too large. The bottom of my display is clipping slightly by about 5-10 pixels. As in, there should be another 5-10 pixels of information that is simply getting cut off on the bottom.

Here is a link to my unit: https://www.amazon.com/gp/product/B011R51QWM/ref=oh_aui_search_detailpage?ie=UTF8&psc=1

Any advice would be appreciated.
[MTCB Software Development] dsa8310:
Set ro.sf.lcd_density=240 in your /system/build.prop file, using a root explorer/editor (instead of 210), then reboot.

Try also the 4.4.4 image from the peer forum.
[MTCB Software Development] Wipperdog:
Just tried editing lcd_density, it did not appear to change anything. It would be nice if I could stick to 5.1 so that I could use Android Auto with Headunit Reloaded in self mode. Any other ideas?
[MTCB Software Development] dsa8310:
Check out the/my KK firmware for GPU access (simply install with clear all from sd card, the images are identically partitioned).

Why would Android Auto with Headunit Reloaded not work under KK?

Anyway, I was never aware of a GPU issue...
[MTCB Software Development] Wipperdog:
Android Auto's APK has a minimum requirement of Android 5.0. From what I've tried, it won't run on KitKat. I'll try installing your KitKat firmware later today or this Friday then I'll let you know if it has GPU access on my unit.
[MTCB Software Development] dsa8310:
Okay, until then, a suggestion: I use the LP (or KK if performance is of concern) on HU with very few apps, but all working very well while driving: Poweramp for music, TomTom GO for navigation, (True) Contacts & Hangouts for dialing out, Google Voice Search, Gmail, Chrome browser; of course, your mileage may vary.
[MTCB Software Development] Wipperdog:
This is for a car driven by multiple individuals. It's more convenient to have the head unit to just be a central hub that allows access to Android Auto specific to that person. But it still would be nice for all of the functions (google maps, android auto in self-mode) to be available if in a pinch.

Also, if I had to take a guess as to what's happening based on my knowledge, the hardware encoders on these units will only operate at specific resolutions. Seeing how my display is currently over-scaling slightly, it may be that somehow the unit is operating at a resolution that isn't supported, and is using SW methods to operate as a fallback. As it is right now, there is nothing on the system being processed by the GPU (system-ui, launcher, apps).

Here's an image of the over-scaling. The text on the Google Maps UI isn't supposed to be that close to the bottom.
[MTCB Software Development] typos1:
Did you reboot ? It has to be rebooted to work.
[MTCB Software Development] Wipperdog:
Tried soft reboot and hard reboot.
[MTCB Software Development] typos1:
Did you open build.prop with a text editor and save it after you edited it?

Incidently, [MENTION=5228031]Johny DJ[/MENTION]'s microG version of [MENTION=6041319]dsa8310[/MENTION]'s L ROM has forced GPU rendering.
[MTCB Software Development] Wipperdog:
Yeah. I opened it with ES File Explorer's text editor then saved. I confirmed that the setting had sticked. I was originally having an issue where editing it with X-plore would cause the build.prop to revert instantly. But yeah, seems like it worked fine with ES File Explorer, but I don't visually see any change in the system after restarting.
[MTCB Software Development] typos1:
You should see that the launcher has slightly bigger icons. Have you tried un-installing Google Maps updates and re-installing them when it asks ?
[MTCB Software Development] Wipperdog:
I haven't noticed the icons in the launcher increase in size. DSA8310's ROM doesn't come preinstalled with Google Maps, so there wouldn't be any "uninstall updates" option.
[MTCB Software Development] typos1:
Strange - its the first thing I do when I install [MENTION=6041319]dsa8310[/MENTION]'s ROM (dunno why the hell he puts it at 210) and the launcher layout changes slightly after its done.

Unistall maps and re-install and check that the change in build.prop is still there after re-booting.
[MTCB Software Development] pcmender2005:
Try this dpi changer

https://play.google.com/store/apps/details?id=com.chornerman.easydpichanger
[MTCB Software Development] Wipperdog:
I'll use that DPI changer and try reinstalling Google Maps/Headunit Reloaded in a little bit.

Could a lack of GPU access really be related to DPI settings though?
[MTCB Software Development] typos1:
All the app does it alter the build prop same as you did. Have you checked the change has stuck ? Did you read my post explaining that [MENTION=5228031]Johny DJ[/MENTION]'s version of this ROM has forced GPU rendering ?
[MTCB Software Development] dsa8310:
I don't think there is anything wrong with the LP firmware or, in any case, anything I could do about it.

And this is my point of view! :)

(for newcomers, this means that you could interact with & join my ignore list users, or you might get replies from me, but not both in the same time... a rotten apple spoils the barrel)
[MTCB Software Development] typos1:
No one was suggesting there was a fault with your firmware, although if it turns out that there is, your attitude, as ever, is unhelpful.

I think the problem is not with the firmware, but with the "developer". :)

[MENTION=8563473]Wipperdog[/MENTION], bearing in mind [MENTION=6041319]dsa8310[/MENTION]'s response, I would strongly suggest that you use [MENTION=5228031]Johny DJ[/MENTION]'s version - it has all of the benefits, plus some extra ones.
[MTCB Software Development] Wipperdog:
At the very least, I learned that my DPI settings did stick. They were just minimal enough to where I didn't notice. Also the DPI Changer app works. It just doesn't fix any of the issues I'm having with screen overdraw and no GPU acceleration. Will be trying all the other suggestions given in the previous posts.
[MTCB Software Development] rockuman_ex:
Can you provide us with Johnny's link?

The reason why I'm still using this one is because i can't find a better one yet.
[MTCB Software Development] typos1:
Click on the "MTCB Software Development" link above, its only the 6th thread down, very, very easy to find.
[MTCB Software Development] Wipperdog:
Just installed Jonny's 5.1 ROM. Same issue. Interface clipping and no GPU rendering. Going to try DSA8310 4.4 now.
[MTCB Software Development] typos1:
ALL [MENTION=6041319]dsa8310[/MENTION]'s ROMs have DPI set to 210, including [MENTION=5228031]Johny DJ[/MENTION]'s version, but you can set it to 240.

Pretty sure his KK ones do to.

Only [MENTION=5228031]Johny DJ[/MENTION]'s microG ROM has forced GPU rendering, the openG one does not.

I ve used all these ROMs and I ve never not been able to change the DPI back to standard 240, this is very strange.

I have had an issue befpore where factory settings stays at 210DPI so the areas at the top of the screen cant be "touched" via the touchscreen and I ve ahd to use a mouse.

Ypou could try this (it works with MTCB/C units too) :

https://xdaforums.com/android-auto/...ns-development/tool-mtcd-rom-builder-t3475444

and see if you can make some mods to the ROM before you flash it, though I cant remember if you can change the build.prop as well, worth looking at though.
[MTCB Software Development] Wipperdog:
To reiterate, I can change the DPI as much as I want. All of the methods I have used to change the DPI have worked. But changing the DPI does not affect the screen clipping, nor does it enable GPU rendering. I am currently in the process of testing DSA8310's 4.4 ROM for GPU acceleration. Afterwards, I will test Johny's MicroG version, since the version I had tried before was openGApps.

---------- Post added at 11:11 PM ---------- Previous post was at 10:46 PM ----------

Just tried DSA8310's 4.4.4 ROM. Even after enabling the developer setting for flashing on GPU rendering, nothing had shown up. But, Google Maps undoubtably works faster at about 20-30fps, and Headunit Reloaded works without having to use SW decoding. It is possible the developer option for displaying GPU rendering updates is broken on MTCB units. Will post back when I try the 5.1 MicroG from DSA.
[MTCB Software Development] typos1:
Hmm ok, maybe the problem I had in factory settings was not related to DPI, but something else to do with the screen ?

Theres always [MENTION=2127754]booroondook[/MENTION]'s [MENTION=3590033]Malaysk[/MENTION]'s ROMs.
[MTCB Software Development] Wipperdog:
In the past I've tried both. On Malaysk's ROMs, they were absolutely unusably slow. It would start out working fine for the first 5-10 minutes, but then it would gradually get slower until pressing an app icon or swiping across the launcher would be delayed by 5-10 seconds. Eventually the system would completely freeze and reboot. And for Booroondook, I tried his 5.1.1 FUSE ROM and could not get it to boot no matter what I tried. It's 100% possible that YINUO (AUTOTOP) had done some strange hardware customization to their units causing all of these ROMs to not work properly. I could upload the factory update.img file provided by AUTOTOP if someone here wants to delve into it.

Perhaps the issue is that the display that is lower resolution, but reports itself as 1024x600? But, I'm really not sure that something like that could cause system halt. It could be a combination of a whole array of things, you can never know with these Chinese Hui Fei Type units.

I'm currently in the process of flashing Johny's MicroG 5.1 for testing purposes.
[MTCB Software Development] typos1:
What unit do you have ? ie what is your MCU ?
[MTCB Software Development] Wipperdog:
MTCB-KGL.

Also, just finished testing the MicroG version. It had the same issues as all the other 5.1 ROMs.
[MTCB Software Development] typos1:
Right, KGL are the manufacturer of your unit, Yinuo/Autotop are just a seller, they couldnt make any mods to the units even if they tried, they wouldnt know how.

I dont know what to suggest, I ve not heard of this or experienced it before.

You are wiping data/cache after installing each ROM ?
[MTCB Software Development] Wipperdog:
Yes of course. I think for now my current plan is to give up on my hopes and dreams of Android Auto with Headunit Reloaded in self mode, and just go with a 4.4 ROM. Perhaps I'll try this again a year from now using different ROMs.
[MTCB Software Development] dsa8310:
Two "empty" pages is rather a lot about nothing of importance in thread's economy... Reminds me of:

:)
[MTCB Software Development] typos1:
They wouldnt be blank if you didnt have such a long ignore list, if youre not going to offer help, then please stay silent.
[MTCB Software Development] thivamero:
Hello,

I use this rom and I find it great, but I do not like the music player because I do not know how to manage music files (it takes all the sounds present, GPS, voice, etc ...). I use the music player rom malaysk that I find very nice, but I have a problem:

at the first use everything was fine but now the titles are poorly displayed when there are accents

when there is the letter "é" in a title it shows me "ñ", with "ê" it displays "k" .. someone would have a solution to this problem, I emptied the cache, erased the data but the problem persists ??

thank you in advance
[MTCB Software Development] dsa8310:
If you use Poweramp instead, then you will also benefit from the firmware included support (see OP). Background play, and so on. But it is not free, albeit very affordable.
[MTCB Software Development] Oldpapa49:
I guess for some reason, google voice no longer mutes audio of a playing source. It picks up the radio or cd and tries to do with it what it can.

I tried all roms and same thing happens. Maybe my unit has an issue internally or I forgot how it works.. But I guess I head back to trusty ole [MENTION=6041319]dsa8310[/MENTION] 4.4.4 rom which works very nicely.

I tried all 5.1.1's to see and no workee.
[MTCB Software Development] thivamero:
I have poweramp, I uninstalled because what annoys me is that when I quit poweramp by putting the radio, if I restart poweramp it does not start all alone it stays on pause .. is there a solution to this problem?

thank you
[MTCB Software Development] dsa8310:
Well, I use Poweramp which always yields audio focus. Also the mtc direct sound control (HW). But actually, I don't use voice search much... basically only when resetting up the HU after testing before release of newly modified firmware.
[MTCB Software Development] dsa8310:
Check the PA settings out, the Audio Focus, select the bottom menu entry (start by playing, something).
[MTCB Software Development] thivamero:
I have already done, so that PA starts automatically I must press the button "return" before launching the radio .. which is quite painful
[MTCB Software Development] dsa8310:
Nah, PA yields audio focus automatically, while radio doesn't.
[MTCB Software Development] dsa8310:
Gee, I hope my today collected free TT GO mileage will last for another month... ;)
[MTCB Software Development] dsa8310:
Legacy, Folks!

I have included the latest available XposedInstaller app in firmware (v3.1.2), not because is indeed better than the alpha app, but because it displays prominently the xposed framework version that we all use on our LP HU.

I feel that, from time to time, a reminder of one's legacy is appropriate. :)

===

BTW, latest is v3.1.4... I will check things out, to make sure that the newer installers don't break my system.
[MTCB Software Development] dsa8310:
I have updated script install-recovery.sh, mtcxp to v4.1, and included in firmware the latest XposedInstaller app v3.1.4, although the framework is unchanged.

However, there will be visible 1-2 crash messages of the new app during that one time first run, followed by the automatic reboot. So, wait patiently for it, or/and dismiss the messages, it makes no difference, the reboot comes implacably as expected.

Setup is bullet proof, as before, even if the mtcxp and/or XposedInstaller apps are uninstalled brutally/manually.

Only by disabling xposed from the XposedInstaller menu (or attempting an upgrade - don't!) would bring back the black screen - but relax, a wipe all data/cache from recovery will fix it, albeit with a subsequent HU reconfiguration.
[MTCB Software Development] Lwysiwyg:
I'm facing same issues : freezes / lags on startup and long response time when pressing icons / apps. Same with dsa and Johny's ROMs. I was previously on Malaysk's KK ROM (maybe some of his customizations make something goes wrong with LP ROMs, like FUSE system).

My HU is from Joying ; no issue with KK ROMs. Always clean installs, full wipe.

About 200mb free RAM. Lags / freezes seem to be stronger when Waze is starting / running.

I forced minimum CPU frequency to 1200MHz using Kernel Auditor but same issue.

Any idea dsa8310 ? I don't think it's related to your excellent work. I will probably switch to a new HU soon (PX5 inside :))
[MTCB Software Development] dsa8310:
Final LP Firmware

The LP firmware has been updated with a conceptually new & greatly simplified mtcxp/XposedInstaller automatic installation method - previously, it was an ugly hack, trust me.

As usually, just wait for the onetime (unavoidable) initial reboot which deals with the KLD black screen issue.

This is the must-have, definitive version - released on November 4th.

We are done! :cool: ... :( ... :)
[MTCB Software Development] Lwysiwyg:
Just to let you know : I reverted back to latest Malaysk's KK ROM. Everything is now working great : no more freezes / lags.

Some RK3188 HU seem to be underpowered for LP ROMs (dsa8310 and Johny's). Dunno why.

Mine is a Joying HU (JY-UQ130), 1 GB RAM, latest MCU, and lagging / freezing very very often. I must wait about 5 minutes to gain full access, but when I start a new app, I face new freezes / lags.

Maybe it could be useful to have more feedback about this.
[MTCB Software Development] Oldpapa49:
Yes, LP on our MTCB's is not good at all. Stay with LL. [MENTION=6041319]dsa8310[/MENTION] has a very good ROM to use on straight KK's. No fuss Rom.

I have explored all ROM's and for a ROM with little bloatware, he has it.

You can add and change to what ever you like.

But as far as LP goes, not so good.

Even the MTCD's which are LP's have some type of issue.
[MTCB Software Development] typos1:
Not quite right - [MENTION=5228031]Johny DJ[/MENTION]'s microG version of [MENTION=6041319]dsa8310[/MENTION]'s L ROM is nice and speedy - 470mb of RAM is free, more even than KK. :)
[MTCB Software Development] pcmender2005:
??

[youtube]JmvCpR45LKA[/youtube]
[MTCB Software Development] dsa8310:
Final - just joking :) mtcxp v4.2

I have released the final mtcxp/xposed app:

mtcxp-4.2.apk -- updated in post #265

It's, hopefully, my farewell gift to all TomTom GO users.

Now, the official play store TT GO navigation app becomes directly downloadable on our HU, and updates are seamless (as they should be).

Together with ttxp/xposed, and the storage support from script install-recovery.sh, these modules make TT GO use (on any xposed enabled device) a great experience.

===

All firmware, LP & KK, has been updated accordingly.
[MTCB Software Development] dsa8310:
A word to the wise: under both LP&KK, the two xposed modules, mtcxp&ttxp should be updated by hand; merely updating the firmware (without wipe all, of course) won't upgrade mtcxp (and neither ttxp) albeit included.

Under KK, the apps are in the /system/preinstall folder, while under LP in /system/xp (mtcxp) and the oem partition (ttxp).
[MTCB Software Development] Newcomerpx3:
Is this mtcxp&ttxp only for TT go navigation app?

Cause i dont use TT ....should i uninstall mtcxp?

I use waze app !?
[MTCB Software Development] dsa8310:
No, keep it! Under LP, it's reinstalled anyway automatically by script install-recovery.sh because without it we get the Klyde black screen error.

I put the non configurable parameters in mtcxp, they benefit to all apps, not only TT GO (e.g. config_voice_capable, to make phone icons clickable, in Contacts); read the xposed manifest.

In ttxp there are the configurable params, almost exclusively for TT GO (with the exception of ro.serialno which could be used by other apps as well).

===

Waze, huh?! Traitor! :) BTW, does waze have 3D buildings on maps?
[MTCB Software Development] Newcomerpx3:
There is no other option for me as navigation app cause in our region the only nav app which shows online traffic with navigation is waze ? and the sad part is government has filtered it , we have to use vpns in order to use it .... wazers over here keep reporting hidden traffic police cams and police checks, online traffic issues [MENTION=6041319]dsa8310[/MENTION] ??