Cannot Sync my Android Phone to MyPhoneExplorer WinePrefix

...in Tower's Manjaro KDE, but it works fine in Maui & openSUSE Tumbleweed KDE.

SUMMARY

  1. The MPE WinePrefix works well -- MPE correctly runs, except...
  2. Cannot Sync my phone to MPE in Manjaro, as 100% of attempts to establish the USB connection fail.
  3. From MPE log perusal i suspect possible root-cause as incompatible ADB version, but i don't know how to prove it or fix it.

BACKGROUND

Already Installed:

20180108_001

Here's how i created my MPE WinePrefix:

Install & Run MPE in Linux (Manjaro KDE) WinePrefix
   [works with Wine 1.8+]


1.   Using Octopi or Pamac for convenience, install: wine, wine-mono, wine_gecko, winetricks.

2.   WINEPREFIX=~/.wine-myphoneexplorer WINEARCH='win32' winecfg

3.   WINEPREFIX=~/.wine-myphoneexplorer WINEARCH='win32' winetricks vb6run

4.   cd "~/path to/MyPhoneExplorer (directory locally storing the MPE installation EXE)"

5.   WINEPREFIX=~/.wine-myphoneexplorer WINEARCH='win32' wine MyPhoneExplorer_Setup_v1.8.8.exe

6.   <<MPE should now be installed & runnable.>>         
#########################################

adb wait-for-device

#########################################

#!/bin/bash

#Run this BEFORE opening MyPhoneExplorer in PlayOnLinux or Wine, otherwise USB connection to my Android phone fails,
#Having first done this [a once-only necessity, not every time MPE runs]:
adb wait-for-device
#########################################

Log of successful Sync connection with MPE WP in Maui:

Logdatei MyPhoneExplorer
************************
Programmversion: 1.8.8
Datum:   07/01/2018

17:11:35.59       Windows Version=5.1
17:11:35.59       Setting Port: 999
17:11:35.59       Setting Baud: 115200
17:11:35.59       Avaiable Ports: COM0=; 
17:11:35.60       Main Load frmSplash
17:11:35.61       Load frmSplash...
17:11:35.62       Show splash...
17:11:35.62       frmSplash geladen
17:11:36.37       Hauptfenster wird geladen
17:11:36.51       Sidebar fertig geladen
17:11:36.74       UC SMS wird geladen
17:11:36.79       UC Phonebook wird geladen
17:11:36.82       UC Phonebook fertig geladen
17:11:36.83       UC Calls wird geladen
17:11:36.87       UC Organizer wird geladen
17:11:36.98       Organizer initiated
17:11:37.00       Startpage=3
17:11:37.02       UC Filebrowser wird geladen
17:11:37.10       UC Filebrowser fertig geladen
17:11:37.10       UC AppBrowser wird geladen
17:11:37.13       UC Notes wird geladen
17:11:37.16       UC Calls wird geladen
17:11:37.31       Setting Lastuser: motorola XT1068 [snipped]
17:11:37.34       PasswordCheck OK, check Userfolder, G_AppData=Z:\media\sf_Mobile_Phone_Backups_&_Databases_(Point_MPE_HERE)\MyPhoneExplorer
17:11:37.34       CheckUserDirectory for: motorola XT1068 [snipped]
17:11:37.34       Userfolder=Z:\media\sf_Mobile_Phone_Backups_&_Databases_(Point_MPE_HERE)\MyPhoneExplorer\motorola XT1068 [snipped]
17:11:37.34       ParseModell
17:11:37.36       Lade Userdatenbank: motorola XT1068 [snipped]
17:11:37.84       LoadDatafile: pb_metadata.xml(2648 Bytes)
17:11:37.85       LoadDatafile: Phonebook.dat(30365 Bytes)
17:11:38.49       Kontakte geladen
17:11:38.49       LoadDatafile: Calls.dat(21686 Bytes)
17:11:38.51       ParseDialedCalls needed 4ms
17:11:38.77       Anrufe geladen
17:11:38.77       Organizer LoadUser DefaultTimeColWidth=141
17:11:38.81       LoadDatafile: Organizer.dat(30024 Bytes)
17:11:38.83       LoadDatafile: cal_metadata.xml(863 Bytes)
17:11:38.87       Organizer geladen
17:11:38.88       LoadDatafile: notes_metadata.xml(114 Bytes)
17:11:38.88       Notizen geladen
17:11:38.88       Load SMS Data...
17:11:38.89       LoadDatafile: SMS.dat(569579 Bytes)
17:11:38.89       SMS - Datenbank wird geladen...
17:11:39.30       SMS Laden  - Readfile: 7 Split: 3 Parse: 391 HandleMultiSMS: 10 Nachrichten: 2577
17:11:39.31       LoadDatafile: SMSArchive.dat(1915 Bytes)
17:11:39.31       SMS Archiv laden - Parse: 19
17:11:39.64       RefreshList (Archive): Addrows=1 Sort=21 MenuUpdate=0 Redraw=0
17:11:40.00       SMS Data Loaded...
17:11:40.00       SMS geladen
17:11:40.37       Hauptfenster fertig geladen
17:11:40.48       Init Android Connection for future connect via USB
17:11:40.48       RunADBCommand: start-server
17:11:40.75       ADB CommandResponse: 
17:11:40.75       Run DeviceTracker
17:11:40.75       Init Tracker
17:11:40.76       Device Tracker Message: OKAY0012ZX1D234S84	device

17:11:46.37       Connect via USB
17:11:46.38       RunADBCommand: start-server
17:11:46.74       ADB CommandResponse: 
17:11:46.74       RunADBCommand: devices
17:11:47.12       ADB CommandResponse: List of devices attached 
ZX1D234S84	device
17:11:47.12       RunADBCommand: -s "ZX1D234S84" forward tcp:5210 tcp:5210
17:11:47.38       ADB CommandResponse: 
17:11:47.38       Try connecting to 127.0.0.1...
17:11:47.41       Socket closed
17:11:47.41       RunADBCommand: -s "ZX1D234S84" shell am start -n com.fjsoft.myphoneexplorer.client/.MainActivity --ez adb true
17:11:49.29       ADB CommandResponse: Starting: Intent { cmp=com.fjsoft.myphoneexplorer.client/.MainActivity (has extras) }
17:11:49.44       Try launch USB connection
17:11:49.56       Connect to Android OK (127.0.0.1)
17:11:49.56       Settimeout: RT=2000 WT=500
17:11:49.56       bOpened=True
17:11:49.56 [TX]: AT+CGSN
17:11:49.59 [RX]: AT+CGSN
17:11:49.59 [RX]: snipped
17:11:49.59 [RX]: OK
17:11:49.60       Settimeout: RT=15000 WT=1000
17:11:49.60 [TX]: AT*PIN?
17:11:49.61 [RX]: AT*PIN?
17:11:49.61 [RX]: *PIN: ACCESS OK,10
17:11:49.61 [RX]: OK
17:11:49.61 [TX]: ATI
17:11:49.63 [RX]: ATI
17:11:49.63 [RX]: motorola XT1068
17:11:49.63 [RX]: OK
17:11:49.63 [TX]: AT*APPVERSION=1.8.8
17:11:49.64 [RX]: AT*APPVERSION=1.8.8
17:11:49.64 [RX]: 23,1.0.45
17:11:49.64 [RX]: OK
17:11:49.65 [TX]: AT*ECAM=1
17:11:49.66 [RX]: AT*ECAM=1
17:11:49.66 [RX]: OK
17:11:49.67 [TX]: AT+CBC
17:11:49.68 [RX]: AT+CBC
17:11:49.68 [RX]: +CBC: 1,42
17:11:49.68 [RX]: OK
17:11:49.68 [TX]: AT+CSQ
17:11:49.70 [RX]: AT+CSQ
17:11:49.70 [RX]: +CSQ: 8,99
17:11:49.70 [RX]: OK
17:11:49.70       Alle Verbindungsaktionen beendet
17:11:49.71 [TX]: AT*SOPS
17:11:49.73 [RX]: AT*SOPS
17:11:49.73 [RX]: *SOPS: YES OPTUS,50502,au
17:11:49.73 [RX]: OK
17:11:49.80 [TX]: AT*GCMID=B8CE17B1
17:11:49.82 [RX]: AT*GCMID=B8CE17B1
17:11:49.82 [RX]: OK
17:11:57.12       Refresh ComDescriptions...
17:11:57.36       Error in StartFritzboxSearch: 429 ActiveX component can't create object
17:11:59.47 [RX]: *ALIVE: 1,42,8
17:11:59.78       Device driver info:
17:11:59.78       Devices with ADB Interface: 
17:11:59.78       ADB Devices: 
17:11:59.78       Portable devices: 
17:11:59.78       Unknown devices:

Manjaro Konsole ADB transcript [must do this before initial USB connection attempt (& before launching MPE) each KDE desktop session (in ALL Linux distros)]:

[kdemeoz@GA-Z97-HD3-Tower ~]$ adb wait-for-device
* daemon not running; starting now at tcp:5037
* daemon started successfully
[kdemeoz@GA-Z97-HD3-Tower ~]$

Log of UNsuccessful Sync connection with MPE WP in Manjaro [note Line 58+ (17:17:31.21, denoted by my appended "### ie, FAILS here")]:

Logdatei MyPhoneExplorer
************************
Programmversion: 1.8.8
Datum:   07/01/2018

17:17:25.56       Windows Version=6.1
17:17:25.56       Setting Port: 999
17:17:25.56       Setting Baud: 115200
17:17:25.56       Avaiable Ports: COM1=\Device\Serial0; COM2=\Device\Serial1; COM3=\Device\Serial2; COM4=\Device\Serial3; 
17:17:25.56       Main Load frmSplash
17:17:25.57       Load frmSplash...
17:17:25.57       Show splash...
17:17:25.58       frmSplash geladen
17:17:26.13       Hauptfenster wird geladen
17:17:26.24       Sidebar fertig geladen
17:17:26.33       UC SMS wird geladen
17:17:26.37       UC Phonebook wird geladen
17:17:26.41       UC Phonebook fertig geladen
17:17:26.41       UC Calls wird geladen
17:17:26.45       UC Organizer wird geladen
17:17:26.53       Organizer initiated
17:17:26.55       Startpage=3
17:17:26.56       UC Filebrowser wird geladen
17:17:26.62       UC Filebrowser fertig geladen
17:17:26.62       UC AppBrowser wird geladen
17:17:26.66       UC Notes wird geladen
17:17:26.68       UC Calls wird geladen
17:17:26.73       Setting Lastuser: motorola XT1068 [snipped]
17:17:26.75       PasswordCheck OK, check Userfolder, G_AppData=Z:\home\kdemeoz\VM Share Folder\Mobile Phone Backups & Databases (Point MPE HERE)\MyPhoneExplorer
17:17:26.75       CheckUserDirectory for: motorola XT1068 [snipped]
17:17:26.75       Userfolder=Z:\home\kdemeoz\VM Share Folder\Mobile Phone Backups & Databases (Point MPE HERE)\MyPhoneExplorer\motorola XT1068 [snipped]
17:17:26.75       ParseModell
17:17:26.76       Lade Userdatenbank: motorola XT1068 [snipped]
17:17:26.91       LoadDatafile: pb_metadata.xml(2648 Bytes)
17:17:26.92       LoadDatafile: Phonebook.dat(30365 Bytes)
17:17:27.26       Kontakte geladen
17:17:27.26       LoadDatafile: Calls.dat(21686 Bytes)
17:17:27.28       ParseDialedCalls needed 8ms
17:17:27.51       Anrufe geladen
17:17:27.51       Organizer LoadUser DefaultTimeColWidth=141
17:17:27.55       LoadDatafile: Organizer.dat(30024 Bytes)
17:17:27.57       LoadDatafile: cal_metadata.xml(863 Bytes)
17:17:27.60       Organizer geladen
17:17:27.61       LoadDatafile: notes_metadata.xml(114 Bytes)
17:17:27.61       Notizen geladen
17:17:27.61       Load SMS Data...
17:17:27.61       LoadDatafile: SMS.dat(569579 Bytes)
17:17:27.61       SMS - Datenbank wird geladen...
17:17:27.99       SMS Laden  - Readfile: 3 Split: 2 Parse: 367 HandleMultiSMS: 9 Nachrichten: 2577
17:17:27.99       LoadDatafile: SMSArchive.dat(1915 Bytes)
17:17:27.99       SMS Archiv laden - Parse: 1
17:17:28.22       RefreshList (Archive): Addrows=1 Sort=4 MenuUpdate=0 Redraw=1
17:17:28.59       SMS Data Loaded...
17:17:28.59       SMS geladen
17:17:28.82       Hauptfenster fertig geladen
17:17:28.92       Init Android Connection for future connect via USB
17:17:28.92       RunADBCommand: start-server
17:17:31.21       ADB CommandResponse: adb server version (39) doesn't match this client (36); killing...   ### ie, FAILS here.
17:17:31.21       Run DeviceTracker
17:17:33.21       Connect with ADB failed (DeviceTracker)
17:17:36.83       Connect via USB
17:17:36.83       RunADBCommand: start-server
17:17:37.09       ADB CommandResponse: * daemon not running. starting it now on port 5037 *
17:17:37.09       RunADBCommand: devices
17:17:37.37       ADB CommandResponse: List of devices attached
* daemon not running. starting it now on port 5037 *
17:17:37.37       Run DeviceTracker
17:17:39.37       Connect with ADB failed (DeviceTracker)
17:17:39.37       RunADBCommand: forward tcp:5210 tcp:5210
17:17:39.64       ADB CommandResponse: * daemon not running. starting it now on port 5037 *
17:17:39.64       Try connecting to 127.0.0.1...
17:17:39.64       SocketError: 10061 - Connection is forcefully rejected
17:17:39.64       RunADBCommand: shell am start -n com.fjsoft.myphoneexplorer.client/.MainActivity --ez adb true
17:17:39.91       ADB CommandResponse: * daemon not running. starting it now on port 5037 *
17:17:40.07       Try launch USB connection
17:17:40.07       SocketError: 10061 - Connection is forcefully rejected
17:17:40.37       Try launch USB connection
17:17:40.37       SocketError: 10061 - Connection is forcefully rejected
17:17:40.66       Try launch USB connection
17:17:40.67       SocketError: 10061 - Connection is forcefully rejected
17:17:40.97       Try launch USB connection
17:17:40.97       SocketError: 10061 - Connection is forcefully rejected
17:17:41.27       Try launch USB connection
17:17:41.27       SocketError: 10061 - Connection is forcefully rejected
17:17:41.57       Try launch USB connection
17:17:41.57       SocketError: 10061 - Connection is forcefully rejected
17:17:41.87       Try launch USB connection
17:17:41.87       SocketError: 10061 - Connection is forcefully rejected
17:17:42.17       Try launch USB connection
17:17:42.17       SocketError: 10061 - Connection is forcefully rejected
17:17:42.47       Try launch USB connection
17:17:42.47       SocketError: 10061 - Connection is forcefully rejected
17:17:42.77       Try launch USB connection
17:17:42.77       SocketError: 10061 - Connection is forcefully rejected
17:17:43.07       Try launch USB connection
17:17:43.07       SocketError: 10061 - Connection is forcefully rejected
17:17:43.37       Try launch USB connection
17:17:43.37       SocketError: 10061 - Connection is forcefully rejected
17:17:43.67       Try launch USB connection
17:17:43.67       SocketError: 10061 - Connection is forcefully rejected
17:17:43.97       Try launch USB connection
17:17:43.97       SocketError: 10061 - Connection is forcefully rejected
17:17:44.27       Try launch USB connection
17:17:44.27       SocketError: 10061 - Connection is forcefully rejected
17:17:44.56       Try launch USB connection
17:17:44.57       SocketError: 10061 - Connection is forcefully rejected
17:17:44.87       Try launch USB connection
17:17:44.87       SocketError: 10061 - Connection is forcefully rejected
17:17:45.16       Try launch USB connection
17:17:45.17       SocketError: 10061 - Connection is forcefully rejected
17:17:45.47       Try launch USB connection
17:17:45.47       SocketError: 10061 - Connection is forcefully rejected
17:17:45.76       Try launch USB connection
17:17:45.77       SocketError: 10061 - Connection is forcefully rejected
17:17:46.06       Connect to Android failed!
17:17:46.07       bOpened=False
17:17:46.07       Refresh ComDescriptions...
17:17:46.07       ErrMsg: Connection to phone could not be established!
17:18:04.56       Refresh ComDescriptions...
17:18:04.70       Error in StartFritzboxSearch: 429 ActiveX component can't create object
17:18:07.38       Device driver info:
17:18:07.38       Devices with ADB Interface: 
17:18:07.38       ADB Devices: 
17:18:07.38       Portable devices: 
17:18:07.38       Unknown devices:

Does anyone have any suggestions how i might solve this pls? For now i am getting by via my Win10, Maui & oS TW KDE VMs, each of which work correctly... but it would be much more convenient & elegant if i could do it directly in Manjaro.

Can you connect to your phone with the adb command in Manjaro?
Can you see your device with

adb devices

and can you connect to it with

adb shell

Thanks for v fast reply.

Yes & Yes.

There's never a problem with Manjaro seeing my phone; instantly that i connect the USB cable Manjaro's Device Notifier pops up to confirm the connection & offer me choices.

Instead, the problem is that [apparently] the [Manjaro] MyPhoneExplorer WinePrefix cannot see the phone, hence no sync with it is possible til that is solved [unless i use one of my previous distros' VMs].

In case anyone wonders, i MUST use MPE for this, as i do this not for file transfers [though it does that too (well, in my distros before Manjaro)], but for SMS history. It's so important to me coz MPE GUI provides a great way for me to view & sync to my desktop my phone's contacts, call log, but the most critical of all = all my SMS. It provides these in a great conversation array, & also allows me to interactively send & receive new SMS as well as review all old ones. Of course it also thus lets me backup all this data, coz post-sync all data is copied to my /home, & therefore participates in my weekly data backups.

I don't know how MyPhoneExplorer works. But I thought it uses the local adb binary to connect to your phone. But when you can use the adb comand to connect to your phone, it seems MPE can't use the version Manjaro provides.

When I do

adb version

I get

Android Debug Bridge version 1.0.39
Version 8.1.0_r1
Installed as /usr/bin/adb

You might want to try android-tools 7.1.2_r27 or a other 7.1 package, it should be adb version 1.0.36.

1 Like

Found your Maui thread, as @xabbu pointed out it sounds like a version issue.

What version of android-tools-adb and Wine did you use in the other distros?

If you need to use a previous version you can try downgrade tool

$ downgrade android-tools
Available packages:

*  1) android-tools-8.1.0_r1-1-x86_64.pkg.tar.xz (remote)
*  2) android-tools-8.1.0_r1-1-x86_64.pkg.tar.xz (local)
*  3) android-tools-8.0.0_r17-1-x86_64.pkg.tar.xz (remote)
*  4) android-tools-8.0.0_r17-1-x86_64.pkg.tar.xz (local)
*  5) android-tools-8.0.0_r11-1-x86_64.pkg.tar.xz (remote)
*  6) android-tools-8.0.0_r4-2-x86_64.pkg.tar.xz (remote)
*  7) android-tools-8.0.0_r4-1-x86_64.pkg.tar.xz (remote)
*  8) android-tools-7.1.2_r27-1-x86_64.pkg.tar.xz (remote)
   9) android-tools-7.1.2_r6-1-x86_64.pkg.tar.xz (remote)
  10) android-tools-7.1.1_r13-2-x86_64.pkg.tar.xz (remote)
  11) android-tools-7.1.1_r13-1-x86_64.pkg.tar.xz (remote)
  12) android-tools-7.0.0_r21-1-x86_64.pkg.tar.xz (remote)
  13) android-tools-7.0.0_r1-1-x86_64.pkg.tar.xz (remote)
  14) android-tools-6.0.1_r46-1-x86_64.pkg.tar.xz (remote)
  15) android-tools-6.0.1_r30-1-x86_64.pkg.tar.xz (remote)
  16) android-tools-6.0.1_r24-1-x86_64.pkg.tar.xz (remote)
  17) android-tools-6.0.1_r22-1-x86_64.pkg.tar.xz (remote)
  18) android-tools-6.0.1_r16-1-x86_64.pkg.tar.xz (remote)
  19) android-tools-6.0.1_r10-2-x86_64.pkg.tar.xz (remote)
  20) android-tools-6.0.1_r10-1-x86_64.pkg.tar.xz (remote)
  21) android-tools-5.1.1_r33-1-x86_64.pkg.tar.xz (remote)
  22) android-tools-5.1.1_r18-1-x86_64.pkg.tar.xz (remote)
  23) android-tools-5.1.1_r13-1-x86_64.pkg.tar.xz (remote)
  24) android-tools-5.1.1_r5-1-x86_64.pkg.tar.xz (remote)
  25) android-tools-5.1.1_r4-1-x86_64.pkg.tar.xz (remote)
  26) android-tools-5.1.1_r2-2-x86_64.pkg.tar.xz (remote)
  27) android-tools-5.1.1_r2-1-x86_64.pkg.tar.xz (remote)
  28) android-tools-5.1.0_r3-1-x86_64.pkg.tar.xz (remote)
  29) android-tools-5.0.2_r1-1-x86_64.pkg.tar.xz (remote)
  30) android-tools-5.0.0_r7-1-x86_64.pkg.tar.xz (remote)

Just be aware that downgrading may not work if dependencies are not satisfied

$ pacman -Qi android-tools
Name            : android-tools
Version         : 8.1.0_r1-1
Description     : Android platform tools
...
Depends On      : pcre2  libusb

If downgrading isn't working, you can get a pre build binary from Google. Unfortunately I could only find the newest Version as an small download.

You might need to investigate this, a good staring point is probably https://developer.android.com/studio/releases/platform-tools.html

Thank you both. I felt a frisson of excitement at the possibility that downgrading might solve the problem [as i said in my initial summary, #3, i suspected this possibility, but was clueless how to proceed]. My frisson soon enough turned to frustration when i was reminded of my lack of knowledge:

[kdemeoz@GA-Z97-HD3-Tower ~]$ sudo downgrade android-tools
[sudo] password for kdemeoz: 

Downgrading from A.L.A. is disabled on the stable branch. See https://wiki.archlinux.org/index.php/downgrading_packages for more details.
loading packages...
warning: android-tools-8.1.0_r1-1 is up to date -- reinstalling
resolving dependencies...
looking for conflicting packages...

Packages (1) android-tools-8.1.0_r1-1

Total Installed Size:  2.13 MiB
Net Upgrade Size:      0.00 MiB

:: Proceed with installation? [Y/n] n
[kdemeoz@GA-Z97-HD3-Tower ~]$

I read that Arch link, & also https://wiki.manjaro.org/index.php?title=Downgrade which says

note: If you are in stable branch ALA is disable by default because potentially dangerous ( a message warning you ). If needed, you can enable it by setting the environment variable DOWNGRADE_FROM_ALA to 1. See man downgrade for further details

I don't understand how to

setting the environment variable

so i duly read man downgrade. It says [partial extract]

DOWNGRADE(8)                                                                                                                                    

SYNOPSIS
       downgrade [PACKAGE, ...] [-- [PACMAN OPTIONS]]

DESCRIPTION
       Downgrade Arch Linux packages.

ENVIRONMENT VARIABLES
       PACMAN_CONF Your pacman configuration file.  Default is /etc/pacman.conf.
       
       DOWNGRADE_FROM_ALA Search the A.L.A.  Default is 1.

but this does not help a numpty like me [ie, the Synopsis does not mention anything about how to use Environment Variables, only Options, yet the subsequent section says nothing about Options; sigh]. It mentions /etc/pacman.conf so i looked in there, but did not notice anything helpful.

I tried, & failed with:

[kdemeoz@GA-Z97-HD3-Tower ~]$ sudo downgrade android-tools DOWNGRADE_FROM_ALA=1
[sudo] password for kdemeoz: 

Downgrading from A.L.A. is disabled on the stable branch. See https://wiki.archlinux.org/index.php/downgrading_packages for more details.
[kdemeoz@GA-Z97-HD3-Tower ~]$

I suppose some might say this is another reason i should change from Stable to Testing branch, but in my mind my ongoing ineptitude remains a compelling warning NOT to change to Testing [Warning warning, danger Will Robinson].

I'm sure it will be trivial once i know -- pls could you explain how [in Stable] i temporarily access downgrades from ALA?

Don't necessarily need to run downgrade with sudo, you'll be prompted for your sudo password after selecting the package to downgrade to.

You can explicitly prefix the downgrade statement for simplicity sake

DOWNGRADE_FROM_ALA=1 downgrade android-tools

As for why ALA is disabled in stable, there was a long thread on this

As you can see, opinions vary, but the workaround with DOWNGRADE_FROM_ALA is a simple enough workaround if required in the stable repos.

As for setting environment variables, I use either .bashrc ...

export PS1='[\h \W]\$ '
export SUDO_EDITOR=kate

or /etc/environment ...

_JAVA_OPTIONS='-Dawt.useSystemAAFontSettings=on'

to set them for my system.

For more info the Arch wiki is always the best source ...

https://wiki.archlinux.org/index.php/Environment_Variables

Some might argue, myself included, that encountering and fixing issues is the best learning tool available. That and researching any associated concepts on the Arch wiki.

1 Like

I did not ask that, i understand WHY it's disabled, just not how to temporarily workaround it. About to try your clue now... thank you.

Still an interesting read, with a lot of contrasting viewpoints, assuming you haven't already that is.

1 Like

Bummer.

[kdemeoz@GA-Z97-HD3-Tower ~]$ DOWNGRADE_FROM_ALA=1 downgrade android-tools

Downgrading from A.L.A. is disabled on the stable branch. See https://wiki.archlinux.org/index.php/downgrading_packages for more details.
[sudo] password for kdemeoz: 
loading packages...
warning: android-tools-8.1.0_r1-1 is up to date -- reinstalling
resolving dependencies...
looking for conflicting packages...
                                                                                                                             
Packages (1) android-tools-8.1.0_r1-1                                                                                        
                                                                                                                             
Total Installed Size:  2.13 MiB                                                                                              
Net Upgrade Size:      0.00 MiB                                                                                              
                                                                                                                             
:: Proceed with installation? [Y/n] n                                                                                        
[kdemeoz@GA-Z97-HD3-Tower ~]$

My understanding is that explicit prefix should work, although its been some time since I was on the stable branch. Maybe others can explain why it doesn't now.

Testing branch switch then ... yay ... be brave !

:slight_smile:

Teehee... as a dedicated lifetime coward that's a big ask... but maybe i still should anyway. Thinking, thinking...

Changing branches is simply switching mirrors.

You can use pacman-mirrors to do this, which is basically a small program to take the configuration in /etc/pacman-mirrors.conf and generate your mirrorlist file. Its a Manjaro specific tool to make mirror management automated and easier.

When I switch branches for something like a single package downgrade I simply update the mirrorlist file manually.

sudoedit /etc/pacman.d/mirrorlist

A different branch is simply a different path on the mirror server, for instance

## Country : Germany
Server = https://mirror.netzspielplatz.de/manjaro/packages/stable/$repo/$arch

references all packages for the stable repo, change to reference testing packages is as simple as

## Country : Germany
Server = https://mirror.netzspielplatz.de/manjaro/packages/testing/$repo/$arch

If you are installing packages from a different branch sync repo databases beforehand

sudo pacman -Syy

When done change it back and re-sync your repo database.

Each update pacman simply syncs the packages in that specific mirror path with your local packages. Any differences are either updated (-u) or downgraded (-uu).

Thank you. It's not actually the mechanics of how to switch that daunts me [as you showed that's quite straightforward & i daresay reasonably numpty-proof]. Instead it's my substantial lack of faith in my ability to extricate myself from any difficulty i might subsequently experience, without having to throw myself on the mercy of the forum for help... & frankly i feel i have already been doing too much of that!

The other reason though, which i enunciated in another recent thread, is purely pragmatic... i left openSUSE Tumbleweed KDE for Manjaro KDE Stable partly because i tired of the sheer volume of TW updates that meant i was updating & rebooting [with all the associated interruption to my workflow] daily or each other day [you see, i do not shutdown my pc at night & boot it in the morning; i Suspend it at night, with all my docs & pgm windows still laid out across my VDs & Activities per my efficient workflow, then i Resume it each morning, thus am efficient right from the start] . My other concern therefore with Testing is that i might well then find myself back in that same v frequent reboot rhythm, constantly disrupting actually doing stuff, & instead constantly maintaining the pc. At least with Stable i typically seem to get about ~5 days' Uptime before needing to do the updates & reboots [or at least i think i did, before Meltdown & Spectre].

1 Like

Community is what makes Manjaro, well, Manjaro. Great distro, but the forum is the real difference maker IMO.

No matter what the question there will always be someone hanging around willing to help, or at least attempt to.

1 Like

Works here...

$ DOWNGRADE_FROM_ALA=1 downgrade android-tools

Downgrading from A.L.A. is disabled on the stable branch. See https://wiki.archlinux.org/index.php/downgrading_packages for more details.
Available packages:

   1) android-tools-8.1.0_r1-1-x86_64.pkg.tar.xz (remote)
   2) android-tools-8.0.0_r17-1-x86_64.pkg.tar.xz (remote)
   3) android-tools-8.0.0_r11-1-x86_64.pkg.tar.xz (remote)
   4) android-tools-8.0.0_r4-2-x86_64.pkg.tar.xz (remote)
   5) android-tools-8.0.0_r4-1-x86_64.pkg.tar.xz (remote)
   6) android-tools-7.1.2_r27-1-x86_64.pkg.tar.xz (remote)
   7) android-tools-7.1.2_r6-1-x86_64.pkg.tar.xz (remote)
   8) android-tools-7.1.1_r13-2-x86_64.pkg.tar.xz (remote)
   9) android-tools-7.1.1_r13-1-x86_64.pkg.tar.xz (remote)
  10) android-tools-7.0.0_r21-1-x86_64.pkg.tar.xz (remote)
  11) android-tools-7.0.0_r1-1-x86_64.pkg.tar.xz (remote)
  12) android-tools-6.0.1_r46-1-x86_64.pkg.tar.xz (remote)
  13) android-tools-6.0.1_r30-1-x86_64.pkg.tar.xz (remote)
  14) android-tools-6.0.1_r24-1-x86_64.pkg.tar.xz (remote)
  15) android-tools-6.0.1_r22-1-x86_64.pkg.tar.xz (remote)
  16) android-tools-6.0.1_r16-1-x86_64.pkg.tar.xz (remote)
  17) android-tools-6.0.1_r10-2-x86_64.pkg.tar.xz (remote)
  18) android-tools-6.0.1_r10-1-x86_64.pkg.tar.xz (remote)
  19) android-tools-5.1.1_r33-1-x86_64.pkg.tar.xz (remote)
  20) android-tools-5.1.1_r18-1-x86_64.pkg.tar.xz (remote)
  21) android-tools-5.1.1_r13-1-x86_64.pkg.tar.xz (remote)
  22) android-tools-5.1.1_r5-1-x86_64.pkg.tar.xz (remote)
  23) android-tools-5.1.1_r4-1-x86_64.pkg.tar.xz (remote)
  24) android-tools-5.1.1_r2-2-x86_64.pkg.tar.xz (remote)
  25) android-tools-5.1.1_r2-1-x86_64.pkg.tar.xz (remote)
  26) android-tools-5.1.0_r3-1-x86_64.pkg.tar.xz (remote)
  27) android-tools-5.0.2_r1-1-x86_64.pkg.tar.xz (remote)
  28) android-tools-5.0.0_r7-1-x86_64.pkg.tar.xz (remote)
  29) android-tools-5.0.0_r2-1-x86_64.pkg.tar.xz (remote)
  30) android-tools-4.4.4_r2.0.1-1-x86_64.pkg.tar.xz (remote)

select a package by number: ^C

1 Like

Yabba dabba doooooooo, it works!

Dear @xabbu & @sueridgepipe, thank you so very much for your help; you have solved this problem. Now finally i can successfully sync my phone with my MPE WinePrefix directly in Manjaro [Stable, teehee]. Yay.

I don't really understand why my previous attempt to do the downgrade failed, but within the past 30' on a whim i tried it again, & this time i did get the multiple ALA choices as well as my cache:

[kdemeoz@GA-Z97-HD3-Tower ~]$ DOWNGRADE_FROM_ALA=1 downgrade android-tools                                                                                       
                                                                                                                                                                 
Downgrading from A.L.A. is disabled on the stable branch. See https://wiki.archlinux.org/index.php/downgrading_packages for m                                    ore details.                                                                                                                                                     
Available packages:                                                                                                                                              
                                                                                                                                                                 
*  1) android-tools-8.1.0_r1-1-x86_64.pkg.tar.xz (remote)                                                                                                        
*  2) android-tools-8.1.0_r1-1-x86_64.pkg.tar.xz (local)                                                                                                         
   3) android-tools-8.0.0_r17-1-x86_64.pkg.tar.xz (remote)                                                                                                       
   4) android-tools-8.0.0_r11-1-x86_64.pkg.tar.xz (remote)
   5) android-tools-8.0.0_r4-2-x86_64.pkg.tar.xz (remote)
   6) android-tools-8.0.0_r4-1-x86_64.pkg.tar.xz (remote)
   7) android-tools-7.1.2_r27-1-x86_64.pkg.tar.xz (remote)
   8) android-tools-7.1.2_r6-1-x86_64.pkg.tar.xz (remote)
   9) android-tools-7.1.1_r13-2-x86_64.pkg.tar.xz (remote)
  10) android-tools-7.1.1_r13-1-x86_64.pkg.tar.xz (remote)
  11) android-tools-7.0.0_r21-1-x86_64.pkg.tar.xz (remote)
  12) android-tools-7.0.0_r1-1-x86_64.pkg.tar.xz (remote)
  13) android-tools-6.0.1_r46-1-x86_64.pkg.tar.xz (remote)
  14) android-tools-6.0.1_r30-1-x86_64.pkg.tar.xz (remote)
  15) android-tools-6.0.1_r24-1-x86_64.pkg.tar.xz (remote)
  16) android-tools-6.0.1_r22-1-x86_64.pkg.tar.xz (remote)
  17) android-tools-6.0.1_r16-1-x86_64.pkg.tar.xz (remote)
  18) android-tools-6.0.1_r10-2-x86_64.pkg.tar.xz (remote)
  19) android-tools-6.0.1_r10-1-x86_64.pkg.tar.xz (remote)
  20) android-tools-5.1.1_r33-1-x86_64.pkg.tar.xz (remote)
  21) android-tools-5.1.1_r18-1-x86_64.pkg.tar.xz (remote)
  22) android-tools-5.1.1_r13-1-x86_64.pkg.tar.xz (remote)
  23) android-tools-5.1.1_r5-1-x86_64.pkg.tar.xz (remote)
  24) android-tools-5.1.1_r4-1-x86_64.pkg.tar.xz (remote)
  25) android-tools-5.1.1_r2-2-x86_64.pkg.tar.xz (remote)
  26) android-tools-5.1.1_r2-1-x86_64.pkg.tar.xz (remote)
  27) android-tools-5.1.0_r3-1-x86_64.pkg.tar.xz (remote)
  28) android-tools-5.0.2_r1-1-x86_64.pkg.tar.xz (remote)
  29) android-tools-5.0.0_r7-1-x86_64.pkg.tar.xz (remote)
  30) android-tools-5.0.0_r2-1-x86_64.pkg.tar.xz (remote)

select a package by number: 7
[sudo] password for kdemeoz: 
 android-tools-7.1.2_r27-1-x86_64                  207.5 KiB   162K/s 00:01 [##########################################] 100%
 android-tools-7.1.2_r27-1-x86_64.sig              566.0   B  0.00B/s 00:00 [##########################################] 100%
loading packages...
warning: downgrading package android-tools (8.1.0_r1-1 => 7.1.2_r27-1)
resolving dependencies...
looking for conflicting packages...

Packages (1) android-tools-7.1.2_r27-1

Total Installed Size:   0.61 MiB
Net Upgrade Size:      -1.52 MiB

:: Proceed with installation? [Y/n] 
(1/1) checking keys in keyring                                              [##########################################] 100%
(1/1) checking package integrity                                            [##########################################] 100%
(1/1) loading package files                                                 [##########################################] 100%
(1/1) checking for file conflicts                                           [##########################################] 100%
(1/1) checking available disk space                                         [##########################################] 100%
:: Processing package changes...
(1/1) downgrading android-tools                                             [##########################################] 100%
:: Running post-transaction hooks...
(1/1) Arming ConditionNeedsUpdate...
add android-tools to IgnorePkg? [y/n] y

[kdemeoz@GA-Z97-HD3-Tower ~]$ pacman -Qi android-tools
Name            : android-tools
Version         : 7.1.2_r27-1
Description     : Android platform tools
Architecture    : x86_64
URL             : http://tools.android.com/
Licenses        : Apache  MIT
Groups          : None
Provides        : None
Depends On      : openssl  pcre
Optional Deps   : python: for mkbootimg script [installed]
Required By     : None
Optional For    : None
Conflicts With  : None
Replaces        : None
Installed Size  : 623.00 KiB
Packager        : Anatol Pomozov <anatol.pomzov@gmail.com>
Build Date      : Tue 18 Jul 2017 09:45:34 AEST
Install Date    : Mon 08 Jan 2018 19:37:12 AEDT
Install Reason  : Explicitly installed
Install Script  : No
Validated By    : Signature

[kdemeoz@GA-Z97-HD3-Tower ~]$

I decided to firstly try that downgrade of the primary package only, not also pcre2 & libusb, & i did choose #7 android-tools 7.1.2_r27 as suggested. This turned out to be entirely sufficient. After the downgrade, i physically connected the USB cable, issued the ADB command, launched the MPE WP, in its GUI then clicked the Connect menu option, held my breath... & delightedly saw the connection finally succeed... after which i was able to perform the Sync. This is wonderful.

Again, thank you both very much :sunny:

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

Forum kindly sponsored by