yashsingh1/xdaforums huggingface dataset:
[Nexus S Android Development] The1Shark:
Checking with you guys first..

Edit :

I can overwrite this by using setcpu but I really like NSTOOLS and I don't want to use 2 apps that does the same ..
[Nexus S Android Development] omartins:
Hi there!

I'm using CFS 18.0 along with CNA 1.5.5 and really loving the way this bundle is behaving! Though, I have this small issue, which I'm not sure it's kernel related, but maybe you can help me sort it out.

With Touch Wake ON, during a call and with screen OFF, if I touch the screen, no matter where on the screen, call is immediately ended. Does anyone confirm this behavior? Any solution, work around, besides turning touch wake off?

Thanks!

RM
[Nexus S Android Development] Skunk Ape1:
What rom are you using? I am guessing NexusMV or you're using the supercharger script.

---------- Post added at 12:26 AM ---------- Previous post was at 12:08 AM ----------

Not sure it's kernel related either. it's most likely the rom...
[Nexus S Android Development] omartins:
I really can't tell it isn't a ROM issue, the first time I've experience this situation I was running CNA 1.4.0 and Matr1x 16...17.x (not really sure) and now I'm running CNA 1.5.5 (clean install though).

So far I've TW turned off, otherwise I'm always ending calls when I shouldn't.... but it is definitely an handy feature!

RM
[Nexus S Android Development] DaX05:
Try another rom & use the same setup with the kernel & see if you're getting the same results.

Beamed from my Nexus S using Tapatalk 2 beta 2
[Nexus S Android Development] mixtapes08:
Mk how's the update cookin ? :D
[Nexus S Android Development] SA-07:
??? It will come out when it comes out
[Nexus S Android Development] caliban2:
I think this means the next update is on the simmer... :D
[Nexus S Android Development] laif:
Crashes frequently

Well, release V18 of this Matr1x kernel crashes my Nexus S GT-I9020T phone frequently. It will reboot spontaneously.

I'm running Ice Cream Sandwich IML74K.

I finally found a kernel which was only modified with only Voodoo and a couple of other minor things:

http://xdaforums.com/showthread.php?t=1420542

It's Terryhau's "Simple Kernel."

That will work much better for my purposes.
[Nexus S Android Development] DaXmax:
What version yu used?
[Nexus S Android Development] laif:
Hmmm?

The version of Terryhau's Simple Kernel? I used the one that's currently posted at the top of that thread - version "1.11-voodoo." It seems completely stable.

All I wanted from a custom kernel, was the Voodoo ability to adjust the screen color on my AMOLED screen. (Why Google would omit the ability for users to control that sort of thing is beyond me. The screen is ten times more beautiful with a bit more contrast and richer colors.)

Supercurio's app for controlling the screen's gamma and color settings from a GUI is no longer on the market. It was Voodoo Control_2.1.1.apk. I can attach it here, if you want.

You can always control the screen colors from the command line using instructions that Supercurio has posted in various parts of the pages of this conversation:

http://xdaforums.com/showthread.php?t=935637&highlight=voodoo

That's what I do. I made a little script that resets the screen the way I like it each time the phone boots up.
[Nexus S Android Development] al_madd:
supercurio already state he not recomended anymore to use vodoo color..

the color from from matr1x kernel already beautiful...:):)
[Nexus S Android Development] laif:
Supercurio says that he's working on a replacement for the Voodoo color kernel hack... but it's not finished yet. The experimental app which he has on the market now only works to place a black filter on top of the screen. I assume that eventually he'll make it so that it allows a filter on various other color channels.

Screen color is a matter of taste. You may like what you have. I didn't. I like my blacks really black, and not just gray. I feel that I need the ability to make the adjustments manually.
[Nexus S Android Development] al_madd:
Ok then...we have choices to choose right??it up to you..it is about the taste i think...

For reboots problems...maybe your phone cant handle UV from matr1x kernel..try increased you voltages first...
[Nexus S Android Development] SA-07:
Please don't link to other kernels in my thread.
[Nexus S Android Development] laif:
Nope, Mathkid95, I can't accomodate you

I'm sorry mathkid95, but this is NOT your thread. This is a public conversation. I only commented here, because I wanted to inform you about a problem I was experiencing with your kernel. I thought that it was polite to do so. Do you want any more debugging information from me? I'd be happy to reinstall your Matrix kernel and then send you a copy of "adb bugreport," for example.

At the same time, it occurred to me that other people like myself may have this one particular need for Supercurio's Voodoo color tool, and might want to have a simpler kernel which is closer to stock. So, I thought it might be wise to add a note about that. Then, I answered someone's question.

I really don't understand you taking umbrage because of me pointing people to another resource.

Secondly, I don't understand the lack of any interest on your part getting information from me which might help you debug your work. I heartily thank you for your time and effort working on the Matrix kernel. It's very kind of you to share what you've done, with everybody.
[Nexus S Android Development] chalan30:
Thanks for your effort Mathkid95

glad you found another kernel that works for you, but to thumbs down this kernel and link to another kernel in THIS thread is disrespectful in my opinion. go praise terryhau's kernel in his thread. and if you want to talk about your "dislike" for the matr1x kernel do it in another thread. If you had problems with matr1x did you even post them before abandoning it?

---------- Post added at 03:05 PM ---------- Previous post was at 03:03 PM ----------

How did your initial post even begin to insinuate that you had any interest whatsoever in mathkids help?
[Nexus S Android Development] al_madd:
dislike people who being rude or flaming the devs...

this will make dev go away from xda...:mad::mad:
[Nexus S Android Development] laif:
It's only a picture in the corner of one of countless posts in this conversation. Don't be so sensitive. It's not some terrible thing.

We are all here to help each other. Mathkid is doing his part, and I wish to do mine, as well. If people hate me because I do a good deed... that's their problem. DaxIΠFIΠITY wanted some help, and I offered it. I have no use for sycophants on the net. It's not disrespectful to someone like Mathkid95 to point out where there might be problems, and to offer a solution or workaround that other people might find helpful as well. Building a kernel is a tricky business, and you need feedback from testers in order to iron out the rough points. Helping someone improve something is not the same as detracting from what they've already done.

Chalan, I obviously don't understand the social mores around here. There seems to be a personality conflict between myself and other people in this conversation and therefore I probably ought to take my leave. I don't want to sidetrack the conversation any more.

'Bye.
[Nexus S Android Development] caliban2:
WTF?!

it's bad taste to point to other projects which aim at the same thing! And afaik, no one asked you about your personal preference or a link to another kernel.

Nothing you said about v18 happens on my sys, know what that means? Not kernel related, it's your sys.

How about you, you obviously need assistance learning some manners. I'm ready to help, and if necessary, place them manually into your thick skull.

Goddamn, ungrateful leeches like you are the reason more and more devs leave xda!
[Nexus S Android Development] laif:
Peace, Caliban...
[Nexus S Android Development] mixtapes08:
@laif

Go flash what you want we don't care.

Sent from my Nexus S
[Nexus S Android Development] DaXmax:
Errr... I didnt ask for help, actually, im tryin to help yu. =_="

I was trying to help yu stay Matrix kernel as the others has perfect stability on their Nexus with v18. So i asked you, what version of the kernel u used? Not simple kernel, i dont like the kernel. As i am a overclocking junkie. ;)
[Nexus S Android Development] DarkhShadow:
Voodoo sound app still has it
[Nexus S Android Development] shohratshankar:
Hi,

Some advice needed:

If I Live OC to 110%, do I need to increase volt? And if yes then by how much?

Will that ensure stability?
[Nexus S Android Development] caliban2:
Chances are high that you have to, because matr1x already is undervolted (you need to up both arm- and int-values). But there's also a chance you won't have to. How much and if depends on your hardware, each phone has a different grade of tolerance.

Also note that you have to change in steps of 25mV, that's a hw-limitation.

And finally, give a thought to not using live-oc at all. Its advantage is that gpu gets overclocked as well, something you'll notice primarily in games. But you can compensate a lot by just upping the max cpu-freq, for example 1200 MHz. That way, you only have to deal with one voltage if it gets unstable.
[Nexus S Android Development] 4I-I:
@mathkidd Im maybe going to change to the galaxy nexus... i was wondering if you're also active in the galaxy nexus forum and in developing? That would be awesome because i fell in love with your kernel!

Sent while eating an ice cream sandwich in the matr1x!

I flash roms therefore i am!!
[Nexus S Android Development] SA-07:
I did release one for that but I abandoned it lol... so not at the moment :(
[Nexus S Android Development] DaX05:
We're modding our phones to have a better battery life & a dual core isn't going to help that cause. Why can't we have outstanding battery life on our android devices?

Beamed from my Nexus S using Tapatalk 2 beta 2
[Nexus S Android Development] sdhanjal15:
Math kid=complete genius

Sent from my Nexus S
[Nexus S Android Development] chalan30:
110 live oc has always been unstable for me at stock voltages and ive never taken the time to test higher voltages for extended periods of time. have you considered using the selective live OC feature to have the oc only apply to certain frequencies? for instance you can have live OC 110% apply to say...200-800 (so you get 100,210,420,840 while 1000 1200 1300 and 1460 remain untouched. having the oc not apply to the whole freq range may help you find some greater stability...

---------- Post added at 07:12 PM ---------- Previous post was at 07:09 PM ----------

Hey hey...Dont give him any ideas about leaving nexus S! lol :p
[Nexus S Android Development] SA-07:
I will prank you successfully!..eventually ;)
[Nexus S Android Development] chalan30:
neverrrrrrr hahahahahha!!!!
[Nexus S Android Development] shohratshankar:
Thanks a lot for the details.

If I only up the max cpu frequency and the phone becomes unstable, then which voltage should I increase? And by how much?
[Nexus S Android Development] chalan30:
which governor you use can also make a big difference because each one will ramp up to the max freq at different rates and that "jump" to the max frequency can cause instability, that, and how long they take to step down from the max freq, because the longer they stay at that freq there are more chances for instability.

my phone is ok at stock matr1x voltages at 105% live oc but then again, i dont peg my max freq, i keep the max low. but in my experience most people's phones arent stable at those higher frequencies. its ok to "visit" them but not ok to "live" there.
[Nexus S Android Development] ArnoutVos:
I've posted (by fault) my problem in the 4G forums, I have a original US Nexus. (dec-2010). So this is a crosspost:

--------------------------------------

CNA (Codename Android) 1.5.5. No scripts (I think?), just the defaults from the ROM.

Today I got another freeze. It started with a responsive phone. Then I started Google Maps (which is for me the test for this problem).

After that, for minutes the phone was totally unresponsive. Screen stays off even if you press the power button. Sometimes the screen gets one single update, which is not enough to make it readable. Multiple ANR's in Google Maps.

root@android:/ # uptime
uptime
up time: 16:09:00, idle time: 09:31:17, sleep time: 04:38:16

I noticed that besides mmcqd, also kswapd/0 is at the top of the process list (CPU Overlay, ROM feature). mmcqd and kwsapd/0 were fighting for the first position in the process list. A lot (30 or more) other processes were running (far more than normal).

And then from one second to another, all lag has gone and it's like nothing happened, kswapd is not showing up and mmcqd is sometimes showing up but at the bottom of the list (which is normal I think).

So that brings me to the topic of swapping. And indeed, a massive amount of memory is swapped out:

root@android:/ # free
free
total used free shared buffers
Mem: 362048 356732 5316 0 1980
-/+ buffers: 354752 7296
Swap: 199996 121772 78224

Which commands should I use to further investigate this problem? Maybe this is not SD card related, but a memory leak or something like that?
[Nexus S Android Development] chalan30:
wow what were you running that you used so much swap???? um have you tried disabling swap and running it that way for a while?

swapoff /data/swap

note: sometimes it seems to hang for like a minute when you run this command. sometimes it is instant ;)

other than that.... have you tried something simple like make a nandroid---then format system from recovery and reflash rom, kernel, and gapps (all while still in recovery then reboot), you will keep your data.
[Nexus S Android Development] mixtapes08:
Up.... ;)

Sent from my Nexus S
[Nexus S Android Development] ArnoutVos:
Did turn off swap yesterday and it looks like that was at least part of the problem.

I wiped the phone completely, several times (also with the ROM-wiper CWM zip), but that doesn't make sense.

Maybe that swap is more a indicator of memory (allocation) problems due to a leak or something like that. So turning off the swap makes the problem less visible, but leaves the original cause untouched (growing memory usage over time).

Before yesterday I didn't know this kernel switched on a 200MB (!) swap file, which is more than 50% of the total memory available after boot. That's a lot.

I don't understand why you would turn on swap at all at an Android device. The Android application lifecycle (kill the less used app) is a much better way of handling lack of memory. Linux' swap is at a lower level, and I personally do not prefer to have swap on top of Android' own memory management model. Is Android' memory management still working ok after enabling swap?

One question: when swap is (heavily) in use, is it normal to see mmcqd among the top processes? In other words, is mmcqd also (besides SD read/writes) used for /data/swap ???
[Nexus S Android Development] darius0519:
Hi mk thanks for the awesome kernel. It gives me the best battery experience with my phone. :)

PS can you please check this thread about enabling fast charge. I hope you can put on your next patch :p

http://xdaforums.com/showthread.php?p=24046636
[Nexus S Android Development] SA-07:
I'm thinking of getting rid of swap for 18.5. What's the consensus ;)
[Nexus S Android Development] mixtapes08:
Yup... get rid of it :)

Sent from my Nexus S
[Nexus S Android Development] sdhanjal15:
Do it

Sent from my Nexus S
[Nexus S Android Development] easye420:
Yea definitely. I'm back on 17.5 patiently waiting for an update. :) ill try what ever you come out with though. Its your choice.
[Nexus S Android Development] SA-07:
Final decision: goodbye swap
[Nexus S Android Development] afzalarsalan:
Swap was meant to be used for linux desktops. As zeppelinrox would say:
[Nexus S Android Development] sdhanjal15:
so how about that update?

Sent from my Nexus S
[Nexus S Android Development] glennkaonang:
Hi MK, is it possible to disable BLX?

If so, could you tell me how?

Thanks.
[Nexus S Android Development] Harbb:
Set it to 96 and it will basically act like stock. Set it from 97 - 100 and it will be a cosmetic change, still charging like stock. Set it below 96 and BLX will be enabled and stop charging at lower charges.
[Nexus S Android Development] Realtyem:
MK you gots a pm.
[Nexus S Android Development] glennkaonang:
So it's not possible to completely disable it?

Anyway, when we set it to 96, will the real battery charge fully? (I don't really care about the percentage though)
[Nexus S Android Development] DarkhShadow:
Our phones only charge to 96% anyway, so yes

Sent from my ice cream powered Nexus S
[Nexus S Android Development] jamrong:
this kernel work for rom 4.0.4 ?

i use this kernel always in ICS 4.0.3

review please thx before :D
[Nexus S Android Development] al_madd:
Yes...work for 4.0.4...

review for??
[Nexus S Android Development] SA-07:
Looking for a tester that knows how to use fastboot and adb. Pm me email id
[Nexus S Android Development] SA-07:
18.5 most likely coming out tomorrow
[Nexus S Android Development] fritzmann:
do you have a kernel working for cm7.2RC1 and BLN support?

thx
[Nexus S Android Development] ArnoutVos:
Disabling swap resolves the minutes-during lag, for me.

But the root cause (growing memory usage over time) isn't gone: after a uptime of 36 hours, the 'Android-system' process grows from 40M to 140M.

This leaves the device with almost no memory left for running active applications. For example, web browsing is possible (slow rendering though) but wipes out all other applications including the launcher.

Cannot determine if this is a problem caused by the ROM (CNA 1.5.5) or kernel, or just a faulty app.

Any ideas how to determine the cause?
[Nexus S Android Development] suhas_sm:
As soon as I flashed Matrix 18.0, I started getting low memory space error. Virtually left my phone impossible to handle OS. Anyone experienced anything like this before ?

Had wiped both the caches. Tried flashing it a couple of times. Same problem. Flashing Air Kernel for now and seeing if it is working.
[Nexus S Android Development] RicardoOneri:
Just wait for new version Mk is going to push it very soon (tomorow maiby)
[Nexus S Android Development] jasonmaloney:
Android 4.0.4 being pushed to AOSP :D

Go-go updated kernel source!
[Nexus S Android Development] suhas_sm:
Flashed Air kernel still the same problem. Flashed CNA 1.5.5 again. Same problem. Will do a full wipe now. No other option left.
[Nexus S Android Development] chalan30:
It's the swap file taking up space. It's not going to be in 18.5. If you go into terminal and type

su

swapoff /data swap

you can then delete the swap file which is like 195 megabytes located in data/ and 55swap script which is in system/etc/init.d. But unless you remove it from the kernel zip it will come back when you flash again.
[Nexus S Android Development] suhas_sm:
Hmmm. Nevermind I just flashed 4.0.4 :D
[Nexus S Android Development] DarkhShadow:
Matr1x V18+stock 4.0.4=OOOOMMMMGGGG

Sent from my ice cream powered Nexus S
[Nexus S Android Development] original21:
If i flash Matr1x CFS V17,5 to my stock 4.0.4 will there be any problems? Can you reflash stock kernel back (any links?)
[Nexus S Android Development] sdhanjal15:
Update!
[Nexus S Android Development] DarkhShadow:
You can flash it fine, don't have stock sorry :s
[Nexus S Android Development] mykos5:
if i do not install the widget for fast charge, it will bring me some kind of problem?
[Nexus S Android Development] SA-07:
No but you need to either use the widget or a rom setting to toggle fast charge
[Nexus S Android Development] mykos5:
ok..thanks!

i don't need the fast charge because i have my car charger modded (mod post) and it charges at 800mA.
[Nexus S Android Development] mluu921:
thanks for everything! amazing update!

The update works like a charm. Loving the fastcharge mod!
[Nexus S Android Development] RicardoOneri:
Thank's for update Mk will flash right now and test Fast Charge ( phone allmost out of battery) ! Will report soon!
[Nexus S Android Development] mixtapes08:
Thanks mk :)

Sent from my Nexus S
[Nexus S Android Development] DaX05:
Thanks mate! Running good! As usually. I'll try that widget if fast charge gets added to CM9 of course.

4.0.4 is out for Nexus S :) Says its improved the battery life.

Beamed from my Nexus S using Tapatalk 2 Beta-4
[Nexus S Android Development] ferdi7103:
Hai Math...

Thanks for your great New Kernel

I'm already flash it over Pixel Rom 1.6. ICS 4.0.4

All running well, will try for fast usb charge after batt weak

Thanks for your great work ;)
[Nexus S Android Development] sdhanjal15:
Thanks man

Sent from my Nexus S
[Nexus S Android Development] Oodie:
Using 18.5 CFS . although i have the same boot up issue ( I think that's a isue with my device ) , after boot everything's fine .

Running very smooth , on default governor & I/O , BLD on , Deep Idle on .

Thanks for the update . Will check on fast charge later .
[Nexus S Android Development] sdhanjal15:
Any other way to try out fast charge

Sent from my Nexus S
[Nexus S Android Development] SA-07:
rom toggle
[Nexus S Android Development] sdhanjal15:
Thanks man!

Link?

Sent from my Nexus S
[Nexus S Android Development] SA-07:
oh I meant like a roms inbuilt settings... some roms (like aokp or cna) have these... what rom are you on?
[Nexus S Android Development] Oodie:
isn't there a init.d script or something for fast charge toggle ?
[Nexus S Android Development] sdhanjal15:
I am on stock

Sent from my Nexus S
[Nexus S Android Development] anshulajain:
Is the latest version (18.5) safe to install on stock 4.0.4?
[Nexus S Android Development] chad0989:
Can use IncrediControl also:

https://play.google.com/store/apps/details?id=com.incredicontrol

I don't fully support the S on it, but it will toggle fast charge.
[Nexus S Android Development] SA-07:
Oh yeah I forgot about the echo command... check here for the exact one

http://xdaforums.com/showthread.php?t=1564973
[Nexus S Android Development] SA-07:
Yep!
[Nexus S Android Development] sdhanjal15:
You should change the topic to 4.0.4 so people know its safe

Sent from my Nexus S
[Nexus S Android Development] SA-07:
No I think everyone can figure it out or ask.
[Nexus S Android Development] suhas_sm:
Flashed ICS 4.0.4 with full wipe, still the same problem. That command is not working. Says

swapoff: /data: Function not implemented

swapoff \: can't start ''swap': No such file or directory

Should I do swapoff -a ?

:confused:
[Nexus S Android Development] mixtapes08:
Are you in 18.5? swap is been already removed

Sent from my Nexus S
[Nexus S Android Development] suhas_sm:
Nopes. Was in stock kernel. did the following now :

1) wiped dalvik

2) wiped cache

3) wiped data...

4) used dalvik-wiper.zip

5) rebooted RECOVERY

6) formatted system, cache and data

7) flashed 4.0.4

8) rebooted phone

9) Flashed TiBu and Matrix 18.5.

Hopefully the problem is gone. Poof!
[Nexus S Android Development] sperelli:
So is FastCharge off by default?
[Nexus S Android Development] ArnoutVos:
People who have upgraded from 18.0 to 18.5 should manually delete the /data/swap file in order to free up 200MB of internal (app) storage. I just upgraded and noticed the swap file still being present.

Kernel running fine so far.
[Nexus S Android Development] Icecoldmeat:
v18.5 runs like a charm.
[Nexus S Android Development] Jamalsid:
How can we test if the fast charge works?
[Nexus S Android Development] maxone001:
You have 2 http:// in the adress.

well... in the suggestion adress..
[Nexus S Android Development] arshad14:
Oh, I get that at times too with Multiupload. Try either using Opera browser if you don't have access to a computer or just download using the computer itself.
[Nexus S Android Development] RonnieRuff:
LOL.

Stock OTA ICS Version 4.0.3
[Nexus S Android Development] iGoogleNexus:
o.o didn't notice.. sank yu!

-Google
[Nexus S Android Development] Beako:
Are voodoo drivers included in 12.5?
[Nexus S Android Development] ranadroid:
Nope i just installed still no Voodoo. we have to wait Voodoo update i guess..
[Nexus S Android Development] SA-07:
Nope! supercurio is working on that right now ;D