4 ms·

As I understand it, the OEM modifications will be relegated to the vendor/odm partitions. They specifically hint at being able to push new system partitions dir

As I understand it, the OEM modifications will be relegated to the vendor/odm partitions. They specifically hint at being able to push new system partitions directly in the future.

pjmlp 9y ago
1 - One needs to buy a new Android 8 device. 2 - Android 7 has currently about 13% acquisition after one year 3 - There is currently no obligation for OEMs to provide updates 4 - Given the failure of security updates, only being delivered to flagship devices, I believe Google will ship them directly when they actually do it.
- EddieRingle 9y ago
  1 - Which OEMs will be pushing consumers to buy, according to you. 2 - Right, this is something Treble will attempt to solve. 3 - Which is why Google is making it as easy as possible for them to do so, right down to actually pushing out the updates for them.
  - pjmlp 9y ago
    1 - I guess only Google with its rather expensive Pixel device, and probably Samsung and Huawei flagships only, in the same price category. 3 - I would really like to be proven wrong here. Still waiting for my Android 7 update on a newly bought device.
  - s73ver_ 9y ago
    None of that actually seems to solve the issue of developing updates and pushing them to users, though.
    - EddieRingle 9y ago
      Actually it does! For example, something I was excited to see is in the updated documentation on source.android.com with regards to how they recommend developing kernel branches alongside devices: https://source.android.com/devices/architecture/kernel/modular-kernels#beyond-android-o https://source.android.com/devices/architecture/kernel/modul... Basically, one of the issues that's plagued OEMs in the past is the fact that each SoC vendor (e.g. Qualcomm, Samsung, ARM) would not only have a kernel for each SoC, but each OEM device using that SoC would be another branch on that SoC-specific repository. This would then be compounded by the OEMs having their own kernel repositories that pull from the device-specific branches of a SoC repository, and bug fixes from OEMs would have to trickle back upstream to the vendor repository before making them back to other device-specific kernels. The new proposed model would see a single kernel soruce for a given SoC, and device-specific changes would come in the form of kernel modules, config overrides, and device tree overlays. They are also strongly recommending SoC changes to the kernel be upstreamed to mainline Linux, which would greatly ease porting to newer kernels in the future.
      - pjmlp 9y ago
        Recommendations are just that, advices that might be followed, or not. It isn't the first time that Google does recommendations to OEMs. They also did recommendations for security updates. An advice that OEMs only follow for the customers that paid the big bucks for the flagship devices. So unless they actually provide requirements instead of recommendations, nothing will change for consumers.

As I understand it, the OEM modifications will be relegated to the vendor/odm partitions. They specifically hint at being able to push new system partitions directly in the future.

pjmlp 9y ago

1 - One needs to buy a new Android 8 device. 2 - Android 7 has currently about 13% acquisition after one year 3 - There is currently no obligation for OEMs to provide updates 4 - Given the failure of security updates, only being delivered to flagship devices, I believe Google will ship them directly when they actually do it.

EddieRingle 9y ago
1 - Which OEMs will be pushing consumers to buy, according to you. 2 - Right, this is something Treble will attempt to solve. 3 - Which is why Google is making it as easy as possible for them to do so, right down to actually pushing out the updates for them.
- pjmlp 9y ago
  1 - I guess only Google with its rather expensive Pixel device, and probably Samsung and Huawei flagships only, in the same price category. 3 - I would really like to be proven wrong here. Still waiting for my Android 7 update on a newly bought device.
- s73ver_ 9y ago
  None of that actually seems to solve the issue of developing updates and pushing them to users, though.
  - EddieRingle 9y ago
    Actually it does! For example, something I was excited to see is in the updated documentation on source.android.com with regards to how they recommend developing kernel branches alongside devices: https://source.android.com/devices/architecture/kernel/modular-kernels#beyond-android-o https://source.android.com/devices/architecture/kernel/modul... Basically, one of the issues that's plagued OEMs in the past is the fact that each SoC vendor (e.g. Qualcomm, Samsung, ARM) would not only have a kernel for each SoC, but each OEM device using that SoC would be another branch on that SoC-specific repository. This would then be compounded by the OEMs having their own kernel repositories that pull from the device-specific branches of a SoC repository, and bug fixes from OEMs would have to trickle back upstream to the vendor repository before making them back to other device-specific kernels. The new proposed model would see a single kernel soruce for a given SoC, and device-specific changes would come in the form of kernel modules, config overrides, and device tree overlays. They are also strongly recommending SoC changes to the kernel be upstreamed to mainline Linux, which would greatly ease porting to newer kernels in the future.
    - pjmlp 9y ago
      Recommendations are just that, advices that might be followed, or not. It isn't the first time that Google does recommendations to OEMs. They also did recommendations for security updates. An advice that OEMs only follow for the customers that paid the big bucks for the flagship devices. So unless they actually provide requirements instead of recommendations, nothing will change for consumers.