the Meizu MX device has opensource in gethub.
The kernel source code is for meizu m030, m031 and m032 wcdma smartphone .
You can see the url below.sorry for i cannt published directly link.
hope the custom roms will be more and more.
https://github.com/lvchaqiu/meizu-mx-kernel
Hardly a post for Android development. Moving to General.
Do not forget to follow/subscribe the other topic of interest for Exynos (4412):
http://cleanimport.xda/index.php?THREADs
(skip to posts past ~23 Oct 2012 for interesting stuff)
Though it addresses lack of proper driver sourcecode (RIL, camera, HWC, etc. etc.) support in particular, which may not apply to Meizu devices.
Related
Hi
Today on MIUI facebook thay share with us information about MiCode
this is content of this post
"MIUI port projects officially go open source
http://www.micode.net/portal.php
Here you can find the information and source code you need to build an Android-compatible device. Android is an open-source software stack for mobile devices, and a corresponding open-source project led by Google. We created Android in response to our own experiences launching mobile apps. We wanted to make sure that there was no central point of failure, so that no industry player can restrict or control the innovations of any other. That's why we created Android, and made its source code open."
so Please could someone do or try something with this for our X8
{Polish On}
A miałem to dodać xD
{Polish Off}
Okey , i was thinking about that this code will help devs port miui to x8.
What do u think about that ? By my opinion this would help devs port miui to x8 which will be great ;D
It wont be easy, but possible. X8 has a armv6 processor, but originally MIUI requires a armv7 processor...
Hit the THANKS button if I helped!!
Sent from my W8 using Tapatalk
I'm cloning PatchRom now to see if I can learn how it works, looks like it takes an "stock" rom and transforms it on a MIUI rom.
@Darth @Heisenberg Open source is right For all :/ I learned from xda and if you all remember I had my first thread closed for it too. (Kernel thread) .... Well let's stop the intro and talk straight this Thread by @ED300 Cm13.0 by ed300 has all Obsolete and Non updated sources It doesn't even contains device tree :/ and Obsolate Kernel tree too if you check his kernel Compiled date. plus Vendor By floromu has no camera vendor And Blobs As well for adreno blah blah one have to use openssl concept for it ... That means the sources on ops thered are either not updated and I remember I read somewhere that GPL sources should be published but why op @ED300 didnt ? That's sad ! Am I fool trying to make Device tree from Lettuce Jalebi and Make ROMs For this device and open source it for public I just want to ask that when I will be able to see the correct device tree and Vendor source :/ on our OPs thread first of all let me Make few things clear Latest sources By Floromu 6-7month old are way obsolete than cm structure latest Structure is here check this
Link :- https://gitlab.com/dev-harsh1998/android_device_lenovo_a6000/tree/master
Well that means ROM can't be compiled On Floromu's tree
And as Says our op has elberry 6 latest Patch interesting
point 2:- Kernel sources :- dated 6 months old
Compiled Date xyz with unlocked freqs and wake Gesture.
I have No hate For @ED300 I just want our op to opemsource his GPL things And follow proper Rules
Sir,
You've reported nothing on this, using the proper report system. Also, accusations like this tend to fall under rule 12 here, http://forum.xda-developers.com/announcement.php?a=81
Have you privately brought this up to the person you're accusing? Did it not lead anywhere?
Then gather clear evidence and click report on the OP of the thread in question. That is the proper way to handle these things .
Creating drama in threads, or opening a thread like this is NOT how to handle these situations. And accusing mods and xda of not caring? Yet you've not followed the steps above? That's ridiculous I'd have to say.
Read rule 12, follow procedures listed and if you report it, bring evidence.
This thread is closed. And please don't stir up drama publicly in the future. :good:
Darth
Senior Moderator
dev_harsh1998 said:
@Darth @Heisenberg Open source is right For all :/ I learned from xda and if you all remember I had my first thread closed for it too. (Kernel thread) .... Well let's stop the intro and talk straight this Thread by @ED300 Cm13.0 by ed300 has all Obsolete and Non updated sources It doesn't even contains device tree :/ and Obsolate Kernel tree too if you check his kernel Compiled date. plus Vendor By floromu has no camera vendor And Blobs As well for adreno blah blah one have to use openssl concept for it ... That means the sources on ops thered are either not updated and I remember I read somewhere that GPL sources should be published but why op @ED300 didnt ? That's sad ! Am I fool trying to make Device tree from Lettuce Jalebi and Make ROMs For this device and open source it for public I just want to ask that when I will be able to see the correct device tree and Vendor source :/ on our OPs thread first of all let me Make few things clear Latest sources By Floromu 6-7month old are way obsolete than cm structure latest Structure is here check this
Link :- https://gitlab.com/dev-harsh1998/android_device_lenovo_a6000/tree/master
Well that means ROM can't be compiled On Floromu's tree
And as Says our op has elberry 6 latest Patch interesting
point 2:- Kernel sources :- dated 6 months old
Compiled Date xyz with unlocked freqs and wake Gesture.
I have No hate For @ED300 I just want our op to opemsource his GPL things And follow proper Rules
Click to expand...
Click to collapse
Also,
XDA doesn't require things like vendor files and device trees to be published, as they are not licensed under the GPL but rather Apache 2.0 (like the rest of Android). Apache allows you to close source things if you want, there is no publishing requirement, just that you still have the license applied to the file. Only kernel source is required to be published due to GPL.
Thanks @nathanchance :good:
Huawei is extremely reluctant to publish the Linux 4.x kernel source code they are using on Mate9, although it is a blatant violation of the General Public License (GPL).
Meanwhile one can buy a (overpriced) HiKey960 development board https://www.amazon.de/ALLNET-LeMaker-4xARM-Cortex-LEMAKER-HIKEY960/dp/B071429D9W , which is a heavily stripped down version of Mate9: no LCD+touchscreen, no modem, no GPS, no accelerometer/gyroscope/compass, less RAM, etc.
Linaro/Huawei are providing the full 4.4 (and 4.9) kernel source code together with the
Debian image and AOSP, and full schematics for this board: https://github.com/96boards-hikey/tools-images-hikey960/blob/master/README-technical.md
I think we should make a side-by-side comparison of HiKey960 and Mate9 hardware and (closed source) firmware. Feel free to post your findings here, because it seems to be our only real chance to have a properly running LineageOS on Mate9 in a timeslot before this device will become obsolete.
Hi,
I am opening this thread to start a discussion about LineageOS and the recently announced Project Mainline to put together a Q&A list (I will summarize the interesting questions and answers in this first post).
1. In general: will Project Mainline still work when you switch from your manufacturers stock ROM to LineageOS..? Or may there some restrictions for non-official ROMs through the Play Store?
2. Will LineageOS be able to support Project Mainline for devices that support Project Mainline in their stock ROM?
3. Will LineageOS be able to support Project Mainline for older devices? Or do old Linux kernels prevent this? Are kernel refreshs for old devices even technically feasible or is it far too much effort and too buggy in most cases?
4. These are the 14 components Project Mainline is able to update via the Play Store:
• Security: Media Codecs, Media Framework Components, DNS Resolver, Conscrypt
• Privacy: Documents UI, Permission Controller, ExtServices
• Consistency: Timezone data, ANGLE (developers opt-in), Module Metadata, Networking components, Captive Portal Login, Network Permission Configuration
I assume this doesn't cover all "components" in Android, or does it? What parts are left out and why - does anybody know?
Cheers,
carsten
Hello all,
I have found some watches with open source Roms here at xda-devs but I am not sure about how active the developers are and if a Rom from months back have the required security kernel patches (for example).
It would be nice if this thread gathered all (or most) of the information about smartwatches that have good open source Rom support.