yashsingh1/xdaforums huggingface dataset:
[Nexus S Android Development] barqers:
That's weird I don't get any issues on the newest TEUV kernel with the 4-way reboot. All have been working for me!
[Nexus S Android Development] morfic:
Moved the TUV 12092011 to OP.

If you grabbed it from simms22's link, no need to regrab, everyone else, grab it

new ezekeel patches included in next release
[Nexus S Android Development] saranyan:
Can someone gimme a link for the TUV 10 kernel since its not in the OP. Having issues with the latest tuv11 :(
[Nexus S Android Development] simms22:
try the tuv that was updated in the op a few minutes ago.

tuv10 is dead, unless you can find a necromancer..
[Nexus S Android Development] cheech87:
Is the only change between 1109 and 1209 the voltages in the voltage.h file? Having some trouble with 1209, whereas 1109 ran flawless. So I find it hard to believe that the only change is a slight voltage increase.
[Nexus S Android Development] simms22:
yes sir. slight bump in voltage. use 11/09. every phone is different.
[Nexus S Android Development] cheech87:
Yeah, restored back. But in my experience, if my phone can handle a certain UV setting, then it can usually handle any uv closer to stock voltages as well. And shouldn't be so finicky wrt slight changes in a conservative direction.

Maybe I'm too stubborn, but wont be 100% convinced until Morfic posts the changes to his euroskank git.

Still loving tuv-1109 and can see this being my daily driver for some time.
[Nexus S Android Development] gotjazz:
For me too 1109 runs great. I don't need more voltage and I don't use any of the dimmers either. So I guess I can skip this one. On the other hand...... I'm kinda itching to flash something :)
[Nexus S Android Development] saranyan:
Okay, I'll try. thanks. :)
[Nexus S Android Development] morfic:
Then you have a problem.

I checked git log.

That one commit is a few days worth of changes including ezekeel patches.

I'll push it when I get home, so you can see it.

EDIT: ok, working on 3 kernels at once i got timeline wrong, 1109 already had the bump, 1209 had a extra settle time for TUV, not the other kernels.

1109 was long committed, 1209 i pushed right now.
[Nexus S Android Development] morfic:
morfic@othris:~/NSDEV/samsung$ git commit -a

[testing 68d3b33] settle UV with more time than others, possibly this will be unconditional later

1 files changed, 5 insertions(+), 5 deletions(-)

morfic@othris:~/NSDEV/samsung$ git push

morfic@morfic.euroskank.com's password:

Counting objects: 11, done.

Delta compression using up to 6 threads.

Compressing objects: 100% (6/6), done.

Writing objects: 100% (6/6), 569 bytes, done.

Total 6 (delta 5), reused 0 (delta 0)

To ssh://morfic@morfic.euroskank.com/home/morfic/morfic.euroskank.com/git/linux-samsung.git

3064b34..68d3b33 testing -> testing

morfic@othris:~/NSDEV/samsung$
[Nexus S Android Development] king23adrianc:
so should i choose 1209 over 1109 if i m running 1109 quite smooth?
[Nexus S Android Development] morfic:
If you want to let me know if you concur with cheech that 1209 is iffy, while 1109 ran, sure.

Else there is nothing for you to gain yet.
[Nexus S Android Development] cheech87:
yeah, i see the 1209 commit now. Hard to argue that change is the sole source of the issue I'm having and wouldn't be surprised if it's just my phone that doesn't like it.

If it helps, I get lock ups on boot when the lockscreen comes up (more likely) or within the first minute of getting control of the launcher (less likely). cm7-N180. I guess keep an eye out for similar symptoms before reverting.
[Nexus S Android Development] Bamdroid:
I just got 2 reboots on the newest TUV. All I did was plug in my charger. O_o like within mins of the 1st reboot.

But I'm a trooper. Still rockin it. FTW.

私のネクサスSから送ら
[Nexus S Android Development] Bamdroid:
110911 TUV runs better for me. Noticed a difference in the transitions switching homescreens immediately. (After reverting back to 110911).

私のネクサスSから送ら
[Nexus S Android Development] brainmaster:
That makes me a necromancer, since the dead TUV10 can be found in the second post of my MIUI ROM Thread.

I can confirm that. The latest TUV gives me random reboots when connected to charger.

@ morfic - it seems like there are issues with Ezekeels patched and non-i9020 devices, since I can't run them on my i9023 and other users are also reporting random reboots since the Ezekeels stuff is integrated in your kernels.

You already mentioned that you could provide two kernel versions - one with and one without Ezekeels patches. Are you gonna do that?

I believe that this is important, since there are users like me that don't use that stuff and we love your kernels, but have random issues when those patches are integrated.
[Nexus S Android Development] simms22:
:eek:
[Nexus S Android Development] bringonblink:
beat me to it, was gonna dropbox it

Sent from my Google Sexus S
[Nexus S Android Development] morfic:
http://goo.gl/u52dZ TUV 14092011, a test build without dimmers

there were enough changes going on aside dimmers, that any issues people encounter do not in any way have to relate to dimmers.

Anyone rebooting on charger, please give info about charger.

Like: charging on PC, charging on AC walwart (for usb cables or hardwired connector),

max amps of charger

Oh yeah, Oppenheimer says "Hello"
[Nexus S Android Development] DrSpanky:
I'm using an I9020 with the CM7 Kang from Sunday and I'm getting the same thing. It seems to run fine for an hour or two without being plugged in and using Pandora, but it reboots about every 10-15 minutes when plugged in using Pandora.
[Nexus S Android Development] kecinzer:
morfic:

Do you plan add dimmers back in future releases? I use to it for this mods and I don't want to loose it.
[Nexus S Android Development] morfic:
This would be an alternative build for purists.

I will add the other proximity patch for the dimmers into the other build.
[Nexus S Android Development] Bamdroid:
It was the AC charger. Just plugged in, everything froze then rebooted. Maybe 3 mins after everything booted up it rebooted again. No issues like that on 911 version.

私のネクサスSから送ら
[Nexus S Android Development] brainmaster:
For me it was on both - AC Charger and connected to Laptop.
[Nexus S Android Development] DrSpanky:
So far it only reboots when I'm using speakers or headphones. It's rebooted with Pandora, Google Music, and MoboPlayer. They run fine while charging and not charging for 15-20 minutes each, but within 5 minutes of plugging the speakers or headphones in it will freeze and reboot. I know this isn't much time, but I'll keep trying to find things to crash it consistently. Oh and it's being charged by USB to my computer during all of this.

Is there a certain set of voodoo settings I should be using?
[Nexus S Android Development] brainmaster:
The TUV 14.09 without Ezekeels patches gave me reboot when plugged into Laptop.
[Nexus S Android Development] alf69mi:
I've always had reboots during normal use,

never noticed a reboot when plugged to AC, i had reboots also on 0912 with 'slightly' increased voltages. Trying now 0914, i don't use Ezeekel's patches, 95dimmers script is still present, is it safe to delete? 10x
[Nexus S Android Development] melvinchng:
Night mare are back! The boot sound.. :'(

140911 tuv11 freeze after installed for 30minutes while I was in running service tab

Edit. Back to 1109 kernel.. 1409 freeze for me.

Accidentally sent from my Nexus S using XDA Premium App
[Nexus S Android Development] DrSpanky:
I couldn't get it to freeze with Google Music or MoboPlayer anymore, but Pandora got it to freeze almost instantly with and without the headphones. It was charging with the PC during both, and now it's freezing and rebooting at the first lock screen for 6 times in a row, but finally got past it on the 7th. The first 2 of those 6 were charging and the last 4 were not.

I ran 5 Quadrants in a row without any problems. Then, to see what kind of score I could get I put the min and max to 1100 and it froze on the stairs part. It wasn't charging during this.

tl dr; I can't find any pattern other than Pandora that crashes it quickly and consistently.
[Nexus S Android Development] alf69mi:
TUV1409 constantly rebooting, i was able to collect last_kmsg.

Sent to morfic, hope he will get it.

[ 5.711338] warning: `rild' uses 32-bit capabilities (legacy support in use)
[ 6.614917] [MODEM] modem_reset()
[ 6.945330] modemctl_ioctl() 0
[ 7.925620] Unable to handle kernel NULL pointer dereference at virtual address 00000000
[ 7.925743] pgd = c0004000
[ 7.925801] [00000000] *pgd=00000000
[ 7.925915] Internal error: Oops: 817 [#1] PREEMPT
[ 7.926020] last sysfs file: /sys/power/state
...
...
[ 7.985817] Backtrace: frame pointer underflow
[ 7.986033] Code: e2460018 e590301c e5902018 e5823004 (e5832000)
[ 7.986132] ---[ end trace 52de60a603ea8fe7 ]---
[ 7.986240] Kernel panic - not syncing: Fatal exception
[ 7.986298] Backtrace:
[ 7.986411] Rebooting in 5 seconds..
[Nexus S Android Development] ellesshoo:
+1. First thing I do after downloading is extract the zip and delete dimmers & poweron audio (I know it's opt-in now) , and replace boot animation. Wish dimmers was opt -in, I'd venture to guess most people don't want or have a use for them and 1st time trinity users probably freek out after flashing if they weren't expecting them. Just a lot of posts about them by people who want them bc people have issues with the settings.
[Nexus S Android Development] saranyan:
Tried the latest TUV11, Had two reboots in like 4 hours. :(
[Nexus S Android Development] Roscopcoletrain:
I flashed the older TUV 1109 and its been great! I was having reboot and that off colour bootanimation reboots on the latest cm7 nightly but since flashing this yestderday, Ive yet to have one. Maybe it was the Dalvik wipe? Either way Im happy :)
[Nexus S Android Development] ZeDestructor:
Been running the new T15 kernels from simms22-land. Runs cooler and (probably consequently) is more stable than T144. Never expected a mere 40Mhz boost in Bus would cause that much extra heat.... IMO T15 with 200Mhx bus is better than than T144 with 240MHz since general usage is smoother (I don't play games on my phone).

For everyone complaining about Ezekeel's scripts: I have no issues on my i9023. granted, I haven't activated them at all, but still...

kernel in question: T1552-Any-NS+4G-11092011
[Nexus S Android Development] bringonblink:
Question for the super nerds here.

I like trinity kernel but i like setting my own UV voltages.

Now i know morfic said he wont implement it ever, so im wondering.... how difficult is it to implement it myself?
[Nexus S Android Development] endursa:
hmm i don't know but i feel like the TUV144 kernel with ghz cap to 1ghz feels like it needs more battery than standard nexus kernel, could it be?
[Nexus S Android Development] DrSpanky:
As far as I know, the bus is still clocked to 240mhz instead of the stock 200mhz even when the CPU is set to 1ghz.
[Nexus S Android Development] endursa:
ah ok that could be the problem, my battery draind from 95 to 15 today in about 8 hours with 20min music and about 2h of display and wifi on!
[Nexus S Android Development] Naa Laa:
I am having issues (doesn't reboot - will have to remove the battery to restart) with the 4-way reboot using TEUV kernel (080911 version). First, I thought it was the ROM (MIUI 1.9.9) causing it but after reading some of the post here maybe its the kernel.

Usually, when the phone is connected to the charger normal reboot option does not work properly but when the phone is not connected to the charger it works fine.
[Nexus S Android Development] dario3040:
I think it's only 240 at 1.44 Ghz

Also, 1440 / 6 = 240
[Nexus S Android Development] asdfghjkl:
Has anyone been getting a green screen when the screen dims? If I don't touch it, it will dim before lockscreen and today it started looking green....on MIUI 1.9.9. Any suggestions? I already deleted the 95dimmers...
[Nexus S Android Development] gotjazz:
And rebooted afterwards?
[Nexus S Android Development] Bamdroid:
I'm not sure what's going on for I've NEVER had any issues using Trinity. I just heard Oppenheimer 4x since flashing the latest 140911 TUV. Going back to 911 version again...

私のネクサスSから送ら
[Nexus S Android Development] morfic:
thanks for the reply, if you flashed what semeon linked earlier, delete the file

there is a "c" version that is slightly better, but not perfect

i'm working on it, until you see some big (probably typical silly) announcement regarding TUV being healed, consider it sick and stick with the ones that are healthy as a horse

test kernels below:

http://morfic.euroskank.com/simka/TUV-Any-P2C-HIF-NS+4G-14092011c.zip (not cured yet)

http://morfic.euroskank.com/simka/TEUV-Any-P2C-HIF-NS+4G-14092011.zip (healthy as a horse)

using the old cooler colors (cool as in white balance cool, aka "blueish) and a tiny change to the battery is full at x% define)
[Nexus S Android Development] kecinzer:
Thanks. So in latest TEUV are all ezekeel mods included? I'm now on TEUV from first post and have 100% stability, speed and hell good battery life with all ezekeel mods :)
[Nexus S Android Development] simms22:
most wont know who semeon is.. semeon is me btw :D
[Nexus S Android Development] khartaras:
Haven't tried TUV 14/9, but I can confirm TUV 12/9 is not as fast as TUV 11/9. Only getting 4000 on Quadrant with TUV 12/9, while I got 4200 on TUV 11/9
[Nexus S Android Development] Ezekeel:
Lemme guess. You set it from 95 to 100 expecting it will now charge the battery to 100%?

Spoiler: No it won't. Already tried that some time ago. ;)

The reason is that changing this value only changes how the charge state of the battery is reported to the kernel. The MAXIM max8998 chip which handles the charging of the battery does not care for this, because it monitors the charge state either by directly communicating with the battery or by some internal measure. As soon as the max8998 decides that the battery is fully charged it triggers an interrupt which then causes the kernel to send a signal to that chip to end the charging process. It you want to make sure that the battery is actually charged to 100% it might work to test for this and ignore the interrupt if the charge state is still below 100% (http://www.pastie.org/2533594). I have not tried it, so this might not work at all, crash your device or explode your battery.
[Nexus S Android Development] kecinzer:
I hope, that I finaly see 100% battery on my Nexus :)
[Nexus S Android Development] simms22:
i can confirm, it didnt work on my phone. stopped at 96%, so im charging it with screen on the rest of the way to 100%.
[Nexus S Android Development] dario3040:
I knew that
[Nexus S Android Development] king23adrianc:
damn! but i guess i will still flash the TUV b anyway just for fun :p
[Nexus S Android Development] kecinzer:
When we are in this mods... Is there any way how to do 2 way call recording? When I had HTC Desire, there were kernels that allow this. But I don't know if this even possible with Nexus S.
[Nexus S Android Development] asdfghjkl:
Yup. Rebooted and nothing. Wiped dalvik and cache (not necessary) and nothing lol I'll flash the new "healthy as a horse" one from 9/14 and see if its better.

Edit: So the new one is working fine...no green screen dim but im going to wait and see. The previous TEUV "treat" worked fine for 2 days and all of a sudden went green today :/
[Nexus S Android Development] king23adrianc:
do we need to install voodoo for the colour change?
[Nexus S Android Development] simms22:
what rom are you using? because this can be a rom issue. cm is know to have this happen to it occasionally, and ive heard this happens with miui occasionally as well, without running trinity.
[Nexus S Android Development] morfic:
I didn't fully expect it to be that easy

i came across it looking for the ac charger vs usb charger stuff

but since the reboots since happened unplugged, i have not looked at either

no, i didn't look at how the code uses it, just interesting how the number matches most people's "charged" state, that's all

i'm headed to work, so there will not be new versions until tomorrow
[Nexus S Android Development] khartaras:
MIUI is CM-based, so it's expected to have the same bugs as CM.
[Nexus S Android Development] alf69mi:
Install Voodo Control app then go to

Color Profiles and choose "Original <2.3.3"
[Nexus S Android Development] king23adrianc:
do u mean voodoo profile v1 ?

cuz original doesn't change anything
[Nexus S Android Development] ellesshoo:
2 reboots and 2 lock ups today on tuv11. All occurred while connected to power. Once connected to AC, the others on car charger (DC to USB). Unplugged has been okay for now.
[Nexus S Android Development] alf69mi:
Yes 'Original <2.3.3'

but you need the SAmoled I9020, i think the SLCD version won't work.

In I9020 when you switch from 'Voodo profile v1 <2.3.3' to 'Original <2.3.3' you will see red in the darker grey at the left (this is why Google fixed it >2.3.3)
[Nexus S Android Development] king23adrianc:
i have 9020

probably i didn't use <2.3.3 colour for a long time

kinda got use to >2.3.3 LOL

so the red in darker area is correct right?
[Nexus S Android Development] alf69mi:
Yep, is the 'problem' Google fixed >2.3.3

The original tint showed red in the darker areas of images, to fix it Google had to change the color profile to a warmer (yellowish) one.
[Nexus S Android Development] king23adrianc:
alright!! gonna try now :)
[Nexus S Android Development] Bamdroid:
Mucho grassy ass..downloading n flashing now..

私のネクサスSから送ら
[Nexus S Android Development] king23adrianc:
woww now there is version C , reflashing again LOL
[Nexus S Android Development] asdfghjkl:
Yup MIUI lol I guess il just stick it out. It just bothers me when i look at it...
[Nexus S Android Development] Bamdroid:
Now I feel like a noob. The colors are all funky lookin. If I go to voodoo 5.1 its semi gray but original gives me a red tint? I also don't have the options to set my own color settings (which were awesome if I might toot my own horn bwahaaa).

Used healthy as a horse option.

**edit** ok..now the red tint just magically disappeared? Did I miss something? Kinda fixed itself after my 1st post, so maybe 6-10 mins later. The red tint now looks gray..perfect actually.

私のネクサスSから送ら
[Nexus S Android Development] Bamdroid:
Damn necromancers and triple sixes.. black magic I tell ya! :)

私のネクサスSから送ら
[Nexus S Android Development] morfic:
Boot up, look at the colors.

Turn off screen, turn on screen.

Look at colors again.

This is voodoo color v1, not adjustable.

Maybe I can merge the code with the white balance table later. No promises.

Sent from my Trinity G2x
[Nexus S Android Development] Bamdroid:
Well normally I'll let the phone go to sleep after it boots up before I access anything (just to give things time to load). That was just a weird 'thing' that happened I suppose. Seems ok now. (My mms are back to being compressed to 1kb I noticed). Not sure if that's a kernel thing or something else. Wasn't doing it on TUV10 or TUEV88. Outside of that, things are cherry so far. Thanks for your continuous hard work n black magic. Bwahaa...

Actually think I'm gonna stick with TUV 110911...like it the best personally..

私のネクサスSから送ら
[Nexus S Android Development] morfic:
Try TUV 100/800 please.

Have a few thoughts but need more data.

Since I can't build until after work, data collecting here is all I can do.

Thanks in advance
[Nexus S Android Development] Bamdroid:
Which one? (TUV)

私のネクサスSから送ら
[Nexus S Android Development] morfic:
Today's 'c' TUV, linked a few posts up.
[Nexus S Android Development] Bamdroid:
Ah.. I used the healthy one earlier (just caught it was TUEV). Trying now..

私のネクサスSから送ら
[Nexus S Android Development] Bamdroid:
Everything's cherry still..no issues rebooting or anything on version C.

私のネクサスSから送ら
[Nexus S Android Development] morfic:
100/800 or 100/1100?
[Nexus S Android Development] ragnarokx:
I'm using an older MIUI edition kernel. Has the error when rebooting with WiFi on been fixed in the newer kernel versions?
[Nexus S Android Development] Bamdroid:
100/1100 for now lol..

私のネクサスSから送ら
[Nexus S Android Development] simms22:
completely unrelated to anything except crApple.. lmao!
[Nexus S Android Development] tehgeekguy:
simms.... that is AWESOME! :-D
[Nexus S Android Development] Bamdroid:
Hmmm...plugged in charger n Oppenheimer scared the **** outta me n my cat! Lmao.. 2 reboots. Gotta go back to the 9/11 version. Just no issues with that one..

私のネクサスSから送ら
[Nexus S Android Development] simms22:
i went all night and morning without reboots on this test version of TUV, and i put this one through a lot of abuse.. and i do mean a lot of abuse http://goo.gl/1whUv

test it out, give us some feedback :D
[Nexus S Android Development] king23adrianc:
LOL i totally forgot oppenheimer is back

and guess what... i flashed it in my lecture :o

then i pretend nothing happens... turn my head left and right and pretend the sound was from others :p
[Nexus S Android Development] endursa:
Is this with or without backlight dimmer? I can't use a kernel without it anymore :-D

And btw are the 1.5 ghz kernels going to be supported or where they just test kernels?!

Sent from my Google Nexus S
[Nexus S Android Development] eduke:
same here ... solid as a rock.

I went to bike with fear of losing the 'bike path' (Endomondo) ... but no. Very good! :D
[Nexus S Android Development] Roscopcoletrain:
scared to change...been so good on the 1109 build lol
[Nexus S Android Development] simms22:
this is without ezekeels mods. the 1.5 kernels.. test kernel, but theyll always be around ;)
[Nexus S Android Development] gotjazz:
Same here. Although 1109 seems to draw a bit more battery than previous versions
[Nexus S Android Development] Bamdroid:
Are you referring to the test TUV Simms posted 24 mins before your post, or the ones from yesterday that you had no issues n put thru abuse?

私のネクサスSから送ら
[Nexus S Android Development] Bamdroid:
Thanks..flashing now.

私のネクサスSから送ら
[Nexus S Android Development] eduke:
the one from yesterday of course, that put morfic ... are the same...
[Nexus S Android Development] simms22:
not the same. this one i posted earlier is different.
[Nexus S Android Development] eduke:
I misunderstood the message ... sorry

..ops... and the date? :cool: well, I'll try...

...back to yesterday, posted by morfic ... three reboots in a minute ...
[Nexus S Android Development] thedudejdog:
Been using it since you posted it, no problems yet. Normal usage
[Nexus S Android Development] Bamdroid:
After flashing (no wipe just flashed kang/new test kernel) got 2 reboots back to back from checking LPP twitter widget. Now I've wiped cache/dalvik, powered off, pulled battery n waited a couple mins n booted up. Testing now...

私のネクサスSから送ら
[Nexus S Android Development] JmPTaz09:
This kernel "http://goo.gl/1whUv", test kernel posted by Simms, is running great so far w/no freezing. I am one who has had a lot of freezing with recent TUV kernels; will see how this one fares.
[Nexus S Android Development] Bamdroid:
Frickin ****ety...

Woke up from a nap, sent two texts....froze, rebooted twice..screen turned green during the 2nd reboot.

Back to 11092011 version for me.

Like I said before, I've never had any issues with ANY Trinity kernel until the ones after 9/11.

私のネクサスSから送ら
[Nexus S Android Development] simms22:
check your pm's
[Nexus S Android Development] Bamdroid:
#Boom

私のネクサスSから送ら
[Nexus S Android Development] Bamdroid:
Dumb question but gonna ask anyways..

You guys don't think the data hack has anything to do with it, do you? I doubt it but just curious.

私のネクサスSから送ら
[Nexus S Android Development] GeezyAF:
No voodoo?
[Nexus S Android Development] morfic:
What are you talking about?

Sent from my Trinity G2x
[Nexus S Android Development] GeezyAF:
The kernel that simms just posted doesn't have adjustable temperatures or gamma.
[Nexus S Android Development] king23adrianc:
its not adjustable

its fixed.. voodoo profile v1