When wil it be possible to port marshmallow to our device? i've seen it with the nexus 4 and a few other devices.
and if it's not possible Why not? and why others phones do?
thanks,
We've only got a few developers at the moment. (Could count them on one hand.) Give it a bit before the device gains more popularity. I've also asked similar as I'd like to build aosp 6.0 but am unsure if we need to wait for Motorola 6.0 kernel source.
Related
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!
Hey,
i'm just curious about what the title describes. First of all.
What do i really need:
-kernel sources
-binary blobs (extractable)
-recovery / boot.img (extractable)
Let us just talk about the fairphone 2. Additional to the things mentioned we get the full source code of the OS (which i do not need?).
Where do the difficulties lie? For my understanding we just take the kernel sources, the official cyanogenmod (e.g.) source code, the binary blobs and the recovery / boot.img.
How difficult would it be to port Cyanogenmod to the fairphone 2.
Why is it difficult to port a device with existing (again cyanogenmod just as an example) cyanogenmod to a newer Cyanogenmod (Android) version?
I ask this to estimate/evaluate/judge (don't know the right term) the effort needed to do this. I think i'd be able to do that if i put enough work into it (i "speak" c and java), but i just need some answers.
Especially for example why it is more difficult to port Android 6 instead of Android 5 (which is the currently running Android version)
Thanks!
bigCrash
Has nobody an answer? Just one?
Im specifically interested in why it is more difficult to port e.g. cyanogenmod if there is only an older version of stock android and how important the kernel is? Why do we need kernel sources? Can't one just self-compile a kernel.
Where are the limits if i have a device running 4.2. Why can it possibly run 5.1 but not 6? Is the kernel limiting? Or only the effort to realize such a thing.
Thanks!
bigCrash
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?
Will we get it?Im 1000% sure the phone is capable of running it.I believe somebody must mess with the RIL,the P8 devs say they have some issues with it(while building cm based roms),anyway flashable rom is easily to be made.
Here I found the source of the phone: http://emui.huawei.com/en/plugin.php?id=hwdownload&mod=detail&mid=70
Even if we dont have source,there is still a chance that we can make custom rom for it,just like broadcom grand neo got cm11.
''Contrary to the popular belief, userspace driver source code is not always required to make an AOSP-based ROM as long as the proprietary binaries shipped with the device does not modify the API too heavily (or is from a very different version of Android). Instead of modifying the source code of the drivers, the Android source code was adapted to be able to use the proprietary binaries.'' - using this logic there is flyme os 5.1.1 in 4pda,which is also skinnned chinese rom,we might be able to port the newer emui from p9 or honor 7.
Edit:Just saw that there is android n beta for p9 based on emui 5.Anyone wanna give a shot porting it?
Are there actually any active developers?
I think it's possible but it will be so difficult for the devs to do such thing...
But I really hope that some one ports it for our phone
Sent from my H60-L04 using Tapatalk
hamzio7 said:
I think it's possible but it will be so difficult for the devs to do such thing...
But I really hope that some one ports it for our phone
Sent from my H60-L04 using Tapatalk
Click to expand...
Click to collapse
I think porting the android n beta for p9 should be possible,or if not the beta then when the official version comes out.It has kirin 955 and mali gpu,I think it can be crossported.It would be easier to port from the p8,but I think it wont get it too.
Practically replacing some libs and folders with the ones from the stock marshmallow,that did work with mtk chipsets,but Im new at the kirin stuff.
Can we expect Lineage OS to be released for realme X3? I have a feeling that it is one of the phones that can really benefit from lineage OS as despite having excellent specifications it is bogged down by terrible software support by realme?
jaidosajh said:
Can we expect Lineage OS to be released for realme X3? I have a feeling that it is one of the phones that can really benefit from lineage OS as despite having excellent specifications it is bogged down by terrible software support by realme?
Click to expand...
Click to collapse
There is no way to know if or when any device will get any kind of custom ROMs. That is a matter of whether someone with the knowledge to create custom ROMs owns one of those devices or not and whether or not they choose to build a ROM for that device and that is only "if" the stock source code has been made available to the public. If the stock source code has not been made available to the public, custom ROMs cannot be built for the device because stock source code is required in the building process.
The short answer is you will just have to wait and see or take it upon yourself to try building LineageOS for your device for yourself. Trying to build it yourself might get you there faster because you might be in for a long wait if you wait for someone else to do it or may never happen at all.