yashsingh1/xdaforums huggingface dataset:
[Nexus S Android Development] Lar5:
What a nice surprise to see that this amazing kernel is still kept fresh. Thanks for sharing bedalus :good:

I've had a few crashes with 8.2 on my i9023 running SlimBean build 3.

First time I was writing a SMS and it just froze for 10-15 sec. 1365331338415.txt

Second time i had just enabled backlight dimmer and notification and OC'ed to 1.096 Ghz

(stable at this freq. the last half year) 1365335862342.txt

Hope these last_kmsg's points out something useful.

When it's not crashing everything feels very smooth. :D
[Nexus S Android Development] shivasrage:
Nice to see you back beadalus...:)

Thank´s for the updates...:good:

cheers
[Nexus S Android Development] :
Hmm, looks horrible, the task killer going mental in both messages. There's a new version out shortly.

Try the next version and report back if you get any further trouble
[Nexus S Android Development] :
v8.3 is here: http://goo.gl/HvUrp

-Adds voodoo, fixes 100% battery and bluetooth drain.

Please continue to report back on stability issues! (Hopefully there will be none!)
[Nexus S Android Development] anshumandash:
Wow. I was on 8.0 today morning my time and now it's 8.3. Thanks a lot for the update. My phone now feels new again. :)

Sent from my Nexus S
[Nexus S Android Development] leap_ahead:
Here the result for 8.3cm : All working !!! But I see Screen Refresh rate is 56.14... the v7.2.2 is 49.22

+1 need for 412Mb ram now!!
[Nexus S Android Development] :
Yes, I decided to keep it the same between i9023 and amoled. It keeps the code simpler.

High Ram version this evening...
[Nexus S Android Development] :
Yes, I've been busy today!
[Nexus S Android Development] leap_ahead:
But lower screen refresh rate is not mean battery saver?

Sorry i forget ...on nstools is not showing the blx ...so i dont thinkis working
[Nexus S Android Development] :
I don't know if I'll add BLX. I personally liked it, but it was never requested, praised, mentioned, or even acknowledged by anybody. I think people just want to charge up as much as possible.

Yes, the reduced rate was a saver for battery, but I'm not sure whether it is worth it or not. Try the new refresh rate for a bit, see if it looks nicer. Then judge if discharge rate is affected badly.
[Nexus S Android Development] leap_ahead:
blx is not 100% battery ?
[Nexus S Android Development] :
Yes, user configurable memory was an idea of DerTeufel, but I don't think it's complete yet
[Nexus S Android Development] :
v8.3 bigmem: http://goo.gl/HvUrp

This is the exact same v8.3 kernel, just with more memory taken from the camera module. It may break the camera app on some Roms, but for a lot of you, this is the one!
[Nexus S Android Development] sdhanjal15:
YouTube is fixed. Just needed a bigmem patch.
[Nexus S Android Development] migz012788:
what scheduler is best for ondemand? specially when using games for this kernel??
[Nexus S Android Development] sdhanjal15:
Reflash your ROM.
[Nexus S Android Development] JokerAce:
Deadline
[Nexus S Android Development] robrob777:
how can i patch it?

youtube it is not working here. on JB doublex

thank you
[Nexus S Android Development] sdhanjal15:
Adams jelly belly ROM add highbigmem. And it began to work.
[Nexus S Android Development] :
Sounds like some people can run it, some can't. That's weird. I think there must be a reason, like different phone model or something. Mine is amoled. I'm going to reboot and wipe cache and dalvic and see if that can break it, but i doubt it.

Edit: it still rebooted perfectly.
[Nexus S Android Development] sdhanjal15:
Rebooted during instagraM browsing.

https://www.box.com/shared/67853d117625ed25498a
[Nexus S Android Development] spupuz:
Fixing permission?

Inviato dal mio Nexus S con Tapatalk 2
[Nexus S Android Development] :
It's probably my biggermem settings, I may have gone too far.

Hmm.... maybe not. I'm no expert at reading these logs, but it looks like it had some issue with ADB. I'm sure I've seen a couple of reports that enabling USB debugging causes a reboot too.

Just for confirmation, how about you first: see if you can enable and disable USB debugging with no issues; then with USB debugging disabled, see if your app works normally.
[Nexus S Android Development] jalyn02:
Two words...love it!
[Nexus S Android Development] alen1901:
Awesome kernel. ;)

Sent from SpeedMachine i9023
[Nexus S Android Development] Icecoldmeat:
Deadline.
[Nexus S Android Development] :
For tchaari: http://d-h.st/Sjf

This is the exact same kernel, but with the ramdisk from AdamG's .1.1 (it will not work on CM 10, I tried.) I'd like you to try this, and see if it boots. If so, I need to find out why. Also, do you have amoled?

Anyone else struggling to boot the release version from the OP, feel free to try this one too, but no guarantees... this one is UNTESTED.

Please report back if this one works for you, but the original didn't.
[Nexus S Android Development] N@th_OC:
Usb debugging is crash for now.Reboots and FCs are normal. It's a known bug of CM10.

The problem has been fixed in the last CM10 maguro version. We have to wait kalim's next build for our nexus s.

---------- Post added at 10:33 AM ---------- Previous post was at 10:30 AM ----------

Won't boot for me. My model is a i9023.

Variants seems to be the problem.

like the problem of usb debugging, it seems not everybody is impacted.

Please people who have USB debugging not working and bedalus v2 won't boot, can you post the name of your model of Nexus s i9023, i9020A, i9020...
[Nexus S Android Development] Bucci:
following all manuals here, I'm not able to go through Google logo stuck with my 9023 (tested 3 (JB) kernels with the same result)
[Nexus S Android Development] :
Yes model versions will be useful.

About Deep Idle, I found this: https://github.com/bedalus/bedalusKERNEL/blob/jb_cyan_base/include/sound/soc-dai.h

...which is part of the sound system and specifically:

struct snd_soc_dai {
const char *name;
int id;
struct device *dev;
void *ac97_pdata;	/* platform_data for the ac97 codec */

/* driver ops */
struct snd_soc_dai_driver *driver;

/* DAI runtime info */
unsigned int capture_active:1;	/* stream is in use */
unsigned int playback_active:1;	/* stream is in use */

...which means that, if my programming skills have come far enough, I can modify Deep Idle to check with this struct to find out if the stream is in use. If it is, then DI can be active. If not, then DI must remain inactive. Even if I can do this, it's probably going to be looked at as an 'ugly hack', but if it works... :p
[Nexus S Android Development] N@th_OC:
I think it's definitely a i9023 problem. When ICS sources was release, there was problems like that.

Hardware variants always causes problem....

---------- Post added at 10:53 AM ---------- Previous post was at 10:51 AM ----------

I will definetly follow that, if you need somebody to test your updates, PM me.
[Nexus S Android Development] alen1901:
I had a reboot with 1.4d

Cyanogenmod RC2

Min:100mhz

Max:800mhz

Deep Idle: ON

Init.d scripts: bln, yours, cm9 stock

Happend while exiting xda app.(multitasking) Might be a rom problem. Kmsg attached.

http://db.tt/fJkEOcQs

Sent from SpeedMachine i9023
[Nexus S Android Development] :
I can see that it's not my code that caused that, but unfortunately, I have no idea what the problem might have been. If it happens again, post again.
[Nexus S Android Development] leap_ahead:
u are fast !!!!
[Nexus S Android Development] :
On 8.3 it should charge to 100%, blx is not required.

Interestingly, the limit hardcoded into the kernel is 95%. I wonder why they did this...
[Nexus S Android Development] sidnoit22:
Limit is 95% and it shows 410mb of memory in setting plus everything is so smooth. :)
[Nexus S Android Development] skinner12:
Hi,

Where can I find latest row code?

Thanks..

Nocerino's Rulez with RAScarlo's ROM features TriNitY ;)
[Nexus S Android Development] :
If you're building your own kernel you also need a couple of patches for elevator, I'll find them and put the links here asap.

Here's row: https://github.com/maxwen/enrc2b-kernel-BLADE/commits/master/block/row-iosched.c

Here's what you need first: https://github.com/maxwen/enrc2b-kernel-BLADE/commits/master/block/elevator.c
[Nexus S Android Development] TsarFlow:
So latest is V8.3 or will there be some updates soon ?
[Nexus S Android Development] :
Unless I screwed something up really badly I'll probably have a rest for a bit!
[Nexus S Android Development] leap_ahead:
Guys u use cfq row or noop? Anyone know what is the best for broswer on internet ... Also i use ondemand..
[Nexus S Android Development] benoit2600:
Can you push your source on github please ? :fingers-crossed:
[Nexus S Android Development] noloukos:
Camera on jellyshot 3.2 with 8.3 bigmem cm version works fine
[Nexus S Android Development] leap_ahead:
+1 for rasbeanjelly
[Nexus S Android Development] skinner12:
I've tried to patch but I've error on elevator.c

block/elevator.c: In function â€˜elv_reinsert_requestâ€™:
block/elevator.c:620:38: error: â€˜struct elevator_opsâ€™ has no member named â€˜elevator_reinsert_req_fnâ€™
block/elevator.c:623:39: error: â€˜struct elevator_opsâ€™ has no member named â€˜elevator_reinsert_req_fnâ€™
block/elevator.c: In function â€˜elv_completed_requestâ€™:
block/elevator.c:845:15: error: â€˜REQ_ATOM_URGENTâ€™ undeclared (first use in this function)
block/elevator.c:845:15: note: each undeclared identifier is reported only once for each function it appears in
block/elevator.c:846:4: error: â€˜struct request_queueâ€™ has no member named â€˜notified_urgentâ€™
block/elevator.c:847:4: error: â€˜struct request_queueâ€™ has no member named â€˜dispatched_urgentâ€™
block/elevator.c:848:3: error: implicit declaration of function â€˜blk_clear_rq_urgentâ€™ [-Werror=implicit-function-declaration]

and compile stops.

EDIT: Resolved editing blk files..
[Nexus S Android Development] TsarFlow:
8.3 bigmem non-cm on XenonHD is pure smooth and camera works well.
[Nexus S Android Development] androidforeve:
Agreed running great with slim bean
[Nexus S Android Development] rockerblood:
works on unofficial AOKP 8.3bigmem cm, camera works as before :)
[Nexus S Android Development] tchaari:
bedalus is back in action. Great news :)
[Nexus S Android Development] treesurf:
8.3 is working great on HellyBean, camera is fine, 410mb RAM. Many thanks Bedalus!
[Nexus S Android Development] leap_ahead:
Battery 100% is ok ! No need to show in nstools
[Nexus S Android Development] sperelli:
Which version for miui 3.4.5? I see default kernel is cyanogenmod..

EDIT: CM version sticks.
[Nexus S Android Development] samsyr:
Anyone have problem with Wi-Fi tethering in 8.3 big memory CM

Sent from my Nexus S
[Nexus S Android Development] :
ah, possibly because I forgot pmfast
[Nexus S Android Development] Nicolae-Daniel:
Hello

Can you please tell me if i can flash this on cm10?thnks.
[Nexus S Android Development] :
One works, the other doesn't. See if you can work out which is which...
[Nexus S Android Development] deani77:
So far working stable on CM10.1... Thanks for another new version
[Nexus S Android Development] polobunny:
Nice to see a rebuild. Too bad I'm not here anymore. =(

I'll post my Nexus S up for sale soon enough, so I'll have to put it back to stock. Shoo.
[Nexus S Android Development] :
How's the new SGS3 working out for you?
[Nexus S Android Development] polobunny:
Pretty good. A few little hiccups with the switch from 3.0 to 3.4 kernel on CM10.1 & other roms but otherwise it's a very capable phone. The "downside" is that the battery is definitely not lasting as long as the Nexus S, which in itself isn't a record breaker either.

The fact it's somewhat recent and the switch from 3.0 to 3.4 makes it rather hard for kernel devs to create a stable kernel for one, and even more so to optimize it for battery saving. It'll come in due time though, I'm sure.

I'm still messing with governor tunables to find something I like, plus all this mpdecision, thermald and default startup scripts are confusing me. :p

I imagine it's pretty similar for nearly all recent phones.

Still very pleased, and you get used to the screen size pretty quickly, not mentioning the drastic increase in performance (casually score 11500 on Antutu with the base CM kernel and no overclock).

How is it on your side with the HTC One X+? That's a beast of a phone too.
[Nexus S Android Development] ej8989:
MMS delays a significant amount of time when using cfq and row schedulers. Noop works fast. Can anyone explain? I'm on Slimbean 4.2.2 build 3.
[Nexus S Android Development] :
Co-incidence? Keep testing please
[Nexus S Android Development] :
v8.4 is here: http://goo.gl/HvUrp

-Fixes PM Fast

-other minor fixes

Please test! (Anything else I forgot?)
[Nexus S Android Development] :
The main problem with the phone was that the hotplugging was causing lags and heat, and was generally a total disaster. I fixed it by preventing hotplugging, and create my first app (!) to control the number of cores I wanted manually.

Generally, limiting to one core everything works just great anyway!
[Nexus S Android Development] leap_ahead:
is bigmem ?
[Nexus S Android Development] Erythnul:
While I know I haven't been very active in the thread recently, I'm just throwing in my thoughts on this..

BLX, for me, is pretty much a must-have feature in a kernel. I'm really sorry I haven't been appreciative enough of it, but I always put it on 90%, and still get a great time.. So I'm now mentioning, acknowledging and praising it all in one post, I think requesting it might be a bit much? :P

Anyway, if it's not added, it'd be a bummer, but nothing will stop me from using Marmite, not even things I'd previously considered dealbreakers ;)

Thanks again for all your great work on this kernel bedalus!
[Nexus S Android Development] leap_ahead:
why 90% ?? i use it on 100%
[Nexus S Android Development] dchriste90:
I had had reboots and lag with 8.3-bigmem, but 8.4 seems better to me (much better actually). I have been rocking it, since posted, at 1.32GHz with row scheduling. Wifi-tether works as well.

--dchriste
[Nexus S Android Development] alen1901:
To lower charge cycles so battery will last longer (in termin of years) until it reaches its lifetime cycle.

Sent from SpeedMachine i9100
[Nexus S Android Development] :
Nope, I'll do another bigmem tomorrow if the feedback indicates no problems :D
[Nexus S Android Development] :
Good to hear from you. I'll re-consider BLX if a few more people express an interest
[Nexus S Android Development] :
Okay, I have a confession, I broke my whole build setup, and it took me a long time to get around to fixing it. In the process, I lost all of my repos. Of course, they're on github... but I started fresh.

To build the current version:

-start with the bare samsung source:

git clone https://android.googlesource.com/kernel/samsung.git

-use this patch: http://d-h.st/fsV

-Then merge android/common-3.0 (you may need to use mergetool on one wireless file)

The toolchain is that listed in the op.

The reason it's not on github is because I can't bear the hour or more of uploading I'll have to do! But I will get around to it at some point :p
[Nexus S Android Development] skinner12:
Sorry, I don't remember what is blx..

Nocerino's Rulez with RAScarlo's ROM features TriNitY ;)
[Nexus S Android Development] openlatedotorg:
Using 8.4 on slim build 3

Things seem fine, except when using camera it flashes when it opens then works fine.

Thanks for the wicked work man!
[Nexus S Android Development] leap_ahead:
Bedalus i get lower screen time with 56 ..if u can and want make it 49 pls ...
[Nexus S Android Development] :
Might have to put this one to the vote
[Nexus S Android Development] polobunny:
Not looking to stir anything, but was there ever any sort of tangible proof that BLX made a real world difference? You know, other than limiting your battery to charge past that, was it ever tested that it somehow extended battery life further than one you'd charge at the "fake" 100%?

Not looking specifically at BLX itself but rather any battery limiting testing done on the same type of batteries that compares any number <95% vs say the accepted 95~97%. Just wondering if everyone using it is just using it because it sounds great or there's an actual difference in longevity.

I ask you this bedalus, because if anyone ever looked into research or papers that might have been done about this, I think it would be you. :p

Edit: As for 56 vs 50, didn't the later kinda made things choppy on SAMOLED? Wasn't it the reason you split it in the beginning?
[Nexus S Android Development] alen1901:
Really? You can tell that after what, bearly one day of using kernel? Hmmm

Sent from SpeedMachine i9100
[Nexus S Android Development] TsarFlow:
v8.4 is a bit smoother on XenonHD than v8.3 bigmem.
[Nexus S Android Development] leap_ahead:
Because i do the same usage every day !! Also air kernel if u use the 65fps u will se that is more battery drain ..

That all on my phone i dont know how is work on other!

I see many user that vote 7.2.2 kernel so i am not alone
[Nexus S Android Development] alen1901:
You know that you need at least one day (one charge cycle) to calibrate battery. Maybe it will be better in next few days.

Sent from SpeedMachine i9100
[Nexus S Android Development] leap_ahead:
Every day i flash new kernel ..i am on 8.4 now and wait gor bigmem
[Nexus S Android Development] :
BLX - Yeah, the only place I've seen it vindicated was in a modern samsung netbook, where the BIOS had a BLX-type option which limited the charge to 80%

The frame-rate reduction was modified to work on amoled, but leave SLCD unaffected. The choppy effect was only noticeable when you go below 50 fps
[Nexus S Android Development] leap_ahead:
Same here
[Nexus S Android Development] :
He's right, the biggest battery eater is the screen, and going from 56 to 50 would give about a 10% reduction in power (I measured it with the ammeter back in the day...) so would yield a noticeable increase in battery life, albeit a small one.

The thing is, does anyone feel like the frame rate is noticeably better than the v7.* series? If not, then we might as well have the battery savings.
[Nexus S Android Development] :
The camera flashes when it opens? Did this happen on v8.3?
[Nexus S Android Development] leap_ahead:
Yes same on 8.3... The screen that show is flash
[Nexus S Android Development] :
Can you be a bit more descriptive? I can't test myself...
[Nexus S Android Development] leap_ahead:
One with the flash and other the normal..View attachment 1868236View attachment 1868237

See u tomorow guys ...time for sleep
[Nexus S Android Development] micha3lvd:
Yep same here, it blinks some gray color before it goes to the app..
[Nexus S Android Development] treesurf:
Awesome update bedalus, thank you. Looking forward to the next bigmem version!
[Nexus S Android Development] polobunny:
So empirical claim but no empirical evidence, you'd say? Cause I've only seen people saying it SHOULD affect battery lifespan, but no test whatsoever done on an albeit long scale by any company or person to back those claims. Seems like people just do it because it would sound like a good idea, while it may be completely useless.

Thanks a bunch for the answers. =)
[Nexus S Android Development] openlatedotorg:
The screenshots just posted are fairly close to what happens. It seems it takes the camera app a second or so to refresh the camera to finally display the camera view.
[Nexus S Android Development] xxxMADxxx:
On Marmite 8.4 cm only 406 mb of ram right??
[Nexus S Android Development] leap_ahead:
Yes
[Nexus S Android Development] :
And on v8.2 the camera behaved normally?
[Nexus S Android Development] deepaktom:
I think that half a second of the camera flashing is not a bad compromise for the extra RAM

---------- Post added at 12:14 PM ---------- Previous post was at 12:09 PM ----------

Yep. a bigmem version is coming soon I think.
[Nexus S Android Development] Lar5:
I've just tested a the camera (SlimBean 422 b3 mod) with different kernels.

With Marmite 7.2, 8.2 and 8.4 i can't see any difference in the cameras startup.

The screen is gray for about ½ a sec. I even tried Matr1x v. 25. Same same behavior.

http://www.youtube.com/watch?v=ztaJ-KcHfFs

It works fine :good:
[Nexus S Android Development] :
wonderful feedback. Thanks!
[Nexus S Android Development] xxxMADxxx:
Latest marmite kernel work nice on miuiv5..:good::good:
[Nexus S Android Development] Nicolae-Daniel:
How can i overclock and also change gouvernor on cm10.1?:D
[Nexus S Android Development] andrei1015:
You have to go to settings, performance, processor.

Sent from my Google Nexus S
[Nexus S Android Development] ppamungk:
Been using the kernel 8.4cm with Jellyshot for a day now... Seem to be very stable and smooth... Hopefully will continue to be like this :) Great job Bedalus.. Thx for the great job....
[Nexus S Android Development] :
Here we go: http://batteryuniversity.com/learn/article/how_to_prolong_lithium_based_batteries

Reasonably believable source stating that cutting the charge early improves the longevity of the battery
[Nexus S Android Development] polobunny:
Yeah, but once again, no stats were provided regarding this on any battery tested (unless I missed them?).

And an excerpt from the link shows what really matters (not that you or I learned anything there I believe, but worth pasting IMHO):

Cheers once again for the link, it's a good read. Hopefully other users will peruse this, if only for general knowledge about Li-Ion batteries.

Edit: Should be added that the excerpt targets batteries NOT in use, but the same principles apply to batteries in use. Cool = happy battery
[Nexus S Android Development] alen1901:
Well i was 6 days at sea last summer, and every day i left my nexus in car on hot sun, all day, so when i came to car u just pulled battery and let it cool down. No problem with battery, no problem with phone.. nothing, all is like it used to, and i doubt someone would place its phone on sun for a longer time than me. :D

Sent from SpeedMachine i9100
[Nexus S Android Development] andrei1015:
Wow 8.4 seems really neat! But I did have a random reboot. It happened while I was listening to music and the phone was in my pocket. I didn't have the change (or the knowledge) to capture a logcat. Sorry. Keep up the good work :D
[Nexus S Android Development] polobunny:
Consider yourself lucky, but 6 days isn't really prolongated abuse either. :p
[Nexus S Android Development] alen1901:
On 50+ degrees, whole day, six days in a row.. not abuse? :eek::eek:bi dont want to know what abuse IS then, hahah.

Sent from SpeedMachine i9100
[Nexus S Android Development] :
Were you overclocking?
[Nexus S Android Development] polobunny:
I've seen horrible things.... u_u One of my friends left his cell RIGHT in the windshield area and the battery busted and bubbled all over his car dash. It smelled terrible and the cell was dead.
[Nexus S Android Development] nibla101:
SIO and Smartassv2 is a badass combo, I noticed that from the vta2-kernel. And please don't go reducing the refresh rate this phone is laggy enough already :o
[Nexus S Android Development] andrei1015:
Only to 1096:o
[Nexus S Android Development] :
Your phone wasn't designed to go at that speed. If it reboots it's hard to say whether it's a kernel issue
[Nexus S Android Development] Basche:
Just wanted to say I'm using the 8.3 highbm and it works fine with MDO and camera is fine. Thanks for the rebuild bedalus
[Nexus S Android Development] !Lür:
What do you mean with this? How can i proove if my phone was designed to go at this speed?

I remember the 1096Mhz Step is a specific step, am I right?

PS: Good work, love this kernel. Best kernel for my Nexus S ! :good:
[Nexus S Android Development] leap_ahead:
Bedalus 8.4 big mem for us ???
[Nexus S Android Development] alen1901:
On 1096 fsb (gpu) is overclocked too, and your phone probably cant stand that gpu oc.

Sent from SpeedMachine i9100
[Nexus S Android Development] sperelli:
Any hint about undervolting? I would gain some battery life..