Best Firmware to Update to - MTCB Android Head Units General

Hey guys,
I have an MTCB Carjoying unit back from early 2016 with Malaysk 4.4.4 ROM from that time still running on it. It's run absolutely fantastic for 2 years now. Started looking back through here and see theres a bunch of options to upgrade to now...and it's kind of a lot to take in since I last was "in the game" haha. So I thought maybe you guys could recommend best firmware to update to, since it looks like Malaysk isnt the only guy in the game right now, and his stuff seems way more than i need!
Carjoying VW Android 4.4.4 MTCB RK3188 1024x800 headunit
Most Important things:
Startup time, as fast startup as possible
Auto startup to previous music app, if it was sd card music or radio
Button remapping
pandora/spotify working
IGO Primo or equivalent Nav system working offline
Torque Pro Working
Other than that, not that much else needed... I'm of course open to ideas of what things you guys like best as well!

dannyboy223 said:
Hey guys,
I have an MTCB Carjoying unit back from early 2016 with Malaysk 4.4.4 ROM from that time still running on it. It's run absolutely fantastic for 2 years now. Started looking back through here and see theres a bunch of options to upgrade to now...and it's kind of a lot to take in since I last was "in the game" haha. So I thought maybe you guys could recommend best firmware to update to, since it looks like Malaysk isnt the only guy in the game right now, and his stuff seems way more than i need!
Carjoying VW Android 4.4.4 MTCB RK3188 1024x800 headunit
Most Important things:
Startup time, as fast startup as possible
Auto startup to previous music app, if it was sd card music or radio
Button remapping
pandora/spotify working
IGO Primo or equivalent Nav system working offline
Torque Pro Working
Other than that, not that much else needed... I'm of course open to ideas of what things you guys like best as well!
Click to expand...
Click to collapse
I think the best is @Johny DJ's ROM.

Related

Help with Pumpkin RQ0248 car radio (MTCB-KLD6-v2.85) Android upgrade

Hi all, I'm certain this info can be found in tons of places on this forum, but I'm brand-new (first post, woo!) and that amount of info here is a little overwhelming.
So, first thing's first: Pumpkin's forum is crap, the one moderator there either doesn't allow posts about android upgrades or flatly denies it isn't possible (I know they're lying).
I have a Pumpkin RQ0248, using an RK3188 cpu and still running Android 4.4.4. I've learned here that it's also known as "MTCB-KLD6-v2.85". It seems like my car radio CAN be upgraded to Android 5.1 (which is awesome), but I'd just like to check some facts with the experienced folks here:
- I download an "Update.img" file to a... microSD card? USB? (Does it even matter? Pumpkin's site says microSD in the maps slot).
- I run the System update button (or whatever it's called) and select the above image file. Let it do it's thing. It'll reboot, at which point I do a factory setting reset? I believe so.
- The file I've downloaded is "KLD_LP_rk3188_p_2016_05_11", I think it's the right one, but I want to be certain. Perhaps there's an even newer one?
- While poking around (and getting confused) I saw some people claim their radio app sometimes would stop working? Is that a regular thing? I know how to enter the "factory" settings (using PW 126) and saw that some people just had to change their radio chip version? Is that trial and error or is there a specific one I should use for mine?
Thanks for all the help in advance! And sorry for the newbie questions!
Anyone? Please lend a hand... I'm very nervous about flashing (and possibly bricking) my car radio...
cmetaphor said:
Anyone? Please lend a hand... I'm very nervous about flashing (and possibly bricking) my car radio...
Click to expand...
Click to collapse
You need to take pictures of the pages in factory settings for later use. e.g radio and other settings.
What you have given so far concerning MCU it should be possible to upgrade. Don't touch MCU, only
ROM needs to be upgraded.
Also be sure you can get in to recovery. Important is also the screen size 800 or 1024. You have to pick the right one. If you don't
know go to play store and install an app that tells your screen size. It doesn't matter in which SD-slot you're upgrading from.
Normally we use the GPS-slot (left one).
halloj said:
You need to take pictures of the pages in factory settings for later use. e.g radio and other settings.
What you have given so far concerning MCU it should be possible to upgrade. Don't touch MCU, only
ROM needs to be upgraded.
Also be sure you can get in to recovery. Important is also the screen size 800 or 1024. You have to pick the right one. If you don't
know go to play store and install an app that tells your screen size. It doesn't matter in which SD-slot you're upgrading from.
Normally we use the GPS-slot (left one).
Click to expand...
Click to collapse
ROM? I thought MCU was the important part that needed to be "flashed".
Can't post links to photos... not enough posts yet... Just tell me other info is required beyond what I posted originally?
I know my screen size is 480x800. Recovery mode, I don't know right now how to get enter it, but I know it exists (button combination held when booting).
Was the file I mentioned in my first post not the correct one to use?
The "official" response from the Pumpkin trash "tech" is that there is no real upgrade for my unit, but he provided a link for me to try it (aka removing any responsibility for bricking the radio). So full of crap, I've already seen RQ0248's being sold online with Android 5.1
If you haven't figured this out yet...here you go. I believe you and I have exactly the same unit. I actually read your thread with Jammy and his responses. HAHA. He isn't much help. I actually flashed what he provided to you and it booted, but the resolution was all off. I think that was for a 800X480 unit.
Pretty simple:
Download the latest V2.97 MCU image file for KLD6: http://forum.xda-developers.com/showthread.php?t=3246386
and download the latest Malaysk Rom: http://forum.xda-developers.com/showpost.php?p=69366390&postcount=860
I just put them both onto a USB flash drive, booted into recovery, and flashed them. After flashing I wiped data again and flashed them again, and wiped data one more time. First boot can take some time, but it's working flawlessly now.
dmband64 said:
If you haven't figured this out yet...here you go. I believe you and I have exactly the same unit. I actually read your thread with Jammy and his responses. HAHA. He isn't much help. I actually flashed what he provided to you and it booted, but the resolution was all off. I think that was for a 800X480 unit.
Pretty simple:
Download the latest V2.97 MCU image file for KLD6: http://forum.xda-developers.com/showthread.php?t=3246386
and download the latest Malaysk Rom: http://forum.xda-developers.com/showpost.php?p=69366390&postcount=860
I just put them both onto a USB flash drive, booted into recovery, and flashed them. After flashing I wiped data again and flashed them again, and wiped data one more time. First boot can take some time, but it's working flawlessly now.
Click to expand...
Click to collapse
Yeah, don't get me started with that forum over there... I shiver in disdain with my entire experience there.
TBH, Im like 99% certain my radio is 800x480 (we ARE talking about the RQ0248 right?). I'm still running the v2.91 MCU with the stock image "that person" gave me. And at very least, most of my issues with the radio have improved since doing so: My FM radio reception seems a little clearer, and the Bluetooth audio quality (streaming from spotify on my phone) is also quite a bit better.
That being said, everything about the 5.1.1 OS i'm running is HIDEOUS. The home screen and radio app particularly are just so ugly, aesthetically-speaking. I wasn't about to push my luck on the other forum though: it was hard enough to get an official response to fix my software bugs in the first place.
So, question time!
1) What does MCU v2.96 offer vs v2.91?
2) What does the Malaysk ROM offer vs the stock 5.1.1?
3) Does the Malaysk offer different skins? Customization?
4) Is there some way to improve the functionality of the built-in radio/music apps? (ex: no ID3 tags from MP3s... I'm pretty sure my MP3 player from 2002 has ID3 tags, this radio does not).
Thanks for answering! I had almost given up hope for this forum, it seems very popular in some areas, but this section seems to have much less in the way of activity.
Looking forward to hearing back!
cmetaphor said:
Yeah, don't get me started with that forum over there... I shiver in disdain with my entire experience there.
TBH, Im like 99% certain my radio is 800x480 (we ARE talking about the RQ0248 right?). I'm still running the v2.91 MCU with the stock image "that person" gave me. And at very least, most of my issues with the radio have improved since doing so: My FM radio reception seems a little clearer, and the Bluetooth audio quality (streaming from spotify on my phone) is also quite a bit better.
That being said, everything about the 5.1.1 OS i'm running is HIDEOUS. The home screen and radio app particularly are just so ugly, aesthetically-speaking. I wasn't about to push my luck on the other forum though: it was hard enough to get an official response to fix my software bugs in the first place.
So, question time!
1) What does MCU v2.96 offer vs v2.91?
2) What does the Malaysk ROM offer vs the stock 5.1.1?
3) Does the Malaysk offer different skins? Customization?
4) Is there some way to improve the functionality of the built-in radio/music apps? (ex: no ID3 tags from MP3s... I'm pretty sure my MP3 player from 2002 has ID3 tags, this radio does not).
Thanks for answering! I had almost given up hope for this forum, it seems very popular in some areas, but this section seems to have much less in the way of activity.
Looking forward to hearing back!
Click to expand...
Click to collapse
I'm not sure what the benefit is of the 2.96, but it's newer so it must be better! That was just the latest so that's what I used. THere are a ton of benefits so you should read the thread....but here are a few: Malaysk offers quite a few optimizations, built in root, customization including skinned apps and radios, and MOST importantly in my opinion is the FUSE support...which means the full 16gb of system space are available to use for apps. You won't run out of space again. Yes there are other music apps included in his ROM as well, but I haven't used them much so I can't really speak to their functionality...but I'm sure it's better than the stock app.
But, do the new music apps work with the steering wheel controls?
That pumpkin forum is ridiculous lol yes im after a factory looking stable rom with fuse the origional firmware that came with the 2.85 mcu worked flawlessly but it double booted so i tried custom firmware when he sent me the original firmware again, it wasnt the same it didnt even boot properly with 2.85 i had to update the mcu to 2.91 for the firware to even become useable
cmetaphor said:
But, do the new music apps work with the steering wheel controls?
Click to expand...
Click to collapse
Can I get an answer to this? The music app is terrible in terms of supporting things like ID3 tags and the like.
Don't even get me started on the 5.1.1 radio app, never seen something so hideous.
So I really want to know if there are alternative apps out there, or at very least better skins, for the garbage apps that Pumpkin dishes out.
Side Note: How good is the android auto integration in these head units? I've never tried it myself.... But Android auto is quite pretty to look at, and I really wouldn't mind tethering my phone via USB cable to my car radio if it meant a better overall experience. That being said though, things like the steering wheel control absolutely MUST function with android auto tether/mirror link/whatever it's called too.
Thanks in advance for anyone that replies! It's unfortunate that so few people do reply here, and this forum has been far more helpful than any other I've used so far.
cmetaphor said:
Can I get an answer to this? The music app is terrible in terms of supporting things like ID3 tags and the like.
Don't even get me started on the 5.1.1 radio app, never seen something so hideous.
So I really want to know if there are alternative apps out there, or at very least better skins, for the garbage apps that Pumpkin dishes out.
Side Note: How good is the android auto integration in these head units? I've never tried it myself.... But Android auto is quite pretty to look at, and I really wouldn't mind tethering my phone via USB cable to my car radio if it meant a better overall experience. That being said though, things like the steering wheel control absolutely MUST function with android auto tether/mirror link/whatever it's called too.
Thanks in advance for anyone that replies! It's unfortunate that so few people do reply here, and this forum has been far more helpful than any other I've used so far.
Click to expand...
Click to collapse
Pumpkin is a seller only, there is no such thing as a "Pumpkin RQ0248", its a Klyde unit. I m guessing you havent bothered to read the wiki, if you did youd find a load more info and realise that that your unit is the same as any other Klyde unit no matter what it looks like on the outside or who you buy it from (Eonon, Pumpkin, Erisin ) and that its also so similar to any other MTCB or MTCC head unit made by the 10 odd manufacturers who produce these units, that it can use the same software as all of them.
I m also guessing that you dont read or look in the main threads in the 4 MTCB/C forums either, cos youd know all about the custom ROMs and modified apps that are available.
I m guessing neither did the OP or he wouldnt have opened the thread in the first place, we cant have a thread open for every made up model number by every seller of all 10 manufacturers, there would be literally 1000s of thread all with the same content. All the info for this unit is the same for any other MTCB/C unit.
cmetaphor said:
But, do the new music apps work with the steering wheel controls?
Click to expand...
Click to collapse
typos1 said:
Pumpkin is a seller only, there is no such thing as a "Pumpkin RQ0248", its a Klyde unit. I m guessing you haven t bothered to read the wiki, if you did youd find a load more info and realise that that your unit is the same as any other Klyde unit no matter what it looks like on the outside or who you buy it from (Eonon, Pumpkin, Erisin ) and that its also so similar to any other MTCB or MTCC head unit made by the 10 odd manufacturers who produce these units, that it can use the same software as all of them.
I m also guessing that you dont read or look in the main threads in the 4 MTCB/C forums either, cos youd know all about the custom ROMs and modified apps that are available.
Edit: Yay! This forum had an ignore button! Just learned that today too.
I m guessing neither did the OP or he wouldnt have opened the thread in the first place, we cant have a thread open for every made up model number by every seller of all 10 manufacturers, there would be literally 1000s of thread all with the same content. All the info for this unit is the same for any other MTCB/C unit.
Click to expand...
Click to collapse
Oh look everyone! I've found the @#$%.
Kind replies are far more helpful than sarcastic, snide, rude and jerk replies. Instead of replying next time, I'd prefer you not reply at all.
There are actual helpful people here that could explain these to me nicely, and have been doing so thus far. These forums are MASSIVE - I don't have the time to read for hours and possibly put myself on the Wrong track if I happen to miss some important details. Also, unless I somehow was able to magically learn what a Klyde radio is on my own, I had never heard of that detail before. Maybe a nice person could've explained it to me.
But kind isn't you. So please go away and allow the nice people to speak.
cmetaphor said:
Oh look everyone! I've found the @#$%.
Kind replies are far more helpful than sarcastic, snide, rude and jerk replies. Instead of replying next time, I'd prefer you not reply at all.
There are actual helpful people here that could explain these to me nicely, and have been doing so thus far. These forums are MASSIVE - I don't have the time to read for hours and possibly put myself on the Wrong track if I happen to miss some important details. Also, unless I somehow was able to magically learn what a Klyde radio is on my own, I had never heard of that detail before. Maybe a nice person could've explained it to me.
But kind isn't you. So please go away and allow the nice people to speak.
Click to expand...
Click to collapse
I didnt write anything that was unkind, snide, sarcastic rude or jerk, I simply gave you some information about where to look to avail yourself of some basic info about your headunit, I didnt have to, I wasnt paid for it, yet I did, in my book, thats "kind". What you require, it seems is someone to spend their time re-typing out whats already been written in other threads into this thread, because you cant be bothered to either look for it/read it yourself (known on xda as "spoon feeding").
It seems that you also havent bothered to read the post I just made properly either, because if you had, you would have seen me refer to "the wiki" (also linked to in the sticky in the very first post of this forum AND in my signature !) and would realise that you dont need any "magic" to learn what a "Klyde" is, you just need to read something mentioned TWICE on the screen in front of you !
In your previous post you also complained that "so few people reply here", if you read what I wrote in my reply, you ll realise why that is - theyve all read the basic info and are replying in threads that apply to ALL MTCB/C headunits.
On xda youre supposed to read stuff and find out for yourself and if you cant find the info you need or dont understand something or need help with something then there are loads of people (including me - look at my thanks meter) who will happily help you. But its clear that you havent read a thing, nothing, not one bit, not the sticky in the general section, not the Q&A section's first thread, not the wiki, nothing, diddly squat. So to help you in the way you want, I would have to write whats already been written and I aint doin that - you read at least the basics of it and ask questions if you dont understand something or cant find it.
Curtusz said:
That pumpkin forum is ridiculous lol yes im after a factory looking stable rom with fuse the origional firmware that came with the 2.85 mcu worked flawlessly but it double booted so i tried custom firmware when he sent me the original firmware again, it wasnt the same it didnt even boot properly with 2.85 i had to update the mcu to 2.91 for the firware to even become useable
Click to expand...
Click to collapse
Sounds like the ROM you were given was more up to date ROM - new features often have to be enabled by updating the MCU too, as that controls a lot of functions. Its also because you now have an MTCC MCU - 2.85 is MTCB, 2.91 is MTCC and older ROMs dont work with older MTCB MCUs.
Yup it is now a mtcc unit ... im actually using kld9 2.98 i think, i found now my new rom is also double booting after an app install , so its certain apps that cause double booting. Just outa interest what rom are you using? (if you have a kylde unit)
Curtusz said:
Yup it is now a mtcc unit ... im actually using kld9 2.98 i think, i found now my new rom is also double booting after an app install , so its certain apps that cause double booting. Just outa interest what rom are you using? (if you have a kylde unit)
Click to expand...
Click to collapse
I m using booroondook's ROM. When you say double booting do you mean it boots, shuts down then reboots ?
Basically boots up as it should , then after about 5 seconds boot logo appears then boots again doesnt shut/power down , it started after i downloaded an app called virtual dyno mobile, i will try the rom your using
Curtusz said:
Basically boots up as it should , then after about 5 seconds boot logo appears then boots again doesnt shut/power down , it started after i downloaded an app called virtual dyno mobile, i will try the rom your using
Click to expand...
Click to collapse
Thought so, not heard of that before, strange.
Yeah its common across the pumpkin forum. I dont know where they are getting their roms from but they are terrible.
Curtusz said:
Yeah its common across the pumpkin forum. I dont know where they are getting their roms from but they are terrible.
Click to expand...
Click to collapse
They get their ROMs from Klyde, the manufacturers of the units !

Bluetooth Metadata issues after Nougat Upgrade

Hi guys,
For those that have Bluetooth in your cars and use apps like SoundCloud, Pandora, etc., have you had issues with track information being displayed correctly?
Ever since I upgraded my Nexus 6 to nougat, the track information seems to be routed differently by the phones Bluetooth to my car's aftermarket Bluetooth receiver. Same has happened with my wife's Nexus 6 after she upgraded last week.
Both phones were working fine when on marshmallow using the same apps...Nothing else different other than upgrading to Nougat.
The only app that shows the metadata correctly on the main screen is the Play Music app. For all other 3rd part apps, I have to select "Channel List" and then I can see the track name. That was not the case with Marshmallow. All apps showed the metadata at the main screen where now it just displays some random numbers.
I know it's not the 3rd party music apps because they all display the metadata correctly when I have my work iPhone connected to my car.
Had the same problem on stock as well as Pure and Nitrogen. It's so frustrating because I don't have the slightest of clue on how I can go about figuring out what, if anything, has changed with the Bluetooth profile.
Any help or feedback would be greatly appreciated!
aerohp said:
Hi guys,
For those that have Bluetooth in your cars and use apps like SoundCloud, Pandora, etc., have you had issues with track information being displayed correctly?
Ever since I upgraded my Nexus 6 to nougat, the track information seems to be routed differently by the phones Bluetooth to my car's aftermarket Bluetooth receiver. Same has happened with my wife's Nexus 6 after she upgraded last week.
Both phones were working fine when on marshmallow using the same apps...Nothing else different other than upgrading to Nougat.
The only app that shows the metadata correctly on the main screen is the Play Music app. For all other 3rd part apps, I have to select "Channel List" and then I can see the track name. That was not the case with Marshmallow. All apps showed the metadata at the main screen where now it just displays some random numbers.
I know it's not the 3rd party music apps because they all display the metadata correctly when I have my work iPhone connected to my car.
Had the same problem on stock as well as Pure and Nitrogen. It's so frustrating because I don't have the slightest of clue on how I can go about figuring out what, if anything, has changed with the Bluetooth profile.
Any help or feedback would be greatly appreciated!
Click to expand...
Click to collapse
Ok first you need to understand a few things.
1. Just because it works on an Iphone doesnt mean anything when talking about android apps. They are completely different OSs as well as completely different apps. Built completely separately with different SDK
2. Just because it worked on the last update doesnt mean it will work on this.
As google play music works, that says they changed something in the 7.x update that broke the other apps. They will need to be updated to work with the change in the code.
zelendel said:
Ok first you need to understand a few things.
1. Just because it works on an Iphone doesnt mean anything when talking about android apps. They are completely different OSs as well as completely different apps. Built completely separately with different SDK
2. Just because it worked on the last update doesnt mean it will work on this.
As google play music works, that says they changed something in the 7.x update that broke the other apps. They will need to be updated to work with the change in the code.
Click to expand...
Click to collapse
Appreciate the feedback, thanks!
Yup... Definitely understand that iOS and Android are 2 complete different bases...I tested with the iPhone to make sure that the aftermarket Bluetooth receiver in the car was not the problem.
I do believe it's something that Google has changed and I'm starting to realize that the only option I may have is to wait and see.
One point I want to add is that the Nougat update did not break anything when it comes to connecting to my wife's Acura with built in Bluetooth. The track info continues to work fine..
I was hoping someone with more in depth knowledge of the Android systems maybe be able to chime in on what could have changed...I know the 3rd party apps i use have gone through multiple updates since Nougat came out so if they were gonna update something due to compatibility with Nougat, it would've happened already.
aerohp said:
Hi guys,
For those that have Bluetooth in your cars and use apps like SoundCloud, Pandora, etc., have you had issues with track information being displayed correctly?
Ever since I upgraded my Nexus 6 to nougat, the track information seems to be routed differently by the phones Bluetooth to my car's aftermarket Bluetooth receiver. Same has happened with my wife's Nexus 6 after she upgraded last week.
Both phones were working fine when on marshmallow using the same apps...Nothing else different other than upgrading to Nougat.
The only app that shows the metadata correctly on the main screen is the Play Music app. For all other 3rd part apps, I have to select "Channel List" and then I can see the track name. That was not the case with Marshmallow. All apps showed the metadata at the main screen where now it just displays some random numbers.
I know it's not the 3rd party music apps because they all display the metadata correctly when I have my work iPhone connected to my car.
Had the same problem on stock as well as Pure and Nitrogen. It's so frustrating because I don't have the slightest of clue on how I can go about figuring out what, if anything, has changed with the Bluetooth profile.
Any help or feedback would be greatly appreciated!
Click to expand...
Click to collapse
Exactly same issue here in my '15 Civic Si with Shamu, Victara, and Titan, Bluetooth metadata breaks after the first pairing/connection. Once Bluetooth is interrupted, either by shutting off car or disconnecting Bluetooth, metadata never displays again until I either clean flash ROM anew or delete the bluedroid folder contents and do the whole unpair and re-pair both audio device. Quite a pain of a workaround, and it doesn't stick either, breaks as soon as Bluetooth is interrupted again.
Since you're on Shamu, I can recommend Cyanide ROM and SIX ROM, also Pure Nexus (not sure why yours didn't work with it), I've tested a few updates of each of the three ROMs, and Bluetooth metadata worked fine. Nitrogen never worked for me either. AICP, CM, LOS, Resurrection Remix, Dirty Unicorns, Emotion OS, all break on this feature for now. Not sure how Google's own OS is running in this department, but I've seen quite a number of complaints on this issue with the 5x, 6p, both pixels, but not so much with Shamu. I've not ran Google's nougat since developer preview 5 of 7.0, and back then it was working, can definitely confirm. I just hopped on the custom ROM train ever since DU released their flavor of Nougat, and just can't or want to go back to stock vendor OS. But do try out Cyanide and SIX ROMs, they both worked flawlessly on this device. Both are packed with extra goodies too. If battery is more important, go with SIX ROM, it's by far the most fine tuned nougat ROM I've tested. You won't find it on XDA, look for it on G+ under "Frankie T (R3DS)" community. It's posted with all the direct links for proper installation. Cyanide is another amazing ROM, also another fine tuned ROM, comes with built in black theme, and good battery life (if you set the governor to interactiveX), but really smooth experience overall. SIX, by the way, uses Pure Nexus as a base platform, so just a heads up there. Personally I've used the last two pure Nexus ROM updates and had zero issues with song data displaying via Bluetooth. Make sure you clean flash the ROM, wipe dalvik cache, cache, date, and system. Leave the internal storage unchecked. If the issue persists, then backup your internal storage files/folders to an external drive/device and format the whole internal storage of your Shamu, then throw everything back on and try clean flashing, pure Nexus should work thereafter. I've even restored it as a nandroid backup a few times and had no issues. SIX ROM is pretty much a refined Pure Nexus with extra features. Give these a shot, well worth it. Let me know how it goes for you.
Syndrome666 said:
Exactly same issue here in my '15 Civic Si with Shamu, Victara, and Titan, Bluetooth metadata breaks after the first pairing/connection. Once Bluetooth is interrupted, either by shutting off car or disconnecting Bluetooth, metadata never displays again until I either clean flash ROM anew or delete the bluedroid folder contents and do the whole unpair and re-pair both audio device. Quite a pain of a workaround, and it doesn't stick either, breaks as soon as Bluetooth is interrupted again.
Since you're on Shamu, I can recommend Cyanide ROM and SIX ROM, also Pure Nexus (not sure why yours didn't work with it), I've tested a few updates of each of the three ROMs, and Bluetooth metadata worked fine. Nitrogen never worked for me either. AICP, CM, LOS, Resurrection Remix, Dirty Unicorns, Emotion OS, all break on this feature for now. Not sure how Google's own OS is running in this department, but I've seen quite a number of complaints on this issue with the 5x, 6p, both pixels, but not so much with Shamu. I've not ran Google's nougat since developer preview 5 of 7.0, and back then it was working, can definitely confirm. I just hopped on the custom ROM train ever since DU released their flavor of Nougat, and just can't or want to go back to stock vendor OS. But do try out Cyanide and SIX ROMs, they both worked flawlessly on this device. Both are packed with extra goodies too. If battery is more important, go with SIX ROM, it's by far the most fine tuned nougat ROM I've tested. You won't find it on XDA, look for it on G+ under "Frankie T (R3DS)" community. It's posted with all the direct links for proper installation. Cyanide is another amazing ROM, also another fine tuned ROM, comes with built in black theme, and good battery life (if you set the governor to interactiveX), but really smooth experience overall. SIX, by the way, uses Pure Nexus as a base platform, so just a heads up there. Personally I've used the last two pure Nexus ROM updates and had zero issues with song data displaying via Bluetooth. Make sure you clean flash the ROM, wipe dalvik cache, cache, date, and system. Leave the internal storage unchecked. If the issue persists, then backup your internal storage files/folders to an external drive/device and format the whole internal storage of your Shamu, then throw everything back on and try clean flashing, pure Nexus should work thereafter. I've even restored it as a nandroid backup a few times and had no issues. SIX ROM is pretty much a refined Pure Nexus with extra features. Give these a shot, well worth it. Let me know how it goes for you.
Click to expand...
Click to collapse
Wow! Thank you for the detailed feedback! Does your Si have factory nav?
Anyway, I can't tell you how many things I've tried to get this thing figured out...I also have active communication with the manufacturer of the Bluetooth unit to see if we can troubleshoot the issue..So far nothing.
This is the first time I'm hearing of SIX ROM so I'm gonna do some reading and then flash it later on in the week. I'll reply back with updates.
Thanks again!
aerohp said:
Wow! Thank you for the detailed feedback! Does your Si have factory nav?
Anyway, I can't tell you how many things I've tried to get this thing figured out...I also have active communication with the manufacturer of the Bluetooth unit to see if we can troubleshoot the issue..So far nothing.
This is the first time I'm hearing of SIX ROM so I'm gonna do some reading and then flash it later on in the week. I'll reply back with updates.
Thanks again!
Click to expand...
Click to collapse
Happy to help. No my Si doesn't have the navigation option, I just use my Shamu for that. I've finally got the attention of AICP moderator and developer at AICP G+ community, so it's looking like the Bluetooth metadata issue is a CM/LOS issue so far, they're going to look into it. I captured a logcat and pictures which are posted there under bugs+logcat. It's under AICP G+ community if you want to look at it, posted under my main Google account as Andrey K, you can check it out here: https://plus.google.com/112643646080294190790/posts/4FRbAonGT55.
As for you never hearing about SIX ROM, that's because the dev doesn't participate on XDA forums. It's a really stable nougat ROM all around, and now supports phh's root, which if paired with Magisk app, allows to hide root access from apps like Android pay and Pokemon go.
The most a manufacturer would offer is to replace the device, possibly for a fee, that won't solve your problem. Most nougat ROMs are currently experiencing this bug. Cyanide, SIX, and Pure Nexus do not have this problem, at least not on Shamu.
anyone ever come across a fix for this?
nerdyone255 said:
anyone ever come across a fix for this?
Click to expand...
Click to collapse
Nah, still struggling with it...I keep hoping that a new Android update will fix it but so far no luck. It used to work fine for me in Lollipop but nothing since I've upgraded to Nougat. I'm on Nexus 6. Wife has a pixel XL and had the same issue when she was on Nougat so it's not the phone. She did get the Oreo update this week so I'll try again to see if it works. If not, then this must be a compatibility issue that the adapter manufacturer may need to look at...
The annoying thing is that the metadata transfer is fine when using my work iPhone. But I hate the iPhone/Apple so I only touch that thing when I absolutely have to (work calls, work emails, etc)
Any solutions so far?
My S2 worked perfect with the Civic (only it did not import the whole phonebook). With S8 I have the whole phonebook but no metadata on tracks (still plays and controls work)
---------- Post added at 01:31 AM ---------- Previous post was at 01:31 AM ----------
Any solutions so far?
My S2 worked perfect with the Civic (only it did not import the whole phonebook). With S8 I have the whole phonebook but no metadata on tracks (still plays and controls work)

Quick question for Mexican EVA-L09

Hi guys,
just a small question from someone who is not modding his device every day
I have a P9 EVA-L09C69, so a mexican device with a Telcel branding. As everything with Telcel it will take ages or probably never happen that they release the update to Android 7/EMUI5.
In general I´m fine with that, the only issue is that Android Auto is not working with the official built (as Huawei seems to have messed up with some video drivers....).
This feature is quite important for me, so I would be willing to update the phone to some version where it´s working.
I need this phone every day, so the only thing I´m really looking for is a verion where everythign works as it should, bluetooth, camera and so on. Only some ROM where somebody verified that Android Auto is not showing "not supported on this device" would be nice.
Anybody uses this and could recommend me a version and how to get there?
Thanks in advance.
LordBadHabit

AA Shutting down after screen unlock

Hi all guys, I've been missing a long time from here, so please be care enough to forgive me if I posted the thread in the wrong place.
I'm currently using Android Auto and enjoying very much the amazing work made from Gabriele (AAAD, of which I payed the PRO version in order to help the developer's job).
I'm running AA version 6.3.611314 (downgraded from 6.4, because otherwise AAAD didn't work, since AA 6.4.... doesnt' let you show the apps installed apart from the official ones); Ford Focus Active with Sync 3 updated to 3.4 version, a Galaxy Note 20 Ultra5G (European) with Android 11.
Everything works fine, even AAAD installed programs.
The only problem is that every time I unlock the phone it disconnects from AA and then it starts again from the beginning. I opened the DEv Options in the phone settings and chose as standard setting for the usb - File transfer / Android Auto.
My question is: Why this disconnections happen and HOW can I fix it? I currently drive with the phone unlocked and, useless to say, it doesn't charge as much as it would if the screen had been off. I alredy tried with other cables, even with a Sam S9+ original one.
Thanks in advantage, any help is appreciated.
Same here, S10+ latest official, AA 6.4.611714-release, Ford Sync 3.x .
Doing so for about a week (or some more). At phone unlock, AA is crashing to Sync interface, and phone is asking for permissions in order to start Android Auto again (need to press Allow, otherwise AA will not start!)
Thx!
Same here , s10
It'd be nice to know whether the problem starts from the phone version , the AA version or from the car itself.
gidannifico said:
It'd be nice to know whether the problem starts from the phone version , the AA version or from the car itself.
Click to expand...
Click to collapse
I can confirm that the issue is related to the last Sammy update , I have downgraded to may update , now aa works perfect
Guys, Google just updated the discussion thread three days ago:
Thanks for all the reports. We informed the Samsung team and they have applied a fix on an upcoming upgrade as part of the regular July maintenance release to resolve this issue. Please keep checking for system updates on the device.
Click to expand...
Click to collapse

Best ROM/Android Version for Android Auto Mirroring (Car gauges)

Hey guys,
I'm back here after many years because I bought a Pixel 5 to mirror my screen to show my EcuTek gauges for my Infiniti Q50 on the infotainment display via Android Auto. I was very into Android modding back when I had the Nexus 5X, so I thought this would be an easy task and I was very wrong. So much has changed since then. (there's two firmwares now? lol)
I got the phone rooted on the latest AOSP image, but none of the Android Auto root apps seem to have too much of an effect. I can't downgrade AA because it appears baked into the AOSP Gapps.
What's the best setup to use for this? The phone can be on any version/ROM of Android and will not be connected to cellular/wifi/hotspot so it can't auto-update.
Thanks for the help!

Categories

Resources