Anyone looking to improve the audio quality of their MTCD/E head unit has 5 options, each in their own thread scattered across 3 of the 4 MTCD forums, so I thought I d open one overarching thread for discussing and comparing all 5 options.
These mods apply to R3188/PX3 and RK3368/PX5 units, they should also work on Sofia units as well, but I dont recall reading that anyone has tried, theyll likely work on the new RK3369/Px6 hexacore units too, but again AFIAK no one has one yet.
1) The easiest and simplest way to improve sound quality is to flash one of @cs-x(RU)'s modified sound patched MCUs which give improved overall sound quality, just find one that matches you manufacturer and flash it, job done. No root required. Gives a small but useful improvement in sound quality. Thread here :
https://forum.xda-developers.com/an...ent/mod-cs-x-mod-mtcd-e-mcu-firmware-t3816042
2) @Wadzio has cleverly managed to implement @7floor's hardware mod (see below) in software, all thats needed is to flash one of his MCUs and install a few apps. Root is only required if you want to replace the original amp app with @Wadzio's - the original can be left installed for non root users. It doesnt work on all units yet as it requires the MCU to be modified quite heavily and @Wadzio cant spend all his time modded MCUs ! (he has released a guide on how to do it, though). It can be buggy on some units. Increases sound quality and enables much more control and more settings. Thread is here :
https://forum.xda-developers.com/an...elopment/mod-bd375xx-sound-processor-t3834657
3) @7floor's sound mod - on units without a factory fitted upgraded DSP (ie most currently), the audio chip is controlled by the MCU, @7floor's mod involves disconnecting the MCU from the audio chip and connecting the audio chip directly to the SoM so Android control it, some basic soldering skills are required. Units must be rooted, installing an app is also required. It works on Lollipop and MM units but its not currently working on Oreo units as the system cannot find a small file, however I its a minor bug that I think could be fixed easily. The mod was originally developed for the related MTCB/C units which is why the original thread is in the MTCB forum. Increases sound quality and enables much more control and more settings. Threads here :
https://forum.xda-developers.com/an.../mtc-sound-controlling-bd37xxx-sound-t3234660
https://forum.xda-developers.com/an...re-development/7floor-sound-mod-mtcd-t3624035
4) @cs-x(RU) has managed to retro fit an upgraded DSP to the same spec as the new units with factory fitted upgraded DSPs and it uses existing apps which the unit will automatically use if it detects that a DSP is fitted to the motherboard, so units dont have to be rooted. This mod wont be for everybody as it involves buying a DSP board and a lot of soldering. Increases sound quality the most. Thread here :
https://forum.xda-developers.com/an...nt/mod-simpledsp-installation-mtcd-e-t3823075
5) Buy a new unit with the upgraded DSP fitted at the factory. Thread here :
https://forum.xda-developers.com/an...eneral/dsp-units-androidautoshop-com-t3803557
this thread is incredibly helpful! Thank you!
sev said:
this thread is incredibly helpful! Thank you!
Click to expand...
Click to collapse
No probs, thats the idea.
Agreed - great idea. As a new MTCE Android head-unit owner, my head was spinning trying to figure all of this out. Unfortunately for me, this thread was a little late, but I'm sure it will be very helpful to other new users in the near future. Thank you for putting this together.
Should Viper4Android be added to your list (I'm acutally going to go that route myself instead of any of the other options - at least for now)?
Great thread @typos1, we'll done. Re. Wadzio #2 - root is not required if not replacing the stock apk.
I.E. there are two options
1. root - replacing the built in eq app or
2. Non-root - installing a second eq app.
jtrosky said:
Agreed - great idea. As a new MTCE Android head-unit owner, my head was spinning trying to figure all of this out. Unfortunately for me, this thread was a little late, but I'm sure it will be very helpful to other new users in the near future. Thank you for putting this together.
Should Viper4Android be added to your list (I'm acutally going to go that route myself instead of any of the other options - at least for now)?
Click to expand...
Click to collapse
Thanks. I havent included Viper4android, Dolbyatmos (not sure anyones tried that on a headunit actually) or any other equaliser app cos the thread was meant to be about MTCD/E specific improvements.
marchnz said:
Great thread @typos1, we'll done. Re. Wadzio #2 - root is not required if not replacing the stock apk.
I.E. there are two options
1. root - replacing the built in eq app or
2. Non-root - installing a second eq app.
Click to expand...
Click to collapse
Ta.
I never considered keeping the original amp app as an option TBH, but it means non root users can benefit from the mod, I ll edit it.
typos1 said:
Thanks. I havent included Viper4android, Dolbyatmos (not sure anyones tried that on a headunit actually) or any other equaliser app cos the thread was meant to be about MTCD/E specific improvements.
Click to expand...
Click to collapse
Ah - that makes sense. Otherwise, you'd have a gizillion different "equalizer"-type apps to include. Although, I truly think that Viper4Android is in a league of it's own and far more than a typical equalizer. I consider is a "software-based DSP", not just an equalizer - but like you said, it's not MTCD/E-specific, so I understand why it's not included.
But thanks again for putting this together - this will be a huge help for new MTCD/E owners!
I'm curious what others think of the different sound improvements. What is their favorite and why? And how do people feel about the software mods compared to Viper4Android?
I was really disappointed to find that these units didn't have a "real" 9-band EQ. At the very east, you'd think that it would be implemented via software if it can't be done via hardware. Is there any reason why it can't be done via software by the manufacturer (instead of needing to root and use Viper4Andorid in order to get a real EQ)? To me, Bass, Mid and Treble just isn't enough.
typos1 said:
Anyone looking to improve the audio quality of their MTCD/E head unit has 5 options, each in their own thread scattered across 3 of the 4 MTCD forums, so I thought I d open one overarching thread for discussing and comparing all 5 options.
These mods apply to R3188/PX3 and RK3368/PX5 units, they should also work on Sofia units as well, but I dont recall reading that anyone has tried, theyll likely work on the new RK3369/Px6 hexacore units too, but again AFIAK no one has one yet.
1) The easiest and simplest way to improve sound quality is to flash one of @cs-x(RU)'s modified sound patched MCUs which give improved overall sound quality, just find one that matches you manufacturer and flash it, job done. No root required. Gives a small but useful improvement in sound quality. Thread here :
https://forum.xda-developers.com/an...ent/mod-cs-x-mod-mtcd-e-mcu-firmware-t3816042
2) @Wadzio has cleverly managed to implement @7floor's hardware mod (see below) in software, all thats needed is to flash one of his MCUs and install a few apps. Root is only required if you want to replace the original amp app with @Wadzio's - the original can be left installed for non root users. It doesnt work on all units yet as it requires the MCU to be modified quite heavily and @Wadzio cant spend all his time modded MCUs ! (he has released a guide on how to do it, though). It can be buggy on some units. Increases sound quality and enables much more control and more settings. Thread is here :
https://forum.xda-developers.com/an...elopment/mod-bd375xx-sound-processor-t3834657
3) @7floor's sound mod - on units without a factory fitted upgraded DSP (ie most currently), the audio chip is controlled by the MCU, @7floor's mod involves disconnecting the MCU from the audio chip and connecting the audio chip directly to the SoM so Android control it, some basic soldering skills are required. Units must be rooted, installing an app is also required. It works on Lollipop and MM units but its not currently working on Oreo units as the system cannot find a small file, however I its a minor bug that I think could be fixed easily. The mod was originally developed for the related MTCB/C units which is why the original thread is in the MTCB forum. Increases sound quality and enables much more control and more settings. Threads here :
https://forum.xda-developers.com/an.../mtc-sound-controlling-bd37xxx-sound-t3234660
https://forum.xda-developers.com/an...re-development/7floor-sound-mod-mtcd-t3624035
4) @cs-x(RU) has managed to retro fit an upgraded DSP to the same spec as the new units with factory fitted upgraded DSPs and it uses existing apps which the unit will automatically use if it detects that a DSP is fitted to the motherboard, so units dont have to be rooted. This mod wont be for everybody as it involves buying a DSP board and a lot of soldering. Increases sound quality the most. Thread here :
https://forum.xda-developers.com/an...nt/mod-simpledsp-installation-mtcd-e-t3823075
5) Buy a new unit with the upgraded DSP fitted at the factory. Thread here :
https://forum.xda-developers.com/an...eneral/dsp-units-androidautoshop-com-t3803557
Click to expand...
Click to collapse
What a nice post!
Saw this video today, which led me to your post here, and I wonder if the speaker distance/delay setting works accordingly? Not expecting Pioneer-quality time alignment affect here, but a little bit of such an ability would be a big win.
jtrosky said:
Ah - that makes sense. Otherwise, you'd have a gizillion different "equalizer"-type apps to include. Although, I truly think that Viper4Android is in a league of it's own and far more than a typical equalizer. I consider is a "software-based DSP", not just an equalizer - but like you said, it's not MTCD/E-specific, so I understand why it's not included.
But thanks again for putting this together - this will be a huge help for new MTCD/E owners!
I'm curious what others think of the different sound improvements. What is their favorite and why? And how do people feel about the software mods compared to Viper4Android?
I was really disappointed to find that these units didn't have a "real" 9-band EQ. At the very east, you'd think that it would be implemented via software if it can't be done via hardware. Is there any reason why it can't be done via software by the manufacturer (instead of needing to root and use Viper4Andorid in order to get a real EQ)? To me, Bass, Mid and Treble just isn't enough.
Click to expand...
Click to collapse
The standard DSP has a 3 band equaliser and the related MTCB/C originally had this, but at some point it was changed to the fake 9 band set up (which some how takes average values for each band to make the extar 6 bands), @7floor's and @Wadzio's mods revert to the true 3 band equaliser, so one of these 2 mods is what you need to do to get a real eq.
I stopped using viper as soon as I did 7floor's mod, as I thought it was unnecessary after that, not keen on layers and layers of sound enhancements personally.
Xcaptain said:
What a nice post!
Saw this video today, which led me to your post here, and I wonder if the speaker distance/delay setting works accordingly? Not expecting Pioneer-quality time alignment affect here, but a little bit of such an ability would be a big win.
Click to expand...
Click to collapse
Thanks. Theres nothing to suggest that the delay settings dont work.
typos1 said:
The standard DSP has a 3 band equaliser and the related MTCB/C originally had this, but at some point it was changed to the fake 9 band set up (which some how takes average values for each band to make the extar 6 bands), @7floor's and @Wadzio's mods revert to the true 3 band equaliser, so one of these 2 mods is what you need to do to get a real eq.
I stopped using viper as soon as I did 7floor's mod, as I thought it was unnecessary after that, not keen on layers and layers of sound enhancements personally.
Click to expand...
Click to collapse
When I say that I want a "real" EQ, what I mean is that I want something with more than 3 bands. To me, 3 bands just isn't enough. That's why I'm interested in Viper4Android - becuase it will give me more than 3 bands and still be a "system wide" EQ. I really don't care if it's a hardware or software-based EQ - as long as it works and has more than 3 bands. I'm thinking that an octa-core unit with 4GB of RAM should be able to handle software-based EQ without issues - at least for what I'm planning to use it for... Not to mention all of the other cool stuff that only Viper4Android offers - such as the irs files. I've always been a fan of BBE and they even have irs files for BBE...
I was really disappointed to learn that the stock EQ was "fake" and was really only a 3-band EQ as a 5-band+ EQ was one of my "pre-requisites" when buying a head-unit. I'm hoping that Viper4Android will give me the extra tuning capability that I'm looking for though - becuase I REALLY like the flexibility of these Android head-units (used to WinCE head-units without any flexibility!).
Although, I haven't actually tested the unit "in car" yet, so maybe I'll be happy with the stock "fake" EQ. After all, I have an amp that has DSP built-in (auto-tuning DSP though - I can't customize it after it sets it up, which is why I still need the head-unit EQ to make small adjustments).
Great thread idea, something like this was definitely needed, and this is fairly comprehensive. I'll just put in that I have done the hardware DSP mod (Option #4 on this list) with great success. It has dramatically increased the audio quality of my unit, which was extremely poor before (Bad hiss and processing 'noise' from both RCA and speaker level outputs, which became basically unusable if you plug in anything to the USB ports).
I will note that this option is not necessarily compatible with all PX5 SOM's - I had to swap mine out in order to have the additional 4 pins required on the SOM.
jtrosky said:
When I say that I want a "real" EQ, what I mean is that I want something with more than 3 bands. To me, 3 bands just isn't enough. That's why I'm interested in Viper4Android - becuase it will give me more than 3 bands and still be a "system wide" EQ. I really don't care if it's a hardware or software-based EQ - as long as it works and has more than 3 bands. I'm thinking that an octa-core unit with 4GB of RAM should be able to handle software-based EQ without issues - at least for what I'm planning to use it for... Not to mention all of the other cool stuff that only Viper4Android offers - such as the irs files. I've always been a fan of BBE and they even have irs files for BBE...
I was really disappointed to learn that the stock EQ was "fake" and was really only a 3-band EQ as a 5-band+ EQ was one of my "pre-requisites" when buying a head-unit. I'm hoping that Viper4Android will give me the extra tuning capability that I'm looking for though - becuase I REALLY like the flexibility of these Android head-units (used to WinCE head-units without any flexibility!).
Although, I haven't actually tested the unit "in car" yet, so maybe I'll be happy with the stock "fake" EQ. After all, I have an amp that has DSP built-in (auto-tuning DSP though - I can't customize it after it sets it up, which is why I still need the head-unit EQ to make small adjustments).
Click to expand...
Click to collapse
Lol, youre the opposite of me - the only time I use the equaliser is for music older than the 1990s when I use the Rock setting, other than that I listen to it flat.
It sounds to me like you should do @Wadzio's mod, then install viper, at least @Wadzio's mod will give you the correct 3 band equaliser and not the fake 9 band one.
kaise123 said:
Great thread idea, something like this was definitely needed, and this is fairly comprehensive. I'll just put in that I have done the hardware DSP mod (Option #4 on this list) with great success. It has dramatically increased the audio quality of my unit, which was extremely poor before (Bad hiss and processing 'noise' from both RCA and speaker level outputs, which became basically unusable if you plug in anything to the USB ports).
I will note that this option is not necessarily compatible with all PX5 SOM's - I had to swap mine out in order to have the additional 4 pins required on the SOM.
Click to expand...
Click to collapse
Thanks.
Interesting what you say about the SoM differences, do you have any pics ?
typos1 said:
Lol, youre the opposite of me - the only time I use the equaliser is for music older than the 1990s when I use the Rock setting, other than that I listen to it flat.
It sounds to me like you should do @Wadzio's mod, then install viper, at least @Wadzio's mod will give you the correct 3 band equaliser and not the fake 9 band one.
Click to expand...
Click to collapse
Maybe we're not that differernt.... It's just that I'm old, so that vast majority of music that I listen to is older than the 1990s.
I just like having complete control and be able to adjust different frequencies as needed.
I would probably try @Wadzio's mod, but I have two problems:
1. I still don't have an original version of my MCU (MTCE_WWW_V2.85d_1)
2. I don't see a MTCE_WWW version of @Wadzio's mod... Some have said WWW = KLD, but without a backup of my original, not going to risk it.
I did find a MTCE_WWW version of @cs-x's mod (looks similar to @Wadzio's, but lacking loud adjustment) - but again, without having a backup of my original MCU, I'm hesitant to try it.... I did eventually convince Eonon to give me a copy of the stock ROM zip (update.zip) for my unit, but still trying to get the original MCU files...
It's killing me, but I'm being patient as I want to make sure I have a way to get back to where I started, just in case.
jtrosky said:
Maybe we're not that differernt.... It's just that I'm old, so that vast majority of music that I listen to is older than the 1990s.
I just like having complete control and be able to adjust different frequencies as needed.
I would probably try @Wadzio's mod, but I have two problems:
1. I still don't have an original version of my MCU (MTCE_WWW_V2.85d_1)
2. I don't see a MTCE_WWW version of @Wadzio's mod... Some have said WWW = KLD, but without a backup of my original, not going to risk it.
I did find a MTCE_WWW version of @cs-x's mod (looks similar to @Wadzio's, but lacking loud adjustment) - but again, without having a backup of my original MCU, I'm hesitant to try it.... I did eventually convince Eonon to give me a copy of the stock ROM zip (update.zip) for my unit, but still trying to get the original MCU files...
It's killing me, but I'm being patient as I want to make sure I have a way to get back to where I started, just in case.
Click to expand...
Click to collapse
WWW is deffo KLD and you dont have to have a back up - there are numerous WWW and KLD MCUs spread over various threads.
If youre waiting for a specific WWW 2.85 then this is also unnecessary - new MCU versions are released all the time , so your v2.85 is already out of date anyway.
In factory settings use the "Export" function, it will save your MCU settings.
typos1 said:
WWW is deffo KLD and you dont have to have a back up - there are numerous WWW and KLD MCUs spread over various threads.
If youre waiting for a specific WWW 2.85 then this is also unnecessary - new MCU versions are released all the time , so your v2.85 is already out of date anyway.
In factory settings use the "Export" function, it will save your MCU settings.
Click to expand...
Click to collapse
I'm don't really need the exact MCU, but I would at least like a WWW MCU that is equal to or greater than what I have now before I start messing with it - and so far, I haven't found one. I remember reading somewhere that the KLD MCU is ever so slightly different than the WWW MCU (I think the KLD powers off the unit with a press of the volume knob where WWW requires a press-and-hold). That may sound minimal, but I really don't want my unit shutting down if I bump the volume knob by accident - so even that little difference is enough to make me avoid the KLD MCU if I can - at least until I have a WWW version to fall back on if needed.
This is not really the right place, but if anyone reading this happens to have a stock WWW MCU file for 2.85d_1 or greater, please share. I'm assuming it's out there because I've seen a sound-modfied version of it. I just don't want to get stuck in a situation where I can't get back to where I started - epecially if I'm going to mess around trying to use KLD versions instead of WWW versions. I learned long ago to always make sure you can get back to where you started before you start "playing". I'll post a request in one of the MCU threads to see if I can find a recent WWW version, just in case I can't get it from Eonon.
jtrosky said:
I'm don't really need the exact MCU, but I would at least like a WWW MCU that is equal to or greater than what I have now before I start messing with it - and so far, I haven't found one. I remember reading somewhere that the KLD MCU is ever so slightly different than the WWW MCU (I think the KLD powers off the unit with a press of the volume knob where WWW requires a press-and-hold). That may sound minimal, but I really don't want my unit shutting down if I bump the volume knob by accident - so even that little difference is enough to make me avoid the KLD MCU if I can - at least until I have a WWW version to fall back on if needed.
This is not really the right place, but if anyone reading this happens to have a stock WWW MCU file for 2.85d_1 or greater, please share. I'm assuming it's out there because I've seen a sound-modfied version of it. I just don't want to get stuck in a situation where I can't get back to where I started - epecially if I'm going to mess around trying to use KLD versions instead of WWW versions. I learned long ago to always make sure you can get back to where you started before you start "playing". I'll post a request in one of the MCU threads to see if I can find a recent WWW version, just in case I can't get it from Eonon.
Click to expand...
Click to collapse
Seriously, youre being way, way too over cautious. That WWW is KLD is well known and you can remap the buttons in factory settings.
If you search the MCU threads you ll find a copy of a WWW MCU, but a I said, its not needed.
typos1 said:
Seriously, youre being way, way too over cautious. That WWW is KLD is well known and you can remap the buttons in factory settings.
If you search the MCU threads you ll find a copy of a WWW MCU, but a I said, its not needed.
Click to expand...
Click to collapse
I've read that being that my unit requires a CANBUS module, that key re-mapping cannot be done. Not sure if that is only for steering-wheel controls or if that also includes the physical buttons on the faceplate (I honestly didn't even realize the faceplate buttons could be remapped at all). I've very new to these radios, so yes, I am being overly cautious. In the end, if I experiment and end up with something that doesn't work right or just doesn't work like it "used to", then I'm SOL - at least until I have a copy of the current MCU, which I know at least works 100%. Believe me, I've searched and searched and searched and so far, I cannot find an MTCE_WWW_2.85d_1 or higher MCU file. I found one post that had a link to it (2.85), but the link was dead.
I'll see what Eonon comes back with tomorrow, but yes, due to previous experiences with stuff like this, I'm being very cautious - especially since my knowledge level is still low at this point. Rather be safe than sorry - especially since I'm still within my return window and am not even 100% sure that I'm keeping the unit. I must say, the CANBUS warning-chime and turn-signal sounds that I finally heard in-car yesterday were absolutely horrible - like I couldn't believe how bad.
But I do appreciate all of the input - it's all part of the learning process. I'm still reading and searching through the thousands and thousads of posts related to these radios - but it takes time... Threads like this are a huge help though!
jtrosky said:
I've read that being that my unit requires a CANBUS module, that key re-mapping cannot be done. Not sure if that is only for steering-wheel controls or if that also includes the physical buttons on the faceplate (I honestly didn't even realize the faceplate buttons could be remapped at all). I've very new to these radios, so yes, I am being overly cautious. In the end, if I experiment and end up with something that doesn't work right or just doesn't work like it "used to", then I'm SOL - at least until I have a copy of the current MCU, which I know at least works 100%. Believe me, I've searched and searched and searched and so far, I cannot find an MTCE_WWW_2.85d_1 or higher MCU file. I found one post that had a link to it (2.85), but the link was dead.
I'll see what Eonon comes back with tomorrow, but yes, due to previous experiences with stuff like this, I'm being very cautious - especially since my knowledge level is still low at this point. Rather be safe than sorry - especially since I'm still within my return window and am not even 100% sure that I'm keeping the unit. I must say, the CANBUS warning-chime and turn-signal sounds that I finally heard in-car yesterday were absolutely horrible - like I couldn't believe how bad.
But I do appreciate all of the input - it's all part of the learning process. I'm still reading and searching through the thousands and thousads of posts related to these radios - but it takes time... Threads like this are a huge help though!
Click to expand...
Click to collapse
AFAIK its only SWC, but there is a way to remap SWC anyway, so even if it applies to panel buttons it can be overcome.
You are deffo not SOL if something goes wrong, cos there are copies of WWW MCU in other threads, any WWW MCU will work "100%" and you can also use KLD MCUs. As I keep saying. Plus theres a wealth of info and help from us on here, so SOL you deffo arent.
Try remapping the panel buttons now - go into factory settings (password 126 or m123456), go to the tab for remapping and see.
Eonon ? Lol, they know F all about the units that they resell, good luck with that !
Cant see what the turn signal sounds have to do with your unit.
typos1 said:
AFAIK its only SWC, but there is a way to remap SWC anyway, so even if it applies to panel buttons it can be overcome.
You are deffo not SOL if something goes wrong, cos there are copies of WWW MCU in other threads, any WWW MCU will work "100%" and you can also use KLD MCUs. As I keep saying. Plus theres a wealth of info and help from us on here, so SOL you deffo arent.
Try remapping the panel buttons now - go into factory settings (password 126 or m123456), go to the tab for remapping and see.
Eonon ? Lol, they know F all about the units that they resell, good luck with that !
Cant see what the turn signal sounds have to do with your unit.
Click to expand...
Click to collapse
The turn signal and warning chime sounds in my car are generated from the head-unit. With the stock radio, the CANBUS interface in internal and those sounds come out of the cars speakers (and sound very good). But with these MTCE head-units, they give you an exteral CANBUS module, which allows the steering-wheels keys to work (and from what I've read can't be changed on these GM-specific units?) and they also actually generate the turn-signal and warning-chime sounds, which they play through a little "stick on" speaker (instead of through the car speakers). However, the sounds that the CANBUS module generates are absolutely horrible (it's almost laughable how bad they are) - and I've read that it's not the external speaker that is the problem - it's the CANBUS module itself that is generating the horrible sounds - so there is no way to fix it that I'm aware of - unless I can get a different, higher-quality CANBUS module that works with these units.
For what it's worth, I have a GM-specific unit (the Eonon model # is GA9180A if you wanted to actually see it and what it comes with). Like I said, I've also read on these forums that the steering-wheel keys are preset and cannot be changed - unless there is some hack to do it (the normal method to map the steering wheel keys apparently doesn't work on these units). But again, I'm still crawling and searching through all of these threads, so I'm just going by what I've read - not from actual experience. Maybe I missed it, but I've yet to find a stock WWW MCU file the same or newer than mine (2.85). The problem with going with an older version is that you know that there were isuses that were fixed, so it seems silly to go backwards (or risk having to go backwards). This may seem silly to you, but to me, being that I'm still a "noob" with these radios, I just don't feel comfortable moving ahead with major "mods" until I know I can get back to where I started. Besides, I still have plenty to read and learn and don't even have the unit installed in-car yet (still testing "on the bench" other than a quick in-car test yersterday), so I'm not in a huge hurry.
jtrosky said:
The turn signal and warning chime sounds in my car are generated from the head-unit. With the stock radio, the CANBUS interface in internal and those sounds come out of the cars speakers (and sound very good). But with these MTCE head-units, they give you an exteral CANBUS module, which allows the steering-wheels keys to work (and from what I've read can't be changed on these GM-specific units?) and they also actually generate the turn-signal and warning-chime sounds, which they play through a little "stick on" speaker (instead of through the car speakers). However, the sounds that the CANBUS module generates are absolutely horrible (it's almost laughable how bad they are) - and I've read that it's not the external speaker that is the problem - it's the CANBUS module itself that is generating the horrible sounds - so there is no way to fix it that I'm aware of - unless I can get a different, higher-quality CANBUS module that works with these units.
Click to expand...
Click to collapse
Right, a friend of mine recently installed a unit in his (GM) Opel Astra, it came with a speaker and we wondered what it was, although he hasnt said that any sounds are different after installing it. In factory settings you can see a list of CAN Bus box manufacturers, one from another manufacturer may sound different. Any OEM MTCD/E or indeed any retro fit head unit will come with a CAN Bus box because modern cars use CAN Bus. Few have the external speaker thing though as usually the car generates the noise. As I keep saying the SWC CAN BE CHANGED !!
jtrosky said:
For what it's worth, I have a GM-specific unit (the Eonon model # is GA9180A if you wanted to actually see it and what it comes with). Like I said, I've also read on these forums that the steering-wheel keys are preset and cannot be changed - unless there is some hack to do it (the normal method to map the steering wheel keys apparently doesn't work on these units). But again, I'm still crawling and searching through all of these threads, so I'm just going by what I've read - not from actual experience. Maybe I missed it, but I've yet to find a stock WWW MCU file the same or newer than mine (2.85). The problem with going with an older version is that you know that there were isuses that were fixed, so it seems silly to go backwards (or risk having to go backwards). This may seem silly to you, but to me, being that I'm still a "noob" with these radios, I just don't feel comfortable moving ahead with major "mods" until I know I can get back to where I started. Besides, I still have plenty to read and learn and don't even have the unit installed in-car yet (still testing "on the bench" other than a quick in-car test yersterday), so I'm not in a huge hurry.
Click to expand...
Click to collapse
You dont have an Eonon unit, there are no Eonon units, Eonon are a seller not a manufacturer, they buy from the manufacturer and sell as their own, "GA9180A" is a number made up by Eonon. Your unit is a Klyde unit, its made by Shenzhen Klyde, as we ve discussed WWW MCUs are the same as Klyde (KLD) MCUs. For the 4th time - the SWC CAN BE CHANGED !! I ve also told you how to remap the panel buttons, so can try it and then use a KLD MCU, but you dont seem to have tried it. I know youre a noob, I have 5 years experience with these units and I ve given you my advice, its up to you whether you take it.
Related
Hey there devs. I just fixed A2DP for VanillaEclair, and I have to share this. Now we can all provide full-featured AOSP-roms, so good luck with tweaking your kernels!
Apparently the solution was simplier than we all thought. We had a missing bluetooth firmware file. Put this to /system/etc/firmware and you'll get A2DP working properly. I got this idea from Darchstar, while I was looking at the firmware file in his rom. Damn... we could've fixed this months ago! So... enjoy and let the fun begin!
PS: unzip this, of course...
Ah, you little bugger You beat me to it.
I actually saw this yesterday while trying to pull proprietary files to compile Cyanogen's Hero port, and noticed that this exact file was missing from my phone. I didn't take too much notice of it until I realized what 'brf' could stand for (Bluetooth Radio Firmware). Was just busy experimenting around this morning
Anyway, well done on the fix - you've made a lot of AOSP lovers happy Might I suggest that you possibly look for further missing files that may solve some other hardware bugs (maybe trackball LED?). I'll see what I find missing today in the ROM.
Mr P.
solved yesterday ....
You've ported Darchstar's ROM, eh? Damn file, this could have been solved for ages. But it's good to have it now anyway.
cheer for you
missing firmware? I had a feeling the problem would be very simple
gonna try this on aHero .. thanks man
RaduG said:
You've ported Darchstar's ROM, eh? Damn file, this could have been solved for ages. But it's good to have it now anyway.
Click to expand...
Click to collapse
but what I think is not enough in some cases, I also worked on the driver liba2dp
The firmware file itself fixes the issue. Nothing else is required.
great! it works! thx
RaduG said:
The firmware file itself fixes the issue. Nothing else is required.
Click to expand...
Click to collapse
I have not had a chance to test it with my edits, though I now also works on bluetooth transfer after work on liba2dp
Now we have it sticky. Thanks Fallen Spartan!
robin04 said:
but what I think is not enough in some cases, I also worked on the driver liba2dp
Click to expand...
Click to collapse
One thing to keep in mind: although the term A2DP is thrown around a lot when talking about bluetooth audio, A2DP has been working fine for a while now. A2DP is the bluetooth profile for high quality uni-directional stereo sound. HFP and HSP are the profiles that allow you to actually talk to someone on a call.
en.wikipedia.org/wiki/Bluetooth_profile
It doesn't make much of a difference when conversing with others on the forums, but if you are actually diving into code it makes a huge difference.
This is ignoring the fact that the problem could have been bluetooth not switching away from A2DP properly or some other such problem, but that didn't seem to be the case because headsets that don't support A2DP still did not work right. This is also assuming that the bluetooth stack in these devices don't depend on A2DP code for all audio over bluetooth as I have not looked at much of the code.
If you already know this, then sorry for the post, but if you didn't, it might save you many hours of banging your head against the wall. On the other hand, if you know for certain that the A2DP code is used when making a call, I'd like to know that as well so I don't get frustrated figuring out how it all ties together.
Derek
Nebvin said:
One thing to keep in mind: although the term A2DP is thrown around a lot when talking about bluetooth audio, A2DP has been working fine for a while now. A2DP is the bluetooth profile for high quality uni-directional stereo sound. HFP and HSP are the profiles that allow you to actually talk to someone on a call.
en.wikipedia.org/wiki/Bluetooth_profile
It doesn't make much of a difference when conversing with others on the forums, but if you are actually diving into code it makes a huge difference.
This is ignoring the fact that the problem could have been bluetooth not switching away from A2DP properly or some other such problem, but that didn't seem to be the case because headsets that don't support A2DP still did not work right. This is also assuming that the bluetooth stack in these devices don't depend on A2DP code for all audio over bluetooth as I have not looked at much of the code.
If you already know this, then sorry for the post, but if you didn't, it might save you many hours of banging your head against the wall. On the other hand, if you know for certain that the A2DP code is used when making a call, I'd like to know that as well so I don't get frustrated figuring out how it all ties together.
Derek
Click to expand...
Click to collapse
I'm not banging my head. mine is the first rom that works on bluetooth audio.
However, as I wrote in the post, in some cases may be associated with
A2DP, in fact, I added the firmware missing
Regards,
robin04
robin04 said:
I'm not banging my head. mine is the first rom that works on bluetooth audio.
However, as I wrote in the post, in some cases may be associated with
A2DP, in fact, I added the firmware missing
Regards,
robin04
Click to expand...
Click to collapse
Like I said, if you already know all of that, then sorry for posting it. There are many on these forums that don't know the difference though, so maybe it will help them. Most headsets don't even support A2DP, my Jawbone Icon only recently got support for it (yay!).
I currently use your rom as I need one with a BFS kernel. The Audible beta app runs with barely any stuttering with it, whereas those with higher end devices are complaining about the poor performance. Thanks!
Derek
What's the point in saying you have fixed it first if you didn't even bother to share? Many things appeared in my ROM for the first time, but I didn't even mention it. We both went out on kicking some guy's ass because he wasn't helping the community, but it seems that you didn't have that in mind either.
Anyway... now everything works in the Vanilla ROMs and that's good.
RaduG said:
What's the point in saying you have fixed it first if you didn't even bother to share? Many things appeared in my ROM for the first time, but I didn't even mention it. We both went out on kicking some guy's ass because he wasn't helping the community, but it seems that you didn't have that in mind either.
Anyway... now everything works in the Vanilla ROMs and that's good.
Click to expand...
Click to collapse
I've simple answered nebvin ....
I do not understand why you have to start a war for anything.
I was going to share (you ask xenoside) but have not had time to make a package to flash.
collect information before judging.
Regards,
robin04
I knew it! I knew it! I knew it! Why did I not follow my instincts on this! I saw all the other ROMs from the G1 area and they had this file. But I should have realized it!
RaduG what's the difference between this and brf6300.bin? Do we need both?
I don't think we need brf6300.bin. Here's the difference:
BRF6300
The BlueLink 5.0 platform from TI is a highly integrated, digital CMOS, single-chip solution supporting Bluetooth® Specification v2.0 and all software needed for Bluetooth operation.
Click to expand...
Click to collapse
BRF6350
The BlueLink 6.0 platform from TI,BRF6350, integrated device includes Bluetooth baseband, RF transceiver, ARM7TDMI®, memory (ROM and RAM), power management and an FM receiver.
Click to expand...
Click to collapse
So these are two different chips, and we have only one inside our heros. What's curious is the fact that the taiwan 2.1 ROM only included BRF6300 firmware and A2DP works with that. One more interesting think is that apparently BRF6350 includes an FM reciever, so in theory we might be able to get the radio functionality.
I see. Thanks!
First off I'd like to say thanks for this great forum. I've used it many times over the years but just recently registered. I've never really had anything substantial to add (still don't). In the past I've had a Photon and HTC One M7, both from Sprint. I never really had the urge to mess with them at all. I recently bought a Note 4 and I decided to root it. I'm more of a computer person, building and customizing but never got into messing with phones.
With that said I'm in need of some help so I decided to register. Not sure if I have much to add at this point to become a contributing member so if anybody is hesitant to help I completely understand. I've been a noob on many other forums, and have also seen noobs come and go. So if anybody can help, that's great and I thank you ahead of time. If not, that's OK too.
I was completely torn between the new LG, an HTC One M9 and the Note 4........ I even considered the Nexus. The audio quality of the M7 that I had was and still is better than any other non-HTC phone on the market and it was really tough to convince myself to get something different. I wanted a big screen with great hardware. The Note 4 had all that except for the audio. The audio, speakers and headphone quality absolutely suck. I am terribly disappointed. I was going to see if HTC was going to release a version with a bigger display, I saw that it is a toned down version. If HTC made a 5.5-5.7" maxed out version like the smaller M9 I would have gotten it.
Now, I've rooted this phone and I've gone through all the steps of installing V4A and no matter what I do it does not function at all. The problem I see is that my phone upgraded to Lollipop. In order to properly install V4A the SELinux mode needs to be set to permissive. There was an app (I forget the name of it offhand) that could change the mode, unfortunately it is not compatible with Lollipop. Without changing the mode to permissive I cannot properly install V4A.
I've searched through this forum a couple times over and can't seem to find what I'm looking for. Is there another way to change this mode? What about recommendations for one of the custom ROM's that has V4A in it? I'm really open to any suggestions. I'm really fed up with this phone telling me what volume level is enough. I use this phone for music all the time and the stock equalizer automatically cuts the volume down to the highest equalizer setting. I can hear the difference, when using Spotify if I skip to the next song the stock equalizer (SoundAlive) takes a split second to kick in and you can hear how it should sound without SoundAlive. For all this Note 4 has, I'm really starting to regret getting this over the M9. It would be a great phone if I can get some volume back as well as some decent sound quality.
JJFIVEOH said:
First off I'd like to say thanks for this great forum. I've used it many times over the years but just recently registered. I've never really had anything substantial to add (still don't). In the past I've had a Photon and HTC One M7, both from Sprint. I never really had the urge to mess with them at all. I recently bought a Note 4 and I decided to root it. I'm more of a computer person, building and customizing but never got into messing with phones.
With that said I'm in need of some help so I decided to register. Not sure if I have much to add at this point to become a contributing member so if anybody is hesitant to help I completely understand. I've been a noob on many other forums, and have also seen noobs come and go. So if anybody can help, that's great and I thank you ahead of time. If not, that's OK too.
I was completely torn between the new LG, an HTC One M9 and the Note 4........ I even considered the Nexus. The audio quality of the M7 that I had was and still is better than any other non-HTC phone on the market and it was really tough to convince myself to get something different. I wanted a big screen with great hardware. The Note 4 had all that except for the audio. The audio, speakers and headphone quality absolutely suck. I am terribly disappointed. I was going to see if HTC was going to release a version with a bigger display, I saw that it is a toned down version. If HTC made a 5.5-5.7" maxed out version like the smaller M9 I would have gotten it.
Now, I've rooted this phone and I've gone through all the steps of installing V4A and no matter what I do it does not function at all. The problem I see is that my phone upgraded to Lollipop. In order to properly install V4A the SELinux mode needs to be set to permissive. There was an app (I forget the name of it offhand) that could change the mode, unfortunately it is not compatible with Lollipop. Without changing the mode to permissive I cannot properly install V4A.
I've searched through this forum a couple times over and can't seem to find what I'm looking for. Is there another way to change this mode? What about recommendations for one of the custom ROM's that has V4A in it? I'm really open to any suggestions. I'm really fed up with this phone telling me what volume level is enough. I use this phone for music all the time and the stock equalizer automatically cuts the volume down to the highest equalizer setting. I can hear the difference, when using Spotify if I skip to the next song the stock equalizer (SoundAlive) takes a split second to kick in and you can hear how it should sound without SoundAlive. For all this Note 4 has, I'm really starting to regret getting this over the M9. It would be a great phone if I can get some volume back as well as some decent sound quality.
Click to expand...
Click to collapse
You need custom kernel to set mode from enforced to permissive... or google there is away to enable V4A to work with stock kernel that involve romtool.
This phone imo is top notch in all areas but I agree with you on the audio quality, stock music player that is. I use PowerAmp and all of that changes, even through the phones tiny speaker. My suggestion is to revert to stock and simply install the app if you're just looking to improve audio quality. Just my 2 cents.
https://play.google.com/store/apps/details?id=com.maxmpz.audioplayer
patrick_1 said:
This phone imo is top notch in all areas but I agree with you on the audio quality, stock music player that is. I use PowerAmp and all of that changes, even through the phones tiny speaker. My suggestion is to revert to stock and simply install the app if you're just looking to improve audio quality. Just my 2 cents.
Click to expand...
Click to collapse
I've heard many good things about PowerAmp but as far as I know that's only applicable to downloaded songs. It doesn't work with Spotify.
JJFIVEOH said:
I've heard many good things about PowerAmp but as far as I know that's only applicable to downloaded songs. It doesn't work with Spotify.
Click to expand...
Click to collapse
Yeah that's true. Sorry
I'd suggest using the Emotion r14 kernel. That will get you permissive and a much snappier phone as well as having tweaks specific to sound. It supports Faux 123 sound on top of everything else. You should find a link to the kernel in the original android development area.
---------- Post added at 01:18 AM ---------- Previous post was at 01:13 AM ----------
Sorry the Emotion kernel can be found here.
http://forum.xda-developers.com/showthread.php?t=2990557
kenjesse said:
I'd suggest using the Emotion r14 kernel. That will get you permissive and a much snappier phone as well as having tweaks specific to sound. It supports Faux 123 sound on top of everything else. You should find a link to the kernel in the original android development area.
---------- Post added at 01:18 AM ---------- Previous post was at 01:13 AM ----------
Sorry the Emotion kernel can be found here.
http://forum.xda-developers.com/showthread.php?t=2990557
Click to expand...
Click to collapse
Thank you for the recommendation. I'll check it out. If I can get the permissive setting I shouldn't have any issues getting V4A installed. Everything else that comes with that kernel is an added bonus.
OK, that kernel worked great! I was able to install V4A almost flawlessly. No disrespect to any of the equalizer apps out there but V4A is by far the best audio control I've used. I've been banging my head against the wall trying to get this installed. That kernel did make the phone a little "snappier" as you put it. I haven't had a chance to mess with Synapse, I might just leave well enough alone as it's now working he way I want. Thanks again.
im just curious do you still have data after flashing that kernal?
Do I still have data? Not sure what you mean.
Hello to all.
Can someone help me with the tunein radio not working with viper audio?
I changed my phone to permissive, and added the 2 zips somebody uploaded that changed the build prop. But i still cannot get viper and tunein to work together. Maven Pro audio works great as does iheart with viper.
Thank you in advance.
Blessings
I'm not a subscriber of Tunein, I wish I could help ya. Does V4A work with other audio services?
JJFIVEOH said:
I'm not a subscriber of Tunein, I wish I could help ya. Does V4A work with other audio services?
Click to expand...
Click to collapse
Yes. I heart and maven pro music player works great with viper.
Thank you for your reply.
Blessings
ulremember said:
Yes. I heart and maven pro music player works great with viper.
Thank you for your reply.
Blessings
Click to expand...
Click to collapse
According to this it's an issue with Tunein. It is a little old so not sure if there is a different issue since then, so take it for what it's worth.
http://forum.xda-developers.com/showthread.php?t=2456073&page=24
Hey guys,
First of all let me thank you for taking the time to read my question. I tried to prevent this post but as I really don`t like bricking my unit I felt like I had to confirm my suspicions, couldn`t confirm this myself as the search button has not been proven to be my friend
I have a GS (Hot Audio) unit 800 * 480 RK3066 running on a rooted Android 4.4.2 at the moment and wanted to upgrade this to 4.4.4 however since my last visit to this wonderful forum a lot a changed and given me a case of information overload. Therefor I have the following questions.
- It is not mandatory to include the MCU.img in the update package
- Otherwise I can take one of these: http://forum.xda-developers.com/showthread.php?t=3246370 (Top 4)
- I can use any update.img as long as the resolution and chip number is correct. In other words there is no need anymore to look at the model KLD/GS/KGL (This one for example: http://huifei.fs-fileserver.de/content/firmware/KK 4.4.4 Dual core Coudu Rooted /KLD/800x480/)
If you would be able to relieve me of these doubts I would be very grateful.
Thank you all again :good:
No one will shoot you. Ignore the grumps.
You are correct on all three points as long as you are sure of your head unit's make/details which sounds like you are. I know you used it for an example but in your third point you linked to Coudu's ROMs which are way outdated, stick to Malaysk's as they are superb.
Just be aware that there might be some settings (thinking of the configurable sleep timer delay) in newer ROMs that require an updated MCU so something like that won't work if your MCU is too old. But I don't know how applicable this is to you as I don't know what MCU revision you have for your GS. You can always update your MCU at a later time by itself if need be, no biggie.
Well a small update I just finished the install and to be honest I wished I would have done it much, much earlier Malasyk has done some incredible work
Thx again for your help again :good:
Ok so just bought a new car head unit, the one stated above to save some space and time, it's on Android 4.4 AC8xx, and rooted. I've read the forums over and over and have seen that I can adb over network to the deck and install twrp, though I'm not sure if it's comparable with my unit, I would love to remove a lot of the crap it came with except for the radio app. It would be really cool to have a custom rom if any exists. I'm not sure if anyone even visits this thread but if you do help would be amazing ??
ne0ns4l4m4nder said:
Ok so just bought a new car head unit, the one stated above to save some space and time, it's on Android 4.4 AC8xx, and rooted. I've read the forums over and over and have seen that I can adb over network to the deck and install twrp, though I'm not sure if it's comparable with my unit, I would love to remove a lot of the crap it came with except for the radio app. It would be really cool to have a custom rom if any exists. I'm not sure if anyone even visits this thread but if you do help would be amazing
Click to expand...
Click to collapse
You need to go into settings and look at the about machine or something like that.
It has to say MTCB with some other stuff under MCU Version
If it says something like MTCB-????-V???
??? can be anything
Check it says nothing lol just the kernel version :/
Says MCU v1.0.0_2017.6.21.4.52
ne0ns4l4m4nder said:
Says MCU v1.0.0_2017.6.21.4.52
Click to expand...
Click to collapse
Sorry, none of these roms will work. I'm not sure if their is a listing here. Better check in the main area for the MCU info.
Sorry for long title, missing question mark (it didn't fit) and my somewhat limited english.
So, for example lenovo stops upgrade, are there anyone tried to make exact copy (what it could be) of oreo? No other "trinkets" added. I mean not any of those suggestions added, what users asks on the thread. Not a single feature added in the phone menu. So, point me one if there is, please.
That would be a hit, I think. At least I would install one to my dad's phone, this time Nexus because he asks for that (and even mom's phone Lenovo P2), but if the menus are different its a big no. It WILL confuse them. A lot. So bad they want to go back even old version had bugs they cursed.
---------unrelated rant------
Oh, I really don't mean actual fixes, if those are even possible to fix, because I think it is in the hardware. Bluetooth sound from headphones is so awful its unuseable. I have two Lenovo P2's, so I know what I'm talking about. One must be deaf if not hear that. Shamefull. In this time and age, when bluetooth headphones are standard. Sound separation is close to mono. Its so bad, I had to buy wired headphones (Marshall has wire+bt 2in1) Uh, actually I use smiley for that. ...let me see if I find one, that fits..... Here! :cyclops:
Hi, I don't know if I'm allowed to answer but I do it anyway.
I totally get your point but don't understand your consequences from it. If they both upgrade from nougat to oreo, there will be a difference in the menu structure anyway. You just have to keep them the same between the nexus and the p2. So why does it have to be a pure stock rom? why don't you just install the same custom rom, like lineage os, to both phones?
Best regards