Related
Update on Issue #1: 2010.11.29
This issue appears to affect all unlocked Froyo devices on the Rogers network. It MAY affect all Froyo devices, regardless of network lock status, but we have been unable to confirm this (yet) on the only Froyo device locked to Rogers - The Acer Liquid e.
There are currently 4 threads (that I am aware of) scattered around XDA. As this problem affects multiple devices I will start posting updates in the General Discussion/Q&A thread, and will stop posting updates here. If you are looking for more information, please refer to:
Main Thread: http://forum.xda-developers.com/showthread.php?t=845152
Other Device Specific Threads:
N1: http://forum.xda-developers.com/showthread.php?t=849969
DZ: http://forum.xda-developers.com/showthread.php?t=848793
SGS: http://forum.xda-developers.com/showthread.php?t=850784Wanted to see if this is isolated to my phone or if others have these issues.
_________________________________________________________________________________________________________________
Phone is Rooted, S-Off, Paul Obriens Custom ROM with HTC Sense on Rogers Network.
1. Cannot get a location lock unless I use GPS, it will not give me a location in Maps at all unless I turn on GPS.
2. Display is set to Automatic Brightness but the screen stays the same no matter if i'm in direct sunlight or in a pitch black room
3. Have SMS Timestamp fix but am still getting messages which sometimes show hours behind or hours ahead
Bump
Sent from my HTC Vision using XDA App
For the GPS issue, you should post this up in the thread on Paul's ROM, to see if others have the problem. I presume your GPS worked fine on the stock ROM ?
Others have reported issues with the automatic brightness setting. I suspect it doesn't work at all, even on the stock ROM.
Also have issue with automatic brightness adjusting not working.
ayewhy said:
Also have issue with automatic brightness adjusting not working.
Click to expand...
Click to collapse
I don't think I've seen anyone saying that it *does* work for them in the stock ROM. Anyone ?
steviewevie said:
For the GPS issue, you should post this up in the thread on Paul's ROM, to see if others have the problem. I presume your GPS worked fine on the stock ROM ?
Others have reported issues with the automatic brightness setting. I suspect it doesn't work at all, even on the stock ROM.
Click to expand...
Click to collapse
Will do, hopefully it can get fixed. The GPS works fine, locks fast. It's when I don't have GPS enabled that it won't give a location using the wireless network now.
Wonder if making a single thread regarding auto brightness would be good. I've emailed HTC and they gave the typical "pull battery, factory reset" garbage. And after "exhausting" those "fixes" they simply say to call and RMA the device...ugh
It works on my DZ(stock ROM), but not flawless. It adjusts the brightness when I shine on the sensor with a flashlight, but it won't change back to 'normal' when I move the flashlight away. It changes back after going to sleep and unlocking. Also, it won't go below approx. 50%.
Edit: I checked it again and it does change back, it just takes a few seconds.
Sent from my HTC Vision using XDA App
andijvie42 said:
It works on my DZ(stock ROM), but not flawless. It adjusts the brightness when I shine on the sensor with a flashlight, but it won't change back to 'normal' when I move the flashlight away. It changes back after going to sleep and unlocking. Also, it won't go below approx. 50%.
Edit: I checked it again and it does change back, it just takes a few seconds.
Sent from my HTC Vision using XDA App
Click to expand...
Click to collapse
Can you take a video possibly of this, what are the details of your phone? Rooted? S-Off?
The screen will "dim" when the backlight times out but it never actively dims because of the sensor on my phone.
Stealth1985 said:
Can you take a video possibly of this, what are the details of your phone? Rooted? S-Off?
The screen will "dim" when the backlight times out but it never actively dims because of the sensor on my phone.
Click to expand...
Click to collapse
My phone is completely stock. The dimming might be too little to be noticed, have you tried to shine a light directly in the light sensor, while being in a fairly dark room, so that you can observe the maximum change of brightness?
You could also download one of the sensor apps out there and see if the sensor works. Mine says light level 0 in a darker room, and max when i shine a light in the sensor.
I doubt the sensor is very useful though, as the brightness only goes from approx. 50 to 80%...(going from zero light to lightest) might be better if these values could be set.
About the video, the only camera I have right now is the DZ, so I'll see what I can do.
Sent from my HTC Vision using XDA App
andijvie42 said:
It works on my DZ(stock ROM), but not flawless. It adjusts the brightness when I shine on the sensor with a flashlight, but it won't change back to 'normal' when I move the flashlight away.
Click to expand...
Click to collapse
That's interesting, thanks, I'll give that a try.
Sounds like the auto-brightness and the keyboard/cap buttons backlight (both of which use the light sensor) might both suffer from the same thing - i.e. very poor programming/implementation.
I have issues 1 and 2 (but not 3).
I would like to add that auto-brightness seemed to work fine when I (briefly) used CyanogenMod RC2, though I have no other Android devices to compare with.
I dumped the stock Sense ROM pretty quickly so this might have worked fine on the original ROM.
This definitely sucks, what ROM do you have that the location doesn't work too?
Pretty disappointed that I'm having these issues and HTC's response is send it in. I am not paying to re-unlock another phone because they can't make something that fully works.
Sent from my HTC Vision using XDA App
I have some bad news for you about point 1. It looks like a number of people on various unlocked android devices (N1, Desire, SGS i9000m) are experiencing the network location problem.
http://forum.xda-developers.com/showthread.php?t=845152
There is w (crappy, but still functional) work around, but...
For most of us it started sometime around Nov 14th.
It has some pretty unhappy implications for those of us who prefer android and want a top-end phone.
Good luck.
Damn Rogers seems to have screwed things up.
Sent from my HTC Vision using XDA App
Yeah. Maybe.
It seems to be an interaction between Rogers and unlocked android phones. We don't know whether it is all unlocked android phones, though, or even if it is specific models (i.e. would an unlocked Rogers Captivate have the same problem), or a specific OS (i.e. we don't know yet if the problem happens on eclair - while not directly useful to the DZ owners, it would at least help to pinpoint the problem and might help to get Google to step-up).
There are just too many unknowns, and how do you speak with someone with sufficient knowledge to speak intelligently? Rogers tech support hasn't been much help, and Google and Rogers seem to want to bounce the problem between each other.
Auto-brightness: Using My sensors free market app, checked the light sensor. All the sensors but the light gives live info. Looks like it doesnt work at all, like not switched on.
Uk htc z, stock rom.
-- sent from htc z using xda app
tbalden said:
Auto-brightness: Using My sensors free market app, checked the light sensor. All the sensors but the light gives live info. Looks like it doesnt work at all, like not switched on.
Click to expand...
Click to collapse
Could be that the app doesn't work with the DZ light sensor properly though ? I know my light sensor does something, because the keyboard/cap keys backlight turns on and off kind of randomly depending on light levels (and if you block the sensor then the lights come on).
Thats true. It happens here too. But still might be related...
-- sent from htc z using xda app
Ok.with very bright flash light around it gives data with the my sensors app. Then its the levels its moving light level between,as mentioned in this thread before.
-- sent from htc z using xda app
tbalden said:
Ok.with very bright flash light around it gives data with the my sensors app. Then its the levels its moving light level between,as mentioned in this thread before.
Click to expand...
Click to collapse
Cool, kinda sounds like it works, just very very badly.
Hello,
I recently bought an Incredible for my girlfriend on craigslist. It was only 2 months old (in great condition to boot). Either way after flashing CM7.0 I noticed that the automatic backlight setting did not work. I just set it to around 25% and figured I would figure it out later. After 7.0.2.1 came out I flashed that and no change. I then decided to figure it out. It seems that after waking the sensor doesn't work unless really flooded with direct bright light (such as the flash light from my incredible). After that it works mostly as intended.
Here is how I tested it. I lock the phone when in the custom light levels screen. When unlocking the Sensor (filtered / raw) is at 10/10 and will not change no matter what I do until I hit it directly with a bright light. I believe that it will also change eventually letting it just sit. Most of my tests involved using bright light sources. After that the sensor works just fine and changes almost instantly when I cover it with my hand and then move it into regular room light. Is this a known issue? I checked the bug tracker briefly but did not see anything. I have had two others test. One had fine light sensor response the other had the same issue as me.
Anyone have any idea?
I've noticed that the automatic brightness does work, but at the default levels its way too dark. Had to go info the menu and bump up all the levels and it's alright now. Doesn't seem like it works quite as smoothly as it does on sense roms but I haven't gone through and tweaked everything perfectly, I honestly don't understand all the adjustments that are available.
Sent from my ADR6300 using XDA App
k_nivesout said:
I've noticed that the automatic brightness does work, but at the default levels its way too dark. Had to go info the menu and bump up all the levels and it's alright now. Doesn't seem like it works quite as smoothly as it does on sense roms but I haven't gone through and tweaked everything perfectly, I honestly don't understand all the adjustments that are available.
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
It does work but the sensor doesn't respond in a timely fashion.
Have you tried changing the sample interval?
Sent from my ADR6300 using XDA App
What settings are you using? I.E. do you have filtering enabled? What is your window length? Sample interval? Etc.
I've never seen anyone discuss this as a CM7 bug. Based on the way you are describing it, it sounds like you might just need to tweak your settings.
For example, if your window length is very long and sample interval slow, that might be why your readings are taking so long to update. As for why the reading changes as soon as you hit it with a bright light, you could be tripping the reset threshold.
Just in case you haven't checked it out already:
Numerical explanation of the CM7 automatic backlight settings
I will check when she gets off work. All I did was flash cm7. I didn't mess with light sensor settings.
Ok... I have checked it... Not good. Sample intervals were set to 1s. Even still they were not enabled. Messing with the settings didn't yield any results either. It was still sluggish until hitting it with bright light...
I would search, there are multiple threads around where people have posted their settings, I would try those then tweak it to your liking. Also check out byrong's thread, the man knows his stuff.
Sent from my ADR6300 using XDA App
The automatic brightness sucks on stock as well. Just turn it off. You can't see the screen in bright sunlight no matter what the setting is, and you can see it just fine at 64/255 inside. All the automatic brightness does is give you a headache.
Hi all.
I'm reading a lot about 'screen flicker'. But it seems people are using this to describe a few different faults.
I've noticed that my one x backlight flickers when in auto brightness mode. But it only does it under artificial light. Under natural light it's totally fine.
If I turn off Auto brightness, it is completely fine also, regardless of what level I set the brightness to.
It's almost as if the software isn't filtering the auto brightness sensor output enough and trying to respond instantaneously to even the slightest light change, giving the impression of a flicker.
Who else has this issue specifically?
It looks to me like a software issue, but I only have 3 days left in my return for refund peiod and I'm not sure what the best option is.
Cheers.
EDIT: On to my 10th handset now with the same issue and just about ready to give up, but have noticed that the flicker seems to be worse when the CPU is coming on and off heavy load.
Can someone with Root and SETCPU installed please try different governers to see if they make any difference to this issue? I don't wan to root this phone to try it myself as I may end up returning it. Thanks!
Sentinel196 said:
Hi all.
I'm reading a lot about 'screen flicker'. But it seems people are using this to describe a few different faults.
I've noticed that my one x backlight flickers when in auto brightness mode. But it only does it under artificial light. Under natural light it's totally fine.
If I turn off Auto brightness, it is completely fine also, regardless of what level I set the brightness to.
It's almost as if the software isn't filtering the auto brightness sensor output enough and trying to respond instantaneously to even the slightest light change, giving the impression of a flicker.
Who else has this issue specifically?
It looks to me like a software issue, but I only have 3 days left in my return for refund peiod and I'm not sure what the best option is.
Cheers.
Click to expand...
Click to collapse
Oh well return it, and buy a new one thats probably the best option, i ordered mine yesterday, and ill do the same in 2 weeks if it have issues
Yeah I'm thinking that might be the best option. It's just that it seems to be a Software issue to me.
Anyone upgraded to 1.28 and seen this specific problem (not the screen jumping and flickering pixels) go away?
Sentinel196 said:
Yeah I'm thinking that might be the best option. It's just that it seems to be a Software issue to me.
Anyone upgraded to 1.28 and seen this specific problem (not the screen jumping and flickering pixels) go away?
Click to expand...
Click to collapse
I've upgraded to 1.28 and still have the flickering problem. I would love to be able to believe its software and its going to get fixed with an OTA, but at the moment everyone is simply uncertain as to what the future holds.
HTC advices anyone with a flickering screen to go to your carrier and ask for a replacement
Sent from my Desire HD using xda premium
On to my 10th handset with auto-brightness flicker now. At what point should i jsut give up? lol
It seems to be somehow related to CPU load also as I'm noticing the flicker is far worse when the cpu is changing power states.
Can someone with root try a different governer for the CPU and see if that changes the flicker at all?
BUMP. I'd be really great if someone rooted could test this theory!
..
I really cant help but ill tell my experience with my onex for the past two or three weeks.
I had the flickering screen twice,
1. random on the notification bar.
2. I was taking photos and got the CPU loaded because I was shooting too many pics. the bottom side of the screen was flickering.
anyway, I notice that the flickering only happend when the auto screen rotate is enabled.
Thanks for the reply, but I think you're talking about a different flicker. I'm talking about the back-light flicker when Auto Brightness is enabled. Not the LCD panel flicker.
Hey guys,
I bought a HOX with a broken touchscreen. I changed the whole display unit and that is fine now, but I had flickering backlight before and after changing the display unit.
I noticed this was a common error earlier, but I don't know if it still is? Is there any fix to it? I read that it was fixed back in october or so and my version is:
4.1.1
software number 3.14.207.27
sdk api 4.63
kernel 3.1.10-g946d78d
[email protected] #1
Can I fix it by flashing another kernel /ROM?
This is what I see:
I can't change display brightness. It doesn't matter whether I do "automatic", lowest or highest, nothing changes.
When It is charging: No or only light flickering
When it is not charging: If I do nothing at all, there is no flickering. as soon as I touch the screen or it has to process something, I have a light increase/decrease in brightness.
The backlight is NOT dead. It is only pretty low. I can still see if the room is dark and even when there is light shining in the room.
I am just bothered by not being able to adjust brightness and the flickering when not charging..
I have done a factory reset via bootmanager but it still is the same.
But I REALY like this phone so I'd realy love to keep it.
Any help?
I have no problems with flashing as I have flashed previous mobiles, but I would like to know whether there is a ROM/kernel that will fix this.
for example when I have the analog clock on the screen and it starts ticking forward each second, as soon as it starts moving, the screen goes darker a tiny bit.
I hace the same problemas. Did you fixed this issue?
Dont bother yourself with it, its not a problem, its very common, all one x's i handled had the same "issue", my current one also has it, just ignore it or put brightness around 50%, much less noticable
It has to do with tegra 3.
Sent from my HTC One X
:thumbdown::thumbup:
Sent from my HTC Explorer using xda app-developers app
I have investigated this further and came to a conclusion that this is something called smartdimmer, connected to tegra 3. I now just want to find out how to disable it ^^
Sent from my HTC One X
Hello, my device was working great for a month, now suddenly, screen flicker, it flickers quickly every now and then.
Is this hardware related or can it be fixed by software?
It appeared after I installed a new Rom, but now it appears in different roms.
It also started appearing after I played with root dim app, setting screen brightness to lower than usual (and not only laying a filter). Not sure if that might have anything to do with it.
In it is not present when brightness is at 100 %. But anything lower it is there.
Read somewhere about someone opening the device and clean the connector apparently solving his flicker. Hoping I won't have to do that though.
Thanks in advance!
Sent from my Nexus 7 using xda app-developers app