Leaderboard

Fx Service is an Android application notably enabling Pro1 smart case support. It also provides various solutions to common Pro1 problems or simply new features including: Smart case support: configurable lock and wake functionalities. Screen filter overlay to lower display brightness beyond system settings. Configurable vibration upon keyboard key action. Alternative auto-rotate solution to bypass system auto-rotate which tends to get stuck. Filter out unwanted system key input. Feel free to post here to discuss bugs and feature requests.

F(x)tec Team: I remain hopeful that the Pro1 will make it. It is very important to me that it does, especially with the demise of the Blackberry QWERTY cellphone keyboards that will occur this coming October 2020. I have learned that if you are a visionary, it is often a lonely place. It is a curse when you are the only one in the room that sees what you envision. In my case, my friends and co-workers laughed at me in 1989 when I created an electronic health record database software system (today known as Ezpro - https://ezprosystem.com/?page_id=74, https://ezprosystem.com/?page_id=6

Modem crashes are always fatal, eg. reboot AFAIK. And the modem software is completely closed source. The OEM may have the source, I don't know. If they do, I might be able to build a kernel that crashes to ramdump mode. This would allow you to pull a copy of the device state at the time of the crash and send it to the OEM for analysis.

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).

Well, I did a quick test file yesterday as well, might give printing it a try this evening:)

@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

Already gone. Damn that went so fast. Whoever bought the phone got a smoking deal... Sorry the phone didn't work out for you OP.

Very interesting, thanks! I tag @Waxberry to make sure he sees this, so It can be forwarded to the right people. 🙂 Especially interesting that they even got a workaround..

There it is: Fx Service. For better and easier Pro1 integration with smart case cover.

I googled a bit and I think that I might have found something to resolve this issue. Some Sony Xperia devices (XZ1 Compact and XZ Premium) with same chipset (SD835, MSM8998) have also suffered from random reboots. There were very similar symptoms. "I'll add that it's still ongoing and I've noticed it happens in the same physical place with some consistency. I take a train for my daily commute and it usually happens in the area between two particular stations. Perhaps relevant is that this area has always had a bad radio signal." "I was able to reproduce it consistently during

I forced my phone to use only WCDMA and traveled that 70km but I was not able to produce random reboot. When I was driving back I selected GSM/WCDMA preferred but no reboot. I checked that my phone was connected to both B1 and B8 bands during the trip. This was a trip that I had not drove before so I don't know if there would be reboot with stock settings anyway. I started to think about a new scenario that maybe WiFi 2.4G issue is related to assumed network issue. I have 2.4G WiFi at home but I haven't faced reboots at home. Maybe there is a really specific usage scenario where both W

Title, selling my Pro 1. Took it out of the box and couldn't get it to work on my carrier, back in the box it went. Never spent a second in a pocket or on a table, still has the IMEI sticker on the back. Selling at a loss just to get some of my cash back. Asking $550. https://www.ebay.com/itm/223934674653

Yeah that is probably a good idea, I'll update that. When I have something that prints ok I will post all files. The entire thing did not fit in my printer, but I printed the top part for testing and the camera hole is correct (camera position is actually visible in scan), but other holes need some adjustment.

This is great!! One thing that i missed from my old phone was smart cover function. I tried android program that was doing same with just a proximity sensor but i didn't like that as it shut down the screen when ever i placed my hand even a little bit over the phone. Getting your program to work was bit difficult at first because i didn'n know that you had to allow it to work from accessibility menu. Also getting the magnet to line up perfectly with the hall sensor needed a few tries.

Similar to pretty much any other Android phone, you do a build by pulling binaries off the device. I don't know if FxTec has provided any "official" kernel sources but this repo has the full OEM history, which is a step above your typical "here's a tarball" that most every other OEM does: https://github.com/tdm/android_kernel_idealte_msm8998/commits/oem-history

I believe this is the OEM: http://www.idealte.com/ check posts from tdm he has mentioned.

Tactus Technology actually showed this kind of implementation few years ago. There were "bubbles" on the touch screen surface. I don't know what happened to that technology since I haven't seen that later. Imagine that technology with Galaxy Fold. However, I would still pick up Pro1 anytime because of slider.

This energy spike thing could seem plausible. I also live in a large town in the UK which has good signal coverage, but my specific house has none. It could be the increase of transmit power to compensate for the loss of cellular signal combined with the reconnection of the device to my home wifi at the same time that causes this - maybe due to mail syncing at the same time, but I can't explain why 5Ghz doesn't seem to do the same. It used to be even when I popped outside and the phone got a sniff of a cellular signal it would reboot too - didn't even have to arrive home just walk out ont

Don't think so. In my case I was never connected to WiFi, during the reboot. The theory with energy spike causing reboot seems more plausible, I have dual-sim with multiple mail and messenger accounts always syncing.

It's wild how different the experiences with their customer service are. Due to financial issues I had to cancel my order and ask for a refund yesterday (really not an easy decision) and just 9hrs later I got an answer and an email confirming my refund. After reading what other customers had to deal with I was expecting the worst but it seems I got extremely lucky...

oops, you are right, tdm, i should have specified who owns root here, sorry about that ! i meant root on the host (and i did not yet need to be root on the phone). you are most probably right regarding the udev rules and i googled similar notes elsewhere on the web. interestingly jmtpf worked over the last few worked for the "PTP"-mode - but as i started to play also with the "File transfer" mode it broke my previous access to the phone photo data. so neither access worked for me as regular user as of today but for root both worked just fine. anyway, i assume the number will be th

Thank you, yeah I figured it is still technically a second hand device since I opened the box so I wanted to make sure the value is there for someone to pick it up. The money's going to go back in my rainy day fund to try again in a couple of months, once maybe F(x) opens up some more possibilities with other carriers.

Too bad you can not get it working. Some US carriers require some trickery. Have you seen this thread?

i am not sure if i mentioned it already in this forum (my search before didn't help) but i experienced some two weeks ago the very same problem as alexmarzulli did in that the upper 16% or so of the screen became unresponsive to touch, out of the blue, for no clear reason. i used the built-in factory test mode which revealed that the area of the last two upper rows with red circles are indeed unresponsive to touch as i can't erase them like the others lower down : i contacted Fxtec and they promised me a replacement screen in the coming weeks - see my recent post in this forum. ob

I yesterday got the old SCH-U750 aka Zeal aka Alias 2. Very interesting. There are little movement of each key, but to my surprise it looks like the e-ink move with the key, so it is not just a transparent mat on top of a common e-ink display, But it looks like it is 42 individual matrix e-ink displays! And a warning to @abielins: The below is AFTER a thorough cleaning attempt. You do NOT want to know how it looked before. I believe it might have been an entire eco-system....

I will also try it in the moment, I'm making image of my own disk. That's how game runs on S8+ with this same SoC.

I just flashed test8 build, coming from stock. Does anybody else still have problems with calls? I saw on Git, the issue seems to be fixed. After a fresh reboot I called my Pro1 from my other phone and apparently the Pro1's mic didn't work. After I turned on speakers in the call it worked, even after turning speakers off again. That seems to be working now. I am not able to hear the other person though, sound is just muted. Works though, if I turn speakers on -> stops working if I turn them off again. Maybe my "phone call" speaker is just broken? Is there a way to check that

Have you tried opencamera? If so, any reason why FV5 is better? I only ask because opencamera seems to work well for me, but I'm not a very good judge of camera apps. I tried a few gcam ports but they didnt work with camera button which for me is a showstopper. The only other camera app that worked right with camera button is the default lineageos camera app.

Since both devices are Linux, I need to clarify... you need to be root on the host or on the phone? If it's on the host, which I assume since there isn't any official way to become root on stock, it is likely because your udev rules are not marking the specific vid:pid used by the pro1 as owned by the correct group. I can tell you that the pro1 has a very minimal set of changes from the qcom bsp so it's probably using the default qcom USB compositions. Many device vendors customize these.

So sad. Hope to see you back.

And now, with test8, the stuff I'd done in custom keymaps is built in as an option, I don't even need to use the custom keymap I made: In the future I hope/imagine there may be an option there to use the the right slant arrow as slash/questionmark (which I will use) or maybe even right shift or right control incase someone needs one of those keys for something, or prefers an easier to reach right shift. Can also see he's working on a switch for qwertz, rumour has it the qwertz fn-keymap doesn't match print completely, but I suspect it will be soon. (And with sym key as

A cheaper (and I think still usable) alternative would be a touchscreen (e-ink ot not) and a real 3d screen protector with the grid between the virtual keys: you can feel the position of the keys and get the feedback through vibration. One could try this with the LG G8X (If there is enough space between the screen for a "relief rubber mat").

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

Though there is a common rubber mat over everything, and clicking VERY close to a border with a nail, can click the neighbouring key also. Tried to lift up the separator grid with a nail and hold it with a toothpick: So optical illusion that the e-ink moves with the key...

OK STEP BY STEP COMING UP... 1. Ensure keyboard mapping is set to no keyboard mapping 2. Click Advanced keyboard settings 3. Click Key repeating 4. Currently I have selected Slight key delay (recommended) 5. Open your keyboard 6. Go to your web browser and select the address bar, so that the flashing text entry cursor is flashing. 7. A little keyboard icon will appear at the top right of your screen in landscape. (unfortunately unscreenshotable.) 8. Click on the icon and Select Keyboard helper rather than Gboard. 9. You will notice now when you clo

Look at this link. the key is making sure it is ON External Keyboard Helper... While not rooted. Little keyboard icon comes up. I have just turned the on screen keyboard OFF completely. I wanna type, use keyboard, I wanna flick use the phone closed. Trust me once corona virus blows over they will get more proactive in the next OTA update. I bought this phone April 2019, delivered Jan 2020... I am patient my phone is working perfectly. The other option was F(x)tec could have waited another 6 months to a year, to Launch and make it perfect. 2012 is how long I have really been wa

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

There once was a man from Ohio While in search for a phone he went psycho He then found a brand new one When he thought that there were none But he did not at first know the logo. Its full keyboard laid out so neatly The potential for typing so clearly F(x)tec they were called They were new from abroad "I must have it!" he exclaimed emphatically. Pictures and videos began to emerge Diligently the man did his research One day his said "Screw it" His budget, he blew it For this phone he decided to splurge.

Works with current sfos just fine....

test5 build is up. I've added a changelog section to my lineage page so you can see what is new. Most all the changes from test4 are keyboard related. Please note that in addition to the listed changes: The vendor blobs are unchanged from test4. I got the updated vendor image from @bmccrary but haven't had time to pull in the updated files yet. a2dp is still not working. I looked at it briefly but still can't figure it out. I don't think it's super high priority right now, so I'm not blocking test releases on it. qwertz keyboard users must still set their

I've been actually developing on the Pro¹ today, which is a bit of a strange experience. I'm using ConnectBot to ssh into my build box, enabling adb over network, and connecting back to the device to push files and etc. Then I run "adb reboot" and *poof* the terminal goes away and the device reboots. Anyway... so I've been pulling in patches from @Sean McCreary and it looks like he's got the keyboard backlight fixed and the wake on any key fixed. So I'll probably make another build with those changes tomorrow. PS. Please forgive formatting errors, this forum does not

Let's see, there are a number of games I play on the Pro1 Where Is the Setting Game How Do I Make This Stop Search Game What Does This Do Challenge The Volume Game Puzzle The Notification Light Game Holding The Pro Russian Roulette Can You Hear Me Challenge I find new games to play EVERY time I use it. It's such fun :D

I tried, and can confirm my deduction from what people told me they heard. Held to the ear I hear zero problems. But hands free there indeed ARE issues. To my experiments it seems like a matter of a minimum LEVEL of the incoming sound to the microphone. If I speak clearly like I would naturally do outdoors or to a meeting it gets through just fine, but if I lower my voice (including mumbling), it is cut away, though not immediately, but sort of faded out. A guess could be that it is the algorithm that is meant to filter out background noise that needs to have its bottom level r

I experience distorted sound from ear speaker due to high volume which can't be lowered any further. I bet it will get better when the high volume bug is sorted.

Hmm, I guess I better do some experiments... I think calling another phone with a headset and muted mic, should make it possible to see erhm hear if there is a clear pattern in what is going on. E.g weakening the signal by putting the phone in a partly closed microwave should force it to increase sending power, and that could make it worse if caused by interference.

Secret deleted tweets!

Soon available in the store, a calendar with all the inpirational tweets :).

I think only those also on the Discord fully understand this last one xD.