Device sensors are flaky - real orientation code needed #19
Labels
No labels
Doing
To Do
bug
clarification needed
duplicate
enhancement
help wanted
invalid
question
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
nik/veripeditus-server#19
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Device sensor data is very flaky and slow in Firefox for Android. Not sure if it's Firefox, Android or my device.
On Eike's device, no sensor data appears at all.
My device: SAMSUNG Galaxy Note 4 (SM-N910F), CM 12.1-20160711-NIGHTLY (Android 5.1.1)
Eike's device: Sony XPERIA M4 Aqua (E2303), Sony-Android 5.0
It is also unclear how to get more or less calibrated values for the alpha oreintation value. What we really need is the compass orientation the device is pointed at, be it when it is flat or held vertically. We need to find out which compass direction the camera is facing.
Note for (Hacktoberfest) contributors
Veripeditus uses Angular.JS. Maybe this is not a good idea at all. However, you can find a description on how we handle device data, etc. in commit
4c39f75bba. It is about loading game data, but basically, getting device information works the same way. Right now, Angular.JS only processes broadcasts from the DeviceService once per second, but that is another issue. What we do need is a way to get the real compass bearing from the alpha, beta and gamma values received in www/js/control/cam.js.Understanding the code base right now might be a bit difficult, but we will get you started on it and support you with all means. Just raise your voice if you want to help us ☺!
The speed issue is Angular's event system.
Closing because this is more or less contained in #15.