Jump to content

Leaderboard

Popular Content

Showing content with the highest reputation on 03/05/2023 in all areas

  1. 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 bu
    2 points
  2. I should add an update that the problem is currently consistently happening. I tried switching to fluenceplus by changing device/fxtec/pro1x/vendor.prop and rebuilding but that didn't help. I noticed some SELinux errors early in the boot so I also tried compiling in new_value=0 in SELinux to always make it permissive, and that made the symptoms of the problem slightly different but ultimately the same. I'm kind of stuck because ultimately the q6voice.c calls make a call to apr_send_pkt and I don't know where the source of this is.
    1 point
×
×
  • Create New...

Important Information

Terms