Ran out of memory. 
What's that mean, and why is it worse on the I3 platform?

Well, nothing's changing on the device or on the Chumby backend systems.  Something must be happening on Pandora's end that is exposing some existing issue on the devices.

These types of problems are the worst to debug, since they take so long to manifest.

I wonder if I change the channel if that helps it clear up the problem, I am going to be trying that since it seems to quit in about 90 minutes now.  I guess it might or might not free up memory.

The different server side scripts, those are on pandora.com's servers I presume?

That sounds fixable, if the chumby scripts do not exhibit the problem, and everything else is the same, I would think there would be *someone* in the world who would be able to fashion a script for the Insignia branded devices that would work from the script that is working OK on the Chumby branded devices.   By changing a few values.

That's if it's possible to get Pandora to let them be changed, that is.  I presume you have contact with them?

These failures are getting pretty serious.  Getting worse by the day. And I only have the one Chumby branded device, but I have a pile of Insignia branded ones.  So this affects me more than most I imagine.

Well, the chumby classic has quit playing pandora when left playing overnight, twice now.

A couple days ago I saw the "still listening" prompt, but not yesterday or today, it was back playing space clock, which is the only widget in the channel.

I think this is digressing. 

As I said before the Infocast 3.5 quits in about 90 minutes now.  When I started this thread it was much longer, but not anymore.  60-90 minutes.

And I left the I3.5 playing pandora about 5 hours ago, I just returned and it was playing space clock.
So I dunno.

Any progress on this? 
This is getting really annoying. 
Pandora played without issue for months before the relaunch.

Sorry, no progress on this.

The weird thing is that you're saying it's getting worse, when nothing has changed, either on the server or the client.

The other weird thing is the difference between the behavior of I3 vs C1, which are pretty much identical devices - there's a minor revision of the main board, but the firmware is identical.

The Pandora player code, both on the server and the client, is the same code that was running before the relaunch.

Here's something to to try...

Create a new account on the server, and deregister your device from your current account and re-register it to the new account.  Since this new account will not be subscribed, so it should behave pretty much like the system did before the relaunch - a single clock.  See if that fails.

I'm wondering if this could be a TCP port reset issue (NATting router dropping the connection?) and the app failing to reconnect properly...

I have the same I3.5 in a new, unsubscribed account, to which I was just able to add a channel.

I should not have been able to do that, I thought.  The idea of being subscribed is so you can add channels.

I just checked, and I am indeed logged in to the unsubscribed channel.  Somehow, someway, I am logged in as subscribed.

A default channel is present in the account, as well as a test channel containing only space clock, and another Days Test channel that I just created with 4 widgets.

OK, I just rebooted the chumby and it now says unsubscribed. 
So even though I was able to add channels on chumby.com they are not on the device.  I get it now.

It's playing Pandora unsubscribed again.

Maybe unsubscribing should delete those settings, which are actually personal information.

Widget subscription is completely optional and not required to use music, so unsubscription should not clear those settings.

The more reasonable thing would be deactivation, however, the device itself is not involved in the deactivation process, and once that's done, the server can no longer communicate with the device. We don't keep *any* music settings, including credentials, on the site, so there's nothing there to clear upon deactivation.

The only way to address this would be for the Control Panel to clear music credentials when it finds itself deactivated upon the next attempt to authenticate - however, since Pandora is actually a plugin module, the Control Panel theoretically has no knowledge of how and where Pandora stores the credentials.  In practice, however, since the music subsystem is pretty static at this point, it might make sense to hard code specific support for clearing of Pandora credentials under these circumstances.  The downside is that if you had a temporary network disruption that somehow caused the CP to think the device is not activated, then the credentials might get incorrectly deleted.

In general, though, someone planning on passing their device onto other people should do a factory reset, just as they should when disposing of a phone.