yashsingh1/xdaforums huggingface dataset:
[G3 Android Development] guillerv1974:
thanks in advance for such an exceptional kernel, I'm using it in stock rom and when I connect the phone to the pc not Reconce me, just load, could you give me a solution to continue using it, thank you very much.
[G3 Android Development] djdeeles:
Maybe later I'll look
[G3 Android Development] takis:
Have you done anything for the problem where the phone doesnt boot when connected to power supply?
[G3 Android Development] bhang:
This has been an issue for me using fulmics which has a stock kernel...

Its a bit offtopic but...
[G3 Android Development] Emu:
Had this issue across phones... Nothing you can do other than leave it turned off until it charges to like 5% or something and then boot.
[G3 Android Development] MaddMaxx636:
I have been getting a lot of random soft reboots. Either while im using my phone or while the screen is off. It always recovers but still its annoying. Im using the most current version of the kernel.
[G3 Android Development] Reli4nth:
For those who have random reboots, switch alucard (both governor and hotplug) for some others.

I had reboots with alucard, but no more with lionheart+msm hotplug.
[G3 Android Development] MaddMaxx636:
Im using Interactive and MSM hotplug.
[G3 Android Development] djdeeles:
Who had random reboots or locks I need logs and more details about govs, uv and frequencies.

You must provide logs to find solution.

Thnx
[G3 Android Development] MaddMaxx636:
I have tried to get logs but they dont get made once it starts freaking out. If it does make logs they are corrupted
[G3 Android Development] Alukrad:
I've heard that implementing that on a custom kernel+ROM is very difficult. DTTW isn't convenient enough? LOL

---------- Post added at 12:15 AM ---------- Previous post was at 12:14 AM ----------

Did you dirty flash his kernel on top of another custom kernel like Nebula?
[G3 Android Development] MaddMaxx636:
Nope. I was using the nebula kernel before but i did a full wipe and flashed CM13 and this kernel clean.
[G3 Android Development] Alukrad:
It may be incompatible with the ROM you're using since this is a kernel built for AOSP
[G3 Android Development] MaddMaxx636:
I just said i was using CM13... This is a CM/CM13 kernel.
[G3 Android Development] Emu:
The new update is great so far. Less lag than before. Using 300 Hz instead of dynamic fixed the lag problem I had after leaving the phone on for more than 6 hours. I knew that was the issue but I don't have the knowledge to fix it myself. Thank you. Much much better now.
[G3 Android Development] Alukrad:
Actually.....if you look at the title of the thread it does say AOSP on it. Not CM lol
[G3 Android Development] MaddMaxx636:
Well why does is say 'Latest CM13 patches' in the features and ' Merges from CM' in the change-log?

If this is going to become a pointless argument about if this kernel supports CM13 lets just stop now. I dont want to flood this thread with a pointless argument.
[G3 Android Development] Alukrad:
Well see we're trying to troubleshoot here. What I'm trying to say is try a different ROM and see how the Kernel acts. If it doesn't give you reboots then you know where the problems belong. Also if I'm not mistaken low mem G3's don't do too well with this Kernel. Pls don't be aggressive since we're trying to help you here
[G3 Android Development] MaddMaxx636:
I understand that you are you are trying troubleshoot and help. I have the VS985 model. 32GB. Also if it seemed like i was being aggressive than im sorry, I wasn't trying to be. I just dont like either starting or being in the middle of pointless arguments and flooding threads.
[G3 Android Development] Alukrad:
Much better. Now, if you could try the Kernel with another ROM and report back we'll have a better view of your problem here. Good luck!
[G3 Android Development] MaddMaxx636:
Ok. Well ill try it later tomorrow. I would rather not have to flash another rom since ive already got my CM13 all set up how i like it. haha
[G3 Android Development] drdexter1989:
Here is my report with aCC 1.5. with ATT D850

In first instance i was using Fulmics ROM 5.0 and stock kernel, then i decide to give a try to OrionOS (I made a backup first of Fulmics), instaled rom, kernel, gapps, supersu, addons as my usual rom install process. Booted up and worked smooth and well. suddenly, restoring my apps from playstore I got a reboot, booted up again and when i gots lockscreen it reboots again.

So, i reverted to my Fulmics Backup and using Fulmics, and guess what. I'm still getting random reboots. Tryed Temasek's rom, random reboots, AICP Rom, it stucked on first boot.

I hope it could be helpful to the developer, to figure out where the problem is.
[G3 Android Development] :
Did you clear dalvik, system, data, and cache before restoring your Fulmics backup?
[G3 Android Development] souler456:
I only got the chance now to update into v1.5 with the new XenonHD update as well, and no reboots so far... Came from a clean wipe with no internal sd wiping. Gonna observe for a day or two with my new setup and hope that it'll survive without reboots :p

Per Core Control makes my core0 stuck at it's highest mhz, so no luck on using it here. On that time, I'll update my setup which I posted here to make an even (hopefully) better underclocked setup, adding alucard hotplug settings, and some i/o scheduler stuff.

:D :) ;) :good:
[G3 Android Development] drdexter1989:
Yes, I always do that before revert a backup or install new roms
[G3 Android Development] EternalFlame:
Nice find! :good:

Same behaviour on my lowmem d855, when i turn off the screen it jumps back to 587 or 462... hope this is fixable.
[G3 Android Development] MaddMaxx636:
I think i might have found the random soft reboot BS. I was last using the Nebula Kernel and was using the same setup (same gov and hotplug) and i think the MSM hotplug is the issue. It doesn't have a max online cores when screen is off option. The only time its soft rebooted was when the screen is off or sleeping. So i think if you could add that into the hotplug (if thats even possible) it might fix the issue.

NOTE: The soft reboots were happening on 2 other roms.
[G3 Android Development] Alukrad:
There's been a standing problem with MSM Hotplug which is why it's been removed.

Besides that Hotplug is soooo outdated I think we voted it out of this Kernel. In Alucard we trust.

EDIT: Just checked and it's still there. I forget when but if I'm not mistaken there's been an issue with MSM Hotplug before, not sure when but if you scour around you'll find a post about it.

---------- Post added at 10:23 PM ---------- Previous post was at 10:16 PM ----------

Are you using the most recent version of modded KA? My Alucard gov is very well sitting on 2.2ghz with no stickiness. On the other hand my GPU freq jumps around when it feels like it o.o but it's been that way since 1.4 and I kinda just let it do what it wants lol.
[G3 Android Development] souler456:
Yep, on the latest, though I underclocked even more to 1728mhz with Slim Gov, which is surprisingly fine with just minimal tasks. And unless the dev has actions for this issue, GPU will prolly stay like that.

:D :) ;) :good:
[G3 Android Development] Alukrad:
It used to be stuck at 330ghz on ver 1.4 now it bounces between Max(where I wanted it to be) and 480 I think. So far not even a hiccup or crash or lag so I'm really not tripping. My battery life has never been better too. On heavy use I'm getting 4.5 to 5 hrs on my setup
[G3 Android Development] souler456:
So... I took up an self-endurance test with the v1.5. Browsed through the web via 3G (mainly facebook, reading manga, and some downloading stuffs) while playing music (with V4A) straight with no screen-offs, and results are:

I was hoping for a 5-hour SoT with 15% battery left, but 4 and a half is still nice... :good:

:D :) ;) :good:
[G3 Android Development] Alukrad:
See! I told ya'll it was possible :) I bet you if you disable a few wakelocks you could achieve the same with 2.2ghz

What I/O setup do you use?
[G3 Android Development] souler456:
SIO/Trip. I will try another setup of mine on Slim gov, since I always have 5 hours with 15% bat left with intellidemand governor on an another kernel (which doesn't exist on this kernel), and adjusting to Slim gov is pretty hard.

:D :) ;) :good:
[G3 Android Development] Alukrad:
Very nice! Let us know how it goes. So far you got 4.5 hours from aCC right?
[G3 Android Development] souler456:
Yes, 4.5h. I'll use my more underclocked version to see if it'll save even more b.juice, hopefully... And as usual, I'll post my setup just like I did here

:D :) ;) :good:
[G3 Android Development] :
I would like to use the interactive governor with this kernel. Anyone have any tunables for the interactive governor?
[G3 Android Development] souler456:
Okay.... Well... This is new... My phone went 5%, and when I plugged the charger, left it there, and checked it back an hour later, it is not charging, worse, it left me with a 3% juice left.

First thing I did is to change my charger, which didn't worked. Next is change the plug location which didn't worked as well. Finally, took a risk, rebooted the device even though it's 3% left, and it now charges.

Due to me on a panic state, I freakin' forgot to take a logcat out of it. Next time it happens, I'll be sure to get some logs.

But I'll still ask, is this kernel related? :confused:

:D :) ;) :good:
[G3 Android Development] hean_burak:
Never had it before.
[G3 Android Development] :
C

This has happened to me on a variety of different custom ROMS such as Candy6, BlissPop, and Resurrection Remix (All MM based) but not on Fulmics 5.1 (Stock based MM ROM) Went back to a stock based ROM just to make sure it wasn't my wall adapter, battery, or USB charging cable that was dying. It might be an issue across CM/AOSP ROMS at the moment, or it might be Acc kernel. By the way, how do you get a logcat?
[G3 Android Development] souler456:
It's pretty straightforward to get a logcat. You just have to download an app called Catlog on PStore, open it, then minimize Catlog, reproduce the bug, go back to Catlog again, press Save Log, then upload the logcat. Easy. :good:

Just make sure your android logger is enabled via KA, or else Catlog wont... well... won't logcat... ;)

:D :) ;) :good:
[G3 Android Development] :
Alrighty. Got everything prepared for when the G3 stops charging again. Hopefully I don't forget to logcat.
[G3 Android Development] oranget:
Same here...mine started doing that as well. Rebooting phone fixes it and it starts charging again, but it happens very randomly.
[G3 Android Development] hunting_:
I don't have any problem even today i flash 4 time in a day
[G3 Android Development] Alukrad:
It's happened to me on stock kernel and aCC I think it's a ROM issue. It goes away permanently after awhile :)
[G3 Android Development] Taracair:
Can anyone check if the Slimport HDMI Adapter 1080p works? Mine doesn't, but it works on the same G3 with stock rom. May it be kernel related issue?
[G3 Android Development] souler456:
My side as well. One time, I left my G3 charging plugged with 10%, slept for 2 hours, checked the phone, and it's 77% and still charging, which is weird, since it should be full by that time.

So ignoring that, I left the phone again charging, and when I checked it 30 minutes later, it's still 77% and charging. Scratching my head, i unplugged-replugged my charger and now it charged back to normal.

Meaning, sometimes charging randomly "stops" and I don't even know why. It's a first time I experienced since using this kernel, though I have no logs provided, so you can treat this as if it never happened... Well, for me it did :eek:

So on this situations, logcats are VERY important.

I use XenonHD with this kernel. From 6 months of using XenonHD, I had NEVER experienced that... Well... Until now... :D

If you read the changelogs from the v1.5 release, there's a "Slimport fixes" noted in there... So... It's "probably" on the kernel side which is giving you that... But just to be sure, better wait for the dev for his response regarding on your case, since the new changelogs is "supposed" to fix it... :p

:D :) ;) :good:
[G3 Android Development] Emu:
If your phone isn't charging anymore it's a ROM related issue. Happens here and there. Only fix I found is to turn your phone off. Remove the battery for like 15 sec, put it back in and boot. No more issues.
[G3 Android Development] :
Sad how all the custom ROMS I've tried have the charging issue with the kernel it came with or while using acc kernel. I've even used the stock G3 charger and the Aukey charger and it stops charging regardless. I've tried the battery pull for 15 seconds and the charging issue did go away until the phone reached 85% Oh well. Maybe some variants have the charging issue.
[G3 Android Development] Emu:
Yup. Even had the issue across phones so this is definitely not just tied to G3's. So my guess is the issue goes back to CyanogenMod which is the mother of almost all custom ROMs. This is also the reason why I could never imagine having a phone without a removable battery. I mean what do you do when your phone freezes for good and the power button doesn't respond?
[G3 Android Development] Taracair:
Is probably ROM related. I'm in contact with official Slimport support. Will post solution soon.

There is small reset button hidden under SIM/SD card cap in every phone with non removable battery.
[G3 Android Development] souler456:
The "not charging" thing as I reported here appeared once again on me, but this time I caught some logs, and hopefully, it'll help...

I ran XenonHD b050816 with Xposed v80, and on aCC v1.5...

:D :) ;) :good:
[G3 Android Development] EternalFlame:
Yes! Got my 5h+ SOT back with v1.5 :D :good:

edit:

oh and [MENTION=5075251]souler456[/MENTION] i made a kernel settings thread a few months ago, if you don´t mind i add your settings there too :)

Here is the link: http://xdaforums.com/lg-g3/general/...le-sharing-t3233200/post63482094#post63482094
[G3 Android Development] v.konvict:
Great results...i like this kernel. Had a question...i used to get great battery life till i added myself to some whatsapp groups now whatsapp keeps radio active for long periods of time and chews up a lot. Any solutions to this.
[G3 Android Development] oranget:
Ok..i can confirm the issue with the phone randomly stops charging issue is a rom problem, apparently has to do with CM base somewhere. I have gone to a totally different rom with their stock CM based kernel and it is still happening. So this kernel is NOT the culprit of the random charging problem happening lately. Just for everyone to know.
[G3 Android Development] Koont:
Uhh, I didn't have this issue with nebula ( I had others though) and AICP. Reboot fixes it. But yeah, started with this kernel.
[G3 Android Development] Roi007leaf:
Can anyone confirm that this kernel works with MultiROM?
[G3 Android Development] marcdw:
You know, I didn't even realize it had kexec boot patch (haven't read the list of features in awhile). Cool. I'll test it today on my primary and see how it goes.

EDIT: Tried and failed with versions 1.4 & 1.5. Boot menu does not come up. Just goes black or reboots over and over.

LG G3 D851, Resurrection Remix-M ROM, Tapatalk 4.9.5
[G3 Android Development] EternalFlame:
hey there, sorray to bother again [MENTION=3585838]djdeeles[/MENTION] but i really hope you can fix that gpu thermal thingy... just had a crazy mmsservice wakelock and saw that gpu thermal error flying around the log every few minutes... it was already mentioned a few days ago but i thought i bring it up one more time :p
[G3 Android Development] Alukrad:
Have you tried installing CTT mod as a temporary measure? I've been using the mod since 4.4 and they do a good job with thermal issues. Or possibly just shut off intellithermal within KA should null that error
[G3 Android Development] EternalFlame:
I´ll give it a shot, thanks man.
[G3 Android Development] marcdw:
aCC and MultiROM...

LOL. I knew I should've gotten some sleep first. My primary ROM is Lollipop. Even though I was only checking to see if the boot menu would show up it might still be a factor.

Welp, it's my day off and nothing on TV. Reckon I'll backup everything, install MM as primary ( ? ), then try the kernel.

LG G3 D851, PAC-MAN ROM, Tapatalk 4.9.5
[G3 Android Development] marcdw:
Latest test. Backed up and deleted my LP primary ROM. Wiped everything.

Flashed an MM ROM (AOKP) and aCC kernel. Injected for good measure.

No go. Black screen or reboots.

Also tried Nebula2e (not knowing if it has the patch or not) with same result.

Finally used Nebula 12.5-MM kernel and all is good. Boot menu comes up.

Lastly I'll try 777 to round things out.

EDIT: 777 R22 MM kernel also works.

Nebula and 777 are the only two so far.

LG G3 D851, Resurrection Remix-M ROM, Tapatalk 4.9.5
[G3 Android Development] Alukrad:
Noice, I'm considering using a dual boot setup for ROM and Kernel Testing once i get a bit more info in kinks and how to fix in case I Bork something lol
[G3 Android Development] Emu:
Don't flash the ROM and kernel without a reboot between them. Yes it will optimize the apps again but what can you do.
[G3 Android Development] hunting_:
Download link not work any help ?
[G3 Android Development] djdeeles:
It's up right now.
[G3 Android Development] souler456:
So, you mean after flashing the ROM, we reboot, then reboot to recovery again to flash this kernel, then wipe cache/dalvik, yes? Reason for this procedure? :confused:

But I would like to try this, if it doesn't make sense to me, 'coz I'm going crazy with this "not charging" issue, but I don't want to let go for this kernel for testing purposes, so I'll let any "tricks" on my option as well.... :eek:

:D :) ;) :good:
[G3 Android Development] Emu:
Yes. Otherwise you will get stuck in a bootloop. Not charging issue is super easy to fix. Once you flashed the kernel, boot to your OS. Then turn your phone off. Remove the battery, put it back in after 5 sec and boot again.
[G3 Android Development] souler456:
Uhmmmm.... No... I always do this:

> Full Wipe (/system /data /cache)

> Flash ROM

> Flash GApps

> Flash aCC Kernel (or any other Kernels out there)

> Flash Xposed

> Reboot

..and it NEVER gives me bootloop, like EVER :eek:

About the "not charging" issue, a simple reboot always do the trick... But... Come on, man... I want to see my ROM & Kernel combination's total uptime and how long this kernel lasts without reboots.

But even though I can confidently say that this kernel can give me no reboots whatsover, this charging issue spoils it, sadly :(

:D :) ;) :good:
[G3 Android Development] Emu:
Ah. I never do full wipe. Just flash the rom so I run into other issues. Like I said this works for me. Only have to remove and insert the battery once and never again until I flash a new kernel.
[G3 Android Development] souler456:
So, you mean to say:

> Full Wipe

> Flash ROM

> Flash GApps (opt)

> Flash aCC

> Flash Xposed (opt)

> Reboot

> When device booted, power-off

> Pull-out battery, wait for a couple of secs

> Put the battery back again

> Reboot

> "Not Charging" issue solved...? :confused:

:D :) ;) :good:
[G3 Android Development] Emu:
If you already flashed everything, just remove the battery and put it back in. It should do the trick. No reflashing necessary. :)
[G3 Android Development] Meneldur:
Started trying this kernel today and did similarly (just kernel last after Xposed, and only cache wipes).

It worked flawlessly.

Mnldr/D855/16G/CM13
[G3 Android Development] Andrewoidd:
I might be missing something but I never get the whole selection of CPU governors that it states have been added. I have tried v1.3, 1.4, and 1.5, but the additions that were in the changelog for v1.3 were not there. Any ideas why?
[G3 Android Development] Alukrad:
It's been a month now and the not charging issue has become a rare occurrence ever since I slapped on CTT mod. I think the heat triggers charging to stop and make the error.
[G3 Android Development] souler456:
I just reflashed my chosenROM with aCC and did the "pull-out-yo-bat" trick... So far so good... I may post my new setup for another critisizing, since I can't before due to me getting insane on the charging issue...

And I can play games now and max is always 75C. No CTT. May try that MOD in the future, if I went "experimental" mode again :eek:

:D :) ;) :good:
[G3 Android Development] takis:
Can you ahare your setup? Rom?
[G3 Android Development] souler456:
About the ROM, I use XenonHD. About the kernel setup, I'll post it later on since I'm still testing it. The screenie I attached "should" be 2.5 hours, since I only browse the web, mainly reading manga and light novel, checking mah facebook while listening to music, but as you can see, it's not what I expected, so... Still twerking... I mean... Still tweaking it... :eek:

:D :) ;) :good:
[G3 Android Development] foxtaur:
this kernel has charging issues and big time across all roms on my d852. I even went back to an older kernel and if it werent for the occasional crash and fact that settings dont stick that one would be my default kernel. ACC 1.5 is ok but again seems like it needs a lot of work still. It feels laggy (even on turborom)
[G3 Android Development] Alukrad:
I'm telling you guys the charging problem goes away and it's with the CM base side issue. Ask around for kernel settings from veteran users and you'll be sure to find something speedy to match your ROM :) combos are everything
[G3 Android Development] foxtaur:
I'm reluctant to believe that, running d852 and have tried all sorts of ROMs. BrokenromOS,xenon,and turbo and after a while the phone stops charging. I've tried all the kernels and the one that does not have any issue at all are Joes and nebula2e and older nebula's. I dont play favoritism, I just know when it ain't working, it ain't working. Sure give it a reboot and its fine but it gets frustrating when I shut off phone during night for a full charge on my zerolemon battery and the light ain't displaying. I hear the notification that phone has been plugged into a wall wart outlet but no light appears. I'm also running mtp enabler. In the meantime running nebula2e and hopeful this gets sorted or Michael Harrell makes a return and updates nebula2e.
[G3 Android Development] Alukrad:
Not a problem. But if you read through the number of posts here you'll see that we've pretty much figured out where the problem stems from.

And like I said the problem does go away either completely or becomes a very rare occurrence after a while. I say this because i've used the kernel since day one and now a month into 1.5 I've not had the issue any longer.
[G3 Android Development] souler456:
I used this kernel on Turbo once. Same setup on my current ROM XenonHD. Difference is Turbo gave me lags, Xenon didn't. Even more visible when playing games.

By this, we can learn that NOT all lags comes from kernel. Eliminater said this also. So... Yeah... Pick a good ROM for starters, of course I'm a Xenon bias, so go for Xenon :p

'Bout the charging issue, if you look at the older posts, we discussed it too, and I'm currently trying the pull-out battery trick for it... And so far so good... None of the "not charginf" issue arises as of this time... Although it's only 3 days so far... :eek:

'Bout the kernel setup not sticking, use the Modded Kernel Adiutor, pal. Or if you're already using it, do NOT hibernate it on Greenify. It'll block the boot service if you do.

:D :) ;) :good:
[G3 Android Development] Omar-Avelar:
I managed to fix my "stops charging issue" on CM13 by disabling the "Enable per-app profiles" setting under "Battery" :) ... strange but it works...

[IMG="[Settings]"]http://i68.tinypic.com/mlrpd.jpg[/IMG]