EskeRahn

Yes, any good suggestions?

They also got a "FiLMiC Pro Evaluator" that is free, running that all are ticked (except OIS) including "Audio Gain", that I guess is what we are looking for.

When you guys see the phenomena, does it do it both opened and closed? Could it be the ribbon cable between the two halves that gets issues over time? If it appears both opened and closed a wild guess could be if a pin of some sort over time is eating its way through some insulation of say a cable? That it gets triggered by a (gentle) press could indicate something like that.

Please read again. The point is that you apparently need to shut down bluetooth before any changes attempted on the Codec in Developer Options takes effekt. It could make sense if they only look at the settings when bluetooth is started, and do not monitor any changes we may make later on.

I found something that might be related here, someone suggests to turn off Bluetooth before changing the setting in developer options - worth a try. Most likely you should also make sure that it is un-paired if it shows up as paired (though not working), as it might else remember the APTX for the device.

Try "Developer options" , "Bluetooth Audio Codec", and try one of the many options not mentioning APT-X HD.

If you prefer a more pure Linux experience you should know that an ubuntu port exists. I'm not sure how far it has been developed though.

Maybe @Rob. S. can help? He has been using it

Please enlighten us which one, if others want to experiment 😉

If used hand held (and that is not uncommon for a phone) fumbling with the device it self will unavoidably cause some noise, and my guess is that is the reason for the cut off. But sure it could make sense to give the user more control. It could be the same cut-off level that make the device hard to use for hands free calls, unless you raise your voice to 'meeting level'. So might be deep in the microphone driver/circuitry,

You need a noisier washing machine.... 😇 There seem to be some sort of cut off level so that at levels below this nothing is recorded. In some contexts that can make a lot of sense but in others not, so what is lacking is a way for the user to select this level.

A very cheap and simple solution could be to find a suitable small plastic back to stick the sleeve and phone in while at work. It will also be easier to change/clean than most sleeves/cases

This seems to be related to the specific dated router model Huawei B525s-23a! Half a day ago I tried to change the Pro1's connection to a newer Huawei router (B535-232), and it seems to make a HUGE difference. I will need more time, but I currently estimate that that the consumption went down around 0..5%/h, but take that number with a BIG pinch of salt for now. (Confirmed over a 12h time span). Just wanted to state that it is NOT the Pro1 as such, but the combination that is the issue, so if amyone see a disproportional drain, you might want to consider to upgrade your router. (th

Due to the nature of the sleeve it will not protect the open end from dust. So for a "very dusty environment" I would suggest to find/make a deeper sleeve, where you can fold over the excess end to better protect the device. (Not only for the microphone and speakers)

Are you sure It is the "Andriod security patch level" and not the "Vendor security patch level"? Here the first says Aug 5, and the second Sep 5 (as it was last week too).

The sound is the small support arm when closed. Try the shake when open. Can be remedied with a tiny piece of self adhesive felt or rubber, as described in other threads. The end of the sim tray can wriggle a bit compared to the tray itself. But not to the extent it can rattle on my units. Try holding a finger on is while shaking to eliminate as a possible culprit.

And as you said earlier it MIGHT be worth a try to use a different port, a USB-hub and/or a different cable. And as you guide also point out EDL mode must be reinitiated on the device between each attempt.

Yes, it is one step 'deeper' as I understand it, but @tdm is MUCH more knowledgeable on this...

From other posts, it should be rather picky on port, driver and cables. So try changing, perhaps using a hub. For another flashing tool I made this initial quide 1) The Pro1 must be unplugged 2) Power off the Pro1 3) Connect a usb-cable to the PC but NOT the Po1 4) Hold both volume keys while 'immediately' inserting the usb-plug

These certainly explains why it will not boot... But how to get out of this mess is another matter.... If anybody can use it, the similar from mine (on stock) is attached. fastboot getvar all 2>fastboot_getvar_all.txt fastboot_getvar_all.txt

I just split it to a new thread: https://community.fxtec.com/topic/3129-unwanted-notifications-on-cellular-connection-status-change 🙂

Yes let us hope it is 'merely' a damaged display. I have had the pre-production unit without phone and gps since spring 2019, the "Final sample" a year, and the retail unit since November, only having something related when using a no-name charger I'm preferring (both low and high current in same charger). BUT I can sometimes interact with the screen some ½-1mm above the display, so the touch is VERY sensitive. And I guess the humidity of the air and fingers could matter also as it is not always (today I need to actually touch).

I took the liberty to split this into a new thread. Feel free to give it a better title, (I just tried to summarize) And unfortunately I have not got an answer.

Just a thought, as I assume from the bank used that you are from Germany. The qwertZ model is "out of stock", so if you ordered that, they just MIGHT have put your order on hold. But just a guess. And as @netman said, you should ask support what is going on.

We can not see the bottom of the phone, is it connected? Mine reacts poorly to touch when connected to a third party charger (Does not see the pheneomeny when connected to a PC though, and do not use the original charger) Just to narrow it down. I do not see it as bad as on your unit though, here touches are misinterpreted, not spontaneously generated as on yours. But I still suspect sensitivity to static charge could be the mechanism causing both.