Hi everybody. I'm a newbie with digging deeper into my device. I'm looking for a solution to control buttons backlight. Since P600 doesn't have led for notifications, I'm interested in using hardware buttons for this purpose. Especially I would like to have backlight while I'm connecting the device to the charger. I hate the screen lighten up (especially at night time) when I plug it in, so I disabled this feature, but it disabled hw buttons backlight as well. It happened to me few times that I plugged in the device and I thought it is charging, but I was wrong and I ended up with discharged tablet at the morning ? I have searched through the Internet and found some clues, but nothing worked for me. I tried some apps and even played with Tasker, but since I'm a beginner, I wasn't able to succeed... So I would appreciate any help My device operates on LineageOS 14.1 and is rooted by Magisk
It seems that I figured it out by myself ? I digged bit more into Tasker app, I watched some tutorials and read about running shell commands. Overall it's a quite complicated subject, but for basic purposes it's comprehensible even for me It's all come down to locating proper "brightness" file which is responsible for lighten up capacitive buttons. In case of this device I found it in a different location than in most other devices. Then using Tasker (you need to be familiar with basic operations at least and you need to have root) I set some simple commands to trigger buttons backlight when I plug the device in (I attached a screenshot). I haven't tested other applications of this feature yet, but I belive it could be used in a similar way for other purposes as well.
I described my experiences because maybe somebody would be willing to take advantage of this ?
EDIT: Something went wrong with loading the image so I'm writing commands to run with Tasker:
1. Run shell
Command echo 1 > /sys/devices/virtual/sec/sec_touchkey/brightness
2. Wait
2 seconds
3. Run shell
Command: echo 0 > /sys/devices/virtual/sec/sec_touchkey/brightness
And you have to check "Use root"
Related
I have seen in other threads that people use tasker to turn of their tablet when there is no power, for example when you turn of ignition in cars etc.
I want to do the same, since it will be getting cold here in a couple of months. This together with fastboot, will be good. But i see no option in tasker to turn off the tablet completely when there is no power present?
Anyone want to help me out?
edit; http://forum.xda-developers.com/showthread.php?t=2657308
Here you can see someone used tasker to turn off tablet completely
henrikrox said:
I have seen in other threads that people use tasker to turn of their tablet when there is no power, for example when you turn of ignition in cars etc.
I want to do the same, since it will be getting cold here in a couple of months. This together with fastboot, will be good. But i see no option in tasker to turn off the tablet completely when there is no power present?
Anyone want to help me out?
edit; http://forum.xda-developers.com/showthread.php?t=2657308
Here you can see someone used tasker to turn off tablet completely
Click to expand...
Click to collapse
I hope you're familiar with how Tasker works. If not, please read some basic tutorials.
Create a new profile State->Power->Power
On the State edit leave the Source as Any and tick the Invert box, so this works when it is not charging.
Create a new task and add a new action System->Reboot
On the Action edit view there is a Type selector, when you tap it you're presented with a list of different options, one of those is shutdown, select it and that's it.
alresave said:
I hope you're familiar with how Tasker works. If not, please read some basic tutorials.
Create a new profile State->Power->Power
On the State edit leave the Source as Any and tick the Invert box, so this works when it is not charging.
Create a new task and add a new action System->Reboot
On the Action edit view there is a Type selector, when you tap it you're presented with a list of different options, one of those is shutdown, select it and that's it.
Click to expand...
Click to collapse
Thank you, only problem is system reboot is red here and says unavailable for me, i already rooted using geohots method, do i need to do more?
nvm, i haven't installed superuser
im so stupid
Thank you so much for answering me Really appreciate it
Is there a command I can run in adb-shell or a terminal that will output a list of all the settings which aren't in the GUI menu but can still be manipulated with the "settings put" command? Like "captive_portal_detection_enabled" or "captive_portal_server" for example. Or is there a file somewhere in the rom that lists them all?
At the moment I'm most interested in disabling whatever network-connectivity check is happening for me on mobile data, with AFWall enabled I'm getting a little x on my mobile data icon.
The other thing I'm interested in looking for is a way to completely disable the safe volume warning and anything/everything to do with it.
And in general I would enjoy taking a look at what's available to mess up the rom with.
edit:
I managed to find these lists, only there's nothing about captive portals or volume listed in any of them that I can see. Not sure my little x on the mobile data is the same as captive portal detection for wifi though. Search box on these pages doesn't yield much either (because I don't know what I'm looking for most likely).
https://developer.android.com/reference/android/provider/Settings.Secure.html
https://developer.android.com/reference/android/provider/Settings.Global.html
https://developer.android.com/reference/android/provider/Settings.System.html
edit:
I *think* I've found the safe volume setting - "config_safe_media_volume_enabled" - out of the description of an old xposed module, which calls it a "system parameter" so I ran "settings put system config_safe_media_volume_enabled false" in adb shell. Headphone volume is still initially set to around 75% after reboots, but I've been blasting some loud Venetian Snares breakcore at 100% volume with GoneMad's preamp maxed out and I don't seem to have triggered the popup yet. Not sure though, the xposed module's description says it sets the parameter at boot and the one I set seemed to survive a reboot (it was "null" before I set it to false). Time will tell, I get that damn popup at least a few times a week.
So I know some time ago, this functionality had been hacked using a combination of the NFC LockscreenOFF Xposed module and modification of the NFC apk. Base on what I can find in the forums, this last worked with Lollipop, but there seems to be little or no activity on this front since then.
I'm just wondering if anyone knows of a way to restore this functionality in Oreo, or if the discussion has ceased because there is a simpler, more obvious solution that I can't find.
Essentially, my goal is to have an NFC tag on my phone cradle in my car which facilitates Tasker profiles/tasks for using the phone in the car. My current setup *sorta* works. The tag sets a variable, and when the variable is set and the phone is plugged in, the profiles/tasks execute. When the phone is unplugged, the exit tasks execute, including clearing the variable set by the NFC tag.
The problem is that if I turn the screen off, the process repeats itself the next time I turn the screen on.
Ideally, the NFC tag would be detected even if the screen is off, the entry tasks would run, and the exit tasks would be triggered by the NFC tag being lost (phone removed from the cradle). Because the tag would still be detected when the screen is off, I wouldn't have to worry about the tasks executing again when I turn the screen on. I could skip the variable entirely and eliminate the "powered" condition for the profile.
Any insight on a solution for this would be much appreciated. If this is the wrong section, please point me in the right direction. I searched every applicable forum I could think of, so my apologies if I've overlooked something.
I'm running a Nexus 5X, stock Oreo 8.1, rooted with Magisk and running systemless Xposed. Tasker and Secure Settings are installed, if that matters.
Thanks in advance for any input.
Looking for this as well. Did you ever find a solution?
So after installing Always On Enabler substratum overlay I noticed, that as side effect shows night mode options. For some reason I started looking for more info. We all know this toggle do nothing now, but if I remember correctly we also need android.auto_generated_rro__ to be enabled (or at least be present in /vendor/overlay) to actually run night light. And here's issue when we paste it directly to /vendor/overlay it will it will magically work, but if we just install it, it will show --- instead [ ] in adb shell.
The whole point is to find a way to enable this overlay. In my opinion if we made it run we might get night light on stock. Any thoughts, ideas?
I managed to get Debian booting on my Gemini PDA wifi version pretty easily.
Certainly there are rough edges, but it looks like it will be useful...but for one problem. I can't reliably get it to sleep and wake.
I don't mean the "Sleep" and "Hibernate" options from the "Leave" menu--I have never gotten them to work at all. I'm just trying to get the "Off" feature on the Esc key to work. Or the lid close, either would do.
Trying to reproduce the problem I have had lots of theories of what exactly it takes to make it fail, but none seem to verify. The problem is frequent but erratic.
I do have a clue. The world map screen (the one with the various sized circles) where I type my password tends to do a brightness change; it appears bright, then I think adjusts to the ambient light. In the cases where I see it fail I think it does the same thing, but instead of adjusting to a new brightness it goes black. (No, I can't successfully type my password blind.)
When this does happen, I think the computer is still running, I think I have been ssh-ed in and that was still alive.
Any others had problems with the lockscreen and found what's the problem or a workaround?
Thanks,
-kb
More Info: Network Related
More experimenting and the lockscreen seems reliable as long as wifi is on. If wifi is turned off, it is unreliable. Not 100% failure, but significant.
Suggestions welcome.
Thanks,
-kb, the Kent who wants wifi off to save power.
I can confirm this issue. And Wifi-on does not avoid it, as I had WiFi always on when this happened. Genrally Fn-ESC for screen locking works and unlocking (world map) also. But sometimes, always after longer times of inactivity, the device does not wake up at all. Screen stays black, blind-typing the password does not work, at least the screen stays black. Only solution in this case I found so far is Fn-ESC (aka "Off") until the device is powered off and reboot.
Edit:
Just happened quite shortly after a reboot, so the "always after longer period of inactivity" seems not to apply.
And the UI seems not to work/respond at all. Trying to - blindly, via keyboard - login and shutdown via systemmenu does not work too - typing pwd, Enter, Ctrl+Esc, three times cursor up, one time right, four times down and two times Enter
Partial workround
Using ssh
sudo service sddm restart
gets you to the initial login screen.
As I'm not allowed to post links: See my post on oesf.org forum, topic 35528 for further comments/notes