Error logs, how to?

Help Fairphone 2
1

Hey
since last FP update I got a problem of sync with an app (google contacts, ok I know ;(
I have been patient and hoped for an update fix but nothing new
I would like to see if some error logs somewhere can help me to fix the problem after having tried in vain many options, phone wise or google account wise

I tried to follow this
My linux system does not allow me to list de device. I tried again through adding a udev rule, but udev is obsolete now, systemd has taken over, and I am stuck again.

Is there a way to view specific logs attached to specific apps?
A friend recommands after having searched infinite bug possibilities to reformat the phone but I find that solution a bit harsh.
thanks
Bruno

2

What does “My linux system does not allow me to list de device.” mean?

Does your phone appear, when you run lsusb?

udev is obsolete now, systemd has taken over

That is simply not true. udev is a part of systemd, now, yes. But it still does the autodetection of devices.

But this udev rule only solves the problem I described in the post:

If it’s not device but unauthorized you need to unlock your phone and confirm the debugging for this PC and / or restart adbd as root on your PC. (For GNU/Linux this should be adb kill-server && sudo adb start-server.)

If it doesn’t appear at all, an udev rule won’t solve your problem, I think.

If none of this does help:

Have you tried running journalctl -ef and plugging in your phone?
There could be a few interesting things in that log.

3

Hello
OS is
Mageia 6
noyau : 4.9.43-desktop-1.mga6
arch: 64-bit
Bureau : KDE

Yes, the phone does appear via lsusb : Bus 003 Device 007: ID 2ae5:9039
no name or designation attached to it though

the command adb devices show nothing (or a blank line)

[bruno@localhost ~]$ adb devices
List of devices attached

[bruno@localhost ~]$

so I tried the solution through udev, which does not work
You are right of course with udev sorry

result of journalctl -ef after pluging:

sept. 13 18:43:23 localhost.localdomain kernel: usb 3-1: new high-speed USB device number 12 using xhci_hcd
sept. 13 18:43:23 localhost.localdomain kernel: usb 3-1: New USB device found, idVendor=2ae5, idProduct=9015
sept. 13 18:43:23 localhost.localdomain kernel: usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
sept. 13 18:43:23 localhost.localdomain kernel: usb 3-1: Product: FP2
sept. 13 18:43:23 localhost.localdomain kernel: usb 3-1: Manufacturer: Fairphone
sept. 13 18:43:23 localhost.localdomain kernel: usb 3-1: SerialNumber: fbd5f66d
sept. 13 18:43:23 localhost.localdomain kernel: usb-storage 3-1:1.1: USB Mass Storage device detected
sept. 13 18:43:23 localhost.localdomain kernel: scsi host7: usb-storage 3-1:1.1
sept. 13 18:43:23 localhost.localdomain mtp-probe[28819]: checking bus 3, device 12: “/sys/devices/pci0000:00/0000:00:14.0/usb3/3-1”
sept. 13 18:43:23 localhost.localdomain mtp-probe[28819]: bus: 3, device: 12 was not an MTP device
sept. 13 18:43:24 localhost.localdomain kernel: scsi 7:0:0:0: Direct-Access Linux File-CD Gadget 0000 PQ: 0 ANSI: 2
sept. 13 18:43:24 localhost.localdomain kernel: sd 7:0:0:0: [sde] Attached SCSI removable disk
sept. 13 18:43:24 localhost.localdomain krunner[2767]: “/org/freedesktop/UDisks2/drives/Linux_File_CD_Gadget_fbd5f66d” has new interfaces: (“org.freedesktop.UDisks2.Drive”)
sept. 13 18:43:24 localhost.localdomain org_kde_powerdevil[2810]: “/org/freedesktop/UDisks2/drives/Linux_File_CD_Gadget_fbd5f66d” has new interfaces: (“org.freedesktop.UDisks2.Drive”)
sept. 13 18:43:24 localhost.localdomain kdeinit5[2690]: “/org/freedesktop/UDisks2/drives/Linux_File_CD_Gadget_fbd5f66d” has new interfaces: (“org.freedesktop.UDisks2.Drive”)
sept. 13 18:43:24 localhost.localdomain plasmashell[2768]: “/org/freedesktop/UDisks2/drives/Linux_File_CD_Gadget_fbd5f66d” has new interfaces: (“org.freedesktop.UDisks2.Drive”)
sept. 13 18:43:24 localhost.localdomain org_kde_powerdevil[2810]: “/org/freedesktop/UDisks2/block_devices/sde” has new interfaces: (“org.freedesktop.UDisks2.Block”)
sept. 13 18:43:24 localhost.localdomain krunner[2767]: “/org/freedesktop/UDisks2/block_devices/sde” has new interfaces: (“org.freedesktop.UDisks2.Block”)
sept. 13 18:43:24 localhost.localdomain kdeinit5[2690]: QObject::connect: invalid null parameter
sept. 13 18:43:24 localhost.localdomain kdeinit5[2690]: “/org/freedesktop/UDisks2/block_devices/sde” has new interfaces: (“org.freedesktop.UDisks2.Block”)
sept. 13 18:43:24 localhost.localdomain kdeinit5[2690]: QObject::connect: invalid null parameter
sept. 13 18:43:24 localhost.localdomain plasmashell[2768]: “/org/freedesktop/UDisks2/block_devices/sde” has new interfaces: (“org.freedesktop.UDisks2.Block”)

So clearly the phone is recognized. But I never got any problem with file transfer anyway, except sometimes it is a bit unstable.

Otherwise, before plugging the phone there are lots of

sept. 13 18:40:35 localhost.localdomain plasmashell[2768]: QXcbConnection: XCB error: 2 (BadValue), sequence: 8427, resource id: 132120592, major code: 141 (Unknown), minor code: 3

I don’t know what that is

4

This has nothing to do with your phone.

sept. 13 18:43:23 localhost.localdomain kernel: usb 3-1: new high-speed USB device number 12 using xhci_hcd
sept. 13 18:43:23 localhost.localdomain kernel: usb 3-1: New USB device found, idVendor=2ae5, idProduct=9015
sept. 13 18:43:23 localhost.localdomain kernel: usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
sept. 13 18:43:23 localhost.localdomain kernel: usb 3-1: Product: FP2
sept. 13 18:43:23 localhost.localdomain kernel: usb 3-1: Manufacturer: Fairphone
sept. 13 18:43:23 localhost.localdomain kernel: usb 3-1: SerialNumber: fbd5f66d

So, your phone gets detected.

Have you enabled USB Debugging in your phone’s settings?

Did you try starting adbd as root on your PC?

5

I did[quote=“YtvwlD, post:4, topic:32982”]
Did you try starting adbd as root on your PC?
[/quote]

I did

To give more precision the reason why I want to solve the problem of Contacts is not even to sync with the google account, this I can dispense with, but when using Contacts there are to many messages “Synchronisation de google Contacts s’est arrêt”

i installed another contact app and even disabled google contacts, but the error message nevertheless keeps reappearing, even when preventing Contacts notifications

6

Ok I chose the option to reset to factory setting, although it did that while reinstalling straight away Android 6.
I do not have the contact sync problem, but adb is still not recognising the phone anyway. Windows does that, so probably a problem whit mageia+fairphone, since a samsung was recognised with adb devices.

7

This topic was automatically closed 182 days after the last reply. New replies are no longer allowed.