yashsingh1/xdaforums huggingface dataset:
[Ornate TrueSmart] CyberianIce:
I repeat once again (and for last time): they do not charge for sources; they charge for technical documentation/support, and sources you got for free if you buy their product. How many of us bought anything from them? This whole thread is backwash of trolling OEM company and frustrated users.
[Ornate TrueSmart] Lokifish Marz:
Directly from MTK. In short, we don't care if you buy our stuff you are still not getting source unless you agree to our license agreement.
[Ornate TrueSmart] AndreiLux:
You're implying MediaTek themselves do not have the license, in which case they technically don't because they are breaching it due to providing this compile service - but you're trying to argue with a chicken-and-egg logic.

And no I'm not mistaken, you can sell it however you want: http://www.gnu.org/philosophy/selling.html

Let me remind you who wrote this license:

That's what I said, you sue the OEM, not MediaTek. It's up to the OEM to sue MediaTek.
[Ornate TrueSmart] saratoga2:
Link to your documentation supporting this claim or retract it.

You're missing the point. If Verizon tried to carry their products, Qualcomm could simply request that their shipments be denied entry into the US because they contained stolen software. At this point MT would have to show that their licenses are in order. They can't actually do this, which is why you can't get MT stuff in countries that respect software copyrights. You're essentially saying that its the OEM who would technically be at fault, but it wouldn't really matter who is at fault when the shipment of MT parts was crushed and dumped in a landfill.

And then the OEM turns around and sues MediaTek for selling them illicit software and getting their phones crushed.
[Ornate TrueSmart] AndreiLux:
The software does not become illicit because MT doesn't release sources, it's still GPL.

Basically this whole discussion is retarded because:

1) Supposedly MediaTek doesn't release sources to customers who don't buy they "tech/documentation/support" package.

2) If that is the case, then it means there are companies who buy these chips without support? Which is an insane notion in itself.
[Ornate TrueSmart] superdragonpt:
Actually Mediatek will never released the FULL Source Code, Vendors actually can't do much about that either.

You'll be lucky if your vendor publish the

full and buildable

Kernel Source code, and even the few vendors that did that, not all published the full kernel sourcecode (they usually delete the kernel/Mediatek and ..Mediatek dirs) making that kernel source pretty useless.

As an example :

V970M.kernel.tar.gz - 102.52 MB

This is the kind of kernel source they published (this one from my zte v970 device)

Btw

: It took (me and our zte v970 FB Group) , many months of spamming zte to release the kernel source.

And all we got was an old ICS and incompleted source code.

My new MTK device Wiko Darkmoon, haves the full kernel sourcecode released:

http://wikogeek.com/

Wiko has been one of the very few MTK vendors, complying with the GPL.

BUT, even with the full kernel source code, you will need to "re-learn" to compile an kernel, MTK code is weird and needs an few "hacks" to properly compile.

- Toolchain, can't be higher than 4.6.x

- The zImage usually needs an "header" patch for it to boot, and so on...

Regards
[Ornate TrueSmart] CyberianIce:
You are not an expert of international law and patent rights didn't You?

In some point you are in right, but there is flaw in your logic: Umeox/Omate is not FCC certified for selling products and, so it is hard to expect that they would behave like Verzion on market. Umeox/Omate are absent from US market for good reason (like this i.e). People why bought their products should search for sing on rear side or on the box before taking complaint about breaking their rights.

On the other side, we in Europe have CE (FCC equivalent), and as ALU (Alcatel-Lucent) is now ONLY certified MTK OEM, they can sell products with MTK but they provided us with source codes, unlike Umeox/Omate. For my knowledge ALU is only firm on EU which have legalized selling of MTK products. And they are providing source codes for free.

So I don't get it? Why attack on MTK? Why not on Umeox/Omate and other OEMs which dont have licence for selling GSM equipment at all? How can you expect justice from firm which don't have approval for what they doing? And how you expect from MTK to take responsibility for their actions? You can't be serious.

Take a look at this chain of production (in my case):

MTK (System-On-Chip) -> TCL (Board) - TCT (Device) -> ALU (OEM Branding) -> TELENOR (Operator Rebranding) -> End User.

You can't jump from end of the chain to top because there are many hoops between.
[Ornate TrueSmart] Lokifish Marz:
Omate doesn't have FCC certification. News to me.

So here's how this went;

Omate, we need source. Omate doesn't have source, go talk to Umeox.

OK. Umeox, we need source. Umeox doesn't have it, go talk to MTK.

OK. MTK, we need source. It is against company policy to release source to the public. Only partners that have agreed to our licensing terms can have access to source. And Umeox/Omate have no license agreement with us.

Please keep in mind than Adam Outler, myself and a number of other have the email chain in which all this went down.
[Ornate TrueSmart] CyberianIce:
Sorry, my fail. I though they don't have, but I used to look at this list:

https://apps.fcc.gov/oetcf/eas/repo...ame=N&application_id=463819&fcc_id=2ABF5-OTS1
[Ornate TrueSmart] AndreiLux:
From what I read so far is that basically Omate/Umeox don't have a distribution license and this compile server basically sounds like an evaluation method for companies before they go sign a license with MediaTek - in which case it's totally legal for MediaTek to do such a thing under GPL.
[Ornate TrueSmart] Lokifish Marz:
And does that apply to devices that are sold via retail channels? It's not just the TS here but the entire x201 platform.
[Ornate TrueSmart] AndreiLux:
Clearly they're in breach. The point is I'm rather pointing the fingers at the Kickstarter company and the Chinese company rather than the global semiconductor company.
[Ornate TrueSmart] Lokifish Marz:
Don't get me wrong, they are all at fault here in one way or another.

About that "Kickstarter company", it's actually a spin off company of the original Omate design department of Umeox with the majority of the start up capital coming from Umeox.

There is another possibility that Umeox/Omate is lying and has source but after talking with their engineers on multiple occasions I find it hard to believe they even know how to compile seeing I had to educate them on what chown was. (there's emails for that too)

EDIT

I have no emails to back this up but;
[Ornate TrueSmart] jumoog:
Before i buying a device im checking their source background.

What do you expect if you buy rebranded low price stuff?

I bet you dont even have a warrenty and you want their kernel code... Btw if you download Kernel sources for sgs 4 you cant compile it too. Because not all parts of their kernel are under gpl (good example is nvidia gpu driver)

If you look @ leaked kernel sources you will see that their code is not under gpl
[Ornate TrueSmart] xboxfanj:
It is legal to sell GPL software, however, the price of source may not exceed the price of the binary.

Straight from their FAQ: Does the GPL allow me to charge a fee for downloading the program from my site?

Yes. You can charge any fee you wish for distributing a copy of the program. If you distribute binaries by download, you must provide “equivalent access” to download the source—therefore, the fee to download source may not be greater than the fee to download the binary.

Technically, the fee for the binary could be considered the price of the device, so as long as the price of source does not exceed the price of the device, it seems to me that there is no violation.
[Ornate TrueSmart] superdragonpt:
And is it legal for MTK, to simply put an new licence header on some of the /kernel files ?

Becouse right now their source is an mix of:

apache + GPL license + proprietary source, its an mess !

Regards
[Ornate TrueSmart] xboxfanj:
I would imagine not. Their entire "BSP" is a total mess. It's weird how they try to get around giving source, but a lot of this source isn't required such as the HAL code.
[Ornate TrueSmart] xboxfanj:
NVidia gets around it by using external modules and not using GPL symbols.

SGS4 kernel should compile; could be a compiler issue or one of the random ones that comes up sporadically (such as headers (#include <linux/header.h> fails so you have to #include "../../include/linux/header.h" instead)).
[Ornate TrueSmart] Lokifish Marz:
I'm really not trying to put every piece of info we have out there but here's some more info.

MTK is precompiling and sending it to Umeox

Umeox adds their APKs and edits then repacks

The edited repack is sent to the factory to be flashed.

MTK does not give Umeox source code at any point as Umeox has not paid for the license nor has Umeox agreed to the NDA that accompanies it. So if Umeox pays for the licensing then they are bound by the NDA to not release source.
[Ornate TrueSmart] jumoog:
i'll help you out :D

1.) extract boot.img to get Ramdisk content

2.) from their we can create a Device Tree and can build Android
[Ornate TrueSmart] superdragonpt:
Yes

that isn't new, MTK always force OEM's to sign NDA's.

Lol

Regards
[Ornate TrueSmart] Neuer_User:
If anyone really wants to get source code for the Omate TrueSmart, the only way I can imagine is this:

Go together with FSF and sue Pearl in Germany.

Pearl sells the Omate TrueSmart under a different name with a different casing, but everything else the same. Pearl is big enough to be able to mount a law suit against Umeox, which again would need to go against MediaTek. Pearl is located in Germany and sells also in France, Austria and Switzerland. All those countries have a rather GPL compliant law system.

Without a law suit I don't see much chance to go up the ladder to MediaTek.

So, first thing should be to go and talk to FSF if they would support us against Pearl. If yes, let's go ahead.
[Ornate TrueSmart] dedesuper:
MTK Source Codes

Lokifish you are completely right.

The PCB come already precompiling and the software manufacture just assembling the PCBA and after they making there own adjustments.

I will happy to help all of you and get you the Source Codes but its like fighting to a Wall, it is very hard to get that.

Also dont count that MTK6572 will receive soon an upgrade for 4.3 or 4.4KitKat you are loosing your time on that.

At my side I am fighting to get the source codes also for the MTK6572 because we will have a Low cost smartwatch running on this Chipset.

If I will succeed will be happy to help all of you .....

Best Regards

Damien Douk

A.I Watch Creator

www.aiwatchtech.com
[Ornate TrueSmart] Lokifish Marz:
Pearl also gets their watches from Umeox so it would be Pearl>Umeox>Mediatek, we are already at the Umeox level now (who does not get full source from MTK).
[Ornate TrueSmart] Neuer_User:
I think there is a very BIG difference. Currently 5 independent developers plus Laurent and his small company being owned by Umeox is asking for source from MediaTek.

What I would expect to be much more efficient is: All lawyers of Umeox sueing Mediatek to give source code. Why should they do that? Well, there would only be one valid reason: Because they are sued by some other company (Pearl).

I highly respect your efforts and those of the other participants, but this still remains a request from a few independent developers and a small startup (Omate), which has less than 10 employees and negligible sales. You will never reach anything against MediaTek.

So, climbing up the ladder and ensuring that each step is done with the highest power (sueing), each step will get you more powerful:

From a few independent developers to a multinational (but still small) company Pearl, to a bigger chinese company Umeox and finally towards MediaTek.

This only works if each participant is really threatened by his predecessor. So, this could work, although I do not know how much Pearl can threaten Umeox and Umeox then finally MediaTek. But it is surely more effective that internet petitions or similar.
[Ornate TrueSmart] Lokifish Marz:
[MENTION=2750664]Neuer_User[/MENTION]

Because without source it threatens any carrier contracts that Umeox has and is currently negotiating, additional vendors ordering the device, current vendor contracts. You have to realize that every x201 model is a 10/10 security risk and there are over 50K units waiting to be sold pending contract finalization. This has also already gone to the CEO level at Umeox.

I understand your point of restating the entire process but there are a couple things to consider. It increases the amount of time to get a resolution, leaves a large number of users with one of the most unsecure devices that Dees, Adam, Ryan and myself have ever seen.
[Ornate TrueSmart] dedesuper:
Lokifish Marz,

Take an advice from me and I know well what I am talking about, from UMEOX you will get nothing dont waste your time there.....

Best Regards
[Ornate TrueSmart] Ne0gotenks:
Way to keep things positive....
[Ornate TrueSmart] Ije:
Bottom line.. we take our fight to MTK here in the US and everywhere else on the Internet on every future device that is planned .. Not only do we blast them on the lack of source code but they fact their devices are not secure. We blast not only MTK but any OEM or carrier that plans on selling any equipment with their chips in it. It may very well be late for the TS but we make sure there is hell to pay with negative publicity wherever we can shout it and lets see what happens. If we cant get to MTK, we hit the OEMs and Carriers that use their chip.
[Ornate TrueSmart] superdragonpt:
Dont you love this?

# Copyright Statement:
#
# This software/firmware and related documentation ("MediaTek Software") are
# protected under relevant copyright laws. The information contained herein
# is confidential and proprietary to MediaTek Inc. and/or its licensors.
# Without the prior written permission of MediaTek inc. and/or its licensors,
# any reproduction, modification, use or disclosure of MediaTek Software,
# and information contained herein, in whole or in part, shall be strictly prohibited.
#
# MediaTek Inc. (C) 2010. All rights reserved.
#
# BY OPENING THIS FILE, RECEIVER HEREBY UNEQUIVOCALLY ACKNOWLEDGES AND AGREES
# THAT THE SOFTWARE/FIRMWARE AND ITS DOCUMENTATIONS ("MEDIATEK SOFTWARE")
# RECEIVED FROM MEDIATEK AND/OR ITS REPRESENTATIVES ARE PROVIDED TO RECEIVER ON
# AN "AS-IS" BASIS ONLY. MEDIATEK EXPRESSLY DISCLAIMS ANY AND ALL WARRANTIES,
# EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE IMPLIED WARRANTIES OF
# MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE OR NONINFRINGEMENT.
# NEITHER DOES MEDIATEK PROVIDE ANY WARRANTY WHATSOEVER WITH RESPECT TO THE
# SOFTWARE OF ANY THIRD PARTY WHICH MAY BE USED BY, INCORPORATED IN, OR
# SUPPLIED WITH THE MEDIATEK SOFTWARE, AND RECEIVER AGREES TO LOOK ONLY TO SUCH
# THIRD PARTY FOR ANY WARRANTY CLAIM RELATING THERETO. RECEIVER EXPRESSLY ACKNOWLEDGES
# THAT IT IS RECEIVER'S SOLE RESPONSIBILITY TO OBTAIN FROM ANY THIRD PARTY ALL PROPER LICENSES
# CONTAINED IN MEDIATEK SOFTWARE. MEDIATEK SHALL ALSO NOT BE RESPONSIBLE FOR ANY MEDIATEK
# SOFTWARE RELEASES MADE TO RECEIVER'S SPECIFICATION OR TO CONFORM TO A PARTICULAR
# STANDARD OR OPEN FORUM. RECEIVER'S SOLE AND EXCLUSIVE REMEDY AND MEDIATEK'S ENTIRE AND
# CUMULATIVE LIABILITY WITH RESPECT TO THE MEDIATEK SOFTWARE RELEASED HEREUNDER WILL BE,
# AT MEDIATEK'S OPTION, TO REVISE OR REPLACE THE MEDIATEK SOFTWARE AT ISSUE,
# OR REFUND ANY SOFTWARE LICENSE FEES OR SERVICE CHARGE PAID BY RECEIVER TO
# MEDIATEK FOR SUCH MEDIATEK SOFTWARE AT ISSUE.
#
# The following software/firmware and/or related documentation ("MediaTek Software")
# have been modified by MediaTek Inc. All revisions are subject to any receiver's
# applicable license agreements with MediaTek Inc.

............
[Ornate TrueSmart] Lokifish Marz:
[MENTION=5238428]superdragonpt[/MENTION]

Hasn't the same thing been found in GPL protected files? I remember seeing it months back but can't remember where.
[Ornate TrueSmart] superdragonpt:
Yeap

Check my github

There's plenty of Mediatek Sources there.(if not all ...)

Some self-compiled others from OEMs/custom kernels from friends :)

regards
[Ornate TrueSmart] myphoneuser:
I think that'll work better. Articles like this:

http://www.xda-developers.com/android/have-you-paid-your-linux-kernel-source-license-fee/

will make the difference.
[Ornate TrueSmart] superdragonpt:
Hi

well i was checking my stock kernel dump (from one of my phones) for sub-lens and saw this:

Do you see something strange?

lol
[Ornate TrueSmart] jumoog:
no tun.c is in every kernel just look @ https://git.kernel.org/cgit/linux/k...t/tree/drivers/net/tun.c?id=refs/tags/v3.13.7
[Ornate TrueSmart] superdragonpt:
My bad ;)
[Ornate TrueSmart] :
My Suggestion is to give Umeox a Simple Dead Line for Providing the Kernel Source Code and all other GPL Licensed Stuff like the bootloader.

I have heard the People at Busybox are very good when it comes to GPL Problems.

Try to get BusyBox Developers to Sue Umeox in USA and Germany like Apple did with the Goal to block Sales and Shipment in USA and European Union.

Great would be if you can sue Mediatek together with them for not Cooperating in the deliverment of GPL Licensed code to Umeox and try that way to Block all Sales and Shipments of MediaTek based Devices in USA and Europe.

The only Reason why i buyed the Truesmart was becouse i believed Kernel Rebuilding would be no problem as it was Promised that Sources will be Published. After i Buyed the Omate and realised that it has a MediaTek SoC i knew same **** will happen with disclosure of the Kernel Sources by MediaTek. I Own since Years a Z1 Smart Watch Phone based on the MediaTek MTK 6516 SoC Platform and i am not able to Upgrade the Kernel nor the Android 2.2 Operating System.

The Chinese Company APPSCOM

=> http://www.appscomm.cn/Watch Phone-...tch-ProductDetails/Android Watch Phone-Z1.htm

Provide a GPL Licensed Linux Android Firmware Build on her Website for Download

=> http://www.appscomm.cn/Watch Phone-Android watch-Sports watch-DownLoad.htm

But Fails to delivers the need Sources and are clearly in Breach since Years.

Have Contacted them and did not get one Reply from them till yet even i am a Customer and have Buyed her Products and have a legal Right for the Sources!!!

At most to blame is from my Point of View Linux Torvald for Refusing having a GPL3 Linux Kernel in parallel to a GPL2 Linux Kernel.

That way Developers have the Freedom do decide if they want put her Efforts into a GPL3 Kernel and make GPL2 outdated or not. Customers will have also the Freedom to Buy GPL3 vs GPL2 Devices.

In my Point of view such things can be easy solved by Having a GPL3 Linux Kernel but Torvalds refused to provide this Option.

I think clearly Torvalds is to blame for this Stupidity at most!
[Ornate TrueSmart] Lokifish Marz:
And...........

Omate had to fork over money for it.

Not a win in my book.
[Ornate TrueSmart] jumoog:
i hope they learned something and dont use MTK anymore
[Ornate TrueSmart] :
Hi Helgaiden.

Thanks a lot for letting people know that Omate Trusmart finally got the Source Code after they Paid the needed Money to MediaTek.

Source => https://plus.google.com/111628072657804333818/posts/9anVhPpR9UQ

From my Experience and what i have seen till yet the Kernel Source will be Full with Copyrighted and closed Mediatek Files that can not be Published.

Asking me if every Dev Backer will have the Chance to get the Sources also even with the NDA that Omate needed to Sign and all the Copyright Protected MediaTek Files.

At least we have more Controll over our Smart Phone Watches that is good.

Really Big thanks to Omate and Laurent Le Pen.
[Ornate TrueSmart] Helgaiden:
this I knew. Maybe LLP was just trying to quick-fix it instead of trying to get it through some other long and drawn out process. As it is, its an improvement, even if it isn't a win.
[Ornate TrueSmart] Uclydde:
Does this mean I can start hoping for Cyanogenmod 11 builds?
[Ornate TrueSmart] dragonfly1113:
agreed!
[Ornate TrueSmart] Lokifish Marz:
For those that don't dev, the first thing it to be able to compile a bootable using the source code they gave us. If a bootable build cannot be made then it's almost the same as not having source at all.
[Ornate TrueSmart] kuronosan:
Unless it can be built, no.
[Ornate TrueSmart] superdragonpt:
No

Afaik

MTK code is weird.

It involves some specifics commands/build env/ toolchain,etc.

To build my first custom mtk kernel was an pain in The...

Regards
[Ornate TrueSmart] Uclydde:
And we don't know if a bootable can be built yet?
[Ornate TrueSmart] kuronosan:
It can be. The question is how long and how difficult.
[Ornate TrueSmart] martinbogo1:
--- I'm afraid that the kernel in this case doens't have much of a device tree to extract. Talk to Grant.. he'll give you the skinny on how Device Tree has evolved over the last few kernel series for ARM.

Just having the DT isn't enough. You need to have everything needed in the state engine for initialization of the hardware, and that's not trivial.

-M

---------- Post added at 06:24 AM ---------- Previous post was at 06:20 AM ----------

Well, I'd like to help if I can. I have experience writing ARM kernel drivers ( 10 Gig E driver for the Calxeda EnergyCore chip ), power management, and device tree.

-Martin
[Ornate TrueSmart] pof:
Where can I download the kernel sources for the TrueSmart?
[Ornate TrueSmart] Lokifish Marz:
I think Dees is still trying to to get everything together. What we got was an incomplete, mixed up kang from another device.
[Ornate TrueSmart] pof:
damn it! I need to compile a kernel ASAP to see if i can fix my touchpanel issue by modifying the driver source, so i don't have to go through the pain of getting a replacement unit from Omate. ;)
[Ornate TrueSmart] kuronosan:
If you want to help with kernel development you can start by joining up on plus or hangouts, where ideas get shared much more rapidly.
[Ornate TrueSmart] Lgrootnoob:
bump, link me the hangouts room
[Ornate TrueSmart] superdragonpt:
Just ordered mine yesterday...

As soon as it arrives i will start working on OMATE sources

Regards
[Ornate TrueSmart] kuronosan:
Awesome, we're stalled right now, so we can start up after the smoke clears and you get your unit n
[Ornate TrueSmart] superdragonpt:
I'm not very active on omate section.

So if I understood right, no one was able to compile an working kernel ?

I though omate gave the full build able sources ?

I think I'll be luckily by adapting from another mt6572 device source .

I'll start working on it this weekend.

Regards
[Ornate TrueSmart] Lokifish Marz:
Incomplete kang from an ipro so not even the source is original.
[Ornate TrueSmart] superdragonpt:
DAMM.

Let me do my research, concerning your device sensor configs (ALPS/touch/LCM/etc), got an MT6572 source here, that looks complete (only kernel, compiles ok now, after fixing symlinks and build errors )

You should have an projectconfig under data/misc (on / system), but usually its not complete, and sometimes there's diffs comparing to the kernel projectconfig, but should be an good start point

EDIT:

Yeah "your source" Target Product (lcsh72_we_jb3) is the same as the sources i own from another MT6572 device ...

Regards
[Ornate TrueSmart] death_entry:
What device is this? Ooo can't wait to see what you manage to sort out :)