Develop Bugs

CyanogenMod 12/Android L Discussion

Hello everybody.
So I was wondering, when CyanogenMod 12 comes out, will they still support all of the devices they have been supporting? Or at least, in specific, our device? I can't imagine why'd they drop support.
Also, I hear in the new Android version, the Linux 3.10 kernel is being used. As opposed to the current 3.4 kernel we are using. Does anybody know about any significant changes between the two?
This is very exciting if/when we get this on our device I personally will just wait on a CM or AOSP version of Android as stock never really does it for me.
I don't know, but the more I think about it, the more excited I get (also the more apprehensive I get since I'll have to upgrade my kernel sources).
I know I probably shouldn't bring this up, but I also can't wait to blow my friend's new iOS 8 update out of the water with CM12/L (Not like CM11 doesn't already do that )

Snepsts said:
Hello everybody.
So I was wondering, when CyanogenMod 12 comes out, will they still support all of the devices they have been supporting? Or at least, in specific, our device? I can't imagine why'd they drop support.
Also, I hear in the new Android version, the Linux 3.10 kernel is being used. As opposed to the current 3.4 kernel we are using. Does anybody know about any significant changes between the two?
This is very exciting if/when we get this on our device I personally will just wait on a CM or AOSP version of Android as stock never really does it for me.
I don't know, but the more I think about it, the more excited I get (also the more apprehensive I get since I'll have to upgrade my kernel sources).
I know I probably shouldn't bring this up, but I also can't wait to blow my friend's new iOS 8 update out of the water with CM12/L (Not like CM11 doesn't already do that )
Click to expand...
Click to collapse
I'm so excited about this. It will be sooooooo cool. I need to learn to develop ROMs and stuff, because if developer support dies for this phone I would want to keep the development going.

Well then start now rjm....... Better now then never
2SHAYNEZ

rjmxtech said:
I'm so excited about this. It will be sooooooo cool. I need to learn to develop ROMs and stuff, because if developer support dies for this phone I would want to keep the development going.
Click to expand...
Click to collapse
You'll have me doing the little bit I can for this device for the next 8-9 months I'm stuck with this thing
Don't worry about developing ROMs, all you really need to know is how to compile and maintain. I plan to attempt at some unofficial builds of a ROM or two once I can deem my kernel as done. But don't worry, the LG OGP is definitely booming with activity right now, and will probably only get better with the following months to come.
We already have:
Gummy
PAC
Beanstalk
CM11
AOKP
AICP
Vanir
and a pretty good range of stock ROMs.
Soon (and I mean within a month or so) I hope to add Carbon and Paranoid Android to this list, but we will have to see. I do not know how to compile unofficially or much about it, but it doesn't look extremely difficult. So my hopes are high.
Plus, as this device drops in price, we may get some more people to keep development for this device relevant. Although I did not see our device in the local AT&T store last time I was there...
We have a beautiful phone with the processing power to last as a quality device for another year at least. LG makes some pretty nice stuff.
Unfortunately, we will be seeing more and more of our users leave as the months drag on as this phone gains age
We'll have to see who lasts the longest with this phone as their primary device... lol.
I suspect we will reach our peek in ROMs soon a few months after Android L is up and running. Just my guess though.
Shayne has a good point though, now is definitely the time to start. So better hit the tutorials!

Snepsts said:
You'll have me doing the little bit I can for this device for the next 8-9 months I'm stuck with this thing
Don't worry about developing ROMs, all you really need to know is how to compile and maintain. I plan to attempt at some unofficial builds of a ROM or two once I can deem my kernel as done. But don't worry, the LG OGP is definitely booming with activity right now, and will probably only get better with the following months to come.
We already have:
Gummy
PAC
Beanstalk
CM11
AOKP
AICP
Vanir
and a pretty good range of stock ROMs.
Soon (and I mean within a month or so) I hope to add Carbon and Paranoid Android to this list, but we will have to see. I do not know how to compile unofficially or much about it, but it doesn't look extremely difficult. So my hopes are high.
Plus, as this device drops in price, we may get some more people to keep development for this device relevant. Although I did not see our device in the local AT&T store last time I was there...
We have a beautiful phone with the processing power to last as a quality device for another year at least. LG makes some pretty nice stuff.
Unfortunately, we will be seeing more and more of our users leave as the months drag on as this phone gains age
We'll have to see who lasts the longest with this phone as their primary device... lol.
I suspect we will reach our peek in ROMs soon a few months after Android L is up and running. Just my guess though.
Shayne has a good point though, now is definitely the time to start. So better hit the tutorials!
Click to expand...
Click to collapse
If you could keep Beanstalk going for our device if development stops I would greatly appreciate it. I'll try and help out too when I learn how in case development does stop.

rjmxtech said:
If you could keep Beanstalk going for our device if development stops I would greatly appreciate it. I'll try and help out too when I learn how in case development does stop.
Click to expand...
Click to collapse
I have a feeling that we don't have to worry about Beanstalk

No it won't stop..... Aicp has seemed to come to a hault .. Maybe you should jump on that rmj..... Read read read and then read .... Then compile yo stuff
2SHAYNEZ

shayneflashindaily said:
No it won't stop..... Aicp has seemed to come to a hault .. Maybe you should jump on that rmj..... Read read read and then read .... Then compile yo stuff
2SHAYNEZ
Click to expand...
Click to collapse
It seems as though a lot of ROMs by that particular dev get abandoned eventually... but that's none of my business.
Yes AICP would be a great one to start on, first thing is first though, rjm, get yourself on a Linux VM or a Linux computer. Also, I hope you have some decent specs or it'll be hell trying to do it.
For example, I have an AMD FX-6350, so I have 6 cores in my system. I can allocate 4 to my VM
And you'll want some RAM, too. Like 8 GB so if you're using a VM you can allocate 4 as well.
For the distro I suggest using Linux Mint 64-bit (has to be 64-bit).
And I really hope your host OS is 64-bit, because otherwise you are probably incapable of compiling ROMs.
Best of luck!
P.S: I downloaded Carbon sources today. We'll see how that goes.

Oh also be sure you have PLENTY of free space, those sources love hogging space. I just cleaned out my old VM and set up a new one with 200 GB of space allocated. Thank God for Terabyte HDDs
Staying on topic, the L/5.0 SDK was released today. Approx. two weeks until the official Nexus release, and hopefully not too long until we get a taste of that afterwards.
KitKat was great (it felt like the smoothest Android experience ever when I flashed my first KK ROM) but I'm ready for Lollipop!
Material design looks interesting, although I gotta say... the circle triangle square virtual buttons aren't the best design choice imo. Maybe it's to make switching from an iPhone to an Android easier for the iUsers that find the current system to difficult to understand :laugh: They sure like their shapes of rounded edge squares and circles.
I'm not kidding, actually. A friend of mine steals my phone all the time and she cannot figure out PIE to save her life...

shayneflashindaily said:
No it won't stop..... Aicp has seemed to come to a hault .. Maybe you should jump on that rmj..... Read read read and then read .... Then compile yo stuff
2SHAYNEZ
Click to expand...
Click to collapse
I don't think I want to compile AICP. Beanstalk is the only ROM IMO that really would be a loss if development stopped. The features of Beanstalk outnumber those of other ROMs

rjmxtech said:
I don't think I want to compile AICP. Beanstalk is the only ROM IMO that really would be a loss if development stopped. The features of Beanstalk outnumber those of other ROMs
Click to expand...
Click to collapse
What about compiling it for the sake of learning how to compile...?

Snepsts said:
What about compiling it for the sake of learning how to compile...?
Click to expand...
Click to collapse
Maybe

rjmxtech said:
I don't think I want to compile AICP. Beanstalk is the only ROM IMO that really would be a loss if development stopped. The features of Beanstalk outnumber those of other ROMs
Click to expand...
Click to collapse
Is Beanstalk as stable as cm11. Does it have a RC or something similar to PAC or M11?

dpalmer76 said:
Is Beanstalk as stable as cm11. Does it have a RC or something similar to PAC or M11?
Click to expand...
Click to collapse
I'm pretty sure Beanstalk only releases stable updates. From what I remember there aren't any nightlies, as it sometimes is months before a new update is released. That is another reason why I like Beanstalk better than other ROMs.

I will be happy to see official LG update for Android Lollipop 5.x Waiting for updates!

rahib172 said:
I will be happy to see official LG update for Android Lollipop 5.x Waiting for updates!
Click to expand...
Click to collapse
Not much news from lg on updates yet:
http://www.androidauthority.com/which-phones-android-lollipop-540232/
---------- Post added at 05:11 PM ---------- Previous post was at 05:05 PM ----------
rjmxtech said:
I don't think I want to compile AICP. Beanstalk is the only ROM IMO that really would be a loss if development stopped. The features of Beanstalk outnumber those of other ROMs
Click to expand...
Click to collapse
Probably a sort of noobish question, but anyway many roms are cm-based (including beanstalk), and even aokp is cm enabled. How dependent are these roms on cm, basically meaning could they sustain themselves without cm continuing support too?

abumy said:
Not much news from lg on updates yet:
http://www.androidauthority.com/which-phones-android-lollipop-540232/
---------- Post added at 05:11 PM ---------- Previous post was at 05:05 PM ----------
Probably a sort of noobish question, but anyway many roms are cm-based (including beanstalk), and even aokp is cm enabled. How dependent are these roms on cm, basically meaning could they sustain themselves without cm continuing support too?
Click to expand...
Click to collapse
I think CM official support is close to vital for these ROMs, mainly for the kernel, but also because they update the device thingy you use to build ROMs I do believe.
I am 90% sure we will receive updates from CM though. They sure know how to take care of their devices.

Any custom ROM will do, if we are talking about testing the new Android L. What's bothering me is the support for F240x devices. If CM, Beanstalk, VANIR/COMMOTIO or AICP (the one I am using for a long period of time), will release an update, will there be a KERNEL or ROM that will work for the F240x?

MitoTakatori said:
Any custom ROM will do, if we are talking about testing the new Android L. What's bothering me is the support for F240x devices. If CM, Beanstalk, VANIR/COMMOTIO or AICP (the one I am using for a long period of time), will release an update, will there be a KERNEL or ROM that will work for the F240x?
Click to expand...
Click to collapse
I really hope it is for your sake. Luckily the dev that makes F240 ROMs for you guys seems to know what he's doing, and I'm sure he'll keep working for you. As long as e980 has support he can use that kernel and use it for F240.

Snepsts said:
I really hope it is for your sake. Luckily the dev that makes F240 ROMs for you guys seems to know what he's doing, and I'm sure he'll keep working for you. As long as e980 has support he can use that kernel and use it for F240.
Click to expand...
Click to collapse
Hopefully.

[Q] Is no one sharing sources?

Hi, HAM devs!
You propably don't know me yet, as i am new to the HAM. I already built CM7, 10 and 11 on LG devices though, so i am not totally new to android development/building.
Well.. i just got this Ascend Mate, and thought it would be nice to have a custom rom on it, like i had on other devices.
But all i can find is closed source flashables. Seems like joe.stone is the only one who shared atleast something.
Don't you guys think we could achieve more, if we work together?
I really want to work on custom stuff for our HAM, but it would be easier if i don't have to start from scratch, while a bunch of people COULD share their experiences with me.
So please contact me, if you can provide some useful informations on how to build for the HAM. - Let's do something!
- MisjudgedTwat a.k.a. BangL

Dont hold your breath mate, in my opinion This is one of the worst forums on xda !

Well, maybe i just start instead of flaming.
Here we go: https://github.com/hwmt1-u06
If anybody is interested in participating to this, just let me know.

I think the main reason for that is that most of the stuff here was developed in Russia or China and those of us here just basically searched online and found ROMs and posted links here.
Joe Stone was the main Dev here and he's moved on. Gold Concert did some good work here too and moved on. Outside of these guys I think the rest of people in the group are like me. We know a little about developing but we're not Devs so as a result the forum has pretty much died.
I would welcome your developing skills here right now:beer:
sent from my MT1-U06 using Tapatalk 2

yeah, i kinda figured that out already, my first post was a little bit fast maybe.
well, let's see what i can do... so far i can boot, but sound and reboots arent working well (maybe more).
currently trying to contact mrAlmid, and looking into his roms for a hint to the right direction.

Just a thought. Since huawei mate and huawei p6 are essentially same hardware (same motherboard, same cpu/gpu) with main difference in display, maybe some of the sources for p6 will come in handy?

tileeq said:
Just a thought. Since huawei mate and huawei p6 are essentially same hardware (same motherboard, same cpu/gpu) with main difference in display, maybe some of the sources for p6 will come in handy?
Click to expand...
Click to collapse
absolutely, yes.

alright, i got my first pretty-much-useable build done, so let the bug-hunting begin...
http://forum.xda-developers.com/asc...-unofficial-cyanogenmod-11-0-beta-v0-t3229182

Once a Finnish developer tried porting sailfish to the P6, he (or someone he forked from) had managed to collect almost all the sources for the P6. You can try tinkering around, if you have time, you could figure out how to build the needed libraries for the graphics stack from source (all the other devs jumped the boat already), if you succeed then we may have a chance of compiling a working Lollipop rom. For the mate, dont forget to change the touchscreen drivers as it differs on the P6 and the Mate. Heres the repo: https://github.com/locusf/cm11-p6

tauio111 said:
Once a Finnish developer tried porting sailfish to the P6, he (or someone he forked from) had managed to collect almost all the sources for the P6. You can try tinkering around, if you have time, you could figure out how to build the needed libraries for the graphics stack from source (all the other devs jumped the boat already), if you succeed then we may have a chance of compiling a working Lollipop rom. For the mate, dont forget to change the touchscreen drivers as it differs on the P6 and the Mate. Heres the repo: https://github.com/locusf/cm11-p6
Click to expand...
Click to collapse
a working lollipop rom? i dont feel like beeing THAT professional, to be honest. but i will check if i can use something for more stability on kk. thanks for the information, though! maybe i can find something to fix "reboot to recovery"-freeze

I got my current rom (carbon rom 4.4.4) from this website:
http://mateone4you.blogspot.nl/2015/04/carbon-rom-444-for-huawei-ascend-mate.html
He has a few more too.
Edit: I guess you know, reading your CM thread, but some may not....
Would welcome some more development, especially bluetooth connecting to audio is horrible...
I tried his other roms too, only got carbon working nicely.

SvenHee said:
I got my current rom (carbon rom 4.4.4) from this website:
http://mateone4you.blogspot.nl/2015/04/carbon-rom-444-for-huawei-ascend-mate.html
He has a few more too.
Edit: I guess you know, reading your CM thread, but some may not....
Would welcome some more development, especially bluetooth connecting to audio is horrible...
I tried his other roms too, only got carbon working nicely.
Click to expand...
Click to collapse
yeah, that's Alex Midnight (mrAlmid), i used some huawei binaries off his roms already.
i will see what i can do about bluetooth a2dp, dont have to much hope though, that a2dp stuff was a hell on LG's p990 already.

why are we waiting...

Waiting for the sources that is, what are porters planning on sticking on this? Personally I want the sources to attempt to port Sailfish, only reason I bough the phone. I currently have the Nexus 5 and the OS runs buttery smooth thanks to the porters over at #sailfishos-porters
Am even wondering did I make a mistake buying this device when the Nexus 5, is more than enough omph to power the OS. But I've got it and gotta try, to atleast expand my own knowledge base.
also do you guys know how chainfire managed to build the kernel for it without the sources?

WTF?
The phone has been out for less than a month. Have some patience or start learning to develop yourself, rather than creating a useless thread, just to whine.

I got my 5x last Tuesday and forgot how little I like "pure" android. I think the usual progression is flash aosp then flash cyanogenmod once the nightlies start to stabilize. I know I'm in the minority but the nexus phones usually have too much Google on them for my taste. I like the hardware, but the software is another story.
At any rate, I'm also waiting for the binaries and device tree so that I can start building my own.

m4r0v3r said:
Waiting for the sources that is, what are porters planning on sticking on this? Personally I want the sources to attempt to port Sailfish, only reason I bough the phone. I currently have the Nexus 5 and the OS runs buttery smooth thanks to the porters over at #sailfishos-porters
Am even wondering did I make a mistake buying this device when the Nexus 5, is more than enough omph to power the OS. But I've got it and gotta try, to atleast expand my own knowledge base.
also do you guys know how chainfire managed to build the kernel for it without the sources?
Click to expand...
Click to collapse
If you knew much about how android works, you'd know that chainfire didn't make a kernel. He took the boot image and modified some fstab, prop, and sepolicy stuff, repackaged it, and released it. He didn't build his own kernel.
In any case, I'm curious about this, how long does it usually take google to release their sources?
Sent from my Nexus 5X using Tapatalk

sn0warmy said:
WTF?
The phone has been out for less than a month. Have some patience or start learning to develop yourself, rather than creating a useless thread, just to whine.
Click to expand...
Click to collapse
oh yeah Ill just go and create a kernel, and while am at it, I may as well write my own drivers. Maybe I'll call my kernel linox, and adopt this policy of sharing my source code so other people could collaborate. Maybe using some sort of version control, call Hit or something, maybe on some website called HitHub.
Yeah that sounds like a good way to develop it...Or Google could hurry the **** up and release the sources and binaries so I wouldn't have to.
Well if you read my post you'd see I was curious about what people wanted to port.
drsn0w said:
If you knew much about how android works, you'd know that chainfire didn't make a kernel. He took the boot image and modified some fstab, prop, and sepolicy stuff, repackaged it, and released it. He didn't build his own kernel.
In any case, I'm curious about this, how long does it usually take google to release their sources?
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
Not make but people have been saying it was built with forceencrypt disabled so I thought he built the kernel with that flag, (ie he had the sources). But it seems thats not the place to change it

Wow the self-entitlement is real nowadays, patience bro. You cant have everything instantly when you want it.
m4r0v3r said:
oh yeah Ill just go and create a kernel, and while am at it, I may as well write my own drivers. Maybe I'll call my kernel linox, and adopt this policy of sharing my source code so other people could collaborate. Maybe using some sort of version control, call Hit or something, maybe on some website called HitHub.
Yeah that sounds like a good way to develop it...Or Google could hurry the **** up and release the sources and binaries so I wouldn't have to.
Well if you read my post you'd see I was curious about what people wanted to port.
Not make but people have been saying it was built with forceencrypt disabled so I thought he built the kernel with that flag, (ie he had the sources). But it seems thats not the place to change it
Click to expand...
Click to collapse

timjp692 said:
Wow the self-entitlement is real nowadays, patience bro. You cant have everything instantly when you want it.
Click to expand...
Click to collapse
what to expect an open source based phone to have the sources with it?
No I know I can't have everything when I instantly want it, but really what could be the reason for the delay. Since am already pretty pissed about the force encryption.

m4r0v3r said:
what to expect an open source based phone to have the sources with it?
No I know I can't have everything when I instantly want it, but really what could be the reason for the delay. Since am already pretty pissed about the force encryption.
Click to expand...
Click to collapse
I'm sorry, but you sound like a whiney little 12 year old who is used to having everything they want RIGHT when they want it. Kind of sums up the turn this forum has taken over the past couple of years.
In the real world you'll learn that good things take time. The phrase, "patience is a virtue" holds true merit.

Offer a bounty if you're that impatient.

sn0warmy said:
I'm sorry, but you sound like a whiney little 12 year old who is used to having everything they want RIGHT when they want it. Kind of sums up the turn this forum has taken over the past couple of years.
In the real world you'll learn that good things take time. The phrase, "patience is a virtue" holds true merit.
Click to expand...
Click to collapse
Apology accepted.

bblzd said:
Offer a bounty if you're that impatient.
Click to expand...
Click to collapse
For what exactly? Someone to break in Google servers and take the source code? lol

m4r0v3r said:
For what exactly? Someone to break in Google servers and take the source code? lol
Click to expand...
Click to collapse
I'm waiting too- it's not like google is still working on the binary drivers and just building the production rom with hacked up device trees until they get the real ones. I could be mis-remembering, but in the past, I thought the factory roms and binary drivers were available the day the devices were released.
I can certainly understand being patient with devs who are working on roms (for free/beer/donations), but google is done with the rom and has already released it to production. The factory image for the 6p was delayed as well. It's not a secret- they are going to push it to every one who bought a phone. My conspiracy theory is that google is trying to bury aosp, and merging android and chrome will be another stab into the heart of both privacy and freedom.

and its outtt

m4r0v3r said:
and its outtt
Click to expand...
Click to collapse
Waiting for some real nexus thing then

[ROM][UNOFFICIAL][CM12.1][5.1.1][ALPHA][KIWI][2/1/2016 security]

Preface:Lots of great developers have been bringing Cyanogenmod to the Honor 5X, but no one has posted any experimental builds for people to flash. Since I have been able to build CM with the sources other developers have kindly created, I would like to share builds for others to try out on their devices without having to setup an Android build environment.
I would like to clarify a few things:
These builds are UNOFFICIAL and may not be daily driver material.
I just build these ROMs from sources OTHER developers create. See credits below for developer list.
I cannot provide ETAs for the next build, new features, or anything else.
I have only tested these builds on KIW-24, so other variants might not support this ROM.
You are solely responsible for flashing this ROM along with any damage that might result from said flash. See the disclamer.
See post 1 for install instructions and downloads
See post 2 for screenshots and changelogs
Disclaimer: Voided warranties, bricked devices, rogue alarms at 2AM etc. are all your own problem. Neither any developer nor XDA is responsible for any unpleasantness that may result from using this ROM.
Credits:
@deadman96385
@CosmoDroid
@crpalmer
 @InkSlinger420
@EarlyMon
@wimbet
@Chainfire
Cyanogenmod
Google
And anyone else I might have missed. Let me know if I should add someone else to the credits.

To flash this ROM you need to:
Unlock bootloader and install TWRP
Boot into TWRP, perform wipe, and then flash ROM .zip and optional gapps *NOTE* non kiw-24 users see this post for information on flashing.
Reboot, and enjoy CM on the Honor 5X
Unofficial ROM Downloads:
3-10-16 - REMOVED by OP
Optional Gapps Downloads:
http://opengapps.org/ (ARM64, 5.1.1, Full)

Changelog:
3-10-16 - Initial build. (Tested) working features; wifi, BT, (some) data/LTE, normal phone features.
Known bugs:
No rear camera
No fingerprint sensor
No extra kernel features like Tap To Wake
Some cellular/data features may not work. I can't test this so check posts below to see if someone else can confirm.
Screenshots attached.

Del

Zakaria.R said:
Why is it kiw-24 specific ? I read on the other thread that it worked just fine on another variant
Click to expand...
Click to collapse
I can only test on kiw-24. Another user has reported being able to flash ROM on kiw-22. If you or someone else can confirm that this will work on other variants, I'll update the OP.

Nothing was posted cause there is still things that need to be fixed...lol.. Bugs in builds suck..

Awesome! 40 days after US release. ( i know its been around these forums for a little while) but having a flash-able file is a big bonus. Any general working or not working info ?

InkSlinger420 said:
Nothing was posted cause there is still things that need to be fixed...lol.. Bugs in builds suck..
Click to expand...
Click to collapse
I didn't mean to imply that other devs where in anyway at fault for no posted builds. I understand the desire to focus on fixing bugs rather than maintaining builds, but there a lot of people, myself included, that don't mind running buggy builds if we can get a taste of CM.
By the way, do you want me to add you to the credits?

eruji said:
Awesome! 40 days after US release. ( i know its been around these forums for a little while) but having a flash-able file is a big bonus. Any general working or not working info ?
Click to expand...
Click to collapse
See post #3/reply #2

Bandit Development said:
I can only test on kiw-24. Another user has reported being able to flash ROM on kiw-22. If you or someone else can confirm that this will work on other variants, I'll update the OP.
Click to expand...
Click to collapse
Thanks for replying fast man, actually I don't own the device yet, I was following the development here and thanks to you guys I might consider getting it, you made a big difference hope you keep on with this, your work is much appreciated :victory:

Bandit Development said:
I didn't mean to imply that other devs where in anyway at fault for no posted builds. I understand the desire to focus on fixing bugs rather than maintaining builds, but there a lot of people, myself included, that don't mind running buggy builds if we can get a taste of CM.
By the way, do you want me to add you to the credits?
Click to expand...
Click to collapse
My deal is this... I also have builds of BrokenOs (my rom) for this device but i havent posted any for public use, for one reason...Respect... @crpalmer is doing 95% of the legwork for this device over there at CM and Im sure once hes ready and comfortable with where it is, he will announce builds somewhere for it....I think its both premature, and kinda crappy, to make public someones work before even they think its ready for public use.... My 2 cents... Oh, and i dont care about credit for anything..Im just a rom dev, i get enough for that....

InkSlinger420 said:
My deal is this... I also have builds of BrokenOs (my rom) for this device but i havent posted any for public use, for one reason...Respect... @crpalmer is doing 95% of the legwork for this device over there at CM and Im sure once hes ready and comfortable with where it is, he will announce builds somewhere for it....I think its both premature, and kinda crappy, to make public someones work before even they think its ready for public use.... My 2 cents... Oh, and i dont care about credit for anything..Im just a rom dev, i get enough for that....
Click to expand...
Click to collapse
Thanks for your input. I certainly do respect @crpalmer along with all the other devs who have worked on this device, and I in no way want to detract from the fame/glory/respect they are due for all their hard work.
@crpalmer or any other dev, if you want me to remove this thread or change it in any way, please let me know. I don't want to step on anyone's toes. I was only trying to help others get a early taste of CM so they didn't have to build it themselves.

Appreciate the credit but I just fetch coffee and hound Huawei when necessary for devs doing actual work.
No harm removing me from the credits.

Thnx to all the devs trying real hard to get these awesome roms on our device.... Really appreciated
Sent from my KIW-L21 using Tapatalk

Bandit Development said:
Thanks for your input. I certainly do respect @crpalmer along with all the other devs who have worked on this device, and I in no way want to detract from the fame/glory/respect they are due for all their hard work.
@crpalmer or any other dev, if you want me to remove this thread or change it in any way, please let me know. I don't want to step on anyone's toes. I was only trying to help others get a early taste of CM so they didn't have to build it themselves.
Click to expand...
Click to collapse
Thank you @Bandit Development for the build. While I understand where @InkSlinger420 is coming from I much prefer the state of where @crpalmer has brough CM to over stock. I've been running this for about 4 hours. GPS works great, data and phone work great. Most importantly switching between apps doesn't draaaaaaaag.

Hopefully those responsible for the hard work on this rom will realize this wasn't an attempt to grab the spotlight, but rather a way to placate the masses. Also, needed or not, there is valuable information even in the few early posts because not everyone uses their phones the same way, so one person may never run into a bug that another person sees frequently.
Fingers crossed, but perhaps this thread will also limit the number of posts in the [Dev] thread asking when etc.......... I know I filled it with build questions which probably didn't belong there either. However, I'm trying to learn a little about rom development and one of the first steps to that is to be able to build the rom so you can test your tweaks, or at least see how someone else's changes affect the phone.

Bandit Development said:
I didn't mean to imply that other devs where in anyway at fault for no posted builds. I understand the desire to focus on fixing bugs rather than maintaining builds, but there a lot of people, myself included, that don't mind running buggy builds if we can get a taste of CM.
By the way, do you want me to add you to the credits?
Click to expand...
Click to collapse
It would take me approximately 30 seconds to add automatic nightly builds to my autobuild server (I already generate some builds every night).
Consider that and the fact that I haven't done so as an indication of whether or not I thought builds should be posted right now...

crpalmer said:
It would take me approximately 30 seconds to add automatic nightly builds to my autobuild server (I already generate some builds every night).
Consider that and the fact that I haven't done so as an indication of whether or not I thought builds should be posted right now...
Click to expand...
Click to collapse
Wow, didn't realize you have a server dedicated to building. Because of this, I did not know that you wanted to wait to post builds. Would you like me to ask an admin to remove this thread? I sincerely don't want to mess with your work, plans, or anything else.

Bandit Development said:
Wow, didn't realize you have a server dedicated to building. Because of this, I did not know that you wanted to wait to post builds. Would you like me to ask an admin to remove this thread? I sincerely don't want to mess with your work, plans, or anything else.
Click to expand...
Click to collapse
You don't need to remove the thread, I am just pointing out that I don't think that the build is at a level of quality that represents well the work of CyanogenMod.

crpalmer said:
You don't need to remove the thread, I am just pointing out that I don't think that the build is at a level of quality that represents well the work of CyanogenMod.
Click to expand...
Click to collapse
Well, I'm happy to let you take over cooking builds if you'd like. I certainly don't claim to be able to make quality builds.
I would really appreciate any tips/info you'd like to share that would improve my builds. I've been trying to learn how to fix bugs and contribute to the ROM development, but the task seems to be a rather undocumented and slow-going.

Android 8 - ROM release

Do you know when we can expect a ROM based on Android O?

Can't say for sure. May never see an official release from Nextbit/Razer, but I'm sure custom rom devs will release it when it's ready.

davehasninjas said:
Can't say for sure. May never see an official release from Nextbit/Razer, but I'm sure custom rom devs will release it when it's ready.
Click to expand...
Click to collapse
Didn't Nextbit or Razer hire the devs from Paranoid Android? If they are working on the Robin ROM, I'm pretty sure it's safe to say we'll get Oreo. However Razer announced a gaming phone a while ago, so there is no way to tell.

Baconator724 said:
Didn't Nextbit or Razer hire the devs from Paranoid Android? If they are working on the Robin ROM, I'm pretty sure it's safe to say we'll get Oreo. However Razer announced a gaming phone a while ago, so there is no way to tell.
Click to expand...
Click to collapse
One of the Developer's for PA is also one of the 30 teams members of nextbit.

There are quite a few links like these which mention Lineage OS 15 (Oreo) supported devices and robin is one of them! I cant wait for the release!
http://www.lineageosdownloads.com/lineage-os-15-supported-device-list/

protonsavy said:
There are quite a few links like these which mention Lineage OS 15 (Oreo) supported devices and robin is one of them! I cant wait for the release!
http://www.lineageosdownloads.com/lineage-os-15-supported-device-list/
Click to expand...
Click to collapse
Except those are all fake. The LOS maintainers won't actually know if a device will support LOS 15 until they actually try porting it in the first place. As of now, they haven't tried for the Nextbit Robin yet, so we don't know if the Robin could actually get LOS 15 yet.
If you wanna keep tabs on what devices are currently being worked on, go to https://review.lineageos.org/#/q/statuspen and look for anything being commited to the lineageos-15.0 branch for android_device_nextbit_ether.

Software updates till February as they say on Twitter. Apart from nextbits cloud framework the OS is pretty much stock AOSP and it seems to me they're really good with releasing kernel source and providing updates almost every three months.

Robin, on N, is a mess. If it does eventually get O, it will be a while. We cannot upgrade it to O until we fix out the bugs we have on N first.

What are the bugs on N? I'm thinking about buying one. Is it worth it?

oh1blksheep said:
What are the bugs on N? I'm thinking about buying one. Is it worth it?
Click to expand...
Click to collapse
Camera, GPS, battery blah the list goes on. The kernels a mess because of bad sources. I wouldnt recommend it , it would be better getting a moto G device or similar at this stage.

DarkExistence said:
Camera, GPS, battery blah the list goes on. The kernels a mess because of bad sources. I wouldnt recommend it , it would be better getting a moto G device or similar at this stage.
Click to expand...
Click to collapse
I have two devices, and I don't have troubles with it.

HeaDekBatHblu said:
I have two devices, and I don't have troubles with it.
Click to expand...
Click to collapse
Doesn't make a difference, the code base is a mess. If your buying for a Dev device, dont. Even the top lineage Devs are struggling to make it as stable as it is (and it's not very stable, messy as hell!) As an every day device it's ok but there are better phones now a days in the price range, and support is basically dead for robin now.

DarkExistence said:
Doesn't make a difference, the code base is a mess. If your buying for a Dev device, dont. Even the top lineage Devs are struggling to make it as stable as it is (and it's not very stable, messy as hell!) As an every day device it's ok but there are better phones now a days in the price range, and support is basically dead for robin now.
Click to expand...
Click to collapse
Development is not dead at all. Have you seen Gerrit for many of the ROMs??? The CarbonROM Dev already has pushes to Gerrit for O. Lineage still gets device specific changes. ParanoidAndroid has a private kernel source for ether so their working on it behind the scenes. AICP and many other ROMs use the Lineage kernel, so there aren't many differences to those that use that kernel. O development is still ongoing, and this device is still great for the price. The ROMs at the moment, are very stable in my opinion.

xWolf13 said:
Development is not dead at all. Have you seen Gerrit for many of the ROMs??? The CarbonROM Dev already has pushes to Gerrit for O. Lineage still gets device specific changes. ParanoidAndroid has a private kernel source for ether so their working on it behind the scenes. AICP and many other ROMs use the Lineage kernel, so there aren't many differences to those that use that kernel. O development is still ongoing, and this device is still great for the price. The ROMs at the moment, are very stable in my opinion.
Click to expand...
Click to collapse
I know, I'm the AICP maintainer for ether lol... And discuss with the official lineage maintainers for ether daily ..
I meant official development, btw, meaning a lot of the bugs won't be fixed because we need official updates to be able to fix them.
O development for lineage ether hasn't even begun yet, N bugs need to be fixed before O begins, and that will take awhile.

DarkExistence said:
I know, I'm the AICP maintainer for ether lol... And discuss with the official lineage maintainers for ether daily ..
I meant official development, btw, meaning a lot of the bugs won't be fixed because we need official updates to be able to fix them.
O development for lineage ether hasn't even begun yet, N bugs need to be fixed before O begins, and that will take awhile.
Click to expand...
Click to collapse
My apologies if I seemed aggressive. Official development seems to be like any other manufacturer, however, as we all know, software support is ending soon. I've been following Gerrit and have noticed the ongoing development by our developers (including you). IIRC camera was borked on one of the nightlies, but was immediately fixed. IMO, we are now depending on development from our ether devs rather than official support since Nextbit have been ghosting for the past few months.

oh1blksheep said:
What are the bugs on N? I'm thinking about buying one. Is it worth it?
Click to expand...
Click to collapse
Keep in mind what DarkExistence said, and realize the Robin's closest equivalent is a Nexus 5. If you can get better & newer hardware for a little more money, do so. I got mine as an "emergency" replacement when I was short on funds a few months ago. I lucked into an eBay sale & discount code which brought the phone to about 100.00. I'm happy with it, but I wish Razer would have made good sources available & gave full permission for them to be hosted elsewhere. So the devs didn't get so frustrated with what should be a decent phone to run custom ROMs on.
Sent from my Robin using XDA Labs

So how us the Robin treating you. Did you root? ARE you using any ROMs

oh1blksheep said:
What are the bugs on N? I'm thinking about buying one. Is it worth it?
Click to expand...
Click to collapse
Yes, for $130 it's worth buying. The bugs on android N are not nearly as bad as what some claim them to be.
Here's as list of what I can recall:
1. Enhance colors distorts colors (so turn it off)
2. Screen static displays when unlocking phone for 1/10th of a second with some roms
3. You can hear The Speakers turn off after sound has stopped playing if You listen closely
4. Headphones with a mic sometimes cut out and play through internal Speakers although there is as work around for this
5. Audio fx does not work
Other than any of those there is not much i can personally complain about and I own 2 robins. About to get a moto g4 plus because it's time for something that has a larger XDA fourm and something that has been confirmed to get android O (wich nextbit has yet to announce a decision to besides "we have been discussing it").
If I were You and my budget was under $200 i'd get The robin.
If You can spend $225 get The g4 plus without a doubt. Hope this helps

oh1blksheep said:
So how us the Robin treating you. Did you root? ARE you using any ROMs
Click to expand...
Click to collapse
I like it, especially for the price. Currently using CarbonROM rooted with Magisk. Just realize you're getting a phone with zero support from the manufacturer, so don't spend more than you're willing to lose.
Sent from my Robin using XDA Labs

DarkExistence said:
I know, I'm the AICP maintainer for ether lol... And discuss with the official lineage maintainers for ether daily ..
I meant official development, btw, meaning a lot of the bugs won't be fixed because we need official updates to be able to fix them.
O development for lineage ether hasn't even begun yet, N bugs need to be fixed before O begins, and that will take awhile.
Click to expand...
Click to collapse
Well thank you for being the maintainer on Ether. I just ordered the phone. 129.00 for a phone with these specs. Couldn't pass it up. I'm sure you will eventually make AICP stable. Thank you for your honesty.