yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S III] GideonX:
I found a few areas of improvement. New build linked below.

Here you go: https://bitbucket.org/gideonx/bms_j...c88/arch/arm/mach-msm/acpuclock-8960.c#cl-783

Here's a new build.

- Tweaked voltages again

- Tweaked auto_hotplug sampling rates and thresholds

- Defaults to row scheduler

This version should improve battery life (I hope) :)

2013-01-31 Build - http://goo.gl/PObvx
[Verizon Samsung Galaxy S III] jakereeves31:
Alright. I'll let you know how it goes

Okay, well one thing I notice is that there is hella flicker when I play this game called Ruzzle.

THE BEAST
[Verizon Samsung Galaxy S III] x714x:
1/31 build wont boot for me, running Liquid
[Verizon Samsung Galaxy S III] GideonX:
I just installed Ruzzle, can't reproduce your flicker :(

Did 1/29 zip boot for you? (http://goo.gl/OXz1n)

Edit: Booted Liquidsmooth with 1/31 zip on mine. Can anyone else confirm non-boot on Liquid?
[Verizon Samsung Galaxy S III] nguyenvn:
Still no boot for me. Oh well. I'm sure it's my S3 having a crappy "slow" cpu type.
[Verizon Samsung Galaxy S III] juancaperez2000:
It boot for me running CM, so now should be better run ondemand (tweeked) and row (tweeked), also sometimes if i reboot my phone i need pull out the battery for power on my phone
[Verizon Samsung Galaxy S III] GideonX:
Give ondemand/row a try.
[Verizon Samsung Galaxy S III] GideonX:
2013-02-01 Build - http://goo.gl/mPd38

- Trinity colors :)

Here's epic citadel benched at 1836 ondemand/row.
[Verizon Samsung Galaxy S III] jakereeves31:
Just tried this one, and it flickers in Ruzzle as well

THE BEAST
[Verizon Samsung Galaxy S III] juancaperez2000:
Just play for first time ruzzle no flikers at all, good game, awesome kernel
[Verizon Samsung Galaxy S III] GideonX:
Is hardware overlay in dev options enabled or disabled in your rom? Not sure if that's the cause, but a while back someone mentioned flickering on a rom and toggling that stopped it.
[Verizon Samsung Galaxy S III] osuron07:
Anybody getting boot loops on the newest build?
[Verizon Samsung Galaxy S III] GideonX:
For folks getting bootloops or can't boot, try Test Build 1 first. If that doesn't fair any better than before, proceed to Build 2. I'm testing a few things right now:

Test Build 1 - http://goo.gl/xUs28

Test Build 2 - http://goo.gl/c1O6D
[Verizon Samsung Galaxy S III] jakereeves31:
I don't understand why I got the flicker. It doesn't flicker on any other kernel

THE BEAST
[Verizon Samsung Galaxy S III] GideonX:
Do me a favor and try the test builds I posted. It might fix the flicker.

Sent from my SCH-I535
[Verizon Samsung Galaxy S III] jakereeves31:
Alright. Let you know how it goes

THE BEAST

---------- Post added at 09:25 PM ---------- Previous post was at 09:00 PM ----------

I still have the flicker:/

THE BEAST
[Verizon Samsung Galaxy S III] GideonX:
Alright, ill work on that for test build 3. The previous two were meant mostly to boot or stop bootloops.

Sent from my Nexus 7
[Verizon Samsung Galaxy S III] jakereeves31:
Alright, sweet. And just in case you wanted to know. I'm running Black Bean

THE BEAST
[Verizon Samsung Galaxy S III] hsomnus:
Flashed 02/01/13 kernel...got sod after boot...im on liquid 3.2.1
[Verizon Samsung Galaxy S III] GideonX:
Try test build 1 and 2 that I posted a few posts above yours. Let me know if you fair better with either of those versions.

Sent from my SCH-I535
[Verizon Samsung Galaxy S III] TheBurgh:
I am running illusion 1.2.1 and had no problems flashing test #2. Colors look great.
[Verizon Samsung Galaxy S III] osuron07:
Happy to report Build 1 started right up :). Did you still want build 2 tested, or is your focus more on build 1?
[Verizon Samsung Galaxy S III] GideonX:
I think I'm going to merge both test builds into one. It should cover the non-booting and bootloop issues people are having :)
[Verizon Samsung Galaxy S III] juancaperez2000:
Running the ones before test builds, really good kernel!!! Edit: build 02/01
[Verizon Samsung Galaxy S III] GideonX:
Here's 2013-02-02 Build - http://goo.gl/Bmsnt

- Fixes the non-boot and bootloops issues. It supports slow bin phones now as well.

- Added USB Fast Charge - credit to imoseyon and chad
[Verizon Samsung Galaxy S III] jakereeves31:
Will it fix my flicker?:)
[Verizon Samsung Galaxy S III] GideonX:
Probably not with this build since I didn't change much besides merging in the two changes from earlier tests :)
[Verizon Samsung Galaxy S III] jakereeves31:
Haha. Okay, I shall continue to wait:)
[Verizon Samsung Galaxy S III] GideonX:
However, aside from flicker in that game, it should be pretty good for ya.
[Verizon Samsung Galaxy S III] jakereeves31:
Yeah, but I play that game a lot, so I'm just gonna wait. Haha
[Verizon Samsung Galaxy S III] hsomnus:
This one worked for me...just flashed it though so havent had enough time to gauge it yet.
[Verizon Samsung Galaxy S III] nguyenvn:
Thanks! Working for me now. Seems to be working well so far.
[Verizon Samsung Galaxy S III] TheBurgh:
Is this the latest version? I am still on test build 2
[Verizon Samsung Galaxy S III] GideonX:
2/2 release combines two fixes (test 1 and 2).

Sent from my Nexus 7
[Verizon Samsung Galaxy S III] nguyenvn:
Yes. The latest version 2/2.
[Verizon Samsung Galaxy S III] juancaperez2000:
It is some major changes between b02/01 and 02/02?
[Verizon Samsung Galaxy S III] GideonX:
Mainly frequency table and bus changes. Also addition of usb fast charge.

Sent from my SCH-I535
[Verizon Samsung Galaxy S III] hsomnus:
Some apps force close on 2/2 release...back on lean kernel for now
[Verizon Samsung Galaxy S III] GideonX:
What's the min/max cpu speed you are using? I'll adjust the frequency table for slow.

Sent from my SCH-I535
[Verizon Samsung Galaxy S III] nguyenvn:
I powered off, changed my battery and it would boot loop. Not sure what happened. Tried reflashing 2-2 release and boot loops still.
[Verizon Samsung Galaxy S III] GideonX:
Now that's odd. Gimme a few mins, I'll build another with more relaxed values for slow.

Sent from my Nexus 7

---------- Post added at 10:15 PM ---------- Previous post was at 09:42 PM ----------

Try this one: http://goo.gl/pSYp1

The frequency table for slow is just about identical to stock.
[Verizon Samsung Galaxy S III] osuron07:
So far I've had no issues.

---------- Post added at 11:43 PM ---------- Previous post was at 11:33 PM ----------

After stability for most is accomplished, any chance you could consider making a version with voltage control? I only know how to compile kernels, last time I tried messing with anything intense my phone locked up instantly haha.
[Verizon Samsung Galaxy S III] nguyenvn:
Tried b25 and still got boot loops. Not sure how I got it to work earlier. Even tried switching back to the other battery.
[Verizon Samsung Galaxy S III] GideonX:
Voltage control will be next on the list after squashing some of these boot bugs.

Sent from my Nexus 7

---------- Post added at 12:23 AM ---------- Previous post was at 12:22 AM ----------

Hrm, not sure how swapping batteries caused this weirdness.

Sent from my Nexus 7
[Verizon Samsung Galaxy S III] masri1987:
just wanna say i'm running the 2-2 build on illusions on vzw and it works fine.
[Verizon Samsung Galaxy S III] jakereeves31:
Try playing Ruzzle and tell me if there's flicker, yeah?
[Verizon Samsung Galaxy S III] masri1987:
I downloaded and opened didn't sign in tho because I don't play it, no flicker yet, do I gotta sign in?
[Verizon Samsung Galaxy S III] jakereeves31:
Yeah, it happens during the actual game play.
[Verizon Samsung Galaxy S III] GideonX:
Build #26 - http://goo.gl/tVUG2

- Added support for WPA/WPA2 wifi tethering in CM (testing).

So far it works in CM's wifi tether :)

Edit: Created a new thread to preserve this one. Onward!
[Verizon Samsung Galaxy S III] Obaterista93:
To those with the flicker, who has on GPU rendering or HW overlays? Those have been known to cause flickering for some games, and fix it with others.

Sent from FBI Headquarters
[Verizon Samsung Galaxy S III] morfic:
Building a 1620MHz version to test.
[Verizon Samsung Galaxy S III] prdog1:
Had no problem booting 1.9 on other kernels. Maybe something else went bad in build or upload. Never activated data.
[Verizon Samsung Galaxy S III] got556:
Also having this issue. On Synergy r71.
[Verizon Samsung Galaxy S III] morfic:
Please try the 1620MHz version in comparison.

EDIT: Because this will show if it's in the speed or configuration changes.
[Verizon Samsung Galaxy S III] Breezer23:
Oooo I missed the colors! I kiss Jelly Bean but the colors make it worth it.
[Verizon Samsung Galaxy S III] prdog1:
Same. Still bootlooping.
[Verizon Samsung Galaxy S III] morfic:
Alpha6 is in OP, using the previous config with only the changes needed for DVFS (plus enabling 2 more governors)
[Verizon Samsung Galaxy S III] got556:
Bootlooping on home screen for the first Alpha 5 kernel. So therefore I got back up and running, then ordered Chinese, uninstalled System Tuner, then wiped everything, reflashed r71 Synergy, then flashed the new Alpha 5 kernel and still bootlooping on homescreen.

Will flash Alpha 6 here in a sec once I get back up and running.
[Verizon Samsung Galaxy S III] Schaweet:
Yeah sorry I was reading in order and didn't see the new kernel yet.

Sent from my SGS3 on Synergy Nightlies
[Verizon Samsung Galaxy S III] morfic:
I was just pimping you a bad kernel, seems something i can do on TMO makes *both* LTE variants loop, reverted most config changes for Alpha6 now, keeping only what i need for DVFS and enabled 2 std. governors.
[Verizon Samsung Galaxy S III] prdog1:
Alpha 6 still bootlooping.
[Verizon Samsung Galaxy S III] got556:
Same here. We have faith in you Morfic, and you know I'm a believer in your kernels. :good:
[Verizon Samsung Galaxy S III] morfic:
Well, at least i now know what's looping there.

Interestingly I'm not looping here with any of the Alpha5 or 6 kernels.

Need to see what it is the LTE phones hate.
[Verizon Samsung Galaxy S III] 1ManWolfePack:
Mine booted, but system crashed (TW FC everywhere)....
[Verizon Samsung Galaxy S III] WizeGuyDezignz:
Same here.
[Verizon Samsung Galaxy S III] got556:
Anything particular you need me to try?

ETA: Woah just thought I lost my IMEI lol. Have it backed up but man when I reflashed Synergy data took a long time to grab haha.
[Verizon Samsung Galaxy S III] morfic:
What does logcat look like during the great crashing?
[Verizon Samsung Galaxy S III] got556:
Let me see if I can get it up and running enough to pull a log. Being that mine is bootlooping and I can't even unlock the homescreen upon start up I'm not sure how useful my phone is going to be to extract info.

Some of those guys getting FC's however hopefully will chime in.

I'll reflash A6 and see what happens. Looking fwd to having TKT back on a phone.
[Verizon Samsung Galaxy S III] Schaweet:
Mine boots on 6 but lags so hard at the lock screen that I can't unlock and then there is a system force close. Not sure how to run an log cat at that point and I'm not near a PC.

Fwiw.....alpha2 is what I'm on and it's rockin so not sure what you changed.

Sent from my SGS3 on Synergy Nightlies
[Verizon Samsung Galaxy S III] morfic:
with adb on your pc and a usb cable you can log while UI is crashing or before it ever comes up.

adb lolcat > log.txt

then you can attach and email log.txt when you think you logged enough and hit ctrl-c to stop the logging.
[Verizon Samsung Galaxy S III] got556:
I got a FC once when I was trying to unlock the home screen...but it bootlooped before I could see what the exact FC was.

I'll do a PC logcat here in a minute. Eating my dinner. :good:

---------- Post added at 08:22 PM ---------- Previous post was at 08:04 PM ----------

Running adb logcat on bootup it states waiting for device, then starts bootlooping w/out ever recognizing or logging anything from the phone. adb logcat does work however since I tested before I shut down the phone and flashed the Alpha 6 kernel.

ETA: N/M I see what I gotta type so it still outputs but wont show anything in the cmd window.
[Verizon Samsung Galaxy S III] 1ManWolfePack:
Same exact thing here.
[Verizon Samsung Galaxy S III] got556:
Logcat

https://www.dropbox.com/s/osasqj1ip8c0pm9/TrinityAlpha6%20Logcat.txt

ETA: 7zip file

https://www.dropbox.com/s/wwo3sanzgpe4f8i/TrinityAlpha6%20Logcat.7z
[Verizon Samsung Galaxy S III] morfic:
could someone open up alpha6, empty out system/etc/init.d and repack

then empty out /system/etc/init.d/ on the phone

then flash the emptied out alpha6?

just trying to rule that out
[Verizon Samsung Galaxy S III] morfic:
can i see a logcat off of Alpha2 in comparison?
[Verizon Samsung Galaxy S III] got556:
Don't have alpha 2 but if you link it I'll get you one.

ETA: D/Ling from the OP now.:good:
[Verizon Samsung Galaxy S III] 1ManWolfePack:
It's in the OP again...
[Verizon Samsung Galaxy S III] prdog1:
Removed init.d. Still no boot.
[Verizon Samsung Galaxy S III] got556:
A2 runs beautiful!

Alpha 2 Logcat zip

https://www.dropbox.com/s/x6tdjyg9b9o9tdd/Trinity%20Alpha2%20Logcat.7z

Alpha 2 Logcat txt

https://www.dropbox.com/s/h93y1k489yt31gu/Trinity%20Alpha2%20Logcat.txt
[Verizon Samsung Galaxy S III] evolishesh:
Is alpha 2 booting on synergy rom?
[Verizon Samsung Galaxy S III] got556:
Yes
[Verizon Samsung Galaxy S III] evolishesh:
Thanks! I'm going to try it out
[Verizon Samsung Galaxy S III] faehsemc:
Anyway to add fast charge?
[Verizon Samsung Galaxy S III] SMR-DINO313:
What's the battery life on this kernel ? Tempted to try I'm running stock ..

Sent from my LandLine
[Verizon Samsung Galaxy S III] got556:
It's in the trinity kernel toolkit.
[Verizon Samsung Galaxy S III] vx2ko:
Has anyone tested this against cleankernel? As in battery life and performance?
[Verizon Samsung Galaxy S III] got556:
First and foremost this kernel just dropped today for us VZW S3 guys. Secondly battery life is very subjective, some could overclock, some could undervolt, signal strength, etc. plays into this.

I will say this. If Morfic builds a trinity kernel for a device I own, I run it. His kernels are very stable. Hoping we can get to GNEX status with his kernels eventually. So once all the bugs are worked out and he's pumping out builds every night, I suggest you get the Trinity Kernel Toolkit from the Play Store and enjoy the vice's that Morfic has a fix for. :good:
[Verizon Samsung Galaxy S III] morfic:
It's untested, i don't have a USB strong enough to test it, It's slightly different than on other devices, it uses Samsung's own fast charge, just with the togle enabled i force the charge current max to 1.5A, which is the max defined in the source, it lacks testing, it was an attempt for my TMO sgs3 and as i said, VZW And SPR were caught up pretty much fully on source side.

I'll just have to figure out why i'm not able to unlock dvfs for the LTEs w/o them going into a spin cycle.

I can boot all 3 stock kernels on my sgs3 and fully uses the max clock in that kernel, why this doesn't work on the LTEs, we will find out.

If someone could grab me a dmesg off of a looping device that might be useful.

adb shell dmesg > dmesg.txt

or

adb shell
su
dmesg > /sdcard/dmesg.txt
adb pull /sdcard/dmesg.txt

either way, that dmesg, as close to booting as possible would be great.

obviously i meant booting of the kernel, not of the OS
[Verizon Samsung Galaxy S III] josephpalozzi:
First time with Trinity

Nice kernel, I like the color tweaks and it will be interesting to use this after a bit more development. I am also wondering what the audio tweaks are. Have you fixed some of the USB audio issues with USB OTG?

One issue i have noticed, it seems to have an problem with recognizing exFat formatted SDcards. No issues with LG1 or CleanKernel but Trinity or KT747 and upon booting I get the notification that "SD card ready to be removed". Root explorer sees nothing and removing and replacing the SD card does nothing (same noticication pops up).

Thanks for the work!
[Verizon Samsung Galaxy S III] fix-this!:
what governors does this kernel have?
[Verizon Samsung Galaxy S III] epagib:
Msm-dcvs

Ondemand

Userspace

Power save

Performance

With noop, deadline, cfq

Sent from a SYNERGIZED GalaxySIII
[Verizon Samsung Galaxy S III] boynamedstacy:
What! No buzz words!? :p

Glad to see you decided to add d2vzw to your repertoire Morfic! Now my androids are complete :D Thanks brother.

Sent from my SGH-I535
[Verizon Samsung Galaxy S III] got556:
I'm looking fwd to his JB kernels :D:D:D
[Verizon Samsung Galaxy S III] Breezer23:
After a day of use I must say this is smooth. I missed the colors. Unfortunately, I miss JB so I'll have to go without the colors for now.
[Verizon Samsung Galaxy S III] WizeGuyDezignz:
Has not being able to overclock been addressed, or is it just me still having that issue?
[Verizon Samsung Galaxy S III] Schaweet:
Its an alpha release. He's still working out issues.

Sent from my SGS3 on Synergy Nightlies
[Verizon Samsung Galaxy S III] 1ManWolfePack:
I'm able to overclock just fine, but only using Trinity control.

And yes, I absolutely 2nd that this is currently the smoothest TW kernel for me. Everything is considerably smoother and more fluid.

Battery is looking great too. Thanks!
[Verizon Samsung Galaxy S III] idelgado782:
Installed this morning and have been running it since with no issues yet. I ran your kernaIs on my Nexus S. Definitely looking Forward to future development!
[Verizon Samsung Galaxy S III] BrUhNiGGs:
God damn I missed the trinity colors from my gnex and now its on my S3 :) now my whites arent yellowish But I do notice that the blacks are green because of the low contrast. Is there a way to tune up the contrast to 0?

I am going to test this kernel out for a while. It doesnt have the CPU 1 going offline problem does it? I checked the box that said "Force nonboot cpu" so Im wondering if it is referring to that problem.
[Verizon Samsung Galaxy S III] PetRiLJoe:
Quoted because I have the same question. I need to know if this fixes the issue with 1 CPU not working on the synergy ROM.
[Verizon Samsung Galaxy S III] boynamedstacy:
Its fine bro. Both cpu's working great here.

Sent from my SCH-I535
[Verizon Samsung Galaxy S III] BrUhNiGGs:
Yeah I can now confirm that both CPU 0 and CPU 1 are running just fine with this kernel. It may be because I have the "force non boot cpu" option checked in the toolbox app. I'm running synergy r73 with ondemand stock frequencies since I can't oc.

Edit: I did a little further testing and CPU 1 will only stay online if you have the trinity toolbox with the force cpu boot checked. It also does not play well with CPU Sleeper. The cpu will not come back on until you uncheck and recheck the force boot cpu option in the toolbox.
[Verizon Samsung Galaxy S III] Metfanant:
So kernel alpha 2 from the op is the latest for our vzw phones yes?

Is there an md5 we can compare the download to?

sent from my unlocked VZW Galaxy S3 running SynergyROM nightlies
[Verizon Samsung Galaxy S III] pyunny:
this is what i'm getting:

C96191735698165E1CEE37CD103E1A3E
[Verizon Samsung Galaxy S III] SlimSnoopOS:
I'm seeing the same md5 too
[Verizon Samsung Galaxy S III] PetRiLJoe:
Thanks for that. I am with a lot of others on the synergy thread that has CPU 1 go offline after the screen turns off. from another poster I learned that if you change governors then go back to your preferred governor then the second CPU starts working again but only until the screen goes off. The developer of synergy has not commented on this and it is obviously a concern to a lot of people.

I'm definitely interested in this kernel (just because of the CPU 1 issue) but since it's so new I might just wait another day to see if we get another update.

I heard a couple people complain / comment on colors. Is the contrast or the colors somehow I justed in this kernel so that it doesn't look normal?

Thanks again,
[Verizon Samsung Galaxy S III] jcurley:
Love the kernel! By far the smoothest on synergy.

Noticed the colors are washed out. Tried using your app, but no color adjustments available.

Does anyone know how to adjust this?
[Verizon Samsung Galaxy S III] im_on_fire:
It appears i have a runaway Android OS process. Never had it before. Lost 13% battery life while sleeping with mobile data turned off. Anyone else have this? Screen on time is about one hour.
[Verizon Samsung Galaxy S III] prdog1:
Check with better battery stats. Sounds like the gsiff-daemon bug but could be something else. Saw you were using leankernel and Imo has a workaround in kernel for it. Reboot usually fixes for a while. There are threads about it in forum. Have also seen facebook and alarms doing the same. Need to check wakelocks and see what process is actually keeping it awake.

Better battery stats XDA edition free to members at bottom of this post. Feel free to donate to dev if it helps you.

http://xdaforums.com/showpost.php?p=15869886&postcount=2
[Verizon Samsung Galaxy S III] Anonamoose:
I just wanted to say thank you and this is the smoothest kernel I have tried for the -gs3. I actually have it slightly down clicked to 1.2ghz and it's amazing. Ty again.
[Verizon Samsung Galaxy S III] stephenj37826:
For some reason the settings don't stick as far as clock speed goes. I am using the tkt app as well.
[Verizon Samsung Galaxy S III] morfic:
I'm working on that for SPR and VZW.
[Verizon Samsung Galaxy S III] prdog1:
They only stick if you leave app open in mutitask by hitting home button. If you close app with back button or reboot will reset to default.
[Verizon Samsung Galaxy S III] montebello13:
Settings stick for me but not using trinity toolkit. Had trouble with other kernels keeping my settings, this one just works :) and its great on performance and battery

Thanks morfic
[Verizon Samsung Galaxy S III] BrUhNiGGs:
But is does it stick after you exit out of whatever app your using? And how is CPU1 staying online?

I hope you will fix the oc stick issue soon Morfic as I really want to go over 1.5ghz. I need my phone more smooth :)
[Verizon Samsung Galaxy S III] morfic:
If it's not smooth at 1512, then i'm doing something wrong.
[Verizon Samsung Galaxy S III] BrUhNiGGs:
It is smooth but I find kernels and overall experience to be much more snappy if I clock it up more than it already is.
[Verizon Samsung Galaxy S III] prdog1:
As long as I leave toolbox app open in multitask I can go in and out of any other app with no problem. Both cores working fine. Deep sleep good also. Battery great.
[Verizon Samsung Galaxy S III] morfic:
Alpha7 booting at 1728MHz is in the OP, i need VZW confirmation that it takes 1728MHz, however, i have confirmation the same change worked for SPR.

If you know where to look in sysfs, a confirmation would be nice.
[Verizon Samsung Galaxy S III] jzd5032:
It works great on Verizon (Synergy Nightly r73). Sticks and is very fluid. Thank you!
[Verizon Samsung Galaxy S III] morfic:
Well, looks like I can continue now .
[Verizon Samsung Galaxy S III] prdog1:
Booting fine on Synergy 64. Settings stick when app closed. Set to 1512. Getting some flunctuations on reboot at 1728 and some at 1134. May be thermald. Phone pretty hot right now from flashing. Will let settle and retest. Both cores working as should. Good work Morfic. :cool:
[Verizon Samsung Galaxy S III] morfic:
I can include a relaxed thermald.conf
[Verizon Samsung Galaxy S III] prdog1:
Some of the hold set on reboot on all these kernels seems like it may be related to the scaling apps are getting a late hookup to root permission. They are getting SU permission late in the boot process.
[Verizon Samsung Galaxy S III] morfic:
They all have to wait until OS signals that boot is complete, which can happen late enough that people lately (especially on JB) were on their homescreen and inside TKT before that signal is given, triggering false reports of "settings don't stick",making it harder to deal with correct reports.

Best way to verify is to open app after you see the toast from SuperSU that TKT was given root access and not before.

Lately many get into the app long before that. Thus seeing defaults.
[Verizon Samsung Galaxy S III] prdog1:
Looks good now. Set at 1512. When it was hot would underclock to 1134. Now that it is cooled down it is sticking on 1512 on reboot. Looks good to me. I normally run 1728 anyway.