[Announce] The One Ring - Page 107 - maemo.org

Active Topics

Sailfish OS for the Motorola Moto G7 Power (XT1955-5) - (ocean) (4)
to SailfishOS by Maemish - 5 hrs, 35 mins ago
The N900 is now 15 years old! (6)
to Nokia N900 by Macros - 2 days, 1 hr ago
F(x)tec Pro1x (QWERTY) for sale (0)
to Buy & Sell by aln00000 - 2 days, 14 hrs ago
n770 youtube video (0)
to General by nmdv - 6 days, 13 hrs ago
more...

Page 107 of 109

107

Thread Tools

getnani	2013-01-31 , 05:17
Posts: 129 \| Thanked: 32 times \| Joined on Jun 2010	#1061

I was wondering who else might be using this!!! glad to find at least two people are using it. I was hesitant to post becos i couldnt see any activity on this thread! anyways, very happy to someone who is ready to share his exp. without any hesitation!

Originally Posted by Xenolith0

For the last 5 or so days TOR has been unable to connect to GV. After researching the problem, I found what has changed is Google's login URL. Which previously was "https://www.google.com/accounts/ServiceLoginAuth" and has now changed to be "https://accounts.google.com/ServiceLoginAuth".

Until the developer updates his package, a quick work-around to this is to edit the file "/opt/theonering/lib/gvoice/backend.py" go to line 169 and change:
self._loginURL = "https://www.google.com/accounts/ServiceLoginAuth"
to
self._loginURL = "https://accounts.google.com/ServiceLoginAuth"

After that just initiate a reconnect, and it should work.... Assuming anyone else is having this issue. After searching the forums I have not seen anyone else reporting this problem, so maybe Google only hates me.

However, this is why I LOVE open source software. <3 Maemo.

theonering.log:
Code:
(2013-01-30 16:49:56,405) DEBUG AsyncPool.gvoice.browser_emu: Performing download of https://www.google.com/voice/m
(2013-01-30 16:49:57,410) DEBUG AsyncPool.gvoice.browser_emu: Performing download of https://www.google.com/accounts/ServiceLoginAuth
(2013-01-30 16:49:58,586) DEBUG AsyncPool.gvoice.browser_emu: HTTP Error 404: Not Found: https://www.google.com/accounts/ServiceLoginAuth
(2013-01-30 16:49:58,591) DEBUG AsyncPool.gvoice.browser_emu: MozillaEmulator: urllib2.URLError, retrying 1
(2013-01-30 16:49:59,058) DEBUG AsyncPool.gvoice.browser_emu: HTTP Error 404: Not Found: https://www.google.com/accounts/ServiceLoginAuth
(2013-01-30 16:49:59,119) ERROR AsyncPool.gvoice.backend: Translating error: HTTP Error 404: Not Found
(2013-01-30 16:49:59,159) ERROR AsyncPool.util.go_utils: Error, passing it back to the main thread
Traceback (most recent call last):
  File "/opt/theonering/lib/util/go_utils.py", line 191, in __consume_queue
    result = func(*args, **kwds)
  File "/opt/theonering/lib/gvoice/backend.py", line 294, in login
    loginSuccessOrFailurePage = self._login(username, password, galxToken)
  File "/opt/theonering/lib/gvoice/backend.py", line 283, in _login
    loginSuccessOrFailurePage = self._get_page(self._loginURL, loginData)
  File "/opt/theonering/lib/gvoice/backend.py", line 779, in _get_page
    raise NetworkError("%s is not accesible" % url)
NetworkError: https://www.google.com/accounts/ServiceLoginAuth is not accesible
(2013-01-30 16:49:59,171) ERROR MainThread.connection: https://www.google.com/accounts/ServiceLoginAuth is not accesible
(2013-01-30 16:49:59,175) INFO  MainThread.connection: Disconnecting

Quote & Reply |

	sondjata	2013-02-01 , 15:09
	Posts: 1,076 \| Thanked: 176 times \| Joined on Mar 2007	#1062

Looks like the built in RTComm for GoogleVoice is hosed as well.

__________________
---
N800
Diablo
Boot from MMC
Gpodder Cache on MMC
MTube Cache on MMC
Mugen 1800mAh Battery
Addesso USB rollup keyboard
Solio Solar Charger
Holux GPSlim GPS

N810
community SSU
Turbo Diablo
8GB external
Boot from Internal SD
Still no GPS Fix.

N900
Stock
32GB
Many Solar Chargers (Saved bacon during Sandy!)
Inland ProHT BT keyboard
What's this? A GPS Fix? Wowwwwwww

Quote & Reply |

Mentalist Traceur	2013-03-31 , 23:38
Posts: 2,225 \| Thanked: 3,822 times \| Joined on Jun 2010 @ Florida	#1063

Originally Posted by sondjata

Looks like the built in RTComm for GoogleVoice is hosed as well.

There's a built-in one?

Anyway, major thanks to the person who figured out why this thing was failing to sign in, and how to fix it! I too was having difficulty figuring out why I was getting "Network Error" when trying to connect to GV with this, since it seems google failed to index any references to this problem.

Quote & Reply |

	sondjata	2013-03-31 , 23:44
	Posts: 1,076 \| Thanked: 176 times \| Joined on Mar 2007	#1064

Interestingly I cannot place GV call anymore. Must use the website. Boo... AT least I have my Text and IM's working.

Quote & Reply |

jackivan88	2013-04-01 , 02:31
Posts: 1 \| Thanked: 0 times \| Joined on Apr 2013	#1065

Originally Posted by Xenolith0

Until the developer updates his package, a quick work-around to this is to edit the file "/opt/theonering/lib/gvoice/backend.py" go to line 169 and change:
self._loginURL = "https://www.google.com/accounts/ServiceLoginAuth"
to
self._loginURL = "https://accounts.google.com/ServiceLoginAuth"

I've edited the file and still can't connect through The One Ring. Any other common issues that have cropped up in the last few weeks that might be causing a hangup? Something related to RTComm?

Quote & Reply |

	Xenolith0	2013-04-11 , 03:46
	Posts: 8 \| Thanked: 34 times \| Joined on Mar 2010	#1066

Originally Posted by jackivan88

I've edited the file and still can't connect through The One Ring. Any other common issues that have cropped up in the last few weeks that might be causing a hangup? Something related to RTComm?

TOR is still working fine for me after doing the URL change. I'm able to both receive and initiate outbound calls & texts.

Quote & Reply |

MTCONE	2013-04-29 , 20:48
Posts: 32 \| Thanked: 17 times \| Joined on Feb 2010 @ Earth	#1067

I have edited line 169, but still get the same error message about not being able to access "https://www.google.com/accounts/. . . "

I see no other instance of that url in backend.py

Does The One Ring work any more?

Any suggestions?