Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Signal folder not visible on Nexus 5x when connecting via USB to Windows computer #7760

Closed
4 tasks done
ahelwer opened this issue May 3, 2018 · 12 comments
Closed
4 tasks done

Comments

@ahelwer
Copy link

ahelwer commented May 3, 2018


Bug description

I am attempting to use the backup/restore workflow specified here to transfer my Signal messages from my old Nexus 5x phone to a new phone. Under the "How do I move messages to my new phone?" section, step 2 says to transfer the "Signal" folder from your old phone to your new phone (along with a disclaimer that the process varies by phone/OS). On the Nexus 5x running Android 8.1.0, the Signal folder is not visible from Windows Explorer, even when specifying that hidden items should be shown. The signal folder is visible from the Android file system explorer, including all backups contained therein. This reddit thread indicates other users have encountered this issue.

Workaround: On your Nexus 5x, go to Settings > Storage > Files and open the Signal directory. Move or copy your Signal backups to the Downloads folder. Connect your Nexus 5x to your computer, and then copy the Signal backup from the Nexus 5x downloads folder to your own computer in preparation for transfer to your new phone. Note that the Signal backup files might show up as 0 KB in size from Windows Explorer; disconnecting then reconnecting my phone to my computer fixed this issue, and the Signal backup files were sized as expected.

Steps to reproduce

  • Create backup from Signal Settings > Chats and Media > Chat backups on your Nexus 5x Android device
  • Connect your Nexus 5x to a Windows computer via USB
  • On your Nexus 5x, use the USB connection alert to enable file transfer between your computer and device
  • Open Windows Explorer and navigate to the root "Internal shared storage" directory; note absence of Signal directory
  • On your Nexus 5x, go to Settings > Storage > Files and note the presence of the Signal directory (and backup(s) therein)

Actual result: Signal directory is not visible from Windows explorer, hindering attempts to backup/restore Signal messages on another phone.
Expected result: Signal directory is visible from Windows explorer, enabling easy copying of Signal directory onto your computer and then onward to your new phone.

Screenshots

Windows Explorer view (note Hidden items is checked)

Android file explorer view

Device info

Device: LG Nexus 5x 32 GB
Android version: 8.1.0
Signal version: 4.18.3

Link to debug log

https://debuglogs.org/9ac618bbe6bdf40c02e730a3d6c4c8f25b377bc2a109af36a548d797fc32c2ba

@ahelwer
Copy link
Author

ahelwer commented May 3, 2018

Secondary minor bug (or gap in the restore instructions) - on my Nexus 5x, the directory structure was /Signal/signal-xxxx.backup but in order to be auto-detected as a backup on the new phone the directory structure must be /Signal/backups/signal-xxxx.backup.

@igor2x
Copy link

igor2x commented May 13, 2018

I agree it is big annoyance you can't quickly copy/paste data to new device, but this issue in my humble opinion does not satisfy the new rules condition for opening bug report: If you disagree with the way that a feature is working that's not a bug.

May I kindly suggest this issue to be closed down as bug report and invite you to continue discussion on community forum.

@ahelwer, I also have Nexus 5x and from Setting | Storage | Files I can see Signal/Backup directory and backups stored in there.

Also if Signal directory is seen with Android file explorer and can't be seen with Windows explorer this may be an issue in Windows file explorer (or USB driver or similar) not displaying directory. You assumption is that Signal has done something to hide an directory. In my humble opinion assumption is not enough to open a bug report. In such corner cases I would like to invite you to open an issue on community forum instead and community discussion will provide an answer if this qualifies for bug report.

@Signal-Android maintainers, if you feel this reported issue does not comply with new bug reporting rules, please close down the bug report in hope discussion will continue in Signal's community forum.

@ahelwer
Copy link
Author

ahelwer commented May 13, 2018

The bug here is that I was attempting to follow the backup/restore instructions and ran into two separate pitfalls which likely would have frustrated a less-technical user and kept the feature from working. I don't "disagree" with the way the feature works, I am reporting that the feature does not work as documented. Either the documentation is wrong or the feature has a bug. In complicated features like a backup-restore workflow involving, at minimum, two separate mobile devices (possibly with two separate mobile OSs) and a computer running a fully different OS, these tiny rough patches are absolutely bugs that must be fixed in order for the feature to work.

As an aside, even if the directory display bug is on Windows file explorer's side (a pretty big assumption given the relative software maturity of the two parties under discussion) other apps have no problem revealing their directories to Windows explorer and working around this hypothetical bug. Signal is taking a dependency on Windows explorer for their backup-restore feature, so it also should work around this hypothetical bug.

@piratenpanda
Copy link

Same for me on Arch Linux so definitely not a problem with Windows Explorer. I need to boot to TWRP to restore the backup so I'd also like to see this fixed for not so technically inclined people.

@igor2x would be nice if you'd actually read and understand the bug report and not act like some kind of authority which you are not. The bug is annoying for everyone and not only Windows users.

@Hormesis
Copy link

I've had the same issue across multiple phones. An invisible folder is very much a bug, not a feature.

@siccovansas
Copy link
Contributor

siccovansas commented May 16, 2018

I think this might not be a Signal issue, but rather the following Android issue: Android MTP support does not show recent files until the device is rebooted.

To be sure that this is the problem. See if you can see the Signal folder and its files after you rebooted your phone.

My fix to avoid rebooting my phone is to run SD Scanner (F-Droid, Google Play) after I created an export/backup (this problem also happens if you e.g., export your phone's contact list) and the folders/files will show up on the file explorer on your computer.

@ahelwer
Copy link
Author

ahelwer commented May 16, 2018

Neat, thanks @siccovansas ! I'll try testing this theory on my phone when I get a chance. I don't have my Nexus 5x anymore, but maybe I can repro the invisible folder issue on my new phone then see if rebooting fixes it.

@piratenpanda
Copy link

Seems indeed to be the problem @siccovansas

@2-4601
Copy link
Contributor

2-4601 commented May 17, 2018

Thanks for confirming. I haven't tried the new backup feature in Signal but I've run into this Android bug @siccovansas referenced to many times.

@2-4601 2-4601 closed this as completed May 17, 2018
@haffenloher
Copy link
Contributor

As this "SD Scanner" app mentioned by @siccovansas doesn't seem to require root, maybe there's a way for us to do the same thing this app does to work around the Android bug? If not, this problem and the non-trivial workaround (rebooting your phone) should at least be mentioned in a support article.

@2-4601
Copy link
Contributor

2-4601 commented May 17, 2018

@StrawberryPearl
Copy link

@ahelwer I need to tell you, your post saved my sanity. I was switching from a Droid Moto to a Pixel 3a and I nearly lost my mind trying to figure out how to get the Signal backup file from the old phone to the new phone. It is absolutely a bug in Signal - there is no way it needed to be as difficult and time consuming as it was. Thank you, thank you, thank you, a million times, thank you.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

8 participants