Moineauworld

Tag: sideloading

Pixel HiLight Unleashed by Indie App | Analysis by Brian Moineau

Posted on by Brian Moineau

TL;DR

  • Google’s Pixel 11 Pro HiLight is an RGB ring that, at launch in August 2026, only handles calls from favorites and a glow during Gemini chats; the open‑source HiLight Studio app by Dhananjay Bhosale adds per‑app rules, colors, and animated patterns like comet, pulse, and rainbow. [1][2][3]
  • The deeper story is policy: Google prioritized safety, supportability, and brand risk over openness, while an indie developer demonstrated a viable feature set with duty‑cycle caps and Shizuku‑based permissions. [1][2][8]
  • Expect a tug‑of‑war through late 2026 between user demand for per‑app signals and Google’s caution; that balance decides whether HiLight becomes Android’s “Glyph‑style” signaling layer or another Pixel curio. [3][7][8]

What the source said

Android Authority’s August 2026 write‑up confirms the Pixel 11 Pro’s rear HiLight LED only does two things out of the box: it pulses for calls from starred contacts and it glows during Gemini interactions; Google’s own help page limits official app eligibility to Phone and WhatsApp at launch on Pixel 11 Pro, Pro XL, and Fold. HiLight Studio, released as open source by Dhananjay Bhosale, adds per‑app notification triggers, custom RGB colors, and patterns (comet, pulse, rainbow), plus Quick Settings tiles and safety guards like auto‑dimming after 10 seconds and a global 5‑minutes‑per‑10‑minutes cap to avoid overheating or glare. Setup requires sideloading an APK and granting core permissions via Shizuku’s wireless debugging path, which the publication flags as non‑trivial for mainstream users. Once configured, the app worked as promised in testing, which raises the obvious question: why didn’t Google ship a comparable Settings surface or API at launch. [1][2]

Why it matters

Pixel 11 Pro buyers in 2026 are paying for novel hardware that behaves like a tech demo, as Google’s help page explicitly lists only Phone and WhatsApp support for HiLight and warns about interactions with Flash notifications and Do Not Disturb. That narrow scope means many owners will see just a couple of glows, which undersells a marquee feature introduced alongside the Pixel 11 family in August 2026. [2][3]

Google bears the liability and support burden in the U.S., EU, and elsewhere, and early reviews from Tom’s Guide call HiLight promising yet half‑baked during the critical post‑launch window. If a third‑party app can show safe, delightful use with built‑in caps and DND awareness, pressure shifts to Mountain View to provide an official path or cede the narrative to sideloaded tools maintained on GitHub and APKMirror. [8][1][5]

Original analysis

Pixel 11 Pro HiLight: control vs. openness (2×2)

  • Axes:
    • X: Platform posture — Controlled (Google/OEM‑only) to Open (Android SDK/API for 2026+ devices).
    • Y: Utility — Novelty to Daily driver for notifications across Phone, WhatsApp, Telegram, and more.
Example Posture Utility today Why it sits there
Pixel 11 Pro HiLight (stock) Controlled Low Only calls + Gemini; no general notification API or per‑app settings at launch. [2][3]
Pixel 11 Pro + HiLight Studio “Unofficially Open” Medium–High (for tinkerers) Per‑app rules, effects, presets; setup friction via Shizuku and sideloading. [1][6]
Nothing Phone 2 Glyph Semi‑Open Medium Reviewers described Glyph as “cool but underutilized,” despite more LED zones in 2023. [7]

Consensus in August 2026 says, “Open HiLight for everyone.” The contrarian read: Google’s caution is rational until Android formalizes an OS‑level contract with enforceable limits. Unbounded LED access risks glare, distractions in cars and theaters, and support tickets when apps misbehave, which echoes why HiLight Studio itself enforces a 10‑second dim and a five‑minutes‑per‑ten duty cycle because the array isn’t intended for continuous illumination. The right solution looks like a system service with caps, DND hooks, and user‑visible controls, not laissez‑faire access via notification listeners. [1]

Historical analogue: Nothing’s Glyph (2022–2023)

Nothing’s Phone 1 and Phone 2 showed there’s appetite for a back‑of‑phone light language, but novelty plateaued without deep system tie‑ins; TechRadar’s 2023 Phone 2 review called the Glyph interface “cool” yet “underutilized,” even after expanding LED zones and features like “Glyph Composer.” The lesson for 2026: unless Google wires notification semantics, DND precedence, and permissions into Android settings, HiLight risks the same “fun, then forgotten” curve. [7]

What an Android‑level “Notification Light Service” must include

  • A single runtime permission (“Use hardware notification light”) in Android Settings > Apps > Special access, with per‑app toggles, category granularity, and timeboxing; Google’s current doc already scopes eligible apps to Phone and WhatsApp and explains DND interactions. [2]
  • Enforced guardrails: maximum on‑time per interval, face‑down‑only behavior by default, and Quiet Hours/DND override; HiLight Studio’s 10‑second dim and five‑minutes‑per‑ten cap prove usable defaults that avoid heat and eye fatigue. [1]
  • Pattern safety: cap brightness and animation frequency, block seizure‑risk strobes unless the user opts in with a health warning, and require “attention‑grabbing” profiles to respect DND and Bedtime modes set in Android 14–18.
  • Clear precedence with camera flash and flash notifications; Google’s help page states Flash notifications disable HiLight for calls, so the framework must arbitrate conflicts deterministically. [2]

The punchline: Android can ship what HiLight Studio demonstrates, but as a first‑party framework that scales across Pixel 11 Pro, Pro XL, and Fold units shipping in 2026 while keeping support load predictable and brand risk contained. The third‑party app proves feasibility; the OS should institutionalize it with policy and tooling. [1][2]

Named-stakeholder breakdown

  • Google (Pixel hardware/software): Ship an SDK and policy this cycle or let enthusiasts define defaults via sideloading while mainstream reviews keep labeling HiLight half‑done in Q3–Q4 2026. [2][8]
  • Dhananjay Bhosale (developer): Clear PMF among power users on GitHub/APKMirror; if Google opens an API, he becomes the “Pro mode” client; if not, he owns the niche with first‑mover mindshare into 2027. [1][5]
  • App developers (Telegram, Signal, DoorDash, Uber): A sanctioned API would let them encode urgency by channel (e.g., calls vs. messages vs. deliveries) without accessibility hacks; few will support sideload‑only behavior.
  • Competing OEMs (Nothing, Samsung): Nothing can claim it pioneered light‑based signaling in 2022–2023, while Samsung could add a guarded API in One UI and pressure Google to standardize in AOSP. [7]
  • Users: Power users win now via Shizuku and sideloading; mainstream buyers on carriers like Verizon and EE remain limited to two stock behaviors until Google expands official support. [1][2][6]

What others are missing

The bottleneck is trust and distribution, not animation variety: HiLight Studio requires sideloading and Shizuku over wireless debugging, which triggers Play Protect warnings, ADB prompts, and re‑permission after reboots that many buyers on the Play Store ecosystem won’t accept. Android Authority flags the friction in its hands‑on, and Shizuku’s docs show the atypical setup path for granting elevated permissions without root. Until Google publishes a formal Android permission and a Play‑policy‑compliant API, every clever demo remains a niche for enthusiasts rather than something WhatsApp, Telegram, or DoorDash can support at scale in 2026. [1][6]

What to watch next

  1. By the November 2026 Pixel Feature Drop, Google expands HiLight beyond Phone and WhatsApp or adds a Settings surface for category‑level behaviors (e.g., Messages: Direct vs. Promotions), no sideloading required.
  2. By December 2026, Google publishes an Android 17/18 developer preview or AOSP change proposing a hardware‑notification‑light manager with enforced duty‑cycle caps and DND hooks.
  3. By Q1 2027, at least one major third‑party app (e.g., Telegram, Signal, Uber, or DoorDash) ships official HiLight support via a sanctioned API rather than an accessibility or notification‑listener workaround.

My take

Google should stop debuting delightful hardware like HiLight and then treating it as a lab toy through 2026. Either commit to a Notification Light Service with strict guardrails this year, or don’t ship the ring on the Pixel 11 line. HiLight Studio already demonstrates what users want—per‑app semantics, patterns, and quiet hours—while Google retains platform power to make it safe and boring by default. Ship the API, set conservative limits, and let the ecosystem paint within the lines; otherwise HiLight becomes another clever flourish reviewers dismiss and owners forget. [1][2][8]

Sources

  1. This app does with Pixel 11 Pro’s HiLight what Google should have done in the first place — Android Authority (https://www.androidauthority.com/google-pixel-11-pro-hilight-studio-3700860/) — Confirms stock HiLight limits, details HiLight Studio features, setup via Shizuku, and built‑in safety caps.
  2. Use HiLight to stay informed on your phone — Google Pixel Phone Help (https://support.google.com/pixelphone/answer/17455810?hl=en) — Documents official HiLight behaviors at launch (supported on Pixel 11 Pro/XL/Fold; works with Phone and WhatsApp; interactions with flash notifications and DND).
  3. HiLight on the Pixel 11 Pro has two features at launch — 9to5Google (https://9to5google.com/2026/08/12/pixel-11-pro-hilight/) — Corroborates that HiLight shipped with only two supported uses and explains Google’s framing of the feature.
  4. Pixel 11 Gets HiLight App That Does What Google Couldn’t — Droid‑Life (https://www.droid-life.com/2026/08/20/pixel-11-gets-hilight-app-that-does-what-google-couldnt/) — Independent confirmation that HiLight Studio adds per‑app notifications, effects, and requires sideloading.
  5. HiLight Studio 1.0.4 beta APK — APKMirror (https://www.apkmirror.com/apk/dhananjaybhosale/hilight-studio-github-version/hilight-studio-1-0-4-release/hilight-studio-1-0-4-android-apk-download/) — Lists supported devices (Pixel 11 Pro/XL/Fold), distribution, and notes open‑source build instructions and Shizuku/ADB transport.
  6. User manual | Shizuku — Official Docs (https://shizuku.rikka.app/guide/setup/) — Explains Shizuku setup via wireless debugging, providing the basis for the permission model HiLight Studio employs.
  7. Nothing Phone 2 review — TechRadar (https://www.techradar.com/phones/nothing-phones/nothing-phone-2-review) — Establishes that a back‑of‑phone LED interface can be “cool but underutilized,” a useful analogue for HiLight’s adoption risk.
  8. Google Pixel 11 Pro and Pro XL review — Tom’s Guide (https://www.tomsguide.com/phones/google-pixel-phones/google-pixel-11-pro-pro-xl-review) — A mainstream review calling HiLight interesting yet half‑baked, illustrating the reputational risk of keeping it closed.



Related update: We recently published an article that expands on this topic: read the latest post.

Related update: We recently published an article that expands on this topic: read the latest post.

Why I’m Done Buying Kindles Permanently | Analysis by Brian Moineau

Posted on by Brian Moineau

I'm never buying another Kindle, and neither should you

I used to think a Kindle was the easiest way to carry a library in my pocket — until my device stopped being built for readers. "I'm never buying another Kindle, and neither should you" isn't just clickbait; it's the honest reaction of someone who’s watched a device I trusted become more about corporate control than quiet, private reading. Recent firmware changes, DRM tweaks, forced updates, and reports of devices becoming effectively useless have made me rethink the whole premise of buying into Amazon’s e-reader ecosystem. (androidauthority.com)

What changed: from thoughtful gadget to locked-down appliance

Kindles pioneered e-ink reading, long battery life, and a genuinely book-like experience. Over the last few years, though, Amazon has tightened the screws: new firmware has introduced stronger DRM, removed features some users relied on, and in certain cases left devices struggling after updates. The result feels less like thoughtful product stewardship and more like product control. (pocket-lint.com)

Forced updates and buggy firmware have bricked or destabilized multiple devices, according to user reports. When a device that once simply displayed text can suddenly fail because of an overzealous update, you stop seeing it as a durable tool and start seeing it as a service tethered to a corporation’s whims. (wired.com)

Why control matters for readers

Reading is a private, low-friction activity. We choose e-readers to remove distractions, extend battery life, and preserve a single-minded focus on the text. That expectation breaks down when:

  • The manufacturer can silently push updates that change functionality.
  • DRM prevents you from backing up the books you paid for.
  • Amazon can remove or alter access to features or formats without meaningful recourse. (pocket-lint.com)

When your books are tied to an ecosystem that can alter device behavior remotely, ownership becomes ambiguous. You may own the hardware, but you don't fully own the reading experience.

Alternatives that respect readers

Not every e-reader treats you like a license holder. Devices and ecosystems like Kobo and Android-based readers (Boox, etc.) prioritize open file formats, library integration, and — in many cases — local management of files. That means you can borrow from libraries, load ebooks directly, and keep local backups without jumping through Amazon-sized hoops. For people who value interoperability and control, these options are more appealing. (laptopmag.com)

Transitioning away from Kindle may involve a learning curve — Calibre and EPUB support are foreign to some Kindle-only users — but the trade-off is a system where your purchases and local files feel genuinely yours.

The DRM problem: more than inconvenience

Amazon’s recent firmware updates introduced stronger DRM layers that make backing up content harder and complicate transferring books between devices. That’s not just inconvenient; it’s a long-term risk. If support for older devices ends (as Amazon recently announced for devices from 2012 and earlier), users can lose features or compatibility overnight, increasing e-waste and effectively forcing upgrades. (pocket-lint.com)

If you value longevity and the ability to archive purchases locally, heavy-handed DRM is a red flag. It means your “library” may vanish into formats and servers you can’t control.

The human cost: frustration, lost time, and distrust

This isn’t abstract. Real readers report waking up to bricked devices, losing access to sideloaded books, or spending hours on support calls that don’t resolve the core problem. That friction chips away at trust. Once the relationship between buyer and device shifts toward paternalistic control, the emotional value of the product drops. People don’t just want features — they want reliability and respect for ownership. (reddit.com)

What Amazon could do (but hasn’t)

There are straightforward, reader-first moves Amazon could make:

  • Stop forced updates that can brick devices or remove core features without clear opt-in.
  • Provide a robust offline-side-load and backup path for purchased content.
  • Limit DRM to the minimum necessary and make archival/export tools available.
  • Offer clear, dated support timelines so buyers can make informed choices.

Until Amazon anchors its strategy around reader rights and device longevity, skepticism is rational.

Alternatives and practical next steps

If you’re fed up and thinking of switching, here’s a quick roadmap:

  • Try a Kobo if you want straightforward EPUB support and library integration.
  • Consider Android-based e-ink devices (Boox, Onyx) if you want apps and flexibility.
  • Use Calibre to manage local libraries and maintain backups of any DRM-free files.
  • When buying, prefer sellers that clearly state region and support policies to avoid warranty headaches. (laptopmag.com)

These options aren’t perfect, but they foreground user control over corporate convenience.

My take

I still love the idea of a dedicated e-reader: the tactile simplicity, the long battery life, the focus. But a device that can be subtly reshaped by the company behind it — sometimes to the detriment of the user — no longer earns my loyalty. For me, “I’m never buying another Kindle, and neither should you” captures a larger point: buy tools that respect your ownership, not products that treat you as a subscription to be managed.

Closing thoughts

We buy gadgets to make our lives richer, not to become pawns in product strategies. Reading should be low-friction, private, and durable. When a platform that once delivered that experience starts prioritizing control over readers, it’s time to look away and support alternatives that preserve the simple joy of turning a page.

Sources



Related update: We recently published an article that expands on this topic: read the latest post.

Related update: We recently published an article that expands on this topic: read the latest post.

Delete These Dangerous Mobile Apps Now | Analysis by Brian Moineau

Posted on by Brian Moineau

Check your smartphone now — these apps are dangerous and should be deleted.

You should read that sentence again and then open your phone. Check your apps. Check what permissions they've been allowed. The FBI has just issued a public warning about mobile applications — especially those developed and maintained overseas — that can quietly collect and leak personal data. Check your smartphone now — these apps are dangerous and should be deleted. This is not fearmongering; it's a practical reminder that our pocket computers hold the keys to our contacts, location, photos, messages, and sometimes banking tokens.

Why the FBI warning matters

Over the last few years, governments and security agencies have flagged concerns about certain foreign-developed apps that request broad device permissions, persistently collect data, or route information through infrastructure in countries with different national security laws. The FBI’s recent public service advisory highlights three recurring risks:

  • Apps that ask for access to contacts, SMS, storage, and location can harvest data about people who never installed the app.
  • Some apps persistently collect information even when they aren’t actively used.
  • Apps that host or hide malware can exfiltrate data or enable surveillance.

The advisory doesn’t ban specific mainstream brands by name in every case, but it does nudge users to be extra cautious about apps that maintain infrastructure or data stores in foreign jurisdictions where local laws may compel that data be handed over to state authorities.

Transitioning from awareness to action is the point: if an app on your phone requests sweeping permissions and you don’t trust its origin, treat it as a red flag.

Which apps you should watch for

The FBI’s message is broad rather than a neat list of offenders. That’s intentional: the risk isn’t just one app, it’s a pattern in how some apps behave and where they store data. Still, coverage from security outlets and tech sites highlights common categories to scrutinize:

  • Free VPNs and “lite” streaming or downloader apps that ask for device-wide access.
  • Lesser-known social or utility apps that request contact lists, SMS, and storage access on install.
  • Apps hosted outside official stores (sideloaded APKs on Android) or unofficial versions of popular services.
  • Apps that solicit device admin rights, accessibility privileges, or persistent background access.

If an app is obscure, newly published, or from a developer you can’t verify — and it asks for broad permissions — it’s safer to delete it and find a well-reviewed, reputable alternative.

What to do right now

  • Open your phone’s Settings and review app permissions. Revoke anything that looks unnecessary (camera, mic, contacts) for apps that shouldn’t need them.
  • Uninstall apps you don’t recognize, don’t use, or that you installed outside Apple’s App Store or Google Play.
  • Update your OS and apps to the latest versions so security patches are applied.
  • Only download apps from official stores and check developer details and reviews.
  • Change passwords for sensitive accounts and enable multi-factor authentication where possible.
  • If you suspect an app has stolen data or behaved maliciously, reset the device and reach out to your bank or services you use — and file a report with the FBI’s IC3 or your local authorities if you’re in the U.S.

These steps reduce the attack surface and limit persistent data collection even if an app is trying to overreach.

How real is the risk?

A follow-up question is fair: how likely is your app to be an active surveillance tool versus just a privacy-invasive tracker? The answer is: both are possible. Some apps are simply greedy for advertising and analytics data. Others — whether through negligence or design — may process and store data in ways that expose it to foreign legal orders or hostile actors. Security researchers and agencies have repeatedly found malware-laden or trojanized apps on third-party stores and even within official marketplaces.

So while the worst-case scenarios are rarer, the cost of inaction is high: identity theft, account takeover, and privacy compromise. Treating your smartphone like a personal device that needs periodic audits is smart hygiene — not paranoia.

Navigating nuance: don’t throw the baby out with the bathwater

Not every app developed abroad is a threat. Big, reputable companies with clear transparency reports, independent audits, and local presence are different from small, opaque developers. Context matters:

  • Look for transparency: where is data stored, how is it encrypted, and what do the privacy policies say?
  • Prefer apps with independent security reviews or a track record of responsible disclosure.
  • Remember that removing permissions or uninstalling apps may break functionality — weigh that against the information at stake.

In short: be skeptical, not reflexively fearful. Make decisions based on permissions, provenance, and behavior.

My take

Smartphone security is a habit, not a one-off action. The FBI’s advisory is a timely nudge reminding us that convenience often comes with trade-offs. A regular five-minute check of permissions, coupled with a quick uninstall sweep for unused apps, will dramatically improve your safety. We can enjoy modern apps while still insisting they earn our trust.

Final thought: think of your phone like your home — you wouldn’t give a stranger permanent access to your house keys or bathroom drawers. Treat app permissions the same way.

Sources



Related update: We recently published an article that expands on this topic: read the latest post.