Database Info

KitKat?

When should we expect the release of KitKat for the Relay?

When TeamApexQ deems fit to release it.
Sent from my Amazon Kindle Fire2 using Tapatalk 4

Nardholio said:
When TeamApexQ deems fit to release it.
Sent from my Amazon Kindle Fire2 using Tapatalk 4
Click to expand...
Click to collapse
Nardholio, do you expect any major innovations, and most importantly, any major sources of bugs or instabilities with KitKat?
Thanks!!

Guiyoforward said:
Nardholio, do you expect any major innovations, and most importantly, any major sources of bugs or instabilities with KitKat?
Thanks!!
Click to expand...
Click to collapse
That's a question we won't really be able to answer until there is more solid information on KitKat generally available.

Looks like CM is setting up the KitKat AOSP code for there builds Check out @CyanogenMod's Tweet: https://twitter.com/CyanogenMod/status/396000889011326976
Sent from my SGH-T699 using Tapatalk
---------- Post added at 10:29 AM ---------- Previous post was at 10:23 AM ----------
Cyanogenmod Google+ post " Android 4.4 Source
Source is now being pushed to the AOSP trees. Of course, when it is all there we will begin the process of figuring out what changed, needs work, and/or is no longer feasible or needed.*
We are not in a rush to get 4.4 builds out. We are going to continue the process of working on CM 10.2 M1 - getting that out the door and onto your devices. Further, we will 'finish' the 10.2 code base, similar to what we did with 10.1.*
As a friendly reminder, please don't flood us with requests for 4.4 - we all want new and shiny things, but we will not do so at the expense of abandoning the hard work our contributors have put into 10.2.*
Final note, a lot of folks are reading into the "512mb" item on the release notes. No, this does not mean a sudden resurrection of older hardware, there are dependencies beyond the RAM (and CM has enforced that minimum since ICS)."
Sent from my SGH-T699 using Tapatalk

pst @Magamo this thread was best ended with a simple "when I say so" response and nothing more
Sent from my SGH-T699 using Tapatalk

Nardholio said:
pst @Magamo this thread was best ended with a simple "when I say so" response and nothing more
Sent from my SGH-T699 using Tapatalk
Click to expand...
Click to collapse
I actually was referring to an official KitKat OTA update from T-mobile.
How long did it take them to release a JB update after it was first introduced?
I have no interest in a CM ROM full of bugs and things that don't work.

andrewsfm said:
I actually was referring to an official KitKat OTA update from T-mobile.
How long did it take them to release a JB update after it was first introduced?
I have no interest in a CM ROM full of bugs and things that don't work.
Click to expand...
Click to collapse
Given that we never got upgraded to 4.2 or 4.3 by T-mobile/Samsung, I kinda doubt we'll be getting an official 4.4. And our CM rom, which has been built for us by a couple of people working for free, currently has fewer bugs than the official ROMs.

Jax184 said:
Given that we never got upgraded to 4.2 or 4.3 by T-mobile/Samsung, I kinda doubt we'll be getting an official 4.4. And our CM rom, which has been built for us by a couple of people working for free, currently has fewer bugs than the official ROMs.
Click to expand...
Click to collapse
4.2 and 4.3 were minor updates with no name change. JB was a major update and they did update to it.
4.4 KitKat being a major update, I've got my fingers crossed considering the wide range of devices that it's being planned for.
Was just hoping to see if there was any news on a KK update for this model.
CM is fun to play with and all, but it's not something I would trust on an everyday phone.

I use CM as a daily driver every day, and have been doing so since 10.2 became CyanogenMod official - everything just works. Now I'm not one of those people who demands a LOT of my phone, but I use it in the course of doing my job daily and it performs better, and more efficiently (with regards to battery consumption) than it did on the debloated stock rom, so much so that I deleted my Nandroid of that setup.
Sent from my SGH-T699 using the XDA-Developers app.

onebornoflight said:
I use CM as a daily driver every day, and have been doing so since 10.2 became CyanogenMod official - everything just works. Now I'm not one of those people who demands a LOT of my phone, but I use it in the course of doing my job daily and it performs better, and more efficiently (with regards to battery consumption) than it did on the debloated stock rom, so much so that I deleted my Nandroid of that setup.
Sent from my SGH-T699 using the XDA-Developers app.
Click to expand...
Click to collapse
I'm not sure if I fall into the category of demanding alot from my phone, but if there are issues like, Wifi and BT can't be on at the same time, that's not good enough. That's a serious issue. So if I forget to turn one of them off, stuff stops working? That's not okay...
I want my camera to work, for videos and photos. I want the phone to do everything the hardware is supposed to do.

andrewsfm said:
I'm not sure if I fall into the category of demanding alot from my phone, but if there are issues like, Wifi and BT can't be on at the same time, that's not good enough. That's a serious issue. So if I forget to turn one of them off, stuff stops working? That's not okay...
I want my camera to work, for videos and photos. I want the phone to do everything the hardware is supposed to do.
Click to expand...
Click to collapse
Awesome! And you want that for free? You don't seem to appreciate a lot the effort that other people are putting into this...

The wifi/bluetooth issue isn't that bad. It only falls apart when WiFi is on and connected to a 2.4GHz access point, and bluetooth is on and connected to a bluetooth device. If you have an N wifi access point that operates at 5Ghz, you can just connect to that instead of the 2.4Ghz node and then the two play nice. It's what I do.

Jax184 said:
The wifi/bluetooth issue isn't that bad. It only falls apart when WiFi is on and connected to a 2.4GHz access point, and bluetooth is on and connected to a bluetooth device. If you have an N wifi access point that operates at 5Ghz, you can just connect to that instead of the 2.4Ghz node and then the two play nice. It's what I do.
Click to expand...
Click to collapse
I would do this if I had a 5GHz AP, but what I'm saying is that I don't want to have to worry about stuff like that.
Guiyoforward said:
Awesome! And you want that for free? You don't seem to appreciate a lot the effort that other people are putting into this...
Click to expand...
Click to collapse
I don't want anything for free, except a stock KitKat update from T-Mobile/Samsung for the hardware I paid for... At no point did I say I was interested in CM. I've been explaining why I'm not, the whole time.
I started this thread to find out how long historically after the release of a new OS, does it usually take Samsung/T-Mobile to release an OTA?

andrewsfm said:
I would do this if I had a 5GHz AP, but what I'm saying is that I don't want to have to worry about stuff like that.
I don't want anything for free, except a stock KitKat update from T-Mobile/Samsung for the hardware I paid for... At no point did I say I was interested in CM. I've been explaining why I'm not, the whole time.
I started this thread to find out how long historically after the release of a new OS, does it usually take Samsung/T-Mobile to release an OTA?
Click to expand...
Click to collapse
Normally only after the Samsung high-end phones get the update and they are just barely getting Android 4.3. It also depends if they decide to update this phone at all. I have been asking t-mobile and Samsung that and they keep blaming each other or referring me to the forum for the phone on there websites.
Sent from my SGH-T699 using Tapatalk

chris122380 said:
Normally only after the Samsung high-end phones get the update and they are just barely getting Android 4.3. It also depends if they decide to update this phone at all. I have been asking t-mobile and Samsung that and they keep blaming each other or referring me to the forum for the phone on there websites.
Sent from my SGH-T699 using Tapatalk
Click to expand...
Click to collapse
I guess Windows has spoiled me, because I don't understand how it's so hard to port Android to each device.
AMD or Intel, they both use the same instruction set, so they work on any x86/x64 processor, and then you install drivers for your hardware peripherals.
Shouldn't Android run on any ARM processor, and then just have drivers that need to be plugged into it for each component of the phone to work?
Apparently it's a lot more complicated than that, but why...

andrewsfm said:
I guess Windows has spoiled me, because I don't understand how it's so hard to port Android to each device.
AMD or Intel, they both use the same instruction set, so they work on any x86/x64 processor, and then you install drivers for your hardware peripherals.
Shouldn't Android run on any ARM processor, and then just have drivers that need to be plugged into it for each component of the phone to work?
Apparently it's a lot more complicated than that, but why...
Click to expand...
Click to collapse
A lot of the complexity comes from the manufacturers of the SoCs not opening up the workings of their drivers to the wider world that makes porting to new devices, and to new versions of Android so difficult. Things work on one kernel, or one interface, and that's it, and we have no way of tweaking it to work in other ways. Back to the subject at hand. I personally suspect that the Relay will get no official update to KitKat. The Relay is over a year old, T-Mobile has been trying to dump it since 2013 began, and they are the only retailer. The 4.1.2 Jelly Bean updates were rolling out to the then mainline Samsung phones within a week of the Relay's release in September 2012, and we didn't get our update (which frankly is a broken PoS, ESPECIALLY when held up against any CM build for the Relay) until March or April of '13, so expect another 6 months before we MIGHT (and likely won't) get an official 4.3 update.

Looks like coding for CM 11 has started. Check out @CyanogenMod's Tweet: https://twitter.com/CyanogenMod/status/397817644650205185
Sent from my SGH-T699 using Tapatalk

Magamo said:
A lot of the complexity comes from the manufacturers of the SoCs not opening up the workings of their drivers to the wider world that makes porting to new devices, and to new versions of Android so difficult. Things work on one kernel, or one interface, and that's it, and we have no way of tweaking it to work in other ways. Back to the subject at hand. I personally suspect that the Relay will get no official update to KitKat. The Relay is over a year old, T-Mobile has been trying to dump it since 2013 began, and they are the only retailer. The 4.1.2 Jelly Bean updates were rolling out to the then mainline Samsung phones within a week of the Relay's release in September 2012, and we didn't get our update (which frankly is a broken PoS, ESPECIALLY when held up against any CM build for the Relay) until March or April of '13, so expect another 6 months before we MIGHT (and likely won't) get an official 4.3 update.
Click to expand...
Click to collapse
Ah k I see. The hardware vendors are mostly to blame it seems.
I may try a stable CM11 if that ever sees the light of day, but I won't hold my breath.
I've heard about the official JB ROM being problematic, so I plan to stay on ICS the phone originally shipped with.
I'm just glad to be getting rid of my Droid3 and Gingerbread.

andrewsfm said:
Ah k I see. The hardware vendors are mostly to blame it seems.
I may try a stable CM11 if that ever sees the light of day, but I won't hold my breath.
I've heard about the official JB ROM being problematic, so I plan to stay on ICS the phone originally shipped with.
I'm just glad to be getting rid of my Droid3 and Gingerbread.
Click to expand...
Click to collapse
True, there have been some bugs. However, I use the official nightly of cm10.2 as a daily driver. I'd rather put up with the MINOR issues that are left (hardware is stable for the most part) than have a manufacturer ROM. IMHO, the stock ROM that comes with the phone is usually full of crap bloat ware that I don't use and takes up space, and a UI that is SEVERELY limited in customization.
Also, the more people participate and report problems, the faster it takes TeamApex to fix and push out. At least team apex RESPONDS to their users. As mentioned before, it can take as long as 6-8 months after an android release for the manufacturer to roll out an update...still full of crap ware that's NOT used and cannot be uninstalled without root privileges or botching up the UI further.
These people who work tirelessly to provide to us, the end user, an updated version of Android, do so out of their own free will, and don't get a penny. These devs are here to proudly share what they have created, and I applaud and give my utmost respect to them.
You don't wanna install aftermarket firmware? Don't want to aid in bug reporting? Fine, put up with the crap that the manufacturer pushes onto you. Plus, Samsung & T-Mobile don't get any more of your hard earn dollars rolling out an Android update for our year-old device. They'd rather you dump it and buy the latest phone. THAT'S THEIR BUSINESS MODEL! So they have no interest in rushing an update to something as "old" as the Relay.
If you want JB or KK and are unwilling to wait for & install after-market firmware, I suggest you pony up the dough and buy a nexus 5. Better still, learn how to dev and make your own version of JB or KK for the Relay. That's the beauty of open source.
Your rant and *****ing about when "they are going to develop Kit Kat" makes you come across as arrogant, snobbish, and child-like.
Sorry for MY ranting, but it's unappreciative asshats like andre that just piss me off.
Sent from my SGH-T699 using XDA Premium 4 mobile app

Me venting about CM on the moto G

Wow. Just wow. I mean, this phone has got to be at least nine months old by now. And guess what - I haven't seen a stable build of CM11 yet. In fact, I haven't seen a build where audio even works as it should, and in the latest nightly, the audio derped out completely, even in calls. GPS doesn't work. WiFi drops every 5 minutes or so. Mobile data doesn't activate for about half an hour, even then it drops out every 5 minutes, just like the WiFi.
Cyanogenmod is beyond a joke. The Moto G runs stock android out of the box, so there is literally nothing for the CM team to modify to get CM to work on it. They should at least get audio and GPS working - in contrast there is an unstable, unofficial build for the Samsung Galaxy Ace "s5830" of CM11 that has more things working than the current "official", "stable" build on the Moto G.
I thought CM was meant to be about bringing Stock android to all devices, on Google's schedule, long after OEMs and carriers have dropped support for these devices. What's crazy here is that the Moto G's "stock" software has had a version of 4.4.4 available for months; Motorola have finished it, and carriers have got round to rolling it out - and it's been on my phone for several weeks now.
My point is, Motorola (who are very lazy when it comes to updates) have finished 4.4.4, given the update to carriers, who then procrastinated about rolling it out for weeks before finally rolling it out, and still, despite all this, Cyanogenmod haven't even got a stable build of kitkat at all, let alone 4.4.4, to offer. They are literally worse than OEMs and carriers at updating their phones on time.
If you have a Moto G, please do not ruin it by installing cyanogenmod on it. It is useless beyond belief, and you will cry for days about having turned your phone into an expensive paperweight. On the bright side, if that corner of your piece of paper just won't stick down, go ahead and install CM.

Is this is a complain or something like that lol? BTW I don't have any issues with CM or CM based ROMs.

Here we go. At this point, I am also waiting for a more stable version of CM 11 for Falcon. Yes, there are issues with it. Some are pretty notable, others are barely (or not at all) notable.
The thing here is that you are using open sourced software. There are some really, really experienced developers working on CM 11 to make it better for us, the end users. However, and I have seen this happen before, some lesser-experienced developers might forget about something every once in a while causing issues on the devices. This can happen. It happens to everyone, Motorola developers included (just look at the reports of battery drain issues across the Android versions).
CyanogenMod is a great team and are introducing features that improve Android in small, yet very useful ways. These features, in themselves, are working brilliantly. The only quirk with this is that CyanogenMod is trying to get each and every different phone to run Android in combination with those features. I might be wrong here, but that seems like that's causing a lot of trouble over some different devices, including the Moto G. If CyanogenMod adds a new feature to (for recent issues' sake) audio for devices CyanogenMod support (an update library for example), there's always a chance that gets pushed to the Moto G, and there's something with the Moto G that makes it not function properly. This is really notable in the Nightly releases. The most recent Nightly releases, 07-24 and 07-25 contain an issue that makes it so that audio isn't functioning properly. This is always a possibility. It's a Nightly, unstable, release. You cannot complain that it's not working on a version that's not intended to be stable.
This brings me to another point, the "Stable" release category. Moto G's most recent "Stable" release, M6, is really pretty stable. On everyday use, I could not see any one issue with it. The reason for there not being a M7 or M8 "Stable" release, is that there's issues with them, so CyanogenMod decided that it shouldn't be classed "Stable" for our device and therefor did not release them. I'm sure that, when there's a new safe-to-be-called-Stable release, CyanogenMod will push that to our device as well.
CyanogenMod is open source. There are bugs in it. You sign up for that in exchange for some new features and continued support from the developers. For the most part, the core software is stable. It's the "drivers" for the phone that are causing issues. Also, the new features have to be tested and the bugs that are in them should get reported to CyanogenMod so that the team can fix them. If you don't report the bugs, how would they get squashed? I have reported the audio issue on the most recent Nightly releases to CyanogenMod, which brings it to their attention and, while it is being fixed, the Nightly releases are temporarily postponed until the issue is fixed to prevent any further harm that this issue might cause. That is what CyanogenMod is about. They release something, obtain feedback, fix it, release that fix, obtain feedback, fix it and release that fix. That cycle keeps continuing. If they don't obtain feedback, they will just keep doing what they are doing -- add new features, which might cause the bugs you found to keep being there forever and ever.
And you may say that trying to report stuff in Nightly releases isn't 'allowed' on their feedback site, you're looking in the wrong place. You should look in the Nightly Regressions section of the CyanogenMod JIRA -- not the regular Issues section.
If you have any comment on what I just stated, please do reply to me. If there's anything that's wrong with what I just stated, please do correct me. If you dislike anything about what I just stated, please do not just post a hate comment on it -- actually explain what you don't like and why so I can, in turn, respond to that as well.
Thanks for reading.

I've never had problems with CM11 i'm using xt1032 btw

Whoooa... sorry guys didn't mean to offend anyone just wanted to vent.
My point is if some 12 year old can get audio working on some ****ty outdated low end samsung device with no sources (eg the s5830i), whoever is in charge of the Moto G (a modern, officially supported device btw) should be able to AT LEAST MAKE THE DAMN AUDIO FECKING WORK.
IMHO custom ROMs are dead and xposed is the future.

I've just heard they've stopped development for the Moto G entirely. Motorola and the various carriers their phones are on have got their act together and released 4.4.4, CM haven't finished... ...anything.

moto_g_n00b said:
Whoooa... sorry guys didn't mean to offend anyone just wanted to vent.
My point is if some 12 year old can get audio working on some ****ty outdated low end samsung device with no sources (eg the s5830i), whoever is in charge of the Moto G (a modern, officially supported device btw) should be able to AT LEAST MAKE THE DAMN AUDIO FECKING WORK.
IMHO custom ROMs are dead and xposed is the future.
Click to expand...
Click to collapse
Whoa… No need to swear. I'm not flaming on you. I even partially agree with you. I just provided you with what I think about the matter, and nothing negative about any of what you commented. There's absolutely no need to go crazy about what a few members comment on your post.
Have a great day, sir, and lighten up a bit.

Is official CM12S still coming in Jan / Feb ?

A Few months ago, OPO and Cyanogen, said 90 days after the official Lollipop release from Google, the OnePlus One OS would get the big Lollipop date. So that puts it end of Jan / early Feb. But is that still on track of happening ?
But...with the all the news lately of Cyanogen and OPO not getting along, and the whole India deal, etc...
What will OPO official release as far as the Lollipop update ? Will there still be a CM12S made specific for the OnePlus by Cyanogen ? Or will OPO just release their in house Lollipop ROM they made themselves without CM ?

The last I read, there is a big update coming in January, which would presumably be CM12S Lollipop. OnePlus also has announced that they are on the verge of releasing their own, house built ROM, so it's possible that is also coming in that time frame.
Sent from my iPad using Tapatalk

There's not much point in asking that here, nobody here can answer the question properly. Plus, even if CM were reading here, they don't respond to requests for ETA's.
Transmitted via Bacon

timmaaa said:
There's not much point in asking that here, nobody here can answer the question properly. Plus, even if CM were reading here, they don't respond to requests for ETA's.
Transmitted via Bacon
Click to expand...
Click to collapse
Not really asking for an ETA. I know they both said 90 days after Lollipop code release.
But my question is more about if it will even come at all now ? Due to the rocky relationship between OPO + Cyanogen.
Sent from my A0001

Zorachus said:
Not really asking for an ETA. I know they both said 90 days after Lollipop code release.
But my question is more about if it will even come at all now ? Due to the rocky relationship between OPO + Cyanogen.
Sent from my A0001
Click to expand...
Click to collapse
Yeah but unfortunately the answer remains the same; nobody here knows, we can only speculate. The only people who know are CM, and they won't comment on it. There's the "big" update coming in January but I'm not putting any money on it being 5.0, they haven't even hinted to that.

As with everything when it comes to ROMs/Kernels/OTAs... no one knows and employees don't release release dates because then they'll feel pressured that they'll NEED to have it done.
Would you rather have a rushed release with bugs causing your phone not to work properly? Especially if its a person who does not involve themselves with rooting/flashing?
Or would you rather have a release where it works and is tested thoroughly.
If you can't wait, try a Lollipop ROM. If you want to stay as close to stock as possible, flash CM12.

I am not asking for a specific CM12S release date.
This thread is more about asking if there will even be a CM12S released period, ever ? With all the recent bad press between OPO and Cyanogen. I am worried there might not ever be an official OnePlus One CM12S OS release at all now in a couple months ?
Sent from my A0001

And the answer is still (and always will be) nobody here can answer that.
Transmitted via Bacon

Zorachus said:
I am not asking for a specific CM12S release date.
This thread is more about asking if there will even be a CM12S released period, ever ? With all the recent bad press between OPO and Cyanogen. I am worried there might not ever be an official OnePlus One CM12S OS release at all now in a couple months ?
Sent from my A0001
Click to expand...
Click to collapse
That is specific to the market of India. I'm sure that oneplus and cyanogen have a contract that they need to abide by otherwise therell be lawsuits.
I wouldn't worry about it, I'm sure there will be a cm12s. When? Don't know.
If you can't wait, flash cm12 unofficial. Now if we talk about the oneplus two (or whatever they plan on calling it, I wouldn't be surprised if they did abandon CyanogenMod in favor of their own rom.)
Sent from my Nexus 6 using Tapatalk

zephiK said:
That is specific to the market of India. I'm sure that oneplus and cyanogen have a contract that they need to abide by otherwise therell be lawsuits.
I wouldn't worry about it, I'm sure there will be a cm12s. When? Don't know.
If you can't wait, flash cm12 unofficial. Now if we talk about the oneplus two (or whatever they plan on calling it, I wouldn't be surprised if they did abandon CyanogenMod in favor of their own rom.)
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
For the OnePlus One, you're darn right there will be lawsuits if we don't keep getting CM branded official updates. That was what the phone was marketed as, printed with Cyanogen branding, and I as a customer bought it for. If they abandon CM branded official upgrades, I'd be forced to kick off or join a class action lawsuit against both OnePlus and Cyanogen. I won't tolerate bait and switch.

maybe in february

They are suppose to deliver CM12s in Jan(this month) ..at least at the very end, it's the 90 days they promised us. Feb is too late as it won't be 90 days but more
Don't promise if you can't deliver, also I'd like a pure android experience as a second option, something as pure as it can get(it performs better on benches ..at least their alpha version from what I've seen)

evronetwork said:
They are suppose to deliver CM12s in Jan(this month) ..at least at the very end, it's the 90 days they promised us. Feb is too late as it won't be 90 days but more
Don't promise if you can't deliver, also I'd like a pure android experience as a second option, something as pure as it can get(it performs better on benches ..at least their alpha version from what I've seen)
Click to expand...
Click to collapse
Steve Kondik has said it will be out later next month. Check his Google+ profile. Sorry I can not post a link.

freelancer1988 said:
Steve Kondik has said it will be out later next month. Check his Google+ profile. Sorry I can not post a link.
Click to expand...
Click to collapse
I believe this is the link:
https://plus.google.com/app/basic/stream/z13evbgalmvfdffve220xb2reqilvvbw504

evronetwork said:
Don't promise if you can't deliver, also I'd like a pure android experience as a second option, something as pure as it can get(it performs better on benches ..at least their alpha version from what I've seen)
Click to expand...
Click to collapse
You people and your benchmark scores. Give it up already
Sent from my A0001 using XDA Free mobile app

Mr Patchy Patch said:
You people and your benchmark scores. Give it up already
Sent from my A0001 using XDA Free mobile app
Click to expand...
Click to collapse
I just made a pointless fact(from other people's tests) about that no need to act like that, be polite man ..you should try it next time.
I really don't care about benches, I prefer if it feels smooth-liquid, runs fast and not with 20fps at games and have 1000 points on antutu rather than having a sci-fi 80.000 points and be garbage

Just interested in
Guys can someone describe me difference shortly of CM11 and CM1s. Coz I'm on CM12 Nightly builds on my OPO atm and it's working fairly good.

Qwsazy said:
Guys can someone describe me difference shortly of CM11 and CM1s. Coz I'm on CM12 Nightly builds on my OPO atm and it's working fairly good.
Click to expand...
Click to collapse
There's very little difference except CM11S has the fancy lockscreen and camera. CM11 receives nightly updates whereas CM11S received periodic updates.
Transmitted via Bacon

Yeah it confuses me why people still beg for the same product with an S attached to it as it will make things better for them. This phone is a developer type of phone for people who will try rooting and flashing. With the recent updates in CM getting closer to stable why do we care about an 11s.
Also lets be honest if we do not have all the proper working features in a nightly you cant expect to see a stable release.... At least a 12M or something has to be put out for our phones too me before we say an 12S
@Zorachus - step back and think for a second why are you asking your question. No one associated with giving you an answer will come here and give it to you. You can Google it and see whats out there and draw your own conclusion. I feel this is what others were trying to get across to you. You are asking a question that can't be answered no matter how you slice it up

playya said:
Yeah it confuses me why people still beg for the same product with an S attached to it as it will make things better for them. This phone is a developer type of phone for people who will try rooting and flashing. With the recent updates in CM getting closer to stable why do we care about an 11s.
Also lets be honest if we do not have all the proper working features in a nightly you cant expect to see a stable release.... At least a 12M or something has to be put out for our phones too me before we say an 12S
Click to expand...
Click to collapse
Because for some people it's a matter of principle. CM stated very clearly that this device would receive official updates for two years, if the S branch is dropped they're reneging on that agreement.
Because this isn't strictly a dev phone, this is a developer-friendly phone. Not everyone wants to unlock and root their device, in fact the majority of the user base most likely don't want to. So if support is dropped then those people are left with a device that isn't receiving the updates it was promised to have, those people have a right to expect those updates.
Transmitted via Bacon

Release the source code!!!!

so this last week i recieved my Huawei Ascend Mate 7 MT7-L09 and a 128GB microSD card. i have to admit that after a few minutes i was a bit disappointed....... not with the hardware but with the software. i waited 2 days and installed CM11 (thanks Demazda!!). after installing CM11 i fell in love!!!! that same day i reset and updated my nexus 5 with the lasted PAC-ROM and gave it to my dad. this phone does everything i could want it to.
the only drawback that i have is that there are many functions not available due to the lack of a kernel source. without it our devices will not be able to host the many great custom roms such as CM12, PAC-ROM, Paranoid Android, KANG, OMNI, and many, many others. google has made it clear that in order to use android, manufacturers must release their kernel source to the public.
given that, i think that we should make our voices heard! im sure that a few hundred letters and emails would make our voices heard. if Huawei wants to gain a foot hold in the US, then it must start listening to its customers. i really want to soon see complete roms for our mate7. is anyone willing to join me??

droidbot1337 said:
so this last week i recieved my Huawei Ascend Mate 7 MT7-L09 and a 128GB microSD card. i have to admit that after a few minutes i was a bit disappointed....... not with the hardware but with the software. i waited 2 days and installed CM11 (thanks Demazda!!). after installing CM11 i fell in love!!!! that same day i reset and updated my nexus 5 with the lasted PAC-ROM and gave it to my dad. this phone does everything i could want it to.
the only drawback that i have is that there are many functions not available due to the lack of a kernel source. without it our devices will not be able to host the many great custom roms such as CM12, PAC-ROM, Paranoid Android, KANG, OMNI, and many, many others. google has made it clear that in order to use android, manufacturers must release their kernel source to the public.
given that, i think that we should make our voices heard! im sure that a few hundred letters and emails would make our voices heard. if Huawei wants to gain a foot hold in the US, then it must start listening to its customers. i really want to soon see complete roms for our mate7. is anyone willing to join me??
Click to expand...
Click to collapse
Here...this is what you are looking for?
Mate7 SourceCode
Open source code
Version: Mate7,kernel.tar[This version is only for android developers,please do not download for other usage
MD5: 0F3AAFD9B7B136993DF3C29D9D31C43A
Size: 215.79MB
http://en.ui.vmall.com/plugin.php?id=hwdownload&mod=detail&mid=74

I am totally down for getting something going to get the source. I would love a fully functioning CyanogenMod ROM. So... how hould we start this?

CCDillon said:
I am totally down for getting something going to get the source. I would love a fully functioning CyanogenMod ROM. So... how hould we start this?
Click to expand...
Click to collapse
Hey, thanks for the interest. It seems that there are only two of us interested i guess. Let's see if we can get some more people interested.

What is going on with LineageOS? Is it dying?

So all of a sudden just a little while back the phone I had at the time just suddenly was, without warning, abandoned by LineageOS and all ROM downloads removed. So I started using a third party ROM with mostly minimal issues (but there's definitely a difference between official support and not it seems.) Then when I broke that phone I started looking into other possibilities and I started to notice: a shocking number of devices have been dropped. Many are even fairly standard well supported devices (like Nexus devices!) And more and more now I find more and more devices listed as no longer supported with no ROMs available. I ultimately did finally find a suitable phone for my needs that was still officially supported, but it's getting harder and harder to find anything whenever I search for a new device for a friend to find something with official support. Plenty of devices have various unofficial ROMs out there with varying degrees of issues, but the list of devices with official support and official builds available seems to be shrinking almost daily. I tried to look at possibilities for a certain sort of tablet for someone and found that there are virtually no tablets even left in the list anymore even.
Is LineageOS dying or what? What is going on with it all of a sudden lately? It seems a real shame to see LineageOS devolve into just an unofficial collection of unofficial ROMs from random people on the Internet who are just putting in a bit of their spare time and often enough not even able to really test it out well, yet it really feels like that's what is happening to me. After whatever happened with CyanogenMod I am, I believe, justified in being a bit worried.
BTW, is there any sort of alternative for something relatively clean with official support for a lot of devices? Maybe some sort of official AOSP porting project or something?

Nazo said:
So all of a sudden just a little while back the phone I had at the time just suddenly was, without warning, abandoned by LineageOS and all ROM downloads removed. So I started using a third party ROM with mostly minimal issues (but there's definitely a difference between official support and not it seems.) Then when I broke that phone I started looking into other possibilities and I started to notice: a shocking number of devices have been dropped. Many are even fairly standard well supported devices (like Nexus devices!) And more and more now I find more and more devices listed as no longer supported with no ROMs available. I ultimately did finally find a suitable phone for my needs that was still officially supported, but it's getting harder and harder to find anything whenever I search for a new device for a friend to find something with official support. Plenty of devices have various unofficial ROMs out there with varying degrees of issues, but the list of devices with official support and official builds available seems to be shrinking almost daily. I tried to look at possibilities for a certain sort of tablet for someone and found that there are virtually no tablets even left in the list anymore even.
Is LineageOS dying or what? What is going on with it all of a sudden lately? It seems a real shame to see LineageOS devolve into just an unofficial collection of unofficial ROMs from random people on the Internet who are just putting in a bit of their spare time and often enough not even able to really test it out well, yet it really feels like that's what is happening to me. After whatever happened with CyanogenMod I am, I believe, justified in being a bit worried.
BTW, is there any sort of alternative for something relatively clean with official support for a lot of devices? Maybe some sort of official AOSP porting project or something?
Click to expand...
Click to collapse
The reduction in development is probably partly due to lack of manpower on the official LineageOS team and fewer developers owning certain devices(if there are no developers that own the device, that device doesn't receive any development). It is also partly due to devices becoming more and more secure, this leads to fewer people creating development and fewer devices that are capable of being customized.
It isn't just devices being dropped from development, the size of the XDA community and amount of overall activity on this whole website is also declining.
Sent from my SM-S767VL using Tapatalk