Database Info

[Q] Building AOSP (not CM) for the OPO, is it possible?

Hi, I've just received my OPO on the 27th. I was really interested in Android development when I had my Nexus 5 and started building my own AOSP ROM, I've been looking into doing the same for the OPO but am unable to find an actual way of building AOSP with Google's code. I know OPO released their AOSP kernel source here: https://github.com/OnePlusTech/android_kernel_oneplus_one and CyanogenMod has thiers here: https://github.com/CyanogenMod/android_kernel_oneplus_msm8974 but I'm unable to work out a way of including these into my AOSP build and I would prefer to not build CM.
Note: I'd like to build AOSP myself, I'm fully aware that there is a current official OPO build available.
Thanks in advance,
Lewis

LewisD94 said:
Hi, I've just received my OPO on the 27th. I was really interested in Android development when I had my Nexus 5 and started building my own AOSP ROM, I've been looking into doing the same for the OPO but am unable to find an actual way of building AOSP with Google's code. I know OPO released their AOSP kernel source here: https://github.com/OnePlusTech/android_kernel_oneplus_one and CyanogenMod has thiers here: https://github.com/CyanogenMod/android_kernel_oneplus_msm8974 but I'm unable to work out a way of including these into my AOSP build and I would prefer to not build CM.
Note: I'd like to build AOSP myself, I'm fully aware that there is a current official OPO build available.
Thanks in advance,
Lewis
Click to expand...
Click to collapse
It's advisable that you create your own tree from the CAF MSM8974 using CM GPS and other drivers and build CAF AOSP. Otherwise, it's close to impossible/very difficult. Pure AOSP is again near impossible/very difficult for non nexus devices.

Thank you very much for the reply, so building AOSP is pretty much impossible then?
I was having a look around on the internet last night and came across this: http://developer.sonymobile.com/kno...uild-aosp-kitkat-for-unlocked-xperia-devices/
Would there be a way of adapting this guide to allow for an easier build process of AOSP for our device? The other confusion that I face is if it's impossible to build AOSP for the OPO then how are ROMs such as this available?

LewisD94 said:
Thank you very much for the reply, so building AOSP is pretty much impossible then?
I was having a look around on the internet last night and came across this: http://developer.sonymobile.com/kno...uild-aosp-kitkat-for-unlocked-xperia-devices/
Would there be a way of adapting this guide to allow for an easier build process of AOSP for our device? The other confusion that I face is if it's impossible to build AOSP for the OPO then how are ROMs such as this available?
Click to expand...
Click to collapse
VanirAOSP uses CM trees as of now. Again, CAF AOSP is basically AOSP for non nexus Qualcomm devices., and any experienced dev can whip up a tree and get it working. Also, reaally good devs can/may be able to port AOSP if they wanted. It's a matter of whether they want to do it or not.
That link is for Sony devices only because Sony already provides CAF trees as an OEM so devs can build.

rudi_j7 said:
VanirAOSP uses CM trees as of now. Again, CAF AOSP is basically AOSP for non nexus Qualcomm devices., and any experienced dev can whip up a tree and get it working. Also, reaally good devs can/may be able to port AOSP if they wanted. It's a matter of whether they want to do it or not.
That link is for Sony devices only because Sony already provides CAF trees as an OEM so devs can build.
Click to expand...
Click to collapse
Ah yes, I see what you're saying now. Thanks for clearing this up for me! I just noticed when I looked at the VanirAOSP ROM thread that it states CM for it's credits, haha. I apologize for my ignorance.

Hello
I would like to create my first rom for oneplus one but without modification from OMNI or CM, basically vanilla rom. but I have some doubts.
Can I create a rom based on AOSP with device tree from OMNI/CM right?
Thanks!

Will community continue to develop to this phone after cyanogenmod is done in 6 days?

Will community continue to develop to this phone after cyanogenmod is done in 6 days? As some of you may know Cyanogen inc had lots of issues so they decided to shutdown the company after 7 years of work. Some of the official devs started to tease a cyanogenmod reborn, named Lineage OS. You can find them on twitter, facebook, google+ and their new site lineageos.org . The site is still wip but i hope that Lineage OS will be developed for this phone and i dont have to throw my phone off the window just cause i dont have the latest update

As the source code will still available and the team is willing to continue, I see no reason for stopping, as long as our device maintainers support this device. But it may slow down a bit for a while, it's been a major transition after all. And rest of the custom ROMs might get affected too. Better to stay tuned in every thread possible, ours is not so big
Broadcasted from Zeta Reticuli

Gravemind2015 said:
As the source code will still available and the team is willing to continue, I see no reason for stopping, as long as our device maintainers support this device. But it may slow down a bit for a while, it's been a major transition after all. And rest of the custom ROMs might get affected too. Better to stay tuned in every thread possible, ours is not so big
Broadcasted from Zeta Reticuli
Click to expand...
Click to collapse
youre right. i guess ill make sure im in the latest nightly in the next days if anything happens

The question is will CyanogenMod continue to live now that they have lost all support from Cyanogen, including build servers, monetary, and technical support... CyanogenMod will be renamed to LineageOS... The biggest problem is all development on Moto G 2015 (and many other Moto devices) is based on CyanogenMod, and there is no other source at this time. How will that play out? We don't know yet...
A well formed (and informed) answer from Stack Exchange's Android Enthusiast group:
CM's own blog is unreachable now, but XDA-Developers already summed it up and clarified some important bits:
All monetary and infrastructural support for CyanogenMod from Cyanogen Inc. will cease. -> CyanogenMod will no longer receive nightly builds after December 31st... unless the team finds another host to build nightlies.
The CyanogenMod team will not continue official development on the project.
CyanogenMod will rebrand as LineageOS.
Since it's clear that Cyngn is going in a new direction, Cyanogen OS will almost certainly have no future, since it's not community-driven in the first place. CyanogenMod, on the other hand, will live a bit longer, until Lineage dawns (or fails).
Click to expand...
Click to collapse

Wasn't Omnirom a fork of CM after the creation of Cyanogen Inc? As I recall all the developers were upset over going commercial and the future of cyanogenmod. Lineage OS would in essence be a fork of Cyanogenmod as well. I think it will really depend on whether they can find funding for some build infrastructure and how many developers jump on board.

acejavelin said:
The question is will CyanogenMod continue to live now that they have lost all support from Cyanogen, including build servers, monetary, and technical support... CyanogenMod will be renamed to LineageOS... The biggest problem is all development on Moto G 2015 (and many other Moto devices) is based on CyanogenMod, and there is no other source at this time. How will that play out? We don't know yet...
A well formed (and informed) answer from Stack Exchange's Android Enthusiast group:
Click to expand...
Click to collapse
The repositories are being mirrored (probably 'forked' is the correct term) into linageOS so I think we'll have a copy of our source code. And they said the source code for CM would still be available.
https://github.com/LineageOS?tab=repositories
Broadcasted from Zeta Reticuli

BTW, it isn't ending on Dec 31st like most people thought... it's ending prior to Dec 31st... They lost DNS and Jenkins yesterday, the blog is gone (so no reference to the official posts), official Cyanogen and CyanogenMod websites are down, and probably more that I haven't noticed mentioned yet are gone already.
But https://download.cyanogenmod.org is still live.

What would be the status of other custom roms that are based on cyanogenmod. Would they be affected ?

aa1010 said:
What would be the status of other custom roms that are based on cyanogenmod. Would they be affected ?
Click to expand...
Click to collapse
Of course...ALL ROMs for this device, except stock based ones, use the CM device tree and base code... Will LineageOS replace that? Right now it appears that way but time will tell.
To be honest, if CM/LineageOS doesn't make it... Probably 80℅ of all ROMs out there will disappear as we know them today, we really don't know the long-term effects this will have on the ROM community.

Some dumb questions:
1. LineageOS is the same team as CM?
2. There's a release date for the lineageOS and it will be compatible with moto g 2015?
3. To keep updated is better to wait or change to an AOSP based rom since AOSP will still be releasing?

h0ttentot said:
Some dumb questions:
1. LineageOS is the same team as CM?
2. There's a release date for the lineageOS and it will be compatible with moto g 2015?
3. To keep updated is better to wait or change to an AOSP based rom since AOSP will still be releasing?
Click to expand...
Click to collapse
1.2.3 i dunno but i hope everything will be fine

h0ttentot said:
Some dumb questions:
1. LineageOS is the same team as CM?
2. There's a release date for the lineageOS and it will be compatible with moto g 2015?
3. To keep updated is better to wait or change to an AOSP based rom since AOSP will still be releasing?
Click to expand...
Click to collapse
1. Yes, to a point... for more information look at http://lineageos.org/Yes-this-is-us/
2. We don't know yet, they do not have build servers at the moment
3. I would wait, there is little chance of getting a working AOSP device tree at this time, but we will just have to wait and see.
The point is, right now we don't know exactly how this is all going to play out... we need to have patience and just see what happens.
---------- Post added at 01:29 PM ---------- Previous post was at 01:12 PM ----------
I would suggest everyone following this thread, look here: http://forum.xda-developers.com/2015-moto-g/general/cyanogenmod-to-lineageos-t3526944

Porting B2G to moto g3

Hi Folks,
I'm trying to port B2G to my moto g3. I was referring to this doc (https://developer.mozilla.org/en-US/docs/Archive/B2G_OS/Porting_B2G_OS/basics). However some of the things mentioned in this doc are not clear to me. Could you please help me with the below issue.
I'd like to build the AndroidKernel from source. So where should I include the below lines? Is it in this file?
https://github.com/LineageOS/android_device_motorola_osprey/blob/cm-14.1/rootdir/etc/init.target.rc
HTML:
on early-init
start ueventd
import /init.b2g.rc
Also if I understood correctly. building the kernel from source doesn't require to unpack , edit the init.rc file and repack the kernel from the device. Could you please confirm this?
Thanks,
Arun

Hi Arun,
I totally understand your frustration with this. You'd like to contribute to the Servonk project but first you need to port B2G to your phone or buy a new phone. Since the only other supported phones are the Z3 compact and Nexus 5, both of which are still relatively expensive secondhand, you want to use your Moto G3 which means first porting B2G to it.
So, I think there are two options you have:
1. Port direct from the AOSP code
2. Port from the CM12 code.
As Gerard said in telegram, porting from CM to B2G was never finalised so may actually require more work. However there may actually be more people here who can help you since people seem more familiar with CM than AOSP (in general, I know some people are very knowledgeable in both).
I see you've posted in the AOSP 7.1.1 kernel thread. Unfortunately, for the Servonk project you currently need a Lollipop based build, so 5.x AOSP kernel or CM12.x.
It might be worth asking a mod to move this thread into one of the development sub-forums.
As you know, this is the limit of my knowledge, but I really hope you find some success, if would be great if you could contribute to the Servonk project.
Your last option is to use the desktop build of Servonk, based on Glutin instead of Gonk, but I understand that you really want to get Servonk working on your phone.
Best of luck

[ROM] [UNOFFICIAL] LineageOS 14 for Meizu M5C [MT6737m]

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

How to create a distribution of crDroid for the tablet Teclast t40 pro (rooted, unlocked bootloader)

Hello,
Could somebody give me links, initial instructions or an overview of how to adapt the crDroid custom rom to be able to install also on the Teclast t40 pro ?
Or in other words... Which changes should be made (and a general how-to) to that rom once obtained its source code, to add support for a new device, in this case that tablet ?
I am a software developer in .NET with some linux experience also, and this could give me the opportunity to learn something big'n new...
Thanks in advance !

It's so sad that nobody can give me a hand on this; At least a general intro. Ok, I will forget about it and I'll change my little goals in life to something more useful and productive.
Have a nice day.

Hello try this
[GUIDE] Build crDroid ROM from source
Because I saw some requests for a build guide for crDroid (ROM with many added features based on CM) I decided to make one. Please report if it worked. If you have errors I will try my best to resolve them. Please read everything carefully...
forum.xda-developers.com
and this below this information below.
Thanks

I hope you are very successful in this process.

I hope you are very successful in this process.