yashsingh1/xdaforums huggingface dataset:
[Nexus S Android Development] stojshic:
I dunno what you've read, and where, but strawberry IS based on rasbean, and more or less only difference is IOCTL (or whatever it's called) which is CM feature, and that's the only reason why we need kernels for CM based ROM's. That's nothing to do with Bedalus
[Nexus S Android Development] caliban2:
What's this all about anyway? Bedalus already said he'll add the other versions in a few hours, then everybody can DL whatever he/she wants. :)
[Nexus S Android Development] simms22:
heads up, theres no nexus s support in aosp android 4.2..
[Nexus S Android Development] alen1901:
I bet we will see some ROM after a week or two.
[Nexus S Android Development] stojshic:
Yup, but if he wants strawberry, he MUST use CM kernel, any other will go to bootloop...

PS. I can't believe Google left us out of 4.2 :/ This phone, for sure, can handle it.... I guess it's time to change it for newer nexus... Considering N4 will probably be around $600-700 here, I'm going for GN...
[Nexus S Android Development] polobunny:
Unsurprisingly though. There's a time you just gotta let it be. :p
[Nexus S Android Development] alen1901:
Man dont buy gnex! Better buy s2 if you really want. But i would wait for nexus4 price go down.
[Nexus S Android Development] RunTech:
What version of marmite kernel (stock,CM,other,) I have to use with slimbean ROM?
[Nexus S Android Development] alen1901:
CM
[Nexus S Android Development] RunTech:
Thanks man :D
[Nexus S Android Development] stojshic:
I'm nexus g33k :) I't wouldn't be my style not to own nexus :D

(a da cekam cenu da se spusti, kad uzimas pod ugovorom ovde, u Srbiji, cene GN su i do 55.000 dinara (550e), tako da ce N4 biti i mnogo skuplji, a cene u oglasima i u prodavnicama obicno zasnivaju na tome, tako da ce biti dosta skup N4 i u narednih godinu dana)
[Nexus S Android Development] aladin6:
Come on man, GNexus is an awesome device, even comparing to S2! Was on Samsung devices and now i really feel the power of Nexus devices, no comparaison! Samsung devices is for girls :D.
[Nexus S Android Development] alen1901:
lets stay on topic please, no more discussing. ;)

Sent from SpeedMachine i9023
[Nexus S Android Development] simms22:
man, the gnex is a great device. id never consider a s2 over the gnex. thats just wrong. if thats what you want, id go for the gnex without even thinking about it.
[Nexus S Android Development] stojshic:
Totally agree with you, gnex is great. I never, ever, considered S2 as it's design is ugly to me (as is S3). Gnex looks great (not that great comparing to G4, but what the heck) and it's most probably gonna be mine in the coming days/weeks...
[Nexus S Android Development] alen1901:
If you look at performance and battery, s2 beats gnex, also better screen on s2 in my opinion. There are decent roms for s2 international version too. So you wouldnt missing anything except googles up to date software. But for allmost the same price or cheaper i would rather buy s2 and sacrifice up to date thing. I have s1+, s2, s3 and nexus s at home, so i know what im talking about. My next thing to buy is s3 or nexus4 for myself. Or s2 if i find cheap one, then sell it for highet price. Its all plaussible in my country. :D
[Nexus S Android Development] atxbang56:
please this is marmite kernel's thread so speak about that

Sent from my pretty cool Nexus S

Phone : Google Nexus S i9023

ROM : MIUI 2.11.9 by MIUI France

Kernel : Marmite v6.7.9 by Bedalus @1096MHz
[Nexus S Android Development] polobunny:
Galaxy Nexus has a higher screen resolution, is pentaband thus absolutely not carrier locked in any way, score similarly in Antutu, has Google support, has a bigger screen. I don't see why the S2 is a winner here except for the better back and front camera and removable storage...

Anywaaaaay
[Nexus S Android Development] atxbang56:
borinnng

Sent from my pretty cool Nexus S

Phone : Google Nexus S i9023

ROM : MIUI 2.11.9 by MIUI France

Kernel : Marmite v6.7.9 by Bedalus @1096MHz
[Nexus S Android Development] dinos3:
Thanks cooking this awesome kernel, and guides ;)

But, can you add 1300mhz without GPU OC? :)
[Nexus S Android Development] waterface:
Apart from, if you're unlucky like I was, the absolutely crappy purple tinted, blotched, grainy, unevenly colored screen. Had to sell it, couldn't stand it. Tried to get a replacement but Samsung "Exclusive" Club didn't help when Samsung tech department folks (who you obviously can not talk to in person, at least in Italy) claimed "customer perception" as they refused to exchange it. Exclusive my ***. I wish we had the kind of customer service that you guys have over the pond.

Ok, I feel better now. :)
[Nexus S Android Development] leap_ahead:
guys stay on chat about Kernel pls !!!!! so what voltage (int and arm) you have for 1096 Mhz or 1200Mhz ... i set to 1350 and 1100 for 1200Mhz
[Nexus S Android Development] VerminX:
I get rock stable 9020t device at:

Int 1200 1150mv

1200 1375mv
[Nexus S Android Development] caliban2:
Kernel is stable and fast, nothing to talk about. :p

Or maybe - is anyone getting no caller-pic? Takes a while to show up here. Wonder if it's caused by the extra ram. Or the usual rom-hiccup once in a while.

Nice voltages. Would they work on my phone too, make oc stable for me? (Deliberately playing dumb)
[Nexus S Android Development] Maxxd01:
With this kernel I have BLN disabled.

Any way to activate it without using third party app ?
[Nexus S Android Development] alen1901:
See 1st post.
[Nexus S Android Development] ScOULaris:
Marmite disables the option from within the CM10 settings, but you can still enable it with NSTools. That's the only way, as far as I know.
[Nexus S Android Development] micha3lvd:
Haven't found a solution for my BLN problem yet =|

Flashed 6.3CM, no succes

Re-flashed ROM + gapps etc, no succes

Messing with settings in BLN Control pro + NS tools, no succes

Only solution is complete wipe?

Still running 2.9CM, once again with 6.7.9CM
[Nexus S Android Development] :
I'm not providing further OC. Feature requests are welcome, bit this is a personal project that I'm just sharing, so be prepared to hear a no.
[Nexus S Android Development] caliban2:
6.3cm, 2.9cm, 6.7.9cm - dafuq, what now?! :confused:

Forget all those apps, use a script (how-to in first post).
[Nexus S Android Development] :
You might as well go to town and backup and format your sdcard. Start again really clean.
[Nexus S Android Development] :
v6.7.10: http://goo.gl/HvUrp

-Re-add Ezekeel's bigmem patch, adds 4MB extra free RAM

This patch is probably fine. I believe the stability issue has been resolved with the buck voltage fix mentioned earlier. Still, watch out for reboots and try to grab me a last_kmsg if you're not over-clocking.

This version will be renamed v6.8 or v7 if I decide stability is technically a feature. :p

Lots of testing required first.

I'm also particularly pleased that no black-screen-with-status-bar issue has been reported, which means I managed to nail the v3.0.35 mainline issue. I looking forward to investigating why this happens. If I can work it out maybe I'll be able to file a bug report to the mainline, team!

Note: If you're on the test version with extra mem, this version offers nothing new, except 4MB less RAM, so it may not be worth your time flashing this.
[Nexus S Android Development] VerminX:
I noticed rdata has added 1300 step to his kernal, I'm wondering if we could maybe get a test kernel here with that frequency ?
[Nexus S Android Development] towelboy:
Flashed 6.7.10 and after the phone turn on I opened calendar right away and the screen froze and I had to pull battery.

No OC!

can I still be able to retrieve a last_kmsg?
[Nexus S Android Development] :
I just answered that question on this very page :(
[Nexus S Android Development] :
No you won't get one. wipe cache and fix permissions. Make sure your 1GHz voltage is 1250mV or maybe you need 1225mV or 1275mV...
[Nexus S Android Development] stojshic:
Just had another soft-reboot :( i was browsing some news... again, last-kmsg was from recovery, so no helping from there... Anyone else noticing this, or is it me doing something wrong? I'm not n00b, and, I did clean install (even formated my sd-card, and didn't restore any apks), kept my installed apks to minimum this time, and still get soft-reboots. I did clean install because of them. I'm on 6.7.8 and latest rasbean. Just to get clear, I'm not, in any way, saying this is coused by kernel, I have no idea what couses it...
[Nexus S Android Development] dinos3:
Can anybody post stock voltages for 1200 on this kernel? (Arm and int, ofc)
[Nexus S Android Development] :
Maybe you should try strawberry. It's based on rasbeanjelly. I expect you can flash over the top (wipe caches) and flash cm kernel.
[Nexus S Android Development] Hawkw1nd:
arm 1300/ int 1100
[Nexus S Android Development] Maxxd01:
Alen, i checked before posting and checked now. I Dont find the required information.
[Nexus S Android Development] dinos3:
Sorry, you are limited to 8 thanks per day

Many thanks!
[Nexus S Android Development] CrackerTeg:
Had a reboot while browsing Tapatalk. Latest rasbeanjelly. No OC. On version 6.7. i9020a
[Nexus S Android Development] Hawkw1nd:
That's OK. I'm not helping in the hope of increasing my thanks meter - just hoping to accrue some good karma :) ...
[Nexus S Android Development] sperelli:
oh so sorry and ungrateful... i hadn't read it!

thanks for the answer.

to tell the truth i use kb3 now and then, but never had those issues with ki1, why do you advice for that?
[Nexus S Android Development] :
Stability issues are solved (I think due to a mistake in the buck voltage setting) since 6.7.3

V6.7.10 is now available with bigmem if you want to help test

Edit:

s3cfb s3cfb: [fb0] video memory released
request_suspend_state: wakeup (0->0) at 5778347565474 (2012-11-14 02:57:27.184060189 UTC)
...
init: untracked pid 5890 exited
Unable to handle kernel paging request at virtual address e70518c0
pgd = e7044000
[e70518c0] *pgd=5700040e(bad)
Internal error: Oops: d [#1] PREEMPT
Modules linked in:
CPU: 0 Tainted: G W (3.0.51-bedalus-03444-gb6b98d2 #443)
PC is at _fw_samsung_mfc_fw_bin_name+0x277d0/0x2b0d8

Actually this crash does actually look like it might have something interesting

https://github.com/bedalus/marmite/commit/e817e9eb06a273f44bafe1e5cefcdbf7ed386405

Immediately after the video memory was released, it crashed. And the panic points to mfc. If you look at the bigmem code in my github link above, that's the same container.

The plot thickens. I introduced the buck voltage bug at the same time as bigmem, and removed both these things at the same time.

However, in v6.7.10 bigmem is back, so we just need more testing to confirm if it's actually safe.
[Nexus S Android Development] :
Restore a nandroid from when ki1 was working?
[Nexus S Android Development] Jamalsid:
http://xdaforums.com/showpost.php?p=30087898&postcount=1311
[Nexus S Android Development] :
Got sent an odd report by Crucio32000:

"hi bro! no reboot for me so far or any stability issue, but i've noticed that when i have an alarm pending , clock doesn't refresh until i do a manual reboot! It remains stucked at the one when i put the alarms.

Luckily they work as they should do!"

Anyone else with this issue?
[Nexus S Android Development] stojshic:
Again me, maybe this have something to do with my soft-reboots, maybe not... I'll install bbs now and try to track it down..
[Nexus S Android Development] :
I've had this one before. No idea what causes it, but it was solved by rebooting. But I suppose it might be better not to... Install the app first and see what's causing it. Thanks!
[Nexus S Android Development] stojshic:
I was asleep during that period, not using my phone at all. Now I installed BBS, and looking at my phone, every minute my screen turns on for a 5 seconds, then goes back, like I pressed some button. I'll leave it idle for an hour and see if I can track down what's the cause of all this... :/
[Nexus S Android Development] caliban2:
Bedalus, I hope you never take those 411mb of ram away from me. After almost a day the sys still flies as if it just booted!

PS:

I think the rest of the kernel might have something to do with it as well. ^^
[Nexus S Android Development] :
Thanks.

I think CrackerTeg's reboot is either a one off co-incidence, but if other people have similar crashes I'll be forced to remove bigmem again. But if the test version is working for you then keep using it!
[Nexus S Android Development] leap_ahead:
i flash 6.7.10 i like the more ram!!!
[Nexus S Android Development] :
So that's that part out of the way, I see what you were trying to do, and I noticed that mistake with policy->user_policy.max when I cherry-picked the deep idle code last week it was the first thing that jumped out at me. Commit says set min to 800, yet max is being set? The code doesn't match with the message.

I still fail to understand what you did to make the scheduler bug though, and why you thought it was something else which had bugged.

You might call it public humiliation, I call it peer review, which is what open source is about, and let's face it, your git is...somewhat messy. If you don't want people to call your development skills, perhaps stop committing so much junk, because the source and commits is what people look at and review.

If you have ever been on the Linux Kernel Mailing List, you will accept what I said was nothing more than honest advice, public humiliation is done very well on LKML...

---------- Post added at 09:55 PM ---------- Previous post was at 09:54 PM ----------

Lol. /me stays silent. :laugh::laugh::laugh:
[Nexus S Android Development] :
Phew, okay, glad you stuck around. I do need help. Did you see my post on the tail of the comment you made on my admittedly terrible github? https://github.com/bedalus/bedalusKERNEL/commit/b76badeaa6db0f998648b2d40e0138ae1ea228f2

I'm totally with you. I had every intention of squashing those commits to make it readable. But I just forgot and pushed a long list of individual commits. It was pure git noobishness. I gave myself a severe kicking. I was going to ask how I can make my changes into a patch like yours with the spinlocks?
[Nexus S Android Development] :
Right, why not call the code to save and restore the frequency from early_suspend() and late_resume()

That way you can create a function which you can pass a boolean to which will either lock the frequency and change to performance, or unlock it and change the governor back to what it was.

Just a thought.

It seems like a **** idea to do it all inside request_suspend_state(), it makes for messy code. Create a separate function for it and call it from early_suspend and late_resume
[Nexus S Android Development] sperelli:
keys don't turn on, config in signature.
[Nexus S Android Development] Articudos:
http://goo.im/devs/RcrdBrt/crespo/BigMem_NS_ICS.zip

For the highbigmem patch, plz add this in op or include this in kernel zip file.

Just in case..;)

Thanks to rcrdbrt for the links

Kalim for the patch:)
[Nexus S Android Development] noobiekins:
it's already put into this kernel
[Nexus S Android Development] polobunny:
So about Voodoo colors...

Changing gamma settings in Voodoo app won't do anything if it's set under 0. Was that meant to be? Pushing the values forward to 20 for RGB will make the screen darker though (what?!).

I have the feeling I have simply not read some post somewhere, and if so, you have my excuses.

All in all, with gamma values at 20-20-16 and RGB multipliers at 370-370-429 I've reached a satisfactory look, better than what it was. Cheers!
[Nexus S Android Development] :
Blackcrx, you rebooted to recovery after your crash, so this is a CWM recovery kernel log. It wrote over the last_kmsg from my kernel.
[Nexus S Android Development] Blackcrx:
Oops. Sorry. I didn't know it made a difference.
[Nexus S Android Development] :
It looks like Morfic's multipliers have an inverting effect on voodoo. So I've raised all mine to 20, then I've set my rgb to 189-185-214.
[Nexus S Android Development] JokerAce:
Actually, for people like me that don't run any apps during screen-off, I don't have to enable deep-idle right? Does background syncing require deep-idle to save battery?
[Nexus S Android Development] Articudos:
Oh, when I'm using v1.0 right now, and I couldn't see libs in v1.0;)

Anyway, downloading v1.4...
[Nexus S Android Development] Billchen0014:
any chance of this working on 4.1 aosp?
[Nexus S Android Development] apatal:
You can try, but chances are that it won't. Too many mods which are optimized for ICS and might cause problems for JB. :)
[Nexus S Android Development] N@th_OC:
It will not work. Bigmem kernels are not working with JB.

Your phone will bootloop if you used it. With JB run the latest Thalamus kernel.

I'm waiting for a JB kernel of bedalus too!!!
[Nexus S Android Development] doc_v15:
Link for 1.4 doesnt work :(

EDIT: Its working!
[Nexus S Android Development] xjerlzx:
any recommended settings for battery life?
[Nexus S Android Development] :
I would recommend thalamus' kernel right now to be honest. I'm waiting for official proprietary drivers.
[Nexus S Android Development] :
Read my battery thread! Find the research link in the op
[Nexus S Android Development] treesurf:
Yup, flying along smoothly here as well on last test version. Funny that my phone reports 412 ram, not 411. Does the rom affect available memory as well?

Sent from my Nexus S
[Nexus S Android Development] :
Either that or phone model. I'm not sure.
[Nexus S Android Development] xis123:
Will upgrading the kernel version bring about improvements, or do people generally stick with what they prefer the most? I feel like reverting to 4.8.3 :S #firstworldproblems
[Nexus S Android Development] caliban2:
I think it depends on ROM. With CM I always get 1 mb less than others. (403/407/411)

---------- Post added at 11:25 AM ---------- Previous post was at 11:22 AM ----------

But he was running 6.7 - can you really judge all the later versions by that? After all you've been fixing quite a few things since then. (Granted, I'm a bit surprised. 6.7 was always stable for me and still is my fallback-kernel)

Actually, I'm so happy with my current setup I think I'll give it a proper test, see how long it takes to make me reboot. (Okay, a 4.2.-rom might spoil that)
[Nexus S Android Development] _yaz_:
bigmem kangs caused stability problems on my crespo, always, but 6.7.10 is pretty stable so far (still on the test version). thx !
[Nexus S Android Development] stojshic:
Ok, moving on with my problem, before I restart, or install other ROM... After leaving screen of for about 30 mins, suspend_backoff kept my phone from going into deep_idle. 32mins screen off, 32mins awake by suspend_backoff. Any help?
[Nexus S Android Development] alen1901:
No problems like that. Everything works perfect with 6.7.10 so i give myself a push and overclocked it. Stil working like a beast. ;)
[Nexus S Android Development] :
I guess it was a ROM/App issue then!
[Nexus S Android Development] :
Feel free to use that version, but there have been a lot of improvements since then
[Nexus S Android Development] :
It could be co-incidence. But it's a pretty strong one. I'll have to see how we progress with the latest test version. If v6.7.10 shows any last_kmsges like that then bigmem is getting reverted.

I suppose I should set some sort of countdown. I think I'll provide the extra RAM like in the test version you're using for all the CM based users in the next release, and I'll call it v7 to celebrate problems being solved. Lucky 7! :p

I'll wait a few days, or until I can't wait any more (whichever comes first :p) and release v7 so long as no more last_kmsges like CrackerTeg's appear.
[Nexus S Android Development] CrackerTeg:
It may have been coincidence. I adopted the "I'm going to run a version until it crashes and then upgrade method" from here on out. Weird thing is, for the most part while running that version, I was also OC. I didn't have a long uptime as I changed some settings in init.d a couple of times. With that crash, I only had about 8 hours uptime. Flashing latest version as I type this.
[Nexus S Android Development] RunTech:
With v6.7.10 is the version of the kernel 3.0.35 or is 3.0.51???....and also for the MIUI ROM what version i have to download? :)
[Nexus S Android Development] g33kt:
It's 3.0.51 and you should use All other version
[Nexus S Android Development] RunTech:
Thanks :) I asked for MIUI because I listened that it's based on Cyanogen so I asked. Thanks again
[Nexus S Android Development] fear_factory84:
166 hours uptime ;)

rasbeanjelly 11/06 + marmite v6.6 + radio kl1
[Nexus S Android Development] uncle_seuss:
Have you looked at the Samsung automatic color limiter for your kernel yet?
[Nexus S Android Development] polobunny:
So yesterday I was going to update rom + kernel while I rebooted for my 2G glitch.

Did the usual steps but for some reason it would hang at "Android is upgrading... Starting applications". Wiping data/factory reset fixed that.

Kinda annoyed me, but gave me a good reason to wipe everything clean, re-install rom + kernel and then extract my apps from a Nandroid and set up my stuff. Running smooth, can't whine about that.

Now on v6.7.9, we'll see how this one fares! (Can someone say 200 hours test? :p)
[Nexus S Android Development] caliban2:
Dammit. I just HAD to update Gmail + Keyboard-apk from the 4.2-update. Of course that needs a reboot and there goes my uptime-test. Was around 26 hours on 6.7.10-extramem. It was stable, fast, smooth, swift - this is not a bugreport! Just me lamenting about myself. ^^

(Gmail-app was worth it, keyboard seems to be lagging now)
[Nexus S Android Development] :
Any link?
[Nexus S Android Development] caliban2:
a) before you start that test - nightly 1113 has something, was a tick better than 1112 (if your sig is correct; i know both of them)

b) v6.7.9 is a good test-base, but on the other hand it would be very interesting how YOU would be doing with that 6.7.10-extramem cm-kernel...

(1113-nightly should be the same as the stable ones that got released that day, ours just didn't build)

Edit:

nevermind. Euroskank, not CM. d'oh!
[Nexus S Android Development] treesurf:
I'm still going for uptime on the extramem (good name) kernel. Current setup is so good I have no desire to flash anything else.

Sent from my Nexus S
[Nexus S Android Development] caliban2:
It's not like I flashed it, I replaced the apk's manually. But only after a reboot they worked. ^^
[Nexus S Android Development] polobunny:
It's 1112, and 6.7.9 right now. Not absolutely settled on all my stuff anyway, so I might end up updating today.

I don't see why Ezekeel bigmem would cause a problem since it didn't seem to cause any in previous test versions I ran.

Do you know why 13 didn't build? I know center clock kept giving grief but don't know otherwise.

Edit: I see you were talking about official nightlies and not skank builds. I might still make the move, don't need the picks that bad.
[Nexus S Android Development] xis123:
Not to bomb this thread, but I've encountered a weird error now.

Suddenly apps that used to be available and compatible from the Play Store are no longer compatible (Documents To Go 3.0 ) + Swiftkey 3.. this is off a full wipe, flashed Slim Bean 2.9 & marmite 6.710 , no other changes.

Is this a common error? Anyone know any solutions? o_O
[Nexus S Android Development] polobunny:
ROM issue, not kernel.

If you changed DPI or modified build.prop that happens. You'd likely get better help in Slim's thread. =)
[Nexus S Android Development] caliban2:
Yes, I mixed up CM and Eurokang.

About making the move: We're still waiting for a stable build on NS, but a lot of builds were failing in the past 48 hours. Yesterday's nightly should be the same though.

And I was not talking about the "normal" marmite 6.7.10 (407/408 mb), but this one (411mb on CM, 412 on others)
[Nexus S Android Development] xis123:
Fixed it myself, didn't realise I flashed a older version of Slim Gapps >_<" just wiped again.

Thanks anyway polo!!
[Nexus S Android Development] polobunny:
Thanks for the link, will likely update if the stable comes out.