Samsung One UI 7 (Android 15) Updates

[Sparker0i]

When Android 16 is around the corner, why does Samsung even bother releasing OneUI 7 now?
Shouldn't they go straight to 8?

 

[honey95]

When Android 16 is around the corner, why does Samsung even bother releasing OneUI 7 now?
Shouldn't they go straight to 8?

It's in beta stage with having many bugs and crashed in system OS. Google doesn't want to give OS to other android manufactures until they tested carefully. hence, Android manufactures are having different hardware's and OS things. Every company that need to test its' OS with different machines along many processors from Qualcomm and meditek.

In this way, they need to ask for software patches, updates , for bugs and fixes with google and processor companies for compabilities. It's will take months until the final OS will be ready by Google with all fixed. Only they need to wait for monthly fixes that Final OS having bugs in different OS.

In my research, mostly bugs are created by company itself to make old os slower to let user's move to fresh OS and hardware.

 

[Sparker0i]

It's in beta stage with having many bugs and crashed in system OS.

There are very minimal bugs in Android 16 Beta 3 and 4, nothing that is a hard blocker.

Google doesn't want to give OS to other android manufactures until they tested carefully. hence, Android manufactures are having different hardware's and OS things.

In this way, they need to ask for software patches, updates , for bugs and fixes with google and processor companies for compabilities. It's will take months until the final OS will be ready by Google with all fixed. Only they need to wait for monthly fixes that Final OS having bugs in different OS.

Surprising you say that. A16 beta program is being run by other OEMs too.
Also Google gives out the releases to all OEMs one month before it is released to the public.

In my research, mostly bugs are created by company itself to make old os slower to let user's move to fresh OS and hardware.

This is a very ridiculous research. AOSP source code is open source, anyone can check that to see if Google is malicious or not.
By the Linux' GPL license, OEMs are supposed to open source their Kernel as well. One can very easily check the kernel code to see any malicious entities or not.
So the system and the kernel images cannot be compromized by anyone.

The only place where your claim stands a chance is either the GMS or the Vendor image. GMS is the same for everyone controlled by Google, so very minimal chance Google introduces something malicious there.
Now with the Vendor image which contains any proprietary things like integrations with other partners (Hasselblad, Harman, Zeiss etc), it has to be tested with only every new major version of Android, and not with the monthly security patches. But this very rarely covers things like Battery management or processor speed. That is a part of the AOSP code - unless OEMs decide to use a custom implementation (like Nokia/HMD in the past, or Samsung with some phones nowadays)...

Also it wouldn't be bugs. Sometimes this has to be done intentionally. Newer Android versions have more resource requirements. So OEMs have to throttle certain system features in order to not let the phones die young.

Please do proper research before making any claims.. This is coming from someone who has developed Android apps in the past and also have built Lineage OS for my Android phone back in the day...

 

[React]

Does this update has 5g only network mode selection? Or 4g/5g clubbed?

 

[Advik]

Does this update has 5g only network mode selection? Or 4g/5g clubbed?

5G only mode is available.

 

[Bapun]

Does this update has 5g only network mode selection? Or 4g/5g clubbed?

These are the available network modes on One UI 7.