yashsingh1/xdaforums huggingface dataset:
[Nexus S Android Development] :
Mat1x v17.0 benched. Beats its personal best!

Results here: https://docs.google.com/spreadsheet/ccc?key=0AntDDKv-lS6IdFZ6VDRQV0cxRXFVT2dKYm94bWJyQ0E
[Nexus S Android Development] italia0101:
Does anyone else have this issue :

Ics 4.0.3 with flavors mod...

Then flashed the Bluetooth fix for deep idle to work ..

Now when I hold the power button on my phone I just get a reboot every time ...

I'm guessing the Bluetooth fix overwrote something in the framework and conflicted with my power button ?
[Nexus S Android Development] mixtapes08:
New version is so superb again. Tnx mk :)

Sent from my Nexus S
[Nexus S Android Development] qtwrk:
i have different thoughts , of course , i don't know for sure and i didn't actually test it.

if clock speed is down , it should take more times to complete the same task ?

for example 1 Ghz needs 2 seconds to down a calculation , which in turn , 800 Mhz needs 2.5 seconds , and 1.2 GHz needs 1.67 seconds.

and in voltage table , 1200 Mhz = 1325 mV , 1000 = 1250 and 800 = 1175

by my stupid math and electricity which i have failed in school

1325 mV * 1.67 sec = 2212.75 mV

1250 mV * 2 sec = 2500 mV

1175 mV * 2.5 sec = 2937.5 mV

....

so??? overclock actually take less power to complete a same task:confused:

because my stupid brain tells me that to complete same task , 1.2 GHz took 2212.75 mV , 1 GHz took 2500 mV and 800 Mhz took 2937.5 mV

or just it doesn't calculate in that way ?

more time + less voltage equals or not equals less time + more voltage ???

just like a simple math 1 + 2 = 2 + 1 , or what ?
[Nexus S Android Development] mixtapes08:
Conservative is the best :) battery life and performance :)

Sent from my Nexus S
[Nexus S Android Development] deetailed:
In the first post it says "- Deadline, SIO, and BFQ I/O Schedulers". Does this mean Noop is not included in v17 or it's just the description that's not up to date? Sorry but I've never really paid attention to this part of the first post before.
[Nexus S Android Development] sakisds:
Noop is included, along with deadline, cfq, bfq, sio and vr.
[Nexus S Android Development] aLNG:
For race-to-idle concept u are right, but for underclocking fans there is one more concept, dvfs. Dynamic Voltage Frequency Scaling. Not all workload is CPU related. In my opinion this race-to-idle vs dvfs depends on many things. Ur usage, CPU arch(modern CPU has ACPI C like gnex, suitable for race-to-idle? Better ask Ezekeel), ...so test by urself :)
[Nexus S Android Development] gotjazz:
hrm the cfs version of 17.0 has different checkums on the file page than listed in the directory page - something gone wrong uploadeng?
[Nexus S Android Development] :
It doesn't work like that exactly. It's not the voltage, it's the current too.

from my battery thread:

Read more here: http://xdaforums.com/showthread.php?t=1478406
[Nexus S Android Development] Harbb:
That won't work, because flavours edits the framework-res.apk. Then you replaced that edit with a stock framework with only the bluetooth toggle. Defia in the flavours thread has uplodaded a v0.7 with the bluetooth fix included. I use this myself and checked over the work, flawless.

Sadly it is not quite like that. Power usage depends on frequency and voltage squared, while capacitance remains static (C * F * V * V). There is some invaluable information in the battery benchmark thread about this, as well as hard facts supporting such theories. Besides, the only valid use of higher frequencies are efficiency and user experience. 20mhz on these processors is extremely inefficient in comparison to 100 or 200mhz.

What you are describing is a race-to-idle scenario, but in many situations there is no feasible idle state (in a perfect world we want deep sleep) that will save as much power using a higher frequency over a lower one. All of this is far too tedious to put together in a couple of paragraphs, so i'll just leave it at that. Visit the benchmark thread and all of the links to get the whole story.

Beaten twice in one day (and on the same page). I'm on a roll.
[Nexus S Android Development] rip_noob:
Cna 1.4.0 has a ksm option. Should we enable it or it is on by default?
[Nexus S Android Development] Imppy:
Having the deep idle problem again even with the patch...any services can prevent from going to idle? Codename 1.40 from here
[Nexus S Android Development] Harbb:
Google Talk, you'll have to open/close camera on each boot to get deep idle working. CNA, from memory, has the BT patch so you should get top=off times as soon as the camera closes and the screen is off.
[Nexus S Android Development] qtwrk:
:p well , i see now why i failed my electricity class:(
[Nexus S Android Development] italia0101:
Thanks I'll try that 0.7
[Nexus S Android Development] FlatEric0074:
Flashed matrix kernel 17.0 cfs on top of last NexusMV rom build 2.02.15. Works like a charm, running without any problems. Deepidle on, 1200/100 MHz, lulzactive gov., no liveoc.
[Nexus S Android Development] y3mita:
Using latest 17 cfs version, flying fast! Trying that lionheart governor along sio 200-1000 def voltage! Got rid of nstools and using system tuner instead, looking in app setting to read deep idle stats!
[Nexus S Android Development] afzalarsalan:
Did you add the colors you discussed with me?

If so, I'll stick to my promise and donate

Edit:

Looks like you did by your github so there my donation :)
[Nexus S Android Development] y3mita:
no green flicker

Whatever you did to this kernel I do not experience the annoying green flicker... my voodoo settings for color:

RGB: 288 - 333 - 392

Gamma hack: 2.3.3 defaults!

Nicely done!

Also, loving the speed and performance... about battery I will do some serious testing after a full charge!
[Nexus S Android Development] DarkhShadow:
That's why you have no green flicker lol

Sent from my ice cream powered Nexus S
[Nexus S Android Development] y3mita:
I used to get them before even with gamma hack as defaults! This time, I went and hit punchy after my RGB changes and then reset to 2.3.3 defaults! For some reason my punchy settings remained as I did not see changes on the display *which is nice*

Anyhow, 2.3.3 does the trick as you mentioned at least for me on this last version.
[Nexus S Android Development] giannis_mathiou:
Hey mathkid congratulations for your great kernel. I'm getting amazing battery life with apex ROM and your greatest kernel.

Although I find everything great on your kernel I have a crazy request. Could you add some eye candy feature on your kernel like Eugene373's kernel? The blue bar loading in the Google screen? Thank you very much.
[Nexus S Android Development] b1337:
lol u call that eye candy i remember everyone *****ing about that, its pretty easy to make your own boot animation, you will probably have better luck that way
[Nexus S Android Development] IIIV:
Can anyone else confirm this please?

Thanks
[Nexus S Android Development] The1Shark:
Just flashed ver 17.

Thanks MK !!
[Nexus S Android Development] IIIV:
Just flashed v17.0 (also wiped cache and dalvik cache and reset NSTools from recovery) and had a freeze on the lockscreen. So, I took off and put back on the battery and had a freeze during boot. So, I took off and put back on the battery again and now it's stuck on the "Downloading... Do not turn off Target!!!" logo. :confused:
[Nexus S Android Development] SA-07:
Don't wipe cache. Just wipe dalvik cache and flash kernel
[Nexus S Android Development] DarkhShadow:
The .zips don't have a auto dalvik cache wiper?

Sent from my ice cream powered Nexus S
[Nexus S Android Development] SA-07:
No they don't.
[Nexus S Android Development] DarkhShadow:
*wonders how I don't have to wipe dalvik*

Sent from my ice cream powered Nexus S
[Nexus S Android Development] SA-07:
Ohh nooo
[Nexus S Android Development] coolfranz:
Does anyone have a boot issue with this kernel?

Today i tried a lot of ICS Rom's, with all i have the same problem after flashing matrix kernel.

When i power off the phone it doesn't start properly the next time (if i hit the reboot button in some apps this doesn't happen all the time).

The phone boots, then the boot animation freezes, the phone powers down after a few seconds, then it goes on again an then it boots how it should.

Before installing the different Roms I installed the "Rom Wiper .zip" and I am using a i9023.

Does have anybody similar problems, or a solution for this?
[Nexus S Android Development] DarkhShadow:
Lol I know, never had any problems from flashing your kernel

Sent from my ice cream powered Nexus S
[Nexus S Android Development] DarkhShadow:
So you did:

ROM wiper>flash rom>flash kernel?

Sent from my ice cream powered Nexus S
[Nexus S Android Development] SA-07:
Fran that does a clean install right?

In addition did you do the process like this?

1. Wipe data, cache, dalvik cache, and format /system

2. Flash rom then set it up

3. Go back to cwm and wipe dalvik cache then flash kernel

4. Reboot

That usually works
[Nexus S Android Development] ferdi7103:
Same case with you...but only in version 17...before never like this,and then i try to go recovery and then restore nandroid backup
[Nexus S Android Development] SA-07:
Try my above steps
[Nexus S Android Development] coolfranz:
Yes!

I did: ROM Wiper > flash Rom > Reboot > Wipe Dalvik + Cache > install Matrix

and also: ROM Wiper > flash Rom > install Matrix

nothing worked really good.
[Nexus S Android Development] SA-07:
Yeah don't wipe cache before flashing the kernel.
[Nexus S Android Development] IIIV:
Tried to reflash v17.0 and I'm stuck on boot logo... I guess I'm gonna have to reflash my ROM, which sucks 'cause I haven't backed up my apps in a while.
[Nexus S Android Development] coolfranz:
First of all, thank you for your fast reply!

I used the CNA Rom, installed it exactly as you said, the first boot after installing matrix was fine...

Then i turned off the phone and then on again - it got stuck at bootanimation, turned off and then booted just normally.
[Nexus S Android Development] SA-07:
What cpu governor?
[Nexus S Android Development] coolfranz:
Did't change anything, in settings performance > processor speed it says ondemand

Changed it to lulzactive, still the same problem...

Edit:

I was able to get a little bit further...

I checked the option to disable the boot animation in the CNA settings an now it boots, I am able to enter the PIN, watch my homescreens, then it freezes and reboots, then anything is working fine.
[Nexus S Android Development] S_Dot:
Is the Bluetooth fix mandatory for all flashes?
[Nexus S Android Development] TheLastMirana:
Hey math kid I flashed ur v 17 and can deep idle patch and for some reason I dibt see either top off or on . Its all zeroes... v16.5 works perfectly.. also is ksm recommended to be enabled
[Nexus S Android Development] moriz1:
I detected some color changes, and the screen no longer flickers. It's definitely more bluish, though the difference is subtle.

Btw, how do I enable ksm? Is it enabled by default?
[Nexus S Android Development] SA-07:
@mirana I don't know what you're doing but deep idle on v17.0 works fine for me.

What rom are you on?
[Nexus S Android Development] TheLastMirana:
I'm using code name android from and have kam enabled I used the authors deep idle patch
[Nexus S Android Development] TheLastMirana:
V 16.5 plus the patch worked properly
[Nexus S Android Development] SA-07:
I don't know... I didn't do anything to deep idle in v17.0
[Nexus S Android Development] coolfranz:
@mathkid

any ideas on the boot problem with the i9023?

Edit:

There must be any issue with this kernel, I just tried glados and it works just as expected...
[Nexus S Android Development] belvedere:
bro, my phone just did my laundry. this kernel module has been implemented perfectly.
[Nexus S Android Development] rrohanjs:
with aokp build 23 i am currently on 40% battery and its been 1 day 6hrs :P

matrix 16.5 cfs smartass v2 noop deep idle enabled
[Nexus S Android Development] theooo:
Hello MK, just installed v17 and using smartassv2 100-1200 on Codename Android. Everything was ok until i modified smartass parameter trough NSTools, i changed ideal wake freq ->800, ideal sleep ->200 and wake up freq to 1000. After that my nexus became hot and very laggy, settings and NSTools not responding. I wonder why this is happen.

After that i tried to change governor to ondemand and everything ok again..
[Nexus S Android Development] zgomot:
I also experience random reboots. 16.5 was really bad with lots of reboots and 17 seems way more stable, yet it still rebooted a few times.

100/1300 | smartass v2 | noop | deep idle on | all voltages +30 | kangy13

Sent from my Nexus S
[Nexus S Android Development] SA-07:
Raise your int voltages as well
[Nexus S Android Development] zgomot:
I have already raised them all by 30, do you mean to raise them some more?

Sent from my Nexus S
[Nexus S Android Development] SA-07:
So you raised both arm and int?

For testing purposes, do the reboots still occur with deep idle off?
[Nexus S Android Development] LibertyMonger:
I'm not having any reboots or issues with v17 everything is great for me. Seemed I was having issues with signal on 16.5 so I reflashed gummy to wait for your v17 and all is great again.
[Nexus S Android Development] zgomot:
I'm not sure what you mean by "both arm and int". I used Rom Control, the app that comes with Kangy. NS Tools correctly shows the custom values I set.

Foe testing purposes I will turn deep idle off for a while.

Thanks for your time.

Sent from my Nexus S
[Nexus S Android Development] mixtapes08:
i don't know mk but all your kernels was so stable for me. no bugs at all.

im using v17 with this settings:

Governor: conservative(tweak with nstools) sampling rate:20000,down threshold:20%,up threshold:60%,sampling down factor:1 step,freq step:5,ignore nice load: off.

IO scheduler: cfq(according to bedalus this is the best for conservative gov)<<true ;)

UVd arm volt by 25

stock int volt

deep idle enable

rom:cm9 2.1

superb battery and performance...
[Nexus S Android Development] mushupork:
In nstools, on the VOLT tab, the top set of values are the "ARM" voltages, the lower set of values are the "INT" voltages.
[Nexus S Android Development] caliban2:
Those reboot problems sounded familiar, got them with v16.5 already. So I flashed v17 - and they're there. Flashed back to glados - gone. Only flashing kernel, sys stayed as it were.

Did some more testing with v17 then: Phone has to have been running for some time for the bug to occur. Got 3 manual reboots in a row just fine, but if the phone has been up for 15 minutes - bug. Also, if I wipe cache and dalvik on reboot, it doesn't occur. (Silly me didn't test if both need to be wiped or only one of them)

Anyhoo, this points to a certain direction (errors in caches). Should also note that I set voltages to the same values as glados has - undervolting shouldn't be the cause.
[Nexus S Android Development] 6marcus9:
What do you mean with "UVd arm volt by 25"?

Do you mean of subtract a value of 25 at all UVd frequency??

thanks
[Nexus S Android Development] caleb1783:
using latest matrix w smartassv2 w noop at 400/800

superb battery and performance! great one mk … keep up da good work…

for details on each setup plz refer to my signature…

Sent via Divinus Nexus S...
[Nexus S Android Development] The1Shark:
V16.5 didn't use deep idle code ..

It used cpu idle.

EDIT :

Sorry my bad. I confused with v16.

.
[Nexus S Android Development] mixtapes08:
Undervolted arm voltage by 25

Sent from my Nexus S
[Nexus S Android Development] jimkaps:
What should I wipe before installing a new kernel ?
[Nexus S Android Development] aLNG:
Dalvik cache
[Nexus S Android Development] jimkaps:
I have done this. I am using cm9 with matr1x kernel v16 and I detect lag while opening the dialer
[Nexus S Android Development] Dorilife:
This happens alot on ICS, what i did was turn off haptac feedback and touch sounds and it stoped it, noticed it on all my ics devices..S2/Nexus/Glacier/Razr

Dont think its kernal related.
[Nexus S Android Development] jimkaps:
AAA thanks I will try it
[Nexus S Android Development] alxjag:
Just installed 17.0 and faced few troubles.

Camera works pretty unstable: strange horizontal 'sync' lines during the preview, and shots sometimes are not taken at all or contains no data - just some green noise.

Is it a known issue?

PS: 9020t, v17.0 cfs, flashed over the stock rom, no CPU frequency changes.
[Nexus S Android Development] caleb1783:
mine seems fine..

Sent via Divinus Nexus S...
[Nexus S Android Development] SA-07:
I have not had those issues at all...
[Nexus S Android Development] Imppy:
I'm still not getting idle...already installed Bluetooth patch and also killed talk video...
[Nexus S Android Development] insomnia48:
Hey guys,

Is it my idea or is v17.0 sluggish at times?

I've been using Matr1x ICS since day one and I never had any problems.

The lag seems to disappear after a reboot, but give it some hours and it comes back again.

I've always updated to the latest version, but v17.0 is troubling me, I'm considering rolling back to v16.5.

Anyone else experiencing this?
[Nexus S Android Development] SA-07:
Nope no lag here. Consider changing your governor/clock speed! :D
[Nexus S Android Development] insomnia48:
Really? :D

I've been using smartass for more than a year now, from back in my Hero days and I never had a problem with it. Same goes for my clocks, I've been using this setup for a little less than a year now, since I've bought my Nexus S.

Anyway, I updated my CM9 installation to v3.0 tonight, so I'll test it a few more days and see how it goes.
[Nexus S Android Development] SA-07:
Yeah I mean it could be the ROM as well. I'm on Codename android 1.4.0 and it's very smooth... running it at 1300/400 ondemand

But maybe just let CM run a bit longer haha
[Nexus S Android Development] mixtapes08:
Are u using the latest nstools with this gov.? If you are. Thats the problem. Bec latest nstools mess up smartass gov.

Sent from my Nexus S
[Nexus S Android Development] dark06:
Yes i can confirm only smartass.i switched to ondemand because it really is crawling when on smartass be it scrolling pics on gallery or playing music for the first time after reboot.so nstools is the problem not the kernel?
[Nexus S Android Development] zgomot:
How does the latest NSTools mess up smartass? This is my setup and I can't say anything's messed up.
[Nexus S Android Development] j1po:
Using matr1x v17 on cm9 v2p1

DI works fine

Then I upgraded to cm9 v3

DI not works

Back to cm9 v2p1, now DI working fine

Anyone has this issue?
[Nexus S Android Development] mixtapes08:
Yup its been reported several times in nstools thread. Nstools change the given value of smartass gov that causing freeze reboots and sometimes overheating of phone. If you want to use smartass and tweak them .better do it in terminal emulator and uninstall or go back to the previous of nstools version.

Here is my setting

Smart ass v2

For battery life

Code:

echo "500000" > /sys/devices/system/cpu/cpufreq/smartass/awake_ideal_freq;

echo "200000" > /sys/devices/system/cpu/cpufreq/smartass/sleep_ideal_freq;

echo "500000" > /sys/devices/system/cpu/cpufreq/smartass/sleep_wakeup_freq;

echo "85" > /sys/devices/system/cpu/cpufreq/smartass/max_cpu_load;

echo "70" > /sys/devices/system/cpu/cpufreq/smartass/min_cpu_load;

echo "200000" > /sys/devices/system/cpu/cpufreq/smartass/ramp_up_step;

echo "200000" > /sys/devices/system/cpu/cpufreq/smartass/ramp_down_step;

echo "48000" > /sys/devices/system/cpu/cpufreq/smartass/up_rate_us

echo "49000" > /sys/devices/system/cpu/cpufreq/smartass/down_rate_us

Sent from my Nexus S
[Nexus S Android Development] y3mita:
Look for CPU tuner in market! You'll love it
[Nexus S Android Development] arifhn:
Did you success run any of those command?

I tried this

echo "500000" > /sys/devices/system/cpu/cpufreq/smartass/awake_ideal_freq

the command never returned to shell
[Nexus S Android Development] al_madd:
Finally..after months.....I can flash matr1x back...

How I missed Matr1x kernel so much..haha
[Nexus S Android Development] vasilios1979:
Hello to all...i would like to ask why voodoo color settings are not activated...i use apex rom and latest matrix kernel...
[Nexus S Android Development] DarkhShadow:
they are, but you need to use voodoo control app to modify them, or use terminal

Sent from my ice cream powered Nexus S
[Nexus S Android Development] vasilios1979:
i have voodoo control..but only the sound settings come up no color...
[Nexus S Android Development] DarkhShadow:
Do you have a i9023? If you do then you don't get voodoo colours, if you do have a i9020 then you must have done something

Sent from my ice cream powered Nexus S
[Nexus S Android Development] vasilios1979:
Yes i have i9023... so no voodoo colors for me then...thnks for the info
[Nexus S Android Development] briggl:
Did anyone experienced that using Matr1x kernel (i've tested v16, 16.5, 17 cfs) causes a reboot once while bootanimation any fully boots up at second time?

For me the first boot after flashing was normal but any other reboot needs two runs to boot up completely.

I've tested it on the latest CM9 v3.0 and the stock ICS RoM -> same behavior.

I've tried two different ways to flash:

1) full wipe (factory reset, cache, dalvik) -> flashed RoM -> flashed kernel -> flashed latest gapps (2012 02 15) -> reboot

2) full wipe -> flashed RoM -> flashed gapps -> reboot (all works fine) -> flashed kernel

none of them worked for me.

I wonder if anyone has the same issue, respectively solved it?

If necessary, my device is the i9023 one with XXKI1 baseband version.

Hopefully someone can help.
[Nexus S Android Development] mixtapes08:
Yes but i freeze 1st the nstools before doing that. Anyway i dont use smartassv2 very often so i always using your tool for tweaking conservative and it is wonderful. Hope you can fix it soon sir thanks :). Btw did you type "su"? before entering these commands bec its working for me.

Sent from my Nexus S
[Nexus S Android Development] Konfuddle:
I've followed exactly the same steps as labeled above but, I still get the same boot problems as Fran. After I turn off my phone overnight and I turn it on the next morning, it'll freeze halfway during the boot, and then boot again normally.

I have an i9020t on CM9 3.0 and Matr1x 17.0. I've had this problem since v16.5 of the kernel. Any ideas what I'm doing wrong or is it the kernel?

Aside from that, great work on the kernel. It's very smooth and fast. I only have issues with the boot. But other than that, the kernel is amazing!
[Nexus S Android Development] y3mita:
Have you tried a different ROM?
[Nexus S Android Development] aLNG:
Try reinstall again rom and kernel. This time before flash rom add also format /boot
[Nexus S Android Development] briggl:
Exactly same problem as i described two posts before.

Good to know i'm not alone!

I've tried different RoMs even on stock ICS i have this boot issue with Matr1x kernel.

Maybe others have not noticed this issue yet as i recognized it by chance.

Any suggestions to solve this?
[Nexus S Android Development] 00Droid00:
Great kernel, good work. Just have one annoying problem still. Every time I turn the screen off then back on my WiFi stops working. It stays blue in status bar but just wont connect at all. Once I toggle WiFi off on it works fine until screen is shut off. I'm using Codename rom 1.4. I've tried completely wiping phone, even sd card.
[Nexus S Android Development] Konfuddle:
I've tried again with format /boot and I still have the same issue. First boot freezes and the second is normal.
[Nexus S Android Development] mrjimyjohn:
Seems strange. I'm running the same setup as you(CNA 1.4.0/Matr1x v17) and I've definitely not run into such a problem. When you say it stays blue in the status bar, do you mean the toggle in the notification drawer, or the actual wifi icon in the status bar?
[Nexus S Android Development] 00Droid00:
Yeah the actual wifi icon. It also has a down arrow on it but will not go away cause I'm assuming it can't download anything.