|
2010-05-08
, 19:17
|
|
Posts: 361 |
Thanked: 108 times |
Joined on Sep 2008
|
#502
|
|
2010-05-08
, 19:49
|
|
Posts: 1,684 |
Thanked: 1,562 times |
Joined on Jun 2008
@ Austin, TX
|
#503
|
1) New router at work. Sometimes N900 appears to connect fine, but doesn't really get connected. It's not visible on the network and can't browse (N900 problem not TOR). TOR tries to connect continuously, but can't. I think this was causing battery drain. Is there a timeout after x number of failed attempts or a way to let the user know there is a problem?
2) At least 2x last week, I was unable to send GV sms through TOR. From conversations, I'd type a new message in an existing conversation. It wouldn' show up in the convo or GV. This was on 3G connection (I don't use work wifi because of issues above). Dis-connect / re-connect 3G connection fixes. Again, perhaps a N900 issues, not TOR. Although I do have the green dot indicating TOR is connected.
The Following 2 Users Say Thank You to epage For This Useful Post: | ||
|
2010-05-14
, 15:25
|
|
Posts: 1,359 |
Thanked: 717 times |
Joined on May 2009
@ ...standing right behind you...
|
#504
|
|
2010-05-14
, 16:41
|
|
Posts: 1,684 |
Thanked: 1,562 times |
Joined on Jun 2008
@ Austin, TX
|
#505
|
Haven't been following the thread for the past few weeks+ and recently re-installed TOR and RTComm and am noticing something:
When I reboot, or change wifi connection, all my google talk connections connect fine but the google voice (tor) entry in rtcomm always fails and gives a network error.
If I go into chat, disable the google voice entry and re-enable it - it connects fine.
I'm using 0.8.12-0, Diablo.
|
2010-05-14
, 16:57
|
|
Posts: 1,359 |
Thanked: 717 times |
Joined on May 2009
@ ...standing right behind you...
|
#506
|
I believe this has been reported before and if not for Diablo at least for Fremantle.
I think the issue is that the network is being a bit unrespnsive hitting a timeout in TOR. The problem is what timeout is appropriate.
|
2010-05-14
, 17:06
|
|
Posts: 1,684 |
Thanked: 1,562 times |
Joined on Jun 2008
@ Austin, TX
|
#507
|
Is there a config file where I can play around with different time-outs to see if that would help?
/usr/lib/theonering/gvoice/browser_emu.py
socket.setdefaulttimeout(30)
|
2010-05-14
, 17:09
|
|
Posts: 369 |
Thanked: 167 times |
Joined on Mar 2010
|
#508
|
|
2010-05-14
, 17:11
|
|
Posts: 1,684 |
Thanked: 1,562 times |
Joined on Jun 2008
@ Austin, TX
|
#509
|
I have it too on Fremantle. But it mostly happens at work, so I figured it was just me.
I find that I don't need to disable then reenable. I open the connection settings then click as if to edit my password. I of course don't edit the password, just click save then it works.
This works for me almost every time on the first try. If not then then always on the second try. Again, I'm on N900 so I guess it might be different.
|
2010-05-14
, 17:51
|
|
Posts: 1,359 |
Thanked: 717 times |
Joined on May 2009
@ ...standing right behind you...
|
#510
|
socket.setdefaulttimeout(45)
The Following User Says Thank You to silvermountain For This Useful Post: | ||
1) New router at work. Sometimes N900 appears to connect fine, but doesn't really get connected. It's not visible on the network and can't browse (N900 problem not TOR). TOR tries to connect continuously, but can't. I think this was causing battery drain. Is there a timeout after x number of failed attempts or a way to let the user know there is a problem?
2) At least 2x last week, I was unable to send GV sms through TOR. From conversations, I'd type a new message in an existing conversation. It wouldn' show up in the convo or GV. This was on 3G connection (I don't use work wifi because of issues above). Dis-connect / re-connect 3G connection fixes. Again, perhaps a N900 issues, not TOR. Although I do have the green dot indicating TOR is connected.
I also have seemingly random periods were TOR won't get new messages.
No logs at the moment. But I'll try to get some.
*Consumer*, not a developer! I apologize for any inconvenience.
My script to backup /home and /opt
Samsung Galaxy S Vibrant, Huawei S7, N900(retired), N800(retired)