yashsingh1/xdaforums huggingface dataset:
[Nexus S Android Development] BBuZZ:
I had already told you tchaari,awhile ago in slimbeans thread, that its problably from my Titanium backup against the 182 DPI from slimbean..my random reboots were usually on sms typing..i never blamed slim for the reboots... I never overclock nor dirty flash...so it must be my backups..

Sent from my Nexus S
[Nexus S Android Development] rodem77:
I don't have this issue (nexus S9023, stock rom, no overclock).
[Nexus S Android Development] leap_ahead:
bedalus I must ask you why my nexus not reboot alone ??? I use your kernel long time and ofcource rascarlo rom !!!!!
[Nexus S Android Development] Setting.Out:
You are just doing it wrong.. Hold the power button, select reboot, and select ok, and voila, reboot.. :D

And for further clarification, this was all only a joke, emphasizing that Bedalus makes a great kernel..
[Nexus S Android Development] xbs:
I would like to emphasize that your joke wasn't funny :eek:
[Nexus S Android Development] xxxMADxxx:
First time use crespo and this kernel on many roms never had reboot problem..Love this kernel..My amoled screen look amazing..Keep support it !!
[Nexus S Android Development] Warren_Orange:
Hi.

What is the most stable marmite for Jelly Shot?

Thanks.
[Nexus S Android Development] ej8989:
7.3cm if you want a bit more battery life, 8.6cm bigmem if you want pure performance (not that bad of a battery life either).

Both are stable enough. Just don't overclock. :good:
[Nexus S Android Development] BBuZZ:
Why dont over clock? Im @ 1200 with no issues, when gaming..

Sent from my Nexus S
[Nexus S Android Development] Basche:
The battery life drops since more power is given to processing
[Nexus S Android Development] BBuZZ:
Yes I know, but i only oc when i'm gaming... I wrote that... ;)

And oc is not good for cpu life neither..
[Nexus S Android Development] explorer-10:
i hope i'm not asking for too much, but anyone use caller id apps with the latest RBJ build in combination with kernel v8.6(cm-version, big mem)? One specific app I found to be working well while using Matr1x kernel is https://play.google.com/store/apps/details?id=com.guidology.talkingcallerid, but then til recently, when i flashed marmite, I've been having problems like the announcer starting to crap out on me, as if the voice was dying in a robotic manner. :(

i'm loving the kernel and its bigmem features and not freezing up on me as often, however, the only thing that's affecting me is the caller id announcer not working so well

Sent from my Nexus RBJ S using Xparent Skyblue Tapatalk 2
[Nexus S Android Development] Me Gusta:
I think you shouldn't use the cm-version of RBJ

Me Gusta!
[Nexus S Android Development] explorer-10:
you mean marmite? :p
[Nexus S Android Development] Me Gusta:
Yes, sorry, wasn't very clear indeed! But you shouldn't use a cm version of a kernel on RBJ, unless you flashed a mod that can be found in the nexus s general forum

Me Gusta!
[Nexus S Android Development] explorer-10:
anyway, I just flashed the non-cm bigmem version, and it still causes the same problem as the cm bigmem version! :(
[Nexus S Android Development] Basche:
My bad, thought you meant that you oc because you use the device for games, not oc only when you play games :p
[Nexus S Android Development] explorer-10:
and to add, the announcer for incoming sms works just fine, it's only the caller announcer that im having a problem with, idk if it's because of the vibration that's making it that way, but i already have vibration disabled for incoming calls and for some reason, it still vibrates for some reason
[Nexus S Android Development] leap_ahead:
only I know marmite cm for rbj
[Nexus S Android Development] explorer-10:
I've even tried reverting to v8.5 non-cm bigmem version, still has the same problem.

How it's supposed to sound: https://www.box.com/s/ou581gk0a4w2vkssga7l

How it really sounds: https://www.box.com/s/c1zaj9vvntk8r0c8x37i

Sent from my Nexus S using Xparent Skyblue Tapatalk 2
[Nexus S Android Development] Zahih:
Hi Bedalus, is there any reason that you don't add blink BLN feature? Btw marmite v8.6 bigmem is the most stable.. And good battery life and good performance too with smartassV2... Thanks
[Nexus S Android Development] alen1901:
Blink consumes more battery and its not stable for some.

Sent from Sparkling Nexus 4
[Nexus S Android Development] Me Gusta:
What do you mean by that??

Me Gusta!
[Nexus S Android Development] leap_ahead:
cm kernel for rasbenajelly
[Nexus S Android Development] explorer-10:
Can flashing back & forth between a previous kernel and a newer kernel or a cm version of one cause a boot animation screen not to show up? Cause right now I have one flashed, but it's blank screen :(

Sent from my GT-I9100 using Xparent Skyblue Tapatalk 2
[Nexus S Android Development] Me Gusta:
Any advantages from cm-version over the non cm-version?

Me Gusta!
[Nexus S Android Development] :
As already said, blinking caused wakelocks for some, draining battery.
[Nexus S Android Development] leap_ahead:
I dont know
[Nexus S Android Development] andrei1015:
I don't think you can compare the two. They are for different kinds of ROMs.
[Nexus S Android Development] explorer-10:
can anyone confirm? :(
[Nexus S Android Development] andrei1015:
Don't flash a CM version on stock or viceversa.
[Nexus S Android Development] Setting.Out:
You can compare them, there is a flash able zip to alter your ROM to/from cm/aosp.. And I have, with no noticeable results...
[Nexus S Android Development] explorer-10:
is RBJ considered cm?
[Nexus S Android Development] Jamalsid:
It's not a matter of whether they are considered CM or not it is all about whether the ROM uses the CM custom I/O tweak (I believe).
[Nexus S Android Development] explorer-10:
i think my nexus is slowly starting to deteriorate! :( whenever i flash kernels back and forth, it slowly messes with the bootanimation. either it takes a while for it to show up, or it just stays at a black screen for a really long time causing me to remove my battery constantly and doing it again, OR flash back to matr1x and then eventually run into a screen freeze which i have to do another battery pull once again. im stuck in a loop! :'(

i've wiped cache and fixed perms, cache-dalvik-AND perms, reflashed zips, problems still there. i've even just gone through a problem where my phone reboots right after it finishes loading, including loading scripts from rom toolbox(I am now stuck in a bootloop trap :[ )
[Nexus S Android Development] :
Backup your apps and wipe everything and start fresh
[Nexus S Android Development] teoserio:
I suggest you all one of the tool from JRummy that I recently discovered. It's ZIPme.

Is still in beta, but the idea above it's simple and very helpful for the people addicted to flash :)

Don't create file of more than 10 app per time or the creation of update.zip can likely fail (the app use the data internal memory storage as RAM while making the file).
[Nexus S Android Development] explorer-10:
just to be safe, wiping doesn't interfere with the usb storage correct? also, how can I backup my ttexts if I can barely access the homescreen?
[Nexus S Android Development] Setting.Out:
Do a full nandroid backup.. Can't confirm if it saves all texts?? if you only wipe dalvik cache data, your sd will be safe, but always good to backup incase of any issues that could arise.. And make sure you wipe dalvik and cache before flashing other zips like kernels over a rom..
[Nexus S Android Development] polobunny:
Nandroid saves everything but SD card. If you do a factory reset, all the data is wiped, but again not the SD.
[Nexus S Android Development] explorer-10:
oh yes praise the good Lord! I can gain access to my phone once again! better make some important changes while it's still in working order and do a android backup and probably .xml data backup as well!

hmm, ok this is weird. now that my phone works, I have lost 99% of my contact numbers since am logged out of google and the google account doesn't show up under accounts. when I go to add account, there's nothing google related and I am also unable to access the play store. on another note, my keyboard doesn't Swype words now. when I Swype, nothing comes out, I have to manually type it out. adding on, my talking caller id calls & sms app now ceases to work
[Nexus S Android Development] ej8989:
What will he do with the nandroid backup? The buggy rom, kernel, and all the crap it has will be restored if he decides to do so. Solves nothing.
[Nexus S Android Development] explorer-10:
on the upside, my phone magically came back in working order :) i have no idea how, but it somehow just did

downside however, the talking caller id calls & sms, talking caller id app & others similar seems to have a really choppy voice when announced, dunno if it has to do with takback having problems with the kernel(but when previewing the announcer, it's fine. the issue arises when i receive a call) and bootanimation takes a while to show up, leaving me at a black screen for a long time(approx. 2-3 mins or so) before it shows up. other than those problems, everything else seems to be okay, at least i think it's okay
[Nexus S Android Development] :
I think your best bet is to get just the apps you really need into a titanium backup, then copy that folder off your phone.

Copy all your media off your sdcard too, then wipe every partition including sd and install any Rom that you know works properly.

Setting up your phone fresh can be fun, and certainly rejuvenates performance.

Put your titanium folder back to the same location, restore your apps selectively. Maybe just the caller id one first to see if it works right.

Then you can start to bring your other apps back. Continue to check caller id along the way.
[Nexus S Android Development] weedy2887:
I'm having issues getting 1.3ghz stable, before I give up on it can everyone please post there /sys/class/misc/customvoltage/{arm,int}_volt settings?

Also bedalus can you give the camera another mb or something? It loads 8 times out of 10 for me, with 1 to 3 restarts needed when it FCs.
[Nexus S Android Development] :
Sounds odd. Are you on the bigmem version?
[Nexus S Android Development] leap_ahead:
I test big mem version on 4.2.2 rom and no problem with camera
[Nexus S Android Development] Jamalsid:
Hi bedalus just wanted to say thanks for the great kernel. I am retiring my nexus s as I have moved onto the HTC one. Thanks for keeping the nexus s alive.
[Nexus S Android Development] :
It was a great pleasure to have you add a regular here! Enjoy your new device :)
[Nexus S Android Development] explorer-10:
I too am having a problem keeping 1.3 ghz stable. The highest I can keep stable is 1.1 ghz or in this case,1096 Mhz. On 1.3 ghz, it would reboot.

Sent from my GT-I9100 using Xparent Skyblue Tapatalk 2
[Nexus S Android Development] :
It won't work for everyone unfortunately
[Nexus S Android Development] ej8989:
+100mv gives me a stable 1.32ghz OC on marmite.
[Nexus S Android Development] leap_ahead:
Where 100mv?
[Nexus S Android Development] ej8989:
+100mV on 1320mhz step only.
[Nexus S Android Development] Sucky1983:
Does adjusting the int voltages make any sense?

Nexus S jellyshot and marmite bigmem
[Nexus S Android Development] :
Here's a link from the op: http://xdaforums.com/showthread.php?p=33184975

It's a little out of date as 1.2GHz step is gone

Just remember 1.3GHz step has fsb/gpu oc

Whatever INT volt works for you at 1.1GHz, you need the same at 1.3
[Nexus S Android Development] Sucky1983:
Thank you! Arm and int +25mv looks good for 1096mhz at the moment. I have been using your kernel for ages, but never managed a stable over clock. Today I discovered, that you can scroll down in devil tools and set int values. *facepalm*

Nexus S jellyshot and marmite bigmem
[Nexus S Android Development] leap_ahead:
int and arm ?
[Nexus S Android Development] ej8989:
yep. but i only did it for a little more than a day. i don't know if it's safe to keep it that way. :confused:
[Nexus S Android Development] leap_ahead:
Anyone know if is safe

?
[Nexus S Android Development] skinner12:
Is it possible to compile this kind of kernel with gcc 4.8? I've tried with linaro gcc but it won't start: I had loop on boot animation..
[Nexus S Android Development] tommy0823:
If you can provide a logcat and your last kmsg, that would help determine the cause.
[Nexus S Android Development] :
I saw a suggestion that slab might work. Change the .config
[Nexus S Android Development] leap_ahead:
If boot i want to test !!!
[Nexus S Android Development] :
I think there might be some performance regressions with the early 4.8.* gcc
[Nexus S Android Development] alen1901:
If you use linaro 4.8, you must switch to SLAB. SLUB is somehow not compatible. Also, with 4.8 linaro there is visible performance boost.

Sent from Sparkling Nexus 4
[Nexus S Android Development] polobunny:
Quantifiable with synthetic benchmarks?
[Nexus S Android Development] alen1901:
Screw benchmarks. User experience is what matters.

Sent from Sparkling Nexus 4
[Nexus S Android Development] polobunny:
Everything can be benchmarked, it's just a matter of benchmarking it with the proper tools and form.
[Nexus S Android Development] :
We love the benchmarks! :p
[Nexus S Android Development] skinner12:
How can I take log if upto 5 seconds of boot image it reboots?

Ok, I take a look into..
[Nexus S Android Development] ciaastek:
Hi, I just wanted to say that today I received my Xperia S. My Nexus S is going to my fiance so it won't be that far. I'll still subsribe this thread and SlimBean's because I'm really curious what will devs bring to this great device. I convinced my fiance to use Nexus (she had Nokia Asha 303, blegh) just because I wanted to test it from time to time and compare it to Xperia.

Many thanks to you bedalus and other people who contributed making this device fast and fresh, even now, even when Google left it. Thank you!
[Nexus S Android Development] :
I'm glad you're hanging on to it! Sort of... Enjoy your new device!
[Nexus S Android Development] alen1901:
Well... No. I dont believe in any benchmarks. Its not because of benchmark apps and its codes, its because phones and its cpu, gpu, ram etc, they cant operate all the time at the same level, that way benchmarks can vary. User experience is what is good benchmark. Human eye can see every speed up or slow down, stutter, lag etc more better than benchmark app. So if i see my phone flies (not talking about fresh reboot) with new kernel in comparison with older one, and also there are quiet few other reports, ill believe in that rather than benchmark.

Sent from Sparkling Nexus 4
[Nexus S Android Development] towelboy:
Crazy how when bedalus got the htc one x+ I didn't think about getting one but now I have one! (although not international version)

I miss this forum, is the nexus still running good? :D
[Nexus S Android Development] NickName98:
I have a problem about the audio. I asked it in jellyshot thread but they told me its Marmite's issue.

Whenever I listen to music, the volume is very low. I think its around -10 and -15db. I use voodoo sound app to set it at +0db. Although, I have to launch the app every time I want to hear some music and it's really annoying. How can I fix this?
[Nexus S Android Development] Setting.Out:
[MENTION=4128576]bedalus[/MENTION], or anyone that can answer this.. How can you extract a kernel from a rom?..
[Nexus S Android Development] :
It's usually in the zip. Probably in the root of the zip, but you're looking for a file called boot.img
[Nexus S Android Development] polobunny:
Not looking forward sparking a debate, but the human eye is one of the least reliable benchmarking tool. Ever tried to estimate the height of a building? Or maybe you know someone who wears glasses? Have you ever seen a magician perform a trick? Your eye might be better than mine, or vice versa.

If we based ourselves on our perception to compare everything, we'd live in a very hectic and unsafe world. It's difficult to make quality comparisons if we don't even use the same tools. :)
[Nexus S Android Development] leap_ahead:
boot.img is the kernel ?
[Nexus S Android Development] :
It's a combination of the kernel the ramdisk. You need a tool to extract the zImage if you only want the kernel
[Nexus S Android Development] Setting.Out:
Every article I've read has me looking for a zImage, but I can't find it in my rom folder..??
[Nexus S Android Development] :
You need a tool to separate the zimage out from from the boot.img. I'm not sure if I've got the tool anymore. I'll have a look now for you
[Nexus S Android Development] Setting.Out:
A ton more reading.. Unyaffs and the lot.. Can I skip a step and just swap boot images?.. If they are both crespo, no worries right?.. Both cm and or Aosp?..
[Nexus S Android Development] androidphone2012:
http://xdaforums.com/showthread.php?p=5626300

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

http://xdaforums.com/showthread.php?t=2073775
[Nexus S Android Development] Setting.Out:
Thanks [MENTION=4489079]androidphone2012[/MENTION], [MENTION=4128576]bedalus[/MENTION]... Looks like someone will be cooking in the kitchen tonight.. Now can someone help me from getting introuble with my wife for being glued to the computer?.. Is there a "wife tool".. *WAIT* don't answer that.. lol
[Nexus S Android Development] :
Aha, found it: http://d-h.st/wVZ

These are the tools you'll need to split the ramdisk and the kernel from the boot.img

Go to the first page and ctrl+f 'boot.img' to look for the info you need
[Nexus S Android Development] alen1901:
I know that. But here you are not estimating anything. And there are many people (FPS game players and eye trained ones) who can notice every stutter or slowdown. Its because newer phones are allways faster and our eyes adopts to it, it become normal, not fast after some time of use. So when you use n4 for 2 weeks, than go back to s2, you will see massive performance degradation on s2. Because your eye adopts to faster speeds, smoother transitions etc. I personally can see every little thing on phone, every single stutter. Sure some people dont have trained eye at all and wont see a difference between n4 and galaxy i7500. And also, guys who spend many months on forums, provides feedback etc, flashes kernels and roms, and have respectfull status, that are the ones to trust. They also know their phones inside and out. Im not saying benchmarks are stupid, they just cant calculate and bench real life user experience. Use galaxy s4 for example. Scores on every benchmark are in heaven, beats every other device, but in real life usage, you dont see that. You see many stutters and little freezez. And dont say its because of touchwiz. Sure, yeah, it helps to degrade performance, but htc one and nexus 4 are so fluid and smooth phones. Htc one and n4 are on paar. Htc one is little faster (better cpu). So, i say that benchmarks are only for people who wants numbers. :) user experience and real life usage is what counts the most.

Sent from Sparkling Nexus 4
[Nexus S Android Development] :
I think you've raised some interesting points. Of course it's a debatable issue, which of course means there's just as much opinion as there is fact. I did test BFS versions, and found they had higher benchmarks, but definitely introduced problems with the interface.

Also, on the quad core HTC One X+ I was looking for a tweak to improve SD performance, and noticed that when limiting to one CPU, continuous writes were faster. So I created a tweak to ensure one CPU did all the IO ops. Continuous writes were faster, but every other benchmark was worse! So even if you improve something, you need to be careful that it hasn't damaged something else!

I think it's desirable to see benchmarks going up, but what's more important is that they don't go down! And finally, after messing with anything, it's important to get user feedback! I hope I've done that in this thread!
[Nexus S Android Development] alen1901:
You bedalus mastered yourself in every way. ;)

Sent from Sparkling Nexus 4
[Nexus S Android Development] skinner12:
I tried to modify configuration for build with gcc 4.8 but it looped on Google screen..
[Nexus S Android Development] :
SLAB didn't work then?
[Nexus S Android Development] skinner12:
No, i activated slab and turn off slub, but didn't work and I don't know how to debug errors..

Nocerino's Rulez with RAScarlo's ROM features TriNitY ;)
[Nexus S Android Development] :
Yeah, I think just stick to v4.7.x for now
[Nexus S Android Development] leap_ahead:
ok I have the zImage now but how to flash ? this is name of file : boot.img-zImage
[Nexus S Android Development] :
Rename it to zImage and paste it into marmite.zip in the kernel folder instead of the existing zImage
[Nexus S Android Development] leap_ahead:
thanks for the trick is working !!
[Nexus S Android Development] CataHd:
Hy guys i am new here,just moved yesterday from galaxy gio and i just wanted to say this kernel is awesome,tried it yesterday on cm10 and today i moved to cm10.1 great work:)

BTW why didn't anybody tried to port linux kernel 3.4.x for cm10.1?
[Nexus S Android Development] :
I was tempted to give it a shot, but I got a new device.
[Nexus S Android Development] CataHd:
Ok then:)

Hopefully someone could port it
[Nexus S Android Development] polobunny:
Because there's no real advantage to doing so for an aging device.
[Nexus S Android Development] Setting.Out:
Whoa.. Aging??.. Shhhhhh.. My phone could hear you..

I don't think that just because it's not "new" that we should throw in the towel.. :)
[Nexus S Android Development] polobunny:
It's not throwing the towel, it's pretty much pointless. It brings nothing of use for the Nexus S yet requires much effort.

See what 3.4 brings:

http://kernelnewbies.org/Linux_3.4

Might be worth looking at what anything over 3.0 offers to, to fully understand.

http://kernelnewbies.org/LinuxVersions
[Nexus S Android Development] Setting.Out:
I get it.. You opened my eyes.. Improvement for improvement sake is pointless if it's too hard to do... if a developer wants to innovate a relic I say great!! I am glad that all the devs here haven't stopped improving the old NS...
[Nexus S Android Development] polobunny:
That's the thing though, it wouldn't be noticeable improvement. You'd have the latest kernel, but it would feel exactly the same as 3.0. Improvement for the sake of improvement is great, but working hard for the sake of having the latest yet not having any tangible improvement is masochism. :p
[Nexus S Android Development] Setting.Out:
Pull out the leather... Lol.. It's still the dev's choice... I'm just glad to have their support..
[Nexus S Android Development] :
I'm no masochist! It's a good kernel, getting in to porting the drivers now would be really difficult, and not very satisfying given I couldn't even test it!
[Nexus S Android Development] leap_ahead:
Hmm
[Nexus S Android Development] polobunny:
And not very necessary. :p
[Nexus S Android Development] leap_ahead:
If you want for test just send me :p
[Nexus S Android Development] Setting.Out:
+1
[Nexus S Android Development] CataHd:
Isn't it more easy to port it using CAF kernel sources like the developers from galaxy s plus did?
[Nexus S Android Development] joshk89:
Just wanted to stop by and say this kernel it's great and thanks for your work. Running super smooth on slim Rom
[Nexus S Android Development] leap_ahead:
bedalus any news ?
[Nexus S Android Development] :
Uh, I'm working really hard on the one x+

What needs doing?
[Nexus S Android Development] Sucky1983:
8.6 is too stable, we need bugs to brag and cry about :silly:
[Nexus S Android Development] leap_ahead:
Oh sorry i think you try to port 3.4 on nexus
[Nexus S Android Development] polobunny:
*chuckles*
[Nexus S Android Development] :
no point in porting when there is no real advantage in doing so
[Nexus S Android Development] Setting.Out:
+1.. lol..
[Nexus S Android Development] polobunny:
I don't even know how to say it anymore. It's like people think 3.4 will make their lives better, just cause it's 4 decimals bigger than 3.0. :p
[Nexus S Android Development] :
I'm too drunk right now to port kernels. I like pear cider, mmm.
[Nexus S Android Development] leap_ahead:
Guys if u see i use the old good 7.2.2