agent008

Update on the battery, it seems the radio is to blame, and changing the network type seems to help. This night the phone was on my nightstand and over the course of 6 hours went from 100 to 34%. Network was set to LTE/TDSCDMA/CDMA/EVDO/GSM/WCDMA. Looking at battery usage over system showed the radio as the big culprit. (See image). I've set it before to LTE/TDSCDMA/GSM which seems to work for my local cell network, and battery life seemed to be good, however sometimes the phone would hang while on standby and I changed the network type hoping this would not happen. It didn't happen but th

Thanks, this is info that's good to know, if I ever go back to stock. Currently giving LOS 22.1 a chance. Although it is eating away at the battery almost as fast as 22.2... 🤦‍♂️

I have flashed the Stock, with GMS, file several times and it worked successfully every time. This is a great tool and guide. However, Stock with GMS only leaves 8GB free storage in Android. Some of which is occupied by the GMS apps. I was surprised to see the "low storage" warning after a few hours of use and few apps installed! I am not sure about the non-GMS Stock, I did flash it but did not take note of storage space. If I'm not mistaken it's a reduced storage as well. Flashing LineageOS exposes 240GB of free storage. What gives? Has anybody faced this same issue?

Yesterday when I wanted to switch from LineageOS 22.2 to 22.1, I foolishly performed a factory reset/data wipe on LineageOS22.2 Recovery before removing the Google account I had logged on to on 22.2 with MindTheGapps. Now, if I flash MindTheGapps, I cannot login to my google account on the phone -- it fails. I can use the phone if I flash an OS without GMS. But then I cannot st the PIN/screen-lock. I suppose something is amiss on the persist partition? I do have the backup which I took before logging in to Google. Is there still no trustworthy method for flashing the persist bac

I have managed to find a recovery for the "microG" flavour of LineageOS 22.1 and that has allowed me to flash 22.1. For future reference if anyone needs, I downloaded it here from microG's website. The archived image from timschumi as pointed out by @TeZtdevice worked perfectly. I have just booted into 22.1 and will check battery life and usability in the next couple of days. Thanks for all the help! EDIT: Daaaargh! I forgot to remove my google account from the phone when I was on 22.2. Now I can't re-login on the phone on 22.1! Had to reflash LOS without MindTheGapp

Thanks. I guess I will return it to stock via QDL once more, then flash 22.1. Hopefully the 22.2 recovery that I have will allow installing the 22.1 zip! EDIT: That didn't work out. I will need to find a 22.1 recovery... If anybody has backed up 22.1 files, help is appreciated. Thanks!

Thanks! That is fantastic. Now, I downloaded that image and tried sideloading it but the 22.2 Recovery refuses to install it with error: "Current SPL: 2025-06-01 Target SPL: 2025-03-01 this is considered a downgrade. Denying OTA because it's SPL downgrade". Is there no other way than me reflashing the phone to stock prior to installing 22.1? Since I don't have the 22.1 recovery, do you guys believe 22.2 Recovery will do?

Hi all, Battery life is dismal on my recently received Pro1x with Lineage 22.2. I have read somewhere here 22.2 has a bug that makes the battery decrease quickly. From what I read I understood 22.1 does not have this issue. However, I can't seem to find 22.1 available for download at LineageOS's website. Does anybody by any chance have a 22.1 zip lying around? Thanks

I have just pulled the backups now. Here's what I did. 1) Unlocked bootloader following this guide --> (ATTENTION, at the end of step 3, after enabling USB Debugging, find another option on the same screen called "OEM unlocking". Enable that option too, else you cannot unlock the bootloader. Then, proceed with the remaining steps on the guide) 2) Installed Magisk and rooted phone following this guide --> 3) Downloaded LineageOS 22.2 recovery.img only at this point. Booted to the bootloader, by issuing the command below: adb reboot bootloader Then flashed th

I was on full stock. Still couldn't make it work. After bashing my head a lot, I found the answer. Here's what I had missed:

Oh, I forgot to add. I'm an IndieGoGo contributor, not a website customer. I've never heard(read) of anyone who ordered from the website actually getting a phone.

Hey Forum, I'm going to repeat what I posted on the "state of production and delivery" thread here, because I believe it's more on-topic. Has anybody experienced the same? I can't unlock the bootloader on my recently received Pro1X so that I can install a better camera app and take full advantage of LineageOS. Any help appreciated!

I have finally taken possession of my ordered Pro1X. I am from Brazil but had it delivered to a friend in the US to avoid tariffs. This was last August 2024 so none of the new US tariffs were in force. I finally came to his house yesterday and opened the box ( he wouldn't dare opening it before despite all my insistence ). I am disappointed to say I received a used phone with a fading label on the back, scratch marks on the aluminium frame, with what looks like a brand new screen and a used cable. It's evident to me it was a return or, worse, a service phone delivered to the wrong pe

Thank you, this was very helpful, with qdl I was able to successfully flash my Pro1X with the factory "Non-GMS" image, version 2.1.5. I had to edit some of the .c files to add <stdlib.h> as a header include, but after that it compiled successfully. I'd like to install LineageOS but am having a hard time unlocking the bootloader.

Today I got an email notification from my US based mail forwarder. "You have a new package". I was baffled as I didn't remember having ordered anything recently... To my surprise, when I checked the package photos, there it was. "Sender: FX Technology"... So here I am, another customer who finally has had their phone shipped. Contribution #21XX

Has anybody who got the email and completed the form received an acknowledgement email after they filled in the form? I have filled in mine and did not get any confirmation.

I'm in contribution #21XX and have received the email on June 27th. Was in holidays so just saw and filled in the form today. Hope there's still stock (original order blue/256GB).

Well, of all 3 scenarios you put forth this would be the best one. Meaning we might get a fixed version. Oh man. Everyone has limits. I am pushing mine further away in hopes that the outcome will be a good one.

Oh my... December? It's quite a change in tune from "it will ship next week". I hope people at FxTec are getting better at estimates, rather than spitballing the December 2022 date which then might turn into March 2023. I've been supportive of FxTec's struggles and endeavour to make a grat phone but with my Pro1 turned into a paper weight (for now at least) and my replacement phone showing signs it might soon give up the ghost... I'm utterly disapointed. I'm trying to find solace in the reasoning that since they changed the estimates from "next week" to December, they might have

Hi everyone. No updates here but I've seen some posts around the net about people having received their Pro1X's. I've seen one or two people post here that they got their Pro1X. Is that all for the time being? I was expecting mine to be on the way soon since my Indiegogo Contribution # is on the 2100's...

I second that, I've been corresponding with tech support in order to see if my Pro1's no-keyboard and no-touch issue can be solved, and the rep at support has been quick to reply and also stated they have the USB board and display on stock.

Whoa, then it has finally started! Around what number is your contribution? Mine is in the 2100's.

Hi, I'm curious, does the Fold work well for those who like to type a lot? Does it have a "keyboard" function that could emulate the Pro1?

Hi, how can I help with this? Even though I believe my case is different (no touch at all, touch driver absent from i2c bus, whereas the problem here is insensitive touch margins). Last thing I attempted was flashing an older Lineage version (17.1) and running the display firmware upload APK. The apk never was able to update the display always complaining that firmware update wasn't supported.

Perfect, I figured this one would be conductive and left it there. I just didn't remove the black film "backing" from the old screen to put it on the new one.