Database Info

No sound on touch screen

Have the Thunderbolt set up for making sound when touching screen. The screen will work as it should and then without reason it will get very soft and sometimes completely stop making any sound. Checked all my settings and they are as they should be. I also have the Sensation and the screen is set up the same way and it works properly. Is there something I'm overlooking or is this another bug?? Any help would be welcomed. Running stock Thunderbolt.
Thanks,

restart phone and go from there
Sent from my ADR6400L using XDA App

vinnyjr said:
Have the Thunderbolt set up for making sound when touching screen. The screen will work as it should and then without reason it will get very soft and sometimes completely stop making any sound. Checked all my settings and they are as they should be. I also have the Sensation and the screen is set up the same way and it works properly. Is there something I'm overlooking or is this another bug?? Any help would be welcomed. Running stock Thunderbolt.
Thanks,
Click to expand...
Click to collapse
It's a bug of some kind. I've had it since the day I bought my TBolt(Launch Day). I think the reason its not heard about much is because most users don't use the screen sound option and also because a lot of users here and at AC root and flash custom roms.
I'm still running launch day software because it just works for me for the way i use my device.... this being the only bug that affects me. I rooted and flashed this rom:
http://forum.xda-developers.com/showthread.php?t=1013577
and the issue went away so if it really bothers you I would go that direction. I assume other custom roms fix it as well but I cannot comment as the above is the only rom I flashed before going back stock and un-rooting.

Thanks for your input, checked other sites and found other people with same issue. Going to root this thing anyways and I'm sure the new Rom will fix the issue. Might check out the one you downloaded, looks pretty fast.
Thanks again.

burned into the screen?

Hi, My problem is that sometime stuff get's bruned into the screen. If i reboot my device the problem is solved but what happends if i don't do a reboot?
Thanks in advance, P.S i will try to get a img so i can show you guys what i mean.

Hi.
I made a thread about it some time ago, but apparently not many of us have this problem. Anyway, I also had it, but it goes away after some time with screen off. Also I've disabled auto brightness (left 25%) and I haven't noticed it coming back for quite a while.

I have started noticing a little bit of screen burning, mainly with the clock, but that's about it.

havent faced such problem, It would be great if you post a screenshot

jullejul said:
Hi, My problem is that sometime stuff get's bruned into the screen. If i reboot my device the problem is solved but what happends if i don't do a reboot?
Thanks in advance, P.S i will try to get a img so i can show you guys what i mean.
Click to expand...
Click to collapse
I wonder if you try using the fast reboot application from the market whether that would be a faster and simpler way to resolve the problem than a full device reboot (saver battery too)
Swyped from my Desire S using XDA Premium

Okay i will try to take a SS but it really hard to see it on the camera because i failed at the gym and dropped my ds on the floor and the screen cracked
ben_pyett said:
I wonder if you try using the fast reboot application from the market whether that would be a faster and simpler way to resolve the problem than a full device reboot (saver battery too)
Click to expand...
Click to collapse
Okay will try that, i often get it when i read on the web. the zoom in and zoom out buttons get stuck

Screen Flicker Galaxy S III-Fixed?

I've search high and low but it seems like any thread related to this was closed when the forums were split up. In any case, please report any screen flicker issues here and what keyboard you might be using and whether or not you're rooted. I bought this phone new and had a screen flicker before I rooted it. I figured it might be software related so I rooted and installed another ROM. I still notice it from time to time when typing. I don't think this flicker will ever go away. I'm now on CM10 and still notice the problem. I've been using Swiftkey from the start but I'm not sure yet if that's what causing it.
Thanks to TechSavvy2, I think this problem has been fixed.
Originally Posted by TechSavvy2
Go to settings - developer options - and check the box disable hw overlays. It should drastically fix flicker or at least help till the fix is merged (who knows when)
Click to expand...
Click to collapse
Known problems when selecting this option.
-Swiftkey FC's. (link to vote to fix problem - http://support.swiftkey.net/forums/116693-2-swiftkey-bugs-/suggestions/3143605-disabled-hw-overlays-due-to-screen-flicker-galaxy-

I have experienced it too on my s3

AndroidGraphix said:
I've search high and low but it seems like any thread related to this was closed when the forums were split up. In any case, please report any screen flicker issues here and what keyboard you might be using and whether or not you're rooted. I bought this phone new and had a screen flicker before I rooted it. I figured it might be software related so I rooted and installed another ROM. I still notice it from time to time when typing. I don't think this flicker will ever go away. I'm now on CM10 and still notice the problem. I've been using Swiftkey from the start but I'm not sure yet if that's what causing it.
Click to expand...
Click to collapse
Aren't you on CM10??? Go to settings - developer options - and check the box disable hw overlays. It should drastically fix flicker or at least help till the fix is merged (who knows when)
Sent from my Galaxy S3 using Tapatalk 2

TechSavvy2 said:
Aren't you on CM10??? Go to settings - developer options - and check the box disable hw overlays. It should drastically fix flicker or at least help till the fix is merged (who knows when)
Sent from my Galaxy S3 using Tapatalk 2
Click to expand...
Click to collapse
I'm pretty sure this has fixed the screen flicker problem for the galaxy s3. Thanks a million. What exactly does this option do
Sent from my SCH-I535 using xda premium

AndroidGraphix said:
I'm pretty sure this has fixed the screen flicker problem for the galaxy s3. Thanks a million. What exactly does this option do
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
Not sure what it does, but you will need to tick the same option every time you reboot if you're on CM10 official at least(I can't speak for the other AOSP ROMs.)
You got a screen flicker BEFORE you did anything to your phone tho? That's the first I've heard of the flicker anywhere except an AOSP ROM. Hmmm. And was/is it only when you used Swiftkey? If so, gotta be some conflict between Swiftkey and our phones. (I really don't care for swiftkey since it doesn't have any kind of swipe option. I use Touchpal, which is pretty good on the autocorrect/predictions especially for a freebie)

I've also had the screen flicker on my phone since I activated it. I am on stock touchwiz and the thing that kepts it from occuring every time i opened the keyboard was installing thumb keyboard. I really wish Samsung would send a fix sometime in the near future. I am hoping this is just a software issue and not hardware.

shangrila500 said:
I've also had the screen flicker on my phone since I activated it. I am on stock touchwiz and the thing that kepts it from occuring every time i opened the keyboard was installing thumb keyboard. I really wish Samsung would send a fix sometime in the near future. I am hoping this is just a software issue and not hardware.
Click to expand...
Click to collapse
Ya, I know for a fact, I had the flicker before I rooted or even changed the bootloader. I've tried every rom out there and still have a real bad flicker every now and then. It does go away when I turn hw overlays off but by turning it off I can't use SwiftKey which really bites. Isn't this an indication its software related?
And I'm not sure if it's just SwiftKey related. I guess, I'll experiment with the other keyboard to test.
By any chance could it be kernel related?
Sent from my SCH-I535 using xda premium

It happened to my GF's S3, lets call this S3 A, screen fickers and with series of lines vertically, phone freezes, had to do hard boot, then the battery dropped to 3% instantly. We think it's the battery, lucky us, we have another S3, we'll call this S3 B, in which has no flickering issue, and we exchange the battery and the flickering did not happen on S3 A anymore but it did happen to S3 B in which has no flickering issues at all from the start.
And we noticed the S3 A battery is beginning to bloat (it is getting fatter than the battery of S3 B) maybe due to wear and tear or over charging.
So our conclusion, the battery is culprit, we've replaced it and we'll observe for about a week.

I can also experience flickering and very crappy battery life. Guess I need to buy a new batter then? I don't want to waste money if changing batter doesn't work so please tell me if I should buy or not.

[Q] CM10 Phone's Screen Stays Black When Unlocked

So what happens every so often when I hit the unlock button is that my phone screen won't come on. Everything else works fine but the screen isn't on so obviously I can't see what's happening. Is this happening to anyone else or is this a possible hardware malfunction? It's been happening with several CM10 based roms over the last month and a half. It's gotten progressively more frequent.

Sounds like you're getting what they refer to as SOD. Its buggy software in CM10 that will hopefully be sorted out soon.

I agree, likely SOD. If your kernel allows control of CPU voltages, I would bump them up for the lower clock speeds. Seemed to help for me.
Sent from my SCH-I535 using xda app-developers app

Which "unlock button" are you hitting. It's a common issue with the CM10 ROMs that if you hit the home button when the phone is locked and the screen is off that it doesn't bring the phone to life as it should. I have it happen all the time and just have to hit the home button several times or hit the power button to unlock it. I haven't tried seeing if the phone worked with the screen off like you mentioned I've always just tapped the home button till it lit up finally.

Slacker101 said:
So what happens every so often when I hit the unlock button is that my phone screen won't come on. Everything else works fine but the screen isn't on so obviously I can't see what's happening. Is this happening to anyone else or is this a possible hardware malfunction? It's been happening with several CM10 based roms over the last month and a half. It's gotten progressively more frequent.
Click to expand...
Click to collapse
This drives me crazy and it has me considering using another ROM. Is it fair to call this "stable" release so if this keeps happening? Just food for thought.

brando7010 said:
I agree, likely SOD. If your kernel allows control of CPU voltages, I would bump them up for the lower clock speeds. Seemed to help for me.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Realize this post is over a year old but it helped me fix my issue. I used Benchmark and Tuning (available for free on play store) which allows you to choose a few types of governors one of which was on demand. hasn't black screened since. Thank you guys.

Proximity Sensor Troubles? I think I have your fix... [AOSP or Sense]

I've seen several posts in different ROM threads talking about proximity sensor issues, and I think I have your fix.
Awhile ago, back when I was on CM10, I noticed that my proximity sensor was no longer functioning as expected. The screen would remain on when I was on phone calls, and would stay black for long periods of time after hanging up.
I initially chalked it up to a CM10 issue, but when I flashed back to a Sense ROM, the issue remained. Eventually, I discovered this app...
https://play.google.com/store/apps/details?id=com.incredicontrol.ProxSensorCalibrator&hl=en
...and it worked perfectly.
The best thing to do is start up the app and see if it says "NEAR" or "FAR" at the bottom, then move your hand close and further from your phone to see when it changes. To be completely honest, I don't entirely understand what the settings in the app correspond to - I just played with the settings until the "NEAR" and "FAR" labels appeared at what I believed was the correct time. The attached screenshot shows the settings that ended up working for me.
Sure enough, I have no proximity issues now - except when I recently flashed LiquidSmooth, and forgot to re-run this app. As soon as I re-calibrated, it worked great again. So, this fix isn't permanent - you have to keep this app installed, and it has to be set to run on boot. You also have to have root for it to work its magic.
Hope this helps some of you out there!

Thanks for the info. I'm definitely going to give this a shot. I've had issues like you had on all 4.2 ROMs with s2w. My issue does go away when I go to something different though. Still gonna give it a whirl though and see if it helps.
Oh well, it doesn't look like my calibration is off. Thanks for the suggestion though.
Sent from my One X using Tapatalk 2

pside15 said:
Thanks for the info. I'm definitely going to give this a shot. I've had issues like you had on all 4.2 ROMs with s2w. My issue does go away when I go to something different though. Still gonna give it a whirl though and see if it helps.
Sent from my One X using Tapatalk 2
Click to expand...
Click to collapse
Yeah, I think the s2w bug may be something different entirely, but it can't hurt to check.

Silellak said:
I've seen several posts in different ROM threads talking about proximity sensor issues, and I think I have your fix.
Awhile ago, back when I was on CM10, I noticed that my proximity sensor was no longer functioning as expected. The screen would remain on when I was on phone calls, and would stay black for long periods of time after hanging up.
I initially chalked it up to a CM10 issue, but when I flashed back to a Sense ROM, the issue remained. Eventually, I discovered this app...
https://play.google.com/store/apps/details?id=com.incredicontrol.ProxSensorCalibrator&hl=en
...and it worked perfectly.
The best thing to do is start up the app and see if it says "NEAR" or "FAR" at the bottom, then move your hand close and further from your phone to see when it changes. To be completely honest, I don't entirely understand what the settings in the app correspond to - I just played with the settings until the "NEAR" and "FAR" labels appeared at what I believed was the correct time. The attached screenshot shows the settings that ended up working for me.
Sure enough, I have no proximity issues now - except when I recently flashed LiquidSmooth, and forgot to re-run this app. As soon as I re-calibrated, it worked great again. So, this fix isn't permanent - you have to keep this app installed, and it has to be set to run on boot. You also have to have root for it to work its magic.
Hope this helps some of you out there!
Click to expand...
Click to collapse
Thank you. I hated hitting the wrong button with automatic machines. Will try this out. I am also on liquid smooth so I may try the same settings. Thanks!
Sent from my One X using xda app-developers app

solving with
Proximity Sensor Fix

Worked for me! Thank you

Hitting the thanks button is probably enough, rather than digging up an old thread by commenting on it.
Sent from my Evita

My Device: HTC One X
There are problems with the proximity sensor.
The application worked fine. Thank you very much.