[Android Head-Units] kaween:
There are quite a lot of people complaining about this storage location issue, strangly enough I've never had any issues with it.

Try Rocketplayer : It will try to scan your device quite aggresively upon launch or rescan and see if it makes any difference.

I can't really comment on your CAN problem as I don't have canbus for radio on my car but I wouldn't expect the Canbus thing to work over just ONE wire ? Hopefully another user can chime in.

All MST's are really 4.1 no matter what the seller says. Even the so-called 4.2 firmwares are 4.1's in reality and as I said earlier, I don't think that will ever be updated : the firmware updates I've seen so far mainly adress bugfixes. I'm running 2.8.8 myself, and it behaves pretty well : I don't detect real bugs in it except for these 2 :

1) Radio Text part of the RDS system works ... more or less. Sometimes it provides the complete and correct info, sometimes it's blank. When I use my cell phone on the same radio station, I can see the correct Radio Text info right away. It SEEMS the issue is connected to the way the Radio app interpretes "scrolling Radio Text".

2) Speed Dependant Volume Control works, but it does odd things when the system must correct the volume of for example the Radio in the background and the Voice Guidance of *all* Navi software I've tested so far : it's like the Radio gets priority, and given the voice command is long enough, the radio will apply the speed dependant voice change "during the voice guidance instruction". Meaning, it will start speaking pretty silent, and halfway the instruction it will blast my ears off. Switching off the SDVC function solves this issue, but of course you loose the SDVC. :(

---------- Post added at 12:58 PM ---------- Previous post was at 12:31 PM ----------

Wow. Now actually over here (Europe), in terms of court ect ect we're in the same boat, but most sellers have enough decency to help their customers without having to resort to other measures.

Many sellers are very sensitive to bad press or bad feedback on their forums/sites as they know that disgrunted buyers will simply take their future business elsewhere.

The issue is this :

1) if you want to infuse a software problem that is reversable, a smarter seller will be able to reverse it too so you end right back where you started.

2) "software under waranty" ??? What ? That's the world in reverse ? If there's one thing they must do in waranty it really should be hardware ! Those guys are really dishonest and I pitty the customers that have to deal with such sellers.

3) if you think the seller is not able to solve something like a wrong mcu, why bother ? Change the hardware binding of the buttons so they don't work correctly anymore or are binded to the wrong actions. If those guys can't solve a wrong MCU, they won't be able to solve such a thing either.

4) but if you still want to go the mcu route : look at Mike's file repository and hunt down your correct mcu as backup. Then take a "bad mcu" with a different hardware code (for example if you have a "1", install a "7") : it will cause wrong behavior in terms of non-working EQ settings (bad sound) or comparable issues like wrong behaviour of the hardware buttons).

5) another trick I used in the old days .... transparant sticky tape. For example, carefully open the front of the unit to have access to the big flex that connects the screen to the mainboard. Take out one side of the flex, and carefully cover the silver conductors with tape. Cut the tape so it covers that part of the flex only and doesn't stick out anywhere : when you do that in a clean manner it will be visually very difficult to spot unless you know what you're looking for, yet YOU can easely remove the sticky tape and restore full functionality if need be.

I understand your situation, and whish you best of luck. Sad to hear that there are always some sellers who lack common decency and are only in it for the quick buck. :(