Database Develop

It seems 4.2.2 updates has some media server fixes

Going through the change log posted on android police. I noticed this part. I am not really able to make sense of the commit but it seems to contain some fix for the mediaserver service (which has been a cause of many battery user reported battery drain problems) guess we have to keep our fingers crossed.
Bug 7463620."
Change-Id: I3b7e7ebe660bb3f0e4367d2a3ed63ee76f78fe58
commit cd3231f501b7ee038af5ab378ee5550090b7bc2e
Author: Eric Laurent <[email protected]>
Date: Fri Nov 2 16:48:26 2012 -0700
audio service fix dock after crash - DO NOT MERGE
merge from master:
"audio service: set dock use on mediaserver restart
Restore forced usage of dock audio for media according to
current setting when media server restarts."
Bug 7485250.
Change-Id: Ie67b80ede1ed92d223dd96de83c1beb985dfba06
http://www.androidpolice.com/2013/02/12/developer-changelog-heres-whats-new-in-android-4-2-2-jdq39/

Nice, my sister's phone was affected by this. I saw her over the weekend and disabled Google Music, supposedly doing that or fixing broken mp3 files (she had none) would fix it but she didn't stay long enough for me to verify.
Sent from my Nexus 4 using xda premium

Let's fix up CM10.1 (bugs + discussion)

Again: No chitchat, no "thank you" posts, no non-technical questions, no bug reports without logcats.
As the other CM10.1 threads usually are overrun by users let's try to make use of the new section and create a new bug thread in here.
Bug reports including a clear description and a logcat are welcome, every offtopic post will get deleted. Simple as that :fingers-crossed:
This thread can get used for discussion of these bugs as well - as long as it's closely development focused (e.g. "based on the logcat the problem is in package xyz, here's my idea how to fix it").
We have created a github organization where we'll push the fixes (and commit them to Gerrit if @aremcee is still interested at maintaining the P990 ).
https://github.com/p990-dev
If you want to help just send a pull request (or PM me about getting full access).
There are dedicated branches for the old bootloader ("cm10.1", following CM) and new bootloader ("cm10.1-newbl").
This will hopefully make it easier for devs to support both bootloaders.
Again, pull requests are always welcome.
Please don't discuss gapps related bugs (keyboard closing, gtalk video not working etc.) in here, there's a dedicated thread about non-neon gapps.

1st update:
I digged into the Wifi Hotspot issue.
One reason it doesn't work seems to be that cyanogen reverted a P990 specific patch in the netd package for merging Android 4.2 sources.
Link: https://github.com/CyanogenMod/android_system_netd/commit/d2fe72845348bb1c9e67d2cf3c648e68a93be05f
We need to bring that back. But the structure of the SoftapController.cpp changed substantially, I (or whoever beats me to it) need to look into it closer to determine who to apply the custom patch with the new format.
Additionally I just committed the bootanimation fix:
https://github.com/p990-dev/android...mmit/e298d5c00afb1eb057f1599dd8a71ba677c3c6ca

HI tonyp, another bug is "in-call" mic muting. We can't mute the mic when in call, even when muted, the voice goes through. It's present in CM 10 as well as 10.1. Secondly, I found a temporary solution for Bluetooth A2DP accelerated streaming, keep your Bluetooth turned on and reboot the phone. When the phone connect immediately after booting, the streaming works normal. However when you disconnect subsequently and try to connect again, the music streaming will be accelerated again

About bluetooth, just found a similar issue reported on the HTC One X forums (http://forum.xda-developers.com/showpost.php?p=38647415&postcount=11481). Similar as in same log output, probably not in the result. But both our logs and his log show that there's a buffer overload that after a few starts exploding (our log follows)
Code:
...
03-07 19:54:21.230 W/bt-btif ( 834): btif_media_aa_prep_2_send congestion buf count 25
03-07 19:54:21.230 W/bt-btif ( 834): btif_media_aa_prep_2_send congestion buf count 24
03-07 19:54:21.230 E/GKI_LINUX( 834): ##### ERROR : timer_thread: tick delayed > 5 slots (-547249208,-50000000) -- cpu overload ? #####
03-07 19:54:21.230 E/GKI_LINUX( 834): ##### ERROR : timer_thread: tick delayed > 5 slots (-538364208,-50000000) -- cpu overload ? #####
03-07 19:54:21.230 E/GKI_LINUX( 834): ##### ERROR : timer_thread: tick delayed > 5 slots (-529468208,-50000000) -- cpu overload ? #####
03-07 19:54:21.230 W/bt-btif ( 834): btif_media_aa_prep_2_send congestion buf count 25
03-07 19:54:21.230 E/GKI_LINUX( 834): ##### ERROR : timer_thread: tick delayed > 5 slots (-520578208,-50000000) -- cpu overload ? #####
03-07 19:54:21.230 W/bt-btif ( 834): btif_media_aa_prep_2_send congestion buf count 24
03-07 19:54:21.240 E/GKI_LINUX( 834): ##### ERROR : timer_thread: tick delayed > 5 slots (-511690208,-50000000) -- cpu overload ? #####
03-07 19:54:21.240 W/bt-btif ( 834): btif_media_aa_prep_2_send congestion buf count 25
03-07 19:54:21.240 E/GKI_LINUX( 834): ##### ERROR : timer_thread: tick delayed > 5 slots (-502803208,-50000000) -- cpu overload ? #####
03-07 19:54:21.240 W/bt-btif ( 834): btif_media_aa_prep_2_send congestion buf count 24
...
Of course this leads to faster / slower output (in any case inconsistent). Now, the interesting report from that guy on the One X forum is that bt works fine when wifi is off, and doesn't when it's in COEX mode. Anyone that is able to reproduce the problem, please, can you log an a2dp streaming session with wifi on and one with wifi off ? I need to see if there are different outputs and i'm not on 10.1 at the moment. Probably later today or in the weekend i'll setup dual boot so i can test first hand.

Pengus, I cam confirm that BT without wifi works the same way. I pair my phone for music streaming in my car and it's the same accelerated streaming.

tonyp said:
As the other CM10.1 threads usually are overrun by users let's try to make use of the new section and create a new bug thread in here.
[*]HDMI orientation broken.
The problem is: the GB libnvdispmgr_d.so blob contained a method NvDispMgrAutoOrientation() to change the orientation.
The ICS binary doesn't have that anymore, and pengus and I couldn't figure out yet how to achive the rotation.
(and no, using the old blob won't work).[/LIST]
Please don't discuss gapps related bugs (keyboard closing, gtalk video not working etc.) in here, that'll happen in a dedicated thread.
Click to expand...
Click to collapse
About the hdmi this is also an issue on the P920 what i think lg did here was set the natural orientation in surface flinger to landscape 90 then countered it to 0 when using auto sensor while on cm10+ its @ 0 the hdmi output only reads the default orientation

defcomg said:
About the hdmi this is also an issue on the P920 what i think lg did here was set the natural orientation in surface flinger to landscape 90 then countered it to 0 when using auto sensor while on cm10+ its @ 0 the hdmi output only reads the default orientation
Click to expand...
Click to collapse
Something like that. I managed to have portrait hdmi work correctly changing only a bit of rom code in surface flinger, but the rotation to full landscape mode is achievable only using private methods from the blobs or, as i'm attempting to do, by hijacking the hdmi output and sensor orientation directly in the kernel at the framebuffer level.

pengus77 said:
Something like that. I managed to have portrait hdmi work correctly changing only a bit of rom code in surface flinger, but the rotation to full landscape mode is achievable only using private methods from the blobs or, as i'm attempting to do, by hijacking the hdmi output and sensor orientation directly in the kernel at the framebuffer level.
Click to expand...
Click to collapse
from my understanding its surface flinger -> hwc -> framebuffer
in my case the current output is 648x1080 if i were to make changes @ kernel level would it not result in 1080x648 not 1920x1080? do you guys use ida pro to check lib exports?

defcomg said:
from my understanding its surface flinger -> hwc -> framebuffer
in my case the current output is 648x1080 if i were to make changes @ kernel level would it not result in 1080x648 not 1920x1080? do you guys use ida pro to check lib exports?
Click to expand...
Click to collapse
I'm waiting to get my hands on the hex-ray arm decompiler... soon
Anyway this is the base init of the hdmi fb in kernel world
Code:
static struct tegra_fb_data star_hdmi_fb_data = {
#ifdef CONFIG_MACH_STAR
.win = 0,
.xres = 1366,
.yres = 768,
.bits_per_pixel = 16,
#else
.win = 0,
.xres = 800,
.yres = 480,
.bits_per_pixel = 32,
#endif
.flags = TEGRA_FB_FLIP_ON_PROBE,
};
In fact on boot it's correctly set, then it rotates when surfaceflibger/hwc takes control and never get back to the right mode.
Moreover in the drivers/video/tegra/dc/hdmi.c source file we can see that both 720p and 1080p resolutions are supported by the driver, together with 480p and 576p modes.
As soon as i'll get hex-rays i'll decompile the ics surfaceflinger lib and try to see what externals it calls for panel setup / rotation. I guess it'll happen somewhere next week.

Guys please do not push this thread without reason - so no "thank you" posts, no "good luck" posts and stuff like that.
Each post in here should have a valid reason (read: should be development related).
Read the instructions of the developer discussion section first.
Thank you

pengus77 said:
I'm waiting to get my hands on the hex-ray arm decompiler... soon
Anyway this is the base init of the hdmi fb in kernel world
Code:
static struct tegra_fb_data star_hdmi_fb_data = {
#ifdef CONFIG_MACH_STAR
.win = 0,
.xres = 1366,
.yres = 768,
.bits_per_pixel = 16,
#else
.win = 0,
.xres = 800,
.yres = 480,
.bits_per_pixel = 32,
#endif
.flags = TEGRA_FB_FLIP_ON_PROBE,
};
In fact on boot it's correctly set, then it rotates when surfaceflibger/hwc takes control and never get back to the right mode.
Moreover in the drivers/video/tegra/dc/hdmi.c source file we can see that both 720p and 1080p resolutions are supported by the driver, together with 480p and 576p modes.
As soon as i'll get hex-rays i'll decompile the ics surfaceflinger lib and try to see what externals it calls for panel setup / rotation. I guess it'll happen somewhere next week.
Click to expand...
Click to collapse
Further investigation into surfaceFlinger from ics from 2x + p920
Shows ics had this
Code:
.text:00021880 loc_21880 ; CODE XREF: android::SurfaceFlinger::setOrientation(int,int,uint)+24j
.text:00021880 MOVS R1, #1
.text:00021882 STRB.W R7, [R4,#0x6D]
.text:00021886 STRB.W R5, [R4,#0x6C]
.text:0002188A MOV R0, R4
.text:0002188C BL _ZN7android14SurfaceFlinger19setTransactionFlagsEj ; android::SurfaceFlinger::setTransactionFlags(uint)
.text:00021890 ADD.W R0, R4, #0x74 ; cond
.text:00021894 MOV R1, R6 ; mutex
.text:00021896 BLX pthread_cond_wait
.text:0002189A
.text:0002189A loc_2189A ; CODE XREF: android::SurfaceFlinger::setOrientation(int,int,uint)+2Aj
.text:0002189A ; android::SurfaceFlinger::setOrientation(int,int,uint)+64j
.text:0002189A MOV R0, R6 ; mutex
.text:0002189C BLX pthread_mutex_unlock
.text:000218A0
.text:000218A0 loc_218A0 ; CODE XREF: android::SurfaceFlinger::setOrientation(int,int,uint)+12j
.text:000218A0 MOV R0, R5
.text:000218A2 POP.W {R4-R8,PC}
.text:000218A6 ; ---------------------------------------------------------------------------
.text:000218A6
.text:000218A6 loc_218A6 ; CODE XREF: android::SurfaceFlinger::setOrientation(int,int,uint)+Cj
.text:000218A6 ADD.W R6, R0, #0x54
.text:000218AA MOV R0, R6 ; mutex
.text:000218AC BLX pthread_mutex_lock
.text:000218B0 LDRB.W R0, [R4,#0x6C]
.text:000218B4 CMP R0, R5
.text:000218B6 BNE loc_21868
.text:000218B8 B loc_2189A
.text:000218B8 ; End of function android::SurfaceFlinger::setOrientation(int,int,uint)
setOrientation(int,int,uint)
public static native void setOrientation(int display, int orientation, int flags);
think they excluded the method for hdmi from being called from the framework but just ran it from with in the lib
all they would have needed was the orientation value coming from display 0x0 and sent it to display 0x1 ie hdmi
jellybean is using nativeSetDisplayOrientation(IIII)V with the addition of parameter "externalRotation"
by the way getExternalRotation in Display.java is set to 0x0 i don't if CM10 CM10.1 etc knows what todo with "externalRotation" on our devices

Could someone on the newbl who has problems with bluetooth fast-forwarding-sound please try this build:
http://tonyp.hopto.org/temp/cm-10.1-20130311-UNOFFICIAL-p990.zip
My headset doesn't have any problems whatsoever - neither with official CM sources nor with this build, so I need to wait for testers.
Attach a kernel log + logcat as well please.
Oh and of course one of the most annoying bugs:
After unlocking the brightness often gets reset to a way too low value.
Logcat and kernel log don't show any error.
arcee already tried to fix it some time ago (see here) but this didn't fix it fully.
I guess we can workaround it in here:
https://github.com/CyanogenMod/lge-kernel-star/blob/cm-10.1/drivers/video/backlight/aat2870.c

tonyp said:
Could someone on the newbl who has problems with bluetooth fast-forwarding-sound please try this build:
http://tonyp.hopto.org/temp/cm-10.1-20130311-UNOFFICIAL-p990.zip
My headset doesn't have any problems whatsoever - neither with official CM sources nor with this build, so I need to wait for testers.
Attach a kernel log + logcat as well please.
Click to expand...
Click to collapse
Got this bug immideatly with this rom.
dmesg: http://pastebin.com/F0rTb6fR
logcat: http://pastebin.com/08h2bJBW
BT headset: Jabra BT3030

Here is mine. Hope it help.

Does the provided logs help a bit?
Are they sufficient or do you need more?

chp2 said:
Does the provided logs help a bit?
Are they sufficient or do you need more?
Click to expand...
Click to collapse
I finally compiled and flashed a clean 10.1 on my phone. I'm currently working on fixing both bluetooth media and the low I/O. What i found out so far:
- I/O is perfectly fine on ext4 filesystems (system / data / cache) but slow to a crawl on the sdcards (internal and external both). This is most probably a rom-related problem because testing the speed from a shell results in perfectly fine speeds. I'm looking into a fix.
- Bluetooth media is a mess. We're not the only ones facing this problem and it's not related to CM. I've found on google references to the same error on both CM and AOSP. I'm starting to think this one will be messy to fix and i'm following closely the AOSP git activity related to bt and audio.

pengus77 said:
I finally compiled and flashed a clean 10.1 on my phone. I'm currently working on fixing both bluetooth media and the low I/O.....
Click to expand...
Click to collapse
Yeepeee....
Pingus, I have no doubt you'll find the bugs.
(you're the best hehe)
Question : is it possible to use JB 4.1.2 BT subroutines here?

chp2 said:
Yeepeee....
Pingus, I have no doubt you'll find the bugs.
(you're the best hehe)
Question : is it possible to use JB 4.1.2 BT subroutines here?
Click to expand...
Click to collapse
Google changed from bluez to bluedroid in Android 4.2. It would be possible to revert that but it would be extremely messy and is only the last resort.
Sent from my LG-P990 using xda app-developers app

tonyp said:
Google changed from bluez to bluedroid in Android 4.2. It would be possible to revert that but it would be extremely messy and is only the last resort.
Sent from my LG-P990 using xda app-developers app
Click to expand...
Click to collapse
I understand that you don't want to revert bluedroid to Bluez but I found this when searching on Google where someone has already tried to do so. I'm not a dev so don't know if it was successful.

darkcastleking said:
I understand that you don't want to revert bluedroid to Bluez but I found this when searching on Google where someone has already tried to do so. I'm not a dev so don't know if it was successful.
Click to expand...
Click to collapse
Thank you very much for this, I will check out these instructions on Monday/Tuesday and do another testbuild!
Edit: Oh no, had a quick look, as you can see in the activity stream he deleted a couple repos in january which are linked in the manifest.
Additionally I'll try to revert the Wifi Hotspot changes. It would be better to write a new Interface for the Wifi Hotspot, but I don't really know how to do so.
Both approaches can't be submitted to Gerrit unfortunately, but as long as it works it would be nice.
Hopefully arcee will gain interest into the 2x again some day - I'm pretty sure he can easily fix that stuff, as he knows the Android Source and overall background really well.

[ROM] [4.4.4] [p3110] [unofficial] CM-11.0 for Galaxy Tab 2

CyanogenMod 11.0 for Galaxy Tab 2 P3110.
P3110: cm-11-20210110-NIGHTLY-p3110.zip
Security Patch Level: January 2021
Note: See thread for full changelogs
Recommended Gapps: gapps-base-arm-4.4.4-20170902-1-signed.zip
ClockworkMod Recovery v6.0.5.1: cm-11-20190309-NIGHTLY-p3110-recovery-signed.zip
Custom bootanimation: cm11-600x600-bootanimation-alt-signed.zip
Local Manifest: https://github.com/syphyr/cm_build_scripts/blob/master/local_manifests/local_manifests_cm-11.xml

THANKS!
I have exceeded the 16 "THANKS" limit for today, but I must thank you.
I am especially thankful for this, that after the end of the CyanogenMod team activity, you did not give up your device, which you devoted much of your time to.
Big, big thanks for long term support (LTS) for P3110.

ze7zez said:
I have exceeded the 16 "THANKS" limit for today, but I must thank you.
I am especially thankful for this, that after the end of the CyanogenMod team activity, you did not give up your device, which you devoted much of your time to.
Big, big thanks for long term support (LTS) for P3110.
Click to expand...
Click to collapse
Hmmmmmmm................. I need to try out this ROM.

Help @Deltadroid!
The Terminal Emulator has the option "Term Here".
Unfortunately, it does not work in Total Commander.
Instead of opening the selected directory, it appears at the prompt
Code:
1, 100R
and the opening directory is always "/".
Changing the font size to 20 results in opening a window with:
Code:
0; 50R
Something causes that Total Commader does not read the Terminal Emulator operation parameters correctly.
How to diagnose it?

ze7zez said:
Help @Deltadroid!
The Terminal Emulator has the option "Term Here".
Unfortunately, it does not work in Total Commander.
Instead of opening the selected directory, it appears at the prompt
Code:
1, 100R
and the opening directory is always "/".
Changing the font size to 20 results in opening a window with:
Code:
0; 50R
Something causes that Total Commader does not read the Terminal Emulator operation parameters correctly.
How to diagnose it?
Click to expand...
Click to collapse
Unfortunately, the terminal emulator in cm11 is closed source and that apk is just pulled in by the author of the app.

https://github.com/jackpal/Android-Terminal-Emulator/commits/master
But right, gets pulled in prebuilt and isn't compiled from source

I wonder, however, why the "Terminal Emulator" widget
and sharing the "Term Here" works well in 4.4.4 OMNI and 4.4.4 Slim (and in every 6.0.1 ROM),
and it does not work properly in CM 11 and Lineage 11 (also on other devices).
I'm sorry, but I do not want to dominate the topic only with this issue.
However, only here I have a unique opportunity to discuss the matter with two very experienced developers of one device.

ze7zez said:
I wonder, however, why the "Terminal Emulator" widget
and sharing the "Term Here" works well in 4.4.4 OMNI and 4.4.4 Slim (and in every 6.0.1 ROM),
and it does not work properly in CM 11 and Lineage 11 (also on other devices).
I'm sorry, but I do not want to dominate the topic only with this issue.
However, only here I have a unique opportunity to discuss the matter with two very experienced developers of one device.
Click to expand...
Click to collapse
Maybe you could try pulling the terminal emulator apk from omni 4.4.4 and see if it fixes the problem with cm-11.0.

Deltadroid said:
Maybe you could try pulling the terminal emulator apk from omni 4.4.4 and see if it fixes the problem with cm-11.0.
Click to expand...
Click to collapse
As mentioned above @Android-Andi, Term.apk, which is in CM/Lineage 11, is not compiled from sources. In OMNI and Slim, I install Terminal Emulator_1.0.70.apk, which is binary identical to Term.apk. (md5sum 801006944755b591cd214b1fef685237).
Even if I manually remove from CM/Lineage 11 Term.apk from the system and install it as a regular application, the problem still remains.
There must be something in CM/Lineage 11, which makes it difficult to read the Terminal parameters correctly.
However, I do not know how to investigate it.

Sir could you include Agni kernel for the tab 2 p3110 as well?

ze7zez said:
As mentioned above @Android-Andi, Term.apk, which is in CM/Lineage 11, is not compiled from sources. In OMNI and Slim, I install Terminal Emulator_1.0.70.apk, which is binary identical to Term.apk. (md5sum 801006944755b591cd214b1fef685237).
Even if I manually remove from CM/Lineage 11 Term.apk from the system and install it as a regular application, the problem still remains.
There must be something in CM/Lineage 11, which makes it difficult to read the Terminal parameters correctly.
However, I do not know how to investigate it.
Click to expand...
Click to collapse
Term.apk also uses these two proprietary libraries:
libjackpal-androidterm5.so
libjackpal-termexec2.so
Are these two libraries also the same b/n Omni and CM?

Deltadroid said:
Term.apk also uses these two proprietary libraries:
libjackpal-androidterm5.so
libjackpal-termexec2.so
Are these two libraries also the same b/n Omni and CM?
Click to expand...
Click to collapse
Exactly (md5sum) these two files contain
Terminal Emulator_1.0.70.apk = Term.apk.
In CM/Lineage 11 they are placed in /system/lib
and in OMNI and Slim they are installed there by apk.

Security Patch Level: February 2018
cm-11-20180213-NIGHTLY-p3110.zip
Changelog:
Code:
android
4710919 (4 weeks ago) track Android 8.0.1 system/ca-certificates (jumoog)
build
52b6018 (49 seconds ago) Bump Security Patch Level to 2018-02-01 (Tim Schumacher)
d50b945 (4 days ago) Bump Security Patch Level to 2018-01-01 (Tim Schumacher)
external/aac
674cab0 (4 weeks ago) DO NOT MERGE Prevent out of bound memory access in GetInvInt (Jean-Michel Trivi)
49d60cc (4 weeks ago) Fix out of bound memory access in lppTransposer (Jean-Michel Trivi)
external/libvpx
95ef3b3 (4 weeks ago) DO NOT MERGE | libvpx: Fix OOB caused by odd frame width. (Jerome Jiang)
external/sonivox
257ea97 (2 minutes ago) Fix memory leak (Marco Nelissen)
4a4bd68 (2 minutes ago) Add recursion limit to XMF_ReadNode (Robert Shih)
228b666 (2 weeks ago) Sonivox: sanity check headerLength in XMF_ReadNode. (Wei Jia)
frameworks/av
241a2f7 (3 minutes ago) httplive: check for malformed EXT-X-STREAM-INF (Robert Shih)
cc8b9f5 (3 minutes ago) Apply input buffer validation also to AVC and MPEG4 encoders (Dongwon Kang)
e196692 (4 weeks ago) stagefright: MP4Extractor: allow 10% overhead on default sample size (Lajos Molnar)
0303b87 (4 weeks ago) Add EFFECT_CMD_SET_PARAM parameter checking to Preset Reverb (Mikhail Naganov)
8bb2073 (4 weeks ago) Fix edge case when applying id3 unsynchronization (Marco Nelissen)
61f5d18 (6 weeks ago) OMXNodeInstance: use a lock around OMX::freeNode (Lajos Molnar)
frameworks/base
14848f6 (4 days ago) Fix ClipboardService device lock check for cross profile (Siyamed Sinir)
cb06a19 (4 days ago) Prevent getting data from Clipboard if device is locked (Siyamed Sinir)
c0bd191 (4 days ago) DO NOT MERGE Backporting potential usb tapjacking precaution. (Beverly)
b1631e0 (4 days ago) Adjust Uri host parsing to use last instead of first @. (Adam Vartanian)
libcore
f8f5bf2 (4 weeks ago) Move CA certificates to a separate project (Kenny Root)
system/core
70bd46d (4 weeks ago) libnetutil: Check dhcp respose packet length (tintin)
system/media
0b64f2b (4 weeks ago) Camera metadata: Check source metadata size (Emilian Peev)

cm-11-20180216-NIGHTLY-p3110.zip
Code:
kernel/samsung/espresso10
15259cf (14 minutes ago) dm: fix race between dm_get_from_kobject() and __dm_destroy() (Hou Tao)
4a122a9 (14 minutes ago) isofs: fix timestamps beyond 2027 (Arnd Bergmann)
d271924 (14 minutes ago) media: omap_vout: Fix a possible null pointer dereference in omap_vout_open() (Markus Elfring)
2002a7c (14 minutes ago) ALSA: seq: Make ioctls race-free (Takashi Iwai)
ffb1f57 (2 days ago) netfilter: xt_TCPMSS: add more sanity tests on tcph->doff (Eric Dumazet)
3e24e4a (2 days ago) netfilter: xt_TCPMSS: correct return value in tcpmss_mangle_packet (Phil Oester)
4ad9d88 (2 days ago) netfilter: xt_TCPMSS: fix handling of malformed TCP header and options (Pablo Neira Ayuso)
1f4244d (2 days ago) netfilter: xt_TCPMSS: Fix missing fragmentation handling (Phil Oester)
8250b75 (2 days ago) netfilter: xt_TCPOPTSTRIP: don't use tcp_hdr() (Pablo Neira Ayuso)
e9fe7f6 (2 days ago) netfilter: xt_TCPOPTSTRIP: fix possible mangling beyond packet boundary (Pablo Neira Ayuso)
e4ee144 (2 days ago) ALSA: usb-audio: Add sanity checks in v2 clock parsers (Takashi Iwai)
f214844 (2 days ago) ALSA: usb-audio: Fix potential out-of-bound access at parsing SU (Takashi Iwai)
ab46f0e (2 days ago) ALSA: usb-audio: Add sanity checks to FE parser (Takashi Iwai)
4ebcf54 (2 days ago) ALSA: timer: Remove kernel warning at compat ioctl error paths (Takashi Iwai)
ad7c194 (2 days ago) l2tp: ensure sessions are freed after their PPPOL2TP socket (Guillaume Nault)
f11e505 (2 days ago) l2tp: push all ppp pseudowire shutdown through .release handler (Tom Parkin)
7d6d741 (2 days ago) l2tp: purge session reorder queue on delete (Tom Parkin)
6ae0773 (2 days ago) l2tp: add session reorder queue purge function to core (Tom Parkin)
080ee28 (2 days ago) rtc: set the alarm to the next expiring timer (Alexandre Belloni)
6b77684 (2 days ago) rtc: interface: ignore expired timers when enqueuing new timers (Colin Ian King)
74f3988 (3 days ago) ALSA: timer: Fix missing queue indices reset at SNDRV_TIMER_IOCTL_SELECT (Takashi Iwai)
22927bd (3 days ago) ALSA: timer: Fix race between read and ioctl (Takashi Iwai)
e0c7a36 (3 days ago) packet: fix tp_reserve race in packet_set_ring (Willem de Bruijn)
28e3b26 (3 days ago) timerfd: Protect the might cancel mechanism proper (Thomas Gleixner)
5a80ec1 (3 days ago) mqueue: fix a use-after-free in sys_mq_notify() (Cong Wang)
1ff61d3 (3 days ago) tcp: fix wraparound issue in tcp_lp (Eric Dumazet)
e6b6a27 (3 days ago) tcp: eliminate negative reordering in tcp_clean_rtx_queue (Soheil Hassas Yeganeh)
e3e6f6e (3 days ago) tcp: avoid fragmenting peculiar skbs in SACK (Yuchung Cheng)
0086559 (3 days ago) tcp: fix tcp_match_skb_to_sack() for unaligned SACK at end of an skb (Neal Cardwell)
9168698 (3 days ago) net: ping: do not abuse udp_poll() (Eric Dumazet)
0dae152 (3 days ago) net: add kfree_skb_list() (Ben Hutchings)
5d686db (3 days ago) selinux: fix double free in selinux_parse_opts_str() (Paul Moore)
559eb5d (3 days ago) fuse: initialize the flock flag in fuse_file on allocation (Mateusz Jurczyk)
42b6ca1 (3 days ago) KEYS: don't let add_key() update an uninstantiated key (David Howells)
bbd3f94 (3 days ago) ALSA: seq: Fix use-after-free at creating a port (Takashi Iwai)
9b4bd7e (3 days ago) KEYS: add missing permission check for request_key() destination (Eric Biggers)
ec65219 (3 days ago) KEYS: trusted: sanitize all key material (Eric Biggers)
45d39a1 (3 days ago) ALSA: seq: Fix nested rwsem annotation for lockdep splat (Takashi Iwai)
bd2f0f1 (3 days ago) ALSA: timer: Add missing mutex lock for compat ioctls (Takashi Iwai)
2223497 (3 days ago) crypto: shash - Fix zero-length shash ahash digest crash (Herbert Xu)
a5b73bf (3 days ago) ipsec: Fix aborted xfrm policy dump crash (Ben Hutchings)
181baa0 (3 days ago) ext4: fix fencepost in s_first_meta_bg validation (Theodore Ts'o)
968dd80 (3 days ago) packet: only test po->has_vnet_hdr once in packet_snd (Willem de Bruijn)
0c4a2df (3 days ago) KEYS: prevent creating a different user's keyrings (Eric Biggers)
c6dbe8d (3 days ago) KEYS: fix key refcount leak in keyctl_read_key() (Eric Biggers)
7602215 (3 days ago) KEYS: fix key refcount leak in keyctl_assume_authority() (Eric Biggers)
3a12b9a (3 days ago) KEYS: don't revoke uninstantiated key in request_key_auth_new() (Eric Biggers)
c55899e (3 days ago) KEYS: fix cred refcount leak in request_key_auth_new() (Eric Biggers)
7fe8a04 (3 days ago) Bluetooth: bnep: bnep_add_connection() should verify that it's dealing with l2cap socket (Al Viro)
30e879b (3 days ago) Bluetooth: cmtp: cmtp_add_connection() should verify that it's dealing with l2cap socket (Al Viro)
18204c6 (3 days ago) Bluetooth: hidp: verify l2cap sockets (David Herrmann)

Is this OK to flash on the 10 inch tablets as well? Since it isn't in the unified section figured I better ask

twfs said:
Is this OK to flash on the 10 inch tablets as well? Since it isn't in the unified section figured I better ask
Click to expand...
Click to collapse
I would say yes. But I don't know.

twfs said:
Is this OK to flash on the 10 inch tablets as well? Since it isn't in the unified section figured I better ask
Click to expand...
Click to collapse
no, its only for p3110
Sent from my PRA-LX1 using XDA Labs

Deltadroid said:
CyanogenMod 11.0 for Galaxy Tab 2 P3110.
Local Manifest: https://github.com/syphyr/cm_build_scripts/blob/master/local_manifests/local_manifests_cm-11.xml
Security Patch Level: February 2018
cm-11-20180216-NIGHTLY-p3110.zip
Note: See thread for changelogs
Click to expand...
Click to collapse
@Deltadroid
I am running your latest build. This ROM is sooooooooooooooo fast and awesome. For anyone that decides to leave stock, and looking for a ROM, I would recommend giving this ROM a try, to get their device away from TouchWiz s***. :laugh:
Thanks for keeping our Galaxy Tab 2s alive!

Deltadroid said:
CyanogenMod 11.0 for Galaxy Tab 2 P3110.
Local Manifest: https://github.com/syphyr/cm_build_scripts/blob/master/local_manifests/local_manifests_cm-11.xml
Security Patch Level: February 2018
cm-11-20180216-NIGHTLY-p3110.zip
Note: See thread for changelogs
Click to expand...
Click to collapse
@Deltadroid, any chance of a new build this month?

Security patch level: March 1, 2018
w/ additional Blueborne security fixes
cm-11-20180312-NIGHTLY-p3110.zip
Code:
build
8c7e7df (23 hours ago) ASB March 2018, update security string to 2018-03-01 (MSe1969)
external/bluetooth/bluedroid
d68511b (7 minutes ago) Bluedroid: Use PAN_BUF_SIZE (syphyr)
741f2dd (7 minutes ago) BNEP: Check received frame type (Myles Watson)
0a8349f (8 minutes ago) Remove memory reference to invalid mem in error log (Stanley Tng)
1ba8e0a (8 minutes ago) SDP: Include the offset in sdp_disc_server_rsp (Myles Watson)
5168dd8 (8 minutes ago) SDP: Pass the bounds to process_service_*_rsp (Myles Watson)
4925920 (8 minutes ago) Fix unused parameter warnings in static functions by changing prototype (Mike J. Chen)
e544d7f (9 minutes ago) Fix unexpected behavior in reading BNEP packets (Hansong Zhang)
383519f (9 minutes ago) PAN: Fix Use-after-free in bta_pan_data_buf_ind_cback (Myles Watson)
e058fda (9 minutes ago) AVRCP: Check the number of text attributes requested (Ajay Panicker)
f950fae (9 minutes ago) Fix unexpected behavior in SDP (Hansong Zhang)
ab466dd (10 minutes ago) Add missing continuation offset check for SDP continuation requests (Pavlin Radoslavov)
3d4f677 (10 minutes ago) Disable PAN Reverse Tethering when connection originated by the Remote (Pavlin Radoslavov)
790eb29 (10 minutes ago) Add missing extension length check while parsing BNEP control packets (Pavlin Radoslavov)
77779ae (10 minutes ago) Add missing packet length checks while parsing BNEP control packets (Pavlin Radoslavov)
5ebe91c (11 minutes ago) Add a missing check for PAN buffer size before copying data (Pavlin Radoslavov)
0e8137a (11 minutes ago) Free p_pending_data from tBNEP_CONN to avoid potential memory leaks (Pavlin Radoslavov)
2b92160 (11 minutes ago) Allocate buffers of the right size when BT_HDR is included (Pavlin Radoslavov)
frameworks/av
0b01355 (2 days ago) AACExtractor: check bounds during seek (Robert Shih)

[ROM][cepheus][A13] iodéOS = LineageOS 20 + MicroG + adblocker [04/04/2023]

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Introduction
iodéOS is a privacy-focused operating system powered by LineageOS and based on the Android mobile platform. iodéOS aims at protecting the user's privacy with a built-in adblocker and by freeing the smartphone from snitches.
The objectives in the conception of this ROM are threefold:
To keep the stability and security level of LineageOS, by minimizing the modifications made to the system. Apart the system modifications required by the adblocker, we mainly only added a few useful options commonly found in other custom ROMs, made some cosmetic changes, modified a few default settings to prevent data leaks to Google servers.
To ease a quick adoption of this ROM by new users. We especially target users that are concerned by the protection of their privacy, but are not reluctant to still use inquisitive apps like Google ones. We thus included MicroG as well as a coherent set of default apps, and simplified the initial setup of the system. Particularly, an initialization of MicroG has been made with GCM notifications allowed by default, a privacy-friendly network location provider (DéjàVu) pre-selected, as well as Nominatim Geocoder.
To provide a new and powerful way of blocking ads, malwares, data leaks of all kinds to many intrusive servers. We are developing an analyzer, tightly integrated into the system, that captures all DNS requests and network traffic, as well as a user interface (the iodé app). Compared to some other well-known adblockers, this has the advantages of:
Avoiding to lock the VPN for that use. You can even use another adblocker that uses VPN technology alongside our blocker.
Being independent of the kind of DNS server used by the system or set by an independent app: classical DNS on UDP port 53 or any other one, DNS over TLS (DoT), DNS over HTTPS (DoH), ..., as we capture the DNS requests before they are transmitted to the system function that emits the DNS request. What we do not support, is DoH when it is natively built into applications, i.e. when an app communicates directly with a DoH server, without asking name resolution to the system. It would require to decrypt HTTPS packets between such an app and the DoH server, which may create a big security hole.
Precisely mapping DNS requests and network packets to the Android apps that emitted (or received) them.
Deciding which apps have a filtered network usage (by default, all apps), and which ones can communicate with blacklisted servers.
Since its first versions, we added many features to the iodé blocker: several levels of protection, fine-grained control over the hosts that should be blocked or authorized, displaying statistics on a map to see the quantity of data exchanged to which countries, clearing statistics... We are actively developing the blocker, and new functionalities will be regularly added.
Features
Changes in LineageOS to prevent data leaks:
Default DNS server: Google's DNS replaced by Quad9's 'unblocked' servers in all parts of the system.
A-GPS: patches to avoid leaking personnal information like IMSI to supl server.
Captive portal login: connectivitycheck.gstatic.com replaced by captiveportal.kuketz.de for connectivity check.
Dialer: Google default option replaced by OpenStreetMap for phone number lookup.
Pre-installed apps:
We included many useful default apps, but our choice cannot suit everyone; so we added the possibility to remove them. It can be done at the end of the phone setup, or at any time by going to Parameters -> Apps & Notifications -> Preinstalled apps.
MicroG core apps: GmsCore, GsfProxy, FakeStore.
NLP backends for MicroG : DejaVuNLPBackend (default), MozillaNLPBackend, AppleNLPBackend, RadioCellsNLPBackend, Nominatim Geocoder.
App stores : FDroid (with F-Droid Privileged Extension) and Aurora Store.
Browser: our own fork of Firefox (with Qwant as default search engine, many other ones added, telemetry disabled, parts of telemetry code removed) instead of Lineage’s default browser Jelly.
SMS: QKSMS instead of Lineage's default SMS app.
Email: p≡p (Pretty Easy Privacy).
Camera: our own fork of Open Camera, with a few tweaks.
Maps/navigation: Magic Earth GPS & Navigation (the only one free but not open source).
Keyboard: OpenBoard instead of AOSP keyboard.
PDF: Pdf Viewer Plus.
Personnal notes: Carnet.
{Ad/Malware/Data leak}-blocker: iodé.
News: to keep users informed about our developments, as well as a FAQ.
Meteo: Geometric Weather.
Pre-included FDroid repository:
The apps that we tweak or develop (microG services, the browser based on Firefox, the News app, Open Camera ...) are available through a repository that we included in FDroid (check the "Apps for iodéOS" category). For this purpose and to avoid name conflicts of some apps, we also had to make a few changes in FDroid.
Useful options from other custom ROMs:
Smart charging (disables charging when a given level is reached, to protect battery health).
Fingerprint vibration toggle.
Swipe down to clear all in recent apps (Android 10 only).
Installation Instructions
To download and flash our latest build, see https://gitlab.com/iode/ota.
You can also find here direct links to the latest builds.
Supported devices
Fairphone FP3/FP3+
Fairphone FP4
Google Pixel 3
Google Pixel 4
Google Pixel 5
Google Pixel 6
Google Pixel 6a
OnePlus 9
OnePlus 9 Pro
Samsung Galaxy A5/A7 2017 (a5j17lte/a7j17lte)
Samsung Galaxy S9/S9+ (starlte/star2lte)
Samsung Galaxy Note 9 (crownlte)
Samsung S10e/S10/S10+ (beyond{0,1,2}lte)
Samsung Note 10 (d1)
Samsung Note 10+ (d2s)
Sony Xperia XA2 (pioneer)
Sony Xperia XZ1 (poplar)
Sony Xperia XZ2 (akari)
Sony Xperia XZ3 (akatsuki)
Xiaomi Mi9 (cepheus)
Teracube 2e
Xiaomi Mi 10T 5G / Mi 10T Pro 5G
Xiaomi Mi 10 Lite 5G
Sources
iodéOS: https://gitlab.com/iode/os
LineageOS: https://github.com/lineageos
device tree: https://gitlab.com/iode/os/public/devices/xiaomi/device_xiaomi_cepheus
https://github.com/Demon000/device_xiaomi_sm8150-common
kernel:
(iodéOS 1.x) https://gitlab.com/iode/os/public/devices/xiaomi/kernel_xiaomi_sm8150
(iodéOS 3.x) https://github.com/crdroidandroid/android_kernel_xiaomi_cepheus
Bug Reporting
You can post a message in this thread or (preferred) open an issue here.
Credits
LineageOS is a free, community built, aftermarket firmware distribution of android, which is designed to increase performance and reliability over stock android for your device.
All the source code for LineageOS is available in the LineageOS Github repo. If you would like to contribute to LineageOS, please visit their Wiki for more details.
This ROM would be nothing without the tremendous work made on MicroG, and all the other open source apps that we included. We are very grateful to their authors.
Contributors
Direct contributors: @iodeOS, @vince31fr
Indirect contributors (too numerous to list): All the people that contributed to the device tree, to LineageOS, and to the included open source apps.
Sponsoring
You can help in the development of this ROM by paying us a coffee here: https://paypal.me/iodeOS.
Screenshots

Downloads : iodéOS
04/04/2023 (build 20230401):
Upgrade to iodéOS 4.1 based on Android 13 / LineageOS 20
Installation procedure: move to a fastboot script (read instructions: https://gitlab.com/iode/ota)
Blocker: improved use of blocking lists (sub-domains blocking)
FDroid: fixes an issue on apps update
LineageOS synchronized with March security patch included
All apps updated
Recovery bug: iodéOS v4 recovery on cepheus does not correctly format data. If you need to format data, you can (1) do it with TWRP, or (2) do it in bootloader with the commands:
fastboot format:ext4 userdata
fastboot format:ext4 cache
07/02/2023 (build 20230131):
Blocker:
Improved blocking settings. You can now choose 'Standard' blocking (ads, trackers, malwares, etc) or 'Reinforced' blocking (same objective but more extensive), and then select additional categories.
The 'Porn' category has been extended to a wider 'Sensitive content' one, that also includes fake news, gambling, drugs, piracy, torrent..., with mainly child protection in mind.
The 'Extreme' category has been removed, as it is now part of the reinforced blocking.
Improved blocking lists. We merge several acknowledged and up-to-date sources, and have diversified our sources to produce more complete lists. The standard list has however been reduced a bit, to avoid as much as possible interference with apps expected behavior.
Added a new network location provider: Local NLP Backend. It is an improved version of the DéjàVu NLP backend which was already available in iodéOS. Like DéjàVu, it builds a local database connecting localizations learned from other NLP backends and apps using GPS, and mobile antennas/Wifi; but also has an active mode (not preselected) that can trigger GPS requests. To configure it: Settings -> System -> microG -> Location modules
LineageOS synchronized with January security patch included
All apps updated
New devices support: Pixel 3, 6, 6a
16/12/2022 (build 20221215):
Blocker: added multiple selection in settings / domain customization. Long-press on a domain, select several domains or all, apply actions (block all, authorize all...)
PdfViewerPlus: improved security by updating core libraries
Network settings: added a switch to disable connectivity check (and thus captive portal detection)
LineageOS synchronized with December security patch included
All apps updated
New devices support: Pixel 4 & 5, OnePlus 9 & 9 Pro
24/11/2022 (build 20221121):
Improvements in the blocker user interface (iodé app)
LineageOS synced with September security patch included
All apps updated
17/10/2022 (build 20221014):
Blocker:
Network blockings following their type (Wifi, mobile data, VPN) added
Default blockings definition for new apps
Personnalized recipients management improved
iodé's app access restrictions by password added
Search filters added in report and map
Display theme selection
Automatic and 'real-time' refresh of the whole app
Performance and fluidity improvements of the app
LineageOS synced with September security patch included
All apps updated
27/07/2022 (build 20220726):
SafetyNet certification activated: allows many apps, notably banking ones, to fully work
Setup wizard: the push notifications configuration page now also activates SafetyNet (fine-grained control in Settings->System->microG)
OpenCamera: the 'Use alternative flash method' in photo settings is no more necessary and can be disabled, allowing flash optimization
News app: German translations
LineageOS synced with July security patch included
All apps updated
21/07/2022 (build 20220530):
Upgrade to Android 12 / Lineage 19.1. Beware: this upgrade needs a data format due to an incompatibility in the encryption method. It is thus not available as OTA, a manual flash is required
Setup Wizard: new page to configure push notifications through microG
Lockscreen settings: switch added to disable fingerprint unlock when screen is off
Improved German translations
Bug fixes and improvements
LineageOS synced with May security patch included
All apps updated
02/05/2022 (build 20220407):
News app reworked
Setup Wizard: new iodé introduction
iodé blocker: pull to refresh replaced by automatic refresh in report tab
Teracube 2e 2022 batch released, video playback in browser and video recording fixed
Music app : playlist crash fixed
Open Camera : crash when tapping thumbnail of a newly recorded video fixed, photos and videos now editable
LineageOS synced with March security patch
All apps updated
03/02/2022 (build 20220127):
New iodé blocker map feature
Build mode changed to 'user' (i.e. release) mode): more apps work out-of-the-box and more secure device, but more restrictive recovery
Camera app changed to Open Camera
Wireguard kernel module included
Dark bootanimation
January security patch
Preinstalled apps updated
Beware: Play store Magisk module broken
18/11/2021 (build 20211109):
LineageOS updated (November security patch)
Preinstalled apps updated
Iodé blocker: hosts can now be customized, either globally or by app
10/09/2021 (build 20210828):
LineageOS updated (August security patch)
Preinstalled apps updated
Backup app included: Seedvault
microG now uninstallable: Settings -> Apps & notifications -> Preinstalled apps
New default accent color (clear blue from iodé logo)
AI key now configurable (short press only, Settings -> System -> Buttons)
03/08/2021 (build 20210729):
Preinstalled apps UI reworked with the introduction of categories.
Dark theme in the iodé blocker UI (next improvement will be hosts customization).
p≡p (https://f-droid.org/fr/packages/security.pEp/) is now the defaut email client, and replaces lineageOS client which is no longer maintained.
Preinstalled apps updated to their latest version.
LineageOS updated (July security patch).
28/05/2021 (build 20210527):
Different protection levels in iodé's blocker added: in addition to the default standard blocklist, we added three lists (socials, porn, extreme) that can be activated globally or on a per-app basis (more information in the FAQ).
Geometric Weather app added.
Preinstalled apps selection at setup wizard added.
Preinstalled apps including microG updated to their latest version.
LineageOS updated (May security patch).
Updated kernel to 4.14.232
Merge CAF TAG LA.UM.8.1.r1-17100-sm8150.0
07/03/2021 (build 20210306):
Blocker UI improved: performance at startup, statistics display (with sortable columns), DNS stream
Preinstalled apps management (uninstall / reinstall) menu added (Settings -> Apps & Notifications -> Preinstalled apps)
Latest lineageOS sources synced
Default apps updated
Updated kernel to 4.14.221
Merge CAF TAG LA.UM.8.1.r1-16900-sm8150.0
22/01/2021 (build 20210119):
LineageOS sources synced
Prebuilt apps updated
Activated Camera APIv2 in Snap
Force auto-update of apps in FDroid to keep in sync with iodé apps. It can be disabled.
Updated kernel to latest stable (4.14.214)
Merge CAF tag LA.UM.8.1.r1-16600-sm8150.0
26/12/2020 (build 20201125):
Kernel completely remastered and updated to latest stable, 4.14.212. Due to problems with fod sometimes not working, conflicts between screen-off fod and dt2w, stability problems, I started a new kernel from scratch. Major drawback though: flash with fingerprint authentication is back. This is preferable to a half-functioning fod though
Fod now works without dt2w being set
Added Wifi Display (Miracast). Maybe some problems with sound: need user feedback
Added poweroff alarm
Device tree reworked
Vendor updated to 12.0.6.0
LineageOS sources synced
Prebuilt apps updated
02/12/2020 (build 20201127):
Kernel updated to latest stable: 4.14.209
Merged CAF tag LA.UM.8.1.r1-16200-sm8150.0
LineageOS sources synced
Prebuilt apps updated
New default wallpaper
Firefox browser renamed as iodé Browser and logo changed due to trademark restrictions
The iodé blocker can now be correctly coupled with a VPN
20/11/2020 (build 20201119):
Kernel updated to latest stable: 4.14.207
Made some internal changes to improve stability
iodé app (blocker): app switches replaced by shields around app icons, aggregated apps view in report, historical data deletion for each period by long press on an app line in report, black list updated
LineageOS sources synced
Prebuilt apps updated
Added a iodé category in FDroid, to quickly distribute the apps we customize. We had to fork FDroid for this purpose.
Magisk survival script working again: it is not needed anymore to reflash Magisk after an OTA
29/10/2020 (build 20201029):
Kernel updated to latest stable: 4.14.202
Merged CAF tag LA.UM.8.1.r1-16200-sm8150.0
Updated blobs to miui 12.0.5.0
Switched to QTI bluetooth stack
Built as much stuff as possible from sources.
Synced Lineage sources.
Added screen-off FOD (one glitch though: DT2W must be enabled to make it work - to be fixed).
Reworked auto-brightness levels.
Updated Microg to 0.2.13.203915 with commits up to 28/10, in particular Mapbox maps which now mostly work.
Replaced Qwant browser by Firefox, with Qwant set as default search engine and telemetry disabled by default.
05/08/2020 (build 20200805):
Synced LineageOS sources and device tree
microG updated to v0.2.11.202414 plus commits up to 05/08
AppleNLP backend working again
Prebuilt apps updated to their latest version
25/07/2020 (build 20200725):
Synced lineage (security patch r40) and device tree
Minor UI fixes and improvements in iodé adblocker
Updated blocklist
Updated preinstalled apps
Improved bootanimation
28/06/2020 (build 20200628): initial publicly available build of iodéOS for cepheus. It inherits the work previously published in this thread. NB: the default browser of LineageOS, Jelly, has been replaced by Qwant. For those who miss Jelly, you can install it from iodé FDroid repo (look at "Apps for iodé" in FDroid categories).
Downloads : add-ons
phonesky-magisk.zip : Magisk module for NanoDroid patched Play Store, for those who really need to get access to their paid apps that don't work with microG. This module can be generally be deactivated when you have installed and ran once the paid apps.
NB : you may have to wait a couple of hours after activating the module for being able to install paid apps.

I'll try soon.

Nice work, might try this soon.

vince31fr -- Can we dirty flash this new iodéOS ROM over your previous LineageOS 17.1 + MicroG (Unofficial) ROM?

dmahtani said:
vince31fr -- Can we dirty flash this new iodéOS ROM over your previous LineageOS 17.1 + MicroG (Unofficial) ROM?
Click to expand...
Click to collapse
Yes you can, but be careful, make a backup. There is no particular reason for a dirty flash to fail : the basis is the same, the ROM is signed with the same keys... The modifications made to the system for supporting the adblocker should not be harmless.
There's only one thing that may cause a problem, is that microg, as I told in the old thread, has been compiled with the mapbox option.
About microg, even with the mapbox option, many apps with integrated maps still do not work properly... But the development on microg is starting again, so we may expect some progress.
Maybe some users that tried dirty flash could tell if it worked?

Thanks -- I went ahead and dirty flashed this iodéOS ROM over your previous LineageOS 17.1 + MicroG (Unofficial) ROM and everything seems to be working fine.
vince31fr said:
Yes you can, but be careful, make a backup. There is no particular reason for a dirty flash to fail : the basis is the same, the ROM is signed with the same keys... The modifications made to the system for supporting the adblocker should not be harmless.
There's only one thing that may cause a problem, is that microg, as I told in the old thread, has been compiled with the mapbox option.
About microg, even with the mapbox option, many apps with integrated maps still do not work properly... But the development on microg is starting again, so we may expect some progress.
Maybe some users that tried dirty flash could tell if it worked?
Click to expand...
Click to collapse

Hi, for the record I'm antoine, I work with vincent on this project.
As mentioned in the OP, this adblocker is still in its infancy (we use it for months now and it seems robust), but there may still be bugs. We are actively developing it, and many more features will be added over the next months. We are open to receive bug reports, suggestions, comments of any kind...

I also installed your building out of curiosity, but I did not know how to recover my contacts and photos that are obviously on Google, is there any alternative to this ??

baggino said:
I also installed your building out of curiosity, but I did not know how to recover my contacts and photos that are obviously on Google, is there any alternative to this ??
Click to expand...
Click to collapse
You can export your contacts from google and import them in the Contacts app. Last time I used google photos, it was working, except synchronization. You can also export all your photos in an archive file.
Personally, I use a nextcloud account at infomaniak, not very expensive. I sync contacts, calendar, photos, ... If in the future I get a decent upload rate at home, I'll probably use nextcloud on a home server.
Leaving google has a price...

neat!
What a surprise that rom ! I'm going to attempt a migration from before your rom @vince31fr.

Bluetooth
I really like this ROM!
The only problem I've found so far is that I have problems with bluetooth stuttering.
When listening to music or podcast, the audio quality sometimes gets terrible, like when you walk away from your phone with your headset.

peking12 said:
I really like this ROM!
The only problem I've found so far is that I have problems with bluetooth stuttering.
When listening to music or podcast, the audio quality sometimes gets terrible, like when you walk away from your phone with your headset.
Click to expand...
Click to collapse
Thanks for the feedback !
We will look into this
---------- Post added at 10:37 AM ---------- Previous post was at 10:10 AM ----------
michal383 said:
I'll try soon.
Click to expand...
Click to collapse
Great !

iodeOS said:
Thanks for the feedback !
We will look into this
---------- Post added at 10:37 AM ---------- Previous post was at 10:10 AM ----------
Great !
Click to expand...
Click to collapse
When I changed Bluetooth audio codec to SBC in developer settings, the problem goes away. Does anybody know how I can make this change persistent?

peking12 said:
When I changed Bluetooth audio codec to SBC in developer settings, the problem goes away. Does anybody know how I can make this change persistent?
Click to expand...
Click to collapse
If you know which codec was used but does not work well (I read about problems with AAC but thought it was fixed), you can remove it by editing /vendor/build.prop, and remove -aac from the line
Code:
persist.vendor.qcom.bluetooth.a2dp_offload_cap=sbc-aptx-aptxtws-aptxhd-aac-ldac-aptxadaptive

This rom is just awesome. Iodé is a great concept. Congratulations, guys, on a job well done! Probably the best and most original rom I've seen since I registered on this forum (2009).
For info, my bluetooth headset works without any problem (I use the LDAC codec).
I made a dirty flash and everything works as excepted.

vince31fr said:
If you know which codec was used but does not work well (I read about problems with AAC but thought it was fixed), you can remove it by editing /vendor/build.prop, and remove -aac from the line
Code:
persist.vendor.qcom.bluetooth.a2dp_offload_cap=sbc-aptx-aptxtws-aptxhd-aac-ldac-aptxadaptive
Click to expand...
Click to collapse
Yes, it is AAC which is my problem.
But removing -aac from that line in build.prop didn't change anything.. The default codec is still AAC after a reboot. It goes back to AAC when I disconnect my headset also.

peking12 said:
If you know which codec was used but does not work well (I read about problems with AAC but thought it was fixed), you can remove it by editing /vendor/build.prop, and remove -aac from the line
Yes, it is AAC which is my problem.
But removing -aac from that line in build.prop didn't change anything.. The default codec is still AAC after a reboot. It goes back to AAC when I disconnect my headset also.
Click to expand...
Click to collapse
Try to remove aac in /system/build.prop too

wain_hero said:
This rom is just awesome. Iodé is a great concept. Congratulations, guys, on a job well done! Probably the best and most original rom I've seen since I registered on this forum (2009).
For info, my bluetooth headset works without any problem (I use the LDAC codec).
I made a dirty flash and everything works as excepted.
Click to expand...
Click to collapse
Many thanks for that enthusiastic comment! We could not expect much more
We're just at the beginning, many things remain to be done. Especially in the adblocker, which is the tough part, requiring a lot of development... Btw, what's your opinion about it ?

vince31fr said:
Try to remove aac in /system/build.prop too
Click to expand...
Click to collapse
Doing that prevents my phone from booting. Tried it two times and results are the same.
I was not allowed to edit /system/build.prop from a file manager with root privileges. Therefore I had to do it in TWRP.
I copied /system/build.prop and edited it. Then booted in TWRP to replace /system/build.prop with my edited version. I also took a backup of the original file.
Phone won't boot with the edited version, but booted when I put back the original version.

[ROM][APOLLON][A12] iodéOS = LineageOS 19.1 + MicroG + adblocker [04/04/2023]

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Introduction
iodéOS is a privacy-focused operating system powered by LineageOS and based on the Android mobile platform. iodéOS aims at protecting the user's privacy with a built-in adblocker and by freeing the smartphone from snitches.
The objectives in the conception of this ROM are threefold:
To keep the stability and security level of LineageOS, by minimizing the modifications made to the system. Apart the system modifications required by the adblocker, we mainly only added a few useful options commonly found in other custom ROMs, made some cosmetic changes, modified a few default settings to prevent data leaks to Google servers.
To ease a quick adoption of this ROM by new users. We especially target users that are concerned by the protection of their privacy, but are not reluctant to still use inquisitive apps like Google ones. We thus included MicroG as well as a coherent set of default apps, and simplified the initial setup of the system. Particularly, an initialization of MicroG has been made with GCM notifications allowed by default, a privacy-friendly network location provider (DéjàVu) pre-selected, as well as Nominatim Geocoder.
To provide a new and powerful way of blocking ads, malwares, data leaks of all kinds to many intrusive servers. We are developing an analyzer, tightly integrated into the system, that captures all DNS requests and network traffic, as well as a user interface (the iodé app). Compared to some other well-known adblockers, this has the advantages of:
Avoiding to lock the VPN for that use. You can even use another adblocker that uses VPN technology alongside our blocker.
Being independent of the kind of DNS server used by the system or set by an independent app: classical DNS on UDP port 53 or any other one, DNS over TLS (DoT), DNS over HTTPS (DoH), ..., as we capture the DNS requests before they are transmitted to the system function that emits the DNS request. What we do not support, is DoH when it is natively built into applications, i.e. when an app communicates directly with a DoH server, without asking name resolution to the system. It would require to decrypt HTTPS packets between such an app and the DoH server, which may create a big security hole.
Precisely mapping DNS requests and network packets to the Android apps that emitted (or received) them.
Deciding which apps have a filtered network usage (by default, all apps), and which ones can communicate with blacklisted servers.
Since its first versions, we added many features to the iodé blocker: several levels of protection, fine-grained control over the hosts that should be blocked or authorized, displaying statistics on a map to see the quantity of data exchanged to which countries, clearing statistics... We are actively developing the blocker, and new functionalities will be regularly added.
Features
Changes in LineageOS to prevent data leaks:
Default DNS server: Google's DNS replaced by Quad9's 'unblocked' servers in all parts of the system.
A-GPS: patches to avoid leaking personnal information like IMSI to supl server.
Captive portal login: connectivitycheck.gstatic.com replaced by captiveportal.kuketz.de for connectivity check.
Dialer: Google default option replaced by OpenStreetMap for phone number lookup.
Pre-installed apps:
We included many useful default apps, but our choice cannot suit everyone; so we added the possibility to remove them. It can be done at the end of the phone setup, or at any time by going to Parameters -> Apps & Notifications -> Preinstalled apps.
MicroG core apps: GmsCore, GsfProxy, FakeStore.
NLP backends for MicroG : DejaVuNLPBackend (default), MozillaNLPBackend, AppleNLPBackend, RadioCellsNLPBackend, Nominatim Geocoder.
App stores : FDroid (with F-Droid Privileged Extension) and Aurora Store.
Browser: our own fork of Firefox (with Qwant as default search engine, many other ones added, telemetry disabled, parts of telemetry code removed) instead of Lineage’s default browser Jelly.
SMS: QKSMS instead of Lineage's default SMS app.
Email: p≡p (Pretty Easy Privacy).
Camera: our own fork of Open Camera, with a few tweaks.
Maps/navigation: Magic Earth GPS & Navigation (the only one free but not open source).
Keyboard: OpenBoard instead of AOSP keyboard.
PDF: Pdf Viewer Plus.
Personnal notes: Carnet.
{Ad/Malware/Data leak}-blocker: iodé.
News: to keep users informed about our developments, as well as a FAQ.
Meteo: Geometric Weather.
Pre-included FDroid repository:
The apps that we tweak or develop (microG services, the browser based on Firefox, the News app, Open Camera ...) are available through a repository that we included in FDroid (check the "Apps for iodéOS" category). For this purpose and to avoid name conflicts of some apps, we also had to make a few changes in FDroid.
Useful options from other custom ROMs:
Smart charging (disables charging when a given level is reached, to protect battery health).
Fingerprint vibration toggle.
Swipe down to clear all in recent apps (Android 10 only).
Installation Instructions
To download and flash our latest build, see https://gitlab.com/iode/ota.
You can also find here direct links to the latest builds.
Supported devices
Fairphone FP3/FP3+
Fairphone FP4
Google Pixel 3
Google Pixel 4
Google Pixel 5
Google Pixel 6
Google Pixel 6a
OnePlus 9
OnePlus 9 Pro
Samsung Galaxy A5/A7 2017 (a5j17lte/a7j17lte)
Samsung Galaxy S9/S9+ (starlte/star2lte)
Samsung Galaxy Note 9 (crownlte)
Samsung S10e/S10/S10+ (beyond{0,1,2}lte)
Samsung Note 10 (d1)
Samsung Note 10+ (d2s)
Sony Xperia XA2 (pioneer)
Sony Xperia XZ1 (poplar)
Sony Xperia XZ2 (akari)
Sony Xperia XZ3 (akatsuki)
Xiaomi Mi9 (cepheus)
Teracube 2e
Xiaomi Mi 10T 5G / Mi 10T Pro 5G
Xiaomi Mi 10 Lite 5G
Sources
iodéOS: https://gitlab.com/iode/os
LineageOS: https://github.com/lineageos
device tree: https://gitlab.com/iode/os/public/devices/xiaomi/device_xiaomi/apollon
kernel: https://github.com/LineageOS/android_kernel_xiaomi_sm8250
Bug Reporting
You can post a message in this thread or (preferred) open an issue here.
Credits
LineageOS is a free, community built, aftermarket firmware distribution of android, which is designed to increase performance and reliability over stock android for your device.
All the source code for LineageOS is available in the LineageOS Github repo. If you would like to contribute to LineageOS, please visit their Wiki for more details.
This ROM would be nothing without the tremendous work made on MicroG, and all the other open source apps that we included. We are very grateful to their authors.
Contributors
Direct contributors: @iodeOS, @vince31fr
Indirect contributors (too numerous to list): All the people that contributed to the device tree, to LineageOS, and to the included open source apps.
Sponsoring
You can help in the development of this ROM by paying us a coffee here: https://paypal.me/iodeOS.
Screenshots

Downloads : iodéOS
04/04/2023 (build 20230401):
Installation procedure: move to a fastboot script (read instructions: https://gitlab.com/iode/ota)
Blocker: improved use of blocking lists (sub-domains blocking)
FDroid: fixes an issue on apps update
LineageOS synchronized with March security patch included
All apps updated
07/02/2023 (build 20230131):
Blocker:
Improved blocking settings. You can now choose 'Standard' blocking (ads, trackers, malwares, etc) or 'Reinforced' blocking (same objective but more extensive), and then select additional categories.
The 'Porn' category has been extended to a wider 'Sensitive content' one, that also includes fake news, gambling, drugs, piracy, torrent..., with mainly child protection in mind.
The 'Extreme' category has been removed, as it is now part of the reinforced blocking.
Improved blocking lists. We merge several acknowledged and up-to-date sources, and have diversified our sources to produce more complete lists. The standard list has however been reduced a bit, to avoid as much as possible interference with apps expected behavior.
Added a new network location provider: Local NLP Backend. It is an improved version of the DéjàVu NLP backend which was already available in iodéOS. Like DéjàVu, it builds a local database connecting localizations learned from other NLP backends and apps using GPS, and mobile antennas/Wifi; but also has an active mode (not preselected) that can trigger GPS requests. To configure it: Settings -> System -> microG -> Location modules
LineageOS synchronized with January security patch included
All apps updated
New devices support: Pixel 3, 6, 6a
16/12/2022 (build 20221215):
Blocker: added multiple selection in settings / domain customization. Long-press on a domain, select several domains or all, apply actions (block all, authorize all...)
PdfViewerPlus: improved security by updating core libraries
Network settings: added a switch to disable connectivity check (and thus captive portal detection)
LineageOS synchronized with December security patch included
All apps updated
New devices support: Pixel 4 & 5, OnePlus 9 & 9 Pro
24/11/2022 (build 20221121):
Improvements in the blocker user interface (iodé app)
LineageOS synced with September security patch included
All apps updated
17/10/2022 (build 20221014):
Blocker:
Network blockings following their type (Wifi, mobile data, VPN) added
Default blockings definition for new apps
Personnalized recipients management improved
iodé's app access restrictions by password added
Search filters added in report and map
Display theme selection
Automatic and 'real-time' refresh of the whole app
Performance and fluidity improvements of the app
LineageOS synced with September security patch included
All apps updated
27/07/2022 (build 20220726):
Upgrade to iodéOS 3.1 based on Android 12 / LineageOS 19.1
SafetyNet certification activated: allows many apps, notably banking ones, to fully work
Setup wizard: the push notifications configuration page now also activates SafetyNet (fine-grained control in Settings->System->microG)
OpenCamera: the 'Use alternative flash method' in photo settings is no more necessary and can be disabled, allowing flash optimization
News app: German translations
LineageOS synced with July security patch included
All apps updated
02/05/2022 (build 20220408):
News app reworked
Setup Wizard: new iodé introduction
iodé blocker: pull to refresh replaced by automatic refresh in report tab
Teracube 2e 2022 batch released, video playback in browser and video recording fixed
Music app : playlist crash fixed
Open Camera : crash when tapping thumbnail of a newly recorded video fixed, photos and videos now editable
LineageOS synced with March security patch
All apps updated
03/02/2022 (build 20220127): initial publicly available build of iodéOS for apollon.

@vince31fr are you on telegram? Would be nice to post this in Apollo channels there. Looks like great work

Dosen't work for me.
Current from LineageOS 18.1
TWRP: 3.5.2_10_By_Master
Workflow:
- TWRP
- Wipe Data
- Sideload lineage-18.1-20220122-nightly-apollon-signed.zip
Code:
Starting ADB sideload feature...
minadbd I 02-05 06:01:26 697 698 usb_ffs.cpp:232] opening control endpoint /dev/usb-ffs/adb/ep0
minadbd E 02-05 06:01:26 697 698 usb_ffs.cpp:249] failed to write USB descriptors: No such process
minadbd I 02-05 06:01:27 697 698 usb_ffs.cpp:232] opening control endpoint /dev/usb-ffs/adb/ep0
minadbd I 02-05 06:01:27 697 698 usb.cpp:180] UsbFfsConnection constructed
minadbd I 02-05 06:01:27 697 700 usb.cpp:311] USB event: FUNCTIONFS_BIND
minadbd I 02-05 06:01:27 697 700 usb.cpp:311] USB event: FUNCTIONFS_ENABLE
minadbd I 02-05 06:01:27 697 697 adb.cpp:110] UsbFfs: already offline
minadbd I 02-05 06:01:32 697 702 minadbd_services.cpp:110] sideload-host file size 1463511061, block size 65536
Installing zip file '/sideload/package.zip'
unknown fuse request opcode 2016
Unmounting System...
I:Update binary zip
Verifying package compatibility...
Package doesn't contain compatibility.zip entry
I:Extracting updater binary 'META-INF/com/google/android/update-binary'
I:Zip does not contain SELinux file_contexts file in its root.
I:Legacy property environment not used in updater.
SELinux: Loaded file_contexts
unknown fuse request opcode 2016
Target: Redmi/apollo_global/apollo:11/RKQ1.200826.002/V12.5.5.0.RJDMIXM:user/release-keys
Extracted file "/tmp/install/bin/backuptool.functions"
Extracted file "/tmp/install/bin/backuptool.sh"
Extracted 2 file(s)
Target: Redmi/apollo_global/apollo:11/RKQ1.200826.002/V12.5.5.0.RJDMIXM:user/release-keysDM_DEV_REMOVE failed for [system]: Device or resource busy
Cannot unmap system before removing group qti_dynamic_partitions.
script aborted: assert failed: update_dynamic_partitions(package_extract_file("dynamic_partitions_op_list"))
assert failed: update_dynamic_partitions(package_extract_file("dynamic_partitions_op_list"))error: 25
Updater process ended with ERROR: 1

xps1992 said:
Dosen't work for me.
Current from LineageOS 18.1
TWRP: 3.5.2_10_By_Master
Workflow:
- TWRP
- Wipe Data
- Sideload lineage-18.1-20220122-nightly-apollon-signed.zip
Code:
Starting ADB sideload feature...
minadbd I 02-05 06:01:26 697 698 usb_ffs.cpp:232] opening control endpoint /dev/usb-ffs/adb/ep0
minadbd E 02-05 06:01:26 697 698 usb_ffs.cpp:249] failed to write USB descriptors: No such process
minadbd I 02-05 06:01:27 697 698 usb_ffs.cpp:232] opening control endpoint /dev/usb-ffs/adb/ep0
minadbd I 02-05 06:01:27 697 698 usb.cpp:180] UsbFfsConnection constructed
minadbd I 02-05 06:01:27 697 700 usb.cpp:311] USB event: FUNCTIONFS_BIND
minadbd I 02-05 06:01:27 697 700 usb.cpp:311] USB event: FUNCTIONFS_ENABLE
minadbd I 02-05 06:01:27 697 697 adb.cpp:110] UsbFfs: already offline
minadbd I 02-05 06:01:32 697 702 minadbd_services.cpp:110] sideload-host file size 1463511061, block size 65536
Installing zip file '/sideload/package.zip'
unknown fuse request opcode 2016
Unmounting System...
I:Update binary zip
Verifying package compatibility...
Package doesn't contain compatibility.zip entry
I:Extracting updater binary 'META-INF/com/google/android/update-binary'
I:Zip does not contain SELinux file_contexts file in its root.
I:Legacy property environment not used in updater.
SELinux: Loaded file_contexts
unknown fuse request opcode 2016
Target: Redmi/apollo_global/apollo:11/RKQ1.200826.002/V12.5.5.0.RJDMIXM:user/release-keys
Extracted file "/tmp/install/bin/backuptool.functions"
Extracted file "/tmp/install/bin/backuptool.sh"
Extracted 2 file(s)
Target: Redmi/apollo_global/apollo:11/RKQ1.200826.002/V12.5.5.0.RJDMIXM:user/release-keysDM_DEV_REMOVE failed for [system]: Device or resource busy
Cannot unmap system before removing group qti_dynamic_partitions.
script aborted: assert failed: update_dynamic_partitions(package_extract_file("dynamic_partitions_op_list"))
assert failed: update_dynamic_partitions(package_extract_file("dynamic_partitions_op_list"))error: 25
Updater process ended with ERROR: 1
Click to expand...
Click to collapse
USE LINEAGE RECOVERY.. WORKS WELL

Hello sir, please share support group

*** New Update : 02/05/2022 ***
Available as OTA (see OP)​

Nice build, but can u add in it smth to manage TTL and may be VIper instead of AudioFX?

Hello out there.
Yesterday i did the update from 2.4 to 3.0 (Android 12) and discovered, that NFC-option and Battery Saver are greyed out, even in settings. So i did a firmware update to V13.0.6.0.SJDEUXM. Battery Saver is back, NFC is not. Apps using NFC do not detect NFC. Did i miss something?
Regards

*** New Update : 27/07/2022 ***
Upgrade to Android 12 /LineageOS 19.1
Available as OTA (see OP)​

110errm said:
Hello out there.
Yesterday i did the update from 2.4 to 3.0 (Android 12) and discovered, that NFC-option and Battery Saver are greyed out, even in settings. So i did a firmware update to V13.0.6.0.SJDEUXM. Battery Saver is back, NFC is not. Apps using NFC do not detect NFC. Did i miss something?
Regards
Click to expand...
Click to collapse
Unfortunately, the build you flashed has been discarded very shortly after it has been released. The last one solves these issues.

vince31fr said:
Unfortunately, the build you flashed has been discarded very shortly after it has been released. The last one solves these issues.
Click to expand...
Click to collapse
Yessss. Everything is working quite well now. Even battery live is like before. Thank u. For me it's perfect now.

I really like much of what this ROM provides, but I'm rather connected to Google services at the moment:
* Gmail
* Calendar
* Maps
* Android Auto
* Work profile
* Play Store
Is it possible to still have main Google apps like this working properly while benefiting from everything else the ROM provides?

*** New Update : 17/10/2022 ***
Available as OTA (see OP)​

BREAKING NEWS
iodéOS is now fully Open Source!
(read more here)​

*** New Update : 24/11/2022 ***
Available as OTA (see OP)​

I want to try this piece of art, seems the best rom we can use.

I use it on MI 9 and Mi 10T and Mi 10T pro and nothing can reach this it is top of the top.

Been using about one month. The idea that iode that block ads without all around the system and prevent data leaks is great . The only problem i face is battery draining while in idle. Thank you developer for your support to our device!

Yesterday I tried the Rom, it looked very nice, I love all the philosophy, the aesthetics and that they use Lineage as a base, but I thought that the battery would last longer than with Lineage + Gapps, but the duration was the same, I didn't give time to see how it runs out in iddle.
It reminds me of Nobara or Ubuntu or other distributions that make all the work easier for you so that you just have to enjoy it and it is something to be thankful for, because it brings this whole niche closer to common users.
The only problem is that I like to be the one who installs and chooses what to install at all times, although I can disable or uninstall things, but this is my personal thing (I prefer Debian to Ubuntu or Fedora to Nobara, only I would not use Debian since requires much more work than for example Fedora with the same results)
Once again, thank you for this work and bringing these types of alternatives closer.