Formal request for source code

[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

 

[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

 

[superdragonpt]

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

My bad

 

[ARAN]

@Neuer_User

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.

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!

 

[Helgaiden]

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!

 

[Lokifish Marz]

And...........

Omate had to fork over money for it.

Not a win in my book.

 

[jumoog]

And...........

Omate had to fork over money for it.

Not a win in my book.

i hope they learned something and dont use MTK anymore

 

[ARAN]

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.

 

[Helgaiden]

And...........

Omate had to fork over money for it.

Not a win in my book.

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.

 

[Uclydde]

Does this mean I can start hoping for Cyanogenmod 11 builds?

 

[dragonfly1113]

Does this mean I can start hoping for Cyanogenmod 11 builds?

agreed!

 

[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.

 

[kuronosan]

Does this mean I can start hoping for Cyanogenmod 11 builds?

Unless it can be built, no.

Sent from my Galaxy Nexus using Tapatalk 2

 

[superdragonpt]

Does this mean I can start hoping for Cyanogenmod 11 builds?

No

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.

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

 

[Uclydde]

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.

And we don't know if a bootable can be built yet?

 

[kuronosan]

And we don't know if a bootable can be built yet?

It can be. The question is how long and how difficult.

Sent from my Galaxy Nexus using Tapatalk 2

 

[martinbogo1]

i'll help you out

1.) extract boot.img to get Ramdisk content

2.) from their we can create a Device Tree and can build Android

--- 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 ----------

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.

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

 

[pof]

Where can I download the kernel sources for the 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.

 

[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.