Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Google confirms Android attacks; no fix for most Samsung users

forbes.com

Post reply on HN
Print view View original

31–40 of 177 posts

Re: Google confirms Android attacks; no fix for most Samsung users

#31

Post by crazygringo »

jcranmer wrote: post #30
shwaj wrote: post #23

Earlier quoted context omitted.

It’s “Fuchsia” with a “chs” not a “sch”. Where do you get your information that it’s dead?

As Randall Munroe pointed out in https://blog.xkcd.com/2010/05/03/color-survey-results/ , almost nobody knows how to spell "fuchsia" correctly. I only remember it by the mnemonic of it's fuck, but with an s.

I vote to just change the spelling to what almost everyone already thinks it is anyways.

It'll still be just as weird. But "chs" is just nonsensical. The idea that it would sound like "sh" is baffling. I mean, I know this is English spelling which is not known for its regularity, but this is just too much.

Re: Google confirms Android attacks; no fix for most Samsung users

#32

Post by shiandow »

kwanbix wrote: post #29
charcircuit wrote: post #17

>But in reality, Samsung (and the other Android OEMs) cannot compete with Google and its unique control over hardware and software. Yes, they can. We are talking about applying provided security patches to source code, and then releasing a new version of their OS. For patches that have existed for months. The time from patch to release should be on the order l of days from receiving the patches to having a validated…

The problem is that each OEM releases 50 different models per year, vs Google (or Apple) that release 3 or 4 models.

If that truly is an issue then Android is a fundamentally broken OS.

How many different models of PCs get released? How hard is it to patch any of their OSs?

Re: Google confirms Android attacks; no fix for most Samsung users

#33

Post by edoceo »

bigbadfeline wrote: post #20
xnx wrote: post #5

No fix yet for Samsung. Being reliant on the hardware manufacturer (or network operator?) for OS updates is the crazy world we live in.

> Being reliant on the hardware manufacturer (or network operator?) for OS updates is the crazy world we live in. Being reliant on a single OS permanently nailed to the hardware is no less crazier. I'd like to be able to install another OS on a vulnerable device, it would help tremendously and not only with the security of that specific device. Now I've got some expensive paperweights that I can't even use as such be…

Please try to e-recycle rather than normal land-fill trash.

Re: Google confirms Android attacks; no fix for most Samsung users

#34

Post by Terr_ »

jeffbee wrote: post #27
kelnos wrote: post #11

> This [update] was rushed out to all Pixel users. Pixel 8 here, still don't have the update. That's... not great.

Just go to the software update, touch the button, then touch it a second time, and that will give you all available updates immediately, regardless of your random position in the rollout process.

Not working for me on Android 16, additional taps of the "Check for update" button in the bottom-right don't change the fact that it says "Your system is up to date" and that the last change was last month.

Re: Google confirms Android attacks; no fix for most Samsung users

#35

Post by jacquesm »

charcircuit wrote: post #17

>But in reality, Samsung (and the other Android OEMs) cannot compete with Google and its unique control over hardware and software. Yes, they can. We are talking about applying provided security patches to source code, and then releasing a new version of their OS. For patches that have existed for months. The time from patch to release should be on the order l of days from receiving the patches to having a validated…

And then you install that 'security patch' and end up with a borked phone, apps that no longer work, new apps that you didn't ask for and so on.

Give me just the security updates please.

Re: Google confirms Android attacks; no fix for most Samsung users

#36

Post by jeffbee »

Terr_ wrote: post #34
jeffbee wrote: post #27

Earlier quoted context omitted.

Just go to the software update, touch the button, then touch it a second time, and that will give you all available updates immediately, regardless of your random position in the rollout process.

Not working for me on Android 16, additional taps of the "Check for update" button in the bottom-right don't change the fact that it says "Your system is up to date" and that the last change was last month.

Could be model-specific. I got the update by doing that manually on my Pixel 8 Pro, that also happens to be on the beta track so there are a few confounders. But that is the way to get the latest software that is waiting to be released to your phone, without waiting.

Re: Google confirms Android attacks; no fix for most Samsung users

#37

Post by klooney »

kwanbix wrote: post #29
charcircuit wrote: post #17

>But in reality, Samsung (and the other Android OEMs) cannot compete with Google and its unique control over hardware and software. Yes, they can. We are talking about applying provided security patches to source code, and then releasing a new version of their OS. For patches that have existed for months. The time from patch to release should be on the order l of days from receiving the patches to having a validated…

The problem is that each OEM releases 50 different models per year, vs Google (or Apple) that release 3 or 4 models.

The fix was released in September according to GrapheneOS, so you'd think they could have it out for the flagships

Re: Google confirms Android attacks; no fix for most Samsung users

#38

Post by reactordev »

shiandow wrote: post #32
kwanbix wrote: post #29

Earlier quoted context omitted.

The problem is that each OEM releases 50 different models per year, vs Google (or Apple) that release 3 or 4 models.

If that truly is an issue then Android is a fundamentally broken OS. How many different models of PCs get released? How hard is it to patch any of their OSs?

>How many different models of PCs get released?

If you want to go that route, each manufacturer is responsible for their own drivers for windows, linux, and possibly Mac (though if it’s novel enough, they will do it). Then think about the components that make up a PC. Motherboard, CPU, Memory Control, IO, OS, Audio, Video. Each of those needs to release patches. So its orders of magnitude more than any Android OS. It’s just pure laziness on the hardware manufacturers that don’t want to invest in software/support. They want Google to do that.

Re: Google confirms Android attacks; no fix for most Samsung users

#39

Post by pwdisswordfishy »

crazygringo wrote: post #31
jcranmer wrote: post #30

Earlier quoted context omitted.

As Randall Munroe pointed out in https://blog.xkcd.com/2010/05/03/color-survey-results/ , almost nobody knows how to spell "fuchsia" correctly. I only remember it by the mnemonic of it's fuck, but with an s.

I vote to just change the spelling to what almost everyone already thinks it is anyways. It'll still be just as weird. But "chs" is just nonsensical . The idea that it would sound like "sh" is baffling. I mean, I know this is English spelling which is not known for its regularity, but this is just too much.

It comes from the surname of a German botanist. Which just happens to mean "fox". Never had problems with it.

It would probably help if you pronounced it right, with a /ks/.

Re: Google confirms Android attacks; no fix for most Samsung users

#40

Post by drtgh »

kwanbix wrote: post #29
charcircuit wrote: post #17

>But in reality, Samsung (and the other Android OEMs) cannot compete with Google and its unique control over hardware and software. Yes, they can. We are talking about applying provided security patches to source code, and then releasing a new version of their OS. For patches that have existed for months. The time from patch to release should be on the order l of days from receiving the patches to having a validated…

The problem is that each OEM releases 50 different models per year, vs Google (or Apple) that release 3 or 4 models.

They must release drivers and firmware for all the devices that they no longer support.
Post reply on HN