Leaderboard

Yeah I'll contact support later today. I don't really want to take the phone apart as long as there is warranty on it 😉

I am pleased to announce that the Pro1 has received official support in LineageOS 16.0. You can find the builds and installation instructions on the official LineageOS Downloads page. Please note that LineageOS does not include the proprietary Google apps (aka. "gapps", Play Store, etc.), nor a "su" binary. These are "extras" or "add-ons". You may use any appropriate gapps package for Android Pie. I personally recommend MindTheGapps which can be found here. LineageOS maintains an official su add-on and a couple other extras here. Note the Pro1 is arm64 and be sure

You're just rubbing it in now! 😒😂

Not exactly strange. For calls to work on LTE, it needs VoLTE, which is a different standard. But so far I've seen, it has been a complete shitshow in North American networks. A lot of times it's only on a subset of their own phones sold that works. North American carriers do this kind of bullshit all the time. Device whitelisting, slowing or outright not providing updates, you name it. They seem to only care about locking you into a new contract every 2 years with "new" hardware. Whereas my 4 year old, North American market BlackBerry Priv which has been out of support and pro

Sure we could close it, but I see no harm in it being open, I think the recommendation of the link to the new thread would suffice. Don't you? I guess once test-builds for 17.1 appear, we would have a new thread for that too, that should also be recommended. I mean if someone (for whatever reason) prefer one of the old 16.0 test builds it would be natural for anything related to that to be in here. (not that any support on the old test builds could be expected from the developers, but there still might be sharing between users)

Also, check that there is not dirt or fluff in the port that could cause problems.

Very good point!

Could be the issue outlined in _DW_'s reply or at worst you've got a dry joint on the where the USB port is soldered to the board. If it's the cable problem then go through every cable you have (if you've bought a lot of tech gear in the past, like me you should have a few lying around). But a quick question. You haven't got the phone in a case, have you?

There is a fxtec community discord server, with a lineageos channel and we'd love to have you 😉 https://discord.gg/4GVR7rA There is also a bridge to discord server from riot/matrix: #pro1-lineageos:reverso.de There is also #fxtec on freenode irc. That's the only place I've seen los development discussion before, including mccreary in the past.

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 😌

Okay, I can see this conversation taking up several dozens of messages in this thread. Please contact me in PM and we can find a way to chat without spamming users.

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

You make good points that I hadn't considered. I guess I figured this was more like 'first time LineageOS test builds' but you are right, there could be more 16.0 tests here. I'm fine to leave open after consulting with you 😅

My guess is that the wireless pad just won't supply enough power to charge the phone, but enough to trigger the LED. That was often the case on my previous phone, with the added bonus of still heating it up... They're really not that efficient, and depending on what you plug it into it might just not be enough to offset the power needed to keep the phone on.

Well its happened to my Nokia E7s all the time. after every few months the cable will not connect. so i will push it harder and it will work for few times and then pushing harder wont work either. basically it the beginning of the end of the usb port. and then i had to get the usb port replaced from the workshop. Didn't someone posted that its easy to get usb port replaced from any workshop?

It sounds to me as you need to contact support. 😥 With no dirt, my guess would then be a bad soldering. Luckily the USB-plug is not on the main board, so it should be a rather small operation to change the board.

Indeed. a tiny amount of pocket lint, can make havoc in the wrong place,

That's pretty close to what I think. That they are just playing it safe in case my unknown device only supports up to 3G

I have AT&T Prepay-- they don't even keep track of what phone you have. I suspect you have a contract plan. It's possible, if you took a sim that was previously used in a contract phone, that they still think you have that phone. They are almost certainly not aware you have a Pro1, nor do they know what it is. The Pro1 supports 4G just fine.

From a quick look at the link, it seems like AT&T is doing away with their 3G bands. Basically if you do not have 4G LTE connections then you won't have service. My guess is that AT&T doesn't know anything about our Pro1s. (If I go to my T-Mobile account it says that my phone is an "unknown device" yet my service seems to be working fine) I honestly think you'd be ok seeing as the phones supported on the list include an iPhone 6. We both know our Pro1s are much higher spec than that. ... But I could be completely wrong. It's just my two cents.

First, thank you for volunteering to contribute. I've been working my figurative butt off for months and I'm getting tired, to be honest. Which is why Nolen is doing Lineage 17.1. More inline... Check the keyboard files. This is probably in the KCM file, if it can be changed at all. Notice the keyboard is declared type ALPHA. If you declare it type FULL, I believe both autocapitalization and the symbol popup will go away. Certainly. And add a device specific setting to toggle sticky fn, I assume. Build it in a Line

I had this issue with a particular cable today that works on another phone. I used a Nintendo switch controller charge cable instead and it was fine. One difference is the other cable isn't flush when connected the Nintendo one is so maybe connector length related.

It seems that first official Nightly build is available 🙂 - https://www.lineageoslog.com/16.0/pro1 Edit: here also, https://download.lineageos.org/pro1

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.

Definitely be careful with cheap garbage in general 😅

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

I have upgraded my Droid 4 back then with a wireless charger. Unmounted the charging coil from a wireless charging backplate of another phone and glued it onto the battery. The backplate actually did fit since it was around 1mm thin. I connected the output directly to the 4 pin connector on the back (no idea what it was for in the first place) which ran on the same line as the USB input. So that should definitely work and I guess it would be quite slim. Does the upgrade option come with a flat USB C adapter so it won't be in the way while holding/using the phone? Also, I don't know ho

Just a quick note: It finally worked for me! I just ignored the device for 4 or 5 weeks, supposedly letting the battery drain completely just like suggested above. Then, I held down both volume keys and the power key before inserting a standard USB cable. I let go of the power key after a while and the QUSB__BULK device appeared in the Windows device manager. The flash tool detected the device and flashing a stock firmware image worked on the first try! Thanks to everyone!

5mm hole punch does the job just fine then you can try any material you want.

I know there are a lot of hardware issues @Slion and it's not that which is the problem - it's the insinuation that I'm essentially lying in order to get another display..

FYI... Made huge progress on selinux today. I should have an enforcing build by end of week. And I think it can go official after that.

Anyone reporting speeds over 100 wpm (phone or PC) gets a visit from this guy: I know there are people who type faster than that, but we aren't taking any chances.

OK, so I received my third display recently after a reversing of the decision by support to only send out a display after me taking a video of the second display with the light bleed. I am happy to say that this display is much better performing than the first two, however it still appears there are some, albeit small, dead zones at each side of the display. It does mean though that it is usable and I think that's the best I can hope for - would be interesting to see if other people who don't have a problem with their display notice any kind of dead zone on theirs? For reference, I'v

Yeah does sound like a bad port it happens unfortunately 😞