I'm having an issue running the over clock command from this thread http://forum.xda-developers.com/showthread.php?t=1594804. When I run the CPU command, after I type /proc/overclock/ it creates a new line as I finish with the /mpu_opps, and it thinks I'm starting the command from the > /proc . It doesn't continue my command in one whole line. I don't know why when I get to the end of a line in the terminal window it jumps down to a new one. Can anyone shed some light?
Just to clarify you are doing the following and its going to a new line after the > symbol?
su (enter to get into rootspace note that it will change from app_********* to [email protected]*******)
echo 3 1200000000 62 > /proc/overclock/mpu_opps (enter)
echo 384000000 > /proc/overclock/gpu_opps (enter)
Whenever I do it it will continue to type on the same line and push back the echo like in the video.
Yes, that is correct.
All you have to do is permanently mod the file that starts the overclocking - see my posts on this page:
http://forum.xda-developers.com/showthread.php?t=1594804&page=3
Once you do that it automagically starts in overclocked mode every time without you having to mess with the terminal window or hooking up a USB-to-PC (ADB) session.
I am using nyakkernel which supports fast charge and Disabling Fsync and i tried typing commands in terminal but i always get nothing can anyone tell me what i should do exactly ?
You could use an application like nsTools or:
To enable Fast Charge:
Enter in terminal emulator:
su
echo 1 > /sys/kernel/fast_charge/force_fast_charge
To disable:
su
echo 0 > /sys/kernel/fast_charge/force_fast_charge
Dynamic Fsync:
Disable:
su
echo 0 > /sys/kernel/dyn_fsync/Dyn_fsync_active
Re-enable:
su
echo 1 > /sys/kernel/dyn_fsync/Dyn_fsync_active
is this tested?
Hello XDA-developers
How can I disable the LED while charging?
I have root access on my Huawei ascend P7.
Lightflow (lite) doesn't help, and Settings > Display > LED and disable it there doesn't help too.
Thanks for your help.
heyhou95 said:
Hello XDA-developers
How can I disable the LED while charging?
I have root access on my Huawei ascend P7.
Lightflow (lite) doesn't help, and Settings > Display > LED and disable it there doesn't help too.
Thanks for your help.
Click to expand...
Click to collapse
Hello !
Here it is :
Code:
> adb shell
$ su
# echo 0 > sys/devices/platform/hkled/leds/green/brightness
# echo 0 > sys/devices/platform/hkled/leds/red/brightness
# exit
$ exit
Good luck !
surdu_petru said:
Hello !
Here it is :
Code:
> adb shell
$ su
# echo 0 > sys/devices/platform/hkled/leds/green/brightness
# echo 0 > sys/devices/platform/hkled/leds/red/brightness
# exit
$ exit
Good luck !
Click to expand...
Click to collapse
sudru ..
i replaced bootanimation.zip bxcos i want original animation.. but instead is just small android write in the middle .. why it doesnt work ?
surdu_petru said:
Hello !
Here it is :
Code:
> adb shell
$ su
# echo 0 > sys/devices/platform/hkled/leds/green/brightness
# echo 0 > sys/devices/platform/hkled/leds/red/brightness
# exit
$ exit
Good luck !
Click to expand...
Click to collapse
Hey surdu_petru, what options else are there? You say echo 0 with output at red and green....can i find the options somewhere?
My red and green/red files are on zero but i have light at charging.
surdu_petru said:
Hello !
Here it is :
Code:
> adb shell
$ su
# echo 0 > sys/devices/platform/hkled/leds/green/brightness
# echo 0 > sys/devices/platform/hkled/leds/red/brightness
# exit
$ exit
Good luck !
Click to expand...
Click to collapse
It works
Thank you very much and good luck with the CM port.
Dont work on Mate S
surdu_petru said:
Hello !
Here it is :
Code:
> adb shell
$ su
# echo 0 > sys/devices/platform/hkled/leds/green/brightness
# echo 0 > sys/devices/platform/hkled/leds/red/brightness
# exit
$ exit
Good luck !
Click to expand...
Click to collapse
I tried that now under Lollipop, but it doesn't survive a reboot. When only setting brightness to zero, the light returns after un- and replugging. So, I set the rights to -r--r--r--, now it works until reboot.
There is also a file called trigger, which I can't change at all, although the rights are -rw-r--r--. I could save, but when opening the next time, it is like it was originally.
Does anyone have an idea how to make those changes permanent? Might the reset be caused by the kernel?
Everyone ecxited about xposed framework released for lollipop.. But there are many facing problems installing framework because of SELinux set to enforce by default.
You can check you Selinux status in settings - About phone
You can set the SELinux to Permissive temporarily by running the bellow two commands in Terminal emulator
su
setenforce 0
But it SElinux will change to default once you hard reboot your phone.. In order to keep it in permissive, you need to soft reboot always whenever reboot needed and it's quite annoying..
So I found a workaround to Set the SELinux to permissive on boot itself.
For this you need to have init.d support.. If you don't have just install it via universal init.d tool available in xda.. (just do a search, u will get it) install universal init.d and activate init.d..
Then go to /etc/init.d directory, create a file and rename it as "08setperm" (without quotes) and add the below lines in the file and save it..
#!/system/sh
setenforce 0
And give full permission (rwxrwxrwx) .. Use root Explorer to edit and give permissions..
Now hard reboot your phone and you can see SELinux is set to "permissive" on boot itself..
Now install Xposed framework by following the steps mentioned in the official xposed thread..
This method is tested in moto G and working fine for me... I'm not responsible for anything if happened with your mobile after trying this..
Ps: if you flash any new nightly or new rom, you need to add the file in to init.d directory again..
I posted this using my mobile. So pardon me if any formatting issues..
Hit thanks if i helped you..
Very obviously, can't set permissive on Galaxy S5. Hopefully soon though.
Thanks, I was looking for the enforce command to make a script. It worked perfectly for me on an S4.
LGtMgG2t said:
Thanks, I was looking for the enforce command to make a script. It worked perfectly for me on an S4.
Click to expand...
Click to collapse
Press thanks button dude instead of saying it..
Doesn't work on Z3 Compact (D5803) CM12 nightly.
Nexus 6
"Alright So i have everything down according to your installation guide, When i want to set the file "08setperm" is when root browser tells me that the operation failed even though it has SU Granted."
Okay so I did some tinkering, Got it to work Reboot but after the 2nd Reboot it Boot-looped, On my Nexus But it can work .
Scriptkiddie7 said:
"Alright So i have everything down according to your installation guide, When i want to set the file "08setperm" is when root browser tells me that the operation failed even though it has SU Granted."
Okay so I did some tinkering, Got it to work Reboot but after the 2nd Reboot it Boot-looped, On my Nexus But it can work .
Click to expand...
Click to collapse
Upgrade your root Explorer or super Su and try
Using the commands below should get permissive even after reboot
per http://forum.xda-developers.com/showpost.php?p=58887725&postcount=230
su
mount -o remount,rw /system
mkdir /system/su.d
echo "#!/system/bin/sh" > /system/su.d/permissive.sh
echo "echo 0 > /sys/fs/selinux/enforce" >> /system/su.d/permissive.sh
chmod 755 > /system/su.d/permissive.sh
Zwulf said:
Doesn't work on Z3 Compact (D5803) CM12 nightly.
Click to expand...
Click to collapse
Which part didn't work? As far as I can tell, we don't have init.d support on the Z3 Compact yet. Was it the Universal init.d Tool that didn't work for you?
mattdm said:
Which part didn't work? As far as I can tell, we don't have init.d support on the Z3 Compact yet. Was it the Universal init.d Tool that didn't work for you?
Click to expand...
Click to collapse
CM has init.d support buddy.
aalupatti said:
Using the commands below should get permissive even after reboot
per http://forum.xda-developers.com/showpost.php?p=58887725&postcount=230
su
mount -o remount,rw /system
mkdir /system/su.d
echo "#!/system/bin/sh" > /system/su.d/permissive.sh
echo "echo 0 > /sys/fs/selinux/enforce" >> /system/su.d/permissive.sh
chmod 755 > /system/su.d/permissive.sh
Click to expand...
Click to collapse
Doesn't work this way. You should have read following posts.
Solution:
su
mount -o remount,rw /system
mkdir /system/su.d
echo "#!/system/bin/sh" > /system/su.d/permissive.sh
echo "setenforce 0" > /system/su.d/permissive.sh
echo "0" > /sys/fs/selinux/enforce
chmod 755 /system/su.d/permissive.sh
Click to expand...
Click to collapse
Works!
Finally got a permissive system on reboot.
Edit: Doesn't help to get XPosed working on my Z3C though.
Another z3c here on the latest nightly, none of these methods even give me permissive status on boot...
EDIT: I lied I just had to install SuperSu
Solution:
su
mount -o remount,rw /system
mkdir /system/su.d
echo "#!/system/bin/sh" > /system/su.d/permissive.sh
echo "setenforce 0" > /system/su.d/permissive.sh
echo "0" > /sys/fs/selinux/enforce
chmod 755 /system/su.d/permissive.sh
Click to expand...
Click to collapse
This method worked for me also thank you sir :good:
Just dd the kernel partition and hex-edit the kernel command line (androidboot.selinux=permissive).
So i am using Xperia Z2 with CM12.
Now, the issue with this particular CM12 is that, in case if we do a soft reboot then xposed starts working but networks vanishes. The Network comes back upon a normal restart but with soft reboot the issue comes back.
I have used these steps to
su
mount -o remount,rw /system
mkdir /system/su.d
echo "#!/system/bin/sh" > /system/su.d/permissive.sh
echo "setenforce 0" > /system/su.d/permissive.sh
echo "0" > /sys/fs/selinux/enforce
chmod 755 /system/su.d/permissive.sh
Make permissive survive a normal reboot but it doesnt work till i do a soft reboot. any help?
Exact same issue for me
I have same phone with CM12, when I soft reboot
1st soft reboot: no network
2nd soft reboot: screen goes black after unlocking the device
in last 2 days of multiple soft reboots, i got one soft reboot where xposed and network everything worked.
manu44 said:
So i am using Xperia Z2 with CM12.
Now, the issue with this particular CM12 is that, in case if we do a soft reboot then xposed starts working but networks vanishes. The Network comes back upon a normal restart but with soft reboot the issue comes back.
I have used these steps to
su
mount -o remount,rw /system
mkdir /system/su.d
echo "#!/system/bin/sh" > /system/su.d/permissive.sh
echo "setenforce 0" > /system/su.d/permissive.sh
echo "0" > /sys/fs/selinux/enforce
chmod 755 /system/su.d/permissive.sh
Make permissive survive a normal reboot but it doesnt work till i do a soft reboot. any help?
Click to expand...
Click to collapse
Ok, so..
I want script who started on boot(set permissive), because i do not have soft reboot after every normal reboot to working Xposed. How to do it? I have CM12 Nightly on Xperia Z1.
If i wrote in terminal this script:
su
mount -o remount,rw /system
mkdir /system/su.d
echo "#!/system/bin/sh" > /system/su.d/permissive.sh
echo "setenforce 0" > /system/su.d/permissive.sh
echo "0" > /sys/fs/selinux/enforce
chmod 755 /system/su.d/permissive.sh
Click to expand...
Click to collapse
It's work on every boot phone or once?
Code:
su
mount -o remount,rw /system
mkdir /system/su.d
echo "#!/system/bin/sh" > /system/su.d/permissive.sh
echo "setenforce 0" > /system/su.d/permissive.sh
echo "0" > /sys/fs/selinux/enforce
chmod 755 /system/su.d/permissive.sh
Work cm12. No need soft reboot:good::good:
@UP:
Only wrote this in Terminal and all is it?
Rygiel98 said:
@UP:
Only wrote this in Terminal and all is it?
Click to expand...
Click to collapse
SuperSu + android terminal or adb shell
Can I use gasket to enable upsm at 5% ? I'm complete noob so will need talking through thanks
ROOT + shell
echo "0" > /sys/devices/virtual/mdnie/mdnie/accessibility
echo "1" > /sys/devices/virtual/mdnie/mdnie/accessibility
echo "2" > /sys/devices/virtual/mdnie/mdnie/accessibility
echo "3" > /sys/devices/virtual/mdnie/mdnie/accessibility
0 : Normal Screen
1 : Inverted Colors
2 : Ultra Power Save Mode
3 : Screen off but not locked and touchscreen is still working
Thanks for reply but that means nothing to me?
No one with a basic guide
Do you have ROOT?
If not, you can"t auto turn on UPSM.
Yes I have root
@bandit250
you are still interested?
Yes please
First, Make a test.
Task:
1. Run shell [mark ROOT]
Command:
echo "2" > /sys/devices/virtual/mdnie/mdnie/accessibility
Push play
upsm should turn on.
Hi I get this error
17.49.16/E Run Shell: ->
17.49.16/E Run Shell: ->
17.49.16/E Run Shell: ->
17.49.16/Shell runBackground echo "2" > /sys/devices/virtual/mdnie/mdnie/accessibility root: true timeout: -1
17.49.16/Shell start process-thread ID 4097
17.49.16/E add wait type Shell1 time 2147483647
17.49.16/E add wait type Shell1 done
17.49.16/E add wait task
17.49.16/E Error: 1