yashsingh1/xdaforums huggingface dataset:
[Nexus S Android Development] qzfive:
Try raising the voltage for 1.4Ghz in Proton Voltage Control/SetCPU - I need to raise 1.4Ghz voltage by at least 50mv before it's stable for me, your mileage may vary with how much you may need to up the voltage.
[Nexus S Android Development] Sk0ly:
Haha, I had that problem with 6.5. 7 gives me the odd one, but I am also overclocked to 1.2.

Sent from my Nexus S
[Nexus S Android Development] SA-07:
Yeah mess with the voltages ;)

Pat there are instructions in ezekeels blx thread
[Nexus S Android Development] mike216:
Please explain how to,can't get above 96% and I would love to have the other4% now that I'm on my phone all day thanks to you and Frank,thanks MK nice work today

sent from my Nexus NScollab
[Nexus S Android Development] SA-07:
http://xdaforums.com/showthread.php?t=1257497

Here ya go :)
[Nexus S Android Development] mike216:
Thanks Mk

sent from my Nexus NScollab
[Nexus S Android Development] simms22:
ezekeels mod does not let your phone charge to 100%. quite opposite, it tops the phone off at 80% in order to let your battery have a slightly longer life. if you want to charge to 100% then charge until it stops(94-97% usually) then unplug and plug the phone back in and charge the rest of the way to 100% with the screen on. eventually it will reach 100%.
[Nexus S Android Development] SA-07:
Yeah no problem.

Btw I just want to ask something. It seems after version 5.5 things have been going downhill for this kernel. Lots of people have switched to different kernels. And so that's making me wonder, what am I doing wrong?

And its kinda also making me reconsider supporting the ns. Idk, just wondering since nobody uses this kernel anymore...
[Nexus S Android Development] SA-07:
Ohh yeah i forgot Lol

Sorry Mike, do what simms said. I forgot bout that haha
[Nexus S Android Development] morfic:
It's still the favorite kernel for many, since you pack anything you can find in it, including stuff i will flat out not do. put your kernels on goo.gl links (if you aren't already) and check how many downloads you get to have an idea how many exactly constitutes "nobody"
[Nexus S Android Development] SA-07:
I mean that was an exaggeration but lot of ppl have switched haha
[Nexus S Android Development] insomnia48:
Well, a lot of people, including myself, are using this kernel with NSCollab #39, which was superb with 5.5 and 6.0. But 6.5 and 7.0 were problematic with that version of the rom. I tried a few times to install 6.5 and 7.0 on #39 but to no avail! So I waited until the rom got updated, and I have to say that we are back in business now! For me personally #40 and 7.0 are a big step forward.

You and Frank did it again! Thanks!!!
[Nexus S Android Development] mike216:
Could you post 5.5+ so we can throw it on top of 1.0.40

sent from my Nexus NScollab
[Nexus S Android Development] SA-07:
Take his boot.img lol
[Nexus S Android Development] mike216:
It seems there weren't issues until you added Ezekiels mods and then only were there some issues,I wish I could suggest something bit your the genius that I depend on.lol..I have had nothing but great experiences with your kernels and I've tried them all,I would really appreciate it if you continued your work here.I feel confident that you'll for find the bug that's found its way in after 5.5 so please don't get down because I'm sure they will be back when they find the grass wasn't greener

Keep it up and don't get discouraged but use it as motivation,thanks MK

sent from my Nexus NScollab
[Nexus S Android Development] SA-07:
Haha ok, ill try to make everything better next update
[Nexus S Android Development] NicholasQ:
Hmm, Mike216 has a good point. Is it possible that adding those mods introduced a couple of bugs?
[Nexus S Android Development] mike216:
It seems like previous miui users experience weird problems who knows what those roms could have introduced,I haven't had a single hiccup and been running matrix and nscollab a while now,

MK check cyanogen mod comments in rom manager everyone says running with matrix fast and stable (that's your rep)check it out,that should be a good motivater

sent from my Nexus NScollab
[Nexus S Android Development] SA-07:
Nicholas, I don't think so...
[Nexus S Android Development] mike216:
Also I don't like to use set cpu because I don't want to many things controlling my voltages that's why I requested 5.5+ to flash over 1.0.40,don't really know though just my op

sent from my Nexus NScollab
[Nexus S Android Development] SA-07:
I told you how to do it like 20 times :D

Take his boot.img, then go

fastboot flash boot boot.img

And it should work
[Nexus S Android Development] mike216:
Let me make this crystal clear.I'm not saying anything bad about Ezekiels mods but maybe you missed s work around or something

sent from my Nexus NScollab
[Nexus S Android Development] SA-07:
I really don't think his mods have any effect... I've made sure to include all the right files as well
[Nexus S Android Development] mike216:
I told you 20 times I don't know where the boot.img is but that's ok,ill figure it out

sent from my Nexus NScollab
[Nexus S Android Development] SA-07:
It's in the root of the zip. Download the zip, and it should be right there.

You can just pull the img out as well
[Nexus S Android Development] mike216:
Oh ok sorry I was looking in system bin,kernel basically everywhere besides there thanks for your patients but take it easy on is noobs

So the only way to install is going in bootloaders and fastboot flashing it no root explorer way to install

sent from my Nexus NScollab
[Nexus S Android Development] SA-07:
Yeah Haha, its an img file ;)
[Nexus S Android Development] generalagony:
Or charge with your hotspot turned on. That gets me to 100%
[Nexus S Android Development] SA-07:
Oh ok, I didn't know that. Thanks for sharing!
[Nexus S Android Development] insomnia48:
Is the smartass governor the new version 2?
[Nexus S Android Development] Sk0ly:
Mathkid please don't stop development. I love this kernel, it is so much faster at opening apps than netarchy, even if it its a little less stable.

Sent from my Nexus S
[Nexus S Android Development] eiabea:
you can't stop developing!! which thread at xda should i then read at work? :D

So here an interessing mod ;) --> http://xdaforums.com/showthread.php?t=1271792

maybe you can implement it :)

OFFTOPIC: are you guys all from the other side of the world?? everytime i am online, i am alone ^^

i am from europe/austria, not australia, no kangaroos :D
[Nexus S Android Development] SA-07:
Yeah ill get that governor in next update
[Nexus S Android Development] SA-07:
No I can add it tho
[Nexus S Android Development] gioyann:
Mat, don't kid us! Your kernel is the smoothest and fastest by far!
[Nexus S Android Development] dario3040:
We probably have the same time zone then. :rolleyes:
[Nexus S Android Development] ~Reaper~:
i have installed this 2x and it puts my phone into a boot loop

why is it not working
[Nexus S Android Development] ikhtiaralam:
Yeah, he's right. Yours has a good balance of everything. There are just ignorant people who don't know how to use profiles on SETCPU. ;).
[Nexus S Android Development] markywylder:
Hey Mathkid, just so you know, apparently your 7.0 is rockin' with MarkVis' ROM. I suggested he drop back a release and wait for 7.X and he said this. Not bad.
[Nexus S Android Development] Arkaknio:
No internal storage after flashing v7.0. My /sdcard just gone. I can see it onto recovery but not in Android.

Any idea? lol
[Nexus S Android Development] ~Reaper~:
i cannot figure out why my damn phone will not boot

i have wiped cache and everything and tried flashing 3x

same thing everytime
[Nexus S Android Development] UniqueNate:
As always, I come back and Math has upped it again. 7.0. I guess I should take my precious NS4G out the box and flash this speedy kernel of yours.
[Nexus S Android Development] Sk0ly:
Did you install over top of another custom kernel like netarchy? I seem to have problems when I flash on top of anything but the stock cm7 kernel

Sent from my Nexus S
[Nexus S Android Development] NicholasQ:
I like to flash the wipe dalvic cache zip 3 times, wipe cache 3 times, flash kernel, power off in recovery. pull battery for 2-5 minutes. Boot phone. Sounds tedious I know, but I like to make sure it's super clean and ready for something new. :D
[Nexus S Android Development] SA-07:
Do what Nicholas does LOL
[Nexus S Android Development] reddv1:
I think all that stuff is pointless. Dalvik-cache is a cache of the dex files that are in your apps, it should only be wiped if your flashing a theme, modded app or rom. Cache doesn't ever have to be wiped, it's used only when downloading apps from the market temporarily, sometimes has the dalvik-cache of the system apps in custom roms and most importantly has a log of your recovery activity which can be used to see what went wrong when flashing. Rebooting is enough, pulling the battery and waiting is just a waist of your time. The only thing I can think of doing before flashing a kernel is formatting the boot partition, but most likely unnecessary.

Sent from my Nexus S
[Nexus S Android Development] SA-07:
Yeah I mean its just a precaution ;)
[Nexus S Android Development] dark79:
No problems with this kernel, but I'm hoping for an update with new governors. Hoping the next update has at least SmartassV2, but SavagedZen (if it's even available on NS - I just came from the N1) or the new Snappy governors would be cool too.
[Nexus S Android Development] SA-07:
Yeah don't worry those are coming ;)
[Nexus S Android Development] SovereigN7:
Nooo, 7.0 just rebooted itself on me while on rest. I'll try upping the voltages later.
[Nexus S Android Development] SA-07:
Cool
[Nexus S Android Development] supralover72:
How's the battery life on 7.0 compared to 1.3.7 CFS netarchy?

I came from the Evo camp so I'm a pretty diehard netarchy man and have been getting AMAZING battery life, but the continued support and updates for Matrix are making me itch to switch.
[Nexus S Android Development] albundy2010:
Don't give up on it.

A suggestion. Make a kernel with stock voltage for testing. Can help figure out what may be causing issues.
[Nexus S Android Development] :
Well, my with first normal-use test I'm down to 30% after 26 hours. Using 7.0 CFS with interactive 100/800 MHz, and CM7-201 nightly.
[Nexus S Android Development] synaesthetic:
I'll chime in here a bit.

I actually used this kernel on the NS4G, but it caused instability and other problems--I ended up returning that device. I've used it on my T-Mobile NS, but I eventually settled on netarchy's kernel.

It looks like netarchy's gone to the SGSII, however, and I'm thinking about going back to Matr1x as a result. The stability of the kernel seemed to be less than that of netarchy's, though. Perhaps that has changed since v5.5, but I had some issues with it, which prompted me to use netarchy's instead.

Personally I think a lot of these custom kernels just have too much stuff in them. I like netarchy's because it's basically just a kernel with OC/UV support, Voodoo tweaks, BLN and smartass. That's pretty much my NS kernel wishlist, though I wish the smartass was tweaked to let the CPU clock go higher with the screen off, so MP3s would stop with their occasional skipping.
[Nexus S Android Development] SA-07:
Ok cool!
[Nexus S Android Development] synaesthetic:
Since the CM7 nightlies just went to 2.6.35.14 and netarchy seems too busy with the SGS2, I suppose it's either your kernel or morfic's, so it's time to play kernel test-drive again. :D
[Nexus S Android Development] synaesthetic:
Quick question: is the BLX enabled or disabled by default? This phone doesn't get stellar battery life to begin with, and I don't want it charging less than 98% (the maximum for my particular NS).
[Nexus S Android Development] SA-07:
No it's not enabled by default lol
[Nexus S Android Development] Tzorg:
Mathkid,

Your kernels for NSCollab are superb. 5.5+ only gave me the occasional bootloop and 7+ on NSC40 looks very stable. A bit weird that boots at 200-1000 rather than 100-1000 though, is that on purpose?

I don't like the fact that I cannot tweak voltages with Trinity, so I'd rather use yours.

Thanks and keep them coming :)
[Nexus S Android Development] SA-07:
Yeah Frank wanted a 200 min
[Nexus S Android Development] SA-07:
Guys,

to get more stability u mind if i get rid of 940Mhz? Does anybody even use it??
[Nexus S Android Development] qzfive:
I don't - I tried 940Mhz vs 1000Mhz and personally found no difference in performance/battery life, other people's mileage may vary.

Also, to me, it doesn't really make much sense to have an extra frequency a little bit below default max.

Just my opinions :)
[Nexus S Android Development] SA-07:
Haha ok, thanks for ur opinion!

I really think the 940 Mhz is a major player in the instability, so I really want to get rid of it
[Nexus S Android Development] insomnia48:
Spot on! IMO the 940 MHz frequency might just be the sole reason for instability.
[Nexus S Android Development] qzfive:
Are you implementing (or thinking of implementing) the Snappy and SmartassV2 governors in your next release? I'm trying the new stock CyanogenMod kernel that has SmartassV2 as default and it seems to do well keeping the CPU speed low when with the screen off, although I haven't had the chance to do a "real world" test of battery life v performance yet :(
[Nexus S Android Development] Tzorg:
I tried 940 with your 7 kernel when I was on NSC39 with not much luck.

In fact I was quite relieved to see that 7+ didn't have it. As far as I'm concerned, you can get rid of it :)

I normally do 100-1000 on battery or 100-1200 when charging.
[Nexus S Android Development] SA-07:
Ok then! BAM! Gone!
[Nexus S Android Development] insomnia48:
Does that mean you are bringing back 1300 MHz?
[Nexus S Android Development] SA-07:
Uhh it's in here already lol
[Nexus S Android Development] insomnia48:
Oups! :o

Well, 6.5 and 7.0 wouldn't boot on NSCollab 1.0.39 so I waited for NSCollab 1.0.40 and I went straight to 7.0+ after 6.0. So I didn't know that you included it in 6.5 or 7.0 LOL. I thought that in the + versions you replaced 940 with 1300.
[Nexus S Android Development] SA-07:
Hahaha no biggie, this update I am working on will be stable, don't worry. It was the 940Mhz that was causing instability
[Nexus S Android Development] al_madd:
love this kernel.....:D
[Nexus S Android Development] SA-07:
Ok guys, kernel update.

Things seem to be a bit more stable now....

I have went back to 1.44 Ghz, and as you know it's not a stable speed and it's VERY tough to find a standard voltage for it. So I made my best estimate for a stable voltage and if it's not stable, just tweak it up and find one.

Thanks!!!
[Nexus S Android Development] king23adrianc:
smartassv2.. nice

and u didnt reply me bak after ur sudden pm :eek:
[Nexus S Android Development] SA-07:
:eek::eek::eek:
[Nexus S Android Development] king23adrianc:
:eek::eek::eek::eek::eek::eek::eek:

i m mad!

:mad:

lol
[Nexus S Android Development] mike216:
Please get rid of 940 and keep it simple at 1000,1200,1300.1400 just my opinion your the man MK so will go with your best judgment
[Nexus S Android Development] SA-07:
Hahaha

just another point to make:

I have set the voltage to 1420. The max is 1500, so I have given a lot of space to try things out. Some people might need only +20, while others need +50...

So just try things out and see!

thanks!
[Nexus S Android Development] SA-07:
The 940 is gone dude lol
[Nexus S Android Development] mike216:
Where can we find stock voltage settings to be sure I don't go over stock and in the new 7.5 are the voltages for 1000,1200 stock or lower as I'm on nscollab and you know how that goes with the voltage settings
[Nexus S Android Development] king23adrianc:
WOW SIMMS22... that just scared me now LOL
[Nexus S Android Development] SA-07:
1 Ghz 1250000

800 Mhz 1200000

400 Mhz 1050000

200 mhz 950000

100 Mhz 950000
[Nexus S Android Development] SA-07:
Yes, it scared me too. :eek:
[Nexus S Android Development] mike216:
Those are stock,thank-you MK
[Nexus S Android Development] SA-07:
Yeah no probs
[Nexus S Android Development] simms22:
i scared myself too :p
[Nexus S Android Development] SA-07:
hahahaha :D
[Nexus S Android Development] mike216:
I've never had any issues with your kernels but do you think the few who have had issues should try the script cleaner provided in nscollab op,do you think that's necessary before a rom flash I've only ever ran nscollab and oxygen and as I stated I've never had any weird issues besides a reboot around every 40 days since being on nscollab so there is something else going on for some who were talking about issues or they have something else up there sleeve that may not ne nice I've seen it on the vibrant forums.I'm sure some experience issues once in a while but who really knows,is the script cleaner doing anything the rom install isn't ,thanks in advance
[Nexus S Android Development] SA-07:
I never use it haha

I mean you CAN, and I think it might help. So go ahead and use it, but just wipe dalvik cache as well
[Nexus S Android Development] synaesthetic:
Ooh, new version!

*scurries off to flash*
[Nexus S Android Development] SA-07:
Hahaha go for it!
[Nexus S Android Development] markywylder:
I'm pretty sure anyone who has any problems must be getting them from something they've done individually on their phone. I know that personally I always, 99 percent of the time trace my problems back to some stupid thing I didn't think of and when I fix it, it works. Even if its driven me nuts and I'm SURE I did everything right, then.....ooooooohhh yeeeaaahhhh. ****. Should've done my own research before giving the dev ****. Lol If 10,000 people have an issue, its probably the ROM. If 50 people have an issue, time to do some housekeeping.....been using .40 with 7.0 and man, this combo

Kicks

Some

Ass.

Just sayin'.
[Nexus S Android Development] SA-07:
Hahaha ok, try this version out and let me know!
[Nexus S Android Development] markywylder:
7.5.....man I'm getting old I can't keep up with you mathkid!

XD
[Nexus S Android Development] SA-07:
Yeah, there really aren't any HUGE updates with kernels haha
[Nexus S Android Development] markywylder:
I know huh? You write a few more lines into your build and have us running around flashing and rebooting and going nuts LOL you're lovin' it aren't ya ;)
[Nexus S Android Development] markywylder:
OK so just flashed 7.5 and everything a-ok except when I open CPU settings in cyanogenmod settings getting a force close. Fixed permissions, rebooted twice, same thing. Ideas?
[Nexus S Android Development] SA-07:
Can you try flashing another kang or something?
[Nexus S Android Development] markywylder:
Just wiped cache dalvik fix permissions in recovery same thing. Flashing a kang now
[Nexus S Android Development] albundy2010:
Each phone is different. Saying that since it runs on your device anybody else having issues doing something wrong is just foolish.
[Nexus S Android Development] markywylder:
was that directed at me? I certainly wasn't saying that since it works on mine everyone else is doing something wrong...you misunderstood. If you read, you'll see I said things go wrong on mine all the time, case in point: right now lol. it's just a matter of finding out what it was :)

But, if that wasn't directed at me, I apologize. :)

---------- Post added at 01:38 AM ---------- Previous post was at 01:35 AM ----------

So Mathkid, I just did a full wipe, flashed a CM7 Kang, flashed 7.5, rebooted, still got force close on only the CPU settings in Cyanogenmod settings. Wiped all again, restored a backup of latest NSCollab with 7.0 and good to go.
[Nexus S Android Development] albundy2010:
Yes it was mark. "I'm pretty sure anyone who has any problems must be getting them from something they've done individually on their phone." I am not here to argue or anything. Just saying that line is absurd.

Most people here actually know what they are doing with their phones if anything. We know what we are doing and know when the kernel is at fault. Even mathkid himself was saying there was stability issues with the recent kernels.

Anyways again I do not wish to fuss about it. Just that opening line urked me thats all.
[Nexus S Android Development] demo23019:
So far so good been running 7.5. @ 1.3/100 snappy gov for few hours now ran few bench and played modern combat 2 for about hour no locks or reboots *knock on wood*
[Nexus S Android Development] synaesthetic:
No force-closes?
[Nexus S Android Development] markywylder:
I do not wish to fuss either :)

Fuss only comes about when someone pays too much interest to linguistics and not enough to the "overall meaning" of a statement, and a misunderstanding ensues. And alas, to assume I'm not aware that people here do know what they're doing is also "absurd". See how this nitpicking thing is useless ? LOL sorry if I offended you mate!

:)
[Nexus S Android Development] markywylder:
Yes...has anyone else had the force close problem that I speak of in particular, with the CPU settings in Cyanogenmod settings?

Edit: fixed the problem using setcpu. If anyone else has the same problem ill tell ya the fix :)
[Nexus S Android Development] synaesthetic:
I use setCPU anyway so I didn't notice, but I just checked in the CM settings and it's not force-closing.
[Nexus S Android Development] demo23019:
Seems to have issues with no frill CPU OC utility also. Opened fine couple times to set clocks. Later i tried to open again and just sits on black screen without option. If i leave it it will forceclose

Reinstalled app cleared cache..ect no go
[Nexus S Android Development] mike216:
How did you fix your cm force close issue with set CPU,just curious
[Nexus S Android Development] :
@mathkid95 Hi. How about latest Cm7 Kernel improovement. will you merge them all?
[Nexus S Android Development] synaesthetic:
CM settings doesn't force-close for me, but this kernel doesn't seem to like the browser. It'll fail to load and crash to homescreen (no force-close error) and continue to behave this way until I reboot. This fixes it for a while, until the phone idles for 20-30 minutes, and then the browser starts acting up again.

Google Reader app exhibits the same problem. Any ideas?
[Nexus S Android Development] SA-07:
Try a different browser, like the dolphin one...

Pat, what was merged?
[Nexus S Android Development] :
You Can check cm7 202 and 203 changelog
[Nexus S Android Development] SA-07:
Oh i didn't check that at all lol. I'll look at it haha
[Nexus S Android Development] markywylder:
I made it sound more like I knew what I was doing lol

It seems there is something that setcpu does at root level that fixes this problem I have. I'm trying to hunt it down. When the app is installed, and only after root access is permitted by me, I am instantly able to access cpu setting in cmsettings. Not if i deny root access. I uninstall setcpu and am still able to access it for as long as i have my phone on but after rebooting I get the same force close problem as before setcpu was installed. I've tried just rebooting only, and rebooting after a wipe. Same results. It must be something in the cache or a running process or something.

Can anyone else NOT using setcpu see if they have the same issue?

I don't know how to use logcat but will look it up and do a couple of them.
[Nexus S Android Development] SA-07:
Oh interesting..
[Nexus S Android Development] markywylder:
Also just flashed 7.5 over NSCollab .39 and same thing.
[Nexus S Android Development] SA-07:
Ohk cool
[Nexus S Android Development] rockb.blues:
Hey mathkid love your work!

I was wondering if you could point me in the right direction. I use miui, the latest, and I have always used on demand and have gotten solid performance at 940 or 1000. I wanted to try some of the other governors and I was wondering if you could suggest which to use for battery conservation.

I'm currently using smartass v2 and its working great but I'm not sure if its better than on demand in terms of battery. Not very savvy in terms of kernels so any help would be amazing.