View Single Post
Faz's Avatar
Posts: 284 | Thanked: 80 times | Joined on Mar 2007 @ London, UK
#29
I initially steered clear as I didn't want to enable developer mode and start messing around so early on, but after a couple of days I could resist no more!

Just my luck I had similar as others have reported, where I could open Google Settings, but Play Store kept closing immediately after launching.

After a couple of sleepless nights, a few reboots, some rmdir -rf and chowns I finally managed to launch Play Store and successfully install some apps. Not sure what exactly fixed it, but the final steps were uninstalling then installing Android support, after I had already performed the rycnc and ensured the system directory was owned by root:root.

Also I recall at one stage no Android apps would load at all, although I did have support installed. At this point, I think I already performed the rsync command and ownerships were all root. I removed Android support, had a nose around /opt/alien/ and noticed the system directory was still there. Process listing confirmed alien dalvik was no longer running.

Next I reinstalled Android support and tried Play Store, which was already installed. It worked! It did crash a couple of times but seems to have settled down now.

My lock screen now has a number of briefcases with ticks, which I suspect is the notifications from the store, so unchecked this from its setting (first option) so hopefully at least won't receive any more.

I think the ownership of the system folder was the problem. I'll try to replicate later to pin in down, but first best get some sleep before the sun rises. |-)