Database Develop

[GUIDE CM11] How to build your own CyanogenMod 11.0 ROM from sources for the Nexus 4

Make your 'own' KitKat-ROM today!
V1.1 - 20131108 Update 1: Java part added. Error remarks. Local_manifest: branch update.
V1.0 - 20131106 Initial release
Thank you note: Thank you to the whole CM-Team for bringing up-to-date-Android to so many devices.
{
"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"
}
Overview
I. Preparation
II. Installation of the required packages
III. Installing Java
IV. The sources
V. Building the ROM
VI. Rebuilding with newest sources
I. Preparation
Things you need for building:
A computer
An internet connection
An open mind
Time
Patience
First of all, you need a running up-to-date Ubuntu/Linux system. I am using Ubuntu 13.10 64-bit.
Use the terminal to make the steps. A terminal window can be opened by pressing Ctrl+Alt+T. Every single command for the terminal is marked with a $ sign. Just paste every command (without the $ sign) to your terminal window and there shouldn't be any problem.
IMPORTANT: INSTALL EVERYTHING AS A NORMAL USER. DON'T INSTALL AS ROOT!
II. Installation of the required packages (Ubuntu 13.10 64-bit)
Install packages:
Code:
$ sudo apt-get install bison build-essential curl flex \
g++-multilib gcc-multilib git-core gnupg gperf \
lib32ncurses5-dev lib32readline-gplv2-dev lib32z1-dev \
libesd0-dev libncurses5-dev libsdl1.2-dev \
libwxgtk2.8-dev libxml2 libxml2-utils lzop \
openjdk-6-jdk openjdk-6-jre pngcrush schedtool \
squashfs-tools xsltproc zip zlib1g-dev
III. Installing Java
You need a version 6 Java Development Kit for building CM11.0. Usually, the SUN JDK 6 is recommended. But there is another way: you can use the OpenJDK 6. When you installed the required packages as described above, you will just need to configure your Java installation.
Check your Java version:
Code:
$ java -version
Verify the symlinks. Javac, Java, Javaws, Javadoc, Javah, Javap and Jar should all point to the right Java location and version:
Code:
$ ls -la /etc/alternatives/java* && ls -la /etc/alternatives/jar
If they are pointing to the wrong versions you have to change that to OpenJDK6.
Select the default Java version for your system:
Code:
$ sudo update-alternatives --config javac
$ sudo update-alternatives --config java
$ sudo update-alternatives --config javaws
$ sudo update-alternatives --config javadoc
$ sudo update-alternatives --config javah
$ sudo update-alternatives --config javap
$ sudo update-alternatives --config jar
That's it.
IV. The sources
Install repo:
Repo is a tool that makes it quite easy to download and maintain the sources of Cyanogenmod.
Code:
$ mkdir ~/bin
$ PATH=~/bin:$PATH
$ cd ~/bin
$ curl http://commondatastorage.googleapis.com/git-repo-downloads/repo > ~/bin/repo
$ chmod a+x ~/bin/repo
Create the working directory:
Code:
$ mkdir ~/cm11
$ cd ~/cm11
Initialize Repo:
Code:
$ repo init -u git://github.com/CyanogenMod/android.git -b cm-11.0
and enter your credentials.
Download the sources:
Code:
$ repo sync
Wait until it's finished - takes some time to download the hefty 12 GB of source code!
Have a break, have a KitKat!
If the process hangs use Ctrl+C to break out of it and resume the download with another
Code:
$ repo sync
If you are running into a lot of syncing errors the reason might be that the 'repo sync' command is establishing four threads automatically. This might be too much. So try to change the command to run with one thread only by using
Code:
$ repo sync -j1
Initialize the environment
Code:
$ . build/envsetup.sh
Obtain the proprietary files:
First get two missing repositories for the Nexus 4 by running
Code:
$ breakfast mako
Then create a file with the name local_manifest.xml in the local_manifests directory. To see this directory, you have to press Ctrl-H in your file manager.
Use this code
Code:
$ gedit ~/cm11/.repo/local_manifests/local_manifest.xml
Update: Branch revision is now cm-11.0
Paste the following lines to the editor
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="TheMuppets/proprietary_vendor_lge.git" path="vendor/lge" remote="github" revision="cm-11.0"/>
</manifest>
Save the file.
Run
Code:
$ repo sync
again to get the files needed.
Download the necessary prebuilts from cyanogenmod by running
Code:
$ cd ~/cm11/vendor/cm
$ . get-prebuilts
$ croot
And you're done!
V. Building the ROM
Now build it:
Code:
$ brunch mako
And the building process starts. Now have patience. Building takes around half an hour on fast systems and a lot more on older and slower machines.
Update 20131108: The errors from 20131106 are gone now. If you made the changes revert them, sync the repo and then brunch again. There is no need to edit the source at the moment.
YOU ONLY NEED THIS PART IF YOU WANT TO REVERT THE CHANGES YOU MADE BEFORE
As of writing, you will run into two errors:
First error you will encounter:
Code:
build/core/java.mk:23: *** frameworks/support/v4:
Invalid LOCAL_SDK_VERSION '19' Choices are: current 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18. Stop.
Go to frameworks/support/v4/Android.mk and edit line 128 (it's at the end of the file):
Look for
Code:
# A helper sub-library that makes direct use of KitKat APIs.
include $(CLEAR_VARS)
LOCAL_MODULE := android-support-v4-kitkat
LOCAL_SDK_VERSION := [COLOR=DarkRed]19[/COLOR]
and change the "19" to "current"
It should look like this
Code:
# A helper sub-library that makes direct use of KitKat APIs.
include $(CLEAR_VARS)
LOCAL_MODULE := android-support-v4-kitkat
LOCAL_SDK_VERSION := [COLOR=DarkRed]current[/COLOR]
Save the file.
Re-run
Code:
$ brunch mako
The second error you will see:
Code:
build/core/java.mk:23: *** packages/apps/Launcher3:
Invalid LOCAL_SDK_VERSION '19' Choices are: current 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18. Stop.
Go to packages/apps/Launcher3/Android.mk and edit line 35 (it's in the middle of the file):
Look for
Code:
LOCAL_PROTOC_OPTIMIZE_TYPE := nano
LOCAL_PROTOC_FLAGS := --proto_path=$(LOCAL_PATH)/protos/
LOCAL_SDK_VERSION := [COLOR=DarkRed]19[/COLOR]
LOCAL_PACKAGE_NAME := Launcher3
and change the "19" to "current"
It should look like this
Code:
LOCAL_PROTOC_OPTIMIZE_TYPE := nano
LOCAL_PROTOC_FLAGS := --proto_path=$(LOCAL_PATH)/protos/
LOCAL_SDK_VERSION := [COLOR=DarkRed]current[/COLOR]
LOCAL_PACKAGE_NAME := Launcher3
Save the file.
Re-run
Code:
$ brunch mako
-END OF THE OLD ERROR CORRECTION-
When everything worked as it should you will find your new ROM-image in ~/cm11/out/target/product/mako
It is called cm-11-DATE-UNOFFICIAL-mako-zip. You can flash it via CWM/TWRP as usual.
VI. Rebuilding with newest sources
Whenever you like to update your sources and build a new version you have to run these four simple commands:
Code:
$ cd ~/cm11
$ repo sync
$ . build/envsetup.sh
$ brunch mako
Compiling takes less time than it took for creating the ROM the first time because it's only building new parts while reusing old parts that haven't changed.
Happy building!

Reserved
Reserved

Nice Tutorial, thank you for the work :good:
Now i have to organize a linux-computer... :/
edited to linux, my brain is out of order today...

Thank you for your post. I knew how to compile but I was lazy to compile for myself any rom until now. I planned to wait until someone will post it, but your post just got me excited and I will compile.
Thank you for your instructions and all. Good luck!

This is what I keep getting...
[email protected]:~/cm11$ repo init -u git://github.com/CyanogenMod/android.git -b cm-11.0
bash: /home/bruce/bin/repo: Permission denied

B4tnam said:
[email protected]:~/cm11$ repo init -u git://github.com/CyanogenMod/android.git -b cm-11.0
bash: /home/bruce/bin/repo: Permission denied
Click to expand...
Click to collapse
try chmod a+x /home/bruce/bin/repo

hansichen123 said:
Nice Tutorial, thank you for the work :good:
Now i have to organize a linux-computer... :/
Gesendet von meinem Transformer Pad mit Tapatalk 4
edited to linux, my brain is out of order today...
Click to expand...
Click to collapse
If you have a quite new PC running Windows, you could use a virtual machine to install Linux ontop of your Windows installation. Have a look at VirtualBox for example. It's free. https://www.virtualbox.org/

@Raum1807 How's cm11? What features have been implemented so far?

B4tnam said:
[email protected]:~/cm11$ repo init -u git://github.com/CyanogenMod/android.git -b cm-11.0
bash: /home/bruce/bin/repo: Permission denied
Click to expand...
Click to collapse
Of course, because you didn't hit the thanks button. (joking, but of course, just press it now)
Your problem is with folder permissions. I don't know how you created the folders but somehow you just don't have enough permisions now.
Try to:
chmod a+x /home/bruce/bin/repo

Bah my linux box broke.. @op Can you release the cm11 build you made?
Sent from my AOSP on Mako using Tapatalk

Imperticus said:
@Raum1807 How's cm11? What features have been implemented so far?
Click to expand...
Click to collapse
It's work in progress... :fingers-crossed:
It's actually very nice. A bit rough around the corners at the moment... But since KitKat is just a few days old, the progress right now is already fantastic compared to last year's Android 4.2-Release. I am looking forward to the days after the M2 release of CM10.2 when most of the devs will focus on CM11.0. Everything is mostly in English, but the handling is very smooth and my short test didn't reveal anything as not working.
Oh, and a printing feature has been implemented (not tested), new launcher is coming (Launcher 3), etc.
Looks very promising!

Remember guys if you try this that you can't use the ART compiler with De-Odexed GApps, so you will have to use PA GApps instead.

Raum1807 said:
It's work in progress... :fingers-crossed:
It's actually very nice. A bit rough around the corners at the moment... But since KitKat is just a few days old, the progress right now is already fantastic compared to last year's Android 4.2-Release. I am looking forward to the days after the M2 release of CM10.2 when most of the devs will focus on CM11.0. Everything is mostly in English, but the handling is very smooth and my short test didn't reveal anything as not working.
Oh, and a printing feature has been implemented (not tested), new launcher is coming (Launcher 3), etc.
Looks very promising!
Click to expand...
Click to collapse
looks great. printing is part of 4.4 not CM
can you check if compass is working?

cobhc said:
Remember guys if you try this that you can't use the ART compiler with De-Odexed GApps, so you will have to use PA GApps instead.
Click to expand...
Click to collapse
Right! Thanks. Forgot to post it.
The PA-GAPPS (FULL COMPLETE PACKAGE) from yesterday is what I was using with my test-build.
http://forum.xda-developers.com/showthread.php?t=2397942
Look for Download-Link under
Full Complete Package ~201MB
then for
pa_gapps-full-4.4-20131105b-signed.zip

Imperticus said:
looks great. printing is part of 4.4 not CM
can you check if compass is working?
Click to expand...
Click to collapse
Maps was working; GPS signal was fast and precise. But I must admit that I haven't tested the compass function while in maps...

Dang!! Now I can't wait to get out of work and try this. I've never compiled my own ROM before, but I'm looking forward to trying it with your instructions. I have full backups of my phone right now in case I blow it up. Will need to fire up Virtual Box, as one commenter pointed out. Good idea

Could this work with other phones? Assuming we use the correct device specific calls

Raum1807 said:
Right! Thanks. Forgot to post it.
The PA-GAPPS (FULL COMPLETE PACKAGE) from yesterday is what I was using with my test-build.
http://forum.xda-developers.com/showthread.php?t=2397942
Look for Download-Link under
Full Complete Package ~201MB
then for
pa_gapps-full-4.4-20131105b-signed.zip
Click to expand...
Click to collapse
I said that, then the build I tried from Dev-Host still FC's with the PA GApps you linked and the ART compiler :S

cobhc said:
I said that, then the build I tried from Dev-Host still FC's with the PA GApps you linked and the ART compiler :S
Click to expand...
Click to collapse
pa gapps are deodexed. you need odex gapps to work with ART. Use this - http://d-h.st/8PP

cobhc said:
Remember guys if you try this that you can't use the ART compiler with De-Odexed GApps, so you will have to use PA GApps instead.
Click to expand...
Click to collapse
PA Odexed GApps?
edit: user above answered my question

Collection of official CyanogenMod boot animations

This thread is to build up a collection of all official CyanogenMod boot animations at all available resolutions. If you come across any more animations or resolutions, please post them in the thread and I will update this post to include them (if they are legit).
To backup the existing boot animation, copy /system/media/bootanimation.zip (on the device) to somewhere.
To restore it, or replace it with a new boot animation, copy the desired bootanimation.zip from the source location to /system/media/bootanimation.zip and make sure that /system/media/bootanimation.zip has these permissions:
Code:
Owner: root
Group: root
S R W X
Owner: [ ] [X] [X] [ ]
Group: [ ] [X] [ ] [ ]
Others: [ ] [X] [ ] [ ]
NOTE: You will need to have root access to replace /system/media/bootanimation.zip.
CyanogenMod 12
1440x2560: bootanimation.zip
Click to expand...
Click to collapse
CyanogenMod 11
???
Click to expand...
Click to collapse
CyanogenMod 10
???
Click to expand...
Click to collapse
CyanogenMod 9
800x1280: bootanimation.zip
Click to expand...
Click to collapse
CyanogenMod 8
???
Click to expand...
Click to collapse
CyanogenMod 7
960x960: bootanimation.zip
Click to expand...
Click to collapse
CyanogenMod 6
???
Click to expand...
Click to collapse

I'm also not sure what the boot animations for versions of CyanogenMod earlier than CM6 were. If someone could enlighten me on that I'd be grateful.

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