I am encountering strange touchscreen locks. They occured first with Google Navigation amd always after approx. 20-30 minutes of permanent display usage.
It looks like I would tap on the screen (I see the maginification buttons clicked in the lower right corner), but I cannot go back, because the screen does not react anymore. I have to use the power button twice to get it back to work, sometimes even that does not help. Imagine you want to stop the Navigation software (which is still talking) but you cannot...
This happens also with Navdroid, but the software seems not to be hindered as much as Googles Navigation. In any case, the screen does not react to touch anymore.
I also found this to happen after a longer telephone call, the screen does simply not react anymore, but still shows everything.
I had this effect with Megatron, Void, Prime, Miks CM7 and Andys Gingerbread ROMs, so is this then a hardware or a software (driver) issue? I cannot remember having that with the stock ROM, but that's a long time ago
With the Gingerbread ports there seems to be a problem with the screen after calls but am not too sure if thats the reason for ur problem as u had the same with Froyo.
I am on stock rom and i dont have any such problem. And i have never heard anyone else having the same problem. You could try wiping everything and then flashing a froyo rom again. If that doesn't work, it might be a hardware problem.
In case you do need to send it in to LG, you will have to revert it back to stock condition. When you do that, check if this happens then too.
Over the past week or so I have noticed the backlight on my Atrix acting strange during calls. Sometimes it will not shut off when placed next to my head(I can see the screen out of the corner of my eye) or it will not light up when taken away from my head(to key in a selection on a menu). Sometimes it also shuts the backlight off as soon as the call is placed and I have to press the power button to "wake it up" so that I can make a selection.
The only other thing that I noticed just a little bit ago is - while in a call the LED next to the earpiece appears to be glowing red(dim - like the Terminator's eye right before it got crushed ).
I haven't added any apps in the last two weeks and there haven't been any major updates to speak of.
The phone is basically stock. I did root it so I could use titanium backup and barnacle.
Build: OLYFRU4 1.8.3
Kernel: 2.6.32.9-00007
baseband: n_01.77.15p
android version: 2.2.2
sys ver: 4.1.83.nb860.att.en.us
Has anyone else had a similar problem? More importantly, has anyone else resolved a similar problem?
Thank you in advance for any assistance provided.
Interesting.. I have similar problems, and I've heard this is a known problem with the Gingerbread update (which you haven't done it seems). I've personally noticed that this happens after I use bluetooth and making calls and stuff with BT devices. Do you do anything like that?
I do use a bluetooth headset but haven't noticed any problems when using it.
Shortly after making this thread I checked for any OTA updates and there was the gingerbread update available. I went ahead and performed the update and the problem still exists.
I also believe that my terminology was different and that is why I didn't have success when searching. I have found several threads describing the problem as dealing with the proximity sensor instead of the light sensor. I have not found a definite solution though yet - I'm contemplating a factory reset.
So I went ahead and did the big wipe and still have the same issue. I've read over the other "proximity issue" threads which all involve editing the value in build.prop.
The problem with this is, mine seems to have problems both ways. I've had it blank the screen right after pressing "dial" and then I've also had it not blank the screen at all(allowing it to cheek dial). The other weird thing I mentioned in my first post, is the sensor LED( to the right of the ear slot) is glowing red when there is an active call. I don't recall seeing it do that before.
I'm really tempted to have an insurance claim really soon.
71chevellejohn said:
So I went ahead and did the big wipe and still have the same issue. I've read over the other "proximity issue" threads which all involve editing the value in build.prop.
The problem with this is, mine seems to have problems both ways. I've had it blank the screen right after pressing "dial" and then I've also had it not blank the screen at all(allowing it to cheek dial). The other weird thing I mentioned in my first post, is the sensor LED( to the right of the ear slot) is glowing red when there is an active call. I don't recall seeing it do that before.
I'm really tempted to have an insurance claim really soon.
Click to expand...
Click to collapse
Unfortunately, it sounds like your proximity sensor (or logic board in general) may be going haywire - meaning a hardware problem not a software problem (I'm guessing that since, as you said, it's happening both ways)...
In my sig there is a app called Build.prop editor. You can use this to change the proximity timing and distance. the little red light you see is the infrared sensor that tells the screen to shut off.
In the build.prop edit mot.proximity.delay=200
and edit mot.proximity.distance=30
should fix screen not turning off issue.
Once again link in my sig for build.prop app( must be rooted)
You can try other values that fit you, doesnt have to be 200 and 30
Anyone else have issues with their accelerometer being off. I was trying to play temple run and noticed I had to hold it at an angle for the player to stay in the middle of the screen. Then I loaded up bubble level and it shows it being 5 degrees off. I tried to calibrate it from the screen menu and a factory reset neither of which helped. Should I send to Samsung for repairs?
Hmm, no clue. Have you tried Googling "how to calibrate android accelerometer" or similar?
Sent using Tapatalk
Me too
Man, that's so weird. I had almost the same problem on the same day. Suddenly, my player's accelerometer freaked out. The x axis keeps showing -9 at horizontal position. I have tried calibrating it many times and also tried lots of wipes and even 2 flashes using odin and nothing seems to solve the problem.
My player was bought 2 months ago in Brazil and I have never let it fall or suffer any kind of physical shock. Now I don't know even how to send for repair cause I only have rooted roms to flash on it and support may discover custom roms through CWM recovery on boot.
I'm still pretty sure it's not hardware malfunction. Something has happened and I can't find out how to reset sensors the hard way.
Strange that happened to us on the same day (at least, with me was on 21st).
I'll keep searching for a solution. It's horrible to use the player with this issue. (Not to say, almost impossible.)
Best regards.
I have found this and it seems to work for many ppl. I'll try it later, when I get back home (I'm at work).
First, navigate to /data/system folder and then rename or delete ms3c_yamaha.cfg
Later (you need to have your phone rooted), try this at the terminal:
adb shell
su
/system/bin/sensorcalibutil_yamaha
then place your phone horizontally and still and press enter.
Finally, run the Horizontal Calibration from the Display settings and then reboot.
Really hope it helps and work.
I tried everything I could
So, I got back home and started trying many things I saw on the web.
I reflashed again, using odin, different roms (now I'm keeping Eryigit-GB-2.3.6 G70ZCKPA Galaxy Player 5.0 For USA and INT (Rls:3.5) with rotation off).
I also tried what I have posted before and it didn't work, actually I found 2 files similar to the ones posted before: One is caled sensorlib_yamaha_test.so and the other is sensorlibconfig.so (not pretty sure about the name of the second file).
What happened during my attempts was that: before, the X sensor had the problem (value -9 with the cellphone laid on a desk, at horizontal position) and now, surprisingly, the X sensor is OK and now the Y sensor has the failure.
Using the HORIZONTAL CALIBRATION in SAMSUNG 2.3.6 (or 2.3.5, whatever), the ball only stays in the middle of the screen if I keep my phone in vertical position - upside (cause of the Y axis). Even if I rotate the tab in every direction possible, the ball never goes UP, so it only keeps with negative values and never positive ones.
BUT If I shake the phone, not so hard and not so soft, I see the ball of the calibration software moving on all directions. But when I manage to do it softly (as we do with normal use), the ball never goes up.
I have downloaded many sensor programs to test the calibration and after trying about 20 programs, ONLY ONE have showed the exact values as if the accelerometer was normal, but the calibration of the program did not affect the accelerometer on the system and other programs.
So, this is it, of course I won´t give up and try as many things as I can. Here in Brazil we have a saying that is: I'm Brazilian and I never give up.
P.S. I hope someone reads this and give me ideas. hehe
Thanks in advance.
Have a nice day u all.
Great news - a solution
GREAT NEWS - I HAVE SOLVED IT
Ok, after lots of attempts here is what I did.
I have downloaded android Froyo firmware from a Korean website (its on a thread of android development from galaxy player). Then I flashed it with ODIN and when it turned on, at first it was discalibrated the same way (Y axis only showing from 0 to -9).
I turned the player OFF and then turned it ON holding vol + button to enter in stock recovery mode. In recovery mode I wiped cache and data. Then I tried to calibrate again, with my device upside down and then voila.
Of course it was sort of a luck, but I had to try everything my mind could guess.
After all, I think that maybe It wasn't necessary to flash other roms (but it would be impossible to solve it using ICS due to a lack of calibrator - without having to use terminal / for curious noobies like me).
Then, I always tried to calibrate my tab laying it in horizontal position and that is the why I never got any satisfactory results. When I tried the calibration with the tab in 'incorrect' positions, the problem was solved. I guess, the calibration program tried to compensate the wrong results cause of the vertical position and then it calibrated itself.
Hope this helps someone someday. (But I really hope you won't have this kind of problem. It's frustrating.
Any device you have, if you have accelerometer problems, you should try this idea: wipe data and cache, and the first calibration you do, do it with your device turned to the side that has the wrong value or to the oposite side. This worked for me.
Best Regards,
Very happy Zilian28.
go to settings>display>horizontal calibration lay it on a flat surface and calibrate it
Sent from my GT-I9000 using XDA
Hey guys,
I know there has been a couple of posts like this that I have found through searching but none have actually found a solution, so instead of resurrecting a old thread I thought I would start a new one.
Basically I am having some issues with my new pebble blue (yey) S3 . I have found that sometimes when the phone is sleeping when I press the power button to bring it out of sleep the lock screen begins to hang. This is followed by a number of different things, the screen either glitches for a bit and then begins to work or it stays locked and needs a battery pull. As well as this I've found that randomly either when charging or not and the phone is sleeping it simply becomes unresponsive, staying on a black screen and needing a battery pull to fix (this has only occured a few times, the hanging lock screen occurs quite often).
I have done some searching and found little in the way of a solution or what the problem is, however I have found that when the lock screen hangs -if it begins to work again after glitching out the 'WIFI connected to ****' appears at the bottom of the screen. Anyway if anyone has any ideas or also recieves this problem I would really appreciate some help as it's driving me crazy and I'm unsure if it is a common S3 bug or a faulty handset, in which case I have limited time to RMA.
Cheers in advance
Hmm, sounds like a faulty phone to me. Try taking it back to get it exchanged for onother one. S3 was built to fly not crawl.
You'll want to go through a process of elimination to figure out when might be causing it.
Something you can try and test with (one at a time)
-turn on airplane mode
-turn off live wallpaper
-shut down all running tasks
-change your lock screen security method
-limit the number of widgets running on all the screens
-reduce the number of active screens
Probably other things you can try to pull out of the equation, but thats a good start
After looking up dial-a-phones returns policy it would seem that I have 28 days to return if the handset is faulty, so this atleast gives me some breathing room to try out any suggestions for fixes. I will begin to eliminate each of the suggested items above however as the lock screen problem is intermittent it make take a day so actually see if it has had an effect, which is annoying at the least.
On another note a numberupted of people are stating high battery life on their devices however mine doesn't seem to be as good and I do have power saving on as well as nfc etc. turned off. This makes me believe my handset could have a fault, but tbf I haven't allowed for a discharge to 5% and the recharging to 100% which I heare allows for optimisation of the battery.
EDIT**** I have changed the lock screen previously and found it had no effect on the problem and I do not have a live wallpaper in use.
Phone Freezing after reboot and auto wifi signal found on.
Same here, been happening the last few days after I installed Avast. Also, turning off and on the auto on wifi seemed to replicate the problem.
The phone will boot to the lock screen and freeze a bit, and sometimes the news ticker freezes, and then after unlocked, I try to turn off wifi signal has been found on the notification dropdown and then tries to auto connect to wifi, the phone will freeze up if I dont turn it off in time.
Once the auto wifi connect is off and reboots, then the phone will keep glitching up until it catches up processing alot of processes it was trying to do for about 1/2 hr. Also, if phone freezes up for too long, like after trying too many time of unlocking the screen while freezing up, the phone gets stuck at the lock screen and the phone almost overheated, in an area right below the battery. I had to pull the battery out to cool it off.
It seems to be a glitch in the auto wifi, especially if alot of resources are being used. Once Avast was on my phone about 1.5GB RAM is being used sometimes and since has really slowed the phone down. Going uninstall alot of apps.
JCrinage said:
Hey guys,
I know there has been a couple of posts like this that I have found through searching but none have actually found a solution, so instead of resurrecting a old thread I thought I would start a new one.
Basically I am having some issues with my new pebble blue (yey) S3 . I have found that sometimes when the phone is sleeping when I press the power button to bring it out of sleep the lock screen begins to hang. This is followed by a number of different things, the screen either glitches for a bit and then begins to work or it stays locked and needs a battery pull. As well as this I've found that randomly either when charging or not and the phone is sleeping it simply becomes unresponsive, staying on a black screen and needing a battery pull to fix (this has only occured a few times, the hanging lock screen occurs quite often).
I have done some searching and found little in the way of a solution or what the problem is, however I have found that when the lock screen hangs -if it begins to work again after glitching out the 'WIFI connected to ****' appears at the bottom of the screen. Anyway if anyone has any ideas or also recieves this problem I would really appreciate some help as it's driving me crazy and I'm unsure if it is a common S3 bug or a faulty handset, in which case I have limited time to RMA.
Cheers in advance
Click to expand...
Click to collapse
Same problem.
No problem if Wifi is switched off prior to sleep.
No problem if Wifi connection is still available.
Problem to lockscreen if Wifi connection is broken (move away from connected router).
Any suggestion?
sassorock said:
Same problem.
No problem if Wifi is switched off prior to sleep.
No problem if Wifi connection is still available.
Problem to lockscreen if Wifi connection is broken (move away from connected router).
Any suggestion?
Click to expand...
Click to collapse
Exactly the same here. Driving me crazy. I did root the phone using the Samsung Galaxy S3 Toolkit. I don't know if the problem also exists on non rooted devices.
S3 black screen after unlocking
Has there anyone experience S3's screen went on black? I have pebble blue S3 - GT-I9300. Cases when unlocking, answering an incoming call or attempting to turn off an
alarm? Mine happens when after unlocking the screen then it goes black and screen becomes unresponsive. It happens intermittently and even after 3 times of
reprogramming. I am now going to have it replaced. I am having a lot of troubles -- it exits on its own when im reading or composing an SMS; files were deleted after
restarting the unit, and an app opens up even not touching the scree. This is expensive and I am paying a lot just to experience this king of inconvenience.
DavidNieuwpoort said:
Exactly the same here. Driving me crazy. I did root the phone using the Samsung Galaxy S3 Toolkit. I don't know if the problem also exists on non rooted devices.
Click to expand...
Click to collapse
I also rooted my S3 a few days ago (with the S3 toolkit), and have had lots of problems with unresponsive lockscreens (I use PIN, because of exchange connection). It takes a few seconds or maybe up to as long a minute before I'm able to punch in the PIN-numbers. Before this the screen lights up but does not respond to input.
But the WiFi-connection issue might be what is the triggering factor, because after a boot it wotks just fine for several hours, if I'm not moving out of my current WiFi zone. First I thought it was either Secure Settings or Tasker that made my device lock up in this matter, but now as they are both uninstalled, the problem still occurs.
Are you running some kind of custom rom, or just the latest stock ROM, but rooted?
Flodas said:
I also rooted my S3 a few days ago (with the S3 toolkit), and have had lots of problems with unresponsive lockscreens (I use PIN, because of exchange connection). It takes a few seconds or maybe up to as long a minute before I'm able to punch in the PIN-numbers. Before this the screen lights up but does not respond to input.
But the WiFi-connection issue might be what is the triggering factor, because after a boot it wotks just fine for several hours, if I'm not moving out of my current WiFi zone. First I thought it was either Secure Settings or Tasker that made my device lock up in this matter, but now as they are both uninstalled, the problem still occurs.
Are you running some kind of custom rom, or just the latest stock ROM, but rooted?
Click to expand...
Click to collapse
Just the latest stock ROM but rooted. I've found out that turning off the wifi power safe mode fixes the problem for me. To do this:
- In the dailer enter *#0011#
- Press the menu key
- Select wifi
- Press the on/off button.
The wifi power safe mode will however be turned on during boot. So rebooting will set it back on.
*#0011# seems does the trick. But is annoying had to do this every time after power off (change battery, change Sim, flying).... Anyway to keep the setting?
I am also on stock Rom and rooted. Interested to know any non-rooted phone got this problem?
BTW. I found a quick (at least quicker than pull the battery) way to get out of the forzen lock screen (sometimes forgot to do the 0011 trick): press the power button (screen will Dim instead of OFF), then hold the home button for few seconds, as soon as you see the "menu" and "back" button lit up, the lock is un-freeze...
A permanent solution is appreciated for such an advance phone....
sassorock said:
*#0011# seems does the trick. But is annoying had to do this every time after power off (change battery, change Sim, flying).... Anyway to keep the setting?
Click to expand...
Click to collapse
Not that I know of.
Problem solved. For me anyway. Hope works for all of you having the same trouble.
My trouble begin with recent upgrade to LH3. My S3 was rooted by S3 toolkit v2.0. CWM installed was v4 something.
I un-rooted the phone. Uninstalled S3 toolkit v2.0. Re-installed the S3 Toolkit v5.0. Rooted the phone again (CWM become v6....).
I do not know it was CWM version caused the trouble or not. But my S3 is ok now.
I got it on my non-rooted phone, any additional solutions/suggestions? or service?
I found solution for problem . And my phone is working well. I downloaded rom file android 4.1.2 and flash my phone
JB 4.1.1 caused these WiFi issues on my phone
Jodatnia said:
I found solution for problem . And my phone is working well. I downloaded rom file android 4.1.2 and flash my phone
Click to expand...
Click to collapse
Exact opposite for me...never had the problem then since loading stock JB 4.1.1 with root I get lockups or freezes whenever WiFi is turned off or I leave my router's range. As soon as I disconnect from WiFi the whole phone freezes.
The *#0010# also locks up the phone when I turn off the WiFi power saving feature.
None of this happened before JB...and I replaced my phone with week via warranty due to this and the new phone does the exact same thing as soon as I upgraded to JB with root.
Any ideas?
Black screen / random reboot solution
Hi All,
I've had the black screen / random reboot issue for a few days. The only way to restore functionality on black screen lockup was to remove the battery.
I tried changing to Chrome browser and stopping the stock browser as suggested in some threads but it kept crashing.
I searched everywhere and most threads suggest a dodgy motherboard.
For me the issue was related to either a single PDF download via the stock browser or the fact I had quite alot of saved PDF files on my phone (S3 Stock firmware I9300XXELLA)
After deleting all the files listed in Internet downloads (look for Downloads with a green arrow Icon in apps) my trusty S3 has returned to normal. No black screen lockups, no hanging, runs like a dream!
I appreciate this may not solve everyones black sceeen issues but I haven't found any other thread with this solution. Hope it works for you.
Thanks,
Giz.
giz_zard said:
Hi All,
I've had the black screen / random reboot issue for a few days. The only way to restore functionality on black screen lockup was to remove the battery.
I tried changing to Chrome browser and stopping the stock browser as suggested in some threads but it kept crashing.
I searched everywhere and most threads suggest a dodgy motherboard.
For me the issue was related to either a single PDF download via the stock browser or the fact I had quite alot of saved PDF files on my phone (S3 Stock firmware I9300XXELLA)
After deleting all the files listed in Internet downloads (look for Downloads with a green arrow Icon in apps) my trusty S3 has returned to normal. No black screen lockups, no hanging, runs like a dream!
I appreciate this may not solve everyones black sceeen issues but I haven't found any other thread with this solution. Hope it works for you.
Thanks,
Giz.
Click to expand...
Click to collapse
Thanks for the tip...
Was this happening on JB for you? You mention stock firmware (not familiar with I9300)...so I am guessing it was ICS.
For me the issues are with JB and I had no files at all in the Downloads folder after a certain point when I wiped / formatted the SDCard...so I do not think my lockups were related to PDFs. But I did (and still do) have a ton of music and a lot of movies on the External MicroSD Card....and quite a few custom notification and ringtone MP3s on the Internal SDCard. Next time I load JB I will run it a few days with none of this media loaded....
Jodatnia said:
I found solution for problem . And my phone is working well. I downloaded rom file android 4.1.2 and flash my phone
Click to expand...
Click to collapse
For me this also worked. Resolved everything. (on i9300 int)
Boomer6345 said:
Thanks for the tip...
Was this happening on JB for you? You mention stock firmware (not familiar with I9300)...so I am guessing it was ICS.
For me the issues are with JB and I had no files at all in the Downloads folder after a certain point when I wiped / formatted the SDCard...so I do not think my lockups were related to PDFs. But I did (and still do) have a ton of music and a lot of movies on the External MicroSD Card....and quite a few custom notification and ringtone MP3s on the Internal SDCard. Next time I load JB I will run it a few days with none of this media loaded....
Click to expand...
Click to collapse
This is on JB 4.1.2, Phone had been updated to 4.1.2 for about a month. The issues started after a pdf download. Once all pdf's were deleted the handset works perfectly.
Giz
Got my Zu a few weeks back. When in stock, this problem occurred randomly and extremely infrequently. Now, the phone is unlocked and rooted and currently in 757 (4.4.2). Now the frequency of the problem has increased many fold. Whats the problem? ... The device just switches off without any notification or alert!! Even when fully charged. I need to switch it back on (with the power button) when I realize it has switched off.
This switch off randomly happens at-least 3-4 times a day. I used the "catlog" app to see if any errors or failures are logged (which may cause the shutdown), but the log entries are so many and so many are generated that they just fly past for me to figure out anything. Is there any specific error that I may have to search for? Any ideas on how to approach the problem and maybe solve it? If it turns out to be a h/w issue, I can send it for service. But I need to ensure that it’s a h/w issue Any help will be greatly appreciated. Thanks!