Hey everyone,
I wasn't sure where to submit these 2 bugs that I found with the currents daydream screensaver. So I figured I'd start here and see if anyone else was coming across these as well.
I love the Currents daydream screensaver, in fact, I switched back to currents from flipboard in order to use it. Sometimes I like to discover news serendipitously (which daydream now allows for) and use pocket to read it later, and sometimes I like to hunt the news down in the feeds (through the Currents app interface). But if I use daydream, and open up a story, unless I remember to close it completely, it prevents new stories from opening up. So, more specifically, while at my desk with the Nexus 7 on it's dock, I:
1) Click on story A from the daydream screensaver and select "open in google currents"
2) Unlock screen (this is bug #2, will get into it later)
3) Open up story in a sort of preview view with "Done" and "Open Edition" buttons along the bottom. In order to then read it later with Pocket, I then select "Open Edition" and then share it with Pocket. Because this takes a while, I then turn back to my work and ignore it all together. Meanwhile, the currents app is still open, but it was started from that "preview" process, which, being a child process of it, still is open in the background somewhere.
4) time passes, I see another story to read later, story B, I click it and do the same as steps 1 and 2
5) however instead of going to the new story, the original story A opens up again because I forgot to close it entirely. I feel the desired behavior in this case should be just like web browsers where even if something is already open, you can still open up an additional process or just navigate away from story A and onto story B. Like I said before, this is mitigated only if I remember to close all the processes/stories that I opened in step 3.
So that's bug #1, bug #2 is as follows:
I have my nexus 7 encrypted, so I have the pin password set to a VERY long pin for security purposes. Having to enter it in more then I need to is very annoying. So I have my screen sleep set to 1 minute (which is a good balance for reading/battery saving purposes) but my screen auto-lock set to 10 minutes. This is a perfect timing for me because I tend to either check or use my Nexus on my desk within that 10 minute period, therefore never needing to use that screen lock because it is constantly reset. Then when I'm out and about, I tend to use it in frequencies longer then 10 minutes, so it locks more often. HOWEVER, since using the currents daydream screensaver, it actually ignores my system settings and automatically locks the screen 1 minute after the screen sleeps (ie. 2 minutes after innactivity starts) instead of after 10 minutes as I selected in the system settings. Very annoying.
If anyone else has any ideas for fixing this unnoficially or where to submit a bug report, it would be much appreciated. Thanks,
I wasn't sure where to submit these 2 bugs that I found with the currents daydream screensaver. So I figured I'd start here and see if anyone else was coming across these as well.
I love the Currents daydream screensaver, in fact, I switched back to currents from flipboard in order to use it. Sometimes I like to discover news serendipitously (which daydream now allows for) and use pocket to read it later, and sometimes I like to hunt the news down in the feeds (through the Currents app interface). But if I use daydream, and open up a story, unless I remember to close it completely, it prevents new stories from opening up. So, more specifically, while at my desk with the Nexus 7 on it's dock, I:
1) Click on story A from the daydream screensaver and select "open in google currents"
2) Unlock screen (this is bug #2, will get into it later)
3) Open up story in a sort of preview view with "Done" and "Open Edition" buttons along the bottom. In order to then read it later with Pocket, I then select "Open Edition" and then share it with Pocket. Because this takes a while, I then turn back to my work and ignore it all together. Meanwhile, the currents app is still open, but it was started from that "preview" process, which, being a child process of it, still is open in the background somewhere.
4) time passes, I see another story to read later, story B, I click it and do the same as steps 1 and 2
5) however instead of going to the new story, the original story A opens up again because I forgot to close it entirely. I feel the desired behavior in this case should be just like web browsers where even if something is already open, you can still open up an additional process or just navigate away from story A and onto story B. Like I said before, this is mitigated only if I remember to close all the processes/stories that I opened in step 3.
So that's bug #1, bug #2 is as follows:
I have my nexus 7 encrypted, so I have the pin password set to a VERY long pin for security purposes. Having to enter it in more then I need to is very annoying. So I have my screen sleep set to 1 minute (which is a good balance for reading/battery saving purposes) but my screen auto-lock set to 10 minutes. This is a perfect timing for me because I tend to either check or use my Nexus on my desk within that 10 minute period, therefore never needing to use that screen lock because it is constantly reset. Then when I'm out and about, I tend to use it in frequencies longer then 10 minutes, so it locks more often. HOWEVER, since using the currents daydream screensaver, it actually ignores my system settings and automatically locks the screen 1 minute after the screen sleeps (ie. 2 minutes after innactivity starts) instead of after 10 minutes as I selected in the system settings. Very annoying.
If anyone else has any ideas for fixing this unnoficially or where to submit a bug report, it would be much appreciated. Thanks,
Facebook
Twitter
Instagram