As there hasn't been an AOKP release for a while I thought I'd compile an unofficial nightly with the 4.1.2 changes that have been merged into it.
As usual all credits go to the AOKP team and the respected developers as i've just compiled and released.
Nexus S only.
DOWNLOAD LINK:
http://d-h.st/Xaq
MD5 - 536e85215f3a9a8d3c16cef14b1eeb41
Have fun
Does anyone have a recent or mako specific guide on how to build Paranoid Android builds, I'd like to cherry pick a few smaller features into the already powerful ROM.
Would following the OmniRom guide and basically replacing the Omni values with the correct Paranoid Android values work out? Or is there other specific stuff I need to do?
I've got Ubuntu 13.04 & currently building OmniRom whenever I see there's a bit of a decent update but other then that I'm pretty much a noob .
http://forum.xda-developers.com/showthread.php?t=1863547
Basically just clone the PA source, add the mako specific stuff (kernel, device, and vendor from TheMuppets repo) and compile. If you have any other questions just ask in the thread a linked above.
Although I have used Android (phones & tablet) for about 4 years, I have only just started dipping my toes into the exciting world of rooting and mods. And so I have just wiped my Samsung Galaxy S3 and flashed the most recent Omnirom - a process which was so painless as to be almost pleasant!
It seems, however, that multiview/split screen is not available in this particular version of Omnirom (or if it is, it's so well hidden that I've not been able to find it!). So I'm wondering if it's possible to compile my own version of Omnirom from source, with just those parts of it I need. I used to compile linux kernels (before the days of loadable modules); can I do the same with Omnirom? That is, can I compile a version of Omnirom which might contain different fuctionailty that the nightly build?
Thanks!
It's pretty straightforward of you have a Linux box, and doable on Mac as well. There are great instructions on the OmniROM wiki. Plan on the source sync taking several hours (or overnight) the first time. Make sure you set up ccache so that subsequent builds go quickly.
http://docs.omnirom.org/Main_Page
Once you've built a straight-up version that works, you can branch and cherry-pick the multi-window patches from the OmniROM Gerrit instance.
---
Posted from whatever phone booted today
Okay Guys,
I am working hard to bring up Cyanogenmod to our beloved moto g.
But i am a bit Noobish in this field.
I have been reading guides and following the process.
So far I have setup the build environment and synced the latest repo from CM sources.
Now, further most imp step is Vendor, Kernal and Device tree.
I have found this so far, by searching this forum only,
https://github.com/MotorolaMobilityLLC/kernel-msm/tree/kitkat-4.4.4-release-titan
Now, reading further some guides, they say kernel and device tree will require some modification to work with CM12, but i couldnt find about this modification.
so I request all developers to guide me on this.
We can surely do this together. :fingers-crossed:
N.K.V. said:
Okay Guys,
I am working hard to bring up Cyanogenmod to our beloved moto g.
But i am a bit Noobish in this field.
I have been reading guides and following the process.
So far I have setup the build environment and synced the latest repo from CM sources.
Now, further most imp step is Vendor, Kernal and Device tree.
I have found this so far, by searching this forum only,
https://github.com/MotorolaMobilityLLC/kernel-msm/tree/kitkat-4.4.4-release-titan
Now, reading further some guides, they say kernel and device tree will require some modification to work with CM12, but i couldnt find about this modification.
so I request all developers to guide me on this.
We can surely do this together. :fingers-crossed:
Click to expand...
Click to collapse
I love your initiative! Unfortunately I'm not a developer...
Send from my XT1068 using Tapatalk.
nice work mate.... developers are needed urgently....
Why do you think developers will find you and this thread? It works the other way. You need to find developers and ask for help. I suggest you start here and here
I keep my fingers crossed for the success of the project :highfive:
Yes, I am reading all possible guides given by the developers.
By that only i have reach this far.
But for device tree and kernel, device specific modifications are necessary, and I really need help of some one who has actually done this before.
If this is successful , we can have an alpha build of CM 12 , in 3-4 days.
@ N.K.V.
ok i will help you with this..
first we need to set up device tree and vendor trees....
there is 2 ways to do this
first:- get a official motorola stock lollipop update for your phone.
(unfortunately it not yet released for all variants)
examine the similar device trees like falcon or htc a5 (desire 816) of lg l90 or sony m2 or sony e3
compare the kernel sources of falcon and titan (these are kitkat sources so may be in future motorola will release updated lollipop kernel source)
there are various major differences.
set up a basic device tree from falcon with msm8226 common of cm repos.
take vendor blob list from falcon
adapt it for titan
extract vendor blob from phone.
compile the rom
second:- from existing 4.4.4 rom
repo sync kernel from github
make changes to falcon and msm8226 device tree to adapt titan
extract vendor blobs with falcon list
compile
problem with second approach is that you have to make many changes to kernel and other things
but if we get official moto update of lollipop with kernel source then it will be little easier...
still if you are going to compile and want to make a cm12 from 4.4.4 i am with you ...i will set up device trees and other trees to set up things in motion.....
and then we can change vendor blobs and kernel to lollipop when it get released...
k2wl said:
@ N.K.V.
ok i will help you with this..
first we need to set up device tree and vendor trees....
there is 2 ways to do this
first:- get a official motorola stock lollipop update for your phone.
(unfortunately it not yet released for all variants)
examine the similar device trees like falcon or htc a5 (desire 816) of lg l90 or sony m2 or sony e3
compare the kernel sources of falcon and titan (these are kitkat sources so may be in future motorola will release updated lollipop kernel source)
there are various major differences.
set up a basic device tree from falcon with msm8226 common of cm repos.
take vendor blob list from falcon
adapt it for titan
extract vendor blob from phone.
compile the rom
second:- from existing 4.4.4 rom
repo sync kernel from github
make changes to falcon and msm8226 device tree to adapt titan
extract vendor blobs with falcon list
compile
problem with second approach is that you have to make many changes to kernel and other things
but if we get official moto update of lollipop with kernel source then it will be little easier...
still if you are going to compile and want to make a cm12 from 4.4.4 i am with you ...i will set up device trees and other trees to set up things in motion.....
and then we can change vendor blobs and kernel to lollipop when it get released...
Click to expand...
Click to collapse
This is great news. A team effort can do anything.:good:
Thanks to NKV and Kewl. Great initiative. God Bless You.
Sent from my Nexus 7 using XDA Free mobile app
okay guys,
let's keep this thread clean for developers.
you can always hit like to appreciate
UPDATE: @k2wl is working on kernel and device tree, it will take him some days.
@k2wl and N.K.V.
Thx for your time and work :good:
I wait for the right Software on xt1068!
I have a little bit of knowledge and i can learn really fast, if you guys need help, you can count on me
which model will this be for? (please say xt1064)
Bobboman said:
which model will this be for? (please say xt1064)
Click to expand...
Click to collapse
Doesn't matter. It will be for all variants!
absolutely brilliant, i wish i knew a lick of programming so that i could help get this done faster (i'm tired of seeing a SU update in play store and not being able to use it because it sends my G into a bootloop)
Thanks man, lollipop official update have a bug while playing music via bluetooth when screen is lock, can you fix it on this rom?
Ha ha...Let's make the ROM first..
Bug fixing in Second task.
Now that lollipop soak has started in India....i think Work should go fast. :beer:
Waiting for it. Please keep updated though!
I'm interested in helping with this.
Sent from my A0001 using XDA Free mobile app
Hope to See this soon! Thanks guys!!
Nice intitiative...but i think making device tree and vendor for this device will not be tht easy....still hope for best
New CyanogenMod 13 snapshot build (ZNH5Y) is rolling out.
The Android ROM community isn't quite as active as it was a few years ago with Android itself becoming more feature-rich. Still, CyanogenMod is chugging along with support for a ton of devices and a reasonably fast update cycle. A new snapshot build of the Marshmallow-based CyanogenMod 13 is now official (ZNH5Y), and it will be available on the first wave of devices today.
This is a snapshot build, meaning it's the most stable build of CM you can get. Of particular note, this version of CM will include all security patches up through the August bulletin. Build ZNH5Y also includes fixes for several of the recently reported Quadrooter kernel vulnerabilities. Two of the vulnerabilities aren't accessible to the CM team, so those patches need to come from further up the chain.
If you're running the ZNH0E snapshot build, you can flash the new one on top of it. ROMs for various devices will roll out as they are ready. Today, you can expect downloads for popular devices from OEMs like OnePlus, Samsung, and Motorola, as well as most Nexus devices. The full list is available on CM's blog post, but they're all code names.
Source: http://www.androidpolice.com/2016/08/15/new-cyanogenmod-13-snapshot-build-znh5y-rolling/
CM 13.0 Release – ZNH5Y - http://www.cyanogenmod.org/blog/cm-13-0-release-znh5y
Full changelog: http://pastebin.com/ptatg6kh
cm-13.0-20160816-SNAPSHOT-ZNH5YAO0F6-bacon.zip
Link - http://download.cyanogenmod.org/get/jenkins/174518/cm-13.0-20160816-SNAPSHOT-ZNH5YAO0F6-bacon.zip
Which is better / newer ? This on ore this one cm-13.1.1-ZNH2KAS2X1-bacon-signed-704f3ea59b ?
Thanks in advance
EDIT: I discovered what is difference, this one is cyanogenmod the other one is cyanogenOs, i got wrong with the filename.
I get reboots every time I receive a phone call with clean install and the latest stock opengapps. Works fine without opengapps, now trying to get it to work without the google dialer.
Edit: ok I looked into it, I never had to do this on recent cm13 nightlies but it's necessary to set dialer as default app for phonecalls.
Spaghetti-XRY said:
Which is better / newer ? This on ore this one cm-13.1.1-ZNH2KAS2X1-bacon-signed-704f3ea59b ?
Thanks in advance
EDIT: I discovered what is difference, this one is cyanogenmod the other one is cyanogenOs, i got wrong with the filename.
Click to expand...
Click to collapse
Your are trying to compare CM with COS?
I am the proud owner of two Oneplus One devices. (TWRP 3.0.2.0)
Just dirty flashed cm-13.0-20160816-SNAPSHOT-ZNH5YAO0F6-bacon on top of the previous Snapshot version on my two devices.
DDR is wiped perfectly.
Flash process well documented (log on screen)
After Flash, do a wipe of Cache / dalvik (just to be sure)
That's all. Works well, no issues.
Again, a nice job of Cyanogen.Mod... (Some may not like them, but I (and my devices) do like them)