by noahl on 3/18/15, 4:29 PM
This appears to actually be an issue with the kernel, which I believe is the same as the kernel in the Android version of the device. Therefore, unless I'm missing something, the title is misleading - this is actually an issue with Mediatek's Linux kernel modifications, which applies to Android, Ubuntu, and anyone else who tries to make a Linux-based phone with Mediatek hardware using Mediatek's official kernel patches.
by petersabaini on 3/18/15, 8:36 PM
by bjackman on 3/18/15, 4:11 PM
This is surely more of a Mediatek/BQ issue than an Ubuntu one. Regardless, Canonical are supposed to be on the side of software Freedom, and it's on their shoulders to make Mediatek sort this out.
by userbinator on 3/18/15, 4:06 PM
Mediatek is known for being "gongkai" with respect to licensing etc., as do the majority of Asian companies. A good explanation of that ecosystem is here:
http://www.bunniestudios.com/blog/?p=4297
You can find datasheets, schematics, and various other bits of info on their chipsets in various Chinese sites, but if you ask MTK they'll never officially give them to you.
by azinman2 on 3/18/15, 7:35 PM
This is the reason you won't buy an Ubuntu phone? Really?
Wouldn't be high on my priority list, let alone a "normal" user.
by delonia on 3/18/15, 5:16 PM
The author of Mer is unhappy with Ubuntu and this looks more like an attack than a constructive post.
MediaTek is now contributing directly to the Linux kernel. Those header files are from 2010. It's just an issue of updating them.
by aaddaarrsshh on 3/18/15, 4:21 PM
Well that's sad, Ubuntu phone was the only good thing. Android is boring.
by worklogin on 3/18/15, 3:53 PM
That is a truly awful blog layout. So much whitespace, and what appears to be around a 40 character line limit. I see the point is made once the license is pasted in a few times, but still frustrating.
For all that, the post has a valid question about how an open phone can have such messages in its source code.