Closed
Bug 737098
Opened 12 years ago
Closed 12 years ago
Physical events values are not displayed on FroYo devices
Categories
(Firefox for Android Graveyard :: General, defect)
Tracking
(Not tracked)
RESOLVED
INVALID
People
(Reporter: xti, Unassigned)
Details
Firefox 14.0a1 (2012-03-19) Devices: HTC Desire, LG Optimus 2X OS: Android 2.2 Steps to reproduce: 1. Open Fennec 2. Browse to http://dl.dropbox.com/u/8727858/physical-events/index.html 3. Check if values are displayed and updated for each event Expected result: Values are live updated. Actual result: No value is displayed.
Comment 1•12 years ago
|
||
Any errors or failures in GeckoApp in logcat?
Comment 2•12 years ago
|
||
The HTC Desire might not have either a gyroscope or an acceleromator so it's expected that the values for each event would be blank.
Reporter | ||
Comment 3•12 years ago
|
||
(In reply to Aaron Train [:aaronmt] from comment #1) > Any errors or failures in GeckoApp in logcat? I didn't notice anything related to this issue. (In reply to Aaron Train [:aaronmt] from comment #2) > The HTC Desire might not have either a gyroscope or an acceleromator so it's > expected that the values for each event would be blank. Regarding to http://www.gsmarena.com/htc_desire-3077.php, it seems that Desire has both accelerometer and gyroscope (compass).
Comment 4•12 years ago
|
||
Does this work under the stock browser? compassneedscalibration, deviceorientation, devicemotion
Reporter | ||
Comment 5•12 years ago
|
||
(In reply to Aaron Train [:aaronmt] from comment #4) > Does this work under the stock browser? > > compassneedscalibration, deviceorientation, devicemotion No, it doesn't. It seems that's not working on any FroYo device both on Nightly or stock browser. -- Firefox 14.0a1 (2012-03-23) Device: Samsung Galaxy S OS: Android 2.2
Comment 6•12 years ago
|
||
Sounds like something introduced in Android 2.3
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → INVALID
Assignee | ||
Updated•3 years ago
|
Product: Firefox for Android → Firefox for Android Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•