dejanh
New Head-Fier
- Joined
- Jul 24, 2016
- Posts
- 5
- Likes
- 10
Yeah, it really sounds like the DFR (and for that matter, likely the DFB as well) could benefit from AQ investing some more time into to the firmware implementation. Two posts up somebody mentioned that the nature of iOS CCK connection is that it is always on. I would have to partially disagree with the implication of this comment.
The "consumption" of power is a function of the device that is being powered off of the phone, meaning that even if the connection is an always-on connection, the hardware on the other end of the CCK connection should be able to enter low-power states that reduce battery drain while still maintaining an active connection. I am certain that there is a problem with the DFR implementation but I'd like to know if even one person actually sees their DFR in the "red" standby state when plugged in to an iOS device, just to rule out a hardware fault.
The "consumption" of power is a function of the device that is being powered off of the phone, meaning that even if the connection is an always-on connection, the hardware on the other end of the CCK connection should be able to enter low-power states that reduce battery drain while still maintaining an active connection. I am certain that there is a problem with the DFR implementation but I'd like to know if even one person actually sees their DFR in the "red" standby state when plugged in to an iOS device, just to rule out a hardware fault.