Database Users

bugs with SHV-E210K build (i9300 variant)

I have Omni booting and running on a E210K (It is a SGS3 Korean variant, only changes are LTE, 2GB and DMB antenna), but some major bugs need fixing. There not much if any device trees for these out there so I have just been modifying the i9300 and it works.
These are probably the major two issues I have for now:
1. without manually adding ro.zygote.disable_gl_preload=1 to the build prop, it won't boot. I noticed this line wasn't in the i9300 builds either, but it's definitely referenced in my builds:
/android/omni/device/samsung/smdk4412-common/common.mk
# Set default USB interface
PRODUCT_DEFAULT_PROPERTY_OVERRIDES += \
persist.sys.usb.config=mtp \
ro.zygote.disable_gl_preload=true
Click to expand...
Click to collapse
2. Can't adjust the vibration in advanced settings, when I do I get the logcat message below, there is no (very light) feedback because it seems the value is set very low.
If I manually edit the values (by putting it up to 10+) I can get feedback, so it is working.
Code:
I/ActivityManager( 2466): Displayed org.omnirom.device/.DeviceSettings: +428ms
W/DeviceSettings_Utils_Read( 5375): file /sys/vibrator/pwm_val: 2
W/DeviceSettings_Utils( 5375): file /sys/vibrator/pwm_val not found: java.io.FileNotFoundException: /sys/vibrator/pwm_val: open failed: EACCES (Permission denied)
W/DeviceSettings_Haptic( 5375): key: vibrator_tuning
but I have no idea where/how to proceed.
My device tree is up over at:
https://github.com/kaijura/android_device_samsung_e210k
I am using the same omni sources for smdk4412-common and kernel.
Thanks in advance

kaijura said:
I have Omni booting and running on a E210K (It is a SGS3 Korean variant, only changes are LTE, 2GB and DMB antenna), but some major bugs need fixing. There not much if any device trees for these out there so I have just been modifying the i9300 and it works.
These are probably the major two issues I have for now:
1. without manually adding ro.zygote.disable_gl_preload=1 to the build prop, it won't boot. I noticed this line wasn't in the i9300 builds either, but it's definitely referenced in my builds:
2. Can't adjust the vibration in advanced settings, when I do I get the logcat message below, there is no (very light) feedback because it seems the value is set very low.
If I manually edit the values (by putting it up to 10+) I can get feedback, so it is working.
Code:
I/ActivityManager( 2466): Displayed org.omnirom.device/.DeviceSettings: +428ms
W/DeviceSettings_Utils_Read( 5375): file /sys/vibrator/pwm_val: 2
W/DeviceSettings_Utils( 5375): file /sys/vibrator/pwm_val not found: java.io.FileNotFoundException: /sys/vibrator/pwm_val: open failed: EACCES (Permission denied)
W/DeviceSettings_Haptic( 5375): key: vibrator_tuning
but I have no idea where/how to proceed.
My device tree is up over at:
https://github.com/kaijura/android_device_samsung_e210k
I am using the same omni sources for smdk4412-common and kernel.
Thanks in advance
Click to expand...
Click to collapse
LTE screams "qcom modem" to me - perhaps look at the i9305 tree?

Figured it out, for anyone searching for this problem - the issue has to do with the ramdisk portion of a (custom) kernel as it wasn't matching up omni's init setups.
Entropy512 said:
LTE screams "qcom modem" to me - perhaps look at the i9305 tree?
Click to expand...
Click to collapse
Tried a i9305 build it was a little worse off (no mobile connection), haha. I'm thinking of submitting for an official build after I figure out the build for a working stock omni kernel.
Since this device gets few attention (maybe less than 50 in the sgs3 forum) is it possible that you guys could set the jenkins buildbot to build like every week or other week?

kaijura said:
Figured it out, for anyone searching for this problem - the issue has to do with the ramdisk portion of a (custom) kernel as it wasn't matching up omni's init setups.
Tried a i9305 build it was a little worse off (no mobile connection), haha. I'm thinking of submitting for an official build after I figure out the build for a working stock omni kernel.
Since this device gets few attention (maybe less than 50 in the sgs3 forum) is it possible that you guys could set the jenkins buildbot to build like every week or other week?
Click to expand...
Click to collapse
Hmm, that might be a possibility...

kaijura said:
I have Omni booting and running on a E210K (It is a SGS3 Korean variant, only changes are LTE, 2GB and DMB antenna), but some major bugs need fixing. There not much if any device trees for these out there so I have just been modifying the i9300 and it works.
These are probably the major two issues I have for now:
1. without manually adding ro.zygote.disable_gl_preload=1 to the build prop, it won't boot. I noticed this line wasn't in the i9300 builds either, but it's definitely referenced in my builds:
2. Can't adjust the vibration in advanced settings, when I do I get the logcat message below, there is no (very light) feedback because it seems the value is set very low.
If I manually edit the values (by putting it up to 10+) I can get feedback, so it is working.
Code:
I/ActivityManager( 2466): Displayed org.omnirom.device/.DeviceSettings: +428ms
W/DeviceSettings_Utils_Read( 5375): file /sys/vibrator/pwm_val: 2
W/DeviceSettings_Utils( 5375): file /sys/vibrator/pwm_val not found: java.io.FileNotFoundException: /sys/vibrator/pwm_val: open failed: EACCES (Permission denied)
W/DeviceSettings_Haptic( 5375): key: vibrator_tuning
but I have no idea where/how to proceed.
My device tree is up over at:
https://github.com/kaijura/android_device_samsung_e210k
I am using the same omni sources for smdk4412-common and kernel.
Thanks in advance
Click to expand...
Click to collapse
This says u r building a rom.Is it working fine?
thanks

[DISCONTINUED][ROM][UNOFFICIAL][UBERTC/linaro]nvertigo-cm-12.1 for SM-T800 16gb

Bad news: this build is discontinued.
Good news: lineageos is comming to chagallwifi. @Paulicat from TeamExynos5420 is doing a great job: https://forum.xda-developers.com/ga...m-lineageos-14-1-sm-t700-t800-coming-t3535159
CU, Nvertigo
I do not do any further builds of this rom. But thanx to @ristokoo - who is not just talking, but taking action - and thanx to @deadman96385, who will commit future fixes - the rom is carried on. For the most current builds look at the last pages of this thread for @ristokoo's builds. Since @ristokoo has no working build-environment, I'll provode you with security fixes and - propably - monthly updates. Many, many Thanx to @ristokoo for his time, dedication and support!
IMPORTANT: from build 201151118 on it is mandatory to use a Lollopop boot loader!!! You can check your bootloader version in a rooted shell (adb shell or terminal): "getprop ro.boot.bootloader" the third last digit has to be "O". A odin flashable tar for BOJ1 can be found here.
Please refer to posting #3 on how to report an issue.
IMPORTANT: netflix does NOT show HD content for the most devices. For detailed information refer to this posting.
I consider the builds from 20151112 on as non-beta and stable.
Don't expect nightlys. I'm planing one build per 10 - 14 days. @lionheartk is pushing upstream updated builds from time to time. You can find them in the thread when he publishs them - so read the thread. When hunting down an issue or implementing new features, I will push test-builds in the thread - not here in OP.
CyanogenMod (pronounced /saɪ.'æn.oʊ.dʒɛn.mɒd/) is an enhanced open source firmware distribution for smartphones and tablet computers based on the Android mobile operating system. It offers features and options not found in the official firmware distributed by vendors of these devices.
http://wiki.cyanogenmod.org/w/About
Code:
#include
/*
* Your warranty is now void.
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
*/
Credits
@Barracuda77777 (without his contributitions and encouragement there would be no cm11 rom. He alone saved me from loosing myself in source code! Whenever I got stuck he came up with the brilliant change or the day saving idea. Thank you, brother!)
@UpInTheAir (most of the code changes in the kernel from the last 10 days before Christmas are from his SkyHigh kernel. He let me use his code, and most important: he explained with endless patience to me what I was doing... To reflect this the default branch of our kernel is no longer cm-11.0 but cm-11.0-sh [sh for small sister of SkyHigh]. Thank you, mate!
@crpalmer (for picassowifi device and kernel gits - the base @Barracuda77777 and me sstarted of from)
@eousphoros (for his device git: the base for @crpalmers work)
@lionheartk for providing twice-a-weak-builds.
@diegocr for getting rid of repackrom.
@deadman96385 for the kernel source from build 20151118 on.
@halaszk88, @faux123 and all the others I forgot
Unique Features
Features not to find in cm at the moment:
sswap support (using sswap binary for utilizing the swap partion of chagallwifi)
init.d support
modulized kernel and module loading support through init.d script 01moduleload
Known Issues
MHL has no sound and wrong colors
If you map MENU to a capacitive key (no matter if key itself or "long press", it will not work - workaround: do not map MENU to anything at all, then the apps are forced to show action overflow menu (aks 3 dot menu) - works on some apps (i.e. bootloguptime) on others not.
Some minor crackling when using bt-audio the same time as 2.4GHz wlan (5Ghz wlan is issue free).
No real issue, but a not currently supported feature: no onscreen navbar. If you want it - no problem: This is your chance to give something to the community!!! Untill you fixed it, you can use this untested workaround
YOU tell us...
Before reporting issues install the most recent release, read the thread and in doubt do a clean flash. For reporting an issue, please read posting number three
Installation
I recommend official twrp3 build from http://forum.xda-developers.com/showpost.php?p=65594033&postcount=315
Do a nandroid backup (and try at least once a restore to be sure it works - reboot to recovery in between backup and restore)
Download the flashable zip and check md5 checksum
read thread (reread postings 1 to 5)
Always do a "clean flash" as described in posting #2 (if you are already on my cm12 rom you can try a "dirty flash" as described in #2 - if you come from any other rom "clean flash" is mandatory!)
(optional: flash gapps)
Recomended
Third party installations of busybox may affect rom; read this.
opengapps: opengapps.org. I use the nano package for arm, version 5.1, from 20151129 (newer may work - but 1129 is proofed to work, as 0304 - for example - is proofed to be an issue).
On Xposed
Xposed is not supported in this thread: xposed changes systemfiles, so the resulting system is not the origin rom any longer. I don't want to discourage anybody from using xposed with this rom: if everything works, you are fine. If issues occur, clean flash with only gapps installed and reproduce the issue.
Source code
Device: https://github.com/nvertigo/android_device_samsung_chagallwifi
Kernel: https://github.com/nvertigo/android_kernel_samsung_chagallwifi
Binaries: https://github.com/nvertigo/android_vendor_samsung_chagallwifi
Standard build branch is current-12.1.
(Due to heavy work in progress git repositories are not always up to date.)
WARNING: try to not ask already answered questions - this will lead to bad karma, which leads to unwanted side-effects in your life. Kidding, of course - but really try to read the thread.
Changlog and Download
Mirrors are welcome. Thank you in advance!
For cm-12 upstream changelog please consult: http://www.cmxlog.com/12/#
Build 20161118
Fixed Zygote whitelist after the patchup from android security bullentin.
Build with UBERTC/linaro toolchains instead of aosp's stock toolchains.
ROM: https://www.androidfilehost.com/?fid=457095661767116515
MD5: f1a68ffce9144ecb9582a3deea61286d
History
Build 20160123
No changes in device-tree and kernel - just a maintain-release with all the cm changes (12:00 h GMT).
ROM: link follows, as soon as upload has finished.
MD5: b65a084022752fd753ac5286b7085352
Build 20160113
Changelog:
Double tap to wake: fix settings. — nvertigo
BoardConfig.mk: enable BOARD_HARDWARE_CLASS. — nvertigo
powerhal: enable wake_gesture when screen switches off, and disable wake_gesture when screen switches on. — nvertigo
CMHW: Add Double Tap to Wake support (1/2) — Sean Hoyt
Switch to software h264 decoding — Sean Hoyt
kernel: use [email protected]'s deathly kernel again. — nvertigo
proprietary-files.txt: not maintained, therefore extract-files.sh and setup-makefiles.sh are needless. — nvertigo
cm.dependencies: removed; doesn't work with UNOFFICIAL builds. — nvertigo
sepolicy: allow netd module_request and fsetid. — nvertigo
sepolicy: allow hostapd searching in efs_file:dir. — nvertigo
fstab: add length for encryptable footer. — nvertigo
device.mk: fix PRODUCT_AAPT_CONFIG, this should not contain dpi keywords. — nvertigo
CMHW: Add Double Tap to Wake support (2/2
changed to cyanogenmod_chagallwifi_defconfig. — nvertigo
power_profile: Correct values from stock rom — Schischu
Inform vendor/cm that BFQ is in use — Sam Mortimer
synaptics_dsx: Add double tap to wake support — Schischu
chagallwifi: add IKCONFIG and IKCONFIG_PROC as module. — nvertigo
synaptics_dsx: Add double tap to wake support — Schischu
chagallwifi: add support for /proc/config.gz — Sean hoyt
tc300k: Fix blinking of capacitive buttons — Schischu
ROM: https://www.androidfilehost.com/?fid=24369303960684813
MD5: 4b7a25fd16e9c11bf8f73d2f2bf4da3b
Mirror:
https://github.com/nvertigo/android...-20160113-UNOFFICIAL-nvertigo-chagallwifi.zip
Happy Flashing!
Build 20151118
IMPORTANT: from build 201151118 on it is mandatory to use a Lollopop boot loader!!! You can check your bootloader version in a rooted shell (adb shell or terminal): "getprop ro.boot.bootloader" the third last digit has to be "O". A odin --flashable tar for BOJ1 can be found here.
Also I strongly recomend a clean flash this time - sorry, folks.
Changelog:
Changed kernel source: this rom comes with deathly kernel from @deadman96385 (Thanx, dude!).
Changed kernel graphics driver f-rom t6xx to midgard.
Updated mali blobs to Lollipop.-
Fixed missing selinux domains for macloader and sswap.
If you expirience bt-audo issues, when using 2.4GHz wlan at the same time, you can try flashing an other audio_policy.conf from here. Depending on your bt-audio-device, time of day, moonphase and humidity one or an other will give better results.
ROM: http://charlesingo.mine.nu/ftp/nvertigo/cm-12.1-20151118-UNOFFICIAL-nvertigo-chagallwifi.zip
MD5: http://charlesingo.mine.nu/ftp/nvertigo/cm-12.1-20151118-UNOFFICIAL-nvertigo-chagallwifi.zip.md5sum
Mirror:
https://www.androidfilehost.com/?fid=24269982086999228 Thanx to @diegocr
http://forum.xda-developers.com/showpost.php?p=63903074&postcount=1617 Thanx to Hannibal226
Mirroring is welcome! Please use Mirror as soon as availible - I'm running out of data volume on my download host!
Happy flashing!
Build 20151113
I'm quite proud to call this build the first non-beta, stable release. As I can tell from the user testing of the last test builds, this is the most reliable, media compatible and nearly issue free combination of the configurations we tested. it has chagalls native kitkat mali blobs. Most of the other blobs are from kitkat, too - only wifi-, bt- and widevine blobs are lollipop. I reverted the introduction od lollipop OMX-blobs, 'cause the lollipop ones were introducing some small issues with media playback.
If you expirience bt-audo issues, when using 2.4GHz wlan at the same time, you can try flashing an other audio_policy.conf from here. Depending on your bt-audio-device, time of day, moonphase and humidity one or an other will give better results.
Changelog:
Update mali blobs to native chagall version.
BoardConfig.mk: derp: fix wrong path. — nvertigo (HEAD -> 121-work
Boardconfig.mk: updated graphics and FIMGAPI settings. — nvertigo
cm.mk: remove \ from last line. — nvertigo
Update to BOJ1: wifi and bluetooth. See also the changes in the vendor-git. — nvertigo
audio: desabled offloading again; makes things worse. — nvertigo
add 48k sampling rate for a2dp — Franco Rapetti
audio: added audio offload. Idea from cm's i9500 git. — nvertigo
BoardConfig.mk: cleanup and beautyfy. — nvertigo
Revert "audio_policy.conf: update from N9005." — nvertigo
Disable journaling on system image for save space — nexor (nvertigo/current-12.1, current-12.1
audio: Fix ril log tag. — Andreas Schneider
hal: audio: Match HAL function prototypes. — Andreas Schneider
Various storage fixes — Sinisa (thermskin
fstab.universal5420: fix vold warnings — Sinisa (thermskin
device.mk: Add permissions for bluetooth and voip — Andrew Tarabaras
Add firmware path for Station, fixes wifi hotspot — Andrew Tarabaras
patches: adjusted OMX-google-ffmpeg.diff to upstream. — nvertigo
audio_policy.conf: update from N9005. — nvertigo
patches: adjusted OMX-google-ffmpeg.diff to upstream changes. — nvertigo
rootdir/etc/fstab.universal5420: enabled the additional use of f2fs for /cache and /data. From [email protected] — nvertigo
ROM: http://charlesingo.mine.nu/ftp/nvertigo/cm-12.1-20151112-UNOFFICIAL-nvertigo-chagallwifi.zip
MD5: http://charlesingo.mine.nu/ftp/nvertigo/cm-12.1-20151112-UNOFFICIAL-nvertigo-chagallwifi.zip.md5sum
Mirror:
http://forum.xda-developers.com/showpost.php?p=63820133&postcount=1594 Thanx to @Hannibal226
Happy Flashing!
Build 20150413
Updated from cm-12.0 to cm-12.1 - cm-12.1 is based on AOSP 5.1. Remeber to update your gapps package to 5.1. I recommend pa gapps pico: http://forum.xda-developers.com/paranoid-android/general/5-1-x-5-0-x-4-4-x-pa-gapps-mirror-t3069879
ROM: http://162.220.240.98/ftp/nvertigo/cm-12.1-20150413-UNOFFICIAL-nvertigo-chagallwifi.zip
MD5: bdc8dc0937ac7416bad5314a45896719#
Mirrors:
http://forum.xda-developers.com/showpost.php?p=60089014&postcount=893 Thanx to @Hannibal226
Build 20150331
Another sepolicy fix allows the cm-12.0 bootanimation to show up immidietly on boot. ccode is reverted to 00.
Changlog:
sepolicy: allow surfacflinger to add Exynos.HWCService. — Nvertigo
chagallwifi: init: Do not override init.rc! — Christopher R. Palmer
chagallwifi: init: Remove reference to init.recovery.universal5420.usb.rc — Christopher R. Palmer
Revert "Compile stock and Samsung MTPs together [AndreiLux]" — Nvertigo
Revert "enable CONFIG_USB_ANDROID_SAMSUNG_MTP again." — Nvertigo
Revert ccode to 00. — Nvertigo
ROM: http://charlesingo.mine.nu/ftp/nvertigo/cm-12-20150331-UNOFFICIAL-nvertigo-chagallwifi.zip
MD5: 7161aed1b89f7190702dc5abe77a6f18
Mirrors:
http://forum.xda-developers.com/showpost.php?p=59820711&postcount=806 thanx to @Hannibal226
Build 20150319
This build has a significant advantage: I fixed sepolicy in a way (see git for details), that it's NOT necessary any longer to flash @Chainfires SuperSU. Init.d is working right out of the box. Also Titanium has fixed its problems with cm's superuser. I have adjusted the OP accordingly, so I recommend you read OP again.
I also worked again on MTP and UMS: UMS is only working without problems, if you DON'T use move2sdvard, 'cause sdcard gets unmounted to present it as mass storage to the device on the other end of your usb-cable. BUT: MTP is presenting internal AND external memory WITH ALL DIRECTORIES and not only media containing directories - so you can use it at least on windows machines as substitute for UMS.
The kernel modifications I introduced with rhe seperate keenel are included in roms kernel, and I set ccode for 2.4GHz to EU.
Changelog:
wifi country code: set ccode to EU for 2.4GHz to enable channel 12 and 13. — Nvertigo
Revert "selinux: make init.d work again." — Nvertigo
sepolicy: allow debuggerd access to mali. — Nvertigo
sepolicy: vold: allow module_request. — Nvertigo
sepolicy: fix init.d support for 01moduleload and 10systemtuning. — Nvertigo
include/linux/sched.h: fix my derp from incomplete conflict resolving. — Nvertigo
defconfig: enable CONFIG_CRYPTO_AES_ARM_BS. — Nvertigo
defconfig: adjusted cyanogenmod_chagallwifi_defconfig after incorparating manta's 5.1 from exynos5420. — Nvertigo
for not in cm tree building: adjust CROSS_COMPILE; can be overwritten on command line. — Nvertigo
HID: input: generic hidinput_input_event handler — David Herrmann
net/compat.c,linux/filter.h: share compat_sock_fprog — Will Drewry
sk_run_filter: add BPF_S_ANC_SECCOMP_LD_W — Will Drewry
ARM: pull in <asm/simd.h> from asm-generic — Ard Biesheuvel
crypto: create generic version of ablk_helper — Ard Biesheuvel
ARM: 8120/1: crypto: sha512: add ARM NEON implementation — Jussi Kivilinna
ARM: 8119/1: crypto: sha1: add ARM NEON implementation — Jussi Kivilinna
ARM: 8118/1: crypto: sha1/make use of common SHA-1 structures — Jussi Kivilinna
crypto: arm-aes - fix encryption of unaligned data — Mikulas Patocka
CRYPTO: Fix more AES build errors — Russell King
ARM: add .gitignore entry for aesbs-core.S — Russell King
ARM: add support for bit sliced AES using NEON instructions — Ard Biesheuvel
ARM: move AES typedefs and function prototypes to separate header — Ard Biesheuvel
ARM: 7837/3: fix Thumb-2 bug in AES assembler code — Ard Biesheuvel
ARM: 7723/1: crypto: sha1-armv4-large.S: fix SP handling — Ard Biesheuvel
ARM: 7626/1: arm/crypto: Make asm SHA-1 and AES code Thumb-2 compatible — Dave Martin
arm/crypto: Add optimized AES and SHA1 routines — David McCullough
ARM: add seccomp syscall — Kees Cook
CHROMIUM: ARM: r1->r0 for get/set arguments — Will Drewry
CHROMIUM: ARM: arch/arm: allow a scno of -1 to not cause a SIGILL — Will Drewry
CHROMIUM: arch/arm: select HAVE_ARCH_SECCOMP_FILTER — Will Drewry
CHROMIUM: arch/arm: move secure_computing into trace; respect return code — Will Drewry
CHROMIUM: arch/arm: add asm/syscall.h — Will Drewry
cgroup: remove synchronize_rcu(
power: Avoids bogus error messages for the suspend aborts. — Ruchi Kandoi
freezer: shorten freezer sleep time using exponential backoff — Colin Cross
seccomp: Use atomic operations that are present in kernel 3.4. — Robert Sesek
seccomp: implement SECCOMP_FILTER_FLAG_TSYNC — Kees Cook
seccomp: allow mode setting across threads — Kees Cook
seccomp: introduce writer locking — Kees Cook
seccomp: split filter prep from check and apply — Kees Cook
sched: move no_new_privs into new atomic flags — Kees Cook
Fix execve behavior apparmor for PR_{GET,SET}_NO_NEW_PRIVS — John Johansen
seccomp: add "seccomp" syscall — Kees Cook
seccomp: split mode setting routines — Kees Cook
seccomp: extract check/assign mode helpers — Kees Cook
seccomp: create internal mode-setting function — Kees Cook
CHROMIUM: seccomp: set -ENOSYS if there is no tracer — Will Drewry
seccomp: fix build warnings when there is no CONFIG_SECCOMP_FILTER — Will Drewry
seccomp: ignore secure_computing return values — Will Drewry
seccomp: use a static inline for a function stub — Stephen Rothwell
ptrace,seccomp: Add PTRACE_SECCOMP support — Will Drewry
seccomp: Add SECCOMP_RET_TRAP — Will Drewry
signal, x86: add SIGSYS info and make it synchronous. — Will Drewry
seccomp: add SECCOMP_RET_ERRNO — Will Drewry
seccomp: remove duplicated failure logging — Kees Cook
seccomp: add system call filtering using BPF — Will Drewry
seccomp: kill the seccomp_t typedef — Will Drewry
arch/x86: add syscall_get_arch to syscall.h — Will Drewry
Add PR_{GET,SET}_NO_NEW_PRIVS to prevent execve from granting privs — Andy Lutomirski
prctl: adds PR_SET_TIMERSLACK_PID for setting timer slack of an arbitrary thread. — Ruchi Kandoi
mm: add a field to store names for private anonymous memory — Colin Cross
ROM: http://charlesingo.mine.nu/ftp/nvertigo/cm-12-20150319-UNOFFICIAL-nvertigo-chagallwifi.zip
MD5: d3164baca1f11987a61a306f87d7985f
Mirrors:
http://forum.xda-developers.com/showpost.php?p=59573116&postcount=693 Thanx to @Hannibal226
Build 20150310
fix vulnerability to FREAK attack in Browser.apk. Until cm (there are curtently two diffrent suggestions in gerrit to fix this) commits a fix, every rom builder can do this before brunching:
Code:
pushd external/chromium_org/third_party/openssl
git fetch http://review.cyanogenmod.org/CyanogenMod/android_external_chromium_org_third_party_openssl refs/changes/39/90739/1 && git cherry-pick FETCH_HEAD
popd
kernel: gone back a few steps (for details see git). After patching kernel to 3.4.106 and applying some additional commits, I hoped increasing speed and decreseaing battary usage, I realized in many loading cycles, that one or some of the additional commits slightly decrease battery life (the opposide of my intention) - so I removed them again. Sadly I have not the time to examine, which commit really did the bad. I will push the questionable commits in branch "questionable". Everybody can test which commit is the culprit patch. My gut feeling suggests the "squash 'enhanced power efficiency' patch" commit. I would be very thankful for help on testing, 'cause it's very time consuming. You need AT LEAST two complete recharging cycles to make an educated decission. Thanx in advance.
UMS mode: fix write acces to device.
ROM: http://charlesingo.mine.nu/ftp/nvertigo/cm-12-20150310-UNOFFICIAL-nvertigo-chagallwifi.zip
MD5: 77cc7bc67818f1251dcf295482fddd65
Mirrors:
http://forum.xda-developers.com/showpost.php?p=59363050&postcount=578 thanx to @Hannibal226
Build 20150305
Changed wifi countrycode back to 00 (rememner to adjust this to the country code your wifi router is operating in, if expirience wifi issues)
Updated f2fs driver
ROM: http://charlesingo.mine.nu/ftp/nvertigo/cm-12-20150305-UNOFFICIAL-nvertigo-chagallwifi.zip
MD5: 4229d8df0afd698fe0c10dfaed3327db
Mirrors:
http://forum.xda-developers.com/showpost.php?p=59253368&postcount=540 thanx to @Hannibal226
Build 20150228
KODI/XBMC and some games,no input issue solved.
Power off charging fixed.
Updated kernel to 3.4.106.
Cherry picked some effiziency changes from SkyHigh (thanx to @UpInTheAir
USB UMS mode fixed.
Added mdnie mode setting to init.d/10systemtuning. From: [email protected]
Make wifi 2.4GHz channel 12 (and perhaps channel 13) working again.
ROM: http://charlesingo.mine.nu/ftp/nvertigo/cm-12-20150228-UNOFFICIAL-nvertigo-chagallwifi.zip
MD5: e6ff3a48b31826cfc5c1e31211062e2e
Mirrors:
http://forum.xda-developers.com/showpost.php?p=59161974&postcount=501 thanx to @Retiredfinally
http://forum.xda-developers.com/showpost.php?p=59175868&postcount=507 thanx to @Hannibal226
http://forum.xda-developers.com/showpost.php?p=59179113&postcount=509 thanx to @Bantryred
Build 20150203
fix move to sd card. (*)— Nvertigo
fix power off charging (lpm charging) partly. (**) — Nvertigo
chagallwifi: sepolicy: Fix denial killing CM's SetupWizard — Christopher R. Palmer
chagallwifi: bluetooth: Fix audit denial — Christopher R. Palmer
sepolicy: fix gpsd: simplify file_contexts; restrict gpsd access to files to the required rights. — Nvertigo
chagallwifi: wifi: Switch to world regulatory domain. — Christopher R. Palmer
(*) Works even if wiping system to do a rom-flash, but be carefull: it takes time. If you have moved some apps to sdcard wait for 10 minutes or so after boot seems completed before logging in. On a test I was impatient and the apps seems to have gone from homescreen (nova) and appdrawer, but after a while they was back in app-drawer and I had to readd them to home screen. If waiting a bit before logging in, everything is in place.
Remember when apps are moved to sd, that a nandroid WILL NOT(!) INCLUDE THE MOVED APPS.
Not all apps are movable. If you move apps, that require root, you will be asked again to allow root (like you just reinstalled them).
(**) power off charging IS working. It charges and does not emergency reboot to recovery any longer. It even shows the sammy charging animation, BUT gpio keys (power, volume and home) do not work. So you can't reboot, while plugged in. You also can't switch on screen with animation again. If you want to reboot, plug off device, then the screen will come on with charging status. Wait til it goes black again, wait for three more seconds, and start your device normally with the power button.
This build is done from the 12-work branches of my three gits. I will push this status to current-12.0 soon.
ROM: http://charlesingo.mine.nu/ftp/nvertigo/cm-12-20150203-UNOFFICIAL-nvertigo-chagallwifi.zip
MD5: 2d0c5826ba5d2ba1d2f3761c5165664a
Build 20150128
fixed selinux for gps
fixed selinux for init.d support works only if you flash @Chainfire's SuperSU
ROM: http://charlesingo.mine.nu/ftp/nvertigo/cm-12-20150128-UNOFFICIAL-nvertigo-chagallwifi.zip
MD5: 36bc597e89be0af6233abf4f4824bc69
Build 20150125
fixed netflix
adjusted battary capacity to our 7900 mAH specs
all upstreammcommits till 20150125 18:00 h UTC
ROM: http://charlesingo.mine.nu/ftp/nvertigo/cm-12-20150125-UNOFFICIAL-nvertigo-chagallwifi.zip
MD5: ac0d1198c4100b407bcc46a01235c6c7
Build 20150123
Set selinux to permissive for now. This fixes: gps and init.d support. repo synced: 20:00 20150123 UTC.
ROM: http://charlesingo.mine.nu/ftp/nvertigo/cm-12-20150123-UNOFFICIAL-nvertigo-chagallwifi.zip
MD5: d5fc4388c383e9b8a5beb9aa67cde5e2
Build 20150121
ROM: http://charlesingo.mine.nu/ftp/nvertigo/cm-12-20150121-UNOFFICIAL-nvertigo-chagallwifi.zip
MD5: f2a0a10cd867b34a3d3107ef5640b9c8

Different ways of flashing
Very dirty flash:
flash rom
Dirty flash:
wipe system
wipe cache
wipe dalvik-cache
flash rom
flash gapps
Clean flash
factory reset in recovery - (without wiping /data/media) this resets your settings and deletes your installed apps
[optional for paranoids - 'cause it's done from installer-script in the process of flashing] wipe /system
wipe cache
wipe dalvik-cache
wipe data (without wiping /data/media) this resets your settings and deletes your installed apps
flash rom
flash gapps
Very clean flash
factory reset in recovery - (without wiping /data/media) this resets your settings and deletes your installed apps
[optional for paranoids - 'cause it's done from installer-script in the process of flashing] wipe /system
wipe cache
wipe dalvik-cache
wipe data (without wiping /data/media) this resets your settings and deletes your installed apps
wipe internal memory
flash rom
flash gapps
I recommend ALWAYS a "Clean flash", though myself I do many times "Dirty flash"es while testing. Whenever I run in issues, I reflash the "Clean flash" way. On the issues with Camera2 I even did "Very clean flash"es - to ensure no old data is interfering.
On many threads it is MANDATORY to have done a "Clean flash" before reporting issues. Not so here - and I want to leave it this way. But always ask yourself: how many times have I done a dirty flash? Have I tested and edited files? Is it time to "Clean flash"?
I count on users good judgment.

Reporting issues
Before you report an issue
Make sure you have installed the most current build.
Do a "clean flash" as described in posting #2 (do NOT flash xposed: it's not supported - see above #1). Dirty flashes are ok most of the time. But you can never know when "not most of the time" a dirty flash produces issues, so before repprting an issue it is mandatory to perform a "clean flash", just in case...
What an issue report should contain (at least)
The more detailed information is provided, the better I can iron it out. It's not possible for me to hunt down any issue that I can't reproduce or understand, the only way to undestand your issue and it's underlaying dynamic is a logcat. I don't know automagically all usecases of all users.
Detailed description of steps to reproduce the issue.
logcat, while reproducing the issue (as text)
I'll ignore all other reports, 'cause that would be just guessing and begging for information.
How to get a logcat
Go to settings->about tablet and tab build number 7 times to enable developer options.
Go to just enabled settings->developer options and enable root access as well as local terminal
open terminal from app-drawer and type:
Code:
su -
logcat -d >/sdcard/Download/logcat.txt
zip /sdcard/Download/logcat.txt
Now you have /sdcard/Download/logcat.txt.zip - this file is the oxygen to burn down your issue!
provide this logfile with your report. Alternatly you can skip the zipping step and upload the palin text file to paste.bin or dropbox or something like this.

How to build cm12 for chagallwifi
Most important preperation step!
Learn git. Read all the manpages, that come with git. I don't speak of github - thats a nice service I like to use, but working with git means working on the command line. githubs web interface is a lightwight, impotent version of git. Github is great as server to store your projects, but not that what youmwill need the next days... Learn git or go home.
Setting up the environment
Consult the HOWTOs of your distro. You can use any distro to build android on, there is even a HOWTO on setting up an android build environment on cygwin on win. Ubuntu, archLinux and gentoo are known to work and have detailed descriptions on the settup.
I use gentoo with icedtea-7. But as stated: any distro will work, once you have setup your environment.
Getting cm12
Find a place on your harddisc partitions with at least 18 GB free space and appropriate access rights for the user you are building with. Get a shell as this user and get the scm source:
Code:
mkdir cm12 #you can call the dir how ever you want - but whenever I refer to cm12
# as directory in this howto, I refer to THIS directory. I may also use the
# term: cm build root.
repo init -u git://github.com/CyanogenMod/android.git -b cm-12.1 # this initiates the repo
repo sync # this fetches the code (quite a couple of GBs - get a laaaarge cup of coffee)
Getting chagallwifi specific gits
Copy the following lines as nvertigo_local_manifest.xml to cm12/.repo/local_manifests/
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<remote name="tm"
fetch="https://github.com/TheMuppets/" />
<remote name="cm"
fetch="https://github.com/CyanogenMod/" />
<remote name="nvertigo"
fetch="https://github.com/nvertigo/" />
<!-- save us from the step of extract-files -->
<!-- BLOBS for manta -->
<project name="proprietary_vendor_samsung" path="vendor/samsung" remote="tm" revision="cm-12.1" />
<project name="proprietary_vendor_audience" path="vendor/audience" remote="tm" revision="cm-12.1" />
<project name="proprietary_vendor_widevine" path="vendor/widevine" remote="tm" revision="cm-12.1" />
<project name="proprietary_vendor_broadcom" path="vendor/broadcom" remote="tm" revision="cm-12.1" />
<!-- BLOBS for lge -->
<project name="proprietary_vendor_lge" path="vendor/lge" remote="tm" revision="cm-12.1" />
<!-- BLOBS for oneplusone -->
<project name="proprietary_vendor_oneplus" path="vendor/oneplus" remote="tm" revision="cm-12.1" />
<project name="proprietary_vendor_oppo" path="vendor/oppo" remote="tm" revision="cm-12.1" />
<!-- BLOBS, device tree and kernel for chagallwifi -->
<project name="android_vendor_samsung_chagallwifi.git" path="vendor/samsung/chagallwifi" remote="nvertigo" revision="current-12.1" />
<project name="android_device_samsung_chagallwifi.git" path="device/samsung/chagallwifi" remote="nvertigo" revision="current-12.1" />
<project name="android_kernel_samsung_chagallwifi.git" path="kernel/samsung/chagallwifi" remote="nvertigo" revision="current-12.1" />
</manifest>
As you can see, I'm building for more devices then chagallwifi. I've decided to keep this file this way: perhaps it holds a hint on how to save us from extract-files.sh.
After you have put nvertigo_local_manifest.xml in place, make sure all dependencies are there and fetch the additional git repos:
Code:
source build/envsetup.sh
breakfast picassowifi #this pushes the relevant git repos to .repo/local_manifests/roomservice.xml and fetches them
repo sync # this one fetches our additions to nvertigo_local_manifest.xml
Build cm12 for chagallwifi
Now you are ready for build. So let's clean the build environment and fire off the magic to homegrow a cm12 rom for chagallwifi (you guessed it: from cm12 dir):
Code:
source build/envsetup.sh
make -j9 ARCH=arm clean #cleaning from previous build; you have to replace 9 by number of cores + 1
make -j9 ARCH=arm clobber #paranoid; you have to replace 9 by number of cores + 1
time breakfast chagallwifi >make.log 2>&1
time brunch chagallwifi >>make.log 2>&1
# in a second shell: tail -f make.log
make.log is better seacheble then scrolling on terminal. If something goes wrong, search for "Error 1". In the lines before that you can see what breaks your build. On my slightly overclocked amd-fx8150 with 16GB Ram brunching takes about 100 minutes.
Now you have build a flashable rom. Congrats.
Developing
Learn git.
Put the following four lines in your /etc/gitconfig
Code:
[alias]
lg1 = log --graph --all --format=format:'%C(bold blue)%h%C(reset) - %C(bold green)(%ar)%C(reset) %C(white)%s%C(reset) %C(bold white)— %an%C(reset)%C(bold yellow)%d%C(reset)' --abbrev-commit --date=relative
lg2 = log --graph --all --format=format:'%C(bold blue)%h%C(reset) - %C(bold cyan)%aD%C(reset) %C(bold green)(%ar)%C(reset)%C(bold yellow)%d%C(reset)%n'' %C(white)%s%C(reset) %C(bold white)— %an%C(reset)' --abbrev-commit
lg = !"git lg1"
Example 1: You have a fix for the device tree.
Code:
cd device/samsung/chagallwifi
git lg1 # get an impression of the git in treeview; scroll, read, learn the way the source flows
git checkout -b my-branch #you create your own local branch
#edit the files for your fix
#if you add a new file
git add new_file
#if you editied an existing file
git add edited_file
#if you want to remove a file
git rm removed_file
#now each edit is in gits staging area, but it's not commited; to commit it locally:
git commit -em "Fix foobar: foo the bar from... Try to document what you have done and why."
#now the message is taken as title for the commit and an editor opens: you can write in more detail to document your changes.
#if you want to provide such a commit in a way I can use ist
git lg1 # get the hash of the commit you want to provide
git format-patch -1 --stdout hash >/tmp/my-commit.diff
Send me the file - do NOT copy'n'paste the content. That would break tabs and spacing and render the commit unsuable. I will apply the commit with "git am", so authorship remains as well as git history. The latter is important if later one wishes to merge two different gits with simalar commits.
If you decide to keep your own git at this point, go to the github web interface, login with your name (i.e. XXXX), go to my device repository and clone it. Back to your local shell in cm12:
Code:
cd device/samsung/chagallwifi
git remote add yyyy https://github.com/XXXX/android_device_samsung_chagallwifi.git
git fetch yyyy
#remember you have commited your changes locally in your local branch cm-12..0
#the local branch cm-12.0 is setup to follow the branch cm-12.0 of the origin remote git
#but we want the local cm-12.0 to follow the one from yyyy:
git branch --set-upstream-to=yyyy/cm-12.0 cm-12.0
git push
Now you have pushed your local commit to your own remote git. Congrats. Now you write me an email: "Huh, look at my git, it fixes everything and will finally bring peace to earth.... It's in hash." Of course, I want this commit in my repo, and that is
Example 2: Take a commit from an other devs git
Code:
cd device/samsung/chagallwifi
git fetch https://github.com/XXXX/android_device_samsung_chagallwifi.git #I don't want to have this as an additional remote
git cherry-pick hash
...to be continued....

Looking forward to your up coming updates of cm12.:good:

Bushcrafter said:
Looking forward to your up coming updates of cm12.:good:
Click to expand...
Click to collapse
Me too... Would really like to try my build.
It seems my router/3g-stick is broken:
I'm not at home at the moment. I have my development server connected to the internet via a netlink n3000 with a 3g-stick. Sinve yesterday I get connection closings. I tracked that down: I can login to my machine, but as soon as the traffic increases the n3000 reboots... First after 180 to 220 MB of traffik, at the moment after som Kb (if I "tail -n250 /var/log/messages" connection breaks du to reboot...). I'm pissed off.
I'm will be at home at end of the week - hopefully it's the stick (I have a spare one). If the router is broken I need to order a new one...
How ever: sorry for making you expect a cm12 build - but it will be there as soon as I get my developing machine back to an reliable internet connection!

nvertigo67 said:
Me too... Would really like to try my build.
It seems my router/3g-stick is broken:
I'm not at home at the moment. I have my development server connected to the internet via a netlink n3000 with a 3g-stick. Sinve yesterday I get connection closings. I tracked that down: I can login to my machine, but as soon as the traffic increases the n3000 reboots... First after 180 to 220 MB of traffik, at the moment after som Kb (if I "tail -n250 /var/log/messages" connection breaks du to reboot...). I'm pissed off.
I'm will be at home at end of the week - hopefully it's the stick (I have a spare one). If the router is broken I need to order a new one...
How ever: sorry for making you expect a cm12 build - but it will be there as soon as I get my developing machine back to an reliable internet connection!
Click to expand...
Click to collapse
No problem. Hope you get it figured out when you get home!:good: We all need your expertise with cm12 so we can have the best tab s ROM in the WORLD!:laugh: :good:

Bushcrafter said:
No problem. Hope you get it figured out when you get home!:good: We all need your expertise with cm12 so we can have the best tab s ROM in the WORLD!:laugh: :good:
Click to expand...
Click to collapse
+1 :good::

nvertigo67 said:
Me too... How ever: sorry for making you expect a cm12 build - but it will be there as soon as I get my developing machine back to an reliable internet connection!
Click to expand...
Click to collapse
No need to apologize. I doubt the rom development for the tab s would be anywhere close to where it is now without your work.
Now after approx 24 hours of hoping for a cm12 rom that will finally boot on my t805, i almost don't dare to ask if there is a slight chance it will happen this time?

Uh maybe someone (maybe me? I'm trying!) could compile the rom from your GIT and upload it somewhere?

Thread is closed until OP can provide a download link. At that time the OP can contact moderation team for re-opening.
MD

Moscow Desire said:
Thread is closed until OP can provide a download link. At that time the OP can contact moderation team for re-opening.
MD
Click to expand...
Click to collapse
Sorry for the incinvience! Thank you for your help!
Download is up - Known Issues is updated. I will cleanup now and update git repositories.
Remember: IT'S ALPHA - for daily driver use my cm-11.0 build.
Thanx to all for their patience!!!

nvertigo67 said:
Sorry for the incinvience! Thank you for your help!
Download is up - Known Issues is updated. I will cleanup now and update git repositories.
Remember: IT'S ALPHA - for daily driver use my cm-11.0 build.
Thanx to all for their patience!!!
Click to expand...
Click to collapse
I will give it a try!:good: Its good to see that you got your router problems figured out!
Update: Just got your ROM running on the s and so far so good. How good do you expect battery life to be with this ROM?

Bushcrafter said:
I will give it a try!:good: Its good to see that you got your router problems figured out!
Update: Just got your ROM running on the s and so far so good. How good do you expect battery life to be with this ROM?
Click to expand...
Click to collapse
I don't know. I'm using cm12 perhaps 7h h longer then you. As long as I haven't fixed gps I suppose it not too good - but I'm guessing here.

nvertigo67 said:
I don't know. I'm using cm12 perhaps 7h h longer then you. As long as I haven't fixed gps I suppose it not too good - but I'm guessing here.
Click to expand...
Click to collapse
I will run it for a couple of days and see what my battery life is like. Is there anyway to get synapse to work with your kernel? Just curious.

Yay LP thanks will flash when it's a bit more stable

Bushcrafter said:
I will run it for a couple of days and see what my battery life is like. Is there anyway to get synapse to work with your kernel? Just curious.
Click to expand...
Click to collapse
Synapse don't know anything about a kernel - UKM does. UKM does not support our device. Grep the current version of UKM (i belive there is also a git repository for it), take a look at the device files and jason scripts and modify for chagall. You can do it in a way, that settings not availibale in a given kernel are not shown. Everybody would be glad...
My time is limited and I have made the decision to use my time on cm12 for chagall - I have started the above work. I you really want to develop UKM for us all drop me a note and I will push my work to git. But first of all make yourself familar with UKM and git. Propably it would be usefull to read the UKM thread and contact the developer.

Hi, Just to say thanks for this rom and to let you know that I flashed it and have it running now on my T800 there is just a couple of minor issues SuperSU won't update and I don't have access to my external SD card.
Thanks again :good:

Screenshot, wait time batery life

maxal said:
Hi, Just to say thanks for this rom and to let you know that I flashed it and have it running now on my T800 there is just a couple of minor issues SuperSU won't update and I don't have access to my external SD card.
Thanks again :good:
Click to expand...
Click to collapse
Sdcard: read issues section in OP for workaround. init.d support is broken at the moument.
What do you mean with "SuperSU won't update"? Error message? Logcat?

Guide to port to Lineage-16.0

Hello,
I am interested in trying to port sumire to Lineage 16.0, the problem is I couldn't find any guide that seemed to help me get started.
In IRC someone told me I had to:
1. Fork the cm-14.1 branch to lineage-16.0, change the required config files, and build in a 16.0 build env.
2. Wait for it to error out, fix error, repeat. Eventually once it builds, attempt booting, check logs to see why it isn't booting, fix error, repeat.
But as you can see, its not much.
I have been taking a look into the first commits for sumire on cm-14.1, https://github.com/LineageOS/androi...mmit/7be9d2e5edf6f7ea1f399febbeee9d9fbdc122e1
But I do not know if its the best way to learn.
Where could I find some guides?
Best regards

algui91 said:
Hello,
I am interested in trying to port sumire to Lineage 16.0, the problem is I couldn't find any guide that seemed to help me get started.
In IRC someone told me I had to:
1. Fork the cm-14.1 branch to lineage-16.0, change the required config files, and build in a 16.0 build env.
2. Wait for it to error out, fix error, repeat. Eventually once it builds, attempt booting, check logs to see why it isn't booting, fix error, repeat.
But as you can see, its not much.
I have been taking a look into the first commits for sumire on cm-14.1, https://github.com/LineageOS/androi...mmit/7be9d2e5edf6f7ea1f399febbeee9d9fbdc122e1
But I do not know if its the best way to learn.
Where could I find some guides?
Best regards
Click to expand...
Click to collapse
It's not really a guide, but the guy in this thread tried to port LOS 15 to the Z5, so it's probably the best place to start. He ran into issues with the camera so take a look at the last few pages too see what's going on. The people in that thread are willing to help.
https://forum.xda-developers.com/z5...erimental-lineageos-15-1-z5c-suzuran-t3894617

Devo7v said:
It's not really a guide, but the guy in this thread tried to port LOS 15 to the Z5, so it's probably the best place to start. He ran into issues with the camera so take a look at the last few pages too see what's going on. The people in that thread are willing to help.
https://forum.xda-developers.com/z5...erimental-lineageos-15-1-z5c-suzuran-t3894617
Click to expand...
Click to collapse
Thanks, although its not for the same device (Mine is sumire) it may be helpful.
I have also found this guide, it seems interesting:
https://fat-tire.github.io/porting-intro.html

algui91 said:
Thanks, although its not for the same device (Mine is sumire) it may be helpful.
I have also found this guide, it seems interesting:
https://fat-tire.github.io/porting-intro.html
Click to expand...
Click to collapse
Is there any progress at porting LOS 16?

BrazzerHead said:
Is there any progress at porting LOS 16?
Click to expand...
Click to collapse
I'm still on it. Advancing slowly as I am a newbie on this and only have a few hours/week to do it.
I will keep you updated

I have successfully come to execute brunch sumire, but I am having problems with open jdk-9:
Code:
/run/media/hkr/BackUp/out/soong/make_vars-lineage_sumire.mk:644: warning: JAVAC does not match between Make and Soong:
/run/media/hkr/BackUp/out/soong/make_vars-lineage_sumire.mk:644: warning: Make : /home/hkr/.gentoo/java-config-2/current-user-vm/bin/javac
/run/media/hkr/BackUp/out/soong/make_vars-lineage_sumire.mk:644: warning: Soong: prebuilts/jdk/jdk9/linux-x86/bin/javac
/run/media/hkr/BackUp/out/soong/make_vars-lineage_sumire.mk:1044: error: Soong variable check failed.
I have copied the prebuild version of java that comes with android into my own local version in gentoo, but still getting the same error.
Any ideas?

I have set up android_device_sony_sumire from sony-msm8994 in the included .repo/local_manifest. Setting ROOMSERVICE_BRANCHES=cm-14 as it functions as a fallback branch was suggested in the console output while i was getting familiar and this is a helpful feature worth noting.
There is an incompatibility in https://github.com/sony-msm8994/android_device_sony_sumire and kitakami-common, the lineage.dependencies file needs to be moved or it will try and download dependencies for the sumire files from the LineageOS Github (http://github.com/LineageOS). Next there are two easy defines, SND_AUDIOCODEC_ALAC and SND_AUDIOCODEC_APE to deal with before an untimely error because of a typo present in the Xperia kernel, content_interprtation_type instead of content_interpretation_type.
Code:
hardware/qcom/media-caf/msm8994/mm-video-v4l2/vidc/vdec/src/omx_vdec_msm8974.cpp:9377:60: error: no member named 'content_interprtation_type' in 'msm_vidc_s3d_frame_packing_payload'; did you mean 'content_interpretation_type'?
if (s3d_frame_packing_payload->content_interprtation_type == 1)
^~~~~~~~~~~~~~~~~~~~~~~~~~
content_interpretation_type
out/target/product/sumire/obj/KERNEL_OBJ/usr/include/media/msm_vidc.h:109:15: note: 'content_interpretation_type' declared here
unsigned int content_interpretation_type;
^
hardware/qcom/media-caf/msm8994/mm-video-v4l2/vidc/vdec/src/omx_vdec_msm8974.cpp:9379:65: error: no member named 'content_interprtation_type' in 'msm_vidc_s3d_frame_packing_payload'; did you mean 'content_interpretation_type'?
else if (s3d_frame_packing_payload->content_interprtation_type == 2)
^~~~~~~~~~~~~~~~~~~~~~~~~~
content_interpretation_type
out/target/product/sumire/obj/KERNEL_OBJ/usr/include/media/msm_vidc.h:109:15: note: 'content_interpretation_type' declared here
unsigned int content_interpretation_type;
^
hardware/qcom/media-caf/msm8994/mm-video-v4l2/vidc/vdec/src/omx_vdec_msm8974.cpp:9394:89: error: no member named 'content_interprtation_type' in 'msm_vidc_s3d_frame_packing_payload'; did you mean 'content_interpretation_type'?
s3d_frame_packing_payload->fpa_type, s3d_frame_packing_payload->content_interprtation_type, stereo_output_mode);
^~~~~~~~~~~~~~~~~~~~~~~~~~
content_interpretation_type

It compiled, but gives a black boot screen both from early boot, a kernel issue, adb seems to be communicating, I'm meddling with the boot image atm so i will know more later (Later: The updated mdss code broke for our case somewhere. I will also need to work on the local_manifest) (Later: New Manifest attached) . Last I tested the kernel a few moons ago it worked on the Z1, so issue this was a surprise... I will also import the changes from the sony-msm8994 project, who is doing a great job, i see quite a lot of work to the sdcardfs code.

threader said:
It compiled, but gives a black boot screen both from early boot, a kernel issue, adb seems to be communicating, I'm meddling with the boot image atm so i will know more later (Later: The updated mdss code broke for our case somewhere. I will also need to work on the local_manifest) (Later: New Manifest attached) . Last I tested the kernel a few moons ago it worked on the Z1, so issue this was a surprise... I will also import the changes from the sony-msm8994 project, who is doing a great job, i see quite a lot of work to the sdcardfs code.
Click to expand...
Click to collapse
How did you managed to compile it? I am finding a lot of problems, for example, in system/core/init/util.h
Code:
#include <android-base/chrono_utils.h>
#include <selinux/label.h>
were not found, so I had to comment them out, but I do not know if this its going to be the best approach...

@algui91
Im about to test what built tonight. I suspect i need to port the binder from sony-msm8994 though, it lookst tasty anyway. But does your build by any chance warn against building with a pre compiled kernel? I guess or simply some headers might have new names maybe or some feature needs to be introduced into the kernel.
The .repo/local_manifest/oss.xml contains some qcom opensource projects, to compile for 16.1 change opensource-location from revision=o-mr to p-mr. Also add https://github.com/sonyxperiadev/transpower/commits/android-8.1.0_r35, for 15.1 or probably master for 16.1, i missed that yesterday.

threader said:
@algui91
Im about to test what built tonight. I suspect i need to port the binder from sony-msm8994 though, it lookst tasty anyway. But does your build by any chance warn against building with a pre compiled kernel? I guess or simply some headers might have new names maybe or some feature needs to be introduced into the kernel.
The .repo/local_manifest/oss.xml contains some qcom opensource projects, to compile for 16.1 change opensource-location from revision=o-mr to p-mr. Also add https://github.com/sonyxperiadev/transpower/commits/android-8.1.0_r35, for 15.1 or probably master for 16.1, i missed that yesterday.
Click to expand...
Click to collapse
Hello,
Thanks for your quick reply, How did your test went? this are the only warnings I get when running brunch sumire:
Code:
build/make/core/combo/TARGET_linux-arm.mk:43: warning: cortex-a53.a57 is armv8-a.
build/make/core/combo/TARGET_linux-arm.mk:45: warning: TARGET_2ND_ARCH_VARIANT, armv7-a-neon, ignored! Use armv8-a instead.
Trying dependencies-only mode on a non-existing device tree?

I applied the required binder changes from sony-msm8994 for AOSP 8.1 and it turns out it results in a locked kernel that fails to even boot, so i'm looking that problem now. So for instant results instead of my Z1 to Z5 kernel, use https://github.com/sony-msm8994/android_kernel_sony_msm8994 in , .repo/local_manifests/LA.BR.1.3.3_rb2.14.xml , you need to comment out common-headers common-kernel, also i see i commented out my kernel, a good place to add sony-msm8994, i realize my project to update the unified kernel is riddled with mines., and we really need 15.1 and 16.1 yesterday.

I've come around to testing the whole Sony-msm8994 project that's up on Z5c, Lineage 15.1 is up with wifi, location, nfc available at least, so is the usb otg switch, not working is fingerprint and gsm services, camera.
Spotted this in logcat.
Code:
Abort message: 'CANNOT LINK EXECUTABLE "/system/bin/netmgrd": cannot locate symbol "_ZN6google8protobuf2io16CodedInputStream20ReadVarint32FallbackEPj" referenced by "/system/vendor/lib64/libcneapiclient.so"...'
TARGET_CPU_VARIANT in device/sony/kitakami-common/BoardConfigCommon.mk is set to generic, it's supposed to be TARGET_CPU_VARIANT := cortex-a53

threader said:
I've come around to testing the whole Sony-msm8994 project that's up on Z5c, Lineage 15.1 is up with wifi, location, nfc available at least, so is the usb otg switch, not working is fingerprint and gsm services, camera.
Spotted this in logcat.
Code:
Abort message: 'CANNOT LINK EXECUTABLE "/system/bin/netmgrd": cannot locate symbol "_ZN6google8protobuf2io16CodedInputStream20ReadVarint32FallbackEPj" referenced by "/system/vendor/lib64/libcneapiclient.so"...'
TARGET_CPU_VARIANT in device/sony/kitakami-common/BoardConfigCommon.mk is set to generic, it's supposed to be TARGET_CPU_VARIANT := cortex-a53
Click to expand...
Click to collapse
Have the same problem, spotted the same Fatal message, Did the change in TARGET_CPU_VARIANT solved the problem?
Best

I've got a problem with librmnetctl, vendor/qcom/opensource/dataservices, not building, netmgrd is complaining about that missing now, I'm trying the version on Xperiadev, but now I've messed up the build i built earlier and need to rebuild all of it...

threader said:
I've got a problem with librmnetctl, vendor/qcom/opensource/dataservices, not building, netmgrd is complaining about that missing now, I'm trying the version on Xperiadev, but now I've messed up the build i built earlier and need to rebuild all of it...
Click to expand...
Click to collapse
I am trying to detect where the error
Code:
Abort message: 'CANNOT LINK EXECUTABLE "/system/bin/netmgrd": cannot locate symbol "_ZN6google8protobuf2io16CodedInputStream20ReadVarint32FallbackEPj" referenced by "/system/vendor/lib64/libcneapiclient.so"...'
comes from.
I am guessing its some makefile which has a SHARED_LIBRARY link to _ZN6google8protobuf2io16CodedInputStream20ReadVarint32FallbackEPj missing, but do not know where to find it. I've searched on the LineageOS repos without luck.

algui91 said:
I am trying to detect where the error
Code:
Abort message: 'CANNOT LINK EXECUTABLE "/system/bin/netmgrd": cannot locate symbol "_ZN6google8protobuf2io16CodedInputStream20ReadVarint32FallbackEPj" referenced by "/system/vendor/lib64/libcneapiclient.so"...'
Click to expand...
Click to collapse
It seems to be called from protobuf, maybe a missing link to it somewhere?

threader said:
It seems to be called from protobuf, maybe a missing link to it somewhere?
Click to expand...
Click to collapse
It seems so, the question is where that 'Somewhere' is. . Will keep searching.

algui91 said:
It seems so, the question is where that 'Somewhere' is. . Will keep searching.
Click to expand...
Click to collapse
I see its in prebuilt compiler also.
But maybe?
Code:
external/protobuf/src/google/protobuf/io/coded_stream.cc :
Los 14.1
bool CodedInputStream::ReadVarint32Fallback(uint32* value) {
if (BufferSize() >= kMaxVarintBytes ||
// Optimization: We're also safe if the buffer is non-empty and it ends
// with a byte that would terminate a varint.
(buffer_end_ > buffer_ && !(buffer_end_[-1] & 0x80))) {
const uint8* end = ReadVarint32FromArray(buffer_, value);
if (end == NULL) return false;
buffer_ = end;
return true;
} else {
// Really slow case: we will incur the cost of an extra function call here,
// but moving this out of line reduces the size of this function, which
// improves the common case. In micro benchmarks, this is worth about 10-15%
return ReadVarint32Slow(value);
}
}
Los.15.1
int64 CodedInputStream::ReadVarint32Fallback(uint32 first_byte_or_zero) {
if (BufferSize() >= kMaxVarintBytes ||
// Optimization: We're also safe if the buffer is non-empty and it ends
// with a byte that would terminate a varint.
(buffer_end_ > buffer_ && !(buffer_end_[-1] & 0x80))) {
GOOGLE_DCHECK_NE(first_byte_or_zero, 0)
<< "Caller should provide us with *buffer_ when buffer is non-empty";
uint32 temp;
::std::pair<bool, const uint8*> p =
ReadVarint32FromArray(first_byte_or_zero, buffer_, &temp);
if (!p.first) return -1;
buffer_ = p.second;
return temp;
} else {
// Really slow case: we will incur the cost of an extra function call here,
// but moving this out of line reduces the size of this function, which
// improves the common case. In micro benchmarks, this is worth about 10-15%
uint32 temp;
return ReadVarint32Slow(&temp) ? static_cast<int64>(temp) : -1;
}
}
The function ReadVarint32Fallback is used in the following libraries :
vendor/sony/kitakami-common/proprietary/vendor/lib64/libsettings.so
vendor/sony/kitakami-common/proprietary/vendor/lib64/libcneapiclient.so
vendor/sony/kitakami-common/proprietary/vendor/lib/libsettings.so
vendor/sony/kitakami-common/proprietary/vendor/lib/libcneapiclient.so
vendor/sony/kitakami-common/proprietary/vendor/lib/mediadrm/libwvdrmengine.so

So i rolled back the functions required by the libraries in external/protobuf/src/google/protobuf/io/coded_stream.h, external/protobuf/src/google/protobuf/io/coded_stream.cc, attached a patch to get a bit farther .
I get the following error now.
Code:
520 F DEBUG : Abort message: 'CANNOT LINK EXECUTABLE "/system/bin/netmgrd": cannot locate symbol "_ZN6google8protobuf8internal14WireFormatLite10ReadStringEPNS0_2io16CodedInputStreamEPNSt3__112basic_stringIcNS6_11char_traitsIcEENS6_9allocatorIcEEEE" referenced by "/system/vendor/lib64/libcneapiclient.so"...'
I think the correct thing to do now is call ReadStringEPNS0_2io16CodedInputStreamEPNSt3__112basic_stringIcNS6_11char_traitsIcEENS6_9allocatorIcEEEE

OPEN BETA for 17.1 UNOFFICIAL LineageOS T550 rom

BEFORE YOU decide to try this rom, please read all of post 1 and 2.
The UNOFFICIAL LineageOS 17.1 T550 ROM
BACKUP YOUR DATA AND OLD ROM BEFORE trying my rom.
Let me be clear, I have the SM-P550, NOT the SM-T550.
So I built a SM-P550 rom which is almost the same as the SM-T550 except the "P" stands for Pen.
I believe my P550 rom with minor modifications will work on the T550, but I have no T550 to test it on. I believe it will work because I have used virsys T550 rom on my P550 and it works, but the X-axis touch is inverted.
So I built SM-P550 with code to fix the X-axis touch inverted problem and it's one of line code. If I leave that one line of code out, then the X-axis will be correct for the T550. I have tested my 17.1 T550 rom on my P550 and it works, but again with the X-axis inverted. Just remember I don't have a T550 to test it on so you may run into bootloops, stuck at boot animation, etc.
If you are NOT an expert in using fastboot, adb, odin, heimdall, twrp, DO NOT attempt this ROM. You must know how to use these tools to revert back to your old rom. I'm not a Windows user so do not expect any help from me. My main OS is Lubuntu 20.04 LTS and all my roms are built on this platform.
If you are new to flashing custom roms, do NOT attempt this.
If you need your tablet for work and something important, do NOT flash this rom. This rom could result in a bricked device or boot loop or non booting device or you not being able to revert back to your old rom.
Again, the T550 rom that I built does boot and function on my P550, but I have no T550 to verify.
BACKUP YOUR DATA AND OLD ROM BEFORE trying my rom.
The rom has the latest monthly 2021 security patches.
What works
1. bluetooth
2. wifi
3. brightness
4. external audio
5. GPS
6. audio through headphone jack
7. camera
8. touchscreen X-axis works properly
9. Google play store - use pico apps
10. flip flap smart cover
11. audio over bluetooth
What doesn't work
1. LineageOS FM Radio app does not work. The P550 and T550 don't have the LTE chipset for it to work.
2. The stock Jelly browser crashes a lot. Use a different browser. There's lots of better options that are more stable and reliable than the built in Jelly browser.
3. Home screen text may look fuzzy.
Text on home screen looks funny/fuzzy. This only seems to affect the home screen and nowhere else. I have seen the same problem on the SM-T350, SM-T560NU, SM-P550 and Nexus 7 2013.
Problem is with stock trebuchet launcher and/or its fonts. I tried rootless pixel launcher from fdroid as a quick and simple test and see no problems with home screen text. Rootless pixel uses a different font though. A future LineageOS update could resolve the problem?

FAQ - I spent hundreds of hours building this rom. The least you can do is spend a few minutes reading everything before posting.
Q1) Why are you releasing a ROM for a tablet that you do not own?
A1) I don't own the SM-T550, but have the SM-P550. I also build roms for the SM-T350 and SM-T560NU. All these platforms use the same msm8916 code base. As such, all my work from the SM-T350, SM-T560NU and SM-P550 could possibly benefit SM-T550 users. For one P550 owner, there are probably twenty T550 owners.
Q2) What if my app, xyz, doesn't work?
A2) I won't answer questions regarding why your app doesn't work. If your app, whatever it is, doesn't work, then go back to your old rom. It's difficult enough building and maintaining these roms. Remember, I'm an unpaid volunteer making a rom for free for your benefit, not mine as I don't even have the T550.
Q3) Your rom is laggy and buggy.
A3) If you find the above, then go back to your old rom. There's only so much software can do on a 2015 budget level tablet. Remember a budget tablet will have the slower SoC/CPU and less DRAM than a top of the line model. Your tablet will also run slower when you use gapps (google apps). You can run a lot of software without using gapps. Research newpipe, microg, youtube vanced, aurora store etc.
Q4) What TWRP should I use?
A4) Use 3.4.0.0. Get it at
Download TWRP for gt510wifi
Download TWRP Open Recovery for gt510wifi
dl.twrp.me
Q5) Why should I use this rom?
A5) You don't. I only offer it because I have built the SM-P550 and it was an easy change to make a SM-T550 rom. If you don't like this rom, then don't use it. Yes, it's that simple.
Q6) Can you build SM-T555 (LTE) or a crDroid version of the SM-T550?
A6) No. All the source code is open source and my changes are in the repo diff file. You can use these two with the roomservice.xml to build your own rom.
Q7) Will you offer monthly updates with security patches?
A7) That all depends on if I continue to have high speed Internet and on the reaction of the posts in this thread. If people are going to complain, then I have NO incentive to make an update. Remember, I don't have the T550 so I get zero benefit from making this rom for myself.
Q8) Can you help me? I'm a newbie. Can you provide step by step instructions?
A8) There are lots of tutorials, videos, etc on how to flash roms. Do your own research.
Q9) Can I report a bug with respect to the rom?
A9) Yes, but you need to supply a) how to recreate it b) a logcat c) a github commit showing how it was fixed. Even then, if I don't have the means to recreate it, I won't be working on it.
Q10) Can I build this rom? Where are the source and kernel source files?
A10) Yes. The kernel source files are at
Samsung MSM8916 Devices
Samsung MSM8916 Devices has 68 repositories available. Follow their code on GitHub.
github.com
aala27 - Repositories
aala27 has 7 repositories available. Follow their code on GitHub.
github.com
Q11) Okay, I understand the consequences and that this is beta rom and willing to take the risks outlined, now where can I find the rom?
A11) Downloads are at
retiredtab - Browse /SM-T550/17.1 at SourceForge.net
sourceforge.net

Hi rretiredtab
I have a T550 with the latest virsys image 16.0 from March 2020.
It is more or less stable, but I think, it will be always slowlier. Empty dalvic and cache does not help.
I'm ready for a new challenge. If I can help you, please let me know.
Best regards
Schaagi

Hi retiredtab,
I ready to try this rom

Schaagi said:
I have a T550 with the latest virsys image 16.0 from March 2020. It is more or less stable, but I think, it will be always slowlier. Empty dalvic and cache does not help.
Click to expand...
Click to collapse
My 16.0 rom for the SM-P550 is based on virsys repos. However, I was only able to make 2 builds using his repos before a LineageOS update in Sept 2020 caused it to get stuck at the boot animation.
Then I tried virsys 17.1 repo and it too gets stuck at the boot animation. I know virsys built crDroid Android 10 rom and uploaded it sometime June 2020, but his Android 10 repos on github are dated March 2020 so whatever patches he did to get crDroid working isn't on github.
I don't know if 17.1 will be faster than 16.0. The 17.1 builds, by default, use an overclocked CPU and GPU in the kernel code. However, I don't know if you will see any real world differences in performance from the overclocking.
In addition, I don't know if virsys March 16.0 March 2020 is overclocked or not. You can always download an utility like CPUinfo at
CPU Info | F-Droid - Free and Open Source Android App Repository
Information about device hardware and software
f-droid.org
to see if the CPU is running at 1.2Ghz or 1.6Ghz (overclocked).

@Schaagi and @Simone101, please let me know if the T550 ROM boots or not after you have installed it. I'm pretty sure it will, but would like to know ASAP.
Then, afterwards, you can let me know how it works over a 24 to 48 hour period. I'm interested to see if it randomly reboots or crashes.
As for speed and performance, just remember it's a 5 year old entry level tablet and unless LineageOS is written in assembler language, it will never match a top of the line model tablet.
Thank you.

I've installed your image as clean-install. It boots !!!
At the beginning of the setup process there is a bluetooth error, that repeats after every new boot.
First installation without opengapps -ok
Second one with opengapps - ok
Restore Data from previous image - ok
As next I will try to install magisk.
Wow, good job. I will check it for the next days and give feedback later.
Best regards
Schaagi

Schaagi said:
At the beginning of the setup process there is a bluetooth error, that repeats after every new boot.
Click to expand...
Click to collapse
Can you provide a screenshot of the error please?
I haven't seen the bluetooth error before on my SM-P550 and I reboot my SM-P550 a lot because I'm always flashing new builds.
I don't use bluetooth at all, but when I turn it on, I can see my neighbor's 65 inch TV. Also, I can pair two tablets together using bluetooth.

Meanwhile I have installed Magisk 21.1 and it works too
I've attached 2 screenshots from Bluetooth error.

Schaagi said:
I've attached 2 screenshots from Bluetooth error.
Click to expand...
Click to collapse
The above is why we need BETA testers.
Okay, I ran into the bluetooth error problem on the SM-T350 and it was due to a missing bluetooth library.
In my SM-T350, I have
Code:
# RT 17.1 copy bluetooth file otherwise bluetooth keeps crashing
PRODUCT_COPY_FILES += \
vendor/samsung/msm8916-common/proprietary/vendor/lib/libbtnv.so:$(TARGET_COPY_OUT_VENDOR)/lib/libbtnv.so
Those 3 lines of code are not in the T550 build. It's easy to add and I can create another BETA build. It's building right now and probably be done in the next 2 hours or so.
If you want to add the libbtnv.so file yourself, here are the instructions
1) Boot into TWRP 3.4.0.0.
2) Click Mount. Choose System.
3) On your computer, goto
proprietary_vendor_samsung/libbtnv.so at lineage-17.1 · Galaxy-MSM8916/proprietary_vendor_samsung
proprietary_vendor_samsung. Contribute to Galaxy-MSM8916/proprietary_vendor_samsung development by creating an account on GitHub.
github.com
4) Click download.
5) Goto the directory where the libbtnv.so is saved.
6) Plug in microusb cable to tablet.
7) Then use adb to push the file using the command
Code:
$ adb push libbtnv.so /system/vendor/lib/libbtnv.so
libbtnv.so: 1 file pushed, 0 skipped. 48.5 MB/s (16128 bytes in 0.000s)
8) Check to make sure file was pushed.
Code:
$ adb shell ls -al /system/vendor/lib/libbtnv.so
-rw-r--r-- 1 root root 16128 Dec 19 21:24 /system/vendor/lib/libbtnv.so
9) Reboot into system and bluetooth error should be gone.
OR
Just wait until my next build is done to get rid of the bluetooth errors. I'm confident the error is due to the missing bluetooth library file.
I will send you and Simone101 a PM when the new build is done.

The new BETA build is finished, but having problems uploading to host server right now. I will try again in a couple of hours to upload. I will PM when I get it uploaded.

I've installed the new image and bluetooth error has gone.But I'didn't test the functionality of bluetooth at the moment.
Will check more in detail and inform you about the results. Thank you.
Regards
Schaagi

@retiredtab
I want to test your ROM , where I can download it.
At the moment I use the cdroid 10 by virsys
My CPU runs at performance mode with 1600 MHz.

bierma32 said:
At the moment I use the cdroid 10 by virsys
Click to expand...
Click to collapse
Over at the T550 thread, it seems that some people who are using crDroid 10 are reporting
1) camera not working
2) brightness not working
3) browser crash (that's you)
#1 and #2 work on my build. As for #3, if you are using the built in Jelly browser, I have noticed that if you open more than 4 windows, it crashes sometimes.
While not perfect, I found that smartcookieweb app works better than Jelly.
Releases · CookieJarApps/SmartCookieWeb
A secure, open source web browser for Android. Contribute to CookieJarApps/SmartCookieWeb development by creating an account on GitHub.
github.com
The Brave browser seems to work the most reliable. You can use Aurora store to download it from play store or try downloading brave apk somewhere.
On a daily basis, I use smartcookieweb as it has built in adblocker and suits my daily browsing needs.

@retiredtab
Both cameras works on Cdroid for me.
Yes, browsers crashes after some times, I use opera mini.

Bluetooth works for, tested sending and recive images.
GPS is not working, will try it again next time.
Magisk 21 works.
WiFi works.

Hi retiredtab,
Nice to see that anybody has try to give us an update for this fossile
Please let me knoe where can I download and test your build.
regards,
L

bierma32 said:
GPS is not working
Click to expand...
Click to collapse
No need to retest GPS. I already know what's wrong. This is the same problem I had with the T350.
The T550 build is missing the commands
Code:
# GPS
PRODUCT_COPY_FILES += \
vendor/samsung/msm8916-common/proprietary/lib/libloc_api_v02.so:$(TARGET_COPY_OUT_VENDOR)/lib/libloc_api_v02.so \
vendor/samsung/msm8916-common/proprietary/lib/libloc_ds_api.so:$(TARGET_COPY_OUT_VENDOR)/lib/libloc_ds_api.so
Now I did test the T550 build on my P550, but it looks like when I made the final image, some of my scripts or commits didn't get copied, like the above, over when I initially changed some P550 naming/parameters to T550.
Some background. I had only 1 hard drive for the P550 and T550 code. I did test bluetooth and gps on my P550 and both work.
After I tested everything, I then later split the P550 onto one hard drive and the T550 to another so I wouldn't get confused when compiling and making changes. I suspect now that I forgot to copy over my T350 script to fix gps and bluetooth onto the new T550 drive.
To fix gps without having to re-download another 440MB file,
1) Boot into TWRP 3.4.0.0.
2) Click Mount. Choose System.
3) On your computer, goto
proprietary_vendor_samsung/libloc_ds_api.so at lineage-17.1 · Galaxy-MSM8916/proprietary_vendor_samsung
proprietary_vendor_samsung. Contribute to Galaxy-MSM8916/proprietary_vendor_samsung development by creating an account on GitHub.
github.com
and
proprietary_vendor_samsung/libloc_api_v02.so at lineage-17.1 · Galaxy-MSM8916/proprietary_vendor_samsung
proprietary_vendor_samsung. Contribute to Galaxy-MSM8916/proprietary_vendor_samsung development by creating an account on GitHub.
github.com
4) Download both files above (libloc_ds_api.so and libloc_api_v02.so).
5) Goto the directory where both are saved.
6) Plug in microusb cable to tablet.
7) Then use adb to push the file using the command
Code:
$adb push libloc_api_v02.so /system/vendor/lib/libloc_api_v02.so
libloc_api_v02.so: 1 file pushed, 0 skipped. 7.6 MB/s (116316 bytes in 0.015s)
$adb push libloc_ds_api.so /system/vendor/lib/libloc_ds_api.so
libloc_ds_api.so: 1 file pushed, 0 skipped. 29.5 MB/s (26132 bytes in 0.001s)
8) Check that both files exist.
$adb shell ls -al /system/vendor/lib/libloc_api_v02.so
-rw-r--r-- 1 root root 116316 Dec 7 2020 /system/vendor/lib/libloc_api_v02.so
$adb shell ls -al /system/vendor/lib/libloc_ds_api.so
-rw-r--r-- 1 root root 26132 Dec 7 2020 /system/vendor/lib/libloc_ds_api.so
9) Reboot into system and GPS should be work now.
I'm making a new BETA image again and before I upload it, I will retest everything again on my P550. It's a bit awkard as everything is mapped backwards on the X-axis.
I'll post here when it's up.

Well it was around 1AM in the morning when I saw the gps not working post and now it's 2:13AM. I'm just waiting for the last 5 minutes of my new build, but the host server is having major problems right now.
So I'm going to sleep and will try uploading the new image tomorrow after I retest everything with the P550 running the T550 image. Everything will be mapped backwards for me on the X-axis while testing.
Dec 21 BETA build up. Androidfilehost is having major problems so I put it up on sourceforge.net. No way I could go to sleep with this hanging over my head. It's 2:30AM. Now I'm going to sleep in tomorrow.
Dec 21 build has gps fix.

Ooh i want really like to test!

Need help building a SM-T555 (gt510lte) LineageOS ROM

Dear all,
I am trying to build a LineageOS 17.1 ROM for the Galaxy Tab A 9.7 (gt510lte) SM-T555.
Using the repos of @retiredtab and aala27's repos I managed to build a config that resulted in a buildable LineageOS that I could install and that shows the Lineage boot animation but crashes/reboots after a while.
Fyi, my forks for the GT510LTE (SM-T555) I currently maintain here: https://github.com/blizzard4591?tab=repositories
Questions to @retiredtab:
- What is your current local_manifest/roomservice? I could not locate this in your Github and used one posted by aala27 in a different thread, but it might be "off".
- Did you extract the required proprietary files by hand from stock ROMs or is there an automated way? I have "SM-T555_1_20190103084053_we4a668guy_fac" with T555XXU1CQHA/T555XXU1CRG1 that I know works on my T555.
- The repo "vendor-samsung-gt5note10wifi" in your Github only contains a branch for Lineage 18.1, is that intentional?
Sadly, I am a total noob in the area of building Lineage, so I might miss some obvious things!
I am willing to put in some time and effort to make this work, but I just do not know enough to do it efficiently.
If you can spare the time for a few hints, I believe I can make some progress!
Cheers
Update 1:
My image is working, i.e. it boots and gives a stable system.
Problem: Bluetooth does not work and crashes a lot, I have no clue what the problem is.
Problem: Audio is not working, I see a lot of "audio_route: unable to find path 'low-latency-playback speaker'
The system settings dialog is missing the "Android Patchlevel" information - is this expected? I am building using "repo sync, breakfast gt510lte, brunch gt510lte" - is this correct? I am just an idiot.
Update 2:
Bluetooth and Audio are working, SELinux is not, so permissive it is for now.
Builds available on request.

RandomAndroidTinkerer said:
- What is your current local_manifest/roomservice? I could not locate this in your Github and used one posted by aala27 in a different thread, but it might be "off".
Click to expand...
Click to collapse
It was there before, but I think after the switch to Xenforo on Dec 1, 2020, it might have gotten lost. It's there now and what I use to generate 17.1 for T550.
RandomAndroidTinkerer said:
- Did you extract the required proprietary files by hand from stock ROMs or is there an automated way? I have "SM-T555_1_20190103084053_we4a668guy_fac" with T555XXU1CQHA/T555XXU1CRG1 that I know works on my T555.
Click to expand...
Click to collapse
No, I just used what's in at https://github.com/Galaxy-MSM8916. Having said that, I found that for the SM-T350, it was missing some very important files so I grabbed those from stock.
RandomAndroidTinkerer said:
- The repo "vendor-samsung-gt5note10wifi" in your Github only contains a branch for Lineage 18.1, is that intentional?
Click to expand...
Click to collapse
gt5note10wifi is for the P550, not T550. You shouldn't be using that as the *.mk files won't copy the correct blobs for your device.
RandomAndroidTinkerer said:
Update 1:
My image is working, i.e. it boots and gives a stable system.
Problem: Bluetooth does not work and crashes a lot, I have no clue what the problem is.
The system settings dialog is missing the "Android Patchlevel" information - is this expected? I am building using "repo sync, breakfast gt510lte, brunch gt510lte" - is this correct?
Click to expand...
Click to collapse
Congrats on getting a bootable stable system. For bluetooth, you are probably missing a bluetooth blob. Look in your adb logcat (see below) for red messages that are bluetooth related. It might say something like "missing libbt-nv.so".
Missing Android Patchlevel means you don't have a property declared in your *.mk file. Right now, I can' t remember what it is, but I will look for it.
Instead of brunch, I do
Code:
TARGET_BUILD_TYPE=debug TARGET_BUILD_VARIANT=eng make -j2 bacon
This makes an engineering build that starts adb logcat immediately. That way, you can see all the messages as soon as the device boots. It helps a lot in troubleshooting stuck at boot animation problems.
The -j2 indicates how many CPU cores I have. If you have more, say 4, then -j4.
Once you solved all your problems and if you want to share your ROM, then do a brunch which is userdebug by default (for me, I just do a make -j2 bacon).
For adb logcat, I find
Code:
adb logcat -C | nl
helpful. It color codes the log so anything in red (error) needs attention. Nl numbers the log so it's easier to remember where you error messages are vs a timestamp.

For the Android patch level, show me a screenshot so I exactly what you mean.

RandomAndroidTinkerer said:
Problem: Audio is not working, I see a lot of "audio_route: unable to find path 'low-latency-playback speaker'
Click to expand...
Click to collapse
Try not to edit your initial post because I didnt' see the audio problem. Just make a new one so that I see new responses.
The audio problem is likely you don't have the correct definition in mixer_paths.xml. aala27 had the exact same problem. It's likely this
[UNOFFICIAL][ROM] LineageOS 17.1 for Galaxy Tab A 9.7[SM-P550]
NOTE: There is no S-pen support. If you need S-pen, DO NOT USE THIS ROM. I am not responsible for lost data, identity theft, lost money, security vulnerabilities, bricked devices or any other hardware or software malfunctions that comes as a...
forum.xda-developers.com
For SM-T550, the line inside mixer_paths.xml looks like
Code:
<path name="low-latency-playback speaker">
<ctl name="QUAT_MI2S_RX Audio Mixer MultiMedia5" value="1" />
</path>
You can see above, I have a path name that matches 'low-latency-playback speaker' exactly. Your mixer_paths.xml probably doesn't have this defined so you get no audio.

BTW, all the info I'm giving wasn't available via search engine when I first started. It's extremely frustrating to troubleshoot when I first started. Even now, I have problems with audio over bluetooth and stuttering audio over bluetooth for two platforms that both worked perfectly on the previous last major revision on Android.

Thank you so much; I know how hard this kind of initial research is!
Regarding the audio issues:
I tried that already, as you can see in https://github.com/blizzard4591/android_device_samsung_gt510lte/tree/lineage-17.1/configs/audio I used the config files from my stock image (I had assumed they would work, but they do not - why?) and then added said speaker there, but no luck, it still has the same error message. What am I misunderstanding?
Regarding Bluetooth:
Thanks to you tip, I added the libbt-nv.so module, but this did not change the situation.
I am now building a debug/eng build, but in the log I still see no messages of missing drivers/firmware/SOs. You can find my Logcat attached - could you take a look and tell me whether I am missing something? Should there be messages?
How did you find out that you were missing BLOBs?

RandomAndroidTinkerer said:
I tried that already, as you can see in https://github.com/blizzard4591/android_device_samsung_gt510lte/tree/lineage-17.1/configs/audio I used the config files from my stock image (I had assumed they would work, but they do not - why?) and then added said speaker there, but no luck, it still has the same error message. What am I misunderstanding?
Click to expand...
Click to collapse
You need to check the actual rom image to see if the mixer_paths.xml is correct. Do
Code:
adb pull /system/vendor/etc/mixer_paths.xml
and compare if the two are the same.
RandomAndroidTinkerer said:
Regarding Bluetooth:
Thanks to you tip, I added the libbt-nv.so module, but this did not change the situation.
Click to expand...
Click to collapse
I only guessed at what might be missing. The logs will tell who what's missing.
RandomAndroidTinkerer said:
You can find my Logcat attached - could you take a look and tell me whether I am missing something?
Click to expand...
Click to collapse
I see no log attached. Zip the log and then attach it.

You need to check the actual rom image to see if the mixer_paths.xml is correct. Do
Code:
adb pull /system/vendor/etc/mixer_paths.xml
and compare if the two are the same.
Click to expand...
Click to collapse
Yes, the file was incorrect, I guess the path
Code:
$(LOCAL_PATH)/configs/audio/mixer_paths.xml:$(TARGET_COPY_OUT_VENDOR)/etc/mixer_paths.xml
did not resolve to where it should, I changed that, once the build is done I will check.
I see no log attached. Zip the log and then attach it.
Click to expand...
Click to collapse
Interesting, I can see it, but I attached it as ZIP!

The log you attached is missing all the bootup sequence. You need to start adb logcat as soon as the device boots.
Audio
=====
Your mixer_paths.xml should be in /vendor/etc. /system/vendor is usually a link to /vendor. From my P550.
Code:
$ adb shell
gt5note10wifi:/ # ls -al vendor
lrw-r--r-- 1 root root 14 2008-12-31 17:00 vendor -> /system/vendor
If you are using the 17.1 msm8916-common repo, see lines 80 to 83
android_device_samsung_msm8916-common/msm8916.mk at lineage-17.1 · Galaxy-MSM8916/android_device_samsung_msm8916-common
Common MSM8916 tree for Samsung devices. Contribute to Galaxy-MSM8916/android_device_samsung_msm8916-common development by creating an account on GitHub.
github.com
may be overwriting your stock mixer_paths. I would comment out lines 80 to 83 as a test.
Bluetooth
=========
You have tons of errors with your bluetooth. If you view your logcat in color, these are all in red.
Code:
04-01 13:19:22.910 1212 1212 F DEBUG : *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
04-01 13:19:22.911 1212 1212 F DEBUG : LineageOS Version: '17.1-20210401-UNOFFICIAL-gt510lte'
04-01 13:19:22.911 1212 1212 F DEBUG : Build fingerprint: 'samsung/gt510ltexx/gt510lte:7.1.1/NMF26X/T555XXU1CQI8:user/release-keys'
04-01 13:19:22.911 1212 1212 F DEBUG : Revision: '8'
04-01 13:19:22.911 1212 1212 F DEBUG : ABI: 'arm'
04-01 13:19:22.912 1212 1212 F DEBUG : Timestamp: 2021-04-01 13:19:22+0200
04-01 13:19:22.912 1212 1212 F DEBUG : pid: 866, tid: 1203, name: bt_hci_thread >>> com.android.bluetooth <<<
04-01 13:19:22.912 1212 1212 F DEBUG : uid: 1002
04-01 13:19:22.912 1212 1212 F DEBUG : signal 6 (SIGABRT), code -1 (SI_QUEUE), fault addr --------
04-01 13:19:22.912 1212 1212 F DEBUG : Abort message: '[0401/131922.772914:FATAL:hci_layer_android.cc(119)] Check failed: btHci != nullptr.
When it crashes hard like above, there's no way bluetooth will work.
Again, if you are using the 17.1 msm8916-common repo, it's missing the bluetooth entries for manifest.xml and msm8916.mk.
For the manifest.xml you need something like
Code:
<hal format="hidl">
<name>android.hardware.bluetooth</name>
<transport arch="32+64">passthrough</transport>
<version>1.0</version>
<interface>
<name>IBluetoothHci</name>
<instance>default</instance>
</interface>
</hal>
For msm8916.mk, you need
Code:
# Bluetooth
PRODUCT_PACKAGES += \
[email protected]

[Sorry for the delay]
Okay, I think I ironed out most of the issues.
What is confirmed working:
- WLAN
- Bluetooth
- Audio
- GPS (though the initial fix took 30min+...)
What does not work
- SELinux
WLAN:
I see a messages like
wificond: No Offload Service available
wificond: Offload HAL not supported
wificond: Failed to get NL80211_ATTR_EXT_FEATURES
Click to expand...
Click to collapse
Is that an issue? I don't know...
I see a lot of messages from the PowerHAL:
QTI PowerHAL: Failed to acquire lock.
Click to expand...
Click to collapse
I already tried https://review.statixos.com/c/android_device_essential_mata/+/1626/1 but that apparently was not enough.
SELInux:
I added the policies by https://github.com/VirsysElectron/android_device_samsung_gt510wifi and made them work, but it seems they are not really working.
Example:
I/init ( 233): type=1400 audit(0.0:4): avc: denied { mounton } for path="/firmware-modem" dev="mmcblk0p25" ino=27 scontext=u:r:init:s0 tcontext=ubject_r:tmp_root_mount_file:s0 tclass=dir permissive=1
I/e2fsck ( 253): type=1400 audit(0.0:5): avc: denied { read } for name="mmcblk0p13" dev="tmpfs" ino=7580 scontext=u:r:fsck:s0 tcontext=ubject_r:efs_block_device:s0 tclass=blk_file permissive=1
I/e2fsck ( 253): type=1400 audit(0.0:6): avc: denied { open } for path="/dev/block/mmcblk0p13" dev="tmpfs" ino=7580 scontext=u:r:fsck:s0 tcontext=ubject_r:efs_block_device:s0 tclass=blk_file permissive=1
I/e2fsck ( 253): type=1400 audit(0.0:7): avc: denied { write } for name="mmcblk0p13" dev="tmpfs" ino=7580 scontext=u:r:fsck:s0 tcontext=ubject_r:efs_block_device:s0 tclass=blk_file permissive=1
I/e2fsck ( 253): type=1400 audit(0.0:8): avc: denied { ioctl } for path="/dev/block/mmcblk0p13" dev="tmpfs" ino=7580 ioctlcmd=127c scontext=u:r:fsck:s0 tcontext=ubject_r:efs_block_device:s0 tclass=blk_file permissive=1
I/init ( 1): type=1400 audit(0.0:9): avc: denied { relabelfrom } for name="rmt_storage" dev="debugfs" ino=6571 scontext=u:r:init:s0 tcontext=ubject_r:debugfs_rmt:s0 tclass=dir permissive=1
I/init ( 1): type=1400 audit(0.0:10): avc: denied { relabelfrom } for name="rmts" dev="debugfs" ino=6574 scontext=u:r:init:s0 tcontext=ubject_r:debugfs_rmt:s0 tclass=file permissive=1
Click to expand...
Click to collapse
I declare
/firmware-modem(/.*)? ubject_r:tmp_root_mount_file:s0
Click to expand...
Click to collapse
in device/samsung/gt510lte/sepolicy/file_contexts, but it is not applied:
dr-xr-x--- 3 system drmrpc ubject_r:vfat:s0 16384 1970-01-01 01:00 firmware-modem
Click to expand...
Click to collapse
And I really do not know enough about SELinux to effectively engage this.
@retiredtab: How did you solve SELinux in your builds for the T550?

RandomAndroidTinkerer said:
- GPS (though the initial fix took 30min+...)
Click to expand...
Click to collapse
That seems like a really long time. Did you go outside to do the GPS reading? Sometimes it makes a difference if you are in or outside. You should do an adb logcat while testing out GPS. It might show some clues as to why it takes so long.
With the P550 and using GPStest from
GPSTest | F-Droid - Free and Open Source Android App Repository
An app for testing GPS and GNSS capabilities of a device
f-droid.org
I get a lock in 48 seconds by the window.
RandomAndroidTinkerer said:
What does not work
- SELinux
Click to expand...
Click to collapse
You need to read posts 202 and beyond at
[ROM][SM-T350][UNOFFICIAL][crDroidAndroid-10.0][v6.17][ANDROID 10] Galaxy Tab A 8.0
Finally this thread is back :)
forum.xda-developers.com
I list the tools that you can use to help build selinux policies. As I wrote in the other thread, do you blindly trust the policies generated by the tools? I'm not an expert so I don't know and it's highly dependent on each hardware device.
I built an image with selinux enforcing as a test sometime in March and while it works, I'm not confident and ready to release that. In addition, each device will require it's own set of selinux policies. What might work for the P550 may not work on the T555 due to differences in hardware (LTE, S-pen).
Building the correct selinux policies is an iterative exercise. Wipe everything on your device, format data. Install the ROM only. You grant the initial batch of policies, reboot, look at logs, grant some more and repeat until they are gone. You should do this with the ROM only. Don't load gapps, games, apps, etc and then run selinux.
RandomAndroidTinkerer said:
Is that an issue? I don't know...
Click to expand...
Click to collapse
I see them in my own builds and so far there's been no problem.
RandomAndroidTinkerer said:
I see a lot of messages from the PowerHAL:
Click to expand...
Click to collapse
Same as above.
RandomAndroidTinkerer said:
I already tried https://review.statixos.com/c/android_device_essential_mata/+/1626/1 but that apparently was not enough.
Click to expand...
Click to collapse
You will find through experience and more building that what works for one platform may not work for another. It's highly dependent on the device and code specific to that device.
RandomAndroidTinkerer said:
SELInux:
I added the policies by https://github.com/VirsysElectron/android_device_samsung_gt510wifi and made them work, but it seems they are not really working.
Click to expand...
Click to collapse
In order to boot selinux enforcing, you need to remove line 140 from
android_device_samsung_msm8916-common/BoardConfigCommon.mk at lineage-17.1 · blizzard4591/android_device_samsung_msm8916-common
Common MSM8916 tree for Samsung devices. Contribute to blizzard4591/android_device_samsung_msm8916-common development by creating an account on GitHub.
github.com
Also, I'm not an expert in selinux, but I don't know why you would permit untrusted_app.te, untrusted_app_25.te and untrusted_app_27.te?

retiredtab said:
That seems like a really long time. Did you go outside to do the GPS reading? Sometimes it makes a difference if you are in or outside. You should do an adb logcat while testing out GPS. It might show some clues as to why it takes so long.
With the P550 and using GPStest from
GPSTest | F-Droid - Free and Open Source Android App Repository
An app for testing GPS and GNSS capabilities of a device
f-droid.org
I get a lock in 48 seconds by the window.
Click to expand...
Click to collapse
I think it was just the initial, first fix, and yes, I was not in the best position. Now that it knows where and when it is, a new fix even inside takes a couple of seconds. I used the same tool, also from F-Droid
retiredtab said:
You need to read posts 202 and beyond at
[ROM][SM-T350][UNOFFICIAL][crDroidAndroid-10.0][v6.17][ANDROID 10] Galaxy Tab A 8.0
Finally this thread is back :)
forum.xda-developers.com
I list the tools that you can use to help build selinux policies. As I wrote in the other thread, do you blindly trust the policies generated by the tools? I'm not an expert so I don't know and it's highly dependent on each hardware device.
I built an image with selinux enforcing as a test sometime in March and while it works, I'm not confident and ready to release that. In addition, each device will require it's own set of selinux policies. What might work for the P550 may not work on the T555 due to differences in hardware (LTE, S-pen).
Building the correct selinux policies is an iterative exercise. Wipe everything on your device, format data. Install the ROM only. You grant the initial batch of policies, reboot, look at logs, grant some more and repeat until they are gone. You should do this with the ROM only. Don't load gapps, games, apps, etc and then run selinux.
Click to expand...
Click to collapse
I had to load Magisk and LiveBoot to even get the early-boot log. Using ADB logcat I was unable to get a log from "system start" - the adb process would hang and wait for the device to be fully booted. Even afterwards, no messages from boot. I had USB debugging enabled, default USB conf "file transfer", etc.
Any ideas what I am doing wrong?
retiredtab said:
I see them in my own builds and so far there's been no problem.
Same as above.
You will find through experience and more building that what works for one platform may not work for another. It's highly dependent on the device and code specific to that device.
In order to boot selinux enforcing, you need to remove line 140 from
android_device_samsung_msm8916-common/BoardConfigCommon.mk at lineage-17.1 · blizzard4591/android_device_samsung_msm8916-common
Common MSM8916 tree for Samsung devices. Contribute to blizzard4591/android_device_samsung_msm8916-common development by creating an account on GitHub.
github.com
Also, I'm not an expert in selinux, but I don't know why you would permit untrusted_app.te, untrusted_app_25.te and untrusted_app_27.te?
Click to expand...
Click to collapse
Good catch - I simply copied the policies from VirsysElectron to start, but since they do not really work, I don't think I will continue much on this path. I share your opinion on old drivers and the greater picture. I had hoped the old policies would work for most of the basics, but they do not.

RandomAndroidTinkerer said:
I had to load Magisk and LiveBoot to even get the early-boot log.
Click to expand...
Click to collapse
For an eng build, there's no need for Magisk and LiveBoot to get an adb logcat. Part of the eng parameters is that it enables adb right away.
For developing selinux policies, you leave it in permissive first, develop the policies as I stated and then when you think you are done, then enable selinux enforcing. More at
Validating SELinux | Android Open Source Project
source.android.com
RandomAndroidTinkerer said:
Good catch - I simply copied the policies from VirsysElectron to start,
Click to expand...
Click to collapse
And that's the problem right there. It's so easy to kang or copy someone else's work today (legal or illegal) that some don't bother to check if it's right in the first place. I'm not saying VirsysElectron code is wrong, he may have a good reason why those files are generated.
I also fall into that boat. I use the public open source repos, but there's no way that I have the expertise or time to check everything in the repo for errors, security vulnerabilities, code correctness, etc.

retiredtab said:
For an eng build, there's no need for Magisk and LiveBoot to get an adb logcat. Part of the eng parameters is that it enables adb right away.
Click to expand...
Click to collapse
No, that is the problem - it did not. I am using eng-builds and, as I described, adb did not work, and I have no clue why.
retiredtab said:
For developing selinux policies, you leave it in permissive first, develop the policies as I stated and then when you think you are done, then enable selinux enforcing. More at
Validating SELinux | Android Open Source Project
source.android.com
Click to expand...
Click to collapse
I read that and some other introductions to SELinux, I get the general idea and concept - but as shown in my example, the labeling rule
/firmware-modem(/.*)? u: object_r :tmp_root_mount_file:s0
Click to expand...
Click to collapse
is not applied, I did not find anything that would tell me why or how to debug such an issue.
retiredtab said:
And that's the problem right there. It's so easy to kang or copy someone else's work today (legal or illegal) that some don't bother to check if it's right in the first place. I'm not saying VirsysElectron code is wrong, he may have a good reason why those files are generated.
Click to expand...
Click to collapse
I started writing my own policies from scratch (its somewhere in the repo history), but I first wanted to get my bearings, see how things work - ideally from a known, working starting point - which was a good idea, as otherwise the issue mentioned above regarding the labeling rule that does not get applied would have cost me much more sanity than just questioning someone else's code

Hello RandomAndroidTinkerer
I also own a T555, currently with TWRP 3.3.1 and LineageOS 16.0 from Virsys( 20191231). It's very stable, except the SIM didn't work.
Am of course interested in your image and would like to test it out. Which TWRP version do you use ?
Friendly greetings
Schaagi

Hallo RandomAndroidTinkerer,
thank you very much for your work and of course thanks for retiredtab and the others for their work This is my first post here and I you are the only one I found who builded an actual image. I'm very interested in testing your build. Could you send me an link, please? Thank you and bye bye.

Hi, I applied for an uploader account at AndroidFileHost, once this is granted I will upload a current build.

Current engineering build is up: https://www.androidfilehost.com/?w=files&flid=324776
I am using TWRP 3.1.0 from here.
Be kind on the feedback

RandomAndroidTinkerer said:
Current engineering build is up: https://www.androidfilehost.com/?w=files&flid=324776
I am using TWRP 3.1.0 from here.
Click to expand...
Click to collapse
For fun, I tried it on the P550 and not surprisingly, it doesn't boot. It doesn't even out adb logcat.
LineageOS also builds it's own recovery.img as another recovery option to TWRP. It's not as user friendly and lacks some features, but it's functional.

Thank you so much for your image - I am very excited to test it. Feedback follows in the next days.