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!

Difference between unofficial caf and official cm nightlies

Hey guys! The title says it all. I have read some topics about caf and I've understood that it has better support of qualcomm hardware but at the same time has no off opo libraries? Can you please tell me all of the difference between these versions? Thanks!

Release Of Kernel Sources & Custom Rom Development ?

Will Xiaomi release kernel sources fully for this smartphone & therefore able to have active rom development (including Android M 6.0 roms) in the near future ?
(Kernel sources for the Xiaomi Mi3 & Mi4 were released very late and not in full and are the reason I believe that many Lollipop roms for these devices are not stable).

I think it depends on whether the device goes international. They were quick to release the sources for the Mi4i, and that is the only phone they officially sell internationally. That said, at least it uses the most common SOC of 2015.

Does it help that it has the same soc as the nexus 5x?

ermacwins said:
Does it help that it has the same soc as the nexus 5x?
Click to expand...
Click to collapse
It helps a little bit maybe, but the problem is all the other stuff inside the phone is different. You still need proper sources from Xiaomi.
M.

Do Xiaomi devices have root "built-in" ?
I'm interested in ROM development, too, but for the first months having root would be enough.

Giocarro said:
Do Xiaomi devices have root "built-in" ?
I'm interested in ROM development, too, but for the first months having root would be enough.
Click to expand...
Click to collapse
I have seen a guide on MIUI forum: "How to flash TWRP Recovery and Super Su(Root) on Xiaomi Mi4C"

Having access to kernel will also mean ir blaster will work on custom roms?

ermacwins said:
Having access to kernel will also mean ir blaster will work on custom roms?
Click to expand...
Click to collapse
Don't count on that. Many device that have kernel source and ir blasters still don't work on aosp based roms. Due to all the drivers for the hardware being closed sourced.

zelendel said:
Don't count on that. Many device that have kernel source and ir blasters still don't work on aosp based roms. Due to all the drivers for the hardware being closed sourced.
Click to expand...
Click to collapse
When we say kernel source, is that pertaining to the soc?

ermacwins said:
When we say kernel source, is that pertaining to the soc?
Click to expand...
Click to collapse
The kernel covers all aspects of the device in one form or another.

zelendel said:
The kernel covers all aspects of the device in one form or another.
Click to expand...
Click to collapse
Let's say xiaomi is taking long to release their kernel source but the source for nexus 5x soc is out, would that be enough for aosp rom?

ermacwins said:
Let's say xiaomi is taking long to release their kernel source but the source for nexus 5x soc is out, would that be enough for aosp rom?
Click to expand...
Click to collapse
No it won't. You will also need the device tree for this device. It's not how long it takes for them to release it that I would be worried about. It's if the source is complete and not broken like they are known to release. They have a habit of release broken source to force users to use miui. If you look at other devices from this OEM it takes months some times a year before they release it and when they do it is broken and devs have to take weeks to get it even remotely working. Then there are still bugs that are never fixed.

zelendel said:
No it won't. You will also need the device tree for this device. It's not how long it takes for them to release it that I would be worried about. It's if the source is complete and not broken like they are known to release. They have a habit of release broken source to force users to use miui. If you look at other devices from this OEM it takes months some times a year before they release it and when they do it is broken and devs have to take weeks to get it even remotely working. Then there are still bugs that are never fixed.
Click to expand...
Click to collapse
So having an aosp based rom as a daily driver is out of the question?

ermacwins said:
So having an aosp based rom as a daily driver is out of the question?
Click to expand...
Click to collapse
isn't the Broken OS ROM by TS Team AOSP based ?

Of interest:
[News] Mi 3/4/Note Kernel Source Code Released! Next to Be, Mi Note PRO, Mi 4c/S:
http://en.miui.com/thread-235127-1-1.html

Don't sceptical, I reconstruct Redmi 2 kernel source without any help from Xiaomi. They released Redmi 2 kernel source for KitKat when my device already run "fully open source" and almost bug free Marshmallow :laugh:

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

New linux kernel 4.9 for Snapdragon 625 and kernel and HAL source code

Great news fron Weibo, thanks for Mokee's developer XiNGRZ's share.
New linux kernel 4.9 for Qualcomm Snapdragon 625 and kernel and HAL source code of Android 9
http://caf.mokeedev.com/?version=9
https://wx1.sinaimg.cn/large/4b263fe4gy1futf5hw8wmj21hs0a2gt0.jpg
https://m.weibo.cn/status/4279258651583321
I don't know how to upload the picture, so only can give you the website's hyperlink

Yes! Looking in the CAF sources page (https://wiki.codeaurora.org/xwiki/bin/QAEP/release) you can see that kernel 4.9 for msm8953 and msm8953pro exists since Oreo ( LA.UM.6.6.2.r1-04200-89xx.0 is yet based on kernel 4.9 and CAF released it in 19/07/2018) and it was based on Linux 4.9.82, now with Android 9 it's based on Linux 4.9.112.
So, long life to all these devices that has this SoC!
But, for Pie there are 2 tags and one is still based on kernel 3.18 (to be more precise, 3.18.115, LA.UM.7.6.r1-02000-89xx.0 ) and the other one is at kernel 4.9 (4.9.112, LA.UM.7.6.2.r1-03000-89xx.0 ). I think we can see some ROMs with kernel 4.9 in the next months, but for now we stay on 3.18 while waiting they make perfectly working 4.9.

matteo0026 said:
Yes! Looking in the CAF sources page (https://wiki.codeaurora.org/xwiki/bin/QAEP/release) you can see that kernel 4.9 for msm8953 and msm8953pro exists since Oreo ( LA.UM.6.6.2.r1-04200-89xx.0 is yet based on kernel 4.9 and CAF released it in 19/07/2018) and it was based on Linux 4.9.82, now with Android 9 it's based on Linux 4.9.112.
So, long life to all these devices that has this SoC!
But, for Pie there are 2 tags and one is still based on kernel 3.18 (to be more precise, 3.18.115, LA.UM.7.6.r1-02000-89xx.0 ) and the other one is at kernel 4.9 (4.9.112, LA.UM.7.6.2.r1-03000-89xx.0 ). I think we can see some ROMs with kernel 4.9 in the next months, but for now we stay on 3.18 while waiting they make perfectly working 4.9.
Click to expand...
Click to collapse
Nice ! I love my sd625 device, good to know it's not left behind with an old Kernel.
Do you think this Kernel could improve performance and battery life ? Maybe make this chip even more efficient

Redmi4power said:
Nice ! I love my sd625 device, good to know it's not left behind with an old Kernel.
Do you think this Kernel could improve performance and battery life ? Maybe make this chip even more efficient
Click to expand...
Click to collapse
No, I think it just improves security. But it's yet a big step for sd625

matteo0026 said:
No, I think it just improves security. But it's yet a big step for sd625
Click to expand...
Click to collapse
It does improve performance and battery life. Main thing, amongst other things like improved security and way newer drivers, is the EAS.
Our devs are already working on 4.9 kernel for Mi A1, already testing it and recently released experimental builds and even now it's no comparison to 3.18 in it's current state, it's not even fair to compare.

airidosas252 said:
It does improve performance and battery life. Main thing, amongst other things like improved security and way newer drivers, is the EAS.
Our devs are already working on 4.9 kernel for Mi A1, already testing it and recently released experimental builds and even now it's no comparison to 3.18 in it's current state, it's not even fair to compare.
Click to expand...
Click to collapse
I saw that thread on Mi A1, devs are doing a good work. And do you think that EAS could be usable on our SoC too? If yes, I know that improves much the battery life

matteo0026 said:
I saw that thread on Mi A1, devs are doing a good work. And do you think that EAS could be usable on our SoC too? If yes, I know that improves much the battery life
Click to expand...
Click to collapse
Of course, EAS is impremented by Qcom itself on 4.9, so it is properly optimized and calibrated. Even now I don't need to adjust anything, just left it as it is.
What's more interesting is what OEM is going to do - be with 3.18 or move on to 4.9. Knowing Xiaomi, I'm guessing they'll stay on 3.18.

airidosas252 said:
Of course, EAS is impremented by Qcom itself on 4.9, so it is properly optimized and calibrated. Even now I don't need to adjust anything, just left it as it is.
What's more interesting is what OEM is going to do - be with 3.18 or move on to 4.9. Knowing Xiaomi, I'm guessing they'll stay on 3.18.
Click to expand...
Click to collapse
Ehm, yes I they stay on 3.18 because there are 3.18 tags based on Pie for msm8953_64. I'm thinking to do 4.9 for p2, but... I don't know what I have to do... I haven't knowledges, but I want to give a try.

matteo0026 said:
Ehm, yes I they stay on 3.18 because there are 3.18 tags based on Pie for msm8953_64. I'm thinking to do 4.9 for p2, but... I don't know what I have to do... I haven't knowledges, but I want to give a try.
Click to expand...
Click to collapse
Some crucial stuff might need backporting for sure, you should ask around other people. They might help you out. I'm out of development game, too busy doing other things in my life, so can't comment on this much more.

matteo0026 said:
Ehm, yes I they stay on 3.18 because there are 3.18 tags based on Pie for msm8953_64. I'm thinking to do 4.9 for p2, but... I don't know what I have to do... I haven't knowledges, but I want to give a try.
Click to expand...
Click to collapse
p2 community is with you. we can help you with testing. go ahead ???

Any update?

There will be advantage ?
Is it easy to port ?

Can not download source code for msm8953_64

Ask in tissot forum may be they'll know something

when its coming?
so excited:fingers-crossed:

ZJ_CN said:
Great news fron Weibo, thanks for Mokee's developer XiNGRZ's share.
New linux kernel 4.9 for Qualcomm Snapdragon 625 and kernel and HAL source code of Android 9
http://caf.mokeedev.com/?version=9
https://wx1.sinaimg.cn/large/4b263fe4gy1futf5hw8wmj21hs0a2gt0.jpg
https://m.weibo.cn/status/4279258651583321
I don't know how to upload the picture, so only can give you the website's hyperlink
Click to expand...
Click to collapse
any update ?
SD625 kernel 4.9

Hello, please help me find the kernel sources CAF for msm8953_64 3.18.71-74, thanks in advance
---------- Post added at 02:28 PM ---------- Previous post was at 02:21 PM ----------
Hello, please help me find the kernel sources CAF for msm8953_64 3.18.71-74, i have compile kernel for device billion capture +, thanks in advance

Would like to breath new life into my Lenovo P2, but I guess 4.9 will remain a dream?