Sunday, July 15, 2018

Delivery Optimization

After my installation of Windows 10 April 2018 Update I went to Settings / Storage just looking for how much space was used by the backup copy of Windows.

But I got distracted...


I clicked on "Free up space now".

As it was scanning the entry for "Delivery Optimization Files" caught my attention with over 2 GB.


What are "Delivery Optimization Files"?

From Microsoft (archive.is)
Windows Update Delivery Optimization works by letting you get Windows updates and Microsoft Store apps from sources in addition to Microsoft, like other PCs on your local network, or PCs on the Internet that are downloading the same files.
So, how well is it working? Go to Settings / Delivery Optimization.

I always set it to "Allow downloads from other PCs" but only check "PCs on my local network".

Then click on "Activity monitor" to see what it's doing.


While I started on this journey on a PC that had just updated to Windows 10 April 2018 Update, I went over to a PC that hadn't updated to get representative numbers.


This PC is the only one Ethernet connected to the Internet. 2/3s of the Windows Update data came from Microsoft and 1/3 came from other PCs on the local network.

But further, this PC provided over 1 GB of Windows Update data to other PCs on the local network.

Interesting.








Sunday, July 08, 2018

Android Messaging, Part 2

I hadn't even gotten my Android Messaging post published before everything changed.

Inexplicably, AT&T Messages had started working again. Pulse was working great.

Then Google changed the world.
Google launches Android Messages on PC so you can text from your computer - as it looks to take on WhatsApp
This has 90+% of the function of Pulse for free and delivered by Google, not a third party.

The web presentation is way more Material Design than Pulse but I thought Pulse was fine.

Messages for Web doesn't have scheduled messages and I've used them a couple of times. I'll miss them but will trade them for an integrated solution.

I had trouble getting the Android Notifications working like I wanted but that may just be my unfamiliarity with Android 8.1 Oreo notifications.

The web presentation is a little more chatty than Pulse in that it asks you if you want to run Messages for Web if you have it open in more than one place.

If you have an active web presentation you don't get the notification on the phone. That's problematic when you have been using the web presentation and then walk away from the PC. It seems to take a couple of minutes (5?) before it will resume sending notifications to the phone. The messages get delivered to the phone just without notification.

The Android Messages client generates battery warning messages now and then that you can turn off and the web presentation reminds you that the phone is not on Wi-Fi. That's easy to turn off as well.
How to set up Android Messages on PC
  1. Go to the Google Play Store and update or install Android Messages to the latest version
  2. Head over to messages.android.com on whichever PC or laptop you want to text from. You'll be greeted with a massive QR code.
  3. Open up the Android Messages app on your phone.
  4. Tap the three vertical dots on the right hand side and find the "Messages for web" option
  5. Tap the "Scan QR code" option and point your phone's camera at the QR code in the browser window.
  6. Your phone will buzz with a vibration and you'll be all set up and ready to go. Your conversations will show up on the left hand side of the browser window.
      https://www.mirror.co.uk/tech/google-launches-android-messages-pc-12757484
There's really lots more in this latest update of Messages. Read it all here.

Now I just wonder when Google will kill this.

PS. I'm not sure about Android Messages for Web. Since I've purchased the lifetime subscription for Pulse ($10.99) I've gone back to Pulse until I can sort out Android Messages for Web.

Sunday, July 01, 2018

Android Messaging, Part 1

I have been using AT&T's messages.att.net for months. It worked well.

But then in January 2018 I got the following text message:


I called AT&T and they said to ignore it. That was wrong.

I started getting this response to https://messages.att.net:


After literally months of calls to AT&T their story was that they have discontinued this service except for non-phone devices, e.g. tablets and watches. Another story was that it only ever worked for AT&T branded phones. But we know different, don't we?

So I went off on a quest for alternatives.

I first tried Join. Here's a brief write-up on it.

I thought it was an interesting implementation. It uses your Google Drive as a place to store the text messages. It runs an app on the phone that watches the Google Messages app and sends the data to your Google Drive. Then I used Join's web version to view the text messages. In addition to the web presentation Join offers a Chrome extension and a Windows 10 app (paid).

The web version has a 60 second timer between updates and often paints the messages out of sequence and omits messages. The web version doesn't support displaying MMS pictures yet. The author said he will have to add that in the future. In a group thread you can't tell who the author of an individual message is.

The other presentation methods may address these issues but I wasn't impressed.

The next app I found was Pulse. Pulse is simple and fast. Here's a good write-up on it.

Pulse installs a replacement app on your phone for Google Messages. I wasn't wild about that but it really works nice. By being the default SMS app the Pulse app gets instant visibility of text messages. The Google Messages app still sees all the messages so apps like SMS Backup & Restore still work.

The web version requires you to create an account with Pulse and login to it. For that you get instant visibility to your phone's text messages. All of the issues I had with Join were solved with Pulse.

Both Join and Pulse are paid apps. Both also require that your phone is turned on and connected to data and cellular networks.

Post script: Just for giggles I tried messages.att.net again. It worked fine. My history was empty (it only goes back 90 days) but otherwise it worked.

Nah, not going back.

PS. Don't do anything until you read Part 2 next week.