hi my wildpuzzle version is 8.0, but i'm waiting a bit before upgrading to one of the latest.
I'm waiting also because i'd like to know a bit more about overclocking the cpu.
On one hand, i'm sure the phone will be smoother and faster, but on the other hand? Are there any problems, or effect i should be aware of?
One more thing, there is a list with 6 different kernels with oc enabled. How do i choose which one to flash? Which is the best?
thanks in advance
pro:
your phone will be faster
battery usage during idle is potentially decreased
cons:
your phone might become unstable as the hardware will be running outside of tested specs
battery usage during active usage is increased
The different kernels all have different levels of overclocking. If you try one and your phone becomes unstable (random Force Closes or restart) try and flash it with a slower kernel (lower maximum frequency).
There is no danger of directly harming the hardware in the phone from overclocking. However if the phone is pushed so far it is becoming unstable data corruption might occur.
ok that's what i was afraid of.
is this (damaging the hardware) a real possibility? Or is it just in theory?
Than is the phone really faster? I mean, is it worth to overclock the cpu (considering the possible damage of the processor and the various improvement)?
Sorry about that...
I missed a "no" in there. I meant to say that your phone will not explode into a ball of fire or otherwise become unusable from overclocking.
If it is pushed to far it will simply hang or crash and need to be rebooted.
I can notice a rather big difference. I mean going from 528Mhz -> 768Mhz. That's almost a 50% speed increase.
If you require a rock solid telephone and do not want to mess with stability then don't over clock. If you on the other hand like experimenting just go ahead and try it.
just remember to make a nandroid backup that you can go back to in case your phone doesn't work properly after installing the new kernel.
if we overlocking the wildfire , can i play divs with rockplayer or auther?
If I have WPR 8.06 installed and the 0050kernel, is it ok to try installing new kernels to test? And if its unstable, just test a new one? (have a previous nanbackup that I done directly after rooting the phon).
* Do I have to wipe everything, installing the wpr everytime, or just update the kernel without having to do anything else? cheers!
The Wildfire temperature will increase greatly in theory.
If the Wildfire hasn't got it in its design to cool that amount then it will damage the phone, same with computers.
Akerhage said:
* Do I have to wipe everything, installing the wpr everytime, or just update the kernel without having to do anything else? cheers!
Click to expand...
Click to collapse
You can flash kernels back and forth. You don't have to reflash the entire ROM for that. Just make sure you have a working nandroid backup first in case your phone doesn't want to boot.
Skye Menjou said:
The Wildfire temperature will increase greatly in theory.
If the Wildfire hasn't got it in its design to cool that amount then it will damage the phone, same with computers.
Click to expand...
Click to collapse
Yes, in Theory. In practice computer CPUs have temperature monitors that will limit CPU speed to prevent it from rising to high.
In the context of a phone it will be to hot to handle before the temperature becomes high enough to do any critical damage.
Yes, the life time of the electrical circuits will be shortened but a mobile phone will become outdated. Besides the phone is only active for very short periods of time compared to computer.
Skye Menjou said:
The Wildfire temperature will increase greatly in theory.
If the Wildfire hasn't got it in its design to cool that amount then it will damage the phone, same with computers.
Click to expand...
Click to collapse
with a 768mhz speed?.. i dont think it will result to an intense heat that makes the device unusable.. it will make more heat than usual but its tolerable enough..
@OP
Please post in the appropriate sections. This thread belongs in the General Section not Android Development.
Related
After reading, reading and more reading on these forums (thanks to everyone posting) I've finally broken into the true capabilities of these phones. I come to a question every time i'm surfing around tho...
Voodoo or not?
If so, what do the sv, lv, ov remarks mean when choosing a kernel? I havent and dont want to mess things up on my phone...
any insight is always appreciated
I guess you run what the phone can handle. From a logical point of view, if you increase the performance of something it will need more fuel to operate. Some folks seem to be able to get away with low voltage or ultra low voltage kernels at the higher processing speeds without ill affects but it was the opposite for me. When I tried the OTB ul1300, lv1300, or sv1300, it would constantly have issues running most any app, and the lower the voltage the more it would boot loop. With the over voltage 1300 I was able to almost function normally but it still wasn't steady enough for daily use. Any 1200 I tried worked with no problems.
You go with stability and performance that suits you. If I were you I would start at the top but have all of the kernels you want to try at the ready so you can go into recovery and flash another and try again until you settle on what works best. The 1300's are almost guaranteed to give you problems but it's a simple fix if you have them all on standby.
Whether to go with voodoo or not; it works very well and with the new recovery(red lagfix version), it is a piece of cake to disable. Just go to voodoo menu and disable for next boot and enable the partition conversion. As long as you are testing voodoo kernels, you don't have to mess with that setting. Just flash the next one.
I came from a g1,mytouch,and droid 1 to the fascinate. Rooted from day 1. I also questioned the voodoo method. I chose not to because of the hassle of removing it to install certain roms then reinstalling it. It fixes lag in the file system but i truely haven't noticed any without it. And to answer your kernel questions....oc=overclocked sv=standard voltage and lv=low voltage (doesn't always work with all phones)
Sent from my SCH-I500 using XDA App
xlinth said:
I chose not to because of the hassle of removing it to install certain roms then reinstalling it.
Click to expand...
Click to collapse
Yeah, you don't have to do that any more. Voodoo5 plays well with Clockwork (or, actually, comes with its own custom Clockwork), so you only have to remove it to switch to a non-Voodoo kernel. Nandroid backups, restores, etc. can all be done with Voodoo active.
Plus removing it doesn't hang up much (if at all) these days.
What I'm battling is battery life, I'm running DJ05/SuperDark v.9/StupidFast 1.54. I use my phone for almost everything, all the time(even now via wifi tether for internet). I'm expierencing moderate batt life. Although I have ample oppurtunities to be on a charger, I'm worrying about those times I cant. Obviously I want great life w/ great performance. Maybe I'm watching the battery too much and expecting more than I should. I guess I'm still trying to find the best combination for my needs. Can't wait for cyanogen.
props to all the devs
First - If there is thread like this already, I missed it, and please close this one.
Does anyone else experience your HD2 getting very warm when running NAND roms? I dont have it with all builds so that leads me to believe its not magldr. When using GB or CM builds the phone does not get too warm but it usually happens when running an app, like a game for to long. With Sense builds the phone gets even warmer when running apps to long and sometimes when charging the phone. Maybe it is just me, maybe my phone is jacked up, maybe others have this issue??
Any thoughts???
Thanks
Some devs overclock their kernel/builds by default, that's probably why. Underclock it w/ setCPU and it should be fixed.
Edit: charging always heats it up more by the way, that's normal but can be dangerous in combination with high, overclocked activity and other stuff such as tethering.
i have setcpu running and keeping 998max. you think this should be set lower?
Lowering will probably decrease temperature, but less than 1Ghz shouldn't be a problem actually. Are you talking about a lot of heat? CPU's produce heat, and Sense is generally more resource intensive, it's not unusual to feel some heat production, it's oniy bad when it becomes too much.
its not a burn my hand kind of hot. but its not something im used to with this phone. its pretty warm sometimes, i get concerned to the point i will turn off the phone for a bit.
Sense roms tend to produce a lot of heat... I use Cyanogenmod7 and it doesn't get as hot
Sent from my HTC HD2 using Tapatalk
If normal usage doesn't produce any really noticeable heat, your phone is probably doing just fine. Switch to a non-Sense build if you don't feel comfortable (less heat also means less battery waste by the way), the new Gingerbread UI beats the rather cliché and plastic-looking Sense UI any day imo. Combined with the extra features and speed of GB/CM, I know what I'd go for.
If you're just keen on the Sense apps and widgets, they all have their alternative. A little googling will certainly help you out on that part.
The radio was causing the heat issue. Had 2.15 and changed to 2.12. I even getter better signal....go figure.
how do you set cpu lower than 1ghz?
with setcpu or any other clocking tool.
updated my kernell for my mt4g
but everything is gone off my sd
i think thats why its bootlooping
can anyone help me out
not running any custom roms
i can boot into recovery and bootloader
big_d093 said:
updated my kernell for my mt4g
but everything is gone off my sd
i think thats why its bootlooping
can anyone help me out
not running any custom roms
i can boot into recovery and bootloader
Click to expand...
Click to collapse
You are attempting to run a custom kernel with the Stock ROM. The two most likely causes of your loop are 1) you installed the wrong kernel, or, 2) you are using the wrong version of Recovery to install the new kernel. I'm guessing #2, because it's very common for people to assume a higher number is better, and use CWM Recovery 3.0.0.5 with Froyo-based ROMs and hose things up really well.
Restoration options, if you are using CWM 3.0.0.5:
a) Restore from the Nandroid backup you made before overlaying your kernel. Oh, yeah, you can't, you didn't make one, otherwise you'd have already done that and wouldn't have posted....
b) Flash the appropriate CWM Recovery (2.5.1.2 for Froyo-based ROMs) using adb from your PC. Reboot into it, find the kernel you wanted to use, and reinstall it.
c) Install a Gingerbread-based ROM, such as CM7.
Pick a,b, or c. If you have any specific questions, please ask.
Just flashed a nightly mod then icerglacier over it problem fixed no need to be a **** though thanks
Sent from my HTC Glacier using XDA App
big_d093 said:
Just flashed a nightly mod then icerglacier over it problem fixed no need to be a **** though thanks
Sent from my HTC Glacier using XDA App
Click to expand...
Click to collapse
Are you serious? All he did was try and help you figure out what YOU did wrong. I would imagine that you would have rather him put a bunch of smiley faces and thank you for not researching some other threads to get this figured out.
WTF is wrong with people these days? And BTW, as much as you think your problem is fixed...and that one probably is. You are going to run into other things and people such as myself arent going to be as willing to help you when you treat the people that are trying to help like that.
Dont forget that you are the one asking for the help not us.
Oh, I can see where he saw me as "being a ****." My comment about not having a backup available can be seen as snide. (Of course, with the wrong version of CWMR installed, a restore isn't going to do anything more than produce a boot loop anyway.)
My apologies for being a large penis.
jggimi said:
Oh, I can see where he saw me as "being a ****." My comment about not having a backup available can be seen as snide. (Of course, with the wrong version of CWMR installed, a restore isn't going to do anything more than produce a boot loop anyway.)
My apologies for being a large penis.
Click to expand...
Click to collapse
LOL wow wow wow thats to much information there lets keep it G rated LOL.
Now keep in mind this has NOTHING to do with CWM as it has to do with the chip itself what you have to understand is not all chip is created equal as some can utilize normal stock voltage and other can be using lower voltage thus not allocate in first place and it will be stuck on bootloop. Faux address this as most of his kernel has LV/SV but sometimes it may not work as you have to replace it with another kernel like granklin's and then flash it over. This is not CWM issue its kernel issue.
BlackSHELF said:
LOL wow wow wow thats to much information there lets keep it G rated LOL.
Now keep in mind this has NOTHING to do with CWM as it has to do with the chip itself what you have to understand is not all chip is created equal as some can utilize normal stock voltage and other can be using lower voltage thus not allocate in first place and it will be stuck on bootloop. Faux address this as most of his kernel has LV/SV but sometimes it may not work as you have to replace it with another kernel like granklin's and then flash it over. This is not CWM issue its kernel issue.
Click to expand...
Click to collapse
The kernels available all boot at close to stock clocks, so you would have to set it higher before the boot loop problem.
Flashing a rom with the wrong version of cwm would cause the loops instantaneously.
option94 said:
The kernels available all boot at close to stock clocks, so you would have to set it higher before the boot loop problem.
Flashing a rom with the wrong version of cwm would cause the loops instantaneously.
Click to expand...
Click to collapse
Thats normally true but in his case its VOID. If you check his post you will see he didn't flash new rom.
"not running any custom roms"
As I know this is problem with voltage which is kernel related.
"updated my kernell for my mt4g"
Now I am not sure what your talking about in this line.
"so you would have to set it higher before the boot loop problem"
You are confusing clock frequency with voltage the power supplied to the chip to function. Now he can't access that if he knew how and where it was allocated in kernel then we wouldn't have be in this thread. BTW not all kernel use stock voltage or even close. This is not CWM related as it has NOTHING to do with it.
They don't run stock voltages, correct.
Generally, problems only arise when over clocking, not with voltage changes, since the changes in the kernel are fairly minimal. I have yet to hear about anyone having issues with any of our kernels voltages. Only about not being able to clock past a certain point without freezing.
As always, I could be wrong. Just my observations and experience.
option94 said:
They don't run stock voltages, correct.
Generally, problems only arise when over clocking, not with voltage changes, since the changes in the kernel are fairly minimal. I have yet to hear about anyone having issues with any of our kernels voltages. Only about not being able to clock past a certain point without freezing.
As always, I could be wrong. Just my observations and experience.
Click to expand...
Click to collapse
Look let me put it this way once the kernel is flashed and when you reboot it has to be allocated right? now if its under voltage it won't even get passed the bootscreen. This is voltage problem which has to be supplied to the chip for it to function normally which varies chips to chips as they are not all created equal which depends on the defect rate of the wafer. But yes you are correct in your post above as that is aftermath of clock frequency which can only be initiated once the kernel is fully allocated, which also depends on the threshold of the chip itself as they are not all equal. If you get passed the bootscreen then obviously its working but it can still freeze as you stated. Only time voltage come in play again is when you scale from very low frequency to high frequency in short time because normally gradually the power has to be supplied but since it can't due to the power swing it will freeze. Don't confuse clock frequency with voltage. I been OCing for past 15+ years lol long before it was made easy back when you had to manually change the controller's die.
BlackSHELF said:
Look let me put it this way once the kernel is flashed and when you reboot it has to be allocated right? now if its under voltage it won't even get passed the bootscreen. This is voltage problem which has to be supplied to the chip for it to function normally which varies chips to chips as they are not all created equal which depends on the defect rate of the wafer. But yes you are correct in your post above as that is aftermath of clock frequency which can only be initiated once the kernel is fully allocated, which also depends on the threshold of the chip itself as they are not all equal. If you get passed the bootscreen then obviously its working but it can still freeze as you stated. Only time voltage come in play again is when you scale from very low frequency to high frequency in short time because normally gradually the power has to be supplied but since it can't due to the power swing it will freeze. Don't confuse clock frequency with voltage. I been OCing for past 15+ years lol long before it was made easy back when you had to manually change the controller's die.
Click to expand...
Click to collapse
I understand your point quite well actually, all I was saying is that if the voltages were truly causing his issue, It would be the first time that its been reported to my knowledge. Generally, the only issues we have on this phone are clock speed based.
option94 said:
I understand your point quite well actually, all I was saying is that if the voltages were truly causing his issue, It would be the first time that its been reported to my knowledge. Generally, the only issues we have on this phone are clock speed based.
Click to expand...
Click to collapse
Well you are right that if you go beyond curtain threshold then it will freeze but that falls under clock frequency. Which means the kernel was allocated and successfully booted thus user were able to amend changes to the clock frequency which in any extreme case would freeze and need battery pull. But once rebooted it will go back as it won't get stuck in bootloop even with the max OC thus voiding the whole point of the thread as it would not be stuck on the bootloop and isolating CWM and clock frequency as the cause.
However voltage fits the bill and it is not new issue in kernel world as its very common issue matter of fact this has been reported by many users for MT4G and its not new issue. I use to make kernels for device and system as I been using *nix for close to 12+ years and virtually mastered SC.
My hd2 has been getting "really hot" recently. I have hyperdroid cm7 running on NAND. And alot of other things running to make it fast, battery efficient etc etc. My phone has also been "freezing" (haha). Is this just NAND in general? Is it the heat? It never goes over 105-110 degrees. Idk.
Any suggestions are more than welcome.
eyeisdasteve said:
My hd2 has been getting "really hot" recently. I have hyperdroid cm7 running on NAND. And alot of other things running to make it fast, battery efficient etc etc. My phone has also been "freezing" (haha). Is this just NAND in general? Is it the heat? It never goes over 105-110 degrees. Idk.
Any suggestions are more than welcome.
Click to expand...
Click to collapse
The two most popular causes of freezes / reset loops on overheating, are bent battery pins (check and try to delicately strengthen them if so), or defective mainboard (requires replacement). Check this post for more details and references (sorry too lazy to write it all over again)
eyeisdasteve said:
My hd2 has been getting "really hot" recently. I have hyperdroid cm7 running on NAND. And alot of other things running to make it fast, battery efficient etc etc. My phone has also been "freezing" (haha). Is this just NAND in general? Is it the heat? It never goes over 105-110 degrees. Idk.
Any suggestions are more than welcome.
Click to expand...
Click to collapse
What clock freq settings do you have? Perhaps too much or too low OC? I got some FC and freezes when I tried to max OC...
If you undervolted your CPU it may be potential reason.
I had freezes when using CPU undervolting script from here: http://forum.xda-developers.com/showthread.php?t=1148578 .
As for heat, yeah it can get warm sometimes. I wouldn't worry myself over it as long as you can hold it without getting burned.
fpu
I have CPU set at 1190. That could possibly be it. Should I bring it down to stock?
Of course overclocking can cause instability...
Heat will be also produced by using computationally intensive apps like 3D games.
Just check out non-oc.
I brought it back down to 998. It's not getting hot anymore. But it's still freezing. -.-
I've brought mine down as low as 500mhz - still freezes.
THOUSANDS of people with the hd2 heat problem.
i'm gonna say same as i always say...aint ever gonna be solved on hd2.
cant wait to get some cash and get rid of this phone!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!1
matt
matthew33 said:
I've brought mine down as low as 500mhz - still freezes.
THOUSANDS of people with the hd2 heat problem.
i'm gonna say same as i always say...aint ever gonna be solved on hd2.
cant wait to get some cash and get rid of this phone!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!1
matt
Click to expand...
Click to collapse
what helped with my device was mainboard replacement, no problems since, but then I was lucky to still have valid warranty
Hi i have flashed many nand roms to my hd2 the end result is always the same. phone works fine until i try to play games anywhere between 30s to 10 min and the phone freezes up and is unresponsive. only way to fix is to remove battery. any ideas on what this is why it happens and how to fix it.
what is your ROM? what's your magldr version? what is your HTC HD2 type EU or TMOUS? What is the name of your games? i need more information sir..
psypix said:
Hi i have flashed many nand roms to my hd2 the end result is always the same. phone works fine until i try to play games anywhere between 30s to 10 min and the phone freezes up and is unresponsive. only way to fix is to remove battery. any ideas on what this is why it happens and how to fix it.
Click to expand...
Click to collapse
I'd hazard a guess at it being an overheating problem. Do you overclock on the ROMs you use? Does the phone get extremely hot? If yes to these, try not overclocking and see if it works.
magldr version is 1.13 and it a tmous hd2 running nexus h2 ics 4.0.4 cm9 hwa v1.2 by tytung. not overclocking running at the standard max of 998Mhz min somewhere around 200. the only option i have used is in the performance settings under memory management i ticked the kenel samepage merging which seems to have reduced the amout of freezing i am experiencing. tried playing the game called drag racing think is by creative mobile. phone on its own works great but even playing angry birds anywhere between 5 to 15min it freezes. noticed yesterday my battery was low so the charge light was flashing and when the screen frooze the light still continued to blink but the phone was totally unresponsive. Any ideas
Nigeldg said:
I'd hazard a guess at it being an overheating problem. Do you overclock on the ROMs you use? Does the phone get extremely hot? If yes to these, try not overclocking and see if it works.
Click to expand...
Click to collapse
not overclocking running at the standard max of 998Mhz min somewhere around 200
Click to expand...
Click to collapse
I have similar problem. But not so often. He is not overclocking, neither do I.
I also use zRam 26%.
This often happens when the phone is under load, so I think that maybe this is due to lack of memory. The phone heats up when the screen freezes.
Any tips?
OK, this might sound stupid but try putting the phone in the fridge for a while to cool it down, then play. Obviously don't do it for too long, it is after all a phone, but I read somewhere that this had helped someone with overheating. I doubt it is a RAM issue cos that wouldn't cause a freeze, it would probably result in the launcher being killed to free up RAM.
Sent from my NexusHD2 using XDA
not sure putting it in the fridge every time want to play will be quite the fix i am looking for. Might prove the theory that the phone is overheating but then there must be a setting somewhere that can be envoked to get this to stop happening
psypix said:
not sure putting it in the fridge every time want to play will be quite the fix i am looking for. Might prove the theory that the phone is overheating but then there must be a setting somewhere that can be envoked to get this to stop happening
Click to expand...
Click to collapse
Yeah I know it isn't a practical solution, I just meant it to test my overheating theory. Perhaps there is a fix, but to be honest if you aren't OCing then I really don't know why it should be heating up so much. Sure, mine gets warm but even when I've played for around an hour on Contract Killer: Zombies (fairly graphically intense and a very fun game) it doesn't shut down or anything. There IS a hardware fix but it's quite dangerous and requires a lot of expertise and the right equipment, neither of which I have Should you wish to try it, just make sure you're very careful