Android
The new home of /r/Android on Lemmy and the Fediverse!
Android news, reviews, tips, and discussions about rooting, tutorials, and apps.
πUniversal Link: !android@lemdro.id
π‘Content Philosophy:
Content which benefits the community (news, rumours, and discussions) is generally allowed and is valued over content which benefits only the individual (technical questions, help buying/selling, rants, self-promotion, etc.) which will be removed if it's in violation of the rules.
Support, technical, or app related questions belong in: !askandroid@lemdro.id
For fresh communities, lemmy apps, and instance updates: !lemdroid@lemdro.id
π¬Matrix Chat
π°Our communities below
Rules
-
Stay on topic: All posts should be related to the Android OS or ecosystem.
-
No support questions, recommendation requests, rants, or bug reports: Posts must benefit the community rather than the individual. Please post to !askandroid@lemdro.id.
-
Describe images/videos, no memes: Please include a text description when sharing images or videos. Post memes to !androidmemes@lemdro.id.
-
No self-promotion spam: Active community members can post their apps if they answer any questions in the comments. Please do not post links to your own website, YouTube, blog content, or communities.
-
No reposts or rehosted content: Share only the original source of an article, unless it's not available in English or requires logging in (like Twitter). Avoid reposting the same topic from other sources.
-
No editorializing titles: You can add the author or website's name if helpful, but keep article titles unchanged.
-
No piracy or unverified APKs: Do not share links or direct people to pirated content or unverified APKs, which may contain malicious code.
-
No unauthorized polls, bots, or giveaways: Do not create polls, use bots, or organize giveaways without first contacting mods for approval.
-
No offensive or low-effort content: Don't post offensive or unhelpful content. Keep it civil and friendly!
-
No affiliate links: Posting affiliate links is not allowed.
Quick Links
Our Communities
- !askandroid@lemdro.id
- !androidmemes@lemdro.id
- !techkit@lemdro.id
- !google@lemdro.id
- !nothing@lemdro.id
- !googlepixel@lemdro.id
- !xiaomi@lemdro.id
- !sony@lemdro.id
- !samsung@lemdro.id
- !galaxywatch@lemdro.id
- !oneplus@lemdro.id
- !motorola@lemdro.id
- !meta@lemdro.id
- !apple@lemdro.id
- !microsoft@lemdro.id
- !chatgpt@lemdro.id
- !bing@lemdro.id
- !reddit@lemdro.id
Lemmy App List
Chat and More
view the rest of the comments
It happens on multiple Pixel 10s running Android 16 when an alarm goes off and the screen is not locked.
If you slightly miss the "Stop" button on the alarm notification, that notification will sometimes disappear completely. There is then no way in the UI to stop the alarm and it just keeps getting louder - a real problem in public places. Probably killing the Clock app would do it but it's easier to shut down the phone.
There is laundry list of other serious bugs that have been a problem on multiple Pixels. A couple weeks ago one phone randomly switched time zones, another (not carrier related) known bug. We use our phones as clocks and it caused a missed appointment.
I have an old Oneplus 6T running Android 11 and it is far more reliable.
Oof. Yeah, that's ridiculous. With it being a Pixel, you probably have ROM options, but that's a lot of messing around setting everything up again, for basic functionality that should work anyway.
I use cheap AF Motorolas with more storage than Pixels, call it the "Snapdragon for less" plan. Rip out everything unnecessary with Canta (Shizuku required) and now the battery lasts three days. I'm happy to be on Android 15, for now...
I really like Motorola phones but wanted to run Graphene. Unfortunately it's a PITA to switch at this point. It will take a day or more to install Graphene and completely configure everything again. The other thing is Graphene is based off the original Android code and I expect most of the same bugs will exist there as well.
Because of the lousy, beta quality software they release I've long thought Google employees never use their own products. For example the current version of Maps on the Pixel regularly switches to night mode during the day and won't switch back, something that should never have made it past their internal beta tests if they actually used their own stuff. Interestingly the few Google employees I've known all use Iphones so it seems they hold the same opinion of Android that I do.
You may have already tried playing with the now-very-granular notification permissions:
GrapheneOS is based on AOSP, not Google Android. So, for built-in apps like Clock, you would have "com.android.deskclock" instead of "com.google.android.deskclock". Both forked from Cyanogenmod. π€
I do know it comes from AOSP, but my understanding is that everything first comes (in some fashion) from Google? Is there another path for the source code that does not include Google?
There's nothing in notification settings or permissions that I've found that will fix the alarm problem.
I think that is a fairly recent change. 1.5 years ago?! I'm getting old.
https://www.androidauthority.com/google-android-development-aosp-3538503/
My wife had a minor basic functionality bug when she had a Pixel 3. The phone app would turn the screen on to show an incoming call, then go dark, and she would have to put in her PIN to unlock in order to answer the call. π€¦ I had the same model and no problem, and also could not find any difference in settings or anything that would cause it.