Related
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.
Well, this is an odd issue and i'm sure many other have it because all of my friends with GS3's have this problem. I have a rogers GS3, my friend has a Telus and other videotron and multiple times a week, when we try to send a moderate or long sms (3 lines and more) the phones fails to send the message. This is very odd because i've tried everything from a factory reset, full odin wipe, different roms, and nothing works. I'm on CM10 M2 now and the problem is also there.
When i try to send a long sms, it fails, then i sent a short one right after, it works, then i copy and resetn the original one that failed and it faisl again. I pretty sure many of you have it because we have 3 different GS3 on 3 different networks and it happens to all of us
I tried looking around, i have not found much, maybe somebody has such problem and perhaps a solution?
This happened to me earlier this morning. No idea what can even cause an issue like this.
nobody??? im sure many people have this
I think this is based on all aosp roms.
I don't know if it's fact or opinion, but I always get the "sent" message after receiving the "not sent" error.
In other words, it seems like it still sends the whole text, but just throws you an error initially.
Can someone correct me if I'm wrong?
Well i can correct you wrong because i've tested it it does not sent the messages nor does it have anything to so with AOSP roms because i've used both AOPK and they both have the issue,
I send long sms no problem.. some in fact so. Long it automatically breaks them into two. What firmware are you on.
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
First off this belongs in Q&A so I will move it
Second AOKP is also considered an AOSP type ROM
There should be an option in your mms app to split messages over 160 characters. Make sure it is checked.
On the Touchwiz ROMs that came with the SIII and all TW custom ROMs this is not an issue. This is a Touchwiz phone so changing your ROM to anything but that will have some bugs and require fixes and workarounds.
Friendly Neighborhood Moderator
Contact your carrier
Especially if you're having this issue on and off
Do other apps work? I use ChompSMS (fixes lots of annoying bugs in the TW SMS app) and I can send long messages fine.
kennyglass123 said:
F
On the Touchwiz ROMs that came with the SIII and all TW custom ROMs this is not an issue. This is a Touchwiz phone so changing your ROM to anything but that will have some bugs and require fixes and workarounds.
Click to expand...
Click to collapse
i have to disagree. I had like i said in OP, i tried ALL roms, stock, stock rooted, cyanogen and many other, this was an issue in all roms.
polish_pat said:
i have to disagree. I had like i said in OP, i tried ALL roms, stock, stock rooted, cyanogen and many other, this was an issue in all roms.
Click to expand...
Click to collapse
are you using a mms app other than what's provided with the rom? And are you able to send any messages at all? or does it fail to send only on long ones?
If you were on stock and still can't send any/long messages, check your apn settings and make sure it's correct for your provider, especially if you are installing roms (stock or custom) that are specifically developed for AT&T phones. From your profile I'm assuming you have a Canadian version.
Check the APN settings. If that's all correct, return the phone for a new one
all apn settings are fine and this is not an issue with the phone because like i said, it would be one hell of a coincidence if this happened to both of my friends with gs3s on different providers. Also i am using stock sms app and this only happens with moderately long sms, it doesnt always ahppen, its random
If it's intermittent, and it's not just you but also your friends, it sounds like a provider problem. From what I have been reading on different forums, it seems service in Canada has been sketchy because they're adding LTE towers everywhere.
I don't know if that's really the case, but all I can say is texting works well for me down here on the AT&T network, both on AOSP (which also includes AOKP as you were mistaken earlier) and stock-based ROMs, although I do get the error on AOSP based roms for long messages. I've asked my friends and they say they receive the whole message just fine.
Last thing I can think of is if you flashed a custom kernel and it messed with some of your drivers. I know KToons kernel has modified drivers, and you're supposed to flash the stock kernel provided in that thread if you're going back to stock. Try that and see if that fixes your problem.
yup, i've flashed ktoon kenel as i had major issues with faux kernel as per this thread: http://forum.xda-developers.com/showthread.php?t=1937476
i'll report back in a week to see if any different
thanks for you help
New user, first post, if I am missing info then I apologize.
I have the tmobile galaxy s 3 SGH-t999.
Started looking around at different roms, etc, ended up with trying the cyanogenmod 10 first.
Did the required steps, used oden to load the clockworkmod recovery.
Wiped/factory reset, then loaded up the rom. Seemed to work pretty well other than some issues with the cam crashing (seperate issue which I researched and believe I have the answer to). But overall the problem was that intermittently the inbound audio on calls sounded robotic, and reverberating. Also dealt with 4 hour battery life. Tons of info to address later when this issue is corrected however.
Have been digging around on forums, and see this issue, but no articles yet (that i have found) addressed for the SGH-t999.
Ended up re-wiping the phone and put on the liquid smooth rc9 (d2tmo).
So far it appears i am having basically the same exact issues that occurred in cyanogenmod. If I reboot the phone, it will continue. Then for whatever reason the next few calls or so later that are sent or received it sounds fine. Then back to robotic.
End user can hear me fine. The audio issue is just for inbound voice.
Tried to factory reset again, still the same issue.
I have installed the google pack to be able to use play store, etc. Perhaps this is causing the issue?
I did try to get the log cat, but could not replicate the issue while running it, so I am not sure if it would be of any use or not.
Also, this issue does not make a difference whether bluetooth is enabled or not. Am not doing wifi calling, have not tested that yet.
Again very sorry if this article is incomplete.
Thanks in advance for the help!
Resolved
tsm233 said:
New user, first post, if I am missing info then I apologize.
I have the tmobile galaxy s 3 SGH-t999.
Started looking around at different roms, etc, ended up with trying the cyanogenmod 10 first.
Did the required steps, used oden to load the clockworkmod recovery.
Wiped/factory reset, then loaded up the rom. Seemed to work pretty well other than some issues with the cam crashing (seperate issue which I researched and believe I have the answer to). But overall the problem was that intermittently the inbound audio on calls sounded robotic, and reverberating. Also dealt with 4 hour battery life. Tons of info to address later when this issue is corrected however.
Have been digging around on forums, and see this issue, but no articles yet (that i have found) addressed for the SGH-t999.
Ended up re-wiping the phone and put on the liquid smooth rc9 (d2tmo).
So far it appears i am having basically the same exact issues that occurred in cyanogenmod. If I reboot the phone, it will continue. Then for whatever reason the next few calls or so later that are sent or received it sounds fine. Then back to robotic.
End user can hear me fine. The audio issue is just for inbound voice.
Tried to factory reset again, still the same issue.
I have installed the google pack to be able to use play store, etc. Perhaps this is causing the issue?
I did try to get the log cat, but could not replicate the issue while running it, so I am not sure if it would be of any use or not.
Also, this issue does not make a difference whether bluetooth is enabled or not. Am not doing wifi calling, have not tested that yet.
Again very sorry if this article is incomplete.
Thanks in advance for the help!
Click to expand...
Click to collapse
Ok, after 4 different roms, and lots of testing, I finally figure it out.
Using Voxer caused the issue. As soon as a voice message is sent using voxer, the problem starts immediately, and is correct by a reboot. Issue immediately returns once Voxer is used.
Any idea of how to work around this, besides the obvious? =)
Long time fan; first time post.
I was hoping this posting had provided a solution, but the 'Contacts Fix' did not help with my apparent issue:
(Synergy ROM) Phone app now not working?
I'm lovin' the Synergy ROM, however every time I start up the phone, I always get the 'com.android.phone has stopped' error.
Please, would anyone like to take a look at the Logcats provided?
Attached in the zip file are two logcats. One records my attempt to make a phone call; the other I hope reflects what's happening when the phone is starting up: AttemptedPhoneCall.txt & StartingUpPhone.txt
Sure, I could go back to my High On Android ROM (Have to give a nod to its author, Max of GalaxyS3root.com), but it was Max that raved about Synergy in the first place, and it has grown on me.
Despite the fact I can't send or receive any calls. I can text and surf, but it's not a phone anymore.
I never received that error on Synergy, but I have seen it on other ROMs. Have you tried a full wipe and reflash? In my experience, flashing Synergy worked best when I flashed it from another TW based ROM.
You could try a different kernel such as ktoonsez kernel. I had a lot of issues with the standard ziggy kernel when I used synergy
Sent from my SAMSUNG-SGH-I747 using Tapatalk 4 Beta
Will do
altrikdout21 said:
I never received that error on Synergy, but I have seen it on other ROMs. Have you tried a full wipe and reflash? In my experience, flashing Synergy worked best when I flashed it from another TW based ROM.
Click to expand...
Click to collapse
Thanks, altrikdout21.
Yes, I intend to. I was just curious if there were some developers out there that like to look at logcats for kicks.
Didn't think of that.
Domoo said:
You could try a different kernel such as ktoonsez kernel. I had a lot of issues with the standard ziggy kernel when I used synergy
Click to expand...
Click to collapse
Problems with the ziggy, uh?
Ok, I'll try another and let you know.
Thanks, Domoo.
Got it working...almost sort ya.
Restored my last ROM, HighOnAndroid. I did do the reflash of Synergy with a stock kernel, but there was no improvement, and so I restored my previous ROM. I can now start up the phone without the 'com.android.phone has stopped' error. However, there's a problem. I still can't make a phone call! Yikes! Now how can that be??? I did a ROM restore. Shouldn't the phone app be back as it was? It appears all the other apps are working. I can text, surf, etc. What's happening here?
I start up the phone app, select a contact, press the phone icon on the contact's screen, it comes up like it's going to initiate a call but then I see the 'end call' just as fast and the phone app then retreats back to the previous screen listing the contact I had selected to call.
As an aside, is there a place to drop off you logcats on this forum? Being an old VB programmer (what's that you ask?!), I'm curious to see what these new fangled 'android programmers' can do. However, now I'm ever more anxious to find out what's wrong with the phone app since I've restored my ROM only to find the one lone thing I do use regularly (it's a phone for pete sake!) is still not working.
I've got a low post count but wanted to weigh-in on the current version of the Sense 5 rom.
I'm using T-Mobile, so not sure if my issues are related to my carrier or not...
1) Bluetooth isn't working. Turning it on does not result in anything...it goes fro turning on to off. Assuming it's the HTC One S ril that the rom is based on casuing this problem.
2) HTC Messages (the stock messenger) will not let me click a link in the message. If someone send me a text with an external link, and I go to click it, it causes Messages to force quit. I can use 3rd part apps and it works fine. Just an FYI...
3) HTC Locations doesn't work but I believe that is a Sense 4/ Sense 5 issue.
Everything else seems to be working. I am using this as my daily rom and haven't had any troubles (besides the ones mentioned above).
Thank you to everyone working on this!
rsiddall3130 said:
I've got a low post count but wanted to weigh-in on the current version of the Sense 5 rom.
I'm using T-Mobile, so not sure if my issues are related to my carrier or not...
1) Bluetooth isn't working. Turning it on does not result in anything...it goes fro turning on to off. Assuming it's the HTC One S ril that the rom is based on casuing this problem.
2) HTC Messages (the stock messenger) will not let me click a link in the message. If someone send me a text with an external link, and I go to click it, it causes Messages to force quit. I can use 3rd part apps and it works fine. Just an FYI...
3) HTC Locations doesn't work but I believe that is a Sense 4/ Sense 5 issue.
Everything else seems to be working. I am using this as my daily rom and haven't had any troubles (besides the ones mentioned above).
Thank you to everyone working on this!
Click to expand...
Click to collapse
when I used it the dailer would freeze and fc and data wouldnt stay on 4g or h
More insights:
Camera works but the facial recognition seems to be wonkey. I've turned it off so as not to see it jumping around like crazy.
Video...not sure if this is working. I do know that it comes on and the camera crashes and I have to restart.
FM radio...not a deal-breaker, but if I stick a pair of headphones in - the tuner never lets go and stations can't be tuned in.
GPS...saw that was one of the 'not working' apps. I don't really use it for navigation...as long as you've got wifi it seems to be able to locate but driving with it is impossible as it doesn't seem to know where you or or lock your position in.
I've been using this since JMZ updated the last version (so 2 weeks?). Haven't had a problem. And none of these, for me, make this rom unusable...it would just be nice to have a fully working one with Sense 5.
I will work on it some more when I get my oc back as my desktop is old and slow.
Sent from my HTC One VX using xda app-developers app
This ROM also duplicate pictures and songs