Is there a find device app as an alternative to the google “find device” function
with which you can control the cell phone (delete data, ec,)?
There is an app “Find my device” in the F-Droid store, but I have not had such good experiences with it - was perhaps also due to the device-
seems /e/OS works on something to provide this from the get go - if you search the forum and sort by recently there are some relevant posts. I’d probably just wait
I read about it somewhere here in the forum, I believe they’re working on something fully functional for the upcoming major revision next month. I’d see how that pans out.
It’s a fairly critical function for me as well so I’m glad it’s in the pipeline.
In /e/OS 3.0 beta, it’s natively implemented
No locations were sent. it dosen t work on my device.
Dear @Manoj,
I’m also facing this issue that “Find my Device” is not working for me. I’ve successfully configured the service, but as soon as I send the secret via SMS to my device, no location is sent back. However, I can confirm that “something” happens, because as soon as the SMS with the secret arrives, the following message pops up:
Do you have any ideas what might be wrong here?
Thx and have a great weekend!
FP5 + /e/OS 3.0.1
I configured the code for getting the location of my FP5, then tested it sending the code via SMS from another smartphone.
I received the “calling” SMS with the code and a notification appeared on my FP5 with the message “Background localzation…”. This notification never close automatically, and the SMS with localization info is never sent back.
I checked the code many times.
I checked the active state of geolocalization feature.
I also have another smartphone (Google Pixel 6a) with /e/OS 3.0.1, so I did same tests with it, but it gave me no problem and sent me back the localization SMS.
Any suggest?
I am experiencing similar problems. /e/OS 3.0.1 on FP5.
The SMS arrives, but the phone does nothing with it (that I can observe) and there is no automatic reply.
(This feature is also not documented. Why not? How am I supposed to troubleshoot?)
I’m also facing this issue, maybe let’s continue our discussion here at the other thread.
You can find the guide on Find my device here
Any ideas what might be the problem, @Manoj? Imho all requirements from the docs are met in my case 
In this thread Testing: Find my device...FMD...anyone tried and know if fake location is disabled - #2 by aibd
I walk though the output of
$ adb shell dumpsys location
Maybe see if the output of that command suggests anything.
Before I activated FMD I felt more secure with limiting SMS sending by any App to manual confirmation. With FMD I needed to change the SMS limitation to 5 per minute. After that the location is sent automatically.
You can search the option “SMS limitation” and set a value. Maybe it works for you.
With the Xiaomi Redmi Note 10 Pro phone, the Find My Device app returns the code sent from the other device instead of the coordinates.
Of course, location data is enabled, fake geolocation is turned off, and for example the Maps app works perfectly. FMD does not work—that is, it doesn’t function as it should.
I updated the system from 3.1.1 to 3.1.4, but the Find My Device app has become even more buggy. Now it doesn’t even send the code back to the sender’s device. Instead, the code arrives as a plain SMS, and the phone plays a notification sound when the SMS is received. Meanwhile, the text “Find my Device by SMS Tracking location in background” appears on the screen.
Is there already a solution for this problem? It seems I’m not the only one for whom this isn’t working.
I also noticed that in the Location Settings, where you can normally see which apps have recently accessed location—such as Maps or BlissWeather—the Find My Device entry doesn’t appear at all, even though I would expect it to. I suspect the issue might be that FMD doesn’t have access to location, and there’s no setting that lets me grant location permission to that app.
Works very well here, accurate to approx. 5-10m.
I’m glad it’s working for you—that gives me hope it’ll work for me someday, too. Which device and which version of /e/OS are you using?
Maybe you could try as Post #13 and having read the linked walkthrough, pastebin the output here.
FP5 with Android 13 and e/OS 3.1.4