Where is the 2013.320 build?

[IownFIVEechos]

Well I just had the famous out of the blue 'lets recover for no reason' on my echo. Wife was alittle freaked. Any who, why can I not get the .320 back. That was the one I had the most luck with. It did not make me feel like I was going to have a seizure while watching tv? Please add it back ceton. If you are not going to make new builds please do not remove older ones. People can decide if they want it or not right? C'mon Man?

[Crash2009]

I only have 2 Echo's. Echo1 is running 2013.304.1657 and Echo2 is running 2013.320.1349. I don't see much of a difference between the two, although, I only use them to watch TV or play WTV's. Where I noticed a big difference between reliable and unreliable was with the setup software that you install on the HTPC. When I installed ceton_echo_setup_w7_13_01_16_0480 I started getting all the negative symptoms that I read about here. I went back to ceton_echo_setup_w7_201212204_12_04_0935 and the problems disapeared.

I was toying with the idea of getting both Echo's on the same firmware, and I opened a ticket with Ceton support. It is possible to go back to stable, however, it is a bit of a pain, so I didn't bother.

The following are the directions that I received from Ceton Support:

For the Echo on the beta firmware the easiest way to revert is to do a recovery. We would like to try and force your unit to recover using the Echo's built in recovery ability. Please make sure you are always using both the supplied USB power adapter and special USB cable provided in your Echo kit and follow the steps below:

1.) Attach network, power and video cables to your Echo, then turn it on.
2.) Power off the Echo using your remote control.
3.) Type the word "recovery" (73268379) on the number pad of your remote control.
Be steady, with no pauses when entering the code. If you mistype the entry just try retyping the entire number sequence again.
4.) The Echo should turn on and enter recovery mode. Please leave it in this mode until it completes, or for at least 60 minutes.
5.) If Echo has not completed recovery after 60 minutes, please power it off with the remote, then power it back on and allow it to sit for another 60 minutes.

Please let us know the outcome. Once the recovery is complete you can then just update to the latest stable release, 2013.304.1657.

Thank you,
Ceton Support

[Crash2009]

I think I miss-read you. Are you trying to get the beta back? What version are you on?

[IownFIVEechos]

I think I miss-read you. Are you trying to get the beta back? What version are you on?

That is correct. .320

[IownFIVEechos]

I had a long winded reply, but when I hit submit I got a html page does not exist error so with that said I will make this short.

I am on the stable version now, no other version seems to be offered. I want to be back on .320. One of my echos is still on that flavor (until it gets recovered like this one did this morning).

[Crash2009]

I think I miss-read you. Are you trying to get the beta back? What version are you on?

That is correct. .320

Have you gone into Echo settings and turned on Update Channel "Beta"?

[IownFIVEechos]

Yes and now the stable version appears in both beta and stable. I remember someone else mentioning this awhile back. I would love to have it back.

[Crash2009]

Yes and now the stable version appears in both beta and stable. I remember someone else mentioning this awhile back. I would love to have it back.

I thought I read somewhere that 320 had been discontinued/pulled, don't know for sure. One way to find out though, would be to copy your mac address, open a Ceton Support Ticket, and request an upgrade to 320. I seem to remember awhile back, we had to register our mac's with support, so that the update server would recognize us.

[barnabas1969]

It did not make me feel like I was going to have a seizure while watching tv?

The seizure angle might work! If Ceton feels like they might be sued for causing seizures, they might actually step up to the plate and deliver an update to address the issue!

It works for my employer. All you have to do is say that something about your workstation (chair, desk, keyboard, mouse, monitor, whatever) is causing repetitive motion injury, headaches, or something similar... and you get a new chair/desk/keyboard/mouse/whatever!

[shortcut3d]

320 was pulled. It was widely known to have issues with HBO. However, I think 320 had more functionality than 304. At least, MP4s play on 320 at an almost acceptable level (some stutter, but not stop start of 304). I'd like 320 back for my Echo that also went into recovery and is now at 304.

[Sammy2]

Maybe ceton pinged all the echos on the planet and sent them into recovery to put .304 on them?

[mcewinter]

Maybe ceton pinged all the echos on the planet and sent them into recovery to put .304 on them?

Except for the one that got an Android update.

[th3Pil0t]

I had massive issues with 320 (lost h264 playback completely as well as premium cable 'stuttering'). Ceton rolled me back to the latest stable. It is much better IMO, however still has it's fair share of issues

Is there something that you are missing that is exclusive to 320?

Edit: Would be nice if Ceton did initiate roll back, as that might indicate some type of progress. I am done holding my breath though.

[Crash2009]

Maybe ceton pinged all the echos on the planet and sent them into recovery to put .304 on them?

They musta missed mine. Maybe I've been entered in the Android Lottery Gotta go shine my Halo.

[barnabas1969]

I had massive issues with 320 (lost h264 playback completely as well as premium cable 'stuttering'). Ceton rolled me back to the latest stable. It is much better IMO, however still has it's fair share of issues

Is there something that you are missing that is exclusive to 320?

Edit: Would be nice if Ceton did initiate roll back, as that might indicate some type of progress. I am done holding my breath though.

Are you turning blue yet? If you've been holding your breath all this time, you should be gray (meaning dead).

[IownFIVEechos]

What I was hoping is that Ceton would explain to us why they removed it? It appears they are not even dealing with this forum any longer? I had no issues with any HBO or stutter. I enjoyed a recorded movie over the weekend and even said to myself this is not too bad. And then... And then... TRYING TO RECOVER! And now not so much as far as a clean picture. If you want to make the echo recover you just have to pull the Ethernet wire while it is booting or clear your arp tables and dhcp in the routers. Atleast that's what I am able to do. No need for the crazy codes they suggest. And what is that 'wait 60min' all about?

This last recovery occurred when my internet providers internet was down? How is this possible to bomb the echo. The internet comes in on the provided router from the cable company, it is then fed to another router on a totally different subnet which then does DHCP. So I can not understand why the internet being down forced the recovery mode? Maybe the boot logic is.

If no errors goto WMC, else RECOVER?

[shortcut3d]

Its very disturbing the Echo is actually regressing. 320 improved functionality in many areas. It's bad enough that there have been no updates for 5 months and there is no timeline, but to revert to older firmware revisions after the product inexplicably crashes.

[Motz]

We removed build 2013.320.1349 from Beta as there were some reports of instability with this build as part of mp4 playback improvements. It is not available for download anymore. I have updated the firmware thread, I am sorry that it was not updated earlier.

[IownFIVEechos]

We removed build 2013.320.1349 from Beta as there were some reports of instability with this build as part of mp4 playback improvements. It is not available for download anymore. I have updated the firmware thread, I am sorry that it was not updated earlier.

Aren't all the builds in a similar situation? Non seem completely stable for everyone. Those of us who have had better luck with the .320 would argue that the earlier ones are less stable? Can we get this build by registering our MAC addresss? Thanks for the reply.