yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Original Android Development] _motley:
Thanks everyone! Please do let me know how it goes and if anyone experiments with the new tune-ables.

Yes, that is by design. OnDemand is still there if you want to try it, but I opted for interactive since it has input boost to replace the absence of the project butter input boosting. The auto-hotplug tuning can also be taken into consideration.

Thanks, it was the 30th, so it is now over here...so on to the next year of my life LOL.
[Nexus 4 Original Android Development] nick314:
Happy Birthday!

On exp 10. Best battery life of all the kernels I've tried.
[Nexus 4 Original Android Development] mgear356:
Btw Franco has added in the 3g patches from quadcomm .. Is it in exp 10?
[Nexus 4 Original Android Development] w0dash:
Just out of pure interest, can somebody explain to me why there are 2 different versions, one for AOSP and one for CM?

Other kernels only come in one version for all roms.
[Nexus 4 Original Android Development] _motley:
Well, here is some background info. It basically comes down to the fact that

ALL

of the most downloaded kernels are either altering the ramdisk, altering/renaming binaries in the /system partition, OR both. This is true whether they use the AnyKernel method or not. This is also true for my experimental kernel. Using the term "experimental" in the way I do, I also consider

ALL

of the most downloaded kernels experimental because they either altering or removing mpdecision, thermald, or PowerHAL. Read my OP for more information on how I define mainline (stock-like) and experimental kernels. Perhaps I should use the term "Open" instead of experimental.

After you flash any of our "experimental" kernels you have to flash the kernel reset zip in the OP (stock ROMs) -OR- flash your current ROM nightly (custom ROMs). This has to be done before you can safely move to another kernel. If you don't follow this rule, then the new kernel you flash either won't work properly or may not even boot. Users don't understand this or don't read all the directions and end up in a bad situation. Of course they blame the kernel at first, but it is really contamination from a previous install. Users also make the mistake when coming to a new device that things will be exactly the same as how they have flashed kernels for other Android devices. This is just not the case as there are always exceptions. With a Qualcomm SoC, things are a bit more complicated and thus we have more to deal with. This is why half the posts in some of the kernel threads say: "I can't boot" or "it is really laggy" or "my Android log is full of PowerHAL errors".

My mainline kernel has one zip for all ROMs because it uses the AnyKernel method. It slips the kernel zImage inside the existing boot.img and re-flashes it. This preserves the ramdisk without making any edits to it. However, this method can be troublesome when users are coming from another kernel or ROM that uses a custom kernel as they have to follow the procedure above to revert back to their initial state.

With my experimental kernel, I have moved back to using a full ramdisk install. This protects users from having to worry about ramdisk contamination when coming from other kernels or a custom ROM. They just flash the correct version (stock AOSP or CM) and go. The added bonus here is that the stock ROM gets init.d. CM already has this feature.

This may change and I may move back to a "dynamic" AnyKernel install like showp1984 is using, but even then the end result is very much the same since I need to make changes in the ramdisk for the experimental build to set the default gov to interactive, keep mpdecision/thermald from starting etc.
[Nexus 4 Original Android Development] _motley:
Yes, I saw this Code Aurora patch he merged last night. At first he had it merged into the wrong source file and I was skeptical. I was just about ready to notify him, but then I noticed that someone else posted on github to let him know. I had to grin because at times I have found myself looking in the wrong place for the board source file. For mako they are in a custom folder unlike most other kernels.

I will be testing this fix in my next sprint and will be including it in the next build if all goes well during testing.
[Nexus 4 Original Android Development] yonpa:
I came from Franco kernel and for now I can say, great work motley very smooth and the battery life is very similar. Going to try it for more time
[Nexus 4 Original Android Development] w0dash:
Wow, many thanks. I didn't expect such a detailed answer :)

Just one question, which Version do I have to use for AOKP?
[Nexus 4 Original Android Development] _motley:
No problem. AOKP is AOSP kernel compatible I am told, so that is the install to use for my exp kernel. The mainline anykernel install is compatible as well.

Happy New Year everyone!
[Nexus 4 Original Android Development] ptesmoke:
Checking in later than expected but I'd like to say standby drain is awesome and gaming feels fine in need for speed most wanted.

Impressed. I'm never leaving this kernel again! Thanks motley!!
[Nexus 4 Original Android Development] port76:
can someone give me a link for the kernel I'm on a stock based ROM pls much apreciated:D:thumbup:
[Nexus 4 Original Android Development] inffy:
It's in the first post (AOSP)
[Nexus 4 Original Android Development] trismegistos:
Very nice kernel, using latest exp version on cm and runs really good so far. Thx motley!

Gesendet von meinem Nexus 4 mit Tapatalk 2
[Nexus 4 Original Android Development] dwang:
Been testing out franco, harsh, and faux's kernels and I've been experiencing intermittent 3g data drops with all three of them. They all seem to have the 3g power saving patches. Other people have also reported some issues with 3g data drops on those threads.

No issues with 3g data drops with exp10.

Have u run into any 3g data drops while testing the 3g power savings patches?
[Nexus 4 Original Android Development] _motley:
Thanks for the feedback. Gaming has also been good for me in b10 after all the latest thermal enhancements. For those that want more headroom (and are fine with a little more heat), can raise the throttle temp a bit. I think the 64C is a nice default.

Thanks for the info. To be honest, I have been busy the last couple days over the holidays so I haven't gotten in any real world testing with the 3G patch yet. I haven't experienced anything like this in b10 either (knocks on wood). I'll have to read up on what is going down in those threads to see if everyone agrees on the common denominator.

----

If anyone else has feedback on b10, please let me know ASAP. Thx!
[Nexus 4 Original Android Development] ixxeon:
Really outstanding Kernel - fixed the two main issues I was seeing with Nexus 4 on stock - CPU heat and battery life

With stock 4.2.1 by the end of the day my Nexus 4 was at 20-25% battery, now with motleys Build 57 i'm seeing more than 50% under the same useage patterns and no issues at all. Using default Ondemand gov. Performance is as fast as ever in the becnhmarks.

So I just dropped motleys build 246 onto my Nexus 7 with 1.6GHz CPU OC and seeing Vellamo 2,0 metal benchmarks jump from 355's to 505 !

I will be making a donation after writing this, THANK YOU, GREAT WORK !

Requests for future Nexus 4 builds: optional CPU OC 1.6-1.7GHz, GPU OC to 450MHz, move governors like to play with like interactive, smartassV2 etc.
[Nexus 4 Original Android Development] rlaw:
Hmm, battery life on latest experimental is excellent as ever (3-5+ hours screen on time) but I'm occasionally getting slow down and stutters when my ram usage gets to 1-1.2GBs.

Never experienced that with any of your previous kernels. :(

I don't think it's a rogue app since I'm running the same apps, widgets etc and my usage is the same. Not sure what's up.
[Nexus 4 Original Android Development] lazer155:
How do I install the experimental kernel if I do not want to use custom recovery to do so? Can I use fastboot instead? Normally I use boot.img files with fastboot but this is packaged as a zip. If I extract the boot.img from the zip and install it will it fully install the kernel? I am trying to return my kernel to stock with your reset stock kernel package before I install your experimental beta 10 version. Will extracting the boot .img from your stock reset zip result in a full stock kernel reset? There are 2 folders inside the zip besides the boot.img and that is why I am thinking it will not be a proper full reset and could cause problems when I install the experimental kernel.

I am coming from franco r23.

Also can I control this kernel with the franco.updater app? Things like the cpu and color settings?

FransicoFranco also mentioned this:

"There is not kernel reset script, not kernel clean up, not kernel reset. I use my own ramdisk no matter how many cleanup things you use my ramdisk will always be overwriting whatever was there before."

Is that true? I thought the reset kernel that motley packaged includes a stock ramdisk. That just doesn't made sense to me that franco's kernel wouldn't be overwritten with motley's kernel.
[Nexus 4 Original Android Development] Globespy:
I read that you have a zip for restoring stock kernel settings, but it doesn't contain the actual stock kernel?

Do you know where to find the stock kernel? And wouldn't this reset everything anyway?

Sorry if I'm missing something...
[Nexus 4 Original Android Development] kitch9:
I could do with more in depth instruction too... I've downloaded the zip, but I'm unsure what to do with it.,..
[Nexus 4 Original Android Development] 3rdeyer:
Great kernel! I am using b10 for about one day now with the interactive governor and the device has never been so fast.

The ratio between performance and battery is perfect for me. I've tried several tried faux's kernels but I came to the conclusion that this one will be my daily driver.

^^ - just flash the reset kernel in recovery and install your desired kernel afterwards.
[Nexus 4 Original Android Development] _motley:
Thanks for feedback and your generous donation ixxeon, it is much appreciated. If I decide to OC, it will be in the experimental build. I think I have the proper thermal control in place now that it could handle it. As you read through the other threads, especially in the beginning, there has been a fair number of people that have had problems with overclocking and I am not 100% sure why this is. I tend to agree with showp that it likely has to do with thermal control over the CPU and the stock kernel didn't have the proper controls in place.

Let me know if you can pinpoint what is causing it and whether you are on the stock ROM. What apps do you have loaded that consume large amounts of RAM? Curious to know whether they are gpu intensive or other types of apps. In system tuner, you can see the amount of kernel RAM being used. I would also be curious to know what you see there when it is in this state.

P.S. one thing that I have done that seems to help with a bit of periodic lag I was having. I went into the "Currents" program that comes with stock and I have turned off sync. Most of the time lags are due to disk activity. If your issue is with disk IO, you can also try some other IO schedulers to see if they help.

I definitely recommend using a custom recovery to install the kernel. If you flash the kernel using the boot.img in the zip, it won't properly update /system (experimental), so you would have to copy those files separately etc. Custom recovery offers so much more than stock recovery and you can always go back to stock if you want. Not sure why anyone would resist this. It makes your life so much easier.

Yes, his app will likely work to control color, CPU etc., however I have not tested it. I normally use System Tuner and Trickster MOD. Both have free versions you can try. For voltage control, I recommend one of these two.

While franco may not provide a zip to restore the stock kernel, I do provide a reset zip in my OP for the

stock ROM

. This will replace the ramdisk and kernel and with the stock version. It also replaces 3 binaries back to stock. If you have a ROM other than stock, just reflash your nightly to achieve the same. After the reset, you can flash my kernel and it should work fine.

If you flash my experimental kernel, you shouldn't even have to do any of the above since it includes the ramdisk and provides the binary it needs.
[Nexus 4 Original Android Development] rlaw:
I currently have 14 apps open in app switcher but they don't really consume much RAM, have 936 used and 935 free. I'm using codefireX SR1 but had not experienced slowdown with it on experimental 8.

I've increased read ahead size to 2048 and haven't noticed any lag or stutter yet.. Only been about half a day, though.

I'm also wondering if you've seen the entropy mod for Android that supposedly increases performance?

I've seen two alternative methods to the apk the author created (as that app wakes the device every second). Zeppelinrox's method http://xdaforums.com/showpost.php?p=36093065&postcount=254 and the symlink method http://xdaforums.com/showpost.php?p=36226518&postcount=331.

Zeppelinrox's method seems better suited towards maintaining cryptographic secure, high quality randomness while the symlink method is much simpler. Maybe you'd like to test these two out for any possible performance increase for a future experimental build?

I'm using symlink and my performance seems better but that could very well be a placebo.
[Nexus 4 Original Android Development] ctfrommn:
Motley,

Any chance of implementing a gamma tweak like Franco? Whatever values he changed make his kernel look absolutely amazing and perfect in my eyes. I know Faux's implementation is "closed" as it were and I have no idea what or how Franco modified his so simply wondering. Thanks for all your hard work with this.
[Nexus 4 Original Android Development] trismegistos:
hi, 2 ways to go:

1: ask france what blue/green/red settings he has set in his settings

2: look in his githup, it should be there somewhere.

if you have the values you can set them with any kernel app.
[Nexus 4 Original Android Development] ctfrommn:
Not looking for RGB but rather the gamma settings. I will look at his guthub, but I still wont be able to change gamma as that needs to happen at the kernel level.
[Nexus 4 Original Android Development] lazer155:
Does anyone notice a slight lag when waking the phone up to view the lock screen after it has been asleep for awhile? This is without any lock screen widgets and just the time. When the lock screen comes up, it is frozen for a second before unfreezing and the slide to unlock circle begins to pulse that ring of dots. It's just something I noticed coming from the franco kernel. With franco, the lock screen's slide to unlock circle never delayed pulsing the circle of dots when you pressed the power button to view the lock screen/wake up the device.
[Nexus 4 Original Android Development] ctfrommn:
Which kernel? (Stable or Exp) Rom? Kernel settings? I have never seen a hiccup on Motleys kernels.
[Nexus 4 Original Android Development] lazer155:
Sorry forgot to mention which one I am using. I'm on the stock rom. The kernel is experimental beta 10. Before flashing it, I made sure to flash his reset kernel so it should be a good install. I haven't changed any kernel settings, everything is default. The short delay only seems to happen after the device sleeps for awhile. If you unlock it, relock it, and unlock it again quickly; the delay doesn't happen.
[Nexus 4 Original Android Development] trismegistos:
i saw this on faux, motley and harsh kernel. never seen it with bricked/franco...it happens everytime after the phone is switched off for about 10 seconds..
[Nexus 4 Original Android Development] lazer155:
Is it possibly due to deep sleep turning on after 10 seconds so it takes longer for it to wake up? Or could it be the default on-demand setting rather than interactive like franco? Franco and motley are the only kernels I have tried so far. So I'm not sure what default setting bricked, faux, or harsh use.
[Nexus 4 Original Android Development] trismegistos:
i always use interactive, so that was not the problem. i think it only happens if the phone was in deepsleep before.
[Nexus 4 Original Android Development] lazer155:
That's strange then. Maybe motley could look into the issue for correction in a future release. It's not bad enough to make me switch kernels but it would be a nice improvement for a future update.

Is the difference between interactive and on-demand very noticeable for you in terms of interactive being a little more performance focused and on-demand focused a bit more on battery life?

I switched from Franco because my screen on time never improved from the stock kernel. I'm hoping motley's will be better. So far it seems great.:good:
[Nexus 4 Original Android Development] rlaw:
Same thing here. Little bit of a catch up period once the phone's been asleep for a while.
[Nexus 4 Original Android Development] dwang:
looks like cm10.1 folks are running into the mobile data issues as well. cm10.1 merged in the hsic ehci patches a few days ago.

http://xdaforums.com/showpost.php?p=36246205&postcount=2721

exp10 still running like a champ!
[Nexus 4 Original Android Development] trismegistos:
For me there is a huge difference between on demand and interactive. Interactive is much more responsive for me.

Gesendet von meinem Nexus 4 mit Tapatalk 2
[Nexus 4 Original Android Development] Stefa.:
I installed the motley kernel and I can see that the min CPU freq is: 1026 MHz (governor "ondemand").

Is it correct?

Is not this value too high for a good battery life?
[Nexus 4 Original Android Development] batman368:
that shouldn't be right, low is 304Mhz. i think that the governor sometimes moves the low end, or at least that is what it looks like in system tuner. you should open system tuenr and just let it sit for a while, then low will go down to 304
[Nexus 4 Original Android Development] Stefa.:
I am using "TricksterMOD" and i can see that actually the CPU goes down to 304 if i do not perform any operation but if i control the CPU freq limits i see that the "min" is setted to "1026 Mhz".

Should I ignore this and manually set it to 304Mhz?
[Nexus 4 Original Android Development] batman368:
don't change it, just trust your dev :)

seriously, i wouldn't change anything from defaults, besides voltage.
[Nexus 4 Original Android Development] Stefa.:
Got it!

I trust motley but i just wanted to know how this frequency limits work ;)
[Nexus 4 Original Android Development] tengen:
The 1024mhz you're seeing is Project Butter at work. Basically whenever you touch the screen, the system will ramp up the CPU automatically (temporarily overriding your minimum frequency settings) to make sure that everything runs buttery smooth :) When you touch the screen to adjust frequencies in TricksterMod, Project Butter kicks in for a bit - so don't worry, it'll go back down to 304 after a few seconds of not touching.
[Nexus 4 Original Android Development] _motley:
Yes, I am running rooted stock since I bought the phone, but I am also getting an itch to flash something new. It will likely be CM10 tomorrow so I can check out what they are doing with their ramdisk and if there is really a compat issue with the anykernel zip. Anyone else running this kernel with CM10? Gotta head to bed, I am dead tired :(
[Nexus 4 Original Android Development] ptesmoke:
Hehe I was thinking the same thing. I'm on modaco's ROM right now....which works fine..but is pretty much stock.

I'll be flashing tomorrows cm10 nightly and whatever kernel you have avail at the time :)

Thanks again for your work!
[Nexus 4 Original Android Development] kaiser_tytnii:
Thanks! Working so far so good with this UV setting! Wondering what u set for 304mhz
[Nexus 4 Original Android Development] DONNY TRUMP:
CM10

I wanna try this with CM10 dammit lol why isnt it simple anymore???
[Nexus 4 Original Android Development] 0.0:
Maybe the reason for my yellowish screen issue is I was on a cm ROM, not stock

Sent from my Nexus 4
[Nexus 4 Original Android Development] okyere:
_motley, I appreciate your work on the Nexus 7. When my N4 arrives I'm flashing this kernel. Thanks.
[Nexus 4 Original Android Development] whittikins:
Motley, should we be using Ondemand or Interactive? I flashed the .ZIP, and it defaults to Ondemand, but I saw in your OP that the .IMG uses Interactive and a lower voltage. Does the .ZIP not use a lower voltage? It's a little confusing as to which one does what :)

From the looks of it, the .IMG will be better for battery... :confused:
[Nexus 4 Original Android Development] kaiowas82:
I'm using your kernel with cm10 from yesterday...everything smooth so far, I've undervolted but doesn't seem to gain any battery life compared to stock cm, but again, I flashed it only yesterday :)
[Nexus 4 Original Android Development] kptnk:
I'm using it since 24 hours and battery life is excellent so far. Will see more precisly after the 2nd full charge. The sleeping is especially awesome : when it sleeps, nothing is loss, while it wakes very fast (unlike me...)....excellent job, thank you. And yeah, still very snappy at 1350 cpu max, with CodefireX rom.
[Nexus 4 Original Android Development] tpboi:
Np. I gotta say this kernel with some proper nv I'm getting near 6 hr screen on to. Thank OP!!
[Nexus 4 Original Android Development] Jordanooo:
Does this mean you can mount NTFS USB's?

Sent from my Nexus 4.
[Nexus 4 Original Android Development] il buono:
Battery life is definitely great with this kernel. I'm using it with Paranoid Android and now I can easily get over a full day of usage whereas before it would need to be charged right when I got home. :good:

Sent from my Nexus 4
[Nexus 4 Original Android Development] Cyb3rGlitch:
I'm currently using this kernel, and discovered that capping the clock rate to 1GHz with a 150mV UV works great.

https://plus.google.com/115395645419924848353/posts/RegaU7oC6fj
[Nexus 4 Original Android Development] digweed4me:
Can we have your full set up or u just did -150 uv on all CPU frequency?
[Nexus 4 Original Android Development] cpom1:
I'm running your latest kernel with cm10 and I like it. :)

Sent from my Nexus 4
[Nexus 4 Original Android Development] Imppy:
Which program do you guys prefer when setting CPU and voltage settings?
[Nexus 4 Original Android Development] keda:
I hear less and less people talk about setcpu now. Does it still work well with JB? What do you guys prefer?
[Nexus 4 Original Android Development] Cyb3rGlitch:
-150mV on all frequencies.
[Nexus 4 Original Android Development] gbroon:
I found set CPU doesn't change voltages Using system tuner https://play.google.com/store/apps/details?id=ccc71.pmw.

Heres my current voltages that don't seem to have caused problems after a few hours. If I have no porblems by tomorrow I'm going to play about with voltages starting with my most commonly used speeds from CPU spy and start finding lowest values.
[Nexus 4 Original Android Development] Logi_Ca1:
I would like to know as well. Both SetCPU and voltage control don't allow me to change voltage for some reason :(
[Nexus 4 Original Android Development] Stefa.:
Thanks for your explanation, really useful ;)
[Nexus 4 Original Android Development] inffy:
Is francos kernel app able to control also this kernel?
[Nexus 4 Original Android Development] ctfrommn:
Yes....it will control basic features of any kernel.
[Nexus 4 Original Android Development] lazer155:
I noticed in the OP for the release it says that on-demand is the default CPU governor but when I look at the governor settings with system tuner, it reports interactive as the current governor method. I haven't changed any settings. Was interactive made the default in a newer update so the OP isn't correct by saying on-demand is the default setting?
[Nexus 4 Original Android Development] ctfrommn:
OnDemand is default for stable and Interactive for the Experimental.
[Nexus 4 Original Android Development] lazer155:
That explains it. I'm using experimental.
[Nexus 4 Original Android Development] ctfrommn:
Thats the better one anyway.....amazing kernel!
[Nexus 4 Original Android Development] Stefa.:
Is it the experimental kernel also better for what concern the battery life?