Leaderboard

Looks like the suspicion I wrote about earlier was correct. Since I disabled "4G calling" (HD voice aka wideband audio) in "Network and Internet" -> "Mobile Network", I didn't get any calls anymore with too loud in-call audio. I'm quite confident about this now as one specific caller which always used to be too loud when calling from his home line wasn't too loud anymore after I made that change. So far I don't see any disadvantages of that change, either. [Edit:] This is LineageOS 17.1. Sorry I didn't mention this earlier...

I don't kow if it is related to VoLTE but that is not available for me (however, the service provider supports it). Anyway, I have to turn speaker volume to lowest level and I still feel it is sometimes too loud - however, when speaker volume is higher, it can even have distorted audio because it is too loud also for the speaker (and overdriving the speaker it is generally not a good thing at all). Otherwise, there are solutions which are louder while others are relatively quiet. ...like when I have tested my Pinephone for the first time, its output (at other party) was extremely loud

i don't seem to have this feature : "4G calling" (HD voice aka wideband audio) - but i definitely experience this very loud audio volume with certain callers, notably with one that uses a landline phone as you observed too. are the settings under "Mobile Network" perhaps carrier specific ? my phone/data service is with Bell Canada.

You backed them via IGG if I recall correctly. You can't compare the two. I'm not agreeing with how things work. Spec changed, I would want my money back too. But, you bought via IGG. After a backing term has passed, this money is used to start up. New design = startup. IGG backing = basically no rights, not afterwards at least.

Good morning everyone, The credit was transferred to my account "immediately" after my post here. In any case, I received an email from f(x)tec within a few hours and the money arrived in my account in Germany via TransferWise the same morning. I'm talking about 13 January 2021, the day I started this thread. Greetings from Germany kabay

I waited over a week between using the https://www.fxtec.com/contact-us form and sending the e-mail to info@fxtec.com, and then I waited another 2 weeks between sending that e-mail and making this post. Is the queue to receive an acknowledgement of my message normally that long? Given that the contact form says that they "aim to get back to you within 24 hours," I figured that a week (and then two more weeks) was a reasonable time to wait for a response.

I've sent a couple of e-mails through the support form on the website and by directly e-mailing ionfo@fxtec.com, but I haven't heard back after several weeks. Is there any other way to contact Fxtec for hardware support on my phone? Thanks.

Hi all. Been using my pro1 ever since this good community helped me to fix software hitches. Thanks again 😉 So now after about a half year, the right side hinge (at the screen) started to become loose at open position. It rattles about half a millimeter; I wouldn't care about it much but it's started about two months ago with a barely noticeable wiggle and has gotten worse. I am pretty sure out of warranty now (unless you get a new full year warranty with a replacement unit?). Did this happen to any of you? This is not related to any fall (experienced my first fall just two days ago, doh) o

Yes, I have tried that.

The same applies for me... I hope my current Pro1 will last for a long time anyway. Also, if it will have a "UFS flash chip issue", I may find a way to replace that chip (potentially with a 256 GB version) if a Pro2 will not come up by that time... and I may also do it if I will buy a Pro2 anyway. 🙂 I am mostly afraid about two potential hardware issues with Pro1: - Screen breakage without a potential replacement - Flash worn out issue (which is normal for long-term usage but a very bad problem to have)

Same here, I also took a perk for a Pro1X, to get an (even) more powerful Pro1 than I already got. So I have a strong suspicion that it is only going to be my daily driver, when support for 835 Pro1 dies out, from various developing sources. But that is the risk of crowd funding I took..

I'm on LineageOS 17.1. Changed title and first post accordingly... Sorry for not mentioning it. My partner's Fairphone 3 (stock Android 10), same carrier as me, doesn't seem to have the setting, either.

Excellent!

Conference call works for me without VoLTE.

Glad to hear that they can be so swift, when they are not swamped in a lot of pending mails. 🙂 The chronology of this date indicates that it was before they found out they had been swindled on the 835, with all the following commotion.

same here, is it a LOS thing?

Giving this a try, thank you! :)

Indeed. But as they just discovered the mail-setup bug @Hook described a few days ago, they might well have a pile waiting there. 😥

Bitwarden should work with Fulguris once the following changes are merged and released: https://github.com/bitwarden/mobile/pull/1333 I can't tell you how long that will take as I'm not familiar with the bitwarden project. I've tested those changes and it seems to work nicely.

Also, last week their exchange email servers were hit. On IGG they posted: So may have been a double whammy.

that's the isssue, there are no bushings. Maybe should start fabricating some, will be much more simple compared to making new screws. couldn't agree more, and as a micro mechanics engineer and watchmaker it really bothers me

Just started happening. Call rings through, but the screen stays dark. There is no ongoing call notification. Also when I try to touch the button to turn on the screen it ends the call.

No. It literally does the same thing a battery pull would do. Doesn't touch your apps. I don't know exactly why it solves problems, but I know in the old days pulling a battery from a phone (like blackberries) would also solve wonkiness often.

Thing is the calls are coming through but just no call answer option. It's very odd. And I am using Contacts+ not stock Android. Guess I'll have to play with the settings more.

@Erik Any idea?