yashsingh1/xdaforums huggingface dataset:
[Nexus S Android Development] ebs512:
Had 2 reboots 1 when playing music and 1 when toggling WiFi using 5.3 back to 5.2 for now
[Nexus S Android Development] caliban2:
The pvr-bug is what you like to call my out-of-the-blue bugs - which were gone for a long time when I was on 20121011 and marmite v5. I think they are a symptom, not the source.
[Nexus S Android Development] polobunny:
Except I still have/had them. :p

The last_kmsg I posted I believe was with v5 and 20121011 and same as the others. Might be fixed though since they changed some stuff on the 17th (that I wouldn't know)
[Nexus S Android Development] caliban2:
Lol, reading this made me try and disable WiFi manually - "poof". :D http://db.tt/pdR2qrzp

That burns v5.3, back to 5.1.

You and your out of the blue bugs... :p
[Nexus S Android Development] ebs512:
Bb6+marmite 5.2 are the most stable on crespo and crespo4g,

My testers report any issues, I report them along with issues I may have on the crespo4g
[Nexus S Android Development] polobunny:
Yeah go figure, now I don't have normal bugs anymore. It's an infection. :laugh:
[Nexus S Android Development] kwibis:
This thread is really difficult to keep up with lol. I see you guys are all busy with bugs, buy I have a different question. How do you guys change kernel settings like custom voltage or OC? I have NStools now but I guess there's something different.

Sent from my Nexus S
[Nexus S Android Development] :
There's a few guides for settings in the OP. They involve some very minor file editing.
[Nexus S Android Development] :
Thanks to everyone who posted about the wifi bug, which was a lot of people! Too many to thank individually, but it makes me happy that so many people are willing to report bugs. I think I know what is wrong with the wifi, and I also think I know what is wrong with Android OS.

If anyone wants to confirm, I think if you have wifi on, you don't get it, and if you have it off, you do. Or something like that.

EDIT: Yep, fixed the wifi->off reboot bug. It was a botched (missing) line in the wifi deadlock patch, but I'm very happy with it now! I'm just going to have a little look at a few other things and then I'll upload the custom voltage version too.

EDIT2: Here's some interesting reading:

source: http://www.dirac.org/linux/system.map/

...so when I disabled kallsyms to reduce the size of the kernel, according to the above paragraph it's possible that some drivers may not appreciate this. Oh dear. Better enable kallsyms again, just in case. :p
[Nexus S Android Development] :
Here is v6: http://goo.gl/HvUrp

-Fixed the wifi-reboot issue

-Added custom voltage only at 1.2GHz

-A couple of compiler warning fixes (thalamus)

-Re-add kallsyms

I've bumped to version 6 to reflect the new feature of custom voltage, but this is still strictly a test version due to compiling with v3.0.47-rc1. When the mainline is officially released, I'll dump this patch and merge the official.

Please continue to report any bugs, and upload last_kmsges, which are very useful. I look at all of them, and if I haven't responded to you personally, it doesn't mean you didn't help! Thanks! :D
[Nexus S Android Development] Articudos:
Just Rebooted in v6.

Last_kmsg: http://db.tt/TBw0ywGi

No OC, cfq/ondemand bln/bld on.

I was swiping launcher, and It suddenly freezed, showed Black lines..etc. It was like "*drying* Cabbages in desert", lol

ROM: Latest rasbeanjelly

And Init.d configuration file which I used in v5.2 didn't worked.

:)
[Nexus S Android Development] siddhesh.raikar:
Hey.. m getting an awesome battery life with Wi fi on.. as opposed to Wi-Fi off..

V6 stable on stock rom.. :)
[Nexus S Android Development] beppegg:
I don't know of somebody already answered: you should disable usb debug for mtp to work!

Inviato dal mio Nexus S con Tapatalk 2
[Nexus S Android Development] :
That's a log from a 3.0.46 kernel, so the crash you had was so severe the kernel couldn't backup the log.
[Nexus S Android Development] granets:
That's why I like you and your kernel so much bedalus. You listen to the people and your stuff just works so well. Keep it up. As soon as I get some money in my debit card, I am donating some money. It won't be much, but I hope it would help you in some small way.

EDIT: Do you have a donations account set up anywhere?
[Nexus S Android Development] Articudos:
Oh....I should've read log more carefully... I checked only "kalimochoaz" things..

+ It's really strange, I use only init.d..

But BLD doesn't work now..(after two hour full sleep with charging)
[Nexus S Android Development] :
I don't take donations, but if you like MTP you can donate to krarvind, who made it available for the nexus s.
[Nexus S Android Development] :
I would wipe cache, dalvic, and fix permissions. I suspect something might have gone awry if you had a severe reboot. If that doesn't fix it, then the best bet might be to restore /data from a nandroid, then reflash ROM and kernel, then restore your init.d files.
[Nexus S Android Development] :
I'm now determined to find the source of this Android OS bug, which I just discovered does in fact disappear when the high res timers are enabled. However, android system goes through the roof. I think there's probably some good reason for it, which I don't fully understand, and I need to investigate the code involved more.

Hands up who thought it was the timers? You each get a gold star! :)
[Nexus S Android Development] aladin6:
:good::good: if you have found out the source of the problem we can say that the problem is solved ;P
[Nexus S Android Development] anshumandash:
So I get a gold star :D Well there is nothing to take credit :p

Sent from my Nexus S
[Nexus S Android Development] Erythnul:
Shut up and take our money, you damn good dev you! :P
[Nexus S Android Development] Articudos:
I full-wiped and reflash rom, and Installed v5.2.

I gave same permission as JokerAce..but It doesn't work. :/

Here is copy of my init.d, but I cannot see what is the problem..

#!/system/bin/sh
echo 1 > /sys/class/misc/backlightdimmer/enabled
echo 3000 > /sys/class/misc/backlightdimmer/delay
echo 1 > /sys/class/misc/backlightnotification/enabled
echo 0 > /sys/class/misc/backlightnotification/in_kernel_blink
echo 60 > /sys/class/misc/backlightnotification/max_blink_count
echo 100 > /sys/class/misc/batterylifeextender/charging_limit
echo ondemand > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
echo 20000 > /sys/devices/system/cpu/cpufreq/ondemand/sampling_rate
echo 95 > /sys/devices/system/cpu/cpufreq/ondemand/up_threshold
echo 1 > /sys/devices/system/cpu/cpufreq/ondemand/sampling_down_factor
echo 0 > /sys/devices/system/cpu/cpufreq/ondemand/powersave_bias
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] BenHeng:
I never managed to get my init.d scrypt to work (copy from the one in the thread, then tried every thing I could...). I ended up naming it 99problems but it doesn't helped either... :p so after every reboot, I go to /sys/class/misc... and change the value manually.

When I'm not flashing something every minutes it's not so annoying .

Envoyé depuis mon Nexus S avec Tapatalk
[Nexus S Android Development] :
Possibly you need to enable 'startup tweaks' somewhere in the ROM system settings
[Nexus S Android Development] Articudos:
Rasbean doesn't have it.;)

I just solved issue- modified boot.img myself;) (added init.d function)
[Nexus S Android Development] CommanderDuplex:
NICE !! love that Kernel !
[Nexus S Android Development] aladin6:
Does someone noticed that the ROM is more fuild with SmartassV2 :confused: ? I think that it's better than ondemand (that it's not dedicated to embedded/small systems i think).
[Nexus S Android Development] FirePoncho86:
Indeed, smartassv2 typically will make your ROM more fluid
[Nexus S Android Development] :
Uh, no... it should be about one minute... What ROM are you on?
[Nexus S Android Development] :
I think it's the time of day. Their site is probably being hammered. I've attached it here.
[Nexus S Android Development] N@th_OC:
For me no problem at all. Everything work perfectly. DI with screen off 400Mhz is working very good.

A great kernel!
[Nexus S Android Development] Randomwalker:
Was way over 1min each time. But now I'm on my 4th try and DI is working for the 2nd time in a row. Maybe something fixed itself... :-)

ROM is stock 4.0.4.

EDIT: Definitely fixed, tried it a few more times.
[Nexus S Android Development] gotjazz:
Just so I get this right: this kernel is being tweaked to be used with on demand 100/1000?
[Nexus S Android Development] :
It's a tweaked version on the regular ondemand governor, and it also has tweaked parameters that you can reset to your own preference in NSTools. The only difference between my parameters and stock is half the usual polling interval. It polls twice as often, meaning it scales up and down more frequently, following system system load with less delay.
[Nexus S Android Development] Blackcrx:
can you please post these parameters and polling intervals?

reason is i have made a config file from 1.2 and when i flash new versions of your kernel i just load the old config. I just want to confirm and make sure the polling intervals are correct on my current 1.3b
[Nexus S Android Development] AirOne70:
This kernel have Bigmem ? When Bigmem was added ?

Envoyé depuis mon Nexus S
[Nexus S Android Development] vis80k:
on slim ics rom3.9. bedalus kernel 1.3b. smartass, deep idle on, BLN and BLD on, everything else default kernel settings.

playing music on device or streaming with screen off, I get 800mhz consistently used for the time the music was played.

it may be the rom issue, but I don't remember having this with 1.2...

just wondering if others experience something similar to this as well....
[Nexus S Android Development] doc_v15:
Using v1.3 so far so good. Have no complaint yet. Using Oodie miui rom. Smartassv2/deadline
[Nexus S Android Development] Blackcrx:
Currently running 1.4test and CPU spy is still showing deep sleep at idle.

400mhz shows when I'm listening to music with the screen off

No SOD either.

Build #133
[Nexus S Android Development] :
I'm pretty sure it's a standard CM Kernel feature...?
[Nexus S Android Development] :
It's not an issue, it's a feature, read the OP please. Thanks!

--- --- ---

Okay, I feel self concious about not releasing 7 versions yesterday, but my testers are reporting that DI fixed at 400 MHz is stable, which is great. I'll implement that in the next test version: I'm working hard on it, yesterday I spend about 18 hours making test versions, while I learn to debug the kernel. I'm getting better with using pointers and dereferencing correctly, you can check out my latest commits (see OP) which I push to github yesterday, but I know I can get my performance governor based DI idea working! I went to bed at 2:30am last night, about 4 hours later than I should have done, just because I felt I was very close... But the goal seemed to move further away sometimes!
[Nexus S Android Development] 309041291a:
5 hours 40 minutes on-screen use, 13 hours

can't post screen on XDA app though :(.

Second day of usage

Nexus S (GMS i9020a)

Paranoid (1.6 - 4.0.4)

Matrix Kernel (CFS - 20.0)

Intellidemmand (800/100)

Deep Idle (On - Noop)

Live OC - 105 (800/1000)

BLX - 98 (Inverted Apps)
[Nexus S Android Development] alexdemonumber3:
Can you make a version for AOSP-JB? this kernel is too good..
[Nexus S Android Development] 309041291a:
I'd just wait until official JB comes out before you ask for stuff like that

Nexus S (GMS i9020a)

Paranoid (1.6 - 4.0.4)

Matrix Kernel (CFS - 20.0)

Intellidemmand (800/100)

Deep Idle (On - Noop)

Live OC - 105 (800/1000)

BLX - 98 (Inverted Apps)
[Nexus S Android Development] Articudos:
Official binaries are not released.

IMO, that's kind of mixture with ics.

Just wait until official release of binaries.;)
[Nexus S Android Development] madd0g:
You mean the kernel source.
[Nexus S Android Development] Articudos:
Well, I don't have any idea about kernel source.

FYI,

http://xdaforums.com/showthread.php?p=28847971
[Nexus S Android Development] gotjazz:
Thanks - - I gathered that it wasn't an everyday on demand governor. What my question really pointed at was whether it made a lot of sense to experiment with other governors or min freqs. Usually I use smartassv2 400/1000 with deep idle on for example
[Nexus S Android Development] :
I think maybe with rasbean, whether or not init.d works depends on where you install busybox?
[Nexus S Android Development] :
It's going to keep your device running on higher frequency, which uses more power. So it's a compromise. I only use smartassV2 to play asphalt 7. And I only play Asphalt 7 to test OC. So, who uses what and why varies a great deal. Ondemand will quickly get your clock down to the lowest necessary frequency, so it's the best choice for saving power. Considering how good it is at saving power, it really is quite remarkable how snappy it is.
[Nexus S Android Development] stojshic:
The way I got it, dunno if I'm right, is that if you install brainmaster's tweaks, you must install busybox to /xbin for init.d support to work. Rasbean, by default, doesn't support init.d, that's way brainmaster added support for it in it's tweaks...
[Nexus S Android Development] caliban2:
Depends on your settings, you still using 800/800/800?
[Nexus S Android Development] :
No, I've set it to aim at 1.2GHz, and scale down from there steadily. If it detects any need to scale up, it goes straight back to the top.

Here's a kernel for you, since you're here: http://d-h.st/wkj (more RAM)

...and for Non-CM users: http://d-h.st/UCs (more RAM)

... and for anyone who can't make use of the extra RAM, normal versions will be on the spreadsheet in a couple of minutes...
[Nexus S Android Development] :
v6.0.1 is here: http://goo.gl/HvUrp

-Re-added High Resolution timers to fix android OS bug

-Used a couple more of thalamus' commits to fix a section mismatch (in a different way to how I fixed it)

-Tried to strip out some useless stuff from the .config

-Test update to mainline 3.0.47

Please continue to report any crashes in the usual way:

-Your model i9020 i9023 etc.

-Your ROM

-Kernel version

-What you were doing at the time of the crash

-Upload a last_kmsg if you can

And if apps don't seem to be working right, try fixing permissions in CWM recovery, and/or wiping cache.
[Nexus S Android Development] alen1901:
Downloading and flashing 6.0.1 more RAM. Testing begins.

Sent from SpeedMachine i9023
[Nexus S Android Development] caliban2:
That's not really smartass anymore... ^^ But yeah, batt-life will suffer doing it like this. Is asphalt that heavy on the CPU? I can play NfS Hot Pursuit lag free with smartassv2, but on 400/100/400 MHz...

Hehe, "ram it up cm"... You trying to say something? ^^

BTW, v6 was doing fine for five hours, but I'll test v6.0.1.
[Nexus S Android Development] aladin6:
Great explanation, you surely made some tweaks for the ondemand governor so ;).

Downloading 6.0.1 version. Feedback later ;).
[Nexus S Android Development] Articudos:
I installed it via Stericson's busybox installer.

Anyway, I fixed it:p

Trying v6.0.1 now..:D
[Nexus S Android Development] azrealsoh:
I wanna sell this phone to a friend of mine few days ago. After I flashed this kernel, i change my mind. Thank you bedalus!
[Nexus S Android Development] Jamalsid:
would you mind detailing how you did that please? I know I can achieve the same thing by flashing brainmasters tweaks but I dont want to if i can avoid it.
[Nexus S Android Development] Articudos:
Removed

Don't flash this,
[Nexus S Android Development] :
If someone can confirm it, i will. thanks!
[Nexus S Android Development] aladin6:
To all members, DO NOT CHANGE/SELL/EXCHANGE your NS to other ones until.... bedalus stop that project :( (I hope that he will never do it :o)

---------- Post added at 02:59 PM ---------- Previous post was at 02:57 PM ----------

3MB(6.0.1) and every time a network error... Come on i can't wait that much !
[Nexus S Android Development] leap_ahead:
bedalus i get nfc servicr keep wake with 6.0.1

ok after reboot is ok

thanks
[Nexus S Android Development] Jamalsid:
just going to do a nandroid and then flash this and test my init.d script.

I assume you need busybox in xbin?
[Nexus S Android Development] caliban2:
Which 6.0.1, normal or ram-test?

NFC service is normal for me, 9 wake locks in an hour, 3 secs total. (Though I always wonder why it's even there, NFC is disabled.)
[Nexus S Android Development] leap_ahead:
the normal ...
[Nexus S Android Development] Articudos:
Sorry. My mistake.

I forgot to remove BM's tweak.

Here is r2,

Init.d installer for crespo, flash via cwm or twrp.

Be sure to install busybox first.:)

http://db.tt/VIPVUmB8

@bedalus

If Jamalsid confirms, I'll make new post, so you can link to that post:D
[Nexus S Android Development] Jamalsid:
Well it boots but my init.d script is not running.

I am running rasbeanjelly 2012-10-16 with Marmite 5.1 I think, cant really remember tbh!

busybox is installed in the xbin folder and my script looks like this

#!/system/bin/sh
# ---------- CPU (Overclock and Gov) ----------
#echo "smartassV2" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
#echo 100000 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq
echo 1200000 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq

# ---------- BLD (Backlight Dimmer) ----------
# Enabled (0 - Disable; 1 - Enable)
echo 1 > /sys/devices/virtual/misc/backlightdimmer/enabled

# Delay (in milliseconds)
echo 4000 > /sys/devices/virtual/misc/backlightdimmer/delay

# ---------- Vodoo Colors ----------
#echo 1951208320 > /sys/class/misc/voodoo_color/red_multiplier
#echo 1720296160 > /sys/class/misc/voodoo_color/green_multiplier
#echo 1974299520 > /sys/class/misc/voodoo_color/blue_multiplier
#echo -50 > /sys/class/misc/voodoo_color/red_v1_offset
#echo -53 > /sys/class/misc/voodoo_color/green_v1_offset
#echo -44 > /sys/class/misc/voodoo_color/blue_v1_offset

# ---------- BLN (Backlight Notification) ----------
# Enabled (0 - Disable; 1 - Enable)
echo 1 > /sys/class/misc/backlightnotification/enabled

# Blink (0 - Disable; 1 - Enable)
echo 0 > /sys/class/misc/backlightnotification/in_kernel_blink

# Blink Speed (1 is fastest; 10 is slowest)
echo 10 > /sys/class/misc/backlightnotification/blink_speed

# Blink Mode
# MODE 1: Normal blinking, no special timing effects
# MODE 2: Starts fast, and slows
# MODE 3: Starts slow, and speeds up
# MODE 4: Starts fast, slows, then speeds up again, etc
echo 1 > /sys/class/misc/backlightnotification/blink_mode

# Max Blink Mode
# MODE 1: how blinks there will be.
# MODE 2/3/4: how many times the pattern will repeat
echo 0 > /sys/class/misc/backlightnotification/max_blink_count

# Final Blink State(1 is on, 0 is off)
echo 0 > /sys/class/misc/backlightnotification/blink_finalstate

permissions are set like the screenshot.

Any ideas?

Does the name of the file matter?
[Nexus S Android Development] Articudos:
@Jamalsid

Plz restore nandroid, and try r2 again. I removed permission related lines in update-script, but didn't removed BM's init.d package.:silly:

Permission in 99_myscript in screenshot is correct.

Duplicated 99 can be problem:silly:
[Nexus S Android Development] Jamalsid:
Ok will do
[Nexus S Android Development] JokerAce:
Try to avoid using 99 or 98 for init.d scripts. As there are a couple of script hack on forum that generates those init.d scripts with 99 - 97 as the initial of the file name. I always use 96 or 95 to be safe.
[Nexus S Android Development] caliban2:
Oh come on, in his case the number won't matter. And if someone uses script-mods plus his own script, he has to have a look into them anyway.

Your rule reminds me of another myth, "wiping caches BEFORE flashing a zip prevents bugs". :p
[Nexus S Android Development] Jamalsid:
Your second zip doesn't create the initd folder, can I just create it myself?
[Nexus S Android Development] gregorypeg1000:
Now with custom voltage i can finally run 1200mhz :D. Only one question.On 5.1v bedalus implemented gpu oc when the cpu freq is at 1200mhz.Is this happening automatically or i hava to do something manual to oc the gpu?
[Nexus S Android Development] :
Automatic!
[Nexus S Android Development] Accidd:
After 1 day of testing custom voltage i got nothing ;) I mean no reboots with 1200. Whole day browsing network, Tapatalk, emails. Still great battery. I've added +25mV to int and arm voltages for 1200 frequency. Smartass governor.

Nice ;)

Sent from my MIUI Nexus S Jelly Bean.
[Nexus S Android Development] atxbang56:
Awesome kernel on MIUI 2.10.19. Custom voltage is perfect for phones that doesn't really like OC. Thank you bedalus.

Sent from my AwEsOmE Nexus S

Samsung Nexus S

Android 4.1.2 Jelly Bean

ROM : MIUI 2.10.19 by MIUI France

Kernel : Marmite v6.0.1 Extra Ram ( CFQ / SmartAssV2, 1.2 GHz)
[Nexus S Android Development] gregorypeg1000:
Are you sure that it works? My 3d scores at quadrant and antutu remains the same no matter if it runs at 1200 or at 1000mhz.
[Nexus S Android Development] :
I'm not entirely certain no. I haven't personally tested it. The main way I test is on Asphalt 7, which I think got smoother, but I might have been imagining it. I'll double check the code and do some 3D benchmarks to make sure.

Also, can anyone confirm if ADB is working? I think I removed something important!
[Nexus S Android Development] gregorypeg1000:
Ok.Yes,adb works
[Nexus S Android Development] alen1901:
I am syncing sources, i will check tomorrow for adb.

Now excuse me, i go out on a beer, ill drink some for you guys. ;) :beer:

Sent from SpeedMachine i9023
[Nexus S Android Development] :
Ah, yes, you were right. I thought I'd done it correctly, but in fact, I had not changed anything! I've just built a test version and my nenamark2 score went from 24.7 to 27.6 fps.

I'll have to upload another set now!

EDIT: Actually, I'm struggling to find reliable voltages, and I think that it might be because ideally, the FSB should be a divisor of the CPU freq. I'm looking at how morfic does it now, which is quite interesting. I really want the 220MHz bus, because it makes gaming much nicer, so the obvious choice would be a top freq. of 1100MHz, however morfic has 1096MHz, but again, I think this has something to do with clock dividers. I need to make sure I get the right values for stability. If I remember rightly, very few people were unable to run morfic's T11 kernels.

EDIT2: Okay, morfic's approach is very clever. I've not stolen his approach, only his specific configuration for T11, since when I first got my nexus s, that was the kernel I used for a very long time. A very very long time. Hopefully, this will build without errors, and run without crashing. Fingers crossed!

EDIT3: Booted, and Nenamark is up to 27.9 FPS. Just going to play some Asphalt 7 for a few minutes, see if all is well...

EDIT4: Well, that was fun. I finally got up to 100 gold stars on Asphalt 7, so I've probably unlocked a new car to celebrate this successful new kernel mod. Seems totally fine. I'm just going to make a little adjustment to smartassV2 because having the ideal freq set to the OC frequency is a little overkill. I'll go to 1GHz :p

Will upload shortly.
[Nexus S Android Development] Articudos:
Yes:)

If it confirmed, I'll put .placeholder in r3.
[Nexus S Android Development] :
v6.0.2 is here: http://goo.gl/HvUrp

See the changelog on the spreadsheet, or read my previous post above. All seems well at my end, and I'm looking forward to the feedback. Enjoy!
[Nexus S Android Development] caliban2:
Good timing, 6.0.1 ram-test just crashed on me. Got very laggy, notification-bar vanished, then it froze, reboot to bootanim and then bootloop. Oh, I've been watching youtube-videos when it happened. (I love that new smart-tv!!!)
[Nexus S Android Development] :
What, the Samsung one?