yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S III] rockingondrums:
I'm getting some crazy coloration with cm10.2 nightly 10/19 and latest BMS. Holo blue is now orange (kinda like MIUI), reds are blues, etc. The stock nexus wallpaper that's like a dark argyle pattern looks like scrambled 8-bit.

I took a screenshot but I'm not sure if it's on the rendering or displaying side of things, so you may not be able to see anything...
[Verizon Samsung Galaxy S III] GideonX:
CM made some changes. Try this test build - http://goo.gl/W6FXV3
[Verizon Samsung Galaxy S III] GideonX:
The test builds look to be working, so here's the official release.

Build 2013-10-19 - http://www.droidhype.com/kernel/34/
[Verizon Samsung Galaxy S III] SlimSnoopOS:
Appreciate this man! Would you mind posting or linking me to the display commit that the rom we're using needs to have? I was looking at today's newest Slim Bean weekly changelog and I couldn't tell if it was included.
[Verizon Samsung Galaxy S III] ryanstfl:
I would like to know this too, I mean, will it not boot or just cause battery drain or soft reboots

EDIT: it doesn't work
[Verizon Samsung Galaxy S III] hallstevenson:
I don't think this is the intended result... This is the 10/19 kernel.
[Verizon Samsung Galaxy S III] SlimSnoopOS:
Ahh don't tell me that lol I was about to try it in a few. The latest 10/19 BMS does not boot on Slim Bean 1.9?

Edit: Ahh, well as long as BMS 10/16 works then I have no choice but to be happy. But you know, green looks good on the S3...
[Verizon Samsung Galaxy S III] BrUhNiGGs:
Thanks for the update. Working fine on latest carbon nightly
[Verizon Samsung Galaxy S III] rockingondrums:
The test build worked, thank you. Will flash this one the next time I update ROM.
[Verizon Samsung Galaxy S III] krazie1:
Has anyone tried the build released today with PacMan?
[Verizon Samsung Galaxy S III] hallstevenson:
You try it. What's the worst that could happen ?
[Verizon Samsung Galaxy S III] GideonX:
The world implodes and krazie1 goes missing :(
[Verizon Samsung Galaxy S III] krazie1:
My phone could explode and then i'll go from the community with no way to help anyone anymore

Exactly my point, thanks for understanding
[Verizon Samsung Galaxy S III] hallstevenson:
No one else saw those weird graphics / glitches with the 10/19 build?
[Verizon Samsung Galaxy S III] GideonX:
What rom? If it does not have the new commits from CM, you will have glitches. Check the download page for the 10/19 release for more info.
[Verizon Samsung Galaxy S III] hallstevenson:
Sorry, I didn't read that close enough when you first posted it. It was made available on 10/17 and presumably updated 1-2 days (or more) prior to that, so it's no doubt the reason.
[Verizon Samsung Galaxy S III] GideonX:
New build today that should address all the issues related to the ramdisk.
[Verizon Samsung Galaxy S III] Reborn627:
Any chance it will correct the qcril issues, at least I'm guessing that's the issue, with Mastamoon's ROM? I attempted the 10/19 build and got the dredded "Unfortunately com.android.phone stopped working". Just curious.

Peace,

Ray
[Verizon Samsung Galaxy S III] GideonX:
Looks like it does ;)
[Verizon Samsung Galaxy S III] twistedillutions:
Battery life not that good

Smatmax sio undervolt - 75 across

Went i set to powersave my fone goes very slow

Besides smartmax what other gov is good for battery saving
[Verizon Samsung Galaxy S III] Reborn627:
Da man! On a side note. Got a random reboot after flash. Not completely uncommon after flashing lately but I thought I'd note it. Otherwise slick as s***

Peace,

Ray
[Verizon Samsung Galaxy S III] farenteria:
You really think so? Your stats look really good to me. I get about two hours of screen on time before I need to charge it
[Verizon Samsung Galaxy S III] twistedillutions:
I would 13+hrs with 7hrs on sleep mode n almoat 5hrs on screen . I shouldn't complain since stock i would do worse
[Verizon Samsung Galaxy S III] GideonX:
Build 2013-10-23 - http://www.droidhype.com/kernel/34/
[Verizon Samsung Galaxy S III] Reborn627:
OK, I'm on Mastamoon's 10/22 build and GideonX ' s kernel from today and I'm getting random reboots left and right. I've had 3 more since my last post. I'm stuck at work so a logcat is not possible, and I can't seem to get alogcat to do anything either. Is anyone else experiencing reboot issues? My first was within 10 minutes of flashing the rom, gapps & kernel and then about every 20-30 minutes there after. Nothing is overclocked/underclocked and no tweaks whatsoever. Thoughts?

Ray

Sent from my Galaxy S3 rockin' Mastamoon's Unofficial and GideonX 's BMS kernel.
[Verizon Samsung Galaxy S III] TotallyAnxious:
Wheatley (I prefer wheatley) and intellidemand are good alternatives. CFQ might work a little better than SIO.
[Verizon Samsung Galaxy S III] GideonX:
Did you try flashing rom, gapps, boot to homescreen. Then flash BMS? Sounds like something isn't playing right.
[Verizon Samsung Galaxy S III] Reborn627:
No, I do it all at once in TWRP. In that order though. I'll give it a shot that way. When you say "homescreen" you mean in recovery, right?

Ray

Sent from my Galaxy S3 rockin' Mastamoon's Unofficial and GideonX 's BMS kernel.
[Verizon Samsung Galaxy S III] GideonX:
I mean let it boot completely, then reboot back into recovery and try BMS.
[Verizon Samsung Galaxy S III] Reborn627:
Oh, OK, no I've never done it that way. I'll give it a shot. Only clear dalai after rom flash, correct? Or should I do it after kernel as well?

Sent from my Galaxy S3 rockin' Mastamoon's Unofficial and GideonX 's BMS kernel.
[Verizon Samsung Galaxy S III] tdawgg777:
Gideon you run slimbean yes? Such version are you o 1.9 or the unofficial 1.9 nicklovell put up on goo?
[Verizon Samsung Galaxy S III] hallstevenson:
It should not be necessary to clear dalvik or cache when flashing kernels
[Verizon Samsung Galaxy S III] GideonX:
Currently running Carbon, but before this I was on Slim 1.9 weekly (official).
[Verizon Samsung Galaxy S III] Reborn627:
That's what I thought. Unfortunately I've tried 3 different ways and I'm still getting reboots :-\

Ray

Sent from my Galaxy S3 rockin' Mastamoon's Unofficial and GideonX 's BMS kernel.
[Verizon Samsung Galaxy S III] GideonX:
Do me a favor, can you find out what your min/max cpu speeds are after flashing everything? Trickstermod can show you on the first tab if you have that installed.
[Verizon Samsung Galaxy S III] SlimSnoopOS:
BMS 10/19 and 10/23 load fine on the unofficial SB, in case you were wondering.
[Verizon Samsung Galaxy S III] Reborn627:
Not familiar with trickstermod, play store? Anyway, I use cpuspy and according to that mastamoon's kernel is 1512/384 and your kernel is 1836/189.

Ray

Sent from my Galaxy S3 rockin' Mastamoon's Unofficial and GideonX 's BMS kernel.
[Verizon Samsung Galaxy S III] GideonX:
Bingo. It's not limiting to the default 384/1512 correctly. It's hitting 1836 and your phone can't handle it. Easiest way to stop the randomness for you is to grab trickstermod (or similar) and set the min/max to 384/1512.

Working on getting it set in the zip atm, bbiab.
[Verizon Samsung Galaxy S III] Reborn627:
OK, looks like it's under the general tab. Check the freq lock box and set, yes?

Sent from my Galaxy S3 rockin' Mastamoon's Unofficial and GideonX 's BMS kernel.
[Verizon Samsung Galaxy S III] GideonX:
Just set min to 384, max to 1512. No need to lock.
[Verizon Samsung Galaxy S III] Reborn627:
Fantastic! Thanks for the help!

Ray

Sent from my Galaxy S3 rockin' Mastamoon's Unofficial and GideonX 's BMS kernel.
[Verizon Samsung Galaxy S III] hallstevenson:
I'm running PAC-Man (10/20 nightly build) and it shows 1512/384 max/min. You think the ROM is setting the mix/max CPU frequencies on it's own ?
[Verizon Samsung Galaxy S III] GideonX:
Probably not the rom. I'm setting the limits now in kernel. Reupload coming in a sec.
[Verizon Samsung Galaxy S III] GideonX:
Updated zip uploaded, same link. Small change, but it should now limit min/max correctly on boot.
[Verizon Samsung Galaxy S III] twistedillutions:
Ok thanks ill give it a try

On another note does drop to 189 make a difference compare to 384??
[Verizon Samsung Galaxy S III] jlokos:
I ran the 10/23 kernel on the 10/23 vanir build. I kept getting "the process com.android.phone has stopped unexpectedly. please try again " When I pressed ok, the same message popped up again. I rebooted to recovery, reflashed the kernel, and got the same error again. However, this time when I pressed ok, the error message did not come back and everything now is working fine.
[Verizon Samsung Galaxy S III] TotallyAnxious:
I wouldn't do it. 384 is stable and works fine for battery life. If you drop it too low your phone will be laggy. And if it lags it has to use more power to catch back. So point is stability helps battery life.
[Verizon Samsung Galaxy S III] GideonX:
189 isn't for everyone. Experimenting is key.
[Verizon Samsung Galaxy S III] thelangosta:
I had the same issue but was on a different kernel. It's the rom and some of the guys/gals on cm10.2 were having the same issue.
[Verizon Samsung Galaxy S III] Rrrracer:
Weirdness... I just loaded up SB1.9 official and the 10/23 BMS kernel (same recovery session) and my screen looks like Hallstevenson's above. Suggestions?
[Verizon Samsung Galaxy S III] GideonX:
Sb1.9, use bms 10/16 for now.
[Verizon Samsung Galaxy S III] Rrrracer:
No problemo. Is it a Slim thing?
[Verizon Samsung Galaxy S III] indyssee:
No. Its the video drivers. Nick posted an updated ROM with the necessary commits on his goo.im account and its working great with the 10/23 BMS
[Verizon Samsung Galaxy S III] GideonX:
The official weekly just doesn't have the new commits. Use older BMS or grab the test build in the slim thread and use newest BMS.
[Verizon Samsung Galaxy S III] ryanstfl:
It would have been really nice of you to post that link, because I have no idea who Nick is and how to find his goo.im account...

http://goo.im/devs/nicklovell23/Sli...zw-4.3.build.1.9-UNOFFICIAL-20131023-0412.zip
[Verizon Samsung Galaxy S III] Rrrracer:
Running great on 10.16. Thanks GideonX!
[Verizon Samsung Galaxy S III] kidruk:
I know its a long shot but will the latest build work on pac-man 10/29 nightly? .. I need BMS in my life lolol ..
[Verizon Samsung Galaxy S III] jkdrinkard:
Yes it runs perfectly on the lastest pac nightly. Refer to that thread for updated install instructions.
[Verizon Samsung Galaxy S III] kidruk:
Appreciate it! .. Just wanted to make sure as I did not see anyone in that thread stating so ..
[Verizon Samsung Galaxy S III] hallstevenson:
It's not working for me. I keep getting random reboots with it.
[Verizon Samsung Galaxy S III] jkdrinkard:
Which ROM are you on?
[Verizon Samsung Galaxy S III] hallstevenson:
PAC 10/28. The ROM works fine until I install BMS...
[Verizon Samsung Galaxy S III] kidruk:
Good thing I asked .. I was about to flash that kernel too .. I'll just wait it out ..
[Verizon Samsung Galaxy S III] jkdrinkard:
Did you perform a full wipe then install pac, gapps then bms?
[Verizon Samsung Galaxy S III] GideonX:
Can you post exactly how you flashed everything? I assume you have not adjusted anything rom or kernel after flashing?

Edit: To clarify why I'm asking:

BMS now uses anykernel, which takes whatever ramdisk you use and combines it with BMS during the flashing process. I do not ship a ramdisk anymore.

So if you were on another kernel or if you had the ramdisk altered, you are basically merging that altered ramdisk with BMS. My kernel should work with 99% of the stock ramdisks out there. I've tested enough on d2vzw to get a good sampling.
[Verizon Samsung Galaxy S III] kidruk:
So your latest should work on the latest PAC man? .. I usually get reboots until I undervolt .. I'll flash and report back ..
[Verizon Samsung Galaxy S III] GideonX:
Yes, it should work. Flash the rom, gapps, BMS and go.
[Verizon Samsung Galaxy S III] kidruk:
Perfect .. Just wanted to make sure .. Its just not the same without BMS lolol ..

---------- Post added at 10:11 PM ---------- Previous post was at 09:57 PM ----------

You might want to undervolt .. I'm currently running 10/29 nightly on the latest BMS kernel .. Running perfectly fine ..
[Verizon Samsung Galaxy S III] hallstevenson:
Yes. Papa indicated that you have to do a full wipe if you're going from anything prior to 10/27 builds.

---------- Post added at 10:39 PM ---------- Previous post was at 10:34 PM ----------

I've been wondering if it had anything to do with anykernel setup. I might try a pre-anykernel version and see how it goes.

I flash the ROM and gapps and let it reboot. I set up the Google stuff and let apps restore and then flash the kernel. I don't make any extensive adjustments to the ROM other than personalization stuff.
[Verizon Samsung Galaxy S III] SomeGuyDude:
clean flash with Carbon nightly and all is well. That's everything flashed at once, ROM -> gapps -> Kernel -> font. Works just fine.

Any recommended setups, Gideon? I've been leaving most of it stock, just underclocking it and using smartmax but I'm curious what might be "optimal".
[Verizon Samsung Galaxy S III] GideonX:
I use sioplus/interactive, but whatever works for you should be fine.
[Verizon Samsung Galaxy S III] hallstevenson:
I don't know what's wrong.... This morning, I did a fresh install of PAC 10/28, gapps, and BMS 10/23 build. As soon as the phone started up the first time (after going through the Google setup stuff), I got repeated Force Close pop-ups for com.android.phone.

I have learned one thing I can share as a tip !! If the screen is unlocked, most people probably aren't quick enough to tap "OK" and "Reboot" and then "Recovery" as the FC pop-up takes over all input so quickly. So, LOCK the phone, then wake it up, but do not un-lock it. Leave it on the lock screen. You can still press the power button and get the power menu without the FC pop-up interrupting you ! :D
[Verizon Samsung Galaxy S III] GideonX:
The only time I've seen that is on the older rom builds or if you restored your old call log. Anyone else seeing this on PAC?
[Verizon Samsung Galaxy S III] hallstevenson:
I don't restore anything. To me, the Play Store reinstalling apps doesn't count as "restoring" as it's installing compatible (with my Android version, DPI, etc) versions of the same apps I had previously and any app data should be created from scratch.

It bugs me that it's working fine for others though.... That tells me the kernel is fine !
[Verizon Samsung Galaxy S III] kidruk:
Im good on PAC ..
[Verizon Samsung Galaxy S III] hallstevenson:
Okay, trying again.... There's a problem with PAC and the "PAC in Black" setting in that when it's enabled, it causes force closes. Other problem is, it's now ENABLED by default, while I'm positive that in the past it was not. Anyway, I made sure it was off and flashed the 10/23 BMS build again. When it restarted it, the status bar and background wallpaper were missing (could be more but I don't know what) along with a error message that System UI has closed. I hit okay and then SystemUI seems to reload -- status bar shows up, wallpaper changes, etc, etc. So far, nothing else bad has happened. I'll keep a watch on it...

---------- Post added at 03:59 PM ---------- Previous post was at 03:39 PM ----------

Well, that didn't take long (20-30 minutes). It just rebooted on it's own....

Hmmm, the max frequency is 1836mhz !! I wonder if that's my problem ? Changing it to 1512mhz now.
[Verizon Samsung Galaxy S III] GideonX:
You have the old BMS 10/23 zip. Redownload the same zip from the same link. New zip should fix the max cpu speed problem.
[Verizon Samsung Galaxy S III] hallstevenson:
I'll download it but no need to install it, right ? I have the max set to 1512 and "set on boot" checked. I remember you released one with this O/C'd speed as the default and fixed it but I thought it was an older build.
[Verizon Samsung Galaxy S III] GideonX:
Right, if you have it set on boot, then you're fine. I'd download just in case for future flashing.
[Verizon Samsung Galaxy S III] hallstevenson:
It's downloaded and replaced the bad one. Hasn't rebooted yet...
[Verizon Samsung Galaxy S III] toklas:
tried reading through the thread for an answer...

running latest d.i.r.t. rom which kernel version should i use the 3.0 or 3.4?
[Verizon Samsung Galaxy S III] necropuppy:
3.4 as it is android 4.3.1
[Verizon Samsung Galaxy S III] ryanstfl:
I'm curious what everyone's setup is? I need about 3 hrs screen on and about 12 hrs of battery life. Right now I get about 10. Any recommendations?

Voltages, scheduler, gpu gov and cpu gov? Any recommendations help. My last really good battery life was on BionicSheep and I can't seem to duplicate its success. Closest I've gotten is with bms.

Also, are there major differences between schedulers? There's so many!
[Verizon Samsung Galaxy S III] aypeeootrek:
Is there any suggested app to use with this? I'm using Rom toolbox pro and when my device starts lagging a little,I check my settings and see that they haven't stuck. I'm on Pac man 11/2. Just wondering if there is an app conflicting. And sorry if this isn't the right thread for the topic,I out it here because I felt it deals with the kernel. Thanks

---------- Post added at 12:35 AM ---------- Previous post was at 12:33 AM ----------

need to use the 3.4 before 10/19. There commits added after that that aren't updated in dirty unicorns. Once its updated the latest should work
[Verizon Samsung Galaxy S III] GideonX:
Trickstermod works really well.
[Verizon Samsung Galaxy S III] xdapadogx:
thanks much. look forward to giving it a go
[Verizon Samsung Galaxy S III] GideonX:
Anyone try this on CM11 or equiv?
[Verizon Samsung Galaxy S III] Reborn627:
Gonna give it a rip

---------- Post added at 01:02 PM ---------- Previous post was at 12:52 PM ----------

Ok, it seems to be working OK. I still don't have access to the external SD, says it's mounted but 0 bytes. Only other issue is a crashing ffc. Phone reboots when trying to use it. I'll keep you posted. Mastamoon will hopefully have a fresh build of 4.4 tomorrow that I'll give a good run. Until then:)

Peace,

Ray

P.S. Oh yeah, I'm running ART instead of dalvik. Seems smooth.
[Verizon Samsung Galaxy S III] GideonX:
Cool.
[Verizon Samsung Galaxy S III] razz1:
So far this is working great on 4.4 kitkat.

Thanks for the update!
[Verizon Samsung Galaxy S III] GideonX:
Which rom are you running?
[Verizon Samsung Galaxy S III] razz1:
One of the unofficial builds from the 11th I think. There are 2 cpu slots at 1728 by the way and the 3d graphics seems to lag. Not sure if thats a kernel issue though.

EDIT: The CPU slots work just fine. I wasn't looking at it correctly.
[Verizon Samsung Galaxy S III] duarian:
This might seem like a really silly question, and I blame having a math exam and working 10 hours on it..but which kernel do we use for the unofficial CM 4.4 builds? the 3.4 one?

Thank you!
[Verizon Samsung Galaxy S III] GideonX:
Yup, just grab the latest BMS. It works on both 4.3 and 4.4.

If you hold off a little, a new build is coming...
[Verizon Samsung Galaxy S III] GideonX:
Build 2013-11-13 - http://www.droidhype.com/kernel/34/
[Verizon Samsung Galaxy S III] jlokos:
I was just about to tell you that I flashed the kernel on Dmeadows CM11 and it appears to be workng fine. Now I'll have to flash this new one. I'll let you know the results tomorrow. Thanks for all the work you do for the S3.

Update: new build working great on 4.4. Fast charge works and all is well. Great job, Gideon; thanks for for your hard work.
[Verizon Samsung Galaxy S III] kinnerful:
Thanks for your hard work!

BTW, do I still need to flash bms_frandom to activate frandom?
[Verizon Samsung Galaxy S III] GideonX:
Yup
[Verizon Samsung Galaxy S III] RayMcGrath:
Thanks so much! BMS is ROCK'N on 4.4!
[Verizon Samsung Galaxy S III] RBarnett09:
Anyone know if the new Liquidsmooth v2.37 is required to have the 3.0.y version of this kernel?

I have no idea how I'm supposed to tell whether or not the ROM is based on 3.0.y. :confused:

I'm doubting it is, but just want to be sure.
[Verizon Samsung Galaxy S III] aypeeootrek:
3.4 kernel
[Verizon Samsung Galaxy S III] RayMcGrath:
r

no, use the 3.4.

btw I liked it so much, I stole your tag line.:good::cool:
[Verizon Samsung Galaxy S III] RBarnett09:
Thank you guys.

So my correct download will be the one he posted only 8 posts back?

This one, for quick links:

http://www.droidhype.com/kernel/34/
[Verizon Samsung Galaxy S III] RayMcGrath:
Yes. 3.4.y

:)

---------- Post added at 12:00 PM ---------- Previous post was at 11:59 AM ----------
[Verizon Samsung Galaxy S III] SlimSnoopOS:
This might be the wrong place to post that.
[Verizon Samsung Galaxy S III] RayMcGrath:
I am so sorry and embarrassed. I thought I was in the 11.0 thread.
[Verizon Samsung Galaxy S III] beepea206:
So I've noticed there's a difference in compatibility with kernels to roms... older versions of roms won't work with newer kernels and such. I see Liquid 2.37 uses the new version of this kernel (yay!), but what about DirtyUnicorn (10/14/13)? I have BionicSheep 3.4.65 flashed, but I wonder which version of this kernel I'd use with DU?
[Verizon Samsung Galaxy S III] SlimSnoopOS:
Use BMS versions from BEFORE BMS 10/19. 10/19 had kernel drivers that were updated from CM and your rom needs to be dated after 10/19 for kernels synced to CM. I'm pretty sure there was a 10/16 BMS release. This is normal, happens periodically.
[Verizon Samsung Galaxy S III] beepea206:
Thx mate. That makes it super easy.
[Verizon Samsung Galaxy S III] xneuromancer:
I'm using "Build 2013-10-16" with Dirty Unicorn 3.9 (2013-10-17) build which is based on 4.3.1.

I've been having "msm_otg" wakelock issues with the default CM kernel which came with the ROM. So I tried the BMS "Build 2013-10-16" (which is the one i have to use, due to the recent video driver changes) and I am still getting the "msm_otg" wakelock issue.

I looked around and supposedly this was fixed in a recent CM or AOKP commit a few months ago. Am I missing something or should this be fixed?
[Verizon Samsung Galaxy S III] d1ez3:
Anyone experiencing slow screen turn on times. When the phone is alseep and pressing the power button it takes a full 2 seconds before the screen is on. On latest kernel on liquid 2.37
[Verizon Samsung Galaxy S III] kinnerful:
Try bumping up the voltage a little if you undervolted.
[Verizon Samsung Galaxy S III] beepea206:
I read online +25 increments of voltage are suggested to find the 'goldy locks' voltage. Does that sound right?

FWIW, I notice a teenie bit of screen lag, but the power savings are worth that microsecond of inconvenience for me.
[Verizon Samsung Galaxy S III] kinnerful:
Every phone is different. I have been doing -50 from GideonX's stock value for a long time and YMMV.
[Verizon Samsung Galaxy S III] GideonX:
That shouldn't be around anymore and most likely is related to something else. Last time I heard of it, someone wiped and re-flashed everything and it was gone.

Like others have mentioned, you might need a voltage bump. BMS comes undervolted by default, d2vzws all react differently to it.
[Verizon Samsung Galaxy S III] steve97ta:
Are you using this on Kitkat?

Latest build Rom/kernel?
[Verizon Samsung Galaxy S III] beepea206:
Yep. 11/23 build. Works like buttah.
[Verizon Samsung Galaxy S III] hallstevenson:
How's this for battery life?
[Verizon Samsung Galaxy S III] hallstevenson:
I've encountered this a couple times previously with the latest kernel and that is extremely slow charging. In fact, I saw battery % decrease while plugged in!
[Verizon Samsung Galaxy S III] JRJ442:
I've had that before too. I think it has more to do with the pos Samsung charger. I started using my Moto charger and haven't had the issue since. Do you have another you can try?
[Verizon Samsung Galaxy S III] GideonX:
That's how smartass2 works, provides very good standby time if I'm not mistaken. Give the other gov/scheds a try.
[Verizon Samsung Galaxy S III] cvsolidx17:
Re: [KERNEL][JB42][AOSP] ¤ BMS ¤ d2vzw / d2usc [2013-02-20]

Lol so can somebody explain what the Asswax governor is good for? Besides a laugh :'D, gonna try a Smartass/Zen combo and underclock a little more to see if that gives me a little more longevity