Mine is TL and flashed the UK generic JB firmware via Flashtool. The JB upgrade is great, however recently, because the strong sunlight on Texas, I noticed that the light sensor was no longer working. I've tried to erase the data, reset, and reflash. None of those made the light sensor working. Is everyone got their light sensor working on the JB so that's only TL's problem or it's actually not working on the JB?
greatremix said:
Mine is TL and flashed the UK generic JB firmware via Flashtool. The JB upgrade is great, however recently, because the strong sunlight on Texas, I noticed that the light sensor was no longer working. I've tried to erase the data, reset, and reflash. None of those made the light sensor working. Is everyone got their light sensor working on the JB so that's only TL's problem or it's actually not working on the JB?
Click to expand...
Click to collapse
Haven't tried the stock JB rom, but with AOKP-Kangxperia, which is JB based, the light sensor is working fine.
on my Xperia T light sensor doesnt work too ...
Supersonic335 said:
on my Xperia T light sensor doesnt work too ...
Click to expand...
Click to collapse
your's the LT30p right? so maybe it's kind of bug of the JB?
Arcano said:
Haven't tried the stock JB rom, but with AOKP-Kangxperia, which is JB based, the light sensor is working fine.
Click to expand...
Click to collapse
it's not about the JB version...but the stock one. I think it might be some kind of bug...
in the service test, the light sensor remain 0 not matter how strong the light went.
greatremix said:
Mine is TL and flashed the UK generic JB firmware via Flashtool. The JB upgrade is great, however recently, because the strong sunlight on Texas, I noticed that the light sensor was no longer working. I've tried to erase the data, reset, and reflash. None of those made the light sensor working. Is everyone got their light sensor working on the JB so that's only TL's problem or it's actually not working on the JB?
Click to expand...
Click to collapse
Xperia T here. Light sensor works fine.
Not sure with the Xperia T but should there be a proximity sensor calibration app? If nit find one. Let me have a look.
Sent from my Samsung Galaxy Note II LTE GT-N7105 using xda premium
weeo said:
Not sure with the Xperia T but should there be a proximity sensor calibration app? If nit find one. Let me have a look.
Sent from my Samsung Galaxy Note II LTE GT-N7105 using xda premium
Click to expand...
Click to collapse
It worked on mine on stock FTF or the one that's deodexed...
Mine doesn't work after upgrade.
doministry said:
Mine doesn't work after upgrade.
Click to expand...
Click to collapse
the ALS shows a 0 when checked under the service tests, but the screen does change brightness depending on light conditions.
My Xperia T light sensor stopped working as well after JB update.
Sent from my LT30p using xda premium
I have some issues also, brightness is set to auto but when entering from sun light into the buildings where the light is low, the screen remains at full brightness and the sensor is working ok only after i'm locking the screen once.
ALS sensor works, differently from ICS, but works. It takes more time, decreasing the backlight when coming to low light conditions and sometimes it takes more time, increasing the backlight in high light conditions after waking the screen. This could be a little faster.
And I suggest disabling DLS, it's annoying and I see no benefit from using it.
smardu said:
I have some issues also, brightness is set to auto but when entering from sun light into the buildings where the light is low, the screen remains at full brightness and the sensor is working ok only after i'm locking the screen once.
Click to expand...
Click to collapse
This describes the behavior I had on my TL with ftf's from UK or CE. If it doesn't happen right away, it's just a matter of a short time (less than a couple days) until it begins. Once it starts, the behavior doesn't go away.
Odp: Anyone got the Light Sensor working on the JB?
greatremix said:
Mine is TL and flashed the UK generic JB firmware via Flashtool. The JB upgrade is great, however recently, because the strong sunlight on Texas, I noticed that the light sensor was no longer working. I've tried to erase the data, reset, and reflash. None of those made the light sensor working. Is everyone got their light sensor working on the JB so that's only TL's problem or it's actually not working on the JB?
Click to expand...
Click to collapse
I had exactly the same problem. Dealt with it by wiping /system, /cache, /data partitions in recovery, booting the phone (of course it stopped on Sony logo) and then flashing JB again. But I'm not sure you could do this on TL. I think you will lose LTE then.
Tapatalked from Poland using Xperia T
LesPaulGuitarPlayer said:
This describes the behavior I had on my TL with ftf's from UK or CE. If it doesn't happen right away, it's just a matter of a short time (less than a couple days) until it begins. Once it starts, the behavior doesn't go away.
Click to expand...
Click to collapse
I've used: LT30p_9.1.A.0.489_1265-1626, Xperia T_9.1.A.0.489_Europe and OTA upgrade from LT30p_7.0.A.3.223_(1267-4649), same issue with all these versions.
All versions were installed with full wipe.
Can some one see if it is only in this ROM? Try another jb rom and confirm. If so then someone can look into it with me.
Sent from my Samsung Galaxy Note II LTE GT-N7105 using xda premium
Related
hello, i recently bought Xperia T lt30p everything is good except one problem. My screen flickers very much.In service menu ambient light sensor values dont change always are 0.I repaired my phone with pcc but no success.Are your values also dont change please help
olimjon said:
hello, i recently bought Xperia T lt30p everything is good except one problem. My screen flickers very much.In service menu ambient light sensor values dont change always are 0.I repaired my phone with pcc but no success.Are your values also dont change please help
Click to expand...
Click to collapse
your problem will be solved after update to JB 4.1.2 either .489 0or .492(italy) ...:good:
zeff84 said:
your problem will be solved after update to JB 4.1.2 either .489 0or .492(italy) ...:good:
Click to expand...
Click to collapse
I am already in official 4.1.2 when i set the brightness to automatic my screen wont change always are dim that i cannot see anything.
Hi,
I have a H1 and today morning i thought of taking some pictures in my garden. Everything went on fine and then all of a sudden my phone's camera was unable to focus on anything. it just stays blurry. and when in touch to focus it just keeps changing the metering. if i turn the app off for 5 min and turn the camera on again it focuses for a few seconds and then again loses focus.
Could this be a hardware issue or software issue? im running ARHD 7.3 with a stock kernel.
regards
Archit
architkumar said:
Hi,
I have a H1 and today morning i thought of taking some pictures in my garden. Everything went on fine and then all of a sudden my phone's camera was unable to focus on anything. it just stays blurry. and when in touch to focus it just keeps changing the metering. if i turn the app off for 5 min and turn the camera on again it focuses for a few seconds and then again loses focus.
Could this be a hardware issue or software issue? im running ARHD 7.3 with a stock kernel.
regards
Archit
Click to expand...
Click to collapse
hi
greetings,
IMO its a software issue
boot into recovery and wipe cache and dalvick cache and reboot againg
shrex said:
hi
greetings,
IMO its a software issue
boot into recovery and wipe cache and dalvick cache and reboot againg
Click to expand...
Click to collapse
I had tried that among other things like changing kernel and upgrading from arhd 7.2 to 7.3..
.
But I noticed something, my battery was low so I was running at 1ghz and now it's at 50% and the problem has gone... Could be a mix of diff software issues.. Fixed for now though... Whew!!!
architkumar said:
Hi,
I have a H1 and today morning i thought of taking some pictures in my garden. Everything went on fine and then all of a sudden my phone's camera was unable to focus on anything. it just stays blurry. and when in touch to focus it just keeps changing the metering. if i turn the app off for 5 min and turn the camera on again it focuses for a few seconds and then again loses focus.
Could this be a hardware issue or software issue? im running ARHD 7.3 with a stock kernel.
regards
Archit
Click to expand...
Click to collapse
I am having exactly this issue..
After a few seconds camera can no longer focus -
Stock T-Mobile UK
Could be due to low power or might also be because of dirt/dust/spec in your camera lens
Riyal said:
Could be due to low power or might also be because of dirt/dust/spec in your camera lens
Click to expand...
Click to collapse
tony_man said:
I am having exactly this issue..
After a few seconds camera can no longer focus -
Stock T-Mobile UK
Click to expand...
Click to collapse
i fixed the issue buy just putting my phone on charge! it was definitely cause of the low battery. ive programmed setcpu to underclock it to 1ghz when it reached under 25% battery, so that was causing the issue..since then ive not seen the issue crop up again. i highly doubt dust can get in so there shouldnt be any need to panic about it.:good:
architkumar said:
i fixed the issue buy just putting my phone on charge! it was definitely cause of the low battery. ive programmed setcpu to underclock it to 1ghz when it reached under 25% battery, so that was causing the issue..since then ive not seen the issue crop up again. i highly doubt dust can get in so there shouldnt be any need to panic about it.:good:
Click to expand...
Click to collapse
Happens on full charge..
Just charged - got full light -- lens clean
after a few seconds - focus is gone.
are you on a custom rom?
architkumar said:
are you on a custom rom?
Click to expand...
Click to collapse
nope - I'm completely stock t-mobile
Camera is fine when its first used.
tony_man said:
nope - I'm completely stock t-mobile
Camera is fine when its first used.
Click to expand...
Click to collapse
hmmmmm....wow i thought it was a custom rom issue..maybe rooting the phone and the installing a cpu governer like daemon or setcpu might help..you try setting minimum frequency to 1.2 and see if that helps..
coz i got myself an O2 version from uk and installed a custom rom on it.. and well one morning it started acting whacky..but putting it on charge helped..it could be possible..i sifted through the other posts and i believe we are the only 2 people who have faced this problem..but had it been a hardware issue it would not have been fixed so easily so im pretty sure its a software bug..
Could be a problem with the camera sensor over heating
Wow is that even possible? I did not know that.. The problem Did come up after I tried some panoramic shots and a few regular pics out in the sun..
Sent from my HTC One using xda app-developers app
T-mobile have offered to replace my phone
And HTC UK have offered to take it for repair..
Not sure which option gives me the quickest turn around.
It's annoying as it works fine from time to time.
That's sad.. Coz I know how it feels to not have your phone with you.. I was lucky then I guess that it got fixed for me automatically.. But dad's theory could be correct about the sensor heating up.. Keeping in mind that it's more sensitive to light in the first place
Sent from my HTC One using xda app-developers app
and the problem is back again i was out with my friends last night and we were testing low light capabilities and the moment i switched to hdr video the camera gave up again... now its not even able to focus after being put on charge.. i tappe the phone a couple of times and it focussed but again failed..you think its a hardware issue
? or a power management issue by the kernel??(tried stock and bulletproof kernels)
Definitely sounds like the sensor overheating. On a lot of dSLR cameras with video and live view, they switch off after a short time to avoid the sensor failing
Dal1970 said:
Definitely sounds like the sensor overheating. On a lot of dSLR cameras with video and live view, they switch off after a short time to avoid the sensor failing
Click to expand...
Click to collapse
But I left the phone along overnight and it still had trouble holding focus for too long.. 5 or 6 seconds max... Could there be a possible software issue too coz apart from me only one other person is facing the same issue..
Sent from my HTC One using xda-developers app
That is why it sounds like hardware fault. If it was software, then more people wold be getting the problem.
Once it has cooled down for about 5-10 mins then it will work again, briefly.
Send back for a replacement, is my recommendation
i cant...i had it imported so its almost impossible to get it replaced..ill have to figure something else out...
Anyone else facing the same issue? it keeps cropping up again and again..
Since a while, I've issues with my ambient light sensor : autobrightness sometimes worked, sometimes not.
Now, it doesn't work at all anymore.
I've tested the ambient light sensor via service test, the value remains stucked to 0...
Do you think my light sensor is broken ???
nreuge said:
Since a while, I've issues with my ambient light sensor : autobrightness sometimes worked, sometimes not.
Now, it doesn't work at all anymore.
I've tested the ambient light sensor via service test, the value remains stucked to 0...
Do you think my light sensor is broken ???
Click to expand...
Click to collapse
It looks like it's broken. Do you have warrenty? send it for service, don't forget to relock bootloader before you do.
service test always show 0... try AndroSensor from play store and u will see under light that value is changing under bright light
Supersonic335 said:
service test always show 0... try AndroSensor from play store and u will see under light that value is changing under bright light
Click to expand...
Click to collapse
Thanks. It stays stuck at 0.000 lux with Androsensor. It must be broken...
Supersonic335 said:
service test always show 0... try AndroSensor from play store and u will see under light that value is changing under bright light
Click to expand...
Click to collapse
Hum... after reboot, it works again, and I can see the value changing in AndroSensor. But it will fail again, I'm pretty sure... I should try a factory reset to see if it fix the issue.
If you have Xperia T then it's a known issue as in JellyBean the ALS is broken and always shows 0. It fixes itself after the reboot (still showing 0) but it breaks again after a while.
Tapped from The Bond Phone!
romcio47 said:
If you have Xperia T then it's a known issue as in JellyBean the ALS is broken and always shows 0. It fixes itself after the reboot (still showing 0) but it breaks again after a while.
Tapped from The Bond Phone!
Click to expand...
Click to collapse
Yes, I've just seen your thread... But I've been using JB for 6 months and this problem only occurs since 1 month. No hope to definetely fix this, even doing a factory reset ?
You are a lucky one, I wish my sensor was working for such a long time...
In my case I tried everything - different ROM and kernel combinations but the ALS was always dead after a couple of minutes. The only solution was to get back to ICS...
Tapped from The Bond Phone!
Hi,
I installed few app for brightness controll (lux, velano) but both reported that phone don't have brightness sensor and offered to use camera sensor instead so I am not sure is it true or not?
zic1 said:
Hi,
I installed few app for brightness controll (lux, velano) but both reported that phone don't have brightness sensor and offered to use camera sensor instead so I am not sure is it true or not?
Click to expand...
Click to collapse
Maybe the problem is that you are using a custom rom which was mainly developed for p990. And your device is not p990.
I have been searching for a quite long time what can cause these problems with brightness but with no result.
Also I found out that you are the only one who has got problems with brightness.
Solution for you should be a factory reset or you can install another custom rom.
Hi,
I am curently using ROM from my signature... I will try stock and check if sensor will be recognized by app (if is exisiting in this device)...
lubosmj said:
Maybe the problem is that you are using a custom rom which was mainly developed for p990. And your device is not p990.
I have been searching for a quite long time what can cause these problems with brightness but with no result.
Also I found out that you are the only one who has got problems with brightness.
Solution for you should be a factory reset or you can install another custom rom.
Click to expand...
Click to collapse
......................
Hi,
I have a Problem with my mi8.
The Display flash
https://youtu.be/cLJ4-46QTsI
I think its a Hardware Problem
What you think ?
toniq1 said:
Hi,
I have a Problem with my mi8.
The Display flash
I think its a Hardware Problem
What you think ?
Click to expand...
Click to collapse
Turn off aod
Aod ?
toniq1 said:
Aod ?
Click to expand...
Click to collapse
Always on display. Sametimes it's help but it's probably fault of ambient light sensor or screen.
It is the same If aod Off
Not good
That's a common thing with faulty oled screens, it is a hardware issue
I have the same flashing screen when I turn the screen off before the aod is displayed. It does not happen all the time. Turning off aod does not help. I doubt that it is a hardware issue as the flashing started after updating to MIUI 11 - at least for me.
I have also this problem, started a while ago when I was on MIUI 10 after I installed some kind of dark theme
This indeed looks like a AOD fault cause turning it off solves the problem, and the latest version of AOD with custom picture customization, reduced this issue for me
But it also seems like it mostly happens when the ambient light is low so the automatic brightness reduces the screen light and AOD starts to flash
I hope it won't be a hardware problem
One other thing that I want to mention is sometimes it goes really bad and the screen starts flashing for a long time, in this case phone seems to become unresponsive as not touch and not the fingerprint sensor and infrared camera doesn't work at all
navzahed said:
I have also this problem, started a while ago when I was on MIUI 10 after I installed some kind of dark theme
This indeed looks like a AOD fault cause turning it off solves the problem, and the latest version of AOD with custom picture customization, reduced this issue for me
But it also seems like it mostly happens when the ambient light is low so the automatic brightness reduces the screen light and AOD starts to flash
I hope it won't be a hardware problem
One other thing that I want to mention is sometimes it goes really bad and the screen starts flashing for a long time, in this case phone seems to become unresponsive as not touch and not the fingerprint sensor and infrared camera doesn't work at all
Click to expand...
Click to collapse
ago是什么意思
beibei2 said:
ago是什么意思
Click to expand...
Click to collapse
It is used for past time if you're asking
So a little update on the flashing screen situation
I disabled auto brightness and set the brightness a little below middle of brightness bar and so far so good. No flashing here for a while
Also disabling the AOD completely solves the problem
Another update on the state of this flashing issue, after Android 10 update haven't seen any flashing so far, AOD display works fine, light sensor and automatic brightness work just fine.
I guess it was a software issue after all
I hope you have solved it. Do you have the anti-flick on?
Nikos kouk said:
I hope you have solved it. Do you have the anti-flick on?
Click to expand...
Click to collapse
Nope I don't
Anyone else who has this issue:
Try disabling hardware overlays in developer options, also check to see if the Game driver option within Developer options is set to default. Although its possible that this could be the beginnings of a hardware issue, it could also be a software related issue.
If none of the things that I mentioned work, i would try reflashing the stock fastboot rom. ( must be fastboot version)
Similar happened to me but i think this is not recoverable.
https :// youtu(dot)be / u1dnIb9SoAw
No matter what i do, it only flashes and nothing else is visible. Device purchased about 1.5 years ago.
koudy66 said:
Similar happened to me but i think this is not recoverable.
https :// youtu(dot)be / u1dnIb9SoAw
No matter what i do, it only flashes and nothing else is visible. Device purchased about 1.5 years ago.
Click to expand...
Click to collapse
You need to return to stock using a fastboot rom, using a recovery rom will not work.
Most likely you have corrupted files. but sure it could be an hardware issue, especially if you have dropped the phone or installed something to increase the refresh rate. If you flashed a refresh rate mod, then you need to flash the DBTO image from the fastboot stock rom.
tsongming said:
You need to return to stock using a fastboot rom, using a recovery rom will not work.
Most likely you have corrupted files. but sure it could be an hardware issue, especially if you have dropped the phone or installed something to increase the refresh rate. If you flashed a refresh rate mod, then you need to flash the DBTO image from the fastboot stock rom.
Click to expand...
Click to collapse
I have TWRP installed and thought of checking it out but it simply flashes there as well. Right now i have the display on, set never sleep in Developer options and simply keeping it up until new phone arrives. Once i am on new phone, i will try factory reset on this first and go from there i think. Not sure how to get to fastboot when display is not working.
Due to such weird nature that nothing really helps i tend to think that this is HW issue.
EDIT : Turned off display by accident (because phone call happened) and now it's back to flashing disco with absolutely nothing working. Fastboot (power + lower volume key together) is of course flashing as well so inacessible.
Happened to me too. Turned off AoD, restarted, turned on and it was ok for a while. Now flashed again. Dont know what is causing this :/
Odesláno z mého MI 8 pomocí Tapatalk
I also got the same issue on my dipper. The only solution that works perfect is by flashing to LineageOS 17.1. I know it's an OLED screen faulty but Lineage really fixes it. Been using Lineage for a few months and never have this display issue again. Other custom ROMs can't fix this display issue.