Leaderboard

Soo yesterday i have madded my battery refurbishment . It was simple process - remove kapton tape, cut old battery cell contacts from pcb, littlebit shorten contacts on new cell, solder new cell to pcb with spot welder, isolate, bend pcb to correct place and then new kapton tape. It looks like original and whole process was for 5 mins 🙂 I am now inside testing - charged to full - lineage batt info shows approx 2900mA after full charge. I have now 66% on battery after 10 hours usage (lineage update, yt music for 2 hours in car, 40 mins on browser, some calls e

Soo yess...my phone have stuck on 10% (battery saver) for more than one hour with youtube playing. Final time on battery was approx 34 hours and 6 hours on display. After second charging my phone charges up to 3138mAh but after few seconds after disconnect chager it shows again 2900mAh. It looks like i can be happy with new cell. Question is for how long. BTW cell looks exactly same as original with contacts on exactly same place.

I edited my previous post with updated information. Pro1 and Pro1-X are more different than I first thought so you cannot swap parts that easily. I added also the source for the information. Here are few Indiegogo updates: #14 Both the fingerprint sensor and the camera will be redesigned once the samples have been fully tested in the factory. #15 The Fingerprint sensor now has a new module. We’re expecting the performance to be more accurate than the Pro1 and keep you updated once we have a working prototype. #20 Our engineering team in China has had to sta

I once tried to swap-in the screen assembly of a Pro1-X into a Pro1. They fit mechanically and connector-wise. The result was that the Pro1 was able to boot into a (working) Lineage recovery, but not into the full OS. I thus assumed the selfie camera was different. Of course, the top half of the Pro1(X) includes more than the (touch)screen and camera. There is the indicator LED, the ambient-light photodiode, a speaker and (I guess) a mic for handheld audio. But somehow I had assumed those were analogue devices that could not cause a crash upon boot.

No we can't, it is a mat, sorry, but you can change what the keys actually return. I have for five years used a Pro1 qwertZ setup for qwertY (as I disliked the shifted qwerty) using FINQWERTY the nice open source work by @Anssi Hannula, and selected a Danish layout. ADD: See below

I agree with your criticism of the Pro1-X's remaining hardware and delivery process. But in these lines you essentially state that you backed a keyboard phone even though you have absolutely no use for a keyboard phone. Of course you have every right to do this. But then do not lateron blame F(x)tec when they indeed ship you a keyboard phone as ordered ...

Yeah, the screen with frame does not include front camera module and the board for the connector. So those parts would need to swap anyway from the old screen. But the frame and the panel itself is the same so it makes the change much easier.

A bit of a tangent, but in what universe is August 26th 2 weeks before September 3rd? :D

@Aeong – to be fair, the screen is not "defective", it's a minor cosmetic blemish, and all of us had to put up with it who needed to source a replacement screen outside of Fxtec, which was often the case. On the parts market, perfect replacement screens haven't been available at all now for a long time, and it seems that at this point not even Fxtec is capable to source any. Your complaints on some of the other issues you mention are, of course, perfectly valid. When I was still using my Pro1X which also had basic connectivity issues, practically inhibiting calls and text messages a

Can't find it back either. But I just checked: If you *carefully* lift the edge of a cap with a pair of tweezers, you can see the transparent mat below. So the keycaps indeed seem to be individual parts. Not something that was meant to be user-customizable, but it does seem possible ...

Looks like something really screwed up your partitions... This is now beyond what I can think at the moment. I'm currently out of ideas.

As previously stated, I can only agree. I have 2 x Pro1 and 1 x Pro1-X and all displays have these black moons in at least some of their corners. The good news is that they haven't worsened over time, which is 4+ years for my initial Pro1.

I am not sure but maybe will it be same as when i have changed battery cell on my old motorola photon. After first full charge motorola stuck on 5% battery for hours and was needed to wait util phone off and then recharge. After 3 full charging was battery info "recalibrated" and all was fine. ...i am now on 55% after 15 hours and phone says that will be on battery up to tomorrow 14:30

Another thread here made me thinking that what are the chances if Pro1-X mainboard could work on Pro1 (and vice versa). Of course, the phone would change to Pro1 -> Pro1-X (or other way around) since the main board determites software etc. https://community.fxtec.com/topic/4137-shopping-for-a-working-pro1-not-x-mainboard/ The board is definitely different (not the same SoC etc.) but the size could be identical. We know that battery has different connector and camera is different so you probably need to swap those also. But if other connectors are the same could it be just "plug an

I wa under the impression that the persist partiton contained unique information so copying it would sort of making the two devices clones. Interesting if that is NOT the case as we could thus have one available somewhere.

so with a lot of help and custom made images from TheKit, now i got it running. Basically the persist of mine was corrupt. Some other device persist.img flashed and it worked!

I had already forgot this picture but the discussion here helped me to remember. Individual keys are indeed possible to swap or even rotate x).

I do that on my old pro1 No problem with the key himself, it stills work today. (but doesn't solve my keyboard problem, other story) Sorry the picture is blurry but could be interessant to give an idea from the dark side of the pro1s keyboard...

Someone brave should test to flash stock Android 9 firmware of Pro1 to Pro1-X with new screen. I mean the same process that Lineage OS users have done when changing the screen. "You have your current rom installed and try to overwrite it without wiping data. The installation starts and fails after a few minutes, however the display area is reconfigured" It works on Pro1 and you do not lose data. But probably the flashing of Pro1 firmware to Pro1-X does not even start. And if it does, there might be high risk to brick device.

When was it released? Was it nearby 2020/1? Was it produced by a company with deep pockets? Those two are VERY important to take into account. You need absurdly deep pockets to handle such kind of market offer.

Mine has the marks too. This is an issue with the display manufacturer which seem to have a 70+% failure rate at the screen edges. However, they scam buyers by cherry picking the displays for test units, so none of the test units have these visible issues. F(x)tec is scammed and they are incapable and don't have enough money to fight back.

I agree. There's no noticeable errors or warnings in the logs. @trahe I found this almost by chance: Does it help you? It shows that restoring some of the partitions worked to unbrick his phone.

never. we all start somewhere. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ I can't provide much better steps than what is already in the OP. I guess start here: backup persist. try adb method first. requires unlocked and a recovery boot if above doesn't work, install EDL (see readme and OP) edl r persist persist_backup.img edl r modemst2 modemst2_backup.img edl r modemst1 modemst1_backup.img edl r fsc fsc_backup.img edl r fsg fsg_backup.img flash your OS of choice:

I don't know if UBInstaller deletes the persistent partition. Look at this guide: Try to do a backup of the partitions and let us know the outcome of it. If you are willing to, show us the full output from the tools used to backup.

Not using SFOS myself since many years. But others indeed have reported much better results. As you had similarly devastating experience with Droidian, also (kind of) positively tested by others, I wonder if something is wrong with your device. Did it work correctly with stock Android 11?

I've been daily driving Sailfishos for about 4 years on the Pro1 then the X. I haven't experienced these issues.

No no no claude0001, I'm not gonna read this! :)) BTW the psychologist appointment has been canceled - fxtec promised me to send new screen!

i still did not figure out, so i am not sure if the e.g. phone works. (e.g. IMEI is not shown) So know we know, that the root of my problems was regarding to the corrupted persist but wifi and bluetooth works just fine... So the the keypoints for the fix: having some ~working~ persist i needed to the patched boot.img, which stops early and runs the telnet server, so i was able to format userdata into ext4

I was thinking that they are the same. Is the selfie camera different? I thought that only rear camera is different. But anyway, maybe @gusscan confirm? I think guss ordered pro1 screen panel with frame for Pro1-X. Also, some sellers list same screen for both Pro1 and Pro1-X (see attachments).

I was under the impression that the frame for the Pro1 is not 100% identical to the frame for the Pro1x (different camera? Other subtle differences?). Anyone know. I can't remember.

hello and thanks for the tip. the dealer has the same display for qx1050 and qx1000, so pro1x and pro1 on offer. but he doesn't ship to Germany, well, everything works fine. I just wanted to be on the safe side, burkhard

I found a possible correlation between the phone's temperature and whether the touchscreen works or not, as it has sat in sleep mode for a few days now and the touchscreen seems to be working every time I grab it. Phone has consistently been at room temperature every time I've tried. But when I plug the phone in and charge it, after a minute or two it warms up a bit to the touch...and the screen won't receive any touch input. It's wacky. A loose cable does seem possible, especially on the motherboard side. I'm still waiting on that replacement screen. I searched "QX1050" an

Lineage-21-20240902-NIGHTLY-pro1x with Aug 5th security patch installed smoothly via OTA. MindTheGapps14, and root was maintained. Notice, Monday's date as expected, but didn't actually show up until today, Tuesday. And, woo hoo, I can dismiss the lock screen with the space bar again! :D I'm probably the only one here who cared about that ;-)

I think someone here reported that one of the keycaps came off, and they glued it back in place?

That would be my guess too, but strange that that it starts working again though shortly. If you are lucky, it is a cable not locked in the connector and maybe the way holding it can make the cable just get or just loose contact BUT this is a pure guess,

right something about the partitioning is my guess as well

OK sure, and thanks for helping the edl backup procedure i logged, and for further information i as well included the output of fastboot getvar all the product is *bengal* the last flash attempt has had been UBTouch i can as well have Pro1x or QX1050, depending on which ROM to flash (stock rom / Lineage21 i tried to no bootable avail) As a sidenote, i as well tried to do the : Pro1-X: Flash Stock Firmware in fastbootd Mode from the "official" Gdocs, and as well installed the newest platform-tools, but fastboot create-logical-part

yesss....good question...i dont know old values 😄 Old battery was holds only around 8-10hours max.

Lineage-21.0-20240901-nightly-pro1-signed.zip OTA installed. Sill: No Camera No Flashlight https://review.lineageos.org/q/project:LineageOS/android_device_fxtec_pro1

You can flash different OS (like Lineage OS or Sailfish OS) and go back to stock Android just by flashing it IF you do not brick the device during the process. The device is not completely wiped when you flash different OS. Idea of the back up is to save all partitions just in case if some error happens. However, currently there is no way restore those back ups but it does not mean that they are useless or could not be used in the future. So, just be careful when flashing 😉.

Make sure your cell phone provider connects to the same network bands as what the phone supports. This is important because every carrier may support 3g/4g/LTE but connect with different bands. You have to do some research on your end and when you do find the right carrier, the phone will not have these issues unless it is defective device itself.

Maybe it is. But not because you dislike the screen. Rather because you do like the rest of the phone! Just joking of course ... 😉

Hello all, I wanted to post one success story after the years of despair in this community. My Pro1 X arrived last week to Czechia with around 50% charge in black instead of blue but I am grateful to receive something. Contribution #36xx. Flashing LineageOS 21 worked like a charm. My impression after a few days: Pros The keyboard is great: I was used to Blackberries but I find the wide layout quite comfortable, the thumbs must travel a bit more but it's superior for languages with accents like Czech. LTE works fine in Czechia with T-Mobile including VoLTE. I am lucky in this regar

Well, today my saga has finally come to an end. After paying a 49 euro import fee, the delivery guy was gone in a flash. The packaging looked like it was meant for the original Pro1, but inside was a blue Pro1X. Unfortunately, it has a custom engraving on the back. And, of course, it won’t turn on. So, I’ve resorted to putting a rubber band on the power button while it’s hooked up to the charger, hoping it’ll eventually come to life. Regardless i will 3d print a frame and put it on my wall. This will likely be my final post here, as my journey has come to a rather ironic conclusion. I’ll

Sadly a lot of the Pro1s have this defect, mine included, and on mine it's not even nearly symmetrical like on yours. Definitely not acceptable but if I ever RMA'd in the past there is a good chance I wouldn't have seen the phone for years so I just put up with it.

I have several Pro1 and Pro1X, and they all got it to some degree, sorry. It is the same screen from Boe used on the Elephone U, and you can find complaints on that too. So though annoying, it would be really lucky to find one without the issues...

You must be new here ... Sorry for the pun, but you'll soon learn that f(x)tec is no ordinary business ... 😄

I wouldn't worry about those. My Pro1's (got two of them) and my Pro1-X have had these black spots in the corners of the screen since day one. They haven't worsened over time (we're talking years for my initial Pro1)

So far I have only had it working for about a day. I haven't done much with Sailfish other than some tinkering around in the terminal. It runs smoothly and once you perform some of the tweaks (mentioned in the first post) it feels like it was very much designed for a device like the Pro1-X. I haven't attempted to run waydroid yet but when I do I'll update how successful (or not) that attempt is. The Pro1-X is not going to be my daily driver. I intend to use it as a small personal laptop (browsing, email, media consumption etc.) rather than a phone.

Hi all, I am late to the party. I didn’t expect to receive this device and it showed up at my door late last week. I am really struggling to install Sailfish on the qx1050. I followed the instructions in the first post of this thread and I can’t get past the “Powered by Android” boot screen. I tried both the March 2023 (Sailfish 4.5) and October 2022 (Sailfish 4.4) releases. I booted to the bootloader, ran the flash.sh script. Each time it states the script has completed successfully but no joy. Can anyone advise me as to what to do? UPDATE: I figured out what I did wrong. When I fi