Opened 9 years ago
Last modified 9 years ago
#28 new defect
HTC Droid DNA - Helicopter won't fly
Reported by: | craigroberts | Owned by: | |
---|---|---|---|
Priority: | normal | Milestone: | |
Component: | Android | Version: | 1.4.3 |
Keywords: | Cc: |
Description
Followed all the directions. Bluetooth and IR connection appear to be working, signal is good, thresholds met, helicopter won't budge. The IR sensor is lighting up as if its sending signals but the helicopter hasn't shown any signs of life.
Please help
Attachments (1)
Change History (5)
comment:1 in reply to: ↑ description Changed 9 years ago by sc
comment:2 Changed 9 years ago by sc
- Summary changed from helicopter won't fly to HTC Droid DNA - Helicopter won't fly
comment:3 Changed 9 years ago by sc
Many thanks for that, report received:
Manufacturer: HTC
Model: HTC6435LVW
Product: verizon_wwe
Hardware: dlx
Device: dlx
Android Version: 16
So this is the HTC Droid DNA. I have the exact same phone here in front of me and unfortunately can confirm we are currently having trouble getting it to fly with this model (though we are actively working on it).
I will increase the priority of this as we know now we're not the only ones affected!
This ticket will be updated and I will attempt to email you directly as soon as progress has been made.
comment:4 Changed 9 years ago by sc
A Zip file has been attached to this ticket which consists of data files captures from a RIGOL DS1052E digital oscilloscope, comparing matching signals output from a known-working Google Nexus 7 tablet and a HTC Droid DNA phone (with signal inversion enabled).
Here is a photo of the oscilloscope:
These data files can be used to help determine why the Nexus 7's control signal successfully operates the Puzzlebox Orbit helicopter whereas the Droid DNA currently does not (as of version 1.4.3)
Replying to craigroberts:
Many thanks for the feedback Craig, we certainly appreciate you taking the time to file a ticket.
Would you please mind quickly using the feedback form found under the "Support" tab of the software interface so that we can collect the hardware, make and model details of your mobile device? You don't need to provide lengthy details, just a name (or initials), email, and maybe "28" as the body so we know it is in reference to this ticket?
We try to keep track of which hardware we encounter and any issues in this wiki document: OrbitDeviceCompatibility
The most obvious things to try are:
Hopefully one of these will help (if not attempted already) but if not reporting the hardware information will definitely aid us in debugging remotely.
Cheers