When Android was horrible: this was the worst of the operating system

When Android was horrible: this was the worst of the operating system

Android was and is imperfect, like any operating system. However, its evolution has been remarkable in recent years, and is that little or nothing have to do with the current versions we use compared to what we had to suffer in its infancy. The age of lag and instability are practically surpassed , although having such a high number of manufacturers it is logical that some ghosts are still alive.

Today, we take a look at the past to remember the worst era of Android . A time in which even the representatives of the high range had a poor performance, and in which the manufacturers did nothing but worsen the user experience of their buyers.

The worst era of Android

The lag as the main representative

While Samsung devices currently have a brilliant performance, a few years ago were all you could not ask a phone in terms of fluency. In this Tolo video we can see how the Samsung Galaxy S3 was unable to keep the S-Voice invoker in the start button without completely slowing down the action of returning to Home , and how it was necessary to walk away by deactivating functions to have a performance relatively optimal.

We have to take into account that we are talking about devices that produced at most 20,000 points in AnTuTu, far from the more than 300,000 points we have reached now . However, the optimization of both the operating system and the Samsung ROM left much to be desired.

When Android was horrible: this was the worst of the operating system

2013 was a golden year for personalized ROMs. There were many users who, tired of the bad performance of their terminals, opted to modify Android completely with a new ROM . Back then the cameras and the audio were not too good, so the loss of some proprietary bookstores was not too much drama.

Samsung was not the only firm with poor performance, and is that the low amount of RAM and the low power of the processors made Android a slow and rough system . We came to find frequencies in the processors of less than 1 GHz, and the most generous mobile did not exceed 2 GB of RAM.

Something that lasted until “two days ago”

These homemade videos are an ode to the most unworthy time of Android

He continued to improve the hardware, but the lag continued. The LG G3 was one of the most flagrant cases in 2014 . A mobile that made the leap to QHD with a panel of dubious quality and hardware that was not able to move the interface. The freezes and lag were its main features, and after coming from the LG G2, considered by many as one of the best phones in history, the blow was even harder.

Nor can we forget the redraw in the launcher , something that incredibly continues to happen in Android devices 1,000 euros-yes, sometimes counted. The terminal is not able to keep the launcher in memory after coming from a heavy application, so it is necessary to render the entire interface again.

Waiting 2 or 3 seconds for our launcher to be functional was customary, and especially with Google Now Launcher. This launcher was able to slow down any Android by moving to its feed screen , lack of optimization that was present and that until recently was still presenting these performance problems.

Nova Launcher acquired the name that it has now because it is one of the few launchers capable of accelerating the device , and that was so poor the optimization of the manufacturers that Nova managed to provide a totally different user experience. A simple launcher!

Versions that came and went

In all the operating systems there have been better and worse versions, but Android had a time when it seemed that it did not seem to have a footing . Android 2.2 and 2.3 were a real disaster and two tragarecursos of care. With 2.3.7 things improved somewhat, especially thanks to CyanogenMod, but it was not a good time for Android.

The arrival of Android 4.0 also brought enough problems . It was a pretty big leap by the system, and the users noticed the consequences. The subsequent jump to KitKat also caused several mobiles to suffer . I remember experiencing the jump from Android Jelly Bean to Kitkat in my Moto G 2013. I won lag and a couple of hours less screen .

We leave this video here of the Google Nexus 5 to remove the bad taste in your mouth.

With Material Lollipop came, and again the lag was present . Lollipop is known as one of the worst versions of our operating system due to poor performance and lack of optimization. From here, things started to improve. Android 6.0 Marshmallow, although it did not sit well with everyone, was considered as a more polished version, reaching its maximum refinement with Android Nougat. In Oreo the remaining details were polished, being currently one of the best versions of Android ever created, and redefined with Android 9 Pie, version of which we are quite proud.

The Holo interface

The Android Holo interface is not something we can be proud of. It is true that it was another time and that tastes are always subject to subjectivity, but in perspective, we do not look at this interface with too much desire. The blue accents had too much presence , the design of the applications left something to be desired, and in general the operation was not too smooth.

With the arrival of Android Material Design finally became at the design level in a reference, leaving behind that era of poorly designed icons, widgets overloaded with ancient sources , and that 3D air that accompanied the entire interface.

Battery drains at rest

When Android was horrible: this was the worst of the operating system

Android has never been characterized as a system with low consumption at rest, although currently the numbers have nothing to do with what we suffered before. Before Android 6.0, our system spent at rest as if there were no tomorrow , so it was necessary the arrival of a system that controlled the second planes.

With Android 6.0 came Doze, although in an inefficient way. The system came to rest only if the terminal was physically stopped , something without too much sense that caused that the consumptions were equally bad. With Nougat Doze was activated more frequently and without the need for the mobile was stopped, but still not the wonder. The developers had to invent alternatives such as Forze Doze to make the system hibernate well.

With Android Oreo things improved, although it has not been until the arrival of the

Our friend forcing closure

When Android was horrible: this was the worst of the operating system

The forced closures are still present in Android, although nothing to do with the frequency of before. In the first versions of Android rare was the week in which we did not close an application . Luckily, with the passage of time, the system was stabilized and little by little we forgot the forced closures.

An even greater fragmentation

When Android was horrible: this was the worst of the operating system

If now we complain about fragmentation, what was before had no name . The big manufacturers took about 6 or 7 months to update, and this was seen as normal. The worst thing is that in many current cases it is still that way , although it seems that little by little this improves. The high end of the year finally comes with the latest version of Android – something unthinkable last year – and everything points to the pace of updates – at least in the high range – will continue to increase little by little.

Follow us on” to find out about the highlights of day and best android offers>

Facebook Comments