yashsingh1/xdaforums huggingface dataset:
[G2 Android Development] Matze060906:
I don't know which hotplug dorimanx and dr87 use. I ran these kernels with stock settings. You build R13 with msm and R14 with falcon, is it right? I had reboots with both builds, so I think the hotplug is not the problem.

Btw: In battery stats I see Google services with 10% or more. I see this since I flashed R13. I think it drains the battery life to much. In older builds it was not listed. I had wiped cache and dalvik in recovery, but it doesn't help. What can I do?

Here's a Screenshot from wakelock detector...
[G2 Android Development] 1ceb0x:
It is not kernel related. Use this xposed module to minimize the Google wakelocks: http://xdaforums.com/xposed/modules/mod-nlpunbounce-reduce-nlp-wakelocks-t2853874
[G2 Android Development] ThatKidDrew:
Search for NlpUnbounce. It's an xposed module that allows you to set how often nlp can wake your phone

VS980 running AICP 4.4.4
[G2 Android Development] 1ceb0x:
Beat you to it :P

R16 is up!

PS: R16 does not fix Alegen and CM11 (unofficial build 4.4.4) phone crash.

Render said he will add the other commits inside on the next builds so that this problem will get fixed.
[G2 Android Development] Matze060906:
Just had another reboot. I'll flash R16...

---------- Post added at 07:18 AM ---------- Previous post was at 07:02 AM ----------

Installed. Google play services is not listed in the battery stats. I did no changes, because I don't no where.
[G2 Android Development] 1ceb0x:
you don't need to change anything. just install and that's it. the module will do the work for you!
[G2 Android Development] Matze060906:
Great, thanks for your help... [emoji4]
[G2 Android Development] drkow19:
Hey, thought I'd post my... thoughts... on this kernel. I just downloaded R15 and am using it on AICP Verizon. Everything is working okay, Interactive tuned for high speed, ROW 2048, but I can't get some of the settings to stick. I tried using just Trickstermod, and the Thermal Throttle option always changes back to Off. I really wish there was a kernel for AOSP ROMs that kept my high thermal settings. I like to play games and you can tell the minute it starts throttling how the performance changes. The frequency sometimes changes too, but that might be because of thermal throttling. I keep it at 300-172000. Performance is great, before the settings start to change. No reboots or lockups here.

edit: Yep, just got the cursed reboot, as soon as I typed that last sentence and hit Submit, lol.
[G2 Android Development] Matze060906:
I have the same problem: If I write the kernel runs great - reboot.

Solution: Don't write the kernel runs great... [emoji12]
[G2 Android Development] drkow19:
Umm, I just had something really weird happen. It rebooted again (I am not undervolted and running pretty standard setup with R15) and when it booted, and during boot screen, all I saw were really weird lines! I did not have my other phone charged to take a picture. It booted and ran fine, but the display was completely scrambled. I just held the power button to turn it off, turned it back on and back to normal. Pretty scary!

It seems to be rebooting when it is going to rest, like when the display has just turned off.
[G2 Android Development] Matze060906:
Vertical black lines on the right side of the display?
[G2 Android Development] 1ceb0x:
this is not something you specifically get from this kernel. it is something you can get even if you run stock :).

its a hardware failure that happens at very high temperature.

happened with mine. the connectors from the motherboard to display is getting 'released' due to heat.

i would avoid playing with min-max cpu freq if i were you. you specified you keep yours underclocked to 1.7. that's not actually a good idea because 1.7 is one of the 3rd steps from interactive governor.
[G2 Android Development] drkow19:
No, all colors, and the lines were scattered, some horiz some vert. It was reacting to touches and the colors were changing. The guy below is probably right. My display has been replaced once, it might have done that. The CPU was only at 70. It has just never happened to my G2 before.

I've never had any problems with keeping it lower like that. What do you mean by 3rd steps?

I installed the recently released R16 and am trying that now. First impressions: WOW. I think I had an issue with Kernel Tweaker (an AICP app) trying to set old settings over Trickstermod. I cleared data to KT and it this running stable now. I've never messed around with Interactive kernel settings before, but I have some fast ones that are making this phone perform better than I have ever seen it. The temps are low too, only about 73 while gaming. I am dev'ing a game right now, and I have an FPS counter in the HUD, plus I can just watch how smooth the gameplay is. I know this CPU/GPU combo can do 60 fps smooth but most kernels have not done that, or they overheat quickly. So I mess around with the settings a bit usually to keep the CPU frequency high, but not cook the phone. Anyway, with R16 the game is pretty much stuck at 60 FPS like a rock for an entire 5 minute session, no overheating. Amazing!
[G2 Android Development] bgx:
R15 till now without reboots in my D802 with last Mahdi. Going to install R16 now. Good work render!
[G2 Android Development] Matze060906:
Any other devices with reboots or only d802?
[G2 Android Development] mhajii210:
R16 audio distortion on D801 Mahdi 8-17 ROM

I just wanted to report R16 was giving me weird audio distortion (sounded like buzz sounds) when playing music videos on the Vevo app. It's probably stuttering or something. Did not have any problems streaming Spotify over Bluetooth with the screen off. I reverted back to R14 and Vevo plays normally again. I was using all default kernel settings (didn't make any changes). R14 gives me random reboots, but fortunately it happens every 3 days or so. I'll stick with that for now. I will try again when R17 comes out.

mhajii210
[G2 Android Development] Z0ld3n:
Just got reboot when trying to turn screen on. Here is log: http://pastebin.com/98gdpLdf I'm using latest Mahdi on D802 with kernel version R15. Also can confirm sound distortions.

Wysłane z mojego LG-D802 przy użyciu Tapatalka
[G2 Android Development] ThatKidDrew:
Not necessarily true, I set all mine to 600 seconds. Some people have set them to 900, so I'd say it's more about personal preference

VS980 running AICP 4.4.4
[G2 Android Development] RenderBroken:
I have been looking at the logs and I see a common thread that has been popping up. It has to do with the suspend process. The warning is saying that a core was not it the correct state when it was time to bring the core down into suspend. I have found some solutions for this that I will work to implement. As for audio, I am going to be doing a sound driver overhaul as well. So far I have been bringing up different sections of the kernel. Sound is next.
[G2 Android Development] fix-this!:
Tap to wake is slow but its pretty good. My phone feels smoother with intelliactive.
[G2 Android Development] hamisgood:
Sorry to report this again, but this kernel isn't working on TeamEOS anymore and I can't get a log due to the process has stopped error again. Not sure if they changed anything..

Model: F320S

ROM: TeamEOS
[G2 Android Development] 1ceb0x:
I believe you are talking about com.android.phone process? If yes, Render is well aware of this and he is currently looking to fix it. An attempt has been made in R16 but it needs more attention into it.
[G2 Android Development] RenderBroken:
Thanks! You are correct. I will be downloading and extracting the ramdisk tonight to see what else is missing other than the multi sim bootclasspath.
[G2 Android Development] RenderBroken:
OK Thanks, I was curious. I will look at the different sysfs settings it uses to compare to mine. I do know that mine is more conservative since it is used as the default daily driver. IF I see that this is something that could fill in a gap then I will re-add it back. Thanks for the response.

I am also looking into adding in SmartMax. The main thing I want is to have governors for different situations. If you want battery,user Ondemand, if you want a pretty smooth experience at the cost of some battery, use interactive. You see what I mean. I just dont want overlapping like I felt with intellidemand. But to have a gaming governor by using intelliactive so you dont have to jack with the daily driver settings in interactive. That is something I can see doing.

Lastly, I finally have noticed the sound issues some have reported. I originally though it was a bluetooth connection issue but I am pretty certain it has to do with Min freq. For those out there with constant sound issues, does the problem still exist while the screen is on and you are doing stuff? (IE all cores are on and above min freq) I hope the future sound overhaul will help alleviate this.
[G2 Android Development] RenderBroken:
Anyone get any reboots with R16?
[G2 Android Development] Matze060906:
I flashed R16 a few minutes after release. No reboots since flashing...

But you know: If I write "no reboots", they will come...
[G2 Android Development] pqee:
No reboots here either on EOS.
[G2 Android Development] Matze060906:
And here's the reboot...

https://docs.google.com/file/d/0BwVur07uzqm6eUk4TGNuMWxXUkk/edit?usp=docslist_api

I think the only solution for me is: Never say it runs without reboots... lol
[G2 Android Development] bgx:
Reboots no but sod with R16
[G2 Android Development] stewyfallingup:
Man I'm sorry. Although pretty funny, it must be annoying. [emoji17]
[G2 Android Development] murdoch1:
R16

Been on R16 since release on D802.... No problems whatsoever..... Mahdi 17/8
[G2 Android Development] simon_lefisch:
Flashed R16 last night. Let it settle and has been running smooth so far. Will report back later tonight after having R16 installed for 24 hours. VS980, clean Mahdi 8/17.
[G2 Android Development] RenderBroken:
This made me laugh out loud! Sorry bro.
[G2 Android Development] Matze060906:
It's very crazy, isn't it?
[G2 Android Development] sai777:
R16 is so far buttery smooth and I experienced no problems and will update in a day or two. :good:
[G2 Android Development] ZeNiXxX:
yeah here to. R16 seems to be very smooth don't know how the Batterylife is, But it seems More smooth than barts Version of dorimanx kernel

Gesendet von meinem LG-D801 mit Tapatalk
[G2 Android Development] mhajii210:
Sound distortion

I am getting sound distortion (happens seemingly at random and it's not very noticeable) when playing YouTube or Vevo videos. I have not noticed it at any other time. Of course the screen is on when watching the video. I installed Viper4Android and still the same glitch. Same thing happens on Dorimanx kernel, but stock Mahdi 8/17 kernel on my D801 or your R14 kernel does not have this bug.

mhajii210
[G2 Android Development] Z0ld3n:
It's happening less frequently with screen on but it's happening anyway. Dr87 had same guess about min freq. He tried to fix it in few attempts but raising min freq didn't help. It's just that everything was fine on Mahdi (both sound and dt2w) up to one release of rom (can't remember the exact date). Dr87 said that he didn't change anything sound or dt2w related in kernel so I'm starting to believe it might be more rom than kernel related (if it's possible).

Wysłane z mojego LG-D802 przy użyciu Tapatalka
[G2 Android Development] RenderBroken:
I agree that it is rom related. There is a sysfs settings:

write /sys/devices/virtual/input/lge_touch/touch_gesture 1

If you actually look at it though it shows blank. This is part of the reason DT2W is not working correctly or at least a side effect
[G2 Android Development] 1ceb0x:
Dude have you even tried a fresh install? Or at leadt changing the rom? You seem to be one of the constant guys that gets reboots.

When was the last time you did a clean flash? (Wipe data, system, caches)? Also - do you change some settings from the kernel? Do you use trickster or kernel tweaker or both in the same time?

I mean - it gets frustrating to see that one user still has problems while majority of people report nothing but positive results.
[G2 Android Development] fix-this!:
2 reboots since i installed 16 tonight. Went back to 15 and had yet another lockup. :(

---------- Post added at 11:07 PM ---------- Previous post was at 11:05 PM ----------

Umm read the thread. Many people are having lockups and reboots. Including me on aicp. Always have since i started using render. The dev is well aware.
[G2 Android Development] 1ceb0x:
I read the thread daily. What i am saying is 10 people reported that r16 works wonderfully without reboots and 2 people reported reboots and lock ups. I know we have those but i kind of doubt a bit that we should still have them now in R16.

Something tells me that either your rom is acting fishy or indeed the kernel needs more commits.

I looked in one dmesg posted by someone way back on R16 and i found out that that the cpus are not handled well while they should be suspended. We found out an interesting commit coming from mako and Render will commit it any time soon. We will see how well that plays with you guys.
[G2 Android Development] simon_lefisch:
[MENTION=5438598]RenderBroken[/MENTION] just had a reboot on R16. Log below. VS980 Mahdi 8/17 clean install.

http://goo.gl/SzcpWo
[G2 Android Development] RenderBroken:
Thanks!

Yrd the problem is the way cores are offlined during suspend. From what I can tell the issue has to do with wanting to offline the core into a certain suspend state but the CPU is not where (In the suspend cycle) the PM driver thinks it is. This I am trying to alleviate.

Also I understand the frustration, I am on the opposite. Luckily everyone so far has been very cordial. It sux because I have the rare superphone so I dont get the issues like everyone else so I cannot verify. I do get logs and that helps tremendously. It sux because users want a decent AOSP kernel that performs better than Dorimanx and simple (Mahdi). Side note. I just benched R16 and was able to hit 35K in Antutu. I have said before, as long as everyone is patient like they have been I will continue to work through the reboot issue. One thing to note is I do believe re-basing has been successful. Now I can build up the kernel without worry there is a nefarious commit that will go unseen causing havoc. I will keep looking into the reboots guys Thanks!
[G2 Android Development] Matze060906:
Yes, I did a clean install yesterday and yes, I changed something in trickster mod. But after a reboot it was set automaticly to default. This don't stop the reboots. I'm not the only one with reboots. I know it, because I opened a thread in a German forum to present this kernel. There a some people with reboots too. They are using Mahdi and aicp and they all have the d802. And here are some people too with reboots.
[G2 Android Development] RenderBroken:
Another thing I have noticed while digging is:

This is from my script

############################

# Power Settings

#

echo 4 > /sys/module/lpm_levels/enable_low_power/l2

echo 1 > /sys/module/msm_pm/modes/cpu0/power_collapse/suspend_enabled

echo 1 > /sys/module/msm_pm/modes/cpu1/power_collapse/suspend_enabled

echo 1 > /sys/module/msm_pm/modes/cpu2/power_collapse/suspend_enabled

echo 1 > /sys/module/msm_pm/modes/cpu3/power_collapse/suspend_enabled

echo 1 > /sys/module/msm_pm/modes/cpu0/power_collapse/idle_enabled

echo 1 > /sys/module/msm_pm/modes/cpu1/power_collapse/idle_enabled

echo 1 > /sys/module/msm_pm/modes/cpu2/power_collapse/idle_enabled

echo 1 > /sys/module/msm_pm/modes/cpu3/power_collapse/idle_enabled

echo 1 > /sys/module/msm_pm/modes/cpu0/standalone_power_collapse/suspend_enabled

echo 1 > /sys/module/msm_pm/modes/cpu1/standalone_power_collapse/suspend_enabled

echo 1 > /sys/module/msm_pm/modes/cpu2/standalone_power_collapse/suspend_enabled

echo 1 > /sys/module/msm_pm/modes/cpu3/standalone_power_collapse/suspend_enabled

echo 1 > /sys/module/msm_pm/modes/cpu0/standalone_power_collapse/idle_enabled

echo 1 > /sys/module/msm_pm/modes/cpu1/standalone_power_collapse/idle_enabled

echo 1 > /sys/module/msm_pm/modes/cpu2/standalone_power_collapse/idle_enabled

echo 1 > /sys/module/msm_pm/modes/cpu3/standalone_power_collapse/idle_enabled

echo 1 > /sys/module/msm_pm/modes/cpu0/retention/idle_enabled

echo 1 > /sys/module/msm_pm/modes/cpu1/retention/idle_enabled

echo 1 > /sys/module/msm_pm/modes/cpu2/retention/idle_enabled

echo 1 > /sys/module/msm_pm/modes/cpu3/retention/idle_enabled

Here is what stock AOSP kernels use:

# Enable Power modes and set the CPU Freq Sampling rates

write /sys/module/lpm_levels/enable_low_power/l2 4

write /sys/module/msm_pm/modes/cpu0/power_collapse/suspend_enabled 1

write /sys/module/msm_pm/modes/cpu1/power_collapse/suspend_enabled 1

write /sys/module/msm_pm/modes/cpu2/power_collapse/suspend_enabled 1

write /sys/module/msm_pm/modes/cpu3/power_collapse/suspend_enabled 1

write /sys/module/msm_pm/modes/cpu0/power_collapse/idle_enabled 1

# From the original setup scriptage, revisions != 1.0 disable retention...

write /sys/module/msm_pm/modes/cpu0/retention/idle_enabled 0

write /sys/module/msm_pm/modes/cpu1/retention/idle_enabled 0

write /sys/module/msm_pm/modes/cpu2/retention/idle_enabled 0

write /sys/module/msm_pm/modes/cpu3/retention/idle_enabled 0

Obviously I use numerous more Low Power Modes, This could possible by a cause for some of yalls reboot woes. These are different suspend states (AKA C-States). Some phones can handle deeper Suspend states. I am going to do a test run using the "stock" settings to make sure there are not any adverse effects. If none I will build again tomorrow and those of you who have numerous reboots, I would appreciate your assistance in testing the newest build. Just thought I would share.
[G2 Android Development] Matze060906:
All the people with reboots have to do a clean install of rom and the test builds or not?
[G2 Android Development] RenderBroken:
Nope, Just install the new build later today (1:15 am here) and report back. If you could leave the kernel stock though for the time being. Just want to rule this out first. i really hope this works for you.
[G2 Android Development] Matze060906:
Ok, I'll do this. Btw: here it is 8:18 am). I hope this too...
[G2 Android Development] RenderBroken:
I have also set it so when the screen is off cpu-boost suspends as well along with the hotplug. I am excited for the next build because I have been looking at the source of other kernels that don't have reboots and we are pretty much the same. The only real difference is the above changes. Also Good Morning! lol Time for bed for me. Danka
[G2 Android Development] 1ceb0x:
Hope i can also help testing this in CM land... I don't know if you made further progress in that. I guess you are first taking care of the suspend states.
[G2 Android Development] jeff5347:
Render didn't get a chance to run but 16 is great fresh install of 8/29 aicp and 16. No freezes reboots nothing. One thing I tried nameless and the kernel keeps the ROM from booting. Not sure what nameless is built w but a while ago it used to boot but not anymore. Great job
[G2 Android Development] RenderBroken:
I think I figured it out. The change that I made must have not been saved. I took another look at the file and its missing. I re-added it back and am about to test. This should also fix Team EOS.
[G2 Android Development] RenderBroken:
Just wanted to let yall know that I have confirmed that I can now boot AlegenRom just fine now that I had made the change to my ramdisk. I will be building shortly.
[G2 Android Development] RenderBroken:
Already started uploading new builds.
[G2 Android Development] Matze060906:
Just installed. I'll run it with default settings, hope the reboots are gone. With R16 I had only the reboot I mentioned here. Since this one, the build runs without any problems.
[G2 Android Development] RenderBroken:
R17!!!!

Reworked MSM_Hotplug! Now it works WITH CPU-Boost!

CPU-Boost - Now suspends while screen is off so its now boosting the cpu on touch while the screen is off anymore. Also now works to help "wake" the hotplug when you turn the screen on!

New Governor! Optimax - I wanted to try out a few new governors and get yalls opinions. Seems to be more performance based but that's with all default settings. Let me know!

New IO_Schedulers will be in the next build.
[G2 Android Development] RenderBroken:
Also forgot to mention that I had reverted my custom C-States back to "stock" settings. I may need to build up the appropriate subsections first before forcing them as enabled.
[G2 Android Development] Lazy79:
Latest version runs great so far. If you're looking for interesting governors.. Maybe HYPER is something you might like. Thank you very much for all your passion and work!
[G2 Android Development] RenderBroken:
If you get more reboots, please let me know. I will build a special kernel for you that makes it so when the suspend process is running, console (The terminal) does not suspend too. This way I can gather more info on the process. Also I have found a few other things to try. I will get to the bottom of this! lol
[G2 Android Development] 1ceb0x:
Just installed on unofficial cm11 for d802 - works like a charm. com.android.phone process is not crashing anymore. Will test heavily tonight and tomorrow and report back although i have a mega feeling that this build will have 0 reboots. Thank you very much Zach!
[G2 Android Development] Matze060906:
I can't get more reboots with R16, because I flashed R17... [emoji4]

Dt2w works much better with R17. Thanks for the good work.
[G2 Android Development] fix-this!:
Flashed aicp and r17. So far so good. Optimax is a pretty laggy govenor compared to intelliactive or interactive.
[G2 Android Development] Orvils:
Used stock rom for a week and this kernel has got from r4 to r17 ? awesome! Anyway r17 working fine on unnoficial cm.
[G2 Android Development] goast:
Hi don't know if someone who really knows.. Maybe [MENTION=5438598]RenderBroken[/MENTION] can tell me... I see mp decision is off by default.. Is that because there is something else built in the kernel in it's place?
[G2 Android Development] RenderBroken:
Yes that is correct. I use msm_hotplug
[G2 Android Development] sai777:
No problems with R17 so far, awesome job again RenderBroken. BTW what governor do you all use most of the time?
[G2 Android Development] RenderBroken:
Interactive. It's the default governor.
[G2 Android Development] ThatKidDrew:
R17 is so far so good for me, no reboots or SODs. Max frequency settings isn't sticking though (trying to set it to 1.7) and I'm using trickster mod

VS980 running AICP 4.4.4
[G2 Android Development] fix-this!:
So far so good on 17 and aicp. Id say 15 was the smoothest and best battery but sadly it had reboots.