Related
Hi. This is a question for a rooted Droid /Milestone, but should be applicable to other models as well. I'd like to know if there's a command or any other functionality I can use to "lock" the brightness setting so that other applications can't change it.
I know it's possible, because there's an app in the Market called AdjBrightness (looks like the developer posts here, as well) that is capable of locking it, but I don't quite need all the functionality it provides, and I can't work out how to reverse its home row backlight disabling, which means I ALSO have to run LEDs Hack... I'd like to just write something simple for my specific settings to replace both.
I'm trying to create a very short script I can run with Tasker and set to a widget that will accomplish 3 things: Disable the home row backlights, set the brightness to 2/255, and then "lock" that setting so that other apps can't affect it. I want to run Aldiko for reading in pretty much total darkness, and this is the ideal setting for me.
So far, I can get it set properly using the following:
su
echo 2 > /sys/class/leds/lcd-backlight/brightness
echo 0 > /sys/class/leds/button-backlight/brightness
and with Tasker I can run that as a script and set it to a widget, with another widget to complement it that runs:
su
echo 100 > /sys/class/leds/lcd-backlight/brightness
echo 1 > /sys/class/leds/button-backlight/brightness
which reverses the process and sets everything back to normal.
What I need is to figure out how to lock in that "2" brightness setting, which at this time persists only until some other app affects the brightness. When I run Aldkio, its built-in brightness control feature overrides my setting and lights the thing back up too bright.
So, can this be done with a script? I imagine a chown command that temporarily takes ownership of that function could work, but I'm not smart enough to know how, and I've exhausted Google and the forum search. As I mentioned, this thing would always be run with a complimentary script that could later reverse the chown and give it back to whatever process it ought to belong to... I KNOW it's possible because there's at least one app that does it perfectly; the AdjBrightness setting change persists after I open Aldiko, indeed it persists basically forever; you've got to kill the app or reboot to be able to adjust the brightness with any other means.
Can anyone point me in the right direction?
Bump? Still trying to figure this out.
Bump
Still wondering if there's a way to do this.
+ 1 - if you find a way to lock it via command line, do post back, as will i
i am currently using adjbrightness it to control my button backlights on my dell streak
its great as it locks it on for that session. but after reboot have to manually renable
so i have written an execute entry in tasker to control all or just some of the leds for various notifications
but would love a command line way to lock these as adjbrightness does, i cant find out how its doing that!!!
jdb1981 said:
Hi. This is a question for a rooted Droid /Milestone, but should be applicable to other models as well. I'd like to know if there's a command or any other functionality I can use to "lock" the brightness setting so that other applications can't change it.
I know it's possible, because there's an app in the Market called AdjBrightness (looks like the developer posts here, as well) that is capable of locking it, but I don't quite need all the functionality it provides, and I can't work out how to reverse its home row backlight disabling, which means I ALSO have to run LEDs Hack... I'd like to just write something simple for my specific settings to replace both.
I'm trying to create a very short script I can run with Tasker and set to a widget that will accomplish 3 things: Disable the home row backlights, set the brightness to 2/255, and then "lock" that setting so that other apps can't affect it. I want to run Aldiko for reading in pretty much total darkness, and this is the ideal setting for me.
So far, I can get it set properly using the following:
su
echo 2 > /sys/class/leds/lcd-backlight/brightness
echo 0 > /sys/class/leds/button-backlight/brightness
and with Tasker I can run that as a script and set it to a widget, with another widget to complement it that runs:
su
echo 100 > /sys/class/leds/lcd-backlight/brightness
echo 1 > /sys/class/leds/button-backlight/brightness
which reverses the process and sets everything back to normal.
What I need is to figure out how to lock in that "2" brightness setting, which at this time persists only until some other app affects the brightness. When I run Aldkio, its built-in brightness control feature overrides my setting and lights the thing back up too bright.
So, can this be done with a script? I imagine a chown command that temporarily takes ownership of that function could work, but I'm not smart enough to know how, and I've exhausted Google and the forum search. As I mentioned, this thing would always be run with a complimentary script that could later reverse the chown and give it back to whatever process it ought to belong to... I KNOW it's possible because there's at least one app that does it perfectly; the AdjBrightness setting change persists after I open Aldiko, indeed it persists basically forever; you've got to kill the app or reboot to be able to adjust the brightness with any other means.
Can anyone point me in the right direction?
Click to expand...
Click to collapse
In my device adjbrightness app lock the brightness just by changing the permission of "/sys/.. /brightness" file to 444. So even system can't change the brightness value if requested by any other apps. To unlock the brightness permission of "/sys... /brightness" is restored to previous state, 644.
So in terminal the commands can be "for changing brightness to 2 and lock it"
su
echo 2>/sys/class/leds/lcd-backlight/brightness
chmod 444 /sys/class/leds/lcd-backlight/brightness
"for unlock and restore "
su
chmod 644 /sys/class/leds/lcd-backlight/brightness
echo 100> /sys/class/leds/lcd-backlight/brightness
Same goes for button backlight brightness file
But I found it "not suitable" for my device even with adjbrightness. If I lock brightness using adjbrightness after my screen turns off normally or by using power button , I can't turn it on using power button, so I have to open the battery and reboot the device. Same thing happens if I do it using "commands" or script. So "something" should be done so that the permission of ".. /brightness" file is set to 644 before the screen turns off normally or by other means.And after the screen is on the file permission will be 444 again. I think it may be done using tasker but still don't know how.
Hope someone will help.
Thanks.
Hi
I am not sure why, but I can't turn off screen, with "echo 0 >" into brightness.
It seems that there is some minimum brightness somewhere which I need to configure ?
I really struggle with it.
Any idea how to do that ?
Thanks,
Ranchu
Have you ever tried having your phone lay on a table for some time and when you come back to pick it up, it had almost burned through the table because of the battery heat do to an app running the CPU on a constant 100%?
Or have you tried waking up two hours to late for work, because you alarm did not go off do to the phones battery running dry during the night?
Bad applications or problems with some back-end processes is a problem for most people. To get some help with this problem, I have been running the Watchdog app for the last 3 years. It is a great application that will alert you whenever an app or a process is running wild in the background. However there is one issue with this app. It only alerts you when there is a problem. This does not help much if you are to far away from the phone, if your phone is in silent mode or if you are sleeping.
I wrote the developer of the app to see if there was any plans for making a tasker plug-in so that profiles can be made to handle this. I have yet to get an answer. In the mean time, I have made a complete watchdog profile for tasker that does what the watchdog app does, only this profile will auto terminate any wild processes if the screen is turned off. If the screen is on, it will to what the watchdog app does and alert you of the problem. It could be that you was playing a game or running a benchmark, so auto terminate while the screen is on, would not be a good idea.
The profile however, will drain more battery than the watchdog app does. Because of this I have set the check interval for 15 minutes instead of the 5 minutes I used on the app. This reduces the drain to about the same amount.
And to save even more power, I have included a Data control profile that will turn off data/wifi/sync when the screen is off, as long as you are not connected to a power source or if you are downloading, uploading or streaming. In this case the profile will wait until this state changes before turning off anything. And while off, tasker will alow sync (email and such) once every 15 minutes.
Both profiles is included in the attached download below.
Important!
The watchdog profile will need a proper busybox installed with proper symlinks for sed, grep and awk. It will also need a toolbox that supports top and ps with arguments.
You can run the update script from the Busybox Installer thread to make sure that your phone will work with this profile.
Changelog (2012-11-18)
Reduced the time from where the screen turns off, to the time Data/Sync is disabled
Data/Sync will now turn back on when the screen is unlocked rather than turned on. No need to waste power if you just want to check the time or notifications (Which can be done from lock screen in Android 4.x)
Fixed the 15 minutes data check when the screen is off. It only executed once after the screen was turned off
_______________________
Wow! Your watchdog implementation looks great! Will adopt it on my phone over the weekend.
Now I have only one battery-drain-controlling dream left - being able to find out the apps holding the wakelock for too long to kill them automatically. The reason for this is that sometimes I find battery drain to go from usual 1% per hour to 10% per hour just because some badly written app has not released the wakelock.
Alte.78 said:
Wow! Your watchdog implementation looks great! Will adopt it on my phone over the weekend.
Now I have only one battery-drain-controlling dream left - being able to find out the apps holding the wakelock for too long to kill them automatically. The reason for this is that sometimes I find battery drain to go from usual 1% per hour to 10% per hour just because some badly written app has not released the wakelock.
Click to expand...
Click to collapse
Are you talking about BetterBatteryStats? I know that it tells you exactly how long since a point in time (which can be manually customized) that certain programs/tasks hold wakelocks.
But not sure about any kind of specific stratification that displays only programs that hold the lock too long to kill them automatically (assuming that's what you are wanting?).
And OP, these sound great - I'm importing them as we speak :highfive:
dk_zero-cool said:
Important!
The watchdog profile will need a proper busybox installed with proper symlinks for sed, grep and awk. It will also need a toolbox that supports top and ps with arguments.
_______________________
Click to expand...
Click to collapse
I got all excited when reading about this until I read the Important section. After watchdog everything started getting confusing . I know I read somewhere about busybox but the other terms are all new to me...could someone explain it with a little more details on what I have to get/set up in order for this to work??
2am said:
I got all excited when reading about this until I read the Important section. After watchdog everything started getting confusing . I know I read somewhere about busybox but the other terms are all new to me...could someone explain it with a little more details on what I have to get/set up in order for this to work??
Click to expand...
Click to collapse
The profile is using some linux commands to get a list of all current processes and their CPU usage. These commands needs to be available in order for the profile to work.
If you are using a custom ROM, then you are most likely to have all what is needed. Especially if you are using a more current custom ROM.
In order to test this, download a terminal app or enter an ADB shell (Hope you know what this is) and see if the command line
Code:
top -n 1 | sed -e 1,7d | grep -e '[0-9]\+%' | awk '{print $3}'
returns anything. If it does (Except errors), then you will have all that is needed.
Alternatively you could check my Better Busybox Integration thread which will make sure that your phone is setup to work with this.
dk_zero-cool said:
The profile is using some linux commands to get a list of all current processes and their CPU usage. These commands needs to be available in order for the profile to work.
If you are using a custom ROM, then you are most likely to have all what is needed. Especially if you are using a more current custom ROM.
In order to test this, download a terminal app or enter an ADB shell (Hope you know what this is) and see if the command line
Code:
top -n 1 | sed -e 1,7d | grep -e '[0-9]\+%' | awk '{print $3}'
returns anything. If it does (Except errors), then you will have all that is needed.
Alternatively you could check my Better Busybox Integration thread which will make sure that your phone is setup to work with this.
Click to expand...
Click to collapse
well I entered that command and got
invalid argument "-n". and then a bunch of other lines after that...and I checked your other thread and there's even more code language ...ugh, I think this is one of those threads that I need to leave alone because it's too much for me to handle...sucks too cause your set up sounds really awesome...thanx for trying to help me though
2am said:
well I entered that command and got
invalid argument "-n". and then a bunch of other lines after that...and I checked your other thread and there's even more code language ...ugh, I think this is one of those threads that I need to leave alone because it's too much for me to handle...sucks too cause your set up sounds really awesome...thanx for trying to help me though
Click to expand...
Click to collapse
I will make a more simple command fix for you tomorrow that will make your phone work with this without having you enter any code.
dk_zero-cool said:
I will make a more simple command fix for you tomorrow that will make your phone work with this without having you enter any code.
Click to expand...
Click to collapse
ah thank you soo much!!!
2am said:
ah thank you soo much!!!
Click to expand...
Click to collapse
I have updated the Busybox Installer script to make sure that it will work on newer devices other than MTD, and I have added a custom toolbox binary that will contain the proper options for these profiles.
Just check the first post at the buttom in the Important section. Fallow the link, download the installer and run it in your recovery. After that you can import the profiles from this thread into your Tasker application.
I'm trying to write a tasker script for Extreme Power Saver while at work. Secure settings has a feature, but doesn't seem to work. I'm hoping I can just have tasker execute a terminal (command line) script to activate EPS.
I accomplished this by launching an activity via secure settings. I can't detail exactly how I did it at the moment but it wasn't difficult, just tinker with the secure settings plugin. If I have some free time tomorrow, I'll explain in more detail.
TidusWulf said:
I'm trying to write a tasker script for Extreme Power Saver while at work. Secure settings has a feature, but doesn't seem to work. I'm hoping I can just have tasker execute a terminal (command line) script to activate EPS.
Click to expand...
Click to collapse
I just tried this and it seams to work.
http://forum.xda-developers.com/htc...wer-saving-t2808839/post53988422#post53988422
jsaxon2 said:
I just tried this and it seams to work.
http://forum.xda-developers.com/htc...wer-saving-t2808839/post53988422#post53988422
Click to expand...
Click to collapse
I saw that. but I don't want to have another app just for one command, when I use tasker already for 3 others. I want to keep it all together.
I've been using tasker to start epsm for months.
My setup I have is profile for screen off, run task Epsm
Tasks
Epsm
Run shell script
am start -a android.intent.action.MAIN -n com.htc.htcpowermanager/com.htc.htcpowermanager.extremepowersaver.ExtremePowerSaverConfirmActivity
And be sure to check run as root obviously.
Enjoy
And yes that can be ran in terminal however since you already use tasker you can automate it however you like
Thought I would elaborate a bit on this.
You can us the
am start
command to launch any app activity.
If you need to find what activity any app has just check their manifest inside the apk.
The only thing I haven't been able to figure out that I really would like to is to shut it off via terminal.
If you think of it logically the epsm is just a launcher so you can kill it via kill-server or force-stop command which will in fact bring you back home to your standard launcher however non of the setting will revert.
Same for if you instead just launch the default launcher via am start.
So if you can isolate exactly what triggers are sent (which I haven't isolated just yet(well I have but haven't been able to emulate via shell)) let me know if you have any progress or ideas.
:edit
i knew if i just sat down for a minute without distractions i would get it
easier and cleaner way to do it would be with the broadcast call
so to enable
Code:
am broadcast -a com.htc.intent.action.HtcPowerSaver.ExtremeAutoModeOn
to disable just
Code:
am broadcast -a com.htc.intent.action.HtcPowerSaver.ExtremeAutoModeOff
sent from space
runandhide05 said:
Code:
am broadcast -a com.htc.intent.action.HtcPowerSaver.ExtremeAutoModeOn
Click to expand...
Click to collapse
Thank you. I have a profile that checks for BUSY activities in my google calendar (such as my work schedule), so I just hit SCRIPT and put in the code (and checked run as root). works great. Thank you very much for your assistance with this.
TidusWulf said:
Thank you. I have a profile that checks for BUSY activities in my google calendar (such as my work schedule), so I just hit SCRIPT and put in the code (and checked run as root). works great. Thank you very much for your assistance with this.
Click to expand...
Click to collapse
No problem. I'm about to sit down and find the intent for the normal power saving profile as well because I find myself slightly annoyed waiting for extreme power saving mode to exit. So maybe a profile for extreme during off peak hours and just power saving during peak usage hours
for normal power saving mode its
am broadcast -a com.htc.intent.action.HtcPowerSaver.AutoModeOn
and Off for off of course
sent from space
This guide is meant to help those who have rooted their phones and are now finding it slow, laggy, messy, etc.
I've been seeing a lot of posts repeating common problems that have been fixed by other members of the forums, so I'll compile a list of the most common bugs and fixes for them (the ones that can be fixed) in this guide so people can refer to it instead of swamping dev threads with the same questions over and over again. The quicker we can get through the common problems, the quicker we can get to fixing the ones we don't have solutions to so far.
Disclaimer: After installing the ENG bootloader, you are going to experience less battery life. There are things we can do to improve this, but nothing I have discovered so far will get you back to stock battery life... except re-installing stock ROM. Also standard disclaimer that all of the fixes here are done at your own risk. I am not responsible for any of these fixes breaking your phone.
Bug #1: Phone is laggy after rooting the phone/Battery is down the tank.
Fix: The phone is (partially) lagging because the ENG bootloader automatically sets the CPU governor to "Performance." While this is supposed to lock the CPU frequency at the maximum values, it does cause a lot of heat and possibly throttling. Additionally, the max core clocks are set to 1.593Ghz instead of their actual maximums. Not every CPU Tuner will allow you to set the big cores separately, so look around for one that does if you don't want to use Kernel Toolkit.
First, use Flashfire to flash one of two zips provided by psouza4 on our sister Verizon Galaxy S7 (Edge) threads.
1. Kernel fixes & tweaks V15
2. Kernel fixes, tweaks, & Debloater
You need only flash one of these two zips. One additionally debloats the system, one does not. Choose whichever suits your needs.
What the zips do:
Adds a rotate button to the native gallery app.
Adds a shortcut call button in the call log next to each logged call.
Adjusts several CPU tunables, which fixes phone lag and battery life issues.
Disables "No SIM" popup when no SIM card is present.
Disables roaming data by default.
Disables secure storage support, which fixes Wi-Fi passwords not saving issue.
Disables Verizon provisioning for Wi-Fi tethering/hotspot (will still use your data plan, of course).
Enables ADB to run as root by default.
Enables CPU idling/sleeping, which fixes phone heat issues.
Enables mock GPS locations.
Enables native call recording feature in the dialer.
Enables native Wi-Fi calling feature in the dialer.
Enables RIL power saving features.
Enables scheduled messages in the native messaging app.
Enables the camera during calls.
Enables unlimited contact merging.
Enables using the new 3GPP2 Profile ID (Verizon exclusive).
Fixes various 'searching for service' and other cellular network connectivity issues (SMS/MMS not working, calls not working, etc.)
Knox apps, drivers, and data are removed (fix+debloat version).
Prefers LTE network.
Raises the contact name length limit to 1,280 characters.
Raises the maximum SMS recipient limit from 10 to 90.
Remove nagging 'unauthorized actions' security notification (fix+debloat version).
Removes VoLTE icon.
Removes bloatware and/or apps that can be downloaded from the Play Store and don't need to live in /system (fix+debloat version):
Next, install a CPU Tuner utility like Kernel Toolkit, then change the governor from "Performance" to "Interactive." Also change the max CPU frequency of the little cores to 1.593Ghz and the big cores to 2.150Ghz while you're at it. Leave the cores at their default minimum frequency. This will go a long way to improving the speed of the phone. Also make sure you that have the new settings to apply on boot. Every kernel manager should have this option somewhere.
Note: Although the max frequency in the settings screen will drop to some number, as long as you can see the CPU ramp up to the new settings in the information screen, then everything is fine. You can test the max frequency by turning the screen off and then back on.
Then, install sEFix and set entropy to "Ultra."
Lastly, install L Speed and:
Code:
-Main Tweaks: Turn on
-Battery Improvement
-OOM Killer
-Kernel Tweaks - "Light"
-CPU Tuner: Turn on
-CPU Optimizer
-LNET Optimizer: Turn on
-Google DNS
-Faster Streaming
-Faster Dormancy
-IO Tweaks: Turn on
-IO Boost
-Partition Remount
-RAM Manager
-Balanced
-Seeder
-Moderate
Their individual effects can be read up on here.
Bug #2: Weird "hurricane" icon in the corner.
Fix: This is related to the imsservice.apk which controls the RCS icon and the VoLTE icon being displayed. Someone has a modified version of the Note 5 imsservice.apk with these removed. You can find the apk HERE in the OP's attachment. HOWEVER, you will push this to a different location than the location mentioned in the guide there. You have two choices, you can either push the apk via ADB from you computer or you can copy the file using a root file manager.
ADB Method (Assumes you know what you're doing. Don't copy the code verbatim if you don't know what the command is doing):
Code:
adb remount
adb push imsservice.apk /system/priv-app/imsservice/imsservice.apk
adb reboot
Root File Manager Method:
Transfer the imsservice.apk to your phone. Anywhere where you'll remember the location is fine. Open the file manager with root compatibility and copy the file to /system/priv-app/imsservice/ and overwrite the imsservice.apk already in the folder.
Set permissions of the file to 0644 or rw-r--r-- depending on your file manager. You can set permissions using most file managers.
Restart the phone.
I've included the stock PD8 imsservice.apk as an attachment below if anyone has issues with the modified one from the guide.
Bug #3: Notification warning that system has been modified.
Fix #1: Disable com.samsung.android.securitylogagent & com.tmobile.pr.adapt using your favorite package disabler. This will hide all notifications associated with this app as well as the root check that you might have encountered.
Fix #2: This fix requires Xposed. You can follow the instructions to install Xposed HERE.
Then install the Xposed module NotifyClean, activate the module, and reboot the phone. You will then use this app to block the notification under the package com.samsung.android.securitylogagent by clicking on the package so that it is highlighted red. The notification should disappear!
Note: This app can also be used to hide the icon for WiFi Calling if it's annoying you. You can still use the WiFi calling function while hiding the notification.
Bug #4: I keep losing root.
Fix #1: Secure boot/startup has caused the loss of root. So make sure you DO NOT SETUP the secure boot option when you're first setting up the phone or any time afterwards. This is the same option that forces users to type in/swipe in their password on a screen with a black background. This is not the normal type/swipe your password on your lockscreen after a boot.
Fix #2: Disable Security policy updates. I've also heard that people who leave this option on lose their root after a couple of reboots. You can find this setting under:
Settings > Lock screen and security > Other security settings > Security policy updates > Automatic updates (Turn this setting off).
Fix #3: Disable auto-updates for apps in Google Play Store. It's possible that SuperSU auto-updated, breaking root.
Fix #4: Disable automatic updates for the phone. I don't think these run anyways on modified software, but it can't hurt. You can disable the applications responsible for automatic updates using Titanium Backup, EZ Disabler, or any other package disabler you know of. The packages to disable are:
com.sec.android.soagent
com.wssyncmldm
com.samsung.firmware.nfc
com.samsung.android.firmware.tsp
Bug #5napchat: Unable to log into Snapchat.
Fix #1: This happens if you attempt to login to Snapchat after installing Xposed. Just make sure you login to Snapchat prior to installing Xposed. Done.
Fix #2: If you've already installed Xposed, you can:
-Do a clean install through ODIN, and re-root your phone, install and log into Snapchat, then install Xposed.
-Uninstall Xposed by flashing THIS through Flashfire, uninstalling the Xposed framework app, and clearing the data on your Snapchat app. Then login to Snapchat and re-install Xposed.
Bug #6: WiFi passwords aren't being saved
Fix: Use a root file manager like Solid Explorer and go to /system and open/edit build.prop. Scroll down or use the "find" function to search for ro.securestorage=true and change it from true to false (ro.securestorage=false). Save the file. Done!
If you guys have any more bugs that you run into, please feel free to post them here. Anyone who knows of any additional fixes to these bugs or solutions to any bugs that others post, also feel free to add them in the comments and I will compile them into this guide when I get a chance.
I've included the PD8 imsservice.apk below if you need it
Reserved
Reserved
I downloaded CPU scale and I dont see 1.5hz and 2.1ghz as options to switch too
thegameksk said:
I downloaded CPU scale and I dont see 1.5hz and 2.1ghz as options to switch too
Click to expand...
Click to collapse
Not every CPU Tuner utility will let you set the individual big.LITTLE cores separately. Try using the one recommended or look for another one that does allow it. Kernel Toolkit is the only one that I remember off the top of my head. I'll also make an edit in the post to avoid further confusion.
hey all, does anyone have or has experienced your incoming calls not being recieved? i have called myself and others also and it either rings until voicemail or it just goes straight to voicemail,
any ideas whats causing this?
thanks,
Great post! Unfortunately I'm having problems with smart view after rooting. Every time I try to screen mirror it works but it is extremely laggy making it unusable. This has only been an issue since root and I've tried mirroring to three different devices and it's the same with all of them. I followed the instructions in this thread to see if these tweaks would help but they didn't change my screen mirroring issue at all. Is anyone else out there experiencing this?
little help please.
Followed the guide for bugs 1 & 2 exactly as mentioned. Used the root manager method for bug #2. Now i keep getting this pop-up that the phone is not responding...Any solutions to get rid of this?
thanks
cris_epic said:
hey all, does anyone have or has experienced your incoming calls not being received? i have called myself and others also and it either rings until voicemail or it just goes straight to voicemail,
any ideas whats causing this?
thanks,
Click to expand...
Click to collapse
Just started for me too. Doesn't go straight to voice mail but i don't get calls and cant call out now. Seemed to happen right after i replaced the imsservice.apk and rebooted. The annoying hurricane icon is gone now, just at the expense of making and receiving calls lol.
Did you also happen to overwrite the imsservice.apk?
JKLIMES1 said:
Followed the guide for bugs 1 & 2 exactly as mentioned. Used the root manager method for bug #2. Now i keep getting this pop-up that the phone is not responding...Any solutions to get rid of this?
thanks
Click to expand...
Click to collapse
Looks like I forgot to mention changing permissions on the file after you copy it over. From there, the easiest way to restore it would probably be to adb push the file over since you don't need to reset permissions if you push through adb. This should correct the crashing and allow you to use your phone.
JKLIMES1 said:
Just started for me too. Doesn't go straight to voice mail but i don't get calls and cant call out now. Seemed to happen right after i replaced the imsservice.apk and rebooted. The annoying hurricane icon is gone now, just at the expense of making and receiving calls lol.
Did you also happen to overwrite the imsservice.apk?
Click to expand...
Click to collapse
Yeah I believe I replaced the imsservice.apk when I flashed the fixs and debloater zip thats been going around
Sent from my SM-G935T using XDA-Developers mobile app
Is this what you mean about the cores?
thegameksk said:
Is this what you mean about the cores?
Click to expand...
Click to collapse
Leave the min frequency of the cores at the minimum otherwise your cores will always be at max frequency which is something you definitely don't want.
h.nocturna said:
Looks like I forgot to mention changing permissions on the file after you copy it over. From there, the easiest way to restore it would probably be to adb push the file over since you don't need to reset permissions if you push through adb. This should correct the crashing and allow you to use your phone.
Click to expand...
Click to collapse
AWESOME!! changing the permissions did the job for me. Thanks.
h.nocturna said:
Leave the min frequency of the cores at the minimum otherwise your cores will always be at max frequency which is something you definitely don't want.
Click to expand...
Click to collapse
I switched the minimum to 307 and max 1593 for small cores. For big cores minimum 307 MHz and Maximum is 2150 mhz.
Its not letting me save these numbers. I had min set to 307 and when I left the screen and went back it jumped back up to 1593
cris_epic said:
Yeah I believe I replaced the imsservice.apk when I flashed the fixs and debloater zip thats been going around
Sent from my SM-G935T using XDA-Developers mobile app
Click to expand...
Click to collapse
Trying changing the permissions as mentioned, that worked perfect for me.
thegameksk said:
I switched the minimum to 307 and max 1593 for small cores. For big cores minimum 307 MHz and Maximum is 2150 mhz.
Its not letting me save these numbers. I had min set to 307 and when I left the screen and went back it jumped back up to 1593
Click to expand...
Click to collapse
If you look at the information menu, do you see the cores ramp up to the 2.150 Ghz we set? If it does, then the settings have been saved despite it not reflecting on the settings screen. You can force it to ramp up to max but turning the screen off and then turning it back on.
h.nocturna said:
If you look at the information menu, do you see the cores ramp up to the 2.150 Ghz we set? If it does, then the settings have been saved despite it not reflecting on the settings screen. You can force it to ramp up to max but turning the screen off and then turning it back on.
Click to expand...
Click to collapse
Yes all 2 cpus go to 1593 and 2 go to 2150. This happens for 2 seconds than all 4 go down to 307
thegameksk said:
Yes all 2 cpus go to 1593 and 2 go to 2150. This happens for 2 seconds than all 4 go down to 307
Click to expand...
Click to collapse
This is the expected behavior. This just means that they will clock up to the max when there is a high load, but then drop back down to the lowest frequency to save battery when there is nothing to be done. Everything is working as it should.
Thank you for your help. Does your phone run hot when gaming or charging? My charger also gets very very hot while charging.
thegameksk said:
Thank you for your help. Does your phone run hot when gaming or charging? My charger also gets very very hot while charging.
Click to expand...
Click to collapse
Mines was hot just with normal usage. I used every tip and fix that people suggested but it was still pretty slow and lagged if I had a game running and a couple of more apps running. Battery was OK though.
Hi.
I come with a problem that I encountered with my Samsung Galaxy S7 G930F. The problem is that when I set the brightness to 100% and lock the phone, after unlocking it, it sets the brightness to the minimum, but the brightness bar remains at 100%. I did some digging in the files and found a file called "max_brightness" in the "/sys/class/backlight/panel/" directory. Sooo... i launched ADB and typed the following commands:
adb shell
su
cat "/sys/class/backlight/panel/max_brightness"
To my surprise, I got "365" value. I tried to change the value in this file to 255 with "echo 255> / sys / class / backlight / panel / max_brightness", but after executing it nothing happens and the value itself remains unchanged.
I think that changing this value can fix this error, unless someone has a better idea, then please give it below, I will gladly try it, because this error irritates me every time i change the brightness and lock my device.
EDIT: I forgot mention, that i use Havoc-OS v3.7.
Regards!
Perhaps you have auto brightness turned on or some other feature that uses phone sensors, regardless of them, the file you're checking has nothing to do with what you're facing.
This file is inside the Kernel, which means it's value is already specified (as you found it to be 365), and you can't normally change it's value, and definitely not permanently with your current steps.
I'll highlight you a few points:
Any file does have permissions, these permissions controls who can do what to/with the file, and there are owners, these are the users who can do what they actually want to the file. So when you can't change a file's value, you probably don't have the write permission.
SELinux can actually prevent you from modifying a lot of stuff, specially these kernel parameters, so you should set enforce to 0 if you want to have a wider range of freedom.
Using init.rc scripts can be quite helpful in your current situation, all you have to do is set permission, and write the value, and it will be applied when you reboot. (don't forget the selinux state)
I don't understand why you tried 255? as far as I know, that's for color range such as RGB and so ... P.S. that 365 value is your Screen's maximum brightness, the maximum it can get, if you lowered it, it'll seem really dim next time you set brightness to max. Your current brightness is in some other file.
The right way to change a value of such a file is by executing:
Code:
su
setenforce 0
chmod 0644 /sys/class/backlight/panel/max_brightness
echo "255" > /sys/class/backlight/panel/max_brightness
You should report a bug to the ROM developer, either by Forum, DM, or Telegram.