yashsingh1/xdaforums huggingface dataset:
[G3 Android Development] imnm:
same issues...

Yup I had same issues, this morning updating my purity rom and acc kernel too. everything was good with 1.2 but today flashing 1.3 messed up something...my phone screen was black, then i pulled out my battery, rebooted and the phone was freezing after a while on, then i've managed to enter twrp and tried to flash acc 1.3 and some errors popped out "failed to mount /system (invalid argument), failed to mount /cache (invalid argument)" so no boot anymore just stuck on bootlogo and even trying to restore my twrp backups didn't fix the prob.

i've tried almost everything... :/

not blaming anyone btw... **it happens
[G3 Android Development] hean_burak:
I meant interactive or something else. I would like to help but don't know about this issue. Hope [MENTION=3585838]djdeeles[/MENTION] can help

LG-D855 cihazımdan Tapatalk kullanılarak gönderildi
[G3 Android Development] Alukrad:
Logcat?

---------- Post added at 04:56 PM ---------- Previous post was at 04:43 PM ----------

Send logcat to dev. Also try changing the ROM you're using. Since RR is mostly CM based that could be conflicting with some code of the kernel. And yes, some ROMs arent compatible with some kernels
[G3 Android Development] djdeeles:
Maybe it's related to bootloader problem that mentioned in cm thread take a look.

I had two random boot with v1.2 but after v1.3 that's solved. No reboot even with lover voltages. I need logcat about reboots if someone had.
[G3 Android Development] imnm:
since i had no chance to boot my phone again...i've flashed kdz and thanks it saved my day
[G3 Android Development] Alukrad:
Resurrection Remix has always been a problem with custom kernels. From lag problems to random reboots to bad GPS issues. Try to stick to AOSP based ROMs. It's a much better experience
[G3 Android Development] Emu:
Answering the poll you should keep all of them. There are workarounds and what works for one may not work for others.
[G3 Android Development] matt4321:
Cleaned up this thread a bit.

Look if you want to put your phone in the freezer go for it. But we're not going to allow discussion on it as it is just going to lead to issues and unforeseen problems with devices.

Please remember when you use unofficial software there is likely to be issues so be careful.

Forum moderator,

matt4321
[G3 Android Development] Alukrad:
Thank you sir.
[G3 Android Development] matt4321:
Thread reopened, please post on topic and relevant to this kernel.

Forum moderator,

matt4321
[G3 Android Development] Abrilabr:
This works only on MM? Or maybe 5.1?
[G3 Android Development] :
Nope. Kit kat. We be rollin old school... ;)

http://xdaforums.com/showpost.php?p=65578404&postcount=9
[G3 Android Development] Abrilabr:
Damn, i wanted it to be compatible with JB :(

Another question, does Synapse work with it? Cuz in MM most kernels give problems
[G3 Android Development] :
JB FTW!

No UCI support with synapse. You can use the modded KA though... http://xdaforums.com/android/apps-games/kernel-adiutor-mod-singularity-kernel-t3333549
[G3 Android Development] Emu:
If you can, try to get the March 2nd update of BlissPop. Not the current one. In my experience it is by far the most stable and smoothest ROM at least for T-Mobile's G3. The only disadvantage is that the proximity sensor is broken, but that hasn't been fixed yet and it's been an issue with all CM-based ROMs
[G3 Android Development] Alukrad:
Yikes, you totally need to try Dirty Unicorns. No broken things, most stable ROM, TONS of features. Gave up on bliss and RR alonnngg time ago. Once you go DU I promise you'll never go back.

---------- Post added at 08:31 PM ---------- Previous post was at 08:24 PM ----------

http://xdaforums.com/showthread.php?t=3335522

Do eet
[G3 Android Development] Emu:
Bah! I had AOKP and DU on my previous phone. But I just read they switched the base... hmm ok. I will
[G3 Android Development] Alukrad:
Yes sir. The thing is built so well, my phone has been near bulletproof. Not even as much as a hiccup.
[G3 Android Development] levider:
The Best kernel for me

Keep good working :)
[G3 Android Development] djdeeles:
I have created two polls about cleaning govs & hotplugs please chose what you want to remain in this kernel.

http://goo.gl/SYlqVJ and http://goo.gl/ejZJv5.
[G3 Android Development] eric93se:
I say, whatever works leave it in there. There are few of us users that are willing to take the time to try every single option (wow there are so many) and choice is always good. Not to mention not many who can tell how well an option is working or if its working at all. How much performance would we gain from a lighter kernel? I can't imagine it's going to be a whole lot.

Kernel is running awesome BTW :D

I got a new battery and battery life has been insane, also switched to Team Exodus (AOSP) which is light weight and they must have fixed some leakages because the rom idles really well.
[G3 Android Development] Emu:
I have found ultimate proof making zzmove redundant (thanks for the hard work tho zanezam). You can get zzmove type of behavior with two damn tweaks. One you switch to Alucard governor and hotplug and lower the minimum clock speed to the lowest that you can get. Maximum whatever you are convenient with. Then in the Alucard hotplug setting, limit the max # of cpus to 2. Now look at how your CPU behaves. Not only is it like zzmove in terms of battery life, but it retains the smoothness of Alucard.
[G3 Android Development] :
May someone recommend me other kernel settings? I have already set the CPU gov and hotplug gov to Alucard. I have been using this combo for quite some time and I'm ready to try out some more settings to make my G3 even better. :) As for fast charge, do I just enable the toggle? Will it work right away?
[G3 Android Development] djdeeles:
Update:

I'm working on state notifier. Its working fine but it needs more work. Some hotplugs & govs will be removed according to poll.

Next week new test version will be out.
[G3 Android Development] fmehdi:
I like your kernel but when i use your kernel is laggy compared to stock cm kernel

Im disabling adreno adler but no effect is still laggy

Good work brother
[G3 Android Development] djdeeles:
UPDATE TEST VERSION: v1.4t1

Test version posted for D855 in test folder.

- Replaced Powersuspend with StateNotifier

- Removed Mako hotplug becouse its never worked

- Removed Fast_Plug

- Updated hotplugs to use StateNotifier

- Some Sched patches

- Disabled Adreno idler at startup for smoothness

- Default Gov & Hotplug is set to Alucard

- Zzmoove updated to dev branch

- Enabled Dynamic refresh rate between 50-60hz
[G3 Android Development] denf666:
great ! "Default Gov & Hotplug is set to Alucard"
[G3 Android Development] ROKO__:
* Anykernel Ramdisk Format (Compatible with all ROMS)

so is this mean that will work on stock MM rom ?
[G3 Android Development] djdeeles:
Yes but kernel might not be compatible. It's for aosp roms especially cm.
[G3 Android Development] Roi007leaf:
State notifier doesn't stick in modded ka
[G3 Android Development] djdeeles:
KA problem,it shows state wrong. It's always running after boot. You can check in terminal with "ps | grep state_susp_wq" command.
[G3 Android Development] Roi007leaf:
Sweet, thx
[G3 Android Development] v.konvict:
So far everything is smooth with test kernel
[G3 Android Development] Jake2kOne:
This Kernel, like every other Kernel (777 and Nebula) , gave me too often "not charging" message on my D855-CM13. Gone back to stock kernel and now it's charging properly.

No idea why...

Will test further versions.

But what I can say so far: This kernel runs stable, no BSODs or so like with Nebula (no idea why, now idea when).

I will still use all kernels when there are new versions... ;)
[G3 Android Development] djdeeles:
Do you use original battery & charger?
[G3 Android Development] Jake2kOne:
Yes and no

Original battery but I'm using several wireless chargers (home, work, car) and other wired ones.

With every custom kernel I have problems since a few weeks or so. On stock kernel it's fine with every charger I own (even with the not "QC 2.0 compatible" cables).
[G3 Android Development] djdeeles:
It's because custom kernels have higher charge current. Your adapters can't give required current.
[G3 Android Development] @AdairJunior:
Hey, where do I find a download link to the CM13 stock kernel?
[G3 Android Development] Emu:
hey djdeeles, can you figure out this strange bug I get in almost every ROM for D851? It does not cause any major issues but I do think it has a small effect on performance.

The error occurs whenever I touch the status bar, scroll up or scroll down the notification. Yes I have tested multiple kernels, stock and custom and tested across ROMs (Bliss and DU), this is the error I get after I flash this kernel:

http://hastebin.com/hoqepaqiqa

03-26 09:53:58.195 E/ANDR-PERF-MPCTL( 1092): PERFLOCK Failed to connect to socket: errno=111 (Connection refused)
03-26 09:53:58.195 E/QCOM PowerHAL( 1092): Failed to acquire lock.

Scroll to bottom to see repeated errors. They happen whenever there is a touch input by me as I said, especially when I touch the status bar... I hope you can repeat the error and fix it.
[G3 Android Development] edoardotavecchio:
I found this bug on my previous smartphone, using a custom kernel: this happens because you're not using stock Mpdecision hotplug, there is a difference through the two hotplugging driver's touch boost, and this creates this boring log. [MENTION=3585838]djdeeles[/MENTION], if you're interested into it, a solution (the one that was used by the custom kernel's developer I was talking before), is creating a mod for the file power.msm8974.so in /system/vendor/lib/hw, and replace the modded file with the stock one. It's not a comfortable solution, but it works if you're don't find any other way to solve it. You can find more informations here: http://xdaforums.com/galaxy-s3-neo/orig-development/kernel-cyanogenmod-12-1-overclock-1-593-t3230195

This is the custom kernel of which I was talking about before, through the posts there are some talking about the problemi and redirecting to the original xda thread where the problem was discussed and solved.
[G3 Android Development] Jake2kOne:
Just install a cm13 image. No matter if the current or any further one.
[G3 Android Development] Emu:
Thank you. I couldn't find the modded zip file.

http://xdaforums.com/galaxy-s3-neo/...lock-1-593-t3230195/post63807540#post63807540
[G3 Android Development] edoardotavecchio:
The modded zip file refers to the msm8226 chipset, that is the one that's used by galaxy s3 neo, the modded file have to be created by a dev or by your own (if you think you're able to) for the selected chipset (in our case I think it's msm8974, correct me if I'm wrong). I don't know how to do that, maybe you or [MENTION=3585838]djdeeles[/MENTION] could contact [MENTION=6370385]Renix63[/MENTION] (the s3neo kernel dev) to ask how he fixed that bug.
[G3 Android Development] djdeeles:
You can delete that file to solve error but a down side dt2w not works or you need to build rom without mpdecision & thermal support.
[G3 Android Development] cultofluna:
Didn't work for me ..end on bootloop

D855 NN 3.0 STOCK 30C
[G3 Android Development] Emu:
Aww thanks for the info. So there's no way to mod the file to have both? I mean other kernels do not have the error. Does the error have any negative effects in your experience? I rather deal with the error than to sacrifice dt2w or thermal support but it would still be nice not to see it.
[G3 Android Development] snoop5:
This is working for me and I'm on Fulmics 2.7 so I guess works for some on stock and not others
[G3 Android Development] Taracair:
Using it with Dirty Unicorns ROM. Seems pretty good so far. Phone stays cool and the performance together with this ROM is just great. Zzmove and bricked hotplug gives good SoT. More feedback soon.
[G3 Android Development] Reli4nth:
zzmoove has its own hotplug integrated, you should disable bricked and all extra hotplugs to avoid problems.
[G3 Android Development] Taracair:
Didn't know, thanks for advice.
[G3 Android Development] djdeeles:
Or you should set disable_hotplug to 1 in zzmoove options.
[G3 Android Development] marcdw:
Yes. With some ROM/kernel combos performance is better with that set and using external hotplug instead.

LG-D851, MoKee Open Source LP ROM, Tapatalk 4.9.5
[G3 Android Development] djdeeles:
V1.4 is up

v1.4-- 12.04.2016

- Replaced Powersuspend with StateNotifier

- Removed Mako hotplug becouse its never worked

- Removed Fast_Plug, Thunderplug, Msm_Sleeper

- Removed Darkness gov (next version will remove more govs according to poll)

- Updated hotplugs to use StateNotifier

- Alucard Hotplug updated

- Some Sched patches

- Disabled Adreno idler at startup for smoothness

- Default Gov & Hotplug is set to Alucard

- Zzmoove updated to dev branch

- Enabled Dynamic refresh rate between 50-60hz
[G3 Android Development] hean_burak:
Is there any difference between this 1.4 stable and beta?

LG-D855 cihazımdan Tapatalk kullanılarak gönderildi
[G3 Android Development] djdeeles:
Yes, especially alucard hotplug.
[G3 Android Development] edoardotavecchio:
You should update thread's title, to avoid confusion about kernel's latest version ?
[G3 Android Development] denf666:
often "not charging" on D855 (Dirty Unicorns v10.1).

with Kernel 777 and Nebula no problem. i dont known why
[G3 Android Development] Jake2kOne:
Had the same problem, but with 1.4 it's not happened again so far.

Using it with cm13.
[G3 Android Development] Emu:
Smoother than ever. Thanks
[G3 Android Development] TheWolfer22:
I'm using this kernel with AOKP rom on mi D855 and it works well, i haven't had "not charging" problem. For now i must test how is the battery autonomy using this kernel with the default alucard governor.

Enviado desde mi LG-D855 mediante Tapatalk
[G3 Android Development] levider:
What gov, hotplug etc are you prefer guys ? :)
[G3 Android Development] aaanadie:
Some special procedure to switch from Nebula to this kernel?
[G3 Android Development] FaySmash:
I had HUGE problems when I flashed acc over nebula. (all cores stayed online, max clock locked to 700mhz ect) I suggest flashing your curent rom again and than acc on top. that what I do to be sure that everything works proberly. but you can try to dirty flash acc over nebula but if it lags or gives huge battery drain it's because of the dirty flash.
[G3 Android Development] Emu:
I noticed that SELinux was set to permissive. Can I set it back to Enforcing or are there any settings in the kernel that need it to be permissive?
[G3 Android Development] marcdw:
Use Kernel Adiutor-Mod by Yoinx. It has an SELinux switcher built-in. It's worked for me.

LG G3 D851, PAC-MAN ROM, Tapatalk 4.9.5
[G3 Android Development] Koont:
Found out the hard way but, the process you described worked. And so far, this Kendall is kick a$$. No black screens, no heat. So far. Thanks.
[G3 Android Development] Nakashima Taiki:
SeLinux

Is this kernel permissive? Sorry if I repeating other's question.
[G3 Android Development] marcdw:
Ach, I got confused. ?

Deleted.
[G3 Android Development] Nakashima Taiki:
XOSP

Does anyone have luck running this kernel on XOSP rom? I stuck at the boot logo. Some help would be great.
[G3 Android Development] djdeeles:
No. Its build enforcing.

You need to dirty flash rom first if you'r coming from another kernel its same procedure for all kernel changes.
[G3 Android Development] huzefaonline:
Had the same issue. Despite all the efforts, it didn't boot. Using xosp with its stock kernel.
[G3 Android Development] japin:
Use Nebula kernel if you at least want something different.
[G3 Android Development] THEBANDIT420:
Can't seem to get max GPU frequencies to stick, always reverts back to 627 MHz anyone know how to stop this?
[G3 Android Development] Alukrad:
having the same problem but I'm stuck at 389mhz max. On V 1.4 of the kernel D851 on Dirty Unicorns ROM
[G3 Android Development] EternalFlame:
Guess it could be a GPU frequencies thermal throttle thingy?

Had the same problem as you guys but since i managed to stay under 50°C CPU Temp, GPU frequencies stick.
[G3 Android Development] Alukrad:
Possibly. Gonna pair it up with CTT Thermal mod and see how it flies
[G3 Android Development] levider:
+1
[G3 Android Development] Abrilabr:
+1

My phone is overheating a lil bit, i think underclocking GPU could reduce the temperatures
[G3 Android Development] Emu:
I have noticed an issue since using this kernel. It is incredibly smooth for around the first 12 hours. But, after that it becomes laggy for some reason and it's the type of lagginess I can only remove by soft rebooting. I am not really able to reproduce this issue other than telling from my experience. It usually occurs when the screen has been off for more than 1 hour. Something seems to happen that just doesn't work right and causes scrolling to be laggy. This is definitely not due to the governor as I had the same issue with zzmove or Alucard.

Does anyone here know how to fix the issue? If I find a solution I will share of course :D
[G3 Android Development] Alukrad:
Reflash back to 1.3 ver and see if the problem persists and go from there. So far new version has been kind to me. Are you underclocked? What ROM are you running currently? Do you like to flash all the things?! >.>
[G3 Android Development] Emu:
No. That issue has been with me since I can remember flashing any kernel so I will keep on searching.
[G3 Android Development] Ufoex:
how change SElinux to permissive in this kernel?
[G3 Android Development] marcdw:
If you're ROM doesn't have a switch for it use Kernel Adiutor-Mod. It will allow you to switch.

LG G3 D851, PAC-MAN ROM, Tapatalk 4.9.5
[G3 Android Development] Taracair:
Does this kernel support Slimport adapters? Does it need to be supported by kernels or always work by default? I cannot get it working with DU ROM and this kernel. It was working properly on XenonHD LP before with Nebula kernel. What is more - I've got another LG G3 D855 (lowmem variant) and it doesn't work with pure stock ROM. Any ideas why?
[G3 Android Development] Alukrad:
if I recall right there's a difference and usually two separate kernels for lowmem and regular versions of D855 and I think this is for the regular version. I'm also using DU and have this kernel on with no issues.
[G3 Android Development] hean_burak:
[MENTION=3585838]djdeeles[/MENTION] Hocam bir de cm lolipop için yapsan harikulade olur. Bizimkinde adam akıllı bir kernel yok.

Looking forward to a lp kernel with these features.
[G3 Android Development] DaveKing:
Me too. Incredible how the horrible 6.0.1 gets more kernels than the excellent and stable 5.1.1 Lollipop. The only thing it lacks is kernels for who don't give a damn to Google SDCard Block Policies and will keep LP forever. It's a shame how developers nowaday forget the essence and what it's important. Big cheers to Eliminator74 for being different until now, and his Nebula with 5.1.1 support.
[G3 Android Development] RapHaeL_4_4_4_:
The dev do what they want, they work on their free time and you are still not happy?

If you want a kernel for lollipop so bad then you can always build your own.
[G3 Android Development] death_syndrome:
hello there :)

it's been a while since i last rooted and played around with my phone so i have a question!

in order to flash this kernel i should be running an AOSP rom first? meaning i should flash the rom first then i flash this kernel or is it vice versa?! or is there any other process i should go through?!

thanx in advance
[G3 Android Development] Sloba89:
+1 for LP kernel if you have time! :)
[G3 Android Development] hean_burak:
[MENTION=3174460]death_syndrome[/MENTION]

1) Flash rom, gapps etc.

2) Flash kernel.

Kernel must be flashed after rom. This kernel is made for cm based roms. So it should work with aosp as well.
[G3 Android Development] death_syndrome:
thank u
[G3 Android Development] EternalFlame:
[MENTION=3174460]death_syndrome[/MENTION]

But wipe caches via recovery before flashing a custom kernel to avoid unexpected effects :cool:
[G3 Android Development] denf666:
need i buy a fast charger for the fast charging option in KA Settings?
[G3 Android Development] Mr. Jedge:
Phone was fine until I rebooted it, and then the phone boots but the screen remains black. Had to reflash ROM. Any ideas?
[G3 Android Development] Windforce0511:
Very good results.

Which hotplug, cpu gov, i/o scheduler for performance? Do I need CTT mod with this kernel Thanks
[G3 Android Development] Alukrad:
CTT optional
[G3 Android Development] Roi007leaf:
No boot on stock rom
[G3 Android Development] Alukrad:
this Kernel is NOT for stock. Only AOSP and CM based
[G3 Android Development] Roi007leaf:
Ik was just doing it so if anyone thinks about it they will know what happens
[G3 Android Development] Alukrad:
LOL
[G3 Android Development] EternalFlame:
LMFAO

Sent using XDA One
[G3 Android Development] djdeeles:
It's v1.3 I think so with zzmoove got with zzmoove hotplug with thermal mod, no ctt mod.
[G3 Android Development] Windforce0511:
I have above 1000 for single core and above 3000 for multi core in Geekbench but I have stuttering while scrolling. With Interactive no problems with scrolling smoothness but geekbench score is much lower...
[G3 Android Development] piskor:
So You need to choose benchmark or overall performance :)

I would choose performance :)
[G3 Android Development] Windforce0511:
Btw which one is best in terms of UI smoothness and performance? What about Hotplugs? :)
[G3 Android Development] piskor:
I'm on interactive but with another kernel. Now i'm testing msm hotplug and it looks good.
[G3 Android Development] schwem:
Finally decided to give this kernel a try on my vs985. Holy crap! Why did I wait so long to try thus. Helped my temp issues using alucard hotplug and governors and I love the ability to increase saturation intensity of the screen. Almost looks like an Amoled! The colors are way more vivid and blacks are more black set at 60. Any suggestions to get rid of the small bit of scroll lag. It's not bad with alucard but it's there a little bit say... Aon G+ or chrome with certain web pages. Anyways, thanks for the awesome kernel. Best one I've used yet.
[G3 Android Development] NatesLaw:
I 2nd this and would like to add...FINALLY a kernel that OC's & UC's actually STICK in Kernel Adiutor! :good:
[G3 Android Development] schwem:
Yeah I noticed that too. I always underclock the gpu and undervolt my voltage globally by -25mv and so far they've stuck. So far the temp control is working great and I've got it set to throttle at 70°c. I can't believe I've waited to try this!
[G3 Android Development] Taracair:
Thanks for the advice about colors. Never used that before.
[G3 Android Development] edoardotavecchio:
Could you explain me what does the "Suspend" toggle in Alucard Hotplug settings mean? I haven't understood yet if toggling it on means that the phone can suspend or not, the explanation in KernelAdiutor it's a little bit confusing.
[G3 Android Development] schwem:
Yeah I was just playing around with it and got the colors to look much more rich and crisp. Definately better than the way it's tuned stock. Glad I could help. This kernel is crazy good. Can't believe the improvement!
[G3 Android Development] Taracair:
I hope it doesn't affect the lifespan of the screen.
[G3 Android Development] schwem:
I don't see how it could. It's an LCD not an Amoled, no burn-in. All the heat issues I had before using this kernel, now that will probably wreck the screen!
[G3 Android Development] :
Thank you for the saturation intensity value. It really makes the colors vivid and blacks blacker. It's very pleasing to my eyes. Try these values for the G3 screen if you wish. These are screen values recommended in the Gabriel Kernel thread but if you have better values, please recommend them to for us to use. :)

Red: 250

Green: 252

Blue: 255

Saturation Intensity (What you recommended) : 60

Screen Value: 127

Screen Contrast: 138

Screen Hue: 24