When I use Set CPU my phone will freeze up randomly, the screen goes completely black and I lose a large chunk of battery when I get it turned back on. This is really annoying, do I have a setting wrong?
Related
I have the screen set to always on (no time out) when I have it in the car, it stays on fine while listening to music or if it just sitting there doing nothing, but no matter if I get a call or I make a call -- the screen will always turn off after a couple seconds even though the screen is set to always stay on, also as soon as the call ends -- the phone automatically locks and I have to log in / unlock it every time. I know on the old Froyo ROMs it would stay on if I had it set to always on -- didn't matter a call or not, it stayed on like it is supposed to do and it did not automatically lock either. I am on the Weapon 3.0ROM and I am using the same widgetsoid app as the the switching mechanism for the "always on" screen setting in a widget on one of the home screens. I have checked the widgetsoid settings and there is no definition between call settings and normal data for the screen time out. Under settings in the main menu, there is no toggle to enable/disable the proximity sensor either, but since the phone face has nothing close to it when it is mounted in the car (like it would be if you had it up to your ear), I don't think that this is the proper setting to manipulate. I really believe that this is a timing setting, and I am wondering if it is separate setting that can be changed or linked to the normal screen time out settings.
Is there a way to stop the screen from timing out on the Weapon3.0 Rom during phone calls and then automatically locking the phone when the call ends? its getting a bit annoying and any help would be appreciated.
Am I really the only one experienceing this?
I have tried fully wiping the G2x and started from scratch reloading the ROM, apps, settings, etc. and with the Weapon 3.0ROM when the phone is plugged in charging it still automatically shuts the screen off a few seconds into a call, and then locks the phone even though I have the LCD screen setting set to always be on.
For the most part I really like the Weapon ROM, but this auto screen off and locking when I have the G2x plugged in, in the car is annoying as ****, any help to remedy this problem would be appreciated.
crockashat said:
I have tried fully wiping the G2x and started from scratch reloading the ROM, apps, settings, etc. and with the Weapon 3.0ROM when the phone is plugged in charging it still automatically shuts the screen off a few seconds into a call, and then locks the phone even though I have the LCD screen setting set to always be on.
For the most part I really like the Weapon ROM, but this auto screen off and locking when I have the G2x plugged in, in the car is annoying as ****, any help to remedy this problem would be appreciated.
Click to expand...
Click to collapse
I think that is an unwanted "feature" of the 2.3.3 Gingerbread rom. I am not sure of anyway around it without changing to a rom that is not 2.3.3 based.
Have my Screen Timeout set to Keep Screen On on my LG G3 running 4.4.2 and something keeps resetting it back to 30 seconds. I've posted on the LG forums with no response. I've tried running Log Cat but I'm apparently too dumb to figure out how to find out what's causing the setting to change. Any thoughts?
Bump... anyone?
I think you can set the timeout on display setting, set time as you want it.
Thanks yeah... I know. I have it set to not turn off. But it still reverts to 30 seconds periodically.
I have set 2 minute timeout on my phone, and its work fine, but it will be reverts to 30 seconds if the battery is low (on state < 15%) . I'm not quite sure but i think your phone timeout setting periodically reverts is because your phone is in low battery state
My battery has never been below 50% so that's not it.
Thanks though!
Hello,
I have a strange problem with my phone. I use the original flip cover case. When the phone is upside down (screen facing down) and a call comes. I pick up the phone and open the flip cover, I can see who is calling but the touch screen do not respond. I can not control the call, I have to press the power button twice so the screen closes and opens, then I gain control on the screen.
This problem does not occur when I use the phone without flip cover case or when I leave the phone with screen facing up.
Do you have this problem with your phone?
I have this problem with all roms that I tried. But when I use an auto screen on off program for flip cover phones, my problem solved. The program make my phone awake all the time, it seems disturbing at the beginning but I saw that the battery consumption of my kitkat rom decreased while my phone is idle (screen off). Normally my kitkat rom uses 4-5% per hour when screen off but with this program it decreased to 1.5-2% per hour. So I also found an indirect solution for my kitkat rom that do not go into deep sleep
Also I noticed that the cpu usage is high (1209 Mhz) while the screen is off, so I used a cpu tuner program to reduce it while screen is off. And the battery consumption reduced to nearly %1 per hour while screen is off.
A rom developer can use this and write a code that awake the phone but not using battery like auto screen on off program.
So, like every other thing out there, stuff fails. I woke up this morning and checked my phone to check the time. Nothing unusual. I go to get changed and I come back to my phone and it just shows the Verizon boot logo. I thought "Ok, it must have just crashed somehow and it'll reboot!" And so I waited...and waited....and waited. It seems to be half-booted, but stuck somewhere along the way. The screen is dimmed (indicating the auto-brightness feature is working) and it has the orange hue over the white text (indicating the night-light mode is still on). I had medium Power Saver mode on to keep the battery overnight, and the CPU cap was enabled. I've noticed that some apps don't like to start with that setting enabled, so I'm inclined to believe that the 70% CPU cap is somehow messing up the system and keeping it from fully rebooting. I'm currently waiting for the battery to die since I can't remove my battery in the Note 5. I've checked the device temperature by hand every now and then, and it doesn't feel warm so the CPU isn't cycling up like it should. I don't have access to my computer until I finish moving and unpacking my new house, so I can't use ADB to try and do anything. What should I do?
BluSpectre said:
So, like every other thing out there, stuff fails. I woke up this morning and checked my phone to check the time. Nothing unusual. I go to get changed and I come back to my phone and it just shows the Verizon boot logo. I thought "Ok, it must have just crashed somehow and it'll reboot!" And so I waited...and waited....and waited. It seems to be half-booted, but stuck somewhere along the way. The screen is dimmed (indicating the auto-brightness feature is working) and it has the orange hue over the white text (indicating the night-light mode is still on). I had medium Power Saver mode on to keep the battery overnight, and the CPU cap was enabled. I've noticed that some apps don't like to start with that setting enabled, so I'm inclined to believe that the 70% CPU cap is somehow messing up the system and keeping it from fully rebooting. I'm currently waiting for the battery to die since I can't remove my battery in the Note 5. I've checked the device temperature by hand every now and then, and it doesn't feel warm so the CPU isn't cycling up like it should. I don't have access to my computer until I finish moving and unpacking my new house, so I can't use ADB to try and do anything. What should I do?
Click to expand...
Click to collapse
Ok, so I fixed my own problem. I tried a variety of small post-boot tricks like trying to force the device into a different boot mode (ex: Power+minus=safe boot, power+home+VolDown= Download Mode) and forcing it into Download mode worked. It overrode the issue and I was able to tell it to reboot again. This time it rebooted normally. This was really weird. I've never had this happen before on any other device I've ever owned. I hope this might help someone in the future.
Hello,
My Tablet - Samsung Galaxy Tab S2 9.7 Wi-Fi (stock Android v.7) gets unresponsive when I turn on the screen after being left idle for some hours. After installing a monitor app I noticed the Disk reading values will be at 100% for some time (3 or 4 minutes) and only when it lowers to values near 10% will the tablet become responsive.
Any suggestions?
How can I identify the apps that are taking over Disk readings?
Thanks!