Snapdragon X70
qualcomm.com
qualcomm.com
some graph optimization, i guess. but channel, antenna tuning, network selection? what, isnt this all simple closed form "pick the best number"?
if its just flexing its ability to be used as edge compute as well thats cool too
The first is exactly the sort of thing where a cheaper "Good Enough Estimate" may be a great solution - which is what a fair bit of "AI" hardware does today. Though I don't know if firing up a separate AI block instead of an integrated to the radio "hardware" solution would be better, but it may be there's some crossover of techniques that can help.
https://www.technologyreview.com/2021/07/30/1030329/machine-...
https://www.wsj.com/articles/walmart-shelves-plan-to-have-ro...
https://medium.com/starsky-robotics-blog/the-end-of-starsky-...
I have never read a single comment that appreciate the complexity of 3GPP modem design. So this may be the first one in ten plus years.
Designing a working 4G / 5G modem is not hard. Designing one that is as good as Qualcomm and works in thousands of edges cases in hundreds of different carrier configuration all around the world is god damn hard.
Massive-MIMO on FDD in itself is complicated enough. One could argue we should all switch to TDD, but we dont have that luxury and it is not always a win. Carrier aggregation with mmWave beamforming since Qualcomm is somehow still keen on getting it done.
And this is just on the client side. Most if not all on HN have very little to no appreciation on the complexity of mobile network and 5G. No wonder why sometimes you hear engineers working in telecom equipment industry are rather pissed about Tech industry in general.
It's just a vacuous statement at this point.
How it's done is a business secret, I would be surprised if they told us much more.
If it's loosely integrated (e.g. doesn't need super high bus access) it's not even as if it'll affect stuff like the clock tree or bus complexity much either.
I'd be surprised if the new CPU would take that much power, especially since for most use cases the CPU is mostly idle.
Was a pain to root, had to jump through a few hoops, but did manage to get Cyanogen on there. The result felt WAY better, snappy, better scrolling, much less aggressive at killing apps, faster app switching, minimal lag for the home button, and generally just a pleasure to use. I mentioned this in various forums and the theory was that Samsung was optimizing for benchmarks instead of multitasking. Even things like switching apps to use maps or contacts during a call would cause whatever app you were using to be killed. I returned the Samsung Note to stock before selling it, and checked, and sure enough it felt sluggish and even with just 2-3 apps going when I switched I'd get a splash screen as the app relaunched after being killed.
I "upgraded" to a pixel, that had less ram and CPU, and it felt WAY better than the stock Samsung Note. I do wonder if your results are related to the Samsung software being optimized for benchmarks (i.e. running the clock high, killing off anything that's not fullscreen currently, etc) instead of interactive use. Generally the OnePlus phones seem to be closer to pure android than Samsung from what I can tell.