Leaderboard

I've made this error every single time I re-flash the phone. Normally I realize it just as soon as I'm happy with my config. Wiping userdata will fix it and you can start all over.

Recently received my pro 1x a few days ago and been tinkering with it on adjusting network settings to be able to work with Verizon. I went down the whole list in my settings and the ones that seemed decent is CDMA/EVDO and NR. Anything with LTE doesn't work for phone calls or messages at least for me located in Utah. With CDMA/EVDO network it sends messages almost instantly but of course its only 3G. When I have NR selected its LTE or supposedly 5G now and messages take anywhere from 10-25 seconds to send. When I message through snap chat or Facebook message it seems way better which I

I'm like a toddler, i now I shouldn't fiddle with it but I do anyway 🤣. But I'll will hold myself back and let it be

That's fair. You can get generic build instructions from the EDL GitHub page, then simply enter the equivalent commands into the terminal. I've had success in both macOS and Arch using this method.

FWIW, the OnePlus 3 that I'm using for GPS is running LineageOS too, so it's not an issue with LineageOS (i.e. the common base) per se

The Pro1X camera do protrude about 0.8mm, which is more than on the Pro1, where it is less than what I can measure.

My phone doesn't exhibit what you describe, but then again I think we can give you the all-clear there, because what you can touch on the back of the phone is not the camera itself, it is just a clear window over the camera, part of the phone's casing. The camera unit is fixed inside on the opposite plate, the one on top of which is the keyboard.

With the original Pro1 and LOS 18.1, I mostly did use 'Manual Camera' because I like its interface and it also can produce raw (DNG) files (not with the Pro1X, though), in theory giving me more options for post processing including best-of-breed noise reduction. For the Pro1X, I've now found 'ProShot', which not only can output DNGs, but also has an intelligent image optimisation, which, for example, sharpens the (generally weaker) corners more than the centre, producing visibly better default results than I've seen from other apps until now. Unfortunately it has no HDR options and therefore i

A well founded decision. It's just not compatible with my laziness 😉 Bummer, that strengthens the suspicion... And given that other Launchers also suffer from the issue, it might not even help to uninstall and reinstall Nova... but that's what I did just now. Deleted its data before uninstalling just in case. We'll see how it goes.

Hi, so after the long wait, I finally have my Pro1X. When will LineageOS be ready for Pro1X ? I couldn't find an update on what works needs to be completed and by whom. I only bought the Pro1X to work with LineageOS and don't want to run Android, I bought the phone to get away from it, like most of us.

I got all tags working after a hint here about the placement and I can confirm that the phone is very picky about the location - the tags were read only when placed on the camera sensor or very close to it according to their own position of the antenna. That's the trick.

This seems to be an Android/AOSP issue. My OnePlus 7T Pro with LineageOS 18 recently started showing the same behavior. I don't see that on my OnePlus 5T with Lineage 19.

Thank you! Yeah I'd love to carry a real camera, but right now I already have to carry 2 phones (work and personal), so just no room in general to have one with me. Maybe I can look for a really slim camera that would fit away nicely in a pocket...

I made a quick and dirty guide for Linux & macOS. If something is egregiously wrong, please let me know. It includes instructions on backing up and restore persist as well as all user data. Many commands lifted from @mosen 's posts and from the Windows guide. flashing_pro1-x.pdf

(took the liberty to clarify in the title that it is not an issue with the camera function but the camera housing)

@marmistrzAdmitted, i am not after the google free experience on this device. I have my privacy sensitive things on the Pro¹-X with SailfishOS. But since the gps reception is miserable on sfos, i thought i'd prepare the Pro¹ as a secondary Navigation and Messenger machine. Thanks for the discussion!

None of the devices I'm using has GMS installed

Now activated the google location service that was offered in settings -> location -> location services. And deleted the AGPS cache using gpstest from F-Droid. Lets see what that does.

Ah, ok, that sounds VERY familiar to the situation on SailfishOS. The problem on SailfishOS lies in the AGPS support. Mozilla at some point 3 years ago changed the license model for its MLS. Which ment that SailfishOS users lost celltower based location assitance via Mozilla Location Services. A work around attempt on SialfishOS that never really worked was to manually feed the offline availabe MLS files. But since we are on Android, maybe there is a way to enable the google location service or whatever makes stock android get gps fix instantly?

For me the "next fix" usually works. But sometimes it doesn't and getting a fix takes tens of minutes. This is why I carry my old OnePlus 3 whenever GPS is crucial... 😞 It's been that way ever since, I guess it's yet another bug that will never get resolved.

Thank you @Kaali, much appreciated! I now successfully applied the "sideload magisk.apk renamed as zip" method. I was put off by following the Pro¹-X stock rooting procedure.

@marmistrzI don't think it is necessary even. I was just not expecting that the first fix would take 30 minutes. I tried multiple times around 15 and 20 minutes, then starting to look for a possible solution -> gps.conf. But as soon i got a "first time ever fix" after like 30 minutes and then rebooted, after reboot i had instant fix. This behavior now persists, i get a fix within 30 seconds constantly and i think the issue is explained and solved. Thank you!

It sticks out a bit, it just doesn't let itself be pushed inwards. If you could look at it from the inside, you would see it having a substantial margin with which it is glued to the frame. On your phone it would seem that the glue doesn't stick well. If I were you, I'd try to not fiddle with it, as to not let it become completely unglued.

My guess is that you need to format userdata e.g. using: fastboot format userdata

I tried to upstream this "fix" for gps fixes and it turned out it never really worked for me.

Answering here too, Magisk has a good guide that if you follow you shouldn't really have any problems with the rooting. https://topjohnwu.github.io/Magisk/install.html REMEMBER ALWAYS DOWNLOAD MAGISK ONLY FROM THE OFFICIAL TOPJOHNWU GITHUB!!! Magisk has two methods of rooting which the easier one is to just rename the magisk apk to .zip and sideload update it like you do with gapps, idk why the maintainer does not recommend this method. It also has the perk of persisting through OTA's so you don't have to install it again every week after lineage updates. The boot image patching met

Yes, there is a small Hall sensor in one half and a magnet in the other. Seen in landscape, it is slightly above the USB, and if I remember correctly about 1cm in. Add from here The sensor is near the camera button about 12mm closer to the keyboard, and roughly 5mm in from the USB edge You could also display the image from here full size on the Pro1 display...

I asked and they haven't. Reassembled the phone now as it is, and I'm actually surprised it switched on and booted successfully, given how clumsy I've been... That said, and to get back to being on-topic for a sec, in the process I also damaged the volume-up button and the camera button... Thankfully the phone is still usable without both. One other thing happened, too; the screen orientation is now fixed to landscape, as if the keyboard slide mechanism would permanently signal 'keyboard out'. Any idea what I could have missed in reassembling there? (For now, if I have to use the old

I saw it initially but have not seen it since. But would be REALLY surprised if some magic secret update should have been issued that does not even change the build/number. More likely it is something that disappears after 'something', the big question then is what that 'something' is. Could be as simple as a boot, but sound unlikely that those having the issue have not booted.

I got all three working, after studying the antennas, and it is really picky on how it is placed for the credit cards with the 'large' antennas.

Yes, i missed something. With adb reboot bootloader I had to switch to the bootloader and run there the flash script. Now I have droidian on my pro1-x 😎

It probably was me. However, edl.py does the required job for the commands that QFIL does in windows. It appears to be even more stable that QFUL too!

My low light stuff is always stills (like an ice cave I checked out recently).

I also read a NFC-tag on the late sample Pro1X. I have two other tags that can be read by the Pro1, but NOT the Pro1X. I edited the title slightly. This tag works on Pro1X, Pro1 (and Titan Slim also on stock Android 11) This tag I only managed to get to work once(!) a few times with the Pro1X after maybe once every 100 retry. Else i get "NFC read error. Try again." (Pro1 & Slim OK) Have not been able a really hard time to get this one to work at all on the Pro1X. (Pro1 & Slim OK) But I CAN get it working, holding it exactly right!

I'll just note that I never do this. I don't trust Google back ups, precisely because, especially with a new phone, I worry about bringing in some element that is no longer compatible. I don't enable Google backups and I never allow Google to reinstall apps on a new or wiped phone. I will use app backups, so I'll let Nova use a saved Nova backup, and I will let Aquamail import it's own account backups, etc. I just don't trust Google and will do the extra work myself to retrieve and set up apps. Often results in house cleaning as I realize I don't need certain apps. 😄 This is also wh

As a fellow linux user, i advise to use the edl.py method explained here. Testers are using this method since month intensly. The windows QFIL instructions are a recent thing to make full reflash possible for windows users. Never tried the QFIL method myself. Always used edl.py as of yet and had no problems. But mind to make backups before flashing anything.

will do

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

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.

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.

@claude0001 I have a Pro-1x. The future of Linux on this phone is looking exciting.

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.

My E7 is currently 12 years old and its hinge mechanism, which I use a lot, works flawlessly. There are zero signs of anything wearing out - nothing is loose or rattly.

Got a response back, apparently it's something they are aware of and looking to come up with a patch very soon. So looks like it's a firmware issue, rather than a hardware issue thankfully.

if you want the keyboard in the 'wrong' direction (BB-style) with few and small keys, the least huge is the UniHertz Pocket Titan. My personal favorite is the Pro1, that is about to be replaced by the Pro1X any day (after covid and other delays - the original Pro1 is unavailable except used from e.g. ebay) There is also the Cosmo Astro Slide, with larger but fewer keys, that is also close to shipping, if they have not already begun. There are a few more options with a huge Titan and and odly folding older Cosmo, but the three above would be my suggestion to have a look at, depen

YIKES So you are saying that I can not limit Phewton to a (virtual) machine to compile edl? Phewton actually have to infect the physical machine that is connected to the phone? ... Not a chance... But thanks anyway.

droidian-OFFICIAL-phosh-phone-fxtec_pro1x-api30-arm64-24_20220804 I run sudo ./flash_all.sh but I only get this output: I: Waiting for a suitable device I: Waiting for a suitable device I: Waiting for a suitable device I: Waiting for a suitable device I: Waiting for a suitable device E: No supported device found I'm still on stock Android like delivered. Developer option and USB-Debugging are enabled. What do I miss?

Regarding that guide... ... I've read somewhere else that QPST/QFIL doesn't work from a Windows VM within a Linux installation, either, as @Casey did suggest; or does someone have other information/experience?