Hi,
i just installed greenify 2.6.2 beta 2 on my nexus 5 with android 5.0.1, working xposed (i use gravitybox without any problem), but it seems that greenify cant detect that i activated the module inside xposed.
Whenever i try to activate any funciont that needs xposed module it asks me to activate greenify module and reboot.
I tried rebooting but nothing changed
I have the same problem on my Nexus 5 as wel as on my Asus TF700.
I'm getting this also, on 4.0.4.
same on android 5.0.2 oneplus one cm12s
Can confirm the same.
Same here :/
Same. So frustrating. This update was supposed to fix the problem with deep hibernation interfering with certain apps (Drive, in particular), but now deep hibernation and all other Xposed features don't work for me at all. G3, 4.4.2
Same thing here with my device as well. I just updated to the Greenify v2.6.2 beta 2 on my rooted/xposed Verizon Galaxy Note 3 4.4.2 and I'm also getting the exact same error after trying to activate any of the Experimental Features that require Xposed. This appears to be a HUGE bug in this particular BETA version that spans several, if not all, versions of Android. This dev is good and he seems to be very responsive to his user-base, so I'd say we'll see an update with a fix very, very soon...hopefully today/tonight..
Same problem on kitkat nexus 4. I'm sure we'll have a fix soon. Going back to previous version until then.
same issue on oneplus one running 5.0.2 CM12 nightlies.
Have the same issue on LG G2 4.4.2, step back to beta 1
Same here... S4 4.4.2
the same problem moto G 2014, only greenify problem the other xposed are working normally
Same issue! Greenify not working with xposed at all. Could anyone please attach beta1 apk?
Sent from OnePlus One
Same here on ArchiDroid 3.0.x!
So it seems to be a general issue with the latest beta. After downgrading to previous version, everything's working again.
Very sorry for the broken xposed module in lollipop, beta 3 is rolling out to fix that.
+1 M8 sense based on 5.0.1
---------- Post added at 10:49 AM ---------- Previous post was at 10:45 AM ----------
Here is beta 3 with fix https://www.dropbox.com/sh/mspso6yvv1wbvju/AADc-vrK07my2C6-Drc20ErGa/Greenify.v2.6.2.beta.3.apk?dl=1
oasisfeng said:
Very sorry for the broken xposed module in lollipop, beta 3 is rolling out to fix that.
Click to expand...
Click to collapse
I'm not sure if anyone else experienced this yesterday after updating to beta 2, but incoming text messages stopped coming through because of beta 2.
I just updated to beta 3 and still am experiencing this same issue with receiving text messages, however the Xposed Framework issue has been fixed. So that's good at least.
I went ahead and downgraded back to beta 1 and I am back to receiving text messages just fine, as I always have with it and prior. I've been using Greenify since forever now so it's not something I Greenified plus I haven't Greenified anything in months either. I went through my list again just to check and I don't see anything abnormal that would be related.
It's just for receiving text messages, those whom I tested with did receive my text messages I sent just fine.
Any insight oasisfeng?
Tnx beta 3 is working fine.
misticalx said:
I'm not sure if anyone else experienced this yesterday after updating to beta 2, but incoming text messages stopped coming through because of beta 2.
I just updated to beta 3 and still am experiencing this same issue with receiving text messages, however the Xposed Framework issue has been fixed. So that's good at least.
I went ahead and downgraded back to beta 1 and I am back to receiving text messages just fine, as I always have with it and prior. I've been using Greenify since forever now so it's not something I Greenified plus I haven't Greenified anything in months either. I went through my list again just to check and I don't see anything abnormal that would be related.
It's just for receiving text messages, those whom I tested with did receive my text messages I sent just fine.
Any insight oasisfeng?
Click to expand...
Click to collapse
Do you have Deep Hibernation activated? And have you greenified the messaging app?
Related
After the last update I'm getting fc in greenify this is photo from log viewer
G.M.L.
Same here on beta 4, the device is 4.4.2 Touchwiz based tablet Note Pro 12.2 LTE. Greenify crashes right after clicking the icon ;(
Although it is still working fine along with MaterialUI design on OnePlus One @4.4.4.
EDIT:
Sorry, the error is somewhat different, although still seems to be related to layout:
Also a few lines earlier there ars some issues with something called GoogleTagManager, dunno if they are related but the PID mentioned in logcat looks the same, not sure:
Beta 3 still working fine. Also, even after upgrading, the widget preserved on the homescreen since beta 3 works fine too.
Same here. FC after greenifying any app. I thought it only fc on system app but when i tried to greenify user app, sameway, fc
Looks like an issue with google support classes included in the app, related to UI features.
Hope for a quick fix as on my OnePlus One - where the whole thing is working ok - new layout looks really astonishing
After the last update the problem its fixed!!!!"Thanks to the development!!!!!
G.M.L.
Too bad my problem still istn't solved ;(
still fc
i think greenify works by fc the apps
Hi,
My s5 has been randomly rebooting. Sometimes, it has happening when I am on the call, or in the mid night. Is any one has the same issue? Is the phone defective or hardware problem? My phone is never rooted.
jc_hwz said:
Hi,
My s5 has been randomly rebooting. Sometimes, it has happening when I am on the call, or in the mid night. Is any one has the same issue? Is the phone defective or hardware problem? My phone is never rooted.
Click to expand...
Click to collapse
My wife got hers a week ago and has till this Friday to take it back. This started happening a few days ago Also. Random. I know she also got that security update just a couple days ago
Sent from my HTC One_M8 using XDA Free mobile app
jc_hwz said:
Hi,
My s5 has been randomly rebooting. Sometimes, it has happening when I am on the call, or in the mid night. Is any one has the same issue? Is the phone defective or hardware problem? My phone is never rooted.
Click to expand...
Click to collapse
I have been having the same issue. I have had the phone since release and haven't had any problem, until about a month ago. It has rebooted a few times randomly. I am completely stock non-rooted.
I got one time today when I opened the YouTube app. I uninstall the update for the YouTube, and see what is going on
So I've noticed this happening for a few weeks now. Thought something was wrong with the phone and did a warranty replacement. New phone (not referb) does the same thing, just not as often. I think maybe it's an app running in the background now that had a bad update. I'm in the process of removing apps to see if it still happens.
1sae said:
So I've noticed this happening for a few weeks now. Thought something was wrong with the phone and did a warranty replacement. New phone (not referb) does the same thing, just not as often. I think maybe it's an app running in the background now that had a bad update. I'm in the process of removing apps to see if it still happens.
Click to expand...
Click to collapse
It has happened last mid night again. In today moring, I found my phone restart one time, because I saw the popup notice for reminding the back cover that means the phone restart already. Please tell us what happen after you remove the apps. I think it is the software problem rather than the hardware problem. I don't want to get replacement phone because it is refurbished phone.
jc_hwz said:
It has happened last mid night again. In today moring, I found my phone restart one time, because I saw the popup notice for reminding the back cover that means the phone restart already. Please tell us what happen after you remove the apps. I think it is the software problem rather than the hardware problem. I don't want to get replacement phone because it is refurbished phone.
Click to expand...
Click to collapse
Well I'm still trying to determine which app is causing it. For all I know, it could be the firmware T-mo pushed out prior to the latest one. T-mo says they haven't had reports on this issue so I don't want to blame the FW right off the bat. I have ruled out about 70% of my apps and right now have about 5 uninstalled and phone hasn't restarted in 3 days. Below is are the apps I have yet to try and the ones currently removed.
Current Removed:
Code:
'Disable Increasing Ring'
'netflix'
'uber'
'hbo go'
'battery widget'
'2x rdp client'
'pandora'
Yet to try:
Code:
Google Maps
Facebook
Chrome
chromecast
hangouts
tinder
lookout security
Touchpal Keyboard
Reuters
Beep'nGo
Might help if you let me know which ones you have in common above. FYI, I also tried removing my sd card like I saw in a few forums. Also, Tmobile says they don't give you referb phones. They give new phones that were returned to the store within a few days. So openbox, mine looked perfect.
1sae said:
Well I'm still trying to determine which app is causing it. For all I know, it could be the firmware T-mo pushed out prior to the latest one. T-mo says they haven't had reports on this issue so I don't want to blame the FW right off the bat. I have ruled out about 70% of my apps and right now have about 5 uninstalled and phone hasn't restarted in 3 days. Below is are the apps I have yet to try and the ones currently removed.
Current Removed:
Code:
'Disable Increasing Ring'
'netflix'
'uber'
'hbo go'
'battery widget'
'2x rdp client'
'pandora'
Yet to try:
Code:
Google Maps
Facebook
Chrome
chromecast
hangouts
tinder
lookout security
Touchpal Keyboard
Reuters
Beep'nGo
Might help if you let me know which ones you have in common above. FYI, I also tried removing my sd card like I saw in a few forums. Also, Tmobile says they don't give you referb phones. They give new phones that were returned to the store within a few days. So openbox, mine looked perfect.
Click to expand...
Click to collapse
I just do some research online. Many articles are talking about that the android 4.4.2 has randomly reboot bug. I think this the common bug for the 4.4.2. Hopefully, the 5.0 is rolling out for international version. I think t-mobile will update the s5 to 5.0 soon.
Its the 4.4.2 firmware. Its because of all the apps updating to the new lollipop 5.0 but where still on kit Kat. Remember now these apps are set to run on art now so i believe there conflict between the dalvik thats the norm. On 4.4.2. I noticed if i run my SM-G900T 4.4.2 in art mode the rebooting stops. So at the end of the day this means when 5.0 is released to our S5 the reboots should stop. If your bothered by the reboots just run the 4.4.2 in art mode. Good day☺
Sent from my SM-G900T using XDA Free mobile app
beachbum40 said:
Its the 4.4.2 firmware. Its because of all the apps updating to the new lollipop 5.0 but where still on kit Kat. Remember now these apps are set to run on art now so i believe there conflict between the dalvik thats the norm. On 4.4.2. I noticed if i run my SM-G900T 4.4.2 in art mode the rebooting stops. So at the end of the day this means when 5.0 is released to our S5 the reboots should stop. If your bothered by the reboots just run the 4.4.2 in art mode. Good day☺
Sent from my SM-G900T using XDA Free mobile app
Click to expand...
Click to collapse
I just turn off the VoLTE, and the phone runs for 10 days without any reboots. Do you think it is the problem of the VoLTE?
jc_hwz said:
I just turn off the VoLTE, and the phone runs for 10 days without any reboots. Do you think it is the problem of the VoLTE?
Click to expand...
Click to collapse
Could be.? I'm just making an educated guess that it's the fact that when our apps like YouTube, Gmail ,ect.. updated it seems that's when my reboots started. Volte could be a cause to. Your guess is as good as mine. But I truly believe it's the fact that the updated app where modified to art and 4.4.2 is dalvik. ?? I'm sure when the 5 update comes this will be resolved ☺
Sent from my SM-G900T using XDA Free mobile app
Will stock 4.4.2 unrooted run art? How would I enable that?
chazel3 said:
Will stock 4.4.2 unrooted run art? How would I enable that?
Click to expand...
Click to collapse
1.) Go into Settings, and About Device. Where it says: Build number press on this over and over again until it gives you the Toast message: Developer Options Turned On (something to that effect).
2.) Go back into Settings, and just below Security and above About device, you will see Developer options. Open this.
3.) 4th Item down is: Select runtime system. It should say: Use Dalvik. Change this option to: Use ART. It should work for a little bit, then Reboot your phone.
4.) All done!
Note: If you plan to Root your phone, and use Xposed, it is NOT compatible with ART runtime. If you plan to stay unrooted, or not use Xposed if you do root, then you are fine. You can always switch back if you decide to do this.
https://dl.google.com/dl/android/aosp/mantaray-lmy47d-factory-63eade7f.tgz
Have fun!
Hm, it's been sitting on "sending bootloader" for a while now. Should I be worried?
So far feeling very good and fast, nice update
Rand Brittain said:
Hm, it's been sitting on "sending bootloader" for a while now. Should I be worried?
Click to expand...
Click to collapse
Welp, doing it over on a different port and cable seems to have handled it.
Flashed it.
Might be placebo but it seems much smoother.
Also the recent bug is fixed and the toggles in the Account Sync have been changed.
Images flashed......"optimizing app 98 of 154" so first 5.1 boot should be soon.
Anybody tested this bug?
http://forum.xda-developers.com/nexus-10/help/android-5-0-sound-problem-charging-t2939672
tylerdurden83 said:
Flashed it.
Might be placebo but it seems much smoother.
Also the recent bug is fixed and the toggles in the Account Sync have been changed.
Click to expand...
Click to collapse
What about wifi performance and the audio bug wile/straight after charging/docked?
I don't understand what the bug is. I never experienced it before, but I can try to replicate it in 5.1 if you explain what I am supposed to do clearly.
isarebe said:
I don't understand what the bug is. I never experienced it before, but I can try to replicate it in 5.1 if you explain what I am supposed to do clearly.
Click to expand...
Click to collapse
What I got is, sometimes when starting the N10 while charging, there is no sound at all, and I have to reboot the N10 without charging to get the sound back.
I tried with 5.1 and so far, 5-6 times, no bug, but as I said is only happening sometimes before...
Audio Bug Squashed?
It looks like 5.1 has fixed the audio bug. It has for me at least.
Anyone experience lag when pulling the notification tray on the home screen?
matejilic said:
Anyone experience lag when pulling the notification tray on the home screen?
Click to expand...
Click to collapse
Using the default Launcher3, not really. The Google Launcher lags when pulling down the tray, and lags all other animations for that matter. It always has since 4.4, but I put up with it because I like the GEL. It doesn't lag anywhere else thankfully, so it's your call.
On March 10th I did a factory image update to 5.1 but did not wipe user data on both my Nexus 10 and 5.. At least for me, this is the best version of Lollipop I've experienced.
My Nexus 10 was more stable than my Nexus 5 on any 5.0.x release but it seems that all the issues I'd been experiencing are resolved. On 5.0.x my Nexus 5 experienced the memory leak causing UI slow downs, odd reboots, total freezes needing power cycles and frequent disconnects of both WiFi and my cell network.
Android 5.1.0 did break the K9 email reader but that was fixed this morning and Jota+ SMB support currently is not functioning. On the Nexus 10 my battery stats still does not update always showing 100% charge even when its been off the charger for hours. Its been like that for a long time including with KitKat.
I am rooted and use a number of app beta versions including Nova Launcher, GMD Gesture Control and GMD Auto Hide Software keys, Viper4Android and they all worked before and after the OS update. That is a little surprising as previous Lollipop 5.0.x updates had broken more apps when they were first released. For the first time in a long time MX Player Pro still worked after an OS upgrade.
This was what the Lollipop release should have been. I'm happy especially as my Nexus 5 is as reliable as it was with KitKat.
That's great. Smooth
My 5.02 Nexus got an OTA to 5.1 last night (I'm in the UK). Everything seems fine and I am really happy that I have a tablet that is still supported.
Alan
Is anyone getting a screen freeze? Basically the screen just freezes but the unit seems OK ie it's not a system crash. It needs resetting to work again.
Sent from my Nexus 10 using XDA Free mobile app
Warren_Orange said:
Is anyone getting a screen freeze? Basically the screen just freezes but the unit seems OK ie it's not a system crash. It needs resetting to work again.
Click to expand...
Click to collapse
Sometimes, but always related with Chrome playing videos.
Hi.
I have narrowed it down to when i bring up google search with the swipe up gesture. Once on google search the screen becomes unresponsive. But a can reboot by pressing the power button and choosing 'reboot now'. I may try and reinstall it.
This only started happening with 5.1.
Sent from my Nexus 10 using XDA Free mobile app
Warren_Orange said:
I have narrowed it down to when i bring up google search with the swipe up gesture.
Click to expand...
Click to collapse
In my case I have that feature replaced by a more useful one: a handy launcher:
https://play.google.com/store/apps/...store&pcampaignid=APPU_1_cw0YVbWgJ8XTU_77gYgP
It never freezes.
Halp!
I'm losing my mind trying to figure out the issue here. SMS works fine. Hangouts will only notify of a newly received message if you open Hangouts and are on the conversations list screen (main screen). If you are in a conversation it won't even update of the newly received message until you back back to the main conversations list screen. Doesn't matter if it's on WiFi or mobile data. This is a brand new phone that I bought about a week ago and for the record I'm using the same phone I bought a month ago from the same seller on the same firmware. The only difference is that mine is rooted and I've frozen or uninstalled most all of the bloatware and VZW bullcrap. Otherwise they're identical and one has what seems like an app bug but the other one does not.
I've tried numerous things before posting here (to include lots of searches that only seem to turn up similar issues for those who updated to Lollipop) including uninstalling Hangouts updates as well as Google+ updates as per one thread I saw. Neither had any affect on the issue. I went into the user's Google account to see if any other devices were signed in currently and it doesn't appear to be the issue.
My next step is to root and see if freezing the same apps corrects but where it sits right now would make a warranty exchange through the seller a little bit easier I would imagine.
I'm not really sure what else to try short of accepting the OTA update (Lollipop) which will w/o a doubt introduce more problems than it fixes based on what I've read. Not only that but my LG G3 is functioning just fine on 4.4.2 so I see no reason why the same device shouldn't perform the same on the same firmware version. Makes no sense.
Can someone help me out here?
Thanks!
Hey there XDA community and Pocophone users and owners. I have recently encountered a problem with Snapchat on my phone which locks my account due to the reason of "3rd party applications". This has started occurring on the 17th February. Since then, it has been occurring everyday, causing it to increase in duration each time and this has been quite a frustrating experience. I am running MIUI Stable 10.2.2.0 Global with stock kernel. My phone is rooted with Magisk 18.1 and passes the safetynet test. I am also using the stock Snapchat Alpha app. I have never encountered this problem before, but now that the problems have arise, it has caused as such. I have tried using magisk hide to no avail as the symptoms continue to persist. My suspection is that it is either the MIUI camera port or the Google Camera by San1ty. I also set the lib for the Google Camera to Xlib V2 if that is relevant. My reason for suspection is because the problems I had encountered came soon after I had installed both these apps. After my Snapchat account was locked again, I have since removed both of these applications from my phone in order to see if they were the cause of the problem. I will be checking tonight if my account will still get locked after doing this. I just ask for you fellow Pocophone owners and Snapchat users, have you ever had this problem? And if so, how were you able to fix it?
This happened to me too right now it's the second lock (24 hours) so somebody would better search for a fix. I think something related to magisk triggers the snapchat. Also I am using a J5 2017 (prometheus lite rom ).
i think because root
iMystic said:
Hey there XDA community and Pocophone users and owners. I have recently encountered a problem with Snapchat on my phone which locks my account due to the reason of "3rd party applications". This has started occurring on the 17th February. Since then, it has been occurring everyday, causing it to increase in duration each time and this has been quite a frustrating experience. I am running MIUI Stable 10.2.2.0 Global with stock kernel. My phone is rooted with Magisk 18.1 and passes the safetynet test. I am also using the stock Snapchat Alpha app. I have never encountered this problem before, but now that the problems have arise, it has caused as such. I have tried using magisk hide to no avail as the symptoms continue to persist. My suspection is that it is either the MIUI camera port or the Google Camera by San1ty. I also set the lib for the Google Camera to Xlib V2 if that is relevant. My reason for suspection is because the problems I had encountered came soon after I had installed both these apps. After my Snapchat account was locked again, I have since removed both of these applications from my phone in order to see if they were the cause of the problem. I will be checking tonight if my account will still get locked after doing this. I just ask for you fellow Pocophone owners and Snapchat users, have you ever had this problem? And if so, how were you able to fix it?
Click to expand...
Click to collapse
Hey Mate, is there a way you can tell em where did you get the SnapChat Alpha app that is compatible with Android 9 and is it nessesary to root the phone as well?
jonas.anderssen said:
Hey Mate, is there a way you can tell em where did you get the SnapChat Alpha app that is compatible with Android 9 and is it nessesary to root the phone as well?
Click to expand...
Click to collapse
Hey man sorry I don't really understand what you said b it you if have this problem with Snapchat just install Magisk beta 19.0. this will solve your problems if you are getting banned
Well i want to use thr Snapchat ++ or Alpha that allows you to create fake stories and atuff on my android 9. So can you tell.me what i need to do in order to have that Snapchat feature or App running on my Android?
Do i need to do something specifically?
Thank you