yashsingh1/xdaforums huggingface dataset:
[G2 Android Development] Thunder1D:
I forgot to mention that I have a D800. Not sure how much of a difference that makes when enabling these modules.

Thank you for your efforts!
[G2 Android Development] idkwhoiam322:
Synapse showing device not supported. Cleared cache, app data, reinstalled, error remains :(

RR 6.0.1 , lambda kernel Galante stable
[G2 Android Development] Floodland:
Use Kernel Adiutor and forget about Synapse, ukm, ukelele and all their problems[emoji14]
[G2 Android Development] blastagator:
Synapse needs se-permissive. Check that. Or use Kernel Adiutor.
[G2 Android Development] paul89rulez:
Bootloop for me with turbo rom by zg85
[G2 Android Development] johnb380:
It must be CAF/CM based ROM to work with this kernel.

Sent from my LG-D801
[G2 Android Development] peanutsz:
Thank you GalacticStryder for this amazing kernel and for continuing to update the not so popular phones models like D803!! Really appreciate it man!!

Edit: can someone post some recommended synapse settings? battery is priority but still want snappiness, i dont play any games, Thanks
[G2 Android Development] lunafag:
GPU max frequency keeps resetting to 450, even when you press gaming boost button, with every governor(that works). Otherwise this release is really good, I've been waiting for something like this for almost two years. You have to tune it of course, interactive governor gives some stutters. Impulse is fine but I'm hoping to see smartmax in next releases.
[G2 Android Development] nitrobg:
I can't find 04/08 versions for F320 and 980. Should we expect one?
[G2 Android Development] bamonkey:
Seem to be getting System UI crash on latest AICP nightly with Galante. noticed this on the last N2 Beta as well. This was a fresh/clean install from yesterday just wanted to make sure i was completly fresh. Could be xposed but before that i seemed to be running xposed and everything else i load on my phone normally. attached a catlog and will try to reinstall AICP just with gapps and Galante and see what happens. Thanks for all the awesome work btw ive been following progress closely :good:

edit: Fresh install of AICP just gapps and Galante stuck at finishing to boot. grabbed another for logcat2. A quick lookover i see multiple errors in ThermalEngine but not sure if thats the actual culprit. i have to immediatly kill logcat on generating or else the filesize quickly balloons over the limit.
[G2 Android Development] johnb380:
Wow didn't even notice the new stable release... Now I know!

Go download it people!

Sent from my LG-D801
[G2 Android Development] Mo.Joe:
Lambda Kernel ~ Galante [STABLE][04/08] don't work for me, Boot Loops and what i saw over liveboot thermal issuses with a not found file!?

I have no log sorry, liveboot only saves the last one,...

After a long night i'am back at last PURE release, this works fine.

Thx,

Mo
[G2 Android Development] bamonkey:
What rom are you using? just curious as it seems others are having no issues with the latest stable release. As you can see above i have a similar issue to you on AICP. could be ramdisk issues..could be something else..
[G2 Android Development] Mo.Joe:
I use the latest RR 6.0.1 from 04.0.4.16 (LG-D802)
[G2 Android Development] paul89rulez:
Its caf, i think there is a problemi with thermal driver.

Phone becomes hot, it stucks at finishing boots. It will optimize 2-3 apps then reboots, then bootloop.
[G2 Android Development] edi194:
CM13 Snapshot with stable release works fine.
[G2 Android Development] GalaticStryder:
Yup, any CyanogenMod 12.1 and 13.0 works beautifully with Lambda. The problem happens when people install an uncertified firmware (aka ROM), if the ROM developers add things like AdBlocker and such services that need permissive selinux, it will obligate Lambda to refuse all the denials and may not work as intended, giving FC and crashes. Same for xposed and such services. Why not just switching to permissive by default?

https://wiki.gentoo.org/wiki/SELinux/Tutorials/Permissive_versus_enforcing

CM ships their firmware on enforcing by default, it has a purpose. Previous releases were set to permissive although you could turn it on on terminal, app or in Synapse. I may do that if the problem persists for those problematic projects.

Synapse does run on enforcing, not sure who said it doesn't, anyway. If you see a "Device not supported". That's another issue related to bad development. The filter I used catches the device from build.prop, CM sets ro.product.device property to be the device name this way:

d802. If the developer uses D802 or g2int or another that isn't d802, it won't recognize and throw device not supported error. There's no blaming on kernel for this one as well.

Why to use Synapse? How are you going to control things like force fast charger if you don't use it? Even though you see an entry for it in Adiutor, it's placebo, it won't affect the 2 sysfs entries needed for dori's fast charger. You won't get the GPU booster, gamma control and all the clarification about features that I added to my UKM/Synapse.

I'll rebuild all devices today and push with selinux set to permissive. People that don't have Synapse working cause of bad property in build.prop can edit the file to pass the verification.

ro.product.device=D802

Change to:

ro.product.device=d802

As an example.

I hope you sort that out! I'm writing a FAQ today to be READ before installing.

Wish you a good day.
[G2 Android Development] jeebspawnshop:
Another thing that may be of interest;

http://xdaforums.com/showpost.php?p=66259568&postcount=7591

(Unsure if it applies to your kernel, but worth a look)
[G2 Android Development] edi194:
[MENTION=6175749]GalaticStryder[/MENTION] I'm using Xposed and AdAway with this kernel, Synapse works correctly and every other app runs smoothly without problems with SeLinux enforcing (V4A installed correctly too, but here is patch for it) :P So problems are with ROM's, especially with latest buggy CM13 releases.
[G2 Android Development] 4r44444:
Hey OP I would be glad if you could back Intellimm governor, with it I had after day 20% battery left and now with any other govenor after half day 30% left with same or lower usage. Greetings
[G2 Android Development] rstorabb:
Anyone know why when I install stable or n2 beta I have no sound at all on cm13?
[G2 Android Development] johnb380:
You guys make sure when flashing the kernel you try it after the first boot of a clean flash. That's what I did clean flashed then went through the setup and all that then I rebooted to recovery and flashed kernel and everything was well then!

Maybe try it or try different roms! I can def recommend Mokee ROM it is very stable and fast and doesn't seem to have any of cm13s issues like most other roms heres the link... http://xdaforums.com/showthread.php?p=64400059

Just make sure you clean flash and setup then reboot into recovery and flash kernel and profit!

These 2 together are awesome!

Sent from my LG-D801
[G2 Android Development] GalaticStryder:
What variant? We use custom mixer paths, maybe it doesn't for your device. I didn't change a thing on sound drivers. Also, use a decent firmware, always.
[G2 Android Development] rstorabb:
D802. sound works with stock cm kernal but not lambda.
[G2 Android Development] jneto3000:
I flashed Beta N2 on Turbo ROM. First boot it bootlooped (and only first boot) :confused:

But after that, no more bootloops and all worked fine. :victory: :good:
[G2 Android Development] GalaticStryder:
I'm on D802, many users are as well and all fine here. Audio, video, bluetooth... everything. Could you test clean flashing the latest nightly? I'm on 04/08 version.
[G2 Android Development] rstorabb:
I have just clean flashed the latest nightly but still same issue. I notice the audiofx app gone too. Anyone know where I can find n1 beta d802? That was last one it worked with.
[G2 Android Development] blastagator:
What ROM? I am on cm13 4/8 (and previous nightlies) and synapse doesn't work in enforcing. I checked my build.prop as suggested. Hmm... :confused:
[G2 Android Development] edi194:
As i said before, i'm on cm13 snapshot, becouse it's working better than nightlies from this week :cyclops:
[G2 Android Development] Floodland:
In my experience, selinux is trouble. Everything works best with it completely disabled (not permissive, disabled). At least with Turbo and Broken ROMs, you are right, that is certainly related to the issue with your kernel refusing to boot.

In my particular case stable version from last night only booted in safe mode with turbo ROM, without showing anything on screen but the indicator that it was in safe mode (first time ever I see safe mode with our devices). The kind of thing selinux generates... No last kernel log is available after reverting to its default one. Will wait until the new build to try again.

Please think if disabling selinux (and killing its developers [emoji14]) won't be a benefit for the community. No? Ok, just disable it, if it doesn't kill ROMs which compiled the malware in the first place.

Regards
[G2 Android Development] rabinorojo:
Thanks for that great kernel job.

Could be adapted to F-320L/S/K ?
[G2 Android Development] jneto3000:
I didn't see 04/08 build. Thought the newest was Beta version. Gonna flash the Stable 04/08 soon.

I have Beta N1 file here. If the dev allow me I can upload and post the link here or via PM for him.
[G2 Android Development] Mrondo:
RRs and random FCs on CM13 04/09 nightly with the latest stable release, D801. Had to go back to the N2 Beta, which works flawlessly. Both Synapse and V4A don't work on my setup with SELinux set to enforcing
[G2 Android Development] johnb380:
Viper and Synapse are both working just fine with the newest stable release and every release before this and selinux is on enforcing. [MENTION=6175749]GalaticStryder[/MENTION] has added boot scripts to allow for these to work with enforcing selinux. Idk why anyone is having problems.

Sent from my LG-D801
[G2 Android Development] Floodland:
Just because SElinux is harmful. We are using custom ROMs, Android and Linux because we want freedom, and SELinux goes against it, interfere, restrict and sits over everything, disabling access without asking first, imposing how software should work just because they say so... This is not news, we are suffering SELinux for quite some time now. Corporations try to push it because they assume consumers do not understand anything and should not have the choice to decide if a software should access the system or not. They do not want people touching "their" systems... Kind of philosophic position.
[G2 Android Development] shaneel1491:
Is there a Simple thermal driver alternative being implemented on this kernel, cause monitoring the CPU while doing things on performance governor with high CPU loads and thermal driver disabled (and enabled and set all parameters to max CPU) the CPU throttles quite a bit, or is this built into the hardware to avoids overheating and killing the chips?

Thanks for the great work!

Edit: Nvm, found out it was probably built into hardware, as it went to 90 Celsius and shut off! :)
[G2 Android Development] GalaticStryder:
Ok, I'm fixing all the mess right now. All builds were taken down until I finish the support for everyone.

1st. People that have device not supported in Synapse. Open your /system/build.prop and post the entry for: ro.product.device. I'll add your entry to the official naming scheme in case the developer did change it.

#Official
case $DEVICE in
d800|d801|d802|d803|f320|l01f|ls980|vs980)
CONFIG="galbi";; #LG G2
esac;

This is the official naming scheme from CyanogenMod and all its forks should use the same, CM is the only LG G2 tree as of now.

2nd. SELinux is set to permissive, you can enable it if needed on the terminal app or in Synapse.

3rd. The FAQ is almost done, read the whole thread before flashing if you are a newbie, the old dudes should do the same every once in a while to check new features, changelog...

4th. I test fast charger today, it's doing the job. The default LG G2 charger goes all the way up to 1830mA in here and maintains about 1790mA of average.

5th. The GPU boost button is just a helper, I won't add OC to 650MHz when using it cause it's fairly not needed. I played a little bit of Pacman Maze 256 on 533MHz OC and Adreno Idler set to performance, all fine, the temperature was held with easy by simple thermal.

Pretty cool? All the downloads will be up when I update this post. #StayKissing
[G2 Android Development] ramabg:
I think I have figured out why I got bootloop after I flashed the stable. Previously, I set my SE Linux to permissive on Beta then I flashed Stable, which cause bootloop. After I reflashed the Beta, turned SE Linux to enforcing, then flashed the Stable, the bootloop had gone. In addition, I installed Xposed and SuperSu from Chainfire. My phone is D802.
[G2 Android Development] xxoscarxx28:
I don't think there are any problems with synapse... I once have this "UCI not supported" message and all that I did to make it work is open up the terminal, then "su -c uci"

Open again synapse

Benefit
[G2 Android Development] bamonkey:
*Edit* Ignore here. Latest Aicp was working on first boot with Galante but after reboot appears to be back to issues...weird stuff going on as i track down the problem.

*Edit Edit* Okay seems to be working again. not sure what the difference was. To duplicate going BACK to working i flashed the pure version and confirmed working and then just tried galante stable and seems to holding even after reboot.
[G2 Android Development] nitrobg:
F320L bootloops on the LG logo with the 0410 kernel. Everything is fine on the earlier versions.

The ROM is Dirty Unicorns 9.8 (CM12.1).
[G2 Android Development] lash444:
Not sure if this was resolved, but I too had the issue with N2 causing a loss of sound on videos. VS980 running CRDroid 04042106. Flashing N1 back to the device didn't even resolve it. When the video is playing, if i hit the button to raise the volume, it doesn't show the media volume icon. Instead it shows the phone volume being raised/lowered.
[G2 Android Development] Floodland:
Just to report, latest stable version rocks! Everything I tried working as expected, testing impulse with sioplus, really smooth. R_24 might help as well.

Great job! Just let me know if you need to test something in particular.
[G2 Android Development] bk2601:
Just installed on D802.

Wanna ask. I noticed that default freqs are 2,8Ghz CPU and 650Mhz GPU. Is it safe?
[G2 Android Development] adriannxda:
Latest stable running great.

Excellent kernel))

Trimis de pe al meu LG-F320 folosind Tapatalk
[G2 Android Development] johnb380:
Yes it's safe because [MENTION=6175749]GalaticStryder[/MENTION] has implemented and tweaked the simple thermal driver to make it safe but everyone has to run the device their way, so if you don't want or need that high of freqs then change it via Synapse. I personally use 533 for GPU and 2.5ghz for CPU because I don't need the faster ones. But each person has to figure out their own way or just try stock settings out for a day or 2 and see.

Good luck and have fun!

Sent from my LG-D801
[G2 Android Development] 4r44444:
Had Reboot while performing Antutu Benchmark, what logs do you need?
[G2 Android Development] GalaticStryder:
All of the logs and your configuration. I'm testing AnTuTu here although it's pointless. Benchmarking worked just fine, not sure if your logs will report a kernel issue. I'm using the latest RR for testing and as I said, all fine on AnTuTu, GeekBench3 on the latest kernel that I pushed today.
[G2 Android Development] 4r44444:
https://drive.google.com/file/d/0B5zPrCJoNwCDS1dxTFFORGlheW8/view?usp=sharing

https://drive.google.com/file/d/0B5zPrCJoNwCDTkpMVlloVndHc3M/view?usp=sharing

I did Antutu again and the restart was again, Phone restarts at second benchmark.
[G2 Android Development] szabyka95:
i guess bcz of silicon lottery, what works for dev for x settings not neccesarily works for you too (e.g. undervolt, overclock)
[G2 Android Development] GalaticStryder:
All Adiutor settings are messed up on your boot settings, vdd_restriction, sound control... We don't use 'em. Also, Xposed has crashed several times on this logcat. Clean flash your firmware, do the setup and go back to recovery to install the kernel. Do the AnTuTu benchmark again, it will work as intended. Use Synapse, it's not beautiful but works.

Stock Kernel settings, should have a much better performance on a cleaner UI (without themes and this bunch of customization I made for stress testing).

OBS: Everyone knows this is useless...

OBS2: Geekbench multicore score is much higher when benching on a full battery + untouched CyanogenMod in terms of UI (no theme). The singlecore score is almost the same.
[G2 Android Development] Mo.Joe:
I managed to separate a boot loop log.

Lambda Kernel ~ Galante [STABLE][04/08]

Meanwhile with a clean RR flash.

Please have a look.

Thx ,

Mo

https://www.dropbox.com/s/0f2e6s7swppffoz/liveboot.log.7z?dl=0

**EDIT**

Same Problem with the latest Kernel

Lambda Kernel ~ Galante [STABLE][04/10]

https://www.dropbox.com/s/xha4sb6galc1p8p/liveboot.log.04.10.7z?dl=0

Gesendet von meinem LG-D802 mit Tapatalk
[G2 Android Development] GalaticStryder:
Clean flash the firmware + gapps. Set it up and flash kernel back again, what version/date of the build are you flashing? I tested 04/09 build and it's fine, I'm gonna stick with SlimLP for now, all the new releases with cmsdk are as buggy as I can say "Rechtsschutzversicherungsgesellschaften" from back to front. Oops looks like SlimLP server that had all the builds went down.
[G2 Android Development] pipyakas:
sr for OT but where did you got a RR-M for f320? i cant find it anywhere :confused:

for the stable G release, is there anyway to flash it while using permissive SELinux? Im using permissive and i got bootloop after flash the kernel, so im reverting back to beta N2 and try to change it to enforcing.

The problem is that i also have v4a and v4a can cause bootloop on enforcing selinux i believe? so it's kinda confusing

edit: i redownloaded and dirty flashed the stable build again and it worked :)
[G2 Android Development] johnb380:
New kernel is already Permissive ...

Sent from my LG-D801
[G2 Android Development] pipyakas:
I got bootloop after flashing the kernel so i thought it was permissive problem :)

but now i actually know what was the problem, it only works if i dirty flash the kernel, once i wipe cache & dalvik the system messed up on first reboot and if i reboot the phone it will bootloop

I dont know why, but when i flash the kernel then wipe cache & dalvik in twrp, upon rebooting it doesnt seem to do the "optimizing apps" thing and everything oc really hard

I even got a storage shortage notification while having 9gb free in the internal storage :confused:

Im using bliss 6.2, is there anything wrong that i did or is it a problem and can i provide any info?
[G2 Android Development] johnb380:
I'll bet your using xposed huh? If not then it sounds like you may need a clean flash my friend if you do go to clean flash just flash ROM and gapps then boot up set up your phone then reboot to recovery then flash kernel and reboot to system then you should be good.

FYI xposed modifies your art cache and that may be the issue.

Sent from my LG-D801
[G2 Android Development] pipyakas:
thanks for the advice, i will try clean flash, i just never expect this issue since it never happened before, all beta version worked fine with xposed, and my battery has gone from 80% to 9% due to all the flashing restoring this morning so

Hope that everything go smoothly, as for the kernel as well :)
[G2 Android Development] xxoscarxx28:
F320 bootlooped on Galante Stable 4/10
[G2 Android Development] Mo.Joe:
I don't understand, why the "Galante" - Kernel is such delicate. For me "Galante" is not stable, but i'am not a pro in flashing.

I factory resetted my phone (wiped all partitions) and formated data partition, then i flashed the stack RR04/09 / Open gapps / "Galante" with bootloop.

If i do this with Pure, it works fine, what is the difference? Why so complicated with setting up RR and flash over "Galante"?

I will test it in the next days,....

Thx for your work!

Mo

**EDIT**

Could be the hybrid bootstack a problem? ([BOOT][CAF & STOCK][ALL-VARIANTS] G2 Hybrid Bootstacks from daniel.stuart14)
[G2 Android Development] pipyakas:
It seems that a lot of f320 users are having bootloop problems

I can only get it to work if i remove the battery then plug it in again then reboot, because i cant even force shutdown the phone by holding the power button

And also i think the 2.8ghz cpu oc is causing some reboot problems too, in the case of bliss it has both kernel adiutor and a power profile selector, and changing settings between those 2 makes some settings in kernel adiutor doesnt stick, which in the end cause the max cpu clock go to 2.7 and 2.8ghz, cause reboots. My f320 can only handle up to 2572mhz without any problems or thermal throttling, and i consider not so many other g2 can do that either :eek: while 650mhz gpu oc is fine :highfive:

edit: maybe something like an aroma menu to choose the max cpu clock while installing the kernel like elementalx is good for this situation, i dont know if it's hard to do or not but you may take a look at that approach :)
[G2 Android Development] seyrine:
F320 chiming in with no problems. I just flashed the new stable build over the beta N2, wiped the cache as prompted by twrp and rebooted. I'm on Blisspop 3.4 with xposed and the latest hybrid bootstacks, performance is excellent. Battery life on standby is great too; I unplugged at 3am and finally got to 15% battery by 6pm, with 4+ hours SOT. No issue with heat as well during an extended gaming session of Mupen64.

Make sure you disable all auditor settings, then disable the app in settings before doing anything with synapse. Preferably before flashing the new build.
[G2 Android Development] johnb380:
Who is all these other people? I only see you and one other with issues. If your having problems where is your dmsg log and last kmsg if your getting reboots. I suspect that you are changing something in xposed that is messing up your phone and it has nothing to do with kernel. Or that your kernel.settings are corrupted. Try to remove Synapse and kernel auditor completely before flashing kernel then reinstalling and setup and also remove xposed and trying with just ROM gapps and kernel. Then I believe your problems will be over.

Sent from my LG-D801
[G2 Android Development] android extreme:
Personally i can't believe that a sd800 can't handle max oc on both gpu and cpu, for sure there is a problem in your rom/mod configuration. Try to make a clean flash install an AOSP CAF rom and flash the kernel without any mod

Someone know a changelog for the 10/4 kernel release?
[G2 Android Development] pipyakas:
You asked for it, here it is

I did a full wipe, means wipe data + cache + dalvik + system, flashed bliss 6.2+ pico gapps 6.0, rebooted, removed kernel adiutor, then rebooted again then flash the kernel

Then i download synapse, and the moment i open synapse the phone freeze and reboot

But it got stuck in the LG logo, and i have to pull the battery out

While i trying to reboot it got bootloop at the boot animation, or the screen go black completely, really i have to pull the battery out for 2-3 times

When i got it to boot properly i try to get these logs in synapse right away, if those doesnt help please tell me what to do, since i want to use this kernel and im not making stories up or something

I did tried to do OC on 3 different G2, a d802, a l01f and now a f320, all 3 of them can be oc up to 2572mhz cpu without thermal throttling, reboots etc.. 650mhz gpu oc work all the time, in stock kk and lp with dorimanx kernel

Maybe it's bliss problem, if that's the case then i will try on other roms

The one part that i dont get it is beta N2 work since it came out, no problem, i did revert back to that version and there is no problem to be found compare to the stable one