yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Original Android Development] deckard2123:
Mathkid,

Thanks for all your work on this kernel, it has truly been a masterpiece. I'd like to share my undervolting experience with version 8.5

Matr1x GPU OC with CM 10.1 Nightlies has been extremely stable for me on my "fast" binned chip running an additional -50 mV across the voltage table starting with version 3.0 and up to 8.0.

With version 8.5, I'm no longer able to run 1.5 GHz at 1,000 mV without frequent crashes. If I set my max CPU frequency to 1.35 GHz with the -50mV, it's perfectly stable.

Additionally, I haven't found the 192 MHz step useful, since 288 MHz is stable at 700 mV and I can't get 192 MHz to run at a lower voltage without crashing.

Thanks again for the hard work you've put into this kernel.

-deckard2123
[Nexus 4 Original Android Development] SA-07:
Do me a favor and find stable voltages with the 192Mhz step.

I mean if everyone doesn't like 192, I can remove it. It really isn't a big deal for me.

Sent from my Nexus 4
[Nexus 4 Original Android Development] m4r0v3r:
I've had no real problems with the 192mhz if anything my battery life seems tad bit better and the device cooler. It just seems people are obsessed with undervolting this to ****.
[Nexus 4 Original Android Development] DowntownJeffBrown:
I agree... I abandoned trying to undervolt my phone to the extreme long ago. I just don't see many positive results to continue doing it. I keep my defaults at what mathkid sets them (nominal chip) and at times I bump my max CPU down a bit but no undervolting.

Sent by my Kitteh he chews on muffins on my Sexy Nexi 4 using Tapatalk
[Nexus 4 Original Android Development] danielsf:
I have no problems with 192mhz, I have it running at 637mV perfectly fine but any lower I get instability. I have got a faster binned chip. Although I'm having a voltage problem with 8.5, as in I can't use the voltages I've used for months with out it locking up, but if I go to bricked or 8.0 I can use my normal voltages again. In 8.5 I've had to increase everything by 25mv compared to =<8.0. It's not a problem I'm concerned about as its only 25mv which is nothing, just thougt I'd bring it up. Anyway thank you very much :)
[Nexus 4 Original Android Development] chappy824:
I have fast binned chip and have been running 192 min 1512 max very stable at -125 UV total Wheatley deadline on liquid smooth. No reboots or any issues to speak of. My phone can go -150 UV if I want. 192 step has increased my battery life. When I'm at work I uc to 1026 max and battery lasts forever.
[Nexus 4 Original Android Development] bjc112:
Please don't remove it. It works fAntastic with wheatley governor. Everything is rock stable.
[Nexus 4 Original Android Development] sirxdroid:
I do not think you should remove the feature, some people like experimenting with it. A few posts back I was merely suggesting perhaps a bit more conservative defaults when the kernel is installed fresh, maybe go with 384 as a default freq and -75mV uv by default. This would make it stable for the vast majority if not all users who may want to try Matr1x. There are a couple of reports in this thread that 725mV is not enough for 192 and I think these reports should be the guiding factors not the ones that say "push it down to 600mV because it's rock solid for me".

---------- Post added at 08:01 AM ---------- Previous post was at 07:55 AM ----------

Because it's the default and I like it in general. I think that in general MPDecision + ondemand makes any kernel smooth. For some reason interactive for example doesn't feel very interactive to my fingers.I know Matr1x removed MPDecision, I like to run 4 cores online all the time though.

The other thing is that wheatley doesn't seem to be available in other custom ROMs and I usually like to compare similar settings.

I will give wheatley a try though.
[Nexus 4 Original Android Development] JamesInsights:
For some reason wheatley makes my phone hotter than ondemand..

Sent from my Nexus 4 using a toaster
[Nexus 4 Original Android Development] yethz:
Ive reverted back to 8.0 stable and working for me all stock setup

8.5 seems to crash for me (faster bin) stock setup.

Same apps and phone usage throughout the days...
[Nexus 4 Original Android Development] sirxdroid:
Try putting all 4 cores online all the time (Hotplug settings in Trickster Mod) and keep a low min freq, 192 for example, with ondemand governor.

---------- Post added at 08:09 AM ---------- Previous post was at 08:08 AM ----------

Good to know, I'll keep an eye on it when I try it.
[Nexus 4 Original Android Development] SA-07:
Alright, I've said this enough and only some people seem to get it.

I don't care if you want to go back to 8.0. That's your choice.

Either post voltages that work for you so I can get a glimpse of what to do for 9.0 with 192, or don't post at all. These types of clutter posts are absolutely useless and don't do anything for me or anyone. Now either try to help, or don't post.

Sent from my Nexus 4
[Nexus 4 Original Android Development] sirxdroid:
I approve this strategy. I first discovered it with the Trinity 117 kernel and it surprised me but the more I thought about it the more sense it made to me, there's gotta be some non-negligible overhead to on/off-lining cores all the time, given that processes would have to be migrated to a different core. I'd rather have the cores online ready to ramp up quickly when needed, and compensate by running a tad lower voltages and lower max freq.

No worries, we're cool. I was merely suggesting perhaps a bit more conservative defaults for the kernel out of the box. The features are very valuable to people who like to push the envelope, they should not be removed.
[Nexus 4 Original Android Development] yethz:
Ow sorry for the clutter and useless for u.

But, im just saying that 192 doesnt work for me and I thought that would help.

Coz u are the developer and im just an end user u probably know what could be the cause. Since some of here try to tweak to make it work, but I dont do that coz i first try the default setup included and coded in the kernel and if that doesnt work for me, then theres already an issues.

So, sorry for the useless post that u think it would not help u.

Great devs sometimes are rude to end users like me coz i havent contributed to his work...

Thankfully Im not a dev lol...

EDIT:

I think end users that dont want to dig to much just for the kernel to work for him because default setup arent working are not allowed to post in this thread.

Maybe I'll create another thread for matrix kernel for dumb users like me, and for I think there are many more wants to talk plain and simple not complicated brains out there who wants and answer that simple enough to help them..

EDIT 2:

Yes, ive read your queries about post voltages that works from thier phones.

And yes i think u think too much for kernel to be stable and working, im thankful for that, try to enjoy life outside and be proud that u have done a great job, coz I am more thankful for your dedication for us N4 users.

2-thumbs-up for great kernel.

Thank you.
[Nexus 4 Original Android Development] SA-07:
Even though you're an end user, you can still read through the thread and see that I have requested people to continue testing and posting voltages. If you don't want to do that, that's fine but your post seriously doesn't help in any way. I didn't want to come off as rude, though.

Anyway, just forget about it.

Sent from my Nexus 4
[Nexus 4 Original Android Development] sirxdroid:
Question for those using Wheatley: do you adjust sampling_rate and up_threshold to match the defaults for the ondemand governor? Wheatley is based on ondemand, hence my question, to see how it improves (or not) upon ondemand using the same settings. Or are the defaults for Wheatley supposed to be used as-is?
[Nexus 4 Original Android Development] n2d551:
Hey mk, I personally think that the voltage set up, stock @ what your kernel offers now is amazing. I'm running @ 192 for the min, screen off, and I checked the phone @ idle the other day and I think I was losing 1% or less in an hour.
[Nexus 4 Original Android Development] cheech87:
An additional -50 mv is stable for me (nominal chip). -75 crashes and shows artifacts.
[Nexus 4 Original Android Development] cantevencode:
Is there any way to change default voltages before flashing without compiling from source? I changed roms and now I'm getting a bootloop when I try to flash this.
[Nexus 4 Original Android Development] deckard2123:
I spent the better part of today hammering out my minimum stable voltage table for Matr1x 8.5. I've got a "fast" binned chip and this is what I've come up with:

192 MHz 700 mV

288 MHz 700 mV

540 MHz 725 mV

702 MHz 775 mV

1.02 GHz 850 mV

1.18 GHz 925 mV

1.35 GHz 962.5 mV

1.51 GHz 1,037.5 mV

So far this setup runs stable and takes artifact free photos.

If the minimum stable voltage is the same for 288 MHz and 192 MHz, are there any battery saving benefits for running at the lower clock speed?

-deckard2123
[Nexus 4 Original Android Development] icepixie:
Happened to me too. So I flashed my rom again that includes the stock enhanced kernel. I went into Fauxclock and ensured I didn't undervolt. Once that was fixed I flashed 8.5 and no more bootloops.
[Nexus 4 Original Android Development] IAmAN00bie:
Yes, the power dissipated by the CPU is directly proportional to the square of the voltage as well as the frequency. So even though both are running at the same voltage, the lower clock results in less power used.
[Nexus 4 Original Android Development] JamesInsights:
I tried both on two different cycles and i was using ondemand on the third and counting. Wheatley provides less battery life for me, not sure if it is because it made my phone hotter than ondemand. Next i changed it to fit ondemand settings from the kernel tweaks guide somewhere on xda (cant post link now, try searching governor control tweaks). I realised my phone was not as hot but the general performance was not as smooth relative to ondemand. Eventually I just moved back to ondemand and just leave it be. Remember that Mathkid has tweaked ondemand and as we have all learned it's always better to trust him :)

I know wheatley is tweaked ondemand not sure if tweaked for higher performance or higher battery but i felt ondemand had higher battery.

Try it out and let me know how it works for you cause every n4 is different :)

Sent from my Nexus 4 using a toaster
[Nexus 4 Original Android Development] rizocreations:
Been using 8.5 since release. It is the best kernel I have tried so far. Please do not remove 192 ever!

Screenshots posted were the first cycle, was at voltage of 700 @ 192. I've never gotten that much battery life, EVER!

Over night the phone goes into a nice deep sleep and barely loses any battery. I did not turn anything off to help conserve more battery except GPS and NFC, unless I was using it. Location services, Google Now, and sync all enabled all the time.

Voltage I'm using now and still getting great battery is 687.5 @ 192 and still stable. No problems with any reboots at all.

Max freq set is 1026, min obviously at 192. Using wheatley, with nothing else modified with it.

Thanks mathkid, your a genius.
[Nexus 4 Original Android Development] Ulver:
First run with this kernel and I'm very impressed! I'm using wheatley too.
[Nexus 4 Original Android Development] dEris:
Love this kernel.

[DEVICENEXUS⁴] [ROMXYLON] [KERNELMATR1X] [RECOVERYTWRP]
[Nexus 4 Original Android Development] sirxdroid:
@rizocreations - what ROM is that please?
[Nexus 4 Original Android Development] serkanhiziroglu1998:
Hello guys. Which app should i use to edit kernel settinggs ?

Nexus 4 cihazımdan Tapatalk 2 ile gönderildi
[Nexus 4 Original Android Development] ceejay83:
trickster
[Nexus 4 Original Android Development] ctfrommn:
+1 for Trickster, I even bought the paid version so I can backup/restore kernels and other things....awesome app.
[Nexus 4 Original Android Development] rizocreations:
PAC with CM10.1 S4 (paid) theme.
[Nexus 4 Original Android Development] sirxdroid:
I use Trickster Mod Don't forget to enable the "set on boot" option when you are happy with the settings otherwise they will not survive reboots.
[Nexus 4 Original Android Development] michelD:
I find Wheatley is a very good compromise in term of smoothness vs battery drain.

The only modification I did is power save_bias that I set to 500 (meaning 50%) instead of 0. This further save battery in heavy usage while preserving smoothness (at least for me)
[Nexus 4 Original Android Development] sirxdroid:
I tried wheatley and don't find it as smooth as ondemand, maybe because of the different settings for up_threshold and sampling_rate. I also changed them to match the default ondemand settings and still could not get it to be as smooth as ondemand - could have been all in my mind (or my fingers rather) at that point.

I find that MPDecision+ondemand makes any kernel very smooth for me (for kernels that allow MPDecision). The other strategy that I like for kernels that disable MPDecision: all 4 cores online with a min freq 192-384, max freq 1026, ondemand governor. Otherwise I tried many other things and can't get a smooth experience. I know many like the interactive governor but I find it choppy unless I tweak it to the point where it's very aggressive and that's not good for battery.
[Nexus 4 Original Android Development] m4r0v3r:
I have a very smooth kernel with Wheatley can't personally tell the difference between it and on demand. I've never actually had any real lag on the nexus 4 no matter what settings/kernel I use.
[Nexus 4 Original Android Development] jejecule:
Hello,

I've been testing this fantastic kernel v8.5 for 5 days now, and I'm more than happy with the results, never reached such a combination between smoothness and battery life with other kernels!

Set up:

192 MHz 700 mV

288 MHz 725 mV

540 MHz 775 mV

702 MHz 800 mV

1.02 GHz 875 mV

1.18 GHz 950 mV

1.35 GHz 975 mV

1.51 GHz 1,000 mV

min 192/ max 1026

Wheatley

3 core online max (i don't know why though:))

The rest stock

With that I achieve between 4 and 5hrs on screen time depending on the phone calls duration, wifi and sync always on when screen on, and off when screen off thanks to better wifi on app from the better battery stat app dev.

Around 1 and an half day total duration.

Thanks a lot dev, I found the perfect setup for my N4:good:

Cheers
[Nexus 4 Original Android Development] sirxdroid:
@jejecule - those are pretty aggressive voltages. If you say it's all stable, you must have a good chip. Mine, even though Fast bin, seems to only like +50mV from your voltages. It's all good though, I haven't run out of juice yet without being close to a power source.
[Nexus 4 Original Android Development] jejecule:
Yep it must depend from one device to another, i have more experience on S3 and know that for a specific kernel and voltages, two devices with the same apps, same rom, and same usage will react completely differently.

I'm on faster bin, forgot to mention it.

Yes this voltage seem agressive but it's very stable on my device, and no heat or other issues with camera for exemple. I've read all the posts in this thread since the 8.5 version release, and it seems that this setup is not far from the average one (at least for faster bin chips).

It may also depend on the rom we use, perfect for me with this setup on Carbon.

I also add that I don't play games with this setup, i think i may have problems with such a voltage should I try it :)
[Nexus 4 Original Android Development] JamesInsights:
That's weird thanks to 8.5 i seem to be undervolting more with a nominal cpu than people with fast ones.. I have 192 at 712 and everything else follows

Sent from my Nexus 4 using a toaster
[Nexus 4 Original Android Development] resynx:
Just flashed Matr1x for the first time, excited to see how it performs :)
[Nexus 4 Original Android Development] :
This is a bit more aggressive. But it works well, while temperature is not too high. Just if I use it in the sun, but that is not the phones fault.
[Nexus 4 Original Android Development] dEris:
Anyway we can get 2way recording. Really need to record baby mama drama for court evidence. Mic recording sucks, so please don't suggest any.

[DEVICENEXUS⁴] [ROMXYLON] [KERNELMATR1X] [RECOVERYTWRP]
[Nexus 4 Original Android Development] ooohhaaahh:
I'm about +25mv over you and it plays games fine for me, I only upped the voltages abit since I added a lock screen widget and it caused difficulties waking the phone. That seems to have fixed it.

Testing out wheatly since it was amazing on my gnex
[Nexus 4 Original Android Development] Magnumxxxl:
Quick question

I have a quick question, how do you put it in single core?
[Nexus 4 Original Android Development] naenee:
You can use Hotplug settings, for instance with the Trickster Mod app, and select max cores = 1.
[Nexus 4 Original Android Development] eng.stk:
A few days with v8.5 I notice that UV is a little lower on both lowest and hightest frequencies (25mV difference, using stable values and no artifacts or reboots). Tested with default settings, only changed voltages (I'm on a faster binned chip btw)

Performance is better in my opinion, wheatley is more smooth than on v8, battery usage is a little better too (if using michelD tip, powersave_bias = 500 is even better, thanks mate:good:)

EDIT: 192MHz step doesn't mak e difference for me, I can get same voltage on 192, 288 and 384 (this last on others kernel I tested).
[Nexus 4 Original Android Development] trillo69:
Is there any recommended settings for this kernel? I mean about governor and i/o scheduler, I ask because I see that on demand is default governor (not very battery friendly).
[Nexus 4 Original Android Development] adidas007:
I get 5hrs on screen time. My best being 5hrs and 51 mins
[Nexus 4 Original Android Development] trillo69:
With on demand governor?

Just another question, on governor settings I see 3 values for up_threshold:

up_threshold

up_threshold_any_cpu_load

up_treshold_multi_core

I'm familiarized with the first one, but what's the difference with the other 2?

PS: this kernel with min cores online = 4 is f***** awesome. Great job!
[Nexus 4 Original Android Development] cowst:
With 1024 I feel a bit slower, but what kills performances is 500 powersave bias.

Wheatley/row with 2 cores feels good.
[Nexus 4 Original Android Development] michelD:
Personally, with Wheatley, I use powersave_bias=500 with 196-1512MHz, row and 4 cores min.

For me it is perfect for daily usage, no lags and good battery life.

I agree that to force 4 cores always ON, does not impact battery life (even in standby) while improving performances.
[Nexus 4 Original Android Development] trillo69:
I'm running with 4 cores online, on demand and raised up_threshold to 90 and it's really smooth with aokp pub. And battery life is being awesome. Also benchs great, good for trolling people. :p

It would be awesome to have higher freqs to OC on future builds.
[Nexus 4 Original Android Development] m4r0v3r:
hmm may attempt to use the 4 min core setting after good feedback.
[Nexus 4 Original Android Development] misterpho06:
whats the best setting for TCP congestion control, i/o control, minimum online cpus, and min/max cpu freqs for a buttery smooth experience but also for best battery life.

right now I haven't changed any of the settings in trickster mod and i'm getting around ~1.5 days on battery with minimal usage.
[Nexus 4 Original Android Development] Enkiduz:
Guys... This kernel it's AMAZING, but i have only one problem with it.

When i wake up my phone from deep sleep, the lockscreen lags.. after that, the phone is smooth 100%

I tried with CM, fresh install, with stock setting without changing anything and with System Tuner changing voltage, min clock, force all the 4 core online.. tried all setup..

what can it be?

I read few pages back someone that have the same problem.. he resolved? i did not find a solution
[Nexus 4 Original Android Development] tuilalnvinh:
1/ Are u using lastest baseband (0.48)?

2/ Try raising mjn freq to 288mhz
[Nexus 4 Original Android Development] Enkiduz:
Yes for both...

i even tried with 540 min freq

same result every time
[Nexus 4 Original Android Development] chappy824:
You should try liquidsmooth ROM

here>> http://xdaforums.com/showthread.php?t=2221501

Also use trickster app to adjust kernel settings and hit check mark at top right to apply changes. I have zero lag at stock settings and at extreme uv and uc.
[Nexus 4 Original Android Development] kipue:
Hi, first, thanks for the great work!

Second, I m trying to make some changes to the kernel as I read this thread. Can anyone please tell me what is the name of the option allowing to change the number of online cores?

Thanks!
[Nexus 4 Original Android Development] misterpho06:
hot-plug control

---------- Post added at 10:18 PM ---------- Previous post was at 10:13 PM ----------

---------- Post added at 10:18 PM ---------- Previous post was at 10:18 PM ----------

for paranoid android rom...

should I flash the non-CM version of this kernel???? or CM version?
[Nexus 4 Original Android Development] adidas007:
Non cm
[Nexus 4 Original Android Development] resynx:
Had a random reboot :(

Using stock voltages, here's a log :D

Edit: hold on log not uploading

Edit: Here you go :)
[Nexus 4 Original Android Development] Dungeon47:
I'm no expert, nut it looks like you had mp decision on, which may be causing conflicts.
[Nexus 4 Original Android Development] alekos-ep91:
hi guys

i just flashed matrix kernel and i cant change governor...its stuck to ondemand...

what can i do?:crying:
[Nexus 4 Original Android Development] m_zet:
Try reboot the phone.
[Nexus 4 Original Android Development] alekos-ep91:
i have done this:crying:

i will try to flash the reset kernel and then again the matrix...hope it works
[Nexus 4 Original Android Development] Enkiduz:
As well as system tuner, I tried trickster mod too.. Same result..

I will go to try liquidsmooth then.. And let you know if the lag persits..

Others ROM with stock look to reccomend to me?

Inviato dal mio Nexus 4 con Tapatalk 2
[Nexus 4 Original Android Development] trillo69:
Bionic Pure AOSP.
[Nexus 4 Original Android Development] odeccacccp:
Yes
[Nexus 4 Original Android Development] Goku80:
actually let me rephrase....love this kernel and have to say is great...

but having a few issues and hopefully someone can help out please.....now i have been using Carbon rom and now Xenon and been using the non cm version 8.5...everything has been running well but when i been trying to set up settings up with Trickster i had a couple of occasions were once the rom froze and just rebooted....once it rebooted it optimized all my apps and then just rebooted again.....now i always before flashing a new kernel i wipe cache and dalvik and flash a reset kernel....

anyways tried a new rom and flashed the non cm version and set my settings up and UV...rebooted and checked trickster and everything went back to default...but then again few moments afterwards had random reboots again...could it be since the kernel is already UV and by me trying to UV more it gives it the random reboots?

everytime i try and get a log or a ksmg it just not let me
[Nexus 4 Original Android Development] Enkiduz:
Nothing to do..

For now i have tried 4 rom (PAC, PA, Liquidsmooth and AOKP M1)

With this kernel and all settings @ stock, ONLY the lockscreen lags.. i just can't belive at it.

I really do not understand why most of you don't have this problem.. at this point maybe the cpu is one of the unlucky and needs a more voltage?

Any idea?
[Nexus 4 Original Android Development] ckret:
it could be caused by low freq.

try setting your min freq a bit higher
[Nexus 4 Original Android Development] resynx:
Nope, mpdecision is off =/
[Nexus 4 Original Android Development] Enkiduz:
Done it already.. up to 540 mhz..

Just now i have tried 288 min freq with all 4 core online and voltage a little bit higher, seems problem gone..
[Nexus 4 Original Android Development] Goku80:
sorry to requote this just hoping someone sees my edited post
[Nexus 4 Original Android Development] Archmag3:
flashed the kernel looks smooth.anyway to get min cpu freq to 384 ?