They should not be worried, they should be educated.

If you worry a new user enough they’ll go back to Windows or Apple because there’s less scary warnings there.

We need to make the transition as pain free as possible. Learning about the joys of kernel compilation and SELinux can come later.
The first step is "Hey, this is as usable as Windows, without stupid ads in the start menu.

Sounds quite similar to Markov chains which made me think of this story:

https://thedailywtf.com/articles/the-automated-curse-generator

Still gets a snort out of me every time Markov chains are mentioned.

Yeah, inductive charging is basically a must.

Especially because it eliminates the guesswork if the watch is correctly seated to charge

Oh, they’re putting a lot of thought into it I’m sure.

That thought being “Money, Money, Money, Profit, Profit” of course.

No actual technical solution here, but it smells slightly of XY-Problems.

From what you described it seems the main issues are

• too many calls
• not knowing who’s calling
• not wanting to answer the phone
• not reaching the phone in time

Maybe you could look into solutions like setting a custom ringtone for important callers or having the phone announce caller names so your mother can decide if she wants to make the effort to get her phone.

I’m speculating a bit here but I can imagine that getting up and answering the phone is exhausting for your mother. Also if her mindset is " a ringing phone means it’s important" that could make it even more stressful.

Maybe you could find a way to let her silence all calls except caregivers and ICE contacts. (On Android DND exceptions could work for that)

That way she doesn’t feel pressured to answer the phone every time it rings and stays reachable.

If it’s actually just the physical issue of reaching the phone in time, does she have a convenient way to carry the phone indoors like a lanyard?

Hope some of this helps you

There should be an external hard drive full of portable game installs in some drawer that fits the time period.

Should easily kill a week.

Coconut at least…

That feature is right on the border between real neat tech and deeply unsettling.

“Hey, my phone uses its last few electrons to turn into a bluetooth beacon to stay findable” sounds like sci-fi “reserve power emergency mode”

“I can’t turn off the locator chip in a device that holds half my life and memories” is just dystopian.

I’m wondering if there would be a way to keep it useful while minimizing impact for people who stay off the grid. A hardware switch would probably be a good start but they won’t fly with current all-touch designs.

Ah, you “work” in “marketing”?

B stands for Billion (Parameters) IIRC

To a certain degree, yes. If someone at Google decides to wage all-out war against ad blockers they have a good chance. But if that costs more money than it generates, odds are that someone will stop it. Google / Alphabet is publicly traded after all and that means profit above all else.

Embedding ads into the stream would be hard to counter, but it’s far away. That would invalidate caches along the way and need extra performance to reencode the stream with the ads inserted.

That’s extra costs that are hopefully orders of magnitude above the lost ad revenue from ad blockers

Okay, you got me there. In all fairness, as instruction videos go, that one is on the tame side.

Thanks for posting the instructions here.

Tl;dw:

Append systemd.debug_shell to the boot command line.

Yeah there are multiple duplicates.

First AI in public office in 42 and 43

I’m hopeful that reencoding on the fly or even merging preencoded files into a single stream is too expensive because it needs a lot of compute power and invalidates caches .

I built a custom app to do it since I couldn’t manage to fire the relevant intents from an adb shell without root.

I lifted the code from AAAD

Specifically the InstallAPK method in MainActivity.java

Intent intent;

            if (Build.VERSION.SDK_INT >= Build.VERSION_CODES.N) {
                intent = new Intent(Intent.ACTION_INSTALL_PACKAGE);
                intent.setData(getUri(file));
                intent.setFlags(Intent.FLAG_GRANT_READ_URI_PERMISSION | Intent.FLAG_ACTIVITY_NEW_TASK);
            } else {
                intent = new Intent(Intent.ACTION_VIEW);
                intent.setDataAndTypeAndNormalize(Uri.fromFile(file), "application/vnd.android.package-archive");
                intent.addFlags(Intent.FLAG_ACTIVITY_NEW_TASK);
            }

            intent.putExtra(Intent.EXTRA_NOT_UNKNOWN_SOURCE, true);
            intent.putExtra(Intent.EXTRA_INSTALLER_PACKAGE_NAME, "com.android.vending");
            getApplicationContext().startActivity(intent);
        } 

Basically you construct an Intent ACTION_INSTALL_PACKAGE with data pointing to the APK file and the extras EXTRA_NOT_UNKNOWN_SOURCE=true and EXTRA_INSTALLER_PACKAGE_NAME="com.android.vending" which tells the installer that this APK is not sideloaded and it’s the play store asking to install it.

You might still need to enable unknown sources in Android Auto developer settings (separate from phone developer settings).

If I remember, I’ll try to pull the code for my app from my PC and post it.

The problem is that android auto is restricted to apps installed from the play store.

The F-Droid Version supports Android Auto, but it’s blocked by Google.

I managed to enable it by spoofing the installer-package during installation.

For me, the navigation is near unusable. Location tends to lag behind by a few seconds when running on Android Auto. On my phone it’s fine.

IT changes usually affect management as well, while “cost saving” in production doesn’t.

Stopping AWS instances would be handy, but your idea to slag the drives is unnecessary.

Just set up full disk encryption for everything.

You die -> no key -> no data