Related
I've noticed this strange process under *#*#4636#*#*, Battery History, Drop Down, Network Usage >>> An almost completely blue bar for this process "0".
I'm searched high and low with google and no one had posted exactly what it is or why its using so much in-bound data, on any forum.
Some people said it was FB or flickr sync, but I've removed both of those accounts, restarted the phone with startup cleaner stopping everything, and 5 hours later - without touching the phone - it's back.
I'm not sure if it was there before I updated to Fresh 1.0.1, yesterday, but I'm sure getting worse battery life since then.
Also, yesterday when I used facebook for well over 2 hours throughout the day, it's network usage bar was about 1/4th of what 0 was. :|
I've got the same issue, only used Unrevoked1, and 0 just loves to dominate the network activity bar. I would love to know why...
WOAH! WTF! Same issue here... What is this?
Not sure. I'm rooted with simple root, before the OTA from sprint, then running fresh 1.0.1. It was probably there before I updated, I just never checked.
I think it might be the HTC flashlite plugin. I have the app lookout running (tracks your phone, has virus checker and something else) and I see it popping up randomly saying that it's checked HTC flashlite plugin and it's secure, several times a day, even when I'm not using the browser.
Hell, it might be the Lookout app for all I know. Any of you using that same app?
'0' is the system of the phone, it's using battery because the phone is on.
mrono said:
'0' is the system of the phone, it's using battery because the phone is on.
Click to expand...
Click to collapse
Makes sense, but why does it only show up under network usage; why is it using so much more inward bandwidth when compared to to other data using programs below? It doesn't show up under CPU usage, ect.
Well, you could just try to be like this guy, and try to create a class action lawsuit because your network process is eating too much battery and offending you...
Just kidding...seriously...anyways, 0 process is just the system itself (I think...lol). You could take a more detailed look at it if you have a program like autokiller, and/or try to kill it to observe what happens.
~Jasecloud4
jasecloud4 said:
Well, you could just try to be like this guy, and try to create a class action lawsuit because your network process is eating too much battery and offending you...
Just kidding...seriously...anyways, 0 process is just the system itself (I think...lol). You could take a more detailed look at it if you have a program like autokiller, and/or try to kill it to observe what happens.
~Jasecloud4
Click to expand...
Click to collapse
Yes, you're right! I've also noticed that the "Seeds of Life" live wallpaper is using an extra 0.50% of my battery life every charge, therefore, I'm going to sue sprint, htc, google and every last damn sperm swimming around on my screen! These big money mongering companies need to give the end-user more control over how they use out battery life and collect out data. Fking sperms. Hahah.
Everybody is out to try to become rich, but 99% of the time in class-action suits, the lawyers are the people who make all the money. In fact, it'd hard to be in business and getting harder by the year.
thats really wierd...probably live wallpaper
I wondered the same thing and discovered something a bit curious..
If you go to proc/1 and look in the file status.
You get this
Name: init
State: S (sleeping)
Tgid: 1
Pid: 1
PPid: 0
TracerPid: 0
Uid: 0 0 0 0
Gid: 0 0 0 0
Then some more irrelevant info...
Notice the parent process id for the sleeping state is 0.
Does this mean that most of the our network usage occurs when the phone is inactive?
I would assume so.
Should we be worried about conspiracy, oh yesh.
Class action lawsuit part 2 here we come lol.
It's definitely weird. I've been using the browser nonstop since boot but its only about 1/3 of the 0 process..
Wish it wouldn't force close when we tap on it..
Bump.. I'm curious, has this been figured out yet?
I'm sure someone somewhere has an answer..
Guys.. 0 = root
Like mrono said its the system running itself, plus any programs that require root.
What you fail to understand, is that this is under NETWORK USAGE.
The system does not need a nonstop connection to the web.
I'm sure it's just data sync and that kind of crap but I have a hard time believing that an hour of HQ youtube takes less network usage than a sync or two.
This just a guess, but I'd say network process 0 is likely the system loopback connection.
pseudo_nomen said:
This just a guess, but I'd say network process 0 is likely the system loopback connection.
Click to expand...
Click to collapse
Yep. Im pretty sure it's the kernel that would handle the loopback.
Sent from my PC36100 using XDA App
nvm.......
Any update on this? I suspect the root 0 process (as seen in the already mentioned Network tab) is keeping wi-fi/3g connections constantly at full priority, causing excessive battery drain since WiFi never stops "Running" (if u look at your other usage stats in Spare parts or #*#*4636*#*#)
So, on the Linux side, PID 0 comes from the kernel.
PID 1 is init, which the the father of all processes, and initialized by the kernel.
Anything bellow that is initialized by INIT, and normally on the RC scripts.
So, all thi usage that your are seeing should be from the scheduling process of the linux kernel that Android is running on top of.
I have the same issue with my Desire Froyo 2.2,
I have Process 0 which uses Network, BUT when selecting "Total since boot" another weird process shows up: 1010 and com.android.settings also crashes when tapping on it (same as with proc 0).
Do you have the same process?
I also noticed that my router is showing in the logs my android phone as the one which does port scans using different technics like: Null scan, vecta scan, SYN scan etc.
I suspect this processes involved in this malicious activity! Those of you which has spotted process 0, can you see if you have the same in the your router security logs and get here with an reply?
I have the same exact problem. I'm not sure when but I think ever since the newer OTA's (3.28/3.29) I've been experiencing some terrible battery life. I did not have this problem with the 3.26 based ROMs. I think I'm going to try flashing the kernel to Netarchy and see if the problem goes away. My battery has been awful and I've mostly been idling the phone and sending the occasional text message/gtalk. (It's not syncing to Facebook or anything like that)
Hi,
I've found the same behavior across several different ROMs on different phones, one of them completely factory fresh and recent. I was lucky to record /proc/kmsg dump before the beginning of this behavior, and see it starting.
It looks like mmc0 stops getting correct data - at some point every transaction attempted results in CRC error, and kmsg is full of those errors. The phone during that time appears unresponsive - screen dimmed but not completely off, or soft buttons lit but screen doesn't appear, or when it appears - it doesn't react to touch.
Turning WiFi off and on after it happens seems to cure it.
Now, if I'm not mistaken, mmc0 is the SDIO interface to WiFi card. I see that "card0001 is attached" on it when WiFi is toggled on, and removed when WiFi is off. I believe that it's a dedicated interface and nothing else is connected to it. Kernel devs - can you confirm?
kmsg dump:
http://pastebin.com/zrDzNRUc
Starts looking weird at line 100:
<3>[ 1728.086883] msm_pm_wait_state(2, 0, 0, 0) failed 11001
Then at line 156 bad things start happening:
<4>[ 2736.639434] dhdsdio_checkdied: msgtrace address : 0x00000000
From this point, it goes down the drain until WiFi is turned off and back on (and the log ends on it).
So what I'd like to do, is to find the reason for this happening, and possibly make a simple workaround - I'd prevent WiFi turning off and on over a hung phone. Anyone with kernel / driver knowledge cares to assist? I'm not much of SW developer, but I know my HW.
I wasn't sure whether to post it here or in Development. It's not a Q&A thread, and I'm not asking for confirmations/opinions, unless people are rooted (that's a requirement to be able to dump kmsg), have enough knowledge and are willing to assist with gathering data / solving the problem.
Thanks.
Bump.
In the meantime, I'll try to change a kernel on stock FRG83 to see if it helps.
Seeing this as well. Hope you get to the bottom of it.
I believe many people started seeing it with FRG83. It might not only be affected by WiFi, but also Bluetooth - they're using the same SDIO path to the same BCM4329 controller, using the same MMC0 controller for access.
Since it was always present, but got worse with FRG83 - I believe it might be a race condition somewhere in the code.
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
As the title says, I have this issue on my N4.. It started on Tuesday night. I am on Slimkat at the moment because I cannot be bothered to flash yet another ROM anymore but it started as a problem on Paranoid Android BETA 2. However, it has persisted over Slimkat ROM and others along with different kernels such as franco's. I am not sure if it is a hardware issue although it is restricted to the bottom ~5% of the screen (i.e. the navbar) but it works fine when I am using the keyboard. Any other time, that bottom part of the screen is unusable. Over the past 24 hours it has become noticeably worse. I have the screen touch pointer enabled in developer options and I can see it slide left to right extremely fast at the bottom and doesn't stop unless I lock the screen and it happens randomly no matter what app I'm in! It also tends to get stuck in the bottom right corner quite a lot and if I touch the screen anywhere else, it zooms in so it is acting as though I am holding the bottom right corner with my thumb. Locking the screen and unlocking it fixes the issue for around 30 seconds but the bottom part is still unusable. After that 30 seconds it starts over again with the touch pointer going crazy.
I really hope it isn't a hardware issue as I have never dropped the phone nor had this problem prior to earlier this week. The logcat from paranoid android shows powerHAL is acting up and that touch_boost does not exist on my phone which should be there apparently. I have pasted a part of my logcat below and attached the full file if anyone is interested - scroll down about 3/4 of the way and it's all errors.
[ 05-06 02:17:04.118 793: 793 V/DeadZone ]
consuming errant click: (372.5,9.5)
[ 05-06 02:17:04.219 609: 763 E/PowerHAL ]
touch_boost: failed to send: No such file or directory
[ 05-06 02:17:04.219 609: 763 E/PowerHAL ]
touch_boost: failed to send: No such file or directory
[ 05-06 02:17:04.229 609: 763 E/PowerHAL ]
touch_boost: failed to send: No such file or directory
[ 05-06 02:17:04.229 609: 763 E/PowerHAL ]
touch_boost: failed to send: No such file or directory
[ 05-06 02:17:04.399 609: 763 E/PowerHAL ]
touch_boost: failed to send: No such file or directory
[ 05-06 02:17:04.399 609: 763 E/PowerHAL ]
touch_boost: failed to send: No such file or directory
[ 05-06 02:17:04.399 793: 793 V/DeadZone ]
consuming errant click: (179.5,9.5)
If anyone can help I'd appreciate it tremendously. I feel like this is mostly a software issue but I could be wrong. Thanks in advance!
Same problem mate since yesterday....my phone is 1year old too....and now the Navy bar isn't working....no idea what's the problem....I am on pa 4.3; beta 3....I think it's mostly the hardware....if someone could help us it would be great
Sent from my Nexus 4 using XDA Premium 4 mobile app
And you guys reverted to stock rom to see if It persist?, i had my bottom left of the navigation bar not working half a year ago with pa so I went to stock to make sure, it worked again and haven't had the issue since
same to me, same day, same issue. I also have no sensibility to the upper right corner of the screen.
I reverted to stock, the problem persists. I think it's hardware, as it appeared also in the touch recovery
Hello there,
been searching a solution for a while, but did not find anything that would help fix my issue.
My issue is that the screen turns black (not dimming, or fading to black but suddenly switching black), while the phone is still on.
This can occur under those conditions :
- Watching a twitch stream
- Watching youtube video
- Browsing a web page
- browsing the photo gallery
- playing some games
I know the phone is still on cause the audio is still running while watching video (stream and/or youtube), or playing a game.
What is really weir is that, for example when this occur in the photo-gallery, if I continue to scroll down (or up), the screen will re-appear as if nothing happens. Same when browsing some web page (mostly when this is a photo-gallery).
What is even more weird is that it will occur always on the same photos in the gallery. Let say I have a large number of photo (1000+), if I remove the photo that I identified as causing this issue , I can then browse the photo gallery without the screen going black (until i'll reach another photo that will cause the same issue). And it might as well occur only if in portrait mode, if I rotate the screen to be in landscape display, it would not occur...
So initially I had stock 5.1.1 (that was working quite well till this happened). I then decided to upgrade with OTA, but this issue remained. Other users complaining about similar behavior related to Moto attentive display being turned on/off would solve the issue for them... but that did not solve the issue. So that's why I decided to go for a custom rom.
I moved to CM13 yesterday with great hopes... but still the same issue occurs. (and during the CM13 installation process I did really clear all possible partition/cache/etc...). Even after the fresh install with stock apps, the issues occurred when browsing some web sites (always the same that I know for sure will cause this : TheChive, however other web site does also cause the issue) and after copying back my photos on the phone (photos taken with the internal cam) and browsing them with the gallery app.
Any clue what I should be checking ? Tried and adb logcat and captured the logs when I browse the gallery and got this black screen issue.
From the logs I see some weird things like "08-15 17:30:21.519 414 552 I qdhwcomposer: getPanelResetStatus: got change event in fb0 with PANEL_ALIVE=0
08-15 17:30:21.644 414 414 W qdhwcomposer: hwc_prepare: panel is in bad state. reset the panel"
08-15 17:30:20.538 5351 7327 D Paper : Rect(476, 36652 - 941, 37117)
08-15 17:30:20.540 5351 7327 D Paper : Rect(0, 36652 - 465, 37117)
08-15 17:30:20.540 5351 7327 D Paper : Rect(952, 36176 - 1417, 36641)
08-15 17:30:20.545 5351 7327 D Paper : Rect(476, 36176 - 941, 36641)
08-15 17:30:20.548 5351 7327 D Paper : Rect(0, 36176 - 465, 36641)
08-15 17:30:21.519 414 552 I qdhwcomposer: getPanelResetStatus: got change event in fb0 with PANEL_ALIVE=0
08-15 17:30:21.644 414 414 W qdhwcomposer: hwc_prepare: panel is in bad state. reset the panel
08-15 17:30:21.644 414 414 D qdhwcomposer: reset_panel: setting power mode off
08-15 17:30:21.644 414 414 D qdhwcomposer: hwc_setPowerMode: Setting mode 0 on display: 0
08-15 17:30:21.912 414 553 I qdhwcomposer: handle_blank_event: dpy:0 panel power state: 0
08-15 17:30:21.913 414 414 D qdhwcomposer: hwc_setPowerMode: Done setting mode 0 on display 0
08-15 17:30:21.913 414 414 D qdhwcomposer: reset_panel: setting power mode normal and enabling vsync
08-15 17:30:21.913 414 414 D qdhwcomposer: hwc_setPowerMode: Setting mode 2 on display: 0
08-15 17:30:22.116 414 553 I qdhwcomposer: handle_blank_event: dpy:0 panel power state: 1
08-15 17:30:22.119 414 414 D qdhwcomposer: hwc_setPowerMode: Done setting mode 2 on display 0
08-15 17:30:24.569 420 420 I MSM-irqbalance: Decided to move IRQ283 from CPU3 to CPU0
08-15 17:30:25.090 923 2718 D WifiStateMachine: starting scan for "BAS"-WPA_PSK with 2472
08-15 17:30:27.639 4473 5489 I ClearcutLoggerApiImpl: disconnect managed GoogleApiClient
Could it be some H/W gpu/ram issues ? still... got puzzled why this would happen always with the very same photos (which are readable with any other device or, if you rotate the screen for landscape mode...)
Really lost here.
Regards,
Manu
Edit :
I just noticed I had slightly different behavior if using the stock photo gallery 1.1.40030 (com.android.gallery3d) or the moto gallery 530032 (com.motorola.MotGallery2), in both case the screen will go black, but on different photos (but the result is consistent, always the same make the screen go black for each version of the gallery)....
Not specially focusing on "Gallery", but it's the easiest way to reproduce the issue.
Also had the issue while browsing some news web pages, on one part of the web page the screen will go (and stay) black, if I continue scrolling, the screen will then turn on again, and if I scroll up the page on the same place that caused this black screen, it will immediately go black again, etc etc... it's like if when a specific pattern is displayed, it will cause the screen to shutdown.... does not make really make sense... but 100% reproducible....
I recorded the display with a capture tool, to "see" what happens when the screen turns black. Nothing... on the capture the screen is always on, no glitch, screen garbage or display artefact whatsoever.
and since the question was asked, some more system details :
Cyanogenmod :CM 13.0-20160814-Nightly-clark
Kernel : 3.10.102-CM-g2396296 (13-august 2016)
Baseband : M8992_125531.29.01.88.02R
Does it go black sitting at the homescreen?
Kir6y said:
Does it go black sitting at the homescreen?
Click to expand...
Click to collapse
Nope, only in the listed apps (so far...).
I seen it a couple of times when I closed Chrome Browser v52.0.27.43.98 , but I haven't paid much attention to what I was doing when it happened, I think it was buffering, then when it caught up it displayed
What Build Number is it?
Stock or Custom?
February or May security update?
CLETjB said:
I seen it a couple of times when I closed Chrome Browser v52.0.27.43.98 , but I haven't paid much attention to what I was doing when it happened, I think it was buffering, then when it caught up it displayed
What Build Number is it?
Stock or Custom?
February or May security update?
Click to expand...
Click to collapse
mmm, yes I forgot to give some basic system info
So, I'm currently running Cyanogenmod :CM 13.0-20160814-Nightly-clark
Kernel : 3.10.102-CM-g2396296 (13-august 2016)
Baseband : M8992_125531.29.01.88.02R
But since I had the same behavior with stock rom I'm not sure this is really relevant...
Ok, I decided to flash back the phone with stock rom (5.1.1) and then update via OTA till 6.0.1 (build MPHS24.49-18-4 with May security update).
Now this same issue (screen going full black) happens almost anywhere (even on home screen). No apps installed, no data... looks like a hardware issue to me.
Has anyone else had this happen? I have this problem right now. Basically, either turning on the phone with the moto display screen or the power button, the screen will stay on for about 1 second and then turn right back off again. I am stock rooted, bootloader unlock with xposed running a few modules. Any advice. I just bought it on Swappa so I'm wondering if it's a hardware issue. Thanks.
Have you found any solution to this problem ?
xgerryx said:
Has anyone else had this happen? I have this problem right now. Basically, either turning on the phone with the moto display screen or the power button, the screen will stay on for about 1 second and then turn right back off again. I am stock rooted, bootloader unlock with xposed running a few modules. Any advice. I just bought it on Swappa so I'm wondering if it's a hardware issue. Thanks.
Click to expand...
Click to collapse
I'm also facing the same problem,
but the difference is it happens with a specific kernel i made for my phone
And, yeah, it is related to gpu, fb etc.
Thanks