Related
Anyone else having issues with the phone shutting itself off at random intervals? It is happening on mine and I have to pull the battery in order to power it back on.
So far have rooted, installed su file browser, and system panel. Only other thing I have done is removed Amazon mp3.
Thanks in advanced, just want to know if I need to exchange my phone or not.
Sent from my SGH-T959 using XDA App
kopykatkiller said:
Anyone else having issues with the phone shutting itself off at random intervals? It is happening on mine and I have to pull the battery in order to power it back on.
So far have rooted, installed su file browser, and system panel. Only other thing I have done is removed Amazon mp3.
Thanks in advanced, just want to know if I need to exchange my phone or not.
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
This happen to me yesterday 3 times after the phone's screen was off for more than 10 min
I uninstalled setcpu and it never happened again so far.
Ok maybe it is a setcpu setting that is defaulting wrong. Anyone with setcpu installed that is not experiencing this? If so, what are your settings?
Sent from my SGH-T959 using XDA App
i also had this happen to me w/ setcpu active, i have yet to have it happen w/o setcpu
Happened with setcpu to me to. Removed it no problem since.
Same as everyone else. W/ SetCPU it happens. W/o SetCPU it doesn't.
Just sent the dev a message to let him know of the situation. http://twitter.com/MINUS_Stl/status/18719463969
Are you guys changing the scaling governor? From early reports, the Galaxy S phones can't take ondemand, you have to stick it to conservative.
You can "simulate" ondemand by changing freq step in Advanced to 100%.
Ya know. I did actually change it to ondemand seeing as that's what I always used on my G1. Gonna reinstall and see how we do. Will definitely report back. Thanks.
UPDATE: 1 hour in on 'conservative' and all is good.
I probably have to put a warning or something for Galaxy S for ondemand. It's probably a kernel flaw for that.
For now, it looks like conservative is 100% stable, haven't had reports of crashes on it.
Yeah, I'd say conservative is it. Thanks, bro.
Yes, before the reply about the conservative setting I had messed with it and set to that. Wanted to verify before posting, but as stated that appears that is the key. Thanks guys.
Loving this phone by the way.
Sent from my SGH-T959 using XDA App
coolbho3000 said:
Are you guys changing the scaling governor? From early reports, the Galaxy S phones can't take ondemand, you have to stick it to conservative.
You can "simulate" ondemand by changing freq step in Advanced to 100%.
Click to expand...
Click to collapse
I had SetCPU set to Conservative since I installed it. Yesterday it randomly powered off 6 times. I found this post and deleted SetCPU and am currently using Overclock widget. So far I haven't had it power off.
Has anyone else had this issue while having it set to conservative?
Yes! I changed my charger and it hasn't happened ever since.
Sent from my SGH-T959 using XDA App
i have also noticed that if i set a profile so that the cpu has a max of 400mhz while screen is off it will crash on me randomly. i have to keep it at at least 800mhz. It has just started doing this.
also does anybody know if it is dangerous to run in performance mode at a constant 1000mhz? it makes my phone super fast(obviously) but sounds dangerous making it run at maximum power constantly while the screen is on.
I've never used or installed SetCPU and my phone was shutting down by itself as well and had to do the battery pull to get it back on. I found it to be the "Power saving mode" in the display setting. Ever since I turned it off it has not shut down.
I also experienced this once when I try to install setcpu on my vibrant running bionix-v 1.2. Uninstalled it and it never happend again. =)
Just use the stock kernel.
Sent from my SGH-T959 using XDA App
this used to happen to me all the time so I got a replacement from tmobile but it continued to happen. It finally stopped when i rooted and flashed my phone
This thread is quite old, and while I do appreciate the contributions, it was long ago when this was posted and was dealing with a very early version of the over-clocked kernel. Please let this thread die, so that current ones maintain priority.
Sent from my SGH-T959 using XDA App
at least you guys are getting something. My phone shuts down 1-3 times a day. it is whether its rooted or not, customized rom or not. It just like to go to deep sleep really bad. Hopefully I can exchange it. But i just get my gps fixed, i dont know if i will get a new one with crappy gps.
Guys I was just wondering if there is any side effects of running g2 at those speeds for extended period of time?
Sent from my T-Mobile G2 using XDA App
kinacool said:
Guys I was just wondering if there is any side effects of running g2 at those speeds for extended period of time?
Sent from my T-Mobile G2 using XDA App
Click to expand...
Click to collapse
There are...
By increasing the voltage/speed you reduce the life of the CPU itself. However, these chips aren't designed to last 3 years and then die. They are designed to last 20 years and so OC'ing take the life to something akin to 12 years. Nothing to worry about.
If your software doesn't hang and the phone doesn't freeze/overheat then no worries.
I've had mine overclocked for a few days now with SetCPU to control the speed, and I've noticed that the phone is significantly faster and that the battery lasts longer on idle. Mine is running at 1305 (seemed to be the sweet spot without fiddling with voltage, might play with that another time) and I haven't had any issues at all. Unless you consider a free speed boost to be an issue, anyway.
kinacool said:
Guys I was just wondering if there is any side effects of running g2 at those speeds for extended period of time?
Sent from my T-Mobile G2 using XDA App
Click to expand...
Click to collapse
Yeah I found a side effect.. not being satisfied with stock and not knowing when to stop overclocking lol 1.6 here I come!!
Sent from my T-Mobile G2 using XDA App
Side effects?!
You will become very picky with phones.. trust me, once you get used the the fast overclocked G2, you don't want to use any other slow pines.
I know for certain that you could reduce the lifespan of your CPU, but that's if you're not being smart with it. Along with SetCPU, I was able to increase my battery life by having it idle very low when it's sleeping. I was able to keep my phone at 100% charge, unplugged, for five hours straight before it dipped down to 99%. Then it slowly started picking up.
I'd say that so long as you're smart with overclockiing, you'll be okay.
Sent from my T-Mobile G2 using XDA App
Thread locked, not developmental
So recently here I've been having an issue with my G2. After hitting the unlock button to wake the G2 up, the screen struggles to light up and sometimes it doesn't at all!
When this happens I have to hit the unlock button multiple times just to get the screen to wake itself up, is this happening to anyone else?
Thank god my 3rd G2 is on its way, I should have it tomorrow.
I'm having the same issue also. I think the issue is from setting the CPU down while the screen is off.
Could this be because we've got out G2 oc to 1.42ghz+?
Sent from my T-Mobile G2 using XDA App
My G2 is stock and has this problem.....
Sent from my T-Mobile G2 using XDA App
EdTeach1680 said:
My G2 is stock and has this problem.....
Sent from my T-Mobile G2 using XDA App
Click to expand...
Click to collapse
Well that answers that question lol
Sent from my T-Mobile G2 using XDA App
also have this problem, i usually just open the keyboard.
My stock phone did this...I was under the impression it was some issue with the unlock button. Tmo sent a new one and my replacement hasn't had any issues.
Sent from my T-Mobile G2 using XDA App
This started happening to me when I ran that app that blinked the notification lights when you got a text/voicemail/whatever. (sorry, can't remember what it was called...) When I uninstalled it, it went back to working properly.
[edit - NoLED is the app that was causing it for me.]
Having this same problem, and its extremely frustrating. Sometimes it goes away for a few mins, but most of the time I have to keep pressing the power button till the screen stays on. For some reason, it registers almost every press of the power button as 2. As someone said in one of the above posts, it might have to do with setcpu's screen off profile, but turning that off doesn't solve it for me =(
Sent from my HTC Vision using XDA App
I have this same problem. I was wondering if it was maybe baconbits or setcpu. It never really happened before I got perma root and installed baconbits. Sometimes flipping out the keyboard doesnt even unlock the phone.
I don't know about stock. But this def happened with baconbits for me. I flashed the 2 different sense roms and whenever i applied the baconbits kernel for those roms i had the issues, once i flashed a different kernels I was fine again. So I'll have to pass on bb for now. I hope they can fix this issue because the setcpu settings were great with it.
It happened with my first stock G2. At first I just dealt with it, but then I checked out my wife's G2 (purchased together) and her's worked perfectly. I eventually decided to go though the hassle of getting a replacement from Wirelfy. The replacement's been working fine after perm root & OC.
Install ota and you won't have this problem.
[G2/HTC Vision]
Try removing the setcpu widget from your screen, it seems to have fixed it for me
This was happening to me too. If you have baconbits and setcpu installed, do not use the on demand governor. I changed mine to interactive and my problem went completely away. Conservative works fine as well. On demand was giving me problems though. Even before baconbits on demand was not working properly.
xeduran said:
This was happening to me too. If you have baconbits and setcpu installed, do not use the on demand governor. I changed mine to interactive and my problem went completely away. Conservative works fine as well. On demand was giving me problems though. Even before baconbits on demand was not working properly.
Click to expand...
Click to collapse
Going to give this a try. Do you happen to know what the difference between interactive and on demand are?
Phawkes said:
Going to give this a try. Do you happen to know what the difference between interactive and on demand are?
Click to expand...
Click to collapse
trying this too. The problem seemed to start when I overclocked the cpu. very annoying
Phawkes said:
Going to give this a try. Do you happen to know what the difference between interactive and on demand are?
Click to expand...
Click to collapse
Interactive ramps up to your max speed faster and ramps down from the max slower. So you basically get a little faster performance than ondemand, but at the cost of a little more battery usage. I do not think the battery usage is very significant though.
On my Bell Atrix, I've found that in every build of Gingerbread I've tried (both the AT&T and Orange France versions), my CPU never cycles down from 1 GHz. On Froyo, it would change depending on usage, but with Gingerbread, it's always pegged on max. According to SystemPanel app, approximately 40% of the CPU is constantly utilized by "System" non-stop. This was not the case with Froyo.
I wonder if this ties in with the entry in the battery usage list which shows X as being among the top two users of battery. The CPU total for X is almost the same as the time the phone has been awake.
Has anyone else experienced this? I know there have been a lot of people complaining about the poor battery life on Gingerbread (and I'm one of them), but now I'm wondering if it has to do with "Service" and the mysterious X constantly using the CPU in the background.
Do u have any OC kernels in there or just stock GB?
Sent from my MB860 using XDA Premium App
I've used the stock kernels, the original ones with the RAM fix, and edgen's overclocked kernel and they all behave exactly the same.
frelnik said:
I've used the stock kernels, the original ones with the RAM fix, and edgen's overclocked kernel and they all behave exactly the same.
Click to expand...
Click to collapse
I had the same problem, when you delete all data from fastboot (fastboot-w), install 2.3.4 gingerbread returned and the battery lasts me about the same as the stock 2.1.1 FR. (taking into account that spends more battery 2.3.4). now I have the Orange Radio 2.3.4 with kernel faux123 0.100.00R. sorry for my English
I've run fastboot -w, and used CWM to clear data/cache both before installing ROMs and after installing ROMs, and none of that made a difference. BUT last night I installed kennethpenn's Beta 4, and for the first time, my CPU frequencies were properly scaling, and System was not taking up 40%. Since then, I've wiped data/cache and tried different kernels and different ROMs, and all of them are working. It's almost as though kennethpenn's ROM installed something that wasn't there previously and is persisting through wipes, and ROM/kernel installations. Is that even possible?
freeze your bloat.
use setcpu for system profiles.
problem solved.
For me it was X server running in background and taking 40-50% of cpu. I had to move it because there was no other solution.
Magnetox said:
freeze your bloat.
use setcpu for system profiles.
problem solved.
Click to expand...
Click to collapse
No.
I didn't have to do this with the Froyo builds and I still had excellent battery life (2-3 days). if I go back to 1.8.3 I still have excellent battery life. And that's with Corporate Sync, Gmail push, and Twitter and Facebook in Blur's Social Networking.
There is something in the leaked Gingerbread roms that eats batteries for lunch.
stewartsoda said:
No.
I didn't have to do this with the Froyo builds and I still had excellent battery life (2-3 days). if I go back to 1.8.3 I still have excellent battery life. And that's with Corporate Sync, Gmail push, and Twitter and Facebook in Blur's Social Networking.
There is something in the leaked Gingerbread roms that eats batteries for lunch.
Click to expand...
Click to collapse
You're right. This wasn't in 1.83. But if you freeze your bloat and use setcpu profiles, you will get 2 days of use from your phone.
Sent from my MB860 using Tapatalk
frelnik said:
On my Bell Atrix, I've found that in every build of Gingerbread I've tried (both the AT&T and Orange France versions), my CPU never cycles down from 1 GHz. On Froyo, it would change depending on usage, but with Gingerbread, it's always pegged on max. According to SystemPanel app, approximately 40% of the CPU is constantly utilized by "System" non-stop. This was not the case with Froyo.
I wonder if this ties in with the entry in the battery usage list which shows X as being among the top two users of battery. The CPU total for X is almost the same as the time the phone has been awake.
Has anyone else experienced this? I know there have been a lot of people complaining about the poor battery life on Gingerbread (and I'm one of them), but now I'm wondering if it has to do with "Service" and the mysterious X constantly using the CPU in the background.
Click to expand...
Click to collapse
I'm also on a bell Atrix with 2.3.4 Orange. I've actually never seen this X process that some people talk about? I don't see it anywhere in my battery usage. My top 2 are almost always display and phone idle. I wonder whether you guys are using a setting or app that I'm not. That said, I'm not getting great battery life either. 10 hours and my phone dies.
I'm also using setcpu with a screen off profile. Haven't decided yet whether it helps or not.
Sent from my MB860 using XDA Premium App
maledyris said:
I'm also on a bell Atrix with 2.3.4 Orange. I've actually never seen this X process that some people talk about? I don't see it anywhere in my battery usage. My top 2 are almost always display and phone idle. I wonder whether you guys are using a setting or app that I'm not. That said, I'm not getting great battery life either. 10 hours and my phone dies.
I'm also using setcpu with a screen off profile. Haven't decided yet whether it helps or not.
Sent from my MB860 using XDA Premium App
Click to expand...
Click to collapse
Freeze the bloat on your phone and use edgan's international kernel. I'm getting 24-30 hours on my bell atrix on 2.3.4 orange.
jaysonsantos said:
For me it was X server running in background and taking 40-50% of cpu. I had to move it because there was no other solution.
Click to expand...
Click to collapse
That's pretty much what I was getting as well. X was always second to display in terms of battery usage, and it seemed to be using the CPU constantly whenever the phone was awake. I'm not sure what to make of it, what with some people seeing it and some people not. All I know is that after I tried kennethpenn's ROM, X disappeared, and my CPU seems not to be occupied nonstop. Since then I've wiped my phone and installed the Ninja ROM and faux's stock international kernel, and my phone continues to function without X eating up the CPU. This was the exactly same setup that, prior to kennethpenn's ROM, was suffering from constant high CPU usage. No idea what changed it, but now things *seem* to be operating normally and my battery is much improved.
I solved it renaming "/etc/X11" to "/etc/X11.bkp". So... X process magically disappeared!!!
Anyone notice that if you throttle CPU down, to 1mhz then run your finger back and forth on the screen it will still throttle to 1.3mhz? Or is it just me?
Edit: using setcpu
Sent from my MB860 using XDA App
Sass86 said:
Anyone notice that if you throttle CPU down, to 1mhz then run your finger back and forth on the screen it will still throttle to 1.3mhz? Or is it just me?
Edit: using setcpu
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
Open setcpu. Go to profiles. Then quit and go back in to setcpu and it should stick. Don't know why. I'm going to try a profile to keep it at 1100 like temp over 0. Who knows.
Sent from my MB860 using Tapatalk
Funny. I opened setcpu and it was back at 1300, so my solution is moot. I did just set a profile if battery is below 101% then scale to 1100 low priority (40)
Sent from my MB860 using Tapatalk
I don't know what the deal is. Set cpu tells me the clock is set to 1100. Which matches cm7 settings which also matches system panel. But watching the cpu speed in setcpu it will go to 1300. So yeah. Back to the drawing board.
Sent from my MB860 using Tapatalk
Bear with me. Not spamming. Here's my deal. Most people's governors are greyed out. Mine is not. Tasker, system monitor show it which then allows setcpu to show it. If I'm on powersave the clock will not stick to my setting of 1100. If I set it to performance. It sticks. Any one confirm or deny?
Sent from my MB860 using Tapatalk
I was seeing the same thing until I made a profile for Battery < 101 max at 1000 and a priority of 80%. Now every time I open setcpu he cpu maxes as 1000.
Indeed.. atrix with stock kernel runs all the time at high freqs..
with faux kernel, is at lowest value, so we save battery.
does it have a governor enabled by default or something?
whatever he did, its pretty good!
Imagine that with undervolt..
I recently recieved the LG G2 for christmas, via upgrade through at&t. Upon getting it, I loved it (still do), but recently i have been experiencing a few problems. First off, battery life; I mostly play games and things of that sort on my phone. From waking up in the morning, and instantly playing a game for 2 hours or so, my battery will be around 60%, after even with only moderate use for the rest of the day i have to plug it in to charge in the afternoon and right before bed. Ive even tried factory resetting it.
2. Inconsistent performance; when i first got the phone it boot up in a couple seconds. Another time it might boot up in 20-30 seconds and take a minute to completly load my home screen and all app icons. Antutu benchmark also has inconsistant performance results. One day i might get 35000 and the next get 22000. I have tried deleting and ending processes, using no widgets or more widgets, and everything else i can think of. I dont want to root yet incase i decide to swap out the unit. Maybe ive recieved a faulty phone?
Thanks for reading.
My apologies for not cutting it shorter.
livelysins96 said:
I recently recieved the LG G2 for christmas, via upgrade through at&t. Upon getting it, I loved it (still do), but recently i have been experiencing a few problems. First off, battery life; I mostly play games and things of that sort on my phone. From waking up in the morning, and instantly playing a game for 2 hours or so, my battery will be around 60%, after even with only moderate use for the rest of the day i have to plug it in to charge in the afternoon and right before bed. Ive even tried factory resetting it.
2. Inconsistent performance; when i first got the phone it boot up in a couple seconds. Another time it might boot up in 20-30 seconds and take a minute to completly load my home screen and all app icons. Antutu benchmark also has inconsistant performance results. One day i might get 35000 and the next get 22000. I have tried deleting and ending processes, using no widgets or more widgets, and everything else i can think of. I dont want to root yet incase i decide to swap out the unit. Maybe ive recieved a faulty phone?
Thanks for reading.
My apologies for not cutting it shorter.
Click to expand...
Click to collapse
you need to have the phone settle down...my tips is to use the phone regularly for a week, stop factory resetting and your battery seems right to me...according to that calculation you should get 5 hours of screen on time. not many phone can do that.
Factory settings tend to run the cpu low to max. I've found RoW and interactive a great lag free combo. Switching to conservative while mainly gaming makes a big difference in BL.
G1_enthusiast said:
you need to have the phone settle down...my tips is to use the phone regularly for a week, stop factory resetting and your battery seems right to me...according to that calculation you should get 5 hours of screen on time. not many phone can do that.
Click to expand...
Click to collapse
Phone
HTC Touch pro II -----> Tmobile G1 -----> HTC HD2 -----> Tmobile G2 -----> Samsung galaxy S II -----> Samsung galaxy S3 -----> Sony Xperia "Zed"----->LG G2 (Thank God, dont ever own a Sony)
I'm buzzled between Sony Z1 and LG G2
what u would recommend?
sadiq90 said:
Phone
HTC Touch pro II -----> Tmobile G1 -----> HTC HD2 -----> Tmobile G2 -----> Samsung galaxy S II -----> Samsung galaxy S3 -----> Sony Xperia "Zed"----->LG G2 (Thank God, dont ever own a Sony)
I'm buzzled between Sony Z1 and LG G2
what u would recommend?
Click to expand...
Click to collapse
only if you shower with your phone then z1, otherwise g2 beats every aspect in my flavors
Sent from my LG-D802 using xda app-developers app
bachera said:
only if you shower with your phone then z1, otherwise g2 beats every aspect in my flavors
Sent from my LG-D802 using xda app-developers app
Click to expand...
Click to collapse
:laugh:, thanks bro
maybe by next week i m gonna buy one
yes swap it
Sent from my LG-D802 using xda app-developers app
My g2 never gave me even 30k on benchmarks, it always gives me 26 or 28. Im running stockmod rom and Dorimanx kernel with ondemand plus governor.
Enviado de meu LG-D802 usando Tapatalk
ravefolk said:
My g2 never gave me even 30k on benchmarks, it always gives me 26 or 28. Im running stockmod rom and Dorimanx kernel with ondemand plus governor.
Enviado de meu LG-D802 usando Tapatalk
Click to expand...
Click to collapse
Run the test while the phone is cool.
vPro97 said:
Run the test while the phone is cool.
Click to expand...
Click to collapse
Well it just gave me 30.070 now, for the first time. The phone seemed cool for me when I ran antutu. Can it be related to the Cpu governor I'm using?
Enviado de meu LG-D802 usando Tapatalk
It could be. In my opinion you should care less about benchmarks and more about how it performs in real life. The governor best for daily usage isn't the best for benchmarking . Thermal throttling comes to play when your phone is hot and that easily cuts 5-6k off the score.
But I'm kinda disappointed that you aren't able to get higher scores with that kernel.
Protip : check your PVS bin and undervolt your device
Sent from my LG-D802 using XDA Premium 4 mobile app
Just did a benchmark. I'm stock unrooted and the CPU temperature at the beginning of the test was 46 degrees C (it shot up to 58 degrees at the end of the test). Your results are kinda low.
Sent from my LG-D802 using XDA Premium 4 mobile app