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?
Related
It is my understanding that some gen8 devices aren't waking up from sleep when they go to sleep in a dimmer screen state. Thanks to a diligent XDA user with a 101, I was able to fix this problem.
To fix this, download SuperDim 1.51dev2 from http://code.google.com/p/superdim/downloads/list
Then go to Menu | Options, and check "Fix no-wake-from-sleep". That's all: it should now work.
My testing indicates that low brightness levels aren't enough to switch the backlight from off to on. So what the SuperDim fix option does is that when the device awakes with a low brightness setting, it first sets 22% brightness, which is enough to activate the backlight, and only then sets the desired lower brightness level.
I reported both the bug and the fix to Archos.
It might be possible to make the fix work without root if there is enough demand.
I would very much like to have a fix without having to root my 101!
I installed and to exactly what u introduced but I still have that issue now. Im realy disappointed. Is there any other methods
yes i also tested it - but somehow i didnt see the feature while waking up - but when going to sleep - this somehow is weird and useless - might be the reason for not working for others
Sleep: press power - screen gets brighter -> get darker -> off
Wake up: press power -> wake up by luck
perhaps recontact the develoeper something might be messed up
(i didnt take the version u mentioned - but the latest maket version wich is newer)
So, let me get clearer on what's happening. You have SuperDim installed, and its "fix wake from sleep" option is activated. And you're still not having the device wake from sleep when the screen is dimmed. Right?
If you can install adb on your PC, or install an ssh daemon on your device and connect to the device via ssh from your PC, you can help me diagnose the problem.
Well I hoped my explanation was clear enough - it is what u said + the point that the function u explained in post 1 doesn't happen while waking up but instead when going to sleep...
Device is on (screen is dimmed, archos option is on) -> press power -> screen gets brighter -> screen gets darker -> off
Device is in sleep -> press power -> wake up by luck
Anyway I got ssh woring thought putty(win) and UD ssh daemon.
ADB is also installed on my pc but i nerver used it
EDIT:
hey - btw i asked u for the cycle funktion some time ago and noticed u implemented it now - and a lot of other things
Thanks for that - somehow i lost track of your app since i had exams
Anyway i just noticed i have the turn-on bug also when I don't use your app sometimes... (even when the screen is not dimmed at all) so there must be another problem also i suppose
Regarding the cycle funktion i noticed a "strange" behaviour:
"night 1" -> 3x cycle -> ends in "day 2" (thast right)
but
"night 1" -> 2x cycle -> "night 1" -> cycle -> ends in "day 2" also and not in "night 2" (so it seems u forgot to ask for the current state while cycling though the modes)
anyway I would be glad if u would make a cycle+ and a cycle-
jw3 said:
I would very much like to have a fix without having to root my 101!
Click to expand...
Click to collapse
PM me your email address. I may have a fix for you.
hello.
I have a similar problem with my GEN 8 A43
I am runing Cyanogenmod bull latest VR since yesterday with GO lancher/
and when i wake up my phone it is only making a sound -"bip" like its turned on, but I dont see anything of the screen...
so the only thing I can do is tern off the device by long press on the power key, and turn it on again...
rarely it is working fine and the regular unlock screen show up...
plese help my to fix this.
thank you !
Moko_Loko said:
hello.
I have a similar problem with my GEN 8 A43
I am runing Cyanogenmod bull latest VR since yesterday with GO lancher/
and when i wake up my phone it is only making a sound -"bip" like its turned on, but I dont see anything of the screen...
so the only thing I can do is tern off the device by long press on the power key, and turn it on again...
Click to expand...
Click to collapse
Have you tried SuperDim, now known as RootDim, and its sleep of death fix option?
Hey,
I upgraded my device from a Nexus 5. In my Nexus 5 I had an option in the Settings to create a schedule for silent times (or priority only). Before I did the switch, I had a setting on to put the device on silent mode at 21:30. Now, in my OnePlus3, I notice that it also goes silent at 21:30 every day (it probably automatically migrated this setting along with the other settings when I first set up the device). But in the OnePlus 3 I no longer have a setting to disable this schedule... This is extremely annoying, because when the device goes into Silent mode I can't even turn up the volume with the volume rocker, I have to physically push the alert slider to "silent" mode and then back to "all notifications" mode.
The device is not rooted and I'd much rather keep it this way if I can.
I hate the fact that there something going on that I can't switch off...
Ideas? Tips? any thoughts will be highly appreciated.
Several people have reported this problem and I have it as well. You are correct that it comes from transferring the settings from your previous phone to the OP3 which has no way to control do not disturb settings through software. None of the suggested fixes have worked for me. My hope was that the new OTA, which apparently had notification fixes would stop it, but it did not. The only thing that has been reported as working all the time is wiping the phone entirely and setting it up as new without transferring your old settings. If you still have your old phone, you could change the settings on it to remove all dnd settings, use it for a bit so that it backs up and then try setting up your OP3 again. I plan on doing that or starting new and fresh later this week.
Edit:
Here's the other thread on this. Looks like the problem exists for people who did clean installs as well. http://forum.xda-developers.com/oneplus-3/help/disturb-settings-t3400979
Had this problem, too. I did transfer the settings from my old phone, but I had no DND settings active on this device (in fact I never ever used DND). The only way to get out of this silence loop was to restart the phone and set the slider to priority and back to all.
daClaus said:
Had this problem, too. I did transfer the settings from my old phone, but I had no DND settings active on this device (in fact I never ever used DND). The only way to get out of this silence loop was to restart the phone and set the slider to priority and back to all.
Click to expand...
Click to collapse
That didn't fix it, the behavior returned after a while.
Apparently this is a big issue:
https://forums.oneplus.net/threads/do-not-disturb-notifications-problem.451989/
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.
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"
I use the left swipe for menus a lot and was really hating the back gesture messing that up. Found https://android.gadgethacks.com/how-to/disable-androids-back-gesture-left-side-make-hamburger-menus-easier-open-0338679/ and worked perfectly. The below ADB code is what I used and assumes you have the Android SDK and ADB set up.
Code:
adb shell settings put secure back_gesture_inset_scale_left 0
You can adjust the sensitivity for each side in settings. This just turns it completely off?
letrain02 said:
You can adjust the sensitivity for each side in settings. This just turns it completely off?
Click to expand...
Click to collapse
Yes and it works perfectly on Pixel 5 too.
Setting lower sensitivity won't disable back gesture.
letrain02 said:
You can adjust the sensitivity for each side in settings. This just turns it completely off?
Click to expand...
Click to collapse
I don't think it turns out all the way, I've had it trigger in apps with no left menu. It's much less sensitive though and the menu will pop out first. I'm thinking of doing it in the right too because it's way too sensitive for the browser I use, which has a ton of gesture controls.
The sensitivity in settings did nothing for me so found this.
brandontowey said:
I use the left swipe for menus a lot and was really hating the back gesture messing that up. Found https://android.gadgethacks.com/how...ide-make-hamburger-menus-easier-open-0338679/ and worked perfectly. The below ADB code is what I used and assumes you have the Android SDK and ADB set up.
Code:
adb shell settings put secure back_gesture_inset_scale_left 0
Click to expand...
Click to collapse
you should mention that others should try -1 or -2 if 0 does not work, 0 did not work for me but -2 seems to have disabled it
bramble with proton rom and kernel
I put -20 on both sides (to make sure it doesn't trigger in the cutout area in landscape mode) and use FNG instead. Works like a charm.
old thread, but this worked for disabling the right-back-gesture on Android 13/Pixel 6
adb shell settings put secure back_gesture_inset_scale_right 0
I use this command to use gesture from 3rd party application, but the original back gesture still working on my vivo x60 pro. Any thoughts please?