The user should be able to see quickly the state of the mobile connection and the remaining battery.
The current implementation requires a half swipe up to view this info.
Together with the lack of notification events when the connection is lost or the battery is too low leave the user in uncertainty.
see also issues:
| 2 | retagged |
The user should be able to see quickly the state of the mobile connection and the remaining battery.
The current implementation requires a half swipe up to view this info.
Together with the lack of notification events when the connection is lost or the battery is too low leave the user in uncertainty.
see also issues:
| 3 | No.3 Revision |
The user should be able to see quickly the state of the mobile connection and the remaining battery.
The current implementation requires a half swipe up to view this info.
Together with the lack of notification events when the connection is lost or the battery is too low leave the user in uncertainty.
see also issues:
| 4 | retagged |
The user should be able to see quickly the state of the mobile connection and the remaining battery.
The current implementation requires a half swipe up to view this info.
Together with the lack of notification events when the connection is lost or the battery is too low leave the user in uncertainty.
see also issues:
| 5 | No.5 Revision |
The user should be able to see quickly the state of the mobile connection and the remaining battery.
The current implementation requires a half swipe up to view this info.
Together with the lack of notification events when the connection is lost or the battery is too low leave the user in uncertainty.
see also issues:
| 6 | retagged |
The user should be able to see quickly the state of the mobile connection and the remaining battery.
The current implementation requires a half swipe up to view this info.
Together with the lack of notification events when the connection is lost or the battery is too low leave the user in uncertainty.
see also issues: