Skip to main content

The secret life of the OnePlus 3




So I bought the OnePlus 3 on launch day; it has been about a week since. Buying products on launch day is a practise I am personally against and don’t recommend, but end up falling for more often than not. More comprehensive reviews and bugs surface only after a few weeks from the public release; this time however, things were a little different. Reviews by both The Verge and MKBHD were released as soon as the launch event ended. For me, reviews by The Verge are nothing more than in-depth first impressions. It seems as if they don’t really use the phone as a daily driver or even for more than a day but instead they have some really talented people who produce great content and sometimes catch things that others don’t in the first go. MKBHD on the other hand has always been very reliable- he uses each phone as his daily driver for at least a week before publishing a review. The OnePlus3 got rave reviews by both and was marked to be nearly perfect.
The interesting bit however is that OnePlus 3 has been secretly leading a life which both of them failed to discover. This life has two aspects — the display and the RAM.
Let us first talk about the display. Switching from the iPhone 6S, I was very excited to move to an AMOLED panel. It meant that colours would pop and contrast ratios would be way better. AMOLED panels are also famous for looking good but not caring much about accurate colour reproduction. Knowing this, I gave my eyes time to settle to the new display even though I was immediately thrown off by the colours at certain places, for example, the emoji panel. The emojis looked pale and generally under the weather. I tried to tinker with the settings but nothing really helped much. Digging deeper I found out that the panel on this phone is actually a Pentile AMOLED. A pixel should ideally have 3 sub pixels one of each red, green and blue colours. A Pentile display however uses an alternating green sub pixel between red and blue, leaving the effective chroma resolution to be way lower than 1080p that too on a 5.5inch display. Now this is less of a problem if you aren’t switching from super high res phones like the Galaxy S6 or S7. To top it, OnePlus has made it worse by moving to an extremely high blue tone which cannot be modified. There is no RGB setting to play with and hence no way out. I fail to understand how this went unnoticed by almost all major reviewers out there. Again to most people this would not mean much and go unnoticed because the display is not washed out nor does it have especially poor viewing angles. I have realised that I can still tinker with it by using the night mode which adds a yellow tint to the entire screen.
Now the second aspect feels clearly like a big stab in the back once you discover it after buying. This phone has 6gb RAM which is a major attraction for a power user like me. I like to keep everything on memory and never really force close apps. This is usually a big problem for the OS and it will force apps out once it runs out of memory. But with 6gb RAM, I thought my life was sorted. Turns out OnePlus has not only implemented an extremely harsh memory eviction algorithm but there is also NO WAY to utilise all of its 6gb memory. So basically around half of your total RAM will just sit there doing nothing. This technically improves the battery efficiency of the phone but makes me super sad and not feel like talking to anyone. This does not mean the phone is in any way really slow but it is just not what it is sold to be.

Comments

Popular posts from this blog

Nouveau - Summer Project

Implementing a software scripting engine on Fermi to achieve safe memory re-clocking. Fermi stands for Nvidia GPUs based on Fermi architecture. NVidia cards have long had the possibility to reclock at least some of the engines of its GPUs. Up to the geforce 7 (included), reclocking used to happen at boot time and usually didn't involve memory reclocking at all. It changed with geforce 8 (nv50) where almost all laptops got the capability to reclock both the VRAM and the main engines. This was introduced in order to lower power consumption when the GPU was mostly idle. The default boot clocks were usually in some intermediate state between the slowest and the fastest clocks. The reclocking process for these cards is mostly understood and Nouveau is not far from being safely reclock on the fly, even while gaming. Geforce 200 (nva3) introduced load-based reclocking on all the cards. This started being a real problem because the default boot clocks are a third to a half of the

uCharts - Financial Charting API

A few months back, the first stable release of the charting API, that I have been working on was released. A part of the uTrade product portfolio, it has been aptly named uCharts. uCharts is a general purpose charting API with prime focus on financial markets and data. In this post, I will give a brief overview of the features, compatibility and scope of extensions. Features The API currently supports 6 types of charts: Line Area CandleStick OHLC Bar Pie It has been designed in a manner that all aspects of the charts are user defined. Starting from the color of the charts, width of the candle bars till the number of ticks on each axis. Mentioning each element seems like a futile exercise. However, brushing over a few notable features seems more fruitful. Aggregation Formula The number of data points that can be displayed on a screen or inside a DIV is limited by its resolution. The number of pixels available can lead to a severe limitation especially

Two concepts to help upgrade our definition of science

Two concepts to help upgrade our definition of science.  Everybody agrees that there are a ton of things which people believe in to have some basis in science but don’t. This agreement is however limited to what somebody else believes in and not they themselves. Applying the scientific method to everything that we come across is not possible. We as individuals have neither the resources nor would our experience as a single data point count for anything more than an anecdote. There are two concepts to help us check if what we believe in would even qualify to be evaluated by the scientific method. The first is “correlation does not imply causation”. Just because two things are found to be correlated, it does not mean one is the cause of the other. The more popular version of it is a similar fallacy, an event that followed another was necessarily a consequence of the first event. For example, you bought a car on a Saturday and then later met with an accident. Drawing a conclusion th