My Desire HDs cpu is always at 99%. I downloaded watchtower and saw that Settings Storage was using between 50% and 75% and htc sense normally around 20%. I've already tried a factory reset which worked for a few days then the problem just came back today.
Went into running services and stopped the 'Immediate Mode Service' under HTC Sense. This seems to solve the problem temporarily but if the phone is restarted the problem comes back. What is this Settings Storage process and how do i find a permanent solution??
Any help greatly appreciated!
listnc said:
My Desire HDs cpu is always at 99%. I downloaded watchtower and saw that Settings Storage was using between 50% and 75% and htc sense normally around 20%. I've already tried a factory reset which worked for a few days then the problem just came back today.
Went into running services and stopped the 'Immediate Mode Service' under HTC Sense. This seems to solve the problem temporarily but if the phone is restarted the problem comes back. What is this Settings Storage process and how do i find a permanent solution??
Any help greatly appreciated!
Click to expand...
Click to collapse
That happens when you upgraded to Android 2.2.1
It's a known issue and HTC put down the update, so their fixing this.
Did you try enabling USB debugging? If not go to Settings -> Development and then tick the USB Debugging box.
If you are syncing with HTC Sense, remove the account from sync and reboot
Should go back to normal.
I ended up resetting to factory before I found other people on here with this issue (my Google & search skills suck)
It munched my battery in 4 hours before I fixed it
Well I thought I was the only one...
Guess that means there will be another update sometime soon. Regarding the HTC Sense sync thing I turned it off ages ago as it kept on updating and since mine doesn't even work I don't really think I need it on!
Again... did you try USB debugging?
I had USB debugging enabled anyway. Deleting the HTC Sense account seems to have fixed the problem anyway. Thanks for the info Homerr.
This happened to me yesterday...couldn't find a solution online so I reformatted - good excuse to install the latest version of the Android Reovlution HD ROM
Homerr said:
If you are syncing with HTC Sense, remove the account from sync and reboot
Should go back to normal.
I ended up resetting to factory before I found other people on here with this issue (my Google & search skills suck)
It munched my battery in 4 hours before I fixed it
Click to expand...
Click to collapse
Thanks so much. Been searching around for ages to find a fix.
Android system was showing ~70-80% CPU usage and HTC Sense ~20%. Removed my sense account on my DHD and rebooted now Android System showing <10% CPU. Will have to wait and see what impact it has on battery life.
USB debugging seems to be a fix for the /init process consuming masses of CPU. didn't haven any effect on my problem. Seems my problem was HTC Sense.
I have the same problem.
CPU is always at 99%.
According to Watchtower, "Settings Storage" / "system_server" is using around 75~85%.
I have USB debugging ON, and I do not have HTC Sense sync on. Never have.
Restarting the phone seems to fix it for a while, but it inevitably just comes back.
Any ideas?
Running Android Revolution HD 3.1.
happened at revolution roms
never ever happened on vanillain rom 1.6 (for DHD)
best regards (USB Debugging never ever changed anything with this problem, I'm a dev, so its always on anyways )
change: happened today also vanillain rom 1.6.1 :=((
Yeah, I know the debugging thing was a fix for the INIT problem, not this, but I felt I'd mention it anyway.
It seems most people resolved this problem by disabling sense sync, but since I don't have that turned on to begin with, I am not sure what I should do...
I've only had the phone for a few days now, but so far I have had to restart it on a daily basis to keep it running snappy.
Sent from my Desire HD using XDA App
:=)
shiftis said:
but since I don't have that turned on to begin with, I am not sure what I should do...
Click to expand...
Click to collapse
don't really understand this sentance... ?
u don't want to turn it on? why? <- correct?
best regards,
I am referring to having an HTC Sense account set to sync in the "accounts and sync" settings.
People say they resolved the 99% load issue by disabling syncing of their sense account, but since I already have it disabled and am still experiencing the problem, that solution doesn't work for me.
Sent from my Desire HD using XDA App
okay...
thanks for explaining!
I just don't want to disable it, because that's one reason why i got such a phone
I'm sry to say, i cannot help you :=(
(but i suffer form the same problem (((( )
best regards,
mike
I've exactly the same problem since some days... The ImmediateModeService will let the Android System process use 100% of CPU.
same problem with ImmediateModeService; but If I delete HTC Sense synchronisation it solve also the problem... The 99% is also present if the automatic synchronisation is of... you have to disable HTC Sense
Ever since upgrading from Android Revolution 3.1 to 3.2, the 99% CPU problem has gone away.
Related
Hi All,
I have just bought this device yesterday, I was previously using an HTC HD2.
The device is great so far, but one major issue is when it is connected via USB and Internet Sharing is Selected, the device reboots itself after 2-10 minutes.
The battery is fully charged, and I have restored device to default settings with no apps etc..
It has original firmware 2.1.
Anyone else getting this issue? I can take it back to store, but I wanted to check if it is a setting that I need to change.
Thanks in Advance.
____________________________________________________________________________________________________________________________________
Solved it ** Phew **
Talking SOLVED
HI All,
I just figured out the answer to my own problem. The the phyone doesn't reboot when just browsing, its when torrents are active on my laptop is when it crashes.
So I reduced the number or Conccurrent Connections for My client down to 5 downloads and 5 upload and no more problem.
It looks like the torrents 100's of concurrent connections were overloading the Handsets NAT Buffer and causing the OS to crash because it couldn't monitor the internal/external IP mapping for all connections.
Phew.. Device isn't fault !!
I have been testing for 30 minutes now and no issue, before it would crash in 2 minutes.
_EDIT******______________________________________________________________
I spoke too soon, although it lasted about 1 hour this time, it still crashed.
It looks like im not the only one either, It seems to be an issue with the stock asian ROMS.
I am currently testing with PDANet and it has been working fine for 20 minutes, but I will update in a few hours.
That should not happen. You will not need to apply any settings other than the ones in which you require to establish the connection and make it work.
Have you performed a factory reset to eliminate any software bugs?
MasDroid said:
That should not happen. You will not need to apply any settings other than the ones in which you require to establish the connection and make it work.
Have you performed a factory reset to eliminate any software bugs?
Click to expand...
Click to collapse
Hi,
Yes I have performed a factory reset of device, and it still does the same. But it doesn't reboot any other time, Only when running internet sharing.
Im stumped.
wickedpenguin said:
Hi,
Yes I have performed a factory reset of device, and it still does the same. But it doesn't reboot any other time, Only when running internet sharing.
Im stumped.
Click to expand...
Click to collapse
I would get it replaced then. You have not rooted it and it is running the stock rom so it should not be a problem to have it replaced as it is still under warranty. Just explain the problem you are facing and they should replace it without any fuss. Is the device completely brand new? I mean, could you tell whether it has been opened/used when you received it?
MasDroid said:
I would get it replaced then. You have not rooted it and it is running the stock rom so it should not be a problem to have it replaced as it is still under warranty. Just explain the problem you are facing and they should replace it without any fuss. Is the device completely brand new? I mean, could you tell whether it has been opened/used when you received it?
Click to expand...
Click to collapse
Yes, I just bought it yesterday. I just called and they are happy to swap for another new one, But the store is a bit of a drive and its a bit frustrating as everyone other part of the phone works great.
It was totally brand new when I bought it , sealed in box with the plastic seciruty covers still on device.
wickedpenguin said:
Yes, I just bought it yesterday. I just called and they are happy to swap for another new one, But the store is a bit of a drive and its a bit frustrating as everyone other part of the phone works great.
It was totally brand new when I bought it , sealed in box with the plastic seciruty covers still on device.
Click to expand...
Click to collapse
Maybe try swapping with another sd card. Also, it could be down to overheating. Does the battery get hot after 10 mins when it reboots itself? The battery could cause these reboots because as it may not produce enough power / ampere in that moment so that the device reboots. I don't suppose you have another battery to try?
SOLVED
HI All,
I just figured out the answer to my own problem. The the phyone doesn't reboot when just browsing, its when torrents are active on my laptop is when it crashes.
So I reduced the number or Conccurrent Connections for My client down to 5 downloads and 5 upload and no more problem.
It looks like the torrents 100's of concurrent connections were overloading the Handsets NAT Buffer and causing the OS to crash because it couldn't monitor the internal/external IP mapping for all connections.
Phew.. Device isn't fault !!
I have been testing for 30 minutes now and no issue, before it would crash in 2 minutes.
I'm having the same problem n still on stock asian rom. e issue is that i wasn't using any torrent but concurrently downloading several files in firefox.
stan79 said:
I'm having the same problem n still on stock asian rom. e issue is that i wasn't using any torrent but concurrently downloading several files in firefox.
Click to expand...
Click to collapse
that's exactly the same problem i'm facing. asian rom as well.
problem persists even after returning / exchanging my handset.
Guys try using pdanet for tether n c if problem still occurs
Sent from my HTC Desire
stan79 said:
I'm having the same problem n still on stock asian rom. e issue is that i wasn't using any torrent but concurrently downloading several files in firefox.
Click to expand...
Click to collapse
I am also using an Asian Rom, From Hong Kong.
Seems to be any load on the device overloads the NAT buffers and causes the os to crash.
I wil try PDA net today and see if the same problem occurs.
PDANET Test
pisonic said:
Guys try using pdanet for tether n c if problem still occurs
Sent from my HTC Desire
Click to expand...
Click to collapse
I have just installed PDA net on my device and I'm downloading some torrents at 500kb's per second with no limit on concurrent connections. Been 10 minutes so far.
I will keep you updated!!!! Fingers Crossed.
Really Solved this time
PDA Net did the trick
It looks like there is definately a bug with the native internet sharing software for Asian 2.1 Rom.
I have been running PDAnet under High load for the last one hour and thirty minutes and no reboots.
I did get a USB error that popped up briefly from the PDA software, but I think that was because I picked up the device to check the heat. ( Temp is Warm, but definately not hot.
3 hours now and no issues. I have written a letter to HTC, but lets hope that the 2.2 is the fix all that they all think is going to be.
I'm curious if others are seeing their EVO reboot with random use. It doesn't seem to be related to one specific application although it is hard to say if a background app is the cause. I will be using navigation or an Internet-based app, then the screen goes black and the phone reboots.
I originally thought it was due to rooting, but I'm seeing it on different ROMs. I've wiped the cache and data when flashing the new ROMs and I've tried running with limited apps loaded with my recent move to the OMJ ROM. Everything actually runs great with the exception of the reboots.
I'm posting the issue here since it doesn't seem to be ROM specific and I'm curious if it may be hardware related. Is there a tool that would allow me to easily catch a log of the potential error to seek further help? A point in the right direction would be greatly appreciated.
I'm running stock 2.2 no root, and with gps on my phone reboots in the middle of 911 calls. (Thank God I wasn't calling about an immediate emergency) but it happened twice, once when I called and the other when they called me back. After turning off GPS, it worked fine. I thought this was a bug in 2.1 before update1, I didn't receive the problem until the 2.2 update.
adb logcat might see an error, but I'm not really sure.
Seeing it here. Not Rom or application specific.
try a factory reset.
That's scary news about the reboots during 911 calls. I can't say that I tested that as a trigger for the reboot and I hope I don't have to in the near future. However, it makes me curious if it is related to the phone's interaction with the Sprint network. In your case your 911 call may have been a direct trigger whereas my reboots are seem indirect while I'm using my data plan.
One reason for my reboot was due to me getting the Error Code 67 "Your PCS Vision username and/or password may be incorrect" when trying to tether (USB or hotspot). Rooting allowed me to tether using 3rd party apps, but there may be the underlying problem with my account.
I also should have mentioned that the reboots happen with GPS on as well as off. I typically have it off to save battery life. I've also done factory resets each time I've changed or updated my ROM.
Thanks for the feedback and suggestions so far. I'll try logcat and continue to monitor the forum for advice. I'll also post back any answers I may find elsewhere.
Thanks again.
I had a reboot tonite, phone was just sitting on table off charger about 90% battery, and I heard the Sprint screen come on looked down and noticed phone was booting up....no idea why first time I've noticed this.
Stock froyo no root...unfortunately :'(
AzmatEQ said:
That's scary news about the reboots during 911 calls. I can't say that I tested that as a trigger for the reboot and I hope I don't have to in the near future. However, it makes me curious if it is related to the phone's interaction with the Sprint network. In your case your 911 call may have been a direct trigger whereas my reboots are seem indirect while I'm using my data plan.
One reason for my reboot was due to me getting the Error Code 67 "Your PCS Vision username and/or password may be incorrect" when trying to tether (USB or hotspot). Rooting allowed me to tether using 3rd party apps, but there may be the underlying problem with my account.
I also should have mentioned that the reboots happen with GPS on as well as off. I typically have it off to save battery life. I've also done factory resets each time I've changed or updated my ROM.
Thanks for the feedback and suggestions so far. I'll try logcat and continue to monitor the forum for advice. I'll also post back any answers I may find elsewhere.
Thanks again.
Click to expand...
Click to collapse
Correction... I meant to say that the reason I rooted (not rebooted) was to get tethering without running into the Error Code 67. I tried the various solutions posted for the Error Code 67, but nothing seemed to work. But I'm curious if this may be part of the underlying issue if my device reboots based on a faulty account configuration when using some aspect of the Sprint network.
sprink0281 said:
I had a reboot tonite, phone was just sitting on table off charger about 90% battery, and I heard the Sprint screen come on looked down and noticed phone was booting up....no idea why first time I've noticed this.
Stock froyo no root...unfortunately :'(
Click to expand...
Click to collapse
The exact same thing happened to me last night. I sent a text, switched to my GMail and then boom. Error message about failure to send an SMS then reboot. Stock unrooted FroYo.
I had reboots only when using Undervolted kernels.
Seemed to be triggered by GPS + Phone call.
Yes, I was also having this problem. Definitely GPS related. Usually it would happen only if I was using the GPS for a long amount of time (navigating) - so I imagine it may be conflicting with cellular data if I received a txt while navigating or something. Who knows.
It was driving me crazy because A. I got lost and B. It started rebooting constantly and would randomly get caught in a boot-loop. I even had the problem after wiping EVERYTHING (even my SD) and reinstalling various ROMs (I tried 5 different ones).
The only solution I found in the end was to find the latest radio and wimax updates, wipe, re-install those - and then install the ROM again.
GPS may be a symptom, but not a cause for me since I typically have GPS off. I find that it typically happens when I'm using a networked based app, like the web browser. Following your post I turned on the GPS, started the navigation app and found that my EVO rebooted after the same amount of time I was experiencing with GPS off.
The more I think about it, it does feel like I just assume that it will reboot after a certain amount of time passes (regardless of app). GPS and Internet are two uses where I will have the screen on for more than just checking email and etc.
Your reply gave me hope and I wiped, reset and reinstalled today. All seemed well and then... auto-reboot. This is driving me nuts. I'm seriously considering reverting back to stock to see if that stops it.
AzmatEQ said:
GPS may be a symptom, but not a cause for me since I typically have GPS off. I find that it typically happens when I'm using a networked based app, like the web browser. Following your post I turned on the GPS, started the navigation app and found that my EVO rebooted after the same amount of time I was experiencing with GPS off.
The more I think about it, it does feel like I just assume that it will reboot after a certain amount of time passes (regardless of app). GPS and Internet are two uses where I will have the screen on for more than just checking email and etc.
Your reply gave me hope and I wiped, reset and reinstalled today. All seemed well and then... auto-reboot. This is driving me nuts. I'm seriously considering reverting back to stock to see if that stops it.
Click to expand...
Click to collapse
Don't go back to stock. I did and it did not fix the rebooting problem. Now I have the rebooting problem and don't have root anymore. Out of the frying can and into the fire.
What's funny is that my phone went through a few days where it would randomly reboot, and this was before I rooted. When it rebooted for the second time in a meeting, I pulled the battery, and didn't put it back in until the meeting was over a few hours later. Don't know if that did anything, but it hasn't rebooted on its own since.
Sent from my blah blah blah blah
Having same issue and my theory is that its sd card related in my case at least... I think it might have to do with froyo netarchy based kernals found in most of the newer froyo roms combined with a slow sd card. (on hardware rev 2)... try flashing a 2.1 rom like fresh 1 or one of the 2.2 roms with an htc based kernal like the am evolution or cyanogen with snap5 or 7.11 (onyl 7based kernal ive tried so far, was panicking because i thought my evo was wrecked). those have both worked for me and i had that issue with 1.3 baked snack, fresh 3, evio and damage control. got random reboots when phone is totally idle, in use, charging or not. evio runs super smooth but the restarts...)
edit for spelling and update roms that gave me the reboot issue.
+1 for random reboots here... it is CERTAINLY more prevalent during GPS use, but I've gotten it without.
Fresh 3 + King BFS#4 got me in a bootloop requiring wipe reflash, standard baked snack 1.5+whatever kernel it comes with has been doing it.
I dig the battery life I was getting... but if undervolting is causing this... ugh.
I'm also getting the boot loop problem. Stock 2.2, all updates.
I've even done the hard reset.. twice!
I tried to follow it with LogCat, but reboot disconnects adb. I was thinking it was the SprintZone app. The P.O.S. app is doing all sorts of non-sense while booting, but eventually it'll reboot around the 11th time and freeze at the "htc EVO 4G" screen.
I wish we could get some resolve here D;
Random Reboots
Thanks for all the input and I'm sorry to hear that I'm not alone, but it is a bit comforting to know I'm not the only one that is frustrated.
I took gleax's advice and I dropped down to the stock 2.1 release found in the thread number 715915. (Sorry, the forum won't let me paste the link.)
I did the required wipes prior to installing the new ROM and I'm still seeing reboots. I now see the OTA update for Android 2.2 and I'm tempted to accept, then send the phone back to Sprint in the even this is a hardware issue. I'd prefer not to, but there doesn't seem to be a way to identify the issue and work towards a resolution. I've tried logcat, but the log seems to start clean after each reboot. That being the case, I don't know how to capture the log leading up to the reboot that would help identify the issue. Any suggestions on a logging tool and where to post to help several of us that are seeing this issue?
Gleax suggested this is may be SD related, so I bought a class 4 card in addition to dropping down to 2.1. I'll give that a shot and try another clean 2.1 install. I'll post the results here in the event they may help others. I'll likely give it a week before unrooting and seeking help from Sprint. I really need a usable device more than I need root access (although both would be ideal).
I had this problem on a very regular basis when I was running OTA 1.32, 2.1 android.. but since I rooted and went to SteelH's stock 2.2, no issues at all. Updated radios when I did that as well.
Hrm, I may have to try flashing to a stock build for awhile... it'll KILL me, but even fully wiping, new radios, cyanogen, still get crazy reboots.
When I set my Date & Time to Automatic from the network provider, it seems to jump ahead by 10 mins every now and again.
If I uncheck the the Automatic option and the recheck it, the time corrects itself but will them jump by 10 mins after a while.
I have only noticed this since upgrading to 2.3.3.
I am on the Orange network and have an unbranded handset.
Has anyone else noticed this issue? I'm not sure if it is network or 2.3.3 related so would appreciate any info from
It will fix itself eventually. I fixed it by having the wifi on for a while. Turning it off, waiting and then turning it back on again. Seems like a local server issue so just wait it out and keep it connected to wifi for a while and see what happens.
RED_ said:
It will fix itself eventually. I fixed it by having the wifi on for a while. Turning it off, waiting and then turning it back on again. Seems like a local server issue so just wait it out and keep it connected to wifi for a while and see what happens.
Click to expand...
Click to collapse
I will give it a try. I usually have my wifi on all the time when i am in the house. I'll monitor it over the next few days and see how it goes.
I have had the same problem since the gingerbread update on my Vodafone Desire HD. I have Wi-fi on all day at home and work and only thing that corrects the time is turning the automatic setting off and on again. Definitely a bug in there somewhere.
tiger zero said:
I have had the same problem since the gingerbread update on my Vodafone Desire HD. I have Wi-fi on all day at home and work and only thing that corrects the time is turning the automatic setting off and on again. Definitely a bug in there somewhere.
Click to expand...
Click to collapse
That's good to know. Looks like it may not be a network issue then.
Do you have an unbranded handset?
Same here in Australia, but only started to happen last night. I can trigger it by going to the weather app and manually updating the weather. Updating again restores the time to normal.
I have sent a email off to HTC about the issue. Lets see what they say about it.
They seem to be quite active on Facebook these days so I think I'll leave a comment on their page also.
Hopefully will get a reply soon to say it's a bug or that they are investigating it. With past experience in contacting their customer service dept, I'm not holding my breath.
OK people it looks like it's a known issue and HTC are currently working on it. They sent me the following reply on Facebook :
Hi scotia_rfc, it's not an issue caused by the Gingerbread update, we've seen that some handsets are showing the time 10 minutes ahead. We would like to reassure you that we are currently working to rectify this and will have an update for you shortly. We apologise for any inconvenience that this may be causing.
Click to expand...
Click to collapse
I haven't had this issue. My phone alarm is what gets me up for work, so that would be a big problem.
I have had the same issue since updating to 2.3.3
Definitely seems like it is update related to me - I have a couple of phones synced to an Exchange server so I would have noticed before the update if the clocks were out of sync by 10 minutes as the alarms and reminders would have been going off at different times on the two phones, but since I updated yesterday they go off at different times. If you turn off the automatic update, correct the time and re-enable automatic update then it will sometimes roll on an extra 10 minutes within a few minutes. Seems to roll on more rapidly when moving about so perhaps related to cellular location updates?
Phones are HTC Incredible S (unbranded, s710e from Taiwan), Nokia E5 (not my choice - work phone!)
This may be just a little problem waiting for a fix. I only noticed today that it shows me weird time, but it was automatically updated after a few minutes.
scotia_rfc said:
When I set my Date & Time to Automatic from the network provider, it seems to jump ahead by 10 mins every now and again.
If I uncheck the the Automatic option and the recheck it, the time corrects itself but will them jump by 10 mins after a while.
I have only noticed this since upgrading to 2.3.3.
I am on the Orange network and have an unbranded handset.
Has anyone else noticed this issue? I'm not sure if it is network or 2.3.3 related so would appreciate any info from
Click to expand...
Click to collapse
Same here and I'm on o2-UK. I have also found by having WiFi on it corrects itself but surely there is a proper fix ?
Sent from my Desire HD using XDA App
If your rooted I'd recommend ClockSync. It works wonders for me. Keeps my time synced with 0.uk.pool.npt.org . You can use any timeserver local to you using http://www.pool.ntp.org/ . Be sure to turn off Automatic in "Time & Date".
Same problem here: Vodafone RO, unbranded DHD on stock 2.3. Strange thing though is that I've only noticed it after rooting my phone a couple of days ago. I don't remember having this issue before rooting.
I found this today! Thought I was going to be late but turned out I was on time but my time was over 20 min ahead of it's self!!!
Un-checking and then checking the automatic time update sorted it out
Global NTP servers are out of sync, so HTC cannot fix that. It will get fixed in no time.
Sent from my Desire HD using Tapatalk
Same, but worse
I have the same issue, so deactivate the automatic update.
But since I upgraded to 2.3.3, I loose both Wifi and phone networks (3G/edge/simple phone) if the device has not been used for about 2 hours. I must switch off "Data" and "Wifi", and switch on again.
Has anyone the same problem ?
jkoljo said:
Global NTP servers are out of sync, so HTC cannot fix that. It will get fixed in no time.
Sent from my Desire HD using Tapatalk
Click to expand...
Click to collapse
Hm. Then why does unticking and reticking the automatic sync fix this problem? I mean, it always gets the time right when doing this, doesn't it mean the servers are fine?
I think i had this problem before i updated.
NOw it asks if i want to automatically update time everytime i reboot
I posted this in NilsP's Business GingerSense thread, but don't think it's a ROM issue, more of a Google Talk issue. Running the 2.0 version of that ROM.
The issue is where Google Talk shows all your contacts as Offline after a period of say five to ten minutes, maybe shorter than that. I'll be messaging someone, and after a few minutes when they haven't responded, I'll wake my phone and open GT. All the contacts are Offline. A simple sign out/sign in fixes that, and the usual contacts show Online or Away.I've noticed this all week, so I'm thinking it's a GT issue, but I've never had it happen before.
Don't want to have to sign out/in every time I want to use it. Cleared GT cache, fix permissions, multiple wipes of data/system/cache/boot/dalvik/user data before each ROM install, and haven't had this before now.
Thoughts?
EDIT: After playing, it happens when switching from 3G to WiFi and vice versa, so maybe it is a ROM thing...?
i'm having the same issue. noticed after my gingerbread OTA update from verizon.
Droid 2.
It seems to happen a few minutes after logging on.
I also have that issue with Gtalk. After some time all contacts appear to be offline, but only when I'm on data connection and not on wifi.
There is still no solution for this?
Cheers!
carapauzinho said:
I also have that issue with Gtalk. After some time all contacts appear to be offline, but only when I'm on data connection and not on wifi.
There is still no solution for this?
Cheers!
Click to expand...
Click to collapse
Me too. Anyone was able to do something?
Well I've since moved on, and haven't noticed it on other ROMs. Right now I just tested toggling Wifi on and off, and the contacts would appear offline, then come online once 3g or wifi connected.
I'm thinking in my case, it was that version of the ROM I was running at the time.
Sent from my ADR6300 using xda premium
Just a thought, check any task killers / managers and make sure talk is unchecked. I had the same problem a long time ago and ATK was the culprit. Haven't had the issue since and I have used almost every Rom possible at one point or another
Sent from my Incredible Stock+v2.6 Ginger Tiny
dragon droid said:
Just a thought, check any task killers / managers and make sure talk is unchecked. I had the same problem a long time ago and ATK was the culprit. Haven't had the issue since and I have used almost every Rom possible at one point or another
Sent from my Incredible Stock+v2.6 Ginger Tiny
Click to expand...
Click to collapse
True. Right after I rooted over a year ago, I had an issue with the alarm clock not going off intermittantly, and coincidentally I was using ATK at the time. After reading that ATK could be the issue, uninstalling it fixed the issue. Since then, I don't actively kill tasks, but I do have System Panel installed just in case.
I'm running Stock+ v2.6, and since moving on from v2.0 of NilsP's ROM where I had the initial issue, I haven't noticed/had the problem.
RMarkwald said:
True. Right after I rooted over a year ago, I had an issue with the alarm clock not going off intermittantly, and coincidentally I was using ATK at the time. After reading that ATK could be the issue, uninstalling it fixed the issue. Since then, I don't actively kill tasks, but I do have System Panel installed just in case.
I'm running Stock+ v2.6, and since moving on from v2.0 of NilsP's ROM where I had the initial issue, I haven't noticed/had the problem.
Click to expand...
Click to collapse
Hi,
Me and the other user are I9000 users. No task killers. We're trying to figure out if its a stock / custom ROM issue (since we're both using the same ROM), or some app forcing GTalk to sign out, or even a network problem (we both use the same mobile operator).
Thank you both for your input.
If you're on a stock ROM (you're both rooted right?), back up your ROM and flash another just to see if it happens in something different.
RMarkwald said:
If you're on a stock ROM (you're both rooted right?), back up your ROM and flash another just to see if it happens in something different.
Click to expand...
Click to collapse
Yes, we are.
The thing is that it seems to me that it happened only after XXVJR (meaning it happened to me in XXJVS and XXJVT, and now we're already at XWJVU, all these being Samsungs "leaks"), and I have a friend with XXJVS that works just fine.
I even tried flashing a stock ROM, to see if it happens again. Testing that one now.
Thanks for your advice.
Same problem here.
Although I have not tried it with stock non rooted phone...
I'm having the same problem on a stock rooted Motorola Photon. Very annoying to have to sign out and back in to see who's online. Hopefully someone comes to the rescue with a solution.
Hi,
The only thing I could find is that the problem is, indeed, NOT in the custom ROM's. It's google's problem.
The only way I could get by was with an alternative IM. And, for me, the better is Trillian (taking battery, performance, etc. in consideration.)
I updated my software which included an updated gtalk with video..so far so good.
crs77 said:
I updated my software which included an updated gtalk with video..so far so good.
Click to expand...
Click to collapse
Mine got better with one of those. But it ended up all the same.
DarkSorcerer said:
Me and the other user are I9000 users. No task killers. We're trying to figure out if its a stock / custom ROM issue (since we're both using the same ROM), or some app forcing GTalk to sign out, or even a network problem (we both use the same mobile operator).
Click to expand...
Click to collapse
I am having this issue too. I have had it since the beginning, when I had the preinstalled stock rom, I had it with all the other stock roms I flashed, I had it with all the versions of Talk I tried (those which supported video calls), I had it with all the other customs roms I tried (Simplicity, CyanogenMod, MIUI). I never used any task killer. For these reasons I am strongly convinced this is a Google Talk related bug.
Some more details about the problem:
after a few minutes after having logged in, contacts are shown offline on Android while they appear online on the desktop client;
despite their offline status I still receive messages from them and as soon as I answer only that contact appears online while the others keep being shown offline;
signing out and back in fixes the problem temporarily, but it happens again after a few minutes.
What surprises me is how come very few people seem noticing it or being annoyed by it? How come a huge bug like this has been out for so long and Google hasn't fixed it yet? All the posts I have seen reporting this problem on Google Talk Help Forum have been ignored.
Exact same problem with my I9100, Gtalk with video. Very annoying.
I have the SGS i777 (Samsung Galaxy S2 on AT&T), and just recently (since late February) started experiencing the same issue. When on WiFi, it doesn't appear to be an issue, only when not on WiFi, particularly if I have just recently turned off WiFi.
Other "friends" show me as "Away", so I am connected.
This is bone stock 2.3.6 Samsung official ROM (never rooted UCKK6).
I tried crawling a bit through the logs (aLogCat output), filtering for "[Tt]alk", but I can't make enough heads or tails about where the failure might be (not being an actual developer), other than lots of messages get created. I'll see if I can't figure something more useful out about it.
A hard reset with no apps installed has the same problem. Though I've noticed that the problem appears to get "worse" as the phone "ages" - namely, hard reset fixes the problem, but it slowly (over days) gets worse and worse.
Update: I have not noticed this issue at all since getting the official Samsung/AT&T ICS build (IML74K.CLE5).
Google Talk failing for toooo loooong
Hi there,
I'm a cyanogen 7.1 (stable) android user, and I just want to join myself to every other person who's affected by this issue.
I'll leave here some links to other places discussion exactly the same issue:
code.google.com/p/android/issues/detail?can=2&start=0&num=100&q=gtalk%20offline&colspec=ID%20Type%20Status%20Owner%20Summary%20Stars&groupby=&sort=&id=24242
You may check this thread: groups.google.com/a/googleproductforums.com/forum/#!topic/chat/6m0YqHoiIDg
Until now, I wasn't also able to find any clue to what the cause may be.
Starting to suspect that's something on Google's side, not android/rom itself.
Maybe something to do with our google accounts' settings?
Are there any news about this issue? I'm having the same problem.
Hello all,
Apologies if this has been covered elsewhere, I've searched but couldn't find anything.
I have an Xperia S on regardless of what ROM I'm running I always encounter a problem whilst browsing over mobile data. WiFi is fine.
After I've browsed for a while, I'll get a message saying 'Unable to connect to the proxy server' or similar depending on the browser. Switching to a different browser doesn't help and the only way I can restore mobile data is to reboot the handset.
I've tried stock ROMs, FXP and now I'm running Slimbean 4.2.2 Build 5 with Kernel 3.0.67-EOS+ and every time I have had the same problem. I had this problem out of the box. This is my second handset after my first developed the yellow screen fault, but my first handset also had this proxy problem.
Hopefully one of you helpful folk can point me in the direction of something that might fix this problem.
Thanks a lot,
Ewar
I had that problem only with 4.2 roms. CM10 and stock/stock based are all fine. The only thing I could do to fix the problem was airplane mode toggle. It's faster and uses less battery than restating the phone...
Sent from my LT26i using Tapatalk 4 Beta
stojshic said:
I had that problem only with 4.2 roms. CM10 and stock/stock based are all fine. The only thing I could do to fix the problem was airplane mode toggle. It's faster and uses less battery than restating the phone...
Sent from my LT26i using Tapatalk 4 Beta
Click to expand...
Click to collapse
Thanks for your quick reply and suggestion.
It's strange, but I've had the problem since I went from GB to ICS. I'm sure I've tried airplane mode back when it first happened, I've tried many things but the only thing that definitely works is a reboot.
It might just be me, but it seems like the speed at which the problem reoccurs is linked to the length of time the phone is in a shutdown state. If I do a reboot, the error will occur quicker than if I'd have shutdown the handset and left it for a few minutes before switching on. Of course, it could be a slow onset of insanity brought about by owning an Xperia S!
Ewar Woowar said:
Thanks for your quick reply and suggestion.
It's strange, but I've had the problem since I went from GB to ICS. I'm sure I've tried airplane mode back when it first happened, I've tried many things but the only thing that definitely works is a reboot.
It might just be me, but it seems like the speed at which the problem reoccurs is linked to the length of time the phone is in a shutdown state. If I do a reboot, the error will occur quicker than if I'd have shutdown the handset and left it for a few minutes before switching on. Of course, it could be a slow onset of insanity brought about by owning an Xperia S!
Click to expand...
Click to collapse
Quick Question : Is this only happening with the current service provider or every service provider?
I really think the problem maybe with the phone settings.
The service provider might be using a proxy channe.
Could you please try to edit the proxy data setting under the APN.
I hope this would solve the problem. I wonder how the proxy keeps popping out for you if the data works for sometime