threshold : 0, // You can set threshold on how close to the edge ad should come before it is loaded. Default is 0 (when it is visible).
forceLoad : false, // Ad is loaded even if not visible. Default is false.
onLoad : false, // Callback function on call ad loading
onComplete : false, // Callback function when load is loaded
timeout : 1500, // Timeout ad load
debug : false, // For debug use : draw colors border depends on load status
xray : false // For debug use : display a complete page view with ad placements
console.log(“error loading lazyload_ad ” + exception);
It’s not exactly news that Android upgrades almost always take a lo-o-o-o-o-ng time to roll out to most users. As in months. Often, many months. Sometimes more than a year.
(There is an exception: Google delivers new versions of Android to its Pixel line right away, and did just that with the release of Android 9.0 (Pie) last fall.)
It’s now been six months since Pie arrived, which means it’s time for Computerworld blogger JR Raphael’s comprehensive look at how device-makers are doing when it comes to upgrades.
Raphael joined Computerworld Executive Editor Ken Mingis to go over the findings, as well as discuss how Google’s Project Treble is working. Treble is the company’s answer to slow update rollouts; it’s designed to streamline the process as much as possible to help the hardware folks push out updates quickly.
(Spoiler: Project Treble doesn’t seem to have helped much.)
Raphael then rounds out the discussion with insights into why Android upgrades are so important.
For an audio-only version of this episode, click play (or catch up on all earlier episodes) below. Or you can find us on iTunes or Pocket Casts, where you can download each episode and listen at your leisure.
Happy listening, and please, send feedback or suggestions for future topics to us. We’d love to hear from you.