kevg 14 Posted March 5 Share Posted March 5 (edited) This post isn't specifically about F(x)tec as I had the same problem with Unihertz. I got my Pro¹X about a month ago. I was excited. I love the keyboard. It's fun to whip out at parties. But it simply doesn't work. I mean, the most basic function of making a phone call: sometimes, the caller can't hear me. My issue isn't with the technical problem. It's a new phone, and hardware and software are hard. That's understandable. My issue is the lack of working with users to solve problems and the poor prioritization of issues. Companies can be forgiven when a user reports an issue but the user can't reproduce it and gather diagnostics.. This is not an excuse with me. I've been a programmer for 20 years and I made it clear I'm glad to gather diagnostics or run custom diagnostic builds. I can reproduce the problem easily. I opened a support ticket in mid-February with logs. It was acknowledged, and I haven't heard back since. I have continued to send logs and new details as I've discovered them myself, and I've heard nothing. Again, this isn't about F(x)tec in particular. I had the same problem with my Unihertz. I had a Titan Pocket and the WiFi would constantly drop out. Again, I understand these issues are complicated, but I gave them the same offer: I wanted it to work and I'm a professional that can run debug builds and diagnostics for free. I heard back essentially nothing. I escalated to any email I could find at Unihertz and heard back nothing, so I returned it. If a phone is failing at a core function, and a user shows up at your door who can reproduce the issue, is technically competent, and is eager and willing to spend their precious time to help fix the issue for free, you should prioritize this issue above nearly everything else. You should respond to them and send them a diagnostic build to gather additional logs. We know you all have limited resources, but this isn't complicated (in the sense of how to interact with users and prioritize issues). This isn't just my issue and has been confirmed by other users. I spent most of yesterday adding pr_warn log statements to kernel/fxtec/sm6115/techpack/audio/dsp/q6voice.c to try to figure out the "voice_get_cal: No cal data for cal 8" and "voice volume failed" errors (which are not seen when the issue doesn't happen), but ultimately the calls go to apr_send_pkt and I don't know where to find the source of the other side of this call. More broadly, reverse engineering all of DSP and APR is just too much for me right now. I already tried switching to fluenceplus which didn't work. I bought another phone last night. I won't return or re-sell this phone in case F(x)tec wants to gather more diagnostics, and I can pop the SIM back in and gather data. The independent, open source phone industry will die or be totally irrelevant unless it works with eager users like myself and properly prioritizes issues by severity. Edited March 6 by kevg Clarify 3 Quote Link to post Share on other sites
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.