- Posts: 121
- Joined: Mon Mar 17, 2014 5:13 pm
Hi Patrick,
This is a known bug in firmware 4.4. You can rollback to 4.3.3, or just use your workaround until they release the next firmware update.
Adam
Users browsing this forum: No registered users and 156 guests