Leaderboard

Well the high demand may have been true a few weeks ago. But consider the fact, that a lot of people have now ordered a pro1x from the IGG campaign. I understand your desire to sell it as high as possible. But you know, selling it for the highest possible price always takes a lot of time. I don't want to buy your phone and don't want to talk you into lowering your price. I am just saying I think if you can get the original price somehow, I would not wait to sell it. But as said, that is a personal opinion, and I might be wrong.

I have been using LOS 18 for 14 days and i am quite happy with it. Volte works on the latest builds and the phone works fast, would say like LOS 17. Like the new android features. Didn't find any bugs besides not working vowifi yet. Magisk v21, Gapps, xposed, banking apps... everything works. Not sure about my sound quality during call (me not them) but was shitty before.

I'm no expert here, but based on the first factory image files from October 2019, I don't think you need the set the active partition (and you certainly don't need to set both active) because you are sending the same files to both partitions. Really doesn't matter where you boot to. Also, in the Oct 2019 bat file flashing "userdata.img" is commented out and there is no such file. I would try commenting that out and just doing fastboot erase userdata, which is what I added to the October bat file when I used it to flash the October 2019 stock. I do know if Userdata isn't erased befo

All server startup scripts in Debian are meant for systemd. They are not expected to work in a chroot (where systemd is not around). Just start /usr/sbin/xrdp-sesman and /usr/sbin/xrdp manually, as I do in the final lines of my chroot startup script (attached to the post). For initial debugging, it is quite useful to start them with the flag --nodaemon from an interactive session, this way you can see what actually happens as you try to connect.

@EskeRahn Just did a test with the voltmeter. Got this readout. But I just tried another reflash and got a different result from the flasher, as per the other pic. The fact that this has happened is a little more encouraging.

As it can be seen from a computer as in loader mode, I would say that it is very unlikely that it is the USB-port. And as you reported it as 75% shortly before becoming unavailable, I do not think that it is (or at the least not was) depleted. Why you are not allowed to flash it once it is connected in loader-mode is really beyond me. My best suggestion would be to follow the advices from others and try from different computers. (And/or with different cables) Especially slightly older computers with a USB-2 and not USB-3 port, as I repeatedly seen this reported as helping others. (gene

Thank you all very much for your answers! Please excuse the late response, I didn't have time to look in the forum for the last few days. As the question is now solved, @Eske Rahn or another moderator could close this thread.

I have noticed it also in my Moto G6 after upgrading from stock Android 8 to 9 and if I remember well, it was in better place before. So it is not Pro1-related, it is Android 9-related. I don't have problems with voice quality unless using speakerphone. The basic but huge problem with speakerphone mode is the reversed speakers - one of them is muted and the other one produces sound, but they should have been interchanged as currently the one next to the microphone produces sound and the farther one is muted which is not correct. Once they modify it to work the other way, this proble

I guess not being able to crack the bootloader is the only "security" feature left on that phone with its outdated, unsafe, unsupported stock Android – a device that used to be marketed as "the world's most secure Android device"... Security updates stopped just a few weeks after I bought mine. Anyway, as much as I liked the phone, I never liked the portrait-orientation keyboard...

Hello, I am about to order the pro1. But I still have a few doubts about it... I have a blackberry priv for 3 years, changed the batterie, but it's dying again... batterie goes down to 50% to 0 % in a second. I also have a lot of overheating problems with it, and it restarts for no reasons almost everyday, sometime 3 times a day... So I am about to give up with that phone because it's getting worse. Before I buy the pro1 I need to be sure that I will not have the same problems that I have with my priv. For those who had both phones, can you tell me why the pro1 would be bette

Merging device specific changes that were done on LOS 16 to newer version of LOS. And there are also other msm8998 devices that make the same changes. So if someone on another device that uses the same platform makes a change... you can merge that change also in you build. If you don't have a device you can't test it 😉 but if it builds.. it builds. You can see that here. Search for a device, click some changes, follow them to the original author.

(I split the posts on Lineage 18 into a separate thread here)

I got the very same error under Windows when the flash was unreachable, but to be sure, you may need to debug USB communication. I have tried it under Linux, but it was clearly visible in Wireshark what happened. First flasher uploads a binary to the phone, then run it, then xml-like communication starts and that one is shelf-explanation.

Where are you getting these links from? My google fu not working well 😄

Well there is an older unofficial one in the thread, lineage-18.0-20201121-UNOFFICIAL-pro1.zip is the latest test one that i have and has volte working, but has gaps included. lineage-18.0-20201120-UNOFFICIAL-pro1.zip is a bit older but also has volte working and no gaps If you are flashing this you also need a UNOFFICIAL boot image that you flash prior as you can't flash from the OFFICIAL build. This one works lineage-17.1-20201118-UNOFFICIAL-pro1-boot.img , it is lineage 17.1 but you can use it for flashing 18. You can get extract the newer ones from the firmware package wi

Maybe a stupid idea, but can you superglue the broken corner back together? I'm still working on getting a usable 3d printed case. I'm working with one of the "manufacturers" (aka a guy with a 3d printer) on treatstock to edit the @LIMA design a bit to get it to fit my phone better and not pop off. If I get something working I will share what I can with the community.

I forgot to add, I am puzzled by system and vendor being commented out. You need those. I almost suspect they included one of their test batch files by mistake, I would restore those.

The original post mentions 16 files to flash but the latest archive contains 24. What do we do with the other 8? Is there a certain order to follow? Also the fastboot_all.bat causes confusion. The 'fastboot flash userdata.img' command results in an error: unknown partition 'userdata.img' fastboot: error: cannot determine image filename for 'userdata.img' And both the system.img and vendor.img are commented out. Is there a specific reason for this?

No, that is the way I deliberately can put it in this mode. 😉 My wild guess was if your volume keys (seen from the phone) appeared as being constantly pressed, that might prevent it from ever trying to boot. Pocket lint that crept in could be an issue, so that is why I asked if they felt moving 'normally'. (And positive sign that it charges with 1A 5V too, that is totally normal, and reduces when above something like 90% charged)

@EskeRahnWhen you say about pressing both volume buttons accidentally, when you plug your cable in, I'm wondering if, due to the case not being made for the Pro1 it has put pressure on the buttons and somehow, as I've put it into my pocket the power button got pressed. 🤔

(merged the two threads)

I don't, but a couple of guys on that thread are reporting shipment notifications:

Laziness... Also isn't the clock broken currently, or something like that? I figure it's running stable enough as it is, maybe I'll update after a few more releases! :P

I also had/have a PRIV. I did enjoy it, but also have the battery dying on it with constant reboots/refusing to charge. I was keeping it around just to be another sync point for Resilio, but it's getting less and less useful due to the battery. I have had my Pro1 a little over a month and it's taken a while to get used to the landscape keyboard again. I've installed Lineage OS 16 and recently playing around with Debian running as a chroot so I can do some little bits of coding. The battery life seems to be great and I don't bother disabling GPS/WiFi/Data/BT like I did with the PRIV. Of co

How do you know they have a batch ready? My Samsung S5 mini is growing veeeery annoying 🙂

The VNC client app I like to use for all connections is VNC Viewer, because it has no on screen GUI to block views. Some have little bars or dropdowns for touch screen interaction, and this doesn't. The server is Xvnc which I think is TightVNC or TigerVNC. It's LineageOS 16, the first stable official build. Also have issues with wifi that I forgot to mention... anything 40% or lower drops in and out constantly on top of just generally weak reception on all networks. Another dissapointment. This is a HTML version of my vimwiki page of notes on the project which has a lot of confi

@EskeRahn I should be receiving my voltmeter in the next couple of days. Let you know what my findings are. No response from FxTec as yet, but I did get a reply from Clove Technologies asking me to keep them updated on this.

Yeah on my other phones it was just Settings -> Call Settings -> Call Forwarding. The Pro1 sucks a$$ s far as the voice quality so when I am home I always use my landline. Instacart had called to talk about a grocery order so that took a little while. Buttons were being pushed and beeping even though the phone was on speaker and I didn't touch anything. And the speaker level is horrid and there is a lot of feedback. And that was using Wi-Fi calling too.

I have also searched for a while before I have found it. I don't know if it was changed in Android 10 or later, but it is in a very strange place in Android 9.

Thank you. That was very unintuitive but I found the settings.

Open "Phone" application, click on the three vertical dots, then "Settings", "Phone Accounts" (or similar menu item, I use my native language in my phone), then on the specific SIM card, then "GSM call settings" (or maybe CDMA) - or similar -, then "Call divert" - or similar -, then "voice". You will find your carrier's settings there.

Sure you are allowed to in this forum 🙂 That it is not official does not make it illegal, but perhaps it is not the optimal thread for it. IS it the XDA build mentioned here, or is there another one?

lol ... yea ... I'm contemplating opening my own support ticket ... but in the past, they do some public post when its a full batch, not a single user thing Just trying to cover my bases before I start rattling cages! 😄

Hi all only for inspiration. I had problem with my cover. Fxtec was very big problem eject from cover so I did fix:

They also have mentioned renewing their contracts, which I think is a positive thing. Their communication is still pretty bad, but I have some hope for the future as long, as @VaZso mentioned, new Covid difficulties don't arise. I think the batch of Pro1s that will be shipped this month will fill most of any previous orders of long standing (and I suspect fulfill the ten Pro1X orders promised for Xmas). Obviously, I don't have any idea what the cut-off will be. I would expect, if there are still a lot of Pro1s ordered but not fulfilled, we would see a shipment in Jan or Feb as they gear up

I hope so. They already have experience how these manufacturing-related things are going and they seems to have chosen a relatively wide timeframe. They currently have close to 1000 backers which is a number what can be clearly seen, so there is a chance a manufacturer takes them seriously enough to fulfill their needs, maybe the very same manufacturer is willing to do the process for them which is very likely. They know the background (remaining Pro1 orders, expected speed and potential problems) and they should not make the very same mistakes. I hope COVID will not cause a s

My understanding is that they have no obligation the provide any warranty. However they said they would provide warranty on the IGG page.

Not quite. If you buy the screen assembly I assume it is, but the BOE spare screens we can get from AliExpress just got a hole, so the actual LED is behind the display with the speaker and the narcissistic camera, ADD: Roughly here on the long PCB next to the camera (Crop from the picture 73 of the disassembly manual)

I have tried to take some images, but none are good.... in showing neither Pros nor cons. The light is made from individual R+G+B LEDs, with no diffuser. Clean R, G, B colours work just fine and bright, and that is the ones used in stock. If you try to use base colour combinations to get more colours, these will not keep the combined colour when viewed from a shallow angle shadowing one of the base colour-LEDs If/when I need to take a Pro1(X) apart, I will try to add some kind of diffuser above the LEDs.

Well peeps, guess who apparently volunteered their precious Pro1 & screen case to be tested? Me. Happy Cyber Monday? 4 foot drop from counter to tiled floor. 3D printed screen case is caput, broke in half due to the impact. But even though it cost it it's life, the case fulfilled its function of limiting damage to the screen to the bare minimum, which in this case is the bottom-left edge of the Pro1's screen fingerprint protector got peeled about 2 cm out of place. No other damage. Since the bumper case is damaged beyond repair AFAIK, I'm ordering this universal bumper case to tr

CTIA (Also known as AHJ). I do not know if any new phones/phablet still uses the once very common OMTP? I remember that Nokia and SonyEricsson was using OMTP a decade ago, but it is rare to find new devices using it, except those that keeps backwards compatability with earlier products in a line like playstations. See e.g. https://help.longtailproducts.com/hc/en-us/articles/207970396 The CTIA headphone plug is one of the few standards aPple followed (well almost...) with their Iphones, and after a mess with converters as aPple grew, most have changed away fra OMTP since. It

I had the same behavior with the stock camera app, clearing data/cache for it in settings->apps fixed that (it seems permanently). My best guess is that an updated version of the app can't cope with the data from the original version that comes on the phone. Also my friends never complained of video quality, but they're used to me using a potato cam so I'm not sure that means anything xD.

Does the the ebay requirement apply to selling within the EU? I would think you could easily sell it within the region.

I would print one for you but I would wait for someone less far than me to cut in shipping price, otherwise I'll take a look for it. BTW I'm in Canada

Hi Guys, Just an update of the progress. After the front case breaking twice due to drops, I made it a bit beefier. I also Cut out a section so that the front case does not sit on the first row keys. Not sure if it is enough for people with bigger fingers or with long finger nails. I'd need to find someone with thicker fingers to try it out. I also made some more adjustments to the the back case for usability. I don't have super detailed pictures of the back case adjustments but I am fairly confident that I am close to finished product. Here are some shots. If yo

Adding to this, no matter how large a person's hands are, relative to the keyboard, the Pro1 *will* take longer to type the same content, when compared to a smaller keyboard, with all other things being equal. Has anyone ever played the game Whac-A-Mole in an arcade? The key to getting a better score on that is to minimize how far your hand/arm must travel. Keeping the hammer close to the machine and in the middle of the holes reduces the delay each time you need to pound one of the teasing critters. If you make that machine twice as wide, it will take longer to reach the mo