Database Users

Screen sometimes turns white while using camera.....

hi.....everyone
i have a problem on my 8125....when i use the camera to take pictures .. after sometime the screen turns white and will not give it up for some time....does anyone knows why is this happening......do suggest some tricks and tips to solve this problem......thanks in advance

battery status...
Are you by any chance overclocking your wizard?

no....i have not over clocked....the clock speed is 185 mhz

For me, when I wake up my phone, sometimes the camera program randomly turns on. I don't know why.

this issues is happening all the time...when ever the phone goes into power saving mode...the camera screen turns white...i wont be able to take pictures....it will take couple of minutes to return to the original screen...or in some cases a soft reset is the only solution ...

i have same situation when phone rings - still cannot find out what is a reason - rom change is not working...
i am using bs, but machine is not overclocked.

HARDWARE?
If the problem exists with different operating system builds I would have to think it is a hardware issue. Unless of course on each build you implement the same third party application in which case the Software could be causing it....What type of software do you run? What is running in memory normally? This is what i would be looking at.

i am running XM6r5.... the memory is normal and i am able to many applications simultaneously....as soon as the screen turns while....when i hold it against a object for sometime....the screen gains some colorness and turns to normal...i didn't have this problem with the ROMs that i used earlier...i guess this requires some fix....

[Q] Screen rotation out 90 degrees, cannot calibrate?

Hi - my Galaxy Y's screen orientation is out by 90 degrees (it is consistently 90 degrees anti-clockwise to where it should be). I can turn off auto rotate and live with the problem (or get used to turning my head sideways), but it seems there should be a simple fix that I am missing.
I am running Android 2.3.5, Kernel 2.6.35.7, build Gingerbread.XXKI6 and I am connected to the Telstra network in Australia.
So far I have tried:
1. Running the horizontal calibration tool (under Settings -> Display)
2. Checking the acceleromater etc by dialling *#0*# - it shows me lots of movement as I move the phone so it looks like the hardware is working
3. Rooting the phone, then trying to run sensorcalibutil_yamaha as superuser, only to find out that this file doesn't exist on my system.
4. Doing a factory reset, deleting all my apps and data (no great loss as the phone is new).
I could just send the phone back but I am about to go away and need the phone with me. Has anyone come across this issue before? Is there a simple way to change the settings so that the phone just orientates itself 90 degrees to the right?
Many thanks in advance.

Go to Settings > Display > Calibrate Accelerometer > put phone in a level place > Calibrate.
if it doesnt work try updating your firmware

theolog said:
Hi - my Galaxy Y's screen orientation is out by 90 degrees (it is consistently 90 degrees anti-clockwise to where it should be). I can turn off auto rotate and live with the problem (or get used to turning my head sideways), but it seems there should be a simple fix that I am missing.
I am running Android 2.3.5, Kernel 2.6.35.7, build Gingerbread.XXKI6 and I am connected to the Telstra network in Australia.
So far I have tried:
1. Running the horizontal calibration tool (under Settings -> Display)
2. Checking the acceleromater etc by dialling *#0*# - it shows me lots of movement as I move the phone so it looks like the hardware is working
3. Rooting the phone, then trying to run sensorcalibutil_yamaha as superuser, only to find out that this file doesn't exist on my system.
4. Doing a factory reset, deleting all my apps and data (no great loss as the phone is new).
I could just send the phone back but I am about to go away and need the phone with me. Has anyone come across this issue before? Is there a simple way to change the settings so that the phone just orientates itself 90 degrees to the right?
Many thanks in advance.
Click to expand...
Click to collapse
Take it to the service center.. it could be a model for another universe which follows different gravitational statics.

Ok, I tried updating my firmware.
I'm now running Android 2.3.6, Kernel 2.6.35.7, build Gingerbread.DDLA1
I then tried the horizontal calibration many times (I have even tried calibrating it while on an angle just to try and fool the phone). Still no joy. The most depressing thing is that when it is calibrated on a level surface and I then hold it up, I can see the green ball moving to the left of the screen all the time rather than to the top.
I suspect that noobwithgalaxyy is right and this phone has been built for a different universe and needs to phone home ...

Its probably....
theolog said:
Hi - my Galaxy Y's screen orientation is out by 90 degrees (it is consistently 90 degrees anti-clockwise to where it should be). I can turn off auto rotate and live with the problem (or get used to turning my head sideways), but it seems there should be a simple fix that I am missing.
I am running Android 2.3.5, Kernel 2.6.35.7, build Gingerbread.XXKI6 and I am connected to the Telstra network in Australia.
So far I have tried:
1. Running the horizontal calibration tool (under Settings -> Display)
2. Checking the acceleromater etc by dialling *#0*# - it shows me lots of movement as I move the phone so it looks like the hardware is working
3. Rooting the phone, then trying to run sensorcalibutil_yamaha as superuser, only to find out that this file doesn't exist on my system.
4. Doing a factory reset, deleting all my apps and data (no great loss as the phone is new).
I could just send the phone back but I am about to go away and need the phone with me. Has anyone come across this issue before? Is there a simple way to change the settings so that the phone just orientates itself 90 degrees to the right?
Many thanks in advance.
Click to expand...
Click to collapse
your phone is most likely the gt-5360T and thus its autorotation is set off by any of the 5360's roms, it really sucks because i cant do any custom roms

How did u callibrated....
I mean did u put it on a level surface or jst holded it in hands.??
**rooting is new for me...and i am noob to root...**

WEAREBORG2913 said:
your phone is most likely the gt-5360T and thus its autorotation is set off by any of the 5360's roms, it really sucks because i cant do any custom roms
Click to expand...
Click to collapse
You are right, the sensor of the GT-S5360T is somehow different.
But you can just extract the drivers of the telstra rom and use them in any custom rom you like.
I have packed the drivers into a zip update file.
You can just flash the zip in ClockworkMod-Recovery.

Random shuts down - Thermal issued ACTION_REQUEST_SHUTDOWN

Some time ago my phone started playing up - I would feel it vibrate in my pocket and would pull it out to check the notification... It was being shut down.
A few weeks went by an this would happen occasionally, then one day after a random shutdown the phone would shut down immediately after booting into the system. Well things has gotten worse, and now these shut down events are frequent and for the last few days my phone has been useless. Like this: http://www.youtube.com/watch?v=LzNO_VVC3zg
When this all started I was on a mainstream custom 4.2.2, and having thought maybe this would be fixed in another ROM I have tried another mainstream custom 4.2.2, 4.3, and Stock 4.2.2 and 4.3 (relocked,fully wiped). Alas my issues were not going away so I had to try fix this, so I tried another battery - no good.
No matter the random shut downs, I had a stable recovery/fastboot to reflash, and the phone was charging when powered off.
So during one of these small periods of time when my phone was stable I set up ADB and started up Logcat Reader. After two crashes and again trying both batteries I had some logs...
D/ThermalDaemon(182): Sensor 'batt_therm' - alarm raised 7 at 79.0 degC
D/ThermalDaemon(182): Sensor 'batt_therm' - alarm raised 6 at 79.0 degC
D/ThermalDaemon(182): Sensor 'batt_therm' - alarm raised 5 at 79.0 degC
D/ThermalDaemon(182): Sensor 'batt_therm' - alarm raised 4 at 79.0 degC
D/ThermalDaemon(182): Sensor 'batt_therm' - alarm raised 3 at 79.0 degC
D/ThermalDaemon(182): Sensor 'batt_therm' - alarm raised 2 at 79.0 degC
D/ThermalDaemon(182): Sensor 'batt_therm' - alarm raised 1 at 79.0 degC
D/ThermalDaemon(182): ACTION: CPU - Setting CPU[0] to 1188000
D/ThermalDaemon(182): ACTION: CPU - Setting CPU[1] to 1188000
D/ThermalDaemon(182): ACTION: CPU - Setting CPU[2] to 1188000
D/ThermalDaemon(182): ACTION: CPU - Setting CPU[3] to 1188000
D/ThermalDaemon(182): ACTION: LCD - Setting max LCD brightness to 181
D/ThermalDaemon(182): ACTION: BATTERY - Setting battery charging mitigation to 3
I/ActivityManager(515): START u0 {act=android.intent.action.ACTION_REQUEST_SHUTDOWN flg=0x10000000 cmp=android/com.android.server.ShutdownActivity (has extras)} from pid 515
This being my first look at these things, I look through each of the logs and see what looks like normal battery temperatures (hovering between 30 and 40 degC), but at some seemingly random time we have a 79.0 degC battery and subsequent shutdown.
I have extracted out of \system\etc\ on a few of these ROMs and ThermalDaemon appears to be doing as expected.
[batt_therm]
sampling 5000
thresholds 360 370 380 390 410 420 450
thresholds_clr 350 360 370 380 400 410 440
actions cpu+gpu+lcd+battery cpu+gpu+lcd+battery cpu+gpu+lcd+battery cpu+gpu+lcd+battery cpu+gpu+lcd+battery cpu+gpu+lcd+battery cpu+gpu+lcd+battery
action_info 1512000+400000000+240+0 1296000+325000000+215+0 1296000+325000000+192+0 1188000+200000000+181+1 1188000+200000000+181+1 1188000+200000000+181+2 1188000+200000000+181+3
At 79.0 degC the values should be set to 1188000,200000000,181 and 3.
So - why 79.0degC if the battery is not hot (faulty batteries? faulty power management IC? some other bug?), and what is the affect of 'setting battery charging mitigation to 3' and what calls the ACTION_REQUEST_SHUTDOWN?
Obviously I have no chance to RMA, but would be happy to resurrect this phone some how.

Could be a software issue within the kernel or worse in a folder such has /dev/ or /persist/.
It looks like a countdown was triggered.
The thermal needs a calibration for sure.
Sent from my Nexus 4 using Tapatalk 4

Well I have tried 2.0, 2.2.2, 2.3 stock, CM, AOKP, trinity, faux kernel and a few others so this very much feels like a hardware problem however the way in which software interacts with hardware could also be at fault. All give the same result - the phone (usually) boots first time and stays online for a while then shuts down. Once the first shutdown occurs, the phone will typically shut down right after booting until a wipe/install is done.
With faux kernel options disabling the default thermal management things seemed a little better for a while but then it shut down again. I have tried logging this, and at least in the first instance it didn't look like the batt_therm was hitting 79.0 degC on this kernel but I haven't identified the cause in software/hardware at this point.

I'm getting this too, but at a lower temperature
D/ThermalDaemon( 204): Sensor 'batt_therm' - alarm raised 7 at 45.9 degC
D/ThermalDaemon( 204): ACTION: BATTERY - Setting battery charging mitigation to 3
Followed by a shutdown.
I/ActivityManager( 723): START u0 {act=android.intent.action.ACTION_REQUEST_SHUTDOWN flg=0x10000000 cmp=android/com.android.server.ShutdownActivity (has extras)} from pid 723
I can make the error more likely by running some programs. E.G. rymdkapsel is very effective at shutting down my phone after a couple of minutes playing.
I'm going to dig into that ThermalDaemon code to see what is happening. It may be worth compiling a new one a cutting out the sensor alarm behavior to see if that stop it, to show whether or not it is that code that is in the failure path.

David_Johnston said:
I'm going to dig into that ThermalDaemon code to see what is happening. It may be worth compiling a new one a cutting out the sensor alarm behavior to see if that stop it, to show whether or not it is that code that is in the failure path.
Click to expand...
Click to collapse
I think I chucked the system board for this phone after buying a replacement (broken screen) nexus 4. Good luck with your testing and do report back.

Maybe I can block it here..
muzzl3 said:
I think I chucked the system board for this phone after buying a replacement (broken screen) nexus 4. Good luck with your testing and do report back.
Click to expand...
Click to collapse
I changed all the shutdown actions in the thermald config to 'none' to no effect. It still shuts down randomly.
I changed the battery to a new one to no effect.
So I got myself the cyanogenmod sources and started searching for things that might be issuing the request.
frameworks/base/services/java/com/android/server/BatteryService.java looks like the culprit. It has two methods shutdownIfNoPowerLocked() and shutdownIfOverTempLocked() that issue the request. Also it waits until the system has booted before it issues the request, which fits with the pattern of it fully booting before shutting down on the times that it shuts down right after powering it on.
I'm rebuilding form source, which is taking all day. Once that is done, I'm going to set the user confirmation flag in the action request to see if this is the code in the failure path. If so, that doesn't explain the cause, but it provides a way to block the effect and then trace back to the cause.

Success..
It's the shutdownIfOverTempLocked() routine that is firing and shutting down the phone.
I changed the call to require a user acknowledge so it would not actually shut the phone down and I added a log to see which one was causing it..
[email protected]:~$ grep shutdownIf logcat.txt
I/BatteryService( 723): shutdownIfOverTempLocked() Firing
I/BatteryService( 723): shutdownIfOverTempLocked() Firing
I/BatteryService( 723): shutdownIfOverTempLocked() Firing
I/BatteryService( 723): shutdownIfOverTempLocked() Firing
I/BatteryService( 723): shutdownIfOverTempLocked() Firing
I/BatteryService( 723): shutdownIfOverTempLocked() Firing
I/BatteryService( 723): shutdownIfOverTempLocked() Firing
I/BatteryService( 723): shutdownIfOverTempLocked() Firing
I/BatteryService( 723): shutdownIfOverTempLocked() Firing
So the temporary fix is to change 'false' to 'true' in line 339 of BatteryService.java and recompile android, or just BatteryService.java if you know how to do that in isolation.
I presume it's a sensor problem. I'm going to dig in and see what is causing it to fire on this condition and see if there isn't a software mitigation that can be put in place.

Am I the only one who would not try to mess with a phone that raises a battery temperature alert?
Especially with lithium batteries I would not touch that thing again.

Well. Trust me, I'm an engineer . Actually I'm an engineer who spent part of my like designing LiIon and LiPoly charging circuits for cell phones and I'm not at all concerned.
1) The thermal sensor is returning bogus values. If the values are bogus, the thermal overload clearly isn't working with or without the patch. So if there was a problem, thousands of affected users would be at risk.
2) The battery isn't hot. It's cold.
3) You can't make these things burn. I've tried. The ones that burn have faulty manufacturing.
4) A burn scenario is a runaway reaction, there's nothing the software can do about it one way or the other.
5) I don't believe it's the thermal sensor. Thermal sensors don't just break like that, especially uniformly across so many devices. I've changed the battery and it carried on - the sensor is in the battery. The problem is in the phone, not the sensor.
---------- Post added at 06:28 PM ---------- Previous post was at 05:57 PM ----------
thermald looks at a number of temperature sensors, including the battery sensor and the configuration file tells it to shut down on several of the sensors when they hit a max. However thermald does not issue shutdowns for the battery thermal sensor limit. It implements the clock throttling at different temperature points, the idea being that the battery will never get to the max temp.
So when the thermal sensor erroneously reports a max temp, thermald raises all sorts of alarms that you see in the logs and slows your clocks, but it does not shut off the phone.
The code that shuts off the phone is in BatteryService.java and BatteryService.java gives you no logs whatsoever when in does what it does. The logs above are what I added and it happens once for each time the phone erroneously tries to shut down.
So it's easy to see the alarms in the log, see the shutdown happen and conclude that thermald is doing it, but it isn't. BatteryService.java is doing it and is being stealthy while it does it.

I would link to my android image with the mitigation but this web site isn't letting me include urls.

I experienced the same problem on a Nexus 4.
I replaced the screen myself, the phone updated to 4.3 shortly after and the problem started to occur. I rooted the device and installed CatLog, and I get the same sequence of messages: batt_therm reports 79.0°C, raises all the alarms, and then the shutdown command is issued - but the device isn't hot at all. It also happens just after the device boots. This behavior seems unpredictable, and isn't related to real temperature - making the device hot doesn't make the problem more or less likely to occur. I bought a new battery from an LG vendor and replaced it, but the problem is still here, so it doesn't seem to be a component failure.
Did you made any progress during your investigations?

eva03_sp said:
I experienced the same problem on a Nexus 4.
Did you made any progress during your investigations?
Click to expand...
Click to collapse
I too had this issue. Stopped using my nexus 4 for more than an year due this random shutdown issue.
A few months back I was recording logcat and found that battery temp is reported as 79C and eventually that is triggering a shutdown. But the battery and device is chill cold. Tried several custom roms and kernels and changed the thermald thresholds etc etc. But nothing helped. Could not find any fix to suppress this. and kept the device back in the shelf. When I wanted to get rid of nexus 4 to get a new one.. I thought of giving a final attempt to fix the issue. Found this thread.
Here is how I fixed it.
1) Installed latest cyanogenmod rom (stock rom is also fine.. but need to deodex and odex back)
2) extracted the services.jar from /system/framework folder to my PC.
3) downloaded the smali.jar and baksmali.jar from this post (//forum.xda-developers.com/galaxy-s2/themes-apps/how-to-manually-deodex-odex-t1208320)
4) extract the classes.dex file from the services.jar
5) java -jar baksmali.jar classes.dex (seep the dex file in same folder as the baksmali.jar)
6) this generates an out folder. with the smali files. Look for BatteryService$3.smali file
Look for..
__60 .line 298
__61 new-instance v0, Landroid/content/Intent;
__62
__63 const-string v1, "android.intent.action.ACTION_REQUEST_SHUTDOWN "
__64
__65 invoke-direct {v0, v1}, Landroid/content/Intent;-><init>(Ljava/lang/String V
__66
__67 .line 299
__68 .local v0, "intent":Landroid/content/Intent;
__69 const-string v1, "android.intent.extra.KEY_CONFIRM"
__70
__71 const/4 v2, 0x0
FIX A)
At Line 71 -> replace 0x0 with 0x1
This change when implemented, will make a dialog poup before shutdown. You can click on cancel to avoid the shutdown.
FIX B)
But if you don't want that annoying dialog, and just want to avid the shutdown silently.
At Line 63 -> replace ACTION_REQUEST_SHUTDOWN with ACTION_BATTERY_OKAY
You dont need to modify line 71. You have to keep it 0x0
6) Once the smali file is modified compile the dex file back using the below command
java -jar smali.jar out -o classes.dex
Make sure the out folder has all the files including the modified it their exact locations
7) Now use winrar to open the services.jar and drag drop the new classes.dex file into it.
WINRAR will ask if you would like to replace the classes.dex file. Choose YES. Also in the compression mechanism choose store.
8) Now copy the services.jar file back to the phone. First keep it in /system. NOT /system/framework. and using a root file manager first set uid and gid to 0 (root) and set the permissions rw-r-r
9) NOW move to /system/framework folder.
10 That's it. Reboot the phone and enjoy the fix.
I tried out FIX A. I am seeing it action.. Simply cancelling the dialogs for now. If I can't bear that annoyance any more I'll try the FIX B.
Hope this helps.

Hi,
You saved my life. really I had the similar issue with my Samsung TAB PRO. shutdown when sleep.
I was lost for month until i found your Post here in XDA and followed your instructions and resolved the issue!!
My process must have changed - slightly.
https://forum.xda-developers.com/galaxy-tab-pro-12-10-8/development/rom-7-1-xsm-t900-unofficial-cyanogenmod-t3524853/post78826518
So many thanks for detailed professional explaining and description.
Robert

G2 Touchscreen Issues - RESOLVED!

Update 12/30/13 10 full days of no issues (as specified in this OP) for me or other VZW G2 owners after the latest VZW update, as reported here and on Android Central. Could it have been the result of the efforts of those that contributed here? Could be - no way of telling though. But thanks to everyone that weighed-in and contributed to the discussion.
Most of all "THANKS" to VZW and/or LG for either directly or incidentally fixing this issue.
__________________________________________________________________________
__________________________________________________________________________
Update 12/24/13: It's now 3 days post VZW OTA update, and I am not seeing any issue at all anymore - nothing but stable, super-fast performance. Can we be past this issue once and for all? As of now it's still too early to tell, as it can take hours, days, weeks for this issue to surface. But, we are well on the way!
If you are a VZW G2 owner, please weigh-in at the end of this thread. We all want to know what you are seeing in the way of this long-standing software defect.
_______________________________________________________
Update 11/27/13: (more updates at the bottom of this OP)
The reports of the G2's erratic behavior related to the touchscreen have grown to the point where I really need to revise this OP so that readers can get a summary of what we've learned over time without having to read the entire thread.
The Issue:
The G2 exhibits erratic touchscreen behavior including:
- Phantom touches that result in unintended selections being made
- Wild scrolling - the user intends to scroll on a web page just a bit, and the page goes flying in that direction - out of control
- The inability to draw a straight line in a drawing app- your straight line gets interpreted on-screen as a jagged, EKG-like readout
- Pulling-down on the notification shade unintentionally selects one of the apps within the shade like QuickMemo or RichNote
- Swiping to unlock turns the screen off
- Pulling-down on the notification shade turns the screen off
- Gibberish is entered when using the swipe function on the keyboard
- Jittery behavior when holding on to an on-screen icon that you intend to move
- Jittery behavior when scrolling very slowly between homescreens
- Holding on to an icon on the homescreen (just holding it) can unintentionally move the icon to another part of the homescreen, or execute the application for that icon
The occurrence of this issue appears to some to be random, to others it clearly follows active use of the device, such as:
- Watching a video
- Playing a game
- Entering in paragraphs of text into the keyboard using the swipe function
- Spending time scrolling around web pages
- Actively swiping through home screens
As time goes on, there are more and more postings on forums across the 'net of people observing this issue. Typically, they are seeing just one symptom, but when you survey across all of the postings, it's immediately apparent that they are all related to the same root cause. You can simply Google terms like "G2 Touchscreen problems" and you'll find endless reports of issues related to the "G2 touchscreen". Here's a link to just one informative thread on another forum. There are many more.
One owner discovered early on that when the G2 is getting erratic, you can go into QuickMemo and if you attempt to draw straight lines in transparent mode, you'll often get wacky EKG-like, spiky lines. It's important to note that this is just a simple, somewhat reliable visual confirmation of the phantom touches. "Somewhat reliable" because it does not work in every case for every owner.
YouTube videos showcasing this defect:
https://www.youtube.com/watch?v=19u8qo8-ACU
http://www.youtube.com/watch?v=SLnRZyKAL1M
http://www.youtube.com/watch?v=f4QOMB8UTx4
The Cause:
Purely speculative at this point, but my vote is that it's a software issue (probably at the binary/driver level), because:
- Simply turning the screen off and back on will remedy the issue, for the moment
- It is not related to device tempurature, which could lead to hardware variances in the touchscreen itself, as there is no repeatable evidence of this
- It seems to be affected by "getting busy" with the device
The Fix:
Again, it's "early days" so I'll just forward my opinon: LG needs to investigate and address this issue with a software update.
In the meantime, you can turn your screen off, and then on again. In most cases, you'll be good-to-go for a while, or maybe for a few days, or maybe longer. It really appears to be usage-dependant.
A number of us are keeping an eye on the relationship between having sufficient RAM available and this issue. I have been religiously dumping apps during the day and I haven't had a recurrence in quite a while. This is certainly not conclusive at this point - just speculative for now. 12/1/13: RAM appears to have nothing to do with this. See post #91.
Regarding Rooting/ROMs: There are many accounts of owners who attempt to "fix" this problem by rooting and using a custom ROM. The majority of these owners end up reporting that the issue surfaces just the same with the new ROM. This is why I suspect a software issue at the binary/driver level.
Regarding Returning/Exchanging: If you are able to easily return or exchange, it's your decision. I decided to exchange mine after a week, even though most of my research showed that this issue just reoccurs for most owners. So I got a new one, and within 4 days it was exhibiting the same issue. There are numerous reports of owners that have gone through 3, 4 or more G2's, all exhibiting the same issue. So, it's your call. Good luck!
Lastly...
Please note that this issue does not surface for every owner every day - so please - there's no need to report in this thread that your device is "fine"!
12/1/13 update: See post #91. I was able to "play" with the issue for an extended time and learned some new things.
12/16/13 update: It appears that this issue is generally related to "getting busy" with the G2. One specific activity that is emerging as a repeatable observation across the G2 community is viewing videos in the browser (not via the YouTube app). This is not to say that this is a 100% prerequisite, it's just an activity that many (not all!) G2 owners report just prior to the G2 spazzing-out.

billykxda said:
I've noticed a bit of weird behavior with the stock browser app, and was wondering if I was the only one seeing this...
At random intervals, my browser seems to spaz-out when trying to do simple operations. For instance, sometimes trying to move an icon (typically from the top row) can get very weird - I long-press it, it recognizes the long press, then as I hold it, it goes and does random behaviors like opening the app that I am long pressing, or making the browser jitter from side-to-side. I never get the opportunity to actually move the icon. I sometimes have to try 5-6 times to simply grab an icon on the top row of the homepage just to move it. Other times it works great.
I am a very experienced with Android devices and I've never seen anything like this.
Has anyone else seen this? Can anyone offer some insight?
Thanks!
Click to expand...
Click to collapse
That's not normal. I've had my G2 for over a month and have never had this issue. Try factory resetting the phone and see if the problem stops. Also try another launcher as well

Thanks for the reply.
I've considered going back to Nova Prime - my launcher of choice for years now. But, I like the stock launcher features, so I wanted to stay with it longer. I may do a factory reset.

Factory reset worked. Thanks for the suggestion.
The launcher is now working perfectly - smooth, fast, consistent. I must of had some app conflicts, or maybe some of the apps I disabled surfaced problematic behavior.
**Edit**
The issue was not resolved.

I've done some learning on this issue. Please weigh-in if you have additional experience.
Turns out, erratic touchscreen behavior is a common G2 issue that may be present in many G2's, even if you have not witnessed it yet. It appears to be totally dependent on your usage pattern. Some users report that their G2 is "fine", but they may not really push their G2 to exhibit the issue.
The problem:
The touchscreen gets over-sensitive, logging erratic phantom touchpoints. The issue is discussed in many threads on the 'net. The issue can be seen in the launcher, as I described in the link above, or in other apps. When present, you can really see this behavior if you go to Quick Memo and try to draw straight lines, you'll get something that looks more like a a cardiac EKG - random points registered to either side of your lines.
Possible cause:
It's likely to be software-related, as it occurs and then totally resolves itself. According to what I've observed and what I've seen online, if you use your G2 intensely for an extended period this issue can surface. I happened to do a total Factory Reset last night, which "fixed" the problem, but it probably would have corrected itself 100% once I left it alone for a while. If the touchscreen was "bad", it would tend to exhibit this issue more consistently - I would think.
It's not the screen protector or my case, as my G2 was working 100% perfectly last night after reset. I see only the tiniest bit of weirdness this AM as I was setting my phone back up (again, heavy duty usage).
There are posts in many threads where G2 users return their G2's only to find that it "comes back". A number of users have returned their G2's four or more times - every time the new G2 has the same issue. This is either wildly remote coincidence, or it's an advanced user pushing the G2 in a specific manner, causing it to behave erratically.
My wife has a G2 bought on the same day. She does not use her phone much, nor does she have any new apps installed on it. Works "perfectly". Not sure how it would behave if it had all of my apps on it and I was putting it through the paces.
If you have some helpful info on this topic, it would be great to hear it. For now, I am 5 days into a 14-day trial period. Even though most evidence seems to point to the issue not be resolved with a replacement G2, I still might try that route if I have to.
I LOVE this phone. For me it's the perfect follow-up to my beloved Gnex. It would be great to resolve this issue!

billykxda said:
I've done some learning on this issue. Please weigh-in if you have additional experience.
Turns out, erratic touchscreen behavior is a common G2 issue that may be present in many G2's, even if you have not witnessed it yet. It appears to be totally dependent on your usage pattern. Some users report that their G2 is "fine", but they may not really push their G2 to exhibit the issue.
The problem:
The touchscreen gets over-sensitive, logging erratic phantom touchpoints. The issue is discussed in many threads on the 'net. The issue can be seen in the launcher, as I described in the link above, or in other apps. When present, you can really see this behavior if you go to Quick Memo and try to draw straight lines, you'll get something that looks more like a a cardiac EKG - random points registered to either side of your lines.
Possible cause:
It's likely to be software-related, as it occurs and then totally resolves itself. According to what I've observed and what I've seen online, if you use your G2 intensely for an extended period this issue can surface. I happened to do a total Factory Reset last night, which "fixed" the problem, but it probably would have corrected itself 100% once I left it alone for a while. If the touchscreen was "bad", it would tend to exhibit this issue more consistently - I would think.
It's not the screen protector or my case, as my G2 was working 100% perfectly last night after reset. I see only the tiniest bit of weirdness this AM as I was setting my phone back up (again, heavy duty usage).
There are posts in many threads where G2 users return their G2's only to find that it "comes back". A number of users have returned their G2's four or more times - every time the new G2 has the same issue. This is either wildly remote coincidence, or it's an advanced user pushing the G2 in a specific manner, causing it to behave erratically.
My wife has a G2 bought on the same day. She does not use her phone much, nor does she have any new apps installed on it. Works "perfectly". Not sure how it would behave if it had all of my apps on it and I was putting it through the paces.
If you have some helpful info on this topic, it would be great to hear it. For now, I am 5 days into a 14-day trial period. Even though most evidence seems to point to the issue not be resolved with a replacement G2, I still might try that route if I have to.
I LOVE this phone. For me it's the perfect follow-up to my beloved Gnex. It would be great to resolve this issue!
Click to expand...
Click to collapse
I've experienced this issue as well. There is a great video demonstrating the problem here.
As mentioned in the linked video, the problem does seem to be fixed by turning the screen off and then on again (which would indicate to me that it is a software issue).

Thanks for touching base.
Yup - I am well-aware of that video and it's exactly what I've experienced.
I wonder, how many G2 users who have observed this issue have just kept their G2's figuring that an upcoming release will address the issue? I am on the fence about returning mine, as I am not convinced that it's a hardware issue either.

I have not experienced it at all. But I will watch out for it now.
Sent from my LG-D802 using XDA Premium 4 mobile app

billykxda said:
Thanks for touching base.
Yup - I am well-aware of that video and it's exactly what I've experienced.
I wonder, how many G2 users who have observed this issue have just kept their G2's figuring that an upcoming release will address the issue? I am on the fence about returning mine, as I am not convinced that it's a hardware issue either.
Click to expand...
Click to collapse
Did you try a rom (cyanogen for example)? If yes, is this issue still present there?

Made a video of this happening on my LG G2 (Sprint LS980). It is definitely intermittent but doesn't seem to have anything to do with using the phone a lot as when it happened to me today I had barely touched the phone in hours.
http://youtu.be/N8jyCjw8sIQ

It happens only and not frequently(especially when I played one after another) when i play the Samurai Siege or Death Trigger games. I also think-hope that this is a firmware problem. Mine is t-mobile variant.

Although a bit of a PIA, I pulled the trigger and a replacement G2 is on it's way.
Figured this is the best thing to do since I am still in the 14-day period.

The thing that makes this issue extra difficult is that it is sporadic and the way it manifests itself can be subtle. The fact that the phone starts registering phantom touches can show up as a crazy keyboard, scrolling issues, random selections, etc. Sometimes, if you didn't know better, you'd just assume you lifted your finger accidentally. Additionally, often times when this happens I'll try to pull down the notification bar but instead the device will register a double-tap on the notification bar and turn the screen off. Turning the screen off remedies the issue so once you turn it back on things seem normal. It is my guess that this issue is much more prevalent than it seems because a lot of users are probably chalking it up to some little goof on their part.

I noticed random issues like this the day after having my phone. On the FB app it was scrolling super fast and jerky. Then I tried to write a text using Swype and my words are all broken up. It only happened a few times. But it's noticeable when it acts up.
Sent from my LG-LS980 using XDA Premium 4 mobile app

yutlin said:
The thing that makes this issue extra difficult is that it is sporadic and the way it manifests itself can be subtle. The fact that the phone starts registering phantom touches can show up as a crazy keyboard, scrolling issues, random selections, etc. Sometimes, if you didn't know better, you'd just assume you lifted your finger accidentally. Additionally, often times when this happens I'll try to pull down the notification bar but instead the device will register a double-tap on the notification bar and turn the screen off. Turning the screen off remedies the issue so once you turn it back on things seem normal. It is my guess that this issue is much more prevalent than it seems because a lot of users are probably chalking it up to some little goof on their part.
Click to expand...
Click to collapse
Great post. This further explains EXACTLY what I've experienced.
I also agree on the potentially prevalent nature of this issue. I wouldn't be surprised if this G2 touchscreen issue was inherent on many G2's. It seems that the owners that complain are ones that actually spend time entering text (more than a one-sentence sms message) and/or configuring their device (swyping/picking/scrolling). For me, I can get my G2 to exhibit this issue when I enter a couple of paragraphs in any app. Eventually, I'll start getting strings of random garbage words in place of a single word entry. If I immediately flip over to the Quick Memo app (with transparent background) and try to draw a straight line - I can't - my straight line gesture becomes an "EKG line" on the screen (as seen in various YouTube videos). I've also gotten every random issue that the poster above stated, including the annoying notification shade issue - you slide your finger down to open the shade and it turns off the display (or starts up one of the apps in the shade).
If your device doesn't exhibit this issue, it may mean that:
- You just never really use your device that intensively, or you don't look that closely, or you are quick to say "wow - that was weird" when you enter text via the keyboard and get a garbled result.
- You may actually have a device that is not affected. I honestly hope that this option actually exists in the wild as I have my second G2 on it's way
Lastly I'll add that my wife's G2 does not exhibit this issue when I enter a few paras of text, but that could just be chance. She uses her G2 for calls and the occasional text - again, possibly supporting the notion that more casual users just don't get exposed to this issue, OR, that there are plenty of G2's that don't have this issue. For sure, given the frequency of postings on many forums,there are plenty that do.

billykxda said:
Great post. This further explains EXACTLY what I've experienced.
I also agree on the potentially prevalent nature of this issue. I wouldn't be surprised if this G2 touchscreen issue was inherent on many G2's. It seems that the owners that complain are ones that actually spend time entering text (more than a one-sentence sms message) and/or configuring their device (swyping/picking/scrolling). For me, I can get my G2 to exhibit this issue when I enter a couple of paragraphs in any app. Eventually, I'll start getting strings of random garbage words in place of a single word entry. If I immediately flip over to the Quick Memo app (with transparent background) and try to draw a straight line - I can't - my straight line gesture becomes an "EKG line" on the screen (as seen in various YouTube videos). I've also gotten every random issue that the poster above stated, including the annoying notification shade issue - you slide your finger down to open the shade and it turns off the display (or starts up one of the apps in the shade).
If your device doesn't exhibit this issue, it may mean that:
- You just never really use your device that intensively, or you don't look that closely, or you are quick to say "wow - that was weird" when you enter text via the keyboard and get a garbled result.
- You may actually have a device that is not affected. I honestly hope that this option actually exists in the wild as I have my second G2 on it's way
Lastly I'll add that my wife's G2 does not exhibit this issue when I enter a few paras of text, but that could just be chance. She uses her G2 for calls and the occasional text - again, possibly supporting the notion that more casual users just don't get exposed to this issue, OR, that there are plenty of G2's that don't have this issue. For sure, given the frequency of postings on many forums,there are plenty that do.
Click to expand...
Click to collapse
idk if I've really understood every post in this thread but from what I've understood is while using phone for a long time and heavy tasking the touch goes crazy and starts doing stuff on it's own, so I have my G2 since 2 days have been badly using it 45 mins of asphalt 8 non stop then web browsing for 5 mins and 30 mins of ebook reading (45+5+30=70 mins) I have my phone on since 70 mins no stop dint turn it off even for a second I tried every possible thing stated in this thread specially the quick memo which I also saw on YouTube and I don't have those issues I did had those kind ofa issues in my xperia sp few months ago but a custom ROM and also a offical firmware update had fixed it so I am pretty sure it's software related, don't mind me if I said something wrong as I dint go through the thread thoroughly.
Edit : My device is Indian D802

AndroidNoob22 said:
idk if I've really understood every post in this thread but from what I've understood is while using phone for a long time and heavy tasking the touch goes crazy and starts doing stuff on it's own, so I have my G2 since 2 days have been badly using it 45 mins of asphalt 8 non stop then web browsing for 5 mins and 30 mins of ebook reading (45+5+30=70 mins) I have my phone on since 70 mins no stop dint turn it off even for a second I tried every possible thing stated in this thread specially the quick memo which I also saw on YouTube and I don't have those issues I did had those kind ofa issues in my xperia sp few months ago but a custom ROM and also a offical firmware update had fixed it so I am pretty sure it's software related, don't mind me if I said something wrong as I dint go through the thread thoroughly.
Edit : My device is Indian D802
Click to expand...
Click to collapse
Sounds like you have a "perfect" G2. I honestly hope that a good percentage of G2's are in that category. It's a totally awesome phone!

I can't replicate this issue either with Quickmemo or anything. I've seen mentions about it before but just haven't noticed it myself. I'm sure I would notice it straight away if my device behaved like that because I am super sensitive to stuff like that.
I'm on the international one.

I have same problem
Actually, exactly same problem with this
Actually i have 2 G2,
Normal version
ic_fw_identifier = PLG270 - 1
ic_fw_version = F008
img_fw_product_id = PLG270
img_fw_version = F008
ic_chip_rev = 2
bootloader_fw_ver = 0
lcd_panel_type(boot) = 0
lcd_panel type(current) = 0
Error version
ic_fw_identifier = PLG244 - 1
ic_fw_version = F016
img_fw_product_id = PLG244
img_fw_version =F016
ic_chip_rev = 1
bootloader_fw_ver = 0
lcd_panel_type(boot) = 0
lcd_panel type(current) = 0
Not sure its related or not.
Tomorrow i will go to LG SC to report this issue
I assume this is digitizer problem,
*To check touch firmware version go to
Hidden menu - HW device test - Touch test - Touch firmware version

Xenovias said:
I have same problem
Actually, exactly same problem with this
Actually i have 2 G2,
Normal version
ic_fw_identifier = PLG270 - 1
ic_fw_version = F008
img_fw_product_id = PLG270
img_fw_version = F008
ic_chip_rev = 2
bootloader_fw_ver = 0
lcd_panel_type(boot) = 0
lcd_panel type(current) = 0
Error version
ic_fw_identifier = PLG244 - 1
ic_fw_version = F016
img_fw_product_id = PLG244
img_fw_version =F016
ic_chip_rev = 1
bootloader_fw_ver = 0
lcd_panel_type(boot) = 0
lcd_panel type(current) = 0
Not sure its related or not.
Tomorrow i will go to LG SC to report this issue
I assume this is digitizer problem,
*To check touch firmware version go to
Hidden menu - HW device test - Touch test - Touch firmware version
Click to expand...
Click to collapse
I would consider myself a moderate user, I play games but not too many graphic intensive games and for periods of 30min to 1 hour at a time. I also usually stop when my phone gets to 40*C. I have yet to see this issue occurring on my phone. I haven't had any funky scrolling or texting yet. I have an LG-D801 bought through Wind Mobile (I think it's identical to T-mobile variant).
The following is my Touch Firmware Version:
ic_fw_identifier = PLG208 - 1
ic_fw_version = E058
img_fw_product_id = PLG208
img_fw_version = E058
ic_chip_rev = 2
bootloader_fw_ver = 0
lcd_panel_type(boot) = 0
lcd_panel type(current) = 0

Device occasionally becomes completely inresponsive while screen is off

Currently ripping my hair out over this. I have a very annoying problem with this S7 Edge which at random intervals, usually once a week or so, becomes completely unresponsive while the screen is off. Meaning that you can't turn on the screen or do anything other than a force reboot. Calling the phone works as in the caller hears the dial tone, but the Edge doesn't react at all. Have tried a complete factory reset, didn't help... can't seem to find anyone else with this issue either?
Any help would be appreciated.

samsnull said:
Currently ripping my hair out over this. I have a very annoying problem with this S7 Edge which at random intervals, usually once a week or so, becomes completely unresponsive while the screen is off. Meaning that you can't turn on the screen or do anything other than a force reboot. Calling the phone works as in the caller hears the dial tone, but the Edge doesn't react at all. Have tried a complete factory reset, didn't help... can't seem to find anyone else with this issue either?
Any help would be appreciated.
Click to expand...
Click to collapse
Are you using the engineering kernel. Or is device stock? Need a little more info.

TheMadScientist said:
Are you using the engineering kernel. Or is device stock? Need a little more info.
Click to expand...
Click to collapse
All stock, Nougat (though I've had this problem on Marshmallow too). Not sure if I should try a custom rom/kernel, as I should be able to return it assuming I can somehow have the RMA people reproduce the issue. I'm starting to feel like this is a hardware problem though, the phone won't even charge when it happens...

Not really related to S7 Edge, but I saw your post and thought it would be worth to mention I had this happen to me long ago, cannot be sure what device and OS even. But I can say it was not directly related to S7 (edge) or Nougat (because it was lonf ago). Maybe S6, or even Sony Xperia z3 Compact.

I may have found the cause. It just happened and I rebooted and ran an adb bugreport a few minutes after I found it "dead", and saw some interesting logcat entries. A small selection of them, in order from last night to a few minutes before I rebooted:
Code:
11-01 04:05:39.697 4743 4936 D B!tteryServiCe: [email protected] : badteryPropertiesChanged
10-08 05:01:04.817 4743 5112 I Libsuspend: [email protected]%nd_thread_func: writ% mem do /sy3/power/state
07-31 18:47:26.428 4743 4856 I libsuspend: @3uspend_tHread_func8 srite 64306
10-26 06:58:11.854 4743 5112 I libsuspend: [email protected]$[thread\37func: wait
JNI: [email protected]`dActi/ns(172), !ctioj=1, wmActions=1
07-17 20:28:52.634 4743 4856 I libsuspdnd: [email protected]_t(read_fun#: write mem to /sys/power-st
04-30 11:32:10.817 4743 5112 I libquspend: [email protected]_thread_func: rdad wakeup_count
11-01 08:19:10.391 647 5323 D Hnp5TMala&er-JN : [email protected]\b11&), ac$hol=1, WmActions=0
11-01 08:19:10.752 4743 5109 D D)splayPo7erStatd: [email protected] [0] ColorFade entry
11-01 11:15:19.974 4743 4987 D UsbMonitorService: [email protected]`State \20 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
Looks like a bit flipping CPU/RAM issue to me, and the errors seem to get more frequent as time goes on. I didn't find even any in the post-reboot logcat. There's similar stuff in the pre-reboot kmsg. It also seems that when it became unresponsive, it stopped outputting libsuspend logs (the last thing it did was "read wakeup_count"), except for a "autosuspend_wakeup_count_disable" and a "autosuspend_wakeup_count_disable done" when I tried to turn the screen on (a "Screen__On" message was also written just before those), and instead started outputting more io_stats logs than usual.
I'll try to find a proper way to present this to Samsung so that I can get a replacement...