Jump to content

Slion

Members
  • Content Count

    1,369
  • Joined

  • Last visited

  • Days Won

    28

Slion last won the day on September 13

Slion had the most liked content!

Community Reputation

1,090 Excellent

1 Follower

Recent Profile Visitors

2,071 profile views
  1. There were people waiting for Pro1 general availability... they are still waiting. I think pre-ordrer is all we will get. But who knows maybe F(x)tec is making plans to pump out larger volumes.
  2. If you order now I guess you could hope to get it in a year at best, more likely winter 2022. They still need to show finished prototypes and start production. Then they need to ship to customers who ordered the Pro1, some years ago, and never got it. Then they need to ship to all the Pro1X buyers, then you. Though in terms of volume they don't need to produce that much really. Looks like they sold about 1500 units on IGG. So I guess with 3000 units they could easily complete all their orders. Much depends on how fast they can produce them really. I doubt they will be able to produce more than
  3. I do not know how to just change the screen brightness range rather than use Night Light to do that. Looking in our configuration we are already using quite a low minimum brightness – it is set to one, could it be zero? Should not make much of a difference anyway. – so I'm guessing this is more of a Kernel driver issue and I'm not sure where to look for it. <integer name="config_screenBrightnessSettingMinimum">1</integer>
  4. I'll be testing the following parameters: <!-- That's the one actually used on Pro1 vres = vat2 + vbt + vy-int --> <string-array name="config_nightDisplayColorTemperatureCoefficientsNative"> <!-- R a-coefficient --> <item>-0.0000000189359041</item> <!-- R b-coefficient --> <item>0.000302412211</item> <!-- R y-intercept --> <item>-0.198650895</item> <!-- G a-coefficient --> <item>-0.0000000189359041</item> <!-- G b-coefficient --> <item
  5. To configure Night Light you need to edit that config.xml resource overlay: https://github.com/LineageOS/android_device_fxtec_pro1/blob/lineage-18.1/overlay/frameworks/base/core/res/res/values/config.xml It is in fact overriding values from the platform config.xml in which you can find all defaults: https://github.com/LineageOS/android_frameworks_base/blob/lineage-18.1/core/res/res/values/config.xml From the two quadratic equations defined in our config, Pro1 uses the native one, at least in the configuration I tested: config_nightDisplayColorTemperatureCoefficientsNative Red co
  6. I think so. It does fire as a keyboard key, but even as an accessibility service you don't get it because the screen is locked. Same issue on Lineage yes until we implement a proper sensor for it. See post and link above. I may get around doing some clean-up at some point yes.
  7. US Int. layout works fine on LOS 18.1 yes. Though the default one provided by Android is far from complete, many AltGr character mods missing. The French accent dead keys are working though.
  8. On my proposal the left AltGr should really be labelled Sym and then everyone can map it to whatever they want, Del for instance. The right AltGr is really needed, not least for Alt+Tab.
  9. Me, I'm just happy it boots... However you have a point, if your phone does not boot I guess it's really secure 🥴 😁🤪
  10. I think you mean register the intent in app manifest. That's the first thing I checked, and the calculator does register the proper intent. Maybe I missed something though.
  11. Thanks for the tip 🤣 just want to illustrate what it looks like when an app publishes its own shortcuts.
  12. If like me you get stuck in a reboot loop after updating your ROM and no amount of GApps sideload can fix it, try that: https://gerrit.aicp-rom.com/c/AICP/device_google_wahoo/+/63092/1/device.mk https://source.android.com/devices/tech/config/perms-allowlist The logs during the reboot loop were mentioning: "Signature|privileged permissions not in privapp-permissions whitelist:" Basically I just added the following lines to my device.mk: # Bypass privapp-permissions whitelist PRODUCT_PROPERTY_OVERRIDES += \ ro.control_privapp_permissions=log
  13. @tliebeckWelcome on the forums. I think the displayed layouts on the IGG page are still what they were when first published. The community has already heavily criticized them in multiple places on those forums. My take on this, is that it should look like that: See also: The last thing we want is removing modifiers, also having printable characters on the bottom row of keys is not a good idea IMHO.
  14. Though Meta+A does not launch the Calculator for some reason, not on my Pro1, not on my Galaxy Tab S6.
×
×
  • Create New...

Important Information

Terms