Leaderboard

Pics or it didn't happen.

test13 is up. Changes: * Updated QWERTZ keymap. * Addressed some SELinux denials. If you have a QWERTY device, there is pretty much no reason to upgrade from test12. If you have a QWERTZ device, please test and provide feedback. Please remember to remove any custom keymap before testing.

Sidekick. What phone don't YOU miss anymore?

Seems an awful waste since a) I have no idea why you think you are entitled to a refund for a smashed phone and b) unsmashed, you probably could have sold it. But if the therapy was worth $700+, glad it was cathartic. By the way, very little of the above has been my experience.

My Xperia Mini Pro... Was way cuter than the BB Priv and allowed custom roms.

Nokia E7-00

47:0026:802b (l and ') It was in issue 35 and by some reason did not get into qwertz test1 and later in test2...

Not missing my BB Priv, how I managed to stay on it for 3 years is still a mystery.

I'm no longer missing my n900, and definitely not the dumb slab phones I used after it :)

TeZtdevice, your advice was greatly appreciated - i replaced the original screen of my Pro1 and the new screen works flawlessly, or let's say, the upper 1/6 part of the screen started to be responsive again ! that's fantastic because apps like SONOS or FOTOS cannot be rotated and do not allow landscape mode. now i am able to reach reach again the apps' settings buttons. of course i also very much appreciate Fxtec's support service that sent me this replacement part for free !

I am pleased to announce test builds for LineageOS 16.0. Please note this thread is for test builds. These builds are not necessarily stable or suitable for daily use. You can find the build(s) and detailed installation instructions here: Lineage on FxTec Pro1 Test Builds Please report any issues here and I will do my best to fix them. Thanks!

Today was the best moment I've had with the pro1. I bent it with my hands, threw it across the room into a wall, I retrieved it and the thing was still on even though the screen was cracked, and the keyboard dislodged from the body! I pulled my sim and sdcard from the phone so I could finish the job. I took it out to my workbench and smashed it to pieces with a hammer. It was truly the most satisfying moment I had with the pro1. The spontaneous reboots for days on end and then stability for a couple weeks, only to start rebooting again. The ability of the camera to take one

Sounds like you could be right. Looks like an odd scam. The account created a few days ago using a "spamdecoy" mail-address. It all have an ooze of fake... But I could be wrong of course.

The Phone I doubt I will ever miss is the HTC Diamond. Not because of the hardware, but the extremely unstable Windows software. I would be lucky to have a day without a reboot, and I needed to do a factory reset at the least every fortnight! I actually ended up making a MORT_SCRIPT that could perform a full factory restore, and install my apps, and set the needed settings!!! Ran it about every second week, or when the device had messed it self up too much- Often when the phone rang you would be unable to pick it up.... With Vista being a competitor, I think this is the worst software M

When developing N900 at Nokia we had a special koops handler which saved the crashing kernel oops to a log area in NAND memory. The saved dumps were then automatically reported on the next reboot. It collected valuable statistics about the frequency and stacks frames of kernel crashes. Without the NAND based logger the devices would have had to be logged via serial console.

I was so close to getting that phone back then, the Relay. Got one that was unlocked, it kept chewing SD cards and corrupting all the data on it, not sure why. Had to return it and ended up down the dark, dark, BlackBerry route and got a Classic.

I don't miss my N900 but I still miss the freedom of its Maemo system and its usability (the real multitasking and proper application-handling for example).

The Pro1 is my first keyboard phone, so I'm not missing any phone I ever had. But I especially don't miss my Nexus 5, which was my favorite slab phone ever and was the only phone that made me not miss my Palm TX anymore. 😉

Thanks. It took me a while to guess how to find the qwertY/qwertZ setting. I browsed through the Settings-tree unable to guess where it is. Gave up and tried searching for "qwerty" or "qwertz" that did not find it either. BUT if I do a search for "keyboard" or "layout" it do pop up on the search-list. 🙂 Would be nice if it had some natural entry in the settings-tree, preferably under Settings ► Language & Input ► Physical keyboard Or perhaps in a special top level setting group for all the customizations settings that are device specific. e.g. "Pro¹" or "Pro¹ sp

Just published release v0.9.1. This one introduces significant redesign of the menu and tabs list tool bar for improved user experience, obviously 😁

Yes, with the qwertz test2 boot image you may specify AltGr as a modifier. It seems this is very close to the final desired mappings, so I will incorporate it into test13. Because the '?' symbol is generated with shift, you would probably need to choose another key to map for use with the yellow-arrow. Perhaps the "O" key, for example: 44:0018:8035 And, now that you mention it, the SYM key does also generate KEY_RIGHTALT, aka. AltGr. So I am wondering if that is still desirable...? Thanks for the report. Please file an issue on g

I'm from Germany with order #36xxx for a QWERTZ device, though mine wasn't in this batch yet. But I got this new message: Hello! We hope you are well and keeping safe. With the factory returning to normal production speeds, we are making steady progress working through remaining orders. The factory has confirmed a small batch of Pro1’s is ready to leave the factory, and those that have been allocated stock should now have received a shipping update. We are currently negotiating shipment releases on a 2-3 week basis with the factory, and will be in touch when the next shipment is ready.

Hello! We just wanted to let you know that Pro1 production is well underway, and we expect to ship more units over the next few weeks. Continued restrictions on the movement of goods around China has resulted in some processes taking longer than anticipated and at slightly higher costs, but overall the situation in China is improving and we now have almost 100% of our factory staff back to work. This means that we can ramp up production as we work our way through the backlog of orders pre Covid-19. As always, thank you for your continued patience and support. Sincerely, Team F(x)tec

@Craig I'll respond once here... In theory gapps should persist from install to install. If that is not working, someone may need to investigate. You do not need to re-install the recovery once you have it. I'll try to get the instructions updated. The slant arrows are fully dead keys in the current Lineage build. I would like to make them customizable but haven't gotten there yet, as there are higher priority issues. After they are customizable, however, you will still need to keep at least one key as KEY_FN (or whatever I decide to make it) for a fully dead modif

As I have reported before, my device has been having random reboots once a while. It has been almost daily. Typically, when I wake up, I come to kitchen from upstairs and start to make breakfast. Looks like I have better network upstairs, because these reboots almost always happen in the kitchen, usually at morning when having breakfast. Also I have those reboots sometimes when I travel to places with weaker network coverage. But what is strange, is that I don't have these reboots anymore. Like, at all. Let's say no reboots in 7 days at least. Nothing have changed in my phone lately, and I hav

test 13 does not boot like test12. Returns to recovery. And no way to boot into test11 which worked ok, although the slot a/b thing should be designed for that? History: 1. Returned to stock and decided to offer my Pro1 to sale... 2. Decided still to test again SailfishOS. Flashed twrp to boot_a and using twrp installed SailfishOS. 3. tdm resumed development and decided to continue testing qwertz layout 4. flashed test12 boot to boot_a and sideloaded test12 to b - did not boot 5. repeated that with test11 boot&zip - test11 booted ok and was able to test q

My phone also reboots. It's not at random times. It's whenever I'm at certain locations. If I'm connected to the wifi at my house, I get "random" reboots. Sometimes up to 6-8 per day. The network at home uses a 192.168.1.x address range with 2.4GHz and 5Ghz wifi bands. If I'm at work with a different subnet, it's just fine. FXtec support knows about the issue, the first thing they asked when I said I was getting reboots and couldn't hold a call, was "are you using wifi and is wifi calling enabled". If I'm using wifi at my house, I can make a call for about 1 minute and 20 seconds before t