Skip to main content
Solved

Getting Kindle Fire to scream

  • October 12, 2012
  • 3 replies
  • 23 views

I just downloaded Webroot on my son's Kindle Fire.  We are trying to use it like a remote alarm clock, so I need to be able to get it to scream.  When I log into the website and go to the page to make it scream, I get an error of
 
"We were unable to contact your device at this time.
Your device will receive the "scream" request the next time it checks in.
Please note that your device must be online to check in and receive the command."
 
It is connected to our Wifi so I don't understand why it won't work.  Any ideas?
 
Thank you

Best answer by MikeR

Hey rHd,
 
This is because non-telephonic devices can still receive Lost Device Protection commands. However, it is not through our primary delivery method, which requiries telephonic features. Instead, we do it through a polling feature where the device receives the command the next time that it checks in online (usually within 30 minutes).
 
The MyWebroot Account may show that it cannot scream immediately with these non-telephonic devices, but it is still possible for the command to be sent through our secondary delivery method.
 
Hope that clears things up. 😉
View original
Did this help you find an answer to your question?

3 replies

Cat
Forum|alt.badge.img+4
  • Retired Webrooter
  • 241 replies
  • October 12, 2012
Unfortunately, the scream feature does not work in a Kindle Fire currently because it doesn't have a phone number and can't receive the SMS command for the device action.
 
It's also not a device that is in your My Webroot account so it can't be given the "scream" command.
 

  • New Voice
  • 8 replies
  • October 18, 2012
It is interesting... I get to scream on my kindle fire just fine. It does take a while though but it works. 
 
Web always give me immediate error when trying to do scream or lock.  not sure why as it finally works after a while.

MikeR
  • Retired Webrooter
  • 1455 replies
  • Answer
  • October 18, 2012
Hey rHd,
 
This is because non-telephonic devices can still receive Lost Device Protection commands. However, it is not through our primary delivery method, which requiries telephonic features. Instead, we do it through a polling feature where the device receives the command the next time that it checks in online (usually within 30 minutes).
 
The MyWebroot Account may show that it cannot scream immediately with these non-telephonic devices, but it is still possible for the command to be sent through our secondary delivery method.
 
Hope that clears things up. 😉

Reply