Your not missing out. The 2GB model has faster eMMC speeds and you can most likely get higher overclocks out of the RAM.
The SoC is a bit underwhelming for a laptop, that’s for sure. But for the price i guess you really can’t complain too much considering it’s a small-volume device and it’s running open source software. Hopefully the RK3588 comes out soon (finally) and pine can start working towards getting it up and running and proceeding to pack it into a pinebook pro with 8GBs of ram.
They actually only have a select number of those 3GB ram chips available. They are rare to find, and especially with the component shortages going on it likely wont get any better. So it’s possible that one day they wont even be able to offer the 3GB version anymore. That said i honestly don’t think it’s needed as mobile linux so far is pretty well optimized, with only more optimizations to come over time ideally. And infact the 2GB pinephone has much faster eMMC speeds than the convergence model, not to mention it seems there’s a much better chance of being able to overclock the DRAM of the 2GB model than the 3GB one and maintain stability. As for convergence… that’s kind of a pipe dream with the current hardware… it just isn’t up to par outputting to a 1080P or higher resolution (The A64 has a Mali 400 MP2 which was the first arm mobile GPU to have OpenGL ES 2.0 support back in 2008… And it’s weaker than a first gen iphone’s GPU). Not saying the pinephone is bad, but it’s intended really as a development platform and a toy, not a device for consumers to use yet. Hopefully the next edition comes not too far in the future and really rocks the socks off of everyone.
The idea is that this current pinephone will be low end to force developers to optimize for low powered hardware. That and it’s a phone… you only have one app open at a time… And with only a few tabs open in a mobile-oriented browser such as angelfish or morph you shouldn’t be anywhere near using up 2 GBs. Things are much lighter in Linux than android. As for games, the A64 is the bottleneck anyways. By the time an application will start eating up anywhere near the 3GBs of ram (or even 2GBs), the A64 will already be the main bottleneck to things running smoothly, not the ram.
Well as i understand it the A64 can only access 2GBs of ram at one time because it uses asymmetric dual rank ram. Perhaps that has something to do with it as well.
Fun fact, the eMMC of the 2GB pinephone is actually MUCH faster than the 3GB’s eMMC module. Further the 2GB ram chips for whatever reason are better overclockable with the A64.
I feel you. It’s happening in the US too. Sadly it’s only just started. Get ready for some rough years.
Plamsa has it as a built-in option among other sources like NOAA. Though i doubt that makes it worthwhile for you to jump DEs.
I use mullvad, not because i expect 100% privacy (pretty sure it’s in 5 eye country too), but because i trust them to handle it slightly better than my ISP at least.
I think going forward I’d rather just use lemmy.
I use my Pinetime daily with WaspOS. It’s been great, but it’s definitely not at the same tier as a mainstream smart watch. I see it as a handy tool for telling the time, acting as a flashlight for really dark rooms, and doing alarms. WaspOS does support notifications but only with android devices. I think once I start using my Pinephone as a daily driver in a month or two I will switch to Infinitime which has more features and has a native app for the Pinephone.