yashsingh1/xdaforums huggingface dataset:
[G2 Android Development] bleached45:
The stock interactive settings are always recommended. Render made some edits (improvements) to interactive (including a new hot plug). In very happy with the balance for me.
[G2 Android Development] RenderBroken:
Sure, let me know and I will do what I can. Feel free to ask in thread but if you do just mention me so I am sure to see it.
[G2 Android Development] RenderBroken:
Tru dat! Thanks for assisting!
[G2 Android Development] ckyy:
Ah, didn't know that.
[G2 Android Development] Saythis:
Yep, as I recall Interactive is the only governor to offer Falcon Hotplug driver for RenderKernel.
[G2 Android Development] BFruchtfliege:
Dont work on my latest PACman-Rom 4.4.4. (05.08.2014)

Courios is, that LG-Logo load and after 20min LG-Logo (WITHOUT reboots/loops) i decided to go back with nandroid :)

after this i looked which base PACman really is, but i didnt find anything. Its a mix of PA,AOKP and CM, but which Base? And is there a Kernel for?
[G2 Android Development] NisseGurra:
There is big lack of kernels for the 320 devices.

I like to start a bounty for an CM11 320 kernel.

I put in 30 USD as a start.

Any other 320 users like to join in?
[G2 Android Development] ckyy:
Do i need to set it with an application? Because i don't see an option to change it (hotplugging) in trickster.
[G2 Android Development] RenderBroken:
Its all good.

Falcon_hotplug works with all governors. But instead of this hotplug acting like the default one (MPDECISION) it doesn't calculate load on its own. It directly scales according to the load generated by the governor itself. What this means is the way interactive calculates load is more aggressive so hotplugging will be more aggressive compared to Ondemand. Ondemand is more conservative with how it calculates load and will hotplug less aggressively. Also I don't need the hotplug calculating load along with the governor calculation load for no reason. Its wasteful CPU time.

But the reason I use interactive is how well it works. Its simply the BEST governor our there. I can adjust timings depending on load. no other governor does that unless they are based of interactive (Intelliactive). The reason I do not use intelliactive by default is the needless extra "stuff" that it does. I just need a governor to scale correctly depending on what task I am doing. If I am reading a book don't jump to max freq when I turn the page (Intelliactive). If I am multitasking with Gmail, Calendar, Drive, etc (My work) I need the governor to ramp up but when I am reading an email I don't need it to STAY at max freq.

Sorry for the long winded explination. I like to educate others out there if they are willing to learn. I am by no means a master at this either.

I am looking at building for CM after releasing R4. I think I have worked out a way to do so without having to build a completely separate kernel. So we will see . . .

There is not an option because Falcon_Hotplug is fairly new. If you want to change the settings go to:

/sys/kernel/hotplug_control/
[G2 Android Development] HueyT:
PAC is 4.2.2 based (despite it's outer appearance of 4.4.4). This is 4.4.4 based. You must use JB (4.2.2) modem flash after your PAC rom if you're already running KitKat for PAC to even boot. If you're still on JB and running PAC then this Kernel is not for you. Look at Savoca's Furnace 1.8.1 kernel (or older for AOSP)
[G2 Android Development] RenderBroken:
Thanks for the great explanation!
[G2 Android Development] crnkoj:
Btw I think I stumbled across a possible reason for the sound distortion during idle/screen off. I'm using the aosp dorimanx version but it shouldn't differ much. I found out that if I use the msm_hotplug it doesn't matter which governor I use and it doesn't distort the sound, while if I select alucard_hotplug it doesn't matter which governor I use as it distorts sound on all. So perhaps your hotplug is the actual reason why some have the distortions, so possibly look into it. I'm in holidays now hence I didn't manage to install your kernel again, as I'm out of country and have limited Internet access....
[G2 Android Development] somboons:
It's work for cm11?
[G2 Android Development] bgx:
Read four post before!!! :eek:
[G2 Android Development] RenderBroken:
I listen to audio books all day. I have the D800 so it may be a model issue. What model do you use? Can others chime in and let me know if they are having audio distortion? Let me know, but I don't think its the hotplug. Otherwise it would happen to everyone and it doesn't. If those of you are having audio issues whether it be slight pauses or distortions, please give me the following:

Phone Model

Rom

If you have changed from the default kernel settings, list the settings you did change.
[G2 Android Development] bgx:
D802 Mahdi Rom

Audio distortion while listen to apollo player over bluetooth some time.
[G2 Android Development] elementalfusion:
Hey Render, just wanna say really great work on your kernel! Was using Mahdi with R3 previously and I was also getting the audio decepticons attacking the phone.

Then I flashed slimkat just to try it out, and surprisingly it doesn't have any decepticon sounds while screen off. Flashed R3 onto slimkat and tested again, perfect audio even while screen is off. Music app used is Spotify.

My model is D802, hope this helps!
[G2 Android Development] Raagh:
Exactly the same. Audio hicups on mahdi+render but not on Temasek+render
[G2 Android Development] RenderBroken:
So far the only common thread is the phone model. Anyone else? Those how have reported, thank you very much!
[G2 Android Development] Saythis:
Thank you very much for the explanation :good: I would absolutely love a CM variant of your kernel.
[G2 Android Development] crnkoj:
D802

Mahdi 19/7

As said in the previous post it's not your kernel, but I thought it might be useful what it stumbled upon.

I'm having these distortions during Skype calls either on the headset or loudspeaker, I didn't notice it before as i normally don't listen to music or use Skype on the phone. One more thing I saw is that if the Skype call is active and I changed hotplug to Alucard it made the distortion sound on clicking apply and the sound came in regular time intervals, as if it would be timed by a timer.
[G2 Android Development] MaluNoPeleke:
Same audio problem here with Spotify on Mahdi and a D802. I cannot listen to music anymore :(
[G2 Android Development] Matze060906:
I don't understand why people have problems by hearing music on d802. For me there's no difference between Mahdi and stock rom. I'm using poweramp and the sound is clear as it is.
[G2 Android Development] SeVIIn:
Yeah I have sound problems on my D801. I believe it's a mixture of the ROM and kernel. Mahdi being the worst unfortunately. Also, it's very intermittent, sometimes I can go hours without distortion other times only minutes. Raising the cpu to 422 or changing the hotplug (if available) does help sometimes.
[G2 Android Development] livadaki:
The same for me, D802 + Mahdi + Render kernel
[G2 Android Development] bleached45:
D800 with Mahdi 7/29 and R3. I get the audio hiccups as well. The sound doesn't pause, it actually makes a weird "digital" kind of sound. Just a small one for a half a second. But it is a known issue on Mahdi (although, the hotplug has been thrown around in that thread before). And it can go for a while without hearing any glitch to every 15 to 30 seconds.

It is almost exclusively when screen is off. I did raise the min freq to 422 but other than that, all stock settings (except for faux sound control, I upped the Analog gain).

But this is known for Mahdi (and afaik, only Mahdi). It may not be something Render Kernel can fix. I'd love to try and build Mahdi with the G2 audio drivers but wouldn't know what to change. Anyways, while I'm glad you are working on it, don't beat yourself up over it until dr87 gets it sorted out in his ROM/kernel.

Thanks for the hard work. Looking forward to R4.
[G2 Android Development] phoenix_rizzen:
Sorry for the delay, been very hectic with household issues.

I have a D803.

It's mostly habit from my Optimus G days, where bumping the lower bound improved performance, especially with screen off or just after turning screen on.

I've never had issues with skipping or hissing or distortion when using MX Player, PowerAmp, Google Play Music, or Podkicker Pro. But, I still bump the lower freq. Maybe it makes a difference, maybe it's a placebo, but it works for me. :)

Typos courtesy of my LG G2 (D803) running Mahdi-ROM.
[G2 Android Development] RenderBroken:
I was going to suggest the exact same thing for others to try. If they can give it a shot and let me know that would be great!
[G2 Android Development] MaluNoPeleke:
422 as minimum frequency makes no difference
[G2 Android Development] SeVIIn:
I've bumped mine up, works fine for listening to music, the real annoyance is notifications, they always sound like my phone is dying when the audio glitch hits. I think this occurs most often when I receive a notification while the phone is in deep sleep. Haven't found a way to fix it completely aside from avoiding a couple of different ROMs, sadly they're my favorite heh.
[G2 Android Development] fix-this!:
No audio bugs on aicp. Its probably mahdi guys, not this kernel.

V4 this weekend render?
[G2 Android Development] RenderBroken:
:D Today if I can help it. I was going to work on it the past two days to finish it but my Virtual Server was down. Now it is back up and running great. I work remotely from my main job alot and I was not able to remote in. Uhg. But I do plan on releasing ASAP. I was looking into the issue with DT2W and the power button not responding like it should. Then I was reading the Mahdi thread (WARNING Conjecture ahead!) and this along with audio problems are being recorded with the 7/29 build. I even flashed my earlier builds that had perfect working DT2W for me and still the problem persisted. Good news is I don't have to keep spinning my wheels trying to figure this out. Bad news is the problem seems to be with Mahdi 7/29 itself so not much I can do. . . So I will just move on and commit a few more changes that I have bookmarked. After that I will release.
[G2 Android Development] simon_lefisch:
Audio prob seems to be variant related. I'm on vs980 running mahdi 7/29 and have no probs with audio at all. All stock settings. Seems to be d80x models.
[G2 Android Development] RenderBroken:
I agree. I would like for some of them to try another rom to see if problem persists. But I have the D800 and have NO issues. Also flashed and old build of Mahdi and DT2W works just fine. So something with the newest Mahdi build is conflicting. Hope it can be fixed . . .
[G2 Android Development] RenderBroken:
Just so I am not leading people on, I wont be releasing til Saturday. I was hoping to have more time to finish but with School starting back up its pretty crazy for myself. Also tomorrow I will be out of town soooo Saturday is it. It is already such a big change from R3 as far as work put in so I need to stop somewhere, release, and make sure the builds continue staying nice and tight.
[G2 Android Development] simon_lefisch:
Thanks for the update. I flashed back to stock Mahdi just so I could get a good comparison of stock and Render. This will give me extra time to get a better comparison. Looking forward to R4! Keep up the great work, and thanks for providing your kernel for us to use [emoji106][emoji16]
[G2 Android Development] chrisexv6:
Good thing you clarified otherwise we would be forced to call you a kerneltease!

:)
[G2 Android Development] RenderBroken:
lol yea. . I try to keep my word as much as possible. Kernel work is usually after Fam, work, then play, then kernel work though kernel work is alot like playing. I use all of my own builds and I am always wanting to add and improve!
[G2 Android Development] SeVIIn:
Are you following a guide or anything? I was thinking of trying the same, building from source, but I haven't ever done it before so I'm trying to find the best way to start.
[G2 Android Development] bleached45:
I actually just started trying to build stuff (ROMs, but I need more HD space to build). I suggest XDA university, it helps you get set up and getting sources downloaded. Though, not sure what goes into kernels. Good luck!
[G2 Android Development] fix-this!:
Hoping v4 is availble tomorrow as i do my weekly aicp update. Sadly i had my first reboot - lockup this morning when my alarm went off. Seems to be related to deep sleep id say.
[G2 Android Development] TOdblD:
Flashing now in car.
[G2 Android Development] capuagenclik:
I am on MAHDI ROM i enabled fastcharge and then disable it now MTP doesnt works. When I plug it in the phone just charges how can I turn MTP back on.
[G2 Android Development] TOdblD:
Flashed and running now and so far so good. A lot of good reviews for this kernel, glad to have found out. Thanks dev.
[G2 Android Development] chrisexv6:
SOD then reboot this morning....took phone out of pocket because I felt a notification, the screen flashed on then off quickly (I think I ended up with my finger over the proximity sensor so it told the phone to turn the screen back off). After that couldnt wake it with double tap or even power button, then it rebooted.

Running on AICP 8/1 nightly, RenderKernel R3

Last kmsg pastebin - http://pastebin.com/GpegjDaZ
[G2 Android Development] SnakeHaveYou:
Well, something strange happened to me this morning..

I was on a call, and the phone went off unexpectedly..

I Tried to power on with the power button and nothing..

Tried to power on with the power button and volume down and it just started to power on, but after the LG logo and the dimmed LG logo, it just went off again..

So I tried a few times, and nothing ..

I connected the phone to the PC, and it recognised it.. To my surprise, because i was thinking the phone was off.. So, while the phone screen was off, i rebooted with "adb reboot recovery" and it booted correctly into TWRP..

In TWRP, rebooted into system, and nothing!

So i rebooted into recovery again with adb..

In TWRP, strange white vertical spots appeared, like the ink in the LCD was blurred..

Flashed again SlimKat (NO WIPES!) only to replace RenderKernel, and the system just booted..

The white vertical spots stayed there, only visible with maximum brightness in Chrome and other apps with a grey or black background..

Now they're dissapearing, i think.. Just an advice guys!

BTW.. No logcat :( In the hurry, i forgot to save it to a file..

The spots are vertical spots, no lines..
[G2 Android Development] SeVIIn:
Yeah, just a little lost on what to pull from Mahdi, then from Dr87, and finally Render's GitHub to make it one full complete package.
[G2 Android Development] Raagh:
I have the same problem. I build full roms before but never make a full rom pulling things from diferent sources. I ll be returning home on tuesday. Add me on hangouts we ll figure it out together. Send me a pm

---------- Post added at 07:49 PM ---------- Previous post was at 07:46 PM ----------

Maybe we can share some suff, us 3.
[G2 Android Development] gamepro602:
If you turn that on you won't have access to your data. Just turn it off and try again.
[G2 Android Development] RenderBroken:
I have no idea what happen. Don't think it was my kernel or it would happen to more people and so far you are the only to complain of this issue. Very glad to hear they seem to be going away!

If you all would like to discuss kernel building in thread, I would be happy to help where I can. The way to deal with multiple sources is to:

Setup build environment

Setup Github account

Fork compatible kernel

Clone repo to local computer

Then just cherry-pick the commits you want to add

Of course this is EXTREMELY watered down but I could go into greater detail later. This is a learning thread so what better to learn about here than Kernel Development!
[G2 Android Development] simon_lefisch:
Man, now I'm getting interested. I've always wanted to learn how to build ROMs/kernels. I might have to get in on this.....
[G2 Android Development] drkow19:
You plug the phone into a computer, then go to Settings -> Storage, and there should appear a menu button. Under that menu, it is USB Connection Type or something. The menu only appears when the phone is plugged into a computer.
[G2 Android Development] Raagh:
Thanks men this seems amazing. I already setup the enviroment, on tuesday when i get home i ll follow this steps. I saw the ones of github and fork and clon to local in a guide of rom porting, i ll shared it here when i get home, im on vacations till tuesday
[G2 Android Development] RenderBroken:
YES, welcome to the dark side! lol

I have alot of free time this weekend so tomorrow I will go into more detail on the steps to take. The one that took me FOREVER to do right or find and RELEVANT info was on git cherry-pick. I will write up easy to use steps and place them in OP#3.
[G2 Android Development] Raagh:
Great men, can wait to read it. Yeah that steps is the one i simply have no idea ahaha.**** now i cant stop thinking about this, need to enjoy my vacations somehow ahaha
[G2 Android Development] MaluNoPeleke:
You can take a look at the XDA university: http://xda-university.com/as-a-developer/getting-started-building-a-kernel-from-source
[G2 Android Development] fix-this!:
So im guessing no v4 this weekend?
[G2 Android Development] Lawlrus:
He said Saturday a few pages back.

Sent from my Vs980 running SlimKat 7.0
[G2 Android Development] simon_lefisch:
Saturday isn't over yet.....
[G2 Android Development] Matze060906:
Hope for that, because new Mahdi is coming today... [emoji2]
[G2 Android Development] RenderBroken:
Is it? Good. I found that the new pocket detection crap is causing alot of issue for his and my kernel. That's the cause for having to hit the power button more than once and why DT2W isnt working either. I wasted a whole day trying to track down the issue and remembered that they had added this new change. I flashed an older build of Mahdi and it worked fine. . .fml lol

Also it is still 3:30p CST here so I have some time left! I am working on the last pieces now.
[G2 Android Development] Lawlrus:
Take your time. It will come when its good and ready.

Thanks for your continued development!

Sent from my VS980 4G
[G2 Android Development] RenderBroken:
Almost done. This will be a pretty massive update. I will list the changes shortly.
[G2 Android Development] Saythis:
Are you also releasing a CM CAF variant or will that come later? Either way, awesome job! :good:
[G2 Android Development] RenderBroken:
Later but I have already reached out to others that may be able to help. I want to find the best way to merger in their blobs instead of having to build two separate kernels. Kinda like I can use the same source for Stock LG and AOSP but just using "CONFIG_AOSP=y" in the defconfigs when wanting to build for AOSP. I would love to setup a way for doing something similar for CM CAF but I am not sure its possible.
[G2 Android Development] RenderBroken:
Building now. . .

I still have more I want to add but its a good stopping point. I will let others try it out and report back. This will give me time to merge in the rest I wanted to.
[G2 Android Development] RenderBroken:
Uploading now . . .

Falcon_Hotplug Updated!

Scheduler Optimizations (WAY more to come!)

LZ4 Optimizations

Generic Idle

Workqueue Optimizations

Out of Memory (OOM) Optimizations

CPUFREQ Optimizations

Kernel Mode Neon

Debugging Sysfs added to Powersuspend: Now you can see what its doing in real time! Thanks Dori.

Quick Wakeup:

This driver allows clients to register code to be called upon wakeup

so that clients can perform specific checks and vote to drop the system

back into suspend without fully resuming if the wake reason was a special

quick wakeup event.
[G2 Android Development] Raagh:
Already flashed, ll report. Amazing work thanks
[G2 Android Development] blacklight1025:
Loving the update! No hiccups when unlocking anymore!
[G2 Android Development] Matze060906:
Just downloaded and waiting for new Mahdi before flashing. Is the issue with the paid apps fixed?
[G2 Android Development] quang61:
Did you fixed the sdcard for the arm f320 ?
[G2 Android Development] Rick O:
Is this happening in R4? (Not listed in latest additions)

Thanks
[G2 Android Development] Matze060906:
Has anyone tested R4 with the newest Mahdi build?
[G2 Android Development] Saythis:
Running smooth here.
[G2 Android Development] Matze060906:
Which device do you have?
[G2 Android Development] Saythis:
VS980
[G2 Android Development] Matze060906:
Ok, thanks. Hope it runs great on d802 too. I'll flash rom and kernel today...
[G2 Android Development] MaluNoPeleke:
I lost all my paid apps coming from Mahdi 08/09 on a D802.

Very annoying. I will send a log to [MENTION=5438598]RenderBroken[/MENTION] via PM
[G2 Android Development] ThatKidDrew:
R4 running fine on latest AICP (08/09)

VS980 running AICP 4.4.4
[G2 Android Development] hamisgood:
R4 still breaks SD cards for the F320 line sadly.. Was hoping for a skip free Mahdi ROM
[G2 Android Development] RenderBroken:
Thanks, I will be looking at it shortly. R5 is right around the corning. I have way more I plan on adding but just didnt have the time to merge it all yesterday. Thanks for your help and I am sorry it is giving you a hard time.

My source for mounting SD cards is the same as everyone else's. Can you tell me which kernel it works on?
[G2 Android Development] RenderBroken:
I believe I found the issue. Would you be willing to test?
[G2 Android Development] RenderBroken:
Also should fix the SD card issue.

I had checked my ramdisk awhile back and thought I compared every file and must have missed 2 lines of code. I will try to merge in what i wanted to last night since it seems the kernel is running smoothly. I don't put alot of stock into benchmarks but R3 to R4 is about 6000 points better. But it will bench lower than it seems it should. This is because my hotplug driver is not stupid and doesn't just online all 4 cores all the time like:

QCOM MPDecision

Intelliplug

These are not bad hotplug drivers but they are VERY different from what I use. I don't need 3000 lines of code to hotplug, just 500. So when you benchmark, the stock kernel (MPDecision), will online all 4 cores while testing. Mine will online maybe 3 but most of it will just be 2 online. For an example, Open trickster or whatever you use to see the cores online or not. Have it open and then bring down the notification shade. Do it realy fast, over and over. You will hardly ever get more than 2 cores online. Now use a kernel that has a different hotplug and you will see when you bring down the shade once, it will online all 4 cores or at least 3. The object is to work smarter, not harder.
[G2 Android Development] RenderBroken:
Holy Crap!

Also should fix losing Radio (Bug) when directly flashing my kernel over Mahdi.
[G2 Android Development] Matze060906:
The perfect kernel is near? [emoji2]
[G2 Android Development] MaluNoPeleke:
Yeah, I could do that, no problem. Just send it to me via PM
[G2 Android Development] hamisgood:
SD card works on the default bundled Kernel with Mahdi and TeamEOS ROMs. I have no idea how to extract the Kernels from the ROM but I shall link the ROMs, hopefully it may lessen your trouble

Team EOS: http://xdaforums.com/showthread.php?t=2769042

Mahdi: http://xdaforums.com/showthread.php?t=2590700
[G2 Android Development] fix-this!:
already had a lockup, restart about 2hrs after installing v4. really hoping we can resolve these. otherwise it is running smooth on aicp.
[G2 Android Development] RenderBroken:
Does this only happen with my kernel? Does it happen when you doing a specific task? The only time I get a lockup/reboot is when I have low LTE signal.

It has to be something specific to your phone or something like that. It just doesn't play nice with you. I wish others had this problem like you do so I can find a common thread. What are you doing during these lockups?
[G2 Android Development] RenderBroken:
What is your phone model?
[G2 Android Development] kewkie:
Missing knock on or when its working its having a high delay (like 10 seconds?) on latest mahdi with R4 (clean flash)