>>686 It is still unusable in many ways. Sometimes basics like Wifi won't work and software, while evolving still needs time to mature.

>>1794 It has since died. It was running Android 5.

>ARM >open hardware

>>685 are you schizos that retarded? If they wanted to go through all this hustle just to spy on you they'd just make a normal phone and deal with the marketing crap. Whats next, metal alloy case that feels like plastic but is secretly modified to conduct electricity in a way that bypasses the actual hard switch?

'Murrican here. What about this whole thing with At&t demanding phones need VoLTE compatibility starting in 2022. I have Cricket (owned by At&t) and just discovered this. Like fuck-all of any decent phones are on the compatibility list and it sounds like they're just dropping service for them. I honestly don't know how I've only heard about this just now, or why I haven't seen anyone, especially on boards like these, talking about it. Perhaps this isn't the right thread for it, but it's kinda relevant since I considered getting this phone but now I can't since it won't work on Verizon, At&t, or T-mobile, or any carrier operating on their infrastructure. Please tell me I have this completely wrong.

How would the security of the device be if someone got access to it while it was unencrypted? As I understand it Android is still pretty secure as long as it's behind the lock screen even if the phone is turned on as long as USB debugging isn't enabled. But if you're logged into your user account and there's only a lock screen between a bad actor and your machine in public or if they've captured the device how would it fare? I suppose at least with Linux it wouldn't be too difficult to set it up to instantly flush the memory and power off.

Man when will pine64 get their shit together and get stuff back in stock and release their products in a timely manner instead of just delaying releasing it makes them look like shit and can they actually get their products out of beta before creating a new project to work on, most of their shit is so unfinished.

>>198 >don't cut off power to the camera. wouldnt the old electrical tape trick still work? i had a phone a few years ago where i was able to physically remove the camera from the phone shell, it was only attached via a ribbon cable

>>216 >I'll personally take my oscilloscope to the wifi modem and cameras just to prove your tinfoil ass wrong. what if i use a precision screwdriver to destroy the wifi modem and cameras? i did that with my old phone's speaker to make it silent (except via headphones). i also plucked a few led's off different pcb's on flash drives and stuff, that worked fine. will the pinephone refuse to boot if the camera lense is crushed?

>>4884 >are you schizos that retarded? If they wanted to go through all this hustle just to spy on you they'd just make a normal phone and deal with the marketing crap they put dummy buttons in elevators to make people feel in control of the doors opening/closing. they put dummy buttons at crosswalks to make pedestrians feel in control of the walk signal. why do you doubt a phone manufacturer would put a placebo switch on their device?

>>284 >that's we they're lying about fake disconnect switches that just send the same signal as the OS For me the issue is not so much about whether or not the hardware switch is sending the same signal as the OS on a normal phone, it's more about how the signal is being sent. As this anon >>217 said, >Try transmitting or receiving with the rtl8723cs when it's chip enable isn't enabled I am confident enough in the hardware to trust that it will do what it is supposed to do when the appropriate commands are sent. But I am not at all confident that an operating system will do what I tell it to do every time, especially not one owned by Apple or Google. I have seen different OS enable switches not work at times on my old Iphone, and I have even seen them turn themselves back on after I turned them off. The hardware switch on the PinePhone removes this variable

>>5207 > but now I can't since it won't work on Verizon, At&t, or T-mobile, or any carrier operating on their infrastructure I bought a PinePhone last year and T-mobile gave me service On this note, does anyone have any carrier recommendations for the PinePhone in the US? While T-mobile did connect my phone, they don't have any service at my house, so it was kinda pointless. The phone appears to be compatible with US Cellular networks, but they won't allow it on their network. I haven't tried Verizon yet because I can't stand them.

>>6572 tello for phone calyx for data

>>6598 Well unfortunately Telllo runs on T-mobile towers, so that won't help Calyx is very interesting though, thanks for sharing

This is not exactly Pinephone related, but here's an interesting discussion on secure phones and the levels that authorities went to in order to gain access. <No they didn't build a custom chip that pretended it was doing something that it wasn't https://darknetdiaries.com/episode/105/

>>191 Here's a schematic for ya, my ass.

>>114 >Pinephone Don't be a bunch of raycists anons, get a Google Pixel instead as featured in the Super Bowl commercials yesterday.

>>7464 >low dynamic range + underexposed >niggers are underrepresented in photography :*( >higher dynamic range + ideal studio/outdoor lighting >cutting edge camera technology that ends racism forever I wish marketing executives had reason to fear for their lives for putting out shit like this

How secure is an Android phone with a custom rom? If it's possible to unfuck a phone with decent specs I'd like to do that instead of deal with limited hardware.

>phone kys loser

I was interested but then >32 bit risc >secure custom OS >soldering iron These people are just retarded.

>>7464 Wow very beautiful

>>7464 >bad pics are black gorilla niggers in bad lighting >"good" pics are mostly light skinned mutts in good lighting such technology <second pic Some based intern must have snuck that in because that's a comical lack of self awareness.

>>7464 It's just niggers, fags and cripples from here on out until the end of time, isn't it?

>>8365 You forgot drooling retards such as yourself anon

>>114 ACTUALLY trash.

>>114 >open hardware phone bullshit They don't release full schematics/boardfiles. If they can't even do that partially (no, what essentially amounts to generic "pinout maps" doesn't count). There's severly diminished hackability, repairability and extensibility if you can't even look at the schematic/board layout to see what components with what values are where and connected how. That aside, it's at least a step in the right direction. Fairphoney died for me the moment they decided to remove the headphone jack becaue their incredibly limited, specific, niche base of potential buyers that in no realm here or elswhere would be bothered by a few mm³ extra "wanted it". AARRRGHHGHGGHGG

>>284 >>tl;dr trust the chip bro You made a sweeping assertion. Anon refuted your assertion by putting it in context with the general situation. Shut up if you won't read, retard. Or annoy these guys: https://libresilicon.com/ but for goodness sake stop this asinine bullshitting when another anon takes time to give you a reply in good faith. >>284 >power source being disconnected. you know nothing about hardware, putting a power switch into VCC on these chips is retarded and unreliable. Chip enable pins are there for a good fucking reason and having chip-enable not respond is the easiest to find out. There's much better chance at the firmware level. Right now a bridge-solution would be to build a device/os in a way that allows compartmentalization of e.x. the modem so we can put it in a quarantine both on the software and the hardware level. Modems usually have direct memory access, that's a relevant thing to argue about, not fucking putting switches (i.e. variable R-C-L components) into the goddamn VCC of the wifi chip. >>289 My guess would be that the switches do the same thing as what some output pin does when the OS is employed to "turn off" the wifi - the chip enable pin. Let us know why you're talking out your ass as you are talking out of your mouth, shit-blabbler. https://yewtu.be/watch?v=Q4PC8Luqiws

>>10083 I know, I just want it to be said because that shit was infuriatingly stupid. Nice to meet you. At least you read it so when another fool starts blabbling about it you can refute it in rough terms. h-hey why'd you delete?

>>10084 >h-hey why'd you delete? because i remembered that covid only killed geriatrics and aids patients, and then my joke didnt make sense anymore

>>10085 Kek okay anon. cya

>>10090 he probably also thinks that if he turns on airplane mode that google deletes his history

>>10094 You will never be fully vaccinated

>>10096 I was fully vaccinated before I could form memories of what it was, because I got the MMR near infancy. I'm told I was a cranky child for quite some time afterward.

Got the pinephone, works great for what it is. Got the keyboard, remember to avoid using the phone usb with the keyboard mounted. 1 year later, battery unit in keyboard still works great, but keyboard died after auto-repeating a ton of characters while writing a text message. Felt like a cable failure to me, similar to how a laptop keyboard goes out sometimes. Now I need to pry open the keyboard and try to figure out why pine64 does not sell replacement cables for the keyboard's internal pogo pin interface to the phone. The hinge still works good, but the cable was routed through there, and would obviously flex a little. I do not think it is a ribbon cable, at least. Just really thin gauge wires in a sheath.

>>114 <GLOWIE POST >GLOWIE POST <GLOWIE POST >GLOWIE POST <GLOWIE POST >GLOWIE POST