Ok, so there are quite a few threads about colour banding, 4 or 5 I think. All/most saying different things, sometimes the same things in different ways
Neways, although I really didn't want to add to it, I wanted to show everyone a few things about android colour.
Note: In order to really do these tests you need to set brightness to 100% so there is a common mark from which to draw any conclusions.
I believe the following:
1. It's apparent that super duper amazing amoled plus and then some Shows more detail (maybe due to sub pixel processing nature of the screen).
2. Due to point 1. and added to the fact that by default and quite often chosen by developers that most apps are set to use the 565 mode (5bits red, 6bits green (human eye sees more green) 5bits blue) or 16bit mode for performance reasons. With this we see banding in some colour transitions (More so green)
3. There are many bitmaps/images/textures that have been palletised in conversion and compressed for in-app performance reasons. This also produces artefacts that can be seen on our wonderful displays
So in collusion to those points it quite impossible to say banding is a software problem or hardware problem unless:
1. You wrote the app yourself and have forced the 888 mode.
2. You compressed the resources (bitmaps etc) yourself and know that they should be perfect while also doing point 1.
(NOTE: you cant just use a browser or image viewer to look at an image and say well that shouldn't look like that without thinking about all of the above!)
Ok so how do we look at these things?
Well 1st off, I'm doing an nice app with a theme framework that uses lots of bitmaps for the default theme, so I put in the ability to change from 16 to 24 colour modes, so I can allow users to pick from SPEED or LOOK preference! This shows how both the SGS2 and TAB7 can have banding on a drop shadow, or not:
View example (View the 720p)
Sorry about audio, couldn't be arsed setting up a proper studio mic!
Also sorry about the blur box I HAD to use
http://www.youtube.com/watch?v=8QlnuoNSdXo
OK so a few other tests on your own device
Test 1. UPDATED
Using the attached bandingTestUPDATED
Ok altered this little thing to show 2 photos I took, one of mighty mugs Prime!!! and one of a robin! The app forces 888 mode and allows you to switch images with settings/menu button. It displays at 100% so you cant zoom out or in, you can just view as is. For comparison these are the images in use :
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Test 2.
Using the attached xda-gradtest
This is an app that is set to 888 and uses procedural gradients rather than bitmaps (as in the gradient is program generated rather than image based).
What you should see is only very slight banding in low greens due to our eye being very very very good at green colours compared with blue and red. There should be little or no banding on anything else.
More Info / Conclusion:
Well the gradientTest app is the best thing to look at, and the real test, the reason we see more banding on low green is 2 reasons.
The first:
Well we all see sh*t loads more green than any other colour (cause were ace) I recommend you look into human eye perception theory regarding both colour and detail perception as I have had to do over my many years in game console art development (wicked reading ).
Second:
I believe oled screens are not as good as others at low intensity low contrast due to the nature of how colour is processed.
I have many android devices ranging from the crappiest tablets you can buy of ebay, up to the best and even have iphone ipads also. I must say that with a finite gradient in 565 on the crap tablets and lesser displays, it looks better cause they are actually crap (dithered and filter to hell)
The same is true of this display I'm typing on now compared to another I have on my mac pro. One is an IPS pro colour variant of an LCD panel and one is not. Crap looks better on the lesser monitor! But Amazing looks amazing on the IPS pro panel that I HAVE to use for my 3D Graphics, Photography and Video work.
more..
If you plan to use apps that are set to 565, you have to deal with the banding or get a lesser display that just doesn't show it!
If you plan to use lots of apps (24bit)(888) that use low contrast dark green to black transition graphics, you will have to deal with the gradient banding
Alternatively
You could wait till the average target device has a minimum spec like the sgs2 and also a min OS of 2.3.* then probably most apps will have higher colour set and higher fidelity resources (bitmaps etc) in use But as it stands the mass market is much lower spec and the dominant os version is a mix of 2.1 and 2.2 devices
New info
previous to some 2.2 and all 2.1 android os defaulted to low colour if a developer didn't set it. Now in 2.3+ it defaults to high colour if they dont set it.
UPDATE 14 June
As some have mentioned (godutch etc) dnie (Digital Natural Image engine) by samsung is a colour/image processor that could be in use. Having looked at test 1 with the images, there is hardly any banding at all, but just a tiny bit I can see in primes left window. With this in mind and only mildly pissing me off, started to look at ROM and found many different " mdnie_profiles " that are apparently used and have different settings in each profile relating to all the major visual aspects (video, gallery blaaa blaaa)
So gonna have a play (these are in /etc/mdnie_* ) but I dont reccomend ne1 doing this unless you really know what your doing.
SO....
Hope this helps kill lots of thread activity on the same subject across multiple threads where info is getting hard to find and peeps just cant read all of those posts.
As always due to who I am I will say that I could be in part or on a whole wrong on this to any degree, but I believe this info to be correct as of the time of this post and this is only for the purpose of putting a few peoples minds at ease and also as information that doesn't sit 50 posts into some of these massive threads
Wow! I'm not a techie person like you but the way you explained it I kinda get the idea.. I'm very thankful for people like you who share their knowledge to educate us so we can come up with a decision whether to buy sgs2 or not. I'm looking forward to upgrade my Samsung i8910hd to sgs2 come July, and I'm researching in the forums to check the users' feedback as to their personal experience with their new sgs2.
As said above, I'm not a techie (Not as much as the OP anyway ) though am also grateful for people who post up tech info like this.
To the 2nd poster.... Ignore negative comments given by a lot of users, regardless of whatever bugs may be present, the S2 is an amazing phone and you will not be disappointed!
People are too quick too moan, yet don't talk about the plus sides
Thank you for the time and energy you put in to explaining this. It's sometimes hard to participate in certain technical conversations/threads because there are so many moving parts and so many different theories. This thread is refreshing.
But there's still very noticeable banding on 888. Less than 565 but there still is. So the banding problem really exists.
Sent from my GT-I9100 using XDA App
EleCtrOx666 said:
But there's still very noticeable banding on 888. Less than 565 but there still is. So the banding problem really exists.
Sent from my GT-I9100 using XDA App
Click to expand...
Click to collapse
Read the post and instructions fully, along with expected results!! Cause if your talking about angry birds bg, then I explained that! So no1 knows what your on about unless your precise. I've yet to find a problem with anyones display in this manner, thats not to say there may not be a first, but you have to be clear and read properly, then I would look to do some proper display test apps.
deanwray said:
Read the post and instructions fully, along with expected results!! Cause if your talking about angry birds bg, then I explained that! So no1 knows what your on about unless your precise. I've yet to find a problem with anyones display in this manner, thats not to say there may not be a first, but you have to be clear and read properly, then I would look to do some proper display test apps.
Click to expand...
Click to collapse
I read everything. With Xda Gradtest the green has the banding issue, so yes maybe our eyes are more sensible to it, but that doesn't excuse it & the problem exists, the green banding on a larger scale can be very noticeable.
Sent from my GT-I9100 using XDA App
Well my samsung galaxy tab had the same problem with gradients and it just had a simple lcd display. So I believe the problem lays with samsung as no other device I owned had that issue.
Sent from my GT-I9100 using Tapatalk
I don't know see any banding on my htc desire though, and the gradients look super smooth on it.
godutch said:
I don't know see any banding on my htc desire though, and the gradients look super smooth on it.
Click to expand...
Click to collapse
Cause it dosent have a high colour high detail display like amoled plus, on the galaxy s 2, which is what this thread is for
Sent from my GT-P1000 using XDA Premium App
Thank you deanwray for your work and explanation.
Discussion apart ... what can be done in the firmware (by Samsung) to correct this problem with the actual 16bit "low quality" apps and OS? the OS can be improved, only depends on Samsung, but will we have to wait for the apps developers to give us better IQ in their future releases?
Thanks again!
jvidia said:
Thank you deanwray for your work and explanation.
Discussion apart ... what can be done in the firmware (by Samsung) to correct this problem with the actual 16bit "low quality" apps and OS? the OS can be improved, only depends on Samsung, but will we have to wait for the apps developers to give us better IQ in their future releases?
Thanks again!
Click to expand...
Click to collapse
Well the os supports full 24bit colour with another 8bit for various non-palletized blending modes. Thats just Android, but most of the base functions you see in android are indeed independent apps like phone, calendar, contacts etc.
So the OS is fine.
As for applications, to the best of my knowledge, you cannot force an app to be 24bit mode, but even if you did, as the test app shows with angry birds bg, the source resources (images, textures etc) have to be of a quality that fits.
So in short, nothing to OS, as for apps, ask devs to put more work into them to do different resource graphics and optional 24bit colour mode. 24bit switch is only in my apps cause I'm and artist If I were a full blown programmer I probably wouldn't bother Also the market figures say it would be quite a bit of work for a very very very small percentage of ppl
thanks we will have to await for developers to work better. At leat the apps included by Samsung should be 24 bits !
It's a crime not do do so in a device like S2.
A little off-topic ... as a developer I am I'm currious ... you developed those 2 apps in what language? .net + Android SDK, Basic4Android, ... ?
jvidia said:
thanks we will have to await for developers to work better. At leat the apps included by Samsung should be 24 bits ! It's a crime not do do so in a device like S2.
A little off-topic ... as a developer I am I'm currious ... you developed those 2 apps in what language? .net + Android SDK, Basic4Android, ... ?
Click to expand...
Click to collapse
the two sh*tty test apps are about 20 lines of java using android sdk
The app in the video is a big combo (mess) of everything
I don't get why you're saying that banding doesn't occurs in 24-bit mode if it does occur ?! (talking in general)
EleCtrOx666 said:
I don't get why you're saying that banding doesn't occurs in 24-bit mode if it does occur ?!
Click to expand...
Click to collapse
it does only on low luminance green, but tbh, it's on every display depending on how subjective you are. But the horrid banding ppl talk about mostly is not an issue if resources are good and app is set to 24bit.
deanwray said:
Cause it dosent have a high colour high detail display like amoled plus, on the galaxy s 2, which is what this thread is for
Sent from my GT-P1000 using XDA Premium App
Click to expand...
Click to collapse
It has (I have the slcd version) and gradients are super smooth, anyway something weird is going on, I already posted this earlier:
take a screenshot with home+power and look at the pic on your computer ->banding
take a screenshot with qtadb and look at the pic on your computer -> no banding
godutch said:
It has (I have the slcd version) and gradients are super smooth, anyway something weird is going on, I already posted this earlier:
take a screenshot with home+power and look at the pic on your computer ->banding
take a screenshot with qtadb and look at the pic on your computer -> no banding
Click to expand...
Click to collapse
..and where did you find a S-LCD version of GS II?
I was talking about my desire
a couple of points. the nexus one and other amoled phones all had horrible banding for the last year, till the 2.3.3 update, and now the banding is gone completely. for example the XDA tapatalk app splash screen had banding. once 2.3.3 came out, the xda tapatalk app banding was gone. the app did not change from RGB565 to RGB888, the OS itself was updated with "something" which we arent clear on.
now considering the super amoled plus display has MORE sub pixels than the amoled with pentile sub pixel arrangement, it would be easy to think that banding should be even less on the plus version since there are more pixels for the same resolution.
anyway it still doesnt fully explain why angry birds on a nexus one, or any other phone, doesnt show the banding. but it DOES show banding on the SGS2. its the same app version. also considering the nexus one WAS seeing banding on these apps, but since 2.3.3 update, that banding is now gone, it makes me highly inclined to say this is a samsung software issue.
for fun i installed the test apks on n1, no banding on minimum brightness on RGB_888 on either apk. of course it was there on angry birds background RGB_565, but playing the app itself does NOT show the banding (only thanks to the android 2.3.3 update).
Related
Hi Guys,
I've seen some discussion around the HD2's screen colour depth.
I've been doing some experimenting and have found that the colour depth is decreased when using a live wallpaper.
Im using the Darkstone's Froyo V1 Build with Cotulla's latest zImage. I havn't tested with the Sense build yet...
Give it a try :-
Set a Live Wallpaper
Now Add The Analogue clock widget, power control and Home Screen Tips widgets to a blank desktop.
Notice the Gradients of the widgets look blocky and appear low resolution.
Now apply a normal Image Wallpaper and you'll notice a real increase in quality of the gradients in those Widgets
I've taken screenshots to show you but when the screenshot of the Live wallpaper is looked at on the computer it looks perfect so must be an issue with the Way the HD2 is displaying it..
Here's the 2 screenshots :-
goodness me, does every little detail require a new thread?
Flashmore said:
goodness me, does every little detail require a new thread?
Click to expand...
Click to collapse
Goodness me do threads cost you anything?? -
Dont read them if your not interested?
This is something that no-one has noticed so far and actually could be quite important - now why dont you go back to your 9million page thread and continue pointing people to post#4 like the real helpful fella you are eh....ffs
Yes, it's especially noticeable on the anologue clock but not on the pics you posted up. Didnt notice it at first. Sharp eyes you've got there. Lol
paulrgod said:
Goodness me do threads cost you anything?? -
Dont read them if your not interested?
This is something that no-one has noticed so far and actually could be quite important - now why dont you go back to your 9million page thread and continue pointing people to post#4 like the real helpful fella you are eh....ffs
Click to expand...
Click to collapse
HD2 has poor colour quality from the get go, running multiple applications let alone an OS that is overlapping another OS on top of of multiple applications running in the background is bound to have more than some effects, least of all important right now being the colour. I have no idea what you're talking about, but perhaps a quick browse over the forum rules would be a good start, it isnt 9 million pages long so you shouldnt have too much trouble. The least you could do is post in a thread of whoever ROM/Android release you are using.
Julian2103 said:
Yes, it's especially noticeable on the anologue clock but not on the pics you posted up. Didnt notice it at first. Sharp eyes you've got there. Lol
Click to expand...
Click to collapse
Yeah unfortunately they look normal on the screenshots i took for some reason which leads me to believe there's an issue with the way it's been displayed on the HD2.
Flashmore said:
HD2 has poor colour quality from the get go, running multiple applications let alone an OS that is overlapping another OS on top of of multiple applications running in the background is bound to have more than some effects, least of all important right now being the colour. I have no idea what you're talking about, but perhaps a quick browse over the forum rules would be a good start, it isnt 9 million pages long so you shouldnt have too much trouble. The least you could do is post in a thread of whoever ROM/Android release you are using.
Click to expand...
Click to collapse
First of all - the point of my post was to 'Prove' that the HD2 can display more then 65K colours as was first thought, if you'd read my post at all - what you've posted above is a complete nonsensical response.
This IS important as people 'like you' seem to think the HD2's screen is of low quality when in fact it isn't.
Maybe you'd have an idea of what im talking about if you took the time to read my post instead of 'trying' to be a Mod?
Maybe you should peruse the Forum rules and then you may in fact realise that i havn't broken any of them?
I wasn't moaning about it not booting, GSOD, SOD, No Sound etc i posted a unique 'observation' that may help in the further development of 'proper' graphics drivers for our port.
I also wasn't moaning about a bug of this particular build - so why should it be posted in the Thread for that build?
I just think some people around here have a chip on their shoulder and are trying to be something they are not - & you dear sir are not an XDA mod.
...whoa...nice...calm down guys...calm down...
Yep, no reason to get upset. I think that's a pretty interesting point you found there. Do you have any opportunity to store the screenshots into a lossless format? I really can't tell any significant difference from the two jpg´s you've posted there - been watching the two for about a minute and i can tell you that my eyes are known to color difference detection
i think it's better a thread like this than the 2348740860th always about "no booting, no sound, no radio, no android, no intelligence", all completely useless if the author read the forum form 5 minutes before posting, this thread is about a new "problem / symptom" and it's not useless... maybe it's not importante now to obtain 16m colors, but it's always something that can be fixed
on topic guys Dev forum not flaming
Keep it peaceful
Josh
i haven't really used an actual android phone (day to day) but im sure Google put that in there, because of Live wallpaper taking up CPU power thus lowering the quality of widgets.
EDIT: and the pics look EXACTLY the same (except for the wallpaper and time of coarse.)
but, on the device itself it is less quality, ive seen it before and thats why i use a static wallpaper.
Hi guys, yeah as i said in the post for some reason the screenshots taken directly didnt really show the difference for some reason.
I've taken some pictures using a camera and the difference is clearly highlighted here.
Cheers
Paul
I installed a live wallpaper on my Desire V5 build and noticed that the moon on the weather portion of the Sense clock (it was a clear night last night) changed color and looked a little more green than gray with the live wallpaper running. Don't know if its a bug or not, but it's just my observation.
Sorry to resurrect this ageing thread but it at least shows I bothered to search for it.
I seem to get this effect on some ROMS more than others, I also get it on the wallpaper itself but only for some.
I am thinking that it must be the wallpaper itself for me, it must be in a colour depth beyond the capabilities of the phone. For instance if I install the honeycomb ADW theme with the wallpaper enclosed I get this effect on the wallpaper.
Couldn't see any other threads about this, any ideas anyone?
Now that Samsung have officially confirmed that the Note will be one of the first to get the ICS update, what improvements will it make? Will it be worth while doing it for Note works very well on Gingerbread.
The most important for me, except other nice features, is that ics will optimized full the 2 cores of Note and improved more battery life.
Sent from the best smartphone, Galaxy Note...
I am sure ICS will fly on the Note. Full dual core optimisation is what I am wanting.
Sent from my GT-N7000 using xda premium
the most SICK news it's "hardware acceleration"
we got much mote better GPU than Samsung Galaxy Nexus !
So our phone will ROCK !
i know they said ICS in Q1 but have they released a tentative date?. .
any ideas? .or patterns with samsung?
I hope they take their time releasing ICS. The fewer the bugs, the better for us
mcatt66 said:
i know they said ICS in Q1 but have they released a tentative date?. .
any ideas? .or patterns with samsung?
Click to expand...
Click to collapse
I was talking to a Samsung rep on phone today and when i asked him about ICS, he said "Its already on ICS". So my next question was: "are you sure? cause i am on 2.3.6". He said "yeah what i meant was, since our nexus has it, it won't be long before the note gets it. No official dates as to when it comes" So, either a) he had no idea what he was talking about, or b) ICS is being tested on the note as we speak
what im waiting for is AOSP ICS rom or CM9 would do. The reason is FULL tablet interface, experience.
I'm wondering how much faster the camera will be. Romain Guy said that the zero shutter lag on the galaxy nexus is a combination of software+hardware optimisations, so it will be interesting to find out what kind of improvement we will get. At the moment it feels like there is 1 second between each of 1) Pressing the camera button, 2) The shutter noise and 3) actual photo taken. It's a bizarre experience.
It's gonna be LEGEND......
..wait for it....
....ARY!
wabz said:
I'm wondering how much faster the camera will be. Romain Guy said that the zero shutter lag on the galaxy nexus is a combination of software+hardware optimisations, so it will be interesting to find out what kind of improvement we will get. At the moment it feels like there is 1 second between each of 1) Pressing the camera button, 2) The shutter noise and 3) actual photo taken. It's a bizarre experience.
Click to expand...
Click to collapse
The main reason they used a 5MP instead of an 8MP camera in the Galaxy Nexus was speed. Fewer pixels to process, fewer pixels to write to storage. Don't expect that kind of speed on the Note, or a GS2, etc when they get the ICS camera app.
To be honest, if you use the technique and aren't using the flash where you prepare the camera by pressing the shutter button first and then release when you want to take the picture then there is virtually no meaningful lag.
You definitely have a different note than me. The lag ducks. Do like the camera tho.
airwater9 said:
To be honest, if you use the technique and aren't using the flash where you prepare the camera by pressing the shutter button first and then release when you want to take the picture then there is virtually no meaningful lag.
Click to expand...
Click to collapse
Im hoping that ICS might correct my offset screen (s-pen, finger input) and somehow get rid of the pinkish huein the middle of the pictures i take.
If Dolohin HD crashed less that would be great.
Other than that, everything else would be gravy. I love my Note and I am now done with iphones. My son still has a 4gS but I cant even stand to look at it!
However, Im not one of those people who judge others. If you love iphones, more power to ya!
BeamMeUpStreaky said:
Im hoping that ICS might correct my offset screen (s-pen, finger input) and somehow get rid of the pinkish huein the middle of the pictures i take.
If Dolohin HD crashed less that would be great.
Other than that, everything else would be gravy. I love my Note and I am now done with iphones. My son still has a 4gS but I cant even stand to look at it!
However, Im not one of those people who judge others. If you love iphones, more power to ya!
Click to expand...
Click to collapse
Ics should fix the spen problem, ics has stylus input already built in.
Yes having the spen more accurate would be a great new advantage of having ICS on Note..
I am still impressed by the speed of my note. With ICS if it gets better... Awesome!
Sent from my GT-N7000 using XDA App
Ryanscool said:
Ics should fix the spen problem, ics has stylus input already built in.
Click to expand...
Click to collapse
I got sick of my pen making random selections and acting erratic. I had a fit lol amd ripped the button off the side of the pen. Problem solved. Its still offset and i despise that bur at least when i pass the pen over the screen it doesnt select something from and inch away from the screen. I will buy a new pen with no button function. Thr only thing i ever used the button for was screen caputure but i can do that easily with hone button + sleep button.
I notice that on some web pages when i want to click a link, i have to compensate by pressing higher that the hyper link with my finger or pen.
Samsung wants to have an s-pen smartphone... GET IT RIGHT. As far as finger touch goes, there is no excuse for having to press 2mm higher than the hyperlink. Thats a lack of screen calibration which i find ignorant.
Now if i could stop all of my browsers from closing abruptly i would be less angry about the screen calibration. My iphone browser has never closed on me, not on any of them.
Still love my phone though. However, i seem to be refering to it as the galaxy n7000 because between tje pen and the unforgivable lack of screen calibration, "Note" seems a like a title that it has yet to earn.
Strange, I have no spen inaccuracy problem.
However I would like to see:
1-Better camera picture quality,the sharpness in the taken pics really sucks.
2-faster,this is a must be addressed issue,the wakeup lag from the homebutton,the lag while opening applications specially the Contacts is just unforgivable for hardware with such specs.
3-I have no such issue in the Opera browser since its not hardware accelerated,but both Dolphin and stock browsers which support that feature crush a lot and suffer from battery drainage. This of course could be because gingerbread doesn't support that feature either.
Other than these three very important issues all is well on my front.!!
hagba said:
Strange, I have no spen inaccuracy problem.
However I would like to see:
1-Better camera picture quality,the sharpness in the taken pics really sucks.
2-faster,this is a must be addressed issue,the wakeup lag from the homebutton,the lag while opening applications specially the Contacts is just unforgivable for hardware with such specs.
3-I have no such issue in the Opera browser since its not hardware accelerated,but both Dolphin and stock browsers which support that feature crush a lot and suffer from battery drainage. This of course could be because gingerbread doesn't support that feature either.
Other than these three very important issues all is well on my front.!!
Click to expand...
Click to collapse
Correct. Whilst it's not perfect the wake up lag is poor. Sometimes when opening sms messages or contacts/phonebook it takes upto 4 seconds which is unnacceptable!!!
It should be instantaneous...
im pretty excited about ics too exspecially about the new ui. I was looking through the features list and it didnt say any thing about it there but does any one know if the default mail app (not gmail) has push notifications
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I read the page but it didn't say anything about push email which is really important to me, i use yahoo mail as a default mail and i use the ymail app, not that there is anything wrong with it but i prefer the default email app as sometimes when you want to "share" something there is the message, Bluetooth, email and stuff but sometimes it doesn't have the share through yahoo mail app, plus the yahoo mail takes forever to 'attach' pictures and send.
I just wanted to know if you guys know anything about the push email on the default email app, i know the gmail app has it but im not switching to gmail
Another thing i would like to know is this:
Huge fan of reading ebooks, and note has a sexy screen perfect for reading books, and i love the ui the books are displayed above, can any one clarify if that is only for tablets, or is an app on the android market (checked the market and nothing) or will only be available on ics when it comes out
Also will the 'US' version of android market be available outside US on ics or we still got to root and then use market enabler?
Hope ICS comes out soon with as little bugs and and plenty of improvements possible!!
I have installed Paranoid Android on my Note and noticed that there is severe clipping in the CM9 UI elements. Even the default ICS wallpaper , the one with the"rainbow" coloing stripes show severe clipping on the lockscreen. It looks just plain ugly. And since most of the CM9 UI backgrounds are a shade of grey, there is severe clipping of these grey elements to a purplish pixellation and to black. You can notice this if you take the settings page in Paranoid android or any other CM9 based ROM (assuming most CM9 based ROMS have the same default theme) Look under the status bar where the grey background fades to black and you may notice severe pixellation like issues at that area. Now, go to advanced, screen settings and MDNIE mode, you will notice that the clipping keeps changing when changing modes but its still there in every screen mode.
How many of you are experiencing this? Assuming a majority of the people who run Custom ROMS run a CM9 based ROM, why isnt this issue reported anywhere? I'm asking because, the issue is plainly visible in these grey areas and UI elements making the visual experience really bad. And why is Gamma Control disabled in these CM9 kernels? I believe lowering the gamma would solve the problem.
I've noticed that CM9 kernels have the worst clipping whereas in other stock based kernels, the clipping is comparitively lower, closer to the stock kernels.
So once again users of CM9, please do report if you face this issue.
CM9 users please report back because I havent seen anybody talking about this issue in any of the CM9 related ROMS thread. People seem to ignore an issue which stares back right at the face even in ambient lighting. Why havent this been reported?
I dont have much idea about who develops CM9 kernels for the note. How can we contact the CM9 developers and let them know of this issue and request to enable Gamma Control within the kernel?
Somebody please help me out here. Because its been a month after I bought my note and I've been struggling and doing my best to find a solution to this horrible clipping. I had got in touch with GSMArena and got this issue published, yet Samsung never responded, I tried kernel after kernel and realised that the intensity of the issue varies from kernel to kernel. I've seen that whomever I ask about the clipping in this forum says they have it but then everyone seems to be happy running different ROMS and in these CM9 based ROMs which look as close to stock Google ICS UI have severe clipping all over the UI and yet people dont seem to bother.
So what can I conclude from this? Is this an isolated issue or are all of you Note users who have this issue just keeping silent and living with it?
I do not mean to spoil anybody's peace or anything. I clearly dont know how to get in touch with the CM9 devs for the Note, somebody help me if possible. And if you feel that this is an isolated issue, do let me know otherwise. Because, when the basic UI shows severe clipping, the whole user experience is spoiled and nobody wants to live in fear with bright UI elements and bright wallpapers dreading the clipping if anything at all has to be dark. We paid a premium for this device and even Samsung seems to ignore. I have the SGS3 and there is no clipping on it but just that everything seems darker on the GS3 when compared to the Note. This alone shows that Gamma is a culprit here and I could just sell away my Note and just live with the GS3. But that doesn't help anybody who is facing this issue and wants to see a solution. Even I personally like the note more than the GS3 and I want to keep it but for this issue. Not everybody has the money to jump to the next flagship every now and then and for the people who spent their money on the Note doesn't have to "live with it" just because they decided to buy it without knowing such an issue existed. Not every store lets you try and trial their devices before buying them.
Samsung has even seemed to ignore the EMMC issue even after claiming they are "working on it" I dont see anything productive from Samsung's side as even a device which was previously unaffected had the affected kernels pushed to it via an update. So basically if it was not for people like Entropy who works day and night for that issue, Samsung could keep replacing motherboards for every random wipe a user does. They basically want to sell the note until the Note 2 and then this wouldn't be their problem anymore. Problems like the emmc bug is a MISTAKE from Samsung's part and they should be ready to repair devices even beyond warranty as the user may have only done the most harmless thing, i.e to reset the device to factory settings.
So, coming back to topic, how do we get in touch with the CM9 devs and enable gamma control on these ROMs? Most ROMS have gamma control under MDNIE settings which is greyed out, most probably because the kernel doesnt support it. This is the best I can do for the people who are affected by the clipping issue as I'm not a developer. This issue isnt an isolated case in my opinion and affects every Note I've got a chance to see.
It might help if you actually posted requests in the cm9 discussion thread? #commonsense
Seriously after reading TS long posts still*cannot figure out his problem
please post shots to show your issues
I have been using CM9 roms since build 2 and do not seem to notice such issues or maybe i am blind ?
mobile88 said:
Seriously after reading TS long posts still*cannot figure out his problem
please post shots to show your issues
I have been using CM9 roms since build 2 and do not seem to notice such issues or maybe i am blind ?
Click to expand...
Click to collapse
Yeah. OP is TL;DR complaining about some "severe" issue I've never seen and no one else has.
As to gamma control being disabled - I should remove that from the settings app, as that's something supported by the I9100/I777 display driver but not ours.
Entropy512 said:
Yeah. OP is TL;DR complaining about some "severe" issue I've never seen and no one else has.
As to gamma control being disabled - I should remove that from the settings app, as that's something supported by the I9100/I777 display driver but not ours.
Click to expand...
Click to collapse
Oops..I'm sorry for the long post. Its basically about the severe "black clipping" which has been affecting the Note since release. This issue is best seen when displaying dark shadows in images and videos. There were many threads discussing this issue. And GSMArena had published this issue in their news after I mailed them about the same.
What I wanted to tell was, I feel this is caused by the Note's screen having the gamma cranked up quite high and I believe lowering the gamma would resolve this issue.
The default CM9 theme shows severe clipping in backgrounds and UI elements. All the grey backgrounds, (the default theme) clip to black just below the status bar.
Even all the videos which have dark shadows are totally blocky due to this and the clipping makes them literally unwatchable.
I had reported this issue to GSMArena
http://www.gsmarena.com/samsung_galaxy_note_plagued_by_display_issues-news-4513.php
I wanted the Gamma Control feature which is presently disabled to be enabled in the CM9 kernels so that we can tune down the Gamma to eliminate this clipping
The same issues existed on the GNexus and was fixed with the Lean Kernel which had Gamma Tuning.
So once again, in short, I'm talking about the "Black clipping\crush" on the Note when displaying darker shades of colours.
All the notes have this problem, and we need to access to gamma control but as supercurio said it won't solve all the problems of the black clipping and banding issues
Sent from my GT-N7000 using xda premium
Satishp, i know what are you talking about. Just take a picture of your note and post it here. Of course, you won't use a screenshot feature but a camera.
I sold my note bc of the black clipping issue, but now I cannot buy an s3 or HoX cause their screens are just to small, that is, narrow. Gonna buy Note again and hope some solution will come out. It is too bad to buy a phone for its screen and get a crappy quality. Issue on s3 is solved with lowered gamma. Comparing with the Note, s3 has much darker screen. Sometimes too much.
Entropy512 said:
Yeah. OP is TL;DR complaining about some "severe" issue I've never seen and no one else has.
As to gamma control being disabled - I should remove that from the settings app, as that's something supported by the I9100/I777 display driver but not ours.
Click to expand...
Click to collapse
It's a very real issue affecting EVERY Note, derp
NotablyNice said:
It's a very real issue affecting EVERY Note, derp
Click to expand...
Click to collapse
http://www.gsmarena.com/samsung_galaxy_note_plagued_by_display_issues-news-4513.php
Huh?
Everytime I turn my screen on I smile at how awesome it is..Hell it seems even better now that I have been using cm10 but i think thats just because its brightness seems to be overall set higher.
MrDSL said:
Huh?
Everytime I turn my screen on I smile at how awesome it is..Hell it seems even better now that I have been using cm10 but i think thats just because its brightness seems to be overall set higher.
Click to expand...
Click to collapse
Same. I don't often stare at my phone from a distance of 3cm to see any imperfections.
Sent from my GT-N7000 using xda premium
All of the speculation and misinformation of this issue is really starting to get frustrating. First, the issue IS with the hardware. It may be possible to reduce it's impact using software but the fact remains this is a hardware issue. How do I know? I have replaced my Note's screen and the newer screen I have isn't as good as the old one.
The new one isn't awful, it simply isn't as good as the other.
2nd point - everyone will have this issue. It is simply an inherent problem with the screen hardware and it is completely implausible that there are 1 or 2 'perfect' screens out there. There will simply be variations. Some people WILL have better screens than others. For some people the issue may be completely unnoticeable and for others it will be glaringly obvious. Don't judge or hate on people because their screen is worse than yours and vice versa.
3rd the issue is MORE noticeable at lower brightness values than high brightness values. If you have your note on higher brightness values then you're unlikely to notice it. In my case, I can not see any clipping if I am in a lit room. The only time I can see it is when I'm sat in the dark with very low brightness. As I said above this will vary from person to person.
I have attached 2 photos below. One is a normal exposure where you can see the clipping is hard to see. Another is a long exposure which amplifies the issue more and makes it more noticeable (I used a longer exposure on my camera to show this). Fortunately it isn't so bad for me, but for some people my long exposure image is the reality unfortunately.
Standard: http://i48.tinypic.com/4uxnia.jpg
Long Exposure: http://i48.tinypic.com/5akew3.jpg
Why have we got a clipping problem and can software solve it? I believe it is highly unlikely that this issue can be solvable. I also think the issue stems from one simple shortcoming to the screen; the minimum brightness achievable per pixel. The problem is the jump from this minimum brightness to the 'off' (perfectly black) pixel is too great. There is no transition. Can gamma control solve this? I'm not convinced. I think the issue is more to do with what the lowest pixel brightness the screen is capable of. For the poorer people this minimum brightness will be quite bright. For others the minimum brightness will be lower.
If any devs know of a way of controlling pixel brightness on a level where it can be noticeably changed and if it is possible to reduce this minimum brightness then sure, it would certainly be a possibility. But I don't think this is possible.
Part of this might be a limitation of the HD Pentile AMOLED technology. But if you notice, both the Galaxy Nexus and the Galaxy S3 share the same technology. For people who argue that the S3 uses a different manufacturing procedure, Samsung has no where mentioned this and its just an assumption.
The GNexus had the same issue but was solved with the LEAN kernel which implemented a gamma control within the kernel. If you've seen the S3's screen ( I own an S3 too, So I've spent a good time comparing), you will notice that the S3's screen is visibly darker than the Note's screen. Images tend to look darker and this shows that the S3's screen has its gamma set to a lower value which eliminates the clipping.
More proof for you, lets take the gammatest image and view it on our PC. Most PCs use an LCD display and still you can see the greys gradually fading to black.
Now increase the gamma of your display from your display adapter's color settings and view the same image again. You will see that you can see all the way upto 1 and then black just like how the image is displayed by the note.
http://forum.xda-developers.com/showthread.php?t=1800117
Now view a 720p or 1080p clip on your PC with the gamma values still high, you will see the clipping in every dark scene. Try it yourself.
This shows that gamma calibration can correct the issue to atleast some extent.
Hmm. There appears to be truth in what you say. Unfortunately the Note is lacking somewhat in the developer department. And the few devs there are have other pressing issues to deal with so the question becomes who can implement gamma control on the Note?
MrDSL said:
Huh?
Everytime I turn my screen on I smile at how awesome it is..Hell it seems even better now that I have been using cm10 but i think thats just because its brightness seems to be overall set higher.
Click to expand...
Click to collapse
Yup. Despite being pentile, compared to my I9100/I777 the screen is even more gorgeous.
I'm on minimum brightness nearly all the time. No clipping issues whatsoever.
MrDSL said:
Huh?
Everytime I turn my screen on I smile at how awesome it is..Hell it seems even better now that I have been using cm10 but i think thats just because its brightness seems to be overall set higher.
Click to expand...
Click to collapse
Yup, and it's even better when you switch the screen mode to "Dynamic" (Advanced Settings).
Sent from my GT-N7000 using xda premium
I have the clipping regardless of which mode I put it in, apart from the clipping the screen is mint, which makes me even more pissed off when I watch a movie and a dark scene comes on, then the shade between black and grey turns into a lego block mess. I really cant beleive so many people are happy with it, half of u guys must be blind, I exchanged my Note twice, tested my cousins and my bosses Notes, all have the exact same problem. I even bluetoothed the gamma test image to a few in carphone warehouse , same with them, even the samsung rep I spoke to over the phone said the one they have in the office also has the issue. Total crap imo, Samsung total FAIL.
Entropy512 said:
Yup. Despite being pentile, compared to my I9100/I777 the screen is even more gorgeous.
I'm on minimum brightness nearly all the time. No clipping issues whatsoever.
Click to expand...
Click to collapse
Actually use your Note and go watch a dark movie... It's there
NotablyNice said:
Actually use your Note and go watch a dark movie... It's there
Click to expand...
Click to collapse
I've watched plenty of dark movies... As good as if not better than my I9100/I777.
Entropy512 said:
I've watched plenty of dark movies... As good as if not better than my I9100/I777.
Click to expand...
Click to collapse
Please take a picture if your note displaying the gamma test image (blocks numbered 1 to 20) with stock gallery app in a dark room, screen mode dynamic, max brightnes with auto adjust switched off, I bet number 4 is light grey, then number 3 is black, if so your device has black clipping. There should be no abrupt drop from grey to black, it should be a gentle fade.
Thanks.
So I just got my hands on the device a couple hours ago, and this is so great I felt the need to write a review immediately.
When I heard the name "oppo", and saw that company from China, I wasn't expecting something spectacular. It had good specs on the paper, but in my mind I was thinking "Meh, it will be just a blown up chinese device". Well, I'm glad to say I was wrong!
The package
Opened the first cardboard box. This first one looked like a shoebox, pretty amusing at first, and inside is contained the actual device box. And there came the first great surprise: it's already original. The box actually unfolds, seated by a magnet. You then get your eyes on the phone, and under it you can find the classic accessories (earbuds, charger, USB) PLUS! Two programmable NFC tags. Nice little gift.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
The device itself
The device itself is pretty standard:
- On the top of the front, you can find the front camera, earpiece, and a notification LED. Other sensors are pretty hidden, which make it very clean. On the bottom, 3 touch keys that light up when the screen is on (and they're otherwise invisible), from left to right Menu, Home and Back. Since I'm used to Nexus 4 touchkeys, the back key is on the other side.
- The back is also clean, similar to some HTCs. A simple and small camera sensor on the top, a tiny hole for the 2nd microphone next to it, a big speaker at the bottom, and that's it. There's a subtle "oppo" logo written in the middle, and I'm wondering right now if they shouldn't rotate that logo, as it's written vertically, thus you're not sure if it's "oddo" or "oppo", especially if you're holding it in landscape the wrong way.
- On the left side, the SIM tray, similar (if not exactly the same) to the Nexus 4 one ; you need a small extractor tool to open it, and under it the power button.
- On the right side, just the two volume buttons.
On the top lays the headphone jack, and the USB on the bottom.
All the buttons feels super sturdy and well-made, there's little to no jankiness. A sturdy device. The design is original and you cannot say "what's that iPhone" when seeing it.
Turning it on
Duuh, a boot sound, I hate that.
Okay first, the screen is GORGEOUS. I never had the chance to see another 1080p screen in a phone yet, but the Find 5's one is definitely one of the best screens I've seen. It doesn't have burning colors like AMOLED, and has just the right contrast. The viewing angles are way better than Nexus 4's (which gives blue if you look from one side, or yellow from another side), to put it straight there's simply no color offset at all from any angle. There a very small contrast increase when you look from the bottom or the top at a high angle, but you really have to be looking for it. The resolution is just great, it's beautiful.
Classic connectivity. I don't have my SIM card in yet, but it has all the things you'd need: Wi-Fi, Bluetooth, NFC (with a little tool to write some features to the provided tags), support for Wi-Fi Display, Wi-Fi Direct, etc. Of course, they use the normal NFC protocol, so you can Beam with your friends having a Nexus. The Wi-Fi reception seems pretty good, no loss of speed anywhere in my house.
Now, one big downside, the software. Actually, it feels like TouchWiz, and god knows I hate TouchWiz. It's like having a Galaxy S, with iOS-like icons (rounded glossy squares) and the same exact style of app drawer. The settings menu has been revamped, and it's a big mess. Everything feels just unsorted and messy, there no logical way to find out a particular option. And the Developer Settings menu lacks 90% of options.
The notification bar puts Wi-Fi and 3G on the left, notifications on the right (just like an iPhone). The top of the notification drawer is the Jelly Bean one, and JUST underneath you get gray gradients with quick settings icons (just like TouchWiz, again), and a old-style notification list, with the clear button at the bottom.
In the gallery, the Android's Action Bar has been removed to put a small shortcuts bar at the bottom, iOS-styled once again. The contacts app is also TouchWizy.
You can find some extra features in the settings, like gestures and motions to pick up a call.
There sure are some good ideas from Oppo's software designers, but they really took a direction waaaay too straight towards iOS (now, did I say TouchWiz because I'm not used to see them on an iPhone originally? Heh). Take the same color scheme, but with Holo design, and you'll be an epic win for me.
Wait, it's not all! Camera time!
From what I could see previously, it's no surprise that the Camera software is also not spectacular. It has that same iPhone inspiration, and both the UI and UX are very perfectible. The settings cannot be naturally scrolled, and it's a bit bad to use.
However, the Camera hardware is pretty great, at least on the video part. You can record the classic 480p, 720p and 1080p resolutions with the back camera, and 120fps video in either slow-motion or at regular speed in 480p resolution. This is something never seen before, and sports fan will probably like it, as you can record things moving fast in a smooth slow-motion.
The front camera allows recording in 720p, and has a pretty good lighting.
For pictures, even though both front and back support HDR, the quality is not spectacular. It's in the range of most phones, at least in medium-low light. The image is pretty noisy and grainy, and a bit blurry even when focusing as best as possible.
A sample from the back camera (click to enlarge):
Wrap-up
From a hardware point of view, the Find 5 is really awesome: great SoC (same as Nexus 4) with 2GB RAM, superb screen, nice speakers, notification LED, nice camera, original design, and the touchkeys are ideally positioned. It's a sturdy device, that tells you "I can live forever".
However, the software really lacks polishing (but CyanogenMod will take care of that, hehe). You can smell the iPhone inspiration everywhere, and it just breaks the Android experience as all the other apps behave differently than the system. Some apps like the Settings app has been revamped and became a mess, but there are some nice ideas like the Files app, having an okay design, and cool features like FTP or DLNA.
All in all, that's a 8.5/10 for me, because I know the software won't last long on my device. It's really worth the price. The back camera could be a little bit better when it comes to pictures, and a little refinement of the device shape (especially some edges) would make it even better, but I'm nitpicking.
If you want it, don't hesitate, you should get it.
Thanks friend.
Will have cm10.1 support
Ty
Aerys said:
Thanks friend.
Will have cm10.1 support
Ty
Click to expand...
Click to collapse
Of course, I want that device to be my Nexus 4 Plus.
XpLoDWilD said:
Of course, I want that device to be my Nexus 4 Plus.
Click to expand...
Click to collapse
I help you test
Aerys said:
Thanks friend.
Will have cm10.1 support
Ty
Click to expand...
Click to collapse
Unless we run into some horrible unforeseen obstacle, yes.
Where you guys bought the oppo?
Aerys said:
Where you guys bought the oppo?
Click to expand...
Click to collapse
Normally, Chinese manufacturers set up us teh bomb
Instead...
oppo set up us teh free device
I'm not quite ready for a review yet - But here's some observations regarding their software, from a development perspective:
First, a bit of background - Qualcomm devices are almost always derived, to some degree, from Qualcomm's reference source at CodeAurora, aka CAF.
https://www.codeaurora.org/gitweb/quic/la/
A good way to determine which CAF release tag a manufacturer used was to check out various tags from https://www.codeaurora.org/gitweb/quic/la/?p=kernel/msm.git;a=summary , drop the manufacturer's source release on top, and find the CAF tag that produces the smallest diff after dropping the source on top.
A list of CAF tags (which can sometimes be quite outdated, but is good enough for our purposes) is at https://www.codeaurora.org/xwiki/bin/QAEP/release
In the case of the Find5 - they derived from CAF tag A8064AAAAANLYA101034 - which is fairly old (October 2012). It's on branch jb_rel_rb4 Oppo didn't merge in upstream CAF changes at all in the interim. Sony's Xperia Z kernels were based on A8064AAAAANLYA1334, which is only about a month newer date-wise, but is at least Android 4.1.2 instead of 4.1.1
A8064AAAAANLYA101034 is a tag along the jb_rel_rb4 branch
Oppo's kernel produces a diff against the base CAF tag that is only about 583k in size - this is pretty small (good news!)
I'm in the process of pushing these diffs as a reference to https://github.com/Entropy512/kernel_find5_reference - NOTE: I will NOT be doing any development in that particular repo, AND I may rebase it periodically. It is for REFERENCE ONLY.
Attached is a complete patchset against the above tag, generated using
Code:
git format-patch
EDITED: Previously I thought the base CAF tag was A8064AAAAANLYA103010 - this is wrong.
Thanks for the review xplodwold! Its kinda cool to hear your take on it.
Aerys said:
Where you guys bought the oppo?
Click to expand...
Click to collapse
Oppostyle.com..or amazon
Sent from my X909 using Tapatalk 2
So it means it is hackable? No locked bootloader, fastboot open, rootable, kernel source?
Chris
Sent from my Barnes & Noble Nook Tablet using xda app-developers app
Aerys said:
Where you guys bought the oppo?
Click to expand...
Click to collapse
Coreym said:
Oppostyle.com..or amazon
Sent from my X909 using Tapatalk 2
Click to expand...
Click to collapse
also ibuygou.com
chrmhoffmann said:
So it means it is hackable? No locked bootloader, fastboot open, rootable, kernel source?
Chris
Sent from my Barnes & Noble Nook Tablet using xda app-developers app
Click to expand...
Click to collapse
Yep
Sent from my X909 using Tapatalk 2
detritu5 said:
also ibuygou.com
Click to expand...
Click to collapse
Stick to official stores for warranty.
First off, a great review which is killing me more as I'm waiting for DHL to update my tracking info. The best is that the future is looking bright for this device in the ROM department, thanks guys!:good:
chrmhoffmann said:
So it means it is hackable? No locked bootloader, fastboot open, rootable, kernel source?
Chris
Sent from my Barnes & Noble Nook Tablet using xda app-developers app
Click to expand...
Click to collapse
Bootloader seems wide open.
Biggest "quirk", which doesn't take too long to figure out, is that you need to add Oppo's USB vendor ID (0x22d9) to ~/.android/adb_usb.ini (that's on Linux, not sure which Windows/MacOS equivalents are...)
Entropy512 said:
Bootloader seems wide open.
Biggest "quirk", which doesn't take too long to figure out, is that you need to add Oppo's USB vendor ID (0x22d9) to ~/.android/adb_usb.ini (that's on Linux, not sure which Windows/MacOS equivalents are...)
Click to expand...
Click to collapse
That's interesting. Maybe that's why we were having so much problem to get adb working
Sent from my X909 using Tapatalk 2
please xplodwild, make us a cyano rom...oppo rom is so s.hitty and buggy :crying:
chrmhoffmann said:
So it means it is hackable? No locked bootloader, fastboot open, rootable, kernel source?
Chris
Sent from my Barnes & Noble Nook Tablet using xda app-developers app
Click to expand...
Click to collapse
Yes ,yes ,yes ,yes and yes .
What a great news, I'm a oppo find 5 owner, now very pleased by your great job to bring us third part ROM!!!!!
I've taken a break from find5 to try and get camera working on the Sony Xperia Z using a trick pointed out to me by one of the other CM maintainers.
If this works, it means that instead of starting with a massive kernel rebase, we can use the same approach the Z maintainers are currently using for their bringup (bring patches from mako into the factory kernel) and then do a major kernel rebase later.
The method used to do bringup on the Z is much faster, however it was previously thought it would not be possible to get camera working without some major hacks. Now it looks like there may be an easier (although still a bit hacky...) solution - if it works on the Z, that'll be a good path to go on this device.
It seems strange that a screen that could, if properly integrated with small aesthetic changes in the software, extend dramatically the battery life of this device is being asked more and more (with every update) to energize and illuminate as many pixels with 100% white as possible. It is maddening to me. When we add into the mix the non-replaceable battery, the whole thing starts to reek of planned obsolescence.
I would like to give motorola the benefit of the doubt, and imagine that the software developers in charge of the texting, dialer, and contacts truly have our eyes and sensibilities at heart, but it is difficult.
Thank you to all developers, including those who created this very app, who have followed in the footsteps of blackle (or without any external inspiration) and afforded the end user a simple switch in a settings dialogue somewhere.
I am assuming that at some point another software update will happen for this otherwise amazing phone. What are the options for communicating the desire for such a change to those rolling out 4.4.next? Whose skirt do I tug on? I have seen a LOT of similar sentiment. Also, should the ability to root an at&t '58 ever come to light, are there any ROMs that are skinned in darkness? Oh wait, I know, UTSF.
I feel better just talking about it. Thanks.
What?
It's stock Android, not specifically the Moto X. Indeed if you root there are many ways to make the white black
Sent from my XT1060
rocketsaucev2 said:
It's stock Android, not specifically the Moto X. Indeed if you root there are many ways to make the white black
Sent from my XT1060
Click to expand...
Click to collapse
any root app for this?
super65man said:
any root app for this?
Click to expand...
Click to collapse
Gravity Box for all black system and "team blacked out" (they invert many apps) for a lot else. Also, there are many apps, that have "dark" (black) themes. I use Textra (sms) and whatsapp plus (find a black costum theme). Also, for Firefox there are extensions, that invert webpages. Too bbad Firefox is crap
But hold your horses, the difference in battery life isn't that dramatic. People will ALWAYS pick the phone that is brighter and has more "vibrant" colors in the store. The latest Samsung ad even refers to the critic, the colors on their devices are over saturated. It's a feature, not a bug
Dark menus and apps like the dialer are generally harder to view outside, and aren't as pleasing to the eye. Had a GS4 (it has an AMOLED screen as well) and tried a custom ROM done exactly to accommodate the AMOLED with dark colors and clear black everywhere possible. Well, I didn't enjoyed that in the long run, although it looked sleek at first sight. As I said it's generally harder to view the screen outside, and the eyes tend to tire from the black background.
Simply not worth it for the additional hour or two at most of battery life.
thesimulacre said:
It seems strange that a screen that could, if properly integrated with small aesthetic changes in the software, extend dramatically the battery life of this device is being asked more and more (with every update) to energize and illuminate as many pixels with 100% white as possible. It is maddening to me. When we add into the mix the non-replaceable battery, the whole thing starts to reek of planned obsolescence.
I would like to give motorola the benefit of the doubt, and imagine that the software developers in charge of the texting, dialer, and contacts truly have our eyes and sensibilities at heart, but it is difficult.
Thank you to all developers, including those who created this very app, who have followed in the footsteps of blackle (or without any external inspiration) and afforded the end user a simple switch in a settings dialogue somewhere.
I am assuming that at some point another software update will happen for this otherwise amazing phone. What are the options for communicating the desire for such a change to those rolling out 4.4.next? Whose skirt do I tug on? I have seen a LOT of similar sentiment. Also, should the ability to root an at&t '58 ever come to light, are there any ROMs that are skinned in darkness? Oh wait, I know, UTSF.
I feel better just talking about it. Thanks.
Click to expand...
Click to collapse
Well you could have just said I want the choice to change all light themes to dark to save battery. Wow, did that all in one sentence LOL sorry had to be a smart ass. I do agree I prefer black especially at night even on a low setting it is blinding.
I like the black/blue look mainly because it looks more high tech than all the white nonsense of KitKat. That's why my X is still on 4.2.2.
bigv5150 said:
Well you could have just said I want the choice to change all light themes to dark to save battery. Wow, did that all in one sentence LOL sorry had to be a smart ass. I do agree I prefer black especially at night even on a low setting it is blinding.
Click to expand...
Click to collapse
Brevity is not my strong suit.
The search function brought me to a cyanogenmod version of the texting that, with a little defaults finegeling, brought me back the old black n blue, which I also like better.
I think that without the ability to change permissions, though, the contacts and dialer are out of reach.
If you like black and blue,I'm sure there are forums for that.
_MetalHead_ said:
I like the black/blue look mainly because it looks more high tech than all the white nonsense of KitKat. That's why my X is still on 4.2.2.
Click to expand...
Click to collapse
That's absolutey ridiculous. You are missing out on so many Motorola updates not to mention android itself by staying on jelly bean. I don't even
Sent from my XT1060
rocketsaucev2 said:
That's absolutey ridiculous. You are missing out on so many Motorola updates not to mention android itself by staying on jelly bean. I don't even
Sent from my XT1060
Click to expand...
Click to collapse
I have a Nexus 5 as well, so I do have a phone that is running the latest and greatest. I know what I am missing out on, and it's not much as far as I'm concerned. For me, my Moto X is perfect. It does everything I need it to, the way I need it to so there is absolutely no reason for me to update it. If it ain't broke, don't fix it. I'm not one of those guys who has to have the latest software on everything. My MacBook Pro is still on Snow Leopard, my iPad Mini Retina is on iOS 7, and again, my X is on 4.2.2. Heck, even my 2013 Nexus 7 is still on Jelly Bean. I find something that works, and I stick with it.
_MetalHead_ said:
I have a Nexus 5 as well, so I do have a phone that is running the latest and greatest. I know what I am missing out on, and it's not much as far as I'm concerned. For me, my Moto X is perfect. It does everything I need it to, the way I need it to so there is absolutely no reason for me to update it. If it ain't broke, don't fix it. I'm not one of those guys who has to have the latest software on everything. My MacBook Pro is still on Snow Leopard, my iPad Mini Retina is on iOS 7, and again, my X is on 4.2.2. Heck, even my 2013 Nexus 7 is still on Jelly Bean. I find something that works, and I stick with it.
Click to expand...
Click to collapse
Not just the 'latest and greatest'. If updates to the Motorola features on the Moto X are not much as far as your concerned then that defeats the purpose of owning the Moto X. They haven't fixed anything that was broken, they've made them better. I guess you couldn't know what you are missing because you have made the puzzling decision to willingly stagnate your device ?
Sent from my XT1060
rocketsaucev2 said:
Not just the 'latest and greatest'. If updates to the Motorola features on the Moto X are not much as far as your concerned then that defeats the purpose of owning the Moto X. They haven't fixed anything that was broken, they've made them better. I guess you couldn't know what you are missing because you have made the puzzling decision to willingly stagnate your device ?
Sent from my XT1060
Click to expand...
Click to collapse
As I said, the features I use work perfectly for me. I don't need anything else from my X besides what I'm already getting from it. Trust me, I know what I'm doing.
_MetalHead_ said:
As I said, the features I use work perfectly for me. I don't need anything else from my X besides what I'm already getting from it. Trust me, I know what I'm doing.
Click to expand...
Click to collapse
The software you are running is inferior
Sent from my XT1060
rocketsaucev2 said:
The software you are running is inferior
Sent from my XT1060
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Lol! My thoughts exactly! ? Trust me I know what I'm doing
Sent from my XT1060