Lucky-KernelForExynos-Variant's
Code:
#include
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this Kernel
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
* If you dont like this Kernel, Stay away from this thread!
*/
What to say... I come from Samsung Galaxy Nexus and its development until the beginning of September 2016...
I did a one-year break from kernel programming, and I came back here for you. To bring you a good kernel for this device that still has a lot to give.
My work is on kernel source, I add, delete, modifing code, but with a criterion, that everything, must make sense
I consider the kernel as beta, although it is very stable, I will update the kernel when needed, with the necessary security patches, and a few extra grays
Android8.0
This kernel Boot on 8.0(lineage-buid) but I think also on AOSPExtended rom 8.0 it will Boot..
Android7.1
EDIT: Don't Boot.. thank's to @spookcity138 for news
Good download at all, and let me know your opinion
XDA:DevDB Information
[KERNEL] Lucky [O], Kernel for the Samsung Galaxy S5 Mini
Contributors
Fenix46, hennymcc, spookcity138
Source Code: https://github.com/Fenix46/android_kernel_samsung_kminilte
Kernel Special Features:
Version Information
Status: Beta
Beta Release Date: 2017-11-11
Created 2017-11-11
Last Updated 2017-11-12
Reserved
Del.
Good evening,
at first I had the patched twrp from the LineageOS 15.0 thread installed and flashing your kernel it produced a fault 11 error. Then I flashed the official twrp and the installation on AOSPExtended 8.0 worked just fine.
Could you please elaborate a little bit more what you did to the kernel sources or if there is something special included? Nevertheless: Thank you for contributing!
Best regards
Hey,
Great to have another developer working on the S5 Mini! I can confirm that the kernel does not boot on 7.x ROMS (Slim7 at least,but I imagine all) I expected this though as my kernel build doesn't boot on Android 8. I can also confirm issues flashing with the Oreo compatible TWRP version. I just recently flashed a test build of TWRP by Ayke and got this same error 11,so I extracted the boot.img and flashed that. I also tried to flash my kernel after yours to get my system back up and also got an error flashing in TWRP,so something has changed there apparently.
tester02 said:
Good evening,
at first I had the patched twrp from the LineageOS 15.0 thread installed and flashing your kernel it produced a fault 11 error. Then I flashed the official twrp and the installation on AOSPExtended 8.0 worked just fine.
Could you please elaborate a little bit more what you did to the kernel sources or if there is something special included? Nevertheless: Thank you for contributing!
Best regards
Click to expand...
Click to collapse
Yep, with official twpr, flash without problem, this error 11 is related to the twpr for Oreo... however, I've add some commit on kernel source, and my work is this, add commit, and update the kernel
spookcity138 said:
Hey,
Great to have another developer working on the S5 Mini! I can confirm that the kernel does not boot on 7.x ROMS (Slim7 at least,but I imagine all) I expected this though as my kernel build doesn't boot on Android 8. I can also confirm issues flashing with the Oreo compatible TWRP version. I just recently flashed a test build of TWRP by Ayke and got this same error 11,so I extracted the boot.img and flashed that. I also tried to flash my kernel after yours to get my system back up and also got an error flashing in TWRP,so something has changed there apparently.
Click to expand...
Click to collapse
@spookcity138 thank's for welcome However Thannk's again for feed on 7.x rom... this error is related at updater-script.. on Oreo the first line "assert" is not present, so cause this.. but with official twpr flash go fine, I think to change the updater-script if cause another problem
I would't call this development or a kernel which offers something over the stock LOS kernel (that's the reason why no changes are mentioned in the OP - because there none). I only see 1 rename commit. So overall it doesn't change anything which deserves to call it 'your' kernel. This entire repo are upstream commits only. If you only provide such 'development' I highly suggest to work directly on the official kernel and submit pull request instead which then would help everyone and not only people which using this kernel here.
CHEF-KOCH said:
I would't call this development or a kernel which offers something over the stock LOS kernel (that's the reason why no changes are mentioned in the OP - because there none). I only see 1 rename commit. So overall it doesn't change anything which deserves to call it 'your' kernel. This entire repo are upstream commits only. If you only provide such 'development' I highly suggest to work directly on the official kernel and submit pull request instead which then would help everyone and not only people which using this kernel here.
Click to expand...
Click to collapse
what changes did you want to find on the kernel? did you see the commit series I added? Do you think the changes are all in the name of who works on the kernel? for those who work on ROMs as @hennymcc or @spookcity138 or other's they can very well take my base and insert it to build the ROM..
I expect some changes which improving the kernel e.g. in performance otherwise I stick with the LOS kernel because you 'commit series' I found so far are years old now and pointless in Oreo. I'm not sure what's the point to create an thread when there are seriously no changes, I not deny that you might work on it but that should be mentioned as 'work in process' or something here but since there is no changelog, downloadable release or explanation on this kernel I think I have the right to ask what's going on here.
And just because someone else might contribute to your project doesn't mean this is relevant, as said I checked it and there was no change. I haven't chedckd all branches but master and the asop-8.0 branch was not really what I expected to see when someone announce a kernel. As said earlier I think it would be better to contribute to LOS directly instead of making another kernel.
Please explain or show why someone should use your kernel or in other words - what's wrong with the LOS one?! Thanks.
CHEF-KOCH said:
I expect some changes which improving the kernel e.g. in performance otherwise I stick with the LOS kernel because you 'commit series' I found so far are years old now and pointless in Oreo. I'm not sure what's the point to create an thread when there are seriously no changes, I not deny that you might work on it but that should be mentioned as 'work in process' or something here but since there is no changelog, downloadable release or explanation on this kernel I think I have the right to ask what's going on here.
And just because someone else might contribute to your project doesn't mean this is relevant, as said I checked it and there was no change. I haven't chedckd all branches but master and the asop-8.0 branch was not really what I expected to see when someone announce a kernel. As said earlier I think it would be better to contribute to LOS directly instead of making another kernel.
Please explain or show why someone should use your kernel or in other words - what's wrong with the LOS one?! Thanks.
Click to expand...
Click to collapse
What you saw, that you think is old, are needed on Nougat as well, because interfaces better the kernel, with the modules, because our kernel don't have support on kernel Device Three.. and it's just the beginning of this, because my main job will be to reformulate the theard for a rom. Nothing to take away from the kernel LOS, and I did not want to create useless controversies. if you do not want to use this kernel, it does not change anything. however if you look good on the download section, find the zip package to download.
Twrp 3.1.1 official, SM-G800F, AospExtended Oreo. Error 11 by flashing.
Where is the Download Link?
Open xda in Browser, under downloads
(look at the middle of my Screenshot)
MikeT. said:
Open xda in Browser, under downloads
(look at the middle of my Screenshot)
Click to expand...
Click to collapse
Thanks
. . .
Related
CyanogenMod is a free, community built, aftermarket firmware distribution of Android 6.0.x (Marshmallow), which is designed to increase performance and reliability over stock Android for your device.
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
*/
CyanogenMod is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. You will need to provide your own Google Applications package (gapps). CyanogenMod does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for CyanogenMod is available in the CyanogenMod Github repo. And if you would like to contribute to CyanogenMod, please visit our Gerrit Code Review. Your changelog is whatever was merged into gerrit.
Instructions
First time flashing CyanogenMod 13.0 on your device, or coming from another ROM?
Download the zip(s).
Install a compatible Recovery
Perform a NANDroid backup of your current ROM (Optional)
Wipe data & cache partitions of your device (required when coming from stock!).
Flash CyanogenMod.
Optional: Install the Google Apps addon package.
Broken Features / Known Issues
VIDEO ENCODER/DECODER ISSUES: This results in green lines on videos/pictures taken using the Intel HW encoder/decoder and other playback issues dependent on video formats. See the list below:
Snapchat: thin greeen line tends to appear on recorded videos for snapchat
Asus Pixelmaster Camera App: Super resolution mode does not work. Turning off "Optimizations" from settings clears up any green line issues.
Some video formats do not play as expected
FM Radio is unsupported.
audio is a little weird in Real Racing 3.
sim 2 cannot be disabled (this is true for all CM builds on non qualcomm hardware)
Other than Fugu (Nexus Player TV box) there are no Vendor released M x86/x86_64 builds in existance. You may experience some issues with GAPPS and some known apps not loading or working correctly. Below is a list of KNOWN apps that do not currently run on CM13 based x86 Zenfone 2 builds :
Ingress, Polaris Office, Chase Mobile, Showbox...
Other Issues?
Before posting on this thread, make sure of a few things:
You've utilized the search function of the forums. Nothing irritates me more than lazy people who do not search for an answer before asking or ask the same question over and over again.
If you are the only one having a problem. Boot into recovery, wipe data/factory reset, reflash the rom/gapps and nothing else. Boot up and see if the problem persists.
Make sure your post is relevant to this thread. "I'm having problems rooting/unlocking" is NOT relevant here.
LOGS LOGS LOGS!!!! Use this: SysLog by Tortel
As the Zenfone2 has multiple models from multiple countries please include the following information in your report:
model #
CPU Speed / RAM Size
device state when errors occur (BT/wifi/nfc on ? On a call ? sitting idle on shelf ? )
method to reproduce if you've found something consistent
Download Links
CyanogenMod for Z00A/ ze551ml: ROM @ http://get.cm/?device=Z00A
CyanogenMod for Z008/ ze550ml: ROM @ http://get.cm/?device=Z008
Recovery Links
Z00A
Official TWRP: TWRP.ME
Z008
Official TWRP: TWRP.ME
Google apps addon:
Recommend GAPPS for now as the updated x86 gapps. Our resident x86 GAPPS guru @deadman96385 has been working with the opengapps crew to keep these current for us.
Flashable Modem updates:
Currently only supported in jrior001's unofficial TWRP
May or may not work in others
** see this post for more info **
Intel stores some modem firmware in the OTA's in a file labeled "ifwi.zip"
These are flashable zips to receive the updated firmware while staying on custom ROMS
**THIS IS A ONE WAY PROCEDURE, JUST LIKE THE OTA's THERE IS NO KNOWN WAY
TO FLASH BACK TO EARLIER MODEM FIRMWARE, PROCEED WITH CAUTION**
IF you still wish to proceed, current flashable ifwi zips are available HERE for Z00A AND Z008
FOR INFO ON MM BOOTLOADER BASED BUILDS SEE THIS POST
XDA:DevDB Information
CyanogenMod 13.0 Nightly Bulids (Z00A/Z008), ROM for the Asus ZenFone 2
Contributors
jrior001, crpalmer
Source Code: https://github.com/CyanogenMod/android_kernel_asus_moorefield
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.10.x
ROM Firmware Required: 2.20.40.16x stock base
Version Information
Status: Nightly
Created 2015-12-05
Last Updated 2016-09-07
Reserved
FAQ
Does Official TWRP work?
* Yep
* Unified recovery builds as of TWRP 3.0.0-0, same build for both Z00A/Z008
Can I use a custom kernel with these builds?
* At your own risk, don't complain here if something gets broken in the process
*Also, doing so makes any feedback useless to us because the kernel and the ROM are a complete package and changing part of that means you may have broken something beyond our control.
Will this be an Official ROM?
* When all the show stopping bugs are fixed and all the upstream commits are merged, yes.
* Until then, no because CyanogenMod has very high standards for accepting new devices.
* As of 3/17/16 we now have official builds
Do I need to unlock the bootloader?
* Yes.
Upgrade from CM-12.1 ?
* Tools have been put in place to make upgrading from 12.1 nightlies smooth however backups are always recommended. Make a backup and attempt upgrade from 12.1 -> 13.0. Make sure to Flash 6.0 gapps at the same time. 6.0 only applies the proper permissions for system apps on first boot.
* If the above fails to load smoothly, restore your backup, take the necessary backups of apps and such and make a clean flash upgrade instead.
EXTERNAL SDCARD in M
* There were major changes in AOSP in the handling of storage.
* Two options :
(1) used as external storage. Removable, plug and play storage like we all know and love.
(2) used as Adoptable storage. non removable, Sdcard becomes an extenstion of your /data partition. Removing Sdcard will cause signifigant data loss.
* On first boot you are presented with the option to choose how to handle your sdcard. CHOOSE WISELY
* read more about this feature in this article from android central
Green lines on Pixelmaster camera/Snapchat
* In the Asus camera app disable "Optimizations", this should clear green lines/distorted pictures here.
* In Snapchat, issue is far less intrusive and there is no workaround.
FM Radio
* Currently this is unsuported. As of yet we have not managed to figure out how Asus made this feature work. Should we figure that out We'd love to support it but until then it is not a high priority issue to resolve. ** UPDATED** I found some source code for the FM radio implementation but it's clearly marked as proprietary and unuseble by us at this time.
Call Recording
Native Call Recording is a feature that while only legal in some countries, has become very popular on CM.
Currently we do not have full audio HAL source for Intel devices and have no way to implement this in CM for this device.
C-APPS
They're are currently no C-APPS packages for CM-13. Due to the way M handles system app permissions this is not likely to be available at any time in CM13.
I'd like to make a donation
Support of this project is a joint effort between @crpalmer and @jrior001. Many users like to show support via Donations. If you feel so inclined to support us in this manner you can do so HERE(jrior001) and HERE(crpalmer). Donations are by no means expected, but always appreciated.
Reserved
Wow.. AWESOMEE.. Thanks Guyzz
Full wipe required when coming from 12.1?
Awesome!!! But... Must.. Resist... The urge.... Aauuggggh.
Updates issues and notes on upgrading from cm-12.1 .
RIL connectivity is not very good right now, requires manual setup on most sims. Clean install w/gapps is preferred, but CM team goes to great lengths to make sure upgrade path is smooth so a flash-able update from 12.1 nightly "should " work fine. Just make sure to flash your gapps w/ROM prior to rebooting. Flashing gapps later is not something that is going to work well for you.
jrior001 said:
Updates issues and notes on upgrading from cm-12.1 .
RIL connectivity is not very good right now, requires manual setup on most sims. Clean install w/gapps is preferred, but CM team goes to great lengths to make sure upgrade path is smooth so a flash-able update from 12.1 nightly "should " work fine. Just make sure to flash your gapps w/ROM prior to rebooting. Flashing gapps later is not something that is going to work well for you.
Click to expand...
Click to collapse
We have resolved the DRM video issue and the audio lag in games has yet to be an issue in cm-13 thus far.
I should be studying for a test, but........CM13 is coming first now
Sent from my ASUS_Z008 using XDA Free mobile app
Fantastic! Just Z00A for now?
Just finished the SAT. Came home to a welcome surprise!
troy5890 said:
I should be studying for a test, but........CM13 is coming first now
Sent from my ASUS_Z008 using XDA Free mobile app
Click to expand...
Click to collapse
550 version doesn't seem to be up yet, unfortunately.
kanagawaben said:
Fantastic! Just Z00A for now?
Click to expand...
Click to collapse
I manually ran a z00a build to test the setup. Assuming all goes well, there will be a z008 build tomorrow.
kanagawaben said:
550 version doesn't seem to be up yet, unfortunately.
Click to expand...
Click to collapse
We weren't going to do the thread till tom but somebody found the test build.... It will come, but probably not till next nightly cycle
Sent from my N5206 using Tapatalk
crpalmer said:
I manually ran a z00a build to test the setup. Assuming all goes well, there will be a z008 build tomorrow.
Click to expand...
Click to collapse
Thank you! No rush at all, of course.
---------- Post added at 11:44 PM ---------- Previous post was at 11:42 PM ----------
jrior001 said:
We weren't going to do the thread till tom but somebody found the test build.... It will come, but probably not till next nightly cycle
Sent from my N5206 using Tapatalk
Click to expand...
Click to collapse
Ditto, my comment above. Absolutely delighted it is coming, and happy to wait a bit longer. Thanks for your sterling work guys!
jrior001 said:
Updates issues and notes on upgrading from cm-12.1 .
RIL connectivity is not very good right now, requires manual setup on most sims. Clean install w/gapps is preferred, but CM team goes to great lengths to make sure upgrade path is smooth so a flash-able update from 12.1 nightly "should " work fine. Just make sure to flash your gapps w/ROM prior to rebooting. Flashing gapps later is not something that is going to work well for you.
Click to expand...
Click to collapse
yeah, i got that sim problem, but choosing manually worked, flashing this rom with open gapps worked fine
Seutp wizard has closed. Keep getting g that message. Back to 12.1.
How install super SU?
Awesome
I formatted my sdcard1 over and over... but my zen can't access it.
Any reason why?
CyanogenMod 13.0 is a free, community built, aftermarket firmware distribution of Android 6.0.x (Marshmallow), which is designed to increase performance and reliability over stock Android for your device.
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
*/
CyanogenMod is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. You will need to provide your own Google Applications package (gapps). CyanogenMod does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for CyanogenMod is available in the CyanogenMod Github repo. And if you would like to contribute to CyanogenMod, please visit our Gerrit Code Review. Your changelog is whatever was merged into gerrit.
Other Issues Not in Known Issues?
Before posting on this thread, make sure of a few things:
You've utilized the search function of the forums. Nothing irritates me more than lazy people who do not search for an answer before asking or ask the same question over and over again.
If you are the only one having a problem. Boot into recovery, wipe data/factory reset, reflash the rom/gapps and nothing else. Boot up and see if the problem persists.
LOGS LOGS LOGS!!!! Use this: SysLog by Tortel
If you have a hard reboot (to the vendor boot logo, not the CM boot logo), use adb or any other file explorer tool to pull a copy of
/sys/fs/pstore/console-ramoops (command: adb pull /sys/fs/pstore/console-ramoops)
after the reboot and provide that.
Note: We will not support any kind of modification on the ROM not done by our sources. If you are running XPosed, Kernel Booster or whatever occurs to you, we won't support you in any way. The problem will in every case be treated as the additional softwares' fault (because often it is!)
Download Links
CyanogenMod: ROM @ http://download.crpalmer.org/nightlies/pme/
Google apps addon:
(Note: Not required to run the ROM)
We are using Open GApps (Link) Arm64 version. (make sure to use 64bit when using other packages), others might also be working
Note: In case you want to use any gapps, YOU MUST install the right gapps the first time that you flash a marshmallow ROM. Do not boot with an older gapps or without one and then try to install it later.
Note: If you install a package which replaces the default dialer (mostly "Stock Gapps") you have to go to Settings->Apps->Gear-Icon and set the new dialer as a default telephony app to prevent force closing of apps
Known Issues
Rear Camera Force Closes when enabling HDR
MTP not working
Magnet detection/Ice View not working
LED notification settings are available but don't work
SELinux is in permissive mode
Notification volume is too loud
?? Headphone volume is too loud? (I don't know what is normal on stock as I've never used them on stock...)
XDA:DevDB Information
CyanogenMod 13.0, ROM for the HTC 10
Contributors
crpalmer, squid2, raymanfx
Source Code: https://github.com/CyanogenMod/android_kernel_htc_msm8996
ROM OS Version: 6.0.x Marshmallow
Version Information
Status: Nightly
Created 2016-09-20
Last Updated 2016-11-05
Reserved
reserved
Thanks for thread and ROM.
Use Google Camera for front camera. Perfect running.
Gesendet von meinem HTC 10 mit Tapatalk
morpheus620 said:
Thanks for thread and ROM.
Use Google Camera for front camera. Perfect running.
Gesendet von meinem HTC 10 mit Tapatalk
Click to expand...
Click to collapse
That's good news!
Sent from my HTC 10 using XDA-Developers mobile app
Fyi I can't get the download link to work. It loops back to itself, asking me to choose which app to open it with over and over
@crpalmer ... You are a god among men. I saw why you posted this thread in another thread, and would like to thank you for the harm reduction measures on behalf of the whole community.
stonew5082 said:
Fyi I can't get the download link to work. It loops back to itself, asking me to choose which app to open it with over and over
Click to expand...
Click to collapse
I screwed up the link, fixed the op now I hope.
I hate to be that guy but does or will this boot on all variants? I.e. sprint, Verizon etc.
jmkarnai01 said:
I hate to be that guy but does or will this boot on all variants? I.e. sprint, Verizon etc.
Click to expand...
Click to collapse
I've been told it boots and functions if you flash the latest US Unlocked firmware, minus the radio.
Captain_Throwback said:
I've been told it boots and functions if you flash the latest US Unlocked firmware, minus the radio.
Click to expand...
Click to collapse
Didn't really want to mess with firmware being on sprint and all, but maybe I just need to dive right in. One question, how will that affect me going back to sense?
jmkarnai01 said:
Didn't really want to mess with firmware being on sprint and all, but maybe I just need to dive right in. One question, how will that affect me going back to sense?
Click to expand...
Click to collapse
It might have no effect at all. I'm not on Sprint, so I'm not the person to ask.
Using MultiRom to boot the 0920 snapshot. Home button does not function as home. I press it and it doesn't go home. Is this because of Ex kernel I am using at the top level in MultiRom? I remember someone having this trouble with Ex kernel and CM.
Does someone remember having patch I can apply on top of Ex kernel (I am building it myself) to get this working? I remember it was a single line patch.
devsk said:
Using MultiRom to boot the 0920 snapshot. Home button does not function as home. I press it and it doesn't go home. Is this because of Ex kernel I am using at the top level in MultiRom? I remember someone having this trouble with Ex kernel and CM.
Does someone remember having patch I can apply on top of Ex kernel (I am building it myself) to get this working? I remember it was a single line patch.
Click to expand...
Click to collapse
Yeah the kernel causes this. Not sure about the patch sadly
devsk said:
Using MultiRom to boot the 0920 snapshot. Home button does not function as home. I press it and it doesn't go home. Is this because of Ex kernel I am using at the top level in MultiRom? I remember someone having this trouble with Ex kernel and CM.
Does someone remember having patch I can apply on top of Ex kernel (I am building it myself) to get this working? I remember it was a single line patch.
Click to expand...
Click to collapse
You can try elitekernel. It's based on EX and he has patched the home button as well.
Edit: I guess this was the change
https://github.com/Elite-Kernels/HTC-10/commit/defb8a468268f757c5ce3ddf7c09ff4738282e9c
Hi, can you post any changelog when you upload a new build please? just a .txt file with same name in order to know what's new on each build
Thanks
fabiere said:
Hi, can you post any changelog when you upload a new build please? just a .txt file with same name in order to know what's new on each build
Thanks
Click to expand...
Click to collapse
Hey buddy,
For the changelog Mr. Palmer has mentioned to go to Gerrit (http://review.cyanogenmod.org/)
The specific section for HTC 10 changes are as follows (http://review.cyanogenmod.org/#/q/project:CyanogenMod/android_device_htc_pme).
It will be easier to look there as if will have all the relevant changes you need. He may look to put up a change log when we are closer to or at a stable build.
Sent from my HTC 10 using XDA Labs
rav101 said:
Hey buddy,
For the changelog Mr. Palmer has mentioned to go to Gerrit (http://review.cyanogenmod.org/)
The specific section for HTC 10 changes are as follows (http://review.cyanogenmod.org/#/q/project:CyanogenMod/android_device_htc_pme).
It will be easier to look there as if will have all the relevant changes you need. He may look to put up a change log when we are closer to or at a stable build.
Sent from my HTC 10 using XDA Labs
Click to expand...
Click to collapse
Ok thanks, sorry i haven't understand this correctly, thanks for your explanations
Hi.
can I dirty flash that over Captain_Throwbacks CM13 build?
Hello, this ROM for which version of HTC 10 is compatible?
perfume_uhl, perfume_whl or perfume_wl?? Thanks you very much!
LineageOS is a free, community built, aftermarket firmware distribution of Android 7.1 (Nougat), which is designed to increase performance and reliability over stock Android for your device.
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
*/
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. You will need to provide your own Google Applications package (gapps). LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit our Gerrit Code Review. Your changelog is whatever was merged into gerrit.
Important information:
This thread is for official LineageOS 14.1 builds for LG G4 . The following will not be supported here:
Custom kernels
Mods
Xposed
We don't support Xposed and any logcat which includes a Xposed module will be ignored. You're kindly invited to not report bugs if you:
Flashed a custom kernel
Installed or did mods from untrusted sources
Modified system files
Known bugs:
Video Recording
Installation:
First time flashing LineageOS 14.1 on your device, or coming from another ROM?
Download the zip(s)
Install a compatible Recovery
Perform a nandroid backup of your current ROM (Optional)
Wipe data/factory reset
Flash LineageOS
Optional: Install the Google Apps addon package, install the SU addon package(https://download.lineageos.org/extras, choose arm64)
Reboot
Download:
h815: https://download.lineageos.org/h815
h811: https://download.lineageos.org/h811
personnal nightlies http://host.erwanleboucher.fr/
XDA:DevDB Information
CM 14 on LG G4, ROM for the LG G4
Contributors
genesixxbf3, codeworkx
Source Code: http://github.com/CyanogenMod
ROM OS Version: 7.x Nougat
ROM Firmware Required: V20A Bootloader and modem
Version Information
Status: Beta
Created 2016-10-10
Last Updated 2018-01-28
Reserved
What's working.
everything except what's not working.
What's not working ?
encryption (who use that )
f2fs (who use that too )
QHD video recording
official = signed
unofficial = no signed
to go to unofficial to official flash experimental first (and boot it)
Reserved
If you don't have a sim card detected try that
Code:
adb root
adb shell rm /data/user_de/0/com.android.providers.telephony/databases/telephony.db
adb shell rm /data/user_de/0/com.android.providers.telephony/databases/mmssms.db
adb reboot
Nice job mate! Thank you!
Everythink work ??? no bug ? no issues ? theme engine work ?
yes i know Nougat is too Young for Stable custom Rom at this moment but hope
What doesn't work? if you dont mind me asking?
Awesome work, thanks Genesixx
If there are known issues I am sure the OP will update the first post. You can also flash it and post if you find anything, just don't forget to make a full backup first ????
How is the camera on this build?
Op says you should flash gapps 6.0, is this right?
ashensii said:
Op says you should flash gapps 6.0, is this right?
Click to expand...
Click to collapse
7.0 gapps
to see what's not workin check second post
wow excellent work!
Is this stable enough to use as a daily driver?
ceanth said:
wow excellent work!
Is this stable enough to use as a daily driver?
Click to expand...
Click to collapse
It is
Was running the 10-05 build for several days. I find it works just as good as CM13, possibly better (smoother/faster). Bugs are very minimal, features are too but overall this is a very stable and solid build so far!
THANK YOU @genesixxbf3 for bringing this to us! I don't really like CM13, but 14, something about it is very nice (coming from someone that prefers stock over aosp).
EDIT: It should be posted that H811 users need to be on 20o FW before flashing this, to make sure they get best experience (if you want sound/camera working).
EDIT2: Oh and now there is a thread for me to report: Zooming with standard gallery hot-reboots the phone.
theslam08 said:
It is
Was running the 10-05 build for several days. I find it works just as good as CM13, possibly better (smoother/faster). Bugs are very minimal, features are too but overall this is a very stable and solid build so far!
THANK YOU @genesixxbf3 for bringing this to us! I don't really like CM13, but 14, something about it is very nice (coming from someone that prefers stock over aosp).
EDIT: It should be posted that H811 users need to be on 20o FW before flashing this, to make sure they get best experience (if you want sound/camera working).
Click to expand...
Click to collapse
thanks, i might flash it tonight then. Should 815 users also be on stock rom before flashing this? I am currently on v20d stock rom
ceanth said:
thanks, i might flash it tonight then. Should 815 users also be on stock rom before flashing this? I am currently on v20d stock rom
Click to expand...
Click to collapse
Unfortunately I am not sure about the h815. With the h811 we had a recent issue where we had to be on the latest FW for it to fully work.
I would 'assume' it would be the same for you. May wish to wait for 815 users to report back which FW they're on and how it all works for them.
(and you don't have to actually be running the stock ROM before flashing this, the firmware is a once-flash-always-flashed type situation; firmware is not ROM based it stays between ROMs)
ceanth said:
thanks, i might flash it tonight then. Should 815 users also be on stock rom before flashing this? I am currently on v20d stock rom
Click to expand...
Click to collapse
v20A or newer. So you are fine. Before flashing you don't care what rom you are on. You just need to wipe system , data , cache and dalvik cache and flash whatever you like.
kessaras said:
v20A or newer. So you are fine. Before flashing you don't care what rom you are on. You just need to wipe system , data , cache and dalvik cache and flash whatever you like.
Click to expand...
Click to collapse
ok great.
I'll give it a go and report back with feedback to the group
ceanth said:
ok great.
I'll give it a go and report back with feedback to the group
Click to expand...
Click to collapse
(out of subject)
I wonder how do you live with the stock rom on G4
You charge the phone 2 times per day ? haha
The stock rom has issues and it doesn't let the phone get into doze.
Have fun flashing you will never wanna go back to stock again
kessaras said:
(out of subject)
I wonder how do you live with the stock rom on G4
You charge the phone 2 times per day ? haha
The stock rom has issues and it doesn't let the phone get into doze.
Have fun flashing you will never wanna go back to stock again
Click to expand...
Click to collapse
Haha. I flashed stock rom because I wanted to use Android Pay. There is a deal on in the UK where by you get free London Underground travel on Mondays throughout October.
I was planning on flashing something else after the offer is done but Android Pay failed to work this morning causing a massive queue behind me I have had enough of it!
ceanth said:
Haha. I flashed stock rom because I wanted to use Android Pay. There is a deal on in the UK where by you get free London Underground travel on Mondays throughout October.
I was planning on flashing something else after the offer is done but Android Pay failed to work this morning causing a massive queue behind me I have had enough of it!
Click to expand...
Click to collapse
Hmmm. I don't use android pay but I read somewhere that you can use it with cm 14 or 13 if you use an official and stable build , not nightly or unofficial , and disable superuser in developer settings.
Of course I don't know if that's true
Code:
/*
* Your probably long dead 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.
*/
LineageOS is a free, community built, aftermarket firmware distribution of Android 7 (Nougat), which is designed to increase performance and reliability over stock Android for your device.
This thread is organized into different posts so that people dont quote the whole OP.
Please read all the posts and updates, before flashing.
Changelog Summary:
For full changelog follow the link.
#FINAL: 28 Jan 2018
Repo synced with latest LineageOS 14.1 sources.
Updated system webview to 64.
Added postinstallzip due to kernel not being flashed.
Added Magsik 15.3 support in ramdisk.
#4: 14 Nov 2017
New feature: UA:CMA
Added back Device Settings.
#3: 14 Nov 2017
Switched to a more stable kernel with improvments
Fixed Camera
Fixed Bootanimation
#2: 12 Nov 2017
Enabled OpenGLES 2.0
Fixed Audio/Video Playback.
Fixed Webview.
#1: 11 Nov 2017
Initial build.
Latest Download:
You need to flash lineage-14-postinstall.zip after installing the ROM, or else it wont boot.
For some reason ramdisks arent being flashed.. and I cant be bothered to figure out why..
lineage-14.1-20180127-UNOFFICIAL-galaxysmtd.zip
lineage-14-postinstall.zip
Older builds
#4 lineage-14.1-20171117_140654-UNOFFICIAL-galaxysmtd.zip
#3: lineage-14.1-20171114_062105-UNOFFICIAL-galaxysmtd.zip
#2: lineage-14.1-20171112_085706-UNOFFICIAL-galaxysmtd.zip
#1: lineage-14.1-20171111_094959-UNOFFICIAL-galaxysmtd.zip
XDA:DevDB Information
GalaxyS1 Resurrected Nougat Project, ROM for the Samsung Galaxy S I9000
Contributors
(°_o), ColdwindOfnowhere, xc-racer99
ROM OS Version: 7.x Nougat
Based On: LineageOS
Version Information
Status: Beta
Created 2017-11-11
Last Updated 2017-11-14
XDA:DevDB Information
GalaxyS1 Resurrected Nougat Project, ROM for the Samsung Galaxy S I9000
Contributors
(°_o), ColdwindOfnowhere, xc-racer99
ROM OS Version: 7.x Nougat
Based On: LineageOS
Version Information
Status: No Longer Updated
Created 2017-11-11
Last Updated 2018-01-28
Working List:
Boots
RIL (SMS, Call)
WiFi
Audio/Video Playback (fixed in build#2)
Camera Pictures (fixed in build#3)
Not Working List:
RIL Data
FAQ:
Dont install too many apps obviously
The first boot should be faster than previous nougat roms.. Since I have now used pre-odexed /system.
Known Issues:
Lagginess ofc, due to our device being old
Sometimes SystemUI gets killed due to low memory and we get Black Screen of Death
Install Instructions :
[WARNING]:
You must be already on at least Lollipop/Marshmallow ROM and have latest TWRP 3.1.1.
You must format /data as f2fs in TWRP.
Bootanimation is working since build #3.
You should already been familiar with flashing custom ROMs before.
And know how togo from gingerbread -> nougat.
Please check other threads for that..
If someone wants to contribute install instructions for this ROM.
I will be happy to add here and give credits.
Gapps
I havent tested GAPPS.. but I can guess the performance will be horrible with it.
However, I have included the patch for microG GmsCore signature spoofing. So you could try that.
Additional Info:
Built from latest LineageOS 14.1 Sources.
Latest kernel from @xc-racer99 aosp-7.1 branch
Live wallpapers, LineageOS Updater, Weather Service removed for low memory footprint.
Reserved.811919
Reserved.224232
Credits:
@xc-racer99 and @Coldwindofnowhere for getting the device upto android 7.1.1
And all others who had worked from beginning till now on this device.
Sources
Galaxy S1 Resurrected: Project Nougat
Device Trees:
https://github.com/galaxys1-resurrected/
https://github.com/galaxys1-nougat
Kernel:
https://github.com/galaxys1-resurrected/android_kernel_samsung_aries
I'm delighted that there's still someone who is working on this device. I'll be appreciated to wait for a more stable version of nougat.
The rom is indeed quite stable.
However, Webview doesn't seem to work. I think you should take a look here.
Also, built-in root with the Su-addon doesn't work.
And flashing a Magisk or SuperSu zip (made by @xc-racer99 ) resulted in a bootloop, but I was able to access the recovey.
MYEUHD said:
The rom is indeed quite stable.
However, Webview doesn't seem to work. I think you should take a look here.
Also, built-in root with the Su-addon doesn't work.
And flashing a Magisk or SuperSu zip (made by @xc-racer99 ) resulted in a bootloop, but I was able to access the recovey.
Click to expand...
Click to collapse
Expect lot of stuffs dont work at the moment.. listed in Not working.
About webview I will try to replace it.
Magisk and SuperSu try to patch boot.img and ramdisk.. and our device uses a very hacky way to load ramdisks.
I will create a patched ramdisk with latest Magisk then..
This has to be the fastest Nougat ROM I've flashed on this phone! Thanks for keeping this amazing phone alive. Can't wait to see it become more stable in the future
Full changelog: build #2
Fixed Audio/Video playback
I had to remove ffmpeg codecs as they were causing hardware decoding to not work.
Hardware decoding is working fine and 720p playback is smooth too..
I've tested without bigmem mode.. I havent implemented bigmem libs for 720p playback.
So please try without bigmem before reporting issues with it.
Fixed Webview
AOSP Webview was somehow not working on our device.. as pointed out by @MYEUHD
The solution he linked was to revert to older webview.
But that is outdated and unsafe so I tried with latest Android System Webview.
It seemed to work so I set it to default.
I havent tried but we can also use Chrome as our Webview..
Switched to OpenGL 2.0
We were stilling using OpenGL 1.4 for rendering.. this shouldnt affect much.. but animations should be smoother
Since we no longer get Shader errors with OpenGL 2.0
Let me know if you find any difference performance wise compared to build #1.
Downloads are in OP.
Status Update:
Project discontinued.
Status Update:
You can skip this paragraph if are not intrested in my long story cut short.
So I have been trying to fix stuffs which means.. rebuilding and flashing the ROM.
Wiping data .. getting logs.. testing if something works.. Repeat
I hadnt really used my Galaxy S1 phone.. It was just lying around a corner of my table getting dust.
Until one day I thought, let's build Oreo for this old time phone.. turns out the battery was RIP due
to not charging it for so long.. so I got a replacment battery then booted to see cm-14.1 build by
Coldwindofnowhere and missing IMEI which I sucessfully restored after creating a thread here.
Again thanks for that to @xc-racer99 and @MYEUHD
So I started out device trees and repos based on Coldwindofnowhere and xc-racer99
and made it compatabile with Oreo. And thanks to rInanD0 I was able to pick stuffs necessary on
kernel side.
Then me and @xc-racer99 discussed some stuff and I picked changes from Unlegacy-Android gerrit to properly do some stuff.. I fixed lots of stuffs.. but I couldnt get the display to initialize... so I decided
to wait for Unlegacy-Android for their take on Galaxy Nexus which shares same GPU as us to bring up Oreo first.
In the mean time, I thought again.. why not build Nougat for now.. so I again setup device tree and repos for
nougat. and we are here..
Okay so I havent really used my Galaxy S1 let alone this ROM.
This ROM does seem fast while moving around just after a first boot.
And really I hadnt installed or used any apps besides the one that came with LineageOS.
But today while trying to fix Camera, I had to actually take photos. Oh, and the reason camera was not working
was due to I had disabled building of Camera HAL in Oreo which stuck around... big derp
So camera preview was working now.. Snap camera wasnt savinf photos at first..
so I thought to install Open Camera.. I installed F-Droid.. then Open Camera..
Then I clicked some photos which seemed to be saved.
There were a lot of photos created so I decided to delete them.
But Files app wasnt deleting them.. must be a permission issue?
So i installed a file manager from F-Droid and deleted the photos.
Good enough.. then I thought I need to download these apps again after a data wipe..
Lets backup them.. so I installed an apk backup again from F-Droid.
While it was downloading.. BAM Screen went all BLACK.
I tried clicking home button but nothing.. then I clicked power button nothing.
Then I hold power button.. i got the options...
Now I was reminded of this bug which has been around since Lollipop? or Marshmallow days..
Screen going all black.. back then Coldwindofnowhere predicted it might due to out of memory issues..
And he is right.. I had adb running so I checked free memory and swap.. The swap file was and memory was nearly full.
I checked dmesg for logs... then I saw lowmemorykiller killing all kinds of stuff.. but there was only one time it killed this..
Code:
lowmemorykiller: Killing 'system:ui' (5642), adj 902,
And thats the reason for the black screen.. Now we all know this device doesnt have much memory.
So the option would be to not install many or any apps.. on this option..
Ofcourse I could try to get CMA working properly.. which adds just around 70-80mb I guess..
And we could just white list system ui to not get killed.. but then it would kill other important processes..
So I've decided to stop working on Nougat. I dont wanna give people false hope of *stable* nougat.
I will still upload a build with Camera fixed.. Well video recording still doesnt work.. Looking at logs.. i need to resurrect
the old way of video buffer. which got removed in Nougat.
And while Project Nougat is offically discontinued, Project Oreo is still alive just paused.
I will at least get Oreo bootanimation on this device.
Thanks for trying out this short lived nougat ROM.
Full changelog: build #3
Switched kernel from @Coldwindofnowhere to @xc-racer99
I think xc-racer99 kernel has better memory management. since the lowmemory killer doesnt kill many processes..
However I did make some changes to it.
Disabled CMA
Enabled and set zRAM to 1/4 of total memory
Some kernel build optimizations.
Note that.. this kernel doesnt have BigMem Support so wer'e stuck with 383MiB ram for now.
Fixed Bootanimation
Yeah.. that was a my mistake.. err..
At least you know its booting now.. but since we use pre-odexed ROM first boot shall be done in 5 minutes now..
Fixed Camera
Taking pictures should work now. Video recording is broken.. It needs to updated for Nougat..
Added Magisk in ramdisk
Latest version 14.0. Just install magisk manager AND DONT TRY TO PATCH BOOT.IMG..
We use very differnet system for boot.img and ramdisks..
I will try to update Magisk to latest version.
Fixed a big mistake in updater
https://github.com/galaxys1-nougat/...mmit/a6f51178503a01f6b1e7b0c8222e875392af8a8e
Flashing boot.img would actually result in wiping it in some cases..
If you had troubles installing this ROM or any ROMs in the past.. this might be the case..
The flash over mm dont work for me i have an error 7 i try to reflash and now no twrp i need to restore via odin any help?
laharl_22 said:
The flash over mm dont work for me i have an error 7 i try to reflash and now no twrp i need to restore via odin any help?
Click to expand...
Click to collapse
Error 7 is assert error... which I guess is coming from updater script..
You dont need to restore whole stock ROM..
I have built a twrp only recovery image... so you can just straight boot to recovery after Odin..
You can also flash recovery.img from heimdall .
https://drive.google.com/drive/folders/1KthyR6QWPswaIT8fw2nbiR4fathP-QU0?usp=sharing
How is this Rom compared to the LineageOS 4.4.4?
LuckyK
The Kernel for any ROM
LuckyK was born from the desire to keep a device on line as per the parent company, and my job is to keep it as clean as possible and suitable for android. I'm back working on the kernels after 5 years of stop, my first device was the Galaxy Nexus, where I learned a lot of things about this world, but most important of all, is that keeping a clean job, the kernel boot in any rom.
Click to expand...
Click to collapse
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
*/
Click to expand...
Click to collapse
This is how I present to you, LuckyK the kernel for any rom, at the moment it works really well on LineageOS-17.1, but as the same @z3DD3r says, if I boot on LOS-17.1, also on LOS-18.1 he will boot quietly, but still I'm not sure about this, in days I will try it personally, but if anyone wants to precede me try it and let me know if I boot on LOS-18.1 or other rom android-11.
The kernel is stable, at the moment I have not found any bugs to mention.
Basically he runs in stock as on Kitkat in:
CFQ
Ondemand
The Zram has been added, but only the Zpool and the CleanCache are active, let's say it's a small hack, because if we activate the Zram, after some use the device starts to be slow, because it allocates the pages only in the mmc memory, without using the Ram anymore, so instead, it allocates the extra pages on the mmc, but uses the Ram to govern them, and therefore transforms itself into maximum responsiveness of the device
Downloads:
See the first post, for attached files...
Source Code:
Commits · Fenix46/Kernel-hammerhead
Contribute to Fenix46/Kernel-hammerhead development by creating an account on GitHub.
github.com
Contributors:
@Fenix46 @z3DD3r
Kernel Version: 3.4.0
Android Version: 10 / 11?
Status: Stable
Reserved
hello , thank for the work , i tested on crdroid a11 but don't boot .
Mmm how I think... Kernel will the related commit for android 11... Tomorrow I will update it... Thank's for the reply
Wi-Fi seems to not be working... I tried your kernel on LOS 17.1.
snow said:
Wi-Fi seems to not be working... I tried your kernel on LOS 17.1.
Click to expand...
Click to collapse
mmm are you sure?? I have been try it 2 days, and work's great wifi, maybe is the bug mentioned on LOS 17.1 theard
About Wi-Fi
When I flash this kernel
It works with linage-17.1-20201231-UNOFFICIAL-hammerhead.zip
Does not work with linage-17.1-20210416-UNOFFICIAL-hammerhead-signed.zip
Thank you for your work.
Fenix46 said:
mmm are you sure?? I have been try it 2 days, and work's great wifi, maybe is the bug mentioned on LOS 17.1 theard
Click to expand...
Click to collapse
Yup, it doesn't work with latest build posted by z3DD3r (20210416).
Thank's guys to reportely this to me... I will fix it soon... at the moment, I'm work on port k3.10 on hammerhead, and I don't try the new build...
Fenix46 said:
LuckyK
The Kernel for any ROM
This is how I present to you, LuckyK the kernel for any rom, at the moment it works really well on LineageOS-17.1, but as the same @z3DD3r says, if I boot on LOS-17.1, also on LOS-18.1 he will boot quietly, but still I'm not sure about this, in days I will try it personally, but if anyone wants to precede me try it and let me know if I boot on LOS-18.1 or other rom android-11.
The kernel is stable, at the moment I have not found any bugs to mention.
Basically he runs in stock as on Kitkat in:
CFQ
Ondemand
The Zram has been added, but only the Zpool and the CleanCache are active, let's say it's a small hack, because if we activate the Zram, after some use the device starts to be slow, because it allocates the pages only in the mmc memory, without using the Ram anymore, so instead, it allocates the extra pages on the mmc, but uses the Ram to govern them, and therefore transforms itself into maximum responsiveness of the device
Downloads:
See the first post, for attached files...
Source Code:
Commits · Fenix46/Kernel-hammerhead
Contribute to Fenix46/Kernel-hammerhead development by creating an account on GitHub.
github.com
Contributors:
@Fenix46 @z3DD3r
Kernel Version: 3.4.0
Android Version: 10 / 11?
Status: Stable
Click to expand...
Click to collapse
Give me a link for a donation .
You are now a Hero..
I don't have an account for donation.. sorry :/ ... I appreciate the support from community
Good Morning community, at least, we have a booted aosp-kernel 3.10 on TWRP.... is a very good news... I have fixed the display, and now booted fine on TWRP.. but need yet fixes for usb and for display wake up...
if anyone will help, the branch is this https://github.com/Fenix46/Kernel-hammerhead/commits/test2
Good morning comminity, usb is fixed.... now debug is more simple for anyone...
storage work's also fine. in recovery, in android won't boot but I have a first logcat... if anyone will help
logcat 3.10 - Pastebin.com
Pastebin.com is the number one paste tool since 2002. Pastebin is a website where you can store text online for a set period of time.
pastebin.com
community, we have a bootable k3.10... now needed update for stability and then for newer android version