I'm running Slimkat on my Nexus 7 2012. I just got a notification for 4.4.3 . I opened it and thought it was from the Slimkat guys. But it was from Google.
I also noticed that it was downloading through Google Play Services. I've Force Stopped the app for now.
What will happen if it gets installed. Will it break stuff?
I'm running the latest TWRP recovery.
Should I make a backup, or it will be fine?
Related
I have tried cyanogen 11, and Lungo, and on both of those 4.4 ROMs I get an error after installing google play services. As soon as I install those, my keyboard reports an error, or my call app mallfunctions. Sometimes the whole rom crashes.
Could someone please pinpoint the problem for me, as I have tried latest TWRP and CWR recoveries to install the ROMs, cleaned every part of the phone before installing, and nothing seems to fix this problem.
ATTM, I'm on Lungo, and it worked perfectly till I updated google play with this crap.
Have you installed the current gapps for cm11? I think that could be the problem.
If the rom is 4.4.3 you need 4.4.3 gapps
http://www.androidfilehost.com/?w=files&flid=14703
About 3 weeks i installed the Kitkat rom stock on my N5.
Today i tried to see something about the OTA update to Lollipop, and surprisingly i saw isn't it arrived to me.
I just tried to Clear Data from the Google Services Framework- still the same.
Somebody know how can i get it ?
Thanks for answering,
Tal.
Are you rooted? If so, you'll need to unroot to take the OTA.
Sideload this via ADB: clickity-click.
Wait. I think you'll need to sideload the 5.0 update first, and then do the one I linked for 5.0.1. Can somebody confirm this?
First of all don't clear Google services framework data that messes up stuff pretty bad. Second d, this should be in q and a section. Third just flash the 5.0.1 factory images or there is a flash able zip out if you're rooted with custom recovery.
Sent from my Nexus 5 using Tapatalk
I agree wid op...
I have used kk for past 2-3 weeks... And notification never popped out...
I flashed manually 5.0 and i got ota for 5.0.1 ... I dont knw whats up wid google ota system...
5.0 ota seems pulled, Got 3 N5 which all have the ota prompt before, but none of them get the ota message now.
Sent from my Nexus 5 using XDA Free mobile app
So isn't it only on my device. OK.
Thanks !!
It never was your device. The OTA is rolling out in phases (not sure it's true that it got pulled but I could be wrong)... Just flash the factory images or lollipop stock ROM flashable zip. There are plenty of threads about this in the stickies...
Hey guys,
a few days ago and out of nowhere (haven't changed anything) my Google app stopped working. Everytime I only start the app or press on the search bar the app doesn't even show up - it just gives me the crash dialog. I tried different GApps and even clean flashed my ROM (Exodus 5.0 based on CM12). A friend of mine is getting the same error on CM12 nightlies. So it's not ROM related (but maybe CM12?). Have you guys got any suggestions?
Cheers
How did you solve the issue
Hi there members of xda
A few months ago i updated to marshmallow on my moto g3 , and the experience was awful, not to mention the touch screen issues. I successfully downgraded to lollipop by skipping gpt.bin and bootloader.img, and i used lollipop for a while then got bored of it, so i tried to install cm13 official. When i did that , my phone gets google play store and google play services FC's on cm13. I have set google play services all permissions .. I have tried a wide variety of gapp packages and they all have the same problem. Google play store instantly crashes when i tap it, if that helps atall.
For now, i reflashed marshmallow stock. Should i be flashing cm13 from stock mm , or stock lp.. becuase i havent tried flashing using stock mm , becuase i didnt think it would make a difference as i always wipe the system partition before flashing cm anyway. :/
Many thanks,
therealduff1
therealduff1 said:
Hi there members of xda
A few months ago i updated to marshmallow on my moto g3 , and the experience was awful, not to mention the touch screen issues. I successfully downgraded to lollipop by skipping gpt.bin and bootloader.img, and i used lollipop for a while then got bored of it, so i tried to install cm13 official. When i did that , my phone gets google play store and google play services FC's on cm13. I have set google play services all permissions .. I have tried a wide variety of gapp packages and they all have the same problem. Google play store instantly crashes when i tap it, if that helps atall.
For now, i reflashed marshmallow stock. Should i be flashing cm13 from stock mm , or stock lp.. becuase i havent tried flashing using stock mm , becuase i didnt think it would make a difference as i always wipe the system partition before flashing cm anyway. :/
Many thanks,
therealduff1
Click to expand...
Click to collapse
Which gapps did you use? If you are having issues on cm try CrDroid or BrokenOS (go to their G+ community)
Btw, on the cm thread Alberto posted a fix for the touchscreen issues.
Henriquefeira said:
Which gapps did you use? If you are having issues on cm try CrDroid or BrokenOS (go to their G+ community)
Btw, on the cm thread Alberto posted a fix for the touchscreen issues.
Click to expand...
Click to collapse
I installed an old build of cm in the end and then updated to new version via ota. thanks anyway !
Hi,
I have a new Moto G4 runnning Slim-athene-6.0.1.build.1.11-WEEKLY-20161111-1135.
I am trying to get my apps installed and running without error and experiencing one setback after the next, see attachment. Installing gapps along with the rom and I can't get passed the setup stage. Installing the rom, rebooting then installing the current gapps and the keyboard does not work.
The closest I have got to being up and running is installing prior version of the gapps Slim_minimal_gapps.4.4.3.build.5.8-60.zip. However once this is installed my apps won't run and prompt me to install Google Play Services, and once I do that I get constant errors that Google Play Services has stopped working and the phone is practically useless. I have read clearing the cache for the app fixes this, but not for me.
Anybody managed to beat this?
Wrong forum!