Keep digitiser on for gestures? - Xposed General

Hi. I'm new to Xposed. I was wondering whether there was a module that would allow the digitiser to be kept on (even while screen is off) to accept gestures (like skip forward/backward, toggle flashlight etc). Apparently CyanogenMod on the OnePlus One does this and also the LG G3 for the double-tap feature.

If it's possible on a rom it should be possible in xposed. Xposed is very, very powerful and there is a reason it's called "xposed", as in the meaning to expose or make vulnerable, to show inner secrets.
As for whether such a mod exists right now, probably not. But that doesn't mean other xposed mods don't have such features. It probably depends on the make and model of your device.
Sent from a stolen phone!

shivadow said:
If it's possible on a rom it should be possible in xposed. Xposed is very, very powerful and there is a reason it's called "xposed", as in the meaning to expose or make vulnerable, to show inner secrets.
As for whether such a mod exists right now, probably not. But that doesn't mean other xposed mods don't have such features. It probably depends on the make and model of your device.
Sent from a stolen phone!
Click to expand...
Click to collapse
Hi. Thanks for the information. In my case it's the Samsung S5 phone and the Tesco Hudl 2. I'll try asking on their respective forums. Thanks again.

ME too
i am also waiting for such a xposed module. most of the devs tell its hardware feature all. or some tell its processor feature. and most of the people tell its a kernal fuction.

jjbro007 said:
i am also waiting for such a xposed module. most of the devs tell its hardware feature all. or some tell its processor feature. and most of the people tell its a kernal fuction.
Click to expand...
Click to collapse
Is indeed a kernel feature!

No, it's a hardware feature. If it is not implemented in hardware, it will require constant active mode.

Double tap 2 awake is hardware and software funkcion you need to have this feature implemented in kernel and you need to have screen with digi that can use this software perfect egzample xperia z1 and z1compact they have other screens and z1 can handle this feature and z1c can't have it because of hardware limitation

Related

[REQ] NFC support for S II

have been using this rom since a month without problems and i got the "P" version of i9100 with nfc included, but obviously it not working with this rom. i'm thinking about of the implemetation on kernel of this option for i9100P users like me. i have been reading about that in xda, and i found this thread:
http://forum.xda-developers.com/showthread.php?t=1822447
but, its not continuous or seems to be stopped.
could be this feature implemented someday?
i think i found the driver of nfc chipset ,https://android.googlesource.com/ke...7456ef92735a1257c95eac44/drivers/misc/pn544.c
Edray said:
have been using this rom since a month without problems and i got the "P" version of i9100 with nfc included, but obviously it not working with this rom. i'm thinking about of the implemetation on kernel of this option for i9100P users like me. i have been reading about that in xda, and i found this thread:
http://forum.xda-developers.com/showthread.php?t=1822447
but, its not continuous or seems to be stopped.
could be this feature implemented someday?
i think i found the driver of nfc chipset ,https://android.googlesource.com/ke...7456ef92735a1257c95eac44/drivers/misc/pn544.c
Click to expand...
Click to collapse
The main problem is handling the fact that some of the NFC stuff behaves VERY badly if put into a device that doesn't have the hardware.
No one ever figured out a way to get it added to the P without either having a separate build or breaking the non-P I9100.
Although with the new infrstructure for "unified" device builds, this might now be possible.
As an FYI, the I777 (which REQUIRES a different build due to having different call audio, touchkeys, and a few other things) has NFC. The main blocker on the P was not wanting to create yet another build.
and it will be not possible a flashable zip with NFC enabler, and a script like superSU for not being erased by the updates?
thanks for your reply:good:
Edray said:
and it will be not possible a flashable zip with NFC enabler, and a script like superSU for not being erased by the updates?
thanks for your reply:good:
Click to expand...
Click to collapse
We don't do separate flashable ZIPs and stuff like that. Our build system doesn't support it, among other things.
One more in the request
I join to the kind request for this feature. As you know, NFC is now of use for payment and ID (to enter your office, for example), so I hope it makes sense for you to consider the effort and risk of creating a separate version in a near future. I can't adopt any ROM wo NFC unless I carry additional ID/VISA cards (2 more in my crowded wallet).
bajajel said:
I join to the kind request for this feature. As you know, NFC is now of use for payment and ID (to enter your office, for example), so I hope it makes sense for you to consider the effort and risk of creating a separate version in a near future. I can't adopt any ROM wo NFC unless I carry additional ID/VISA cards (2 more in my crowded wallet).
Click to expand...
Click to collapse
Sorry, but adding NFC to the I9100P won't help you here.
AOSP is missing HCE support for any device with an NXP NFC chipset. Until that changes, the I777/I9100P will not be payment capable even if NFC is added for P builds.

[REQUEST] PBMC for Magisk

If you all remember an xposed module "Physical Button Music Control - PBMC" developed by @Xspeed. I am basically looking for that module to be part of Magisk.
Is there anyone that could port it? It's a humble request from the great developers of this community.
ABOUT THE MODULE:
It basically allows u to have various control options for music, system shortcuts, keyboard presses, application launch etc by using volume buttons of ur phone as well as other buttons regardless of whether the screen is on or not. (You can set the actions to only occur if screen is on or off).
My main concern is that the function should would with screen off.
TahirZX said:
If you all remember an xposed module "Physical Button Music Control - PBMC" developed by @Xspeed. I am basically looking for that module to be part of Magisk.
Is there anyone that could port it? It's a humble request from the great developers of this community.
ABOUT THE MODULE:
It basically allows u to have various control options for music, system shortcuts, keyboard presses, application launch etc by using volume buttons of ur phone as well as other buttons regardless of whether the screen is on or not. (You can set the actions to only occur if screen is on or off).
My main concern is that the function should would with screen off.
Click to expand...
Click to collapse
Hello,
i am looking also from 1 or 2 months on that but it's REALLY difficult because Magisk is really different from XPosed, so i search a framework that i could "import" on Nougat.
The difficuty is in fact that i search an android Framework library that is must up to date (or its me that will must make it up to date), find a way to implement it with Magisk and debug all the stuff..
For me, it's purelly impossible to implement theses features on Android stock without any dedicated framework.
XPosed is an hooking method to implement an art framework, by this fact you can use this framework implementation to declare several extra functions on Android.
Magisk is an system-less implementation system that allow u to use "mororring" Linux fonctions to avoid system partition modifications.
I'm familiar with the difference between magisk and xposed but can't all these functions work say in like a custom kernel? Like how the holding power button turns on flash?
TahirZX said:
I'm familiar with the difference between magisk and xposed but can't all these functions work say in like a custom kernel? Like how the holding power button turns on flash?
Click to expand...
Click to collapse
No, because has my answer on the original thread was confirmed by the dev, more than most of the commands used in the code of PBMC aren't recognized by default in android and so require an external framework like XPosed.
It's the same fact for others apps too certains options in Greenify (as an exemple).
Customs kernels could define differents hardware-software values from stock bases, but they don't add really completly massive codes in android frameworks.
Alright then well have u found any Alternative or would we just have to wait for stable xposed on nougat?
Back in the day before the creation of Xposed people used framework patchers to add volume button track skip feature for example. But this was usable only to ROM developers on custom ROMs.
While it MAY be possible to create a patcher to use with Magisk, it's purely theoretical and would have a lot of flaws in practice (one example would be multiple developers trying to patch one file and users ending up bricking their devices in worst case scenario). Other issue would be time: Java development took me a whole year to make PBMC, and making a patcher would take twice as much time. Not really a good idea, I guess Xposed for Nougat will come earlier than that
Xspeed said:
Back in the day before the creation of Xposed people used framework patchers to add volume button track skip feature for example. But this was usable only to ROM developers on custom ROMs.
While it MAY be possible to create a patcher to use with Magisk, it's purely theoretical and would have a lot of flaws in practice (one example would be multiple developers trying to patch one file and users ending up bricking their devices in worst case scenario). Other issue would be time: Java development took me a whole year to make PBMC, and making a patcher would take twice as much time. Not really a good idea, I guess Xposed for Nougat will come earlier than that
Click to expand...
Click to collapse
Then we shall all wait patiently for u to port it to nougat when xposed on nougat is stable. ?
TahirZX said:
Then we shall all wait patiently for u to port it to nougat when xposed on nougat is stable.
Click to expand...
Click to collapse
As far as I remember I made it compatible and I've seen people saying it works on that unstable version of Xposed for Nougat.
Actually it does work on Nougat, the problem is that Xposed for Magisk breaks the SafetyNet.
I'm looking for something like this as well...
Not looking for anything fancy. I just want to be able to long press volume up or down to skip music tracks while screen is off. Im on stock OOS rooted and TWRP on OnePlus 6.

Upcoming root/Backup TA w/o loosing functions?

Hey there,
yesterday I bricked my Xcompact (never come back option).
Now I can choose between a Xc and a new XZ1c.
Root and DRM is very important for me and I do not want to miss it.
Do you think, there´s a fully functional Root-/DRM (TA) Workaround upcomming in the near future or is it unlikely?
Kind Regards,
Chris
dhchris said:
Hey there,
yesterday I bricked my Xcompact (never come back option).
Now I can choose between a Xc and a new XZ1c.
Root and DRM is very important for me and I do not want to miss it.
Do you think, there´s a fully functional Root-/DRM (TA) Workaround upcomming in the near future or is it unlikely?
Kind Regards,
Chris
Click to expand...
Click to collapse
You can restore DRM function with a "bypass" patch once you have root and lost your keys... but if you "unroot" you wont have the DRM functions
Full DRM keys backup as old days seems impossible with current Sony security, I believe
dhchris said:
Do you think, there´s a fully functional Root-/DRM (TA) Workaround upcomming in the near future or is it unlikely?
Click to expand...
Click to collapse
As mentioned above, there is no way back from deleting your TA partition. There are several threads on this forum regarding using a DRM 'fix', but it looks pretty tricky to set up.
But, help is at hand. The developer sToRm// is about to release a 'one stop shop' fix for all types of Sony. So follow his Sony Xperia XZ Premium TWRP + KERNEL + ROOT + DRM fix/restore thread and this will be the easy solution.
LineageOS is also gaining traction and reading the comments is almost at a daily driver level.
There's a fix released.
I trully don't understand why Sony spends so much time with this DRM stuff when their camera isn't all that good. It's just sad.
Official link: https://www.xperifix.com/
sToRm// said:
To all XZ1 and XZ1 Compact users:
XperiFIX now supports your devices! You can download the current version (fixed) again, install and run it.
https://www.xperifix.com/download/xperifix-latest/
Please report if it works for you!
Original thread: https://forum.xda-developers.com/xz...hack-mod-sony-xperia-xz-premium-twrp-t3695171
Cheers!
Click to expand...
Click to collapse
Is it actually worth rooting this phone? I only see 1-2 custom roms, no camera mods, basically no mods in general.
Apart from adblock and getting rid of bloatware (which you can disable), what's the real advantage of voiding the warranty?
Just to be clear, I usually root all my android devices, maybe what I'm missing for the XZ1c are mods and roms..
charliebigpot said:
Is it actually worth rooting this phone? I only see 1-2 custom roms, no camera mods, basically no mods in general.
Apart from adblock and getting rid of bloatware (which you can disable), what's the real advantage of voiding the warranty?
Just to be clear, I usually root all my android devices, maybe what I'm missing for the XZ1c are mods and roms..
Click to expand...
Click to collapse
Well... for me, one of the main reasons is to install Xposed and then X Messenger Privacy Premium
Since the device only has 32GB, installing [Magisk Module] Magic Folder Binder in order to expand the internal storage transparently as I explained in this reply
There's also other goodies with Magisk such as ENABLE DOZE on Google Play Services or Greenify4Magisk.
For exposed depending how comfortable you're with the idea of ripping off YouTube Red you have YouTube background playback
All in all, there isn't any direct mods to Xperia Roms, but the ones that come with Xposed/Magisk.
luminoso said:
Well... for me, one of the main reasons is to install Xposed and then X Messenger Privacy Premium
Since the device only has 32GB, installing [Magisk Module] Magic Folder Binder in order to expand the internal storage transparently as I explained in this reply
There's also other goodies with Magisk such as ENABLE DOZE on Google Play Services or Greenify4Magisk.
For exposed depending how comfortable you're with the idea of ripping off YouTube Red you have YouTube background playback
All in all, there isn't any direct mods to Xperia Roms, but the ones that come with Xposed/Magisk.
Click to expand...
Click to collapse
Just got and set up my XZ1 - jeez, I take it all back, can't stand all the apps that are already installed, I'll root for sure.
Btw, thanks for the links!
charliebigpot said:
Just got and set up my XZ1 - jeez, I take it all back, can't stand all the apps that are already installed, I'll root for sure.
Btw, thanks for the links!
Click to expand...
Click to collapse
If your biggest reason for root is only because of the preinstalled apps, then might I suggest you take a look at this thread. Unless you have other pressing root uses, in my opinion it's not worth voiding your warranty just to get rid of a couple of apps which can be done without root.
Don't know what Android devices you've previously owned, but in case you weren't aware, with Sony phones you permanently lose your unique DRM keys once you unlock your bootloader with no way of getting them back.
Basically, your warranty would be irreversibly voided, doesn't matter if you relock your bootloader, clean flash stock firmware or whatever.
Currently there exists no method of backing up and restoring those keys, which is likely one of the main reasons for the lack of custom developments for this phone.
Could be a different scene once phones begin to age past their warranty period and people no longer have any other reason to hang on to those keys, but for now, I'd still recommend to hold off rooting.

What to consider before Rooting?

I was a Sony fan until lately it got a bit not worthy in my opinion.
I had Xperia mini then Xperia z3 compact until 3 months ago (that i got note 9)... it was rooted, custom rom, Xposed and stuff.
I know that by Rooting a Sony phone, you loose DRM features (camera improvement ...) that can be later restored by flashing a DRM fix zip and that's it, you still have everything.
but this is my first Samsung phone so I'm unfamiliar with all stuff(Odin, Knox, etc....)
questions I have:
1_ What I loose by Rooting? can they be restored after root?
2_ Wich method you suggest and why? magisk or SuperSU? or something else
3_ What do you recommend to install/set/tweak/flash after Rooting?
my phone: SM-N960F Running Android 9.0 updated 1 July 2019
Welcome to the dark side my friend!
Your Knox bit will flip from 0x0 to 0x1 - that's the first thing that will happen once you flash a custom recovery & kernel. This means that all Samsung features that check the bit status will permanently stop working; including, but not necessarily limited to, Samsung Pay, Secure Folder, S Health, Samsung Pass, the works. The change is permanent and can not be reversed by erasing everything and returning to stock firmware. As far as long-term effects on rooting go, that's pretty much it. Unlike on Sony Phones, outside these specific applications, there's no impact on other functionality like proprietary camera processing and image enhancement.
These days Magisk is generally recommended. SuperSU has been going downhill for a while, ever since Chainfire retired and handed off the development. It's also the only way to pass Google's SafetyNet checks while rooted.
As for recommended tweaks - well, that's up to your personal tastes. Myself, I'd protect the battery from excess wear by limiting maximum charge to 80%, and set up support for Sony's DualShock 3 I'm sure you'll find that most tweaks you liked on the Sony side will also work here.
You will lose samsung pay as well which supports MST which is a killer feature for me.
oddbehreif said:
Welcome to the dark side my friend!
Your Knox bit will flip from 0x0 to 0x1 - that's the first thing that will happen once you flash a custom recovery & kernel. This means that all Samsung features that check the bit status will permanently stop working; including, but not necessarily limited to, Samsung Pay, Secure Folder, S Health, Samsung Pass, the works. The change is permanent and can not be reversed by erasing everything and returning to stock firmware. As far as long-term effects on rooting go, that's pretty much it. Unlike on Sony Phones, outside these specific applications, there's no impact on other functionality like proprietary camera processing and image enhancement.
These days Magisk is generally recommended. SuperSU has been going downhill for a while, ever since Chainfire retired and handed off the development. It's also the only way to pass Google's SafetyNet checks while rooted.
As for recommended tweaks - well, that's up to your personal tastes. Myself, I'd protect the battery from excess wear by limiting maximum charge to 80%, and set up support for Sony's DualShock 3 I'm sure you'll find that most tweaks you liked on the Sony side will also work here.
Click to expand...
Click to collapse
Thanks for the Complete answer
I'm okay with, most of it... you know the secure folder is an awesome feature (at least for me) that is built in, super fast and integrated into various apps.
I haven't seen such an app as this stable and secure while maintaining this much functionality over many apps and locations inside the phone.
so that's a 'not sure yet' for me ... ?
can't something be made to reverse or change Knox trip to 0x0 again?
it made me interested... I want to participate or donate to such a project if it's ongoing
EL MAXERO said:
can't something be made to reverse or change Knox trip to 0x0 again?
it made me interested... I want to participate or donate to such a project if it's ongoing
Click to expand...
Click to collapse
Unfortunately, no. When an unsigned kernel is booted, the bootloader will detect it and trip a physical fuse in the SoC. There are ways to fake 0x0 status when fully booted, but since these features check the actual "eFuse", there's really nothing that can be done short of replacing the entire motherboard.
I remember this being a hot topic among developers since the Note 3 days; to this day nobody has claimed the bounty of several thousand dollars sitting in the Note 3 section of XDA Forums.
With root and Dr.Ketan ROM you basically get everything from this device:
- Native call recording
- Full/Half screen caller with native dialer
- All sorts of optimizations, memory management and tweaks
- Youtube Vanced (it can be used without root, but with root is a bit more convinient)
- GPay works with Magisk
You can see the list of all features(they are a ton) on Dr.Ketan ROM thread as well on his page http://www.drketanrom.com/
I was using the same Rom+root on my Note 8, now on my Note 9. I also got his Tweaks Pro app which is paid, but very useful. It's a no-brainer for me since I care much more about the functionalities rather than the warranty of this phone.
Ofc, this is my subjective point of view.
No more Samsung Pass? I like not having to type passwords in all the time. Is there something with similar functionality?
asif9t9 said:
No more Samsung Pass? I like not having to type passwords in all the time. Is there something with similar functionality?
Click to expand...
Click to collapse
LastPass works but requires a yearly subscription. You can also use the one in Google.
asif9t9 said:
No more Samsung Pass? I like not having to type passwords in all the time. Is there something with similar functionality?
Click to expand...
Click to collapse
pretty sure it works so does the google version called auto complete.
BajaBlast4Life said:
LastPass works but requires a yearly subscription. You can also use the one in Google.
Click to expand...
Click to collapse
LastPass is free. You can get a paid version but is not necessary.
In all honesty there is really not that much of a benefit in rooting a modern day android device, unless you are a developer or an android hobbiest! As the current iterations of android are pretty good right of the bat!

Xposed Framework Device Compatibilty

Hi
I have a primary phone (Xiaomi mi 8) running Android 10. I also have an SM-A710M galaxy (I know this not popular at all) running LineageOS
Both these phones are rooted with magisk and I tried to install the xposed framework on the Samsung using this tutorial : https://forum.xda-developers.com/xpo...posed-t3388268
In this thread, it is said that the framework works on all Android versions and that if a device supports Magisk rooting, then Xposed is also supported
Well actually that is not true as it turns out xposed is not supported on my two different phones.
Is this a bug ? Is it just because Xposed is not THE APP IT USED TO BE ? Or are my phones really not compatible ?
Sorry for my english
Thanks for any help
Just ordered a Galaxy A71; anyone have any idea whether I'd be able to install Xposed and GravityBox?
Kimmoth said:
Just ordered a Galaxy A71; anyone have any idea whether I'd be able to install Xposed and GravityBox?
Click to expand...
Click to collapse
You will be able to install edxposed with magisk but not gravity box.
Gravity box is made for AOSP ROM, almost all features of gravity box will not work on One UI of Samsung.
Fishcat7 said:
You will be able to install edxposed with magisk but not gravity box.
Gravity box is made for AOSP ROM, almost all features of gravity box will not work on One UI of Samsung.
Click to expand...
Click to collapse
Yeah, I was afraid of that... but isn't more like, the more a vendor modifies AOSP, the more tweaks are broken?
The big one for me, a reason just by itself to install GravityBox, is to enable the volume buttons to move the caret in a text field. Second-biggest reason is to allow customisation of all buttons for double-tap and long-press functions. Third, more control over DPI setting (I like to make stuff as small as I can see, to use desktop mode in my browser; standard control doesn't let me go far enough). The other tweaks I make with GravityBox, I could live without.
So technically speaking, these are very small reasons to bother with Xposed and GravityBox, but the useability gains make it worth the hassle. I don't suppose I could find these modifications as individual tweaks for the A71's stock firmware, somehow?
Kimmoth said:
Third, more control over DPI setting (I like to make stuff as small as I can see, to use desktop mode in my browser; standard control doesn't let me go far enough).
So technically speaking, these are very small reasons to bother with Xposed and GravityBox
Click to expand...
Click to collapse
Two things. The first one is that if you want to have full control over DPI I advise you to use the root essentials app : https://play.google.com/store/apps/details?id=com.superthomaslab.rootessentials
Using edXposed is a great solution but (if I am not mistaken, I think you rooted with Magisk no? Just keep in mind that if you install edXposed, you will loose one the most important magisk feature : pass Safety Net check
cl.ement05 said:
Two things. The first one is that if you want to have full control over DPI I advise you to use the root essentials app : https://play.google.com/store/apps/details?id=com.superthomaslab.rootessentials
Using edXposed is a great solution but (if I am not mistaken, I think you rooted with Magisk no? Just keep in mind that if you install edXposed, you will loose one the most important magisk feature : pass Safety Net check
Click to expand...
Click to collapse
I haven't got the phone yet... every damn time I get a phone, it's like I have to go back to square one learning how to root; it's like fortnight of eye-glazing research to make it happen. Googling Safety Net this time around, things look grim.
For the first time, I'm wondering if it's a better idea to not mess with my phone, which pisses me off hard.

Categories

Resources