yashsingh1/xdaforums huggingface dataset:
[Galaxy Tab 7.7 General] questionmark:
This is correct especially the Astronomy references to planetary alignment!

I how somehow pictures and took my old pentax reflex attempting to display circles. As you know I do have CIRCLE in total pitch black my eyes adapting slowly the screen displaying BLACK picture (lcdtest). In this condition the screen is NOT totally black but radiate some kind of fluorecent light with circles appearing.

I'm not a good fotographer and it shows ... but in total black without stands its quite a challenge IE like Astronomy pictures.

So not sure if those pictures say something but I would believe I'm the one 1% VERY lucky out there...when I bought it should have bought a loto ticket :)

The device is 3 weeks old with intensive daily usage.

1 screenfilter setting : used for 2 and 3 attempting to show burnin.

on gray you see nothing but used the same orientation that I use normally. On 3 blue you can notice top and left shadows I believe from the task bar...the bun in...I guess

Believe or not but the screen look more consistent and even in real for all colors.

ALSO I need to use screenfilter from the market to apply some gray (low down the intensity).

2 gray was taken with : PENTAX K100D f/4.5 1.5 exp iso-400

3 3 sec exp iso 400

4 is me trying to capture circle that I could not see anyway in the condition I was. I did not use screenfilter (disregard file name mistake from me) and had the brightness in setting to the minimum. The room I took the picture was not totally dark, but dark enough I had to enable the status bar so I could find the tablet in the view finder of the camera.

this was taken with 2 sec exposure at 400 iso

Again I do see CIRCLE my eyes adapting in total black.... but would not know how to capture with my photo skill and without stands. Kind of deeps space imaging :)

5 black level test using minimun brightness setting ( not filter at all in movie mode) exp 1.5 sec at 400 iso... I let you judge this one... the first row quit though but 4, 5 I see...

6 using screen adjuster on market and see what can be tweaked here are the setting

7 the result using sceeen adjuster and brightnest set to minimum. The color of grey might look odd and uneven but in reality that was different.

So not sure what all this tells... But I have hard time to complain about the display so as I say lets seen in 6 month time... Surely we can read oled are subject to burn in... but what is reasonable... I would not bet but believe that in 6 month time I still would need

low brightness + screen filter to see status bar shadow...so with a colorful desktop I doubt...

So am I in the 1% lucky one? or the picture does not tell nothing and are useless if last then I really don't mind as I'm happy ... I ought to attempt explaining what I see and owed picture...

I know you can see circle using picture, you show your picture I had your device I'd be indeed really really annoyed, are you really sure 99% are wasted hence no point for you to chase a new one?

Cheers
[Galaxy Tab 7.7 General] shazoom:
Checked out the images metioned in the feedback thread. I got some burn in too :-( Oh well, my advice to myself is to get over it and I don't let it ruin my enjoyment of an otherwise great device.

For those interested, and propably already mentioned, Honybar works. It essentially provides an invisible button to show/hide the status bar.
[Galaxy Tab 7.7 General] NewForce:
Circle? What Circle? I couldn't even see one with Queationmark photos.

In normal usage, particular web page surfing, photo and video viewing hardly see any circle on Super AMOLED screen. Could it be the LED backlight hotspot native behavior causing all the fussiness?

Or it's just, "picky people being picky" situation? If this was the case, my advice is, you should get over with it. Since it done nothing on normal viewing mode, enjoy more of the screen contents would be a more proper approach instead of putting yourself into various depression mood with test pictures or softwares. Doing that also help making your life much easier. We got better things to worries about than just this circle.
[Galaxy Tab 7.7 General] EarlZ:
@questionmark

Im not using the screen filter app since i dislike the grey overlay it adds to the screen, also lowest brightness is already dim enough for me.

On your photos I can see that the status bar shows discoloration from its left and right edges, which is not normal regardless of how subtle it is, on your grey images I see some green discolorations, is that caused by the camera? I also see the famous vertical/horizontal lines on the grey image. If you need screen filter to show those issues then you've got a great unit. I've checked more than 20 already and lost count, all of them show very obvious discolorations at the sides some are even obvious enough that you can see that surprised look from the sales rep's face.

Samsung is getting 1 replacement delivered to my place, if its still a dud Im returning the product.

Why would you assume that all of the screens have circle marks?

So you admit to see it but its not that visible. SAMOLED has no backlight.

Be the judge of my images, no special settings on the camera aside on the grey needed to take it at 1.5seconds exposure. The reset are just taken with automatic mode in normal lighting conditions. camera is very old sony dsc p200.

http://xdaforums.com/showpost.php?p=23529783&postcount=27
[Galaxy Tab 7.7 General] pikulu:
@EarlZ,

So strange,but i thought that as samoled plus is the more advanced technology than samoled,there are chances of burn in of samoled only not plus! !but i was wrong.

How many users do complain about the burn in on note?I think u may be lucky for not having burn in ,but others may have?
[Galaxy Tab 7.7 General] EarlZ:
No clue on the burn in with the note, you might wanna post a thread on that part of the forum.
[Galaxy Tab 7.7 General] NewForce:
Aha, finally seeing 'the circle'. I've never realize there's any circle on Super AMOLED Plus screen, even with my old S2 which my wife using it for 5months. Well she didn't complaint of anything during the time she having great fun with it.

On my current 2 white Galaxy Note Super AMOLED HD (without the Plus), so far so I never check for 'the circle' or 'the dark side' because Me and my wife are busy having great time with it instead faults finding.

Maybe we are just the type of people who are, 'more easy going that willing to settled for issue that was neglectable, when the excitement that the device bring are so great. It's just a smartphone or tablets. After all nothing is perfect.'
[Galaxy Tab 7.7 General] GOF007:
+1 (for a hundred times)
[Galaxy Tab 7.7 General] EarlZ:
First of all the Galaxy Tab7.7 is not a Galaxy S2 or a Galaxy Note, you are covering 3 different screen technologies here and you are also assuming that the S2 and the Note suffers the same issue which is absolutely wrong, though there were rare reports on the Galaxy S2 about the circle marks but not as common as it is on the Tab7.7, do not use your Galaxy S2 or Note as a basis for this issue, different devices different screen technologies.

So going by your definition, watching movies, accessing the market and going into the settings menu is "faults finding" since I see the circle marks there and the discolored sides almost every where, I wonder what kind of limited usage should I be doing to 'avoid' these faults?

Then again there is also a difference of expectation and standards, yours is just totally different than mine and I can understand that, nobody is looking for perfection just a screen that is well with in spec.. say like your Galaxy Note's screen.

EDIT:

Bottom line is difference of expectations and standards, lets just go back to the topic and if you wish to continue this discussion just go to the proper thread and move post there with the a quote.
[Galaxy Tab 7.7 General] NewForce:
Hey EarlZ,

Omg.. you're thinking too much. Don't get me way too wrong about my intention here. I am not criticizing how you reacted, I'm just telling you the type of person I am. Yes agreed with you, we're different in expectation. Anyway, we are just doing some discussions, nothing personal, calm down will ya? :)
[Galaxy Tab 7.7 General] EarlZ:
Im just telling you whats on my side as well, not being defensive or taking thing personally and im very relaxed:)
[Galaxy Tab 7.7 General] questionmark:
Hi EarlZ

Yes I did not notice on the picture the discoloration of the status bar and indeed they do show in my pictures but don't recall seeing them or being strike by it on the screen while making pictures neither now using the device. So not sure if it is the camera? Will check further. The green discolorations of gray image that I notice in my picture on black level test is definitely the camera.. I mentioned in real it looks even and fine at least for my eyes.. About vertical and horizontal line on full gray : actually using white screen largest white screen + screen filter I really did not notice anything... And even now looking again my picture, and not sure what you mean exactly. Sorry In real it is also much more even.. The picture are jpg resized at 800x600 using irfanview and think 80% quality. It maybe it is artifact compression of jpg ie in the blue screen I see some lines not talking about darkness on the top and left side and those are present in real the burning I believe.. I may try to do a full picture raw of a gray screen, can you point me out the link of it please your gray? I woukd use minimum brightness and no scrennfilter

I use scrennfilter only to show what I believe to be marks of burning.

The reason of me doing that is to say

1 yes there are defects circle but unable of capture them and possible burnin. Again really hard for me to see.. Need to use screen filter for burnin

2 I don't think 99% of screen are defective or as bad as your seems to be as you are able to capture them and show circles in images not only gray or black... That was my point of trying doing pictures.

Because we are on Ipad3 screen vs 7.7 I can see picture of ipad3 with screen bleeding in image that seems to be easy to capture on camera even in non total dark room of course me assuming here.. In comparison my screen is black full black unless I'm spending couple sec under the cover total pitch black then I see screen emits light like crt does for a few when switched off at this point I start to distinguish circles... I think I could capture with a camera stand and exp of more than than 5 sec at 800 iso? But I feel it is pointless.

All I can say is that it is hard for me to complain about it and maybe lucky and I truly wish you where as other.

The luck here is already to afford gt 10.1 then 8.9 and finally 7.7 the other device gave away to family.. I read magazine and my bought of 7.7 was a caprice and before seeing it I thought no ics! samsung bye bye after all my buy used will not get a peny... But I felt for it... What I realized now is my eyes reading magazine on 7.7 are far less tired than the 8.9... Every time I open it since 3 weeks now is always a wow... I guess it is because I spend more tan 8 hours a day for work behind 2 relatively cheap 1080p monitors..

To summarize it I love it and wish most if not all would be as happy... When you like u like to share as much as when you hate... Generally discontented people complains more in general. I I'm here to balance on the feeling as much as possibly in an objective way.

Cheers
[Galaxy Tab 7.7 General] NewForce:
That's great. We're cool! :)
[Galaxy Tab 7.7 General] EarlZ:
@questionmark

Since you dont see any issues on your end why look for them? If you still want the grey images its on the screen feedback thread, most of them are there.
[Galaxy Tab 7.7 General] holyrabbit:
the big fight!

Retina Display by Apple

Super AMOLED Plus by Samsung

who's gonna win?

which side must win?

IMHO, i don't think we could compare with to straight about this product, maybe some people already know it or don't

Retina Display & Super AMOLED Plus made by Samsung,

sorry..not only retina display, ipad 2 and ipad 1 also Samsung made it.

have you ever try to compare SGSII vs Iphone4s? well, i might say i choose Iphone in different way, but sometimes i regret it and i choose SGSII :D

too close to compare it, but now when i have 7.7, everything goes complete i 100% choose this display either ipad 3 retina display, the brightness and nice color show up at Super AMOLED Plus, Retina Display more show natural color.
[Galaxy Tab 7.7 General] NewForce:
Nope, iPad 1/2 IPS-LED display was by LG and Sharp.
[Galaxy Tab 7.7 General] holyrabbit:
so LG? oh i just read link

Link

if it is true LG or Sharp, more than worst for me :D

equal Samsung or Chimei Innolux than LG or Sharp, for me
[Galaxy Tab 7.7 General] NewForce:
holyrabbit, Thanks for the extra info. Anyway, the main vendor for old iPad screen was still LG, Samsung next and Chimei Innolux only supply a small percentage.

If LG and Sharp finally managed to overcome their yield issue, they may start to ship screen for new iPad too in the near future. Given Apple unfriendly relationship with Samsung and business strategy, it always trying to source for more parts supplier vendor.
[Galaxy Tab 7.7 General] chan005:
Is that what the difference is. It just look better to me. Never figured out why. I do that when I watch a few TV shows or a movie on a long flight. The rest of the time, I like the over saturated screen.
[Galaxy Tab 7.7 General] NewForce:
+1, I like that too :)
[Nook Touch General] apeine:
Just saw this one at "the ebook reader" blog:

link

BN.com info:

What's new in Ver 1.1.2?

The NOOK Simple Touch Ver1.1.2 update provides minor system enhancements.

I guess it won't be this time that we'll see multitouch!!!
[Nook Touch General] Googie2149:
Hopefully we get multitouch.
[Nook Touch General] case-sensitive:
Accorinding to http://bookclubs.barnesandnoble.com...ased/m-p/1307783/message-uid/1307783#U1307783 this update fixes wifi issues (limited to selected wifi routers).
[Nook Touch General] Renate:
Running 1.1.2

Everything back to normal.

My library book is still on the same page.

I would recommend doing a backup beforehand.

Maybe write yourself a nice script or makefile to redo your personalizations.
[Nook Touch General] case-sensitive:
Care to share with us exactly what you did? Specificially,

* did you simply go to BN.com and manually update? and if so, did you unrooted your device first?

OR

* did you device got OTA update? and if so, did you unrooted our device first?

Thanks!
[Nook Touch General] Renate:
I just went to http://www.barnesandnoble.com/u/Software-Updates-NOOK-Simple-Touch/379003175/

Downloaded nook_1_1_2_update.zip

Stuck it in /media (that is the root of the first normally mounted partition on USB).

It updated, then booted up stock.

Rebooted on system SD card and replaced uImage and uRamdisk from previously.

It booted up rooted.

Ran a big makefile with lots of ADB commands to fix everything the way I like it.

I had kept good notes on everything that I had customized.

I don't use any jar mods.

P.S.Don't forget to restore /system/bin/su and do a chmod 6755
[Nook Touch General] skyjedi:
UI downloaded the update put it in the root of the Nook mount. It goes to sleep flashes the screen black for a moment and then reboots. It doesn't update and it deletes the update file on the nook. Any Ideas?
[Nook Touch General] Renate:
I don't know. Did you check logcat?

Mine went in without a hiccup.

Do you have modified jars?
[Nook Touch General] skyjedi:
I just reset the nook using the two bottom buttons during boot. Update went fine after that
[Nook Touch General] mali100:
uRamdisk content hasn't changed, so the rooted uRamdisk files from the 1.1 release can be used.
[Nook Touch General] bobstro:
Mine was doing the same. Since I had nothing important on it, I did the 8 reboot reset and an unregister and wipe. Then it updated properly.

Hopefully, there's an easier way, but I was impatient and needed to clean it up anyhow.
[Nook Touch General] Renate:
Here's what's different between versions 1.1 and 1.12:

/kernel
/kernel-recovery
/MLO
/ramdisk-recovery.img
/ramdisk.img
/romrestore.zip
/u-boot.bin
/recovery/recovery-from-boot.p
/recovery/etc/install-recovery.sh
/system/build.prop
/system/app/DeviceManager.apk
/system/bin/AacEncoder_Test
/system/bin/debuggerd
/system/bin/framebuffer_test
/system/bin/G711EncTest
/system/bin/G726EncTest
/system/bin/G729EncTest_common
/system/bin/hal_client_test
/system/bin/hal_server_test
/system/bin/iLBCEncTest_common
/system/bin/JpegTestCommon
/system/bin/JPEGTestEnc_common
/system/bin/NBAMREncoder_Test
/system/bin/pvr2d_test
/system/bin/pvrsrvinit
/system/bin/services_test
/system/bin/sgx_blit_test
/system/bin/sgx_clipblit_test
/system/bin/sgx_flip_test
/system/bin/sgx_init_test
/system/bin/sgx_render_flip_test
/system/bin/testwrap
/system/bin/texture_benchmark
/system/bin/VidDecTest_common
/system/bin/VPPTest_common
/system/bin/WBAMREncoder_Test
/system/bin/sgx/bc_example.ko
/system/bin/sgx/omaplfb.ko
/system/bin/sgx/pvrsrvkm.ko
/system/etc/NOTICE.html.gz
/system/etc/factory/barcode_build.bmp
/system/etc/security/otacerts.zip
/system/etc/wifi/tiwlan_drv.ko
/system/framework/am.jar
/system/framework/android.policy.jar
/system/framework/android.test.runner.jar
/system/framework/bmgr.jar
/system/framework/bncloudapi.jar
/system/framework/com.bn.app.crypto.jar
/system/framework/com.bn.app.deviceinfo.jar
/system/framework/com.bn.authentication.jar
/system/framework/com.bn.cloud.jar
/system/framework/com.bn.gpb.jar
/system/framework/com.bn.provider.utils.jar
/system/framework/com.bn.waveformdownloader.jar
/system/framework/core.jar
/system/framework/ext.jar
/system/framework/framework.jar
/system/framework/ime.jar
/system/framework/input.jar
/system/framework/javax.obex.jar
/system/framework/monkey.jar
/system/framework/pm.jar
/system/framework/services.jar
/system/framework/svc.jar
/system/lib/libbndeviceinfo.so
/system/lib/libglslcompiler.so.1.1.15.3172
/system/lib/libIMGegl.so.1.1.15.3172
/system/lib/libnetutils.so
/system/lib/libpvr2d.so.1.1.15.3172
/system/lib/libpvrANDROID_WSEGL.so.1.1.15.3172
/system/lib/libPVRScopeServices.so.1.1.15.3172
/system/lib/libsrv_init.so.1.1.15.3172
/system/lib/libsrv_um.so.1.1.15.3172
/system/lib/egl/libEGL_POWERVR_SGX530_125.so.1.1.15.3172
/system/lib/egl/libGLESv1_CM_POWERVR_SGX530_125.so.1.1.15.3172
/system/lib/egl/libGLESv2_POWERVR_SGX530_125.so.1.1.15.3172
/system/lib/hw/gralloc.omap3.so.1.1.15.3172
/system/media/books/Quick_Start.epub

:eek: Don't tell me that the Quick Start guide has been changed! No!!!
[Nook Touch General] Googie2149:
Really? Guess that means I can continue working on my Rooting method then.
[Nook Touch General] mali100:
Yes. The uRamdisks itself have a different md5sum, but if you extract them, the content is exactly the same
[Nook Touch General] AzulmArinO:
This update has a SERIOUS BUG. It spoils the Back-to-book button and the Reading Now link in the home page by taking you back to page one of the last book you had opened. Fortunately you still can return to where you had left reading by opening the book directly from the library.

Is there a way to go back to 1.1.0 firmware?
[Nook Touch General] Renate:
"Home Page"? What's that? The thing with all the ads on it?

I haven't been there in months. I just use the upper left hand corner of the action bar.

Yes, the last read is flakey and sometimes pops you back to page one.

Whether this is happening more or less with this update is unclear.
[Nook Touch General] bobstro:
I am not having that problem with 1.1.2. Tapping either the Reading now cover, or the last read button at top-left takes me to the correct page in my current (sideloaded) epub book.

I had some problems with other epubs always showing page 1 on Reading now on v1.1.0, but I need to reload those titles to test.

From the descriptions I've read, no changes to any of these functions has been formally identified for 1.1.2. Were you having any problems with that same title on older firmware versions, or is this a new ebook you started reading since the update? The "page 1" problem on the home screen is a known issue with the NST.
[Nook Touch General] mali100:
Here is a patched framework.jar that should allow market registration. Untested!
[Nook Touch General] Guyman2:
Mine does that in 1.1.0 with certain books only. So maybe its not a 1.1.2 bug.
[Nook Touch General] Googie2149:
This has been a bug since 1.1.0, but only with a few (sideload only) books.
[Nook Touch General] case-sensitive:
Thanks for your reply. I'd be most appreciative if you could clarify a few steps:

> Rebooted on system SD card and replaced uImage and uRamdisk from previously.

By system SD card do you mean "noogie.img"? Also, how do you replace uImage and uRamdisk? I remember reading somewhere that incorrect replacement of these files would result in bootloop...

I need to use my device for a work trip shortly; your help and assistance is most appreciative.
[Nook Touch General] Renate:
@case-sensitive:

Yes, noogie.img on an SD card will give you a system and access to the internal flash.

Some reported that the upgrade didn't even touch uImage or uRamdisk.

I didn't even bother to check, I just copied the two backup files over it.
[Nook Touch General] case-sensitive:
Thanks! I turn off my NST, insert the noogie.img SD, and then connect the NST to my computer. However, I can't find uImage or uRamdisk. Where might I be able to find these two files?

I did find these two files in the touchnooker 2.1.31 SD. I assume that once I find the two files on my NST, I just replace them with the corresponding files in touchnooker?

Thanks!
[Nook Touch General] Renate:
I'm confused. If you are running noogie on an SD card and the display says "Rooted Forever" then your boot partition should be mounted on your PC. uImage and uRamdisk should be there, along with a bunch of files like charging.pgm. I believe it mounts two partitions. Are you sure that you have the right drive letter?

More to the point, is your Nook still rooted after the 1.12 upgrade anyway?
[Nook Touch General] case-sensitive:
I've tried several different ways to update to 1.1.2 and then reboot, but none of them work:

(1) Restore the NST back to unrooted, stock 1.1.0, update to 1.1.2, and then use touchnooter 2.1.31. Result: the NST goes back 1.1.0 and rooted

(2) Restore the NST back to unrooted, stock 1.1.0, update to 1.1.2, and then (after inserting the noogie.img SD and reboot) replace uImage and uRamdisk (from the touchnooter 2.1.31). Result: the NST hanged at the boot screen

(3) Take rooted NST 1.1.0, inserted noogie.img SD and reboot, put the BN 1.1.2 zip in the root directory, and let the NST reboot/update itself. Result: gets back to original rooted 1.1.0

I probably misunderstood what I'm supposed to do with (2) (and other steps)... Thanks for your help!
[Nook Touch General] Renate:
I'm even more confused than ever.

I don't see how in processes #1 and #3 how it ever could get rolled back to 1.1.0 after being happily in 1.1.2

That is, unless it's going into recovery and restoring an older version somehow.

In process #2 I can only guess that there is something wrong with the files.

uImage should be 1.8 Megs or slightly more. Mine is 2.6 Megs because it has all sorts of junk in it.

uRamdisk should be around 185K or so.

The 1.0, 1.1.0, 1.1.2 are all minor changes and they should all work with any two working "U" files.
[Nook Touch General] case-sensitive:
I wonder if I have a corrupted noogie.img -- e.g. after I insert the noogie SD and reboot, I cannot see the folder with the u-files in XP (but I can, in linux). Unfortunately noogie is not longer available via nookdevs.com (multiupload problem). Could anyone upload it to xda? Thanks!
[Nook Touch General] ApokrifX:
Could you tell what was changed there? :)