yashsingh1/xdaforums huggingface dataset:
[Nexus S Android Development] atl4ntis:
Not like the battery will go from 100% performance to 0 in one day, it will perform worse during the months and some day you have to replace it. To me 10 hour life in aero mode and 0 apps means probably a bricked battery
[Nexus S Android Development] debaj:
Sure, it isn't normal.
[Nexus S Android Development] mejobloggs:
Brand new phone. Maybe dud battery? Might try buying a new battery
[Nexus S Android Development] debaj:
Then wait for a few power cycles, if it does not solve the problem, then try to replace it in warranty.
[Nexus S Android Development] insomnia48:
+1
[Nexus S Android Development] mejobloggs:
Power cycle as in, full charge to 0 charge a few times?

And sorry, used incorrect phrasing. I meant to say my phone has been like this since brand new. Hasn't degraded over time just always sucked
[Nexus S Android Development] caliban2:
Check if your phone sleeps properly then or if something keeps it busy during standby.
[Nexus S Android Development] gabling23:
What are the sleep and awake freq? Now I m using these settings and my nexus is very smooth.. now I'm testing battery life

Inviato dal mio Nexus S con Tapatalk 2
[Nexus S Android Development] sdhanjal15:
Actually not sure but my guess I'd that the sleep freq is for when you phone is sleeping and awake would be where you want you phone to be when you using it.

Hope you get some good results
[Nexus S Android Development] Blackcrx:
can someone please post the stock kernel voltages? i was playing with the voltage settings and now i dont remember what the factory voltages were

i tried re installing the kernel but it kept the old voltages
[Nexus S Android Development] chalan30:
It's been posted here before, do a search. I don't know them sorry
[Nexus S Android Development] micha3lvd:
Just uncheck keep settings at boot in nstools (last page) and it should return to stock values
[Nexus S Android Development] omartins:
Hia!

I've been running 19.5 CFS since it came up, using ondemand+noop without OC and have to say... great performance/battery, IMHO the best around the competition!

The only issue I found still being with Touch Wake when settings\accessibility\power button ends call is checked. With this combination I cannot touch the display during a call, otherwise it will be immediately ended. Solution so far is to uncheck "power button ends call"

RM
[Nexus S Android Development] abbysingh:
Hey! I've was using matrix when it was on on version 6 or 7 maybe, about a year ago. Then I switched to stock. Now, I just flashed aokp a few days ago and flashed matrix with it. I got a few reboots so I increased all the voltages by 25. The phone is running fine but I'm still getting reboots when I run the facebook app. Everything else works fine.
[Nexus S Android Development] sdhanjal15:
Life is complete!
[Nexus S Android Development] ejatds:
wtffffff?

how :mad:
[Nexus S Android Development] lupoalberto12:
Percentage battery?

How :confused: ?

Bye!

! :) !
[Nexus S Android Development] sdhanjal15:
Cyber gr mod v12

Smart ass governor

Noop

No over clock.
[Nexus S Android Development] Blackcrx:
Smart ass settings?
[Nexus S Android Development] insomnia48:
Hey mathkid, CM must have changed something in the latest nightlies in the USB mounting implementation. USB Speed when you copy files is extremely slow with your kernel, about 128KB/s.

Have a look at it when you have some time.
[Nexus S Android Development] sdhanjal15:
Look a couple of pages back...
[Nexus S Android Development] sdhanjal15:
How did it go?
[Nexus S Android Development] derekwilkinson:
what does that have to do with the kernel
[Nexus S Android Development] Skunk Ape1:
Use rom toolbox to raise your transfer rate.

But the fastest transfer rates are available only in recovery. Plug your phone into the computer while in recovery. Then navigate to mounts and storage and choose mount usb storage. The computer will auto run asking what to do. You get much faster data transfer rates like this.

_______________

Just Flash It !!!
[Nexus S Android Development] thuanngotau:
What is your performance setting?
[Nexus S Android Development] sdhanjal15:
There ya go

Coupled with smart ass and noop
[Nexus S Android Development] insomnia48:
It has to do with the kernel because speed is normal under the CM kernel. And before you say something like try a full wipe, I assure you that I have backed up my configuration and then runed multiple tests with the last couple of nightlies, everytime formatting everything including system.

And to be frank, I just can't understand what your problem is. I simply posted a request to Shankar to check it out when he has some time. I didn't bash his kernel and I never will, I have been a happy continuous Matr1x user since version 5.5 last August. I just wanted to inform him on a possible glitch, which as I have already said, was not caused by him.

I know that it is much faster in recovery and that is the method I use when transferring large files, but I don't think I have to boot into recovery just to transfer an mp3. Plus, it was working fine before. And as I have said above, the speed is acceptable when the CM kernel is used.
[Nexus S Android Development] N_E_X_U_S:
hi, what is this tool?
[Nexus S Android Development] sean1984:
https://play.google.com/store/apps/...=W251bGwsMSwxLDMsIm1vYmkuY3lhbm4ubnN0b29scyJd
[Nexus S Android Development] N_E_X_U_S:
what is the best configuration for the better performance?
[Nexus S Android Development] rickbosch:
Codename Android RC2, Matr1x 19.5 CFS, Ondemand, 100/1000, Deadline, Deep idle on. Wow.

Whenever I flash matr1x I end up wondering why I left.
[Nexus S Android Development] Dukko:
I have an issue with matr1x and AOKP.

Ever once in a while, process.gapps.core starts crashing, resulting in a mass crash and unusable phone.

I found out that usually reflashing AOKP and gapps fixes it, but it's a pain in the ass to do every couple days.

Anyone else has this problem? Any advice? :(
[Nexus S Android Development] chalan30:
haha i thanked you when i meant to reply ;) anyway. I have never had that issues with AOKP and it has been my rom of choice for many months. when you first flashed it did you do a full wipe? which rom were you coming from? Its not the kernel that is doing that though. Matr1x and AOKP is really a really solid combo in my opinion.
[Nexus S Android Development] chalan30:
These are my speeds on the 5/18 euroskank kang. im not sure whats wrong with your setup because its not CM9 or the kernel.
[Nexus S Android Development] Dukko:
I'm not the only one having this (check out the AOKP topic on Nexus S General for another case) and I'm actually sure that there's some incompatibility between Matr1x and AOKP, at least on my phone. I flashed AOKP doing a full wipe, coming from Cyber.GR, but again, factory reset + wipe + everything in CWMR ;)

I think it's a permissions issue, although it's not always fixed by fixing permissions.

I narrowed down the issue to Matr1x, because every other kernel I tried don't give this error.

I'll stick with AIR for now, even if I really liked battery and performance on Matr1x, but hey, if anyone knows the possible cause... :o

A thank is always welcome :D
[Nexus S Android Development] chalan30:
the thing is, if many others are not having this problem with matr1x and AOKP (including myself) then how can it be matr1x? Are you still using a theme? Also, why dont you post in AOKP's thread? Or did you already? thats not really a question for general.
[Nexus S Android Development] Dukko:
AOKP thread is in General, and yes, I already posted there ;)

I'm not saying Matr1x is bugged, I was just pointing out my issue, wondering if it was a known issue or not.

Even without theming (I recently flashed AOKP b36 and the theme I loved isn't ready yet) it happened, so it shouldn't be a theme issue.

Again, I love Matr1x and I know it's a really rare bug, but hey, bug reporting ;)
[Nexus S Android Development] chalan30:
Ah ok. well that is strange issue, ill have to try and follow the thread a little more. btw have you tried kangyu yet?
[Nexus S Android Development] Dukko:
No, for now I'm really satisfied with normal kang. Thanks for the advice though ;)
[Nexus S Android Development] bsanto9:
How do I get noop or what is it
[Nexus S Android Development] Dukko:
Download NSTools and edit Scheduler there.
[Nexus S Android Development] derekwilkinson:
it's definitely not the kernel if air works since air is just a kanged kernel based off matrix
[Nexus S Android Development] Dukko:
That's good (and bad) to hear.

Then I have no clue. All I know is that on AIR it doesn't happen, while on Matr1x it does O.o

I'll post a logcat I took during one of the cascade of crashes, if helps.

https://www.dropbox.com/s/5kapogrx1zic2im/alogcat.2012-05-10-23-29-56+0200.txt
[Nexus S Android Development] derekwilkinson:
i'm guessing u have an app installed that is messing with it so do a clean install of cm9 and matr1x don't install anything and see if it happens
[Nexus S Android Development] Dukko:
I thought about it. I did a clean install of Cyber.GR and still happened.

Then I moved on to AOKP, clean install, again crashes. :mad:
[Nexus S Android Development] TransWarp:
Well, you're not alone with the issue. I kept gettingt that too when I was on AOKP M5/Matr1x. I spent days trying to figure out why Android would spontaneously think the filesystem was in read-only mode when, in fact, it wasn't.

After the third flash/setup, I gave up on AOKP and went back to CM9 Skank/Matr1x 19.5cfs. No more com.android errors. I recently decided to try AOKP again, but this time, KangyU. KangyU is amazing. I haven't been brave enough to flash Matr1x yet but the stock kernal seems to be fine (despite missing some Matr1x goodies)
[Nexus S Android Development] chalan30:
Kangyu + matr1x is pretty rad. Definitely worth another try. fwiw
[Nexus S Android Development] derekwilkinson:
tl;dr guy doesn't wanna use matr1x anymore but wants to stick around and complain
[Nexus S Android Development] nodstuff:
I agree. You are a stupid user.

Math kid is very helpful, even in re releasing 12.5 he put in a lot of work so people could enjoy his kernel, people who prefer his kernels because of the way he looks after them and their problems. He doesn't get paid for this and donations are your own choice. Its not his fault your phone doesn't like custom voltages. Some phones don't. Deal with it.. now go away and stop trolling.

Every one else thinks his work is great, one insignificant troll changes nothing.
[Nexus S Android Development] heroheto:
Unfortunately. Everytime I run mixing music player, my name phone reboots... I hope this hekps

Sent from my Nexus running stock 403 rooted.
[Nexus S Android Development] albundy2010:
Mathkid or any other dev does not have to release a kernel with the official stock voltages. He/They are not google/samsung and are required to have a setting that works for every single phone or usage pattern.

He wants to release his kernels with a UV. You want a kernel with stock. Use another kernel then. It is that simple.

Who do you think you are to basically demand stock volts? All this learn from other people nonsense is a flat out insult.

I
[Nexus S Android Development] cpaixao:
Applying an cooler is not the only way to get temperatures down on a hardware. Android itself is able to manage clock and governor for different situations, and, guess who is the guy behind that management... (bluff surprise now), KERNEL!

And add some voltage is not so dangerous. You do it all the time when Developing an component . Components gives many clues about what it can/cannot take.

I think to live is more dangerous than OC something... lol

Finally, i dont think we are trolling the MK thread, since OC may be a very common doubt for non-specific-expertise users.
[Nexus S Android Development] SA-07:
You're not trolling ;D

Its good discussion stuff
[Nexus S Android Development] athanaso77:
Any ETA for v13?
[Nexus S Android Development] benrees21:
1st rule: Never ask for ETA's!

Sent from my Nexus S on NexusBeam ROM, Morfic's Test TEUV ICS Kernel and some help from Tapatalk!
[Nexus S Android Development] ashkan_mc:
Are waiting for voodoo sound !
[Nexus S Android Development] dark79:
Same here. YouTube crashed on playback of anything.
[Nexus S Android Development] albundy2010:
You can use voodoo sound without it being built into the kernel. Just need root and the voodoo app. For colors you need it baked into the kernel.
[Nexus S Android Development] Pikkuhannu:
i9023 and works great, only video no work.

Matr1x user since GB, and hopefully Matr1x user whit next version (jelly?:D)

Keep up good work!
[Nexus S Android Development] KBanause:
I just wanted to write the same :D
[Nexus S Android Development] Xhaotic:
Something that never ceases to amuse me is when ppl dont take into consideration that just cuz two phones may be the same brand and make, doesn't mean they will operate identically.

No trolling here but in my personal exp with matr1x kernels its been a better expo vs glados. But that's neither devs faults.

Glados overheats my screen and hardware. I blame Samsung/Google for that.

Neither one devs work is better than the others but rather a personal preference.

If you can't contribute to their work with positive feedback, say nothing at all and stick with what works for you.

I personally tip my hat to mathkid for being the beast that he is, and consistent with his work.

---------- Post added at 05:26 PM ---------- Previous post was at 05:20 PM ----------

Delete youtube via root explorer and download/install fresh copy of this. won't turn up in market either way but at least it'll work. Fix for youtube and matr1x coming in v13 as stated so many times before, just be patient :)
[Nexus S Android Development] onasri15:
As soon as I turn my screen off it restarts. How do I fix this? Same thing happened with glados 2.1. Someone please help :)
[Nexus S Android Development] nodstuff:
Raise voltages maybe. What settings are you using? Oc etc?
[Nexus S Android Development] onasri15:
I'm using stock voltages. No OC, deep idle off because it doesn't work. Any other ideas?
[Nexus S Android Development] RonnieRuff:
I wonder how many of those that complain and say I am leaving your kernel for another ever donate or say thanks? Devs mostly hear people complain. Merry Christmas I guess

Since 2010 offered 22 thanks... mmmmm

Stock ICS OTA 4.0.3
[Nexus S Android Development] aic719:
Okay for one MK is a really good dev and if you don't like his work just quietly switch! Let me remind you'll that most of everyone here is enjoying his work for free! And he said he will address the problems in the next release and he simply asked you'll to use another kernel till he can release v13! Its not like he is telling you'll to f*ck of completely is he!?

Oh and btw MK awaiting v13 impatiently :)

Sent from my ice creamed Nexus S sandwich
[Nexus S Android Development] SA-07:
Lol, it might be a while ;D
[Nexus S Android Development] chronophase1:
Smartass v2 noop screen on and wheatley screen off, my phone has never idled so well. Its odd because I haven't changed any of my apps and my phone isn't waking up like it was before. My awake and screen bars are how they should be. Damn near equal. :)
[Nexus S Android Development] jasonmaloney:
Do you have one for the NS4G?
[Nexus S Android Development] SA-07:
I may be out of updates soon... :/
[Nexus S Android Development] Sejmir:
still its enough xd matr1x>all
[Nexus S Android Development] apatal:
Don't stop now! 3.0.32 kernel released by Linux.org. :D

Sent from my Nexus S
[Nexus S Android Development] Nuclear_Geko:
I'll try with disabled DIDLE... I've had 1 day and 12 hours of battery life with barely 2 hours of screen usage (I9023 with SLCD)... :(
[Nexus S Android Development] sdhanjal15:
Noooo!!!
[Nexus S Android Development] caliban2:
Looks like noop doesn't play nicely on my phone/setup, always produces crashes while listening to music (Google play music). Doesn't matter if I use it with lazy or smartassv2, didle always on. Didn't test without didle, because on deadline everything is working fine.
[Nexus S Android Development] glennkaonang:
That's awesome already, man!

Remember it's a smartphone which connects to the Internet continuously.

Having it stands more than a day from a single charge is great.

Don't expect to get more unless you disconnect the mobile network, or leave it on inside your drawer.
[Nexus S Android Development] Nuclear_Geko:
I see..

@Mat: I've found the lazy governor to be buggish.. it makes my phone signal not work comin' from AirPlane mode... not all the time but you have to reboot the phone. Now I'm testing noop+smartassV2 :)
[Nexus S Android Development] chronophase1:
Haha. +1 to that!
[Nexus S Android Development] mejobloggs:
Same with me, but using deadline. I fixed it by turning didle off, or raising 100mhz int college to 975
[Nexus S Android Development] mejobloggs:
How do you set the screen on/off profile?
[Nexus S Android Development] jimdem:
I had some issues with AOKP b35 and matrix using smartassv2 and noop. So i changed to ondemad/deadline and is much more stable now. Flickering in music is gone. Also the battery seems a little bit better. As for the speed, 100/1000mhz deep idle on, 95% up threshold and the phone is literally flying!!! Fantastic job ;)
[Nexus S Android Development] caliban2:
if that means noop+didle doesn't give you problems, then why don't you use it?

the effects of deep idle are always bigger than those of the io-scheduler (apparently, noop saves a bit more power than deadline).
[Nexus S Android Development] alen1901:
SetCPU.

Sent from SpeedMachine i9023
[Nexus S Android Development] civicdrivr:
Its didle. I had the same, very annoying issue on mine. Didle didnt even make a big difference for me, so I keep it disabled.
[Nexus S Android Development] glennkaonang:
If you rarely uses your phone to listen to music while the screen is off, deep idle won't affect much as far as I know.

Deep idle is mostly effective for listening to music with screen off.
[Nexus S Android Development] caliban2:
Then it's didle plus noop not working together. Maybe. Or just noop acting up on my sys. Because if you read my post carefully, didle plus deadline is fine. (For months!)
[Nexus S Android Development] tchaari:
For what period mathkid? I will really miss the updates. Matr1x is the best kernel I tried since v19 until now.
[Nexus S Android Development] SA-07:
Actually, nvm! Update soon!! ;)
[Nexus S Android Development] rickballs:
I tried a lot of kernels and I always come back to matrix. Thanks for the hard work
[Nexus S Android Development] lupoalberto12:
Mathkid95, don't joke with us :mad: .

Bye!

! :) !
[Nexus S Android Development] micha3lvd:
Late April 1st joke? xD
[Nexus S Android Development] apatal:
DaxMax let slip that next version will be 19.8. :)

Sent from my Nexus S
[Nexus S Android Development] :
Haha that would be hilarious :)
[Nexus S Android Development] SA-07:
He was joking lol
[Nexus S Android Development] SA-07:
Kernel update! We have finally reached v20 :)
[Nexus S Android Development] s1l3nt:
thank you :) couldn't use the thanks button ran out of thanks. Who created that rule anyway
[Nexus S Android Development] caliban2:
Sweet, always wanted to know if this fuzz about 50hz was justified.

Saw you changed some settings for smartassv2 - one question: how should it ever reach 700 & 600 MHz when those steps are not there at all?! :p
[Nexus S Android Development] SA-07:
Oops... lol
[Nexus S Android Development] lupoalberto12:
Thanks.

Bye!

! :) !
[Nexus S Android Development] original21:
Hi, does the refresh rate (50Hz) reduces 3d performnce?

Am using BM CM9 V3

Min200 Max 1300, SmartassV2 (i always use this settings).

Just turned back to 19,5. It feels smoother. I also run a couple of benchmarks and i got better results with 19,5. Have a look at the pics. Maybe its just SmartassV2 changes.
[Nexus S Android Development] legolas93:
Can it be a problem Mathkid? :confused:
[Nexus S Android Development] chalan30:
your benchmarks arent that bad to begin with. and unless you only use your phone for benchmarks, the question should be when you use your phone can you tell the difference in 3d performance from having 50mhz refresh rate.
[Nexus S Android Development] nibla101:
math, please go back to 56Hz I can really feel the change and here are some good sample tweaks for smartassv2 from this thread

For battery:-

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

For performance:-

echo "800000" > /sys/devices/system/cpu/cpufreq/smartass/awake_ideal_freq;
echo "200000" > /sys/devices/system/cpu/cpufreq/smartass/sleep_ideal_freq;
echo "800000" > /sys/devices/system/cpu/cpufreq/smartass/sleep_wakeup_freq
echo "75" > /sys/devices/system/cpu/cpufreq/smartass/max_cpu_load;
echo "45" > /sys/devices/system/cpu/cpufreq/smartass/min_cpu_load;
echo "0" > /sys/devices/system/cpu/cpufreq/smartass/ramp_up_step;
echo "0" > /sys/devices/system/cpu/cpufreq/smartass/ramp_down_step;
echo "24000" > /sys/devices/system/cpu/cpufreq/smartass/up_rate_us
echo "99000" > /sys/devices/system/cpu/cpufreq/smartass/down_rate_us
[Nexus S Android Development] SA-07:
I'm not going to atm... I will see how this goes and see for the next release... feel free to use an older version if you want
[Nexus S Android Development] renna1992:
i actually don't have a problem with the new setting. i'm really curious about battery life cause with 19.5 it was just outstanding.

thanks for the update btw. :)
[Nexus S Android Development] original21:
Thanks for the reply. As i said 19,5 feels smoother (scrolling between home screens, and from apps to widgets). So i used the benchmarks and the main difference i saw was in the 3d performance. With 19,5 it reach 58fps where us with 20 it was just below 50. I did not try any games. Then i saw the comment of caliban2 and i thought it could me something to do with smartassV2.

I have been using matr1x since my first custom ROM a few months ago. I really love his work.
[Nexus S Android Development] caliban2:
@nibla101:

Don't see any bad effects from 50hz yet, what do you mean?

About those batt-saving settings for smartassv2:

You do know that our CPU doesn't have a 500mhz step, hm? Those settings are for sgs2. But in general they work very well on nexus s, currently I'm running them with 400/100/400. Also I had to lower min CPU-load to 50%, phone was a bit laggy sometimes with 70. Rest is as in that post you quoted.
[Nexus S Android Development] original21:
+1 on battery life. For me 19,5 is outstanding. Excellent in all aspects.:)
[Nexus S Android Development] nibla101:
I used the trinity kernel before this one and when they made a kernel with 50hz and 56hz I made the 50hz kernel a daily driver and after awhile I tried out the 56 and it felt like a new phone. Maybe its different from people to people but I can really feel those 6hz just like in I do in computer games and fps. Yeah I know they are for sgs2 I meant he could use them as a base for hes own settings like I have.
[Nexus S Android Development] rickbosch:
yeah, V20 of matr1x is kind of like trinity's TEUV, super lean on battery usage. Or in theory at least, V19.5 with Codename Android RC2 is the smoothest/best battery life combo my Nexus has had.
[Nexus S Android Development] caliban2:
Hm, in that case I guess I'll flash back 19.5 tomorrow and see if it really feels faster. But first get accustomed to v20. So far everything feels the same (=smooth, fast & stable).

As I said, the settings are great, just a few changes needed. :) maybe I'll try with ideal sleep @ 200 next...
[Nexus S Android Development] civicdrivr:
I work in a very loud data center, music is always playing on my phone.