"Phone" app crashing - ASUS ZenFone 7 / 7 Pro Questions & Answers

Hi all.
I've updated to the latest Android 11 release and am having a few problems with it. The built-in phone app (Link) crashes immediately on execution. I've been able to workaround by installing the Google phone app, but even this crashes sometimes too.
Another thing that's weird is the "System" menu in settings. I've attached a screenshot of how it looks.
I've tried reflashing the zip to no avail. I'm wondering if the problem is that I originally went from Android 10 to the WW-30.40.30.96 version, and then from this version to the latest WW-30.41.69.51 version. Any thoughts?

Related

[Q] ZuluGen 1.0.3 Issue

Constantly crashing with both update from older version and fresh install. Fresh install crashes even with no other apps installed. Anyone know what might be causing this?
Edit: seems to happen whenever I open the gallery.

[Q] [SOLVED] com.google.process.gapps stopped working

System Specs:
TF101
Android Version: 4.1.1 (now 4.1.2)
Kernel Version: 2.6.39.4 CyanogenMod RaymanFX DHD (now 2.6.39.4ASUS [email protected] #1 Sat Oct 13 19:34:10 CEST 2012)
CyanogenMod Version 10-20120916-UNOFFICIAL-tf101 (now 10-20121013-UNOFFICIAL-tf101)
Problem
com.google.process.gapps stops working
What I have done so far:
Cleared cache
Cleared davlik cache
Removed Gmail account and re-added
Disabled ALL sync options
What I did to get here:
Installed TWRP (replaced Clockwork Recovery)
Installed CM10
Installed GooManager (for gapps)
Restored ALL apps I had/wanted back from the Play store
This problem occured immediately after I finished installing all apps. I dont know what one app might have caused this. I am trying to avoid a factory reset, but it seems this may not be avoidable at this current step. My question is, what else is there I can do short of a factory reset?
EDIT 1: just found out the GAPPS i am using is for 4.1.2. Would this cause the issue since i am on Android 4.1.1?
EDIT 2: Re-flashed the GAPPS from GooManager and it seems to be working better. I will update after testing it throughout my 24 hour duty.
EDIT 3: I let it go to "sleep" and when i woke it up, the process failed again.
EDIT 4: Used another version of GAPPS for Tegra. Now trebuchet crashes after going to sleep. Seems the GAPPS is the cause of the problem. Is there a stable version for my device and CM10? The latest crashes the com.process.google.gapps and the later crashes trebuchet
.
EDIT 5: After a night of troubleshooting, I found out i was using version B3 instead of V6 of CM10. Thus the Android version of 4.1.1 instead of 4.1.2. I just flashed V6 to my tablet and now I am testing the device for compatibility with the first version of GAPPS that i had installed earlier. I will post results after my tests.
EDIT 6: So far so good, everything seems to be running normally. I have not had any problems for the last five hours. I hope this fixed my problem
EDIT 7: So after waking up to my tablet sleeping, i woke it and the process failed again. Is there a compadible GAPPS zip out there somewhere?
EDIT 8: Ok, so I decided to do a factory wipe, install CM10 V6 fresh. Then install google apps filename "gapps-jb-20121011-signed.zip" Seems that the google apps keeps failing. I even unchecked all the sync options and didn't put my account in until after i installed the google apps. At this time there are NO apps installed other than the default CM and GAPPS. I am officially stumped. HELP PLEASE!
EDIT 9: I did a factory wipe, no re-install of CM10 or GAPPS, just a standard wipe followed by clearing both caches. Upon reboot it wanted my credentials for google. Seems to be working ok, meaning it GAPPS is not crashing at this current moment. However, it has dropped WiFi on me while it went to sleep and came back. I told it to not turn WiFi off when it sleeps, but alas, it seems to be broken. Also, it lockes up randomly, and the only way to recover is to hold the power button to turn it off and then reboot. Thoughts?
EDIT 10: Changed to the nightlys from CM and updated to the most recent GAPPS. Everything is working great. Minus some of the things that have already been mentioned. My lock screen disappears ever so often. Also, I have noticed that when not charging, the tablet will shut down at 49% when sleeping. I don't know if that is a feature of the CM10, but it is annoying. I have yet to have any random lock ups, but some of my apps won't work anymore. I have noticed that some apps will work one moment, the next it will have a video failure, but the sound will continue and the process will continue. Just the video display will be stuck on one image. For example, Jetpack Joyride does this. Also, Song Pop Free will not work, among some other apps. So, I guess I have to wait for a Jelly Bean update for some of these apps.
I've had a similar issue with gapps, usual provoked by accessing gmail or maps however I did have the same issue with the stock rom.
Sent from my Transformer using Tapatalk HD
I appreciate the info, was this with ICS or Jelly Bean? I am assuming with your stock you mean ICS. Am I missing something about GAPPS? Is there a better compatible build for this?
.. just go to the settings and then click on the application manager and then click on all and then scroll to download manager and enable it if it is disabled. .......Thanks. ....
video
haythams said:
.. just go to the settings and then click on the application manager and then click on all and then scroll to download manager and enable it if it is disabled. .......Thanks. ....
Click to expand...
Click to collapse
just like this video
go to youtube and type com.google.procces.gapps and click the video that says solution for the problem.
humnn. did you got that idea from this.
haythams said:
.. just go to the settings and then click on the application manager and then click on all and then scroll to download manager and enable it if it is disabled. .......Thanks. ....
Click to expand...
Click to collapse
thanks bro it worked. thanks for the info.
I had a slightly different solution
wipe the google play services data complete it will then need to be updated

Many apps have stopped after Android 6.0 update - any global way to fix?

Hi all,
A few months ago I've installed a Developer Preview of Android 6.0 on my Nexus 5. It has worked surprisingly well and today I've updated manually to the latest build (MRA58N). So no root, official recovery...
Android itself works well, but many apps from the Play Store stop with the famous "Unfortunately [App name] has stopped" message. Virtually half of them.
I've tried the usual ways to fix the problem like the cache cleaning and so on, but nothing works. The only way is to uninstall the app and to install it again. Of course, every one needs to be configured next.
What can I do? Of course, I can reinstall and reconfigure every single app, but maybe there is a global fix already available?
[Update]: I continue to investigate the issue because my other Nexus 5 has been updated perfectly. It seems the problem is related to the app permissions as some of them can't access the files, other launch, but can't open any file. Any way to repair the permissions?
Thanks in advance.

Bootloop after updating apps like Telegram?

Maybe this is a very stupid question but I really have no idea why this problem occurs
My phone (HTC One S Ville mit Resurrection Remix (Android 5.1)) worked perfectly fine until last Friday.
At this date a new update of Telegram Messenger was released. I installed it and while installation of this app my phone did a restart and got stuck in a bootloop.
I restored using TWRP and retried - same problem. I also deleted the app and its data to do a fresh install - bootloop after installation.
Furthermore I noticed the exactly same behavior for the last update of WiGLE. All other apps could be updated to their latest versions without problems.
I used Google Play to update these apps.
What could be a problem for that? Is android just too old to these apps or could there be a collision with something installed on my phone/the ROM? How can I debug this?
I am not an android expert and I am very thankful for any kind of help :')
Thank you! =)
Same Problem with LG G2 mini / Android 6
Hello,
I'm facing the similar problems since a few days. Running Resurrection 6.0.1 on LG G2 Mini.
It started with installing maxdome-app at thursday, last week. Phone went into bootloop.
Wiping and or deinstalling the app in safe-mode did not work. So I restored to an older backup. This worked some time but ran into bootloop after a while ( I do not know what I've done exactly to get into this, this time).
I tried around a little. One part was a fresh install of cyanogenmod 13. This worked some time and I could find out that installing telegramm messenger had the bootloop-effect repeatable.
Sorry for not giving any help to the thread-creator but I hope we can give any more information to each other or anyone else can help?
Right now I am installing apps and backing up all the time to get some half-working system, but better ideas would be appreciated
Good to know that I am not alone
I figured out that there are a few more apps causing the bootloop. Here is a list:
WiGLE Wardriving
Telegram Messenger
pr0gramm.com app
Playstore Changelog (XPosed Module)
Statusbar Download Progress (XPosed Module)
Maxdome
I already updated Xposed Framework, Google Play Services and Google WebView to prevent incompatibilities. Problem still exists.
I updated everything as far as possible and made a backup using TWRP so I can restore my OS at any point. Further you could backup your apps using Titanium Backup. I it worth its price!
I started facing a similar problem of app updates causing bootloops on my device which was running CandySix ROM / 6.0.1. Apps causing bootlooping included Greenify and Nova Launcher. I had another device which has a factory 6.0.1 ROM rooted with Xposed and that device didn't have bootloop issues with these same versions of apps. Fortunately I was able to update the first device to a LineageOS 14.1 7.1.2 ROM and once again continue using the latest version of apps without bootlooping issues - but I never did understand exactly what was causing the bootlooping problem. That was a rather frustrating experience.
When the first bootloop happened, I was updating one single app, so I knew it was probably the one I should roll back to the previous version to fix the problem - so I didn't have to resort to a full TWRP restore.
How did you do a rollback of an app while you are in a bootloop? I would be glad to know that
Unfortunately my Device One S Ville does not get any updates anymore
In my case I can boot to custom recovery/TWRP to delete the app apk from the its /data/app folder - which basically prevents it from running when I reboot the phone. I also use an apk extractor app to save the apk of all apps I install and I also use Titanium Backup - so between those two I have copies of the older apk versions to install. You can also find older apk versions on apkmirror.com.
Depending on the severity of the bootloop, you can also connect your phone to a PC and use adb to disable/uninstall the app causing the problem if you know which one it is.
-kw said:
How did you do a rollback of an app while you are in a bootloop? I would be glad to know that
Unfortunately my Device One S Ville does not get any updates anymore
Click to expand...
Click to collapse
Thank you for your explanation! This sounds a bit more stressful to me than rather restore via TWRP but could me more time efficient for larger ROMs. I will keep this in mind
Thanks and can confirm that deleting the app folder/apk via twrp can help. I got back into my android 6 again. For me seems more that DavDroid caused it (but Telegram was suspicious, too).
DavDroid mentioned in the last update on 4th November, that they released a workaround against crash and bootloops on some custom roms
Depending on how old your TWRP backup is, restoring from TWRP is an option. But often I have not made a backup in a while or made many recent changes that I didn't want to lose, so the other ways I suggested are more time efficient in some cases.
-kw said:
Thank you for your explanation! This sounds a bit more stressful to me than rather restore via TWRP but could me more time efficient for larger ROMs. I will keep this in mind
Click to expand...
Click to collapse
Upgrade to Android 7
I can add EDS app to the non-working programs.
As far as I could install Telegram (same Version) by downloading .apk I suspect the problem is something depending with playstore. This would explain the many affected apps. But of course I don't know it for sure.
Inspired from divineBliss I upgraded to Android 7 (LineageOS 14.1) and could install everything as I wanted without problems so far. Thanks for that. Looks good, but I will wait some days after I'm convinced.
@-kw: did you try the following link for upgrading to higher android-version?
https://forum.xda-developers.com/htc-one-s/development/7-1-lineage14-1-htc-one-s-ville-t3540981
Glad you were able to update ROMs and escape the bootlooping problem
I have been running LineageOS 14.1 for about a month now without any bootlooping issues due to app updates - so I expect you won't have any issues. I did cause some dread time consuming to resolve bootlooping due to some bad substratum themes, but that's a different issue altogether .
michibr said:
I can add EDS app to the non-working programs.
As far as I could install Telegram (same Version) by downloading .apk I suspect the problem is something depending with playstore. This would explain the many affected apps. But of course I don't know it for sure.
Inspired from divineBliss I upgraded to Android 7 (LineageOS 14.1) and could install everything as I wanted without problems so far. Thanks for that. Looks good, but I will wait some days after I'm convinced.
@-kw: did you try the following link for upgrading to higher android-version?
https://forum.xda-developers.com/htc-one-s/development/7-1-lineage14-1-htc-one-s-ville-t3540981
Click to expand...
Click to collapse
@michibr:
I am very pleased with my Resurrection ROM; but this is stuck on Android 5.1. I will give a new ROM a try when I have the time for that
At this time it seems like this is the only solution of escaping the bootloop-problem
FYI
I updated to Android 7.1 RR and now I can update all my Apps without problems
I am sorry that this is the only solution I can provide, but still better than nothing
Hi all,
I'm having exactly the same problem, it all started with FB, then some other apps.
I had to reboot into Safe Mode to uninstall those apps.
I'm running on cm12.1 and I have my own reason not to upgrade to higher Android.
Am hoping someone can come out with a solution.
For now, here's my list of apps:
- Facebook (Facebook Lite is fine)
- Telegram
- Bluemail
- Local telco app
I am sorry to inform you that I did a lot of research and was not able to find any other solution than upgrading to a higher android.
The problem is with appt2 someone reported it in google's issue tracker and someone from goole descriped it in detail here's it :-
CyanogenMod has this function getPkgName (https://github.com/CyanogenMod/android_frameworks_base/blob/cm-13.0/libs/androidfw/AssetManager.cpp). It creates a ResXMLTree on the stack and points it at a buffer from an asset without making a copy. Then it closes the asset before the ResXMLTree is destroyed.
For apps built by aapt, this is benign. However, aapt2 produces UTF-8 string pools, which cause the ResXMLTree's ResStringPool(mStrings)'s mCache to become non-null in ResStringPool::stringAt (https://github.com/CyanogenMod/android_frameworks_base/blob/cm-13.0/libs/androidfw/ResourceTypes.cpp). Then ResStringPool::uninit dereferences mHeader (which is now dangling), and a crash ensues.
This crash shows up in different ways. On one Cyanogen OS device, the launcher crashes when an app built with aapt2 has been installed, but only if the manifest is large (probably due to how deallocation happens for small vs large blobs). On another device, system_server crashes at boot if an aapt2-built app is installed.
We're attempting to work around this with a custom build of aapt2 that always produces a UTF-16 string pool for the manifest. Results so far are promising.
Can this be patched somehow at the OS via xposed for all of the roms that won't get updated?
The fix for this issue is available here (CM13):
https://forum.xda-developers.com/showpost.php?p=74636021&postcount=216
CM12.1:
The fix for this issue is available here (12.1):
https://forum.xda-developers.com/showpost.php?p=74842530&postcount=464
Is this .zip patch for any device with any Lollipop 5.1.1 ROM?
Because I just installed it and my HTC one X with Resurrection Remix ROM (Lollipop 5.1.1) goes black after the HTC logo.
lescht said:
The fix for this issue is available here (CM13):
https://forum.xda-developers.com/showpost.php?p=74636021&postcount=216
CM12.1:
The fix for this issue is available here (12.1):
https://forum.xda-developers.com/showpost.php?p=74842530&postcount=464
Click to expand...
Click to collapse
Hello what is about cm11 kitkat 4.4.4 sameissue but no fix-
could anyone make a fix? Please help.

"Files has stopped" Issue

Hi there. I've just upgraded my phone to Oreo and I have this issue with the 'Files' app (not the My Files app). Whenever the Files app is launched to pick a file (e.g. attach a file in Gmail or select a photo in Snapseed) the Files app will immediately crash with a 'Files has stopped' error.
I have tried booting the phone into safe mode and tried attaching a file in Gmail, which worked perfectly. So my guess is that a third-party app is causing the persistent crash. However, my phone has several apps and trying to identify the culprit app(s) will be too much of a hassle.
Does anyone else have the same issue after upgrading to Oreo and have a solution to it (other than factory resetting)?
Any help will be greatly appreciated. Thanks in advance.
Probably there's a bug somewhere. So you could do any of the following:
1. Wait for an update
2. Do a factory reset
Apart from these two, I don't see other options.
RossTeagan said:
Probably there's a bug somewhere. So you could do any of the following:
1. Wait for an update
2. Do a factory reset
Apart from these two, I don't see other options.
Click to expand...
Click to collapse
Hmmm well alright, thanks for your help
I have the same problem with my NOTE8, after the March Update, this problem started to appear.
Got in touch with the guys from MyFiles and after few e-mails, they say:
''I checked your log files and found out some error.
But these are regardless of MyFiles so cannot handle it anymore by our side.
com.android.documentsui has problem and it seems to be below apk''
Went here: android.stackexchange.com/questions/187501/what-is-com-android-documentsui
And I believe its a major software glitch that has to be corrected by google/android/samsung...
As others have suggested this may be due to the app nit working with Oreo.
I use FX explorer app from play store, it works with every version of android I have ever used including S8× exynos Oreo
As well as being a great file explorer / management app it can be used to navigate to a specific file to attach etc.
https://play.google.com/store/apps/details?id=nextapp.fx
Hi, sorry I forgot to update. I don't know what happened, but I think after a minor software update, the issue resolved on its own.
Nevertheless, thanks for all your insights and advice on this matter
My files stopped on my android galaxy phone
Hello dear,
Hope you are fine.
Dear, I have a problem with my samsung phone which is : "My Files Stopped Working..". Could you help me resolving this problem please??
Also, I have another question, if I want to do system update or software update for my phone, does it affect my files, folders, pictures, videos, etc... Or it just update the phone system??
If you know about these problems, please help me.. And thanks alot.

Categories

Resources