Related
...about Honeycomb. And it's not like I'm an Android developer or even an addict who's flashed a hundred different ROMs on his twelve different Android devices or anything. I actually just decided two days ago that I didn't want to use the stock gTablet ROM. So I don't know what the deal is with dreaming about mobile platform releases.
None of my friends are nerdy enough to appreciate this, so I was hopin' to get some love from the xda community. Love your work, by the way.
dear liveblog;
....
I dont even care about honeycomb anymore. The Froyo ROMs run extremely fast and stable. I care more about getting more games, apps, and widgets. This is the main problem with Android tablets. Not enough love in the Android market!
Point definitely taken, Mech. I really like where I'm already at with Froyo on my phone and Gtab.
Honeycomb is laggy and buggy according to reports. Froyo is stable and fast. Latest and greatest versus fast and stable. Take your pick.
Actually, Froyo was having some issues with some apps that Gingerbread does not, so I upgraded to Vegan-Tab 7.0 and haven't looked back. I don't know what Honeycomb can provide that I don't already have...
I'm going back to donut. This new fangled software is over rated
i like phone OS's. Its cool when you hold it to your ear to make a call on google voice. it gets head turns
I so feel you. Most of my dreams are about technology. At times i think there is something wrong with me. Why aren't I dreaming about lots of money or even Beautiful women? ah i mean my lovely wife who is the most beautiful girl in the whole wide world..
The major issue for me is video play back. Thats the biggest reason Im unable to leave Froyo. Then next to that is the speed. Its kind of like comparing Windows XP to Vista. As far as I can see from playing around with Honeycomb at BestBuy there is no real leap in OS. There is still so much to improve in the way of a user experience on Android. The basics are there but if you have no apps, games or widgets to install your just stairing at a wallpaper.
thebadfrog said:
I'm going back to donut. This new fangled software is over rated
Click to expand...
Click to collapse
Rofl...stfu gtfo with your donut. Haha
That's funny. Donut is neither stable or latest or greatest. You're gonna kill goodintentions with that post.
Donut is perfectly stable and quite delicious. Especially when Krispy Creme is making them fresh. mmmmmmmmmmmmm....tasty. Eclair is just a fancy french donut. It just gives up at the first sign of trouble.
I'm writing off Honeycomb. There's no reason to expect it will ever go to AOSP. Google didn't want to release it because it was hacky, and they didn't want unscrupulous providers or devs trying to shoehorn it onto phones.
Ice Cream Sandwich, on the other hand, is being heralded as the merging of the two codelines. If that's the case (and we'll find out for sure within a week), there's no reason Google shouldn't put it out to AOSP. Once that's done, nobody will say two words about Honeycomb again.
So, if you're "stuck" with perfectly serviceable Froyo/GB for another four to six months, just to pull a timeframe from my nether regions, is that really such an impediment? What's in Honeycomb that's so compelling (other than support for a few tablet-specific apps)?
MechAniX.one said:
The major issue for me is video play back. Thats the biggest reason Im unable to leave Froyo. Then next to that is the speed. Its kind of like comparing Windows XP to Vista. As far as I can see from playing around with Honeycomb at BestBuy there is no real leap in OS. There is still so much to improve in the way of a user experience on Android. The basics are there but if you have no apps, games or widgets to install your just stairing at a wallpaper.
Click to expand...
Click to collapse
You guys should try nightly CM7 from Cyanogen which is to me stable, faster and reliable, and gives great battery life when you combine with Pershoot's kernel.
I am running nightly Cyanogen on my phone EVO and my Gtablet. Could not be more happier for the choice I have made to go with Cyanogen.
I dont see any ROM being considered usable daily if it cant play back movies well.
now, i understand that development takes time, but given the potential of this tablet, i am somewhat dissapointed. i haven't really seen much progress past getting root, unlock, a recovery, a few roms based on stock, and one guy trying to port cm10. i guess what we are waiting for is the official jellybean upgrade before development picks up.
tweeklulz said:
now, i understand that development takes time, but given the potential of this tablet, i am somewhat dissapointed. i haven't really seen much progress past getting root, unlock, a recovery, a few roms based on stock, and one guy trying to port cm10. i guess what we are waiting for is the official jellybean upgrade before development picks up.
Click to expand...
Click to collapse
I feel you buddy, I'm coming from the Epic Touch forum that is very active in the development area. I too am disappointed with the lack of devs and ROMs for this tablet, but you have to realize its still fairly new and pretty expensive. I imagine most tablet devs would gravitate toward the Nexus 7 instead. Give it some time though, more will come.
Sent from my Samsung Galaxy S II Epic 4G Touch.
SuperSwagSauce said:
I feel you buddy, I'm coming from the Epic Touch forum that is very active in the development area. I too am disappointed with the lack of devs and ROMs for this tablet, but you have to realize its still fairly new and pretty expensive. I imagine most tablet devs would gravitate toward the Nexus 7 instead. Give it some time though, more will come.
Sent from my Samsung Galaxy S II Epic 4G Touch.
Click to expand...
Click to collapse
yeah, and they released this iteration way too soon (<6 months i think) for devs to leave their primes
I think a lot of the devs have sent theirs back. I'm kind of wishing I had with mine. Pretty disappointed with the device so far.
One of the AOKP devs is working on a port to the tf700, and judging by his twitter the only major things holding him back from a release are issues with Bluetooth and some visual glitches. Once we have that, roms should follow since we'll have a working AOSP base.
His twitter account is here:
www.twitter.com/_mrbirdman_
Actually to me, having custom ROMS on tablets is a little overrated. Root I can understand but seeing as I have owned the Xoom, Prime, and new the Infinity, must of the ROMS I have played with didn't add that much to the experience that stock already had. Outside of being able to use Sixaxis app, I have had little interest in rooting this Infinity. I think the wait for Jellybean is going to be with it.
Add in the fact that people are doing this on their free time, taking time away from their families, waiting a little bit won't hurt too bad.
SuperSwagSauce said:
I feel you buddy, I'm coming from the Epic Touch forum that is very active in the development area. I too am disappointed with the lack of devs and ROMs for this tablet, but you have to realize its still fairly new and pretty expensive. I imagine most tablet devs would gravitate toward the Nexus 7 instead. Give it some time though, more will come.
Sent from my Samsung Galaxy S II Epic 4G Touch.
Click to expand...
Click to collapse
and if you were in the e4gt forums from the beginning you will remember that it took several months for anything worth while to show up and how long for stable cm9? it took that forum quite a while to really get going.
legendary1022 said:
Actually to me, having custom ROMS on tablets is a little overrated. Root I can understand but seeing as I have owned the Xoom, Prime, and new the Infinity, must of the ROMS I have played with didn't add that much to the experience that stock already had. Outside of being able to use Sixaxis app, I have had little interest in rooting this Infinity. I think the wait for Jellybean is going to be with it.
Add in the fact that people are doing this on their free time, taking time away from their families, waiting a little bit won't hurt too bad.
Click to expand...
Click to collapse
Well to each their own, but to me, it's in custom development that you really begin to use the device to it's full potential. For instance, the OG Xoom has been literally given new life with EOS Jellybean builds. Yes, the Xoom wifi did get the JB OTA update, but stock JB is nowhere near as great as the EOS nightlies. They have tweaked it to capacity. The same will happen with the TF700 in time, I hope.
I also have the Nexus 7 and it's true that development has exploded for it, but honestly, it's a really limited device. For that reason, devs are in a performance competition...pushing things to the max. The TF700 though needs to be able to work really well...we'll need to be able to find the balance between high performance and stability. The fact that it's not really skinned is in its favor. It's not a Nexus device though and so some devs will not be interested in working with it.
Part of the problem in developing custom roms - which I have been doing for the Galaxy S 2/3 - is that currently you cannot decompile/recompile the SystemUI.apk file for the TF700T. XDA user iBotPeaches has taken over development of the apktool (tool to decompile/recompile APKs) project and is aware of the problem I and others are having. He is working to fix it.
As soon as it is fixed, I will be releasing a custom rom for the TF700T, but I need to make changes to the SystemUI.apk file. I can decompile/recompile the framework-res.apk file (have added CRT OFF effect already - and it works better than on my Galaxy S3).
So please have a little patience while the development tools are fixed and improved.
One other point to consider is that the Jelly Bean update is right around the corner, so putting much effort into modifying the current ICS version or actually making Jelly Bean work on the tablet is a waste of time.
Link to article is below.
"Amid the mad rush to buy new iPhones this week, Android was still in the headlines. Perhaps the biggest news was in regards to CyanogenMod (CM): The group behind the custom Android software is now an official company and may have its first hardware partner.
Not familiar with CM? Most mainstream Android device owners probably aren’t and they’re missing out. CM has long been a great software option for those that want what may be an even better version of Android than Android itself. The small group of developers behind CM have made their custom software available for at least four years. So why isn’t CM software on mainstream phones? Users need to have root access to their handset; something that most people have no idea how to gain, or even know about.
Still, in the overall market — particularly with Android enthusiasts — CM has a solid base: It’s estimated that more than 7.5 million Android phones run the software with its custom improvements over native Android. And why not when CM offers features such as performance boosts due to CPU overclocking, better custom theme options and support for FLAC audio files, to name a few.
CM raised $7 million in venture capital this week and one of the easiest ways it can boost usage of its software is to make it easier to install. That’s exactly what the new company plans to do. Instead of a multi-step process that requires a computer to install CM, the company is working on an app for the Google Play store that will do all of the hard work.
It would also help CM if phones were launched with its software and it appears that may happen next week. Oppo’s N1 could be the first handset partner for the young company. An announcement is planned for September 23 and based on a teaser video, it appears a version of the N1 will ship with CM pre-installed."
http://gigaom.com/2013/09/21/android-this-week-cyanogenmod-is-a-new-company-while-ol-hp-has-new-slates/
Looks like it's not all sunshine and rainbows.
https://plus.google.com/106978520009932034644/posts/L8FJkrcahPs
Yeah, I read about the corp thing a few days ago on Facebook.
Not sure how I feel about it.
What will it mean to all the awesome AOSP ROM's produced around here that are based off CM's code.
But, I do hope it means I'll eventually get to use an AOSP ROM with the APT-X bluetooth codec. It's the only thing CM doesn't have, that I really, really want.
Anyways, anytime a new company is formed, there will be moral mistakes made and also some pretty awesome things should happen. So give CM time to make and fix mistakes, and then get settled in as a company.
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
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.