CalcProgrammer1 @ CalcProgrammer1 @lemmy.ml

Software Engineer, Linux Enthusiast, OpenRGB Developer, and Gamer

---

Read more

Posts

0

Comments

452

Joined

4 yr. ago

I went through probably 20 different iterations of keycaps and got close to one I liked, but haven't gotten back to finishing the project since I haven't been using my PinePhone much. I think the main remaining thing is to make an Enter key model and a Tab key model. I want to get back to that project eventually but haven't had time.

AOSP and even factory kernel source tends to be only mildly useful for proper Linux phone use. Android phones tend to ship with old kernel revisions that the chip maker forked a long time ago and developed their chip drovers on without following accepted kernel conventions or submitting any code to the actual kernel maintainers for proper review and integration into the most up to date "mainline" kernel. Due to this, and the fact that phone makers need to constantly ship new products out the door, the quality of this code added into the old kernel is often garbage, poorly commented and with no documentation. Usually no git history either.

There are other teams of people trying to clean up and/or rewrite these drivers from scratch in a way that is reviewable and acceptable in mainline. Only a small handful of the vast number of phone chips have such support, so proper Linux phone is limited to a small selection of hardware. The designed-for-Linux librem and PinePhone models intentionally chose old chipsets because these chipsets had good mainline support and thus could receive actual kernel updates rather than being stuck forever on an ancient kernel release from the manufacturer that has long since been abandoned.

Lately the Qualcomm Snapdragon SDM845 chip is seeing growing mainline Linux support and quickly becoming one of the most viable chips for mobile Linux that isn't a complete dinosaur in terms of performance and power draw. The OnePlus 6 and 6T, which both use the SDM845 chip, have become quite popular as Linux phones now despite not yet having VoLTE and thus being useless for calls. I carry a OnePlus 6T as a secondary non-phone pocket PC because the Linux experience is very good other than the lack of phone and camera functionality. It's fast and can do all my terminal and coding stuff as well as run full fledged web browsers well.

Nice review. I agree with others here that this phone is borderline scam for the price and with all the delays people had in receiving them. Performance seems on par with the $200 original PinePhone which I had a similar experience with.

The one good thing that came out of Purism/Librem 5 is Phosh. It's a pretty good phone shell/UI for other more capable Linux phones to use. I particularly like Phosh for its on-screen keyboard Squeekboard which allows for custom keymaps.

Then you run far, far away from that app. Even on an Android phone I don't trust garbage apps that require locked bootloader and no root. There are plenty of banks out there and paying with your phone is not a necessity.

We have Waydroid which is close enough. It needs some quality of life improvements for better integration with the native Linux ecosystem but it runs Android apps just fine on Linux phones.

I haven't used it on the PinePhone or PinePhone Pro in a while, but Waydroid is solid on my OnePlus 6T with postmarketOS. Android apps that only need an Internet connection work fine. I installed microG and have push notifications working for Discord and Teams. However, notifications don't get passed through to the Linux side so they only show if you open the Android UI. Screen rotation doesn't work on Waydroid which can be very annoying. Apps that use other hardware features such as location, Bluetooth, vibration, access to calls/texts won't work properly.

I tried to daily drive a PinePhone for a long time, then a PinePhone Pro. It is not really ready. Too many dropped/failed to answer calls and missed texts. I love having a fully capable Linux PC in my pocket and am typing this on my OnePlus 6T with postmarketOS, but as a phone it is not ideal. My setup now is that I have a OnePlus 6 with stock Android and my main SIM for doing phone stuff (calls, texts, some apps, Bluetooth handsfree) and the OnePlus 6T with pmOS for Linux experimentation and doing pocket computer things (browsing, coding, SSH, VPN, testing Waydroid). I got a second cheap SIM so I can have service on both devices, but as the 6T with pmOS can't receive calls in 4G mode it really doesn't work as a phone. The PinePhones can work as a phone but the modem dropouts make it less than ideal and their battery life and performance leave much to be desired while the OP6T has fairly good performance and battery life on pmOS.

I have Waydroid set up on my postmarketOS OnePlus 6T mainly so I can use the Discord app. Waydroid still needs some integration issues worked out (access to location, access to Bluetooth, access to calls/texts, ability to forward notifications to the Linux side) but otherwise it runs quite well. Performance feels pretty similar to native. I also have a OnePlus 6 running stock OS for my main phone tasks as pmOS doesn't have VoLTE support for the 6T so is kinda useless as a phone right now.

I've had an A770 Limited Edition since its release in late 2022. Overall, I'm happy with it. The drivers were a mess at launch but now everything works as expected. Performance is decent in the games I play, though I have a 144Hz 4K monitor and it's not really capable of that resolution and refresh rate except on the lightest esports games so I use FSR on most games. My most played game is Overwatch and it hits 144Hz with dynamic resolution scaling on and medium settings. I want to buy a higher end GPU eventually to really push this monitor but waiting to see what happens with the next generation of Intel and AMD cards (NVIDIA is not even in the running unless NVK suddenly gets performance parity with the proprietary drivers).

Steam Deck is an open platform because you can run any OS, launcher, etc. on it. It's just a handheld PC. Steam itself is a closed ecosystem but the Deck is very open.

That's why I mentioned the "without an OS installed already" though a corrupt OS is another possibility that would need some other system available (whether phone, tablet, another Deck, or PC).

GitLab used to be awesome when it was the place to go after MS bought out GitHub. They had premium access for all public projects under a FOSS license and top-tier CI. Then as time went on, they began pulling support for various functions in a very Microsoftian EEE sort of way. First requiring credit cards fir new users to access the CI, then taking away the CI almost entirely except for a practically useless monthly allotment, then taking away the premium access for public FOSS licensed projects. If I were migrating today I would not have chosen GitLab, but it is where I settled after leaving GitHub and my projects have grown to depend on GitLab CI even if I'm now forced to run my own runners due to the extreme nerfs they've done to the hosted CI. I mirrored OpenRGB to Codeberg, but since the CI pipelines depend on GitLab I don't see Codeberg becoming the main hub anytime soon unless they can execute GL CI configs. Sad to see how far GitLab has fallen though, it is unrecognizable from what it used to be as far as support for FOSS prohects goes, especially given how GitLab itself started as a FOSS project.

And you can create the bootable USB with the Deck before you swap the SSD. You should never need a second PC to set up the Deck unless you bought your Deck without an OS installed already.

Leo's covers are the best, been following him for years.

Plug in hybrid usually refers to a car that has some amount of purely electric range, charges like an EV, but after depleting its battery falls back into conventional hybrid mode where the battery is maintained to some level of reserve power using a gas engine. The Chevy Volt is probably the best example. I drive a Volt and all my daily commute is purely electric unless it's super cold outside.

I love my 2014 Gen 1 Volt and would love to see the technology continue to improve. If they made a Gen 3 Volt with at least 100 miles all electric range and a heat pump system that didn't halve the battery when it's cold outside I would absolutely consider it over a pure EV for my next car.

AMD's integrated GPUs have been getting really good lately. I'm impressed at what they are capable of with gaming handhelds and it only makes sense to put the same extra GPU power into desktop APUs. This hopefully will lead to true gaming laptops that don't require power hungry discrete GPUs and workarounds/render offloading for hybrid graphics. That said, to truly be a gaming laptop replacement I want to see a solid 60fps minimum at at least 1080p, but the fact that we're seeing numbers close to this is impressive nonetheless.

Pretty much all the alternative SBCs are either Rockchip or Allwinner if you want ARM. There are a few RISC-V SBCs now but software support isn't as solid and many of these lack GPUs. There are also a few x86/64 SBCs based on either older Intel Atom or newer mobile parts too.

There are plenty of alternative SBCs out there, many mimicking the RPi form factor as well. Look into Radxa, Banana Pi, Orange Pi, Pine64, ODROID, etc. I picked up an Indiedroid Nova board last year that is RPi form factor but has the more powerful RK3588 processor. Drivers are still WIP but it is quite fast. I also run my home server on a Radxa Rock Pi 4, which has an RK3399 processor and is very comparable to the RPi 4. Drivers for it are pretty solid these days and it doesn't require extra work to set up. Just download an Armbian image and go.

I'm fine with Apple retaining interoperability between their first party software products, they just need a way to bypass the walled garden. If they have sideloading (everywhere and without restrictions) and ideally also bootloader unlocking, they provide a sanctioned path around the walls of their ecosystem and now it's up to the user to choose to leave that garden. If the user is comfortable there, they can stay. Trying to fuck over sideloading is the issue here. I'm fine with the App Store being restrictive if there's a way around it, and simply sideloading an app shouldn't break the rest of the OS's capabilities.