yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Original Android Development] chappy824:
If you dirty flash your ROM then flash matr1x it will work fine.

---------- Post added at 09:26 PM ---------- Previous post was at 09:25 PM ----------

Use no frills app to set freq. Then apply changes
[Nexus 4 Original Android Development] 3dawg:
Thanks. Any idea about the first part?
[Nexus 4 Original Android Development] SA-07:
I'm going to talk to showp about this. I've also heard the same problem exists in the faux kernel. Let me see what I can do.

For those of you having problems with s2w, just disable it for now and as I said I'll talk to both faux and showp.

Sent from my Nexus 4
[Nexus 4 Original Android Development] SA-07:
Other than the s2w, how's the kernel? I'm going to work on getting even more battery life.

Sent from my Nexus 4
[Nexus 4 Original Android Development] Simer03:
Very responsive and no lag anywhere so far...recents button transitions are smooth and no lag when pressing the button

Edit: sod just happened

Sent from my Google Nexus 4
[Nexus 4 Original Android Development] 3dawg:
After using the kernel for a while and keeping an eye on CPU spy, it seems that the ramp up freq on touch events is affected. It doesn't automatically jump to 1GHz when starting touch events any more. Is there a reason for this? And does this kernel break any other Project butter tweaks?

Other than that, the Kernel is running beautifully now. Thanks.
[Nexus 4 Original Android Development] chappy824:
I don't have that issue...can you try to dirty flash your ROM then matr1x to see if that fixes it.
[Nexus 4 Original Android Development] 3dawg:
That was the first thing I did :p So are you saying that the touch event freq scaling is working for you?
[Nexus 4 Original Android Development] chappy824:
Yes...its definitely working right. I'm on stock rom and its good.
[Nexus 4 Original Android Development] evostevo1:
The kernel itself is pretty smooth and fast.
[Nexus 4 Original Android Development] chappy824:
UV too far?
[Nexus 4 Original Android Development] Stryder5:
I'm also getting the unresponsive lock screen with s2w enabled. Running Paranoid Android Beta 9.5.
[Nexus 4 Original Android Development] JmPTaz09:
Kernel seems really smooth on today's CM nightly, using V4.5. Scrolling on xda app even seems less choppy. :beer:
[Nexus 4 Original Android Development] whittikins:
Any chance of implementing Faux's gamma controls?
[Nexus 4 Original Android Development] cruizgaray:
I'm using this kernel with PA (last version too) and swipe2wake works just perfect!!!

Thanks Mathkid

Enviado desde mi Nexus 4 usando Tapatalk 2
[Nexus 4 Original Android Development] ichbinich:
Me too! :(
[Nexus 4 Original Android Development] SA-07:
Oh no! Look a few posts above you!

Sent from my Nexus 4
[Nexus 4 Original Android Development] paratox:
one of the fastest N4 kernels out there!

thanks for this fantastic kernel mathkid95! :)
[Nexus 4 Original Android Development] SA-07:
Yeah, I hope he releases the sources soon! :)

Sent from my Nexus 4
[Nexus 4 Original Android Development] Harsh:
Faux say he will not release his sources because of some trouble, he would however provide libs if kernel devs ask him. Those binaries would enable gamma control. Maybe it's time u pm him :)

Sent from my Nexus 4
[Nexus 4 Original Android Development] jarjar124:
Have you harsh? :p
[Nexus 4 Original Android Development] Higgsy:
My experiences with 4.5

Deep sleep issues - With sweep2wake enabled the CPU was locking at 1026MHz rather than sleeping. Noticed it over night when I got a 25% battery drain in 7 hours with data/wifi switched off. Switched off sweep2wake and it the freq would then drop to 288MHz but again would not deep sleep. Redownloaded and reflashed and still same behaviour. Also noticed it doesn't seem to be using all freq steps. 288/1026/1350 are all I am seeing utilised. Rolled back to 4.0 and everything is back to normal and behaving as expected.

Settings:

No change to voltage

Max 1350MHz

Min 288 MHz

Ondemand Gov

ROW scheduler

Latest PAOSP ROM

Checking with TricksterMod
[Nexus 4 Original Android Development] m_zet:
Kernel 4.5 on Xylon 14 stable (02-01-2013) runs GREAT!

No problem with sweep4wake (with deepsleep) or lockscreen unlock. Everything smooth - I did not UV though and did get back to stock kernel from faux123 and than from stock to matr1x 4.5.

Keep up ULTRAMEGA splendid WORK!
[Nexus 4 Original Android Development] Higgsy:
Following on from my previous post above...The fact that no one else is reporting these issues and someone has confirmed no deep sleep issues...

I flashed 4.5 over 4.0 and it is behaving normally now, sleeping ok etc... I had originally flashed 4.5 at the point of flashing the lastest PAOSP. As I said before I even redownloaded/reflashed 4.5 and was getting the same behaviour. So some how flashing over the top of 4.0 has resolved my issues - oh well this isn't the first time something weird and unexplainable has happened while flashing ROMs/Kernels on an android device and I'm sure it won't be the last:silly:
[Nexus 4 Original Android Development] hicks12:
I don’t know what I was expecting from sweep2wake however I am finding it a lot less useful than expected :P, my thumbs aren’t long as it requires far too much stretching to even be useful as I had hoped it would improve one handed usability, the best thing they could do is implement a vertical down or up motion or draw a U gesture, would be awesome then. However it is nice when using two handed so I will keep it enabled for now.

mathkid, the kernel is simply blowing my mind atm.. I was disappointed with idle performance on stock rom/kernel and your kernel along with rasbean rom has drastically improved this, over the last few days it has gone even better, I haven’t really used my phone that much as it’s still the holiday and it tends to be on my desk next to my router so I have it on Wi-Fi all the time (Wi-Fi on my O2x drained battery like no tomorrow!) now my phone which had better battery performance was the O2x but it was fairly slow so I didn’t find myself wanting to use it for much, it generally was just used for emails and important quick browsing and a few texts. I have now used my N4 in a similar way over the few days and I can now safely say the performance is way better than my O2x :).

I have changed kernels(v4.0 to v4.5) during this battery unintentional test and I am leaning towards v4.0 being better on battery, there is no explanation as my voltages are exactly the same ( -137.5mV undervolt on every level apart from 288Mhz step which is -162.5 mV undervolt) yet battery is draining slightly quicker, maybe missing something really obvious so apologies if I have! My only real theory is the processor is ramping up far too high, project butter doesn’t seem to work correctly? I recall when touching the screen on v4.0 that it would ramp up cores to 1.02Ghz (was it one or two cores?) but in v4.5 its ramping up core 0 and 1 to 1.02Ghz, however core 1 then immediately goes up to 1.5ghz and takes a few seconds to ramp back down so it seems to me as extra cores aren’t locking to the same 1.02ghz speed they are meant to, could be totally off the mark here though :P.

Anyways here’s the screenshots, like I said haven’t used it that much but essentially it was this:

Few text messages

Email accounts - 2 Sync @ 1 hour intervals, 1 Syncs @ 30min intervals

Pulse news app - 6 hour syncing with notification and refreshing on load - Read a few stories on here

Browser - Browsed a few websites probably about 20minutes

tapatalk - about 30 minutes total

Few photos

Uploaded a couple photos and downloaded a few files off dropbox

a handful of benchmarks

Thats mostly it, as you can see from the graph there is a massive drop and that is simply when I flashed version 4.5 (didnt a couple flashes...) every boot made me lose a lot of battery percentage so I think in total I lost 20 % in that space of time :P

Now I will be doing a proper test, charging to 100% going in airplane mode and just looping a video and see how long it dies, be interesting to see if there is a big difference :).
[Nexus 4 Original Android Development] janjan:
Nice kernel ...great job thanks. Really like the sweep2wake. Thanks very useful
[Nexus 4 Original Android Development] nellisere:
Just about to flash this Kernel, how would I go about disabling Sweep2wake? Can I disable it using FauxClock?
[Nexus 4 Original Android Development] Higgsy:
Had 2 instances of the phone not accepting and touch input on 4.5 in the last hour -having to reboot via holding power down. 4.5 really doesn't like me:eek: I'll see about getting logs
[Nexus 4 Original Android Development] robs898:
Wow i'm on the same setup as you with RBJ rom. This is very helpful thanks!
[Nexus 4 Original Android Development] chappy824:
Not sure as I don't have that app...you can use trickster or sweep2wake widget.
[Nexus 4 Original Android Development] Higgsy:
It can be disabled not 100% on faux app but I think I have seen post where people have disabled it in the Bricked thread using that. Definitely an option in trickstermod.
[Nexus 4 Original Android Development] Stryder5:
Do you have S2W enabled? If so, disable it.
[Nexus 4 Original Android Development] nellisere:
I can see that you have to donate to get frequency lock, does that mean that min and max settings and sweep2wake options don't stick on reboot?
[Nexus 4 Original Android Development] robs898:
Ignore
[Nexus 4 Original Android Development] hicks12:
its disabled by default :).
[Nexus 4 Original Android Development] Higgsy:
Yeah cheers - Already done.
[Nexus 4 Original Android Development] SA-07:
I will add the s2w touch gestures in the next update.

I've already fixed the battery issue which will also be in the next update (fix).

Sent from my Nexus 4
[Nexus 4 Original Android Development] kennyp987:
This kernel runs like a dream but my touchscreen wasn't getting any input response multiple times and only works when i force a reboot...
[Nexus 4 Original Android Development] SA-07:
How many times do I have to quote the same thing? Lol

Sent from my Nexus 4
[Nexus 4 Original Android Development] kennyp987:
I never enabled it bro and I'm assuming its disabled by default....i have no app installed to enable or disable the feature which is why i am confused
[Nexus 4 Original Android Development] chappy824:
Did you come from another kernel? Its almost a must to either do a clean install of ROM then kernel or do a dirty flash of ROM then kernel to be absolutely certain of kernel problems.
[Nexus 4 Original Android Development] Stryder5:
I think it's actually enabled by default on this kernel. Why don't you try swiping and see if you can lock your phone, or wake your phone?
[Nexus 4 Original Android Development] zimphishmonger:
Faux pretty much has a working solution. I was able to pull a log for a touch lockup, which started a fix, then a few others started having it, more fixing, etc.. Showp is also about to release s2w 2.0 soon, which could add something to the mix
[Nexus 4 Original Android Development] kennyp987:
i tried that it wasn't enabled
[Nexus 4 Original Android Development] bigmase521:
It was definitely enabled by default for me. Disabled in Trickster.

I'm also noticing the cores staying way too long at 1026 as someone mentioned earlier... Even though I have frequency lock enabled. Didn't see this behavior with 4.0 and below. Mathkid, what could cause this? Mpdecision tweaks?
[Nexus 4 Original Android Development] m_zet:
I am on Xylon Stable from 2-01-2013 and the mart1x 4,5 started to give me unresponse lockscreen after I sweep too many times.

So when I started to wake by sweeping with first attempt no luck, then second ok. Then I turned off and tried again.

I guess the kernel or s2w does not like when someone is playing with it. I just disabled it i Trickster.

And all ok.

I can confirm that by defauld s2w is ON/enabled.
[Nexus 4 Original Android Development] 320flyboy320:
I don't have lock screen enabled and s2w is woking great for me....thanks
[Nexus 4 Original Android Development] SA-07:
Sweep2wake is not enabled by default. You should wipe both cache and dalvik cache in order to make sure it gets registered in the applications (like trickster) and is shown as not enabled by default.

Sent from my Nexus 4
[Nexus 4 Original Android Development] hicks12:
Math mate I am going to have to say that so far v4.5 isn't as good as the v4.0 in terms of battery performance, using the phone similar as before I'm getting about 2.5x more idle battery drain, the following seem to have crept in betterbattery stats

Suspend back off

Power management service

Msm hsci host

Suspend back off is the highest at a considerable margin, I can only think sweep2wake or something else is causing this?. I will try it for another day wipe all my battery stats and charge up,will let you know tomorrow how it goes.

Oh and haven't really noticed any change in speed or nothing, guess the kernel is far to fast for any changes to make a difference haha. :)
[Nexus 4 Original Android Development] SA-07:
Ok, I said I was going to fix it. You can use v4.0.

Sent from my Nexus 4
[Nexus 4 Original Android Development] undercover:
Your battery stats get wiped automatically every time you charge your phone over 90 percent and take it off charger.
[Nexus 4 Original Android Development] klutch:
sorry for the noob question but since i have v4.5 i can flash it back down to 4.0? dosent do anything bad to it?
[Nexus 4 Original Android Development] zimphishmonger:
no issues whatsoever.
[Nexus 4 Original Android Development] klutch:
thnx bro bout to downgrade the kernel then :good::)
[Nexus 4 Original Android Development] hicks12:
Sorry must have missed your post there math just wanted to let you know :)
[Nexus 4 Original Android Development] oddfuturejoey:
Hey, I've never used a Matr1x Kernel before, so I wanted to ask because I'm a little confused:

When I click the download link in the OP, I can't find the 4.5 which is the one I need since I need S2W and the reverted touchscreen drivers.

I'd appreciate any help!

Thanks!
[Nexus 4 Original Android Development] webdo:
http://downloadandroidrom.com/file/matr1x/Nexus4
[Nexus 4 Original Android Development] meangreenie:
Having the reverted touch screen drivers stick on boot is glorious!!

wish 300 or 325 gpu frequencies were available though
[Nexus 4 Original Android Development] SA-07:
Been busy but v5.0 coming soon!

Sent from my Nexus 4
[Nexus 4 Original Android Development] qpqpqp:
I hate to be the person that ask about eta, but whats the ETA?
[Nexus 4 Original Android Development] Hrithan2020:
Then don't ask.:p

Buy I am sure we won't have to wait too long. :)

Sent from my GT-I9100
[Nexus 4 Original Android Development] Stryder5:
Two weeks.
[Nexus 4 Original Android Development] mackster248:
Probably a day.
[Nexus 4 Original Android Development] m_zet:
Got the news about S2W - by default it is disabled, but when you install Trickster it enables S2W after installation.

As the proof I disabled S2W in Trickster and then there was an update of it and then I was able to sweep to wake and I noticed that it was enabled by Trickster.
[Nexus 4 Original Android Development] Stryder5:
Just updated Trickster and my S2W stay disabled.
[Nexus 4 Original Android Development] oddfuturejoey:
So yeah I've had it happen 5 times now where I go to use S2W and my touchscreen stays completely unresponsive.

Had to hard reboot.

Sucks
[Nexus 4 Original Android Development] SA-07:
Sucks that you don't read.

Sent from my Nexus 4
[Nexus 4 Original Android Development] oddfuturejoey:
Hey man, that kinda sucks. I was just saying.

This forums gone to ****.
[Nexus 4 Original Android Development] SA-07:
What? That's not the point here.

Sent from my Nexus 4
[Nexus 4 Original Android Development] Simer03:
I'm on Franco right now but I'll be jumping to 5.0 as soon as its out...I still think this kernel is superior based off personal experience with them all

Sent from my Google Nexus 4
[Nexus 4 Original Android Development] Hrithan2020:
Hi mathkid95,

It seems that faux has updated his code for s2w, after talking to showp1984 to address many of the issues with s2w . [basically releasing all the touch events before enabling the interrupt request.] Till sweep2wake version 2, I hope this might fix some issues users are reporting and it is just a 1 line addition? Sorry if you knew about this already.

Hope you could include this. :)
[Nexus 4 Original Android Development] SA-07:
Sure, I'll test it! Thanks! :)

Sent from my Nexus 4
[Nexus 4 Original Android Development] aletto:
Is it possible for you to release a non-gpu-oc kernel version? I think that the N4 is more than powerful enough. After all, those extra 50 mhz are 12.5% of the standard clock, which is definitely a considerable amount.

edit: and does anyone know where to find the voltage control interface? I even searched for it in the nexus s forums but it seems to elude me.
[Nexus 4 Original Android Development] the1onewolf:
Knock knock.

Who's there?

An angry mob of over zealous jelly beans who are going to sucrose you to death and key lime your house.

:angel:
[Nexus 4 Original Android Development] SA-07:
You, sir, just made my day. :D

Sent from my Nexus 4
[Nexus 4 Original Android Development] Foxololo:
Reduced voltage CPU -50mV on all frequencies. Became noticeably less warm. In antutu 18,100 balls (before that it was not more than 17,200, probably prevented throttling). In stabiliti test 39 degrees after 10 minutes. When the voltage is at -25mv caught reboot.
[Nexus 4 Original Android Development] ceejay83:
+1 would like a stock gpu version also
[Nexus 4 Original Android Development] lwfb:
Would you mind sharing your values in SetCPU?
[Nexus 4 Original Android Development] Simer03:
Damn it...my phone rebooted and didn't boot up correctly and I had to hard reboot so my readings won't be accurate lol! I would have easily surpassed 4 hours on screen time tho!

Sent from my Google Nexus 4
[Nexus 4 Original Android Development] colobos:
I will give it a test soon but happy with stock just took these and this is on all stocks rom and kernel
[Nexus 4 Original Android Development] Higgsy:
Would be nice if we could get this at stock frequencies with the option to over clock. I personally like to just use a kernel out of the box and not mess with under/over clocking etc. I don't really need 1.7ghz myself. Maybe a version that runs at stock speeds and an over clock version would be a good idea.

Sent by Galaxy Note
[Nexus 4 Original Android Development] eep2378:
Personally I've always like ondemand/cfq combo. Make sure you set your minimum CPU step to 384. I always set my ignore nice load to "1". I Left powersave bias alone for now until we know more about how this chip will respond to certain tweaks :D YMMV ;)
[Nexus 4 Original Android Development] brianbgrp:
Anyone on this kernel still get the msm_hsic_host wake lock? I get it pretty heavy on stock...wondering if a new kernel will help. Trying to run stock a while for comparison basis later but this wake lock hurts
[Nexus 4 Original Android Development] eep2378:
It's here but I believe it's minimal compared to stock. It's only about 3 to 4%
[Nexus 4 Original Android Development] brainmaster:
Well that is cruel.

I also use only Trinity kernels, but you don't do stuff like that. Especially not in the kernel developer thread.
[Nexus 4 Original Android Development] lwfb:
So far I'm really pleased with this kernel, excellent job!

I'll be able to give better feedback after a full cycle, but from first impressions I can say that this is some fine work... Sips battery from what I can tell so far and there's been no decrease in performance.

Edit: This kernel flat lines while idle, it's a huge improvement over stock. I'm digging it.
[Nexus 4 Original Android Development] SA-07:
Sorry about the bootup frequency guys... I'll make it boot up at 1.512 Ghz next release.
[Nexus 4 Original Android Development] barondebxl:
Thanks!
[Nexus 4 Original Android Development] Simer03:
Meant no disrespect...I've been recommending this kernel to everyone I know! I apologize if u took that the wrong way but as all my trinity family know, the fact that I'm praising a different kernel, should tell u how much I love this kernel! Didn't mean to start trouble

Sent from my Google Nexus 4
[Nexus 4 Original Android Development] mikeyinid:
Battery life is good. That is all.
[Nexus 4 Original Android Development] Simer03:
I rebooted a lot, aokp has been a bit buggy so I couldn't get a legit reading on battery but for what its worth, here it is, still have battery left but I had to reboot at least 3 times! Will be trying cm10.1 next!

Sent from my Google Nexus 4
[Nexus 4 Original Android Development] morfic:
Me too!
[Nexus 4 Original Android Development] cpom1:
Did you get a Nexus 4?

Sent from my Nexus 4
[Nexus 4 Original Android Development] morfic:
Still not.
[Nexus 4 Original Android Development] jaestreetss:
Been in this a few days now and battery life is phenomenal
[Nexus 4 Original Android Development] kptnk:
Wait, does this mean you eventually received your N4 ?

Oups, haven't seen your reply. Hope you'll get it soon.
[Nexus 4 Original Android Development] DaX05:
No. It means he still has NOT received his Nexus 4.

Beamed via Nexus 4
[Nexus 4 Original Android Development] SA-07:
Sorry, I will not be releasing a stock GPU OC version because I like it how it is.

Sent from my Nexus 4
[Nexus 4 Original Android Development] Odiumvex:
I'm running Matr1x v4.5 kernel and Xylon rom ...and when im in calls the screen is off but i can still hit buttons? Anybody have an idea if it's the kernel or rom?
[Nexus 4 Original Android Development] Simer03:
That actually only happens to me when I use this kernel...so it may be kernel

Sent from my Google Nexus 4
[Nexus 4 Original Android Development] strra:
+1
[Nexus 4 Original Android Development] Higgsy:
That is an issue caused by sweep2wake. Was confirmed by show p in the bricked kernel thread,

Sent from a nexus 4
[Nexus 4 Original Android Development] m_zet:
I can confirm that S2W from 4.5 kernel (tested on Xylon and SB) causes possibility to hit buttons during calls. Just downgraded to 4.0 version. :D
[Nexus 4 Original Android Development] loscassapalle:
there is no way to remove the S2W (without downgrading). sometimens when i take the phone from my pocket, the screen turns on
[Nexus 4 Original Android Development] knapz:
I'd use Trickster to turn off S2W.
[Nexus 4 Original Android Development] Stryder5:
Trickstermod app should allow you to disable it.
[Nexus 4 Original Android Development] Simer03:
I wonder what updates s2w have been getting... I haven't been keeping track!?

Sent from my Google Nexus 4
[Nexus 4 Original Android Development] m_zet:
In my case even if s2w is disabled in Trickster accidentall button hit during calls happen to me on xylon and SB.

None of this on 4 kernel.
[Nexus 4 Original Android Development] chappy824:
I don't have this issue on stock rom. But experienced this on other custom roms. So I don't think its kernel related imo.
[Nexus 4 Original Android Development] showbo:
Searched this post but couldn't find anything. Any reason my flash just doesn't work? It is greyed out. I have only been running this Kernel, on 4.5 now.

LOL had HDR selected. GG me.
[Nexus 4 Original Android Development] Vangelis13:
Takes great pictures tho! :cool:
[Nexus 4 Original Android Development] SA-07:
Phew... finally, kernel update!

Be sure to try out the min_online_cpus module!

What it does is set the the minimum number of online CPUs when the screen is on.

The values are between 1-4. (minimum number of cores that should be on when screen is on)

For example, if you want 2 cores running at all times when the screen is on, do:

echo '2' < /sys/module/auto_hotplug/parameters/min_online_cpus

or just change the file directly from Android Mate or Root explorer.

*For CM users, I think you might need to use a script and load through ROM toolbox for the value to stick.

**If you enter a value outside of the range 1-4, the value will be set back to minimum of 1 core.

Also enjoy the revised sweep2wake with faux's touch screen patch!
[Nexus 4 Original Android Development] morfic:
You mean '>'