Dashclock

---

Hey I have epinter's CM 10.1 installed but somehow can't access the dashclock widget from the playstore. Can anyone advise?

Originally Posted by ravanne

Hey I have epinter's CM 10.1 installed but somehow can't access the dashclock widget from the playstore. Can anyone advise?

I've just had a look at this and have got it on mine with Epinter's rom.

Download and follow the instructions on the page https://play.google.com/store/apps/d...oman.dashclock
When you have swiped across and you can see the Dashclock window, press and move it to the right and it will move stock lockscreen over and your Dashclock widget will become your primary (all you are doing in effect is merely replacing one 'lock' screen with another (rather like the home screens)
Hope that helps.

Originally Posted by barry_

I've just had a look at this and have got it on mine with Epinter's rom.

Download and follow the instructions on the page https://play.google.com/store/apps/d...oman.dashclock
When you have swiped across and you can see the Dashclock window, press and move it to the right and it will move stock lockscreen over and your Dashclock widget will become your primary (all you are doing in effect is merely replacing one 'lock' screen with another (rather like the home screens)
Hope that helps.

It's not so much as not knowing how to use it on my phone as the playstore rejecting the rom as incompatible to the widget app...

Originally Posted by ravanne

It's not so much as not knowing how to use it on my phone as the playstore rejecting the rom as incompatible to the widget app...

Check the screen resolution settings in your build.prop

EDIT: This problem occurred in the previous release by epinter. He fixed it with the latest release. You may consider updating.

Originally Posted by dedebekri

Check the screen resolution settings in your build.prop

EDIT: This problem occurred in the previous release by epinter. He fixed it with the latest release. You may consider updating.

I already updated to the latest rom, for some reason it just took playstore a while to recognize it as 4.2. But consider this case solved. Thanks.