What are the odds of us getting an L Preview port - Verizon HTC One (M8)

I mean, we have a GPE port. I know, I know, this is literally the definition of shot-in-the-dark. No source code release means extremely difficult to build for alternate devices, and unless Google chooses to release a preview for GPE devices we're screwed.
Still, I have to ask: is there even a tiny chance?

Oh there is always a chance of a crappy port. But you are better off just waiting for the official release. Look at the issues CM has and they have source.
Sent from my HTC6525LVW using Tapatalk

Of an official preview I would say nill. That a Dev will hack something together even if its just the GUI I would say put that pretty high.
I would bet a lot of the aspo devs have already looked at it and are trying to size up the challenge.
Sent from my HTC6525LVW using XDA Free mobile app

CM has source? I think Google is waiting on the Nexus 9 to release source. They always withhold source until the Nexus device that launches the new version is released. Then they release source and CM and the others start building. KitKat didn't get a Nexus device; if you remember, it was released on Halloween (31 October) last year. It was just released, source and all. And CM had releases inside a week. There's a developer preview out, but it's beta and has issues even in the official binaries. I'm not putting it on my N7.
We're getting L within 90 days from HTC. Then you'll see the Sense-based ROMs get it. But I imagine CM will beat HTC to the punch, so all the AOSP-alike ROMs will get it long before then. CM, LiquidSmooth, and such.

i think what @termleech was saying is look at how much time it takes for a "stable" CM release for any given phone. and they have a KK source base to work with.
also @termleech it wouldn't just be google to decided. google would have to ok it. then they would give the source to HTC who would then release a build.
But its really not in HTC's interest. Unless google is going hey where not changing any of these features other then for bug fixes then HTC would be putting in time to build and test a build that they will have to disregard when google changes major things.

Unfortunately, I think the chances of a preview build are very low; however, devs have already started baking in L features into 4.4.4 GPE roms which would be a decent substitute until the GPE M8 gets the update and is then ported to our device. In any case, we're pretty much first in line for HTC when it comes to pushing L out. They've already promised an update within 90 days of the release but it will probably be sooner.

Related

When will Android 3.0 get released?

When will it get released? I have read everywhere that Google is focusing the most on the UI and im eager as hell to see it.
im also waiting to see the next android version
it might be 2.3 tho
3.0 might be released next year id say
Froyo didn't come out long ago. So i don't tnink they will bring another one out this early
Sent from my GT540 using XDA App
As far as I know Google will release the new version of Android OS some time in the mid this month.
retskrad said:
When will it get released? I have read everywhere that Google is focusing the most on the UI and im eager as hell to see it.
Click to expand...
Click to collapse
Welcome to XDA! Nothing official on a date but maybe by the end of Oct.
What device are you using and planning to upgrade?
i personally wont expect it for months yet. even more so to be ported to existing devices.
jh17 said:
i personally wont expect it for months yet. even more so to be ported to existing devices.
Click to expand...
Click to collapse
Froyo was running / ported on the motorola droid within a week of the Google I/O announcement. The nexus one had it officially released 24 hours or so after the announcement.
Any build of 3.0 will get ported to most major phones (well the phones that aren't locked down, thanks so much moto droid 2 / X and the new HTC g2) in less then a week from any build released.
I thought the rumoured date was Nov. 11th or something like that
No source because i forget where i got that one from
This might shed some light
http://www.miui.com/thread-857-1-1.html
Translate it, enjoy.

What's the point in 4.4 when most phones aren't even on 4.3 yet?

This has always puzzled me since I switched over to Android 5 months ago. I noticed that most carriers don't push the latest update for months to come, if ever in some cases. For example, my SGS4 ATT hasn't been officially updated to 4.3 yet, but 4.4 is being released soon. Its not like as soon as 4.4 is released, everyone can update to it, like iOS. My question is, why is this? What's the point in Android releasing another major update when the majority of non-rooted phones aren't even running their latest update?
Sent from my SGH-I337 using xda app-developers app
It's not googles fault the oems can't keep up. Google even gave them the tools they needed to port software to newer versions of Android. If google took longer to release, that's longer oems would take
Sent from my Samsung Galaxy S4
Google
I think a big part of it is that Google knows that the people with the know-how will go get 4.4 themselves and start testing/coming up with fixes for bugs and such. Yes, we all do it for advanced features/rooting, but at the same time Google can go look at bug fixes online just like the rest of us can
bubblebuddyi said:
This has always puzzled me since I switched over to Android 5 months ago. I noticed that most carriers don't push the latest update for months to come, if ever in some cases. For example, my SGS4 ATT hasn't been officially updated to 4.3 yet, but 4.4 is being released soon. Its not like as soon as 4.4 is released, everyone can update to it, like iOS. My question is, why is this? What's the point in Android releasing another major update when the majority of non-rooted phones aren't even running their latest update?
Sent from my SGH-I337 using xda app-developers app
Click to expand...
Click to collapse
Simple, most updates are minor and bit by bit remove the "Open" source features of AOSP.
Next android version will include the ability to have custom Messenger app that can recieve SMS. Google will probably replace it with a propietary version that integrates with g+ and other services and end up not support AOSP version. Its only natural because propietary software earns alot more money and google can earn money both from ads and its services.
Yes, android as we know it is being left to die by google.
Also, the thing others said here are correct, OEMs do not have the interest to update or support a device for more than one year, thats their cycle. This adds to android version fragmentation.
Its the same reason there are over 30% of devices still using gingerbread 2.3
Android devices are usually advertised heavily, distributed, supported for 1 year, and abandoned. This goes mostly for midrange devices. Flagships might get special treatment-
Low end devices are never updated to rarely if never updated to new versions. Of course, this policy might differ based on OEM.
LG uisually releases 1 update and thats it. Samsung does 2-3 updates for higher end devices. Dunno about HTC or Sony, but they should be the same.
it may be availble for all device
as far as i know google is planing to bring all android phones under one roof with same os.. they had worked on pusing updates through playstore .. so we may see soon that we are getting our os upgrades directly from playstore
Pipo
Keep an close eye on official release& waiting!
Thank goodness for developers who take the updates and then make far better roms than the carriers could ever do.. These updates are more for the artists that make the art that is the rom, or am I wrong?
M919 running Virgin GP ed. ROM
I think for the moment the answer is you simply don't need 4.4.
If you have 4.1 and up your phone will support all the new apps coming with 4.4, in fact they're already available...
We won't see universal Play Store upgrading for the foreseeable future, because remember, Google wouldn't want the hassle of handling hardware support for every single phone out there, they have enough on their plate with their Nexus line.
The road taken, if you will, probably is for the best, where Google develop their services independently of the platform as much as possible.
Sent from my GT-I9000 using XDA Premium 4 mobile app

Has lack of 3rd party "official roms" changed much?

So generally speaking I've always stuck to sister phones of nexus devices. My Samsung Captivate was sorta the "nexus with an SD card" in terms of being identical to the Nexus S, the LG Optimus G was "4g + SD Card Nexus" and I never really had any problems running roms with the latest version of Android. Running nightlys and experimental software wasn't such a big deal because it allowed me to keep my phone up to date long after it would have been updated otherwise.
The general lack of desire to stand behind the stability of a particular version coupled with a general lack of "stable" releases kinda has me jaded when I can just keep rolling with the newest version of Android officially.
It has made me wonder if there are any "stable rolling release" versions of roms? Like "here is the stable rolling release, once a week we push the latest stable versions and features from our nightles over the last month!" Letting those who want to try the newest upgrades immediately have nightly and letting people who want the latest version of android with more tweaks get the version that suits them the most?
Edit: I'm not really asking for specific ROM recommendations so much as ROM trends in general.
Many AOSP roms do this.. We can't recommend Roma to you because those comparisons are against the rules but the ROM I use (slim) has weekly builds and then a monthly stable.
The stable has a code freeze a while before release to extend testing to ensure it is stable but the weeklies are stable too.
The devs also post personal test builds in between the weeklies for those who want to test particular new functions.
Sent from my Nexus 5 using Tapatalk
rootSU said:
Many AOSP roms do this.. We can't recommend Roma to you because those comparisons are against the rules but the ROM I use (slim) has weekly builds and then a monthly stable.
The stable has a code freeze a while before release to extend testing to ensure it is stable but the weeklies are stable too.
The devs also post personal test builds in between the weeklies for those who want to test particular new functions.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
My mistake I should have phrased the original thread more carefully and I'll edit it after this.
I was more looking at general ROM trends as opposed to looking for a specific ROM.
Many AOSP roms do this
Sent from my Nexus 5 using Tapatalk
Snow_fox said:
So generally speaking I've always stuck to sister phones of nexus devices. My Samsung Captivate was sorta the "nexus with an SD card" in terms of being identical to the Nexus S, the LG Optimus G was "4g + SD Card Nexus" and I never really had any problems running roms with the latest version of Android. Running nightlys and experimental software wasn't such a big deal because it allowed me to keep my phone up to date long after it would have been updated otherwise.
The general lack of desire to stand behind the stability of a particular version coupled with a general lack of "stable" releases kinda has me jaded when I can just keep rolling with the newest version of Android officially.
It has made me wonder if there are any "stable rolling release" versions of roms? Like "here is the stable rolling release, once a week we push the latest stable versions and features from our nightles over the last month!" Letting those who want to try the newest upgrades immediately have nightly and letting people who want the latest version of android with more tweaks get the version that suits them the most?
Edit: I'm not really asking for specific ROM recommendations so much as ROM trends in general.
Click to expand...
Click to collapse
your "sister" phones in reality have nothing to do with the nexus, and are not similar. the only similarities they have is using the same kind of cpu, but tweaked completely differently. maybe the same screens as well. all the other internals are completely different. completely different as in your "sister" phones are nothing like their nexus counterparts. so unlike nexus, that i would never call them a "sister" phone.
and there are many completely stable aosp roms out there for the n5.
I really don't see a point in releasing "Stable Releases" with a nexus device. With a Nexus device, the whole source is there for developers and the device is fully unlocked. So most likely, if a dev knows what they are doing, there shouldn't be very many bugs, if any at all. It would be mainly feature additions and whatever else the dev wants to add.
Now with Non Nexus devices, it's a little harder to get EVERYTHING working since the devices are usually locked down and all. So "Stable releases" are kind of a bigger deal.
That's my view on it anyway.
the thing about android is that someone somewhere is finding something new everyday, and waiting around for the release of monthly releases of roms kinda puts the users off("ohh active notifications!" "wow heads up notification" "can i get the <insert fancy OEM specific feature here> in my device?"). I for one, coming from an XMP which had rom's being updated once every two week found it hard in the N5 community where the nightlies where more common.
The thing is you have to keep changing fast and there is always room for improvement so there can never be a "stable" version just short term triumphs.
The thing is, there isn't much need for "stable" builds anymore, the nightlies for most ROMs are really stable and daily driver capable (of course sometimes something doesn't work right here and there, but generally). Some have Delta updates too so you don't need to flash the entire ROM over each nightly, kind of like daily OTAs.
jsgraphicart said:
I really don't see a point in releasing "Stable Releases" with a nexus device. With a Nexus device, the whole source is there for developers and the device is fully unlocked. So most likely, if a dev knows what they are doing, there shouldn't be very many bugs, if any at all. It would be mainly feature additions and whatever else the dev wants to add.
Now with Non Nexus devices, it's a little harder to get EVERYTHING working since the devices are usually locked down and all. So "Stable releases" are kind of a bigger deal.
That's my view on it anyway.
Click to expand...
Click to collapse
Out of curiosity is the same true for the Play edition devices? With that said I was thinking about ROMs in general not ROMs specific to devices. I'd also argue (having worked QA professionally) the need to check new features added ranges drastically depending on what you want to add to the device.
gamer.11 said:
the thing about android is that someone somewhere is finding something new everyday, and waiting around for the release of monthly releases of roms kinda puts the users off("ohh active notifications!" "wow heads up notification" "can i get the <insert fancy OEM specific feature here> in my device?"). I for one, coming from an XMP which had rom's being updated once every two week found it hard in the N5 community where the nightlies where more common.
The thing is you have to keep changing fast and there is always room for improvement so there can never be a "stable" version just short term triumphs.
Click to expand...
Click to collapse
As someone who loves new features I find the "additives" as great. I've also found just having the latest version of Android with a working stable feature set is pretty cool too.
Lethargy said:
The thing is, there isn't much need for "stable" builds anymore, the nightlies for most ROMs are really stable and daily driver capable (of course sometimes something doesn't work right here and there, but generally). Some have Delta updates too so you don't need to flash the entire ROM over each nightly, kind of like daily OTAs.
Click to expand...
Click to collapse
I might look into the Delta Updates. There are a few things I do miss about ROMs such as being able to close all active windows and stuff. I just don't miss how some ROMs basically were just a conglomeration of shoving as much stuff into one ROM as possible regardless of how it ended up.
Snow_fox said:
Out of curiosity is the same true for the Play edition devices? With that said I was thinking about ROMs in general not ROMs specific to devices. I'd also argue (having worked QA professionally) the need to check new features added ranges drastically depending on what you want to add to the device.
Click to expand...
Click to collapse
Google Play Edition devices aren't the same as Nexus devices, they just use a more "AOSP-like" ROM that doesn't have the respective OEM skin on top of it. Not sure if bootloader unlocking process is different (Nexus devices have fastboot oem unlock) but the stock ROM on them still has some parts of the OEM framework underneath (like double tap to wake and duo camera editing on HTC One M8). The Nexus 5 is more popular then Google Play Edition devices and which is why it subsequently has more developer support.
Lethargy said:
Google Play Edition devices aren't the same as Nexus devices, they just use a more "AOSP-like" ROM that doesn't have the respective OEM skin on top of it. Not sure if bootloader unlocking process is different (Nexus devices have fastboot oem unlock) but the stock ROM on them still has some parts of the OEM framework underneath (like double tap to wake and duo camera editing on HTC One M8). The Nexus 5 is more popular then Google Play Edition devices and which is why it subsequently has more developer support.
Click to expand...
Click to collapse
This makes sense. I didn't know if the Play Edition devices still had OEM fragments or if they were as free as the Nexus series.
Heavy oem frameworks
Sent from my Nexus 5 using Tapatalk
To be fair, there was a pretty significant gap between 4.2 releasing on the Nexus 4 and Cyanogenmod releasing 10.2 stable. As mentioned though, many of the ROMs have released stable versions and those that haven't are still fairly stable despite not having an "official" stable release.
I will say that I'm less likely to stick with a ROM despite bugs on Nexus devices than on other devices for two main reasons. With other devices, you're often getting rid of a manufacturer skin (so it's a completely different interface, instead of just having some tweaks) or you're moving up an Android version early.
Its worth pointing out that some devs only call their last ever release "stable" when they absolutely won't add or change anything again.
I think it's too easy to get wrapped up in the terminology and not appreciate the development we have
What a stable release means to 1 dev, means something else to another.
Sent from my Nexus 5 using Tapatalk
nearly every single ROM that I've ever used that has been titled "stable", has been less stable then the regular builds. especially with cm. a real ROM is neither called " stable" nor "experimental", its just called by its name and released. people add the word "stable" to them just to trick a few into a few more downloads.
There number of quotation marks in here is too damn high.
For good reason...
Sent from my Nexus 5 using Tapatalk

Guess on how long it will take for a 5.0 rom once AOSP is released?

This is obviously a difficult question to answer since it's all speculation but I am needing to decide between sticking with my Nexus 5 and getting the Android 5.0 update on November 3rd or ordering the OnePlus One that I preordered on Monday. I think 5.0 is kind of a game changer and I don't want to be rocking 4.4.4 until possibly February waiting for Cyanogenmod to push out 5.0.
So what I'm wondering is about how long it is expected to take for a decent 5.0 rom for the One to come out once AOSP drops? I have had Nexus phones since the Galaxy Nexus so I'm not used to having to think about these kinds of things, haha.
paulr24 said:
This is obviously a difficult question to answer since it's all speculation but I am needing to decide between sticking with my Nexus 5 and getting the Android 5.0 update on November 3rd or ordering the OnePlus One that I preordered on Monday. I think 5.0 is kind of a game changer and I don't want to be rocking 4.4.4 until possibly February waiting for Cyanogenmod to push out 5.0.
So what I'm wondering is about how long it is expected to take for a decent 5.0 rom for the One to come out once AOSP drops? I have had Nexus phones since the Galaxy Nexus so I'm not used to having to think about these kinds of things, haha.
Click to expand...
Click to collapse
Official CM11S confirmed to be released 90 days after release. I don't know the first CM nightlies, which may be unusable because of bugs will maybe start 1.5 or 2 months after release. AOSP port should be there noticeably sooner Maybe we'll even see the dev preview ported before the release
5-6 days for the nightlies for the first alpha versions.
It's kinda like asking how long a piece of string is. Nobody can answer this question for sure.
Transmitted via Bacon
2 weeks.
Sent from my Nexus 5
1day
Sent from my A0001 using XDA Free mobile app
Within 3 months of release for 11S but for sources who knows they will need all the updated drivers etc from the manufacturers and such.
Thanks guys, I somehow forgot about CM alpha builds, nightlies, etc. It's been a while since I was a CM flash-a-holic I guess, haha. I'm totally fine with flashing somewhat unstable builds though, so I went ahead and pre-ordered the One. Now I have a 4-6 week wait anyway so maybe we'll have a usable 5.0 build by then.

What are the odds we get a 6.0 ROM soon?

Since it's being released in a couple days, is it possible we will get the source code to build for OnePlus?
Sent from my A0001 using XDA Free mobile app
it is possible, but i don't know what will happened
From the official sources, no clue. From ROM devs, I'd say give it a month once source code drops. Cyanogenmod already built for this device, I mean look at the back of the phone, so I'm sure they will support us for at least 2 more android versions. My very first android phone the Droid Incredible came out in 2010 and for rom support from devs all the way up to 4.4.4, so I'd say pretty dang high from rom devs. Helps also that we have a simple bootloader unlock, which makes devs even more inclined to work on the device. Based on my past device experience, we'll get at least 3 more major versions, 6.0 included, maybe more. By then, your battery will be useless, and you'll have moved on, which is awesome.
kdb424 said:
From the official sources, no clue. From ROM devs, I'd say give it a month once source code drops. Cyanogenmod already built for this device, I mean look at the back of the phone, so I'm sure they will support us for at least 2 more android versions. My very first android phone the Droid Incredible came out in 2010 and for rom support from devs all the way up to 4.4.4, so I'd say pretty dang high from rom devs. Helps also that we have a simple bootloader unlock, which makes devs even more inclined to work on the device. Based on my past device experience, we'll get at least 3 more major versions, 6.0 included, maybe more. By then, your battery will be useless, and you'll have moved on, which is awesome.
Click to expand...
Click to collapse
CM are only obligated to support this device until April next year, so Marshmallow will be the last official version we get. They're contracted for 24 months from the time of release and they'll drop this device like a hot potato the first chance they get.
Heisenberg said:
CM are only obligated to support this device until April next year, so Marshmallow will be the last official version we get. They're contracted for 24 months from the time of release and they'll drop this device like a hot potato the first chance they get.
Click to expand...
Click to collapse
While I'd like to agree with you, that's in regards to business, we will see 6.0 for that reason alone. I was more referring to the fact that we still see updates on the nexus 4 up to 5.1 and the fact that open popular devices seem to get much longer support. Wasn't trying to disagree with you at all in that respect. I'm not that likes to hang onto their old devices, or sell them to friends, so I have seen how amazing that support can be even for older devices. My TF101 tablet is still rocking, and running 5.1.1 it's smoother than it's ever been. Don't think that'll see 6.0, but I didn't expect it to make it to 5.0. It all comes down to "We'll see how long it gets supported, but don't demand anything past 6.0" even though historically, we should get 3 more major versions if it follows most devices paths when it comes to rom support. That boing said, I'll be flashing 6.0 as soon as we get a rom that can multiboot!
kdb424 said:
While I'd like to agree with you, that's in regards to business, we will see 6.0 for that reason alone. I was more referring to the fact that we still see updates on the nexus 4 up to 5.1 and the fact that open popular devices seem to get much longer support. Wasn't trying to disagree with you at all in that respect. I'm not that likes to hang onto their old devices, or sell them to friends, so I have seen how amazing that support can be even for older devices. My TF101 tablet is still rocking, and running 5.1.1 it's smoother than it's ever been. Don't think that'll see 6.0, but I didn't expect it to make it to 5.0. It all comes down to "We'll see how long it gets supported, but don't demand anything past 6.0" even though historically, we should get 3 more major versions if it follows most devices paths when it comes to rom support. That boing said, I'll be flashing 6.0 as soon as we get a rom that can multiboot!
Click to expand...
Click to collapse
There's no doubt we'll see the next version after Marshmallow on this phone, but I can guarantee you it won't be in the form of official updates via Cyanogen Inc, it'll be in the form of community developed ROMs via CyanogenMod. If you meant CyanogenMod and not Cyanogen Inc then I misunderstood you.
I just meant Roms in general
Sent from my A0001 using XDA Free mobile app
Rom developers are really fast, i would say 1 week after we get the source there will be a alpha version. Cyanogen13 will take at least months.
_Beni_ said:
Rom developers are really fast, i would say 1 week after we get the source there will be a alpha version. Cyanogen13 will take at least months.
Click to expand...
Click to collapse
Sounds good to me! We have great devs here! Hopefully they don't leave for the Nexus phones, they really aren't worth the $ in my opinion. 808 and 810 have too many problems. I got the Moto X Pure and had that for 2 weeks and even the 808 had terrible heating issues. This years chipsets by Qualcomm are just terrible. Not to mention even now, 3 weeks in they have no dev support and Motorola (now Lenovo) is very shady company.
Sent from my A0001 using XDA Free mobile app
nikeman513 said:
Sounds good to me! We have great devs here! Hopefully they don't leave for the Nexus phones, they really aren't worth the $ in my opinion. 808 and 810 have too many problems. I got the Moto X Pure and had that for 2 weeks and even the 808 had terrible heating issues. This years chipsets by Qualcomm are just terrible. Not to mention even now, 3 weeks in they have no dev support and Motorola (now Lenovo) is very shady company.
Sent from my A0001 using XDA Free mobile app
Click to expand...
Click to collapse
What makes Moto shady? Nexus 6, first non nexus company to update their phones to lollipop, budget friendly phones...
And even if they were shady, I think OnePlus still takes the #1 spot in that category lol
jukiewalsh said:
What makes Moto shady? Nexus 6, first non nexus company to update their phones to lollipop, budget friendly phones...
And even if they were shady, I think OnePlus still takes the #1 spot in that category lol
Click to expand...
Click to collapse
Motorola says they aren't going to update the Moto E although they advertised that they would. Also not updating Moto X 2014 AT&T and Verizon version.
runderekrun said:
Motorola says they aren't going to update the Moto E although they advertised that they would. Also not updating Moto X 2014 AT&T and Verizon version.
Click to expand...
Click to collapse
Moto E: cheap budget phone that I think people only bought as a placeholder when they broke a phone or something else happened, it's not a flagship. nobody bought it to use for 2+ years and I don't think it was intended as such.
Moto x: did you see that the pure is getting updated? That means it was the carriers decision, not Motorola's. Also, it's easy to convert the att/Verizon version to the pure version and then you'll get the update fine.
jukiewalsh said:
What makes Moto shady? Nexus 6, first non nexus company to update their phones to lollipop, budget friendly phones...
And even if they were shady, I think OnePlus still takes the #1 spot in that category lol
Click to expand...
Click to collapse
As soon as Lenovo brought out Pure they let go about 500 Motorola employees, many who were in the dev department... They are giving people hard times about returns saying it will take 6-8 weeks to get their money back on an overnight return label. The pure QC is piss poor, if you go to their forums, their most popular thread is about returning the phone... This clearly isn't the same Motorola we used to love. I'm not big on OnePlus either, I only came back here, because at least I know my OnePlus works, I'll never buy from them again though, that's for sure.
Sent from my A0001 using XDA Free mobile app
Here they don't say we will get COS13 but only Oxygen / Hydrogen :
http://www.gadgetlite.in/2015/10/here-is-list-of-devices-getting-android.html#.VhNtuWuBS6F
But since the communication of Cyanogen is not really a "thing" I won't settle for this news
Source has dropped, so we might see devs starting to build soon
https://android.googlesource.com/platform/build/+/marshmallow-release
Anybody already found the radio online time fix commits? or didnt they even fix it?
Well i think it will be possible to get a bootable AOSP 6.0 Rom , cause we already had a booting 5.1.51 Rom!
_Beni_ said:
Anybody already found the radio online time fix commits? or didnt they even fix it?
Click to expand...
Click to collapse
the radio issues are driving me nuts, no matter what modem i use i still run into issues.
Heisenberg said:
CM are only obligated to support this device until April next year, so Marshmallow will be the last official version we get. They're contracted for 24 months from the time of release and they'll drop this device like a hot potato the first chance they get.
Click to expand...
Click to collapse
Agreed. Look at when we finally got 5.1.1...SMH
BTW, pretty sure you meant Cyanogen Inc, not CM
nikeman513 said:
Since it's being released in a couple days, is it possible we will get the source code to build for OnePlus?
Sent from my A0001 using XDA Free mobile app
Click to expand...
Click to collapse
The probability is high that we'll get a taste (not likely daily driver level sweet mind you) of Marshmallow by tomorrow:
Follow this thread

Categories

Resources