verspielt verspult 🫠

  • 0 Posts
  • 23 Comments
Joined 2 years ago
cake
Cake day: June 23rd, 2024

help-circle


  • This is a great summary. Also, see the GrapheneOS teams list of hardware prequisites. They have said themselves before that this is not a very high bar, but that there are just no other manufacturers focusing on security. Apple claim they do, and get recommended as second best option in the forums sometimes, but given the walled garden approach, it must be next to impossible to develop against, even if they unexpectedly completely open up their ecosystem.

    They would probably also have to take a lot of criticism for their implementation approaches and their brand integrity would suffer immensely. Maybe there would even be some new undisclosed vulnerabilities to fix, like the goto fail bug breaking SSL encryption ten years ago.

    Compare it to the new open source Nvidia drivers for Linux, they have taken quite a while to develop since Nvidia announced the release, and I don’t know if they have yet reached the performance levels of the proprietary ones. Doing this for a whole Phone, given they even fulfil the requirements hardwarewise, will probably take a decade. And in this decade, ten new iPhones will be released…


  • There are no phones with working encryption (a must imho and a lot of others) except the ones I listed in my initial comment. iPhones are no option because they are not unlockable. Samsung recently announced they will remove the option to unlock the bootloader as well. They also have a very broad and everchanging lineup of phones.

    Google Pixel has been more of a hardware and software reference to developers than a Phone people would usually buy up until the redesign with the Pixel 6. There are so many hardware and software features that make it the perfect device to develop against (up until the recent events lol).

    I’d recommend you to read their own documentation on this topic.




  • I always point people here: https://youtu.be/uPYjJYQEFSg

    Hard to give you hints when we don’t know what your background is, so here is some basics:

    For starting selfhosting I’d recommend getting comfortable with the linux command line at first (this may help: https://www.linuxcommand.org/). Set up a VM in Virt-manager / VirtualBox / VMWare / whatever hypervisor you want, install a Linux image (I’d recommend plain Debian without desktop environment). Now you have a sandbox where you can toy around. If you’re on windows you can use WSL2. If you’re already on a linux desktop, toy around there.

    If you already got some hardware like a raspberry pi or old Laptop, get that up and running with a distro of your choice, plug it into your network and SSH into it, then you have got your playground there. Get the basic commands in like ls, pwd, cat, tail, touch, mkdir, rm, … And some things you can do with them. Check out their respective man-pages.

    After that, install some packages, change configs (I’d recommend nano over vim for starters). From now on, there are no boundaries of what to do. Set up your first basic webserver with apache / nginx / caddy, install docker / podman and containerize / get some images, set up pihole, nextcloud, jellyfin, do whatever you like… Congratulations, you are now “self hosting”.

    Maybe some day switch that Raspberry pi out for a thin client as seen in the picture from OP and install a hypervisor like Proxmox on it. If you got all that, which may take a while, you can consider networking and firewalls IMHO (you could get a cheap router that supports OpenWRT to learn about these things). Don’t open ports to the internet as long as you’re not 100% sure what you are doing. You can set up a VPN with DynDNS on most modems / routers connected to your ISP though, opening up your self hosted services only to you / anyone with access. Or use something like Tailscale / Twingate.

    I could go on, but like I said, self hosting and home labbing is kind of use case / requirement specific.



  • I actually plan on putting hardware related stuff on an extra pi since I only run a single proxmox node right now. Would be home assistant and nut tools for the ups but I might put pihole and unbound on that as well.

    I am worried about the performance though because of home assistant. And it is pretty comfortable to have everything on one host that is far from being used to capacity anyway.


  • Without support from the vendor they don’t. Mobile computing is so locked down right now that it might be possible that not even the vendor can repair a bricked phone tbh.

    Compare it to a broken BIOS on a PC. You can basically throw out your motherboard if you fail while updating it. Some devices have hardware pins used only for provisioning and debugging (JTAG) but they would have to be reverse engineered first.




  • I’m not into drama in general, and those are serious allegations. He sure had questionable stuff going on, but considering him being an actual nazi had always seemed far off to me, but we’ll never know.

    This guy rambling about degoogling and GrapheneOS, to an audience (700k views after 3h) that surely has nothing to do with that, is just great news to me as of now.



  • Those do not have to cancel each other out necessarily. The open and modular design of Application APIs in AOSP lets the user decide which way they want to interact with the devices they own compared to the walled garden. Graphene does an excellent job by leveraging this design with further encapsulation while focusing on baseline compatibility and keeping up with google. Sadly the last one is a difficult task, so some features may take their time, while others we may never see.




  • Thanks for the great writeup! Some of your Issues may be fixable, others stem from the fact that its sadly an alternative OS developed by a hand full of people compared to a multi billion dollar corp. But trying out new things and seeing true progression in development can be exciting too / make up for the inconveniences. In the long run this project can’t stay dependant on google, since they make their money from data and not hardware, and one of GrapheneOSs main purposes is to remove that source of income i guess. Also google is known to kill their products out of nowhere. Anyways:

    • I don’t know much about Immich myself but its a pretty young project, maybe the kinks will work out someday. In the meantime you could try Nextcloud. It has a specific Photos application and you can enable auto upload on your phone. You could also sync your contacts, calendar, notes (in markdown), etc. Would also sync to other devices and you would have kind of a backup. The Nextcloud Notes App is really good as well.
    • If you would want to ditch Spotify in the future (hardest of all subscription services to substitute imho) you could try jellyfin + finamp
    • You could also use the Aurora Store to get Apps from the Play Store API without enabling Google Play Services. For the apps that need it you could install those in a second user profile (which can be allowed to run in the background) with Google Play services and Play Store. Notifications work for most apps (I don’t use whatsapp) but there is a permanent silent notification. This is needed so that android doesn’t kill the app. You can disable those from appearing in the status bar.
    • If you use TOTP for 2FA you could try Keepass. There are several implementations. The classic one would be Keepass2Android. Another one with a more modern feel to it would be KeepassDX. You can also use it to store and autofill your passwords. It stores everything in a file which can be synced both ways, using e.g. Nextcloud
    • Battery life is rather a GrapheneOS Issue than an Android one. The reasons are additional encapsulation by using containerized apps, missing optimization since google pulls features from AOSP into apps you only get from the Play Store / with Play Services etc. But then again, I noticed that most of the battery (about 2/3) on my phones is used by mobile data / connection. If you have bad signal like me its harder for the phone to stay connected. On my testbench pixel 6a without a SIM card I got about 3-4 days with regular usage compared to 1-1.5 days on stock Pixel OS with a sim card installed (Google Play Services lives in another profile which is shut down when in background).
    • Fingerprint recognition is a hardware issue since the Pixels up to version 8 use optical scanners, from Pixel 9 on they use ultrasonic ones which are exceptionally good. The phone is unlocked before the screen even turns on. As others said, you could register the same finger several times. It’s still usable, you just have to be careful to not leave a single grain of dust under screen protectors in the region of the fingerprint sensor though and rescan your fingerprints after installation.
    • I don’t have USB connection issues, neither when playing music in the car over an adapter nor when transfering files. You could try disabling the USB security feature where the data pins are deactivated on hardware level when the phone is locked.
    • There has been a bug with auto brightness for about a month in the upstream Pixel OS that causes the screen to go completely dark sometimes, but other than that i have always found it pretty reliable.
    • Google Keyboard is really good (for which you can and should disable network access on app level) but FUTO Keyboard is great as well. I guess it’s just your muscles being used to something else since i really can’t type on the IOS keyboard ;)
    • Vanadium has a reader mode. Its just patched Chromium after all.
    • Google Camera App is a must imo. You can disable network access and it doesn’t need Google Play Services to function (for now).