Develop Bugs

Issues With HAVS

For some reason, my phone will not run a kernel with HAVS on it. Some kernels boot loop at the evo 4g screen. Others load up, only to experience random reboots every few seconds. I've tried wiping everything several times, flashing rom and kernel at the same time, flashing rom then kernel after reboot, etc. Also, this happens with or without SetCPU. I've searched the forums, and have also asked on one of the kernel forums, only to get the answer "some phones just don't get along with HAVS." Any other ideas?? Anything I can try?? Thanks in advance.
Nate

I have the same problem. I pretty much haven't been able to get a kernel to work correctly after CM6 RC2. I've tried many different versions of the snap kernel. Pretty much none of them work. I have gotten away with a few custom kernels working, but normally I will get at least 1 random reboot per day with them. And they're from August. I don't know what it is, stock kernels run fine; however, I haven't been able to get CM6 to even boot for me after RC1.
I don't seem to be having any kernel panic. k_lastmsg isn't even there after these Cm6 boot loops.
I really hate sense, so I have been running Emerald mod 1.1.1. It's the closest thing to CM6 right now. It works because it's using a kernel that can't OC, and only has 2 touch points.
I have a few k_lastmsg files, that explain the random reboot. These are from snap kernels. I can't get any useful information out of them.

It's possible the minimum possible undervolt with the HAVS kernel is set too low for your particular phone; some phones can be really picky with how far they can go.

Do you live in the south? Are your normal room temperatures above 85F?
Are your evos getting too hot?

No. Temperatures here have been around 60. I don't think it's over heating. I was able to boot a HAVS975 kernel. The kernels that have higher voltages seem to boot, but are not stable. However, anything under 900mv cause boot loops. This was on the latest CM6 nightly. It booted, but 3 minutes after I got a random reboot.
I just flashed 8 kernels over CM6.0 final. The only one that actually works for more than 5 minutes is SnapV2. I can get 5 of them to boot. The rest loop. 7/8 result in a random reboot after about a minute or so. I can post some logcat logs. If anyone can help me decypher the actual problem, it would be great.

[Q] Quadrant Standard causing multiple reboots

So recently I installed Baked Snack 1.8 on my phone and wanted to try out quadrant standard on it. It starts the benchmark and gets maybe halfway through and then the phone just crashes and reboots several times.

althis said:
So recently I installed Baked Snack 1.8 on my phone and wanted to try out quadrant standard on it. It starts the benchmark and gets maybe halfway through and then the phone just crashes and reboots several times.
Click to expand...
Click to collapse
Are you over clocking the phone?

To 1.15, it's never been a problem before using QS. If I went up to 1.267 then my phone would crash but it was always stable up to 1.15

althis said:
To 1.15, it's never been a problem before using QS. If I went up to 1.267 then my phone would crash but it was always stable up to 1.15
Click to expand...
Click to collapse
I hear ya, but typically I get that crash when my phone is too far over clocked.

Are you using the stock kernel that comes with 1.8? I've noticed Kernel 6 provided by Hero works best. Maybe it will stop your reboot problems.
Or you can try netarchys kernel.
These newer built in kernels don't really work too well with setCPU because of the included governors

[Q] HAVS kernel killing every launcher?

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.

proper way to use smartass?

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.

[Q] Random Reboots driving me crazy

I've had this E4gt for a few days now. First thing I did was root it with the FI27 Odin one click method, then install Agats source 6.5 kernel. Had some random reboots that I shrugged off as my phone not liking any undervolting. But it still does it, even under _dan's lightweight v0.2 rom
It isn't completely random though. Most of the reboots are when I'm trying to wake up the phone after letting it sit idle. Other times it'll reboot while it's sleeping idle. it has NEVER rebooted during use (I ran pandora/poweramp for 8 hours no problem)
It also occurs under most governor settings.
It almost seems that for whatever reason, idling at 200mv is causing the phone to crash and reboot.
the only overclock utility I use is System Tuner Pro, however I don't know if this could be the cause.
Only other option I can see is unroot/flash stock FI27 and see what happens, but I really don't want to go through the hassle, especially having to get another effing phone (since assurion can't be bothered to ever send a proper working phone)
bit of info on my phone I guess
Rooted it from bone stock factory FI27 using Odin FI27 One click rooting (success on first try)
Agats source 6.5 kernel
_dan's Lightweight v0.2 rom
Ktoonservative kernel (however it seems every kernel does this)
Scheduler set to noop
no oc/uv settings currently
I use System Tuner Pro to adjust clocks/governor settings, etc however, I haven't done many tweaks besides my OOM settings.
Stock rooted with Agat's source 6.5 was causing reboots as well, under the same conditions (deep sleep reboots, and waking from deep sleep)

m4xwellmurd3r said:
I've had this E4gt for a few days now. First thing I did was root it with the FI27 Odin one click method, then install Agats source 6.5 kernel. Had some random reboots that I shrugged off as my phone not liking any undervolting. But it still does it, even under _dan's lightweight v0.2 rom
It isn't completely random though. Most of the reboots are when I'm trying to wake up the phone after letting it sit idle. Other times it'll reboot while it's sleeping idle. it has NEVER rebooted during use (I ran pandora/poweramp for 8 hours no problem)
It also occurs under most governor settings.
It almost seems that for whatever reason, idling at 200mv is causing the phone to crash and reboot.
the only overclock utility I use is System Tuner Pro, however I don't know if this could be the cause.
Only other option I can see is unroot/flash stock FI27 and see what happens, but I really don't want to go through the hassle, especially having to get another effing phone (since assurion can't be bothered to ever send a proper working phone)
bit of info on my phone I guess
Rooted it from bone stock factory FI27 using Odin FI27 One click rooting (success on first try)
Agats source 6.5 kernel
_dan's Lightweight v0.2 rom
Ktoonservative kernel (however it seems every kernel does this)
Scheduler set to noop
no oc/uv settings currently
I use System Tuner Pro to adjust clocks/governor settings, etc however, I haven't done many tweaks besides my OOM settings.
Stock rooted with Agat's source 6.5 was causing reboots as well, under the same conditions (deep sleep reboots, and waking from deep sleep)
Click to expand...
Click to collapse
Is the phone new or did you acquire it used? I had random reboot issues...tried numerous software fixes (new ROM, new kernel, uninstalling apps). Finally found the problem...a faulty power button. The solution for me was to replace the phone under warranty.

Its an assurion refer. According to the phones lifetime stats however it wasnt used for more than a week or so in august.
Also its not the power button. I watched it lock up and reboot earlier today
I'm almost thinking I should call asurion and tell them they sent me another effed uup phone and demand a nib phone. But that means unrooting this one and I'm not sure how big of a pain that will be
Sent from my SPH-D710 using xda premium

Ktoon... gov gave me some odd results too, try pegasusq and don't under volt until you have established a stable setup.
Honestly though try a different rom, FI27 seemed buggy to me but FI03 was alright. If you want to try Jellybean then give Codename a try. Its been rock solid.

someguyatx said:
Ktoon... gov gave me some odd results too, try pegasusq and don't under volt until you have established a stable setup.
Honestly though try a different rom, FI27 seemed buggy to me but FI03 was alright. If you want to try Jellybean then give Codename a try. Its been rock solid.
Click to expand...
Click to collapse
Interesting that you would mention ktoonservitive!
My setup has been always dead stable. But....
I've had a few random reboots when on calls lately and have been running that (ktoon..) for a little while now.
I'll have to switch that out and see what happens.

Well im currebtly running the latest version of recaulk so ill report back with my results if i gwt any reboots.
Sent from my SPH-D710 using xda premium

m4xwellmurd3r said:
Well im currebtly running the latest version of recaulk so ill report back with my results if i gwt any reboots.
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
After running Re-Caulk all night, I've come to the conclusion that FI27 was the culprit.
Ktoon probably wasn't helping, as I was running it quite often.
I'm using whatever kernel comes with re-caulk, min at 100mhz, max at 1400mhz, -25mv. Battery life is better than before (though, with my 3800mah battery, its already insane)
buttery smooth goodness too

Bit of an update since I made this thread.
Running smartbench 2011 I was getting abysmall productivity scores, and it seemed overall my scores were AWFUL no matter what in any benchmark (overclocking to 1.5 would barely get the almost to baseline numbers)
I called asurion and told them I was having reboot issues with the phone etc, they sent me another refurb today.
Scores are exactly as they should be now. Productivity scores in smartbench 2011 went from 2500-2800 to 4000+
I think the CPU on my first e4gt had a problem with the processor, which is why deep sleeping was crashing it.
I do realize benchmark scores mean nothing in terms of real world performance, but when there's a known baseline number for a particular phone, and your phone is struggling to even get close to that baseline (even with a maximum overclock) there is clearly something wrong with it.