Q: iOS 8 Calendar on iPhone showing GMT times for new events.

Same here!  It works!  No more GMT!  Woooooooooooo!

Still doing it here.  But I am on Exchange, not Google.  Would be really helpful if people, when they state this is fixed, could indicate what Calendar service they are using to sync.

If this is 100% working on Google now, my guess is that Google changed something on their end, not that Apple has fixed anything.  And I would speculate further is that what Google did, is to block the server's time clock setting from being shared to any clients.  So iOS is still trying to pick it up, but there's no data so it can't complete screwing up you appointments.

Sorry if I wasn't clear about being on Outlook using Google Calendar syncing.You are correct, anyone who has the GMT issue resolved should state what there basic set up is. I have Outlook syncing with Google Calendar and iOS 8.1.3.

Appears to be working correctly here.  Setup is iOS syncing directly from Google (Mail/Calendar/Contacts) running 8.1.3.

Interesting—me too! I no longer have the GMT bug. I wonder what changed? Certainly nothing I did.

edit—I use Google Calendar under Win7Pro and iPod Touch 5 with iOS 8.1.3.

Jeremy

Working here as well.
iPhone 6, GCal.

Again please tell us what your setup is when you report that "it is working."  Without that info, we have no idea what is working.  In this case I am going to speculate jeremynichols is using Google Calendar to sync.  Am I correct?

By responses so far, the "fixed" calendars are exclusively those syncing using Google Calendar, not MS Exchange.  This pretty much confirms that some change was made on the Google system, not anything in iOS.

Congrats to all of you.  Seriously that is great that Google stepped up and did something to fix this.  The rest of us who use Exchange, are still screwed for the time being.

This is definitely a fix by Google. I have another calendar URL that I've subscribed to/added in GCal. Iphone is still showing that one as GMT. I tried removing it completely from iCal and GCal, then readding it, and it's the same.

I 100% agree.  Is there anyone else out there besides me syncing using Exchange (not Outlook using Google to sync but actual Exchange like on a corporate server or hosted account like Office 365) that can confirm whether or not they are still seeing this bug?

I am near 100% certain Apple hasn't done anything to address this.  Google did something that keeps Apple's still-buggy iOS code from being able to acquire the server time zone setting and since the bug can't get that, it can't "do its thing" and screw up your appointment times.  This is the same reason the GMT Bug didn't show up on various Yahoo and Hotmail accounts earlier....those protocols don't supply the server time clock setting to clients (i.e. you iPhone, iPad, iPod etc.).

With all the Google Calendar users problem addressed by Google, I doubt Apple is ever going to do anything to fix this for the rest of us.  They will revert to their new corporate mantra of "Thanks for being an Apple customer, and for giving us your $$$$, now go f^#k yourself."

Sorry, JG. You've been our unofficial leader in this crusade. Apparently this problem hitting the blogs have spurred some kind of a solution for the Google sync user. I guess with Exchange there isn't a way to find out what Google did and implement a fix. It's dependent on Apple. And now BGR (BGR.com) is reporting that 8.2 is not scheduled to be released until March to coincide with the release of Apple Watch.  Sorry you are still having the issue. Hopefully it gets resolved for you soon but thanks again for helping out all of us.

You are welcome!!  I'm glad my brain damage on this issue has potentially helped others even if it hasn't helped me yet.

It IS looking promising that perhaps this will be fixed for EVERYONE in iOS 8.2.

There's this:

http://www.iphonehacks.com/2015/02/gmt-bug-in-calendar-app-fix-in-ios-8-2.html

And then this:

https://twitter.com/Shawzborne/status/562342320717455361

I don't have too much of a problem waiting until March as long as I know there's a fix coming.  It's the total lack of any official confirmation from Apple that has really set me off....along with so many other users.  Bugs happen...even to self-proclaimed-infallible Apple.  It's Apple's decision to lie to its customers about it, have their tech support staff tell everyone "we've never heard of this before," claim it's a "feature" etc. that I find infuriating.

Yes, Google Calendar—I edited my post to add that information. Thanks for the reminder.

@JG in SB I am using two calendars on my iPhone the first is Outlook 365 which I use for work and was provided by my employer, the second is Google which is on my Google account and is for personal use (I rarely put items on the iCloudg calendar which came with the iPhone).  I am on iOS 8.1.3.  Google is the default calendar in my iPhone 6 Plus settings.

I did not, and do not now, encounter any problem with my Outlook 365 calendar. 

I had encountered the GMT issue with events created on my Google calendar reagrdless of the event being created on the iPhone or desktop.  First time I created an event after the iOS 8.2 Beta claim of fixing the issue was today, and the problem had disappeared for me.

I think that it is unfair towards Apple to claim that it is not their doing.  I don't know if it is or not but it is coincidental with the release of iOS 8.2 Beta.  As you pointed out yesterday the release notes say that the issue was fixed. 

Claiming that Apple did not do it implies that the fix must be on the client side, namely individual iPhones and iPads.  But it is quite possible that the issue was buried on some servers and that it indeed was fixed by Apple.  Assume for a moment that the client devices, iPhonea, iPads and iPods communicate with an Apple server which then in turn communicates with the Exchange or Google server and that the code on these server was changed by Apple.  There is no evidence that Google did anything, nor is there evidence that Apple did or did not do anything to fix the issue.  I doubt we will ever know but we do not know enough to reach a conclusion that it was Google who fixed the issue and that Apple has done nothing.  I think they should be given the benefit of doubt.