iOS 27 brings a cool, but obviously online-only feature. On-device AI is such an elusive thing.
π7
Tadi Channel
https://fixupx.com/MegaMarian12350/status/2064438214023123327
I think a big part of it is ironically about lockdown. Samsung stuff used to leak much more often, bypassing security features was a frequent occurrence, while they don't have a kind of insane authorization for what your unit is allowed to run (except ARB), and their way to cope with it is to stop users from unbricking their own devices, coincidentally serving the financial incentives once device is out of warranty.
In other words, there's so little you can do with an iPhone that they don't have to be afraid of offering everyone a straightforward way to unbrick. Other OEMs would love the same level of lockdown, but lack the willpower, instead deciding that unbricking is a backdoor for the privileged, despite the implications of right to repair laws.
In other words, there's so little you can do with an iPhone that they don't have to be afraid of offering everyone a straightforward way to unbrick. Other OEMs would love the same level of lockdown, but lack the willpower, instead deciding that unbricking is a backdoor for the privileged, despite the implications of right to repair laws.
π₯5π1
BTW, if that isn't obvious, the phone market could be fixed with a single law: just allow users to run any bootloader akin to status quo of PCs. Suddenly, the stuff like the above would improve dramatically too. If to narrow down such a law to include the ability of verified dual booting (where you're still attested while on stock, but have a working alternative system alongside), mobile Linux would start to thrive overnight, as the penalty for using it would only last as long as your session. The eww apps would no longer require a separate device, but merely a reboot.
π10β€8π2
Tadi Channel
To run an untouched (just kidding, the toggle in question and GP signing cause your app to be far from "untouched") original app enrolled into this unnecessary restriction, use: pm disable com.your.app/com.pairip.licensecheck.LicenseContentProvider
On recently (June?) updated apps, this no longer works. Not logged in MicroG still does.
The background is:
<Let's hope Google doesn't patch it at least for a year>
The background is:
<Let's hope Google doesn't patch it at least for a year>
π7
Trump Phone is literally using the HTC Camera app. Contrary to everything else, this one aspect is a little bit more unprecedented, unless HTC's own camera app isn't their own either.
π12π3π2
There's a different Photon Camera and it takes straightforward bracketed raws.
https://github.com/bjzhou/PhotonCamera
Disadvantage: motion easily causes purple/green artifacts. Highlights can sometimes clip before white level (and turn purple). Despite that, definitely refreshing.
https://github.com/bjzhou/PhotonCamera
Disadvantage: motion easily causes purple/green artifacts. Highlights can sometimes clip before white level (and turn purple). Despite that, definitely refreshing.
GitHub
GitHub - bjzhou/PhotonCamera: Open-source Android camera application focused on static photography
Open-source Android camera application focused on static photography - bjzhou/PhotonCamera
π6β€3π₯2π1
Media is too big
VIEW IN TELEGRAM
Sony just casually posted a wildly dishonest/incompetent trippy video to sell a genuinely relevant technology
π4π€―4π4π₯1
I've been informed and got a quite evident separate confirmation that the API limitation of actual RAW stream access on iOS (not to be confused with temporal-filtered ProRes RAW video Apple touted in the past) is that you're only able to obtain frames while camera is "in focus" and not "focusing" since the API is designed solely for photo capture. On all these truly-RAW-based apps, you should expect that the Japanese iPhone units will try to play shutter sound for every single frame.
π6π2π€―2π1
Tadi Channel
Photo
The fun part? Now that iOS devices are getting actual RAW (and RAW-based) video through third party app devs who finally started moving, it'll no longer gather the headlines the official, fake RAW video got on Apple's announcement. It'll be a mere curiosity, while lots of "professionals" will stay with the former, size-inefficient implementation.
π2π1
Third message in a row: yes, as soon as I'll see a video comparing ISP-processed RAW with actual RAW video on iPhone 17 Pro, I'll link it here. From what I've seen from actual RAW photos (such as from Bayer Cam), the sensor mode exposed for third party apps is a quite clean 12-bit, likely not through LN2/LN4 or DCG, but through 12-bit ADC mode (so not best DR-wise, but nice). This may end up with better results even in a static scenery. At smaller file size.
β€1π1π1
Fourth (sorry): all this is a really good news for mobile Linux. Software ISP prove itself through different codebases and through different operating systems and hardware. We may add a watt or few to camera operation, but mere access to RAW stream combined with swISP running on GPU can let us skip tons of reverse engineering.
π5β€1π1
A recommendation: don't buy a Pixel, while hoping to use it on stock and keeping any privacy.
Yeah, you may think "but it's Google, they can't be as bad as an arbitrary bloatware you get on other major OEMs", but only here I see a casual "we'll now upload your data to cloud from this previously offline feature" served so casually.
Yeah, you may think "but it's Google, they can't be as bad as an arbitrary bloatware you get on other major OEMs", but only here I see a casual "we'll now upload your data to cloud from this previously offline feature" served so casually.
π16π7β€2