• PSA: How to sms/mms cross platform Google Messages Android:{Windows,macOS,Linux,Tablet}

    From Maria Sophia@mariasophia@comprehension.com to alt.comp.os.windows-10,comp.mobile.android,alt.os.linux on Wed Oct 7 12:10:49 2026
    From Newsgroup: alt.os.linux

    PSA:
    How to sms/mms cross platform Google Messages Android:{Windows,macOS,Linux,Tablet}

    In a recent c.m.a thread, it was asked how to sms/mms using the Windows PC.
    Newsgroups: comp.mobile.android
    Subject: Re: Tool for sending text message to or from computer
    Date: Tue, 6 Oct 2026 16:07:16 -0300
    Message-ID: <11a3gt4$2c2$1@nnrp.usenet.blueworldhosting.com>

    Frank Slootweg wrote:
    The web interface just allows you to use a big screen, normal keyboard
    and 'mouse', instead of a small phone touch screen.

    I just switched my wife to Google Messages today, because PulseSMS updated
    to the latest version (which has ads) and the downgrade installed fine
    adb install -d -r -i not.com.android.vending PulseSMS5.4.6.2816.apk
    Normally that works because it does the following:
    -d means allow downgrades
    -r means replace w/o wiping out the data
    -i to anything but com.android.vending (i.e., the google play store)

    Where adb allows me to check this information to make sure it stuck.
    adb shell dumpsys package xyz.klinker.messenger | findstr installerPackageName
    => installerPackageName=not.com.android.vending

    But, apparently due to mismatches in versions, the downgrade kept crashing.
    So I checked what API level was needed, and that seemed to be fine.
    adb shell getprop ro.build.version.sdk
    => 33
    adb shell dumpsys package xyz.klinker.messenger | findstr "versionName versionCode"
    => versionCode=2816 minSdk=21 targetSdk=30
    => versionName=5.4.6.2816

    And then I had to check which version the APK was set to NOT run on.
    aapt dump badging pulsesms_5.4.11.2831.apk | findstr /R "sdkVersion versionName versionCode"
    => package: name='xyz.klinker.messenger' versionCode='2831'
    => versionName='5.4.11.2831'
    => compileSdkVersion='30'
    => compileSdkVersionCodename='11'
    => sdkVersion:'21'

    It shouldn't have crashed, but it's probably a database schema mismatch.
    Even though the database "appears" empty, adb shows me 26K messages.
    adb shell content query --uri content://sms/
    Which is kind of neat that you can read all the messages so easily.

    Anyway, This gave me a summary that there were 26695 messages on her
    phone, which I didn't want to take the risk of wiping out by mistake.
    adb shell content query --uri content://sms/ --projection _id
    => ... over twenty six thousand rows...
    => Row: 26693 _id=33
    => Row: 26694 _id=32
    => Row: 26695 _id=31

    So even though her PulseSMS downgrade can't read the database, it's there.

    Rather than fight an old version of software, I simply installed the Google messages app on her phone 'cuz she logs into Google like most people do.

    Google Messages seems to work fine, as I could see all 26K messages:
    And it has RCS which will work when MMS'ing the grandchildren in iOS.

    I'm gonna add a link to <https://messages.google.com/web>, as Frank
    suggested, on both her non-SIM Android tablet & on her Windows 11 laptop.

    Instructions (from looking it up):
    1. Open <https://messages.google.com/web> in any web browser
    2. Apparently we will see a QR code on the screen.
    3. Then open the Google Messages app on the Android phone.
    4. Tap the profile icon in the top right corner & select Device pairing.
    5. Tap the QR code scanner button and point the phone's camera
    at the QR code on the computer screen to scan that QR code.
    6. Once scanned, supposedly that makes the messages sync
    Note: The phone needs to remain connected to the internet (via Wi-Fi
    or mobile data) for the web version to send & receive messages.

    Actually, I had her phone in front of me when I "tried" those instructions. What happened was she was already logged into both so it showed 3
    pictographic images on the web page & one of them on the Android.
    a. It asked: Select the image on the phone that is on the web
    b. And that did, apparently, a device-pairing verification
    c. I didn't test it further but it seems to be very easy to do

    If it were me, I just use scrcpy since then the entire phone (not just the SMS/MMS messenger) is using the PC keyboard & mouse & speakers & clipbrd.
    <https://github.com/Genymobile/scrcpy>
    <https://github.com/Genymobile/scrcpy/blob/master/doc/windows.md>
    <https://i.postimg.cc/5NrK7jtg/scrcpy16.jpg>

    That also works on all desktop platforms, which means the entire phone
    is mirrored two feet tall onto your monitor over Wi-Fi or over USB.

    Either way, scrcpy or just Google Messages on the web is a nice way of
    using the desktop to send/receive mms/sms cross platform Android:Desktop.

    Obviously if you know of better or easier ways to do it, let all know.
    --
    On Usenet, kind helpful people learn from others in every single article.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Lawrence =?iso-8859-13?q?D=FFOliveiro?=@ldo@nz.invalid to alt.comp.os.windows-10,comp.mobile.android,alt.os.linux on Fri Oct 9 06:32:40 2026
    From Newsgroup: alt.os.linux

    On Wed, 7 Oct 2026 12:10:49 -0300, Maria Sophia wrote:

    It shouldn't have crashed, but it's probably a database schema
    mismatch.

    I see no mention of what errors appear in the logcat.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Maria Sophia@mariasophia@comprehension.com to alt.comp.os.windows-10,comp.mobile.android,alt.os.linux on Fri Oct 9 11:19:18 2026
    From Newsgroup: alt.os.linux

    Lawrence DoOliveiro wrote:
    It shouldn't have crashed, but it's probably a database schema
    mismatch.

    I see no mention of what errors appear in the logcat.

    Hi Lawrence,

    Wow!

    Thank you for asking! You are simply amazing. And I mean that very much.
    Nobody is like you in terms of understanding what I would have done.

    Because I didn't even mention I had run a logcat.
    You simply *knew* that I would have run it.

    Because it's the normal way to debug when using adb every day.

    Wow! 99% of the time, people don't understand much about any Usenet post.
    But you understood fully.

    Very clever of you to ask for logcat results. I don't think I even
    mentioned the logcat, but of course I ran it as part of my debugging.
    adb logcat -d -s AndroidRuntime:E

    But I didn't include the results which implied the sqlite schema was off. Because of two reasons:
    a. Most people would never have understood a word of it, and,
    b. In th eend, I ditched PulseSMS in favor of Google Messages for her.

    Note: I still use PulseSMS 5.4.6.2816 & it works fine on the same
    A32-5G model phone with the same Android 13 software.

    Luckily, I had kept a running log of my debugging, as I was gonna write a tutorial to help others install the best version of PulseSMS out there.

    Here are my logcat results that I had put into my debug log at the time.

    adb logcat -d -s AndroidRuntime:E
    --------- beginning of crash
    10-06 21:17:37.628 6301 6301 E AndroidRuntime: FATAL EXCEPTION: main
    10-06 21:17:37.628 6301 6301 E AndroidRuntime: Process: xyz.klinker.messenger, PID: 6301
    10-06 21:17:37.628 6301 6301 E AndroidRuntime: java.lang.RuntimeException: Unable to create application xyz.klinker.messenger.MessengerApplication: android.database.sqlite.SQLiteException: Can't downgrade database from version 20 to 18
    10-06 21:17:37.628 6301 6301 E AndroidRuntime: at android.app.ActivityThread.handleBindApplication(ActivityThread.java:7624)
    10-06 21:17:37.628 6301 6301 E AndroidRuntime: at android.app.ActivityThread.-$$Nest$mhandleBindApplication(Unknown Source:0)
    10-06 21:17:37.628 6301 6301 E AndroidRuntime: at android.app.ActivityThread$H.handleMessage(ActivityThread.java:2400)
    10-06 21:17:37.628 6301 6301 E AndroidRuntime: at android.os.Handler.dispatchMessage(Handler.java:106)
    10-06 21:17:37.628 6301 6301 E AndroidRuntime: at android.os.Looper.loopOnce(Looper.java:226)
    10-06 21:17:37.628 6301 6301 E AndroidRuntime: at android.os.Looper.loop(Looper.java:313)
    10-06 21:17:37.628 6301 6301 E AndroidRuntime: at android.app.ActivityThread.main(ActivityThread.java:8762)
    10-06 21:17:37.628 6301 6301 E AndroidRuntime: at java.lang.reflect.Method.invoke(Native Method)
    10-06 21:17:37.628 6301 6301 E AndroidRuntime: at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:604)
    10-06 21:17:37.628 6301 6301 E AndroidRuntime: at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1067)
    10-06 21:17:37.628 6301 6301 E AndroidRuntime: Caused by: android.database.sqlite.SQLiteException: Can't downgrade database from version 20 to 18
    10-06 21:17:37.628 6301 6301 E AndroidRuntime: at android.database.sqlite.SQLiteOpenHelper.onDowngrade(SQLiteOpenHelper.java:640)
    10-06 21:17:37.628 6301 6301 E AndroidRuntime: at android.database.sqlite.SQLiteOpenHelper.getDatabaseLocked(SQLiteOpenHelper.java:512)
    10-06 21:17:37.628 6301 6301 E AndroidRuntime: at android.database.sqlite.SQLiteOpenHelper.getWritableDatabase(SQLiteOpenHelper.java:413)
    10-06 21:17:37.628 6301 6301 E AndroidRuntime: at xyz.klinker.messenger.shared.data.DataSource.database(Unknown Source:22)
    10-06 21:17:37.628 6301 6301 E AndroidRuntime: at xyz.klinker.messenger.shared.data.DataSource.getScheduledMessages(Unknown Source:31)
    10-06 21:17:37.628 6301 6301 E AndroidRuntime: at xyz.klinker.messenger.shared.data.DataSource.getScheduledMessagesAsList(Unknown Source:5)
    10-06 21:17:37.628 6301 6301 E AndroidRuntime: at xyz.klinker.messenger.shared.service.jobs.ScheduledMessageJob$Companion.scheduleNextRun(Unknown Source:25)
    10-06 21:17:37.628 6301 6301 E AndroidRuntime: at xyz.klinker.messenger.shared.service.jobs.ScheduledMessageJob$Companion.scheduleNextRun$default(Unknown Source:6)
    10-06 21:17:37.628 6301 6301 E AndroidRuntime: at xyz.klinker.messenger.shared.util.UpdateUtils$Companion.rescheduleWork(:4)
    10-06 21:17:37.628 6301 6301 E AndroidRuntime: at xyz.klinker.messenger.MessengerApplication.onCreate(Unknown Source:15)
    10-06 21:17:37.628 6301 6301 E AndroidRuntime: at android.app.Instrumentation.callApplicationOnCreate(Instrumentation.java:1266)
    10-06 21:17:37.628 6301 6301 E AndroidRuntime: at android.app.ActivityThread.handleBindApplication(ActivityThread.java:7619)
    10-06 21:17:37.628 6301 6301 E AndroidRuntime: ... 9 more
    10-06 21:19:50.939 18207 18207 E AndroidRuntime: FATAL EXCEPTION: main
    10-06 21:19:50.939 18207 18207 E AndroidRuntime: Process: xyz.klinker.messenger, PID: 18207
    10-06 21:19:50.939 18207 18207 E AndroidRuntime: java.lang.RuntimeException: Unable to create application xyz.klinker.messenger.MessengerApplication: android.database.sqlite.SQLiteException: Can't downgrade database from version 20 to 18
    10-06 21:19:50.939 18207 18207 E AndroidRuntime: at android.app.ActivityThread.handleBindApplication(ActivityThread.java:7624)
    10-06 21:19:50.939 18207 18207 E AndroidRuntime: at android.app.ActivityThread.-$$Nest$mhandleBindApplication(Unknown Source:0)
    10-06 21:19:50.939 18207 18207 E AndroidRuntime: at android.app.ActivityThread$H.handleMessage(ActivityThread.java:2400)
    10-06 21:19:50.939 18207 18207 E AndroidRuntime: at android.os.Handler.dispatchMessage(Handler.java:106)
    10-06 21:19:50.939 18207 18207 E AndroidRuntime: at android.os.Looper.loopOnce(Looper.java:226)
    10-06 21:19:50.939 18207 18207 E AndroidRuntime: at android.os.Looper.loop(Looper.java:313)
    10-06 21:19:50.939 18207 18207 E AndroidRuntime: at android.app.ActivityThread.main(ActivityThread.java:8762)
    10-06 21:19:50.939 18207 18207 E AndroidRuntime: at java.lang.reflect.Method.invoke(Native Method)
    10-06 21:19:50.939 18207 18207 E AndroidRuntime: at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:604)
    10-06 21:19:50.939 18207 18207 E AndroidRuntime: at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1067)
    10-06 21:19:50.939 18207 18207 E AndroidRuntime: Caused by: android.database.sqlite.SQLiteException: Can't downgrade database from version 20 to 18
    10-06 21:19:50.939 18207 18207 E AndroidRuntime: at android.database.sqlite.SQLiteOpenHelper.onDowngrade(SQLiteOpenHelper.java:640)
    10-06 21:19:50.939 18207 18207 E AndroidRuntime: at android.database.sqlite.SQLiteOpenHelper.getDatabaseLocked(SQLiteOpenHelper.java:512)
    10-06 21:19:50.939 18207 18207 E AndroidRuntime: at android.database.sqlite.SQLiteOpenHelper.getWritableDatabase(SQLiteOpenHelper.java:413)
    10-06 21:19:50.939 18207 18207 E AndroidRuntime: at xyz.klinker.messenger.shared.data.DataSource.database(Unknown Source:22)
    10-06 21:19:50.939 18207 18207 E AndroidRuntime: at xyz.klinker.messenger.shared.data.DataSource.getScheduledMessages(Unknown Source:31)
    10-06 21:19:50.939 18207 18207 E AndroidRuntime: at xyz.klinker.messenger.shared.data.DataSource.getScheduledMessagesAsList(Unknown Source:5)
    10-06 21:19:50.939 18207 18207 E AndroidRuntime: at xyz.klinker.messenger.shared.service.jobs.ScheduledMessageJob$Companion.scheduleNextRun(Unknown Source:25)
    10-06 21:19:50.939 18207 18207 E AndroidRuntime: at xyz.klinker.messenger.shared.service.jobs.ScheduledMessageJob$Companion.scheduleNextRun$default(Unknown Source:6)
    10-06 21:19:50.939 18207 18207 E AndroidRuntime: at xyz.klinker.messenger.shared.util.UpdateUtils$Companion.rescheduleWork(:4)
    10-06 21:19:50.939 18207 18207 E AndroidRuntime: at xyz.klinker.messenger.MessengerApplication.onCreate(Unknown Source:15)
    10-06 21:19:50.939 18207 18207 E AndroidRuntime: at android.app.Instrumentation.callApplicationOnCreate(Instrumentation.java:1266)
    10-06 21:19:50.939 18207 18207 E AndroidRuntime: at android.app.ActivityThread.handleBindApplication(ActivityThread.java:7619)
    10-06 21:19:50.939 18207 18207 E AndroidRuntime: ... 9 more

    From that, I had tentatively deduced the issue was likely
    java.lang.RuntimeException:
    Unable to create application xyz.klinker.messenger.MessengerApplication:
    android.database.sqlite.SQLiteException:
    Can't downgrade database from version 20 to 18

    From that I had tentatively concluded when I downgraded PulseSMS 6.6.1.3018
    to version 5.4.6.2816 (which expects SQLite database version 18), the app immediately encountered the database file left behind by the newer version (which is at version 20).

    I assumed because Android's default SQLiteOpenHelper throws a fatal exception when
    attempting a downgrade without a custom migration path, the application
    crashes instantly on launch before it can even build its interface.

    To fix this crash and allow version 5.4.6.2816 to launch cleanly while preserving
    local files, the database version metadata flag inside the SQLite file needs to be adjusted from version 20 down to version 18, matching what the older app code expects.

    I skipped mentioning in the Usenet post that I also installed 5.4.11.2831, which had different issues, so that's really the point at which I punted.

    Given both my wife and I have the same free Samsung A32-5G from T-Mobile.
    <https://i.postimg.cc/Xq5SpS4D/tmopromo02.jpg>
    What's interesting is by me *staying* on the last known good version
    <https://tinyurl.com/pulsesms>
    I avoided all the problems with the database schema uprevving, apparently.

    But she had allowd the Google Play Store to update her PulseSMS to the
    evil versions (which have advertisements) and that up-revved the schema.
    (I think)

    Once she up-rev'd the schema, I didn't have the skills to down-rev it.
    So, at this point, my A32-5G is working fine with the last known good
    version of Pulse SMS, but I couldn't get it to work on her same phone.

    The good news is when she "noticed" she had Google Messages instead of PulseSMS, she asked why, and I told her that PulseSMS is no good anymore.

    She accepted that over simplification.
    You didn't.

    To your credit, you looked for evidence that the schema had changed.
    I'm really not sure if it did, but I "think" it did from logcat results.

    Thanks for asking as it showed two things about you:
    1. You were thinking about the issues in an engineering way, and,
    2. You knew that I would have been doing the same (even as I didn't say so)

    That's really nice to know how much you're on the ball.
    I appreciate that.
    --
    My goal on these Usenet newsgroups is to teach, learn and to help others.
    --- Synchronet 3.22a-Linux NewsLink 1.2