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!

no more alternative rom....?

I saw different post where we can see, flashing magictrick file, that adb command work well to unlocked bootloader and to be able to install twrp ... and rooting oppo f1.... but there's no other rom to install... Should we wait only for the spectrum official project by oppo ?

i think ,just wait for cyanogen rom based on marshmallow...

The CM device tree is finished and has been done by Uberlaggydarwin. CM is now patiently waiting for Oppo to release the kernel source for the F1f. If you want to speed up the kernel source release by Oppo I suggest to start sending emails and demanding them. The more people do it the higher the chance Oppo will listen.

celoxocis said:
The CM device tree is finished and has been done by Uberlaggydarwin. CM is now patiently waiting for Oppo to release the kernel source for the F1f. If you want to speed up the kernel source release by Oppo I suggest to start sending emails and demanding them. The more people do it the higher the chance Oppo will listen.
Click to expand...
Click to collapse
We will do it...Ill send the one[emoji12]
Sent from my F1f using XDA-Developers mobile app

celoxocis said:
The CM device tree is finished and has been done by Uberlaggydarwin. CM is now patiently waiting for Oppo to release the kernel source for the F1f. If you want to speed up the kernel source release by Oppo I suggest to start sending emails and demanding them. The more people do it the higher the chance Oppo will listen.
Click to expand...
Click to collapse
I have the source (both Project Spectrum and ColorOS from Aprilish) , I'm just super busy so I haven't fully rebased it on Project Spectrum yet. Let me know if you want to help though

uberlaggydarwin said:
I have the source (both Project Spectrum and ColorOS from Aprilish) , I'm just super busy so I haven't fully rebased it on Project Spectrum yet. Let me know if you want to help though
Click to expand...
Click to collapse
Do you have the F1f kernel source too?
I was thinking about rebasing the R7S to Project Spectrum too but my first tests ended in the Camera constantly crashing. I don't think its a Camera Hal problem. Project Spectrum is still unstable and full of bugs. If they come out with a stable release a rebase would make more sense imho. For now I let the people use the PS aboot to unlock the device.

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

Oreo Kernel Source Request

As it was quite a success requesting the source code as a community last time, we should try to request for the oreo kernel too...
1. Go to the opensource website: http://opensource.samsung.com/reception/receptionSub.do?method=sub&sub=F&searchValue=sm-g955f
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 G955FXXU1ZQJJ source code (it's important that you mention the base)
6. Agree the terms and send it to samsung
7.Write something like Kindly release source for SM-G955F & G950F XXU1ZQJJ

Ansuel said:
As it was quite a success requesting the source code as a community last time, we should try to request for the oreo kernel too...
1. Go to the opensource website: http://opensource.samsung.com/reception/receptionSub.do?method=sub&sub=F&searchValue=sm-g955f
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 G955FXXU1AQJ1 source code (it's important that you mention the base)
6. Agree the terms and send it to samsung
7.Write something like Kindly release source for SM-G955F & G950F XXU1ZQJJ
Click to expand...
Click to collapse
They're not going to release a source for a closed beta I don't think, maybe when oreo drops officially yes as the source code thst was requested before was for official software available to everyone

sofir786 said:
They're not going to release a source for a closed beta I don't think, maybe when oreo drops officially yes as the source code thst was requested before was for official software available to everyone
Click to expand...
Click to collapse
erm don't we try and see the response?

Ansuel said:
erm don't we try and see the response?
Click to expand...
Click to collapse
Well, i support the effort i have a SM-G950U and just asked for them to release the source for the SM-G955F & SM-G950F. May the odds be ever in our favor!

TimelessPWN said:
Well, i support the effort i have a SM-G950U and just asked for them to release the source for the SM-G955F & SM-G950F. May the odds be ever in our favor!
Click to expand...
Click to collapse
Just increased our odds, albeit not by much, so good luck to us!

[ROM][TEST]Nexus 5X (Bullhead) HCE Always(off screen payment) Testing rom (AOSP OREO)

Hi.
I've edited android framework code to make HCE(card emulation) feature without turning the screen on.
But I have no device to test this feature because of samsung knox .
So I built a test rom for bullhead.
This rom is based on OPR5.170623.014.
And I want to get feedback about this rom
1. The off screen mobile payment (HCE) feature works well?
2. Then Please let me know the battery time is acceptable or not.
compared to AOSP.
Plus! I do not guarantee this rom is not work properly
If your device broke with my rom, I can't do anything for that
Download Link :
https://drive.google.com/file/d/1w-vO80Jo7O55uUeqCqG0Y83OFqToi7vs/view
Opensource :
https://github.com/HyungJu/hce-always
Apply this patch to frameworks/
Download Gapps for 8.0.0.
Thank you.

No offense, but I think whoever tests this may want to see the source code for whatever you changed.
In my case I wouldn't test this unless I looked at the code and then compiled it myself. Really, it's nothing personal.
The "chain of trust" of most ROMs is that you can easily reproduce the binary version that you can download elsewhere by building from the available source code instead if you wanted to.

Paul L. said:
No offense, but I think whoever tests this may want to see the source code for whatever you changed.
In my case I wouldn't test this unless I looked at the code and then compiled it myself. Really, it's nothing personal.
The "chain of trust" of most ROMs is that you can easily reproduce the binary version that you can download elsewhere by building from the available source code instead if you wanted to.
Click to expand...
Click to collapse
Thank you for your advice.
I uploaded a patch file that I made to github
https://github.com/HyungJu/hce-always
Thank you.

vendor.img..? opr5 14...?