



The point of this is to break Fdroid, as the point of removing device tree publishing from their phones was to remove third party ROMs that would ignore the requirement for verification, as well as the changes to AOSP updates. This is a war on users that want to keep control of their phones and when it’s done, you will not be able to escape the enshittification and surveillance. And I’m convinced that was the price they paid to get out of the FTC lawsuit.


What I remember most was having to make an e/OS account a la google in order to be able to use the ROM, and some of the third party apps it shipped with were of dubious origin, mainly Chinese IIRC. I’d heard other sources talking about it being behind on patches then as well. Overall, it gave me the ick, especially the account bullshit, and I continued with Lineage.
Not sure why you feel the need to call me a scumbag.
I switched from a Pixel 4a to a Moto Razr when the 4a lost support, because I wasn’t going to go any bigger than the 4a. Wish it had a custom ROM like Graphene though.
I’ve actually been really happy with the Razr for size and screen protection when folded. Haven’t broken it yet and that’s a record for me.
The 6a replacement screen is damn near the price of another used phone. I’m with the other poster, I ended up just getting another used phone, a Moto Razr+ 2023 fold. Unfortunately, no custom ROMs for it that I’ve found.
So I’m a farmer and the unholy things that my phone get subjected to makes it hard to find something that’s strong yet useful. I’ve either been lucky or this phone is exactly right for my lifestyle. It folds up small enough that it doesn’t get bent in my pocket or fall out. I’m a little worried about the outer screen but I’ve dropped the phone closed a couple times on gravel, no damage. And I think it closes up small enough that it might survive a trip up the grain auger, which is what got one of my phones a couple years ago. I haven’t had a phone survive so long undamaged yet. And I just have a pretty minimal case on it, no hinge protection.
Now that I say that, I’ll break the screen tomorrow, I imagine.
If you don’t find a FOSS one, my wife and I have used OurGroceries for years and it’s a dead simple shared list app that can do more if you want, but it’s hidden behind the simple bit. I’ve been thinking I should build a selfhosted version myself because if it went offline, I’d be lost. I use it for quick lists if I’m working on something and need a bunch of stuff from the garage/toolbox, or a list of things I want to research later, etc, etc.
Installs all apk files in a given folder to a connected device.
#!/bin/bash
# Check if directory argument is provided
if [ $# -ne 1 ]; then
echo "Usage: $0 <directory_path>"
exit 1
fi
# Store directory path
APK_DIR="$1"
# Check if directory exists
if [ ! -d "$APK_DIR" ]; then
echo "Error: Directory '$APK_DIR' does not exist"
exit 1
fi
# Check if adb is available
if ! command -v adb &> /dev/null; then
echo "Error: ADB is not installed or not in PATH"
exit 1
fi
# Check if any device is connected
if ! adb devices | grep -q "device$"; then
echo "Error: No Android device connected"
exit 1
fi
# Count total APKs
total_apks=$(find "$APK_DIR" -name "*.apk" | wc -l)
if [ "$total_apks" -eq 0 ]; then
echo "No APK files found in '$APK_DIR'"
exit 1
fi
echo "Found $total_apks APK file(s)"
echo "Starting installation..."
# Counter for successful and failed installations
success=0
failed=0
# Find and install all APK files
find "$APK_DIR" -name "*.apk" | while read -r apk_file; do
echo -n "Installing $(basename "$apk_file")... "
if adb install -r "$apk_file" &> /dev/null; then
echo "SUCCESS"
((success++))
else
echo "FAILED"
((failed++))
fi
done
# Print summary
echo
echo "Installation complete!"
echo "Successfully installed: $success"
echo "Failed installations: $failed"
echo "Total APKs processed: $total_apks"
Enshittified garbage. I bought the last generation and it’s unusable unless you fully submit to the Google shackles. Didn’t even want to have the damn thing in my house and took it back.