[ROM][UNOFFICIAL][N][UsU]CypherOS 4.2 [H812]

[ROM][UNOFFICIAL][N][UsU]CypherOS 4.2 [H812] - G4 Android Development

Features:
- Status bar Customization
- Changeable icons
- Quick pulldown
- Smart pulldown
- Notification count
- Clock position
- Seconds in clock
- Date design
- Quick Settings
- Brightness slider
- Brightness icon
- Tile tap customization
- System
- Screenshot partial and full
- Scrolling cache customization
- Power menu customization
- One-handed mode
- Specials
- UsU compatible build so no need for a baseband package to be flashed!
- Using latest TITAN kernel sources
Requirements
Your device need to be unlocked by UsU
Your bootloader stack should be on MM (see FAQ #20 for how to upgrade your bootloader stack)
Latest TWRP - PREVIEW build: click
Clean modem partition (so no UsU baseband flashed) - see Installation topic for details
Installation
If you have ever flashed the UsU baseband package: Clean flash the modem partition in TWRP:
- TWRP flashable MM modems (N will not work)
Read & follow (!) this very useful post by user @sdembiske (consider to show ur appreciation by clicking thx on that post) --> click
Full wipe like described here (click & go to FAQ "#zzz") is highly recommended. DO NOT REPORT ISSUES when you have skipped that step!
Flash AOSCP
Flash GApps (7.1 - ARM64) if you like to use google apps
Flash SuperSU / Magisk if you want root
Boot (will take long on first boot!)
Enjoy
Credits
LineageOS
AICP
PureNexus
AOKP
Dirty Unicorns
Paranoid Android
kessaras
sdembiske
steadfasterX
and more..
Sources
Kernel
device tree

reserved 1

reserved 2

So do I have to flash h812_aoscp_boot_build-50-nougat.img after installing this ROM? I was having overeating and battery drain so I did, hoping it would help because the guide said, "Flash the downloaded UsU kernel (has to be done again after a ROM flashing!): "
Maybe I'm confused. No matter what I am happy you are working on all the details. Do you ever sleep? cheers!
Edit: I think the overheating problem was being caused by an app called "Yappy". I uninstalled the app and everything is cool now.

cablematicman said:
So do I have to flash h812_aoscp_boot_build-50-nougat.img after installing this ROM? I was having overeating and battery drain so I did, hoping it would help because the guide said, "Flash the downloaded UsU kernel (has to be done again after a ROM flashing!): "
Maybe I'm confused. No matter what I am happy you are working on all the details. Do you ever sleep? cheers!
Click to expand...
Click to collapse
no need to flash a kernel. the guide says:
Installation
If you have ever flashed the UsU baseband package: Clean flash the modem partition in TWRP:
- TWRP flashable MM modems (N will not work)
Read & follow (!) this very useful post by user @sdembiske (consider to show ur appreciation by clicking thx on that post) --> click
Full wipe like described here (click & go to FAQ "#zzz") is highly recommended. DO NOT REPORT ISSUES when you have skipped that step!
Flash AOSCP
Flash GApps (7.1 - ARM64) if you like to use google apps
Flash SuperSU / Magisk if you want root
Boot (will take long on first boot!)
Enjoy
Click to expand...
Click to collapse
I cant read anything about flashing a boot image
tbh when you flashed h812_aoscp_boot_build-50-nougat.img after you flashed the latest version of this ROM you have downgraded the kernel to an earlier version..
.

@steadfasterX is it possible to get an aoscp 4 build for non USUed H815 with the Oreo back ported goodies?
Thx a lot for your efforts.
Gesendet von meinem LG-H815 mit Tapatalk

steadfasterX said:
no need to flash a kernel. the guide says:
I cant read anything about flashing a boot image
tbh when you flashed h812_aoscp_boot_build-50-nougat.img after you flashed the latest version of this ROM you have downgraded the kernel to an earlier version..
.
Click to expand...
Click to collapse
Good thing I made a backup just before that. Thanks for replying. I was reading the guide from the kernel thread, it sounded like even after flashing a rom that has USU available you still have to flash the USU kernel again after. I think I see now.... If I was using the h811 version of this rom, of the USU h812 version was not available, only then I would have to flash the H812 USU'd kernel on top.
Anyway thanks. Everything works well, just randomly overheats and kills the battery once a day. Seems unpredictable. I'm trying to figure out what initiates that problem.

popy2006 said:
@steadfasterX is it possible to get an aoscp 4 build for non USUed H815 with the Oreo back ported goodies?
Thx a lot for your efforts.
Gesendet von meinem LG-H815 mit Tapatalk
Click to expand...
Click to collapse
wrong thread i guess but no.. nothing planned. maybe I will run aoscp kernel builds but can't say when.
cablematicman said:
Good thing I made a backup just before that. Thanks for replying. I was reading the guide from the kernel thread, it sounded like even after flashing a rom that has USU available you still have to flash the USU kernel again after. I think I see now.... If I was using the h811 version of this rom, of the USU h812 version was not available, only then I would have to flash the H812 USU'd kernel on top.
Anyway thanks. Everything works well, just randomly overheats and kills the battery once a day. Seems unpredictable. I'm trying to figure out what initiates that problem.
Click to expand...
Click to collapse
yea or when a newer UsU kernel has been released as the ROM build would be another example
Have fun

overheat, shut down
This ROM seems to work so well. boots incredibly fast, runs cool, long battery life... then seemingly randomly overheats and shuts down the device. Today was good for hrs, then I received an SMS message and it immediately overheated and shut down. I plugged in, rebooted and have been texting ever since with no problems.
I just did my first LOG .... the text that seemed to initiate this occurred at 11:05am DST. but the log only goes back to 11:15, before that looks like Jan 1? I have never looked at a log before so idk. I'll see if I can capture a better one next time.
Here's a link to the LOG... maybe somebody will see something I don't see. Thanks!
https://mega.nz/#!CIYUmCoC!uZMQRti8sfRTYFP8V9bn6SjJ7h5XdWz-OyrAd5OL448
Edit: I think the overheating problem was being caused by an app called "Yappy". I uninstalled the app and everything is cool now.

Well I guess I'm gonna be "that guy" today.
Steadfaster, what do you think there is any chance that the video recording and playback problem we have on AOSCP for the H812 will ever be resolved?
I can't watch any video > 480p without stuttering, low framerate, and slow playback speeds. It affects YouTube, Twitch, Funimation, Snapchat, and every other app I have that can stream video. Even local video files are affected, and stutter in MX Player Pro.
I know Kessaras has no plans to look at it, but maybe you do? I will provide whatever details you ask for, if I can.
I miss HD playback and 60fps recording, and I miss being able to use camera apps that are fast and stable.
I don't mean any disrespect nor am I trying to tell you what to do. I guess I just want to know if I'm waiting for something that is never going to happen.
Thanks!

vsTerminus said:
Well I guess I'm gonna be "that guy" today.
Steadfaster, what do you think there is any chance that the video recording and playback problem we have on AOSCP for the H812 will ever be resolved?
I can't watch any video > 480p without stuttering, low framerate, and slow playback speeds. It affects YouTube, Twitch, Funimation, Snapchat, and every other app I have that can stream video. Even local video files are affected, and stutter in MX Player Pro.
I know Kessaras has no plans to look at it, but maybe you do? I will provide whatever details you ask for, if I can.
I miss HD playback and 60fps recording, and I miss being able to use camera apps that are fast and stable.
I don't mean any disrespect nor am I trying to tell you what to do. I guess I just want to know if I'm waiting for something that is never going to happen.
Thanks!
Click to expand...
Click to collapse
Well I hear about that the first time. So first I need to understand the issue.
Is this problem specific to the h812?
Video is not my area but if you wanna see a chance (no guarantee) open a new issue here:
https://github.com/Suicide-Squirrel/issues_oreo/issues
Provide a logcat and dmesg and add any other details you have there.
That's your best chance that I remember this when I may get bored one day
Sent from my LG-H815 using XDA Labs

Thanks!
I've opened two issues:
- Video Recording Issue #10
- HD Video Playback Issue #11
Several people brought this up in the UsU thread when it was first opened, but largely it was brushed under the rug because there are some third party camera apps on the Play Store that "work" well enough for most people. I stopped bringing it up because I figured that was the end of it.
Thank you

steadfasterX said:
wrong thread i guess but no.. nothing planned. maybe I will run aoscp kernel builds but can't say when.
yea or when a newer UsU kernel has been released as the ROM build would be another example
Have fun
Click to expand...
Click to collapse
So what is the disadvantage to flashing a ROM that doesn't have an USU kernel available. For example another h811 ROM not LOS or CypherOS? Is the USU kernel mandatory or is it a performance / stability improvement? I did try to find the answer in the USU unlock thread, I followed that thread all the way through to the end over several months. I ended up with the impression that I could flash ANY h811 ROM on my h812. I thought USU was the bootloader unlock and that the h812 was otherwise compatible with the h811 in other ways.

cablematicman said:
So what is the disadvantage to flashing a ROM that doesn't have an USU kernel available. For example another h811 ROM not LOS or CypherOS? Is the USU kernel mandatory or is it a performance / stability improvement? I did try to find the answer in the USU unlock thread, I followed that thread all the way through to the end over several months. I ended up with the impression that I could flash ANY h811 ROM on my h812. I thought USU was the bootloader unlock and that the h812 was otherwise compatible with the h811 in other ways.
Click to expand...
Click to collapse
Ofc you can run any ROM shown as compatible in SALT.
But that requires to flash a hack. The baseband package. That will replace the baseband files with those compatible with UsU.
Flashing an UsU kernel will work without that hack.
Sent from my LG-H815 using XDA Labs

steadfasterX said:
Ofc you can run any ROM shown as compatible in SALT.
But that requires to flash a hack. The baseband package. That will replace the baseband files with those compatible with UsU.
Flashing an UsU kernel will work without that hack.
Click to expand...
Click to collapse
And from Github...
steadfasterX said:
Ok just to let you know: I will focus only on LOS. Kessaras on aoscp
and we all do only oreo. There will be not further development for N.
Click to expand...
Click to collapse
So, would it be too much to ask for you to build an Oreo H812-UsU kernel for either of those ROMs? Or a rom specifically for the H812-UsU?

vsTerminus said:
And from Github...
So, would it be too much to ask for you to build an Oreo H812-UsU kernel for either of those ROMs? Or a rom specifically for the H812-UsU?
Click to expand...
Click to collapse
FYI: I installed the AOSCP (OREO) for h811 on my h812 and then flashed the USU baseband immediately after and everything works perfectly. I believe this is the same result as a specific USU version of the ROM? It seems to be working great!

vsTerminus said:
And from Github...
So, would it be too much to ask for you to build an Oreo H812-UsU kernel for either of those ROMs? Or a rom specifically for the H812-UsU?
Click to expand...
Click to collapse
It's all in the works. when kernels have been build you will find them here
https://forum.xda-developers.com/g4/development/kernel-usu-patched-kernel-versions-t3763679
And for the ROM I will open a new thread. when it's ready.
cablematicman said:
FYI: I installed the AOSCP (OREO) for h811 on my h812 and then flashed the USU baseband immediately after and everything works perfectly. I believe this is the same result as a specific USU version of the ROM? It seems to be working great!
Click to expand...
Click to collapse
Of course it works great that's why I've made that baseband package. it's still a hack though :angel:
Sent from my LG-H815 using XDA Labs

cablematicman said:
FYI: I installed the AOSCP (OREO) for h811 on my h812 and then flashed the USU baseband immediately after and everything works perfectly. I believe this is the same result as a specific USU version of the ROM? It seems to be working great!
Click to expand...
Click to collapse
Which version? You mean video playback/recording is working too?

I was just referring to the request for "Oreo H812-UsU kernel for either of those ROMs", it's not required. You just glad the usu baseband like steadfasterx said. It works the same. It will be no better, just the same, which in my opinion is great (not perfect). I don't record it playback video very often. I change ROMS frequently anyway. The automatic network provided time is off by 1h30m I've never seen that happen before.

Oreo
cablematicman said:
I was just referring to the request for "Oreo H812-UsU kernel for either of those ROMs", it's not required. You just glad the usu baseband like steadfasterx said. It works the same. It will be no better, just the same, which in my opinion is great (not perfect). I don't record it playback video very often. I change ROMS frequently anyway. The automatic network provided time is off by 1h30m I've never seen that happen before.
Click to expand...
Click to collapse
Are you still using this ROM? Does it have more options than aoscp N? Is it responsive? I find aospc N to be a hit laggy.
Also what color is the notification dropdown? Does it have a volume slider?
Edit: thinking of using this on my h812 as well....

Related

ABANDONED [TWRP][20151015] dr4stic's TWRP 2.8.7.0 w/ stuff (Most Variants)

I BUILD ABANDON A TWRP!
THIS PROJECT IS ABANDONED (2015-12-06)
Blastagator's 2.8.7.3 release fixes the problem that started my quest: the sepolicy squashing that damaged the gapps permissions on CM-12 OS updates. Given that I had many more issues that came from my choice of CM-12.1 as a base (instead of whatever TWRP wanted) and that I lacked the time, inclination or expertise to pursue the issues, I have chosen to abandon this project. If it worked for you and you didn't need the extra features that were buggy, then by all means enjoy. However this project is no longer supported.
What is it?
It's TWRP! It's for a number of the G2's! Which ones? The ones supported by whatever the current CyanogenMod is. GSM: D800/1/2/3, CDMA: LS980, VS980. This is because, despite the TWRP documentation, I use CyanogenMod as a base, and if CyanogenMod doesn't currently support the given model, then I won't be supporting it with my TWRP. This TWRP is built with hints from (and thanks for) @blastagator's TWRP.
README.FIRST / DISCLAIMER
THERE BE DRAGONS HERE!!! USE THIS AT YOUR OWN RISK!!!
This is your one AND ONLY warning. I am not responsible for whatever happens to your phone. This software has the feature set to let you backup all of your partitions, but it also has the power TO BOTCH each and every partition on your device. This includes your EFS and other sensitive things. It is entirely possible that you may end up bricking your device. I really hope that doesn't happen, but I am also not responsible if it does. Please, behave responsibly and know that if you've taken the time to get this installed, well... your warranty is void.
Features
Flashes Gapps properly so that it doesn't crash on reboot
Thermal Support
Material Theme
{
"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"
}
Known Issues / Red Flags
I've only really tested on the D800 because that's what I have access to. However I've reports that it works fine on the other variants.
Reports that it doesn't work with blastagator's hybrid LP bootstack. (User says reboots into bootloader)
F2FS Support currently a bit borked. (User's say formatting doesn't work and causes ROM to bootloop, or is very slow and doesn't work.)
Users using AROMA will have issues installing things. Something about the installation process causes the recovery to reboot.
Cherry Picks / Links
Device Repo: https://github.com/dr4stic/twrp_device_lge_g2-common
CyanogenMod / 89474: Make recovery permissive (manually applied) - (20151003 - current)
TWRP / 12728: [WIP] gui: stock theme rework - (20151015 - current)
CyanogenMod / 110402: f2fs: Import latest F2FS + AIO Optimization - (upcoming)
TWRP / 14355: Fix broken fsflags support (upcoming)
TWRP / 14462: Support resuming block based OTAs (upcoming)
Releases / Changelog:
2.8.7.0 - 20151015
Added directives to tell twrp where our media REALLY is (blastagator suggested bad things happen if I don't)
Cherry picked a more material like theme because Rashed97 whined about ugliness
D800: twrp-2.8.7.0-20151015-d800.zip - 11.6 MB (MD5 Sum: 7e46ea96fed69a5cde9da73e26d6742e)
D801: twrp-2.8.7.0-20151015-d801.zip - 11.4 MB (MD5 Sum: 7a71cda865b0f32c1403938eb76eeb5e)
D802: twrp-2.8.7.0-20151015-d802.zip - 11.4 MB (MD5 Sum: 52143681915a53b910040fb6501dd324)
D803: twrp-2.8.7.0-20151015-d803.zip - 11.4 MB (MD5 Sum: e8ee2f05ca06be1924a45e49da29e439)
LS980: twrp-2.8.7.0-20151015-ls980.zip - 11.4 MB (MD5 Sum: f76642bd7f5bb2b0eb8bb2a20e4adfed)
VS980: twrp-2.8.7.0-20151015-vs980.zip - 11.4 MB (MD5 Sum: bdfdb1e2132ab08a8f7e42c06e3699a4)
2.8.7.0 - 20151003
Initial release
Download 2.8.7.0 - 20151003: D800 | D801 | D802 | D803 | LS980 | VS980
Thanks To:
The TWRP Development Team
@blastagator
@Rashed97

dr4stic said:
Hello folks,
I BUILD A TWRP!
Click to expand...
Click to collapse
When I see how many projects are done for the G2, I really think I should give a try... Anyway, !gg mate, I'll try this recovery .

What did you change? Or did you just build my repos and post a new thread?

blastagator said:
What did you change? Or did you just build my repos and post a new thread?
Click to expand...
Click to collapse
It's not just a download and rebuild, if that's what you're asking (and, I'm not trying to upset the apple cart or anything).
The build started as the end of my trying to figure out what the problem was with CM and Gapps that required it to be re-flashed each time a rom update was flashed. I experimented with running commands by hand, dissecting upgrade scripts, found that contexts were either not being set or being lost, etc... etc... And at some point the only answer I could come up with was that it was the recovery. I tried the CM recovery, which is worse than the black death, and it worked fine. Since your TWRP is the latest, I didn't understand why it wasn't keeping contexts. At that point I decided to build my own TWRP, so I started from the only official docs I could find. That's what my base started as.... the cm-10.1 repos they have on their github for g2.
After realizing that simply wasn't going to work, I started re-working and basing off of CM. I didn't necessarily want to look at your work because in my mind yours was done right and based on latest CM. I eventually looked at it for some hints (hence my attribution). It wasn't until I realized your device repos looked odd to me that I realized what happened. Your device repos were based from back when the G2 stuff was barely starting out on CM-12.1... it was still very 12.0 (which, in itself was a ball of vomit for the g2). It lacked the selinux stuff (which is why it was losing contexts) and you also used an alternate kernel (unsurprisingly, cuz the CM stuff was still in a state of vomit). There are no judgements. At the time you built the recovery, it's what was available and working. I don't think the G2 got selinux turned up until some time in very early August.
So, I decided to fork copies of the latest CM device repos which all work now, base everything off the current CM kernel (I figured this was safest for compatibility). I actually looked through the TWRP sources to hunt for actual BoardCommonConfig.mk settings (the docs seemed VERY lacking) and an understanding of how they all interacted. I looked at your repo for hints, but I didn't just copy it. As a result I use more current settings (a few of yours are actually deprecated). I'm assuming because of the age of your repo that your builds were lokified and you bumped them after the fact. Mine have all the changes that came with 12.1 including a lack of loki and being bumped as part of the build process. The rc files are all stock CM. Many things simply don't exist from your version because the recovery environment seems REALLY restricted once it's built. The few things that I did borrow, I moved into more appropriate locations and file names to be more respectful of the build process.
So, to answer your question: it started as a rather long and annoying bug hunt, then turned into a long but fruitful learning experience, and once I had a version that worked, I posted it for the few folks on the CM forum for whom this is a real pain in the ass.
It certainly wasn't a quick process and a grab for glory.... hell, once I realized that the CM build process needed to build a full ROM to get all the appropriate files into the recovery image, each one of those device builds took over an hour to build.
I started a new thread because I wanted to have a specific place where I could respond to issues if they arose, or at least tell people that I didn't care about their piddly little problems. I wanted a little more control over the support process, to be able to modify the OP with pertinent issues and links as they came up. It's something I wish had happened with CM-12.1 "official" threads.
There are things that I'm not sure of, and I try to indicate as much in the OP. The thread regulars indicated the history of needing thermal support, but I'm not sure if I got it right. Neither your recovery nor mine actually got the thermal libraries or binary included in the file system, however the process seems to be running. Nor are the configuration files included on the file system. f2fs support seems to simply be an additional package, and since the official G2 repos theoretically have f2fs support, I added that and moved along. The tools seem to be included on the file system.
I'm in the process of posting my changes to github, probably tomorrow since I'm still sorta learning to do that and I have things to do tonight. You can see them then. If you post an updated version of your recovery with my modifications, I'll happily close this thread.

@dr4stic
There's no "thermal support" official twrp uses their kernel, which blasts all cores on max freq, generating needless amounts of heat.
From the sounds of it, you're using the stock cm12.1 kernel, so there should be no heat issues. If the CPU gets hot, it will throttle as it is supposed to.
So that's what his twrp means when it says thermal support. It uses our phones kernel so it operates like it would on a ROM.

Lawlrus said:
There's no "thermal support" official twrp uses their kernel, which blasts all cores on max freq, generating needless amounts of heat.
From the sounds of it, you're using the stock cm12.1 kernel, so there should be no heat issues. If the CPU gets hot, it will throttle as it is supposed to.
So that's what his twrp means when it says thermal support. It uses our phones kernel so it operates like it would on a ROM.
Click to expand...
Click to collapse
@Lawlrus, thank you for the explanation! After I investigated I assumed that's what was going on, but I didn't want to assume and then tell people something I wasn't sure about. I noticed that mine gets a slight toastier than blastagator's, but not a significant difference. I attributed it more to kernel tuning with the finalized CM kernel than anything else.

dr4stic said:
It's not just a download and rebuild, if that's what you're asking (and, I'm not trying to upset the apple cart or anything).
I'm in the process of posting my changes to github, probably tomorrow since I'm still sorta learning to do that and I have things to do tonight. You can see them then. If you post an updated version of your recovery with my modifications, I'll happily close this thread.
Click to expand...
Click to collapse
Nah man, I'm not upset. I made it so easy (or tried to make it easy, at least) to build my source so other people could muck with it. My curiosity stems from wanting to add any improvements in to my build.
I briefly messed with cm12 device trees but didn't have luck the first go around so I didn't bother going down that road. Will definitely keep an eye on this thread.
My builds are built with the Omni 4.4 Source, and these changes:
https://github.com/blastagator/cm_device_lge_g2-common/blob/cm-11.0/blastagator_g2-common.xml
The device trees are actually based on cm-11, not 12.
As for SELinux, issues probably stem from this: https://github.com/blastagator/aicp...mmit/85953d0cf8dd3d33406ad8a745ced99e5039f766. When I committed it I thought it set SELinux to permissive. However, it actually completely disables SELinux, so the kernel won't automatically preserve contexts, etc. This seems like the most likely culprit for your issue. I will run a test build and revert that commit, if you'd like it to test.
As to cm-12, in general: I'm certainly interested in moving up, I just never really had a reason to spend any time on it.

blastagator said:
Nah man, I'm not upset. I made it so easy (or tried to make it easy, at least) to build my source so other people could muck with it. My curiosity stems from wanting to add any improvements in to my build.
I briefly messed with cm12 device trees but didn't have luck the first go around so I didn't bother going down that road. Will definitely keep an eye on this thread.
Click to expand...
Click to collapse
PM me with your email. I'll shoot you the diff I made. The only reason I haven't posted it to github is that I wanna show the changes piecemeal instead of in one big diff. If you can call it big... it's really just 4 changes
Honestly, I'm not sure why they recommend against building on CM. Despite their documentation being utter crap, the build itself was easy once I figured out where the pieces were all supposed to go.
And yeah... CM 12.1 at the time you built things was an absolute mess. But the stuff in the official repo's is really rock solid now. Well, maybe not tonight, it seems there were a bunch of g2 changes and one in particular is gonna break the build for tonight

Tried the d800. Device went into fastboot mode, doesn't boot into recovery. Back to blastagators.

dr4stic said:
PM me with your email. I'll shoot you the diff I made. The only reason I haven't posted it to github is that I wanna show the changes piecemeal instead of in one big diff. If you can call it big... it's really just 4 changes
Honestly, I'm not sure why they recommend against building on CM. Despite their documentation being utter crap, the build itself was easy once I figured out where the pieces were all supposed to go.
And yeah... CM 12.1 at the time you built things was an absolute mess. But the stuff in the official repo's is really rock solid now. Well, maybe not tonight, it seems there were a bunch of g2 changes and one in particular is gonna break the build for tonight
Click to expand...
Click to collapse
Github makes tracking all of this better. My suggestion is that you first create a "fork" of blastgator's repo on Github, and then "clone" the repo on your local machine. Apply your diffs to it. Commit and Push (to your fork). Then issue a pull request to Blastgator.

sandys1 said:
Github makes tracking all of this better. My suggestion is that you first create a "fork" of blastgator's repo on Github, and then "clone" the repo on your local machine. Apply your diffs to it. Commit and Push (to your fork). Then issue a pull request to Blastgator.
Click to expand...
Click to collapse
Thanks for your suggestion. I'm already talking to blastagator. The problem is that his current build isn't actually based on CM-12, we are working from different sources.

jacoghi said:
Tried the d800. Device went into fastboot mode, doesn't boot into recovery. Back to blastagators.
Click to expand...
Click to collapse
I have a few d800's, it's the device I use. Which bootloader are you on? JB? KK? LP?

I have the hybrid LP bootstack, from blastagator, which includes the KK aboot. Blastagator's twrp works without hitches

jacoghi said:
I have the hybrid LP bootstack, from blastagator, which includes the KK aboot. Blastagator's twrp works without hitches
Click to expand...
Click to collapse
Just a few things...
Are you talking about the "Bump LP" bootstack on this page?
Are you sure you downloaded the d800 recovery?
If you did, could you verify the md5 of the file you downloaded against the one I list in the OP?
Thanks.

dr4stic said:
Just a few things...
Are you talking about the "Bump LP" bootstack on this page?
Are you sure you downloaded the d800 recovery?
If you did, could you verify the md5 of the file you downloaded against the one I list in the OP?
Thanks.
Click to expand...
Click to collapse
Yep to all of them. I flashed your image using blastagators twrp and got the fastboot mode. Let me know should you need any extra info. Thanks

jacoghi said:
Yep to all of them. I flashed your image using blastagators twrp and got the fastboot mode. Let me know should you need any extra info. Thanks
Click to expand...
Click to collapse
Do you use cm-12.1? Which ROM do you use (and version) if you don't mind me asking.

dr4stic said:
Do you use cm-12.1? Which ROM do you use (and version) if you don't mind me asking.
Click to expand...
Click to collapse
I'm using cloudy 3.3 right now with xceeds kernel. After I got the fastboot mode, I could boot my system normally, if that helps. Rebooted again, got fastboot once more. Then booted system up again and installed autorec, which corrected the problem.

Well, messed around with this for a bit, decided to format /data to f2fs.
Dont do that. Not on this recovery. Formatting to f2fs takes forever (probably hangs entirely as i waited at least 10 minutes before rebooting)
Then noticed my /data wouldnt mount on reboot, causing my rom to bootloop and, even worse, the recovery to bootloop.
Due to a (probably unrelated) bug the lg flash tool didnt work either, so had to open up the device to boot in qhsusb mode and manually format /data to ext4.
This is the closest I've been to a complete brick on this phone since I got it.
Please update the OP to warn people about f2fs.
Nice work on the kernel update, but I personally am going to avoid this recovery until the above issue is solved

My problem is that it would not reboot nor power off while in this recovery. But it works by pressing power button.

It is ok now by removing the theme file ui.zip.

[ROM][5.1.1][SlimRoms] SlimLP JFLTETMO [UNOFFICIAL]

{
"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"
}
Being a SlimRoms fan, I looked everywhere for up to date versions of Slim5 or Slim6, and after I couldn't find any newer Slim ROM for my SGH-M919, I decided to compile one. By God's grace, it worked! I hope that other's can enjoy this ROM too, so I put it here to share it with you!
**** This is an UNOFFICIAL ROM. Install at your own risk! ****
Downloads:
Rom Download link:
http://www.mediafire.com/download/3irz4n9kzrawux1/slimlp-jf-20160818.zip
Gapps link:
http://forum.xda-developers.com/slimroms/general/gapps-official-slim-gapps-trds-slimkat-t2792842
I have personally tried the Slim_zero_gapps.BETA.5.1.build.0.x-20160429.zip file, which worked flawlessly. Be sure to slap their thanks button for the Gapps!
Old Rom without hand updated Critical Security patches download link:
http://www.mediafire.com/download/4liij279jjx7pd4/Slim-jf-5.1.1-UNOFFICIAL-20160721-aklu.zip
This Rom has been very stable for me. Be sure to follow these installation steps very carefully, as they may be different then what you are used to.
Installation instructions:
-Download ROM and gapps, and put them on your phone or external storage.
-Reboot into recovery mode - TWRP (I personnally am using 2.8.7.0).
-Backup what you had. (Just to be safe.)
-Wipe.
-Install Rom.
-Wipe Cache and Davlik. <--VERY IMPORTANT!
-Install Gapps. - Optional.
-Wipe Cache and Davlik again! <--VERY IMPORTANT! Or WiFi may not work first boot. Will work thereafter.
-Reboot to system and enjoy!
Code:
What works:
-So far everything that I have tried works, such as
- Phone calls/receiving
- Data 2g/3g/LTE
- Bluetooth
- WiFi
- MTP
- GPS
etc....
What doesn't:
- I have not found any big errors, fault crashes, or problems yet. Please let me know if you find an issue!
- I have posted a few notes in Post #2 below.
Change log:
Code:
20160818
-Added May 2016 Security updates (Critical updates only) by hand. See posts for more information. May not be perfectly secure.
-Edited updater-script so zip may be flashed on any JFLTE phone. Built for JFLTETMO though. Use with caution!
20160815
-Added April 2016 Security updates (Critical updates only) by hand. See posts for more information. May not be perfectly secure.
-Edited updater-script so zip may be flashed on any JFLTE phone. Built for JFLTETMO though. Use with caution!
20160805
-Added March 2016 Security updates (Critical updates only) by hand. See posts for more information. May not be perfectly secure.
-Edited updater-script so zip may be flashed on any JFLTE phone. Built for JFLTETMO though. Use with caution!
20160721
-Added GPU overclock kernel - control with Kernel Adiutor app.
-Edited updater-script so zip may be flashed on any JFLTE phone. Built for JFLTETMO though. Use with caution!
20160711
-Removed NFCPU in favor of Kernel Aduitor
-Synced with SlimLP source - Note: They do not appear to be updating thier security patches, since Feb, 2016.
-Edited updater-script so zip may be flashed on any JFLTE phone. Built for JFLTETMO though. Use with caution!
20160707
-Added Kernel Aduitor app to build.
-Added Fast Charge to kernel.
-Edited updater-script so zip may be flashed on any JFLTE phone. Built for JFLTETMO though. Use with caution!
20160623:
-Added the Lionheart and SmartMax governors to the kernel.
-Added "No Frills CPU" app to build.
-Edited updater-script so zip may be flashed on any JFLTE phone. Built for JFLTETMO though. Use with caution!
20160618:
-Synced with SlimLP source.
-Edited updater-script so zip may be flashed on any JFLTE phone. Built for JFLTETMO though. Use with caution!
20160512:
-First release.
Disclaimer: SlimRoms is not responsible for any damages to your device.
In the Rom, I left the original SlimLP boot animation, however, I have made a couple of simpler custom boot animations for SlimRoms, which you can find here if you would like to use one of them instead:
http://forum.xda-developers.com/slimroms/general/homemade-slimroms-boot-animation-t3377271
This SlimLP ROM was built for the JFLTETMO, the T-Mobile Samsung Galaxy S 4. However, The updater script has been modified, and it would allow itself to be installed on any of the Galaxy S 4 devices. I have not tried this on any other device, but you are welcome to try it AT YOUR OWN RISK.
A huge thanks to the SlimRoms team!
SlimRoms XDA Forum: http://forum.xda-developers.com/slimroms
Source Code: http://github.com/SlimRoms/
Official websites: http://www.slimroms.net/ or http://slimroms.org/
ROM OS Version: 5.1.1 Lollipop
ROM Kernel: Linux 3.4.112
Based On: AOSP
Device Tree: https://github.com/alaskalinuxuser/
Features the AKLU kernel:
http://forum.xda-developers.com/gal.../kernel-marshmallow-lollipop-kernels-t3411543
Created 2016-05-12
Last Updated 2016-12-20
All of my work is completely available for any who wish to use or modify it. I didn't make SlimRoms, the device trees, or vendor blobs. I simply used and edited existing material. A huge thanks should go to those who actually created this stuff.

Notes: a place for notes about the ROM.
Background image
The futuristic and really cool background images used in this rom were provided by The Quiet Learner, you can visit his website for more information and more really great pictures. https://qlfiles.net/
Security Updates
As of February 2016, the SlimRoms team has stopped updating SlimLP with security updates. I have decided to continue updating SlimLP, but only with Critical security updates from the Android Security Bulletins: https://source.android.com/security/bulletin/index.html. Please note that I am only updating Critical updates, not High, Moderate, or Low security threats. I am doing this by hand and may miss one update. Please be advised that this rom is not as secure as Marshmallow roms that are kept up to date. I am doing my best, but I may also be a little behind the bulletins. Please be patient. I decided Critical updates were better than none, but I can only do Critical updates, as this sometimes takes editing over 800 files per monthly bulletin.
Camera
Every now and then, when I use the built in camera app, it will take 2 or 3 pictures, and then the camera picture button will be grayed out, and you must exit and re-open the camera app to take more pictures. This does not happen with Open Camera app, which is available online or at the play store. Overall the camera seems to be working great, I'm not sure why the built in app sometimes has this issue.
GPS
GPS seems to take an unusually long time to get a fix, even outdoors in the open sky. It does work and stay locked for me, but I thought I would share, in the event others noticed this as well. @redx64 has pointed out that you can speed up the GPS by downloading GPS Status and toolbox and use fastergps to update your GPS config file to your region.
Gapps or no Gapps?
For those who do not wish to install, or who are prohibited from installing Gapps, there are some great alternatives. Aptoide works really well in general, and I did take some time to test it with this ROM. As for my apps, Aptoide had all but 2 of the apps I use available, and many alternative apps as well. If you wish to forgo Gapps, but still want a login, app searching, automatic updating (or not, depending on your settings), user friendly tool, then you might want to give Aptoide a try.
The best way to use layers successfully with this ROM:
After doing some testing of the layers on SlimLP, I learned a few helpful tips.
1. The PlayStore Layer Manager App is too "new" for SlimLP. The 4.+ version available from the PlayStore will not let you undo the layers, and hense you cannot go back to stock. Use this older version (3.5) instead, which allows you to install, apply, delete, and undo changes:
https://www.mediafire.com/download/q94w8j7xuyhpudz
2. The PlayStore layers themes are often incompatible with version 3.5 of the layer manager app. Don't worry though, there are tons to choose from here on XDA:
http://forum.xda-developers.com/showthread.php?t=3011075
This Mega thread has tons of them to choose from. If you want these, only download the ones that are zip files for best compatibility. The zips should show up in your download folder, which you can move anywhere and use from the app.
The app has an option to "delete" layers, which actually means "undo" that layer, not actually delete the zip file.
If you still wish to use the PlayStore app and themes, keep in mind that you cannot "undo" your choice of theme. And sometimes themes have an undesired side effect. Two themes from the PlayStore that I have successfully used were BluSky theme, and Elixium theme, both of which worked well, with the exception of the systems -> battery settings chart looked funny.
If you use the themes, I highly recommend doing a TWRP backup first, to make sure that you can always go back!
Governors:
If you want to save battery life, I recommend that you use the "No-frills CPU Control" app and set your Governor to something like Powersave or SmartMax, and your I/O scheduler to Noop. This may affect performance slightly, but will save on some battery power.
If you want to increase performance, I recommend that you use the "No-frills CPU Control" app and set your Governor to Lionheart, Ondemand, or Performance, and your I/O scheduler to CFQ. This will boost performance slightly, but will have a negative impact on battery power.
Powersaving <----------> Performance:
Powersave, SmartMax, Conservative, Interactive, Lionheart, Ondemand, Performance.
Fast Charge:
To use Fast Charge, you must enable it in the Kernel Adiutor app. If you want to set custom settings, you will need to get another app from the Play Store, such as Device Manager or other apps that allow you to control the fast charge settings. Note that some fast charge settings apps do not change the appropriate values to function. The lockscreen may still say "slow charge" as the rom itself does not natively support fast charge, even though the kernel does.
Also, if you have any questions or comments (even if you didn't like it) about this ROM you are welcome to post them in this thread. SlimRoms is not for everyone, since it is rather "slim". No sense starting a Q&A thread for this ROM when we already have a thread here...

Thanks for your work on this. Really miss having a SlimRom, used to run on my SG4. With all the BT issues plaguing MM ROMS currently, I may give this a whirl.

Thanks for this. . Keeping it in my back pocket
Sent from my SGH-M919V using XDA-Developers mobile app

christoophat said:
Thanks for your work on this. Really miss having a SlimRom, used to run on my SG4. With all the BT issues plaguing MM ROMS currently, I may give this a whirl.
Click to expand...
Click to collapse
Thanks. I did test the Bluetooth, but I do not use it much. It would be good to know if this Bluetooth is rock solid when it comes to headphones, speakers, and such.
Sent from my SGH-M919 using XDA-Developers mobile app

kazzxtrismus said:
Thanks for this. . Keeping it in my back pocket
Sent from my SGH-M919V using XDA-Developers mobile app
Click to expand...
Click to collapse
Thanks! Does this ROM work on the SGH-M919V as well?
Sent from my SGH-M919 using XDA-Developers mobile app

AlaskaLinuxUser said:
Thanks. I did test the Bluetooth, but I do not use it much. It would be good to know if this Bluetooth is rock solid when it comes to headphones, speakers, and such.
Sent from my SGH-M919 using XDA-Developers mobile app
Click to expand...
Click to collapse
I should think BT is fine, as devs had it working pretty much 100% for the LP ROMS.
MM seems to have changed something that hasn't quite been solved yet.:silly:

AlaskaLinuxUser said:
Thanks! Does this ROM work on the SGH-M919V as well?
Sent from my SGH-M919 using XDA-Developers mobile app
Click to expand...
Click to collapse
It should be fine.. Wind apn might need added tho
Sent from my SGH-M919V using XDA-Developers mobile app

Any chance of you doing. Dirty unicorn build 6.0 mm

immorality said:
Any chance of you doing. Dirty unicorn build 6.0 mm
Click to expand...
Click to collapse
If I am not mistaken, that has already been done:
http://forum.xda-developers.com/showthread.php?t=3292806
Please let me know if I am wrong, but can't we use this version also?
Be sure to slap their thanks button if you enjoy their ROM!
Edited: I now see that it does not work on the M919. I am currently pursuing SlimRoms 6.0, but perhaps I can look into it. No promises, though.
Sent from my SGH-M919 using XDA-Developers mobile app

AlaskaLinuxUser said:
If I am not mistaken, that has already been done:
http://forum.xda-developers.com/showthread.php?t=3292806
Please let me know if I am wrong, but can't we use this version also?
Be sure to slap their thanks button if you enjoy their ROM!
Edited: I now see that it does not work on the M919. I am currently pursuing SlimRoms 6.0, but perhaps I can look into it. No promises, though.
Click to expand...
Click to collapse
Its a rough build with little updates
As you know you cannot flash jfltexx versions of the ROM
If you want to you need to flash a xx recovery
Could you add super user to settings
(I feel dirty unicorn covered the most ground with its settings menu
Feels like slim always misses something so I finished testing an went back to a previous ROM

AlaskaLinuxUser said:
If I am not mistaken, that has already been done:
http://forum.xda-developers.com/showthread.php?t=3292806
Please let me know if I am wrong, but can't we use this version also?
Be sure to slap their thanks button if you enjoy their ROM!
Edited: I now see that it does not work on the M919. I am currently pursuing SlimRoms 6.0, but perhaps I can look into it. No promises, though.
Sent from my SGH-M919 using XDA-Developers mobile app
Click to expand...
Click to collapse
Actually, I'd welcome an SLim MM ROM more!
Does this ROM currently use CM Theme engine?

christoophat said:
Actually, I'd welcome an SLim MM ROM more!
Does this ROM currently use CM Theme engine?
Click to expand...
Click to collapse
No, SlimLP does not use the CM theme engine.
-AlaskaLinuxUser
https://thealaskalinuxuser.wordpress.com

immorality said:
Feels like slim always misses something so I finished testing an went back to a previous ROM
Click to expand...
Click to collapse
Slim is certainly slim. I do like some of the built in features, like the ability to remap hardware buttons in the settings menu, the built in screenshot tool, slim pie, and the slim recent apps bar when you hold down the home key. So I think that Slim has lots of "subtle" features that most folks are unaware of.
No worries though, thanks for trying the ROM out.
Edit: I finally figured out how to take a screenshot while the slim pie controls were open.
-AlaskaLinuxUser
https://thealaskalinuxuser.wordpress.com

Hey guys, I'm new to the ROM scene, this is my first go. Well, second time trying to flash a rom. Anyway it flashed and booted fine but on first boot its having trouble with all the gapps, I assume I used the wrong version of the gapps zip file. Should I just try different versions one at a time? Could that brick it?
Thanks

karovamilkbar said:
Hey guys, I'm new to the ROM scene, this is my first go. Well, second time trying to flash a rom. Anyway it flashed and booted fine but on first boot its having trouble with all the gapps, I assume I used the wrong version of the gapps zip file. Should I just try different versions one at a time? Could that brick it?
Thanks
Click to expand...
Click to collapse
First and foremost, thanks for giving SlimLP a try!
Second, as for the Gapps, trying different ones wont brick it, but you will need to do a fresh wipe, install the rom and then gapps, as per the first post instuctions. I recommend that you try this one:
https://www.androidfilehost.com/?fid=4996500813288308963
I hope that gets you going, good luck and have fun with SlimLP!
-AlaskaLinuxUser
https://thealaskalinuxuser.wordpress.com

karovamilkbar said:
Hey guys, I'm new to the ROM scene, this is my first go. Well, second time trying to flash a rom. Anyway it flashed and booted fine but on first boot its having trouble with all the gapps, I assume I used the wrong version of the gapps zip file. Should I just try different versions one at a time? Could that brick it?
Thanks
Click to expand...
Click to collapse
Open gapps is my go to,
Then it's dynamic gapps
But here we have 100s of gapps (well like 5-10 to choose from)
Rome are tricky learn everything you can before the flash (read some issue reports by users and don't forget to post yours (log is best)
I've been around since sidekick 4g /.o I miss the keyboard never had to look at it to type

Loving this rom. Most stable and fast compared to the Dirty unicorn and Pacrom I tried before. If anyone is having problem with GPS , i reccomend the following. Download GPS Status and toolbox and use fastergps to update your gps config file to your region.

Here is a screenshot of the benchmark with this ROM using the linaro 4.7 tool chain. I was hoping to try a few other tool chains to see if it makes a difference. So far the kernel build fails with the linaro 4.9 tool chain.
-AlaskaLinuxUser
https://thealaskalinuxuser.wordpress.com

By the way, you can set the display to 320 DPI to get the most out of your screen, too. It is in the settings menu as LCD density.
Sent from my SGH-M919 using XDA-Developers mobile app

[ROM][Z3/Z3DUAL][deprecated] LineageOS 14.1 [CLOSED]

{
"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"
}
Click here to get to the new post where we'll keep updating this rom
What it is
It is an LineageOS 14.1 alpha build from official LineageOS sources devices trees and fresh caf 3.4 kernel port. This is not related anymore (2017-03-22) to the Sony Open Device Project (sonyxperiadev). They work on a different way and we are helping each others as often as possible.
This rom is worked to be as stable as possible to be used as a daily driver. There are no changes into LineageOS sources, manifest to build is attached in this post. The idea is to share this built with the community to improve this rom. If it is good enough, maybe, someday, get official again for our D6603. Thanks a lot to @tomascus who made this possible. (his donate link)
Disclaimer
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 me for messing up your device, I will laugh at you.
*
*/
Who can use it
It is only for Z3 and UNLOCKED UPGRADED BOOTLOADERS
How to install
%= Only needed at first flash
% Update ROM to .291 with emma (or Flashtools)
% When install is done go into fastboot mode (plug usb + vol down key = blue led)
% Flash this TWRP (version 3.1.x) | If you are a Z3 Dual user, flash zip below before installing Z3 Dual version. / If you already are in .291 and have a working TWRP (modded rom/kernel/adv kernel) you can use the flashable zips below instead.
Shutdown the device
Unplug the usb cable
Maintain volume down & power until you see twrp splash screen
% Wipe system, cache and data
Install rom zip (+ % gapps if you need it)
Reboot
Rolling back to stock
Flash stock rom with emma or flashtool
If you flash with flashtool remember to check wipe apps_log and userdata partitions to get a clean install
What gapps to flash?
Use f-droid
You can flash any gapps you want, our partition is 2GB and rom is 700MB:
Code:
z3:/ # df -h
Filesystem Size Used Avail Use% Mounted on
/dev/block/mmcblk0p23 2.4G 680M 1.7G 28% /system
Just take 'arm' and not 'arm64'
Gapps need to be flashed at first rom flash!
NEW RELEASE
2017-06-13:
Xperia Z3
Download
md5: 2d4ca5f88de0303575f2ab9c249d521f
TWRP 3.1.1 - 2017/06/09
Xperia Z3 Dual
See below
md5: 360fd6f9e0e22eb4ff0de72059c7de24
TWRP 3.1.1 - 2017/06/09 | Mandatory if coming from Z3 builds or new to the rom.
Temporal Z3 Dual rom (fixes SIM problems)
nailyk said:
Many thanks to @xkeita for providing a working rom as soon as the device get delivered.
20170622 / b8a79c826ddf0a786010cc04b3943b2e
twrp / 61e8c27f19c114dc9ac1f33dd4c7fb39
Rom is tagged nailyk because I build it but everything on it is @xkeita work!
Many thanks everybody
Click to expand...
Click to collapse
What's new:
Code:
- Updated Camera profiles
- Reworked Z3 Dual RIL
- Updated Audio HAL flags
- BFQ I/O Scheduler
- Bluetooth aptX support
- Qualcomm Connectivity Engine support
- Imported audio ids from original .291
- ANC Headphones support
- Dual Mic config enabled for voice calls/audio recording
- Ok Google everywhere fixed (untested)
- Tweaked autobrightness (again)
Release notes:
2017-06-09 is just a minor update with some [experimental] tweaks for bt connections and fixed minor issues with z3dual
Older Releases
Based on Kernel 3.4
Some of these can be found here
Release History
Code:
2017-06-09:
- Tweaked a little bluetooth values (untested)
- Fixed Z3 Dual sim problems
- Latest Google source (7.1.2_r17)
- June security updates
- Permission fixes for new PowerHAL
- Z3 and Z3 Dual code cleanup
- Forced camera modes to [email protected], [email protected], [email protected], [email protected]
- Fixed all of the device sensors (they're all online and working properly now)
- Latest LineageOS updates
- Smoother UI rendering with CPU
2017-05-17:
- Tweaked general audio output processing
- Updated vendor audio libraries configs (enables qcom effects)
- Auto brightness/brightness changes
- New thermanager configs based on stock
- Changed deprecated Gello for Jelly
- Some device tree cleanup
- General radio/wifi tcp updates
2017-04-16
- Audio changes,
- NFC fixes,
- Brightness changes,
- Verbosity increased for logs after night reboot + PERISTENT_TRACER
- No more vol- buton at boot time
- A lot more
2017-04-05:
- Enforcing selinux
2017-04-01:
- Audio fixes
- Encryption fix
- A lot more that I can't remember right now
2017-03-22:
- Full rework based on stock 3.4 kernel
Based on Kernel 3.10 by @nailyk
2017-01-23:
Download
md5: 04a3a614d820df78e7a70538df61203d
sha1: 10a3ea95d823a6b87b5f5a8f79896e3dabf7a8b5
Status
Workaround for in-call reboot
Include PR1130 PR1128
2017-01-15:
Download / 2
md5: 8b8898c18d631dc7f9d78a18b1e7500f / b40c7ba870ae579827e1bd7a427afc1f
sha1: 588d2c1e0fd2ef4790706980fc1050a8d793d559 / f28ba7714987a94c5ba43a6ee39fe05f0b5a5fca
Use of the reworked device trees
Include some experimental kernel pull requests
2017-01-01:
Download
md5: 6c5abcbeda01c75344cd4296bb2358d1
sha1: a46ef81e2d26ac9610f16cb90bc13e63d58a2983
Switch to LineageOS
Bluetooth deepsleep fixed
2016-12-02:
Download
md5: 496de65608fd4236f5d451a4179e1ce8
sha1: 74a25eabc0f8ac5be3458bd9d98461f9519c7c73
Bluetooth improvements
P.S.: i'm almost affiliated to LineageOS, just like tomascus who made everything.
Sources
Manifest file.
Everything else is Lineage.
Contribute gerrit.
XDA:DevDB Information
LOS-14.1, ROM for the Sony Xperia Z3
Contributors
nailyk, xkeita
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.4.x
Based On: LineageOS
Version Information
Status: Beta
Beta Release Date: 2017-06-09
Created 2016-11-27
Last Updated 2017-07-01

Thank you!
Thanks to
@tomascus
@xkeita
@derf elot
@panzerox123
@Robot76
@gr8st
@mcgi5sr2
@rcstar6696
@yecomixer
@TheAvengingTITAN
@@AdrianDC
@@doriandiaconu
@SuperLamic
@DiscMan55
@drakonizer
@aclegg2011
@DevUt
@tomascus
@blackhawk_LA
@erickas
@malacha
@jimRnor
@optimumpro
@steadfasterX
@Myself5
All the members of the ivy team: @Quarx, @Olivier, @cdesai, @Myself5 and the one I miss.
TeamWin
LineageOS
All the dev who made the downstream kernel
All of you for testing rom and supporting me

FAQ
How to post
I want to say thanks --> Thanks you. Gratitude is really important for us. Find some posts from us and hit thanks buttons. It will be most appreciated You can also use @tomascus donate link.
We are here into the dev thread, not user one. For now the rom is under development.
We wont talk here about not related to device problems (where is foo setting, how to flash bar).
Reports will simply be ignored if already answered.
Reports without logs or step to reproduce are useless (read contribute).
Substratum is officially not supported into Lineage.
You are welcome to post your review: what is working, not working, etc... Check into know issues before.
You are welcome to post your unusual and not supported use-cases (like: "I have only ipv6 at home and the RA doesn't work without IPv4")
You are welcome to report any typo, error, etc...
No variant are supported now. Only D6603. You want support for variant? Consider help on porting or a hardware donate.
My device is screwed and I need it for my job interview in 1h --> go to IRC (how to report problem, #3)
I want say how SODP is bad --> Read this and above.
This is not against you but try to keep thread clean as a dev reference. Thanks in advance.
What is not working
BT headset calls --> pending. Detailed post.
OTG --> 2017-04-16
Wifi auto connect (boot/deepsleep),
HW Encryption, --> 2017-04-16
Vibrator level
4k (unfixable without Sony camera app)
120 fps (pending)
Some volume loudness problem --> not reported
Microphone when ok google is installed (do not install gapps will fix! An app which constantly record your microphone is a malware!) -->Pending,
Slow charging,
Phone reboot at 3AM while plugged-in, --> Workaround disable "auto time" into settings.
NFC, --> topic
Wifi access point,
Adaptive brightness not good. --> Fixed by @xkeita
How to report problems
To report problems there are multiples ways, depend on each person. The How to contribute section provide information on the way to do and should be applicable to everyone. The How to get logs section is the final touch on how to report problems.
Thanks wanting reporting, as, for an early development rom, reports are a necessary step to move forward
Some examples:
I cannot record videos with open camera.
Click to expand...
Click to collapse
Is useless on a dev thread and you probably won't get an answer.
Just wanted to report that this ROM doesn't support my 128gb sandisk SD card..and gives a message, unsupported SD card and asks to format.. this is the only bug which prevents me from using this ROM.. however the same card works perfectly fine on all other ROMs like 7.1 CM or AICP ROM and also all lollipop ROMs and stock ROM.
Click to expand...
Click to collapse
Is better as there is explanation, context and cross rom tests. With log this report used to be perfect.
This guide is really detailed and explained everything about bug reports. (deserve all bug-report cases, not specially this thread or xda)
@steadfasterX write a good guide about IRC, here you can get quick support (like when your device is totally broken, etc...)
steadfasterX said:
You talked about using IRC to get support. What is this and how can I use that?
Meaning of IRC => Internet Relay Chat. A very good IRC client is this one here: hexchat <-- download it and read the quick intro to get started: Quick-Start
--> when asked if you want to join a channel type in "#LineageOS" and after connected you will be in.
If you do not want to install anything you can simply use the webchat instead directly over here: Webchat
Howto communicate? IRC means many people talking the same time and there are some goods and bads to know about using IRC.
So please read this mini and very quick overview (especially the good manners there): Good manners in IRC (matches for all OS not for fedora only)
Click to expand...
Click to collapse
How to get logs
Here you have some info about how collecting log. It is always better to include reference to the Installed version.
How to contribute
I have c knowledge:
All the sources to build this rom are public and are provided into the manifest, in the howto build section. It means all the repository are from LineageOS github, except those mentioned into this manifest. Depending on where you find the bug/improvement there is different way to contribute: gerrit, github PR, etc... Contact me to test with you patch as everyone can try and give feedbacks then join IRC to discuss the best way to merge.
Code is like hieroglyphs for me:
No worries you can contribute anyway! Install the rom, do tests, read failure logs, look at internet for potential fix/similar users experience, is the biggest part of debugging. Then collect all of this and write your results here.
Code is like hieroglyphs for me and logs are worst:
No problem, collects logs the right way if you can, explain how you encounter the problem: detailed step to reproduce could be enough: explain exactly how you encounter the error/problem, it should produce each time someone repeat your steps. Then we will be able to fix it.
Installed version
When reporting problems, specially for work in progress, it is good to provide the build version:
- 'uname -a' will give you the kernel version,
- 'getprop ro.cm.display.version' will give you the rom build version.
What is LineageOS
LineageOS is re-brand of CyanogenMOD. At the end of 2016 some bad things appends. Lineage is the same rom that CyanogenMOD so you can still dirty flash, etc... However as all *cyanogenmod.org services are down, OTA update will not work until you flash lineage one time.

Thanks for posting this rom. Thank you for your awesome developing.

Great work man!!! I hope you will continue you work on CyanogenMod for Xperia Z3!!! Thanks

great work and z3 compact?

What I don't understand is you seem to be having a whole bunch of issues with CM, whereas Rhine devices build perfectly well and all features work on them.
Have you tried building AOSP using Sony Xperia dev sources?
Back in the cm13.0 days, all I used to do to build cm13.0 was use all AOSP device trees and HALs and just make a cm.mk and include vendor/cm/common_phone.mk and everything used to work perfectly fine. Have you tried that?
Anyway, I love the way you develop and your determination. I hope to see you around here often!

drakonizer said:
What I don't understand is you seem to be having a whole bunch of issues with CM, whereas Rhine devices build perfectly well and all features work on them.
Have you tried building AOSP using Sony Xperia dev sources?
Back in the cm13.0 days, all I used to do to build cm13.0 was use all AOSP device trees and HALs and just make a cm.mk and include vendor/cm/common_phone.mk and everything used to work perfectly fine. Have you tried that?
Anyway, I love the way you develop and your determination. I hope to see you around here often!
Click to expand...
Click to collapse
Thanks a lot but your are in a position to know that all the dev had been done by others and I am only porting for now
The biggest source of issue building CM was the codename change. Into sonyxperiadev and all other close to OEM codename is 'leo'. Historically cm rename the device to 'z3' because they already have leo (HTC hd2, IIRC). Here start the pain: as you build too you know a *bunch* of files are codename dependent. Also I wonder if a codename check isn't present into blobs.
I haven't tried to build aosp for now as I didn't have enough free space and wont learn another toolchain. But I test carbon rom which is really efficient.
I tried what you said and give me the best result. Now my branch are ~even with sonyxperiadev. The problem is those version can't be pushed to official CM repo.
We are now experiencing problems on hardware accelerated display, like FPS drop, but I'm not able to fix this. So next step is deep sleep. Are you experiencing this too? Can I ask you some points about this please? Like enabling debugfs, collecting logs after tests etc...?
Edit:
mcgi5sr2 said:
We are still getting echo on the line and a static in call volume issue on the d5803 with latest sources. rancidfrog has provided logs
https://github.com/sonyxperiadev/device-sony-aries/issues/49#issuecomment-263256754
is the issue isolated to the Aries or do Leo users have this issue as well? Similar question to Honami board devices?
Click to expand...
Click to collapse
Can you report me as I can answer please?

nailyk said:
Thanks a lot but your are in a position to know that all the dev had been done by others and I am only porting for now
The biggest source of issue building CM was the codename change. Into sonyxperiadev and all other close to OEM codename is 'leo'. Historically cm rename the device to 'z3' because they already have leo (HTC hd2, IIRC). Here start the pain: as you build too you know a *bunch* of files are codename dependent. Also I wonder if a codename check isn't present into blobs.
I haven't tried to build aosp for now as I didn't have enough free space and wont learn another toolchain. But I test carbon rom which is really efficient.
I tried what you said and give me the best result. Now my branch are ~even with sonyxperiadev. The problem is those version can't be pushed to official CM repo.
We are now experiencing problems on hardware accelerated display, like FPS drop, but I'm not able to fix this. So next step is deep sleep. Are you experiencing this too? Can I ask you some points about this please? Like enabling debugfs, collecting logs after tests etc...?
Edit:
Can you report me as I can answer please?
Click to expand...
Click to collapse
As far as I know, which is from my honami tests, deep sleep issue was present only in AOSP builds. A quick look at BBS revealed that it was the radio(ProxyServer) that kept the device awake, and using the phone without SIM would let it go into deep sleep.
When I got a chance to build and test cm14.1, there was no such issue with deep sleep.
In order to figure out whether we have the same issue, could you (or someone else in this thread) use BBS and tell me what the app says?
As for hardware issues: since you're using Sony HALs and device trees, I don't understand why you're having said issues.
AOSP doesnt need any new knowledge, in fact, it should be easier to build and test. If you can clear some space, I suggest you try it. It could rule out any issues with the device trees or Sony HALs, and then you can focus on finding the issue with CM.

Hello, I dont get it, where is the download?
I want it sooo badly, but I am to dumb to find the download

Shadow of Destiny said:
Hello, I dont get it, where is the download?
I want it sooo badly, but I am to dumb to find the download
Click to expand...
Click to collapse
As you can see there are no releases in the opening post. I guess that if you really want to help testing you have to ask nialyk for a flashable version. Be aware though that, as stated by the developer, the ROM has still many bugs that harm usability.

mattia.bf said:
As you can see there are no releases in the opening post. I guess that if you really want to help testing you have to ask nialyk for a flashable version. Be aware though that, as stated by the developer, the ROM has still many bugs that harm usability.
Click to expand...
Click to collapse
Well, thanks then.

Shadow of Destiny said:
Hello, I dont get it, where is the download?
I want it sooo badly, but I am to dumb to find the download
Click to expand...
Click to collapse
Link is not yet added because I'm dealing with weird GPU issues and I'm waiting for a feedback about a fix before adding it. It should be ok in some hours.
drakonizer said:
As far as I know, which is from my honami tests, deep sleep issue was present only in AOSP builds. A quick look at BBS revealed that it was the radio(ProxyServer) that kept the device awake, and using the phone without SIM would let it go into deep sleep.
When I got a chance to build and test cm14.1, there was no such issue with deep sleep.
In order to figure out whether we have the same issue, could you (or someone else in this thread) use BBS and tell me what the app says?
As for hardware issues: since you're using Sony HALs and device trees, I don't understand why you're having said issues.
AOSP doesnt need any new knowledge, in fact, it should be easier to build and test. If you can clear some space, I suggest you try it. It could rule out any issues with the device trees or Sony HALs, and then you can focus on finding the issue with CM.
Click to expand...
Click to collapse
IDK what BBS is but the /sys/kernel/debug/wake_lock table is really instructive. From the early experiments we have two issues: like you ril is one of them, and usb is the second one. If your reboot the device in airplane mode without usb attached wake_locks are a bit better.
Yes building AOSP is a good idea but @accleg2011 never get it working so I really doubt I can. Device was really fine on CAF display, game were really smooth, menu too. With SODP display menu are ok now but game are laggy and I don't know how to check if they are software or accelerated rendered. I tried to mimic hammerhead config.mk (it is the same device than z3 except for camera) but it doesn't provide results. I'm almost sure it is another PEBKAC with a missing flag.
I have a bunch of log to analyse and will post my results a bit later. Thanks for your advice, maybe I simply should buy another ssd.
If you have some time to waste, can you try frozen bubble on your device with SODP display, please? When balls pop, it is the most GPU intensive rendering. Is it laggy for you too? (from what I see ~5FPS)

nailyk said:
Thanks a lot but your are in a position to know that all the dev had been done by others and I am only porting for now
The biggest source of issue building CM was the codename change. Into sonyxperiadev and all other close to OEM codename is 'leo'. Historically cm rename the device to 'z3' because they already have leo (HTC hd2, IIRC). Here start the pain: as you build too you know a *bunch* of files are codename dependent. Also I wonder if a codename check isn't present into blobs.
I haven't tried to build aosp for now as I didn't have enough free space and wont learn another toolchain. But I test carbon rom which is really efficient.
I tried what you said and give me the best result. Now my branch are ~even with sonyxperiadev. The problem is those version can't be pushed to official CM repo.
We are now experiencing problems on hardware accelerated display, like FPS drop, but I'm not able to fix this. So next step is deep sleep. Are you experiencing this too? Can I ask you some points about this please? Like enabling debugfs, collecting logs after tests etc...?
Edit:
Can you report me as I can answer please?
Click to expand...
Click to collapse
Hi I posted this in a different thread and am confused as to how it came up in your CM14.1 thread. I build using all the sonyxperiadev device trees

mcgi5sr2 said:
Hi I posted this in a different thread and am confused as to how it came up in your CM14.1 thread. I build using all the sonyxperiadev device trees
Click to expand...
Click to collapse
Pardon my clumsy. I quote you here because thinking that cm can provide useful results for your question as we are using the same devices trees and blobs. Won't do it again.

nailyk said:
Pardon my clumsy. I quote you here because thinking that cm can provide useful results for your question as we are using the same devices trees and blobs. Won't do it again.
Click to expand...
Click to collapse
Hey no problems, I'm actually battling just to get my latest CM build to install properly

mcgi5sr2 said:
Hey no problems, I'm actually battling just to get my latest CM build to install properly
Click to expand...
Click to collapse
Do you take a look at Myself5 repos ? You can ask him a CarbonRom test but his repo where very helpful for leo. Also, maybe you can reuse mine and we can concentrate our efforts. I try to be as close as possible to SonyCM ones.
I will update the OP with the build instructions when XDA will work.

2016-11-28 release
Rom link added.
I'm currently uploading screenshots.
A bunch of peripherals are broken. Since I test this PR bluetooth is broken.
Hardware accelerated part are missing or broken.
Camera is partially working, switching to video mode crash camera app.
Deep sleep still not working.
Gps seems to be broken too.
Don't forget we are into a dev thread please, so post comments with logs, faulty line or patches. Thanks.
This rom is not intended to be used as a daily driver and is unstable!

cm14.1 wowww :good:

After a total mess-up with bluetooth, a full rebuild make it ~work again (still some crash).
And 3D apps seems to be working too.
Can you confirm/infirm difference please?

[9][OFFICIAL][WEEKLY] CarbonROM | cr-7.0 [maple]

Downloading,I will feedback

Sorry for my bad english
But I found some problems:
1. NFC is not working, I cant open NFC
2.Fingerprint sensor is insensitive,
when I try to create my fingerprint,the system says "It has stains on sensor." but I have cleaned already
Sorry it seems that is my problem , please ignore it.
3.Style Cover Stand SCSG10 is working inappropriate (same problem on early oreo builds)
when i covered up, xzp couldn't sleep
4.Mobile data cant work
others seems work perfectly
My firmware is 47.2.A.10.107
---
Edit:
I changed firmware to 47.1.A.16.20, NFC can work now
SCSG10 still works inappropriately, and Mobile data doesn't work. (only calls / sms)
But now the system says "your vendor doesn't match to your system".

1,NFC is dead
2,G8142 card 2 can't be recognized
3,Network not available
（basic on .107）
other things working Great！！！
how about make Camera Switch available？

I'm coming from a fully clean install of 47.2.A.10.107.
NFC is working fine, however I can confirm the mobile data issue, which is very weird as this was working flawless before. I'm looking into it.
As for DualSIM support: I released a build in the 6.1 thread a few days ago, which no DualSIM user provided any feedback to, so I went ahead and released these builds with the Single SIM device in mind. Unless I find a way to unify the devices (like I did in Oreo, which apparently doesn't work anymore because thats what this build uses) I'm not going to support the DualSIM variants.
If anyone is willing to help me debugging this issue on the DualSIM variants by flashing testbuilds and getting logs etc, hit me up.
Edit: found the cause for the mobile data, must've removed that by accident during a cleanup. A working build will be released later today
EDIT2: Build is running right now and will appear on the download page once done.

Can anyone confirm camera2api and gcam hdr+ support?

Thanks for fixing Mobile data and now it works.
NFC is also working, but need reboot after gapps setup wizard or first boot, I dont know if this is a problem.
(Just clean flash 47.2.A.10.107, I dont know why i cant open nfc in my first try. I clean flashed before...)
Incrovantilist said:
Can anyone confirm camera2api and gcam hdr+ support?
Click to expand...
Click to collapse
No, this rom blobs are based stock, so no level3 support.

Just flashed the rom and its smooth and awesome. So far everything working except dt2w.
For some reason with Magisk 19.3, ctsProfile is returning false. It didnt fail in any of the other SODPs or the latest stock rom. Anyone facing same issue?

Myself5 said:
I'm coming from a fully clean install of 47.2.A.10.107.
NFC is working fine, however I can confirm the mobile data issue, which is very weird as this was working flawless before. I'm looking into it.
Click to expand...
Click to collapse
It seems Carbon's kernel tree is almost identical to cryptomilk's.
I recall I can't turn on NFC when using cryptomilk's kernel tree to build my own ROMs, either. However, NFC works fine with Sjll's kernel tree, despite being a few days older.
Not sure about the exact cause of this, but it's possible that something in 47.2.A.10.107 might be needed. My phone is currently still based on 47.2.A.10.80 as the .107 build for my region is not out. If the older stock base is indeed the cause of the issue, I'll consider flashing a current stock ROM of different region.
Myself5 said:
As for DualSIM support: I released a build in the 6.1 thread a few days ago, which no DualSIM user provided any feedback to, so I went ahead and released these builds with the Single SIM device in mind. Unless I find a way to unify the devices (like I did in Oreo, which apparently doesn't work anymore because thats what this build uses) I'm not going to support the DualSIM variants.
If anyone is willing to help me debugging this issue on the DualSIM variants by flashing testbuilds and getting logs etc, hit me up.
Click to expand...
Click to collapse
Does SD card functionality still work on G8142? I haven't tested the new CarbonROM build, but personally I had positive results with SD card on other ROMs/kernels that were targeting G8141.

LSS4181 said:
It seems Carbon's kernel tree is almost identical to cryptomilk's.
I recall I can't turn on NFC when using cryptomilk's kernel tree to build my own ROMs, either. However, NFC works fine with Sjll's kernel tree, despite being a few days older.
Not sure about the exact cause of this, but it's possible that something in 47.2.A.10.107 might be needed. My phone is currently still based on 47.2.A.10.80 as the .107 build for my region is not out. If the older stock base is indeed the cause of the issue, I'll consider flashing a current stock ROM of different region.
Click to expand...
Click to collapse
Given it works on both my phones that were on .107 before and that the blobs are from .107, this could be the cause. If you flash the latest stock ROM make sure to fully boot into it at least once because the stock ROM sometimes also upgrades the NFC Firmware on the chip itself.
P.S. The kernel is the same as cryptomilks.
LSS4181 said:
Does SD card functionality still work on G8142? I haven't tested the new CarbonROM build, but personally I had positive results with SD card on other ROMs/kernels that were targeting G8141.
Click to expand...
Click to collapse
Oh cmon man you literally quoted a message of me saying that I don't have the Dual SIM variant nor any testers for it (yet). I have quite a few ideas on how I could fix it, but without any testers I'm just not gonna touch it at all.

I have G8142 and I can say, "Yes, SD card still works on G8142."
But I dont have 2nd sim card so i cant test if dualsim works

.107 clean installation, there were also problems with NFC, after rebooting it was fixed.

The Smart Cover function does not work, the screen continues to light after closing the cover, or the action of the magnetic cover (by the Hall sensor), I do not know how it should, but it does not work ..

So far stable enough to be daily driver except issues with magisk. Magisk keeps getting uninstalled on its own and have to be reinstalled in twrp every now and then. And after it gets installed, the rom stutters and doesn't open any apps or the settings and have to be restarted a few times for it to go back to normal.
Also a feature to modify charging led settings would be awesome. (I tried to find and modify it in root but couldn't find the charging led settings in /sys/class/leds)
Camera is frickin awesome. It's sooo much better than stock even without lvl3 camera2api. For anyone trying to find a decent camera app, try using opencamera with camera2api enabled in settings. Except for hdr(doesn't work, will force close), it's able to take really good images. If only somehow able to shoot 960fps slomo .

Magisk 19.3 - there were no problems with self-removal, there is a delay when starting up applications with a white screen after a reboot, it holds the battery well 2% per night.

I spent some time working with @haiha2001 on the XZ1 Dual today. Along the road we came across a few things but it's not working yet. HOWEVER, the XZ1 seems to have a different/more advanced issue than the XZ Premium. Whereas the XZ Premium has SIM1 working, the XZ1 doesn't have any SIM working at all.
That brings me to the following:
There was a fairly obvious flaw (thank Sony for that for not having unity of system property locations across Single/Dual SIM) which could explain why only one SIM is working on the XZ Premium. I've fixed it in the linked boot.img. If someone with two SIM Cards and the Dual SIM variant could try and let me know how it's doing on maple_dsds I'd be very happy.
https://dl.myself5.de/maple/.fwafwafwafo/boot.img
flash it via fastboot with
Code:
fastboot flash boot boot.img
on top of the latest weekly.

Just flashed your boot.IMG
I'll put in the wife's sim and see

Myself5 said:
I spent some time working with @haiha2001 on the XZ1 Dual today.
Click to expand...
Click to collapse
Off-topic but @haiha2001 is a great guy! He also tests aroma zip files and other zips for me, to do with another rom.

Beetle84 said:
Off-topic but @haiha2001 is a great guy! He also tests aroma zip files and other zips for me, to do with another rom.
Click to expand...
Click to collapse
Because I see the XZ1 seems to be less supported by programmers for this device while the XZ Premium has quite a lot, while I know that the XZ Premium is not too different from the off-screen XZ1, so I'm willing to support the programmers to check the rom or mod version for XZ1, if they have an idea I will help my best ?
Sent from my Sony G8342 using XDA Labs

beammer335d said:
Just flashed your boot.IMG
I'll put in the wife's sim and see
Click to expand...
Click to collapse
Did she voluntarily gave it to you yet or do we need to send armed troops to make her ? First screenshot looks promising already.
also, in case you're rooted, please get me the output of the following:
Code:
adb shell
then enter
Code:
su
(Accept Magisk request on the phone)
and then run
Code:
cat /cache/modem/modem_switcher_status
cat /cache/modem/modem_switcher_report
And send me the output.
Alternatively you can run it via terminal emulator starting at the "su" part.
Beetle84 said:
Off-topic but @haiha2001 is a great guy! He also tests aroma zip files and other zips for me, to do with another rom.
Click to expand...
Click to collapse
+1

[ROM] [UNOFFICIAL] LineageOS 16.X | 17.X for LG G4 | Android 9.X | 10.X

{
"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"
}
Lin·e·age
/LineageOS/
1. lineal descent from an ancestor; ancestry or pedigree.
2. a sequence of species each of which is considered to have evolved from its predecessor.
Download from my unofficial LineageOS Download Folder:
Mega: Lineage 16.0
Mega: Lineage 17.0
Open Gapps:
http://opengapps.org/#
-LG G4 needs Platform "ARM64"-
-*You don't have to use Gapps if you don't want to-
Wiki:
https://github.com/Suicide-Squirrel/android_device_lge_g4/blob/lineage-17.0/README.md
https://wiki.lineageos.org/devices/h815
https://wiki.lineageos.org/devices/h811
https://en.wikipedia.org/wiki/LG_G4

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.
*/
Contributors
kessaras
steadfasterX
Additional information and details here: https://forum.xda-developers.com/g4/development/rom-lineageos-16-0-t3929082
XDA:DevDB Information
[ROM] [UNOFFICIAL] LineageOS 16.X | 17.X for LG G4 | Android 9.X | 10.X, ROM for the LG G4
Contributors
kessaras
Source Code: https://github.com/Suicide-Squirrel
ROM OS Version: 9.x Pie
ROM Kernel: Linux 3.10.x
ROM Firmware Required: !!>>>>> Nougat v29A <<<<<!!
Based On: LineageOS
Version Information
Status: Stable
Current Stable Version: 16
Current Beta Version: 17
Created 2019-09-05
Last Updated 2019-09-05

Yea LOS 17 isn't even out and you made it
You have done an awesome job here again!
I didn't know that you plan to build and offer LOS 16(!) as well... maybe you describe the difference to my builds so I and everyone else understand why you are doing this?
Sent from my OnePlus 6T using XDA Labs

steadfasterX said:
Wow I didn't know that you plan to build and offer LOS 16 as well... maybe you describe the difference to my builds so I and everyone else understand why you are doing this?
Click to expand...
Click to collapse
No I'm not building 16.
I just made the thread for lineage 17 because that's the only one I'm going to build for this specific device.
I could also share nothing and build for myself.
Is there some problem ? Your post looks like you are attacking me for some reason. Is it about glory ?
Very kind of you.
We r alone here in a legacy device full of problems and we keep this device alive when most of developers quit on it, and even LG quit on it and the first thing I see below lineage 17 op is you attacking me. But I won't delete it. I will keep this post there to remind me of this day.
And to think that I also actually linked to your thread out of respect of it...

Awesome man can't wait to try this out! Kessaras Just curious is the LOS 16 your build of it or just SFX one? Just wondering cause i want to try it out.

kessaras said:
No I'm not building 16.
I just made the thread for lineage 17 because that's the only one I'm going to build for this specific device.
I could also share nothing and build for myself.
Is there some problem ? Your post looks like you are attacking me for some reason. Is it about glory ?
Very kind of you.
We r alone here in a legacy device full of problems and we keep this device alive when most of developers quit on it, and even LG quit on it and the first thing I see below lineage 17 op is you attacking me. But I won't delete it. I will keep this post there to remind me of this day.
And to think that I also actually linked to your thread out of respect of it...
Click to expand...
Click to collapse
calm down I was just curious and that's why I'm asking why LOS 16. There was no offense in my request sorry if I made you felt like that. I have changed my post a bit in the hope it's better understandable now.
Glory? Lmao.. I always refer to the suicide team in my changelogs as our ROMs like aoscp and LOS is done by teamwork not by a single person. Exactly that was the reason why I said you should explain why you build an own version of LOS 16(!) so ppl understand the differences and there are some. That's all.
Sent from my OnePlus 6T using XDA Labs

Scooterthedude said:
Awesome man can't wait to try this out! Kessaras Just curious is the LOS 16 your build of it or just SFX one? Just wondering cause i want to try it out.
Click to expand...
Click to collapse
steadfasterX said:
calm down I was just curious and that's why I'm asking why LOS 16. There was no offense in my request sorry if I made you felt like that. I have changed my post a bit in the hope it's better understandable now.
Glory? Lmao.. I always refer to the suicide team in my changelogs as our ROMs like aoscp and LOS is done by teamwork not by a single person. Exactly that was the reason why I said you should explain why you build an own version of LOS 16(!) so ppl understand the differences and there are some. That's all.
Sent from my OnePlus 6T using XDA Labs
Click to expand...
Click to collapse
Ok.
First of all,
i'm not the type of guy who will maintain something old.
When N was released that was when i started developing for first time and i made custom roms here have same camera quality with stock, because i wanted it for myself. I wanted to take good photos, not some bad pixels with noise.
When O was released i abandoned my sleep and i spent 3 weeks x24 hours to make this uncompatible kernel work perfectly to bring up O. And i did. I imported the code from bullhead line by line so that i won't break anything.
When P was released i did it in 1 day (i had more experience + all this hard work in O was not for nothing). I didn't release it because i let it go to bring up AOSCP for p20 pro. Few months later I came back and we made this thing stable together.
Now i did Q in just few hours. I didn't release it because i want to do a "clean" work. I forced it to build by hacking the "build" repo. So i can't push those commits, so i wait a bit.
But what history showed ? Upon every new Android release i never maintained the old one and i never built all variants. I do not have a server and i need my PC to also entertain myself, i can't have it building for hours.
So , even if i did one Lineage 16 build what does it really matter ? And even if i bring up Q in a few days what does it really matter ? It's your server who will be building and will be doing the most work.
One Lineage 16 build means nothing. I will never build Pie again just like i never built Oreo again.
Differences:
1. https://github.com/Suicide-Squirrel...mmit/c6fc9746ec75bc76e8b0247b007ef1ad89af0ac3
2. https://github.com/CypherOS/hardware_qcom_power/commits/poundcake-release
3. kernel. Instead of fixing some useless functions , i chose to remove them, in order to have less jobs for CPU to do.
4. Policies. I have added more policies when on the other hand you added less policies and have some functions blocked.
Nothing else. 3 and 4 are just details.
And it's just personal. I simply shared one build, the one im using at my phone.
XDA is about sharing. It's not our job. I'm simply sharing the rom i flash to my device.
In my point of view , i do not have to answer to questions like whats different. They do not even pay me. I'm not selling anything. I do this for fun.
I'm not doing Pie. The link is there until i release Q and it will stay there for historical reason.
To remind me that this was the last Pie and what i see in that rom is the fruit of a hard work of one whole year.
CU in Q.

little advice for ppl passing by: flashing kessaras los 0409 over latest los by sfx results in bootloop.

sperelli said:
little advice for ppl passing by: flashing kessaras los 0409 over latest los by sfx results in bootloop.
Click to expand...
Click to collapse
yup. they have those differences that make my rom unique so it's like another rom. You can't dirty flash from one to the other.

Does Los 16 have the play store issue? Will Q have it also? Since your banned from Google.

I try to install lineage-16.0-20190904-UNOFFICIAL-h815.zip
From TWRP all is done....i restart my device and after 2 minutes with logo restart and come back to TWRP....why?
Resolve: Don't install TWRP app and set it like a System App

Nova Launcher don't work, it close endlessly :'(

Gigio755 said:
Nova Launcher don't work, it close endlessly :'(
Click to expand...
Click to collapse
Many App keep crash....Google Photo too

Scooterthedude said:
Does Los 16 have the play store issue? Will Q have it also? Since your banned from Google.
Click to expand...
Click to collapse
It doesn't matter what rom I build , I have apps missing.
I'm lost I don't know where the ban exactly is.
When I build from @steadfasterX server there is no ban.
For example if sfx syncs to aoscp and build it , there is no ban.
So don't worry. Me I will bring up Q. After that only when I build it it will have apps missing.
So strange.... I will maybe try change my email and signature in the future to test what will happen.
Gigio755 said:
Nova Launcher don't work, it close endlessly :'(
Click to expand...
Click to collapse
Albertrebla said:
Many App keep crash....Google Photo too
Click to expand...
Click to collapse
Normally I shouldn't care for third party apps.
If you get me a log while it crashes I will take a look at it.
And Google apps don't crash. I use them too. I'm Google addicted. Google even knows when I'm in the toilet
Start logd before you get a log, as a root.
adb shell start logd
"There are times that you guys are making angry."
Is it even possible , since i still use this phone and i'm using the rom i build, to have stuff or core apps or default apps or google apps crashing and i haven't done anything about it ?
(3rd party apps is another story).
It's like you don't trust me and i'm here since 2013......
Always logs ! No chatting.
Say i have this problem here is the log.
I will see what you did wrong or what i did wrong , the next day it's fixed.

Yeah I see ....
Just to lose my time for nothing , right ?
?
Isn't this Nova Launcher ? It's not crashing.

Yeah I'm using Los 16 and everything is running smooth with stock open gaps and migrate of apps. Nothing's crashing. H811. Good battery life also. Thanks for looking into the Google ban issue. Much appreciated.

kessaras said:
Yeah I see ....
Just to lose my time for nothing , right ?
Isn't this Nova Launcher ? It's not crashing.
Click to expand...
Click to collapse
Don't be ironic, what do you think we're both here to lose time? easy man :silly:
I only report my experience, with your 04/09 build, i clean flash, i had problem with nova launcher prime, when the system ask which launcher use by defaul and i tap nova, it crash, at reboot even, new clean flash even
it's not a problem for me, i flashed another rom, I'm not here to bother you

Scooterthedude said:
Yeah I'm using Los 16 and everything is running smooth with stock open gaps and migrate of apps. Nothing's crashing. H811. Good battery life also. Thanks for looking into the Google ban issue. Much appreciated.
Click to expand...
Click to collapse
But the ban is still present?

crettit1204 said:
But the ban is still present?
Click to expand...
Click to collapse
Yes it is. That's one thing I really hope he can figure out when q comes along from him.

Hey @kessaras
Thank you for making this build for this legacy device that I still use as my daily driver.
Is the camera on your oreo rom the same as stock?
That is the biggest gripe I have with using LOS at the moment
Do you plan on doing monthly builds for H815 to incorporate the latest security patches?

owlery_hk said:
Hey @kessaras
Thank you for making this build for this legacy device that I still use as my daily driver.
Is the camera on your oreo rom the same as stock?
That is the biggest gripe I have with using LOS at the moment
Do you plan on doing monthly builds for H815 to incorporate the latest security patches?
Click to expand...
Click to collapse
Hey! This thread is only for Los 16 and 17 which means Android 9 and 10! You can try the builds yourself, I think this is the best way to decide. Until now, yes, these guys have been providing almost monthly builds, including the monthly security patches.

Develop Bugs

welcome