Leaderboard

the virus seems to have a better chance of reaching me than pro1 :(

Not sure if we've had much info on this officially but they at least Tweeted back on this... So if nothing else, then at least we know it's planned

This will take you to a poll which includes the fxtec pro1 as one of it's options. Let's make this happen.

@tdm I know you've got some ideas of what keycodes to assign the various modifier type keys, and recently I saw something about you doing some odd things with the slant-arrow keys that might restrict user customization, etc. I've chatted with mccreary a few times about my thoughts, and thus learned a lot of stuff, and wanted to share what I believe would be the ideal way to map keycodes in kernel that takes advantage of built-in AOSP features, and allows user to fully customize layout afterwards. Esc --> Esc Slant Arrows --> Meta (left & right - separate key codes ar

you can use camera on another phone for find sensor 🙂

I just found out about this phone, watched a vid, and am in looooove. Want to purchase (pre-purchase), but need to know-can this phone be locked/what kind of security features does it have?

So I've managed to restore my device to the original image. I was following the solution from Tom and using his tool from here: http://files.nwwn.com/android/pro1/factory.html However, I've faced the same problem which some people were posting here: "Connection time out". Have no idea what could be the reason of that. Nevertheless, in the end I managed to successfully reflash the phone. The trick is to have prepared tool for reflashing and to press a button as fast as possible immediately after you reboot the device (power + volume button down). Because device ins completely unrespo

Thanks. When Foxconn factories restart at Shenzhen it will be in the news. This news is about Zhengzhou: Apple supplier Foxconn restarts key China plant with 10% of workforce, source says "The company, however, has not yet been allowed to restart production in Shenzhen, a southern manufacturing hub, the source said."

I'll attach it as a screenshot for others who can't get into it: basically it's something for the "near future"

I think they don't know it - also their manufacturer doesn't really know that I think. Even our PCB production partner can not predict when they are able to assembly our panels - not related to F(x)tec.

EskeRahn posted a NVRAM variable here, but how do I set it in fastboot?

Sure, it seems silly to me also. But that's the way the keyboard is printed. I would map the fn keys to something else but they are required to generate '/' and '?'. But the beauty of the new keyboard driver is that you can remap all the keys. The gpio keys aren't remappable yet but I'd like to make them remappable before I finish.

I'm on the 20200106 firmware but can't swear right now whether I was at the time.

I am going to make the default keymap as close to what one would expect by just looking at the keyboard as possible. That means: * The right-slant-arrows (fn-keys) are (dead) modifiers that allow generating the yellow symbols. * The FxTec key could be anything, really. Home would be fine, or any other reasonable suggestion. * Chording the FxTec key (FxTec+number) is sort of asking for two things at once -- you want it to be both a normal key and a modifier key. That's probably not easily doable. But I would like a way to generate F# keycodes. I was thinking maybe fn+ctrl+#

Fn does not go sticky on Alpha.

KEYCODE_FUNCTION?

The built in AOSP launcher shortcuts only work with Meta keys. That's why I originally suggesting make Fx key meta key, so you can use launcher shortcuts from there. But if we make the slant arrow keys meta, then that's where the global shortcuts will come from, and Fx key is useless (other than its current use, android home) but that function can be meta+h so not needed to have a dedicated key - but that's my opinion. I get the impression some people like this single press home key, and that's how Fxtec seems to want it. This is using built in Android stuff so not major work for fxte

Windows 10, 64-bit, MTP (it's called "File Transfer" on the phone's USB menu) and, yes, USB debugging is enabled.

Well if if the Yellow arrows becomes Meta then why not let the Logo become Fn? And map Fn+] respectively Fn+Y as home (for qwertY and qwertZ), the key just above the logo, so very easy to press with one finger... And PERHAPS (similar to press and release Alt with Gboard) let Press and release Fn do Home as it currently does, if this does not require some special coding. Giving both the existing and potential additional behaviour.... Fn+1..0 plus next two could give F1 to F12.

Thought this was worth reminding people of this while we wait for internal solution, as I've seen it referenced in a few other threads lately. Plus even if they fix the keyboard stuff, there's still plenty of use for this app.

Yeah I don't care about the colors, I expect shift to be level 2 like every other keyboard in the world, until now I hadn't even made the connection that the slant arrow and 2nd level characters were both yellow, I just assumed that's an fxtec color they chose to use for looks. But yes, the lack of slash and question mark should be handled in the kcm, not kernel. And if fxtec doesn't provide layouts that can get slash and question mark, then finqwerty is our solution. I personally plan to map the right slant arrow to slash key once the two oem keys have separate key codes in kernel.

My numbers come out the same. I have this card. https://smile.amazon.com/gp/product/B0758NHWS8/ref=ppx_yo_dt_b_asin_title_o03_s00?ie=UTF8&psc=1 Could this be because of being formatted FAT32? I have no rel knowledge in this area. I luckily don't often write large files to the card, just occasionally move some media over from my PC. What I have noticed is that if moving a large amount of media via USB connection to my computer, the connection will time out after a while. I discovered this when trying to move my whole music library to the card. It took 3 or 4 attempts to

Well it might work while closed, but I doubt they would stick when slid open, but could be worth a try. Note though that the hard edges could be complex to modify for the buttons and fingerprint reader. Being creative, what about modifying TWO sets? One for each part of the Pro1, cutting down the covering back on one case and the front on the other case...

Yes, but manufacturer may just released an update about unknown production time (at least for us)... So, currently it is not simple at all to say any meaningful information... so yes, an update about no update is possible but nothing more unfortunately.

I see this on a Pro1 too. Pure stock, no rooting or the like.

My phone tried to brick itself when the SD card I set up as adoptable storage failed. I ended up having to flash back to stock, reapply the OTAs, and re-root as well. I had to take it back to Verizon along with my old Samsung so they could deactivate and reactivate my SIM. Until they did that, the Pro 1 would get stuck trying to register in the switch. That was per the Verizon tech watching what was going on from their end. Steps were: 1) put SIM back in Samsung and establish everything works; 2) deactivate and reactivate SIM, establish everything works; 3) put SIM back in Pro 1 and verif

I know, I tried to find that information earlier when I was making the previous post. Thing is, because (I only just noticed) the screen of the Pro1 is marginally smaller than the base it looks as if even the other style of P20 Pro cover will also be too big. We'll need to locate a case with smaller dimensions than the Pro1 to fit the screen portion properly. EDIT: Scratch that, because of the screen curve the vast majority of it is 'smaller' but the screen actually curves down to the same size as the base. However, because its not as thick as the base the 'rear' cover doesn't f

...Well I received a P20 Pro split case like the one shown above today. Unfortunately because the screen half slips over the rear half it is too big to sit over the Pro1 screen. ☹️ The thing is the rear half also seemed slightly too big to stay on the screen. ...One thing I have found out is the Pro1 screen is far easier to open with the protectors over the screen, just need to find one that fits...

Just curious. Are they a-holes because they only want to support mainstream phones with a large enough customer base to be profitable or are they actually a-holes? 😉

That happened to me once. I then managed to mess up and brick my phone (trying to unroot and take OTA... not sure how but I refer to it in Magisk thread). I recovered by reflashing the October original factory image, took all the updates including the January one I had been trying to unroot for. When I set Verizon up again everything was magically working and has ever since. And, no, I don't suggest you try my remedy. 😉 🙄 Make sure you set everything back up, including all the LTE provisioning and selecting the right preferred network(s). "Global" works great for me. There's a l

CORRECTION #2 : testing the indicator LED actually worked just once, for missed phone calls - now it doesn't make a blink, nada. i suppose the Android permission settings in my Pro1 don't suit the requirements for the Light Manager 2 app. oh man, how much do i miss the CLI - there at least i know what and when i do something wrong... is there any other app out there that could help here ? HOPPALAH ! the LED is now blinking yellowish and greenish alternatingly, perhaps some 10min after i had started the last test ! there is even some red in the light. as you say, VaZso, a light d

Regarding the bug a few posts back where things found in the search results can't be found on the linked topic/page.... The problem appears to be when posts have been moved by a moderator to another topic. The search data isn't updated for whatever reason. I'm not sure if some index can be rebuilt for that or if it is a more ingrained bug with the forum software. It doesn't happen with every post moved. It could be that the search lags behind the move and that the instance I found today will be resolved when more time has passed.

It is slightly left of the speaker. Note that it got quite a delay in reacting to changes, but pressing power off and on, triggers a new read.

Works fine here.

The router does both, of course, but my Pro1 is connected to the 5.8Ghz access point

That's weird - I thought a posted (another) response... I got it working by allowing updates over data/the network (instead of just wifi). All sorted. 👍

Speedtest also works fine on mine. And I did the ADB thing to allow charging when turned off, but I am not currently rooted, stock firmware. My BL is unlocked as it came to me that way and I have never changed that.

Yes that is what I wrote: Android Market , http://market.android.com/ ...I know i'm old, but I'm not going to use the silly alias

F(x)tec didn't think real hard about searching when they used parenthesis in the brand name and superscript in marketing name.

Didn't see it in the list, so Telus (Canada) working with no issues. 4G, calls, SMS, MMS, other data, all good.

Ah Thanks! That explains the difference! And yes silly limit, could have been a range. Let us hop they fixed that in 10 also. Setting the font to small also, does not seem to offer more options.

Try read the initial post in the thread. It was never intended as a discussion threads on apps. And as this is actually a feature request that is fixed by the app, I found it more suitable in here. That apart it did not seem to work that well on my unit, maybe it is because I fetched it from the Android Market, where it is 3.2.0, the version is slightly lower in your link 3.1.8. It does offer a lock mode I did not try, but simply turning off the display would have been enough for me. It seems a little odd that it would need more privileges to turn off the screen than to turn it on. B

Thank you both, it worked.

The main part of this is you have to boot to bootloader before executing this command. From android, you can execute adb reboot bootloader; I think you're sfos, so you're stuck using the voldown+power method to get there which always works.

You need to have usb debugging enabled, and ADB installed. Then we can execute fastboot oem off-mode-charge 1 EDIT: from fastboot mode, see Craig's correction below.

is there any new information about the current corona virus lockdown and is there any idea when production will start again? the wait is really hard to bear 😢

Hooray! The problem seems to be solved, after flashing some of the partitions, as described in thread of Factory Restore Tool, with command-line tool qfpkg_cli . Apparently, Sailfish OS makes it very easy for user to format internal phone partitions, under mistaken belief of them being memory card partitions... In short: don't go and format a partition just because GUI recommends to do so - it is not necessarily a good enough reason. Thank you! Best wishes. ~~~~~~~~~~~~~~~~~ Per aspera ad astra...

If I was F(x)tec I would get a portrait device in development to cover that section of the market.

Thats the problem these days no real differences between devices.

I use the app "Battery charge limit" from XDA, which allows you to limit the battery percentage. I usually set it to 85% except if I'm going for holidays or so. I think it could already work with the Pro1, but maybe we need to wait (and ask) for the support. According to the magnetic chargers: I use a couple of mobile devices for work and have not yet found a reliable charger that does also charge quickly. And I'm not even talking about quickcharge or data transfer. They all are flimsy, have a stupid LED (and some further electronics to prevent burning them out) or break after