yashsingh1/xdaforums huggingface dataset:
[Nexus S Android Development] :
I will upgrade my phone when this one dies, not before! :D I love my nexus s!

v7.1.6 has the most modifications. v7.1.7 has some code removed (dubious backported code from the 3.4 kernel which aimed to prevent soft reboots, but may have been unnecessary) so might be a safer choice. It won't become unstable as your uptime increases. Where did you get that idea?

v7.2 has memory given back to the camera module so it will work properly on all ROMs. Some people don't need that, and will prefer v7.1.7 or v7.1.6. For most users I would recommend v7.2, but I believe v7.1.7 will work fine on Slim Bean and Cyanogenmod at least.
[Nexus S Android Development] caliban2:
7.1.7 indeed shows the old snappiness. :) Can't complain about anything and I'm sure it will be as stable as all versions during the past two months. For the record: 410mb on CM10.
[Nexus S Android Development] :
Cool. That's reassuring.

I've been looking at a lot of 3.4 kernel code, and seeing how the developers for other devices have worked it, and I think it should be possible to build a 3.4 kernel from scratch and just work in what little samsung code is necessary to get the thing working. Whether I personally have the talent to achieve this is another matter entirely. But I think I need something to chew on, because I've plateaued on this one.
[Nexus S Android Development] alen1901:
It would be great to see 3.4 kernel for our phone. I think that kernel has better performance and multitasking abillity, but not battery friendly. thats where you show up. :D also there is 3.4 kernel port for galaxy 3, old Samsung phone, good one. Maybe it can help you? Ill edit post with a link.

EDIT: here you go. See if you can find something usefull here.

http://xdaforums.com/showthread.php?t=1644204

Sent from SpeedMachine i9023
[Nexus S Android Development] capoooro:
Me too.
[Nexus S Android Development] :
Ugh. Raised my brightness up to full and the screen suddenly went very dark. I had to reboot. Anyone else has this?
[Nexus S Android Development] BenHeng:
Yes. I guess your on a 4.2 ROM ?

I have it since I updated to 4.2 and created a script to restore brightness via SManager and put the shortcut in on of the top corner of the home screen (maybe it could be linked to a gesture, didn't thought about it before).

However, the script is

#!/system/bin/sh

echo 250 > /sys/class/backlight/s5p_bl/brightness

You can replicate the effect by changing the value on your computer via Airdroid but it's not the easiest way I found, and you will not be able to lock the phone before rebooting (don't ask me why, it doesn't work, that's all).

The bug is setting the brightness to 0, which is not very dim, but completely dark (I guess it's what our phone looks like when the screen is off and the phone not locked, but that's only a supposition). I occurs at random time when the brightness is changing (i.e. really often with auto-brightness on).

I'm not sure you're having the same issue as me, but I seems similar.

PS: if someone knows how to trigger a scipt when a certain event is occuring (it would be the brightness going to 0), the perfect workaround might be found!
[Nexus S Android Development] lowtje:
Not here
[Nexus S Android Development] :
Yes, I'm testing an early build of Slim Bean for my good friend tchaari, who is working on the 4.2 based version.

I wouldn't worry about the script. It sounds like a simple bug that will easily be fixed.
[Nexus S Android Development] gfinockio:
Am I crazy, or did screen rotation stop working for anyone who flashed the latest version?
[Nexus S Android Development] :
It's working for me.
[Nexus S Android Development] n2d551:
Have I become kernel stupid? I must be doing something wrong. I usually run a kernel cleaning script and still wipe cache & dalvik when flashing a new kernel. I don't when flashing from one marmite vers. to another, because I believe that bedalus said it wasn't necessary. However still do this going from different kernel to kernel. But lately when I've already set up a rom & later decide to flash a new one, all I get are boot loops at the Google logo unless I have flashed the rom then the kernel. Any 4.2.1 this happens?
[Nexus S Android Development] :
When you flash a ROM you need to wipe the dalvic cache
[Nexus S Android Development] n2d551:
When I flash a rom, I wipe everything. Later, I might switch kernels...and this happens. Like today. I switched from matrix to try the new 7.2 and bootloops
[Nexus S Android Development] :
Can you add zRam?
[Nexus S Android Development] :
It's not a good thing!
[Nexus S Android Development] :
Yeah, I think if you're coming from another kernel, format your system, reinstall your ROM, then flash the kernel, then wipe caches.
[Nexus S Android Development] bravo04:
sorry bedalus, i dont get it with what you mean by reinstall your kernel. do you mean it has to flash the room again?
[Nexus S Android Development] towelboy:
On 7.1.7cm, i9020t, no oc.

Had to pull battery cause screen froze but capacitive lights can still turn on and off while heavy multitasking; pandora music playing, switching between notepad, instagram, Facebook and flip board (if that helps)
[Nexus S Android Development] Drizzzle01:
On CM nightly 12/09, marm7.1.7, smartassV2, no oc, no GPS lock. Tried reflash, GPS reset and download from GPS status to no avail. Flashing 7.2 now...

Edit: Scratch that loaded marm7.2, CM stable (11-15 or so), stock settings, no GPS issues so far.
[Nexus S Android Development] killswitch70:
v7.2

Cannot access the play store. It just pops up briefly, then reverts back to previous task.

Edit: Apparently using the wrong wiping method. Got everything working now. Again thumbs up for bedalus. Thanks! =)
[Nexus S Android Development] Sugadadee:
v7.2, with CM10 stable seems all good. No GPS issue, No play store issues, no brightness issues, no reboots.
[Nexus S Android Development] bravo04:
how is the correct wiping method?
[Nexus S Android Development] sidnoit22:
v7.2 have less memory than 7.1.6?
[Nexus S Android Development] csdibiase@gmail.com:
So my modem instability is still happening in 7.2 with CM10 stable. What diagnostics can I grab to help? I have a bit of time today and I might be able to continue testing (though my Nexus 4 is set to deliver today)

since the phone isn't rebooting anymore, last_kmsg doesn't seem to have anything of value.

From a behavior standpoint, at least today, rather than a complete drop of signal it's more that the cell signal status goes grey (meaning it's dropped its connections to google), and incoming calls drop to voicemail rather than ringing the handset. For a test I have pandora running since that only intermittently connects to stream music so I can hear when a disruption has occurred. The only one I was able to catch in logcat this morning had nothing of interest pointing at the radio, but did include a multitude of DNS related errors, which I would expect if the connection had droped.

Now while I usually don't have problems with my cell phone in the office, and my iPhone appears to be working fine, I won't completely rule out that AT&T is at least part of the problem.

Again, tell me what you want me to capture or try. I'll have some flexibility since the Nexus is my "personal" phone and I have it's replacement on the way.
[Nexus S Android Development] polobunny:
Yes.
[Nexus S Android Development] hiphopboy:
7.2 with problem when i'm using it on 4.1.2
[Nexus S Android Development] klinker:
Here Rasbeanjelly 4.2.1 with marmite 7.2 CM and all is ok for now. Freq are 400/1096mhz & performance governor...the rom is like on butter :D

Don't know why the phone take boot like 5 and more min, with non CM version of the kernel.
[Nexus S Android Development] seriosbrad:
Man, I don't know what it was about the Trinity kernel but my Nexus S was incredibly slow and consistently locking up and overheating. Chrome was the main culprit in slowing it down to a crawl, often freezing on a black screen for 2 minutes. I thought it was just my phone reaching it's age, but then I installed Marmite out of boredom and it's like night and day, all slow symptoms GONE. Chrome is fast again. :silly:
[Nexus S Android Development] skinner12:
Yes, me too.. But I think you can't compare 1 still active and develop kernel and 1 that is not upgraded from month..

My ns is another phone now with this kernel. Great work!

Nocerino's rulez..
[Nexus S Android Development] homerograco:
Marmite give much more available memory, which is visible when using heavy apps like Chrome or Photosphere (with ROMs that support it).
[Nexus S Android Development] :
Hi guys, I'm going to be busy for the next few days. Try to help out with anything any new users ask if you can, thanks! :D
[Nexus S Android Development] polobunny:
What's wrong?
[Nexus S Android Development] bravo04:
anyone knows how's the wipe method for this kernel?

I wiped cache and dalvik. at first it's looks normal, until then I got reboot and bootloop with CM 10 stable.

please help me.
[Nexus S Android Development] alen1901:
Flash cm version. And dont oc.

Sent from SpeedMachine i9023
[Nexus S Android Development] hiphopboy:
not any wifi connection :D
[Nexus S Android Development] rip_noob:
Had another reboot while upgrading an app from the play store.

Nexus S i9023, CM10, marmite 7.1.7 no OC, no scripts, im just enabling bln from nstools

last_kmsg http://www.mediafire.com/view/?noqmc1hbva7pl70
[Nexus S Android Development] bravo04:
ya.. i flash cm version and no oc. but still. :(
[Nexus S Android Development] polobunny:
Update to 7.2. The additional ram might be giving some troubles.

---------- Post added at 08:51 PM ---------- Previous post was at 08:50 PM ----------

Fix permissions in CWM
[Nexus S Android Development] hiphopboy:
lolz ! i installed new ROM and wipe all & fix permission always i did
[Nexus S Android Development] killswitch70:
Wiping from earlier kernel version

[If using an earlier kernel version] Wipe dalvik cache, then wipe cache, then install latest kernel. Reboot.
[Nexus S Android Development] alen1901:
You dont have to wipe.

Sent from SpeedMachine i9023
[Nexus S Android Development] 4tticuz:
Just a question for my understanding:

Why is the screen on first boot after chaning kernel black for a while?

Thanks alot!
[Nexus S Android Development] gunner49:
Free RAM

Is there a setting to enable the Free RAM with this Kernel? from NS Tools or Rom control?

I'm still looking at the same amount before I flashed 7.2. Currently running BB6 rom. Thanks.
[Nexus S Android Development] Basche:
There's no option like that, it should automatically have free ram, it may be your ROM doesn't support the free ram. Also try 7.1.7 or whatever version is out right now

You have just been beamed
[Nexus S Android Development] polobunny:
Are you sure it's not a ROM issue? Nobody has reported any problem with wifi in eons.

Doesn't seem to happen to me, but are you wiping in between kernel swaps, or are you updating your rom? If yes, it's possible it's simply the part where the cache is rebuilding, right after the rom bootanimation (not the Google one, the one after).

Which version did you use before? 7.2 has LESS free RAM than 7.1.6. That's to possibly root out people having issue with the RAM being taken from something else. It's possible, more or less concidentially, that 7.2 has the same amount of RAM as the last kernel version you tried. ;)
[Nexus S Android Development] Nemesis2k9:
I agree. This option always causes a huge amount of stuttering to the point that the device becomes unusable.
[Nexus S Android Development] polobunny:
Compcache can be "useful" but I believe it's mostly convenient for devices with even less RAM than that. On our Nexus S it would only mean more multitasking possiblities at the expense of processing power, thus bigger battery drain and losing a bit of snapiness.

Don't think it's necessary or even interesting for us.
[Nexus S Android Development] jiro-kun:
Wow.. Polobunny.. You are on a roll.. Answering ppl's questions.. You have my respect! Thumbs up! :thumbup:
[Nexus S Android Development] polobunny:
Slow days at work. ;)
[Nexus S Android Development] gunner49:
Thanks mate, looks I'll have to try out a previous version then

I don't know exactly which version it was. It was the stock one that came with BB6, I think the "Kernel version" in "About Phone" settings said 3.0.48-bedalus. Thanks.
[Nexus S Android Development] Drizzzle01:
@Bedalus

Two separate reboots per your request this is as much information I can gather.

a) were over-clocking - Was not overclocked

b) didn't report their ROM CM10 Stable (11-15)

c) didn't report their device NS4g

d) didn't report the kernel version 7.2

e) didn't supply a last_kmsg OR attached zip

I was at the GYM listening to music from Play Music. I had swiped to kill frequent apps including Tapatalk v2.xxx, Facebook, Fantasy Yahoo Football, and another App I can't recall maybe 10 minute before because of sluggish skipping on a song. It was like listening to a scratched CD from the mid 90's.

I hope all of this is useful. Please let me know if you require anything else.
[Nexus S Android Development] Drizzzle01:
Here is the other instance of a reboot from a couple days ago. I would have had it sooner, but Tapatalk does not allow for uploads of files.

a) were over-clocking. Was not overclocked.

b) didn't report their ROM CM nightly from 12/9

c) didn't report their device NS4g

d) didn't report the kernel version. I think it was 7.1.7

e) didn't supply a last_kmsg OR (attached)

This was from a fresh boot only thing I was doing was attempting to get GPS to work (It appears that I had heavy cloud coverage). I was inside GPS Status and downloading GPS data and resetting it at the same time. I might have launched Google Maps as well, not to certain.

Please let me know if you need anything else.
[Nexus S Android Development] Krayvon:
!

noticing RR with slimbean 3.1, anyone else getting better performance on a different rom?
[Nexus S Android Development] skinner12:
Tried both version..

7.1.7 give me 411 mb of ram..

7.2 give me 406mb of ram..

Nocerino's rulez..
[Nexus S Android Development] Nemesis2k9:
The only thing I miss when using this kernel is Gama controls. And I miss it a lot. I guess this is the price of performance. I mist say this kernel has pumped new life into my device. :D love it. Keep up the awesome work!
[Nexus S Android Development] polobunny:
Gamma control was added back by bedalus not too long ago, you know. :|

---------- Post added at 03:36 PM ---------- Previous post was at 03:32 PM ----------

That's a good one. Definitely a kernel panic.

binder: 683:683 transaction failed 29189, size 88-0
Unable to handle kernel NULL pointer dereference at virtual address 00000005
pgd = d3500000
[00000005] *pgd=00000000
Internal error: Oops: 5 [#1] PREEMPT
Modules linked in:
CPU: 0 Not tainted (3.0.55-bedalus-03503-g035beb6-dirty #641)
PC is at schedule+0x3c/0x70
LR is at do_nanosleep+0xa4/0xe4
pc : [<c057edcc>] lr : [<c057fe6c>] psr: 20000013
sp : d0bddec0 ip : d0bdded0 fp : d0bddecc
r10: d0bdc000 r9 : 00000001 r8 : d0bddf20
r7 : 00000000 r6 : 77359400 r5 : 00000000 r4 : 0000c350
r3 : d0a56900 r2 : 00000001 r1 : 00000003 r0 : 00000001
Flags: nzCv IRQs on FIQs on Mode SVC_32 ISA ARM Segment user
Control: 10c5387d Table: 43500019 DAC: 00000015

Then follow the dump heh!
[Nexus S Android Development] Nemesis2k9:
Yea but it's crippled. Can't go below 0 without getting the nasty green flash. Or am I late to the party!?
[Nexus S Android Development] polobunny:
I think you misunderstood me when we had this dicussion earlier this week. Or maybe I missed one of your posts.

If I'm not mistaken, 0 on Marmite is already equal to something lower than the usual 0, hence why even at 0 the colors are decent/vibrant. That's why the green flash comes earlier, because there's an offset compared to normal Voodoo

If you take a kernel with Voodoo and set it to 0 for the gamma, and you take Marmite and set it to 0 for the gamma, and make sure multipliers are identical, Marmite will be quite darker.

Feel free to correct me if I'm wrong though. :)
[Nexus S Android Development] kalinusa:
I am truly happy with the Kernel. I am on 7.1.7 with the Rascarlo jelly bean from 11.06 last version.

The only thing is that the MTP patch stop working from time to time and I have to reboot the phone to get it back. It would be working then I will take the phone to do something with it and next time when I plug it into the USB I do not get USB connection, only charging.

Anybody else?
[Nexus S Android Development] temo2k:
After using slim bean for a few weeks (using only clean upgrades) I switched to jelly shot and haven't had a single reboot or performance issue in the following week or two (even using dirty upgrades). i don't know if it's something inherent to 4.2, but I can run overclocked, experimental kernels and it's just as reliable as stock.
[Nexus S Android Development] anshumandash:
Are you overclocking? I am on pacman ROM and its a heavy and sluggish ROM. But I have no issues with 7.1.6 @1096. It feels quite smooth with this version of marmite.
[Nexus S Android Development] polobunny:
Note to bedalus: phone uptime currently 102 hours and no sign of instability. Gotta agree with you soft reboots seem banished. :cool:
[Nexus S Android Development] garethb:
I'm getting that same green flash as well as a strong green hue over the screen. I'm using nightsky's 7500K colour schemes. Any pointers on how I can tweak this?

Only started getting the problem after flashing 7.2

for reference nightsky's post can be found here: http://xdaforums.com/showpost.php?p=32004184&postcount=3097
[Nexus S Android Development] benoit2600:
Try Android 4.2, No more green flash, even with the darkest gamma settings ! :)
[Nexus S Android Development] gunner49:
Is anyone using this kernel with BB6 Rom? I'd appreciate your experience. Thanks
[Nexus S Android Development] polobunny:
Are you still having questions regarding the total ram available?
[Nexus S Android Development] gunner49:
Thanks for your reply. Yes and a couple of other weird things that never happened before.

1. Light Flow lite application was using too much battery, it was on top of the list every time - I have since uninstalled, but I didn't have this

problem with an earlier version of this kernel which came with BB6. Don't know exactly what version it was but I remember that it was listed as

3.0.48-bedalus in the "About Phone" settings.

2. After uninstalling Light Flow , I rebooted and the battery went down from 60% to 10% after the reboot. I went into recovery and wiped battery

stats, cache and dalvik, rebooted and placed the phone on charge.

3. I checked the phone from time to time to see that it was charging normally. At one point the phone was completely dead with the charger still connected. It would not wake up and not even power up. So I removed the battery, put it back in and it powered up normally. I think it was still at 92-93% at that point. Glad its a Nexus with removable battery otherwise I wouldn't have known what to do if it were a Nexus 4 which I'm thinking of getting!

I'm starting to think that the phone does not 'like' this kernel, so my options are to go for an earlier version like 7.1.7 or change to some other kernel altogether. I'm aware that it could also be something to do with the Rom as well, but these things didn't happen with the previous kernel like I explained. I've posted for help in the Rom thread as well regarding the free RAM.

Sorry for writing long but I wanted to give complete details instead of replying with my queries in multiple posts! Thanks again.
[Nexus S Android Development] r_tarandus:
If I'm not mistaken, it looks like you have to wipe everything then reflash your ROM before flashing this kernel (version 7.2)? That's a bit more work than usual, why is it necessary?
[Nexus S Android Development] leap_ahead:
try to record video with 7.1.7 anmd tell me if you get fc on gallery after you stop recding ....
[Nexus S Android Development] polobunny:
Battery stats aren't really related to the kernel though*, the fact it jumped from 60% to 10% on a reboot, plus an app going rogue makes me think you're having other issues than the kernel. You can simply reflash the rom, same version, on top of your current install to re-install the kernel.

It's possible though that Light flow might be interfering with backlight notifications for some reason or another. Is there any specific reason you're using it?

Try to track your battery usage with BetterBatteryStats (free for XDA members), and don't worry more info is better than less!
[Nexus S Android Development] gunner49:
Thanks again for your reply. Yes, that's one thing I didn't do when updating the kernel - not reflashing the rom - but since the older kernel was also marmite, I thought that I didn't need to do the rom as well! I'm giving it another try reflashing everything and see what happens. In the meantime I've had a reboot during a phone call!

I used Light Flow because I like the option to have it repeat the notification sounds after x amount of time for missed calls/sms and also the notification when the battery has been fully charged. :) But I have uninstalled it now since I noticed that heavy battery usage. Thx.
[Nexus S Android Development] polobunny:
You don't usually need to reflash the rom before upgrading the kernel but I know at some point bedalus asked us to do that because he changed the way the ramdisk was handled.

I mostly meant reflashing the rom so you would go back to the kernel you previously ran though, and thus could see if you had any issues, even when going back to this kernel. If you do, then it wouldn't seem like it's kernel related. :)
[Nexus S Android Development] gunner49:
That's what I thought as well. No I don't remember having any of these problems with the other kernel. I had light flow working without the issues of the heavy drain of battery. I'll give it another chance by reflashing everything though and see what happens. Thx again.

Update: Reflashed everything and the system seems to be more stable and smoother as well. I did leave a couple of apps out though like avast, android assistant and light flow. Been playing with it for a day now and had only just the one reboot and the email app closing which must be rom related I guess. Thanks for the help.
[Nexus S Android Development] :
Hello, I'm still short on time. Looks like for the most part everyone is happy. Problems with gamma control are not something I can fix, apart from removing it completely.

The last_kmsg posted looks quite unusual, so I'll investigate that when I've got more time. I suspect it was probably a random one off.
[Nexus S Android Development] :
Oh, and a personal thanks to polobunny for fielding loads of questions! Please carry on helping each other. It's so good when everyone lends a hand :)
[Nexus S Android Development] Zahih:
Nope, no FC on gallery after I record video.

I'm on rasbeanjelly 8 Dec with 7.1.7 marmite.
[Nexus S Android Development] ziociccio:
hi bedalus...

version 7.2 works with rom jb 4.2.x?
[Nexus S Android Development] Sucky1983:
Yes, for jellyshot 0.5.2 the marmite kernel works great. Its a 4.2.1 Rom
[Nexus S Android Development] ziociccio:
thanks

i use tsm jb 4.2.1 rom based on source code jop40d : which version of kernel i must download?
[Nexus S Android Development] joeyddr:
same here i use rasbean 12/10 and 7.1.7 works fine, i prefer it for the extra mem.
[Nexus S Android Development] sperelli:
Already reported quite same issue same weeks ago. Change of baseband didn't help.

---------- Post added at 06:46 PM ---------- Previous post was at 06:40 PM ----------

Bedalus, i keep on experiencing serious difficulties for charging till 100%. Blx is on and set to 100% but it still charges to 98%. Seldom it reaches 100. Why??
[Nexus S Android Development] leap_ahead:
I mean on rascarlo 4.1.2 rom i get fc on gallery with 7.1.7...

Also 98% blx...i must disconect and reconect again
[Nexus S Android Development] :
I'm busy trying to get the 3.4 kernel working! I will check on BLX again soon.