Hello to all. Got my Galaxy Tab 2 P3110 8gb on Monday and found a little problem in it: when I leave at minimum brightness and energy saving mode, in other words, when I leave the screen darker, I see the whole screen with brightness oscillation, increasing and decreasing, is very light but it is annoying. It does not occur when the brightness is higher. To illustrate: it is almost like a lamp burning. To perceive you need to stare at the screen, fixedly. Anyone have any suggestions other than the exchange of the product? Any change in the frequency of refresh of the screen, whatever ... Thanks everyone and sorry for English Google Translator lol
I m also experiencing this issue after the 4.2.2 update .. it noticeably visible in white backgrounds .. I didn't have this issue on 4.1 .. whats your android version BTW ??
appsmarsterx said:
I m also experiencing this issue after the 4.2.2 update .. it noticeably visible in white backgrounds .. I didn't have this issue on 4.1 .. whats your android version BTW ??
Click to expand...
Click to collapse
EXACTLY, only on white backgrounds... Im on 4.1.2 stock. So.. it is software and not hardware? U tried a custom rom?
mualmeida said:
EXACTLY, only on white backgrounds... Im on 4.1.2 stock. So.. it is software and not hardware? U tried a custom rom?
Click to expand...
Click to collapse
honestly I m not sure this is hardware or software issue since I haven't noticed this in 4.1.1 . I m yet to try a custom rom
appsmarsterx said:
honestly I m not sure this is hardware or software issue since I haven't noticed this in 4.1.1 . I m yet to try a custom rom
Click to expand...
Click to collapse
Try a custom rom and tell me here please. I'll try to downgrade to 4.0.4 ... but im not sure cuz i see this issue in white letters("SAMSUNG") at the boot screen.
In the dark gray menu of Youtube's app you can see very well the oscillation even at full brightness.. OMG, is terrible =(
hay, since your device is new try to get a new one without this defect ( this could be a hardware bug too ).. I ve read many complaints about this low brightness flicker issue specially with Nexus 7 .. anyway I ll try to downgrade back to 4.1.1 (or upgrade it to 4.3) next week and let you know ..
Related
As the title suggests i have got a problem with the new rom VoidU S v1.1a [Android 2.3.5 :: Sense 3.0]
The backlight for the 4 touch keys will never turn on! not even in a dark room or when i cover the sensor. The main screen backlight responds just fine to dark conditions and covering the sensor.
I only have this problem on this particular rom, as do quite a few other people. But the majority of people running the rom dont seem to have this??
This is becoming increasingly fustrating as no1 seems to know why some have this issue while others don't
If any1 has any fixes or can point me in the direction of a flashable patch to help sort out some problem files maybe?
also.... the backinghts themselves deffinatly work as they come on when the phone is booting up and always work in conjunction with the sensor with every other rom ive tried!
thanks in advance guys!
Eclipse
Eclipse_Droid said:
As the title suggests i have got a problem with the new rom VoidU S v1.1a [Android 2.3.5 :: Sense 3.0]
The backlight for the 4 touch keys will never turn on! not even in a dark room or when i cover the sensor. The main screen backlight responds just fine to dark conditions and covering the sensor.
I only have this problem on this particular rom, as do quite a few other people. But the majority of people running the rom dont seem to have this??
This is becoming increasingly fustrating as no1 seems to know why some have this issue while others don't
If any1 has any fixes or can point me in the direction of a flashable patch to help sort out some problem files maybe?
also.... the backinghts themselves deffinatly work as they come on when the phone is booting up and always work in conjunction with the sensor with every other rom ive tried!
thanks in advance guys!
Eclipse
Click to expand...
Click to collapse
Sorry mate tried mine tonight in dark room and they came on ,without even having to cover the sensor.
Really sorry but i can offer up no ideas on this one
no problem, hopefully i will get something sorted once some devs see this thread maybe thanks for your input though mate
your not alone, I have this problem too
i seem to be able to get it working now. but only in extremley dark rooms! covering the sensor doesnt work for me atall with this rom
Eclipse_Droid said:
i seem to be able to get it working now. but only in extremley dark rooms! covering the sensor doesnt work for me atall with this rom
Click to expand...
Click to collapse
Same here, if it's pitch black they work fine, but in low light levels (like where you can't see the keys without the backlight), nothing....hopefully there will be a fix soon....
It's the same for me, but as far as I noticed this is supposed to be so with VoidU. I think It's meant to save battery.
Don't you guys know it by heart where the buttons are already?
Yeh I actually noticed that my mates sensation buttons (stock rom) are more sensitive than mine.
His light up in a low level light room, but mine only in a darker room
Sent from my HTC Desire S using xda premium
olyloh6696 said:
Yeh I actually noticed that my mates sensation buttons (stock rom) are more sensitive than mine.
His light up in a low level light room, but mine only in a darker room
Sent from my HTC Desire S using xda premium
Click to expand...
Click to collapse
surely someone can make a patch for adjusting the sensitivity???
Eclipse_Droid said:
surely someone can make a patch for adjusting the sensitivity???
Click to expand...
Click to collapse
I guess they could! Myself, I'm not to bothered about this, as it means that I can save more battery if the backlights stay off!
Because tbh I know where the buttons are , and I can usually make them out in a dark room with little.light
But in a pitch black room it is difficult to see them, but the backlights come on here. So all is well for me!
Sent from my HTC Desire S using xda premium
Hi,
I searched thorugh the forums but found no similar threads.
The video recording on my Samsung Galaxy SL i9003 has suddenly become very dark. The camera is perfect and the video recording used to be perfect as well and have a number of recorded 720x480 videos which are all bright and clear. I am not sure if this has happened because I upgraded to Gingerbread 2.3.6 or because of an app because I've done a factory reset of the phone a number of times and it's still bad. I noticed that when I increase the resolution from 720x480 to 1280x720 it does get a bit better but it still useless for recording.
Can someone please help me.
wwwescape said:
Hi,
I searched thorugh the forums but found no similar threads.
The video recording on my Samsung Galaxy SL i9003 has suddenly become very dark. The camera is perfect and the video recording used to be perfect as well and have a number of recorded 720x480 videos which are all bright and clear. I am not sure if this has happened because I upgraded to Gingerbread 2.3.6 or because of an app because I've done a factory reset of the phone a number of times and it's still bad. I noticed that when I increase the resolution from 720x480 to 1280x720 it does get a bit better but it still useless for recording.
Can someone please help me.
Click to expand...
Click to collapse
Maybe you might have lowerer Exposure Value.
Check and set it to 0.
hi, i also have the same problem with samsung i9003 when i update to 2.3.6, i check the exposure its default. when i install I9003XXKPE 2.3.4 the problem is solved but as its a old rom have some bugs. plz xda help to solve this prob,,
Facing same problem, any solution ????
SikanderKeynes said:
Facing same problem, any solution ????
Click to expand...
Click to collapse
1280*720 use this resolution in bright areas
got new galaxy i9003 on replacement.....
ddkp2/ext4/cwm 5
sirilpta said:
1280*720 use this resolution in bright areas
got new galaxy i9003 on replacement.....
ddkp2/ext4/cwm 5
Click to expand...
Click to collapse
With 1280 X 720, I am having the SAME recording. (The good one)
Compared with friend's XXKPE and My XXKPQ, the same quality on 1280 X720
sirilpta said:
1280*720 use this resolution in bright areas
got new galaxy i9003 on replacement.....
ddkp2/ext4/cwm 5
Click to expand...
Click to collapse
Yes, It's better in 1280*720 but still recording was much better in froyo in low light areas as compare to xxkpn/xxkpq. Recording indoor with low light sucks big time in gingerbread.
this seems to be a bug in the camera on gb roms. I am seriously thinking to get back froyo 2.2.1
sgsI9003 said:
this seems to be a bug in the camera on gb roms. I am seriously thinking to get back froyo 2.2.1
Click to expand...
Click to collapse
I am currently on ddkp2 and i dont have any problem and its very smooth
got new galaxy i9003 on replacement.....
ddkp2/ext4/cwm 5
sirilpta said:
I am currently on ddkp2 and i dont have any problem and its very smooth
Click to expand...
Click to collapse
I plan to test ddkp2 soon I am hoping it solves the car bluetooth bug else froyo xxkb3 is only option for the time being.
sgsI9003 said:
I plan to test ddkp2 soon I am hoping it solves the car bluetooth bug else froyo xxkb3 is only option for the time being.
Click to expand...
Click to collapse
What's the car bluetooth bug? :O
bangalorerohan said:
What's the car bluetooth bug? :O
Click to expand...
Click to collapse
Car bluetooth fails to connect due to access to phonebook bug
here is the thread I posted which has details of this bug.
http://forum.xda-developers.com/showthread.php?t=1389412
The problem with ddkp2 is lack of mods. I will happily shift to ddkp2 if mods like custom kernel, call recording etc are available. Hope there will be a camera mod available soon enough . One thing i don't understand is that there are so many users having GB but there are far less complaints of its buggy video recording.
SikanderKeynes said:
One thing i don't understand is that there are so many users having GB but there are far less complaints of its buggy video recording.
Click to expand...
Click to collapse
Most users were /are desperate to have GB , for them higher version number matters most & they don't much bother about bugs.
I myself long ago requested that rom developers 1st find a stable rom which has least bugs & then root out the bugs & develop custom roms based on that stable rom.
true ! the camera does sum serious damage to the exposure and contrast :\ i couldnt even findmy friends face in a video i recoeded on new years night :\ dam man ! now i gotta try ddkp4 !
i have also the same problem dark video recording!
Same here. The video recording in low light areas is useless. Need a fix :/
same here man, had 2.2.1 before this update which had same problem
Can any1 fix problem ??
I tested this bug as I had indoor (same place) video shot with 2.2.1 xxkb3 versus with 2.3.6 ddkp2 & I can confirm that the brightness/contrast settings are not helping to get better or similar video in dark indoor lighting whereas daylight shots/video are fine.
I wish this problem can be addressed.
today i upgraded my sl i9003 from 2.2.1 froyo to 2.3.6 gingerbread,it also have the same problem.
Camera is completely dark and Video is recording is darker than that.
Any solution guys?
I have Nexus S i9020 and I have this bad problem..
It's started when I flashed AOSP ICS Brainmaster's Mix.. When I locked the phone, I had a strange yellow-green flash on the screen.. I tried flashing different kernels - no effect.. When I tried playing with Voodoo colors - no effect.. The only "semi-cure" was: if you return to "Stock gingerbread colors" that damn screenflash was seen only on the contour of clock and "that slide thing to unlock the screen" (don't know how to name it in english=))..
I thought that it was just the bug of the ROM then.. But when I flashed CM9 latest alpha everything remained the same.. I also thought that it was just a bug of the ROM..
But now I flashed ICS OTA after the downgrade to stock 2.3.6.. And the result is the same to switching to gingerbread colors in Voodoo app on AOSP old ICS ROMs.. I still have the screenflash on the contour on the lock and that "slidething"..
It's really annoying now as I'm starting to think that it is a hardware issue.. But all other functions work just perfect, not any single issue with the screen.. I haven't dropped my phone, haven't kicked it or something (bought it in June)
Can anybody help with this please?
P.S.: there were some similar threads here, but I haven't found the cure..
I tried playing with "Transition animation scale" and "Window animation scale" in Developer Options.. Setting window animation scale to 0.5x solves the problem.. But it turns off CRTscreen fadeout.. So there is something wrong with it on my phone.. I don't want to loose it, it's beautiful..
Any advice please?
I understand that I can only annoy with this question.. But still I don't know what to do! Please suggest any possible ideas, every piece of wisdom could help!
Now I've rooted official ICS, installed Nexus Beam 4.1.0 and flashed Glados 2.1 kernel.. And the green & yellow screenflash once again all over the screen when I lock the phone..
In every other possible way the screen behaves itself perfectly.. But when it turns off I see that damn flash..
Mine does it too
Sent from my Nexus S using XDA App
Mine does it only when i wake the phone and put it back to sleep without unlocking it
Mine has the exact same problem. It doesn't happen in gingerbread but on ics roms, even stock, it does a flash. On stock its lighter and harder to see, but if I change voodoo settings it turns green. I doubt its hardware considering it works fine on gingerbread.
Sent from my Nexus S using xda premium
So we have not only one complaint.. Something must be done to cure it.. It's really annoying as it is the only thing that works not fine on this phone!
Can somebody of the developers please comment on this problem?
Has someone found an answer to this?
Max2mus said:
I have Nexus S i9020 and I have this bad problem..
It's started when I flashed AOSP ICS Brainmaster's Mix.. When I locked the phone, I had a strange yellow-green flash on the screen.. I tried flashing different kernels - no effect.. When I tried playing with Voodoo colors - no effect.. The only "semi-cure" was: if you return to "Stock gingerbread colors" that damn screenflash was seen only on the contour of clock and "that slide thing to unlock the screen" (don't know how to name it in english=))..
I thought that it was just the bug of the ROM then.. But when I flashed CM9 latest alpha everything remained the same.. I also thought that it was just a bug of the ROM..
But now I flashed ICS OTA after the downgrade to stock 2.3.6.. And the result is the same to switching to gingerbread colors in Voodoo app on AOSP old ICS ROMs.. I still have the screenflash on the contour on the lock and that "slidething"..
It's really annoying now as I'm starting to think that it is a hardware issue.. But all other functions work just perfect, not any single issue with the screen.. I haven't dropped my phone, haven't kicked it or something (bought it in June)
Can anybody help with this please?
P.S.: there were some similar threads here, but I haven't found the cure..
Click to expand...
Click to collapse
Max2mus said:
I tried playing with "Transition animation scale" and "Window animation scale" in Developer Options.. Setting window animation scale to 0.5x solves the problem.. But it turns off CRTscreen fadeout.. So there is something wrong with it on my phone.. I don't want to loose it, it's beautiful..
Any advice please?
Click to expand...
Click to collapse
Max2mus said:
I understand that I can only annoy with this question.. But still I don't know what to do! Please suggest any possible ideas, every piece of wisdom could help!
Now I've rooted official ICS, installed Nexus Beam 4.1.0 and flashed Glados 2.1 kernel.. And the green & yellow screenflash once again all over the screen when I lock the phone..
In every other possible way the screen behaves itself perfectly.. But when it turns off I see that damn flash..
Click to expand...
Click to collapse
Raver27 said:
Mine does it too
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
tdtylert said:
Mine does it only when i wake the phone and put it back to sleep without unlocking it
Click to expand...
Click to collapse
apreichner said:
Mine has the exact same problem. It doesn't happen in gingerbread but on ics roms, even stock, it does a flash. On stock its lighter and harder to see, but if I change voodoo settings it turns green. I doubt its hardware considering it works fine on gingerbread.
Sent from my Nexus S using xda premium
Click to expand...
Click to collapse
Max2mus said:
So we have not only one complaint.. Something must be done to cure it.. It's really annoying as it is the only thing that works not fine on this phone!
Can somebody of the developers please comment on this problem?
Click to expand...
Click to collapse
matmat07 said:
Has someone found an answer to this?
Click to expand...
Click to collapse
I've seen this discussed somewhere already, but can't recall where!? But to my knowledge, if I can remember correctly it can be corrected by resetting voodoo control settings back to 2.3.3 defaults! Something to do with gamma settings I think! But obviously you have to be rooted to have & use voodoo control!!
I've tried a couple of those settings, but it never totaly get rid of the problem, it's just less visible. But since I know it's there, i'll always be seeing it XD
Hi everyone,
I had updated my Nexus S to android 4.1 jelly bean yesterday. I am satisfied with everything but the loss of my turn-off screen animation that previously we had for Nexus S (the oldschool TV turn-off animation).
I would like to know if this is a bug during my installation (the installation went smoothly) or android 4.1 purposely removed such animation? Such screen-off effect is one of the reasons that I bought my Nexus S and I am not willing to see it gone. I had searched the forum but so far did not see anyone facing such problem. Kindly advise me what to do.
Thanks everyone in advance!
emperal said:
Such screen-off effect is one of the reasons that I bought my Nexus S ...
Click to expand...
Click to collapse
Really? Good thing it wasn't deciding factor for me, because I don't seem to have it.
there is thread already on this issue.
http://forum.xda-developers.com/showthread.php?t=1785277
Wow. Only a few topics down and you would have seen that massive thread in the previous post.
emperal said:
Hi everyone,
I had updated my Nexus S to android 4.1 jelly bean yesterday. I am satisfied with everything but the loss of my turn-off screen animation that previously we had for Nexus S (the oldschool TV turn-off animation).
I would like to know if this is a bug during my installation (the installation went smoothly) or android 4.1 purposely removed such animation? Such screen-off effect is one of the reasons that I bought my Nexus S and I am not willing to see it gone. I had searched the forum but so far did not see anyone facing such problem. Kindly advise me what to do.
Thanks everyone in advance!
Click to expand...
Click to collapse
Just hold on for a while and cyanogenmod will bring it back.
alien_x said:
Just hold on for a while and cyanogenmod will bring it back.
Click to expand...
Click to collapse
I just updated to jellybean myself and i did notice that that tv animation was gone too. So after some digging U have to go to settings scoll down to developer options and then down to window animation scale and change it to 1x to bring back that tv on/off screen animation back. Also I kept the Transition animation scale at 5x for apple iphone type of visuals.
The only thing that i do not know what is does is the option called Animator duration scale. I played with it from 5x up to 10x and i have not noticed any difference
If anyone knows a explanation would be nice.
I think it may be the "fade in" animations. I'm still trying to figure it out, but I'm pretty sure that's what those are.
emperal said:
Hi everyone,
I had updated my Nexus S to android 4.1 jelly bean yesterday. I am satisfied with everything but the loss of my turn-off screen animation that previously we had for Nexus S (the oldschool TV turn-off animation).
I would like to know if this is a bug during my installation (the installation went smoothly) or android 4.1 purposely removed such animation? Such screen-off effect is one of the reasons that I bought my Nexus S and I am not willing to see it gone. I had searched the forum but so far did not see anyone facing such problem. Kindly advise me what to do.
Thanks everyone in advance!
Click to expand...
Click to collapse
That's seriously one of the reasons you bought the Nexus S??? It's a cool effect, but to be one of the deciding factors of your purchase.....??
Hi everyone,
Thanks for all replies!
For the tv animation it is just one of the many factors that help me in making my purchase, it is just like the choice between super-lcd and super-amoled can be a deciding factor for someone, but not for someone else who cannot see the difference or who does not care. During my comparison regardless of price my friends told me that galaxy s2 has better spec, better screen, better camera etc. but I chose nexus s over s2 for also reasons that the s2 model in my country could not be updated to latest android without rooting.
For the developer option method it works for me too, but I really dnt like all the extra efforts and time needed to solve these problems, it makes me feel like google doesn't take care of its old customers (my perception only).
If Google didn't take care of it's old customers you wouldn't have the JB update to complain about in the first place...
A TV animation just seems like a trivial thing to complain about in all honesty. Its a known bug on the SLCD model and no software is perfect. And is it really that hard to tap a few buttons to fix some settings? I mean, seriously.
chronophase1 said:
A TV animation just seems like a trivial thing to complain about in all honesty. Its a known bug on the SLCD model and no software is perfect. And is it really that hard to tap a few buttons to fix some settings? I mean, seriously.
Click to expand...
Click to collapse
Exactly. The OP put in more effort to make this thread than it took to re-enable the screen off animation.
shinmadhatter said:
I just updated to jellybean myself and i did notice that that tv animation was gone too. So after some digging U have to go to settings scoll down to developer options and then down to window animation scale and change it to 1x to bring back that tv on/off screen animation back. Also I kept the Transition animation scale at 5x for apple iphone type of visuals..
Click to expand...
Click to collapse
This doesn't work on my device.
chronophase1 said:
A TV animation just seems like a trivial thing to complain about in all honesty. Its a known bug on the SLCD model and no software is perfect. And is it really that hard to tap a few buttons to fix some settings? I mean, seriously.
Click to expand...
Click to collapse
is it really that hard to understand that tapping a few buttons won't fix anything? adjusting the animation scales and whatnot will fix bull****
shinmadhatter said:
The only thing that i do not know what is does is the option called Animator duration scale. I played with it from 5x up to 10x and i have not noticed any difference
If anyone knows a explanation would be nice.
Click to expand...
Click to collapse
Well... that 1x solution didn't work which was already by default on me but increasing 5x and 10x did work.
Sedge.One said:
Doesn't work for me.
All animations are set to 1x bx default, and changes do not affect the behavior of the screen-off-animation.
Click to expand...
Click to collapse
asphantix said:
is it really that hard to understand that tapping a few buttons won't fix anything? adjusting the animation scales and whatnot will fix bull****
Click to expand...
Click to collapse
I just wish I knew why adjusting the rate at which those animations occur seems to somehow fix the issue for some. My complaint was more along the lines of people not wanting to take the effort to attempt to even get into the menu to find those settings. Of course hitting buttons ain't gonna solve anything . Well in most case it wouldn't work. Haha. Speaking of, when I originally disabled my animations, my app drawers animations stopped. Never did that in ICS.
My animation still works...
So to clear up the confusion: This bug only concerns the SLCD version. For those who don't know it, AirKernel seems to fix the problem, it did it for me and I'm running Euroskanks CM10.
Aktifit said:
So to clear up the confusion: This bug only concerns the SLCD version. For those who don't know it, AirKernel seems to fix the problem, it did it for me and I'm running Euroskanks CM10.
Click to expand...
Click to collapse
I am using latest alpha - 0.8 - cm10 rom from kalim for a week and crt animation was gone.
Today I flashed latest hypothalamus-07.26.zip kernel and animation is back on my slcd i9023 :good:
063_XOBX said:
If Google didn't take care of it's old customers you wouldn't have the JB update to complain about in the first place...
Click to expand...
Click to collapse
emperal said:
Hi everyone,
I had updated my Nexus S to android 4.1 jelly bean yesterday. I am satisfied with everything but the loss of my turn-off screen animation that previously we had for Nexus S (the oldschool TV turn-off animation).
I would like to know if this is a bug during my installation (the installation went smoothly) or android 4.1 purposely removed such animation? Such screen-off effect is one of the reasons that I bought my Nexus S and I am not willing to see it gone. I had searched the forum but so far did not see anyone facing such problem. Kindly advise me what to do.
Thanks everyone in advance!
Click to expand...
Click to collapse
the effect will only works on nexus s amoled screen, those models with SclearLCD like i9023...you can't see the effect because the timing of turn off the back light happen earlier than the effect. The TV off effect is actually there, but without backlight, we can't see it...you will see it sometimes, because of delay of the backlight due to hardware slow response... have a nice day, guys... pass this to google team and xda team, this will help them easily fix it ...!
Hi guys, I need something confirmed. When I go to settings with brightness full I get these moving lines going up and down as if the screen is broken, and if I rotate my tab to landscape the lines are in same place but going the other way! So how can it be screen? , but on stock I dont get it, I think maybe contrast on cm might me diffrent as the black on cm looks diffrent to stock black. Maybe someone could tell me if they have the same problem in cm? Also if im to get my tab fixed they will have to see the problem or they wont repair, but I get this to happen on stock rom.......
Before anyone says reflash rom dont as its not a bad flash or anything like that.
Thanks, maybe someone could help me.
sent from my xperia neo v
Sent from my MT11i using XDA Premium 4 mobile app
Maybe you should first take a screenshot but i am not sure can it be seen on pic but at least try to get pic to here so we can help more. I don't have that problem even i have too cm 10.2.
T3ER said:
Maybe you should first take a screenshot but i am not sure can it be seen on pic but at least try to get pic to here so we can help more. I don't have that problem even i have too cm 10.2.
Click to expand...
Click to collapse
Its be confimed by 4 users now. Screenshot isnt possible I dont think. Im currently on stock and this does not happen. I think the screen cant display the contrast very well, or maybe cm limits the screen power! I have made the problem clear to people on the cm10.2 thread, maybe you have bigger tab? Mine is the 7" p3110
sent from my xperia neo v
mitchellreece said:
Its be confimed by 4 users now. Screenshot isnt possible I dont think. Im currently on stock and this does not happen. I think the screen cant display the contrast very well, or maybe cm limits the screen power! I have made the problem clear to people on the cm10.2 thread, maybe you have bigger tab? Mine is the 7" p3110
sent from my xperia neo v
Click to expand...
Click to collapse
Yeah i have 10.1 inch screen so that is probably reason.