Hi there! I understand you're experiencing issues with the Tuta app on your Android device running Android 16. Could you share a bit more about what's happening? For example, is the app not opening, crashing, notifications not coming through, or something else?

Once I have a clearer picture, I can guide you with specific troubleshooting steps. Meanwhile, I can mention a couple of common issues users have faced with the Tuta app on Android in 2023:

1. Notification problems where users don’t receive alerts unless the app is open.
2. Some users needed to update the Android WebView component to fix slow or problematic app behavior.

Does any of that sound like what you're dealing with? Also, have you tried restarting your device or updating the app recently?

Crash when open, send error log

Thanks for the details! Since the Tuta app crashes immediately on startup on your Android 16 device, and you want to send the error log, here’s how you can collect and send useful crash information:

1. Check for Crash Reports in Android Settings:
- Go to Settings > Apps > Tuta (or Tutanota).
- Tap on Storage & cache and clear the cache first.
- If the app crashes again, sometimes Android shows a “Send feedback” or “Send report” option right after the crash—if available, use that to send the log directly.

2. Use Android’s Developer Options for Logs:
- Enable Developer Options on your phone by going to Settings > About phone > Tap "Build number" 7 times until you see a message that Developer Options are enabled.
- Go to Settings > System > Developer options and enable USB debugging.
- Connect your phone to a PC with adb (Android Debug Bridge) installed.
- On your PC, open a command prompt and run:
adb logcat > tutalog.txt
Then open the app on your phone until it crashes.
- After the crash, stop the logging by pressing Ctrl+C. This creates a file named tutalog.txt with the crash logs.
- You can then send this log file to support at [email protected] for detailed troubleshooting.

3. App Reinstallation and Update:
- If you haven’t yet, try uninstalling and reinstalling the app.
- Also, check the Play Store to ensure you have the latest Tuta app version.

4. Contact Support with Error Details:
- If you encounter an error message at any point, please copy it.
- Send your email address linked to the Tuta account, the error message (if any), and the log file if possible, to [email protected]. This helps the support team diagnose the cause more quickly.

If you need help setting up adb or capturing logs on your Android 16 device, I can guide you step-by-step!

Are you comfortable with using these steps, or would you like me to assist with specific parts?

Broken Android app

Hi again! Since your Tuta app on Android is crashing or not working properly, here are some focused steps to try based on recent common issues reported by users like you:

1. Update the Tuta App:
- Make sure you have the latest version from the Google Play Store or F-Droid. Sometimes, older versions are blocked or have compatibility problems.2

2. Check Android WebView Version:
- Problems with the Android WebView component have caused crashes or loading issues for some users.
- Go to the Play Store, search “Android System WebView,” and update it.
- If you recently updated WebView and started seeing crashes, try uninstalling its updates to revert to a stable version.6

3. Clear Tuta App Cache and Data:
- Go to Settings > Apps > Tuta
- Tap Storage & cache
- Clear cache first, then if needed clear data (this will reset app settings, so only do if cache clear doesn’t help).

4. Disable Battery Optimization for Tuta:
- Battery optimization can stop background processes needed for the app.
- Go to Settings > Battery > Battery optimization and exclude Tuta.

5. Try Reinstalling from F-Droid (if applicable):
- Some users resolved login or crashing issues by switching from the Google Play version to the F-Droid version of the app.3

6. Check Network and Permissions:
- Ensure the app has all required permissions (Storage, Network, Contacts if used).
- Test on both Wi-Fi and mobile data to rule out connectivity issues.

If after trying these your app still crashes on startup, capturing and sending the error logs as I described earlier would be the best next step to diagnose the problem thoroughly.

Would you like me to walk you through updating WebView or switching to F-Droid? Or assist with sending logs? Let me know!