Related
Hi, after I rooted my Oneplus X and installed all necessary features like Xposed installer etc I cant get Greenify (donation package) to work, specifically the GCM Push notifications. It gives me an error that the ROM is incompatible. Is there any way for me to fix this?
Thanks!
Same here.
Haven't seen a fix yet...
Maybe it'll be OK on CM12.1 builds once they're available?
Hey guys, I installed CM12.1 on my Redmi Note 2. Everythings working fine, a big compliment to the devs. Still I couldn't find a working Xposed Framework. I flashed the framework in twrp version 2.xxx (don't remember thr exact version, I am now writting from ms second device and am not a home). When I open the xposed app, it says that no framework is installed. Can anyone share with me a working xposed app installer and a working xposed framework? Thanks a lot!!!
10.11.2019 new beta 4.7.5 released on Play Store.
See change log on Play Store
https://play.google.com/store/apps/details?id=com.oasisfeng.greenify
NOTE: YOU MUST REGISTER FOR GREENIFY BETA to install the Beta versions. See the Greenify Play Store page for the link.
Older versions released (a few may not be listed here):
_____
02.24.2019 - beta 4.6.3
02.17.2019 - beta 4.6
10.21.2018 - beta 4.5.1.0
10.20.2018 - beta 4.5.0.0
09.20.2018 - beta 4.3.3.0
09.07.2018 - beta 4.3.2.0
09.06.2018 - beta 4.3.0.0 (reported to crash on some devices - suggest not using this version)
08.06.2018 - beta 4.2.0.0
07.02.2018 - beta 4.1.0.0
06.07.2018 - beta 4.0.1
05.09.2018 - beta 3.9.9.1
02.01.2018 - beta 3.9.5
01.24.2018 - beta 3.9.3
12.30.2017 - beta 3.9.1
12.22.2017 - beta 3.9.0
12.02.2017 - beta 3.8.9
12.01.2017 - beta 3.8.8
11.30.2017 - beta 3.8.7
11.14.2017 - beta 3.8.5
10.30.2017 - beta 3.8
10.10.2017 - beta 3.7.1
09.30.2017 - beta build 3.7
08.22.2017 - beta build 3.6.2
08.12.2017 - beta build 3.6.1
07.01.2017 - beta build 3.5.4
06.30.2017 - beta build 3.5.3
06.08.2017 - beta build 3.5.2
06.04.2017 - beta build 3.5.1
05.13.2017 - beta build 3.4.2
04.30.2017 - beta build 3.4
03.31.2017 - beta build 3.3
02.28.2017 - beta build 3.2.2
02/16/2017 - new build 3.2.1
02/12/2017 - new build 3.2.0 released on Play Store.
_____
[BETA] Greenify 3.1.2 build 1, 1/26/2017 is on the Play Store for beta testing enrollees:
https://play.google.com/store/apps/details?id=com.oasisfeng.greenify
Anyone tried it yet? Please post feedback here if you do. Thanks!
This new Greenify version uses Prescription. Read more here:
https://github.com/greenify/greenify.github.io/blob/master/README.md
From the Play Store listing:
"What's New
NEW: "Prescriptions (beta)", the community-driven precisely targeted blocking rules. (Learn more: https://github.com/greenify/greenify.github.io)
NEW: App shortcuts for Android 7.1.
Improved the support for privileged working mode (ROM-integrated).
Wake-up monitor and cut-off now works on Android 7.x in root mode.
Fixed wake-up monitor in root mode on the first installation.
Fixed root privilege check on some devices."
I have installed subject version Greenify on my system-less rooted 6.0.1 with Xposed. I have not seen any signs of the Prescription enhancement which is supposed to be in this version. I have seen Greenify activity logged in SuperSU 2.79-SR2 log. Everything seems to be working normally as before so far.
Thanks for adding the shortcuts in Android 7
:good: Hello Everyone !!!!
On my zopo zp999 greenify 3.1 buil 1 works well with module xposed installed!!!!
On huawei g610-u20 greenify 3.1 build 1 with module xposed installed refuse to install......error.......!!!!
Anyone knowing how to solve this problem !?!? super thks and have a good day everyone !!!!!!
greenify 3.0 build5 working good on huawei g610-u20 !!!!!!!!
Please provide some relevant details like OS version and Xposed version, etc.
star trek said:
:good: Hello Everyone !!!!
On my zopo zp999 greenify 3.1 buil 1 works well with module xposed installed!!!!
On huawei g610-u20 greenify 3.1 build 1 with module xposed installed refuse to install......error.......!!!!
Anyone knowing how to solve this problem !?!? super thks and have a good day everyone !!!!!!
greenify 3.0 build5 working good on huawei g610-u20 !!!!!!!!
Click to expand...
Click to collapse
I just installed beta Greenify version 3.1.1 build 1 from the Play Store. Working fine and no clue what changed . The people running Nougat will see the changes.
Thread title has been updated.
So just to clarify, prescriptions don't work past lollipop?
Where did that come from? I think Prescriptions applies to Nougat currently.
jetknife said:
So just to clarify, prescriptions don't work past lollipop?
Click to expand...
Click to collapse
Now serving version 3.1.2 b1:
NEW: v3.1.2: Prescription import is now fixed
There is an issue when want to read the guides how to configure system via USB-DEBUG for some features to work on non-root Marshmallow (e.g. wake-up tracing or doze on the go)
There's no link passed to external applications (browsers).
Please provide the link to these guides here if you can.
Sent from my SM-A510F using Tapatalk
Here :
https://greenify.uservoice.com/knowledgebase/articles/all
ioy said:
There is an issue when want to read the guides how to configure system via USB-DEBUG for some features to work on non-root Marshmallow.
There's no link passed to external applications (browsers).
Please provide the link to these guides here if you can.
Sent from my SM-A510F using Tapatalk
Click to expand...
Click to collapse
It's my first time using Greenify on Nougat.
I installed the latest beta and granted WRITE _SECURE_SETTINGS, and DUMP, but I cannot enable Doze on the Go.
It says it is not compatible with my ROM or device, is it normal?
On Marshmallow, I could eanble Doze on the go with DUMP permission granted..
My device is Sony Xperia Z5C.
I can't read Chinese, but my "Doze on the Go" switch is also grayed out and says "Already enabled in Xposed features". Do you have Xposed installed like I do and what do those Chinese characters say ?
kulguy said:
It's my first time using Greenify on Nougat.
I installed the latest beta and granted WRITE _SECURE_SETTINGS, and DUMP, but I cannot enable Doze on the Go.
It says it is not compatible with my ROM or device, is it normal?
On Marshmallow, I could eanble Doze on the go with DUMP permission granted..
My device is Sony Xperia Z5C.
Click to expand...
Click to collapse
divineBliss said:
I can't read Chinese, but my "Doze on the Go" switch is also grayed out and says "Already enabled in Xposed features". Do you have Xposed installed like I do and what do those Chinese characters say ?
Click to expand...
Click to collapse
That says "My device or ROM is incompatible" (I guess, because parts of the phrase is cut out).
I don't have Xposed installed, and my device is not rooted. Does Doze on the Go on Nougat need Xposed?
p.s. It is not Chinese, but Korean
kulguy said:
That says "My device or ROM is incompatible" (I guess, because parts of the phrase is cut out).
I don't have Xposed installed, and my device is not rooted. Does Doze on the Go on Nougat need Xposed?
p.s. It is not Chinese, but Korean
Click to expand...
Click to collapse
If you are using the stable version, you will not be able to enable Doze on the Go. I also had it. I think that the stable version is not fully compatible with Nougat. In the current beta (3.1.2 build1), it works and you can enable the option.
---------- Post added at 04:36 PM ---------- Previous post was at 04:33 PM ----------
divineBliss said:
I can't read Chinese, but my "Doze on the Go" switch is also grayed out and says "Already enabled in Xposed features". Do you have Xposed installed like I do and what do those Chinese characters say ?
Click to expand...
Click to collapse
You can enable it in only one place. If you have enabled it in Xposed features, the other option will be greyed out. The Xposed option works better. Unfortunately, Nougat is yet to have Xposed.
tnsmani said:
If you are using the stable version, you will not be able to enable Doze on the Go. I also had it. I think that the stable version is not fully compatible with Nougat. In the current beta (3.1.2 build1), it works and you can enable the option.
Click to expand...
Click to collapse
I'm using the current beta, too. But I cannot enable Doze on the Go... Did you root your device?
I didn't, and just granted DUMP and WRITE _SECURE_SETTINGS permission through adb...
What I want to know is if Doze on the Go works on non rooted Nougat device...
I don't have N and don't know if DOTG works with N.
kulguy said:
I'm using the current beta, too. But I cannot enable Doze on the Go... Did you root your device?
I didn't, and just granted DUMP and WRITE _SECURE_SETTINGS permission through adb...
What I want to know is if Doze on the Go works on non rooted Nougat device...
Click to expand...
Click to collapse
I am rooted and Doze on the Go works. I don't know about unrooted.
Warning
This module fixes a problem on OOS 4.5 devices that crash when Xposed 87.3, 88 or 88.1 is active.
The root cause of the problem has been fixed in Xposed 88.2, so you do not need this module with Xposed 88.2 or later.
If you are experiencing soft-reboots and/or crashes without Xposed installed, this module cannot help you.
Requirements
An OOS Device.running Nougat
Xposed (Official @rovo89 or systemless Magisk)
Description
If you're trying to run Xposed on OOS Devices, you may notice that every time your phone is left charging for a while, Android crashes with:
Code:
OPConfig:ConfigProvider: Module:BackgroundOptConfig
BackgroundDexOptService: blacklist add : com.chinamworld.main
BackgroundDexOptService: blacklist add : cn.kidyn.qdmedical160
BackgroundDexOptService: blacklist add : com.paic.zhifu.wallet.activity
BackgroundDexOptService: blacklist add : com.pingan.paces.ccms
BackgroundDexOptService: blacklist add : cn.damai
BackgroundDexOptService: blacklist add : com.baidu.carlife
BackgroundDexOptService: [OnlineConfig] BackgroundOpt updated complete
art : No implementation found for java.lang.String dalvik.system.DexFile.getOatFileCompilerFilter(java.lang.String, java.lang.String) (tried Java_dalvik_system_DexFile_getOatFileCompilerFilter and Java_dalvik_system_DexFile_getOatFileCompilerFilter__Ljava_lang_String_2Ljava_lang_String_2)
AndroidRuntime: *** FATAL EXCEPTION IN SYSTEM PROCESS: BackgroundDexOptService_IdleOptimization
AndroidRuntime: java.lang.UnsatisfiedLinkError: No implementation found for java.lang.String dalvik.system.DexFile.getOatFileCompilerFilter(java.lang.String, java.lang.String) (tried Java_dalvik_system_DexFile_getOatFileCompilerFilter and Java_dalvik_system_DexFile_getOatFileCompilerFilter__Ljava_lang_String_2Ljava_lang_String_2)
AndroidRuntime: at dalvik.system.DexFile.getOatFileCompilerFilter(Native Method)
AndroidRuntime: at com.android.server.pm.PackageDexOptimizer.getOatFileCompilerFilter(PackageDexOptimizer.java:167)
AndroidRuntime: at com.android.server.pm.PackageManagerService.getOatFileCompilerFilter(PackageManagerService.java:19879)
AndroidRuntime: at com.android.server.pm.BackgroundDexOptService$3.run(BackgroundDexOptService.java:373)
DownloadManager: Removed 0 stale downloads
MDM_DropBox: record:system_server_crash
OSTracker: OS Event: system_server_crash
Then this module is for you.
Install, activate, reboot and crashes be gone.
This module has no UI.
Technical explanation
For some reason OnePlus has patched the Background Dex Optimization service. I think it's related to the aggressive optimization OOS 4.5 pushes (it uses the "speed" compiler filter everywhere) and also implements some filtering of some apps (see the blacklist add lines in the backtrace).
Note that the Background Dex Optimizer as shipped by OOS will not obey the pm.dexopt.bg-dexopt property and will always use "speed" irrespective of the pm.dexopt.bg-dexopt setting. Gah...
In their patching, OnePlus made the com.android.server.pm.PackageDexOptimizer.getOatFileCompilerFilter() framework function call the dalvik.system.DexFile.getOatFileCompilerFilter() native function.
dalvik.system.DexFile.getOatFileCompilerFilter() is implemented in OOS by /system/lib64/libart.so.
And Xposed replaces /system/lib64/libart.so with its own version, which does not contain dalvik.system.DexFile.getOatFileCompilerFilter().
When the OOS phone is left charging and reaches 100% battery, a timer starts. 1h after reaching 100% battery, the Background Dex Optimization runs, and promptly crashes. Since this is in the Android system, the whole phone soft-reboots.
The module works by hooking com.android.server.pm.PackageDexOptimizer.getOatFileCompilerFilter() and having it return null instead of calling the native method dalvik.system.DexFile.getOatFileCompilerFilter(). That's what the native method returns anyways, so no functionality should be lost.
Device Status
Working and tested on:
OnePlus 5 running OOS 4.5.12, Magisk 14.2 and Xposed 88.0.
Changelog
Release 0.1 on October 11, 2017
Initial release.
Download
httphttp://dl-xda.xposed.info/modules/com.fifsource.android.oosbackgroupdexcompilationfix_v1_830eb4.apk (on Xposed Module Repository)
XDA:DevDB Information
OOS Background DEX Optimization Fix, Xposed for all devices (see above for details)
Contributors
Fif_
Xposed Package Name:
Version Information
Status: Beta
Current Beta Version: 0.1
Beta Release Date: 2016-10-11
Created 2017-10-12
Last Updated 2017-10-12
Attention beta testers:
Please let your device run on power overnight and send me the Xposed log file.
You should see many lines with the "OOSDEX" prefix.
Trying it now, thanks very much!
Does this effect mm at all or simply n?
I only found this problem on OOS 4.5.x, which is Nougat. The package won't install on anything but N or above. Did you experience a similar crash on a MM OOS ROM?
Thank you!!! Really hope this works! Noticed this when my alarm didn't go off 2 days ago.. Last night I woke up a few times and when i looked at my phone it asked asked my code. This happened 3 times , so at least 3 reboots while on charger.
My 3T (running OB 15) charged just fine without crashing last night.
I guess it's a good thing that I'm sticking with it for now. OxygenOS open beta roms are about as close to perfect as it gets when you add magisk, xposed, and substratum. I love custom roms as much as anyone else, but OOS is hands down the best stock ROM. Remaining close to AOSP gives it the versatility that other stock roms lack.
HampTheToker said:
My 3T (running OB 15) charged just fine without crashing last night.
I guess it's a good thing that I'm sticking with it for now. OxygenOS open beta roms are about as close to perfect as it gets when you add magisk, xposed, and substratum. I love custom roms as much as anyone else, but OOS is hands down the best stock ROM. Remaining close to AOSP gives it the versatility that other stock roms lack.
Click to expand...
Click to collapse
I'm happy to hear that your phone didn't crash overnight. Did you have the module enabled?
If so, can you share your Xposed log from that night? Right now the module has lots of logging, which I will pare down later, but I'd like to check everything is working fine.
@Fif_ does your module work on v88.1?
Sent from my ONEPLUS A5000 using Tapatalk
Haven't tried, waiting for the systemless update for 88.1.
Given that the module is very simple, if Xposed 88.1 works for you, the module should work. Please report back and share your Xposed log in any case. Thanks.
I added a technical explanation to the project description, in case anyone's interested in understanding what happens.
Still no reports of success of failures, with 219 downloads so far. It's working fine for everyone I guess, or I'd hear more complaints...
Hi Fif_,
Thanks for the fix. Have you reported this issue to rovo? Seems like an xposed framework bug to me. Shouldn't it be fix in the framework itself? But anyway good job!
Working great so far on my OnePlus 5, OOS 4.5.12, Magisk 14.2, and official Xposed 88.1. I also attached my xposed log for you since you requested some.
aeonix_05 said:
Hi Fif_,
Thanks for the fix. Have you reported this issue to rovo? Seems like an xposed framework bug to me. Shouldn't it be fix in the framework itself? But anyway good job!
Click to expand...
Click to collapse
I agree, this seems like something that in the end should be fixed within the framework itself.
Fif_ said:
I'm happy to hear that your phone didn't crash overnight. Did you have the module enabled?
If so, can you share your Xposed log from that night? Right now the module has lots of logging, which I will pare down later, but I'd like to check everything is working fine.
Click to expand...
Click to collapse
No, it wasn't installed. I'm on open beta, so I don't think this bug applies since my 3T didn't experience a crash as far as I can tell. I'll give my phone a couple more battery cycles and let you know if this bug affects us 3/3T open beta users.
BatedUrGonnaDie said:
Working great so far on my OnePlus 5, OOS 4.5.12, Magisk 14.2, and official Xposed 88.1. I also attached my xposed log for you since you requested some.
I agree, this seems like something that in the end should be fixed within the framework itself.
Click to expand...
Click to collapse
Thanks for the log. Everything happened as I expected on your phone.
I'm not sure if this is an Xposed framework issue. Have you read the technical explanation?
I see the situation this way: @rovo89 publishes the official Xposed framework based upon AOSP sources. Then third parties publish modified Xposed frameworks for specific ROMs. There's Wanam Xposed for Samsung phones. There another one for MIUI. There are surely others.
For us, OOS users, a simple mod using the framework itself is sufficient to make the official AOSP-based Xposed work on OOS. I think this is better than having a forked OOS-specific Xposed framework.
Fif_ said:
Thanks for the log. Everything happened as I expected on your phone.
I'm not sure if this is an Xposed framework issue. Have you read the technical explanation?
I see the situation this way: @rovo89 publishes the official Xposed framework based upon AOSP sources. Then third parties publish modified Xposed frameworks for specific ROMs. There's Wanam Xposed for Samsung phones. There another one for MIUI. There are surely others.
For us, OOS users, a simple mod using the framework itself is sufficient to make the official AOSP-based Xposed work on OOS. I think this is better than having a forked OOS-specific Xposed framework.
Click to expand...
Click to collapse
Hmm, you do make a good point, but with the current release rovo is working on samsung and miui compatibility (ex: v88.1). It seems like he is trying to make it as universal as possible instead of having a different version for each phone.
i have the same soft reboot issue. it happens only when the phone is on the charger for a longer time and in flight mode. i'll try your module. thanks!
Working great, no reboots all night. Time for a build without all the debug code in the logs
Working great! Thanks for the fix :good: Slow testing of course because of waiting for full charge and then next another hour of waiting for a crash. Which did not occur anymore, so it works! :good:
vincentkoevoets said:
Working great! Thanks for the fix :good: Slow testing of course because of waiting for full charge and then next another hour of waiting for a crash. Which did not occur anymore, so it works! :good:
Click to expand...
Click to collapse
Yeah it was a long debugging session...
Hello guys.
This is details of my phone.
1. Lenovo k8 plus
2. Twrp is not install properly but also i root my phone and it say orange state.
3.i download modified xposed framework by topjohnwho and rovo89 module. I download that in magisk.
4. I want to download xposed 90-beta3 version.
5. I download the modified xposed installer .
6.after complete this steps its say only and only one thing please active xposed framework.
7.when I am click on install it gives me error resources is busy.
8.and if I use busybox also it say xposed.prob is already available or xposed.prob I/O error.
9.My phone have Android 8.0.0 Oreo API
10.pocesser arm64
I did already see xda developer post related my problem like remove disabled from /data/data... Etc.
Or ☑ disable resources hooks etc..
But that all kind of stuff didn't work.
AFAIK for devices runnning Android 8 and higher you use EdXposed framework and/or LSPosed framework instead of XPosed framework
jwoegerbauer said:
AFAIK for devices runnning Android 8 and higher you use EdXposed framework and/or LSPosed framework instead of XPosed framework
Click to expand...
Click to collapse
jwoegerbauer said:
AFAIK for devices runnning Android 8 and higher you use EdXposed framework and/or LSPosed framework instead of XPosed framework
Click to expand...
Click to collapse
Thank you for Reply .
Yes you are right and i also try Edxposed Framework and also its works.but i want use use sms toolkit for send anyone flash sms so that tool didn't work on EdXposed framework .what can i do for send flash sms using sms toolkit made by hackistan.Any other way to send Flash sms ,SMS DOS , or etc thing like this. without Xposed Framework.then i dont need that. and ya i also Search on internet that how to send flash sms without xposed framwork it gives not any information related this . so what can i do ????
can i add /system/framework/telephony-common.odex in android 4 to android 8 ??