Enable DayDream Function

[GoogleCodeExporter]

Implementing DayDream support for the app, so for those who dock their device, 
relevant information could be deduced quickly.

*Bonus feature request: Also include an option within DayDream to additionally 
dim the display in the same way the default clock may.

Original issue reported on code.google.com by Noll...@gmail.com on 12 Feb 2013 at 2:01

[GoogleCodeExporter]

I'd like to also request this feature, daydream is really great with docked 
phones / tablets, and this widget is far better than the ones available today.

Original comment by stonedon...@gmail.com on 13 Feb 2013 at 8:36

[GoogleCodeExporter]

it should also fade out every minute and reposition itself at a slight offset, 
just like the default Clock daydream.

Original comment by eliseos...@gmail.com on 13 Feb 2013 at 11:19

[GoogleCodeExporter]

i also think displaying battery percentage within daydream would be a great 
option.

Original comment by aaron.sc...@gmail.com on 14 Feb 2013 at 2:41

[GoogleCodeExporter]

Issue 165 has been merged into this issue.

Original comment by roman.nurik on 17 Feb 2013 at 2:18

[GoogleCodeExporter]

what's the development status on this one? would be an awesome addition now 
that I use a Nexus 4 wireless charger. I wouldn't mind tackling it.

Original comment by m...@novie.co on 18 Feb 2013 at 11:56

[GoogleCodeExporter]

Hey Mike, I'm planning on working on this in the next couple of point release 
(1.6 or 1.7 maybe?). There are a lot of ways to go on this, and potentially 
customization steps, so I'd like to think about this a bit more before jumping 
in.

Original comment by roman.nurik on 19 Feb 2013 at 1:33

[GoogleCodeExporter]

I'd look into Clock Plus that is on Google Play. I'd love that functionality 
baked into DashClock. An important thing would be to have separate addons for 
the daydream.

For instance in the daydream I'd like to show battery status, but not on the 
ordinary widget, since I see it in the status bar anyway.

Original comment by fred...@duprez.org on 19 Feb 2013 at 6:08

[GoogleCodeExporter]

Separate dimming settings (i.e. Alpha value) should also be there since some 
people may use it on the night stand where the default setting might be too 
bright.

Original comment by mbi...@gmail.com on 23 Feb 2013 at 9:58

[GoogleCodeExporter]

Planning to begin working on initial Daydream support in the next few point 
releases (1.5? 1.6?)

Original comment by roman.nurik on 1 Mar 2013 at 6:37

• Changed state: Accepted

[GoogleCodeExporter]

Awesome, just came on to request this and see that you are already considering 
it!

Please make it as close to the stock clock daydream as you can (obviously with 
your dashclock style).

Original comment by lenn...@gmail.com on 7 Mar 2013 at 11:15

[GoogleCodeExporter]

Came here to ask for just this :)

Original comment by aziz.mansur@gmail.com on 11 Mar 2013 at 8:30

[GoogleCodeExporter]

Early look at the Daydream: 
https://plus.google.com/113735310430199015092/posts/B2MJdbgVc7j

Original comment by roman.nurik on 25 Mar 2013 at 4:00

[GoogleCodeExporter]

Thank for sharing the beta! Few minor remarks; the status bar in the top of the 
screen does not fully dissapear in daydream mode: clock and battery remain.
Also personally, i think the widget should stay in the center of the screen at 
least a few seconds before it starts moving to the side. The continous moving 
is a bit unnerving :)

Original comment by error...@gmail.com on 26 Mar 2013 at 5:12

[GoogleCodeExporter]

I agree with the above comment that clock and battery should be removed from 
the daydream. 

Configurable dim level is a must-have feature.

I would like to be able to configure extensions for daydream only - e.g. 
battery percentage.

Looking forward to this feature!

Original comment by fred...@duprez.org on 26 Mar 2013 at 6:06

[GoogleCodeExporter]

I'd also prefer to have the option for a larger, more prominent clock. I
use the Daydream function as a night clock at the moment so an easily
readable clock would be useful.

Original comment by blaster...@googlemail.com on 26 Mar 2013 at 6:49

[GoogleCodeExporter]

Seconded the adjustable brightness. I just tried it in my car and it's way too 
dim. 

Original comment by error...@gmail.com on 26 Mar 2013 at 6:53

[GoogleCodeExporter]

The movement of the clock is OK, but the clock shouldn't leave the screen. I 
have to wait to read the info too often.
Instead maybe a vertical movement could be nice.

Other wishes:
- Brightness setting (like others already said).
- Size setting (at least it could be a little bit larger)

Original comment by peterbo...@gmail.com on 30 Mar 2013 at 12:55

[GoogleCodeExporter]

Using the 1.5 Beta -- I dont think the System bar at the top should be visible, 
that info should be incorporated into the widget

having persistent elements may lead to screen burn in and stuff 

Original comment by 1jus...@gmail.com on 2 Apr 2013 at 2:27

[GoogleCodeExporter]

It seems like in DayDream mode, Dashclock is using more CPU than Clock or 
ClockPlus.  Granted, there are some plugins loaded (Plume, System Monitor, and 
Google Voice), but I see my endeavoru staying at ~340MHz with 80% CPU usage, 
versus with Clock where it is 51-102MHz most of the time.

I didn't look at the code, but maybe the constantly scrolling display could use 
some throttling?

Original comment by ScottE.S...@gmail.com on 2 Apr 2013 at 10:09

[GoogleCodeExporter]

At the beginning I've noticed, that my phone charges a lot of slower with DC 
than with ClockPlus. After removing the battery extension charging was OK 
again. So the CPU load clearly depends on the selected extensions. And I guess 
that System Monitor regularly refreshes its values and that's a killer for 
DayDream.
Maybe we need a separate setup for the DayDream function.

Original comment by peterbo...@gmail.com on 3 Apr 2013 at 9:52

[GoogleCodeExporter]

Marking as fixed, as this will be available in the next release and is 
currently in beta.

Original comment by roman.nurik on 10 Jun 2013 at 7:06

• Changed state: Fixed

[GoogleCodeExporter]

Original comment by roman.nurik on 12 Jun 2013 at 8:56

• Added labels: TargetRelease-1.5

[GoogleCodeExporter]

v1.5 has been published. Will take a few hours to propagate. Marking this 
feature/bug as closed.

Original comment by roman.nurik on 17 Jun 2013 at 8:26

• Changed state: Released

[GoogleCodeExporter]

Thanks! Seems to work very nice!

Original comment by wimp...@gmail.com on 19 Jun 2013 at 8:59