yashsingh1/xdaforums huggingface dataset:
[G2 Android Development] SeVIIn:
I've noticed thus far that R14 performs just slightly worse than R13 for me. Also, benchmarks give it an overall lower score, and the audio glitches are prominent again with the screen off.
[G2 Android Development] RenderBroken:
Yea I feel asleep, I will finish uploading around noon cst

Yea, this hotplug is more conservative son when you are benching, you do so with only 2 to 3 cores instead of all 4 all the time the test is on. Weird about the sound though. Only changed the hotplug. At least this helps narrow down some of the issue. Thanks for reporting.
[G2 Android Development] Matze060906:
I think it's a war between the kernel and me, but the kernel doesn't know my secret weapon: RenderBroken! He'll make the kernel stable for me and I'll win this war... [emoji4]
[G2 Android Development] RenderBroken:
So is r14 working great for you?
[G2 Android Development] 1ceb0x:
r13 working great and smooth for me. i didn't even changed the suspend (i reinstalled my rom) and r13 doesn't give signs of reboot... let's see.. i hope i am not speaking too soon :)!
[G2 Android Development] Matze060906:
Till now it works...
[G2 Android Development] Raagh:
Hey [MENTION=5438598]RenderBroken[/MENTION] sorry to bother you. What hotplug re you using in yor latest version?

I been reading about inteli falcon and msm so i dont where we re now.

Thanks., good luck with R14
[G2 Android Development] Matze060906:
R14 use falcon hotplug...
[G2 Android Development] blacklight1025:
R13 is msm and R14 is falcon
[G2 Android Development] Matze060906:
R13 is msm too...
[G2 Android Development] blacklight1025:
I know, jus edited my comment
[G2 Android Development] Matze060906:
Reboot on R14. Phone was in sleep.

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

Another reboot. Phone was in sleep too. I switch back to R13. I'll have reboots too, but with this one the phone runs smoother. It seems to be that not the hotplug is the problem...

https://docs.google.com/file/d/0BwVur07uzqm6dnpfZE1pMEhCTVk/edit?usp=docslist_api
[G2 Android Development] 1Nexus:
R14 reboots when I put it to sleep (like Matze)

R13 works well when I made the change in ES explorer from 2 to 4 cores suspend. (What Render asked us to test) Gonna test it for the whole day to see if I get any reboots!
[G2 Android Development] phoenix_rizzen:
R4 was extremely stable on my D803, and is the one I always reverted back to. Usually within a day of trying a newer release. Been on R4 for the past several days without any issues.

R5 through R11 (I think that was the last one I tested) were very unstable for me, with lots of full reboots, hot reboots (runtime re-init), and SoDs. Never really complained, though, as I hadn't gathered any logs or done any leg work to make a valid complaint. :) And there were lots of others reporting similar issues. :)

Installed R14 yesterday. Charged the phone up. Played some music via Google Play Music to help the 3-year old fall asleep. Alarm went off on time this morning (although I had to hit snooze multiple times). :) Listened to a couple podcasts, checked e-mail, gmail, facebook, tapatalk, g+. No issues with DT2W or power button wake/sleep. Sent/received a handful of SMS via hangouts. Phone has been on and running for just over 11 hours now.

The only kernel settings I changed were:

* I/O scheduler: row

* Min CPU freq: 422 MHz

* Throttle temp: 75C

The rest were the defaults as shown in Trickster.

So far, so good. :)

Whoops, forgot to mention, I'm running Mahdi. Currently the 20140817 version.
[G2 Android Development] Matze060906:
And the same with R13...

https://docs.google.com/file/d/0BwVur07uzqm6TUlPUDJKaGtHdkE/edit?usp=docslist_api
[G2 Android Development] hovanhuang:
Running R14, 7am - 2pm no reboot or SOD. so far so good.

I raise the min freq to 424. and change I/o to fioqs. dt2w seems more responsive. do you think scheduler would have effect on it?
[G2 Android Development] BlakeSm:
Reboot on R14 stock settings, D800, AICP nightly.

Keep up the great work Render :good:
[G2 Android Development] 1Nexus:
Still no reboots on R13 with Render's recommended test changes!

6h 19m 33s on battery.
[G2 Android Development] SeVIIn:
Two reboots with R14 both while in use on my D801 running the latest Mahdi. Thinking of going back to R13, my phone seemed to like it a lot more and there's no sound clipping issue.

https://drive.google.com/file/d/0ByQU4ANsxailY1drcFNBUW83SzQ/edit?usp=sharing

https://drive.google.com/file/d/0ByQU4ANsxailM0hnR0tyMmxvdXM/edit?usp=sharing
[G2 Android Development] undeadking:
No VS980 R14? Or is it still baking lol [MENTION=5438598]RenderBroken[/MENTION]?
[G2 Android Development] fix-this!:
No reboot yet on r14. I do notice my 4g lte signal is lower on render. I tried the dorimanix kernel and i have much better strength? Seems odd but the kernel does play a role with both wifi and the radios. Any thoughts render? Im on a d800 unlocked on tmobile.
[G2 Android Development] abby_nitewolf:
Hello, just a question here since i seemed to confused myself.

I changed max cpu online susp on r13 to 4. But after a reboot it changed itself back to 2. Is this supposed to reset itself back or did i just do something wrong?

Also what is the difference between msm hotplug and falcon plug. I searched on xda and can't seem to find an answer. Thank you.
[G2 Android Development] 1ceb0x:
yes it is intended to change back, for safety. change it back to 4 and don't reboot.
[G2 Android Development] RenderBroken:
Uploading the others now. . . Too . . .Much . . .work.

I will be back later after finishing power nap lol
[G2 Android Development] 1ceb0x:
i don't want to go back to falcon hotplug. i love the way this kernel works with msm one.... even though on r13 i had strangely only one reboot in 12 hours, without changing the suspend to 4... i don't want to part away from it. did you found something causing these reboots so far?:(
[G2 Android Development] ThatKidDrew:
Changing the suspend stopped my reboots and SODs, thank you

VS980 running AICP 4.4.4
[G2 Android Development] RenderBroken:
No but I was able to find some clues. I was thinking of downloading the latest stock source and then re-applying my commits to it. I have an idea of where I want this kernel to be and I feel I would be having to do way more work if I don't do a clean setup of my own instead of basing off of Savoca's no matter how different mine is from the original source now. There are still some of his commits in the background. This is my latest idea. I also have to agree the msm_hotplug just plain performs better.

So what this would mean to you all is I would have to go back to a bare nothing kernel and start adding in all the goodness we love. Luckily its not too much I would have to addin feature wise so that should not be an issue but the first couple releases might not have everything.
[G2 Android Development] 1ceb0x:
I think we all agree here that in order to get rid of these pesky reboots is to do a clean kernel. There is no point on going like this if the problem doesn't seem to be where you think it is. While it will not have everything from the start, every kernel starts bare bones (except the ones that are based on something) so from my side, i don't mind to have to wait to have every stuff included - i don't change the settings anyway - i only let stock settings.

But yeah, it will be a lot of work to bring it from ground 0 but at least you can ONLY implement what we all need - one hotplug, only a few governors and a few schedulers, no undervoltages :).

I'm confident it will be the best kernel around for AOSP!
[G2 Android Development] musashihatred:
Hi, can someone post a screenshot of governor settings of interactive governor such as go_high_speed etc.

can't install Render Kernel im on Stock Based Rom as of now. Just want to replicate the settings (tho might not be efficient), because somewhat the stock kernel lags XD thanks in advance
[G2 Android Development] 1ceb0x:
You will not be able to replicate all the settings - some settings depend on the hotplug :).
[G2 Android Development] musashihatred:
yeap. just wanted to try tho. like timer rate etc. :/
[G2 Android Development] 1ceb0x:
above_hispeed_delay - 20000 1400000:40000 1700000:20000 (hotplug dependant)

go_hispeed_load - 90

hispeed_freq - 1190400

io_is_busy - 1

target_loads - 85 1500000:90 1800000:70

sample_time 40000

timer_rate 30000

sampling_down_factor 100000

timer_slack - 30000

up_threshold_any_cpu_load - 75

sync_freq 1036800

up_threshold_any_cpu_freq - 1728000

min cpu freq - 300 mhz

max cpu freq - 2.3 ghz
[G2 Android Development] Raagh:
Good luck render i know you can pull it off. You re going to use simple kernel or what source as a base?

Or you mean stock 4.4 sources?
[G2 Android Development] phoenix_rizzen:
/sys is a virtual filesystem that's created at boot time. Any changes you make to files under /sys only last as long as the kernel is running.

To make a change persistent across reboots, you'd need to use an app or script to write the changes after each boot.

Typos courtesy of my LG G2 (D803) running Mahdi-ROM.
[G2 Android Development] RenderBroken:
Yes I will be using Simple Kernel as the base. Really, the tree will be reset to almost stock. I just don't want to have to go through the process of making it "AOSP" compatible and such. So really it will be VERY close to stock. But this way I can build up each subsection the way I want it. There are just too many smaller items that I don't like that I believe could be hurting this kernel or at least my direction for it and I could comment stuff out and change kconfigs and such but the code will still be there and it will be unnecessary. This has been something I have been wanting to do since day 1 but I was not familiar with the G2 and its many "Facets" so I was daunted by setting it up from scratch. Savoca was a good starting point, I am carrying MUCH of what I have done/commits to the new kernel so I don't have to work as hard.

Dev Tip:

You can Clone a repo and use the format patch command to generate a number of patches you permit from all of the commits that make up that repo/tree

git format-patch

What the above means I can just turn my current stable branch into patches and then I can just apply them to my new kernel tree with:

git am *.patch

Then just fix the ones that don't patch cleanly by using:

patch -p1 < #.patch

git add new files

git am --continue

This will save me a crap ton of time. (Thanks [MENTION=3795148]neobuddy89[/MENTION] for dropping some knowledge on me awhile back!)
[G2 Android Development] abby_nitewolf:
I haven't had a sod or reboot since i set susp from 2 to 4 on r13. Awesome!
[G2 Android Development] Ace42:
Using R14+Mahdi 8-17 & everything has been fine for the last few hours on D800.
[G2 Android Development] BlakeSm:
Another reboot while using Twitch.tv app on R14, D800, AICP nightly.
[G2 Android Development] hamisgood:
[MENTION=5438598]RenderBroken[/MENTION] I'm still unable to boot without the Android process failing since R12. Painstakingly managed to get a log so hopefully you can help me with this issue.

Model: F320S

Rom: TeamEOS

Kernel: R14

Runtime: Dalvik

Others: I'm using xposed but it shouldn't be a problem as it never caused an issue thus far
[G2 Android Development] musashihatred:
Works great xD
[G2 Android Development] fix-this!:
V14 seems ok soo far. No reboots. I agree with the others render. Maybe start over from scratch.
[G2 Android Development] hovanhuang:
how you do with dt2w on R14? I'm with D800 on tmobile as well. so far which kernel is most stable for you?
[G2 Android Development] phoenix_rizzen:
R14 has been running on my phone for just shy of 35 hours now (single charge). No reboots, no SoD, no audio glitches. It's as stable as R4 has been on this D803.

The only "glitch", and not sure whether this is kernel or ROM related, is that a couple times per day, every running app will just close, and the launcher will restart. The status bar will be blank (just shows the clock and signal icons). Launching apps will take extra long, as they are loaded fresh from disk (you can see the full-screen "loading" screens for apps like Facebook, Chrome, etc). The really odd part is that the Recents menu will still be populated with all the apps that were running previously. It seems to happen most often when running Podkicker Pro for at least an hour, or Endomondo Pro for at least 30 minutes.

As this happens mostly while I'm walking to/from work or with my daughter, I haven't grabbed any logs yet. Hoping I can reproduce this while at work or home with time to grab and read logs.
[G2 Android Development] RenderBroken:
Thanks. I will take a look.
[G2 Android Development] RenderBroken:
I have already started the process of building from scratch last night. I am pretty excited!
[G2 Android Development] hovanhuang:
Similar here. For me, the same thing happen with error message systemui has stopped. I think thats mostly rom problem conflicting with the theme engine.

By the way, everybody is talKing about the audio glitching isssue. Whats that? Haven't noticing any things about my audio.
[G2 Android Development] phoenix_rizzen:
Hrm, could be. I do use an older theme and a newer icon pack. I'll try disabling those and see how it goes.

The only audio-related issue I've had with my phone was in the early days of the conversion to 4.4 kernel sources and the transition from LG's audio drivers to the Nexus 5 audio drivers. Those issues were the inability to change volumes and audio that was either way too loud, or way too soft. Those 2 issues were fixed over a month ago, though.

The "audio glitch" that most people discuss nowadays are pauses, blips, and skips in (mainly) streaming audio while the screen is off. I've never personally had this issue, nor have I read about any D803 users having this issue. No definitive cause nor solution has been found. Some find that installing Viper4Android solves it; others find that playing with DSP Manager solves it; others find that nothing solves it. It seems to be variant (and phone) dependent. Most of the complaints I've seen come from D802 users, with some LS/VS980 users.
[G2 Android Development] fix-this!:
It works good. As far as i know render has the only aosp kernel. Might b trying miui v6 this weekend to change roms up. I know render wont work on that.
[G2 Android Development] hovanhuang:
well. Vanir is turning dorimanz kernel to ASOP. but the latest 8/21, 8/22 built is unstable. I don't have a good dt2w on R14. do you? if yes, what's your setting?
[G2 Android Development] hamisgood:
And F320 users as well >.<
[G2 Android Development] c_brown93:
Render. Excited to see next version since you are restarting from scratch.
[G2 Android Development] DrugsBunny:
Getting constant com.process.phone error after flashing R14 first time trying this kernel on latest alegen rom soon as phone boots i get that error over and over no matter what i do or clean it will just keep crashing and im on D802

would love to try the kernel out :(
[G2 Android Development] RenderBroken:
Not sure what change on their end to cause such shenanigans but since I am building from scratch now, I hope to address the reason in the new build.
[G2 Android Development] TheSpaceManatee:
Its a Mahdi ROM issue if I'm not wrong
[G2 Android Development] phoenix_rizzen:
Yeah, looks like it's theme-related. I was using an older theme (Black Infinitum) that worked beautifully with the old theme engine in Mahdi. Doesn't seem to like the new theme engine.

Since switching back to the default Holo theme, the phone has been extremely stable running R14. Haven't had any issues since yesterday when I switched themes.

Typos courtesy of my LG G2 (D803) running Mahdi-ROM.
[G2 Android Development] Matze060906:
[MENTION=5438598]RenderBroken[/MENTION]: I had one reboot since this one. It seems to be that the kernel becomes more stable after a few days of running. I think we all had to test longer before you release a newer build.
[G2 Android Development] hovanhuang:
Same for me. looks like render kernel is jot compatible with alegen rom. Switch back to vanir 8/9 then everything's fine.
[G2 Android Development] RenderBroken:
Kernel rebuilding is going very well. I should have new builds for all tomorrow. First tests look to be very promising.
[G2 Android Development] Matze060906:
New build is with falcon or msm hotplug?
[G2 Android Development] 1ceb0x:
MSM
[G2 Android Development] zootzoot:
I can't get r14 to work on Alegen Rom either exactly the same error. What a shame.
[G2 Android Development] RenderBroken:
What about R12 or R13?
[G2 Android Development] jjlyons:
Do you get audio output when you use render with vanir?
[G2 Android Development] sai777:
Hey guys, I know this may have been asked before but I just want to know why dt2w isn't running on my device. I have R14 with Mahdi on my G2. I activated it in the settings but it doesnt work at all. Even if it works, I have to press like 20 times and then the screen will turn on. Can anyone shed some light on this problem?
[G2 Android Development] mhajii210:
R14 on D801 Mahdi 8-17 ROM

Hi guys. I just wanted to report I've been running R14 for over 72 hours now with no issues (reboots etc.) whatsoever. This kernel running on ondemand governor completely fixes my audio glitches when streaming music with the screen off. I'm VERY happy =D

mhajii210
[G2 Android Development] fix-this!:
Running like a beast on the new aicp nightly. I did have one sod this morning but none since.
[G2 Android Development] 1ceb0x:
r14 has 2 cores suspended and 2 cores online when in deep sleep. that's why it wakes up a bit hard. if you go back and you change this setting from the sysfs file like render said a few pages back (and don't reboot), it will work faster.
[G2 Android Development] hovanhuang:
I'm on alegen with dori now and waitting for renders new built. What audio output you meant?
[G2 Android Development] jjlyons:
Any sort of media audio output. Like playing music.
[G2 Android Development] hovanhuang:
All audios are fine.
[G2 Android Development] jjlyons:
Interesting, I'll have to try R14. Last time I tried I had no media audio with vanir.
[G2 Android Development] NEO2598:
R14 running awesome on Deviant Xone (D802,stock settings).
[G2 Android Development] Matze060906:
No reboots since 2 days with R13. I've set the min CPU freq to 192mhz. No problems with poweramp when the display is off.
[G2 Android Development] allan1229:
R14 is running super fast on slimrom. No reboots in 4 days so far.

D801
[G2 Android Development] fix-this!:
Hows the new fresh build coming render?
[G2 Android Development] RenderBroken:
Pretty good. I planned on having a test build out this weekend but ran into car trouble. So I spend all day Sunday working on it I stead of my new build. I was able to build anyways and it runs pretty great. Ran into one issue with L2 when I put it under heavy load for a long time but couldn't get it to happen again. So I am looking at what a have been the cause

Still it has been very solid the past few days.
[G2 Android Development] ThatKidDrew:
No reboots or sods on R14, but max frequency and governor settings don't stick. I use the built in kernel tweaker on AICP

VS980 running AICP 4.4.4

---------- Post added at 01:50 PM ---------- Previous post was at 01:44 PM ----------

Literally posted that comment, put my phone in my pocket, pulled it out and had a reboot. Here's the log ?

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

VS980 running AICP 4.4.4
[G2 Android Development] sai777:
I have R14 and Mahdi and I have seen reboots twice in the last 3 days. Can anyone tell me if I did anything wrong?
[G2 Android Development] Lawlrus:
You give no information, so no, no one can.

Your best bet is to download syslog from the play store and when you get a reboot, open it and get the last kmsg, then post it here.

Stock kernel settings? Device? Mahdi build date?

Sent from my Vs980 running CloudyFlex 2.6
[G2 Android Development] fix-this!:
Mine sticks. Use trickstermod.
[G2 Android Development] ThatKidDrew:
So if a different kernel setting app works then does that mean it's AICPs fault?

VS980 running AICP 4.4.4
[G2 Android Development] RenderBroken:
Thanks for the log!

Two things to note, the Max freq will show whatever is max freq at the time (Literally) so if the thermal driver bumps it down to 1.4GHz then that is what will show even if you are manually trying to set higher than 1.4GHz. This is how the driver works.

Point two is I have had others verify the the Kernel Tweaker app in AICP has been kinda flaky which sux because I don't mind using other apps. Trickster is just a tool I use for looking at Cores being online/offline, Max freq, etc.
[G2 Android Development] RenderBroken:
Also let me officially say that I don't require any more logs til after the next release. I am working on the new build now and should be ready soon. Since MY kernel is no longer based off of the same source it would no longer help me. Thanks to the community so far for the help and the support. I could do personal builds all day and night but I prefer to release them for the public because I love to learn and teach as well. No better way to do it.
[G2 Android Development] Lawlrus:
In regards to kernel tweaker? First thing I'd ask is are you using superuser, or SuperSU?

Superuser is trash and only works half-assed with some apps. Ever since I started using v4a, I've been flashing SuperSU since.

If you are using SuperSU, I would say its an issue with kernel tweaker and the kernel. The ROM itself shouldn't play any part in settings not sticking I don't think. I use trickster mod anyways.

Sent from my Vs980 running CloudyFlex 2.6
[G2 Android Development] ThatKidDrew:
Ya I use supersu 2.0.2 but I guess I'll be using tricks mod from here on out, thanks for all the responses

VS980 running AICP 4.4.4
[G2 Android Development] sai777:
I know RenderBroken said no need for more logs but I just had another random reboot and here are my logs. Thanks in advance.
[G2 Android Development] phoenix_rizzen:
Kernel Tweaker caused so many issues for Mahdi users that it was removed from the ROM. Consider freezing it with Titanium, or even forcibly uninstalling it, and using something else.

Typos courtesy of my LG G2 (D803) running Mahdi-ROM.
[G2 Android Development] HelloDominick:
flashed this on mahdi rom

usig d80 using latest build and im getting this on my screen " 780 fastboot mode started. 830-udc_start()
[G2 Android Development] sai777:
I think you soft bricked your phone. If you have nandroid backup, use that. If not, go to download mode and flash KDZ file and go back to stock. And then start all over from there.
[G2 Android Development] TDSJR:
Did you flash the patch? If you clean flashed, you still have to flash the patch 1st.
[G2 Android Development] simon_lefisch:
If you're using mahdi and want to use a different kernel, you still need to flash the mahdi patch before installing a different kernel. Reason being is that the patch contains the stock mahdi kernel as well as other necessary files for your specific device.
[G2 Android Development] Lawlrus:
Or just boot the ROM once and reboot and flash.

I never understood the idea behind flashing a custom kernel before even booting the phone once.

Sent from my Vs980 running CloudyFlex 2.6
[G2 Android Development] beandroid9:
Random Bootloop

I downloaded and flashed the R12 kernel.. now getting a lot of boot loops.
[G2 Android Development] 1ceb0x:
i think you mean reboots... it is a known issue. wait for R15 or move back to R4.
[G2 Android Development] DrugsBunny:
Just tried it with R12 and R13 both do same thing as R14 on latest alegen rom.
[G2 Android Development] mgear356:
So far I think this may have been the problem for my d802.

Before flashing s3 patch, I noticed under status, it states aa d801. I also experience reboots in r 13 and 14

After flashing s3 and r13 ..all is good.. Shall monitor further
[G2 Android Development] RenderBroken:
Thanks, I will look at their ram disk to see what change they have added.

I have been working too much lately so I have not had time to work on the new build this week. I should have time tomorrow to do so. I am really close to releasing it though. I just have to tighten up a couple things.