So my V10 is rooted with Xposed Installed
Modules used: GravityBox, G4 TweakBox
I also used the FC on Second Screen Fix with the replacement files posted in forum
So here's my Glitches
1. Google Chrome will completely reboot my phone after a few minutes. Forced me to use Chrome Beta
2. Ever so often screen dims and gets brighter
3. BlueTooth isn't as reliable with my Car
4. Every time start up phone get promoted (optimizing apps) says 2 apps but not which ones.
Debating to reinstall OS and Re Root and do everything over. Hoping there are some custom roms out there to try
Do you have a recovery like TWRP? If you do I'd start with clearing your cache and dalvik cache. After you reboot and if you still have the problem reinstall chrome. Also the G4 tweakbox might not work correctly on the V10 and might need to be updated or removed. I had a problem on my G3 with SpeedBooster Xposed module causing reboots on my phone, but after I cleared the caches and updated the module everything was cleared up.
The two apps that get optimized at boot are not a glitch. It is the only thing keeping the second screen apps from crashing when you are using xposed. I've had no problems with chrome, Bluetooth, or my screen dimming, and I don't use any of the modules you named. So you're likely having problems with tweakbox and gravitybox. That's the tradeoff for using modules and root apps and such. The only xposed modules I use are Greenify and Flat Style Keyboard.
1-3 are not happening on my rooted V10, so you either screwed something up or have a defective unit.
As for #4, you installed the Contacts and InCallUI APKs that fix the second screen crash during calls when Xposed is installed. Delete their respective .odex files and it will not optimize them on every boot anymore.
---------- Post added at 23:37 ---------- Previous post was at 23:36 ----------
ubergeek77 said:
The two apps that get optimized at boot are not a glitch.
Click to expand...
Click to collapse
It is a glitch in that whoever posted those APKs didn't tell people to delete their respective .odex files, which gets rid of the optimizing on every boot.
No need. I flashed the No Name Rom in another board and honestly loving it. Had all the tweaks I needed without needing gravity box or g4 tweaks
Deleted, dunno why it double-posted.
It was probably gravity box messing everything up, it messed my phone up. G4 tweaks worked perfectly for me and others
Sent from my LG-H901 using Tapatalk
Related
Hello, I dont know if I should be posting here or in the ROM thread, but this may not be ROM related.
I flashed a new ROM recently. I installed these apps from the Play Store to make sure they were working fine :
SwiftKey, Wakelock Detector, and Tapatalk
They worked well without any issues. Later I restored a backup with TiB of multiple apps, including Xposed modules. Now these apps crash upon start or in the case of SwiftKey, when I try to access my themes.
I have many apps. It's there an easy way to find out what the issue is? I'm guessing it's another app, most likely an Xposed module, but I can't imagine what it would be.
Any advice would be appreciated.
Never-ending, the offender was an Xposed module called Force Fastscroll
Never mind *
Hi all
I am using a Samsung Galaxy Note 2 4.3 stock rooted and I am having some issues with greenify. Everytime I start the app to see if it working I get this message: "Auto-hibernation service is stopped" The problem is that I am not using a 3rd-party tool or any other mode as energy saving mode on my note 2 and I still get this message. What should I do to fix it?
thx
This same problem,
S III, rom > http://forum.xda-developers.com/galaxy-s3/development/rom-archidroid-v2-4-6-power-hands-t2354859
Xposed framework installed
Greenify is device administrator
I have full version
Please read the FAQ in post #2 in the main thread. Both of you may be having root issues.
If I may make a suggestion?
I started getting the same error message (it started right after I paid for the app). After reading "thousands" of pages I think I may have hit on the answer. Greenify is in "boost" mode, that somehow, even though it uses xposed framework, doesn't need root. So I checked supersu and greenify wasn't listed. Then I changed to "root" method and greenified an app, then supersu asked to allow greenify, thereby now having it listed again in supersu.
I then changed it back to "boost" and so far haven't had that error. Coincidently, Greenify seemed to work ok anyway even with that error.,
edit: well that blows, I started to get the error message again, so disregard what I wrote above. Maybe a fix is coming, or I'll live with manually starting auto-hibernation.
tnsmani said:
Please read the FAQ in post #2 in the main thread. Both of you may be having root issues.
Click to expand...
Click to collapse
No, I check this 3 times ...
colin p > nothing, still this same problem
anyone has ideas, what else, I can do ?
Just to add additional info, this auto-hibernation error only started after I bought the Donation Package. I don't know if it's something to do with the additional options or not. Before I bought the program, auto-hibernation worked fine.
I have a Nexus 4 (rooted with towel-root) and SuperSu and of course the Xposed framework. I uninstalled/re-installed Greenify, as well as the Donation Package and still the error pops up the first time I open Greenify. I then have to manually start auto- hibernation and it works ok after that, at least it "seems" to as everything is under the hibernated section.
After I re-installed, SuperSu asked to allow Greenify root access, so it is properly listed. I would imagine that if a significant few of us have the issue, a future update will address the error problem.
I would like to try to enable Greenify as root mode. Will the message appear?
If it isn't I would then disable the Greenify module in Xposed, then reboot (no soft reboot, just to be sure), enable module, reboot again, and then select boost mode within Greenify. Then make a last reboot. Then inspect the problem.
This is not a definite fix, though in some weird circumstances, it might work
TechnoSparks said:
I would like to try to enable Greenify as root mode. Will the message appear?
The message appears in either root or boost mode on the first time the program is opened after a boot up.
If it isn't I would then disable the Greenify module in Xposed, then reboot (no soft reboot, just to be sure), enable module, reboot again, and then select boost mode within Greenify. Then make a last reboot. Then inspect the problem.
Tried your suggestion and still get the "auto-hibernation has stopped" error.
This is not a definite fix, though in some weird circumstances, it might work
Click to expand...
Click to collapse
Unfortunately, no dice. Still get that error, thanks anyway.
By George...
Well after a lot of screwing around, I think (at least for my circumstances) I "may" of found the answer. Because the error said something like "auto hibernation service is being blocked by 3rd party tool or system settings (ex.stamina mode in sony devi es. autostart manager in MIUI) Please whitelist greenify for automatic hibernation to work", I uninstalled Donkey Guard and Cydia Substrate (they were installed a couple of days before I got the pro version of Greenify, even though there was no problem with them before I got the paid version of Greenify), but still got the error. Ruling out program issues, this time I actually shut down my phone (no reboot or soft reboot) and on opening Greenify, no error. Since I was using the reboot toggle in "Notification Toggle", I tried rebooting through xposed (not soft reboot) and this time, no error. Tried again with Notification toggle and got the error.
So, at least for me, I think I may have solved the issue.....for now.
BTW thanks TechnoSparks as you gave me something to work with.
colin p said:
Well after a lot of screwing around, I think (at least for my circumstances) I "may" of found the answer. Because the error said something like "auto hibernation service is being blocked by 3rd party tool or system settings (ex.stamina mode in sony devi es. autostart manager in MIUI) Please whitelist greenify for automatic hibernation to work", I uninstalled Donkey Guard and Cydia Substrate (they were installed a couple of days before I got the pro version of Greenify, even though there was no problem with them before I got the paid version of Greenify), but still got the error. Ruling out program issues, this time I actually shut down my phone (no reboot or soft reboot) and on opening Greenify, no error. Since I was using the reboot toggle in "Notification Toggle", I tried rebooting through xposed (not soft reboot) and this time, no error. Tried again with Notification toggle and got the error.
So, at least for me, I think I may have solved the issue.....for now.
BTW thanks TechnoSparks as you gave me something to work with.
Click to expand...
Click to collapse
No problem mate. If it really works for a long time, it might be good to report here as I may take your method as a suggestion to other people facing the same problem as well. :good:
romdroid. said:
I am using a Samsung Galaxy Note 2 4.3 stock rooted and I am having some issues with greenify. Everytime I start the app to see if it working I get this message: "Auto-hibernation service is stopped" The problem is that I am not using a 3rd-party tool or any other mode as energy saving mode on my note 2 and I still get this message. What should I do to fix it?
Click to expand...
Click to collapse
I seem to have this same problem, but I don't think it's easily repeatable, which makes it hard to narrow down a possible cause. I have a Samsung Galaxy Note 3 running Android 4.4.4 but it's not rooted, so the other posts here (which I think all involve root) don't seem to apply in my case. Is there a possible known cause and/or solution for this problem of auto-hibernation stopping on unrooted devices? Thanks for your help!
Can anyone confirm whether it was fixed in 2.4.4 beta 1 or beta 2?
oasisfeng said:
Can anyone confirm whether it was fixed in 2.4.4 beta 1 or beta 2?
Click to expand...
Click to collapse
I had not got this message for quite a long time, but after updating to beta 2, the first time I rebooted and opened Greenify, I got this message. Afterwards, for the whole of today, I haven't got it.
Everything is working great for me.
Make sure you have SuperSu (latest)
Also after installing Greenify, set it as a device administrator.
Settings>security>device administrators>select Greenify.
Enable accessability as well (settings>accessibility>Greenify>Enable.
I have these enabled and have no issues.
Sent from my Nexus 4
gorilla p said:
Everything is working great for me.
Make sure you have SuperSu (latest)
Also after installing Greenify, set it as a device administrator.
Settings>security>device administrators>select Greenify.
Enable accessability as well (settings>accessibility>Greenify>Enable.
I have these enabled and have no issues.
Sent from my Nexus 4
Click to expand...
Click to collapse
You are right. After my last post, I found that Greenify was not enabled in Accessibility settings.
After every update, the Accessibility setting has to be re-enabled. Why?
tnsmani said:
You are right. After my last post, I found that Greenify was not enabled in Accessibility settings.
After every update, the Accessibility setting has to be re-enabled. Why?
Click to expand...
Click to collapse
for me i have to enable it in accessibility after every restart of the phone ....
Anyone found a solution to this? I am getting the same error.
oasisfeng said:
Can anyone confirm whether it was fixed in 2.4.4 beta 1 or beta 2?
Click to expand...
Click to collapse
HI Oasis - just to reply that I am still getting Auto-hibernation stopped with Greenify v2.5.1
Basically after a while auto-hibernate just seems to stop. I have all my apps waiting to be hibernated even after a few hours of screen off. I do not get the 3rd party message saying auto-hibernation is stopped. I have Accessibilty on and have given Greenify Device Administration rights.
I will get the 3rd party message if I force close Greenify or if I reboot. In those cases Accessibility will have turned itself off. After turning Accessibility back on, the message disappears but I still have apps waiting to be hibernated after seveal hours of screen-off.
After every reboot, I find that Greenify does not seem to ask SuperSU for root access. Even though I've granted Greenify automatic access,the log files for SuperSU never show Greenify as either being granted or denied rights. I know that Greenify is meant to ask for those rights when the screen is off. I guess it might be another app is locking the device when the screen is off before Greenify can ask for access. I've tried removing Device Admin privileges for other apps and remove PIN unlocks but this does not seem to help.
The only way I have managed to get Greenify running again is to uninstall and reinstall, which seems to be the only way when the screen is on that I can get it to request root access via SuperSU. This does mean I cannot use the Xposed installer options, because I would first need to reinstall Greenify, grant it root access via SuperSU, then enable the XPosed module, then reboot. But after reboot SuperSU access seems to be withdrawn and I can't get it to request root unless I uninstall and reinstall.
I'm sure I'm missing something but I'm not sure what. I am not sure if there is a way of forcing Greenify to request SuperSU access even when the screen is on without having to reinstall.
I am rooted with SuperSU 2.4 and Xposed installer, HTC One on Viper 7.02 ROM, Greenify 2.5.1 with donation package.
EDIT: I've found that I can get Greenify to ask for Root Access through Xposed if I first degreenify Facebook, re-greenify Facebook, launch another app which wakes up Facebook (eg Agoda) and then request Greenify to cut-off the wake-up. Seems to be working.
EDIT2: Alas, still having problems. Usually nothing auto-hibernates after charging the phone. Yesterday it was working fine, today I unplugged, started some apps, closed the phone and went for breakfast. 1.5 hours later the apps were still waiting to hibernate. Am completely lost on what to do next.
Dronak said:
I seem to have this same problem, but I don't think it's easily repeatable, which makes it hard to narrow down a possible cause. I have a Samsung Galaxy Note 3 running Android 4.4.4 but it's not rooted, so the other posts here (which I think all involve root) don't seem to apply in my case. Is there a possible known cause and/or solution for this problem of auto-hibernation stopping on unrooted devices? Thanks for your help!
Click to expand...
Click to collapse
I occasionally get this message, generally after an update to Greenify, but just tap on the message and continue on with my day. After exhaustive (I'm rather OCD) research, the general consensus is to forget about it as it is just Greenify's way of letting you know that the auto-hibernation has stopped and needs to be restarted. I have gone without tapping on that message and the service still starts up all by itself.
My advice is to open Greenify after an update (updates have slowed considerably anyway) and just tap on the message and it will be good to go until the next update.
Thanks for the response. I have been tapping on the message when I notice it, but it still seems to appear without updates to Greenify. I've tried checking a little more, though probably not as exhaustively as you did, and I suspect that there's some kind of conflict with Tasker. One of the main things I do with Tasker is alternate between "home" and "work" modes, part of which involves using a screen lock for "work" and turning it off for "home". It seems like when things are working fine at home, I go to work making it switch to work mode, and return home at the end of the day going back into home mode, Greenify complains. Since Greenify only works without a screen lock in non-root mode, I'm guessing this switching may be affecting thing, but I'm not completely sure. I guess I just have to live with it. One thing I've tried doing to mitigate the problem is add a Greenify hibernate action to my Tasker profile for turning mobile data off when the screen goes off. I'm not sure how well it's working, because at work I normally hibernate manually and at home I often don't worry about it, but even if it's not working, I think I get a placebo effect of thinking it's doing *something* so I'm less concerned about checking to see if Greenify has stopped auto-hibernating.
Greenify "went away" as did two apps it had hibernated, now I can't re-install them
Hi,
I recently rooted my AT&T LGv30 and installed TWRP and Magisk 1.6. I then installed Xposed via Magisk Manager and played with it a bit. I went on to install Greenify donation and enabled all the beta and aggressive stuff, as well as Xposed integration. I later discovered that Xposed breaks SafetyNet checks so I decided to remove it. When I did, Greenify "went away". I had to re-install it. It was only later that I noticed 2 other apps were missing, namely Xmeye (a security camera app notorious for consuming battery) and Spotify (here I was just playing around, but Greenify said it was using battery, so...). These were the only two apps I had added to Greenify.
I then attempt to re-install both of these apps from the Google Play store. It goes through the process of downloading, then installing, but at the end of the installation process, the Google Play button simply reverts back to "Install", as if nothing happened. The same thing happens when I try again, on either app. I can install any other app just fine.
I've run the latest Xposed uninstaller zip from recovery, but this didn't help. I do have a vague recollection of Greenify continuing to run in root + Xposed mode after Xposed had been removed, if that makes any sense. Eventually, after a subsequent re-install of Greenify (not if before or after Xposed was removed), it then walked my through the setup again, and is now running only in root mode. Yet, the problem with the two apps remains.
I'm hoping someone has a suggestion before I wipe everything and start over.
Thanks,
Daniel
Following up on my own post. I ended up installing SD Maid, which was able to show me both Spotify and Xmeye as "stopped". From the app I selected to delete both applications, which I could not do anywhere else, as they didn't show up in normal apps. My guess is that Greenify with Xposed and therefore root caused some file ownership issue that the normal utilities were not able to handle.
Daniel
DanielCeregatti said:
Following up on my own post. I ended up installing SD Maid, which was able to show me both Spotify and Xmeye as "stopped". From the app I selected to delete both applications, which I could not do anywhere else, as they didn't show up in normal apps. My guess is that Greenify with Xposed and therefore root caused some file ownership issue that the normal utilities were not able to handle.
Click to expand...
Click to collapse
Root cause likely resides elsewhere; Greenify doesn't mess with permissions.
Davey126 said:
Root cause likely resides elsewhere; Greenify doesn't mess with permissions.
Click to expand...
Click to collapse
Yet the two apps managed by Greenify stopped working. So you're saying correlation does not equal causation? Because the evidence here indicates otherwise. Just sayin'...
DanielCeregatti said:
Yet the two apps managed by Greenify stopped working. So you're saying correlation does not equal causation? Because the evidence here indicates otherwise. Just sayin'...
Click to expand...
Click to collapse
Correlation assumed but unproven. Greenify has been around a long time with a large user base. The situation you describe appears to be an outlier.
First off, T-Mobile version H932 rooted with bootloader unlocked and TWRP installed.
I was a long time user of Cyanogenmod/Lineage on other platforms in the past and overall prefer AOSP based ROMS that are close to stock. So, I have tried PixelExperience, Lineage, and LiquidRemix on my V30. I like them all but overall I like LiquidRemix the best mostly due to some of the LiquidLounge options.
However, I have 3 things I miss. I could probably do without them but I think my overall usefulness of the phone is better when I have them.
1. WiFi Calling - I have poor coverage in my office until TMO deploys Band 12 or Band 71 in my area. Not on schedule for almost a year yet.
2. OK Google support. I have tried numerous things to get this working on all 3 of the custom roms but it simply does not. Sounds like a MIC volume issue currently in all AOSP based ROMS on the V30. I use Android Auto (with a headunit) and not having this is kind of a pain.
3. Google Pay NFC support. I installed Magisk on all 3 custom ROMS but never could get it to fully pass all the safetynet checks.
As for running Stock. I know it would fix 1&2 above, but if I kept the device rooted and bootloader unlocked I am not sure #3 would be fixed. However, I can deal with that. What I hate about LG Stock overall is the interface, all their crap, and especially their dialer. I previously was side loading APK version of Google Dialer but it is missing the SPAM features and such unless you can flash it. I also sideloaded a pixel launcher and GCAM. But the dialer thing was always a pain.
I am going to try the debloated/magisk 20p STOCK. Anyone using this and have suggestions on how to get it working with Google Pay, Google Dialer, etc?
Next phone, I will probably spend the money on a pixel
Havoc is pretty awesome
TheCoryGuy said:
Havoc is pretty awesome
Click to expand...
Click to collapse
Yes, I'm sure it is. The guys doing custom ROMs do great work. But... Does I'm sure none of the 3 things I listed work on it.
Some day we'll get Wi-Fi calling in a custom ROM. One would think this would be more a standard method built into Android itself
I've got a H931 (basically daily driver with us998 20g) and a ls998 that I've used to test various roms and am now experimenting with serious debloating us998 20g on it.
I'm also accustom to Lineage, but as you know, there are not official builds for all devices. While the available roms are good, they are still a bit away from supporting all the basics.
In the meantime (and possibly for longer), just got through debloating the ls998. Now only 27 apps installed. Everything I need is working, very well actually. Looking at debloating even further. Watching to see if there are any ill effects.
It's difficult to determine what is the best, most productive way to go. At this point for me though I think it's debloating a stock rom. Time consuming but I hope worth it.
Good luck with your choice, Cheers
So I am on de-bloated stock with a few mods (google dialer, gcam, pixel launcher. Only thing not working at all is Google Pay. Magisk hide not working to fool it. Not a big deal.
thebitjockey said:
So I am on de-bloated stock with a few mods (google dialer, gcam, pixel launcher. Only thing not working at all is Google Pay. Magisk hide not working to fool it. Not a big deal.
Click to expand...
Click to collapse
That's easily fixed. Go to set->apps->google.services and delete cache and data. Make sure to hide magisk and any apps u don't want to see it first, reboot. Worked for me.
Cheers
AsItLies said:
That's easily fixed. Go to set->apps->google.services and delete cache and data. Make sure to hide magisk and any apps u don't want to see it first, reboot. Worked for me.
Cheers
Click to expand...
Click to collapse
Can you be more specific? I did what I think you mentioned:
Setup Magisk-Hide to hide from GPay, Google Play Store, and Google.
Cleared data and cache for Google Play Services (I assume that's what you meant?)
Rebooted, checked GPay, and it still says I can't use it because my device is rooted/altered.
Running Magisk 18.1, manager 7.1.1. Safetynet passes (both green checkmarks). What am I missing?
schwinn8 said:
Can you be more specific? I did what I think you mentioned:
Setup Magisk-Hide to hide from GPay, Google Play Store, and Google.
Cleared data and cache for Google Play Services (I assume that's what you meant?)
Rebooted, checked GPay, and it still says I can't use it because my device is rooted/altered.
Running Magisk 18.1, manager 7.1.1. Safetynet passes (both green checkmarks). What am I missing?
Click to expand...
Click to collapse
You're not running any Xposed modules, are you?
ChazzMatt said:
You're not running any Xposed modules, are you?
Click to expand...
Click to collapse
Nope, no Xposed at all, never installed it. Only one Masgisk module (Google dialer). VS996 20i otherwise (installed via TWRP... so stock rooted overall).
I thought I read that we need Magisk Canary now, as 18.1 isn't enough by itself. Another tip was to manually Magisk-Hide Google Play Services? I didn't want to dig in that deeply, if others are able to get by without these tricks...
schwinn8 said:
Nope, no Xposed at all, never installed it. Only one Masgisk module (Google dialer). VS996 20i otherwise (installed via TWRP... so stock rooted overall).
I thought I read that we need Magisk Canary now, as both 18.1 isn't enough by itself. Another tip was to manually Magisk-Hide Google Play Services? I didn't want to dig in that deeply, if others are able to get by without these tricks...
Click to expand...
Click to collapse
I don't know. Mine was hiding from Google Pay very well on18.0 and then 18.1 -- until I decided I cared more how my status bar icons looked than Google Pay.
So had to go Xposed route even though I know that can't be invisible from Safety Net. I made the choice on purpose.
ChazzMatt said:
I don't know. Mine was hiding from Google Pay very well on 18.1 until I decided I cared more how my status bar icons looked than Google Pay.
So had to go Xposed even though I know that can't be invisible from Safety Net.
Click to expand...
Click to collapse
Stock rooted US998.
* Battery circle with percentage number inside, instead of TWO stock LG battery icons (wasted space and looks ugly). How complete the circle is also indicates percentage.
* Actual LTE symbol, not silly"4GLTE".
* H for HSPA, not "4G".
* Gradient distinction for both carrier and Wi-Fi strength.
Some are build prop edits, but I'm also running two Xposed modules.
Sent via open market LG US998 V30/V30+
schwinn8 said:
Can you be more specific? I did what I think you mentioned:
Setup Magisk-Hide to hide from GPay, Google Play Store, and Google.
Cleared data and cache for Google Play Services (I assume that's what you meant?)
Rebooted, checked GPay, and it still says I can't use it because my device is rooted/altered.
Running Magisk 18.1, manager 7.1.1. Safetynet passes (both green checkmarks). What am I missing?
Click to expand...
Click to collapse
Funny, in that I just tried my procedure on my 2nd device and it didn't work - but still working / worked on the H931...
My guess is that on one, Titanium bkup wasn't installed (installed after enable gpay), on the other, already installed?
will post back if I figure it out.
Try magisk hide props module
Bupreno said:
Try magisk hide props module
Click to expand...
Click to collapse
What is "props module"?
schwinn8 said:
Can you be more specific? I did what I think you mentioned:
Setup Magisk-Hide to hide from GPay, Google Play Store, and Google.
Cleared data and cache for Google Play Services (I assume that's what you meant?)
Rebooted, checked GPay, and it still says I can't use it because my device is rooted/altered.
Running Magisk 18.1, manager 7.1.1. Safetynet passes (both green checkmarks). What am I missing?
Click to expand...
Click to collapse
Go to Magisk forum. It has detail instructions how to pass Google pay.
You have to install old version of Google service frame work in order to make it.
It's working fine on my phone.
I have Oneplus n10 unlocked/global
With magisk 24.1
No rom(s)
Not sure what Magisk module caused this issue. My guess was MicroG-Gapps.
After a few reboots Oneplus launcher (and third party launchers) keep stopping
I keep getting XYZ keeps stopping (Weather, Google, Oneplus Account, Duo, Maps, Youtube, Google Fi,)
After a few mins of constantly tapping close app it seems that Malware-bytes keeps opening,.
I cannot load my icons/homescreen
I can sometimes get into settings via drop down notifcation bar and clicking on the gear icon.
I can get into apps and open a few apps from there.
As soon as malware-bytes starts opening itself it becomes a tug-of-war.
Say I get to open magisk malware-bytes auto opens every few sec and sometimes will stop for maybe 2mins.
I have to go back to Settings>apps>magisk>open and act quicky before malware-bytes opens again and takes me away from previous app.
I have TWRP 3.5.2_10-1_eduardoa3677 installed with a few backups pre crash. Backups do not repair this issue TWRP cannot load/access SDcard or OTG/USB
I have gone into filemanager (TWRP) and removed MicroG-Gapps obviously still everything is still crashing.
My guess is everything is just corrupt.
I was able to disable all Magisk Modules.
Any advice on restoring apps?
At this point I am leaning twords flashing DerpFestR Rom?
Edit: Reinstalled Microg-Gapps that has stopped the constant apps crashing. I cannot open anything that uses googleplay services / google. I might try to install Gapps From androidfilehost or maybe from a rom forum on XDA. hopefully that will reset google services?