Disclaimer
Your warranty is now void!
You will be doing everything at your own risk.
I am not responsible for bricked or damaged devices.
What's working
Mostly everything
How to install
1. Wipe system, data and both cache partitions
2. Install the ROM + GApps
3. Wipe again both cache partitions
4. Now you can boot to the system
Download
Unofficial LineageOS 14.1
opengapps
Sources
github.com/sgspluss
Credits and Thanks
@sgspluss @Konstantinosj77 @galaxyfreak
Changelog
Code:
[B]lineage-14.1-20180721-UNOFFICIAL-eagle.zip[/B]
Sync with latest LineageOS sources
Some other device and kernel stuff
[B]lineage-14.1-20180626-UNOFFICIAL-eagle.zip[/B]
Add increase wlan network scan interval
Add and enable wakelock blocker
Clean up system.prop a bit
Sync with latest LineageOS sources
Some other device and kernel stuff
[B]lineage-14.1-20180620-UNOFFICIAL-eagle.zip[/B]
Initial release
Troubleshooting
Playstore show not certified
Try to clean app data and cache first, if its not working for any reason read this
https://www.xda-developers.com/how-to-fix-device-not-certified-by-google-error/
Low RAM Configuration
Add the four lines into your build.prop with any rootexplorer you want, save it and restart your phone to activate them.
Code:
# Low memory device
ro.config.low_ram=true
# Force high-end graphics in low ram mode
persist.sys.force_highendgfx=true
If you need more information read this
https://source.android.com/devices/tech/perf/low-ram#intro
Just ask to be sure, is anyone interessed to get updates for this rom?
If not will take the ressources to build an other rom...
Sent from my athene using XDA Labs
[ROM][8.1.0][eagle] Unofficial LineageOS 14.1
is it oreo or nougat??
I see you are building a lot of roms, thats really nice M2 is alive again.
but I recommend that you stick with 1 build until it gets stable and start with next one.
all the best bud.
Its lineage 14.1 meaning nougat, just typo failture in titel.
I have build this as fallback because its at the moment stable, while oreo need more work.
Also to build more as one rom is no problem, because the bugs are the same and if i've fixed them in one rom, they also will be fixed in all other. The main working place is lineage, all other roms are just because its possible.
Sent from my athene using XDA Labs
I'm a noob.
I like this version, although it's the only unofficial one I've tried. Please choose the variant you think is the best one.
Thanx again!
Here we will stay unoffical, its easier to maintain it.
Update will comes time by time, but focus is now on lineage 15.1 since 14.1 is stable.
That's nice to know; useful info.
Thanx.
New update is out...
If you want to know whats new, read post #2 https://forum.xda-developers.com/showpost.php?p=76872447&postcount=2
The problem with los14.1 is when enabling low ram flag, animations becom very lagy, can you do something about that?
Afaik but not sure, you can build any 4.4+ rom that support low ram flag new animations, but you must follow some steps to make it compatible.
This is what what I thought after reading @AdrianDC 's thread about low ram flag.
If my informations are wrong, please let me know right ones.
If animation thing can be fixed, I'll stick with nougat to the rest of my life.
Thank you.
You can try to add this two lines into the build.prop
# Low memory device
ro.config.low_ram=true
# Force high-end graphics in low ram mode
persist.sys.force_highendgfx=true
The first disable it, it disable all heavy ram features, the second enable high graphic features.
Sent from my athene using XDA Labs
sgspluss said:
You can try to add this two lines into the build.prop
# Low memory device
ro.config.low_ram=true
# Force high-end graphics in low ram mode
persist.sys.force_highendgfx=true
The first disable it, it disable all heavy ram features, the second enable high graphic features.
Click to expand...
Click to collapse
i tried this on 8.0, and here is the result; phone became so laggy and there is black everywhere (well thats what i expected) but second flag does not do anything at all
Its OT here, but which version are you are unsing of my oreo with build date, then i can tell you more why it doesnt work.
For nougat its working fine, just add it now into the build.prop and overall animations are fine so far, also transparency is given so all high grafic features are enabled while heavy ram things are disabled.
sgspluss said:
Its OT here, but which version are you are unsing of my oreo with build date, then i can tell you more why it doesnt work.
For nougat its working fine, just add it now into the build.prop and overall animations are fine so far, also transparency is given so all high grafic features are enabled while heavy ram things are disabled.
Click to expand...
Click to collapse
oh i understand, it is kj77's lineage 15.0 alpha 2 build. i will give a shot to this rom thanks for responding.
also i am curious, do you add special code when you build to prevent these issues?
With kj's 15.1 you just need to add persist.sys.force_highendgfx=true because the first one is already build in due to go optimization.
If you are using my latest 15.1 goedition you need to add ro.config.low_ram=true the second one is already build in.
Last but not least if you are unsing my latest 15.1 unoffical build you need to add both into your build.prop.
kj does build without jack that causes timekeeping and telephony problems, while i complie with jack.
Apart of this and my optimizations and fixes, there are no differences because both 14.1 and 15.1 based on his given sources.
sgspluss said:
With kj's 15.1 you just need to add persist.sys.force_highendgfx=true because the first one is already build in due to go optimization.
If you are using my latest 15.1 goedition you need to add ro.config.low_ram=true the second one is already build in.
Last but not least if you are unsing my latest 15.1 unoffical build you need to add both into your build.prop.
Click to expand...
Click to collapse
yeah i know these, but i am using android 8.0, which has not go property built in. i am curious how you made it to 7.1
Ah if you using alpha 2 you need to add both, sorry did not read that befor, my fault.
I did not build that in, its an feature since kitkat times so the code is given you just need to activate it.
Since oreo you have the option to build the rom with go optimization by default, but also here the code is given just need to activate it.
Why its not working can not say, to be honest, did not test early alpha builds.
Thank you.
I will try adding those lines as soon as I get my device from repair service.
If anyone will confirm that the both lines (you need to add them manually into the build.prop)...
# Low memory device
ro.config.low_ram=true
# Force high-end graphics in low ram mode
persist.sys.force_highendgfx=true
...are working and makes things better, then i will add them for next update. Also volume problem is fixed, thanks @JuniorCaesar for the hint.
Sent from my athene using XDA Labs
Related
Overview:
Code:
[B]Experimental CyanogenMod 12.1 compiled with [URL="http://releases.linaro.org/14.10/components/android/toolchain/4.9"]Linaro 4.9 (14.10) Toolchain[/URL].[/B]
This is CyanogenMod 12.1 built straight from source with Code Review
cherry-picks and my own custom device trees and kernel.
CDMA carrier setup:
The following only needs to be done once to allow init to properly setup your carrier specific system properties.
This will set ro.boot.carrier to your specific carrier identifier and will persist through future flashes of this ROM.
Code:
From the bootloader issue the following commands depending on your carrier:
'fastboot oem config carrier verizon' (Verizon)
'fastboot oem config carrier pageplus' (Page Plus)
'fastboot oem config carrier reliance' (Reliance Mobile)
'fastboot oem config carrier sprint' (Boost Mobile)
Builds:
CM-12.1 06-08-2015 (MD5: (2414f09586228eb94bcda47c1f149ed0)
MMS Flashable Zip Fix Thanks @starkly_raving @Alberto97
TK Gapps Mini Modular 5.1 (05-30-2015)
Build Archives
Source Code:
codyf86/android_device_motorola_falcon
codyf86/android_device_motorola_msm8226-common
codyf86/android_kernel_motorola_msm8226 (Stock CM kernel Not even stock anymore kernel xD)
Code Review Cherry-Picks: (Latest build)
healthd: Use android blue for charge percentage
PowerManagerService: Fix updating of mUserActivitySummary
Add option to set default custom function to button recents (1/2)
Add option to set default custom function to button recents (2/2)
cmsdk: do not crash system if CustomTileListenerService isn't present
Note: When Items drop off the above list 9/10 they have been merged.
Changelog:
Code:
I don't believe in change logs; I believe in Github.
Please look above at the Code Review and also through
the source code commits to see what's changed.
The proof is in the [STRIKE]pudding[/STRIKE] Github.
Nice man ... Will be giving this a shot. Do you have a bug tracker set up or do you want logs and reports posted here?
Yummy. Also trying this out for sure.
Edit: Sub'd, Muuahahaha!....Oh.
starkly_raving said:
Nice man ... Will be giving this a shot. Do you have a bug tracker set up or do you want logs and reports posted here?
Click to expand...
Click to collapse
Feel free to post logs / bugs here. Mainly have time to build after work on weekdays. On the weekends is when I can actually work on fixing things.
For device specific things just post the bugs / logs here. For CM specific bugs I would use JIRA and post a link to the bug here. (More helpful/useful to the CM team to make an actual JIRA bug report.)
3 WORDS: STABLE AS ****!
thanks for the rom, this will forsure be my daily driver. only little problem is the no service icon (xt1031) but data is working. soft reboot fixes it though!
Can anyone please comment on the speed of this ROM since it is Linaro based? The other 5.1 ROMs on my phone are pretty responsive, but if even more speed can be gained with our limited hardware, that will be great.
@CodyF86,
Having a problem with the download link. Rom starts downloading but does not download the whole 251mb. Only partial download. Tried about ten times but still same result. Tried with a different browser but same result.
Edit: Nevermind. Downloaded the rom from my phone and copied it from download folder on phone to internal storage.
Hello there @CodyF86 ! Thanks for you work! One little request. Do you think you will be able to add a mirror or upload your work to another claudbased storage? Like MEGA or Mediafire or AndroidFileHost or whichever you want. This one you are using is insanely unstable for me. It gets interrupted every 5 minutes. I'll be really glad if you could change it or add other(s).
Cheers.
I'll upload to Google drive starting tonight also. Driving home from work, will do another one.
CodyF86 said:
I'll upload to Google drive starting tonight also. Driving home from work, will do another one.
Click to expand...
Click to collapse
Thank you very much! And sorry for bothering you with this. I really want to test your ROM since al Linaro builds seem gone from this forum. Thanks again. Drive safe
Cheers.
New build posted. Main link is to Google drive now.
Some more ARM assembly fun if you look under the kernel source commits.
Will fix the signal indicator so you don't have to do a soft reboot for it to work this weekend. Need to go through the soak test build.prop and compare a few other things...just need time this weekend.
CodyF86 said:
New build posted. Main link is to Google drive now.
Some more ARM assembly fun if you look under the kernel source commits.
Will fix the signal indicator so you don't have to do a soft reboot for it to work this weekend. Need to go through the soak test build.prop and compare a few other things...just need time this weekend.
Click to expand...
Click to collapse
thanks for both: new link and new build Can I dirty flash it over the build before? Just installed the first release lol
Cheers.
I've been dirty flashing; should be good to go.
Update: yes, this ROM is very fast indeed! Thanks for sharing.
This ROM is very fast! Especially for a CM ROM (which in my experience have gotten horribly slow over the last few versions) I haven't experienced nearly as many redraws, stutters, freezes or any other general unpleasantness. Good job @CodyF86
starkly_raving said:
This ROM is very fast! Especially for a CM ROM (which in my experience have gotten horribly slow over the last few versions) I haven't experienced nearly as many redraws, stutters, freezes or any other general unpleasantness. Good job @CodyF86
Click to expand...
Click to collapse
Same here. great work! Not as many customizable like other 5.1 based out there, but is enough fast and stable. Thanks.
just wondering what recovery you are using and do partitions need changed from stock?
What models are supported?
@CodyF86
thanks for your work!
I've a strange bug on last cm...every time i reboot time and data change and the year switch to 2025. I've read its time_daemon related bug...can you control? I've this issue with last cm12 builds
Shawnsch said:
just wondering what recovery you are using and do partitions need changed from stock?
Click to expand...
Click to collapse
CWM 6.0.5.1 I think 6.0.4.7 is the last one posted on CMs website, I'll post the latest one in the OP tonight, but they're basically the same. Nothing needs to be changed from stock.
Orjakone said:
What models are supported?
Click to expand...
Click to collapse
Theoretically they all should work, but I need someone to the GSM version to try it out.
The_Poison said:
@CodyF86
thanks for your work!
I've a strange bug on last cm...every time i reboot time and data change and the year switch to 2025. I've read its time_daemon related bug...can you control? I've this issue with last cm12 builds
Click to expand...
Click to collapse
Weird, I haven't noticed that, but tbh I haven't actually payed attention to what year my phone shows / I don't even have it set up to show me I'll have to look and see if mine does it also.
Will do another one tonight / it's the weekend can play around with it get some things done now.
Preamble
Hey everyone!
Xiaomi JUST released their source on 17/5/17 for mm. THAT IS SO DAMN COOL, THE WAIT IS FINALLY OVER. You guys can expect a custom kernel from me sooner or later(i'm busy). However, if the custom kernel really comes out from me, it won't be on this thread. This thread will maintain active development though, repacks of other custom kernels!
What is a repack? A repack is essentially, in layman terms, porting a kernel. I can run a kernel for AEX on RRN and stuff like that, but please do take note that my repacks are tweaked towards battery life, while keeping some speed. I might add bonus scripts in future, but for now, i'm just trying to get this up and running.
Please flash at your own discretion. I try my best to test at every release, but sometimes i just don't have the time to do so. I have homework and revision and all,and i need sufficient sleep for growth(i'm 13) so just bear with me. I am NOT responsible for anything that happens with your device
Links
KernelsGit Repository
Source
- Stock MIUI Marshmallow Stable V8.2.5.0.MCFMIDL
- Stock MIUI Nougat Dev V7.5.19
Sauce released!
Requirements && Instructions
- TWRP
- Basic flashing skills
- A working human brain
- The will to void your warranty
Just flash the zip after flashing the rom. It'll do it's thing.
Features- Better battery life
- Snappier
- Runtime(Dalvik) optimisation
- Governor optimizations
- TCP tweaks
- 3G Tweaks
- Google DNS
- Faster internet
- Battery tweaks
- JIT as compiler
- Support both ipv4 && ipv6
- No ring delay
- Better voice quality
- GPU optimisation
- Faster boot
- 4 compile thread for dex2oat
- Better camera and image quality
- Purge assets(save battery)
- Logging and debugging disabled(save battery)
All these come from the tweaked ramdisks. All can be found on the git repo above.
Supported Roms- MIUI Marshmallow [V8.2.5.0.MCFMIDL]
- MIUI Nogat [V7.5.19]
- LineageOS 14.1
- Cypher OS V3.6.2
- AOSP Extended 4.2
- crDroidAndroid v3.1
- Android Ice Cold Project
- Xperia Open source Project(XSOP)
- DarkNess reDefined v1.5
- Resurrection Remix Nougat 5.8.3
More will be added based on requests and popularity
Credits
Jarius980 for teaching me how to do repacks and being cool
osm0sis for AIK
Lucas for being cool XDDD (Like the best tester and adviser ever)
CyanGreenMod for fixing the misplaced semicolon
Everyone who contributed/tested/supported
Notes
- WIpe dalvik cache and cache after flash, as dalvik's behavior and execution mode is changed
- Spot something wrong? Pull requests are always welcome!(just make sure you work on the latest upstream)
- Reporting bugs or failed boot are also contributions(VERY HELPFUL)
- Please attach log along with reports if possible
- Pre-release is available on git before release, go ahead and flash if you want
- Safetynet will still be intact since all modifications goes directly to the boot.img
- Thread is still under construction, it may look ugly for now
- NOT ALL THE RELEASES ARE STABLE, PLEASE DO A NAND BACKUP OF YOUR CURRENT BOOT
Thread rules
Do:
- You help one another
- You stay on-topic
- You READ and SEARCH
Don't:
- You do not demand
- You do not ask for ETAs
- You follow the RULES
Announcement:
Please report any issues with build #6
Changelog(please refer to git repo):
Build7:
Dalvik flags
Other tweaks and improvements
Base update
Firmware
Build6:
Update tweaks(dalvik and others)
Update base
Stabilisation
Clean dalvik cache && cache automatically
Build5:
Update tweaks(HUGE)
Fix setprop errors
Build4:
Hopefully fix all wifi issues
Update nogat base
Applied some tweaks
Build #3:
Support new roms (ACIP, RRN5.8.3, XSOP)
Wifi issues fixed for AEX
Build #2:
Fix wifi for some
Stabilisation checks
Build #1:
Compatibility build, so NA
Todo:
Take a huge break because of exams
Create build scripts(in meantime, manual is the only way out)
Dev Log:
[6/5/17]
-I'm too lazy to type it all out, just view my commits on git
[3/5/17]
- Added ACIP, RRN5.8.3, XSOP
- Update AEX Base
- Fix all wifi issues
(More detailed log look at git commits)
[1/5/17]
- Fix wifi for some
[30/4/17]
- Prerelease Build #1
- Complete compatibility checks
- Wrote update script
- Initialised git repo
- Added source unpacked boot files(ramdisk && split_img)
- Setup base and dependencies
Potential feature and support requests:
Known issues:
- Cast screen(Not kernel related unless explicitly proven)
FAQ:
How to NOT break safetynet?
- Just flash the build after the flashing the rom. You can flash mods like magisk and systemless supersu that does not modify /system
Why did i lose my root after flashing(SuperSU)?
- Because supersu patches boot.img and adds a script to start the SU daemon. Flashing a new boot.img will cause the script and patches to be overridden. Just flash the supersu zip again and everything will be reapplied
What can i report?
- After testing a build for a specific rom, you can state the rom your device is on, how old your device is, then the thing you wanna report. You can report failed boots, function bugs and SOT(battery)
Useful Links:
- Telegram Group Chat
https://t.me/joinchat/AAAAAEHQRgRmzU2eCxWK8w
- Whatsapp Group Chat
https://chat.whatsapp.com/7morKcwxExyAcc2deOoYu0
- Discord
https://discord.gg/HS8Ku
- Twrp 3.1.0-0
http://tinyurl.com/midotwrp
- Firmware
https://www.androidfilehost.com/?fid=817550096634766008
- LineageOS addons download
https://download.lineageos.org/extras
- OpenGapps
http://opengapps.org/
-BeanGapps
http://tinyurl.com/beangapps
Wanna donate?
I have to ask my mom again if she allows me to have her paypal donation link. But for now, i guess not
Got any examples of what can be added in? I assume it's mostly ramdisk related since the zImage can't be modified.
AutumQueen92 said:
Got any examples of what can be added in? I assume it's mostly ramdisk related since the zImage can't be modified.
Click to expand...
Click to collapse
yesh. and the ramdisk will be tweaked accordingly
like i can optimise governor values and stuff. the real development will start once sauce gets release(SAUCEEEEEE)
Edit: actually, ill just add this in OP
ala_mo said:
yesh. and the ramdisk will be tweaked accordingly
like i can optimise governor values and stuff. the real development will start once sauce gets release(SAUCEEEEEE)
Edit: actually, ill just add this in OP
Click to expand...
Click to collapse
Welp, is there any way to obtain the voltage values per frequency from there (Reading the values, not changing it)? I wanna read it and make a governor tweak.
AutumQueen92 said:
Welp, is there any way to obtain the voltage values per frequency from there (Reading the values, not changing it)? I wanna read it and make a governor tweak.
Click to expand...
Click to collapse
f im not wrong voltages are inside the kernel source, no way to change that if the kernel does not support it(its not by default)
Governor tweaks can be made. Values are found in init.qcom.rc
Whats rom this working?
Molniya said:
Whats rom this working?
Click to expand...
Click to collapse
Added in OP. I dont't want the first builds to fail, i need to go for class now. Will test myself tonight before release
Does it work on miui 8.2.2.0??
Prem2628 said:
Does it work on miui 8.2.2.0??
Click to expand...
Click to collapse
Miui MM is supported. will upload a build for this tonight.(10more hours) i will have to test before releasing since its the first build
Maybe this kernel will activate technology quick charge by Qualcomm? *Hopefully and I'll migration from Kenzo to Mido ?
Sent from my Redmi Note 3 using XDA Labs
NOS_bzone said:
Maybe this kernel will activate technology quick charge by Qualcomm? *Hopefully and I'll migration from Kenzo to Mido ?
Click to expand...
Click to collapse
QC requires kernel-side changes
AutumQueen92 said:
QC requires kernel-side changes
Click to expand...
Click to collapse
yeah...alot of stuff comes packaged if the kernel supports it(qc, voltage, more governers) but currently, the kernels from xiaomi are not meant for any customization, thus what i can do is to tweak whats currently in store. I cannot add features to the kernel now. I can only tweak the available features The real development starts when the sauce gets released
ala_mo said:
yeah...alot of stuff comes packaged if the kernel supports it(qc, voltage, more governers) but currently, the kernels from xiaomi are not meant for any customization, thus what i can do is to tweak whats currently in store. I cannot add features to the kernel now. I can only tweak the available features The real development starts when the sauce gets released
Click to expand...
Click to collapse
Heh, even with the kernel source I still can't add QC into my Xperia. It's a good thing the Note 4 has more devs. Also, are you experienced in kernel building?
The Carbon Rom that popped up last night listed Mido kernel sources, which I'm highly sceptical if it works. I just need someone to confirm since the OP isn't responding.
AutumQueen92 said:
Heh, even with the kernel source I still can't add QC into my Xperia. It's a good thing the Note 4 has more devs. Also, are you experienced in kernel building?
The Carbon Rom that popped up last night listed Mido kernel sources, which I'm highly sceptical if it works. I just need someone to confirm since the OP isn't responding.
Click to expand...
Click to collapse
from what i know, i suspect it's a partial source. That means that its not full, and there will be some limits
Pertaining to your first question, i can and will build kernels, but i will only do so in December, because my school projects require windows and linux would me more ideal compared to bash on win(always get that dpkg error)
where is the download link? oh, this is just pre-release?
Justin Timberlake said:
where is the download link? oh, this is just pre-release?
Click to expand...
Click to collapse
READ
ala_mo said:
from what i know, i suspect it's a partial source. That means that its not full, and there will be some limits
Pertaining to your first question, i can and will build kernels, but i will only do so in December, because my school projects require windows and linux would me more ideal compared to bash on win(always get that dpkg error)
Click to expand...
Click to collapse
Yeah, linux on windows is a pain. I ended up dual booting with Ubuntu and W10 too.
Features
Based on Codeaurora's msm-3.18 kernel branch LA.UM.5.5.r1-06700-8x96.0
Support for the camera laser autofocus
Lightweight (minimal amount of logging, tracing and debugging functions)
Compiled with Linaro GCC 6.4 using flags specific for Kryo
Userspace display color calibration (Kcal)
Under-the-hood performance patches
Caveats/To-Dos
Focusing on getting the NFC working (the kernel supports PN547, however, the blobs/configs provided by Lineage are for PN548)
Add F2FS support
Compatibility
Tested on LineageOS (2018-01-23), using the 20s bootloader/modem firmware
Downloads
https://forum.xda-developers.com/devdb/project/?id=24609#downloads
XDA:DevDB Information
Typhon Kernel, ROM for the LG G5
Contributors
waau
Source Code: https://github.com/waau/platform_kernel_typhon_q
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.x
ROM Firmware Required: 21S
Version Information
Status: Testing
Created 2018-01-26
Last Updated 2018-02-21
Changelog
M1
Initial release.
M2
Added (untested) support for the H830 & RS988 variants
installscript: Removed the partition fstrim step
ramdisk: Some memory bandwidth tweaks thanks to oxavelar @ the V20
Misc updates
M3
Ported the camera driver from stock, there are issues with the Lineage Snap camera see https://jira.lineageos.org/browse/BUGBASH-1076.
M4
Reverted to CAF's initial 3.18.31 kernel tree due to upstream changes causing crashes
Imported LMK changes from Motorola (avg time to find a task to kill from 1004us to 43us)
Misc driver improvements (bt should work better during streaming intensive workloads)
The IPC/Binder has been updated (is Oreo booting now?)
Relaxed the polling rates in some parts of the kernel
Crypto libs update
Booting takes 40 seconds or so.
This should be a stable build for all the supported variants, I'll improve the overall performance after taking a break and revisiting the Lineage kernel for the charging problem. M5 will be a mostly feature-oriented update including battery saving changes.
Artificial benchmarks seem much better now.
https://browser.geekbench.com/v4/cpu/6766622
M5 RC1
Merged EXT4 encryption from Lineage
Attempt to reduce the power consumption (artificial benchmarks will probably take a hit in some areas, the UX should not be affected)
Imported memory bandwidth improvements from Motorola
Re-enabled the ramoops console
Other misc merges
Let the phone settle for a while after the first boot.
The ramoops console has been re-enabled, in case there are any kernel panics, attach the dump and I'll take a look at it (/sys/fs/pstore/console-ramoops) The rest of the features will come in the final version. I'll also try to get the NFC working.
M6
Redone some parts of the memory management system (compaction, slab, ksm, cma, zram), also pagecaches are now dropped when the screen turns off
Dropped the serial console, kernel initialization should be faster
Driver adjustments (targeting memory leaks)
Memory bandwidth improvements from Sony
Enabled NTFS support (for OTG, untested)
Enabled KSM
Cleaned up the ramdisk, media.camera.ts.monotonic will need to be set manually (read: https://jira.lineageos.org/browse/BUGBASH-1076)
This is probably the last build since I'm giving away my G5 this month, if anyone wants to continue the kernel you are welcome to fork it, the new source is here.
https://github.com/waau/platform_kernel_typhon_q
Mirror for the kernel zip https://github.com/waau/platform_kernel_typhon_q/releases/tag/M6
Wait this is actually great. Quick charge on LOS 14.1 is back?
Kye2000 said:
Wait this is actually great. Quick charge on LOS 14.1 is back?
Click to expand...
Click to collapse
Ported from stock since it was too much of a hassle to fix it on the Lineage kernel, probably these merges broke it
https://review.lineageos.org/#/c/181342/
https://review.lineageos.org/#/c/181479/
waau said:
Ported from stock since it was too much of a hassle to fix it on the Lineage kernel, probably these merges broke it
Something amazing has begun. Thank you. :highfive:
Click to expand...
Click to collapse
Yup. Quick charge works on a fresh RRN install. Thank you very much.
EDIT: From an initial impression, the screen burn-in seems to be reduced a bit. Still very noticeable, though.
totalnoob34 said:
Yup. Quick charge works on a fresh RRN install. Thank you very much.
EDIT: From an initial impression, the screen burn-in seems to be reduced a bit. Still very noticeable, though.
Click to expand...
Click to collapse
I didn't reduce the panel voltage in the build posted here, only the one posted in the LOS thread has the panel voltage reduced. Probably going to reintroduce it later.
waau said:
I didn't reduce the panel voltage in the build posted here, only the one posted in the LOS thread has the panel voltage reduced. Probably going to reintroduce it later.
Click to expand...
Click to collapse
That's placebo effect right there. Is anything else different? I can test it, if you want.
totalnoob34 said:
That's placebo effect right there. Is anything else different? I can test it, if you want.
Click to expand...
Click to collapse
Nothing significant, besides reverting the reduced panel voltage stuff and dumping exFAT. Sure gonna attach it to this post after it's compiled.
Edit: Panel UV Build
This is fantastic! I'm itching to move back to LineageOS from Fulmics. Any chance we might see a fix for LiveDisplay or is that not related to the kernel?
halomademeapc said:
This is fantastic! I'm itching to move back to LineageOS from Fulmics. Any chance we might see a fox for LiveDisplay or is that not related to the kernel?
Click to expand...
Click to collapse
I will take a look at it.
waau said:
Nothing significant, besides reverting the reduced panel voltage stuff and dumping exFAT. Sure gonna attach it to this post after it's compiled.
Edit: Panel UV Build
Click to expand...
Click to collapse
Installed. I'll post back on how it goes.
For laser focus:
https://github.com/waau/platform_ke...ers/media/platform/msm/camera_v2/sensor/proxy
check: vl53l010 files.
Maybe it help to check LG G3 LOS kernel source because Laser focus is working.
I'm happy to report that the kernel works on an existing install of RR too, no need to clean flash :victory:
I was still on the 20a bootloader/modem so I flashed 20s first, just in case ... here are the steps I took:
Reboot to recovery
Nandroid
Flash 20s bootloader + modem
Wipe dalvik/cache
Reboot to system ... all good
Reboot to recovery again
Flash qc-typhon-h850-m1.zip
Wipe Dalvik/cache
Reboot to system
I was (well still am) on RR-N-v5.8.5-20171203-h850-Final and everything seems to work without an issue
Thanks for giving us back "normal" charging @waau :good: :highfive:
walter79 said:
For laser focus:
https://github.com/waau/platform_ke...ers/media/platform/msm/camera_v2/sensor/proxy
check: vl53l010 files.
Maybe it help to check LG G3 LOS kernel source because Laser focus is working.
Click to expand...
Click to collapse
Thanks, although I will try to port the camera drivers from stock and hope that the Lineage HAL cooperates.
waau said:
Thanks, although I will try to port the camera drivers from stock and hope that the Lineage HAL cooperates.
Click to expand...
Click to collapse
Would u be willing to recreate this kernel for the rs988? We only have 2 ROMs to choose from PA and rr and both have the slow charging issue
goast said:
Would u be willing to recreate this kernel for the rs988? We only have 2 ROMs to choose from PA and rr and both have the slow charging issue
Click to expand...
Click to collapse
I will add support for the RS998 and H830 tomorrow.
waau said:
I will add support for the RS998 and H830 tomorrow.
Click to expand...
Click to collapse
Thank u and I will be flashing tomorrow too lol
How can I help?
Hello, I have no development experience and am technically limited, but this project really gives me hope for the future of the G5. Is there anyway I can support you or be of assistence? Thank you so much for taking this on!
Hiya!
Would you be able to add CPU and GPU overclocking as well? I found this post from an old kernel developer who isn't updating theirs anymore, so the work is pretty much done I think.
https://forum.xda-developers.com/lg-g5/development/stock-kernel-t3540157/post72361249#post72361249
I would just use theirs and not bother you, but their kernel breaks bluetooth support for some odd reason, and I need that to use.
If you could add in overclocking I would be SUPER appreciative...
thanks!
Disclaimer
Your warranty is now void!
You will be doing everything at your own risk.
I am not responsible for bricked or damaged devices.
What's working
Mostly everything except for those mentioned in not working list.
What's not working
Video recording (working but laggy if you want to watch it)
SELinux
How to install
1. Wipe system, data and both cache partitions
2. Install the ROM + GApps
3. Wipe again both cache partitions
4. Now you can boot to the system
Download
Unofficial LineageOS 15.1
sgspluss-gapps
Sources
github.com/sgspluss
Credits and Thanks
@sgspluss @Konstantinosj77 @galaxyfreak
Changelog
Code:
[B]lineage-15.1-20180722-UNOFFICIAL-eagle.zip[/B]
Sync with latest LineageOS sources
Some other device and kernel stuff
[B]lineage-15.1-20180707-UNOFFICIAL-eagle.zip[/B]
Fix low volume
Fix livedisplay
Fix kernel local version
Sync with latest LineageOS sources
Some other device and kernel stuff
[B]lineage-15.1-20180624-UNOFFICIAL-eagle.zip[/B]
Initial release
Troubleshooting
Video recording
Video recording is broken in stock camera, just install
https://play.google.com/store/apps/details?id=com.simplemobiletools.camera
as workaround for now.
Playstore show not certified
Try to clean app data and cache first, if its not working for any reason read this
https://www.xda-developers.com/how-to-fix-device-not-certified-by-google-error/
Low RAM Configuration
Add the four lines into your build.prop with any rootexplorer you want, save it and restart your phone to activate them.
Code:
# Low memory device
ro.config.low_ram=true
# Force high-end graphics in low ram mode
persist.sys.force_highendgfx=true
If you need more information read this
https://source.android.com/devices/tech/perf/low-ram#intro
sgspluss said:
Disclaimer
Your warranty is now void!
You will be doing everything at your own risk.
I am not responsible for bricked or damaged devices.
Information
This are unofficial builds made by myself, will fix things, resync and rebuild it if i'll find some free time.
What's working
Mostly everything.
How to install
1. Wipe system, data and both cache partitions
2. Install the ROM + GApps
3. Wipe again both cache partitions
4. Now you can boot to the system
Download
Unofficial LineageOS 15.1
sgspluss-gapps
Sources
github.com/sgspluss
Credits and Thanks
@sgspluss @Konstantinosj77 @galaxyfreak
Click to expand...
Click to collapse
did you fix some problems in this version?
i mean is there any different from the rom BETA 2?
and what abut laging? did you fix it?
Telephone works now, also timekeeping seems to work and not many lags faced yet.
Please try it on yourself, did not have much time to test every build because of my little family and work.
Every feedback is welcome!
thank you by the way to complete bulding this rom.what abt adding sony m2 stock cam app? from kitkat 4.4.4 maybe because its better than cam in v 5.1
---------- Post added at 04:39 PM ---------- Previous post was at 04:36 PM ----------
sgspluss said:
Telephone works now, also timekeeping seems to work and not many lags faced yet.
Please try it on yourself, did not have much time to test every build because of my little family and work.
Every feedback is welcome!
Click to expand...
Click to collapse
great news..iam ready for start testing..i will report if i found somthing
hooooossamq said:
thank you by the way to complete bulding this rom.what abt adding sony m2 stock cam app? from kitkat 4.4.4 maybe because its better than cam in v 5.
Click to expand...
Click to collapse
snap is better because it uses newer drivers and open source (like the rom itself). and there is no point if you add sony camera because it is an AOSP rom, it meant to be pure android (except lineage tweaks)
Also @sgspluss , is this rom deodexed? if not, can you make it deodexed, it will make customisation easier
hooooossamq said:
what abt adding sony m2 stock cam app? from kitkat 4.4.4 maybe because its better than cam in v 5.1
Click to expand...
Click to collapse
Thats not that easy as you think, because need to port this app to the api, but apart of this i want to stay close as possible to lineage.
hooooossamq said:
Also @sgspluss , is this rom deodexed? if not, can you make it deodexed, it will make customisation easier
Click to expand...
Click to collapse
Afaik there will be no odex files, if there are one i will change it in next update. To be honest, did not check it.
Very nice to see new build But unfortunately I'll have time to play with it in this or next weekend :/
@sgspluss do you know why Magisk don't work on previous builds? M2 is no longer supported by Magisk or it's just fixable in the next builds?
after a test i notice these bugs:
1- laging so much after installing opera mini and es file Explorer.
2- over heating in charging bluged and using net for 10 minute.
3- in the screen setting / style/ auto day and night. itsnot working.
4- the lightbar not working even if i enable the light settings.
Hrustus said:
Very nice to see new build But unfortunately I'll have time to play with it in this or next weekend :/
@sgspluss do you know why Magisk don't work on previous builds? M2 is no longer supported by Magisk or it's just fixable in the next builds?
Click to expand...
Click to collapse
Sadly its not fixed, just test it now on myself and magisk not working, do you know any version where its working befor?
hooooossamq said:
after a test i notice these bugs:
1- laging so much after installing opera mini and es file Explorer.
2- over heating in charging bluged and using net for 10 minute.
3- in the screen setting / style/ auto day and night. itsnot working.
4- the lightbar not working even if i enable the light settings.
Click to expand...
Click to collapse
Are they also present in builds befor?
Sent from my athene using XDA Labs
sgspluss said:
Sadly its not fixed, just test it now on myself and magisk not working, do you know any version where its working befor?
Click to expand...
Click to collapse
Unfortunately no, but maybe somebody else remember version. Hmmm... Actually I am not sure that Magisc was working on LineageOS or on Ressurection ROM...
sgspluss said:
Sadly its not fixed, just test it now on myself and magisk not working, do you know any version where its working befor?
Are they also present in builds befor?
Sent from my athene using XDA Labs
Click to expand...
Click to collapse
the lag is much more in your bulid..light bar was working in BEAT 2.
style day and night bug was present in BETA 2..
i was test ALPHA 4 before.every thing working of the bug i say before expact the light bar.and its the most smoth version.. its lagy.. but most smother than all
About problem with magisk, we are also unable to install the magisk manager will look into it whats the reason.
About lags and bugs its strange because i am using same sources, as you can read.
If Something not working logs are helpfull otherwise it takes more time to figure out whats wrong.
What you can do about lags, install supersu from lingeage 14.1 (currently the one from lineage 15.1 and magisk are broken), go into your build.prop, search ro.config.low_ram=true, remove this line and safe build.prop, now restart your phone and test if lags are better.
Sent from my athene using XDA Labs
sgspluss said:
What you can do about lags, install supersu from lingeage 14.1 (currently the one from lineage 15.1 and magisk are broken), go into your build.prop, search ro.config.low_ram=true, remove this line and safe build.prop, now restart your phone and test if lags are better.
Click to expand...
Click to collapse
and here goes my report (very early report, i will add more information)
1-) without gapps, there is some frame dropping in animations and recent apps section (with or without android go mode) but it is same as beta 2, but a bit slower than 8.0 versions. i wonder is there a huge change under the hood between two versions
2-) no lag present in bootanimation, that's unexpected
3-) front camera video works
4-) dark mode works just fine
summary: our device can't handle gapps, that's what i see here. there are minimal frame droppings. also rom is odexed sadly
Just invest some minutes about the magisk problem, seems that we are not compatible yet or never was. But you can send the developer logs, he will look into it, it has nothing to do with rom, lucky me at this point.
About the .odex files that seems to be normal, also can be found on other devices, so there i can not do anything.
Also flashed Alpha4 doesnt be smoother its just uses more animations and some more graphic things related to not using go optimization, also takes more ram, because of not using go optimization so this will be preserved also in the future.
Sent from my athene using XDA Labs
sgspluss said:
Just invest some minutes about the magisk problem, seems that we are not compatible yet or never was. But you can send the developer logs, he will look into it, it has nothing to do with rom, lucky me at this point.
About the .odex files that seems to be normal, also can be found on other devices, so there i can not do anything.
Also flashed Alpha4 doesnt be smoother its just uses more animations and some more graphic things related to not using go optimization, also takes more ram, because of not using go optimization so this will be preserved also in the future.
Click to expand...
Click to collapse
go optimization is better for our device for sure, but this recent apps lag holds me back. but without go and using microg, rom holds up pretty good actually.
As written bevor try to remove ro.config.low_ram=true from build.prop and tell me if this problems you faced will be fixed. All other go optimizations are not changeable manually.
If this will solve the problem, will remove it for future builds, thats fixed for all.
Sent from my athene using XDA Labs
sgspluss said:
As written bevor try to remove ro.config.low_ram=true from build.prop and tell me if this problems you faced will be fixed. All other go optimizations are not changeable manually.
If this will solve the problem, will remove it for future builds, thats fixed for all.
Click to expand...
Click to collapse
as i said before, i am using rom with low_ram=false, and there is less lag compared to go enabled mode.
hello
Me too "low_ram=false" make my m2 less laggy
Thank you for your work
Chihayafuru might feel like an awkward name for a kernel, but the meaning is pure and beautiful. Inspired from an Anime series, the name means "do towards good direction powerfully" like a "thousand swift swords". That's exactly what this kernel is.
This kernel has been made with love by cherry-picking commits from most of the work already done by other developers and introducing other slight changes which ensure your device gets the love it deserves. From performance to battery saving options, you're in full control of your device and the plethora of configurations available allow you to tweak it to your needs.
Presenting CF Kernel (ver 0.90) for Huawei Honor 8
Compatibility Notes:
This kernel is tested to work with stock EMUI 8, Treble 8.x and 9.x ROMs. Compatibility with other ROMs is not guaranteed, However, this doesn't mean I won't support them. If you face a bug or issue, please report it here and I'll happily take a look at it.
GPL Notice:
This kernel conforms to GPL license requirements. Thus all the source code is freely available here without any charge: https://github.com/hackslashX/android_kernel_hisi_hi3650
Recommended Apps:
To tweak most of the settings in the kernel, I recommend using EX Kernel Manager: https://forum.xda-developers.com/general/paid-software/app-ex-kernel-manager-t3560850, Kernel Adituor: https://play.google.com/store/apps/details?id=com.grarak.kerneladiutor&hl=en and FK Kernel Manager: https://play.google.com/store/apps/details?id=com.franco.kernel&hl=en
Early Release Notice:
The kernel is still young and not yet mature. However, with time and your support, we can help make this project rock solid stable for Honor 8. Even though my initial testing has proved good, things might break on your end. Don't fret when that happens, take some logs and send it to me so that I can take a look at them and attempt for a fix.
Features:
Compiled with UberTC 4.9 toolchain with Cortex A53 and O2 optimizations
Upstreamed to v4.4.198
Added blu_active and enabled sched CPU governors (sched, blu_schedutil)
Enabled Scene Aware, Performance, and Powersave GPU governors
Enabled HiSilicon GPUFreq Hotplug and Frequency Hopping feature
Disabled useless drivers and features
Say no to Huawei D.U.B.A.I analytics and root scan feature
Disabled Huawei OASES and Livepatching feature
Disabled Swap and zRAM for much smoother operations
Mali GPU tweaks for improved performance
Added zen, FIOPS IO Schedulers
Added westwood and other advanced TCP algorithms
Fingerprint boost driver for quick recognition
Added CPU boost driver to reduce input lag
Reduced allowed wakelocks and better timer frequency
Boeffla Wakelock Blocker to kill unecessary wakelocks that interrupt your device sleep
Dynamic Sched Tune CPU support
Fast USB Charging support
Option to toggle FSync
Option to toggle SELinux to Permissive or Enforcing
Wireguard VPN support
Improvements to the sound module and vibration driver
... and more which I didn't note down or forgot xD
Installation:
Installing the kernel is pretty easy. Reboot your device to fastboot and execute the following command:
Code:
fastboot flash kernel <kernel-name.img>
Downloads:
Please check the Downloads tab for all downloads (till versions v0.45).
For v0.60 and later, please download from Google Drive: https://drive.google.com/open?id=1fHd7Y9XulrhzHou4013o3K_Ew3AZx2nq
XDA:DevDB Information
Chihayafuru Kernel v0.90 Honor 8 for Android 8.0+, Kernel for the Honor 8
Contributors
hackslash
Source Code: https://github.com/hackslashX/android_kernel_hisi_hi3650
Kernel Special Features:
Version Information
Status: Stable
Created 2018-09-08
Last Updated 2019-11-05
Thank you for your work
And i hope someone running android pie gsi can test this and see if it fix the overheating problem
Thanks a lot <3
Trying it .. will let you know, if I hit any issues
Does it affect the root after flashing this kernel?
$lim $hady said:
Does it affect the root after flashing this kernel?
Click to expand...
Click to collapse
No root is not affected after flashing this kernel.
The kernel image only modifies the 'kernel' partition and leaves the 'ramdisk' one as it is.
hackslash said:
No root is not affected after flashing this kernel.
The kernel image only modifies the 'kernel' partition and leaves the 'ramdisk' one as it is.
Click to expand...
Click to collapse
Thanks will flash it now..
Thank you bro' i flashed on my FRD-L09 Oreo ( stock + root ) and it's work
enzospain said:
Thank you bro' i flashed on my FRD-L09 Oreo ( stock + root ) and it's work
Click to expand...
Click to collapse
Good to know
delete
PremiumBlaze said:
Thank you hack slash for your support for having the honor 8 finally have a custom kernel, it works very well for me
I Flash the custom kernel using twrp for my honor 8, it went very well,
Performance is nice, I notice some speed improvements in games and also battery Improvment.
Im waiting for Undervolt now and the battery would be awesome!!!
Click to expand...
Click to collapse
Thanks for your review.
For gaming you can also set GPU governor to Performance for a more better experience.
I've noted down your request. I'll do my best to deliver.
I never flashed custom kernel before. Is there any chance of permanent brick? If something goes wrong, can't I just flash stock kernel and get it working again?
Also, do I need to wipe data after flashing kernel to see the changes?
SirDarknight said:
I never flashed custom kernel before. Is there any chance of permanent brick? If something goes wrong, can't I just flash stock kernel and get it working again?
Also, do I need to wipe data after flashing kernel to see the changes?
Click to expand...
Click to collapse
There's no chance of permanent brick. Restoring is as easy as flashing the stock kernel via fastboot.
You don't need to perform a data wipe. However, you should allow the kernel to 'settle' i.e. use it for 2-3 charge/discharge cycles to see the effect.
@hackslash .. Installed it yesterday, seems to be working fine.. Jus wanted to check, I m running LoS B5, any specific recommendations on the Governor setting for battery?
I'm using openkirin RR b2. Recent Openkirin on H8 seems to have the problem to barely go into deepsleep or not anymore at all after a while. So I suffer from a quick battery drain. The support channel suggested to try out a custom kernel. I wonder if you know that this kernel will solved the problem?
How about future openkirin or kernel updates? Will I have to go back to stock first or can I just flash new openkirin while still being on this kernel?
Thanks for your hard work! I recently flashed it and it works like a charm!
UPDATE 1: I redownloaded the EMUI 8 package and now it contains everything, including the stock kernel.
UPDATE 2: Short-term experiences: The fingerprint scanner's performance is drastically improved and now it is just as fast and accurate as on EMUI, the camera performance is now closer to EMUI, but there's a little room for improvement, the fast charging is faster than on EMUI, the phone doesn't want to overheat anymore on my custom ROM and overall the phone is now a little bit faster. I'm testing it with the Kirin-GSI AOSP Android 9.0 Pie ROM, not with an OpenKirin ROM, but it is really stable just like on EMUI and OpenKirin ROMs. And I have a suggestion for bugfixes for Honor 8s (eights) running this AOSP Android Pie ROM: Please fix the broken hotspot function in kernel level on Honor 8s (eights) running this custom firmware, implement the EMUI camera app into the kernel and make the camera performance identical to EMUI's. The Kirin-GSI project is now abandoned because the dev bought a new phone which is not a Huawei phone, so he wouldn't fix the problems anymore. It's really annoying that I can't share my unlimited cellular data to friends or to my PS4 when I'm on vacation.
Damn. Now my touchscreen is no longer working. :crying:
Sujanth said:
Damn. Now my touchscreen is no longer working. :crying:
Click to expand...
Click to collapse
Have you managed to back up or download the stock kernel image? You can flash it back.
---------- Post added at 05:56 PM ---------- Previous post was at 05:55 PM ----------
Sujanth said:
Damn. Now my touchscreen is no longer working. :crying:
Click to expand...
Click to collapse
Have you used fastboot or TWRP? If you used TWRP, you need to flash back the stock recovery and the stock kernel, then you can try again flashing CF via fastboot. Flashing with fastboot makes different results than flashing with TWRP.
Sujanth said:
Damn. Now my touchscreen is no longer working. :crying:
Click to expand...
Click to collapse
Noted. I know what's causing the issue. I disabled several touchscreen drivers since not all of them are needed for Honor 8. Flash stock kernel for your device and please send me the file:
Code:
/sys/devices/platform/huawei_touch/uevent
ThePS4Gamer said:
Thanks for your hard work! I recently flashed it and it works like a charm!
UPDATE 1: I redownloaded the EMUI 8 package and now it contains everything, including the stock kernel.
UPDATE 2: Short-term experiences: The fingerprint scanner's performance is drastically improved and now it is just as fast and accurate as on EMUI, the camera performance is now closer to EMUI, but there's a little room for improvement, the fast charging is faster than on EMUI, the phone doesn't want to overheat anymore on my custom ROM and overall the phone is now a little bit faster. I'm testing it with the Kirin-GSI AOSP Android 9.0 Pie ROM, not with an OpenKirin ROM, but it is really stable just like on EMUI and OpenKirin ROMs. And I have a suggestion for bugfixes for Honor 8s (eights) running this AOSP Android Pie ROM: Please fix the broken hotspot function in kernel level on Honor 8s (eights) running this custom firmware, implement the EMUI camera app into the kernel and make the camera performance identical to EMUI's. The Kirin-GSI project is now abandoned because the dev bought a new phone which is not a Huawei phone, so he wouldn't fix the problems anymore. It's really annoying that I can't share my unlimited cellular data to friends or to my PS4 when I'm on vacation.
Click to expand...
Click to collapse
Thanks for taking the time to review the kernel.
Let's get some facts straight. First, camera performance has nothing to do with the kernel and 'camera app' can't be implemented inside the kernel. That's not how things work. Camera processing and everything is handled by Android and so your ROM developer can help you with that. Taking about hotspot, I'm not sure why it doesn't works with Pie. Again, I believe it's a ROM bug and has got nothing to do with kernel. I would wait for Pie releases by OpenKirin team and see if that bug exists there too and 'really' requires a kernel hack to fix it.