Skip to main content

Why the color of battery icon is yellow on my iPhone?


Most of the iPhone user may encounter with this problem. Since whenever your battery goes below 20 %, a pop-up menu appears and asks for activating "Low Power Mode". At first, you find this proposal logical and activate "Low Power Mode".

Figure: Low Battery pop-up window appears

When this pop-up window appeared, color of the battery icon is  red. If you choose Low Power Mode on the screen, then color of the battery icon will be yellow. 


The scenario goes like this:
1- Battery level goes below 20% and a pop-up appears asking for "Low Power Mode"
2- You activate "Low Power Mode"
3- You plug in your phone to charge it.
4- You are in hurry or you do not have time and you plug out your phone before 80 % level.
5- After a while you recognized that color of battery icon is yellow!!! "OMG there is a problem with my battery".

Since color red means "WARNING", color yellow means "CAUTION" and color white means "ADVISORY" in general use, you will be naturally cautious about this yellow sign. But, don't worry. You are at the right place for the solution. Yellow battery icon is not a bug/failure but a feature of iOS.


  • Open "Settings" App by tapping on it.

  • Tap on "Battery"


  • Switch off "Low Power Mode".
As you see in the below picture, Low Power Mode is ON and color of the batter icon is YELLOW.




Switch off Low Power Mode, then you will see that color of battery icon is no more yellow as shown in below picture.



In the scenario mentioned early in this post, if you wouldn't perform 4th step (do not plug out before battery level is 80 %) you would have never seen the yellow battery icon. Since, after 80% battery level, Low Power Mode is automatically switched off by iOS. For more information on Apple's own page, please click here. 

NOTE: iOS 10.1.1 is used throughout the steps of this post.





Labels:

Comments

Post a Comment

Popular posts from this blog

Star Wars ASCIImation with Python - Windows

In this post, we'll watch a Star Wars movie in ASCII format. The only thing we need for this demo is Python-installed PC and internet connection. Figure : Screenshots from Python Command line while Star Wars is being streamed All credits gained in this demo will go to " blinkenlights.nl " [2] website, which broadcasts this ASCII movie using Telnet protocol on Port 23, and Python which makes socket implementation very easy for us. No authentication is needed for this broadcast. Anyone who is able to create a TCP socket and listens  blinkenlights.nl  on port 23 would be able to get this stream and display on their Python command line. CODE My main source for Python source code is [1]. What  code below does is simply importing Python "socket" library, create a socket, use " towel.blinkenlights.nl " address variable to create connection, receive data from socket and display it. While typing (copy/paste) code, be careful about indentatio...
Post a Comment
Read more

How to setup MongoDB tools to test/develop applications in C#?

In this article, I will be mentioning about how to install MongoDB infrastructure to develop any application in C#. After you have read this article, you will be ready to develop C#-MongoDB applications by following the below instructions step by step. Versions of tools used in this demo: Visual Studio 2010 .NET 4.0 MongoDB C#/.NET driver Version 1.11.0 MongoDB 3.4.0 Robomongo 0.9.0 1- Download MongoDB To download latest version of MongoDB, click here . Below page is opened. According to your Operating System, select MongoDB version and click to " DOWNLOAD ". After downloading, go ahead and install MongoDB. 2- Download RoboMongo Click  here  to download latest version of RoboMongo. As December 2016, latest version of RobomMongo is 0.9.0. To download the latest version, click " Download " button. If you want to download previous versions, click on " Download previous version " After that, select the OS and download RoboMon...
Post a Comment
Read more

STORY: Most Challenging Bug

It was an embedded software running on a specific hardware. Software was consisting of different modules for each task. The functionality that I was testing was related to two different modules which are written by two different developers. Required functionality was not working and test was failing consistently. Then, we debugged the Module-1 with Developer-1, Module-1 seemed to work properly. Then, we debugged the Module-2 with Developer-2, Module-2 also seemed to work surprisingly. Of course, each developer was blaming the other developer for the fault : ) Then I suspected about my own test case and re-reviewed and inspected it again, but test case also seemed as OK. Afterwards, we suspected about the software testing tool and debugged it with the developer of the test tool. Not surprisingly, test tool also seemed to work properly : ). Ooopsss. What is next? The next suspicious guy was the data buses between test tool and the software/hardware. Then we checked data...
Post a Comment
Read more