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.

You can try to uninstall the Snapdragon Camera app via ADB. This only uninstalls the app for the user, so it's not really gone and does not require root. This will prevent anything from launching when pressing the camera button, but the executable responsible for launching it is still active... so question is if listening to camera button events work or that launcher is hogging the key too much still. Tasker for example doesn't have its Camera Button event triggered, even with Snapdragon Camera out of the picture.

Maybe this code sample from here can be modified to a more general list, of course of different type and the firstOrNull should obviously be replaced with some loop private lateinit var sensorManager: SensorManager private var mSensor: Sensor? = null ... sensorManager = getSystemService(Context.SENSOR_SERVICE) as SensorManager if (sensorManager.getDefaultSensor(Sensor.TYPE_GRAVITY) != null) { val gravSensors: List<Sensor> = sensorManager.getSensorList(Sensor.TYPE_GRAVITY) // Use the version 3 gravity sensor. mSensor = gravSensors.firstOrNull { it.vendor.contains("Googl

The list in Quicom's "Device Info" seems longer (50 sensors), But it does not seem to appear there either. It could be the one five from the bottom with the long name "BU52061NVX ROHM_HALL_EFFECT", but it does not show the readout from the sensor. So hard to say if that is the one See this

like i said, check WaveUp's source code, while its primary function is to wake the phone by waving over the sensor it also has 'pocket mode' which turns on the screen when taking the phone out of a pocket (or opening a case)... which works when the screen is off and locked. it also has the function to lock the screen when the sensor is covered, but that requires special permissions. your app does this too, what permissions does that require?

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?

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.

Here are some screenshots of the touch reticle I've slid the fingers from the start all the way to the top bezel, they all stop in the same height both in landscape and in portrait mode

Did anyone here update Riru EdXposed to "0.4.6.1 (4510) SandHook" already? The thought of updating and getting stuck in a boot halt terrifies me ... but my OCD wants to klick the download button in Magisk manager 🙂

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

Just a random case for another new device, and this is even just an evolution over what they already got.... https://www.dpreview.com/news/4862735124/some-galaxy-s20-ultra-smartphone-reviewers-report-multiple-camera-issues

I haven't noticed any performance issues with my Pro1 in daily life. Also, when I ran some benchmarks Pro1 was performing like it should. For reference OnePlus 5T (Snapdragon 835) got these results according to PhonesData GeekBench 5 Single Core 383 GeekBench 5 Multi-Core 1655 Antutu 8 score 263919

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

The keyboard driver only polls when at least one key is pressed. When no keys are pressed, it uses interrupts. So there should be little concern for the CPU usage. I could even get rid of the option and always use 20ms. I just preferred the longer delay because I could not detect any keyboard lag at all with 40ms. Also note that there is still one more optimization that I would like to make for the keyboard, which is a hybrid interrupt/poll mode. In this mode, the driver would only poll on the rows that have keys pressed (it is currently all-or-nothing). This would reduce the work

If your continuing this might be nice to have a 3D printed case thread so people can find/share info on doing this.

Indeed, economic downturn is worrying. I'm prety sure Fxtec is lean enough to survive it but if some of the suppliers and parterns are going bust it could geopardize that product.

What I really enjoy is reading with the keyboard open and the book forced to portrait. This might only be a pleasure for right-handers, but wrapping my left hand around the keyboard gives me a very firm, comfortable grip while my right index finger turns pages, or my right hand grabs my coffee. My hand doesn't get tired holding it this way. It's perfect for reading.

Eske is super chill with people with different opinions, but he does not like discussions based on personal opinion instead of data and science. So he is just saying that the mechanism is rock solid once mastered. You could of course argue that it would be wiser to have one that instantly can be used but then the tricycle comparison is pretty on spot. So there is no reason to feel belittled.

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

These are all valid complaints yet most of them are not an issue for me anymore after getting used to them. I have not much problems handling the phone carefully to not press the side buttons and screen edges, am used to huge phones already, and I simply like the hinge mechanism as is. The issue with cheeks pressing the screen during calls is supposed to be prevented by the proximity sensor turning off the screen in calls, and at least for me it seems to try but I have to admit it has happened to me once or twice, but it did so for phones before that too, maybe it can be tweaked in software bu

This is a massive improvement, thanks for the hint!

In addition to that, DragonBox has a nice "Hints and fixes" page for Pro1. https://www.dragonbox.de/index.php?fc=module&module=ybc_blog&controller=blog&id_lang=1&id_post=9 I am using Edge Null with "Detect Edge Swipes" activated. I would add Google Camera to the list also (either BSG or PocoPhone F1 port). @fxyo1 If you want to sell the broken unit I would like to have it for spare parts.

Dude, I understand completely! I've had some moments the second week, I'm pretty sure if my screen cracked during my darkest hour I also would have broken it in at least half. You are not alone. That being said, I am so thankful for a physical keyboard, I would probably still buy a new one.

Honestly, i'm tempted to give my device off to some engineer to design a case in CAD which can then be 3D printed at will using a nice rubbery material. A proper fitting case is a custom made solution.