The author mentions that the issue is present both on 16 Pro Max and 17 Pro Max. When I upgraded to 17 Pro Max from my 14 Pro I noticed it too, even thought I might've gotten a defective camera unit. I think it all boils down to a different lens with a different focal length.
Off topic, it was very interesting to peek into libphonenumbers metadata. I find it curious that we have so many ways to write down an already standardized identifier.
When traveling, I always try to use local payphones and call friends or just myself. Maybe the name is not quite apt because the phone service is often provided for free.
Is SMS federated though? Genuine question. As far as I know it requires manual each-to-each setup on MNO level thus very fragile when we talk about cross-border or even cross-operator messaging. It is nowhere near email in terms of federation.
I got served with an invalid certificate too, just for one hit, then the site loaded normally. Haven’t made a screenshot, but the certificate was issued by crewai dot com.
Sadly this phone turned out to be barely usable on my VoLTE network: when someone whose number I have in phone contact list calls, the phone displays number only and no name unless I turn off VoLTE, thus degrading voice quality and reception. Also the UX is generally bad. It is nowhere near the good old Nokia days.
I had a Nokia flip phone running kaios a few years ago. Kaios was the worst phone software I've ever run. The Nokia hardware was even worse. More often than not, keypresses wouldn't register at all or would act like you'd pressed the button four times.
reply