Leaderboard

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.

F(x)tec will release flashing instruction using Qulcomms QFIL software on windows soon. The unofficial method to flash the provided EDL images that testers used on linux would be: Install EDL-Tool by bkerler https://github.com/bkerler/edl Put Pro¹ X in EDL mode using adb reboot edl when you got adb available. Else, Pro¹-X needs to be put in EDL mode manually. Hold power and vol + and vol - During boot and release all after android logo flashes up shortly and goes into a dark screen second. If it stays dark after you removed the combo, Prawn is in EDL mode.

I found what the problem was. I issued the following command: adb reboot bootloader After that, the device accepted the following 2 fastboot commands and off-line charging works: fastboot oem enable-charger-screen fastboot oem off-mode-charge 1

@matf Please add this warning to your first post. Users should backup their persist partition as early as possible. 1. Attestation data in persist partition is unique to the device unit, therefore backup of persist is strongly recommended to people attempting to flash a custom OS. 2. The consequences of losing this data currently don't seem too critical, as the standard attestation checks like SafetyNet are passed on such devices. But they won't pass rarely used hardware attestation checks. 3. Warning, the rawprogram0.xml.bak from the EDL package will flash your persist partition with t

Another shipping update on Indiegogo: So we now know that there is a – albeit smaller – third batch coming, too.

Agreed, disclaimer, i was just curious and can not fully oversee the implications. Checking the device with fastboot getvar all revealed slot_a to be active "anyway". So i was curious to try what happens without the set active command. Note, the original ubuntu instructions even had a set active a before the boot image flash. Which is already omitted in the first posts instructions.

I will highly recommend NOT omitting this tiny step. Remember that an OTA update swaps what is active between A/B so could easily become a mess Alternatively flash the boot image to booth boot_a and boot_b, so it is in whatever is active.

I certainly didn't do anything that would have changed the system partition, and if I'm not mistaken, system, boot_a, and userdata are the only real parts in play here, and the latter two are overwritten in the Sailfish flashing process. It's curious indeed. Right now I don't really want to undo the work I've put into Sailfish, but it will be interesting to see if anyone else runs into a similar problem. Maybe it's just me, and the warning added to the first post is unnecessary.

Interesting that that worked for you. I have just tested that exact boot.img on my own device and it does not boot. Flashing back the image from last week and I'm back to booting just fine. What is your hardware configuration? I am 8/256 (and the device is black FWIW).

Re: First post: I successfully flashed, omitting the set active command. All i did after receiving the Pro¹ X with Android built 2.1.2 was: 1) Download Ubuntu Touch image and extract the boot.img From this build (2830649718 artifact.zip) 2) Download the SailfishOS 4.4.0.64 devel build and extract the userdata.simg From here (2807435728 artifact.zip) 3) Execute fastboot flash commands fastboot flash boot_a boot.img fastboot flash userdata userdata.simg Happy sailing! Hope this wrap up helps someone.

So far this is working pretty well, but I may have run into my first example of "not quite ready for primetime". I'm trying to set up my personal VPN (OpenVPN) and while I can get it to connect just fine if I execute the openvpn client myself from a root shell, it will not connect via the (not especially helpful) UI. journalctl reveals two errors possibly related: Aug 11 11:37:09 Pro1-X connman-vpnd[548]: error setting gid -1 Invalid argument Aug 11 11:37:09 Pro1-X connman-vpnd[548]: error setting gid list Invalid argument This is perhaps beyond the scope of this thread, but just

I was able to retrieve my package from the FedEx location today by showing my identification; all set.

Following @esialb's thread on Ubuntu Touch, here's one showing that SailfishOS works too: ——— Instructions: - First and foremost, backup your "persist" partition. Better safe than sorry. Instructions are in other guides, Please, do not skip that step, there is no other way back to the vanilla persist partition. - Download and extract the latest artifacts.zip from the SailfishOS port repository: https://gitlab.com/sailfishos-porters-ci/halium-qx1050-ci/-/jobs - Pick your clacky Pro1x, power it down, hold down [Volume -] and [Power] until it boots

So as some of u know i recently bought and received a Unihertz Titan Slim true kickstarter its can be found here : https://www.kickstarter.com/projects/jellyphone/titan-slim-the-new-sleek-and-slim-qwerty-android-smartphone/description I wanted to see if there is more people here who have bought this device Why make a post about this phone ? Mostly because i want to share the owner experience is with this phone I might not be very pleased with FX tec and the way they have gone about their whole pro 1 x campaign but that does not mean im not excited to receive it in the future

I've seen it reported that the Pro1 doesn't come with its own recovery. There is a standard recovery included with the phone's firmware. I think there may have been some confusion due to the way you need to access recovery mode. To access recovery mode, you have to either: A) Hold down the volume up when you boot the phone (before the logo screen comes up) or B) Use "adb reboot recovery" from a connected computer or C) Boot into the bootloader (by holding down the volume down when you boot the phone (before the logo screen comes up) O

Yeah, i am getting it hard today... I did use the edl command and just copied the fastboot command from XDA without testing... There must be a way using adb. But i am to tired to get that right now. Sorry for the confusion.

No - it makes weird popping noises, and when I set the audio really loud (like a YT video, put the volume to the max) it works, pretty much. It's weird. I've managed to power off and power on my phone (not restart) and the effect was gone - ONCE. Worked for a while, then after some time (I can't tell what have I been doing exactly) it started behaving like this again.

Yes, I noticed that. Next draft, I'll just make it a general statement, if anything complains about being unsigned, say yes. 😄

Looks fine to me. One minor detail. Flashing AICP, the 47% blah blah click yes is on the main zip, and does not appear again on the Gapps zip. So Lineage and AICP acts slightly different here.

New version of the pdf placed in my post at the top of the thread. Made a bunch of revisions based on more experience. Hopefully things are clearer, but I probably just corrected some problems and introduced new ones. 😄 I should just make it a todo list and take out all of the explanation. 🙄😂

Mine arrived today (Australia). The blue colour looks pretty nice to me. 👍

Me too: https://eskerahn.dk/?p=4539 Most important: Settings ► Intelligent assistance ► Other Settings ► Home key function ► Double press to launcher.

HA, I replied you in the other thread too.... EDIT: Cleaned up my mess, now point back here! I'm pretty sure that is what is going on. I both tried to do multiple "Advanced", "reboot to recovery", and that did not change a/b. Then did a new flash of AICP, and instead did "Advanced", "reboot to bootloader", and there "Recovery", and it also showed it switched, I do not know if there is any other way to get the Recovery to refresh it self than to reboot to recovery. But would be nice if it at the least gave a warning if you attempt to make a new "Apply Update", that it will NOT go to the

Indeed, the device needs to be in fastboot mode for fastboot commands to work. 😉 The alternative method of activating that mode is by holding "Volume down" + "Power" when switching on the device.

Congrats. And very interesting desktop setup! I start to understand what you meant when you wrote it is optimised for operation via keybindings. 🙂 As you have the same setup on both devices (Pro1 and Pro1X) now, can you say anything about performance? In the past we worried a lot about the Pro1X's slower CPU (after its re-design). As, in our Linux containers, we rely on all-software rendering (llvmpipe) there could be a significant difference e.g. in OpenGL benchmarks or video playing ...

Should have answered here instead of in the AICP thread... 😉 You are right. The trouble with being more of a follow the recipe guy than deeply technical. What I'm really talking about, and I will reword to make this clear, is that I am simply going by what appears on the phone screen. After flashing the update, it shows one slot at the top of the recovery menu (e.g., a;) and then, after rebooting to recovery, it shows the other slot at the top of the recovery menu (e.g., b). I don't know what is really going on under the hood, I just know you need to do the reboot to recovery after fl

I do not know about the Pro1-X, but for the Pro1, the command to enable charging when powered-off was fastboot oem off-mode-charge "1"

You are right. The trouble with being more of a follow the recipe guy than deeply technical. What I'm really talking about, and I will reword to make this clear, is that I am simply going by what appears on the phone screen. After flashing the update, it shows one slot at the top of the recovery menu (e.g., a;) and then, after rebooting to recovery, it shows the other slot at the top of the recovery menu (e.g., b). I don't know what is really going on under the hood, I just know you need to do the reboot to recovery after flashing the update if you are going to install Gapps and that the c

Same hw config but i got the blue IGG model. They should be 100% the same, just different casings. I flashed sfos as first action after unboxing. Maybe you changed something to the stock settings the Pro¹ X got delivered with? If you are not keen to debug the issue, i'd just reflash to the 2.1.2 build factory image using EDL/QFIL to have the device in unboxing state again. Like described in this thread:

Huh, guess that depends on a country. My courier did not want any money from me, but that happened before with Fedex. They don't collect cash for taxes directly, they usually send me an invoice after the delivery (with post, not with Fedex 😛 ).

It does light up when I plug the charger in. Dang that's weird. I can see absolutely zero settings related to it, maybe it needs an external app for it - wonder if it's just the Android build that doesn't have it or they just ditched this functionality.

I don't, and at the moment I'm playing around with Sailfish, so I can't go looking. It should certainly light up, even in default configuration, when you plug in a USB cable to charge.

It is blue 😄 Wait what!? OK, there's something there indeed. Do you know where are the settings for it in this stock Android?

But is it blue? 😁 By "notification diode", do you mean the general notification LED on the front of the device? There is one, RGB, upper right corner.

Thanks for testing. Maybe what recovery boot image I have in slot boot_b for some reasons make it behave less bad than yours - I have no idea what version.... nor do I know how to find out what version is flashed in slot boot_b? Obviously I could flash to both boot_a and boot_b, that is dong the flashing double before first boot, To make sure I am in a well known state.... With the risk of making it unable to boot AICP-S. I will consider this, the next time I'm in need of a wiping it anyhow. ADD; I tried sending the boot image to both, and it worked fine, (with no reset, and nothing missin

In your guide it says that the step rebooting into recovery from within recovery "will switch the active boot slot", I believe that is strictly incorrect, When I do that it says "active slot: a" (or b) NOT changing, I believe that the "apply update" from within the bootloader of the main flash that does the switch of active slot (without the header of the recovery reflecting this), and then the reboot to recover boots into that slot... Note that flashing e.g. Gapps, does NOT change the active slot, so it is part of the flashing the main 'only'. So that a more correct wording would be e.g.

Oh of course. My post was intended to be a "helpful hint", not a "waah this doesn't work". 😆

Received today. No duty/tax payable (Australia). We must have a free trade agreement.

For what it's worth, we are grabbing files off a developer build server, whose purpose is to compile untested bleeding-edge code so the developers can test on actual hardware. Trying to install and run binaries from it is way out of scope; the intended use is to assist with the process of breaking the build in an orderly fashion.

(For what it is worth, we might have similar issues with newer boot images for AICP-S for the Pro1, see this thread)

Over at IGG, "Buffer Bear" was charged "UK. Duty of £51.45" so it seems to vary quite a bit...

If you still haven't received one when all of batch #1 has shipped, you will have a reason to complain, and rest assured I will complain in case the phone I ordered in Sept 2019 won't come in batch #1, too. If you cannot contain yourself for the few more days that will take, all the more so after you have been waiting for more than two years now, your fuse it too short. And then tell us which other tiny, but "thriving" and "efficient" company has been denied an already promised supply of SoCs, making scrap out of their mainboard, in place of which they then had to create a completely new

When holding my phone in certain positions, my hand rests against the fingerprint reader. When using Chrome, this constantly refreshes the page. I cannot find where this can be disabled.

With newest platform tools gives fastboot: error: Unable to get max-fetch-size. Device does not support fetch command. On both Pro1 and Pro1X

After a few days of trying to persevere I've sent an email detailing the issues and unfortunately had to go back to my cheap £100 Nokia for the time being. I will await the response.

I'm seeing log messages like these. There's about 122 of them since I booted the Pro1-X. 08-11 08:54:32.294 594 600 E android.system.suspend@1.0-service: Error opening kernel wakelock stats for: wakeup11: Permission denied 08-11 08:54:47.232 240 240 W kworker/u16:2: type=1400 audit(0.0:2513): avc: denied { kill } for capability=5 scontext=u:r:kernel:s0 tcontext=u:r:kernel:s0 tclass=capability permissive=0 08-11 08:54:47.440 594 594 W Binder:594_1: type=1400 audit(0.0:2514): avc: denied { read } for name="wakeup48" dev="sysfs" ino=57280 scontext=u:r:system_suspend:s0 tcontext=u:

Today's delivery attempt failed because the delivery person wanted to collect import VAT (130 €). Next attempt tomorrow. (FedEx did not announce the fact, let alone give me the option to pay online beforehand, as UPS did last time I received something through them... )

Well i thought i double posted a response to this, but now i only see the one i edited and removed everything. Anyway, I have two 5 GHz access points in the house, one is 25~30 feet away, mounted on the ceiling, within perfect, unobstructed line-of-sight. And the signal strength is "Fair" to "Poor". No 2.4Ghz access points in the house.

@EskeRahn No joy (using the LOS 18 boot image you posted), although some things changed. When aicp-s was flashing it said only 2 parts, not 3 and did not announce itself as Android 11 at the end of the screen dump. However after flashing mtg12 and rebooting, I got the error screen again after the 7 boot loops. I tried taking the offer to factory reset (I did before flashing aicp-s, but what they hey at this point), but that just sent me to the bootloader where picking "Reboot to Revovery" just returned me to the bootloader, so somehow recovery wiped itself out on the factory reset. 😄

The Pro1-X has a single-stage camera shutter button. The website will be updated accordingly...