yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Original Android Development] chrone:
i always switch back to cfq 128 as in my experience it is the best fluid experience i had when scrolling content inside apps or opening apps. it's very subjective though.

stock kernel uses cfq io scheduler with 128 readahead.
[Nexus 4 Original Android Development] :
Hi,

No, these values are for the LowMemoryKiller (and before you ask, don't touch these values or learn about memory management in Android before :D, no offense ;) ), nothing to do with the I/O scheduler.

It's this for the SIO I/O scheduler:

And I use 2048 readahead.

@ chrone, yes ok, so you already tried SIO, and with my values?

In any case I can also try CFQ to see... but for me (actually) it's SIO that run better between Deadline / FIOPS / RAW / NOOP but it's right I never tested CFQ...

And yes maybe all this stuff about I/O scheduler is subjective, maybe placebo... Even if I don't really know if an I/O scheduler can really make a difference at this point (I mean in general UI), at least for me. There is some benchs about the different I/O schedulers around the web for to have an idea... It's BFQ I would like to have to see (in the last update like BFQ v3 or v4, I don't remember exactly).

:)
[Nexus 4 Original Android Development] Remoteconcern:
I've always used SIO since the GNex. Its always been the fastest for benchmarks and I've never noticed improvements in speed using any other scheduler, so I'm guessing its worth sticking with.

Motley makes it default for a reason. Its been a really long time since he's been here though, I'm concerned!
[Nexus 4 Original Android Development] Kocai:
I'm quite sure that my battery is calibrated. Maybe it's like what thracemerin said, the battery chip in this phone is quirky. I haven't done any further or advanced testing though. I got 5+ hours screen on time this morning with 20+ hours on battery after charging with the wall charger. Let me charge it with the orb again tonight and see if the battery would drop faster (hopefully not).

Luckily, I don't have the wake lock anymore. It only happened the first time I used the orb.

I asked my friend's wife to ask her cousin in the US since she's asking her cousin to buy the N4 for her from the play store when it got restocked. Bought it at normal price + shipping and tax; around $70.

As far as the charging time, I don't think it's any different than the wall charger.

To be honest I haven't seen the micro stutter you've been mentioning. And the flicker because of the new 4 layer composition that moles talked about only affects PIE or full screen mode which I don't know what the flickers look like. I don't think it has something to do with the micro stutters you're seeing. I only notice recently that I got weird black line flashing for a split second at the top part of the screen whenever I clear apps from the recent apps list which only happens when I start clearing the app one by one from the bottom.

And like I said before, Google hasn't done a good job with JB 4.2.x. JB 4.1.2 was a beast and a beauty as well compared to 4.2.x.

Just ignore those micro stutter and enjoy your phone. It can't be fixed from the kernel side nor ROM side at the moment. Or buy the Nexus 5 with KLP ;)
[Nexus 4 Original Android Development] :
Yes the build.prop edit about "persist.hwc.mdpcomp.enable=true" is only related to screen flickering.

Set this line to "false" or "3" should avoid screen flickering in certain case but can slow down the UI as Molesarecoming said.

Also on the other part about micro stutters in certain animations I think it depends on the system itself but some roms and some CPU settings can help. With AOKP PUB and my settings I have not micro stutters. But like chrone noticed (if I remember right) after about 2 days without a reboot I have these micro stutters also (I noticed it the last time I posted here my battery stats for 2 days, it was a long time I've never rebooted my phone for 2 days :D). Not a big deal since in general I reboot my phone once a day for different reasons and also wipe the dalvik cache in recovery seems to help...

Yes something is not well optimized in the system about the animations, like I said maybe something in the framework I think. Or also a combination of different things.

It's a workaround but a reboot once a day (with dalvik cache wipe), Interactive governor with "performance" oriented settings (and other settings like I/O scheduler) and a rom with Linaro / Bionic /Krait optimizations (it's not only for benchs these optimizations :D) helps a lot. At least it's my opinion after testing too many things...

Some changes in the buil.prop for "dalvik.vm.dexopt-flags" line seems also to play something... I let you search on Google for this, I'm currently testing some different settings... :D

To many things to test and investigate... :eek: :D

And...... yes......... Key Lime Pie!!!!!!!!!!!! :p :D

:)
[Nexus 4 Original Android Development] Spec-Chum:
I just stick with the default sio With 1024 readahead.

Can't say I've noticed any stutter compared to cfq when I was on pure stock.
[Nexus 4 Original Android Development] :
Re,

_motley is connected yesterday... but still no news, as always I hope he is fine. I'd be happy if he give us some news of his health. Or he's taking a break from development :confused:

In any case just a "little hello" with some news would be good, even if it's not some good news (I hope it's not the case), just to know, to have some informations... my bad, I worry for him.

:)
[Nexus 4 Original Android Development] meangreenie:
Is the stutter you talk about where when scrolling a screen up or down you get a jerk/stutter just as the scrolling slows and stops?
[Nexus 4 Original Android Development] :
Hi,

No, it's about micro stutters in some animations like when you open settings or when you open an app, sometimes the animation is not smooth. But it depends, some have it, some no...

In developper options, animation set to 1 is always smooth but it's when it is set to 0,5... sometimes :eek:

What you are talking about it's a typical XDA app thing (or mainly Tapatalk app) :p:laugh:

:)
[Nexus 4 Original Android Development] hoangtungst:
Hi Viking, my phone is smooth now after i use your setting with sio scheduler but it is hot now. Battery can reach 37 degree c and cpu can reach 55 degree c when i use wifi for surfing web or watching video on YouTube
[Nexus 4 Original Android Development] :
@ hoangtungst,

Ha, nice to hear! :), I'm glad for you ;)

Your battery and CPU temperatures are absolutely normal, mostly with this kind of use..., no worries.

A little reading about temperatures, read the OP and my posts (:D), I'm too lazzy to repost here... :laugh:
[Nexus 4 Original Android Development] hoangtungst:
There is no problem if i charge my phone overnight?
[Nexus 4 Original Android Development] :
I don't think so, but I avoided... you never know :D

No particular reasons for me but I have never left my phone charging during the night (nor in the journey LOL), when it is fully charged I unplug, always.

Maybe you'll have more advice about this question...

:)
[Nexus 4 Original Android Development] ‬1‬:
i've been charging my phone overnight since the day i bought it.
[Nexus 4 Original Android Development] trillo69:
I dont think there's any problem with that, amperage is really low near 100% so it's hard to damage your battery doing that. You can check in the morning that your battery is cold.
[Nexus 4 Original Android Development] :
Hi,

It's quiet here... :D

Do you want to try something...? Like chrone tested some build.prop edit to avoid micro stutters, I try also... :D and since I like test a bunch of things with my phone...

Make a Nandroid backup first, I'm not responsible for anything could happen (in any case I have not faced any bootloop or weird issues but we never know ...). And maybe the following things are pure placebo effect... And carefully read the following lines (all, mainly the end).

Edit your build.prop and add the following lines at the end:

Then modify the following line from:

To:

Then modify the following line from:

To:

And finally go to /system/lib/egl and delete or rename (with the .back extension) the libGLES_android.so file.

Then reboot in recovery, wipe dalvik cache, reboot and see...

I know there is also some other things related to RAM and VM management to do but these things have not given conclusive results for me (maybe some little improvements on a side but some things broken on another side like lags about 1 day, smooth UI but lags in game or vice versa, etc...). And there is a bunch of tread about these twinks in Android Software and Hacking General.

It's a little Off-Topic, I know, but since we are spoken about micro stutters here... and there is not much more to talk about the kernel because it's perfect I therefore allows myself a slightly Off-Topic.

No need to speak about it for 10 pages for why or how that, just test, see and let a little feedback if you see something better or not. If you want to know exactly what this line does or not, Google will be a better explanation than me I think.

Sources:

Google search, XDA, some tweaks from my Gnex days (with ICS so... :confused:), some rom tweaks (credits to the devs) and I don't remember...

Like I said maybe these tweaks does nothing (nothing is scientifically or technically proven :D) or it's the placebo effect or I'm totally wrong so if you don't see any improvement you are warned ;). In any case they don't hurt, at least for me. And I have not the pretention (like some threads about these kind of tweaks) to have found the extrem turbo smoother, mega giga tested fluid tweaks in the world :silly::laugh: and I'm the first to say that these tweaks don't do (almost) nothing :eek::p:D

And you will know that some CPU settings helps a lot also like some other factors.

Then we'll talk about the kernel itself huh :p:laugh::laugh::laugh::D:D:D

:)
[Nexus 4 Original Android Development] chrone:
lots of tweaks there. :good:

it often started with smoothness after flashing kernel/rom/wiping cache-dalvik-cache/tweaking kernel paramater and such, and then after a prolong idle when sleeping, the micro stuttering reappeared again when i woke up. used to get more than one week uptime on galaxy nexus without the need to reboot the phone, but on n4, i found myself flashing/rebooting several times a day just to get rid of the stuttering animation.

now, i give up and set all animations to 0. lol :D
[Nexus 4 Original Android Development] ctfrommn:
Those work great on anything ICS and below. They were mainly designed for GB phones. I used all those on my N1 and they made a huge difference. I have yet to find a build prop tweak that helps a bit on JB though. All they seem to do is make things worse.....the cleaner you keep things the better they run. Case in point, try Pimp My Rom and start turning things on, you will see what Im talking about. I wouldnt spend too much time on these things.....IMHO :)
[Nexus 4 Original Android Development] hoangtungst:
my phone has smooth for few days and now lag appears again . I think it is a lag animation and only when i scroll last page ( apps) to left
[Nexus 4 Original Android Development] :
Last_kmsg

Hi,

This is the first time that I have a hot reboot since I use _motley kernel :eek:

No undervolt, no overclock, I was trying to open a file with Root Explorer and BAM!

It's due to a" Kernel panic - not syncing: Fatal exception" but as far as I know we cant't know the eaxct reason, right?

If someone can take a look at my last_kmsg in attachment, thanks :)

Hi,

Hum... a reboot will normally get rid of your lags or it's something else (lack of ram, an app that use a lot of ressources, etc...)... Where are your lags? Always in your app drawer?

PS: about my "tweaks", I know and it's why I said "read all and mainly the end"... ;)
[Nexus 4 Original Android Development] kszaq:
Are you using Motley's original kernel or my modified one with updated WiFi drivers? I was getting this type of reboots quite often lately and sometimes it caused my apps' data to be wiped (that's how I learned to do a Nandroid every other day!). I thought it was due to some other tweaks I applied to Motley's source, but I couldn't really track it down. I'm no dev after all, simply a cherry-picker... ;)

You have to keep in mind that Motley's kernel is already a bit undervolted, but I don't think that would be the reason of your reboot, cause they also happened to me when I compiled the kernel without undervolting. I didn't try removing underclocking, though.

Another thing that may be causing the reboots is Thalamus' auto-hotplug. I remember Franco used it for some time (after some modifications) and his users were reporting problems very similar to yours. It may be that our APQ8064s don't like that implementation of hotplugging.

Please keep in mind that these are only my guesses, I'm no dev at all.
[Nexus 4 Original Android Development] :
Hi,

Thanks for the reply ;)

I use _motley's original kernel (b49). Weird it's the first hot reboot since about 2 month I use _motley kernel, never had any reboot even in "hard" conditions...

It's not a big deal, it was just to know.

Fortunately no apps data was wiped even if I have fsync and Dyn_fsync disable for both... Mainly a data app wipe is due to fsync off when a hot reboot happened.

:)
[Nexus 4 Original Android Development] hoangtungst:
I reboot my phone everyday, lags appear only when i scroll last page of app drawer to left
[Nexus 4 Original Android Development] caaznkid:
So is motley okay? Heard something was up that's why he hasn't been updating. Hope he's alright.
[Nexus 4 Original Android Development] chrone:
All i can say is that motley kernel handle uv the extreme way, didn't have any reboot even after 2 days of usage with 600mv uv.

But once i started flashing matr1x kernel and set the same uv, i got rebooted instantly. Lol :D so i set the minimum voltage to 725mv for the minimum cpu freq as in motley just to be safe. Even on faux kernel the minimum uv is 800mv for cpu bin fast.

This kind of android 4.2.2 issue bugs the hell out of me. Lol. I just want project butter again. Smooth smooth smooth to the last scroll and swipe. :)

Have you tried to set all animations to 0 and force gpu rendering and reboot?

Sent from my Nexus 4
[Nexus 4 Original Android Development] :
LOL :laugh:

We need Mpdecision back maybe :confused: :D

Micro lags / stutters also with the stock kernel? We need to tweak the Interactive governor to avoid them (

or at least almost avoid them

) ... It's what I experienced...

@ hoangtungst, you can try Nova launcher, smooth... but I agree it's not THE solution.

:)
[Nexus 4 Original Android Development] chrone:
I'm guessing the gpu driver is not optimized yet, or something in the android os starved the gpu bandwith thus translates the stuttering.

I've done some reading on intel atom e6xx errata that when using hw overlays the screen will flicker due to lacks of bandwith when playing 1080p video, but not if using 3d rendering.

I'm just a normal user, so take my two cents with a pinch of salt. Haha :p

Sent from my Nexus 4
[Nexus 4 Original Android Development] hoangtungst:
I have tried set all animations to 0 but it dosen't effect to app drawer. I turn on force gpu rendering always but not really effective
[Nexus 4 Original Android Development] ctfrommn:
On advice from simms and others, I have been playing with all 4 core always on to negate the battery/performance hit seen by constantly onlining/offlining cores. I must say I was skeptical but it is mpdecision smooth with the same battery as before. I know Motley's allows the same option. Give min cores online=4 a try.....its an interesting experiment for sure. I have underclocked to 1026 also so battery is really good.
[Nexus 4 Original Android Development] ptesmoke:
epic dev is epic :) motley you rock dude

edit: looking perfect so far...settings sticking across all cores...even after reboots. thanks man!
[Nexus 4 Original Android Development] Logi_Ca1:
motley just wondering, is 700mv the lowest we can go, or could you lower the limit even more?
[Nexus 4 Original Android Development] jordant2:
Just had to say thanks for this kernel. Just the slight RGB tweak you did really made my screen pop. I definitely recommend it, and coming from the One X my screen colors seemed a bit pastel. Now it looks great!
[Nexus 4 Original Android Development] whittikins:
This is running very smoothly :). Do you think you could make it use the lower frequencies a bit more aggressively or use 1026/1500 a bit less aggressively? I ask because after some light Reddit and Tapatalk browsing, my cpu usage looks like this. I don't necessarily want to cap my max frequency, but rather make it take more load or longer load to jump up from the lower ones. Let me know if there's something I can tweak! Thanks!
[Nexus 4 Original Android Development] JmPTaz09:
16 hours on build 41; great battery life with normal usage. About 4 hrs screen on
[Nexus 4 Original Android Development] magestic1995:
Great kernel. Just started using it, will update with how its working for me
[Nexus 4 Original Android Development] _motley:
Haha, thanks. Glad to hear it is working good for you. I couldn't just sit back and watch everyone wrestle with those cores! It was bugging the crap out of me as well:laugh:

Not sure, but I feel that it is pretty aggressive thus far. We'll see how 700mV goes for the masses before we push it further. The default is 750mV at 304MHz, but I will have mine set at 700mV all day today to see how it works out.

Thanks for stopping by, glad you like the color tweak. Hopefully it will get even better as we move forward.

In order to do this, I would have to stop the mpdecision daemon (QualComm proprietary) and replace it with kernel level hot-plugging. I will likely do this in an experimental kernel to see how it goes. If it works well, then it's possible that I will come out with a 2nd kernel build and have it compete directly with this mpdecision controlled kernel to see how they stack up against each other, and versus stock.

Great, hopefully b48 will be able to stretch that a little further:)

Awesome, please do let us know how it goes.
[Nexus 4 Original Android Development] bamsbamx:
Motley, one thing about kernel, i have noticed that some videos have some frameskips with your kernel... I tried the same with franco kernel and i worked without frameskips, even with the same clock frequencies...

I want to use this kernel, because it has very good battery life... So please, could you fix this???

I guess that it can be I/O scheduler although i am not sure...
[Nexus 4 Original Android Development] dwang:
Build 48 deep sleeping really nicely.

Only lost two percent after 7.5 hours.
[Nexus 4 Original Android Development] Rafase282:
I just flashed build 48 and I noticed that the min goes to the 1.02 frequency but unlike before it goes back to the min frequency I set up. That is great. Thanks for the kernel. Still my favorite across devices.
[Nexus 4 Original Android Development] _motley:
Great, mine is performing efficiently so far as well. I am running 304 at 700mV today to see how it goes.

Hi, awesome to see you here with an N4:) Glad it is running well for you.

If you can provide a link to a vid or site that can duplicate the issue, I will have a look. Also, which apps are you using that show the issue? (Youtube, Gallery or some other app?) I haven't done anything to the GPU, so that part of the kernel is stock. If you are reading a large video off the SSD, the io scheduler could be involved. I did make some tweaks to the SIO in one of the builds. We can try the build before this to see if it worked better before that. Also, if you can test with different CPU govs (interfactive vs OnDemand) and IO schedulers (Deadline vs SIO), that would be helpful to see if you notice anything different. Thanks.
[Nexus 4 Original Android Development] dwang:
Any chance of decreasing PHY_SUSPEND_TIMEOUT_USEC to 100 to save even more battery life? I didn't have any issues running franco and faux's kernels with those values. I like your kernel the best though.
[Nexus 4 Original Android Development] UZ7:
So far with my 7hr day I didn't use the phone much only 10min screen time lol but my audio recorder was on for lectures and that was on for about an hour so right now I'm at 87% which isnt bad at all! :good: this is on build 48

Previous two builds were averaging me 15hr~ with 3-4hr screen time. Most of the time I leave my data on unless I'm at home which then i switch to wifi.
[Nexus 4 Original Android Development] siberian85:
What app to use to control this kernel
[Nexus 4 Original Android Development] JmPTaz09:
In just leaving everything at defaults and it's smooth, fast and conserving battery well. If you wanna play around with stuff (which a lit if times has a negative impact, though i do play around once in awhile as well), you can use any. System Tuner is a good one and i believe most if not all should work, such as no frills CPU, setcpu, etc.

He's got it set up pretty damn well right out of the box I must say. :beer:
[Nexus 4 Original Android Development] UZ7:
Theres a few apps out there that can control whatever depending on what you want (overclock, voltages, governor, io schedulers etc..) I personally use system tuner, only thing is have to make sure you're stable stable if you want to apply on boot, if you have unstable values it could cause bootloops or soft brick.
[Nexus 4 Original Android Development] sideeffects:
It's strange I get defaults of

304000, 725000

486000, 875000

594000, 900000

702000, 925000

810000, 937500

918000, 950000

1026000, 962500

1134000, 975000

1242000, 987500

1296000, 1025000

1404000, 1037000

1512000, 1050000

They are displayed with Android Tuner which is in beta (same devs as system tuner). Data and cache of the app were cleared, no boot settings used, no other control software installed. Cache and dalvik cache cleared on kernel install.

Is it possible that a script is messing with the defaults? If so where would it likely be as I don't have an init.d folder.

Edit - Do all Nexus 4 phones in world have the same stock voltage?
[Nexus 4 Original Android Development] whittikins:
Mine also has these voltages by default on Motley build 48.
[Nexus 4 Original Android Development] aventu:
Faux123 Kernel App is an often updated tool and specially made for the N4.
[Nexus 4 Original Android Development] bamsbamx:
Okay, here is the video http://m.vitalbmx.com/videos/featur...aign=Feed:+vitalbmx/aIrF+(Vital+BMX+Homepage)

Clicked on hd version, played online and downloaded (long press, save link). Always with stock gallery app.

Underclocked 300-1200. Tried with ondemand and interactive.... Interactive has less frameskip.... But it is still frameskipping a bit. Build 48

I tried with deadline and sio, no differences...
[Nexus 4 Original Android Development] :
Hi,

Ok, thanks for the feedback I'll try and see (weird, I never thought of that). I currently use 2 minimum online cores. But maybe that with my agressive Interactive governor settings it will be even less battery friendly to run all the cores online :D.

Maybe switching between from 2 cores online to 4 cores online (depending on the use / load) consume more battery than to keep the 4 cores always online :confused:, if you see what I mean...? More cycle to switch on / off the cores... But it's what Hotplug stuff is supposed to do...

Also need to see about heat... But maybe all cores online needs lower CPU freqs than only 2 cores online at higher CPU freq (always depending on the use / load).

I don't know if I explain right what I mean :eek: :crying::D:D:D

I'll try, feedback later... :)
[Nexus 4 Original Android Development] Spec-Chum:
Hmm, interesting, I think I may test this too.

Would I be correct in assuming that even before going into deep sleep it goes down to 1 core when screen is off regardless of minimum core setting?