(untitled)

Hi /tech/, I can't escape the botnet with my phone: custom roms aren't enough, and not having Gservices cripples a lot my ability to use it. I, tho, need a portable device with my passwords, totp codes and fun stuff. Is https://youtu.be/YWlZ3B_hq_g a good idea? I know that the rpi uses precompiled binary to boot, is it that big of a security hole? Is there any similar project, or can I use an alternative SOC? Thanks in advance

Stop larping. Disable kernel modules for gsm module in kernel of your Android device and use it as a PDA. Without premium, features of "DIY" Pi-device like high-resolution 640x480 3-inch display, 3-printed case and a bluetooth keyboard. >and not having Gservices cripples a lot my ability to use it. If something "cripples" it, it won't even run on Pi then. What do you need gservices for anyways? Only proprietary crapware relies on them. XMPP and offline apps are fine without it,

>>7161 >What do you need gservices for anyways? I would use this as secondary device, I still need whatsapp, gmaps and normal person stuff in my day to day life >Disable kernel modules for gsm module in kernel of your Android device and use it as a PDA. I would need a keyboard for that, and I would still have the full android stack, that I don't need. Can I recompile the kernel and use just fbdev and the tty, then install the full gnu userspace with gcc and a package manager, possibly binary? I'd like not to use the chroot approach, but to have a bloat free enviroment.

>>7162 P.S., that's something that I still can't figure out Are drivers in an android device on the jvm stack? How deep can I get without breaking everything?

>>7161 >Disable kernel modules for gsm module in kernel of your Android device That's an interesting approach. It doesn't solve the problem if the baseband processor doing it's own thing and having full access to the phone's ram though. >>7162 >Can I recompile the kernel and use just fbdev and the tty, then install the full gnu userspace with gcc and a package manager, possibly binary? You may be interested in a project called PostMarketOS. I think you will need a physical keyboard if you go with this approach. >>7163 >Are drivers in an android device on the jvm stack? No they're not. Android is basically an embedded Linux box and then in userspace there is a Java (Dalvik) environment for apps to run in.

>>7162 You're doing it wrong. Get a phone for CopperheadOS or a Galaxy S2 with Replicant, don't install Google Play Services, replace WhatsApp with Signal and Maps with OsmAnd. Stop moaning about the botnet if you keep enabling it, you might as well stick a Google Probe up your butt.

>>7164 Wouldn't just removing the SIM card solve most potential issues with the baseband processor? Not registering with the network should make it quite safe, right? Of course only if it doesn't control WiFi as well - not sure if that's often the case. And since we are discussing PDA's and disabling GSM, wouldn't it make more sense to get some more FOSS friendly tablet instead?

Look into Postmarket OS.

>>7164 Just an FYI, they phased out Dalvik in favor of ART (android runtime)

>>7162 >I still need whatsapp, gmaps and normal person stuff in my day to day life I feel ya. You can use whatsapp without gapps and change gmaps for osmand and you'll be good to go. if you still need to install apps from the normal store and you're too fuarrrking lazy to download apks, install F-Droid and search for Yalp Store.

>>7177 >Wouldn't just removing the SIM card solve most potential issues with the baseband processor? No because SIMless phones still join the network to make emergency calls (to the police etc.). So even without a SIM card and without relevant code in the Linux kernel they can still be used as remote backdoors. >Of course only if it doesn't control WiFi as well - not sure if that's often the case. I wouldn't think so because they are different frequencies. WiFi and Bluetooth tend to share the same chip because they are both 2.4Ghz. The problem is everything is glued onto the same soc with access to the same ram so a malicious wireless processor can compromise the whole phone. Google Project Zero has a good series of writeups on exploiting broadcom wifi chips over the air and using them to get code execution under android. >And since we are discussing PDA's and disabling GSM, wouldn't it make more sense to get some more FOSS friendly tablet instead? I've been looking into that. Tablets tend to be big though. Even the kiddy ones are still 6 or 7 inches. There are some phone sized non-phones. Nokia N810 is a nice one because it is basically Debian inside, but it's pretty old and hard to find now. iPod touch is another idea but they are not really foss friendly, you are kind of stuck running your soykaf under the iOS kernel.

>install Signal good goyim

>>7192 >Talk soykaf about a proven /sec/ app without any argument or proof Good nonfat-soykaf drinker

>>7190 >The problem is everything is glued onto the same soc with access to the same ram so a malicious wireless processor can compromise the whole phone. That's what I was talking about, can I ever feel secure with a smartphone? They are basically backdoored at hardware level.

>>7197 There's an argument to be made that all commercial hardware is backdoored. The problem with phones is that the long range radio makes the backdoor accessible no matter where you are relative to the attacker. And phones have cameras and microphones and gps and all your emails and im messages and personal data. It's pretty bad. Purism is working on a phone which will isolate the baseband and limit the damage it can do. We'll see if that ever gets finished. https://puri.sm/posts/librem-5-roadmap-to-imx8/

>>7197 You shouldn't, but then again if you use them wisely they're immensly powerful tools and not more of a threat to your privacy than any other cellphone. Most people do not, I have to admit. >>7192 What else would you use?