yashsingh1/xdaforums huggingface dataset:
[Nexus S Android Development] polobunny:
Blinking will switch between 100Mhz then deep sleep and back to 100Mhz and so forth. Consumes more power than lit up even if the total lit up time is similar because of wakelocks.
[Nexus S Android Development] fear_factory84:
I'm on rasbeanjelly 11/06 + marmite v6.6, no oc and no brainmaster tweaks, 120hours uptime and counting, no reboots and problems for me.

Previously on rasbeanjelly 10/16 + brainmaster tweaks and the same marmite v6.6 kernel it was very unstable (soft reboots, application hangs like on phone app and contacts).

I think I'll keep this combination for a while!
[Nexus S Android Development] sisterchick:
2G/3G works!

Yeah...the 2G/3G toggle weirdness went away with 6.7.9! (It was still broke with 6.7.7.) Thank you, Mr B!
[Nexus S Android Development] migueldbr:
Brainmaster tweaks also brought instability to my phone. It has been great since i removed them
[Nexus S Android Development] fear_factory84:
2g/3g switch is fine on my phone with marmite v6.6. What was your problem?
[Nexus S Android Development] sisterchick:
Long story short, it didn't work with CM10 nightly. Meaning, 2G only was checked but connecting to 3G/H no matter what. In the metal building where I work, 2G signal is much stronger; 3G is weak and runs down the battery. I have WiFi. It started somewhere around 6.5 kernel. Tried it again yesterday with 6.7.7 with the 11-09 CM10 I had installed and it was still broke. Same ROM and 6.7.9 kernel and I'm back in business! I am a happy girl!
[Nexus S Android Development] jojoost:
Thanks Bedalus!!
[Nexus S Android Development] alen1901:
can you send me PM with a name of that theme you are using? tnx. :)
[Nexus S Android Development] BenHeng:
I'm on 6.7.9 and have a little battery drain from the system: 144 wakeup.

9% of drain from power manager service and 8% from modem_IP. I had slightly better battery life with previous version ;)

Everything else is perfect. :eek:

Envoyé depuis mon Nexus S avec Tapatalk
[Nexus S Android Development] waterface:
HELP! Off-topic, but please read

Pulled battery, now phone is dead. UnBrickable Resurrector won't detect it.

bedalus, do I remember wrong or something like this happened to you (or someone writing in your thread) while you were doing all of your benchmarks a few months ago?

I know this is off topic. But please, any help is appreciated. Thnks in advance everyone.
[Nexus S Android Development] gabling23:
which kernel should i use with blackbean rom?
[Nexus S Android Development] sisterchick:
Define "dead"? What happens when you try to power up? What was going on when you pulled the battery?
[Nexus S Android Development] waterface:
Pulled battery during boot. Done that before, I think I may just have done that too soon this time.

Nothing whatsoever happens if I try to power up...
[Nexus S Android Development] alen1901:
What if you plug in charger, does screen lights up?
[Nexus S Android Development] waterface:
Nothing. Stuck, still like a brick.

Thanks for your answers, I know this is off topic..
[Nexus S Android Development] nexususer1:
Did the same thing. Pulled the battery on bootloader. Result = fried motherboard. I sent it on warranty and they fixed it within 10 days without having to pay a single. Stay cool providing you have a warranty :)
[Nexus S Android Development] waterface:
I don't, I'm afraid. Phone bought used, comes from the States, I'm in Italy.

Fried motherboard you say? No hope with JTag?....
[Nexus S Android Development] towelboy:
I had two freezes where I quickly scrolled through my instagram follower list. I had to pull battery so I couldn't get last_kmsg. v6.7.8, Smartassv2, no oc.
[Nexus S Android Development] jojoost:
Had exactly the same last month
[Nexus S Android Development] micha3lvd:
I'm having some issues with my BLN.. it wont turn on :S tryed using the BLN control pro app (from neldar) and nstools.. both say the BLN is on but when i get a notification they wont turn on.. (did work on previous versions)

Using slim 2.9 with 6.7.9CM

Rest of the kernel is superb =D
[Nexus S Android Development] ScOULaris:
For one thing, why are you using the CM version of Marmite for a Slim ROM? Try switching over to the vanilla 6.7.9.
[Nexus S Android Development] :
Yeah it was in June. It hasn't surfaced because I reverted the entire set. Now I've merged the entire set back in, apart from the offending bit of code (i hope)
[Nexus S Android Development] :
Same thing happened to thalamus. He had to send it off for repair
[Nexus S Android Development] :
Slim requires the cm kernel or you'll have no display.
[Nexus S Android Development] :
Anyone else having trouble with bln?
[Nexus S Android Development] jimdem:
No problem here. 6.7.9 with aokp m1. Though I'm not using an app for bln control, I use my own init.d script. Your kernel rocks. Literally I've forgotten the reboots haha ;)

Στάλθηκε από το Nexus S μου χρησιμοποιώντας Tapatalk 2
[Nexus S Android Development] treesurf:
No problems with BLN here. Using the BLN control app. Really nice kernel here bedalus, thanks!

Using 6.7.8, on Strawberry.
[Nexus S Android Development] :
Just had reboot to boot animation while using twitter. No last_kmsg. I'm on v6.7.9

Any other v6.7.9 user get anything like this?
[Nexus S Android Development] waterface:
So it was him. I thought I remembered someone talking about it. You don't happen to remember where he talked about it? Just wanted to take a look back onto what happened, as you say it seems very similar to what just happened to me..
[Nexus S Android Development] stojshic:
I'm on 6.7.8 and latest rasbean, and I noticed two soft reboots while using fb messanger (I thing first time was also fb messanger, but can't remember, but second time it was it). Is it even related to kernel, and, is it worth copying last_kmsg after soft reboot, or it's unusable?
[Nexus S Android Development] :
It's in his thread in general. You might try a search by username _thalamus and keyword battery.

He was doing some battery drain measurements at the same time, but essentially just pulled the battery. I think he saw a spark too.
[Nexus S Android Development] :
I'm not sure if soft reboots are related to the kernel, but you can certainly try and get a last_kmsg for me.
[Nexus S Android Development] stojshic:
Kk, here's log, hope it helps:

http://db.tt/OYMBzLFX
[Nexus S Android Development] capoooro:
I had a total freeze navigating with chrome. I had to pull the battery. No lastkmsg. Going back to the smoother I've used the last three de days 6.7.3. :)
[Nexus S Android Development] qu3becker:
My Nexus S was stolen today. So I had to buy a new phone. Got myself a Samsung Galaxy S II X (Would have waited for the Nexus 4 but I can't, unfortunately). I have to thanks Bedalus who made the Nexus S experience a great one and will probably do so for quite a time more for others.

I won't repeat what everyone is saying about him but I'm he is a part of what is great of this community.

Thanks a lot. I will miss you. Otherwise, I'll see you all in the nexus7 forum and GS II X.
[Nexus S Android Development] polobunny:
That sucks about your phone pal. My friend got a SII X from koodo. I got to play with it, it's not too shabby. I like the bigger screen, even though I used to tell myself the one on the nexus was good enough haha. Definitely snappier experience than with the Nexus, after all its one year younger or so.
[Nexus S Android Development] Accidd:
Got freeze on Tweetcaster and reboot on Tapatalk. It started since 6.7.7 I think. Rasbeanjelly, no oc. SmartassV2.

Sent from my MIUI Nexus S Jelly Bean.
[Nexus S Android Development] qu3becker:
Yeh, I'm with Koodo too. It's definitely snappier, even in battery saving mode. I'm running stock for now. I will probably put AOKP or CM in a near future. I'll check if the battery life is better than the NS, I hope so. The screen is big but 4 inches is the maximum size for WVGA resolution, otherwise it doesn't look as sharp but beggars can't be choosers.

Actually, I'll probably go back to stock touchwiz when the 4.1 update will roll in just to see if I like it. I'll miss my Nexus for the updates but at least Samsung do a good job if we compare them to other manufacturers.

Anyway, enough off topic. I'll probably stray around this thread for a while, I feel like home even though I didn't post more and most of the time, I didn't have time to answer questions asking for help.

Good night.
[Nexus S Android Development] caliban2:
He was attempting some battdrain-tests alright. That included some wires, with which he short-circuited his batt/mainboard -> spark -> not good.

Alarm went off fine this morning, no fc like yesterday.

Uptime 19:30h and counting. Guess I'll update to today's nightly soon though. Threw everything at it I could think of - wouldn't crash. :) But there's one thing I don't like: when waking it up from standby, it doesn't react right away. Takes about half a second for backlight to come on, followed by the keys and then the screen comes on. Doesn't sound dramatic and it isn't. But in the past this was always an indicator that something is wrong, which might end in a SoD or crash eventually. But could be a rom-issue as well. I just hope despite upgrading my ROM later, I'll have another day to test 6.7.9. (Maybe the new nightly helps)
[Nexus S Android Development] :
Thanks, unfortunately this is a recovery log
[Nexus S Android Development] :
Cheers! Thanks for your support and the nice farewell. Enjoy your new device!
[Nexus S Android Development] :
I have a short delay before my screen comes on, but it's a ROM feature in my case: the screen illuminates gradually.

Is anyone else noticing a half second delay before the device reacts?
[Nexus S Android Development] BenHeng:
I am. :rolleyes:

Envoyé depuis mon Nexus S avec Tapatalk
[Nexus S Android Development] :
Do you think it's a ROM thing? Or is it the kernel?
[Nexus S Android Development] caliban2:
It isn't that. I could enable that feature too, but I don't like it.

It's like I said, it looks like coming out of standby takes some effort.

I'm taking a longer coffee break, flashing today's nightly. Gives me the chance to test it out: nightly plus 6.7.9, if it's still there -> 6.7 (I know it was okay back then). If it's still slow, it's a ROM thing.

PS:

Uptime for 6.7.9: 21:30h. Looks good to me since I think I threw some rather heavy stuff at it (gaming, torrent-dl, browsing, 3 photospheres - never mind normal use)

PPS:

Never mind. http://xdaforums.com/showthread.php?p=34049143
[Nexus S Android Development] BenHeng:
As soon as I have time I'll download a few other kernel and test them to see if it disappear, but I have a huge lot of work so maybe it won't be done before a day or two

Édit : indeed, it happened yesterday, not today : it might be that 6.7.9 fixed the bug
[Nexus S Android Development] caliban2:
ROM-update, 6.7.9 -> comes out of standby smooth and fast. False alarm. :o
[Nexus S Android Development] :
Cool. I think we're on to a winner here. (I only say that because I enjoy jinxing myself :p)
[Nexus S Android Development] anshumandash:
I am seeing that on bb6. I didn't have it on some previous versions. I didn't enable such a feature in the ROM. Currently running 6.7.9.

Sent from my Nexus S
[Nexus S Android Development] caliban2:
Didn't YOU report a crash to bootanim? :rolleyes:

BTW, seeing that it happens on other ROMs as well, I have another idea what might be causing it: mem-management. So let's wait if I get it again over the next few hours.
[Nexus S Android Development] :
Yeah, I reported my own reboot! But it was a soft reboot, and the last_kmsg wasn't backed up, which would happen if there was a kernel panic. I think this was a ROM or app issue.

Virtually none of the last_kmsges reported since stability disappeared with v4.8.3 were actually kernel panics. Without a panic, it was virtually impossible to say the cause. And because the reboots occurred so randomly, it was difficult to say at exactly what point they appeared. By the time I realised there was the same bizarre issue occurring for many users, I'd already got to v6.

I know that polobunny is not having any issue with the version that I removed the 200MHz step from, and that one still has bigmem. On that basis I'm going to re-add it, and see if it really was the cause.

The possibility which I now think is the strongest contender for the source of the reboots:

version 4.8.3
-Revert dodgy memory patch
-Tweak colours
-Reduced 1GHz step volts from 1275mV (CM) to 1250mV (Samsung default)
-Reduced preload 1GHz step in the same way
-Reduced 1.2GHz step from 1350mV to 1300mV in accordance with my calculations (see: http://goo.gl/mEMfW)
-Stability is improved for me (re: OC'ing)
-Added fastcharge
version 4.8.1
-More memory from Ezekeel's bigmem tweak
-Fixed MTP on 4G

Can you spot it?

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

... did you see it?

Voltages.

I had been setting my voltages to 1275mV because I had copied the CM voltages. Then I realised that the Samsung source was different. Plus I did that graph thing: http://goo.gl/mEMfW

I realised that not only was 1250mV the stock setting, but it also fit my graph better, and my stability was much better (no more reboots on Asphalt 7).

However, I made a major cockup. I noticed something called buck voltages, and conincidentally, it was 1275mV. I changed it to 1250mV without thinking. When did I discover this 'buck' value is meant to be 1275mV? Not until v6.7.3.

v4.8.3 - 5th October

v6.7.3 - 8th Novemeber

That's a month of that particular error existing in the kernel. :o

Co-incidentally, I blamed bigmem because I added it and removed it at the edges of the same window. My basis for that was that Ezekeel's kernel suffered random reboots which he never solved, and my assumption was that he was never able to pin down something random that produced no panics. However, this is a tenuous connection, and the only way to confirm or refute is to add it back in.

As it stands, I think the voltage is much more likely to have been the source of the problem. But I'm going to continue to wait a bit longer before providing bigmem, because it's nice to have a little peace in the thread! There's been 150+ downloads of v6.7.9 so far, so it's nice to see so many people still willing to test. With those numbers, each hour that ticks by is worth one person testing for a week!

One big plus is that I certainly learned a hell of a lot about the kernel while trying to pin this issue down!
[Nexus S Android Development] ej8989:
Reboots when opening ANY game. (temple run, virtuatennis, etc.)

No OC. kmsg attached.

ROM: Strawberry v11.10

Kernel: Marmite 6.7.9 CM
[Nexus S Android Development] fear_factory84:
Today with v6.6 I've verified that wifi pm_fast don't work.

Is it worth to update to v6.7.9, since v6.6 works flawlessy on my phone since 138 hours?
[Nexus S Android Development] :
Actually I'm going to build a personal test version now for CM only with bigmem, and extra mem stolen from the camera. This should work on cyanogenmod nightlies and Slim Bean with no problems. Strawberry, can someone please test camera and youtube?

If it works properly on Cyanogenmod nightlies and Strawberry, then I might as well always provide the extra ram from the camera.

Link: http://d-h.st/6YG (411MB free in Slim Bean, camera, video, video playback, youtube all working fine)
[Nexus S Android Development] treesurf:
I can test on Strawberry.
[Nexus S Android Development] caliban2:
Cool, I'll give that a go. Will be interesting how 4.2-camera reacts to it. :)
[Nexus S Android Development] :
Good idea, link is: http://d-h.st/6YG
[Nexus S Android Development] :
Cool, thanks!
[Nexus S Android Development] treesurf:
Tested Youtube and took several pictures, a couple videos, and a panorama. Youtube worked fine, pictures worked fine, panoramas worked fine. Got a message that Gallery had crashed after shooting one video but the Camera app stayed open and video was successfully saved.

Let me know what other testing I can do...

edit: holy crap! 412MB of RAM!
[Nexus S Android Development] :
That's pretty much it. Does gallery always crash after doing a video?
[Nexus S Android Development] treesurf:
I could have sworn I had one where it didn't crash, but I just tried shooting four more videos and it crashed each time after stopping the video. And I reported wrongly originally. The Camera app does shut down after the error message.
[Nexus S Android Development] caliban2:
With 4.2-camera:

Did 10 shots, took a 1min-video and all's fine. After that I switched to Photosphere - it took about double the time to activate. But it works fine, did a full 180°-shot. After closing the app and opening Photosphere again it took the normal amount of time to activate. Gallery works okay, so does quickpic.

So, wouldn't say you have to take action right away. Time will tell.

And yes, holy crap! 411mb...!!! :victory:
[Nexus S Android Development] treesurf:
Actually this is the first time I've ever shot a video with the phone. I'm going to flash back to a previous version of the kernel and try another video just to make sure it's not just something with my phone...

---------- Post added at 06:52 PM ---------- Previous post was at 06:48 PM ----------

OK, confirmed my videos crash on 6.7.8 as well. So it's not something in this test version that's causing it. I'll flash back to the test version and continue to run it for stability.

Funny how I never shot a video before on this phone, but now that I know it doesn't work properly I'm off to try and fix it..
[Nexus S Android Development] caliban2:
Took 4 more videos, one of them 4 minutes (got a phone call in the office, recorded that one ^^) plus another Photosphere - no problems.

So, CM nightly 20121113 plus marmite v6.7.10 plus 4.2-gallery => initial test passed.

And I think I should do a littlebit work now. Oh wait, it's lunchtime. :silly:
[Nexus S Android Development] :
Kernel testing in office hours. Nice procrastination!
[Nexus S Android Development] waterface:
Thanks everyone for your feedback. i9020T will be probably sent for a desperate attempt at a jtag rescue.

I won't ever pull the battery again unless I am forced to.

I'm back with a used i9023. Liking the SLCD screen a lot- let's look at the bright side of life...
[Nexus S Android Development] :
I reckon you need to head to CWM, wipe cache and dalvic and fix permissions. Your camera should definitely work on v6.7.8
[Nexus S Android Development] :
Ah, good to have you back. :)
[Nexus S Android Development] caliban2:
It's not like flashing a kernel and taking a few shots takes forever. ;)
[Nexus S Android Development] :
I'm not even allowed to have my phone on or visible at work!
[Nexus S Android Development] treesurf:
Tried that, still crashing. Tried the new 4.2 camera, videos still crashing. :confused:

Anyways, I'll take this issue elsewhere. Currently enjoying 412MB of RAM. :D

\

edit: crisis averted. Video function that I will probably never use is now working.
[Nexus S Android Development] alen1901:
More mem 6.7.10 is working great here on Slim Bean with 4.2 camera/gallery, YouTube works, video watching, photosphere shooting works, video capture is working. ;)

EDIT: spoke too soon, photosphere preview not working. Little planet, so you can scroll 360° photo.

EDIT2: my mistake, it was a bad flash or something, not kernel related
[Nexus S Android Development] atxbang56:
no 6.7.10 for non-CM ROMS?

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] capoooro:
6.7.10 on strawberry 11.10

Camera 4.2

Keyboard 4.2

No oc

412 mb of memory

Video OK

Photosphere OK

Gallery ok
[Nexus S Android Development] sperelli:
Hi there,

I tried to use the advanced settings for HSUPA, in the 4 different ways, in order to see how it affected the data flow.

I was on BB6.

Since then, I am encountering hard issues on data upload, when sendind sms in Whatsapp, in FB, etc etc.

I full wiped and installed SlimBean this time, to find the problem was still there.

Once more I tried to fix this annoying issue by messing with the same settings.

Yet anything seems to solve.

Is there any way to reestablish the upload transport as it is by default?

Thanks a lot
[Nexus S Android Development] :
Will make it available this evening.
[Nexus S Android Development] :
If it's compatible with your device, you could flash kb3 radio (no upload cap)
[Nexus S Android Development] deani77:
As for me, my boss will lecture me if I didn't bring my phone since they gave allowance for phone bills... :D

Anyway after 2 hours testing 6.7.10 with a few photosphere picture, phone call and no OC. No problem occurred so far.
[Nexus S Android Development] polobunny:
Yesterday I had an issue where some apps force closed themselves in what looked like a low mem available situation (including android.process.acore) after I updated a few software including HaxSync (sync with FB contacts).

Then after a minute everything came back to normal and I continued what I was doing. Could be ROM or app issue, who knows. Mostly blaming the app update, because AFAIK acore is related to sync...

Either way I'm at 180 hours uptime, so I think whatever issues might be left won't be too terrible.
[Nexus S Android Development] :
You're still on the one with no 200MHz step?
[Nexus S Android Development] polobunny:
Yup.

I'll have to reboot today because I misadvertantly clicked 2G network only. Whenever I do that, even if I disable it after, my phone cannot find my 3G only network. Switching plane mode doesn't help either. Silly issue not related to the kernel, it did that when I just got it and was still on stock 2.3.4. :p
[Nexus S Android Development] VerminX:
I get the same...I bet you are either on T-Mobile or wind network
[Nexus S Android Development] polobunny:
Neither. Koodo, Canadian carrier tat only has a 3G network. So no 2G fallback sadly (hence why I like to save battery so much haha)
[Nexus S Android Development] fear_factory84:
radio version?

I usually switch many times per day from 2g only to 2g/3g and it works fine for me.

rasbeanjelly 11/06 + marmite v6.6 + radio KI1

I had problems in the past with older radio versions...
[Nexus S Android Development] polobunny:
Any version (tried up to KJ1). Thanks for trying to help me, but believe me, it's not a kernel or radio issue.

Koodo is a 3G only carrier. No 2G service offered at all. Switching misadvertantly to 2G only will make it disconnect from the network, and after unchecking it, it won't reconnect to the network even if starting a network search. Looking for networks will only show Rogers wireless, which offers emergency service in case Koodo network falls down, so you can call 911.

It's no biggie, because I normally don't go often in the network settings, but my greasy hands went too fast and checked that dreaded box, so I have to reboot. :p
[Nexus S Android Development] granets:
Hey bedalus, Strawberry is like rasbeanjelly, but with some apps removed. So you should do a StockOTA release for it, not CM. i think this could lead to problems. If you make stockOTA releases, I am willing to test, but I don't wanna flash a CM kernel. Last time I had a no booter, and I sort of need my phone, and I don't always have the time at work to troubleshoot stuff and reflash kernels

edit: now that I read closely, Strawberry has nothing to do with rascarlo's creation - it is AOSP based. nevermind me and my blindness
[Nexus S Android Development] polobunny:
??

Bedalus already releases Stock OTA kernels. Just he doesn't always have the time to release 5 different versions each time he makes a small correction, but you'll get it eventually.

Either way, if you check the version matrix, you'll see 6.7.9 is already available for stock OTA.
[Nexus S Android Development] granets:
yeah I know, but he was asking for testing on some stuff on Strawberry with 6.7.10 that's why I did this post. I thought Strawberry is based on stockOTA, but I guess I was wrong. My bad again