Beware of Virus! Adware "PDF Reader & Quick View" (com.flowersathletics.snakevenom) on Google Play floods your phone with full-screen ads, how to find and remove it
An Android 15 phone started showing ads everywhere, on top of any app. In Safe Mode there were no ads. Uninstalling random apps didn't help: opening any app brought them back.
I checked it over USB (adb) and found the culprit:
\- Play Store name: PDF Reader & Quick View
\- Developer: FLOWERS ATHLETICS LLC (10K+ downloads, still listed on Google Play)
\- Package: com.flowersathletics.snakevenom
\- Its internal code is actually named com.pdfreader.viewer.quick (doesn't match the package name)
\- Installed from Google Play the same day; in about 3 minutes it opened 156 full-screen video ads (ByteDance/Pangle ad SDK) on top of other apps
\- Starts on boot, receives push messages, runs a foreground service, and requests MANAGE_OWN_CALLS (why would a PDF reader need that?)
\- No accessibility or device-admin abuse, so it's easy to remove
HOW TO REMOVE IT
1. Settings > Apps > find "PDF Reader & Quick View" > Uninstall.
2. If the ads keep coming back: reboot into Safe Mode and uninstall it there.
3. Not sure which app shows the ads? When one appears, open Recent apps, long-press the app icon at the top > App info.
4. With a PC (adb): adb shell pm uninstall com.flowersathletics.snakevenom
5. Then run Play Protect (Play Store > profile picture > Play Protect > Scan) and report the app on its Play Store page.
After removing it, the ads stopped completely. Hope this helps someone.
https://redd.it/1xysftp
@reddit_android
An Android 15 phone started showing ads everywhere, on top of any app. In Safe Mode there were no ads. Uninstalling random apps didn't help: opening any app brought them back.
I checked it over USB (adb) and found the culprit:
\- Play Store name: PDF Reader & Quick View
\- Developer: FLOWERS ATHLETICS LLC (10K+ downloads, still listed on Google Play)
\- Package: com.flowersathletics.snakevenom
\- Its internal code is actually named com.pdfreader.viewer.quick (doesn't match the package name)
\- Installed from Google Play the same day; in about 3 minutes it opened 156 full-screen video ads (ByteDance/Pangle ad SDK) on top of other apps
\- Starts on boot, receives push messages, runs a foreground service, and requests MANAGE_OWN_CALLS (why would a PDF reader need that?)
\- No accessibility or device-admin abuse, so it's easy to remove
HOW TO REMOVE IT
1. Settings > Apps > find "PDF Reader & Quick View" > Uninstall.
2. If the ads keep coming back: reboot into Safe Mode and uninstall it there.
3. Not sure which app shows the ads? When one appears, open Recent apps, long-press the app icon at the top > App info.
4. With a PC (adb): adb shell pm uninstall com.flowersathletics.snakevenom
5. Then run Play Protect (Play Store > profile picture > Play Protect > Scan) and report the app on its Play Store page.
After removing it, the ads stopped completely. Hope this helps someone.
https://redd.it/1xysftp
@reddit_android
Found a working pre-rebrand Musical.ly APK on my old Android tablet that still connected to TikTok’s backend
Hey everyone, thought some app archivists and nostalgia fans here might find this cool.
While digging through some old tech, I remembered I still have an original, pre-August 2018 Musical.ly build installed on an old Android tablet.
The crazy part is that the last time I booted the tablet up (around 2023), the app didn't just open locally—it actually connected to TikTok's live servers. I was able to:
Sign into my account
Browse and watch modern TikTok videos inside the classic pink/red Musical.ly UI
Even post videos directly from the app
I haven't powered the tablet back on since 2023, so I'm not sure if ByteDance has finally killed support for this specific API version by now, or if it still works today.
Before I charge it up and connect it to Wi-Fi (making sure auto-updates are off so Google Play doesn't overwrite it with modern TikTok), I wanted to see if anyone here knows which specific transition-era build version this might be, or if archivists are looking for this APK to be dumped.
Let me know if you guys want me to fire it up, check the exact build/Android version numbers, and share some screenshots!
https://redd.it/1xxhtfl
@reddit_android
Hey everyone, thought some app archivists and nostalgia fans here might find this cool.
While digging through some old tech, I remembered I still have an original, pre-August 2018 Musical.ly build installed on an old Android tablet.
The crazy part is that the last time I booted the tablet up (around 2023), the app didn't just open locally—it actually connected to TikTok's live servers. I was able to:
Sign into my account
Browse and watch modern TikTok videos inside the classic pink/red Musical.ly UI
Even post videos directly from the app
I haven't powered the tablet back on since 2023, so I'm not sure if ByteDance has finally killed support for this specific API version by now, or if it still works today.
Before I charge it up and connect it to Wi-Fi (making sure auto-updates are off so Google Play doesn't overwrite it with modern TikTok), I wanted to see if anyone here knows which specific transition-era build version this might be, or if archivists are looking for this APK to be dumped.
Let me know if you guys want me to fire it up, check the exact build/Android version numbers, and share some screenshots!
https://redd.it/1xxhtfl
@reddit_android
I investigated a supposedly new Redmi 15C: conflicting RAM/storage reports, hidden root modules, LSPosed, and Keystore injection
# I bought a brand-new Redmi 15C 8/256GB for my grandmother. It may actually be a modified 4/128GB device with hidden root components, LSPosed, and Keystore injection.
**TL;DR:** I bought what was advertised as a brand-new **Xiaomi Redmi 15C Global, 8GB RAM / 256GB storage** from Ozon, a major online marketplace.
The phone was unusually slow right out of the box. That led me to investigate it using ADB, Fastboot, Linux kernel interfaces, Android logs, APK decompilation, and static ELF analysis.
What I found was much more concerning than ordinary budget-phone performance:
* Android reports approximately 8GB RAM, while `/proc/zoneinfo` accounts for only **4 GiB of present physical memory pages**.
* Android reports storage consistent with 256GB, while Fastboot reports a `userdata` partition of approximately **104.3 GiB**.
* Android claims the bootloader is locked and verified, while Fastboot reports `unlocked: yes` **and** `secure: no`.
* Multiple previously undisclosed root-related components are running, including **Zygisk-related daemons, LSPosed, and a module called** `network_module`.
* Logs show **TEESimulator reporting successful injection of a native library into Android's** `keystore2` **process**.
* An official KernelSU Manager APK that I installed for investigation was later uninstalled without my intervention. Android's PackageManager log attributes the uninstall request to **UID 0 (root)**.
* Developer Options and USB debugging repeatedly became disabled after reboot.
* After a factory reset, the phone unexpectedly displayed Chinese-language system menus, despite having been sold as a Global model.
I have preserved the original logs, Fastboot output, process information, extracted binaries, static-analysis results, hashes, and video evidence.
**Important disclaimer:** I am not claiming that I have conclusively identified the physical RAM/storage chips, proved malicious intent, or established that Xiaomi itself was involved. This is an investigation of one particular device sold by a third-party marketplace seller.
#
# 1. How this started
The phone was intended as a gift for my grandmother.
I wasn't expecting flagship performance. I understand that the Redmi 15C is a budget smartphone.
However, its behavior was abnormal almost immediately.
The interface was extremely sluggish. Some system interactions stalled for several seconds, and Android logs later showed SystemUI-related ANR events.
I also observed the battery indicator dropping from approximately **20% to 4% in around five minutes**.
Initially, I suspected a poorly optimized HyperOS build, background applications, or defective hardware.
Then I noticed that Developer Options and USB debugging would become disabled after restarting the phone.
That was unusual enough to justify a closer look.
I connected the phone to my Linux computer and started collecting evidence using ADB.
For reference, the device identified itself as:
Model: 25078RA3EA
Device: dew_global
Fastboot product: dew
Platform: mt6768
HyperOS: OS2.0.214.0.VBNMIXN
The advertised configuration was **8GB RAM / 256GB storage**.
# 2. The RAM discrepancy: 8GB reported, 4 GiB accounted for by the kernel's zone information
Android reports:
/proc/meminfo:
MemTotal: 7880704 kB
The system settings also report:
miui_ram_size = 8.0GB
That looks consistent with an 8GB device.
However, I checked `/proc/zoneinfo`.
The recorded values were:
DMA32 present = 786432 pages
Normal present = 262144 pages
Total = 1048576 pages
The system page size is:
4096 bytes
Therefore:
1048576 × 4096
= 4294967296 bytes
= 4 GiB
This is a major discrepancy.
The kernel's zone information accounts for **4 GiB of present pages**, while `/proc/meminfo` reports almost 8GB.
The extended RAM feature was reported as disabled during the investigation.
**What this establishes:** Two different system interfaces
# I bought a brand-new Redmi 15C 8/256GB for my grandmother. It may actually be a modified 4/128GB device with hidden root components, LSPosed, and Keystore injection.
**TL;DR:** I bought what was advertised as a brand-new **Xiaomi Redmi 15C Global, 8GB RAM / 256GB storage** from Ozon, a major online marketplace.
The phone was unusually slow right out of the box. That led me to investigate it using ADB, Fastboot, Linux kernel interfaces, Android logs, APK decompilation, and static ELF analysis.
What I found was much more concerning than ordinary budget-phone performance:
* Android reports approximately 8GB RAM, while `/proc/zoneinfo` accounts for only **4 GiB of present physical memory pages**.
* Android reports storage consistent with 256GB, while Fastboot reports a `userdata` partition of approximately **104.3 GiB**.
* Android claims the bootloader is locked and verified, while Fastboot reports `unlocked: yes` **and** `secure: no`.
* Multiple previously undisclosed root-related components are running, including **Zygisk-related daemons, LSPosed, and a module called** `network_module`.
* Logs show **TEESimulator reporting successful injection of a native library into Android's** `keystore2` **process**.
* An official KernelSU Manager APK that I installed for investigation was later uninstalled without my intervention. Android's PackageManager log attributes the uninstall request to **UID 0 (root)**.
* Developer Options and USB debugging repeatedly became disabled after reboot.
* After a factory reset, the phone unexpectedly displayed Chinese-language system menus, despite having been sold as a Global model.
I have preserved the original logs, Fastboot output, process information, extracted binaries, static-analysis results, hashes, and video evidence.
**Important disclaimer:** I am not claiming that I have conclusively identified the physical RAM/storage chips, proved malicious intent, or established that Xiaomi itself was involved. This is an investigation of one particular device sold by a third-party marketplace seller.
#
# 1. How this started
The phone was intended as a gift for my grandmother.
I wasn't expecting flagship performance. I understand that the Redmi 15C is a budget smartphone.
However, its behavior was abnormal almost immediately.
The interface was extremely sluggish. Some system interactions stalled for several seconds, and Android logs later showed SystemUI-related ANR events.
I also observed the battery indicator dropping from approximately **20% to 4% in around five minutes**.
Initially, I suspected a poorly optimized HyperOS build, background applications, or defective hardware.
Then I noticed that Developer Options and USB debugging would become disabled after restarting the phone.
That was unusual enough to justify a closer look.
I connected the phone to my Linux computer and started collecting evidence using ADB.
For reference, the device identified itself as:
Model: 25078RA3EA
Device: dew_global
Fastboot product: dew
Platform: mt6768
HyperOS: OS2.0.214.0.VBNMIXN
The advertised configuration was **8GB RAM / 256GB storage**.
# 2. The RAM discrepancy: 8GB reported, 4 GiB accounted for by the kernel's zone information
Android reports:
/proc/meminfo:
MemTotal: 7880704 kB
The system settings also report:
miui_ram_size = 8.0GB
That looks consistent with an 8GB device.
However, I checked `/proc/zoneinfo`.
The recorded values were:
DMA32 present = 786432 pages
Normal present = 262144 pages
Total = 1048576 pages
The system page size is:
4096 bytes
Therefore:
1048576 × 4096
= 4294967296 bytes
= 4 GiB
This is a major discrepancy.
The kernel's zone information accounts for **4 GiB of present pages**, while `/proc/meminfo` reports almost 8GB.
The extended RAM feature was reported as disabled during the investigation.
**What this establishes:** Two different system interfaces
report incompatible memory information.
**What it does not establish:** I have not physically inspected the memory chips or obtained an independent hardware-level measurement. The kernel itself may have been modified, so its reports must also be treated cautiously.
My working hypothesis is that this may be a device with approximately **4GB of physical RAM being presented as an 8GB model**.
# 3. The storage discrepancy: 256GB in Android, approximately 104 GiB of userdata in Fastboot
Android showed a data filesystem size of approximately **226 GiB**, which would be consistent with a nominal 256GB storage configuration.
However, I rebooted the device into the bootloader and ran:
fastboot getvar all
The bootloader returned:
product: dew
is-userspace: no
partition-size:userdata: 1a14cf8000
partition-type:userdata: f2fs
Converting the hexadecimal partition size:
0x1a14cf8000
= 112018292736 bytes
≈ 104.325 GiB
That is much closer to what one might expect from a 128GB device after accounting for system partitions and other reserved space.
The same Fastboot output reported the `super` partition as 9 GiB.
Again, there is an important limitation.
**The size of the userdata partition is not the same thing as the total physical storage capacity.**
I cannot conclusively claim that the storage chip is 128GB without independently verifying the full device capacity and partition layout.
Nevertheless, Android presenting a roughly 226 GiB data filesystem while Fastboot reports a roughly 104 GiB userdata partition is a serious inconsistency.
Combined with the RAM discrepancy, it raises the possibility that a lower-specification device was modified to appear as the advertised 8/256GB variant.
# 4. Android says the bootloader is locked. Fastboot says it is unlocked.
This was another major finding.
Android reported:
ro.boot.flash.locked=1
ro.boot.vbmeta.device_state=locked
ro.boot.verifiedbootstate=green
But the actual bootloader interface reported:
unlocked: yes
secure: no
The Fastboot session was in bootloader mode, not userspace Fastboot:
is-userspace: no
In other words, the operating system presented the device as locked and verified, while the bootloader reported otherwise.
I am not claiming that Fastboot is an infallible independent hardware trust anchor.
However, these results should not be casually dismissed as normal behavior.
At minimum, the reported security state is inconsistent across interfaces.
This matters because users rely on bootloader state and verified-boot information to understand whether their device's operating system has been modified.
# 5. Unexpected root infrastructure was already running
I did not root this phone.
Yet the investigation found multiple active processes associated with root and runtime modification infrastructure.
Examples include:
zn-daemon
zn-nsdaemon-zygote
zn-zygisk-companion64 network_module
lspd
sdk_server
TEESimulator
The process tree included commands referencing:
/data/adb/ksu/bin/busybox
/data/adb/modules/network_module/service.sh
/data/adb/modules/zygisk_lsposed/service.sh
/data/adb/network/sdk_daemon.sh
The observed parent-child relationship included:
network_module/service.sh
|
v
sdk_server
|
v
TEESimulator
Eight investigated processes were running as UID 0, while `lspd` was running as UID 1000.
The processes reported the SELinux context:
u:r:ksu:s0
SELinux itself was reported as enforcing.
This is not ordinary stock-phone behavior.
These components indicate that the operating system contains an active root and runtime-modification infrastructure.
I have not established who installed it, why it was installed, or whether all of its components are malicious.
# 6. LSPosed was modifying the Android runtime
The investigation discovered two executable files associated with LSPosed that were accessible through existing bind mounts.
The logical source paths were:
**What it does not establish:** I have not physically inspected the memory chips or obtained an independent hardware-level measurement. The kernel itself may have been modified, so its reports must also be treated cautiously.
My working hypothesis is that this may be a device with approximately **4GB of physical RAM being presented as an 8GB model**.
# 3. The storage discrepancy: 256GB in Android, approximately 104 GiB of userdata in Fastboot
Android showed a data filesystem size of approximately **226 GiB**, which would be consistent with a nominal 256GB storage configuration.
However, I rebooted the device into the bootloader and ran:
fastboot getvar all
The bootloader returned:
product: dew
is-userspace: no
partition-size:userdata: 1a14cf8000
partition-type:userdata: f2fs
Converting the hexadecimal partition size:
0x1a14cf8000
= 112018292736 bytes
≈ 104.325 GiB
That is much closer to what one might expect from a 128GB device after accounting for system partitions and other reserved space.
The same Fastboot output reported the `super` partition as 9 GiB.
Again, there is an important limitation.
**The size of the userdata partition is not the same thing as the total physical storage capacity.**
I cannot conclusively claim that the storage chip is 128GB without independently verifying the full device capacity and partition layout.
Nevertheless, Android presenting a roughly 226 GiB data filesystem while Fastboot reports a roughly 104 GiB userdata partition is a serious inconsistency.
Combined with the RAM discrepancy, it raises the possibility that a lower-specification device was modified to appear as the advertised 8/256GB variant.
# 4. Android says the bootloader is locked. Fastboot says it is unlocked.
This was another major finding.
Android reported:
ro.boot.flash.locked=1
ro.boot.vbmeta.device_state=locked
ro.boot.verifiedbootstate=green
But the actual bootloader interface reported:
unlocked: yes
secure: no
The Fastboot session was in bootloader mode, not userspace Fastboot:
is-userspace: no
In other words, the operating system presented the device as locked and verified, while the bootloader reported otherwise.
I am not claiming that Fastboot is an infallible independent hardware trust anchor.
However, these results should not be casually dismissed as normal behavior.
At minimum, the reported security state is inconsistent across interfaces.
This matters because users rely on bootloader state and verified-boot information to understand whether their device's operating system has been modified.
# 5. Unexpected root infrastructure was already running
I did not root this phone.
Yet the investigation found multiple active processes associated with root and runtime modification infrastructure.
Examples include:
zn-daemon
zn-nsdaemon-zygote
zn-zygisk-companion64 network_module
lspd
sdk_server
TEESimulator
The process tree included commands referencing:
/data/adb/ksu/bin/busybox
/data/adb/modules/network_module/service.sh
/data/adb/modules/zygisk_lsposed/service.sh
/data/adb/network/sdk_daemon.sh
The observed parent-child relationship included:
network_module/service.sh
|
v
sdk_server
|
v
TEESimulator
Eight investigated processes were running as UID 0, while `lspd` was running as UID 1000.
The processes reported the SELinux context:
u:r:ksu:s0
SELinux itself was reported as enforcing.
This is not ordinary stock-phone behavior.
These components indicate that the operating system contains an active root and runtime-modification infrastructure.
I have not established who installed it, why it was installed, or whether all of its components are malicious.
# 6. LSPosed was modifying the Android runtime
The investigation discovered two executable files associated with LSPosed that were accessible through existing bind mounts.
The logical source paths were:
/data/adb/modules/zygisk_lsposed/bin/dex2oat32
/data/adb/modules/zygisk_lsposed/bin/dex2oat64
They were mounted over:
/apex/com.android.art/bin/dex2oat32
/apex/com.android.art/bin/dex2oat64
I copied the accessible binaries for static analysis.
The 32-bit wrapper was approximately 4.9KB, and the 64-bit wrapper approximately 7.1KB.
The 64-bit ELF analysis revealed code that:
1. Connects to an abstract Unix-domain socket.
2. Exchanges messages and receives file descriptors through `SCM_RIGHTS`.
3. Requests a hook library identified as `liboat_hook.so`.
4. Adds the argument `--inline-max-code-units=0`.
5. Sets `LD_PRELOAD` using a `/proc/<pid>/fd/<fd>` path.
6. Calls `fexecve()` to execute the received file descriptor.
The Unix socket name embedded in the binary matched an active socket visible in the device's socket tables.
This is consistent with an ART hooking mechanism.
**Crucially, I did not find RAM or storage spoofing logic in these two wrappers.**
The actual hook library and most of the module's files were not accessible.
Therefore, I cannot attribute the specification discrepancies to LSPosed specifically.
But the existence of runtime hooking infrastructure on a supposedly new, stock smartphone is itself a significant finding.
# 7. TEESimulator and injection into Android Keystore
This is one of the parts that concerns me most.
The logs from two separate boots showed TEESimulator reporting that it successfully loaded:
/data/adb/modules/network_module/sdk_tricky.so
into the Android `keystore2` process.
Related log entries referenced:
sdk_tricky.dex
libcertgen.so
keybox.xml
/data/adb/network
The logs also described loading package configurations and creating software-backed cryptographic operations.
Android Keystore is a security-sensitive component involved in cryptographic key management and hardware-backed security functionality.
The presence of a module attempting to modify its behavior deserves scrutiny.
One possible explanation is that this infrastructure was intended to simulate or manipulate device attestation or security-related responses.
However, I want to be precise:
* The logs report successful injection; I did not independently dump the target process's memory.
* I have not verified the contents of `keybox.xml`.
* I have not demonstrated a successful forged hardware attestation.
* I have not proven that cryptographic secrets were stolen.
* I have not established that the installed binaries match the source code of any similarly named open-source project.
I am reporting what the device actually logged, not claiming a proven compromise of every Android security mechanism.
# 8. I installed the official KernelSU Manager. It disappeared after reboot.
Because the running processes referenced KernelSU-related paths, I attempted to investigate using the official KernelSU Manager.
I obtained two releases from the official project:
KernelSU Manager v3.3.1
KernelSU Manager v0.9.5
Neither recognized the installed root implementation.
The newer version reported that the driver interface could not be accessed, including a syscall blocked by seccomp.
That result does not establish that the existing root infrastructure was absent.
After a reboot, the older manager was gone.
I had not manually uninstalled it.
The Android PackageManager log contained this entry:
11-16 11:15:36.396
pm_critical_info:
Uninstall pkg: me.weishu.kernelsu
u0 flags:2 from u0/3572 of null
Subsequent events confirmed that the package had been fully removed.
The important detail is:
from u0/3572
The uninstall request was attributed to UID 0.
My ADB shell was UID 2000 and had not been granted root access.
This means a privileged process requested the removal.
**I have not identified the specific process or script responsible.**
It would be premature to say that a particular root module deliberately removed the manager to hide itself.
Nevertheless, an official root-management app disappearing after a reboot, with a root-attributed uninstall event
/data/adb/modules/zygisk_lsposed/bin/dex2oat64
They were mounted over:
/apex/com.android.art/bin/dex2oat32
/apex/com.android.art/bin/dex2oat64
I copied the accessible binaries for static analysis.
The 32-bit wrapper was approximately 4.9KB, and the 64-bit wrapper approximately 7.1KB.
The 64-bit ELF analysis revealed code that:
1. Connects to an abstract Unix-domain socket.
2. Exchanges messages and receives file descriptors through `SCM_RIGHTS`.
3. Requests a hook library identified as `liboat_hook.so`.
4. Adds the argument `--inline-max-code-units=0`.
5. Sets `LD_PRELOAD` using a `/proc/<pid>/fd/<fd>` path.
6. Calls `fexecve()` to execute the received file descriptor.
The Unix socket name embedded in the binary matched an active socket visible in the device's socket tables.
This is consistent with an ART hooking mechanism.
**Crucially, I did not find RAM or storage spoofing logic in these two wrappers.**
The actual hook library and most of the module's files were not accessible.
Therefore, I cannot attribute the specification discrepancies to LSPosed specifically.
But the existence of runtime hooking infrastructure on a supposedly new, stock smartphone is itself a significant finding.
# 7. TEESimulator and injection into Android Keystore
This is one of the parts that concerns me most.
The logs from two separate boots showed TEESimulator reporting that it successfully loaded:
/data/adb/modules/network_module/sdk_tricky.so
into the Android `keystore2` process.
Related log entries referenced:
sdk_tricky.dex
libcertgen.so
keybox.xml
/data/adb/network
The logs also described loading package configurations and creating software-backed cryptographic operations.
Android Keystore is a security-sensitive component involved in cryptographic key management and hardware-backed security functionality.
The presence of a module attempting to modify its behavior deserves scrutiny.
One possible explanation is that this infrastructure was intended to simulate or manipulate device attestation or security-related responses.
However, I want to be precise:
* The logs report successful injection; I did not independently dump the target process's memory.
* I have not verified the contents of `keybox.xml`.
* I have not demonstrated a successful forged hardware attestation.
* I have not proven that cryptographic secrets were stolen.
* I have not established that the installed binaries match the source code of any similarly named open-source project.
I am reporting what the device actually logged, not claiming a proven compromise of every Android security mechanism.
# 8. I installed the official KernelSU Manager. It disappeared after reboot.
Because the running processes referenced KernelSU-related paths, I attempted to investigate using the official KernelSU Manager.
I obtained two releases from the official project:
KernelSU Manager v3.3.1
KernelSU Manager v0.9.5
Neither recognized the installed root implementation.
The newer version reported that the driver interface could not be accessed, including a syscall blocked by seccomp.
That result does not establish that the existing root infrastructure was absent.
After a reboot, the older manager was gone.
I had not manually uninstalled it.
The Android PackageManager log contained this entry:
11-16 11:15:36.396
pm_critical_info:
Uninstall pkg: me.weishu.kernelsu
u0 flags:2 from u0/3572 of null
Subsequent events confirmed that the package had been fully removed.
The important detail is:
from u0/3572
The uninstall request was attributed to UID 0.
My ADB shell was UID 2000 and had not been granted root access.
This means a privileged process requested the removal.
**I have not identified the specific process or script responsible.**
It would be premature to say that a particular root module deliberately removed the manager to hide itself.
Nevertheless, an official root-management app disappearing after a reboot, with a root-attributed uninstall event
in the logs, is highly unusual for a device sold as new.
# 9. Developer Options and USB debugging kept turning off
Every time the phone rebooted, I had to re-enable Developer Options and USB debugging.
I investigated the Settings and SecurityCenter APKs using JADX.
In the decompiled SecurityCenter code, I found a method named:
DevModeModel.optimize()
Its implementation includes operations that:
* Hide Developer Options in the UI.
* Send `com.android.settings.action.DEV_CLOSE`.
* Write `adb_enabled=0` to `Settings.Secure`.
* Write `development_settings_enabled=0` to `Settings.Global`.
This is a possible mechanism for disabling both features.
However, the static analysis did not establish that this method was called during boot.
I also ran temporary observers across controlled reboots.
They recorded both settings initially enabled, but the observers did not capture the exact transition to the disabled state.
So the responsible component remains unknown.
The fact that a method capable of disabling these settings exists is not, by itself, proof of malicious behavior.
# 10. A root-owned network socket was listening on port 15678
The investigation also found a TCP/IPv6 listening socket bound to a wildcard address:
Port: 15678
UID: 0
What I could not determine:
* The owning PID.
* The application protocol.
* Whether authentication was required.
* Whether the socket was reachable from outside the device.
* Whether it was related to any of the root modules.
I did not connect to it or perform active network probing.
This is a finding worth investigating, but **it is not proof of a remote-access backdoor**.
# 11. How much of the hidden root software could I actually extract?
Not much, unfortunately.
The final investigation performed **117 read attempts** against candidate module and executable paths.
Results:
Successful module-file reads: 2
Permission denied: 115
The two accessible files were the LSPosed ELF wrappers described above.
The main scripts remained inaccessible:
network_module/service.sh
network_module_ksu/service.sh
zygisk_lsposed/service.sh
sdk_daemon.sh
The contents of the root modules could not be reconstructed reliably from process names alone.
I did not exploit vulnerabilities, bypass permissions, inject code, modify SELinux, or flash the device to obtain further access.
The final root-investigation phase was read-only.
Earlier diagnostic steps did include user-authorized reboots and installation attempts involving official KernelSU Manager APKs.
# 12. After the factory reset, the phone switched to Chinese
After preserving the diagnostic evidence, I performed a factory reset in preparation for returning the phone.
The phone had been sold as a **Global** Redmi 15C.
Following the reset, its initial system interface and power menu appeared in Chinese.
I had not completed the HyperOS setup wizard at that point.
This was surprising, given how the phone had originally presented itself.
However, I cannot claim that this alone proves the device is a Chinese-market variant.
A reset can change locale settings, and I have not yet verified whether Russian or English remains available in the setup language selector.
I am including this observation because it occurred after the other discrepancies had already been documented.
# 13. What I actually preserved
The investigation generated a substantial evidence archive containing:
* Original ADB and Fastboot output.
* Android boot logs.
* Kernel memory and process information.
* PackageManager uninstall events.
* Process ancestry and SELinux contexts.
* Socket tables and mount information.
* Copies of accessible ELF binaries.
* Decompiled Android application classes.
* APK and DEX inventories.
* SHA-256 hashes.
* Static-analysis reports.
* Screenshots and video evidence of the specification discrepancies.
The archive includes separate technical reports covering the initial diagnosis and the root-component investigation.
The analysis was performed using Linux, ADB, Fastboot, Python, JADX, `readelf`,
# 9. Developer Options and USB debugging kept turning off
Every time the phone rebooted, I had to re-enable Developer Options and USB debugging.
I investigated the Settings and SecurityCenter APKs using JADX.
In the decompiled SecurityCenter code, I found a method named:
DevModeModel.optimize()
Its implementation includes operations that:
* Hide Developer Options in the UI.
* Send `com.android.settings.action.DEV_CLOSE`.
* Write `adb_enabled=0` to `Settings.Secure`.
* Write `development_settings_enabled=0` to `Settings.Global`.
This is a possible mechanism for disabling both features.
However, the static analysis did not establish that this method was called during boot.
I also ran temporary observers across controlled reboots.
They recorded both settings initially enabled, but the observers did not capture the exact transition to the disabled state.
So the responsible component remains unknown.
The fact that a method capable of disabling these settings exists is not, by itself, proof of malicious behavior.
# 10. A root-owned network socket was listening on port 15678
The investigation also found a TCP/IPv6 listening socket bound to a wildcard address:
Port: 15678
UID: 0
What I could not determine:
* The owning PID.
* The application protocol.
* Whether authentication was required.
* Whether the socket was reachable from outside the device.
* Whether it was related to any of the root modules.
I did not connect to it or perform active network probing.
This is a finding worth investigating, but **it is not proof of a remote-access backdoor**.
# 11. How much of the hidden root software could I actually extract?
Not much, unfortunately.
The final investigation performed **117 read attempts** against candidate module and executable paths.
Results:
Successful module-file reads: 2
Permission denied: 115
The two accessible files were the LSPosed ELF wrappers described above.
The main scripts remained inaccessible:
network_module/service.sh
network_module_ksu/service.sh
zygisk_lsposed/service.sh
sdk_daemon.sh
The contents of the root modules could not be reconstructed reliably from process names alone.
I did not exploit vulnerabilities, bypass permissions, inject code, modify SELinux, or flash the device to obtain further access.
The final root-investigation phase was read-only.
Earlier diagnostic steps did include user-authorized reboots and installation attempts involving official KernelSU Manager APKs.
# 12. After the factory reset, the phone switched to Chinese
After preserving the diagnostic evidence, I performed a factory reset in preparation for returning the phone.
The phone had been sold as a **Global** Redmi 15C.
Following the reset, its initial system interface and power menu appeared in Chinese.
I had not completed the HyperOS setup wizard at that point.
This was surprising, given how the phone had originally presented itself.
However, I cannot claim that this alone proves the device is a Chinese-market variant.
A reset can change locale settings, and I have not yet verified whether Russian or English remains available in the setup language selector.
I am including this observation because it occurred after the other discrepancies had already been documented.
# 13. What I actually preserved
The investigation generated a substantial evidence archive containing:
* Original ADB and Fastboot output.
* Android boot logs.
* Kernel memory and process information.
* PackageManager uninstall events.
* Process ancestry and SELinux contexts.
* Socket tables and mount information.
* Copies of accessible ELF binaries.
* Decompiled Android application classes.
* APK and DEX inventories.
* SHA-256 hashes.
* Static-analysis reports.
* Screenshots and video evidence of the specification discrepancies.
The archive includes separate technical reports covering the initial diagnosis and the root-component investigation.
The analysis was performed using Linux, ADB, Fastboot, Python, JADX, `readelf`,
`strings`, and `llvm-objdump`, with assistance from OpenAI Codex.
I have not published the raw archive yet because it may contain serial numbers, device identifiers, package information, and other potentially sensitive data.
I would need to sanitize it first.
# 14. My current interpretation
I see three major issues.
**First: The advertised hardware specifications are questionable.**
The 4 GiB physical-page accounting and 104.3 GiB Fastboot userdata partition are consistent with the possibility of a lower-specification device being presented as an 8/256GB model.
That is a strong hypothesis, not a confirmed identification of the physical chips.
**Second: The software environment is clearly not an ordinary untouched stock installation.**
The running root infrastructure, LSPosed modifications, and Keystore-related injection logs demonstrate substantial modifications.
**Third: The device's security reporting cannot be trusted at face value.**
The conflicting bootloader states, unexpected privileged package removal, and repeated disabling of debugging features make the system difficult to assess.
I do not know whether the seller installed these modifications, whether the phone was refurbished, whether it originated from another market, or whether some earlier party modified it.
I am not accusing Xiaomi of installing this software.
I am describing the state of one device that was sold to me as new.
# Conclusion
This investigation documents a Redmi 15C sold as a new Global 8GB/256GB device, with substantial inconsistencies in hardware reporting, bootloader state, and operating-system integrity.
The evidence includes:
* A discrepancy between approximately 8GB reported by /proc/meminfo and 4 GiB accounted for by /proc/zoneinfo.
* A discrepancy between Android's reported storage capacity and the Fastboot userdata partition size.
* Conflicting bootloader security states reported by Android and Fastboot.
* Active root infrastructure, LSPosed-related ART modifications, and logs reporting injection into keystore2.
* An unexpected KernelSU Manager uninstall request attributed to UID 0.
These observations establish that the device's software environment was substantially modified. They do not conclusively establish the physical RAM or storage capacity, identify the party responsible, or prove malicious intent.
This case illustrates why Android-reported specifications and security properties should not always be treated as independent evidence of device integrity.
The findings apply to this particular device and should not be generalized to all Redmi 15C units or Xiaomi devices.
# Visual Evidence
Screenshots documenting the RAM, storage, and bootloader security-state discrepancies:
[https://imgur.com/a/XQ4ANzo](https://imgur.com/a/XQ4ANzo)
The screenshots contain Russian annotations. All measurements, calculations, and their limitations are explained in the technical sections above.
https://redd.it/1xxlyyw
@reddit_android
I have not published the raw archive yet because it may contain serial numbers, device identifiers, package information, and other potentially sensitive data.
I would need to sanitize it first.
# 14. My current interpretation
I see three major issues.
**First: The advertised hardware specifications are questionable.**
The 4 GiB physical-page accounting and 104.3 GiB Fastboot userdata partition are consistent with the possibility of a lower-specification device being presented as an 8/256GB model.
That is a strong hypothesis, not a confirmed identification of the physical chips.
**Second: The software environment is clearly not an ordinary untouched stock installation.**
The running root infrastructure, LSPosed modifications, and Keystore-related injection logs demonstrate substantial modifications.
**Third: The device's security reporting cannot be trusted at face value.**
The conflicting bootloader states, unexpected privileged package removal, and repeated disabling of debugging features make the system difficult to assess.
I do not know whether the seller installed these modifications, whether the phone was refurbished, whether it originated from another market, or whether some earlier party modified it.
I am not accusing Xiaomi of installing this software.
I am describing the state of one device that was sold to me as new.
# Conclusion
This investigation documents a Redmi 15C sold as a new Global 8GB/256GB device, with substantial inconsistencies in hardware reporting, bootloader state, and operating-system integrity.
The evidence includes:
* A discrepancy between approximately 8GB reported by /proc/meminfo and 4 GiB accounted for by /proc/zoneinfo.
* A discrepancy between Android's reported storage capacity and the Fastboot userdata partition size.
* Conflicting bootloader security states reported by Android and Fastboot.
* Active root infrastructure, LSPosed-related ART modifications, and logs reporting injection into keystore2.
* An unexpected KernelSU Manager uninstall request attributed to UID 0.
These observations establish that the device's software environment was substantially modified. They do not conclusively establish the physical RAM or storage capacity, identify the party responsible, or prove malicious intent.
This case illustrates why Android-reported specifications and security properties should not always be treated as independent evidence of device integrity.
The findings apply to this particular device and should not be generalized to all Redmi 15C units or Xiaomi devices.
# Visual Evidence
Screenshots documenting the RAM, storage, and bootloader security-state discrepancies:
[https://imgur.com/a/XQ4ANzo](https://imgur.com/a/XQ4ANzo)
The screenshots contain Russian annotations. All measurements, calculations, and their limitations are explained in the technical sections above.
https://redd.it/1xxlyyw
@reddit_android
Imgur
proof
Discover the magic of the internet at Imgur, a community powered entertainment destination. Lift your spirits with funny jokes, trending memes, entertaining gifs, inspiring stories, viral videos, and so much more from users.
Samsung Begins One UI 9.5 Beta Program
https://news.samsung.com/global/samsung-begins-one-ui-9-5-beta-program
https://redd.it/1xzgtmo
@reddit_android
https://news.samsung.com/global/samsung-begins-one-ui-9-5-beta-program
https://redd.it/1xzgtmo
@reddit_android
Samsung Global Newsroom
Samsung Begins One UI 9.5 Beta Program - Samsung Global Newsroom
Samsung has launched the One UI 9.5 beta program, giving users an early look at One UI 9.5
Elevating games: New large screens and foldables quality standards on Google Play
https://developer.android.com/blog/posts/elevating-game-quality-foldables-large-screens-google-play
https://redd.it/1xzmgvf
@reddit_android
https://developer.android.com/blog/posts/elevating-game-quality-foldables-large-screens-google-play
https://redd.it/1xzmgvf
@reddit_android
Android Developers
Elevating games: New large screens and foldables quality standards on Google Play | Android Developers' Blog
To give these experiences to players and ensure your games shine across every screen size, Google Play is introducing new large screen quality requiremen…
Elevating apps: New adaptive quality standards on Google Play
https://developer.android.com/blog/posts/google-play-adaptive-quality-standards
https://redd.it/1xzmio5
@reddit_android
https://developer.android.com/blog/posts/google-play-adaptive-quality-standards
https://redd.it/1xzmio5
@reddit_android
Android Developers
Elevating apps: New adaptive quality standards on Google Play | Android Developers' Blog
To give users the premium experience they expect and ensure your apps shine across every screen size, Google Play is introducing new adaptive app quality…
Lock your apps with app lock, available for testing in the Android 17 QPR3 beta!
Hi Reddit,
I’m excited to give you a preview of a highly requested security feature coming to Android: App lock.
App lock addresses multiple user concerns relating to phone theft and device sharing. Many of you have asked for a feature like this to add an extra layer of protection to apps that lack their own built-in app locks, such as some social media apps, mail apps, or cloud storage apps. We’ve also heard that many of you want a feature like this so you can hand your unlocked phone to a friend or family member without worrying about them snooping through your private apps.
# Introducing App Lock
App lock is a new, easy to use security feature that allows you to quickly lock apps to prevent unauthorized access.
When an app is locked, it can’t be launched without entering your device credential (PIN, pattern, or password) or biometric. While an app is locked, its notification content is hidden, widgets and shortcuts are removed, and content in the recents screen is redacted.
https://preview.redd.it/nsikg4ol5f2i1.png?width=2048&format=png&auto=webp&s=f4fe1b2758e5601b9b90ba931fbebc4032ceaf0c
Pixel users can test the app lock feature on their devices starting with the Android 17 QPR3 Beta 3 release.
If you have a Pixel device enrolled in the Android Beta program, please help us test it! The product team is planning to release the app lock feature with the Android 17 QPR3 platform release in Q1 2027, and any feedback you can share with us will help us to deliver a seamless, high-quality app locking experience.
# How to lock an app
You can quickly lock apps from your home screen or manage them in bulk via Settings:
Lock an app via the home screen: Long-press the app icon, select "App lock," and authenticate using your device credential (PIN, pattern, or password) or biometric.
Lock apps in Settings: Go to Settings > Security & privacy > App lock, authenticate, and enable app lock for one or more apps.
# How to disable app lock
Disable app lock via the home screen: Long-press the app icon, select "Remove app lock," and authenticate using your device credential (PIN, pattern, or password) or biometric.
Disable app lock in Settings: Go to Settings > Security & privacy > App lock, authenticate, and disable app lock for one or more apps.
# FAQs
Is app lock available for all apps?
App lock is available for all apps except for certain preloaded apps and apps that hold certain roles.
Can data from locked apps still be accessed by other apps?
AI agents and services you've allowed to access locked apps will still be able to access their data. Furthermore, photos and videos from locked apps may still show in other apps that have access to your photos and videos. For more protection, we recommend using private space.
Does an app reveal that it is locked through any visual cues on your home screen?
No, it does not. To avoid potential privacy issues, the icon for a locked app will remain unchanged.
Does app lock work with alternative launchers?
Yes, app lock works with alternative launchers. When set as the default home app, alternative launchers can utilize new APIs available starting in Android 17 QPR2 to trigger app lock enablement and disablement from the home screen on devices that support the feature.
When do locked apps relock after I unlock them?
Once you authenticate to open a locked app, it stays unlocked while it's in the foreground and for a short grace period after you leave it. Locked apps also lock immediately whenever you lock your device.
Try this feature out today in the Android 17 QPR3 Beta and let us know in the comments if you have any feedback!
https://redd.it/1xznwhs
@reddit_android
Hi Reddit,
I’m excited to give you a preview of a highly requested security feature coming to Android: App lock.
App lock addresses multiple user concerns relating to phone theft and device sharing. Many of you have asked for a feature like this to add an extra layer of protection to apps that lack their own built-in app locks, such as some social media apps, mail apps, or cloud storage apps. We’ve also heard that many of you want a feature like this so you can hand your unlocked phone to a friend or family member without worrying about them snooping through your private apps.
# Introducing App Lock
App lock is a new, easy to use security feature that allows you to quickly lock apps to prevent unauthorized access.
When an app is locked, it can’t be launched without entering your device credential (PIN, pattern, or password) or biometric. While an app is locked, its notification content is hidden, widgets and shortcuts are removed, and content in the recents screen is redacted.
https://preview.redd.it/nsikg4ol5f2i1.png?width=2048&format=png&auto=webp&s=f4fe1b2758e5601b9b90ba931fbebc4032ceaf0c
Pixel users can test the app lock feature on their devices starting with the Android 17 QPR3 Beta 3 release.
If you have a Pixel device enrolled in the Android Beta program, please help us test it! The product team is planning to release the app lock feature with the Android 17 QPR3 platform release in Q1 2027, and any feedback you can share with us will help us to deliver a seamless, high-quality app locking experience.
# How to lock an app
You can quickly lock apps from your home screen or manage them in bulk via Settings:
Lock an app via the home screen: Long-press the app icon, select "App lock," and authenticate using your device credential (PIN, pattern, or password) or biometric.
Lock apps in Settings: Go to Settings > Security & privacy > App lock, authenticate, and enable app lock for one or more apps.
# How to disable app lock
Disable app lock via the home screen: Long-press the app icon, select "Remove app lock," and authenticate using your device credential (PIN, pattern, or password) or biometric.
Disable app lock in Settings: Go to Settings > Security & privacy > App lock, authenticate, and disable app lock for one or more apps.
# FAQs
Is app lock available for all apps?
App lock is available for all apps except for certain preloaded apps and apps that hold certain roles.
Can data from locked apps still be accessed by other apps?
AI agents and services you've allowed to access locked apps will still be able to access their data. Furthermore, photos and videos from locked apps may still show in other apps that have access to your photos and videos. For more protection, we recommend using private space.
Does an app reveal that it is locked through any visual cues on your home screen?
No, it does not. To avoid potential privacy issues, the icon for a locked app will remain unchanged.
Does app lock work with alternative launchers?
Yes, app lock works with alternative launchers. When set as the default home app, alternative launchers can utilize new APIs available starting in Android 17 QPR2 to trigger app lock enablement and disablement from the home screen on devices that support the feature.
When do locked apps relock after I unlock them?
Once you authenticate to open a locked app, it stays unlocked while it's in the foreground and for a short grace period after you leave it. Locked apps also lock immediately whenever you lock your device.
Try this feature out today in the Android 17 QPR3 Beta and let us know in the comments if you have any feedback!
https://redd.it/1xznwhs
@reddit_android
This Cool Signal Alternative Is Now on Android
https://www.wired.com/story/germ-dm-is-now-available-on-android
https://redd.it/1xzjm5q
@reddit_android
https://www.wired.com/story/germ-dm-is-now-available-on-android
https://redd.it/1xzjm5q
@reddit_android
WIRED
This Cool Signal Alternative Is Now on Android
Germ DM is an encrypted messaging platform that uses “burner cards” instead of phone numbers or usernames to compartmentalize your conversations.
Exclusive: Samsung Galaxy Buds Active Revealed With Ear Hooks, IP68 and ANC
https://sammyguru.com/samsung-galaxy-buds-active-features-specs-exclusive/
https://redd.it/1xzxh7h
@reddit_android
https://sammyguru.com/samsung-galaxy-buds-active-features-specs-exclusive/
https://redd.it/1xzxh7h
@reddit_android
SammyGuru
Exclusive: Samsung Galaxy Buds Active Revealed With Ear Hooks, IP68 and ANC
Exclusive findings reveal Samsung Galaxy Buds Active with ear hooks, IP68 protection, ANC, 360 Audio, and UHQ audio.
The Gemini app is now available on lower-memory Android devices
https://blog.google/innovation-and-ai/products/gemini-app/gemini-lower-memory-devices/
https://redd.it/1xzzhzf
@reddit_android
https://blog.google/innovation-and-ai/products/gemini-app/gemini-lower-memory-devices/
https://redd.it/1xzzhzf
@reddit_android
Google
The Gemini app is now available on lower-memory Android devices.
The Google Gemini app now supports lower-memory Android devices. Access Gemini Live and custom image creation on your phone. Download the app today.
Exclusive: Galaxy Studio Has an 870mAh Battery, Wear Detection and a 3.5mm Jack
https://sammyguru.com/samsung-galaxy-studio-features-specs-exclusive/?utm_source=twitter&utm_medium=social&utm_campaign=2026-11-18&utm_content=samsung-galaxy-studio-features-specs-exclusive
https://redd.it/1xzzghh
@reddit_android
https://sammyguru.com/samsung-galaxy-studio-features-specs-exclusive/?utm_source=twitter&utm_medium=social&utm_campaign=2026-11-18&utm_content=samsung-galaxy-studio-features-specs-exclusive
https://redd.it/1xzzghh
@reddit_android
SammyGuru
Exclusive: Galaxy Studio Has an 870mAh Battery, Wear Detection and a 3.5mm Jack
Exclusive APK findings reveal Samsung's Galaxy Studio headphones with ANC, 360 Audio, an 870mAh battery, wear detection, and USB-C and 3.5mm wired audio.
I built an ultra-lightweight TUI launcher (15–20MB RAM) that brings modern LLM AI back to 10-year-old Android devices (Android 5.0+)
Hi r/Android!
Like many of you, I have a drawer with a few older Android phones (Galaxy S4/S5 era, Nexus 5, old budget MediaTek phones). Hardware-wise, they are still fine, but modern Android apps and web browsers have made them virtually unusable. Heavy web frameworks crash under 1GB RAM, Google Play Services drain what's left of the battery, and modern AI tools like ChatGPT or Gemini require Android 10+.
I wanted to see if I could give these legacy devices a genuinely useful second life in 2026. So I built **Tdroid** — a pure text-based (TUI) launcher designed from the ground up for minimal resource usage, privacy, and speed.
\---
\### 🧠 The LLM / AI Integration
The biggest challenge on older devices (Android 5.0 Lollipop & 6.0 Marshmallow) is running modern AI. Heavy web apps freeze the browser, and TLS certificate issues often block HTTPS calls on ancient WebViews.
In Tdroid:
\- Built a native, lightweight network engine with proper TLS support.
\- Integrated a direct **AI Chat** interface that opens instantly without waiting for a browser engine to spin up.
\- Added quick command-line queries directly from the home screen: simply type `ai <your question>` to get answers.
\- Works smoothly even on single/dual-core chips without lag or thermal throttling.
\---
\### ⚡ Key Features & Performance:
\- **Tiny footprint:** Consumes only **15–25 MB of RAM** (idle is under 20MB). Zero background battery drain.
\- **Direct Canvas Rendering:** No Compose, no heavy XML hierarchies, no WebViews — just high-speed monospace terminal rendering.
\- **Two Releases:**
\- **Modern Edition (Android 7.0 – 15):** Full sensor bars, dynamic themes, Material-styled TUI.
\- **Legacy Pro Edition (Android 5.0 – 6.0+ / API 21+):** Backported and verified specifically for old hardware.
\- **Built-in Offline Ecosystem:**
\- Dual-pane **T-Commander** (full file manager with SD card, FTP, WebDAV).
\- Quick notes, task manager, TXT book reader, scientific calculator.
\- Built-in **TDScript IDE** with bytecode execution for lightweight terminal automation.
\- 14 retro terminal games (Snake, Tetris, 2048, Roguelike, Space Invaders).
\- 100% functional without Google Play Services or an active internet connection (except for LLM queries).
\---
\### 📲 Download & Testing
The project is available for both modern phones and older devices:
\- **Download APK directly:** [https://fido2465724100-creator.github.io/my-developer-site/\](https://fido2465724100-creator.github.io/my-developer-site/)
*(For Android 5/6 devices, look for the `Tdroid-Pro-Legacy.apk` package in the green legacy download card).*
I'd love to hear your feedback, bug reports, and see what old hardware you manage to revive with it!
https://redd.it/1xzubee
@reddit_android
Hi r/Android!
Like many of you, I have a drawer with a few older Android phones (Galaxy S4/S5 era, Nexus 5, old budget MediaTek phones). Hardware-wise, they are still fine, but modern Android apps and web browsers have made them virtually unusable. Heavy web frameworks crash under 1GB RAM, Google Play Services drain what's left of the battery, and modern AI tools like ChatGPT or Gemini require Android 10+.
I wanted to see if I could give these legacy devices a genuinely useful second life in 2026. So I built **Tdroid** — a pure text-based (TUI) launcher designed from the ground up for minimal resource usage, privacy, and speed.
\---
\### 🧠 The LLM / AI Integration
The biggest challenge on older devices (Android 5.0 Lollipop & 6.0 Marshmallow) is running modern AI. Heavy web apps freeze the browser, and TLS certificate issues often block HTTPS calls on ancient WebViews.
In Tdroid:
\- Built a native, lightweight network engine with proper TLS support.
\- Integrated a direct **AI Chat** interface that opens instantly without waiting for a browser engine to spin up.
\- Added quick command-line queries directly from the home screen: simply type `ai <your question>` to get answers.
\- Works smoothly even on single/dual-core chips without lag or thermal throttling.
\---
\### ⚡ Key Features & Performance:
\- **Tiny footprint:** Consumes only **15–25 MB of RAM** (idle is under 20MB). Zero background battery drain.
\- **Direct Canvas Rendering:** No Compose, no heavy XML hierarchies, no WebViews — just high-speed monospace terminal rendering.
\- **Two Releases:**
\- **Modern Edition (Android 7.0 – 15):** Full sensor bars, dynamic themes, Material-styled TUI.
\- **Legacy Pro Edition (Android 5.0 – 6.0+ / API 21+):** Backported and verified specifically for old hardware.
\- **Built-in Offline Ecosystem:**
\- Dual-pane **T-Commander** (full file manager with SD card, FTP, WebDAV).
\- Quick notes, task manager, TXT book reader, scientific calculator.
\- Built-in **TDScript IDE** with bytecode execution for lightweight terminal automation.
\- 14 retro terminal games (Snake, Tetris, 2048, Roguelike, Space Invaders).
\- 100% functional without Google Play Services or an active internet connection (except for LLM queries).
\---
\### 📲 Download & Testing
The project is available for both modern phones and older devices:
\- **Download APK directly:** [https://fido2465724100-creator.github.io/my-developer-site/\](https://fido2465724100-creator.github.io/my-developer-site/)
*(For Android 5/6 devices, look for the `Tdroid-Pro-Legacy.apk` package in the green legacy download card).*
I'd love to hear your feedback, bug reports, and see what old hardware you manage to revive with it!
https://redd.it/1xzubee
@reddit_android
Samsung’s Android Laptop Is Codenamed Origin, and New Screenshots Show It Running One UI
https://sammyguru.com/samsung-origin-android-laptop-app-streaming/
https://redd.it/1y0afoi
@reddit_android
https://sammyguru.com/samsung-origin-android-laptop-app-streaming/
https://redd.it/1y0afoi
@reddit_android
SammyGuru
Samsung’s Android Laptop Is Codenamed Origin, and New Screenshots Show It Running One UI
Samsung’s upcoming Android laptop finally has a name, at least inside the company — it's codenamed Origin.
Xiaomi 18 Pro (Global) review - GSMArena
https://gsmarena.com/xiaomi_18_pro-review-3015.php
https://redd.it/1y09v87
@reddit_android
https://gsmarena.com/xiaomi_18_pro-review-3015.php
https://redd.it/1y09v87
@reddit_android
GSMArena.com
Xiaomi 18 Pro (Global) review
The Xiaomi 18 Pro is here, and Xiaomi seems determined to prove that a compact flagship doesn't have to make serious compromises. With a 6.4-inch display,...
Exclusive: Here’s the Motorola Razr Flex, a Wide Rival to the Galaxy Z Fold 8
https://sammyguru.com/exclusive-motorola-razr-flex/
https://redd.it/1y0bxw3
@reddit_android
https://sammyguru.com/exclusive-motorola-razr-flex/
https://redd.it/1y0bxw3
@reddit_android
SammyGuru
Exclusive: Here's the Motorola Razr Flex, a Wide Rival to the Galaxy Z Fold 8
SammyGuru can show you the Motorola Razr Flex, Motorola's first wide book-style foldable and a Galaxy Z Fold 8 rival, in green and beige.
TSMC and Samsung pause some chip shipments to China due to new US export rules: report
https://seekingalpha.com/news/4674687-tsmc-and-samsung-pause-some-chip-shipments-to-china-due-to-new-us-export-rules-report
https://redd.it/1y0cmfh
@reddit_android
https://seekingalpha.com/news/4674687-tsmc-and-samsung-pause-some-chip-shipments-to-china-due-to-new-us-export-rules-report
https://redd.it/1y0cmfh
@reddit_android
Seeking Alpha
TSMC and Samsung pause some chip shipments to China due to new US export rules: report
TSMC and Samsung pause some chip shipments to China under new U.S.
Samsung’s Origin laptops will plug into the Galaxy ecosystem, and One UI is laying the foundation
https://www.androidauthority.com/samsung-origin-laptops-galaxy-ecosystem-apk-teardown-3737235/
https://redd.it/1y0ci9l
@reddit_android
https://www.androidauthority.com/samsung-origin-laptops-galaxy-ecosystem-apk-teardown-3737235/
https://redd.it/1y0ci9l
@reddit_android
Android Authority
Samsung’s Origin laptops will plug into the Galaxy ecosystem, and One UI is laying the foundation
One UI 9.5 Beta 1 code shows Samsung's Origin laptops will plug into the Galaxy ecosystem with Multi Control, Smart View, and Galaxy AI.