118
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 26 Jul 2023
118 points (97.6% liked)
Android
17409 readers
316 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
📰Our communities below
Rules
-
Stay on topic: All posts should be related to the Android OS or ecosystem.
-
No support questions, recommendation requests, rants, or bug reports: Posts must benefit the community rather than the individual. Please post to !askandroid@lemdro.id.
-
Describe images/videos, no memes: Please include a text description when sharing images or videos. Post memes to !androidmemes@lemdro.id.
-
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.
-
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.
-
No editorializing titles: You can add the author or website's name if helpful, but keep article titles unchanged.
-
No piracy or unverified APKs: Do not share links or direct people to pirated content or unverified APKs, which may contain malicious code.
-
No unauthorized polls, bots, or giveaways: Do not create polls, use bots, or organize giveaways without first contacting mods for approval.
-
No offensive or low-effort content: Don't post offensive or unhelpful content. Keep it civil and friendly!
-
No affiliate links: Posting affiliate links is not allowed.
Quick Links
Our Communities
- !askandroid@lemdro.id
- !androidmemes@lemdro.id
- !techkit@lemdro.id
- !google@lemdro.id
- !nothing@lemdro.id
- !googlepixel@lemdro.id
- !xiaomi@lemdro.id
- !sony@lemdro.id
- !samsung@lemdro.id
- !galaxywatch@lemdro.id
- !oneplus@lemdro.id
- !motorola@lemdro.id
- !meta@lemdro.id
- !apple@lemdro.id
- !microsoft@lemdro.id
- !chatgpt@lemdro.id
- !bing@lemdro.id
- !reddit@lemdro.id
Lemmy App List
Chat and More
founded 1 year ago
MODERATORS
Will Samsung ever rethink Knox and allow custom roms without losing warranty coverage and negatively affect resale value? What about allowing banking apps to work again if you go back to the default rom?
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.
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 :(.
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.
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.
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
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
Very very unlikely, don't get your hopes up.
It's an interesting question this and whether Samsung is willing to use GSI's / DSU.
Last time I checked that was a negative?
Most OEMs aren't willing to preload Google's AVB keys for their GSIs. DSU is only really supposed to be used by app developers (and even then most app devs don't know it even exists or use it) which is why most OEMs don't bother with it.
I highly doubt it unless there is constant pressure put on them to do so because Knox at this point has been set in stone, only a niche minority still discusses it (us) and talk about it