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
Related
Introduction
NOTE:
Hello everyone, this is my first kernel for the Moto G4 Plus. I will try to maintain a stable kernel however bugs might arise since I'm not a super star kernel developer. I hope you enjoy the releases.
Important information
I will not reply to complains that do not include clear steps to reproduce the bug, a logcat, and a console ramoops (if random rebooting) or a dmesg (any other issues). Follow this guide to do this.
Features
Here are the major features of the kernel (feel free to explore Github)
Update to date with the latest Linux upstream version (3.10.108-EOL)
Westwood as the default congestion algorithm with many more to choose from
Several subsystems converted to use power efficient workqueues
Compiled with Google's arm-eabi 4.9 toolchain
Audio control from flar2
Downloads
Oreo 8.0 : https://sourceforge.net/projects/babyfish-kernel/files/athene/oreo_caf/
Nougat 7.1 : https://sourceforge.net/projects/babyfish-kernel/files/athene/nougat_caf/
Nougat 7.0 Stock :https://sourceforge.net/projects/babyfish-kernel/files/athene/stock_nougat/
Installation:
NOTE: Please make sure that you return to the stock kernel of the ROM before flashing this kernel. The kernel is unified for Moto G4 and the Plus variant so everything should be working fine.
Install the latest adb and fastboot: https://developer.android.com/studio/releases/platform-tools.html#download
Grab the boot image from the download links above
Method 1:
Using adb and fastboot
Reboot into the bootloader using either restart and hold power button and volume down or adb:
Code:
adb reboot bootloader
Flash the boot image. Run the following command in the folder with the boot image and ensure fastboot is in your PATH:
Code:
fastboot flash boot <boot_image_name>.img
Reboot and profit!
Method 2: TWRP
Keep the bootimage on your phone's storage and boot to TWRP.
Install > Select Install Image > Choose the image > Boot partition > Reboot
Changelog
28 November 2017
Oreo-CAF:
Code:
Initial Release
Introduce Tossug Baby Fish kernel
Add Sound Control
Add TCP congestion algos
Disable crc check for 30% performance improvement in I/O
Linux 3.10.108
Nougat-CAF:
Code:
Initial Release
Introduce Tossug Baby Fish kernel
Add Sound Control
Add TCP congestion algos
Disable crc check for 30% performance improvement in I/O
Linux 3.10.108
Stock N:
Code:
FAQs
1.1 Q Can you help me I have this problem?
1.1 A I will surely try to help if proper bug reporting is done as per the fashion described above.
1.2 Q: Can you add xyz feature?
1.2 A: If you link me the commits or tell me what kernel you had the feature in, I can take a look at them. I will not add any useless governors or features that I don't find practical.
1.3 Q: How do I control the kernel?
1.3 A: I recommend using EX Kernel Manager or Kernel Auditor (Both need root)
1.4 Q: OMFG MY BATTERY SUXXXX PLS FIX!!!
1.4 A: The kernel doesn't drain any battery unless you have overclocked it, I have kept it at stock frequencies and voltages. Use an app like BetterBatteryStats to figure out what app is screwing with your phone.
Thanks to:
The various other developers for their patches (if you want a specific mention, please let me know)
All of you guys for viewing the thread
Thiago Neves @lcrd512 and Abhijeet Bohra.
Kernel source links.
8.0.0 CAF : https://github.com/tywinlannister7/android_kernel_motorola_msm8952/tree/oreo_caf
7.1 CAF : https://github.com/tywinlannister7/android_kernel_motorola_msm8952/tree/nougat_caf
7.0 Stock :
If you like my work, buy me an Appy Fizz or whatever you like
https://www.paypal.me/tywinlannister7 :good:
XDA:DevDB Information
Reviver Kernel, Kernel for the Moto G4 Plus
Contributors
tywinlannister7
Source Code: https://github.com/tywinlannister7/android_kernel_motorola_msm8952
Kernel Special Features:
Version Information
Status: Stable
Created 2017-11-28
Last Updated 2018-12-10
Screenshots
Some Screenshots
Will work on LOS, right? Sorry for asking this nooby question. I just want to be confirm before flashing. ?
tywinlannister7 said:
Some Screenshots
Click to expand...
Click to collapse
Which ROM is this?
Ayan Uchiha Choudhury said:
Which ROM is this?
Click to expand...
Click to collapse
DU 12 oreo
@tywinlannister7 Any plans on making some Device Specific ROM for Athene.? Since Invicta is out of scene now.
Thanks for the new addition in the family.
I hope this will be the favorite member of the family:laugh:
Where is the love for stock user?
thorin0815 said:
Where is the love for stock user?
Click to expand...
Click to collapse
There is a link for stock rom in the op though?
thorin0815 said:
Where is the love for stock user?
Click to expand...
Click to collapse
Stock version won't be released any sooner. I don't have the time for it right now and compilation process of stock kernel is a bit different than CAF kernels. Maybe before the second week of January.
briatide said:
There is a link for stock rom in the op though?
Click to expand...
Click to collapse
Empty as of now
ganeshkmr21 said:
@tywinlannister7 Any plans on making some Device Specific ROM for Athene.? Since Invicta is out of scene now.
Click to expand...
Click to collapse
IDK I don't have the time, we already have so many ROMs available. Creating a new ROM will be adding it to the huge list already available, from AOSP to LineageOS to Dirty Unicorns. I would rather work on optimizing what we have. Quality > Quantity.
jyoti.id said:
Will work on LOS, right? Sorry for asking this nooby question. I just want to be confirm before flashing.
Click to expand...
Click to collapse
Yes. 7.1 version for all N custom ROMs and 8.0 for all the O custom ROMs
DU 12 oreo
Blueman1990 said:
DU 12 oreo
Click to expand...
Click to collapse
about DU 12 oreo where can i get it ?
many thanks
i love new system
Does not boot on LOS15. Can anyone else confirm? Cant do logs cause my data port on my phone is broken. It sits on the boot screen like its loading but never fully boots.
Thank you bro!! finally an oreo kernel!
Where I can get DU 12?
Does this have color management?
And which kennel manager should i use with this?
Thanks
harshal2234 said:
Where I can get DU 12?
Click to expand...
Click to collapse
Its not out yet I guess
---------- Post added at 01:35 PM ---------- Previous post was at 01:33 PM ----------
Ashishliterally said:
Does this have color management?
And which kennel manager should i use with this?
Thanks
Click to expand...
Click to collapse
Bro its just a 2 page thread. At least read. That question has been answered, in the OP!
Can't I get the unofficial build?
Tried it but I got bootloop.
Using latest Resurrection Remix Rom With Stock kernel on XT-1643.
Missed the logcat.
Should I have to flash the magisk again after installing kernel?, may be this was the reaseon I got bootloop because boot.img was changed and again installing magisk could help with that.
Same for me. On LOS 14.1, XT1643
---------- Post added at 05:17 PM ---------- Previous post was at 05:16 PM ----------
ramansehra said:
Tried it but I got bootloop.
Using latest Resurrection Remix Rom With Stock kernel on XT-1643.
Missed the logcat.
Should I have to flash the magisk again after installing kernel?, may be this was the reaseon I got bootloop because boot.img was changed and again installing magisk could help with that.
Click to expand...
Click to collapse
I don't think so. If magisk is installed/flashed once, then no need of flashing ever again until you freshly install the rom. (AFAIK)
ramansehra said:
Tried it but I got bootloop.
Using latest Resurrection Remix Rom With Stock kernel on XT-1643.
Missed the logcat.
Should I have to flash the magisk again after installing kernel?, may be this was the reaseon I got bootloop because boot.img was changed and again installing magisk could help with that.
Click to expand...
Click to collapse
Same happened with me I was on Invicta os 8.0
Hey there,
good news for everyone who is missing the great JDC Nougat!
With smeroni68's authorization I'm offering you the latest version of the ROM, built from source, with some changes to keeping it up to date and maintained.
These changes are:
Latest security bulletins and changes from AOSPKernel upstreams from Linux StableUpdates from Code Aurora Forum (CAF)Some smallish modifications of standard apps or behavior
All credit goes to the JDC team!
(Check attachment for a list of team members).
They are the geniuses behind this awesome ROM and kernel, and I'm only making basic and minor modifications to it.
Besides a huge thanks to each member of the JDC team, thanks to Google, Lineage, Linux, CAF, Github & everyone else involved!
And many thanks also to DennySPB who helped me a lot with all the building stuff!
Have fun and enjoy!
Downloads
ROM / Kernel
Hashes
Recommended firmware
Last and latest Oreo firmware for our Mi 5:
8.11.22
ROM installation
Install latest TWRP
Make backups and store them externally
Wipe dalvik, cache, system, vendor, data
When coming from any android version other than Nougat 7.1.2:
Make external backups of your internal storage content
Format data (type "yes" way)
Reboot to recovery to access the data partition correctly again
Flash adequate firmware
No reboot in between the following and the optional steps
Flash ROM
Optionally:
Flash Gapps for 7.1.x arm64. I recommend OpenGapps Pico with additions (1) OR Stock with gapps-config.txt file (2):
(1) Flash Gapps additions (for example these by @Deltadroid)
(2) Check post_#128
Flash ThemeReady GApps package for Nougat arm64 (I don't)
Flash root (Latest Magisk is working fine for me)
After the first boot
Follow the gapps assistant (in case you installed gapps)
Wait 2 - 5 minutes to let everything settle in
Reboot to system
Kernel installation
You'll only wanna install the kernel separately when there's a kernel-only update later than the last ROM version!
Wipe dalvik and cache
Flash the kernel zip-file
Optionally: Re-flash root (if you were rooted before or now wanna be rooted)
GPL
All repos are forked from AOSP-JF-MM or LineageOS
Device tree source code:
https://github.com/PhilSmith31/platform_device_xiaomi_gemini/tree/aosp-7.1.2_r36
Kernel source code:
https://github.com/PhilSmith31/platform_kernel_xiaomi_msm8996/tree/bb
XDA:DevDB Information
AOSP, ROM for the Xiaomi Mi 5
Contributors
Phil_Smith
Source Code: https://github.com/PhilSmith31
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.x
ROM Firmware Required: 8.1.18
Based On: AOSP
Version Information
Status: Stable
Created 2018-08-28
Last Updated 2020-03-20
Changelogs
20.03.2020
March 2020 security updates from LineageOS
Synced Lineage repos
Kernel is up to date with relevant commits to android/common
02.03.2020
Security bulletins up to Februrary 2020 (no more source.android updates coming from here on)
Updated everything in aosp.xml to latest android tag r39
Updated HALs and all externals under CAF to tag LA.UM.5.5.c25-04600-8x96.0
Upstreamed kernel with all changes to android/common up to date
Merged LA.UM.5.5.c25-04600-8x96.0 into qcacld-2.0
Synced Lineage repos
Kicked opencv
Kernel compiled with latest Linaro toolchain 7.5.0
17.09.2019
ROM:
Security updates from August and September 2019
Merged in CAF tag LA.UM.5.5.c25-03100-8x96.0 into externals, hals, and some vendors
Synced system/gatekeeper with LOS
Kernel:
B--B-Kernel-N-[2019-09-17]-[20:17]-Mi5
From now on always also present in kernel_only folder
Cherry-picked all relevant aosp's kernel/common/android-3.18 commits up to date
Merged in security related changes from aosp
Merged CAF tag LA.UM.5.5.c25-03100-8x96.0 into qcacld-2.0
Wrote simple python script to filter out warnings from compile output
Check extract_warnings.py and changes to build_kernel.sh
Vendor/aosp:
Monitor changelog under Dropbox link only
all changelogs
.
FAQ
I'm having general problems with the ROM installation or don't know what steps to perform to move from x to y or to restore or undo z. What shall I do, Dr. Phil?
Dr. Dr. Phil said:
First read the intro and then see whether your problem is covered here:
Standard Installation Types
Still issues? Then feel free to post in this thread!
Click to expand...
Click to collapse
Gcam mod has green lines in portrait mode or even in general
Dr. Dr. Phil said:
Settings -> advanced -> Fix Camera API2 -> support level override
and set it to "Zsl reprocessing"
Click to expand...
Click to collapse
Gcam mod video recording is force closing all the time.
Dr. Dr. Phil said:
This problem is present in Arnova's cam versions > 8, while photo shooting is working fine with the support level override fix above. You could use stock camera for video recording or use Arnova's gcam mod in versions 7.9 till 8.
Click to expand...
Click to collapse
Proximity sensor lets the screen get black while making a phone call
Dr. Dr. Phil said:
Use the recommended firmware (Oreo 8.11.22).
If that doesn't help, here is a fix that I used once successfully when I had the same problem.
Thanks to Mi5 Arsenal!:
flash zcx twrp
make a backup of your persist partition (let's call that x)
store x externally in case the fix shouldn't work or make anything worse (which I don't believe, but still)
download this zip file and place it where x had been stored (replace x with it)
hit restore in twrp, and select the new backup file you just put in place where x was
reboot to system
You can switch to official twrp afterwards without any problem!
Click to expand...
Click to collapse
Xposed isn't working or producing issues, what to do?
Dr. Dr. Phil said:
In my experience, xposed is very powerful, but can produce all kinds of weird and untraceable behaviour.
I don't recommend using it if not completely nessecary, and cannot support it.
Click to expand...
Click to collapse
Reserved
Hi mate... thanks for your dedication on our work!
Inviato dal mio Xiaomi Mi5 utilizzando Tapatalk
This is exactly what I was looking for N Rom with latest patches:laugh: .Ty so much for your work, will try it soon. :laugh:
What is for boot.img?
XxFatiHxX said:
What is for boot.img?
Click to expand...
Click to collapse
Just so you could flash back stock kernel separately.
Nothing you need for the ROM installation.
Thanks for this great work! Can I dirty flash it on latest original JDC nougat? And can I flash B-B Kernel or better not to do this?
ERRORR2 said:
Thanks for this great work! Can I dirty flash it on latest original JDC nougat? And can I flash B-B Kernel or better not to do this?
Click to expand...
Click to collapse
You should be able to dirty flash, although I think that a clean flash is advisable.
B-B-kernel should be working, but keep in mind that I am gonna keep updating the stock kernel and the B-B one is getting more and more outdated.
Edit:
This info is outdated!
B--B-kernel is even built into the ROM now!
The ol' but gold rom has waken up from long sleep
This rom is eas or hmp ?
Kyru said:
This rom is eas or hmp ?
Click to expand...
Click to collapse
EAS
Phil_Smith said:
EAS
Click to expand...
Click to collapse
Will it work with latest beta firmware ?
Will try soon
Kyru said:
Will it work with latest beta firmware ?
Click to expand...
Click to collapse
I would suggest Nougat-based firmware, but maybe on Oreo-based everything is working as well - can't say.
You need to try that out (on your own risk).
Thanks very much @Phil_Smith
Finally.. must try this one.. thanks @Phil_Smith
I can't believe this is perfect.
Can you add more status bar customizations?
Does alarm from switched off work with this rom?
Inviato dal mio MI 5 utilizzando Tapatalk
This Thread is deprecated!
Please use https://forum.xda-developers.com/sony-xperia-z1-compact/development/rom-lineageos-15-1-xperia-z1-compact-t3884247/
We'll provide Lineage 15.1 builds there as well. They come in two different flavours:
pure LineageOS
Security hardened microG LineageOS
Functionality is completely the same as provived by the builds from this thread - they are build from the same sources. Only difference: The new builds are signed to guarantee a maximum of security.
Code:
#include <std_disclaimer.h>
/*
* 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. Hard & a lot.
*
*/
Status
List template by AdrianDC
Code:
- Boot : Ok
- GApps : OpenGApps Micro recommended
- Partitions (Data, Cache) : Ext4 and F2FS supported
- Bluetooth : Ok
- WiFi : Ok
- WiFi Hotspot : Ok
- RIL - Phone - Data : Ok
- GPS : Ok
- Camera : Ok
- Camcorder : Ok
- Lights : Ok
- MicroSD : Ok
- Accelerometer : Ok
- Compass : Ok
- Gyroscope : Ok
- Touchscreen : Ok
- FM Radio : Ok
- ANT+ : Ok
- Vibrator : Ok
- Microphone : Ok
- Audio & music : Ok
- Bluetooth audio : Ok
- MHL: didn't test
- NFC : Ok
- Kernel : Ok
- Graphics : Ok
- 3D Rendering : Ok
- Clock : Ok
- Offline Charging : Ok
- USB : Ok
- USB OTG : Ok
- Encryption : Ok, but installing updates only works with adb sideload!
- SEPolicies : Enforcing
Download
https://androidfilehost.com/?w=files&flid=269301
latest version: https://www.androidfilehost.com/?fid=11410963190603873784
Click to expand...
Click to collapse
FAQ
What about device encryption?
Device encryption is working. You only have to keep in mind that you need a PC with adb to install systemupdates.
Flashing via recovery isn't working until now, because there isn't a recovery capable of decrypting Oreo /data partitions at the moment. But an easy "adb sideload" should do the job. Or installing from the external SD card.
Click to expand...
Click to collapse
What about reboot to recovery?
Reboot to recovery is only working with magisk installed. Investigating this...
Reboot to recovery is working as it should now (and of course also without magisk).
Click to expand...
Click to collapse
What about GPS?
GPS apps like GPS Status&Toolbox or SatStat don't get location fixes. Nevertheless navigating with Osmand or googleMaps should work. Positionfinding is also slow. Got better
Click to expand...
Click to collapse
I found a bug. What should I do?
We need your feedback for optimization. But your feedback is only useful in connection with logs --> see section Bugreports
Click to expand...
Click to collapse
What about root access?
Root isn't included per default (except root over adb, but it's off by default).
If you want to gain root access to your apps use one of these (depending on your taste/needs):
Official Lineage Add-on https://download.lineageos.org/extras use su (arm) 15.1 here and flash via TWRP
Magisk https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Click to expand...
Click to collapse
Bugreports
You'll find information about logging here.
Please also note how you got the error or how it can be reproduced.
Click to expand...
Click to collapse
Sources
Kernel: https://github.com/AICP/kernel_sony_msm8974
Manifest: https://github.com/115ek/manifest
Click to expand...
Click to collapse
Credits
SpiritCroc: big thanks to him for maintaining the device trees and a lot of very useful hints
rcstar6696
SuperLamic
drakonizer
AdrianDC
munjeni: thanks for tips and tricks
nailyk: thanks for tips and tricks
All the other contributors on sony msm8974 platform
LineageOS team
Click to expand...
Click to collapse
XDA:DevDB Information
Lineage OS 15.1 for Xperia Z1 compact - amami, ROM for the Sony Xperia Z1 Compact
Contributors
115ek, SpiritCroc, drakonizer, rcstar6696, SuperLamic, AdrianDC, nailyk, LineageOS team
Source Code: https://github.com/115ek/manifest
ROM OS Version: 8.x Oreo
ROM Kernel: Linux 3.4.x
Version Information
Status: Beta
Beta Release Date: 2018-09-10
Created 2018-09-10
Last Updated 2019-03-18
Changelog
13.12.2018
fixed wrong bluetooth MAC address (00:00:00:00:5a:ad on all devices), now displaying correct device specific one
12.12.2018
synced LineageOS sources (security patch level December 05, 2018)
11.11.2018
fix problem with Lineage SU addon by using 64-bit binder API (thanks @NyQuilXT)
synced LineageOS sources (security patch level November 05, 2018)
14.10.2018
fixed GPS 3D fix
08.10.2018
fixed MHL (thanks @koron393)
added callrecording
synced LineageOS sources (security patch level October 05, 2018)
23.09.2018
fixed reboot to recovery without magisk
minor improvements from AICP devices trees (thanks @SpiritCroc)
synced LineageOS sources
10.09.2018
initial release
Hi 115ek. Thanks for making this. I'm not new to flashing but I have a question nonetheless. What do you mean by
Encryption : Ok but needs recovery capable of Oreo decryption for installing updates (AFAIK such a recovery doesn't exist until now for our device...)
Click to expand...
Click to collapse
I'm actually having some trouble finding a up-to-date recovery.
Jeroen1000 said:
Hi 115ek. Thanks for making this. I'm not new to flashing but I have a question nonetheless. What do you mean by
I'm actually having some trouble finding a up-to-date recovery.
Click to expand...
Click to collapse
You can use this https://androidfilehost.com/?fid=5862345805528046823 or that https://forum.xda-developers.com/sony-xperia-z1-compact/orig-development/recovery-twrp-3-2-1-t3759450.
For Lineage 15.x flashing you need TWRP>=3.2.x If the version is older you'll end up in a error 7.
Concerning decryption: Google introduced some new encryption stuff and so the decryption of /data from inside TWRP is broken. Some guys are working on it (@nailyk).
Encrypting the device should work fine, but I don't know what happens if you want to update the encrypted device. (I'm going to test that ).
Basically you need to store the update package outside of encrypted partitions... Maybe adb sideload works - but it's circumstantial.
Edit:
That's only interesting if you plan to encrypt your device. Otherways you can relax.
Edit2:
adb sideload should do the job. But you need a PC for updating. Installing an image directly via recovery isn't possible until now.
With sources for both kernel and system unlike the other port! Thanks, I'll definitely be using this!
Xperia J1 Compact
could this work on an Xperia J1 Compact?
it's basically the same phone with the same specs right?
The rom looks very stable and balance, but I've some problems with root procedure. I tried the lineage addon, the root seems active, but opening apps (es. Ad away) results unrooted, any ideas?
Update: Now Works. Flashed lastest Magisk
Amazing to see this old device on Oreo, just installed and it feels smooth and nice. Just a pity that I have broken the sim card connectors inside so I cant use it as a phone but I will fins use of it at home just for fun. Thank you for your work 115ek :good:
Great to see this rom realy! This rom have stock camera?
munjeni said:
Great to see this rom realy! This rom have stock camera?
Click to expand...
Click to collapse
What do you mean with stock camera?
There was a thing with kernel versions 3.4 and 3.10, wasn't it? We're using 3.4.
Concerning the camera: I'm not that expert, but it looks okay I would say.
Feel free to contribute: There's still the reboot-to-recovery problem and Pie is in the starting blocks.
115ek said:
Feel free to contribute: There's still the reboot-to-recovery problem and Pie is in the starting blocks.
Click to expand...
Click to collapse
my phone reboots to recovery.
Need to install Magisk
without it I also do not reboot to recovery
raschad said:
my phone reboots to recovery.
Need to install Magisk
without it I also do not reboot to recovery
Click to expand...
Click to collapse
Thanks, but I already knew this
But I like to reboot to recovery without magisk. I think there are people around who don't like/need magisk (including me).
The fact that it works with magisk may locate the problem to the boot.img. I have init_sony in mind and will check that.
Any ideas welcome
115ek said:
Thanks, but I already knew this
But I like to reboot to recovery without magisk. I think there are people around who don't like/need magisk (including me).
The fact that it works with magisk may locate the problem to the boot.img. I have init_sony in mind and will check that.
Any ideas welcome
Click to expand...
Click to collapse
I meant does this rom have stock camera blobs? Do you have property: ro.bootmode
and does /proc/cmdline shows diferent bootreason when you set reboot reason to recovery?
munjeni said:
Do you have property: ro.bootmode
and does /proc/cmdline shows diferent bootreason when you set reboot reason to recovery?
Click to expand...
Click to collapse
Good news: an easy import of your init_board_device.h did the trick. Maybe a timing problem?
Anyway: reboot to recovery is now working correctly, even without magisk
Is that okay for you: http://gerrit.aicp-rom.com/c/AICP/device_sony_msm8974-common/+/73688 ?
I just found this https://github.com/LineageOS/androi...neage-15.1/init/init_sony/init_board_device.h its just prototype so seems you have missed init_sony/init_board_device.h in your device tree...
munjeni said:
I meant does this rom have stock camera blobs?
Click to expand...
Click to collapse
We're using them https://github.com/AICP/proprietary_vendor_sony/tree/o8.1/rhine-common/proprietary/vendor, so I guess yes.
You're more into topic, aren't you? How to distinguish between AOSP and stock blobs? There were some mysteries around DRM, camera quality and so on. I remember a separate thread you also participated in...
But I'm not really into this topic.
munjeni said:
I just found this https://github.com/LineageOS/androi...neage-15.1/init/init_sony/init_board_device.h its just prototype so seems you have missed init_sony/init_board_device.h in your device tree...
Click to expand...
Click to collapse
No, it's actually in here: https://github.com/AICP/device_sony_msm8974-common/blob/o8.1/include/init_sony/init_board_device.h
But It's different from yours. Yours performs another keycheck.
Seems rom have stock blobs. To distinguish between AOSP and stock blobs... depends on kernel you have using, aosp kernel can't be used with stock blobs since aosp camera kernel module is diferent, but I'm out of development for long, have no free time and to be honest I still didn't forgot treatment & injustice for my status on xda, that made me more inactive here. Recognised members have bad treatment here, seems senior members have much more priority than recognised members, and thats reason why everybody here need to care how many hours per day to waste here. I decided to stop wasting my time on xda since xda leaders do not respect anybody's hard work here. I recommend the same to everyone here.
I tried "reboot to recovery", after Sony logo the phone reboot again (also if you press recovery button), and to enter in recovery you've to push again the button at the second reboot.
It is like a normal reboot... But it's not a problem ?
ULT][MO said:
I tried "reboot to recovery", after Sony logo the phone reboot again (also if you press recovery button), and to enter in recovery you've to push again the button at the second reboot.
It is like a normal reboot... But it's not a problem
Click to expand...
Click to collapse
What recovery are you using? I recommend this one: https://forum.xda-developers.com/sony-xperia-z1-compact/orig-development/lineageos-12-1-z1c-current-sec-patches-t3614936.
With mine from here https://forum.xda-developers.com/sony-xperia-z1-compact/orig-development/recovery-twrp-3-2-1-t3759450 it still won't work. Maybe a timing thing.
But it's okay if we have at least one working TWRP.
And oreo /data decryption is still an issue we have to address.
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.
Central project page
https://forum.xda-developers.com/xperia-xz2/development/recovery-twrp-3-3-1-0-t4074305
11.06.2020
Switch to TWRP 3.4.0
sodp twrp 2020-06 security patch level
stock twrp 2020-05 security patch level for firmware 52.1.A.2.1
Now both twrp should work without a ROM being installed (empty system/vendor/oem partitions) and still be able to decrypt your userdata.
Also the stock twrp touch should now always work instead of playing russian roulette.
Click to expand...
Click to collapse
13.06.2020
Thanks to the fixes in 3.4.0 we got now a TWRP with the following enhancements for STOCK and SODP:
- This TWRP will work with future 10.0 ROMs, you don't need a new build matching the security patch level of your ROM.
- You can install this TWRP again with the buildin ramdisk patcher. Please follow the installation instructions.
Click to expand...
Click to collapse
Please test and report back if you got any touch / decryption problems.
MartinX3 said:
13.06.2020
Please test and report back if you got any touch / decryption problems.
Click to expand...
Click to collapse
@MartinX3
XZ2 Compact here, tried the Version from 0611 and 0613 and with both I got stuck at SONY Logo.. Where can I pull a log for you in this case?
TacoLoco said:
@MartinX3
XZ2 Compact here, tried the Version from 0611 and 0613 and with both I got stuck at SONY Logo.. Where can I pull a log for you in this case?
Click to expand...
Click to collapse
STOCK or SODP based ROM?
STOCK or SODP based TWRP?
You booted into fastboot with software and not with the hardware buttons?
And I hope you didn't flash it with "fastboot flash boot twrp.img"
you could try to press PWR+VolUP for a short time, then shortly after it should crash
Then you should be able to get the /sys/fs/pstore folder files in your system (needs root)
Or if that doesn't work maybe a dump of your TA partition.
You use a 10.0 ROM with kernel 4.14 (SODP) or kernel 4.9 (STOCK)?
MartinX3 said:
STOCK or SODP based ROM?
STOCK or SODP based TWRP?
You booted into fastboot with software and not with the hardware buttons?
And I hope you didn't flash it with "fastboot flash boot twrp.img"
you could try to press PWR+VolUP for a short time, then shortly after it should crash
Then you should be able to get the /sys/fs/pstore folder files in your system (needs root)
Or if that doesn't work maybe a dump of your TA partition.
You use a 10.0 ROM with kernel 4.14 (SODP) or kernel 4.9 (STOCK)?
Click to expand...
Click to collapse
SODP Based ROM and TWRP, did enter bootloader with hardware keys.. I know this stands under known bugs but wouldnt it be more idiot proof to write this into the installation section as a separate step?
Thanks Martin for your ongoing dedication!
TacoLoco said:
SODP Based ROM and TWRP, did enter bootloader with hardware keys.. I know this stands under known bugs but wouldnt it be more idiot proof to write this into the installation section as a separate step?
Thanks Martin for your ongoing dedication!
Click to expand...
Click to collapse
Aaaand added!
Nice to hear and thank you for your report!
MartinX3 said:
Aaaand added!
Nice to hear and thank you for your report!
Click to expand...
Click to collapse
Nice
But now running into the next issue, when executing "Fix Recovery Bootloop":
cd /tmp/repackorig/ && /sbin/magiskboot hexpatch kernel 77616E745F696E697472616D667300
736B69705F696E697472616D667300 process endet with ERROR: 1
Error patching kernel.
Click to expand...
Click to collapse
It boots me to TWRP every time, I think this is related..
TacoLoco said:
Nice
But now running into the next issue, when executing "Fix Recovery Bootloop":
It boots me to TWRP every time, I think this is related..
Click to expand...
Click to collapse
What happens if you reboot the twrp and try it again?
Or if you flash magisk and try to boot?
Do you use a modified kernel?
Did you "fastboot flash boot twrp.img" by accident?
14.06.2020
Reuploaded the stock TWRP with a later touch kernel modules initialization.
Hopefully fixing the randomly happening not working touch.
Click to expand...
Click to collapse
Hi there,
what is 'sodp' please ?
moltes74 said:
Hi there,
what is 'sodp' please ?
Click to expand...
Click to collapse
It's described on the first page of the central project thread.
MartinX3, thanks for all your work!
I have a xz2c dual and, thanks to your guides, backed up the TA partition and flashed the latest Unofficial TWRP recovery with the up to date stock image.
My experience is that the problem with some boots not having the touchscreen working is still there. Fortunately, after rebooting you get a new chance ... and sometimes it actually works.
I used TWRP to install the latest Official LineageOS 17.1. It worked well. However, after that, TWRP was replaced by Lineage Recovery (?!) and I'm now unable to boot into recovery with the Unofficial SODP TWRP to flash it back.
Any guess of what could be the problem? Do you plan to provide a version which would work with the Official LineageOS 17.1 image?
tanty0 said:
I used TWRP to install the latest Official LineageOS 17.1. It worked well. However, after that, TWRP was replaced by Lineage Recovery (?!) and I'm now unable to boot into recovery with the Unofficial SODP TWRP to flash it back.
Any guess of what could be the problem? Do you plan to provide a version which would work with the Official LineageOS 17.1 image?
Click to expand...
Click to collapse
Answering myself back. Yes, this is known and you have already stated that you plan to look at this whenever you find the time: https://forum.xda-developers.com/showpost.php?p=83172223&postcount=345 , and below ...
I'd like to flash my userbuild los 17.1... which file/version do I need? (Android 10>TWRP) Stock or SODP ??
02.03.2021
Reuploaded the SODP TWRP with a workaround for Android 11 compatibility.
Click to expand...
Click to collapse
CHEIb00 said:
I'd like to flash my userbuild los 17.1... which file/version do I need? (Android 10>TWRP) Stock or SODP ??
Click to expand...
Click to collapse
It is currently not compatible with the official LOS 17.1 due to technical limitations by google.
@MartinX3 - using twrp3.4 on eXistenZ Q, (stock-based 10), and working great, but...
- max brightness is too low. Can hardly see the screen in daylight. Any options?
- are there any newer TWRPs for XZ2c stock?
Thanks
levone1 said:
@MartinX3 - using twrp3.4 on eXistenZ Q, (stock-based 10), and working great, but...
- max brightness is too low. Can hardly see the screen in daylight. Any options?
- are there any newer TWRPs for XZ2c stock?
Thanks
Click to expand...
Click to collapse
Is there no brightness setting?
Only behind the download link.
Since stock reached end of life there won't be any new twrp for it.
MartinX3 said:
Is there no brightness setting?
Only behind the download link.
Since stock reached end of life there won't be any new twrp for it.
Click to expand...
Click to collapse
Max brightness as set in settings is very dim...