Jump to content

Leaderboard

Popular Content

Showing content with the highest reputation on 09/13/2021 in all areas

  1. From my experience with LOS (16.1 and 18.1, never used stock) I can say that the excessive call volume is related to VoLTE being enabled and active on both sides. While someone else (on another network) reported he had to completely disable 4G, for me, disabling VoLTE ("4G Calling" in the "Mobile network" settings) was enough to get rid of the issue.
    3 points
  2. Since I have never had stock, I cannot compare LOS to it regarding call quality. But I somehow remember @tdm saying the telephony bits were taken 1:1 from stock, so maybe there really should not be much of a difference ... All I can say is I'm happy with the few phone calls I make. Yes, sometimes I adjust the volume during a call, but no idea if the Pro1 is to "blame" in those cases, or whether it is my partner's phone. That said, I am probably the wrong person to ask, really. I have accepted the fact that reliability and audio quality in telephony reached its peak around the time of the
    3 points
  3. I decided to make the jump and use Lineage OS 18.1 as my daily driver. Moved both my SIMs from my stock Pro1 to my Lineage Pro1. Though I'm not using the official release. Instead I have a custom build with a modified keyboard driver, which is work in progresss. It seems I can still develop that driver without compromising my daily regular use. Took a bit of time and a few reboots to get my Orange FR SIM data to work but I had the exact same experience on stock as I recall. 1&1 DE SIM data worked straight away. Just wanted to congratulate everyone involved in making Lineage OS on
    3 points
  4. Okay, the issue occurs when device is fully charged and shuts off charging by software when the charger is still connected. When the phone is connected to the charger once again, it is not charging, only reset fixes that
    2 points
  5. FYI, the DeviceSettings UI fixes will be in tonight's official build. If there is any problem applying the custom keymap, the user will see a 'toast' error notification and the custom keymap will be toggled back off again. This resolves the problem that there was no feedback when things go wrong. To test, you can use any keymap with a syntax error. I have been using this one for testing: 70:0000:0000 Since there's no key 70, this generates EINVAL which triggers the failure notification and modified UI behavior. I'm sorry this problem wasn't noticed before causing VaZso so much f
    2 points
  6. Is anyone else having an issue charging the Pro 1 ? I connect the phone to the supplied charger via the supplied USB-C lead and nothing happens, if I remove the lead, rotate it and reinsert it the phone charges, occasionally. Sometimes it takes several attempts at this procedure to get the phone to charge, then I've noticed that after a while the charge light will go out and the phone will stop charging requiring me to repeat the whole remove, rotate, reinsert procedure until the phone starts charging again. Sometimes the charge light will come on but the Android battery indicat
    1 point
  7. Sad to hear. But just to be sure, are you on stock Android or LineageOS? (Some are having charging-issues on Lineage)
    1 point
  8. Having switched to Lineage OS as my daily driver I quickly noticed a couple of apps still don't support landscape namely: Reddit and Microsoft Teams. Thankfully the "Force landscape when keyboard is open" feature from Fx Service still works great, to my surprise. Congrats to self 😁
    1 point
  9. As I read what @3zet writes, the point is if you have some software that stops charging when full (to prolong battery life when constantly connected). Charging ought to be accepted again once below a certain threshold.
    1 point
  10. Yes, looks like your USB-C connection has a hardware problem. Hope you can reach F(x)tec support. Be warned though, it seems they have been rather useless lately. They may also have run out of spare parts. Alternatively maybe you can use someone like @EvilDragon to resolder the USB board.
    1 point
  11. I was asking about the patch being "cosmetical" because in the commit message of the patch it says: (emphasis mine). Actually the patch cannot be directly used in LOS 16.0 because more entries (related to the use of PowerHAL in later releases, I guess) have beeen added meanwhile. Anyhow, I backported the change from '44 -> 2c' to a test build of LOS 16, and that has been running normally on my Pro1 for two days now ... Question is, should there be any (net) effect of this change (e.g. regarding power consumption), or not? 🤔 Yes, that one was clear to me. Thanks for the
    1 point
  12. (lineage-18.1-20210013-nightly-pro1-signed.zip on September 5 security patch installed smoothly using adb sideload and Open_Gapps-arm64-11-pico-20210712) ...But the reintroduced Accessibility / keyboard bug is not (yet) fixed, see above.
    1 point
  13. It's not just cosmetical but I have no idea if you can just take it as it is to for earlier version. Though I would think so. However make sure you take the earlier similar change too as not having both will surely cause the lags we had on that one 18.1 release.
    1 point
  14. Should this fix actually be backported to 17.1 and 16.0, or was it purely "cosmetical"?
    1 point
  15. What about the camera modules? I have asked Fxtec to get a warranty replacement for my camera module (due to focus issue), but I don't feel very confident on getting that module very soon. So I wonder if I could source a replacement module on my own. edit: looks like the Pro1 camera module (IMX363) is not available on Aliexpress. The Pro1-X module (IMX586) is there at least. I couldn't find the IMX363 from Google either, so looks like it is already too old technology? Also I am not sure if it is the actual camera module which needs replacement, or is it the smaller, assisting modul
    1 point
  16. I just recently installed AICP on my Pro1 and, in another thread, I was asked how I went about getting root and Safetynet working, including Google Pay working. It was pretty straight-forward really, but I had to dig around a bit to figure it out. Here are the exact steps, as best I recollect them. This may not be the best or only way, but it worked for me. And thanks to a number of developers/contributors and forum posts which I consulted while figuring out this process. - Wipe phone, fastboot flash Lineage recovery, then adb sideload AICP and NikGapps ZIPs. Checked phone boots into Andr
    1 point
×
×
  • Create New...

Important Information

Terms