SufficientlySecure / birthday-calendar

Display all contact birthdays automatically in your standard Android calendar.
https://www.schuermann.eu/android/
GNU General Public License v3.0
94 stars 28 forks source link

birthday adapter has to be restarted manually on samsung s4 s3 note 2 #61

Closed dschuermann closed 11 years ago

dschuermann commented 11 years ago

Original author: wkase...@gmail.com (June 03, 2013 13:30:42)

What steps will reproduce the problem?

  1. Start birthday adapter app
  2. Restart phone
  3. Birthday adapter must be started manually

What is the expected output? What do you see instead? I expect the app to start automatically, as it does with the nexus phones. However, with the samsung galaxy s3, s4, note 2, it has to be started manually.

What version of the product are you using? 1.14(15) On what operating system? Android 4.1* and 4.2.2 but this is in 4.2.*

Please provide any additional information below.

Original issue: http://code.google.com/p/birthday-adapter/issues/detail?id=59

dschuermann commented 11 years ago

From domschuermann@gmail.com on June 03, 2013 13:43:24 Could you please try the Jelly Bean workaround: https://play.google.com/store/apps/details?id=org.birthdayadapter.jb.workaround

I know, it's a workaround for 4.1, but I heard that Galaxy phones have this problem also on 4.2.

Please report back if it works or not. Thanks

dschuermann commented 11 years ago

From wkase...@gmail.com on June 03, 2013 17:00:53 Do I uninstall my existing app? Does this need to have the purchased app to work?

dschuermann commented 11 years ago

From domschuermann@gmail.com on June 03, 2013 17:12:06 The whole problem I thought of only happens with the installed version. When you have the version from FDroid or the free version from Google Play. Then this is a new bug

When you have the purchased full version from Google Play, install the workaround additonally to this app.

dschuermann commented 11 years ago

From wkase...@gmail.com on June 03, 2013 19:22:06 The work-around seems to solve the issue. Thanks!