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?
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!
yep, I have the same issue.
If there is any way to create an error log please let me know and I'll post it here.
same
Same annoying thing with me. Any help?
Donated version, xposed mode..
Hi oasisfeng,
Is it possible to use wake-up cut-off without root but with Xposed in Android 6.0?
My company use airwatch for mail exchange which require non-root devices. However, I can install Xposed framework via customer recovery. In early versions of greenify, in my old phone, with Xposed but without root, wake-up cut-off feature works just fine for me. Could you please consider to bring this wonderful feature back to Xposed? Thanks.
Best Regards,
Update:
Find a alternative solution to control app auto run: Xposed + Greenify + Receiver Stop
Thanks for all the great tools and XDA forum
Hello, has someone install the xposed Framework and get work? I install the xposed v81 sdk23 arm64 on twrp, everything works fine. On xposed Installer, is green and active. But when I start gravitybox it doesn't work.
I successfully flashed the framework, installed the Xposed app, and downloaded some modules on the latest ROM (20160419). None of the modules I've tried activate on reboot or work. I didn't expect modules like GravityBox to work since although the P9000 ROM is close to AOSP it actually has quite a few modifications. However, I was surprised that modules modifying apps such as Greenify or Amplify don't work, nor do relatively simple modules such as double tap to sleep. Hopefully we'll be able to use Xposed soon because the latest ROM update is another step closer to this phone realising its potential.
I think Elephone need to release source in order for full xposed compatibility to be realized ?
I am happy the rom with the phone has a bootmanager ability and together with Adaway + network speed app.. not missing xposed too badly at all!
Already tried to get the kernel source but they don't want to share it. See elephonemobile . eu/t/kernel-mt6755-kernel-source-files/27
new7 said:
Already tried to get the kernel source but they don't want to share it. See elephonemobile . eu/t/kernel-mt6755-kernel-source-files/27
Click to expand...
Click to collapse
Please join the joint action to pressure Elephone to release sources: elephonemobile . eu/t/joint-action-to-get-elephone-to-release-sources/96
Quoted here for convenience:
-----
Hi, I'm proposing a template e-mail to write to Elephone to request the release of sources necessary to further develop the phone and fix issues without having to wait for their internal developers to do so.
Please send an e-mail to [email protected] and [email protected], hopefully with enough pressure, they will eventually release some sources.
E-mail template:
Subject: Please release Elephone P9000 sources
Hello, I own a Elephone P9000 phone and I am having issues with the phone, but I would also like to customize it to my needs. There is people willing to work on improving this phone, which will also boost this device reviews and general acceptance. I strongly believe this phone's hardware is amazing, but there is a lot to improve on the software side.
To be able to do this, developers need the kernel source code (and any other source code that is part of the official ROM that you can provide). The release of these sources could determine the level of success of this phone, so I hope you consider releasing the sources soon.
Thank you.
I just sent my e-mail. Please send yours soon.
Click to expand...
Click to collapse
-----
greenphone6743 said:
I think Elephone need to release source in order for full xposed compatibility to be realized ?
I am happy the rom with the phone has a bootmanager ability and together with Adaway + network speed app.. not missing xposed too badly at all!
Click to expand...
Click to collapse
Xposed is needed for Xprivacy, with Xprivacy , you have full control over what apps may know and may not know.
for instance... Facebook thinks I'm living in Austria, and my phone number is 111111111111
many apps want to know you'r messages, mails, contacts etc.... with Xprivacy you can prevent that :good:
but... only works with Xposed
---------- Post added at 03:08 PM ---------- Previous post was at 03:04 PM ----------
I have installed framework : http://forum.xda-developers.com/showthread.php?t=3034811
also flashed with TWRP the framework to ARM64 version 86 http://dl-xda.xposed.info/framework/sdk23/arm64/
In Exposed framework it is green and says Xposed framework version 86 is active
Greenify and Xprivacy are recognized and selected, but when i want to use Xprivacy, it keeps complaining that it is not selected in XPosed...
Greenify, if i use features that only work with Xposed, it also says that it is not activated in Xposed. but it is...
Xposed is allowed by my SuperSU version 2.77
I don't want to use this phone before i get Xprivacy up and running ( i'm keen on PRIVACY )
but as i am reading here.. it has to do with Elephone ?
dinny said:
Xposed is needed for Xprivacy, with Xprivacy , you have full control over what apps may know and may not know.
for instance... Facebook thinks I'm living in Austria, and my phone number is 111111111111
many apps want to know you'r messages, mails, contacts etc.... with Xprivacy you can prevent that :good:
but... only works with Xposed
---------- Post added at 03:08 PM ---------- Previous post was at 03:04 PM ----------
I have installed framework : http://forum.xda-developers.com/showthread.php?t=3034811
also flashed with TWRP the framework to ARM64 version 86 http://dl-xda.xposed.info/framework/sdk23/arm64/
In Exposed framework it is green and says Xposed framework version 86 is active
Greenify and Xprivacy are recognized and selected, but when i want to use Xprivacy, it keeps complaining that it is not selected in XPosed...
Greenify, if i use features that only work with Xposed, it also says that it is not activated in Xposed. but it is...
Xposed is allowed by my SuperSU version 2.77
I don't want to use this phone before i get Xprivacy up and running ( i'm keen on PRIVACY )
but as i am reading here.. it has to do with Elephone ?
Click to expand...
Click to collapse
Flash GrorkMod.
Jonny said:
Flash GrorkMod.
Click to expand...
Click to collapse
thanks for the tip : http://forum.xda-developers.com/ele.../mod-grorkmod-eragon-aerom-v0-5-beta-t3395667
:good:
i use systemless root and xposed with magisk - works fine and love it - http://forum.xda-developers.com/xposed/unofficial-systemless-xposed-t3388268
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...