yashsingh1/xdaforums huggingface dataset:
[Nexus S Android Development] caliban2:
Okay, flightmode and let it rest in the locker.

Something else on this test version:

Min-cpu is always set to 200, despite having 100 in the script. In cpuspy it shows 100-step has been used, but 0:00:00. (Meaning it's not an unused step like 1200)

I have to manually change it with nstools or cm9-settings once after a reboot to get it used.

This didn't happen on the prior test-version.

Just in case, this is my current setup. It has changed a bit from the one I pm'ed you a few days ago.

#!/system/bin/sh

echo 0 > /sys/class/misc/backlightdimmer/enabled
echo 5000 > /sys/class/misc/backlightdimmer/delay
echo 1 > /sys/class/misc/backlightnotification/enabled
echo 96 > /sys/class/misc/batterylifeextender/charging_limit
echo 1 > /sys/class/misc/deepidle/enabled
echo smartassV2 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
echo 400000 > /sys/devices/system/cpu/cpufreq/smartass/awake_ideal_freq
echo 100000 > /sys/devices/system/cpu/cpufreq/smartass/sleep_ideal_freq
echo 400000 > /sys/devices/system/cpu/cpufreq/smartass/sleep_wakeup_freq
echo 50 > /sys/devices/system/cpu/cpufreq/smartass/min_cpu_load
echo 85 > /sys/devices/system/cpu/cpufreq/smartass/max_cpu_load
echo 200000 > /sys/devices/system/cpu/cpufreq/smartass/ramp_down_step
echo 200000 > /sys/devices/system/cpu/cpufreq/smartass/ramp_up_step
echo 49000 > /sys/devices/system/cpu/cpufreq/smartass/down_rate_us
echo 48000 > /sys/devices/system/cpu/cpufreq/smartass/up_rate_us
echo cfq > /sys/block/mtdblock4/queue/scheduler
echo cfq > /sys/block/mmcblk0/queue/scheduler
echo 100 > /sys/class/misc/liveoc/oc_value
echo 100000 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq
echo 1000000 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq
[Nexus S Android Development] xjerlzx:
alright i have decided to test it myself. any problems i'll report to u.

gonna flash v 1.4 for a test =)
[Nexus S Android Development] caliban2:
thalamus' idle2 sure looks interesting.

maybe all the hassle with performance-gov @ deepidle isn't needed at all...? ^^
[Nexus S Android Development] Randomwalker:
Just had a reboot but no SoD, still interested in a kmsg?

EDIT: latest test kernel@ 4.0.4
[Nexus S Android Development] :
Yes please
[Nexus S Android Development] caliban2:
Yes, but it's not like you fixed some "drain". :)

Gyroscopes, auto light sensors etc drain some battery, that's common knowledge since phones have those things.
[Nexus S Android Development] :
I think tonight I'm going to try and meddle with cpufreq code some more. Now I'm a bit more familiar with it I'm pretty sure I can modify it without introducing errors again. What I want to do is raise the FSB by 10% at 1GHz. This is because I noticed while playing asphalt 7 that my CPU is spending 1 part at 1 GHz for every 2 parts at 1.1GHz, and it seems wasteful to run the code that checks for bus frequency changes that often. This will improve performance in two ways, by extra efficiency, and extra fsb/gpu speed. If that wasn't tricky enough, I also want to make the fsb oc selective, so it only operates if the user policy has 1.1GHz currently selected as the max. Otherwise, I want normal fsb speeds. I.e. if the user selects the max cpu freq as 1GHz or 1.2GHz, then no fsb oc will be applied.
[Nexus S Android Development] caliban2:
I wonder, is asphalt 7 crappy coded or is nfs most wanted perfectly coded... ^^ Or is it your ROM/gov-settings? I don't feel the need to overclock at all, and smartass is toned down compared to your settings. :confused:
[Nexus S Android Development] mpjoe2000:
i would like know where did i had said i have fixed the draining? :cyclops: it is just a workaround that it fits my needs and will bring a little bit of goodness. Obviously sensors will drain some battery, it is obviously logical.
[Nexus S Android Development] alen1901:
Bedalus sorry for off topic, but did you or anyone here ever tryed rasbeanjelly ROM from rascarlo and Slim bean? Im really teared apart from both roms, dunno which one to choose. How are they in terms of speed and battery, the same or?

Sent from SpeedMachine i9023
[Nexus S Android Development] KrisMurdrum:
Flo's 100.1% Stock Google

Marmite v6.3

i9020t

Default kernel settings

Had a reboot last night when I was trying to hook my phone to my laptop for music transfer.

http://ubuntuone.com/1TbuVnaIz0p8QaXeqEvQO9

Carved into the void with my Magic Rune Stone
[Nexus S Android Development] :
Somewhere in between v6 and v6.5 inclusive I introduced some bugs in the cpufreq code the controls the various clocks and locked loops involved in shifting frequency. It's only fixed as of v6.6 so I would blame any reboots on that. I'll probably pull those links actually.
[Nexus S Android Development] :
I can't make a comparison between the two, I don't have the other one!
[Nexus S Android Development] imranaryan:
phone doesnt start when i flash 6.6 Stock

but run fines on 6.5 stock am on stock 4.1.2 rom
[Nexus S Android Development] aladin6:
You surely choose a bad marmite version. On what ROM are you and what kernel did you download ?
[Nexus S Android Development] :
Any other stock users facing this issue?
[Nexus S Android Development] :
Result of meddling with cpufreq again:

[b]old version[/b] (best of three)
performance	1ghz 27.7
1.1ghz 30.0
1.2ghz 27.1
smartassv2	1.1ghz 26.9

[b]new version[/b]
performance	1ghz 27.6
1.1ghz 29.9
1.2ghz 27.3
smartassv2	1.1ghz 27.5

So, it looks like it was worth it. The biggest shift with performance governor was 0.2fps, negligible, probably due to ordinary operating noise. The shift when using smartassV2 was 0.6fps, much more significant, especially considering I lowered the ideal awake frequency to 800MHz.
[Nexus S Android Development] alen1901:
So i see only smartass is improved? So what than means in more humanic understandable terms? :D
[Nexus S Android Development] :
Well, I only use the performance governor for benchmarks. I use the smartassV2 governor if I'm playing games, because I still want the CPU to be able to scale down to save battery. But I still want to have the highest FPS possible. I've managed to improve the FPS when using 1.1GHz despite lowering the smartassV2 ideal awake frequency, so it's a result I'm pretty pleased with. For people who use smartassV2 and 1.1GHz OC for gaming (like me) it'll mean they get a little more FPS (smoother animation) and when possible, some battery saving. They'll only be tiny differences, but if you pile on enough tiny differences, hopefully it becomes noticeable.

EDIT: The FPS will still be higher with ondemand too. It's not the smartass governor changes that have improved the FPS. Rather, the FPS has improved despite the governor changes.
[Nexus S Android Development] alen1901:
Now i get it. ;) btw i went up to 100hours of uptime with 6.2, than i must reboot because of some ****ty app, caused notification bar laggs. Now ill flash some 4.2 goodies and start all over again. :D
[Nexus S Android Development] :
I'm going to upload the one I'm testing. It's a cm based version.

Here: http://db.tt/53Bhkbes

First come, first served.
[Nexus S Android Development] deetailed:
Stock kernel on kwbr's stock ROM here. No such problem.

I did get a reboot last night (about 9 hours ago), but too sleepy to flash debug kernel and get last_kmsg. After I woke up I forgot what I was doing when the reboot happened.:silly:
[Nexus S Android Development] deani77:
Just download and flash on top Nightlies 3/11. So far no problem. Will report back later...
[Nexus S Android Development] caliban2:
Now I'm curious, overclocking too now. Will be interesting how 1096 will change my batt-life with smartassv2 (though my ideal freq is 400). :)
[Nexus S Android Development] pan1980:
flash 6.6 s soon as it was published.

first day was without OC and it was perfectly stable.

second day i tried 1.2 Mhz and had some reboots, tried some voltage changes and i found that int voltage should be 1100 instead of 1150, cpu voltage didn't helped as soon as it was above 1.325

the surprise came when i tried 1.1Mhz, for stability it also wanted 1100 for int voltage!

3 days switching form 1.1 to 1.2Ghz with bot int at 1100 and no reboots, completely stable.
[Nexus S Android Development] :
Some people may need to lower voltages to find a stable point. Others may need to raise.
[Nexus S Android Development] :
It'll be worse than 1GHz! How much worse, maybe 10%
[Nexus S Android Development] caliban2:
Should be more than 10%. But what really surprised me was 1000 being almost completely replaced by 1096...

Anyhoo, got a (oc-)freeze after 15 minutes. ^^ but don't wanna play with voltages now, there's no point for me. Phone is smooth @1000 (same as 1096), even when playing games and that extra-drain settles it. :)
[Nexus S Android Development] vis80k:
hm. a strange observation. a first for me, at least.

on rasbeanjelly 1101 release with marmite 6.6. turned on bld, bln, no blinking, and set freq to 1.2...just for the heck of it but I normally don't.

performance was real good. but after a few hours on-time while surfing web, the screen went fuzzy horizontally and system would not respond. so I had to pull battery. when I mean screen going fuzzy, imagine the when you're playing demanding computer game on a defect video card and the game screen freezes. scared the hell out of me thinking the graphic chip went bad on me....

but after pulling the battery and turning it back on, all seems fine. my guess is maybe the OC has something to do with it? as no one else reporting this? I will try with 1ghz and will return if I have the same problem. ;)
[Nexus S Android Development] granets:
I am using 400 as min frequency. will there be problems with 6.7?
[Nexus S Android Development] caliban2:
Only unnecessary batt-drain. ;)
[Nexus S Android Development] granets:
I disagree. I am getting almost 48h with the way I'm using my phone.
[Nexus S Android Development] Hawkw1nd:
You may be able to get a lot more. If I keep my Nexus S on 2G, turn off sync, and talk no more than 30 minutes a day, I can get at least 100 hours, but that doesn't mean anything to someone who browses, talks, and games heavily. Whatever gains you may get are relative only to your situation ...
[Nexus S Android Development] fear_factory84:
I'm on rasbeanjelly 10/28 with marmite v6.6, I have many "alarms" set by rild, and in the night it drained 15% battery (wifi on and connected).

Do I have to change rild with the cm one like knzo did on its strawberry build? Perhaps I don't know which are the files needed to be changed.
[Nexus S Android Development] :
It's completely replaced 1ghz because it reduces a lot of code execution.
[Nexus S Android Development] caliban2:
No, I mean I expected more scaling. Don't ask why, i know it makes no sense. But for me it's really just batt-waisting, those 1-2 fps I only see in benchmarks, but will never see them using the phone. :)
[Nexus S Android Development] atxbang56:
Hi guys !

can you tell me wich Rom do you use with Marmite Kernel? I'm running MIUI for the moment but it becomes a free-to-use Rom and will get some extra features we'll have to pay...(like themes for now).

Si I'm loocking for a good Rom for daily use (many updates is not a problem for me, I'm a flashmaniac) and good for Gamibg too.

I've read that Bedalus don't want to say the Ro he uses but if anybody know it...

Thanks in advance and many thanks to Bedalus for his work on our old-becoming phone.

Envoyé depuis mon Nexus S avec Tapatalk
[Nexus S Android Development] polobunny:
I got that twice in the last 2 days. One time it rebooted on itself but the other I had to pull the battery. I don't oc, so it's not that... :(
[Nexus S Android Development] Articudos:
I just noticed 6.7 uploaded.;)

Why don't u update thread title..?:)

Isn't it stable version?(green colour in matrix)
[Nexus S Android Development] micha3lvd:
because in the matrix it still says comming soon :)
[Nexus S Android Development] caliban2:
Looking at that changelog, I hope he takes a break more often... :D
[Nexus S Android Development] :
Speaking of FPS, I read a study that said a 10% difference is roughly about where things become noticeable. Less than that it gets hard to tell. So it's not like I'm trying to say it's the difference between night and day, because the difference probably isn't quite 10%

About the battery, running at 1.1GHz isn't going to increase battery consumption by 10%, it's going to be less. Only the FSB/GPU and CPU have been bumped by 10%, and that's only two subsystems in the device. If every system was asking for 10% more in the same unit of time, then you'd see a 10% faster drain. The main drain is the screen, and that isn't going to be asking for more power.
[Nexus S Android Development] :
Hmm, I thought that black screen issue was caused by a DMA commit in mainline v3.0.35, maybe I was wrong. See if you can work out if it's reproducible.
[Nexus S Android Development] :
v6.7 is here: http://goo.gl/HvUrp

See the version matrix for the changelog. I was just waiting for the v3.0.51 official to be released, which I knew was imminent.
[Nexus S Android Development] polobunny:
I can't though. One time I was looking for a song in Apollo, came back to home screen and bam, little colored misplaced pixels appeared on the screen then it rebooted a few seconds after. Didn't have time to pull a log because I was out drinking.

Yesterday I was going through funny pictures on 9gag app, scrolled then it locked with similar pixels appearing. Then the screen went black but stayed lit except for the status bar, then it became black completely.

Tried turning the screen off/on, wouldn't do anything, softkeys lit up when I pressed them though. Pulled battery cause I was in the middle of texting with someone, so no time to plug to PC.

Sucks because otherwise I like the kernel, but I can't ever get a REALLY stable phone with any version. :\
[Nexus S Android Development] caliban2:
I meant 1.1 should need more than 10% over 1.0, just the two steps.

But damn you, now I'm overclocking again (1.1). Good thing is I know from the past my phone can take 1.1 and 1.2. Bad thing is if it freezes, I won't know which step needs more voltage (if I get the changelog right). First world problems... :screwy:
[Nexus S Android Development] :
I'm happy to roll back to v3.0.34 mainline if you'd like to test?
[Nexus S Android Development] polobunny:
I'm up for testing for sure. Same for BLN dying bug if you ever get to that (no stress though, because at least that doesn't kill my phone :p)
[Nexus S Android Development] Pete7ate:
Thanks so much for all information.
[Nexus S Android Development] caliban2:
Okay, this didn't take long, just had a freeze/reboot while taking a photosphere (it benefits big-time from overclocking, btw).

Today's nightly, marmite 6.7@1096.

So now i'm back to stock-speed, to make sure it's not something else. last_kmsg attached anyway.

(I really hate this part of overclocking... ^^)
[Nexus S Android Development] polobunny:
Yep that's the boring back and forth part where you try to figure out the stable voltages, if any. Tedious, but worth it in the end if you can find something that suits you.
[Nexus S Android Development] N_E_X_U_S:
I moved from the CNA rom to the PARANANDROID and I wish continue to use this great kernel.

Which version (column of the matrix) I shall use?

Is it support android 4.1.2?
[Nexus S Android Development] caliban2:
At least I'm almost certain it's the 1096-step, as the phone was very, very busy the moment it happened. So once I'm convinced it's stable otherwise, I have a point to attack. :)
[Nexus S Android Development] rip_noob:
PA is cm based so you have to download the cm version.
[Nexus S Android Development] agnostic900rr:
Took also two photospheres, one with 4.1.2 and one with 4.2 Camera also with marmite 6.7@1096.

No Problem here
[Nexus S Android Development] caliban2:
Good for you. Proves that each phone is different.

I just wanted to give bedalus a kmsg to look at. :p

PS:

Photosphere with 4.1.2-camera? W00t?! :screwy:
[Nexus S Android Development] nhoc_maruko9x:
Maybe panorama with 4.1.2 and photosphere with 4.2 :laugh:
[Nexus S Android Development] agnostic900rr:
of course ;)
[Nexus S Android Development] paino85:
is it compatible with slim bean??

i tried "marmite 6.6-all other rom", but my phone go in bootloop
[Nexus S Android Development] kwibis:
Download cm version

Sent from my Nexus S
[Nexus S Android Development] aladin6:
Feedback: Im on cm10, installed 6.7 version and... i don't have to say every time that this kernel is f****ing awesome !
[Nexus S Android Development] alen1901:
So if i choose 1.1ghz, GPU is overclocked on all cpu clocks?

Sent from SpeedMachine i9023
[Nexus S Android Development] Nexus HAL:
color n sound question

I've just switched to marmite from stock CM kernel of PA. Boy its smoother!!

I need some help with color n sound management.

In advanced setting, CM color controls are now disabled. Is it supposed to be this way? I've installed the CM version of Marmite.

If yes, am I supposed to use Voodoo control for color management?

What will happen to sound processing then? Who will handle it, Voodoo? or CM's DSP manager?

Any clarification will be much appreciated! :)
[Nexus S Android Development] mdean1981:
Voodoo, Voodoo and Voodoo. :)
[Nexus S Android Development] caliban2:
Yeah well, photosphere and panorama are really not the same... ^^
[Nexus S Android Development] polobunny:
I don't know how you guys can take a photosphere unless the lighting is perfect and you're not shaking at all. The smallest error gives you the crappiest distorted view.

Just stitching a perfect panorama is already hard haha. :p
[Nexus S Android Development] caliban2:
Lol, when has shaking ever helped in taking a good picture? :p

The trick is not to shake (hehe) and try to turn the camera "on the same spot". Sure, some stitches are there almost all the time, but most of the time it's way better than streetview. (For some reason outdoor it's better than indoor)

Btw, v6.7 was stable at stock-values. I'm back @1096 and +25 on INT seems to have done the trick... *jinxing myself*
[Nexus S Android Development] CrackerTeg:
Anyone notice how multiple frequencies don't get used on stock smartassv2 settings? CPU spy shows only deep sleep, 100, 800, and 1200 being used.
[Nexus S Android Development] Hawkw1nd:
Yes
[Nexus S Android Development] vis80k:
Wasn't black screen in my case. Screen just stretched horizontally and nothing worked. Screen also had the old tv fuzzy like quality.

Anyway, experienced it again with 1.2 oc...coz I forfot to change it back after reboot. Now on 1ghz and will report back.

One update would be it is not app dependent as it occured on different apps.
[Nexus S Android Development] :
Yes, except for 100mhz step.
[Nexus S Android Development] :
Oh crap, I just realised I need to hike up the voltages for INT but only when FSB oc is engaged.
[Nexus S Android Development] caliban2:
You don't say... 3 minutes after I wrote the above it froze. I kept playing with the values, but at some point I just wanted to play NfS (how often can you see the finish line aleeady and the damn thing reboots?!) and returned stock.

Got some interesting kmsgs though, never seen them THIS ****ed up. :D
[Nexus S Android Development] :
http://d-h.st/t2f (experimental CM/Stawberry/Slim Bean only version)

-When 1.1GHz is selected, 50mV is added to INT for 400/800MHz. (You can set your own 1.1GHz)

-v3.0.35 is reverted completely (may solve the weird black screen bug)

-200MHz is disabled. I think this may help improve stability. There's a reason for this that I can't really explain until I've had some sleep!

@polobunny, can you please test without OC to see if you get any black screens?
[Nexus S Android Development] polobunny:
Great timing, I'm back from the gym. I'll flash right ahead and update you if it crashes. I never OC anyway. :)

Edit: Caliban, I believe it's because of the lighting. Indoor light being very low compared to sun light, some details gets lost and the stitching algorithm has a hard time.
[Nexus S Android Development] Zahih:
Hi Bedalus...

I'm on i9023 run AOKP JB M1, which one your kernel that I should flash?

Thanks.
[Nexus S Android Development] mdean1981:
CM version
[Nexus S Android Development] Zahih:
I cannot boot with CM version.
[Nexus S Android Development] anshumandash:
It should be all other ROM version for aosp & aokp ROMs.

Sent from my Nexus S
[Nexus S Android Development] doc_v15:
Is MTP features still available in 6.7 versions?
[Nexus S Android Development] mdean1981:
Delete
[Nexus S Android Development] Hawkw1nd:
Yep
[Nexus S Android Development] Zahih:
Yup... Finally I successfully flash with all other Rom version.
[Nexus S Android Development] capoooro:
Hi bedalus. 6.7

Strawberry

No OC

Stable
[Nexus S Android Development] benoit2600:
Hi, is BLN work for you with the 6.7 version ?

It doesn't work for me, I use the CM version with Slim 2.9
[Nexus S Android Development] :
It should work. Maybe report this in the slim thread too
[Nexus S Android Development] anshumandash:
I have been using 6.6 on BB6 since the day it was released with ondemand and 1096. It has been very stable even while playing cpu intensive games. Never had any reboots. My 9020T can generally take OC even with lowered voltages. But in the last 24 hour, I had two soft reboots (only boot animation showing up & home screen loads up). Once it happened while the phone was sitting idle next to me on the desk and another time after I dismissed an alarm.

I got last_kmsg, but it does not look complete. I believe this may not be oc related.

Is there a way to know what went wrong?
[Nexus S Android Development] caliban2:
Hm, only tested this one briefly, it boots and survived one race in most wanted @1096. But from the way I understand it and what cpuspy told me, oc'ing for daily use is not really desirable with this one. Anyhoo, I'll give it a thorough testing tonight. Really looking forward to the explanation why and when 200 should cause instabilities. :)
[Nexus S Android Development] alen1901:
On 6.7 i was using chrome, browsing, than my screen went black, only statusbar was there. I could interact with it but nothing else, battery pull needed. No logs. Went back to 6.2