Hi,
first of all, I am not using a HAVS kernel anymore since I only had bad experience with it. But I would like to ask you, if I am the only one who had bad experiences. So here is the problem:
No matter which rom I tried, every time I use a kernel with this super cool HAVS-feature, my batterylife increased a lot, but the phone was nearly unusable after a few hours of idling. Direct after the boot process, the phone worked like normal, but if it was a few hours in stand-by, I had to wait a few seconds (at least 30+) until the phone did ANYthing. Mostly it was a FC from the launcher app, and it didnt matter which one (zeam, launcherpro, adw, and so on, all the same). I somehow didnt care, because once I made a testcall to test if this sluggish behaviour applies to phone-calls, too, and it didnt. Sometimes the launcher wasnt even usable after 3 FC's and I had to reboot the phone. Did I do something wrong? I also tried various SetCPU settings (ondemand, interactive, smartass, profiles) but these settings didnt have any impact on this behaviour.
So, am I the only one with this problem? Because I never read, that anyone else has this problem. If yes, what did I do wrong?
Yes this behavior is normal. Not every desire likes a havs kernel. With havs you use less voltage for the same speed. And because every phone is slightly different you could have one which does not like it. So your phone gets to little power to do it's job, that's why you have crashes etc.
So it's not a problem with havs but a problem with your phone.
Also there are different havs kernel, 875mv or for example 925mv. Maybe you could try a 925mv, that one uses a little more juice. Otherwise stick with SVS.
Ah, thank you for the information. Isnt there a 950mV kernel by chance? I tried from 875 to 925 all I could find, but they behaved all the same . Seems like my Desire doesnt like HAVS kernels at all.
Related
Hi
I have permroot and s/off my phone using gfree method and i flashed a kernal
that i downloaded (Cyanogen Kernel v1.3) the kernal allows overclocking upto over 1400 mhz ,at 1094 mhz everything is fine and my phone is stable but as soon as i set the frequency over that using setCPU my phone freezes ,i dont know what i am doing wrong this is the first time i tried overclocking a phone ,i hope i am wrong but i am thinking since every cpu is unique maybe thats the max mine can handle ??? i apprentice any tips, advise , help ,suggestions
Thanks.
i have also tried EZDZ_Godspeed_update03 but using this kernal my phone doesnt even boot up it crashes immediately when i turn my phone on.
bahmanxda said:
Hi
I have permroot and s/off my phone using gfree method and i flashed a kernal
that i downloaded (Cyanogen Kernel v1.3) the kernal allows overclocking upto over 1400 mhz ,at 1094 mhz everything is fine and my phone is stable but as soon as i set the frequency over that using setCPU my phone freezes ,i dont know what i am doing wrong this is the first time i tried overclocking a phone ,i hope i am wrong but i am thinking since every cpu is unique maybe thats the max mine can handle ??? i apprentice any tips, advise , help ,suggestions
Thanks.
i have also tried EZDZ_Godspeed_update03 but using this kernal my phone doesnt even boot up it crashes immediately when i turn my phone on.
Click to expand...
Click to collapse
You might be right. Not every CPU is created equal and since the phone is only supposed to run 800Mhz you can't exactly complain that it "only" does ~1.1ghz
On the other hand a little more juice can make a reluctant CPU run a little faster. I'm not sure how the voltage tables work out for different Kernels but you might want to look in to that. The higher the voltage, the better the chance your OC will work, typically.
That's true, every cpu is unique. But for now, since the kernels are still going through development, I would assume it's perfectly fine that overclocked speeds are still quite unstable
Thanks for the replys i am not really complaining i just wanna make sure that i havnt messed up somewhere i thought the crashing might be happening because i messed something up or maybe it happend to others and its a common problem or there is a fix for it .
Also i would appreciate it if someone could put me in the right direction in regard to changing the voltage.
Sent from my HTC Vision using XDA App
just wipe my original stock sense rom and flashed it with virtuous-vision_froyo_rom-v0.8.0 and applied all the patches but still the same problem
my phone freezes instantly as soon as i change it to just over 1100 mhz
its so strange its very very stable at 1094 mhz hasnt crashed even once.
any ideas?
The current overclock kernel that Flippy has over in Development (1.4) causes my phone to freeze when I'm trying to play Angry Birds. CyanogenMod's kernel runs it at 1.4Ghz, and I'm using an older, more stable version of Flippy's kernel.
bahmanxda said:
just wipe my original stock sense rom and flashed it with virtuous-vision_froyo_rom-v0.8.0 and applied all the patches but still the same problem
my phone freezes instantly as soon as i change it to just over 1100 mhz
its so strange its very very stable at 1094 mhz hasnt crashed even once.
any ideas?
Click to expand...
Click to collapse
It could be simply that your CPU isn't capable of over-clocking that high. Its hard to say as the kernels are still being developed but the ability to overclock a processor can vary greatly from unit to unit...
I have CM 6.1 and the last few days I have been running my phone at 1017 to compare the performance difference against the 1497 and thus far, I haven't really seen a drastic difference... That may change as the Gingerbread based ROMS start to trickle out but for now 1ghz seems like plenty of power.
You could always try a different kernel and see if it yields different results.
bahmanxda said:
Hi
I have permroot and s/off my phone using gfree method and i flashed a kernal
that i downloaded (Cyanogen Kernel v1.3) the kernal allows overclocking upto over 1400 mhz ,at 1094 mhz everything is fine and my phone is stable but as soon as i set the frequency over that using setCPU my phone freezes ,i dont know what i am doing wrong this is the first time i tried overclocking a phone ,i hope i am wrong but i am thinking since every cpu is unique maybe thats the max mine can handle ??? i apprentice any tips, advise , help ,suggestions
Thanks.
i have also tried EZDZ_Godspeed_update03 but using this kernal my phone doesnt even boot up it crashes immediately when i turn my phone on.
Click to expand...
Click to collapse
you should check/edit the overclock scripts..
I found wrong configuration script (650 Mhz using Androidiani OR)
Does anybody else have this problem? It happens to me about once a day..I'll go to check my phone and its totally off and I have to pull the battery to get it to power up again. It only happens when the screen is off.
I've had this happen a few times, and other have as well. There is a thread about it, with various theories on the cause, but a definitive cause(s) has not been found.
http://forum.xda-developers.com/showthread.php?t=857584&highlight=pulling+battery
One user claimed the GPS was the culprit. But this was not my personal experience. I was never using GPS when it happened to me. Mine might (possibly) have been linked to having screen-off profiles under CPU Tuner. I uninstalled CPU Tuner, and went back to SetCPU, and have not had the issue re-occur in over a month. Do you use either of these CPU over/underclocking apps, any overclocking?
Thanks for the reply I actually just found the thread you linked to right after I started the thread.. My desire Z is rooted but other then that totally stock.
EDIT: It also did this before I rooted.
My Z also did this a couple times the first few days I had it, and it was pretty much stock. Then it didn't do it for a while, during which time I flashed the overclocked Godspeed kernal, and installed SetCPU. Then the power-on issue cropped up again (almost immediately) when I tried using CPU Tuner. The issue stopped after uninstalled CPU Tuner, and hasn't come back in over a month.
My only hypothesis is that its related to some combination of the kernal and CPU Tuner, in my case. But it also may have been a complete coincidence, and have nothing to do with either of those.
ive had this happen to my g2, no setcpu profiles had been set. mine was charging both times i noticed this. had to pull battery and unplug it before i could get it back on
I have an HTC EVO 4G Hardware Ver: 0003. It's running off standard Koni's Elite III. I like the look, and it offers full features. I live in area with 4G so no CM for me. But anyway, I noticed even with perflock disabled, it will not overclock beyond 998MHz. I tried to install Netarchy-Toastmod 4.3.1 kernel to it for overclocking. I tried cfs and bfs, tried no HAVS, with HAVS. Then I tried the beta, using literally each and every possible one. Every single time, it boots perfect, runs for a minute or two, then it locks up, and reboots. This happens immediately if I try to overclock it beyond 998MHz, however even at normal 998MHz, it never stays on longer than 5 minutes before rebooting. I made a Nandroid backup beforehand, had to restore it. So its back to normal, stable, but again, I want to overclock it. Is Elite III not capable???
Crazykid3333 said:
I have an HTC EVO 4G Hardware Ver: 0003. It's running off standard Koni's Elite III. I like the look, and it offers full features. I live in area with 4G so no CM for me. But anyway, I noticed even with perflock disabled, it will not overclock beyond 998MHz. I tried to install Netarchy-Toastmod 4.3.1 kernel to it for overclocking. I tried cfs and bfs, tried no HAVS, with HAVS. Then I tried the beta, using literally each and every possible one. Every single time, it boots perfect, runs for a minute or two, then it locks up, and reboots. This happens immediately if I try to overclock it beyond 998MHz, however even at normal 998MHz, it never stays on longer than 5 minutes before rebooting. I made a Nandroid backup beforehand, had to restore it. So its back to normal, stable, but again, I want to overclock it. Is Elite III not capable???
Click to expand...
Click to collapse
It's not going to be the ROM (well it most likely isn't but you can check and see). If you can run stable on the stock HTC kernel, but not with a custom kernel, then you might just have very sensitive hardware that can't handle changes made.
I have two Evos in the house, one can clock all the way to the max, the other caps out one step past 998. No kernel will fix this. The one that doesn't overclock well also doesn't handle low voltages very well (reboots). The other one works just fine.
If you want to try something else, look out for Ziggy471 on google. He has some EVO kernels you could try also. He isn't GPL compliant (he doesnt release source code) so you won't find him on XDA (dunno if he ever was).
I know I really didn't offer much help, but it could just be the luck of the draw that your phone is really really sensitive. Try another ROM first and see. I know you have tried various kernels, but try a few more. Try AOSP ROMs with newer kernel versions (.37 or .38). Good luck
Also, CM7 supports 4G just fine.
i just flashed invisibleks .37 kernal with OMFGB (ran into some problems with CM7) and i was wondering the proper way to set up setcpu profiles with smartass (if needed at all)
Sorry. This should be in Q&A.....
Sent from my OMFGB powered hTc Incredible.
watt9493 said:
i just flashed invisibleks .37 kernal with OMFGB (ran into some problems with CM7) and i was wondering the proper way to set up setcpu profiles with smartass (if needed at all)
Click to expand...
Click to collapse
I ran OMFGB 1.1.1 for a long time before they screwed up 1.2(soooooo many errors), and really felt the need to have a lockscreen music controler(1.1.1 doesn't). I always ran 128/768, on 1.1.1 it should run perfect(I run chad's kernel though), just unlock slowly. If you want a faster unlock set it 245/768. Either one of those will get you really good battery life(128 being better obviously). If you are running 1.2, I highly recommend you set it atleast at 921(i think) or above as that just doesn't run as smooth. Also note the way smartass works, unless you want to kill battery life everytime you turn the screen on, try to set the max the lowest possible as it will sit as a frequency the phone feels it should run at without losing any speed(most of the time it's 1036 if you've overclocked). So unless you are just texting or calling, it's not bad, but any multitasking or big app using when the screen on, it'll jump way up.
I believe Chad is working on an ingenious kernel that tries to scale intelligently to what it is doing at all times so it'll save battery life not only when the screen is off, but also while the screen is on.
Can i set profiles or no? Like screen off, battery ones, and one temp one?
Sent from my OMFGB powered hTc Incredible.
watt9493 said:
Can i set profiles or no? Like screen off, battery ones, and one temp one?
Sent from my OMFGB powered hTc Incredible.
Click to expand...
Click to collapse
Oh, well, there is no point for a screen off one if you are using smartass on all your profiles. When it's not doing anything, it automatically scales down to the lowest setting possible(128 for best battery but slow unlock speeds or double clicks sometimes, 245 fixes those problems but using a fraction more battery).
I have a Normal profile(128/768), a Temp profile(245/614), just make sure if you are using GPS you manually scale it up some, my phone always ran like crap when Navigating anything less then 883, but everything, and I mean everything usually was fine at 768 on 1.1.1. If you are running 1.2 probably want to do 883 then 998 for GPS.
Just rooted my phone a week ago and installed setcpu and a new kernel (made for 4.0.2 - and I quadruple checked that 1) I am definitely on 4.0.2 and 2) the kernel is definitely made for 4.0.2 (it's Faux's 4.0.2 kernel).
With that out of the way, here's my issue: with SetCPU installed, my phone is a slow, laggy mess. When I uninstall the application, my phone is fast, zippy, and all is well. It doesn't make sense given the context. More details below.
Specific things that lag especially bad are the following: 1) very slow screen wake/unlock (without any screen-off profile set/enabled and with the phone at stock min/max CPU frequency and ondemand and interactive governors, and also when underclocked and overclocked and in any combination you can think of); 2) homescreen performance; 3) typing; 4) switching between apps; 5) answering phone calls
I have tried using Setcpu with and without screen off profiles set and enabled, I have tried using the phone at stock clock, overclocked to 1.35ghz, and underclocked to 920mhz, and in all situations and combinations, the phone is slow, jerky, and a bit laggy. I also played with different scaling governors (interactive and ondemand mostly), and had the issue regardless of the governor used. I have not messed with voltage or anything else.
This issue has persisted over three days now, it happens regardless of how many times I've rebooted the phone and uninstalled/reinstalled the SetCPU application, etc. In short, there seems to be nothing I'm doing wrong on my end (or so I think) to explain this issue. And every single time I uninstall SetCPU, my phone is a speed demon again.
I have never had this issue on any previously rooted phone using Setcpu. Also, yes, I wiped cache AND dalvik cache before flashing Faux's kernel. I am not new to Android, cell phones, rooting, flashing kernels, etc. I can even use ADB without problems.
So, hopefully I covered all my bases. Anyone have any thoughts on why I might have been experiencing this issue?