yashsingh1/xdaforums huggingface dataset:
[Nexus S Android Development] :
just set it so you can wake the screen with volume buttons. and there's other kernels with the feature-- no need to bloat every kernel with the exact same things
[Nexus S Android Development] jayjay3333:
After I bought a Nexus 4, my NS became my 4 year old daughters. I loaded it with kid games and Google Music for me. It sits sometimes but it is used.

This my friend is stability! I chose this over stock and I think I made the right choice :p
[Nexus S Android Development] .stendeck:
Rasbeanjelly 4.1.2 + Trinity (???)

Which version of Trinity you've chosen? :)
[Nexus S Android Development] .stendeck:
Ah, okay. Seems to be TNS12-JB-ALPHA12. :)
[Nexus S Android Development] jayjay3333:
Right :good:
[Nexus S Android Development] UserProfile:
Trinity 1.44GHz + Voodoo Sound for JB please! Your Kernel is only one almost without random reboots on high frequency CPU :rolleyes:

On all other kernels there are problems with OC.
[Nexus S Android Development] explorer-10:
Any working version for 4.2.2?
[Nexus S Android Development] insid3r:
I've got to bump on that.

Flashed T132 and TEUV on CM10.1.2 and the results are awful.

BR
[Nexus S Android Development] :
They all work great for 4.2.2. If you're using a CM based ROM you need the black screen fix
[Nexus S Android Development] leap_ahead:
any news ?? the last time I use this good kernel is from 4.0.4 :(
[Nexus S Android Development] :
nothing to add to an already perfect kernel, except for maybe the BT fix.
[Nexus S Android Development] leap_ahead:
I know but i wait for bt fix,crt fix, and bigmem ..maybe 407 or r 411 mb ram

One more is mtp
[Nexus S Android Development] AndroidWolf59:
I'm using it with 4.1.2 :good: I think that morfic now is thinking about work, holidays, perhaps his kernel for Nexus 4 ... Our old Nexus S is a little bit neglected ... :crying:
[Nexus S Android Development] leap_ahead:
[MENTION=1828657]kwibis[/MENTION] Hello the link is not working

. u can upload again if u have it ?

Thanks
[Nexus S Android Development] kwibis:
I've found one of 5 days earlier (2012-11-01) uploading it now. http://db.tt/0OLGft3b here you go
[Nexus S Android Development] adm1jtg:
If you look up metal dragon overlord in this forum thats ALMOST pure rasbeanjelly but has gapps included. Might be easier for you to setup and it runs superbly
[Nexus S Android Development] leap_ahead:
[MENTION=1122306]morfic[/MENTION] any news about kernel update ? :P
[Nexus S Android Development] leap_ahead:
Guys how ican see if my gpu is 220mhz?
[Nexus S Android Development] cannondaleV2000:
Morfic told me this is how to tell if its higher speed. "Your s*it will be faster
[Nexus S Android Development] morfic:
Quiet in here, does the kernel still work or do we need something for 4.3?
[Nexus S Android Development] jwee5467:
Haha not sure. I rolled back to 4.1.2 rbj
[Nexus S Android Development] morrigan91:
yes.:o
[Nexus S Android Development] morfic:
Either/or, not yes/no
[Nexus S Android Development] leap_ahead:
bt fix, more ram , crt fix
[Nexus S Android Development] morrigan91:
Either ??.. Crespo - Crespo4g ?
[Nexus S Android Development] adm1jtg:
Most 4.3 roms are using selinux in permissive mode and this would need to be enabled in the kernel. If the rom has selinux enabled and the kernel doesn't it causes all kinds of issues.
[Nexus S Android Development] morrigan91:
A ok, i know.. but I had not understood :)
[Nexus S Android Development] AndroidWolf59:
Hallo, I used it till 1 month ago with Carbon Rom (4.2 release) then I went back to 4.1.2 MDO.

Nice to see you're still interested in Nexus S world :good:

p.s. The only think I've noticed is that using your kernel, if I want to OC using NStools I've found no problems, using TKT my Nexus "freeze" and I have to reboot removing the battery ..
[Nexus S Android Development] UserProfile:
Hello

Works wifi tethering with this kernel?

This kernel with Slim Bean 4.2.2 - and Wifi tethering did not work.

With Slim Bean 4.3 - not tested.

and please return 1,44GHz frequency! :P

This is the only kernel works well with such a high frequency...

Have a nice day :)
[Nexus S Android Development] leap_ahead:
any update ??
[Nexus S Android Development] AndroidWolf59:
About 1 month ago morfic asked something about his kernel "status" but I think he was asking if there is any interest in 4.3 version.

I'm using 4.1.2 and testing his last version (1 Apr 2013) I find is good enough ;)
[Nexus S Android Development] leap_ahead:
I try it ...
[Nexus S Android Development] Setting.Out:
And... ??? How does it appear to compare?
[Nexus S Android Development] leap_ahead:
I think is faster because is 220mhz the bus speed.. No overclock on cpu
[Nexus S Android Development] Dark_Eyes_:
Trinity is the only kernel I managed to oc at 1400 mhz without reboot. It is indeed a fast kernel but it's not the only one with 220 mhz on the bus. Marmite is also at 220 mhz when you oc it and devil can go to 220 with live oc at 110%. Only problem for me with Trinity is that it is not SELinux enabled, so it is not a good idea to use with SELinux enabled roms.
[Nexus S Android Development] morfic:
There are nexus s roms that are not simply SELinux "permissive"?
[Nexus S Android Development] Dark_Eyes_:
From my experience, whether it is set on permissive or enforcing doesn't make a difference. If the kernel is not SELinux it will say Not enabled or something like that. The kernel needs SELinux to set it to permissive.

Anyway, if you have any interest, a little tune up with latest mainline updates would be great. You might have to update liblights on crespo cause bln stopped working recently on cm rom.
[Nexus S Android Development] adm1jtg:
No.... Far as I know very few apps support enforce mode SeLinux. Slim rom could run enforce but it breaks everything as apps arent ready to use it
[Nexus S Android Development] Dark_Eyes_:
I know... What I'm saying is that to be in permissive mode, the kernel must still be SELinus enabled... But you're right, I don't think many user use the enforcing mode... I'm in permissive as well, but if the kernel doesn't support it it breaks SELinux and says Not enabled or something like that. Guys at Slimbean said it could cause all sorts of problem if a rom that is supporting SELinux is used with a non SELinux kernel.
[Nexus S Android Development] adm1jtg:
All very true. As of right now I believe the only two "selinux safe" kernels are marmite (discontinued) and devil... unless your really desperate and want to use the default cm kernel that is junk.

Actually I would ask morfic to hold off updating until kitkat since that should be out anytime now, and we will certainly need all the dev's mad skillz to even have a chance of running it on our devices.
[Nexus S Android Development] Dark_Eyes_:
Agreed! I hope there will still be one or two dev willing to build 4.4 for our device cause I'm stuck with it for another long year... I'm using devil by the way and it is very good!
[Nexus S Android Development] AndroidWolf59:
Just my personal opinion

I think that 4.3 roms are a little bit heavy for Nexus S. I tried some of them (like Carbon or CM 10.2) and, comparing with

4.1.2 in term of speed, reactivity, bugs and battery consumption I found everything in the lead of the old version.

So, apart from problems concerning SElinux or similar, I think that take any chances with 4.3 or waiting for 4.4 is simply a waste of time.

Unless you do not expect a miraculous kernel ... ;)

But, I repeat, this is just my thought
[Nexus S Android Development] adm1jtg:
I disagree while that was true for 422 vs 412 I would say slim 4.3 build one is as fast and responsive as rasbean 412
[Nexus S Android Development] ppreuss:
I share this thought 100% ...much problems with 4.3!
[Nexus S Android Development] siffar:
Totally agree. Slim 4.3 is faster than even AOSP 4.1. Thats why I am keeping it :)
[Nexus S Android Development] morfic:
Cm broke bln before, ugh

And yes, permissive is still SELinux, just with development option which defaults it to permissive, that shouldn't be hard to do, but I hate 4.3, and it's too close to 4.4 to do anything
[Nexus S Android Development] Dark_Eyes_:
Well, bln is working in cm if you use the stock kernel... It's the bln that is used in custom kernel that is not working anymore. In fact, cm changed something with the liblights so the old bln file for crespo, s5pc110.so doesn't exist anymore, so that breaks bln. I think one have to build liblights from cm to fix it...

And yes, 4.4 is coming real soon so it's better to hold off a bit and see what we can do about it on crespo!
[Nexus S Android Development] morfic:
The bln in custom kernels came before the bln in cm, so cm broke.
[Nexus S Android Development] UserProfile:
Version with OC for Android 4.4 pleeeasee...
[Nexus S Android Development] jwee5467:
Unfortunately this is not likely to happen. Been a long time for Trinity on crespo but I would personally run latest official rasta with trinity (4.2 me thinks) and be happy with that. I run that on my crespo as a media player whilst having a hammerhead and HTC one as daily drivers. RIP crespo
[Nexus S Android Development] KiD3991:
I know this sounds out of the blue but [MENTION=1811927]simms22[/MENTION] is Trinity update for Nexus S totally dead?

I have a i9023 I'm dying to keep alive, its running 4.4.2 but there's no kernel support for it already.

So if its really dead, can you tell me which version of Android is the latest TEUV(written in Der website) on?

Thanks again. I'm turning into one of the Trinity Minions, you can expect when my GNex reaches the first I'll try is Trinity too. :p
[Nexus S Android Development] jwee5467:
I was running devil kernel (seems like the closest thing to Trinity on crespo) on 4.4.2 before I got my nexus 5. As for trinity I believe there are some test builds still on derkernel but they haven't really changed for a lot time. As far as development goes, I believe morfic is very busy especially with his new rig and trying to get development going for the modern devices. REEEEP
[Nexus S Android Development] KiD3991:
But do you know the Android version of the latest build?
[Nexus S Android Development] jwee5467:
Latest build of what? Trinity? As far as i know the latest Trinity kernels work for 4.4.2 which is the latest android version currently.
[Nexus S Android Development] KiD3991:
Trinity for Nexus S. Is it? But its not inside Derkernel.
[Nexus S Android Development] Setting.Out:
http://www.derkernel.com/jb-crespo.php

These are technically for Jellybean, but Jellybean kernels seem to work, minus some functionality like SElinux..
[Nexus S Android Development] KiD3991:
Thanks for the swift reply, but under which Jelly Bean do they work under? 4.1 or 4.2?

I know its impossible for 4.3 since 4.3 only existed around September 2013.
[Nexus S Android Development] Setting.Out:
again, they work on all Jellybean versions, minus some functionality like SElinux... but I think the last version was geared towards 4.2.x
[Nexus S Android Development] simms22:
so, [MENTION=3644884]Vangelis13[/MENTION] sent me a nexus s today.. now i have a nexus s, again! :)
[Nexus S Android Development] Setting.Out:
Welcome back.. ;)
[Nexus S Android Development] albundy2010:
I still use it regularly as a mp3 player. It's stock plus root for voodoo sound.
[Nexus S Android Development] devil188:
Welcome back mate :)
[Nexus S Android Development] simms22:
thanks :)
[Nexus S Android Development] leap_ahead:
welcome back !! any new for 4.4 on nexus ?
[Nexus S Android Development] devil188:
Just wanna tell that you seem to be the last developer who might make a kernel for us, all the others already jumped out :)
[Nexus S Android Development] homerograco:
Raise your hand if you want Trinity (T144 \m/ or TEUV?) + Bigmem!
[Nexus S Android Development] leap_ahead:
+1 for 4.4
[Nexus S Android Development] DarkShadow69:
+1 for 4.4 :)
[Nexus S Android Development] Setting.Out:
+1 for 4.4
[Nexus S Android Development] iakoboss7:
+1 for 4.4 :D
[Nexus S Android Development] anshumandash:
I still use my nexus s as a backup phone with a working SIM. A new kernel will make it run like a new phone. ;)

Sent from my Nexus 4
[Nexus S Android Development] simms22:
im not a developer, im trinitys official tester. anyways [MENTION=1122306]morfic[/MENTION] cant make a 4.4 kernel, as theres no official 4.4 source for it. without source, morfic wont make it, as he only follows official channels, sorry :(

anyways, how are you guys getting trinity kernel to run? is there another file to flash to get it working on 4.4? i tried and everything got really slow without any button working(lol).
[Nexus S Android Development] devil188:
No

Well, none of us tried yet to flash this kernel straight to 4.4.2 ROM. The devil kernel seems to work, but I don't know if it'll work with this kernel, too. As u said, it really bugged out, so that means someone has to do stuff inside the kernel to make it work.
[Nexus S Android Development] simms22:
well i got trinity working on a 4.4.2 rom, C-RoM. i found a convert for flashing aosp kernels to cm file. flashed it then the last T132, runs well after. i did get an issue though, i dont know if its from the kernel or not, but my storage isnt seen :eek: http://xdaforums.com/nexus-s/development/guide-cm-aosp-kernel-t2245651
[Nexus S Android Development] simms22:
on the latest euroskanks cm11 kang with t132 and that file to flash aosp kernels. running great! but no storage. I get storage back when I flash the ROM again without trinity.
[Nexus S Android Development] leap_ahead:
I have this problem with other kernel
[Nexus S Android Development] FuZZ__:
I haven't been looking into it but at least needs support for SELinux. Here is an example from cm stock kernel: https://github.com/CyanogenMod/andr...mmit/2129c2e966ccbc9e5ba94ab379cf15440a681e07
[Nexus S Android Development] simms22:
well, it runs well. its just that i lose storage if i flash trinity. but if i dirty flash the rom without the kernel, i get my storage back. so, this us how it will be, im gonna use trinity and [MENTION=1982549]Fuzz_[/MENTION] cm kang normally. and when i need to download something, ill just boot the rom without the kernel :)
[Nexus S Android Development] simms22:
:D
[Nexus S Android Development] FuZZ__:
It's been a long time since I've built CyanogenMod for crespo but never imagined that'd happen... and I know why airplane mode is enabled ;)
[Nexus S Android Development] simms22:
yea, it has been a long time my friend :)
[Nexus S Android Development] UserProfile:
+1 for 4.4 :)
[Nexus S Android Development] simms22:
i just enabled art on my nexus s, with a quick boot up time of 40 minutes! anyways, its surprisingly quick using art on it :)
[Nexus S Android Development] anshumandash:
Yes. That's right. I am running an old build of slim and few days ago when I switched to art, I was surprised how smooth it runs with art.
[Nexus S Android Development] simms22:
it actually caught me by surprise, the difference in running art and not. it seems that the nexus s low ram issues arent as obvious when using art as opposed to dalvik.
[Nexus S Android Development] KiD3991:
Nexus S is back in my hands. Time to trinitize all 3 of my Nexus.
[Nexus S Android Development] simms22:
sweet. dont forget to grab that aosp.zip file and flash it before flashing trinity if you chose a cm based 442 rom :)
[Nexus S Android Development] KiD3991:
Done it, thanks ! Will order a GNex and Nexus S battery to revv both of the device up.
[Nexus S Android Development] simms22:
sweet. now i dont feel so alone :angel:
[Nexus S Android Development] anshumandash:
You can't be alone. All of us were here and waiting for you. [emoji6]
[Nexus S Android Development] KiD3991:
I intend to be a Nexus Collector, that have all usable Nexus in their top conditions(internally).

Currently using Nexus S as a Burn-In audio device.
[Nexus S Android Development] simms22:
id have them all as well except i also lost my nexus one in hurricane sandy(as well as my pair of g1) and my galaxy nexus got stolen last august :(
[Nexus S Android Development] KiD3991:
You told me about the GNex lol. Sorry for your loss. :(

I plan to get a Nexus One once the price drops even lower. I'll fixate the thing to a KitKat rom and leave it so.

I remember you mentioned in some post somewhere saying KitKat is not for low RAM devices, I think its only partially right though, KitKat is pretty good on low RAM devices but only if its not running ART.

Yesterday my GNex was in ART but using Trinity, the result is pretty terrible... (could be ROM side too), I then figured to lower minfree values since Linux utilizes all RAM , but its an even worse idea, after a while the device stutters even more, barely usable for a guy that uses N5 in Trinity and Velocity ROM. (Twice the cores, Twice the frequency OC to 2.4, not to mention A9 vs A15).

But on the other hand, on a HTC Sensation which have slightly less RAM than GNex, runs fine without ART but in KK. There's a lot of reasons for the difference though. For instance, its running Qualcomm's last flagship class SoC before going to Krait, which IMO is better than TI OMAP.

Now GNex runs fine on ART when on SlimKat(one of the best team IMO that supports legacy and old devices).

Simms, what's your standpoint on CrossBreeder on older devices?
[Nexus S Android Development] simms22:
thats odd, as i enabled art on my nexus s a few days ago, and it makes quite the difference. it shows less of its ram starved side.

oh, my standpoint on crossbreeder.. wtf is it?
[Nexus S Android Development] KiD3991:
Yet to be concluded, I have not touched my S yet. GNex running fine on 1.5 now. Surprisingly stable and fast. Quite the UV beast, but I didnt UV too much

Similar to something called Seeder which caused quite the hassle a while back, something about entropy pool and filling it reduces lag and stuff.
[Nexus S Android Development] homerograco:
I confirm that ART runs perfectly at the NS. The only downside is that ART uses much more internal memory than Dalvik...not an issue for me since I have just a few apps.

And to be honest, lately I am enjoying much more my old NS than my other (not so old) 2012 N7. There I´ve tried lots of ROMS, kernels and even F2FS, but it doesn´t amazes me as much as the NS :D
[Nexus S Android Development] simms22:
nice :)
[Nexus S Android Development] homerograco:
After a few days ART is not performing that well.. I will return to Dalvik.
[Nexus S Android Development] simms22:
do you reboot often or not?
[Nexus S Android Development] homerograco:
I never reboot, but with Dalvik I feel there is no need to do it. Art makes some apps snappier and others heavier, dalvik is a more stable option I would say.
[Nexus S Android Development] simms22:
you should take that 1 minute time to reboot every day or every couple of days. your phone will appreciate it, and will run better.
[Nexus S Android Development] simms22:
Nexus S, perfect score ;)

rasbean android 4.1.2 and t132.
[Nexus S Android Development] KiD3991:
Simeons(is that your right name?) can you update the rasbean ROM up? I safely assume Voodoo is enabled in the kernel so I'd like to try it out as well. I heard too much about voodoo to the state that I nearly bought a Galaxy S to use it then I noticed i9023 is just as good.

Thanks in advance!
[Nexus S Android Development] KiD3991:
Also is there marginal improvements changing to ART on Nexus S? Or staying Dalvik is a better choice?

I'll ask the same question for GNex...
[Nexus S Android Development] albundy2010:
As far as I can remember the kernel has voodoo sound built in. But even if it doesn't you can load the sound driver with the premium / paid or maybe it was called plus version of francois app if you're rooted
[Nexus S Android Development] anshumandash:
ART feels faster than dalvik on the Nexus s. Switched to it few days ago and could feel the difference clearly.
[Nexus S Android Development] KiD3991:
What are you using? What ROM?

---------- Post added at 11:30 PM ---------- Previous post was at 11:28 PM ----------

I downgraded 4 levels just to try it out. I won't say I am disappointed but Viper4Android can do much better IMO, but just require skills and experimentation to do it.
[Nexus S Android Development] anshumandash:
I am using slim Kat
[Nexus S Android Development] melvinchng:
Looks very fast... so, any things bad about the 94 kernel? Or anythini behaved badly?
[Nexus S Android Development] eatTHESEbullets:
I say just try it. You will never know until you apply it to your device. Some people love it and for others its bootlooping and other random reboots. Just try it and see how it works for you.
[Nexus S Android Development] Babydollll:
This is the latest T13

Sent using two tin cans and some string.....
[Nexus S Android Development] melvinchng:
The quadrant for 940mhz already win dual core 1.2ghz sgs2...
[Nexus S Android Development] asafru:
Got a lot of radio dumps after flashing tuv11. Is there any preferred radio for this kernel? I still use kb1. Any recommendations?
[Nexus S Android Development] simms22:
i use KD1:)
[Nexus S Android Development] Babydollll:
I've been using kb3 with no issues...on my Nexus S....ignore what's below

Sent from my ENG S-Off Sensation (Pipsqueak approves of this message)
[Nexus S Android Development] melvinchng:
Super boot loop on 94.

What ever emergency boot zip or set CPU voltage zip just won't let me boot. Even I stack the 11 kernel, it also freeze after every boot.

Until I stack my ROM, everything works fine now... really horrible....too low voltage I think
[Nexus S Android Development] king23adrianc:
94 boot up normally with cm7 latest nightlies

but going bak to uv11 for daily use, cuz 94 doesn't give me enough horsepower :p
[Nexus S Android Development] HareyCarey:
What quadrant is that? The one from the market looks similar but wont let me do custom benches.
[Nexus S Android Development] melvinchng:
Quadrant advanced. Google it
[Nexus S Android Development] HareyCarey:
Oh okay. Quick question, how do I manually wipe my dalvik cache? Morfic said that cw didn't do it, or didn't do it right. I have ES file explorer to manage/modify files if that makes a difference. Maybe I should get another recovery?
[Nexus S Android Development] eatTHESEbullets:
I use kd1 too. Still not working for me on 3 different roms
[Nexus S Android Development] asafru:
Thanks, will try to flash and let you guys know...
[Nexus S Android Development] lichti1901:
Anyone got teuv94 running on superosr??

It dont work for me! :confused:
[Nexus S Android Development] Babydollll:
Well, I haven't used it.. so I can't bench it....now can I?

Sent from my ENG S-Off Sensation (Pipsqueak approves of this message)
[Nexus S Android Development] simms22:
i use root explorer. you need to delete all the files in /data/dalvik-cache/ and in /cache/dalvik-cache/ then reboot immediately. go to /data/dalvik-cache/, press menu, select all, delete. the same with /cache/dalvik-cache/ then reboot or youll get many fc's. be sure to delete the files within the folder and not the folder.
[Nexus S Android Development] iamxeph:
@simms22

Any plans for more *universal* TEUV94 with slightly higher voltage?
[Nexus S Android Development] HareyCarey:
Thanks :) I may see if that is why Trinity has been a little buggy(that the cache wasn't properly wiped). I love Trinity but it seems to be fickle with the NS4Gs it seems. I am on Kushdeck's new 1.3b. Going to try T13 again.
[Nexus S Android Development] roshga:
I've been trying the new teuv94 and it's great! So smooth, fast,amazing. Thanks for the great kernel.

Btw, 3392 on quadrant :-)

Sent from my Google Nexus S
[Nexus S Android Development] eatTHESEbullets:
NO LUCK

I give up lol. Tried and tried and tried again with no luck on any of these kernels. It makes no sense to me. I am not doing anything different from when i flash matr1x or anything else. I have tried wiping from recovery, from root explorer, double wiping single wiping, not wiping, nothing seems to work. I checked to see if there were any conflicting scripts, nada. Tried three different roms, still nothing. Cant have phone on 3minutes without rebooting. Oh well. thanks anyways, I wanted to try this but I give up lol.
[Nexus S Android Development] dario3040:
Maybe your phone doesn't like it?

Mine just reboots when I use T144.