Leaderboard

Thomas Bonde Pedersen has at IGG posted a fix for the not charging Pro1! ADD: This has been confirmed to work by other users! Please try it, before disassembly (or send in for service)

This actually works. Thanks for this hint. Took me some hours to realize the screen was already turning on and off again. 😅 Well, now I'm stuck with starting it (link). Anyway, helped a lot to fight first resignation after opening a package I waited for more than 2 years, facing it seems broken.

Building on @Hook's answer: I believe the Pro1-X still always comes with official (i.e. googlified) Android, no matter what OS you ordered. You have to flash a Google-free variant yourself. Take a minute to read about the procedures and options, following the various links on that entry point he posted. You will probably want to flash LineageOS 21. Choose between the official version without GApps or substitutes, or the derivative LineageOS-MicroG. I have always only used the former myself. For guidance, follow the very good instructions on the LineageOS wiki. Once booted, install F-Droid

We seem to have confirmation from someone else in Discord. The Pro1x is just kinky and needs to be tied up to get it's juices flowing.

Yes connected, but as he describes not charging continuously, but a few seconds per boot. Amazing that it worked. I really hope others can reproduce it, fixing their issues.

To those that got a Pro1X not charging, try the fix found by Thomas Bonde Pedersen on IGG. Made a thread here:

lineage-21.0-20240701-nightly-pro1x OTA installed okay, 'Camera' and 'Open Camera' still working, root maintained :)

It's not. Just follow the LineageOS wiki precisely. The Pro1X images at lineageos.org are ready-to-run ports of the OS, that support all the Pro1-X's hardware already and are updated OTA once per week (if you let them). No worries. The biggest obstacle can be to find a PC and USB port that supports fastboot reliably. Can be a bit of trial-and-error. This is not specific to the Pro1s though, and you might also just be lucky ...

So I ended up building my own phone. Backstory: A few of you know me for my hardware modding adventures. I've replaced the broken USB port with a new port. I've then removed the fingerprint sensor to replace it with a secondary USB port for a more comfortable landscape mode. I filed away some parts of the display mount to make it more durable and I was about to replace the battery while reusing the old BMS. I did all of that to make my Pro1 work as I wouldn't want to live without a keyboard phone. Sadly, the issues didn't stop. The camera quality is bad, it's horr

It's a long story, if you care to read through the updates on IGG. The 25 cent recap is: 1. The Pro1x was intended to be simply a Pro1 with a different color and more memory with your choice of OS. The OS images already existed for flashing the phones during manufacturing. 2. The company that was supplying their SD 835 chips took their money, but never provided the chips. 3. FxTec had to redesign the phone with a different chip, given their financial constraints. 4. Although prototypes and source code were provided to developers, there was insufficient time for images fo

Correct, they all come with the stock android with Google, but as usual you don't need to login to do the onboarding, I skipped it myself.

Some cool builds in here, I think I will be going the "hack a keyboard onto a phone" route in the future, probably with a Furi FLX1.

Have the same issue. Hoping it will work. It's really frustrating waiting for so long and then finally you receive the phone and it's not charging/turning on

Probably, this is the best place to start (hence it being in the pinned "Start Here" thread. :-) Only Stock Android requires you to have Google.

Interesting. He is basically causing a looping "Battery pull" reboot, so it seems that there is some low level part of that which briefly draws power without needing the usual processes that require being able to fully boot. I've always said the "battery pull" reboot was very useful for a wonky behavior on a phone, but I had no idea. ;-) Hope we can get a record of this working for someone else for verification.

Awakening an old thread. A user reported a way to fix the issue on IGG: