Leaderboard

I have just wanted to show you a part of a photo as an example: I think it is a really good macro photo and it was took in the evening with room light without any flash. Resistors and capacitors are 0805 components. It is more than enough for me. 🙂

Today I have just received my Pro1 bought at dragonbox.de (still a pre-orderer with IGG coupon here). I have still not tested it too much but I am very convenienced with this device. I am very happy that I have ordered QWERTZ layout which works very well currently with the help of FinQwerty's QWERTY layout. (I would have been much happier with unshifted QWERTY anyway but the QWERTZ keyboard with a correct QWERTY layout is a good compromise.) Some sticky modifier keys would be good anyway and also the ability to access layout files somehow (I have still not looked how to do it) as I

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

The layout I currently use ("U.S. international for physical QWERTZ" - also has appropriate version for QWERTY keyboard) generates "!" for "shift+1", so it works as expected. Yes, I also have this bug.

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

@EskeRahnsuper thanks! Here is a new bug which was preventing me to take your advice: I kept going into settings, now trying to deselect 4 different layouts I was trying...but "Setup keyboard layouts" was at a bottom of the popup window, and unaccesible in landscape mode...I had to go to upright mode to finally do it! I think this is a bug, amplified by me also using large system font. OK, I downloaded FinKeyboard (thanks!). It would be nice if there was a layout that defaults "shift+1" to "!", which is what got me into other layouts... The original bug (keyboard stops working) is st

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

Ordered the 711042. I'll report how it goes when I've got both the phone and the holder!

I agree! but have a look at finqwerty that solves a lot! P.S. I agree on a lot of your points but they don't bother me too much. But honestly without finqwerty point 1 would also be a big problem for me!

Since Pro¹ is 73,6mm wide i can safely say i got the 62-77mm variant. Most likely mine is an old model of 511307. But since 711042 starts at min 70mm it should also fit, right.

I think no. I can reach the characters listed in the link you wrote as "U.S. international for physical QWERTZ" because that is the layout I currently use. So also yellow arrow and Alt(gr) both show appropriate characters as in layout description.

Excellent, thanks! That would be one of these, then, best fit is probably #511307 or #711042 ... 🙂

It sounds to me like you might have selected a layout language. There are a lot of android layouts that comes with the phone, they work poorly and should be ignored(!) You got three options selecting the keyboard layout for the hardware 1) For US letter-shifted QWERTY deselect all tick boxes, do NOT select US (Yes I know it is odd....) 2) For German standard QWERTZ select German, do NOT select another qwertz based layout 3) Install FinQWERTY that supports several languages for the Pro1 for both hardware layouts, and you can use more than one, I use Danish+US+Swedish

I use ram x-grip holders in the car and on the motorbike, too. Until now, each phone could be placed in it to reach all of the buttons... https://www.rammount.com/product-lines/x-grip

@Doktor Oswaldo I am maintaining a list of network experiences on the clack. Unfortunately, due to limited time editing, I cannot update the top post to make it a list with everything currently known. Fortunately, @EskeRahn is very helpful, and has the power to paste in the updates I send him. It just seems like a clumsy, bothersome way to do it. I'd rather not bother him, but it is what it is.

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

Kodi Media Player works very well from the keyboard in landscape. Just takes a little moment to work out how to navigate the interface by keyboard rather than by touch or mouse.

The universal holder from Brodit does the job. Sorry, no idea about measurements and order number, it is like 6 years old. But i just needed to widen this universal holder to max after using it for XA2 which was more narrow. The thickness is exactly matching the cutout space so the pro¹ sits very tight. https://twitter.com/eLtMosen/status/1197074326245257216 Oh, and cheers form an Audi 80 [B4] owner for ~10years 😄 Now i upgraded to this nice [W639] Vito with just 260tKm.

So I have to correct myself here, it was posted by the official F(x)tec twitter, this photo https://twitter.com/thefxtec/status/1119617316034162688/photo/4

If I'm not mistaken, that was an image that F(x)tec released (on Twitter?).

That is why forums with editable topics normally need some form of history. But in my opinion it is useless to not be able to correct or refresh a post. Nobody will read through a hundred sites of stuff to get an overview. They will just open a new thread with a title like "What is a good working app for X". Editing the thread with the app recommendations would allow to have one centralized complete list (as an example).

I'm only a 90% sure. The reason for expecting these to fit is that Chen (@Waxberry) showed a photo of a box full of screens on which the numbers are the ones of these panels. We also know screen protectors for this Elephone U fit exactly (which I can confirm first-hand). And do take my advice to contact support, they'll be more certainer, and perhaps have instructions on how to replace. Hope you get it good as new soon :).

From what we have heard is should be very service friendly. Is I understand it the only thing that is not accessible by screws should be the keyboard plate (that requires a heat gun)

Mine was from Clove Tech, received safely...though you can believe I was standing at the door waiting for the UPS delivery driver. The universe is conspiring against pre-orderers and my attempt at 'cheating' would be just my luck to be stolen by my first ever porch pirate.

Thank you very much. Going to pay you a beer :) E: done, just dont know how the Karhu price changed since this summer

Yes I'm aware of the work @netman is doing on the keyboard. I'll incorporate it in due time, after I get the vendor image built and voice calls work.

I can add one in the next FinQwerty version 🙂 Does the below layout look OK? Or should I perhaps swap Y/Z (if both are wanted by people here, I can also add both), or any other suggestions?

You may very well have just saved weeks of head scratching trying to identify this issue! Thank you for sharing this!

One and a half days for a modern smartphone, depending on how you define "moderate use," sounds pretty good. On the days I was testing the heck out of mine, I got down to 50% at bedtime. I consider that good.

FYI, I have imported the Pro1 FinQwerty v1.5.1 key character maps (kcm files) into my LineageOS builds. If there are other kcm files that people have worked out for the Pro1, I'd be happy to add them as well. The current FinQwerty maps add support for Czech, Danish, Finnish, Norwegian, and Swedish, as well as the alternate German mapping. For reference, you can find the patches required to add additional kcm files to a device build here: https://github.com/mccreary/android_device_fxtec_pro1/commits/lineage-16.0/AsantiKeypad The last of the three is not necessary for the stock Pr

As someone who never had a keyboard smartphone before the Pro1, I would say it very much matters what you are used to. The QWERTY layout on the Pro1 might be shifted a bit, but it’s nothing different to simply getting a new keyboard for your PC. There always will be a learning curve. I find the Pro1’s keyboard much more functional than the compared devices above, particularly for the spacing on the Pro1 keyboard. Give it a week, and you’ll see how much faster and accurate you are, especially in the technical tasks such as using terminal. I will not accept disputes on this subject at all,

Somehow I managed to break the glass surface of the screen. The touchscreen itself works just fine. But what do I do now?

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.

This is what the screen looks like... but everything still works.