I have made some more tests regarding the soft reboots and in my view it seem to be a bug and could need a separate thread. The problem: Voice recognition with Google Search (Google Now) reboots the Minix Work around solution (loosing features): Change Location to "Device only" (GPS) At first I thought it was the last update for Google Search the 23rd of October, however when I started to install older versions I saw the problem started with version 3.4 (18.104.22.1683430). That is when they added "Activity Recognition" which is a feature to track what you are doing and use that data for the Google Cards. It is based on the "Location" feature and if you have Google Wear you can hook it up to get even more info (they say). However this is not interesting for us who sit in the sofa with our Minix, To utilize Google Now with their new "cards" you need to put location to "High Accuracy" (GPS, WiFi, Mobile Network). That is when the Minix reboots. Even with "Battery Saving" mode (WiFi, Mobile Network), the device reboots. Since it is less logical it is an issue with the WiFi and it works with the GPS mode, it could mean an issue with the Mobile Network part which make sense since we do not have one, but the settings are still there. Side note: There is not difference if I use Ethernet or WiFi Continuing, I see the only service requesting "Location" is "Google Play Services" which also got an update 23rd of October thinking that might be the cause. I started to install older version of "Google Play Services" but had to stop since it is updated automatically and you cannot disable that in Google Play Store since it is part of the core and does not show. I did manage to install version 5-.0.81 (1250665-038) and the problem still occurred, but this is not proof alone though. To avoid I had an issue with the mic, I tested other apps that works perfectly. For instance Google Translate and Voice Recorder (installed with Minix). Hint: None of these use Location Others has reported Google Map crash in the same way and others say it works. Could it be a difference of Location setting for these people? i.e. "Device only" works and "High Accuracy" crashes? I have made a catlog with debug filter attached (Crash-High-Accuracy.txt). There are some instances linked to Bluetooth and I had soft reboots when I tested some BT headset so I thought there might be a BT bug that interfere. I therefore unpaired the headsets and disabled Bluetooth all together including the setting in Google Now. No difference. I also attached a catlog also with debug filter but where I changed Location to "Device only" (Works-GPS-only.txt). In case it helps to compare when it actually works, since there are some errors in both cases. There is one line that sticks out. "Best location was null"