Pandora widget not functional in the lockscreen

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Place pandora widget into the Widget Setup screen while pandora is 
playing. This causes the proper playback updated widget to be created
2. Exit the widget setup or view the lockscreen itself

What is the expected output? What do you see instead?

The pandora widget goes back to blank state, the state pandora gives it 
for when the widget is added before the account is logged in or before any 
playback station is started. I believe the cause of this issue is twofold

1- Pandora is allowing a local service to spawn in the individual widget 
instance, which connects to the playback service at time of create.
2- The homescreen isn't typically closed down and recreated very often, if 
ever in the stock Launcher. The lockscreen is typically closed down when 
exited, and recreated at sleep. 

The end result is that a local service being spawned inside the widget 
view, to bind back to the playback service to determine what is/was 
playing (this is per the widget tutorial from google in which they spawn a 
local service to retrieve a word of the day update in the example widget). 
This is not a good idea for a music playback widget which will have 
frequent changes. It is not noticed by most users since the stock Launcher 
isn't closed down very much, however it causes the widget to break in our 
lockscreen environment. 

Pandora could fix this issue by implementing a more appropriate remote 
service to call update out to the widget. This remote service would not be 
destroyed when the lockscreen is exited, whereas the currently implemented 
local service IS destroyed when that widget's view is destroyed at 
lockscreen close. The service doesn't get recreated until the time 
interval widget update happens. This must be in place to resolve the blank 
widget after a device reboot. I am going to notify pandora of this 
solution suggestion.

Please use labels and text to provide additional information.

Original issue reported on code.google.com by myLockan...@gmail.com on 5 Apr 2010 at 9:14

[GoogleCodeExporter]

To clarify, I cannot fix this in our code.

The only fix would be to keep the lockscreen process running but only minimize 
it 
when exited.

This is a very bad idea because it will interrupt the app history as you are 
pressing Back to peel back screens, you would land at the lockscreen when it is 
not 
applicable or useful.

Prior to implementing widgets I tested the various approaches to closing or 
only 
minimizing the replacement lockscreen and found that it has to be closed at 
exit to 
avoid this type of stability issue.

Original comment by myLockan...@gmail.com on 5 Apr 2010 at 9:22

• Changed state: Invalid

[GoogleCodeExporter]

By started I mean I will contact Pandora armed with Logs.

Original comment by myLockan...@gmail.com on 5 Apr 2010 at 9:24

• Changed state: Started

[GoogleCodeExporter]

mylock custom lockscreen has been abandoned because the platform refuses to 
support SDK based robust lockscreen interaction or replacement

Original comment by myLockan...@gmail.com on 10 Feb 2011 at 8:22

• Changed state: Invalid