I wrote the question on wrong thread. So i write it here again.
How come Bule build CM13? Did Xiaomi release the source code?
Where did you see that?
on mokee by Bule on xda, on 4pda and in this http://bbs.ydss.cn/
He just said that he was going to focus on CM13, just that. AFAIK he didn't achieved it yet.
i understand what he said and i know he haven't anything ready yet...but my question is obvious. How is gonna make it?? Source code?
Same as Lokjianming, he will use old lollipop kernel to make propably won't bootable ROM It will be better if everyone who can, help nofearnohappy with his kernel source than trying propably impossible
https://github.com/nofearnohappy/Custom_kernel_hermes_new
Related
Okay, First of all, I know this is the incorrect place for a "development" thread, But I am currently unable to post in the correct area.. So here is the second best place.
I've had an idea. Since sadly I am gonna be giving back the Samsung Note 2 (Friend let me borrow it) I have to do something with the new Umi eMax I have.. Its a great potential phone but MEDIATEK wont freaking let us have the source code... So, Why not pull it off a rom? You can easily download something like ColorOS, Get the kernel, and extract the Source code, Am I not right?
I am wanting to do this because Umi has been sitting around barely doing jack trying to get the new 5.0 android up and running.. So installing CM 12.1 would be great!
This is probably totally impossible.. as I am a beginner at this kinda stuff, But, would this idea work or not?
I have the build.prop file if anyone wants to take a look at it.. Though we probably all know it runs off the MT6752.
So, Does anyone have any ideas? Or am I just getting completely over confident on this?
Trying to get 10 posts....
Hello, I should be buying a Swift 2 Plus soon, and as a complete noob, I don't know what the death of Cyanogen is going to do to my device. Obviously it won't instantly brick it, but how am I gonna get future Android updates without installing a custom rom?
have a sexy christmas
Please, read my post here, and the (unconfirmed) Wileyfox's response to Cyanogen move here. It should be enough to clear your doubts
linuxct said:
Please, read my post here, and the (unconfirmed) Wileyfox's response to Cyanogen move here. It should be enough to clear your doubts
Click to expand...
Click to collapse
One thing relating more to the custom ROM area. So some of the CM team (not COS) are rebranding as lineage OS right. And they are continuing off the codebase of CM however we don't have a build of CM so how will and developer , from lineage or anywhere else, build a custom ROM without code from CM or AOSP. Unless Cyanogen Inc release the source code for our phone which I'm not sure they will. (Sorry if this is a noob question)
person123321 said:
One thing relating more to the custom ROM area. So some of the CM team (not COS) are rebranding as lineage OS right. And they are continuing off the codebase of CM however we don't have a build of CM so how will and developer , from lineage or anywhere else, build a custom ROM without code from CM or AOSP. Unless Cyanogen Inc release the source code for our phone which I'm not sure they will. (Sorry if this is a noob question)
Click to expand...
Click to collapse
You're absolutely correct. We can't start with the development with no sources. However, I don't think Cyanogen would do that at the moment, and, after seeing Wileyfox's response to Cyanogen moves, I think (and actually hope) they'll switch to an AOSP-based ROM with Android N 7.0 upgrade, and if that happens I'm really sure they'll have no problem on releasing the source code (remember Wileyfox devices tend to be quite developer-friendly). From that, we can work on bringing Lineage...
Hello!
I'd like to build my own rom from AOSP 8.0 official branch. I'm looking for some kind of guide but couldn't find any So, let's say I've got android source code and files from other custom rom that makes camera work. What have I to do to make my rom now? How can I build it and be sure that everything will work. Generally my target is to install android 8 on my Leeco le 2 x620 device with Mediatek chip
Any help is appreciated ^v^
LEGOL2 said:
Hello!
I'd like to build my own rom from AOSP 8.0 official branch. I'm looking for some kind of guide but couldn't find any So, let's say I've got android source code and files from other custom rom that makes camera work. What have I to do to make my rom now? How can I build it and be sure that everything will work. Generally my target is to install android 8 on my Leeco le 2 x620 device with Mediatek chip
Any help is appreciated ^v^
Click to expand...
Click to collapse
"I'd like to build my own rom from AOSP"
So you mean an aftermarket os like lineageos or carbonrom or do you mean that you take the aosp repo and compile aosp for your device? You can look in source.android.com
"source code and files from other custom rom that makes camera work"
Is that an already compiled rom? Because you won't get source code out of that
"How can I build it and be sure that everything will work"
Ya don't. Nothing can ever be 100% bugfree, it can either be from your device tree's source code, or the aosp code itself.
Generally, if there is a caf tree for your device, it's going to be 3x as hard to create an aosp tree.
It is going to be 100000x as hard to create an aosp tree that is for a newly released, new hardware requirement operating system.
Wanna know the topping of the cake? Mediatek is notorious when it comes to releasing the source (in fact, it has become a meme in the Mediatek users world) but don't let that stop you son.
You can try, but don't give up just because it won't compile the first couple of hundred times. The errors when compiling should give you a great start
Good luck.
ramiabouzahra said:
"I'd like to build my own rom from AOSP"
So you mean an aftermarket os like lineageos or carbonrom or do you mean that you take the aosp repo and compile aosp for your device? You can look in source.android.com
"source code and files from other custom rom that makes camera work"
Is that an already compiled rom? Because you won't get source code out of that
"How can I build it and be sure that everything will work"
Ya don't. Nothing can ever be 100% bugfree, it can either be from your device tree's source code, or the aosp code itself.
Generally, if there is a caf tree for your device, it's going to be 3x as hard to create an aosp tree.
It is going to be 100000x as hard to create an aosp tree that is for a newly released, new hardware requirement operating system.
Wanna know the topping of the cake? Mediatek is notorious when it comes to releasing the source (in fact, it has become a meme in the Mediatek users world) but don't let that stop you son.
You can try, but don't give up just because it won't compile the first couple of hundred times. The errors when compiling should give you a great start
Good luck.
Click to expand...
Click to collapse
Oh God, how am I meant to do this ;0 There is Lineage 14.1 project on my device. I really want to have android 8 on my phone. Thank you for all the advice.
Yes im trying the same andere without any succes so far.
Im also trying to port from a different device ROM to the stock ROM what im running now.
The chip sets are the same but the Android versions not.
It would be really Nice if some mtk ROM developer find some time in his busy life to create a ROM for our phone.
Or a guide to compile/port Android o tot oud phone.
We need build instructions in order for people to more easily make custom roms. Currently most roms here only provide a repo or two, hardly describing the build process if anything. Not sure if those repos contain all the sources/blobs you need either.
It's not that hard to build and you can always go on th cheap and hire a cloud vps for a few hours, so don't bother with local building unless you have the powerful hardware.
Anyhow, so far what I know is that some people just replace the kernel and firmware, it seems this is called repacking.
Others are building Lineage from source as per their instructions, which are not descriptive when you're porting to a new device.
We need concrete and concise information about how it's done.
Lineage wiki is pretty accurate and if someone ask here I can try to solve his doubt.
I am not the best developer but I know the basics xD
Can you describe the basic workflow?
Which repos to check out, what build scripts are there, how to combine them. Basically a short tutorial on stuff. Also how come you're using 821 kernel from zl1, i know 820 and 821 are alike, but when do you patch the kernel to work for 820, i read that you need some config changes and a different gpu blob.
I am a developer myself, but not an android rom one. Things look really fragmented and chaotic. Besides Lineage wiki, I haven't found anything that resembles docs. I really want to contribute on this and have the hardware to build, just need some info on where to begin.
Thanks for taking your time to reply.
randxor said:
Can you describe the basic workflow?
Which repos to check out, what build scripts are there, how to combine them. Basically a short tutorial on stuff. Also how come you're using 821 kernel from zl1, i know 820 and 821 are alike, but when do you patch the kernel to work for 820, i read that you need some config changes and a different gpu blob.
I am a developer myself, but not an android rom one. Things look really fragmented and chaotic. Besides Lineage wiki, I haven't found anything that resembles docs. I really want to contribute on this and have the hardware to build, just need some info on where to begin.
Thanks for taking your time to reply.
Click to expand...
Click to collapse
Thats thanks to codeworkx code. Basically you compile a rom for zl1 and works for zl0.
My workflow is
repo init/sync the rom
Fix libhidl and libbfquio if needed (Dont know why they fix an error creating a bigger one tho)
Take the device tree, vendor and kernel
Adapt the device tree for the rom (Like in cosmic where config is in root not in config folder, boardconfig...)
And just brunch or make or lunch depends on rom xD
Edit: Forgot u need like 200 frameworks/av commits to make zoom work https://github.com/mosimchah/frameworks_av/commits/o8.1 all the january 15th and this one http://gerrit.aicp-rom.com/#/c/54436/
You init the Lineage repos?
What are those libhidl and libfquio about, and how do you fix them?
Vendor is the firmware blobs?
Kernel is obvious
What is a device tree? And how it relates to the kernel?
How did you adapt it to the device?
Different devices have different partion layouts I assume. How do you make the zl1 rom work for both zl0 and zl1? Earlier people were reporting bricks because of flashing roms for zl1 on zl0
randxor said:
You init the Lineage repos?
What are those libhidl and libfquio about, and how do you fix them?
Vendor is the firmware blobs?
Kernel is obvious
What is a device tree? And how it relates to the kernel?
How did you adapt it to the device?
Different devices have different partion layouts I assume. How do you make the zl1 rom work for both zl0 and zl1? Earlier people were reporting bricks because of flashing roms for zl1 on zl0
Click to expand...
Click to collapse
Yout init the rom source you want to compile
You dont need to adapt anything codeworkx already did it for us we just compile zl1 roms with his device tree (Los one) or any of the forked ones (Like Aicp which I recommend).
Libhidl and libbfquio depends on the rom you are building. Libhidl is solved by reverting this changes https://github.com/PixelExperience/system_libhidl/commit/607e961b85eea8969503d8ff8437c014f04f0ca2 and libbfquio by taking this http://gerrit.aicp-rom.com/#/c/56488/
You dont adapt device tree to device you adapt it to the rom you are compiling see how other devs do it in their github (Every rom is different for example in cosmic you rename lineage/aicp.mk to cos.mk and change where to import things)
---------- Post added at 01:53 PM ---------- Previous post was at 01:49 PM ----------
Start by picking up a rom you want to compile that has 8.1 source working and better if a msm8996 device is there (zuk z2, oneplus 3...)
Thanks for the info. Will experiment a bit when I have free time. Planning on making an in-depth guide if I succeed and clarify the concepts.
Btw I see that everyone is using kernel 3.18.20, why can't we get a newer kernel? If we have the sources for it and the blobs? Is the reason being that the drivers are not in the mainline kernel so they need to be ported to a newer kernel?
randxor said:
Thanks for the info. Will experiment a bit when I have free time. Planning on making an in-depth guide if I succeed and clarify the concepts.
Btw I see that everyone is using kernel 3.18.20, why can't we get a newer kernel? If we have the sources for it and the blobs? Is the reason being that the drivers are not in the mainline kernel so they need to be ported to a newer kernel?
Click to expand...
Click to collapse
Np
Not sure dont know much about android kernels
hi peeps. thank u for stopping by
i want to get into android development and make personal touches and changes to my phone. i quite like oxygenOS so i would like to stick with this and modify that slowly. but i cant figure out how to begin specifically with oxygenos? it doesnt appear as if they release their source code anymore. could anyone please point me in the right direction? thank you
kieran_buffet said:
hi peeps. thank u for stopping by
i want to get into android development and make personal touches and changes to my phone. i quite like oxygenOS so i would like to stick with this and modify that slowly. but i cant figure out how to begin specifically with oxygenos? it doesnt appear as if they release their source code anymore. could anyone please point me in the right direction? thank you
Click to expand...
Click to collapse
Hi,
First of all, OnePlus do release their source code. But if you want to modify your phone and keep OxygenOS, you don't look it the right place.
With root you can have a lot more possibilities for customization, so I'll advice you to check Magisk (a root manager/ customization tool with which you can install modules).
If you want to theme your device you can use Substratum, and install themes from the Play Store.
Search about them and give them a try if you want to
Raiz said:
Hi,
First of all, OnePlus do release their source code. But if you want to modify your phone and keep OxygenOS, you don't look it the right place.
With root you can have a lot more possibilities for customization, so I'll advice you to check Magisk (a root manager/ customization tool with which you can install modules).
If you want to theme your device you can use Substratum, and install themes from the Play Store.
Search about them and give them a try if you want to
Click to expand...
Click to collapse
thank u for getting back to me! i took a look at their github page but it said they stopped releasing the source code because it can be found elsewhere, and i cant find where exactly that is. i dont want to modify the OS as is (root it and customise that way), i mean getting the source code, changing, removing and adding things and then flash my own custom flavour of oxygenOS onto my phone. i figure going with what comes with my phone is best when getting into android development so that there are as few compatibility issues as possible. would you be able to point me exactly how i might obtain the source code? it would be very cool my dude
kieran_buffet said:
thank u for getting back to me! i took a look at their github page but it said they stopped releasing the source code because it can be found elsewhere, and i cant find where exactly that is. i dont want to modify the OS as is (root it and customise that way), i mean getting the source code, changing, removing and adding things and then flash my own custom flavour of oxygenOS onto my phone. i figure going with what comes with my phone is best when getting into android development so that there are as few compatibility issues as possible. would you be able to point me exactly how i might obtain the source code? it would be very cool my dude
Click to expand...
Click to collapse
I hope you're familiar with git. I believe this is what you're looking for. https://github.com/OnePlusOSS
Spaceminer said:
I hope you're familiar with git. I believe this is what you're looking for.
Click to expand...
Click to collapse
i am indeed familiar with git, but i dont exactly understand what i am wanting from that page. i want the full source code to oxygenos and the kernal/binary specific packages for my phone. i previously found this site before but to my knowledge what is on there doesnt get me the source code. am i missing something? thank you for your helps
kieran_buffet said:
i am indeed familiar with git, but i dont exactly understand what i am wanting from that page. i want the full source code to oxygenos and the kernal/binary specific packages for my phone. i previously found this site before but to my knowledge what is on there doesnt get me the source code. am i missing something? thank you for your helps
Click to expand...
Click to collapse
Check under the Android section on that page. Which specific OnePlus device do you have? There are many of them. I can help you find it if I know your model.
Spaceminer said:
Check under the Android section on that page. Which specific OnePlus device do you have? There are many of them. I can help you find it if I know your model.
Click to expand...
Click to collapse
i see where you mean. but it seems like they stopped doing these releases. on their latest release (11 months ago) they said; "based on conversations we had with our dev community and the fact that we have only made few changes on AOSP(Qualcomm BSP) device tree, we will not be releasing AOSP device trees for future devices, the community can get the baseline from our device and get the source code from Qualcomm."
"the community can get the baseline from our device and get the source code from Qualcomm." i have no idea where to get what they are talking about.
i have the oneplus 8 pro
kieran_buffet said:
i see where you mean. but it seems like they stopped doing these releases. on their latest release (11 months ago) they said; "based on conversations we had with our dev community and the fact that we have only made few changes on AOSP(Qualcomm BSP) device tree, we will not be releasing AOSP device trees for future devices, the community can get the baseline from our device and get the source code from Qualcomm."
"the community can get the baseline from our device and get the source code from Qualcomm." i have no idea where to get what they are talking about.
i have the oneplus 8 pro
Click to expand...
Click to collapse
They're probably referring to CAF sources for the Qualcomm bit. The baseline part is probably a reference to the script that's in the Android section. This is the closest thing to what you're after that I can find.
https://github.com/AndroidBlobs/device_oneplus_OnePlus8Pro
https://github.com/AndroidBlobs/vendor_oneplus_OnePlus8Pro
https://github.com/codeauroraforum (CAF)
Spaceminer said:
They're probably referring to CAF sources for the Qualcomm bit. The baseline part is probably a reference to the script that's in the Android section. This is the closest thing to what you're after that I can find.
https://github.com/AndroidBlobs/device_oneplus_OnePlus8Pro
https://github.com/AndroidBlobs/vendor_oneplus_OnePlus8Pro
https://github.com/codeauroraforum (CAF)
Click to expand...
Click to collapse
ah yes. my brain has clicked with the baseline part, i would plug my phone in and it would use adb to extract the "baseline"? i understand this process. is what i am asking for difficult? perhaps i am better off taking the kernal files for my phone and integrating it with stock android that i would build and practicing with that? i really appreciate your effort but this "android blobs" is apparantly for reference only, i have no idea what android blobs is. i went into this knowing oneplus isnt extremely AOSP friendly compared to Sony for example, but i am going to push on. do you have any advice? this doesnt appear to be a friendly introduction into existing OS modification by sticking with OxygenOS