droid.rooter

// portfolio / case studies

Casi Android risolti — 46 esempi

Questi casi anonimizzati mostrano problemi e decisioni tipiche. Non garantiscono che un altro dispositivo con nome simile segua lo stesso percorso.

I casi sensibili restano descritti a livello di risultato e diagnosi, non come ricette di bypass.

Caso 01 — FRP su Samsung dopo factory reset

Device
Samsung Galaxy A52
Country
UAE

The Problem

Un Samsung si era fermato alla verifica Google dopo un reset. Prima di qualsiasi intervento sono stati verificati proprietà, modello e patch di sicurezza.

What Was Done

È stato scelto un percorso coerente con firmware e autorizzazione del cliente, senza trattare FRP come un bypass universale.

result → Fixed in 47 minutes. Client confirmed the device boots cleanly to setup with a fresh Google account.

case 02

Caso 02 — Bootloop dopo modifica di sistema

Device
Xiaomi Redmi Note 12
Country
Saudi Arabia

The Problem

Il dispositivo si avviava solo fino al logo dopo una modifica. Invece di fare subito wipe sono stati controllati stato di boot e partizioni toccate.

What Was Done

Diagnosed remotely as a corrupted system partition from the half-applied OTA. Walked the client through entering Mi Assistant Mode, then performed a clean stock ROM flash of the matching MEA-region firmware via Mi Flash on a borrowed PC. The flash was performed in non-destructive mode to preserve the data partition wherever possible.

Il ripristino dei componenti stock corretti ha riportato il dispositivo a un avvio pulito.

case 03

Caso 03 — OnePlus ottimizzato per gaming

Device
OnePlus 9
Country
United Kingdom

The Problem

Dopo un root verificato, l’obiettivo era migliorare frame-time e carico in background, non inseguire overclock estremi.

What Was Done

Unlocked the bootloader via OnePlus’s official method, patched boot.img with Magisk, installed a tuned KernelSU-compatible custom kernel, and configured Zygisk + DenyList + Shamiko to fully hide root from the four banking apps. Tested each banking app live with the client over screen-share to confirm they all open without integrity warnings.

Baseline e misure successive hanno permesso di valutare i cambiamenti in modo oggettivo.

case 04

Caso 04 — Telefono usato ancora legato al vecchio account

Device
Oppo Reno 8
Country
United Arab Emirates

The Problem

Un dispositivo usato era ancora associato all’account precedente dopo il reset.

What Was Done

Verified ownership through the seller-side WhatsApp transcript and the original purchase invoice from the Sharaf DG retailer. Used the Qualcomm EDL test-point method specific to the Reno 8 chipset to flash a clean ColorOS image and clear the cloud-account binding from the protected partition. Re-enabled OTA updates on a clean account.

È stato seguito un percorso di proprietà/account legittimo invece di aggirare una protezione anti-furto.

case 05

Caso 05 — Foto eliminate per errore

Device
Samsung Galaxy S21
Country
Germany

The Problem

Sono state valutate possibilità reali di recupero in base a tempo, uso successivo, TRIM e backup.

What Was Done

Stopped the client from writing further data to the phone immediately. Performed a logical recovery using a chain of Magisk + a custom recovery script over ADB to dump the unallocated regions of the internal partition, then ran file-carving against the dump on the workshop PC to recover JPEG, HEIC and MP4 fragments by file signature. Filtered out corrupt thumbnails and re-built the EXIF where possible.

Sono state controllate prima fonti cloud/cache e minimizzate nuove scritture.

case 06

Caso 06 — Prestazioni migliorate senza factory reset

Device
Motorola Moto G84
Country
Australia

The Problem

Telefono lento, caldo e con battery drain.

What Was Done

Audited installed apps and identified 14 unused carrier and OEM bloatware packages that ran background services constantly. Used ADB pm uninstall --user 0 to remove them safely without unlocking the bootloader. Tuned animation scales, disabled aggressive RAM trim, capped 3 known battery-hungry apps via Doze whitelist removal, and ran a calibrated benchmark before/after.

La diagnosi ha individuato servizi e app problematiche, evitando un reset totale non necessario.

case 07

Caso 07 — Magisk su Pixel 8 Pro

Device
Google Pixel 8 Pro
Country
United States

The Problem

Firmware e init_boot.img sono stati abbinati al build corretto.

What Was Done

Unlocked bootloader via fastboot, downloaded matching Pixel factory image, extracted init_boot.img, patched it on-device with Magisk Manager, then flashed the patched init_boot back via fastboot. Set up Zygisk, DenyList and Shamiko, then installed Play Integrity Fix module and verified Strong integrity passing. Re-locked AVB with custom key was skipped at client’s request to keep updates simple.

Dopo il flash sono stati testati boot, root e app principali, conservando l’immagine stock.

case 08

Caso 08 — KernelSU su Pixel 9

Device
Google Pixel 9
Country
Germany

The Problem

Un utente avanzato voleva root kernel-level invece di Magisk.

What Was Done

Unlocked bootloader, sourced a community KernelSU-Next + SUSFS kernel build matching the current Pixel security patch, flashed via fastboot boot to test, then permanently flashed after confirming boot. Installed KernelSU Manager APK, configured app profiles to grant only required apps, and added Sparkasse + Google Play Services to the SUSFS hide list.

È stato verificato un kernel compatibile e il passaggio è avvenuto senza eseguire due root framework insieme.

case 09

Caso 09 — Galaxy S24 Ultra con rischio Knox accettato

Device
Samsung Galaxy S24 Ultra
Country
United Kingdom

The Problem

Il caso richiedeva prima di tutto una verifica di variante e One UI.

What Was Done

Il cliente è stato informato su Knox e sulle limitazioni moderne prima di proseguire.

result → Magisk active, ad-blocking system-wide, three banking apps verified. Samsung Pay disabled as agreed. 110 minutes.

case 10

Caso 10 — APatch su Galaxy S23

Device
Samsung Galaxy S23
Country
Canada

The Problem

L’utente voleva valutare APatch.

What Was Done

Unlocked OEM bit, downloaded matching S23 firmware, used APatch tooling to inject the kpatch into the kernel image, flashed via Odin. Walked the client through APatch Manager setup and per-app SU policy. Tested RBC, TD and Scotiabank — all opened cleanly with APatch hidden via its module system.

Il percorso è stato trattato come progetto specifico per dispositivo, non come ricetta Samsung universale.

case 11

Caso 11 — OnePlus 12 con Magisk e custom kernel

Device
OnePlus 12
Country
United States

The Problem

Il root è stato reso stabile prima di aggiungere il kernel.

What Was Done

Used official OnePlus unlock token, patched the OnePlus 12 boot.img with Magisk, then flashed a community kernel with WireGuard kernel module and BBR2 already compiled in. Verified WireGuard handshake against the client’s endpoint over the call. DenyList configured for Chase, Venmo and Cash App.

L’approccio a fasi ha reso più semplice isolare eventuali problemi.

case 12

Caso 12 — Xiaomi 14 e attesa Mi Unlock

Device
Xiaomi 14
Country
Germany

The Problem

Client tried to bootloader-unlock a Xiaomi 14 (Global EU) via Mi Unlock Tool and was hit with the new 2026 Xiaomi unlock policy: the 168-hour waiting period plus a per-account quota of one device per year. Account had already unlocked another device 4 months prior.

What Was Done

Il limite era la policy server-side HyperOS, non Fastboot.

È stato atteso lo stato ufficiale di eligibility invece di usare presunti tool di bypass.

case 13

Caso 13 — KernelSU su POCO F6

Device
POCO F6
Country
United Kingdom

The Problem

Dopo unlock Xiaomi valido, è stato scelto KernelSU su un percorso compatibile.

What Was Done

Unlocked bootloader (account had no prior unlocks, completed in standard waiting period), flashed KernelSU-bundled kernel built for HyperOS 2 base, installed KernelSU Manager. Configured app profiles so only Termux and AdAway have SU access. Added banking and Google Play to the umount-from-namespace list.

Firmware stock e rollback sono stati preparati prima dei moduli performance.

case 14

Caso 14 — Nothing Phone 2a con root

Device
Nothing Phone 2a
Country
Canada

The Problem

Il dispositivo è stato gestito tramite Fastboot con build verificato.

What Was Done

Unlocked bootloader via fastboot (Nothing requires ENABLE_OEM_UNLOCK in dev options first), patched boot.img with Magisk via Manager APK, flashed back. Installed AFWall+ with iptables binary check, set up the font module via Magisk repo. DenyList covered RBC, Wealthsimple, Google Play. Verified Play Integrity Strong passing with PIF latest module.

Anche un device “aperto” richiede file esatti e piano di recovery.

case 15

Caso 15 — ROG Phone 8 Pro per gaming

Device
Asus ROG Phone 8 Pro
Country
Saudi Arabia

The Problem

Sono stati misurati temperatura e FPS prima del tuning.

What Was Done

Used Asus’s official unlock APK (still available in 2026 for ROG line), unlocked bootloader, patched ROG-specific boot.img with Magisk preserving Asus-signed components. Installed a community gaming kernel (BBR, schedutil tuned). Verified X Mode and AirTriggers still active. DenyList for Al Rajhi, STC Pay, urpay.

Nessun thermal disabler aggressivo: priorità a prestazioni sostenute.

case 16

Caso 16 — Realme GT Neo 6 importato

Device
Realme GT Neo 6
Country
United Arab Emirates

The Problem

Sono state verificate regione, firmware e disponibilità effettiva di unlock/Deep Test.

What Was Done

Walked the client through reflashing the Realme UI Asia firmware via QPST flash mode, re-applied for in-depth test approval which this time accepted the device, completed the 24-hour required test period, then performed bootloader unlock. Installed Magisk + Tricky Store. Verified Emirates NBD, ADCB and FAB apps.

Non è stato promesso un root senza evidenza concreta per quella variante.

case 17

Caso 17 — Pixel 6a riportato stock per la vendita

Device
Google Pixel 6a
Country
United States

The Problem

Il telefono rooted doveva tornare a configurazione pulita.

What Was Done

Flashed the latest Pixel 6a factory image cleanly via the Android Flash Tool web interface, then re-locked the bootloader via fastboot flashing lock. Verified the AVB orange/yellow warning is gone, device boots straight to setup wizard. Reset OEM unlock allow flag.

È stata installata la factory image corretta prima di valutare il relock.

case 18

Caso 18 — Motorola Edge 50 con limite di unlock

Device
Motorola Edge 50 Pro
Country
United Kingdom

The Problem

Il portale Motorola non trattava la variante come automaticamente eleggibile.

What Was Done

Used the unlock-code workflow against Motorola’s public API with the correct IMEI + region tokens after sanitizing the carrier flag in the device’s mod file. Code generated, bootloader unlocked, Magisk patched onto boot.img, AdAway installed. DenyList configured for Lloyds and Monzo.

Il caso ha mostrato l’importanza di distinguere retail e carrier.

case 19

Caso 19 — Valutazione root Vivo X100

Device
Vivo X100
Country
United Arab Emirates

The Problem

La verifica non ha trovato un percorso pubblico generale affidabile.

What Was Done

Disclosed upfront that no software-only unlock exists for X100 in 2026. Verified via fastboot dump that the bootloader is fully locked with no oem unlock support. Offered a refund of the diagnosis fee (already free) and recommended the client either accept stock OS, or sell and switch to a Pixel / Xiaomi / OnePlus.

Sono stati proposti obiettivi alternativi raggiungibili senza root.

case 20

Caso 20 — App bancaria bloccata mesi dopo il root

Device
Galaxy S22
Country
Canada

The Problem

Un setup che funzionava ha perso compatibilità dopo cambiamenti lato app/integrity.

What Was Done

Identified that the client’s Play Integrity Fix module was 2 versions behind (a Google rotation in late April 2026 invalidated the older fingerprint set). Updated PIF to the latest signed release from the original developer’s GitHub, refreshed the fingerprint via the included tool, rebooted. Verified Strong integrity, then tested both banking apps live.

Sono stati rimossi componenti obsoleti e rivalutato lo stack senza promettere stabilità futura.

case 21

Caso 21 — Sparkasse pushTAN e root

Device
Xiaomi 13T
Country
Germany

The Problem

È stato necessario testare app, build e segnali di root reali.

What Was Done

Added Tricky Store module on top of the existing Magisk stack, configured it to spoof the keystore attestation for de.fiducia.smartphone.android.banking.fints (the Sparkasse package). Imported a known-good Pixel attestation key set into Tricky Store. Verified Strong Integrity with hardware attestation now passing.

Nessuna promessa “modulo X funziona sempre” è stata usata.

case 22

Caso 22 — Google Wallet su Pixel rooted

Device
Pixel 7 Pro
Country
United States

The Problem

Il dispositivo superava alcuni test ma Wallet continuava a rifiutarlo.

What Was Done

Confirmed PIF was up to date, ensured DenyList covered Google Wallet (com.google.android.apps.walletnfcrel), Google Play Services and Google Play Store. Cleared Google Wallet data, signed back in, re-added Chase Visa from scratch. Walked the client through verifying the small charge SMS code.

Il caso è stato trattato come compatibilità applicativa, non come errore automatico del root.

case 23

Caso 23 — Trasferimento WhatsApp da iPhone a Samsung

Device
Samsung Galaxy A54
Country
United Kingdom

The Problem

L’obiettivo era migrare chat e media in modo supportato.

What Was Done

Used the WhatsApp Move-to-Android utility from a fresh install, plus a manual local backup file copied via cable from the source iPhone via WhatsApp’s built-in export. Reinstalled WhatsApp on the A54 with the same number, restored from the local backup file rather than relying on the failing Google Drive bridge.

È stato privilegiato il percorso ufficiale anziché manipolare database manualmente.

case 24

Caso 24 — Problemi Snapchat dopo modifiche

Device
OnePlus 11
Country
United States

The Problem

L’app rifiutava alcune funzioni dopo una storia di modding.

What Was Done

Cleared Snapchat data and the system-side device-id stores, cleaned residual Magisk references from the system identifier props, regenerated a fresh Android ID and Widevine ID via the appropriate Magisk modules, reinstalled Snapchat from a fresh Aurora Store login.

È stato seguito un percorso legittimo di ritorno stock/supporto senza bypassare sistemi anti-abuso.

case 25

Caso 25 — Pokémon GO su dispositivo rooted

Device
Pixel 8
Country
Canada

The Problem

Il caso toccava rilevamento root e anti-cheat.

What Was Done

Switched the device from Magisk to KernelSU-Next + SUSFS, installed Tricky Store + a fresh Pokémon-friendly fingerprint, and configured SUSFS to umount the namespace from the Niantic process. Tested launch over Wi-Fi and 5G.

Non sono state sviluppate tecniche per eludere anti-cheat; sono stati spiegati i trade-off del root.

case 26

Caso 26 — Instagram continua a chiudersi

Device
Samsung Galaxy A14
Country
Saudi Arabia

The Problem

Log e stato sistema indicavano un problema app, non un bisogno di root.

What Was Done

Identified the issue as a corrupted webview component on the A14 specific to that Instagram version. Force-reinstalled Android System WebView from the Play Store, cleared Instagram data, and removed a conflicting third-party emoji keyboard. Tested launch and scrolling.

Il problema è stato affrontato tramite cache/versione/componenti di sistema.

case 27

Caso 27 — Battery drain forte su Galaxy S22+

Device
Galaxy S22+
Country
United States

The Problem

Il telefono perdeva molta batteria in standby.

What Was Done

Pulled bugreport over ADB, parsed the battery-stats blame chains, and identified two background offenders: a weather widget waking the radio every 90 seconds, and a fitness app holding partial wakelock. Killed both apps’ background activity, restricted them via Doze whitelist removal, and rolled back a buggy Samsung Health update.

Battery stats e wakelock hanno permesso di distinguere software da batteria fisicamente degradata.

case 28

Caso 28 — Redmi Note 11 senza segni di vita

Device
Xiaomi Redmi Note 11
Country
United Arab Emirates

The Problem

Il dispositivo non entrava normalmente in boot o recovery.

What Was Done

Diagnosed as a soft-bricked PMIC state from a stuck wakelock (relatively common on this model). Walked the client through the Mi Assistant force-EDL combo, pushed a clean firmware via Mi Flash with battery-safe parameters. Recovered the device without replacing any hardware.

Sono stati verificati Fastboot, EDL/BootROM e indicatori hardware prima di promettere recovery.

case 29

Caso 29 — Wi-Fi si disconnette spesso

Device
OnePlus Nord 3
Country
United Kingdom

The Problem

Client’s Nord 3 disconnected from home WiFi every 30–60 seconds and reconnected. Other devices on the same network were fine.

What Was Done

Sono stati controllati router, DHCP, power management, VPN e log.

Il problema è stato isolato senza riflashare tutto il telefono.

case 30

Caso 30 — Fotocamera con schermo nero

Device
Pixel 7a
Country
Germany

The Problem

Client’s Pixel 7a camera app showed a black viewfinder after a system update. Third-party camera apps had the same issue.

What Was Done

Log e servizi hanno aiutato a distinguere app, HAL, permessi, sensore o hardware.

Le correzioni sono state applicate solo dopo la diagnosi.

case 31

Caso 31 — Thermal throttling forte su POCO

Device
POCO F5 Pro
Country
Saudi Arabia

The Problem

Le misure mostravano calo di frequenze dopo pochi minuti di gioco.

What Was Done

With the device already rooted, installed a community thermal config that loosens the early-throttling table while keeping the safety ceilings intact. Tuned Adreno frequency steps and disabled an aggressive RAM trim that was triggering CPU spikes.

È stato usato un profilo più conservativo invece di disabilitare tutte le protezioni termiche.

case 32

Caso 32 — Parental control su Galaxy A34

Device
Samsung Galaxy A34 (child)
Country
United States

The Problem

Servivano regole chiare per app, tempo e posizione.

What Was Done

Set up Google Family Link as the primary supervision layer, then layered Bark for content monitoring of texts and supported social apps. Configured per-app time limits in Family Link, blocked browser categories at the DNS layer via NextDNS profile pushed to the device, enabled Find My Device location sharing to the parent’s account.

È stato preferito un setup trasparente e proporzionato.

case 33

Caso 33 — Qustodio per due bambini

Device
Galaxy A24 + Pixel 6a
Country
United Kingdom

The Problem

I due dispositivi avevano età e orari diversi.

What Was Done

Installed Qustodio on both devices, granted Device Administrator and Accessibility permissions correctly (this is the step most parents miss), set up per-child profiles in the Qustodio web dashboard, calibrated screen-time schedules and category filters to age-appropriate levels. Tested the uninstall-resistance on both devices.

Profili e alert sono stati separati per evitare notifiche inutili.

case 34

Caso 34 — Valutazione limiti Family Link

Device
Galaxy A14 (child)
Country
Canada

The Problem

La famiglia voleva sapere cosa potesse fare davvero Family Link.

What Was Done

Pulled Family Link audit logs, identified the workaround method (a known guest-account exploit on older Family Link builds). Force-updated Family Link, removed the guest accounts, blocked guest-mode at the device-policy level, and added secondary supervision via Bark for chat content. Disclosed all changes to the teenager as the parent insisted on transparency.

Sono state sfruttate prima le funzioni esistenti invece di vendere subito un tool più invasivo.

case 35

Caso 35 — Valutazione mSpy in ambito familiare

Device
Samsung Galaxy A55
Country
United Arab Emirates

The Problem

Prima del setup sono stati discussi proprietà, età, trasparenza e legge locale.

What Was Done

Installed mSpy with the device physically present (mSpy requires manual install on Android), granted required Accessibility and Notification-listener permissions, configured the dashboard, set up the messaging modules, and verified data flowing into the parent dashboard.

Dove necessario è stata consigliata un’alternativa meno invasiva.

case 36

Caso 36 — LineageOS su Pixel più vecchio

Device
Pixel 4a 5G
Country
Germany

The Problem

Il dispositivo doveva continuare a essere utile oltre il supporto OEM.

What Was Done

Unlocked bootloader (already retail-unlocked), flashed LineageOS recovery, sideloaded LineageOS 22 build for redfin codename, then sideloaded the MicroG variant overlay and the F-Droid privileged extension. Configured Aurora Store for Play Store apps, set up Banking apps via Aurora.

È stato scelto un build mantenuto e documentato il ritorno stock.

case 37

Caso 37 — GrapheneOS su Pixel 8a

Device
Pixel 8a
Country
Canada

The Problem

L’utente voleva sicurezza e privacy, non root.

What Was Done

Used the official GrapheneOS web installer over Chrome, unlocked bootloader, flashed GrapheneOS, re-locked bootloader. Installed Sandboxed Google Play, configured Vanadium browser, set up RBC and Wealthsimple — both worked first try with Sandboxed Play. Walked the client through GrapheneOS’s scoped storage and per-permission profiles.

GrapheneOS è stato trattato come modello di sicurezza separato e non combinato con root.

case 38

Caso 38 — Ripristino IMEI originale dopo flash errato

Device
Xiaomi POCO X3 Pro
Country
Saudi Arabia

The Problem

Il flash aveva danneggiato dati modem/EFS.

What Was Done

Backed up the existing partitions, wrote the correct IMEI numbers from the device’s rear-cover sticker into the EFS/NV partition using the appropriate Qualcomm tool, then re-flashed the matching MEA-region modem firmware. Verified both IMEI numbers in the dialer and tested data on STC.

Sono stati ripristinati solo identificatori originali legittimi, senza clonazioni.

case 39

Caso 39 — Valutazione dual-boot su OnePlus 9R

Device
OnePlus 9R
Country
United States

The Problem

Il progetto richiedeva gestione avanzata di partizioni e slot A/B.

What Was Done

Configured DSU Sideloader, prepared a clean LineageOS GSI image compatible with the OnePlus 9R’s vendor partition, set up the dual-boot launcher, and walked the client through switching between systems via Developer Options. Banking apps live on stock side only.

È stato trattato come sperimentale e non come servizio standard.

case 40

Caso 40 — Richiesta di nascondere Knox per la garanzia rifiutata

Device
Samsung Galaxy S20
Country
United Kingdom

The Problem

L’utente voleva mascherare lo stato modificato del Samsung.

What Was Done

Declined the work and explained why: tampering with Knox to deceive a manufacturer warranty is fraud under UK consumer-protection law and against our policy. Offered an alternative — a third-party screen replacement quote and a check on whether the Knox-tripped state actually affects screen warranty (in this case, no, the hardware was within statutory rights regardless).

La richiesta è stata rifiutata; sono stati spiegati ritorno stock e comunicazione trasparente con l’assistenza.

case 41

Caso 41 — Backup cifrati senza cloud

Device
Galaxy S23 Ultra
Country
Germany

The Problem

Il cliente voleva migrare backup locali cifrati tra dispositivi.

What Was Done

Set up an air-gapped local transfer over USB-C OTG cable. Used Signal’s native device-to-device transfer for chats, exported the Aegis vault encrypted file, copied the KeePassXC database directly, and used WhatsApp’s local backup file plus chat-export for selected conversations. Verified each app on the new device.

È stato usato trasferimento diretto con gestione chiavi chiara.

case 42

Caso 42 — Profilo guida con Tasker

Device
Google Pixel 8
Country
United States

The Problem

Bluetooth auto doveva attivare DND, navigazione e audio.

What Was Done

Built a Tasker profile triggered on the car head-unit’s Bluetooth MAC address. Stack: enable DND with calls-only exception for spouse, set brightness to 80%, launch Google Maps with a saved-route intent, resume the last Spotify playlist via Media Control, enable auto-reply to WhatsApp using AutoNotification ("driving — call you back at <ETA>"). Reverse profile fires on Bluetooth disconnect. Battery audit showed +0.4% per hour of use.

Il workflow è stato costruito su eventi, senza polling inutile.

case 43

Caso 43 — Clock-in autorizzato con MacroDroid

Device
Samsung Galaxy A54
Country
United Kingdom

The Problem

Un workflow aziendale doveva registrare una presenza approvata all’arrivo.

What Was Done

Configured MacroDroid (chosen over Tasker for the simpler UI the client preferred). Geofence around the hospital site with a 50-metre radius. Trigger fires only between 06:00–22:00 to avoid false starts during personal visits. Stack: HTTP POST to the Trust webhook with auth token stored in MacroDroid variables, Telegram bot message via the Telegram-Bot plugin, switch ringer to vibrate. Departure trigger reverses and clocks out.

L’automazione era trasparente e autorizzata, non sorveglianza nascosta.

case 44

Caso 44 — Telefono come sensore Home Assistant

Device
OnePlus 12
Country
Germany

The Problem

Smart-home enthusiast client running Home Assistant on a NUC wanted to expose the OnePlus 12 as a full automation hub — sensors, location, notification actions and DND state — and trigger HA scenes from phone events (waking, leaving home, plugging in to charge).

What Was Done

Installed Home Assistant Companion app, registered the device, exposed all 32 available sensors. Configured HA-side automations: morning step-out-of-bed (detected via accelerometer + screen-on after 06:00) → bedroom lights warm 20%, kettle on. Phone reaching home Wi-Fi → presence binary sensor flips, away-mode disabled. Battery <20% in living room → TV pauses via the Sony Bravia integration. Two-way: HA can ring the phone to find it, push prioritised notifications, and trigger DND remotely.

Il device doveva inviare posizione, batteria e stati scelti.

Sono stati condivisi solo i sensori necessari.

Caso 45 — Modalità NFC per ufficio, sonno e auto

Device
Samsung Galaxy S23
Country
United Arab Emirates

The Problem

Tag NFC diversi dovevano attivare profili diversi.

What Was Done

Sourced 5 NTAG215 stickers (2 spares), wrote each with NFC Tools to fire a Tasker task by ID. Built three Tasker profiles: bedside = DND on, alarm armed for next workday, brightness 0%, blue-light filter on; desk = focus mode (Slack + Gmail + Things only), bridge to Mac via KDE Connect, Pomodoro timer started; car dock = full driving stack as in the Pixel 8 case but adapted for Galaxy S23. Each profile reversible with a second tap on the same tag.

Il setup ha sostituito azioni manuali mantenendo tutto modificabile dall’utente.

case 46

Caso 46 — Bot Telegram con Termux e Tasker

Device
Google Pixel 7a
Country
Canada

The Problem

Power-user client wanted a daily 09:00 Telegram message from their phone to a private channel containing battery health stats, today’s calendar agenda, weather summary, and a list of any unread Signal threads — all generated on-device, no third-party servers.

What Was Done

Installed Termux + Termux:Tasker bridge. Wrote a small bash script that reads battery-stats from /sys via Termux:API, fetches weather from Open-Meteo (no API key), pulls the day’s calendar via Termux:API’s termux-calendar, and queries Signal-CLI for unread thread counts. Tasker profile: Time = 09:00 daily → run the script → POST the formatted markdown to the Telegram bot via curl. Logs kept on-device only. Battery cost ~0.2%/day.

Il telefono doveva inviare dati locali controllati a un bot.

Token e script sono stati documentati localmente senza esporre credenziali in file pubblici.

Hai un caso simile?

Invia modello, build e stato attuale. Un caso simile è solo un punto di partenza.

Contatti — /it/contatti Servizi — /it/servizi