Hi
Company's wifi requires client certificate and TLS auth type to connect. On MIUI 8 and my old Galaxy Note 2 (both rooted) it all worked fine til I decided to unlock bootloader and install Resurrection Remix. Device is Mi Max Hydrogen 3Gb / 32Gb
Currently when I try to connect I see following in logcat of my phone (took screenshot so text has OCR errors)
16:52:34.896 2696 2696 I wpa_supplicant wlan0: Associated with 0c:68:03:ae:2a:b1
1652: 34.896 2696 2696 I wpa_supplicant: wlan0: CTRL-EVENTSUBNET-STATUS-UPDATE status 0
16:52:34,896 2696.2696 I wpa_supplicant: wlan0: CTRL-EVENT-EAP-STARTED EAP authentication started
16:52:34.902 1006 2695 I Wifi HAL : Unknown EAPOL message type
16:52:34.902 2696 2696 I wpa_supplicant: wlan0: CTRL-EWENT-EAP-PROPOSED-METHOD vendor=0 method=13
16:52:34.907 2696 2696 I wpa_supplicant: tls_connection_set params: Clearing pending, SSL error: error 0с000067:ASN.1 encoding routines: OPENSSL internal: BAD_OBJECT_HEADER
16:52:34.907 2696 2696 I wpa_supplicant: tls_сonnection_set_params: Clearing pending SSL error: error 0с00009c:ASN.1 encoding routines: OPENSSL internal: NESTED_ASN1_ERROR
16:52:34.920 412 412 E keymaster1_device: Len returned is < 0 len = 0
16:52:34.921 412 412 W export failed: -22
16:52:34.921 2696 2696 W cannot convert pubkey
16:52:34.921. 2696 2696 E wpa_supplicant: ENGINE: cannot load private key with id "USRPKEY_pdas" ASN.1 encoding routines OPENSSL internal:HEADER_TOO_LONG
16:52: 34.921. 2696 2696 I wpa_supplicant: TLS: Failed to initialize engine
Certificates are the same and get installed without any error, after installation files appear in /data/misc/keystore. Tried many attempts, different auth types, copying cert files manually, and so on and so on - this all didn't helped. Is there any workaround or where to look to resolve?
Our helpdesk said hey even can't see any auth attempt on their RADIUS server. This looks reasonable, in log it seems that process fails early, when openssl just tries to read key. Current keystore type is hardware-backed, maybe it fails because phone is unlocked? Is there any method to make it software-only?
I have the same problem (on several devices) . It seems this occurs on most (if not all) 7.1.x based ROMS (not only CM/Lineage based).
Reported that same network ok on LG G3 with RR 5.8.0. I guess it is some issue with hardware keystore. Thus device dependent. And I found no kernel tweak to store certs on file system
Finally I fixed it. Just created new WIFI connection using wpa_cli in command line (adb shell). Certificates could be placed anywhere in the system, and path to certificate files must be set in wpa_supplicant params using wpa_cli. Need to set read permission to these files (chmod) for all users, otherwise wpa_supplicant will not be able to read them. It is great that we have Linux under the green suite of our robot
DimaRUS said:
Finally I fixed it. Just created new WIFI connection using wpa_cli in command line (adb shell). Certificates could be placed anywhere in the system, and path to certificate files must be set in wpa_supplicant params using wpa_cli. Need to set read permission to these files (chmod) for all users, otherwise wpa_supplicant will not be able to read them. It is great that we have Linux under the green suite of our robot
Click to expand...
Click to collapse
May you please share detailed wpa_cli commands? I am facing the exact same problem (i think) with my OP2. As I am not into wpa_cli commands your help would be much appreciated.
DirtyHarrx said:
May you please share detailed wpa_cli commands? I am facing the exact same problem (i think) with my OP2. As I am not into wpa_cli commands your help would be much appreciated.
Click to expand...
Click to collapse
First use add_network command. It will create a new blank network. You can spot it's ID by typing list_networks.
Then use set_network <ID> <param> <value> commands to configure it. I used an example from FreeBSD man page on wpa_supplicant config.
https://www.freebsd.org/cgi/man.cgi...opos=0&manpath=FreeBSD+11.0-RELEASE+and+Ports
network={
ssid="work"
scan_ssid=1
key_mgmt=WPA-EAP
pairwise=CCMP TKIP
group=CCMP TKIP
eap=TLS
identity="[email protected]"
ca_cert="/etc/cert/ca.pem"
client_cert="/etc/cert/user.pem"
private_key="/etc/cert/user.prv"
private_key_passwd="password"
}
It is well documented and params for set_network are the same as in config file. For keys I used only private_key= param and specified .p12 container and it's password. Finally use save_config.
Don't know why but after a few reboots network disappeared. Need to configure again.
Suddenly My Pixel 3 XL fingerprint sensor stopped working and when I tried to unlock with fingerprint, a message says "fingerprint hardware not available" appears at lower bottom of lock screen. The phone does not unlock.
I tried flash without wipe the factory image (April Security patch image, removed -W), cleared the Dalvik cache (with TWRP) and cache (with an APP), still same issue.
Boot into safe mode still not working, I could start enroll a new finger, however, the enrollment will fail after last fingerprint touch. A message just said "cannnot finish add new fingerprint".
I can not also delete the two already enrolled fingerprints from the setting menu. After touch the "trash can" icon, the fingerprint just got gray out but comeback if I exit the settings activity.
I don't think the fingerprint sensor HW is at fault since it still response to fingerprint touch (at least in Safemode)...
Anyone has similar experience or a solution? (I haven't tried a full wipe yet...)
I am on stock April security patch. (rooted with Magisk 19, however, went back to stock boot.img doesn't help)
Note: I do not have Swift installed...
Thanks a lot!
I'd say a wipe is needed
Maybe something got corrupt that resides on the /data partition
virtyx said:
I'd say a wipe is needed
Maybe something got corrupt that resides on the /data partition
Click to expand...
Click to collapse
Yeah.... That's exactly what I did. It did fix the FPS but need to setup from backup again...
Thanks for reply anyway!
lssong99 said:
Suddenly My Pixel 3 XL fingerprint sensor stopped working and when I tried to unlock with fingerprint, a message says "fingerprint hardware not available" appears at lower bottom of lock screen. The phone does not unlock.
I tried flash without wipe the factory image (April Security patch image, removed -W), cleared the Dalvik cache (with TWRP) and cache (with an APP), still same issue.
Boot into safe mode still not working, I could start enroll a new finger, however, the enrollment will fail after last fingerprint touch. A message just said "cannnot finish add new fingerprint".
I can not also delete the two already enrolled fingerprints from the setting menu. After touch the "trash can" icon, the fingerprint just got gray out but comeback if I exit the settings activity.
I don't think the fingerprint sensor HW is at fault since it still response to fingerprint touch (at least in Safemode)...
Anyone has similar experience or a solution? (I haven't tried a full wipe yet...)
I am on stock April security patch. (rooted with Magisk 19, however, went back to stock boot.img doesn't help)
Note: I do not have Swift installed...
Thanks a lot!
Click to expand...
Click to collapse
I have same problem, see here: https://forum.xda-developers.com/pixel-3a/help/fingerprint-hardware-available-t3947280
it's not hardware issue, it's something in data partition that system treat like tampering and disable fingerprint.
Don't try to change Screen Lock, it will break lock completely.
I'm coming from phone without fingerprint so I can live without it if I had to.
If I find some solution I'll let you know.
Pogo said:
I have same problem, see here: https://forum.xda-developers.com/pixel-3a/help/fingerprint-hardware-available-t3947280
it's not hardware issue, it's something in data partition that system treat like tampering and disable fingerprint.
Don't try to change Screen Lock, it will break lock completely.
I'm coming from phone without fingerprint so I can live without it if I had to.
If I find some solution I'll let you know.
Click to expand...
Click to collapse
I gave up and flash ROM and setup everything again.
Pogo said:
I have same problem, see here: https://forum.xda-developers.com/pixel-3a/help/fingerprint-hardware-available-t3947280
it's not hardware issue, it's something in data partition that system treat like tampering and disable fingerprint.
Don't try to change Screen Lock, it will break lock completely.
I'm coming from phone without fingerprint so I can live without it if I had to.
If I find some solution I'll let you know.
Click to expand...
Click to collapse
how about /data/system and those lockscreen and fingerprint .db files ?
what happens if you delete those.
virtyx said:
how about /data/system and those lockscreen and fingerprint .db files ?
what happens if you delete those.
Click to expand...
Click to collapse
Tried that, after restart home screen showed up but it stuck in 'configuring Pixel...' message. I did uninstall before some apps like pixel setup and maybe if I didn't, it will complete. However, maybe it will just create new account. It might be worth to investigate with stock ROM without modifications except rooting. Anyway I have no access to another phone to test.
Before doing that, I have created another account on the phone and fingerprint was working fine on that account.
Hi,
i've a problem with my A2 lite with stock pie rom. I'm using an 32gb SD card (SanDisk ultra). If the phone goes into standby/sleep it unmounts the SD card every time. If i wake up & unlock the phone a short notification is shown and SD card will be mounted again. This happens every time, and in 1 out if 100 cases the mounting fails and SD card is not available. After reboot everything is fine.
How to prevent the unmounting in standby? I've formated the SD within the phone already.
Any ideas?
Hi!
Same issue here, new phone with Android Pie (no idea what happened in Oreo). It's quite annoying as it keeps reindexing the photos in google photos everytime the sd card is re-mounted, draining battery. It's quite annoying. Anyone has an idea on how to fix this?
trash2009 said:
Hi,
i've a problem with my A2 lite with stock pie rom. I'm using an 32gb SD card (SanDisk ultra). If the phone goes into standby/sleep it unmounts the SD card every time. If i wake up & unlock the phone a short notification is shown and SD card will be mounted again. This happens every time, and in 1 out if 100 cases the mounting fails and SD card is not available. After reboot everything is fine.
How to prevent the unmounting in standby? I've formated the SD within the phone already.
Any ideas?
Click to expand...
Click to collapse
Back up your sd card then format it in settings. This problem may occur sometimes if you blacklisted some system apps in adaptive battery. Be creful while you are restricting background apps..
In my case same is happening with two cards, one samsung I was using in my old phone (and was formatted by the A2Lite) and a brand new Sandisk card, also formated by the A2 Lite.
The unmounts seem to be random to me, but having so many pictures it's messing up with google photos all the time (even when if I use internal memory for the camera app, it indexes the sd card with the pictures from my previous phone and merges them with the cloud database) so the problem's still there.
Same issue here, I am using a new Kingston 64gb card formatted with this same phone. Removing apps from battery settings did not help.
I opened this thread last month but did not find any solution
https://forum.xda-developers.com/mi-a2-lite/help/constantly-scanning-sd-card-t3942996
Yes, it looks exactly the same... It's quite annoying to me, as the Google Photos app is working very badly as it keeps reindexing all the time.
I guess it may unmount the sd card in deep sleep to save some battery? I guess that should not be that bad, provided that the apps can keep their indexes instead of going crazy thinking you just added thousands of new elements...
As a workaround, maybe restricting the battery usage while the app is on the background could work for Google Photos, in the sense, preventing it to be actively reindexing?
It is incredibly frustrating. At first I thought it could be caused by an update of Naptime app, so I disabled aggressive doze but to no avail.
I don't think it is because of the sd card. Maybe caused by the June update?
I just had the phone for 5 days and I updated everything at the beginning so no idea. But I agree that's so frustrating.. Was it happening before the June update?
I got this one explicitly for the sd + 2 sims, but if the sd works buggy there's no point.
I tried to restrict the use of the google photos app using the battery in the background as I said, see if that prevents the reindexing (photos app was taking around 5% battery all the time), let's see if it works better now.
Edit: It still reindexes and finds all the pictures even when not allowing background access.
Issue was also there before june update. Changed in the mean time from 32gb sd to a new 64gb sd (formated in the phone) but issue still persits.
Anyone with rooted phone? May its possible to get some details with MatLog (during wakeup & sleep). But I'm not able to do this, cause my phone is not rooted.
trash2009 said:
Anyone with rooted phone? May its possible to get some details with MatLog (during wakeup & sleep). But I'm not able to do this, cause my phone is not rooted.
Click to expand...
Click to collapse
I have root but no SD card inserted.
I found an old one and put it in. Does it need to be adoptable or removable storage?
I have it as a removable one, but I read threads from people having issues as internal one too (I think that in that case it's worse as the phone seems to reboot when it's unmounted).
cancam said:
I have it as a removable one, but I read threads from people having issues as internal one too (I think that in that case it's worse as the phone seems to reboot when it's unmounted).
Click to expand...
Click to collapse
ok. I've got an old 4GB card and I copied my camera pictures onto it. They show up in Google Photos. I can see it scanning in logcat. So far, it hasn't unmounted though. That permanent notification is annoying
hi!
Thanks for the help.
Which permanent notification? I don't have one. I can just see the Sd card icon on the notification tray appear and disappear instantly sometimes when I wake the phone. It doesn't happen always.
But once GPhotos has syncronized and found the images, you'll see that randomly opening google photos will say that he's "getting ready to back up" again, and pictures appear duplicated while it's doing so (I guess it's just rescanning/hashing the pictures to see which ones are already in the cloud).
At least that's what is happening to me when storing the pictures in the sd card and having them set to back up from there.
It wont let me hide this notification. There's an icon and it's on the lock screen too.
In my case I think it appeared after formatting the card and afterwards I discarded it and it never came back (even after reboots). What about the reindexing, does it happen to you?
cancam said:
In my case I think it appeared after formatting the card and afterwards I discarded it and it never came back (even after reboots). What about the reindexing, does it happen to you?
Click to expand...
Click to collapse
Oh wow. Didn't think to just dismiss the notification!
I haven't seen anything odd. Card is not unmounting. I tried a few cards (but all old, class 4).
On my computer I had some notes about the logcat stuff I was doing. I hope to get it written up so that you can maybe get your phone to tell you what it's doing.
Ok, so here's my notes I was making as I looked at the logcat...
You can get logcat by enabling developer mode (not root).
Matlog can work without root (I have root, but deny Matlog root permissions when it asks).
adb logcat from a computer works without root.
These are Linux/MacOS commands. Windows is a little different (no grep). Advanced text editors generally have "find" functionality so you can filter out lines from a file.
First, lets save your logcat to a file. This runs forever (captures the current log and then writes new logs as they happen). After a few seconds, just press Ctrl+C to stop it.
Code:
adb logcat > logcat.txt
This shows various storage events (MOUNTED, EJECTING, UNMOUNTED, REMOVED, CHECKING). The one that signals a hardware issue is BAD_REMOVAL (I only get this if I eject the tray without unmounting first).
Code:
grep StorageNotification: logcat.txt
07-21 09:51:02.510 2199 2199 D StorageNotification: Notifying about public volume: VolumeInfo{public:179,65}:
07-21 09:51:02.510 2199 2199 D StorageNotification: type=PUBLIC diskId=disk:179,64 partGuid= mountFlags=VISIBLE mountUserId=0
07-21 09:51:02.510 2199 2199 D StorageNotification: state=BAD_REMOVAL
07-21 09:51:02.510 2199 2199 D StorageNotification: fsType=vfat fsUuid=48C7-13E5 fsLabel=4GB
07-21 09:51:02.510 2199 2199 D StorageNotification: path=/storage/48C7-13E5 internalPath=/mnt/media_rw/48C7-13E5
This shows when Google Photos was started up due to a change in storage. These should line up with StorageNotification events.
Code:
grep ExternalStorageStateChangeBroadcastReceiver logcat.txt
07-21 09:42:50.209 2032 2048 I ActivityManager: Start proc 19428:com.google.android.apps.photos/u0a133 for broadcast com.google.android.apps.photos/.sdcard.envcache.ExternalStorageStateChangeBroadcastReceiver
I use a Magisk module (debloater) to "remove" Google Photos and then installed it from the store (so that it's a USER app, not a SYSTEM app). This allows me to do things like turning on battery restriction (ie. don't run in the background), which is probably why I see things like this:
Code:
grep -i photos logcat.txt
07-21 10:01:50.392 2032 4479 W ActivityManager: No permission grants found for com.google.android.apps.photos
07-21 10:01:58.104 2032 11555 W ActivityManager: Background start not allowed: service Intent { cmp=com.google.android.apps.photos/com.google.android.libraries.social.mediamonitor.BackgroundThreadNotifierIntentService (has extras) } to com.google.android.apps.photos/com.google.android.libraries.social.mediamonitor.BackgroundThreadNotifierIntentService from pid=20276 uid=10133 pkg=com.google.android.apps.photos startFg?=false
It is in theory possible to use adb commands to uninstall Google Photos and then install from the store to get the same effect without root...
I was doing some general searching and it seems that hardware issues commonly cause this. Things like bent pins, loose sockets, etc. You describe the SD card as unmounting when the phone is off, but is it perhaps that the SD card unmounts when the phone is moved around (which happens to be when it is off)?
In any event, the logcat should be able to show if the OS thinks the card is being removed.
Hi!
Many thanks for this.
I have not used ADB in a while so I'll try to find some time to set it up and try it. I guess I'd need logcat running for a while or it just dumps all the logs in a dmesg-like way?
The hardware issue theory is interesting, though in my case it's a brand new phone (Should be less likely and be a manufacturing defect), and I have seen the notification even when flat on table (just double tapping to see if there are notifications, no movement involved). Also I guess that if it was movement dependent we would see the notification also while in use around and this has never happened to me.
I tried to restrict the background access to google photos and it let me, though I didn't see any difference.
Not sure if @trash2009 can add something on this too?
a1291762 said:
Ok, so here's my notes I was making as I looked at the logcat...
You can get logcat by enabling developer mode (not root).
Matlog can work without root (I have root, but deny Matlog root permissions when it asks).
adb logcat from a computer works without root.
These are Linux/MacOS commands. Windows is a little different (no grep). Advanced text editors generally have "find" functionality so you can filter out lines from a file.
First, lets save your logcat to a file. This runs forever (captures the current log and then writes new logs as they happen). After a few seconds, just press Ctrl+C to stop it.
Code:
adb logcat > logcat.txt
This shows various storage events (MOUNTED, EJECTING, UNMOUNTED, REMOVED, CHECKING). The one that signals a hardware issue is BAD_REMOVAL (I only get this if I eject the tray without unmounting first).
Code:
grep StorageNotification: logcat.txt
07-21 09:51:02.510 2199 2199 D StorageNotification: Notifying about public volume: VolumeInfo{public:179,65}:
07-21 09:51:02.510 2199 2199 D StorageNotification: type=PUBLIC diskId=disk:179,64 partGuid= mountFlags=VISIBLE mountUserId=0
07-21 09:51:02.510 2199 2199 D StorageNotification: state=BAD_REMOVAL
07-21 09:51:02.510 2199 2199 D StorageNotification: fsType=vfat fsUuid=48C7-13E5 fsLabel=4GB
07-21 09:51:02.510 2199 2199 D StorageNotification: path=/storage/48C7-13E5 internalPath=/mnt/media_rw/48C7-13E5
This shows when Google Photos was started up due to a change in storage. These should line up with StorageNotification events.
Code:
grep ExternalStorageStateChangeBroadcastReceiver logcat.txt
07-21 09:42:50.209 2032 2048 I ActivityManager: Start proc 19428:com.google.android.apps.photos/u0a133 for broadcast com.google.android.apps.photos/.sdcard.envcache.ExternalStorageStateChangeBroadcastReceiver
I use a Magisk module (debloater) to "remove" Google Photos and then installed it from the store (so that it's a USER app, not a SYSTEM app). This allows me to do things like turning on battery restriction (ie. don't run in the background), which is probably why I see things like this:
Code:
grep -i photos logcat.txt
07-21 10:01:50.392 2032 4479 W ActivityManager: No permission grants found for com.google.android.apps.photos
07-21 10:01:58.104 2032 11555 W ActivityManager: Background start not allowed: service Intent { cmp=com.google.android.apps.photos/com.google.android.libraries.social.mediamonitor.BackgroundThreadNotifierIntentService (has extras) } to com.google.android.apps.photos/com.google.android.libraries.social.mediamonitor.BackgroundThreadNotifierIntentService from pid=20276 uid=10133 pkg=com.google.android.apps.photos startFg?=false
It is in theory possible to use adb commands to uninstall Google Photos and then install from the store to get the same effect without root...
I was doing some general searching and it seems that hardware issues commonly cause this. Things like bent pins, loose sockets, etc. You describe the SD card as unmounting when the phone is off, but is it perhaps that the SD card unmounts when the phone is moved around (which happens to be when it is off)?
In any event, the logcat should be able to show if the OS thinks the card is being removed.
Click to expand...
Click to collapse
---------- Post added at 03:55 PM ---------- Previous post was at 03:20 PM ----------
I tried it and this is what came out from logcat:
Code:
07-22 15:16:54.931 1895 1895 D StorageNotification: Notifying about public volume: VolumeInfo{public:179,97}:
07-22 15:16:54.931 1895 1895 D StorageNotification: type=PUBLIC diskId=disk:179,96 partGuid= mountFlags=VISIBLE mountUserId=0
07-22 15:16:54.931 1895 1895 D StorageNotification: state=EJECTING
07-22 15:16:54.931 1895 1895 D StorageNotification: fsType=vfat fsUuid=8E9F-1EEB fsLabel=
07-22 15:16:54.931 1895 1895 D StorageNotification: path=/storage/8E9F-1EEB internalPath=/mnt/media_rw/8E9F-1EEB
07-22 15:16:56.403 1895 1895 D StorageNotification: Notifying about public volume: VolumeInfo{public:179,97}:
07-22 15:16:56.403 1895 1895 D StorageNotification: type=PUBLIC diskId=disk:179,96 partGuid= mountFlags=VISIBLE mountUserId=0
07-22 15:16:56.403 1895 1895 D StorageNotification: state=UNMOUNTED
07-22 15:16:56.403 1895 1895 D StorageNotification: fsType=vfat fsUuid=8E9F-1EEB fsLabel=
07-22 15:16:56.403 1895 1895 D StorageNotification: path=/storage/8E9F-1EEB internalPath=/mnt/media_rw/8E9F-1EEB
07-22 15:16:56.404 1895 1895 D StorageNotification: Notifying about public volume: VolumeInfo{public:179,97}:
07-22 15:16:56.404 1895 1895 D StorageNotification: type=PUBLIC diskId=disk:179,96 partGuid= mountFlags=VISIBLE mountUserId=0
07-22 15:16:56.404 1895 1895 D StorageNotification: state=BAD_REMOVAL
07-22 15:16:56.404 1895 1895 D StorageNotification: fsType=vfat fsUuid=8E9F-1EEB fsLabel=
07-22 15:16:56.404 1895 1895 D StorageNotification: path=/storage/8E9F-1EEB internalPath=/mnt/media_rw/8E9F-1EEB
07-22 15:21:23.712 1895 1895 D StorageNotification: Notifying about public volume: VolumeInfo{public:179,65}:
07-22 15:21:23.712 1895 1895 D StorageNotification: type=PUBLIC diskId=disk:179,64 partGuid= mountFlags=VISIBLE mountUserId=0
07-22 15:21:23.712 1895 1895 D StorageNotification: state=UNMOUNTED
07-22 15:21:23.712 1895 1895 D StorageNotification: fsType=null fsUuid=null fsLabel=null
07-22 15:21:23.712 1895 1895 D StorageNotification: path=null internalPath=null
07-22 15:21:23.713 1895 1895 D StorageNotification: Notifying about public volume: VolumeInfo{public:179,65}:
07-22 15:21:23.713 1895 1895 D StorageNotification: type=PUBLIC diskId=disk:179,64 partGuid= mountFlags=VISIBLE mountUserId=0
07-22 15:21:23.713 1895 1895 D StorageNotification: state=CHECKING
07-22 15:21:23.713 1895 1895 D StorageNotification: fsType=null fsUuid=null fsLabel=null
07-22 15:21:23.713 1895 1895 D StorageNotification: path=null internalPath=null
07-22 15:21:24.647 1895 1895 D StorageNotification: Notifying about public volume: VolumeInfo{public:179,65}:
07-22 15:21:24.647 1895 1895 D StorageNotification: type=PUBLIC diskId=disk:179,64 partGuid= mountFlags=VISIBLE mountUserId=0
07-22 15:21:24.647 1895 1895 D StorageNotification: state=MOUNTED
07-22 15:21:24.647 1895 1895 D StorageNotification: fsType=vfat fsUuid=8E9F-1EEB fsLabel=
07-22 15:21:24.647 1895 1895 D StorageNotification: path=/storage/8E9F-1EEB internalPath=/mnt/media_rw/8E9F-1EEB
I tried to leave it for a while see if it happened again but it didn't. Will try to get a new log when I see the notification back.
To me it looks like he is actively ejecting the card, unmounting it to then for some reason show the BAD REMOVAL (though he ejected it) and then mounting it normally.
The
Code:
No permission grants found for com.google.android.apps.photos
message is also appearing a lot on the logs.
cancam said:
I have not used ADB in a while so I'll try to find some time to set it up and try it. I guess I'd need logcat running for a while or it just dumps all the logs in a dmesg-like way?
Click to expand...
Click to collapse
I dumps an in-memory buffer. So its like dmesg but it also continues to dump new data that appears. that's why you have to manually stop it.
Because it's an in-memory buffer, it's not going to go back very far in time.
cancam said:
The hardware issue theory is interesting, though in my case it's a brand new phone (Should be less likely and be a manufacturing defect), and I have seen the notification even when flat on table (just double tapping to see if there are notifications, no movement involved). Also I guess that if it was movement dependent we would see the notification also while in use around and this has never happened to me.
Click to expand...
Click to collapse
Your description does seem to rule out an actual hardware issue...
cancam said:
I tried to restrict the background access to google photos and it let me, though I didn't see any difference.
Click to expand...
Click to collapse
I was hoping that if Google photos wasn't able to run, then you'd at least delay the rescan until you manually launched it.
cancam said:
I tried to leave it for a while see if it happened again but it didn't. Will try to get a new log when I see the notification back.
To me it looks like he is actively ejecting the card, unmounting it to then for some reason show the BAD REMOVAL (though he ejected it) and then mounting it normally.
Click to expand...
Click to collapse
Yes... It does look like the system is trying to unmount the card before it fails. There may be hints in the full log as to what is triggering this. I'll see what a regular unmount looks like. If you can send some of the raw logcat before the unmount event... You can DM me if you don't want to post it publicly.
I did think that maybe newer cards need more power and the phone is unmounting to save power. I tried turning on battery saver on my phone but it didn't make any change for me.
Thank You! I sent you the logcat in a private message, but it still looks like the phone tries to eject the card, then it remounts it.
Hi there,
I'm using an old lineageos 18.1 build.
I'm on hols, I just broke my screen, unfortunately it's not only the glass, it's the main touchscreen.
I'm still having access to the recovery and to the booting device with adb, but the device never finishes booting.
It keeps trying to setup the touch input.
08-12 18:23:26.171 10064 10064 I HidlServiceManagement: getService: Trying again for [email protected]::IGloveMode/default...
08-12 18:23:26.173 3960 10428 W libc : Unable to set property "ctl.interface_start" to "[email protected]::IGloveMode/default": error code: 0x20
Click to expand...
Click to collapse
I'd like to use scrcpy from my computer to use the phone.
Any idea how to disable the touch input device init so the phone starts the main services ?
looks like removing vendor.lineage.touch from /etc/vintf/manifest.xml did the trick.
not very convenient to use a phone without a screen, that will do until I get back home