I'd used Power Toggles widget (https://plus.google.com/communities/102323355946196101412) on my M7, but alas the various toggles don't work properly in Marshmallow on my X Pure 2015. What I'm looking for is a quick method of toggling Wifi, BT, Tethering and GPS individually without having to pull down the notification drawer. I'm not rooted, but if root was required I'd be motivated to root.
Power Toggles works here. In what way is it not working for you?
m+a+r+k said:
Power Toggles works here. In what way is it not working for you?
Click to expand...
Click to collapse
I discovered that when I was stock and unrooted, I was unable to toggle location properly, same with some of the other components. I was finally able to get it work work, but rooting, but also turning Power Toggles into a system app. Not it works properly.
some work some dont
I have the same issue here.
DATA LOCATION and HOTSPOT not toggling. just sits at the orange (processing) point.
all others (that i use) work fine - blue tooth, screen timer sync and wifi works np
running - resurrectionremix 5.6.5 2016.03.25 ktle
boeffla 3.0bata20
Galaxy s5 900w8 rooted (obv)
Same issues. It's taking me to all the setting screens now vs changing them on the fly. So no quick turning off/on or changing brightness setting etc.
Sent from my Nexus 6 using Tapatalk
I believe you have to be rooted for power toggles to control things like NFC, Bluetooth & maybe location. Not sure which one it requested it for but I know it has su privileges on my phone.
Hi,
I have been using power toggles for quite some time. I like the feature of unlocking screen whenever I want without typing my PIN( attached file).
In lollipop works perfect, but in marshmallow not. My phone is rooted. Any advice?
Related
1. There is no way to sync the clock to any internet time.
2. When the battery is fully charged, the screen turns on from standby (and stays on until the pre-set time-out). This is a problem if you leave you SGT plugged in at night. The screen will turn on in the middle of the night, and possible wake you up if you leave it by night table.
3. Bluetooth tethering for internet access does not work. Using my iPhone (with a legit tethering plan), I can connect to SGT via BT. The internet setting actually recognized BT was connected. A blue square icon was also shown in the lower right corner. However, no data was transferred.
4. Launcher crashes. Regularly about once every 1-2 day, Launcher crashes; i.e., pressed the 'house' icon then a blank screen was shown. Same problem with ADW launcher. The only solution was to reboot (like working with Windows computers, needs constant rebooting).
ikeny said:
1. There is no way to sync the clock to any internet time.
4. Launcher crashes. Regularly about once every 1-2 day, Launcher crashes; i.e., pressed the 'house' icon then a blank screen was shown. Same problem with ADW launcher. The only solution was to reboot (like working with Windows computers, needs constant rebooting).
Click to expand...
Click to collapse
The only consistent crash/force close I have ever had is with the Google Listen app. I've never had a problem with the stock launcher, unless we count that annoying WiFi hang thing. But, that doesn't require a reboot either. Maybe you have defective hardware; can you return/exchange it for a new one?
Sent from my GT-P7510 using Tapatalk
1. If your tab is rooted there is. Get one of the ntp apps like ClockSync from the market.
2. No idea how to disable that. My phone does the same thing but the screen is so small that it didn't bother me much. The tablet is another thing, it lights up the whole room, really annoying.
3. Won't help you much when I tell you that bt tethering works great with my Galaxy S via the bt pan profile. All I have to do is enable bt, click the little wrench next to the Galaxy S and enable tethering. Maybe you have to enable something on your iPhone?
4. Never happened to me. You should try to set up your homescreens from scratch.
Btw. you might want to update your pc to something newer than win98 if you really believe in your comment about windows PCs.
Hi there,
I installed CM10 (thanks a lot for it by the way) this morning and it seems my display sometimes just activates without reason. At first I only noticed the device being extremely warm, so I check battery usage and 92% of it have been "display". The device went from 95% to about 50% in a matter of a two or three hours with me not using the tablet at all in that time. When I checked again a little later, the display was active, although I am sure I had sent the device to sleep mode.
Also, here are two features I would like to request:
1. Please add a way to rotate the lockscreen
2. Please add Mobile Data as a switch for the quick settings (the one you get to by "clicking" the clock). It is rather annoying to go through the menu to activate / deactivate it...
The.Vortex said:
1. Please add a way to rotate the lockscreen
Click to expand...
Click to collapse
OK, found the fix for that problem... the other one still stands
And I have got an additional issue now:
my Mobile Data Connection doesn't work. My carrier is o2 Germany and the stock ROM had some issues with that carrier as well a while back. Maybe it is the same problem?
For now I am switching back to stock, without mobile data, the tablet is only half as usefull, even with the otherwise better ROM
Add your APN Setting manually and it works nice. They are in the 3G Settings. I even had to just add a almost empty one to make things wake up again.
The.Vortex said:
Hi there,
I installed CM10 (thanks a lot for it by the way) this morning and it seems my display sometimes just activates without reason. At first I only noticed the device being extremely warm, so I check battery usage and 92% of it have been "display". The device went from 95% to about 50% in a matter of a two or three hours with me not using the tablet at all in that time. When I checked again a little later, the display was active, although I am sure I had sent the device to sleep mode.
Also, here are two features I would like to request:
1. Please add a way to rotate the lockscreen
2. Please add Mobile Data as a switch for the quick settings (the one you get to by "clicking" the clock). It is rather annoying to go through the menu to activate / deactivate it...
Click to expand...
Click to collapse
I have actually experienced the opposite--battery has been outstanding since flashing the ROM. I usually turn on Airplane mode when I am not using the phone, and am certain to turn off WiFi as well. Try that and see if it makes a difference. Also, be sure you are charging with an appropriate charger!
emuandco said:
Add your APN Setting manually and it works nice. They are in the 3G Settings. I even had to just add a almost empty one to make things wake up again.
Click to expand...
Click to collapse
Thanks, that solved the 3G issue and, as far as I can tell after one day, the issue with the screen activating, as well.
For the other point, being able to activate / deactivate the mobile data easily, I found Power Toggle (can't post link, just look for it in the play market or remove the blanks: ht tps://play.google. com/store/apps/details?id=com.painless.pc) which can add a widget to the notification area that works great
You can add more switches to the menu popping up when clicking on the clock. Thats what I did. Its in System -> Notification Bar (Or something like that, I use it in German ^^)
I've been using llama for quite a while with a lot of success on the stock rooted rom. I use multiple locations to control sound profiles, custom actions, etc.
The most important action I use is that once I'm in my "home" area, Wifi is turned on and once connected to Wifi, the phone goes into airplane mode with Wifi kept on and Sipdroid activated. Once I disconnect from Wifi, airplane mode is turned off and mobile service is restored.
This works flawlessly on rooted stock 4.2.1. However, on the CM 10.1 nightlies, llama constantly freezes and force closes and doesn't perform the scheduled tasks. Also, This morning there was some weird interaction with it and CM. My alarm was supposed to go off at 630 am. My internal clock was telling me it should have already gone off I looked at my phone and the CM chronus lock screen clock showed 6:42. I unlocked the phone and the UCCW clock on my home screen also showed 6:42. The system clock on the notification bar, however, showed the time to be something like 6:17. Obviously I was confused. Within seconds the system clock changed to 6:42 and the alarm went off. Curiously, llama was also not on the correct profile.
Anyone have any experience or ideas? I love using both llama and CM but there seems to be something causing problems. I haven't contacted the developer of llama but I don't expect any support for custom roms. I haven't tried it with anything other than stock and CM so far on the Nexus 4.
I've been using llama on the CM10.1 nightlys with no trouble. I had problems with llama profiles a couple weeks ago due to the way JB based roms handle notification and system sounds. I contacted the developer and he was able to send me a custom apk that solved the problems. Those changes have since been folded into a new release that he put on the play store. The developer is very responsive and had no issues with the fact that I was using a CM nightly build.
It sounds like there might be some things happening beyond just llama problems with your configuration, though. The system clock not being in sync with the other apps is very strange. Are you using a custom kernel with CM10.1? I'm using Franco kernel #28 and my phone is rock solid.
machostallion said:
I've been using llama for quite a while with a lot of success on the stock rooted rom. I use multiple locations to control sound profiles, custom actions, etc.
The most important action I use is that once I'm in my "home" area, Wifi is turned on and once connected to Wifi, the phone goes into airplane mode with Wifi kept on and Sipdroid activated. Once I disconnect from Wifi, airplane mode is turned off and mobile service is restored.
This works flawlessly on rooted stock 4.2.1. However, on the CM 10.1 nightlies, llama constantly freezes and force closes and doesn't perform the scheduled tasks. Also, This morning there was some weird interaction with it and CM. My alarm was supposed to go off at 630 am. My internal clock was telling me it should have already gone off I looked at my phone and the CM chronus lock screen clock showed 6:42. I unlocked the phone and the UCCW clock on my home screen also showed 6:42. The system clock on the notification bar, however, showed the time to be something like 6:17. Obviously I was confused. Within seconds the system clock changed to 6:42 and the alarm went off. Curiously, llama was also not on the correct profile.
Anyone have any experience or ideas? I love using both llama and CM but there seems to be something causing problems. I haven't contacted the developer of llama but I don't expect any support for custom roms. I haven't tried it with anything other than stock and CM so far on the Nexus 4.
Click to expand...
Click to collapse
Mendanbar said:
I've been using llama on the CM10.1 nightlys with no trouble. I had problems with llama profiles a couple weeks ago due to the way JB based roms handle notification and system sounds. I contacted the developer and he was able to send me a custom apk that solved the problems. Those changes have since been folded into a new release that he put on the play store. The developer is very responsive and had no issues with the fact that I was using a CM nightly build.
It sounds like there might be some things happening beyond just llama problems with your configuration, though. The system clock not being in sync with the other apps is very strange. Are you using a custom kernel with CM10.1? I'm using Franco kernel #28 and my phone is rock solid.
Click to expand...
Click to collapse
I had the same problems you described back in December when I was running the beta off of the devs site. All seemed fixed when it got released to the play store.
Currently I'm running the CM stock kernel. I haven't made any mods, no theming, etc. It was a clean install with full wipes of everything twice. I flashed it with TWRP 2.3.3.
It is odd that the system clock could be behind the widget clocks. I've seen it the other way around where the widget would be behind the system if waking the phone after being in deep sleep a while. It's more strange that I can't open llama at all when I'm on mobile data now. It will only open when on Wifi. I do have quite a few Wifi dependent actions but since they work fine on the stock rom they should in theory work on CM. Maybe I'll keep testing and try to get a logcat to show something for the dev
I'm using llama for the same purpose as you.
Events:
1. At Home - enable WiFi
2. When your phone connects to %AP% - enable Airplane Mode and enable WiFi // haven't looked into if it's possible to override wifi shutting off upon entering airplane mode in jb4.2 yet
3. When your phone disconnects from %AP% - disable Airplane Mode
4. Upon leaving Home - disable WiFi
I'm using the version available from the market as of yesterday and also see it constantly freezing up while trying to set it up. It's never force quit on me though and comes out of its stall after half a minute or so each time. I haven't tested it extensively yet, but after getting it setup, it seems to be working okay so far. I used to use a battery of other apps to achieve the same thing, but unfortunately the easily accessible airplane mode toggle api is removed from jb4.2 so those apps don't work anymore. I found that llama has a workaround that requires root, so it'll have to do for now.
I too am using sipdroid.
You aren't using llama for anything to do with alarms right? Then it's weird that causes your clock issues. You can try to see if ClockSync, https://play.google.com/store/apps/details?id=ru.org.amip.ClockSync, works on jb4.2. I had to use it on my HTC Sensation because the clock would drift hard when not connected to a cell tower for some reason. I think it might have been related to a specific kernel I was using, but a few times I saw it lose almost an hour in a 24 hour period.
Update: Twice yesterday, I got missed texts and calls (saw them via google voice site on computer). I checked my phone and saw that it was in airplane mode with wifi off. This doesn't even make sense, since wifi is set to only turn off "upon leaving home"
ziddey said:
I'm using llama for the same purpose as you.
Events:
1. At Home - enable WiFi
2. When your phone connects to %AP% - enable Airplane Mode and enable WiFi // haven't looked into if it's possible to override wifi shutting off upon entering airplane mode in jb4.2 yet
3. When your phone disconnects from %AP% - disable Airplane Mode
4. Upon leaving Home - disable WiFi
I'm using the version available from the market as of yesterday and also see it constantly freezing up while trying to set it up. It's never force quit on me though and comes out of its stall after half a minute or so each time. I haven't tested it extensively yet, but after getting it setup, it seems to be working okay so far. I used to use a battery of other apps to achieve the same thing, but unfortunately the easily accessible airplane mode toggle api is removed from jb4.2 so those apps don't work anymore. I found that llama has a workaround that requires root, so it'll have to do for now.
I too am using sipdroid.
You aren't using llama for anything to do with alarms right? Then it's weird that causes your clock issues. You can try to see if ClockSync, https://play.google.com/store/apps/details?id=ru.org.amip.ClockSync, works on jb4.2. I had to use it on my HTC Sensation because the clock would drift hard when not connected to a cell tower for some reason. I think it might have been related to a specific kernel I was using, but a few times I saw it lose almost an hour in a 24 hour period.
Click to expand...
Click to collapse
I have been unable to duplicate the system clock glitch. I don't use llama for any alarms but I do have quite a few time based events to control volume levels and screen brightness. . After further testing, llama seems to do most of the set actions about 80% of the time. Sometimes it will be one of the actions in a string doesn't stick and sometimes it will miss a time based event. For some reason it has consistently missed the event at 11pm when it's supposed to put the phone into silent mode and lower the screen brightness. That time event is based on being in my "home" area, however, usually at that time my other events have been triggered which puts the phone in airplane mode with Wifi. Keeping Wifi on after triggering airplane mode also doesn't happen quite often. I know JB changed the permissions for apps accessing and modifying airplane mode but since I'm rooted and llama was changed to support it, it should work. I think there may be needs to be an option to add additional delays between multiple actions that are triggered by the same event.
Llama still doesn't work with CM. I contacted the dev and he said that the ROM requires additional permission to perform the actions like disabling/enabling wifi and bluetooth...
Boo I love llama.
lilfleck said:
Llama still doesn't work with CM. I contacted the dev and he said that the ROM requires additional permission to perform the actions like disabling/enabling wifi and bluetooth...
Boo I love llama.
Click to expand...
Click to collapse
https://play.google.com/store/apps/details?id=com.arlosoft.macrodroid :good::good:
Hello all, new to this here.
I've had a Note 3 for quite some time and decided to finally give in to all of this rooting.
By popularity, Alliance ROM seems to be the one to go with.
I managed to get the ROM up and running and I must say this is much better than anticipated.
However, I believe I may have found a bug... if not, I must have done something wrong along the way.
In short, the quick toggles do not reflect any changes. If I turn wifi off, it stays bright green as if its on. Same for any toggle. The only one I see change is the NFC and thats when i switch the s beam on or off (even then it doesnt completely gray itself out, it just goes dim green as if it was changing from on to off, visa versa).
I have wiped and reinstalled the ROM twice with no results.
Is anyone else noticing this? Could it be a fluke?
You have to change the on/off colors manually. It's something that they'll address in the next build but it's a known problem. I forgot how right now but. I'll look for you once I get home.
Settings>custom settings>status bar and toggles> toggle options > toggle icon style
And change it to one that works. Toggles should change immediately and if I remember correctly only one set of toggles worked for me.
Now they all work for me.
Try that and report back.
Any one having issues with the LG V20 miniview not working even tho it's enabled . With a big screen phone the mini view makes it one handed operation feature is handy. If it's working . 2nd issuie has anyone been able to get the flash light notifications to work it's under accessibility and hearing options. Thanks
epj said:
Any one having issues with the LG V20 miniview not working even tho it's enabled . With a big screen phone the mini view makes it one handed operation feature is handy. If it's working . 2nd issuie has anyone been able to get the flash light notifications to work it's under accessibility and hearing options. Thanks
Click to expand...
Click to collapse
yes!
I'm doing the swipe thing and it never works. I managed to get it to work ONCE yesterday, but I was in the settings for that feature. After that, even on that same settings page, it has never worked again.
Haven't tried flashlight notification, but I should try it since this phone lacks an led notification.
Sent from my LG-H910 using Tapatalk
I just fixed my issue with the mini-view. Go to settings-Accessibility and make sure Switch Access is turned off. After disabling Switch Access, mini-view works.
I've enabled the flash on notification thing too. So far its working, but I need more time to test (to see if it just stops for some reason).
Sent from my LG-H910 using Tapatalk
I have. Saw an old reddit post for LG v10 that solved it. You need to put your finger on the recent (square) and quickly and lightly flick slightly in either direction. Now it works every time for me. A flick, not a swipe.
spexwood said:
I just fixed my issue with the mini-view. Go to settings-Accessibility and make sure Switch Access is turned off. After disabling Switch Access, mini-view works.
I've enabled the flash on notification thing too. So far its working, but I need more time to test (to see if it just stops for some reason).
Sent from my LG-H910 using Tapatalk
Click to expand...
Click to collapse
I double checked. This is what causes it . Great job spex
Sent from my LG-H918 using Tapatalk
Just a related update in-case Switch Access is off and miniview still isn't working...
This was my case where Switch Access was never turned on, but other apps were. I turned everything off one-by-one and back on again one-by-one and found that "Lookout" (that controls Safe Browsing) was causing my miniview not to work. I now have Switch Access and Lookout both off and it works again.
Hope this helps, too!
kevs888 said:
Just a related update in-case Switch Access is off and miniview still isn't working...
This was my case where Switch Access was never turned on, but other apps were. I turned everything off one-by-one and back on again one-by-one and found that "Lookout" (that controls Safe Browsing) was causing my miniview not to work. I now have Switch Access and Lookout both off and it works again.
Hope this helps, too!
Click to expand...
Click to collapse
This worked for me as well! Thank you!
kevs888 said:
Just a related update in-case Switch Access is off and miniview still isn't working...
This was my case where Switch Access was never turned on, but other apps were. I turned everything off one-by-one and back on again one-by-one and found that "Lookout" (that controls Safe Browsing) was causing my miniview not to work. I now have Switch Access and Lookout both off and it works again.
Hope this helps, too!
Click to expand...
Click to collapse
Thank you. I disabled lookout so all I had to do was turn off switch access and now I have mini view! [emoji482]
Sent from my LG-V521 using XDA-Developers mobile app
epj said:
Any one having issues with the LG V20 miniview not working even tho it's enabled . With a big screen phone the mini view makes it one handed operation feature is handy. If it's working . 2nd issuie has anyone been able to get the flash light notifications to work it's under accessibility and hearing options. Thanks
Click to expand...
Click to collapse
I have the lg v20 and I was having the same problem. The activation zone is very specific. Try swiping from the home button past the left edge, and I mean go off the edge. Tell me if that works for you. Techadict.com
kevs888 said:
Just a related update in-case Switch Access is off and miniview still isn't working...
This was my case where Switch Access was never turned on, but other apps were. I turned everything off one-by-one and back on again one-by-one and found that "Lookout" (that controls Safe Browsing) was causing my miniview not to work. I now have Switch Access and Lookout both off and it works again.
Hope this helps, too!
Click to expand...
Click to collapse
Yeah I just did the same thing and found out that unfortunately ultimate rotation control breaks miniview, oh well at least I know how to make it work if need be anyway but thanks for this because it was driving me crazy!
Sent from a ridiculously modified ColecoVision
Disabled outlook from the start and Switch Access is off, I still can't get the darn thing to work.
Some apps just break it really. I had parallel windows (an app that had an accessibility service and a spot on the screen you'd swipe from to activate) and miniview did not work at all. The activation hotspot didn't cover the navbar but I still couldn't get it to work. After I uninstalled it miniview worked perfectly fine. I dont have to swipe from specifically the recents key or anything like that, it works from any spot on the navbar.
There are quite a few apps that seem to break the functionality I've noticed. One that I used quite frequently was universal copy. Makes me wonder if it's an app that needs an accessibility service to work properly that does it as there was another one that needed it that also broke it
Hi guys. Am new here. Problem with mini view on LG V20 brought me to this thread. I try everything on this topic and nothing. And i give up.
But today i got new patch.
Sofwear version - V10h-AME-XX
Build number - NRD90M
Kernel ver. - 3.18.31.
And everything is ok know.
Jezzivy said:
Hi guys. Am new here. Problem with mini view on LG V20 brought me to this thread. I try everything on this topic and nothing. And i give up.
But today i got new patch.
Sofwear version - V10h-AME-XX
Build number - NRD90M
Kernel ver. - 3.18.31.
And everything is ok know.
Click to expand...
Click to collapse
Have you tried booting into safe mode to see if it's an app conflicting with it?
KUSOsan said:
Have you tried booting into safe mode to see if it's an app conflicting with it?
Click to expand...
Click to collapse
Didnt try that. But thx