I think its a bug in the new 1.1.1 firmware. see 1st post in link where @Morelli noticed this as well.
1.1.1 firmware bugs