No More Official CM12 Nightlies for the G2? - G2 General
I know this is yesterday's news but I felt compelled to post this and get other users input on this topic.
http://www.cyanogenmod.org/blog/releases-11-12-final
What I don't understand is Cyanogen's priorities when it comes to which devices get 11, 12 or 12.1. I completely understand about phasing out CM11/KitKat as that is now a rather "old" version of android. However what I don't understand is why a device as new/old as ours (Aug 2013 is not THAT old) is stuck on CM12 (and now a final Snapshot build as of 6/25)? I mean, the Galaxy S3 is even getting 12.1 builds. I'm wondering if its because that was a far more popular device than the G2 was?
Just wanted to put this out there and see what other people think and find out what they're running currently on their G2 variant. I own the US T-Mobile D801 variant and do NOT want to run stock (LG) Lollipop since my device tends to run extremely HOT on it. I know not everyone was complaining about their G2 overheating on stock LP but I notice a considerable difference running CM12.
So, how do you guys feel about this? Do you even care or what?
t3chn0s1s said:
I know this is yesterday's news but I felt compelled to post this and get other users input on this topic.
http://www.cyanogenmod.org/blog/releases-11-12-final
What I don't understand is Cyanogen's priorities when it comes to which devices get 11, 12 or 12.1. I completely understand about phasing out CM11/KitKat as that is now a rather "old" version of android. However what I don't understand is why a device as new/old as ours (Aug 2013 is not THAT old) is stuck on CM12 (and now a final Snapshot build as of 6/25)? I mean, the Galaxy S3 is even getting 12.1 builds. I'm wondering if its because that was a far more popular device than the G2 was?
Just wanted to put this out there and see what other people think and find out what they're running currently on their G2 variant. I own the US T-Mobile D801 variant and do NOT want to run stock (LG) Lollipop since my device tends to run extremely HOT on it. I know not everyone was complaining about their G2 overheating on stock LP but I notice a considerable difference running CM12.
So, how do you guys feel about this? Do you even care or what?
Click to expand...
Click to collapse
We haven't had nightlies for a while now. What you see as nightlies aren't really worthwhile builds, they didn't have any device or kernel fixes for the g2.
A new 11 build is coming probably because half the android userbase relies on kitkat at the moment.
As for the s3, it's not getting CM12 nor 12.1, not the international version at the least. Archi is maintaining an unofficial version, but it still carries the bugs from 10.0/10.1.
Lastly, this is the commit that requires to be merged in order for the builds to even be considered started:
http://review.cyanogenmod.org/#/c/93181/
Without it, nothing CAF related can be merged, and as such, no CM12.1 builds can be had for our device. I believe the reason it's not merged because not all of the variants have a lollipop release, if they ever will get one. Also the whole bootstack/amount of users who don't reed is astonishingly dangerous to handle, so rashed simply preferred to skip building for now.
Finally, it's not that popular of a device. It's a nexus without being a nexus with a locked bootloader, which is a pain in the ass and not too many maintainers have it left (they either went with G3 or skipped LG entirely, as did a whole bunch from the exynos team back in the day).
t3chn0s1s said:
I saw you responded to my post about CM12 nightlies not continuing for the G2. Wanted to ask you (since you didn't mention) what 5.1 (CAF source) ROM you're running? What would you suggest for a stable AOSP ROM that has device/kernel specific updates for our G2s?
Click to expand...
Click to collapse
Why not reply to me in this thread then?
I'm running official euphoria builds. Any caf roms run fine. They are all based on the same LG-devs CAF device source + kernel source. Some roms have specific tweaks, but as far as functionality, they all work the same way (ie: if bluetooth deep sleep is broken, it's most likely broken in every rom).
Choristav said:
Why not reply to me in this thread then?
I'm running official euphoria builds. Any caf roms run fine. They are all based on the same LG-devs CAF device source + kernel source. Some roms have specific tweaks, but as far as functionality, they all work the same way (ie: if bluetooth deep sleep is broken, it's most likely broken in every rom).
Click to expand...
Click to collapse
Sorry - was on my phone when I saw your replies and it was just easier for me to respond in the other thread.
Anyways.. thanks for the info. I've done some research and I'm a bit more informed about CAF and what it means to device specific sources, ROMs, etc. Are you just using the stock Euphoria kernel or something else?
On this forum @varund7726 builds his rather excellent ResurrectionRom from the latest CM code release. I suggest you use that. For the D803, @zr239 has beaten all odds including LG not releasing CAF code, to build a fully functional pure CM 12.1 ROM that closely tracks official CM repos.
Lg G2 has it pretty good !
@Choristav
I wanted to clarify something you said in your initial response to my OP. You said the S3 wasn't going to get CM12 or 12.1 but when I navigate to the CM downloads page for ANY S3 variant - they ALL have CM12.1 nightlies still being generated. What exactly did you mean?
t3chn0s1s said:
@Choristav
I wanted to clarify something you said in your initial response to my OP. You said the S3 wasn't going to get CM12 or 12.1 but when I navigate to the CM downloads page for ANY S3 variant - they ALL have CM12.1 nightlies still being generated. What exactly did you mean?
Click to expand...
Click to collapse
I checked, you are right, several of the qualcomm variants have cyanogenmod support. This means that they have active maintainers, but they also don't have to deal with locked bootloader crap, which is why the bump commit is so important for our device.
I only mentioned the international version, which support was dropped because it had a lot of issues thanks to its closed source exynos processor (it requires extra work, and some stuff doesn't end up working anyway).
Not really much to say, the commit is already in CM's gerrit, it's just waiting for review. Maybe it's a CTS-side issue?
Aside from that, being a maintainer doesn't really require much, just effort and presence. It's not an easy task, I'm just saying anyone can apply to be a maintainer and get nighties rolling for a device you might not even have heard of.
@Rashed97 is the man for our G2 when it comes to CM. Dont mind nightlies as long as Rashed is around
Note: he is currently busy with the One M9 but we will hopefully see some cool stuff from him in the future.
Not really a big deal, last I remember those nightlies were still using outdated jellybean components. I wouldn't use them, I would use something on the G2 forums like Rashed97 builds like someone else said.
I don't think that the availability of nightlies has to do with the device itself so much as it has to do with someone maintaining the g2 and building roms, so nightlies could come back at any time if someone steps up and does it.
Ploxorz said:
Not really a big deal, last I remember those nightlies were still using outdated jellybean components. I wouldn't use them, I would use something on the G2 forums like Rashed97 builds like someone else said.
I don't think that the availability of nightlies has to do with the device itself so much as it has to do with someone maintaining the g2 and building roms, so nightlies could come back at any time if someone steps up and does it.
Click to expand...
Click to collapse
And it appears you're correct as there is another nightly build up with today's date. I apparently posted this thread prematurely.
Guys I wouldnt worry to much about CM, its not like they are the only (or even best) option in the forums. If you guys want development then dig in and make some for it.
zelendel said:
Guys I wouldnt worry to much about CM, its not like they are the only (or even best) option in the forums. If you guys want development then dig in and make some for it.
Click to expand...
Click to collapse
You are absolutely right. I had no idea until I posted this thread that CM nightlies did not contain any device specific updates. I honestly NEVER used to like CM at all. I honestly hated it... until owning a OnePlus One. I originally had the G2 right when it came out in 2013 and sold it off long ago & moved on to better devices - but when my OPO got stolen about 2 months back or so - I had to find a relatively cheap, but decent device and the G2 was the best bang for the buck (5.2" display, quick charge 2.0, 3000 mAh battery) and no other phones in 2013 came close to the specs the G2 had at the time.
So, now that I know CM is basically a sh*t ROM for this device I'll be moving on to a ROM that is compiled using CAF sources. Thanks everyone for your input!
Somehow doesn't look too good so far:
https://jira.cyanogenmod.org/browse/CYAN-6556
But why oh why?
The LG G2 still is such a modern and powerful device. It might be almost two years "old", but it's way better than a lot of other current devices.
I am using AICP on my g2. It is based on CM(5.1.1).
What's the best place to follow updates / changes to the CAF stuff?
I know there's a handful of ROMs based on CAF sources, I'm not too interested in the changelogs of those ROMs, more following the progress of CAF before it eventually all gets merged into CM12.1.
Is this it? https://github.com/lg-devs/android_device_lge_g2-common/commits/cm-12.1-caf
seanp25 said:
What's the best place to follow updates / changes to the CAF stuff?
I know there's a handful of ROMs based on CAF sources, I'm not too interested in the changelogs of those ROMs, more following the progress of CAF before it eventually all gets merged into CM12.1.
Is this it? https://github.com/lg-devs/android_device_lge_g2-common/commits/cm-12.1-caf
Click to expand...
Click to collapse
I would watch the Code Aurora forums where CAF comes from.
zelendel said:
I would watch the Code Aurora forums where CAF comes from.
Click to expand...
Click to collapse
It's better to watch public activity on Rashed97's github. He is CM maintainer for LG G2 and he brought up CAF sources for our devices.
adamz667 said:
It's better to watch public activity on Rashed97's github. He is CM maintainer for LG G2 and he brought up CAF sources for our devices.
Click to expand...
Click to collapse
No. It's far better to watch the main code base. Cm messes too much up by not testing code before merging.
zelendel said:
No. It's far better to watch the main code base. Cm messes too much up by not testing code before merging.
Click to expand...
Click to collapse
Okay, but @seanp25 probably want to follow source changes for our device, not common CAF source.
Just saw this:
Çetin ÇÖNE wrote on Jul 26 11:18 AM:
Why there is no nighlies it's really stable. Merge it please
Seth Shelnutt wrote on Jul 26 1:26 PM:
There are no nightlies because SELinux is not enabled. Sensors break with it enabled and I don't have time to address it yet.
Click to expand...
Click to collapse
Source:
http://review.cyanogenmod.org/#/c/103673/
Some days after that there came this:
http://review.cyanogenmod.org/#/c/103674/
So maybe there soon will be 12.1 nightlies?
Related
UNOFFICIAL CM9 Nightly and Alpha 0.6
anyone know that what is difference between Unofficial CM9 Nightly and alpha 0.6 ?
hki_peter said: anyone know that what is difference between Unofficial CM9 Nightly and alpha 0.6 ? Click to expand... Click to collapse Nightlies are probably going to be less stable. Basically, when you get a nightly, it's not yet been released. It's what somebody was working on last night...when they quit working on it, whether successful in what they had been working on or not, it was uploaded - hence the name, nightly. And now you know. And knowing's half the battle.
sean is here. said: Nightlies are probably going to be less stable. Basically, when you get a nightly, it's not yet been released. It's what somebody was working on last night...when they quit working on it, whether successful in what they had been working on or not, it was uploaded - hence the name, nightly. And now you know. And knowing's half the battle. Click to expand... Click to collapse Well its slightly more than just something someone happened to be working on and left it! I'm using the KANG of 20120216 and finding it is far better than my experience with .06! And I'm about to flash 20120217.
pa49 said: Well its slightly more than just something someone happened to be working on and left it! I'm using the KANG of 20120216 and finding it is far better than my experience with .06! And I'm about to flash 20120217. Click to expand... Click to collapse EDIT: I re-read this reply after posting my response, and the first sentence is just incorrect. A 'nightly' is nothing "more than just something someone happened to be working on and left it". The rest is subjective opinion, but the definition of what a nightly is can be found clearly explained below. I think you've misunderstood me, or something else somewhere along the line. I'm not saying that they're better or worse than official releases. I was merely pointing out that the way they come about, is that they aren't fully evaluated and tested for stability in order to be released publicly as a finished product. Before a major release, devs will typically spent time testing their software themselves, in addition to sending it out to 'focus groups' (they aren't REALLY focus groups but serve the same function) where they are further tested...then upon completion of testing, or when a threshold of minimum functionality has been reached (often with a pre-specified maximum number of bugs or critical failures) they can be released publicly. Nightlies don't go through that extensive testing. That's where the name comes from. The devs 'clock out' and the ROM is built, and posted as a 'nightly'. From the CM Team: ... Lastly we have the Nightlies, which are as volatile as a firmware can get. These releases keep coming at an interval of a day or two and if you do end up trying one of these, do not be alarmed if the your device goes cuckoo on you. These ROMs are largely untested, and as advised by CyanogenMod, not meant for use for an average user. These releases, are meant to test untested waters with tweaked codes that may or may not break your phone. Click to expand... Click to collapse
My understanding was that the nightlies were being built automatically by a script that pulls the most recent source from the cm server. As new code is added daily by devs it is automatically put into nightly builds for testing.
joggerman said: My understanding was that the nightlies were being built automatically by a script that pulls the most recent source from the cm server. As new code is added daily by devs it is automatically put into nightly builds for testing. Click to expand... Click to collapse As far as I'm aware, you are correct.
Hey guys, I just want to add, the one of the developers of the official CM9 alpha release is recommending users install the nightly as there may not be an official update pushed put anytime soon. http://liliputing.com/2012/02/nightly-builds-of-cyanogenmod-9-for-the-hp-touchpad-now-available.html
Anyone know which nightly is pretty stable?
wonshikee said: Anyone know which nightly is pretty stable? Click to expand... Click to collapse go for alpha 1 as dalingrin said the nightlies won't be based on alpha 1 until a few days later.
Which cyanogenmod build? Official or mdm?
So i'm a bit confused. Which builds are better for fireball? The official cyanogen nightly or the unofficial mdm builds? I can't post in the offical dev post for cyanogen so i have to post here. Right now i'm running the latest nightly. All seems to be be pretty stable. Just missing 16:9 for the camera, and once in a while while i'm running with my nikeplus app and the google music playing, if i hit the power button to turn off the screen it resets the entire device. Anyways, i can't tell which builds are better / ahead of the others? Sorry i know i posted this in another forum, but it was the wrong forum.
danjfoley said: So i'm a bit confused. Which builds are better for fireball? The official cyanogen nightly or the unofficial mdm builds? I can't post in the offical dev post for cyanogen so i have to post here. Right now i'm running the latest nightly. All seems to be be pretty stable. Just missing 16:9 for the camera, and once in a while while i'm running with my nikeplus app and the google music playing, if i hit the power button to turn off the screen it resets the entire device. Anyways, i can't tell which builds are better / ahead of the others? Sorry i know i posted this in another forum, but it was the wrong forum. Click to expand... Click to collapse I use MDM builds because I have the flicker issue from the cynagen 3.4 kernel. I don't think I've had any random reboots on the MDM like I did with the cyanogen nightlies.
Why then are the mdm releases.. or the guy behind the mdm releases, not working on the official releases? I mean why is his hard work not going into the official releases? I feel like if i switch to mdm i'm going to miss fixes in the official nightlys.. as it's just one guy working on it. Just doesn't make sense. the official releases are open sourced at git hub right? So why isn't the mdm guy working on the official releases?
danjfoley said: Why then are the mdm releases.. or the guy behind the mdm releases, not working on the official releases? I mean why is his hard work not going into the official releases? I feel like if i switch to mdm i'm going to miss fixes in the official nightlys.. as it's just one guy working on it. Just doesn't make sense. the official releases are open sourced at git hub right? So why isn't the mdm guy working on the official releases? Click to expand... Click to collapse @mdmower is working on official releases. instead of merging patches that might cripple the officials he is doing "beta" test outside of it. hence why he's always asking for feed back. once he gets enough feedback on the mdm builds he submits a patch to cm and it gets merged into source. ^_^ i would go with the mdm5 build because it has a working camera focus but once he merges the RIL commit i will be going back because i like the stability of the officials minus the RIL hickup i had. but everyone is different and will react differently.
where did you get the 3.4 kernel? Sum Dumb Guy said: I use MDM builds because I have the flicker issue from the cynagen 3.4 kernel. I don't think I've had any random reboots on the MDM like I did with the cyanogen nightlies. Click to expand... Click to collapse where did you get the 3.4 kernel?
synisterwolf said: @mdmower is working on official releases. instead of merging patches that might cripple the officials he is doing "beta" test outside of it. hence why he's always asking for feed back. once he gets enough feedback on the mdm builds he submits a patch to cm and it gets merged into source. ^_^ i would go with the mdm5 build because it has a working camera focus but once he merges the RIL commit i will be going back because i like the stability of the officials minus the RIL hickup i had. but everyone is different and will react differently. Click to expand... Click to collapse This is mostly right, just couple clarifications: mdm releases exist because CyanogenMod cannot publish releases that include a certain proprietary camera file. They are based on the latest stable CyanogenMod release (10.1.2) with a few tweaks that improve stability. Typically, these changes are backports from nightlies. In my opinion, these are the most functional CyanogenMod releases to date. Unfortunately, the kernel in use by these releases had to be dropped in order to prevent legal repercussions to CyanogenMod from closed-minded manufacturers. I am actively working on the official nightlies. Unfortunately, HTC has not released kernel source for this phone that is meant to work with jellybean. Furthermore, hardware support (for every phone out there) still relies on closed-source manufacturer drivers/blobs, and this phone hasn't seen a jellybean release yet. Long story short, there's stuff that just doesn't work because of lack of jellybean-compatible kernel/firmware/drivers from HTC.
mdmower said: This is mostly right, just couple clarifications: mdm releases exist because CyanogenMod cannot publish releases that include a certain proprietary camera file. They are based on the latest stable CyanogenMod release (10.1.2) with a few tweaks that improve stability. Typically, these changes are backports from nightlies. In my opinion, these are the most functional CyanogenMod releases to date. Unfortunately, the kernel in use by these releases had to be dropped in order to prevent legal repercussions to CyanogenMod from closed-minded manufacturers. I am actively working on the official nightlies. Unfortunately, HTC has not released kernel source for this phone that is meant to work with jellybean. Furthermore, hardware support (for every phone out there) still relies on closed-source manufacturer drivers/blobs, and this phone hasn't seen a jellybean release yet. Long story short, there's stuff that just doesn't work because of lack of jellybean-compatible kernel/firmware/drivers from HTC. Click to expand... Click to collapse and thats why i like the XDA page system. ^_^ straight from the source ladies and gentlemen. thank you for clearing that up.
bad_christian said: where did you get the 3.4 kernel? Click to expand... Click to collapse 3.4 are part of the official nightly releases. MDM uses 3.0.xx Kernels that are more stable for my phone.
KitKat New Linux Kernel
With KitKat introducing a new kernel base for Android, what's the likelihood of the i9300 getting a port anytime soon, or can that even be determined before source is released? I have only a basic knowledge of kernel building and so I thought I might turn to you more experienced devs. Only recently purchased this phone, but obviously without proper Exynos sources any major changes in Android are very difficult to deal with. This is not an ETA question, just curious if there's an idea of how much of a ***** such a new kernel will be. For those that haven't read this yet (if there are any), KitKat looks slated to run on top of either a 3.4 or 3.8 kernel. Sent from my GT-I9300 using Tapatalk 4
Shakes27 said: With KitKat introducing a new kernel base for Android, what's the likelihood of the i9300 getting a port anytime soon, or can that even be determined before source is released? I have only a basic knowledge of kernel building and so I thought I might turn to you more experienced devs. Only recently purchased this phone, but obviously without proper Exynos sources any major changes in Android are very difficult to deal with. This is not an ETA question, just curious if there's an idea of how much of a ***** such a new kernel will be. For those that haven't read this yet (if there are any), KitKat looks slated to run on top of either a 3.4 or 3.8 kernel. Sent from my GT-I9300 using Tapatalk 4 Click to expand... Click to collapse I'm not a dev but I'm gonna answer this as far as my knowledge goes with android so if I'm wrong please be gentle with me lol. Anyway... actually you kinda answered your own question. Until official sources are given no port or even a kernel based on 3.4 or 3.8 will be impossible. Even the main dev of boeffla kernel is kinda pessimistic on how his kernel can be based on latest linux kernel sources since an EOL (End of Life) has been issued on the 3.0 branch with 3.0.100 being the last one to be made. But I think KitKat based kernels seems to be quite far as of this time since 4.3 Jellybean hasn't even arrived yet to our devices. Again I'm not a dev so I maybe wrong on my opinion here. So any devs can shed a light here? I'm actually curious myself
SignetSphere said: 4.3 Jellybean hasn't even arrived yet to our devices. Click to expand... Click to collapse According to GSM Arena 4.3 update for the S3 should be rolling out next month :fingers-crossed:
Will we ever see Android 6.0 Marshmallow?
Maybe on CyanogenMod?
bpc4209 said: Maybe on CyanogenMod? Click to expand... Click to collapse The CM team is making good progress currently, along with their other devices. I'm also working on Pac-Rom sources. And if / when both of those work out, I'll try my hand at AICP. It really is only a matter of time for these things. As I have said in the past, as long as I'm rocking the Jewel, I'll be developing for it as my time allows.
UPDATE - For you builders out there, I'm pretty sure that CM 13.0 will actually compile cleanly now using no commits of any kind. But it won't boot yet. We're getting there.
ZTE working on Official cyanogenmod rom
Anyone else see this: https://9to5google.com/2016/09/19/zte-is-working-to-bring-an-official-cyanogenmod-rom-to-the-axon-7/
Yes, it's been discussed in the CM dev topic.
xtermmin said: Yes, it's been discussed in the CM dev topic. Click to expand... Click to collapse What most are not realizing, is that there are two versions of Cyanogen built operating systems. Cyanogen OS is built by Cyanogen Inc. for the device manufacturer and the other is community driven and is open source. These two operating systems may be identical in how they operate once on the device, but how they are developed is different. The question is which one is actually being developed?
jim262 said: What most are not realizing, is that there are two versions of Cyanogen built operating systems. Cyanogen OS is built by Cyanogen Inc. for the device manufacturer and the other is community driven and is open source. These two operating systems may be identical in how they operate once on the device, but how they are developed is different. The question is which one is actually being developed? Click to expand... Click to collapse http://forum.xda-developers.com/axon-7/development/cyanogenmod-13-a2017u-t3457410/page10
If it is a true CyanogenMod rom, that means ZTE would have to release proprietary source codes for open source development. They have not done that as of this writing. So more than likely a Cyanogen operating system will be created for this device totally in house, thereby not allowing for future development by the "open source" community of devs.
jim262 said: If it is a true CyanogenMod rom, that means ZTE would have to release proprietary source codes for open source development. They have not done that as of this writing. So more than likely a Cyanogen operating system will be created for this device totally in house, thereby not allowing for future development by the "open source" community of devs. Click to expand... Click to collapse From what I'm gathering from the discussions on the ZTE Community forums and the Cyanogenmod dev topic I linked, it seems that ZTE is sending their code to Cyanogen employee Steve Kondik to create an official cyanogenmod github for the A7, not that Cyanogen the company is going to create a CyanogenOS for the device.
Only for USA.
rikin93 said: Only for USA. Click to expand... Click to collapse Correction: Only for unlocked bootloaders, as it will not be officially signed by ZTE.
xtermmin said: From what I'm gathering from the discussions on the ZTE Community forums and the Cyanogenmod dev topic I linked, it seems that ZTE is sending their code to Cyanogen employee Steve Kondik to create an official cyanogenmod github for the A7, not that Cyanogen the company is going to create a CyanogenOS for the device. Click to expand... Click to collapse Based on what I have seen and heard, the difference between OS and Mod is nill. They are exactly the same. The difference between the two is how they are developed. One is open source and can be shared by the general public, the other is developed in house for the device manufacturer and proprietary information is kept in house and not shared. The two are quite often just referred to as CyanogenMod, although they are different.
jim262 said: Based on what I have seen and heard, the difference between OS and Mod is nill. They are exactly the same. The difference between the two is how they are developed. One is open source and can be shared by the general public, the other is developed in house for the device manufacturer and proprietary information is kept in house and not shared. The two are quite often just referred to as CyanogenMod, although they are different. Click to expand... Click to collapse There's a huge difference between CyanogenOS and CyanogenMod behind the scenes though. Like you said, CyanogenOS is in-house, but most importantly it tends to include bloatware, especially now that Cyanogen the company is owned by Microsoft. And since it's closed source, people who want to develop custom ROMs will still have no access to the sources that would speed up development. Plus, if there are bugs or features that people want to implement, they can't, and have to wait for Cyanogen to release them. This also means that things such as security patches will have to wait for official rollout by Cyanogen. Cyanogenmod, however, is open source, not controlled by Cyanogen the company at all, bug fixes / features can be added and addressed by the community, security patches can be applied to nightlies quickly, etc.
jim262 said: If it is a true CyanogenMod rom, that means ZTE would have to release proprietary source codes for open source development. They have not done that as of this writing. So more than likely a Cyanogen operating system will be created for this device totally in house, thereby not allowing for future development by the "open source" community of devs. Click to expand... Click to collapse It's been clarified multiple times on the ZTE forum that it will be CyanogenMod, not CyanogenOS. Unless there's some weird, first-time-in-history NDA regarding the HALs / overlay that ZTE provides for the development of CM, they will be open source.
If they did offer open source at least it would alleviate concerns on the Chinese state-sponsored company reputation
Finally, the best hardware of 2016 and all it needs is aosp love... I hope this helps to spur more development or makes it easier for our fantastic developers at XDA.
From what I read from the Employees at ZTE Forums, ZTE currently doesn't want to deal with setting up a place for Devs to access the needed resources for things, so they're basically going to just dump it all on CyanogenMod for them to sort it out. It's easier for the ZTE higher-ups to swallow that way.
Do we have any ETA on this ? I fear than the OP3 will get more love from the dev, and that the Axon 7 will be forgotten :/
rczrider said: It's been clarified multiple times on the ZTE forum that it will be CyanogenMod, not CyanogenOS. Unless there's some weird, first-time-in-history NDA regarding the HALs / overlay that ZTE provides for the development of CM, they will be open source. Click to expand... Click to collapse Don't count on anything "open" from ZTE. It really doesn't matter what they may say, the reality this phone doesn't have much more than the day it was released.
Araewuir said: Do we have any ETA on this ? I fear than the OP3 will get more love from the dev, and that the Axon 7 will be forgotten :/ Click to expand... Click to collapse The oneplus one still gets more dev support than the Nexus 6p. Oneplus devices get pretty much the best dev support period. That being said, more devs are starting to get the axon 7, but we're never going to be at the oneplus 3 level of support. The oneplus 3 is supported by SultanXDA, flar2, Franco, despair, and dozens more. It had official cm13 support as soon as it was released. It has official support from paranoid Android, elemental x, Franco kernel, PAC rom, dirty unicorns, and pretty much every other rom and kernel you've ever heard of. I love the Axon, but I don't it's ever going to get that kind of support.
jim262 said: Don't count on anything "open" from ZTE. It really doesn't matter what they may say, the reality this phone doesn't have much more than the day it was released. Click to expand... Click to collapse Okay. xxBrun0xx said: The oneplus one still gets more dev support than the Nexus 6p. Oneplus devices get pretty much the best dev support period. That being said, more devs are starting to get the axon 7, but we're never going to be at the oneplus 3 level of support. The oneplus 3 is supported by SultanXDA, flar2, Franco, despair, and dozens more. It had official cm13 support as soon as it was released. It has official support from paranoid Android, elemental x, Franco kernel, PAC rom, dirty unicorns, and pretty much every other rom and kernel you've ever heard of. I love the Axon, but I don't it's ever going to get that kind of support. Click to expand... Click to collapse I feel like the last phone I owned with that level of support was the Nexus 4.
rczrider said: Okay. I feel like the last phone I owned with that level of support was the Nexus 4. Click to expand... Click to collapse One Plus released everything before the phone even hit the market, so there was development for the One Plus 3 from the beginning. The Axon, in my opinion, is a very good device, but ZTE has limited development of this product. It is almost as though they are perfectly happy being an iPhone/Apple wannabe.
japzone said: From what I read from the Employees at ZTE Forums, ZTE currently doesn't want to deal with setting up a place for Devs to access the needed resources for things, so they're basically going to just dump it all on CyanogenMod for them to sort it out. It's easier for the ZTE higher-ups to swallow that way. Click to expand... Click to collapse Which is never a good thing. Especially when they admit they don't care. As a Sprint subscriber I'm locked out of the Axon7 until Sprint stop being dickbags about BYOD, which most likely will be never. If that changes, I'll probably buy an A7 if CM actually appears in a timely fashion since Shamu is being dropped by Google very shortly. ...but dumping code on the community and expecting them to make it right is massively annoying at best. It is exactly what Google does with AOSP....The Nougat AOSP is seriously broken and takes a ton of effort to fix enough just to get to compile. The stock AOSP GApps packages are all in varying stages of brokenness as of now. Sure they release the source, but what you get doesn't compile without a ton of forensic work. Nougat has been on Nexus for over a month (minus Shamu)...and it is not going well.