4 ms·

Youtube page, which has auto-generated transcripts: https://www.youtube.com/watch?v=lLEkUGuw374 https://www.youtube.com/watch?v=lLEkUGuw374 tl;dw: 1. it's exp

by gruez 28d ago

Youtube page, which has auto-generated transcripts: https://www.youtube.com/watch?v=lLEkUGuw374 https://www.youtube.com/watch?v=lLEkUGuw374 tl;dw: 1. it's expensive 2. requires online connection and account to unlock bootloader 3. lenovo (the parent company) had shady behavior in the past

LikelySupernova 28d ago
Then buy Pixel A series, it has none of those cons. And I'd say at that price point, Tensor isn't even a bad processor.
bushwart 28d ago
Needing an account to unlock the bootloader is a real bummer. I can live with issues 1 and 3. Thanks for the notes.
seanw444 28d ago
> 2. requires online connection and account to unlock bootloader That's horrible. I'm surprised the GOS team is okay with this.
- 627467 28d ago
  Is it a fact that when these devices come the process to unlock will remain the same?
  - microtonal 28d ago
    There is little information available about the future devices. I think they are just extrapolating from prior unlockable Motorola devices. IMO it's not worth speculating until there is some official information or someone has actually tested on one of the devices.
    - seanw444 27d ago
      At least there's still hope. It would be weird that this would be allowed to stand, with first-class GOS in the picture now.
- deleted 28d ago
  [deleted]
dmm 28d ago
Unlocking the pixels also requires an internet connection, to determine whether the device has any restrictions on it. From the grapheneos installation instructions: """ On device model variants (SKUs) which support being sold as locked devices by carriers, enabling OEM unlocking requires internet access so that the stock OS can check if the device was sold as locked by a carrier. """ https://grapheneos.org/install/web#enabling-oem-unlocking https://grapheneos.org/install/web#enabling-oem-unlocking
- subscribed 28d ago
  connection != account You can do the Pixel unlocking whilst driving by the random McD. I'm quite surprised it flies with the team.
  - gruez 28d ago
    >connection != account That's not much of a distinction considering that it's trivial to create an email/account (without a phone number, even!) with fake information.
    - subscribed 28d ago
      That's a massive difference to me (you rightly called me out on that one). One is 5 seconds on wifi, second is grumbly attempts to create throwaway email to create the throwaway account. I agree in principle but disagree because I hate unnecessary friction.
aftbit 28d ago
1. So what? 2. This sucks but is basically required to protect against phone theft (though phones could be shipped in an unlock-once state, until you set them up) 3. So what? What company has never been shady?
summm 28d ago
Regarding 2. they seem to refer to this: https://github.com/zenfyrdev/bootloader-unlock-wall-of-shame/blob/main/brands/motorola/README.md https://github.com/zenfyrdev/bootloader-unlock-wall-of-shame...
- subscribed 28d ago
  This reads shockingly bad, but most of that won't apply to the new devices. Like, it will be Qualcomm, it will support unlockng, relocking, custom keys and will not have a secret debug key - otherwise there simply would be absolutely no deal with GoS. IMO these new flagships will not be fully impacted by these issues (if at all), considering how much of the partnership initiative started* at Motorola. It was likely them providing the GOS team with source code of some of the most critical patches, when Google withheld it for months waiting for Samsung to release patches. Why? I guess to get the bragging rights to have the most secure android handsets in the world, to improve their own codebase (GOS pushed a lot of patches upstream and perhaps the hardware). I'm cautiously optimistic - given how allergic the team are to the notion of the enforced compliance imposed by Google, I think it's likely these new flagships will be automatically unlocked in the same way pixels are.
  - microtonal 28d ago
    It was likely them providing the GOS team with source code of some of the most critical patches, when Google withheld it for months waiting for Samsung to release patches. I'm pretty sure reading on Mastodon that it was another OEM that provided them with embargoed patches, but I can't find the Toot now.
    - subscribed 27d ago
      That'd be even better TBF, thanks for the update
gfrecvh 28d ago
Alright number 2 just convinced me I'll never use grapheneos.
- microtonal 28d ago
  There is no proof that that an account will actually be required. The fact that some existing Motorola phone require this does not say much.

by gruez 28d ago

LikelySupernova 28d ago

Then buy Pixel A series, it has none of those cons. And I'd say at that price point, Tensor isn't even a bad processor.

bushwart 28d ago

Needing an account to unlock the bootloader is a real bummer. I can live with issues 1 and 3. Thanks for the notes.

seanw444 28d ago

> 2. requires online connection and account to unlock bootloader That's horrible. I'm surprised the GOS team is okay with this.

627467 28d ago
Is it a fact that when these devices come the process to unlock will remain the same?
- microtonal 28d ago
  There is little information available about the future devices. I think they are just extrapolating from prior unlockable Motorola devices. IMO it's not worth speculating until there is some official information or someone has actually tested on one of the devices.
  - seanw444 27d ago
    At least there's still hope. It would be weird that this would be allowed to stand, with first-class GOS in the picture now.
deleted 28d ago
[deleted]

dmm 28d ago

Unlocking the pixels also requires an internet connection, to determine whether the device has any restrictions on it. From the grapheneos installation instructions: """ On device model variants (SKUs) which support being sold as locked devices by carriers, enabling OEM unlocking requires internet access so that the stock OS can check if the device was sold as locked by a carrier. """ https://grapheneos.org/install/web#enabling-oem-unlocking https://grapheneos.org/install/web#enabling-oem-unlocking

subscribed 28d ago
connection != account You can do the Pixel unlocking whilst driving by the random McD. I'm quite surprised it flies with the team.
- gruez 28d ago
  >connection != account That's not much of a distinction considering that it's trivial to create an email/account (without a phone number, even!) with fake information.
  - subscribed 28d ago
    That's a massive difference to me (you rightly called me out on that one). One is 5 seconds on wifi, second is grumbly attempts to create throwaway email to create the throwaway account. I agree in principle but disagree because I hate unnecessary friction.

aftbit 28d ago

1. So what? 2. This sucks but is basically required to protect against phone theft (though phones could be shipped in an unlock-once state, until you set them up) 3. So what? What company has never been shady?

summm 28d ago

Regarding 2. they seem to refer to this: https://github.com/zenfyrdev/bootloader-unlock-wall-of-shame/blob/main/brands/motorola/README.md https://github.com/zenfyrdev/bootloader-unlock-wall-of-shame...

subscribed 28d ago
This reads shockingly bad, but most of that won't apply to the new devices. Like, it will be Qualcomm, it will support unlockng, relocking, custom keys and will not have a secret debug key - otherwise there simply would be absolutely no deal with GoS. IMO these new flagships will not be fully impacted by these issues (if at all), considering how much of the partnership initiative started* at Motorola. It was likely them providing the GOS team with source code of some of the most critical patches, when Google withheld it for months waiting for Samsung to release patches. Why? I guess to get the bragging rights to have the most secure android handsets in the world, to improve their own codebase (GOS pushed a lot of patches upstream and perhaps the hardware). I'm cautiously optimistic - given how allergic the team are to the notion of the enforced compliance imposed by Google, I think it's likely these new flagships will be automatically unlocked in the same way pixels are.
- microtonal 28d ago
  It was likely them providing the GOS team with source code of some of the most critical patches, when Google withheld it for months waiting for Samsung to release patches. I'm pretty sure reading on Mastodon that it was another OEM that provided them with embargoed patches, but I can't find the Toot now.
  - subscribed 27d ago
    That'd be even better TBF, thanks for the update

gfrecvh 28d ago

Alright number 2 just convinced me I'll never use grapheneos.

microtonal 28d ago
There is no proof that that an account will actually be required. The fact that some existing Motorola phone require this does not say much.