yashsingh1/xdaforums huggingface dataset:
[Xposed Framework Modules] Nees3:
So I found out that the lollipop version is on the first page! (it is not availbable in the Xposed app???)

Seems there is a bug with torch or opening apps.

First I had double press for torch on Home: torch goes on, double tap to turn it off. Turns off. Tried it a few times. After 3 times, it doesn't do anything anymore and then get a popup that Xposed Addition has stopped. And from then on, it happens every time I double press the button and only way to resolve it reboot.

Then I changed double press to Open Camera (selected the app, because Camera would nog work) and it doesn't open correctly then afterwards, says it cannot connect to camera anymore. Need to reboot device to fix it.
[Xposed Framework Modules] dk_zero-cool:
The new version is in the Xposed Repo, whether or not there is a sync problem with Xposed Installer I do not know, it's not my app.

About your problems, I need a logcat of these problems and some ROM/Device information. I can only test this on CM12 as this is the only Lollipop ROM for SGS3 that works with the new Xposed Framework. But do note that Xposed Framework itself is not yet stable, so this might not even be a module problem, but if you provide a log of this issue I can check that fact.
[Xposed Framework Modules] robertogl:
I see the new version from Xposed installer app, no problem for me.

Inviato dal mio GT-I9505 utilizzando Tapatalk
[Xposed Framework Modules] Nees3:
Strange, I don't see it :) Even changed to show experimental builds. Nothing :(

Ohwell. About the logs... It is empty. It even crashes when I try to open it after I encouter the problem and the FC popup.

I couldn't even get into the module after it happens. A few retries later, I do get in, but empty error log. And yes, I enabled it and rebooted device first.

Btw, my device is also an I9300 CM12. Are the logs stored somewhere perhaps? Then I can check with rootbrowser.
[Xposed Framework Modules] dk_zero-cool:
The Error log does not work on Lollipop yet, that is a problem with Xposed Framework. You will have to use a logcat app or something to get it.
[Xposed Framework Modules] Nees3:
For some reason, logcat apps don't show anything new since 16h48. My last reboot. I tried CatLog, that allows recording. Empty log. Also in the full logs, nothing new. Tried another app, same info, nothing new.

Weird.
[Xposed Framework Modules] November91:
when i start the app it says missing system service.. my other xposed apps are working, am i missing something? it is activated in the modules-part of xposed, and i restarted the phone
[Xposed Framework Modules] a.fontenele:
Hey [MENTION=3147360]dk_zero-cool[/MENTION]

I just wanna give you my feedback on this latest release...

It's perfect on stock rom... The issues I had with the torch are now gone... Tks a lot for that...

On my side I see no issues whatsoever on this build.

Great job buddy!

As always I keep pushing my friends to get the PRO version as a "thank you", lol...
[Xposed Framework Modules] dk_zero-cool:
It means that the app service is not active, which is properly because the module crashes for some reason during boot. I need ROM and Device information and a logcat from boot. Either get it during boot from ADB, or grab it from a logcat app right after boot, and I mean right after because the log size is limited so the important information will be gone after awhile.

And just to clarify this once more. The Error log in Xposed Additions does not work yet on Lollipop, so you need a logcat app, the other will not show anything.
[Xposed Framework Modules] diogo.sena:
That's because selinux, in my tests, xposed additions only work if i set to permissive, and soft reboot.
[Xposed Framework Modules] dk_zero-cool:
In that case this is a problem with Xposed Framework and not the module. SELinux protects the Linux environment, but it has nothing to do with the Android Framework, which is where the module lies. Xposed Framework might be blocked from reading the Assets file where the initiations information is placed. That would stop Xposed Framework from loading the module during boot.
[Xposed Framework Modules] diogo.sena:
Other modules are working fine here, can't you do some workaround in the module itself?
[Xposed Framework Modules] dk_zero-cool:
In that case it's properly the systems access to the app's config file that is being refused. Just checked and my ROM runs permissive by default, so properly why I have not encountered this issue. I will have a look at this.
[Xposed Framework Modules] semanty:
i use permissive, but it works not stable, any new module install or reboot or power off and on, it looose effects, but i can enable it again by toggling it once and soft reboot, must soft reboot, not just reboot
[Xposed Framework Modules] TwinAdk:
Hey,

I can confirm this. Im on the AICP ROM (8.0 nightly, running lollipop 5.0.2).

It enforced by default, but i am using an app thats switcing to permissive after boot - BUT, its AFTER boot :) I think thats why i have the

"Missing System Service" prompt when opening the module.

Im looking into switching my rom to permanently permissive on the SE Linux front :)

Og ZeroCool - Xposed Additions er absolut uundværlig på min telefon! Den, og AppSettings er årsagen til at jeg hopper over på LP! :good::highfive::laugh::victory:

Kind Regards

TwinAdk
[Xposed Framework Modules] papatzis:
Hi to all please I want to ask a question.

I have a no name 10,1 tablet running kitkat 4.4.2, I bought a universal case and I cannot switch the device on using the power button, so I installed xposed additions ( I had already xposed framework installed with gravitybox ) and I tried to remap volume- hardware key on screen off to power.

When i turn the screen off and I try after 2-5 seconds with volume- to power on , device powers on succesfully, but if I leave it over 1 minute with screen off, I cannot switched it with volume- I had to press 5-6 times and sometimes 2 of the 10 times it power on

I had also noticed if I have the tablet on charge it is working fine.

Am I missing anything?

Thanks in advance
[Xposed Framework Modules] dk_zero-cool:
This is caused by a pure kernel that does not handle other buttons very well when in deep sleep. When you have the device powered, it does not go into completely deep sleep, which is why you don't have this issue. But when the device is not powered, the kernel takes a bit of time to wake and react on your button clicks.

I cannot do anything about this. The issue is before the module get's any notice of any button presses. Xposed Framework cannot change anything in the kernel, so your only option is to find a custom one, if one such even exists for your no-name device.
[Xposed Framework Modules] papatzis:
Thank you my friend for the answer
[Xposed Framework Modules] robertogl:
Has this feature a name? I've the same 'problem' but how can i see if a kernel can do that without install it?

Thanks ;)
[Xposed Framework Modules] TwinAdk:
I would look for a kernel tweaker that may be able to modify this behavior. If it is even possible to modify I do not know.

m

It's not a thing that is named as such, it's just a part of the properties of the kernel itself. It about deep sleep behaviour and power management internally in the kernel. Custom kernel would be the way to go, BUT MAKE SURE YOU HAVE A BACKUP OF THE STOCK KERNEL!! :)

Kind Regards

TwinAdk
[Xposed Framework Modules] CraiaSoftware:
I'm using an lg g3 with bliss pop rom. I cannot get xposed additions to use any of the soft keys (home, recent, etc) when trying to add a new button remap. Currently searching on XDA is down so I can search this thread. Any ideas why?
[Xposed Framework Modules] ImperatorShade:
Im trying to make this work on a nexus 4 running stock rom with matr1x kernel, and it keeps telling me to install XposedBridge (I'm thinking that's the same as "Xposed Framework") and restart the phone. Any idea what the problem could be?

EDIT : I did some reading (I'm sorry I didn't do it before :P) and I might have figured out the problem.. Is there any way to permanently set selinux mode to permissive?
[Xposed Framework Modules] gerhardo:
Off topic but:

Soft reboot or see this post (seen on the first page for Xposed forum)

http://xdaforums.com/xposed/how-to-set-selinux-to-permissive-boot-t3034245
[Xposed Framework Modules] dk_zero-cool:
It's not a feature, it's just a mater of how the kernel was built. Not sure if it is an issue with some kernels, or if they are made like that on purpose. Anyway you cannot check this without installing and trying the kernel. But if it is a custom kernel, you can write to the developer of that kernel and maybe he/she will be willing to look into it. I am not much of a kernel developer. I have only made minimal changes to some kernels and compiled a few for Android and a couple of my Linux systems, so I cannot tell you where this issue lies. All I know, based on a few tests on such kernels, is that some kernels does not properly direct the button presses to the Android framework while the device is in deep sleep.
[Xposed Framework Modules] robertogl:
Thanks ;)

I'll try some kernels, installing a kernel from a recovery is question of seconds :p
[Xposed Framework Modules] Dj Telo:
Hello!

I have just installed the module on a Samsung s4 running CM12. It doesn't recognise xposed framework. Here's the link to my logcat. Please let me know if it's good enough, as I am not really familiar with this kind if logs. Thanks so much for your hard work, I waited to update to Lollipop until your module was compatible with it.

https://www.dropbox.com/s/qdrx65e59ta8tnv/2015-03-02-22-40-03.txt?dl=0
[Xposed Framework Modules] dk_zero-cool:
Thanks for the log. It has all needed information, but it is already known. SELinux seams to have been extended to watch internal Java IPC (Communications between different processes, or apps if you'd like). The module is divided into 3 parts, a service placed in base of the system, the hooks which are placed in different sections of the system and the app itself. SELinux seams to be protecting the service part from the module hooks (The code that handled all the custom features). In short, SELinux is protecting Xposed Additions from itself.

I am gonna try to sort this out, but in the mean time disable SELinux. If your ROM has this enabled by default (which yours seams to have), you need to use the SELinux changer app (cannot remember the name) and then make a soft-reboot. Normal reboot will not work, as it will just enable SELinux again.
[Xposed Framework Modules] Dj Telo:
Thank you for your quick feedback. Indeed, I changed the SELinux thing and the module works flawlessly so far. No difference from KK to Lollipop. Awesome work, thank you very much!
[Xposed Framework Modules] matii_ziomek:
[bug] vibrations don't work with screen buttons in LG D802.
[Xposed Framework Modules] dk_zero-cool:
Unless you are running some kind of AOSP ROM, it's not really a bug. I make this module based on the original Android source codes. Many device manufacturers has a tendency to make huge changes to this code base, and they do not provide any source codes like Google does. I try to add fixes for most of these devices that does not work properly, but without source codes and even without owning the devices myself, this is not always an easy task. So officially, this module is supported on pure AOSP ROM's, but does work on some others as well, some times with a few minor problems here and there though. There is no way around this, unless LG, Samsung and HTC stops changing things that does not need changing. Or they start providing source codes (I would not bet on it).
[Xposed Framework Modules] matii_ziomek:
Ok. Thanks for answer ;) if you need beta-tester for G2, please, send me PM :) cheers :D
[Xposed Framework Modules] shakeelsaraf:
sir

can the device me made to wake from sleep using the home capacitive button by remaping it to the power button??

i tried the above but doesnt seem to work......

android version: 4.2

mediatek soc MT6589

having 3 capacitive buttons home back and menu

---------- Post added at 09:04 PM ---------- Previous post was at 08:46 PM ----------

also in the add key option i was not able to add my lock/power button or volume up and down button

does this supports only 3 buttons?

also

i selected disable for my all 3 capacitive buttons (home back and menu) (since i wanted to use the on screen buttons) i noticed that the buttons are not fully disabled.....meaning if i press them the touch (touch and hold) screen becomes unresponsive (this is normal for my device that the touch screen does not respond when the capacitive buttons are pressed and held)

so is there any way for me to fully disable the the capacitive buttons? so that i can hold the bottom of my phone and use the touch screen!

ty in advanced sir
[Xposed Framework Modules] dk_zero-cool:
This is how this work.

You press a button on your device

The press action is sent from some embedded software to the device kernel

The kernel sends it to an native android observer

The obsever sents the action to the Android Framework

My module takes the action before it reaches the Framework. Here the module decides whether or not to do something with it, or just give it back to the Framework

So no, my module does not fully disable a button. What it does, is capture it before Android get's it. But I cannot capture it before the kernel or before the chip software, that is to deep inside the operating system and there is no way to get that far down without rebuilding the OS. And even then you cannot get past the chip software.

Capacitive buttons are not real buttons. They are a section of the screen that get's registered as buttons by the embedded software, so when you try to press one while using the display, you are actually performing multi-touch operation on the screen, and how that works depends on whatever software is placed on the chip and/or what your kernel is programmed to and the capabilities of the display itself. Never the less, my module cannot change this. Buttons will always be handled by any software beneath the Android Framework.
[Xposed Framework Modules] dk_zero-cool:
New Version

[MENTION=4419114]rovo89[/MENTION] was kind enough to provide some advise as to how to bypass the new SELinux Restrictions. I have added this solution and some other things to get the module to play nice with SELinux. This means that it should no longer be necessary to put SELinux into permissive mode. The new version is on the Xposed Repo site.
[Xposed Framework Modules] robertogl:
Hi, i've tried the new version on CM12, with SELinux set to Enforcing. It works, but every time i reboot my phone Xposed Additions forgets the button configuration and i've to set that again. With SELinux set to permissive and the old version (3.5.0) it works without this problem.

Thanks for your work!
[Xposed Framework Modules] dk_zero-cool:
That means that SELinux is blocking the service from writing to the configuration file. It will require a bit of rewriting to get that sorted out. Might take a day or two.
[Xposed Framework Modules] robertogl:
Thanks, no problem for me, I will stay on permissive SELinux for now ;)
[Xposed Framework Modules] yelkarama:
Hi

Can you please add possibility to remap double clicks on menu and back buttons?

Thanks
[Xposed Framework Modules] dk_zero-cool:
Double click, trible click, double and trible long press along with combo options are all part of the pro unlock package.
[Xposed Framework Modules] TwinAdk:
I am very happy with this, this module was the only one that required me to have permissive selinux

:) :D

Confirmed on my M7 (AICP rom, LP). Eagerly awaits a fix for this :good:

Kind Regards

TwinAdk
[Xposed Framework Modules] fonz93:
Hi, i use this module on CM10.1, after last update, settings are reset at each reboot
[Xposed Framework Modules] dk_zero-cool:
Yes there seams to be a problem with the new settings handling, although for me it's random, which is properly how it got past the testing. It's being worked on though.
[Xposed Framework Modules] Dj Telo:
Yesterday I installed the last CM12 nightly and updated the module and now it is not working. Cannot detect xposed installed. The SELinux is set to permissive. I will upload the log as soon as I can, unless you have this already under investigation.
[Xposed Framework Modules] TwinAdk:
Flash the zip for xposed in recovery

Boot and install apk

SOFT reboot
[Xposed Framework Modules] Dj Telo:
I have already reinstalled xposed, of course. All the other modules are working fine.

Here's the log.

https://www.dropbox.com/s/8fyd0yrhndv4yrq/2015-03-13-09-26-20.txt?dl=0
[Xposed Framework Modules] dk_zero-cool:
There is something wrong with your xposed framework installation, the module installation or your ROM. Below is two lines from the log that you provided

The module does not work, beause Xposed Bridge does not load it. And yes I do see that the other modules are loading fine.

I cannot tell you why. What I can tell you is that this is not an issue with the module. The module does not even get loaded, so it has no affect on what is going on.

But if you could check what is actually residing inside the directory "/data/app/com.spazedog.xposed.additionsgb-1/" that might help figure out what is going on?
[Xposed Framework Modules] Dj Telo:
Nevermind, I reinstalled you module from scratch and it is working flawlessly now. Maybe it was a problem of restoring it with Titanium Backup after the CM12 update...

Thanks for the support ;)
[Xposed Framework Modules] dk_zero-cool:
Yes that would give you problems. Android 5 has changed the way applications is stored. In previous versions the APK file was placed in /data/app. But in Android 5, they are placed in /data/app/<package name>/. So if you did a restore and they placed it in the base of /data/app, then ART would not be able to locate it.
[Xposed Framework Modules] Kiristiba:
Hello

First of all a big thx for your work :)

I got a used Moto X running experience ROM 4.0 which is based on a Stock 4.4.4 Firmware.

I have a problem wich is already reported in this thread.

As soon as i use a version newer than 3.2.2 my power button stops working,

and the volume buttons only work in the standard way, no matter how i remap them.

I already tried a different custom kernel, but the problem remains.

i enabled the debug log, but there is nothing new written when pressing a button etc.

i know you are busy getting everything working in lolipop but

if i can help you in any way to fix this bug, please let me know.

greetings from germany

kristin
[Xposed Framework Modules] dk_zero-cool:
The log in the app will only report errors. Debug entries is only printed to standard logcat output and you will need an app or ADB to get it. If I am to have possible changes of fixing this I will need you to get some of this log output while producing your power button issue. That way I can see how the module handles it.
[Xposed Framework Modules] Dj Telo:
With the last version of exposed and the module I also have the problem of configuration loss after reboot. Besides, I've been experiencing loss of responsiveness in the home button of my S4. I think I'll wait a few days for a new version before activating the module again. I am convinced that sooner or later it'll work perfectly as it used to with 4.4.
[Xposed Framework Modules] dk_zero-cool:
The problem at this point, is to figure out what issues belongs to the module and which belongs to Xposed Bridge. At this moment, the module's Lollipop support is based on an alpha version of Xposed that has yet to be seen working on anything but mostly CM based ROM's. And even though it seams to be working, there is a great deal of things to sort out. The log contains lots of Xposed errors that, to the user, does not seam to affect much, but they are an indicator that things are not running quite as they should.
[Xposed Framework Modules] Kiristiba:
Hello

I saved a log while pushing the power button multiple times.

I have the latest module version installed and the screen was always on.

If you need more logs, just tell me :)

Greetings and big thx

Kristin
[Xposed Framework Modules] dk_zero-cool:
Well to begin with, the actual log that you are talking about, would be great. Maybe you could attach it? ;)
[Xposed Framework Modules] ayoubij:
[MENTION=3147360]dk_zero-cool[/MENTION] im having a bug, after a while or after reboot my learned keys are gone. For example i put long press menu button to be search and it disapear after a while i enter the app i find no assigned buttons.

Please fix this bug
[Xposed Framework Modules] Kiristiba:
Sry, forgot to push the upload button.
[Xposed Framework Modules] dk_zero-cool:
I know this, just downgrade to 3.5.2 for the moment.
[Xposed Framework Modules] dk_zero-cool:
Well nice done on the log, contains just the correct information. But it looks strange in the way it registers the button. Does the other buttons work as they should? Back, Home, Volume and such? And the power button does not turn the screen on and off?

Could you get a new log, this time with only one single normal click on the power button. Then after that, do the same with another button, Home, Volume, it does not really matter. I just need an output of two buttons with a single click where Power is one of them.
[Xposed Framework Modules] Kiristiba:
Here it is,

i pressed the power button first and then a volume button.

I don't have another key to press.

The volume buttons are nearly working as they should, they change the volume

but if i assign a custom action to them, they still only change the volume.

Big thx for your effort, greetings

Kristin
[Xposed Framework Modules] dk_zero-cool:
That is great. Now just one more, the same as the last only this time press both the keys twice with normal interval (Not double tap speed). First twice Power and then twice volume. I need the logs to compare against the behavior on my own devices, which are working as they should. If your device is not working properly, then something must be different. And if your volume works like it should, then that is also good to compare against your power button.

When you have that log, then let's have a look at your volume remap issue as well. Remap one of your volume buttons to one of the custom actions (Power Menu, Flash Light, or something like that). Then take another log while trying to invoke that action.

And last, could you go to the Error Log in the app and send that via mail to me (the mail option is in the actionbar). It might be empty, but that does not mater. The app will still attach a lot of Device and ROM details that might be useful.
[Xposed Framework Modules] Kiristiba:
Hi, here are the two logs you requested :)

For the second one i remaped the volume key

to the power menu action.

I also emailed you the apps error log but it had 0kb.

The reason for the problems must be somewhere in the changes you made from app version 3.2.2 to 3.3.

If you want, i can get logs from the working app version too :)

Thanks allot, greetings

Kristin
[Xposed Framework Modules] dk_zero-cool:
Yes well the changes between those two version will not help much. About 70% of the whole module part was completely rebuilt, so we are talking about a ton of lines of codes in several files. But hopefully the logs will help.
[Xposed Framework Modules] navdra:
Looking forward to this, also