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.
I've installed on a friends HD2 one of the WinMo 6.5 ROMs, as they're all better than the stock firmware.
This was around a year ago.
A few months ago he told me he's having problems accessing the net, and that the phone locks up every time.
So I've set up a Skype conversation and wanted to walk him through installing a new firmware (at the moment he wanted to try out WP7). I didn't think it's anything serious; WinMo tends to go a little wonky every once in a while.
So I walk him through the typical steps: Task29 + radio, MAGLDR. All this works fine. Then we proceed to install one of the many WP7 roms (to make sure it's a decent rom I tried it first on my own HD2; it was working fine). However, MAGLDR locked up when preparing and clearing the partitions for the system. I've walked him through the procedure a few more times (thinking he might be doing something wrong or it was a one time fluke; we are still talking via Skype, remember), but it was always the same.
I've then tried to walk him through Android installation, but the process, once more, halted when installing Clockwork Recovery (once more, clearing and preparing partitions).
Finally, with no more ideas, I did the SD card trick to reinstall the original OS. That worked fine, but at the end he said the phone still locked up.
Yesterday he came to visit me, and brought the phone with him. I attempted to install Android, and indeed... the furthest I was able to get was the GO GO GO screen when launching AD recovery, at which point the phone locked up. Earlier, it would lock up on the countdown (123456) throwing errors. I must mention that I was able to install Clockwork, but it took far more time than it should when preparing the partitions.
At one point, when redoing the whole thing over (Task29, radio) the phone vibrated 7 times and refused to cooperate when installing the radio.
At this point, after reading some posts, I decided to give the old freezer a try and... put the phone in the freezer for about 30 minutes.
It came out nice and cold, and to my surprise, I was able to install Clockwork, run it, install Android... and it's still working.
It's definitely warmed up since I took it out, and has been working all night (albeit with no SIM card). I was able to reboot it, enter AD Recovery, and all in all, it seemed rather stable. But if it's just a temporary thing, then my friend is more willing to buy a new phone rather than keep on fighting with this one (and since the phone is way past it's warranty, there's little point in taking it for repairs).
With all that said, what's the chance that the phone will now function properly? Could the freezer trick actually FIX the phone, rather than temporarily mask some underlying hardware issue?
the freezer trick is more of a fast solution, but it won't fix the problem.. there's a thread about how to solve this:
http://forum.xda-developers.com/showthread.php?t=982454
I don't have overheating problems so I didn't bother trying it.
The freezer trick will only serve as an indicator that your phone is suffering from the thermal issues that are being addressed in the link that Dr.Move posted. I had another HD2 that wouldn't get past MAGLDR unless it was cold. Even then once it got warm it would shut off.
I have similiar problems with Shaamaan and I have another HD2, which works flawlessly and doesnt get stuck
while it might be either BAD BLOCKS, or the THERMAL problems as posted above, I am half tempted to put it into the freezer
I have warranty though, which I should probably warranty it before doign anything silly
Sorry for the late reply.
The thing is, after going through the freezer, the phone is now running smooth. Again, I don't have a SIM card for it (it's T-Mobile locked), but other than that, I was playing with it using my home WiFI and it didn't lock once. I've also rebooted it a number of time, entering the AD recovery mode without a problem.
I've taken a quick glance at the thread linked Dr.Move and... whoa, that looks scary. It's not even my phone, and I still wouldn't feel comfortable doing that. There's a certain level of finesse required with electronic devices of this kind; I can take a computer apart, but this?
Anyway, seems like I need to put a bit more stress on the phone. Any suggestions? Would running some of those Android performance tools be enough? Or do I specifically need a CPU stress testing tool like the one mentioned in that scary thread?
EDIT: I've found some stress tool on the store, and it's been running for 15 minutes now, reaching a temperature of 34 degrees and seems to stay there.
try to run games or stress tools while charging, this will heat it to over 40 Celsius, I got it over 42 before with no problems, but be cautious.
currently facing this issue as well
wonder if anyone else tried this and it worked, and what tips / concerns can be shared
Is it still fixed???
For awhile now, my Droid 2 has been slow - slow to launch applications, slow to respond to touch, etc. I cannot attribute it to any newly installed application. Updates, maybe, but I'd have no idea which. I had it rooted with Z4Root, but then Verizon pushed out 2.3 and the phone became so slow that it is totally unreliable. I'll receive phone calls and 25% of the time the call will go to voice mail before I can get the phone to respond. I'll try to make a call and it may be 30 or more seconds between initiating the call to when the dialer appears and dials. Data speeds are slow.
At times the phone seems to operate at almost normal speeds and then it gets slow again. I've removed root access and uninstalled applications that require root access. I've also removed many other applications that I just don't need or use.
On my SD card it says I have 6.11GB free (out of 14.83 total). For "Application Storage" it says I have 5.63 Available Space.
I can't figure out what's wrong. Are there any suggestions short of resetting the phone to factory defaults and staring over?
Thanks,
Andrew
This has happened to my phone before also (droid2 rooted stock rom).
What i did to fix the situation, was the only thing i could think of.
I just did a factory reset to froyo and my phone was fast again.
Just back up all you apps and do a factory reset, its your only real option far as i can tell.
You could try installing something like 3g watchdog to monitor your apps and see if maybe 1 of them is eating up your phones processor.
Good luck.
Far as i can tell these phones are not much different from a home pc, in that they acquire so much extra pointless bull**** during their use that it just clogs the system. Forcing a reinstall just like a home pc.
Once they are reset back to factory, their performance returns to normal along with battery life.
Just be careful not to keep putting useless apps you dont even use onto your phone, just the apps that are absolutely necessary.
Keeping to this formula keeps my phone in tip top shape, short of changing roms or major tweaking.
Sigh I guess I'll need to try the reset.
I do have Watchdog installed and the last reported 'incident' was three days ago. No help there.
Everything is backed up, so here it goes... (I'll post back once I recover.)
Sent from my DROID2 using XDA App
I am having the same issues. I have an R2D2 stock, never rooted. Since the Gingerbread update, it has been flaky and getting worse. It is rebooting several times a day. I miss calls because the screen won't respond. Sometimes the hard keyboard won't respond and I have to manually reboot the phone to get the keyboard back. At least once, the soft keyboard wouldn't work either. I am hating Gingerbread but am at a loss on how to remove it. I'll be watching for your updates.
The gingerbread update has been reported to have several annoying as hell bugs, i never installed it for that reason alone. Besides i don't feel like loosing the ability to tether wireless, just to upgrade to a buggy version of android. Ill wait for ice cream to hit then maybe upgrade if i see something worth upgrading for. Till then its froyo, maybe try cyanogen mod 7.1
Far as going back to froyo from gingerbread, i know its been done and is fairly easy to do. Not sure how much different it is from a factory reset.
I've had a pretty good experience with my E900 and updated to Mango as soon as possible. I loved Mango, had some problems with networks, but got it working. Then a few months later I started to run into some issues. The phone is a year old, so it may be hardware. Or it may be software. Overall, the case itself is in pretty good condition, so I don't feel like it's damaged per se. I did perform some update just before all of this started, so I'm thinking there may be a software issue.
Here's what's going on:
About a month ago, the phone died on an international flight. As it had before, it showed the 'connect to a computer' icon on boot-up. This time, however, it would not communicate with the computer. After two days, I figured out how to hard boot, and got it moving. The only problem was that the camera wasn't working. No big deal I guess.
Then the next time the battery died, I had to repeat the process. And the battery started dying frequently because the camera started taking hundreds of photos an hour on it's own.
I have been able to start the phone from a dead battery a few times without cold booting and even got brave enough to try and succeed at updating to Mango.
The problem, however, is now back and I'm having to constantly keep my phone in (see camera issue--meaning sometimes as little as two hours of 'standby' time, especially when it starts shooting video) and cold booting my phone several times a week.
1.) Is this possibly due to a hardware issue--like is there some sort of core battery like on a CPU that might need replacing?
or
2.) Is there a firmware update I might be missing?
or
3.) Is there a way in the Engineer Menu to turn off the camera so at least I have a fighting change. The camera button works fine when I have to cold boot (thankfully) I've checked the key extensively, so I don't think it's a hardware issue.
Thank you!
Cloud you give to us your frimware infos.
Maybe you've just got an issue with an old version of the firmware.
The last one is : 1.1.4.10
If you haven't the latest one, try to do an update it may works.
If the update do not deploy to you a frimware update try to find a way to flash your device.