Smartphone manufacturers have set a two-year time frame for its devices to take on mobile operating system updates. While there is no rule that set everything in stone about this, the reason why the device makers have set an allowable period to update the OS of their devices is to ensure that the smartphones can still perform reasonably well.
As everyone knows, every OS update usually gets bigger and bigger as far as file sizes are concerned and an older smartphone can only take so much before it practically pukes and can no longer handle it.
That seems to be the case with the very popular Samsung Galaxy S4, the flagship smartphone of the Korean tech giant in 2013.
As the smartphone is already close to three years old, Samsung has confirmed in November last year, just weeks after Google officially rolled out the Android 6.0 Marshmallow updates, that the Galaxy S4 and that Galaxy Note 3 will not be receiving the new OS anymore, reports Tech Times.
Why Android 6.0 Marshmallow is no longer coming to Galaxy S4
Apparently, Samsung has a good basis for no longer allowing Android 6.0 Marshmallow updates to the Galaxy S4.
It turns out that the device has been suffering from sub-par performance when it took in the official Android 5.0 Lollipop updates last year that taking on further upgrade would have a telling impact on the performance, functionality and usability of the device.
As a matter of fact, one Galaxy S4 user stated in an online public forum that immediately after he took in the Android 5.0 Lollipop update last year, his smartphone started to crawl. He said that he used to open his e-mail in two seconds but with the Lollipop update, the procedure has gone on to as much as 20 seconds.
The user also complained that the map has been completely hosed. He also finds it difficult to navigate the length of his street, about one-fourth mile, without crashing the whole phone. He also added that the update has seemingly bricked his phone, notes GSM Arena.
He added that he could have just bricked his phone if he knew that the update would practically slow down his handset.
Being creative
The Korean tech giant has officially approved Android 5.0 Lollipop updates to its Samsung Galaxy S4 smartphone and that was it.
So any update beyond Android 5.0 Lollipop is already in the realm of third-party developers who like developing custom ROM based on the latest OS updates.
Many third party developers are already expected to come up with an Android 6.0 Marshmallow-based custom ROM on Samsung Galaxy S4. However, users should actually be wary about taking the updates right away because it will have a major impact on the operating system of their devices.
If Android 5.0 Lollipop updates have been despised by a number of Galaxy S4 users because it had a negative impact on the operations of their smartphones, taking on an even bigger update like the Android 6.0 Marshmallow would perhaps brick their phone altogether.
The mobile OS of Samsung Galaxy S4 has been officially updated by the Korean tech giant up to the Android 5.0 Lollipop which it made early last year, or a few months after Google officially rolled it out in November last year.
Considering how popular the Samsung Galaxy S4 is and the millions of users holding on to the device even if it is already more than two years old, XDA developers immediately recognized the need to update it to have the latest OS.
Thus, even when Samsung no longer released an official update after Android 5.0 Lollipop, a custom ROM based on Android 5.0.2 Lollipop and Android 5.1 Lollipop were developed and released during the year.
But the custom ROM updating of the Samsung Galaxy S4 has not stopped with the Android 5.1 Lollipop as a new custom ROM based on Android 5.1.1 Lollipop was developed early in December.
The custom ROM is called OrionLP and it has become available and ready for installation to Samsung Galaxy S4 bearing the model number I9500.
Page 1 of 212»
Like 2 Tweet Share 0 Share 0 Share 0 Source: Samsung Galaxy S4 will be Too Tedious to Operate if It Takes on Android 6.0 Marshmallow-Based Custom ROM!
No comments:
Post a Comment