A cm12.1 rom, compiled with CAF sources by me
What's CAF? CAF (CODE AURORA FORUM), it's a source provide by qualcomm instead LG. It has a better performance compared to CM stock, and since it uses the LP source (CM 12 uses JB), we don't need to do a lot of modifications to get it to work.
WARNING: THIS IS AN ALPHA AND UNOFFICIALY ROM, DON'T INSTALL IF YOU DON'T KNOW WHAT IS A BRICK, AND HOW TO REVERT THAT.
Code:
/* *** Disclaimer
* I am 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 KERNEL
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
* BOOM goes the Dynamite
*/
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
What is working:
- WIFI
- RIL
- GPS
- NFC
- CAMERA
- H/W AC.
- DT2W (knock On)
BUGS:
- I think any. REPORT ME IF.
Supported Variants:
-D800
-D801
-D802/5/6
-F320
-LS980
-VS980
Installationg Instructions:
(FIRST INSTALLATION)
- Reboot in Recovery
- Format system/data/cache
- Download and install bootstacks for your model. (VERY IMPORTANT, EXPLANATION IN FAQ)
- Reboot Recovery
- Download and install ROM zip for your model.
- Download and install GAPPS (You can use any for 5.1, I recommend BaNKs)
- Reboot! :laugh:
(UPDATE ROM)
- Reboot in Recovery
- Wipe cache
- Download and install ROM zip for your model.
- Reboot! :laugh:
DOWNLOADS:
Mod Edit: Downloads removed pending investigation
ROM = CM12.1 >>> [MODEL] >>> *.zip
BOOTSTACKS = BOOTSTACKS >>> *.zip
-===FAQ===-
WTF is bootstacks? Do I need it? Why?
-"Bootstacks" is how are called the boot partitions on device (laf, rpm, persist, etc). YES, you need it, since without you can't boot. The new lg lollipop source needs the lollipop bootstacks. The one we're using, is a LP bootstack with JB aboot, that provides us loki support.
I am on *ANY ROM*, do I need flash bootstacks?
-Doesn't matter which rom you are, I really recommend you to flash bootstacks.
I have a d805/d806 and I can't boot.
-You'll need a d802 baseband modded to work with your model. See 2# post.
OMFG, I installed the rom without the bootstacks and now I can't boot in recovery, neither in system.
-Power off your phone (press power button for 9s), then, pressing vol-up connect the USB. TCHARAM, now KDZ/TOT it!
Can I flash another kernel with this rom? (thx to @wulsic !)
-Only if this kernel is CAF, but I think there isn't any custom kernel by now supporting CAF. RenderBroken is working on it. If you have some skills, you can compile it from his source.
How can I come back to official CM / LG STOCK (KK/LP)? (thx to @Lawlrus !)
-CM: You'll need flash the JB bootloader before. You can find the images in lg-devs bootstack repo, but, many cm-based threads have an JB bootloader.zip.
-STOCK: You'll need flash KK bootloader before. You can find KK bootloader for d802 in dori's stock LP kernel thread.
Why I don't have root after flash?
-You need activate it in developer options:
How activate: Settings > About This Phone > tap seven times "Build Number". Now, press back and then, settings > Developer Options > Root Acess.
-===FAQ===-
THX TO:
-LG-DEVS TEAM. (For the CAF source, and bootstacks)
-CyanogenMod. (For the cm12.1, )
XDA:DevDB Information
CM12.1 CAF UNOFFICIAL, ROM for the LG G2
Contributors
daniel.stuart14
Source Code: https://github.com/lg-devs
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.4.x
ROM Firmware Required: LP BOOTSTACKS
Based On: CyanogenMod
Version Information
Status: Testing
Created 2015-05-30
Last Updated 2015-05-29
Reserved
FIXs AND MODs
D805/D806 BASEBAND:
1-Go to my mediafire (1# post), then BASEBANDS and download your device baseband.
2-Flash the zip in recovery, after flash BOOTSTACKS.
3-Restart!
INFO: D805/D806 uses D802 bootstacks + baseband.
Warning: You need flash this baseband ALWAYS after flashing bootstacks. (don't need if updating)
Warning 2: Bootstacks already has a modem, so, these basebands are only for unsupported devices, as d805/6.
Click to expand...
Click to collapse
Reserved
Changelog:
30/05: Sync with CM
Added d800, d801, vs980, ls980 & f320.
---Only for vs/ls980 & f320 (coming to others variants soon):
|---- Added script to set baseband
|---- Add loc_launcher service
29/05: First upload. (d802 only)
Based in CM12.1 with CAF sources from lg-devs.
Thank you···320 waiting to test.Now many of aosp roms for 320 that wifi and external card cannot be used perfectly.
greetings to you in Brazil
I installed on D802 version so far /all Good
only option that doesn't work is 4K video recording (it is available in options) / maybe it is my fault since i always delete internal storage after flashing everything ?
i tried also in google camera it starts recording but you cant find that file in gallery/file-manager.
Open Camera however records in 4K but in 16FPS in my room with medium light available.
I will test more but i think this is more stable than testing : )
Thank you
Good work!
Hey, don't want to sound noobish, but could you tell us the difference between this and "normal" cm?
PsychOlli said:
Hey, don't want to sound noobish, but could you tell us the difference between this and "normal" cm?
Click to expand...
Click to collapse
Without having to spend twenty paragraphs explaining what caf is.
This kernel base is 5.0 versus us currently using 4.2. Also the kernel is full caf versus the current kernel being caf patched.
can i ask whats the difference between CAF and normal 5.1.1 AOSP or CM12.1 roms?
sry for this question
freshbooy said:
can i ask whats the difference between CAF and normal 5.1.1 AOSP or CM12.1 roms?
sry for this question
Click to expand...
Click to collapse
Tldr: Qualcomm gives our CPU source code to caf . since we are a legacy device and don't get source from google. (Pure aosp)
Better optimizations for our device
Edit
my post can be deleted thx
Looking forward to the d803 build!
@daniel.stuart14 Nice, I also wanted to say or you could put a note for the flashing beginners that they must not flash a NON-CAF kernel as this is a CAF rom.
Also I wanted to say to you that Rashed97 is also having a caf-panel branch on the device and the kernel tree, it is a bit behind the other commits from the default cm-12.1 caf branch but includes changes for display detection and it also dumped loki in favor of bump. You can use this and pull the changes from the other caf branch but I suppose that Rashed97 is going to update the panel branch with the default caf's branch commits and make it the default branch.
This ROM is working so well.
dt2w works perfectly.
Whatsapp and VoIP audio is all good.
Skype microphone is working and is super clear.
Two thumbs up! Performance is stellar too!
mujka said:
greetings to you in Brazil
I installed on D802 version so far /all Good
only option that doesn't work is 4K video recording (it is available in options) / maybe it is my fault since i always delete internal storage after flashing everything ?
i tried also in google camera it starts recording but you cant find that file in gallery/file-manager.
Open Camera however records in 4K but in 16FPS in my room with medium light available.
I will test more but i think this is more stable than testing : )
Thank you
Click to expand...
Click to collapse
Hmmm, I think I know the problem. Instead 4K it should be 2K recording, since our phone doesn't support 4k. I'll take a look.
=JKT= said:
Looking forward to the d803 build!
Click to expand...
Click to collapse
I'm uploading d800/d801 now. If everything goes okay, ls980/vs980/f320 will be there today.
As d803 doesn't has an LP source, I can't compile it. When it comes out, we can talk about it.
So, if I understand correctly, we need JB bootloader for this one, right?
Sorry to ask if this is obvious, but just got my replacement back. I got black lines in my previous one, due to incompatible bootloader.
Thanks ahead!
wulsic said:
@daniel.stuart14 Nice, I also wanted to say or you could put a note for the flashing beginners that they must not flash a NON-CAF kernel as this is a CAF rom.
Also I wanted to say to you that Rashed97 is also having a caf-panel branch on the device and the kernel tree, it is a bit behind the other commits from the default cm-12.1 caf branch but includes changes for display detection and it also dumped loki in favor of bump. You can use this and pull the changes from the other caf branch but I suppose that Rashed97 is going to update the panel branch with the default caf's branch commits and make it the default branch.
Click to expand...
Click to collapse
I put in FAQ, thanks! :highfive:
About caf-panel branch, I think LP kernel detects the panel automatic. (In stock LP is how it works). But I'll take a look.
One thing I was wanting to do in future, is update the aboot to KK, and push bump over loki. But it'll need update bootstacks package, so let's wait a little time before.
errikosd said:
So, if I understand correctly, we need JB bootloader for this one, right?
Sorry to ask if this is obvious, but just got my replacement back. I got black lines in my previous one, due to incompatible bootloader.
Thanks ahead!
Click to expand...
Click to collapse
Nop, you need to use BOOTSTACKS in download area. It'll install JB aboot (bootloader), but with LP partitions. It's the better of both worlds. haha
@daniel.stuart14
As silly as it is, you and I both know its going to come up, But you might want to add a bit in the op about going from this ROM to another ROM.
That they need to flash say their 4.2 bootstack if they want to go back to a 4.2 kernel based ROM.
Or 4.4/5.0 bootstack for a stock based.
---------- Post added at 09:48 AM ---------- Previous post was at 09:35 AM ----------
By Tuesday, I'm going to see about setting up some Kind of reference thread.
Been meaning too for a while, but I'm so damn lazy
daniel.stuart14 said:
Hmmm, I think I know the problem. Instead 4K it should be 2K recording, since our phone doesn't support 4k. I'll take a look.
I'm uploading d800/d801 now. If everything goes okay, ls980/vs980/f320 will be there today.
As d803 doesn't has an LP source, I can't compile it. When it comes out, we can talk about it.
Click to expand...
Click to collapse
@daniel.stuart14 - could you please help get a gitcompare on the kernel defconfig ( d803 vs d802 in kitkat source) which is available at opensource.lge.com/osSch/list?types=ALL&search=d803 vs opensource.lge.com/osSch/list?types=ALL&search=d800 and opensource.lge.com/osSch/list?types=ALL&search=d802. There were lots of times in Kitkat, one could take a d802/d800 rom and flash a d803 kernel on top and be done.
Possibly a binary blob diff is also necessary.
I only request this because it is entirely likely that you have the source code lying around. That would be very helpful. thanks!
sandys1 said:
@daniel.stuart14 - could you please help get a gitcompare on the kernel defconfig ( d803 vs d802 in kitkat source) which is available at opensource.lge.com/osSch/list?types=ALL&search=d803 vs opensource.lge.com/osSch/list?types=ALL&search=d800 and opensource.lge.com/osSch/list?types=ALL&search=d802. There were lots of times in Kitkat, one could take a d802/d800 rom and flash a d803 kernel on top and be done.
Possibly a binary blob diff is also necessary.
I only request this because it is entirely likely that you have the source code lying around. That would be very helpful. thanks!
Click to expand...
Click to collapse
The problem is that, even if I compile for d803, we'll still without the LP bootstacks. So, it won't boot.
CAF kernel already has an d803-defconfig, unfortunately that's not the problem.
We can only wait.
Related
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Code:
#include
/*
* Your warranty is now void.
*
* I am 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 me for messing up your device, I will laugh at you.
*/
CyanogenMod is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. CyanogenMod does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for CyanogenMod is available in the CyanogenMod Github repo. And if you would like to contribute to CyanogenMod, please visit out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
Device-specific source code:
device
kernel
vendor
Discussion thread -->
What's working:
so far i have tested:
RIL (Calls, SMS, Mobile Datal)
Dual sim on xperia m dual (check notes section)
Display
Camera (photos, camcorder & panorama)
Audio and video
Wifi
Bluetooth
OpenGL rendering
Sensors (accelerometer,compass,light,proximity)
Sdcard
auto brightness
notification led
Wifi,Bluetooth and USB tethering
NFC
GPS
Not working/Tested:
for bugs see this post
Other everything is either untested or broken.
Note:
It's entirely possible that features not used by me (nor the people I've asked to test) are broken, but overall the device should be usable. You have been warned.
Because of art 1st boot take long time so don't panic and make post saying phone stuck on bootanim,
Dual sim works on xperia m dual with this patch
This is BETA so don't treat this as stable version.
CM-12.1 is only for 4.3 baseband. If you are on 4.1/4.2 baseband/firmware then Follow this instruction
If you want to flash unsigned zips or want to backup your phone then flash TWRP FOTA recovery from following thread (Xperia m dual users install fota recovery for flashing ril zip)
Download:
Nightly builds: http://download.cyanogenmod.org/?device=nicki&type=nightly
FXP CM12.1 Builds: http://fxpblog.co/cyanogenmod/cyanogenmod-12.1/
Final nightly build mirror: https://yadi.sk/d/ikPTJ1aIo8p5d
Gapps: http://forum.xda-developers.com/android/software/tk-gapps-t3116347
Install instructions: (For 1st time only)
boot into fastboot (ignore if you coming any 4.4/5.0 rom)
flash boot.img from cm12 zip (ignore if you coming from any 4.4/5.0 rom)
boot into custom recovery
Wipe data and cache
Flash the CM12.1 and gapps zip
Reboot
Upgrading from earlier version of CyanogenMod 12.1:
Boot into Recovery
Flash CM12.1 zip
Reboot
Reporting bugs:
Before Reporting bugs make sure you
Read "note" section
Using stock kernel
Not installed any mods/tweaks - if you have installed mods like xposed you can't report bug
Not modified system files
Checked the posts below for a solution / fix
Read the last 10 pages of this thread for a post with a similar problem
Backup, reflash with a full wipe (do this if mods like xposed is installed) and check if the bug is still there
provide logcat,kmsg. if you reporting radio problem then provide radio log.
Screenshots:
Credits:.
Fxp team and all other developer who is working on sony
Code Aurora Forum
CyanogenMod Team
Cybojenix
And Special Thanks to All Donors
XDA:DevDB Information
CyanogenMod 12.1 for Xperia M, ROM for the Sony Xperia M
Contributors
PecanCM
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.4.x
ROM Firmware Required: Stock 4.3 Firmware
Version Information
Status: Nightly
Created 2015-04-02
Last Updated 2016-02-02
Changelog
BETA 4 24-05-2015
Android-5.1.1_r3 (LMY48B)
Fixed random reboots
Fixes for CVE-2015-3636
Enabled logd
Updated mpdecision and thermald
Updated cm source
BETA 3 27-04-2015
Android 5.1.1 (LMY47V)
Fixes for CVE-2014-5206,2014-7970,2014-2523,2014-8173,2014-9715,2015-1420,2015-2922 and 2015-2041
Enabled netmgr qos
Enabled NEON based AES and SHA1 implementation
Enabled last_kmsg support
Enabled HW aac encoder
Kernel sync with aosp-common/android-3.4
Updated kernel and wlan driver to LA.AF.1.1_rb1.17
Updated mpdecision and thermald
Updated vidc firmware
Updated cm source
BETA 2 08-04-2015
Fixed writing to external sdcard in ums mode
Re-enabled multicolored notification
Updated adreno blobs to LA.AF.1.1_rb1.16(android-5.1)
Disabled legacy mmap
Enabled qcom art and skia optimization
Added missing qcom power hal
Other general cleanup and updates
Updated cm source
BETA 1 03-04-2015
Initial release
FAQ
Q: The 'Developer and Performance options' from 'settings' are gone. Where are they?
A: Touch the 'Build number' seven times in 'about phone'. Then they will appear.
Q: Why no root access?
A: Go to Developer and Performance options, select root access and now select Apps and ADB.
Q: I'm coming from 4.1 and now i can't view my internal sd data, Why ?
A: Go to Data/media now move your all internal sd data to folder named 0 Means under /data/media/0 then you can view your internal sd data.
Great work! I've dirty flashed it over cm12 and it's working flawless so far.
BTW nfc is working I tested it with my smarttags
Great news everyone.
Does it have zram and other latest stuff enabled?
Yes
Hows Battery and performance ?Any significant Improvements vs latest cm12 5.0.2?
Farsiris said:
Hows Battery and performance ?Any significant Improvements vs latest cm12 5.0.2?
Click to expand...
Click to collapse
I just flashed it so can't really tell anything about battery, but it generally seems to perform better than CM12.
I can tell animations are even more smoother, and some ripple effects that used to stutter are smoother now.
krygo said:
I just flashed it so can't really tell anything about battery, but it generally seems to perform better than CM12.
Click to expand...
Click to collapse
Okay .Thx Ill try myself later .
GPS
Hi Pecan, Is GPS completely broken r partially working?
Mod Edit: Post edited
No need to quote the whole OP
Can someone mirror the download link pls? The authorization process at mediafire is driving me nuts!!
How can I flash GAPPS, CM recovery won't let me.
Sh0m1 said:
How can I flash GAPPS, CM recovery won't let me.
Click to expand...
Click to collapse
http://forum.xda-developers.com/xpe...very-cwm-twrp-recoveries-custom-roms-t3016507
just use custom recovery
iks8 said:
http://forum.xda-developers.com/xpe...very-cwm-twrp-recoveries-custom-roms-t3016507
just use custom recovery
Click to expand...
Click to collapse
Thanks, i wasn't sure if it works with 5.1 .
Does battery life improve in 5.1?
Gps working good.
Sent from my C1904 using Tapatalk
@PecanCM good work sir and go on[emoji122] [emoji122]
Performance is much much better! Thank you master!!
When official version ?
My phone randomly rebooted 3 times today. I wasn't even touching it. No app was running in foreground. Stock kernel.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* I am 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 me for messing up your device, I will laugh at you.
*/
What is Code Aurora Forums ?
Code Aurora Forum (CAF) is a consortium of companies with projects serving the mobile wireless industry. Software projects it concerns itself with are e.g. Android for MSM, Femto Linux Project, LLVM, MSM WLAN and Linux-MSM. Code Aurora is basically AOSP plus all Qualcomm specific enhancements and optimization.
What is AOSP-CAF ?
AOSP-CAF is meant to join AOSP and CAF projects into a widely usable repository,
stored on https://github.com/AOSP-CAF/. It also benefits from a few LineageOS updates.
Finally, AOSP-CAF Nougat also includes OMS theming implementations.
Downloads Links
AOSP-CAF 7.x (Unlocked Bootloader) :
Xperia M (Nicki) : AOSP-CAF Nougat [01-05-17]
Old Versions:-
AOSP-CAF Nougat [29-04-17]
Google Applications (optional) :
OpenGapps : http://opengapps.org/ (Use packages for ARM, Android 7.1, Micro or Pico)
About AOSP-CAF : Repositories available on https://github.com/AOSP-CAF/
About GApps : Flash the GApps before the first boot. If not, a clean flash is recommended.
Flashing and updating
AOSP-CAF clean install :
- (Optional) Flash the boot.img kernel from the ROM zip with Fastboot or Flashtool
- (Optional) Wipe the data & cache (Backup to make sure not to loose data)
- Flash the AOSP-CAF ROM zip from the Recovery
- Flash the Dual SIM Patch if you own Xperia M Dual
- (Optional) Flash the GApps to have the Google Applications
- (Optional) Flash the SuperSU zip (recommended, see Q&A informations)
- (Optional) Every additional zip you want to flash
- Reboot
AOSP-CAF update / upgrade :
- (Information) Don't wipe anything unless you want to
- Flash the latest AOSP-CAF ROM zip from the Recovery
- Flash the Dual SIM Patch if you own Xperia M Dual
- (Optional) Flash the GApps on first install / upgrade. Not required later, but do update sometimes
- (Optional) Flash the SuperSU zip (recommended, see Q&A informations)
- (Optional) Every additional zip you want to flash
- Reboot
About UNOFFICIAL builds
Device tree : https://github.com/STRYDER-007/aosp_device_sony_nicki
Kernel sources : https://github.com/LineageOS/android_kernel_sony_msm8x27/
Vendor blobs : https://github.com/TheMuppets/proprietary_vendor_sony/
ROM sources: https://github.com/AOSP-CAF/
Issues and reports
- Report issues only if you use the ROM kernel
- If an additional mod is installed, make sure it's unrelated, and mention it
- Make sure the issue wasn't discussed earlier in the threads
- Share a log of the error with CatLog for example
Q&A - FAQ
Q : Is the ROM suited for daily usage ?
A : Yes.
Q : Where can I change the Quick Tiles and Status Bar ?
A : Long press the Settings icon in the notifications drawer.
> You will have access to the SystemUI Tuner from AOSP.
AOSP-CAF available also thanks to :- AOSP and CodeAurora Forums
- The LineageOS Team
- @Men_in_black007 and the AOSP-CAF Team
- @AdrianDC for Sony related stuff and thread template
- Everyone involved in working and testing
XDA:DevDB Information
[ROM][7.1][OMS] AOSP-CAF for Xperia M [Single/Dual], ROM for the Sony Xperia M
Contributors
STRYDER~007
ROM OS Version: 7.x Nougat
Based On: AOSP
Version Information
Status: Testing
Created 2017-04-30
Last Updated 2017-04-30
Great sir !!!, i'll try this ROM tomorrow :laugh:
Rom is great, but I can't record videos with build-in camera app (Camera close when I select video). Log >> https://pastebin.com/RccdJ2ER
With Open Camera it works, but quality is terrible
EDIT: It's not that bad.
Thanks for the rom....you are the best and thank you sooo much for still supporting our device...Much appreciation and thanks to you
Can i add this rom to my nougat rom thread??? I mean i have written only those rom names which get updated even rarely but are not abandoned
Hello @STRYDER~007!
Thanks for one more contribution for our device. I'm sure that it will be an awesome ROM. But what are the major changes in this ROM? I mean is it the same like @PecanCM's AOSP version, or it's a bit different?
Marek8299 said:
Rom is great, but I can't record videos with build-in camera app (Camera close when I select video). Log >> https://pastebin.com/RccdJ2ER
With Open Camera it works, but quality is terrible
EDIT: It's not that bad.
Click to expand...
Click to collapse
Alright. I'll switch to Camera2 for now then. It seems Snap cam is broken.
Adarsh Dubey said:
Thanks for the rom....you are the best and thank you sooo much for still supporting our device...Much appreciation and thanks to you
Can i add this rom to my nougat rom thread??? I mean i have written only those rom names which get updated even rarely but are not abandoned
Click to expand...
Click to collapse
Yeah sure go ahead!
mayanxoni said:
Hello @STRYDER~007!
Thanks for one more contribution for our device. I'm sure that it will be an awesome ROM. But what are the major changes in this ROM? I mean is it the same like @PecanCM's AOSP version, or it's a bit different?
Click to expand...
Click to collapse
PecanCM's AOSP is based on Google's pure AOSP with only device specific additions. This AOSP-CAF is mixture of both AOSP and some goodies/patches/fixes/upstream changes from Code Aurora Forum. Plus it has theme engine! Just install Substratum app from play store. You'll notice the differences when you'll flash this ROM.
Thanks for the reply brother! One more thing - am I going to lose dual SIM feature if I flash SuperSU after flashing the patch, or am I going to lose root if I flash dual SIM patch after SuperSU like it was happening in AOSP?
mayanxoni said:
Thanks for the reply brother! One more thing - am I going to lose dual SIM feature if I flash SuperSU after flashing the patch, or am I going to lose root if I flash dual SIM patch after SuperSU like it was happening in AOSP?
Click to expand...
Click to collapse
Uh I'm not sure.No other user reported such things. So you'll have to try it yourself.
STRYDER~007 said:
Uh I'm not sure.No other user reported such things. So you'll have to try it yourself.
Click to expand...
Click to collapse
OK, I'll try and report back.
Nicklas Van Dam said:
Great sir !!!, i'll try this ROM tomorrow :laugh:
Click to expand...
Click to collapse
Marek8299 said:
Rom is great, but I can't record videos with build-in camera app (Camera close when I select video). Log >> https://pastebin.com/RccdJ2ER
With Open Camera it works, but quality is terrible
EDIT: It's not that bad.
Click to expand...
Click to collapse
Adarsh Dubey said:
Thanks for the rom....you are the best and thank you sooo much for still supporting our device...Much appreciation and thanks to you
Can i add this rom to my nougat rom thread??? I mean i have written only those rom names which get updated even rarely but are not abandoned
Click to expand...
Click to collapse
mayanxoni said:
Hello @STRYDER~007!
Thanks for one more contribution for our device. I'm sure that it will be an awesome ROM. But what are the major changes in this ROM? I mean is it the same like @PecanCM's AOSP version, or it's a bit different?
Click to expand...
Click to collapse
Is it possible for any of you to join me on Telegram for StryFlex testing? PM me if you want to be a beta tester.
My username- STRYDER_007
Tried!
A few things that I noticed:
Everything works perfectly as supposed to(except Camera app - mainly Video recording).
Dual SIM persists even after flashing SuperSU.
SIM networks fluctuate for a while after first boot.
ROM Updated
AOSP-CAF Updated. Reverted to Camera2. Fixed video recording issue. Enjoy!
Download:-
AOSP-CAF Nougat [01-05-2017]
STRYDER~007 said:
AOSP-CAF Updated. Reverted to Camera2. Fixed video recording issue. Enjoy!
Download:-
AOSP-CAF Nougat [01-05-2017]
Click to expand...
Click to collapse
Thanks alot for the update we will join as beta tester asap
The kernel within the ROM is not working with my Sony M - with normal boot it stucks with SONY on the screen, trying to upgrade the rom wia recovery it says "no e/ -- SD card not found"
Solution:
I took TWRP 3.0.20 for the device - SD card is now present - img can be flashed via recovery
I wanted to use it but my phone died ;--;
KayM6.0.1 said:
I wanted to use it but my phone died ;--;
Click to expand...
Click to collapse
You mean permanently? Or due to charge?
ROM Screenshots pls..
Aaditya.k96 said:
ROM Screenshots pls..
Click to expand...
Click to collapse
This is one of my favorite ROMs.
EDIT: It is themed using AOSP DARK MATERIAL
Here you go buddy:
mayanxoni said:
This is one of my favorite ROMs.
EDIT: It is themed using AOSP DARK MATERIAL
Here you go buddy:
Click to expand...
Click to collapse
Thanks :good:
thanks for your ROM, give me something new to try, I thought this phone is no longer get support from this forum.
I hope you would soon add shorcuts "Sync" and "Screenshot" in Quicksetting They both are so handy. Also my power and camera buttons are dead, I need those shortcuts.
Thanks again. @STRYDER~007
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Code:
#include
/*
* Your warranty is now void.
*
* I am 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 me for messing up your device, I will laugh at you.
*/
SlimRoms is a custom android operating system built from Android Open Source Project (AOSP). Our aim is to offer a clean, fast and high-quality experience on all your devices.
Our main goal is to offer users a slimmed down but still feature rich alternative to other android operating systems. The entire team work together to bring you this tailor-made beauty straight from AOSP source code.
All of the sources can be publicly viewed through GitHub. You can stop by the public Gerrit to submit patches of any type or help translate Slim to your language through our Crowdin project
Feature that included :
Android Nougat [AOSP]
Slim Launcher
Slim Dim
Slim Recents
Removed Bloatwares
Custom Status Bar Option
Custom Recent Panel Apps Option
Custom Navigation Bar Option
Night Light
Improved Performance
And Other Improvement
What's Working :
RIL (Calls, SMS, Mobile Datal)
Display
Camera
Audio and video
Wifi
Bluetooth & Bluetooth Audio
OpenGL rendering
Sensors (accelerometer,compass,light,proximity)
Auto brightness
Notification led
Storage
GPS
Mtp/ptp working same as 6.0
NFC
Adoptable storage
Bugs / Not Working :
Dual Sim device : I don't know this will work or not, try to flash this zip Dual Sim Patch
How To Install
Download Slimroms 7, GAPPS, and SuperSU / Magisk Manager and then copy to your sdcard
Go to recovery mode (TWRP) and wiped your system,cache and data partition
Install Slimroms 7 and GAPPS
NOTE : For dual sim device, try to using Magisk if SuperSU make problem with Dual Sim Connectivity.
Reboot system (first boot take a much time, 5 - 10 minutes)
Download Link
Download Link is on download tab
Download Tab
NOTE :
- NEW updated build available in download tab on this thread
Additional Download
- [OpenGAPPS] : Download
- [Magisk] : Download
Screenshots
Before Reporting bugs make sure you:
Using stock kernel
Not installed any mods/tweaks - if you have installed mods like xposed you can't report bug
Not modified system files
Checked the posts below for a solution / fix
Read the last 10 pages of this thread for a post with a similar problem
Backup, reflash with a full wipe (do this if mods like xposed is installed) and check if the bug is still there
Provide logcat,kmsg/dmesg. if you reporting radio problem then provide radio log.
Describe steps to reproduce bug
Special Thanks
@PecanCM for device source code and almost all code for nicki
@josue Rivera (SlimRoms Community G+ Owner)
@andi B - SlimRoms Community G+ (For troubleshooting and solution)
@robin - SlimRoms Community G+ (For troubleshooting and solution)
@thichthat for saving my device in almost destruction condition
And the others (Remind me if i'm forget it)
XDA:DevDB Information
[ROM][7.1.2][NJH7B] SlimRoms 7 Nougat [Unofficial][BETA], ROM for the Sony Xperia M
Contributors
Nicklas Van Dam, PecanCM, thichthat
Source Code: https://github.com/SlimRoms
Source Code :
Device Tree : Device Source
Kernel Source : Kernel Source
Vendor Source : Vendor Source
SlimRoms Source : SlimRoms Source
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.4.x
ROM Firmware Required: 4.3 / 15.4.A.1.9
Based On: AOSP
Version Information
Status: Beta
Current Beta Version: v1.2
Beta Release Date: 2018-02-18
Created 2017-06-15
Last Updated 2018-02-18
Changelog
Changelog :
Build 20180218 (Slim 2.0)
- Updated to latest SlimRoms source (v2.0)
(SlimRoms Specific Change)
- AOSP security update to 2018-01-05
- Translation update
- Updates to hw/qcom/audio-caf/msm8916: Update to LineageOS latest
- Snap: Updates and fixes from LineageOS
- Update SensitivePhoneNumbers
- APN updates
- Misc build changes
Build 20170618 (Slim 0.28)
- Updated to latest SlimRoms source (v0.28)
- Updated kernel security patches to 20170615 based on MSM8960 source
- Changed Snap camera to Camera2 to fix video recording issue on Snap camera app
Build 20170615 (Slim 0.27)
- INITIAL RELEASE
Reserved #2
..
Reserved #3
..
Thank you very much.
Will flash it tomorrow and report back. Thanks for the ROM brother.
mayanxoni said:
Will flash it tomorrow and report back. Thanks for the ROM brother.
Click to expand...
Click to collapse
Okay, have try
I'm stuck in boot for like an hour. I don't think that's normal?
Edit: Am I missing something? This is the first time I'm upgrading to 7.1 from 6.0 and no matter what ROM I try I get stuck at boot.
TheRealSS said:
I'm stuck in boot for like an hour. I don't think that's normal?
Edit: Am I missing something? This is the first time I'm upgrading to 7.1 from 6.0 and no matter what ROM I try I get stuck at boot.
Click to expand...
Click to collapse
are you already try to wiped data after installing this ROM?
Nicklas Van Dam said:
are you already try to wiped data after installing this ROM?
Click to expand...
Click to collapse
I wiped system, cache, data and then flashed the ROM. Every 7.1 ROM I've tried gets stuck in boot.
TheRealSS said:
I wiped system, cache, data and then flashed the ROM. Every 7.1 ROM I've tried gets stuck in boot.
Click to expand...
Click to collapse
what is your stock firmware that you use it before? is that 15.4.A.1.9?, what package that you're flashed after flash this ROM?
Nicklas Van Dam said:
what is your stock firmware that you use it before? is that 15.4.A.1.9?, what package that you're flashed after flash this ROM?
Click to expand...
Click to collapse
I haven't used stock in years now so I don't remember the last firmware I was on. I've been on CM13 for the last 7 months or so and then I flashed your ROM and then flashed opengapps after. I also tried booting without flashing gapps but I still get stuck on boot. The problem also occurred when I tried flashing AOSP 7.1
@Nicklas Van Dam,
good work and go on [emoji3] [emoji111] [emoji111]
Sent from my Lenovo K10a40 using Tapatalk
TheRealSS said:
I haven't used stock in years now so I don't remember the last firmware I was on. I've been on CM13 for the last 7 months or so and then I flashed your ROM and then flashed opengapps after. I also tried booting without flashing gapps but I still get stuck on boot. The problem also occurred when I tried flashing AOSP 7.1
Click to expand...
Click to collapse
trying to re-flash your stock firmware based on your device model, and try to flash it with latest firmware with full wipe. I don't know too why, if you're only flash rom and stuck on boot. You're not flash any custom kernel right?
but i'm not sure that from firmware, since you can install lollipop and marshmallow without any error. Have you try to flash any Pure AOSP or AOSP CAF for nougat on your device?
And try to not include supersu as flashing step, try only flash ROM only.
Updated to new build
Releasing new build with updated version from slimroms source and included some fix and kernel security patches
Changelog for new update:
Build 20170618 (Slim 0.28)
- Updated to latest SlimRoms source (v0.28)
- Updated kernel security patches to 20170615 based on MSM8960 source
- Changed Snap camera to Camera2 to fix video recording issue on Snap camera app
For more changelog that provide from slimroms, check in here https://slimroms.org/. This is just changelog that applied to our device.
New build available in download tab now, just check it and download new build. I'm not using androidfilehost again for this time, since i'm have problem with upload data on that website.
Have try !!!
Request for a rom
@Nicklas Van Dam
great work here .Slim roms are great and are low on resource utilization . :good:
Can i request you a few things?
1)Ambient display-I guess i could be added to device tree so that it could work (you did it before with mods )
2)puse hand wave features(the one in which notifications are shown is ambient display mode when phone is removed from the pocket or hand is waved over the proximity sensor - again releated to ambient display and proximity sensor
3)Can you also build Aospa (paranoid rom) - its also based on aosp (so lighter ) and has few additional features too (though most of them are still private for now)
Thanks a lot
Btw if you need a tester my xperia m dual is now my secondary device so as long as something does not hardbrick it ,i can test pretty much everything
Download link from download section not working
hhjadeja007 said:
Download link from download section not working
Click to expand...
Click to collapse
Sorry for late respond, link download it's working bro. Try to access it with your PC and check download tab to download it.
I've much homework in this week, sorry
hhjadeja007 said:
Download link from download section not working
Click to expand...
Click to collapse
Working, just downloaded slim_nicki-ota-5ba61727ad.zip
And, Nicklas Van Dam, thank you for your effort to revive our device kernel. Can we see all commits in your kernel repo since this:
Nicklas Van Dam said:
Changelog :
Build 20170618 (Slim 0.28)
- Updated kernel security patches to 20170615 based on MSM8960 source
Click to expand...
Click to collapse
I wish to integrate your kernel in my unofficial builds =)
droncheg said:
Working, just downloaded slim_nicki-ota-5ba61727ad.zip
And, Nicklas Van Dam, thank you for your effort to revive our device kernel. Can we see all commits in your kernel repo since this:
I wish to integrate your kernel in my unofficial builds =)
Click to expand...
Click to collapse
Just look at kernel source on first thread, you can see link and that's link for kernel source .
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
LineageOS is a free, community built, aftermarket firmware distribution of Android 10.0, which is designed to increase performance and reliability over stock Android for your device.
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review.
Code:
#include "std_disclaimer.h"
/*
* Your warranty is now void.
*
* I am 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 me for messing up your device, I will laugh at you.
*/
What's working:
RIL (Calls, SMS, Data)
Fingerprint
Wi-Fi
Bluetooth
Camera
Video Recording
Video Playback
Audio
Sensors
Flash
GPS
DAC
Vibration
Wifi Hotspot
Selinux enforcing
What's not working:
BT Audio in some situations
Where are the features? (LOS18.0 edition)
LineageOS 18.0 is in early development process so don't complain about xyz features missin or crashing!
Instructions:
you flash in TWRP
you DONT inject TWRP (yet, when TWRP is made for metadata, then you can)
you reboot to other lots recovery (atm thats lineage one)
there you HAVE TO format data/factory reset
then you can install gapps and so (by apply update and adb sideload)
then boot system
V40 Telegram group chat
Downloads:
GDrive
Sources:
Device Tree judypn: judypn
Device Tree sdm845-common: sdm845-common
Device Tree lge common: lge common
hardware/lge: hardware/lge
Kernel: sdm845
Vendor: lge
lineage-17.1 branch
XDA:DevDB Information
LOS for Judypn, ROM for the LG V40
Contributors
SGCMarkus
Source Code: https://github.com/LineageOS
ROM OS Version: Android 10/11
ROM Kernel: Linux 4.x
ROM Firmware Required: 10
Version Information
Status: Stable + Pre-Aplha
Created 2019-09-20
Last Updated 2020-09-20
Reporting Bugs
DO NOT Report bugs if you're running a custom kernel or you installed Xposed
Grab a logcat right after the problem has occurred. (Please include at least a few pages of the log, not just the last few lines, unless you know what you're doing.)
If it is a random reboot, grab dmesg . (Do not bother getting a logcat unless you can get it just before the reboot. A logcat after a reboot is useless)
If the problem disappears after running "setenforce 0" from a root shell, grab /data/misc/audit/audit.log
Remember to provide as much info as possible. The more info you provide, the more likely that the bug will be solved. Please also do not report known issues.
Changelogs
Release 20.09.2019
- Initial release
Release 02.11.2019
- Updated LOS sources (October security patch, other things)
- Switched to Z01R prebuilt Display and Media HALs
- Building nearly everything except the necessary prebuilt from source (Display + Media HALs)
- Fixed Wifi hotpot (thx to @Xsavi for pointing me into the right direction )
- Vibration wont **** up anymore (but is weaker instead for some reason)
- Tons of other stuff i might have forgotten
Release 05.01.2020
- Updated LOS 17.0 to LOS 17.1 (december security patch, pixel feature drop rebase)
- Updated Z01R prebuilt Display and Media HALs to final
- Using V405EBW 20d (November) proprietary files
- Added SDFAT driver for exfat support by the kernel
- Few wifi changes
- other things i may have forgotten
Release 09.12.2020
- Updated LineageOS sources, September patch
- based on V405EBW 30b -> requires 10 firmware
- enabled A2DP offload + Qti BT Stack
- Qti power hal + different dt2w
- fixed offscreen gestures
- enabled metadata encryption (ext4 + f2fs supported) by using persdata
- SELinux enforcing (gib logs if something doesnt work properly, so far what i tested it worked)
- removed some unneeded LG crap
- rebased kernel on V405EBW 30b + CAF Upstream to 08100, Linux Upstream to 4.9.235
- fixed DAC issues with avc reset/it turning off automatically
Frequently Asked Questions:
Q. Can this ROM be flashed through TWRP?
A. Yes, proceed with the latest TWRP image
Q. Sounds good. How can I contribute to project?
A. Test the build as much as you can and report bugs which can be reproduced with exact steps and are not random.
Q. How to disable "Apps running in background" dialog?
A. When you see the dialog, long press on it and select "Settings". From there, you'll have a toggle to disable it.
Q. Which Models of the V40 are supported?
A. Tested on V405EBW and V405UA so far, but should work on all, EXCEPT US T-mobile variant.
Wow. Android 10 with los17 came so fast to LG V40. And seems like it's nearly daily driver condition.
Was thinking of buying lg v40 but now I'll definitely go buy it as development seems great on it ?.
You're so awesome!
Any screenshots?
Awesome work Markus! Your dedication to the development of this device is extremely encouraging to get other to want to start developing on this phone. Thank you for your work!
Inerent said:
Any screenshots?
Click to expand...
Click to collapse
Updated with screenshots ^^
@SGCMarkus .. I think you meant V40 telegram group
neocyke said:
@SGCMarkus .. I think you meant V40 telegram group
Click to expand...
Click to collapse
Uuups, too much copy paste xD
Thanks, corrected it, but atleast the link behind it went to the V40 group
Awesome guys thank you all, I will be donating. Question how do I install TWRP on my Sprint (Unlocked Pie) to install this?
Droidman61 said:
Awesome guys thank you all, I will be donating. Question how do I install TWRP on my Sprint (Unlocked Pie) to install this?
Click to expand...
Click to collapse
SGCMarkus already put up the guide for that
Droidman61 said:
Awesome guys thank you all, I will be donating. Question how do I install TWRP on my Sprint (Unlocked Pie) to install this?
Click to expand...
Click to collapse
You can follow this guide here: https://forum.xda-developers.com/lg-v40/development/twrp-lg-v40-judypn-t3970111
good luck!
SGCMarkus said:
...
Click to expand...
Click to collapse
Is there any chance you could try and port Lineage 17 to the V20?
Why doesn't this work on the T-Mobile model, and is there any hope for owners of that model in terms of custom ROMs?
What partitions would I check on backup in TWRP if I was going to install Lineage 16 or 17?
samfriedmann_ said:
Why doesn't this work on the T-Mobile model, and is there any hope for owners of that model in terms of custom ROMs?
Click to expand...
Click to collapse
Because T-Mobile wants to be different, if you try to unlock the bootloader the normal way you get a brick. If my memory is working correctly, Vlad has mentioned something about being able to unlock the bootloader but with soldering and opening the device itself.
---------- Post added at 07:25 PM ---------- Previous post was at 07:24 PM ----------
Android4Lif said:
What partitions would I check on backup in TWRP if I was going to install Lineage 16 or 17?
Click to expand...
Click to collapse
Well first you would backup everything minus system.img and Vendor.img...on both slots just to make sure
samfriedmann_ said:
Why doesn't this work on the T-Mobile model, and is there any hope for owners of that model in terms of custom ROMs?
Click to expand...
Click to collapse
The tmobile variants always have a different RSA key for their firmware -> the one from the other models wont work.
Kernel and so on would work fine (would just need different firmware files), but the issue is that you cant even unlock/root in the first place (to my knowledge)
Unbelievably great work guys!!!!! My upgrade is available next month but this really makes me think twice!
How does it run? Battery life any better on this? Sound? Thanks again!
I have it installed but keep losing my phone/data. It won't recognize my SIM card any suggestions?
Droidman61 said:
I have it installed but keep losing my phone/data. It won't recognize my SIM card any suggestions?
Click to expand...
Click to collapse
What carrier are you with?
[ROM][10] LineageOS 17.1 [OFFICIAL]
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
LineageOS is a free, community built, aftermarket firmware distribution of Android 10, which is designed to increase performance and reliability over stock Android for your device.
Code:
/*
* Your warranty is now void.
*
* I am 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 me for messing up your device, I will laugh at you.
*/
NOTE
Should you ever face any issues, capture logs. I also need to know what build you're on (build number or at least a date).
Hint: "It doesn't work" is not a bug report and posts like this will be ignored.
KNOWN ISSUEs
The Sony stock camera does not work at the moment.
INFO
This ROM does not use the device trees/kernel from sonyxperiadev (aka SODP). The device tree was made from scratch, and the stock kernel (based off 52.1.A.x.y) has been used.
DOWNLOAD
Official builds
NOTE: Since the official builds are signed, you can't simply upgrade from my unofficial builds -- you can either migrate to an official build using a script or do a clean install.
All unofficial builds
Optional: Add-ons
INSTRUCTIONS
First install
Updating to a newer build
SOURCE
LineageOS
Kernel
XDA:DevDB Information
Lineage 17.1 for the Sony Xperia XZ2 Compact, ROM for the Sony Xperia XZ2 Compact
Contributors
Olivier, Sjll
Source Code: https://github.com/LineageOS
ROM OS Version: Android 10
ROM Kernel: Linux 4.x
ROM Firmware Required: 52.1.A.3.49
Based On: LineageOS
Version Information
Status: Stable
Created 2020-04-28
Last Updated 2020-07-31
Changelog
CHANGELOG
20200724:
- addressed critical SELinux denials
20200722:
- added exFAT support to the kernel
- set SELinux to enforcing
- merged July security patches
- merged 52.1.A.3.49 blobs
20200613:
- merged June security patches
- merged 52.1.A.2.1 kernel
20200525:
- fixed microphone issues when the speaker was on during calls
- fixed wireless display/screen mirroring
- added a script for dynamic single/dual SIM variant detection
- merged 52.1.A.2.1 blobs
20200520:
- fixed USB tethering
- fixed notification LED
- merged May security patches
20200428:
- initial public release.
BUILDING
Please check the Lineage wiki for building instructions.
Safety Net
Good afternoon.
I would like to know if this ROM has a Google Play (Safety Net) certificate.
Thanks for the development.
Mykemonster said:
Good afternoon.
I would like to know if this ROM has a Google Play (Safety Net) certificate.
Thanks for the development.
Click to expand...
Click to collapse
Hi, this blog post should answer your question.
Wow, so happy to see this thread. Especially since I just placed an order for the phone an hour ago.
Will you be writing instructions on how to unlock the bootloader and install recovery?
Or should we follow the same steps from the AOSP thread?
Thanks a lot!
Hello, I flashed it in twrp and it failed. Then I tried to flash it using fastboot, and it stopped at the sony logo
ExoDroid said:
Wow, so happy to see this thread. Especially since I just placed an order for the phone an hour ago.
Will you be writing instructions on how to unlock the bootloader and install recovery?
Or should we follow the same steps from the AOSP thread?
Thanks a lot!
Click to expand...
Click to collapse
You can check sony.com for bootloader unlocking instructions. For flashing my builds, you can either use TWRP or Lineage recovery.
Linglai233 said:
Hello, I flashed it in twrp and it failed. Then I tried to flash it using fastboot, and it stopped at the sony logo
Click to expand...
Click to collapse
Please be more specific:
Which TWRP build did you use?
Why did it fail; which error code was returned? Do you have a recovery log?
How did you extract fastboot images from the OTA zip file?
Model number of your device?
Olivier said:
You can check sony.com for bootloader unlocking instructions. For flashing my builds, you can either use TWRP or Lineage recovery.
Please be more specific:
Which TWRP build did you use?
Why did it fail; which error code was returned? Do you have a recovery log?
How did you extract fastboot images from the OTA zip file?
Model number of your device?
Click to expand...
Click to collapse
thank you for your reply
Before flashing, I flashed the Stock firmware with version number 52.1.A.0.672, TWRP comes from MartinX3
‘Https://forum.xda-developers.com/xperia-xz2/development/recovery-twrp-3-3-1-0-t4074305’
But I flashed the generic twrp of firmware 52.1.a.0.618, so it stopped at the TWRP logo and could not enter twrp.
Then I used ‘payload_dumper’ to extract the fastboot image. Based on the stock firmware version 52.1.A.0.672, I flashed it using fastboot, but it stopped on the SONY logo.
I flashed the generic twrp of firmware 52.1.a.0.618 on the Stock firmware with the version number 52.1.A.0.618, and twrp can be used normally. Then I flashed LineageOS 17.1 in twrp. It succeeded.
Currently I am enjoying LineageOS 17.1
My model is SONY XPERIA XZ2 Compact Dual
Linglai233 said:
I flashed the generic twrp of firmware 52.1.a.0.618 on the Stock firmware with the version number 52.1.A.0.618, and twrp can be used normally. Then I flashed LineageOS 17.1 in twrp. It succeeded.
Currently I am enjoying LineageOS 17.1
My model is SONY XPERIA XZ2 Compact Dual
Click to expand...
Click to collapse
I am also running stock firmware 52.1.A.0.672 currently and would like to install 17.1
If I understood your comment correctly, I will have to first downgrade the firmware to 52.1.a.0.618?
And then install TWRP for 52.1.a.0.618?
flashing magisk doesnt work on this
flashing magisk doesnt work on this
ExoDroid said:
I am also running stock firmware 52.1.A.0.672 currently and would like to install 17.1
If I understood your comment correctly, I will have to first downgrade the firmware to 52.1.a.0.618?
And then install TWRP for 52.1.a.0.618?
Click to expand...
Click to collapse
Yes friend, if you want to install LineageOS 17.1, you should first downgrade the firmware to 52.1.a.0.618, then install TWRP for 52.1.a.0.618
My English is very poor, so I use google translation to help me, there may be some grammatical errors, please forgive me
How is the camera in Lineage?
Is it good like stock or is it like in pixel experience?
skaggmuff said:
How is the camera in Lineage?
Is it good like stock or is it like in pixel experience?
Click to expand...
Click to collapse
I think it goes without saying that the camera on custom ROMs will never be as good as on Stock, but I'd say the quality is pretty OK nevertheless. It should definitely be better than on Pixel Experience - they use Sony AOSP (SODP) as a base, while this port uses the Stock blobs and kernel.
Olivier said:
I think it goes without saying that the camera on custom ROMs will never be as good as on Stock, but I'd say the quality is pretty OK nevertheless. It should definitely be better than on Pixel Experience - they use Sony AOSP (SODP) as a base, while this port uses the Stock blobs and kernel.
Click to expand...
Click to collapse
Will the camera app permit to record DNG files (RAW) and not only JPG. If such, I'd be very grateful if someone could share a DNG files. I'd like to check if is is supported by Adobe Lightroom. I would report once checked.
Olivier said:
I think it goes without saying that the camera on custom ROMs will never be as good as on Stock, but I'd say the quality is pretty OK nevertheless. It should definitely be better than on Pixel Experience - they use Sony AOSP (SODP) as a base, while this port uses the Stock blobs and kernel.
Click to expand...
Click to collapse
Okay, thanks for your answer
Thanks, no issues so far. I have switched from my SODP based lineage builds to yours, because of the defunct camera in SODP.
Never occurred to me to use the stock binaries.. Great stuff, thanks!
Hi, I have been having weird touch screen issues with my stock unrooted zx2 compact. ( sometimes the screen just goes unresponsive no touch inputs work, I have to lock then unlock the screen for it to work again).
I'm wondering if anyone has noticed this on this Rom if it's a hardware issue or if its software then I can try a custom Rom.
teostar said:
Hi, I have been having weird touch screen issues with my stock unrooted zx2 compact. ( sometimes the screen just goes unresponsive no touch inputs work, I have to lock then unlock the screen for it to work again).
I'm wondering if anyone has noticed this on this Rom if it's a hardware issue or if its software then I can try a custom Rom.
Click to expand...
Click to collapse
Not yet, so far.
What I encountered:
- switching to loudspeaker during a call does not work - all is just muted
- Notification LED can be turned on somehow, but does not really work and can not be adjusted
- shutter button does not start the camera
Ungewiss said:
Not yet, so far.
What I encountered:
- switching to loudspeaker during a call does not work - all is just muted
- Notification LED can be turned on somehow, but does not really work and can not be adjusted
- shutter button does not start the camera
Click to expand...
Click to collapse
Call via loudspeaker is normal, you need to use the mic on the top of the phone. It's not a bug, it is designed by Sony.
Notification LED works fine for me. You can describe your issue more detailly.
Camera key is a bug of LineageOS, we had no idea about it now.