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

In my case, I never parted from my dumb phone, however, I use my Pro¹-X every day. It's my ultra-portable laptop in which I do all sorts of stuff. I believe I open that keyboard a few dozens of times per day on weekdays and a few on weekends. Given claude001's answer, I think I'm lucky that the keyboard still works perfectly. When I reach 1 year, I will certainly write my 1 year review of my experience with my Pro¹-X. My dumb phone is mostly used for calls and SMS. Pro¹-X's call sound quality is fine but for me, my dumb phone is more reliable to not run out of battery when I most wan

Latest update on IGG (here)

@eugenio, core team member of Droidian, had the idea of dual-booting Droidian and SailfishOS a long time ago and even did some experiments, but this was not tested in depth, nor documented. It now is! See instructions here: https://gist.github.com/Kabouik/94e9e60d84c0eeae9d48e18c11ed419e I am not pasting the how-to here, just the URL, so that there's only one place to edit if changes have to be made in the future. This may work with other secondary OSes with some slight changes, or with the Pro1x (where the extra storage could be handy), but was not tested so far. I chose to do that on th

Dear Community, I wish to announce that the solution in the provided link does indeed work! It solved my accidental lock on my Lineage OS Bootloader for my Pro1X, by clean install everything. I would like to highlight that you may need to DISABLE DRIVER SIGNATURE ENFORCEMENT on your Windows Machine. This was the one headache I had throughout the process... didn't realise I needed to disable driver inforcement. Silly me! Thank you community for your kind support! Cheers!

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

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?

I may be on the other end of the opinions here. I use my Pro1 as a phone since around two years now and it was always a pleasure. I dropped it many times and every corner is damaged but the screen and phone works fine. I type excessively and fast (+300 keystrokes/minute) and the keyboard still works fine. I even melted some keyboard buttons on the right part when trying to change the usb port as I forgot that there was another side of the phone (you can easily get out the usb port pcb). But it works fine. I removed my fingerprint sensor and added a secondary usb port and... since I use

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

I unboxed my Pro1X, put in my T-Mobile SIM from my Pro1, and did the initial set-up. I disabled wifi and placed a call to my voicemail (it worked until the cell signal got too weak, which is normal at my house). I then sent a text message and it was received. Obviously, this is a very small test, but it does show that my Pro1X does work on at least one tower/band here. I'm in Minnesota, NE of the Twin Cities. My phone was at about 50% battery when I took it out of the box. I have it plugged in. I'll have to look around for how to enable charging when powered off, how to root it,

I'm part of the Telegram group for Beta testers etc. Based on a lot of discussion from the community, which seems to have died in the last few weeks, no one knows what causes the issue with data. A couple of people went as far as installing external antennae to see if it's something with the hardware or metal case. Hats off to 'em, not sure about the results though. Again, they were from the community. No-one from Fxtec has communicated anything in months. As far as anyone can tell, all work on this issue is dead and has ceased, everyone has given up and no-one is looking at it at all. Un

I took the Pro1x with me and tried getting it to work during the flight. I'm not quite sure what happened or why. But after about 10 hours into the flight I got it up and running. I've been using it heavy as a portable travel pc instead of my bulky GPD WIn4. I ordered a router from Japan Wireless so I'm connected to the internet. My only issue so far is that the camera won't work from within Signal. During my stay here I have missed 2 telephone calls. I'm assuming this was because of the connectivity issue with this phone. But it could also be because all the noise and just how busy Japan is

I've been doing this with both my Pro 1 and now my Pro1x for years. I do home health care for my wife so my "phone" phone has to be flawless. I don't do a lot of calling and texting, but I'm the front office for doctors and insurance so when I need it, I need it perfect, I find it little trouble to carry two devices (and the cheap phone makes a great hotspot). I sometimes feel that while complaints about the call performance are understandable, people overlook what a fantastic pocket computer it is. It really has meant my laptops stay home, even if I'm traveling for a week. As far a

@Adrienspawn The original battery has 3200mAh so 2900mAh would be fine for a non-standard replacement. I also believe the connector won't be a problem although it actually looks very similar to the Pro1's default connector. I could imagine we can simply input and output electricity without even changing the circuit in the battery. If not, we are most probably able to extract the circuit from the old (broken) battery to add it to the new one. The Lenovo Zuk battery seems great. But 3mm? I believe +1mm is no problem but 3mm is a lot of squeezing. I still ordered one and will give feedba

Another update of LineageOS 16.0 (for SD835-Pro1 only) is available at https://findus.zwergenschaenke.net/~puma/linux.html#lineagepro1. The ROM dated 20230516 gives you backported security patches up to the 5 May 2023 ASB. No other changes since last month. As usual you can refer to the tarball of local mods to learn all about differences with respect to the official lineage-16.0 tree. Have fun!

@Jeffrey I edited your message. It is a really bad idea to post email addresses and phone numbers on forums. It invites collection of that personal information. I left the email in a less bot-recognizable format. You should only provide things like a phone number by DM.

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

You can store batteries at around 30-40% battery and if they aren't connected to anything, they'll hold the charge and capacity. If you want to use it for something, there are 5V to 4.2V converters, you'll get those on ebay for 3-5 dollars.

@pAnthanks for figuring this out ... New kernel is built and working in the devel channel at https://build.sailfishos.org/package/show/nemo:devel:hw:fxtec:halium-qx1050/kernel-adaptation-halium-qx1050 ... if you have any more patch suggestions let me know

The waydroid crash should be fixed by this: diff --git a/drivers/android/binderfs.c b/drivers/android/binderfs.c index 14a4bef358cd..3fd7cf48c39e 100644 --- a/drivers/android/binderfs.c +++ b/drivers/android/binderfs.c @@ -448,6 +448,7 @@ static int binderfs_binder_ctl_create(struct super_block *sb) inode->i_uid = info->root_uid; inode->i_gid = info->root_gid; + refcount_set(&device->ref, 1); device->binderfs_inode = inode; device->miscdev.minor = minor; The edl reboot and pstore console is more complicated and I need to

A new thread that may interest some of you here:

@HookThanks for the clarity, much appreciated, I'll have a play. Edit: That went well, first impressions it looks nice and smooth. Thank you Developers, Community, FxTec.

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

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.

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

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.

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... 😄

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.

Yes, I have sufficient bars--at times, more than @Hook so that doesn't seem to be the issue. There has been discussion that an inconsistent band lock (bands jumping from 4 to 12 or whatever) may be the culprit, but I don't believe anything is definitive. And I also don't believe that the OS choice has anything to do with telephony. Further complicating a found solution is that GSM is still available for TMo users (though next April, it's discontinued), so successful calls may hinge on a GSM default. Hook and I played with many scenarios, and other than his continued calling success, and m

lineage-20.0-20230525-nightly-pro1x-signed.zip with May 5 security patch installed smoothly via OTA. I have MindTheGapps-13.0.0-arm64-202230408_100653, and root was maintained.

You make a good point, and I do actually have them enabled. And they are rare. However, I understand people finding them annoying. They rarely provide actionable information (in the case of amber alerts they may not have a lot of actionable information and the ones I get are mostly so far away from me it rarely matters anyway), I don't mind that they send the alerts far and wide, but why they have to use such an obnoxious loud sound is beyond me. To get me to paty attention. Alas, I spend my time trying to kill the sound rather than Pay full attention to the message. I read every text me

...A totally different question is if it is wise to do so. AFAIK It is not a two-way thing, and should not require location to be turned on. It is the matter of the carrier broadcasting a message over the cell towers covering an affected area. And HOPEFULLY it is needed so rarely that you are unlikely to know if it is on or off. In DK they have started using this with yearly testing, with a nasty ear-wrecking sound, so this year I made sure all my phones were off,,, during the test...

Guessing here but some countries might have legislation that prevent it from being turned off. It might be something forced deep in the android kernel? Here in DK, on a Pro1 (not X) on LOS20, I AM allowed to turn them off, On both a Pro1X and a Pro1 on stock Android it is the same. I have not flashed a Pro1X with Lineage (yet), but seems unlikely that it should be generally disabled by LOS for the Pro1X..

I would open the box and double check. They are using the old Pro1 boxes and, yes, mine had the right label sticker identifying it as a blue 8/256. But I wouldn't be sure that couldn't get mixed up. Opening the box won't affect being able to return it, and maybe when it turns out to really be a black 6/128 it will be doubly disappointing, but with the shipping chaos, I would want to check. Wrong phone or wrong box?

Errrr, yeah. Completely glossed over the "on" in there. Sorry.

Thanks for confirming that... I was pretty sure I saw connectors of some sort under that wrap. I just wasn't sure how important the wrap was or if it was just a protective wrap. I'll eventually get curious enough to investigate, but for now I'm not too worried.

On the top of the battery, there's a sealed circuit. It's around 5mm wide and sealed in some yellow tape. I haven't opened the FxTec battery but most batteries have their two terminals which go into the circuit (usually a BMS - battery management system, sometimes including thermal sensors). I'm 99% sure we'll find the same thing here. And yes, the connector has positive and negative output (4 pins each, I believe), you can measure the battery by those outer pins and also charge it up to 4.2V with them. You could also measure it through your mainboard, there are golden (round) test spots

OTA worked great as well. By the way, since I had to recently do a first flash after leaving my Droidian experiment, I now have the newer MindTheGapps-13.0.0-arm64-20230408_162909. They are fine, and I don't notice any difference, so probably no reason to update.

[deleted *** replied before reading everything...]

Yes, it makes the app believe that the phone is not rooted

You can try the following commands (from telegram) to get the camera working: Just executed two commands and voila: camera works again $ adb shell setprop vendor.debug.camera.eisv3enable 1 $ adb shell killall -9 [email protected]_64 I had even transport apps simply crash (on opening the account/tickets view) when the safety net check failed.

Right click start Computer Management Device Manager Look for unknow devices or Other devices If you come across anything Google or Android, delete the device and drivers. Re-connect your phone while it is in fastboot mode, and then let Windows search for drivers. You may find them in: Settings Windows Update Advanced Options Optional Updates That should work. Flashing my Pro1x on a new W11 pc while I'm typing.

Just got around to updating to the 20230511 nightly (Official) OTA and everything is fine. It has the May 2023 security patch.

1. LineageOs doesn't mess with the persist partition. 2. You need to erase userdata before installing Lineage. So after you flash the dtbo.img and the recovery.img, as per the instructions, you reboot into recovery and select factory reset on the recovery menu. Then you are finally ready to adb sideload the Lineage zip file.

Yes they charged 120€ - 99 + shipping. When it comes time for me to deploy the new battery, if it is a fail I will send it to you if they aren't willing to refund me.

@Hook @EskeRahn @Casey Got some Happy Mail today