yashsingh1/xdaforums huggingface dataset:
[Nexus S Android Development] alen1901:
Bedalus, kernel 3.7 released for ARM devices. Check that out.

And also i will probably change to my dads galaxy s2 in a few days, as he is buying s3. But i will be here for a while. ;)

Sent from SpeedMachine i9023
[Nexus S Android Development] micha3lvd:
I'm having no problem with BLX on the latest rasbeanjelly 4.2.1 with 7.1.7.. used to though :)
[Nexus S Android Development] :
Oh cool, that might be easier.
[Nexus S Android Development] alen1901:
Yeah. Dunno why and how did they jump from 3.4 to 3.7. But thats the android world, you never know whats next. :p

Sent from SpeedMachine i9023
[Nexus S Android Development] JokerAce:
Welcome to SII soon :)

Apologies for OT. How's things here? :angel:
[Nexus S Android Development] alen1901:
No bad reports, bedalus made stable beast of kernel. ;) now, he is trying to make 3.4/3.7 kernel to work on crespo. :)

Sent from SpeedMachine i9023
[Nexus S Android Development] nelars:
Bedalus,

First reboot I get ever since started using marmite. I have to confess about running the cpu at 1096MHz :)

But I figure there could be some interesting info in the log, so here it is the link in case you want to take a look.

http://db.tt/F1uppKhS
[Nexus S Android Development] Sucky1983:
Hey, my device also gets random reboots when over clock just a little bit. I gave up an are running stock freq.

Gesendet von meinem ODYS-NOON mit Tapatalk 2
[Nexus S Android Development] polobunny:
Sorry to burst the bubble, but overclocking logs are useless. What could appear as genuine errors can simply be due to the overclock. More luck finding a needle in a haystack than fishing a bug out of a kernel when people overclock. :p

What is good to know though is that 1096MHz doesn't seem stable on your phone, and like that bedalus can adjust the default voltages if needed be to catter to the most people.
[Nexus S Android Development] :
It does indeed look like a problem with binder. I may well do a version with the backported binder but without the oom_score_adj
[Nexus S Android Development] polobunny:
*shakes fist* :p
[Nexus S Android Development] :
Wait, I read the last_kmsg before I read your post. The problem with over clocking is that I've seen incredibly bizarre things happen, and it's frankly a miracle that the log was backed-up, because stuff is going haywire with the CPU. In your case however it looks like a totally standard log. The problem in trying to eliminate issues this way is that you don't know for sure if the log is due to a error in the code, or an error in the hardware executing it.
[Nexus S Android Development] :
Haha, yes. Legitimate shaking.
[Nexus S Android Development] polobunny:
Hey I was wondering for a moment!

I'm at 165 hours uptime. I commented earlier at 100 hours, and now as I slowly approach the 200 I can finally say I'm perfectly happy with marmite. 7.1.6 is ROCK solid and behaves just as well if not better than the CM kernel. Props!
[Nexus S Android Development] shivasrage:
+1
[Nexus S Android Development] noobiekins:
257 hours on marmite v7.1.5, on jellyshot 0.3
[Nexus S Android Development] Kolero:
I'm at 166 hours on 7.1.4. Is something wrong with my phone? Is it supposed to be this stable? Even my radio has stayed up the entire time, where I used to have it drop out at least once every couple days.
[Nexus S Android Development] JokerAce:
Glad to know :D

I have a kernel dev here whom is as helpful, generous, and motivated as Bedalus. I am glad to meet such people on the phones I use. Real dedicated people. :good:
[Nexus S Android Development] :
We miss you! But glad it is working out on your new device/forum :)
[Nexus S Android Development] alen1901:
Send me a PM with link to his thread. ;)

Sent from SpeedMachine i9023
[Nexus S Android Development] :
http://d-h.st/9r5

Just a test version for people to try out

-Mainline update to 3.0.56

-Revoke gamma control (I prefer my old colours)

-Include the backported binder code.

Please check to see if multi-tasking seems okay or not :)

NB - This is the CM version
[Nexus S Android Development] spider623:
Any news for the 3.7 based kernel ?

Sent from my Nexus S
[Nexus S Android Development] :
I can't even get the 3.4 kernel to compile!
[Nexus S Android Development] VerminX:
160h on 7.1.7 with rasjelly + 1200 oc

I'm a heavy user clocking around 8 to 10h screen on time per day

Everything working and super stable

Thanks again for the best kernel ever
[Nexus S Android Development] :
I think I'm going to abandon 1.2GHz step and replace it with 1.32GHz with 10% FSB boost.

I know some people might be a bit unhappy about this, but I'm afraid that I want more OC for selfish reasons, and that means 1.2 has to retire.

Also, I'm not seeing any problems with multi-tasking, so I'll keep the binder code for now.
[Nexus S Android Development] _yaz_:
just to complete the circle; do you charge twice a day (at least), or did you change the battery, or ... ? my crespo is unable to produce such low consumption with one charge, in any way.

[OTHER Topic]

would anyone, please, explain what is this "binder" is aimed to ? should i change from 7.2 just because of this ? what may i expect from it ?
[Nexus S Android Development] pooley:):
Hi Bedalus :)

thanks for your hard work on that Marmite K. I'm on xylon rom (4.2.1) and I tried to flash your marmite to OC my phone (GNEX) to run GTA Vice City w/o any lags lol, but when I flash the zip CWM said extracting etc then UNUNDERSTADABLE MESSAGE 3 everything runs like it's ok but when I go to my about phone It seems like I still have the daxxmaxx kernel.
[Nexus S Android Development] dadaz007:
This kernel is not for GNEX but for Nexus S. It can't work with your phone.

And the UNUNDERSTANDABLE MESSAGE is just a joke.
[Nexus S Android Development] :
http://d-h.st/zNo

This needs testing. It has higher OC. You may need to find the right ARM voltages. Try +25mV if you get a reboot.
[Nexus S Android Development] mrengineer:
i faced this problem too! but mine is nexus s.

when i install, it says:

Is this normal?
[Nexus S Android Development] superng888:
it's normal lol... its just a joke ;)
[Nexus S Android Development] anshumandash:
As soon as I select 1320, my phone gets into boot loop. I am now running at 1096. Should I increase only voltage for 1320 or across all frequencies?
[Nexus S Android Development] VerminX:
I would love to try it, could you post a normal non Cm ver?

Please keep the voodoo gamma controls, it makes my amoled that much more beautiful.

---------- Post added at 11:19 PM ---------- Previous post was at 11:16 PM ----------

I should have mentioned about the extra battery and chargers everywhere I go. I like to keep the screen nice and bright too, that's why long time ago I gave up on trying to make it on one charge per day.
[Nexus S Android Development] jwee5467:
I increased the 1320 voltages by 25 mV and works fine. Will undergo testing in a bit when i get home to my charger.
[Nexus S Android Development] seriosbrad:
If anyone has Santa Rockstar can you please tell me how it performs for you on this kernel? I'm running 1200MHz and it's unplayable because it stutters on both 7.1.7 and 7.2 on the rasbeanjelly ROM. It stutters at stock voltages and clocks too, before you ask!
[Nexus S Android Development] hiphopboy:
1320 mhz has reboot when i'm running any apps and its make so hot with my phone

---------- Post added at 02:11 PM ---------- Previous post was at 02:10 PM ----------

Voltages by 25 mV is you set more with default is 25 mV or just set 25 mV
[Nexus S Android Development] Hawkw1nd:
He means increase it by 25mV; if it's 1350 mV, then set it to 1375mV .
[Nexus S Android Development] anshumandash:
With the new test version I see 1 hr 40 mins wake lock by Android OS which shows as 50% usage by Android OS in the battery stats.
[Nexus S Android Development] caliban2:
I'm not getting this, android os is at 5%. So it must be a combination of ROM/your setup/kernel, but not kernel alone.
[Nexus S Android Development] anshumandash:
Didn't have this on 7.1.6. Haven't changed anything other than flashing the new kernel. I am on JellyShot ROM.
[Nexus S Android Development] Lar5:
Not stable. It's working fine at 1320 MHz until the CPU works at 100% for more than 2-3 minutes. Things like video recording and Youtube.

Increasing the voltage with .25 didn't help. Actually it seem to crash a bit faster.

I'll try testing a bit more. Maybe push the voltage another notch. I don't like going over 1.4 volts

Marmite 7.2 was rock solid at 1200 MHz.
[Nexus S Android Development] Drizzzle01:
How should we be overclocking? Should I be setting the setting within Settings -> Performance or Nstools? Also, currently I have to set Settings -> Performance to start on boot along with nstools start on boot because I can't set Nstools for the governor. Is this how it's supposed to be set?
[Nexus S Android Development] ej8989:
1320mhz is very stable on my i9023 with CM10 Dec11 Nightly.

I'll be keeping this rom and kernel combo until knzo's new 4.2.1 rom comes out.

Great development. :good:
[Nexus S Android Development] sdhanjal15:
Kk. Seems alright so far.
[Nexus S Android Development] :
I've just tried taking my code out, and fixing Deep Idle at 400 MHz using min and max in NSTools... Got a SOD. Hmm. I should of thought of trying this a long long time ago.

So... it's not my code that's causing the SODs. A relief, but also a shame.

Tried 800MHz with performance governor, set with NSTools, and that froze too.
[Nexus S Android Development] morfic:
You need to find a way to change the sleep frequency from 800 to 400.

Not having 800mhz in the cpu's policy will cause SoD anyway you try it.
[Nexus S Android Development] :
The code i wrote sets a value for the user_policy.max and the user_policy.governor to performance. Even if i set 800mhz i still get SODs.

Right now with this jellybean version, DI doesn't work reliably at all, even without modifications.
[Nexus S Android Development] sdhanjal15:
Stable an no reboots for far.
[Nexus S Android Development] :
I'm pretty sure if you turn all your radios off, and quit all apps, it'll not wake up from deep sleep.
[Nexus S Android Development] sdhanjal15:
Eh I'll pass
[Nexus S Android Development] y3mita:
No Voodoo colors?
[Nexus S Android Development] dckmastaflex:
im a noob with all this i flashed it over a stock jb rom, idk what deep idle is i figured it was in the dev options but figured wrong should a noob like me be messing around with this kernal?
[Nexus S Android Development] Articudos:
http://bit.ly/OgRLIx

Let's wait..;)
[Nexus S Android Development] y3mita:
Voodoo works fine
[Nexus S Android Development] sdhanjal15:
Just sayingg. But I feel like this kernel is bit lagyy on jelly bean. Thats just what I'm experiencing.
[Nexus S Android Development] :
Yes, i was in a rush to get something with mtp out for JB, and also test my fixed fq DI code on a different platform. I'll probably release one last stable for ICS before i start working on JB properly.
[Nexus S Android Development] d_phekt:
Damn... Another kernel that doesn't boot on CM10. There must have been some major changes within the kernel with JB. We were able to flash many different kernels with CM9. Keeping my fingers crossed.
[Nexus S Android Development] :
The test version doesn't boot?
[Nexus S Android Development] d_phekt:
Nope.. stuck on bootscreen. Same with a few other kernels I've tried.
[Nexus S Android Development] :
Testing what will be my final ICS release. Look at that for good overnight behavior.
[Nexus S Android Development] N@th_OC:
Same for me, stuck at bootlogo.
[Nexus S Android Development] :
Okay, I'll have a look and see if it's something to do with the ramdisk or config options.
[Nexus S Android Development] :
Here is v1.4d (ICS): http://d-h.st/66r

-stable*

-probably last version I'll do for ICS

-DI fixed at 800MHz

-reorganised fixed DI code a little

*when I say stable, I mean it didn't have any SODs, FCs or any other unwanted behaviour within the limits of my testing, however, I have left some debug messages in there just in case so feel free to report and/or upload your last_kmsg if something happens.
[Nexus S Android Development] pooley:):
Yep I thought first it was a joke but when I reboot and see no change, I start questioning myself ... But well that makes sens with your answer thanks. Any chance to get that working on GNex on day ?

Sent from my toilets
[Nexus S Android Development] caliban2:
Having a free day I emptied my batt sitting at a coffee diner: 3 hours of screentime net, 3G only, gmail-sync, exchange-push, skype on the whole time, lots of opera, bit whatsapp -> android os at 4%. So I really don't think latest test-kernel has suddenly become a batt-eater. Everything's normal for me. (It's been around 6 hours since I disconnected it from charger)
[Nexus S Android Development] ej8989:
Runs great on my cm10 nightly 12/11 + latest marmite w/ 1320mhz OC.

There's no stutter and it's highly playable. Just don't expect your NS to perform like a Galaxy Nexus.
[Nexus S Android Development] anshumandash:
Thanks. I will do some more testing. I had done a clean flash of the ROM on Saturday. So I will try out for a day more to check Android OS usage and report.
[Nexus S Android Development] ptr347:
7.1.7 version is a beast with rasbeanjelly ! So smooth and battery friendly, sometimes unstable but really fast ! I think the kernel just needs sound optimizations for our nexus s and that's all !
[Nexus S Android Development] Nexus HAL:
sound optimization is already supported on the kernel. use DSP manager or Voodoo sound app to fine tune the advance parameters of built in wolfson audio chip of nexus s. I'm gonna stay with v7.1.7 for a long time as gamma control is something i don't wanna live without. it is a very snappy n stable version as well.
[Nexus S Android Development] :
Thanks, but this must be v7.1.6 as the oom_score_adj code is evident in the last_kmsg. I think this is the first time I've seen a reboot reported on that version. It appears to be pretty similar to many of the soft reboots I've seen, where a load of apps are killed. Everything getting killed points to the memory management as the problem, but my efforts to fix that seem to have been in vain!
[Nexus S Android Development] lurtis:
Why is everyone using older versions? I flashed 7.2 this morning using default settings and its been fine so far. Or am i wrong in thinking 7.2 is the latest offering?
[Nexus S Android Development] polobunny:
It's CM10 stable though. Used to have that before, but didn't have this so far and I'm at 237 hours on 7.1.6. Not on stable though, I followed up with the nightlies. There's always this slight possibility it's not the kernel but the rom.
[Nexus S Android Development] :
Today I found out that my wife has bought me a HTX One X+ for Christmas, which was a rather thoughtful gift. I'm quite surprised actually, considering how much she appears to hate how much time I spend on android forums.

But anyway, I'll continue to provide mainline and android-3.0/common updates to the kernel here, and there's a good chance that she will inherit my Nexus S, so I will still be able to flash kernels when she's asleep. :p

This is very sudden and weird, because I dearly love my Nexus S! I don't think I've been so hands on with a device since my Amiga 600. Maybe I should get a classic car to tinker with instead of electronics. Then I can seclude myself and earn 'man-points' simultaneously :p

Despite the hundreds of hours I've put into this, I'm still a novice developer, but I'm smart enough to track down issues (later rather than sooner) and haven't included anything rubbish in this kernel. It's not just my work either, but, by now, it is the work of hundreds of testers continuously testing, reporting bugs, then coming back for more! So thanks to all those guys and occasional girl, without you it wouldn't have been possible. I think the kernel is in a good spot right now.

Since this is almost like a goodbye (although I'm not about to unsubscribe from my own thread!) I sincerely wish everyone the best, and I raise my glass and tip my hat (and in the process soak my hat in my drink) to the community for making this a lot of fun. Keep the thread friendly! :D
[Nexus S Android Development] polobunny:
Oh dang, well here we go. :p

Enjoy the new toy, phones are still heaps less expensive than project cars though. Those are real money suckers once you start adding so you just usually don't.
[Nexus S Android Development] caliban2:
Oh well, it had to happen... Guess I'll start tracking down a N4 after all. Thanks for making this phone the fun it has been and still is!!! You extended its life span at least half a year. :)
[Nexus S Android Development] kwibis:
There goes the last kernel Dev for the nexus s :( thanks bedalus for providing such great services for the old device. Hope to see you around here some more, but anyhow, have fun with your new toy :D

Sent from my Nexus S
[Nexus S Android Development] leap_ahead:
Bedalus thank you for all help and you make my nexus with your kernel

Also i want 1 last kernel !!!
[Nexus S Android Development] metalmoot:
Thanks bedalus, your kernel makes my day since the first release, thanks a lot and I hope you can bring good stuff to the one X owners

Sent From My SlimBeaned Nexus S
[Nexus S Android Development] towelboy:
Thank you Bedalus for your great work and awesome support for this phone! We all will mourn the loss of a great developer (with no attitude COUGH). This thread has always been my favorite because of obvious reasons but what the hay, have fun on that HTC! :D

Edit: I might lose some 'man-points' for this but I love you and your work for making my nexus s experience a whole lot better, gonna miss you :(
[Nexus S Android Development] alen1901:
Noooooooooooo! Best kernel developer and community lover goes away. Now im not that sad because of going to galaxy s2. Enjoy your one x+, bring them your beast kernel, make them happy. ;) and i hope you get nexus4 another Christmas from your wife. :P

Sent from SpeedMachine i9023
[Nexus S Android Development] Hawkw1nd:
Thanks, bedalus. You've been both a gentleman and a scholar. Hope you decide to keep tinkering with the old NS from time to time :) ...
[Nexus S Android Development] mrengineer:
thank you!
[Nexus S Android Development] sisterchick:
Merry Christmas and enjoy your new toy!

This is probably a stupid question, but is it possible to create a standalone flashable that just implements BLN on top of the stock CM kernel? Yes, I'm trying to future proof my phone since I'll probably not see a new one until next Christmas!

The CM BLN implementation doesn't work with BLN Control to turn off the lights at night.
[Nexus S Android Development] anshumandash:
I never thought this will come so soon. I am very sad. :( I can't switch to a diff phone right now and without Marmite can't continue using my Nexus S for long. It's a great loss for everyone like me. :(
[Nexus S Android Development] ej8989:
Thank you for releasing the 1320mhz cm version sooner. I think it's meant for my device. I think i'll be using it unless mathkid releases a new kernel, which is unlikely to happen. Thanks for sharing your programming knowledge with the community. :good:

No.
[Nexus S Android Development] jayjay3333:
You will be missed. Thanks for everything. The kernel, your passion for making a well rounded kernel, finally for your maturity and integrity. That is oddly hard to find in some threads most days.

Cheers

:beer:
[Nexus S Android Development] anshumandash:
I hope you won't remove the download links in future. They might still be very useful for many who would continue to use Nexus S.
[Nexus S Android Development] superng888:
Bedalus... You're the first person that taught me that it's better to give than to receive... You were the first developer that actually gave me a thanks :D thank you for your kernel and I wish you all the best with one x :cool:
[Nexus S Android Development] :
Stock CM kernel has BLN doesn't it?
[Nexus S Android Development] :
No, I won't. I'll keep the kernel up to date as I promised, but it will be less frequent
[Nexus S Android Development] anshumandash:
The Android OS issue is being caused by suing bluetooth. I think this is a bug in the 4.2 ROMs. No issue with the Kernel. :)
[Nexus S Android Development] Zahih:
This is it...

The last kernel Dev for Nexus S finally got new toy... :)

Many... Many.. Many Thanks for your great support that provide great kernel for our old device, thank you also for your patience to answer all the inquiry...

You will be missed here..
[Nexus S Android Development] Jamalsid:
Sorry to see you going. Others have said a lot of what I would have said. So I'll just stick with a simple thank you for sharing your work and I wish you and your family a merry Christmas. :beer::D:beer:

Enjoy your new toy. Your wife has good taste in phones.
[Nexus S Android Development] mrengineer:
i did not use bluetooth but still i have the android os issue.
[Nexus S Android Development] Nexus HAL:
farewell bedalus.. it's been a pleasure to use your kernel. hope to meet you again with one of my future devices..
[Nexus S Android Development] Hawkw1nd:
bedalus, I forgot to ask - the 1320 Mhz test version is using a 240 Mhz GPU clock, right?
[Nexus S Android Development] 1024k:
bedalus

Merci! Thank you! Obrigado Спасибо! Gracias 谢谢！ありがう！ARIGATOU！Danke! Dziękuję! Dank je / u! Mulţumesc! Teşekkür ederim! Tack!Tack så mycket Grazie! Kiitos! תודה לך! Takk! ďakujem, ďakujem vám ; Hvala! شكراً!shokran Ευχαριστώ! 감사합니다 Děkuji! Tak skal du have! Dankon! Hvala, Hvala lepa, Najlepša hvala Gràcies! Faleminderit Hvala! Ačiū, De’koju, Labai ačiū ขอบคุณ ; ขอบคุณมาก(khàwp khun) ; (khàwp khun mâak) shukrīya (بہت) شكريه (bahut) Cảm ơn cô ; Cảm ơn cô nhiều; Благодаря!Благодаря! Obrigado!” Gracias Þakka þér! baie dankie ; Takk fyri! Sipas dekem متشکرم! Благодарам! Hvala Vam! V Təşəkkür Paldies!Pateicos! / Tencinu! Terima kasih Дуже дякую ;Дякую ; Спасибі! Баярлалаа ; Гялайлаа ; Танд их баярлалаа Terima kasih ধন্যবাদ (dhonyobād) Salamat! Trugarez ! Mersi !Trugarez Danke!+

for your work and passion!
[Nexus S Android Development] anshumandash:
Just read in the Helly Bean ROM thread by DerTeufel1980 that he is trying to fix the 4.2 bluetooth awake (Android OS battery stats) bug by tweaking the kernel. I am not sure if Bedalus will have time to look in to this. But if it is possible, it would be very helpful.
[Nexus S Android Development] leap_ahead:
ohh cool !!!!!!
[Nexus S Android Development] jiro-kun:
You liar bedalusssssss.. You said that you're gonna use this device until it wears out.. :( Sigh.. There goes my favorite developer and thread.. I like it here.. The environment and ppl here are so helpful.. Anyhow as other ppl have said it's bound to happen.. Just never thought that it would be this early..

Everything a side.. I want to express my gratitude! Thanks for everything bedalus! Rawk on your other projects later! All the best! And again thank you! :D
[Nexus S Android Development] rockerblood:
hope this will be our Christmas present from you sir bedalus;)

Sent from my Nexus S™ i9020A
[Nexus S Android Development] :
No, 220MHz, just 10% OC
[Nexus S Android Development] :
That post is from a long while ago!
[Nexus S Android Development] :
You're welcome! :D
[Nexus S Android Development] gfinockio:
A gentleman and a scholar, you are - thanks for all your work and I hope to continue to see you around!
[Nexus S Android Development] spider623:
good bey bedalus we will miss you, now i rally have to change phone :crying:
[Nexus S Android Development] :
http://d-h.st/WjR

Here is a version that reduces the screen refresh rate for amoled only. This will save power and make the battery last longer.

What I'm quite interested in is for a SLCD user to try it. Does it work as normal on SLCD device?

Also merged latest mainline. This is CM only version
[Nexus S Android Development] JerryPi:
Hy i have a i9023 with slcd. Well the latest kernel works ok on my phone. It's just that the transitions are not that smooth to the eye as they where in previous versions;)
[Nexus S Android Development] seriosbrad:
brb, buying a One X+ and stalking bedalus