Database Users

Can I add a Reboot option to my power menu (Stock Rom)?

I have just updated to 4.3 using the Google Factory images, however, I would like to add a Reboot menu to my Power menu.
Is this possible? I am trying to keep kinda stock, with a few tweaks.
I do have TWRP recovery installed to my recovery partition already!

You can, but it's far more complicated than you'd think. I remember Cyanogen had a post with the code before. It was quite lengthy. Might be easier now, but there's no simple switch.
I just use a script app with widget and use
$ su
# reboot
Then you can select from the home screen
Sent from my Nexus 4 using xda premium

Install Xposed framework and use this module to add advanced power menu: http://forum.xda-developers.com/showthread.php?t=2318311
Sent from my Nexus 4 using Tapatalk 4

[Guide][Working] Add haptic feedback

1st of all I used it in stock rooted 4.2.2 k3 rom with project engine kernel and I don't know about others kernel and roms, so first you have to enable haptic feedback you can do it by es taskmanger and after that install xposed installer enable it and reboot then install xposed addition and don't open just goto xposed installer >module and tick the xposed addiction and reboot then open xposed addiction>buttons>add keys and select any key u want by pressing it then open it and enable force haptic feedback then reboot and enjoy
Update> one more thing I checked that it not working when powersaving mode enable so check this on stock kernel too without powersaving mode may be it works.
Credit>
Justforallfun.grand >he's idea of using xposed addiction.
Sent from my GT-I9082 using XDA Free mobile app

Note= I didn't use it any other rom or kernel so plz don't complain if its not working,
Sent from my GT-I9082 using XDA Free mobile app
Press thanks if I helped you

[Q] Status Bar & Xposed Framework

Ok, so I have been in search of a program to customize my status bar on my Rooted Note 3, but unfortunately it seems my searches keep coming back to the need to download Xposed Framework. This Xposed Framework screwed up my Note 3, when I went to use it to blur out my notification screen app. I had to un-root, and flash the original firmware, and let me say, it was a two day process to get everything back, and I tried to use my backup, with no success. So, is there a way to customize the status bar without using Xposed Framework?
Thank you,
AM

Are you sure you didn't modify anything else? Everything xposed can be undone by disabling modules or in the case of a boot loop you can flash the disable xposed zip in recovery. Once disabled it has no residual effects and you should be able to troubleshoot from there. But keep in mind some modules (gravity box) can be used with touch wiz based roms but not everything is supported
Sent from my SM-N900V using XDA Premium HD app

czach5932 said:
Are you sure you didn't modify anything else? Everything xposed can be undone by disabling modules or in the case of a boot loop you can flash the disable xposed zip in recovery. Once disabled it has no residual effects and you should be able to troubleshoot from there. But keep in mind some modules (gravity box) can be used with touch wiz based roms but not everything is supported
Sent from my SM-N900V using XDA Premium HD app
Click to expand...
Click to collapse
I didn't modify anything, I just rooted and left it at that. My intent was to get rid of all those programs that came permanently installed on my Note 3, and to rid of them by using Titanium Backup. I am willing try it again, this time I am prepared.

The only thing I can think of is that you removed something and it didn't cause a problem until you rebooted. You should probably only do one thing at a time. Remove bloatware and reboot and make sure it's stable and after you have that settled then start customizing
Sent from my SM-N900V using XDA Premium HD app

I never gave it any thought, that I may have deleted a program that played an integral part to the proper functioning of my Note 3. So, therefore I must take what I am doing one step at a time as you suggested czach5932. This was very good sound advise. I am done with my chores of getting rid of the programs I don't want, and the phone is functioning flawlessly, so now I am off to tackle Xposed Framework. Thank you.
AM

That's half the fun. Just always have a backup so when you do mess up just restore and try again.
Sent from my SM-N900V using XDA Premium HD app

Xposed Issues on Nexus 6? Try this! *Not needed on Alpha 2

As of March 8th, 2015, rovo89 has updated the Xposed framework to Alpha 2, removing the need to have SELinux set to permissive.
So me and a few other guys over in the Xposed Thread were having issues getting our Nexus 6 devices to run the new Xposed Alpha properly. It kept throwing out errors that Xposed wasn't installed and modules didn't work. After a bunch of trial and error, we figured out how to make it work (at least for us)! So if you're having similar issues, try this workaround until Xposed is updated to fix this (although it may be a Nexus 6 error only).
Note: Make sure you already have Xposed installed. http://forum.xda-developers.com/xposed/official-xposed-lollipop-t3030118
Here's a list of which modules are working or not working for some people.
Although these modules have been reported to be functional for some users, the modules may behave differently on our device.
Method 1
1. Make sure SELinux is set to Permissive. You can set it to permissive using this root app, if your kernel isn't permissive by default. https://play.google.com/store/apps/details?id=com.mrbimc.selinux
2. When rebooting into your system after setting SELinux to permissive, enable the Xposed modules that you want.
3. From inside the Xposed app, perform a soft reboot.
4. When the device fully boots up, Xposed should now be fully working. If you still have issues, converting Xposed to a system app might help.
Method 2 Thanks to skaforey
1. Download this script from post #65
2. Extract the file to the root of your sdcard.
3. Using a Terminal Emulator, type the following commands:
Code:
su
cd /sdcard/
sh initd.sh
4. Reboot and Xposed should now be working without a soft reboot needed.
Method 3
1. Flash one of the these zips, which does the same thing as Method 2, but easier! Thanks to both 4got and rootSU
Both files do the same thing
Zip 1 (by 4got)
Zip 2 (by rootSU)
2. Everything should be fully working now!
Not all ROM/Kernel configurations support init.d scripts!
Method 4
1. Use a kernel that's been set to permissive by default. Please don't bother/annoy devs to make their kernels permissive.
Here's a version of LeanKernel modified by Imoseyon to be permissive be default.
LeanKernel (Permissive)
2. Everything should be working. Flashing another kernel will disable Xposed again, unless the kernel is permissive or you fallback on other methods.
Method 5 Thanks to flar2 and shivindera.
Required SuperSU to be installed.
This method differs from Method 3 because the script to set SELinux to permissive is located in /system/su.d (instead of init.d) and allows for compability with more ROM/Kernel configurations. This post by flar2 will better explain what this script does.
1. Flash this zip by shivindera.
2. Everything should be working
Note: For advanced users who already have files in /system/su.d/ please remove the "delete" line from the updater-script so as to not lose any of your already pre-existing files.
Please post here if it worked for you. So far for us over at the Xposed thread, it seems to have worked. Thanks guys! Enjoy your modules!

The problem I imagine is that xposed activates on boot before the selinux mode changer changes the permissive flag. The soft reboot doesnt envoke the default mode as a full boot does, so the mode changer app has already done what is needed.. On the n5 we had a permissive kernel by @sykopompos. I imagine if we had that, we wouldn't need the soft reboot. Is there such a thing for the n6?

rootSU said:
The problem I imagine is that xposed activates on boot before the selinux mode changer changes the permissive flag. The soft reboot doesnt envoke the default mode as a full boot does, so the mode changer app has already done what is needed.. On the n5 we had a permissive kernel by @sykopompos. I imagine if we had that, we wouldn't need the soft reboot. Is there such a thing for the n6?
Click to expand...
Click to collapse
I'm sure it could be made. I guess it's up to the kernel devs to make the default permissive.
EDIT: I was reading the Xposed thread, and you're right! Xposed runs at boot, but SELinux Changer sets SELinux to Permissive after Xposed runs, which is why a soft reboot works, because your restarting Xposed while SELinux is at Permissive. So yes, a kernel set to permissive to default will do the trick without this workaround.

Dude this worked! Thanks so much!

Worked for me too!

Worked here!
Sent from my Nexus 6 using XDA Free mobile app

Oh but a full reboot removes it again...

poczynek said:
Oh but a full reboot removes it again...
Click to expand...
Click to collapse
Yes. Read above.

I think Kernel Devs won't do such a thing, flar2 for example said for his ElementalX Kernel he won't set it to Permissive for various Reason. I imagine other Devs have a similar Opinion.
But I'm sure rovo will fix it in time

D-m-x said:
I think Kernel Devs won't do such a thing, flar2 for example said for his ElementalX Kernel he won't set it to Permissive for various Reason. I imagine other Devs have a similar Opinion.
But I'm sure rovo will fix it in time
Click to expand...
Click to collapse
I'm sure he will not sure how though. We can't delay xposed start up because ART is not JiT so all instructions run at boot rather than when you run a "command"

Nope. I did manage to bork my app drawer lol. Might be the theme update though.

negativzeroe said:
Nope. I did manage to bork my app drawer lol. Might be the theme update though.
Click to expand...
Click to collapse
The top picture is normal, working or not...

Yep this made it work. Thanks. However does that mean when we boot we will then have to soft boot to get it enabled everytime until either rovo fixes it somehow or kernel debs set their default to SELinux permissive?

rootSU said:
The top picture is normal, working or not...
Click to expand...
Click to collapse
I also set xGEL to have a 5 column app drawer, no-go.

bmg1001 said:
So me and a few other guys over in the Xposed Thread were having issues getting our Nexus 6 devices to run the new Xposed Alpha properly. It kept throwing out errors that Xposed wasn't installed and modules didn't work. After a bunch of trial and error, we figured out how to make it work (at least for us)! So if you're having similar issues, try this workaround until Xposed is updated to fix this (although it may be a Nexus 6 error only).
Note: Make sure you already have Xposed installed. http://forum.xda-developers.com/xposed/official-xposed-lollipop-t3030118
1. Make sure SELinux is set to Permissive. You can set it to permissive using this root app, if your kernel isn't permissive by default. https://play.google.com/store/apps/details?id=com.mrbimc.selinux
2. When rebooting into your system after setting SELinux to permissive, enable the Xposed modules that you want.
3. From inside the Xposed app, perform a soft reboot.
4. When the device fully boots up, Xposed should now be fully working. If you still have issues, converting Xposed to a system app might help.
PLEASE PLEASE PLEASE post here if it worked for you. So far for us over at the Xposed thread, it seems to have worked. Thanks guys! Enjoy your modules!
Click to expand...
Click to collapse
Its working great for me.

Switching to permissive worked for me. Thank you
Nexus 6

Works now, thank you.

Damn, so I'm the only one that it still doesn't work for?

flonker said:
Damn, so I'm the only one that it still doesn't work for?
Click to expand...
Click to collapse
Are you following the instructions closely? Using g a known lollipop compatible module? Tinted status bar seems easiest test to me.

rootSU said:
Are you following the instructions closely? Using g a known lollipop compatible module? Tinted status bar seems easiest test to me.
Click to expand...
Click to collapse
Tried it with YouTube AdAway, I'll try tinted status bar.

Viper4Android, has anyone managed to get it working?

hey guys, just wondering if there are any viper4android users out there and if anyone has managed to get it working on the N6P

driver wont stick for me. I miss my EQ!

This post helped out in the nexus 5x forums,
Post- http://forum.xda-developers.com/showpost.php?p=63486621&postcount=7

richie.slayer said:
This post helped out in the nexus 5x forums,
Post- http://forum.xda-developers.com/showpost.php?p=63486621&postcount=7
Click to expand...
Click to collapse
Thanks! worked for me.

I was able to get it installed using the steps in the 5X forum, but only works in compatibility mode. Has anyone got it working in normal mode?

edd247 said:
I was able to get it installed using the steps in the 5X forum, but only works in compatibility mode. Has anyone got it working in normal mode?
Click to expand...
Click to collapse
nope... would really really hope someone figures this out. viper is a must have for me. #2 reason to why I must root my phones.

johnp357 said:
nope... would really really hope someone figures this out. viper is a must have for me. #2 reason to why I must root my phones.
Click to expand...
Click to collapse
Yep, mine is running in normal. I do have SELinuxModeChanger set to permissive. Did you try that? Did you disable musicFX? Besides that I did exactly what was listed in the nexus 5x set-up.

veggicide said:
Yep, mine is running in normal. I do have SELinuxModeChanger set to permissive. Did you try that? Did you disable musicFX? Besides that I did exactly what was listed in the nexus 5x set-up.
Click to expand...
Click to collapse
where is the musicFX disable option? looked everywhere on the 6p and couldn't find it??
well, I don't know why but it seems to work now... without locating the musicFX disable option... followed the direction like on the link for the nexus 5 but also installed selinuxmodechanger and set to permissive. that seemed to work.

veggicide said:
Yep, mine is running in normal. I do have SELinuxModeChanger set to permissive. Did you try that? Did you disable musicFX? Besides that I did exactly what was listed in the nexus 5x set-up.
Click to expand...
Click to collapse
I am using systemless root and the selinuxmodechanger app does not work with this root method, so I used the permissive zip from flar2. I disabled musicfx and it still wont work in normal mode
---------- Post added at 09:35 AM ---------- Previous post was at 09:34 AM ----------
johnp357 said:
where is the musicFX disable option? looked everywhere on the 6p and couldn't find it??
Click to expand...
Click to collapse
go to settings, apps, then hit menu in top right, press show system, then scroll to find musicfx, then press disable

[/COLOR]
go to settings, apps, then hit menu in top right, press show system, then scroll to find musicfx, then press disable[/QUOTE]
changing musicfx back and forth didn't change the sound. but I know that the sound changed following the instructions and adding permissive option on selinux so maybe removing the file from the directory affected this?

I also followed the steps from the 5x forum and I am unable to get the driver to stick. I am rooted the non systemless way.

I had to use rootbrowser to delete the audio_effects.conf permanently. Once I did that, it worked
Sent from my Nexus 6P using Tapatalk

rpinnocent said:
I had to use rootbrowser to delete the audio_effects.conf permanently. Once I did that, it worked
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
Where is this file located? Also where is the viper for Android apk located?
Sent from my Nexus 6P using XDA Free mobile app

It works for me in Google Play Music but not in PowerAMP, also only with Compatible mode.
I wish it worked perfectly fine

shinta86 said:
I also followed the steps from the 5x forum and I am unable to get the driver to stick. I am rooted the non systemless way.
Click to expand...
Click to collapse
Same here, can't get the driver to stick

bsg411 said:
Where is this file located? Also where is the viper for Android apk located?
Sent from my Nexus 6P using XDA Free mobile app
Click to expand...
Click to collapse
File is located in system/vendor/etc and the apk is in the OP
Sent from my Nexus 6P using Tapatalk

Does viper4android give us system wide audio control? Such as allowing us to change the gain on the top/bottom speakers?
Edit: Dw I found out it does. Just need to root and get it now then.

I'm having constant problems keeping this working. I did everything told in http://forum.xda-developers.com/showpost.php?p=63486621&postcount=7 yet every other day I get the issue of going into Google Music, playing music, and when I try to go to settings to get to Viper EQ, the music stops and Viper tells me all of a sudden that the driver isn't installed again (when it definitely was and was working fine).
Also, lately when I go into the SELinuxModeChanger app, it shows Enforcing is chosen, even right after I change it to Permissive. It keeps changing back on its own, even after root permissions are granted.
This wasn't happening until recently.
Running Elemental X's kernel if that matters.
Any ideas?

So I couldn’t wait any more so this weekend I rooted and got my Viper ON. Viper is one of the main reasons that I root. This is what I did:
1) I get TWRP and rooted by doing this:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
2) Now that I’m rooted, I get busy box working
3) I didn’t need to change my SEL Mode by doing this.
4) I Boot into TWRP and I flashed the attach zip. “ViPER4Android-supolicy.zip”
5) Disable MusicFX and then I went into system/vendor/etc and killed “audio_effects.conf”
6) Open Viper and install best Driver
7) I had to re-flash the zip 2-3 times without wiping before I got it working.
Now my 6P is on MDB08M, Crypted, enforcing mode with TWRP and rooted with Viper.
edit: here more info about the the attached zip:
http://forum.xda-developers.com/showthread.php?p=61242973#post61242973

boxcar8028 said:
So I couldn’t wait any more so this weekend I rooted and got my Viper ON. Viper is one of the main reasons that I root. This is what I did:
1) I get TWRP and rooted by doing this:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
2) Now that I’m rooted, I get busy box working
3) I didn’t need to change my SEL Mode by doing this.
4) I Boot into TWRP and I flashed the attach zip. “ViPER4Android-supolicy.zip”
5) Disable MusicFX and then I went into system/vendor/etc and killed “audio_effects.conf”
6) Open Viper and install best Driver
7) I had to re-flash the zip 2-3 times without wiping before I got it working.
Now my 6P is on MDB08M, Crypted, enforcing mode with TWRP and rooted with Viper.
edit: here more info about the the attached zip:
http://forum.xda-developers.com/showthread.php?p=61242973#post61242973
Click to expand...
Click to collapse
thanks, this worked great for me but I don't have music fx to disable.