Leaderboard

Hello. As I mentioned in some other topic, I received my Pro1X 2 days ago. It looks great, keyboard is even better than in original Pro1 - layout much closer to normal, much more tactile. As with every qwerty phone I started from rooting, and tweaking keyboard to Polish language (by the way, if there are any Poles here, I'd like to share my keyboard tweak as a Magisk module - it really makes a difference!). Unfortunately I encountered a problem with bottom (right) loudspeaker. Sound is intermittent, sometimes popping, sometimes sounds like reversed phase. It helped for a while w

Basically, I have 'modified' finqwerty (added a new layout which is my own keymap). That makes possible to switch keymaps using system default solution. I don't know about Pro1X's actual keyboard driver but theoretically it also supports loading specific keymaps.

Just an update, if you make SURE to back up your persist partition first, flashing the persist.img from the stock firmware WILL return screen rotation and the keyboard backlight.

This is a known issue that was fixed in a later update, that you should get by OTA soon, or through the testing program when they open it to all bravehearted users.

This one (at least that is what I used).

You're right, they're two different things. Then again it might still be a specific problem of your phone; I've tested calls to both mobile and landline connections, calling as well as being called from the other phone, and no such issues came up in any way...

Heyyy it works. Thanks

Hello community, I got my Pro1X last Friday and so let's go. Used https://gitlab.com/ubports/porting/community-ports/android11/fxtec-pro1x/fxtec-pro1x and it's working fine for me too. What's the best place to speak about UT ? On Ubports there is no subforum for Pro1X and on XDA don't happen anything. I wanna dive into Ubuntu Touch with the Pro1X:-) Greetings from Germany

I've sent an e-mail to f(x)tec about this. Please don't send one too. I'll share the answer with you. I just had this chat on #lineageos IRC (LiberaChat) and I got this interaction Weren't we going to get LineageOS development for the PRO¹? What is going on? The LineageOS management doesn't even know about it. They are claiming it as unsupported! @Waxberry/@Casey , what's going on? Is there development happening outside the LineageOS team but the results not sent to LineageOS team yet? Extra: Doing some research things are not adding up... Can it be I wasn't

In my case it was definitely bad connection issue. If it was software, why would popping come only from one speaker, and why would it change on movement of USB cable plugged just by the speaker? But I'll definitely let you know if anything changes.

No, not really. LTE is considered 4G. HSDPA and HSUPA were considered 3.5G technology.

There's a driver because there's a need to manage the digital-to-analog converter and then manage the amplifier for the speakers. There's a chance they are using a driver that was designed for mono and they are using for stereo and it's failing at some points. If it's software, they can fix with OTA! Edit: Appears like it's a hardware issue. See:

The question has also turned up on XDA today, with links to the necessary boot.img file, which indeed seems to relate to the file @Casey Cheung linked to here. The rest I'd suppose should be the same as for the Pro¹... (Personally, I guess I'll wait with root until LineageOS becomes available. Unrooted stock Android on the Pro¹ X so far is a much better experience than I expected.)

The bottom portion here worked for me: https://gitlab.com/ubports/porting/community-ports/android11/fxtec-pro1x/fxtec-pro1x I even flashed all the files from the most recent build copy/pasting the codeblocks, though I do have issues with WiFi starting up not mentioned by anyone else.

I was able to install and use Ubuntu Touch on my Pro1-X after locating the fastboot images on their development server: Jobs · UBports / Porting / Community Ports / android11 / Fxtec Pro1-X / fxtec-pro1x · GitLab. Unzip artifacts.zip for the most recent build, which will have out/boot.img and out/userdata.img. To install: unzip artifacts.zip cd out fastboot flash boot_a boot.img fastboot set_active a fastboot flash userdata userdata.img fastboot set_active a fastboot continue So far it's pretty decent. My intended use for the Pro1-X is pocket computer, not primary phone, and I don't t

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

If they got it for the Pro1. Things have changed slightly for the Pro1X. The fingerprint-reader is new, and I believe they said the antennas are changed too. Obviously these could be backwards compatible.

@spam71 Thanks for the report! Reasons why some of us thought it would have to be software are discussed here. Seems the Pro¹ X screws are fastened tighter than the ones on the Pro¹. Had no problem with that part of disassembling my Pro¹ today—but then again, for me, neither the removal of the keyboard (exactly following the instructions regarding the heat gun), nor the prying apart of the two lower shell parts went without inflicting ugly cosmetic damage to the shell. Especially the latter step was only possible using violence and metal tweezers, no other tool could find purchase be

And another thing i learned, F(x)tec should be able to reprovision the devices with new keys. It seems to be a standard support issue. Afaiu, they can assign new keys as trusted source in the chain.

Just noticed. The file on google changed too. It used to be a .gz file and now it's a tar.gz with multiple files. Now I can find the boot.img and others I was looking for.

Prior to getting your ddrescue and restorecon tips, I tried taking the backed up image, delete all files, and then copy over the data from the stock persist image (hoping it would retain any hidden data but copy the stock sensor data). This produced a non booting system. I'll try out restorecon and ddrescue when I get back to my PC.

I got a hint from TheKit just now that it might be related to SELinux context. He advised me to try restorecon on the sensor folder in a rooted adb environment. https://www.thegeekstuff.com/2017/05/restorecon-examples/ I have no means to try for the next hours so maybe someone else is quicker.

Try using ddrescue to copy them. See if it works that way.

I tried a couple of things: Copying each individual directory from the backup into the stock persist partition using `cp -a` Copying all of the directories apart from the `sensors` directory into the stock persist partition All of these gave me a working phone, with rotate and keyboard backlight, but no device attestation. `cp -a` is meant for archival backups and copies all standard properties and permissions to the destination I'm beginning to think these device keys are either embedded in ext4 metadata not supported by standard tools, or hidden in unused data on th

Note that mine is not a retail unit, so could have been improved since 🙂

If you run the Camera2 app, it reports for both the Pro1 and Pro1X that it ought to be able to do raw. The biggest difference reported seems to be on video where the Pro1 apart from the QFHD (or 3840x2160) as the highest, it also reports it can do 4000x3000 - does not sound very likely though... So maybe the information reported through the Camera 2 API is simply incorrect.... And that can obviously confuse an app trying to use it.

That would be true if Android phones would be obliged to come with a light sensor designed and specified to report correct Lux values, but that is not the case. The app is taking readings from a sensor that never was designed for the purpose, just guessing what Lux value those readings might correspond to. If nothing reliable comes out of that, it's not the fault of the phone.

It's Gorilla glass, and I doubt there's any phone on the market where it's easier to swap screens, provided you get the official replacement unit (which practically is the whole top part of the phone, replacement involves just five screws and a ribbon cable). As a cheaper option there also is the actual display available from sources like Aliexpress which is also not too difficult to replace, but involves gluing which carries the danger of a less than perfect result. Right, but there are other issues which may arise with protectors, and physically breaking isn't what you need to protec

I have a Note 10 that is my primary phone and has never needed a screen protector, but I don't know what kind of glass is in the Pro1X, and I am positive that breaking the screen would be a much more difficult problem than with the Note 10. Regarding sensitivity and touch screen issues, that (and also color and glare problems) are solvable with some UV-curing adhesive, which I have since added to my Pro1X but had not yet done so when I took those pictures. Anyway, with effort and transparent adhesive, a tempered glass screen protector impedes neither the touch sensitivity nor the vis

Sounds likely when modifying inside the volume. Copying the whole image seems to work. Just tried with 108GB userdata, via recovery and adb, and it worked just fine. Updated this.

Agreed. This is not a manufacturing problem. I would intuitively say this is a bug in 1 line of code in the DSP. Some mundane detail, like a decimal point. 😆

Import VAT (129.16 € including administration fees) was 22.4% of the perk's original price for me, $679 which did equal 576 € in Oct 2020. Excluding administration fees (111.31 €), it's 19.3%, close enough to Germany's import VAT rate of 19%. I think I missed the 'super early bird' offer only by a few days back then 😉 but I found and find $679 to still have been an excellent price for what it is. By the way, without root, for the time being, and therefore without the ability to use the 'Advanced Charging Controller' daemon and app (ACC/AccA), I've reactivated my 'Chargie' devices to

Split works just fine here, both portrait and landscape. With the android limitation of only offering one 50:50 split in landscape, and 30:70, 50:50, 70:30 in portrait

I get wildly flashing triangle/circle/square icons when I tap and hold the square icon which is strange, but I get split screen mode by a short tap on the square icon, a short tap on the size-reduced app's icon, and then there's the split screen option. (I keep forgetting how this works as well, with so many changes in past Android versions...)

Screen protectors reduce the likelihood of a shattered display whether or not they are tempered glass, and not by absorbing the impact of a drop. Scratching your screen is scoring the glass, making it significantly more fragile.

Thanks for the link and guide, added this to thread here: https://community.fxtec.com/topic/3207-various-roms-available-to-the-pro1pro1x-available-for-download-links/

Cosmo might have similar problems getting their devices from China to the rest of the world. This is certainly not a problem limited to FxTec and Pro1X for the time being. I know from dialogue with FxTec that the Pro1X I perked for is in Batch 1, and is long delivered from FxTec and they can see that it has been 'processed', but yet it hangs in the shipping so I have not even got a shipping info mail yet.... I guess Expansys/Fxtec awaits enough parcel for Denmark to actually send it? 🤬

Appreciate the info on speaker issues. I don't think our sound output issue is the same issue: It only happens on calls, and the sound output cuts out completely when we're speaking. Also it happens with a wired headset as well. So my guess is that it has more to do with call audio processing than with the hardware or low-level audio drivers. Is anyone having problems with the internal microphone like I described? Thanks!

Welp. I just went through the whole reflash stock procedure and restored my oldest persist backup, and attestation no longer works. It worked yesterday, which was AFTER I backed up that persist partition. Guess I'm sh*t out of luck now... I'm not sure when the unmodified backups stopped working, I'm 90% sure I got back working attestation after flashing the backup over the stock image at least once. But I think it does invalidate my findings above, perhaps one of those operations would work. Or perhaps one of them nuked my keys. Hard to know at this point , but I guess I can't do any test

Yes, right/bottom speaker on mine also cuts in and out. I have not tested pressing on the case. My assumption is that this is a firmware issue. The cutting out seems to occur when the audio exceeds a certain level. I have applied no scientific method to confirm this, yet.

First of I can confirm that the bug is not ALWAYS there - I have no idea what triggers it.... Yes I agree, Mono would do just fine for me too. Turning down the volume sort of do that IF the source is Mono. But if the source is Stereo we get only one channel so not a too good workaround. The big question is what is going on, and how they can fix it.... A wild guess is that it could be related to some circuitry intended to avoid feedback-looping between mic and speaker during calls. Obviously it should not be active during ordinary playback. Just my wild guess though.....