Develop Bugs

| ROM | LineageOS 14.1 | unofficial | 27/02/2017 | Signature Spoofing integrated |

Hello
I am going to release unofficial builds of LineageOS 14.1 for Wileyfox Crackling. The builds will be updated every month after a new security patch level is reached.
The build I made can be flashed on top of Cyanogenmod 13 build (with wiping dalvik and cache). It should work without any problems; I do not experience any.
But I do not take any responsibility if your favorite app/setting/etc. is not working anymore.
If it makes problems, wipe data/dalvik/cache and install again.
Besides that the ROM has two extra features:
I patched signature spoofing support into the ROM. Now it is possible to install microG. This is a re-implementation of Google’s proprietary Android user space apps and libraries. So for many cases you do not have to install the proprietary GAPPS anymore.
Note: This feature is disabled by default and will not affect the ROM in any way. It has to be enabled in the according settings.
Also, there's an option available to record calls now. Please respect the privacy of others.
Android security patch level:
Code:
[URL="https://source.android.com/security/bulletin/2017-02-01.html"]February[/URL] | 2017-02-05 security patch level
Version/Filename:
Code:
lineage-14.1-20170227-UNOFFICIAL-crackling.zip
Download:
Code:
[B][SIZE="2"]Openload.co:[/SIZE][/B]
https://openload.co/f/DBKYItUGllA/lineage-14.1-20170227-UNOFFICIAL-crackling.zip
https://openload.co/f/grRwId0HJJE/lineage-14.1-20170227-UNOFFICIAL-crackling.zip.md5sum
Alternativ:
[B][SIZE="2"]Free.fr:[/SIZE][/B]
http://dl.free.fr/uqIBAf8dM
The kernel and device sources I used to build the ROM can be found here:
Code:
https://github.com/lineageos

thomson.aa said:
Hello
This is my first build of LineageOS for Wileyfox Crackling.
I flashed it on top of my Cyanogenmod 13 build (with only wiping dalvik and cache) and it so far works without any problems.
But I do not take any responsibility if your favorite app/setting/etc. is not working anymore.
This release has the root access option disabled because LineageOS disables root for apps by default. It has to be enabled before building the rom - I didn't know that so I will provide an updated rom with root access for apps available.
Besides that the rom has one extra feature:
I patched signature spoofing support into the rom. Now it is possbible to install microG. This is a re-implementation of Google’s proprietary Android user space apps and libraries. So for many cases you do not have to install the proprietary GAPPS anymore.
Note: This feature is disabled by default and has to be enabled in the according settings.
Android security patch level:
Code:
[URL="https://source.android.com/security/bulletin/2017-01-01.html"]January[/URL] | 2017-01-05 security patch level
Version/Filename:
Code:
lineage-14.1-20170117-UNOFFICIAL-crackling.zip
Download:
Code:
https://openload.co/f/WCt_JxGZ-UE/lineage-14.1-20170117-UNOFFICIAL-crackling.zip
Click to expand...
Click to collapse
Sorry thomson.aa sorry i do not have english my google translation. Work is very nice thanks one has a mistake sim card people do not see a way to solve it? I wish you continued success.

Where is the source ? You can't post this without kernel source

I dirty flashed this over crDroid and it seems to be working pretty well. Thanks.
All my app's (not many at the moment) were working fine.
Playstore thinks it's 'no carrier Wileyfox Wileyfox Swift'... but I guess that's better than 'Wileyfox Pixel XL' (crDroid).
On initial booting the status bar wouldn't pull down but works ok after a reboot.
Buttons were a bit messed up which only gave me a back button even though the usual defaults were all set. After deleting them and re-adding them they worked fine. I'm guessing this may be due to dirty flashing. Shame the button customisation is just as basic as cm13 especially after using crDroid.
Using Kernal Auditor Mod I see that the cpu only scales down to 800mhz and the gpu scales up to 400mhz. I don't know much about this but won't this make it a little power hungry?
Going through the settings, I'm thinking that LOS14 isn't quite as complete as the cm13 I was using a few weeks ago. Although I guess this is to be expected at this stage. And I'm used to the more versatile crDroid now so I'll be restoring that in a mo.
This MicroG project sounds great. It seems a bit complex to get it working as I'd like but I definitely be having a go when I get my head around it.
All in all, Great job. Keep up the good work... please. I'm already waiting for the next release.
Oh, and er... Surely you could find a better file host???

I tried to build the Image myself by using your other Thread's How-To and after flashing i had no WIFI.
Now i flashed this build and WIFI is also not working.
[Edit]
I've collected some Logs - perhaps they'll help.
[Edit2]
Now i tried another '14.1-ROM' and i've the same problem....
During all my Tests the shown MAC-Address during the 'inital install' was weird: 02:00:00:00:00:00.
Before the 14.1 Lineage i had the latest CMmod 13 running without any Problems :/

Ok - solved it....
I encrypted my Device during CM13 and always entered my Key during Boot/TWRP and Formatting/Installation of 14.1.
Now i *really* formated all the Data (and the former encryption), rebooted to Recovery and sideloaded the Image+Gapps.
Now WIFI is working.

How do I enable signature spoofing ? I can't find any relevant setting.

M.A.K said:
How do I enable signature spoofing ? I can't find any relevant setting.
Click to expand...
Click to collapse
Settings -> Apps -> Gear symbol -> App permissions -> Spoof package signature

No... it's not there for me.

M.A.K said:
No... it's not there for me.
Click to expand...
Click to collapse
Works like it is supposed to be. The setting/app permission is only available if you install an app that requires that permission.
So, if you install microG the setting for signature spoofing will become available.

fred0r said:
Now i *really* formated all the Data (and the former encryption)
Click to expand...
Click to collapse
Could you tell me how to do that? I remember trying to find a way to remove encryption back in the day on my Nexus 5 and wasn't able to do it. Thanks!

thomson.aa said:
Works like it is supposed to be. The setting/app permission is only available if you install an app that requires that permission.
So, if you install microG the setting for signature spoofing will become available.
Click to expand...
Click to collapse
Ah, yes... got it now, thanks.

jobedius said:
Could you tell me how to do that? I remember trying to find a way to remove encryption back in the day on my Nexus 5 and wasn't able to do it. Thanks!
Click to expand...
Click to collapse
I booted into the TWRP 3.0.3 and did not enter my Encryption-PW (cancel) and then clicked 'Wipe' and then 'Format Data'.

update to official build?
Is it possible to update (aka dirty flash) to the now released official build? I had some problems doing that, see https://forum.xda-developers.com/showpost.php?p=70829582&postcount=8
Cheers

Nope, its not
Mithodin said:
Is it possible to update (aka dirty flash) to the now released official build? I had some problems doing that, see https://forum.xda-developers.com/showpost.php?p=70829582&postcount=8
Cheers
Click to expand...
Click to collapse
Twrp shows error 7(the data is incompatible). You need to wipe data, cache partitions and the system partition. Then install the zip with arm64 android 7.1 g-apps.
Cheers:good:

fred0r said:
I booted into the TWRP 3.0.3 and did not enter my Encryption-PW (cancel) and then clicked 'Wipe' and then 'Format Data'.
Click to expand...
Click to collapse
Aahhh, that makes sense if you know it! Thanks!

[ROM][P905][UNOFFICIAL] Resurrection Remix 5.8.5 Android 7.1.2 20180118

I'm not responsible for any damage to your device of any sort.
By flashing this you take responsibility of anything that happens.
Process at your own risk!
This firmware was developed for the p905. It doesn't apply to the p905v at this time because it's bootloader locked and a custom recovery isn't possible.
If you want to check firmware - please make backup. Better to store all partitions, at least efs and may be modem.
I'm using nano gapps.
Instructions
1. Install custom recovery
2. Download the zip(s) - firmware and Google Apps additional package (optional)
3. Backup all partitions (it least efs) and store somewhere - it need to do - because you can loose imei
4. Full wipe all
5. Flash firmware and gapps
Links
2: 20180118: remove Magisk, back su: https://drive.google.com/file/d/11V0Hmu9Jjib-oLERLXPNXbMMAie_iORq/view?usp=sharing
1: 20171231: https://drive.google.com/file/d/1m7t_7gntp9cDRRxGnJJqnwufnJxFVKUZ/view?usp=sharing
Gapps
http://opengapps.org/
Platform: ARM
Android: 7.1
Recovery
Official TWRP: http://forum.xda-developers.com/showthread.php?t=2706982
Sources
Sources: https://github.com/ResurrectionRemix/
Device: https://github.com/Valera1978/android_device_samsung_viennalte
Kernel: https://github.com/Valera1978/android_kernel_samsung_viennalte
Vendor: https://github.com/Valera1978/android_vendor_samsung_viennalte

Thanks again a lot for your work.
I wish you a happy new year!

@Valera1978
What such amazing gift for New Year!!!
Thanks for such awesome work my friend!

What is the different from this FW in compare to
https://forum.xda-developers.com/ga...-cyanogenmod-14-0-android-7-0-nougat-t3476335
? Does this thread continous the "old" one or it is a total other FW (other feature, Kernel .... ) ?

Mad07 said:
What is the different from this FW in compare to
https://forum.xda-developers.com/ga...-cyanogenmod-14-0-android-7-0-nougat-t3476335
? Does this thread continous the "old" one or it is a total other FW (other feature, Kernel .... ) ?
Click to expand...
Click to collapse
Hardware and config the same.
The idea is create another thread for custom firmwares, based on lineage\aosp.
Right now it's RR only, i'm working on OMNI rom, and later i'll build more firmwares.

please in other version don't insert the magisk.the rom to go in loop .and add in developer option the root gestion

Dagoncore93 said:
please in other version don't insert the magisk.the rom to go in loop .and add in developer option the root gestion
Click to expand...
Click to collapse
I'm taking a stab at what you are trying to express but the roms take 10 to 15 minutes to boot the first time because you are doing a full wipe. If you are not giving it at least that long magisk is not a likely cause.

Loakidog said:
I'm taking a stab at what you are trying to express but the roms take 10 to 15 minutes to boot the first time because you are doing a full wipe. If you are not giving it at least that long magisk is not a likely cause.
Click to expand...
Click to collapse
I received myself the error system ui crashed, and it got stuck on it.

Thanks Valera 1978, what a great new year gift!

I'm actually running Android 5.0.2, so is that Lollipop
Sent from my SM-G935F using XDA-Developers Legacy app

Albinoni said:
I'm actually running Android 5.0.2, so is that Lollipop
Click to expand...
Click to collapse
Yes

ralph_kl said:
I received myself the error system ui crashed, and it got stuck on it.
Click to expand...
Click to collapse
Send Valera1978 a bug report via Private Message. It is the only way developers can isolate the problem and fix it. In most Roms you can take a bug report via developer options.

help please Valera1978
i am updating from Resurrection Remix 5.8.5 version 20171231.
i wiped cache partitions
flashing rom 20180118 stuck on patching system unconditionally

theogalaxy said:
help please Valera1978
i am updating from Resurrection Remix 5.8.5 version 20171231.
i wiped cache partitions
flashing rom 20180118 stuck on patching system unconditionally
Click to expand...
Click to collapse
Try a full wipe magisk was removed with the latest version and super su added

A little help, please
Hello,
Sorry, but I need an help for understand.
How I can install this system?
I mean, can you explain to me what steps I need to do to install and which files to download?
sorry for my english, which is why I did not understand how to do it
Rosario
Valera1978 said:
I'm not responsible for any damage to your device of any sort.
By flashing this you take responsibility of anything that happens.
Process at your own risk!
This firmware was developed for the p905. It doesn't apply to the p905v at this time because it's bootloader locked and a custom recovery isn't possible.
If you want to check firmware - please make backup. Better to store all partitions, at least efs and may be modem.
I'm using nano gapps.
Instructions
1. Install custom recovery
2. Download the zip(s) - firmware and Google Apps additional package (optional)
3. Backup all partitions (it least efs) and store somewhere - it need to do - because you can loose imei
4. Full wipe all
5. Flash firmware and gapps
Links
2: 20180118: remove Magisk, back su: https://drive.google.com/file/d/11V0Hmu9Jjib-oLERLXPNXbMMAie_iORq/view?usp=sharing
1: 20171231: https://drive.google.com/file/d/1m7t_7gntp9cDRRxGnJJqnwufnJxFVKUZ/view?usp=sharing
Gapps
http://opengapps.org/
Platform: ARM
Android: 7.1
Recovery
Official TWRP: http://forum.xda-developers.com/showthread.php?t=2706982
Sources
Sources: https://github.com/ResurrectionRemix/
Device: https://github.com/Valera1978/android_device_samsung_viennalte
Kernel: https://github.com/Valera1978/android_kernel_samsung_viennalte
Vendor: https://github.com/Valera1978/android_vendor_samsung_viennalte
Click to expand...
Click to collapse

Compability
It is can flash for SM-P091 ?

i want the S Pen features and UI of Galaxy Tab S3 on my Galaxy Note 12.1 Pro Wifi. Am I right here and if yes how to do it please?
In terms of the little RAM I have I will use on microSD card as a RAM alternativ. is this a good idea in combination with a custom Rom?
Thx!

[ROM][james] Unofficial Lineage OS 15.1 for Moto E5 Play (beta v1.01)

LineageOS 15.1 (Beta v1.01)
for Moto E5 Play (james)
Boost Mobile/Virgin Mobile/Sprint Variants
LineageOS 15.1 is a free, community-built, aftermarket firmware distribution of Android 8.1.0 Oreo, which is designed to increase performance and reliability over stock Android for your device.
LineageOS is based on the Android Open Source Project (AOSP) with extra contributions from a myriad of developers and enthusiasts within the Android community. LineageOS can be used without need of having any Google application installed. LineageOS does still include various hardware-specific code, which is slowly being open sourced.
LineageOS Source Code: https://github.com/LineageOS
LineageOS Changelog: https://www.cmxlog.com/15.1
LineageOS Gerrit Code Review: https://review.lineageos.org/#/q/status:open
Kernel Source Code MSM8920: https://github.com/MotorolaMobilityLLC/kernel-msm/releases/tag/MMI-OCP27.91-23
This is a LineageOS 15.1 build based on Project Treble. More specifically, it is based on XDA Recognized Developer @phhusson's Phh-Treble and his ARM32 Vanilla GSI. Because the Moto E5 Play is officially supported by Project Treble, I have taken the vanilla GSI and made it bootable for our device. Along with a modified kernel from the stock Android 8.0.0 OS, I've compiled a TWRP flashable Lineage 15.1 custom ROM for the james. This vanilla ROM is very much bare-bones -- no GApps, no SU addon, etc. -- and is likely chocked full of bugs at this time. So, without further ado.....
DISCLAIMER: Your warranty is hereby null, void, and held for naught. By proceeding further, you are assuming full responsibility for any good or bad consequences which may result from flashing this ROM. While I have installed and tested this ROM on my own device, and can confirm boot up and basic functionality, I cannot yet elaborate on bugs and other types of instabilities. This is truly a work in progress at this point. So, to sum it up, FLASH THIS AT YOUR OWN RISK. I am hereby absolved of any liability from bricked, damaged, or otherwise inoperable devices.
SPECIFICATIONS:
Android Version: 8.1.0
Build: OPM2.171026.006
Kernel Version: 3.18.71
Security Patch Level: June 5, 2018
Build Date: June 26, 2018
LineageOS API: llama (9)
STATUS: Beta
Created: Thu, July 29, 2018 15:00:00
REQUIREMENTS/INSTRUCTIONS:
1. First and foremost, an unlocked bootloader is necessary;
2. TWRP custom recovery installed and force encryption disabled. Please visit @CodyF86's thread on how to do this, and please be sure and hit the THANKS button if you used his work;
3. Download the ROM zip from the below download link and store it on external device storage;
4. Boot your device into TWRP recovery;
5. Select Wipe, and swipe to perform a factory data reset. Now, select Wipe and then Format Data, and follow all prompts to commence formatting;
6. Reboot Recovery (often necessary to ensure proper mounting of /userdata after formatting the partition;
7. Select Install, navigate to the location of the ROM zip, and swipe to commence installation;
8. Reboot System (1st boot up can take around 3 minutes or more);
NOTE: This vanilla ROM does not include GApps so, if you want GApps, visit https://opengapps.org/ and download a package of your preference. If installing GApps, simply flash the package during the above installation process after Step 7, then Reboot System.
BUGS:
Working:
RIL
Bluetooth
WiFi
Not Working:
Camera
Please properly report bugs, with submission of a bug report if you know how. If not, please give a clear and concise explanation of the bug. NOTE: Please DO NOT report bugs if you are running modifications such as Magisk Modules, Xposed Framework, etc. This makes it nearly impossible to pinpoint, troubleshoot and fix bugs and instabilities. Also, please know that I am not a ROM maintainer for Project Treble or LineageOS. So, while I will do my best to resolve bugs and provide some bug fixes and updates, please do not ask for ETAs. I work 55+ hours a week at Motorola Mobility, LLC., so I don't always get a lot of free time.
THANKS & MENTIONS:
Thanks to @SuperR. for his awesome Windows Kitchen;
Thanks to @CodyF86 for breaking ground and building TWRP for the james;
Thanks and credits to @phhusson for his Phh-Treble Vanilla GSIs;
Thanks to the entire LineageOS team;
DOWNLOAD LINK:
LineageOS 15.1 (Beta v1.01): https://drive.google.com/open?id=1TPl879IQvVH2ajYG6ZJ2kobp_rMgRfE5

Guys please provide feedback and feel free to contribute on this. I have more custom ROMs on the way such as ResurrectionRemix, PixelExperience, and AOSP-Extended. But I don't have a lot of free time to maintain ROMs, so I'm going to need help ironing out bugs and compiling patches.

Hum that's weird, wifi works for me on Moto E5
For camera, I have the fix pending for two months, I just haven't committed it yet -_-'

Thanks so much for commenting. After wiping the Dalvik/ART & /cache, WiFi is now working. I'll keep my eyes open for your pending camera commit.

Update: WiFi,, Bluetooth and RIL appear to be functional. Over the next few days I'm in hopes that user feedback will provide me with more insight as to bugs & instabilities.

this boots fine on e5 plus after flashing e5plus-noverity kernel and magisk as for ril data and all i cant tell you until i fix my sprint e5plus modem files messed them up by accidently flashing a differnt e5plus rom will report back more when i manage to completly fix my phone

allenjthomsen said:
this boots fine on e5 plus after flashing e5plus-noverity kernel and magisk as for ril data and all i cant tell you until i fix my sprint e5plus modem files messed them up by accidently flashing a differnt e5plus rom will report back more when i manage to completly fix my phone
Click to expand...
Click to collapse
Ok thanks @allenjthomsen. Yeah there seems to be many of us in the same boat -- patiently waiting for Motorola Mobility to either release or "leak" some factory images for the Moto E5 series devices. I'm actually drafting a baseband radio thread now for the James, compiling a TWRP flashable installer to restore radio/modem firmware and reset the network config to factory default. I know of a couple of devs over at Android Central that may can dump baseband partitions for your device. Also, please provide me with your Baseband Version. Thanks...

I have a bootable Android 9.0-DP3 ROM for the James. Lots of stuff broken, so I'm going to get it more stable, implement a working GApps package, etc. before posting it. Going to try and get our camera app working on this ROM also, maybe see if I can talk @phhusson into sharing his fix. Hint hint

i can dump files if needed and btw i tried your lineage os and i couldnt get data but got signal and camera crash other than that it ran great on my replacement E5 Plus Sprint model

allenjthomsen said:
i can dump files if needed and btw i tried your lineage os and i couldnt get data but got signal and camera crash other than that it ran great on my replacement E5 Plus Sprint model
Click to expand...
Click to collapse
Thank you for your feedback. I have a camera fix underway. As far as data connectivity I've had some issues myself, so I'm dissecting that issue too.

I have the same problem with the camera with GSI roms on a motorola e5 plus (rhannah). I get the impression that Motorola has something not standard in its handling of cameras of this family of devices

What DPI is this device? 320dpi right?

nachoxda79 said:
What DPI is this device? 320dpi right?
Click to expand...
Click to collapse
Yes. 320dpi (xhdpi); 1280 x 720 resolution

MotoJunkie01 said:
Yes. 320dpi (xhdpi); 1280 x 720 resolution
Click to expand...
Click to collapse
Thanks dude.

@MotoJunkie01 Hey, if you get a second pm me. I got your rom to boot on the g6 play by switching kernels, so I decided to compile a treble rom myself and I can compile it successfully, but the rom won't boot...clang seg faults like 30 times trying to compile it, so I think that is the actual issue, but wanted to bounce a few things off of you. No worries, thanks.

CodyF86 said:
@MotoJunkie01 Hey, if you get a second pm me. I got your rom to boot on the g6 play by switching kernels, so I decided to compile a treble rom myself and I can compile it successfully, but the rom won't boot...clang seg faults like 30 times trying to compile it, so I think that is the actual issue, but wanted to bounce a few things off of you. No worries, thanks.
Click to expand...
Click to collapse
I tried to PM you but sending failed. I'll get on my PC and login through the browser. I think my messaging settings are preventing the PM from sending.

Thanks for your work. Would this Lineage ROM work for the T-Mobile variant of the E5 Play (XT1921-3)?

konradsa said:
Thanks for your work. Would this Lineage ROM work for the T-Mobile variant of the E5 Play (XT1921-3)?
Click to expand...
Click to collapse
Not likely. There's no real danger in trying it because my installer does not flash sensitive partitions, but only /system & /boot. While I don't perceive any chance of bricking your device, it would be at your own risk. You would be better off flashing your device with a Treble GSI. While this ROM is technically based on a Project Treble GSI, I done some mods to the stock boot image and compiled the installer from porting. Hence, the ROM should not be characterized as a GSI itself. By the way I do have firmware for the xt1921-3, which I will be posting in my Moto E5 firmware thread over the next couple days.

my model is moto e5 play (XT1920-15)
my model is moto e5 play (XT1920-15) , will it work also my codename is not james. also how we can backup stock rom. before trying dont we need stock rom for this phone , so we can be secure.

rehannasim said:
my model is moto e5 play (XT1920-15) , will it work also my codename is not james. also how we can backup stock rom. before trying dont we need stock rom for this phone , so we can be secure.
Click to expand...
Click to collapse
I can only confirm compatibility with the xt1921-5. But before trying it, as you have correctly noted, it is crucial to have a suitable backup of your /system and /boot partition, just in case anything goes wrong. Most times, backups are made using a custom recovery such as TWRP. However I'm not familiar with your variant and therefore do not know of a working TWRP for your device. I will check my firmware archive and see if I can find a package for your model.
Update; unfortunately, at this time I cannot find firmware or custom recovery for your variant. I would urge you to post under the Q&A thread and ask if any members have your model.

[ROM][Unofficial][8.1.0][deprecated] Lineage OS 15.1 for Xperia Z1 compact 29.12.18

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.

Development [CLOSED] LineageOS 20 BETA for OnePlus 9Pro LemonadeP Android 13 - NOV. 12, 2022

This is a BETA build for NEW Lineage 20, Android 13. Possible bugs may be present. Let me know!!
MSM to Android 11 if you want to start clean, then flash either CrDroid or Nameless c63 firmware to begin.
This is based on the Android Open Source Project. It can be used without any need to have any Google application installed. It does still include various proprietary hardware-specific code.
Gapps must be flashed separately and are not included in this ROM.
All the source code is available in the Github repo here.
Thanks go to Github and LineageOS for their source code and device specific code. I couldn't have built this without it!!!
The ROM uses the LineageOS source code, device specific code and proprietary blobs. I made other minor changes and used compression to lower the file size of the ROM, creating more space in the internal storage with minor reduction in performance. Updated daily with minor changes.
You may use another recovery however you will receive a signature verification error. You can simply ignore and choose yes and flash it anyway. You will need to do this with gapps and magisk.apk to root.
DOWNLOAD ROM & GAPPS HERE
#1 REBOOT TO BOOTLOADER
#2 FACTORY RESET: fastboot -w
#3 REBOOT TO RECOVERY
#4 SIDELOAD ROM IN RECOVERY
adb sideload lineage-20-20221112-UNOFFICIAL-lemonadep.zip
reboot recovery
adb sideload lineage-20-20221112-UNOFFICIAL-lemonadep.zip
reboot recovery
#5 SIDELOAD GAPPS: NikGapps-core-arm64-13-20221109-signed.zip
#6 REBOOT TO SYSTEM
#7 REBOOT TO LINEAGE RECOVERY IF YOU WISH TO ROOT
SIDELOAD MAGISK.APK
adb sideload magisk.apk
#8 REBOOT TO SYSTEM
Updates available in built in updater. settings, system, updater.
You can change preferences to check for updates daily.

Sounds interesting......even though I love stock, this is tempting!

TheGhost1951 said:
Sounds interesting......even though I love stock, this is tempting!
Click to expand...
Click to collapse
I'm with you man. I'm on stock too and Lineage is my least favorite ROM. I'm just trying to help others who like it and diagnose and fix a annoying bluetooth bug.

Is possible to post screen shots. plz
OOS camera included. And Oneplus setting

break.cold said:
Is possible to post screen shots. plz
OOS camera included. And Oneplus setting
Click to expand...
Click to collapse
Come-on guy, do your research like the rest of us here.....Google, bing, xda....search. put forth the effort and the reward is greater

What (and where) are the changes you made to Bluetooth connectivity? Does this solve the longstanding problem of "stuttering" audio on Bluetooth phone calls?

MJPollard said:
What (and where) are the changes you made to Bluetooth connectivity? Does this solve the longstanding problem of "stuttering" audio on Bluetooth phone calls?
Click to expand...
Click to collapse
I don't have it listed anywhere. I dumped the firmware from stock and pulled the bluetooth and implemented it into this. I tested it and didn't notice any issues but I went back to stock. Lineage is not my thing. All I can say is to test it out and report any issues and I'll continue to work on any problems that may exist.

09/27 update posted

10/01 update posted

TheSayaMan said:
10/01 update posted
Click to expand...
Click to collapse
Changelog?

Beytullah61 said:
Changelog?
Click to expand...
Click to collapse
Changes in regards to bluetooth connectivity only.
LineageOS/Bluetooth at main · MikeSaya1/LineageOS
Contribute to MikeSaya1/LineageOS development by creating an account on GitHub.
github.com

10/09 update posted. More bluetooth improvements.

TheSayaMan said:
10/09 update posted. More bluetooth improvements.
Click to expand...
Click to collapse
10/15 posted. October security patch.

Thread changed from LineageOS 19 Android 12 to LineageOS 20 BETA Android 13

Can you build for oneplus 9?

imbasador said:
Can you build for oneplus 9?
Click to expand...
Click to collapse
Yes, I'm working on it

Because of the lack of interest on this. This thread will be closed.

Thread closed at the OP's request.