118
submitted 1 year ago* (last edited 1 year ago) by ijeff@lemdro.id to c/android@lemdro.id

Mishaal Rahman and FragmentedChicken are in South Korea for Samsung Unpacked!

It's weird with time zones but they'll be on for the next hour or so. They're juggling on-the-ground stuff at the press conference so post any questions here and they'll respond once they can!

Edit: We've left the hands-on area, but feel free to continue posting your questions. We'll continue to answer them if we can, and might have another opportunity with some of the devices.

For articles about Samsung's latest announcements, see the Megathread sticky at !android@lemdro.id.

you are viewing a single comment's thread
view the rest of the comments
[-] d3Xt3r@lemmy.world 4 points 1 year ago

Highly unlikely. The root/ROM community has always been a small niche - and these days, it's even smaller that it has ever been. Such a minor audience means nothing for Samsung.

[-] ijeff@lemdro.id 3 points 1 year ago

It's pretty unfortunate. I'd love to see some regulations put into place that would ensure the option for unlockable bootloaders. North American devices are stick without the option in the first place :(.

[-] d3Xt3r@lemmy.world 4 points 1 year ago

Unlockable bootloaders aren't a big issue - you can buy devices with unlockable bootloaders in NA, depending on your carrier - the bigger problem these days is the likes of SafteyNet and KNOX, which makes it a pain to live with an unlocked bootloader. What we really need is a change in thinking that an unlocked bootloader doesn't necessarily mean a device is insecure, and instead of not giving the user a choice and locking them out, they should pass on the responsibility to the user. Eg, a banking app could make a user accept an agreement that the bank will not be held responsible for any hacking related losses etc, instead of straight up prevent the app from running. For this, Google needs to take the lead - they were the ones who introduced SafteyNet and caused this whole mess in the first place. Once Google takes the lead, Samsung and other manufacturers could follow, and the dev ecosystem will follow too. But I'm afraid it's all a bit too late now, the best one could do, as an individual, is to boycott apps which use the likes of SafteyNet, leave bad reviews, complain to the CEO etc, but all this is unlikely to have any impact, given that we root/ROM users are a small minority.

[-] ijeff@lemdro.id 2 points 1 year ago

I should clarify I'm referring to Samsung and their flagships. I bought my S23 Ultra directly from Samsung Canada and unfortunately can't unlock the bootloader.

[-] Im28xwa@lemdro.id 2 points 1 year ago

Why in some countries they sell their devices with unlockable bootloaders and in other countries they don't? I can't make sense of doing such a thing

[-] Im28xwa@lemdro.id 1 points 1 year ago

It is worth mentioning that google does allow for re locking the bootloader on their Pixel line up on custom ROMs and unlike Samsung they did not put a fuse in the Pixels that explodes to permanently disable the device's TEE and its security hardware

this post was submitted on 26 Jul 2023
118 points (97.6% liked)

Android

17668 readers
80 users here now

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

💬Telegram channels / chats

📰Our communities below


Rules

  1. Stay on topic: All posts should be related to the Android OS or ecosystem.

  2. No support questions, recommendation requests, rants, or bug reports: Posts must benefit the community rather than the individual. Please post to !askandroid@lemdro.id.

  3. Describe images/videos, no memes: Please include a text description when sharing images or videos. Post memes to !androidmemes@lemdro.id.

  4. 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.

  5. 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.

  6. No editorializing titles: You can add the author or website's name if helpful, but keep article titles unchanged.

  7. No piracy or unverified APKs: Do not share links or direct people to pirated content or unverified APKs, which may contain malicious code.

  8. No unauthorized polls, bots, or giveaways: Do not create polls, use bots, or organize giveaways without first contacting mods for approval.

  9. No offensive or low-effort content: Don't post offensive or unhelpful content. Keep it civil and friendly!

  10. No affiliate links: Posting affiliate links is not allowed.

Quick Links

Our Communities

Lemmy App List

Chat and More


founded 1 year ago
MODERATORS