Differences

This shows you the differences between two versions of the page.

--- troubleshooting:start [2026/03/28 12:04] – fixed links phobos
+++ troubleshooting:start [2026/03/28 12:25] (current) – Formating phobos
@@ Line 6: / Line 6: @@
 This page does not cover network related issues, see the [[:setting_up_cell_networks#troubleshooting|network troubleshooting]] section for related assistance.
 </note>
+----
+==== Notifications ====
+=== SMS ===
+If you are on the [[phones:kyocera_digno_keitai_4:|]] in particular and are having trouble receiving texts, or are having them not be received, see the [[mediatek_sms_whitelist_issues|]] page.
+=== Missing app notifications ===
+See [[#Apps being killed|]].
+----
+==== Apps being killed ====
+Due to these phones usually having only 1 GB of RAM, the phone has trouble with keeping third-party apps open. Due to the low specs, the phones are optimized to kill background apps when memory is low, or in order to save on battery.
+It should also be noted that at least on Kyocera models, the "Power/Hangup" button will destructively exit the app, causing it to be killed, this is in contrast to the "Back" key which will exit the app instead.
+These issues can be mitigated by turning off "Battery Optimization" for specific apps in the settings, as well as turning off automatic battery saver mode. See the website [[https://dontkillmyapp.com/|Don't kill my app!]] for information on the subject.
+However, even after setting this, apps can still be killed in the background if too many apps are open, leading to needing to open the apps again to bring them back into the phone memory. It is suggested to not have too many applications, or too heavy of applications running on the phone because of this. You can see what applications are taking up memory in Developer Settings, as well as battery life in the [[:android_settings_menu|]].
+If you are on a rootable device such as the [[phones:kyocera_digno_keitai_4:|]], you may opt to use the [[phones:kyocera_digno_keitai_4:systemizing_android_apps|Systemizer]] Magisk module in order to keep important applications alive in the background.
+----
 ==== Lock screen ====
@@ Line 26: / Line 53: @@
 Additionally, if the default keyboard has been [[:debloating_apps|debloated]], open UAD and restore the ''jp.co.omronsoft.iwnnime.ml'' package and try the above commands again.
+----
 ==== App crashes ====
@@ Line 34: / Line 63: @@
 Experienced on the: A202KC (1.000AL Rooted)
+----
 ==== Phone crashes ====
@@ Line 45: / Line 76: @@
 Experienced on the: A202KC (1.000AL Rooted), 903KC[(https://www.reddit.com/r/dumbphones/comments/1rmifp7/comment/ob0sp9s/?context=3)].
+----
 ==== Rendering issues (Third-party apps) ====
@@ Line 55: / Line 88: @@
 There seems to be an issue with apps that use [[wp>Flutter_(software)|Flutter]][(https://github.com/ImranR98/Obtainium/issues/2673)]. Apps such as [[https://obtainium.imranr.dev/|Obtainium]] have visual artifacts.
+----
 ==== Bootloop ====
-If your phone is bootlooping it is suggested that you reach out to us on our [[https://discord.gg/hSUkk3NYZe|Discord]] for support.
+If your phone is bootlooping it is suggested that you reach out to us on our [[:start#community|community]] for support.
-If you are on the DIGNO 4 and have the bootloader unlocked it may be possible to flash an image onto the device. We have an archive of dumped images accessible here: https://drive.proton.me/urls/HWQQPZ7WG0#kYU3MkXOBfiq.
+If you are on the [[phones:kyocera_digno_keitai_4:|DIGNO 4]] and have the bootloader unlocked it may be possible to flash an image onto the device. We have an archive of dumped images accessible here: https://drive.proton.me/urls/HWQQPZ7WG0#kYU3MkXOBfiq.