com.android.phone crashing - Samsung Galaxy Nexus

I wasnt sure where to post this as i am not sure whether the problem is with AOKP M5, Tasker, or Secure Settings.
I have a Tasker profile set to pop up a menu when i plug my phone in, and it has 4 different charging options. The task i have when i unplug the phone includes the following...
1. Secure Settings > GPS Disabled
2. Secure Settings > Location Services Disabled
3. Bluetooth > Off
4. Display Brightness > 75
5. Perform Task > Pandora Off
(Just in case)
the Pandora Off task includes...
1. Media Control > Pause
2. Go Home
3. Kill App > Pandora
4. Media Volume > 0
Now i have used all the same profiles and tasks on all the AOKP builds before this, and the problem started when i went to M5.
Here is where it gets weird...
When i unplug the phone, doesnt matter when, com.android.phone crashes. ALSO, when i open the actual Secure Settings app, it crashes there too.
Any tasker task that needs secure settings really will crash it.
I have updated Tasker, and i have updated Secure Settings and Helper. Unknown sources are checked, and Tasker and SS are set as admins in the security menu.
Edit: also want to mention the crash i get when opening the secure settings app happens whether the phone is plugged in or not.
Not sure what else to check. Thanks for any help.

now that i think about it it may be the theme. I am using natemz red theme. Didn't think to mention it because i thought themes were just graphical enhancements.
I found a couple other threads where themes caused similar issues.
Sent from my Galaxy Nexus using Tapatalk 2

Related

Galaxy S3 i747m HOMESCREEN BUG..

I realized that the homescreen has some bugs especially if you disable the lock screen from settings..
It happened a few time in the past few days..
When I click the home button, the device is on, and I do not need to unlock it since the lockscreen is disabled.
Sometimes, after turning the phone screen on, all my homescreen widgets and the bottom shortcut bar(phone,contact,message,menu) would start to flashing like crazy...
The phone is still responsive, e.g. opening menus, change settings, top menu bar still slides down and up fine, everything is fine operationally except for the flashing widgets and bottom shortcuts..
I turned the screen off and back on, same flashing is present..
I have to power off the phone or restart the phone and it will return back to normal..
I believe this is definitely a software bug... Anyone familiar with this bug?
Are you running stock or are you rooted with a custom recovery?
Sent from my SGSIII with the XDA Premium App
All Stock on my GS3
No recovery mod.
Rogers Samsung Galaxy S3 i747m
Stock Samsung ROM: May 23 build Android 4.0.4 (Rogers Wireless)
My screen lock is turn off btw.
UPDATE:
Also I found out exactly what is triggering this issue..
It has to do with the Developers Options under the Do Not Keep Activities and Background Process Limit..
I am experiencing this issue only when I tick Do Not Keep Activities, and set the Background Process Limit to No Background Process...
Also, today another issue showed up with the same 2 settings ticked Do Not Keep Activities, and set the Background Process Limit to No Background Process.
Basically what it happened is that when I turn on my phone, and open windows such as messages and settings, the phone would automatically attempt to close it down after 2-3 seconds... Also due this time, I received a message, my message tone changed back to the bird chirp default message tone rather than the Pure Bell message tone I setup previously.. When I manage to open the sound settings, I took a quick look and it was still set to Pure Bell, and after a second or so, the phone closed the entire settings window down...
I just press hole the power and click on Restart...
Now the phone reboots, and the phone is back to normal...
When I went back to sound settings, all my own settings are still there
BUT
When I went to the Developer Options, the setting for Do Not Keep Activities, and Background Process Limit where back to the default values.. (Do Not Keep Activities is not UNTICKED, and Background Process Limit is set to Standard Limit automatically by my phone after the reboot.)
I thought it was weird how the phone changed my settings after reboot, and the OS acts weird before I rebooted...
After using it through out today with the default settings for Do Not Keep Activities, and the Background Process Limit, my phone is acting fine.....
Pretty sure this is a SW bug, it is not a HW problem..
I think it did exactly what it should do with those developer options enabled. That was a very aggressive setting use used and does not represent normal operation of the software.
Sent from my Red S3
So this is a known issue?
Yes, pretty much Developer Options are pretty unstable...
The only setting I kept for are Mock Location (for those apps that use GPS without my permission) and the Animation options to 0.5x so the animation is faster.
Turning the Mock Location and Changing Animation Settings do not seem to affect the stability of the Stock ROM
Why on earth would anyone with a phone this powerful want to use those two options anyways!? I would say yes u have those problems with those options on... you have plenty of resources so don't do that to your phone and yes those are "developer options" and typically only temporary testing scenarios for "developers" just leave at default and be happy with much better working phone!
Sent from my SGH-I747M using xda premium
I use those 2 memory clearing options just to extend battery life.

[Q] Talkback will NOT stay disabled...

So i updated to 4.1.2, and now for some reason Talkback will NOT stay disabled or stay removed. I've tried completely removing the app from my phone, and it will still somehow enable itself after a reboot (show talkback notification). Then, since the app was "removed", I have no way of disabling it unless i reinstall the app, then reboot, then go into "Accessibility" and turn it off... Even then, there are still some features turned on, like TTS and highlighting... I've even tried disabling all TTS apps, like Google TTS, Samsung TTS, and Svox TTS... Talkback will still will turn itself on after a reboot... and YES, Driving Mode is disabled...
Anyone have any advice?
That's impossible. If you remove the application using Rom Toolbox lite and you have root access, it will not come back.
Sent from my SGH-T999 using xda app-developers app
re: disable
dansl said:
So i updated to 4.1.2, and now for some reason Talkback will NOT stay disabled or stay removed. I've tried completely removing the app from my phone, and it will still somehow enable itself after a reboot (show talkback notification). Then, since the app was "removed", I have no way of disabling it unless i reinstall the app, then reboot, then go into "Accessibility" and turn it off... Even then, there are still some features turned on, like TTS and highlighting... I've even tried disabling all TTS apps, like Google TTS, Samsung TTS, and Svox TTS... Talkback will still will turn itself on after a reboot... and YES, Driving Mode is disabled...
Anyone have any advice?
Click to expand...
Click to collapse
Try using titanium backup and FREEZE any apps you do not want to run, once you freeze it you will not even see it
in your app drawer. If you change your mind and want to use the app you can always un-freeze it.
Good Luck!
I've tried both uninstall and freeze... it's almost like talkback is built into the framework... I've tried just about everything possible...
TheLastSidekick said:
That's impossible. If you remove the application using Rom Toolbox lite and you have root access, it will not come back.
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
I know right? It's not that the application "came back", but somehow it's being enabled even though the app has been removed... it's showing a "Talkback Enabled" notification whenever I reboot my device. Then when I go to "disable" it... I can't... because the app was REMOVED... WTF... so I'm stumped... it's almost like talkback features have been baked into the framework, and are some how being forced on...? If I can't figure out what the problem is, then I guess I'll just have to wipe and start fresh... as much as I dont want to have to do that...
I've tried to Clear Data for Talkback, and Google TTS. I've Frozen and even fully removed both Talkback and Google TTS. Yet every time I reboot, that damn "Talkback is enabled" notification is back... and it wont go away unless i go in and turn it off... Unless Talkback isn't installed, then I have to reinstall Talkback, and THEN I can disable it to remove that notification... really strange...
dansl said:
I know right? It's not that the application "came back", but somehow it's being enabled even though the app has been removed... it's showing a "Talkback Enabled" notification whenever I reboot my device. Then when I go to "disable" it... I can't... because the app was REMOVED... WTF... so I'm stumped... it's almost like talkback features have been baked into the framework, and are some how being forced on...? If I can't figure out what the problem is, then I guess I'll just have to wipe and start fresh... as much as I dont want to have to do that...
I've tried to Clear Data for Talkback, and Google TTS. I've Frozen and even fully removed both Talkback and Google TTS. Yet every time I reboot, that damn "Talkback is enabled" notification is back... and it wont go away unless i go in and turn it off... Unless Talkback isn't installed, then I have to reinstall Talkback, and THEN I can disable it to remove that notification... really strange...
Click to expand...
Click to collapse
Weirdest thing is I did a Rom where I removed all this bloat and have never even ran into talkback. Good luck, sorry I couldn't help you.
Sent from my SGH-T999 using xda app-developers app
re: talkback
dansl said:
I've tried both uninstall and freeze... it's almost like talkback is built into the framework... I've tried just about everything possible...
Click to expand...
Click to collapse
There are some apps like the play store which you CANNOT uninstall completely or delete, yet when you go into
settings>applications you can delete or disable the updates only for the app.
Perhaps like the play store talkback is also one of those apps, if it is try to uninstall the update to talkback
and then use a app like "system app remover" which has options to uninstall system apps and an option to
FREEZE them.
So first uninstall the talkback update in settings>applications and then find it again using system app remover
and instead of trying to uninstall it freeze it using system app remover.
Other than that I have no other ideas.
Good luck!
Sounds like I might just need to wipe my phone to get this fixed... must be something totally wacked out...
OK, so i found the problem... It's another "accessibility" service I was using that was causing strange issues with Talkback. In my case it was "Pebble Watch" app that was the culprit. I disabled the services for that app, and the issue disappeared. Although... I need this app for my Pebble watch to work... so I guess I will just have to deal with "disabling" talkback every time i reboot my device...
I just don't understand how it was STILL enabling Talkback even after completely removing the app from the device... Really strange issue... My guess is that there are still some "Talkback" features built into the Framework... and somehow my "Pebble Watch" app is triggering those features...
dansl said:
OK, so i found the problem... It's another "accessibility" service I was using that was causing strange issues with Talkback. In my case it was "Pebble Watch" app that was the culprit. I disabled the services for that app, and the issue disappeared. Although... I need this app for my Pebble watch to work... so I guess I will just have to deal with "disabling" talkback every time i reboot my device...
I just don't understand how it was STILL enabling Talkback even after completely removing the app from the device... Really strange issue... My guess is that there are still some "Talkback" features built into the Framework... and somehow my "Pebble Watch" app is triggering those features...
Click to expand...
Click to collapse
I have the exact same issue, also did freeze and uninstall Talkback in Titanium backup and that did not help at all! The only other accessibility service I have running is Llama - after disabling it the issue disappeared - just like your with Pebble Watch. And I like Llama a lot so I will also have to kill that notification at every boot. Darn!
EDIT: It turned out in my case disabling the Llama accessibility service does not affect the app features that I use, so I'm good. Pretty annoying though.
How are you guys figuring out which apps are causing these problems.
I hate seeing that stupid icon in the pulldown every time I reboot.
Thanks
reapur said:
How are you guys figuring out which apps are causing these problems.
I hate seeing that stupid icon in the pulldown every time I reboot.
Thanks
Click to expand...
Click to collapse
If you have ANY accessibility service enabled, you will get the persistent notification at boot. Disabling all accessibility services and then re-enabling removes the persistent notification.
I'm pretty sure at this point that Samsung developers are, quite literally, retarded.
Use Titanium Backup and free Google TTS & Samsung TTS.
OR
From App setting disable above applications.
I tried first option and the issue was gone.
Would you happen to be using Pebble app?
As others uninstalling and/or freezing didn't help. Disabling "Tasker-JB" in Accessibility killed it. Left TTS apps alone. Don't know yet if I broke Tasker. Since Llama is also a problem app, maybe it is related to Location. I do Location by sniffing WiFi AP's so maybe I'm okay. Maddening!
schneid said:
As others uninstalling and/or freezing didn't help. Disabling "Tasker-JB" in Accessibility killed it. Left TTS apps alone. Don't know yet if I broke Tasker. Since Llama is also a problem app, maybe it is related to Location. I do Location by sniffing WiFi AP's so maybe I'm okay. Maddening!
Click to expand...
Click to collapse
It doesn't break Tasker, but it will prevent it from reading to you (notifications, for instance).
Aerowinder said:
It doesn't break Tasker, but it will prevent it from reading to you (notifications, for instance).
Click to expand...
Click to collapse
Great news! I don't want it talking to me anyway.
having similar issues with LMT and Watchit for my Sony Smartwatch. I guess it's just a bug from Samsung.
Solution!
This was posted on the Android Central forums in November by Costas Andriotis. I implemented it and it works to get rid of the talkback notification on boot. You have to leave Talkback installed to disable it on shutdown though.
http://forums.androidcentral.com/t-mobile-galaxy-s-iii/279707-talkback-alert-wont-go-away.html#post3215875
I'm using GoLocker, MissedIt! and Tasker, and I need these enabled in accessibility.
Everytime I rebooted, Talkback was also enabled (known Samsung bug).
I solved this with Tasker + Secure Settings + Secure Settings' Helper, by creating 2 profiles:
Device Boot: Event > System > Device Boot
Tasks:
Wait: Task > Wait (10 seconds)
Flash: Alert > Flash ("Starting boot tasks...")
Enable Go Locker: Plugin > Secure Settings (Helper > Accessibility Services > Go Locker: Enabled)
Enable Tasker: Plugin > Secure Settings (Helper > Accessibility Services > Tasker: Enabled)
Enable MissedIt!: Plugin > Secure Settings (Helper > Accessibility Services > MissedIt: Enabled)
Device Shutdown: Event > System > Device Shutdown
Tasks:
Flash: Alert > Flash ("Shutting down")
Disable Talkback: Plugin > Secure Settings (Helper > Accessibility Services > Talkback: Disabled)
Disable Go Locker: Plugin > Secure Settings (Helper > Accessibility Services > Go Locker: Disabled)
Disable Tasker: Plugin > Secure Settings (Helper > Accessibility Services > Tasker: Disabled)
Disable MissedIt!: Plugin > Secure Settings (Helper > Accessibility Services > MissedIt: Disabled)
What this does, is disable all accessibility services when shutting down (because if any is active, Talkback will get re-enabled), and re-enable them (except Talkback) at boot. If you have different or additional services, you must disable them all at shutdown and re-enable them at boot.
If you reboot normally, all will be well. In case you have an abnormal shutdown, just reboot again properly.
This is a serious Samsung bug, because if you use an alternative lock screen you won't see the SIM unlock screen, and you will be effectively left without the possibility of making calls.
Click to expand...
Click to collapse
talkback clear data
My phone is Samsung Core 2. Accidentally i clear data of google talkback. Now my phone is getting hang...

Tasker - Kill App

I am in the process of configuring Tasker for use in my vehicle to replace my aging CarPC with Nexus 7 2013(MMB29O/rooted). I am currently using Dashdroid as the front end. However, it seems tasker cannot completely kill the Dashdroid app. It still shows as open(when you click the square on the tablet) and not completely killed.
Tasker is set up as such:
Profile > Not Power Any > Tasks > Power Off > Kill App > Car Dashdroid (Use Root On)
Is there a better way to go about this? A way to shut down all apps and go to sleep, etc? Thanks!

How to stop Mobile Manager from killing apps and not receiving notifications

Hi guys,
One of the features i like about ASUS phones is the ability to control apps through the app Mobile manger but the problem with it is that it takes a while to know how to use it. So what ends up happening is that a lot of your apps notifications gets delayed or never show up or your apps are killed when your phone screen turns off or your VPN is killed when you clear it from the recent apps menu.
Solution:
Open the Mobile Manager app:
-Head to Memory Cleaner section
-Go to "Super Clean mode is turned on" Setup - click it
here you can turn off the option for all apps or deselect the apps you don't want to be killed when you clear the apps from the recent menu, once the app is deselected from the App list it will appear under the headline "Standard Clean the following apps".
-Next after deselecting the apps go back to the PowerMaster section in Mobile Manger/ then Auto-start manger /
Here make sure that All apps button is turned green then under the section "Allowed" make sure to select the apps you want to auto start so that you can receive their notifications. Deselect the apps you don't want to auto start.
-Finally go to the settings page /under Battery section / detect battery-draining apps:
unselect "Detect & stop" button.
-Go back to: Battery optimization section:
make all the social apps and apps you want to receive their notifications on time turned to : "Not optimized".
After this your apps shouldn't be killed even after you clear them from the recent menu, and you will receive your notifications on time.
Good Luck
Apparently it's not working for Spotify
Rashad83 said:
Hi guys,
One of the features i like about ASUS phones is the ability to control apps through the app Mobile manger but the problem with it is that it takes a while to know how to use it. So what ends up happening is that a lot of your apps notifications gets delayed or never show up or your apps are killed when your phone screen turns off or your VPN is killed when you clear it from the recent apps menu.
Solution:
Open the Mobile Manager app:
-Head to Memory Cleaner section
-Go to "Super Clean mode is turned on" Setup - click it
here you can turn off the option for all apps or deselect the apps you don't want to be killed when you clear the apps from the recent menu, once the app is deselected from the App list it will appear under the headline "Standard Clean the following apps".
-Next after deselecting the apps go back to the PowerMaster section in Mobile Manger/ then Auto-start manger /
Here make sure that All apps button is turned green then under the section "Allowed" make sure to select the apps you want to auto start so that you can receive their notifications. Deselect the apps you don't want to auto start.
-Finally go to the settings page /under Battery section / detect battery-draining apps:
unselect "Detect & stop" button.
-Go back to: Battery optimization section:
make all the social apps and apps you want to receive their notifications on time turned to : "Not optimized".
After this your apps shouldn't be killed even after you clear them from the recent menu, and you will receive your notifications on time.
Good Luck
Click to expand...
Click to collapse
Dentist.M.Evy said:
Apparently it's not working for Spotify
Click to expand...
Click to collapse
Are you sure you followed the steps stated. Personally i don't use Spotify so i am not sure if it works or not. So far I have no issues with apps I want to receive notifications from and ones I don't want to receive. If nothing works try to disable super clean mode and auto start apps and make sure battery optimization is not on for Spotify.
Really helpful post. I once tried to figure out the way to receive email notification and this just works. Thank you
thanks a lot buddy! i was having notification issues for some of the apps and its solved now! I had done most of the changes already but the Super clean mode was still on and causing issues. All good now.
I have tencent version converted on WW 1608 (fingerprint as well) and don't have that app in phone ???? You have CH rom folks?
CRYPTfromCATACOMBZ said:
I have tencent version converted on WW 1608 (fingerprint as well) and don't have that app in phone ???? You have CH rom folks?
Click to expand...
Click to collapse
Its not an app. Go to Settings > Advanced and you will see Mobile Manager as the first option under Assistive Tools.
On mobile manger cleanup where it says suggested optimization how do I uncheck uninstall rarely used apps I have so far tried resetting app preferences and also a factory reset and a hard factory reset
Vespirah said:
On mobile manger cleanup where it says suggested optimization how do I uncheck uninstall rarely used apps I have so far tried resetting app preferences and also a factory reset and a hard factory reset
Click to expand...
Click to collapse
Thanks Vespirah - did you ever get to un-check the feature (I didn't).

How to fix common Problems in Android 13 ROMs with the Huawei P20 lite

Hello everyone,
After some time messing around and daily with the Android 13 Rom 'LeaOS', I experienced some issues and wanted to share the solutions with you all to save you some time.
1. No sound thru the headphone jack
-It may work already but the headphone icon is not showing in the status bar. To fix this I recommend using "System UI tuner" to activate it.
-If it doesn't work at all, go to the PHH settings, if available:
Open Settings app -> Open PHH treble settings -> Misc settings -> check "use alternate way to detect headsets" and "disable audio effects". Done. This should fix the problem.
2. No Bluetooth audio
- First method is to go to PHH settings again:
Open Settings app -> Open PHH treble settings -> Misc settings -> Bluetooth workarounds: none, Compability max aspect ratio: default, Force-disable A2DP offload: off. Check if those settings are set the same and reboot the device.
-If this doesn't work, go to the Android developer settings and check if "Bluetooth-A2DP-hardware-offload deactivated" is activated. In my case, it's already activated and grayed out.
-If this also doesn't do anything, messing around with the 'Bluetooth AVRCP-Version" and "Bluetooth MAP-Version" helped me. I've set the AVRCP version to 1.3 and the MAP version to default.
Don't forget to reboot after every change to apply it.
3. No mobile data problem
-If you don't have mobile data (internet with your sim card (no wifi)), I have a simple and fast solution:
Open Settings app -> Open PHH treble settings -> IMS features -> Click "Create IMS APN" and check "request ims network" and reboot after that.
-If it didn't work, go to the IMS settings again and click "Install IMS APK for NOT SUPPORTED".
This should fix it after a reboot.
4. Low graphics
If your phone has low graphics in some apps (e.g. settings app, volume control,...)
-go to phh settings -> misc and select "force fps" and select you're screen fps and resolution and reboot.
-if it doesn't work, go to the developer settings and open "Graphics driver settings". Now select a random app and select "graphics driver for system". Now open the app and it should work. If not reboot or try another app.
I'm not sure why it's like that and only some apps do something, but I think this is a solution. In my case "Aliucord" (A discord app mod) makes my whole system upgrade the graphics.
5. Bad performance
This problem is easy to fix:
If your phone is rooted, install a kernel tweaks magisk Module (I use "Yet another Kernel tweaker") and install the app "Kernel toolkit". In the kernel Toolkit app, go to the CPU tab and select the CPU scaling to "performance". Then tick the highest minimum CPU core speed for both the big and small cores. Then go to the developer settings of Android and select animations to 0.5x. Enabling 4x MSAA forcing may improve the performance, but I haven't seen a difference. Just do NOT disable HW overlays. This will destroy the performance completely. Also I got more performance on video playback (it was laggy sometimes) by disabling "settings for media transcoding" completely in developer settings.
!This drains the battery slightly more on usage!
And for the ram usage, go to each apps info, and open battery usage... Then click restrict. Do this to all apps you don't need to run in background. In the developer settings also go to "apps in standby mode" and restrict apps you don't need to run in background. You can also go to "Background checks" in the developer settings to turn off some Services you don't need too.
!Restricting those services will force stop them; you won't get notifications!
This is my Instruction with solutions for my problems. This is just from my knowledge. The display resolution thing is weird and I'm not sure if this is the right solution, but it works for me.
I hope this helps somehow

Categories

Resources