From Newsgroup: comp.mobile.android

1. I have no Android system contacts sqlite database (for privacy reasons).
(Not "my" privacy. But the privacy of people whom I contact.)
It's rude to have a contacts database accessible to others.
2. So I add the names of people to my messenger private space
Klinker Bros. PulseSMS. Version 5.4.6.2816
(last known good version before Maple Media).
3. In the messenger, I search for a name & then press the phone icon.
That calls them.

But if I switch default messengers, that's all lost.
Not the messages. Not the numbers. But the names I associated with them.
Even if I switch back to PulseSMS, they're gone.

So how do we back up contacts stored inside of the messenger database?

This would work you'd think:
Pulse > Hamburger > Settings > Advanced Features > Message Backup
But that asks to "Join the modern world. Create an account."
Fine. But there goes privacy. Not of me. But of my contacts.
It's rude to put other people's names & numbers on the Internet.

This would work you'd think as it's a local "ab" backup which can then
be converted to a tar archive and then we can extract the database.

adb backup -f pulse.ab -noapk xyz.klinker.messenger

WARNING: adb backup is deprecated and may be removed in a future release
Now unlock your device and confirm the backup operation...

Android13, PulseSMS
A full backup of all data to a connected desktop computer has been
requested. Do you want to allow this to happen. If you did not request this backup yourself, do not allow the operation to proceed. If you want to
encrypt the full backup data, enter a password below.
[Do not back up] [Back up my data]
Backup started... Backup finished.
Name: pulse.ab
Size: 47 bytes
SHA256: A6729346170D2D0FA560D884C7ABB08C5E3B9706ECE6FC79C0074A98F067347A

What happened?

Android 12+ silently disables ADB backups for most apps unless they
explicitly allow it. Pulse 5.4.6.2816 (from 2020) does not declare itself backup-friendly under modern Android rules, so Android gives you an empty shell.

So how do we back up our Pulse SMS contacts on Android 12+ with privacy?
--- Synchronet 3.21b-Linux NewsLink 1.2

From Newsgroup: comp.mobile.android

Maria Sophia wrote:

So how do we back up our Pulse SMS contacts on Android 12+ with privacy?

Would downgrading to Android 11 allow adb backup to work again?
Probably. But I'm not doing that for the obvious reasons.

Would rooting help?
Sure. But my Samsung bootloader is not known to be unlockable.

Would installing the latest (Maple Media) PulseSMS temporarily solve the adb-backup problem? No. Starting with Android 12, apps must explicitly set
android:allowBackup="true"
android:fullBackupContent="..."
in order for a non-rooted backup to work, but Maple Media PulseSMS versions don't set that allowBackup flag.

Would using Neo Backup or Swift Backup work?
Maybe.

msedge https://www.swiftapps.org/

https://play.google.com/store/apps/details?id=org.swiftapps.swiftbackup

msedge https://github.com/NeoApplications/Neo-Backup

https://github.com/NeoApplications/Neo-Backup/releases/tag/8.3.16 https://github.com/NeoApplications/Neo-Backup/releases/download/8.3.16/Neo_Backup_8.3.16_release.apk
Name: Neo_Backup_8.3.16_release.apk
Size: 11536103 bytes (11 MiB)
SHA256: CA277EF63C720F79BA6A08BB07434B266C9947ABD9005A92D6B384B444D19686

adb shell pm grant com.machiav3lli.backup android.permission.BACKUP

What seems best is Neo-Backup since it's open source & available to all. Perhaps paired with Shizuku over wireless debugging.

Let's try that next.
--- Synchronet 3.21b-Linux NewsLink 1.2

From Newsgroup: comp.mobile.android

Maria Sophia wrote:

What seems best is Neo-Backup since it's open source & available to all. Perhaps paired with Shizuku over wireless debugging.

Can we back up the PulseSMS database with NeoBackup or Swift Backup
using the adb command to grant the one necessary special permission?

adb shell pm grant com.machiav3lli.backup android.permission.BACKUP

SecurityException: ... not a changeable permission type
Drat. The answer is no on Android 12+ unfortunately.

So let's try Shizuku (which works on-device & no cable after setup)

Disconnect from USB
Reboot the phone.
Unlock the phone
Nova Launcher 7.0.57 (last known good version)
Settings > Apps > Shizuku > Notifications > Allow
Turn off mobile data
Connect to the home Wi-Fi
Go to Developer options -> Wireless debugging
Tap Wireless debugging (the text)
Tap Forget all pairs (if available)
Turn USB debugging -> ON
Turn Wireless debugging -> ON (192.168.1.4:41619)
Open Shizuku and put it on the top of a split screen
Tap Start via Wireless debugging & ut it on the split screen bottom
Pair with device Wi-Fi Pairing Code 649102
Enter pairing code: Pairing successful. You can start Shizuku service now.
IP address & port 192.168.`1.4:38203
Accept the pairing prompt
After that, Shizuku will say:
Shizuku is running

adb shell sh /storage/emulated/0/Android/data/moe.shizuku.privileged.api/start.sh

If that looks easy, it's not because the combination of something
(NovaLauncher UI or Notifications makes the pairing extremely sensitive).
--- Synchronet 3.21b-Linux NewsLink 1.2

From Newsgroup: comp.mobile.android

Maria Sophia wrote:

If that looks easy, it's not because the combination of something (NovaLauncher UI or Notifications makes the pairing extremely sensitive).

Shizuku is finally paired & running but it took about an hour of doing the
same steps over and over and over again. Seriously. It's that sensitive.

Here are idealized steps. ===========================================================
SHIZUKU SETUP: THEORY vs REALITY (SAMSUNG EDITION) ===========================================================

THEORY (8 steps, clean, sane):
------------------------------
1. Enable Developer Options
2. Enable USB debugging
3. Enable Wireless debugging
4. Open Shizuku
5. Tap "Start via Wireless debugging"
6. System shows pairing dialog
7. Pair ¡÷ Shizuku starts service
8. Done

REALITY ON SAMSUNG (actual steps):
---------------------------------------
1. Disconnect USB (Samsung blocks pairing if USB active)
2. Reboot phone (resets stuck ADB daemon)
3. Unlock phone (Samsung hides dialogs on lockscreen)
4. Switch to Nova 7.0.57 (One UI launcher suppresses popups)
5. Enable Shizuku notifications (Samsung blocks pairing dialog if OFF)
6. Turn off mobile data (Samsung sometimes routes ADB over LTE)
7. Connect to home Wi-Fi (ADB requires same LAN)
8. Developer options > Wireless debugging
9. Tap Wireless debugging text (hidden submenu)
10. Tap "Forget all pairs" (clear stale ADB sessions)
11. Turn USB debugging ON
12. Turn Wireless debugging ON (new IP:PORT appears)
13. Open Shizuku in split>screen top (forces popup visibility)
14. Open Wireless debugging bottom (keeps pairing session visible)
15. Tap "Start via Wireless debugging"
16. Tap "Pair device with pairing code"
17. Enter pairing code
18. Accept system pairing prompt
19. Shizuku finally says "Shizuku is running"
20. (Optional) Run start.sh manually for apps that need it

===========================================================
SUMMARY:
THEORY: 8 steps
REALITY: ~20 steps
ROOT CAUSE: Samsung aggressively suppresses system dialogs,
rotates ports unpredictably, and hides ADB prompts unless
the app is visible in split-screen *and* notifications are on. ===========================================================
--- Synchronet 3.21b-Linux NewsLink 1.2

From Newsgroup: comp.mobile.android

Maria Sophia wrote:

Shizuku is finally paired & running but it took about an hour of doing the same steps over and over and over again. Seriously. It's that sensitive.

============================
SAMSUNG SHIZUKU RITUAL
============================

1. Reboot the phone

2. Enable Shizuku notifications
a. Settings > Apps > Shizuku
b. Notifications > Allow

3. Connect to home Wi-Fi

4. Open Developer options
a. USB debugging: ON
b. Wireless debugging: ON

5. Reset wireless debugging state
a. Developer options > Wireless debugging
b. Select "Forget all pairs"

6. Prepare split-screen
a. Open Shizuku
b. Put Shizuku in split-screen TOP
c. Open Developer options > Wireless debugging in split-screen BOTTOM

7. Start pairing
a. In bottom half: select "Pair device with pairing code"
b. Note the pairing code and IP:PORT

8. Trigger Shizuku pairing
a. In top half: select "Start via Wireless debugging"
b. Enter the pairing code
c. Accept the system pairing prompt

9. Confirm service is running
a. Return to Shizuku main screen
b. Look for: "Shizuku is running"

Once Shizuku is running, it stays alive only as long as the ADB-over-Wi-Fi session stays valid, but that session is extremely flaky in and of itself.

============================
WHAT WILL KILL SHIZUKU
============================

1. Rebooting the phone
a. Always wipes the ADB-over-WiFi session.

2. Turning off Wireless debugging
a. Even a brief toggle kills Shizuku.

3. Losing Wi-Fi connection
a. Wi-Fi drop
b. Router reboot
c. Switching to another network

4. Changing IP address
a. Phone gets a new LAN IP
b. Router assigns a new IP
c. Switching between 2.4 GHz and 5 GHz on some routers

5. Turning on Airplane mode
a. Disables Wi-Fi
b. ADB session dies instantly

6. Turning off USB debugging
a. Restarts the ADB daemon
b. Shizuku loses its bridge

7. Forgetting all pairs
a. Developer options > Wireless debugging > Forget all pairs

8. Battery saver or aggressive power modes
a. Samsung may suspend wireless debugging
b. Some models kill background ADB sessions

9. Long idle lockscreen time
a. Some Samsung builds suspend wireless debugging after extended idle

10. Switching Wi-Fi networks
a. Home Wi-Fi to mobile hotspot
b. Home Wi-Fi to work Wi-Fi
c. Any network change resets ADB

Anything that resets ADB, Wi-Fi, or pairing will kill Shizuku.
--- Synchronet 3.21b-Linux NewsLink 1.2

From Newsgroup: comp.mobile.android

Maria Sophia wrote:

Anything that resets ADB, Wi-Fi, or pairing will kill Shizuku.

OK. Now that Shizuku is running (Version 13.5 adb), we can get back to
backing up app data to the local storage.

PulseSMS has three categories of data:
A. Local database
Contains all messages, threads, timestamps, metadata.


/data/data/xyz.klinker.messenger/databases/
B. Attachments
Contains images, videos, audio, files sent/received.
/storage/emulated/0/Android/data/xyz.klinker.messenger/files/
C. App settings
Theme, preferences, account info.

And PulseSMS has two categories of backup:
i. Cloud account mode (syncs to their servers)
ii. Local-only mode (everything is on our phone)

Since we need to use a Shizuku-enabled file manager, we need to grant the
file manager Shizuku access. Managers I have on hand are MiXplorer, Round
Sync, ZArchiver, Ghost Commander, SMT File Manager, FX, Samsung MyFiles,
Amaze & Utilities, X-Plore, OI File Manager & Material Files.

Let's use X-Plore, latest release from September 29, 2025, but note there
is NOTHING written about Shizuku support (AFAICT) on the canonical site.

You just have to know it.

https://www.lonelycatgames.com/download/x-plore_4-44-apk
Name: X-plore_4.44.apk
Size: 13653137 bytes (13 MiB)
SHA256: A84A1467AB4B59F77AD27D1F0049EB1B8B76F93A04475ED3825E760D86A118E8
Allow X-Plore to access Shizuku = Allow all the time

Once permission is granted, X-Plore gains elevated access to:
a. /data/data/
b. /data/user/0/
c. App-private directories
d. Android/data and Android/obb (even on Android 13+)
e. Databases, shared_prefs, internal files of apps
It's not full root, but it's the closest we can get without rooting.

Drat. I added both ZArchiver & X-Plore to Shizuku but I still can't access /data/data (which is one of the most protected folders on Android systems).
--- Synchronet 3.21b-Linux NewsLink 1.2

From Newsgroup: comp.mobile.android

Maria Sophia <mariasophia@comprehension.com> ha scritto:

OK. Now that Shizuku is running (Version 13.5 adb), we can get back to backing up app data to the local storage.

Is there a way to get Neo pointing to SD card or USB storage?

ii. Local-only mode (everything is on our phone)

That's good... but it would be better to save a copy to SD or
otg/USB storage. Don't you think so?
--
Qihe
--- Synchronet 3.21b-Linux NewsLink 1.2

From Newsgroup: comp.mobile.android

Qihe wrote:

OK. Now that Shizuku is running (Version 13.5 adb), we can get back to
backing up app data to the local storage.

Is there a way to get Neo pointing to SD card or USB storage?

ii. Local-only mode (everything is on our phone)

That's good... but it would be better to save a copy to SD or
otg/USB storage. Don't you think so?

Had I been on Android 11 or lower, I'm sure my backup of the PulseSMS data
and settings would have worked, and, by extension, every app's data and settings can be backed up.

But since Shizuku wasn't even working with the file managers which are
known to work with Shizuku (ZArchiver & X-plore), I failed miserably.

It's rare that I fail to do what I want to do, but Android has tightened up
a log since Android 12, so I'm fighting the Palo Alto mothership.

As for your question, I didn't even get to use Neo Backup, but yes,
according to what I've read Neo Backup can acccess both SD storage and
USB-OTG storage through Android's SAF, the Storage Access Framework.

Neo Backup works on any storage selectable through Android's file picker
But Neo Backup can't access either one through direct paths like /storage/XXXX-XXXX/ and Neo Backup cannot use SD cards formatted as internal/adoptable storage.

Here's how to set teh Neo Backup location:
1. Neo Backup Settings
2. Backup location
3. Custom directory
4. Android file picker opens
5. Navigate to SD card or USB drive
6. Choose folder
7. Confirm

Shizuku is optional, it improves backup completeness, but without Shizuku,
and without being rooted, Neo Backup handles only APKs plus limited data.

I haven't used Neo Backup yet though, so all that might be wrong.
--- Synchronet 3.21b-Linux NewsLink 1.2

From Newsgroup: comp.mobile.android

Maria Sophia <mariasophia@comprehension.com> ha scritto:

OK. Now that Shizuku is running (Version 13.5 adb), we can get back to backing up app data to the local storage.

So far so good...

.

Since we need to use a Shizuku-enabled file manager, we need to grant the file manager Shizuku access.

Shizuku doesn't show any button to allow Neo getting the access.
Shizuku will let you enable only the apps in its list (few apps
like Aurora, SAI, Canta, and few others) but Neo is not in that
list.
On the other hand Neo won't show you any app available to backup
without root (a real root).

.

Allow X-Plore to access Shizuku = Allow all the time

Once permission is granted, X-Plore gains elevated access to:
a. /data/data/
b. /data/user/0/
c. App-private directories
d. Android/data and Android/obb (even on Android 13+)
e. Databases, shared_prefs, internal files of apps
It's not full root, but it's the closest we can get without rooting.

Here I understand that shizuku loves X-plore (and ZArchiver) more
than other apps (that shizuku doesn't even show in its app's
list).
--
Qihe
--- Synchronet 3.21b-Linux NewsLink 1.2