OTA-17 Call for Testing Companion Post
AppLee last edited by
I also have a Nexus 5.
@keneda I've already left a comment. I don't think it's related to the linked issue. That field is weird. I tried to type on it until I realized you can't How does it even work on Android and iOS? It just happens that the OSK can simulate the arrow keys so it works on UT.
Yes i saw your answer and answered back.
I tried to type on it until I realized you can't
That's what i tried at first, a year ago or so, but i only succeeded with selection mode.
On Firefox (W7), both typing number directly (numpad or so) and using arrows works (but not the mouse wheele). On morph, only the "simulated arrows" works ^^
@keneda I tried on my android phone. It has a special input method for the time field. It's either an actual clock widget or keyboard input but the fields are in a popup dialog. Not sure if this is something UT can support or specific to android/iOS. Sadly, the cursor mover isn't made for arrow key simulation so your issue may not be considered a blocking point for the issue I linked you to.
This is sad because as you can imagine, that's not the only website that has time input field, and also because for the time being, this particular website is quite mandatory to be usable, even on uTouch.
But i still can use it with this issue, it's a very annnoying behavior, but i can do with it.
The "arrow key simulation" may not be intended, but is very helpfull.
@keneda That is true. Just setting the expectation Like you said, you can still use it. Just need to tap each
But it's good that you reported. Let's see if something can done.
Just need to tap each
Taping each is not a problem, that's the closing of keyboard if you don't swipe very linear that is annoying ^^
In fact, it even would be better that your selection part in the field (hours or minutes) remain captive, i mean, that you can't swap directly from hours to minute, but need to tap, because it often came that you change minutes when you want to change hours and opposite (but that's better than keyboard closing).
Thanks for your help
messayisto last edited by
@lakotaubp thank you - I think I'll stay on the halium devel channel... - will they come together someday?
mihael last edited by
I use a Pro 5 (turbo) on rc channel. In the last week or so I saw a high cpu usage from NetworkManager regardless of wifi being on or off or even flight mode on or off. The average cpu usage for NetworkManager is 17%. It goes from 0% to over 60%. This results in batery drainage. Could this be related to recent changes in the rc channel?
Lakotaubp last edited by Lakotaubp
@messayisto The move to halium is planned for a few more devices in the near future. So should become the norm on those devices.