(10-08-2020, 04:19 AM)lot378 Wrote:Piggybacking on this:(10-08-2020, 03:01 AM)a-wai Wrote:(10-07-2020, 02:53 PM)lot378 Wrote: Please provide a breakdown of the issues encountered with EG25-G for the benefit of the community because they/we are all interested.
Reading through https://xnux.eu/devices/feature/modem-pp-reveng.html already provides a good explanation: there are at least some developers at Quectel who are very poorly skilled and don't really know what they're doing (based on the unreasonable amount of system() in the firmware code).
On top of that, the latest 2 firmware releases both state (pages 8+11) that they "Solved the problem of USB disconnection" (spoiler: nope, is still there).
Because yes, the modem issues (missed call, no more mobile data...) we have when resuming from sleep are entirely due to the modem resetting the USB connection on its side and its QMI interface vanishing (AT commands still work as they use another interface, but only for calls and SMS).
The problem isn't that we don't understand how the modem works, but that (for now) it just doesn't work as it should. They're obviously aware of the problem and seem to be working on it, so there's still hope that modem issues will be solved within a few months (years?).
Thank you. I'd agree that's some pretty lazy programming to use system() calls to echo values in to files (besides the security risks that are obviously inherent). It seems to me Pine64 need to appoint a project manager to get the Quectel issues recognised resolved tested deployed to updated firmware, otherwise expect them to just roll around making the same mistakes like its groundhog day.
If as believed by the Devs, the core firmware of the EG25-G is fundamentally flawed, then it would appear that it's time for Pine64 to depart from its volunteer community based software development at least as it pertains to this issue.
The powers-that-be at Pine should attempt to address the modem's problems with Quectel and obtain some type of solid NDA agreement of cooperation and information sharing, and then commission a qualified developer to begin fixing the EG25 problems. Seems like its worth a try anyway.
