Jump to content

ivoanjo

Members
 View Profile  See their activity

  • Content Count

    36

  • Joined

  • Last visited

 Content Type 

Posts posted by ivoanjo

    Having problems contacting Fxtec support

    in Support

    Posted

    > And then we don't see how many people have had success in their dealings with support, they don't come here to report. It's only the failures we get to see here.

    Sure, but when we're getting to the point where I'm considering I may never see my device or my money again, and fxtec is plainly just not responding to old or new tickets, it's pretty scary. I just want a "sorry, we're missing some parts, we're on it" so that I know that there's life on the other side.

    At this point, one needs to start considering that buying a Fxtec device is a bit like buying second hand. You get what you get, and you have to make do with it. Which is a big shame; it looks like us keyboard fans can't catch a break, there's always a huge deal breaker involved (and it's not just the price or the poor specs).

    • Like 2

    Having problems contacting Fxtec support

    in Support

    Posted

    I'm also on a similar boat.

    Sent my Pro1 for repairs in early July, got this reply on the 12th of July "Thank you for confirming. We'll pick it up this week and it will be repaired and returned to you most likely by early next week."

    ... and nothing. It's now almost October. I've sent in several e-mails. And all I get is radio silence.

    I'm beginning to think I'll never have my phone (or money) back. Help?

    • Sad 2

    Duplicated keys

    in Support

    Posted

    For what it's worth, I never had such issues that I can remember for all of last year. That's why I suspected it may be some new bug on LineageOS, but once I flashed to stock and saw the issues I was pretty much convinced it was a hardware problem.

    If there were such issues when I got the phone in early 2020, I would've immediately sent it back.

    Duplicated keys

    in Support

    Posted

    I think you may be right @auvo.salmi. I flashed back to stock, and no dice -- same problem.

    I'll see if I can send it in for repairs. Indeed like many here I was hoping that my Pro1 would last for a few years, but...

    [Guide] PRO1, Restore to stock firmware using Fastboot method

    in Support

    Posted

    Thanks tdb for your Factory Restore tool. I've used it to go back to stock as I'm trying to see if

    ...is a hardware or a software issue. I got it to work successfully, but did run into a small snag on my way there.

    After a successful flash with the "Q Flash Tool", I got dropped on this menu:

    bootloader.jpg.8078aa92b0fcc1a0140856519fb7feac.jpg

    ...and "start" would not work, not any of the "reboot to recovery" options -- I just got back here. I tried with both the 2020-07-07 as well as with the 2019-10-28 firmwares.

    I then tried your suggestion of using fastboot to set the b slot active (I confirmed with `fastboot getvar all` that a was the one selected):

    On 9/7/2020 at 6:05 PM, tdm said:

    Try switching slots via "fastboot --set-active=b".  If that still does not work, you may have bad flash memory or some other problem that I can't help you fix.

    ...and this fixed it for me. I did have to run the fastboot command a few times, it seems a bit temperamental (once it said "error: Device does not support slots." and twice it said "FAILED (remote: Invalid Slot)").

    So if anyone gets stuck along the way, hopefully my hints can help you get unstuck 🙂

    • Thanks 1

    Duplicated keys

    in Support

    Posted

    Yeah. It's just such a shame that 18-ish years ago I could nuke my Palm Zire 71, do whatever experiments I wanted, and then put it on the cradle, press a button, and everything would be recovered.

    Android is still a mess of some apps that restore their configs, some that don't, etc. Just awful.

    • Like 3

    Duplicated keys

    in Support

    Posted

    No luck! I did a complete nuke this weekend: factory reset, then flash via adb, and I still get repeated keys.


    Damn. I'm trying to resurrect my Blackberry Priv so that I can use it temporarily, and once I do, I'll try flashing back to stock and see if the issue still happens there (and thus is hardware) or not (and thus is LineageOS issue).

    • Sad 1

    Duplicated keys

    in Support

    Posted

    I'm not sure it's the repeat, as it also happens on keys where long press triggers a popup. So if it was "sticking" I'd expect the popup to show, but it doesn't...

    Duplicated keys

    in Support

    Posted

    Hey y'all. I've seen some references to weird input issues in the forum, but none seem to match the issue I've been having. For the past months, I've been getting phantom repeated inputs on the keyboard. I'm typing away, and some letters appear twice (and sometimes the clicks don't register at all).

    I definitely did not have this issue with the stock firmware, and I believe I didn't either when I originally migrated to LineageOS 18.1, but this has been going on for a few months and it's really getting on my nerves (I've been trying to ignore it, since it takes me many many hours to do a reflash and restore my settings, and this is my daily driver).

    I've tried turning "Fast poll" off and on, with no difference, and I'm running the latest 18.1 build, from 14 of June, but I've had this issue for many builds.

    Does this happen to anyone else?

    • Sad 1

    LineageOS 18.1 Official Release for Pro1

    in Pro1 - Thoughts & questions

    Posted

    Two more issues I found (still on April 1 version, will upgrade after I post this):

    - The keyboard seems to be less responsive. Sometimes it seems to not register a keypress, or more often, register it twice. I've tried both with "fast poll" enabled and disabled. 

    - My Samsung Gear 2 Fit Pro fitness band was having a lot of bluetooth connectivity issues, especially with a bluetooth headset connected at the same time. Enabling "Gabeldorsche" in the developer settings seems to fix it (and in general with Gabeldorsche, bluetooth seems to behave better than stock).

    LineageOS 18.1 Official Release for Pro1

    in Pro1 - Thoughts & questions

    Posted

    Does not seem to work. As an experiment, I just changed the existing file to see if it worked: 

    type FULL

key A {
    label:           'A'
    base:            'x'
    shift, capslock: 'X'
}

    Nothing happened. I still get a and A when I type 😞

    I've also tried having a file in /data/system/devices/keychars/ instead of changing /vendor/usr/keychars/ but nothing happens as well...

    LineageOS 18.1 Official Release for Pro1

    in Pro1 - Thoughts & questions

    Posted

    1 minute ago, FlyingAntero said:

    Yeah, that is a pity. I have been talking about this earlier. Currently I cannot write @ symbol with QWERTZ using Finnish layout. It is possible to modify KCM file with root but it is quite hassle.

    I tried it with root as well, but none of my changes would stick (I opened a separate thread for discussion of it). TBH at this point I don't really mind having to do something weird, as long as it works lol.

    How to customize the keyboard layout on LineageOS 18.1?

    in Pro1 - Thoughts & questions

    Posted

    I recently migrated to LineageOS from stock, where I was a happy FinQWERTY user. After seeing it was broken and finding out in the forums that FinQWERTY is expected not to work, I've been crawling all threads related to keyboard layouts and adjustments and nothing I did worked.

    (In my case -- I'd like to type Portuguese, so I want combining ` ' ~ ^ and ç; none of the built-in options really seem to be comfortable for typing. There's a few alt combinations that are really hard to reach for a couple of them, but not all...)

    I tried tweaking a KCM as described in

    but the changes don't seem to be applied.

    I also found out about /data/system/keyboard/keymap (see https://github.com/LineageOS/android_device_fxtec_pro1/blob/2bfa41a3f649e1c97b588dc08ee7ff09d7bd1447/devicesettings/src/org/lineageos/settings/device/Constants.java#L27 ) but I don't really understand the format, since it's different from the kcms.

    Has anyone managed to customize the keyboard on LineageOS? It'd be a big shame if I needed to go back to stock just so I could type comfortably 😕

    • Like 4

    How to install AICP (or other ROM), Magisk, and root with SafetyNet, Certified Device & Google Pay working

    in How Tos

    Posted

    This didn't quite work for me. I've had my Pro 1 on the stock firmware up until today, where I installed LineageOS 18.1 20210401.

    I followed this guide, did the magisk hideprops config, and cleared the google play settings, but afterwards the safetynet would still not pass (even in magisk's own check).

    I googled a bit, and installed https://github.com/kdrag0n/safetynet-fix (downloaded + installed via magisk), then hid magisk and did the clear data/cache/reboot dance again, and afterwards safetynet passes.

    I also installed Google Pay and was able to set up NFC and everything seems to work fine (I didn't need the fix).

    • Like 4
    • Thanks 2
×
×
  • Create New...

Important Information

Terms

  I accept