Well, finally testing out Lollipop. Never tried it bc i use so many Xposed modules but figured I'd give it a whirl. Now, how can I fully maximize Greenify since I can't use Xposed modules, thus not allowing me to enable the experimental features. Can I still Greenify GCM apps and they work properly? Any help is appreciated....
Installed xposed for stock rooted lollipop and fc.
There's a reason Xposed for Lollipop is still in Alpha release status. I would report the issue in the Xposed forum so that the developer is aware. He'll probably want log files to see what the problem is. Or just wait until a stable release is available.
I had the same problem what was the app?
Also i followed this guide and it worked on bliss pop maybe it will work on stock: http://www.phonearena.com/news/How-....0-Lollipop-and-actually-make-it-work_id66065
I think the main thing is to change from enforcing to passive
Hi, before I updated to MM I had more tiles/icons I could use. Now with the new update MM 6.0.1 EMUI 4.0 it's not possible to have more than nine ready-to-use icons. So my question is, given I have root, xposed and phone unlocked, how can I add more icons to the dropdown menu? Any files to edit, or any xposed modules to try ?
I tried GravityBox [MM] but it does not work. Phone is KIW-L24, rooted, xposed and TWRP installed.
Thanks.
PS. I have checked for a while for a solution, but so far no luck.
you will be out of luck to hear this..
unfortunately, you cannot do what you are intending to(as for my knowledge).. feature is burried with lollipop ..
i have surfed over the entire settings and found nothing
Yes, I was afraid I'd not be able to change that, ... too bad such a useful feature gets axed. Is there any custom ROM out there for Honor 5X that can do that, that's close to Huawei's EMUI (I kinda got used to it now) ?
I've checked the custom ROMs sub-forum from time to time, but I'm not sure which to chose. Do you have any suggestions ?
Thanks.
Hello,
As i'm a fan of using Dimple.io (a NFC customisable button sticker), aswell using other NFC compatible devices like my Sony camera. I get annoyed by the sound my phone makes with every NFC tag. On previous Android versions i alsways was able to disable the NFC sound true an Xposed installer bypass. Unfortunatly the current Xposed installer for Nougat has not been stable for me for daily use and i'm looking for other options. I already had found a solution by decompiling the system app NfcNci.apk, and replacing the sound with an silent sound. Unfortunatly the recompiled apk file somehow gets corrupted and i get FC's after rebooting.
Are there any other ways to get this fixed somehow? Been waiting to install Android Nougat on my Oneplus One for this reason only and since i heard there was an Xposed Installer available, i gave it a shot.
I'm on the latest Resurrection Remix rom
Thanks in advance.
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...