I know this is probably a very simple question but I have not seen it addressed yet. What's the best way to root the Essential phone? Is there a working TWRP available yet? Anyone have a guide? thanks :good:
There is no public development currently happening.
It seems very quiet in here as far as root goes. I hope some devs are buying this phone.
in another thread there is a link to magisk and rooting w/o a custom recovery, no one has tried to see if it works on our device.
As soon as FedEx gets over this long weekend and gets me my phone, I'll do the Magisk root and post about it here.
Until then, I'm just stuck twiddling my thumbs and doing other stuff.
I wonder if any custom development will become available for this phone. Yeah, we can unlock the bootloader (pretty useless without a custom recovery) and possibly have root via Magisk (which is fine on the stock ROM), but I have a feeling devs may be staying away from the Essential. Whether it's due to the somewhat negative reviews and new Pixels coming out soon.
hx3 said:
I wonder if any custom development will become available for this phone. Yeah, we can unlock the bootloader (pretty useless without a custom recovery) and possibly have root via Magisk (which is fine on the stock ROM), but I have a feeling devs may be staying away from the Essential. Whether it's due to the somewhat negative reviews and new Pixels coming out soon.
Click to expand...
Click to collapse
in order to root w/ magisk via fastboot, we need the stock.img which isnt available.
It is my humble projection that the Essential will soon become one of the leaders in the ROM/development world.
Relax man... I've seen development for far less popular phones that were far more locked down... Most people that ordered don't even have their phones yet though... give it another week or two to pick up. I paid for my order about 2 weeks ago and it's not getting delivered till Tuesday or Wednesday and there are many others who don't even have tracking info yet.
You guys are probably right. Right now I don't even need root. There is no crap Ola I need to freeze with tibu.. I will still root as soon as it comes. This is the first time I bought a phone that did not come from a carrier.. Jeez what a difference
Sent from my SM-T800 using Tapatalk
I want root simply so that I can add LMT pie controls, hide the nav bar and run adaway. Other than that, there's very little I need root for these days.
im looking to root for adaway and volume skip track. other then that i really have no other need to root. TB for apps would be nice as well.
NeutronBomb said:
I want root simply so that I can add LMT pie controls, hide the nav bar and run adaway. Other than that, there's very little I need root for these days.
Click to expand...
Click to collapse
Try Unique Controls (play store) for pie. Nav bar can be partially hidden with an adb code to enable immersive mode, however this seems to cause layout issues because of the odd status bar implementation. Unfortunately this affects LMT, hence my going with a different app for now. I have a Tasker profile going with AutoTools to turn off immersive mode in apps I know don't work, and I'm getting my full screen pie goodness in about 80% of apps.
tardis_42 said:
Try Unique Controls (play store) for pie. Nav bar can be partially hidden with an adb code to enable immersive mode, however this seems to cause layout issues because of the odd status bar implementation. Unfortunately this affects LMT, hence my going with a different app for now. I have a Tasker profile going with AutoTools to turn off immersive mode in apps I know don't work, and I'm getting my full screen pie goodness in about 80% of apps.
Click to expand...
Click to collapse
Yeah I know how to get it all to work without root but its wonky that way.. Need root and SEL set correctly for everything to fully work without the jankiness.
NeutronBomb said:
Yeah I know how to get it all to work without root but its wonky that way.. Need root and SEL set correctly for everything to fully work without the jankiness.
Click to expand...
Click to collapse
Sorry, what's SEL?
tardis_42 said:
Sorry, what's SEL?
Click to expand...
Click to collapse
The main reason that I use LMT or pie controls in general is so that I have a menu button.. mainly so that in chrome I don't have to reach all the way to the opposite corner to open the menu (since I hold the phone in my left hand 99% of the time). The menu button will not work properly on LMT if you do not have SEL set to permissive. I'm not 100% sure exactly what SEL does but I think its like the SELinux security policy for the kernel or rom. Not a dev, my knowledge is limited..lol I just know it needs to be set to permissive for stuff like that to work properly.
The only reason I want root is for themes but if I could just get my hands on a stock vendor image I could just manually install a Substrantum theme.
Sent from my PH-1 using Tapatalk
root & updates
i'm also looking forward to have root, basically for adaway and titanium. but does anyone have an idea if this is going to have an effect on receiving OTA updates? or if root will be lost every time?
filou76 said:
i'm also looking forward to have root, basically for adaway and titanium. but does anyone have an idea if this is going to have an effect on receiving OTA updates? or if root will be lost every time?
Click to expand...
Click to collapse
For ad blocking look up AdClear.
It's an on device VPN that blocks ads. No root required.
V4A or ARISE is a must for me. Especially when coming from the U11's excellent audio performance.
Related
Alright, first of all, this is an internal device, I will not be using these changes on my own device.
We use tablets (previously Galaxy Tabs) in our office for employees to use an internal application. Our application manages its own navigation, and users do not need to access anything else other than the application. I made it a home screen launcher so it's the first thing that loads. On the Galaxy Tab (Android 2.3), I'm also hijacking all the hardware buttons in the device and I can properly secure the device.
However, on Android 3.0, there are no hardware buttons anymore, and you cannot hide the system bar, I have no way to secure the device if the system bar is always there. I understand why it needs to be there, but this is really killing me.
I have 3 options:
Root the device, try to disable the system bar by editing the framework-res.apk --- Already tried this, unsuccesful since I couldn't find anything in there.
Wait for Android 3.0 to drop in AOSP, build my own custom rom which hides the system bar and do my own modifications on it.
Build Android 2.3 from AOSP for the XOOM -- this will be a lot of work, and I would need help, is anyone interested on helping me with this?
Thanks everyone.
velazcod said:
Alright, first of all, this is an internal device, I will not be using these changes on my own device.
We use tablets (previously Galaxy Tabs) in our office for employees to use an internal application. Our application manages its own navigation, and users do not need to access anything else other than the application. I made it a home screen launcher so it's the first thing that loads. On the Galaxy Tab (Android 2.3), I'm also hijacking all the hardware buttons in the device and I can properly secure the device.
However, on Android 3.0, there are no hardware buttons anymore, and you cannot hide the system bar, I have no way to secure the device if the system bar is always there. I understand why it needs to be there, but this is really killing me.
I have 3 options:
Root the device, try to disable the system bar by editing the framework-res.apk --- Already tried this, unsuccesful since I couldn't find anything in there.
Wait for Android 3.0 to drop in AOSP, build my own custom rom which hides the system bar and do my own modifications on it.
Build Android 2.3 from AOSP for the XOOM -- this will be a lot of work, and I would need help, is anyone interested on helping me with this?
Thanks everyone.
Click to expand...
Click to collapse
Downgrading to 2.3 might be your best bet, wish 3.0 AOSP would hurry up, want to get somethings working differently as well myself. Let us all know if you downgrade and how it went! Wouldn't mind trying to sneak the shut off animation onto 3.0 if possible.
kenhunt said:
Downgrading to 2.3 might be your best bet, wish 3.0 AOSP would hurry up, want to get somethings working differently as well myself. Let us all know if you downgrade and how it went! Wouldn't mind trying to sneak the shut off animation onto 3.0 if possible.
Click to expand...
Click to collapse
Yeah, I haven't gotten into it yesterday, but the only thing I'm concerned about running 2.3 on the Tab is the whole issue with Dual-core support, not sure if I would even be able to do it thanks to that, but I'll see. I'm also trying to call a few contacts to see if we can get into some kind of agreement with Moto to try to get the source code early... we'll see...
Have you tried running a different launcher? They allow you to hide system bars on the old android os...might work on 3.0
Sent from my PC36100 using Tapatalk
bwcorvus said:
Have you tried running a different launcher? They allow you to hide system bars on the old android os...might work on 3.0
Sent from my PC36100 using Tapatalk
Click to expand...
Click to collapse
Yeah, that won't work, the system bar is part of the framework, it's very very low level, you can't hide it since it allows the user to navigate through the device. Before 3.0, devices were required to have hardware buttons, that's not a requirement anymore because of this system bar, it will always always be there.
Atrix runs 2.3 and the same processor
destroyerbmx said:
Atrix runs 2.3 and the same processor
Click to expand...
Click to collapse
True, hopefully they release the kernel source soon so I can take a look and see if I can try to make 2.3 work on the XOOM with the same kernel that's working with 3.0.
here is Tegra 2 with many options running various versions of 2.2 and 2.3.
you should reach out to GoJimi over there.
destroyerbmx said:
Atrix runs 2.3 and the same processor
Click to expand...
Click to collapse
I'm pretty sure atrix is running 2.2.
u can't do anything until source drops. You need baksmali for framework and custom recovery to flash.
I think your best bet would probably be changing the DPI settings somehow (Like they did for the HC build on some phones to get the tablet version) and it would cause you to go into the "phone" version of HC (Doesn't have the system bar) then I would say modify the volume buttons and lock button long presses to recreate the home/back/multitasking buttons if you really want them (such as they have done for the i*hone android ports because ios is dumb and has 1 button). Just a suggestion and honestly I have no idea if this would work.
I'm sure the system bar has a process you can kill with root. I know the status bar can be killed this way on 2.3. Watch logcat and see what you can find. Anyone know more on this?
Porting 2.2 from the g-tab maybe. Similiar hardware I think.
Sent from my Nexus One using XDA Premium App
Just installed lcd denisty on mine and put it at 240 from the default 160...the system bar was gone.
bwcorvus said:
Just installed lcd denisty on mine and put it at 240 from the default 160...the system bar was gone.
Click to expand...
Click to collapse
Glad to see it worked now hopefully the OP sees it. GL to all
Sent from my SCH-I500 using XDA App
Could you please check your /system/build.prop to see whether the lcd density app has added any code?
I usually tweak density directly through this file but the code isnt there atm on my xoom.
I tried changing the density yesterday and was disappointed to discover that the LCD density wasn't in the build.prop. adding the line of code didn't work, either.
XOOM'd from the XDA app.
ftgg99 said:
Could you please check your /system/build.prop to see whether the lcd density app has added any code?
I usually tweak density directly through this file but the code isnt there atm on my xoom.
Click to expand...
Click to collapse
Looking at the date on my build.prop it hasn't been modified. And just to be sure i looked through the file, nothing in there.
Huh, I wasn't receiving notifications on email even though I'm subscribed for instant notifications...
anways, will try the density trick, but that seems like a pain in the butt to redo all the layouts in our app, but that is a very very clever idea, might work.
Update: Yes it works, but only if you use one of those apps, not when editing the system.prop file, anyone care to share what's exactly being edited here?
Thanks again!
Update 2: Actually, I had a typo on the line I wrote on the build.prop, if you write 'ro.sf.lcd_density=240' (or whatever density you want to use), push it and reboot, it does work as it should.
how are u going to press "home" or "back"?
xoom doenst have physical buttons like phones.
how do u get back to home screen if u downgrade to 2.x?
What should replace G3 Tweaks/Xposed on Android 5?
On my rooted KK rom, I used several Xposed functions, out of which the most important to me:
- Four options/extended boot menu
- Volume keys skip tracks (RDIO, PANDORA) while screen is off
- More volume steps
Android 5 (ART) currently voids Xposed
Can you guys recommend ART alternatives for the above (APK or Mod)
Thanks
zolom said:
What should replace G3 Tweaks/Xposed on Android 5?
On my rooted KK rom, I used several Xposed functions, out of which the most important to me:
- Four options/extended boot menu
- Volume keys skip tracks (RDIO, PANDORA) while screen is off
- More volume steps
Android 5 (ART) currently voids Xposed
Can you guys recommend ART alternatives for the above (APK or Mod)
Thanks
Click to expand...
Click to collapse
So there is nothing out there yet, u have to wait if rovo89 make xposed ready for ART or alternatives.
Xposed will not work on Android L
Xposed will not work on Android L
Probably it will not be patched.
Let me tell you a story, of a time before xposed (GHAST, yes, for there was such a time!). Back in these dark days, mods used to be done by pulling apart an apk, making modifications in the code and rebuilding the apk to insert into a rom, the problem was these files were device specific, and often rom specific so it made modding very time consuming, and you had to remake a mod for each device and often each particular rom.
Xposed changed this, it patched files on the fly in such a way that it worked on every device and every rom (so long as the file it was patching, and the code it was changing was present).
Now we have no Xposed, we have to go back to those olden times, lets put on our robes and pick up that longsword and fight back.
..... TLDR: There is nothing that Xposed does that cannot be done 'the old way', it is just a far more time consuming process doing it the old way, and because it is now device and often rom specific finding a developer to do it for your device and rom might not be easy.
If there is automated call recording in a custom android 5 rom I will switch instantly.
Most other things are usually fixed by the custom roms as well.
GieltjE said:
If there is automated call recording in a custom android 5 rom I will switch instantly.
Most other things are usually fixed by the custom roms as well.
Click to expand...
Click to collapse
Xposed/G3 Tweaksbox has automatic call recording...
Tweakbox > call settings > Enable auto call recording
Jodsfk421 said:
Xposed/G3 Tweaksbox has automatic call recording...
Tweakbox > call settings > Enable auto call recording
Click to expand...
Click to collapse
I know, that's why I can't switch to 5 yet.
GieltjE said:
I know, that's why I can't switch to 5 yet.
Click to expand...
Click to collapse
Oh, derp. I thought you were looking for the feature. My bad.
GieltjE said:
I know, that's why I can't switch to 5 yet.
Click to expand...
Click to collapse
GieltjE said:
If there is automated call recording in a custom android 5 rom I will switch instantly.
Most other things are usually fixed by the custom roms as well.
Click to expand...
Click to collapse
ACR app records perfectly calls with the G3
zolom said:
What should replace G3 Tweaks/Xposed on Android 5?
On my rooted KK rom, I used several Xposed functions, out of which the most important to me:
- Four options/extended boot menu
- Volume keys skip tracks (RDIO, PANDORA) while screen is off
- More volume steps
Android 5 (ART) currently voids Xposed
Can you guys recommend ART alternatives for the above (APK or Mod)
Thanks
Click to expand...
Click to collapse
There's apps at Google play for almost everything you want.
Quickclick for the music, reboot menu widget for four way reboot, and so on... [emoji106]
For Active Display what's the best app without xposed?
Any replacement for Xprivacy?
What about Appsettings?
this is only reason for I dont like upgrade to 5.
S3V3N said:
Xposed will not work on Android L
Probably it will not be patched.
Click to expand...
Click to collapse
We know that.
Sent from my LG-D850 using XDA Free mobile app
Dude just wait xposed or something similar will eventually come for Android L too..
It's not just exposed. There are going to be a great many apps and tweaks that won't work on 5.0. Some will eventually be rewritten, some do things that might no longer be possible with Lollipop. All we can do is wait, and in the meantime decide whether the benefits of 5.0 outweigh the things we'll lose.
I'm going to hate the absence of Skip Lock, which the developer says can't be made to work on 5.0. That may keep me from upgrading for a while.
meyerweb said:
It's not just exposed. There are going to be a great many apps and tweaks that won't work on 5.0. Some will eventually be rewritten, some do things that might no longer be possible with Lollipop. All we can do is wait, and in the meantime decide whether the benefits of 5.0 outweigh the things we'll lose.
I'm going to hate the absence of Skip Lock, which the developer says can't be made to work on 5.0. That may keep me from upgrading for a while.
Click to expand...
Click to collapse
Well, LG G3 got a built-in lock skipper. I think its code may be studied and exploited for another use.
GTMoraes said:
Well, LG G3 got a built-in lock skipper. I think its code may be studied and exploited for another use.
Click to expand...
Click to collapse
It does? Can it unlock the device when connected to specific WiFi networks? 5.0 offers trusted Bluetooth, but not trusted WiFi, like Skip Lock does, and it also doesn't allow apps to unlock the screen. But my main point was that even if these capabilities are eventually provided, it will take time. Right now "upgrading" to Lollipop will mean doing without a lot of the tweaks and hacks we've become used to.
meyerweb said:
It does? Can it unlock the device when connected to specific WiFi networks? 5.0 offers trusted Bluetooth, but not trusted WiFi, like Skip Lock does, and it also doesn't allow apps to unlock the screen. But my main point was that even if these capabilities are eventually provided, it will take time. Right now "upgrading" to Lollipop will mean doing without a lot of the tweaks and hacks we've become used to.
Click to expand...
Click to collapse
Bluetooth and NFC. It's a new build, of course it has no hacks. Let's just wait to see what will come.
GTMoraes said:
Bluetooth and NFC. It's a new build, of course it has no hacks. Let's just wait to see what will come.
Click to expand...
Click to collapse
Right. But out of the box, 5.0 doesn't allow any app to trigger a screen unlock. A lot of other things have been locked down, too. For the time being, upgrading to Lollipop is going to mean doing without a lot of the tweaks we're used to.
Since HTC forgot to include the button backlight for the capacitive keys, there is a way to enable them, if you have root. I do not take credit for the app, I just happened to realize it works to enable the keys when I was telling another user about it who wanted to disable the backlight on a Sense ROM. I personally don't use the capacitive keys and use the onscreen nav bar, so I hadn't worried about them, but I just discovered this worked by accident.
Install the following app, grant root permission, and select either bright, dim or off and there is a set at boot option in the overflow menu/settings. The lights shut off with the screen. It isn't the perfect fix, but it will give you backlight on capacitive keys until HTC releases an update.
https://play.google.com/store/apps/details?id=org.sleepydragon.capbutnbrightness
Again, this is not my app, and if you want to support the developer, purchase the paid app from the Play Store.
Paid version: ($2 US) https://play.google.com/store/apps/details?id=org.sleepydragon.capbutnbrightness.pro
Developer's xda thread: http://forum.xda-developers.com/showthread.php?t=2496347
Also, thanks to @dragonballz2k for pointing this out, you have to change the SELinux status to permissive using the following app in order for the permissions to be writable. https://play.google.com/store/apps/details?id=com.mrbimc.selinux
Just install the app, grant superuser permission, tap the "Permissive" button and reboot. Just leave the app installed. It will do its thing in the background automatically. (Note: this is not necessary if you are using ElementalX kernel as it already sets the SELinux status to permissive in the kernel.)
As always, any modifications to your device's software are at your own risk. Do not blame anyone but yourself if you break something. Not even your dog. He doesn't deserve it. And if he eats your friend's iPhone, let him sleep on the couch. He is a good dog.
Sent from my brain using human to phone transport technology.
Second post because it is the cool thing to do.
Sent from my brain using human to phone transport technology.
ABQNM said:
Second post because it is the cool thing to do.
Sent from my brain using human to phone transport technology.
Click to expand...
Click to collapse
Didn't work, granted root permission through SuperSU, but the debug log shows files to be modified to be read-only
KrazyKlutt said:
Didn't work, granted root permission through SuperSU, but the debug log shows files to be modified to be read-only
Click to expand...
Click to collapse
Maybe it works because I am running a custom kernel, ElementalX 19.0. It is possible that it has changed the permissions of the necessary files.
Sent from my brain using human to phone transport technology.
ABQNM said:
Maybe it works because I am running a custom kernel, ElementalX 19.0. It is possible that it has changed the permissions of the necessary files.
Sent from my brain using human to phone transport technology.
Click to expand...
Click to collapse
nope, i use ElementalX 19.0 too
KrazyKlutt said:
nope, i use ElementalX 19.0 too
Click to expand...
Click to collapse
So if you tap the bottom (full sun) button in the app it doesn't light up the keys? The debug info shows as read only for me as well, but it lights up immediately for me.
On: http://imgur.com/HdZcSoY
Off: http://imgur.com/TnELt0E
Sent from my brain using human to phone transport technology.
ABQNM said:
So if you tap the bottom (full sun) button in the app it doesn't light up the keys? The debug info shows as read only for me as well, but it lights up immediately for me.
On: http://imgur.com/HdZcSoY
Off: http://imgur.com/TnELt0E
Sent from my brain using human to phone transport technology.
Click to expand...
Click to collapse
no I get a pop-up with an error message, efter that i looked at the log and since it showed read-only is assumed that was the issue, but maybe it's not.
KrazyKlutt said:
no I get a pop-up with an error message, efter that i looked at the log and since it showed read-only is assumed that was the issue, but maybe it's not.
Click to expand...
Click to collapse
Maybe try revoking su permission and then accepting the supersu permission again when it prompts. If not, I'm not sure what the issue could be. I didn't write the app and it seemed to work fine for me, but there is a lot of craziness going on with sysfs security permissions and Lollipop on the m7 and m8. Flar2 (ElementalX dev) is having issues getting a lot of his custom features working properly because of this, but it seems to randomly affect some people and not others. Also make sure you have a current version of busybox.
Sent from my brain using human to phone transport technology.
ABQNM said:
Maybe try revoking su permission and then accepting the supersu permission again when it prompts. If not, I'm not sure what the issue could be. I didn't write the app and it seemed to work fine for me, but there is a lot of craziness going on with sysfs security permissions and Lollipop on the m7 and m8. Flar2 (ElementalX dev) is having issues getting a lot of his custom features working properly because of this, but it seems to randomly affect some people and not others. Also make sure you have a current version of busybox.
Sent from my brain using human to phone transport technology.
Click to expand...
Click to collapse
Figured it out is it is selinux use this app to fix the issue https://play.google.com/store/apps/details?id=com.mrbimc.selinux&hl=en
dragonballz2k said:
Figured it out is it is selinux use this app to fix the issue https://play.google.com/store/apps/details?id=com.mrbimc.selinux&hl=en
Click to expand...
Click to collapse
Oh man. That is it. I completely forgot I had that installed. I had it running for my sound mod and forgot about it. I guess it does other things. Thanks! I will update OP.
Sent from my brain using human to phone transport technology.
dragonballz2k said:
Figured it out is it is selinux use this app to fix the issue https://play.google.com/store/apps/details?id=com.mrbimc.selinux&hl=en
Click to expand...
Click to collapse
Thanks , that solved it for me as well. Does enabling permissive disturb any other apps you have with root access?
KrazyKlutt said:
Thanks , that solved it for me as well. Does enabling permissive disturb any other apps you have with root access?
Click to expand...
Click to collapse
It may actually make some work better. It may actually make some of the ElementalX kernel features work. I have had it installed since last Friday when I installed Project ERA (sound mod) and forgot about it and everything has been running great. In fact, things are working for me that others cannot get to work, even the kernel developer, flar2.
I have actually been talking to him about SELinux status and sysfs permissions in trying to fix some of the extra kernel features.
You just lose the protections afforded by SELinux enforced permissions that prevent other apps from modifying system files. Though KK 4.4.4 GPe did not have SELinux enforced. It was still permissive.
Sent from my brain using human to phone transport technology.
ABQNM said:
It may actually make some work better. It may actually make some of the ElementalX kernel features work. I have had it installed since last Friday when I installed Project ERA (sound mod) and forgot about it and everything has been running great. In fact, things are working for me that others cannot get to work, even the kernel developer, flar2.
I have actually been talking to him about SELinux status and sysfs permissions in trying to fix some of the extra kernel features.
You just lose the protections afforded by SELinux enforced permissions that prevent other apps from modifying system files. Though KK 4.4.4 GPe did not have SELinux enforced. It was still permissive.
Sent from my brain using human to phone transport technology.
Click to expand...
Click to collapse
Thanks for the info, good to know as I been using ElementalX for a long time and it's an awesome kernel.
All you developer are awesome actually, I feel less need every day to buy another Android phone since apart from the m7 bloody annoying buttons for volume and power, with super creations like ElementalX and hopefully in the near future xposed & gravitybox the M7 is a excellent phone. Although with 5.0.1, I really miss long press volume to change track with Gravitybox...
KrazyKlutt said:
Thanks for the info, good to know as I been using ElementalX for a long time and it's an awesome kernel.
All you developer are awesome actually, I feel less need every day to buy another Android phone since apart from the m7 bloody annoying buttons for volume and power, with super creations like ElementalX and hopefully in the near future xposed & gravitybox the M7 is a excellent phone. Although with 5.0.1, I really miss long press volume to change track with Gravitybox...
Click to expand...
Click to collapse
Yeah I miss xposed for a few features, but not enough to go back to the laggy, battery hungry mess that was Kit Kat on the M7. I have already learned to live without it.
As for the volume key to change tracks, there are a few apps. I use this one. It works with Google Play Music, (and it says Power Amp and stock music players, but I don't use those so I can't test them). I can't get it working on Spotify or Rdio, even using the compatiblity modes. It doesn't use long press, but rather a double press of the volume up or down keys, but it is at least something. It doesn't use any extra battery since it only runs when music is playing and the screen is off. https://play.google.com/store/apps/details?id=com.silentlexx.volbtntrackctrl
Sent from my brain using human to phone transport technology.
ABQNM said:
Yeah I miss xposed for a few features, but not enough to go back to the laggy, battery hungry mess that was Kit Kat on the M7. I have already learned to live without it.
As for the volume key to change tracks, there are a few apps. I use this one. It works with Google Play Music, (and it says Power Amp and stock music players, but I don't use those so I can't test them). I can't get it working on Spotify or Rdio, even using the compatiblity modes. It doesn't use long press, but rather a double press of the volume up or down keys, but it is at least something. It doesn't use any extra battery since it only runs when music is playing and the screen is off. https://play.google.com/store/apps/details?id=com.silentlexx.volbtntrackctrl
Sent from my brain using human to phone transport technology.
Click to expand...
Click to collapse
Yeah I use PocketSkip too, used it even in KK too a long time ago before i used GravityBox. PocketSkip is annoying because double press in more difficult in the pocket (with m7 awful volume rocker...) than a long press. Even more annoying is the sudden increase in volume before it change tracks. I mapped volume down in PocketSkip instead for the next song, more easy on the ear to hear a sudden drop in volume than an increase. I've e-mail and asked the author of any plans for long press and/or fixing the increase or drop in volume before skipping, but no response.
ABQNM said:
Oh man. That is it. I completely forgot I had that installed. I had it running for my sound mod and forgot about it. I guess it does other things. Thanks! I will update OP.
Sent from my brain using human to phone transport technology.
Click to expand...
Click to collapse
i will get it a try
Hitch3n said:
i will get it a try
Click to expand...
Click to collapse
If you are running ElementalX kernel you don't need the selinux app as the kernel has already changed the status to permissive. I don't know about other kernels however.
When xposed will be working for android 7.0?
Sadly there is no time frame as to when it will be released. I too am waiting for Xposed for Nougat but in the meantime i can wait.
lets just wait it out, i will defintely need xposed for Nougat, because there is one module which is a must for me.
it is called 'lockscreen disabler' and what it does is, it bypasses the annoying pin code requirement upon reboot when you have fingerprint set.
so it is an amazing module for me, because it never ever will lock the screen ,literally disables lockscreen so whenever you unlock your phone the screen pops on quick just like having no lockscreen set even though you have it set because of the fingerprint feature.
i love to unlock my phone with the fingerprint reader.
hopefully xposed will be compatible eventually.
I've been waiting for Xposed sine DP3 came out, how long does it usually take for a new Xposed version to be made?
Are the developers even working on a nougat version? Not asking for ETA. Just would be nice to know if it's in the works.
Rovo is actively working on it. Be patient, it was months after MM came out that Xposed was released for it. It will be the same for N most likely
From what I heard we wont get it till after 7.1 is released (probably WELL after.) Hes supposed to be pushing out xposed for systemless root first then working on nougat. So theres no timetable but Id be really surprised if it comes by the end of 2016 (hope Im wrong).
Im happy with MM. With android n-ify Ive got the look of Nougat and it now allows Google Assistant to be installed. It doesn't seem like Im missing out on much & I dont need to give up the xposed mods Ive started to take for granted.
siddy95 said:
When xposed will be working for android 7.0?
Click to expand...
Click to collapse
If you are looking for a temporary solution, and like me mostly use Gravitybox tweaks, SAOSP is a very good mostly stock ROM.
Sent from my Nexus 6P using Tapatalk
leondestiny said:
lets just wait it out, i will defintely need xposed for Nougat, because there is one module which is a must for me.
it is called 'lockscreen disabler' and what it does is, it bypasses the annoying pin code requirement upon reboot when you have fingerprint set.
so it is an amazing module for me, because it never ever will lock the screen ,literally disables lockscreen so whenever you unlock your phone the screen pops on quick just like having no lockscreen set even though you have it set because of the fingerprint feature.
i love to unlock my phone with the fingerprint reader.
hopefully xposed will be compatible eventually.
Click to expand...
Click to collapse
Oh thanks alot for suggestion. I am definately going to try this now.
siddy95 said:
Oh thanks alot for suggestion. I am definately going to try this now.
Click to expand...
Click to collapse
it is an amazing module for me because it kills the lockscreens, i love having my phone ready all the time ,dislike the pattern/pin usage evrytime i unlock the phone, and i use the fingerprint reader function which requires a lockscreen, and this module works nicely with it.
when you downloaded it go to the app interface and top option says 'lockscreen type' choose no lockscreen < this kills lockscreen.
lockscreen type - no lockscreen
http://forum.xda-developers.com/xposed/xposed-framework-android-n-t3336369
mcmb03 said:
Rovo is actively working on it. Be patient, it was months after MM came out that Xposed was released for it. It will be the same for N most likely
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=68920271&postcount=86
Hi all! Does anybody know some tweak ui app to force full screen for all apps? Unable to use the whole screen is very annoying. I've turned off status bar due to screen burning after two months, but the upper line is always empty in portrait or landscape mode.
Thanks in advance!
And peace to all.
aae_nsk said:
Hi all! Does anybody know some tweak ui app to force full screen for all apps? Unable to use the whole screen is very annoying. I've turned off status bar due to screen burning after two months, but the upper line is always empty in portrait or landscape mode.
Thanks in advance!
And peace to all.
Click to expand...
Click to collapse
I am researching on this. On A10 you can use the magisk module "none display cutout". After install, in dev settings you have an option to completely ignore the holepunch area and swithching to fullscreen with gmd gestures lite will have truly fullscreen and no icons to burn in. Sadly this is not working on a11. Module will flash, holepunch will be ignored. But fullscreen mode will just turn off holepunch area
Thank you very much!
But I would prefer to not install twrp and not to flash magisk as well due to some reasons.
Just hope if exists some tweak app with adb granted permissions, like those for immerse mode.
Yes, thx,a solution would really be nice. I have been wondering about this.
aae_nsk said:
Thank you very much!
But I would prefer to not install twrp and not to flash magisk as well due to some reasons.
Just hope if exists some tweak app with adb granted permissions, like those for immerse mode.
Click to expand...
Click to collapse
Do not use the below
DO NOT SELECT DOUBLE CUT OUT
DO NOT USE ON BETA
dladz said:
I think you're going to struggle without root, you'd need to change some files in system, without root I don't think you can.
Have you checked on the display cut out in developer options?
Haven't used it but may offer every you want?
Check out the other OnePlus forums, they're longer established and may have mods which can be adjusted for this OS, or possibly it may even work as is..
Hope this helps.
Click to expand...
Click to collapse
Do not chose double cutout. Instant bootloop with no chance of recovery. Don't say i didn't warned you
elmarian756 said:
Do not chose double cutout. Instant bootloop with no chance of recovery. Don't say i didn't warned you
Click to expand...
Click to collapse
Really? I didn't get any of that, tbh though I don't think I actually clicked that one.
Find it hard to believe that OnePlus would leave that in.
Would assume that safe mode would still work.
Are you on stable or beta?
dladz said:
Really? I didn't get any of that, tbh though I don't think I actually clicked that one.
Find it hard to believe that OnePlus would leave that in.
Would assume that safe mode would still work.
Are you on stable or beta?
Click to expand...
Click to collapse
Stable. Mine instantly died after selecting double lol. I was very pissed off but i had a quick backup so didn't took much time messing with it. Ob3 users reported to me in a testing group that innbeta this doesn't happen
elmarian756 said:
Stable. Mine instantly died after selecting double lol. I was very pissed off but i had a quick backup so didn't took much time messing with it. Ob3 users reported to me in a testing group that innbeta this doesn't happen
Click to expand...
Click to collapse
Maybe it's an ob3 issue? Apologies mate, I had no idea.
Updated my original post to avoid it
You can use the adb command to remove magisk modules in case of bootloop caused by this, happened to me on my 8T. Still looking for a working notch killer for a11
samspark said:
You can use the adb command to remove magisk modules in case of bootloop caused by this, happened to me on my 8T. Still looking for a working notch killer for a11
Click to expand...
Click to collapse
could you post this exact command sir? this is one of the biggest things on paranoid about, they're not being a good version of TWRP for 11
There's definitely a lot of dead space up at top reserved for the humongous status bar icons, a good 0.5".
Should have made them smaller and further up the screen. Like others mentioned this task will be probably zero achievable without root etc.
Burt Squirtz said:
could you post this exact command sir? this is one of the biggest things on paranoid about, they're not being a good version of TWRP for 11
Click to expand...
Click to collapse
adb wait-for-device shell magisk --remove-modules
You need to turn your device on after typing that in adb