yashsingh1/xdaforums huggingface dataset:
[Nexus S Android Development] jvpde:
Morfic, is a final 4.1 kernel in the works for us? I know it was mentioned a few weeks ago but it's been radio silence ever since. Either way, thank you for your awesome work in keeping our phone fresh and have a happy new year.
[Nexus S Android Development] morfic:
I want to finish it, just keep getting sidetracked, right now I'm still in Germany, tomorrow last day before we fly home Thursday, in theory back to work Friday o_O

Not sure on that one yet.

I just won't promise a deadline this time, so i won't break it.

Happy New Year 2013 :)
[Nexus S Android Development] albundy2010:
It is very usable I agree. But it is not very smooth. Once you use a device like the nexus 4 the nexus s simply won't ever feel smooth again period.

I still use the ns every single day as a audio device. Damn I wish more OEMS would use the Wolfson audio chip. I know why the don't but man I wish they would use it anyways.
[Nexus S Android Development] lurtis:
Your kernel is really good. Only thing missing is bigmem as these nexus s phones really benefit from it in jellybean.

Thanks for everything you've done for us!
[Nexus S Android Development] skinner12:
You can't compare devices new and devices with single core of 3 years ago. I don't have n4 but I have n7 and I see the difference but I still use ns and my combo allow me to still have a great ns..

Mine is very smooth, really.. And I repeat, I have all active..

Nocerino's rulez..
[Nexus S Android Development] Wir3start3r:
Could I use this kernel with Stock 4.1.2?
[Nexus S Android Development] deani77:
Sure...
[Nexus S Android Development] morfic:
Nexus 10 uses a Wolfson chip. Which seems to be a evolution of the one you enjoy in the Nexus S, Note 2 uses the same chip as Nexus 10.

One of the reasons I'm so tempted by Note 2 (aside from soc power and screen)

Nexus 10 blew me away when it reminded me what I had been missing with regard to audio quality.

I had only listened to audio on desktop due to crappy audio quality in other devices, but I often drag my nexus 10 around with my cans plugged in.

Nexus S must make a great "Galaxy Player" :)
[Nexus S Android Development] g33kt:
Waiting for The God on Earth
[Nexus S Android Development] ReVo_007:
How good is it performing on i9023, cause last time I read about no booting and had faced the same as well.
[Nexus S Android Development] apatal:
Working well now. Take note though, the alpha builds have just the enough mods (bln & bld) and no bigmem. It's optimized though so still quite nice as ko long as you avoid too much multitasking. :)
[Nexus S Android Development] nexususer1:
Dude, you're everywhere :d

Sent from my Nexus S
[Nexus S Android Development] morfic:
Sounds like I should add bigmem before anything else.
[Nexus S Android Development] jayjay3333:
The extra MB on our Nexus sure is nice.
[Nexus S Android Development] apatal:
Is that bad? :D
[Nexus S Android Development] deani77:
+1 for bigmem. Nexus S still shortage of RAM. To reclaimed a little bit more RAM would be nice.
[Nexus S Android Development] ZeDestructor:
You should get a USB DAC (possibly DAC/Amp combo). Most people report they work fine using class drivers with USB-OTG. For that reason, internal audio quality isn't a big issue for me: it's getting piped to an external DAC+AMP combo, thus bypassing the internal DAC entirely. Well only amp as of now, I'm looking to build an AMB Gamma1/2 sometime soon...

Yup. The Nexus S has just too little RAM these days...

Dammit Google, I want my N4!!!!
[Nexus S Android Development] g33kt:
I really really can't wait!!!

Sorry for my childish enthusiasm
[Nexus S Android Development] morfic:
ok, who will help me test a new build with the MFC0 and MFC1 memory reduced to the previous amounds in ics

since i have no device to test this means you will have to test camera, video playback, anything the memory adjustments could impair.

worst case it may not even boot (less likely but could be)

I updated to the same 4.7 toolchain i'm using on the other devices right now, so if this throws out anything, that could mean the build is in the works a little while longer.

check your free memory now and after

on terminal (after su)"

there should be ~40MB inbound if this boots and runs without issues.

I don't do PM, just email me :)
[Nexus S Android Development] morfic:
I use DACs at home, but i love idea to travel light and still enjoy great music.

And yes i very much enjoyed the N10 + HD380 combo in Germany.

Adding a dac means the battery needs to feed another mouth or well, you plug in more and more, while it's an option, it's not the one i prefer :)
[Nexus S Android Development] apatal:
I'd like to test it for you. What's the email address? :)
[Nexus S Android Development] morfic:
I think i'll just link it here, saying it is untested. Simpler, this way i can fall asleep and people can grab it based on feedback ;)

And as always on xda, click my username, craaaazzzyyyyy stuff there ;)
[Nexus S Android Development] morfic:
Nexus S JB Test kernel with added bigmem, this is untested until feedback says otherwise.

http://www.derkernel.com/simms/T132-JB-BM-ALPHA0.zip

Please verify the kernel flashed and shows todays date and a 18:51 build time.

Then verify the available memory size as shown above.

Verify camera and audio/video apps/functions operate without being impaired.

Thank you for your feedback
[Nexus S Android Development] apatal:
It's booting up.

Camera is working but video crashes while trying to record.

Bigmem it is, with total RAM in app settings amounting to 394MB.

Thanks.
[Nexus S Android Development] simms22:
sweeeet :)
[Nexus S Android Development] morfic:
OK, backed off on the MFC memory reductions.

Building another one.

Someone please help an old man with his memory, what was it about needing some lib modified for this to even work on ics, obviously once the roms included that, we all forgot about it, the old men here seem to have been first to do so.

UNTESTED ALPHA0B
[Nexus S Android Development] morfic:
found something thalamus did that might help there.

building with that in it
[Nexus S Android Development] morfic:
UNTESTED ALPHA0C

This is build C of bigmem, which doesn't throw an error if more memory is requested than is there, instead it attempts to run with what is available.
[Nexus S Android Development] apatal:
Great. Downloading now..

EDIT: Good news! Video recording is working now! Playback is working too. Will report later if any other issue come up but for now. This seems to be a good one.
[Nexus S Android Development] raducux:
Great work ! Its really fast . I didn't know my phone can handle 1320 till now. Do you use stock voltages ?

Can't wait to see how a phone call goes ..because I get most reboots from oc during calls ,when hanging up. But its 7 am in my place and I have no one to call At this time .
[Nexus S Android Development] lurtis:
Morfic your a madman! Thanks a ton will let my phone sleep overnight see how it goes!

Edit: not working on bb7 test build. Seems it needs a cm kernel
[Nexus S Android Development] morfic:
I call a local bank, they announce time and temp and mention some loan deals they have for that ;P
[Nexus S Android Development] morfic:
Wait, madman? why?
[Nexus S Android Development] raducux:
I just called Vodafone's customer service and left the robot lady to talk for a minute and I had a reboot.

But then again ...my i9023 could never stay stable above 1200mhz ..with allmost any kernel I've tried... But its really smooth . I'll will follow this .thanks
[Nexus S Android Development] morfic:
1320 is just a popular speed, this is a single build, just to test out adding bigmem, since i no longer have a nexus s, anything happening to this kernel will be through community testing (as simms22 who had been continuing his testing on nexus s lost his NS to Sandy)

long story short, if bigmem reaches a point where video recording works i'll build a full set of speeds, 3 of which should suit your device.

This is more of a end of life slow approach for people who have been around a long time and there will be no new and dramatic developments.

Just delivering few more promised builds really.

Since you said you are subscribing i figured i give you a little more background vs trying to make sense of all the old old posts :)
[Nexus S Android Development] jvpde:
Video recording and playback are working fine for me. My phone won't do 1.32 so unfortunately, I can't test OC.
[Nexus S Android Development] morfic:
building lower speeds now.
[Nexus S Android Development] lurtis:
Because within one day I come back and I see 3 or so new test builds. :) I'm happy. Always loved your kernels and now with bigmem its the defacto kernel for my jb.

Once I go back to rasbean after my testing of a ROM it will for sure be with your kernel.
[Nexus S Android Development] morfic:
3 builds is like 15 minutes, takes longer to upload and wait for feedback, that's why i prefer to own devices i work on.

Just glad there are still people who are happy to see this old thing ;)
[Nexus S Android Development] morfic:
http://www.derkernel.com/simms/T144-JB-BM-ALPHA0c.zip 1440MHz cpu, 240MHz gpu

http://www.derkernel.com/simms/T132-JB-BM-ALPHA0c.zip 1320MHz cpu, 220MHz gpu

http://www.derkernel.com/simms/T12-JB-BM-ALPHA0c.zip 1200MHz cpu, 200mhz gpu ("stockiest")

http://www.derkernel.com/simms/T11-JB-BM-ALPHA0c.zip 1100MHz cpu, 220MHz gpu

http://www.derkernel.com/simms/TEUV-JB-BM-ALPHA0c.zip 880MHz cpu, 220MHz gpu
[Nexus S Android Development] morfic:
Ok, that's all of them, someone bored please test the rest of them, to make sure all labels match the kernel's max freq.

If everyone is happy i will move them to the public part of the site, for now I'll leave them in above post.
[Nexus S Android Development] jvpde:
T11 and T132 report +1332 kB MemTotal coming from Matr1x kernel. Video recording and playback works on both. 1.1GHz didn't lock immediately :p
[Nexus S Android Development] morfic:
you got 1+MB more than on Matr1x you mean?
[Nexus S Android Development] jvpde:
Assuming I'm reading the output correctly, yes.
[Nexus S Android Development] morfic:
nice :) 1MB! ;P
[Nexus S Android Development] apatal:
Why won't that terminal command work on my setup? I always get this weird error.
[Nexus S Android Development] morfic:
Fix your busybox install
[Nexus S Android Development] apatal:
What do you mean? I installed busybox in xbin. Is that wrong? Or should I just update?
[Nexus S Android Development] leap_ahead:
cool morfic..can you add crt fix pls ?"
[Nexus S Android Development] apatal:
Never mind. Looks like it's busybox that is to blame. Using T11 with no issues so far. BTW, any reason y u no voodoo sound anymore? ;)
[Nexus S Android Development] n2d551:
Man, starting to flash this and you stopped me dead in my tracks with the no voodoo.
[Nexus S Android Development] apatal:
Yeah too bad. I even tried installing the module via the paid app in the Play Store. Still no luck. Says the kernel doesn't support it. :(
[Nexus S Android Development] dinuvali:
Man, starting to flash this and you stopped me dead in my tracks with the no CM IOCTL support :)
[Nexus S Android Development] wmdunn:
Morfic ... thanks for hanging in there with our Nexus S group. Really appreciate you taking the time to give us one last update.
[Nexus S Android Development] kwibis:
Running fine on 1.1!

Sent from my Nexus S
[Nexus S Android Development] Highway 55:
Do these have the Bluetooth sleep fix? Not a big deal, just curious...
[Nexus S Android Development] lurtis:
Test and let us know!
[Nexus S Android Development] cdpango:
both running on 1320 MHz, Trinity scores around 3800 on my phone, but Matr1x scores around 4500 with a higher GPU score. However Matr1x occasionally reboots, and Trinity never.
[Nexus S Android Development] morfic:
That's at 1320/1320?
[Nexus S Android Development] morfic:
Why no voodoo?

Because it wasn't added yet. ;)

NS update got pushed back and pushed back and.... Pushed back.

I'll add most things back in, I'll update things before I let it slumber again, once all the usual suspects are back in it shouldn't need much updating.

Now who can tell me if the cm ioctl change means I need to build 2 kernels or not?

Not a fan of building cm kernels just because they have to break things.

Adding something they need but doesn't affect aosp would be an entirely different story.
[Nexus S Android Development] lurtis:
From what I can tell adding the cm changes effect only the 4.1 ROMs.

Example: matr1x cm kernel works on rasbean 4.2 but not 4.1.2. I'm almost positive this wasn't intended but some fluke that happened with 4.2+. BUT non cm matr1x does not work with cm based ROMs whatsoever whether it be 4.1.2 or 4.2.

Cannot say if cm matr1x works on other aosp 4.2 ROMs as rasbean is pretty much the only stable aosp 4.2 ROM for the nexus s 4g at the moment. All others appear to be cm/aokp based.

I can understand why you would be hesitant to create two kernels as IMO it does seem redundant.

However our phone is pretty old and development has slown down a ton over the last two months and it seems the only updates we get now are the cm nightlys and kangs of that which are all 4.2+ nowadays. Even aokp has pulled support.

At least that's what I see on the crespo4g side of things... Crespo may be different though I rarely visit their dev forum anymore.

Hope that clears some ish up for you and can help you make a decision. Either way its good to see one last hurrah for the crespo phones.
[Nexus S Android Development] skinner12:
Re: [DER KERNEL] NS+4G Trinity (E)UV and OC CM9 + m(any) roms

TriNitY colors are amazing..

Nocerino's Rulez with RAScarlo's ROM features TriNitY ;)
[Nexus S Android Development] Jamalsid:
Re: [DER KERNEL] NS+4G Trinity (E)UV and OC CM9 + m(any) roms

The cm versions of the Marmite kernel by bedalus works on both cm and rasbeanjelly.
[Nexus S Android Development] wmdunn:
Earlier in this thread, this was discussed ... http://xdaforums.com/showpost.php?p=35456252&postcount=14400

When I use Slimbean 4.1.2, which is CM based, and a Trinity kernel ... I just flash the fix. Everything is working great on the new kernels with this setup.
[Nexus S Android Development] lurtis:
Re: [DER KERNEL] NS+4G Trinity (E)UV and OC CM9 + m(any) roms

Very very clever! With that black screen fix I got the latest teuv test to boot on bb7. Damn I've missed trinity colors! Thanks a ton
[Nexus S Android Development] deani77:
Re: [DER KERNEL] NS+4G Trinity (E)UV and OC CM9 + m(any) roms

Working fine with latest CM10 Nightlies. Tested camera and video recording working fine. Using T11
[Nexus S Android Development] cdpango:
Re: [DER KERNEL] NS+4G Trinity (E)UV and OC CM9 + m(any) roms

on both kernels I just set the maximum frequency to 1320 using NSTools, the minimum is not changed.

The CPU scores are both around 1100, the GPU score for matr1x is around 2000,and Trinity 1400.
[Nexus S Android Development] wmdunn:
You're welcome, Bud ... glad I could help.
[Nexus S Android Development] morfic:
EDIT: See below why i just edited this out.
[Nexus S Android Development] morfic:
This is ingenious. sorry, i prefer this a whole lot more than to include a patch just for cm.
[Nexus S Android Development] morfic:
now i just need the zip to upload and link from OP and man do i need to update that topic
[Nexus S Android Development] lurtis:
Right here http://www.mediafire.com/?z95kab6v5p4dxl9
[Nexus S Android Development] morfic:
Thanks, added to OP, and who did you say should get credit for the zip?
[Nexus S Android Development] lurtis:
JackpotClavin posted it. No idea if he made it though.
[Nexus S Android Development] morfic:
Thanks, OP updated
[Nexus S Android Development] anshumandash:
I think he said has built it.
[Nexus S Android Development] skinner12:
That fix is for who get very dark screen and close to green?

Because with 4.2.1 sometimes I have to reboot cause my colors are weird..

Nocerino's Rulez with RAScarlo's ROM features TriNitY ;)
[Nexus S Android Development] Highway 55:
I think that fix is for flashing AOSP kernels on CM 10.1. Flashing Trinity would result in a blank screen, no boot animation or anything.

The issue you are talking about is completely different. I have that problem as well. Sometimes it happens 3-4 times per day sometimes I can go 3-4 days without it happening....
[Nexus S Android Development] lurtis:
The new teuv idles like a champ haha.
[Nexus S Android Development] skinner12:
I guess mine too..

Nocerino's Rulez with RAScarlo's ROM features TriNitY ;)
[Nexus S Android Development] siddhesh.raikar:
Can't set min frequency to 100.. Tried fixing permission. All versions..

Other than that. All smooth.. :)
[Nexus S Android Development] lurtis:
I've had that problem on a few kernels. The trick is to use an init.d script. You just need to set your max frequency in the script. And not set a minimum frequency. Then using CPU spy you should see your 100 MHz being used. If you open nstools though it'll set it back too 200. So put your bln/bld settings in that init.d script as well.
[Nexus S Android Development] Drizzzle01:
Do you happen to have a copy of that script along with instructions on how to implement?
[Nexus S Android Development] jwee5467:
Just use NS tools bro
[Nexus S Android Development] lurtis:
Here my simple init.d script i made using nstools. It sets max frequency too 1000 MHz max / min to 100 MHz. No bln. Bld set to 2 seconds. OnDemand/deadline with a couple changes too the governer.

#!/system/bin/sh
echo 1 > /sys/class/misc/backlightdimmer/enabled
echo 2000 > /sys/class/misc/backlightdimmer/delay
echo 0 > /sys/class/misc/backlightnotification/enabled
echo 0 > /sys/class/misc/backlightnotification/in_kernel_blink
echo 0 > /sys/class/misc/touchwake/enabled
echo 45000 > /sys/class/misc/touchwake/delay
echo ondemand > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
echo 20000 > /sys/devices/system/cpu/cpufreq/ondemand/sampling_rate
echo 95 > /sys/devices/system/cpu/cpufreq/ondemand/up_threshold
echo 1 > /sys/devices/system/cpu/cpufreq/ondemand/sampling_down_factor
echo 0 > /sys/devices/system/cpu/cpufreq/ondemand/powersave_bias
echo deadline > /sys/block/mtdblock4/queue/scheduler
echo deadline > /sys/block/mmcblk0/queue/scheduler
echo 100 > /sys/class/misc/liveoc/oc_value
echo 1000000 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq

You have to put it in your system/etc/init.d folder and set permissions to rwx-rwx-rwx

Also, your ROM has to support init.d scripts. Rasbeanjelly does not by default although you can add it by using Pimp my ROM from the play store.

Its designed to work with the latest T12 test kernel a few pages back. But doesn't OC at all.
[Nexus S Android Development] :
are the beautiful trinity colors in the test kernel?
[Nexus S Android Development] wmdunn:
Yes ...
[Nexus S Android Development] HeavenlyWinds:
Great kernel OP thanks.
[Nexus S Android Development] lurtis:
Running an old gb build of this kernel currently and it's flawless thanks for the years morfic
[Nexus S Android Development] deani77:
Paired well with Xylon ROM. Using T11 alphac. Any other test kernel or we will go for stable Morfic...
[Nexus S Android Development] lurtis:
Re: [ROM][4.2.1] RasbeanJelly 2/3/13

Latest Trinity kernel alphas here in case anyone missed them... Running the TEUV version myself without hiccups.
[Nexus S Android Development] morfic:
Guess it's time to move them public. Long over due.
[Nexus S Android Development] lurtis:
If you ever make any more builds just add voodoo sound options and call it a wrap ;)
[Nexus S Android Development] Wir3start3r:
rasbeanjelly (4.2.1) and "http://www.derkernel.com/simms/TEUV-JB-BM-ALPHA0c.zip" 880MHz cpu, 220MHz gpu do they work together respectively is this a good combination?
[Nexus S Android Development] leap_ahead:
This kernel have bt fix for 4.2.1 rom?
[Nexus S Android Development] morfic:
[morfic@bors ~]$ mv public_html/simms/T*-JB-BM-ALPHA0c.zip public_html/JBNS/prev/

What you see now on the site is just what was linked inline in thread before

I Think they got enough testing to know they are ok.

So they are not new new for most who already got them off of the simms/ links before.
[Nexus S Android Development] lurtis:
Yeah I'm still running teuv. Been over a week now I think and my phones been awesome. Haven't had to reboot yet for any reason
[Nexus S Android Development] siddhesh.raikar:
Hey.. Awesome kernel..

Can you please add the CRT animation fix and the 100mhz frequency fix?? It doesn't stick sometimes..

The kernel is still good to go without these.. :)
[Nexus S Android Development] 309041291a:
No more Trinity for my NS :(. I can't even get into bootloader now. And ignore the Instagram filter. Luckily I'm on my N4 with Trinity :D! It's an honour to say my Nexus S died in the Trinity

Sent from my Trinity powered Nexus 4
[Nexus S Android Development] morfic:
Ouch

Rest in Pieces
[Nexus S Android Development] 309041291a:
Literally

I was using it as an alarm clock on my high shelf. Short story, it vibrated and fell to its death

Sent from my Trinity powered Nexus 4
[Nexus S Android Development] nibla101:
You murderer :(
[Nexus S Android Development] kwibis:
Morfic is it possible to adjust voltages with the trinity app? I found out my phone needs a bit more juice to run 1320 mhz, so would love to try :D or is there any other way?

Sent from my Nexus S
[Nexus S Android Development] ZeDestructor:
No. You have a perfectly usable non-instagram camera. USE IT!

Other than that, RIP NS.
[Nexus S Android Development] JerryPi:
Hy all, i have tested the recent teuv kernel on the latest cm10.1 nightly. With my metawatch connected via bluetooth i get very high android os awake time.

I seem to recall that other kernel devs included some fixes to remedy this issue :cool:
[Nexus S Android Development] leap_ahead:
because this not include bt fix for 4.2.1 rom
[Nexus S Android Development] havlaz:
after "just flash" doesnt work, i did what you said, wipe data, wipe cache, flashed rom (miui 2.6.29 ics) then flashed T132 kernel , then pulled the battery off for 2 minutes, then boot the phone, and its stuck on google logo.
[Nexus S Android Development] polobunny:
Which one did you flash exactly?

T132-NS-CV-56HZ-ANY-201212623?

Because that's the one you need to flash if you're on ICS.
[Nexus S Android Development] havlaz:
T132-NS-CV-56HZ-ANY-201212623 yep

i flashed the rom and the kernel again and it boots file with the trinity logo.

but in "about" i see 1000mhz and not 1320

is it ok?
[Nexus S Android Development] polobunny:
Yes I believe that is normal, if I'm not mistaken it boots at 1000Mhz so that's why it is reported like that in about.

Check with CPUSpy to see if the 1320MHz state is being used properly. It should.
[Nexus S Android Development] havlaz:
afer one reboot i cant get into "about" even.. FC every time
[Nexus S Android Development] polobunny:
Then your phone can't handle the overclock.
[Nexus S Android Development] cdpango:
have been using T132 alpha0c since its release without any problem, only really missing voodoo sound. Anyway chance to add that, morfic? Thanks!
[Nexus S Android Development] morfic:
Yes, there is a chance, just don't know when.

Still working on a lot of things, nexus s usually waits until I have no pressing issues elsewhere.

Glad this still works for y'all :)

Then I'll keep at it.
[Nexus S Android Development] jojoost:
T12 is the smoothest android 4.2 kernel I've ever tried!! Thanks for that!
[Nexus S Android Development] leap_ahead:
bluetooth deep sleep ?
[Nexus S Android Development] JerryPi:
The latest batch of kernels has high android os use if you use bluetooth on 4.2+ roms:-\
[Nexus S Android Development] jojoost:
I never use bluetooth
[Nexus S Android Development] kancrutt:
anyone have latest Rasbeanjelly (4.1.2) from Rascarlo?
[Nexus S Android Development] leap_ahead:
http://xdaforums.com/showpost.php?p=35184087&postcount=14391
[Nexus S Android Development] migueldbr:
And anyone with the last 4.1.1 rasbean?