Jump to content

marmistrz

Members
 View Profile  See their activity

  • Content Count

    135

  • Joined

  • Last visited

  • Days Won

    2

 Content Type 

Posts posted by marmistrz

    Flaky GPS, Pro1

    in Support

    Posted

    On 12/22/2023 at 8:37 AM, SchattengestaIt said:

    So it's been a day aaand... something worked!

    I've edited the gps.conf file a few times but later ended up using the old file I've had before. After every change I restarted and now I've waited a few hours to let the phone reload agps.

    Somehow it works now and I finally get a GPS fix again!

    The accuracy varies between 10 and 30 metres but it seems to be enough for Google maps. I'll continue experimenting a bit with the settings but I am very thankful for you guys for helping me so far. Especially @EskeRahn was a huge help with his almighty forum knowledge.

    Screenshot_20231222-082133_GPS_Test.png

    In the end, what changes did you do? I remember doing gps.conf changes back in the day but they turned out to be placebo ;/

    Camera always detected as in use. Pro1 on LineageOS 18.1

    in General Discussion

    Posted · Edited by EskeRahn
    Clarifyied title.

    I'm currently running LineageOS 18.1 on my Pro1 (19.1 has always had broken dual SIM support). Camera stopped working for me about a month ago. The flashlight applet is grayed out and says "Camera in use". The LineageOS camera only uses the front-facing camera. GCam crashes. There are some camera-related errors during boot: 

    05-01 06:29:44.568     0     0 I iommu   : Adding device soc:qcom,cam_smmu:msm_cam_smmu_cb1 to group 14
05-01 06:29:44.569     0     0 E CAM-SMMU cam_smmu_populate_sids: 2331 __debug cnt = 8, cb->name: :vfe sid [0] = 3072
05-01 06:29:44.569     0     0 E         : ,
05-01 06:29:44.569     0     0 E CAM-SMMU cam_smmu_populate_sids: 2331 __debug cnt = 8, cb->name: :vfe sid [1] = 3073
05-01 06:29:44.569     0     0 E ,CAM-SMMU cam_smmu_populate_sids: 2331 __debug cnt = 8, cb->name: :vfe sid [2] = 3074
05-01 06:29:44.569     0     0 E         : ,
05-01 06:29:44.569     0     0 E CAM-SMMU cam_smmu_populate_sids: 2331 __debug cnt = 8, cb->name: :vfe sid [3] = 3075
05-01 06:29:44.569     0     0 E         : ,
05-01 06:29:44.569     0     0 I iommu   : Adding device soc:qcom,cam_smmu:msm_cam_smmu_cb2 to group 15
05-01 06:29:44.569     0     0 E CAM-SMMU cam_smmu_populate_sids: 2331 __debug cnt = 2, cb->name: :cpp sid [0] = 2560
05-01 06:29:44.569     0     0 E         : ,
05-01 06:29:44.569     0     0 I iommu   : Adding device soc:qcom,cam_smmu:msm_cam_smmu_cb3 to group 16
05-01 06:29:44.569     0     0 E CAM-SMMU cam_smmu_populate_sids: 2331 __debug cnt = 2, cb->name: :camera_fd sid [0] = 2561
05-01 06:29:44.569     0     0 E         : ,
05-01 06:29:44.569     0     0 I iommu   : Adding device soc:qcom,cam_smmu:msm_cam_smmu_cb4 to group 17
05-01 06:29:44.569     0     0 E CAM-SMMU cam_smmu_populate_sids: 2331 __debug cnt = 2, cb->name: :jpeg_enc0 sid [0] = 2048
05-01 06:29:44.569     0     0 E         : ,
05-01 06:29:44.569     0     0 I iommu   : Adding device soc:qcom,cam_smmu:msm_cam_smmu_cb5 to group 18
05-01 06:29:44.569     0     0 E CAM-SMMU cam_smmu_populate_sids: 2331 __debug cnt = 2, cb->name: :jpeg_dma sid [0] = 2049
05-01 06:29:44.569     0     0 E         : ,
05-01 06:29:44.576     0     0 E CAM-SOC msm_camera_get_reg_base: 864 err: mem resource csiphy_clk_mux not found
05-01 06:29:44.576     0     0 E csiphy_probe: no mem resource?
05-01 06:29:44.577     0     0 E CAM-SOC msm_camera_get_reg_base: 864 err: mem resource csiphy_clk_mux not found
05-01 06:29:44.577     0     0 E csiphy_probe: no mem resource?
05-01 06:29:44.578     0     0 E CAM-SOC msm_camera_get_reg_base: 864 err: mem resource csiphy_clk_mux not found
05-01 06:29:44.578     0     0 E csiphy_probe: no mem resource?

    and also 

    05-01 06:29:56.106   800   800 I mm-camera: < INFO> 440: init: memleak tracer not attached
05-01 06:29:56.110   800   800 I mm-camera: <SENSOR>< INFO> 387: eebin_read: failed!
05-01 06:29:56.110   800   800 I mm-camera: <SENSOR>< INFO> 387: eebin_read: failed!
05-01 06:29:56.110   800   800 I mm-camera: <SENSOR>< INFO> 589: sensor_init_probe: opening: /dev/v4l-subdev14
05-01 06:29:56.110   800   800 I mm-camera: <SENSOR>< INFO> 598: sensor_init_probe: failed: to probe eeprom bin sensors (non-fatal)
05-01 06:29:56.117   800   800 E mm-camera: <SENSOR><ERROR> 362: sensor_load_library: dlopen of libmmcamera_s5k3p9sx.so failed NULL handle
05-01 06:29:56.117   800   800 E mm-camera: <SENSOR><ERROR> 193: sensor_probe: sensor_load_library failed (non-fatal). Trying to load binary
05-01 06:29:56.117   800   800 E mm-camera: <SENSOR><ERROR> 301: sensor_load_binary: failed NULL pointer detected fp
05-01 06:29:56.117   800   800 E mm-camera: <SENSOR><ERROR> 196: sensor_probe: sensor_load_binary failed
05-01 06:29:56.117   800   800 I mm-camera: <SENSOR>< INFO> 399: sensor_init_xml_probe: failed: to probe s5k3p9sx
05-01 06:29:56.123   800   800 I mm-camera: <SENSOR>< INFO> 312: sensor_sdk_util_get_i2c_freq_mode: Invalid i2c_freq_mode = 4
05-01 06:29:56.123   800   800 E mm-camera: <SENSOR><ERROR> 457: translate_sensor_slave_info: Invalid position = 0
05-01 06:29:56.382   800   800 I mm-camera: <SENSOR>< INFO> 246: sensor_probe: [imx363]CFG_SINIT_PROBE failed
05-01 06:29:56.382   800   800 I mm-camera: <SENSOR>< INFO> 399: sensor_init_xml_probe: failed: to probe imx363
05-01 06:29:56.384   800   800 E mm-camera: <SENSOR><ERROR> 362: sensor_load_library: dlopen of libmmcamera_s5k5e9yu05.so failed NULL handle
05-01 06:29:56.384   800   800 E mm-camera: <SENSOR><ERROR> 193: sensor_probe: sensor_load_library failed (non-fatal). Trying to load binary
05-01 06:29:56.384   800   800 E mm-camera: <SENSOR><ERROR> 301: sensor_load_binary: failed NULL pointer detected fp
05-01 06:29:56.384   800   800 E mm-camera: <SENSOR><ERROR> 196: sensor_probe: sensor_load_binary failed
05-01 06:29:56.384   800   800 I mm-camera: <SENSOR>< INFO> 399: sensor_init_xml_probe: failed: to probe s5k5e9yu05
05-01 06:29:56.642   800   800 I mm-camera: <SENSOR>< INFO> 312: sensor_sdk_util_get_i2c_freq_mode: Invalid i2c_freq_mode = 4
05-01 06:29:57.182   800   800 I mm-camera: <SENSOR>< INFO> 312: sensor_sdk_util_get_i2c_freq_mode: Invalid i2c_freq_mode = 4
05-01 06:29:57.952   800   800 I mm-camera: <SENSOR>< INFO> 246: sensor_probe: [s5k4h7]CFG_SINIT_PROBE failed
05-01 06:29:57.952   800   800 I mm-camera: <SENSOR>< INFO> 399: sensor_init_xml_probe: failed: to probe s5k4h7
05-01 06:29:58.042   800   800 I mm-camera: <SENSOR>< INFO> 312: sensor_sdk_util_get_i2c_freq_mode: Invalid i2c_freq_mode = 4

    Here's the logcat, grepped by camera: https://dpaste.com/8YKUD972C

    Has anyone encountered such a problem before?

    I'm obviously going to try a full reflash so as to rule out a software issue, so: is there any way to make a full-device backup of the LineageOS install that could be easily restored? Normally, one uses TWRP to do it, but AFAIK TWRP for the Pro1 is only compatible with SFOS.

    3D printed case

    in General Discussion

    Posted · Edited by marmistrz

    12 hours ago, belletrist said:

    I have already included a model with the fxtec and sfos logos.

    I'm from Aus, I'll send you a pm.

    What do you think about providing two variants of the print, one with the headphone jack covered and the other one uncovered? For me the availability of the headphone jack is quite important, even if it comes at the expense of the grip.'

    /edit: ah, I didn't realize that the new design isn't a a TPU-first design. This might change a lot. I really love the TPU case

    F(x)tec Pro1 screen suddenly died

    in General Discussion

    Posted

    19 hours ago, Casey said:

    We can ship a new Pro1 screen to you as soon as we can confirm your order ID and address. The cost would be £149 + shipping fee (I can simulate a shipping fee for you if you can provide your address).

    For the return/repair process, after we received your Pro1, it should take no more than a few working days to get everything sorted (depending on our backlog), then an extra few days for shipping back to you. We don't charge you for looking into the device, but if parts are needed for replacement, we will quote you. In this case, I speculate the problem could either be caused by a broken screen and/or the flat ribbon cable connecting the screen. The cost for each part would be: £149 (screen), £30 (flat ribbon cable), and then both way shipment fees. 

    If you'd like to move forward with either option, drop us an email at [email protected] and optionally post/DM your ticket number here (for fast-tracking), I'll get back to you asap. 

    Thank you very much, it's awesome! I sent the ticket number by DM.

    • Thanks 1

    F(x)tec Pro1 screen suddenly died

    in General Discussion

    Posted

    22 hours ago, Casey said:

    We have spare Pro1 screen in our UK office which we can ship to you directly. But I can't promise this will fix your issue as we don't know the root cause of this. If you'd like, you can submit a ticket to [email protected] and we can initiate a return/repair process to have a look?

    Thank you very much for the reply! What would be the approximate cost of both options?

    F(x)tec Pro1 screen suddenly died

    in General Discussion

    Posted · Edited by marmistrz

    I've happily used my Pro1 for over 2 years. I can't help dropping my devices, but the 3D-printed TPU case saved the screen from cracking throughout its life. However, a week ago, the screen suddenly stopped working, with no clear cause.

    A week earlier days ago I noticed a weird issue: the screen would turn off while it was being touched at one place (the place was around 50% vertically, 25% horizontally counted from the left). When I removed my finger, it would turn itself on again. I supposed some weird driver bug, so I rebooted and the problem went away.

    That day, it was a rainy day and I was on a long walk. I took my phone from my pocket. I tried unlocking it, but instead of the lock screen, I just saw some black, red and white bars. (red and white covered <30% of the screen, I don't remember if the whole screen was on). After a few tries, the screen stopped displaying anything. The digitizer still works properly, I can access the phone using MHL (USB-C/HDMI).

    Reattaching the LCD flex cables doesn't fix anything.  Does this sound like a short circuit in the screen panel? Is there anything else I can do other than to replace the screen (given F(x)tec's recent shipping troubles, this might take a very long time to actually get the screen)

    LineageOS 19.1 Official Release for Pro1

    in Pro1 - Thoughts & questions

    Posted

    20 minutes ago, mosen said:

    Ah, ok, that sounds VERY familiar to the situation on SailfishOS.
    The problem on SailfishOS lies in the AGPS support. Mozilla at some point 3 years ago changed the license model for its MLS. Which ment that SailfishOS users lost celltower based location assitance via Mozilla Location Services.
    A work around attempt on SialfishOS that never really worked was to manually feed the offline availabe MLS files.
    But since we are on Android, maybe there is a way to enable the google location service or whatever makes stock android get gps fix instantly?

    FWIW, the OnePlus 3 that I'm using for GPS is running LineageOS too, so it's not an issue with LineageOS (i.e. the common base) per se

    • Like 1
    • Thanks 1

    LineageOS 19.1 Official Release for Pro1

    in Pro1 - Thoughts & questions

    Posted

    Just now, mosen said:

    @marmistrzI don't think it is necessary even. I was just not expecting that the first fix would take 30 minutes.
    I tried multiple times around 15 and 20 minutes, then starting to look for a possible solution -> gps.conf.
    But as soon i got a "first time ever fix" after like 30 minutes and then rebooted, after reboot i had instant fix.
    This behavior now persists, i get a fix within 30 seconds constantly and i think the issue is explained and solved.
    Thank you!

    For me the "next fix" usually works. But sometimes it doesn't and getting a fix takes tens of minutes. This is why I carry my old OnePlus 3 whenever GPS is crucial... 😞

    It's been that way ever since, I guess it's yet another bug that will never get resolved.

    • Thanks 1
    • Sad 1

    LineageOS 19.1 Official Release for Pro1

    in Pro1 - Thoughts & questions

    Posted

    I tried to upstream this "fix" for gps fixes and it turned out it never really worked for me.

    2 hours ago, mosen said:

    Hey all!
    Trying LOS 19.1 as my first LOS ever on Pro¹. Install went fine including MindTheGapps-12.1.0-arm64-20220605_112439. Flashed to stock android beforehand to start from a clean state.

    Two problems i am facing:

    1.[SOLVED, after some reboots i suddenly got fix without updating gps.conf]
    I read "GPS fix taking a long time" is due to /vendor/etc/gps.conf. I downloaded a gps.conf that is fitting for my region and should speed up sat-fix. But pushing the file using adb root and adb push gps.conf /vendor/etc/ results in "read only device".
    I figure adb root is not enough and i need magisk root for that?

    2. Trying to root via magisk went like following:
    Magisk patched the stock boot.img which was flashed before installing LOS. The one contained in ext4_QX1000_user_20200825231445_dd49dd0dd1.7z.
    But trying to flash the magisk_patched-25200_ceLFW.img back using fastboot flash boot magisk_patched-25200_ceLFW.img always results in
    fastboot: error: boot partition is smaller than boot image on second try, after fb complains about the slot on first try. Also tried to assign boot_b since that is active according to fastboot getvar all.

    image.png

    RE 1. The GPS fix now came on right after a reboot so i figure no need anymore for the gps.conf copy to /vendor/etc/. But 2. is still a mystery to me 😛

     

    • Thanks 1

    LineageOS 19.1 Official Release for Pro1

    in Pro1 - Thoughts & questions

    Posted

    On 7/9/2022 at 12:26 PM, Wheeljack said:

    Are your SIMs pin-protected? Like I wrote in a previous post my two SIMs act a little different after boot. When I proceed to enter both pins right when the phone asks they're both active right away. If I let the screen timeout before that, the phone gets stuck until I manually press the  power button twice.

    I also have deactivated WiFi calling for SIM1. SIM1 is my default one for outgoing calls but when I remotely initiate a call using my helmet's hands-free it would go over SIM2 - it finally started using SIM1 when WiFi calling was off (no idea if my provider supports this anyway).

    So yeah... still some weird issues with two SIMs.

    No, no pin-protection

×
×
  • Create New...

Important Information

Terms

  I accept