Not yet. It’s still in the queue and I believe it should be fixed in the next firmware update.
I understand not wanting to do a firmware update before a gig, but there are several other improvements and fixes between 1.5.0 and the current 1.7.0 that are worth doing the update.