Force preload=none and disable autoplay on lowend Android devices.

third_party/WebKit/Source/core/html/HTMLMediaElement.cpp

Index: third_party/WebKit/Source/core/html/HTMLMediaElement.cpp
diff --git a/third_party/WebKit/Source/core/html/HTMLMediaElement.cpp b/third_party/WebKit/Source/core/html/HTMLMediaElement.cpp
index bd2144dfb9b901bed5592bb9e21165eedb07f9da..d4c641699e3b771abe95170f517045a65434594b 100644
--- a/third_party/WebKit/Source/core/html/HTMLMediaElement.cpp
+++ b/third_party/WebKit/Source/core/html/HTMLMediaElement.cpp
@@ -2003,7 +2003,7 @@ WebMediaPlayer::Preload HTMLMediaElement::preloadType() const
 {
     // Force preload to none for cellular connections or when data saver is explicitly set.
     if (networkStateNotifier().isCellularConnectionType()
-        || (document().settings() && document().settings()->dataSaverEnabled())) {
+        || (document().settings() && (document().settings()->dataSaverEnabled() || document().settings()->forcePreloadNoneForMediaElements()))) {

[foolip, 2016/09/19 13:58:54]

Makes sense, as long as it's OK that calling play() or seeking will start the
load.

[DaleCurtis, 2016/09/19 21:04:46]

Yes, this is fine since it's still relatively protected by a user gesture. When
we enabled Spitzer we brought in some automatic preload which is too much for
these devices, so this restores us to the pre-Spitzer state where the user has
to shoot themselves in their own foot instead of us doing it for them!

Still not great, but there's no guarantee with these older devices (even force
pausing and releasing the resources of the media is insufficient when the device
is in a near oom state).

         UseCounter::count(document(), UseCounter::HTMLMediaElementPreloadForcedNone);
         return WebMediaPlayer::PreloadNone;
     }