Xposed module to fix the bug in some devices that location icon is shown in the status bar even when there is no app requesting location.
The location notification icon in the status bar is designed only to show when an app is accessing the GPS (a.k.a. high powered location); however, this is broken on some devices where the icon is shown all the time, whether or not there is actually an app requesting high powered location. This Xposed module makes sure that the location icon shows up only when it should.
Should work on Android 5.0+.
(As a side benefit, you can check the Xposed log for which packages had accessed or are still accessing high powered location ).
Get it in the Xposed repo:
http://repo.xposed.info/module/com.xinlu.location_icon_fix
Source code URL:
https://github.com/xinluh/Xposed-StickyLocationIconFix
Some technical details of the fix:
The icon change is trigger by an intent from the LocationManagerService, but whether the icon is visible or not is determined by whether any app is currently using the high powered location permission in the AppOps package. I spent a long time tracking down if LocationManagerService is sloppy in forgeting to tell AppOps that a location request is no longer active, but the problem seems to stem from other packages requesting the location permission directly from AppOps without shutting it down properly. So, in essense, whenever the status bar is checking for high powered location requests, there are always active requests in the AppOps package which did not come from LocationManagerService.
The fix, without figuring out where those AppOps requests come from (they seem to come from close source Google services), is to keep track of the intent sent from LocationManagerService without invoking AppOps; to do that, I modified the intent sending code to send also package name and the on/off status. The side effect is that the android.location.HIGH_POWER_REQUEST_CHANGE broadcast is now sent twice, once without and once with the extra information. This side effect can easily be fixed by changing the intent action, but no other packages seem to use it (and it is a system level broadcast, so no user app should be using it).
Excellent.
Thanks a lot.
Ceased working with xPosed 86. Logs forthcoming once ROVO89 tells me what to look for. But I kinda worry this project is abandonware? Can I get a confirm/denial?
Details of why xPosed v86 stops can be found in this info.
rovo89 said:
Finally, a word to all module developers: In v84, I added a warning when a module's APK includes the Xposed API classes instead of just referencing them. I have also sent an email to the developers of all modules I could identify. With v86, I will turn the warning into an error and prevent the module from loading, as it could causes strange issues otherwise. Please update your module as soon as possible.
Click to expand...
Click to collapse
Error log, proving 86 difference has broken module
Code:
07-08 11:13:37.659 I/Xposed ( 383): -----------------
07-08 11:13:37.659 I/Xposed ( 383): Starting Xposed version 86, compiled for SDK 23
07-08 11:13:37.659 I/Xposed ( 383): Device: Nexus 6 (motorola), Android version 6.0.1 (SDK 23)
07-08 11:13:37.659 I/Xposed ( 383): ROM: N6XShamuM v2.2.3 - MOB30M - HeckNoTechnO
07-08 11:13:37.659 I/Xposed ( 383): Build fingerprint: google/shamu/shamu:6.0.1/MOB30M/2862625:user/release-keys
07-08 11:13:37.659 I/Xposed ( 383): Platform: armeabi-v7a, 32-bit binary, system server: yes
07-08 11:13:37.659 I/Xposed ( 383): SELinux enabled: yes, enforcing: no
07-08 11:13:39.979 I/Xposed ( 383): -----------------
07-08 11:13:39.981 I/Xposed ( 383): Added Xposed (/system/framework/XposedBridge.jar) to CLASSPATH
07-08 11:14:11.057 I/Xposed ( 383): Detected ART runtime
07-08 11:14:11.062 I/Xposed ( 383): Found Xposed class 'de/robv/android/xposed/XposedBridge', now initializing
cut
07-08 11:14:36.137 I/Xposed ( 383): Loading modules from /data/app/com.xinlu.location_icon_fix-1/base.apk
07-08 11:14:36.381 E/Xposed ( 383): Cannot load module:
07-08 11:14:36.381 E/Xposed ( 383): The Xposed API classes are compiled into the module's APK.
07-08 11:14:36.381 E/Xposed ( 383): This may cause strange issues and must be fixed by the module developer.
07-08 11:14:36.382 E/Xposed ( 383): For details, see: http://api.xposed.info/using.html
Related
Hi
I buy donate and update phone to Lollipop. And I can not install xposed because I have a lot of bugs. My question is: Can I be notified GCM in frozen applications without Xposed?
UszkiX said:
Hi
I buy donate and update phone to Lollipop. And I can not install xposed because I have a lot of bugs. My question is: Can I be notified GCM in frozen applications without Xposed?
Click to expand...
Click to collapse
No, without Xposed, you can not.
Xposed alpha is compatible with Lollipop 5, not 5.1 or higher. If you have 5, you should be able to install Xposed alpha.
When I install xposed I see "com.android.......
Has been stoped"
And I can not using the phone...
Ya even me also getn bootloops.... Phone-sony Xperia t2 ultra android version-5.0.2
Which version of Xposed are you both trying to install?
You can use Xposed in Lollipop 5.0 and 5.1 but the greenify module will give you a bootloops.
The developer should update the module to make it work.
I trying to flash framework not xposed apk.
UszkiX said:
I trying to flash framework not xposed apk.
Click to expand...
Click to collapse
Then search in Xposed thread.
tnsmani said:
Which version of Xposed are you both trying to install?
Click to expand...
Click to collapse
Latest xposed 20150430
My phne is nt even booting to home screen after flashing the xposed zip
But it works on other phones like z2,z3 having lollipop
pvnsai73 said:
Latest xposed 20150430
My phne is nt even booting to home screen after flashing the xposed zip
But it works on other phones like z2,z3 having lollipop
Click to expand...
Click to collapse
Did you disable all Xposed modules (assuming you were running earlier versions of Xposed) before attempting to install this version?
This version is running without major issues in almost all phones. So may be your phone or OS is causing this. Search in the Xposed thread.
tnsmani said:
Did you disable all Xposed modules (assuming you were running earlier versions of Xposed) before attempting to install this version?
This version is running without major issues in almost all phones. So may be your phone or OS is causing this. Search in the Xposed thread.
Click to expand...
Click to collapse
I did a clean and fresh install of rom..and properly root with r/w and a twrp recovery..but here is my log
05-19 00:01:27.672 I/Xposed ( 994): -----------------
05-19 00:01:27.672 I/Xposed ( 994): Starting Xposed binary version 61, compiled for SDK 21
05-19 00:01:27.672 I/Xposed ( 994): Device: D5322 (Sony), Android version 5.0.2 (SDK 21)
05-19 00:01:27.672 I/Xposed ( 994): ROM: 19.3.A.0.470
05-19 00:01:27.672 I/Xposed ( 994): Build fingerprint: Sony/D5322/D5322:5.0.2/19.3.A.0.470/552693915:user/release-keys
05-19 00:01:27.672 I/Xposed ( 994): Platform: armeabi-v7a, 32-bit binary, system server: yes
05-19 00:01:27.672 I/Xposed ( 994): SELinux enabled: yes, enforcing: yes
05-19 00:01:27.681 I/Xposed ( 994): -----------------
05-19 00:01:27.681 I/Xposed ( 994): Added Xposed (/system/framework/XposedBridge.jar) to CLASSPATH
05-19 00:01:27.785 I/Xposed ( 994): Forcing image recompilation because /data/dalvik-cache/arm/[email protected]@boot.art is not compiled for the current Xposed version
05-19 00:01:55.606 I/Xposed ( 994): Detected ART runtime
05-19 00:01:55.616 I/Xposed ( 994): Found Xposed class de/robv/android/xposed/XposedBridge, now initializing
05-19 00:01:55.689 I/Xposed ( 994): Initializing XposedBridge version 64
05-19 00:01:55.892 E/Xposed ( 994): Cannot load any modules because /data/data/de.robv.android.xposed.installer/conf/modules.list was not found
05-19 00:01:57.206 F/libc ( 1831): Fatal signal 6 (SIGABRT), code -6 in tid 1831 (main)
@pvnsai73,
I think that your problem is here "05-19 00:01:55.892 E/Xposed ( 994): Cannot load any modules because /data/data/de.robv.android.xposed.installer/conf/modules.list was not found"
This has nothing to do with Greenify and you are asking in the wrong place.
Search in the Xposed thread for missing modules list. But I don't think that there is any solution found for this.
UszkiX said:
I trying to flash framework not xposed apk.
Click to expand...
Click to collapse
Have you tried to install the APK than flash the framework?
Battery Shutdown Manager
Download @ Google Play
Do you know that moment when you're on 1% of battery and think "I'll just use my device 20 more seconds then I'll get my charger" - and at exactly that moment it'll switch to 0% and you'll see the threaded "Shutting down" dialog and know it's too late now?
This Xposed module will help by showing you a dialog with a countdown before the actual shutdown, so you'll have time to attach your charger.
The module achieves this by postponing the shutdown for a couple of seconds to give you time to connect the charger.
Please post any kind of feedback or ideas you have regarding this app :fingers-crossed:
I tested the module a lot but can't possibly test it for all those different phones and versions out there.
Thus I will flag it as beta for now so you can provide feedback before I'll release the 1.0 version.
It would be great if some more people could test it. I used the StabilityTest app to quickly drain my battery down to 0%.
Compatibility:
I wrote this module and tested it with AOSP devices as well as on Cyanogenmod.
It should work without any issues on all Nexus and Google Play Edition devices from Android 4.2 to 5.1+.
As almost all Custom ROMs are based on either AOSP or CM they should work without issues, too.
Some vendors might have changed the original code and thus render this module incompatible on their device. Nothing bad will happen when you install it, it just won't work.
Compatible:
Nexus / AOSP / GPE ROMs
Cyanogenmod
Almost all custom ROMs (as they're usually either based on AOSP or CM)
Sony Stock ROMs
Not compatible:
Currently not working for LG Stock ROMs due to internal code changes by LG.
Android devices <4.2. Support for Android 4.0.3+ and 4.1 might be added when I see a greater demand for it.
Installation:
- Download the app
- Activate the module in the Xposed Insaller
- Reboot your device
- Open the app to change it's options to your liking
Bugs/Issues:
If you encounter any bugs just report them here and I'll try to fix them. Always include as much information as possible, including your device model, android version and exact ROM details.
Note that I will most likely need a log to fix the issue, a generic "doesn't work on phone xyz" won't help me fixing the issues.
There are two possibilities to get a log.
Use the Catlog app. In the app press Menu > Record Log before the device shuts down, then attach the logcat to your bugreport.
Alternatively you need to use adb to grab the log.
Unfortunately logging is a bit more complicated for this module as the interesting part happens on shutdown.
The best solution (and what I do personally for debugging this app) is to use ADB over WiFi (e.g. with this app) and grab the log.
Download:
Google Play Store
Xposed Module Repository
Google+:
www.google.com/+thetonyp
Last but not least an obligatory huge thanks to @rovo89 for his amazing Xposed framework!
If you like this module don't forget to press thanks, rate this thread with 5 stars, consider a donation etc. etc.
:fingers-crossed:
I love your icon pack!
Tried it on my cm12.1. No bootloops here. Will edit after full uncharging
EDIT: Turned turning on full brightness, hot spot, gps, flashlight, mobile data, etc... Still 8% to go. Your module and me are waiting eagerly lol
EDIT2: Finally reached 0
And tonyp, I am pleased to say your module works in cm12.1
Suggestion: Make the dialog box closable. So if I am playing a game or writing to a File I can save my progress. Hope you understand.
And I appreciate your idea. Well implemented.
And do you mind sharing that icon pack :hungry:
Samsung galaxy s3 i9300 4.3 mk6 stock rom, bootloops.
Sent from a stolen phone!
Bootloop on Nexus 4, Stock Android 4.3.3...
EDIT Because OP asked how the bootloop occurs on Nexus 4, Android 4.3.3:
Bootloop occurs after activating module and normal (not soft) reboot.
Before reboot app can be runned and configurated.
I have no log app running, so I'm not able to deliver logs.
Yes, please send me a logcat. Bootloops are great, then you can just get the log after the reboot. I literally can't do anything without a log.
mobihack said:
Tried it on my cm12.1. No bootloops here. Will edit after full uncharging
EDIT: Turned turning on full brightness, hot spot, gps, flashlight, mobile data, etc... Still 8% to go. Your module and me are waiting eagerly lol
EDIT2: Finally reached 0
And tonyp, I am pleased to say your module works in cm12.1
Suggestion: Make the dialog box closable. So if I am playing a game or writing to a File I can save my progress. Hope you understand.
And I appreciate your idea. Well implemented.
And do you mind sharing that icon pack :hungry:
Click to expand...
Click to collapse
Thanks for the feedback, then I will add 5.1 to the compatibility at the Play Store.
Regarding the closable dialog, I made it non closable on purpose but I'll consider adding an experimental feature to change that. At first I'd like to fix the bugs, though.
tonyp said:
Thanks for the feedback, then I will add 5.1 to the compatibility at the
Regarding the closable dialog, I made it non closable on purpose but I'll consider adding an experimental feature to change that. At first I'd like to fix the bugs, though.
Click to expand...
Click to collapse
More suggestions:
Add some animations to the dialog
Add option for an alert tune or notification 1min before
Add buttons to dialog box for shutdown(sometimes I dont like to wait)[optional]
Happy with what you had already done and you forgot me an icon pack
bootloops
Bootloop on MMX Canvas Magnus stock ROM (JB 4.2.1)
akhilkbaby said:
Bootloop on MMX Canvas Magnus stock ROM (JB 4.2.1)
Click to expand...
Click to collapse
I'd like to fix the issue, could you kindly send me a logcat of the bootloop?
Unfortunately there is literally nothing I could possibly do without a log.
mobihack said:
More suggestions:
Add some animations to the dialog
Add option for an alert tune or notification 1min before
Add buttons to dialog box for shutdown(sometimes I dont like to wait)[optional]
Happy with what you had already done and you forgot me an icon pack
Click to expand...
Click to collapse
I'm using the stock dialog which guarantees the highest possible compatibility with other devices.
Regarding the notification, I don't know when the battery will be empty before, so there's no way to display a message one minute before. All I could do is starting the dialog at 1% (which I'm considering for a future version), but that would be quite different.
I like the idea for a shutdown button, an option to include that will be in an upcoming version.
Oh, true, the icon pack is called etched material.
Phone freezes when I get a notification from an app. Specifically when I get a notification from Messenger(Facebook app). Is it possible to grab a log if it freezes and I have to restart?
And to make sure it wasn't anything else, I uninstalled it and the freezing stopped.
Galaxy S4 4.4.2 Stock ROM w/ Root
Thanks
HydraS4 said:
Phone freezes when I get a notification from an app. Specifically when I get a notification from Messenger(Facebook app). Is it possible to grab a log if it freezes and I have to restart?
And to make sure it wasn't anything else, I uninstalled it and the freezing stopped.
Galaxy S4 4.4.2 Stock ROM w/ Root
Thanks
Click to expand...
Click to collapse
This sounds very strange, the module is only hooking into one class which has nothing to do with receiving messages.
Yes, usually it works to log the freeze, just start logging (best would be with adb logcat) before it happens.
Can not install on 4.1
I am trying to install it on my xperia x10 running cm10 but it does not install. Please help me so that I can test the module on it.
I am also experiencing odd behavior on CM 11 M11 on two devices: Nexus 5 and 10.
The behavior I'm seeing is that when the battery is running low, the dialog shows up.
When the countdown completes, the device then reboots (seems to be doing a soft boot) instead of shutting down.
I am running some experiments, on a Nexus 4 and I'm hoping to capture a logcat.
---------- Post added at 02:41 PM ---------- Previous post was at 01:49 PM ----------
Fif_ said:
I am running some experiments, on a Nexus 4 and I'm hoping to capture a logcat.
Click to expand...
Click to collapse
There we go, I have it.
This is a logcat of the behavior I was describing earlier: after the countdown, the system performs a soft reboot instead of shutting down.
I have seen this behavior on Nexus 4/5/10 (mako/hammerhead/manta) on CM11 M11.
The logcat below is on a Nexus 4 running CM11 M11 and Battery Shutdown Manager 0.93:
Code:
I/Xposed ( 1726): BatterySM: invokeOriginalMethod. batteryLevel=2, isPoweredLocked=false, chosenTime=30, alertDialog=null, showedDialog=false, prefScreenOff=false, isScreenOn=true
I/Xposed ( 1726): BatterySM: Showing dialog. batteryLevel=0, isPoweredLocked=false, chosenTime=30, alertDialog=null, showedDialog=true, prefScreenOff=false, isScreenOn=true
I/Xposed ( 1726): BatterySM: AlertDialog is showing, postpone shutdown. batteryLevel=0, isPoweredLocked=false, chosenTime=30, alertDialog=true, showedDialog=true, prefScreenOff=false, isScreenOn=true
I/Xposed ( 1726): BatterySM: AlertDialog is showing, postpone shutdown. batteryLevel=0, isPoweredLocked=false, chosenTime=30, alertDialog=true, showedDialog=true, prefScreenOff=false, isScreenOn=true
D/SystemPanel( 4621): Recorder Update, force=false
I/Xposed ( 1726): BatterySM: AlertDialog is showing, postpone shutdown. batteryLevel=0, isPoweredLocked=false, chosenTime=30, alertDialog=true, showedDialog=true, prefScreenOff=false, isScreenOn=true
D/SystemPanel( 4621): Recorder Update, force=false
I/Xposed ( 1726): BatterySM: AlertDialog is showing, postpone shutdown. batteryLevel=0, isPoweredLocked=false, chosenTime=30, alertDialog=true, showedDialog=true, prefScreenOff=false, isScreenOn=true
D/SystemPanel( 4621): Recorder Update, force=false
I/Xposed ( 1726): BatterySM: Dismiss dialog
W/InputMethodManagerService( 1726): Window already focused, ignoring focus gain of: [email protected] attribute=null, token = [email protected]
D/AndroidRuntime( 1726): Shutting down VM
W/dalvikvm( 1726): threadid=1: thread exiting with uncaught exception (group=0x415e4ce0)
E/AndroidRuntime( 1726): *** FATAL EXCEPTION IN SYSTEM PROCESS: main
E/AndroidRuntime( 1726): java.lang.NoSuchMethodError: com.android.server.BatteryService#processValuesLocked(java.lang.Boolean)#bestmatch
E/AndroidRuntime( 1726): at de.robv.android.xposed.XposedHelpers.findMethodBestMatch(XposedHelpers.java:271)
E/AndroidRuntime( 1726): at de.robv.android.xposed.XposedHelpers.findMethodBestMatch(XposedHelpers.java:284)
E/AndroidRuntime( 1726): at de.robv.android.xposed.XposedHelpers.callMethod(XposedHelpers.java:947)
E/AndroidRuntime( 1726): at com.thetonyp.batteryshutdownmanager.BatteryDialog$2.onFinish(BatteryDialog.java:258)
E/AndroidRuntime( 1726): at android.os.CountDownTimer$1.handleMessage(CountDownTimer.java:118)
E/AndroidRuntime( 1726): at android.os.Handler.dispatchMessage(Handler.java:102)
E/AndroidRuntime( 1726): at android.os.Looper.loop(Looper.java:136)
E/AndroidRuntime( 1726): at com.android.server.ServerThread.initAndLoop(SystemServer.java:1289)
E/AndroidRuntime( 1726): at de.robv.android.xposed.XposedBridge.invokeOriginalMethodNative(Native Method)
E/AndroidRuntime( 1726): at de.robv.android.xposed.XposedBridge.handleHookedMethod(XposedBridge.java:631)
E/AndroidRuntime( 1726): at com.android.server.ServerThread.initAndLoop(Native Method)
E/AndroidRuntime( 1726): at com.android.server.SystemServer.main(SystemServer.java:1386)
E/AndroidRuntime( 1726): at de.robv.android.xposed.XposedBridge.invokeOriginalMethodNative(Native Method)
E/AndroidRuntime( 1726): at de.robv.android.xposed.XposedBridge.handleHookedMethod(XposedBridge.java:631)
E/AndroidRuntime( 1726): at com.android.server.SystemServer.main(Native Method)
E/AndroidRuntime( 1726): at java.lang.reflect.Method.invokeNative(Native Method)
E/AndroidRuntime( 1726): at java.lang.reflect.Method.invoke(Method.java:515)
E/AndroidRuntime( 1726): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:732)
E/AndroidRuntime( 1726): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:566)
E/AndroidRuntime( 1726): at de.robv.android.xposed.XposedBridge.main(XposedBridge.java:132)
E/AndroidRuntime( 1726): at dalvik.system.NativeStart.main(Native Method)
W/DropBoxManagerService( 1726): Dropping: system_server_crash (1667 > 0 bytes)
I/Process ( 1726): Sending signal. PID: 1726 SIG: 9
I've trimmed the logcat, but it's available to the dev in its entirety, if needed.
Mubasher96 said:
I am trying to install it on my xperia x10 running cm10 but it does not install. Please help me so that I can test the module on it.
Click to expand...
Click to collapse
The module currently requires Android 4.2 or higher. You can't install the module on CM10 as that is based on Android 4.1.
To support Android 4.0 and 4.1 I need to write some custom code which I need some people to test, so everyone interested in this module on a 4.0 or 4.1 device (including CM9 / CM10 etc of course) please write here or send me a PM and I'll contact you as soon as I have a version ready for testing! Can I count you in?
Fif_ said:
I am also experiencing odd behavior on CM 11 M11 on two devices: Nexus 5 and 10.
The behavior I'm seeing is that when the battery is running low, the dialog shows up.
When the countdown completes, the device then reboots (seems to be doing a soft boot) instead of shutting down.
I am running some experiments, on a Nexus 4 and I'm hoping to capture a logcat.
...
I've trimmed the logcat, but it's available to the dev in its entirety, if needed.
Click to expand...
Click to collapse
Thank you very much for the logcat! It contained exactly what I needed!
Thanks to that I identified the issue and pushed out a new version (0.94) to fix it.
It will probably take a couple hours in the Google Play Store to appear, in the meantime you can find the new version at the Xposed Repo or attached to this post.
Additionally this version fixes a potential bootloop cause for devices running Jellybean (4.2 / 4.3).
Could the affected people please test this and confirm? Again, if you manage to get me a log it will make it a lot easier for me to fix any issue whatsoever.
Changelog v0.94:
fixed a soft reboot on Kitkat devices when the countdown reaches 0
fixed a potential bootloop on Jellybean devices
Nice! This is so necessary… I'm gonna test it.
tonyp said:
Thank you very much for the logcat! It contained exactly what I needed!
I believe I identified the issue thanks to the log and pushed out a new version (0.94) to fix it.
It will probably take a couple hours in the Google Play Store to appear, in the meantime you can find the new version at the Xposed Repo or attached to this post.
Changelog v0.94:
fixed a soft reboot on Kitkat devices when the countdown reaches 0
fixed a potential bootloop on Jellybean devices
Click to expand...
Click to collapse
The 0.94 update fixes the soft-reboot after countdown problem for me on CM11 M11 for Nexus 5. I haven't checked the other devices, and won't be any time soon.
Also, I just bought the Pro version on one device.
The Pro option won't unlock on the other devices, I get a "You already own this item." Error.
@tonyp I'm using WSM Manager (Xposed for MIUI) , but this app still ask to download xposed installer. How to fix this?
Fif_ said:
The 0.94 update fixes the soft-reboot after countdown problem for me on CM11 M11 for Nexus 5. I haven't checked the other devices, and won't be any time soon.
Also, I just bought the Pro version on one device.
The Pro option won't unlock on the other devices, I get a "You already own this item." Error.
Click to expand...
Click to collapse
No worries, they're using the same codebase so it will work on all devices.
Thanks a lot for buying pro
That purchase should work on all devices of course sometimes it takes a little while to propagate at Google, when you still have the issue after a couple more hours could you please drop me a PM? I did test the IAP purchases with all possible ways Google offers for me, but unfortunately that's something that could be greatly improved on their side.
exodius48 said:
@tonyp I'm using WSM Manager (Xposed for MIUI) , but this app still ask to download xposed installer. How to fix this?
Click to expand...
Click to collapse
Ah, I didn't know there exists an alternative manager. I'm explicitly checking for the Xposed Installer. You can ignore the warning for now and I will push an update which recognizes the WSM Manager as well
No bootloops on moto g stock 5.0.2
Hi
Was hoping someone could help. Recently flashed the incremental cm12 oneplus sent out ota. This is the incremental update in prep for lollipop 5.1. Since the I can't seem to xposed working.
I'm am flashing sdk11 via twrp and rebooting and installing the alpha 2 apk but on checking if xposed works screen says it not. This is natter what I do I've tried flashing numerous times and wiping dalvik and cache. To note I am on a one plus with Franco kernal installed 3.4.67. Is anyone aware of any update issues YNGTAS213. I has xposed working perfectly on cm12 YNG1TAS17L. Any ideas?
Thanks
I have just updated toYNGTAS213 and reinstalled xposed and it works fine. Original kernel.
Hope this helps.
I have the same problem, cannot install Xposed.
Tried newest unofficial Xposed arm22 20150520 and still get the sdk21 expecting sdk22 error
same here htc one m8 5.1.1 sdk21 expecting 22 error
DPinched said:
I have the same problem, cannot install Xposed.
Tried newest unofficial Xposed arm22 20150520 and still get the sdk21 expecting sdk22 error
Click to expand...
Click to collapse
dande said:
I have just updated toYNGTAS213 and reinstalled xposed and it works fine. Original kernel.
Click to expand...
Click to collapse
Worked on previous rom, but now not, default kernel too...
Latest build installed, but not working, writes not activ...
Here is the log:
06-29 01:11:14.829 I/Xposed ( 258): -----------------
06-29 01:11:14.829 I/Xposed ( 258): Starting Xposed version 65, compiled for SDK 21
06-29 01:11:14.829 I/Xposed ( 258): Device: A0001 (OnePlus), Android version 5.0.2 (SDK 21)
06-29 01:11:14.829 I/Xposed ( 258): ROM: LRX22G
06-29 01:11:14.829 I/Xposed ( 258): Build fingerprint: oneplus/bacon/A0001:5.0.2/LRX22G/YNG1TAS2I3:user/release-keys
06-29 01:11:14.829 I/Xposed ( 258): Platform: armeabi-v7a, 32-bit binary, system server: yes
06-29 01:11:14.829 I/Xposed ( 258): SELinux enabled: yes, enforcing: yes
06-29 01:11:14.832 I/Xposed ( 258): -----------------
06-29 01:11:14.832 I/Xposed ( 258): Added Xposed (/system/framework/XposedBridge.jar) to CLASSPATH
06-29 01:11:15.258 I/Xposed ( 258): Detected ART runtime
06-29 01:11:15.260 I/Xposed ( 258): Found Xposed class de/robv/android/xposed/XposedBridge, now initializing
06-29 01:11:15.439 I/Xposed ( 258): Errors during Xposed initialization
06-29 01:11:15.440 E/Xposed ( 258): java.io.IOException: Permission denied while reading /data/data/de.robv.android.xposed.installer/conf/modules.list
06-29 01:11:15.440 E/Xposed ( 258): at de.robv.android.xposed.services.ZygoteService.readFile(Native Method)
06-29 01:11:15.440 E/Xposed ( 258): at de.robv.android.xposed.services.BaseService.getFileInputStream(BaseService.java:116)
06-29 01:11:15.440 E/Xposed ( 258): at de.robv.android.xposed.XposedBridge.loadModules(XposedBridge.java:409)
06-29 01:11:15.440 E/Xposed ( 258): at de.robv.android.xposed.XposedBridge.main(XposedBridge.java:103)
06-29 01:11:36.991 F/libc ( 1063): Fatal signal 11 (SIGSEGV), code 2, fault addr 0x7f5b91a0 in tid 1066 (Compiler driver)
06-29 01:11:37.041 E/DEBUG ( 243): unexpected waitpid response: n=1066, status=0000000b
Unable to install YNG1TAS213 update
OPO A001. Nothing special loaded other that my personal apps from the Play store plus the Tapatalk and XDA app. I'm not a full newbie to Android; but neither am I at all new to computing in general.
I get the OTA update available message; but when I click on install; it goes to the install process "Recovery" page. I've chosen both "Apply update" which takes me to a choice of "Apply from ADB" and "Choose from internal storage". Selecting Apply from ADB yields an "Cancel sideload" message. Selecting internal storage route yield choices none of which yield any usable file name. Subsequently; I download a signed file <cm-12.0-YNG1TAS2I3-bacon-signed-fastboot.zip> to the root Internal storage folder. Re-cycled through the update process to the Recovery page found the zip file listed in the /0 folder selected that file and received the same Install failed message ending with the line "Installation aborted". I've tried several times and get the same message.
Anyone able to point me at my point of error and make suggestion on a solution?
Do not set assembly of 65 and 66 for the last snapshot CM12, Lg D802.
Do not set assembly of 65 and 66 for the last snapshot CM12, Lg D802.
I'm new enough to Android to not understand what these settings are. Will you be kind enough to explain?
Thanks
Howard H
Sent from my A0001 using XDA Free mobile app
Finally established on 67 CM12 nightly.
Lockscreen Visualizer
This is (very) simple module which adds Cyanogenmod's music visualizer to lockscreen.
It should work on Lollipop and Marshmallow devices with close to AOSP lockscreen.
If you encounter any problems, first make sure you don't use any sound mods (they may break Android's native visualizer) or other lockscreen mods.
ROMs vastly modified by manufacturers (TouchWizz, Sense, etc) are unsupported (if the visualizer works for you, then great, you're lucky. But if not, don't blame it on me).
If you don't see the visualizer on your lockscreen (but see in the app) and in Xposed logs there's something like "The following required permissions are not granted: ..." then you might try adding that permission (with android.permission. prefix) to the manifest of SystemUI package (decompilation/recompilation needed). Thanks @Kran007 for pointing that out!
Currently tested on Z3 and Genymotion, but should work on every 5.0+ device with close to AOSP lockscreen.
DOWNLOADS
Xposed repo
XDA:DevDB Information
Lockscreen Visualizer Xposed, Xposed for all devices (see above for details)
Contributors
Lawiusz
Source Code: https://github.com/Lawiusz/xposed_lockscreen_visualizer
Xposed Package Name:
Version Information
Status: Stable
Current Stable Version: 1.8.2
Stable Release Date: 2016-11-17
Created 2016-04-08
Last Updated 2016-11-17
Yes, please add Marshmallow support
Tested and works on my Xperia ZR stock 5.1.1
Great module, thanks
ask
Work on 5.0 aosp,thank you!
Tried on Xperia ZL stock 5.1.1 not work, The app stoped working when open, i have gravitybox and tried its lockscreen tweak, could it be the cause of problem? Heres the xposed log of error. Looking forward for stable build ?
04-08 17:31:43.976 E/Xposed ( 1649): at android.media.audiofx.Visualizer.(Visualizer.java:216)
04-08 17:31:43.976 E/Xposed ( 1649): at pl.lawiusz.lockscreenvisualizerxposed.VisualizerView$2.run(VisualizerView.java:84)
04-08 17:31:43.976 E/Xposed ( 1649): at android.os.AsyncTask$SerialExecutor$1.run(AsyncTask.java:231)
04-08 17:31:43.976 E/Xposed ( 1649): at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1112)
04-08 17:31:43.976 E/Xposed ( 1649): at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:587)
04-08 17:31:43.976 E/Xposed ( 1649): at java.lang.Thread.run(Thread.java:818)
04-08 17:35:22.700 E/Xposed ( 1649): java.lang.RuntimeException: Cannot initialize Visualizer engine, error: -4
04-08 17:35:22.700 E/Xposed ( 1649): at android.media.audiofx.Visualizer.<init>(Visualizer.java:216)
04-08 17:35:22.700 E/Xposed ( 1649): at pl.lawiusz.lockscreenvisualizerxposed.VisualizerView$2.run(VisualizerView.java:84)
04-08 17:35:22.700 E/Xposed ( 1649): at android.os.AsyncTask$SerialExecutor$1.run(AsyncTask.java:231)
+1 Marshmallow Support
Hi guys, thanks for your feedback!
TheDevil259 said:
+1 Marshmallow Support
Click to expand...
Click to collapse
shadie21 said:
Yes, please add Marshmallow support
Click to expand...
Click to collapse
Luisbocanegra said:
Please add Support for Marshmallow
Good module
Click to expand...
Click to collapse
Marshmallow's lockscreen seems to be very similar to the L's one. Adding 6.x compatibility should be pretty straightforward.
So stay tuned!
Kran007 said:
Tried on Xperia ZL stock 5.1.1 not work, The app stoped working when open, i have gravitybox and tried its lockscreen tweak, could it be the cause of problem? Heres the xposed log of error. Looking forward for stable build
04-08 17:31:43.976 E/Xposed ( 1649): at android.media.audiofx.Visualizer.(Visualizer.java:216)
04-08 17:31:43.976 E/Xposed ( 1649): at pl.lawiusz.lockscreenvisualizerxposed.VisualizerView$2.run(VisualizerView.java:84)
04-08 17:31:43.976 E/Xposed ( 1649): at android.os.AsyncTask$SerialExecutor$1.run(AsyncTask.java:231)
04-08 17:31:43.976 E/Xposed ( 1649): at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1112)
04-08 17:31:43.976 E/Xposed ( 1649): at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:587)
04-08 17:31:43.976 E/Xposed ( 1649): at java.lang.Thread.run(Thread.java:818)
04-08 17:35:22.700 E/Xposed ( 1649): java.lang.RuntimeException: Cannot initialize Visualizer engine, error: -4
04-08 17:35:22.700 E/Xposed ( 1649): at android.media.audiofx.Visualizer.<init>(Visualizer.java:216)
04-08 17:35:22.700 E/Xposed ( 1649): at pl.lawiusz.lockscreenvisualizerxposed.VisualizerView$2.run(VisualizerView.java:84)
04-08 17:35:22.700 E/Xposed ( 1649): at android.os.AsyncTask$SerialExecutor$1.run(AsyncTask.java:231)
Click to expand...
Click to collapse
In your case the problem seems to be within Android's visualizer library itself (especially in it's native part which throws an exception here). Gravitybox presence is probably not related to this error (because AFAIU the module's ui also crashes). I will dig deeper what the error -4 means, but at this time two things come to my mind:
1. Sound libraries mods (do you use any?) which may cause native visualizer error.
2. Problems with MODIFY_AUDIO_SETTINGS and RECORD_AUDIO permissions. Do you use any mods which may deny those perms?
Working great on my z1c, 5.1.1 236
But sometimes it can be unseen because of the music album color (sorry for my bad English)
G4B33 said:
Working great on my z1c, 5.1.1 236
But sometimes it can be unseen because of the music album color (sorry for my bad English)
Click to expand...
Click to collapse
Colors improvement is currently on my todo list.
Please add Support for marshmallow, i tested it on my nexus 6 and the app crashes, this module can be a legend, please add Support, thank you, the best module of 2016!
A new version version with initial marshmallow support uploaded into Xposed repo. Please let me know whether it works or not, because the only device with marshmallow I have is an emulator. Enjoy!
Thanks for the quick uodate, it works con marshmallow but theres a padding problem
See the screenshot
Moto X 2014 MM stock
I'm running Marshmallow and version 1.2 of your module but it doesn't work. I also am running AudioPrivacy, could that be causing it not to work? Nexus 6, rooted stock AOSP.
Nexus 6P @ Marshmallow
Doesn't seem to be working on my Nexus 6P under Marshmallow.
Here's my log:
://pastebin.com/HGymUvrG
(Can't post links jet. Just add http before ':')
broski270 said:
I'm running Marshmallow and version 1.2 of your module but it doesn't work. I also am running AudioPrivacy, could that be causing it not to work? Nexus 6, rooted stock AOSP.
Click to expand...
Click to collapse
Yes, it may cause the problem, but I think I have workaround for that. Maybe I could do something in the next release.
Damn dont work on Touchwiz For Android 6.0
Lawiusz said:
Yes, it may cause the problem, but I think I have workaround for that. Maybe I could do something in the next release.
Click to expand...
Click to collapse
That's awesome dude! :good: That's one feature that I enjoyed about BlissPop for the short time I was running it, I just don't want the album art to be my lock screen wallpaper.
Lawiusz said:
Hi guys, thanks for your feedback!
In your case the problem seems to be within Android's visualizer library itself (especially in it's native part which throws an exception here). Gravitybox presence is probably not related to this error (because AFAIU the module's ui also crashes). I will dig deeper what the error -4 means, but at this time two things come to my mind:
1. Sound libraries mods (do you use any?) which may cause native visualizer error.
2. Problems with MODIFY_AUDIO_SETTINGS and RECORD_AUDIO permissions. Do you use any mods which may deny those perms?
Click to expand...
Click to collapse
Hello!
I have problem too.
Z1 Compact, 14.6.A.1.216. (5.1.1), module don't work
i have mods for Audio: Viper FX and Gravity Box(lockscreen tvick ON), Music to Walkman
P.S. Sorry for my very bad English
Doesn't work on my Moto G3 Marshmallow 6.0
But the app now launches with update, previous version crashed on start up
Module isn't crashing and it does have a visualiser available inside the app. Yet it is not showing the visualiser on the loxkscreen.
On xperia Z stock 5.11 rom. If you need any logs please let me know. I'm very much interested in this module. I had the mod a while back and it was a battery hog and with incorrect drawables. This one looks like it's the one . Thanks.
Hi. I'm using Cherry Mobile Flare S3ini (Q820) kitkat official rom. The problem is when the resourse hook is disabled, the framework is not working. I wasn't able to use theming modulea due to I need to activate disable resource hook for the framework to work. This is the log.
Sep 12, 2017 8:21:41 PM UTC
Loading Xposed v54 (for Zygote)...
Running ROM 'Cherry_Flare_S3_MINI3G_Q620_V04_20151211' with fingerprint 'unknown'
Errors during Xposed initialization
java.lang.ClassCastException: class android.content.res.XResources doesn't extend class android.content.res.SPRDResources
at de.robv.android.xposed.XposedBridge.cloneToSubclass(XposedBridge.java:787)
at de.robv.android.xposed.XposedBridge.hookResources(XposedBridge.java:365)
at de.robv.android.xposed.XposedBridge.initXbridgeZygote(XposedBridge.java:267)
at de.robv.android.xposed.XposedBridge.main(XposedBridge.java:117)
at dalvik.system.NativeStart.main(Native Method)
My phone is quad core spreadtrum processor, KK 4.4.2 Thanks.