yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Original Android Development] dark_ente:
Unfortunately i can't stay work with this kernel for long because of no gamma control

Gotta go back to faux for now, hopefully you will implement full gamma control soon, because i really like your kernel

Sent from my Nexus 4
[Nexus 4 Original Android Development] motoxxxx:
I'm on b57, if I want to flash exp. 10. Do I need to reset the kernel?
[Nexus 4 Original Android Development] bongostl:
Just to clarify for people about when they have to flash a reset kernel, restore a backup,etc:

Franco uses a custom ramdisk as a part of his kernel.this ramdisk won't work properly with other kernels, which results in your phone not booting.

To get around this, what you need to do is somehow restore the default ramdisk for your rom.

Faux's reset kernel restores the STOCK ramdisk and kernel. If you are on stock, flashing this should solve your problems.

If you are on a non stock Rom, just flash your rom again(and your gapps).this will restore your rom's ramdisk.then flash the kernel of your choosing.

With ALMOST any other kernel, you don't need to do this, as most kernels don't mess with the ramdisk.

I hope this clarifies things for people!
[Nexus 4 Original Android Development] tengen:
For those of you on exp10 - do you notice a significant improvement in battery life and/or performance compared to mainline build 57? I ask because I'm currently on mainline (loving it) and wondering if switching to exp10 is worth it.
[Nexus 4 Original Android Development] consolidate42:
Bear in mind that battery extrapolations are iffy, but I'm getting 4 hours of screen time @ 50% battery. I will see if this equals 8hr screen time on a full drain.

Autobrightness, wifi, mostly browsing with some n64 emu gaming.
[Nexus 4 Original Android Development] AmeriKan47:
Today was my second day using exp10 on cfx and I hit five hours of screen time. My total battery time was over 15h30m. I haven't tried build 57, but I can vouch for exp10.

As far as performance goes, I have no complaints. I get the lockscreen lag occasionally but I have no other issues. How does build 57 treat you?
[Nexus 4 Original Android Development] popophobia:
That's unreal! Did you have a SIM card in at all?
[Nexus 4 Original Android Development] dark_ente:
5 hours is fairly normal, if you use low brightness, use wifi, undervolt and underclocm CPU

Sent from my Nexus 4
[Nexus 4 Original Android Development] whittikins:
It looks like the default interactive settings for b10 are 80% it goes to high speed of 1500. This obviously makes it super fast, but has anyone tried something like high speed of 1026 instead to compare speed and battery life? I'm gonna give it a shot. These settings are the reason we see so much time at 1500mhz and much less in middle frequencies. I'm not saying this is a bad thing, but I'll see how 1026 goes and if the battery is any better during use.
[Nexus 4 Original Android Development] mobilehavoc:
I never understood people who under clock their phones? Are you really that hard pressed to plug in your phone once in a while and enjoy the full power of the Snapdragon Pro. Next time just buy a budget phone their batteries last forever. :rolleyes:
[Nexus 4 Original Android Development] samwebbo1990:
Should I use ondemand or the tweaked interactive for better battery life? BTW I always underclock to 1134 if that makes any difference? :)
[Nexus 4 Original Android Development] sk3201:
5 OK, but not 8 as someone posted before.....

Gesendet von meinem Nexus 4 mit Tapatalk 2
[Nexus 4 Original Android Development] jhericurls:
Some people like me don't have chance to charge it during at least a 8 hour period. But still use the phone for email, GPS, music etc. So what's the point of running at 1500Mhz when your not going to notice the difference at 1140Mhz, yet its drinking more juice.
[Nexus 4 Original Android Development] AmeriKan47:
I use it as a phone. Calls, texting, surfing, and played games. It is on WiFi only (when I'm at home). I use the stock kernel settings and auto brightness.

In the month that I have had my phone, this was my best day yet. I've previously used Franco and faux's kernels, but I'm sticking with motley for the time being.
[Nexus 4 Original Android Development] flipim:
exp10 its Underclocked Kernel? or it has a lower performance than previous versions?
[Nexus 4 Original Android Development] _motley:
Experiment build 12 posted

Hi everyone, experimental build 12 has now been posted. Sorry for the long wait. Glad to hear that b10 is going well. Thanks for all the feedback.

For b12, please use the interactive gov for the best experience. Let me know how you like it. My aim is to make an even smoother UI experience and continue to improve the ability to tune under the covers (if you want to). After this build, I am hoping to bring over others from mainline that haven't tried the exp builds yet. I think this should complete everything needed to convince people on exp if they haven't been yet. I myself won't go back to mainline because exp is better IMHO...we have much more control over things and performance and UI experience should be similar.

For those that like to tweak and experiment, if you haven't looked at post 2 before, there are already many tuning parameters you can choose from (thermal temp, autoplug etc.). b12 improves upon this, so keep an eye on post #2 as I will updating it soon to reflect the latest release notes and tuning parameters.

To answer flipim's question above, no the exp builds are not underclocked, performance should be compatible. But, you can underclock if you want.
[Nexus 4 Original Android Development] :
Thanks! One question though. If the builds are not underclocked then why can i underclock by 175 on faux and only 62,5 here?

My cpu is "fast".

Also: are the additional parameters in your interactive governor explained somewhere?
[Nexus 4 Original Android Development] consolidate42:
I think you're talking about undervolting - underclocking refers to lowering cpu frequencies. the reason you can't seemingly undervolt as much on motley's is because he already has a built in UV while faux's doesn't.
[Nexus 4 Original Android Development] :
Omg i totally mixed that up. Normally i'm less retarded, ty :D
[Nexus 4 Original Android Development] consolidate42:
Trying out the new build now.

Is there a way to turn off input boost altogether in b12?
[Nexus 4 Original Android Development] _motley:
Two things we can do:

Tune it down a bit using the parameters. Please give it a try and see how it works;)

I can provide an "inert" PowerHAL add-on that will just leave it alone (I will provide a zip later today, it will also be better for OnDemand users etc).

I figured this question would come up. Google does this in all JB builds in some fashion or another. It does make the user experience a bit better, however the implementation in the stock kernel N4 was not very good since they built it around the proprietary mpdecision. This implementation is much closer to how it is done on the N7 and Galaxy Nexus. Most like it in those implementations.
[Nexus 4 Original Android Development] Simer03:
I'm gonna do a 3G only test today with exp12 and rasbean stock settings with UV of -32.5! Post back later tonight with results!

Sent from my Google Nexus 4
[Nexus 4 Original Android Development] tengen:
Made the jump from mainline to exp12 :) Had a few questions though:

1. In TricksterMOD's interactive governor control panel, the toggle switch for boost is turned off - what exactly does that do, if anything? The phone still seems to be ramping up the CPU on touch (I think).

2. The "boost" frequency in this build is set to 1296mhz - is this the same as the previous exp builds, or has it been increased? In mainline I believe it was 1026mhz?

Thanks for your great work, motley!
[Nexus 4 Original Android Development] lazer155:
If i am upgrading from b10 to b12, do I have to reinstall my CM 10.1 rom so the kernel is fresh?
[Nexus 4 Original Android Development] consolidate42:
Setting boost duration to 10ms seems to be working , but I'll be looking forward to trying out neutered PowerHal add-on.

The reason I ask is because whatever tweaks you made to interactive in b10(with input boost disabled in Trickster) had already made screen interaction so responsive that I don't think I needed to override the load/frequency curve with input boost.

For browsing webpages (i.e. period screen touches) input boost is fine, but when I'm gaming or using any program that requires constant screen interaction, I'd rather not have the cpu locked into the hispeed_freq value when it can afford to sit somewhere lower.
[Nexus 4 Original Android Development] dwang:
b12 nice and fast.

Just got a spontaneous reboot however.

Here is the last_kmsg

settings are default, never had a reboot with b10.
[Nexus 4 Original Android Development] bamsbamx:
Motley, is there any way to prevent dalvikvm logs from appearing in logcat... I think this should make performance better yet...

Thanks for exp b12, going to try it ;)
[Nexus 4 Original Android Development] air2k57:
Just installed b12, loved b10. However, last day switched to matrix to see how 5.0 was and it was rather fast. So far, with b12, I see that all frequencies are being used, unlike in matrix. So far so good.
[Nexus 4 Original Android Development] popophobia:
I also had two spontaneous reboots on b12

http://db.tt/kxzrvR4Q

http://db.tt/9dvS0Fel
[Nexus 4 Original Android Development] _motley:
No, if you are coming from this kernel you should be fine to just flash b12. If you were coming from another kernel, I would dirty flash your CM 10.1 ROM.

It looks like a thermal event to me, but I don't yet understand all the details. It was throttling ramping frequency down and then ramping it back up. The interactive governor had a problem in the middle and it gave me the line number where the fault occurred, so that is good. I'll look things over later and see if I can figure anything out.

Please give a little more info about what you were doing to cause the throttling event. Did you play a game, run benchmarks, etc.? Also, which ROM are you using? Thx!

Those logs are an Andorid OS thing:( Let me know how it goes with b12!
[Nexus 4 Original Android Development] JmPTaz09:
B12 feels nice :thumbup: smooth, fast, buttery, all that good stuff ;)
[Nexus 4 Original Android Development] dwang:
Using paul obriens ROM.

Reboot happened at home screen. Prior to that was using tapa talk, browser, and YouTube.

Didn't play any games.
[Nexus 4 Original Android Development] ragiut1:
Which is better for battery life in b12, Ondemand or interactive? Also does underclocking the GPU helps battery life? really care about battery life :)

@OP

Best Kernel i used, many thnx for your great work
[Nexus 4 Original Android Development] rlaw:
codefireX ROM has an option in settings to disable logging.
[Nexus 4 Original Android Development] _motley:
Thanks, one those logs is from another device, but the other is helpful.

It's pretty early to tell on b12 since it was just released. If you want the best battery, you should consider underclocking the CPU a bit and play with a little more UV if your device will tolerate it. I run at 1050mV @1.5 and step down to 700mV @ 304MHz. I have a "nominal" chip and it works great. If you use interactive, you may want to bump down the boostpulse duration a bit.

Cool, thanks. I'll see if I can duplicate the issue, or try to fix it based on what you have provided.
[Nexus 4 Original Android Development] renna1992:
motley have you incorporated the hsic wakelock patches in your latest beta kernel? :)
[Nexus 4 Original Android Development] yurilebbie:
I had a spontaneous reboot as well, but last_kmsg was blank so I have nothing to go on.

I was reading an article on chrome when it happened though.
[Nexus 4 Original Android Development] Crimsonthunder:
No reboots no problems. Everything is running well.
[Nexus 4 Original Android Development] Simer03:
Never used a kernel that is so smooth with the recent button transitions!

Sent from my Google Nexus 4
[Nexus 4 Original Android Development] 3rdeyer:
I really like this kernel and all its extra options. I tried to play with the values in post 2. I like the boost feature, but i noticed something weird:

I use trickster mod and interactive governor. I enabled boost, but no matter what number I set for bootpulse duration, it will always stick to the highspeed _freq, even when idle and untouched for a few minutes. It would be awesome if we for example could set it to 4 seconds after touch, let it boost for that period, and than let it scale back to lower frequencies when the screen isn't touched. I think that was your intention, but it isn't working properly yet for me.

Edit: i just checked the boostpulse file with my root explorer and it includes an error message instead of a value: failed to open the file (java.io.IOexecption ....) Might that have something to do with it?
[Nexus 4 Original Android Development] dwang:
I looked at his git and I don't believe he has any of the latest ones. He has 2 from back in Dec, which isn't causing 3g mobile data drops for me and helps with hsic wakelocks on wifi.

Good thing he hasn't patched in the other ones as I was testing franco r32 this morning, which has all the latest wakelock patches and I was experiencing data drops.
[Nexus 4 Original Android Development] Hrithan2020:
Hi, if you don't mind me asking , are you using ondemand now? Asking as when releasing b12, you had suggested trying out interactive. I guess for battery, ondemand is still the best? If not kindly suggest a boostpulse duration, if possible.

I am currently trying out all kernels, for battery life ( with UC to 1.2 Ghz). Have heard good things about motley plus this is the only kernel which support uv till 600 mv. ( I have a "faster" bin cpu ). :D

Also, just wanted to confirm that apart from franco kernel, all other kernels [ I'll be switching from faux ] don't require flashing the stock kernel or cm ROM [in my case], right? [ asking as you have mentioned changing the init ram stuffs, and AFAIK, franco's kernel has the issue only because of changes in that]

Cheers :)
[Nexus 4 Original Android Development] drewtang:
As far as I know, Franco is the only one that uses his own ramdisk, but generally I flash faux's reset kernel before switching to different kernels(not just flashing updates) just for safety's sake. Is it necessary? Probably not, but I figure it can't hurt.

Edit: just noticed you're running CM, reflash your rom rather than the reset kernel. But faux uses the any kernel installer so you should be fine.
[Nexus 4 Original Android Development] Imperticus:
First time using your kernel, great work. Works really well together with codefirex which also linaro optimisation.
[Nexus 4 Original Android Development] digweed4me:
Exp 12 link not working from mobile.

Anybody has mirror for this?
[Nexus 4 Original Android Development] samwebbo1990:
Scroll further down the post and you will see the download
[Nexus 4 Original Android Development] rlaw:
Open in webview.
[Nexus 4 Original Android Development] _motley:
Yes, this is correct. I have been holding out on other patches since they appear to be a work in progress at Code Aurora. I appreciate the other devs that have been merging and working with them. I am still not sure if they have figured out which set of patches are beneficial and which ones to leave out. I have decided to spend my time elsewhere until I have a clear idea on what is going on there.

You don't want to enable "boost" in TricksterMOD or with other apps. That is a different option than the boostpulse feature. If you try to read the boostpulse file in a file explorer, it will behave like you have seen. It is not designed for read, just write. The write is being done from the custom PowerHAL library when Android decides you are interacting with the device. You can write to the boostpulse file by echoing a "1" into from a terminal or adb shell, but this is just for testing if it is active etc. This just instructs it to "pulse" for the duration at the highspeed _freq if it isn't already achieved for two cores.

So, for boostpulse, you only need to play with the two options in post 2 (hispeed_freq and boostpulse_duration).

Interactive is the default gov for now, but you would need to test between the two to figure out what works best for you.

If you use interactive, I recommend the defaults of course, but you can play with the boostpulse_duration and make it a bit shorter or longer if you prefer.

As far as flashing, it is always safe to dirty flash your ROM for CM 10.1. For stock, you can use the stock kernel zip from the OP. After your flash one of those as the first step, then you are fine to flash this kernel as the second step. If you are on an older version of this kernel already then there is no need to do the first step.
[Nexus 4 Original Android Development] air2k57:
Seriously though, thank you for not putting in patches which aren't final yet. I have had so many issues with Franco and data, but this works really well. Not to mention the great battery life.
[Nexus 4 Original Android Development] Simer03:
Just an update on my 3g only day with this kernel... Service varies from one bar to 3 bars here at work , never full service! Probably gonna hit 4-4.5 hours screen time

Sent from my Google Nexus 4
[Nexus 4 Original Android Development] Audioboxer:
Thanks for b12 :good:

I'm going to give ondemand a shot and see how battery goes. Was running interactive with b10.

I don't play any intensive games, so I might as well see which one will give me some more battery :confused: I'm assuming the boostpulse function works quite like mpdecision jacking the frequency up for a few seconds on touch? If so, does ondemand have an equivalent? (I'm assuming the exp kernels rid of mpdecision completely)
[Nexus 4 Original Android Development] flipim:
i dont know if its due to this Kernel.. but now on play store I cant download need for speed most wanted, it says that my device its not compatible with that app.
[Nexus 4 Original Android Development] ceejay83:
It's not related to the kernel. That's EA's fault. Good thing I have it backed up
[Nexus 4 Original Android Development] flipim:
So.. if i restaure to stock kernel, rom etc.. I will be able to download it again ? :S Or its happening even to people with stock roms?

Any known reason why is that happening?

Thanks for answering m8!
[Nexus 4 Original Android Development] 3rdeyer:
No, that wont help. Regardless of the rom and kernel your running on your N4 it will stay incompatible. EA will fix this, though.
[Nexus 4 Original Android Development] ceejay83:
Ea made it not compatible with our devices. If it's for bugs, or its an error we don't know
[Nexus 4 Original Android Development] flipim:
ok! Thanks!

I dont know why they modified that then.. because it was working really great!
[Nexus 4 Original Android Development] bash156:
First time android user bought this nexus absolutely love it I was using Francos kernel ever since I got this phone thought I'd try Motleys kernel with the help and advice from the guys on this thread flashed exp10 last night hammered my phone all day today with stock settings for everything and everything switched on and auto aswell . (WiFi) For the first time I'm seeing 5 hrs screen on time on my phone so thank you motley
[Nexus 4 Original Android Development] mobilehavoc:
B12 is the best kernel IMHO right now. Better than Franco for me.
[Nexus 4 Original Android Development] bash156:
Thanks gonna give that a flash now
[Nexus 4 Original Android Development] tooeasyforkevin:
Just got a random reboot too. Using b12 with xylon and I was just browsing the play store. Not sure how to get logs to help you out though if anyone wants to let me know
[Nexus 4 Original Android Development] bash156:
sorry guys to flash B12 do I just do a flash from my recovery, do I need to wipe caches sorry for the noob questions I used to just press the update kernel on francos app

regards
[Nexus 4 Original Android Development] dwang:
If you're coming from Franco, flash the reset kernel in the OP, then flash motley. I would rec exp12 or exp10.

If u are using Franco app make sure to unset all the boot options as motley runs great w default settings.
[Nexus 4 Original Android Development] jhericurls:
You need to flash the reset kernel first if your coming from the Franco kernel.

But yes, flash the zip in recovery.
[Nexus 4 Original Android Development] bash156:
sorry guys I should have said at the moment im on Motleys kernel on exp10

thanks
[Nexus 4 Original Android Development] pro.aggro:
then just flash the new build
[Nexus 4 Original Android Development] motoxxxx:
I see two build12. Which one do I flash? I'm on AOKP rom
[Nexus 4 Original Android Development] JmPTaz09:
Only flash the CM version if you are on CM or a CM based ROM. For aokp, use the other one.
[Nexus 4 Original Android Development] karanrajpal14:
If I'm not wrong, aokp is a cm based ROM!
[Nexus 4 Original Android Development] co.ag.2005:
Nope

Sent from my JellyBeer gulping Nexus 4
[Nexus 4 Original Android Development] masterg0g0:
Aokp and cm two different teams. Anyone this kernel support touch 2 wake? Good feature :)
[Nexus 4 Original Android Development] _motley:
I have now provided an "Inert PowerHAL library" in the OP. Look down near the bottom. Let me know how it goes. It will dull things a bit, but should help with battery.

I also have cleaned up the OP a bit by hiding some of the older builds with "Show Content" buttons. Maybe it will be easier for folks to read :fingers-crossed:
[Nexus 4 Original Android Development] tengen:
Has anyone noticed some CPU scaling irregularities in exp12? With stock settings on exp12 the CPU seemed to jump very aggressively between 304mhz and 1296mhz. However, once I lowered the hispeed_freq to 1026mhz using Trickster MOD, scaling now seems to more appropriately use frequencies between 304 and 1026.

I also noticed unusually high battery drain from the cell radio today, despite not going anywhere I don't normally go. That's a very preliminary observation though; will go through a few more cycles and report back. FWIW, that high drain did take place before I lowered the hispeed_freq, though that could just be a coincidence.

On the plus side, no crashes, reboots, or freezes so far :)
[Nexus 4 Original Android Development] whittikins:
That's not under clocking. Max is still 1500. I'm talking about hispeed parameter for the interactive governor. It just lets you set a % load that the CPU will jump to a specified frequency immediately (without using the middle frequencies along the way).

Morley's default is that at 80% load, the CPU will jump to 1500mhz. I'm simply testing 1026 instead. It jumps to 1026 at 80% load, but it will certainly still use 1500 too if the load demands it. So far it's still running very fast, but I haven't been able to compare it thoroughly yet.

---------- Post added at 10:04 PM ---------- Previous post was at 09:56 PM ----------

Ditto. This is the main feature that is noticeably laggy on other kernels. It populates instantly on this kernel instead of being delayed and populating a bit slowly.
[Nexus 4 Original Android Development] whittikins:
Thanks for the updates! I'm going to flash b12 tomorrow, but do you mind giving your input on this post? http://xdaforums.com/showpost.php?p=36567541&postcount=618

Also, I saw that b10 has default hispeed_freq as 1500, so I assume that's the reason. I was just curious if hispeed_freq of something like 1026 at 80% (or possibly lower) would still be really fast but save some battery. I'm trying it myself, but I'm still wondering what your thoughts are (and if you already tried this). :)
[Nexus 4 Original Android Development] ptesmoke:
See this doesn't make sense to me. Obviously aokp doesn't have the same kernel. But every non aosp device I've seen with aokp,was based off of cm's device tree.

So is aokp based on cm? Rom wise is guess not but device wise yes?