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
Related
I really want some ICS love! Anyone know any thing about any ROMs based off of ICS or.... even better.... CM9? I am new to this rooting thing so...
Wow. Just search through all the topics in the skyrocket forum and you'll find your answer
Sent from my SAMSUNG-SGH-I727 using xda premium
This is like some kind of Platonic Ideal of a post here.
But, I'm pretty sure they're going to release ICS at the big Samsung/AT&T/Google event tomorrow.
Savitt said:
I really want some ICS love! Anyone know any thing about any ROMs based off of ICS or.... even better.... CM9? I am new to this rooting thing so...
Click to expand...
Click to collapse
Before you ask a question, please search the forum first, therefore other members will not give you harsh answers.
If you are looking for answers to rooting your device, please go here:
http://forum.xda-developers.com/showthread.php?t=1383464
If you are searching for rom developments, please go here:
http://forum.xda-developers.com/forumdisplay.php?f=1383
If you are searching for information on Ice Cream Sandwich, best luck is to search google or in the general section. There is NO certain release date of when ICS will be available, but there are rumors and some information that states it will be in Q1 of 2012.
Good luck to you.
Please press "Thanks" if I have helped you in anyway.
What event? Do you have a link. ?
I think he's referring to the CES 2012 event on January 9th.
Oh thats not tomarrow lol tomarrow is the 5th . Darn i was hoping there was some att/sammy event tomarrow.
Phoneguy589 said:
I think he's referring to the CES 2012 event on January 9th.
Click to expand...
Click to collapse
Indeed. That is the only upcoming event that I am aware of.
I wasn't...LOL. I can't afford to buy another phone. I just pre-ordered the Transformer Prime so I'm out of money...so my wife says.
silver03wrx said:
Oh thats not tomarrow lol tomarrow is the 5th . Darn i was hoping there was some att/sammy event tomarrow.
Click to expand...
Click to collapse
Haha me too my friend l lol the hope jumped up through my body!
Sent from my SAMSUNG-SGH-I727 using xda premium
No, I was being mean. There's not event tomorrow and ICS is but a distant dream. Enjoy your device now and don't sweat the OS version number. ICS is not going to give much more over what you have now.
I'm sort of with the OP in wanting to know about any rom based on ICS. I've searched the forums and google to no avail. I'm seeing other devices getting a version of CM9, but nothing for the Skyrocket yet.
So, my question is this: Is anyone working on an ICS rom for the Skyrocket such as CM9? If I had the know-how I'd be all over that since we have such a great and powerful phone. I know AT&T and Samsung will eventually release ICS, but it'll never compare to the likes of CyanogenMod.
No no ones working on it. Why make a hacked up version. Thats not very functional. When our update is just around the corner. We will see ics, and mabye cm9 but.not until theres a leak for the skyrocket or the actuall update.
silver03wrx said:
No no ones working on it. Why make a hacked up version. Thats not very functional. When our update is just around the corner. We will see ics, and mabye cm9 but.not until theres a leak for the skyrocket or the actuall update.
Click to expand...
Click to collapse
Thanks. Like some others I'm an impatient type...especially after using ICS on my HTC Incredible. Can hardly wait to have it on my Skyrocket, but will sit quietly (maybe) and wait.
Not saying this to start a flamewar or anything but why are so many people with talent focusing on old roms and tweaks and not ICS? IMO this is what is hurting Android with better development etc, it seems like iOS hacking and tweeking seems to be more tight-knit and innovative, where Android seems to just have (almost) the same thing over and over again.
Now, I am not saying it is the same, there are obviously very difficult functions and programming that needs to be done, but I don't get why all efforts by everyone wouldn't be focused on ICS since it is what Android needs, a fresh new OS that could change the game.
Turbojugend said:
Not saying this to start a flamewar or anything but why are so many people with talent focusing on old roms and tweaks and not ICS? IMO this is what is hurting Android with better development etc, it seems like iOS hacking and tweeking seems to be more tight-knit and innovative, where Android seems to just have (almost) the same thing over and over again.
Now, I am not saying it is the same, there are obviously very difficult functions and programming that needs to be done, but I don't get why all efforts by everyone wouldn't be focused on ICS since it is what Android needs, a fresh new OS that could change the game.
Click to expand...
Click to collapse
so you want us to randomly pull kernel source for ICS (linux kernel 3.0+) out of our ass?
samsung has not provided us with enough driver libraries/binary blobs that work properly with AOSP GB, let alone ICS.
the problem here is the manufacturers. they control the proprietary hardware/drivers we need to focus attention on something. we could hack something together, but it wouldnt be worth a crap, and by the time we got something working half decent, Official would be dropped on us with source and we would have to basically start fresh....
tl;dr: it is not worth the time it takes to try to hack something together until we have 'something' from samsung.
Pirateghost said:
so you want us to randomly pull kernel source for ICS (linux kernel 3.0+) out of our ass?
samsung has not provided us with enough driver libraries/binary blobs that work properly with AOSP GB, let alone ICS.
the problem here is the manufacturers. they control the proprietary hardware/drivers we need to focus attention on something. we could hack something together, but it wouldnt be worth a crap, and by the time we got something working half decent, Official would be dropped on us with source and we would have to basically start fresh....
tl;dr: it is not worth the time it takes to try to hack something together until we have 'something' from samsung.
Click to expand...
Click to collapse
Exactly its not as simple as ics source code being out, you also need proper drivers for the hardware
Pirateghost said:
so you want us to randomly pull kernel source for ICS (linux kernel 3.0+) out of our ass?
Click to expand...
Click to collapse
That answers a lot for me, like I said I am not too familiar coming from Iphone (day one, I just got a Samsung Galaxy S II LTE (Skyrocket))
So obviously you need the kernel to work with the OS, I didn't know they were not released.
draztikrhymez said:
....you also need proper drivers for the hardware
Click to expand...
Click to collapse
Is it harder for phone hardware? Seems to be a lot of open source, or scene made drivers for, say video cards.
Turbojugend said:
That answers a lot for me, like I said I am not too familiar coming from Iphone (day one, I just got a Samsung Galaxy S II LTE (Skyrocket))
So obviously you need the kernel to work with the OS, I didn't know they were not released.
So what exactly is open about Android then? If you are at the mercy of the manufacture's to release the kernel, how is that open?
Click to expand...
Click to collapse
Android itself is OPEN. you can go and build your very own version of 4.0 ICS right now from source code. there are very few phones you can STABLY and RELIABLY run it on though.
The NEXUS line of phones exists for a reason. they are untouched by carriers (verizon teabagged the Galaxy Nexus a little), and do not have some stupid overlay on them. they are developer devices in that it is the first phone to get android updates straight from google (no manufacturer interference required).
every other phone is tainted with a manufacturer's UI. Touchwiz on Samsung phones (galaxy nexus is a samsung but they provided the hardware not the software), Sense on HTC, 'non-blur' on Motorola, whatever Sony calls theirs...lol, LG, etc
on top of that tainted Android interface is a carrier branding or lockdown (doesnt apply to the entire world, but im only referring to US here)
so google releases new version of Android
manufacturers build phone, and customize android to fit their model (this is where android almost stops being OPEN)
carriers get a hold of the manufacturers build of android and tweak and modify it themselves (more than likely they just tell the manufacturers what they want), as you know they love to include bloat and lock it down from the user
you receive your android phone after it has gone through all those steps....long process huh? we dont get updates to newer versions as quickly because of that long process...and they would rather us buy new phones instead of improving perfectly good hardware.
Android is open in the sense that manufacturers can use it however they wish, within reason. it is not necessarily meant to be 'open' to the average end user, and manufacturers dont want you messing with the phone they built. its the reason XDA is what it is today, albeit with roots deep in WinMo hacking.
Hey Pirateghost Really great in-depth info with your permission I would like to add this info for noobs here.
Pirateghost said:
Android itself is OPEN. you can go and build your very own version of 4.0 ICS right now from source code. there are very few phones you can STABLY and RELIABLY run it on though.
The NEXUS line of phones exists for a reason. they are untouched by carriers (verizon teabagged the Galaxy Nexus a little), and do not have some stupid overlay on them. they are developer devices in that it is the first phone to get android updates straight from google (no manufacturer interference required).
every other phone is tainted with a manufacturer's UI. Touchwiz on Samsung phones (galaxy nexus is a samsung but they provided the hardware not the software), Sense on HTC, 'non-blur' on Motorola, whatever Sony calls theirs...lol, LG, etc
on top of that tainted Android interface is a carrier branding or lockdown (doesnt apply to the entire world, but im only referring to US here)
so google releases new version of Android
manufacturers build phone, and customize android to fit their model (this is where android almost stops being OPEN)
carriers get a hold of the manufacturers build of android and tweak and modify it themselves (more than likely they just tell the manufacturers what they want), as you know they love to include bloat and lock it down from the user
you receive your android phone after it has gone through all those steps....long process huh? we dont get updates to newer versions as quickly because of that long process...and they would rather us buy new phones instead of improving perfectly good hardware.
Android is open in the sense that manufacturers can use it however they wish, within reason. it is not necessarily meant to be 'open' to the average end user, and manufacturers dont want you messing with the phone they built. its the reason XDA is what it is today, albeit with roots deep in WinMo hacking.
Click to expand...
Click to collapse
ICS was released on Oct 19th 2011. It is almost 4 months and still not a single phone was officially updated to ICS. The closest one was Nexus S which had an update that was pulled for being too buggy.
Why is it that android phones are so slow to update while WP7 & iOS have all their devices updated in days after a new update is out.
The wide varity of devices cannot be the reason as the team managing a device don't have to worry about other devices. For example, Galaxy S2 team needs to worry about Galaxy S2 and not other hundreds of devices.
Does upgrading in Android world means buying new phone and not software updaye like in iOS & WP7?
Although In part what you are asking makes sense it is in large part a flawed question and premise. I can not speak to windows mobile as I am not terribly familiar so everything going forward is about android and apple.
Yes we are all waiting to see how much each oem can f up ics with their version of android, whether it is tw or sense or blur etc. ics is a major change in how android handles things unlike ios5 which was in reality a very minor update to the system. And it was delayed by about 5 months from their typical release so when it was officially released it was available to most iOS devices true, but delayed all the same.
The delay for ics is caused by the oems thinking they can improve on it and give their own twist. If it was a vanilla update your premise would be accurate. As to the nexus s although the official release was pulled back there are several quality ports across several devices using it as a base
Though the source code was available previously, the first ICS device (the GSM Galaxy Nexus) was not released until mid-November. As mcord11758 mentioned, ICS is a *huge* updated to the Android system and it takes time to get everything coded to work properly.
I also saw some information last night that the 4.0.4 rollout would resume for Nexus S 4G devices today, so take a deep breath and relax
It's all that freedom man! It takes time to add bloatware,spyware and hideous UI "enhancements" you know.
alex2792 said:
It's all that freedom man! It takes time to add bloatware,spyware and hideous UI "enhancements" you know.
Click to expand...
Click to collapse
I have an iOS device. All ios5 did was eat my battery faster and do a weak job of copying androids notifications. Not sure what your bragging about
What I have always found funny is why independent devs can get roms out quicker. There was recent interview with one of Motorola's top execs that said the reason for delays was all the different hardware used in all the different phones. I am running jokers çm9 ics on my motorola electrify. An independent dev got it out before motorola with all their resources. They could get updates out a lot quicker if they so chose to.
Sent from my CM9 Motorola Electrify
mcord11758 said:
I have an iOS device. All ios5 did was eat my battery faster and do a weak job of copying androids notifications. Not sure what your bragging about
Click to expand...
Click to collapse
Well, at least you didn't have to wait 6-12 months to actually be able to update your device.
cdrice15 said:
What I have always found funny is why independent devs can get roms out quicker. There was recent interview with one of Motorola's top execs that said the reason for delays was all the different hardware used in all the different phones. I am running jokers çm9 ics on my motorola electrify. An independent dev got it out before motorola with all their resources. They could get updates out a lot quicker if they so chose to.
Sent from my CM9 Motorola Electrify
Click to expand...
Click to collapse
Independent devs get to release ROMs with a "sorry if it doesn't work, but tough sh*t" disclaimer. OEMs/Carriers have to be able to support the ROMs they ship.
Also have to remember that The CM based roms here use open source drivers that dont use the hardware to the fullest. While OEMs use closed sourced drivers built for the hardware. Once they get the update they have to wait for new drivers to be built to work with the hardware to the fullest.
alex2792 said:
It's all that freedom man! It takes time to add bloatware,spyware and hideous UI "enhancements" you know.
Click to expand...
Click to collapse
With each post I'm more convinced your an apple employee but I'll bite and ask what spyware you refer to.
Dave
Sent from my LG P920 using Tapatalk
alex2792 said:
Well, at least you didn't have to wait 6-12 months to actually be able to update your device.
Click to expand...
Click to collapse
Wait...are you saying you would rather a quick but flawed update rather than a delayed but more stable one?
Dave
Sent from my LG P920 using Tapatalk
mistermentality said:
With each post I'm more convinced your an apple employee but I'll bite and ask what spyware you refer to.
Dave
Sent from my LG P920 using Tapatalk
Click to expand...
Click to collapse
Carrier IQ anyone?
The reason it takes so long is because all the manufacturers have there own UI to make there phones stick out from the others and with major updates like in ICS they have to rewite there UI to work smoothly with ICS.
IamJAX said:
Why is it that android phones are so slow to update while WP7 & iOS have all their devices updated in days after a new update is out.
Click to expand...
Click to collapse
I have worked at Microsoft on Windows Phone 7 and on Windows Mobile. Going back pre WP7, updates generally simply didn't get released for phones. Microsoft is trying to improve that, but the software has to go through modification and testing for carriers. I don't think any version was ready for acceptance in less than four months, ever.
I suspect it's worse in Android-land (where my phones live), because at least Microsoft has big teams for their for-profit product. The major manufacturers also have teams on-site at Microsoft, working to do the customizations. And Microsoft controls the hardware more tightly than Android; for WP7's initial release, there were really only two hardware package options (e.g. screen size, resolution, camera, processor, etc.) So less to modify.
And then Moto adds their new Blur incarnation, HTC adds Sense, and so on, each requiring more changes and testing.
So the comparison between WP7 and ICS is off because of profit-driven teams, hardware diversity and software customization that MS doesn't allow.
Idk but isn't this site to get ICS before any update??? Lol
I'm running ICS in my Samsung Captivate and I can promise you ICS will never come to a Captivate ... but guess what I've got it!!!
I can point and laugh at iOS and WP7 for their limited OS and customize my device
Sent from my SGH-I897 using XDA App
To be honest I don't even know why people want ICS.
I was one of the unfortunates to get the update and now am desperately trying to downgrade back to stock 2.3.6 OR even better..load Cyanogen Mod on my phone.
The only good thing about the update is it led me to register and start to poke around this forum!
Bugs in ICS on my Nexus S include:
- Phone won't ring even when it should. It will only vibrate.
- Lags heavily and hangs when pulling up and trying to type a text message.
- Have to write text message most times before inputting contact to send to.
- Runs million processes in the background, thus killing my battery life.
When I upgraded it wouldn't let me sync my contacts and erased over half my names in my contact lists. When I turned on sync, it would continue to delete the names I had recently readded.
Since wiping all data from my phone, it works a bit more like it should and is a bit more snappy, but it still sucks. They need to hurry up and re-release ICS in a workable version, or at least let people roll back their phone to previous version like you could in Gingerbread.
Whatsup with naming their OS after generally crappy dessert items? Someobody in their marketing department is a glutton...
i want to up grade to ics... but i want to learn more first from here...
please give me some advice
SASQ!!!!!!
come on la, use your butt and think....
why android take such a long time to release a update.
because android has just tooo many different model....
while apple only got...umm.....1......
and windows.....ummm....less den android....
so think about it.....
maybe one----huawei Honor(U8860)ANDROID 4.0
the second edition of ICS commercial release
no guidelines, no warranty, no quality
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.
Quite simply, from what I'm reading about S6, and Exynos, the main reason for lack of major AOSP ROMS (CM13 has been finally ported), is the idea that Exynos is not documented so coding for it is difficult.
Knowing now that Snapdragon 820 is a Qualcom chip, which apparently is the most common SoC used for phones, should we expect to see a lot of AOSP based ROMs?
I am very used to Vanilla Android, and I don't think I could deal with TouchWiz, I like CM Theme Engine, and RRO Layers, so the big reason for my question is based on the hope that the probability of non-TouchWiz ROMs is high.
Also, I had a moto x 2014 and I've come to fall in love with AMOLED, and would like to stick to a small form factor 5 to 5.1 inches, combined with healthy ROM community, I'm kind of hoping S7 with SD820 might be the phone for me.
Please don't say "If you like Stock don't buy a Samsung", I get it, but it looks like maybe that stigma might not hold up soon if the ROM cookers are supportive.
Thanks!
I'm not sure on the international versions, but I know most carrier versions of the Note 4, S6, Note 5, etc. never got unlocked bootloaders in the first place, let alone custom ROMs. Knox is killer.
geoff5093 said:
I'm not sure on the international versions, but I know most carrier versions of the Note 4, S6, Note 5, etc. never got unlocked bootloaders in the first place, let alone custom ROMs. Knox is killer.
Click to expand...
Click to collapse
Tmobile variants of all the phones you listed are bootloader unlocked. Knox has never stopped anything.
@Shemploo yes more than likely AOSP roms will be available for the snapdragons. I'm betting even exynos variants will get it although probably a little later.
I don't do carrier contracts so I'd most likely look/hope for a developer/pure edition of the S7.
The Edge does not really interest me, unless they figured out some cool things to do with the curved screen that are actually useful.
I'd much rather have a fingerprint reader, and front sensors like the Moto's, I love waving my hand in front of the display to have it wake up and tell me the time.
People go... you are a Jedi!?
Airtioteclint said:
Tmobile variants of all the phones you listed are bootloader unlocked. Knox has never stopped anything.
@Shemploo yes more than likely AOSP roms will be available for the snapdragons. I'm betting even exynos variants will get it although probably a little later.
Click to expand...
Click to collapse
I know AT&T and Verizon are different stories, good to know it works for T-Mobile though.
Most if not all Sprint phones have unlocked bootloaders too. At least last time I checked!
Yes. However you got something wrong there. The reason why Qualcomm has all the fancy AOSP based ROMs (I say fancy because most people consider non aosp roms boring) is because of this. This is where QCOM releases their soruce code for the platforms. This makes fixing easier because you actually have the code. However exynos and all the other ones don't give a crap about the small percentage of their users that actually flash roms etc. Infact, they only want money. And guess what? ROMs = Longer device lifespan. That's why they don't release it. Thankfully enough there are some geniuses here on XDA that still are able to do the job for exynos! However, QCOM has allot better optimization with CM in terms of performance than with any other chipset. I live in the EU, which means Exynos. After already owning 2 exynos devices, I'm tired of the work that has to be done for them. I was lucky enough that both of them had Exynos chipsets that already had allot of devs mainly from other devices which made building possible for me.
@CTXz I suppose the closest thing to AOSP on Samsung devices QCom, or Exynos, is going to be Cyanogen right?
Would I be right to assume Cyanogen would be the first (possibly only) AOSP to build for Samsung?
In other words, would/could anyone build true AOSP based on Google's source code?
I understand both are considered AOSP, I'm asking cause from general experience with ROMs, when ROM is built on CM, they usually just build in the CM Theme Manager, and only the ROMs based on Google's code do things like RRO Layer support.
Shemploo said:
@CTXz I suppose the closest thing to AOSP on Samsung devices QCom, or Exynos, is going to be Cyanogen right?
Would I be right to assume Cyanogen would be the first (possibly only) AOSP to build for Samsung?
In other words, would/could anyone build true AOSP based on Google's source code?
I understand both are considered AOSP, I'm asking cause from general experience with ROMs, when ROM is built on CM, they usually just build in the CM Theme Manager, and only the ROMs based on Google's code do things like RRO Layer support.
Click to expand...
Click to collapse
Ofcourse, infact that is up to the devs, however CyanogenMod is usually recommended over pure AOSP due it's great documentation, common updates, it's optimizations and tweaks above stock AOSP. It's also the simplest to get the hands on.
EDIT: It's also important to know that CM isn't just AOSP with a few apps. While CM is based on AOSP, it still has it's own community and is still a different ROM than AOSP mainly when it comes to the internal changes.
..
CTXz said:
Ofcourse, infact that is up to the devs, however CyanogenMod is usually recommended over pure AOSP due it's great documentation, common updates, it's optimizations and tweaks above stock AOSP. It's also the simplest to get the hands on.
EDIT: It's also important to know that CM isn't just AOSP with a few apps. While CM is based on AOSP, it still has it's own community and is still a different ROM than AOSP mainly when it comes to the internal changes.
Click to expand...
Click to collapse
After Cm started trying to push that you make an acct with them I will never use CM again. I know that people say Inc has no relation to... whatever non-Inc calls themselves, but I no longer trust any of them and would rather buy a Windows phone or iPhone before I run them on any phone of mine again.
knitler said:
After Cm started trying to push that you make an acct with them I will never use CM again. I know that people say Inc has no relation to... whatever non-Inc calls themselves, but I no longer trust any of them and would rather buy a Windows phone or iPhone before I run them on any phone of mine again.
Click to expand...
Click to collapse
Um... CM =/= Cyanogen Inc
CM is a completely separate group that is not affected in any way. It's like XDA and GOogle. XDA is for developing and still both work on android. I know some people in the official CM group, all of them very friendly and none of it is affected by Cyanogen Inc. You're making yourself lies that aren't true. It's like blaming the entire CyanogenMod team because one dev for a specific device didn't fix the issue yet.
If CM is the main like, why not just get a Nexus and get it over with? You'll get CM right away.
Sent from my VIVO XL using Tapatalk
barondebxl said:
If CM is the main like, why not just get a Nexus and get it over with? You'll get CM right away.
Sent from my VIVO XL using Tapatalk
Click to expand...
Click to collapse
Because some people don't want a nexus
CTXz said:
Because some people don't want a nexus
Click to expand...
Click to collapse
But if CM is what you look for, isn't a Nexus your best bet? Unless you want the S7 hardware.
Sent from my VIVO XL using Tapatalk
barondebxl said:
But if CM is what you look for, isn't a Nexus your best bet? Unless you want the S7 hardware.
Sent from my VIVO XL using Tapatalk
Click to expand...
Click to collapse
And cripple it with bad, forever-beta, with half the functionally misssing software.
Sure hope we get aosp!
Sent from my SM-N920T using Tapatalk
I thought it was primarily due to the 64 bit architecture that was the hold up with aosp on the s6. Buy I could be wrong. Been a while since I went looking.
barondebxl said:
But if CM is what you look for, isn't a Nexus your best bet? Unless you want the S7 hardware.
Sent from my VIVO XL using Tapatalk
Click to expand...
Click to collapse
That is a good argument, however many people DO actually go for the look/hardware and with that said. Afterall xda wouldn't be this big if you could use the word nexus for all excuses, right ?
CTXz said:
That is a good argument, however many people DO actually go for the look/hardware and with that said. Afterall xda wouldn't be this big if you could use the word nexus for all excuses, right ?
Click to expand...
Click to collapse
Might want to get used to it as sooner or later it will only be nexus devices that are worked on.
Also what's the point of getting the device fore the hardware when aosp doesn't take advantage of the hardware? Aosp drivers don't compare to the stock ones.
Yes I read reviews.
I owned a Oneplus One years ago and I gave up waiting for an upgrade and bought something else.
I here that OnePlus is better at upgrading today than they were four years ago. Is this true ?
Like I said I read and I know OnePlus 6 has available an Oxygen Beta (Android Pie) but it has not been officially released ? Is true if I buy a device I may need to wait several months until they Officially release Android Pie.
Now I know you will say just run the Beta it is stable but here is the make of break question I need Android Pay and Wear OS. My experience tells me if I flash a Beta required apps like Android Pay and Wear OS may stop working.
If I buy today I think the safe thing will be to wait for Oxygen OS (Android Pie) to be released. Customer ROMs or Beta OS will break for sure Android Pay.
Other than hating to wait for official releases this device looks fine.
No wireless charging sucks but I can live without it.
The Pixel camera maybe better but I read the OnePlus 6 camera is not bad
The OnePlus 6T will be out in November but ..... THERE IS ALWAYS A NEW DEVICE around the corner. Wait for the OnePlus 6T..... oh but it a few months this will be released.
This device gives better value for the dollar.
Android pay is not working in Beta, you should read the OP forum in the beta thread to see all the things being said.
The 6T rumor is that it will come with Pie installed but since it isn't out yet nobody knows if it will really be installed out from the gate.
Personally, I think Oxygen OS is a mess and from what I see on the threads for Pie, they're just patching it yet again and putting a new UI on it over starting from scratch. All they keep doing is carrying over bugs from previous versions and then trying to re-patch them again for either the new device model and/or new Android system. Considering treble is now installed on both the 5 and 6, IMO they should have started fresh and should have been working on coding an entirely new OS 2 years ago.
If I were you, I would wait until Pie is released in the fall and see how it goes and what the complaints are before buying anything.
Official Pie has been released, you can already download the firmware and flash it.
As for updates and kernel source upload speed, the OP6 gets both the fastest among all devices I had.
As for taking pics, use the gcam port for great picture quality and the oos cam for [email protected] recording.
The Official build for Android pie has been released today which is nice as it took only about 1.5 months after Google released it themselves.
Thanks I jumped on a sale, and ordered one.
I am not even sure at this point I care about the Pixel, it may have a better camera but I am sure ordering the One Plus 6 I saved hundreds of dollars.
The OP 6T is set to be released in the next couple months. Unless you're in need of a headphone jack, I'd wait to get the latest version.
floridaman said:
Android pay is not working in Beta, you should read the OP forum in the beta thread to see all the things being said.
The 6T rumor is that it will come with Pie installed but since it isn't out yet nobody knows if it will really be installed out from the gate.
Personally, I think Oxygen OS is a mess and from what I see on the threads for Pie, they're just patching it yet again and putting a new UI on it over starting from scratch. All they keep doing is carrying over bugs from previous versions and then trying to re-patch them again for either the new device model and/or new Android system. Considering treble is now installed on both the 5 and 6, IMO they should have started fresh and should have been working on coding an entirely new OS 2 years ago.
If I were you, I would wait until Pie is released in the fall and see how it goes and what the complaints are before buying anything.
Click to expand...
Click to collapse
... That's not how android works .. even less since treble... You don't simply "patch" your Android version up to date, especially when it's a major revision that is changed. Most oftenly they start from scratch with some cherry picks. And rebuild blobs whenever necessary... files come from AOSP in it's normal form, then every time android releases a new version, this has to be merged with the current existing release yes, but that means that every difference from x that y has changes into x (x being the updated file, any of em, Y Being the old, already installed one)... Bringing something on /system over from one of the earlier oos, to a newer oos, would break alot. I mean.. we can't even run ob3 custom kernels on GM pie... Because changes... Having something stick around doesn't mean it hasn't been touched, porting is another thing, and there is also maybe a chance that it's the same group of devs handling this as it was back then. It's still oneplus. Also. Oos isnt nearly as bad as you make it sound.. Oos is by far the best fork of Android I've seen launched as an OEM specific android experience, and I've seen alot of phones. Simply due to its close resemblance of the pure experience, with it's small addins for simplicity, performance, and ease of use. The UI is Google's own new material guideline. Not oneplus'. And there was 3 pie betas wherein other Companies reach up to 18-20 betas... Are we owning the same device?
efinityy said:
... That's not how android works .. even less since treble... You don't simply "patch" your Android version up to date, especially when it's a major revision that is changed. Most oftenly they start from scratch with some cherry picks. And rebuild blobs whenever necessary... files come from AOSP in it's normal form, then every time android releases a new version, this has to be merged with the current existing release yes, but that means that every difference from x that y has changes into x (x being the updated file, any of em, Y Being the old, already installed one)... Bringing something on /system over from one of the earlier oos, to a newer oos, would break alot. I mean.. we can't even run ob3 custom kernels on GM pie... Because changes... Having something stick around doesn't mean it hasn't been touched, porting is another thing, and there is also maybe a chance that it's the same group of devs handling this as it was back then. It's still oneplus. Also. Oos isnt nearly as bad as you make it sound.. Oos is by far the best fork of Android I've seen launched as an OEM specific android experience, and I've seen alot of phones. Simply due to its close resemblance of the pure experience, with it's small addins for simplicity, performance, and ease of use. The UI is Google's own new material guideline. Not oneplus'. And there was 3 pie betas wherein other Companies reach up to 18-20 betas... Are we owning the same device?
Click to expand...
Click to collapse
I didn't say they were patching Android, I said they were patching their OS. Yes, I know they are 2 different things and I know things are working differently since treble. They can fully keep taking their Oxygen OS and throwing it over the latest version of Android and patch it to make it work with the new code, which is exactly what they've been doing. Yes, they get a guideline, that doesn't mean they are stuck doing only that and making no improvements/changes. There are literally hundreds of options they can code for, but don't.
I'm sorry, but it's not only simple, it's downright beyond basic even to what Google turns on and codes for features. Spare me the dribble of "pure android" please, it's a ridiculous mantra. I've not put the beta's on my phone but have been reading the forum and I have not yet received the stable update that has been just pushed out. But I already see some of the complaints coming in and no I'm not talking about the nonsensical postings.
If you think that OP is doing a great job on their OS, then you and I clearly have different standards. I'm glad you love it so much, to each his own in that regard.
floridaman said:
I didn't say they were patching Android, I said they were patching their OS. Yes, I know they are 2 different things and I know things are working differently since treble. They can fully keep taking their Oxygen OS and throwing it over the latest version of Android and patch it to make it work with the new code, which is exactly what they've been doing. Yes, they get a guideline, that doesn't mean they are stuck doing only that and making no improvements/changes. There are literally hundreds of options they can code for, but don't.
I'm sorry, but it's not only simple, it's downright beyond basic even to what Google turns on and codes for features. Spare me the dribble of "pure android" please, it's a ridiculous mantra. I've not put the beta's on my phone but have been reading the forum and I have not yet received the stable update that has been just pushed out. But I already see some of the complaints coming in and no I'm not talking about the nonsensical postings.
If you think that OP is doing a great job on their OS, then you and I clearly have different standards. I'm glad you love it so much, to each his own in that regard.
Click to expand...
Click to collapse
To each their own indeed. And it's not a ridiculous mantra.just as countless many others, I do prefer to be able to switch over countless amounts of phone but still have the same familiar, debloated and resource friendly UI. Having to learning all the different "UX"s gets pretty dull, as soon as ie Samsung gets settled with one, they change design language. And that, for me, is a deal breaker, I don't feel like having to relearn the same basics over and over, and where I usually have to install another AOSP based ROM on ie my Xperia, HTC or Samsung. Whilst the OnePlus just has the familiarity and non-rubbish feel to it that AOSP has. But don't get me wrong, as you said, to each their own, and if it wasn't for people like you that don't want the stock feel, we wouldn't have custom kernels and/or ROMs. And I've ran all the betas except ob3 and currently run the stable... And I've yet to run into any app not loading, crashing, or features not working as intended. But I would recommend not jumping on the bandwagon as I regret doing so, until there are some more data and user reviews of the stable branch. And I'm not trusting anyone doing a forum post not being previously recognized or a proper reviewer. The stable build is solid, but it's still early to tell.