Happy to know that it finally works now.
It is of no use for custom ROMs but for others, it’s very much required to get certified(Google approval). CTS just makes sure that the device is compliant with respect to the Android CDD for that particular version.
Since i did my update to 22.2 (a few weeks ago) some apps can’t update in the background it seems?
Stuff like threema push, ntfy still works fine, it seems that only apps which do tasks from ‘time to time’ are stuck. Like FOSS Warn (which pulls notifs every 15 min), currently displays in the notification: Last update: 18:57, next update 19:12 (currently its 21:43). Another example would be thunderbird and my calendar. Thunderbird should pull mails every 30 minutes and my calendar don’t display event reminders. As soon as i open one of the apps everything works fine as long as i have them open xD
I don’t run any google services or microg, just plain lineageos. I also i did not knowningly but back on some batterysaving stuff
am i the only one with this problem?
I can confirm Threema push works, but background updates for Thunderbird won’t (with LOS 22.2-20250507).
However calender sync with DAVx5 works. Btw. background usage is enabled for all 3 apps.
Running LOS without google service or microg.
I tried to debug video_encoder_device_v4l2.cpp, which, as TeamB58 mentioned, could contain the relevant change. But I couldn’t make out any of the debug messages from the video_encoder in adb logcat.
But I found interesting log entries from CCode which seams to be connected with the encoding process.
Full HD resolution appears to be seen by CCode as the maximum width and height.:
05-24 13:54:51.014 1215 22368 I CCodecConfig: query failed after returning 12 values (BAD_INDEX)
05-24 13:54:51.014 1215 22368 D CCodecConfig: c2 config diff is c2::u32 raw.color.matrix = 1
05-24 13:54:51.014 1215 22368 D CCodecConfig: c2::u32 raw.color.primaries = 1
05-24 13:54:51.014 1215 22368 D CCodecConfig: c2::u32 raw.color.transfer = 3
05-24 13:54:51.014 1215 22368 D CCodecConfig: c2::u32 raw.max-size.height = 1080
05-24 13:54:51.014 1215 22368 D CCodecConfig: c2::u32 raw.max-size.width = 1920
When comparing the log for starting a video record with full HD resolution and 4k the relevant difference in the log is:
05-20 19:55:40.887 1260 2190 D VQApply : minquality: 3840x2160 outside of shaping range
05-20 19:55:40.887 1260 2190 D MediaCodec: shapeMediaFormat: deltas(1): AMessage(what = 0x00000000) = {
05-20 19:55:40.887 1260 2190 D MediaCodec: int32_t android._encoding-quality-level = 0
05-20 19:55:40.887 1260 2190 D MediaCodec: }
05-20 19:55:40.888 1260 11311 D CCodec : [c2.android.avc.encoder] buffers are bound to CCodec for this session
05-20 19:55:40.888 1260 11311 D CCodecConfig: no c2 equivalents for stride
05-20 19:55:40.888 1260 11311 D CCodecConfig: no c2 equivalents for slice-height
05-20 19:55:40.888 1260 11311 D CCodecConfig: no c2 equivalents for color-format
05-20 19:55:40.888 1260 11311 D CCodecConfig: no c2 equivalents for create-input-buffers-suspended
05-20 19:55:40.888 1260 11311 D CCodecConfig: no c2 equivalents for flags
05-20 19:55:40.888 1260 11311 D CCodecConfig: no c2 equivalents for encoder
05-20 19:55:40.889 1260 11311 D CCodecConfig: Bad parameter value
05-20 19:55:40.889 1260 11311 D CCodecConfig: c2 config diff is c2::u32 coded.bitrate.value = 42000000
05-20 19:55:40.889 1260 11311 D CCodecConfig: c2::float coded.frame-rate.value = 30
05-20 19:55:40.889 1260 11311 D CCodecConfig: c2::u32 raw.size.height = 2160
05-20 19:55:40.890 1260 11311 W ColorUtils: expected specified color aspects (0:0:0:0)
05-20 19:55:40.890 1260 11311 W CCodec : failed to configure c2 params
While the message from VQApply does not seem to be too relevant it shows us the configured resolution. However CCodecConfig complains about a bad parameter and won’t print the resolution width. It did print the resolution width when full HD resolution was set.
@TeamB58: I think you should undo the mentioned commit just to see if it affects the video recording feature as expected. If so we can still lock for a better solution.
If it is not needed, it is cool that it can be done, but losing 4k for it? I would prefer to keep 4k.
I am highly appreciative of you work though. You really keep this going brilliantly. I habe very high respect for that.
It totally depends on you. Since you said it works without any changes I was happy to not drop the change.
But if you say that it’s still broken then I am fine to get it reverted.
I am sorry, there is a misunderstanding. The HD recording via OpenCamera was broken as well as the 4k in both camera apps.
With the update, the HD recording now works fine again, for whatever reason (I could not find a commit that fit the bill). The 4K is still broken.
I would prefer your change to be reverted if that is the only way to fix the 4K, but I would prefer others to also chime in. 
For me there is no benefit in the 4K modus as the camera is sooo bad that in the end it don’t matter to use the higher resolution.
Btw it seems to be fixed with LOS22.2-20250528 ^^
Indeed, it is recording in 4k again. Did you revert the change?
erm i meant my problem regarding the background app usage 
Cool, then both are solved!
Hello, first I want to thank everybody who brought this new upgrade. Most things work well so far (first day) I have only a small problem since upgrading to LOS4microG 22.1 (20250609) the small light which should only burn when the phone is charging does never go out. It’s a bit annoying. And I did a proper new installation full wipe and all
the problem with the light is solved it disappeared over night
Latest update today is failung during installation, everytime. OTA as well manual.
Is it me or the update-image? Had problems updating Magisk as well.
Hi jelger,
no issue with the 22.2 July 2 build, which I installed as usual, earlier today.
as for magisk, it seems that the first update breaks it and i didnt try to fix it ; my banking apps and itsme still work for some reason, and I can even update them
I disabled some modules in Magisk and update succeeded finally.
With this build, my phone calls all go to external speaker with no way to go to the internal one… Is this only me?
The issue resolved itself with the current update. All good.