Categories: Mobile: Android Samsung LG...

SOLVED: The content of this email cannot be displayed on the gear for security reasons

I have a user with an S3 (current build) and an Gear 2 (updated last night) and when he attempts to read his email on the Gear2, the FROM & SUBJECT line appear but when he clicks on the message to read the body, he receives:

“The content of this email cannot be displayed on the gear for security reasons. For details, view this email on your mobile device”

This is caused by the security policy on the Exchange server requiring REMOTE WIPE approval.  Exchange ActiveSync settings like NUMBER OF FAILED ATTEMPTS ALLOWED will result in a remote wipe when that maximum number is exceeded and GEAR does not support remote wipe… yet.

I have reported this through to Samsung Business Support and they tell me they are aware of the issue.  More specifically:

I’ve just sent out the request as a feature improvement to our global CS team in Korea.

So lets see what happens.

View Comments

  • That's confusing to me if its the Exchange Mobile Device Policy (Im the Exchange Admin) why is it not affecting the 4 users my self included that have a moto360 gen1 and 1 user with Moto360 Gen 2, it only seems to be affecting this one user with the Gear s2??

    • Hi C; Microsoft and Samsung have told me they are making changes to get this to function but I have no further information at this time.

      • I have this issue as well and it makes the watch worth about 1/2 or less what I paid for it. How or where can I file a ticket?

        • I an MS Partner so I have access through those channels. I suspect that the real problem is at the Samsung end and so if you want to push it, I would speak with them. :(

  • I too have this issue on my new Samsung Gear S. Will this ever be resolved? This is a deal breaker for me, if it can't be solved I'll be returning the watch.

    • This isn't a Samsung Gear issue but rather an Exchange ActiveSync setting on the Exchange server. I ran into this exact same issue today after our InfoSec team changed the requirements for our mobile devices from a pattern security to pin code.

      As previously mentioned by users if you install the application Nine (which after using it has a better interface than the Samsung Email app IMHO) the Gear is able to see the body of emails again.

  • This post is titled as Solved but I don't see a solution yet. I was hoping this was a security setting issue but after searching the net it doesn't appear to be. Any news on a solution?

    • Well, the only positives I have is that if you put a SIM card into your Samsung Gear, I am expecting this problem to go away. Few people will want to spend the $10 / month that most telco's want for that service so it is not much of an solution.

  • This was the first topic I read when I encountered this issue with my Gear 2.

    I found that you can install another app to manage your Exchange account, I started using Nine and it works excellent so far.

  • Hello guys! Is there any update about this issue? I am having exactly the same error message stated above and I can't seem to find a solution for it. I am using Gear S, thank you in advcance!

    • I have no new information on this from Samsung but I can confirm that I still see the problem on the brand new Samsung Gear S models (the watches with the curved screens) :(

  • I feel like I have wasted allot of money now on a gear watch that is useless. My previous sony smartwatch email worked with no issue. That device does not have remote wipe....

  • I resolved this by using the email app 'Nine' instead. It doesn't observe the same protocols so the email body is also visible.

    Hope that helps.

    • That is a interesting suggestion to install Nine as the email app for the Samsung Phone.... but... how do you then get the Samsung Gear (whatever version : I have a Gear 2 Neo) to receive the notification and actual email to be viewed from Nine?

Leave a Comment
Published by
Ian Matthews
Tags: email cannot be displayed on the geargeargear2samsung
11 years ago

This website uses cookies.