Leaderboard

After seeing all the quick replies I decided I would open it up and just check it out (after finding a thingiverse possible case solution). Everything works perfectly (well I haven't tried to charge it yet, or traveled away from my home): wifi seems as good or better than my 2XL, Verizon works when swapping SIM from my old 2XL (calls in/out, text in/out), speakers sound good, screen rotates as expected... Really I am starting to feel good about this device...I still want LinageOS so I don't need to have all the Google default cruft, but still being ASOP basically the phone is quick and

Edited the first post with working repair instructions using restorecon. Ii just now successfully found that way to be working on my side. 🥳🎉

It is highly advised to take a backup of your device specific partitions right after you receive the device. Update 20220829: tl:dr: Community has not found a safe way to restore backups as of yet. Making below described backups is still highly advised for a future where some wizard found a reliable way to restore those backups. For now, if you have broken sensors from flashing another OS, the restorecon method described in the "Repair sensors/ folder..." section does 100% work to fix those while retaining your attestation keys. While restoring any backup has a high chance to make the keys

@steebThere is a fix now i tested to relabel the sensors folder in persist into the SELinux context. I updated the backup/restore/repair guide with instructions. Would be great if you flash a persist backup with working keys but broken sensors. And test the restorecon fix:

SwiftKey is an Android software keyboard with an autocorrect function that also works with the hardware keyboard.

Please do keep us posted, but might be good to do it in the dedicated thread here. Just indicate that you have the Pro1 X and not the Pro1.

Correct, I already had an activated Sim card through Verizon. The Sim card I have is about 3 years old and was a replacement for my unlocked blackberry key2le to work on the network. When I first booted up the Pro1x, I follow the prompts and then change the network settings to LTE/CDMA/EvDo/GSM/WCDMA which seems to work a little better than it was first originally selected. I'm able to make phone calls and also receive them quicker but still noticeably slower than my other phone which was a galaxy s10e. Texting has its ups and downs, where it takes about 30 seconds to send or instantl

Ok, i am frankly out of ideas to blind diagnose. And the backlog got so long that i would favour to spend time in starting a fresh attempt. My fear is franceso or casey over at the official support tickets will have a lot of work to disentangle what happened anyway and you will likely have to explain every thing over and over. At this point, imo we should compile a sort of issue tracker or support request form/matrix where the most important questions are answered. I have not seen an official F(x) one. So i guess we could help them a lot with such. A good way to achieve a complete list of

@mosenwell all seems fine then with me... Only last step fail so I remove reboot at the end of command... However I already did flash my device more than 10 times now and result is still the same... Stuck on the F(x)tec logo... Really open for more brave ideas... I only got my device yesterday... Waiting for it more than a year, just checked it was working fine with android then tried flashing Ubuntu Touch via UBports which failed and I'm stuck now... 🙈 If I can make it work with Ubuntu Touch that will be just fine... Was trying to restore stock firmware after I read about that

I understand the concern and I don't want to tell you not to worry because stuff can always happen. But there are a lot of good solutions in this thread if you really want a phone like this. I'm someone who never uses cases or screen protectors (it's a quirk that everyone has tried to talk me out of since my Palm PDA days). The only thing I did for the Pro1 is to put a matte black textured skin (I used one from Dbrand that was intended for the Note 10) because it provided just enough texture that the phone doesn't easily slip from my hand. Maybe I'm just not rough enough on my devices, 😄

@Logan, right, as others say, it is nothing to lose if you try it out. 🙂 It may also worths waiting for a firmware upgrade anyway before a final decision. One advice based on earlier experiences with Pro1 is to handle the back sticker with care, your hand may easily worn its text - and that is what you don't want if you may want to sell it to somebody. I have removed my sticker of Pro1 and put it back to its box anyway. Otherwise it does not matter if you try it out I think.

If you really aren't interested in the phone, leave it closed box. As @EskeRahnsaid, FxTec will honor the warranty for the new owner. If you don't know if you want the device or not, but are worried that open box and tested will lower the value, I wouldn't worry. Take it out, try it out, see if it might be something you want after all. I don't think there is any reason to charge less for open box and tested (again, the warranty will still be good for the new owner), and, who knows, maybe you'll change your mind. 😉

The ability to run the phone for at least 5 years with uptodate kernel with security fixes.

I must admit to not having full understood. Imo your case is isolated due to the instructions having been unclear over the last days. And you where possibly lead into some action i can not really follow. First of all, it has never happened to me that flashing a persist that actually contained keys, did lead to the Key Attestation demo app to not show/use them. There is a fix for the sensors folder now (updated in the backup, restore and repair partitions guide). Hopefully this will help everyone with broken sensors only. To debug your case, lets start all over. I would first of all make

The EDL cable is just a USB cable with extra switch to short lines. It is only ment to set the phone into EDL mode more easily than using `adb reboot edl` or the manual "Both volume rockers pressed until droid flashes shortly" methods. An edl cable has no implications to the flash process other than that. stolen from https://wiki.bananahackers.net/development/edl/diy-edl-cable

@mosenare you using special edl cable or normal USB type C cable that comes with device?

To clarify. I try to not suggest anything. Missing competence for that. I merely try to describe what happened to me, like usually in a user forum 😅 Reseting EDL by booting the device into EDL again worked for me to make the edl commands continue. But i never had to do that consequently many times and have no idea of the implications of doing so.

Thank you. I missed these response. Probably just zoned out reading threads...

I assume that the missing OTG support is part of the issue.

Hi. We(me+Ichernev) are currently messing around mainline kernel on Snapdragon 662. We are going to submit some base stuff pretty soon depending how maintainers will go on merging simple compatibles. However we are working on other devices, Redmi 9T(me) and Oneplus N100(Ichernev). While progress is going to be slow we will get there at some point, one of harder things will be Adreno 610 support due to no GMU but i hope this will be done by SoMainline for 665 SoC so we just can pick it.

will do

Unfortunately the default bootloader does not seem to have a recovery image in it - at the least the 'early unit' I have does not, nor does the retail Pro1 (no X)

Thanks already for the confirmation that you found your keys. That's cool and you can pat yourself on the shoulder for not deleting them by chance 😄 However, i understand correctly that you did alterations to all of your backups by copying into all of them at some point? Then it would make much sense that restorecon can also fix all other folders. When you have your device rooted and moved to /mnt/vendor/. Just try the restorecon -nvRF persist on the whole persist. The verbose output will show every file restorecon can relabel and thus put back to context. The -n option is to no

This is my situation, I have two backups of my persist partition, from when the phone had broken sensors but working attestation keys. They contain a data folder (with files similar to yours) and have only been copied (so I could modify the copy) or mounted read-only (to copy files from). restoring any of my persist backups with the data folder does not restore the attestation. I'm not at my PC until tomorrow night, but I will try out the restorecon method on the data folder when I get back.

@mosen Oddly, this did fix the sensors, but not attestation. I feel quite certain it was working when I backed up the image, but unfortunately I dont have time to try re-flashing again this afternoon.

Pro1 and Pro1X has the same size, if you need to adjust, that is because of differences between 3D printers. Anyway, there are screen protectors made for Elephone U Pro which has the very same dispay, even there is a company which sells screen protector specfically for Pro1(X)... Elephone U Pro is the same regarding screen protector.

Please share details on connecting to Verizon-- did you use a method posted here for the Pro1 or did you do something else? I assumed you had a sim from a previous Verizon phone that you used? What steps did you take. I'm interested in whether there's something about the Pro1x that makes it easier than it seemed to be on the Pro1. Do be aware that it might not last. Verizon is becoming more aggressive about blocking non-approved phones, especially as they take down their CDMA network. Keep us posted if anything happens.

Hi! I also had this exact issue, and contacted support. According to F(x)tec, this is a known firmware problem, and the update is on it's way. No need to take apart your phone. In fact, a few days ago, for me this went from being a reliably reproducible and persistent issue, to suddenly vanishing. My phone's sound now works perfectly at all volume levels. Either the problem is transient after all, or there must have been an update automatically pushed through. I'm still running the stock android OS that came out of the box.

In another thread, I have showed my daily driver Pro1 and my hard rubber case made for P20 Pro which has needed some hand cutting but basically it fits. One disadvantage is the different position of volume / power buttons, so you can not feel their exact position but that is not a huge problem for me. Here it is (see near the end of the video):

I just received my unit yesterday and took about an hour to finally connect to Verizon network in the US. I had to update Google messages to finally send out sms. It does take a bit to call someone but I did finally change the setting for only CDMA. I have notice while I'm at work browsing the web using only my data it disconnects all of a sudden. When I turned on the wifi it hasn't disconnected at all, which is strange,. Not sure if it disconnect because was using to much data but that has never happened before with my other phones. I haven't tested my GPS but will this weekend.

@liquidvx I had the same issue this morning and used the last line on the site: https://github.com/droidian-images/droidian#troubleshooting fastboot format:ext4 userdata Then I flashed again and it works. Kamera is not working. Greetings

There are now a number of wallet-style cases on Amazon made by BINFEN Color but sold under various brand names for about $14USD (I did a search for fxtec under cell phone cases). It looks like they all ship from China or Hong Kong. It's not clear how the phone attaches--other models made by BINFEN seem to snap into place. There are no reviews for any of these cases yet but I may try my luck with one since they are inexpensive.

@mosencan you advise what is the last command meant to do? edl --loader=prog_firehose_ddr.elf reset reboot Is it the same like: edl --loader=prog_firehose_ddr.elf reset Asking because it seems doesn't work for me with reboot at the end 🤔

👍

Okay, I've now tried this, with no luck. I QFIL flashed the whole device to stock Android, then used the edl Python script to write out my persist backup, and I've got the same place as I get with fastboot, i.e. broken sensors and no attestation. Bit of a mystery. Would be good to get more data from others, in case I've somehow just broken the keys in my persist backup and don't know it.

I've had this happen once as well. Boot back into EDL mode (turn of the phone, then hold both volume keys and turn on the phone, it should show a logo very briefly, then go to a black screen) and run the flashing procedure again. This resolved my issue. It might take a few times to get into EDL mode correctly (I've had it boot into EDL but only memory dump mode and no firehose a couple of times first).

I'm currently having issues with my speakers. Playing a video or songs through my Spotify, the volume suddenly decreases even almost set to 70% volume and then go back to normal. Is it a hardware problem or is it a firmware that supposedly they are working on for a future update? Just barely notice it is also doing the popping/crackerl noise also on the bottom speaker

@steeb $ ./flash_all.sh I: Waiting for a suitable device I: Flashing data/boot.img Sending 'boot_a' (34328 KB) OKAY [ 1.318s] Writing 'boot_a' OKAY [ 0.173s] Finished. Total time: 1.528s Sending 'boot_b' (34328 KB) OKAY [ 1.262s] Writing 'boot_b' OKAY [ 0.132s] Finished. Total time: 1.419s I: Flashing data/dtbo.img Sending 'dtbo_a' (119 KB) OKAY [ 0.013s] Writing 'dtbo_a' OKAY [ 0.002s] Finished. Total time: 0.02

@claude0001 Android 12 remove access to the data folder (google "privacy" schizophrenic paranoia, or simply a way removing your right to access your own phone ?) so the archlinux container doesn't install properly, and I didn't find a way to correctly install scripts from SDRausty yet. But I guess it will be a workaround in future, I really trust in the knowledge of this community to make the pro1-x better !

Still not really Linux as in mainline Linux, but speaking of LXC, I have tried to update harbour-containers today to fix some long lasting issues that were keeping many users away: https://talk.maemo.org/showpost.php?p=1574540&postcount=240 It's being tested in the fork, everything may not work, I'm not a dev. If all goes well, I'll make a PR for upstream and push it to the Chum repository (a FOSS GUI store for SFOS).

I'm not using Termux myself. But, in my (very limited) understanding, it still works on Android 12. It is just not receiving updates (or is not installable at all?) from the Google App Store (because it still targets Android 9 SDK). The F-Droid version should not be affected by this, nor manual installation using the *.apk. There seem to be some worries that, in the future, Android 12+ might shut down apps targeting Android 9 SDK via SELinux policies. But would this necessarily also affect LineageOS 19.1+? Anyway, I disabled SELinux on my Pro1 (LOS 16.0) long ago ...

I am in the early stages of tracking something very strange indeed. I've been getting alerts for a few days from my own internal network monitoring (Nagios) that my primary wifi AP is often dropping packets on its ethernet interface. Since I've been busy with other things (not the least of which is the Pro1-X itself), and the packet loss isn't enough to cause problems, I didn't look into the situation carefully until last night. Once I pulled up my reachability graphs, I realised that the issues seem to have started at exactly the same time I received the Pro1-X: There are a c

I'm afraid the solution using Termux and archlinux container from SDrausty won't work any more because of Android 12...(sigh).... That's why I camp on LOS18.1 on my Pro1, before finding time to reinstall all stuffs and probably flashing (un)official LOS16.1 maintained by @claude0001

In the stock ROM I've been testing radio connections a lot in these days. I have LTE, WCDMA and GSM. I have a perfectly working Mi 9T Pro. Comparing the signal levels, there is no significant difference (maximum 5%) on any of the networks. I noticed that with LTE (B20 for sure, B3 I don't know yet) the Pro1X randomly drops the network for a moment (about half a second) and reconnects. This happens roughly every 20-100 seconds. I don't know if anything has an effect on it. Sometimes the upload and download arrows next to the 4G icon on the notification bar disappear for a second and then return

Thanks to MaemoLeste, the N900 can run a 5.x.y kernel now (I should try it at some point). However also here, they had to somehow reuse the original closed-source driver for 3D graphics, and sadly, also the remaining hardware is only mostly supported. And that is 13 years after the device was released ... Not to be misunderstood: the MaemoLeste people do great work here, they are just too late to the party. Pretty good illustration of my point above, about how obsolescence catches up with the phones before their support in mainline Linux matures sufficiently for being practically useful. 😞

You are obviously very skilled with Linux and embedded systems. Sorry for spamming you with technical details on chroots and LXCs that must be completely clear to you. 😄 Hopefully my post can still serve to encourage others who just want to run a GNU desktop environment on their handheld without sacrificing regular smartphone capabilities ... All your points a perfectly valid, and I couldn't agree more that support in upstream Linux should be the ultimate goal, always. Unfortunately, the mobile phone world being what it is, this often means that the hardware reaches obsolescence before it

Hello, be aware everyone of the following issue: Yesterday I tried to check the GPS functionality with this: https://docs.ubports.com/de/latest/userguide/dailyuse/location.html I turned on WLAN, insert a SIM Card and connect the charging cable. 15 min the device was very hot and shut down. I had recognize it to late because I only looked the display. After that I let the device cool down and booted up again. Greetings

Just for the record, for lack of a perfect solution I've now applied on the back of the Pro1 X what probably kept my Pro1 from becoming completely damaged because of frequent drops: clear packaging tape on the back (the one I've used it German 'Tesa'). On the blue Pro1 X, it doesn't even look quite as ugly as on the black Pro 1... The slippery back of the phone is arguably its most dangerous aspect; the phone slides out of your hand as soon as you loosen your grip a bit. And my impression is that the blue shell didn't help there much, if at all...

...or around VoLTE / VoWiFi settings. I also had problems on Pro1 when switched mobile data from one card to another (after doing also an Aeroplane mode on/off switch) that the other card started having problems of receiving/initiating a call because it wanted to also use mobile data but otherwise I did not see VoXXX to be working, however, both cards work well when mobile data was switched to the other service provider (only one of my cards support VoXXX). So it also worth looking around this setting as the source of such problems.

Adam helped me to get Waydroid to work! And shadow.tech works in Waydroid (no sound nor keyboard, though, so it's somewhat limited): See how to get Waydroid to run on SFOS and what doesn't work: https://github.com/sailfish-on-fxtecpro1/droid-config-halium-qx1050/issues/1#issuecomment-1215734546 The current list of issues after just one hour of use: Camera doesn't work (who cares? But it shows that some hardware is not visible to Waydroid) Vibration does not work Landscape rotation is borked (it just stretches ev