Discussion and testing on features and known&potential issues

[ddark-il 100]

CTS profile match: false

Basic Integrity: true

[kashif 350]

5 minutes ago, Craig said:

What results do you get from safetynet test?  https://play.google.com/store/apps/details?id=com.scottyab.safetynet.sample

This is what i get with my Note 8

 

[d 27]

3 minutes ago, ddark-il said:

CTS profile match: false

Basic Integrity: true

same here

[kashif 350]

3 minutes ago, kashif said:

This is what i get with my Note 8

 

so the issue is CTS profile match: false

[kashif 350]

Magisk  might or might not fix it.

i suspect it might not

[Waxberry 638]

Pro1 is under an approval (final stage) from Google to activate security features. Once it's finished we will release an OTA to activate contactless payment. Everything has been submitted and we are awaiting. 

[kashif 350]

2 minutes ago, Waxberry said:

Pro1 is under an approval (final stage) from Google to activate security features. Once it's finished we will release an OTA to activate contactless payment. Everything has been submitted and we are awaiting. 

Thanks Waxberry

[EskeRahn 5,471]

Minor odd bug:

The device info app CPU-Z acts oddly.

After a rather long time (about 20 sec) with a white tab CPU-Z shows the SOC info breifly, but unresponsive to scrolling, and then the entire device restarts.

(But it does not seem to have any other negative side effects)

[scy 10]

On my device, OpenSL ES (Android’s low-level sound API) seems to have issues. I’ve tried using SunVox (paid app, sorry, but it’s worth it if you’re interested in making music) and get all sorts of pops and crackling, even when disabling visualizations (logo on the top left, Preferences, Modules, disable “Show oscilloscope” and “Show level meter”) or increasing sample buffer (in Preferences, Audio, set Buffer to a high value). Sounds to me as if the audio samples don’t get to the DAC fast enough or there’s too little buffer somewhere else down the line. Caustic (free demo) works when using the AudioTrack API. When setting it to OpenSL ES (burger menu on the bottom left, Options, Audio API), it sometimes has the same problems, but most of the time seems to work fine, even with internal latency set to “lowest”. Both apps work flawlessly on my Nexus 5X.

[kashif 350]

16 hours ago, EskeRahn said:

Minor odd bug:

The device info app CPU-Z acts oddly.

After a rather long time (about 20 sec) with a white tab CPU-Z shows the SOC info breifly, but unresponsive to scrolling, and then the entire device restarts.

(But it does not seem to have any other negative side effects)

@EskeRahn I am wondering if its failing on some hardware, do you have any idea?

Have you installed some apps from play and are the other apps working ok?

[_DW_ 628]

11 minutes ago, kashif said:

@EskeRahn I am wondering if its failing on some hardware, do you have any idea?

Have you installed some apps from play and are the other apps working ok?

Exactly what I would assume.

[netman 1,424]

17 hours ago, EskeRahn said:

After a rather long time (about 20 sec) with a white tab CPU-Z shows the SOC info breifly, but unresponsive to scrolling, and then the entire device restarts.

If it does not happen for others may be worth further investigating, with some luck running

adb logcat

on a PC connected to the device via USB, and then reproducing the issue could provide some more insight to what happens.

[ddark-il 100]

17 hours ago, EskeRahn said:

Minor odd bug:

The device info app CPU-Z acts oddly.

After a rather long time (about 20 sec) with a white tab CPU-Z shows the SOC info breifly, but unresponsive to scrolling, and then the entire device restarts.

(But it does not seem to have any other negative side effects)

Same behavior  + AIDA64 crushing on sensors tab

[kashif 350]

@ddark-il can you tell us if all the functions are working?

 

[Wasmachineman_NL 99]

I can't seem to connect my PXC 550 to my Pro1?

 

[ddark-il 100]

Just now, Wasmachineman_NL said:

I can't seem to connect my PXC 550 to my Pro1?

Settings -> Connected Devices -> Gear Icon -> Disable HD audio: Qualcomm...

Tell me if it works

[EskeRahn 5,471]

4 hours ago, kashif said:

@EskeRahn I am wondering if its failing on some hardware, do you have any idea?

Have you installed some apps from play and are the other apps working ok?

Hmm, that it restarts the device, sounds like something deep getting in a very bad state. So my GUESS is some buggy code in a hardware driver.

[EskeRahn 5,471]

4 hours ago, netman said:

If it does not happen for others may be worth further investigating, with some luck running

adb logcat

on a PC connected to the device via USB, and then reproducing the issue could provide some more insight to what happens.

Sure tell me what to do more exactly - know nothing on how torn the logging on/off nor where to look for the log...

[netman 1,424]

25 minutes ago, EskeRahn said:

Sure tell me what to do more exactly - know nothing on how torn the logging on/off nor where to look for the log...

Any of these steps is under the condition you didn't already do it of course, but here hopefully complete instructions if i didn't forget something:

On the phone:
- Turn on developer options
- Go to "Settings -> Developer Options" and enable USB debugging

- [edit] Now when you connect the phone to the pc it will ask if the PC is allowed to debug the device, tell it yes.

On the PC
- Install ADB (on windows you may need some driver also, do not know how)
- Now you should be able to get a command line where you can run adb commands, to check if the phone is connected and found you can run:

adb devices

If that works running the "adb logcat" command I said will simply keep outputting data, until the phone reboots probably. Perhaps a better idea yet is to run:

adb logcat > log.txt

Which will dump the output into the text file "log.txt".

Edited November 20, 2019 by netman

[EskeRahn 5,471]

25 minutes ago, netman said:

.
.
.

adb logcat > log.txt

Which will dump the output into the text file "log.txt".

Ha ha, I thought it generated a log on the device I needed to retrieve, did not realise it just needed a pipe.... Just a sec....

[netman 1,424]

11 minutes ago, EskeRahn said:

Ha ha, I thought it generated a log on the device I needed to retrieve, did not realise it just needed a pipe.... Just a sec....

I would tell these things but I've become oblivious to what is obvious or not to others :D.

[EskeRahn 5,471]

1 hour ago, netman said:

I would tell these things but I've become oblivious to what is obvious or not to others :D.

(For the others in here, we had a 'little' PM dialogue digging in logs, but there were no obvious culprit - though some 'suspects' )

[netman 1,424]

Just now, EskeRahn said:

(For the others in here, we had a 'little' PM dialogue digging in logs, but there were no obvious culprit - though some 'suspects' )

The part I felt most relevant:

11-20 17:48:02.715  6164  6164 E SensorManager: Trigger Sensors should use the requestTriggerSensor.
11-20 17:48:02.736  6164  6164 I chatty  : uid=10159(com.cpuid.cpu_z) identical 1 line
11-20 17:48:02.736  6164  6164 E SensorManager: Trigger Sensors should use the requestTriggerSensor.
11-20 17:48:02.835  6164  6164 I Choreographer: Skipped 1881 frames!  The application may be doing too much work on its main thread.

But no idea how to get dmesg at the time of the crash to maybe find out more. I guess the developers know better though, and seems easy enough to reproduce the issue :).

[netman 1,424]

5 minutes ago, EskeRahn said:

... Found another app, where the sensor can be tried one by one, There are 50, it s the one called "Motion Accel"

Shortly after displaying,it restarts the device

The sensors hypothesis holds water! This actually may help the devs :).

[_DW_ 628]

44 minutes ago, netman said:

The sensors hypothesis holds water! This actually may help the devs :).

Yeah there is something fishy there.