Manually Power Toggles NFC toggle and Magisk - Magisk

Samsung Galaxy S6: Wanted to update from Marshmellow (rooted with SU) to Nougat.
Unrooted, updated to Nougat and rooted with SU 2.78 and used Titanium Backup to re-install some stuff and mainly data back into Nougat.
Everything worked good but while reading a bit more i found that there was a newer version of SU then the one i had used (2.82 instead of 2.78).
So i uninstalled SU 2.78 and installed 2.82 instead.
Then i noticed that some stuff didn't work anymore, one thing was toggling NFC on or off through Tasker, it always came with an error that there was no root for System+ in Secure Settings.
But whatever i tried, i could not get System+ detecting root in Secure Settings, also not when trying a few fixes i found on the internet (ex: https://dammit.nl/20160406-how-to-f...oid-devices-with-supersu-systemless-root.html).
Went back to SU 2.78 but that didn't work our anymore either.
While gathering information (i don't follow the progress on rooting etc... because lack of time) i stumbled on Magisk for doing the root.
Unrooted SU and re-rooted with Magisk 14.2
Then System+ in Secure Setting could be enabled again and i could toggle NFC through Tasker again without issues.
But, tapping on the Power Toggles NFC symbol still brings me to the Nougat settings page to set NFC from there (and then the Power Toggle NFC status isn't updated) instead of toggling NFC direct like it used to do before with SU 2.78 (on Marshmellow and the first install of Nougat with SU 2.78).
Looking for a solution for this i found this on the Power Toggles website (http://powertoggles.com/help/?e=17).
It says that you always are directed to the phone's settings to set either GPS or NFC and only works directly if you have root.
Well, it works fine for GPS but for NFC. Power Toggles see's root for the GPS function but not for the NFC one... weird.
Removing Magisk and re-installing it doesn't help, nor does going back to whatever version of SuperUser so i'm still looking for a solution to toggle NFC directly from Power Toggles.

My Tasker Root Support module have been reported to make Secure Settings recognise root. You could give that a try...

Thx, i'll give it try but this then means i have to go back to SuperUser for root instead of Magisk?
The actual problem is that Secure Setting does detect root now when rooted with Magisk but that Power Toggles only partly thinks is not (works fine GPS toggle, not for NFC).
I guess the problem lies more on the Power Toggles part (but then that's a wild guess) which only seems to see half of a root so to say... LOL.

Toggling NFC with Power Toggles works fine for me. With Magisk.
And no... You'll have to stay on MagiskSU to use Magisk modules. SuperSU isn't compatible with Magisk.

Installed the module in Magisk (double checked if it's activated), unfortunaly no joy...
Confession: Far far away in my brain there is a small spark that says that's is't some sort of setting somewhere and that i had the same problem once in the past (long ago) but since my brain is getting rather old and that spark would refuce to become firework...yet.
I did make a small Tasker task to update the Power Toggles bar on changing NFC status. So i can already check on the PT bar in what status NFC is in even if i changed it through regular settings.

Found also this:
Note: starting with android 4.2, system access is no longer required for any functionality. Root should be enough.
If your device is rooted you could install the Power Toggles app as a system app. You can use apps like Titanium backup or /sys/app mover or any similar app for this purpose.
Installing the app as system app, enables protected functionalities like one-click GPS/NFC toggle or Airplane mode toggle.
Wondering if it could help i tried to installing Power Toggles as system app. However, this didn't work. First i used /sys/app mover but this came also up with error: could no remount/system.
Then i tried Titanium Backup but this kept on going in a loop. After stopping TB after +/- half an hour and a reboot the Power Toggles shortcut was gone but that was it. Retried a second a time and this time TB worked itself through the process quickly but Power Toggles wasn't moved and was not a system app. To be continued...

Noticed a second little glitch with Nougat for the Power Toggles, just a NFC now opens de setting instead of toggling, the same happens with the brightness slider toggle (didn't tried that before).
On Marshmellow this opened only the brightness slider, on Nougat is does the same as with the NFC, it opens the settings and goes to the brightness slider there.
After fiddling around with a bit i thought of reversing the firmware back to Marshmellow to try but this came with an error and de Galaxy S6 locked up. Tried a second time, same issue although the firmware should be valid and the checksum is OK (got it from SamMobile).
Re-installed Nougat (a 1st update now), but the Power Toggles still open settings for NFC and Brightness Slider.
Workaround for the Brightness Slider is using a widget to open a 3th party brightness slider. This works noce but the Power Toggles bar is not as nice (even icons) as before.

Are you sure that Power Toggles have been granted root access? Check the superuser section of the Manager...

Yes it has, just double checked on the SU settings in Magisk.
If it doesn't, tapping the GPS/Location or Mobile Data symbol on the Power Toggles bar also opens up the settings pages like with NFC and the brigthness slider.
And whan it has been granted root access, it doens't do that for GPS/Location or the Mobile Data toggle but still for the NFC and brightness slider. That's the big issue. Whay does it work only partially? It would be easier to solve it was the same for every toggle for which it needs root access.

Like I said previously, there are no such issues on my side with Power Toggles...
Toggling NFC and bringing up the brightness slider works without a hitch.
There must be something about your setup.

Didgeridoohan said:
There must be something about your setup.
Click to expand...
Click to collapse
That's what i'm still thinking too but can't pinpoint it (for now).
I'll keep on diggin'...

Managed to make the Power Toggles app a system (with Titanium Backup) but... no joy.
Unrooting makes every toggle that has no direct action go through the settings page as it is intended to do, rooting again still leaves the NFC and brightness slider in an unrooted action state.

Related

Functional Hotspot Toggle???Using Tasker???

Has anyone found a hotspot toggle that works reliably? Neither Power Toggles nor Widgetsoid are able to turn it on, seemingly because the phone needs to verify the service. They can turn it off ok. It is one of the little annoyances that seem to really bother me. Once in a while I saw it turn on successfully but usually I have to go into settings.
I like Power Toggles design and features but I'd jump ship for this toggle. I'd prefer a widget that allowed multiple toggles on a bar style set up, but a stand alone widget could work
https://play.google.com/store/apps/details?id=com.erez.hotoggle
try by this apps.
Kael ruch said:
https://play.google.com/store/apps/details?id=com.erez.hotoggle
try by this apps.
Click to expand...
Click to collapse
Thanks for the recommendation.
Tried it, but it doesn't work as I hoped. It is primarily a shortcut to the settings menu. I am seeking a one touch hotspot widget, like Power Toggles and Widgetsoid were on my last Android phones. With previous phones I could have a switch that turned hotspot on and off without entering settings; I rarely used the setting menu, as I should be able to access the most frequent things like brightness, hotspot, and sound without going into the menus.
Since NO play store toggles seem to work I turned to Tasker. I've been using Tasker on and off since it came out. Usually for simple tasks like this toggle. However I cannot get Tasker to do it either. The toggle seems to work to switch the setting but the authorization delay before the phone turns it on seems to mess it up.
Any ideas?
+1 would luv a solution.
10 char
If you're rooted, you can get the stock touchwiz hotspot toggle back (that should be in with the quick toggles on the notification pane) with a little digging.
This is the thread I went to to get the mobile data toggle back, but the same works for the hotspot toggle:
http://forum.xda-developers.com/showthread.php?t=2721550
Basically you need to get sqlite and use it to modify values in your settings.db file. Follow his instructions, but instead of adding MobileData; add WiFiHotspot; (case sensitive and don't forget the semicolon)
brivette007 said:
If you're rooted, you can get the stock touchwiz hotspot toggle back (that should be in with the quick toggles on the notification pane) with a little digging.
This is the thread I went to to get the mobile data toggle back, but the same works for the hotspot toggle:
http://forum.xda-developers.com/showthread.php?t=2721550
Basically you need to get sqlite and use it to modify values in your settings.db file. Follow his instructions, but instead of adding MobileData; add WiFiHotspot; (case sensitive and don't forget the semicolon)
Click to expand...
Click to collapse
That's buggy as well. It works great for data and the other toggles work great as well, just not the hotspot. That's probably why AT&T disabled the toggle from original firmware. The toggle was actually there when I only flashed the AP file from the firmware, but disappeared after the other files were flashed.

XPosed, What works and what doesn't

I wanted to start a thread to give and gather information with the community on what works and doesn't with XPosed framework and Wanam XPosed. Please add any other information on what works and doesn't if you have been able to verify.
So far I've verified a few things work on the T-Mobile Note 4.
XPosed Torch
YouTube AdAway
XPosed Torch
In Wanam XPosed I have verified the following working for me.
Hide SFinder bar
Hid Battery icon
Change/Hide Carrier Label
Enable 4 way reboot menu
Screenshot / Power menu
Fake System Status
Themes (make sure you turn each on that you use)
Disable Secure Storage
Raise SMS and MMS limit
Wanam XPosed Setting that are not Working (that I've tried).
Lockscreen Flashlight
Home button long press
Disable SEAndroid
I have actually removed XTether and gone with Wifi Tether Router, as it seems to be working smoother.
Here a Link for Wifi Tether Router:
https://play.google.com/store/apps/details?id=net.snclab.wifitetherrouter&hl=en
A lot of the theme color changes work, though i can't seem to get the handle to change color when selected (the bar when you pull the notifications open).
The following ones not previously mentioned works for me:
AudioPrivacy
DisableBatteryFullAlert
Network Speed
NotifyClean
Wanam Lockscreen ==> "Turn on screen when unplugged" does not seem to work properly.
"Hide WiFi notification" is not working
I've been playing with the Theme colors this morning and found the little 'ON' button hiding at the top right. I am working out which panel/icon/text is what exactly as it's a little overwhelming trying to do it all at once. I recommend only changing one or two at a time and then rebooting to see how the changes work for you.
Hi. Thanks for this thread. I was wondering if you could modify your OP to include what modules are not working as well and encourage others to verify. This might be useful for checking.
Am using CM11 on a LG Optimus e970. Tried to use hangout and lost mobile network tube killed connection and erased apn settings.
Sent from my LG-E970 using XDA Free mobile app
mscion said:
Hi. Thanks for this thread. I was wondering if you could modify your OP to include what modules are not working as well and encourage others to verify. This might be useful for checking.
Click to expand...
Click to collapse
I've been gathering some information on what is and isn't working. I will update the post once I get a few more things confirmed.

[SOLVED] How to get pre-Lollipop features back

And get rid of a few annoyances in the mean time?
EDIT: SOLUTION it cost me half a sunday if not more.
I have a stock Moto X 2013, Europe version. I was very happy with it, apart from a few minor annoyances. Untill I received the Lollipop update months ago.
Missing features or new annoyances since Lollipop:
Wake display by waiving your hand. This was in my opinion a killer feature.
SOLUTION: This website which presents a solution using TASKER. Untested
Shutdown menu - extremely annoying if you just want to reboot
Enable flight mode via Shutdown menu, since the menu is gone, you miss this option as well
Mute phone with 1 button, the volume down button. The alternative, selecting MUTE also disables screen or glow notifications. There is NO way to only mute sound/vibration a Moto X 2013 with Lollipop. You have a SMARTphone that cannot be muted like any other phone!
Bluetooth and mobile data toggles have been removed. OMG even Windows Phone 8 has it.
Lockscreen: swipe to right for camera. Gone.
White popup (general Lollipop annoyance): if you swipe it away, the notification is gone from the bar, you cannot read it/respond from the notification bar after swiping it away.
Minor but not dealbreaker features I would like to have: hide NFC and Bluetooth icon in the notification bar, be able to hide app icons and/or rearrange them in the app drawer.
What do I need to do to get all these features back? I want to stick to the stock experience as much as possible. Custom ROMs with tons of customisation features is not what I am waiting for. A custom ROM with near-stock experience and fixes for the issues mentioned above would be welcome.
But if it is possible to solve all of them with XPosed and/or Tasker, that would be fine. Unfortunately I searched these forums for 3 days now and I cannot find a dedicated Xposed topic with this info (there is 1 but it has little useful info). I hope others have a similar experience and found a solution!
zilexa said:
And get rid of a few annoyances in the mean time?
I have a stock Moto X 2013, Europe version. I was very happy with it, apart from a few minor annoyances. Untill I received the Lollipop update months ago.
Missing features or new annoyances since Lollipop:
Wake display by waiving your hand. This was in my opinion a killer feature.
SOLUTION: This website which presents a solution using TASKER. Untested
Shutdown menu - extremely annoying if you just want to reboot
Enable flight mode via Shutdown menu, since the menu is gone, you miss this option as well
Mute phone with 1 button, the volume down button. The alternative, selecting MUTE also disables screen or glow notifications. There is NO way to only mute sound/vibration a Moto X 2013 with Lollipop. You have a SMARTphone that cannot be muted like any other phone!
Bluetooth and mobile data toggles have been removed. OMG even Windows Phone 8 has it.
Lockscreen: swipe to right for camera. Gone.
White popup (general Lollipop annoyance): if you swipe it away, the notification is gone from the bar, you cannot read it/respond from the notification bar after swiping it away.
Minor but not dealbreaker features I would like to have: hide NFC and Bluetooth icon in the notification bar, be able to hide app icons and/or rearrange them in the app drawer.
What do I need to do to get all these features back? I want to stick to the stock experience as much as possible. Custom ROMs with tons of customisation features is not what I am waiting for. A custom ROM with near-stock experience and fixes for the issues mentioned above would be welcome.
But if it is possible to solve all of them with XPosed and/or Tasker, that would be fine. Unfortunately I searched these forums for 3 days now and I cannot find a dedicated Xposed topic with this info (there is 1 but it has little useful info). I hope others have a similar experience and found a solution!
Click to expand...
Click to collapse
This is a question, shouldn't it be in the Q&A?
1) This can be restored by flashing the 4.4.4 firmware
2) Xposed -> GravityBox (Power)
3) Xposed -> GravityBox (Power)
4) Tasker?
5) Xposed -> GravityBox (QuickSettings), or if you mess with the settings for either of those they may pop up in the quick toggles after some time
6) Xposed -> GravityBox (QuickSettings)
7) Xposed -> GravityBox (Notification Ticker)
Status bar icons can be hidden in GravityBox (Statusbar)
The drawer changing can be done with XGELs (Google Experience Launcher)
If this information helped you get it working, be sure to pay it forward by donating if you can
I am definitely going to unlock bootloader, root and install Xposed, see if I can get all of this back. Saves me the risk of potentially unstable ROMs and saving a lot of time testing different ROMs. Thanks a lot!
And yes, I believe projects like Xposed absolutely deserve a donation. I just finished flashing my own HTC One M7, it will also have Xposed (first time going to use it). The Motorola is owned by the lady. I will definitely donate if it works for me.
Wave-to-wake is present in some roms, for example the modded stock rom
There is also the lockscreen with the swipe for the camera.
In order to modify the power menu, you can use APM+.
For the toggles use Gravity Box.
aledex said:
Wave-to-wake is present in some roms, for example the modded stock rom
There is also the lockscreen with the swipe for the camera.
In order to modify the power menu, you can use APM+.
For the toggles use Gravity Box.
Click to expand...
Click to collapse
Good to know, but why would I go to all the trouble to install that ROM (which would include wiping my phone) if I can reach all those goals with XPosed/GravityBox
I have stock Lollipop 5.1 European version about:
5 - bluetooth toggle exists, IIRC it only appears if you use it; mobile data toggle also exists, just need two clicks - one on mobile data tile and one on toggle
6 - don't know about secure screen options but if you don't use password/pin/other you can swipe left for camera and right for dialer
7 - you can swipe that popup up to just hide it and without dismissing or use one of this app to remove/modify them "Heads-up Notifications" "HeadsOff - TickerOn" even without root
I believe that the Nexus Experience rom (NX ROM) offers most, if not all of the features that you're looking for, and it offers a very stock experience. The only reason that I don't run it is because I've grown accustom to tapping gently on my phones shoulder when it's sitting on my desk to activate the Active Display to see what time it is or what notifications I've been ignoring. With NX ROM, Active Display works great, but it's not as sensitive. So I have to tip my phone up, or sideways, to about 15 degrees before Active Display activates with. A very minor issue, but I'm very picky.
As far as I remember, it has the hand wave feature, power off/reboot/airplane mode menu, all kinds of toggles, and I believe volume down to mute as well. It doesn't do swipe right for camera, but you can swipe from bottom right corner, or from bottom left (customizable) to activate the camera. Not sure about the white popup thing because I didn't use it that long.
Thanks for all the suggestions.
I am extremely annoyed by Google removing useful functionality, harming productivity and introducing new design which is clearly not meant for OLED screens (all white). But with all these suggestions I can hopefully stick with the Moto X for a long time, since no brand but Sony will bring us high end <5" phones.
Bomberlt said:
I have stock Lollipop 5.1 European version about:
5 - bluetooth toggle exists, IIRC it only appears if you use it; mobile data toggle also exists, just need two clicks - one on mobile data tile and one on toggle
6 - don't know about secure screen options but if you don't use password/pin/other you can swipe left for camera and right for dialer
7 - you can swipe that popup up to just hide it and without dismissing or use one of this app to remove/modify them "Heads-up Notifications" "HeadsOff - TickerOn" even without root
Click to expand...
Click to collapse
Also have the European version, but I have a completely different experience. Swiping heads up notification always removes the notification from the statusbar (on all Lollipop phones, not just Motorola). On my HTC One M7 with GPE+ ROM I could lower the popup to 1sec allowing me to access the notification in the statusbar when needed. Works fine.
Another Lollipop bug (not even fixed in Android 6.0.1) is that the dialer shows ALL contacts of ALL your accounts (Google, Exchange, Outlook, Facebook, Skype etc) regardless if they have a phone number or not. The Contacts app does allow you to select specifically which contacts to show per group per account. In 4.4.4 this also applied to the dialer, since 5.0 it does not anymore. Google it and you will see people going nuts about this. A Google employee replying it will be "fixed" in M.. which is nuts since most phones with this issue will never receive an M upgrade.. also, now that M is available for Nexus, it's not fixed. The only solution: find a better dialer in Play Store.. this nums me completely... a phone OS should have at least a good dialer.. and apart from this issue the dialer works fine.
SOLVED
SOLVED:
Documentation + all links below in case anyone or myself ever need to do this again.
The most important part explained in detail:
- uninstall any phone drivers from other phones, uninstall Android SDK etc
- install Motorola USB drivers (Motorola Manager)
- install Minimal ADB & Fastboot in C:\adbfb and install mfastboot in that same folder, use mfastboot instead of fastboot. Scroll down in the Minimal topic to find the link to the Fastboot guide. It lists the command to flash recovery (TWRP): NOTE !!! unplug the phone from the PC right after flashing recovery and use the volume down button to scroll to Recovery in Bootloader, use VOLUME UP to select recovery after uplugging, not the shutdown button and do not reboot first (I used shutdown button and rebooted and spend 2 hours figuring this out)!
- copy all required files (the ROM plus its addons) to c:\adbfb.
- Flash using TWRP, first the ROM, then the addons, then factory reset via TWRP.
Short overall steps:
1. bootloader unlocked via the Motorola site (official method)
2. installed TWRP 2.8.6.0 (the newer one has an issue)
3. installed the modded/debloated stock ROM
4. also installed all the addons for that ROM, listed in that same first post.
5. After first boot and initial setup, Copied Xposed Installer, AdAway and installed them via Amaze File Manager (Play Store).
6. Installed the Xposed modules: GravityBox, Moto Checkbox, Sensify, BTAudio. Used GravityBox and Moto CheckBox to get most features back and personalise Quicksettings and some other great tweaks.
7. Used Sensify to install the HTC Sense Launcher (read the first post to install the correct version!!) which is basically stock launcher WITHOUT persistant Google Search Bar WITH ability to rearrange/group/hide apps in the app drawer and with black background, good for our OLED screen. No free launcher in the Play Store is as simple and plain as this one with these features (Nova Prime can do it but it costs €5 and adds a huge load of features I never need).
8. Wave-to-Wake is still not present in the debloated ROM but I will use the Tasker workaround. Haven't tested this yet.
9. To get the maximum out of your battery and have apps that are easier on the eyes, create a backup using TWRP and carefully follow the instructions of Team Blackout (Black Chrome, Black Calendar, Black Hangouts, Black Keep, Black Whatsapp etc). Haven't tested this yet.
10. Play Store > Settings: disable auto-update in Play Store, also disable the notification of updates.

Any solution to disable system bar?

Hey,
We need a solution to disable or hide a system bar on a rooted Android device (rooted with Magisk). Example device is fiio m11, android 7.0.
The end result requires that user would be completely unable to access the notifications/preferences buttons that are visible when you swipe down the system bar.
Also a basic on/off mechanism controllable on android app (basic checkbox on/off).
Any solution is ok:
completely hide system bar
draw something on top of system bar in order to disable swipe down
leave system bar visible but disable touch (disable swipe down to open notifications list)
Do you have any suggestions?
Cheers!
Hi,gintrux. How did you root your device . As far as I know, when I get into the fastboot my ADB cant find any fastboot devices,
Where did you find the fastboot device of FIIO M11. And we didnt have any rec like TWRP for FIIO M11 how did you install the
magisk?
I also faced your problem ,root is just the frist step. I will search it in XDA and others web. If I find anything ,I will share with you.
gintrux said:
Hey,
We need a solution to disable or hide a system bar on a rooted Android device (rooted with Magisk). Example device is fiio m11, android 7.0.
The end result requires that user would be completely unable to access the notifications/preferences buttons that are visible when you swipe down the system bar.
Also a basic on/off mechanism controllable on android app (basic checkbox on/off).
Any solution is ok:
completely hide system bar
draw something on top of system bar in order to disable swipe down
leave system bar visible but disable touch (disable swipe down to open notifications list)
Do you have any suggestions?
Cheers!
Click to expand...
Click to collapse

[SOLVED] Why does my phone not unlock on 47.1.A.16.20 with Xposed?

[FOR REFERENCE ONLY]
Problem solved!
The confounding variable was NOT Xposed Framework, but conena's Gesture Control app that was set up to use Immersive Mode to hide the navigation bar. And according to this post that I landed on purely by chance, if you don't exempt the Lockscreen Settings app, it causes all these problems.
Note that this problem has nothing to do with the app, it's the Immersive Mode setting to blame, on which any setting change at all will cause these same problems (to be fair, conena's app does preemptively discourage this)
Solution
Use a Substratum overlay to hide the navbar instead; do NOT use GravityBox to do that by setting navbar height to 0, or qemu.hw.mainkeys=1 in build.prop (which doesn't work, BTW). Next, backup your gesture bar data and wipe the data of the app, then restore the bar data – just don't fiddle with that Immersive Mode setting again!
Well, some explanation is in order because it wouldn't make for a great thread title:
I am running the last stock Oreo build on this G8441, which is 47.1.A.12.20, for the primary reason of being able to use rovo89's Xposed Framework because the original XPrivacy module that's vitally important to me does not run on any of the EdXposeds or LSPoseds.
Using systemless Xposed with the latest Magisk version (and older ones too, nothing changes) I find that if I were to set a lockscreen to anything other than "None" and reboot, I will have times where I simply can't see the display when pressing the power button -- but weirdly enough the touchscreen still keeps taking touch input! The only way around is to remove the lockscreen, reboot, then set your locking method and try not to have it restart for any reason.
It's quite obvious that systemless Xposed is causing this problem (Xposed can't be installed normally on this firmware version) because this problem can be reproduced even without any modules active. But I'm at a complete loss as to what's actually causing this lockscreen interference, because I've tried taking system logs with and without Xposed and there's simply nothing at all different except it taking insanely long times for the display to activate upon unlock (but the touch input working just fine for some reason?) and there's a small, dim red LED near the proximity sensor that stays stuck as long as the display is.
Please help me, I'm absolutely out of ideas -- and no, I can't upgrade to Pie, I have to stay on Oreo for the sake of the XPrivacy module.
So it seems like 47.1.A.12.75 is the last problem-free Oreo version for normal Xposed Framework, and I wouldn't mind using that, if it weren't for the fact that there doesn't seem to be any VoLTE-activating SIN file for India for it below 47.1.A.12.270. There's a 2G phaseout in progress with the largest carrier and it's only a matter of time before there'll be no fallback network and I'll have to have VoLTE at any cost.

Categories

Resources