HELP.md
First of all, address lookup is absolutely not required to get an accurate forecast, since it’s based on your longitude and latitude, not on your address, which is a totally different process.
If it’s still an important matter to you, you can select an address lookup source in the location settings.
Just swipe from right to left on location list, or tap the pencil icon on top right.
The source may be temporarily unavailable, please retry a few hours later. If the problem persists, please open an issue on GitHub.
The source may be temporarily unavailable, please retry later or check your network. If the problem persists and you use a custom DNS, VPN or have a firewall, please check them as well.
For most sources, we only have a limited number of calls allowed for free for all users of our app. If too many users use the same source, the only way to be able to continue using it is to check instructions on the source website to have your own API key. This may be troublesome, but if you have your own API key, the rate-limit will only apply to you (one user vs all users of Breezy Weather).
Regarding the “API access unauthorized”, this error may appear when you subscribed to the wrong product, or you’re trying to use features of the API that your subscription doesn’t allow.
This error happens when app was able to find your longitude and latitude, but unfortunately, the weather source did not find any location close to this longitude and latitude. Unfortunately, the only workaround is to try with a different source or add your location manually.
This error should be reported as soon as possible to GitHub, mentioning the source and the location on which it is happening (or for privacy reasons, a nearby location that has the same issue).
This error means that the hourly times of forecast data and your air quality or pollen data don’t match. This can happen in the following case: You live in India, with a timezone of UTC+05:30. The forecast source you selected reports hourly forecast on the :00 time, while your air quality or pollen source reports on the :30 time (or the other way around).
This error may happen when a source is no longer provided by Breezy Weather. In that case, you will need to add a new location with another source, and delete this location. It can also happen when you switch from the standard flavor of Breezy Weather to freenet one which has less sources supported.
This can mean many things.
If this only happens with one source and not others:
If this is happening will all sources, and presumably with other apps, in the worst case, you may be a victim of a man-in-middle attack.
If in doubt, start a discussion to ask for help.
If the app is installed in a work or private profile, turning off that profile will disable background updates, so if you are in that case and want background updates, make sure to not turn off the profile or move the app to the main profile.
Certain manufacturers implement non-standard Android behaviors, which prevents the app from working properly.
The first thing to try is to whitelist Breezy Weather from battery optimization. From the app, go to Settings > Background updates and tap on “Disable battery optimization” (don’t worry, our background update job is optimized to be very battery-friendly, and you can change “Refresh rate” to “Never” at any time!).
If it still doesn’t work, you can find ways to circumvent aggressive manufacturer behaviors on the Don’t kill my app! website.
Affects locations configured to use one of the following sources: EPD HK, FMI, FOSS Public Alert Server, NCDR, NLSC, WMO Severe Weather
These sources need to parse XML data which are known to be slow on devices with hardened memory allocator (hardened_malloc) enabled.
If you want to avoid the issue, you can:
If you don’t already have a widget, you can try adding one (you don’t need to have it on your main page). On some devices, this may help mimic the old “persistent notification” by avoiding app being killed for no reason, although the widget does not run anything like the old method, it just renders once and updates only on background updates or force refresh from the app.
Otherwise, this “persistent notification” method was based on a foreground service which was running every minute to check if there was something to do.
It is not battery-friendly at all. The worker method that we use just tells Android "we need something to run a task every 1 h 30, but if you are too busy to run it at that moment, you have a 10 minute margin to run it", so it’s much more efficient as Android takes care of running all jobs from all apps by itself at the moment it feels the most appropriate, instead of each app having their own foreground service.
If your manufacturer thinks it’s a good idea to not run scheduled workers but has no problem letting foreground services drain battery, then the problem is the manufacturer, not Breezy Weather, not you.
So we will not bring back/implement “persistent notification” for these reasons:
But more generally, we recommend that you follow steps from “Background updates are not working” section to find a workaround.
Short answer: no.
Long answer: Breezy Weather should honor the “refresh rate” setting from Settings > Background updates. If it does not, have a look at troubleshooting above. If for any reason the background update failed, it will refresh if weather was updated more than “refresh rate time” ago.
If you still want shorter refreshes:
The app name is “Breezy Weather”, however in the launcher we use the translated word for “weather”.
The rationale behind this is to offer a better user experience:
This choice is aligned with Breezy Weather principles to make it easy to use as a new user. Many other apps make the same decision.
For users with advanced needs not happy with this choice, we recommend using a launcher that allows customisation of app names.
As always when there is a major design change, there are early adopters who fully embrace the changes, and more conservative users, with the majority of users being in-between.
If you’ve been using the new design only for a few days, we encourage to give yourself a few more weeks.
Here is why:
Material 3 Expressive is the most studied design system by Google, with 46 studies involving more than 18,000 participants.
Top research takeaways include:
Learn more about the Expressive research
Each new design made by Google is more studied, and always gradually adopted by apps (we almost never see the old Holo design in apps anymore).
With clear design toolkit guidelines, Material 3 Expressive provides a consistent developer and user experience across the Android system and the other apps also adopting it.
Regarding the ability to make an option to switch between the new and old design, it’s not possible, because there were significant technical changes during the migration to get rid of most of the technical debt, which allows for easier maintenance of the app.
Maintaining more than 1 design has a high maintenance cost. We do provide some abilities to customize this design for flexibility, but for more significant changes, we provide the ability to make 3rd party designs, either by yourself or by commissioning someone. If you concretize it, we would be happy if you could share it in the Show & Tell section!