Hacker Newsnew | past | comments | ask | show | jobs | submit | Namidairo's commentslogin

> 400GB for Ark

Ark is a strange case. It compresses very very well. Most of it ends up with compression ratios of around 80%.

> Total size on disk is 628.32 GiB and total download size is 171.42 GiB.

From SteamDB's summary of Ark's content depots.


> that let Pixel users enable VoLTE anywhere

It did a great deal more than that. It also allowed the toggling of VoNR, which apparently affected the fallback behavior of some people's services. (Ie. It would fall back to LTE and not roam back to 5G data unless nudged manually)

However for me, it would enable backup calls over a secondary sim card's data, which would allow text and calls overseas without the usual extortionate charges. Oddly enough, I believe that toggle is enabled for my carrier... but only on iOS.


> that toggle is enabled for my carrier... but only on iOS

WiFi calling with SIM1 number via SIM2 data has always worked on iOS, so I was surprised when it didn't work on Pixel.


This does work on Pixel's, but Google allowed carriers to block it, which at least one major US carrier does.


It would be great if google could dick swing on carriers with the same might as Apple


This is the “Backup calling” toggle in Pixel IMS, and carriers are fond of blocking that function.

(TIL: Vo“WiFi” over wired Ethernet over USB doesn’t work on AOSP or Pixel and never did, for no apparent reason except noöne caring to make it work.)


The part that does not work on iOS is putting SIM2 into airplane mode so that it can do VoWiFi without connecting to the network. That would reduce power consumption and avoid utterly obnoxious behavior on the part of some carriers (cough, Visible).


> VoNR

off topic but who the hell names these, a pre-schooler?

"New radio", from the makers of "New folder (1)"


>"New radio", from the makers of "New folder (1)"

https://en.wikipedia.org/wiki/5G_NR


The major carriers perhaps, but support among the MVNOs isn't universal. Number sharing support for smart watch usage is almost non-existent among the MVNOs in Australia.

Eg. ALDI (yes, the German supermarket chain run a MVNO in Australia), have been saying esim support in the future since 2021.


In the US, the overlap between people who would buy the latest iPhones and the people who use MVNOs I would suspect is practically non existent.

The MVNOs here mostly market older, cheaper iPhones.


They've pulled out of my market (Australia) 6 years ago, so that's not really an option, even if I imported one.

If I imported one, the majority of the handsets released before this year wouldn't be able to register on a network, given that the networks have gone and blocked the IMEI TAC associated with most of Sony's handsets.[1]

This is due to Sony not having the correct carrier settings in order to roam onto them for emergency calls, and a ham-fisted direction to have working emergency calls post-3G shutdown.

[1] https://isthisphoneblocked.net.au/device-brands/sony


I loved the early Sony Ericsson but they lost their way on the phones. And the funky camera phones when their stand alone phones are decent to cutting edge.


It's still a pretty hard question to answer, given how specific model numbers are sometimes missing on sales listings, and silent revisions to hardware.


Most likely referring to CVE-2018-6242 aka "Fusée Gelée"

The paperclip was just the easiest way of triggering RCM, which is a standard feature on Tegra. The vulnerability lay in that they didn't bounds check certain types of USB requests properly.


Yup, here's some footage of what it looks like: https://youtu.be/20SYS0_s7QI?t=377


I'm surprised that there are modern Tegra devices shipping with identical SBK across their production line.

I would have thought they'd do some mixing based on serial number or chip id as a baseline.

Or at least that's what the hash of their SBK implies.

I do enjoy seeing the boot chain on Tegra get broken yet again though.


From what I can tell of the block diagram, dropping the 2x 1gbit ports would not yield you a 2nd 10G SFP, as those would be running off the integrated switch as opposed to one of two USXGMII interfaces.

You would have to drop the other ports instead, and then you would just have 2x 10G SFP and a gigabit switch. Which is exactly how the BPi R4 is configured.


I had a similarly negative experience, sadly. Samsung managed to break HDMI-CEC in the final firmware update for one of their tvs, and wouldn't allow downgrading.

Which tends not to be great for a tv one wants to use with a Chromecast or similar media box...


For a second I thought this was referring to the other reset bug on Polaris, Vega and Navi. (These apparently have broken Function Level Reset sequences, requiring quite specific reset code as a separate module or a system reboot to bring back to a working state.)


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: