₦airaland Forum

My machine

E3 on point.

Waiting for Hope

crap! I got my Gionee E3 for 34k and I have not regretted it! a quad core@ 34k when one silly guy wanted to sell s2 to me@ 30k for tokunbo!

if you are planning on buying this fone please by all means do so. this fone is hott!(but not as hot as my new wife if you are planning on buying this fone please by all means do so. this fone is hott!(but not as hot as my new wife

God villa thanks to you and 4peace I for don go buy Samsung Galaxy 2 for 32k but now I have a brand new phone, a quad core, for 34k! now if that's not good value for your money then this planet is not Earth! pls where can I get a working fifa12 apk for this my new wife?

directonpc: hehehe ok na.
Ss

pls does it have an extra battery?

source [url] webdevsys.com/galaxys2-screenBurn.htm [/url]

[url] webdevsys.com/galaxys2-screenBurn.htm [/url]

Samsung Galaxy SII SAMOLED display burn in -
OLED screen persistence, retention S2
It is well known that the Samsung Galaxy S suffered
screen burn-in on its AMOLED (Super Active-Matrix
Organic Light-Emitting Diode) display. The most
prominent area to suffer burn-in (or image retention)
is the status bar. Early models with older firmware
(e.g. Android 2.1) used a grey or white status bar,
causing icons such as the clock and battery symbols
to be clearly burnt in (and becomes very evident
when the phone is showing a full-screen solid colour
such as a grey background).
The Samsung Galaxy S II with its new Super-AMOLED
display, released in early 2011, is yet to yield any
reports on screen burn (as of August 2011) - but then
again, it has been less than six months since its
release. The Galaxy S has been around for about one
year, and thus has had more opportunities for burn-
in to occur.
The SGS2 runs Android 2.3, and by design, has dark
menu bars and a black status bar. The darkness
probably originated from the need to reduce power
consumption on the Samsung/Google Nexus S, which
also features an AMOLED display.
Ways to prevent / reduce screen burn-in
You can mitigate the possibilities for screen burn in by
adhering to these simple rules:
Always try to set the display as dark as practical.
Running the display at full brightness will aggrevate
the potential for burn in. Organic LEDs, especially the
blue ones, tend to degrade in brightness more rapidly
when display intensity is increased.
Disable the auto-brightness. Quite often, an AMOLED
display set to low brightness is more than bright
enough for nearly all indoor environments, and there
is little or no need to increase the brightness. When
outdoors, you can easily increase the brightness on
the SGS2 by holding and sliding on the status bar
(which acts as a hidden display brightness slider). Just
remember to slide it back to dim when you no longer
need the added brightness.
Set a shorter display time-out. A 30 second or 1
minute timeout is very effective at reducing the time
the screen is 'on' when the phone is idle. Only set a
longer time-out (such as 5 minutes) when you really
need it, although such occasions should be rare.
Use dark wallpapers. A solid black wallpaper is even
more effective. The other upside to having dark
wallpapers is that it saves battery power. Organic LED
displays don't use a constant backlight (such as with
LCDs), and will actually consume less energy when
showing a dark image. If you must use a non-black or
other artistic/photographic wallpaper, change them
every once in a while so the same image isn't
constantly being displayed.
Try not to show static content. This applies especially
to the home screens. Change or re-arrange your
icons and widgets so nothing is ever constantly in the
same place more more than a few weeks at a time.
Try not to expose the screen to strong sunlight.
Organic LEDs will break down and degrade rapidly
when exposed to ultraviolet light. Fortunately, the
glass covering on the phone stops most of the UV
from direct sunlight, but the heat and light can still
cause some degredation.
Occasionally change the way icons appear on the
status bar. This can be as simple as changing the
clock format from 12-hour (AM/PM) to 24-hour. When
in 12-hour format, the AM/PM symbols don't change
much and pose a real risk to burn-in (particularly the
'A'). By switching to 24-hour format, the AM/PM
symbols are not shown, and the digits of the clock
actually get shifted to the right to take up the space
originally occupied by the AM/PM. This has the side
effect of shifting other icons that constantly show,
such as the battery status. If you do this every month
or so, it can be an effective way to prevent burn-in on
the status bar area.
Install the Screen Filter app. There is an application
by that name on the Google Android App Market.
Screen Filter allows you to further dim the screen
below the minimum available setting via the normal
means. It will also help to further reduce power
consumption on (S)AMOLED screens. Dimming the
screen can make it easier on your eyes when using
the Galaxy S / SII at night, because even the normal
minimum settings can still be blindingly bright. It can
even dim the screen until it's completely black if you
want, but they say if that happens accidentally, the
app will need to be uninstalled (e.g. via Kies) to
restore the brightness.
Diagnosing screen burn or image persistence
You can activate the diagnostics on the Galaxy S2 by
keying in *#0*# into the dialler keypad. A menu will
appear, and there are buttons to fill the entire display
with red, green or blue. With a solid colour being
displayed, you should be able to discern whether
screen burn has taken place or not.
You can also create an image on your PC with a dark
or solid grey colour. The image dimensions should be
480 x 800 pixels. Save it as a GIF or PNG and copy it
to your phone, and display it using the gallery app.
Using the same technique, you can create a solid
black wallpaper to use on your home screen and/or
lock screens.
Temporary image persistence
It has been noted that after displaying white text and
certain icons for 30 seconds to a minute, then
switching to a different image or menu, a very faint
shadow imprint of the previous text/icons can be
seen. This seems to be normal and the persistence
will gradually go away after 20 to 30 seconds. It can
be unsettling at first, but reassuring once the imprint
dissapears.
SAMOLED display technology still in its infancy?
Commercially available organic LED displays have only
been around for about half a decade, and high-
resolution OLED smartphone displays for only a small
number of years. Unlike LCD technology, which has
had more than 20 years of perfection, organic LED
displays still have a long way to go. The fact that they
use 'organic' dyes and semiconducting materials
means they have a limited lifespan. No one really
knows just how long these displays will last. On the
other hand, LCD displays manufactured 20 years ago
are still going strong.
What can you do about it?
Unfortunately, not very much, apart from the points
listed above. LED displays have a lifetime that
specifies the time to half brightness (similar to the
half-life of radioactivity). The light output will gradully
become dimmer the more the display is used. So,
things such as the clock and battery symbol will cause
the areas of the screen they occupy to reduce in
intensity, thereby leaving a sort of a darkened
'imprint' when the screen is showing a solid colour
when the said icons are not displayed. Hopefully, the
time to half brightness will be much longer than the
useful lifespan of the phone itself. This may not
please some purists and those who like to hold onto a
handset for a long time, but is an unavoidable fact of
this new display technology.
Unlike LCDs, OLED burn-in cannot be 'washed out' by
displaying a complete white screen for an hour or
two. A white image on an LCD causes the crystals to
relax, thereby alliviating the problem of image
retention when showing constant items such as
desktop icons or status / task bars. But on an OLED
screen, a white picture will cause more wear and
degredation of the light emitting diodes.

cahnellven: if u nid an android phn dat wnt give up on u after 3mths,pls desist 4rm buying any phn wit mediatek and atm cpus. Dia gpu is too weak to power android for long ,n dia cortex a7 architecture can hardly get d job done

see this one? how many CPU have you built? what do you even know about GPUs. My advice to you is to always put milk in your garri. It improves brain function.

Emrich: One advice to anyone that might consider buying a used phone. Just make sure the screen technology is not an AMOLED Display or you will hate yourself when you place it side by side with the new one of the same phone or even a used phone with LCD Display. This is because Amoled (put quite simply) expires in about a year or two. And when it does expire, watching anything on the display will be frustrating. This is what happens to all the used Samsung android phones in this country.



So if you will heed my advice I will suggest you go for new Tecno, Gionee or any other China Android phone instead of buying second hand phones with Amoled display. Or you buy Sony, they don't use Amoled, or LG, or Blackberry Z10.



But if you have the cash and you are certain you won't use the phone for more than two years then pick up a new Samsung phone and you will see how graceful Amoled can be when it's new. Remember the key words, "cash" "new" and "not more than two years"



So my friends do not just rush into the second hand market.

you could have said it better

how do I get the htc sensation battery im in Awka

we must make front page!!!!!!!!!

^^
guy thank you so much.

Front Page!!!!!!!!!!!!!

pls o someone should please tell me how much i can get a UK used HTC amaze Abeg Na beg i dey beg

Joel.:
for me i will prefer htc. for strongness. last like forever.

yeah they build them strong but reviews say the battery life is below average. Don't know how true that is.

pls o oga sheelay where and for how much can i get the Samsung Galaxy exhilarate? that is uk used.

i want to get a phone but i can't make up my mind between the HTC sensation and Samsung Galaxy exhilarate which should i go for . Considering battery life and developer options . if there is any phone you know that is better than these and not more than 26k please suggest.

bush4ker: HTC t mobile g2 v2.3.4 was my previous version.I sold it and bought another g2 with froyo 2.2 cuz rooting dat ur version is very difficult.u have to downgrade to 2.2 in oda to root.that really takes u to adb stuffs nd trust me its really difficult.u could even brick ur phone .but if u insist search for how to root HTC g2 with ota update

that was before one click root came in to the scene

benatex: hello guys the pictures on my N3 are not sharp anymore.. i mean all. also some coloured lines r on d screen in the gallery. Any talk or help on this,see my screenshot. mind you i didnt say my camera is not sharp,i said my pictures r not sharp

u have chain fire 3d installed go and revert back the settings you changed.

adeinfinit: Pls guys. Dnt knw wats wrong wit my g2.it unmounts d mem card by itself... Any idea guys?

I guess you are using that fucke d up slim bean ROM you better port to mimicry because that ROM is not it . drains battery like mad!

FRONT PAGE!!!!!!!!! ¡

You don't needto do all those nonsense written up there just send BBUD3 . It's a 2 for one offer

Good one there

hope to come onboard very soon

Abeg how can i root this fone PO I'm currently on 2.34 gingerbread but they say i must downgrade to 2.2 before i can root it also have you heard Of this .Slimbean Rom it's jellybean and i heard its quite stable too [ROM][4.2.2][June 2] Andromadus Slim Bean [build 6] - xda-developers - [ROM][4.2.2][June 2] Andromadus Slim Bean [build 6] - xda-developers http://forum.xda-developers.com/showthread.php?t=2307304

Abeg how can i root this fone PO I'm currently on 2.34 gingerbread but they say i must downgrade to 2.2 before i can root it also CODE EATER have you heard Of this .Slimbean Rom it's jellybean and i heard its quite stable too [ROM][4.2.2][June 2] Andromadus Slim Bean [build 6] - xda-developers - [ROM][4.2.2][June 2] Andromadus Slim Bean [build 6] - xda-developers http://forum.xda-developers.com/showthread.php?t=2307304