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