No, I'm not living in the past with all my fountain pens, keypad phones, pocket calculators and slide rules, cassette and CD players, longwave-enabled and mechanical wristwatches and dreams of bringing back POCSAG and NMT. I'm living in a very probable future that will come when the bubble bursts.

L2 "solutions" are never the answer to the problems rooted in L1. They are merely crutches. And crutches tend to break over time.

And also, are there any options of buying a virtual PSTN number for SIP calling with crypto (and non-KYC, of course) and topping it up with crypto as well? I know about JMP.chat but I need SIP, and not in an experimental status, and I shouldn't be charged for *incoming* calls, no carrier does this here. I could have stuck with my Intertelecom number but I need to get more global. #asknostr

Ok, so CSipSimple, Lumicall etc are pretty much dead on Android 14. Linphone and SipDroid are alive, bu the second one is unusable. So, which FOSS alternatives of Linphone exist at this point?

Great to see people go against the square-holed mindset imposed by googles.

GitHub

GitHub - akavel/hellomello: Experiments with writing Android apps in Nim

Experiments with writing Android apps in Nim. Contribute to akavel/hellomello development by creating an account on GitHub.

I guess the best "traditional" on-screen keyboard application for Android would be Unexpected Keyboard. It's FOSS, it's convenient, it adds everything on par with the PC input (even a dedicated Compose key) and is extremely configurable.

Hmm. The devinfo partition does indeed store both Pixel 6 IMEIs in plain ASCII. They can be found after "imei1" string and zero byte and after "imei2" string and zero byte respectively. Patching any of them in the devinfo image, regardless of whether or not /mnt/vendor/efs/nv_protected* files are deleted afterwards, causes the device to report both IMEIs as 000000000000000 to both the OS and the network (which shows "Unknown Unknown" in place of the phone model in the carrier's account page). Other places to properly patch the IMEIs in addition to the devinfo partition are still being researched. The journey is still far from the end, but, according to some "experts" from the #GrapheneOS forum, even this couldn't be possible because, you know, ReGuLaTiOnS.

Did you know that POSIX standard specifies offset display support for "strings" utility?

strings

Very useful for pure-shell-based patching of some text in binaries (in combination with dd, of course)

OK, temporary IMEIs working. Not every time (those damn AT command timeouts or whatever) but I did see another model on my carrier's page. #GrapheneOS spokespeople were wrong, and it's just the beginning of my quest. The Graphene Saga: part 1 https://hoi.st/posts/2024-03-11-the-graphene-saga-part-1.txt

Ok, I might have found at least something regarding IMEI editing in Pixel 6. The most interesting part is that I **had to** use my carrier's personal account page to verify the change is successful (by viewing which phone model the carrier detects), because whatever is displayed at `*#06#` or `*#*#info#*#*` does not change with this hack. So my method is going to only change whatever the network sees. Exactly the opposite to what those buffoons were stating. Stay tuned.

Found a nice onion-enabled shell service, finally the one where free limits look reasonable:

The Hacker’s Choice

Segfault

Disposable Root Servers.

Of course, one can never be fully sure what they are really monitoring, so be careful.