yashsingh1/xdaforums huggingface dataset:
[Nexus S Android Development] moriz1:
Apparently not for playing music with the screen off, since I tried both frequencies for screen off max step, and both had the same crash. For general use, they both appear to be fine.
[Nexus S Android Development] SA-07:
Deep idle on?
[Nexus S Android Development] moriz1:
It's on, but it shouldn't be an issue, since when playing music, it shouldn't even be in deep idle.
[Nexus S Android Development] SA-07:
Well sometimes it can cause it... but just raise voltages and let it go
[Nexus S Android Development] moriz1:
I'll report if it happens again. For now, 800mhz is at stock voltage.
[Nexus S Android Development] tycruickshank:
I was noticing this problem with my phone as well and I read somewhere that rebooting the phone with the USB plugged in and connected to the computer could change the battery readout. So what I did was let my phone run down to about 5 - 10% and then plug it into the computer and reboot the phone. Right after the reboot my phone showed 30% battery left. So I let it run down to 5 - 10 again and it did the same thing and the battery showed 15% or somewhere around there left. Anyways I kept doing this until the battery percentage read the same after the reboot as before.

Maybe somebody could correct me I'd this doesn't actually fix anything. The reason I think its helped is because the battery today has seemed to last much longer than before I this reboot thing.
[Nexus S Android Development] moriz1:
Very true. The battery meter doesn't seem to measure absolute charge, but difference in charge compared to a certain point. If that initial value is wrong, the whole thing gets shifted by the difference.

At least, this seems to be true at the start. It does seem to correct itself as the battery runs down.
[Nexus S Android Development] nodstuff:
Post your settings. ALL of them.

Lulz settings, oc, live oc, didle and post all your voltages, int and arm.

My phone is set to min step 800 screen off and I undervolted even further than mk has.

I have NO PROBLEMS!

You need to post everything so we can go through this and see what is going on.

Also to ppl having green line probs on camera its a rom problem. Try a different rom.
[Nexus S Android Development] moriz1:
Microprocessors are not made equal. Just because yours can, doesn't necessarily mean that mine can also.

As for settings:

inc load: 55%

Up step: 1

Down step: 2

Screen off max: 800mhz

Up sample time: 15000

Down sample time: 35000

Deep idle on, no oc, no live oc, default voltages.
[Nexus S Android Development] nodstuff:
Yes I know that, I was merely trying to point out that screen off 800 wasn't the problem, do you have problems when the screen is on at 800?? No, didn't think so. It uses the same voltages with the screen off as it does with the screen on so if it doesn't lock with screen on 800 then 800 isn't the problem.

OK that's fine but what I really need is the voltages, arm and int.

Then after you do that when I respond we are going to play a game I like to call find the annoying prick that makes my phone sleep.
[Nexus S Android Development] moriz1:
Actually,I dint know if it crashes with the screen on or not, just that it never did. With the screen on, my usage pattern typically have the phone be very bursty in CPU usage. As such, any lingering instability never surfaces, because it doesn't stay at high clocks for very long.

With the screen off and playing music, the phone probably stay at one voltage for extended periods of time, and instability can have more chance to manifest.
[Nexus S Android Development] nodstuff:
thats utter rubbish. if it hits 800, even for a second, and the voltage isnt right, it will freeze and reboot.

bursty or not you are still using pump up step by 1. it is still going to hit 800.

you gonna give me voltages or do you not want help sorting your problem?
[Nexus S Android Development] moriz1:
As I mentioned already: default voltages for this kernel. Seems to be stock -25mV for everything.

And it's not rubbish at all. Modern processors can run for extended periods of time with insufficient voltage, as long as it is not too low and not stressed for too long or too hard. I have plenty of experience overclocking desktop CPUs; phones work the same way.
[Nexus S Android Development] nodstuff:
ok, now we are getting somewhere.

first i want you to set governor to performance.

this will set min freq to whatever you set as max freq, this is how we will find the troublesome freq.

start at 200mhz, then 400 and so on, open browser or some other app that will put a bit of a workload on the cpu and eliminate each freq that way. screen on and screen off, lets be thorough.

see how that goes.

yes i know that it will run for so long without load, thats obvious, but in general use you are going to have load on the cpu of some sort.

---------- Post added at 01:17 AM ---------- Previous post was at 01:03 AM ----------

these are my voltages:

ARM:

100mhz 900mv

200mhz 900mv

400mhz 975mv

800mhz 1125mv

1000mhz 1250mv

1200mhz 1300mv

1300mhz 1400mv

1460mhz 1450mv

INT:

100mhz 925mv

200mhz 975mv

400mhz 1025mv

800mhz 1050mv

1000mhz 1100mv

1200mhz 1100mv

1300mhz 1150mv

1460mhz 1200mv

see that i uv'd arm volts but i bumped up int volts a little.
[Nexus S Android Development] moriz1:
What is int voltage anyway?

I've worked up to 800mhz now. No crash so far, though I suspect subsonic player force closed at 400.

Edit: nvm, the song ended. No force close.
[Nexus S Android Development] nodstuff:
int voltages are the internal voltages, as opposed to arm being the cpu voltages.

i find the cpu responds better to uving if some int volts are bumped up a tad.

for example didle on an old release made the phone lock up unless 100 and 200 mhz arm volts were bumped up to 950, that sorted the problem.

when i changed my 100 and 200 arm volts back to 900 i bumped up the corresponding int volts by 25 and it solved the lock up problem.

keep putting load on each freq til you find the prob, if you had a fc at 400 then try that one again. maybe the app doesn't like that freq and is causing probs when the screen is off. do you have any problems with stock music app?
[Nexus S Android Development] moriz1:
So just ran through all the frequencies. No fc, no reboots. Everything seems to work fine.

Looks like I have to do a longer test.
[Nexus S Android Development] nodstuff:
maybe its the music app you are using.

you should try out the volts i put up, just raise int before you drop arm.

it was even stable for me using live oc of 110.
[Nexus S Android Development] sushiboy:
Wheatley Gov. is awesome. I usually drop 20-30% at night. After using Wheatley, I drop only 10% during 9 hrs at night.
[Nexus S Android Development] mobile_pc:
@mathkid95

Could you add "65 fps refresh rate"?
[Nexus S Android Development] nexusphone:
+1 :) for the smoother UI or UX
[Nexus S Android Development] PMShodan:
I've been using *Matr1x* since 14.0, but tried the SG-NS-ICS kernel (24012012) yesterday, coming from *Matr1x* v15.

BUT: When I tried to reflash *Matr1x* V15 in CWM after deleting Dalvik Cache, the Kernel froze instantly after reboot, reflashed and tried multiple times, even resetting all NSTools Seetings. Only thing I can do is reflash SG-NS-ICS to get a booting phone again.

What do I have to do anything else für *Matr1x* to work again?
[Nexus S Android Development] :
If your screen is off and deep idle is on, deep idle will be on. This is exactly what it was designed for. Read Ezekeel's thread on it.

For kernel benchmarks and more, see here: http://goo.gl/mpeHI
[Nexus S Android Development] eezak:
Using matr1x 15.0 with wheatley 100/1000 frequencies, the music playing through poweramp skips a lot.

Anyway to fix it?
[Nexus S Android Development] moriz1:
Only if the phone is idle, which it isn't when it is playing music.

If this is actually by design, then Ezekeel made a bad design choice.
[Nexus S Android Development] aLNG:
quote from ezekeel.its for galaxy nexus thread.but the idle or multitasking concept still the same.
[Nexus S Android Development] suksit:
May be you're confusing between deep idle and deep sleep. If the screen is off and the phone isn't doing anything in background, it will go to deep sleep. But if the screen is off and there is an activity going on (like playing music) then the phone will go to deep idle.
[Nexus S Android Development] pilspeda:
I have gone back to v14.5, because v15 gave me a weird amount of battery drain while running the exact same settings. I also had a Radio drop with v15 which I never had with v14.5
[Nexus S Android Development] felpaboy:
flashed Matr1x 15 but get boot loop!

Any ideas? Now, i came back to 14 by restoring the backup.
[Nexus S Android Development] The1Shark:
Well, for me, playing music when the screen is turned off , is the only situation where I can see that Deep idle becomes active.. ( top=off numbers are up ) so I think your conclusion is wrong ..

---------- Post added at 11:37 AM ---------- Previous post was at 11:35 AM ----------

Charge all the way up, clear / wipe battery status from CW recovery.
[Nexus S Android Development] KBanause:
Clearing battery stats will not affect battery life!
[Nexus S Android Development] felpaboy:
DOH! i forgot to wipe cache and dalvik last time! :D

It seems to work now!
[Nexus S Android Development] sperelli:
i had the same thing as http://xdaforums.com/showpost.php?p=21860867&postcount=2010

solved with wipe battery stats...
[Nexus S Android Development] KBanause:
I already asked but I was ignored:

Why should wiping the dalvik-cache help in preventing a bootloop after flashing a new kernel?

It has NOTHING to do with the kernel...
[Nexus S Android Development] mobile_pc:
delete /system/etc/init.d/98_startup_script
[Nexus S Android Development] PMShodan:
Thanks, that did the trick ;-)
[Nexus S Android Development] att1cus:
Maybe. I flashed the SG kernel just to double check and I can confirm what drew2d1 found--green lines gone, camera works fine. Green lines pop up again when I reload Matr1x. I'm still running Matr1x, though. Sometimes the camera works and it's not too big of a deal at the moment. Eff flashing another rom, though. CM9 4eva!!!
[Nexus S Android Development] SA-07:
Sorry no green lines here
[Nexus S Android Development] eezak:
I am having huge music skips while using wheatley governor with 100/1000 no liveoc, any help?
[Nexus S Android Development] att1cus:
actually never mind...
[Nexus S Android Development] nexusphone:
Yup, v15 perfect! Thanks for the greatest work. :)

btw, "65 fps refresh rate" plz on the next version ;)
[Nexus S Android Development] The1Shark:
I didn't say it will.

The "wipe" from the recovery, delete the /data/system/batterystats.bin file which stores the battery status.

I'm pretty sure he does not have a problem with the battery since change in battery level was observed only after a reboot.

His data file must be incorrect, so deleting it will correct the problem.

the1shark
[Nexus S Android Development] Flukzr:
Since a google engineer says that wiping battery stats, has no effect on the battery capacity or the battery bar, it tend to believe her.

I'm just wondering what happens when using NStools to set the charging limit to 96% (default). I know that 100% is purely cosmetic, but if 96%=100% then is 96%=92%?

Am I getting less than a full charge by using 96%, or does the pseudo-charging to 100% only kick in after the 96% mark?
[Nexus S Android Development] DaX05:
Its purely cosmetic so I tend to believe it kicks in once it hits 96% to show 100%.

Beamed from my Nexus S
[Nexus S Android Development] caleb1783:
ive been collectin data regarding different settings and governors on battery life...

http://caleb1783.tistory.com/303

check it out....

fyi. matr1x kernel got best bat while preservin performance!

Sent via Divinus Nexus S...
[Nexus S Android Development] katse:
cool. thanks!
[Nexus S Android Development] aLNG:
i think website is down?
[Nexus S Android Development] moriz1:
the nexus s doesn't have c4 state, so I'm not sure if any of this is relevant. If the phone does go into a deep idle state while playing music with the screen off and is crashing, then it seems that it is occasionally not coming out of it fast enough.

Had another crash last night. I set it to loop an album while I slept.

Subsonic is a music streamer, and I noticed that if I'm actively streaming, it never crash. When wifi is active, deep idle is in top = on. Maybe it is caused by top = off.

I'll try again later by leaving Bluetooth on, which disables top = off, and see if it crash again.
[Nexus S Android Development] aLNG:
you are right that nexus s doesnt have c4 state(is wheatley gov then work properly in nexus s?). but the concept is relevant for any multitasking device.

top off == didle for screen off, top on == didle for screen on

correct me if im wrong
[Nexus S Android Development] xontax:
Best Performance/Battery life with Deadline/smartassv2, thanks!

Sent from my Nexus S
[Nexus S Android Development] moriz1:
The point is, the phone doesn't seem to come out of its idle state fast enough.

As for deep idle top on/off, out seems to be dependent on wifi/Bluetooth/data activity. With Bluetooth on, even with no device connected, the phone never enter top off.
[Nexus S Android Development] The1Shark:
1. What is "best" ?

2. Voltage ? ( kernel default / Stock)

3. Deep Idle on or off ?

4. OC/UC ?

4. Live OC if on , how much ?

5. Screen rotation on or off ?

Please share some more info ..
[Nexus S Android Development] aLNG:
yeap...idk how long it takes to come out from idle state...maybe need to dig out from manual.

but I never had reboot/or any problem when playing music with screen off.
[Nexus S Android Development] dzerveviktory:
TECHNOGRAVY:

Looks like you were right.

First time ive ever hit more than 24 hours!

Thanks! MK seriously impressed with the battery life using matr1x on ultimate ics 3.0!

Thanks!
[Nexus S Android Development] zipredictive:
Can u share ur nstools settings? Thnx

Inviato dal mio Nexus S usando Tapatalk
[Nexus S Android Development] kenshin33:
Deep idle one seams to be causing these reboots.

Played with the phone while listening to music went well. left it alone (listening to music) after some time it froze (Twice). left it really alone it rebooted twice. deactivated deepidle, no problem at all.
[Nexus S Android Development] xontax:
http://xdaforums.com/showthread.php?t=1441905

Hey u, I read this some pages ago.. I never touch voltage because I'm not experienced in this and am afraid of sudden fire taking over :D. Deep Idle is on, unlike franco says, it's a big battery safer. Also I never touched OC/UC. Live OC ist on by default, you can set it to 110% if you like. I never did this though. Screen rotation is on, because I like it this way and will never change it. Like you see, it depends on your personal gout ;)

As you can read above, only netarchy, glados matrix kernel support deepidle properly. Deepidle is essentiel for me, because of the large battery drain which still exists for me. Also speedy-7 is not a solution with his magic battery saver which i never got working.

In comparison, the current glados kernel is worse than stock kernel in every discipline. Netarchy hasn't got good performing scheduler atm so the best choice for me is matrix 15.0.
[Nexus S Android Development] dzerveviktory:
which settings are you looking for? lulzactive?
[Nexus S Android Development] mixtapes08:
I think matrix have some tweaks that may cause that issue. In that case delele all scripts in init.d folder if your on matrix and going in other kernels. Now u say that you have problems going back to matrix. Now delete again scripts in init.d folder that comes in sgkernel or matrix14 kernel. then reboot into recovery wipe cache/dalvic. Flash matrix 15 then reboot.

Sent from my Nexus S
[Nexus S Android Development] mixtapes08:
Latest battery. Slight to heavy use. No reboots no freeze.

Gov:lazy its my fav.

Screen off max frq on

Deep idle on.

Sio

Rom gummy nexus 0.6.6 :)

:)

Tnx mk again. Your kernels are the best for battery life and performance and the best for ns.

Sent from my Nexus S
[Nexus S Android Development] SA-07:
Sweet :)
[Nexus S Android Development] bendirkss:
Drew Garen doesn't recommend this with his Orca ROM on phones with high frequencies..

how do i know what frequency levels im using?
[Nexus S Android Development] clocker66:
Yo mathkid, recently exited from the 10-post hell so now I can thank you :)

v15 is very very fast, snappy and stable with these settings:

-100/1000

-no OC (I thing it brings me only instability and I'm not needing it so far...)

-no UV (my ARM doesn't like being uv'ed)

-deep idle enabled

-lulzactive (pump +1/-1 @ 95%, polling up 10000/ down 20000)

With these settings from cpu spy I can benefit from every cpu freq step (I'm not using my Nexus for tasks like gaming but i'm a 'multithreader', so I swap very frequently from an app to another and I used to play music almost all the time I use the phone for browsing/fb'ing etc, so...), the whole system is very smooth and battery life is quite great (I've got 1d 15h battery life with more than 4h screen time....).

I think I've something to tweak related to the radio (wi-fi is draining like hell and signal strenght not that great) but this is related to something else!

The only thing I've to search for is a crash listening music (screen off) but I think it is related to the cpu min freq (I don't really understand if I have to set it from the "screen off freq" in the lulzactive tweak or in the minimum cpu freq, but I'm more for the 1st...)

keep working on it, great job!
[Nexus S Android Development] darth7:
Deep idle works fine on 15

Enviado desde mi Ice Cream Nexus Sandwich usando Tapatalk
[Nexus S Android Development] moriz1:
Looks like Ezekeel's glaDOS kernel is suffering from the music issue also, and it happens on pretty much every music player. Looks like deep idle is to be blamed then.

My testing with Bluetooth on (thus forcing top = off) is inconclusive. Will try again later tonight.
[Nexus S Android Development] nodstuff:
Bluetooth causes top=on to be used not top=off.

Bluetooth off means top=off is utilised.

That music problem is weird because I have never experienced it.

How many people are having this problem?? Maybe there is a common link other than deep idle.
[Nexus S Android Development] moriz1:
My mistake, I meant top = on.

there are at least a few people reporting the issue. Far as I can tell, there aren't too many commonalities, just deep idle.
[Nexus S Android Development] DaX05:
I use Google Music to stream all my songs & have no issues whatsoever.

Beamed from my Nexus S
[Nexus S Android Development] SA-07:
Check this out!

http://www.youtube.com/watch?v=OkmnzVS7T08&feature=youtube_gdata_player
[Nexus S Android Development] DaX05:
Not a bad video. I prefer CM9 though. :)

Beamed from my Nexus S
[Nexus S Android Development] moriz1:
Apex is what I use also.

So an update on my issue: played with Bluetooth on (thus disabling top = off), and no crash or any bugs in one 1h14m. So tentatively, looks like top = off is to blame. Or rather, the transition between it and regular idle when adding to play buffer is to blame.
[Nexus S Android Development] R-TEAM:
Hi,

have jumped from GlaDOS to matrix to test the deepidle problem and music playing ..

Matrix behavor here the same as GlaDOS - if deepidle on an i play music with the inbuilt music player then it crashes after 2-4min.With deepidlee off, the phone is rock stable.

Maybe i will stay with Matrix, but GlaDOS is nice too :P

I have Ezekeel bugged to implement an 1100Ghz step in his kernel ;)

mathkid95, can we have MaTrix with an 1100Mhz step too ?

The reason is, i use LiveOC with 120%, so i get at nominal 1000Mhz -> 1200Mhz.

But at the next step nominal 1200Mhz i get -> 1440Mhz and this cant handle my phone stable ... but with an nominal step from 1100Mhz i get -> 1320Mhz and this runs fine ;)

(and give 10% more speed [1000->1100 or 1200->1320] :) )

Regards

R-TEAM
[Nexus S Android Development] nodstuff:
Well daxo5 is on cm9, mk and I are using gummynex so maybe there is some bug in that rom because I have never had that issue, neither have mk or daxo5.

Maybe ask the other people who have the problem what rom they use.

It could be the link.

I know when top=off isn't utilised the problem doesn't arise and I accept the correlation but on the other hand I get top=off and no music problems or reboots.

It could be worth a shot. Make a nandroid backup and test a new rom.

---------- Post added at 04:31 AM ---------- Previous post was at 04:30 AM ----------

As a matter of interest what rom are you using???

Nvm I read glados thread. You said that you never flashed the Bluetooth fix so does that mean you have no top=off stats??

Ezeekel said in one post that misbehaving apps sometimes caused reboots so maybe try do a nandroid backup, wipe your phone including formatting system, data and boot. And flashing a new rom and testing.

Needless to say don't wipe your sdcard.
[Nexus S Android Development] R-TEAM:
Hi,

i use UltimateICS 4.0 ROM.

And yes - i dont flash the BT fix - but i dont think this is the reason ....(and so i have no TOP=OFF states - this is right) And as i wrote, by deepidle off, my phone is "Rock Stable" - no reboots.(and this for days and by heavy usage)

I have over 160 Apps installed, but i dont think any make mad things.

Controle my apps carefull and dont like apps that installs waste background tasks or other senseless things.(and i have NO cracked app - all orginal DL from market ;) )

I will ATM stay with deepidlee off , as i have not soooo much time to experiment with diff. ROMs and kernels all days ...

I am not sure which kernel i will use after new relases (GlaDOS or Matrix) as both very good - maybe the kernel with an 1100Mhz step :P

Regards

R-TEAM
[Nexus S Android Development] nodstuff:
Well its just unusual that you get reboots when listening to music and no top=off only top=on and moriz1 gets reboots while listening to music only when top=off is utilised and is stable with top=on.

Its a strange problem and doesn't seem to be very widespread. There must be some other link besides deep idle. Otherwise more people would have this problem.
[Nexus S Android Development] KBanause:
And again my phone froze using v15 (cfs and bfs). But this time it drained all of my battery.

I'm using deadline scheduler with ondemand govenor, cpu frequencies are 200/1000, deep idle is active and all voltages for the frequencies between 100 and 1000 are raised by 25mv with SetCPU.
[Nexus S Android Development] SA-07:
Change governor
[Nexus S Android Development] nexusphone:
IMHO, mathkid would better use "quote" :)
[Nexus S Android Development] caleb1783:
Great work on 15

btw, did you remove conservative governor?

it seems to be missing from the list...
[Nexus S Android Development] isdfoa:
im getting a green flicker every time i turn on the phone, and occasionally when i turn off the phone. any way to fix this, or is it a problem with the rom itself? (sorry new to this stuff)

running gummynex v0.7.0
[Nexus S Android Development] Epic_VS:
update usb host to build 5
[Nexus S Android Development] isdfoa:
can you tell me how to do that?
[Nexus S Android Development] Epic_VS:
Build 4 is included in matr1x 15. I was telling mk to update his kernel to include build 5, but you can install a plain build 5 kernel here
[Nexus S Android Development] isdfoa:
^oh i thought you were replying to my post :)

and adding on to this: it seems to stop happening when brightness is set to 100%
[Nexus S Android Development] KBanause:
First: This was the same configuration I was using with 14.5 (and below) without any problems.

Second: Why should I change the govenor? An explanation would be nice. If the "ondemand" govenor is unstable (which it shouldn't because it's one of the govenors in the stock kernel) then it shouldn't be in your kernel ;)

Third: I have never used anything else then "ondemand" (why changing something that's working good?). So what's a good one and why whould I take that one?