yashsingh1/xdaforums huggingface dataset:
[Nexus S Android Development] atxbang56:
I've never had any problems with your kernel,I know that my Nexus S accept OC only if I raise voltages but with the last versions I don't have to do it, it's stable. This kernel makes Android cool to use with no lags and gaming pretty good even if our phones are now old. Thank you Bedalus. ( to the whiners : stop whining, use your brain and read before posting)

Here is my today battery life running MIUI 2.11.2 by MIUI France : (tapatalk, sms, 1h calling )

Envoyé depuis mon Nexus S avec Tapatalk
[Nexus S Android Development] beppegg:
Oh, I managed it! ;)

I had a reboot while on call and a soft one while using wifi tethering on 6.7.2. I couldn't take last kmsg since I got recalled suddenly :p

Now I flashed 6.7.3, let's how it go!

Inviato dal mio Nexus S con Tapatalk 2
[Nexus S Android Development] polobunny:
But... :p

I give it to you, the nightlies are pretty solid, minus the build that's broken once in a while.
[Nexus S Android Development] g33kt:
I've just flahed 6.7.3 over kwbr's ROM and it doesn't seem to be smooth at all. Should I flash "Stock OTA" or "All other ROM's" version?
[Nexus S Android Development] mdean1981:
Try the All Other. It is gonna be more tweaked then the stock of course.
[Nexus S Android Development] alen1901:
What are you talking about you silly. That doesnt have anything to do with tweaking. Stock OTA kernel version is for roms like it says, stock. All others version is for example for rascarlo/codename, build from aosp sources. And cm version is for cm builds.
[Nexus S Android Development] :
Part of the code that manages the clocks when the CPU frequency changes also forces 800mhz and prevents further changes to the policy until the device wakes up. It's the fastest the CPU can run without requiring a phased locked loop calculation. I think the reason for this is because when the device is asleep, when a timer goes off for an activity the CPU comes back to life to deal with it in the most efficient and quickest way. Race to idle! So the only reason for those sleep/wakeup frequencies is because of that. The governor can't actually influence the CPU frequency during sleep, so I'm just preventing a little code execution by ensuring everything matches. If the device had the screen off, but is awake, playing music or something, the governor is then in charge, and will scale up or down as required.
[Nexus S Android Development] :
You should just be able to use the "restore settings at boot" tick box in nstools. Isn't it working?
[Nexus S Android Development] :
I probably am my own worst enemy. If I could go back and start over, I'd be a lot more restrained.
[Nexus S Android Development] :
You've got some corruption on your flash memory. Backup everything you have to a computer, completely wipe your device, including sdcard and reflash ROM and kernel. Restore only the apps you can't live without. Set up your ROM how you want it, then do a nandroid. Try running the device in a minimal way for a while to see how it behaves.
[Nexus S Android Development] treesurf:
Alarm failure this morning. Opened up one eye and thought "boy, it's getting kind of bright outside!". Grabbed the phone to check the time and as soon as I hit the power button the alarm went off...25 minutes late. Seems like the phone didn't want to wake up even more than me. No harm done, should still make it to work on time...

edit: strawberry, no OC, 9020T, 6.7.3
[Nexus S Android Development] :
It's working fine here. Reboot to recovery and fix permissions? Our check your init.d scripts still exist. You can try nstools if you like.
[Nexus S Android Development] :
How long did you give it to settle?
[Nexus S Android Development] :
Even if the phone reboots, the alarms should still go off. Sounds more like a ROM bug. Maybe you can test the alarms are working normally? Set one for two minutes in the future?
[Nexus S Android Development] treesurf:
It's been waking me up fine every morning using this ROM for several days now. The new kernel is the only recent change. I will accept that it may be a ROM bug and continue to take my chances for the time being. :)

Just did a test alarm and it worked fine. Who knows, the phone may have just needed an extra half hour of sleep this morning. :p
[Nexus S Android Development] :
It hasn't escaped my attention that a some users of my kernel were sticking up for me in another thread, so thanks for that.

I think most of the best developers have a good attitude, in my opinion creativity and arrogance are mutually exclusive traits.

Once again I have to thank the community for the help everyone's provided with the constant feedback. Development wouldn't progress as quickly without it!
[Nexus S Android Development] polobunny:
The alarm not going off thing is weird. The only time I had issues with alarms is back when my phone would freeze over night and stay in a SoD instead if rebooting.

Is it possible, for some reason, the phone is too solicited and the alarm doesn't go off for that? I've had issues where if I'm playing a heavy game sometimes my text notification will not go off but I can see I've received a text in my notification area. Worst case scenario that happens very rarely I don't even get the notification but if I open my sms app I'll see the text there. Just a thought.

---------- Post added at 08:15 PM ---------- Previous post was at 08:13 PM ----------

Oh and don't get offended by my words bedalus. Different ways of thinking, and that's just fine. But I'd rather test something out for real and make sure it's solid before screaming eureka. :)

71 hours, close to the 100 mark woop!
[Nexus S Android Development] caliban2:
Sounds like thalamus showed up again...? Thought that egomaniac was gone, doesn't even own a nexus s anymore. (Btw polobunny, how you can publically agree with that guy on anything, eludes me.)
[Nexus S Android Development] _yaz_:
i always make kernel updates the nerdy way; clean cashes, fix permissions, aso ... (i don't really care about the grumbling of the top gears. it doesn't hurt and makes me sleep better :silly: ) however, yesterday i made a clean install (rom&kernel) and i keep watching ...

anyway, the bln issue i outlined some pages back seems to be persistent. i dropped my note yesterday when i realized that i missed 2 very important msgs. as it's hard to test bln thorough and systematic i just speculate, but it seems as if bln got tired off after awhile and gave up noting me if i didn't react in time (sounds stupid but that's what i experience). sometimes it seems as if the second event killed the note state switched on by the first one (again some mind gaming). would you sentence some time to this issue ?

thx
[Nexus S Android Development] caliban2:
Could just be that you misconfigured BLN, what are your settings?
[Nexus S Android Development] caliban2:
Mmmh, I like that.

In that case sleep_awake @800 would make sense. For sleep_ideal & awake_ideal gov has already taken over. Am I getting this right?

BTW, v6.7.3 is behaving fine here, including alarms. :)
[Nexus S Android Development] :
How do you have it set? No blinking? No timeout? You're not the only one experiencing issues with BLN / BLD. I haven't looked at the code in ages, it's probably due a revisit.

I might go with simplicity and have no blinking and no timeouts.
[Nexus S Android Development] BenHeng:
Huge battery drain with latest version of marmite! I'll try to find out why (exchange has gone crazy but that doesn't seems enough to divide by two battery life). I'll let you know if I can find another culprit.

(On BB6, i9023).

Envoyé depuis mon Nexus S avec Tapatalk
[Nexus S Android Development] polobunny:
While his personality might be difficult for some people to deal with he doesn't speak absolute bull****. He's very tedious and meticulous in his development and I have no problem saying I agree with that method.

As for BLN, I didn't get the BLN dying issue again. Same rom as last time, same init.d, only the kernel I have changed to the test version you sent me bedalus. It used to die sporadically, and now it seems fine.
[Nexus S Android Development] :
Drain seems normal here. Anyone else having an issue with battery life?
[Nexus S Android Development] :
Cool thanks.

Yeah, the governor has no control when the device goes into suspend, until something wakes it up again. There may be levels to it too, I'm not sure, but if the system needs to do something without user interaction, I think the frequency governor stays out of it, but if you get a call or wake the device manually, then the governor steps in once again.
[Nexus S Android Development] CrackerTeg:
I decided to quit stalling and flashed 6.7.3 using your settings bed. This time I'm not over clocking. I'll keep you posted on how this runs.
[Nexus S Android Development] :
I suppose I had been trying to keep him on-side to learn from him, but I guess that's a redundant protocol now, so I'll launch into a little moral story:

I taught kids maths in a school in the worst 1% for deprivation in Britain, and got asked the same questions day in and out, like 'what's six times seven?' Some of my pupils could barely write their own names. But I didn't tell them they were ****ing idiots. Just because people don't have a certain level of knowledge or skill doesn't automatically make them inferior and worthy of abuse. He constantly berated people for spamming his thread, when the worst spam was his endless abuse. What really makes me sick is that when he first started posting in the nexus s section, he had something like 400 thanks, and currently he's on 1647. He's been thanked more than a thousand times for abusing noobs. Unless, uh, people were actually thanking him for IDLE2 (uses more power than it saves, he said he'd not give up on it, then shortly after, he quit).
[Nexus S Android Development] alen1901:
Cant tell right now but it seems i dont have that battery drain. Will report tomorrow if there is some problem. I noticed that android system and OS are 2 lowest things on battery stats. 2 and 3%.
[Nexus S Android Development] ScOULaris:
Just flashed 6.7.3. I'll keep an eye out for battery drain issues and the like, but everything seems fine thus far. :D
[Nexus S Android Development] polobunny:
I understand. As I told you earlier when you started working on your kernel, sometimes you need to do abstraction of these difficulties and see through it and seek for what is good. His work methodology was good, and that's that. He develops like everyone should be developing when doing it professionally, seeking to understand the bugs rather than trying to work around it by reverting changes and crossing your fingers. It's alright to do it for small scale projects on your own, but jokes aside all those stable/beta and so on tags have an actual meaning, no matter what people believe. It's ironic to publish a stable release only to pull it minutes after, if you catch my drift. :p

I'm sure you caught some pupils difficult to deal with in your time, but as you said it yourself, that doesn't mean they were idiots. That works both ways.

I'm not here to defend thalamus, he's old enough to defend himself if needed be, but you have to render unto Caesar the things which are Caesar's, and development he did right and in a logical manner. That's why I'll agree with his work methodology and ethos, but not necessarily with his manners or lack thereof.

Edit: 84 hours woooooo. Might have found my stable fallback kernel version now. =D
[Nexus S Android Development] :
Trial and error certainly hasn't been the most productive way to develop. I understand more now than I did at the start, so I'm happy.

If the reboots have been cured, going forward I'm certainly going to have to adopt a more restrained approach to the releases.
[Nexus S Android Development] polobunny:
And it shows. :)
[Nexus S Android Development] treesurf:
Corrupted screen followed by reboot while placing an app on the home screen. Latest kernel, running latest Strawberry, no OC, 9020t.

Lastkmsg: http://db.tt/JPMZUTIc

Sent from my Nexus S
[Nexus S Android Development] polobunny:
Can someone say PVR explosion? lol

That's a hardcore crash, couldn't write to the hw regs? Although it could be related to the clock speed and the code added to switch it when changing to 1.1GHz. :/
[Nexus S Android Development] gits:
Hi all, i'm on strawberry 19.10 and flashed 6.7.3 a couple days ago.

Got a reboot while whatching a video on youtube.

Maybe it was OC at 1200 at that time.

Hope this kmsg can be useful.

db.tt/loYLDBUy
[Nexus S Android Development] ScOULaris:
n00b Question: So I just went from Marmite 6.7 to 6.7.3 earlier this morning, and I noticed that my on battery time is no longer accurate. It says that I have been on battery for only 3 hours, when I have actually been on battery for over four hours. Is this just a quirk that comes with flashing kernels, and will it go back to accurately reporting the time after a full charge? Or will I need to wipe the battery stats file in order to fix it?

As for battery life, 6.7.3 is great! It seems to be hardly consuming anything when the screen is off.
[Nexus S Android Development] caliban2:
Then tell us, what did he develop that would justify his snotty attitude? I'm expecting a list that rivals ezekeel's. (Wait, thalamus called his mods "crappy code".)

Or are you mixing up "development" and "cooking"? Sadly, the second word never made it to android-xda, everyone is a developer now.
[Nexus S Android Development] polobunny:
Nothing justifies a snotty attitude.

IDLE2, while unsuccessful, was an attempt at bringing something else to the table, rather than simply adding mainline patches like everyone else.

As for ezekeel code, it's not clean code, it's hackish at best, and I'm pretty sure even ezekeel knows that. Doesn't mean it doesn't work, just means it's not the cleanest way of doing it.
[Nexus S Android Development] Ser Gilgoroth:
Running with a full SD wipe now. 6.7.3 on BB6, should anything go awry, I'll post a kmsg.
[Nexus S Android Development] polobunny:
Hopefully it's not something bad happening with those corrupted blocks you had. =)
[Nexus S Android Development] Ser Gilgoroth:
I think the fresh start was a good suggestion. Hopefully it's smooth sailing here on out.
[Nexus S Android Development] caliban2:
That's a short list then. Wait, it's not even a list.

Obviously most of the things have been brought to the table before you owned your nexus s. You seem to have missed everything that happened before ICS. And about judging ezekeel's code - obviously you're just copy/pasting thalamus' rants here. You don't strike me as someone who has the knowledge to read, let alone judge the quality of code.

Neither can I, but I can at least see if something works or not. And I don't need someone like thalamus to make up my mind about something, I prefer to do that myself.

But let's drop this, this has nothing to do with marmite.

PS: Bedalus, you just got some extra love from thalamus in his thread. You naughty boy, you! :p
[Nexus S Android Development] _yaz_:
it is the way i set it; no dim, no blink, no timeout. i use nstools for setting. may it be the reason ?
[Nexus S Android Development] knzo:
The more you know about something the less patience you have to deal with those who don't. This is understandable and happens everywhere and at any field. While I can't condemn impatience (heck, even I, a noob, am impatience to some user's passivity) I also can't condone arrogance. thalamus had a bit of both so it's natural that everyone has mixed feelings towards his person and work as it's not easy to separate them due to the halo effect.

Personally, I really like developers who are strong in the understanding of how it all works (thalamus, morfic, dzo) but I also credit those who are practical and reach their own conclusions through rigorous testing (bedalus) instead of just assuming X is better due to Y and Z reasons. Unfortunately these traits don't usually go together because you won't bother testing other stuff if you are almost positive it won't contribute to your goals.

Either way, I think in the end it's all about results. However, XDA users nowadays are suggestible. The credibility developers project and flashy words counts for half users' perception on how the kernel/ROM performs, you can't really count on them to withdraw their own conclusions. For example, I doubled Strawberry downloads when I started to say it was the best ROM for Nexus S for being designed for it unlike CM, Slim, CNA, etc. This just shows the community's lack of impartial and objective understanding and ultimately it's what drove thalamus out. I have no doubts that if bedalus posted something like: "new version has BFQv5 tuned for flash devices, it's zomgawesome, best performance I have seen so far", there'd be X posts saying "LOL, SO TRUE" and that package would have more download clicks than any other.

As for me I believe the most important thing is respect. As long as users respect the developer, cooker, enthusiast, ... - by not asking questions he has already answered, by not complaining they need X feature for their life to be better, by not assuming it's all a service they're entitled to, by being ungrateful to the time and devotion put in the work - then the developer must also show respect to the users and not deceive them deliberately (I was unjustly burned for this once) or treat them as inferior.
[Nexus S Android Development] caliban2:
I knew you'd respond, would've done it myself. But really? That wall of text?! Forget it, I won't spend time on it.

But please, stop trying to tell bedalus how he should continue his work. With thalamus' way, a lot of features would be missing, which you obviously like too. Or why is it you are here? You'd be running a stock 3.0.32-kernel, with a beefed-up ondemand-gov (running more than 60% at 1000 MHz) and some kernel-warnings fixed. If you like that - his kernel is still up.

And in case you haven't noticed, he didn't just leave the nexus s-forums, he left xda all together. Despite having some tablet as well. What does that tell you? Only idiots in that device's forum too?!

---------- Post added at 07:34 PM ---------- Previous post was at 07:27 PM ----------

Bedalus, obviously we need a new kernel with "something" new, or this thread will go to hell. :D

No, not feature-wanking. But did you have a chance to have a look at pm_fast (at least on cm-kernel)?
[Nexus S Android Development] polobunny:
I'm not telling anybody how to work, but you purposely wrote that post to start a fire, so I replied. If you're not up to a discussion, don't start one. =)

Edit: And your trolling second post just shows your intention. You might aswell rage quit because bedalus asks you to post your setup, if you feel like acting like a child.
[Nexus S Android Development] caliban2:
Takes a troll to know one.

Done yet? I hope so.
[Nexus S Android Development] polobunny:
Or?
[Nexus S Android Development] caliban2:
Could be nstools. Could be really a bug. Let's find out.

Disable nstools (you don't really need it anyway) and add a script to /etc/init.d (how-to in first post)

The how-to contains a lot of stuff, but for BLN standard-config you only need the following. Keep it simple for now, we can add other stuff later (if needed).

#!/system/bin/sh

echo 1 > /sys/class/misc/backlightnotification/enabled
echo 1 > /sys/class/misc/backlightnotification/blink_finalstate
echo 0 > /sys/class/misc/backlightnotification/in_kernel_blink
echo 0 > /sys/class/misc/backlightnotification/max_blink_count

PS:

Great, with polobunny on my ignore-list this page looks like I'm talking to myself. :what:
[Nexus S Android Development] nibla101:
Wait, does the posts disappears when you ignore? Well then I can ignore all you whiners and problems solved. :fingers-crossed:
[Nexus S Android Development] polobunny:
Yes sir, except the quoted. So eventually, you're going to end up seeing the posts any way. Might as well just ignore them without using the feature. :p
[Nexus S Android Development] CrackerTeg:
Holy hell. I don't post or read the thread for a few hours after picking up the last version and this sh!tstorm is what ensues? Where the hell is a mod to clear this up? Bed, I apologize on behalf of what a few others started in here but I appreciate your work.
[Nexus S Android Development] sisterchick:
Bug: 2G/3G toggle

Hi Mr. B -

I believe I caught a bug. Beginning somewhere around version 6.6 and the last week or so of CM Nightlies the ability to set the option of using only 2G networks in CM Nightly stopped working. Meaning I have "Use only 2G networks" checked under mobile network settings and it still connects to 3G/H. It works properly using 5.2 kernel. (The reason I care, of course, is better battery life.)

I tested by doing a fresh install of CM nightly and 6.7 kernel. I was unable to make 2G network stick. I wiped cache and dalvik, reinstalled the nightly and 5.2 kernel and it will stick. It didn't seem to correlate to the version of CM nightly ROM. I was able to "break" a CM nightly previously working with 5.2 kernel by flashing the 6.7 kernel.

Once it is broke, simply wiping cache and dalvik and reinstalling 5.2 won't fix it. I have to reflash a ROM and then the 5.2 kernel. I just verified by trying all this again using today's CM nightly and 6.7 kernel.

Thank you so much for your work and the countless hours you put into it...you really DO need to take a break though.

PS: Sorry I can't be more precise on the versions. I thought it was the nightlies at first. Took me a bit to find the correlation to the kernel. Something must have changed with CM too because I didn't think the 5.2 kernel was supposed to work anymore!

PSS: Turning on Airplane mode doesn't fix the problem either. I tried to clear up the logic by turning off the Use 2G Network only and putting it into airplane mode to turn off the radio, then turning everything back on. That didn't fix it.
[Nexus S Android Development] benoit2600:
Which rom do you use ? with slim rom, I have to activate the "notification light" option (under ASS menu -> interface -> display) to get BLN working.
[Nexus S Android Development] caliban2:
Must be an issue on 9020a then, because it works fine on 9023 (and always has).
[Nexus S Android Development] invd:
Nope, I have a 9023 and 3g/2g-toggle does not work for me either (just with long pressing the toggle)...
[Nexus S Android Development] caliban2:
Interesting. I tried toggle and via settings before I replied - switches just fine, like it should.
[Nexus S Android Development] :
As polobunny says, it's the pvr bug. Sometimes the graphics chip driver breaks down. Hopefully new drivers will be released at some point
[Nexus S Android Development] :
hmm. I really need to do something about that code. How long normally before it starts acting up?
[Nexus S Android Development] :
That's a good bug report. Can anyone else confirm?
[Nexus S Android Development] :
Aha, multiple apps setting the sysfs interface variable.
[Nexus S Android Development] :
hmm... Anyone else getting or not getting this issue?
[Nexus S Android Development] treesurf:
Same alarm fail this morning. It seems to be only me that's having this issue which is odd. I may try going back to 6.2.1 and see if that fixes it, just to be sure it is a kernel issue.

Thanks for identifying that PVR crash. I didn't know about that bug. I'm getting edumacated!
[Nexus S Android Development] stojshic:
I'm on latest rasbean + 6.7.3, clean-flashed this morning, and my 2G/3G switch works as it should... 9023 model
[Nexus S Android Development] Ser Gilgoroth:
Another reboot, during texting. Not sure what I'm looking at, but I think this kmsg is bad. Haha.
[Nexus S Android Development] :
More flash errors. I think you may need to try formatting again. Did you quick format? The flash should be able to keep track of the bad blocks and skip them, but you may need to do a complete format. Anyone with experience care to weigh in on this?
[Nexus S Android Development] Ser Gilgoroth:
I used the format sdcard in cwm recovery. I only ran it once however.

Edit: I'll be in the bush from early Sunday until Monday eve in all likelihood.
[Nexus S Android Development] alen1901:
I might notice that blx is not working(set with init.d script, others are working). Ill see after one more charge.