Hook

I would need a lot more context of what you have and haven't done, in an orderly step-wise fashion. The troubles with your USB-C port I can't address, but it sounds like you have it working if fastboot devices returns fastboot in a terminal screen on Windows. I also can't really address using Windows for this. Although I am a Windows (10) user and have done this with Windows in the past, Windows is so tempramental with this flashing stuff that I switched to an old Thinkpad running Manjaro Linux for all of this. By the way, you don't need to set your usb connection to file transfer

The easy fix is, of course, a tiny piece of black electrician tape cut to the size of the finger print sensor. Actually, the black stickers that cover the screws on the back of the screen (on the Pro1x they are invisible, unlike the Pro) are exactly the right width and can be chained across to cover the length of the fingerprint sensor. I have sheets of those black screw covers, if you want to DM me your address. I think Fxtec has enough on their plate, I doubt the feature request would get a lot of attention right now. I have only heard of this consequence of the sensor being activ

It doesn't happen with Firefox. It does happen with Chrome, Chromium based browsers and I found a couple of other apps that will react to it, but most don't and, being a Firefox user, not using my fingerprint reader and 99% using the device with keyboard out, I never even noticed it before someone called my attention to it.

I have now given up. I have once again been unable to flash Droidian . I have troubleshot this with @matf-kabouik extensively. I am doing everything he does and even verified the sh256 on my download. I honestly don't think this is a problem with Droidian, but some kind of problem on my Pro1, maybe my boatloder even, that Android and Lineage don't care about. For instance, when I try to launch the Droidian flashing script, My Pro1 reboots and I have to put back in bootloader mode. I've tried different ports and different cables. No joy. For now I'm abandoning it, but I don't think other

And I got my package today! 🎉

Another little bump in the trail... a system update popped up, so I said "sure" When it rebooted, something was off with the touchscreen. It wasnlt nonresponsive, this was much weirder. Scrolling was fine, but anything requiring a point press, like launching an app icon, required laborius pressure. What's more, it was worse at the edges of the screen, meaning I couldnt send the open app to the multi-tasking card rack to return to the Phosh home screen. So, since I haven't had time to do a lot with roidian yet, been a busy week, I'm just going to reflash the March snapshot and not take

For anyone worried by the hiccup with the Pro1 update, the 20230504 update for the Pro1x installed smoothly and all is good. Still April security patch, as expected.

To answer your questions: 1) No disadvantages. You will have Android 13 and you will be getting current security updates. You will have all the functionality you're used to with some added features. 2) Here "useable" should be taken to mean it is ready for a daily driver, not as "it works, but..." 😄 It should not change your connectivity as it uses FxTec's own proprietary blobs for that. If you have good connectivity on stock, you will have the same on Lineage. If your connectivity is awful, it won't fix it. 3) Yes, those instructions at Lineage are good. Go slow with the ja

Yes, you are right-- that hasn't been addressed, for now just use the Pro 1 Thoughts and Questions for the Pro1x as well. I'll look into it (I don't think even moderator powers can change those) Also, if you have a Pro1 or Pro1x, it's helpful to use the instructions in the thread I'm linking to indicate what you have so people know when answering your questions. https://community.fxtec.com/topic/3745-please-enter-your-fxtec-device-information-in-your-member-title-slot-under-edit-profile/

Well, I fixed it. I reflashed 2019 stock wondering if there's something Droidian doesn't like about coming from Lineage, and it still didn't work, so then I took all of the updates to 2019 stock (I had forgotten how many updates we got before it just stopped). Tried one more time with the Droidian flash_all and... it just worked. Nothing different about the output of the script, but it booted into Droidian. Will be a while before I get to set it up, but I finally got it. 🥳 🍻

Yes, from what I can tell, Lineage doesn't improve connectivity from stock. So my Pro1x does fine on T-Mobile on stock and does the same on Lineage. Others, who have had problems, have reported those same problems on Lineage.

I don't know if this is my problem or not, but it may be and, if so, I need to know how to do the above, because I'm not sure what it means. However, here is what has gone on up until now. I am trying to flash Droidian on my original Pro1 (not Pro1x). I previously had Lineage on the Pro1. I downloaded droidian-OFFICIAL-phosh-phone-fxtec_pro1-api28-arm64-25_20230324.zip and unzipped it into a folder on my Thinkpad running Manjaro. I then put my Pro1 in bootloader mode and then issued the command ./flash_all.sh Everything went fine, there were no errors. The Pro 1 reboot

There is also my solution (developed for my Pro1, but I like it even though my Pro1x has okay connectivity),,, getting a cheap slab phone to use as a phone and hotspot. Sure, a hotspot is smaller, but it isn't any cheaper than a middle range moto slab on sale and I always have enough pockets. And I get to keep using Verizon. I use my Pro1x 95% of the time, but I have a reliable Verizon phone when I need it and the cheap moto can take the wear and tear of taking it in and out iof the dash mount in my Honda for Android Auto. 😉

I think this is your best hope... Note. I've never done this myself. As you've learned the hard way, you cannot OEM lock the bootloader on anything but the OEM stock. If you want a locked bootloader, you will have to stay on stock Android.

Yes, that is still good. Airplane mode helps. I never use that as I want my emails and dropbox and such updating in real time.

That's definitely good, especially if you were actually doing anything with it during those 8 hours.

Thanks for your early development efforts for the Pro1. I still use Fulguris as a fast and efficient browser (alongside Firefox, which I keep just for access to my desktop bookmarks when I need one).

I received my tracking number this morning as well... and it is to the correct destination! 🥳

Yup, did the same here. Except apparently I couldn't boot to my other slot, I think because I had installed Lineage without anything Google or Magisk and the old slot had the works. When I tried to boot, it claimed the data was corrupted and I had to factory reset. Here's the odd part. I factory reset and it booted into Googleless Lineage-- it was the May 1st nightly and the touch screen is working fine. ??? Be curious what @EskeRahnfinds when he sideloads May 1st-- is the problem with OTA, a problem that Factory resetting solves? Luckily my Pro1 has become my experimental device

I have no idea what to make of this situation. I don't think it's a scam. That is, I am pretty sure it really was FxTec (Francisco, bot or not) asking for my money and I'm pretty sure the Paypal invoice was really from them, and assume the same with yours. So, to my mind, that makes the most likely scenario that they somehow gave you the wrong tracking number (more likely, I think, than they sent your package to someone in GB, though we can't rule that out). Nowhere does FedEx indicate that you ever figured into this shipment. It may even be that your battery hasn't actually been shipped at

Certainly allowed, but skeptical we will get much out of it. There are just too few of us regularly on this forum.

This has real possibilities. The question is, will this generate enough interest in any big companies that can do the R&D to take it out of prototype.

For the life of me I can't figure out how to trigger 3rd and fourth layer symbols. I've tried holding separately and in various combinations Alt GR, Ctrl, Alt, Fn and shift. Lol. It is likely user error, but clearly I'm missing something or my tablet is incompatible in some way.

Oh yes, I don't know why it didn't work the first time I tried with my Thinkpad X230 running Manjaro. Works fine now. What was weird, though, and possibly a coincidence, is that I lost my sound feedback when I connected to Linux, When I repaired with my Windows Thinkpad, the sound was still gone. I had to reinstall your app to get the sound back. Have no idea what happened there. Will run more tests to see a)if it keeps happening. b) is it my tablet doing something funny and not your app (likely) c)if there is any pattern. Made me realize how important BOTH the sound and vibration f

I'm glad you are happy with the script, but it sounds like you were, in fact, not successfully rooted with Magisk.