Related
So CM10.1 recently got an update to the m1 snapshot and I was wondering what's a milestone snapshot? Never knew what it is and how is it different from stable?
danshuynh said:
So CM10.1 recently got an update to the m1 snapshot and I was wondering what's a milestone snapshot? Never knew what it is and how is it different from stable?
Click to expand...
Click to collapse
Cyanogenmod said:
Something we have learned over the past few months is that if you don’t release, someone else will do it for you. Since we are open-source, we absolutely encourage it! Unfortunately, the quality of unofficial builds can vary, and we are serious about quality. Of course nightlies are always available, but we realized that having something that is a bit more stable on a more frequent basis is important. Starting now, we are rolling out our M-Series releases. M-Series builds will be done at the beginning of every month. We did a soft freeze of the codebase for the last week, blocking new features in order to stabilize. Our plan is to continue this (assuming that the response is good) up until stable release, and onward.
We aren’t exactly sure what M stands for. “Monthly”, “milestone”, or perhaps “MINE ALL MINE!”. Whatever it is, I hope that we are meeting the needs of community.
M-Series builds will be available under the EXPERIMENTAL tag. The filename will include the date stamp as well as the M version. These builds should be stable enough for daily use, and we encourage feedback and bug reports.
Click to expand...
Click to collapse
http://www.cyanogenmod.org/blog/cyanogenmod-10-m1
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
So, yeah I'm a bit on the fence with this one. I have an N5 and I love the notion that it's pretty much the first device to receive updates. But, more often as of late, Google pushes updates via its services and even more recently by making its apps available to all, at least to devices running 4.4.x. So, the importance of being able to run with the very latest Android version has been somewhat mitigated.
The thing that has me concerned right now about the One+ 1 are the very long update cycles of CM. Should Android 5.0 roll out within the next few months, it would mean, based on CM update history, an additional 6 months before CM moves on to it the latest Android version nightlies roundup. 6 months is often longer than it takes even the big manufacturers to skin and update the latest Android version, waiting periods which proud Nexus owners have been able to avoid.
Just curious to hear from Nexus people who are thinking about this device and what any inevitable updates might mean to you?
Well I think official updates are irrelevant as developers here will release their ROMs with line to the latest Google releases for the device.....I will just be buying One for Hardware.......
In an interview of Kondik, he said that now that they're a company and this is their product, they have actual paid devs working on the updates, which should make their code more higher quality and updates faster (though now that they have to make it stable means that it will slow updates down, I hope there will be a nightly channel)
mannu_in said:
Well I think official updates are irrelevant as developers here will release their ROMs with line to the latest Google releases for the device.....I will just be buying One for Hardware.......
Click to expand...
Click to collapse
Don't bet on that. Look at how poorly the community CM builds (i'm talking official nightlies, those are "community" builds from the point of view of Cyngn) for the Oppo N1 are. It's Cyngn's official position that they don't care at all if the community builds are completely broken and that users should have no expectations whatsoever from them.
Use nightline updates and you'll be happy :laugh: it helps a lot to devs make CM better and better
From the official point of view CM have said in a previous interview that we should expect 4 months on a major android version upgrade in CM11S.
I think that's pretty decent, anyone in need of a faster update schedule should jump on the nightly train, or find another rom
MrAndroid-HD said:
From the official point of view CM have said in a previous interview that we should expect 4 months on a major android version upgrade in CM11S.
I think that's pretty decent, anyone in need of a faster update schedule should jump on the nightly train, or find another rom
Click to expand...
Click to collapse
Right, but in terms of waiting times, I was referring even to the nightlies cycle. After a new Android release version, it usually takes months before they start to work on it. The stable releases, even the monthly ones, would take even longer. Correct me I'm wrong, but those hoping to jump on the nightlies cycle after the next version might be in for a rude awakening. But, in terms of stability for the nightlies, I have no doubt, they could be used as daily drivers, that is, if they open up nightlies to the general public.
floepie said:
Right, but in terms of waiting times, I was referring even to the nightlies cycle. After a new Android release version, it usually takes months before they start to work on it. The stable releases, even the monthly ones, would take even longer. Correct me I'm wrong, but those hoping to jump on the nightlies cycle after the next version might be in for a rude awakening. But, in terms of stability for the nightlies, I have no doubt, they could be used as daily drivers, that is, if they open up nightlies to the general public.
Click to expand...
Click to collapse
Remmember this is a special verison of CM, there is nothing like it used to that you can rely on. I know how things where in the past, but this is really one of their first projects where they are the main system on the phone from start - I know they where on the Oppo N1 also from the beginnign, but as far as I know, there weren't made a set deal like with the OnePlus..
Here OnePlus have a 2 year contract on a special version of CM.. Only time will tell us how much it differs from their normal releases..
As said before, the Cyanogen transition from a hobby to a company might give a huge benefit here.
It's true that the waiting time between stable releases has historically been quite poor, but I have extremely good experiences with CM nightlies. I'm running nightlies on my Galaxy Nexus and Nexus 7, and I can't really complain about anything. Hopefully we'll have an easy opt-in to the nightlies (like there is currently) and that the first nightlies get pushed out fast as Android is updated.
Also, we'll always have community builds.
Honestly, as long as they open source whatever code they use for the screen-off wake gestures, I don't care what I run on the device. As previously mentioned by others, I'm buying the hardware, not the software.
LiquidSolstice said:
Honestly, as long as they open source whatever code they use for the screen-off wake gestures, I don't care what I run on the device. As previously mentioned by others, I'm buying the hardware, not the software.
Click to expand...
Click to collapse
That's done via touchscreen controller firmware - which isn't itself opensource (it's just a blob encoded into a header file within the kernel), but will work no matter what you're running on the device with a only a few tweaks to the frameworks/kernel. Plenty of projects have experience with these tweaks since the Oppo N1 had the same capability.
floepie said:
So, yeah I'm a bit on the fence with this one. I have an N5 and I love the notion that it's pretty much the first device to receive updates. But, more often as of late, Google pushes updates via its services and even more recently by making its apps available to all, at least to devices running 4.4.x. So, the importance of being able to run with the very latest Android version has been somewhat mitigated.
The thing that has me concerned right now about the One+ 1 are the very long update cycles of CM. Should Android 5.0 roll out within the next few months, it would mean, based on CM update history, an additional 6 months before CM moves on to it the latest Android version nightlies roundup. 6 months is often longer than it takes even the big manufacturers to skin and update the latest Android version, waiting periods which proud Nexus owners have been able to avoid.
Just curious to hear from Nexus people who are thinking about this device and what any inevitable updates might mean to you?
Click to expand...
Click to collapse
Keep in mind they were just an independent developers they were getting some random people WHO ACTUALLY WANTED to help maintain some devices even while there wasn't any driver or source code avaliable (Samsung) which is really hard. They didn't had any office and they weren't getting paid for that. Now they have access to all tools from Google and other manufacturers such as Qualcomm and other drivers which gives them much more possibilities like LG, Samsung or Sony already had from the beginning. CyanogenMod 11S will be much more stable and easier for deliever.
maxver0 said:
Keep in mind they were just an independent developers they were getting some random people WHO ACTUALLY WANTED to help maintain some devices even while there wasn't any driver or source code avaliable (Samsung) which is really hard. They didn't had any office and they weren't getting paid for that. Now they have access to all tools from Google and other manufacturers such as Qualcomm and other drivers which gives them much more possibilities like LG, Samsung or Sony already had from the beginning. CyanogenMod 11S will be much more stable and easier for deliever.
Click to expand...
Click to collapse
Except that they've already had one official partner device (Oppo N1) where the user experience was actually WORSE for most people than many of the community-supported devices.
Entropy512 said:
Except that they've already had one official partner device (Oppo N1) where the user experience was actually WORSE for most people than many of the community-supported devices.
Click to expand...
Click to collapse
I don't know users experiences about Oppo N1 but I do know that CyanogenMod didn't get as many tools from Oppo as they do have now from Oneplus and their hardware partners. Abhisek Devkota from CyanogenMod have been talking about it somewhere on Google plus. I'm not going to sit on cyanogenmod anyway most likely, especially when there will be support from Slimkat and francisco. Reminder: Oneplus One will be fully unlocked and sources will be avaliable for everyone.
If anyone thinks CM is slow I had 4.4 on my tf700 within one month. Nightlies of course.
maxver0 said:
I don't know users experiences about Oppo N1 but I do know that CyanogenMod didn't get as many tools from Oppo as they do have now from Oneplus and their hardware partners. Abhisek Devkota from CyanogenMod have been talking about it somewhere on Google plus. I'm not going to sit on cyanogenmod anyway most likely, especially when there will be support from Slimkat and francisco. Reminder: Oneplus One will be fully unlocked and sources will be avaliable for everyone.
Click to expand...
Click to collapse
That's bull****. The only thing they can blame Oppo on is the initial O-Click fiasco - nothing beyond that. (And I'm letting them slide for the O-Click mess, that really wasn't their fault)
Any failures beyond that have nothing to do with Oppo and everything to do with Cyngn. If you look at oppoforums, the Oppo section of the CM G+ community, and CM's own forums, they're full of users saying they're switching to Omni... Which happens to be maintained by people who got the N1 1-2 months later than Cyngn, aren't paid to work on the device, and didn't have anywhere close to the level of access to Oppo engineers and documentation (Cyngn signed an NDA for Qualcomm docs, we didn't).
So if users are reporting all over that they're switching to a project which had LESS of everything that Cyngn said they didn't have enough of - don't you think something is wrong there?
dracinn said:
If anyone thinks CM is slow I had 4.4 on my tf700 within one month. Nightlies of course.
Click to expand...
Click to collapse
We're not talking about nightlies here, since there's no guarantee for users that they'll be anything but crap. Cyngn is ADAMANT about this position. If community builds (nightlies) for a Cyngn device are broken, you're SOL.
Entropy512 said:
Any failures beyond that have nothing to do with Oppo and everything to do with Cyngn. If you look at oppoforums, the Oppo section of the CM G+ community, and CM's own forums, they're full of users saying they're switching to Omni... Which happens to be maintained by people who got the N1 1-2 months later than Cyngn, aren't paid to work on the device, and didn't have anywhere close to the level of access to Oppo engineers and documentation (Cyngn signed an NDA for Qualcomm docs, we didn't).
So if users are reporting all over that they're switching to a project which had LESS of everything that Cyngn said they didn't have enough of - don't you think something is wrong there?
Click to expand...
Click to collapse
Well that someone prefer more one rom than the other doesn't prove anything. I prefer custom rom Slimkat on my Nexus 4 even if stock is super stable or even a cyanogenmod rom on my phone. I tried OmniRom on my N4 tho but I couldn't find multiwindow at all in rom so I flashed over something else...
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.
Does anyone think that android 5.0 will come to our phones? or are Google Motorola and Verizon going to be an ass and say no. I'm willing to help any development.
We're not going to get official support for 5.0 if that's what you mean. As for custom ROMs, I'm sure it will happen eventually.
Once Android 5.0 L is officially released, we intend to bring this latest upgrade to many of our other Motorola devices, as well. This includes Moto X (1st and 2nd Gen), Moto G (1st and 2nd Gen), Moto G with 4G LTE, Moto E, Droid Ultra, Droid Maxx and Droid Mini. We're still working out the details on timing and the upgrade depends on our partners' support so stay tuned to our software upgrades page for the latest and greatest.
Click to expand...
Click to collapse
http://www.motorola-blog.blogspot.hu/2014/10/nexus-6-from-google-and-motorola-more.html
...and it begins...Took less than a day for someone to ask. It's not even released yet. Coming to the Razrs? Not a snowball's chance in hell. Unofficial, maybe? These things are at EOL and they received a barely functioning official KK update.
Sent from my HTC6525LVW using Tapatalk
Moto kind of hinted at the possibility of having other devices on Lollipop, but I'm not holding my breath this time.
derpyherp said:
Does anyone think that android 5.0 will come to our phones? or are Google Motorola and Verizon going to be an ass and say no. I'm willing to help any development.
Click to expand...
Click to collapse
We're not even going to get KK 4.4.4 officially. The only way we have that is via custom ROMs like CM11.
Those of us in the soak test were told that this latest OTA (.15 release) was the FINAL release for this phone. No more updates. That came straight from a Motorola person in the private soak test forums.
So, don't hold your breath for an "official" Lollipop release. As others have stated, you might see it via Cyanogen or some other custom ROMs, but that will only be for those who have unlocked bootloaders. Those who have already upgraded to the latest OTA without unlocking are screwed forever.
Besides, CM11 for this phone has just recently become completely stable. L isn't even out yet.
here's is how its going to go down.
L comes out nov 3.
cyanoagen inc /PA will merge the code to their repos; take about a month before the first nightly comes out. cm11 is EOL as they move to Lollipop.
gummy slim and others will take the cm base and fork to get their ROMs running too.
then dhacker epinter etc. our great maintainers will port to our devices; first nightly will be for the very brave.
about 2-3 months of bug fixes until it becomes usable.
give or take by feb we have a daily driver of android L
question is with the f* ups of jjbl and kkbl which kernel will be supported to L, i'm sure cm will use a custom kernel just like it did with cm11 before the moto kk ota.
paranoid android to make l for msm8960 unified
just saw a reply from cj360 he will be working on l for msm8960 devices jbbl and kkbl. he said dont hold your breath ait will take a while
Gr8 stuff so far!
I'm enjoying my recently renewed phone anyways!
Btw, this L inspired Nova Pro customizable theme rocks and ART runtime is superb!
Sent from my Razr HD, Unlocked KKBL, latest CyanogenMod CM11 KK 4.4.4 ROM, ART runtime.
Yeah, it's actually available right now.
Check dhacker29's twitter, he has links up.
Flashing soon
the build
cartpig said:
Yeah, it's actually available right now.
Check dhacker29's twitter, he has links up.
Flashing soon
Click to expand...
Click to collapse
I flashed the build from the 14th i have no issues besides the power menu and lack of options, it doesnt have root DO NOT get the one from the play store get supersu 2.1.6 flash recovery. if you get anyother it will soft brick or cause fc issues. The wifi activity arrows are out of line. I will provide the zip. Its smooth no battery life issues its absoultley flawless..
GOOD JOB dhacker29 WE ALL OWE YOU SO MUCH FOR DOING THIS!!!
derpyherp said:
I flashed the build from the 14th i have no issues besides the power menu and lack of options, it doesnt have root DO NOT get the one from the play store get supersu 2.1.6 flash recovery. if you get anyother it will soft brick or cause fc issues. The wifi activity arrows are out of line. I will provide the zip. Its smooth no battery life issues its absoultley flawless..
GOOD JOB dhacker29 WE ALL OWE YOU SO MUCH FOR DOING THIS!!!
Click to expand...
Click to collapse
No, it has issues. Blue-tooth is wonky and Netflix and Google Play Movies won't work (you can't watch anything).
DHacker told me via Twitter that it's due to the DRM libraries. He hasn't figured out the right combination yet to get it working,
But, other than that, it works well.
11/16 has the battery percentage in the notification icon.
11/17 apparently has radio issues. Some people have reported that it works for 5 minutes and then the radio dies. A reboot fixes it for about 5 minutes, and then it dies again. Might want to stay away. I'm going to test it, and if I see the same issues, I'll go back to 11/16.
On the 11/16 build, here's what happens on my xt926M:
Phone > Recents > View full call history (bottom of screen) > Dialer fc's.
Haven't upgraded to the 11/17 build yet, as I don't want to run into any radio issues that I'm reading about here.
Not_A_Dev said:
On the 11/16 build, here's what happens on my xt926M:
Phone > Recents > View full call history (bottom of screen) > Dialer fc's.
Haven't upgraded to the 11/17 build yet, as I don't want to run into any radio issues that I'm reading about here.
Click to expand...
Click to collapse
There's a thread in the dev section that's already dedicated to reporting performance, bugs, etc on the new LP builds....
Sent from my ATRIX HD using XDA Free mobile app
palmbeach05 said:
There's a thread in the dev section that's already dedicated to reporting performance, bugs, etc on the new LP builds....
Click to expand...
Click to collapse
Thanks. Just posted my impressions of running the 11/16 build on that thread.
So here's a question (and I'm being serious when I ask, not trying to be snotty):
What about L is everyone so looking forward to that you all need it so bad? Xposed doesn't work on it, and if you're running a custom ROM you're already more than likely modified beyond anything that "Android L" is going to give you...
Other than "material design" and "ART" (along with being near impossible to root without an unlocked bootloader) I haven't even read up on what is so special about L that everyone is creaming their pants over it. Please someone enlighten me to the goodness of L other than "it's Google's lastest software".
EDIT: An acceptable answer would be to get off of the botched up KK Moto gave us... twice... Thus why I am sporting DU now - never going back.
LifeAsADroid said:
So here's a question (and I'm being serious when I ask, not trying to be snotty):
What about L is everyone so looking forward to that you all need it so bad?
Click to expand...
Click to collapse
For me - in short - battery life. If Android 5.0 hadn't come along soon, I would have downgraded to JB any day now, because that was the perfect OS for my XT926M. For me, KK just does not run right on this device. Why LP? The promise of "Project Volta" and whatnot. Of course, running a pretty much pre-alpha early version of CM 12, battery life is actually worse than it was on KK. I'll chalk it up to the fact that LP still needs development for this device, in hopes of having good battery life, hopefully by next February. Material Design is also pretty to look at.
Not_A_Dev said:
For me - in short - battery life. If Android 5.0 hadn't come along soon, I would have downgraded to JB any day now, because that was the perfect OS for my XT926M. For me, KK just does not run right on this device. Why LP? The promise of "Project Volta" and whatnot. Of course, running a pretty much pre-alpha early version of CM 12, battery life is actually worse than it was on KK. I'll chalk it up to the fact that LP still needs development for this device, in hopes of having good battery life, hopefully by next February. Material Design is also pretty to look at.
Click to expand...
Click to collapse
Lol I will totally agree with you on the battery life thing! I thought my phone was on its way out with how fast the stock KK versions were draining my battery. Constantly had to keep the phone on a charger when I was in one place. I will say that the battery life on DU was one of the things that really caught my attention from the start. Phone makes it through the day, can make it through the night if I forget to charge it overnight, and no more does the phone heat up to 125-140F. Highest I've seen, even with charging, screen on, streaming movies or TV over LTE, has been 98F. Night and day compared to the stock KK ROMs Moto vomited at us. I'd be surprised if other custom KK ROMs for our phones didn't have much improved battery life over that failed attempt at a PR stunt giving us stock KK.
I have to really give major props to the developers of the DU ROM which I ran for a solid 2 weeks, just prior to upgrading to 5.0 They have actually made KK a bearable OS on this device with which I could get 2 full work days out of the XT926M - battery-wise - with moderate use. Still, the MAXX battery is a beast, and less than 2 days should not be acceptable. Under JB that was the case. If LP doesn't deliver soon, I am definitely going back to JB. And right around next March, my contract for this device is up anyway.
+1 for dirty unicorn dev
Not_A_Dev said:
I have to really give major props to the developers of the DU ROM which I ran for a solid 2 weeks, just prior to upgrading to 5.0 They have actually made KK a bearable OS on this device with which I could get 2 full work days out of the XT926M - battery-wise - with moderate use. Still, the MAXX battery is a beast, and less than 2 days should not be acceptable. Under JB that was the case. If LP doesn't deliver soon, I am definitely going back to JB. And right around next March, my contract for this device is up anyway.
Click to expand...
Click to collapse