- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2 weeks ago in
Discussions- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2 weeks ago (Last edited 2 weeks ago ) in
DiscussionsGoogle sent Samsung the Android 16 code already. However Samsung will not be working on this anytime soon. I can guarantee you that Samsung won't be touching that code until the public official launch of Android 16 by that time they might get around to eventually working on Android 16, but my guess is we are unlikely to see Android 16 for Samsung phones until January or February of 2026.
It's even more sad that they are creating such a slow roll-out. So many things are broken in the s23 beta. Seriously, what have they been working on? It sure hasn't been One UI 7. Like was there political unrest in Korea? Worker strikes? What caused them to delay the builds? It seems like they didn't even start working on it until Nov. It would explain why the s23 didn't even get one until this month. If they had political issues and worker strikes in Korea that would explain why they didn't touch Android 15 until October, and releasing the first beta in December.
Creating Android updates is not that hard. Since Google's introduction of dynamic system updates and generic system images, it is scary how easy it is to create generic images for any processor in any phone. There are 1 man developers creating roms for tablets such as the Nexus 7 which is 12 years old and runs beautifully on Android 14 even though that tablet has not received ANY new kernel code in 8+ years. Samsung has it easy.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
2 weeks ago in
DiscussionsHello @0vermind,
We appreciate you taking the time to share your thoughts, and we fully understand your frustration regarding the timeline and communication around the One UI 7 rollout. Your feedback touches on many valid points, including expectations for transparency, responsiveness, and feature readiness.
While itās true that Google shares Android source code with manufacturers ahead of public releases, implementing a new OS like Android 15 into One UI involves far more than just integrating the core AOSP code. Each device goes through extensive adaptation, testing, UI layer development, performance optimization, regional customization, and most importantlyāstability assurance across a wide range of hardware and carrier-specific models.
This means that even with access to source code early, the actual timeline to deliver a polished and stable experience can vary, especially when aiming to meet Samsung's multi-device update commitment and ensuring backward compatibility across generations.
We understand the desire for more direct updates during this process, and while we canāt comment on internal timelines or decisions, we do take your feedback seriously and will share it with the relevant teams.
Thank you for being part of the One UI Beta communityāeven when itās tough. Your voice helps us improve both the software and the experience around it.
Regards,
One UI Beta Team
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
a week ago in
DiscussionsCommunicate with us. Post timelines. Plans always change, everyone knows that, your plans and timelines don't have to be perfect, but give us an idea of what to expect, help us understand what's going on, and make a commitment to do better. That will win us back. I guarantee it. Try to make a commitment to getting the monthly security patches on time every time, and try to make a commitment to get Android updates on time every time. You already committed to 8-10 years of updates, show us you can do this.
Edit: Beta 2 removed digital assistant from corner gesture, are you mother effing kidding me? Why? I think I am seriously done with Samsung. I can't do this. You do all the wrong things, why was it necessary to remove that?

