Related
Okay, guys, here's the problem. I have been pulling my hair out for days over this. On any Lollipop ROM I install, no matter what combination of gapps and AOSP ROM I install on my OPO, after completely and totally formatting caches, system, data, and /data/media, the problem persists:
Always after logging into an account, but not always the same one, I start to get an error "android.process.acore has stopped." It happens every few seconds and renders the device unusable. I have tried every fix I could find online, including wiping contacts storage data, contacts data, etc. I have formatted my phone several times, and each time the problem comes back. It only stops when I disable Contacts Storage in settings, which then in turn disables all contacts functionality.
This is getting totally ridiculous, and the only thing I can think of is that the AOSP version of contactsprovider.apk is totally corrupt. Any ideas?
I have the same problem... Did you succeed in resolving it?
flolep said:
I have the same problem... Did you succeed in resolving it?
Click to expand...
Click to collapse
Somewhat. The issue manifests itself when Facebook is synced with your contacts, and you use Facebook OAuth to sign into another app. For whatever reason, this causes the contacts app to go nuts, and the only way to fix it once it happens is to get rid of the Facebook app. It's a bug that is quite beyond me to fix. There is a modded Facebook apk floating around somewhere, that has had permissions modded so it's not allowed to use your contacts or register as an account in your phone. That works. It also works if when you install a new ROM, you sign into any apps that use your Facebook login before you install the Facebook app, that way you log into them with the browser and they never talk to the contacts app. Once you have installed the Facebook app, DO NOT EVER click "Sign in with Facebook" in any app on your phone, or you're screwed again.
That's pretty much what I've come up with thus far. Hope that helps.
EDIT: Here's the link to the thread with the modded Facebook apk: http://forum.xda-developers.com/showthread.php?t=2333637
I have the same issue on all CM12 based roms. It seems to happen for users with many contacts (hundreds). Uninstalling facebook seems to fix the problem for me. I have no such problems on my Nexus 5 with the same setup and facebook installed, so I wonder if it's not something specific to the bacon CM12 code.
prometheus1010 said:
I have the same issue on all CM12 based roms. It seems to happen for users with many contacts (hundreds). Uninstalling facebook seems to fix the problem for me. I have no such problems on my Nexus 5 with the same setup and facebook installed, so I wonder if it's not something specific to the bacon CM12 code.
Click to expand...
Click to collapse
It happens for other phones users... See here : https://productforums.google.com/forum/m/#!msg/nexus/Ip-hdFEQccY/OSFCz4Qj59oJ
Thanks for your partial solution @jkotzker... For me it's a no go because I am a big facebook user and I can install app with Facebook account linked at anytime... It's really really annoying to not log with Facebook account if the Facebook app is installed I don't know what to do... I tried everything like you.
I've recently been getting the same issue but mine says "unfortunately the process com.android.phone has stopped" everything was fine had this phone for about a month was on a lollipop ROM and that just randomly popped up. At first I thought it was the ROM so I switch to another lollipop ROM and got the same issue. So I went back to the latest ota kk ROM and til now I'm still getting the pop up. What's going on here? Please help
marcviado said:
I've recently been getting the same issue but mine says "unfortunately the process com.android.phone has stopped" everything was fine had this phone for about a month was on a lollipop ROM and that just randomly popped up. At first I thought it was the ROM so I switch to another lollipop ROM and got the same issue. So I went back to the latest ota kk ROM and til now I'm still getting the pop up. What's going on here? Please help
Click to expand...
Click to collapse
Oh yeah I've been trying to figure this out since cm12 unofficially came out for the note 4. Like all of you said it's fine for a while or sometimes it's messed up right away. I've had it work for two or three days then out of nowhere just have the error pop-up and never go away. Disabling google contacts storage also got rid of the error for me but of course I can't have the phone without google contacts and sync. This last time it happened just by downloading and signing into Dropbox, which isn't related to Facebook at all. This is belong frustrating because nobody seems to have a fix and it's the only thing stopping me from using cm 12. Is there any Dev that can help or work on this with a logcat?
Sent from my SM-N910T using XDA Free mobile app
pablo1215 said:
Oh yeah I've been trying to figure this out since cm12 unofficially came out for the note 4. Like all of you said it's fine for a while or sometimes it's messed up right away. I've had it work for two or three days then out of nowhere just have the error pop-up and never go away. Disabling google contacts storage also got rid of the error for me but of course I can't have the phone without google contacts and sync. This last time it happened just by downloading and signing into Dropbox, which isn't related to Facebook at all. This is belong frustrating because nobody seems to have a fix and it's the only thing stopping me from using cm 12. Is there any Dev that can help or work on this with a logcat?
Sent from my SM-N910T using XDA Free mobile app
Click to expand...
Click to collapse
I didn't find one...
I talked about this problem in xda temasek rom thread and ak kernel thread without success. I even sent a message on official cyanogenmod website, with last crash and logcat attached. No success. The problem happened in 2012 too... And since then, Google didn't have a solution for it.
It seems that Google is finally aware about this problem and the correction could arrive in "a future version"... Well. I want it now... Indeed, there seems to be only to increase the buffer transaction between applications and contact storage from 1MB to 2MB for example, to have it corrected. But no dev wants to do it because the problem cannot be reproduced! And it's rare! But we have it! It's incredible to have it back after a full wipe... And happening randomly, just after a random sync between application and Android system...
Any more updates on this issue/ anything else we can do to get this resolved? Even my partial, temporary solutions have stopped working, and I am getting really frustrated.
Glad to see I'm not the only one here with this issue. Took different search terms to eventually land me here since this such an old and somewhat common issue. Nonetheless... Same problem. OnePlus One running Temasek CM12. Disabling contacts storage.... Blah blah blah. Its rather disappointing there's no actual solution instead of a workaround. But, I'm finally happy to know its Facebook. An app I rarely use but do need unfortunately.
Edit: wondering if anyone has had any luck fastboot flashing the factory image? I know it's a pain in the ass to have to back up all your files, etc off the device so I'd like to know if anyone has had success or even tried this. Cuz, I really won't feel satisfied until I've resorted to this last measure if there's the possibility of eradicating the problem.
t3chn0s1s said:
Glad to see I'm not the only one here with this issue. Took different search terms to eventually land me here since this such an old and somewhat common issue. Nonetheless... Same problem. OnePlus One running Temasek CM12. Disabling contacts storage.... Blah blah blah. Its rather disappointing there's no actual solution instead of a workaround. But, I'm finally happy to know its Facebook. An app I rarely use but do need unfortunately.
Edit: wondering if anyone has had any luck fastboot flashing the factory image? I know it's a pain in the ass to have to back up all your files, etc off the device so I'd like to know if anyone has had success or even tried this. Cuz, I really won't feel satisfied until I've resorted to this last measure if there's the possibility of eradicating the problem.
Click to expand...
Click to collapse
I initially had this problem when I switched to lollipop, not sure how it fixed itself but I'm guessing it's the contacts sync like you posted here; only the first time I accidentally synced Fb contacts, and due to the massive number of friends on it, it crashed. But you can disable any sort of sync services on Fb and continue using the app for everything else, I've had no issues since.
Do you mean luck with fixing this issue after flashing the factory image or only returning to stock? Because I've had no issues returning to stock from lollipop by flashing the factory images through fastboot.
Aditya Srinidhi said:
I initially had this problem when I switched to lollipop, not sure how it fixed itself but I'm guessing it's the contacts sync like you posted here; only the first time I accidentally synced Fb contacts, and due to the massive number of friends on it, it crashed. But you can disable any sort of sync services on Fb and continue using the app for everything else, I've had no issues since.
Do you mean luck with fixing this issue after flashing the factory image or only returning to stock? Because I've had no issues returning to stock from lollipop by flashing the factory images through fastboot.
Click to expand...
Click to collapse
I meant with flashing the factory image via fastboot to stop the frustratingly obnoxious pop ups of the process stopping (w/o uninstalling FB). You answered my question.
So, get this... Resolved the error by uninstalling Facebook. Today I picked up a Moto 360 and you HAVE to install Motorola Connect to really personalize the device... Once I allowed it to see my Google+ account info the android.process.acore started again. I'm SO annoyed. Gonna try a factory reset again and see if that helps. The only way to stop it is to uninstall Motorola Connect and that really sucks cuz I want to (of course) mess with my watch. I know nothing of Android Wear yet or how to root, etc the 360 so.... Here I go. Boldly. Lol
I'm just curious why I haven't seen more people having this issue. It's been plaguing me now for almost 2 weeks. I'm ready to throw my Bamboo OPO out the effing window. WTF.
t3chn0s1s said:
I meant with flashing the factory image via fastboot to stop the frustratingly obnoxious pop ups of the process stopping (w/o uninstalling FB). You answered my question.
So, get this... Resolved the error by uninstalling Facebook. Today I picked up a Moto 360 and you HAVE to install Motorola Connect to really personalize the device... Once I allowed it to see my Google+ account info the android.process.acore started again. I'm SO annoyed. Gonna try a factory reset again and see if that helps. The only way to stop it is to uninstall Motorola Connect and that really sucks cuz I want to (of course) mess with my watch. I know nothing of Android Wear yet or how to root, etc the 360 so.... Here I go. Boldly. Lol
I'm just curious why I haven't seen more people having this issue. It's been plaguing me now for almost 2 weeks. I'm ready to throw my Bamboo OPO out the effing window. WTF.
Click to expand...
Click to collapse
It's mostly not because of lollipop, but might be the app itself, I read a few others having this problem on other forums with HTC, the solution they found was to clear data on contacts storage. Give that a try and see if it works, if not I'd suggest going back to Stock or probably the new OxygenOS which is supposed to be out by now. Check out @timmaaa index thread in the general section, it has all the necessary stock images you need. Report back and let us know if it fixed the issue for you
Aditya Srinidhi said:
It's mostly not because of lollipop, but might be the app itself, I read a few others having this problem on other forums with HTC, the solution they found was to clear data on contacts storage. Give that a try and see if it works, if not I'd suggest going back to Stock or probably the new OxygenOS which is supposed to be out by now. Check out @timmaaa index thread in the general section, it has all the necessary stock images you need. Report back and let us know if it fixed the issue for you
Click to expand...
Click to collapse
Yea, I tried clearing contacts storage numerous times to no avail. I can live without the app... At first I thought it was a requirement to change watch faces... But, I do have a backup of stock, rooted but I can't go back to KK after being so used to LP. I'm def going to jump on Oxygen just to try it out but I'm guessing I'll end up running stock CM12s. I can't wait. I'd much rather have a stock (w/root of course) or mostly stock device that actually works completely.
t3chn0s1s said:
Yea, I tried clearing contacts storage numerous times to no avail. I can live without the app... At first I thought it was a requirement to change watch faces... But, I do have a backup of stock, rooted but I can't go back to KK after being so used to LP. I'm def going to jump on Oxygen just to try it out but I'm guessing I'll end up running stock CM12s. I can't wait. I'd much rather have a stock (w/root of course) or mostly stock device that actually works completely.
Click to expand...
Click to collapse
The bug has been corrected by Google themselves with Android 5.1. Finally!.. So, like me, just try omni 5.1 or last cm12.1 unofficial and the error has gone! So good to use my phone.... Hmmm... How to say... Normally... Lol.
flolep said:
The bug has been corrected by Google themselves with Android 5.1. Finally!.. So, like me, just try omni 5.1 or last cm12.1 unofficial and the error has gone! So good to use my phone.... Hmmm... How to say... Normally... Lol.
Click to expand...
Click to collapse
Very nice. Glad to hear this... Xposed isn't compatible with 5.1 yet, right?
Two things to try…
Go into settings/apps , press the menu button and select "reset app preferences". Reboot
You Can also try entering the following in your commands:
Su (enter)
Killall rild (enter)
reboot
Should have read the entire post, glad that has been fixed by google, I experienced the same thing and it's a huge pain in the butt.
t3chn0s1s said:
Very nice. Glad to hear this... Xposed isn't compatible with 5.1 yet, right?
Click to expand...
Click to collapse
No. Not yet. But. Well. CM12 is already good functionality wise. And with this bug disappeared it's really a happiness.
---------- Post added at 12:42 AM ---------- Previous post was at 12:39 AM ----------
tmjm28 said:
Two things to try…
Go into settings/apps , press the menu button and select "reset app preferences". Reboot
You Can also try entering the following in your commands:
Su (enter)
Killall rild (enter)
reboot
Should have read the entire post, glad that has been fixed by google, I experienced the same thing and it's a huge pain in the butt.
Click to expand...
Click to collapse
Yeah, yeah. Already tried... Lol. I think I tried every single advice given in all the Android forums of the world on this bug lol. Well. Google finally heard us. +++
tmjm28 said:
Two things to try…
Go into settings/apps , press the menu button and select "reset app preferences". Reboot
You Can also try entering the following in your commands:
Su (enter)
Killall rild (enter)
reboot
Should have read the entire post, glad that has been fixed by google, I experienced the same thing and it's a huge pain in the butt.
Click to expand...
Click to collapse
Neither worked but thanks for the suggestion. I did find a Facebook work around. Found the Lite Version via a Google search (since its technically not available in the US) , installed it and it works fine. No android.process.acore FC's or repeated pop ups.
Update: This problem reared its ugly head again on CM12 and I ended up having to uninstall Twitter this time. So, now I'm on CM12s and as soon as I logged into my other Google account user Boxers email app I got the android.process.acore crash again. Uninstalling that app immediately stopped it. God I can't wait for 12.1 for our OPOs. This problem is absolutely ridiculous. I can't take this anymore. I really can't use ANY social media apps unless its like Tinfoil for FB or Twitter. I don't have any connected accounts except Google & Cyanogen.. Which I truly can live without but... Just for the hell of it.... Knowing I have a backup and I'm about to clean flash the latest stock build I tried to add Waze and it caused the crash all over again. Uninstalling Waze didn't help. I shouldn't have to deal with this. Only way to stop it is to disable contacts storage. Once it begins it doesn't stop. Effing Google with their half baked crap.
[Android 5.1] Hangout constantly crashes on launch. + "Google Apps has stopped"
I upgraded to 5.1 on Monday by flashing the factory image. After the first boot and flashing root/recovery etc, I checked everything is running smooth and rebooted the device once more. Ever since then, Google Hangout crashes every time I try to open it; with this error -
Unfortunately, Hangouts has stopped.
Click to expand...
Click to collapse
I cleaned its cache, cleared data, uninstalled updates, updated from play store.
I cleaned all system cache from Settings > Device > Storage.
I cleaned Dalvik-cache and cache partition by going to recovry.
Nothing seems to fix it. It still crashes with the same error. From time to time, I'm also getting this error -
Unfortunately, Google Apps has stopped.
Click to expand...
Click to collapse
But all other Google apps are working fine. Anyone else having this issue?
Hangout - 3.0.87531466
Play Services - 7.0.93 (1778921-438)
===============================================
UPDATE -
POSSIBLE CAUSE AND SOLUTION
After spending 2 entire days on it and flashing the 5.1 factory images 3 times, I found out that it was being caused by LBE Security Master's Active Defense mode. This is like a live AppOps. It grants/denies permissions to apps at run time. Even though I had given full permission to Hangout, it was still crashing for unknown reasons. But after I disabled the active defense mode and rebooted the device, everything is running fine now.
So, if you are using any permission control app like LBE or AppOps, try disabling that and reboot your device. Yes, reboot is necessary. Just disabling doesn't fix it.
bagarwa said:
I upgraded to 5.1 on Monday by flashing the factory image. After the first boot and flashing root/recovery etc, I checked everything is running smooth and rebooted the device once more. Ever since then, Google Hangout crashes every time I try to open it; with this error -
I cleaned its cache, cleared data, uninstalled updates, updated from play store.
I cleaned all system cache from Settings > Device > Storage.
I cleaned Dalvik-cache and cache partition by going to recovry.
Nothing seems to fix it. It still crashes with the same error. From time to time, I'm also getting this error -
But all other Google apps are working fine. Anyone else having this issue?
Hangout - 3.0.87531466
Play Services - 7.0.93 (1778921-438)
Click to expand...
Click to collapse
What was your installation process for Play Services 7.0.93?
Aerowinder said:
What was your installation process for Play Services 7.0.93?
Click to expand...
Click to collapse
I had that version after flashing the 5.1 factory image. I guess Google pushed that to my device. It's not sideloaded.
bagarwa said:
I had that version after flashing the 5.1 factory image. I guess Google pushed that to my device. It's not sideloaded.
Click to expand...
Click to collapse
That is strange. I have the same version of Hangouts, but my updated version of Play Services is 6.7.76 (1745988-438).
bagarwa said:
I upgraded to 5.1 on Monday by flashing the factory image. After the first boot and flashing root/recovery etc, I checked everything is running smooth and rebooted the device once more. Ever since then, Google Hangout crashes every time I try to open it; with this error -
I cleaned its cache, cleared data, uninstalled updates, updated from play store.
I cleaned all system cache from Settings > Device > Storage.
I cleaned Dalvik-cache and cache partition by going to recovry.
Nothing seems to fix it. It still crashes with the same error. From time to time, I'm also getting this error -
But all other Google apps are working fine. Anyone else having this issue?
Hangout - 3.0.87531466
Play Services - 7.0.93 (1778921-438)
Click to expand...
Click to collapse
I am having the same issue with hangouts. I've taken the same steps to try to fix it.
As part of troubleshooting, I momentarily disabled hangoouts via app settings, then I started to see the "Google App" error. After re-enabling I didn't see this error anymore.
I have not tried removing hangouts completely, as it seems this would break other things.
Any possible solutions?
EDIT: The Google App error is actually persisting.
My issue is hangouts keeps getting killed by the Low memory killer even though I have 1gb free ram.
I did some monitoring, hangouts Noe has to run its own process that I've never seen before and after a minute it caches itself, and I guess the cache is dumped later since I haven't opened hangouts in 5 minutes, I have to restart the app every time I need to use it. I also don't receive any messages during that time because the app has been killed. Any ideas?
chabsie said:
I am having the same issue with hangouts. I've taken the same steps to try to fix it.
As part of troubleshooting, I momentarily disabled hangoouts via app settings, then I started to see the "Google App" error. After re-enabling I didn't see this error anymore.
I have not tried removing hangouts completely, as it seems this would break other things.
Any possible solutions?
EDIT: The Google App error is actually persisting.
Click to expand...
Click to collapse
POSSIBLE CAUSE AND SOLUTION
After spending 2 entire days on it and flashing the 5.1 factory images 3 times, I found out that it was being caused by LBE Security Master's Active Defense mode. This like a live AppOps. It grants/denies permissions to apps at run time. Even though I had given full permission to Hangout, it was still crashing for unknown reasons. But after I disabled the active defense mode and rebooted the device, everything is running fine now.
So, if you are using any permission control app like LBE or AppOps, try disabling that and reboot your device. Yes, reboot is necessary. Just disabling doesn't fix it.
bagarwa said:
POSSIBLE CAUSE AND SOLUTION
After spending 2 entire days on it and flashing the 5.1 factory images 3 times, I found out that it was being caused by LBE Security Master's Active Defense mode. This like a live AppOps. It grants/denies permissions to apps at run time. Even though I had given full permission to Hangout, it was still crashing for unknown reasons. But after I disabled the active defense mode and rebooted the device, everything is running fine now.
So, if you are using any permission control app like LBE or AppOps, try disabling that and reboot your device. Yes, reboot is necessary. Just disabling doesn't fix it.
Click to expand...
Click to collapse
Actually I'm using LBE as well and I suspected that it could have been the cause, and as you experienced, I removed all restrictions from the hangouts app and the problem still persisted.
My theory now is that a restriction that we've set on another app (or apps) is indirectly causing this issue with hangouts.
Does anyone know specifically which system apps could be connected to the functionality of Hangouts?
UPDATE: I've disabled restrictions on Youtube, Calendar, and Drive. This appears to have solved the problem.
Hangouts is working normally thus far and I haven't seen any error messages. Will update if things change.
I have a feeling that it's Drive.
What s
Is LBE? I'm stock phone sideloafed 5.1 and I have actually disabled hangout prior to upgrade now getting this error
Lee
Google play services "keep awake" disabled could cause it
I let all my apps keep awake in app ops and so on, but still have an issue with hangouts. It gets killed by system 5-10 minutes of not using it even if I leave it in background
2nd Update:
The problem is persisting again... my hypothesis has been disproved.
Any other suggestions or discoveries would be appreciated. I'm trying to find a way to fix Hangouts while keeping privacy settings in place as much as possible...
If XPrivacy was working for Android 5.0+ this issue would disappear.
I re enabled hangouts and updated it and not had the issue since
Play Service 7.0.96 from http://www.apkmirror.com/apk/google-inc/
Hangouts (+LBE) works fine by 5.1
Nexus 5 32GB, Android 5.01
Hangouts crashes occasionally for me also, and I don't have LBE or anything. I sideloaded 5.1 via nrt but my play services still says 6.7.76. Is that going to be a problem? Won't it just update itself eventually? Does the image not contain play services?
(I have the N6 but I thought the issue would still be relevant)
I had a similar issue, so I rolled back hangouts to 2.5x and it's working fine now, YMMV. of course this may not be a viable solution to you but a working older version is better than a non-usable latest version.
Cheers!
Well, the only thing I can think of, in my circumstances, is that I had hangouts disabled when I updated to 5.1 (I don't use it). So yesterday I enabled it, cleared data, and disabled it again, and so far no crash. Maybe something got changed in the update and it didn't like the fact hangouts was disabled. Again, your issue may vary.
spark001uk said:
Hangouts crashes occasionally for me also, and I don't have LBE or anything. I sideloaded 5.1 via nrt but my play services still says 6.7.76. Is that going to be a problem? Won't it just update itself eventually? Does the image not contain play services?
(I have the N6 but I thought the issue would still be relevant)
Click to expand...
Click to collapse
The new play services pretty much renders your phone useless due to nonstop update wake lock, (read more on the cataclysm ROM thread, like last 30 pages). The only way to fix the wake lock so far is to flash the cataclysm ROM patch (idk if it will work with stock ROM but it should) and it blocks the wake lock.
See attached picture below, that's how bad the new google play services is.
As for hangouts I got UKM and lowered the low memory killer to a minimum and disabled laptop mode (I'm using elementalX) and hangouts works just fine for me now.
russian392 said:
The new play services pretty much renders your phone useless due to nonstop update wake lock.
Click to expand...
Click to collapse
Sounds like I should stick with what I've got then! Though having said that I think gp will update automatically when it's released, being a core system component?
spark001uk said:
Sounds like I should stick with what I've got then! Though having said that I think gp will update automatically when it's released, being a core system component?
Click to expand...
Click to collapse
Yes, it would.
Firstly I want to apologize if there's a thread on this. I tried searching and didn't find anything. Google fails me as well.
For a few months now, Chrome has been driving me insane on my stock nordic Z3 (5.0.2 with the .690 firmware). I also have the most recent version of Chrome installed.
Every single time I open the app, it works for about 2 seconds, then completely freezes for around 15 seconds after which a message pops up stating "Chrome is not responding. Would you like to close it?" If I press "OK", it obviously closes the app and the problem appears again when I restart it. If I choose "wait", Chrome works just fine until the next time I open it. EDIT: The freezing problem started happening three times in a row a few days ago.
This happens every single time I open the app, whether launching it or opening it from the recent apps menu.
I'm pretty certain the problem has been around since the v39 build of Chrome, as 38 worked just fine. I have tried everything I can think of to fix it. Uninstalled updates and re-updated it, updating to lollipo didn't help, I also did a completely fresh install today (repairing via Sony Bridge for Mac) and it didn't help either. And apparently I can't go back to v38 anymore since lollipop doesn't seem to support it.
I would really want to use Chrome, as I've gotten used to it and enjoyed it quite a lot. I'd really appreciate the help.
Try clearing the data in settings - apps - chrome
gregbradley said:
Try clearing the data in settings - apps - chrome
Click to expand...
Click to collapse
I have done this too. Also, the problem persists even with completely fresh installs of Chrome.
Remove your google account, restart the phone and restore your google account
gregbradley said:
Remove your google account, restart the phone and restore your google account
Click to expand...
Click to collapse
Tried it, sad to say it didn't work either. Interestingly it now does the same 15 second freeze, but without the error message in the end. Curious indeed.
EDIT: Got the error message again.
Does this happen on Wifi or on data?
If on wifi is always the same router?
gregbradley said:
Does this happen on Wifi or on data?
If on wifi is always the same router?
Click to expand...
Click to collapse
I Use data 90% of the time, and various routers when on wifi. The problem occurs in all circumstances.
Are you rooted? Unlocked bootloader?
You say you are on the Nordic version of .690, is that the original region for the device you bought and the area you reside in?
Can you revert back to KK by flashing a FTF for your device and region and try V38 again to see if that works still.
gregbradley said:
Are you rooted? Unlocked bootloader?
You say you are on the Nordic version of .690, is that the original region for the device you bought and the area you reside in?
Can you revert back to KK by flashing a FTF for your device and region and try V38 again to see if that works still.
Click to expand...
Click to collapse
I have a completely untouched device. So no root, locked bootloader and it's always been that way. Thus Nordic is the original region of my device.
I'd rather not flash back to kitkat, but I can tell you that I tried reverting back to v38 before updating to lollipop and it worked normally without the freezing issue.
This is my version of chrome on Lollipop. Can you update to this? I am also not rooted so you should be able to update to this
gregbradley said:
This is my version of chrome on Lollipop. Can you update to this? I am also not rooted so you should be able to update to this
Click to expand...
Click to collapse
I have the same version of chrome as you. The problem has persisted during every single update after v38.
ok without logs I can go no further with this. Is there any chance you can pull some logs off your device?
gregbradley said:
ok without logs I can go no further with this. Is there any chance you can pull some logs off your device?
Click to expand...
Click to collapse
How do I do that?
install a logCat app from the playstore
gregbradley said:
install a logCat app from the playstore
Click to expand...
Click to collapse
Does this require root? One of the apps I tried is requiring it and the other one isn't doing much either. Should I be doing something to make it work?
isshoni said:
I would really want to use Chrome, as I've gotten used to it and enjoyed it quite a lot. I'd really appreciate the help.
Click to expand...
Click to collapse
Maybe try the beta version of chrome in case it's a bug which has been fixed but not yet rolled out to chrome. Perhaps try this first as it'll be quicker!
Perhaps it's some data associated with chrome that's getting pulled down after each restore. Perhaps you can try, on a desktop pc, backing up your bookmarks and then deleting them, and clearing chrome's data on your phone, then trying again? And if that doesn't work try getting rid of extensions (not that I think they should be pulling them down as chrome for android doesn't yet support them, although I'm sure I read years ago that one day they would). And anything else associated with your chrome account.
Another one, perhaps quicker (not sure) would be to see if you can associate your phone with a new google account with no previous chrome use and see if it goes wrong with that one. It would help to rule out account-related problems.
Another possibility is that it's not chrome causing the problem but something it relies on; google play services, for example. Perhaps clear data on any apps chrome could conceivably use.
I'm happy to report that my problem is now solved, though still a giant mystery.
My upper speaker broke and I had to get it replace under warranty. I got insanely lucky as they replaced both front and backside glass pieces, the frame, the screen module itself and of course the speakers. So I've now got a brand-new looking phone So happy.
Anyway, I complained about the software being a mess so they also did a complete reinstall and after that Chrome works absolutely perfectly. As magically does everything else too. Not yet a sign of lollipop's previous lagging and rebooting.
It still bugs me, however, that why would Chrome suddenly start having this unreasonable issue. I had tried everything suggested in this thread and nothing worked. My own clean install didn't work. I'm really quite bothered by this.
Hello all,
Having a problem with my unmodded XT926. Apps are crashing frequently during the day. Phone is usable but I get messages saying that Google Play has stopped working or Fleksy has stopped working. Keyboard app stops working multiple times a day. At first I was using the native keyboard app, but for the last three days I switched to Fleksy to see if that worked better but no dice. When the keyboard app crashes, I have to force reboot the phone. Do I need to reload firmware or something to get my phone stable again?
Phone has never been rooted (company phone). All I've ever done was disable some apps listed on the Xt926 Bloatware post on this forum and played around with Nova Launcher and Tasker.
XT926
KK4.4.2
182.46.15
kernel 3.4.42-gbd361ac
kernel date Jul 29, 2014
Any help/guidance is appreciated. Thanks in Advance
Boot into recovery and wipe cache. That has helped me in the past
Guapo613 said:
Boot into recovery and wipe cache. That has helped me in the past
Click to expand...
Click to collapse
Thanks for the suggestion. Unfortunately, it has not resolved my problem.
You can always try to enable certain things that you have previously disabled to see if that helps. I'm not sure what you have disabled but what works for some, may not work for you.
Since your rooted, you can also use Titanium Backup to freeze apps.
Are you familiar with RSD Lite?
Guapo613 said:
You can always try to enable certain things that you have previously disabled to see if that helps. I'm not sure what you have disabled but what works for some, may not work for you.
Since your rooted, you can also use Titanium Backup to freeze apps.
Are you familiar with RSD Lite?
Click to expand...
Click to collapse
The app crashes were happening prior to me disabling programs. I have tried enabling everything again and the results are the same. Most of what I disabled are the bloatware apps (Amazon, MC3, Real Racing, Spotify, etc.)
I am not rooted.
Have never used RSD Lite but will look into it.
You can try going into the "Apps" menu in settings and clearing the caches for individual apps. Some of them get quite large, and the cache only stores temporary data for reasons of convenience.
You can uninstall apps you don't really need (some of them run in the background and use up memory, look in "Running" apps in the system-apps listing).
Tasker is always running in the background; do you really need it?
You can try going into developer options (go into "About phone" in settings, then tap the build number many times) and reducing the background process limit.
If all else fails, you can do a factory data reset, or even more drastic, you can reflash the stock firmware.
Also bear in mind that this is an old device, and current apps expect devices with more memory and faster processors. Every time an app is updated with more features, it uses more memory on your phone and makes it run slower.
CryptZero said:
The app crashes were happening prior to me disabling programs. I have tried enabling everything again and the results are the same. Most of what I disabled are the bloatware apps (Amazon, MC3, Real Racing, Spotify, etc.)
I am not rooted.
Have never used RSD Lite but will look into it.
Click to expand...
Click to collapse
Backup important data (pics, music etc.) and try a factory reset. This should cure all you problems.
If this process cures your phones problems, you can root your phone if you like. Look at this thread: http://forum.xda-developers.com/droid-razr-hd/general/index-motorola-droid-razr-hd-2015-t3167557
Factory reset was done prior to my post on this board.
Don't think tasker is the problem. After the reset, I manually added apps one or two at a time... Tasker was the last one added, but crashes were happening before that.
Previously, I had been using tasker for about 6 months with no crashes at all.
Right now, I'm leaning toward flashing the firmware. My company has put a temporary ban on issuing droid phones due to that big exploit that was discovered a few weeks ago. I hate iPhones and am trying to keep this one running until they lift the ban.
Thanks for all the help so far. I'm open to trying anything to just get this phone back to a stable condition.
Sent from my DROID RAZR HD using Tapatalk
so here is the latest.
Phone rebooted itself, after an app crash and is now stuck on the Droid Eye bootup screen thingy...
Force reboot doesn't fix it. Took it to Verizon store downstairs for sh*ts and giggles and they were no help. No surprise there!
Does this sound like a hardware issues to you guys?
Guess I'm going to have to bite the bullet and get an iPhone from my company as a replacement.. unless someone on here has some miracle suggestion.
It sounds more like a software issue to me.
I would see if you can get into fastboot or ADB and flash a fresh copy of the firmware before giving up entirely.
A full flashing of the firmware via RSD Lite will probably fix your issues
So I was able to Flash firmware to 183.46.15 and I also rooted the phone using sd_shadow instructions. Took me quite a while to actually download a working firmware file. The only working link I found was here: http://download1520.mediafire.com/rnbmstjwc1wg/du1p88ti1esd5fk/VZW_XT926_4.4.2-KDA20.62-15.1_1FF.xml.zip
I guess I'll see if the phone is any more stable over the next few days.
Thank you all for the suggestions. Much appreciated!
Was this ever resolved?
By months my 3a won't automatically update itself even with update/download "over any network", I have already tried to restore and wipe from recovery but still unresolved.
Does anyone noticed this issue?
I tried waiting almost one month without system (monthly patch) and apps (all pending) updates popup.
Google support after few attempts, just proposed me a warranty replacement but the phone otherwise is perfect.
Manual updates works.
Any tips?
TY
I had the same issue back in January and didn't get a system update well into April. So I had to manually update. Still haven't gotten the May update yet, but we'll see.
Also with the apps?
If you have an unlocked bootloader, I would not count on automatic monthly updates. They work sometimes, but not most of the time. My personal experience is that I have to sideload the monthly updates about 90% of the time.
As far as app updates, I generally manually check it every couple of days and find that there are pending updates. I will hit the "update" button and manually update them if I see pending updates. That being said, if I don't check it for a while (maybe a week), the phone will eventually update the apps, but it certainly doesn't happen on a daily basis, at least not in my experience. I just wanted to add my experiences as they seem to be very similar to yours.
sic0048 said:
If you have an unlocked bootloader, I would not count on automatic monthly updates. They work sometimes, but not most of the time. My personal experience is that I have to sideload the monthly updates about 90% of the time.
Click to expand...
Click to collapse
Having an unlocked bootloader, too, but I never had issues with updates until now, they are coming directly at the first day Google is sending out the OTA.
I wonder if our phone service provider is also a factor? I have not been seeing the updates available within a day or two of when they are posted on the first Monday of the month. I get my phone service through a T-mobile MVNO. Maybe people on Google Fi are more likely to get it OTA quickly?
My phone is rooted with Magisk.
But I'm impatient so I have always just applied the update manually. It's a bit more of a pain because it means that I have to download not only the update but also the factory image to extract the boot image file and patch it with Magisk.
I have not had a problem installing updates for apps through play. I just have to remember to NOT update youtube so that I don't lose youtube vanced!
Hi all and thanks for your time!
I have a good news.
After avoid to do any manual update, right now I see that few apps have been updated themself from 11 hr and 2 days ago, but other 22 apps are still pending (when I wrote here the 6th May they were 40).
Around the 23th of Feb I had to do manual update search because it still was with Jan patch, even in March and April I did the manual search the week after the day 5th.
My phone is not rooted and during the day it uses both cellular and WiFi networks, mostly of the nights I put it in airplane mode and battery save (so it lasts easily for 2 days).
The cause was because I put all the nights the phone in airplane mode with battery saver, last night I leave it connected to WiFi and under charge, this morning I found the advice to reboot for install the system patch and after boot also the apps were updated.
The system patch has been found around 4 am.
I'm having a similar issue with my rooted 3a. I have stock rom, elemental kernel, and magisk. But apps that came installed as part of the ohone won't update in Google play. Stuff like phone, contacts, sim carrier, Gmail, camera, etc
There's literally about 20 updates right now that won't install. They download, and say installing, then they just skip to the next and still say there's an available update. After the final one is tried, I get a message saying that it was unable to update those apps.
Any app that I downloaded from play or as an apk, allows me to update without any issue at all.
I have googled it and followed the recommendations, but so far, nothing has helped. I cleaned the cache, hard reboots, switch update settings, turned off play protect, deleted cache and data of play store and play services. Removed my account and added it bad. And have some a few more things that I read about -- but yet nothing fixes it.
If I should start a new thread, that's no problem. I don't want to hijack this one. But saw that it dealt with update issues and thought maybe I would see if I could find help.