DieBruine

I would suggest you walk through these steps. Then you can be assured everything is as it should be. I cannot comment yet on the updating to last versions part. Clearly you had issues with that step. So I would suggest you first try it with this version, and immediately after that go to LOS. And depending on which version of ADB you're using, the command changed from "fastboot oem unlock" to "fastboot flashing unlock". Maybe you hadn't noticed that? BTW, I am unable to use SDB over USB C. Luckily my laptop still has one USB A-port. Which by the way is USB 3.x. Sidenote, after downl

I would suggest flashing stock and then go to LOS.

@Erik Could you clarify?

This did not happen on stock. I've only been running LOS for two days now. And I performed a hard reset before. It's the same as with the DOuble CAP as you can see. I'm just the opposite, I type pretty fast. And it looks like it happens more often when I type faster. And I uld alsobelieve it happens when under load. You see what happened there? That's not a typo, this is what happens when I type fast for a longer period of time, at least that is what I think. On the other hand, the sentence before this one, I tried typing as fast as I could, no errors... So, i have absolutely no idea as t

I'm experiencing some keyboard issues with LOS. I use Google Hangouts a lot for IM. Sometimes charcters aren't registered. Sometimes words are repeated. Spcae isn't registered most often. When I take a look at my previous post I notice it happeneqed before. THis is a good example... WTF is that q (happeneqed) doing there!? There is no way I could have typed that by accident. So, anyone else having keyboard issues? Also, shortcuts to special.l characters keep popping up. See the image. I have absolutely no idea as to why... Ow and btw (off-topic), the coating on my "e" is dammaged

But do you have the "Phone call" option? That used to be called "Headset". Without that one, the Pro1 isn't connecting with your carkit for some reason. @tdm For some reason my Pro1 chooses different codecs for APTX-enabled hardware. But that is probably due to the fact that the hardware supports more codecs than just APTX. As stated one device uses AAC, the other SBC, in combination with an HD-audio BT connection. I know that in the past A2DP was limited to 345kbps, I believe this was an Android limitation. SBC can support up to 728kbps. I assume that when you select HD-audio, the

Just got in my car to test it for you. Phone calls function is working. Have you tried toggling this under BT settings? Under LOS I now have the option of HD Audio. I didn't have that option under stock. Also I did some additonal testing on sound quality. When connected to my Pioneer XDP-300R (Android 5), I see the APTX logo and I definitely enjoy much higher bitrate than when connected to the Pro1. Also tried listening to Youtube on my company phone (Samsung A8). The A8 sounds better, less compressed, than the Pro1. Same headset of course.mymmb My car is from 2008, but the BT module

@Wasmachineman_NL So I tried a couple of BT settings. Sony WF-1000XM3 = AAC 16-bits 44.1KHz. Ora GrapheneQ = SBC 16-bits 44.1KHz - This should be an APTX-HD headset. CSR8675 BT = AAC 16-bits 44.1KHz - This should be an APTX-HD / APTX-LL receiver/transmitter VW BT module (original) = sound, but didn't check yet which codec. Toggling HD-media does make a difference, sound is more compressed with the option off. But, the system never shows APTX nor the Qualcomm logo. So I would say, yes we do have a HD BT connection. But it's APTX and certainly not APTX-HD. APTX-HD is 24-bit

Stupid 🥴, I should have posted that "fastboot flashing unlock" is the new command. I think this was changed a couple of months ago in a newer release of adb tools. ALT+U doesn't work anymore for me since I went to LOS. I also changed the keyboard layout to English, that did not help. And as I stated, I think it should work as Craig described. That's how it works for ' , `and ^. But not for " . Also when I press SYM+ I get a lot of the characters in shortcuts (ö ß Ü) but not the one that is impossible to do yourself, ë. I just connected a BT headset to my Pro1 and I have sound over BT.

I've been running LOS for a couple of hours now. Still configuring a lot. Apparently I missed the part about having to root and delete my fingerprints. I was hoping that was sorted with a fresh wipe and format. So later in the evening I will flash SU and delete the data. I have noticed the rotation issue not happening 🙂. But I do have three questions. 1 Can I turn on auto cap? 2 Can I change the "Shift" timing? WHen I press SHif, this happens a lot... The second letter also capitalized. 3 How do you combine :+e to get ë. The only combination keys I was able to find are ˋ'ˆ to combin

So, tried the suggestion. I enabled battery saver and flight mode. It charged from 68% to 69% in 15 minutes 😒. Looked up further specs, trying to figure out why it worked on in combination with the Sony XZs. The CPU is an 820 with a 2900mAh battery. It does not work on the Sony XZ1 compact, which sports the exact same CPU as the Pro1. I have to say I am surprised that it works acceptabel(y) well on the 820, but not the 835 🤔. And I agree with the thought this may be due to a handshake of some sorts.

The technique behind 3G is old school and one of it's effects is low/bad (worse than 4G) reception. The 3G frequencies can be used for 4G which will result in much better reception in places where you now would have bad 3G reception. Also, power consumption on 3G is higher than 4G. And 4G is better suited for IP-traffic.

No way. As I stated, I own a regular wireless charger (Samsung) and three quick chargers (Samsung & BaseUs). Also two car holders with quick chargers (BaseUs). It's the same pad that worked on Priv and XZs. Same meaning exactly that same one (XZs). Just to humor you I just connected it to my Pro1, placed the pad on the quick charger and left it for 15 minutes. Power went down 2% 😥 No metal interference whatsoever. The BaseUs pad I'm using claims an output of 5V 1A. That was enough to charge my XZs in, if I recall correctly, 3.5 to 4.5 hours. No it wasn't fast, but I wasn't in a

My setup... Only found out later that it won't charge the Pro1. Hardware:

Europe here. Stock assigned e-mail. No tracking info. I bet you we'll get an explanation where they tried a different partner and all went to shit. Customs being annoying, shipping info missing, funky smell in the shipment due to dead stowed away animals which lead to the shipment being inspected. You know, let your imagination run wild. I still hope to receive my phones mid August 😌

So, if you get the same response with the stock cable and charger, your USB connector is toast. Good luck with getting that repaired in a reasonable amount of time... Turn your phone off. Does it respond in the same manner? Would be strange if it was due to your recent flash. But alas, I have seen stranger things...

And I was just about to flash my phone. I think I'll wait for a smooth ride on a official nightly. I can deal with bugs. But a choppy interface, Heeell nooo.

Hmm, i will give this a try this week... I have fought with a Fairphone 3 passed weekend. So I most tools should work. Thank you all for making this happen!

Use Sugru. It's a hassle to remove, but not impossible. You can shape it in any form and thickness you like. It does not shine and can be used for dampening...

Well, i for one would not refer to BaseUs as cheap garbage. I truly trust their hardware. Nonetheless, if someone finds a wireless pad that does function with newer phones, I would like to be informed.

No it will not work! Unfortunately it does not seem to work on newer phones. I own a few of these wireless pads, different brands. When connected, they lit up the charging LED, but they do not actually charge the phone. This is also the case with for example the Sony XZ1c. It does work on a Sony XZs. Both the Pro1 and the XZ1 act like they are connected to a charger, but do not charge when placed on a wireless charger. This was tested with BaseUs and Samsung wireless charger, both QC and regular. I think they power delivery is too weak. That is why both phones won't charge. The XZs char

The phone was not warm. Apart from rebooting in case of bad WiFi way back, my phone has rebooted previously while using Maps. In this case even more so. My phone holder is mounted on the vents. It was cooled the whole 2000km on both trips. No way my phone heated up 🙂 . Airco was on all the time. Both holder and phone could not have been above 20 degrees.

I completely forgot to mention my reboots. Three weeks ago I went on a road trip. I was using Google maps and the phone was connected to a QC charger. Out of nowhere it rebooted. On the way back it happened again, twice. I can't say anything else about it. I was just driving with my phone on, connected to a charger and Google maps active. This was during the night in dark mode, all three times while I was driving through France. Apart from these three occurences, it hasn't happened again.

To me, this is an explicit statement we will not be receiving shipping information as soon as they are shipped. Like I stated earlier, this is also what happened when I received my replacement screen. So, all I can say for now is fingers crossed and hoping they're halfway tot the UK by now, or whatever location your area is serviced from. I assume we will be receiving shipping info as soon as they have reached the hubs and are sent from the hubs to the individual addresses.