Jump to content

Sean McCreary

Members
  • Content Count

    99
  • Joined

  • Last visited

  • Days Won

    19

Everything posted by Sean McCreary

  1. Until we are using tdm's driver, there will be undesirable interactions between the F(x)tec's custom keymap and the keyboard language selection in Android. Have you selected a language and layout as directed by the persistent notification to "Configure physical keyboard"? Don't do that. 😜
  2. Believe it or not, this is how we used to create OS distributions back-in-the-day. Fattire even wrote a short poem about it: So Many Zeroes! A Children's Book By Dr. Seuss (a.k.a. fattire) Blue had his V2, all shiny and GNU, and wanted to send it, but stopped to review. "What would this ware weigh, if zipped up today? Should it not be much larger than the SDK?" And yet it was bigger (nearly one-half a gigger!), but Blue still released it with vim and with vigor. "A drive is a drive, at any old size! But a drive is alive when its zero'ed to thrive!" So Blue packered his tracks with a /
  3. sshd is present in /product/bin, with sshd_config in /product/etc/ssh. I don't use this myself, but adb root && adb shell /product/bin/sshd -dddDf /product/etc/ssh/sshd_config doesn't behave the way I would expect. Did this work in 19.1? A quick check of old versions suggests this doesn't work in 19.1 or 18.1 either, so it may have been broken for a couple of years 😞 Since this isn't specific to the beta test you might open a bug report, following the instructions here: https://wiki.lineageos.org/how-to/bugreport
  4. Some of the modifier keys are mapped a little differently from stock, but the driver is still the same one as F(x)tec ships. The most important differences are the 'F logo' key is mapped to META, and the SYM key is mapped to AltGr (ralt). The old behavior of the 'F logo' key (KEY_HOMEPAGE) has consequently moved to 'F logo' + ENTER, but you can now use any of the other keyboard shortcuts built into Android. This list is contextual, and 'F logo' + '/' will bring up the list of shortcuts defined by the current app. FWIW, this is the same mapping as LineageOS uses on the Pro1. Among other mi
  5. That should have worked in the first beta build as well. Did you have problems with the keyboard?
  6. BharOS seems like a student project that got wrapped into a political stunt. For example The Indian Express includes a link to the announcement that calls it a step towards "Atmanirbhar Bharat", a political slogan from Narendra Modi. But on a completely practical level, it won't work at all with Google apps, you can't download it for any device, and it may only support one or more Google Pixel phones when you can.
  7. This is a bug in the stock OS, and happens because they modified Generic.kcm despite the comment at the top of the file instructing them not to. We have fixed this problem in LineageOS here: https://review.lineageos.org/q/topic:pro1x-old_kbd_driver-19.1 Hopefully F(x)tec can include these changes in a future update.
  8. FYI: https://forum.xda-developers.com/t/lineageos-20-for-pro1-x.4543997/
  9. While all our work is public, we don't necessarily post a neon sign saying, "Break ur phone here!" πŸ˜‰ The Pro1-X work is moderately stable now and has been moved to the official LineageOS org on GitHub: https://github.com/LineageOS/android_device_fxtec_pro1x https://github.com/LineageOS/android_kernel_fxtec_sm6115 You are welcome to use these for your own builds, but please be prepared debug any problems yourself. There are a few outstanding fixes on our gerrit, esp. this topic: https://review.lineageos.org/q/topic:pro1x-old_kbd_driver Also, please remember that although we work
  10. I haven't experienced this problem, and I don't think anything we changed in the May 16th build would cause this. I talked to a MindTheGapps maintainer, and he has seen this sort of problem if the device isn't rebooted (to recovery) between sideloading LineageOS and MindTheGapps, or if there isn't enough available space on the device. Are either of these a possible cause in your case?
  11. As a blanket policy, LineageOS does not provide estimates of release dates, etc. However, all of our development work is public, published on GitHub and our gerrit. What I can say is that we have a skillful and experienced team of developers interested in working on LineageOS for the Pro1-X.
  12. TBH, I never could use 18.1, the UI bugs were just too annoying. In comparison, LineageOS 19 is a big improvement πŸ™‚
  13. You really should have opened a bug report, as I never saw your complaints about duplicated keys.
  14. Please let us know if your charging problems change when running LineageOS 19. The official procedure for opening a bug report (at https://wiki.lineageos.org/how-to/bugreport) is still the best way we have to track problems, so please open one if you have new info to report. As far as we have been able to tell, the charging issue is triggered as the device ages, and two LineageOS developers have now reported similar problems. This is difficult to nail down however, as there are no new Pro1s being made that might be free from charging trouble with the latest software. However, our oldest d
  15. Yes, this is something Google did. I'm glad their fix restores proper keyboard functionality, and FWIW the underlying issue is likely an undisclosed security problem.
  16. If you are interested in the new interface Google introduced in Android 12L, you can enable it on the Pro1 with this 'Easter egg': In Settings->Accessibility->Text and display->Display size, move the slider all the way to the left ('Smallest'). IMHO the new UI isn't really finished yet, but it gives us a glimpse of where Google is heading for Android on 'tablet' devices.
  17. I'm hoping to improve the existing Settings app as part of the changes to support the Pro1X. An option to install a custom keymap from within Settings seems like a good idea, and I want to add support for a full custom keymap generator app in the driver. This would include a way to ask the driver what default keymaps are supported, and what keys are in each map (i.e. what is printed on each key). Since the default QWERTY map on the Pro1X will be different from the Pro1, the standard keyboard layout names aren't sufficient specify the correct 'default' keymap.
  18. After a very long delay, this feature has finally been merged in LineageOS 18.1. Beginning with tomorrow's build there will be a new option in Settings to make 'fn_r' (the right-hand diagonal yellow arrow key) send ralt/AltGr. This will enable full Windows-style task switching behavior, as well as assist entering accented characters when typing languages other than English. Enabling this feature will disable the use of this key to enter the yellow glyphs printed on each key, but all of them can be generated by chording with 'shift' instead, with the exception of '/' and '?'. Since these two ke
  19. We're really glad it helps :-)
  20. This has very obvious security implications, however. If you do this, you should be aware you are disabling some of the malware protection Google has built into Android. As an alternative, you might consider including gapps inside your custom OS image, like the OEMs do. For more details on how to do this, see: https://github.com/opengapps/aosp_build
  21. Yes, that is what I meant. FWIW, meta+A doesn't appear in the list shown by Trebuchet, so perhaps there is missing code somewhere in the framework.
  22. This list of shortcuts is scrollable, even though the UI doesn't indicate it. The full list has 14 entries by default. The app must register properly for the shortcut to work. For example, K9 never used to work with the meta+E shortcut, but after the recent UI redesign it now does.
  23. Right now you will need to use 'adb' to install the custom keymap, and there isn't any app to help you create the map πŸ˜• @Slion made this nifty QWERTY keyboard image with each key labelled with the 'key number' in yellow: The manual process is to choose which key you want to remap, and to look up the keycode you want it to generate in this list: https://github.com/torvalds/linux/blob/master/include/uapi/linux/input-event-codes.h You will need to convert the keycodes from decimal to hexadecimal if they don't begin with '0x'. The custom keymap is a file with lines contain
  24. For those of you who are self-building, I thought I should provide some info about where to find the monthly ASB patches. Google is currently backporting security patches to all releases since Oreo (Android 8.1), and there is a simple way to cherry-pick these patches from the AOSP source tree. You'll need to have synced the full tree first, following the instructions at https://source.android.com/setup/build/downloading tl;dr repo init -u https://android.googlesource.com/platform/manifest -b master repo sync Once you have the full tree, you can easily display the patches inclu
×
×
  • Create New...

Important Information

Terms