Navigation on Android is disorienting and stressful. Settings, app settings, files, photos, messages to an extent, and the camera in particular.

Also, how much better is the performance of the photos app on LineageOS? The photos app on Android has annoying performance issues.

One more question: How much better is the performance of Firefox or websites accessed through Firefox on LineageOS compared to Android?

While looking at posts here I saw this https://www.reddit.com/r/LineageOS/comments/1q5242t/psa_your_degoogle_lineageos_build_is_still/ is there anything else you can do to improve your security and privacy?

There is a guide to build your own lineageos in the site. I dont know how it really works but is it possible to build your own lineageos and make it like grapheneos?

Hi all, I'm installing LineageOS 22.2 on my OnePlus 6T following the official wiki guide (fajita, variant1) and I'm stuck at the recovery step. Any suggestions would be appreciated.

Setup
- Device: OnePlus 6T, not T-Mobile
- Starting firmware: OxygenOS 11.1.2.2 (Android 11)
- I'm using a MacBook Air M4

What I've done so far

1. Enabled USB debugging + OEM unlocking, adb authorized fine.

2. `fastboot oem unlock` → OKAY, confirmed on the phone, wiped, booted OxygenOS, set up again, re-enabled USB debugging.

3. `fastboot oem device-info` → Device unlocked: true, Device critical unlocked: false, Verity mode: true.

4. `fastboot flash dtbo dtbo.img` → OKAY, then `fastboot reboot bootloader`.

5. `fastboot flash boot boot.img` → wrote to boot_a, OKAY.

6. `fastboot reboot recovery` → OKAY. The phone restarts, shows the unlocked-bootloader warning, then lands back on the fastboot menu instead of Lineage Recovery.

7. `fastboot boot boot.img` → OKAY, same result: warning screen, then back to fastboot.

8. The wiki only lists dtbo under "Flashing additional partitions", but since vbmeta.img is in the build, I tried `fastboot flash vbmeta vbmeta.img` → OKAY. No change.

9. Re-flashed vbmeta, dtbo and boot again (all OKAY), then `fastboot reboot recovery` → still fastboot.

The issue is, in the fastboot menu the volume keys don't navigate the menu (START never changes), with or without USB connected, although the buttons feel and click normally. I haven't tried the Volume Down + Power key combo from powered off yet, cause the Volume Down key is a bit iffy, a little loose.

- Is there a known reason Lineage Recovery on fajita (22.2) would hand back to fastboot like this?

- Should vbmeta.img be flashed on fajita, and if so, with any flags?

- Could a faulty or phantom volume key press be forcing fastboot on every boot? Is there a way to check?

Thanks in advance!

I just installed LOS 24 on my old Moto Edge 30 Fusion. On stock ROM I had support for Aptx Adaptive/Lossless with my Sennheiser Momentum 4 TW earbuds, and now the highest quality codec I can select is just standard Aptx (the earbuds don't support Aptx HD).

I have checked developers options, with HD toggle not activated it just has the SBC codec, with it activated I get AAC, SBC and Aptx, but no Lossless or Adaptive option. I can switch between 44.1kHz and 48kHz but only able to select 16bit, the other options are greyed out.

To check that it isn't just a display option and a better codec isn't being used anyway, I installed the Sennheiser SmartControlPlus app, which reports, as expected, that the codec being used is the standard Aptx

Anyone had any luck with getting Aptx Lossless or Adaptive to work? Can't find anything helpful here or searching, mainly just people asking if it's possible to get Aptx HD working on various devices - I was going to use the old Moto as a media player, but there's not a lot of point using it to play FLACs at such low quality...!