yashsingh1/xdaforums huggingface dataset:
[MTCB Software Development] Oldpapa49:
You thought I meant that you install.. Nope..

It is not the same as ours, I understand.

But for dsa8310 to look into the structure and see what apps, libs and all and check to see what is the same if any and what might be an improvement.

It is not an update.img at all..

At work, got the file, will look into the apps and all. See what I can see. No one here yet so I can play a bit..

Since it is software, they might think I'm doing something.
[MTCB Software Development] typos1:
Dont think that would help anymore than looking at any other 6.0 device would. :)
[MTCB Software Development] m00n61:
It's the app in Play Store. It really makes a difference. I still have to stay away from the Google app, that is way too heavy on my unit.
[MTCB Software Development] plastik46:
Are you referring to gmaps that's my biggest issue
[MTCB Software Development] m00n61:
Nope. That works very well, I am using it with Automate. I was talking about Google Now.
[MTCB Software Development] plastik46:
ok thanks for the info, will give it a try.
[MTCB Software Development] Oldpapa49:
Something might be on the horizon on 6.0.. Voice commands to command the radio.

I see commands like "change to AM", Play Music.. etc..

Copy Paste:

<SendBroadcast command="AM" keyword="change_band_to_am" action="com.nwd.action.ACTION_KEY_VALUE" extra="extra_key_value" type="byte" value="73"/>

<SendBroadcast command="FM" keyword="change_band_to_fm" action="com.nwd.action.ACTION_KEY_VALUE" extra="extra_key_value" type="byte" value="72"/>

The file is called : VoiceCommand.xml

And who is this? ro.product.nwd.customer=K2001_NWD_GB

Looks like if you are on AM and activate it, and say "FM" it looks to change.. here is the line from what ever to FM:

<SendBroadcast command="FM" keyword="change_band_to_fm" action="com.nwd.action.ACTION_KEY_VALUE" extra="extra_key_value" type="byte" value="72"/>

I think the "change_band_to_fm" is the reply and you can see the action and values..
[MTCB Software Development] typos1:
14 more of us will have 2GB RAM soon . . .
[MTCB Software Development] pekass:
Hi you recommend me to update to the October verdict, I have installed the August 02 2016 MTCC-KLD6-v2.97 1024 * 600, if it is if you please tell me how to update it, or there is some video how to update it, it did not break ?
[MTCB Software Development] Oldpapa49:
1. Make sure you recorded all the settings of your unit including the Factory Settings.

2. Make sure you know how to get into recovery.

3. Format a MicroSD card or USB flash drive (if your unit has access to ) to windows Fat32.

4. Copy the image (dsa8310's latest which also should match your unit resolution) to the USB or MicroSD card (update.img)

5. Insert the MicroSD or USB drive into the unit.

6. Start the unit and enter into recovery (My unit is RESET button and POWER BUTTON held together, the release the RESET and 5 sec later the POWER BUTTON.

7. If MicroSD, select the one with "update system/mcu image from sdcard and clear all or if USB flash, the one that has usb instead of sdcard (3rd or 5th down from the top)

8. Select that option and let it run.

When the unit reboots, go back into recovery and select "wipe all data/factory and cache reset". This helps to setup the locations in the unit.

9. It will return back to recovery and the select 'reboot system now'

It will then restart loading again (your logo might be different, no sweat it). It will start as new, do the slide of new android displays. And it will start a reboot. Wait.. It is fixing stuff and when it finishes, do you think.

If you don't have Titainium Backup, I suggest to get it. Easier to recover apps. Make sure select a folder outside of any internal folder like the USB or if you have a GPS sdcard, let it save there.
[MTCB Software Development] Oldpapa49:
I thought one of your roms was 2G vs 3G or something like that.. Getting forgetful..
[MTCB Software Development] psxsnake:
I'm. Happy with last October... Changed launcher and installed TT... Perfect and speedy

Only one thing I miss... Apn edit or a way to disable GSM card...

psxsnake
[MTCB Software Development] miffymiffy:
so, with fuse, do I have a 2gb or 3gb partition?

I swear I did it as meant to and I think its only 2gb. Can someone post a screen to show what storage looks like?
[MTCB Software Development] mouscolo:
noob question ....may u help me how to install ur rom plz, it come with 2 files
[MTCB Software Development] CARRisma:
Google Maps is laggy with me too.
[MTCB Software Development] m00n61:
Waze problem solved by changing DPI.
[MTCB Software Development] typos1:
dsa's ROM is not FUSE and it has a 3GB data partition, if it was FUSE the partition would be something like 11 or 12GB.
[MTCB Software Development] vch88:
Could you give more details about how to change DPI for Waze?

Thx
[MTCB Software Development] m00n61:
Use Easy DPI changer from playstore.
[MTCB Software Development] tariqkhan.co.uk:
Or you can use AppSettings module for Xposed
[MTCB Software Development] vch88:
Which value i have to set up?

Thanks again
[MTCB Software Development] m00n61:
I tried both 180 and 210. I guess 240 could work too.
[MTCB Software Development] Oldpapa49:
Just make sure in root explorer you can see the complete settings.. That how I tested it.
[MTCB Software Development] mouscolo:
what about google maps issue? its fixed yet?

I tried Malay and booroondook, all are really laggy when I open google maps, I installed booroondook rom 3 days back to check after google maps update to give it a try, but the problem syill exist, how about DSA rom anyone can confirm :) ?
[MTCB Software Development] psxsnake:
Doesn't work, al settings cannot be edit

psxsnake
[MTCB Software Development] psxsnake:
wait ... i start to have problem with connection only with last eonon rom, before never had problem with my 4g key.... so is the rom the problem?
[MTCB Software Development] pa.ko:
I just checked

https://www.sven.de/dpi/

For 6.8" 800x480 it is 137 PPI...
[MTCB Software Development] Oldpapa49:
Change dpi to 230. Be hard to see at 137 I think
[MTCB Software Development] koenvbeek:
Interesting. I also managed to get Waze to work, by following this steps:

- Uninstall the app

- Delete the waze folder from internal sdcard.

- Install Waze 4.8.0.2 from apkmirror.com

- Start it up and login to your account

- Update to the latest version via the Play Store.

Very nice to be able to use my favorite navigation app again :cool: :good:
[MTCB Software Development] pa.ko:
Yes I know. But true dpi is 140. If it is not suitable (yes we all know it is not) then it means these ROMs and apps (stock ones) are made wrongly. And it will be issues. Stock apps require us to select higher than true DPI. Then modern apps which are build correctly to respect DPI (to show true physical size of UI elements on the screen) will be missaligned. For instance, Torque main screen in latest version is using self-adjusting sizing respecting DPI and now it is overstretched if you set dpi higher than 140 which is physically correct.

So I'm just pointing out that stock UI is poorly designed, yes it requires artificial DPI (on 800x480 for sure) to look 'normal'. Yet some new apps will then be missaligned.

So I guess it will require Xposed module to fine tune doing for particular apps, while keeping global doing higher than physical.
[MTCB Software Development] Oldpapa49:
There is an app that you can adj apps dpi too. On play..
[MTCB Software Development] typos1:
Not necessarily - [MENTION=6041319]dsa8310[/MENTION] changes the kernel to make the latest ROMs which we ve only got in 1024x600 format work on 600x480 with the correct resolution, which may explain the behaviour youre talking about I never noticed anything look weird or misaligned on my 800x480 units before August, or maybe you have a faulty screen ?

[MENTION=6041319]dsa8310[/MENTION] has suggested numerous times that 800x480 is not supported anymore, but 800x480 (all 6.2" units are 800x480) units are still being sold, I think its more a case of us not having got hold of any later 800x480 ROMs.
[MTCB Software Development] mouscolo:
i just done testing DSA rom, its the best 5.1 I used, no google maps issues, and not lagy at all, the only problem am facing that everything is huge I believe its something to do with resolution or DPI?

[MENTION=6041319]dsa8310[/MENTION]
[MTCB Software Development] Oldpapa49:
Get Le DPI Changer from Google play and set it to around 230. My unit is 800x480
[MTCB Software Development] mouscolo:
that fix it? :D
[MTCB Software Development] shanetrainST:
Just asked Eonon if they know anything about the New Octocore version that Klyde is offering, looks they will be looking into it.

To quote them exact.

We do not get news about that we will release new version of headunit now.

I have asked them to look into the compatibility for MTCB/C units for this new SOM.

And before anyone jumps in, YES I am aware that Eonon are JUST a Reseller
[MTCB Software Development] tariqkhan.co.uk:
I used to do the above and set the dpi to 180. I then used Xposed AppSettings to set all MTC apps to 180 as they do not look good with the higher dpi.

I now want the bigger look, so leave build.prop at 240 and using Xposed AppSettings, I set certain apps to 180 dpi so I see more (e.g. Sygic, Google Maps, ES Explorer, etc.)

Google Maps runs perfectly on DSA's ROM, providing your not running another app thats using a lot of resources.
[MTCB Software Development] typos1:
So, it would probably have been better to ask Klyde directly to get things from the horses mouth :)
[MTCB Software Development] mouscolo:
I really appreciate it man, but honestly I totally have no idea about what u all type and what to do with it :(

I didn't meant to disrespect but I really don't know how to
[MTCB Software Development] Oldpapa49:
What dsa8310 is pointing out if you use Root Explorer, you can make the settings update when the unit boots all the time in the 'build.prop' file.

And app can do the same. I think the LE DPI has the choice to edit the 'build.prop' file for you. That app works only under a rooted device.

dsa8310 is a really good dev and has great amount of knowledge and will help.
[MTCB Software Development] mouscolo:
no doubt about [MENTION=6041319]dsa8310[/MENTION] man, I tried LE DPI, somehow its not feeling right, like notification center icons become too small but the frame still huge, icons and other thing to fitting well :)
[MTCB Software Development] shanetrainST:
I have directly asked them, Klyde have not responded, Eonon have.

Eonon are chasing it up for me, have a long email history with them anyway. Hopefully they come through with the goods
[MTCB Software Development] KaMu1219:
I did a fresh install of October Firmware. Mtcservice is shown as active in Xposed, I can see the 12 chars serial there.

I installed TomTom go app, downloaded from play store (com_tomtom_gplay_navapp-1640641.apk, 62.698.758 Bytes, downloaded with Raccoon) and installed with the ApkInstaller.

When starting TomTom go, I first get "Starting app retrieving settings from TomTom", then after some seconds "The app cannot connect to TomTom".

I read all over xda-developers.com and thought I was doing everything correct. What am I missing?

In android settings "About device" is showing me a 32 chars serial. Shouldn't it be the 12 chars serial from mtcservice?

Thanks in advance
[MTCB Software Development] KaMu1219:
I didn't change the serial in mtcservice, I just used the one that was there after installation of the ROM. I never installed TT before on this ROM.

But I followed your advice:

1. Uninstalled TT Go

2. Changed serial

3. Rebooted

4. Checked changed serial was there in mtcservice (yes, but in "About device" still the 32 chars serial)

5. Installed TT Go again

-> "The app cannot connect to TomTom".

Sorry for this. I appreciate your help Any more information I can provide?
[MTCB Software Development] KaMu1219:
Deleted serial, rebooted, got new serial, rebooted to check if new serial stayed, installed TT Go -> "The app cannot connect to TomTom"

Uninstalled mtcservice via command line in Termux, rebooted, mtcservice got restored and generated new serial, rebooted to check if serial stayed, installed TT Go -> success.

Rebooted to see if TT go starts a second time -> success

Wow, you made my day. Thanks!
[MTCB Software Development] nuovagrafica:
is dsa rom better than malaysk? Why?
[MTCB Software Development] typos1:
No offence to [MENTION=3590033]Malaysk[/MENTION], but yes because its not as laggy, although dsa's lacks FUSE unlike Malaysk's.

Having said that it would be worth trying Malaysks once you have 2GB RAM fitted. :)
[MTCB Software Development] nuovagrafica:
Escuse me for my bad english... it will be better malaysk or dsa cwith 2gb? Could us have fuse in next versions?
[MTCB Software Development] typos1:
Any ROM will be better with 2GB RAM. With 1GB Malaysks is quite laggy, dsa's is not.

I was just saying that once you have 2GB RAM it will be a good idea to try Malaysks again as the extra RAM may reduce or indeed remove the lag.
[MTCB Software Development] imbakarle:
Tryed the Firmware. No lags and all run fine. Only My 3g doesn't work. I have to disconnect and Connect the usb-stick to get a real connection. The 3g Icon is shown on start but internet don't work without disconnect/Connect.

Is there an option to start the radio after Boot? The fw don't remember the last Situation bevor shutdown.
[MTCB Software Development] typos1:
Try updating your MCU, or re flashing it if you have the latest version. What MCU do you have ?
[MTCB Software Development] imbakarle:
I think KDL6 2.97 - Installed the newest from Server. So I try to reinstall in a few hours.
[MTCB Software Development] typos1:
KLD9 v2.98 stores radio stations, previously the only way to store them was to install Xposed and use the MTCXposed app.
[MTCB Software Development] imbakarle:
I already got the 2.98

I think you read my post wrong. I dont write Station - I write Situation :) . The Problem ist that the mtc dont remember the status after a shutdown.
[MTCB Software Development] miffymiffy:
change the shutdown delay to never. It will reopen where you left off.

And before he corrects you, you said you have kld6.2.97, not kld9.2.98
[MTCB Software Development] imbakarle:
The read wrong refers to Situation/Station. I did not mean to be angry

I will try to change the shutdown time. Thx
[MTCB Software Development] psxsnake:
If u like is better if not is worst... So try

psxsnake
[MTCB Software Development] mouscolo:
here I done the changes using LE DPI, see the screenshots :\
[MTCB Software Development] Anulomax:
I have a problem with this ROM, everything works fine but something fundamental, dont detect any GPS.

The stock ROM 4.4.4 works, the Malaysk 4.4.4 and 5.1 also, the Stock Eonon 5.1 also but this dont works the GPS.

My device is an MTCB KLD6 V2.85 any ideas? I did everything, multiple wipes, install first the ROM of September and then the one of October (in the one of September the gps doesnt work too ), install it after a 4.4.4 or of Stock Eonon 5.1 and it does not work either. Sorry for my English.
[MTCB Software Development] psxsnake:
I think the first to do is "check the cable connection" ;)

[MENTION=7674440]mouscolo[/MENTION] which DPI u set it?
[MTCB Software Development] miffymiffy:
Install xposed 'app settings' and change dpi of separate apps back to 240.
[MTCB Software Development] mouscolo:
160 or 180 I don't remember ill check it now and confirm
[MTCB Software Development] typos1:
Lol, I did, sorry ! :)
[MTCB Software Development] mouscolo:
it didn't help, same look in my screenshots but bigger and pixilated :\
[MTCB Software Development] dcplaya:
I have 2 questions/issues but also some praise!

Questions first

1) When changing the volume while using Google Music to listen to music, each tick on the volume changer causes the audio to cut out for a split second. Not a huge issue but just annoying. Does that happen with anyone else? Is there a way to fix it?

2) When using my steering wheel buttons and I try to change a song, it always changes the station on the radio even if I have Google Music open. I know other ROMs had the ability to pick what app would work with the SWC, is there something like this in this ROM that I just looked over?

I will say the boot time and the general UI is much faster than other ROMs I used. I can actually use Google Maps now for the most part!
[MTCB Software Development] typos1:
Not heard of the volume issue before, but I have heard of the SWC issue with Google Play music, think it was in the Malaysk 4.4.4 or 5.1.1 thread and think its a problem specific to this app on these units as opposed to which ROM youre using.
[MTCB Software Development] mouscolo:
volume things happened with me, but it got fixed after I finish the updates by itself
[MTCB Software Development] dcplaya:
What do you mean it got fixed after you finished the updates? I updated using the .rar packages in post 1 and wiped before and after installation.
[MTCB Software Development] mouscolo:
google service and the other stuff, I got this issue once I installed DSA ROM with Anghami app, after I done all the updates and installing all my apps it got fixed.
[MTCB Software Development] Anulomax:
Nothing appears in the GPS card, when the update is done after copying the system and oem appears a message that seems a mistake but it is so fast that I cant read it and restart. I will try to look these days if the GPS cable is well connected and try another SD card. The error message looks like a failed copy ,maybe external_sd

I'll try take some screenshots, thank you [MENTION=6041319]dsa8310[/MENTION]
[MTCB Software Development] Terabite7:
One quick question, what is the available app space in these roms. I tried searching the thread but didn't found an answer.
[MTCB Software Development] dcplaya:
I am pretty sure Google Music does see the intents but if I have to I can change up the AndroidManifest.xml (Havent decompiled one of those for awhile!). I will look at the install-recovery.sh later this weekend and see what I can do. I will post back the modified files if I get it to work properly. I rarely use the AM/FM radio so using the SWC with that is kind of useless to me
[MTCB Software Development] typos1:
3GB.
[MTCB Software Development] Terabite7:
Perfect, thanks!!! I flashed the rom and I admit it is the fastest 5.1.1 I have tried, I have another question though. In the October version is the Radio app missing or I made a mistake during flashing?
[MTCB Software Development] Terabite7:
So, basically I got to a "Troll Avoidance Policy ignore-list" for wanting some information and help... That was the reason I haven't logged in XDA for soooo long... For guy's like this.... Whatever...
[MTCB Software Development] Oldpapa49:
You too!

Sorry.. Once listed I guess always listed. Not even a pardon is available. I even message him as well.. No go..
[MTCB Software Development] typos1:
Its all because he and I fell out a few months back, since then hes ignored me, last week I happened to put "dsa ROM" in my thread title because the guy who made another custom ROM had stopped doing it and people were having trouble finding which thread [MENTION=6041319]dsa8310[/MENTION]'s ROM was discussed in. He removed all helpful posts from the previous thread which no one can stop him doing, started this one and told people that if they replied to me he would not reply to them. All because I tried to make it easier for people to find the thread with his ROM in it. I ve been on xda for years and I NEVER experienced anyone like this.

According to post #37 pardon IS available [MENTION=4358937]Oldpapa49[/MENTION], if you pm him and remove the posts where you quote someone on his ignore list (which he hasnt published, so how youre supposed to know is beyond me, although some people, including me, seem to think I am at the top of it !).

[MENTION=4358937]Oldpapa49[/MENTION] didnt even know about this policy because he quoted me before [MENTION=6041319]dsa8310[/MENTION] posted it.

Please do not let this put you off [MENTION=2407346]Terabite7[/MENTION] - prior to this the XDA MTC headunit community has been great for 3 years - very helpful and we all normally get along - youre welcome to post in this thread whenever you so wish and others will reply and help you.
[MTCB Software Development] rdavidowski:
Hi,

Can anyone point me to the procedure on how to make the upgrade to 2 GB Ram. I read the whole thread and notice the chips needed and were to get them but no instructions on how to actually install them. Help will be greatly appreciated.
[MTCB Software Development] typos1:
[MENTION=6041319]dsa8310[/MENTION] has removed all his useful posts from the other thread, however he has posted about the RAM in this thread, I cant remember the post but theres not many pages to look through.

Also there is the "2GB RAM Group Buy" thread with some info :

http://xdaforums.com/android-auto/mtcb-hardware-development/2gb-ram-t3483677

Basically its very simple - remove the old chips and solder the others in their place - the solder pads are in the same place on the 1GB chips.
[MTCB Software Development] champikasam:
I installed October 2016 rom on my RK3188 headunit. Everything is working smoothly except for a small issue in the bluetooth app. Phone numbers in my country have the format 0xxxxxxxxx (zero at the front). The address book syncs with the phone well and shows all the contacts. But when a call comes in, the number is shown as xxxxxxxxx (without the 0 in the front) so it does not pick the caller name from the address book. Only the number is shown. Is there a fix for this ?
[MTCB Software Development] dcplaya:
So I am able to get Google Music to start at boot by modifying that script you told me about. But media intents aren't working. The "Previous Track" button actually pauses the music and the next track does nothing.

Google Music does catch the MEDIA_BUTTON intent

<receiver android:exported="true" android:name="com.google.android.music.playback.MediaButtonIntentReceiver" android:process=":main">
<intent-filter>
<action android:name="android.intent.action.MEDIA_BUTTON"/>
</intent-filter>
</receiver>

Which should allow it to handle the hardware media keys (If I am reading stuff correctly). My guess is the app that handles the SWC --> Media intents is not correct? Has anyone looked at the XML for that?
[MTCB Software Development] dcplaya:
I first thought I had to reset my SWC and I even set them to different things first and set them back to next/previous, testing to see if Google Music would see anything each time I changed it and the end result was always the same. I wonder if the intent entry for Poweramp is similar or not. Ill have to check that later.
[MTCB Software Development] dcplaya:
I'm using a resistive converter for my SWC (No Canbus, HU does not support Ford Escape 2011) and I even see the little ">>" or "<<" on screen when the button is push. It is definitely something with either Google Music or MTCService. The search continues on!
[MTCB Software Development] ajayel:
also no 3G internet (Huawei E3131 modem) with MTCB-KLD6-V.285 & October ROM. i would like to get 3G internet working as this is the best ROM i've ever used.

the modem works once after clearing all data via the recovery menu but is not used on subsequent reboots although ES file explorer shows it as an unmountable USB drive labelled USB2006
[MTCB Software Development] typos1:
Try updating your MCU to KLD9 v2.98., this may sort it.
[MTCB Software Development] dsa8310:
Misplaced Threads, Redundant Sections in Android Auto

---
[MTCB Software Development] typos1:
I have already requested for MTCB sections to be renamed "MTCB/C". This is all that needs doing, no other changes to the forum layout is necessary.