Related
Why is it not possible to "just" install latest Android on entry-level phones
I'm just curious, given that android has a linux kernel ( although modified ).
Why is it not possible to just download the latest android os and install
it on any 600+ Mhz 256+ Mb ram entry level phone.
I understand that it takes forever for phone companies ( samsung, htc, etc )
to issue updates because they have to tailor a lot of custom signature
bloatware for their updates, which in some instances makes it not possible
to provide updates on older phones.
But for a pure vanilla install, I just don't see why Google or the Android
division can't release the base OS that people may install on the fly, never
mind if it wipes everything out. I know for a fact that the latest ubuntu / linuxmint
can be installed on hardware from over 5 years ago, with less than 10%
of the current high end specs; this ( for me ) makes android landscape
rather confusing... and quite deceptive.
It as alot to do with the different drivers each device.uses for the radio, screen, touch button and so on.
You have to take into account device-specific drivers, hardware, and a lot more. Imagine if every time a new version of Android was released, devs would have to prepare for every possible legacy chip, and new ones. Android would be a huge, bloated mess. It just isn't feasible.
Plus, from a carrier/phone manufacturer point of view, if you could just get the latest features by installing a simple update, than what would be the incentive for you to buy a new phone?
Hopefully this is a semi-helpful explanation (I'm sure I've left out some stuff that some others will add).
@closeone, I don't see why this can't be feasible. this is exactly what linux distributions already do, release new versions and still provide support for old devices.
I can understand the carrier/phone manufacturer perspective, it is what it is.
But what i don't get is why android development can't provide complete support, for at least the devices released from a year ago. At some point, these devices still
have to comply to certain standards;
Ultimately, I'm getting the impression that Google is starting to expect the users to throw away their smartphones year in and year out.
prokofiev said:
@closeone, I don't see why this can't be feasible. this is exactly what linux distributions already do, release new versions and still provide support for old devices.
I can understand the carrier/phone manufacturer perspective, it is what it is.
But what i don't get is why android development can't provide complete support, for at least the devices released from a year ago. At some point, these devices still
have to comply to certain standards;
Ultimately, I'm getting the impression that Google is starting to expect the users to throw away their smartphones year in and year out.
Click to expand...
Click to collapse
No you can but like Linux it takes some work to get proper drivers and hardware features. The Android OS is a developer based platform. So it can be done. Look at CM they do it just fine. It is alot of work though
ok, I'll concede that it takes time and effort to achieve this goal. Still,
I'm inclined to think that a huge company like Google behind this platform,
they can do for android what Ubuntu, Debian, etc. do for Linux.
prokofiev said:
@closeone, I don't see why this can't be feasible. this is exactly what linux distributions already do, release new versions and still provide support for old devices.
Click to expand...
Click to collapse
You would have to get all the different device manufacturers in the world to not only release their proprietary driver code but, for a standard one for all rom, include all possible drivers in it.
Linux comes on discs and can afford to use lots of space for drivers that a basic phone could not.
Dave
Sent from my LG P920 using Tapatalk
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
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
Does it mean it will be easy to compile AOSP, so that the original Pixel can get essentially stock OS updates for years, and get them quickly, eliminating an advantage of the Pixel 2? Pixel 2 is to get three years of OS updates, compared to only one more year of official OS updates for the Pixel.
Will it really make OS development much easier?
foosion said:
Does it mean it will be easy to compile AOSP, so that the original Pixel can get essentially stock OS updates for years, and get them quickly, eliminating an advantage of the Pixel 2? Pixel 2 is to get three years of OS updates, compared to only one more year of official OS updates for the Pixel.
Will it really make OS development much easier?
Click to expand...
Click to collapse
There's no reason to believe the Pixel 2 firmware will have any compatibility with pixel 1
sd_shadow said:
There's no reason to believe the Pixel 2 firmware will have any compatibility with pixel 1
Click to expand...
Click to collapse
I had thought the idea of Treble was to present a standard interface between hardware and the OS, to separate the device-specific, lower-level software written in large part by the silicon manufacturers from the OS.
"Malchev says that Treble standardizes Android hardware support to such a degree that generic Android builds compiled from AOSP can boot and run on every Treble device. In fact, these “raw AOSP” builds are what will be used for some of the CTS testing Google requires all Android OEMs to pass in order to license the Google apps—it’s not just that things should work, they are required to work." https://www.xda-developers.com/project-treble-custom-rom-development/
Doesn't that mean someone can just compile the latest AOSP build and it will run on a Treble Pixel 1? Don't the current Nexus and Pixel phones essentially run AOSP, but have to be modified to work with the specific hardware, modifications that won't be necessary with Treble?
Or is this the issue: "You won’t be able to boot up flawlessly-working generic Android 9.0 builds on your Treble device just yet, though – device trees and kernels will still require being worked on."
foosion said:
I had thought the idea of Treble was to present a standard interface between hardware and the OS, to separate the device-specific, lower-level software written in large part by the silicon manufacturers from the OS.
Click to expand...
Click to collapse
that's the general idea, but afaict, it's not there yet and not for the pixel 1
foosion said:
"Malchev says that Treble standardizes Android hardware support to such a degree that generic Android builds compiled from AOSP can boot and run on every Treble device. In fact, these “raw AOSP” builds are what will be used for some of the CTS testing Google requires all Android OEMs to pass in order to license the Google apps—it’s not just that things should work, they are required to work." https://www.xda-developers.com/project-treble-custom-rom-development/
Click to expand...
Click to collapse
I didn't read your link, but I did watch the linaro talk from a week or two ago about... The vendor test suite (VTS), is to be used to have aosp be bootable on XYZ SOC, as the idea is to keep all of the vendor blobs outside of aosp / the core of android.... in practice though, even with the pixel, it still isn't 100% like that. ROMs like LOS are still pulling vendor blobs and baking them into their build system....
foosion said:
Doesn't that mean someone can just compile the latest AOSP build and it will run on a Treble Pixel 1? Don't the current Nexus and Pixel phones essentially run AOSP, but have to be modified to work with the specific hardware, modifications that won't be necessary with Treble?
Or is this the issue: "You won’t be able to boot up flawlessly-working generic Android 9.0 builds on your Treble device just yet, though – device trees and kernels will still require being worked on."
Click to expand...
Click to collapse
who knows about android 9.0, but it doesn't work for Oreo and the pixel 1... Nexus and Pixel run aosp with a bunch of Google's tweaks from their own internal android tree + all of the google services and apps... I'm sure there is a reasonably sized set of patches / Delta between aosp and Google's own builds.... but obviously, google provides a very 'vanilla' version of android.
foosion said:
Pixel 2 is to get three years of OS updates, compared to only one more year of official OS updates for the Pixel.
Click to expand...
Click to collapse
Independent of the discussion here regarding Treble, the original Pixel is getting updates for the same duration (from release) as the Pixel 2.
Both devices will get 2 years of Android version updates, and another year of security updates.
https://support.google.com/pixelphone/answer/4457705
The original Pixel will get android version updates through October 2018, and security updates through October 2019. The Pixel 2 will get updates for one year longer simply because it was released one year later, but no additional promises have been made for the Pixel 2.
Fairly sure Pixel 2 is getting 3 years of OS updates which is probably a result of Treble. Google want to show off how easy updates are now so it wouldn't be good if they drop support after 2 years still.
As for the first gen Pixel, I don't believe our devices support Treble.
Edit: sorry, looks like first gen Pixel does support Treble. My bad.
surrealjam said:
Fairly sure Pixel 2 is getting 3 years of OS updates which is probably a result of Treble. Google want to show off how easy updates are now so it wouldn't be good if they drop support after 2 years still.
Click to expand...
Click to collapse
I'd love it if Google extended the support period for their devices. And I could be wrong, but I'm basing stuff from this page:
https://store.google.com/us/product/pixel_2_specs
Under the "Safe and Secure" section, they state "Security updates for up to 3 years".
Farther down on the page, in the tech specs section, they say:
"Minimum 3 years of OS and security updates" and "Pixel’s software and security updates for three years. See website for details." And the website reference is the FAQ page that I linked to above. That page states:
"Pixel phones get Android version updates for at least 2 years from when the device first became available on the Google Store. After 2 years, we can't guarantee more updates." and "Pixel phones get security updates for at least 3 years from when the device first became available on the Google Store, or at least 18 months from when the Google Store last sold the device, whichever is longer. After that, we can't guarantee more updates."
Again, it'd be great to see these phones official support period be extended. But from what I can tell, Google is sticking to 2 years of OS updates + another 1 year of security updates. Even with Treble support.
jss2 said:
I'd love it if Google extended the support period for their devices. And I could be wrong, but I'm basing stuff from this page:
https://store.google.com/us/product/pixel_2_specs
Under the "Safe and Secure" section, they state "Security updates for up to 3 years".
Farther down on the page, in the tech specs section, they say:
"Minimum 3 years of OS and security updates" and "Pixel’s software and security updates for three years. See website for details." And the website reference is the FAQ page that I linked to above. That page states:
"Pixel phones get Android version updates for at least 2 years from when the device first became available on the Google Store. After 2 years, we can't guarantee more updates." and "Pixel phones get security updates for at least 3 years from when the device first became available on the Google Store, or at least 18 months from when the Google Store last sold the device, whichever is longer. After that, we can't guarantee more updates."
Again, it'd be great to see these phones official support period be extended. But from what I can tell, Google is sticking to 2 years of OS updates + another 1 year of security updates. Even with Treble support.
Click to expand...
Click to collapse
I take your point. I was hoping they just hadn't updated the support page as it doesn't list the Pixel 2 yet. But you may be right.... the tech specs section is badly worded and may be misleading.
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.