Related
Here's a bit of info you may want on this project for how we do things differently:
CLICK HERE to find out more about the new team working on this project since our TeamEOS merger.
No features you don't need which slow the device down, or put your data at risk of being stolen. If you want to give it away, it should be your decision.
A fast and clean install with no UX decisions made for you. You make the ROM whatever you would like.
A team constantly exploring totally new feature sets and optimizations geared toward you, the user
We utilize a plethora of optimizations in a build system unlike any other:
Each build has a toolchain built for your device at the time of build. No more generic toolchain android builds.
Consistently updated upstream toolchain module source with our custom backports, fixes, and optimizations applied in a patch at build time.
Fully built utilizing Link Time Optimization (another custom ROM first). Feel free to google this one a bit to get an idea of the performance gain.
Many repositories have code fixes, cleanups, and many minor optimizations which are too generous to even speak of here.
Optimizations are toggled on and off based on device for the best experience we can acheive for your device without sacrificing any stability
Many Qcom optimizations and AOSP master (upstream) optimizations and fixes using device specifications to determine usage.
Fully built utilizing strict aliasing and isognu++11 mode.
Full "-O3" build. To those who don't know, this is the highest "optimization level" available in gcc that sets many other flags.
Important Links:
Download Nightlies - We have a very in depth review system, so these should be considered stable.
Download Weeklies - These are built once a week on Monday.
Download GApps
Download SuperSU installer
Kernel Source
Interactive and Rolling Changelog
Bug Tracker
Instructions:
In the same recovery session, flash the following:
Flash rom
Flash GApps
Flash Superuser zip
Reboot
Thank you for choosing codefireXperiment,
Yippee! First AOSP build with fully functional IR Blaster! I use the HTC implementation so any IR control app must use the HTC IR api. I tested with this app.
http://forum.xda-developers.com/showthread.php?t=2271113
Blaster mode and Learn mode are fully functional and stable. This is the first non-Nexus device I've done AOSP on so bear with me for a bit. The build is rock solid stable and I dare any build to try and out-benchmark me ;D
one more for good measure
This is truly a wonderful suprise!!
This is truly a wonderful suprise!!
Welcome bigrush!
This sounds cool! Thanks for the hard work. Im gonna give this a shot tomorrow.
gunna take this for a spin. sounds pretty solid.
or so i thought.
AAAARG...
keeps spittin out "Warning: no file_contextsassert failed.....Followed by various prop errors about the phones model"
anyone got any idea whats goin on?
Are the APN for ATT in this ROM or do I have to put them in myself
Sent from my HTC One using Tapatalk 2
Does cfx have the same janky animation and sluggishness of other AOSP roms for the One when compared against a Sense or GE ROM?
If anyone could fix aosp/optimize for device specific hw on non-nexus devices its you.
Sieze said:
gunna take this for a spin. sounds pretty solid.
or so i thought.
AAAARG...
keeps spittin out "Warning: no file_contextsassert failed.....Followed by various prop errors about the phones model"
anyone got any idea whats goin on?
Click to expand...
Click to collapse
I'm getting this same error too. Anybody know what's up yet? Probably something simple lol
Are you guys flashing with cw or twrp? Don't worry about the file context warning. I may have to disable device assert in installer script.
bigrushdog said:
Are you guys flashing with cw or twrp? Don't worry about the file context warning. I may have to disable device assert in installer script.
Click to expand...
Click to collapse
im using CW touch 6.0.3.3
running a backup atm but once finished il flash TWRP and see if it works.
Ok. So it fails to flash on cw then?
bigrushdog said:
Ok. So it fails to flash on cw then?
Click to expand...
Click to collapse
yup. it flashed with out a hitch on TWRP...
Sieze said:
yup. it flashed with out a hitch on TWRP...
Click to expand...
Click to collapse
Ya we compile the project with twrp recovery. I'll confer with my associates about tweaking or killing device assert in release tools. Also, I gotta drop a global device build too. First aosp build with IR Blaster and this board gets hardly any traffic! I personally run the build on my m7tmo so any derp gets my attention. There's little minor issues here and there but nothing major. Bluetooth OBEX is derped project wide but should be fixed soon.
bigrushdog said:
Ya we compile the project with twrp recovery. I'll confer with my associates about tweaking or killing device assert in release tools. Also, I gotta drop a global device build too. First aosp build with IR Blaster and this board gets hardly any traffic! I personally run the build on my m7tmo so any derp gets my attention. There's little minor issues here and there but nothing major. Bluetooth OBEX is derped project wide but should be fixed soon.
Click to expand...
Click to collapse
well initial response to laying my finger and moving it on the screen. amazing. i didnt think id feel or tell much a difference in response. but holy S#!7 so smooth and stuff happens when its supposed to aka as soon as i touch the icon its open...
(ノ^_^)ノ also the boot animation is pretty frickin sweet.
also the benchmark has me drooling.
Quadrant Standard: 6749
also im really frickin liking this ROM
Hahaha don't lie! The boot anim sucks ass man! Ya all this ui jitter talk I hear, I'm just not getting all that with our build. If the build sucked I wouldn't run it. And I sure as hell wouldn't publish it. Thanks for the kind words. More win in the pipeline.
bigrushdog said:
Hahaha don't lie! The boot anim sucks ass man! Ya all this ui jitter talk I hear, I'm just not getting all that with our build. If the build sucked I wouldn't run it. And I sure as hell wouldn't publish it. Thanks for the kind words. More win in the pipeline.
Click to expand...
Click to collapse
well hey credits due where its earned right? but yea im still crappin my pants at how there is absolutely no lag at my finger tip.
Hands down the best android experience ive ever had. i can trully feel the power of my device in my hand in all its glory.
Grab that IR app and program your TV man. Dude dropped source for the app so maybe I'll do some IR toggles or something
Sieze said:
yup. it flashed with out a hitch on TWRP...
Click to expand...
Click to collapse
I will also try with twrp tomorrow morning. I personally don't prefer one over the other so if twrp is what works then twrp it is!
mikexmayhem said:
I will also try with twrp tomorrow morning. I personally don't prefer one over the other so if twrp is what works then twrp it is!
Click to expand...
Click to collapse
Flashed with twrp. Still gave error but said successful. After reboot everything looks just fine. Great ROM!
Hello all, I am looking for a way to enable all cores on the Honor 5x. If you use Kernel Adiutor (and I'm sure you do) you'll notice that 99% of the time (save for a reboot) your little cluster is offline when using any AOSP ROM, now the only way I've found to enable them is to edit the value in the active file located in /sys/module/cluster_plug directory. The issue with this method is that it just enables them, 95% of the workload is still handled by the big cluster, even when it's straining itself the little cluster fails to pick up any of the workload. I have done clean installs of the Blaze kernel and the issue is still not resolved. Any incite into this issue will be greatly appreciated. Thanks.
You'll need to mess with:
/sys/devices/system/cpu/cpu0/core_ctl/min_cpus
/sys/devices/system/cpu/cpu0/core_ctl/max_cpus
/sys/devices/system/cpu/cpu4/core_ctl/min_cpus
/sys/devices/system/cpu/cpu4/core_ctl/max_cpus
It takes integer value ranging from 0-4. 0-4 meaning how many cores you want online per cluster.
The only issue is that I don't have /core_ctl directory that you've specified, I don't recall ever having it on this ROM, though I could be wrong. I'm using the krexus ROM in case I hadn't specified before.
I know, reading the stock ROM forums I got very excited to see the before mentioned information that was posted only to see that said (/core_ctl) directory was missing from any AOSP ROM I had used. This is the one thing that is holding me up from giving up my Windows phone as my business phone (the lag as a result of only being able to use 4 cores is intolerable in my line of work) even giving a link to what all these directory files mean would be very helpful. Thanks.
You could google what those directory means and that would give you that answer.
I have done this (and I consider myself well versed in the ways of the interwebs and I rarely come up with anything useful but I've been working on a solution for my original question and feel I am close to achieving it. I will post once I do.....though if anyone has ANY suggestions at all I'm open to try, all of my discoveries have been made through trial and error.
tboned82 said:
I have done this (and I consider myself well versed in the ways of the interwebs and I rarely come up with anything useful but I've been working on a solution for my original question and feel I am close to achieving it. I will post once I do.....though if anyone has ANY suggestions at all I'm open to try, all of my discoveries have been made through trial and error.
Click to expand...
Click to collapse
You may be needing a custom kernel to achieve this successfully.
Sent from my honor 5X using XDA Labs
adriansticoid said:
You may be needing a custom kernel to achieve this successfully
Click to expand...
Click to collapse
I can't recall if I mentioned it or not but I'm using the blaze kernel at the moment (as far as I know it's the only custom one available for this phone?) Also the CPU control I desire is available inside the stock KIWI ROM, just wish I knew of a way to "port" that hotplug to a AOSP ROM.... thinking SELinux policy is prohibiting me from achieving the CPU control I'm after, but not sure if it's the only thing at play when it comes to this issue.
tboned82 said:
I can't recall if I mentioned it or not but I'm using the blaze kernel at the moment (as far as I know it's the only custom one available for this phone?) Also the CPU control I desire is available inside the stock KIWI ROM, just wish I knew of a way to "port" that hotplug to a AOSP ROM.... thinking SELinux policy is prohibiting me from doing this, but not sure if it's the only thing at play when it comes to this issue.
Click to expand...
Click to collapse
Have you joined the beta channel of Blaze in Telegram?
adriansticoid said:
Have you joined the beta channel of Blaze in Telegram?
Click to expand...
Click to collapse
I have not, but would be very interested, what is Telegram?
tboned82 said:
I have not, but would be very interested, what is Telegram?
Click to expand...
Click to collapse
It's a messaging app. Just like Whatsapp, but with some diferences. You can check it in the Play Store. Telegram group link is in the Blaze kernel thread.
Wow thank you, I dirty flashed it (since version 2 dirty flashed fine) and didn't have pleasing results, going to do a clean flash AOSP, but those hotplug features are exactly what our phones need! Who's ready to hunt down some flagships?
tboned82 said:
Wow thank you, I dirty flashed it (since version 2 dirty flashed fine) and didn't have pleasing results, going to do a clean flash AOSP, but those hotplug features are exactly what our phones need! Who's ready to hunt down some flagships?
Click to expand...
Click to collapse
You didn't have screens of death?
Sent from my honor 5X using XDA Labs
tboned82 said:
didn't have pleasing results
Click to expand...
Click to collapse
Don't bother with blaze kernel. It's heavily flawed. As soon as you turn on hotplugging phone will crash and you have to reboot. Unfortunately development seems to be halted.
alpinista82 said:
Don't bother with blaze kernel. It's heavily flawed. As soon as you turn on hotplugging phone will crash and you have to reboot. Unfortunately development seems to be halted.
Click to expand...
Click to collapse
Yeah the developer have not seen action the past few weeks.
adriansticoid said:
You didn't have screens of death?
Click to expand...
Click to collapse
I apologize for my absence, I really hate being that "guy" but all my free time has been devoted to tracking down a nasty electrical gremlin in my sister in laws car, but no I have never had any adverse effects from dirty flashing anything really
alpinista82 said:
Don't bother with blaze kernel. It's heavily flawed. As soon as you turn on hotplugging phone will crash and you have to reboot. Unfortunately development seems to be halted.
Click to expand...
Click to collapse
I currently have blaze kernel installed and using the method I've mentioned before am able to enable all cores, but with very poor load balancing, and the beta version is far from RTM at the moment so guess I'm stuck with version 2 for the time being.
adriansticoid said:
Yeah the developer have not seen action the past few weeks.
Click to expand...
Click to collapse
I have noticed this as well, which is unfortunate because the dev seems like a very talented coder who is quite capable of the task at hand, sometimes life gets in the way of the things we would like to do so I'm just going to be patient and hope he picks back up on the project.
tboned82 said:
I apologize for my absence, I really hate being that "guy" but all my free time has been devoted to tracking down a nasty electrical gremlin in my sister in laws car, but no I have never had any adverse effects from dirty flashing anything really
I currently have blaze kernel installed and using the method I've mentioned before am able to enable all cores, but with very poor load balancing, and the beta version is far from RTM at the moment so guess I'm stuck with version 2 for the time being.
I have noticed this as well, which is unfortunate because the dev seems like a very talented coder who is quite capable of the task at hand, sometimes life gets in the way of the things we would like to do so I'm just going to be patient and hope he picks back up on the project.
Click to expand...
Click to collapse
It's been that story for many developers man. A great project paused because life hit hard again. I believe he'll come back to it soon.
tboned82 said:
Hello all, I am looking for a way to enable all cores on the Honor 5x. If you use Kernel Adiutor (and I'm sure you do) you'll notice that 99% of the time (save for a reboot) your little cluster is offline when using any AOSP ROM, now the only way I've found to enable them is to edit the value in the active file located in /sys/module/cluster_plug directory. The issue with this method is that it just enables them, 95% of the workload is still handled by the big cluster, even when it's straining itself the little cluster fails to pick up any of the workload. I have done clean installs of the Blaze kernel and the issue is still not resolved. Any incite into this issue will be greatly appreciated. Thanks.
Click to expand...
Click to collapse
flash official cm 12.1 built. lol no deep sleep and all cores online...go for it.
methuselah said:
flash official cm 12.1 built. lol no deep sleep and all cores online...go for it.
Click to expand...
Click to collapse
Drains battery like hell. Lol.
Sent from my Galaxy Tab 3 using XDA Labs
methuselah said:
flash official cm 12.1 built. lol no deep sleep and all cores online...go for it.
Click to expand...
Click to collapse
I had thought of doing this, though I don't see any cm 12.1 links in the Honor 5x thread, just 13, (though I'm at work at the moment and have to be stealthy about my research...errgghh Damn kids and their Snapchat) and I have to admit I've kind of fallen in love with the Krexus ROM and am apprehensive to flash another. Just need that hotplug support (and OTA updates would be nice as well
So i been trying to make custom roms for this phone recently but been hitting a major issue, no matter what i do i can't seem to get the WiFi, Camera, Bluetooth, NFC or Loud Speaker working
I Have tried several different kernel source repo's and i even have a working version of ResurrectionRemix working, but it has no bluetooth, wifi, etc. it works for taking calls and general usage but yeah its kinda useless without these functions, does anyone have any idea, I can't really find much information about this phone or building stuff for it, it seems not too many people do custom work for it given its not exactly a mainstream phone
raithsphere said:
So i been trying to make custom roms for this phone recently but been hitting a major issue, no matter what i do i can't seem to get the WiFi, Camera, Bluetooth, NFC or Loud Speaker working
I Have tried several different kernel source repo's and i even have a working version of ResurrectionRemix working, but it has no bluetooth, wifi, etc. it works for taking calls and general usage but yeah its kinda useless without these functions, does anyone have any idea, I can't really find much information about this phone or building stuff for it, it seems not too many people do custom work for it given its not exactly a mainstream phone
Click to expand...
Click to collapse
What are you using for device tree etc.?
VBCerobil said:
What are you using for device tree etc.?
Click to expand...
Click to collapse
Device tree
https://github.com/DevelopedInside/android_device_wileyfox_marmite
Kernel
https://github.com/DevelopedInside/android_kernel_wileyfox_msm8937
Vendor
https://github.com/DevelopedInside/proprietary_vendor_wileyfox
raithsphere said:
Device tree
https://github.com/DevelopedInside/android_device_wileyfox_marmite
Kernel
https://github.com/DevelopedInside/android_kernel_wileyfox_msm8937
Vendor
https://github.com/DevelopedInside/proprietary_vendor_wileyfox
Click to expand...
Click to collapse
As it's known by the creator of those sources the only thing you can do is try to fix it yourself or wait for him to do it...
Well i managed to build the M Version of RR 5.7.4 with Wifi, BT and Stuff working, just anything N i am not having much luck with yet, tho i only got it too boot once and since that it just boot loops for some reason, so i need to debug that
raithsphere said:
Well i managed to build the M Version of RR 5.7.4 with Wifi, BT and Stuff working, just anything N i am not having much luck with yet, tho i only got it too boot once and since that it just boot loops for some reason, so i need to debug that
Click to expand...
Click to collapse
Good luck! Keep us posted I'm gonna try and make a new device tree and build AOSP 7.1.2 with it as it seems to be most compatible... From there I'll try to build up again to other roms.
That sounds good, no issues up to now I am doing a few more tests then I will post it for people to try, I should install stock 7.1.2 at some point and try and extract the needed stuff
raithsphere said:
That sounds good, no issues up to now I am doing a few more tests then I will post it for people to try, I should install stock 7.1.2 at some point and try and extract the needed stuff
Click to expand...
Click to collapse
Good work!
I'm not new at this but I still got some questions regarding to the needed files in device and vendor tree, as to which are needed and why. My first try now will be building aosp with just the very basics of a device tree (as I don't want to copy anything to keep it pure and learn more about it) than logcatting and using the android-blob-utility and go from there. Gonna be a lot of work, but should be worth it... Not wanting to sound like an obsessive person but I eventually want android oreo on my device
He he I can understand that, it's best to know how and why, I am learning all this myself, so it's all new to me given I am normally a php programmer lol, I think O preview is in the aosp repo already too
raithsphere said:
He he I can understand that, it's best to know how and why, I am learning all this myself, so it's all new to me given I am normally a php programmer lol, I think O preview is in the aosp repo already too
Click to expand...
Click to collapse
android-8.0.0_r4 is there
But first 7.1.2 as all the proprietary files are for that version so I think it will be easiest (upgraded the android-blob-utility for sdk 25). Just found a forum post about google cloud for free, downloading the source already on it, it has better speed than my internet connection here... Why does compiling take so much time? I did php for a long time, but really I'm mostly programming in c# now (xamarin projects) Did the "Linux from Scratch" to a few years ago so this should work to...
yeah the google cloud thing is very handy i am using this at the moment, good luck, but yeah 7.1.2 would be better to go for first
raithsphere said:
yeah the google cloud thing is very handy i am using this at the moment, good luck, but yeah 7.1.2 would be better to go for first
Click to expand...
Click to collapse
Very handy indeed, 94% no space left on disk Anyway it's downloaded on my home server now, which compiles even faster as it seems
VBCerobil said:
Very handy indeed, 94% no space left on disk Anyway it's downloaded on my home server now, which compiles even faster as it seems
Click to expand...
Click to collapse
Nice Nice, i managed to setup a system with enough space on Google Cloud it wasn't too hard to change the drive space and everything, but it just eats thru that $300 credit you get i will say that much, anyways i hope you manage to get a 7.1.2 built with Working WiFi and stuff should be very helpful to getting the ball rolling, i am going to keep trying what i can here, going to look at AOSP myself later today probably
raithsphere said:
Nice Nice, i managed to setup a system with enough space on Google Cloud it wasn't too hard to change the drive space and everything, but it just eats thru that $300 credit you get i will say that much, anyways i hope you manage to get a 7.1.2 built with Working WiFi and stuff should be very helpful to getting the ball rolling, i am going to keep trying what i can here, going to look at AOSP myself later today probably
Click to expand...
Click to collapse
Well, switching to omnirom Downloading it now... I did the 100Gb SSD on the cloud to make it build faster, but, as I said, my server at home compiles a little faster even so there's really no point for me, besides the internet speed which is 10x slower here. Would be nice to have a few different options that are stable for our device... Although I'd like to see it go on the official lineage website as well...
VBCerobil said:
Well, switching to omnirom Downloading it now... I did the 100Gb SSD on the cloud to make it build faster, but, as I said, my server at home compiles a little faster even so there's really no point for me, besides the internet speed which is 10x slower here. Would be nice to have a few different options that are stable for our device... Although I'd like to see it go on the official lineage website as well...
Click to expand...
Click to collapse
Ahh fair enough i setup a 20 core thing so it compiles nice and quick, and yes it would be nice to have more options indeed, my RR 6.0 seems to be running ok at the moment, but i am not too sure if i am going to share that one because its M and not N, so its not exactly on the latest security patch
Still no luck here with Anything after M
ResurrectionRemix-M-v5.7.4-20170821 - Working - Just flash the zip file using sideload on TWRP
https://drive.google.com/file/d/0B77lq0Gsa3CtMF9XWUNISzNwU0E/view?usp=sharing
and the N Version if anyone wants to look - Note with the N Version Wifi, Loudspeaker, NFC & Camera are not working
https://drive.google.com/file/d/0B77lq0Gsa3CtWmpDdkxhNS1VeEE/view?usp=sharing
Well it's not a kernel issue, i have used the stock WileyFox Kernel and still no Wifi/BT
Tho i did find in logcat
09-11 17:27:09.203 2931 5396 D WifiHW : insmod: open("/system/lib/modules/wlan.ko") failed: No such file or directory
09-11 17:27:09.203 2931 5396 E WifiStateMachine: Failed to load driver
09-11 17:27:09.204 2931 6628 E OsAgent : Wifi Scan Always Available: 0
Click to expand...
Click to collapse
After checking wlan.ko symlink is there pointing to /system/lib/modules/pronto/pronto_wlan.ko
there is no pronto folder so this could be part of this issue
raithsphere said:
Well it's not a kernel issue, i have used the stock WileyFox Kernel and still no Wifi/BT
Tho i did find in logcat
After checking wlan.ko symlink is there pointing to /system/lib/modules/pronto/pronto_wlan.ko
there is no pronto folder so this could be part of this issue
Click to expand...
Click to collapse
I see you made some progress my friend Check my last post in the lineage 13 post... It's all just proprietary file issues...
i been tinkering a little but not had much time i See that you, BeYkeRYkt and vm03 have been working on the repo's over at DevelopedInside, i would like to say keep up the good work, Hopefully we can get more than LineageOS on the Swift 2 soon enough, i been playing with RR & Validus N recently
Working:
RIL
Audio
Display
Bluetooth
Wifi
Sensors
Camera
Fingerprint
Broken:
VoLTE?
I will release when I want to.
o.o this one fixes the display error for internal storage space!
kgptzac said:
o.o this one fixes the display error for internal storage space!
Click to expand...
Click to collapse
you sure you were using an SD card (and the phone detects it)?
Jus sayin', I'm not gonna test it for now
P650SE said:
Yay! I have never been so excited in my entire life! BTW, how do you guys know the bug for internal storage space has been fixed, or is that just purely speculation? You kinda make it sound like there's already a download available for people who want to beta test.
Click to expand...
Click to collapse
In my opinion nougat and oreo are the most unexciting Google OS I know. It's nice to have, but half of the first year after release devs on XDA and even Google itself trying to bring back the performance or/and battery life the OS version before had.
Not to mention the problems with Magisk etc.
SilentEYE said:
In my opinion nougat and oreo are the most unexciting Google OS I know. It's nice to have, but half of the first year after release devs on XDA and even Google itself trying to bring back the performance or/and battery life the OS version before had.
Not to mention the problems with Magisk etc.
Click to expand...
Click to collapse
I suppose you're right. Neither Nougat or Oreo have brought significant changes, they have both been 'minor' updates with subtle changes to improve certain aspects of the OS. The last major update to Android was Lollipop, when the entire appearance was drastically overhauled from previous versions. I'm only excited because we just have to take what we're given, and any update to update the appearance and usability of Android after an entire year is a refreshing change! Even though Nougat was only a small update, it feels unbearable to me when switching back to Marshmallow without the new quick settings swipe-down; the one before the entire notification area appears. So even the small features can make a lot of difference to the overall experience! I'm still really looking forward to seeing the changes made in Oreo for myself when it comes to the Axon 7.
SilentEYE said:
In my opinion nougat and oreo are the most unexciting Google OS I know. It's nice to have, but half of the first year after release devs on XDA and even Google itself trying to bring back the performance or/and battery life the OS version before had.
Not to mention the problems with Magisk etc.
Click to expand...
Click to collapse
I don't get why people say this, honestly. Just because you didn't get a visual overhaul like you got from KitKat to Lollipop doesn't mean there weren't significant changes. Visually the OS is already at a level where there's no need for a major change (it has been "ready" since Lollipop, imo; Marshmallow, Nougat, and Oreo have all had small visual tweaks but have stuck to the Material language), and most of the tweaks work "under the hood." Oreo will bring Project Treble, which may just be the most significant change in Android in the last few years. It also brings improvements on the behavior of notifications and background services or apps. It's an incremental update, yes. But it's by no means a small update.
@Gases
We talked about excitement.
I mentioned the problems with the new OS updates, which brings maybe more security but also many problems to custom ROMs. Furthermore there are more problems in the first months. I don't need visual tweaks.
Project treble is mainly positive for stock ROMs. We will see, in which way custom ROMs can profit of this new feature.
Background battery eating apps are no problem on custom ROMs based on LOS, if you use the internal features or external apps. But again. It's nice to have already implemented.
Finally I am always thankful for all kind of ROMs and kernels devs provide to the community. And I was always someone who donated to say 'thank you'
@SilentEYE Will this thread be used for development progress or is it just a tease thread?
ethanscooter said:
@SilentEYE Will this thread be used for development progress or is it just a tease thread?
Click to expand...
Click to collapse
I am not the dev but this is probably more a promotion thread. Final builds will surely be on developement thread.
Some devs are working on oreo right now.
Let's wait and be thankful for their work.
Here is a small update about the situation. Since the most common stuff is working im going to release this rom in 1-3 days. But don't expect to much. This rom is still WIP.
Working now:
RIL(Calls, Sms)
Audio
Most of the stuff (NFC etc.)
Broken:
Camera
Fingerprint
VoLTE (Will be probably broken until we get new blobs)
OrdenKrieger said:
Here is a small update about the situation. Since the most common stuff is working im going to release this rom in 1-3 days. But don't expect to much. This rom is still WIP.
Working now:
RIL(Calls, Sms)
Audio
Most of the stuff (NFC etc.)
Broken:
Camera
Fingerprint
VoLTE (Will be probably broken until we get new blobs)
Click to expand...
Click to collapse
Does cellular data work?
ethanscooter said:
Does cellular data work?
Click to expand...
Click to collapse
Yas.
What about the speakers? Do they have the same problem as before the fix was found?
Teet1 said:
What about the speakers? Do they have the same problem as before the fix was found?
Click to expand...
Click to collapse
Probably since they just got audio to work and the ROM is very experimental.
Really looking forward to testing this when the first release is posted on the forums. I'm just hoping the camera and fingerprint sensor will be relatively simple to fix. Thanks for everything you've done so far!
Teet1 said:
What about the speakers? Do they have the same problem as before the fix was found?
Click to expand...
Click to collapse
ethanscooter said:
Probably since they just got audio to work and the ROM is very experimental.
Click to expand...
Click to collapse
Audio is working normal. Like on cm14.1 both speakers are working just fine.
yes.. you are the man!
hopefully cam and fingerprint will fixed soon.
thanks ordenkrieger and all others
Actually it would be nice if you can upload to test for us fp and camera is not important for me.
WesTD said:
Actually it would be nice if you can upload to test for us fp and camera is not important for me.
Click to expand...
Click to collapse
That would be nice and all, but I think the devs want mostly everything to work for those that prefer to have a stable build and etc.
WesTD said:
Actually it would be nice if you can upload to test for us fp and camera is not important for me.
Click to expand...
Click to collapse
I was just looking over in the Nexus 6 forms and to overcome the camera issue for them they had to upgrade from 7.1.2 - 8.0 and then restart the phone. So there is hope especially since the Nexus 6 is a 32-bit phone and I'm pretty sure 8.0 was supposed to be 64-bit.
Hey
This will not be a (much) maintained thread. This is the main thread: G5 forum
Kernel is for Lineage based roms. Works with Android 11
US996 = Officially unlocked
US996Dirty = Unlocked "the other way"
It was tested to give about 30% longer battery life, using youtube playback constantly, than stock lineage/lighthouse kernels.
Stock (original lg) rom was tested also, which lasted 7h in the test. The same as my kernel, but I dare say my kernel will be faster
in addition, but it's obviously difficult to compare stock vs lineage in that manner (stock being very old un-optimized userspace).
Keep in mind the number above is from G5 which has a 2800mAh battery. The tester's battery was also a bit worn.
-----------------------------
Downloads:
V0.8 - Androidfilehost
Beta builds - Androidfilehost
-----------------------------
UPDATE - feb 14 2022
Version 0.7 Beta2 uploaded. You'll find it in the link above.
UPDATE - april 26 2022
For H990 - version 0.7 beta4 - To solve crashing (obsolete with 0.7 stable build)
UPDATE - june 28 2022
Version 0.7 uploaded -- Built with gcc12.1, disabled kpti for better performance and enabled zram (with upstreamed lz4, zsmalloc, zram)
Removed the old builds from this post
UPDATE - feb 19 2023
Version 0.8 uploaded
Source
Thanks to @AShiningRay
I've put his undervolt, and tweak to schedutil in v0.7
I will try building the H990DS variant , Will send here.
Mysteriouslog6 said:
I will try building the H990DS variant , Will send here.
Click to expand...
Click to collapse
Don't bother, I'm building now. I forgot the 990 is also a very common device.
I will also upload the final/stable build for each device at some point.
Edit: Added to post #1
Hi, is the IR working with this kernel? Thanks
timba123 said:
App says so
Click to expand...
Click to collapse
Unfortunately this app only checks if the IR blobs have been implemented and can be accessed by the phone's OS, because it reports the same info on Lineage's stock kernel where the IR doesn't work properly after sending the first signal, so that app is not a reliable way to test it. I could be wrong tho, since i would really like to test this kernel's IR by myself, but it throws me right into fastboot when flashing it on top of either LOS 18.1 or Lighthouse.
IR is not working. I've looked into that and i understand now why nobody has ir working.
The main driver part is in userspace, so we need to implement a solution from a msm8996
LeEco device which has the same ir chip (maxq616), on the ROM side. This is in official Lineage
here: https://review.lineageos.org/c/LineageOS/android_device_leeco_msm8996-common/+/274548
GitHub - LineageOS/android_device_leeco_msm8996-common
Contribute to LineageOS/android_device_leeco_msm8996-common development by creating an account on GitHub.
github.com
People have been saying Gamma kernel works; that may be, but looking at his sources show
no changes in that regard. So then he either wrote his own driver based on NDA restricted
documents or he found something ready-made. In any case; not making it public would be
the right ting to honor the NDA and not get in trouble.
Just putting it out here for potentially interested devs. I have shown this to one of the Lighthouse
devs, and he is currently trying to port those changes.
AShiningRay said:
I could be wrong tho, since i would really like to test this kernel's IR by myself, but it throws me right into fastboot when flashing it on top of either LOS 18.1 or Lighthouse.
Click to expand...
Click to collapse
I see you have a H910 device. Anyone else have the same problem?
askermk2000 said:
I see you have a H910 device. Anyone else have the same problem?
Click to expand...
Click to collapse
As far as i tested some time ago, gamma kernel had the same behaviour after flashing, but i tested that one on LOS 17.1. It might be because my refurbished V20 is a bit weird in regards to the SoC. No matter where i check it, the phone reports a Snapdragon 821 (MSM8996Pro) with clock tables all the way up to 2.34Ghz and etc even on LG's stock rom, which i find really strange because the V20's are supposed to have a Snapdragon 820, so i'm not really sure if that is the reason behind the fastboot problem, since both LG stock and Lineage's kernel works just fine.
And as for gamma, even the IR on that seems a bit finicky at best due to some reports on V20 Reddit also saying it doesn't work, making it even less likely to ascertain exactly "how" or "why" it works there. I am also compiling a custom kernel for the V20 based on LOS 18.1 sources and from what i saw, gamma's source has basically identical IR files, be it LIRC or IRRC, and some logging about the IR has specifically shown me that the kernel is actually issuing the signal correctly, but something breaks between the kernel and the OS, making the ConsumerIRService return error -1 right after that., which eventually led me to this as well:
[REF] How Infrared is (not) working on LePro3 - some infos for IR devs
So, I was also interested why 3rd party infrared apps are not working on the LePro 3, and did some debugging. This thread somehow documents my findings step by step... Edit - Dec 1, 2016: As the postings below got a little bit technical, I'll...
forum.xda-developers.com
It might be something outside of the kernel, but i don't have the skills to mess around with ROMs yet and logging it is the best i can do on them.
AShiningRay said:
As far as i tested some time ago, gamma kernel had the same behaviour after flashing, but i tested that one on LOS 17.1. It might be because my refurbished V20 is a bit weird in regards to the SoC. No matter where i check it, the phone reports a Snapdragon 821 (MSM8996Pro) with clock tables all the way up to 2.34Ghz and etc even on LG's stock rom, which i find really strange because the V20's are supposed to have a Snapdragon 820, so i'm not really sure if that is the reason behind the fastboot problem, since both LG stock and Lineage's kernel works just fine.
Click to expand...
Click to collapse
Ah ok. I know why then.
You see, me and Omar removed some board definitions from our kernel to make it smaller. Those where definitions for sd821 V20s - which we gathered was for some prototype devices which would likely never be in circulation.
But here you are with one such device
Edit: see here: https://github.com/stendro/msm8996_...a80921570789d20375f0b62516be3c6973ccb3375552a
askermk2000 said:
Ah ok. I know why then.
You see, me and Omar removed some board definitions from our kernel to make it smaller. Those where definitions for sd821 V20s - which we gathered was for some prototype devices which would likely never be in circulation.
But here you are with one such device
Edit: see here: https://github.com/stendro/msm8996_...a80921570789d20375f0b62516be3c6973ccb3375552a
Click to expand...
Click to collapse
Welp, at least the phone is doing its job of being a device mainly for development, lol. It also means your kernel probably works fine on H910's running a snapdragon 820, and thanks for clearing that up, makes me feel a bit more comfortable knowing that the chance of my phone being some kind of Frankenstein is a bit smaller.
If you need any testing or logs in the future, i'll be happy to help.
timba123 said:
LG V20 Pro Coming soon to Japan - Trendy Techz
In this post we shared the complete details of upcoming smartphone LG V20 Pro which is coming soon to Japan store. Complete details are here in this post.
trendytechz.com
Click to expand...
Click to collapse
Mine doesn't look very similar to this Pro version, since my variant is actually a H910 and save for the SoC, everything else fits right in line with other standard V20's (the screen for example is clearly 5.7", since it is relatively bigger than my 5.5" Redmi Note 4 despite having smaller bezels, while the V20 Pro reportedly has a 5.2" screen plus a Snap 820, mine also has 64GB of internal storage versus the Pro's 32GB), if i flash a kernel or ROM of any other variant it either gives me a very glitched screen rendering right at boot (US996) or doesn't boot at all.
Edit: After finding some pictures of the Pro model's back, i can now affirm that the design is completely different from mine, even the camera layout that puts the flash and laser in the center and not on the sides, while the one i have is the opposite just like the default mode, so it definitely isn't the Japanese Pro version, but thanks for the heads-up.
AShiningRay said:
And as for gamma, even the IR on that seems a bit finicky at best due to some reports on V20 Reddit also saying it doesn't work, making it even less likely to ascertain exactly "how" or "why" it works there. I am also compiling a custom kernel for the V20 based on LOS 18.1 sources and from what i saw, gamma's source has basically identical IR files, be it LIRC or IRRC, and some logging about the IR has specifically shown me that the kernel is actually issuing the signal correctly, but something breaks between the kernel and the OS, making the ConsumerIRService return error -1 right after that., which eventually led me to this as well:
It might be something outside of the kernel, but i don't have the skills to mess around with ROMs yet and logging it is the best i can do on them.
Click to expand...
Click to collapse
The Lighthouse dev I mentioned has replied. He says that LG has proprietary blobs specifically for IR, and LeEco don't. He'd rather make it work as intended with the blob, instead of using some hacky solution.
So then it makes sense that it work on first try and possibly working normally on gamma - there is some facility already there. Why it doesn't work I can't quite fathom though.
I have looked at source, dtb, configuration... but I may have missed something. I may have to compare to stock config, at least we know it works there.
askermk2000 said:
The Lighthouse dev I mentioned has replied. He says that LG has proprietary blobs specifically for IR, and LeEco don't. He'd rather make it work as intended with the blob, instead of using some hacky solution.
So then it makes sense that it work on first try and possibly working normally on gamma - there is some facility already there. Why it doesn't work I can't quite fathom though.
I have looked at source, dtb, configuration... but I may have missed something. I may have to compare to stock config, at least we know it works there.
Click to expand...
Click to collapse
I guess the only reason the IR supposedly works in Gamma is due to proprietary code not released on Github, because i ran through a massive gitlog of its repository going all the way back to january 2016 and there is no relevant commit about LG's IR as well, only the CAF updates seem to change IR files, and those seem to be present on lineage's source as far as the files are concerned. I could also have missed something, but it is highly unlikely at this point. We could at least find someone that managed to make the Infrared work on Gamma and check if they are running the latest ROMs or if the older ones like LOS 16 are also part of the reason why it works there.
And about the Lighthouse dev's response: That's a bummer, LG could have gone with the SDK approach as LeEco did, now i can just hope he manages to port the proprietary IR blobs successfully, since the only alternative left would be to reverse engineer it.
AShiningRay said:
I guess the only reason the IR supposedly works in Gamma is due to proprietary code not released on Github, because i ran through a massive gitlog of its repository going all the way back to january 2016 and there is no relevant commit about LG's IR as well, only the CAF updates seem to change IR files, and those seem to be present on lineage's source as far as the files are concerned. I could also have missed something, but it is highly unlikely at this point. We could at least find someone that managed to make the Infrared work on Gamma and check if they are running the latest ROMs or if the older ones like LOS 16 are also part of the reason why it works there.
And about the Lighthouse dev's response: That's a bummer, LG could have gone with the SDK approach as LeEco did, now i can just hope he manages to port the proprietary IR blobs successfully, since the only alternative left would be to reverse engineer it.
Click to expand...
Click to collapse
Was my conclusion first as well.
I checkout to gamma-pie source and did a quick make, to create .config for H850. Then I compared to lineage h850 config.
There are two options that stand out that are enabled on gamma but not on lineage, those are:
CONFIG_DEVPORT
CONFIG_AUDITSYSCALL with accompanying (CONFIG_AUDIT_WATCH and CONFIG_AUDIT_TREE)
I did see this before but didn't pay much attention, but now that we know blobs are present, perhaps they make use of some of those facilities.
askermk2000 said:
Was my conclusion first as well.
I checkout to gamma-pie source and did a quick make, to create .config for H850. Then I compared to lineage h850 config.
There are two options that stand out that are enabled on gamma but not on lineage, those are:
CONFIG_DEVPORT
CONFIG_AUDITSYSCALL with accompanying (CONFIG_AUDIT_WATCH and CONFIG_AUDIT_TREE)
I did see this before but didn't pay much attention, but now that we know blobs are present, perhaps they make use of some of those facilities.
Click to expand...
Click to collapse
There's also a possibility that those configs are only needed on older android versions, as that gamma branch is for android 9 and we are currently on 11. But nonetheless i will add those configs into my kernel and see if it compiles, then check if the IR status changes, shouldn't be much of a problem. I'll report back in a few hours.
Edit: Managed to test it sooner than expected (thankfully no repo sync was needed on lineage sources), and there was no change whatsoever, the infrared still fails after the first transmit signal.
The audit configs themselves are mostly used to audit file changes in the kernel so it is more of a system admin feature, while the devport one was more promising, since there was a chance that the IR could be using /dev/port as a way to let the apps interact with it directly, and considering how hacky some proprietary code can be (LG messes up even the KDZ recovery files sometimes, like with my old LG Leon, essentially making it unrecoverable), so you never know.
Turns out the lineage kernel source code has all of those configs defined in the files and they were just disabled.
AShiningRay said:
There's also a possibility that those configs are only needed on older android versions, as that gamma branch is for android 9 and we are currently on 11. But nonetheless i will add those configs into my kernel and see if it compiles, then check if the IR status changes, shouldn't be much of a problem. I'll report back in a few hours.
Edit: Managed to test it sooner than expected (thankfully no repo sync was needed on lineage sources), and there was no change whatsoever, the infrared still fails after the first transmit signal.
The audit configs themselves are mostly used to audit file changes in the kernel so it is more of a system admin feature, while the devport one was more promising, since there was a chance that the IR could be using /dev/port as a way to let the apps interact with it directly, and considering how hacky some proprietary code can be (LG messes up even the KDZ recovery files sometimes, like with my old LG Leon, essentially making it unrecoverable), so you never know.
Turns out the lineage kernel source code has all of those configs defined in the files and they were just disabled.
Click to expand...
Click to collapse
Thanks for testing. I'm compiling gamma kernel now to see if it works, else there's no point in messing with that source.
Another interesting bit is module signature. Gamma has modules enabled and signature disabled. Then I though it might
be possible for blobs to be signed and verified in a similar manner as the *.ko modules in lib/modules.
I asked on irc with some knowledgeable folks, and the answer was: yes its possible. but I'll see at least if gamma works as is, if it does then that could be the cause.
askermk2000 said:
Thanks for testing. I'm compiling gamma kernel now to see if it works, else there's no point in messing with that source.
Another interesting bit is module signature. Gamma has modules enabled and signature disabled. Then I though it might
be possible for blobs to be signed and verified in a similar manner as the *.ko modules in lib/modules.
I asked on irc with some knowledgeable folks, and the answer was: yes its possible. but I'll see at least if gamma works as is, if it does then that could be the cause.
Click to expand...
Click to collapse
Understood. As it stands, all modules compiled by the lineage kernel are test modules for TCP, IO Blocks, optional TCP algorithms and other nonessential things, everything else is baked into the kernel itself. The general lack of warnings of any kind pertaining to them also means that everything that should be compiled is being completed without any problems, unless lineage's default GCC and Clang are implicitly omitting those errors. I'm almost releasing my custom kernel here on the V20 subforum as well, so it will be easier to find people to test it too.
Ok, so it seems it didn't work.
I haven't used the phone previously as a remote, but I got Asmart remote on there, and have a samsung tv in standby.
I tried to shuffle through all samsung models pressing the power button, but tv didn't react.
Then I tried looking at the ir led through a phone camera while pressing button and I could not see anything.
askermk2000 said:
Ok, so it seems it didn't work.
I haven't used the phone previously as a remote, but I got Asmart remote on there, and have a samsung tv in standby.
I tried to shuffle through all samsung models pressing the power button, but tv didn't react.
Then I tried looking at the ir led through a phone camera while pressing button and I could not see anything.
Click to expand...
Click to collapse
That's the worst part actually, i only managed to ascertain that it works on the first transmission because my IR app had a preset that worked on my LGTV right at the start. Mi Remote for example behaves just as your app is behaving, where my TV doesn't respond at all to it, so i guess the phone's IR hangs no matter if it sends the correct signal or not. The only difference there is that my H910 still flashes the IR light even after the first transmit while using Lean Remote, but with a massive delay between each cycle and even freezing the app for a while, but still, only the first command is issued.
askermk2000 said:
The Lighthouse dev I mentioned has replied. He says that LG has proprietary blobs specifically for IR, and LeEco don't. He'd rather make it work as intended with the blob, instead of using some hacky solution.
So then it makes sense that it work on first try and possibly working normally on gamma - there is some facility already there. Why it doesn't work I can't quite fathom though.
I have looked at source, dtb, configuration... but I may have missed something. I may have to compare to stock config, at least we know it works there.
Click to expand...
Click to collapse
Issue is most likely kernel related OR consumerIR related. Reason it works on gamma is that it's using an older version of the linux kernel source compared to say los 18.1. After the kernel was upstreamed, Ir broke.