Develop Bugs

[Kernel][7.1.1] SunKernel Pedigree Z5 for LineageOS [sumire]

A custom Kernel for LineageOS 7.1.1 based on the ideas and experiences of SunKernel corona (StockKernel) for Xperia Z5 series
XDA:DevDB Information
SunKernel Pedigree Z5 for LineageOS, Kernel for the Sony Xperia Z5
Contributors
zacharias.maladroit
Kernel Special Features: FauxSound, KCAL, reworked thermal engine, fast camera, etc.
Version Information
Status: Beta
Current Beta Version: 1.3
Beta Release Date: 2017-03-14
Created 2017-03-14
Last Updated 2017-08-30

Reserved
Changelogs:
14.1_I
initial release - Features:
Click to expand...
Click to collapse
14.1_I.2
changes ...
Click to expand...
Click to collapse
14.1_I.3
add throttling for orientation sensor input events (most likely NOT needed) to cut idle cpu high load of 15-20%
Click to expand...
Click to collapse
14.1_I.4
removed lots of sources for log-spam (dmesg/kernel-log)
BCL<-->KTM interface for BCL (battery_current_limit) driver is now used, faster, more reliable (less overlapping) and better hotplug during thermal events, etc.
more reliable bcl mitigation due to fresh SoC value, allowing frequency-based mitigation even with BCL set to off
MUCH improved sound output
more reliable sound playback
Click to expand...
Click to collapse

Reserved
Kernel Releases (Betas for now):
Link to custom LineageOS 14.1 build (patchlevel March 5th 2017)
not sure what differs between this and the other builds:
https://drive.google.com/open?id=0BykGGWB96CBQR1VIb3QtdGpsTmM
I initiated the fetch of the repo files via
lunch lineage_sumire-userdebug
and added the blobs repo,
then restarted the build ...
From now on
both LineageOS and Resurrection Remix are unified builds that work on Single SIM and Dual SIM devices - no separate kernel or ROM needed !
Resurrection Remix: already IS the unified build (thread is currently parked at the General Subforum: Resurrection Remix 5.8.2 for Xperia Z5 (unified build) )
LineageOS: please download the unified LineageOS builds from olivier: lineageOS ROM (as mentioned at: LineageOS thread )
those are NOT boot-tested but should work (need testing + feedback)

Reserved (3)
Notes:
The preamp of FauxSound or the actual sound/soc driver state seems to be a bit "mushy",
thus the white noise (swoosh-ing, hiss-ing) is a bit high - reduce headphone amp by 10 or 15 (-10 or -15) so that you get a clear and well-defined output,
it really depends on your headphones - with in-ear it is most likely more noticable.
This was with unmodified "stock"/"upstream" lineageOS kernel source and with a bit patched up - so nothing I can and will change
Kernel source:
https://github.com/zachariasmaladro...kami_r2/commits/Sun-Kernel_Pedigree_cm-14.1_I

Thanks, I hope you don't forget dsds variant.

It is a pleasure to have SunKernel in LineageOS.

Thanks @zacharias.maladroit
I will try after released stable LineageOS for dsds and SunKernel.

Flashing lineage and kernel, looking forward to try it
Thanks for upload

s.hossein said:
Thanks, I hope you don't forget dsds variant.
Click to expand...
Click to collapse
you have an up-to-date boot.img for dsds device ?
if yes, please upload

Thx! But After flashing this Kernel i couldnt Boot up. Stuck ar Boot Animation. But the Animation did not stopped.

Same here, bootloop, can u look up to this?
We are so glad you put efforts in custom kernel for lineage, looking forward for an update

zacharias.maladroit said:
you have an up-to-date boot.img for dsds device ?
if yes, please upload
Click to expand...
Click to collapse
I think the tree sources are unified so is there a need for special kernel for dsds? I'll try this one on my E6683.

stipi69 said:
Same here, bootloop, can u look up to this?
We are so glad you put efforts in custom kernel for lineage, looking forward for an update
Click to expand...
Click to collapse
please update to the lineageOS builds from Olivier,
unless he has uncommitted changes locally in his repos - there are no changes,
my lineageOS build is at patchlevel March 5th 2017,
so with recent changes the kernel (more precisely the ramdisk) might be incompatible with the old builds from @Myself5
balrajs99 said:
I think the tree sources are unified so is there a need for special kernel for dsds? I'll try this one on my E6683.
Click to expand...
Click to collapse
it might work, but you most likely run into a bootloop, too, if you're not using latest lineageOS builds (those from Olivier)

In this minute i downloaded fresh update, flashed in this order:
1. lineage-14.1-20170316-UNOFFICIAL-sumire
2. open_gapps-arm64-7.1-nano-20161104
3. UPDATE-SuperSU-v2.78-20160905010000
4. Z5_SK_Enf_v14.1_I.3_sum
lineage from olivier from below link:
https://dl.olivierk.at/sumire/lineage-14.1/
lineage-14.1-20170316-UNOFFICIAL-sumire
i still get bootloop, scren is dimed, lineage animation keeps going for couple of secs, screen goes bright and bootloop from there on, waiting 10+ minutes now... maybe old superuser zipfile for this task? dont know realy, will make clean install

zacharias.maladroit said:
it might work, but you most likely run into a bootloop, too, if you're not using latest lineageOS builds (those from Olivier)
Click to expand...
Click to collapse
Yes, on latest build by oliver it ran into bootloop.

actually this goes into bootloop, flashed latest olivier's lineageos.
edit : is there any proper order of flashing ? and can you share lineageos build that you are on ?

@zacharias.maladroit: Thank you a lot for your work. We should be very thankful to every developer on the Z5!
Just gave your Kernel a try on latest olivier's lineageos (0316). Got a bootloop. After 20 minutes, I did a power reset and dirty reflashed latest olivier's lineageos (0316) via TWRP. Telephone was functional again.

L33Tgod said:
actually this goes into bootloop, flashed latest olivier's lineageos.
edit : is there any proper order of flashing ? and can you share lineageos build that you are on ?
Click to expand...
Click to collapse
yes, currently uploading
I'd install LineageOS + gapps (opengapps),
go through all steps,
then go into TWRP, make a backup and attempt to flash the kernel.
I haven't flashed the ROM via zip,
I flashed it via the .img files and fastboot since the updater-script seemed to cause trouble ...
Link to custom LineageOS 14.1 build (patchlevel March 5th 2017)
not sure what differs between this and the other builds:
https://drive.google.com/open?id=0BykGGWB96CBQR1VIb3QtdGpsTmM
I initiated the fetch of the repo files via
lunch lineage_sumire-userdebug
and added the blobs repo,
then restarted the build ...
Click to expand...
Click to collapse
Can you guys post the content of the updater-script (in
Code:
tags), that works for you ?
I removed the assert line but it still didn't work for me,
also booting the stock ROM kernel via fastboot doesn't seem enough anymore,
it has to be flashed, then the VOL DOWN button pressed to reach TWRP on the recovery partition.
If you reach TWRP via a different method please let me know :)
Thanks

zacharias.maladroit said:
yes, currently uploading
I'd install LineageOS + gapps (opengapps),
go through all steps,
then go into TWRP, make a backup and attempt to flash the kernel.
I haven't flashed the ROM via zip,
I flashed it via the .img files and fastboot since the updater-script seemed to cause trouble ...
Can you guys post the content of the updater-script (in
Code:
tags), that works for you ?
I removed the assert line but it still didn't work for me,
also booting the stock ROM kernel via fastboot doesn't seem enough anymore,
it has to be flashed, then the VOL DOWN button pressed to reach TWRP on the recovery partition.
If you reach TWRP via a different method please let me know :)
Thanks[/QUOTE]
I flashed the rom by flashing pixn kernel then booting into twrp when purple led comes on and it flashes rom normaly and to access twrp later i have to use your stock kernel and type fastboot boot boot.img and it can go into recovery, but can't flash lineageos because of that error 7.
Click to expand...
Click to collapse

L33Tgod said:
I flashed the rom by flashing pixn kernel then booting into twrp when purple led comes on and it flashes rom normaly and to access twrp later i have to use your stock kernel and type fastboot boot boot.img and it can go into recovery, but can't flash lineageos because of that error 7.
Click to expand...
Click to collapse
yeah, that's why I wrote:
Can you guys post the content of the updater-script (in
Code:
tags), that works for you ?
I removed the assert line but it still didn't work for me,
also booting the stock ROM kernel via fastboot doesn't seem enough anymore,
it has to be flashed, then the VOL DOWN button pressed to reach TWRP on the recovery partition.
If you reach TWRP via a different method please let me know :)[/QUOTE]
might be that upstream changed the content of updater-script,
that's why I ask for a working variant ;)
Click to expand...
Click to collapse

[ROM][unified][4.4.4] OmniROM

OmniROM
[#KITKAT]
for Samsung Galaxy Nexus (Unified)
​
[#WHATSOMNI]
[#WARRANTY]
Downloads:
[#DLGITHUBIO]
[#INFOOMNI]
Specials added on top of Official OmniRom Source
All in One Animation Control
Battery Saver mode
On-The-Go mode
Implement App circle sidebar
follow dark 4.4 UI
Those features have never been ready for official Omni, but people spend a lot of time writing those features and i really like those.
I am trying to release an security update monthly after google publish android security bulletins.
Support development
[#DONATETOME]
XDA:DevDB Information
[unified][4.4.4] OmniROM, ROM for the Samsung Galaxy Nexus
Contributors
Android-Andi, Ziyan
Source Code: https://github.com/omni-security
ROM OS Version: 4.4.x KitKat
ROM Kernel: Linux 3.0.x
Version Information
Status: Stable
Current Stable Version: Final Build availabl
Created 2017-08-12
Last Updated 2017-08-18

Hello everyone, first of all, great work @Android-Andi thank you to take the time to support our old device !
And then sorry for my noob questions but :
- I didn't quite understand the difference between device specific and unified builds and I don't want to make a mistake flashing the wrong one.
- What is the main difference between Omni 4.4, Omni 6.0 or Slim 6.0? I want to use one of those but I don't know which one I think Omni 4.4 is the closest from what I had with the official Jelly Bean ROM and the 2 others are optimized version of Marshmallow. And is Slim 6.0 faster than Omni 6.0?
Thank you again

Radder124 said:
I didn't quite understand the difference between device specific and unified builds and I don't want to make a mistake flashing the wrong one.
Click to expand...
Click to collapse
Unified builts are for all types of tuna: Maguro, Toro, Toro+. When booting only the needed (device specific) drivers are loaded, but the drivers fir all supported devices are on board...

Unified works on all tuna variants: maguro, toro and toroplus at same time. It detects your variant on first boot and places needed files. That's the one I'll compile in future too.
Which rom is the best? Use the power of your TWRP and try it out. Test one, check if it fits your needs. If not, make a backup and try a different rom.

Android-Andi said:
Which rom is the best? Use the power of your TWRP and try it out. Test one, check if it fits your needs. If not, make a backup and try a different rom.
Click to expand...
Click to collapse
I can ask you a different question With all the new ROMs, I don't know which ROM you would like to receive bug reports from. Crash logs, etc. I know there is no point giving you CM12.1 crash logs. Which ROM would you like us testing and reporting bugs from?

Thank you for providing this ROM! I finally found a ROM with a working camera for the Gnex with security patches (from 2017-07).

...anyone gotten Xposed Framework installed/working with this? Halp

JLsoft said:
...anyone gotten Xposed Framework installed/working with this? Halp
Click to expand...
Click to collapse
There's somewhere an updated version flying around on XDA, maybe you'll find it (i don't have it anymore)

JLsoft said:
...anyone gotten Xposed Framework installed/working with this? Halp
Click to expand...
Click to collapse
try this

@Android-Andi is it possible to use this ROM with F2FS file system? Which DDK version is included in this ROM? Thank you for your contribution.

Those who are on 4.4:
AOSP Browser was removed for security reasons. Most lightweight Browser use KitKats webview which isn't up to date any more and there's ATM no proper way to update it.
You should use a browser which has its own webview implementation like Chrome, Firefox or Chromium.
From what I have tested Chromium seems to be a good solution. Here's my self compiled Chromium:
https://github.com/andi34/prebuilt_chromium/raw/master/ChromePublic.apk
(It's only missing h264 encoder for legal reasons...H.264 is not a free codec and I don't have the license for distributing)
For Android 5+
https://github.com/andi34/prebuilt_chromium/raw/master/ChromeModernPublic.apk
For Android 7+
https://github.com/andi34/prebuilt_chromium/raw/master/MonochromePublic.apk

New builds are up.
Switched to default libion, thx to @Ziyan and @amaces !
Note: don't flash any custom kernel on this build (also AnyKernel isn't compatible ATM)!

I've been away from the scene for a while so please catch me up. Does this rom bypass carrier limitations when using usb tether?

madspeed said:
I've been away from the scene for a while so please catch me up. Does this rom bypass carrier limitations when using usb tether?
Click to expand...
Click to collapse
Yep, these custom ROMs have nothing to do with carriers

March update is online. Enjoy!

Dear developer,
firstable many thanks for your Rom
I was using OMNI 4.4.4 dated 2015 but I was living issue with GMAIL, HANGOUT and GDRIVE
Today I discovered your product and Installed it on my MAGURO with a clean installation
Unfortunately after few hours I am suffering reboot
The system boots well but after few seconds it reboots itself ... continuosly ...
I am using omni_tuna-4.4.4-20180311-1556
I used GAPPS open_gapps-arm-4.4-pico-20180427
I rooted with SUperSU 2.82 R5
I tried to wipe cache, dalvik-cache, system and reinstall the rom and the gapps wo success
I tried to remove root wo success
HAve you some idea to help me ?
Thanks
Paolo
[EDIT]
I wiped all (clean installation) and installed the older version of rom (omni_tuna-4.4.4-20180128-0005)
[I noted that this version is bigger than the newer of around 30MB ...)
Same GAPPS af above
Same root of above
It runs well now ... cross the fingers and stay tuned

People having issues on latest build could try https://forum.xda-developers.com/showpost.php?p=76429699&postcount=188

The request from root was one of my suspect
Do you suggest to flash new kernel after last updated ROM, gapps and root and so before the first boot ?
Do you confirm that this workaround is not necessary with the previous version ?
Are you able to identify which version needs and which didn't ?
For instance I am using the January version .... Did I need to flash new kernel ?
Inviato dal mio Galaxy Nexus utilizzando Tapatalk

It could be it's needed on all KK roms since end of last year. But only works for latest builds using default libion.

Android-Andi said:
It could be it's needed on all KK roms since end of last year. But only works for latest builds using default libion.
Click to expand...
Click to collapse
Excuse my noob ... What does it mean default libion ?
Inviato dal mio Galaxy Nexus utilizzando Tapatalk

[ROM][4.4][EAS] Enchanted LineageOS 17.1 with 4.4 kernel

Enchanted LineageOS 17.1 with 4.4 Infinity EAS Kernel
Gemini forever alive!
Download:
TWRP with 4.4 kernel
LineageOS 17.1
Installation:
If you are on stock TWRP you need to flash 4.4 to avoid any problems like /data corruption!
You need to perform a factory reset (format /data)!
Flash rom, gapps/microG and optionally magisk.
Known bugs:
Camera hang in Snap when switching to HDR (click back button and open camera again, boom, it's working)
Join Mi5 group on Telegram
Please consider donating to my hard work
https://paypal.me/xNombre
XDA:DevDB Information
Enchanted LineageOS 17.1 with 4.4 kernel, ROM for the Xiaomi Mi 5
Contributors
xNombre
Source Code: https://github.com/xNombre
ROM OS Version: Android 10
ROM Kernel: Linux 4.x
Version Information
Status: Stable
Created 2020-01-06
Last Updated 2020-04-02

Reserved
Antutu Score

Reserved
¯\_(ツ)_/¯

Thanks for your hard work

hi
tanx 4 ur hard work
i want know about battery life plz..

install instruction?
and best frimware?
tanx

Can not change battery icon style it is stuck on Icon Portrait.

Hi @xNombre, just 2 quick questions regarding the the kernel used in your LOS release:
1- Does the kernel support HW Encryption? I remember on Havoc 2.9 (Android P) there was a port of 4.4 kernel with working HW crypto.
2- Will you release a standalone package of the infinity kernel in the future that can be used with other ROMs?
Thanks!

do we need jdc treble for this or what? since it "treble"

What about battery life?

can i flash other android 10 gsi based on this rom since it "treble"

immediately banned from telegram group right after joined. not even wrote a message or got a warning. interesting way to manage a community group.
i'll be around for feedbacks. thanks for your effort anyways.

nebik said:
Can not change battery icon style it is stuck on Icon Portrait.
Click to expand...
Click to collapse
It's LOS bug.
3V0LU710N said:
Hi @xNombre, just 2 quick questions regarding the the kernel used in your LOS release:
1- Does the kernel support HW Encryption? I remember on Havoc 2.9 (Android P) there was a port of 4.4 kernel with working HW crypto.
2- Will you release a standalone package of the infinity kernel in the future that can be used with other ROMs?
Thanks!
Click to expand...
Click to collapse
1. AFAIR not yet because it's not merged on LOS.
2. Probably no because there are too many custom changes made (dt & vendor) and I don't like listening to moaning that something is broken. I want to release more interesting ROMs some day (Syb... uhh ekh... eria).
shandianex1 said:
can i flash other android 10 gsi based on this rom since it "treble"
Click to expand...
Click to collapse
Hmmm, that's interesting question. I've only focused on making it fulfill all Android Q requirements concerning vendor separation (and such as APEX), not intended to make it GSI friendly. I guess there are still some incompabilities and you can't expect such and old device to be GSI friendly.

jackryder38 said:
What about battery life?
Click to expand...
Click to collapse
Test yourself, the biggest culprit about I can do nothing more is RIL. Maybe when Xiaomi releases Q for daisy, the blobs will make it better.
RmznDndr said:
immediately banned from telegram group right after joined. not even wrote a message or got a warning. interesting way to manage a community group.
i'll be around for feedbacks. thanks for your effort anyways.
Click to expand...
Click to collapse
The group is protected with antibot, I've checked your nickname and youre not banned for sure.

Enchanted LineageOS updated!
Changelog:
Merge latest kernel_common and CAF tag into kernel
Merge latest branch into qcacld driver
Use fq_codel queuing discipline, faster net
Update some blobs (those I have access to) from LA.UM.8.6.r1-02900-89xx.0
Remove unused move time data script
Add missing wifi mac generator
Fix USB tethering
Uprev Mapper to 2.1
Tweak Dalvik parameters accroding to new google configs
Go back to stock WiFi config and add some new Xiaomi edits - fixes connectivity problems
Rootdir updates
Minor cleanup
Fixup microG location
Massive overlay update from LA.UM.8.6.r1-02900-89xx.0
Selinux enforcing
Safetynet PASS!!!
Important LOS updates:
Fixed battery style
Updated to android 10.0 r23
Added survival script (magisk reflashes itself)
Repo sync all
Download via sf:
https://sourceforge.net/projects/xn...-17.1-20200119-UNOFFICIAL-gemini.zip/download
Please consider donating...
https://paypal.me/xNombre

xNombre said:
Enchanted LineageOS 17.1 with 4.4 Infinity EAS Kernel
Known bugs:
Speaker playing only left channel
5GHz hotspot
Camera hang in Snap when switching to HDR (click back button and open camera again, boom, it's working)
Click to expand...
Click to collapse
Fixed?

PavelPerm said:
Fixed?
Click to expand...
Click to collapse
Camera still hangs on HDR on/off. 5Ghz Hotspot works and about speaker i do not know.

nebik said:
Camera still hangs on HDR on/off. 5Ghz Hotspot works and about speaker i do not know.
Click to expand...
Click to collapse
Use this Gcam
https://easyupload.io/5ms9tu
It's version 7.2 - optimized and working 100% on gemini

PavelPerm said:
Fixed?
Click to expand...
Click to collapse
Not listed so not fixes, I thought it's clear.
New build could have some problems due to selinux change (dt2w or so) and I will push hotfix when I can.

xNombre said:
Not listed so not fixes, I thought it's clear.
New build could have some problems due to selinux change (dt2w or so) and I will push hotfix when I can.
Click to expand...
Click to collapse
I have problem with permission name (icon != Permission name)

[EOL][SODP][ROM][LineageOS][XZ2, XZ2C, XZ3] LineageOS 17.1 [STABLE][UNofficial]

The Sony Open Devices Project is always happy about volunteers (coding, testing, etc)
Also mainlining your favorite snapdragon powered xperia device into the mainline kernel is possible and we will be glad to help you!
Official site
Unofficial site
Code:
#include <std_disclaimer.h>
/*
*
* 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.
*
*/
This is the LineageOS ROM for the Sony Xperia XZ2 (akari), XZ2C (apollo) and XZ3 (akatsuki)
This ROM build will always mainly based on Code from Sony AOSP & LineageOS and maybe include cherry-picks.
I plan to make monthly builds, after a new security patch level, if there is no need for a critical hotfix.
FAQ:
Switch the A/B slot for every monthly release to make sure you execute the same amount of write cycles on the entire flash storage. (Extends hardware lifetime)
fastboot & adb
https://developer.sony.com/develop/open-devices/get-started/flash-tool/useful-key-combinations/
https://wiki.lineageos.org/adb_fastboot_guide.html
https://developer.android.com/studio/releases/platform-tools
Stuck at SONY logo? Maybe you need to flash the OEM binary to oem_a and oem_b, while just oem is not enough.
For a complete security patch you have to install the newest stock firmware and boot it once.
https://github.com/sonyxperiadev/bug_tracker/issues/258#issuecomment-445816826
TL;DR Flash the latest stockfirmware, boot it once, to update your baseband/mobile network drivers and then flash this ROM.
(I prefer and support only newflasher from XDA and xperifirm to download the firmware.)
Maybe this helps windows users:
https://developer.sony.com/posts/flash-tool-updated-with-new-feature/
jerpelea said:
for a complete security patch you have to
1. flash the stock firmware using https://developer.sony.com/develop/open-devices/get-started/flash-tool/
2. build and flash the ROM
* The security patch may affect or not the proprietary parts depending on HW and implementation
* After official support ends you can still get security updates for kernel and Android but loader and firmware will be stuck to the latest official release
Click to expand...
Click to collapse
Bugtracker:
SODP Bugtracker -> If you think the problem is in SODP
LineageOS Bugtracker -> If you think the problem is in LineageOS
My Bugtracker -> If you think the problem is in my implementation
Bugreport:
A bugreport needs
Code:
logcat -b all
and a way to reproduce the issue.
A crash of the system requires the content of the /sys/fs/pstore folder as bug report
Be aware that a second reboot erases this folder
A crash to the recovery partition requires additionally the content of the /dev/block/by-name/misc partition
You get the content via `cat /dev/block/by-name/misc partition > /path/to/output/file.txt`
To rescue a not responding phone:
VOLUP+POWER for 3 Seconds -> RESTART with one Vibration.
VOLUP+POWER for 20 Seconds -> SHUTDOWN with 3 Vibrations.
VOLUP+POWER+CAMERA for 30 Seconds -> HARDWARE SHUTDOWN by discharging a capacitor.
Thank you very much for your help, code contribution & testing! (Random order):
@jerpelea, the sony employees and their volunteers (people like you and me) coding this wonderful piece of software
@dhacke for providing a download server
@Raphos for the initial installation manual without a recovery system, after I switched to OTA zips.
@kgvarunkanth for the jenkins build server
And many thanks to the few donators!
A telegram group for technical SODP stuff:
Sony [*Kim Jong*Un]official OD Chat
https://developer.sony.com/develop/open-devices OEM binaries: @SMDW_downloads Bug Tracker: https://github.com/sonyxperiadev/bug_tracker This group is only for dev stuff. For support: https://t.me/xdadevelopershub
t.me
XDA:DevDB Information
LineageOS, ROM for the Xperia XZ2
Contributors
MartinX3, SODP Team
Source Code: https://github.com/MartinX3-AndroidDevelopment-LineageOS/
ROM OS Version: Android 10
ROM Kernel: Linux 4.x
ROM Firmware Required: Latest Stock Firmware
Based On: LineageOS
Version Information
Status: No Longer Updated
Current Stable Version: 17.1
Created 2020-02-02
Last Updated 2020-10-23

Download & Installation
Download ROM:
Android File Host
FTP-Server from @dhacke
Download Drivers:
OEM (Tama) binaries
Please use the the OEM build which came before my last release, unless otherwise written.
GCAM Camera App:
Suggested GCams But GCAM's aren't usable at the moment until a camera hardware resource budget bug got fixed in the OEM binary blob.
Installation with a recovery:
fastboot flash oem_a oem_*.img
fastboot flash oem_b oem_*.img
Flash the ROM in a recovery
Reboot into recovery just to make sure you're on the new slot
Google Apps like Playstore
Dual Sim Patcher
(In case a modification prevents your device from booting) fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
Flash the ROM without a recovery:
Extract the payload.bin from the .zip file
Extract the .img files with the Playload Dumper
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
fastboot flash dtbo_a dtbo.img
fastboot flash dtbo_b dtbo.img
fastboot flash system_a system.img
fastboot flash system_b system.img
fastboot flash vbmeta_a vbmeta.img
fastboot flash vbmeta_b vbmeta.img
fastboot flash vendor_a vendor.img
fastboot flash vendor_b vendor.img
fastboot -w (Wipes your internal storage and the userdata)
Continue with the normal installation

News
24.08.2020
since we have now an official lineageos based on stock, this rom would be double work.
So i stop the los port.
(sadly unless a dev owns a xz2p or xz3 these phones won't be supported in the official stock based lineageos)
the only difference between the stock and sodp editions are:
Sodp will get gcam support later and has camera2api level 3.
Stock will never support gcam apps and has the limited stock camera2api level.
Sodp uses a 4.14 kernel and probably get mainline support later.
Stock uses the stock 4.9 kernel and will probably be there forever.
Sodp targets to use as much open source as possible.
And livedisplay doesn't work in my sodp version.
Ps: After the september exams in the new semester i look for a rom replacement for the sake of diversity.
It's good to have a choice and with the available official supported sodp based pixel experiment, we have a rom which sadly forces you to use the full gapps (google apps package).
Click to expand...
Click to collapse
13.07.2020
july security patch level
oemv9c support
and any other sodp open source changes since my last build
Click to expand...
Click to collapse
18.06.2020
june security patch level
oemv8 support
and any other sodp open source changes since my last build
fixes for charger, battery, sleep (sideeffect working bluetooth audio) and more!
Click to expand...
Click to collapse
11.05.2020
may security patch level
oemv6 support
and any other sodp open source change since my last build
ps: Camera is work in progress.
Please flash gapps and the dual sim patcher again after applying an ota update.
It seems that the ota zip replaces every partition and deletes the modifications (like gapps).
Also it enforces avb heavily which prevents modifications like gapps from getting loaded.
So i deactivated avb now.
(but since the device bootloader can't be relocked the avb is not really useful anyway)
Click to expand...
Click to collapse
14.04.2020
now android 10.0.0_r33
april security patch level
oemv5 support
and any other sodp open source change since my last build
switched to:
zip files to flash
dual sim patcher instead of dual sim rom files
removed buildin gapps, since you can flash it now via twrp
installing this rom as an update won't remove the installed gapps.
ps: Camera is work in progress.
Click to expand...
Click to collapse
09.03.2020
march 2020 security update
oemv4 -> camera & other improvements
and any other lineageos / sodp open source changes since my last build
ps: Camera is work in progress.
Ps0:
Other than the aosp release, this lineageos got the new ril by qcom enabled for mobile network access.
Please test and report bugs. (dmesg & logcat, -> and pstore if the device crashes)
it will get activated in the next aosp release as well, if it makes no trouble.
Click to expand...
Click to collapse
01.03.2020
oemv4 is needed or device won't boot.
Oemv4 is not backward compatible with older releases.
oemv4 -> camera & other improvements
and any other lineageos / sodp open source changes since my last build
ps: Camera is work in progress.
Ps0:
Other than the aosp release, this lineageos got the new ril by qcom enabled for mobile network access.
Please test and report bugs. (dmesg & logcat, -> and pstore if the device crashes)
it will activated in the next aosp release as well, if it makes no trouble.
Click to expand...
Click to collapse
29.02.2020
added support for every sodp supported xperia https://github.com/martinx3-androiddevelopment-lineageos/
(except the loire and tone platform which no one requested.)
the oemv4 rom release will delay a bit.
Was in the need to delete my build cache for aosp and lineageos.
Click to expand...
Click to collapse
25.02.2020
need to take down the builds.
Oemv4 which comes tomorrow got some additional last minute changes today which needs a new rom compilation.
Click to expand...
Click to collapse
24.02.2020
oemv4 is needed or device won't boot.
Oemv4 is not backward compatible with older releases.
oemv4 -> camera & volte & other improvements
and an other lineageos / sodp open source changes since my last build
ps: Camera is work in progress.
Oemv4 maybe comes tomorrow.
Click to expand...
Click to collapse
15.02.2020
feburary security patch level
fixed bugs, now my sony aosp release and this lineageos port should contain the same amount of bugs (aside from the stuff on the lineageos part).
Switched from alpha to beta version.
The only instability i found on my own xz2 is a crash at night in flightmode without charger.
Anything else doesn't crash it here.
Might be various reasons.
If anyone has the same bug, please provide logs in my github issue tracker.
(and please look if your logs contain more informations than my logs).
Click to expand...
Click to collapse
02.02.2020
the first lineageos 17.1 build based on the sodp device trees.
My vanilla sodp release and lineageos should share the same bugs.
Plus bugs / missing features in lineageos and bugs introduced by myself porting sodp to lineageos :silly:
sadly i can't upload it at the moment to android file host.
Their new "stackpath" ddos blocking solution banned me, because i tried to upload the rom in 6 browser tabs. :silly:
fixed
have fun!
Ps: Camera is work in progress.
Twrp 10 is not ready, so i sadly can't start develop one for the xz2, xz2c, xz3.
https://twrp.me/site/update/2019/10/23/twrp-and-android-10.html
that's the reason i include opengapps pico for now.
And to use magisk, simply patch the boot.img by yourself in the magik manager app and flash it via fastboot.
Maybe you need to deactivate vbmeta, which wasn't the case at my site.
Gcam doesn't work with oemv3.
There is a library missing.
Click to expand...
Click to collapse

02.02.2020
The first LineageOS 17.1 build based on the SODP device trees.
My vanilla SODP release and LineageOS should share the same bugs.
Plus bugs / missing features in LineageOS and bugs introduced by myself porting SODP to LineageOS :silly:
Sadly I can't upload it at the moment to Android File Host.
Their new "Stackpath" DDOS blocking solution banned me, because I tried to upload the ROM in 6 browser tabs. :silly:
Fixed
Have Fun!
PS: Camera is work in progress.
TWRP 10 is not ready, so I sadly can't start develop one for the XZ2, XZ2C, XZ3.
https://twrp.me/site/update/2019/10/23/twrp-and-android-10.html
That's the reason I include OpenGapps Pico for now.
And to use Magisk, simply patch the boot.img by yourself in the magik manager app and flash it via fastboot.
Maybe you need to deactivate vbmeta, which wasn't the case at my site.
GCAM doesn't work with OEMv3.
There is a library missing.
Click to expand...
Click to collapse

Nice work Martin!!!
I had looked forward to be released this rom
And i have a question to you.
Does this rom support VoLTE?

Orihamburger said:
Nice work Martin!!!
I had looked forward to be released this rom
And i have a question to you.
Does this rom support VoLTE?
Click to expand...
Click to collapse
Thank you
Yes, at least I can use VoLTE in my country with my provider.
You need to test it by yourself. [emoji14]

I need some help from testers for logs and observed behavior.
It seems that the phone crashes while sleeping in combination with the installed firmware on my XZ2.
Does this crash only happen when someone upgraded his phone to stock 10.0 first or does it also happen with a previously installed stock 9.0 rom?
https://github.com/MartinX3-AndroidDevelopment-LineageOS/bug_tracker/issues/1

MartinX3 said:
I need some help from testers for logs and observed behavior.
It seems that the phone crashes while sleeping in combination with the installed firmware on my XZ2.
Click to expand...
Click to collapse
I had the same on PE.
PE rom flashed over latest stock firmware, then latest aosp oem binary.
And always when I Iock phone for some time, impossible to wake up it. Only restart helps using volup+power.
P.S. now i'm on stock.

zhka said:
I had the same on PE.
PE rom flashed over latest stock firmware, then latest aosp oem binary.
And always when I Iock phone for some time, impossible to wake up it. Only restart helps using volup+power.
P.S. now i'm on stock.
Click to expand...
Click to collapse
Thank you
I'm curious if it is the same issue.

hi martin, thanks a lot for your work, a question, in this version the general stability of this rom is the same of your sonyaosp project? i will try today or tomorrow

nikkdib said:
hi martin, thanks a lot for your work, a question, in this version the general stability of this rom is the same of your sonyaosp project? i will try today or tomorrow
Click to expand...
Click to collapse
Thank you, you're welcome
In theory it only contains bugs from SODP and LineageOS :silly:

MartinX3 said:
Thank you, you're welcome
In theory it only contains bugs from SODP and LineageOS :silly:
Click to expand...
Click to collapse
ok i try to flash. now i have stock bugged android 10 firmware
edit: ok i flashed this rom and for now my phone seems doesn't crashed or freeze. i try to install gcam but gcam crash

nikkdib said:
ok i try to flash. now i have stock bugged android 10 firmware
edit: ok i flashed this rom and for now my phone seems doesn't crashed or freeze. i try to install gcam but gcam crash
Click to expand...
Click to collapse
Gcam should work with OEMv4
There is a library missing to run this application.

The XZ3 Dual file is corrupted. It is only 50MB in size

nickholtus said:
The XZ3 Dual file is corrupted. It is only 50MB in size
Click to expand...
Click to collapse
Thank you, but the dual sim version only contains the files different from the single sim version.

MartinX3 said:
Thank you, but the dual sim version only contains the files different from the single sim version.
Click to expand...
Click to collapse
Ahhh damnn, sorry my fault! Stupid mistake

Very promising release=) However, I need your help, Bro, cause I'm officially stuck with the stock=))) Before I used your OMNI for 6 months and it was completely fine just the camera wasn't working at all regardless of any fixes I've tried! After that, I switched my H8266 xz2 Dual to your SODP to try Android 10, which I didn't like after playing with it for a while. And now - I flashed latest 52.0.A.8.131 or newer 52.1.A.0.532 for the US device - I COULDN'T find the correct twrp as well as I CAN'T install OMNIrom. I have a simple question ==> besides the stock, which rom is stable enough here to have a working camera and TWRP. From what I see, almost each rom has some issues. Instead of Lineage 17, could you fix the links for working 16th version? FIX me if I'm wrong=)))

Mazurik said:
Very promising release=) However, I need your help, Bro, cause I'm officially stuck with the stock=))) Before I used your OMNI for 6 months and it was completely fine just the camera wasn't working at all regardless of any fixes I've tried! After that, I switched my H8266 xz2 Dual to your SODP to try Android 10, which I didn't like after playing with it for a while. And now - I flashed latest 52.0.A.8.131 or newer 52.1.A.0.532 for the US device - I COULDN'T find the correct twrp as well as I CAN'T install OMNIrom. I have a simple question ==> besides the stock, which rom is stable enough here to have a working camera and TWRP. From what I see, almost each rom has some issues. Instead of Lineage 17, could you fix the links for working 16th version? FIX me if I'm wrong=)))
Click to expand...
Click to collapse
Thank you
At the moment the source code of TWRP 10.0 is not available/usable, but is needed to create a TWRP with the 10.0 code environment.
Why you can't install omnirom?
The TWRP only work for the 9.0 ROMs at the moment and will be fixed in the future.
The LineageOS 16.0 release wasn't made by me and I can't do anything (except creating my own LineageOS 16.0 but my time/ressources are sadly limited :silly

does anyone know how well gcam works compared to stock camera on locked device?

tb_ said:
does anyone know how well gcam works compared to stock camera on locked device?
Click to expand...
Click to collapse
The camera driver is work in progress
The gcam workarounded missing features on 9.0.
Now on 10.0 we need to wait for OEMv4 for a working gcam.

[ROM] [10.0] [STABLE] [walleye] Dirty Unicorns 14.6 [UNOFFICIAL]

ROM VERSION: 14.6
Device: Google Pixel 2
Build Type: UNOFFICIAL
Code:
* Your warranty is now void.
* We are not responsible for anything that may happen to your phone by installing any custom ROMs and/or kernels.
* You do it at your own risk and take the responsibility upon yourself and you are not to blame us or XDA and its respected developers.
CLEAN FLASH :
Download the latest build (Pixel Gapps included)
Reboot to recovery
Wipe System, Data, Dalvik
Flash the latest build
Reboot
DIRTY FLASH :
Download the latest build
Reboot to recovery
Flash the latest build
Wipe Cache
Reboot
Latest build
Kernel Source:: https://github.com/gibranmather/android_kernel_google_wahoo
Device Tree:: https://github.com/gibranmather/abc_device_google_walleye
XDA:DevDB Information
Dirty Unicorns , ROM for the Google Pixel 2
Contributors
gibranm
Source Code: https://github.com/gibranmather/android_kernel_google_wahoo
ROM OS Version: Android 10
ROM Kernel: Linux 4.x
ROM Firmware Required: May Firmware
Based On: AOSP
Version Information
Status: Stable
Current Stable Version: 14.4
Stable Release Date: 2020-06-08
Created 2020-05-29
Last Updated 2020-06-08

Stock kernel provides a balanced experience in terms of battery and smoothness.
For users who want a lightweight efficient kernel with great battery gains, I would strongly recommend Sultans kernel.
For user who want a bit more customisations from their kernel, I would suggest Flar2's elemental x.

Reserved
This rom provides a lossless pixel experience with extra features and customisations.
All pixel features working: Active Edge, Now Playing, Google Assistant
All sensors are working
Safetynet passes by default
Widevine L1 DRM present for hd video
Kernel is unicornblood for taimen with commits to enable touch on walleye.
TWRP will not be able to decrypt if you have a pin. So only disable pin when you need to use twrp

Thank you for keeping walleye alive!! So far everything is working good.

Pretty stable ROM!! Thanks a lot!

14.4 update is compiling right now. Will release soon

14.4 Out
14.4 Changelog:
June ASB merged
Kernel upstreamed with asb merged
Redesigned front end of tweaks app

gibranm said:
14.4 Changelog:
June ASB merged
Kernel upstreamed with asb merged
Redesigned front end of tweaks app
Click to expand...
Click to collapse
@gibranm THREAD CLOSED! Placeholder are not accepted.
Please advise the moderators' team (best via the report function) to re-open the thread when ready to provide a download link.

New Build 11/08/20
Dirty Unicorns have returned to XDA, hence the thread reopening. Here is du 14.6 for walleye.
Changelog:
- Merged in August's security update
- Add option to hide clock on home screen
- Add in the Caviar Dreams font
- Added various AOSP fixes to improve the overall experience
- Device specific fixes where applicable
- Imported French translations
Latest build

gibranm said:
Dirty Unicorns have returned to XDA, hence the thread reopening. Here is du 14.6 for walleye.
Changelog:
- Merged in August's security update
- Add option to hide clock on home screen
- Add in the Caviar Dreams font
- Added various AOSP fixes to improve the overall experience
- Device specific fixes where applicable
- Imported French translations
Latest build
Click to expand...
Click to collapse
CLEAN FLASH :
Download the latest build (Pixel Gapps included)
Reboot to recovery
Wipe System, Data, Dalvik
Flash the latest build
Reboot
Sorry for the maybe dumb question. Do i have to flash it to both slots A and B? Not mentioned above. Is there a how to?
It's my first Pixel 2 after many years of Nexus Phones. THX
PS: I'm @ abc Rom (Bill Blandford) atm

MontiBurn said:
CLEAN FLASH :
Download the latest build (Pixel Gapps included)
Reboot to recovery
Wipe System, Data, Dalvik
Flash the latest build
Reboot
Sorry for the maybe dumb question. Do i have to flash it to both slots A and B? Not mentioned above. Is there a how to?
It's my first Pixel 2 after many years of Nexus Phones. THX
PS: I'm @ abc Rom (Bill Blandford) atm
Click to expand...
Click to collapse
No need. If you have twrp, reboot to recovery and follow instructions. Don't forget to flash twrp zip after ROM zip

gibranm said:
No need. If you have twrp, reboot to recovery and follow instructions. Don't forget to flash twrp zip after ROM zip
Click to expand...
Click to collapse
Thanks! Stock Rom needed before or just over my current Rom?

No. As long as you are on June firmware and have twrp. Follow the instructions and flash twrp zip

gibranm said:
No. As long as you are on June firmware and have twrp. Follow the instructions and flash twrp zip
Click to expand...
Click to collapse
Hey there, is the June firmware required or will July/August work as well?

Shamestick said:
Hey there, is the June firmware required or will July/August work as well?
Click to expand...
Click to collapse
June or newer will be fjne

gibranm said:
June or newer will be fjne
Click to expand...
Click to collapse
Awesome I appreciate your quick reply, my friend. I also hopped over to the official Taimen thread and your comment was confirmed.
Have had my Pixel 2 for over 2.5 years now and never flashed a custom rom (previous flashaholic on all previous devices ) but I think I may just take this for a spin over the weekend and see how it goes. Always loved DU.

Does anyone use / willing to try installing LMT pie?
This is the first time I've had any problems, but it's granted all the accesses it needs and comes out but the commands won't work. Curious if others have the same.
Sent from my [device_name] using XDA-Developers Legacy app
---------- Post added at 08:46 AM ---------- Previous post was at 08:42 AM ----------
The build is running great otherwise!
Sent from my [device_name] using XDA-Developers Legacy app

Can't use screen mirror or screen cast to Roku tv seems like a kernel crash but can't catch a log as I have another issue I can't tell if ROM related or hardware related so till then screen cast is only issue I have

Tried to download Latest Build. Have to Login with G-Account and send the request. Getting immediately
Delivery Status Notification (Failure)
, can't be send how do i get this rom? @du Homepage only Pixel2 XL is available. Will there be updates?