Hows do I automatically shut and start my phone at specific times
One option is via Tasker with Secure Settings plug-in, but your phone must be rooted.
Action > System > Reboot type: Shutdown
Change reboot type to Normal if you want the device to simply reboot.
Using an s7edge , says reboot option is unavailable
k****ij84 said:
Hows do I automatically shut and start my phone at specific times
Click to expand...
Click to collapse
k****ij84 said:
Using an s7edge , says reboot option is unavailable
Click to expand...
Click to collapse
You can also use the shell command "reboot" (without quotes). I don't remember properly, but I don't think you have to write "su" before. You can try and if it fails, then write "su" before.
#Henkate said:
You can also use the shell command "reboot" (without quotes). I don't remember properly, but I don't think you have to write "su" before. You can try and if it fails, then write "su" before.
Click to expand...
Click to collapse
You mean "su -c"
And he can simply tick the "Use root" box.
Sorry all this is going over my head , new to tasker , can you please put in a step by step
Any help?
Action > Code > Run Shell
Tick the "Use Root" box and enter this code:
reboot
Yes but my device is unrooted , don't want to root
k****ij84 said:
Yes but my device is unrooted , don't want to root
Click to expand...
Click to collapse
Try it without root.
It might work.
want to see for xperia z3.
snhfa said:
want to see for xperia z3.
Click to expand...
Click to collapse
Dude, just read the other posts of this thread.
You'll have to use a method that mimics human interaction. Give auto tools a try. See this reddit post for pointers.
Related
Hello everyone, I apologize in advance if I've posted this in the wrong section. Ok so here is my problem, I recently got Cyanogen 4.04 (Latest stable release) on my phone. I was gonna try out the overclock app from the App market but it doesn't let me open it because i'm not ROOT. I thought users are always ROOT in modded ROM, are they not? If not then what should I do to ROOT? I used the one click method for root at the begining (to install cyanogen) and Haykuro SPL Update. Thanks.
p.s I am a complete noob so please go slow.
If you have used the 1-Click-Root method, did you follow the steps to type in telnetd using a terminal app? If not then I would go back and re-trace your steps.
NeoBlade said:
If you have used the 1-Click-Root method, did you follow the steps to type in telnetd using a terminal app? If not then I would go back and re-trace your steps.
Click to expand...
Click to collapse
Yes I did the telnetd thing. After rebooting clicking on an emptyspace then RETURN, wait, RETURN then telnetd which took me to the contact list. Then Home. Then I went to the terminal app and did the 4 step thing. But I did all that before flashing the Cyanogen for the first time. Now that I have Cynogen installed, if I try to Connect in telnet it gives me an error and if I try to do the 4 step thing in Terminal emulator it says "permission denied. (are you root?)". Please tell me what should I do?
pooranimator said:
Yes I did the telnetd thing. After rebooting clicking on an emptyspace then RETURN, wait, RETURN then telnetd which took me to the contact list. Then Home. Then I went to the terminal app and did the 4 step thing. But I did all that before flashing the Cyanogen for the first time. Now that I have Cynogen installed, if I try to Connect in telnet it gives me an error and if I try to do the 4 step thing in Terminal emulator it says "permission denied. (are you root?)". Please tell me what should I do?
Click to expand...
Click to collapse
type su into the terminal emulator and see what is says. if you were able to flash a custom rom then your phone is rooted, you could've gotten a bad download.
Download Better Terminal from the Maket and as david mentioned, type in "su" then press enter to see if you have root access.
if nothing pops up upon entering su does that mean a new wipe and install is nessecary??
Reason i ask is i can't get the terminal emulator to work either that came with the build....is it the same thing as better terminal????. I used a one click install and everything is running fine on my 4.0.4 build but i tried earlier as well to install the "overclock" app from market and it wouldn't work. I decided to purchase SetCPU instead for a buck and it works no problem. By the way i have a my touch 3g..
mikespy said:
if nothing pops up upon entering su does that mean a new wipe and install is nessecary??
Reason i ask is i can't get the terminal emulator to work either that came with the build....is it the same thing as better terminal????. I used a one click install and everything is running fine on my 4.0.4 build but i tried earlier as well to install the "overclock" app from market and it wouldn't work. I decided to purchase SetCPU instead for a buck and it works no problem. By the way i have a my touch 3g..
Click to expand...
Click to collapse
dont think the terminal emulator works w/o a physical keyboard
better terminal will get the job done, but not the same app. You can just use that instead of terminal
but if terminal does work w/o a physical keyboard, when you type su, what does it do?
if it asks to allow or deny, click allow. if you hit always deny, go to the superuser app and erase all settings.
if it doesnt ask anything, when you type su, it should drop one line and have this symbol #
B-man007 said:
dont think the terminal emulator works w/o a physical keyboard
better terminal will get the job done, but not the same app. You can just use that instead of terminal
but if terminal does work w/o a physical keyboard, when you type su, what does it do?
if it asks to allow or deny, click allow. if you hit always deny, go to the superuser app and erase all settings.
if it doesnt ask anything, when you type su, it should drop one line and have this symbol #
Click to expand...
Click to collapse
Thanks for the help....
I actually did download better terminal and when i typed in su and hit enter. It went to the screen your talking about and since i had just installed SetCPU it asked if i wished to allow i clicked yes. So i asume i have rooted correctly and guess the "overclocking" program on the market might just not download on my phone correctly with the cyan 4.0.4.
Thanks
Thanks to all of you for your replies. I think I know what the problem was. The OverclockWidget is a Widget...duh silly me. I was trying to open it as a regular app and was failing. Added it as a widget on the first screen and now everything works. I have one quick unrelated question, while downloading the latest experimental release of Cyanogen I read at the bottom of the post in read that the users should not use any Apps2SD while using Cyaogen's latest release because the ROM does it by itself or something like that. What does that mean?
@mikespy- tap and hold for a sec on your screen and add the OverclockWidget widget on your screen then tap to open. That's how you open the OC util.
ok this is where i am i unzipped android sdk6 on my c drive.. i put the asroot(unzipped) and the i.5 recovery image in the tools folder of the sdk.. i go to the windows prompt and type "cmd" (no quotes) screen comes up i type cd C\android-sdk-windows\tools.. press enter.. then i get "this system cannot find the path specicied" help.....
Run the setup dcs in the Android ask folder and make sure you do it as admin in Vista and 7. You'll probably have to force http in options, most people do.
-------------------------------------
Sent via the XDA Tapatalk App
darrick913 said:
ok this is where i am i unzipped android sdk6 on my c drive.. i put the asroot(unzipped) and the i.5 recovery image in the tools folder of the sdk.. i go to the windows prompt and type "cmd" (no quotes) screen comes up i type cd C\android-sdk-windows\tools.. press enter.. then i get "this system cannot find the path specicied" help.....
Click to expand...
Click to collapse
are you typing what you put above or cd c:\android-sdk-windows\tools ?
don't see the colon in there.
are you sure you installed it like Kcarp. says?
yeah i put colon still the same
ill try it again
u have a link foe kcarp.. i was doing it like fliptz says...
thanks for all your help...
i forced options but then what ther are nothing but update choices...
ok i got the problem solved it was file name... now i get down to the part where you install the 1.5 flash to the sd card and it cant find it.. yes i did remame it per the little glitch that fliptz said
darrick913 said:
ok i got the problem solved it was file name... now i get down to the part where you install the 1.5 flash to the sd card and it cant find it.. yes i did remame it per the little glitch that fliptz said
Click to expand...
Click to collapse
ok, can you provide a link of what tutorial you are following, and let us know what step # you are stuck on.
THis will make us helping you a lot easier.
i was following the thread of how to root 2.1.. i get down to the part where super user is installed on phone.. the su is there but when i open it its a blank program sheet and the cmd prompt says permission denied . what can i do? and thanks for your help..
--------------------------------------------------------------------------------
i followed the steps for rooting the 2.1 in thread.. i get down to the part where the super user is on phone i open it and the command propmt says permission denied.. and thanks for all your help....
darrick913 said:
--------------------------------------------------------------------------------
i followed the steps for rooting the 2.1 in thread.. i get down to the part where the super user is on phone i open it and the command propmt says permission denied.. and thanks for all your help....
Click to expand...
Click to collapse
is USB debugging enabled in Menu->Settings->Applications->Development
I have it.thanks.we are back.yes!
-------------------------------------
Sent via the XDA Tapatalk App
darrick913 said:
I have it.thanks.we are back.yes!
-------------------------------------
Sent via the XDA Tapatalk App
Click to expand...
Click to collapse
what fixed it?
Like many, I have CM installed on the Touchpad, with that frakking wifi problem plaguing me.
I don't mind redoing my connection every time I take the tablet; however where is the wifi settings "kept" in the file system? I need to delete the profile in order to redo the connection.
Can someone help? There are so many bazillion posts mentioning wifi that nothing of value can be found.
you can see the wifi settings in settings>wireless and networks>wifi settings and you can make your touchpad forget the connection settings by holding on the name of the connection and hitting forget on the pop up. after that you connect to your connection as if for the first time.
isanrap said:
you can see the wifi settings in settings>wireless and networks>wifi settings and you can make your touchpad forget the connection settings by holding on the name of the connection and hitting forget on the pop up. after that you connect to your connection as if for the first time.
Click to expand...
Click to collapse
Yep I tried doing that, and I have Force Close problems on the Wi-Fi menu, when the device does not connect. It's as if internally, there is a loop of something happening.
I thought somewhere in the filesystem bowels, there is a way to delete it "directly" without going via the UI. Thanks for trying to help, I appreciate it
Anyone knows if there is such a file somewhere?
i had this problem two days ago. i changed the channel of my router to 2 and restarted my touchpad into webos and back into android and made my touchpad to forget the network and reconnected it and i don't know what happened but that worked. wish i could be of more help to you, hope you get it working sooner so you could enjoy the android goodness.
don't where where it lives on the filesystem, but this app does it: market.android.com/details?id=com.brilliapps.wifiandmorefixer
http://forum.xda-developers.com/showpost.php?p=20963737&postcount=8
HOW DO I CLEAR OUT *ALL* MY WIFI SETTINGS AND START FRESH?
If you find that your wifi is "strobing" on and off, or you wish to completely wipe out all wifi settings, you can do this in one of three ways:
THE "RIGHT" WAY (USING ADB):
adb shell rm -rf /data/misc/wifi && reboot
(this will remove the settings and then force a reboot)
THE "I-DON'T HAVE ADB INSTALLED" WAY:
From the Terminal app.
# rm -rf /data/misc/wifi && reboot
(similar command as above. The # is a prompt-- don't type that part. If you see a $ prompt instead, type "su" (no quotes) and it should become a #)
Click to expand...
Click to collapse
from here http://rootzwiki.com/topic/10121-releasealpha35cyanogenmod-touchpad/
speakxj7 said:
don't where where it lives on the filesystem, but this app does it: market.android.com/details?id=com.brilliapps.wifiandmorefixer
http://forum.xda-developers.com/showpost.php?p=20963737&postcount=8
Click to expand...
Click to collapse
Yesssssss. Thanks a lot, it works.
It's a (mini) chore each time to clear up everything, but at least it works.
Again, thanks.
speakxj7 said:
don't where where it lives on the filesystem, but this app does it: market.android.com/details?id=com.brilliapps.wifiandmorefixer
http://forum.xda-developers.com/showpost.php?p=20963737&postcount=8
Click to expand...
Click to collapse
b.huss2 said:
from here http://rootzwiki.com/topic/10121-releasealpha35cyanogenmod-touchpad/
Click to expand...
Click to collapse
a benefit of the app i referenced is that no reboot (or worse) required.
speakxj7 said:
a benefit of the app i referenced is that no reboot (or worse) required.
Click to expand...
Click to collapse
true. I'm with ya, just throwing it out there. ADB would be the preferred method but for those that are not familiar with ADB, then an app would be easier, although i don't know if that app is doing the same thing as the ADB approach. if it is then win-win. if not, and problems still exsist, then ADB is an alternative approach.
b.huss2 said:
from here http://rootzwiki.com/topic/10121-releasealpha35cyanogenmod-touchpad/
Click to expand...
Click to collapse
What is adb? I activated it in development options, but where do I get it?
deafasheck said:
What is adb? I activated it in development options, but where do I get it?
Click to expand...
Click to collapse
Why not do your own research? A quick Google search reveals:
http://lifehacker.com/the-easiest-way-to-install-androids-adb-and-fastboot-to-1586992378
https://developer.android.com/studio/command-line/adb.html
Ask only when you really need it.
b.huss2 said:
from here http://rootzwiki.com/topic/10121-releasealpha35cyanogenmod-touchpad/
Click to expand...
Click to collapse
Thanks, I got terminal and I typed in all the commands. Do I include the & & reboot in the code? Any spaces or straight type?
So, I followed the guide we all did here:
http://forum.xda-developers.com/showthread.php?t=1818502
And before someone asks: I have deleted the Backup app (IS11LG_SystemBackupTest.signed.apk) we had to install during rooting after the phone was rooted.
The phone then happily ran, rooted. SUpersu was installed/updated, the phones root check said it's all perfect, I was a happy camper. But today I had to reboot it. I can't say if it was the first reboot after rooting, sadly. The phone boots up, arrives at the lockscreen (some colorful defaultthing, before I get to see my GO Locker screen after login), and then stops being responsive, it basically at first feels like it's not reacting at all. Some things are responsive, strngely ... I get accurate sounds when touching the screen for instance. If I then wait, I eventually get to the SIM Unlock ... which is also totally unresponsive, it will maybe show two digits, then freezes up. Strangely, I could type the remaining digits and hit OK and the SIM would unlock ... but the screen no longer showed what I typed. I then arrive at GO locker, can unlock it (sluggish and slow again) and finally am properly logged in, but still totally sluggish and slow. Needles to say it's a pseudobrick that way, unusable.
What's going on and what could I check?
Please try the following:
alexp999 said:
REALLY SLOW AFTER ROOT?
Remove the "SystemBackupTest" app, if you haven't already.
On your phone, go to "Settings -> Developer options" and make sure "USB debugging" is TICKED
Connect your phone via USB to your computer.
Open a command prompt (may need admin privelages, right click, run as administrator)
Type without quotes "cd C:\o4xr" and press enter.
Type without quotes "adb shell rm /data/local.prop" and press enter.
Type without quotes "adb reboot" and press enter.
Click to expand...
Click to collapse
alexp999 said:
Please try the following:
Click to expand...
Click to collapse
Thanks, that fixed it! It's not easy to do, as the scrolling lists do not work, either, and you can't seem to get to the developer options, it won't scroll. Strangely enough "internally" it seems to do things ... if you re-enter the options, they're down to the end of the list, it looks like it doesn't update the screen properly (much like when I had to enter the SIM code).
Anyway, it's fast again, whew ... I was scared. What is the local.prop thing, if I may ask?
voon said:
Thanks, that fixed it! It's not easy to do, as the scrolling lists do not work, either, and you can't seem to get to the developer options, it won't scroll. Strangely enough "internally" it seems to do things ... if you re-enter the options, they're down to the end of the list, it looks like it doesn't update the screen properly (much like when I had to enter the SIM code).
Anyway, it's fast again, whew ... I was scared. What is the local.prop thing, if I may ask?
Click to expand...
Click to collapse
I'm not entirely sure, I just know it gives us temp root for the rest of the root script to run.
Hm, so its' not a systemwide ini file or so, that existed before ... it was created during the above rooting process and was an undesired leftover from it? I'm always a bit worried if I delete something with such an unspecific name in the OS
voon said:
Hm, so its' not a systemwide ini file or so, that existed before ... it was created during the above rooting process and was an undesired leftover from it? I'm always a bit worried if I delete something with such an unspecific name in the OS
Click to expand...
Click to collapse
Its actually created by the SystemBackupTest app.
The script then removes it just before issuing a reboot.
The only way it can come back, is if you accidently open that app again before uninstalling it.
alexp999 said:
Its actually created by the SystemBackupTest app.
The script then removes it just before issuing a reboot.
The only way it can come back, is if you accidently open that app again before uninstalling it.
Click to expand...
Click to collapse
I see, I might have done that ... good to know. Anyway, great that it works again, thanks again
laggy phone
My lg 4x hd is very slow after root...
I just tried to make this few steps above, but I got this message.
Any idea what to do?
Pls help me!
THX
66aaa
66aaaa said:
My lg 4x hd is very slow after root...
I just tried to make this few steps above, but I got this message.
Any idea what to do?
Pls help me!
THX
66aaa
Click to expand...
Click to collapse
It looks like you have either plugged in more than one android device, or you have an android emulator (from the SDK I guess) running. Unplug all USB devices (except keyboard and mouse) and then try again. Good luck!
If you have an emulator running try "adb -d shell rm /data/local.prop"
Edit: To see all adb-devices type "adb devices". This will return a list of all adb-devices connected (emulators + usb devices)
Dexxon said:
If you have an emulator running try "adb -d shell rm /data/local.prop"
Edit: To see all adb-devices type "adb devices". This will return a list of all adb-devices connected (emulators + usb devices)
Click to expand...
Click to collapse
I still don't understand and hope you do it...
THX for your help!
As you can see the same device is listed two times. Restarting the adb server may help. Just type "adb kill-server" and than launch the second command from your screenshot. Maybe this works.
Dexxon said:
As you can see the same device is listed two times. Restarting the adb server may help. Just type "adb kill-server" and than launch the second command from your screenshot. Maybe this works.
Click to expand...
Click to collapse
This is the result...what to do know?
THX
The devices is detected and the command is executed, but the file does not exist. Make sure that there is a file "prop.local" at /data. If not, you may have a different problem.
Maybe you have an emulator running or Bluestacks installed... Uninstall Bluestacks...
I don't think that this is the case as the device shows up with a serial number in the "adb devices" list.
To be sure it is the correct phone you could compare the serial number shown in the list with the serial number of your phone (you might find this information in settings -> about phone).
Dexxon said:
The devices is detected and the command is executed, but the file does not exist. Make sure that there is a file "prop.local" at /data. If not, you may have a different problem.
Click to expand...
Click to collapse
I don't have in the system/data "prop.local" file...sure....
What is emulator and Bluestacks?
I really don't understand this problem I have...
Could you help me pls?
THX
66aaaa said:
I don't have in the system/data "prop.local" file...sure....
What is emulator and Bluestacks?
I really don't understand this problem I have...
Could you help me pls?
THX
Click to expand...
Click to collapse
An emulator is a program which emulates Android so you can execute Android-Apps on your PC. BlueStacks is an emulator. It may show up as an adb devices, but this is not the case here.
Back to your problem: Are you sure the rooting process worked?
Did you reboot your phone after rooting?
I didn't root my phone under ICS so I don't have any experience with this
no one raised this question to confirm or did this info was provided anywhere
What version of ROM? ICS V10x? JB V20x? User could had used the wrong guide.
Best way out is to do a reflash and retry rooting if all fails.
Dexxon said:
An emulator is a program which emulates Android so you can execute Android-Apps on your PC. BlueStacks is an emulator. It may show up as an adb devices, but this is not the case here.
Back to your problem: Are you sure the rooting process worked?
Did you reboot your phone after rooting?
I didn't root my phone under ICS so I don't have any experience with this
Click to expand...
Click to collapse
I dont't have this Bluestacks emulatur, sure...
I have Superuser working properly on JB V20 stock ROM. The only thing it is very slow sometimes, Thats why I tried to make the process above...
I made the root few month ago...and rebooted many times since than...
Any idea what to do now?
THX
In AOSP based android Q roms, there is a force dark option in developer settings whoich makes almost all apps to be appreaded in dark mode.
This option gets unselected after reboot.
One has to enable it after every reboot.
However it's possible to enable it by default after reboot.
For rooted phone.
Just add the following line in your build.prop file
debug.hwui.force_dark=true
Thats all.
It's working in my phone. Tested.
For unrooted Phone
execute the following line after reboot
setprop debug.hwui.force_dark true
To make it auto after reboot use tasker or script manager app or smthing similer.
Check the space after setprop and dark.
Hit a thanks to me if you are benifited.
Screenshots.??
Screenshot
Hmmmm.
Screenshot for many apps.?
Thanks
LoveFootJob said:
Hmmmm.
Screenshot for many apps.?
Thanks
Click to expand...
Click to collapse
look at your back....its there already
[email protected] said:
For unrooted Phone
execute the following line after reboot
setprop debug.hwui.force_dark true
To make it auto after reboot use tasker or script manager app or smthing similer.
Check the space after setprop and dark.
Click to expand...
Click to collapse
Hi
How did you manage that?
As far as I know, setprop needs root or it won't work unless it's done via adb on a computer
Sent from my SM-N976B using XDA Labs
paolo200 said:
Hi
How did you manage that?
As far as I know, setprop needs root or it won't work unless it's done via adb on a computer
Click to expand...
Click to collapse
No...it will work...
Just auto execute it after every reboot thru tasker
[email protected] said:
No...it will work...
Just auto execute it after every reboot thru tasker
Click to expand...
Click to collapse
Ok. Thanks.
May I ask what is the action to use within tasker?
Sent from my SM-N976B using XDA Labs
davidking2893 said:
First, turn off regular dark mode (if enabled) and reboot your cell phone. Then, toggle the override-dark-mode option in developer settings and restart the settings app. This will force all apps into the override-dark-mode color scheme. Thats' it.
Click to expand...
Click to collapse
Question is how to do it auto after reboot
[email protected] said:
For unrooted Phone
execute the following line after reboot
setprop debug.hwui.force_dark true
To make it auto after reboot use tasker or script manager app or smthing similer.
Check the space after setprop and dark.
Hit a thanks to me if you are benifited.
Click to expand...
Click to collapse
I don't get you. Can you give a detailed tutorial?
Not working
Im on a non-rooted Galaxy S10e [Android 10, OneUI 2.0]. If I run the command with tasker, it gives me the following message ("Ausführen" is german and means "execute", "Fehler" means "error"):
05.06.39/E Shell Ausführen: ->
05.06.39/E Shell Ausführen: ->
05.06.39/E Shell Ausführen: ->
05.06.39/Shell runBackground setprop debug.hwui.force_dark true root: false timeout: -1
05.06.39/Shell start process-thread ID 672
05.06.39/E add wait type Shell1 time 2147483647
05.06.39/E add wait type Shell1 done
05.06.39/E add wait task
05.06.39/E Fehler: 1
If I do it with the app "Android Terminal Emulator" it gives me the following error:
:/ $ setprop debug.hwui.force_dark true
setprop: failed to set property 'debug.hwui.force_dark' to 'true'
Either way, it doesnt work for me. Does anybody know what could be the issue here? Ive also tried setting it to "1" instead of "true", same result. Setting the real setting to enabled or disabled doesnt matter either.
RnKn98 said:
Im on a non-rooted Galaxy S10e [Android 10, OneUI 2.0]. If I run the command with tasker, it gives me the following message ("Ausführen" is german and means "execute", "Fehler" means "error"):
05.06.39/E Shell Ausführen: ->
05.06.39/E Shell Ausführen: ->
05.06.39/E Shell Ausführen: ->
05.06.39/Shell runBackground setprop debug.hwui.force_dark true root: false timeout: -1
05.06.39/Shell start process-thread ID 672
05.06.39/E add wait type Shell1 time 2147483647
05.06.39/E add wait type Shell1 done
05.06.39/E add wait task
05.06.39/E Fehler: 1
If I do it with the app "Android Terminal Emulator" it gives me the following error:
:/ $ setprop debug.hwui.force_dark true
setprop: failed to set property 'debug.hwui.force_dark' to 'true'
Either way, it doesnt work for me. Does anybody know what could be the issue here? Ive also tried setting it to "1" instead of "true", same result. Setting the real setting to enabled or disabled doesnt matter either.
Click to expand...
Click to collapse
In Samsung phone setprop command is diff i guess... Google it for command.
[email protected] said:
In Samsung phone setprop command is diff i guess... Google it for command.
Click to expand...
Click to collapse
Do you have proof it's working for non root??
[email protected] said:
In Samsung phone setprop command is diff i guess... Google it for command.
Click to expand...
Click to collapse
First thanks for the answer , but...
I dont think its different. The getprop command (getprop debug.hwui.force_dark) works fine, gives me true if its turned on.
If i do the setprop command over adb (adb shell setprop debug.hwui.force_dark true) it also works fine.
The only thing not working is the setprop command executed directly on my device. Which lets me conclude that i probably need root?
RnKn98 said:
First thanks for the answer , but...
I dont think its different. The getprop command (getprop debug.hwui.force_dark) works fine, gives me true if its turned on.
If i do the setprop command over adb (adb shell setprop debug.hwui.force_dark true) it also works fine.
The only thing not working is the setprop command executed directly on my device. Which lets me conclude that i probably need root?
Click to expand...
Click to collapse
No... Its working in non rooted device... Tested.
There may be one more thing... Shell need to have write secure settings permission. Its permission issue.
[email protected] said:
In AOSP based android Q roms, there is a force dark option in developer settings whoich makes almost all apps to be appreaded in dark mode.
This option gets unselected after reboot.
One has to enable it after every reboot.
However it's possible to enable it by default after reboot.
For rooted phone.
Just add the following line in your build.prop file
debug.hwui.force_dark=1
Thats all.
It's working in my phone. Tested.
Hit a thanks to me if you are benifited.
Click to expand...
Click to collapse
Hello,
Thank you so much for your solution that works very well on my rooted phone :good:
1) I would like to know how to totally disable this feature if I no longer want the override force-dark someday please ?
2) Actually, how to force the rest of the remaining white applications to become black please ?
Thank you in advance for your help.
Cordially
MobAndro said:
Hello,
Thank you so much for your solution that works very well on my rooted phone :good:
1) I would like to know how to totally disable this feature if I no longer want the override force-dark someday please ?
2) Actually, how to force the rest of the remaining white applications to become black please ?
Thank you in advance for your help.
Cordially
Click to expand...
Click to collapse
Just switch off dark theme... Force dark need not to be changed. Add dark theme icon in qs header
[email protected] said:
Just switch off dark theme... Force dark need not to be changed. Add dark theme icon in qs header
Click to expand...
Click to collapse
Hello,
I've been using the dark mode since I bought my S10.
I discovered the override force-dark a few days ago then I realized that after the reboot this option was disabled on its own and every time.
I did some research to have it automatically and I came across your tuto that worked very well for me. Only some applications had problems with the override force-dark.
Since yesterday, I don't know why now the override force-dark disables itself. When I turn it on, it immediately turns off itself without even restarting.
I don't understand what's going on because this option was automatically activated after each reboot.
I didn't again even touch the build.prop either...
MobAndro said:
Hello,
I've been using the dark mode since I bought my S10.
I discovered the override force-dark a few days ago then I realized that after the reboot this option was disabled on its own and every time.
I did some research to have it automatically and I came across your tuto that worked very well for me. Only some applications had problems with the override force-dark.
Since yesterday, I don't know why now the override force-dark disables itself. When I turn it on, it immediately turns off itself without even restarting.
I don't understand what's going on because this option was automatically activated after each reboot.
I didn't again even touch the build.prop either...
Click to expand...
Click to collapse
It's tough to tell the problem from here. U hv to find it.
[email protected] said:
It's tough to tell the problem from here. U hv to find it.
Click to expand...
Click to collapse
Do you think that I can delete this line "debug.hwui.force_dark=1" and put it back in the build.prop again after reboot please ?
Because it's the first time that I've modified this system file so I'm not used to manipulating it...
Thank you in advance for your answer.