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.
UPDATE: This issue has now been resolved. Update 22.214.171.124 is now available to all users in the Google Play Store. We anticipate an update on the Amazon App Store in the coming days.
Those of you who have a Google Pixel device may have begun experiencing crashes in Reverse Lookup during the past couple weeks. This was due to an unexpected change in the Pixel version of Android 11 which recently began rolling out.
We want our users to know that we have already identified the issue and submitted a fix to the play store. Unfortunately Google’s review team is experiencing delays due to the ongoing worldwide pandemic as well as the recent winter holidays, so we’re currently waiting on them to approve the update before we can begin rolling it out. In the meantime, you can avoid this crash by denying call log access to the app – though using this workaround may require you to use the app’s manual search instead of the call log view. After the update is approved and distributed, you can reenable access to the call log.
Please note that this fix has already been approved and rolled out for users of Reverse Lookup PLUS, so if you’re using that version of the app, please ensure you’ve updated to the latest available version.
As always, we thank you all for your support and apologize for any inconvenience. In addition, we would like to wish all of our users a safe and happy new year!
Update 11/8: Though we haven’t received any further contact from Google, our latest update to Reverse Lookup PLUS has been reviewed and approved, so the app is once again live in the store.
Hello all – Today we received word that Reverse Lookup PLUS has been removed from the Play Store. After reviewing the notice we received, we’re confident that this was a mistake and we’ve reached out to the Play Store for assistance in having the app restored. Please rest assured that the app will once again be available as soon as possible and existing users will still have their licenses intact.
We will share more information as soon as we have it. Thank you for your understanding and we apologize for any inconvenience.
After what can only be described as a chaotic start to 2020, we’re happy to announce that we’re pretty much back to normal work here, and Reverse Lookup 3.5.8 has been submitted to the Google Play Store for rollout beginning today.
This release features various minor bug fixes and some tweaks that should result in better results when searching for callers.
In addition, expect the same update to follow closely for Reverse Lookup PLUS as well as the Amazon App Store version.
Thank you all for your patience during this uncertain time and please stay safe.
Short version: If you have a Google Pixel device, you may need to go into Reverse Lookup’s settings, and enable “List known callers” to see your recent calls in the app.
Long version: Over the past few weeks, we’ve had sporadic reports of users with missing calls on the main call log screen in Reverse Lookup. After some investigation, we realized that in all but one case, the users with this issue were using Google Pixel devices.
After obtaining our own Pixel device to test with, we realized that Google’s proprietary dialer app is now labeling most or all calls as they come and go(in some cases, it’s even labeling them with a blank label!). Traditionally, an Android device would only label calls from known contacts, even if some other caller ID service was being used. Because these calls are now labeled, the app sees them as known callers, and, by default, does not show them.
Luckily, the fix to this is extremely simple and already exists in all recent versions of Reverse Lookup. On the main screen of the app, open the menu to access the app settings, and enable “List known callers”.
After you enable this setting, you should see that all of your recent calls are visible once again. We are also pushing an update to the app that will fix the appearance of calls that have received a blank label. That update should be available to all free and paid users beginning this week, with a rollout lasting up to a week.
As always, thanks again for using the app, and please feel free to reach out if you have any questions.
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.
As a followup to the release of our simple Flashlight Toggle app for Bixby, this is a quick overview of how to remap the Bixby button on your device to launch an app of your choice(may we suggest Flashlight Toggle?)
As of this writing, this method is applicable to the following devices:
As many of you know, Samsung recently added the ability to map an app launch to the Bixby button present on their newer devices in their Android 9.0 Pie update.
For a lot of people, the obvious use for that button is to toggle the flashlight, but alas the flashlight on the Samsung Galaxy phones is not an app, and thus cannot be mapped to that button.
In consideration of this, we threw together this tiny application , simply titled Flashlight Toggle, to help solve the issue.
This app serves only one purpose – each time you launch it, it toggles your flashlight on or off with no interruption or visible interface. At most you may see a brief “slide” animation on your screen as the app does it’s thing.
The app is completely free, doesn’t request any special permissions, and works in tandem with the built-in flashlight on your device. We hope you find it useful in creating your own hardware flashlight button on your Samsung device.
Click the banner below to download from the Google Play Store today.
Necessary cookies are absolutely essential for the website to function properly. This category only includes cookies that ensures basic functionalities and security features of the website. These cookies do not store any personal information.
Any cookies that may not be particularly necessary for the website to function and is used specifically to collect user personal data via analytics, ads, other embedded contents are termed as non-necessary cookies. It is mandatory to procure user consent prior to running these cookies on your website.