Phone not connecting

[alexanderSTW]

Computer: Apple M1 MAX, macOS Ventura 13.0.1
Phone: Samsung Galaxy S22, Android 13.
Software version: OpenMTP v.3.2.0 Mac ARM64.
Had no problem prior to upgrading to macOS Ventura and OpenMTP up from 3.1.15. Going back to OpenMTP 3.1.15 does not solve the issue.
Refreshing OpenMTP per the instructions only results in error "an error occured while setting up the Phone".
Combinations of switching between Kalam / Legacy modes and enabling/disabling auto-detection has no effect on issue.
Thank you,
Alexander.

[eisenbruch]

Computer: Apple M1 Pro, macOS Ventura 13.0.1
Phone: Pixel 7 Pro, Android 13 (fully updated)
Software version: OpenMTP v.3.2.0.6 Mac ARM64.

Don't know what version I was on before v.3.2.0.6 but when I updated just now it stopped working.

[ganeshrvel]

Thanks for the reporting the issue. Momentarily what you could do is:

• Download the version 3.1.5 from GitHub releases and install the app.
• Disable the internet and open the application.
• Turn off the auto updater from settings of OpenMTP.
• Enable internet

This should prevent auto update.

[alexanderSTW]

Thank you for the feedback @ganeshrvel. Followed the steps but even the older 3.1.5 version is not working now. it seems something has permanently changed as the phone filesystem never shows up on OpenMTP any longer.
Let me clarify that
-- "Legacy" is the only connection method; if I select "Kalam" then OpenMTP keeps producing the error "an error occured while setting up the Phone".
-- As soon as the phone is connected by cable to the computer, the phone presents me fine with the prompt to allow data transfer. However, no matter how many times I try refreshing the OpenMTP phone panel, it appears that OpenMTP is non-responsive to the connected phone.
I am guessing that either macOS Vantura and/or Android 13 entirely block OpenMTP from viewing the phone's filesystem. Happy to further assist with testing if you need.

[newdev4ios]

Same issue here but with a Galaxy Fold 4, and same scenario too
except im on 3.2.1.15

[ganeshrvel]

I'm waiting for my cicd partner's response to make a new release which patches this issue

[alexanderSTW]

Grateful for the efforts!

[newdev4ios]

Update: for me installing the Samsung smart switch app for the phone fixed the issue, not my phone connects with no trouble to openMTP and Android file transfer app.

[alexanderSTW]

I can confirm that the latest version 3.2.10 resolves the issue; thank you all for the feedback and Ganesh for the release.

[cleverlemming]

Samsung A71 5G is not recognized after Android 13, One UI 5.1 update.
Tried rebooting, uninstalling smart switch, setting default USB configuration to "transferring files"

[ganeshrvel]

Hi.

Kindly follow the steps on this page (#276) and check if it resolves your issue.

[artfarmer]

Besides disabling the disturbing apps on your Mac – If nothing of the above helps you can try to wipe the caches, for that you need to start your phone in recovery mode:

• switch off your phone
• connect via USB to your computer (just connecting)
• press Volume-up + Power button for 8–10 seconds (at least for Samsung phones)
• in the recovery mode menu select 'wipe cache partition' (not dangerous, will be re-generated) and confirm
• then select 'repair apps' and the phone will restart

This helped twice in my case (last time after the update to One UI 6.0)

[ganeshrvel]

@newdev4ios

Update: for me installing the Samsung smart switch app for the phone fixed the issue, not my phone connects with no trouble to openMTP and Android file transfer app.

did you mean installing helped or uninstalling helped you?

[newdev4ios]

I think it was installing Samsung smart switch app on my MacBook helped.
I think I meant now my phone connects with no trouble...
I can't remember 100% as its been a while because my fold 4 completely broke in two (it is currently in the form of two paper weights)