yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Original Android Development] intersectRaven:
It's all up to you. Interactive is more updated though by Google. :)
[Nexus 4 Original Android Development] kaiser_tytnii:
Great addition to nexus 4 Dev team IR! I still remember the old day when I used to refresh your kernel page for nexus 1 every hour or so lol
[Nexus 4 Original Android Development] jairmoreno:
Hi intersectRaven,

I don't know much about kernels, but it seems that Showp found an error in thermal managment in stock kernel.

And 2 or 3 posts later in Franco's forum he said

I don't know if it is fixed in your kernel.
[Nexus 4 Original Android Development] jassycliq:
Bluewall didn't find anything. He's talking about the work that showp did on his kernel.
[Nexus 4 Original Android Development] intersectRaven:
Thanks for pointing that out. I noticed that before but ignored it because I was confused by the commit message and didn't think it was important. I'll try that in my future test kernel. :)
[Nexus 4 Original Android Development] jairmoreno:
Yep that's correct, I fixed alredy.

No problem, your kernel rocks so I only want to have a perfect kernel :p
[Nexus 4 Original Android Development] elk80:
Can you please make it compatible to faux' gamma adjusting?

That we can callibrate the screen?
[Nexus 4 Original Android Development] Sean09:
I decided to try this kernel with the current AOKP release (4.2). It works well and has great battery life, except for the fact I experience severe lag any time I try to turn on the phone to actually use it. Ie I turn screen on, and for a good 20 seconds or so the phone lags and takes a while to do anything. Once it "wakes" and has that time, it is really smooth. Anyone else have this?
[Nexus 4 Original Android Development] Harsh:
Hi, I was huge fan of your N1 kernel. And glad to have you back after long time. :D..

And that sensor commit is to disable thermal sensor. If you set it to 0, its disabled.

Temperature sensor for cores are as follows 7, 8, 9, 10.

7 being for cpu0 and other for cpu1, cpu2 and cpu3 respectively.

morfic and franco disabled thermal sensor because they wanted msm_thermal control from within kernel, and did not want thermald binary to have any impact on it. While if showp did make it 0, maybe its for his special inkernel implementation of temperature control.
[Nexus 4 Original Android Development] intersectRaven:
Hmmm...so if it's set to 0, thermald is disabled and msm_thermal is enabled? When I set to 0 and debugged there was no change and thermald is enabled while msm_thermal is disabled. Only when I removed thermald from starting in .rc did msm_thermal go up. :confused:
[Nexus 4 Original Android Development] Harsh:
I guess I did mistake. somehow sensor 0 is also active. And for disabling thermald only way would be to rename/remove it completely or remove it from ramdisk
[Nexus 4 Original Android Development] JmPTaz09:
Trying out 1/8 test build... Hoping for no data drops :eek:

So far so good!
[Nexus 4 Original Android Development] :
m2 with 1/8 build - the funny thing is, I've never faced any data drops with your earlier builds :)
[Nexus 4 Original Android Development] smirkis:
its iR! this guy is a genius, and made the best kernels possible on the kindle fire! glad to be able to take a swing at your kernels here on the N4, i barely rooted it yesterday after owning it for a month so i get to play catchup with all these fun tweaks, thanks again iR!
[Nexus 4 Original Android Development] JmPTaz09:
So far no data drops today (at least not while I was using the phone - I have had them on various other kernels, possibly including past versions of this one). So nothing at all to complain about; everything running smoothly! Running it with slim bean (jb version).
[Nexus 4 Original Android Development] intersectRaven:
It's not just data drops you should watch for. Also the random restart of the phone modem (which could be easily seen if you have a mobile PIN). Anyways, I've already had that just a few minutes ago so I'll have to revert something again. :p
[Nexus 4 Original Android Development] undercover:
Have you tested new modem image?

Sent from my fridge. Make:LG Model:N4
[Nexus 4 Original Android Development] intersectRaven:
What new modem image? :confused:
[Nexus 4 Original Android Development] jarjar124:
exactly...i can't find it

edit: i think it is this http://xdaforums.com/showthread.php?t=2087227 bb33
[Nexus 4 Original Android Development] intersectRaven:
But .33 is the stock image so it isn't "new"... :confused:
[Nexus 4 Original Android Development] JmPTaz09:
I didn't have any data problems, ran 1/8 test build on slimbean all day. Cannot attest to any random restarts of the modem... I don't use a lock screen or pin, but I did not notice any restarts... Working pretty well; keep fine tuning! :beer:
[Nexus 4 Original Android Development] Junglist86:
Hallo,

There are 2 stable Version of this kernel, i use aosp (cm) and flashed the "cm10.1" Version, a another member has the paranoidandroid rom (based on aosp) and he flashed the "JB" Version and it works to?! What is the difference of this 2 version?!

Thank you :)

Gesendet von meinem Nexus 4
[Nexus 4 Original Android Development] intersectRaven:
Just the ramdisk. Since CM hasn't diverged yet from AOSP, they're really close still so they still work. :)
[Nexus 4 Original Android Development] :
20130108_22XX is/was absolutely stable incl. data.

Now I'm testing the brand new 20130109_22XX.

Does reverting all the USB things mean, the fantastic low battery consumption (deep slepp >>90%) will be history? :confused:

Keep on developing this fantastic kernel! Thanks !!!!
[Nexus 4 Original Android Development] intersectRaven:
Don't worry about it. The deep sleep issue is a different set of USB commits which are stable as they are. The USB commits I've been focusing on are extremely minor in comparison. :)
[Nexus 4 Original Android Development] :
Good to hear :thumbup:

Gesendet von meinem Nexus 10 mit Tapatalk 2
[Nexus 4 Original Android Development] smirkis:
what governor do you recommend iR? or which one have you tweaked to your liking the most?
[Nexus 4 Original Android Development] rossbeck:
I'm curious about this too...

What other settings is everyone using?

Using SlimBean ROM, 1/8 iR build, I have my Trickster Mod settings @:

Min: 384mhz

Max: 1512mhz

Interactive governor (stock settings)

Read ahead buffer size 1024 (I've heard people like 2048?)

Colors R255, G249, B234

Set on boot: ENABLED

Anyone have different recommendations? Like everyone I'm going for the best battery life while keeping things running smooth.
[Nexus 4 Original Android Development] grisha1:
Fantastic kernel. Smooth like no other, good on battery, good with signal 3G.

A big thank you :thumbup:
[Nexus 4 Original Android Development] rossbeck:
Anyone? Bueller?
[Nexus 4 Original Android Development] JmPTaz09:
Stock settings with interactive and bfq work well.
[Nexus 4 Original Android Development] kevinnol:
Im using Interactive+ROW

If you want to save more battery try to change the highspeed freq to 918 or min samplingtime/timmer rate a little

higher timer or lower min sample.. saves battery

-----

20130108_22XX is Stable but had some data issues didn't test the newest TESTkernel though
[Nexus 4 Original Android Development] elk80:
why can I not adjust the gamma values in faux' app?

It works with the stock kernel but not with yours. :(
[Nexus 4 Original Android Development] Rod3:
Gamma values can only be adjusted using Faux's kernels and his app.

IR, tried the latest 1/11 test kernel and was working phenomally, except for GPS. I couldn't get a lock indoors. Reverted to your 01/09 test kernel and all is well.
[Nexus 4 Original Android Development] elk80:
No. I tested it on stock kernel and it worked too.
[Nexus 4 Original Android Development] rossbeck:
I don't think I've ever gotten a GPS lock indoors unless I was standing next to a window. Just tried mine right now at work and it's not getting a lock indoors on 1/9 (granted, I'm in the middle of a giant concrete shipping warehouse).
[Nexus 4 Original Android Development] Rod3:
Stock, or Faux's modified stock? From everything I had read, only the color values could be changed and not the gamma unless using Fauxs kernel.
[Nexus 4 Original Android Development] ctfrommn:
Stock and Faux's modified stock both are changeable with his app.
[Nexus 4 Original Android Development] Rod3:
I sit right next to a window at work, and it locks within 5-8 seconds on 01/09 but not at all on 01/11.
[Nexus 4 Original Android Development] elk80:
The normal stock kernel.
[Nexus 4 Original Android Development] v3rk:
Just checking in to give my amazing experience with Jan 1 stable kernel. Been up for 240 hours, absolutely rock stable. Great battery life, I stream a lot of Pandora and can easily get 9 hours with two hours screen on time to boot. I never turn off data or sync, and rarely use Wi-Fi. Thanks for the amazing kernel IR!

---------- Post added at 08:25 PM ---------- Previous post was at 08:21 PM ----------

Forgot to mention that performance tops stock kernel. Everything is smooth as can be. I compare against my wife's n4 and am amazed. So much more satisfying than other custom kernels I have tried which always stutter and hiccup. I run stock rooted ROM.
[Nexus 4 Original Android Development] Rod3:
Clean wipe and using the latest unofficial AOKP, 01/11 Test Kernel is now getting a GPS lock indoors. Awesome kernel. Stock settings and getting Linpack scores of 204-208. Thanks IR!

On your 01/09 test kernel, I got 30 hours use with just under 3h screen time. Now that GPS is not a factor, lets see what I get out of the 01/11.
[Nexus 4 Original Android Development] JmPTaz09:
Running the 1/11 test build on Asylum ROM (CM based). No GPS issues, seems fast and smooth on interactive & row. Bumped read ahead value to 2048. I just flashed so I'll run it all day tomorrow to test stability, speed and battery life. :beer:
[Nexus 4 Original Android Development] Pedro Peguero Jr.:
When will there ever be another "stable" release?
[Nexus 4 Original Android Development] JmPTaz09:
Just use the test kernel; it's as stable as any kernel on xda and I've tried them all :thumbup:
[Nexus 4 Original Android Development] intersectRaven:
I'll probably be upgrading the latest TEST to STABLE status since there's been no data drops on my end together with GPS functionality. I am concerned about slimport though but since that's a limited audience, I'm inclined to ignore the possibility of problems with it for now. :)
[Nexus 4 Original Android Development] Pedro Peguero Jr.:
:thumbup:
[Nexus 4 Original Android Development] kaiser_tytnii:
Agree, so far its been the best kernel I have ever used for nexus 4 for the past 6 hours, will report with battery usage after full charge tomorrow, thanks IR!! You surprised me again since nexus 1!!!
[Nexus 4 Original Android Development] kaiser_tytnii:
But full day experience show me something else, unfortunately...

3g only, all sync on including all location settings and latitude:o

Edit: was on latest test kernel
[Nexus 4 Original Android Development] intersectRaven:
I think that's expected since everything's on. In my case I can go well over that with 3g data up although I only have default sync settings. :)
[Nexus 4 Original Android Development] JmPTaz09:
Looks like he was getting E (edge) service based on screen shots; poor reception could be responsible for that less than stellar battery life.
[Nexus 4 Original Android Development] kaiser_tytnii:
Only got that for 2 minutes

Not sure if this is gonna help but here is my last_kmsg

http://db.tt/OPM9iTPM
[Nexus 4 Original Android Development] phewizzo:
Most stable and smooth kernel Ive used and Ive tried then all. Simple is better.
[Nexus 4 Original Android Development] :
IR's latest exp version 3.4.26_CM10.1_20130118_1704 is even better! :)

Thx IR :thumbup:
[Nexus 4 Original Android Development] elk80:
Has this kernel init.d support?
[Nexus 4 Original Android Development] trismegistos:
AW: [KERNEL]intersectRaven's Kernel - 20130116_22XX

Yes
[Nexus 4 Original Android Development] JmPTaz09:
Re: [KERNEL]intersectRaven's Kernel - 20130116_22XX

True, seems fast and smooth. :thumbup:
[Nexus 4 Original Android Development] eservant:
Outstanding kernel. wakelocks gone, deep sleeps after charge without rebooting, and excellent battery life.

Running on slim 4.2.1 beta2.

edit: Link in op is down
[Nexus 4 Original Android Development] intersectRaven:
Re: [KERNEL]intersectRaven's Kernel - 20130118_17XX

Link updated. :)

*side note:

Can everyone post their current kmsg? I'm looking at something which could lower consumption but might not actually be used currently. :)
[Nexus 4 Original Android Development] TobiS87:
Dunno if I've done that right. Never needed to get a kmsg... :D
[Nexus 4 Original Android Development] intersectRaven:
Thanks you did it correctly although I'd appreciate it if you can get one after you've used it for awhile and preferrably after some time idle so I can see what states it uses. :)
[Nexus 4 Original Android Development] eservant:
Re: [KERNEL]intersectRaven's Kernel - 20130118_17XX

Please excuse my ignorance but where is kmsg located.
[Nexus 4 Original Android Development] intersectRaven:
If you're not comfortable with the terminal or running adb, please pass on this. It is fine. :)
[Nexus 4 Original Android Development] schizophrenia:
correct me if I am wrong, you can get it using Root explorer or equivalent to copy and paste it from, under the root directory /proc/kmsg
[Nexus 4 Original Android Development] TobiS87:
AW: [KERNEL]intersectRaven's Kernel - 20130118_17XX

OK. Gonna get it again this evening.
[Nexus 4 Original Android Development] JmPTaz09:
Re: [KERNEL]intersectRaven's Kernel - 20130118_17XX

1/20 build is super slick on interactive and row. :beer:
[Nexus 4 Original Android Development] TobiS87:
AW: [KERNEL]intersectRaven's Kernel - 20130118_17XX

I second that. Battery seems great too with CM10.1. Had to reboot once today because something was killing my battery but since then it is really running well!
[Nexus 4 Original Android Development] oo03sjw:
Xylon

Which version for Xylon ROM please?

Is there a Fast Charge option?

Many thanks as always.
[Nexus 4 Original Android Development] TobiS87:
So. This is the kmsg after the full day. Long idle periods while I was working.
[Nexus 4 Original Android Development] eservant:
Build 18_17xx running on slimbean 4.2.1 beta2 for almost 2 days after a couple of hrs of idle time.
[Nexus 4 Original Android Development] Luigi_2:
performance is excellent, no doubt. But the cellunar connection is bad, when I was on wifi and turn off wifi, there's no connection 2g, 3g. Dont know if this's a known issue, sorry
[Nexus 4 Original Android Development] mykenyc:
Re: [KERNEL]intersectRaven's Kernel - 20130118_17XX

What's row?
[Nexus 4 Original Android Development] mko000:
It's an IO scheduler: ROW - Read Over Write. Google it.
[Nexus 4 Original Android Development] mykenyc:
Thanks, my first time hearing about this IO scheduler, will try it out.
[Nexus 4 Original Android Development] kaiser_tytnii:
Re: [KERNEL]intersectRaven's Kernel - 20130118_17XX

New thing from Qualcomm:D
[Nexus 4 Original Android Development] phewizzo:
Re: [KERNEL]intersectRaven's Kernel - 20130118_17XX

I hate how quiet this thread is, I guess when the kernel is good with no problems theirs no need to comment haha. Patiently waiting on your next masterpeice IR.
[Nexus 4 Original Android Development] intersectRaven:
I'm actually taking the time to rebase from scratch again to see if I missed anything. :D Besides, I've been researching something for power and speed which should be *interesting*. ;)
[Nexus 4 Original Android Development] franciscofranco:
If you beat me to it (is this what we talked about?) I'll kick your arse :D
[Nexus 4 Original Android Development] intersectRaven:
I was supposed to work on that but since you've already started, I fell back to something else I was looking at which *should* help even more once you finish yours. :D
[Nexus 4 Original Android Development] franciscofranco:
I haven't started it yet, plan to do so next week, impossible earlier time-wise :)
[Nexus 4 Original Android Development] intersectRaven:
I can wait. :p I don't like reinventing wheels. :D
[Nexus 4 Original Android Development] Rod3:
IR, I see you have a new test kernel (1/25) but there is a file labeled "do not use" lumped in with the CM/JB variants.

Are these new kernels unusable?
[Nexus 4 Original Android Development] phewizzo:
Re: [KERNEL]intersectRaven's Kernel - 20130118_17XX

Ive been wondering the same thing.
[Nexus 4 Original Android Development] intersectRaven:
As I said in my previous posts, if I don't post in the OP or the TP, it's highly experimental. The fact that I also put a DO NOT USE file to indicate means this is EXTREMELY HIGHLY DANGEROUSLY EXPERIMENTAL so it's not for use. I only put it there since I frequently recompile and my script destroys any zip in my output folder so I put it there for future reference and possible comparison purposes. :)
[Nexus 4 Original Android Development] franciscofranco:
Following your first PM about the Power States I merged a few commits to pm-8x60.c from msm-3.4 codeaurora's branch (I already had the support for Power Retention as you know). I compiled a kernel with FTrace enabled and I ran the trace while using the device. If you want to try it yourself here is a very good text explaining how to run the trace: http://lwn.net/Articles/365835/ . In the trace the low_power function was called a bunch of times and my screen was always on. So, with my understanding the power states are being reached:

<idle>-0 [001] d..1 174.736945: msm_rpmrs_enter_sleep <-msm_pm_idle_enter

<idle>-0 [001] d..1 174.736945: msm_spm_l2_set_low_power_mode <-msm_rpmrs_enter_sleep

<idle>-0 [001] d..1 174.736945: msm_spm_dev_set_low_power_mode <-msm_spm_l2_set_low_power_mode

<idle>-0 [001] d..1 174.736945: msm_spm_drv_set_spm_enable <-msm_spm_dev_set_low_power_mode

<idle>-0 [001] dN.1 174.738044: msm_rpmrs_exit_sleep <-msm_pm_idle_enter

<idle>-0 [001] dN.1 174.738044: msm_spm_l2_set_low_power_mode <-msm_rpmrs_exit_sleep

<idle>-0 [001] dN.1 174.738074: msm_spm_dev_set_low_power_mode <-msm_spm_l2_set_low_power_mode

<idle>-0 [001] dN.1 174.738074: msm_spm_drv_set_spm_enable <-msm_spm_dev_set_low_power_mode

static int msm_spm_dev_set_low_power_mode(struct msm_spm_device *dev, unsigned int mode, bool notify_rpm) -> this is called as you can see and that function receives the new mode as a parameter and sets it.

Can you reproduce this with your unpatched kernel?

EDIT: Seems like retention for example is not supported on any state besides idle:

[MSM_PM_MODE(0, MSM_PM_SLEEP_MODE_RETENTION)] = {

.idle_supported = 1,

.suspend_supported = 0,

.idle_enabled = 0,

.suspend_enabled = 0,

},

Its supported but not enabled? Suspend = hotplug || screen off? Idle means screen on but just idling there with no task? If the later is true do we really need hotplugging (as expensive as it is)? This should be fun :)

EDIT2: Maybe try disable hotplugging entirely and rely only on retention during idle (as far as I can understand they mean idle as idling on screen on, not on suspend(screen off).

/*

* If retention is being disabled, wakeup all online core to ensure

* that it isn't executing retention. Offlined cores need not be woken

* up as they enter the deepest sleep mode, namely RPM assited power

* collapse

*/

Then rely on suspend to power collapse all cores.
[Nexus 4 Original Android Development] intersectRaven:
I've already debugged it extensively. I've managed to activate retention by "fixing" a few values but it keeps getting overriden by power collapse due to the power of collapse being less than retention.:confused:
[Nexus 4 Original Android Development] franciscofranco:
Can you pastie.org what you did? Mine and morfics idea is to get rid of hotplug entirely and rely only on power states. Unfortunately this crap isnt activated unless the cores are on/off so I'm forcing retention to be set all the times on all cores as a test.
[Nexus 4 Original Android Development] intersectRaven:
Here's a pastie of what I did: http://pastie.org/5873351

It has a few unnecessary parts since I haven't finished the cleaning of my source so I just patched everything there and removed most there in the pastie. :)

In essense, I just multiplied the latency_us by 1000 so that when it reaches the lowest_limits method, it will process successfully without leaving rs_limits NULL.
[Nexus 4 Original Android Development] franciscofranco:
Thats intelligent, but I'm doing something different. I'll share when I have more info.
[Nexus 4 Original Android Development] intersectRaven:
That's fine. I happened to chance about it while learning more about what I'm going to implement when I finish with my source maintenance. :)
[Nexus 4 Original Android Development] franciscofranco:
Why would you want retention on screen off by the way? Power collapse is lower state so it will consume less energy than retention as far as I can understand. Retention will be useful on screen on if the cores are online.
[Nexus 4 Original Android Development] franciscofranco:
System crashes if all the cores enter in retention mode just like they wrote in the commit message about hardware restrictions. So power retention is basically useless unless all cores are offline (besides cpu0 of course).
[Nexus 4 Original Android Development] intersectRaven:
Just doing some experimenting on some things. I don't really need retention. It's just something I wanted to look at. :)
[Nexus 4 Original Android Development] phewizzo:
Re: [KERNEL]intersectRaven's Kernel - 20130118_17XX

New test kernel is running smooth. I will comment on 3G battery life tomorrow. Thanks for the new features IR.
[Nexus 4 Original Android Development] :
AW: [KERNEL]intersectRaven's Kernel - 20130118_17XX

+1
[Nexus 4 Original Android Development] mykenyc:
Re: [KERNEL]intersectRaven's Kernel - 20130118_17XX

I don't know if I'm bugging, but the latest test kernel makes me phone feel cooler, literally. Like, the phone don't have a warm spot on it anywhere.
[Nexus 4 Original Android Development] intersectRaven:
I think it's because the upstream commits I've been merging are making the kernel more efficient...but that's just wishful thinking without any hard evidence... :p
[Nexus 4 Original Android Development] JmPTaz09:
Re: [KERNEL]intersectRaven's Kernel - 20130118_17XX

Confirmed that everything seems pretty smooth on 1/28 test kernel. Haven't been in it long enough to comment on battery, but no problems with it so far. Running interactive and deadline.
[Nexus 4 Original Android Development] intersectRaven:
Just an update. Sorry for the wait! I'm almost finished with the review of my commits. There's a ton of changes from upstream mostly! :) If you want to use it now, it's stable already BUT I haven't committed the msm_hsic fix by Qualcomm yet as it's still pending review. If you're fine with that, it can be found in the 2.6.38 branch on my FTP site. :)
[Nexus 4 Original Android Development] phewizzo:
Re: [KERNEL]intersectRaven's Kernel - 20130118_17XX

Cool I will dl and try. How long do you think it will take until the HSIC fix will be reviewed?
[Nexus 4 Original Android Development] intersectRaven:
I can't say. I should be finished by Monday so expect a new AND better stable kernel by then. :) I've deployed improved fixes to the thermal regulation driver by Qualcomm which I found from CodeAurora in that latest one by the way so it should react faster to heating up while in use. Can't guarantee that from experience though as I rarely play games on my N4. :)
[Nexus 4 Original Android Development] Junglist86:
With interactive ("boost" ist activate in Trickster mod) and row a absolutly simple, smooth running Kernel! No freezes, no new boots or something! Perfomance is amazing, and this is my first importend requirement on a kernel! battery life is for me not so importent than the perfomance. 22-23 h with 2-3 h screen on its enough for me :)

very good job :)

Soon (in 2 weeks when i get my money from work :D) there is definitely a donation from me!