Leaderboard

@Khalid I'll refer you to a post that I made a bit over a week ago: https://community.fxtec.com/topic/2809-after-a-solid-month-i-give-up-i-need-to-vent/?do=findComment&comment=45253 The tldr of it is that yes, FxTec nerfed the software and as a result they don't even really have control over the OTA contents or timing. Big mistake? Absolutely. End of the world? Not even close. Software will improve over time and there are alternative ROMs to choose from. Lineage, in particular, is now quite usable except for the notification light (which will be fixed in short

@Khalid I understand and agree with many of your feelings here. It's frustrating, especially after such a long wait, to have so many things get in the way of usability. I hope it gets better for you. But, if not, FWIW you can probably sell with ease (maybe for profit, see thread on used prices I've been watching), these clackers are in high demand right now. I do still struggle with my own Pro1 (like you), but it's actually really common for quality control to be on par with what you see here. In fact, I'm impressed FxTec has created something this stable and reliable. Here are some issue

i had to ask Fxtec recently to replace my screen (i suggested to pay for it) because the upper 16% became unresponsive to touch after which they promised to send me for free a replacement screen & installation video within in a few weeks. i was quite happy with their response and added to my response letter to Fxtex the following few lines : i have my own experience (a little bit) what it means to start a company : it's incredibly and painfully difficult and one also needs a (metric) ton of unpredictable luck for that - all my kudos to Fxtec !

I can and would recommend this to people who want this phone and are willing to put in a bit of effort to customise it their way. Of course it should be great out of the box, but it isn't and if you really want this keyboard phone from this start-up company, you're going to need to reset your expectations and budge a little more than you would usually have to for any of the larger companies. Still I think one of the few phones out there that justifies the price tag.

Isn't that the norm? I mean... All this secrecy.... [/sarcasm] The same way other companies lie? Are you sure the factory didn't just do all of them in one go although the deliveries were slower? Are you sure the WHOLE factory is dedicated for the PRO¹? Do you even know how these contracts work? F(x)tec pays by the phone, not time. If F(x)tec suffers from the virus, it is and will be because the founders need money to live their lives. Other than that, I believe there won't be more losses. This being a niche produ

CPU Throttling Test and GFXBench (use Manhattan Battery Test for long term test) are good apps for thermal test. I will post my results shortly.

...Stop eating whatever you are eating immediately... 🤣

It's definitely the Snapdragon 835 CPU. The sound issue is a bug with the system forcing a power saving rule as investigated below. This is at the top of our list for the coming update/s.

@alexmarzulli Your screen might be broken but you can try to fix it with Piezo igniter (you can dissamply an igniter from a lighter). I have successfully fixed couple LCD screens with this method. I don't know if it works with AMOLED screens but I think that you don't have anything to lose.

Tip, if you have Magisk installed and you keep getting errors on launch make sure Android didn't install it to your external SD card. It needs to be installed on internal storage or else it will crash!

First, I'll say that if you find these points of pain too much for you, you of course should move to whatever makes you happier. However, I take issue with referring to others as apologists because we have found work arounds that make us happy with this phone. Personally, I am very happy with this phone and consider it the best phone I have ever used. New people who read these threads need to understand that for every person who says they are fed up, there are many more who are having a very different experience. In the future, I suggest you don't set expectations so high for a new tech

I got a rough 3d scan of it as a starting point for making a case. Here is the obj file if anyone is interested: https://www.dropbox.com/sh/uee2exvq1k9l0g8/AADEZnXLLar2HUjdHvcaj3O1a?dl=0 It got some artifacts due to the fact that I had to cover it in tape for the scan to work (can't scan non-reflective black surfaces or surfaces with specular reflections).

I have updated and it's working without any issue. 🙂

I tried a few things today, but no luck. HOWEVER, I did find something interesting and it also explains why I thought it was fixed. If there is crackling audio, simply plug in or unplug the usb, then it stops until the app shutdowns or phone goes to sleep again. I'm not sure whether or not it because another sound is being played when that occurs or if something else is somehow being triggered. I grabbed some adb logs of it occurring but haven't narrowed it down to anything yet.

@tdm , I just installed test8 and I am BLOWN away with how much progress you've done with it. And everyone else: Has anyone noticed some oddities with the front facing camera in Google Duo? I get a lime green appearance to my face. This also appears in other apps, but not in the default camera app.

@Khalid I know you wanted something that works out of the box, but test8 of the Lineage build is out of this world good. The margin settings eliminate the accidental touches and TDM's work on the keyboard driver has completely changed how it operates.

These are things I usually do :D. Have not regretted making an exception for the Pro1 though.

I highly recommend this phone, but not to everyone... Generally I would not recommend anyone to buy a brand new device if they want an errorfree experience out of the box (any brand) The Pro1 is a niche product with a limited audience. AND like most new devices it comes with a bunch of more or less annoying software-bugs. And sure bugs ought not to be there, but in the real world they are, the important thing is that things get fixed, but like everything else in China these are delayed by new year and virus... You should try the LineageOS (see the long thread) where quite a lot of the

I read about some thoughts about making a 3D printed case in another thread. I have thought about it as well, so instead off bringing that thread off topic (and making stuff hard to find) lets have a new thread for 3d printed case designs. A first question. Does anyone have a good 3D model of the Pro1?

Hello Imagine having waited for a really long time to get your phone adn, suddenly, the touch screen digitzer stops working. That's exactly what happened to me this morning. As soon as I woke up i could not interact with the quick toggles in the notification area, or swipe away some of the notifications. I managed to move around by using the arrow keys and with some effort, i got into developer settings and activated the touch screen reticle. The responsiveness stops at around the volume down button going up. I thought this was a sotware issue, rebooted a couple of times, nothing.

Here are my results for comparison: CPU: GPU: These results are quite normal so the issue is not thermal throttling. I think that it has to be software thing. Reference (Honor 20 Pro and Xiaomi Redmi Note 8 Pro)

I just tried the first on a S8- (exynos, so not the same) and the Pro1. And even throttled it is higher than my S8- before throttling. (The Pro1 was disturbed by a call I did not answer during the test, the red line)

@FlyingAntero I will give it a try as soon as I get home, my coworker only has a flint and wheel lighter on hand I don't have too much hope because the dead area is very extended, but still, if it works even temporarily at least I can continue using the phone properly until they replace it under warranty

Sorry to hark back so far, but I had this last night. My pro1 always crashes when I go home. I had both the 2.4G andf 5G wifi hotspots saved, and I guess it saw the 2.4 one first. I removed the 5G one from my saved networks, the phone crashed and then was stuck in an infinate reboot loop until I managed to turn off wifi just after it booted. Removing the 2.4G one and re-adding the 5G one - it hasn't crashed since I've done that.

Just a note, if you're installing Magisk on LIneage, you don't need to go to all this effort. Just use lineageos recovery to adb sideload it.

I agree with this but it was told to us before purchasing that the screen will be curved. These things are fixed in Lineage and SailFish, and should be fixed in the next OTA for stock. I'd recommend giving Lineage a try. For stock I can provide a fix in the form of a modified kernel but WARNING this requires a factory reset and breaks OTA (to get back on normal stock you need another factory reset): https://matland.be/pro1/kernel.zip See the readme.txt in the zip for install instructions. I believe the reason we don't have OTA update to fix these things yet is due to chaos related

You can't possibly preorder a first smartphone from an unknown start up and expect to get a bug free experience. If you did then you obviously have little understanding of the technology and complexity behind such a product. My tips to you to avoid such frustration in the future: Do not preorder any product, ever. Buy last year products thus making sure most bugs have been resolved. Stick to main stream, high volume smartphone. Stick to well known brands.

I know what the proximity sensor is ... BUT they just MIGHT be exposing these two Hall sensors as "TYPE_PROXIMITY" (Note: TYPE), The reason to believe so is the binary type output we see in the FactoryKit test-program. And if you are looking for it as a TYPE_MAGNETIC_FIELD sensor, no wonder you can not find it.

The same author also have a "Transparent CPU Monitor", that can show CPU and GPU as a transparent layer. That might be helpful in debugging?

Can you the trigger from the sensor when The case is opened? Or isn't it working when screen is off?

It is a case designed for P20 Pro, random one I bought at a mobile phone shop. @EskeRahn has a great link to his website, with many case experiments and solutions.

Well though you might not care on the battery stamina, I assume you are interested in the battery life - even if the device are not glued together. Heating the device too much kills the battery. (That is the exact reason why we -as you wisely do- should avoid fast charging in normal daily usage, and only use it when we are in a hurry)

Well if you quick-charge it you certainly get it extensively heated, so if you get a low FPS rate then, but a high rate when it is cold, that should give a pattern. You could even try to operate it on something cold, and see if that helps it. If it does, your intuition on throttling is right. Be careful not to take something TOO cold, we do not want risking condensation of water vapour from the air inside the device.

Does the screen behave the same in landscape orientation?

By far the best image quality for photos and video. (That I have tried) Video and Photo are separate Apps. Opens and switches seamlessly between the two when going from video to photo and visa-versa. Also has handy Camera Info in settings: PHOTOS Camera FV-5 Lite (FREE) https://play.google.com/store/apps/details?id=com.flavionet.android.camera.lite Camera FV-5 PRO https://play.google.com/store/apps/details?id=com.flavionet.android.camera.pro VIDEO Cinema FV-5 Lite (FREE) https://play.google.com/store/apps/details?id=com.flavionet.android

All my tests are from app shortcuts.

Well good that you reported it, and the more details the better. I'm not in anyway saying that they by optimisation wenot could extra out of the hardware. But I think they are more than busy with fixing bugs & malfunctions, so the easier we can make it for them to narrow down where there is an optimisation needed, the more likely it is to be implemented. It could be as simple as some code left in a debug mode somewhere, that uses/wastes time on logging, or it could be a complex thing needed. And worst case it is a limitation with the screen hardware/interface. So the more it

Those mushrooms clearly did not do you any good... 🤢 But on a more serious note, I tried to take an extreme HDR-image with both LOS and stock, and in stock I got the below (well here a cropped and reduced version of it). Note the lime-green halo on the flames.

I believe that this step can be automatised via Keyboard/Button Mapper. Just record a trigger when open or close the keyboard and use Keyboard Switch Assistant to change virtual keyboard.

Just got this https://www.amazon.co.uk/gp/product/B07RWGCG9S/ref=ppx_yo_dt_b_asin_title_o01_s00?ie=UTF8&psc=1 worked fine no bubbles see how it goes.

I think it is much a user-dependant thing. When opened I'm yet to experience accidental touches clicking the numbers. But it requires more care opening. Personally I ONLY have problems with the edges when it is closed. Not when opened. Others have huge problems clicking the numbers. I would say the thumb-width is what matters. So I would prefer a setting. But when you got one slider, would it be much work to copy and paste to four? Giving the user complete control of the two edges, opened and closed. You MIGHT even add a tick-box (default set) "Same margin", that links

Most definitely, I can do the same thing with my Droid 4. Not an issue. Also, I can very easily open my D4 with one hand (as I can with the Pro1). I never had any issues opening any of the Droids with one hand. I also never had any of the other issues mentioned above with sliders either. The only exception would be sometimes it will be in a pocket and begin to open, activating the touchscreen without me knowing it. However, it's very rare and happens, at best, 3 to 4 times/year. I like the angled screen, but really only use it while holding it, so I don't consider it a must have fea

Nothing of the sort! Just saying that YES it has a learning curve, and YES it is worth learning. And as many other things once learned, it is easy. Nothing more, nothing less.... I even offered suggestions on alternative (though somewhat odd) ways to open it with practically zero learning curve. I personally can not play a violin, but I do not blame the violin-design for that, and I find it quite silly if people do....

You are aware that none of the one you mention have a similar mechanism, right? They deliberately chose this superior mechanism (previously used in several Nokia-models), despite that it unfortunately do have a learning curve. You just haven't learned to master it yet. Usually beginners also get angry at their bicycle until they master it, but once we do, we can not imagine how it was ever difficult. You could compare the ones you list with tricycles that everyone can operate (almost) immediately, and the mechanism on the Pro1 with a bicycle.

And some switch back from two to three when they get old... 😂 Would it be pushing it (excuse the pun) seeing a plain keyboard slider as a handicap friendly version of a real keyboard device like the Pro1? 😇😇

Missing keypresses might be due to a bug, where you can't press the next key before the last key is released. That should be fixed in one of the new firmware updates. For the / and ? problem, clear your keyboard language selection so that it reads "Default". Then the button next to the left control key will get you / and ? The other 2 are known issues. Hopefully they will be fixed in a newer firmware.

Actually radically different. Using the FinQWERTY mapping for the qwertZ on a qwertY device remaps every key in the middle three rows (as well as others). The version I came up with leaves all of the keys to the right of (the printed) RFV diagonal alone; thus, function matches the key printing. This has two wonderful effects. First, it unshifts the left half of the keyboard, and by doing so, creates symmetry (meaning the standard J key and the newly remapped F key are exactly the same distance from their respective right and left edges (this is a huge plus for me as I can now pickup the ph

This is a massive improvement, thanks for the hint!

Sorry that the phone didn't work out for you. Certainly there are different ideas about what hardware looks and functions best. But I must admit the software is currently a weak spot. I'm going to respond to the software issues. Please keep in mind that I am not employed by FxTec, I'm just a developer who was given a device to get LineageOS running on it. Further, I'm not really a "keyboard phone" type, this is my first keyboard phone (but my wife used to love her Relay 4G, which is why I was the Cyanogen dev for that device for a while). I have gotten to know Chen and a few other

OP, your issues are real imo, but many will be fixed soon in software. And others worked around, but takes effort and patience. But ripping it in half? You coulda sold it. In fact you can probably still sell it, although now you wont get nearly as much as when it just had broken screen.