@FiiO Hi!
After installing firmware 1.0.7 the ghost came back. False touches started to work again. This happens when the player is working intensively - downloading files, playing music and surfing the Internet. What should I do?
Great description of the problem; brilliant to go to some effort to ‘nail’ when it is happening.
So, erm, doesn‘t this perfectly mirror the previous occasions when the problem would arise.
It looks like the digitizer requires ‘a certain amount of math’ (think:CPU runtime) in order to work flawlessly- when it doesn’t get that ‘requisite’ math space, it starts to muck up.
My ‘tongue in cheek‘ to ‘what should I do’, was, “do less”!
I know this isn’t a solution you are looking for, but what other seem logical would not be ideal for many, perhaps-
If the system is ‘optimised for music’, and, for whatever reasons, FiiO has assigned a low task load to the screen digitiser ;so it works fine, with exception to ‘newly setup units that may be re-cataloging a large music collection AND playing compressed music files etc, then it hits its ‘assigned CPU limit for the digitiser’.
At this point, I’d be seeing ‘how close to the limit’ it can be pushed; eg playing back WAVE files (*.WAV) requires close to ZERO cpu grunt; so ‘can you get away with playing WAVs and webbrowsing (and downloading files etc).
Check at what point of the download it starts to cause issues eg is it as the download finishes- at which point an antivirus pass might be happening, or a decompression (or at the least ‘doing a larger file write to disk, eg some OSs would move a cache location ‘download’ to another area on completion of download).
I’d say you
mostly have this figured, and if we can take it a little bit further then we as a group /FiiO techs know exactly what to tweak to ‘get over the line’.
I prefer targeted solutions that hit the nail on the head, rather than blanket changes that ‘might go to far’.
I love how the unit sips power- I have had it playing, via COAX output for DAYS, 24/7, and the battery just ‘sips along’.
It wouldn’t be impossible for the software developers/engineering team to come up with a ‘high performance’ button that changes things up and allows ‘a little more CPU grunt’; but -EVEN BETTER, would be if we can figure out which processes are ‘on the verge‘ of causing the issue, or affect it the most..
eg if downloading isn’t the ‘true issue’ but file read/writes ARE, then they know which workloads to assign to dedicated cores (etc) that allows for the battery to continue to be ‘sipped’ AND deliver seemingly better performance.
(like how Forza horizon 3 used to run bad on PC due to the workload being put MOSTLY on ONE CORE, which limited ultimate performance; when the software team know how to better distribute workload, they can ‘do wonders’. It isn’t as easy as I suggest, but ‘more information’ can easily help (sometimes))
I’d say many users do not use the M11+ in ‘heavy ways’, and the only time I have had the Ghost touch issue (or ‘poor touchscreen control’), was under ‘very heavy load’, a lot of it being ‘in the background’.
Using WAV files is higher READ hit from the drive, but a very minimal CPU hit, and could help BURDEN ONE SYSTEM (drive Input/Output), whilst freeing another (CPU USAGE).
I’d suggest -keep doing as you are doing, and try WAV files and their effect, for starters. Mayhaps pay attention to whether big downloads ‘mid download’ (~CPU, but less intensive drive I/O) are negative hitters, or if it is ‘multiple downloads’ & ‘download completion moments’ (lots of drive I/O, and heavier cpu especially if antivirus kicks in)that are impacting most.. (and WAV files will UP drive I/O, which may exacerbate the issue too)
I bet this fairly simple observation process could ‘take us further’ in understanding the underlying issue(s).