The Successful Use of ADB Drivers, to Enable Automation of Power-Saving, on my Samsung S6 Smart-Phone

I happen to be a long-time user of this app, which exports shortcuts to the Android system, which together with this app, allow for the automation of power-saving mode, by way of .

Until recently, this phone still had on it, which meant that the power-saving app was able to toggle power-saving mode without requiring special permissions. However, since my upgrade to on the phone (), this permission is no longer granted. And so I needed to grant access to the power-saving app, to restricted settings on the phone, via .

Today was the first time I ever used the on my Linux laptop named ‘‘.

Continue reading The Successful Use of ADB Drivers, to Enable Automation of Power-Saving, on my Samsung S6 Smart-Phone

The Newest Dropbox version seems to follow Linux Power-Saving Behavior.

As of an earlier posting, I had “Dropbox” v3.16.1 running on my KDE-4 Linux desktop. This version has updated itself to v3.18.1 . Additionally, I have this Dropbox client installed and idling, on the Linux laptop I name ‘Klystron’.

I see one significant new behavior. When I have left my laptop idle, with the screen turning off, the little Dropbox icon changes to show that it has dropped its connection to the Dropbox server. This is similar to behavior which my “Pidgin” IRC client has shown, and seems to suggest, that there are power-saving measures in place on up-to-date Linux desktop managers, which certain applications may opt to use.

The ‘KDE’ desktop manager has in common with ‘GNOME’, that both now use ‘DBUS’ as their inter-process communication system. So what works under GNOME, will frequently also work under KDE when properly set up.

But the fact that both Pidgin and Dropbox seem to do this on my laptop, means that I do not have to keep looking as hard as before, for causes within the kernel module of my laptop WiFi, for possible connection issues. In both cases, the software seems to reconnect to its server, as soon as I have unlocked my screensaver.

Unlocking the screensaver is an event, which a kernel module usually does not recognize.

(Edit 04/17/2016 : ) One way in which such a power-saving mode would make sense however, is that the Kernel can recognize it, and can give the software command to the Kernel Module, to turn off its antenna as well. However, according to This Posting, I have forbidden the KM from following such a command, such that the antenna does not switch off.

Depending on what software we have installed, simply having the WiFi turn off, can cause problems.



A Realization About Samsung S6 Power Saving Access

In a previous posting, I had remarked that the (famous) “Tasker” app has a 3rd-party plugin named “Secure Settings”, which has a sub-section named “Samsung ROM”, under which there is a function named “Enable / Disable Power Saving”.

The general context of this is, that Tasker is a task Acceleration / Automation tool, in which each Task is defined as a sequence of Actions, many of which are built-in, but some of which are Actions defined by 3rd-party plugins, such as by ‘Secure Settings’. Hence, it was a goal of mine to insert the Action into a Tasker Task, which would turn the Power Saving Mode on, on my “Samsung Galaxy S6″ phone.

I am Not Rooted.

This failed every time, and at first I thought the reason would be, that the author of ‘Secure Settings’ had failed to keep his module up-to-date with the latest Android Lollipop version, which my S6 is running.

But then another observation came to my attention.

The app “NFC Tools Pro”, and its companion, “NFC Tasks”, is also supposed to support, that an NFC Tag should enable Power Saving Mode on a Samsung Phone, when we tap the Tag. ‘NFC Tools Pro’ additionally has a mode in which it executes its Task as a test, before that Task has even been programmed into a Tag. And when I ran the test, this app was also unable to switch on Power Saving Mode.

In both cases the behavior is identical, in that the Action returns as a ‘success’ immediately (even though when I Enable Power Saving manually, it takes several seconds for this setting to kick in), but in that Power Saving Mode is not enabled – even later.

And so an inference which I am making about this feature, is that indeed the app developers are not up-to-date with the latest Samsung API – Only Because on the latest phones, one needs to be rooted in order for this command to work (!)

And so what I ended up doing both as an intended, future NFC Tag Task, and as a present Tasker Task, was simply to script a pop-up to appear, which states “Suggest to Enable (or Disable) Power Saving Mode Now.” It is a shame, that the whole procedure cannot be 100% automated, but I guess that Samsung has been very conscientious in its efforts to increase security. And denying ‘any old app’ permission to fiddle with the power settings in general, could be a step towards greater security.