Database Develop

[AOSP] Who should I be following as the better AOSP. CM or FreeXperia?

Hey so I love that we have AOSP for my Sony = Sony Nexus!!
But who should I be following as the cutting edge of AOSP. I know Sony releases some sources but not the proprietary ones so I know most of it comes from there. I myself have just installed the latest RC3 of CM 10.1. And the bugs I used to have like Lockscreen delay and No audio on Hangouts seem to have gone. But why should I install FreeXperia over CM?
Is CM the base that everyone bases their AOSP on? Is Free Xperia more focused on the Sony Specific Issues?
And what about Linaro? Carbon? AOKP? Are they all based off the same source (they all seem to have the same bugs)
Thoughts? Direction?
Thanks in advance!

First of all, CM roms are made by the FXP team as they are official CM maintainers for Sony devices.
Secondly, Sony's AOSP sources are different from that of CM sources. AOSP implies pure android with stock customizations. CM sources is heavily customizable (think of all the settings you can do in CM10.1) they are based on Google's open source as well as the device specific source code released by Sony.
Sent from my C6602 using xda app-developers app

CM10.1 vs. Free Xperia
What is the difference between the regular CM and the one you can download from FreeXperia project?
E.g. for Xperia Z (the latest releases at the moment):
FXP222a-cm-10.1-20130604-UNOFFICIAL-yuga.zip
Click to expand...
Click to collapse
vs.
cm-10.1-20130608-NIGHTLY-yuga.zip
Click to expand...
Click to collapse

80mercury said:
What is the difference between the regular CM and the one you can download from FreeXperia project? ...
Click to expand...
Click to collapse
I too would like to know this - obviously, they're very close, but there must be something different there.
I spent an hour trying to find this out the other night - got slightly excited when I saw a message from some poor sucker who explained he was a noob, etc, blah, blah, and would someone please explain the difference. The only reply he got was a terse demand that he go read the FreeXperia dev thread and work it out for himself ...
If someone can write an explanatory sentence or two about the difference between the builds on the official Cyanogen Mod site and the FXP* builds from freexperiaproject.com, I would appreciate it.

ratworks said:
I too would like to know this - obviously, they're very close, but there must be something different there.
I spent an hour trying to find this out the other night - got slightly excited when I saw a message from some poor sucker who explained he was a noob, etc, blah, blah, and would someone please explain the difference. The only reply he got was a terse demand that he go read the FreeXperia dev thread and work it out for himself ...
If someone can write an explanatory sentence or two about the difference between the builds on the official Cyanogen Mod site and the FXP* builds from freexperiaproject.com, I would appreciate it.
Click to expand...
Click to collapse
hey man, I had forgotten that I had made this thread but long story short FXP and CM are the same. CM has their own schedule, standards and code they develop and CM work towards AOSP for all their devices. FXP are SONY only, They use the code by CM and are responsible for both the Sony releases via CM and FXP. How FXP differs is that they can go ahead and release a lot of versions without any established "stable" or milestones they just release updates as they go. CM take those Sony specific changes that are made and combine them standard CM code are release Milestones, RC's and Nightlies with varying results
TLDR: They are the same, All the Sony specific code in CM is FROM FXP, FXP has no interest in making a stable version they just release new code in an almost "nightly" fashion. Their is no guarantee that the newest FXP will be more stable then the previous, its the same risk you take when you go with CM nightlies.
Personally I prefer CM Nightlies. If you want stable (with established bugs) go with CM, if you want to be running the latest CM code go with CM but if you want the latest sony fixes (unstable at times) go FXP, who updates about 1 every 1-2 weeks

Great explanation mate, thanks for that.

Unofficial Cyanogenmod 10.2 for I9100G with stagefright fix

What is this?
This a rebuild of Cyanogenmod 10.2 for I9100G where the source has been patched for the Stagefright vulnerability. The only code-wise difference: http://review.cyanogenmod.org/#/c/105496/
Build platform
CentOS Linux release 7.1.1503 (Core)
Linux polaris 3.10.0-229.11.1.el7.x86_64 #1 SMP Thu Aug 6 01:06:18 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux
java-1.7.0-openjdk-1.7.0.85-2.6.1.2.el7_1.x86_64
java-1.7.0-openjdk-devel-1.7.0.85-2.6.1.2.el7_1.x86_64
Build date
8th of august 2015
Download
[md5sum] 13944c192abd11eca5ceee526bb6230a [file] cm-10.2-20150808-UNOFFICIAL-i9100g.zip [download] mirror 1 mirror 2
Please verify checksum after downloading!
Installation instructions
Via recovery & ADB
Boot to recovery, go to sideload mode and run "adb sideload cm-10.2-20150808-UNOFFICIAL-i9100g.zip"
Reboot
Via recovery
Put zipfile on sdcard on some other storage location accessible from recovery
Flash zipfile as you would any other ROM
Reboot
Note from me
I only built this release for myself to protect me from the stagefright vulnerability. I still use CM 10.2 because it works the fastest for my device.
Required notice
This software comes without any warranties and I cannot be held liable for any consequences by your use of this software. You agree to these terms when you download the software.
XDA:DevDB Information
Unofficial Cyanogenmod 10.2 for I9100G with stagefright fix, ROM for the Samsung Galaxy S II
Contributors
RedShift1
ROM OS Version: 4.3.x Jellybean
ROM Kernel: Linux 3.0.x
Based On: CyanogenMod
Version Information
Status: Snapshot
Created 2015-08-09
Last Updated 2015-08-09

any information?
Screenshot?

xn0live said:
any information?
Screenshot?
Click to expand...
Click to collapse
What is this?
This a rebuild of Cyanogenmod 10.2 for I9100G where the source has been patched for the Stagefright vulnerability. The only code-wise difference: http://review.cyanogenmod.org/#/c/105496/
Click to expand...
Click to collapse
http://forum.xda-developers.com/galaxy-s2/development/rom-cyanogenmod-10-2-official-nightly-t2379850
edit:
btw, you might want to start reading the posts before you start asking questions. You spam an awful lot in my opinion. In the future I'll just report your posts, if you didn't bother to read at least the first posts and the last pages.

its 4.3 version right? have that version sod or is it only by 4.1.2

xn0live said:
its 4.3 version right? have that version sod or is it only by 4.1.2
Click to expand...
Click to collapse
Cyanogenmod 10.2 = Android 4.3.1. I haven't had any screen of death issues.

RedShift1 said:
Cyanogenmod 10.2 = Android 4.3.1. I haven't had any screen of death issues.
Click to expand...
Click to collapse
is it the same
toppits posts?
you have screenshot from scrren on ?

xn0live said:
is it the same toppits posts?
you have screenshot from scrren on ?
Click to expand...
Click to collapse
It's exactly like toppits post, no I don't have any screenshots as that's redundant anyway (plus I already customized my only I9100G, I'm not going to revert that just for you). Like I said in the topic start, this ROM is code-wise CM 10.2 aside from the stagefright fixes.

stagefright fixes
what does it mean?

xn0live said:
stagefright fixes what does it mean?
Click to expand...
Click to collapse
https://blog.zimperium.com/experts-found-a-unicorn-in-the-heart-of-android/ This build has a fix for those problems.

only 180mb? we need to flash gapps or only full wipe then flash?
and is there came at the future updates?

Can you build CM12.1 for i9100g? Please.
Thank you for dev.

dacsang97 said:
Can you build CM12.1 for i9100g? Please.
Thank you for dev.
Click to expand...
Click to collapse
I would be happy if the dev focuses more in stability in this version rather than working on more recent updates. Believe me or not, this device isn't really capable in working smoothly above KitKat anymore actually. It's just too old and weak to run smoothly on newer firmwares. You can see why I stopped my RR development, I totally lost my passion in doing it anymore. What's the point of doing it when it cant even run smoothly on it with lags time by time. If I have time, I might learn building a kernel for this build. All I want is performance and stability rather than having more recent updates but with crappy memory management and laggy UI.
Once again, thanks to the dev for this build.

Diatomix98 said:
I would be happy if the dev focuses more in stability in this version rather than working on more recent updates. Believe me or not, this device isn't really capable in working smoothly above KitKat anymore actually. It's just too old and weak to run smoothly on newer firmwares. You can see why I stopped my RR development, I totally lost my passion in doing it anymore. What's the point of doing it when it cant even run smoothly on it with lags time by time. If I have time, I might learn building a kernel for this build. All I want is performance and stability rather than having more recent updates but with crappy memory management and laggy UI.
Once again, thanks to the dev for this build.
Click to expand...
Click to collapse
You try with Mokee Nightly, it is smooth , but battery drain. I believe you can fix RR on next build. Hope . Try your best. Let's do what's best for i9100g . Thank you.

dacsang97 said:
You try with Mokee Nightly, it is smooth , but battery drain. I believe you can fix RR on next build. Hope . Try your best. Let's do what's best for i9100g . Thank you.
Click to expand...
Click to collapse
I tried, on the first 3 days, it works extremely fine. Slowly, the lag increases, yesterday it was lagging so much that I have no choice but to switch to this rom. It's not even my primary device and I got only messenger and gapps installed. Let's see how it goes. =)

Ok, i try this rom , wait kernel from you.

I don't intend on releasing any ROMs or kernels of my own. I only built this ROM so I could keep on using CM 10.2 but have the stagefright vulnerability fixed. You can get decent kernels from other topics in this forum. I may accept patches to fix other bugs or security issues but I'm not intending this to be a long-term project.

Diatomix98 said:
I tried, on the first 3 days, it works extremely fine. Slowly, the lag increases, yesterday it was lagging so much that I have no choice but to switch to this rom. It's not even my primary device and I got only messenger and gapps installed. Let's see how it goes. =)
Click to expand...
Click to collapse
I have the same problem, on both my I9100 and my I9100G. Whenever free memory drops below 100 MB, the system becomes so sluggish that it is painful to use. Freeing memory helps but fills up too fast again. I think android needs 2 GB of RAM to run properly, which our devices don't have.

New rom for our device from China
http://m.romjd.com/Rom/Detail/64860

Haha
Diatomix98 said:
I would be happy if the dev focuses more in stability in this version rather than working on more recent updates. Believe me or not, this device isn't really capable in working smoothly above KitKat anymore actually. It's just too old and weak to run smoothly on newer firmwares. You can see why I stopped my RR development, I totally lost my passion in doing it anymore. What's the point of doing it when it cant even run smoothly on it with lags time by time. If I have time, I might learn building a kernel for this build. All I want is performance and stability rather than having more recent updates but with crappy memory management and laggy UI.
Once again, thanks to the dev for this build.
Click to expand...
Click to collapse
Dude You just said the truth! ^_^

Is this odex or deodex rom?

Custom ROM and Force Reboots

I have had a DT since launch and I have had a custom ROM on for quite a while and upon using Android N (through crDroid) I found an extreme amount of forced reboots, I was wondering what causes them as I would love to join the ranks of the 1%ers who use android N across all platforms.
Obviously saying "it doesn't work please fix" is not going to get me anywhere so ill throw my pride out the window and accept any and all assistance if yall would be so kind.

Sareniah said:
I have had a DT since launch and I have had a custom ROM on for quite a while and upon using Android N (through crDroid) I found an extreme amount of forced reboots, I was wondering what causes them as I would love to join the ranks of the 1%ers who use android N across all platforms.
Obviously saying "it doesn't work please fix" is not going to get me anywhere so ill throw my pride out the window and accept any and all assistance if yall would be so kind.
Click to expand...
Click to collapse
crDroid is notorious for that. Try any of the other 7.1 roms that are out there. I installed AOKP 2 days ago and it hasn't rebooted yet. Battery life is awesome too.

ok. Ill try out aokp as that is what I used in 6.0.1 Thanks!

Sareniah said:
ok. Ill try out aokp as that is what I used in 6.0.1 Thanks!
Click to expand...
Click to collapse
Just to give you an update, I just removed AOKP because whenever I try to make a call through a Bluetooth device (like my car's hands free system), it completely messes up the phone and eventually force reboots. These roms are based on early versions of CM14.1 (we don't even have official CM14.1 builds yet) so some bugs are to be expected, but they're all being updated very regularly so I expect that they will be virtually bug free in a no time. Just keep trying them until you find one that works for you.

TheSt33v said:
Just to give you an update, I just removed AOKP because whenever I try to make a call through a Bluetooth device (like my car's hands free system), it completely messes up the phone and eventually force reboots. These roms are based on early versions of CM14.1 (we don't even have official CM14.1 builds yet) so some bugs are to be expected, but they're all being updated very regularly so I expect that they will be virtually bug free in a no time. Just keep trying them until you find one that works for you.
Click to expand...
Click to collapse
RR 7.x was just released yesterday. People are saying it's quite stable.
[ROM][All Quark][7.x]Resurrection Remix
http://forum.xda-developers.com/moto-maxx/development/rom-resurrection-remix-t3511109
khangozzy said:
24 hrs without reboot issue, great job as usual @bhb27, thanks.
Sent from my DROID Turbo using Tapatalk
Click to expand...
Click to collapse
johnbravado said:
This ROM is awesome. Using latest GApps and no reboots no issues. Smooth sailing. I believe much better than crDroid. The RR team is amazing and thanks to @bhb27 for working hard.
Click to expand...
Click to collapse
quantum tao said:
So far is running good. Not a fan of pixel launcher though, also i think the network icons in crdroid are more functional because they have built in traffic arrows.
Glad to have proximity speakerphone back.
Click to expand...
Click to collapse
xboxbr said:
very stable for me. no reboots so far
Click to expand...
Click to collapse
________
Also @calsurferpunk just re-synced his "unofficial" CM14 to RR's builds to hope to get that stability. Previously he was uing crDroids database (or whatever). His unofficial CM14 builds are a hybrid of more bare bones CM and everything-including-the-kitchen sink tweaks of custom ROMs. His builds have the more popular tweaks, like being able to download Moto apps and a couple more, but are not change-everything ROMs.
[ROM][2016-12-03][Quarks][CM 14.1 Unofficial][7.1.x]
http://forum.xda-developers.com/moto-maxx/development/rom-t3494646
calsurferpunk said:
I just posted an updated build. I'm using repos from RR instead of crDroid (still configured to be stock CM 14.1) and the "stock" kernel from 2bhb27. Hopefully this fixes the instability issues. You should go over and thank him as well for all of his hard work
https://www.androidfilehost.com/?fid=385035244224403322
Click to expand...
Click to collapse

I really appreciate your assistance with this mate. I remember back when we had mofo and your only option was basically build an image yourself or take whatever one guy was developing. I'm really thankful we have evolved no thanks to the developers like chainfire and all the wonderful people who still care for our 3900mah mini Nexus 6... Or at least close enough
Edit: I will try out CM14.1 Unofficial for a day and see how that goes. I really want to stay away from "kitchen sink" roms because of the restarts. Thanks again for your help

[ROM][GT-I9506][ks01lte][Unofficial LineageOS 13.0]

Here is my build of LineageOS 13.0 for the Galaxy S4 LTE A. It is based on the pure LineageOS code unless indicated otherwise.
* IMPORTANT *
Please note that these builds are based on nothing else than the unchanged official code from LineageOS. So every credit goes to the ones providing the code.
I will not and cannot make any changes to the code. The only thing I can do and will do is build the ROM.
Also, it should be understood that I take no responsibilities whatsoever if anything goes wrong when you install the ROM. Like any custom ROM this is completely at your own risk!
However, you can expect that any ROM I share has been installed on my own GT-I9506 (starting with the latest official Samsung firmware 5.0.1) and runs without obvious issues. Your mileage may vary.

https://www.mediafire.com/?c8q4lqh675hc97b,7dhley6dl6j9dnb
Based on LineageOS official code up to https://review.lineageos.org/154230

Which modem and boot loader can you recommend?

audianer said:
Which modem and boot loader can you recommend?
Click to expand...
Click to collapse
I flashed the latest official Samsung firmware to prepare for LineageOS 13.0

I'm trying to build the latest version, which does build without error, but upon booting gets stuck at starting the apps, i.e. just before showing the lock screen. The latest working build was from January 5th 2017 and I experienced the error first on a build of January 8th 2017. So I suspect the commit in question is one from January 6-8.
Before I'm forced to manually investigate commit-by-commit from the latest working version, does anyone know what has changed that causes this error? I was not able to get any output from adb logcat either, so I have no idea what went wrong... which is rather frustrating.

What device tree and kernel did you use?

DualJoe said:
What device tree and kernel did you use?
Click to expand...
Click to collapse
The same as the working previous build: LineageOS/android_kernel_samsung_ks01lte & LineageOS/android_device_samsung_ks01lte. As far as I can see nothing in the kernel or device tree has changed, thus it must be some incompatibility with the rest of the LineageOS code.
I just tried another build just an hour ago, same result: stuck at the final starting apps (before the vibration). I also tried reverting to a working state of the source (of January 5) by using "repo forall -c 'git checkout `git rev-list --all -n1 --before=", but that one didn't even build.
I would appreciate any help here. It's not like there were some exhaustive documentation about how to build LineageOS. And anyway, apparently building is not the issue here.

If that's still Solk2's stuff it might be very old indeed.

DualJoe said:
If that's still Solk2's stuff it might be very old indeed.
Click to expand...
Click to collapse
No. It seems that @solk2 has started to develop the ks01lte again. See the github commits:
https://github.com/LineageOS/android_kernel_samsung_ks01lte/tree/cm-13.0
https://github.com/solk2/android_kernel_samsung_ks01lte/commits/cm-13.0
https://github.com/LineageOS/android_device_samsung_ks01lte/tree/cm-13.0
https://github.com/solk2/android_device_samsung_ks01lte/commits/cm-13.0
(Note: There is no cm14.1 branch on @solk2's github repo yet.)

WeirdSoup said:
No. It seems that @solk2 has started to develop the ks01lte again. See the github commits:
https://github.com/LineageOS/android_kernel_samsung_ks01lte/tree/cm-13.0
https://github.com/solk2/android_kernel_samsung_ks01lte/commits/cm-13.0
https://github.com/LineageOS/android_device_samsung_ks01lte/tree/cm-13.0
https://github.com/solk2/android_device_samsung_ks01lte/commits/cm-13.0
(Note: There is no cm14.1 branch on @solk2's github repo yet.)
Click to expand...
Click to collapse
Uhm... There are cm-14.1 branches too.

zardak said:
Uhm... There are cm-14.1 branches too.
Click to expand...
Click to collapse
I said "@solk2's repo".
And as you can see, there are no additional commits on CM14.1 branch in LOS's ks01lte device repo, compared to cm13.

WeirdSoup said:
I said "@solk2's repo".
And as you can see, there are no additional commits on CM14.1 branch in LOS's ks01lte device repo, compared to cm13.
Click to expand...
Click to collapse
Well, solk2 started to push changes on his kernel's repo days ago, even on cm-14.1 branch.
Anyway, I think is just a matter of time. We'll get official builds sooner or later.
I just don't understand why solk2, kyasu, and possibly gugu0das and others don't collaborate all together to only one kernel/device for this phone

zardak said:
Well, solk2 started to push changes on his kernel's repo days ago, even on cm-14.1 branch.
Anyway, I think is just a matter of time. We'll get official builds sooner or later.
Click to expand...
Click to collapse
Oh, I'm sorry. I misstated. I mean, the "device" repo. (https://github.com/solk2/android_device_samsung_ks01lte/commits/cm-13.0)

zardak said:
Well, solk2 started to push changes on his kernel's repo days ago, even on cm-14.1 branch.
Anyway, I think is just a matter of time. We'll get official builds sooner or later.
I just don't understand why solk2, kyasu, and possibly gugu0das and others don't collaborate all together to only one kernel/device for this phone
Click to expand...
Click to collapse
It looks like a waste of time and work, doesn't it? There is no point in having 3 or more different builds with no particular differences. Devs might want to join the official repos instead and make their changes there.

zardak said:
It looks like a waste of time and work, doesn't it? There is no point in having 3 or more different builds with no particular differences. Devs might want to join the official repos instead and make their changes there.
Click to expand...
Click to collapse
You are absolutely right. I dont know, maybe they have reasons not to join the LineageOS team, but when I got my S4 I was rather confused with all this different versions. I mean for many devices you get unofficial builds with extra features/improvements, but for the I9506 its hard to tell the differences. However at the moment I would say the build by gugu0das is the best, but it looks like he is not going to update it anymore. So yes, it would be great to have all those talented developers out there working on the same repos.

PixelChris95 said:
So yes, it would be great to have all those talented developers out there working on the same repos.
Click to expand...
Click to collapse
I believe this is some sick "if you don't figure it out yourself, you're not supposed to know how to do it" attitude of some (most?) developers. Or another symptom of "not invented here" syndrome.
If LineageOS official builds are available I will surely not waste time to build it myself, but in the meantime I would like to be up-to-date. So still, anyone pointing me to information how to do it is very welcome.

zardak said:
Well, solk2 started to push changes on his kernel's repo days ago, even on cm-14.1 branch.
Anyway, I think is just a matter of time. We'll get official builds sooner or later.
I just don't understand why solk2, kyasu, and possibly gugu0das and others don't collaborate all together to only one kernel/device for this phone
Click to expand...
Click to collapse
I think the same of you. It could be better for all of us to make a ROM with the best of their ROMs.

JohnMcClane1htc said:
I think the same of you.
Click to expand...
Click to collapse
What do you think? That I do not share what I do? I have provided a ROM for i9506 based on cyanogenmod 11.0 for a long, long time, as well as one for Nexus 7. And I have always made clear from where the sources for those builds came. Perfect transparency, don't you think?
It is because of disrespectful people like you that developers (and people like me, because I am not a developer) stop sharing!

NeuDLi said:
What do you think? That I do not share what I do? I have provided a ROM for i9506 based on cyanogenmod 11.0 for a long, long time, as well as one for Nexus 7. And I have always made clear from where the sources for those builds came. Perfect transparency, don't you think?
It is because of disrespectful people like you that developers (and people like me, because I am not a developer) stop sharing!
Click to expand...
Click to collapse
If my comment has offended you, I apologize. My comment doesn't want to disparage anyone. And I recognize the effort of the developers because, although I am not, I know how difficult it must be to develop a ROM.
If my comment has offended you, I apologize. I am sorry.
I also create content in Htcmania and always share and show the sources. I only would want to say that sometimes, when finding so many ROMs based on CM, it can be difficult to decide for one or the other, since the changes between them are very subtle.
Regards

Maintaining/creating roms is usually the way people learn Linux, Android, compiling, git and such. That's why there are so many one-man projects. Once they are into it most vanish again/go over to other stuff though. Only few people keep over long time like Temasek. In the end there can't be enough roms. More options are always better than none. As long as people are posting the source code for other people to pick up they do work together already.

[CLOSED]Test Pilots for new Nougat ROM Build

I have built a new version of the ColtOS Nougat ROM for XT907/XT905 devices, and am looking for someone to test flash the ROM ZIP before I put the effort into creating a proper thread post.
The reason I do not want to test flash it myself is that I am currently running ResurrectionRemix and the ROM is set up juuuust right and don't wish to risk upsetting anything.
The ROM is basically a straight ColtOS build for our device, with my Overclocked Kernel including the additional CPU and IO Governors. This build also includes a new CPU governor, Alucard, and also a new IO Governor, FIOPS. Both the FIOPS IO Governor and the Alucard CPU Governors really interest me to use on my daily; and hence I went to the effort to create a new Nougat build. ie compile them into RR; and maybe crDroid, which would also bring in any LOS specific changes not overridden by the respective custom ROM code.
Here is a thread for a different device: https://forum.xda-developers.com/lg-g3/development/coltos-t3656725
It is from a group (NB: 90% of the changes specifically in crDroid included in our device are done by a single dev) of devs in India, and has very similar features to crDroid ie less than ResurrectionRemix, and my introduction to it was because how closely they stuck to LineageOS in their code, that didn't need to be changed to add a specific feature.
What I would hope for is, someone to clean flash this ROM, Nano or Pico GApps (its an ODEX'd ROM so limited System partition space and ODEX'ing RR caused it to fail), connect to Google and basically confirm it boots and appears to run smoothly. Then also test the new CPU governor (Alucard) and IO scheduler (FIOPF) to ensure they don't cause a reboot.
Please PM me if you are interested and have the time.

it was alright. I disliked the reboot/ power off theme... same reason I don't run pac rom.

Galaxyninja66 said:
it was alright. I disliked the reboot/ power off theme... same reason I don't run pac rom.
Click to expand...
Click to collapse
Yeah, I'm not a fan of the styling, but do respect the fact they have gone out of their way to make it actually look different to all other ROMs. I built it because I downloaded it when my other nougat builds were failing to run (ie before we knew to format our data partitions as F2FS)
As for pac rom, there is also no Nougat for our device either
FYI to all, this ROM also has an under-clocked (as well as overclocked) kernel.
I should have a public build up for this soon.

DiamondJohn said:
Yeah, I'm not a fan of the styling, but do respect the fact they have gone out of their way to make it actually look different to all other ROMs. I built it because I downloaded it when my other nougat builds were failing to run (ie before we knew to format our data partitions as F2FS)
As for pac rom, there is also no Nougat for our device either
FYI to all, this ROM also has an under-clocked (as well as overclocked) kernel.
I should have a public build up for this soon.
Click to expand...
Click to collapse
meh, pac rom was never very good after 4.3 anyways, the only reason I rocked it was for all the rom features, but 5.0+, tablet UI had been phased out, and most roms got closer to AOSP, and more unified as far as features go then before, making pac rom... un needed.

Galaxyninja66 said:
...and most roms got closer to AOSP...
Click to expand...
Click to collapse
That's plain wrong. Try true AOSP (which if your not rocking a Nexus is hard to find), then try RR. TOTALLY different features.

DiamondJohn said:
That's plain wrong. Try true AOSP (which if your not rocking a Nexus is hard to find), then try RR. TOTALLY different features.
Click to expand...
Click to collapse
I was reffering more to the roms PAC was built from, Paranoid android (mostly features like PIE and stuff), AOKP is pretty much dead last I heard, and Lineage is no where near CM when it comes to actual features. I shouldn't say roms are becoming more like AOSP, I should say that AOSP is becoming more like roms, in the sense that more and more features are being added, along with theme support out of the box. RR is obviously the king of customization, but PAC was never based on RR. PAC rom was great because it brought all the features from 3 major roms and put them all together, you got UI switch, you got the CM theme engine, you got all the cool PA features (it's been a while, forgive me for the vague-ness of that last one). Now something like PAC isn't very needed nor wanted.

Galaxyninja66 said:
I was reffering more to the roms PAC was built from, Paranoid android (mostly features like PIE and stuff), AOKP is pretty much dead last I heard, and Lineage is no where near CM when it comes to actual features.
Click to expand...
Click to collapse
You are mixing up time-lines. Lineage IS what used to be CM. And just as CM features would of changed over time, LineageOS developed different features to what previously existed in CM. And further, time changes dev streams in Android BIG TIME. The ROMs I ran as daily's in Lollipop and earlier, are not available in Nougat (at least not to build) As for AOKP, I think AOSPB are the kids on the block to watch ie they are building some interesting features which have or will be brought into many custom ROMs, and then probably into AOSP.
Galaxyninja66 said:
I shouldn't say roms are becoming more like AOSP, I should say that AOSP is becoming more like roms, in the sense that more and more features are being added, along with theme support out of the box.
Click to expand...
Click to collapse
Thats been happening since day dot. Thats one of the benefits/reasons for open source development.
Galaxyninja66 said:
Now something like PAC isn't very needed nor wanted.
Click to expand...
Click to collapse
Now, them there are fightin words everyone has their own preference for specific ROMs. For example, I am surprised that my crDroid build of Nougat appears to have more people rocking it as a daily as compared to RR but I could be the dope, or simply just someone who thinks RR 'is very needed and wanted'.:highfive:

Build is up
Latest build is up.
I'll ask for this thread to be closed.
https://forum.xda-developers.com/droid-razr-m/development/coltos-nougat-xt907-xt905-jbbl-t3708039

DiamondJohn said:
You are mixing up time-lines. Lineage IS what used to be CM. And just as CM features would of changed over time, LineageOS developed different features to what previously existed in CM. And further, time changes dev streams in Android BIG TIME. The ROMs I ran as daily's in Lollipop and earlier, are not available in Nougat (at least not to build) As for AOKP, I think AOSPB are the kids on the block to watch ie they are building some interesting features which have or will be brought into many custom ROMs, and then probably into AOSP.
Thats been happening since day dot. Thats one of the benefits/reasons for open source development.
Now, them there are fightin words everyone has their own preference for specific ROMs. For example, I am surprised that my crDroid build of Nougat appears to have more people rocking it as a daily as compared to RR but I could be the dope, or simply just someone who thinks RR 'is very needed and wanted'.:highfive:
Click to expand...
Click to collapse
I'd agree that RR is wanted and needed, the reason PAC isn't is because it jut cherry picked from 3 major roms, and something like that just isn't very needed when most custom roms come with all of those features out of the box.
Now Lineage, I understand is built off of CM, but it lacks the CM theme engine which I consider the number one reason to use CM (at least for me, it's just a superior theme engine). Not only that, but the built in preformance section was also very missed, and I remember not seeing it in builds of CM13 and wondering why. A lot of awesome CM features that were ONLY in CM or roms based on it. just aren't really their anymore, and I was hoping that Lineage 14.1 would add them back. I don't really count Lineage 13 much, because CM13 was still pretty popular, and it's pretty much a re-brand of that, whereas CM14.1 I don't remember having much traction, as I believe Lineage was out at the time of its release. I might be wrong though, I never really followed very close on the whole "Cyanogenmod/Lineage" thing, because at the time I was still using only AOKP and classic CM builds.

Thread closed per OP