tdm 2,322 Posted September 26, 2020 Author Share Posted September 26, 2020 (edited) 1 hour ago, internationaltraitor said: so how did they wipe my phone? do you think they were smart enough to re-flash it? or did they enter the passcode with too many wrong attempts and it erased all my data? i got my phone back, it still had lineage on it, doesn't look like they reflashed it to stock android from google with gapps... paid them a 100$ for it... with my screen cracked in the lower right side. That was just a guess. Too bad about the damage but I'm glad you got it back at least. Edited September 26, 2020 by tdm Quote Link to post Share on other sites
internationaltraitor 84 Posted September 26, 2020 Share Posted September 26, 2020 40 minutes ago, tdm said: That was just a guess. Too bad about the damage but I'm glad you got it back at least. thank you, but just wondering how they couldve bypassed the screen lock and wiped my data to get into the phone... must've been through a computer or too many wrong attempts at the screen lock? Quote Link to post Share on other sites
tdm 2,322 Posted September 26, 2020 Author Share Posted September 26, 2020 11 minutes ago, internationaltraitor said: thank you, but just wondering how they couldve bypassed the screen lock and wiped my data to get into the phone... must've been through a computer or too many wrong attempts at the screen lock? Most likely recovery. Quote Link to post Share on other sites
Jordi 72 Posted September 27, 2020 Share Posted September 27, 2020 I still have the problem of distant subjects being out of focus with LOS (landscapes, etc), as others have already reported. I tried with different camera apps, all of them behave the same. Is there a way to track the cause of this or a way to work around the problem? Quote Link to post Share on other sites
tdm 2,322 Posted September 27, 2020 Author Share Posted September 27, 2020 1 minute ago, Jordi said: I still have the problem of distant subjects being out of focus with LOS (landscapes, etc), as others have already reported. I tried with different camera apps, all of them behave the same. Is there a way to track the cause of this or a way to work around the problem? Camera is all closed source blobs between the kernel driver and the camera app. It spews out amazing amounts of debug information, but I have never been able to make sense of most of it. So... probably not, unless we get really lucky. 4 Quote Link to post Share on other sites
tdm 2,322 Posted September 27, 2020 Author Share Posted September 27, 2020 I've gotten the stock keyboard driver to work with Lineage, mostly. I was having an issue generating forward slash on QWERTY, but other FN combinations seem to work. And the any-key-to-wakeup feature is not there. But other than that it seems usable for a test. @DieBruine and whoever else is having keyboard issues, can you please try this? Make sure to backup your existing boot image so you can easily go back to it. http://files.nwwn.com/android/pro1/boot-stock-kbd-1.img I've put the code here just in case anyone wants to look: https://github.com/tdm/android_kernel_fxtec_msm8998/tree/lineage-16.0-kbdtest 6 Quote Link to post Share on other sites
marmistrz 93 Posted September 27, 2020 Share Posted September 27, 2020 (edited) What's the purpose of the changes in the "Add keylogger" commit? https://github.com/tdm/android_kernel_fxtec_msm8998/commit/b03a10e872bc451e7300a1d5ed93204f3c3468b1 Edited September 27, 2020 by marmistrz 2 Quote Link to post Share on other sites
Gigadoc2 54 Posted September 27, 2020 Share Posted September 27, 2020 On 9/22/2020 at 8:05 AM, DieBruine said: I have to say, I am curious now if there is a OpenGapps user with keyboard ghosting issues... 🙄 FWIW, I have no Gapps at all, and as mentioned before experience similar problems. Much more seldom, but it happens. Quote Link to post Share on other sites
tdm 2,322 Posted September 27, 2020 Author Share Posted September 27, 2020 1 hour ago, marmistrz said: What's the purpose of the changes in the "Add keylogger" commit? https://github.com/tdm/android_kernel_fxtec_msm8998/commit/b03a10e872bc451e7300a1d5ed93204f3c3468b1 That was for debugging the keyboard issue, you can read about it a page or two back. 2 Quote Link to post Share on other sites
dicer 36 Posted September 27, 2020 Share Posted September 27, 2020 I just had the case again where the physical keyboard does not react to any key presses anymore. This happens every couple of weeks (more or less) and it basically means I can't type anything anymore. Touchscreen and the OS keep working fine, but nothing from the keyboard. Usually I notice when I get the phone out of my pocket and it doesn't react anymore, but this time it was the first time it happened to me while I was typing. No idea what I hit, but it just stopped working. So I went to my computer and took a adb logcat. I'm not posting the full log here cause it is way to chatty and I don't want to remove all the personal stuff from it (@tdm get in touch if you want the full log). What I see is the following though when I press a button now: 09-27 23:10:05.705 629 629 I chatty : uid=1000(system) /system/bin/surfaceflinger identical 2 lines 09-27 23:10:05.707 629 629 I ConfigStore: android::hardware::configstore::V1_0::ISurfaceFlingerConfigs::hasHDRDisplay retrieved: 0 09-27 23:10:09.206 802 802 W android.hardware.power@1.3-service.pro1: Acquire: called while uninitialized 09-27 23:10:09.207 802 802 W android.hardware.power@1.3-service.pro1: Acquire: called while uninitialized 09-27 23:10:09.207 1255 1532 E LightsService: Light requested not available on this device. 2 09-27 23:10:09.264 800 800 I LightService: setKeyboardBacklightLocked: mSliderOpen=true mLcdBacklightOn=true 09-27 23:10:09.298 800 800 I LightService: setKeyboardBacklightLocked: mSliderOpen=true mLcdBacklightOn=true 09-27 23:10:09.327 802 802 W android.hardware.power@1.3-service.pro1: Acquire: called while uninitialized 09-27 23:10:09.328 802 802 W android.hardware.power@1.3-service.pro1: Acquire: called while uninitialized 09-27 23:10:09.331 800 800 I LightService: setKeyboardBacklightLocked: mSliderOpen=true mLcdBacklightOn=true 09-27 23:10:09.431 800 800 I chatty : uid=1000(system) light@2.0-servi identical 3 lines 09-27 23:10:09.466 800 800 I LightService: setKeyboardBacklightLocked: mSliderOpen=true mLcdBacklightOn=true 09-27 23:10:10.697 2107 2107 D ServiceStateProvider: subId=1 I didn't look at the watch when it happened, but the LightsService error did not happen all day until right around the time it stopped working. That's how I assume it stopped working around these log entries: 09-27 22:50:47.457 808 2204 I WifiHAL : event received NL80211_CMD_VENDOR, vendor_id = 0x1374, subcmd = 0xd 09-27 22:50:49.473 808 2204 I WifiHAL : event received NL80211_CMD_VENDOR, vendor_id = 0x1374, subcmd = 0xd 09-27 22:50:49.684 629 629 I chatty : uid=1000(system) /system/bin/surfaceflinger expire 60 lines 09-27 22:50:49.758 1255 16010 I ActivityManager: Killing 9669:com.android.exchange/u0a69 (adj 906): empty #17 09-27 22:50:49.761 1255 1326 W libprocessgroup: kill(-9669, 9) failed: No such process 09-27 22:50:49.781 4929 4929 D GmsGcmRegisterSvc: onBind: Intent { act=com.google.android.c2dm.intent.REGISTER pkg=com.google.android.gms } 09-27 22:50:49.795 4929 4929 D GmsGcmRegisterHdl: handleMessage: package=org.mozilla.firefox what=1 id=3 09-27 22:50:49.809 1255 1326 W libprocessgroup: kill(-9669, 9) failed: No such process 09-27 22:50:49.843 10304 10325 E FirebaseInstanceId: Token retrieval failed: SERVICE_NOT_AVAILABLE 09-27 22:50:49.848 1255 1326 W libprocessgroup: kill(-9669, 9) failed: No such process 09-27 22:50:49.869 751 751 I Zygote : Process 9669 exited due to signal (9) 09-27 22:50:49.888 1255 1326 W libprocessgroup: kill(-9669, 9) failed: No such process 09-27 22:50:49.888 1255 1326 I libprocessgroup: Successfully killed process cgroup uid 10069 pid 9669 in 128ms 09-27 22:50:50.946 1255 16010 E LightsService: Light requested not available on this device. 2 09-27 22:50:51.482 808 2204 I WifiHAL : event received NL80211_CMD_VENDOR, vendor_id = 0x1374, subcmd = 0xd 09-27 22:50:53.483 808 2204 I WifiHAL : event received NL80211_CMD_VENDOR, vendor_id = 0x1374, subcmd = 0xd 09-27 22:50:55.053 1255 1532 E LightsService: Light requested not available on this device. 2 09-27 22:50:55.491 808 2204 I WifiHAL : event received NL80211_CMD_VENDOR, vendor_id = 0x1374, subcmd = 0xd 09-27 22:50:55.588 802 802 I chatty : uid=1000(system) power@1.3-servi expire 12 lines 09-27 22:50:57.491 808 2204 I WifiHAL : event received NL80211_CMD_VENDOR, vendor_id = 0x1374, subcmd = 0xd 09-27 22:50:59.497 808 2204 I WifiHAL : event received NL80211_CMD_VENDOR, vendor_id = 0x1374, subcmd = 0xd 09-27 22:51:01.510 808 2204 I WifiHAL : event received NL80211_CMD_VENDOR, vendor_id = 0x1374, subcmd = 0xd 09-27 22:51:01.779 629 629 I chatty : uid=1000(system) /system/bin/surfaceflinger expire 75 lines 09-27 22:51:03.515 808 2204 I WifiHAL : event received NL80211_CMD_VENDOR, vendor_id = 0x1374, subcmd = 0xd 09-27 22:51:05.143 1255 16010 E LightsService: Light requested not available on this device. 2 The keyboard is not completely gone though! I can still press Caps and the little LED will light up. This is what I get in the log when pressing the Caps button: 09-27 23:17:18.772 629 629 I chatty : uid=1000(system) /system/bin/surfaceflinger identical 10 lines 09-27 23:17:18.773 629 629 I ConfigStore: android::hardware::configstore::V1_0::ISurfaceFlingerConfigs::hasHDRDisplay retrieved: 0 09-27 23:17:18.992 802 802 W android.hardware.power@1.3-service.pro1: Acquire: called while uninitialized 09-27 23:17:18.993 1255 1532 E LightsService: Light requested not available on this device. 2 09-27 23:17:18.993 802 802 W android.hardware.power@1.3-service.pro1: Acquire: called while uninitialized 09-27 23:17:19.197 802 802 I chatty : uid=1000(system) power@1.3-servi identical 1 line 09-27 23:17:19.198 802 802 W android.hardware.power@1.3-service.pro1: Acquire: called while uninitialized 09-27 23:17:19.271 629 629 I ConfigStore: android::hardware::configstore::V1_0::ISurfaceFlingerConfigs::hasHDRDisplay retrieved: 0 09-27 23:17:21.299 629 629 I chatty : uid=1000(system) /system/bin/surfaceflinger identical 10 lines 09-27 23:17:21.300 629 629 I ConfigStore: android::hardware::configstore::V1_0::ISurfaceFlingerConfigs::hasHDRDisplay retrieved: 0 09-27 23:17:21.469 802 802 W android.hardware.power@1.3-service.pro1: Acquire: called while uninitialized 09-27 23:17:21.588 802 802 I chatty : uid=1000(system) power@1.3-servi identical 2 lines 09-27 23:17:21.590 802 802 W android.hardware.power@1.3-service.pro1: Acquire: called while uninitialized 09-27 23:17:21.811 629 629 I ConfigStore: android::hardware::configstore::V1_0::ISurfaceFlingerConfigs::hasHDRDisplay retrieved: 0 Now the weird part: While I was debugging this, the keyboard just started working again! I guess it was hanging (software wise)? No idea why though... I still get the LightsService Error and this when I press a key now (which works): 09-27 23:24:52.927 629 629 I chatty : uid=1000(system) /system/bin/surfaceflinger identical 14 lines 09-27 23:24:52.928 629 629 I ConfigStore: android::hardware::configstore::V1_0::ISurfaceFlingerConfigs::hasHDRDisplay retrieved: 0 09-27 23:24:53.223 802 802 W android.hardware.power@1.3-service.pro1: Acquire: called while uninitialized 09-27 23:24:53.348 802 802 I chatty : uid=1000(system) power@1.3-servi identical 2 lines 09-27 23:24:53.349 802 802 W android.hardware.power@1.3-service.pro1: Acquire: called while uninitialized 09-27 23:24:53.354 629 629 I ConfigStore: android::hardware::configstore::V1_0::ISurfaceFlingerConfigs::hasHDRDisplay retrieved: 0 No idea what to make of this, but maybe one of the devs can make sense of this. 2 Quote Link to post Share on other sites
internationaltraitor 84 Posted September 27, 2020 Share Posted September 27, 2020 sorry, can i reflash the phone with my up to date lineage, with the same up to date lineage ? i want to completely wipe the phone ,, my battery life is unbearable after i got it back. do i just need to do the same exact steps in the lineageOS directions ? Quote Link to post Share on other sites
DieBruine 397 Posted September 28, 2020 Share Posted September 28, 2020 15 hours ago, tdm said: @DieBruine and whoever else is having keyboard issues, can you please try this? Make sure to backup your existing boot image so you can easily go back to it. http://files.nwwn.com/android/pro1/boot-stock-kbd-1.img My phone is back @ FxTec. But I will flash the other two still in this house this evening and let you know the results tomorrow or the day after that. 1 Quote Link to post Share on other sites
EskeRahn 5,433 Posted September 28, 2020 Share Posted September 28, 2020 (lineage-16.0-20200928-nightly-pro1-signed.zip installed smoothly, with and without addonsu) 1 Quote Link to post Share on other sites
Wheeljack 212 Posted September 28, 2020 Share Posted September 28, 2020 15 hours ago, tdm said: @DieBruine and whoever else is having keyboard issues, can you please try this? Make sure to backup your existing boot image so you can easily go back to it. I tried it for 10 minutes and it looked responsive to me but I couldn't figure out how to set it to QWERTZ so I went back to the Lineage bootloader. 10 hours ago, dicer said: I just had the case again where the physical keyboard does not react to any key presses anymore. This happens every couple of weeks (more or less) and it basically means I can't type anything anymore. Touchscreen and the OS keep working fine, but nothing from the keyboard. In my case Alt still gives me the emoji popup when that happens. 1 Quote Link to post Share on other sites
PokeParadox 62 Posted September 28, 2020 Share Posted September 28, 2020 If I install Lineage, can I still use fingerprint reader and GooglePay? Quote Link to post Share on other sites
dicer 36 Posted September 28, 2020 Share Posted September 28, 2020 21 hours ago, Jordi said: I still have the problem of distant subjects being out of focus with LOS (landscapes, etc), as others have already reported. I tried with different camera apps, all of them behave the same. I also seem to have this problem. Plus random times I can't seem to be able to focus at all. A reboot fixes the latter though. @Jordi Did you test this on stock? I am beginning to think this might be a hardware fault. 1 Quote Link to post Share on other sites
tdm 2,322 Posted September 28, 2020 Author Share Posted September 28, 2020 6 hours ago, Wheeljack said: I tried it for 10 minutes and it looked responsive to me but I couldn't figure out how to set it to QWERTZ so I went back to the Lineage bootloader. In my case Alt still gives me the emoji popup when that happens. I may have missed something for the qwertz setting. I'll check. Quote Link to post Share on other sites
tdm 2,322 Posted September 28, 2020 Author Share Posted September 28, 2020 3 hours ago, PokeParadox said: If I install Lineage, can I still use fingerprint reader and GooglePay? Certainly the fingerprint reader works. Google Pay will not work by default. Other users you can make it work by using magisk hide. But I cannot help with that, I don't use magisk. 1 3 Quote Link to post Share on other sites
DieBruine 397 Posted September 28, 2020 Share Posted September 28, 2020 (edited) 23 hours ago, Jordi said: I still have the problem of distant subjects being out of focus with LOS (landscapes, etc), as others have already reported. I tried with different camera apps, all of them behave the same. Is there a way to track the cause of this or a way to work around the problem? 1 hour ago, dicer said: I also seem to have this problem. Plus random times I can't seem to be able to focus at all. A reboot fixes the latter though. @Jordi Did you test this on stock? I am beginning to think this might be a hardware fault. This is not due to a hardware defect. At least, not in general. The issue in my case is the fact that the software chooses an aperture of f/1.8. An this seems to be almost like a default. For those who don't know what this does, it limits the depth of field. If you work that out in distance, only those objects that are between 2.5m~2.8m/7.5f-7.9f will be in sharp focus. This is just an example. Focal length and sensor size matter a lot. But in general, f/1.8 limits DoF a lot! That being said, I have an example which makes me think there is a hardware issue with the lens. This picture was taken with an aperture of f/1.8. If you look closely you see that the left 40% of the picture is sharp all the way. The right 50~60% is not. Take a look at the stones on the ground. Weird huh!? I just hope I get a new or 100% refurbished phone back. BTW, pictures were taken with LoS. And @tdm I flashed my son's phone. The Ms will be next this evening :). Edited September 28, 2020 by DieBruine 1 Quote Link to post Share on other sites
Jordi 72 Posted September 28, 2020 Share Posted September 28, 2020 2 hours ago, dicer said: @Jordi Did you test this on stock? I am beginning to think this might be a hardware fault. Yes I did, no problems with stock firmware. Quote Link to post Share on other sites
raymo 177 Posted September 29, 2020 Share Posted September 29, 2020 Quote ...and whoever else is having keyboard issues, can you please try this? Make sure to backup your existing boot image so you can easily go back to it. http://files.nwwn.com/android/pro1/boot-stock-kbd-1.img ok if I understand : adb and fastboot flash boot-stock-kbd-1.img And then ? How can I backup actual boot image ? sorry and thanks... Quote Link to post Share on other sites
Wheeljack 212 Posted September 30, 2020 Share Posted September 30, 2020 15 hours ago, raymo said: How can I backup actual boot image ? Just get the boot image from here. (Just make sure it's the one matching your currently installed version) 1 Quote Link to post Share on other sites
daniel.schaaaf 177 Posted October 1, 2020 Share Posted October 1, 2020 On 9/28/2020 at 5:01 PM, DieBruine said: That being said, I have an example which makes me think there is a hardware issue with the lens. This picture was taken with an aperture of f/1.8. If you look closely you see that the left 40% of the picture is sharp all the way. The right 50~60% is not. Take a look at the stones on the ground. Weird huh!? @tdm Is you lens clean? Also under the lens protector? I have condensation fogging the lens from carrying the phone in the pocket of my trousers :-( I will remove the lens protection when I find the time, and see what can be done against moisture. The Pro1 is my first phone that has trouble with moisture getting into the camera compartment ... Quote Link to post Share on other sites
DieBruine 397 Posted October 1, 2020 Share Posted October 1, 2020 Nope, it was crystal clear. Do not let get any amount of moisture get near the Pro1. It is very prone to damage-by-moisture. I think my lenses were either not aligned properly or just shifted slightly. That in combination with the f/1.8 aperture. Of which I am not sure if it's a LoS or general algorithm issue. Quote Link to post Share on other sites
daniel.schaaaf 177 Posted October 3, 2020 Share Posted October 3, 2020 @tdm Would you be interested in enabling write access to the external SD-card? Apparently this can be done easily by editing PublicVolume.cpp: https://www.reddit.com/r/LineageOS/comments/gr8ubl/how_about_patching_in_sdcard_write_access/ There are quite a few apps for power-users that would benefit greatly from write access. Quote Link to post Share on other sites
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.