yashsingh1/xdaforums huggingface dataset:
[Nexus S Android Development] TsarFlow:
First, how do you get 1400MHz when the kernel can't go higher than 1320 ? I'm using last marmite with last AnTuTu. I get 5500 at 1096MHz, ans 6000 at 1320 but 1320 is really not stable, I always get reboots even when I overvolt by 25.
[Nexus S Android Development] ej8989:
Sorry for that. Non-marmite kernel @ 1400mhz. On marmite i'm getting lower scores, about 3000-4000. I'll try the latest antutu.
[Nexus S Android Development] .stendeck:
So far, there seems to be no issues at Stock 4.1.2 here. Running for at least 2h.
[Nexus S Android Development] :
Thanks very much, that's interesting.
[Nexus S Android Development] .stendeck:
No problem. But another question that I wanted to ask you for a long time (since 7.*): on Stock ROM I never got marmite as stable as on other ROMs. I often get reboots especially when using messing apps (SMS/MMS, Hangouts), very randomly. Seems to be only soft reboots (don't need to enter PIN of SIM card, uptime doesn't stop). How can I give you some information about these reboots? What I have to do to get a proper log?
[Nexus S Android Development] Miguun:
After 25H, still no issues with the V9 beta :) !
[Nexus S Android Development] TsarFlow:
Same here :)
[Nexus S Android Development] :
After a reboot, wait for device to restart, then upload the file /proc/last_kmsg somewhere, then tell me where! :)
[Nexus S Android Development] .stendeck:
Ah, I see: /proc/last_kmsg was the location of what I meant. Thanks. :)
[Nexus S Android Development] fleischbanane:
Here too. :)
[Nexus S Android Development] suspect008:
Can use with SlimBean 3.1(JB 4.1.2)?

Hello,

I ran marmite for quite some time and it was very stable, fast and good battery for stock, Slim 4 and hellybean and for rasbeanjelly (all JB 4.2).

But today I went back to slimbean 3.1(JB 4.1.2) and when I flashed marmite 8.7 bigmem phone got stuck at the boot logo. can you please tell me what could be wrong or doesn't marmite 8.7 support Slimbean 3.1?

Note : Nexus s i9020T, Slimbean 3.1(JB 4.1.2), Currently running matr1x kernel 25(Drains battery Like hell).

Thank you.
[Nexus S Android Development] :
Thanks for the positive feedback and constructive criticism. I'll just wait for this month's up-to-date toolchain, then I'll merge the mainline updates, and push v9.0 to the version matrix
[Nexus S Android Development] adm1jtg:
Could you please post a test build (slim based) for the greeen screen fix and slow wakeup issue so I can test for you
[Nexus S Android Development] :
The green screen fix is simple, but will won't help the slow wake-up. I'll do it when I'm next in the development chair.
[Nexus S Android Development] xbs:
http://pastebin.com/nzchHBrx
[Nexus S Android Development] :
Everything got killed with no explanation why. Is it reproducible?
[Nexus S Android Development] xbs:
Don't think so. Was browsing and suddenly freeze, a couple of seconds later it rebooted.
[Nexus S Android Development] TsarFlow:
Happened to me only when I OC @ 1320, don't have any problem @ 1096.
[Nexus S Android Development] Basche:
By any chance, are you using operation Killjoy tweak package? I'm getting the same issue and it's from that tweak package.

Whenever you get the chance for a green screen fix, it will be greatly appreciated.
[Nexus S Android Development] xbs:
No tweaks and no OC.
[Nexus S Android Development] andrei1015:
Any kernel/ROM/phone will have issues when overclocked at more than 10-12% of its original frequency. Or so I heard.
[Nexus S Android Development] morrigan91:
Hi, [MENTION=4128576]bedalus[/MENTION]..

Slow wake-up for me... 3-4 second but random.. and with smartassV2 - cfq.. slow and lag... Ondemand-Performace work great!!

Many Thanks..
[Nexus S Android Development] ironia.:
Thanks
[Nexus S Android Development] :
I can't remember. Try it as long as you've got something to flash back to. (There's some 4.1.2 kernels in my second post)
[Nexus S Android Development] onmyouji:
Hi bedalus,

I also have the same problem as mentioned by stendeck. Sometimes my phone just reboot by itself, but it's only soft reboots (no need to enter PIN of SIM card, uptime doesn't stop). Most of the time, it happens when I was downloading or install / updating something from Google Play store.

FYI, I'm running Slim ROM 3.1 (Jellybean 4.1.2), Marmite 8.7 CM, my CPU governor is smartassv2

I've also attached the last_kmsg

Please let me know if you need anything else. Thanks.
[Nexus S Android Development] leap_ahead:
after some day with v9beta and this I prefer this !! I think zCache make different for me ... also the rom I use is not support SElinux and I don't know if is good to use kernel with selinux enable ...
[Nexus S Android Development] :
Probably a lot of people feel the same way.
[Nexus S Android Development] leap_ahead:
so the problem is for SELinux ?
[Nexus S Android Development] :
I think it's too much for this device. It's similar to my G4 powerbook at home. I can run OS X 10.5.x if I wanted, but I'm running 10.4.x because it's lighter, and was developed for longer. I think we can all live without SELinux to be honest. We were getting by without it fine before!
[Nexus S Android Development] leap_ahead:
I wait for Android 4.4 :p
[Nexus S Android Development] adm1jtg:
I completely agree however, here is the issue, selinux is enabled both in the rom and in the kernel, if you only have one side enabled it causes all kinds of extra overhead and lots of freezups and issues. Thus if your rom has selinux support you need to use a kernel with selinux support or your asking for trouble. Cm and slim and a few other newer 4.3 roms all have selinux enabled in the rom portion thus we would need to match it with an selinux enabled kernel.
[Nexus S Android Development] :
Maybe best not to bother with 4.3?
[Nexus S Android Development] adm1jtg:
Actually, me personally, I have found 4.3 slim beta with your latest kernel that has selinux enabled to be very snappy and so far have had no issues at all. Since selinux is in permissive mode it really does not seem to have much if any extra noticeable overhead for me. I actually believe the 4.3 rom is more responsive then the 4.2.2 roms I have used in the past.
[Nexus S Android Development] :
In that case, plough on!
[Nexus S Android Development] jwee5467:
Does this work with 4.1.2?
[Nexus S Android Development] :
See post 2
[Nexus S Android Development] iakoboss7:
post 2 isnt for ics 4.0.4???
[Nexus S Android Development] Basche:
Im using 8.7 with 4.1.2. I haven't tried the experimental/test builds.
[Nexus S Android Development] :
Oops, that's right!
[Nexus S Android Development] explorer-10:
are you using both the latest slim beta and beta v9 kernel?

btw, if i flash kernel for slimbean 4.3, do i use aosp or cm?
[Nexus S Android Development] Setting.Out:
Aosp
[Nexus S Android Development] adm1jtg:
Slim 4.3 has the newest marmite already included
[Nexus S Android Development] explorer-10:
v9 beta 3.0.94?
[Nexus S Android Development] adm1jtg:
I cannot say its the exact same as the beta as slim pulls the code directly and compiles it directly into the build. I can say it has all the new features and tweaks including selinux enabled and .94 code level. We have been working very closely with bedalus on this.
[Nexus S Android Development] .stendeck:
Okay. Now I got the next reboot, but last_kmsg hasn't been created in "/proc". :-/ Was a self-reboot, I didn't do anything manually.
[Nexus S Android Development] polobunny:
last_kmsg doesn't get written on a self reboot.
[Nexus S Android Development] .stendeck:
Wait. What? I think that's the way?! On MDO I got another reboot, and there the file was written successfully. Maybe logging has to be enabled on Stock ROM?! Nevertheless, I will upload my last_kmsg now.

---------- Post added at 01:15 PM ---------- Previous post was at 01:11 PM ----------

Here it is: https://docs.google.com/folder/d/0B2nXCU5mcKlcUzZTNHc3WXdqMUE/edit
[Nexus S Android Development] explorer-10:
i know it's too much to ask, but is there any hope our nexus will be able to use kernels higher than v3.0,94+?
[Nexus S Android Development] cgulliver:
Does this work with CM 10.2?
[Nexus S Android Development] leap_ahead:
of cource
[Nexus S Android Development] ironia.:
Where to manage blx? I haven t that option through nstool.

the battery charges 100% is only cosmetic?

Tnx
[Nexus S Android Development] :
v9.0 is here: http://goo.gl/HvUrp

-Merged mainline updates

-Latest monthly toolchain from [MENTION=4825437]Christopher83[/MENTION] (thanks!)

No-one has reported any serious bugs with this so I'm happy to announce the general release! Please report any issues you find.
[Nexus S Android Development] iakoboss7:
thanks for the work! :)

is it compatible with 4.2.2 roms? (cm10.1 last nightly here)

also is it bigmem 410mb?
[Nexus S Android Development] Zahih:
Thanks Bedalus,

For your continues support for our old device.

I have tried v9 beta in Carbon nightly 20130911 with no bugs, no reboot...

Just great, smooth and fast..

Gonna try this v9.
[Nexus S Android Development] onmyouji:
If I'm not running Android 4.3 ROM, is there any need for me to update? Any additional feature or bug fix for other android version lower than 4.3 ?
[Nexus S Android Development] :
I wasn't expecting it to be, but I think someone already tried and confirmed that it is! Give it a try, and if not, you can always go back. It won't cause any harm.
[Nexus S Android Development] :
Mainline updates provide extra security, stability and performance improvements (sometimes regressions - though these are uncommon and usually picked up and fixed quickly). They are only usually fixes for things that would normally never occur, but it is nice to have them anyway!

The toolchain is built with optimisations specific to this platform, so should provide performance improvements.
[Nexus S Android Development] iakoboss7:
thank you for all the info! i will try it out!
[Nexus S Android Development] fleischbanane:
Wow, it's blasting fast with todays CM10.2 Nightly. Nexus S is back in the game! :cool:
[Nexus S Android Development] Setting.Out:
Boots and working well on 4.1.2... :)
[Nexus S Android Development] Basche:
I'm on 4.1.2 also and no problems so far. :D
[Nexus S Android Development] .stendeck:
Were the last two kmsg logs helpful to find a solution for our reboot issues? :-/
[Nexus S Android Development] iakoboss7:
i second this :)
[Nexus S Android Development] treesurf:
I'm trying v9 with the latest Helly Bean and I'm having problems With Bln. When I open the BLN Control app it says this liblights is not supported. Is this a ROM or kernel issue and is there a work around?

Sent from my Nexus S
[Nexus S Android Development] adm1jtg:
Everything working well on slimbean build 1 EXCEPT I am still getting that green tinged screen off issue mentioned earlier. No issues enabling BLN
[Nexus S Android Development] rodem77:
Hi Bedalus, I see that some people tested your v9 on 4.1 or 4.2 without problems but in your table you wrote that v9 is for 4.3. If I try it on a 4.2 may I lose some functionality that may be specific for android < 4.3? Maybe something that is not easy to "see"?

Thankyou
[Nexus S Android Development] :
It appears to be completely fine!
[Nexus S Android Development] :
Oops, I forgot about that
[Nexus S Android Development] :
Sorry didn't see this until now.

You've got a line in here at the top:

[ 0.000000] Linux version 3.0.50-Cyanogenmod-gb97752e (hudson@koushik-lion) (gcc version 4.6.x-google 20120106 (prerelease) (GCC) ) #1 PREEMPT Sun Aug 4 04:59:11 PDT 2013

Which means this is not my kernel, probably recovery or stock cyanogenmod kernel...?

But anyway, there is something worrying in it:

[ 12.610931] yaffs: Attempting MTD mount of 31.4,"mtdblock4"

[ 12.624499] onenand_wait: ECC error = 0xaaaa

[ 12.656791] onenand_wait: ECC error = 0xaaaa

[ 12.796697] onenand_wait: ECC error = 0xaaaa

[ 13.399398] yaffs: block 33 is bad

[ 13.431375] yaffs: block 111 is bad

[ 13.571462] yaffs: block 450 is bad

[ 14.163135] yaffs: yaffs_read_super: is_checkpointed 0

These corrupt blocks might be a problem. What's on the yaffs bit... the IMEI? Anything else much? The radio or something? (I can't remember)

Is your device working fine now?
[Nexus S Android Development] ironia.:
I tried it a few hours on stock 4.1.2, i see into catlog a lot of clipoboard messagges and come back to 8.7

8.7 for me is smoothest
[Nexus S Android Development] explorer-10:
i just had a random reboot...idk how many times it's been so far, but i lost count(not that it's been THAT many, but I really did lost count) anywho, here's my last_kmsg log
[Nexus S Android Development] :
My guess is that the kernel is trying to map some virtual machine memory that doesn't exist, somehow. Maybe an app is behaving badly? See if you can narrow down when it happens.
[Nexus S Android Development] notbrodie:
v9cm working great on carbon rom. one question: voodoo sound seems to have stopped working. any ideas?

Sent from my Xoom
[Nexus S Android Development] Dark_Eyes_:
Finally !!! I got my 10 posts so I can post here.

First off, thank you SO MUCH Bedalus for the amazing work. Our Nexus S is getting kinda old but you are still taking your precious time to give us the best kernel around.

That being said, is it possible to remove BLN altogether from the CM version of Marmite. The latest nightlies of CM have been tampering with liblights so the BLN included in your kernel doesn't work anymore, yet it also breaks the CM based BLN which works fine on their stock kernel. I don't know if it's possible but the best solution (if you don't want to investigate how to enable it back) would be to stick with the CM version of BLN...

Other than that your kernel is a must have for the Nexus S. Right now the CM 10.2 nightlies give us only 383 mb of RAM, while I get 409 with your kernel. Simply awesome !

P.S. Voodoo sound is working for me on latest CM10.2 nightly...
[Nexus S Android Development] :
Thanks, it's always nice to get a good report!

I think I'll just pull the included file from the zip. At this point I can no longer remember what it's doing in there, and we'll see if removing it breaks stuff.

I'll attempt to sort out that green flash issue, and then I'll upload an update
[Nexus S Android Development] Dark_Eyes_:
Alright! I'll be waiting patiently!

As for the green flash, I only experienced it with the punchy setting in voodoo . So I just added +2 to each RGB and it's good since then. Is it really a kernel problem?
[Nexus S Android Development] explorer-10:
yet, another reboot once again
[Nexus S Android Development] onmyouji:
Do you overclock your phone? From your signature, it seems you're running at 1320
[Nexus S Android Development] explorer-10:
I was overclocked, but then I reflashed the mod and now I'm back at default speeds of 1000/100 max/min. I still get lags from time to time when waking the screen or closing it. Or even, when I try to use maps.Google.com through the browser, it gets choppy.
[Nexus S Android Development] andrei1015:
I flashed it a few hours ago and I like it. It's smoother and apps don't get killed as much. Well, the launcher. CM10.2

Flowed from Nexus S
[Nexus S Android Development] :
Just to confirm, it rebooted at stock speeds and voltages?

If so, can you switch Rom for a while?
[Nexus S Android Development] Dark_Eyes_:
I've decided to thoroughly test the kernel on stock speeds and voltages to see if I also get reboots. I find that Marmite is not as stable when overclocked as other kernels but it's a risk I was willing to take. For now it seems rock solid on cm10.2 with stock settings. And to be honest I don't notice much of a difference in performance...
[Nexus S Android Development] iakoboss7:
[MENTION=4128576]bedalus[/MENTION]

for some weeks now i use this app https://play.google.com/store/apps/details?id=com.grilledmonkey.lagfix&hl=en

and the app says that the cache partition cant be trimmed and this may be a hardware or a kernel issue! i am on cm10.1 (latest nightly) and using your v9 cm kernel (which works very nice!!!).

is it a hardware issue or is it something you can "enable" in the kernel?
[Nexus S Android Development] :
I've got no idea, this is new to me
[Nexus S Android Development] :
to be continued...
[Nexus S Android Development] :
Hello. I'm back in the game :D
[Nexus S Android Development] ej8989:
Wow what a surprise! It's so unfortunate of me to have a bricked Nexus S :/
[Nexus S Android Development] :
I think I was lucky with mine, it's still going strong after all the torture I put it through, and my wife has had it for ten months too.
[Nexus S Android Development] Setting.Out:
My wife still refuses to let me touch her phone.. ;)
[Nexus S Android Development] :
It's nice to see you keeping the nexus s going with your enthusiasm. I've seen your 'War against Obscurity' thread, very nice work :)
[Nexus S Android Development] Setting.Out:
I'm glad to see you around again.. I've considered upgrading, but my phone won't stop working.. ;) I'm glad your NS is as stubborn as mine.. I'm always up for testing if you'd like to send an idea my way.. ;)
[Nexus S Android Development] :
I'll see what I can do about building a kernel tomorrow
[Nexus S Android Development] Zahih:
Welcome back NS's legend..

I'm glad to hear this surprise.

Thx
[Nexus S Android Development] leap_ahead:
wow welcome back !
[Nexus S Android Development] ottoemezzo:
What a morning, I've just heard these excellent news! I'm glad I kept my good old nexus, the fun is about to begin again.

Thank you for coming back!
[Nexus S Android Development] :
Hello again. It feels good to be back!
[Nexus S Android Development] leap_ahead:
:P any new kernel?
[Nexus S Android Development] Setting.Out:
T-minus eta requests has begun... [MENTION=4128576]bedalus[/MENTION] its been several hours.. Eta... Lol..

Sorry, I just couldn't resist. ;)
[Nexus S Android Development] drac0:
OMG [MENTION=4128576]bedalus[/MENTION] is back!!! My NS just had a reboot :D
[Nexus S Android Development] rakeshbro:
WoW What a breaking news!!!!! :victory:

Welcome Back Legend :highfive:
[Nexus S Android Development] :
Thanks for the warm welcome. I'm building now. I'm starting from scratch with an up-to-date toolchain, and the original source code. I should have a basic version ready within the next few hours, barring any major hiccups.

I've learned a lot since moving away from the nexus s, so there'll be a more confident approach to the new version.
[Nexus S Android Development] drac0:
Damn, cant wait to test! :D
[Nexus S Android Development] :
Okay, kernel is built, but I am having a weird problem... when I open the camera, it tells me 'insert sd card'

Anyone know the issue with this?

I've used philz recovery and I'm on android 4.4.3
[Nexus S Android Development] Setting.Out:
No mounting issues on any KK rom yet..

I am on a CM based CyanAOSP, I could see if behaves the same..
[Nexus S Android Development] :
No don't worry. If it's not a known issue it just means I've stuffed up something in the kernel config.
[Nexus S Android Development] Setting.Out:
Take your time, we're excited, but this is for fun..
[Nexus S Android Development] :
Version 10.0

AOSP: http://d-h.st/4g4

Changelog:

- Samsung jellybean kernel source latest

- BLN/BLD/Fastcharge added

- Voodoo sound/colour added with my colour as default (most stable whitepoint at different brightnesses)

- My ondemand and fixed bus speed at 200 MHz

- Battery 100% fix

- CFQ as default io scheduler

- Extra free memory enabled

- Haptic strength sysfs

- PM fast to fix wifi speeds and bluetooth fix

- MTP

I don't think I missed out anything particularly critical. I need to spend a bit of time playing now to see if I'm happy with the performance. CM version will come tomorrow if anyone needs it?
[Nexus S Android Development] Setting.Out:
SeLinux?
[Nexus S Android Development] drac0:
Yes please :) CM version for latest nightlys, btw no more tuned FSB with 1.1 Ghz OC? SeLinux? zRam defaults to 0?

Thanks!
[Nexus S Android Development] Setting.Out:
CM type Roms do account for 80% of the KK available.. ;)
[Nexus S Android Development] :
OK, cm version no problem.

I don't believe zram is a benefit.

Selinux can be enabled, but is it worth it?

OC is available but I haven't tested it.
[Nexus S Android Development] Setting.Out:
Zram is of little use, selinux is nice for controlling apps with odd permissions, and I am happy with anything you build for us.. ;)

Smartassv2 and row are still included?
[Nexus S Android Development] drac0:
Yes, was asking cos lately I found that zram=0 gives more performance and more juice out of battery, same goes for KSM. SeLinux for some weird apps but I can live without it :) and for OC yes I'm missing your rock solid 1.1 GHz with FSB and tuned voltages, that did wonders although it was only 10% increase.

---------- Post added 13th July 2014 at 12:00 AM ---------- Previous post was 12th July 2014 at 11:55 PM ----------

SmartassV2 is unbeatable, Im using it today with NOOP scheduler thanks to [MENTION=3263349]ekerazha[/MENTION] and his Guru kernel and hope to see it here again with those tweaked values! :D
[Nexus S Android Development] varefaz:
This is for android 4.4?
[Nexus S Android Development] Setting.Out:
Yes, but probably works on jellybean as well...
[Nexus S Android Development] ekerazha:
Btw, in my mind SmartassV2 is a temporary solution :p I've some ideas for a new governor (a hysteresis based governor), but at the moment I'm busy with other projects, so I included SmartassV2 until I have time to develop my own governor :D
[Nexus S Android Development] teoserio:
Hi bedalus, you're never really left from here for us you know? [emoji6]
[Nexus S Android Development] :
I was just typing a reply and suffered a soft reboot!

Does anyone know of any kk ROMs that are stable on ART?
[Nexus S Android Development] Setting.Out:
...hmm., I haven't really used ART since December, and I used Euroskank for several days, with no issues.. I did briefly try ART on Omni, but only briefly as it was noticeably slower..
[Nexus S Android Development] KrisMurdrum:
Good god, is this thread still alive? ?

And even better, Bedalus is back to kerneling for it! ?

Almost makes me pine for me Crespo... ?
[Nexus S Android Development] anshumandash:
I am using slimkat with art for a long time on my ns. It feels faster than dalvik.

I am posting in the ns forums like the old days. It feels home. Thanks Bedalus for coming back. [emoji3]
[Nexus S Android Development] leap_ahead:
[MENTION=4128576]bedalus[/MENTION] i flash the last but bln not working ..
[Nexus S Android Development] drac0:
I've used it for a short time with CM kk but ART ate lots of memory and was slower so I got back to Dalvik, but it was rock solid. Also tried Omni and pretty same experience ROM was very stable. Maybe [MENTION=4573092]Sumanji[/MENTION] knows a bit more, just saw in his sig he is using ART too :)

[MENTION=4128576]bedalus[/MENTION] are you still with the statement that tuned screen herz with 65 fps hack will cause drain about 10% more power compared to the usual 56 fps?
[Nexus S Android Development] :
10% Yep, I measured it with an ammeter.

ART is good. Pre-compiled beats on-the-fly compilation every time.
[Nexus S Android Development] :
It's there. You need to wipe cache and fix permissions probably!
[Nexus S Android Development] alen1901:
So, idle2 is not present in v3? That means no DI nor this idle?

Sent from SpeedMachine i9023
[Nexus S Android Development] :
DI is unstable and idle2 measures no improvement in amps. I need to do an overnight drain test to confirm, because the amp meter may not be accurate.
[Nexus S Android Development] sykomaniac:
Anyone else not having usb debugging/mounting options after flashing kernel?
[Nexus S Android Development] meisze:
Is it init.d support ?
[Nexus S Android Development] leap_ahead:
crt is fix ?
[Nexus S Android Development] :
I'll look for a fix in the next release. But I can't modify any code at the moment because I'm testing all the possible IDLE2 frequencies to see which is the most power saving. I suspect it will be 400MHz.