As the post says, any luck on getting either working? I wish to flash Xposed but scared of getting bootloops.
With regards to Gravity Box, the latest current version does not even work with 5.1 without causing bootloops.
kanej2006 said:
As the post says, any luck on getting either working? I wish to flash Xposed but scared of getting bootloops.
With regards to Gravity Box, the latest current version does not even work with 5.1 without causing bootloops.
Click to expand...
Click to collapse
If you are on the Sony LP, you must wipe the ART cache on EVERY boot (Dalvik cache) since it will bootloop otherwise.
On other ROMs such as Resurrection Remix or BlissPop 2.3 based on 5.0.2, Xposed works well. GravityBox works too but is not that necessary on such a customizable ROM.
If you want Xposed without inconvenience, flash a different ROM than the Sony one and if you can live without GravityBox, I would recommend you to follow the 5.1 route and try the latest Cyanide ROM, which is excellent. Xposed Super-Alpha works but not GravityBox (which isn't necessary due to great customization options in the ROM).
Read here:
http://forum.xda-developers.com/xperia-z-ultra/general/xposed-lollipop-14-5-0-242-bootloop-t3086467
I got gravitybox and several other modules running on lollipop with locked BL.
EDIT: Forgot to add, i lost recent key after installing gravity box. I use gravity box to reduce the height of navigation bar. I mean the key is ther and i can use it, just the square icon isn't there for some reason. hasn't really tried anyhting to get it back, just so you know, it doesn't bother me much.,
^ Thank you so much E90 Commie & jassalmithu for your response, both of which have been very useful...
I am indeed currently using the latest stock Sony 5.02 rom. I've not yet tried any other 5.02 rom such as Resurrection or Blisspop.
The main thing for me is battery life. I'm not sure how the above roms are for battery life but currently, the stock Sony rom provides excellent battery, even better than Kitkat. I got almost 6 hours of on screen time over a 2 day period!
For the moment, I'll refer to the link provided by jassalmithu and follow the instructions on getting Xposed running without having to wipe the dalvic cache on every boot.
Thanks so much once again.
Good news! After having followed the instructions, both Xposed & Gravity box are fully working without any boot loops or crashes/force restarts.
This was the link I followed which was posted by jassalmithu.
http://forum.xda-developers.com/z3-compact/general/wip-debloat-lp-690-correct-functioning-t3076161
The only issue is that you have to format your data and re-install Android 5.02 for the above to work.
Other than that, I confirm it's working 100% should you follow the already easy to follow instructions!
Hi all,
I did not know where to post this, but I think "LG General" fits quite nicely.
After @rovo89 announced the availability of Xposed for Lollipop in February this year a lot of us where desparatly waiting for one of the most essential modules to work with it as well: Xprivacy!
Yesterday the Dutch developer Marcel Bokhorst finally released a Beta of Xprivacy which runs really good on Lollipop ROMs.
Although most information until now state a compatibility with Android 5.1.x I decided to give it a try on my D802 with stock 30b (5.0.2) and latest Dorimanx kernel.
I followed this thread to install Xposed and manually added the Xprivacy module right after.
Beside the usual hiccups with Xposed on the G2 in general (LG Smart Cover and LG Weather FC) there are no errors at all. All works as expected on my device. I am sporting a D802 with stock 30b, Dorimanx kernel V2.4 - 3.4.107, XposedInstaller 3.0 alpha2, Xposed sdk21 arm 20150430, and Xprivacy 3.6.16. This combo works, but you'll need a way to get rid of LG Smart Cover before installing Xposed or you'll be stuck in a FC-loop making your device rather unusable. I had to learn the hard way and had to remove the apk from within TWRP. So be warned! I cannot say, if this works on any other combinations of devices, ROMs or kernels. Try at your own risk!
Finally there is a safe way to run Lollipop on the LG G2!
Thanks to all the developers involved in making this happen!
Regards,
Tom
Hi
I`m on Resurrection remix ROM V 5.7.4
Rooted Android 6.0.1 , xposed is installed and working properly
I have used greenify 2.8.1 with donation package without any problem
But after upgrading to last version "V3 build 5" wake up path icon hasn't been available anymore
I returned to earlier versions but the problem still exists .
Unfortunately i can't post screenshots from my device i should have at least 10 posts due to xda forums rules
Any solution ?
Have you enabled Extended Wakeup from Greenify Settings?
MihaiSG said:
Have you enabled Extended Wakeup from Greenify Settings?
Click to expand...
Click to collapse
That option is not there anymore I don't know how to retrieve it back
Try to find on Xposed Settings from Greenify or Troubleshoting.
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...
Thread Closed
Thread Closed
@Francesco Franz
Tested it now over a few days, works like a charm! Thanks for porting it!
Here are some screenshots of it working and some screenshot on how to change the language on first boot!
Working: mega(.)nz/#!nbwjnBxZ!sM7FOlH_Zf5KSmOqblZb-wSvxuQ0UFqoCNOXeiF5Gec
Change Language: mega(.)nz/#!DPgESACK!jvpINpm64EA72edk_g8UHwnJu-M7mUxya8w12JIwrDQ
Greetings from the heart of Switzerland!
Problem found
I found a problem with this mod for XT1771. Let me first state that most rooted apps seem to work with this mod. However, when installing Rom Manager, I received a notification that it had no superuser access. Then, after installing Xposed framework, my Phone hung at its start screen, and now it won't boot anymore.
DON'T INSTALL XPOSED FRAMEWORK USING THIS MOD!!!
Volkmar73 said:
I found a problem with this mod for XT1771. Let me first state that most rooted apps seem to work with this mod. However, when installing Rom Manager, I received a notification that it had no superuser access. Then, after installing Xposed framework, my Phone hung at its start screen, and now it won't boot anymore.
DON'T INSTALL XPOSED FRAMEWORK USING THIS MOD!!!
Click to expand...
Click to collapse
Let me correct you buddy. Twrp is a custom recovery which allows you to wipe and install certain things.
Such a crap. First you need to know whether Xposed framework working in your device or not. Before giving negative review do some research. I can give you the recovery. Rest of the problems aren't mine and should be resolved by you.
Report *Xposed* related problem in Xposed framework thread not here.
will it work for micromax bharat 5 pro
will it work for micromax bharat 5 pro, which is too mt6737m device with 3gb ram , 32gb rom, 5000mAh , 13+5 mp
Closed by OP request!
Thread re-opened at OP's request.