yashsingh1/xdaforums huggingface dataset:
[G2 Android Development] ZeNiXxX:
I never Play games on smartphones.Are you on 29.7 mahdi build? I get about 4 hours screen on Time.

Gesendet von meinem LG-G2 mit Tapatalk
[G2 Android Development] RenderBroken:
This is not a retort, but why does everyone seems so blown away getting more than 5 hours SoT. I am new to G2 and have only really used my own kernel in depth. Is this the same results regardless of Stock and AOSP kernels? Is this your experience? Thanks.
[G2 Android Development] ThatKidDrew:
I don't game and I'm lucky to get over 4 hours of SOT.. Always wondered what the secret was ?

VS980 running AICP 4.4.4
[G2 Android Development] phoenix_rizzen:
Personally, I only managed to get around 3-4 hours SoT using the stock LG ROM (4.2). Granted, I only had stock on my phone for about a week. :)

SlimKat (JB kernel) got me a consistent 4-5 hours SoT.

But Mahdi (4.4 kernel) was what unleashed the power of my phone. Consistently get 6 hours SoT everyday with the stock kernel. And cracked 7 hours SoT several times using RenderKernel. While reading eBooks, just about topped 8 hours a few times (Mahdi kernel and RenderKernel).

Tested Vanir for a week, but couldn't get it over 6 hours (Dorimanx 5 kernel, Dori 6 wasn't stable on my phone). Really like the support for the hardware step counter, though. Really miss that with Mahdi.

Same apps installed (from stock LG through all custom ROMs), same usage patterns (Gmail, e-mail, Facebook, Tapatalk, gReader Pro, lots of surfing using Chrome, Hangouts, Messenger, Google Play Music, Podcaster Pro, Endomondo Pro while walking). JuiceDefender Plus managing cell and wireless radios (radios off when screen off unless active download in progress; turn radios on every 30 minutes for syncing; prefer wifi). Lux Lite managing screen brightness (use Night mode a lot for reading).

The only time I get less than 5 hours SoT is when I play games for over an hour, or when I disabled JuiceDefender for testing.

The only settings I change in Trickster are the CPU governor (usually interactive, sometimes ondemand), the min CPU freq (422 MHz), the I/O scheduler (usually row, sometimes deadline), the I/O readahead (1024 KB), and the TCP congestion control (Westwood). Everything else is left at whatever the kernel dev chose.
[G2 Android Development] Lawlrus:
YMMV is the only explanation, I use about ten or so apps on my phone and I've never had an issue getting 5+ hours sot.

KitKat is worse for battery life then what jellybean was, but its not that big of a deal. I used to get 7+ hours on jellybean.

People install 150 apps that synch data and always have GPS on then wonder why they have terrible sot.

Also could factor in that not all phones, mobos, chipsets are the same, and areas with low to no signal effect it, its not a reliable representation.

Sent from my Vs980 running SlimKat 4.4.4
[G2 Android Development] RenderBroken:
Thanks for the great info! Why do you bump up Min Freq? Do you need to for music listening? I don't need to but I use the D800, which do you use?
[G2 Android Development] jeff5347:
Render, I think when I got my g2.. Loaded pics and all media from my toro and added all my apps ( minus apps for themes, kernel control, custom ROM control ) I would average at least 6-7 hrs. I've gotten close to 9 hrs and that's with medium usage. I usually use WiFi 90% of the time. If I can get 5-6 sot with custom ROM, kernels ect I'm happy. I have a charger so sot isn't the end all b all for me. Great kernel Render can't wait for R4
[G2 Android Development] RenderBroken:
Yea, I have to agree with you. Its a rare day I forget to put my phone on the charger before going to bed. So I really just need to get to that point but I did forget putting my phone on the charger the first time in years and its was refreshing to wake up and still have 40% left. Once again let me say that I came from an Captive > S2 > Moto G > G2. So I have seen the crazy range of battery life.
[G2 Android Development] Draygon:
Is knock off working with render kernel v3?

It doesn't seem to work for me, I'm using Slimkat 6.8. The users in the Slimkat forum tell me knock off is working there at default.
[G2 Android Development] russells.android:
Slimkat 6.8 with v3 kernel here. Knock off on status works for me.
[G2 Android Development] fix-this!:
Any word on v4 render? Hopefully we can get the random reboots elminated.
[G2 Android Development] russells.android:
V3 is just fine with me. What reboots are you talking about?
[G2 Android Development] NEO2598:
Does this kernel work with PA?
[G2 Android Development] Lawlrus:
It shouldn't.

Although it shouldn't work on cm based Roms, and people have reported it working on some Roms.

Make a backup and try

Sent from my Vs980 running Mahdi 4.4.4
[G2 Android Development] simon_lefisch:
No reboots for me on Mahdi 7/18 and 7/29 builds with R3. Been using it since its release.
[G2 Android Development] Matze060906:
I've flashed latest Mahdi build yesterday and now renders kernel r3. After flashing I wiped dalvik and cache and reboot the phone. After start I got FC on calender storage. I rebooted again and all is fine. Have anyone this issue too?
[G2 Android Development] jeff5347:
Yea some phones no matter how u try can't get good sot. Anyone that has used a toro knows. My wife's g pro all stock eats battery like a fat kid and candy. With WiFi it will drop 10% in 10-15 minutes. Horrible. I'm using r3 with carbon and its great. Super smooth and sot usually hits 5+ unless I'm gaming. I'm hooked on dino hunters and damn that games drills the battery temp wise...150- 163 f°. Haven't had any melt downs or reboots when up that high.
[G2 Android Development] RenderBroken:
I am getting close to releasing. Knocking out a buw minor issues I am getting from my test build. I will usaully keep a branch for testing. I am going to try and keep the habit of noting which release. For example I have a test branch that starts with "r4" here:

https://github.com/RenderBroken/render_kernel_msm8974/tree/kk-test-r4-remote-cpufreq-commits

I will try to keep my branches up to date while testing so others can see wat progress is being made. I did add something that may be cool:

https://github.com/RenderBroken/render_kernel_msm8974/commit/346667047cd13a9ac29e1601cd85bc07ca050a2b

power: quickwakeup: initial driver

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.

What this means is when your phone needs to "check in" via cell signal to report location and such it would not need to come fully out of deep sleep and when done with the minor operation it would go right back down. This is just 1 example. There are numerous cases where this could help.

To me it does seem to help but could be plocebo. Need a larger test pool (You guys ;). Also it seems like I have to hit the power button twice sometimes to turn on. May need to make adjustments before final release. I did notice a bug in R3 that deals with the other cores that I should have squashed completely in R4. That should fix the reason for your last reported reboot.
[G2 Android Development] MaluNoPeleke:
Sounds great! Were you also able to fix the removed paid apps problem?
[G2 Android Development] RenderBroken:
Unfortunately not yet, or at least not verified. This and the SD Card not mounting are the main reasons I have not released R4 yet. I love this test build though.

If you are up for it, I would love for someone to get me a log (using syslog) of their phone right after the lose the apps and or another one for a f320x user right after bootup when an sd card wont mount. Do I have any takers?

Thanks Gents and maybe some gals!
[G2 Android Development] Lawlrus:
I installed your kernel on the newest Mahdi, but it didn't mess with my paid apps.

I still got a syslog if you want it though, got it right after reboot

Sent from my Vs980 running Mahdi 4.4.4
[G2 Android Development] RenderBroken:
Did you have the paid apps installed while on stock kernel or mine? Thanks for your help always :)
[G2 Android Development] Lawlrus:
I was on stock kernel with the paid apps and flashed your kernel.

One thing that was different from the last times I've done it, is I'm currently on dalvek while I'm normally on art.

Think that may play a part in it?
[G2 Android Development] RenderBroken:
Its possible, but I don't know how or where. Just the fact that its so hit or miss now . . .lol But really thanks for being so helpful to the community. Its matters and is appreciated. I will keep your finding in mind.
[G2 Android Development] bleached45:
When I dirty flashed the 7/29 mahdi over 7/18 I let it boot to be sure to get a signal, then flashed R3 again and didn't lose any paid apps. Maybe because I had Render Kernel previously without a full wipe?

---------- Post added at 04:34 AM ---------- Previous post was at 04:27 AM ----------

I'm not the user you asked about this, but I also have the D800 and use it for music a lot. On Mahdi 7/29.

I also bumped up the min frequency to 422. Sadly, I still get some audio issues with screen off. But I noticed the voltages (at least, those displayed in trickster) are the same for 300 and 422. So wouldn't it be better to run with 422 min if it uses the same power (assuming that is how it works) and runs a little faster. It also has the potential to run a light task without ramping up like 300mhz might have had to do. And it removes a step for when it does have to ramp up, possibly removing lag?

Please correct me if I am wrong. This was my rather uneducated reasoning.
[G2 Android Development] gobonja:
Has anybody got sweep2wake working?

sweep2sleep works but sweep2wake doesn't. I tried this with Mahdi and Vanir rom. Other than that everything runs great.
[G2 Android Development] NEO2598:
This kernel flashes LG logo boot animation?
[G2 Android Development] RenderBroken:
Both are interesting points. I did not notice the voltage was the same. Not sure if 422MHz messes with deep sleep and the suspend cycle though. I know with the Moto G (I know they are different SoC's before someone tells me lol) there were a couple references to what MHz to "power_collapse" I have not personally seen that in our code though. If so I could change it possible. But it is kinda cool to think we could just drop 300MHz. Thanks for the idea!
[G2 Android Development] Matze060906:
I had lost the paid apps with the R2, not with the R3, but if you need a tester for D802, I can do this.
[G2 Android Development] metalboy94:
The audio issue everyone is talking about is most obvious (imo) with PowerAmp and its DSP. I can partly control it by setting large audio buffers in PowerAmp and tweaking interactive subtly. The sound quality makes it worth it though.

Btw, can you somehow reduce the battery drain of the radio when data is on? I'd rather not use JuiceDefender and just keep my data on at all times when I'm out, and for that reason I rarely top 4 hours SoT (auto brightness, very light gaming, FB/Messenger, Reddit etc)
[G2 Android Development] RenderBroken:
Cool, If you want to take the time to test it again let me know!

Ok I see what you mean. As for reducing power draw while data is on, I have no idea or have ever seen anything that could really make a difference. Note that I am always on the lookout for battery savings.
[G2 Android Development] metalboy94:
Well, thanks anyway for your work - underclocking to 192 Mhz partly goes towards my goal. :D
[G2 Android Development] Matze060906:
Got a reboot this minute with R3 and latest Mahdi, but I have no syslog. I have to reinstall it. I can test again if you want...
[G2 Android Development] Lawlrus:
[MENTION=5438598]RenderBroken[/MENTION]

Since flashing R3 on the 7-29 Mahdi, I'm having that issue you said you had in R4 of needing to hit the power button twice to turn the phone on. Knock on works flawlessly though.

Also I'm getting ridiculous battery on the new Mahdi with R3 as well

Can't wait for R4

---------- Post added at 02:08 PM ---------- Previous post was at 01:34 PM ----------

Logs are ways wanted.
[G2 Android Development] Matze060906:
[MENTION=5438598]RenderBroken[/MENTION]: Here's the log. Hope it helps...
[G2 Android Development] DominikHolecek:
AFAIK PA definitely isn't based on CM. Therefore I don't see any other reason why it shouldn't work...
[G2 Android Development] Lawlrus:
Because houstonn uses his own variation of caf that no one else does.

At this time there are three varients being used.

One for pa

One for cm

And one for aosp, as in anything not pa or cm, even though both are classified as such.
[G2 Android Development] fix-this!:
Out of all the roms i tried aicp works flawless with this kernel. Smooth as silk. No reboot yet on the newest nightly. Hope to see v4 soon. The g2 is becoming my favorite device.
[G2 Android Development] bleached45:
Haha, even hampered by stock ROMs the G2 was something to be messed with. I think the G2 has that effect on many (besides the poor souls with the perm screen damage).
[G2 Android Development] fix-this!:
No lcd issues here. Btw im in west michigan.
[G2 Android Development] NisseGurra:
Some info on the external sd card issue for the f320 users.

If the storage_list.xml file in framwork-res.apk dont include these lines the Sd-card will not be visible:

<?xml version="1.0" encoding="utf-8"?>

<StorageList

xmlns:android="http://schemas.android.com/apk/res/android">

<storage android:mountPoint="/storage/sdcard0" android:storageDescription="@string/gpsNotifTicker" android:primary="true" android:emulated="true" android:mtpReserve="100" />

<storage android:mountPoint="/storage/sdcard1" android:storageDescription="@string/gpsNotifTitle" android:primary="false" android:removable="true" android:allowMassStorage="true" />

<storage android:mountPoint="/storage/usb" android:storageDescription="@string/gpsNotifMessage" android:primary="false" android:removable="true" />

</StorageList>

I attach an modded storage_list.xml, place this xml-file in framework-res.apk/res/xml/

(rename the file to storage_list.xml)
[G2 Android Development] RenderBroken:
So is this a kernel or rom issue? I have not heard of this while doing any kernel work but it could just be something I am not familiar with. Any idea how to fix it permanently? Thanks for dropping some solid info on this thread!
[G2 Android Development] kewkie:
Hey, some guys might use this kernel with mahdi (so like me) and I made a little script which was originally made for aicp, but is working for mahdi too. This is for double tap to wake which is mostly not working proberly but with this script its working. Download smanager from playstore, open this script and set on boot and as root.

Download: https://www.dropbox.com/s/qb4kytq7l9ohq53/knock_on_aicp.sh
[G2 Android Development] NisseGurra:
Its an rom issue, the xml need to be correct. I will try your kernel on my homemade omni for 320K and see if the Sd-card is mounted correctly
[G2 Android Development] chrisexv6:
can we just add the contents of this script to one of the init.rc files already on our phones? I'm not sure which (if any) get run at boot time though.
[G2 Android Development] RenderBroken:
Not really. I could give a pretty changeling but that is just more unnecessary work when you can just look at my source and commit history. I will however add easy to use links to access those. I meant to do that today but will have to add it tomorrow.

I am glad you are happy!

I had also forgotten to mention or announce that I had also made it so you don't need to flash a panel variant kernel. You just flash the one for your phone model! Thanks to [MENTION=5232783]dr87[/MENTION] for providing the script.
[G2 Android Development] r_dub:
No love for VS980 with the new release?
[G2 Android Development] RenderBroken:
It's probably still just uploading.
[G2 Android Development] RenderBroken:
Because I said I would have a build for everyone, I jumped back on the putter to see why it didnt upload. Must have had an internet issue or something (Remote Build Machine) so I re-uploaded it. Should not take long. Enjoy!
[G2 Android Development] RenderBroken:
Man, I don't know why it's not uploading. I may have to completely rebuild the kernel or something if it doesn't upload. Sorry. If not I will do so in the morning. About 1am here.
[G2 Android Development] 1ceb0x:
flashed and booted fine. it is even smoother than the first test version!

Thank you so much, Zach!
[G2 Android Development] reas0n:
http://xdaforums.com/devdb/project/?id=4830#featureRequests It's here, I thought You had seen it :p anyway it's about the EcoMode which for example Savoca's kernel had, it allows to use max two cores, not 4
[G2 Android Development] 1ceb0x:
as render said, if you use stock settings (interactive) you have 2 cores on all the time. i have monitored the cpu load closely since i moved to this kernel and it rarely fires core 3 (depending if your usage is heavy). for browsing and stuff, the cpu sits on 2 cores and it actually scales them properly - not let them stuck at 2.3 ghz all the time. I spoke with Render about this and he said he needs to implement intelli hotplug in order to have eco mode (if i am not mixing my memories right now) and that he preffers his implementation which frankly is great imo! just give it a try :).
[G2 Android Development] undeadking:
Didn't flash so well... Used little kernel flasher to flash and after rebooting system I got a constant "phone process has stopped" was finally able to reboot into recovery and wipe dalvik/cache, same thing after so i factory reset into recovery and flash beanstalk 4.4.4 (deliberate build) and reboot and I got the black lines FML!!! This is my 4th G2 in the past month ? flashed C-Rom 7.1 and finally got things working again... Looks like im heading to Verizon on Saturday for a warranty swap ?
[G2 Android Development] SeVIIn:
Running great on my D801, using interactive/row though I'm not sure if that's the best combination yet, but it seems to be pretty awesome so far.
[G2 Android Development] jesssiii:
Thanks for sharing your work! Looking forward to the Verizon version.
[G2 Android Development] Raagh:
Underclock to 96 mhz still in kernel

Sent from my D806
[G2 Android Development] ecsnead69:
Link is broken......
[G2 Android Development] chrisexv6:
Any R1 love for VS980 ?
[G2 Android Development] russells.android:
Read the previous page. There is the answer to your question.
[G2 Android Development] chrisexv6:
Oops! Sorry about that.
[G2 Android Development] jeff5347:
Has anyone lost sound on the latest release. I'm on the d800 and have no sound for notifications, music, youtube , ect. Maybe I got a bad download
[G2 Android Development] Raagh:
No problems with sound here sorry, been listening music on my way to work :)

Sent from my D806
[G2 Android Development] musashihatred:
[MENTION=5438598]RenderBroken[/MENTION]

Got A random reboot after that, few seconds SOD.

generated a log :D
[G2 Android Development] Raagh:
Re you using intellidemand or multicore power saving?

Sent from my D806
[G2 Android Development] kewkie:
Im not sure, but i think it SHOULD work. I use it with this way to be sure its working as i want
[G2 Android Development] chrisexv6:
Added the line to init.aicp.rc (running 8/1 nightly of AICP 5), rebooted into recovery and flashed Render kernel.

Double tap to wake/sleep works right now, will keep an eye on it (Ive noticed sometimes it works for a bit then eventually stops)
[G2 Android Development] RenderBroken:
I can just add the line to my script that I have already. Thanks for the info!

I would be grateful because I have checked everything I can think of against kernels that it is supposed to "work" on and there is no difference. So it would be cool to find out that its Rom related instead. Thanks!
[G2 Android Development] simon_lefisch:
Double tap to wake works fine for me with latest Mahdi (vs980).
[G2 Android Development] NisseGurra:
Hmm, works on my omniport but not on mahdi. Seems there some more dependencies somewhere. I will try to find it.
[G2 Android Development] RenderBroken:
I know on the newest Mahdi you have to enable the dt2w feature for it to work right. Just throwing that out there.
[G2 Android Development] bleached45:
I believe they were talking about SD support.
[G2 Android Development] RenderBroken:
You right lol . . .
[G2 Android Development] bgx:
Hey RenderBroken!

Would like to use RenderKernel again! But with R3 I've had reboots. I know no ask for etas but I can't see a change in the github and would love to use R4. You said you have fixed the reboots. I must be patient and wait till you release it. In the mean time I stay on dr kernel!

Keep up the good work!
[G2 Android Development] RenderBroken:
What was your setup? R3 has been pretty solid for everyone except the same modem resets that plague every phone no matter the kernel.

Do you have any logs still? R4 should be more stable though. I noticed a bug with the CPU and have fixed it. That may have been the cause for your issue.
[G2 Android Development] bgx:
You find two logs from me in this thread! Now I install R3 again and made log again if you need!

With Dr kernel I don't have reboots and I think you said that you found the coupit whats the reason for the reboots or have I missed something?

Setup was the latest mahdi and your kernel with stock settings!
[G2 Android Development] RenderBroken:
Then I will dig for your logs. I had found that core 2 and 3 seem to have a hard time kicking on. This was fixed in r4
[G2 Android Development] Matze060906:
Hope you will release it soon, can't wait. Thanks for your great work... [emoji106]
[G2 Android Development] bgx:
Thx! Have installed R3 again!
[G2 Android Development] RenderBroken:
VERY soon actually. Since I don't think the SD card issue for the f320x models phones is really on my end. This was high on my "Get This S*** Fixed List" btw. Still if there is something I can do to make it better I will go for it. I am pretty happy where its at now but will probably throw in more goodness first.
[G2 Android Development] musashihatred:
btw, im not really someone who can speak about it (SDCard) but i read that it's related to something called fstab. i also often see it on phones that has sdcard slot. And from what i remember, the fix on G2's SDcard slot was from the HTCs m8's (or m7?) fstab file. or sort :confused:
[G2 Android Development] bgx:
Ok, next reboot. Here's log.
[G2 Android Development] RenderBroken:
hmm, yea it really does not like you huh? I will look at the log shortly.
[G2 Android Development] RenderBroken:
I will also be adding in FM Radio Support in R4. I dont believe it will work with EVER FM Radio app under the sun and will only work with Spirit Radio. The Dev for Spirit FM Radio took the time to mirror my source and create the exact patches needed. So I will go ahead and add it in since he did most of the work to incorporate it. Just fyi.
[G2 Android Development] Raagh:
Hey [MENTION=5438598]RenderBroken[/MENTION] i wanna say congrats on how the kernel is going on. I had reboots on previous builds and allthough they re still present, they re alot less frequent. One in 2 days or sth like that. Your kernel is getting better and much more stable with every release :), keep up the good work
[G2 Android Development] fix-this!:
No reboots yet. Awaiting v4.
[G2 Android Development] ckyy:
Apps are freezing sometimes in mahdi. However it happens in the provided kernel aswell so i guess it's not related to r3? Anyway, is there any optimal gov/sched setting for the best performance/battery life combo?

There's too many to choose from.
[G2 Android Development] Raagh:
Hey [MENTION=5438598]RenderBroken[/MENTION] today i decided start on the android world. Im gonna start building mahdi from source using dr87 sources and your kernel instead of simplekernel, just to learn, maybe then change some apps ,dpi and settings menu, all Before building. I had build roms from source before but never a rom with a diferent kernel. Do you mind help me if i had any issues? Thanks in advance

Edit: i m setting up my VM with ubuntu and the build enviroment right now