Explanations for Android 5 users…

Last few months I’m fighting with Android 5 support problem. The main reason of the problem is that Google totally broke the Silent mode functionality and API for developers (issue on bug tracker).

In two words on Android 5 you have only two options: total silent (in this mode even Alarm doesn’t work), priority mode (in this mode a lot of apps will still goes with sound, you can receive system menu sound, you can receive power plugin sound and so on). Google doesn’t give any comments about this problem.

I’ve tried different hacks and tricks, but it seams that I still have not found reliable solution. Some tricks works proper on one devices but break down all logic on others. Some tricks works from time to time.

I’m really sorry for this situation. It’s really not my fault that Google break down part of there system that works proper for years and was documented and supported API.

After all this weeks of research I have idea how to handle it in reliable way. I’m afraid that solution will have some restrictions but will be reliable and usable. Unfortunately it can’t work in exact same way as on Android 4.4 and earlier. I need week or two to implement and test this idea.

Android 5 users, keep in mind that Nights Keeper can work with defects on your devices now. I really sorry for that. And as I already wrote I’m working on solution. Be patient…

P.S. If you are Android 5 and Nights Keeper PRO user and you don’t want to wait until Nights Keeper fix then report me via bug report for refund.

P.P.S. If you are Android 4.4 (or earlier) user think twice before update to Android 5. “No Silent mode” problem is only top of iceberg…

P.P.P.S. We have chance that in Android 5.1 Google with bring Silent mode back. There are some information about it on web. Please, star issue on bug tracker it can help.

 

Mobile Network control and Android 5

I have a lot of questions about Mobile Network feature from Android 5 (Lollipop) user. I want to explain this situation for public.

The Mobile Network control API is deprecated for external app developers for years ago. But community found work around via system exploit. And it works for all versions starting from 2.2 and till 4.4. But in Lollipop Google fixed this system exploit. So, all apps that use this way to switch Mobile Network were broken.

Currently there is only one way to disable/enable Mobile Network. It’s APN modification. But it’s not acceptable for me, because it’s not safe (user can have problems with restoring Mobile Network after app uninstall) and it’s absolutely useless in terms of power save (your device trying to connect to not existing network and drilling the battery).

I’m apologise for this situation. I’m looking for solution. Before I’ll find it this feature will be hidden on all Android 5 devices.

P.S. Google had a lot of bugs in Lollipop. I’m continue to work on Nights Keeper compatibility. Look forward for updates.

Nights Keeper 2.4.0: Lollipop support

Google-officially-released-Android-5.0-Lollipop-source-code-into-the-AOSP-Details (1)

This release contains bug fixes and support of Lollipop (read more about proper configuration under cut). Unfortunately Mobile Network feature deprecated for Android 5.0 (hope that I’ll find solution later). And I’m happy to announce Hebrew localisation.

Change log:

  • NEW: Android 5.0 support (fix all known problems).
  • NEW: Hebrew localisation.
  • FIX: Muting ringtone by volume button on Moto.
  • FIX: Mobile Network features duplicated for Android 5.0.

Get it on Google Play

 

Continue reading Nights Keeper 2.4.0: Lollipop support