Android - Reddit
1.22K subscribers
16 photos
1 video
34.3K links
Stay up-to-date with everything Android!
Content directly fetched from the subreddit just for you.

Powered by : @r_channels
Download Telegram
I built a family check-in app that doesn't use GPS. Looking for feedback

Hey,



I published an Android app called Closer and wanted some honest feedback from people here.I basically got tired of "family safety" apps that are just location tracking. I don't want a map of where someone is. I just want to know they're okay.

Closer works like this:

\-You invite someone and share a private confirmation number.

\-You send a check-in, either now or on a schedule.

They confirm by tapping that number.

\-f they miss it, get it wrong, or say they're not okay, you get an alert and can call or text them

No GPS or live tracking. Just check-ins with people you trust.

Free version is 1 person and simple once-a-day schedules. There's an optional Plus upgrade if you need more.



Play Store:

https://play.google.com/store/apps/details?id=com.polyhistor.closer

Moe info:

https://closer-family-safety.com



Happy to answer questions.

https://redd.it/1v3ip9g
@reddit_android
Synco — open source, local-first sync between your Android phone and desktop. No cloud, no lag.

Built Synco because I got tired of reaching for my phone during deep work. It mirrors notifications, controls media playback, and routes calls between your Android phone and desktop — all over your local Wi-Fi. Zero cloud, end-to-end encrypted, free.

What it does:

\- Notification mirroring (WhatsApp, Slack, Gmail, etc.) straight to your desktop

\- Real-time call handling — answer/decline from your keyboard

\- Media telemetry & audio routing intelligence

\- Works over Local Wi-Fi, Direct Hotspot, or Bluetooth LE

\- E2EE using Curve25519 + AES-256-GCM

No signup, no cloud, no tracking. Just a direct encrypted link between your devices.

Completely free & open source: https://github.com/Dhruvesh-Dabhade/Synco

https://redd.it/1v3ezdr
@reddit_android
Daily Superthread (Jul 23 2026) - Your daily thread for questions, device recommendations and general discussions!

Note 1. You can search for previous daily threads.

Note 2. Join our IRC and Telegram chat-rooms! Please see our wiki for instructions.

Please post your questions here. Feel free to use this thread for general questions/discussion as well.

https://redd.it/1v4bvph
@reddit_android
Video aspect ratio comparison with the Samsung Galaxy S26 Ultra, Fold8, and Fold8 Ultra

16:9 - S26U landscape, Fold8 portrait unfolded, Fold8U portrait unfolded

16:9 - S26U landscape, Fold8 portrait unfolded, Fold8U landscape unfolded

4:3 - S26U landscape, Fold8 portrait unfolded, Fold8U portrait unfolded

4:3 - S26U landscape, Fold8 portrait unfolded, Fold8U landscape unfolded

21:9 - S26U landscape, Fold8 portrait unfolded, Fold8U portrait unfolded

21:9 - S26U landscape, Fold8 portrait unfolded, Fold8U landscape unfolded

16:9 – S26U portrait, Fold8 portrait folded, Fold8U portrait folded

16:9 – S26U landscape, Fold8 landscape folded, Fold8U landscape folded

4:3 – S26U portrait, Fold8 portrait folded, Fold8U portrait folded

4:3 – S26U landscape, Fold8 landscape folded, Fold8U landscape folded

21:9 – S26U portrait, Fold8 portrait folded, Fold8U portrait folded

21:9 – S26U landscape, Fold8 landscape folded, Fold8U landscape folded

9:16 – S26U portrait, Fold8 portrait folded, Fold8U portrait folded

9:16 – S26U portrait, Fold8 portrait unfolded, Fold8U portrait unfolded

9:16 – S26U portrait, Fold8 landscape folded, Fold8U landscape folded

Disclosure: The S26 Ultra, Fold8, and Fold8 Ultra are on loan from Samsung.

Special thanks to u/welp\_im\_damned for putting together the videos.

Picture captions below in case the Reddit ones don't work:

1.      16:9 - S26U landscape, Fold8 portrait unfolded, Fold8U portrait unfolded

2.      16:9 - S26U landscape, Fold8 portrait unfolded, Fold8U landscape unfolded

3.      4:3 - S26U landscape, Fold8 portrait unfolded, Fold8U portrait unfolded

4.      4:3 - S26U landscape, Fold8 portrait unfolded, Fold8U landscape unfolded

5.      21:9 - S26U landscape, Fold8 portrait unfolded, Fold8U portrait unfolded

6.      21:9 - S26U landscape, Fold8 portrait unfolded, Fold8U landscape unfolded

7.      16:9 – S26U portrait, Fold8 portrait folded, Fold8U portrait folded

8.      16:9 – S26U landscape, Fold8 landscape folded, Fold8U landscape folded

9.      4:3 – S26U portrait, Fold8 portrait folded, Fold8U portrait folded

10.  4:3 – S26U landscape, Fold8 landscape folded, Fold8U landscape folded

11.  21:9 – S26U portrait, Fold8 portrait folded, Fold8U
portrait folded

12.  21:9 – S26U landscape, Fold8 landscape folded, Fold8U landscape folded

13.  9:16 – S26U portrait, Fold8 portrait folded, Fold8U portrait folded

14.  9:16 – S26U portrait, Fold8 portrait unfolded, Fold8U portrait unfolded

15.  9:16 – S26U portrait, Fold8 landscape folded, Fold8U landscape folded

https://redd.it/1v4wap9
@reddit_android
Severe Battery Drain & Overheating on HyperOS (Redmi Note 13 Pro 4G / MediaTek). Root Cause Found: Infinite Loop in SatelliteController

PSA: I am posting this root cause analysis to document a severe flaw in the Android 14 / AOSP telephony framework implementation on MediaTek devices. I am not asking for tech support, but sharing the ADB logs and AOSP source code flaw for community awareness and developer visibility.

Device: Redmi Note 13 Pro 4G (MediaTek)

OS: HyperOS (Android 14) - Build 3.0.301.0.WNFEUXM

There is a severe logic bug in the telephony framework of the current HyperOS build. Using Mobile Data triggers an infinite event loop inside com.android.phone, locking the CPU at 140%+ usage and causing massive battery drain and thermal throttling. The device overheats, and the only temporary workaround is to toggle Airplane Mode (just turning off mobile data does nothing).

Using top -m 15, com.android.phone (PID 3173) consistently shows >140% CPU usage. The MediaTek RIL daemon (mtkfusionrild) is also constantly stressed.

By analyzing the radio buffer via logcat, I was able to pinpoint the exact root cause: the system is trying to register satellite modem listeners on a device that does not have satellite hardware.

The following block of code repeats in an infinite loop (around 30 times per second) as soon as mobile data connects:

07-24 00:15:24.708 3173 3173 D SatelliteController: Satellite for carrier is not supported.
07-24 00:15:24.709 3173 3173 D SatelliteController: registerForSatelliteModemStateChanged: add Listeners for ModemState
07-24 00:15:24.709 3173 3173 E SatelliteController: registerForSatelliteModemStateChanged: mSatelliteSessionController is not initialized yet
07-24 00:15:24.709 3173 3173 E SatelliteController: unregisterForModemStateChanged: mSatelliteSessionController is not initialized yet
07-24 00:15:24.709 3173 3173 D SatelliteController: unregisterForModemStateChanged: remove Listeners for ModemState

After digging deeper and cross-referencing with the AOSP source code and MediaTek vendor trees, it is clear this is an issue rooted in the telephony framework handling for Android 14 on MediaTek devices (this exact same INVALID_ARGUMENTS and mSatelliteSessionController loop has also been reproduced on Custom ROMs like crDroid for the Redmi Note 13 5G 'stone').

Looking at the AOSP source code (frameworks/opt/telephony/.../SatelliteController.java), the exception is correctly generated here:

.SatelliteError public int registerForSatelliteModemStateChanged(int subId,
@NonNull ISatelliteStateCallback callback) {
if (mSatelliteSessionController != null) {
mSatelliteSessionController.registerForSatelliteModemStateChanged(callback);
} else {
loge("registerForSatelliteModemStateChanged: mSatelliteSessionController is not initialized yet");
return SatelliteManager.SATELLITEINVALIDTELEPHONYSTATE;
}
return SatelliteManager.SATELLITE
ERRORNONE;
}

The SatelliteController correctly handles the lack of satellite hardware by returning SATELLITE\
INVALID_TELEPHONY_STATE. The fatal flaw is in the higher-level network manager (likely the MediaTek RIL or the telephony framework's state machine). When it receives this error during a network transition (Wi-Fi to Mobile Data), it fails to handle the exception properly. Instead of aborting the satellite registration, it immediately retries the call in an unconditional infinite loop.

A simple conditional check (if (hasSatelliteHardware)) before attempting to register the listener in the network state change event within the calling process will completely resolve this battery drain issue for all MediaTek devices without satellite capabilities.

https://redd.it/1v4x3rd
@reddit_android
Google officially drops support for Android 6 Marshmallow after 11 years

As of yesterday, Google has officially pulled the plug on Android 6. This means the OS will no longer receive Play Protect updates and will not be included in the new APK program. Having been supported for exactly 11 years, it goes down as the longest-supported version in Android history. Google Play Services is now only supported on Android 7 and above.

Source: https://support.google.com/googleplay/answer/9037938?hl=en

Google also made changes to several other applications yesterday. YouTube now requires Android 10 and above, meaning Android 9 will no longer receive YouTube updates. The Google app's minimum requirement jumped from Android 9 directly to Android 11, and core apps like Gmail now require at least Android 7 and above.

https://redd.it/1v4o307
@reddit_android
I think Google's upcoming Android changes deserve way more attention than they're getting

I've been using Android for years because of one simple reason: freedom.

If I wanted to install an app from GitHub, F-Droid, or directly from a developer, I could. If I wanted to avoid the Play Store, I could. If I wanted to customize my phone, I could. That's what always made Android feel different from other mobile operating systems.

Recently I found https://keepandroidopen.org/, and after reading through it, I honestly think this is something every Android user should at least know about.

From what I understand, Google's planned changes could make distributing apps outside the Play Store much harder for independent developers by requiring developer verification through Google. Whether you're into open source software, custom ROMs, privacy focused apps, or just like having the choice to install software from wherever you want, this could have a real impact on the openness of Android.

I'm only 16, so I'm definitely not an expert, and maybe there are parts of this I'm overlooking. But if Android slowly becomes more restricted over time, I think that's something worth discussing now instead of after it happens.

I'm not posting this to tell anyone what to think. I just think more people in the Android community should be aware of what's being proposed and decide for themselves.

Website:
https://keepandroidopen.org/

I'd really like to hear what you all think. Is this a reasonable security measure, or do you think it goes against what has always made Android different?

https://redd.it/1v4fvwy
@reddit_android
Daily Superthread (Jul 24 2026) - Your daily thread for questions, device recommendations and general discussions!

Note 1. You can search for previous daily threads.

Note 2. Join our IRC and Telegram chat-rooms! Please see our wiki for instructions.

Please post your questions here. Feel free to use this thread for general questions/discussion as well.

https://redd.it/1v59dt8
@reddit_android