Android

• 6.4-inch OLED (FHD+ 144Hz)
• 12/512GB
• Dimensity 8350
• 50MP main cam with a 1/1.56-inch LYT-700C sensor alongside a 50MP ultrawide and a 50MP front-facing camera.
• 5,000mAh battery with 90W charging
• supports DisplayPort 1.4 output
• IP68/69 water and dust proof

cross-posted from: https://programming.dev/post/32337654

For reference

https://www.androidauthority.com/anker-powercore-10000-recall-3567430/

The chip's octa-core CPU reportedly scores over 11,000 points in Geekbench 6's multi-core CPU performance test and over 4,000 points in the single-core CPU performance test.

That is a performance jump of 29% in the single-core test and 12% in the multi-core test compared to the Snapdragon 8 Elite chip. It matches Apple's A19 Pro chip in the single-core CPU test and far exceeds its multi-core CPU performance. The Adreno 840 GPU inside the Snapdragon 8 Elite 2 is said to feature 16MB of graphics memory.

If this report is accurate, the CPU performance of a chipset used in Android phones, including the Galaxy S26 series, will exceed that of Apple's flagship iPhone chip for the first time in the history. The GPU performance of the Snapdragon 8 Elite chip used in the Galaxy S25 already outperforms the A18 Pro's GPU (which is used in the iPhone 16 Pro Max).

Original question by @monovergent@lemmy.ml

The storage and processing power of modern smartphones are touted to rival those of a typical laptop. Yet, my trash-picked testing system from over a decade ago with a bottom-of-the-barrel SATA SSD can still boot to the Linux desktop faster than all but one of my Android devices.

Understandably, this isn't a huge priority since very few people are cold booting their phones every morning. But is it just plain unoptimized? How hard would it be to optimize? Do security features and checks bog it down? Is it that there's many tiny files to load when booting? What gives?

TL;DR

• PS3 emulator aPS3e is now available on the Google Play Store.
• From the mysterious Chinese developer aenu, it’s based on the RPCS3 source code.
• The project now claims to be open-source, but may not meet all requirements.

cross-posted from: https://lemmy.world/post/31229844

As noted by the news release from CalyxOS and Mastodon thread from GrapheneOS, Google did not release the Pixel device-specific source code alongside their Android 16 AOSP release like they usually do. I think many of us, including myself, are hoping this will be published in the near future, but considering they moved AOSP development behind closed doors earlier this year, it's more likely Google has stopped publishing this section or their code altogether, making development of custom ROMs for Pixel devices significantly more difficult. Sad news for the Android ecosystem, and for open source in general.

cross-posted from: https://lemmy.world/post/31185238

It also hides ads, reels, stories, etc at your convenience. Great app with an active dev.