Hello all,
the S4 is my 4th Android cellphone and I also have a few more other Android devices.
Since the last update, I have a few apps that crash to to the main screen with no error message once in a while.
I NEVER had this problem with any of my current or previous Android devices (except the S4 with latest patch, it was fine before the patch btw).
So before I wipe the phone I wanted to know if it was a common problem with the S4 and the latest update.
Thanks.
Note: The phone is stock + CF Root, thats it.
not a common issue no: was your update OTA? First thing I would do is go into recovery and wipe the cache and the davlik cache and re-boot. If the problem persists, you may want to wipe the data -- it sounds to me that the issue is some remnant data from an app that needs updating to the latest firmware -- I presume you've gone into play store and updated all your apps since the OTA update of the firmware?
Related
Was on stock/rooted 4.1.2, twrp 2.3.1.1 and applied the signed OTA 4.2 update via twrp.
The update installed with no errors (saved and restored root via voodoo, schweetness) However, whenever I reboot I get through normal colored X screen and then a dialog box saying 'andriod updating, starting apps' which shows for a few seconds right before it goes to the 4.2 lock screen.
Could this be due to some incompatible programs still installed or is this normal behavior others are seeing?
Also it seems that the 'complete' boot time seems longer than 4.1.2 which I assume is normal as well??
Afterwards the system seems to run normal/stable and very quick.....
Thanks
Totally normal. It's the apps cache rebuilding since it was cleared on the install. If you use twrp to clear cache and dalvik....mainly dalvik, you'll see it do it again. Its normal.
gokart2 said:
Totally normal. It's the apps cache rebuilding since it was cleared on the install. If you use twrp to clear cache and dalvik....mainly dalvik, you'll see it do it again. Its normal.
Click to expand...
Click to collapse
Thanks for the confirmation, much appreciated.....
bonzer2u said:
Was on stock/rooted 4.1.2, twrp 2.3.1.1 and applied the signed OTA 4.2 update via twrp.
The update installed with no errors (saved and restored root via voodoo, schweetness) However, whenever I reboot I get through normal colored X screen and then a dialog box saying 'andriod updating, starting apps' which shows for a few seconds right before it goes to the 4.2 lock screen.
Could this be due to some incompatible programs still installed or is this normal behavior others are seeing?
Also it seems that the 'complete' boot time seems longer than 4.1.2 which I assume is normal as well??
Afterwards the system seems to run normal/stable and very quick.....
Thanks
Click to expand...
Click to collapse
Hi bonzer2u,
i am stock, rooted but with no custom recovery and the Voodoo rootkeeper app. I am contemplating doing the OTA update but heard from other posts that SuperSU v0.98 caused major headaches and issues. Since you were successful in installing the update I was hoping you can confirm if you had the SuperSU installed with the latest version?
Thanks,
JBIRD
Hi
When I first got my S5 I updated OTA to 4.4.2. Hated the restrictions but batt life was good at that point.
So after playing with the phone and installing apps batt life became bad so I reset the phone.
My Batt was still draining more quickly even after a factory reset even though restore option was unticked and no new apps after the reset I ran titanium backup and froze most of the user apps but batt drain was still bad.
In settings>battery it shows Android System as the highest percentage.
When i reset the device to factory settings when it loads up i see SuperSU and GSAM battermonitor root companion installed along with the other essential bloatware apps from Samsung . It also auto updates Chrome as well as Samsung apps like Chaton , wallet even though I turned off Autoupdate apps in the play store ?
How do I stop those Stock Apps (eg ChatOn ) from Updating ? - Chrome is not stock iirc but it also gets updated.
Im guessing my batt drain after a reset is being affected because of updates to system/bloatware apps. Whilst playing around somehow maybe have unknowingly integrated those system updates into the system rom ?
So if I accepted that OTA (guessing 4.4.4) update will all system software be fully reset to stock (whilst still retaining root via SuperSU Survival mode ) so that I can get the similar batt life/drain like when I first got the phone ?
Or what other options do i have so I can reset all the factory software to stock (no updates) ?
I have purchased and installed SuperSU and enabled survival mode.I also installed buzybox.
My second question : How do I stop Chat on ,Samsung Wallet etc from auto updating after a fresh reset ?
AzNDuD3 said:
Hi
Click to expand...
Click to collapse
The update will most likely be downloaded but not installed because you are rooted. You can however flash the entire 4.4.4 rom with Mobile Odin Pro and keep root IF your device is suported. Better check that first.
Hi thx for the reply.
I just dled mobile odin and it said device not supported ? SM-G900i
What are my other options ?
Going to the Sammobile site for the rom it shows the latest 4.4.2 G900IDVU1ANG3 firmware for my device SM-G900i is Android 4.4.2 not the 4.4.4 i guessed
IIs it safe If i flash from my current firmware G900IDVU1ANE1 June to an earlier dated firmware like the G900IDVU1ANC6 April ] [/I]
EDIT/B]
Sp Ive been doing abit of searching and i found Rashr as well Phils Touch Recovery that work on the Galaxy S5. Phils recovery is installed and I can boot into it . The options look similar to CWM Recovery
Im not sure which steps i should take for a fresh firmware install. And I dont want to just choose the wrong option and brick my phone
Should I choose Wipe Data/Factory Reset and then install Zip ?
Latest Firmware Reference for Galaxy S5 SM-G900I
Country/Carrier Date Version PDA Kies
Australia (Optus) 2014 August 4.4.2 G900IDVU1ANG3
Australia (Optus) 2014 June 4.4.2 G900IDVU1ANE1
Australia (Optus) 2014 April 4.4.2 G900IDVU1ANC6
A bit of a weird one.
Updated to CM12.1 Atares ROM :good: I have been running CM12 ROMS for ages and updated to the 12.1 via the OTG in settings and using Nightlies.
I have only noticed problem yesterday and going back to CM12 just causes more problems, also going back to the previous Nightly doesn't help
I cannot access Google Play Store. 'Check your connection and try again' All WiFi settings are correct etc... even when using mobile data, I still cannot get access.
My GT1905 has disappeared off my devices list on the play store too! I've also noticed that Google+ has disappeared off my phone too, but more interestingly my SUBCARD app has gone too! (not sure if others have gone but I noticed this as I like a subway :yum: ) But... if I go to the playstore on my phone (or PC/tablet etc...) via chrome it says it's installed! I cannot access it via my apps list.
So other than doing a wipe of my phone if there any other suggestions?
Did you perform a full wipe before updating?
You cannot just flash it over an old CM 12 you need a fresh install.
Lennyz1988 said:
Did you perform a full wipe before updating?
You cannot just flash it over an old CM 12 you need a fresh install.
Click to expand...
Click to collapse
Well I would of done if it hadn't come via the OTA updates, never noticed it went from CM12 to CM12.1 until Monday/Tuesday last week.
Will do a full wipe later on today and see what happens.
GiGoVX said:
Well I would of done if it hadn't come via the OTA updates, never noticed it went from CM12 to CM12.1 until Monday/Tuesday last week.
Will do a full wipe later on today and see what happens.
Click to expand...
Click to collapse
Custom rom OTA's are not like official rom OTA's. Doing a wipe is still recommended. Anyway, force stopping google play and clearing app cache and data might help you in this case.
Had similar issues on other roms, even though I wiped before flashing.
GDReaper said:
Custom rom OTA's are not like official rom OTA's. Doing a wipe is still recommended. Anyway, force stopping google play and clearing app cache and data might help you in this case.
Had similar issues on other roms, even though I wiped before flashing.
Click to expand...
Click to collapse
I tried clearing all data and cache and also force stopping. WhisperPush kept crashing too.
Wiped the phone and started again, all sorted now with CM12.1 latest nightly build
Cheers for the advice guys.
Hey guys,
Wanted to try and find out whether anyone else is experiencing issues with Google Play Services (9.4.52) crashing after upgrading to Nougat OTA?
I thought I may have a botched install so tried the following:
- Cleared cache
- Reset and didn't restore from backup
- Reset and only installed stock apps
- Safe mode
- Cleared Google Play Services data
- Unsubscribed from all Google beta testing apps
I still can't figure this one out, even after a hard reset back to stock it still kicks up a play services crash about once ever 10-20 minutes... very weird... and frustrating
Anyone else had this issue? Or got any suggestions?
I had the exact same problem after accepting OTA yesterday via the beta program. I was on 6.0.1 on my 6P (no root, no custom rom, locked boot-loader). All Google Apps and Services crash including Messenger (SMS). I performed a hard reset with no luck. I flashed OTA with no luck. Only solution was to unlock boot-loader, flash recovery, and go back to stock. I will try again today.
cybrdude said:
I had the exact same problem after accepting OTA yesterday via the beta program. I was on 6.0.1 on my 6P (no root, no custom rom, locked boot-loader). All Google Apps and Services crash including Messenger (SMS). I performed a hard reset with no luck. I flashed OTA with no luck. Only solution was to unlock boot-loader, flash recovery, and go back to stock. I will try again today.
Click to expand...
Click to collapse
Will try that method instead, the crashes have died down again but I can't find any correlation between specific apps and what's causing the crashes! If I find a solution I'll post.
I think there may be a problem with the final release. It seems Google pulled 7.0 from their factory images site. I downloaded 7.0 for nexus 6, 6P and 9 earlier today and only the download for the Nexus 9 is still available. I don't know which version is giving you a problem but on the Nexus 6P Google earlier posted version MTC20F. I was going to flash it this evening but I think I'll wait and see what version they post back to the factory image site.
Google has finally posted the OTA and Full ROM images for 7.0. Both have the exact same problem on my 6P. All Google Services and Apps crash and the phone reboots randomly (often). I am at a loss. Obviously issues exist with 7.0 and 6P. Google seriously needs to address this non-sense.
Hello. I have a Sprint s7e. Yesterday I updated my phone to the Nougat Beta and everything was going good. This morning I got a notification that an update was available so I accepted and it once it finished my phone keeps rebooting. It will fully load and within a minute of use, it will reboot. Even if I don't use the phone after the reboot, it will reboot in about a minute. Anyone else experiencing this? Possible fixes? I tried Safe Mode and it still rebooted. One mistake I made was I have items disabled with EZ Disabler which I forgot to re-enable. Ive done this before on Marshmallow and it never gave me any issues. Could this be the problem?
Is there a way to revert back to the older Beta Version, or even Marshmallow? Thanks
I would try a factory reset
Sent from my SM-G935P using Tapatalk
I would either try a factory reset or clearing the Cache. The last option would be a factory reset back to Marshmellow and then re-download the beta.
This happens on my wifes s7 edge. I assume its because of the (snapdragon 820) bootloader not liking root. Factory reset didnt solve issue for me because it threw up dm verity argument errors. Only thing that worked was flash combination firmware to completely wipe.
I had a similar issue. I would wipe data and clear cache. Start fresh. Android 7.0 vs 6.01 might have had compatibility issues or data corrupt caused bootloop. This is just my opinion. It sucks redoing everything, trust me. I had the Note 7 then got the s7 edge on Thursday, set it up on the stock 6.0.1. Then Friday found the Nougat beta and did my 1st download. It keeper rebooting constantly after It had finished set up.of course. So, I had to reset it up. I was able to go a day then reboot stuff happened again. So I data wiped and did it all over but this time I did not restore apps. I did fresh install and happy to report no issues thus far.
Sorry for long drawn out personal response, was just trying to share my experience in the event that it is useful to you.
Sent from my SM-G935P using Tapatalk
Has anyone had a problem with "Android Wear has stopped"? It started with the last update to PL3. I've tried clearing app cache and data as well as clearing cache from recovery. Hopefully the next update will fix it, but I've been wondering if anyone with a android watch has had a problem.