On your Android device, long-press the Q Alerts app icon. Select "App Info". Select "Storage & Cache". Select "Clear Cache".

If you have "Auto Save Media" enabled in the app Settings, open the "Photos" app on your Android. Select "Albums". Select the "Q Alerts Media" album. Delete any images that appear to be blank.

Relaunch Q Alerts.

Support Direct Link: 2-0

Notification Settings: First step, open "Settings" on your Android device. Go to "Apps & Notifications". Then find "Q Alerts" and tap it. Review all of the "Notifications" settings. For users running more recent versions of Android, also be sure to tap and review the section entitled "Q Alerts Notifications". You might also ensure that your device is not in DND (do not disturb) mode or that Q Alerts can interupt when in DND.

Try unsubscribing to alerts and re-subscribing: From within the app, tap the Menu (dot dot dot) and then select "Sounds". In Q Alerts versions above 7.1.2 there is a button entitled "Unsubscribe/Reset All Notification Channels". Once the notice is received, completely close the app via the Android back button from the main listings screen. Go into the app again and it will re-subscribe you to alerts. If this latter option (alternate channel) works for you, please let us know.

If this does not work, repeat the process and select "Yes" after tapping the botton to try the alternate notifications channel. Once again, you will need to close the app and reopen it to subscribe to the new channel.

Aftermarket Launchers: We've only personally has an issue with no notifications showing up in Q Alerts when we installed an after market "launcher" app from Google Play. Once we uninstalled the app and reverted back to the stock Android launcher, uninstalled Q Alerts and reinstalled it again, the notifications began coming in again. If you stopped receiving notifications after installing a custom launcher, we advise doing what we did, at least as a troubleshooting step.

Other Solutions Until Resolved: In order to help ensure that you get alerts as you are working to solve whatever issues are causing you to not get alerts, if you are running the paid version of Q Alerts, you can also install Q Alerts LITE and see if that at least gets you notifications. Of course if you are running the LITE version you could purchase the paid version and run them both. You can run both versions on the same device with no issues. Another thing that you can do if running Android is, open Google Chrome on your Android device and visit https://qalerts.app/. Then tap the "Bell" icon (bottom-right). This will allow Chrome to alert you when Q drops, even if your browser is not open.

Interferring Unrelated App(s): It is worth noting that in some of our searching, some users (of other apps) reported that the app in question stopped receiving notifications after they installed another unrelated app. It then began working again when they uninstalled the unrelated app. You might think back to what (if anything) you've installed since the last time Q Alerts notifications worked and try uninstalling that app... at least as a test.

Tech Support Test Alert: Starting with Q Alerts version 7.1.2 you can now send yourself a test alert to test notifications. Within the "Sounds" menu within the app, tap the "Request Test Notification" button. It *seems* that this has helped a couple of users.

Nothing to do with an app update: If you stop receiving alerts, it has NOTHING to do with an app update as we do not change the notifications code when we release updates... no need to. The notifications system is easy... we just send your unique token and to Google Firebase and they handle it from there. Keep in mind, if we did and that broke something, we would be receiving a good ten thousand emails not just one.

Change the sound: IF you are lucky enough to be running an Android version where Q Alerts allows you to choose from which sound that you like from within the app "Sounds" screen, try changing to a different sound. We suggest default.

Battery Optimization: Search Android Settings for "Battery Optimization" and turn optimization off for Q Alerts. Some Internet articles have suggested this worked for some users of other apps that ceased to receive push notifications.

Battery Saver Feature: For one user, he states, "It was the low battery saving feature. Once I opted out, it was fixed".

Android Issues: The long and the short is, Android has issues, especially when it comes to push notifications! Just do a Google search for "no longer receiving Android push notifications" and you'll find a plethera of issues for all kinds of apps and devices.

The truth of the matter is our app and the server scripts that send notifications work off of just one or a few very simple lines of code. The long and the short is, the app just sends your unique device token as well as the topic/channel name you want to subscribe to (qalerts, qalertsfree, qalerts1, qalerts2...) to Google Firebase Cloud Messaging. The server script sends one line of simple code (topic, title, content, sound, vibrate, etc) to Google Firebase Cloud Messaging. They then handle sending the notification to each token that is subscribed to that topic.

Other than the few user settings mentioned at the beginning of this section, this is clearly an Android and/or Google issue! It is NOT the Q Alerts app period, otherwise it wouldn't work for 99.9999% of users. There is not much we can do so please do not leave us a scathing review because we can't fix Android/Google nor spend 8 hours helping you troubleshoot your Android device issues for $.99-$2.99 (chances are slim it would do any good anyway). Believe it or not, it bothers us if something is nothing working, bothers us badly, however, there is nothing that we can do. Article after article on the Internet is ridden with users who can't get this fixed on a wide variety of apps and devices. With all of that being said, with tens of thousands of users, to date we've only had around 10 users have this issue and it seems to only come up for a single user maybe every 4-8 weeks or so and then all of the sudden, weeks later, for often no apparent reason, they email us and say it started working again. Go figure.

Good luck Patriot! Wish we could be of more help!

Support Direct Link: 2-1

From time to time Q will insert a post somewhere beneath the most recent post. This is generally from the PatriotsFight (Q and Whitehats only) 8chan board. This may become more frequent as the storm ramps up and Whitehats use the Patriots Fight board to communicate regarding operations. They may also undelete "marker" posts on that board as they become relevant. There are all kinds of reasons Q may delete a post, reactivate one or insert one.

When this happens, it may throw the numbering off. You may get an alert because the numbers increased on the servers (and other sites), but since it is an insert, depending on how far down it was inserted, the app may not update your locally stored database with the new sequential post numbers. This is because the app generally does NOT download all of the thousands of posts each time you refresh the list. If it did, rest assured we would hear non-stop from many tens of thousands of users about it ;-/. People are very passionate about their "Q", as are we and as we all should be. We all thank you Q by the way.

Let's say the app downloads the most recent 5 posts when you open it, but Q inserted a drop 7 drops down. The app would not have downloaded sufficient posts to renumber your locally stored database properly.

To fix this issue, just tap the more menu and select "Force Full Refresh". After doing this, you may be able to see which post was inserted (if one was inserted) by scrolling down through the list and seeing what post(s) further down are maked as unread.

Keep in mind, this is not something that affects websites such as QAlerts.app, QAnon.pub or QMap.pub since in those cases the posts you are viewing are not stored in a database local to the end-user. However, in the case of websites, it's not possible to easily see which post(s) was inserted either since they can't track what you have read and what you have not.

Enjoy the show! WWG1WGA

Support Direct Link: 2-2

For more information click here. For alternatives see the menu item "Q Alerts for Apple iOS" as well as "Other Q Alerts".

Support Direct Link: 2-3

At times Q goes dark. This can be for days, weeks and on occasion months. This is why you have not received any notifications recently and why no new posts are showing up. You can always confirm this via sites such as QAnon.pub, QAlerts.app/, QMap.pub or QAnonPosts.io. When Q posts, you will receive a notification and the latest Q posts will be displayed.

This is NOT a game! We do not control the Q military intellegence team nor when they post. They disseminate information when THEY tactically see fit and according to THEIR plan/timetable, not for our amusement. Keep in mind, we are all encouraged by Q to "Think For Ourselves" and "Research For Ourselves". Therefore, during times of Q darkness, it is always a good idea to re-read past drops (we already have much more than we know), continue to research and also to educate others in order to bring them into "The Great Awakening".

WWG1WGA!

Support Direct Link: 2-4

Occasionally we get support emails from users who saw a new Q drop come in litterally seconds ago and think that the app is broken since they haven’t received an alert yet. Our servers check for new posts every few minutes so as not to take advantage of the source data sites that so graciously host data for the cause. Additionally, all of the source data sites only complile the latest data every minute or few. Just be patient.

For Android users, we have noticed in very rare situations, Android devices simply for no reason decide to no longer deliver alerts to a particular device. See the topic "I'm not receiving alerts (push notifications)" listed further above.

Support Direct Link: 2-5

At times users may get an alert of a new post yet the post isn’t yet showing up in Q Alerts. Just give it 60 seconds or so and use the refresh button or pull the list down to refresh.

Many Patriot sources write and run server scripts to scrape the chans and aggregate the data from multiple boards into a combined file. These scripts generally run between every 1 to 3 minutes or so. There is always a possibility of a bit of a lag as data propagates the various servers. There isn’t a realistic method to do this in real-time without being disrespectful of our fellow Patriots servers. If scripts were to run every second that would create more problems since the remote file to be read would constantly be being written to disk.

Also keep in mind, all things Q come under attack periodically. There have been many cases where source data sites have went (or have been taken) down or have experienced other outages and attacks. Sometimes it takes time for various sites and products to get things back up and going again. If things are down for more than 10 minutes or so, it may not hurt to send us a support email so that we can look into it. It is possible we are not aware (yet).

Additionally, from time to time we will send an alert notifying users of a new app update or in rare cases an outage. If you somehow missed the alert and are confused because no new Q post is showing up, send a support email and the auto reply message should have the latest notification listed.

Within the app, compare the top-most post number (e.g. 2753). Then open a site such as QAnon.pub or QMap.pub and see what the highest post number is that is listed on those sites. If theirs is something like 2753 and yours is something like 4200, then somehow, possibly an internet hickup, went south and you have many duplicate posts stored in the database. The few users who have run into this had to use "Force Full Refresh" to see the latest post, and it had a much higher post number than it should have had. To correct this, use "Reset Database" from the main menu. Pay close attention to the warning message that is presented.

Support Direct Link: 2-6

For more information click here.

Support Direct Link: 2-7

This is due to a couple of the source images being horrendously large. Since all images are now hosted on our servers, they now are scaled to be no wider/higher than 4096 pixels. Be sure you are running version 6.2.7 or above. If you have "Auto Save Images" enabled and you have previously viewed Post #128 or #132, the images have been saved to your devices SD card. Open an app such as "ES File Explorer" or another advanced file explorer app and search your device for the folder "Q Alerts Media". Within that folder located and delete the following images: "128(1) 1510280445405.jpg" and "132(r1) Q Graphic.png". Once deleted, when you view those two posts again they should download again at the smaller sizes and the problem should be resolved.

Support Direct Link: 2-8

The movement is much larger than portrayed, and Q followers are passionate. When a new Q post comes in, imagine, the vast majority of users all hit the server all at the same time. Just relax. You'll see that most all other times the refreshes are extremely quick, especially considering the massive amounts of data being loaded.

Users are hitting the server not only from Q Alerts for Android, but Q Alerts for iOS (those who were lucky enough to get the app before Apple banned it), users using the web version and users visiting it from the web-based notifications system (see the bell icon that is displayed on supported browsers and OS's). We aren't Amazon, Google or Microsoft... we don't have a 10 billion dollar server farm and hundreds of employees. Relax :).

Support Direct Link: 2-9

The movement is growing. When Q initially makes a new drop, a multitude of users all hit the servers all at the same time which can cause any server to become sluggish. Many of us have seen sites, 8chan included and even government sites go down due to the massive traffic Q can bring to them all at once. Rather than having users wait it out via a long timeout (such as 30, 45 or 60 seconds), the app gives 5 seconds to obtain a response from the primary server and then tries a secondary resource for the post data. If that one times out, it tries a tertiary fallback resource. We do our best to think way ahead and plan for a multitude of senarios and fail-safes.

Support Direct Link: 2-10

In Q Alerts version 8.6.7, tap the right menu item within the app (the 3 dots) and select "Settings". Find "Reconcile Database" and tap it. In version 8.6.8 and above, "Reconcile Database" has been removed and the reconcile feature has been implemented within "Force Full Refresh" from the main menu.

In most cases, any errors may take some time to correct on the server end. Therefore, give it some time and periodically use "Force Full Refresh" to see if we have been able to make the corrections to the server files yet. Once that is done, the corrections should be applied to your database with "Force Full Refresh".

You should not need any alternate methods, however, should you, the following are more extreme options: 1) Open "Settings" from the main menu. Select "Reset Database". Please read all cautions. 2) View a problematic post (such as each duplicate) and use "Delete This Post" from the post menu. The system will automatically add any valid post back, therefore, you will have to keep at it until you get the problem one removed.

Support Direct Link: 2-11

In the unlikely event that you find a bug or software glitch, use the upper right hand menu, select "App Version/Support" and then "Email Support". This option also emails us details about your configuration that will better aid us in helping you. Within the email please describe the issue in decent detail and also take and attach screenshots if possible.

Support Direct Link: 2-12

Google Play allows you to use the app for up to 48 hours and get a refund if you are not satisfied with it. You can automatically get a refund by clicking the "refund" button on the app listing in Google Play. We do not issue refunds for the tiny $2.99 USD amount (in some older cases and cases of sales, much less) after 48 hours. 48 hour is more than enough time for a user to try the app and decide if it is what they're looking for or not. Besides, for that tiny amount of money, the user got $2.99 worth of value using the app for two days. For more information on Google Play's refund policy click here.

Support Direct Link: 2-13

1. Clear Cache
1. Long-press the app icon on your Android device and select "App Info".
2. Tap "Storage & Cache".
3. Tap "Clear Cache".
2. Force Full Refresh
1. Launch the app.
2. Tap the three vertical dots.
3. Tap "Force Full Refresh"
3. Change Max Posts to Show
1. Launch the app.
2. Tap the three vertical dots.
3. Tap "Max Posts to Show"
4. Try a few different options and see if that helps.
4. Reset Database
1. Launch the app.
2. Tap the three vertical dots.
3. Tap "Settings"
4. Scroll towards the bottom and select "Reset Database". Be sure to read the sub text warning about losing data. You will more than likely lose any custom data you have entered such as favorites and notes. You CAN export these for manual reentry later via "Export Post Analyses".
5. Uninstall & Reinstall
1. Long-press the app icon on your Android device and select "App Info".
2. Tap "Uninstall". Note: You will more than likely lose any custom data you have entered such as favorites and notes. You CAN export these for manual reentry later via "Export Post Analyses".
3. Install the latest version from here.

Support Direct Link: 2-14