Thread 106404142

> BeagleV Ahead Single Board Computer (SBC) (comes w/ mainline Linux support, no Intel/ARM/AMD shit in their cores, uses RISC-V architecture, is completely open source and has touchscreen compatibility)
> an open source USB-based HID-compliant resistive touchscreen (like the ones they use for raspberry pi's, such as the XPT2046 touch controller). Just make sure it's Linux-compliant. Note that the XPT2046 is compatible with BeagleV Ahead, however it requires manual setup.
> a HDMI/USB case for a raspberry pi for the buttons (power on/off and volume up/down + HDMI/USB ports to wire to your board, just make sure the GPO mapping works w/ BeagleV) and a 3D printed plastic display case to house all the components and use like a regular cell phone

>>106404142 (OP)
> SysmoUSIM w/ USB SIM card reader + Open5GS + 5GC (set APNs on the handset w/ gNB and srsRAN) + PySIM (personalize IMSI, Ki/OPc, MCC/MNC and OSIM for IMS) + an Android smartphone to clone (pick a device that supports band 48 on CBRS) + a custom build device to use + a SiFive HiFive1 B dev board, using a self-written SOCKS5 proxy scripted in Python w/ X25519, ChaCha20, Poly1305 and Kyber for quantum computer resistance, using E2E encryption on your proxy, and MAC randomization (you'll need to use an external Wi-Fi USB adapter with well-supported chipsets such as Atheros (ath9k/ath10k) for BeagleV, because it doesn't come with support for Atheros hardware or drivers, nor does it come w/ wifi drivers either, which you're gonna need to swap out MAC addresses for every connection), flash Gentoo with Wayland running over it for the mobile UI (like Phosh), which is what they use for the Pinephones (note that while BeagleV does have Wayland support, however it's still developing, so you'll have to set it up manually). Use a custom IMSI range reserved for testing. In pySIM you can define: IMSI – your chosen private ID, K_i – the secret authentication key, OPc / OP – optional operators’ keys for simulating network auth, and will use those keys to authenticate without ever touching the public network. You can bridge an internet connection via scripting a proxy and port forwarding a public VPS for SIP/VoIP so you can both connect to internet on the go and communicate outside your private network. You're just using a lab network as infrastructure to route your calls via internet/PSTN via SOCKS5 proxy without having to use a public carrier (you will need this for SIP/VoIP access to communicate outside the lab network to make your phone reachable to family/friends/whoever, using the lab network to backbone your connection).

>>106404142 (OP)
Does it use Cellular?
If not, then it isn't a phone.

>>106404164
> And you can run multiple firewalls over this (like iptables, rkhunter, clamav, kvm/qemu and firejail for a multi-layered defense). Then throw pyshark ontop and you can run your custom proxies you scripted in Python. Iptables/nftables for firewall (strict default-deny), Firejail to sandbox profiles for apps, rkhunter + clamav for integrity/malware scanning, and KVM/QEMU for isolating subsystems.
> to touch up, give it a Adafruit PowerBoost 1000C, a BMS (Battery Management System), a USB audio interface (used for RPIs), a cellular antenna for USB adaptor, thin copper heatsinks for the boards to reduce overclocking, use eMMC for SD storage and use a mini USB keyboard for use as mini-PC w/ terminal

You could stay on the go using a private carrier w/ cellular antenna on lab network. And optionally, you could use Guix + Wayland (Phosh/Sway/Plasma Mobile) instead of GNU, depending on your preference. Although note that this custom build smartphone isn't gonna replace Android anytime soon, it would just be for hobbyists and developers.

You'll need a VPS IPv4 profile to port forward (Bitlaunch or CrazyRDP because Bulletproof VPS services is blacklisted by ISPs and illegal, so due to regular seizures, I would not entrust my data with these servers) using SOCKS5 protection on the device-level for protection and full invisibility.

But if you want to avoid tunneling a connection from Owrbit/Bitlaunch/CrazyRDP to a .su/.rw./.st domain, use Indian/Tongan VPS servers, which are battle-tested also.

>>106404165
It has VoLTE capabilities. See >>106404164

>>106404188
Cool, now you need to make it in a shape of an phone not a micro CRT TV.

We don't put a space after the greentext arrow here, newfaggot. I didn't even read your post because you are obviously new. Lurk more.

>>106404204
There are some open source MIPI DSI LCDs that are compatible, but the rest are resistive touchscreens that are USB-based (XPT being but one example). Plus you'd need a USB one for inserting Wifi USB adaptor and some other gadgets. The problem is RISC-V is still in its infancy, so we haven't really graduated to having drivers yet for wifi so you can swap MAC addresses.

>>106404164
Btw, by "cloning an Android" I mean cloming the device credentials, not the operating system (which isn't compatible for RISC-V anyhow).

>>106404142 (OP)
>XPT2046
Nice stylus, faggot

>>106404164
>>106404142 (OP)
Honestly the most autistic thing I've seen this year. Even pic related was normal compared to this

>Can I have your number?
>Sure
>takes out phone to save it
>Uhh, you know what, never mind...

>>106404142 (OP)
>no vhdl / verilog files
It's trash. RISC-V is trash. You should feel like trash for believing this shit.

>>106404142 (OP)
This looks like shit lmao.

>>106404142 (OP)
if you had a real government then even your 60+ neighbor would know why their are moving to opensource fpga architectures.
Pro-tip:
those devices will be bought up for cheap by Iran etc, bypassing export restrictions. To be reprogrammed for satelite, rocket usage.
Well done, white labour camp slave

>>106406095
take'm

So where is it for sale?
Will it work in Canada?