Leaderboard

I think there is a deeper worry beneath this: The fear of this being the last real slider keyboard phone, perhaps forever, and not unlikely for many many years. And If so, the newer the specs at launch, the less outdated it will be in say 10 years. Many of us are replacing really old phones with the Pro1.

As of my Pro1 again. Yesterday I put on a "BROTECT" screen protector bought at protectionfilms24.com and I cut another protector bought at bestskinsever.com to fit the back and sides. I feel it is more comfortable to use the phone now because I was afraid I will hurt the device somehow and now I feel it is somewhat protected. I hope some pre-cut full-body protectors will be available after a while, but I feel convenienced with end result. The cutout near camera lens and noise microphone is not perfect, but still I feel it is much better that way. My back panel has a metallic-co

Unfortunately, you are right. That is why I hope Pro1 will have success which will be enough for us to have Pro2, Pro3, etc later. ...but we cannot foresee the future and the last QWERTY phone before Pro1 was manufactured long long time ago. I had a gap of nearly one and a half year with Moto G6 after my N900 which was in use for years (with practically two phones) and basically its performance leaded me to switch. (Remember, 256 MB of RAM is almost nothing these days, however, the system itself still runs well on these resources.) I have used N900 from 2011 to 2018 anyway.

Hi Guys and @EskeRahn i have put cloths to my pro1 i.e put the case on. As per @EskeRahn command i got P20 pro case and it seems to fit pretty well as Eske suggested. I had to make a cut on the case for usb c port and for power button. looks all good. It can slide open pretty well, closing is ok too but sometimes its not properly seated as the case edges are there but then you just press it to sit properly. I hope it will not hurt the display in any form? Below are the pics

I finally got around to doing the steps listed in the OP and it worked flawlessly. I'm now rooted with Magisk. Thanks, @Craig

Oh, and just so everyone knows... This tool and the linked factory packages are meant to do a "normal" factory restore. It does not, by design, reset every single bit that the factory programs. For example, it will not reset the frp partition which contains the boot loader lock flag and the Android factory reset allowed flag. Nor will it reset the radio parameters. Etc. I wrote this tool and I have full access to the underlying capabilities of the programmer. If a normal factory reset does not work, I can generate packages to read and write every single bit on the flash

That's what I'm still wondering too. I still use the original MotoZ which has worse specs than the Pro1 and I have never had problems with the performance. I understand that for a phone in this price range people would expect newer hardware but in reality I don't feel that it will cause any usability problems for me in the next few years.

I have tried HDMI output, it also works well. I have tried two adapters: - This one works for screen sharing but no audio going through - This one is more than a HDMI output but audio also going through HDMI here, USB ports are working, I have also connected a power supply while a video was playing on Youtube and it could also charge the phone (but only with 5V, so no Quick Charge this way). However, LAN interface is currently not working (maybe appropriate kernel module is missing). (Currently it is a bit more expensive than it was earlier but it is also not a cheap device - I th

I agree. The situation is not seemed to be unfixable or really hard to be fixable. Sending back for guarantee is not a good decision. Maybe selling the device is or to find a service person who has more patience or skills to do the well-described steps. ...but doing this while somebody is trying to help and definitively not stuck somewhere is also not a good decision...

I'd like to expand on this a bit. If you screw up your device then you are responsible for fixing it. Returning the device to the retailer is bad for several reasons: (1) you screwed up and you are making someone else eat the cost of your mistake which is not cool. (2) the retailer has less incentive to stock the device (and any non-mainstream device generally) because they are seen as less reliable and thus less profitable. (3) the reputation of FxTec suffers. So resist the temptation to take the device back and claim that it "just stopped working". Not only is it un

Wait, what?!? What shop? Where you bought it? As in you returned it and are done with it for good, or is this just temporary? I hope it's temporary as @tdm was/is working diligently to get this corrected for you, and the solution might very well help everyone. @tdm I have been watching and reading this issue with interest, as always thanks for all your support!

Just a thought on how to make the wait less unbearable, while going through tens of posts in the production status thread is just too much for me. Post here IF, AND ONLY IF You've got anything concrete from FXtec, like: 1) The Pro1 - pictures or video links more than welcome :) 2) a tracking number that can be tracked online 3) a "stock assigned" email message @ moderators - please remove any posts from this thread that do not fall into either of the above three categories. If it's possible and appropriate, may be worth making this thread sticky too.

The typical installation method as described on XDA won't work yet on Pro1, because we don't have a fully working version of TWRP yet. But never fear, it's still easy, five simple steps and you will have the privileges you so rightfully deserve on your own device. 1. Install Magisk Manager App on Phone Download from: https://magiskmanager.com/downloading-magisk-manager or github. After download, install the apk, which will require you to allow the install from "unknown source". 2. Install Android Platform Tools on PC (adb & fastboot) Ubuntu (and presumably de

I have no shutter sound at all anyway, but I don't really need it. However, I miss some feedback of photo being taken. Not sound feedback but something like what I see on my Motorola G6. When I take a photo with my G6, the taken image blinks for a really short while - that is a proper way to have a visual feedback of the photo. That would also help of the behaviour of photo button - one can not really feel when it is fully pressed, but a blanking effect would help a lot. As of gallery thumbnail, I have found it works when I launch the application on touch screen, but never works

Well what I mean is to pay mind to whether the keypresses happen to get missed if two keys are somehow pressed at the same time (even possibly only happening with some combinations and not others), which I happened to do and it was a problem. I'm now running a patched kernel which fixes this. If they get missed when truely only pressing one key at a time it is different issue. HDR seemed to work for me after doing the delete data+cache. Perfect it isn't indeed, shutter sound and the gallery thumbnail depend on the way the app is launched for me, they work if i launch by clicking th

It does. However, as I don't use a case, it isn't a problem. In fact, I hadn't even noticed that-- it isn't by much and does not make a noticeable difference typing on a surface (which I don't do often). It has the advantage of giving me a little additional purchase while holding it and thumb typing ( right index finger wraps it). EDIT: Yeah, okay, so I failed to notice this was a thread about cases when I was looking at the magnetic USB posts. Lol. Sorry.

Interesting, All the round ones I tried were unsuited for the Pro1, being too large so it goes below the underside of the device.

I think we need a proper issue tracker really... With some luck that will come :). Can you check by typing slowly or such if this is related to the inability to register multiple keypresses simultaneously? If yes, this will be fixed soon, also i can provide a temporary fix if you do not mind a factory reset. If not then that is somewhat concerning. I had the same issue with the camera app, clearing its data and cache in application settings has resolved it somehow and now it works quite ok.

1. I disagree: they make writing easier. While I agree that the layout is anything but straightforward and sometimes I do not even know how to type a particular letter, most of the type it really is convienient. 2. Since I am not from the US I do not really care, but it does feel as if 4G support is not as good or stable as with my S8. 3. and 4. I prefer smaller phones in general. My all-time-favorite smartphone was the HP Veer. It was tiny, but did have an excellent keyboard. But the pro1 seems okay and while the keyboard might not be ideal, I can still type quite nicely using it (w

This is the link https://www.altronics.com.au/p/p1896-magnetic-usb-c-and-micro-b-charge-lead/ It looks like its the Australian made and unfortunately i cant find it on ebay. If you want i can send you one by post, i have more then 10 of them

Thanks Eske! Yeh my magnetic usb doesn't extends beyond case and stays inside the case. On little issue i have is that its bit hard with the case to reach the power button to turn display on/off. have you found a way to turn on display by touching it or say pressing the home button?

Looks nice. You should consider to add a small hole (or extend the large one) on the back, for the secondary microphone. And also to punch a hole for the notification LED. The one you used seems slightly better for use with magnetic USB, The least bad of the ones I tried extends a tiny bit beyond the case I used. (And I can not imagine that it will harm the display in any way)

It was said on Twitter that Pro1 should work with Verizon and Sprint. https://mobile.twitter.com/chenliangchen/status/1109828299461660672 Technically that might be true but Verizon has not whitelisted Pro1. https://www.fxtec.com/networks-bands-pro1-support/

Thanks for the video! I can't quite see what's going on in the screen but it seems some light pages load quickly and scrolling is decent. I wonder how more "heavy" websites fair like Amazon product pages (the product images tend to take a while to load) or loading multiple webpages at the same time. It looks like the Xcfe session acts like just another app. Is that right? If so, when it's in the background, does it sleep or keep running? Thank you.

I have also experienced the keyboard lockout bug. I have the latest update installed. "F" key worked, others seem to be not (I have not checked caps lock). After reboot, it works again. Basically I have still a very few applications installed.

Someone must realize that videos should only be shot and viewed in landscape. :-)

Just to throw some more opinions/experiences in the mix: 1, 3, 4. Are things i quite easily got used to, I didn't really find the phone that big even (however my phone before this was a Doogee S60 which is a monsterously big slab). And as for the keyboard layout... I like the letters being offset now that I got used to it but the lack of a / key without fn seems like a weird decision to me. Overall still the best keyboard layout I've seen on a phone. On 2... Did they ever officially advertise it as being compatible with Verizon? I know we deduced on the forum that it *should* work, and it

@devyl I have added the 2019-12-03 package. You can try it to see if it works.

On #2. The phone is compatible with Verizon but that doesn't mean Verizon is going to support it and there is very little a small foreign company can do to change that. Mine works fine where i am, probably because we have good VoLTE coverage and don't need Verizon's CDMA network, which is where the problems with Verizon arise. Knowing Verizon well, I anticipated the problem and made a plan B (AT&T Prepaid) when I made the decision to buy the phone. I am grateful my area seems to have good VoLTE coverage, so I didn't need my Plan B after all. #12 probably deserves it's own th

It seems to be a good solution in portrait mode but unfortunately not in landscape as it applies to short edges then and there is no need to null at those edges but the long side in that mode.

Something as rare as an app that seems to work in landscape only 🙂 And indeed reacts nicely to navigation with arrows, enter, BS and escape

@fxtec5 Regarding your point 5. according to evildragon's setup guide at https://www.dragonbox.de/index.php?fc=module&module=ybc_blog&controller=blog&id_post=9 If you install the app Edge Null it should be solved (not the color issue though and yes the decision to use a curved screen was weird at best)

Hard reboot is done by holding the power button down for about 10 to 15 seconds. But I suspect that won't work either. I can make a package for the 20191203 build, perhaps that might work?

Having used the phone for a weekend now, here are my grievances listed in order of severity: Hardware issues: 1. Function keys. Who thought this was a good idea?!?! If they had just put the ?/ key where the right function key is, they could have completely eliminated them and used a standard QWERTY layout. I am investigating options to remap the keys, but the keycaps are wrong and from what I understand not replaceable even if fxtec came out with a sane qwerty layout. 2. Lack of verizon support. The pro1 was clearly advertised as being compatible with verizon, yet is not actuall

Well, I am looking at the programming files and it shows that it's writing both xbl_a and xbl_b from xbl.elf. So that part should be good. The files themselves should be good, I have flashed my device with these bits on multiple occasions. So I am a bit confused why this isn't getting you to the bootloader. You should at least get a splash screen no matter whether you hold the volume key or not. I've updated the full firmware package on my website to use the older, working programmer. The new md5 starts with 6b0... You can try downloading that instead of

Okay ... according to the device I have here ... root@QX1000:/ # ls -l /dev/block/by-name/ | grep sdb lrwxrwxrwx 1 root root 15 1970-02-09 03:12 xbl_a -> /dev/block/sdb1 root@QX1000:/ # So /dev/sdb contains xbl_a and nothing else. This is the second stage boot loader for slot a. So you did not overwrite anything that cannot be easily replaced. But xbl_a should have been flashed by the package that I sent to you, and that should have allowed you to get to the "upper" boot loader ("abl", or fastboot). Can you

Okay that helps. Let me investigate a bit and see what is on /dev/sdb. Let's hope no radio configuration lives there.

Why do you think it is a terrible phone? A lot of people, me included, do not agree with this opinion. So it would help to explain a little further, we may even be able to help you over some issues.

A simple video showing the SFOS port on the Pro¹, and more specifically Ubu Chromium (run in its own window, and then from xfce4 desktop environment): https://youtu.be/DLl92bISgAo I'm sorry about the overexposure of white web pages. I lowered the screen brightness and adjusted the camera settings, but not enough. 😕

That's great! So how's performance? Does video playback use the hardware decoder? Is there some way to emulate a mouse pointer to make it easier to click on small things and active mouse hover actions? I'm interested in the Pro1 as a UMPC with mobile broadband for desktop OS use on the go only. It's great that some devices are coming out with keyboards and potential desktop Linux distro support (ie. Pro1 and Planet Computers devices) but I really need a mouse pointer. Thanks!

this is my mobile "desktop" solution. i want to make it with my pro1.