No sound notification on POP3 account

Taildragger22

Member
Jul 30, 2017
6
0
1
I can't get email notification sounds on my POP3 account.

I have a new Moto e4 with Android 7.1 and am currently using the remaining minutes of pay-as-you-go T-mobile account, before switching to Republic wireless. I love the phone and have downloaded Bluemail to link two email accounts, Yahoo, and a local POP3 account. I think all the settings are correct in “Settings”, but I get an email notification sound for the Yahoo account, but not the POP3.

“Do not disturb” is turned off
“Block All” is off
“Show silently” is off
The volume on the phone is at 100%

The only difference between the two accounts is that Yahoo is in “Push” mode, and the POP3 account is in “Fetch” mode, with the fetch interval of 3 seconds. In the Bluemail > More > Settings > Notifications > “Fetch or Manual” part of Bluemail there is a grayed out note that says “Push-not available for POP3 accounts”. My POP3 account is my main mailbox so I sure would like to get it ringing in. Thanks in advance.
 
Welcome to Android Central! The different accounts should have their own notification options. If you go to Bluemail's settings and select your POP3 account, is there a notification option there where you can select the tone?
 
Thanks, Yes. in each account there is "Visual/Sound/Vibrate/LED", and under that option there is Enable Visual Notification, Enable LED Light, Incoming Sound, and Custom Incoming Sounds, as well as Vibrate. Incoming Sound is on, and a Custom Incoming Sound is chosen.
 
Ok, is that custom tone saved to Internal Storage or the SD card? Make sure it's in Internal Storage, in the Notifications directory.
 
Try using the same sound on the Yahoo and the POP3 accounts. If you choose a sound, but the file for that sound is actually empty, you won't get a sound. (Also, checking email every 3 seconds is going to kill your battery very quickly. If you can, change that account to IMAP, then set it to Push. (Then the phone won't transmit anything until there's an email waiting for you. The server will "push" it to the phone and the phone will acknowledge it. [If you get an email every 3 seconds, I wouldn't use a phone to retrieve that account.])
 
Thanks to all:
1) I typed faster than my brain could think. Fetch is set to 3 minutes, not three seconds

2) This is a new phone. When I first put in the SD card, I chose to use it as external storage. Later I changed it to use it as part of the operating system. I don't think any apps or anything were stored on it.

3) I have the same sound programmed for the incoming sound for both my Yahoo acct, and the POP3. The yahoo acct rings in, the POP3 does not. I am somewhat savvy with computers, most are dual booted Win/Linux Mint. I have always used Thunderbird for a mail program, and like it, but have never switched anything from Pop to imap. I really appreciate all the help and hope you will stick with me to get this working. Thanks

PS, (I know this is crazy) but a few times over the last few days I have had the POP3 acct ring in, but I don't remember which tone was chosen.
 
I wonder if it's a Bluemail issue. Can you see what happens if you use the Gmail app instead (or the stock Email app, if there is one)?
 
Well, this is getting interestinger and interestinger.

The people over here:

https://us.community.samsung.com/t5/forums/v3_1/forumtopicpage/board-id/GS8QA/thread-id/1286/page/1

seem to have the same problem with their S8s.

and the people over here:
https://github.com/k9mail/k-9/issues/2357

have discovered that the problem seems to have mysteriously appeared with the update to Android 7.

My phone is less than two weeks old and came with Android 7.1, and I am suspecting that this is the issue.

I did decide to uninstall Bluemail, and went with K-9, which I like, but it has the same problem. I've been away from android for a while (daughter gave me her old iphone), and haven't ever switched POP3 for IMAP, so will wait on that until I find out if the problem is with Android 7. Will keep you posted, and thanks again for the help.
 
It would not be unusual for something like this to be a bug that slipped through the testing process of the firmware. Send feedback to Samsung, and encourage others to do the same.