Database Develop

[ROM][5.x] SlimLP

SlimLP
[#LOLLI]
[#ESPRESSONAME]
​
[#WHATSSLIM]
[#WARRANTY]
Download:
[#DLGITHUBIO]
[#INFOSLIM]
Disclaimer: SlimRoms are not responsible for any damages to your device.
[#DONATETOME]
XDA:DevDB Information
[unified] SlimLP, ROM for the Samsung Galaxy Tab 2
Contributors
Android-Andi, SlimRoms
Source Code: https://github.com/SlimRoms/kernel_samsung_espresso10
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.0.x
Version Information
Status: Alpha
Created 2014-12-10
Last Updated 2017-04-30

Reserved
Screenshots attached

Kudos and thanks to all the special Devs let the tablet have new life. [emoji106] [emoji106] [emoji106]
GT- N7100 with Dr.Ketan Hindocha Rom Android 4.4.2

That's great, nice move thank You @Android-Andi :good:

Great!! Thanks dude!!

Initial P3100 build available now Not sure if it works/boots - you will let me know
Someone on P3100 please get out some information for me,
you need su permissions (please flash latest SuperSU from Chainfire):
Code:
adb shell su -c dmesg | grep 'avc: '
Also please upload a complete dmesg for me.

Android-Andi said:
Initial P3100 build available now Not sure if it works/boots - you will let me know
Someone on P3100 please get out some information for me,
you need su permissions (please flash latest SuperSU from Chainfire):
Code:
adb shell su -c dmesg | grep 'avc: '
Also please upload a complete dmesg for me.
Click to expand...
Click to collapse
Tomorrow morning!

Thank you for making this possible!
All the best for you

Working well for me on my p3110 - brilliant job, well done and many thanks
Sent from my BN NookHD+ using XDA Free mobile app

Android-Andi said:
Initial P3100 build available now Not sure if it works/boots - you will let me know
Someone on P3100 please get out some information for me,
you need su permissions (please flash latest SuperSU from Chainfire):
Code:
adb shell su -c dmesg | grep 'avc: '
Also please upload a complete dmesg for me.
Click to expand...
Click to collapse
@Android-Andi I will try now your work ... Feedback in an hour. (I hope it boot ☺)
EDIT:
It boot. I'm writing from tab2 P3100 with slimlp 0.8.
First boot take some time and the boot animation is not fluid.
I now try to install SuperSU and restart the system.
After I try adb shell (from terminal?)

@philidor thanks a lot
adb shell from your PC, need adb binary on your pc.
You can also use Terminal Emulator on your device (but don't type "adb shell").
Edit:
mobile data works?

Android-Andi said:
Someone on P3100 please get out some information for me,
you need su permissions (please flash latest SuperSU from Chainfire):
Code:
adb shell su -c dmesg | grep 'avc: '
Also please upload a complete dmesg for me.
Click to expand...
Click to collapse
Should i do this also on P3110?

Android-Andi said:
@philidor thanks a lot
adb shell from your PC, need adb binary on your pc.
You can also use Terminal Emulator on your device (but don't type "adb shell").
Edit:
mobile data works?
Click to expand...
Click to collapse
@Android-Andi, can i use my terminal in my iMac with the same command you give us? in this case, my tab should be in download mode, right?

SlimShady's said:
Should i do this also on P3110?
Click to expand...
Click to collapse
You can test from time from time if you get an output for "avc:", it will show if there are some denial because of selinux. If i get the output i am able to add a policy to fix it. Hope we can switch to enforced soon
Send from OnePlus One using Tapatalk

MARKBOARD NETSET said:
@Android-Andi, can i use my terminal in my iMac with the same command you give us? in this case, my tab should be in download mode, right?
Click to expand...
Click to collapse
No, device need to boot android.
http://m.youtube.com/watch?v=TMcMVDUbpis
Send from OnePlus One using Tapatalk

Android-Andi said:
You can test from time from time if you get an output for "avc:", it will show if there are some denial because of selinux. If i get the output i am able to add a policy to fix it. Hope we can switch to enforced soon
Send from OnePlus One using Tapatalk
Click to expand...
Click to collapse
My brain stopped working at "if you get an" xD
Edit: Oh, okay I got it. Will do this tomorrow

Android-Andi said:
@philidor thanks a lot
adb shell from your PC, need adb binary on your pc.
You can also use Terminal Emulator on your device (but don't type "adb shell").
Edit:
mobile data works?
Click to expand...
Click to collapse
@android-Andy Tanks YOU a lot!! Sorry I can only help you as a tester.
3G not working. (See picture) I can receive SMS but can't send.
Problem with root binaries. SuperSU installed give me some minutes.
After I will try your commands. Have you some tests for me?

Android-Andi said:
@philidor thanks a lot
Edit:
mobile data works?
Click to expand...
Click to collapse
yes:highfive::good:

jak978 said:
yes:highfive::good:
Click to expand...
Click to collapse
No mobile data don't work for me. I can receive SMS and have my normal signal bars
This is your grep command @Android-Andi
[email protected]:/ $ su -c dmesg | grep 'avc: '
[ 4.256500] C0 [ init] avc: granted { set } for property=net.rmnet0.dns1 scontext=u:r:rild:s0 tcontext=ubject_r:net_radio_prop:s0 tclass=property_service
[ 4.256958] C0 [ init] avc: granted { set } for property=net.rmnet0.dns2 scontext=u:r:rild:s0 tcontext=ubject_r:net_radio_prop:s0 tclass=property_service
[ 4.257263] C0 [ init] avc: granted { set } for property=net.rmnet0.gw scontext=u:r:rild:s0 tcontext=ubject_r:net_radio_prop:s0 tclass=property_service
[ 4.258392] C0 [ init] avc: granted { set } for property=net.rmnet1.dns1 scontext=u:r:rild:s0 tcontext=ubject_r:net_radio_prop:s0 tclass=property_service
[ 4.258728] C0 [ init] avc: granted { set } for property=net.rmnet1.dns2 scontext=u:r:rild:s0 tcontext=ubject_r:net_radio_prop:s0 tclass=property_service
[ 4.259002] C0 [ init] avc: granted { set } for property=net.rmnet1.gw scontext=u:r:rild:s0 tcontext=ubject_r:net_radio_prop:s0 tclass=property_service
[ 4.260101] C0 [ init] avc: granted { set } for property=net.rmnet2.dns1 scontext=u:r:rild:s0 tcontext=ubject_r:net_radio_prop:s0 tclass=property_service
[ 4.260437] C0 [ init] avc: granted { set } for property=net.rmnet2.dns2 scontext=u:r:rild:s0 tcontext=ubject_r:net_radio_prop:s0 tclass=property_service
[ 4.260742] C0 [ init] avc: granted { set } for property=net.rmnet2.gw scontext=u:r:rild:s0 tcontext=ubject_r:net_radio_prop:s0 tclass=property_service
[ 5.750274] C1 [ init] avc: denied { set } for property=supolicy.loaded scontext=u:r:sysinit:s0 tcontext=ubject_r:default_prop:s0 tclass=property_service
[email protected]:/ $

Flashed this as soon when saw that P3100 port also ready. Thanks AndroidAndi! U are really really awesome! Straight change the P3113 version to this version. All working even YouTube able to load video.
What work
- Everything
- Video Player works too. No need 3rd party
Not Working
- 3G Maybe? (haven't tried)
- Recent tab, card stack works perfectly in landscape. When change to portrait, it turns to black color. But, not bothering

[HELP] Some questions about building errors!

Hey all, what's up?
I got a problem, and I'm going crazy xD
I've successfully done a repo sync of AOSPA Legacy and successfully downloaded:
-Device Tree: https://github.com/CyanogenMod/android_device_lge_w7
-Kernel: https://github.com/CyanogenMod/android_kernel_lge_msm8226
-Vendor: https://github.com/Quarx2k/proprietary_vendor_lge
Now I'm following this guide: http://forum.xda-developers.com/showthread.php?t=1863547
In a step it tells me to extract "proprietary-files.sh" from my device folder.
Our "proprietary-files.sh" is called "setup-makefiles.sh"?
This is the first question.
The second question is that I must follow this tip.
"# Create /manifest/<device>.adds:
I'll give you two examples of .adds, to show the general extent of variation between devices:
For i9300:
Code:
Code:
[
{
"remote": "github",
"account": "CyanogenMod",
"repository": "android_frameworks_av",
"target_path": "frameworks/av",
"revision": "cm-10.1"
},
{
"remote": "github",
"account": "CyanogenMod",
"repository": "android_frameworks_native",
"target_path": "frameworks/native",
"revision": "cm-10.1"
Where I can find this kind of repos? D: I tried Googling but with no luck.
3rd question: Where I can find also this kind of things? >_<
"# Create /manifest/<device>.removes:
For i9300:
Code:
Code:
{
"name": "platform/frameworks/av",
"path": "frameworks/av"
},
{
"name": "ParanoidAndroid/android_frameworks_native",
"path": "frameworks/native"
},
{
"name": "platform/hardware/libhardware",
"path": "hardware/libhardware"
},
{
"name": "platform/hardware/libhardware_legacy",
"path": "hardware/libhardware_legacy"
},
{
"name": "device/common",
"path": "device/common"
},
{
"name": "ParanoidAndroid/android_frameworks_opt_telephony",
"path": "frameworks/opt/telephony"
}
]
Help me out
Last question: When I try to build..After 5 min the terminal gives me this.
Code:
"No private recovery resources for TARGET_DEVICE w7
make: *** Nessuna regola per generare l'obiettivo "external/chromium_org/v8/tools/gyp/generate_trig_table.host.linux-arm.mk". Arresto."
And also before this errors, there are other errors like:
Code:
"external/chromium_org/v8/tools/gyp/generate_trig_table.host.linux-arm.mk: File o directory non esistente
find: "phone/java": File o directory non esistente
find: "phone/java": File o directory non esistente
find: "dummy": File o directory non esistente"
If anyone can help me, please answer!
Thank you!!

You don't need to run that command, the proprietary_vendor_lge folder that you added to the manifest is what houses all of those files. Also, you will need to do quite a bit of file editing to get a cm device tree to build properly on AOSP. With that being said, there are much better/easier guides out there to set up your build environment. I'll find a couple and post them here for you to check out

CaptivateKing said:
You don't need to run that command, the proprietary_vendor_lge folder that you added to the manifest is what houses all of those files. Also, you will need to do quite a bit of file editing to get a cm device tree to build properly on AOSP. With that being said, there are much better/easier guides out there to set up your build environment. I'll find a couple and post them here for you to check out
Click to expand...
Click to collapse
I don't want to build a AOSP. I wanna build an AOSPA/Paranoid
Anyways thank you for your answer.

SlimShady's said:
I don't want to build a AOSP. I wanna build an AOSPA/Paranoid
Anyways thank you for your answer.
Click to expand...
Click to collapse
I meant to type AOSPA, but the same goes for building anything that isn't cm, or cm based. You will have to edit a few make files for it to compile correctly with a cm device tree

CaptivateKing said:
I meant to type AOSPA, but the same goes for building anything that isn't cm, or cm based. You will have to edit a few make files for it to compile correctly with a cm device tree
Click to expand...
Click to collapse
And how can I do it?

Grim Fandango Remastered not working with Magisk

Hello everyone,
Grim Fandango Remastered exits immediately when Magisk is installed.
Its working fine with SuperSU.
I am running LineageOS 14.1 on a Xperia Z4 Tablet and tried Magisk 16.0/16.3/16.4.
BTW: Netflix and Prime Video working fine despite CTS Profile failure. Basic integrity check is okay.
Any ideas?
Greetings,
Medizinmann

Unless you post a logcat from when the app exits, it's gonna be hard to have any ideas...

Didgeridoohan said:
Unless you post a logcat from when the app exits, it's gonna be hard to have any ideas...
Click to expand...
Click to collapse
Here is the logcat.....
Any help appreciated!
Greetings,
Medizinmann

Didgeridoohan said:
Unless you post a logcat from when the app exits, it's gonna be hard to have any ideas...
Click to expand...
Click to collapse
After analyzing the logcat i found the following...
Code:
[ 07-05 20:34:59.404 423: 428 E/Vold ]
ASEC loop device creation failed for /storage/emulated/0/Android/obb/com.doublefine.grimfandangoremastered/main.150.com.doublefine.grimfandangoremastered.obb (Permission denied)
[ 07-05 20:34:59.404 423: 428 W/Vold ]
Returning OperationFailed - no handler for errno 13
[ 07-05 20:34:59.404 1578: 2362 D/VoldConnector ]
RCV <- {400 21 obb operation failed (Permission denied)}
[ 07-05 20:34:59.390 428: 428 W/vold ]
type=1400 audit(0.0:415): avc: denied { getattr } for path="/data/adb/magisk.img" dev="mmcblk0p43" ino=508522 scontext=u:r:vold:s0 tcontext=u:object_r:adb_data_file:s0 tclass=file permissive=0
The problem seems to be, that the app can’t access their .obb-Files. But why is that?
Greetings,
Medizinmann

Medizinmann said:
The problem seems to be, that the app can’t access their .obb-Files. But why is that?
Click to expand...
Click to collapse
Yes, I saw that as well... And there's been similar reports for other apps.
It's because Magisk is using the loop device, and this seems to conflict with some apps. It's under investigation...

[ROM][OFFICIAL][pioneer][12] LineageOS 19

{
"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"
}
LineageOS is a free, community built, aftermarket firmware distribution of Android 12, which is designed to increase performance and reliability over stock Android for your device.
LineageOS is based on the Android Open Source Project, with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for LineageOS is available in the LineageOS GitHub organization. And if you would like to contribute to LineageOS, please visit our Gerrit Code Review. You can also view the changelog for a full list of changes & features.
Instructions :
https://wiki.lineageos.org/devices/pioneer/install
Downloads :
https://download.lineageos.org/pioneer
Reporting Bugs
DO NOT Report bugs if you're running a custom kernel, or you installed Xposed
Grab a logcat right after the problem has occurred. (Please include at least a few pages of the log, not just the last few lines, unless you know what you're doing.)
If it is a random reboot, grab /sys/fs/pstore/console-ramoops and /sys/fs/pstore/dmesg-ramoops-0. (Do not bother getting a logcat unless you can get it just before the reboot. A logcat after a reboot is useless)
Remember to provide as much info as possible. The more info you provide, the more likely that the bug will be solved. Please also do not report known issues. Any bug not reported in the bug report format below may be ignored.
Code:
What is your--
LineageOS version:
LineageOS Download url:
Gapps version:
Did you--
wipe:
restore with titanium backup:
reboot after having the issue:
Are you using--
a task killer:
a non-stock kernel:
other modifications:
Provide any additional information (observations/frequency of problem/last version it worked on/etc) as needed:

Thank you !
Just tested lineage-19.0-20220219_132428-UNOFFICIAL-pioneer.zip
A pretty good start for Android 12.
Tested and working :
- fingerprint sensor
- WiFi
- video playback on youtube with default browser
- camera front and rear + video recording + flash light
- USB MTP
- Gyroscope
Comments :
- audio playback working but crackles a bit when at maximum
- The settings menu overlaps the 3 buttons controls
Not tested :
- SIM card and everything related (calls, SMS, ...)
- Bluetooth
- GPS
- GApps
And other things.
Really love to see Android 12 on this one.

Android 12 on my sony xa2 will not boot past the lineage os logo even after changing a/b and factory resetting it is there a fix?

Rolling the lineage-19.0-20220301_131228-UNOFFICIAL-pioneer.zip with firmware 50.2.A.3.77
Tested and working:
- Wifi
- 4g / lte
- rear camera
Flakie :
- selfie camera is not working when switching from back, but then is working
When switching from back to selfie camera :
Code:
[ 627.762250] type=1400 audit(1646511939.837:2926): avc: denied { read } for comm="[email protected]" name="u:object_r:bootanim_system_prop:s0" dev="tmpfs" ino=13144 scontext=u:r:hal_camera_default:s0 tcontext=u:object_r:bootanim_system_prop:s0 tclass=file permissive=0
[ 627.763506] type=1400 audit(1646511939.837:2927): avc: denied { read } for comm="[email protected]" name="u:object_r:default_prop:s0" dev="tmpfs" ino=13201 scontext=u:r:hal_camera_default:s0 tcontext=u:object_r:default_prop:s0 tclass=file permissive=0
[ 627.763858] type=1400 audit(1646511939.837:2928): avc: denied { read } for comm="[email protected]" name="u:object_r:default_prop:s0" dev="tmpfs" ino=13201 scontext=u:r:hal_camera_default:s0 tcontext=u:object_r:default_prop:s0 tclass=file permissive=0
[ 627.782361] PU: mGpioCnt[4]: 1
[ 627.793963] PU: mGpioCnt[5]: 1
[ 627.817922] msm_cci_init:1439: hw_version = 0x10060000
[ 627.818168] msm_sensor_match_id CAM_ID_8M: 0
[ 627.823084] msm_csid_irq CSID2_IRQ_STATUS_ADDR = 0x800
[ 627.853709] msm_vfe47_process_error_status: camif error status: 0x264
[ 627.853760] 0x0000: 00000001 00000040 00000000 098f0cbf
[ 627.853769] 0x0010: 00000cbf 0000098f 00000000 00001f1f
[ 627.853779] 0x0020: ffffffff ffffffff 0014095d 00000264
[ 627.853786] 0x0030: 00000000 00000001 00000001
[ 627.953623] msm_isp_process_overflow_irq: vfe 1 overflowmask 10,bus_error 3f93
[ 627.953655] msm_vfe47_axi_halt: VFE1 halt for recovery, blocking 0
[ 627.953689] overflow processed
[ 627.988483] msm_isp_axi_halt: VFE1 Bus overflow detected: start recovery!
[ 627.988686] msm_vfe47_axi_halt: VFE1 halt for recovery, blocking 1
[ 627.989818] msm_ispif_restart_frame_boundary: ISPIF reset hw done, Restarting
[ 628.020401] msm_vfe47_process_error_status: camif error status: 0x264
[ 628.020452] 0x0000: 00000001 00000040 00000000 098f0cbf
[ 628.020462] 0x0010: 00000cbf 0000098f 00000000 00001f1f
[ 628.020471] 0x0020: ffffffff ffffffff 0014095d 00000264
[ 628.020479] 0x0030: 00000000 0000000f 0000000f
[ 628.053631] msm_isp_process_overflow_irq: vfe 1 overflowmask 10,bus_error 3f93
[ 628.053667] msm_vfe47_axi_halt: VFE1 halt for recovery, blocking 0
[ 628.053700] overflow processed
[ 628.910196] FG: fg_somc_get_real_temp: batt:257 aux:-2730 -> real battery temp:257
[ 628.910263] FG: fg_somc_jeita_step_charge_work: [Charging] RTEMP:257 IBATT:-40mA VBATT:3981mV VCELL:3982mV VCELL_MAX:4034
[ 628.910340] PMI: smblib_somc_handle_jeita_step_fv: set fv:4380000
[ 630.264121] q6asm_callback: payload size of 8 is less than expected.
[ 630.422670] msm_private_ioctl:Notifying subdevs about potential sof freeze
[ 630.422783] MSM-SENSOR-INIT msm_sensor_init_subdev_ioctl:119 default\x0a
[ 630.422965] msm_csid_irq CSID2_IRQ_STATUS_ADDR = 0xff
[ 630.423006] msm_csiphy_irq CSIPHY2_IRQ_STATUS_ADDR0 = 0x0
[ 630.423021] msm_csiphy_irq CSIPHY2_IRQ_STATUS_ADDR1 = 0x1
[ 630.423037] msm_csiphy_irq CSIPHY2_IRQ_STATUS_ADDR2 = 0x0
[ 630.423051] msm_csiphy_irq CSIPHY2_IRQ_STATUS_ADDR3 = 0x20
[ 630.423065] msm_csiphy_irq CSIPHY2_IRQ_STATUS_ADDR4 = 0x0
[ 630.423079] msm_csiphy_irq CSIPHY2_IRQ_STATUS_ADDR5 = 0x0
[ 630.423094] msm_csiphy_irq CSIPHY2_IRQ_STATUS_ADDR6 = 0x4
[ 630.423109] msm_csiphy_irq CSIPHY2_IRQ_STATUS_ADDR7 = 0x0
[ 630.423123] msm_csiphy_irq CSIPHY2_IRQ_STATUS_ADDR8 = 0x80
[ 630.423138] msm_csiphy_irq CSIPHY2_IRQ_STATUS_ADDR9 = 0x40
[ 630.426309] type=1400 audit(1646511942.497:2929): avc: denied { read } for comm="CAM_mct_freeze" name="clk" dev="debugfs" ino=4921 scontext=u:r:hal_camera_default:s0 tcontext=u:object_r:debugfs:s0 tclass=dir permissive=0
[ 630.454176] ispif_process_irq: PIX0 frame id: 2383
[ 630.488551] ispif_process_irq: PIX0 frame id: 2384
[ 630.521908] ispif_process_irq: PIX0 frame id: 2385
[ 630.555239] ispif_process_irq: PIX0 frame id: 2386
[ 630.587439] ispif_process_irq: PIX0 frame id: 2387
When closing camera app, re-opening, selfie is working but following trace :
Code:
[ 520.236493] type=1400 audit(1646511832.307:2918): avc: denied { read } for comm="HwBinder:832_2" name="u:object_r:bootanim_system_prop:s0" dev="tmpfs" ino=13144 scontext=u:r:hal_camera_default:s0 tcontext=u:object_r:bootanim_system_prop:s0 tclass=file permissive=0
[ 520.238093] type=1400 audit(1646511832.307:2919): avc: denied { read } for comm="HwBinder:832_2" name="u:object_r:default_prop:s0" dev="tmpfs" ino=13201 scontext=u:r:hal_camera_default:s0 tcontext=u:object_r:default_prop:s0 tclass=file permissive=0
[ 520.238408] type=1400 audit(1646511832.307:2920): avc: denied { read } for comm="HwBinder:832_2" name="u:object_r:default_prop:s0" dev="tmpfs" ino=13201 scontext=u:r:hal_camera_default:s0 tcontext=u:object_r:default_prop:s0 tclass=file permissive=0
[ 520.252543] PU: mGpioCnt[4]: 1
[ 520.263611] PU: mGpioCnt[5]: 1
[ 520.290503] msm_cci_init:1439: hw_version = 0x10060000
[ 520.291319] msm_sensor_match_id CAM_ID_8M: 0
[ 520.362722] msm_csid_irq CSID2_IRQ_STATUS_ADDR = 0x800
Had a issue on first boot after flash :
- top menu was not acessible (nothing when pulling down)
- only back button was showing on the "virtual button" down
Fixed after a reboot.
You mind sharing your build configs? You are rolling this kernel : https://github.com/luk1337/android_kernel_sony_sdm660/tree/lineage-19.0
With main branch 19.0 of lineage official repo ?

lecler_i said:
You mind sharing your build configs? You are rolling this kernel : https://github.com/luk1337/android_kernel_sony_sdm660/tree/lineage-19.0
With main branch 19.0 of lineage official repo ?
Click to expand...
Click to collapse
Everything you need is either on my github, LineageOS github/gerrit, or TheMuppets.

Hi
Thx for making Android 12 possible on my XA2
Anyway i somehow cant connect properly to wifi!
So i logged into my wifi in the setup (I installed NikGapps) but even tho he says "Connected" he doesnt let me go to the second step of setup. I already tried different Wlans but still nothing.
Hope someone can help me.

Try BiTGApps

Hello
Just installed the latest version available (19.1 - 26/03) and it worked fine. The problem is that, when I went to TWRR to flash gapps, TWRP did not ask for the device encryption password and thus it did not work. I don't know how to proceed.

Ok so I installed the latest version and installed NikGapps through lineage recovery. It works indeed!
Tested:
SIM and SMS
WiFi
Camera
Gapps (I had some problems with Bromite System Webview but disabling the module solved it)
Torch
Location
Cell data
Magisk canary
I miss an option to select the system accent instead of the adaptive one that selects it based on the wallpaper, but everything else is fine.
TWRP still does not ask for a pin and the data keeps encrypted so it is not usable, but as I said flashing through lineage recovery works (at least for gapps)

Does SMSs, Wi-Fi and other stuff work also without GApps or is it required to install it?
Is the ROM still under development?
Thank You in advance.

kereth said:
Does SMSs, Wi-Fi and other stuff work also without GApps or is it required to install it?
Is the ROM still under development?
Thank You in advance.
Click to expand...
Click to collapse
Everything you asked for works absolutely fine without any issues.
You don't need gApps for that.
I can't say how active the developers are, but an update was released just yesterday (16.04)
Thanks a lot @LuK1337

Should I clean flash updates or can I dirty flash them without losing any data?

Now that LineageOS 19 is officially out, will this thread be converted to one for the official build or will there be a separate thread that we have to join?

Don't know about you guys but I have a mixed feeling about the theming in Android 12. Anyone know if there is a way to choose the colour I want the system to use like we had in the previous versions?

@LuK1337
LOS 19.1... Great ROM, and now it's official. Have many thanks for that!!
One (first?) question:
I see, the camera app has changed from former snap-camera to standard android-camera now. How can I switch this camera into silent mode? I can't find any switch for that.
Or, is it possible to have snap-camera even in LOS 19.1, as in former LOS-releases?
Thanks a lot,
samhhmobil

k2helix said:
Should I clean flash updates or can I dirty flash them without losing any data?
Click to expand...
Click to collapse
I did an update from 18.1 and it surprisingly worked well, but it's not recommended to do.
I've got one issue with TWRP, but I don't know if this is related to my dirty flash or some issue with TWRP itself:
I've tried to update the second/other partition of the A/B, but on trying to boot to TWRP with fastboot command, TWRP does not recognize the encryption and shows weird folders and files.
I was using the latest version of TWRP (2.6.1_9)
@LuK1337 do you have any advice what I can try to make TWRP working again and recognize the encryption?
has anyone tried to go to TWRP after updating?

emc02 said:
I did an update from 18.1 and it surprisingly worked well, but it's not recommended to do.
I've got one issue with TWRP, but I don't know if this is related to my dirty flash or some issue with TWRP itself:
I've tried to update the second/other partition of the A/B, but on trying to boot to TWRP with fastboot command, TWRP does not recognize the encryption and shows weird folders and files.
I was using the latest version of TWRP (2.6.1_9)
@LuK1337 do you have any advice what I can try to make TWRP working again and recognize the encryption?
has anyone tried to go to TWRP after updating?
Click to expand...
Click to collapse
The version of twrp I last used is 3.5.1_9. This time I just used the LineageOS recovery.

malerocks said:
The version of twrp I last used is 3.5.1_9. This time I just used the LineageOS recovery.
Click to expand...
Click to collapse
ok, with 18.1 I had issues using the LOS recovery, so I flashed always with TWRP. But I've installed it now on the other partition with LOS recovery and it's working well.
So you think a normal OTA Update of LOS will work now out of the box?

Yes. I tried an OTA today and it went all fine. I never had issues with OTAs with the previous LineageOS version either.

emc02 said:
I've got one issue with TWRP, but I don't know if this is related to my dirty flash or some issue with TWRP itself:
I've tried to update the second/other partition of the A/B, but on trying to boot to TWRP with fastboot command, TWRP does not recognize the encryption and shows weird folders and files.
I was using the latest version of TWRP (2.6.1_9)
[...]Has anyone tried to go to TWRP after updating?
Click to expand...
Click to collapse
You're right, since installing LOS 19.1, TWRP (even the newest one, but the older ones too) cannot decrypt the user data.
samhhmobil

Question ERROR: Reconcile failed: Package com.asus.atd.smmitest has no signatures that match those in shared user android.uid.system; ignoring!]

HI
does anybody know how to get rid of this error:
Code:
1|ASUS_I006D:/sdcard/Download # id
uid=0(root) gid=0(root) groups=0(root) context=u:r:magisk:s0
ASUS_I006D:/sdcard/Download # pm install $PWD/SMMI_TEST.apk
avc: denied { read } for scontext=u:r:system_server:s0 tcontext=u:object_r:fuse:s0 tclass=file permissive=1
Failure [INSTALL_FAILED_SHARED_USER_INCOMPATIBLE: Reconciliation failed...: Reconcile failed: Package com.asus.atd.smmitest has no signatures that match those in shared user android.uid.system; ignoring!]
1|ASUS_I006D:/sdcard/Download #
SMMI_TEST.apk is an app from the original Android for the ASUS Zenfone 8 and I want install it in OmniROM 12 .
regards
Bernd
Update 15.06.2022
Looks like this error can only be fixed by signing the app with the private key used in the running ROM
Update 22.06.2022
The test app works fine on a custom ROM if signed with the private key for that ROM (tested with a self compiled version of OmniROM 12)
Update 25.06.2022
"Resolved" by compiling my own CustomROM -- see How to use the Hardware Test App from ASUS on a Zenfone running a CustomROM
​

from AndroifManifest.xml remove android:sharedUserId="android.uid.system" from manifest

gothta said:
from AndroifManifest.xml remove android:sharedUserId="android.uid.system" from manifest
Click to expand...
Click to collapse
... without that permission the app can be executed but can not do anything anymore