I bought a Gauntlet 320 back in February 2013, for use (mainly) with my rooted Nook Color running Cyanogenmod when away from my home network. From the very start, it had what I considered a minor issue - wifi connections would die about 6-8 hours in, when streaming MP3s to the Nook. (Using the power adapters for both devices, obviously - no magic "overtime" batteries here.) "Die" in this case means the wifi connection would still be visible, but no actual data transfer would occur; as well, new connection attempts (or reconnects from the previously-connected device) would fail with authentication errors - as if the connection had "locked". The device did get somewhat hot (not too hot to touch) in the area directly behind the printed "battery charge" icon on the top cover, and I assumed that charging it while running streaming media over wifi was overheating a component, and so I limited my overall usage time - this seemed to work, and I've had no significant issues until recently.
Within the past six weeks or so, the Gauntlet's time-to-lockup-when-streaming has decreased dramatically - randomly occurring anywhere from the original 6-8-hours timeframe, down to two hours or less. (Using the Nook Color/Cyanogenmod 10.1 or higher, or using my laptop running Windows Vista Home/Win7 Ultimate.) As well, upon powering up, the disk-activity light began to turn on and start steadily lit - as opposed to the normal "flickering" behavior previously observed. Direct USB connection and error-checking/drive analysis showed no significant errors, and no change was noted after corrupt files were removed. The drive shows as 4% fragmented, with 93% in use.
Last week, I purchased a Samsung Galaxy Tab 3 7.0 tablet (stock Android 4.1.2), and attempting to stream MP3s to this device results in audio dropouts (ranging from about half a second to 5-6 seconds or more, followed by the resumption of playback), beginning within the first few minutes of streaming and continuing indefinitely until lockup occurs approximately 2 hours after streaming begins. As well, straight data-copying, to or from the Gauntlet, will randomly either run steadily, or suffer very frequent "recalculations" as to file size/completion times, with a wide variety of speeds ranging from 300 kb/sec or higher, all the way down to 9 kb/sec at the slowest observed. (Audio dropouts were previously only observed when nearing the "lockup" time when streaming to the Nook or laptop, after a much longer period of time. Erratic data transfer was not observed until recently, and neither issue is occurring when connected via USB. The Nook and Tab 3 do not exhibit this behavior when connecting to other wifi sources.)
The Gauntlet firmware was updated to V21_1.2.4.5 after purchase, and this past weekend was updated to the latest version (V_21_1.2.4.6). No change was observed. This morning, I did a factory reset via the pinhole, and manually reconfigured the device. No change was observed. The same kind of audio drops occur when directly under high-voltage power lines, but stop when I move not less than ten feet from directly below. (Data transfer issues have not been tested in that location.) I utilize the Patriot app strictly for settings changes on both the Nook Color and Tab 3 - data transfer on both devices use ES File Explorer, media streaming uses BSPlayer or Neutron. (Laptop transfer is via Windows Explorer, media streaming is Winamp and Media Player Classic.) Direct wifi connect to the devices only - no passthrough has been used.
The feeling I'm getting from this is that the wifi signal or actual hardware is getting overwhelmed - even now, the Nook Color (which is much less powerful than the Tab 3) handles the dropouts/transfer glitchiness better; I'll try a wifi-throttling app if I can find one, just to see what happens. Media quality is set the same for both Nook and Tab, so it's not as though I'm suddenly trying to pull HD video when I'd previously been pulling low-res.
Is it possible that the Gauntlet's firmware is trying to write to some godawful-huge-by-now logfile hidden away somewhere? That might explain the solid drive activity on boot...