Since the device specs meet almost the same to Nexus 5, is it possible to build hammerhead AOSP builds (as is, or official AOSP) for our Note 3?
I was thinking since the M developer preview 3 is out, if anyone could port it for our device.
puppynaz said:
Since the device specs meet almost the same to Nexus 5, is it possible to build hammerhead AOSP builds (as is, or official AOSP) for our Note 3?
I was thinking since the M developer preview 3 is out, if anyone could port it for our device.
Click to expand...
Click to collapse
It would be still difficult, I think we should wait for Google to release M source code and then the developers work from there
Related
Hi, I have seen news about Oppo releasing the Kernel Source and supporting the AOSP community (the same Sony and HTC right now).
My question is, when Android 5.0 and a CM11 is released, does this source or information already released today about the device works for future releases of AOSP based ROMs without the support of the company?
Trying to be clear, Oppo (Sony and HTC too...) release some source today, but the next year they don't support this model, can the AOSP ROMs implement a new stable version using that last year released source from a prior Android version?
Thanks
pedroren said:
Hi, I have seen news about Oppo releasing the Kernel Source and supporting the AOSP community (the same Sony and HTC right now).
My question is, when Android 5.0 and a CM11 is released, does this source or information already released today about the device works for future releases of AOSP based ROMs without the support of the company?
Trying to be clear, Oppo (Sony and HTC too...) release some source today, but the next year they don't support this model, can the AOSP ROMs implement a new stable version using that last year released source from a prior Android version?
Thanks
Click to expand...
Click to collapse
No one knows. We would hope so, but no one would really know. Maybe.
Sent from my Oppo Find 5
kernel-wise - the cyanogenmod team has been able to merge it with the Qualcom sources, so if Qualcom keeps it up to date (most likely yes), then that's no problem (also, nexus 4 shares a lot of the same underlying hardware: CPU/SoC, GPU... that device will get updates, which could be ported over)
http://forum.xda-developers.com/showpost.php?p=40671515&postcount=5
proprietary library-wise - maybe? sometimes, they're compatible cross-android version, sometimes not, and you have to do workarounds to make it work on the new version.... could also steal libraries from other devices (see nexus 4 again)
Once lollipop code is all modified and what have you, will the groundwork make the transition from lollipop to android m be smoother than from kitkat to lollipop? I ask because at this point once lollipop is ready, m will probably be close to release. Just curious, as I just put omni back on an old device but holding out on a custom rom for my nexus 6 and will consider omni once its ready. Its very stable. Thanks.
ryancell said:
Once lollipop code is all modified and what have you, will the groundwork make the transition from lollipop to android m be smoother than from kitkat to lollipop? I ask because at this point once lollipop is ready, m will probably be close to release. Just curious, as I just put omni back on an old device but holding out on a custom rom for my nexus 6 and will consider omni once its ready. Its very stable. Thanks.
Click to expand...
Click to collapse
Not a single clue. UI/UX improvements will hopefully require less work.
The CAF AV/native mess that has held up Omni so long would still be a problem - to the point where maxwen and myself are discussing/attempting an alternate approach. Originally I felt that it was a horrible cop-out/laziness hack, but the more I look at the utter ifdef hell that is CAF vs. AOSP frameworks/av - I think it may be just easier to have two separate frameworks/av setups kind of like we have multiple variants of hardware/qcom/[media,audio,display] - although I intend to keep frameworks/av to only two variants for as long as possible (only exception might be if MTK ever stops sucking and provides platform source - but so far instead our best bet for MTK devices is Android One, which will have some degree of AOSP support.)
will cyanogen port this dev version of Android N.. so that our devs can port it to redmi2?
There's no sense in spend time to port a leaked beta version of Android.
JoaoMarcos said:
There's no sense in spend time to port a leaked beta version of Android.
Click to expand...
Click to collapse
thats not leaked beta....google official released beta version.
only for nexus devices with closed source,as far i porting goes,you need a nexus device with same chip set."N" builds will only be up after official release and publishing of codes in third quarter of 2016
This is an invitation to all developers, compilers and testers of Moto X (2014).
We know that probably our device will not receive officially Nougat update and this is really bad, assuming that our strong Snapdragon 801 can smoothly run without any problems.
My suggestion it's to all developers and compilers from any country work together to sync AOSP from Nougat, adapt device tree and bring up our first AOSP 7.0 rom.
I know that CyanogenMod is working on CM14 for victara... But the idea is bring up pure Android. I never see any pure AOSP rom for our device and would be awesome if we have this now. CM14 maybe will delay a bit and I think that all users here want to feel Nougat experience
Some rumours at internet had saying that Snapdragon 800/801 will not have drivers for Nougat... But I know that this is possible because Nexus 5 had Snap 800 and developers already bring an functional AOSP (link: http://forum.xda-developers.com/google-nexus-5/orig-development/wip-aosp-nougat-nexus-5-t3446875 ). Our developers can check device tree from Nexus 5... See their adaptions in device tree for working Nougat and try to do the same for our Moto X. Maybe disabling Vulkan API for now and we can use same drivers and device tree of Marshmallow!
That's all guys, thanks for reading and we are really expecting an AOSP Nougat for our Moto X before CM14!
The One Plus One (Snapdragon 801) has AOSP Nougat build. Among other devices. The Moto X (2014) is a smaller development community. I was not even expecting CM to build CM14 for this device (see below). It's going to take time
We haven't yet got a Snapshot build (stable release) of Cm13. Small steps.
Visi0nofExcellence2 said:
The One Plus One (Snapdragon 801) has AOSP Nougat build. Among other devices. The Moto X (2014) is a smaller development community. I was not even expecting CM to build CM14 for this device (see below). It's going to take time
We haven't yet got a Snapshot build (stable release) of Cm13. Small steps.
Click to expand...
Click to collapse
I agree, we have small team of developers. And this one more objective of this post: attract more developers.
I think that Moto X doens't have too much developers because we had officially updates since Android 4.4... Numbers of people that goes to custom ROMs is really minimal, because the stock of Motorola doens't give reasons to search custom ROMs (like bloatwares or lags).
But now, we are going to road of needing custom ROMs. Now we have more reasons to search for these ROMs, because we'll probably not receive Nougat. Moto X2 XDA Forum go clog of peoples trying to got Nougat.
I hope for a "pure" aosp too, like the "fake rom" for Nexus 4.
Enviado desde mi XT1095 mediante Tapatalk
cpvm said:
I hope for a "pure" aosp too, like the "fake rom" for Nexus 4.
Enviado desde mi XT1095 mediante Tapatalk
Click to expand...
Click to collapse
Would be awesome
Pls devs we need some nougat !!!
Visi0nofExcellence2 said:
The One Plus One (Snapdragon 801) has AOSP Nougat build. Among other devices. The Moto X (2014) is a smaller development community. I was not even expecting CM to build CM14 for this device (see below). It's going to take time
We haven't yet got a Snapshot build (stable release) of Cm13. Small steps.
Click to expand...
Click to collapse
Dan(Invisiblek) is working on CM14 for Victara. http://review.cyanogenmod.org/#/q/project:CyanogenMod/android_device_motorola_victara+branch:cm-14.0
and our CM13 Nighly builds is very close to a Snapshot build NO BUGS for me xt1092 very stable as Snapshot build.
Yes it's true . I have been using the nightly builds of CM 13 for Victara and it runs really smoothly. I would encourage developers to work on the Nougat ROM for Victara. We will appreciate it. Thanks
I really hope to see Nougat in this phone, sadly I have no knowledge to help in development, but for sure I will test as it become usable material (its my daily phone, so would be nice that alarm at least works as expected)
We already has an bootable CM14 guys! here's link: http://forum.xda-developers.com/showpost.php?p=68555035&postcount=100
Hello Guys after a lot of search i decided to port a pixel Experience Android Pie Rom for Nokia 5
But first I Need Nokia 5 Sources Code
CAN ANYONE PROVIDE THE SOURCES CODE.
HMD Global still not release it for Nokia 5. But what I know, is that the Moto G3 has the same specs as Nokia 5. Can we use it to replace the Nokia 5 source code?
Be ready coz i started port miui 10 theme
And i am 100% sure that i can make bug free rom
Rom will be ready for flashing before 5 Jan.
Jitender Baloda said:
Be ready coz i started port miui 10 theme
And i am 100% sure that i can make bug free rom
Rom will be ready for flashing before 5 Jan.
Click to expand...
Click to collapse
Sorry! But can I know how to do that? I really want to learn about porting and building rom. But I don't know how to begin.
After port miui 10 rom for nokia 5. I will guide you how to port.
Thank you! It will be better if you make a video, or we chat together
Is Pixel Experience even worth on such a phone? I think we're more in need of LineageOS, no? ;s
So you are porting two roms?
Jitender Baloda said:
After port miui 10 rom for nokia 5. I will guide you how to port.
Click to expand...
Click to collapse
stop giving us a fake hope like HMD did. it's already 8th january 2019.
Bro I'm port rom as well as testing the rom myself and cheking every bug. Thats why i take more time
But trust me i m try to provide this rom fully stable.
Can we use Nokia 6's source code and roms since it has the same hw like Nokia 5?
I'm porting the rom not build rom .as i know in porting rom case not required kernal sources
Waiting for this custom rom
Why HMD Global not release Nokia 5 source code? Of we can use Nokia 6 source code for Nokia 5?
If you have updated to android pie on your Nokia 5 ,
Since Nokia phone have stock Android experience ,
You just need to install the pixel 3 launcher port ,
XDA link :- https://www-xda--developers-com.cdn...launcher-google-assistant-search-bar-pixel-3/ , I don't know if this work on Oreo , it works great on my Nokia 5
Miscellaneous1 said:
If you have updated to android pie on your Nokia 5 ,
Since Nokia phone have stock Android experience ,
You just need to install the pixel 3 launcher port ,
XDA link :- https://www-xda--developers-com.cdn...launcher-google-assistant-search-bar-pixel-3/ , I don't know if this work on Oreo , it works great on my Nokia 5
Click to expand...
Click to collapse
The only bad thing is that when you go into the overview you can't see the apps at the bottom which is annoying and the stock launcher cannot be disabled so it runs in the background and uses up memory