Hey there everyone!
So I was just scouring the Internet, as usual, and I came across something unusual on the Elephone download servers: P6000_sourcecode.tar.gz. Of course, as a MediaTek fan, and one who is always campaigning for MediaTek to release their sources (you can see that on my blog at AllDroid Reviews), I immediately grabbed the file and took a look. :cyclops:
You can get the source code here: http://www.droidagency.com/elephone-p6000-source-code-2208/
Have fun playing with it, because as a basic ROM builder/modifier, I have no idea yet how to compile it/compile a ROM. I will try though, and will probably use CM12 as a base ROM.
If anyone has any idea if it is the full kernel source code, ROM code, or anything, please do leave a comment on this thread! :fingers-crossed:
There's an error during extracting the archive on linux.
It builds fine though, however haven't tested if it boots, because the device is not mine and I don't plan working on that kernel.
I.nfraR.ed said:
There's an error during extracting the archive on linux.
It builds fine though, however haven't tested if it boots, because the device is not mine and I don't plan working on that kernel.
Click to expand...
Click to collapse
That's great news! You can try posting the built kernel to the forum at bbs.elephone.hk, the developers there will be more than willing to test it. :good::laugh:
hello, so i have been in communication with huawei regrading the kernel source. i mentioned the lack of source files for the mate 7 and how its part of the google/android agreement that oems must share all relevant sources for devices that use any part of android. they replied with the usual reply about how they will work hard to resolve this issue and whatnot. the rep did give me a link to the kernel source which i believe is for kitkat but i cant be sure so i hope that someone can verify.
having said that, why cant the kitkat source be used to build for lollipop and marshmallow? im still using a nook hd+ that is running MM......... WHAT??? how is this possible if the only kernel provided was for ICS? anyway, im going to keep poking at them until they either give up the LP/MM sources of they tell me to ****off. so, if anyone can please check out the link i would really appreciate it.
Lollipop Kernel?
I don't know if this allowed or not, but with the official release of Oreo now rolling out it would be a good idea for people to request Sammy releases the official Kernel source for developers to crack on with AOSP. If people could do this that would be fantastic.
Instructions as follows:
1. Go to the opensource website: http://opensource.samsung.com/reception/receptionSub.do?method=sub&sub=F&searchValue=G950F (change the value to your device)
2. Click on the "inquiry" letter on the right side of the website
3. Enter your informations (Name/Email and so on), click on "inquiry type", "request for source codes"
4. Source code type: "kernel"
5. Write a message to request the
G950FXXU1CRAP Oreo source code (it's important that you mention the base)
6. Agree the terms and send it to samsung
Thanks to Mohammed in the Telegram chat for these instructions.
Let's get these sources and finally get the AOSP we deserve!
MrDanMak said:
I don't know if this allowed or not, but with the official release of Oreo now rolling out it would be a good idea for people to request Sammy releases the official Kernel source for developers to crack on with AOSP. If people could do this that would be fantastic.
Instructions as follows:
1. Go to the opensource website: http://opensource.samsung.com/reception/receptionSub.do?method=sub&sub=F&searchValue=G950F (change the value to your device)
2. Click on the "inquiry" letter on the right side of the website
3. Enter your informations (Name/Email and so on), click on "inquiry type", "request for source codes"
4. Source code type: "kernel"
5. Write a message to request the
G950FXXU1CRAP Oreo source code (it's important that you mention the base)
6. Agree the terms and send it to samsung
Thanks to Mohammed in the Telegram chat for these instructions.
Let's get these sources and finally get the AOSP we deserve!
Click to expand...
Click to collapse
You won't get aosp from these sources, nougat sources has been out for a very long time and even then there isn't a fully functional aosp Rom.
sofir786 said:
You won't get aosp from these sources, nougat sources has been out for a very long time and even then there isn't a fully functional aosp Rom.
Click to expand...
Click to collapse
FevaX is working on the development with some others. He was working on Lineage 14.1, but decided to hold out for 15.1 instead and Kernel sources.
We can only hope I suppose. I just think there's a lack of developers for our device in this regard but anything that will help FevaX and team would be great.
MrDanMak said:
FevaX is working on the development with some others. He was working on Lineage 14.1, but decided to hold out for 15.1 instead and Kernel sources.
We can only hope I suppose. I just think there's a lack of developers for our device in this regard but anything that will help FevaX and team would be great.
Click to expand...
Click to collapse
I mean I love seeing variety with roms we can flash, but like you said there just haven't been that many devs wanting to work on it. I personally won't be trying a aosp Rom if ever it comes to fruition, i would have bought a pixel phone if that was what I wanted but I know there is some sort of demand for it though so here for you guys to see a fully working release soon
LineageOS (Lineage Android Distribution) members or anyone else on this website is not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed. Please do some research if you have any concerns about features included in the products you find here before flashing it! YOU are choosing to make these modifications, and if you point the finger at us for messing up your device, we will laugh at you. Your warranty will be void if you tamper with any part of your device / software.
How to Install:
1- Make a backup of your important files
2 - Unlock bootloader with this guide
3 - Flash the TWRP, link here
4 - Move Rom & Gapps (optional) into device storage
5 - Full Wipes
6- Flash Rom & Gapps (gapps are OPTIONAL)
for GAPPS:
Choose Gapps Package ARM64 > 7.1 > Micro and below: visit OpenGAPPS
If during the gapps flash it gives you an error then in the TWRP terminal or on the adb shell you have to execute this command: "mkdir /tmp/bin"
Download:
Releases · XRedCubeX/android_device_meizu_m5c
Contribute to XRedCubeX/android_device_meizu_m5c development by creating an account on GitHub.
github.com
Working:
Boots
Storages
Bluetooth
Wifi
GPS - GNSS
Audio
NOT Working:
Camera
Hotspot
Offline Charging
Special Thanks
LineageOS
Moyster for device trees
Device Tree:https://github.com/XRedCubeX/android_device_meizu_m5c
Vendor Tree: https://github.com/XRedCubeX/android_vendor_meizu_m5c
Assim que possível, irei testar!
Hi Red. I was taking a look at the ROM repository on GitHub, and saw that the default branch is now named cm-13.1. So, are you now working on an Android 6.0 ROM for the M5c?
thiagosousa777 said:
Hi Red. I was taking a look at the ROM repository on GitHub, and saw that the default branch is now named cm-13.1. So, are you now working on an Android 6.0 ROM for the M5c?
Click to expand...
Click to collapse
I have a slight indecision, now I can not carry on the Custom ROM because I do not have the right PC but when I am able to compile it, I will evaluate which one can work better
XRed_CubeX said:
I have a slight indecision, now I can not carry on the Custom ROM because I do not have the right PC but when I am able to compile it, I will evaluate which one can work better
Click to expand...
Click to collapse
I see. I would say that in the long run Lineage 14 would be more worthwhile, since Android 6.0 is becoming outdated, with no support for some apps. But really, I just wanted a ROM to replace Flyme, and its bugs. Also, many of the apps I use don't work, or don't work right on Flyme...
These days I was taking a look at /e/ OS. I've been thinking about venturing into porting this ROM to the M5c. For me it would be a challenge, since I've never done this before. But unfortunately at the moment I also don't have a PC that meets the requirements to compile the ROM
thiagosousa777 said:
I see. I would say that in the long run Lineage 14 would be more worthwhile, since Android 6.0 is becoming outdated, with no support for some apps. But really, I just wanted a ROM to replace Flyme, and its bugs. Also, many of the apps I use don't work, or don't work right on Flyme...
These days I was taking a look at /e/ OS. I've been thinking about venturing into porting this ROM to the M5c. For me it would be a challenge, since I've never done this before. But unfortunately at the moment I also don't have a PC that meets the requirements to compile the ROM
Click to expand...
Click to collapse
I find it useless, just use lineage without gapps and it will be better than /e/, then anyway I don't know where to find the manifest
XRed_CubeX said:
I find it useless, just use lineage without gapps and it will be better than /e/, then anyway I don't know where to find the manifest
Click to expand...
Click to collapse
You are right. However, /e/ has some nice features like e account synchronization, an app store, microG, and some of their apps... Of course we could get that with LineageOS, but it is interesting how /e/ already brings that well integrated and ready.
By the way, I am also looking at other non-Android systems, like Ubuntu Touch...
thiagosousa777 said:
You are right. However, /e/ has some nice features like e account synchronization, an app store, microG, and some of their apps... Of course we could get that with LineageOS, but it is interesting how /e/ already brings that well integrated and ready.
By the way, I am also looking at other non-Android systems, like Ubuntu Touch...
Click to expand...
Click to collapse
Ah beautiful those non-android systems yes, unfortunately we have to forget them because of the prebuilt kernel and unavailable sources
XRed_CubeX said:
Ah beautiful those non-android systems yes, unfortunately we have to forget them because of the prebuilt kernel and unavailable sources
Click to expand...
Click to collapse
Well, from what I've been reading the process is similar to porting LineageOS. You just need the kernel sources and the device specific binary blobs. I'm guessing you know how to get them, don't you?
And the interesting thing is that there is a layer, called Halium, that interacts directly with the hardware. And that is actually what you should port to the desired device. Then you can install any Linux system on top of this layer, like Ubuntu Touch, Plasma Mobile, etc, and these are distributed pre-compiled.
thiagosousa777 said:
Well, from what I've been reading the process is similar to porting LineageOS. You just need the kernel sources and the device specific binary blobs. I'm guessing you know how to get them.
And the interesting thing is that there is a layer, called Halium, that interacts directly with the hardware. And that is actually what you should port to the desired device. Then you can install any Linux system on top of this layer, like Ubuntu Touch, Plasma Mobile, etc, and these are distributed pre-compiled.
Click to expand...
Click to collapse
Mhh ... good, you are informed, however the vendor blobs are bull**** to take, the problem is the kernel sources but Meizu has not released them. However, some time ago I booted a Custom kernel based on ALPS (A custom AOSP from Mediatek to be clear) but the touchscreen doesn't work and I'm looking for a solution around but that I can't find
P.S: Fixing that kernel has great potential, forget android 7, you could also boot android 9 with sources, but as long as they are still working
XRed_CubeX said:
Mhh ... good, you are informed, however the vendor blobs are bull**** to take, the problem is the kernel sources but Meizu has not released them. However, some time ago I booted a Custom kernel based on ALPS (A custom AOSP from Mediatek to be clear) but the touchscreen doesn't work and I'm looking for a solution around but that I can't find
P.S: Fixing that kernel has great potential, forget android 7, you could also boot android 9 with sources, but as long as they are still working
Click to expand...
Click to collapse
I confess I didn't quite understand one thing: so how did you port LineageOS to this device? You didn't need the kernel sources?
thiagosousa777 said:
I confess I didn't quite understand one thing: so how did you port LineageOS to this device? You didn't need the kernel sources?
Click to expand...
Click to collapse
At the time I was doing this lineage, I was with the prebuilt kernel, week ago I had done this kernel port to a twrp and the touch was not working so I left the device alone
XRed_CubeX said:
At the time I was doing this lineage, I was with the prebuilt kernel, week ago I had done this kernel port to a twrp and the touch was not working so I left the device alone
Click to expand...
Click to collapse
Thanks for the clarification! It is a shame that Meizu does this (I wonder if they are not violating the terms of the Linux GPL license by distributing the kernel without publishing the modifications made to the source code).
Anyway, if a solution to this kernel problem related to the touch screen comes up, please let me know. In the meantime I'll keep reading Halium's documentation until a solution comes along, or until I get a compatible phone.
Great work!
Hello. I've been testing this ROM on my M5c and love it. The ROM is very good, fluid, lightweight... the only problem is that the camera doesn't work, as well as the cellular network data. Congratulations for the excellent work.
The ROM will no longer receive bugfixes?
pls compile
publish a release
My Question Is How Will the Custom Rom Made From The Aosp Base??
I Really want to learn the Android Custom Rom Development.(Again I'm Telling That I'm Not asking about complier or bulid the rom). I'm asking about the source and how it is made.
I Want To Be a core member.
Giving a Guide To This Question Is Highly Appreciated!!
Thank You Guys
(t.me) is a good place, they use SDK and Android Kitchen etc.
JaswanthTeja said:
My Question Is How Will the Custom Rom Made From The Aosp Base??
I Really want to learn the Android Custom Rom Development.(Again I'm Telling That I'm Not asking about complier or bulid the rom). I'm asking about the source and how it is made.
I Want To Be a core member.
Giving a Guide To This Question Is Highly Appreciated!!
Thank You Guys
Click to expand...
Click to collapse
Custom ROM sources require that the stock source code be made available to the public by the manufacturer/carrier of the device. If the stock source code for a specific device has not been made available to the public, developers can not create custom ROM source code for that specific device. Developers use the stock source code to create the custom ROM source code and then ROMs are built using the custom source they created. I think that is the answer you were really looking for. You want to know how the source code itself that the ROMs are built from is created. You aren't asking about the fruit that comes from the tree, you are asking where the tree that bears the fruit comes from. Am I right?
The only way to get custom ROMs on devices that do not have stock source code made available is to port custom ROMs from a similar device with the same architecture that does have available source code and custom ROMs made for it.
OldNoobOne said:
(t.me) is a good place, they use SDK and Android Kitchen etc.
Click to expand...
Click to collapse
I don't think that is what they are asking.
Droidriven said:
I don't think that is what they are asking.
Click to expand...
Click to collapse
Yeah, I Want To Know About Android Arc
JaswanthTeja said:
Yeah, I Want To Know About Android Arc
Click to expand...
Click to collapse
I answered the question. If you specifically want to know how developers convert stock source code into custom ROM source code, you probably will not find that answer here. Most of the people here work with the stuff that the LineageOS team creates from stock source code after the custom ROM source code has been created, they are not part of the process involved in creating the custom source code. It is like being a construction worker, the construction worker does not create the material that he uses to build a house, someone else creates the materials and then he uses what they created to build a house. Google and the LineageOS team create the material, the developers here use what they created to build the ROMs here.
You should try going to github or the LineageOS website to ask your question.
Droidriven said:
I answered the question. If you specifically want to know how developers convert stock source code into custom ROM source code, you probably will not find that answer here. Most of the people here work with the stuff that the LineageOS team creates from stock source code after the custom ROM source code has been created, they are not part of the process involved in creating the custom source code. It is like being a construction worker, the construction worker does not create the material that he uses to build a house, someone else creates the materials and then he uses what they created to build a house. Google and the LineageOS team create the material, the developers here use what they created to build the ROMs here.
You should try going to github or the LineageOS website to ask your question.
Click to expand...
Click to collapse
cool