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.
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.
My brother and I both got Fascinates this month. Both are rooted, but only mine is upgraded to DJ05. We are both loving the phone except, both of us have a problem where the screen/phone will not wake up from sleep sometimes. It will just show a black screen, it even happened while talking on the phone today, the screen didn't wake when I got off the phone. I've done a few searches and on some other phones people suggested setting SetCP to at least one higher then the minimum when it's in screen off mode, but I just tried that and had the same issue 5 minutes later. With all the development going on, I'm hoping that someone may have found a fix for it. Does anyone else have this problem or know of a solution? I apologize if there is another thread in the fascinate forum about this, I did a few searches, but didn't see anything.
Thanks,
Ryan
You could help yourself by stating what rom version and what specific kernel you are using. And if you are using a task killer and or power managment app.
good day.
Sorry if I wasn't clear enough. We are both rooted, but my brother is otherwise running stock. No task manager, just Setcpu. I upgraded to DJ05 and installed JTs Superclean w/non voodoo and rom. But I wouldn't think that'd be the problem considering he's running stock. Maybe it's setcpu? If so is their another comparable manager for battery life that someone might suggest, I can see if that fixes it?
Setcpu offers no benefit to devices using a stock kernel only good for over clocked kernels. If the problem at hand didn't start until installing setcpu, then you have your answer. I myself do not use any power management apps so I can't speak for them.
good day.
Did you by any chance install something that adjusts the brightness of your screen?
If your running Setcpu and your having problems waking up the phone, are you running a profile for the screen off? You can't run profiles on Sammy phones, they don't like it.
No, no brightness apps.
Yes, I was running a profile for screen off and stuff. That was the whole point of Setcpu, I thought, so you could reduce it when the battery started getting low and the phone wasn't being used. Thanks for the info, I uninstalled it. I guess that's the problem. Only time will tell though. Do you know of any other reputable apps that would be similar to Setcpu?
Why not try geeks last kernel? I believe it was uv and should help battery life if that's what you're going for.
I would, but people have had some issues with them from what I hear, besides he's no longer developing them or supporting them, so sooner or later I'd be changing anyway. Maybe I'll check out juice defender.
You can keep setcpu, just don't use any profiles lol and keep it on conservative
Sent from my SCH-I500 using XDA App
Does it actually do anything for you though to help save battery life without the profiles?
Just because he isn't deving for the sf doesnt mean that his kernels are worse than the stock one...I use adryn's 12/17 test 2 and get amazing battery life..14 hrs at like 60-65% but it's voodoo and you will prob not want that.
setcpu will change the ramp up/ramp down speed...more time at max when you need it more time at min when you dont...i don't think it will help nearly as much as proper kernel
Hello everyone...
I have 2 issues with my Transformer
the first one is that whenever i leave my Transformer for couple hours it shuts down !! doesn't occur when charging but it does when it's not.. even when the battery is around 80% !! i had this problem with ALL kernels except the stock kernel which i don't wanna use !! also had this problem for around 2 months...
the second one happened today when i left my Transformer "Charged" at 100%.. and after couple of hours i found it shut down but when i powered it on again i found the battery 27% !!
i went to the battery stats and found that battery was decreasing slowly and there was a gap (which means that it turned off) and after the gap it shows the battery low !! it happened within 6 hours !!
Please help me if you can... !! I'm using Revolver ROM 3.9.5 and "Blades Kernel 3" that comes in the Revolver Parts...
UPDATE : The problem occurs with the stock kernel !!
This sounds very familiar to the problem I had with my Galaxy S2 a month ago.
It kept shutting down every few hours, and it was driving me mad. Then one day I uninstalled the app greenpower, and it was fine afterwards. You don't have the greenpower app by any chance? If not, maybe it can be caused by some other app you normally use?
The battery might be hosed. Have you ever let it hit 0 before? A lot of batteries never fully recover after being fully depleted once or twice.
Cernunnoz said:
This sounds very familiar to the problem I had with my Galaxy S2 a month ago.
It kept shutting down every few hours, and it was driving me mad. Then one day I uninstalled the app greenpower, and it was fine afterwards. You don't have the greenpower app by any chance? If not, maybe it can be caused by some other app you normally use?
Click to expand...
Click to collapse
I never heard of this app... Just like i said it doesn't happen with the stock kernel !!
But the reason I'm using other kernels is because i wanna Overclock !!
a.mcdear said:
The battery might be hosed. Have you ever let it hit 0 before? A lot of batteries never fully recover after being fully depleted once or twice.
Click to expand...
Click to collapse
No i never let it hit 0%... but i don't think that the problem is in the battery
However I'll try it and see what happens !
sounds like a silly question but i have seen it alot. Are you charging through a computer(USB) or wall?
It could be related to setCPU and the according profiles. Just recently I saw that my profiles were messed up after updating ROM and kernel. Might be worth a shot.
Reinstall stock kernel Issue #1 fixed.
Issue 2 sounds like charger shut off and left TF on not charging.
You've pretty much explained to yourself why the thing is shutting down.. It works fine on the stock kernel but not one that is letting you overclock.. Sounds to me like you are either overclocking more than it can handle or undervolting to much or both.
I can almost bet that its not shutting down completely and its just going into a state that the screen is off but the OS is hung up, so its not responding to you turning the screen on.. This would explain why the battery seems to be dieing when its sitting idle.
Not sure about it dieing while its plugged in other than maybe a fluke.
I don't wanna use the stock kernel.. it's really slow !!
and i over clock to 1.4 ghz only since i can't overclock more than that because it restarts itself endlessly if i overclocked more than 1.4 ghz !! i undervolted about -25 or -50.. not much !!
Yes i charge it on a wall or anything but NOT on my computer...
How can i change profiles in setcpu ??
xMini said:
No i never let it hit 0%... but i don't think that the problem is in the battery
However I'll try it and see what happens !
Click to expand...
Click to collapse
No no you misunderstood! DONT let the battery hit 0.
First, you need to use more exclamation points !!!!
sounds like you are suffering from deep sleep issues. What rom are you running? also, have you tried running a custom kernel and not overclock it? You have several variables that can be influencing your issues, start isolating what may be causing your problems. the kernel seems the must likely of culprits, I would clear the overclock and install setcpu and run it for a but and see if you can replicate your issue.
Sent from my GT-I9000 using XDA App
Just try the non stock kernel, oc it but dont uv it, not all devices can handle uv, even if it is only a little bit. Even take it back too 1000mhz and try to increase the uv and oc by little bits at a time to see exactly what your transformer can handle. I think its the uv thats causing the problems. Experiment a bit and youll find the sweet spot.
I'm using Revolver ROM and i mentioned that...
I've never undervolted till yestersay.. maybe it caused the second problem
I set the clock speed at 1ghz and i'm waiting to see if anything changes..
Yeah... the problem still occurs even after setting the clock speed at 1ghz and default voltage !! using clemsyn kernel ver 22...
Every device is different. Differences in manufacturing etc. You might have a picky device. Plus these are mobile platforms. No fans, just convection cooling. They are not meant to be tweaked and oc'ed they way we do. The stock kernel is very fast. What is it that you cannot do on the stock kernel that the extreme oc let's you do?
Sent from my DROID X2 using Tapatalk
colonel187 said:
Every device is different. Differences in manufacturing etc. You might have a picky device. Plus these are mobile platforms. No fans, just convection cooling. They are not meant to be tweaked and oc'ed they way we do. The stock kernel is very fast. What is it that you cannot do on the stock kernel that the extreme oc let's you do?
Sent from my DROID X2 using Tapatalk
Click to expand...
Click to collapse
I'm guessing my device is bad and it's Asus' problem ! i tried setting the clock speed at normal 1Ghz but the problem still occurs !! the reason i overclock is that because with the stock kernel i get slower web browsing and slower flash playback and slower overall performance!! however I'm back on the stock kernel to check out if the problem is gone or not...
I doubted my device couple months ago... because I've seen everyone overclock their devices at 1.6 GHz Without any issues !! but when i try to overclock a little bit more than 1.4 GHz it restarts itself endlessly !!
Had the same issue a few months ago. Be prepared to wake up to a dead TF.
I sent it back to ASUS and they replaced main board and battery. Under warranty of course. I suggest you unroot and use a stock rom for now.
Sent from my GT-I9100 using XDA App
ropaisoft said:
Had the same issue a few months ago. Be prepared to wake up to a dead TF.
I sent it back to ASUS and they replaced main board and battery. Under warranty of course. I suggest you unroot and use a stock rom for now.
Sent from my GT-I9100 using XDA App
Click to expand...
Click to collapse
What do you exactly mean by "for now" ??
and how can i even send it to ASUS ??! i don't live in the USA
xMini said:
I'm guessing my device is bad and it's Asus' problem !!!
Click to expand...
Click to collapse
You stated in an earlier post that the problem does not show up in the stock ASUS setup, but only with a custom ROM and Kernel. How does that make it ASUS' problem. If you buy a car that says it runs on 87 octane fuel and you put 100% nitro methane in the tank and it blows up it is not the manufacturers fault.
Anybody else experiencing this issue?
I looked everywhere but found no real solution.......
Tried flashing new rom no luck ...
This was quite common with the S2, what you can try is to power off your phone and remove the battery for 20-30mins, if the same issue occurs either the battery sensor is messed up or IDK.
Happened with my infuse in the summer out in the sunlight and i posted a topic in there about it. They say its normal
Well I tried this still not working .....
Sent from my GT-N7000 using XDA App
Same problem here. Even i charge my Note also is heating. Dun know why.
Screen bright again
I dont know what cause this problem, but I got the same thing on my phone. A temporarily solution is to install Brightness Level from Android Market. It does not fix the problem in the system settings but it makes your screen 100% bright again
opiujn said:
I dont know what cause this problem, but I got the same thing on my phone. A temporarily solution is to install Brightness Level from Android Market. It does not fix the problem in the system settings but it makes your screen 100% bright again
Click to expand...
Click to collapse
Maximum brightness? trying to get blind?
just joking....
Why so much brightness?
You know that you will get burn-in sooner with so much brightness?
yea sometimes its like a heatpad on my thigh jeans pocket
Well for me it dissapeared suddenly... I'm happy
Sent from my GT-N7000 using XDA App
Jeshter2000 said:
Anybody else experiencing this issue?
I looked everywhere but found no real solution.......
Tried flashing new rom no luck ...
Click to expand...
Click to collapse
I got this issue before , here is my solation
Use titanium backup to wipe the setting/wallpaper
Than u can adjust brightness but can't set wallpapers
Reboot your phone ...and everything good like before
Jeshter2000 said:
Well for me it dissapeared suddenly... I'm happy
Sent from my GT-N7000 using XDA App
Click to expand...
Click to collapse
Problems that go away on their own, come back on their own...
Is there a way to remove this protection?
When I have the gps in the car I get that all the time, even if the phone is not hot at all, very annoying because with the sun and sunglasses -> cant see the screen very well.. stupid!
If you have one of those tpu softcases you will not know whether or not your note is hot just by the feel. Those cases are terrific insulators. I had overheating with the Note on GPS and charging. It actually shut down once and dropped out of the GPS signal a couple of times. Took the Nillikin case off and found that the whole phone was very hot.
After the case was removed I continued the trip with four days of continuous GPS and on charge with no problems. Even with the TPU naked, it still got pretty warm at the top half of the phone, but worked fine with brightness set pretty high. I think this is normal for the Note
[FiX] Galaxy Note ICS OVERHEATING PROBLEM SOLVED
[FiX] Galaxy Note ICS OVERHEATING PROBLEM SOLVED:
1 Go to settings- developer options - UNCHECK "Dont keep activities"
2 Use go launcher ex (or some other good launcher...) instead of default launcher
3 Instal from google play android assistant and use it to clean cache and stop most of background process
4 install from google play "cpu master free" (MUST HAVE ROOTED PHONE) and set 1000 MHz for MAXIMUM, and check box "set on boot"
P.S. DO NOT expect that your phone will be cold as ice after you do this...
ICS is build that you can use max. out of dual core, and galaxy note is pretty slim and back is made out of plastic...All that increase heating problem...
Hope i helped! =D
download the free version of "watchdog" and it will give you an alert if any software uses a lot of cpu power, you might have to go into setting and add system process to the watch list, you can also whitelist and blacklist program so they are killed as soon as they cpu usage goes above a certain level, though this might be pro version only.
Only use watchdog to find the problem and then remove it as it can use quite a bit of cpu power itself.
https://play.google.com/store/apps/...GwsMSwyLDYsImNvbS56b211dC53YXRjaGRvZ2xpdGUiXQ..
John.
Having modded the framework for my rom to include lower brightness mod i can say that the values set in the decompiled framework are virtually the same as gb values infact brightness was increased at the lowest level from 32 in gb to 40 in ics with powersaving mode set to 32 in ics
Sent from my GT-N7000 using xda premium
thering1975 said:
Having modded the framework for my rom to include lower brightness mod i can say that the values set in the decompiled framework are virtually the same as gb values infact brightness was increased at the lowest level from 32 in gb to 40 in ics with powersaving mode set to 32 in ics
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
I see no difference at 38 and below in LQ3. The lowest dim at 39. At 40 the brightness will then increase.
legion1911 said:
Maximum brightness? trying to get blind?
just joking....
Why so much brightness?
You know that you will get burn-in sooner with so much brightness?
Click to expand...
Click to collapse
Hi legion =)
I most often use phone at 100% brightness simply just because I like it when the screen is bright and clear, colors appear nicely too on high brightness. And outdoors in sunlight its sometimes hard to see whats on the screen even though brightness is set to 100%. You were right about the burn-in. Can see some burn-in if looking very carefully, depending on what colors there are on the screen over the burn-int areas. But still they are so weak and hard to notice even when you know where to look for those areas that I will probably have bought a galaxy note 2 or maybe even 3 before they appear clearly visible and too annoying to endure
Sent from my GT-N7000 using xda premium
Chaimfire made an app called "root dim "
Does as it says
Sent from my GT-N7000 using xda premium
I use the goku kernel together with the LRQ stock rom and my phone does not overheet. Sure it gets hot when charging or surfing the web, especially with wifi on. But this has been normal with all smartphones I have owned so far.
Sent from my Galaxy Note running ICS