ive had my wizard for well over a year now, during that time ive used overclocking apps for at least half the time. in that time i have NEVER been able to overclock my wizard past 234mhs. anything higher will instantly lockup my phone.
i bought my phone used off ebay, when i got it, it had a clean official install...though im sure it was just a result of a clear storage whip.. ...any thoughts to why it would overclock past 234?
thanks for your help!
Because
Not all chips are the same, that's why they're under-clocked to make them all equal. It's not like there is a manufacturing process that determines clock speed. So your chip is on the low end.
Every now and then (like 1 every 3-4 times) when I use the camera app, the entire phone locks up and the only thing that I can do is take off the back cover and remove the battery. This has happened to me twice now. I think that both times that this happened, I was trying to record a video.
Has anyone encountered this problem ?
My G2X is running the newest build of Cyanogen 7 (GB 2.3.4).
This is really annoying me. Has anyone found a solution if you are experiencing this ?
This happen to me when I OC to 1.5ghz.
I test again by lowering to 1.2 ghz and problem ended.
if you oc..lower it..or test another kernel.
I do use setCPU but the only thing that I do with it is set the CPU to 216 when the screen is off. I don't do any overclocking otherwise.
I am having the same freezing issue also. When I switch from camera to video it freezes every time and I have to do a battery pull. I'm running Cyanogen 7 Nightly. Did you find out any info on a fix for this? I've googled everything I could and didn't find anything.
I have just installed the Megatron Rom and the Franco Kernel on my LG P500/LG Optimus One. After installing I rebooted the device and after 5 minutes of the start up screen it said something like "Battery overheated. Automatically shutting down device for safety" . I have tried cooling the battery down and then trying again but it still says the overheat message.
Please help me with the problem.
Thanks
What cpu frequencies are you on?
Sent from my LG-P509 using xda premium
re flash kernel .
remember to wipe cache ,dalvik cache and battery stats.
The battery must have overheated because you must have set the clock speed to 806MHz. And I bet you must have enabled the option to set the clock speed on reboot too, otherwise your phone would have worked fine after you cooled it and rebooted it. So turn on your phone, immediately reduce the frequency back to the normal 600MHz, see if it still overheats. If it doesn't, slowly increase the clock speed to a max of 748 or something, that is if you feel that 600 is too laggy for you (for me its fine). Whenever you overclock your processor, never go straight for the maximum clock speed. As it is, 806 is an unstable frequency (its more than 33% higher than the normal clock speed) and will cause the phone to reboot itself, and it will greatly decrease the life of your processor. Always increase the clock speed in small increments and see if it can be handled by your phone. Never use a clock speed directly just because it works fine for something else. Even though these processors come off the same assembly line, they aren't completely identical. Also, never set the option to set clock speeds on reboot, unless you have used the clock speed for several days and is sure it will not cause any problems.
If you haven't overclocked your processor, then maybe you should try flashing the original firmware back and take it to a service center.
Gremaldin said:
The battery must have overheated because you must have set the clock speed to 806MHz. And I bet you must have enabled the option to set the clock speed on reboot too, otherwise your phone would have worked fine after you cooled it and rebooted it. So turn on your phone, immediately reduce the frequency back to the normal 600MHz, see if it still overheats. If it doesn't, slowly increase the clock speed to a max of 748 or something, that is if you feel that 600 is too laggy for you (for me its fine). Whenever you overclock your processor, never go straight for the maximum clock speed. As it is, 806 is an unstable frequency (its more than 33% higher than the normal clock speed) and will cause the phone to reboot itself, and it will greatly decrease the life of your processor. Always increase the clock speed in small increments and see if it can be handled by your phone. Never use a clock speed directly just because it works fine for something else. Even though these processors come off the same assembly line, they aren't completely identical. Also, never set the option to set clock speeds on reboot, unless you have used the clock speed for several days and is sure it will not cause any problems.
If you haven't overclocked your processor, then maybe you should try flashing the original firmware back and take it to a service center.
Click to expand...
Click to collapse
I haven't set any CPU rates because I am only up to the option where you have to enter you country, date, etc.
NanoNoodle said:
I haven't set any CPU rates because I am only up to the option where you have to enter you country, date, etc.
Click to expand...
Click to collapse
Did this problem come immediately after you flashed the new ROM? Then try to flash another one. If its a software problem, then it should solve it. If the battery still overheats while flashing or on other ROMs, then try to flash the stock firmware using KDZ. I remember reading somewhere that we can flash using KDZ without battery, but I'm not sure, so do proper research before doing that..... then take your phone to a service center
this also brings up a question ive been meaning to ask you guys, are gel cases known to heat up the phone, or trap the heat?
Gremaldin said:
Did this problem come immediately after you flashed the new ROM? Then try to flash another one. If its a software problem, then it should solve it. If the battery still overheats while flashing or on other ROMs, then try to flash the stock firmware using KDZ. I remember reading somewhere that we can flash using KDZ without battery, but I'm not sure, so do proper research before doing that..... then take your phone to a service center
Click to expand...
Click to collapse
I have switched back to the old kernel that i'm using and it's working fine.
---------- Post added at 05:51 PM ---------- Previous post was at 05:48 PM ----------
joeyxl said:
this also brings up a question ive been meaning to ask you guys, are gel cases known to heat up the phone, or trap the heat?
Click to expand...
Click to collapse
I'm using a case (I think it's gel) and it's not really trapping heat. It doesn't seem to be the problem with the overheated battery though.
allright, thanks!
Send fromy P-509 using tapatalk
NanoNoodle said:
I have switched back to the old kernel that i'm using and it's working fine.
---------- Post added at 05:51 PM ---------- Previous post was at 05:48 PM ----------
I'm using a case (I think it's gel) and it's not really trapping heat. It doesn't seem to be the problem with the overheated battery though.
Click to expand...
Click to collapse
Hey I'm a new user here. I've experienced the same problem after flashing a kernel uploaded on the website as well. I'm using an LG Optimus One as well, and as suggested, I've wiped cache ,dalvik cache and battery stats but it doesn't help at all, and I do not have another kernel on my sd card. Any suggestions guys?
dancingfins said:
Hey I'm a new user here. I've experienced the same problem after flashing a kernel uploaded on the website as well. I'm using an LG Optimus One as well, and as suggested, I've wiped cache ,dalvik cache and battery stats but it doesn't help at all, and I do not have another kernel on my sd card. Any suggestions guys?
Click to expand...
Click to collapse
Here’s the reason for anyone of you who is facing this over-heating problem with your p500 or any other p50* phone: your Kernel is NOT compatible with your ROM. Colors will likely be displayed properly, but the over-heating problem will be persistent, and will shut-down your phone as soon as it’s booted. There’s a very easy solution to this problem; however, it will involve installing another ROM which is compatible with that Kernel (or back to your original ROM). I’d suggest you do some research on the ROM you are using with that Kernel, and to get a compatible one flashed, or just to get the previous ROM installed on it again. Follow the following steps.
1. Plug-in your phone to its charger. The ‘over-heating’ sign will disappear.
2. Open your internet (if you have installed the ROM and have done a complete data-reset, just connect it to the Wi-Fi.)
3. Install your previous ROM back to get your phone back to normal and not get that ‘over-heating’ sign again. (Hopefully you know it! If not, PM and tell me.)
4. Now, if you want a different ROM installed, you’d be better off installing one that comes WITH a Kernel. Separate ROMs and Kernels are for experienced users; hence, sticking with those which come with both wouldn’t hurt until you are aware of what you’re doing and know how to handle any problems that may occur.
If you have any questions, please ask. I am extremely busy with exams, but still managed to get this post written.
Note: No CPU frequencies or anything had caused the problem.
Good luck!
Well, so lately I would be using my phone and sometimes when I don't pay attention to it and try to turn it on, I find out that it's somehow off. I turn it back on, and it'll be fine for the day or will be randomly shutting again. At first, I had no idea to the reason why this would occur save maybe my under-volting settings, which I still believe is the case but because I tried switching to the default settings to make sure that wasn't the case, I got back to square one.
I have Octane v3.0, bhundven's 3.1 beta kernel, and thomas.raines' compilation of tweaks Lightning Zap v3.4.2.
My undevolting settings are
level0 - 1000 - 1155 - 1065
level1 - 800 - 1040 - 1035
level2 - 400 - 955 - 960
level3 - 200 - 835 - 950
level4 - 100 - 825 - 930
These values being ones I used from dsexton's guide on undervolting, but that was for Froyo I believe, or at the time, the leaked gingerbread stuff.
So I guess my questions would be what are some settings I could use to UV and not have my phone crash.
note: I just checked the forum for the kernel and the problem might be due to the latest kernel so I might go back to v3 if that'll help.
I'll try and upload a logcat if that'll help...
EDIT: Urgh, I just realized after trying to look up for more stuff related to overclocking and undervolting that the problem is most likely due to the fact that our kernel doesn't actually support overclocking yet and I had wrongly assumed that undervolting and overclocking were different enough aspects of the same thing that despite having no overclocking kernel, undervolting would just naturally be fine... Or that's what I think I've learned from all this.
If the mods can or want to, they can delete this thread, because this was an offhandedly simple question I shouldn't have asked....
Funny how you solved it before anyone answered haha. But I'm glad you fixed it!
Sent from my Rockin' Galaxy S 4G!
If you are using octane 3 and lightning zap, that might be your problem as there could be conflicts since raver put the tweaks right unit the ROM... well, that was the case with lightning zap v1... Plus, I noticed
an issue with v3.4.2 and have issued another update... But that was Bluetooth related... Try removing the init.d folder and replace the build.prop with the original, reboot and test...
Sent from my SGH-T959V using XDA App
I'll be trying that out when I have the time. Luckily it doesn't happen to often, usually when I just completely forget about my phone.
From my tank of a Galaxy S 4G. Seen more floor than a rookie lightweight in wrestling.
I had a problem similar to yours except it randomly turned off when it was in deep idle and reception was low had nothing to do with OC/UV. What i did was I went back to krylons froyo then jumped back to gingerbread or you can just use the one click heimdall to wipe everything and donit restore from any back up and see what happens.
Try putting thick business card or two business cards trimmed to battery size in the battery compartment between the battery and the back cover.Make sure its closed tightly this way when you feel the need hit your phone the battery won't go loose in the compartment, this will also work for dropping the phone on the table.
Vicious89 said:
I had a problem similar to yours except it randomly turned off when it was in deep idle and reception was low had nothing to do with OC/UV. What i did was I went back to krylons froyo then jumped back to gingerbread or you can just use the one click heimdall to wipe everything and donit restore from any back up and see what happens.
Try putting thick business card or two business cards trimmed to battery size in the battery compartment between the battery and the back cover.Make sure its closed tightly this way when you feel the need hit your phone the battery won't go loose in the compartment, this will also work for dropping the phone on the table.
Click to expand...
Click to collapse
Luckily so far I'm not having the force closes, but should I get one in the new week, I'll take these ideas to heart. The padding the area between the case and the battery I might use anyways, that's a nice idea to use.
I flashed Slim Bean 2.5 (3.0 kernel) on my waitresses VZW Galaxy and she had some weird, random video issues when plugged into a charger or computer USB port.
So last night I did a total clean wipe, including format data. And installed the new 3.4 kernel based Liquid Smooth. And ended up having the EXACT same issue.
The only resolution is to go into Developer Options and enable "Force GPU rendering".
I've never had issues like this on my AT&T S3 or either of my two buddies TMO S3's. Any ideas why only the VZW phone has had the issue, on two different ROM/Kernels with a total clean wipe before both flashes?
Pic attached shows what the screen looks like when it gets weird.
CZ Eddie said:
I flashed Slim Bean 2.5 (3.0 kernel) on my waitresses VZW Galaxy and she had some weird, random video issues when plugged into a charger or computer USB port.
So last night I did a total clean wipe, including format data. And installed the new 3.4 kernel based Liquid Smooth. And ended up having the EXACT same issue.
The only resolution is to go into Developer Options and enable "Force GPU rendering".
I've never had issues like this on my AT&T S3 or either of my two buddies TMO S3's. Any ideas why only the VZW phone has had the issue, on two different ROM/Kernels with a total clean wipe before both flashes?
Pic attached shows what the screen looks like when it gets weird.
Click to expand...
Click to collapse
What are your min. cpu clock speeds and voltages? Maybe they are set too low and youre working around the problem by offloading some of the video rendering to the GPU?
corbn89 said:
What are your min. cpu clock speeds and voltages? Maybe they are set too low and youre working around the problem by offloading some of the video rendering to the GPU?
Click to expand...
Click to collapse
We're leaving all those settings "as-is".
We used BMS 3.0 kernel on Slim Bean.
And the stock LeanKernel on LiquidSmooth last night.
Only thing changed was moving the max CPU speed to 1836mhz.
Weird!
This happens to my Tmobile Galaxy S4 when force GPU rendering is on! It started by just the lettering or number on top of a video in portrait and then it started making green tears in the screen. I turn off GPU rendering and its fine now.