Based on Play Store bug tracking data, we’ve noticed that with the recent rollout of Android 11 on many newer Samsung phones(and a couple devices from other manufacturers), some users are now being affected by an old bug in Reverse Lookup.
This issue was detected and resolved about one year ago as Android 11 first began rolling out, and has only recently manifested in these Samsung, OnePlus, and Motorola devices. This appears to be affecting a few hundred users who have not updated Reverse Lookup for a very long time.
So, if you use a Samsung, OnePlus, or Motorola device that was recently updated to Android 11, and you’re now experiencing crashes in Reverse Lookup, please check the Play Store and update to the latest version.
Known Affected Samsung Devices as of 9/14/2021:
Samsung Galaxy S20 5G
Samsung Galaxy Note20 Ultra 5G
Samsung Galaxy A71 5G
Samsung Galaxy S20+ 5G
Samsung Galaxy S10
Samsung Galaxy Note10
Samsung Galaxy S10+
Samsung Galaxy Note10+
Samsung Galaxy S21 5G
Samsung Galaxy S20 Ultra 5G
Samsung Galaxy S10e
Samsung Galaxy Note20 5G
Samsung Galaxy S21+ 5G
Samsung Galaxy S21 Ultra 5G
Samsung Galaxy A32 5G
Samsung Galaxy A51 5G
Other Known Affected Devices as of 9/14/2021:
OnePlus 8 5g
Motorola Moto G Stylus
A few hours after this post goes live, Reverse Lookup 3.4.5 will begin rolling out on the Play Store and Amazon Appstore. The update should make it to all users over the course of the next two weeks. The PLUS version of this update will follow within the next 5-7 days.
In addition to the usual minor bug fixes, this release adds support for spam call detection. This is a feature that we’ve been preparing behind the scenes for a while, and we hope our users find it to be useful. Whenever you search for a call within Reverse Lookup, our systems will now use historical data to determine whether or not the caller has exhibited spam-like activity, and if so, will make a note of that on the search results screen.
This has worked well in testing, and we’ll be closely monitoring the system to make sure it’s catching as many spammers as possible.
As usual, thanks again and please let us know if you have any issues or questions.
We’re happy to announce that our hiatus from the Amazon Appstore has come to an end.
Reverse Lookup PLUS on the Amazon Appstore is now updated to parity with the Play Store version.
In addition, the free version of Reverse Lookup is now available there as well.
Reverse Lookup Free:
Reverse Lookup Plus:
Hey all – just a quick note.. after releasing version 3.3.1 over the weekend, we noticed a bug that was causing crashes at launch for a lot of users.
We’ve just pushed out version 3.3.2 on the Google Play Store which should solve this issue, so please be sure to grab the latest version if you’re having trouble.
Thank you and as always, please reach out if you have any comments or questions.
Hi! Today we’re beginning to launch Reverse Lookup 3.3 on the Google Play Store. All users should start receiving this update today. Although the update is fairly substantial, most of the changes are behind the scenes and most existing users won’t see a difference in their day to day use.
So what did change?
New permissions request model – We’re now building the app against the latest Android APIs, something we had previously planned to do as we moved through the second half of the year. What this brings for our users is the realtime permissions request model that was implemented when Android 6.0 launched a few years back. Existing users won’t see a change – you’ve already accepted the needed permissions when you downloaded the app prior to today. New users on devices using Android 6.0 and up will now be asked to grant permissions as they are needed for the first time. The permission requested at app launch is used to build the main screen from your device’s call log. If you don’t grant this permission, you’ll only be able to search for calls by entering phone numbers by hand. The other permission you may be prompted to grant is for writing contacts, which is used when you use the app to block a number.
Permissions cleanup – Prior to this release, we needed to request the permission for writing to external storage as a requirement of the Google Maps API which is used on the location tab in search results. Google Maps no longer requires this permission, so we’ve removed the request from the app.
As always, we’ll be monitoring the launch and quickly releasing fixes for any issues that arise, so you may receive the app with a different minor version number.
Legacy Android Support dropped – Some of these changes have required us to drop support for devices running versions of Android under 4.0, which was released over 6 years ago as of this writing. According to our data, less than 500 users were still on these versions, and while the app version they have will continue to work for now, they will no longer receive updates or support.
As always, thank you for using the app and please reach out if you have any issues or questions.
At this time, there is not.
However, we are exploring the idea of creating a web version that can be used on any device.
Please keep an eye out here or on Google+ for more info when we can share it.
For VOIP numbers it can be hit or miss as they can easily be spoofed and sometimes change with each call made.
Hi, after you lookup a number, on the results screen, press the button labeled “Copy data to clipboard”. After this, you can long press on any text input in Android and a “Paste” button will appear.
You shouldn’t have to do anything special, but sometimes firmware updates can screw with permissions. If you are getting crashes you may want to try uninstalling and reinstalling the app.
If that doesn’t help please get our email address from the app listing and shoot us a message so we can help you further. Thanks!
Sorry, as mentioned in the app description there is no public data available for cell phone numbers, so we don’t know.