Leaderboard

Long overdue post.. Apologies! Here's a guide on how to flash the Pro1-X stock OS with a script in fastbootd mode. This method works with Windows, macOS, and Linux. Please note, you will need to have your OEM/Bootloader unlocked before you proceed with this flashing process. Click the Google Drive link below for the documentation: https://drive.google.com/drive/folders/18Clj6qv4jXIFGfy0S1NO1K8DoN8bJ3Ms?usp=sharing

I was comparing the ports with the naked eye, and had to do some trial and error. I first tried the MI 8 port (this is for a Xiaomi MI 8 phone battery). That didn't seem to fit. Next, I tried the MI 6 port. The bar got in the way, so I flipped it around and when I was trying to figure out if I had gotten it connected, I noticed the charging board LED had lit up, showing voltage!! I grabbed an old USB charger that is limited to 1 amp. This charging board allegedly has an overcurrent protection mechanism where it will shut down if the current goes over 2 amps, but I didn't want t

We had an emergency alert test at the weekend. SOS_R01.webm

Purpose of topic: In the course of doing the above, my battery became depleted fully. This meant I needed a way to charge up the battery so that I could get the files off the phone. I looked online and found various gizmos that repair shops use. These generally consist of a USB powered board, often with LEDs showing the voltage and current, and a bunch of the wonderful (/sarcasm) proprietary connectors they started putting on these batteries after companies stopped making easily replaceable battery phones. I ordered 2 different makes/models of these boards. I didn't know which connec

What f(x)tec euphemistically refer to as a "sleep state" means nothing else than that the battery erroneously got depleted to literally 0.0 V, so that there is no energy whatsoever left in it. The "battery protection" system should normally prevent this from happening. Not only is so deep discharging bad for a Li-battery's life expectancy, it also turns out that Android actually always needs enough residual charge left to boot its kernel before re-charging from USB can start. So, yes, once bitten by the battery depletion bug, there is no other way than to either 1) send the phone back

A few more tests to share... On a drive to a restaurant, I called my voicemail. It connected fine, but it could only understand 1 or 2 digits of my 4 digit code. I tried repeatedly. I finally hung up. Once at the restaurant, I tried several calls to my voicemail. It did connect every time and it did understand all digits of my code. However, it took several seconds to connect each time. I noticed that it would be on LTE before I'd call, but when I would call, it would try LTE for a while and then give up and try some other protocol and work. Oh, and I tried speed tests bo

Background: My Pro1 USB port failed a little after a year of use. I ordered a replacement port online, took the old one off, and soldered the new one in its place, using very rudimentary tools. It worked better than the failed old one, but still wasn't as good as new. I don't remember the details. I think it required the USB cable to be inserted with a particular side up. Shortly after doing that, I received a replacement port and PCB from fxtec (it took a month and half to reach me after reaching out to them, I believe). The new one worked perfectly. I used that for over 2

Does this mean there is a way to set this parameter with an android app? Theoretically yes, and such an app actually exists, but the one I know of does not work on current Android/LOS versions, so it doesn't help us here. Those apps are not supposed to reach the end user, and what exactly it is they do is not documented for the public, either. The app I've seen comes from the display controller manufacturer. I used it myself to 'flash' my first display replacement when my Pro1 still ran on what I think was LOS 16. For later replacements (I think all in all I had three), while ru

The sunshine ss-909 model, which is what i originally wanted, but was going to take too long to arrive, does have two different input ports, and I believe one set allows for fast charging. However, I think you are supposed to only use that side if the pcb containing your battery port is made to be used with it. I did order one, but it will take some time to arrive. Note: No idea if it has a port that is compatible with the pro1 or pro1X. I will report back when I get it.

So you are saying they sold out their strongest supporters in favor of the masses? 😁 I agree about most people not wanting to buy the Pro1X just for the extra RAM/storage. My purpose was to have a backup for the Pro1. And, as much as some of us grumble about design decisions and quality control, if fxtec stays in business, we'll probably still keep buying new phones they make -- at least until the competition for landscape (AKA "the correct way") keyboard phones creates something competitive. The astro-slide looked like it might be such a phone, but its problems seem even worse than the

As far as I have found earlier, it is simply a configuration, a setting of touch controller... simply it was not easy to reach the circuit on the specific I²C port under Android which would like to use it for touch sensing... So basically it is not flashing, simply a setting which is one of the parameters the touch controller has, stored in an EEPROM-like way.

Yes it is, and I think for the Pro1 it has to be the most recent version, because the display's border defaults (it's a chip on the display that has to be flashed) had changed during the production of the phone, and at some point Fxtec had to account for that in the phone's firmware, if I remember correctly.

Yeah, I think that once the battery goes to sleep, nothing short of taking the phone apart and providing a direct jolt of energy will allow it to charge and supply power. Something that would be waaay above my pay grade. Maybe you could tie it to a kite and fly it in a thunder storm... 😄

It looks like you've run into the dreaded battery protection issue. Most Pro1xs are fine when delivered. Even sitting for a year in the warehouse, the batteries should have 30-50% charge (Mine, delivered in early April 2023 had 50% charge), but the battery protection apparently has a flaw they are investigating. If the battery becomes somehow completely deleted, it enters a sleep state and won't charge. You should contact FxcTec at [email protected] to open a support ticket. Sorry 😞

No. No one knows for sure all the details, but they are switching shippers from Expansys. My best guess (and it is just a guess) is that although they had a contract with Expansys to ship, the phones were so late, with prices having been driven up during the pandemic, that Expansys insisted on more money than the contract called for. We don't know if that was a breech of contract by Expansys or if there was a clause allowing that under "dire circumstances" or whether there was a disagreement on what was allowable. Who knows what the legal challenges are here. So it will take time.

So not all the Pro1X phones have been shipped yet?

Thank you @david for this insightful post! I'm sure this is going to help a lot of people who have similiar battery issues on the Pro1. Unfortunately, we do not plan to make any additional boards for Pro1 and Pro1-X. Though, we do have Pro1-X antenna boards in stock for repair and replacement. The batteries on the Pro1-X have different connectors and protection boards compared to the Pro1.

Just an update to maybe help anyone having the same problem: I had forgotten to delete my old "hidden" Magisk installation and this confusing/preventing Magisk 26.x from realising it was installed in recovery. As soon as I uninstalled the hidden Magisk application, running the latest installed Magisk prompted me to complete the installation finally!

Basically what should be done with the device itself is simple and written in touch controller's datasheet. However, the actual internal working of Android affects the way of how to do it and if it is possible or in what circumstances - and that is where deep knowledge of Android programming may highly affect the possibility of success...

You will need to put the coil on the outside of the Pro1, as the metal back will not let the signal through, but if you mean a shell case for the Pro1, it should not block the field with normal materials. I do not know how much effect will be lost by heat generated by electric current induced in the back-plate, But apart from the coils themselves you will have an extra heat source. So though possible, it is unlikely to be recommendable, unless done for slow charging with low current chargers, say 0.5A, and preferably with the phone vertical, to have simple conductive air flow help dispersing s

(And no , we have no info on what the difference nor why there is a difference. Could be as simple as a supplier stopped producing one or the Pro1 Parts.)

This is awesome news! David. Tanks. The big question is what connector the Pro1X uses, as they say the batteries are incompatible - but that might be the physical shape or the position of the connector, not the connector it self. We really need something to fairly easy charge the Pro1X, unless they by firmware can fix that the Pro1X does not shut down in time, but can deplete it self.

'Manual Camera DSLR Pro' here (the name might be offputting for more casual shooters, but I think the app itself is quite straightforward and has all the usual automatic modes which are also enabled by default). I just have to make sure 'RAW' is disabled, otherwise it just stalls when trying to snap a shot. For when I really want RAW files, I have the 'ProShot' app installed, but rarely ever use it. (I'm still on stock Android, though, so LOS usage may be slightly different at some point.)

My experience based on one Pro1 and two Pro1X phones (both blue, QWERTY, 8/256 GB) suggests that GPS accuracy (and maybe more) is prone to some sample variation between phones. My first Pro1X was like @AndytheNoob's. Recorded GPS tracks while hiking are probably never as straight as someone might expect, but that Pro1X showed far stronger deviations from it than the Pro1. Also, and again other than the Pro1, driving on a road with another road running in parallel in maybe something like 50 or even 100 m distance frequently made the navigation on the Pro1X jump around between both, not being ab

Because buyers and prospective buyers complained, as the 'original' QWERTY layout was actually a shifted, non-standard layout many found less easy to type on than if it would have been non-shifted. Some who would normally have preferred QWERTY over QWERTZ even chose QWERTZ because of it. It's actually one of the few "manufacturer listened to customers" aspects of the Pro1X. To be honest, I couldn't think of any other reason than already being familiar with the shifted layout to prefer it over the non-shifted one, and while I'm a fervent opponent against change just for change's sake, I think t

And they usually need flashing because of the deadzone. I've ordered at least 5 screens, all needed flashing. By the way, not happy with the zones on my Pro1x and 844dp. Portrait and outer 4mm hardly seem to engage

Has anyone in this thread received the design files for the usb pcb and priced out what it would cost to have it fabricated?

Oooh! Is that a thing in Lineage for the Pro1?! Sweet, I'll take a look as soon as the USB-C port gets back from the repair shop. Thanks 🙂

I was going to start another thread with my own experiences thus far with the Pro1X, but figured it's be better to share with one that already exists... I have had the Pro1 for the past couple of years and I loved it, it had flaws and bits eventually stopped working (Minijack socket and USB-C socket) but overall I love the device. So this is more of a comparison than a top to bottom review. On the Pro1 the keyboard was awesome, GPS was great, having a minijack port as a sound engineer is mega handy, messages were perfect and, once the various modules were replaced; people could hear

Thanks! I wrote them an email through the support form. Looks like this is happening to quite a few people. And getting ADB to do anything also seems impossible with the battery in its current state, because recovery/fastboot modes won't work.

lineage-20.0-20230529-nightly-pro1-signed.zip on May 5 security patch installed smoothly using OTA

That's amazing to me (and I'm sure very frustrating to those waiting for phones) that I've been gone so long, yet all the phones still haven't shipped.

No, I don't think so unless there is a complete collapse, and I don't think there is much evidence for that. I think the parts exist. They were set to be shipped after the devices were all shipped. But until the shipping problems are resolved, can't predict any timeline.

I've been away for years. Does this mean we won't get the extra batteries/screens ordered and paid for?

Exactly 3 years ago I ordered the phone via webpage. Still waiting and waiting and waiting ...

Yes, this is fixed. You can find the firmware in the beta testing group:

(lineage-20.0-20230529-nightly-pro1-signed.zip on May 5 security patch installed smoothly using adb sideload and MindTheGapps-13.0.0-arm64-202230408_100653)

For anyone else reading this, I did need to have USB debugging enabled for my device to show when issuing the following command at the command-line in Windows: C:\Users\david>adb devices List of devices attached <serial number removed> device I was then able to issue this command as well: C:\Users\david>adb reboot bootloader After it booted into FastBoot mode, I was then able to issue: C:\Users\david>fastboot oem off-mode-charge 1 OKAY [ 0.008s] Finished. Total time: 0.020s Thanks @E

Happened to me once with LOS 20. The battery literally ran down to 0.00 V and I had to use a lab PSU to recharge it -- definitely not something you want to do every week. @Sean McCreary confirmed that it is a problem with the proprietary BMC code, so the fix needs to come to Stock before community OSs can pick it up. I do not believe it is fixed in 2.1.5 as that has been around since September last year, and f(x)tec reportedly were working on the issue as recently as in March. Maybe in that 2.1.6-beta?

At that raises the question if it is more interesting to know that there are issue, or to hear about possible workarounds? And that is NOT saying that a workaround is a solution. But I will claim that what ever workaround that make things useful for a user, is better than just storing it in a drawer. Waiting for a fix. Our complaining about things not working in a user-to-user forum, are hardly speeding any solution at all. At best it can tell others with similar issues, that it is not a fault specific to their device alone.

You may be right, but that would surprise me. I would think if that were the case, messenger phones would be much more available from the big companies. Most of that audience out there look at me like I'm either nuts, eccentric, quaint or Grandad,,, sometime all of the above... whenever I snap out my keyboard (rarely ever use either my Pro1 pr Pro1x without the keyboard). They are somewhat mystified by how good my internet is, but they don't see the cheap moto on Verizon in my other pocket serving a secure WPA2 connection. 😉

Yeah, this stuff is complicated. Is your Pixel also on T-Mobile? Is it set up for 5G? I'm entertaining the theory that my success is due to magic. 😉

I agree, it would be initially expensive. OTH, it could have been ultimately cost-effective, given the lack of testing has made US market rather off-limits for the Pro1x. I think Planet Computer made the same decision about the Gemini/Cosmo, and the phones ended up having a lot of trouble with Verizon. (TMo pretty much worked.) I've had to abandon my own efforts to make the 1x a daily in the US East Coast. Within the same hour, I couldn't make a wifi call and I couldn't receive an incoming call despite my GSM setting. @Hook seems to be the last US caller standing. He can make p

OK, I've merged the logs generated by Discover LTE with my ping test. Hopefully it makes sense to someone. So there were timeouts as you'll see even though it was much better than usual. I have attached the spreadsheet. The column "LTE event" is just when something is logged by Discover LTE. The column "ping timeout" hopefully is self explanatory. lte_logs.xlsx

I got a tip on the Telegram beta channel to force the toggles to show in SIM setup via the following commands (requiring root): setprop persist.dbg.volte_avail_ovr 1 setprop persist.dbg.wfc_avail_ovr 1 After entering those commands, and then enabling VoLTE on my primary SIM, it does appear to have registered properly to use VoLTE, and when I called into the phone, it did ring, did not change to "3G" on the network indicator, and did not lose connectivity. I'll let the phone sit overnight and we'll see in the morning if the problem is solved.

@SlionSadly all too true in general... However... 😃 !!! I FIXED IT !!! 😃 Disassembly was easy with guide referenced above on github. Actually impressed by how repairable this phone is. Removed battery (cell), did the "prick a hole in the cell to release the gas" trick (don't try this at home - see below). Put it back together and my phone is working just fine after 4 hours' careful work. Will be ordering a new battery from Indiegogo. Obviously, the battery is degraded but phone is working 100%. Yay! * * * The full story... Root cause analysis: I now think it

OK bit the bullet & tried contacting them via the webform instead of my email lets see if they respond to that If the warranty runs out before they respond to me & they start playing silly buggers, they're going to end up paying my lawyers legal fees too -- EDIT -- Ah a request received email, thank you automated reply system

He just said he leaved the bottle there, nothing about the whisky. I guess DieBruine is very skilled at using a straw now 😉

I bet that was the hardest part, to leave that bottle untouched for 48 hours? 😂

Good sales pitch 😄