[Android Head-Units] kaween:
No of course it's not. It's plain old api16. This whole faux labeling of the OS is pretty ridiculous and smells like borderline fraud. Strike that. It IS fraud.

If you "fast tap" the Android version entry in the settings menu, it will respond with a jelly bean instead of the big red "K" a real 4.4 would show you, so they're not even TRY to hide the android version number is complete bogus.

[/COLOR]

You don't have to modify anything anymore in Wavesink to get it working with the AN21 today.

I reported the bad behavior of Wavesink on the AN21-U and discribed the type of problem (sound breakup, both on FM, DAB and DAB+). Two days later, the programmer got in touch with me saying he'd look into it in the weekend and sure enough, he produced a new version which I tested : the new version is NOT flawless (it has produced a new issue which the old version did not have - but this MAY be connected to the tests I've done, and it ONLY happens at the first launch of the app after powerup, so it's bound to be some kind of initialisation error. Basically, first time round, Wavesink shuts down. If you relaunch it, it will continu to work correctly from that moment on.

Wavesink still needs quite some work to be a full internal FM-replacement, but compared to the other things I've seen or tried, it's usable now. The biggest problem is the lack of a car-friendly UI : Wavesink Plus (the Free version does not have it I think) sports a nice looking "Radio Dial"-type of UI, but you have to choose your station by swiping the dial. Not ideal when driving your car ! (look at screenshot of my previous post)

There's no buttons to go to previous/next station yet. If the programmer adds that, and makes these buttons behave correctly with standard android "Next/Prev" hardware buttons, the biggest issue with Wavesink for Car Use is solved.

I THOUGHT the software had issues with Radiotext in DAB(+), but I'm now pretty much convinced this has something to do with the way the Flemish DAB radio stations provide RadioText info : it turns out that NONE of the Flemish DAB stations provide Radiotext data that can be correctly decoded by Wavesink, but oddly enough all the FRENCH-speaking Belgian DAB transmissions have 100% correctly decoded DAB RAdiotext available. So unless you live in the Flemish part of Belgium I think most people will see no problems with DAB(+) Radiotext.

Sound is perfect (depending on the bitrate and codec of the transmission of course). DAB+ is working, the software makes no difference between DAB, DAB+ or FM in the Car-UI : they're all available for reception without limitation, and as the sound passes through the Android OS, V4A does help making the radio sound better, unlike the situation with the internal FM tuner.

You can use almost ANY DVB-T + FM + DAB(+) stick you want, as long as it is build around the RTL2832U + FC0013 Tuner hardware. My Chinese stick costed 14€ or so. Just look for the RTL283U+FC0013 and you should be good. I think Michael (Wavesink's programmer) proposes to use a Logilink V000018.

The stick I'm using is a EzCAP EZTV668 RTL2832U/FC0013 . The DVB-T part can not be used at this time.

The thing feels (and IS) very much a work in progress, certainly the UI needs work.

Also, there's still no TA function, not in FM mode, not in DAB(+) mode. If it turns out the launch issue is not connected to my test setup, that too should be sorted out.

But is it Usable in its current state ? Yes it is.

I've written a mail to the programmer, offering him support if he'd need it to make this piece of software more car-friendly : if he can be pursuaded that there's really a market for this kind of use this thing could become the best solution for people looking for cheap DAB(+) solutions in android car radio's. Because other stuff (like Dension, DABmotion) all feel and work very much like rather expensive "stopgap" solutions.