Skip to content

Dirk Mittler's Blog

A Journal of my Ongoing Experiences.

-6°C
Wind: 4km/h ESE
Cloudy
Humidity: 79%
Montreal, according to OpenWeatherMap
Sat
-15°C
Sun
-13°C
Mon
-13°C

Weather Widget by interconnect/it

During bad weather, this site can go down. If it does, please try again later.

This Is A Log File of the IP-Address inconsistencies, that followed from down-time, since March 20, 2019, Or, of the last 500 hours of known IP-Addresses.

Tags

  • Android
  • Apache
  • Computer Algebra
  • Custom-Compile
  • DCT
  • Debian
  • Debian 9
  • Debian Stretch
  • Desktop Compositing
  • Downtime
  • DSL Problem
  • Future Downtime
  • GPU
  • HBS-750
  • IPv6
  • Kanotix
  • KDE
  • Kernel Update
  • Linux
  • Linux Laptop
  • memcached
  • MOSFET
  • MP3 Compression
  • MySQL
  • NG-SPICE
  • OpenCL
  • OpenGL
  • Pixel C
  • Plasma 5
  • Power Failure
  • PulseAudio
  • Quantum Mechanics
  • Reboot
  • RTL8723BE
  • Samba
  • Sound Compression
  • Source Code
  • Successful Update
  • System Update
  • Unattended Upgrades
  • Update
  • WiFi Disconnects
  • WiFi Problem
  • WordPress
  • X-Server

Most Directly-Viewed, Individual Posts

  • One reason Why, It is Difficult For Me to Guess, at the Variable-Length Encoding of numbers, Chosen By Other People (7,181)
  • Testing the Focusrite Scarlett 2i2 external sound device, with my Samsung S6 Smart-Phone (4,691)
  • My Experiences with the Bell Home Hub 3000 (4,539)
  • I can offer a sound-compression scheme that I know will not work, as a point of reference. (4,277)
  • How DynDNS Works (2,640)
  • I now have Linux installed on my Samsung Galaxy Tab S. (2,088)
  • Getting Pulseaudio to schedule real-time threads under Debian / Stretch and beyond. (2,045)
(Hit Counters Installed March 5, 2016)

Recent Posts:

  • Power Failure Today, Downtime
  • Samsung’s Auto Hot-Spot Feature
  • How to route a USB MIDI Keyboard to a JACK-MIDI Input, under Debian.
  • How to compute the sine function, on a CPU with no FPU.
  • About testing a subwoofer with open-source software, and some inadequate skills in music.
  • ChromeOS Upgrade from Debian 9 to Debian 10 – aka Buster – Google Script crashed.
  • Garmin fenix 5x auto-update stuck at 50%.

Recent Comments

  • Power Failure Today, Downtime | Dirk Mittler's Blog on How DynDNS Works
  • An observation about the new Chrome OS Smart-Lock and Instant Tethering features. | Dirk Mittler's Blog on Samsung’s Auto Hot-Spot Feature
  • Samsung’s Auto Hot-Spot Feature | Dirk Mittler's Blog on An observation about the new Chrome OS Smart-Lock and Instant Tethering features.
  • Dirk Mittler on I now have Linux installed on my Google Pixel C tablet.

Archives

Categories

Pages

  • A Repository Of WebGL Creations
  • A summary of my Site
  • About the Dates / Modification Time-Stamps
  • About The Translations – And The Missing Pieces Of Text
  • Binaries – Executable
  • Communication Through Entanglement?
  • Permalinks
  • Posting Comments
  • Sample Artwork Made With FOSS
  • Some Nastiness that had taken place, with my Blocks Of Code
  • Submit Feedback
  • The Most Directly-Viewed, Individual Posts
  • The Superfluid Fountain
  • Viewing The Equations On My Site

Feedback Form:

Open Feedback Form

Meta

  • Log in
  • Entries RSS
  • Comments RSS
  • WordPress.org

Tag: Account Sync

Why Android Devices Consume More Power, Until They Are Rebooted

One of the many misconceptions which people have about Android, is that it is another flavor of Linux, because it uses the Linux kernel. Android is not Linux, and for that reason, also does not have ‘‘. is a Linux daemon, which allows for the background scheduling of services, that are kept in non-volatile memory. Android does not have this.

The background scheduler which Android uses, is based 100% in volatile memory. What this means is that a given app needs to have run at least once in any given session – i.e. since the last reboot – in order to place an ‘Alarm’ in the background scheduler, for itself to be woken again, according to the clock of the Android device.

This fact can confuse people, because additionally, certain apps have it as their privileges, that a part of themselves should be run once, when our Android device first boots. I.e., if the programmer decides that his app should run in the background, even if a user has never launched it, then he must first arrange to have a part of that app run once, every time the device boots, so that that part of the app can register scheduled re-awakenings of itself afterward.

But what that also means, is that if a user has 200 apps installed as I do, only some small subset of those are set to run when the device is rebooted. Facebook and Twitter happen to be among those. But after that, as I run more and more of my apps in a given session, more and more alarms get registered, so that the device is in standby potentially less and less, and so that my battery consumption also gets worse.

Further, many people like for their apps to give them push notifications. Well, as we run these additional apps, they also re-register with whatever server they are supposed to receive push notifications from, which means that the apps are receiving more push notifications as the session continues. And then our CPUs stay in low-power mode for less and less time.

So it is a good idea, to reboot our devices from time to time, for a number of reasons, not just for the reason I explained here.

Also, Android has a separate list of Accounts, that are specifically listed in the System Settings. Android will make sure when it boots, that all the accounts there which are set to sync, are in fact registered. A longer list of accounts also means greater battery consumption. In fact, I am sure that Android will periodically rescan the accounts there, to make sure that their connection to the server is ‘alive’, as our device disconnects from and reconnects to the network.

Dirk

 

Posted on December 22, 2016December 22, 2016Tags Account Sync, Alarms, Android, Android Accounts, Battery Consumption, cron job, Linux, Non-Volatile, Push Notifications, Reboot Phone, Scheduled Execution, Scheduler, Volatile1 Comment
Proudly powered by WordPress