Exploitee.rs

spower wrote:I had successively applied the android honeycomb updated. Everything was fine, i watched TV, youtube and then turned the unit off. Today when I turned the unit powers up with the logo screen (just logtech with google tv) and stuck there. I couldn't get to the home screen. Any help?

I have the same exact problem - turned off because I was going out for a few hours and the unit just sits at the logosince I turned it on when I got home tonight. Can anyone help?

fdnyubergeek wrote:

spower wrote:I had successively applied the android honeycomb updated. Everything was fine, i watched TV, youtube and then turned the unit off. Today when I turned the unit powers up with the logo screen (just logtech with google tv) and stuck there. I couldn't get to the home screen. Any help?

I have the same exact problem - turned off because I was going out for a few hours and the unit just sits at the logosince I turned it on when I got home tonight. Can anyone help?

I'm not seeing this problem.. How are you guys "turning off" the revue? Are you pulling the power out or just using the keyboard and powering off the TV and STB?

I'll test it again if you tell me what you are doing.

PuppyHacker wrote:

fdnyubergeek wrote:

spower wrote:I had successively applied the android honeycomb updated. Everything was fine, i watched TV, youtube and then turned the unit off. Today when I turned the unit powers up with the logo screen (just logtech with google tv) and stuck there. I couldn't get to the home screen. Any help?

I have the same exact problem - turned off because I was going out for a few hours and the unit just sits at the logosince I turned it on when I got home tonight. Can anyone help?

I'm not seeing this problem.. How are you guys "turning off" the revue? Are you pulling the power out or just using the keyboard and powering off the TV and STB?

I'll test it again if you tell me what you are doing.

"Pulling the power" is an apt description. I have some green outlets and strips in my house that completely shut down "vampire" electronics, so the whole circuit goes off.

"Pulling the power" is an apt description. I have some green outlets and strips in my house that completely shut down "vampire" electronics, so the whole circuit goes off.

That might be your problem right there. Modern day electronics are not made to have power shut off abruptly like that on a continual basis (That's why they have standby mode which uses almost no power at all). Whenever you disconnect or reconnect power to something, it causes a spike in the electrical current, which has the potential to cause damage.

mrandroid wrote:

"Pulling the power" is an apt description. I have some green outlets and strips in my house that completely shut down "vampire" electronics, so the whole circuit goes off.

That might be your problem right there. Modern day electronics are not made to have power shut off abruptly like that on a continual basis (That's why they have standby mode which uses almost no power at all). Whenever you disconnect or reconnect power to something, it causes a spike in the electrical current, which has the potential to cause damage.

True, but there are plenty of devices out there, as well as ones I am using that have no issue with this. Besides, I know there are no spikes in the line because I am using a UPC with power conditioning. Also, I should be able to shut the device down if need be. I wanted to program it in my computer room, test it, and then move it into one of my children's rooms.

fdnyubergeek wrote:

mrandroid wrote:

"Pulling the power" is an apt description. I have some green outlets and strips in my house that completely shut down "vampire" electronics, so the whole circuit goes off.

That might be your problem right there. Modern day electronics are not made to have power shut off abruptly like that on a continual basis (That's why they have standby mode which uses almost no power at all). Whenever you disconnect or reconnect power to something, it causes a spike in the electrical current, which has the potential to cause damage.

True, but there are plenty of devices out there, as well as ones I am using that have no issue with this. Besides, I know there are no spikes in the line because I am using a UPC with power conditioning. Also, I should be able to shut the device down if need be. I wanted to program it in my computer room, test it, and then move it into one of my children's rooms.

Saying "there are plenty of devices out there that have no issue with this" is closed minded thinking. No devices that I can think of are MADE to mess up when disconnected/reconnected. There are millions of toasters out there that work great, but that doesn't stop one from messing up or defecting. You have to look at it from a general electronics point of view. Nothing gives warnings of failure. My microwave doesn't email me ahead of time to let me know it's going to stop working.

As far as the UPC, that's a great thing to use, but it doesn't resolve the potential issue. the power spike isn't necessarily coming from your main line. It's coming from whatever you plug it into, whether that be the main line, a surge protector, a UPC, etc.. The surge comes from the abrupt connect or disconnect from said source (you ever plug/unplug anything and see a tiny arc? same thing). Devices are conditioned to handle this most of the time, but there's no definitive range of power that the surge will produce, so there's always a potential to cause harm by disconnecting/reconnecting.

As far as programming in one room and moving it. I never said it HAS to stay in one location lol. Look at it like a roulette wheel where 95% of the wheel is black and 5% is red. Every time you connect/disconnect the device you're spinning the wheel. Now you have a HUGE chance of no issue coming from it, but there is always that small percentage that you will "land on red" and produce a spike, which in itself has a percentage of causing an issue. The overall percentage is very small, but it's still there, and every time you connect/disconnect from a live source you're "spinning the wheel".

By the way, I know what I said above may come off as rude, and I apologize for that. it wasn't my intention at all. It's 6am in the morning, and my mind isn't processing enough right now to come up with a better way to word what I said.

mrandroid wrote:Saying "there are plenty of devices out there that have no issue with this" is closed minded thinking. No devices that I can think of are MADE to mess up when disconnected/reconnected. There are millions of toasters out there that work great, but that doesn't stop one from messing up or defecting. You have to look at it from a general electronics point of view. Nothing gives warnings of failure. My microwave doesn't email me ahead of time to let me know it's going to stop working.

I agree with everything you've said except your conclusion. After eight years of troubleshooting everything from PC's to enterprise systems, I've developed a feel for probabilities that helps me to direct the investigation down the right path (more often than not). While cycling power can definitely have negative consequences, those consequences tend to be unique and to manifest in fairly random ways on any given device, and through dissimilar circumstances.

What I'm hearing here is a variety of people who have disconnected or lost their power to their Revue after applying the 3.1 upgrade and are now stuck at the exact same place when they attempt to power it up. That sounds less like like random damage and more like a function of design as in: this may be what will happen to anyone who pulls power after upgrading.

Has anyone upgraded to 3.1, pulled power from their Revue and is still able to boot up properly? I wouldn't suggest doing this just to see, needless to say.

Immolate wrote:

mrandroid wrote:Saying "there are plenty of devices out there that have no issue with this" is closed minded thinking. No devices that I can think of are MADE to mess up when disconnected/reconnected. There are millions of toasters out there that work great, but that doesn't stop one from messing up or defecting. You have to look at it from a general electronics point of view. Nothing gives warnings of failure. My microwave doesn't email me ahead of time to let me know it's going to stop working.

I agree with everything you've said except your conclusion. After eight years of troubleshooting everything from PC's to enterprise systems, I've developed a feel for probabilities that helps me to direct the investigation down the right path (more often than not). While cycling power can definitely have negative consequences, those consequences tend to be unique and to manifest in fairly random ways on any given device, and through dissimilar circumstances.

What I'm hearing here is a variety of people who have disconnected or lost their power to their Revue after applying the 3.1 upgrade and are now stuck at the exact same place when they attempt to power it up. That sounds less like like random damage and more like a function of design as in: this may be what will happen to anyone who pulls power after upgrading.

Has anyone upgraded to 3.1, pulled power from their Revue and is still able to boot up properly? I wouldn't suggest doing this just to see, needless to say.

Oh I agree that it's probably a software issue caused by the beta. I just brought this up as a potential cause for a single individual (if you read my first posting to him). I never stated it was THE cause, I just said that it might be his cause.

mrandroid wrote:Oh I agree that it's probably a software issue caused by the beta. I just brought this up as a potential cause for a single individual (if you read my first posting to him). I never stated it was THE cause, I just said that it might be his cause.

No worries. I understood where you were coming from. Since I haven't yet upgraded my Revue, I am anxious to learn if anyone has lost power to their revue and did not experience the behavior of being stuck at the boot screen.

Also, has anyone with this issue tried using ALT-L to enter recovery, and if so, were you able to do something positive after that? I understand from my reading that ALT-L is the recovery mode shortcut for 3.1 on the Revue.

I have tried the FN +Left and ALT+L and I am not able to get anywhere past the initial Logo screen. Holding the Pair/Reset button after powering on for a second does cause the revue to reboot, but it just stays stuck at the logo screen, and does not progress to the Google Tv logo and "horizontal babershop" logo.