Related
I'd like to know if anyone is having the same lag problems as I am getting from time to time..
The lag happens for no reason and comes at different times while doing different things.
I downloaded Watchtower from the Android Market to monitor what was happening. When the phone is running fast the /INIT process is showing as 0%..as soon as the lag starts to happen I check Watchtower again and the /INIT process is at anywhere from 70% to 100% CPU usage.
I dont use an app killer but I donwloaded one to try and see if it would correct the problem, it doesn't. The only way to solve the lag is to Restart the phone, then its fine for the rest of the day, sometimes two days but it always comes back.
I sold my SGS because of the lag issue and now it seems I have it with the DHD..
I did google this and I found that it maybe something to do with android itself..looks like /INIT is an android process..
If you notice your DHD lagging then download Watchtower and I'd bet you will see the /INIT process killing your phone..
------------------------------------------------------------------------------------------------------------------------------------
EDIT - A fix has been found to stop the /Init process lagging the phone.
On your phone go to..
Menu/settings/applications/development/now turn on Usb debugging..
This seems to keep the / init process at 0% CPU usage, it also works when the /INIT problem starts, turning USB debugging on will make the /INIT process drop back to 0%, very nice to see.
Ive contacted the Dev to find out if he can tell us why this method has fixed the problem.
Still need an update from Htc but at least we can use our phones again..
There doesn't seem to be any negative effects from turning this option on, the only thing to note is turning it off to connect to your pc could bring the /init process back and lag your phone. You can download Android Manager from the market for free which will allow you to transfer data from your pc using Wi-Fi, using this app you can keep the USB Debugging on.
-------------------------------------------------------------------------------------------------------------------------------------
EDIT 2 - It looks like you can connect to the pc via USB cable with the debugging turned on without problems, the only difference is that it will try and install additional drivers...because of the debugging mode..
Im using windows 7 and the ABD driver wont install...you need to download Htc Sync on your pc which downloads the ABD driver !!
We should also watch the battery as this may actually increase battery life...
-------------------------------------------------------------------------------------------------------------------------------------
EDIT 3 - Not one single person has come back to me and said that the /INIT problem has returned after this fix...lets hope it stays that way.. 10/11/10
---------------------------------------------------------------------------------------------------------------------------------------------------
EDIT 4 - A lot of people including myself have found that this fix improves their battery life quite a bit.
-----------------------------------------------------------------------------
Last EDIT before thread is locked just for reference and to help people !!!
For people that have the com.htc.bgp process that loads the CPU it stays at 80-90% all the time, and i have autosync on, if you stop auto sync the process goes out....
So here is the final fix in the link below (post 7)
http://forum.xda-developers.com/showthread.php?t=659325
Thank you to everyone in this thread for there efforts...amazing response.
Thanks to all the XDA Community...Including the Devs and Mods
Thread Closed
nednapalm said:
I'm getting the problem.
No apps installed except the flash and maps update, oh and OS Monitor.
Have turned off "Fast Boot" and removed battery to reset, ok for now. Very scared to start installing more apps, nearly unusable when it is lagging
Click to expand...
Click to collapse
I also tried the "turn off fast boot and it was ok for 2 days, it came back this morning though..It is very worrying and yes, the phone is unusable until it is Restarted..Thanks for the reply.
sanju007 said:
LAG WHAT?
I hope not, the samsung galaxy s have lag issus and its very bad and i sold de sgs
And now the DHD gets also lag problems ?
Ik hope not, then i will not buy this phone
Maybe an good task killer wil help ?
More people have lag issus ?
Can you make a video ?
Click to expand...
Click to collapse
An app killer doesn't solve the problem and Im unsure how many people are having this problem, to my understanding its not many...that's why I started this thread to try and find out.
I wouldn't worry yet...
I will make a video when it happens again...it may take a few days to come back....but it always does...a video added to this thread would be most useful...just have to wait till it rears its ugly head again.
So it seems that /init is a core process regarding the initialisation of the Android system and userspace hence the fact it cannot be killed using OSMonitor. It is always the first process that runs on Linux systems after boot and acts as a parent process which itself initialises then processes needed to get the OS going.
Here is a description of the Android Init Process from elinux,
'init'
A key component of the Android bootup sequence is the program 'init', which is a specialized program for initializing elements of the Android system. Unlike other Linux systems (embedded or otherwise), Android uses its own initialization program. (Linux desktop systems have historically used some combination of /etc/inittab and sysV init levels - e.g. /etc/rc.d/init.d with symlinks in /etc/rc.d/rc.[2345]). Some embedded Linux systems use simplified forms of these -- such as the init program included in busybox, which processes a limited form of /etc/inittab, or a direct invocation of a shell script or small program to do fixed initialization steps.
The init program processes two files, executing the commands it finds in them, called 'init.rc' and 'init.<machine_name>.rc', where <machine_name> is the name of the hardware that Android is running on. (Usually, this is a code word. The name of the HTC1 hardware for the ADP1 is 'trout', and the name of the emulator is 'goldfish'.
the 'init.rc' file is intended to provide the generic initialization instructions, while the 'init.<machine_name>.rc' file is intended to provide the machine-specific initialization instructions.
The Bug
The /init bug has presented itself on numerous handsets including the HTC Desire, Nexus One and Droid X models. It seems to be specific to Android 2.2 and reports the same symptoms on all handsets. Primarily this is due the 99% CPU usage causing system slowdown and left unchecked, high battery usage. It is not specific to HTC Sense ROMs as it also presents itself on stock releases. The only solution so far is a reboot. Hard Reboots and altering system settings seem to have no effect on the reproduction of this bug.
I can only speculate to what is causing the issue and hopefully a Dev can shed some more light.
Logically it seems as though a 'rogue' process is triggering /init to resume its primary function in regards to checking filesystems and attempting to spawn other system process. Due to some form of miscommunication between the processes in question, /init continues to perform these post boot tasks in a constant loop.
Think of it like this, if you try perform tasks straight after boot, the phone is unresponsive while the SD is mounted/checked and all other processes are fired up. The /init process is responsible for these tasks. If it were to loop, you would experience the symptoms we are having.
I found this on Wikipedia:
After /init has spawned all of the processes specified, init goes dormant, and waits for one of three events to happen:- processes it started to end or die, a power failure signal[clarification needed], or a request via /sbin/telinit to further change the runlevel.
So our trigger should hopefully be narrowed down to these three events.
Regarding what I posted before, the connection between sync and the bug has proven itself to be a false one.
I've also noticed that sometimes the bug can be present, however there is little impact on the responsiveness of the OS. It can seem as though everything is ok yet the CPU load can be extremely high, resulting in poor battery performance.
Anyway, hopefully more people can contribute to this thread so we can build up a better picture of what is going on. I will also try and grab a Logcat and ask anyone else near their PC when it happens to do the same.
There is a thread here which has users complaining of the same problems, yet no solutions are presented. Hopefully we can make a bit more noise and get some definitive answers.
Regards.
Hey guys some great feedback here, as with my link on starting this thread the /INIT is an android 2.2 process, auto sync on/off doesn't solve the problem neither does a hard reset, taking the battery out ect...
The guy in the link says his method worked for him, can't say the same for myself, I have a feeling his problem will be back...but if it did fix it for him then thats great, just cant say the same for me
http://forum.xda-developers.com/show...3&postcount=42
I have gone 5 days without the problem coming back and then Oh no its back, sometimes it happens twice a day, all the above doesn't fix this problem im afraid from what I have experience anyway.
The /INIT process is only 132k, something so small causes the phone to be basically unusable....very frustrating.
The 1.32.405.6 update also doesn't solve this problem, I updated yesterday and 10 min later I had the dreaded /INIT problem...
The so called "turn off fast boot doesn't fix the problem either, I have had the /INIT lag problem with it switched on and off...
What I find to be the most strangest thing is that if this is indeed an android process which it most likely is then why doesn't every DHD phone have this lag from time to time???.....why only certain phones??..
I haven't had the problem since yesterday (around 12 midday), when it occurs again I will be posting a video as requested...
The mystery continues.......There is NO solution as yet that fixes this problem.
Thanks to Lynxboy, your posts give some good information.
I wonder if this has any relevance to the problem from a linux based PC..
It seems that /INIT uses the same Process ID - 1 (found from using watchtower)
http://www.yolinux.com/TUTORIALS/LinuxTutorialInitProcess.html
BigMango said:
You purchased it from ebay, but did you buy it from a shop or from an individual (second hand)?
If you got it from an ebay shop they should give you a receipt. If it was from an individual, he should give you his original receipt (that's when the warranty started).
Anyway, the phone has a 2 years warranty, so you are covered for the next 2 years minus 1 or 2 weeks. And the paypal transaction is a valid payment receipt (it can be verified directly with paypal); so even without the receipt from the first owner HTC should cover you since the phone can't be 2 years old.
Get in touch with HTC directly, they should replace it. But the tricky part is that the problem must happen when they check it out, for this reason I would also make a video of the problem the next time it happens and send it to them by email so they can keep it on file with your RMA.
Click to expand...
Click to collapse
Thanks for the advice, Im going to contact the seller, he had it on upgrade and shipped it to me the following day..he seemed a nice guy so It should be ok...Now its just a matter of waiting for MR INIT to show up haha....wonder if he wears a hoodie LOL
bimmerfox said:
I'm not wrong because I see it with my own eyes. Even my DHD had the same problems as described. After the update no more /INIT at 90% and it keeps running smooth now.
Try to keep your patience before quoting a person who is willing to help others.
Click to expand...
Click to collapse
What?? Why do you think I made this thread...to help myself and others...as we do at XDA....the update doesn't fix the problem....just because yours hasn't lagged since the update doesn't mean its fixed....I've gone 5 days with no lag and it came back...like yours probably will.
Ridiculous....
EDIT- You can't post a statement that the problem as been fixed when numerous people have done the update and still experienced the /INIT problem...how can it be fixed??...and since the update only came out yesterday you have no way of knowing this for sure... its way to early to say that.. Try reading through posts in the forum and gather some information next time.... the update was for the youtube fix, we're not even sure that HTC were aware of the problem at the time.
Hi guys,
Just finished work and have caught up with the thread since I last posted and wanted to clarify a few things. I would also ask any new readers to find my previous post which covers much of the nature of the /init process.
The problem is solely software based. The hardware is NOT at fault!
The /init process is the parent process of Android/Linux, hence the PID 1 in OS Monitor. Imagine it as the ignition system in your car. You need to turn the ignition to fire up the other systems and that technically is the role /init takes.
It is not a rogue process in itself. It cannot be killed or closed via a task manager.
The latest update was not a fix nor does it resolve the issue.
The bug IS a Froyo bug and affects numerous devices not just the DHD although it is not present in all Froyo ROMs.
It is possible the memory management is to blame however I have run many Froyo based ROMs from FRF55 and not experienced it before; they all use the same memory management.
The three triggers for /init to awaken after its boot tasks are completed are specified in my previous post. These are the most likely causes for our issue and are in my mind triggered by some rogue process interactions.
A logcat will only really be useful if it captures the event taking place. A logcat taken when the /init process has started will report back specifically that.
Just because you haven't experienced the bug in 2days doesn't mean you are bug free, nor is there a bad batch of phones as this would indicate a hardware issue.
Continuing this thought, it is possible if you are on a branded operator ROM you may be bug free.
The /init bug is extremely annoying.
Regards.
Yes off topic...
Im asking the mod to still keep this a sticky but to lock the thread as there is really nothing left to discuss and its just here for people that are still having the /init problem as a reference...
EDIT - Thread being locked soon so....
Agian thanks to all xda community !!
Is this stickie needed anymore? Has this been corrected by any software update?
I've had this problem since the day I got the phone (December 2010) and got it again today. Once I see the obvious lag of everything, I just restart.
If it can help...
I have noticed this phenomenon the first time just after installing 2 things in my DHD :
- creating the HTCSense account (and keeping it synchronized one a day)
- installing the HTC plugin for Picasa Web Albums in the Album application.
Maybe coïncidence, maybe not.
I have disabled all HTC Sense stuff I can see. It always happens when performing some action, like opening a new app. It seems to occur so randomly, it happened again the day after my last post, but has been fine since then.
Problems with calendar after removing cache and program data.
I had major problems with com.htc.bgp using up to about 90% of my processor from time to time. When I searched the forums I found this thread.
I tried what is stated in the top post and went ahead and cleared the calendar data and the gmaill data. This is all fine, I don't seem to get any more warnings about com.htc.bgp reaching the 90% mark. One slight problem that occured though is that now when I'm syncing my calendar back to what it was, it either does not search or does not find all the other calendars that I have. The list is just totally empty. Strange as it is, It does find and sync with the default [email protected] Gmail's working fine and syncing properly though.
Since I rely on the calendar I really need this to be fixed as soon as possible.
I don't want to put words in your mouths, but I figured I might need to factory reset the phone. No biggie, but a time consumer, since I need to recustomize everything again (not rooted, not titanium).
Are there any ways of luring the calendar back on track. Jumpstarting it without a factory reset?
Thanks in advance.
Henrik
So apparently all it needed was a full night of syncing, because now it works again.
It seems though that I got rid of the annoying com.HTC.bgp that drained my processor.
Thanks to the thread
Sent from my Desire HD using XDA App
Have not experienced this since the 2.3.3 upgrade, problem solved!
I'm having this problem on my Defy after installing SetVsel, setting any values, after time the cpu stuck at 100. Watchdog lite didn't show nothing but 100%, not any process higher than 50 even. I turned on in the watchdog to show system processes and ther it showed that:
init
Linux process
Had most the time the highest percent used
I googled and found this topic. The
Menu/settings/applications/development/now turn on Usb debugging.
Click to expand...
Click to collapse
solution solved my problem. The proc isn't anymroe stuck at 100%.
I have searched through XDA and read all the threads regarding the 'suspend process' issue. The specific issue is outlined in Issue # 11126 on the Google Code/Android project home...
http://code.google.com/p/android/issues/detail?id=11126
I am trying to get to the bottom of this, as best as possible. For all intents and purposes, this really appears to be a mystery. Ultimately, it appears as though there is (currently) absolutely no specific reason a to why 'suspend' runs wild until the device is rebooted.
My question is (I know we can all only speculate):
Is there any chance that this could be Google account-specific?
The reason I ask is, I've been doing some "testing," just to try and make sense of this for myself. Here is what I've done/come across thus far...
- My fiancee's first MT4G was a black one manufactured in Taiwan. It had the inferior LCD-SH-C2 screen. Her battery was draining VERY quickly - i.e. before noon, without using the phone for much else other than texting.
- I enabled USB Debugging for her, to "rule out" the init process issue.
- Even though she only had Handcent, Facebook and Angry Birds installed, I removed all of them, leaving only Watchdog.
- I factory reset her phone, twice.
- For all of the above, the device was not rooted. I have since rooted her phone via the steps in this thread.
I'm in the process of creating a new Gmail account for her, exporting ONLY her contacts and then using that account for her new MT4G (Plum) that's scheduled to arrive today. I'm actually thinking of NOT using her new Gmail account at first though, so I can use her original Google account on this new, clean device and see if the suspend issue persists.
I might just be wasting my time, but I enjoy doing this and I don't think it's a complete waste to try and find SOME constant here. Am I nuts for thinking it's tied to the Google account? The Google account seems to be a black box of sorts. There is more than just contacts, apps and settings, yet there is no "window" into everything else that comes down - e.g. I can't log in to Gmail and "configure" it to not restore her wallpaper or WiFi settings. So that's why I say it's a black box of sorts, since it's doing more in the background than we have control over.
Nothing is truly random, at least not in the context of Android and the hardware affected. There has to be some reason why users of various devices, either do or do not experience this issue. Whether it's a specific action or the something that differs between one person's action vs. another person's, there has to be SOMETHING that's triggering this on her device, yet never triggers it on mine. I guess I'm just trying to flush everything out and hope that discussing it will help rule out/rule specific variables.
Let me know what you find. This is driving me crazy! I charge my phone at night, so when I head to work it's at 100%. By the time I'm heading home (4-430pm)... the phone is around 15% battery.
Watchdog tells me suspend ranges from 5%-49% at any given time. I've never had suspend drop below 5% except on fresh reboot. I've noticed, though, after a reboot that the suspend process will slowly work its way back up to using lots of CPU cycles (it starts at, say, .2%, then 10 minutes later its 3%... 30 minutes later its 5%... an hour later its 9%). Battery just gets hotter and hotter due to this.
I'll be checking back to see what you find! Thanks!
mwelliott said:
Let me know what you find. This is driving me crazy! I charge my phone at night, so when I head to work it's at 100%. By the time I'm heading home (4-430pm)... the phone is around 15% battery.
Watchdog tells me suspend ranges from 5%-49% at any given time. I've never had suspend drop below 5% except on fresh reboot. I've noticed, though, after a reboot that the suspend process will slowly work its way back up to using lots of CPU cycles (it starts at, say, .2%, then 10 minutes later its 3%... 30 minutes later its 5%... an hour later its 9%). Battery just gets hotter and hotter due to this.
I'll be checking back to see what you find! Thanks!
Click to expand...
Click to collapse
According to XDA and Issue #11126, you're not alone.
What's really bugging me is that neither my first MT4G, nor its 1st replacement or its 2nd replacement, have ever done this. My fiancee's first phone did this. She is now using my 2nd replacement while she waits for hers to arrive (today). So a device that never exhibited this issue, over the course of at least a week of normal-for-me use, started exhibiting this issue for my fiancee maybe a day or so after using the phone.
I thought I had "solved" it when I didn't see it crop up the first day she used my replacement phone. She was quick to let me know I was incorrect.
So I've got serious pressure here - all of my MT4G's haven't exhibited the out of control 'suspend process' issue while I was using the devices, but with her, it does. <queue the jokes>
We own our own business, so we're in the same room all day long while we use our phones. I was the first to tell her, "it's something you're doing." I'm only repeating myself by saying that I blamed it on an app she installed or something she "did" to cause it. After factory resetting, what...2, 3 times...I'm starting to forget; after checking the apps that are installed (and removing all of them); after verifying every setting from USB Debugging, screen brightness, account sync, etc. I seem to at least be able to say, "every single setting, shortcut, widget, app or usage pattern, does not produce the issue on any device I have used with my Google account, whereas it does with my fiancee."
That's the most difficult part to get absolute - the usage pattern. She's doing such basic things though, but I know that even the slightest of difference can produce different results.
I will most certainly report my results, futile or not.
The only common denominator I've noticed so far is that it only affects Sense UI devices.
Chadastrophic said:
The only common denominator I've noticed so far is that it only affects Sense UI devices.
Click to expand...
Click to collapse
That seems to be the constant, to a degree. I'm seeing people state that they're having this issue on anything from the Samsung Galaxy S (i9000) to a Nexus running Cyanogen 6.1. That's people stating it though, so I'm not sure if they're actually experiencing the same issue or not.
I am biting my tongue, but I think I found another common denominator...I am going to post back in a coupla days once I've seen it last for this entire week.
hi,
i'm running cyanogenmod 6.1 on a desire hd and have been experiencing the suspend process problem exactly as described in this thread a nubmer of times now over the last week. so its definately not limited to devices running sense.
the only circumstances this behavior hasnt shown is when running 2g only with all other sorts of communications and sync off
zero_oli said:
hi,
i'm running cyanogenmod 6.1 on a desire hd and have been experiencing the suspend process problem exactly as described in this thread a nubmer of times now over the last week. so its definately not limited to devices running sense.
the only circumstances this behavior hasnt shown is when running 2g only with all other sorts of communications and sync off
Click to expand...
Click to collapse
Yeah, it didn't seem 100% related to devices running Sense, so thanks for posting back to this.
My fiancee was experiencing this across her first two MT4G devices and has yet to experience the issue on her third and final MT4G. I want to see it run the rest of the week though before I share, but the issue did pop-up for her pretty much within 24-48 hours on her first two MT4G's.
Shlongwoodian: I have been following your posts as the "suspend" process has been affecting me since I received my phone the first day available. However, I am reluctant to send for a replacement as all else is great on the unit I have and there seems no gaurantee that a new phone fixes this issue.
I have tried Tmo and HTC and both seem clueless; therefore, I appreciate your research and look forward to any "fix" short of waiting for Gingerbread.
Anyone have any wisdom to pass on? This issue is driving me crazy! I've noticed it most on my black MT4G (w/the good screen) after browsing the web, youtube or using the media player. My wife's red MT4G (w/the inferior screen) has had no issues and her battery is amazing! The first day she got her phone her battery lasted 24 hours without even conditioning it! Granted she doesn't use it like I do mine, but it is still a huge difference. When this issue comes up on mine, I'm dead within 3-4 hours. I have Watchdog set so when it alerts me I just soft reset. That clears it up until it decides to come back at random intervals. It usually doesn't come back until I open the browser, etc. With as much as I use my phone (I am constantly on the road), it becomes a major pain to have to constantly monitor battery life. Any help is greatly appreciated!!!
Man, I am sorry to report that I gots nothin'. Ok, here was my original theory...
I was speculating that "something" inside the Google/Gmail account was the cause. My reasoning being, essentially, your info is stored in a database. When you get an Android device, that online database is synced locally with the phone's database. We each have different databases and there is more than just your apps, Market links, contacts, etc. I never exhibited the /suspend issue on phones that she experienced the /suspend issue on. I figured it was database-specific.
If a table contains a value, or rather, does not contain a specific value (or if columns are missing, etc.), it can cause an application to respond in a negative way. Sometimes, this causes an error to bubble up in an application. Other times, it doesn't. In my experience, I've seen much more subtle issues in databases, that don't cause errors or a crash, but instead just cause "undesirable results."
When my fiancee got her final, good replacement Plum Glacier, we started with a completely new Google account. We thought we nailed it, when a handful of days passed without seeing /suspend get out of control, leading to Android System and/or OS sucking down battery life. I think it was nearly a week into it and one day while she was out, she realized she lost battery life really quickly - i.e. left the house with 90% and by the time she got to the store, shopped for a bit and looked, her phone was down to like 30-40%. She knows how to check for /suspend and it was, of course, back.
It's still not something that can be completely ruled out, since it's not a very air-tight test. There could be something about my Google account (which I've had pretty much since Gmail beta was available) that's keeping me (and others like me) from getting it or that idea could be crap.
For some reason, I have never, ever seen this happen on my Glacier(s) running stock 2.2.1. Phones that I never saw the issue on, she saw the issue on. There is so much speculation around it, but it just seems like "some people" don't experience it and "some people" do. It's all over different devices, different skill levels, etc. No apps, same apps, whatever and it happens to some but not others.
Sorry to get anyone's hopes up. I'll keep looking for differences/similarities though and if I find anything at all I'll - or if anyone else finds anything, no matter how ridiculous it sounds (yes, we've tested the 'rock' and it doesn't appear to suffer from the /suspend issue) - post it here.
Thanks for trying! It was a good theory. So . . . now what? Is there any way to get this ranked higher with Google, HTC, etc. to get more people working on it? It is really driving me nuts! It mainly happens after I use the web browser, then put the phone on standby for some reason. I can't even use the browser any more without needing to reboot it to save battery life. There is another thread, but specifically for the Evo and I think one for the Nexus one, all with the same problem. What if a new thread were started that is not device specific? That way we can get more people to star it and maybe Google or whoever will pay more attention to it! I would hate to think that we are stuck with this problem until when and if we get upgraded to 2.3. I would suggest rooting and flashing a new ROM, but even those with custom ROM's are having the same problem, so that's not going to help. Thoughts???
jpiano said:
It mainly happens after I use the web browser, then put the phone on standby for some reason.
Click to expand...
Click to collapse
It truly is a mystery to this day. I've seen people say, "it happened right after I installed Handcent" or "it happens as soon as I do..." No one has come up with any concrete evidence thus far.
My fiancee has Handcent, I have Handcent. I used Handcent heavily, never had an issue. She stopped using Handcent - still has the issue. We've gotten so granular in our troubleshooting, we're literally tracking every step. LOL i.e. I pressed the trackpad to wake the phone, once; I unlocked the phone, I swiped my thumb once to view my Watchdog Widget on the screen to the left of my homescreen, etc., etc., etc.
So, for now, we just wait? My phone (and all previous phones) have been just fine. My fiancee however...yeah, I'm trying to find a fix pretty quickly.
One common theme that I've seen with this issue is that it only happens after I put the phone to sleep. I have never seen it crop up while actually using the phone. Maybe we're going about it the wrong way in trying to identify an app, etc that's causing the problem... perhaps it is simply the code involved in putting the phone to sleep and that's why there hasn't been any consistency with what one does to make it appear. In your experience, have you ever seen or heard of it showing up while the phone is being used? Perhaps it's just on mine that it works that way, but I thought it was worth mentioning. I know nothing about code or how android works so please forgive the noob comment if this is an obvious one. Merry Christmas!
I've got this problem big time. Returned my first phone because I thought it was the phone. First few days were good but lately its back and as bad as ever. First thoughts were angry birds twitter or wifi but I have no idea. If I can't figure this out I might have to sell this phone.
I will try to post some more thoughts. I think you're onto some good ideas here.
Sent from my HTC Glacier using XDA App
(Re-posting from the developer's Google blog where others are following this issue): Interesting about using the phone without a Google account. Not sure if this is relevant or not, but I've noticed something else with consistency. Granted I wasn't able to document the behavior through system panel at the time, but this has consistently happened. When suspend goes crazy, I can get it to stop simply by charging the phone! Even if I charge the phone for a few seconds, then unplug, it stays dormant without having to reboot. Noob speaking here but perhaps the part of android that actually logs the battery usage is suspending when the phone goes to sleep? When it us charging, this log is reset and clears the process from running. If this is even possible, then could someone write an app that clears this system log? Maybe by mimicking what happens when the phone is charging, we can at least temporarily clear the issue without the need tovl reboot? Again, I know nothing about all this so sorry if this is all irrelevant. Just sharing what I've noticed to be consistent. Thoughts??
Also, I saw on another xda blog (http://forum.xda-developers.com/showthread.php?t=870557&page=2) that someone linked this issue to a corrupt photo on the sd card. After formatting the card and restoring some files, says the issue has not returned!
jpiano said:
Also, I saw on another xda blog (http://forum.xda-developers.com/showthread.php?t=870557&page=2) that someone linked this issue to a corrupt photo on the sd card. After formatting the card and restoring some files, says the issue has not returned!
Click to expand...
Click to collapse
I wonder if you're on to something with the SD card. I've been thinking I haven't seen the suspend issue return on my phone in quite a while. I just realized that the only thing I've really changed is installed a new 16 gb SD card. Since then, no suspend process problems. For those who are having the problem still, I wonder if removing or formatting their cards would show any improvement? Worth a shot if at least to eliminate another possible factor.
Sent from my HTC Glacier using XDA App
That's cool that this thread is flushing out other ideas and possible variables. I like the idea of connecting it to the charger for a couple of seconds, but my fiancee is so used to just rebooting her phone each morning and sometimes again by mid-day, that it's easier for her to do just that.
jpiano said:
Even if I charge the phone for a few seconds, then unplug, it stays dormant without having to reboot.
Also, I saw on another xda blog (http://forum.xda-developers.com/showthread.php?t=870557&page=2) that someone linked this issue to a corrupt photo on the sd card. After formatting the card and restoring some files, says the issue has not returned!
Click to expand...
Click to collapse
I like the microSD Card notion. This is such a weird issue, that it's so easily associated with other items - e.g. applications, usage patterns, etc. This seems feasible though, but the only way to know for sure is to reproduce it. My fiancee experiences the suspend issue daily, if she doesn't reboot regularly. So, I should be able to take her microSD card and use it in my phone and get the suspend issue. I don't want to 'muddy' up by swapping microSD cards, so I'll try reformatting her card and see if that makes any difference. She usually sees the issue within 24-48 hours of a fresh boot, so it shouldn't be long before we see if that fixes it or not. I can check the card for errors, etc. as well.
werk said:
I just realized that the only thing I've really changed is installed a new 16 gb SD card. Since then, no suspend process problems.
Click to expand...
Click to collapse
I'll be upgrading to a 16 GB Class 10 soon, so I can give her my Samsung if need be. I'd really like to see if this is it though. It would explain the "some people get it and some people don't" pattern.
I also noticed that the minute I plug the phone in the problem goes away. Not sure why, just confirming it happens to me too. I also should note that when I returned my phone, they popped my old SD card into my new phone. So if there is an SD card issue with a corupt file/photo that could be something as well. I wonder woody if your girlfriends phone has had the same SD card after how many times did you say you traded it in? BTW, a side note, how did you exchange it so many times? After I took mine back to the store on day 14 they told me I wasn't able to exchange it again.
I do have a 16GB SD card but just haven't had time to install it. Wanted to double check which things I need on the new one from the old one, but it might be a good way to test this issue. Let me know some ideas before I swap the cards and maybe I can help test this.
Also, one more thing, what is the app you're using to log stuff? I'm just using Watchdog Lite right now.
I've got to figure this out or this is a dealbreaker for me. I have waited 3 years to upgrade phones, first time on Android, really wanted iPhone but wanted to stick with month to month from TMob. If this continues I think I will move to Windows Phone 7 or iPhone if I have to, but I really like this phone when the battery is not draining like a leech.
Thanks.
werk,
Just wondering what process you went through when you upgraded SD cards. Did you copy any files over to the new one or just start blank?
Thanks.
royhobbs said:
werk,
Just wondering what process you went through when you upgraded SD cards. Did you copy any files over to the new one or just start blank?
Thanks.
Click to expand...
Click to collapse
Just straight copied the existing files over from the old card to new one (new one in phone connected via USB, old card in SD adapter in my laptops SD card slot). I think some Angry Birds files didn't make it due to long paths, but reinstalled it and no problems since then.
has anyone done this yet? I noticed it in the settings, but it said it can take up to 1 hour... just wondered if it was worth while.
if you have done it, does it slow anything down, and how long did it take you to run?
Sent from my HTC Desire using Tapatalk
iamdarren said:
has anyone done this yet? I noticed it in the settings, but it said it can take up to 1 hour... just wondered if it was worth while.
if you have done it, does it slow anything down, and how long did it take you to run?
Sent from my HTC Desire using Tapatalk
Click to expand...
Click to collapse
I tried but it appears to not work. You have to be plugged in and fully charged (seems to work from 90% ish), and you have to have unlock PIN set. But once you have selected and confirmed encryption, the screen blanks except for a green line drawing of an Android logo, and then after a minute or so the screen blanks out and then you wait...and wait....and wait...and wait. I gave up after 4 hours.
If at any point you switch screen on, you get the PIN prompt: enter PIN, and you're presented with the blank screen with green line diagram of android logo. I've left it like this for several hours. In the end I reset, and got my device back - but still unencrypted. I've also tried without ever trying to log in until at least 4 hours have elapsed, in case the login attempt disturbed the encryption.
I have logged a defect with Asus for this and a couple of other things, and this morning got a response back saying that "We're still looking into this", which seems to suggest that they agree it is a problem.
Cool in gonna try now, at 95percent battery.
Sent from my Transformer TF101 using Tapatalk
That didn't seem to do anything.... I saw the green android with cog body, maybe I need to give it more time. I will set out before i go bed.
Sent from my Transformer TF101 using Tapatalk
I'm wondering how the encryption is handled, is it software or hardware enabled. I have seen with PC's that use software encryption that there is a performance hit and if the encryption is handled by hardware, like a hardware enabled HDD encryption, there is little to no performance hit. The PC I tested the software encryption on took forever to boot vs the hardware enabled one.
Havoc6266 said:
I'm wondering how the encryption is handled, is it software or hardware enabled. I have seen with PC's that use software encryption that there is a performance hit and if the encryption is handled by hardware, like a hardware enabled HDD encryption, there is little to no performance hit. The PC I tested the software encryption on took forever to boot vs the hardware enabled one.
Click to expand...
Click to collapse
You must have used some strange encryption application or had an old computer.
Try truecrypt - on modern (2 core) computer there is practically no performance hit whatsoever (decrypting and even encrypting on the fly is faster than hard drives - on SSD it could be too slow though). The same goes for standard encryption used by Ubuntu (it's very probable that Android tablets use the same method).
Truecrypt (and probably most other full-disk encryptions too) work like that:
- all the data on hard drive is encrypted (edit: it's encrypted all the time, never, ever is decrypted data written to disk),
- when system reads data - it's decrypted before being send to applications,
- when system writes data - it's encrypted before it's saved to the disk.
Also - Tegra2 should have a part handling encryption and decryption so it could be at least partially hardware encryption.
Your right, it has been a while since I have used encryption due to a bad experience early on. I'll give Truecyrpt a try. The software I used before was Safeguard Easy.
iamdarren said:
That didn't seem to do anything.... I saw the green android with cog body, maybe I need to give it more time. I will set out before i go bed.
Sent from my Transformer TF101 using Tapatalk
Click to expand...
Click to collapse
I left mine overnight, and it still was not encrypted. I had even done a factory reset beforehand to minimize the amount of data to encrypt.
I'm pretty sure this doesn't work. I'll post as soon as I get a reply from Asus.
It did not work, maybe this feature isn't ready yet?
Sent from my Transformer TF101 using Tapatalk
As a feature, it's not ready for prime time. I have it working on the xoom, but every reset it erases my timezone and sets it to GMT. Also, it uses the same PIN as your lock screen, so if you have a numeric pin for easy access, anyone who sees it now knows your encryption password as well. It really should be two different passwords. I intend this weekend to reset my machine and remove the encryption, because it doesn't serve the purpose it was supposed to serve.
Bump. Any info from Asus? I started it at ~7pm. It's midnight, and on the last few power-ups I get nothing except the green android logo after I enter the PIN. So it seems it's still not doing anything? Gonna reset now I guess.
Same problem here with a Transformer TF-101 Build number HRI66.TW_epad-8.2.3.8-20110423
See nothing but a android robot after enter the PIN. 7 hrs later I manually shutdown the machine.
Same here on the Modaco ROM.
Left it on the android pic for 9 hours... it didn't lock the screen or anything, and at the end, the accelerometer still worked when I rotated the screen, but I had to power off and on to get it back.
What does the encryption do, anyway? Does it stop you being able to load files on from the PC? Does it ask for the password when you plug it into the PC?
So no one has been able to get encryption working? I was just going to test this out and saw this thread. Thanks.
I've seen someone talking about some minor issues when running with encryption, so someone got it working.
That MIGHT have been on xoom, but I think it was the transformer.
Just thought I would share my experience with the encryption feature in Honeycomb since some people can't get it working:
At first I couldn't get it working like some people on this thread, I too was stuck on the green wireframe Android for hours on end until I discovered I could still exit back to the homescreen by pressing the home key on the keyboard dock. This happened on both the stock Asus 3.1 ROM and v1.4 of the PRIME! ROM (installed via nvflash).
I then updated recently to v1.5 of PRIME! via CWM and I can report that I was able to encrypt my Transformer after this update. It displayed the green Android wireframe logo for a few seconds, then rebooted and went into the encryption progress page. I had not really done much with the ROM other than change a few small settings and add my Google account, so the encryption was complete in less than an hour. I think the 'hour or more' estimate Google gives within the encryption description text is probably more accurate if you've installed a few more apps afterwards, but of course your timing will vary.
Furthermore I think that the encryption is likely only partial, because I was then able to flash one of the zip files from this thread via CWM without any issues or prompts. Otherwise I'm sure it would've thrown some kind of error such as not being able to mount the system partition or something of that ilk.
Finally (lol ) I also found this page on the Android source website outlining the details of the encyption implementation in Android Honeycomb for anyone interested. There is a mention somewhere of the 128-bit flavour of the AES algorithm being used to encrypt the master key.
Hope this helps anyone trying to get encryption working on their Transformer .
yet another absolutely useless feature, besides bricking the thing for whoever tries to steal it. keeps your data safe.. even from yourself.
i noticed a problem when inserting a microsd (into the pad itself) that it would not be able to boot as long as this is inserted. i am guessing this is because it tries to decrypt the microsd (that is not encrypted) and therefore is stuck in boot.
This is another aspect one should expect if this was a pre-release software. I am extremely disappointed with this product so far, mostly because of the software. most of (not any of the cameras) the hardware (including the keyboard) is pretty good
I did it 2 days ago, and it worked flawless. It tooks about an hour. I use it since and I have no problems at all.
The only thing is that I have to insert the SD card again each time I power on the transformer. Any idea how to change rhat?
fjoesne said:
yet another absolutely useless feature, besides bricking the thing for whoever tries to steal it. keeps your data safe.. even from yourself.
i noticed a problem when inserting a microsd (into the pad itself) that it would not be able to boot as long as this is inserted. i am guessing this is because it tries to decrypt the microsd (that is not encrypted) and therefore is stuck in boot.
This is another aspect one should expect if this was a pre-release software. I am extremely disappointed with this product so far, mostly because of the software. most of (not any of the cameras) the hardware (including the keyboard) is pretty good
Click to expand...
Click to collapse
You likely have ASUS to blame for this, as my understanding is that the Thinkpad tablet deals properly (from the spec anyway) with SD cards attached to the device even to the point it can additionally encrypt them. Again we are all early adopters, Honeycomb was sort of an experiment for Google, and Ice Cream Sandwich is the real next version of the andoid platform.
And encryption is hardly a useless feature, it means Google is finally trying to consider enterprise usage of their products which is very important to the further growth of the platform.
Anyone else expiriencing this problem? For me it goes like this:
At random times the screen gets sluggish in the transitions, and stay this way for quite a while. While this is going on, I can't long-press anything, because of the "lag" the screen doesn't register long-press, but single-press. Meaning there's a bunch of features I can't use..!
It doesn't just regard the GOlauncher stuff, but all of it, like f.ex the lock-screen - if i try yo drag the slider half-way and hold it there, it won't hold, but snaps back. If I slide quickly, I can unlock the phone, so it seems that the problem is to register touches lasting longer than 1/2 sec. or so..
Is this most likely a HW or SW problem?
I watched your video, and yes I had this problem also. Trying to unlock the phone resulted in it resetting input and being an incorrect pattern. Can you do something for me? Download mutlitouch tester (visualizer) and just hold your fingers on there, normally what it should do is stay solid, but with if your problem is the same as mine. It will blink rapidly. Mine was also periodically, the issue appeared to be with the Email and other email clients based of the stock one (not gmail or k9mail) client, so try removing all accounts on there if any. But the cause behind this was the fact that the garbage collector was running every second and it seemed to free up the memory used by the input driver. If this doesn't work, try a different ROM, like B137, or MIUI (I am using this, its great).
and most of all, let me know how you get on.
Feel free to email at [email protected].
Thanks for your reply ryronz, I'll try the multi-touch-tester next time it acts up, for now it's fixed itself again.
Are you positive it's linked to email-accounts, because I actually did just link up my exchange-account..! Could you explain this about the garbage-collector a little bit closer? Are there any settings in the exchange-account I can change to remedy the problem?
toth42 said:
Thanks for your reply ryronz, I'll try the multi-touch-tester next time it acts up, for now it's fixed itself again.
Are you positive it's linked to email-accounts, because I actually did just link up my exchange-account..! Could you explain this about the garbage-collector a little bit closer? Are there any settings in the exchange-account I can change to remedy the problem?
Click to expand...
Click to collapse
Exchange! Yup, thats when it started happening to me, and no I never found a way to solve the garbage collector thing. Its just something that happens whenever the phone feels it needs to run, there is nothing you can do to make it happen or not happen. I ended up removing the email client and using K9Mail.
Even if I don't like the answer, it's always good getting closer to the problem, so thanks
By the way I actually did an official FW-update from Huawei, and had the same problem both before and after.
So what is this garbage-collection? What kind of garbage are we talking about?
toth42 said:
Even if I don't like the answer, it's always good getting closer to the problem, so thanks
By the way I actually did an official FW-update from Huawei, and had the same problem both before and after.
So what is this garbage-collection? What kind of garbage are we talking about?
Click to expand...
Click to collapse
What the garbage collector does is when unused memory is still allocated, it will come and clear it automatically. This should only happen when the memory is used up, or near used up. But in saying that even though it is running all the time, the input driver memory should not be getting garbage collected. So my guess is its another poorly written driving from Huawei.
I have the same problem here. However I have not, up till now, been able to identify what caused the lagging (and battery drainage?).
For testing purposes, I have today deactivated the current exchange account setup, and installed another email client (Touchdown). With the new client running, the lagging was gone.
After that, I have removed Touchdown and reactivated my old account setup.
A search on Google indicates that there might be some issues with Android and the use of Exchange email....
As a new test, I have now changed the sync periode from one hour to 'push'. I found that suggestion somewhere in my search for a solution.
Maybe it is to early to conclude, but as far as I can see after a few hours with the phone mostly in standby, I can spot some improvements with regards to both the lagging and battery drainage.
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