yashsingh1/xdaforums huggingface dataset:
[G2 Android Development] ckyy:
Was on latest mahdi and r5. Had a reboot when i switched apps. After it rebooted i was greeted with the Mahdi setup screen, also some apps ramdomly started up. Had lost a few apps i installed previously. Why did that happen? I had fsync on. Be warned. It was not a big loss for me, but it could be for someone else.
[G2 Android Development] simon_lefisch:
He warned peeps about the fsync. Keep it off so you don't lose data.
[G2 Android Development] thackoon:
I'm on latest Mahdi rom and considering trying Render Kernel (R4). Anyone know if wireless charging works on VS980?
[G2 Android Development] ckyy:
Really? How could i have missed that?..... /s

I was obviously trying to spread the word. I knew what would happen if you keep it enabled.
[G2 Android Development] Lawlrus:
I was actually going to reference that post. But I read it a couple times, and I started reading it as mobile data. So I'm not sure which he was referring to.

Sent from my Vs980 running Omni 4.4.4
[G2 Android Development] RenderBroken:
Yea, it got mixed into r5 by accident. It's not in r6. I will be doing a build with Falcon hotplug along with all the new fixes. Maybe msm_hotplug doesn't play well. I also only have a few more things to omit for the next build to to track down the commit causing the reboots. I'm patient as long as you guys are. I will work through it and get to the bottom of this nefarious business.
[G2 Android Development] Lawlrus:
So by data you mean mobile data? Or apps, pics, ect..

Sent from my Vs980 running Omni 4.4.4
[G2 Android Development] RenderBroken:
I had recieved your post and appreciate the input. I had also replied back to you about me doing the Stock build soon as we are back o nsolid ground again.

Hate to see you go but understand. Thanks for the logs though. I plan on releasing another build tonight. It should bring us back to solid ground again and then we can build off of it. At the moment I have been ruling out the nefarious commit and only have a few more things that could be the cause so I am hopeful we can get past this in the next build.

I was talking about the Moble Data bug. It occurs when you flash Mahdi like this:

Mahdi > Patch > Gapps > (Maybe SuperSU) > then Render Kernel

What would happen is Mobile data would be borked. The only fix for it was to Flash Mahdi like this:

Mahdi > Patch > Gapps > Maybe SuperSU > Reboot into Rom > Then Reboot into Recovery > Then flash Render Kernel

BUT I have fixed the cause of this bug so now you can flash my kernel like you normally would flash a kernel over a Rom without having to go through the extra steps.

Holy crap! Damn these reboots! lol I will say it again, thanks for the support and help while going through these hurdles. It shows and means alot that the community on this thread is mature and considerate. Not a single person has made a negative comment towards me or have bashed me or this kernel in any way. That really means a lot to myself because I am a perfectionist. I still have much to learn and the main reason for releasing and building this kernel is to learn as I go and teach what I know. I want to share my knowledge and be open to the community and not another Dev who snubs people. So a big thank you to all of you out there while we get through this. I will make it worth the headache and the wait.
[G2 Android Development] Matze060906:
I think anyone here know about your hard work. We know that you always try your best and you will fix the problems. If not in the next release then in the release after next...

Thanks for your work...
[G2 Android Development] hamisgood:
I'm sure those that bash you will get flamed by the hundreds of other Render users, myself included. So don't worry and continue doing your good work :good:!
[G2 Android Development] Saythis:
Hey man, you really have nothing to be thanking for. We're all grateful for the work you've put into making this kernel as amazing as possible. We realize that you're doing your very best and that's more than anyone in the G2 community could ask for. Honestly I've never seen such an attentive dev before so if anything we should be thanking you.

On that note however.. I do have to temporarily stop using Render kernel because i do need a somewhat stable phone the next couple weeks..

Sent from my LG-VS980
[G2 Android Development] SeVIIn:
Here's another log for R6 https://drive.google.com/file/d/0ByQU4ANsxaildnA5Tlo2bzR2N2c/edit?usp=sharing I'll probably go back to R4 for now until the new build is up. Thanks again for all your hard work and dont worry too much, us Android users are use to working through bugs haha.
[G2 Android Development] hovanhuang:
Can't find Hotplug

Can somebody help me out here? I can't find hotplug in Trickster MOD and neither the screen boost.

I'm on R4 and free Trickster MOD version.

I do see hot plug when use dr87's patch s3. but when i press it, it said not available.

Please~~
[G2 Android Development] SeVIIn:
You can not change the hotplug in Trickster MOD with these kernel currently
[G2 Android Development] Saythis:
You won't be able to tweak the hotplug settings. They're limited to the developer.
[G2 Android Development] hovanhuang:
Thank you. what about the screen boost for "knock on" function everybody is talking about?

thx.
[G2 Android Development] Saythis:
Well, you won't get Knock on code for AOSP, but you can get Double Tap 2 Wake which is supported by default with Render Kernel.
[G2 Android Development] hovanhuang:
So it's a built-in hotplug already?

Thank you. what about the screen boost for "knock on" function everybody is talking about?

thx.

---------- Post added at 11:49 AM ---------- Previous post was at 11:45 AM ----------

Yes. But some threads is saying that in Trickster, there is a tweak to boost on the cup feq when touching the screen so that these won't be lag and achieve instant response (wake up).

please see below reference:

Originally Posted by Raagh View Post

Doesnt matter. Two poor battery life. Something is eating your battery. My worst battery on aosp is mahdi with simplekernel (6hrs sot 22 hrs usage), and my bests are dorimanx or render(almost 8hours sot).

So setup kernel settings.

I used a modified intellidemand. Tcp westwood, one coreboost, inteli hotplug,both thermal controls, touch boost set up to 96000, gpu simpleondemand. No oc. Default frequencys. No UV, maybe something i forgot+ greenify
[G2 Android Development] SeVIIn:
Yes, he is referring to the the actual governor settings found under "Governor Control" in there you can modify a multitude of different parameters.
[G2 Android Development] chillstep1998:
Frozen Screen + Reboot while browsing Hot or Not

Kernel R6

Logs: https://www.dropbox.com/s/efarxdgd0hlgye8/logs.zip

Sent from my Munsta LG D802 from XDA Premium⁴
[G2 Android Development] hovanhuang:
Thanks.

Hum, that's what i assuming. But when i go to Governor Control, i didn't see any items call "Touch Boost". Is that under other name? or just Render Kernel doesn't support that but only dorimanx.
[G2 Android Development] Lawlrus:
He's not using trickster

He's using either kernel tweaker or stweaks

Sent from my Vs980 running Omni 4.4.4
[G2 Android Development] hovanhuang:
Thx. Just downloaded kernel tweaker. but still can't find the touch boost......
[G2 Android Development] Lawlrus:
Its in stweaks which I dunno if that works with this kernel, I know it works with dorimanx though because it is made by him.

Check faux123 I know that has some pretty impressive thermal cotrols, not sure if t would work with this kernel, and I'm not sure if it works with touch boost. Its like six bucks.

Sent from my Vs980 running Omni 4.4.4
[G2 Android Development] hovanhuang:
OK. use faux 123 pro do see the hotplug and touch boost tweaks. But they are grey out looks like kernel not supported. only option is user control.

I'm now using barts dorimanx asop kernel. it should be supported. weird.
[G2 Android Development] Lawlrus:
Yeah, I dunno man. Nothings working out for you lol

Sent from my Vs980 running Omni 4.4.4
[G2 Android Development] ThatKidDrew:
I've had 3 reboots today but no SODs. I took a log after the last reboot, hopefully it contains the information you need. Compared to R5 my phone isn't getting hot but the battery is still not good. I'm on the VS980 with a recent nightly of AICP, I flashed supersu 2.0.2 right after I flashed R6, here's the log. Thanks for all your work! https://docs.google.com/file/d/0B3rK_px6FpxWVWdOYmJ3SWhLTnc/edit?usp=docslist_api

VS980 running AICP 4.4.4
[G2 Android Development] Raagh:
Dorimanx did not made stweaks.

Stweaks was developed by GokhanMoral he is like the godfather of samsung development(retired now) and developer of SIYAH Kernel( the original kernel that bring stweaks to the game). Dorimanx kernel was based on siyah( in the samsung family of course not here) so i guess he got really comfortable using the app in his kernel and he bring it to the lg g2

Just saying to bring respect to original developer :)
[G2 Android Development] Lawlrus:
Guess that makes sense as to why he bakes it into all of his kernels then, thanks.

Sent from my Vs980 running Omni 4.4.4
[G2 Android Development] RenderBroken:
Both of the hotplugs I have used have sysfs settings that you can change to your liking. But they do not show up in Trickster Mod. All Trickster Mod does is look for KNOWN sysfs settings and give you a GUI to manipulate them. There are SO MUCH more settings that the intrepid android user can change to further his own optimizations as much as he wants! Just use ES Explorer and navigate to /sys.

If you have further questions please feel free to ask. I have no problem going into more detail!

Don't waste your money with Faux's app. It will not help you one bit with my kernels. I use a VERY SIMPLE Thermal driver made from Franco. it does the hard work for you, You just need to set the Max temp. It will do the rest and do it very efficiently.
[G2 Android Development] Lawlrus:
[MENTION=5438598]RenderBroken[/MENTION]

Is there a reason why your kernel charges faster via a wall outlet then what simple kernel does?

Sent from my Vs980 running Omni 4.4.4
[G2 Android Development] RenderBroken:
Your log is the first one to actually give any real data. Thanks Sir! Now I just have to see how it relates to my most recent commits
[G2 Android Development] RenderBroken:
No sir. Should be the same as far as I know.
[G2 Android Development] Lawlrus:
Weird. It always seems like it takes forever for simple kernel to charge, but with yours, it feels like it takes half the amount of time.

Edit: just installed gsam and it says its charging at 500 ma on the lg charger lol

On simple kernel

Sent from my Vs980 running Omni 4.4.4
[G2 Android Development] blacklight1025:
For me v6 is running great. No reboots going on 13 hours with 80% still left. Thanks for all the hard work again. Your kernels breathe new life into an already solid phone. [emoji106]
[G2 Android Development] ThatKidDrew:
Got another reboot along with a log after, not sure if the log will give you the same exact information but I'm providing one just in case. If it's the exact same thing let me know, here's el log https://docs.google.com/file/d/0B3rK_px6FpxWUTA4LVNxVnhSaHc/edit?usp=docslist_api

VS980 running AICP 4.4.4
[G2 Android Development] RenderBroken:
Better safe than sorry! I am building now and will be releasing tonight if possible. I may not have enough time to build for all but since you are getting reboots i will build specifically for your device. Would you test for me?
[G2 Android Development] Saythis:
If you need/want another VS980 for testing I'll gladly help.
[G2 Android Development] RenderBroken:
Sure, I will build shortly. Then upload.
[G2 Android Development] simon_lefisch:
Had my first reboot about an hour ago on R6. Wasn't able to get a log cuz I was using my phone as a timer during a personal training session and it froze and rebooted. Otherwise its been pretty solid. If I get another reboot I'll make sure to grab a log. Looking forward to the next release.
[G2 Android Development] RenderBroken:
Its uploading now.
[G2 Android Development] Saythis:
So far so good! :good:
[G2 Android Development] Raagh:
Changelog for r7? Hotplug is using and stuff?

Downloading :)
[G2 Android Development] Boot_Derran:
Not trying to post anything insignificant but u can't thank the op in the op more than once lol soooooooo R7 IS THE SHIZZ! (a good thing)
[G2 Android Development] Quiox:
Just flashed R7 will report back how it goes!
[G2 Android Development] Raagh:
Btw [MENTION=5438598]RenderBroken[/MENTION] i had some issues with the vm in virtualbox. So i decide to start over, i ve made a new partition to my harddrive and im installing latest ubuntu right now. Tomorrow i ll setup the enviroment and start downloading sources :). I ll inform you how it goes
[G2 Android Development] RenderBroken:
Mainly what R4 was supposed to be minus the nefarious commits. Mainly:

Scheduler bring up (And more to come)

Enabled CPU-Boost

msm_hotplug by myfluxi: Will go down to one core while idle like reading a book or something then online the second core when scrolling and other slightly more. Max suspend cpus set to 1

Disabled Quickwakeup for testing to see if it conflicted with DT2W (Doubtful but cant be sure)

Auto Group Scheduling

QSEECOM patches

etc
[G2 Android Development] RenderBroken:
Please do.
[G2 Android Development] simon_lefisch:
[MENTION=5438598]RenderBroken[/MENTION] I flashed R7 about 15-20 minutes ago. Went to wake up the phone and had a reboot. Log is below. I'm thinking it was just cuz the kernel needs to settle a bit more so I'm gonna keep running it and see if it happens again. For the record, I reflashed Mahdi S3 patch just to clean the boot image and flashed R7 right after. Hope this helps!

http://goo.gl/xawNNx
[G2 Android Development] Raagh:
Ty, read ahead now is 1024. And also new interactive settings right?
[G2 Android Development] simon_lefisch:
[MENTION=5438598]RenderBroken[/MENTION] just had another reboot waking up the phone again.

http://goo.gl/HrDtYs
[G2 Android Development] Saythis:
I had a reboot at first after I installed R7, but I updated to SuperSU 2.0.2 and so far I have yet to have one.
[G2 Android Development] 1ceb0x:
if this is true, that could mean something is wrong with the selinux..
[G2 Android Development] simon_lefisch:
I've been on SuperSU v2.02 for some time. Don't think that makes too much of a difference. The only versions that haven't given me reboots are R3 and R4 and I was on SuperSU v2.01 for some time before switching to v2.02.
[G2 Android Development] Saythis:
Maybe try a clean install with R7?

Yeah, [MENTION=2376110]dorimanx[/MENTION] was having problems with SOD's and reboots also that were attributed to SuperSU.
[G2 Android Development] Andrew_han:
Edit: removed, my apologies
[G2 Android Development] 1ceb0x:
The min cpu frequency set in the .sh file is 300 mhz. That's why it does not go any lower than that. You don't gain too much anyway if you go lower.
[G2 Android Development] Saythis:
Mines dropping to 27Mhz as shown below.
[G2 Android Development] hovanhuang:
Thanks Render. Please go over more what's the later steps after navigate to /sys. I want to fully explore your talents. :fingers-crossed:
[G2 Android Development] simon_lefisch:
Don't think a clean install would matter, as I've reverted back to R4 from R5 and R6 and didn't have any reboots on R4.

Aside from those first 2 reboots R7 is good. Hasn't rebooted since.
[G2 Android Development] Boot_Derran:
Now that I have flashed R7 D2TW only works right after phone is pulled from my pocket or from face down position. Beyond that this kernel (w/updated supersu 2.0.2) has given no reboots whatsoever
[G2 Android Development] BlakeSm:
Reboot while using Twitch app. SuperSu 2.02, Mahdi 8/09, Render v7. Had no reboots when using v6.
[G2 Android Development] murdoch1:
Reboot

D802...mahdi ROM 9/8. Screen was asleep when an alert came through. Couldn't wake phone and reboot occurred.

Logs attached. Using R7.
[G2 Android Development] Matze060906:
Running R7 since 4 hours. No reboots by waking up the phone but I opened zooper widget and want create a new widget. Got a freeze for 5 seconds and then reboot. D802 with latest Mahdi. Here's the log file...

https://docs.google.com/file/d/0BwVur07uzqm6cm5jLWNLRXIzb0k/edit?usp=docslist_api
[G2 Android Development] Saythis:
Hmmm... I'm noticing a trend with Mahdi.. I'm going to try running R7 on Vanir to see if it still occurs.
[G2 Android Development] hamisgood:
I'm on TeamEOS and have been running for about 5 hours and no reboots yet.
[G2 Android Development] murdoch1:
R7

I'm running on Temasek (Build 7) and no reboots at all. Maybe it is related to Mahdi afterall???
[G2 Android Development] TDSJR:
Read a post on Mahdi board about reboots. Asked for clarification on kernel, no response yet.
[G2 Android Development] murdoch1:
r7

Maybe spoke too soon. Just had a reboot. I do wonder if I tried r5 if it would make a difference....
[G2 Android Development] fLipz:
mahdi-render

i'm using mahdi0809 reverted back to R4 no reboots so far.

with R5 - R6 i experienced random reboot. still not flashing R7 yet.
[G2 Android Development] TDSJR:
Been on R7 since last night. No issues. So, about 10 hours? No reboots. Good stuff. Tweaked a bunch.
[G2 Android Development] Matze060906:
Now a reboot. The phone was in deep sleep...

https://docs.google.com/file/d/0BwVur07uzqm6bTF2ek15ZG52OXM/edit?usp=docslist_api
[G2 Android Development] hovanhuang:
I can't found anything about intelli hotplug in /sys. can you help me out? how can i switch from msm hotplug to intelli hotplug?

thx.
[G2 Android Development] bgx:
You can't! MSM is hardcoded!
[G2 Android Development] hamisgood:
Experienced my first reboot in about 10 hours. System was running perfectly during the time but only rebooted during deep sleep presumably. I'll leave it overnight to see if there's another reboot and hopefully the logs I upload can help.
[G2 Android Development] TDSJR:
Is ondemand working properly on V7. It seems to spend a lot of time at the max frequency.
[G2 Android Development] Raagh:
Why using on demand instead of interactive or even intellidemand?
[G2 Android Development] TDSJR:
I had used Intellidemand religiously on dr87's kernel, and loved the balance of performance, battery life and smooth UI. Since moving to KK source, I haven't been able to find an Intellidemand governor, on any kernel, that provided that same smooth UI. I tried Intellidemand on Render V4 and had that same little stutter, so I tweaked Ondemand to my liking, and then saw most of the time was being spent at the top end anyway. Long story short, basically forgot to try to tweak Intellidemand.:rolleyes:
[G2 Android Development] fLipz:
Rendified R7 now to your Intellidemand Tweaks :o
[G2 Android Development] TDSJR:
But, back to the original question. Any idea why it's spending so much time at the top end? Load is very light (reading, social media).
[G2 Android Development] RenderBroken:
No idea, I don't use it and leave it just for the likes of you guys. You could lower the optimal free and such. Also I am making a call to all of you helpful people. I would love to get people to list their personal governor settings and list why they use those particular setting. If certain setups get enough up votes I will use them in my kernel and give credit for doing so. I personally don't use any other governor than interactive. I don't have a good idea on what's the proper settings for the other governors. So this would help me greatly.
[G2 Android Development] Matze060906:
For me there is no reason to tweak the kernel. It runs great as it is with stock settings. The only problem I have is the reboots...
[G2 Android Development] TDSJR:
I would not be of any help with the "how's & why's" on this subject, just the end result.

I do appreciate your honesty with regards to my question, a lot of other dev's would ignore, give some B.S. response or just start hurling insults.

You're work, diligence, and integrity is a credit to the custom ROM community.
[G2 Android Development] simon_lefisch:
[MENTION=5438598]RenderBroken[/MENTION] had another reboot. Was using my phone then put it to sleep. 10 seconds after putting to sleep, phone rebooted. Gonna revert back to R4 for now as that has been the most stable for me. Log below. Hope it helps.

http://goo.gl/TCzxHW
[G2 Android Development] RenderBroken:
So there are numerious sysfs files that change different parameters. the new hotplug setting, they are here:

/sys/module/msm_hotplug/

I like to use ES Explorer. You will need to enable "Root Explorer" to allow you to view and edit root files. So when you select a sysfs file > Open as > Text > Then use the ES notplad to view. Now you can select the menu option and select edit.

So for example if you wanted to set the max number of CPUs allowed to be enabled while the phone is pf you can select:

max_suspend_cpus

(It will be located here: /sys/module/msm_hotplug/max_suspend_cpus)

Edit it and change the number to whatever number you like.

NOTE!!!! Please keep in mind that you are not allowed to be a complete idiot when editing sysfs file. This is not directed at you but to those that have blind disregard about editing SYSTEM FILES. Just be realistic. Don't change the value to something crazy. If you are unsure about what your options are then just ask me or google it! lol We are here to help!

This is just one small example of the power you can wield. There are way more hotplug settings that can be changed and tuned to your liking as well.
[G2 Android Development] hovanhuang:
Thank you Render.
[G2 Android Development] RenderBroken:
OMFG, I think I just realized the issue causing the reboots. I have used a recent commit of Dori's that makes the Powersuspend process more verbose to kinda show what is going on. Apparently it disables some of the different other modes and forces the hybrid mode. Since I have been looking not stop for a fix to these pain in the ass reboots I was looking at his source to find what he may have tried to over come them. I found that he made a change to powersuspend to forgo hybrid mode since it was causing issue for himself as well. SO I will be making the change asap when I get to the house. I will be re-adding back all of the other commits that I have taken out in hopes to fix this issue and will just carry on. I hope, hope, hope that this will be the end of these shenanigans and hope to bring back the stability along with the other major bug fixes that I have introduced lately. I am excited that this may finally be getting leveled out and I can move onto bigger things for this kernel!
[G2 Android Development] Matze060906:
Waiting for release... [emoji2]
[G2 Android Development] simon_lefisch:
Awesome! Glad to hear [emoji16] can't wait for the next release, and again (I'm sure everyone else here feels the same), thank you for your constant hard work. You are one of the most commited devs I have seen on this forum (not to say there aren't others). You consistently updating us with your progress does not go unseen and I thank you for your contribution in providing a great kernel for our awesome G2 [emoji106] donation coming soon when I get my next pay check.
[G2 Android Development] RenderBroken:
Thanks! :D

This may also be the cause for the battery not being as good. If the suspend process is ham stringed then that could very well keep the device from getting any worth while sleep. Building now!