yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] krneki10:
So I see you have some SOD with certain builds as well. Which one have you found to be stable?
[Samsung Galaxy Nexus] David 617:
What's the word on 3-15/16 SmittyV?

To flash or not to flash... this is the question...
[Samsung Galaxy Nexus] hasnol143:
Guys, is there a reason why my home button/status bar/notification bar keeps crashing? I just did a clean install of omnimetal and smitty 3/15. clean install of all apps from play store, did one reboot and now i only have acess to the homescreen because i can't navigate anywhere else.
[Samsung Galaxy Nexus] osm0sis:
Use

>

3.16.14 and you won't have that problem. It was some commits making LMK have 'roid rage.
[Samsung Galaxy Nexus] hasnol143:
lol wait your symbol is confusing me, do i use Dirtyv 3.16 or are you saying to go back to previous smitty. and thanks!! Because there is nothing newer than 3.16...

---------- Post added at 09:59 PM ---------- Previous post was at 09:58 PM ----------

I'd advise against 3-15.
[Samsung Galaxy Nexus] juju2011:
I hear that can't go past 1.5 or I get bootloop when trickster sets lol shocked 1.5 works used to boot loop on 4.3 with what's his face's kernel. I do notice hefty bat drain tho as apposed to 1.35 I usually use but meh not that big of a deal
[Samsung Galaxy Nexus] pattyboi:):
Hey [MENTION=4544860]osm0sis[/MENTION] ,mind making a osmod twrp for toro when you get a chance bro? I almost flashed your maguro one...that would've been fun xD
[Samsung Galaxy Nexus] osm0sis:
Haha sorry. Fixed. ;)

Sure, I'll check it out tomorrow in between beers. ;)

For now you can just use the theme itself by following the link. All you're missing is the curtain and the other minor stuff I added.
[Samsung Galaxy Nexus] pattyboi:):
Lmao,drink some for me! ;) lol,thanks man :)
[Samsung Galaxy Nexus] osm0sis:
Haha you'd think a Patty might celebrate St. Patty's. :p

You want to know how cool Canada is? In Newfoundland it's a federal holiday. :laugh:

Anyway, z31s1g might have a toro curtain image up too if you go looking. Then all you'd be missing is nano and Aroma Filemanager and you can get them from my Odds and Ends thread. Then you'd be all set. :)
[Samsung Galaxy Nexus] pattyboi:):
Oh trust me,patty will be celebrating lmao,I even pre-celebrated,I'm surprised I can type this lmao & now I wanna go to Canada,you Canadians with your maple syrup and your good hockey teams lol :p & thanks man,I'll go look around :good:
[Samsung Galaxy Nexus] DR3W5K1:
Don't forget about the bud!
[Samsung Galaxy Nexus] paarthdesai:
did you just said bud... ^o^ ^_^ (^o^) (^_-) :D :thumbup::thumbup::sly:;):cool::cool::D:D:D
[Samsung Galaxy Nexus] Swede2008:
And their rap :cool:

http://youtu.be/F-glHAzXi_M
[Samsung Galaxy Nexus] DR3W5K1:
I think that Justin Beaber is what I have to be the most thankful for though. :-p
[Samsung Galaxy Nexus] piterdemon:
And legal weed :p

Wytapatano z Galaxy Nexus 4.4 OmniROM
[Samsung Galaxy Nexus] Ashtrix:
Hi, I'v been using my gnex oc'd from the day 1 & since those 2.2 Froyo (Droid) days to the 4.4 KK (Galaxy Nexus) i can say that all CPU's tend to be one of these 3 classifications adding to that CPU's are like humans, they differ a lot ;) !!

1 > Low leakage ( Generate less heat and have less OC threshold )

2 > Med leakage

3 > High leakage ( Can gen more heat but have higher OC threshold )

As for my SGS it was low leakage cannot handle the LiveOc at all beyond the 1.3GHz mark my frnd's could just go till 1.6GHz !!

Credits : Glitch Kernel developers of SGS.

Plus, more cpu's tend to come under med-leakage. Fortunately my Gnex's is high leakage & can handle Oc's upto 1.8GHz but unstable and max safe limit is 1.5 with minimalist crashes, currently i'm running 1.4GHz with nil crashes. Best bet is to follow this, Just in case Guide [From AK's OP :D] try to stabilize the voltages. My max voltage for 1.5GHz step is just 1305mV.

Here these are my voltages on Mpo, they are used to be a lot diff on Trinity (Max OC perf :p ) ....

Hope this could be of some use...thanks !!
[Samsung Galaxy Nexus] ASHURiCAN:
Hi guys,

I wanted to share with you what happened to my GNex with latest DirtyV kernel (03.16) while I was heavily using it. A picture is better than a long story, so here it is on attachment... My question is: May it be because a corrupt/not complete battery stats? I used the phone for only one cycle (charge+discharge) and this after a cache/dalvik cache reset (I assume it's causing a battery stats reset?). If so, will it readjust the stats and take what happened into account for the next charge+discharge cycle?

Thx in advance for any clarification.
[Samsung Galaxy Nexus] pvkiniyan95:
Guys the recents menu button is very laggy since KitKat stable coz when they were in beta it wasnt a great deal but now these drive me crazy. Am I the only one...sometimes they work and some times no app to display
[Samsung Galaxy Nexus] osm0sis:
Pretty clearly a ROM issue. AOKP definitely has the problem with showing none, probably because they added other optional Recents' and introduced bugs.
[Samsung Galaxy Nexus] pvkiniyan95:
BTW I m on vanir even liquid smooth and omnimetal had the same issue specially the lag

Used dirtyv as well as askp remix and also the kernel not to be mentioned.... Don't u guys get that lag, am I missing something
[Samsung Galaxy Nexus] juju2011:
Bahahahahaha omg this describes half my buddies who also seem to enjoy trying to drag my tropical ass along for their winter time missions.
[Samsung Galaxy Nexus] ASHURiCAN:
Nobody ready to nicely give me some answers? :) Will wait for the sleeping guru members... :D
[Samsung Galaxy Nexus] chongns:
Forget that gap, the bat stat will reset every full charge.
[Samsung Galaxy Nexus] ashclepdia:
personally, if it were me, I wouldn't even worry about that unless it happens multiple times.

sometimes battery reading just gets wonky.

it will also look very skewed after a dalvik wipe. this is due to it having battery graph from before a long boot. after that long ass boot the battery is significantly lower, which in turn makes the graph look weird like that.(it doesn't put on the chart boot times and battery used during boot process)

:D
[Samsung Galaxy Nexus] osm0sis:
It's not in Shiny or Carbon. It's a ROM issue.
[Samsung Galaxy Nexus] dbh369:
A few pages back, smitty said there was an SR1.5 and SR3. I just went to trickster and SR is disabled by apparent default. I think he was going to do this because sr3 isn't shown trickster. But it with Sr enabled, there really isn't a reason to tweak voltages, right?
[Samsung Galaxy Nexus] bsmitty83:
The sr that you can manually change values to is smartreflex 1.5 . I don't use it in smittyV builds . sr3 is always on and checking voltages . you can't enable or disable it once its compiled . the switches in trickster are set to "off" because there is nothing for it to do . It doesn't handle the higher freq . and I don't think sr changes volts under load .
[Samsung Galaxy Nexus] ASHURiCAN:
You mean stats will be cleaned on each full charge? But shouldn't it update the stats instead? It would be more logical, isn't?
[Samsung Galaxy Nexus] Ashtrix:
[MENTION=675921]dbh369[/MENTION], actually what the SR does & is, It's an internal Voltage Regulator System that adjusts your voltages in your galaxy nexus automatically and that too just till the 1.3GHz mark, though the stock speed is 1.2GHz. So if you want to overclock you will disable that because it just won't work, the lean's dev imoseyon modified the code to work till ~1.4GHz (Don't remember it exactly) mark but it was Unstable and would work some times and don't depends just like CPU's.

[MENTION=4608636]bsmitty83[/MENTION], So if there's an SR v3 instead of the stock SR1.5 if we overclock with undervolting do they get reset ?? I mean what does the SRv3 does then :confused: ??

Thanks !!
[Samsung Galaxy Nexus] bsmitty83:
I don't think so , sr simply tries to set nominal volts . if your phone needs more it'll use more . if you undervolt , sr might get reset . not sure on that but over clocking it won't touch those freq unless the toggle for it to be allowed to is switched on .

Really its for off load purposes , I'm not sure how it works with load
[Samsung Galaxy Nexus] ASHURiCAN:
An other case may be my battery slowly coming to the end of its very long and heavy lifetime... :(
[Samsung Galaxy Nexus] osm0sis:
It calculates the nominal voltages during boot. That's pretty decent load to go off of, so I imagine things are fine.
[Samsung Galaxy Nexus] Shambola:
[OT]

I'd like to use only Fb on browser too, but how can I get notifications (and chat messages)?

Does anyone have a Tasker recipe for it? It could be a solution....

When I receive notification (via Tasker) I open the browser....
[Samsung Galaxy Nexus] osm0sis:
Tinfoil for Facebook and MB Notifications do the job with no battery impact. MB isn't free unfortunately.
[Samsung Galaxy Nexus] Nephilim:
SmittyV 3/15 running great, wish AnTuTu would fix their app so I could actually get a benchmark. Ever since the March update AnTuTu as well as AnTuTuX both lock up at 87% and then fail to give an accurate benchmark because the 3D GPU score is left out, if that doesn't happen the app simply force closes completely after the OpenGL 2.0 test. It hasn't even saved any of my tests in history since March 11th. The entire Google Play Store page of reviews is full of others pointing out these exact same problems but the developers apparently decided that it's okay to ignore their consumerbase.
[Samsung Galaxy Nexus] osm0sis:
AnTuTu works fine for me, it was getting LMK'd along with Titanium Backup and Google Keyboard prior to 3.16 though.
[Samsung Galaxy Nexus] Nephilim:
AntutuX?

It force closes the app right after OpenGL 2.0 test and I have to re open it to read my score. Before I cleared data it would just lock up on 87% and not register my GPU scores.

Sent from my Android 4.4.2 Galaxy Nexus
[Samsung Galaxy Nexus] osm0sis:
I just got a FC in AnTuTu but it only started happening once I plugged into the charger. Weird.
[Samsung Galaxy Nexus] d0ge01:
i'm not expert about this but i think it's possible...

Galaxy Nexus has a Samsung SWB-B42 BT 4.0 Dual Band Bluetooth chip that make this possible with right driver ble ( already know )

For this reason i think it work well with 3.4 driver porting( like wifi )

=============================================

EDIT:

Latest release of this kernel ( dirtyV 3-16-2014 ) make my device unstable and laggish, with strange glitch on screen anyone else? ( same settings on the previous release i have 0 problem )
[Samsung Galaxy Nexus] osm0sis:
Logs or it didn't happen.
[Samsung Galaxy Nexus] bsmitty83:
Upgrade ? [emoji106]
[Samsung Galaxy Nexus] p34rp34r:
+1 for graphics wonkiness on dirtyV-R 3/16. it looked like what happens when i try using 512 MHz for GPU, but trickster says 307 MHz. freaked out and immediately reflashed last kernel i had on hand before 3/16. which logs would be pertinent if i decide to try again? logcat? dmesg? kmesg? all?
[Samsung Galaxy Nexus] robbnsade:
I've been using BLE perfectly with my fitbit. Got the fixed apk to allow the gnex to use the app since the app on the store is actually the limited factor. If youre using the fitbit, The apk is called fitbit1.8.7fix.apk or something like that.

[MENTION=4022928]Carlos_Manuel[/MENTION]

If you're talking about further changes then disregard. I know we have the same bt chip as the gs3 so should be able to do anything the s3 is capable of.

Sent from my Galaxy Nexus using Xparent Skyblue Tapatalk 2
[Samsung Galaxy Nexus] GilGameshn1:
I think clearing app data of trickster will do the job ... I can't see the the reason for this to happen . hope it help .

Sent From HellRift
[Samsung Galaxy Nexus] osm0sis:
Good insight here. Thank you for actually describing the problem. :)

[MENTION=4608636]bsmitty83[/MENTION] I'm thinking we need the core voltage fixes Francisco made so that 512 works for all. The recent change that added the extra GPU step may not have been all of what is required for that.

Also the variable OC interface doesn't do anything anymore, so that's why Trickster was wrong. Should that be removed or is there still a way to make it work?
[Samsung Galaxy Nexus] bsmitty83:
Not sure . I'll have to dig into Fransisco's git when I get a chance . been way to busy , busier than I like to be lol

Every kernel I put out I set freq at 1.6 GHz , zen , interactive , GPU & zram if available , and throttle off . then I start doing random abusive stuff ,then check dmsg then antutu x for the 3d part , if it OK I'll post it . since I don't dd it , idk what more I can do on my part , because its rock stable on my phone . if it wasent I'd say so .
[Samsung Galaxy Nexus] bsmitty83:
That's awesome dude love the barter system ;) yea plug away man , you always link good stuff .
[Samsung Galaxy Nexus] Nephilim:
I just gotta say, 3/15 SmittyV is insane smooth! Don't know what voodoo was added between 3/13 and 3/15 but well done Smitty!!

Sent from my Android 4.4.2 Galaxy Nexus
[Samsung Galaxy Nexus] bluerez79:
Do you have force GPU rendering checked in dev. options? I unchecked it a while back and haven't had a problem.
[Samsung Galaxy Nexus] Shambola:
Cooooool! Thank you man! I'll call you the wizard of Os

(and for the chat?)
[Samsung Galaxy Nexus] Nephilim:
**EDIT, Nevermind, spoke too soon, I'm getting unresponsive buttons randomly on the navbar and the keyboard is acting up again like before (not opening without tapping the textbox in an app like 10+ times.

SmittyV 3/15 is smooth and produces 13101 for a benchmark but those two issues are constant so back to 3/13 for me.

Here is the dmesg:

https://docs.google.com/file/d/0B_HqOdvKZoQhdXVGUFMxTG9QMW8/edit

---------- Post added at 06:03 PM ---------- Previous post was at 06:02 PM ----------

Nope, I don't change anything in developer options besides enabling usb debugging and switching to ART.
[Samsung Galaxy Nexus] osm0sis:
We already told you why this happens. Use a 3/16 build. :good:

It's just that "not all silicon is made the same" thing. My device could always handle 512 back when Francisco used to make 2 builds; one for 384 and 512. After Fransisco disabled SR for core and tweaked certain non-GPU core voltages nobody had any issues with 512 anymore and he went 512 only. :)

Abuse it all you want, your device is probably fine for 512 but I'm guessing these other guys' aren't. :eek: ;)
[Samsung Galaxy Nexus] Nephilim:
Sorry man, I've been insanely sick the last few days. Haven't had a chance to keep up with the forums at all. I wasn't aware that these problems were still persistant and addressed on the newest SmittyV. I'll just stick with 3/13 until the next SmittyV update hits.
[Samsung Galaxy Nexus] GilGameshn1:
After a 24 hours using my device with DirtyV 3.16 , I can actually can say it is very good so far ... Vanir + DirtyV ... Stock settings ... The only thing that ibcant understand is : even if I flash DirtyV-R , my camera setting can't change to 1080p ... I clear app data reboot ... Nothing happend ... Thanks [MENTION=4608636]bsmitty83[/MENTION] . [emoji4]

Sent From HellRift
[Samsung Galaxy Nexus] osm0sis:
No worries. Feel better buddy! :)

Does the option show at all? Is the .dvbak file in /system/etc/?
[Samsung Galaxy Nexus] GilGameshn1:
The option is available but no such a file available in that location ...

Sent From HellRift

---------- Post added at 03:16 AM ---------- Previous post was at 03:10 AM ----------

Be cool man ... Be cool .

Sent From HellRift
[Samsung Galaxy Nexus] osm0sis:
media_profiles.xml.dvbak?

If it's not there then maybe you need to dirty flash your ROM to make sure you have the original version. :good:
[Samsung Galaxy Nexus] GilGameshn1:
Thanks ... If I find the file after dirty flash and have the same 720p option , then what choice I have ?

Sent From HellRift
[Samsung Galaxy Nexus] bsmitty83:
Its probably because of the rebase , I'll make sure to get the most current one next build . sorry again , I've been itching to build just haven't had a chance
[Samsung Galaxy Nexus] osm0sis:
If you're on DirtyV-SR it should be there, to avoid the FCs when people try to select it with no memory to support it. DirtyV and SmittyV it shouldn't be there since 1080p works. Only way it gets messed up is if you flashed another kernel which replaced the file first.

The script is fine. And 1080p works fine here on my ROM.. :confused:
[Samsung Galaxy Nexus] GilGameshn1:
No worries .... I just curious about this ... I am in your debt bro for giving me such a sleek exp ... [emoji111] ... Hail

Sent From HellRift
[Samsung Galaxy Nexus] bsmitty83:
Yay one thing I didn't *u©k up .........;)
[Samsung Galaxy Nexus] GilGameshn1:
I checked the file and see the script is fine ... The 1080p option is there for mp4 and h264 ... And I flash dirtyV after the stock vanir kernel ... Could be this cause a problem ... Hmmm ... [emoji108]

Sent From HellRift
[Samsung Galaxy Nexus] osm0sis:
Oh wait.. Not so soon! :p

1080p is correctly disabled for -SR builds, but your DirtyV build is correctly ASRAM but has "DirtyV-SR" in About phone.. ;)
[Samsung Galaxy Nexus] GilGameshn1:
Oh ... Why I did not see this ... DirtyV-R and DirtyV-SR ... Sharing a same flag ... [emoji28] ?

Sent From HellRift
[Samsung Galaxy Nexus] bsmitty83:
Comment fixed . my bad
[Samsung Galaxy Nexus] osm0sis:
Hahaha
[Samsung Galaxy Nexus] dbh369:
+1
[Samsung Galaxy Nexus] d0ge01:
Yes sir, my issue is releated to this.

Since first day my device can't handle at nothing 512 GPU, and now i tried to set in previous release to set 512mhz with core SR off and this cause same glitch and freezes...

Another one thing that i don't understand, why all developers are now disabling SR? IMHO it's useless and cause only issue ( due the fact that "not all silicon is made the same", i noticed overheat ( 70-80° after 20 minute usage ) and high battery drain with Smitty without SR ( for this i switched to DirtyV-R series )
[Samsung Galaxy Nexus] bsmitty83:
I took sr 1.5 out of SmittyV because its my personal build . sorry . Smart reflex is still on it's just not adjustable . sorry for the short answer but I'm juggling a bunch of stuff lol .

DirtyV and DirtyV-SR have both SmartReflex 1.5 and 3 .
[Samsung Galaxy Nexus] cujo6801:
How do you do I

think you've met my

faithful handyman

He's just a little (vagoing?)

because when you knocked

he thought you were the Candyman

Don't get strung out by the way I look

Don't judge a book by its cover

I'm not much of a man by the light of day but by night I'm one hell of a lover

Sent from the "DOG" pound

---------- Post added at 05:39 PM ---------- Previous post was at 05:38 PM ----------

PS name that song and from where

Sent from the "DOG" pound
[Samsung Galaxy Nexus] pattyboi:):
http://www.youtube.com/watch?v=pDKyj35ew0E ? :)
[Samsung Galaxy Nexus] cujo6801:
<br />

<br />

http://www.youtube.com/watch?v=pDKyj35ew0E ? :)[/QUOTE]

Hell yaeh...

You just went up in the cool factor!

Sent from the "DOG" pound
[Samsung Galaxy Nexus] Nephilim:
osm0sis, hoping you can help, I just flashed TWRP 2.7.0.0 yesterday, now when I try to nandroid it fails and says it can't locate storage or something along those lines. I've never has this issue before and I have a test build rom I need to try but I won't do so without a nandroid first.

Sent from my Android 4.4.2 Galaxy Nexus
[Samsung Galaxy Nexus] oubeichen:
You may try philz touch(xdaforums.com/showthread.php?t=2201860). TWRP nandroid backup is also supported.
[Samsung Galaxy Nexus] Nephilim:
The thing is I don't want to use a different recovery. I prefer to stick with TWRP, thanks for the suggestion though.

Sent from my Android 4.4.2 Galaxy Nexus
[Samsung Galaxy Nexus] osm0sis:
You maguro? Try the one I posted on my Dev-Host. It definitely works for me.
[Samsung Galaxy Nexus] cujo6801:
Nope...he's toro baby...

Sent from the "DOG" pound
[Samsung Galaxy Nexus] Nephilim:
Toro unfortunately, could you take a look at the image for me? I included it below.

https://docs.google.com/file/d/0B_HqOdvKZoQhUVg2Wkp3MzhDWEk/edit
[Samsung Galaxy Nexus] osm0sis:
Can't really tell anything from the image. Boot the recovery, attempt your backup then post me the log from cache when you boot back to Android. :)
[Samsung Galaxy Nexus] Nephilim:
What type of log do you need?
[Samsung Galaxy Nexus] bsmitty83:
The hub stuff is from some USB stuff that got rebased lol , I'm still working through everything , my brain needs a lmk ........
[Samsung Galaxy Nexus] Nephilim:
Like this?

https://docs.google.com/file/d/0B_HqOdvKZoQhYUVxcUlPWmJqTkE/edit
[Samsung Galaxy Nexus] osm0sis:
Nope. No idea what that is or where you found it. To be very specific, post /cache/recovery/last_log :p
[Samsung Galaxy Nexus] Nephilim:
I'm actually uploading it to my Drive right now, I realized what you needed right after I posted that lol.

Here ya go:

https://docs.google.com/file/d/0B_HqOdvKZoQhb296akRuQVpCNzA/edit
[Samsung Galaxy Nexus] DR3W5K1:
I just picked up a bag of "lowmemoryKILLER". Sounds like you could use a little. I'll share ;)
[Samsung Galaxy Nexus] omniatic:
Don't know where yours came from, but this is the one I used:

http://xdaforums.com/showthread.php?p=50934041

Ran the flashable zip, backed up and restored without any problems.
[Samsung Galaxy Nexus] Nephilim:
Mine has the splash shade themed, it's by z31s1g whom osm0sis has been conversing with and working with so that's why I asked him if he could help with the issue. ;)
[Samsung Galaxy Nexus] omniatic:
Oh...
[Samsung Galaxy Nexus] pattyboi:):
Hell yaeh...

You just went up in the cool factor!

Sent from the "DOG" pound[/QUOTE]

Lmao,thanks bro :good: glad to know someone else remembers that ,heard that when I was lil :silly:
[Samsung Galaxy Nexus] Nephilim:
Disregard, for some reason after updating to 2.7.0.0 it disconnected my storage on the backup page, once I ticked my sdcard again backup is working without a hitch. Goddamn that was annoying, I just spent the last over an hour trying to figure out what was wrong with TWRP lmao!
[Samsung Galaxy Nexus] Ashtrix:
Guys, As my personal experience goes the 512MHz OC step for Galaxy Nexus is wastage of battery with a minimal improvement like say a ~5% of boost (I lost the thread stating the powerloss with the OC) & [MENTION=3685904]ak[/MENTION] also made his last kernels have only 384 step, I ran NFS MW on both and bam !! *null* improvement plus adding to that it gets hot more due to higher powerdrain, Best bet is to stick with the 384 clock only ;) !!

Here, ppl say the same thing !!

P.S : [MENTION=4608636]bsmitty83[/MENTION], the F2FS page at dev-section just got updated. It might be of some help if u have a look there....!
[Samsung Galaxy Nexus] Carlos_Manuel:
I know that bLE works on tuna. I am not using any fitbit.

On 3.4 kernel BT has some nice BLE features like e.g.:

bluetooth: LE conn whitelist implementation

I don't think that I ported 3.4 kernel's BT files correctly to the Tuna's Linux 3.0.101 kernel, but so far BT works fine

Just included /drivers/bluetooth/ too... No building errors
[Samsung Galaxy Nexus] Carlos_Manuel:
These may be helpful or the answer for your question? :)

https://github.com/AOSPA/android_kernel_samsung_tuna/commit/176fea35b97e24df9fab09a5f6c1c65fe9974f37

https://github.com/CyanogenMod/andr...mmit/68bbfe572d39615a2d523e22f652fb5d638e7f2f

https://github.com/CyanogenMod/andr...mmit/ece569c5a019ef6cc6751cd5e5e02eebf207c82e
[Samsung Galaxy Nexus] dbh369:
Warm reboot on smitty 3.10, maybe old news, logs here

https://app.box.com/s/f29slkcrhoxdddiuuco4

BTW, every time I swype smitty, Swype puts in smutty...the nerve!
[Samsung Galaxy Nexus] bsmitty83:
Lol ......

I've been following most of the issues here and will try some things out . I did read from one of the tuna developers that the bottleneck in the GPU is bandwidth , not freq . 512 MHz uses the same amount for it and 380mhz , that's is why they don't recommend the 512 slot
[Samsung Galaxy Nexus] AquilaDroid:
If anyone else has this problem, try deleting the .twrps file in the TWRP folder. It will be recreated the next time you run TWRP.

From my Nexus 5