Discuss HC 3.1 after installed/ Bug report

[PuppyHacker]

Well, good news is that 2-step verification is not a problem for me. I'm able to log in with an account I have 2-step setup on and I'm not prompted for the extra step.

[davpel]

When did you first install the HC update and login to Googe? Was it within the last 12 hours?

[PuppyHacker]

When did you first install the HC update and login to Googe? Was it within the last 12 hours?

The day of the release...I just tested by adding an account that had 2-step verification

[davpel]

I'm just wondering whether Google somehow blocked it for new installs of the upgrade. Waiting to hear from someone brave enough to try an install today.

[Ariq]

Whatever the problem it is I do not think this is from the logitech side. If Logitech shut eveything down then people who aren't forcing the update on would not be able to do a new connect either, at least as far as I can conceptualize. If anyone new is getting connected please post here right away. If there is interference being ran somewhere it doesn't look good for us. If someone is willing to shut people off for wanting to test a leaked beta, removing the open- sourced nature of the beast, then it might be bad news for us getting the official update to (until a root is figured out anyway).

I will say all of my stuff is still up and running which,to me, seems like if there was someone desiring to shut it all down, they likely have the means to halt existing accounts from linking. As weird as it is to say, hopefully we just crashed something important that will be back online once they've fixed it. That's my two cents, remarkable I know.

[divergent]

If someone is able to route their traffic through a proxy application like Squid or Privoxy, we might be able to see why new setups are failing. I have been tempted to give this a shot, but have been hesitant due to no netflix so I can't do it myself.

[quake101]

I believe someone could use wireshark to sniff the traffic as well. If someone hasn't done this by tonight, I'll give it a shot.

[joedeveloper]

Whatever the problem it is I do not think this is from the logitech side. If Logitech shut eveything down then people who aren't forcing the update on would not be able to do a new connect either, at least as far as I can conceptualize. If anyone new is getting connected please post here right away. If there is interference being ran somewhere it doesn't look good for us. If someone is willing to shut people off for wanting to test a leaked beta, removing the open- sourced nature of the beast, then it might be bad news for us getting the official update to (until a root is figured out anyway).

I will say all of my stuff is still up and running which,to me, seems like if there was someone desiring to shut it all down, they likely have the means to halt existing accounts from linking. As weird as it is to say, hopefully we just crashed something important that will be back online once they've fixed it. That's my two cents, remarkable I know.

Uhm yeah to say the least. That's pretty jacked up if they are not allowing people to use it. If they are blocking you from using it, then they have basically said, oops so sorry we have bricked your device!

I have a working version otherwise I would try to help people work around the issue. If it is trying to send out a request to the google server and getting a failed response, one of the ways to resolve it is use wireshark.

Sniff the traffic out and back, probably over port 80. See if the message back is a simple Failed or what the message structure is like. XML? etc. Then you can reroute the traffic internally so that the revue sends the request to your machine or a website you setup that response with the same syntax but has a success message instead of failed.

Just my 2 cents.

[txyaloo]

Uhm yeah to say the least. That's pretty jacked up if they are not allowing people to use it. If they are blocking you from using it, then they have basically said, oops so sorry we have bricked your device!

How do you figure that? If it were an official update, then sure, you could say that, but it's not. It's an unofficial leak. Logitech has no duty to support the leak, enable back-end servers, etc. People knew it was a leak and took that risk. Plenty of other companies take the same stance. Devices being "bricked" are completely the end user's fault.

[joedeveloper]

Uhm yeah to say the least. That's pretty jacked up if they are not allowing people to use it. If they are blocking you from using it, then they have basically said, oops so sorry we have bricked your device!

How do you figure that? If it were an official update, then sure, you could say that, but it's not. It's an unofficial leak. Logitech has no duty to support the leak, enable back-end servers, etc. People knew it was a leak and took that risk. Plenty of other companies take the same stance. Devices being "bricked" are completely the end user's fault.

Agreed, its your risk to do it. I did and got through. However, I do think it's kind of lame to now block on the back end if that is indeed what they are doing.