[Pro¹ X - backup, restore and repair device specific partitions]

Which Key Attestation app do you mean?

There is:

https://github.com/vvb2060/KeyAttestation

https://play.google.com/store/apps/details?id=io.github.vvb2060.keyattestation

and so on.

[Pro1-X with Ubuntu Touch]

On 8/18/2022 at 4:41 AM, EskeRahn said:

We have just yesterday learned that this is not enough....

Care to elaborate? Can you please share a link to any discussions about this?

[Pro1x - really poor connectivity to both wifi and cellular.]

This is the phone that made me adjust my hostapd configuration to get HT40 and change to an unused channel.  Also it stopped disconnecting after I disabled doze on it. It loses some battery life but it's worth it to me to not lose connectivity. I see log messages with doze enabled:

08-11 11:18:10.517   594   600 E [email protected]: Error opening kernel wakelock stats for: wakeup4: Permission denied
08-11 11:18:10.512   594   594 W Binder:594_1: type=1400 audit(0.0:4587): avc: denied { read } for name="wakeup4" dev="sysfs" ino=34968 scontext=u:r:system_suspend:s0 tcontext=u:object_r:sysfs:s0 tclass=dir permissive=0
08-11 11:18:10.516   594   594 W Binder:594_1: type=1400 audit(0.0:4588): avc: denied { read } for name="wakeup56" dev="sysfs" ino=57580 scontext=u:r:system_suspend:s0 tcontext=u:object_r:sysfs:s0 tclass=dir permissive=0
08-11 11:18:10.516   594   594 W Binder:594_1: type=1400 audit(0.0:4589): avc: denied { read } for name="wakeup46" dev="sysfs" ino=57208 scontext=u:r:system_suspend:s0 tcontext=u:object_r:sysfs:s0 tclass=dir permissive=0
08-11 11:18:10.516   594   594 W Binder:594_1: type=1400 audit(0.0:4590): avc: denied { read } for name="wakeup2" dev="sysfs" ino=30725 scontext=u:r:system_suspend:s0 tcontext=u:object_r:sysfs:s0 tclass=dir permissive=0
08-11 11:18:10.519   594   600 E [email protected]: Error opening kernel wakelock stats for: wakeup56: Permission denied
08-11 11:18:10.520   594   600 E [email protected]: Error opening kernel wakelock stats for: wakeup46: Permission denied

 

[Screen freeze or black out-- this problem is strange!]

A day has past and my phone did not get stuck with the screen blank now that doze has been turned off as a work-around.

[Screen freeze or black out-- this problem is strange!]

I'm seeing log messages like these. There's about 122 of them since I booted the Pro1-X.

08-11 08:54:32.294   594   600 E [email protected]: Error opening kernel wakelock stats for: wakeup11: Permission denied
08-11 08:54:47.232   240   240 W kworker/u16:2: type=1400 audit(0.0:2513): avc: denied { kill } for capability=5 scontext=u:r:kernel:s0 tcontext=u:r:kernel:s0 tclass=capability permissive=0
08-11 08:54:47.440   594   594 W Binder:594_1: type=1400 audit(0.0:2514): avc: denied { read } for name="wakeup48" dev="sysfs" ino=57280 scontext=u:r:system_suspend:s0 tcontext=u:object_r:sysfs:s0 tclass=dir permissive=0
08-11 08:54:47.440   594   594 W Binder:594_1: type=1400 audit(0.0:2515): avc: denied { read } for name="wakeup4" dev="sysfs" ino=34968 scontext=u:r:system_suspend:s0 tcontext=u:object_r:sysfs:s0 tclass=dir permissive=0

There is only one app with a waitlock at this time.

$ adb shell dumpsys power | grep -i wake_lock
    no_cached_wake_locks=true
  DOZE_WAKE_LOCK                 'DreamManagerService' ACQ=-9m5s596ms (uid=1000 pid=1547)

I turned off doze. It's still too soon to tell but the "stuck blank screen" issue has not happened yet.

$ adb shell dumpsys deviceidle disable
Deep idle mode disabled
Light idle mode disabled