Related
As mentioned here and here:
adding "echo ro.HOME_APP_ADJ=1" to /data/local.prop fixes the launcher redraw lag.
Documentation:
http://code.google.com/p/sipdroid/wiki/FAQ
Due to limited memory home screen often takes several seconds to load. Luckily these phones allow root access. Issue the command "echo ro.HOME_APP_ADJ=1 >/data/local.prop" and reboot, to lock home screen in memory.
Click to expand...
Click to collapse
update:
it does seem to made a difference
Here are the commands: (batch file to do this here,post#5)
Code:
adb remount
adb pull /system/build.prop .
edit build.prop with a decent text editor and add these two lines a the end
#fix for screen redraw lag
ro.HOME_APP_ADJ=1
Click to expand...
Click to collapse
Code:
adb push build.prop /system/
adb reboot
you could try
Code:
adb shell stop
adb shell setprop ro.HOME_APP_ADJ=1
adb shell start
if it works you just have to add ro.HOME_APP_ADJ=1 to build.prop.
g4rb4g3 said:
you could try
Code:
adb shell stop
adb shell setprop ro.HOME_APP_ADJ=1
adb shell start
if it works you just have to add ro.HOME_APP_ADJ=1 to build.prop.
Click to expand...
Click to collapse
tried:
Code:
adb shell stop
adb shell setprop ro.HOME_APP_ADJ 1
adb shell start
My phone hot rebooted after the last command.
After it rebooted I ran
Code:
C:\Users\meeee>adb shell getprop ro.HOME_APP_ADJ
4
Since its 4. I guess it did not stick.
Also tried setting it and immediately reading it, did not stick.
Code:
C:\Users\meeee>adb shell setprop ro.HOME_APP_ADJ 1
C:\Users\meeee>adb shell getprop ro.HOME_APP_ADJ
4
The setting stuck after putting it in build.prop, time to check if it made any difference...
Code:
C:\Users\meeee\Desktop>adb shell getprop ro.HOME_APP_ADJ
1
Don't reboot, try the commands and watch out if your problem got fixed. If it works like that you can add the line to build.prop.
g4rb4g3 said:
Don't reboot, try the commands and watch out if your problem got fixed. If it works like that you can add the line to build.prop.
Click to expand...
Click to collapse
It did it on its own.
seems to be working, updated op with the commands.
britoso said:
seems to be working, updated op with the commands.
Click to expand...
Click to collapse
Added this cmd to build.prop but see no changes... what lags you talking about btw?
For me my home screens were sluggish. There was a delay when I tried to switch desktops.
I made a little bat.file, which adds those 2 lines to your build.prop.
- put "Launcher_lag_fix.bat" in ..Android/tools/
- doubleklick
- and wait till reboot.
rori~ said:
I made a little bat.file, which adds those 2 lines to your build.prop.
- put "Launcher_lag_fix.bat" in ..Android/tools/
- doubleklick
- and wait till reboot.
Click to expand...
Click to collapse
thanks rori.
No one has posted yet what the command actually does. All it does is tell Android to try to keep the launcher in memory.
Shouldn't affect anything like the scrolling or any response while actually using the launcher, but will fix some lag for when going back home from any other app, as it doesn't have to re-launch the launcher if it was kicked out of memory.
Various options like this exist in some launchers, and I think Cyanogenmod has this option in the settings too. They are not all the same as this command though, so this may work better for some people while the other ways to do it may work better for others.
Clarkster said:
No one has posted yet what the command actually does. All it does is tell Android to try to keep the launcher in memory.
Click to expand...
Click to collapse
As per this it locks the 'screen' in memory. (maybe they mean the screen buffer)
Due to limited memory home screen often takes several seconds to load. Luckily these phones allow root access. Issue the command "echo ro.HOME_APP_ADJ=1 >/data/local.prop" and reboot, to lock home screen in memory.
Click to expand...
Click to collapse
Makes sense as I always have had launcher locked in memory before this and was still having my home screen redraw very slowly when I switched to it.
A good find
Btw just for info there were issues in apps from pre release system dump of arc
However if u r using apps from the retail dump 'they don't lag'
Sent from my U20i using XDA App
rori~ said:
I made a little bat.file, which adds those 2 lines to your build.prop.
- put "Launcher_lag_fix.bat" in ..Android/tools/
- doubleklick
- and wait till reboot.
Click to expand...
Click to collapse
can you specify where is the android/tools mentioned, can it be found in all android phones?
Btw, I have seen ">>" and ">" then "space" /data/local.prop in other websites, while in the sipdroid article, it is exactly
"echo ro.HOME_APP_ADJ=1 >/data/local.prop".
otivaeey said:
can you specify where is the android/tools mentioned, can it be found in all android phones?
Btw, I have seen ">>" and ">" then "space" /data/local.prop in other websites, while in the sipdroid article, it is exactly
"echo ro.HOME_APP_ADJ=1 >/data/local.prop".
Click to expand...
Click to collapse
adb comes with the sdk, for my windows machine its at
C:\android-sdk-windows\platform-tools
in unix ">" sends text to a file (deletes whatever was there) and ">>" appends at the end of a file. If you're not familiar its easiest to just add the one line manually at the end of build.prop.
Hey y'all, wondering if anybody can help me with this:
I'm at work and don't have access to ADB. Can I use Root Explorer to copy the file to the sdcard, mount the card on a PC, edit it, and then use Root Explorer to copy it back again? Or will that cause issues with permissions or something?
EDIT: Well it's intellectual now, I nandroided back to my previous ROM due to some other issues. I'd still like to know though.
Ya the root explorer thing should work but just to be safe I would nandroid first cause worst case scenario your phone freezes you pull battery boot into recovery restore nandroid. But seriously I don't think it will be a problem.
Just out of curiosity I wanted to see if I could do this without a computer at all and turns out all you really need to do is download estrong (or any other root explorer), turn root explorer option on, mount /system and go and edit build.prop through the the built in note editor in estrong. So that might be an alternate solution for you kippswanson.
possible fix workaround for the DSI errors on Motorola Milestone Froyo on nadlabaks github
http://github.com/nadlabak/android_...mmit/e1bb339b133dd88389a4c3a80bad3a984d12db50
EDIT:
IanTester said:
echo 1 > /sys/devices/omapdss/display0/update_mode
Click to expand...
Click to collapse
should do the same
EDIT:
<nadlabak> it causes slight tearing, visible e.g. when scrolling through email list...
Click to expand...
Click to collapse
but better than reboots or freezes
also fps might drop
EDIT:
for stock 2.2.1, customroms should use their 2nd init (CM7 HowTo):
move original file:
Code:
mv /system/bin/mot_boot_mode /system/bin/mot_boot_mode.bin
create file /system/bin/mot_boot_mode:
Code:
#!/system/bin/sh
export PATH=/system/bin:$PATH
mot_boot_mode.bin
echo 1 > /sys/devices/omapdss/display0/update_mode
set rights:
Code:
chmod 755 /system/bin/mot_boot_mode
EDIT:
made HowTo more clear, hopefully
How to apply this?
Sent from my Milestone using XDA App
to apply this fix you hafe to (as root or in OR)
if /system is readonly:
Code:
mount -o rw,remount /system
then edit /system/etc/rootfs/init.mapphone_umts.rc and add
Code:
# Set OMAP DSS update_mode to 1 (auto) to get rid of the DSI errors
write /sys/devices/omapdss/display0/update_mode 1
after these lines
Code:
# Enable panic on softlockup
write /proc/sys/kernel/softlockup_panic 1
reboot Milestone
Maybe it should be
mount -o ro,remount /dev/block/mtdblock6 /system
Hm, there is no directory rootfs in /system/etc/ ... Have you tried what you are writing here? Maybe "rootfs" refers to the root dir "/" and the file to edit is "/init.mapphone_umts.rc".
You don't need a reboot.
echo 1 > /sys/devices/omapdss/display0/update_mode
Click to expand...
Click to collapse
(I presume that's what that command in the rc file does, right?)
But make the changes to the rc file as well, so the above action is performed on subsequant boots.
as it's on nadlabaks github for cyanogenmod4milestone (CM7) it might differ from the way to do in official froyo. but IanTesters way should do the same
ColdSphinX said:
as it's on nadlabaks github for cyanogenmod4milestone (CM7) it might differ from the way to do in official froyo. but IanTesters way should do the same
Click to expand...
Click to collapse
Seems to be the case. But since I'm not able to edit /init.mapphone_umts.rc (that's the reason why there is an extra dir for this in cyanogenmod), how am I supposed to implement this fix in the official froyo?
Done on CM6.
Yesterday I was browsing the system folders and found this file, full of customizable options, now I know that it's useful.
@tuxor1337: look for the mot_boot_mode hack to run a script as it's used for overclock
IanTester said:
echo 1 > /sys/devices/omapdss/display0/update_mode
Click to expand...
Click to collapse
For stock Froyo roms, i applied VR and then ran AOR, connected phone to pc and used the following commands in command prompt.
adb devices ( should show your device as connected )
adb shell
echo 1 > /sys/devices/omapdss/display0/update_mode
reboot
Upon reboot, i did not find any errors in dmesg which i usually find.
Can someone with more knowledge than me confirm if this is ok?
I know that can be a noobish question but what VR stands for ?
fuggii said:
I know that can be a noobish question but what VR stands for ?
Click to expand...
Click to collapse
VR --> Vulnerable recovery
AOR --> Androidiani openrecovery
I had to do it because adb was not recognising my phone while in the stock recovery menu.
Once i ran AOR, adb recognised my phone to be in recovery mode.
I make this "echo 1 > /sys/devices/omapdss/display0/update_mode" from terminal emulator and after reboot its back to "2" it must be done form adb in AOR ?
it has to be done on or after any boot.
I edited the 1st post to include the changes to do on stock 2.2.1
fuggii said:
I make this "echo 1 > /sys/devices/omapdss/display0/update_mode" from terminal emulator and after reboot its back to "2" it must be done form adb in AOR ?
Click to expand...
Click to collapse
Looks like it loses it during reboot, so it could be added to the init.rc file as well. I am not sure, that's why i asked with someone more knowledge to confirm this.
Anyone?
I have Autostart app and i make autostart.sh with that command and now its start every system boot.
In home i will try that ColdSphinX method and see what happend
@fuggii it's not my method, it's just a mot_boot_mode hack so you don't need any app and the fix get's applyed as early as we can
I think this should work but I copied all of this https://github.com/nadlabak/android...b50/prebuilt/etc/rootfs/init.mapphone_umts.rc
And used that as init.mapphone_umts.rc
Hey the OP needs updating....
It's missing the 1
echo 1 > /sys/devices/omapdss/display0/update_mode 1
zeppelinrox said:
It's missing the 1
echo 1 > /sys/devices/omapdss/display0/update_mode 1
Click to expand...
Click to collapse
no
Code:
echo [B]1[/B] > /sys/devices/omapdss/display0/update_mode
writest the value 1 into file /sys/devices/omapdss/display0/update_mode it's an other syntax then using write in the .rc
Well, a couple days ago I installed the Cyanogen Mod RC 2 via this topic. So, i found some problems (common bugs) such as wi-fi dont conecting, the led that lighs the screen blinking, proximity sensor and etc.
To fix these problems, i got this video from this tutorial and flashed the package from the tutorial. The problems were solved, except the led, that some times blinks and turns off randomly. What should I do? Is there any way to "format" and install an official firmware, or original files related to the LED lights to solve it?
Since now thanks!
estevaoem said:
Well, a couple days ago I installed the Cyanogen Mod RC 2 via this topic. So, i found some problems (common bugs) such as wi-fi dont conecting, the led that lighs the screen blinking, proximity sensor and etc.
To fix these problems, i got this video from this tutorial and flashed the package from the tutorial. The problems were solved, except the led, that some times blinks and turns off randomly. What should I do? Is there any way to "format" and install an official firmware, or original files related to the LED lights to solve it?
Since now thanks!
Click to expand...
Click to collapse
I have the same problem, actually I'm using the DDKQ6 2.3.4 ROM, I've installed a lot of other ROMS and i'm still trying to install one to fix the problem...
Any idea if it is a factory issue or it is a rom issue?
"My english is not so good because my default languaje is Spanish"
Just turn it off:
https://market.android.com/details?id=com.deskangel.kblight
Just flashed to CM7.2 by vo1 last night..
before that, I've been using BehradGH's Cm RC 2.2 without any bugs, all wi-fi and LED screen works just fine...
Brajano95 said:
Just turn it off:
https://market.android.com/details?id=com.deskangel.kblight
Click to expand...
Click to collapse
You need to turn off the LED lights to solve the problem. This ROM is known for this problem. Secondary solution is to flash another ROM such as ICS Sunday Final by jusada, which is one the best ROMs ever made.
Brajano95 said:
Just turn it off:
https://market.android.com/details?id=com.deskangel.kblight
Click to expand...
Click to collapse
Turn it off without any application:
Code:
#!/system/bin/sh
echo 0 > /sys/class/leds/button-backlight/brightness
chmod 444 /sys/class/leds/button-backlight/brightness
Copy above script to /system/etc/init.d as 98button-backlight, set the permission to 755.
This is old CM7 issue and already solved. But feel free to use my above script, to save battery for an example. Latest stock firmware just have a annoying update, turning on the button light every time you touch the screen
ketut.kumajaya said:
Turn it off without any application:
Code:
#!/system/bin/sh
echo 0 > /sys/class/leds/button-backlight/brightness
chmod 444 /sys/class/leds/button-backlight/brightness
Copy above script to /system/etc/init.d as 98button-backlight, set the permission to 755.
This is old CM7 issue and already solved. But feel free to use my above script, to save battery for an example. Latest stock firmware just have a annoying update, turning on the button light every time you touch the screen
Click to expand...
Click to collapse
1 more to go Ketut sir XD
EmoBoiix3 said:
1 more to go Ketut sir XD
Click to expand...
Click to collapse
I got 999 because of you
Edit 1: 1000 after a refresh
Edit 2: 1001 after the second refresh
ketut.kumajaya said:
I got 999 because of you
Edit 1: 1000 after a refresh
Edit 2: 1001 after the second refresh
Click to expand...
Click to collapse
I thanked you 4 times in a row LOL (making it 1002)
EmoBoiix3 said:
I thanked you 4 times in a row LOL (making it 1002)
Click to expand...
Click to collapse
LOL. Thanks friend.
ketut.kumajaya said:
LOL. Thanks friend.
Click to expand...
Click to collapse
All you have to do for me is to apply to be a recognised developer
Herpderp Adreno + Tegra.
ketut.kumajaya said:
Turn it off without any application:
Code:
#!/system/bin/sh
echo 0 > /sys/class/leds/button-backlight/brightness
chmod 444 /sys/class/leds/button-backlight/brightness
Copy above script to /system/etc/init.d as 98button-backlight, set the permission to 755.
This is old CM7 issue and already solved. But feel free to use my above script, to save battery for an example. Latest stock firmware just have a annoying update, turning on the button light every time you touch the screen
Click to expand...
Click to collapse
Set permission to 755, what did you mean?
__________________________________________
http://forum.xda-developers.com/showthread.php?t=1387227
ahh
__________________________________________
Anyway, it doesn't work to me, I did exactly what you said. Wth?
__________________________________________
Why always something must not working for me? Yesterday I had The End 2.5, I applied transparent statusbar patch by zdunes (did exactly what was said in tutorial), and statusbar was black, and still had ghosting issue. After every reboot my theme (in theme chooser) was default, not miuiv4 (what was really annoying). Now I'm back to CM7.2 by vo-1 (signature) and after every reboot I must go to keyboard options to 'turn it on' cause if I don't do that my keyboard won't appear. AND NOW THIS. Backlight script isn't working. I think my phone doesn't like me.
thx
Thank you very much.
I solved the problem doing a factory reset and installing the OXFKT1 ROM. The wifi problem, blinking and black screen were solved.
ace_viknesh said:
You need to turn off the LED lights to solve the problem. This ROM is known for this problem. Secondary solution is to flash another ROM such as ICS Sunday Final by jusada, which is one the best ROMs ever made.
Click to expand...
Click to collapse
I just put carbon Sunday beta (by jusada) to my wife's ace. It is even better in my opinion. Also updated lagfree v3 to it. No problems and boy its smooth.
Sent from my GT-I9000 using xda premium
ketut.kumajaya said:
Turn it off without any application:
Code:
#!/system/bin/sh
echo 0 > /sys/class/leds/button-backlight/brightness
chmod 444 /sys/class/leds/button-backlight/brightness
Copy above script to /system/etc/init.d as 98button-backlight, set the permission to 755.
This is old CM7 issue and already solved. But feel free to use my above script, to save battery for an example. Latest stock firmware just have a annoying update, turning on the button light every time you touch the screen
Click to expand...
Click to collapse
I tried doing it but..i think there is some problem in permissions as this script does'nt gets executed automatically while booting(restarting).
My permissions are rwxr-xr-x
But when i open with linux script handler in root explorer and execute it does its job.
so it means script is ok but it has some permissions problem.
plz reply
edit: got it fixed. permissions are correct.
dont knw why tht particular script file was not workin so i copied the two lines and pasted in some other working script kept thr in the same folder which finally worked.
ketut.kumajaya said:
Turn it off without any application:
Code:
#!/system/bin/sh
echo 0 > /sys/class/leds/button-backlight/brightness
chmod 444 /sys/class/leds/button-backlight/brightness
Copy above script to /system/etc/init.d as 98button-backlight, set the permission to 755.
This is old CM7 issue and already solved. But feel free to use my above script, to save battery for an example. Latest stock firmware just have a annoying update, turning on the button light every time you touch the screen
Click to expand...
Click to collapse
man you forgot the semicolons hahaahha here's the right code:
Code:
#!/system/bin/sh
echo 0 > /sys/class/leds/button-backlight/brightness;
chmod 444 /sys/class/leds/button-backlight/brightness;
seanwlk said:
man you forgot the semicolons hahaahha here's the right code:
Code:
#!/system/bin/sh
echo 0 > /sys/class/leds/button-backlight/brightness;
chmod 444 /sys/class/leds/button-backlight/brightness;
Click to expand...
Click to collapse
Really? :laugh: :laugh: :laugh: My S5830 still lying around, thinking to update it to the latest official ROM after you inviting me here :laugh: :laugh: :laugh:
Please update your comment, please learn more about bash scripting
ketut.kumajaya said:
Really? :laugh: :laugh: :laugh: My S5830 still lying around, thinking to update it to the latest official ROM after you inviting me here :laugh: :laugh: :laugh:
Please update your comment, please learn more about bash scripting
Click to expand...
Click to collapse
this is the only way that works... i'm running touchwiz resurrection v9.5 and i checked up the already existing scripts and they all have the semicolons.... after put them the script started work
seanwlk said:
this is the only way that works... i'm running touchwiz resurrection v9.5 and i checked up the already existing scripts and they all have the semicolons.... after put them the script started work
Click to expand...
Click to collapse
No, no, no. My script is correct from the beginning. The most likely cause is Windows EOL (end of line). Windows uses carriage return and line feed as a line ending, which Unix uses just line feed. ROM modder mostly use Windows OS to create a modified ROM for Android and often unaware about this EOL derp
On some roms i cant set swap, my 2nd partition is linux swap and than when i try to enable it its just showing enabling... and nothings happens, only got some SU permissions appearing all the time!
Is there any solution/fix for my problem?
goldenr said:
On some roms i cant set swap, my 2nd partition is linux swap and than when i try to enable it its just showing enabling... and nothings happens, only got some SU permissions appearing all the time!
Is there any solution/fix for my problem?
Click to expand...
Click to collapse
are you using swapper2 app? please specify more info on your problem
You dont need to use an app to get swap. I prefer three lines of code in /system/etc/hw_config.sh
mkswap /dev/block/mmcblk0p2
echo 30 > /proc/sys/vm/swappiness
swapon /dev/block/mmcblk0p2
Try this to see if works
hunff said:
You dont need to use an app to get swap. I prefer three lines of code in /system/etc/hw_config.sh
mkswap /dev/block/mmcblk0p2
echo 30 > /proc/sys/vm/swappiness
swapon /dev/block/mmcblk0p2
Try this to see if works
Click to expand...
Click to collapse
but if rom/kernel doesn't support then gonna use swapper2 from the market.
or else follow hunff instruction and open terminal emulator
-type free
-swap 0 0 0 = not active use swapper2
-swap any value other than 0 = active
Thank you it works!
CKKnot said:
are you using swapper2 app? please specify more info on your problem
Click to expand...
Click to collapse
I am using reset swap app as my title says!
but i tried swapper2 and it says such a directory doesnt exist or other error message forgot it.
I thought ,that swap doesn't work if the kernel doesn't supporting it.
So you say that you can have swap if you have stock kernel(by using swapper?.
Sent from my E15i using Tapatalk
not sure about what he said...
i know you cant use swap partition to set swap with stock kernel
but dont know about swapper through FAT32
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.