Related
I'd been running rooted (Revolutionary) with the Verizon/HTC stock ROM (605.9) for awhile and fairly happy. Then I received the OTA push attempt about 2 weeks ago for 605.19... so I opted to defer the push for 2 weeks (June 1) so I could do some research and decide what best to do.
That's when the following problems began... I noticed right after the OTA request... that anytime I restart or reboot the Tbolt many of my core app defaults now go away:
GO Launcher... requires to re selected
Power widget... will not reload (but GO Calender widget is fine?)
Facebook... contacts sync have to be reset (but Google syncs are fine?)
Swype keyboard... must be re selected
Even though I could/can manually fix these disconnects, I decided to take the opportunity to try some other ROMS to see if that would correct the problem. Long story short... I have basically tried 4 different ROMS including 2 different stock ROM (650.19) variants. I am now currently running iKReaM.605.19.NOSeNSe.ROM.v1.0.RLS-R3Ds
which is a nice running ROM.
BBUTTT... with every clean and wipe and reflash, the above "default" disconnects occur? I have tried to search several sites for anyone experiencing similar problems with no success... I know this can't be a ROM issue because it occurs no matter what ROM I use.
Misc info: Several ($paid$) rooted apps that I use are... TiBackup, ADfree, Root Explorer, Superuser (DDChain), No Frills CPU, ROM Mgr... all of which seem to be working together just fine.
Thanks for reading and any thoughts would be appreciated.
I'm beginning to narrow this down to self-affliction... perhaps via something I've done in ROM manager and I keep restoring the problem (???). I deleted all backup data and have reflashed iKReam. One by one I'm adding apps back and have had no app "default" disconnects as of yet. Also I'm not going to reload GO launcher... since the default iKReam launcher (LauncherPro +) is working/reloading just fine and I don't want to chance it.
App Defaults
Sometimes weird things happen like this for the oddest of reasons.
Try running fix permissions in ROM manager.
If it doesn't work...
Did you also clear the dalvik cache when you flashed over to your new ROM?
Did you restore data only from your pervious ROM onto your new one?
Always make a backup before doing anything different, just in case.
If none of this works, I really don't know what to tell you man.
Hopefully this will bump your thread and someone will be able to help you out a little bit more.
I have searched everywhere for someone having a similar problem and a fix, but for the first time on xda, I haven't been able to find one.
I have a Galaxy SIII on Verizon currently running Hyperdrive RLS13.
When I open the Application Manager, click on an app (any app, it doesn't matter whether I installed it from the Play Store or from an apk) and then click "Uninstall", it does nothing but goes back to the application list. It doesn't install, I get no error message, Settings doesn't crash...it just does nothing. It's the same as using the back button.
I CAN uninstall apps within the Play Store. Occasionally the uninstall button in the Settings will actually give me the confirmation pop-up to continue with the uninstall or to cancel it. But 90% of the time it doesn't and I have to use the Play Store.
I have done a clean flash once already and the issue still persists. My fiance who has the same exact phone as me (but in white) is also running Hyperdrive RLS13 and his phone is fine. In fact, I flashed Hyperdrive onto both our phones with the same exact SD card, using the same zip file.
I've been using custom ROMs for several years so yes, I've done all the obvious things, but I've reached the extent of my knowledge on what could be causing this. Can anyone tell me if they have heard of this issue before or a possible fix? I've never had this issue outside of Hyperdrive (I would post in the Hyperdrive thread but I don't have enough posts to reply in Development).
Have you tried flashing rls14. I would do your wipes and then flash the newest release.
Sent from my GT-P5113 using xda premium
I just downloaded it yesterday but I haven't flashed it yet - it's moving to my SD card right now. The only reason I posted for a fix though is because reflashing 13 didn't help... the issue just randomly started occuring about 3 weeks after I originally installed Hyperdrive. It makes me wonder what caused it.
I will be flashing 14 shortly and will report back.
Following a clean RLS14 flash, I still cannot uninstall within the Application Manager.
My fiance's phone (which I also updated to 14 as well this afternoon) can do so like usual.
So...any ideas?
workaround
assuming you nandroided coming from 13 to 14, just dont select those apps you want uninstalled to backup.
flash 14, restore apps, and only the ones you want will appear.
another workaround to try is install nova, long click the icon on a homescreen, select uninstall. not sure if this is a prime faeture though.
Well, sure - the even easier workaround is to just uninstall them with the Play Store, but I'd rather find out why this is happening.
So I've searched the web and the Hyperdrive thread and can't seem to find anything ANYWHERE. Any insight would be helpful. It seems to make sense that it could be a permissions issue maybe, but I don't know enough about building ROMs to know how to go about testing that.
The notification badge on my stock Messaging app icon is incorrectly showing 1 unread message.
I have a totally stock Droid RAZR MAXX HD running 4.4.2. My stock messaging app is version 4.4.2-10. SMS is set to "Messaging" (not "Hangouts"). All settings are default. Verizon Wireless is my service provider.
From my own troubleshooting, I have concluded that the problem is probably KitKat-related since stopping, disabling, and clearing (data, cache, and defaults) the stock messaging app has no effect. Also, this problem started after my OTA upgrade to KitKat (never had it before). Further, after completely disabling the stock messaging app, I alternatively installed GO SMS Pro, chomp SMS, and Verizon Messages and experienced the exact same problem with each.
Any ideas about how to fix this problem, without FDR'ing or rooting the phone, would be greatly appreciated.
clear dalvik?
you try clearing dalvik cache?
Great suggestion, but how do I perform it? Can you direct me to instructions on how to clear the Dalvik cache on a stock RAZR MAXX HD running KitKat? I can't find any that don't require a rooted phone. Thx much.
PW_Irvine said:
Great suggestion, but how do I perform it? Can you direct me to instructions on how to clear the Dalvik cache on a stock RAZR MAXX HD running KitKat? I can't find any that don't require a rooted phone. Thx much.
Click to expand...
Click to collapse
i never have stock recovery on, so i could be wrong, but i dont think you can do that in stock recovery.
which means you would have to put on a custom one and root, which i think you said you didnt want to do.
it is somewhat common to have random issues like this on a major software upgrade, especially one that jumped so many other builds.
i know you really dont want to do it, but clearing the corrupted data is really the best course of action, and it may be the only one honestly.
and if you are going to go that far, it is really best to just re-flash the phone encase something in the system is corrupt. just no point in going 1/2 way just to find out you still have the issue later.
sorry thats not the answer you were looking for, but sometimes it is not avoidable.
bweN diorD said:
i never have stock recovery on, so i could be wrong, but i dont think you can do that in stock recovery.
which means you would have to put on a custom one and root, which i think you said you didnt want to do.
it is somewhat common to have random issues like this on a major software upgrade, especially one that jumped so many other builds.
i know you really dont want to do it, but clearing the corrupted data is really the best course of action, and it may be the only one honestly.
and if you are going to go that far, it is really best to just re-flash the phone encase something in the system is corrupt. just no point in going 1/2 way just to find out you still have the issue later.
sorry thats not the answer you were looking for, but sometimes it is not avoidable.
Click to expand...
Click to collapse
Have the same problem - I find that if I delete a recent MMS message sent from me, then it goes back to normal.
PW_Irvine said:
Great suggestion, but how do I perform it? Can you direct me to instructions on how to clear the Dalvik cache on a stock RAZR MAXX HD running KitKat? I can't find any that don't require a rooted phone. Thx much.
Click to expand...
Click to collapse
baldbob said:
Have the same problem - I find that if I delete a recent MMS message sent from me, then it goes back to normal.
Click to expand...
Click to collapse
nice suggestion :good: i have never heard of that.
thanks
yeah dont think its possible on a phone that isnt rooted or has a custom recovery, whats the reason you dont want to to root?
Unfortunately, deleting all SMS and MMS messages did not solve the problem either, so I just FDR'ed the phone. Problem is gone on reboot of course, but so is 13 months worth of app configuration. I would root the phone this time except that the screen is also acting up on me and the phone still has 4 months left on the Costco warranty that I got (for free) with the phone. Wouldn't it be great if Android "L" allowed you to back up app settings along with apps without the need to root the phone first! Thx to all.
PW_Irvine said:
Unfortunately, deleting all SMS and MMS messages did not solve the problem either, so I just FDR'ed the phone. Problem is gone on reboot of course, but so is 13 months worth of app configuration. I would root the phone this time except that the screen is also acting up on me and the phone still has 4 months left on the Costco warranty that I got (for free) with the phone. Wouldn't it be great if Android "L" allowed you to back up app settings along with apps without the need to root the phone first! Thx to all.
Click to expand...
Click to collapse
Follow-up: same problem occurred following FDR. It is related to MMS messaging and it is solved by removing all MMS messages from phone. I did not have this problem with JB. It showed up after OTA upgrade to KK. Too bad for those who like to keep their MMS messages.
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.
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?