[Q] GTalk closes upon launching ("failed to get GTalk connection!")

---

Context:

- T-mobile G1
- CyanogenMod 6.1.0-DS

Whenever I try to launch GTalk, the application starts and then instantly closes itself. I tried looking at the phone using LogCat in Eclipse and got the following line:

06-05 17:00:55.967: E/talk(710): signInAccount: failed to get GTalk connection!

What can I do to make GTalk work?

I've already tried:

- Rebooting the phone
- Reinstalling the Google Apps ZIP

... logging in with your Google account?

Sent from my Gingerbread on Dream using XDA

How would I log in? The phone already has a Google login for my account; that's why it can get my e-mail and contact information.

I'm seeing this same issue with CM 7.2.0.1 on an HTC Desire (GSM). I'd only recently (about a week ago), upgraded from a CM 7.1, but gtalk had been working for a while since that upgrade, it stopped working yesterday with the "closes very quickly after starting" behaviour.

Full logcat excerpt for an attempt (fresh after a reboot to install the latest gpapps as I'd not done that before, assuming Google Play would have updated all necessary):

I/ActivityManager(  173): Starting: Intent { act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] flg=0x10200000 cmp=com.google.android.talk/.SigningInActivity bnds=[0,732][96,800] } from pid 277
I/ActivityManager(  173): Start proc com.google.android.talk for activity com.google.android.talk/.SigningInActivity: pid=937 uid=10058 gids={3003, 1015}
D/szipinf (  937): Initializing inflate state
I/ActivityThread(  937): Pub com.google.android.talk.SuggestionProvider: com.google.android.talk.SuggestionsProvider
D/dalvikvm(  937): GC_CONCURRENT freed 412K, 51% free 2765K/5639K, external 0K/0K, paused 3ms+6ms
D/ViewConsistency(  937): AbsListView android.widget.ListView@4076a628 enabled= true
D/ViewConsistency(  937): AbsListView android.widget.ListView@4076a628 enabled= true
D/GTalkService(  261): AcctMonitor.auditGTalkConnections: not starting any connections since shouldTryToConnect is false
I/ActivityManager(  173): Starting: Intent { dat=content://com.google.android.providers.talk/accounts/1 cmp=com.google.android.talk/.SigninActivity } from pid 937
W/GTalkService(  261): blockingCreateGTalkConnection failed due to low storage!
D/dalvikvm(  261): GC_CONCURRENT freed 490K, 49% free 3290K/6407K, external 0K/0K, paused 3ms+14ms
E/talk    (  937): signInAccount: failed to get GTalk connection!
W/InputManagerService(  173): Window already focused, ignoring focus gain of: com.android.internal.view.IInputMethodClient$Stub$Proxy@407e10d0
I/ActivityManager(  173): No longer want com.android.providers.calendar (pid 503): hidden #16
W/ActivityManager(  173): Duplicate finish request for HistoryRecord{40b9e8e8 com.google.android.talk/.SigninActivity}

Note that was an in-place upgrade from 7.1.? and I'm constantly fighting with low phone internal storage on this device, although right now it shows 11MB free.

[SOLVED] Bad default partition sizes ?

---

It seems likely now that this was just one symptom (also had Twitter app Force Closing, Google Reader unable to auth/connect, Browser Force Closing etc) of the bad default partition setup on an HTC Desire.

I managed to get S-OFF and then use the 'CM7r2' partition setup from alpharev.nl (I've too few posts to be able to post actual links) and so far everything's working without issues. Basically the default setup has a /system way too large for CM7's needs, and using that space in /data instead gives a lot of breathing room whereas with the default /data kept on filling and causing apps problems (and, yes, this was with as much as possible APP2SD'd).

It's possible I could have solved this using SD-EXT (partition your SD card to have 2 partitions, one of ~1GB for SD-EXT, the rest for SDCARD as usual), but I didn't try that.

Originally Posted by Athan

It seems likely now that this was just one symptom (also had Twitter app Force Closing, Google Reader unable to auth/connect, Browser Force Closing etc) of the bad default partition setup on an HTC Desire.

I managed to get S-OFF and then use the 'CM7r2' partition setup from alpharev.nl (I've too few posts to be able to post actual links) and so far everything's working without issues. Basically the default setup has a /system way too large for CM7's needs, and using that space in /data instead gives a lot of breathing room whereas with the default /data kept on filling and causing apps problems (and, yes, this was with as much as possible APP2SD'd).

It's possible I could have solved this using SD-EXT (partition your SD card to have 2 partitions, one of ~1GB for SD-EXT, the rest for SDCARD as usual), but I didn't try that.

Since I have no idea what you mean by "S-OFF" or "CM7r2", could you post the search engine keywords you used to find the instructions to use the 2 things?

S-OFF is 'security off'. It refers to a HTC phone feature where some bits of the boot sequence can't be changed whilst it's on, so you need to go from S-ON to S-OFF in order to then be able to change that part of the boot sequence. This I did using the 'AlphaRev 1.8 HBOOT reflash utility' from alpharev.nl , I applied it using VirtualBox to boot the image.

A small guide to doing this is at: http://forum.xda-developers.com/show...1&postcount=31

In turn that part of the boot sequence is where you can tell the following part that the partition table has been changed.

The 'CM7r2' simply refers to "CyanogenMod release candidate 2". Note I mentioned with regards to changing partition layout it when referring to the alpharev.nl site which contains the necessary files to change the partition setup. Just put alpharev.nl into your web browser's address/search bar to go to the site (again, I can't link because THIS site only lets you after a certain number of forum posts, the minimum of which I've not yet reached).

Hope this helps.

So you are saying that alpharev made a patched bootloader that won't check for secure flags on the g1 or you just posted in e wrong thread?

Sent from my Nexus 7 using xda premium

Ah, sorry, I forgot I originally posted about the GTalk problem in a forum not about the HTC Desire, which is what I have.

Still, anyone having such an issue may still find it's due to 'bad' partioning of their phone, whatever the model. The same basic problem may apply: /data is too small, such that it (near-)filling causes apps to randomly fail, both in the manner GTalk can (closes as soon as it opens without being able to auth, logcat suggests some problem with authing), or just simply force closing.

If your phone has enough storage that a change of partition sizes (with the HTC Desire the method I outlined reallocated some un-needed space from /system to /data) will result in a larger /data without compromising functionality then it may solve such issues.