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.
Related
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.
I have been flashing CM7 nightlies for a while now, but in the last few versions (currently on #12) I am starting to see more random reboots (and occasional boot loops). I am using the stock kernel. I have experienced the problem while using the stock adw and LPP.
I had been flashing over just clearing cache and dalvik, but recently did a full wipe to see if I would still have the problem, and I did.
These reboots appear to happen when I am browsing the internet (stock browser), listening to audio (stock app, pandora, or audible.com app), and playing games/downloading something all at one time.
I am not overclocked at all, I am using all stock settings in CM7.
Any instructions on what can be done to fix/avoid this would be great.
I would lean towards it being a CPU issue, It may be that the new CM7 Kernel is slightly undervolted and when you are using the CPU for an extended amount of time that it reboots on you. I suggest trying out some other kernels to see if it continues to happen the new incredikerenel is supposed to address some of the stability issues people have been having lately.
Thanks, I will give the new incredikernel a shot and post back.
Edit: So far so good. After installing the 3.6 incredikernel I have not had any random reboots, even under pretty heavy load. Thanks again for the tip.
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.
Im a little new at this so im not exactly sure how this works. But i am running CM7 and i just flashed the latest incredikernel and everything is working fine.
but now I decided to try setting the voltages (the setvdd_levels zip). I flashed this but now i am not sure what i have to do next. Is there something else i need to do?
Thanks
If you flashed it already then it should be applied. You can use Chad's undervolting scripts or use vipermod, which is terminal emulator-based and super easy to use.
both chad and vipermod had flashable voltage tables. you just put the .zip file on your sd card, and flash it just like you would flash anything else in recovery (or if rom manager is how you do things, fine..). the way i did it was trial and error. i tried the vipermod one's. start with the the 25mv, then the 50mv, then the 75, then the 100, then the extreme (125mv), then the insane (150mv). just start small, run for a day or so, then keep going up. you'l know it when you get too high. i personally run the 100, and it works quite well for me. just flash one right on top of the previous. if you want it back to normal, he has a "reset" flash mod in there too. just play around with it, but remember to give yourself ample time to see the benefits. he also has made it to where you can adjust each table yourself, but i haven't gone that far into it yet. what i'm using is working great, so i'm happy...
Thanks guys. I downloaded vipermod and ran it to lower the voltages by 25, but now every so often my phone reboots and gets stuck on the cyanogenmod 7 loading screen and i have to pull the battery. Is that unusual?
Thanks guys. I downloaded vipermod and ran it to lower the voltages by 25, but now every so often my phone reboots and gets stuck on the cyanogenmod 7 loading screen and i have to pull the battery. Is that unusual?
Click to expand...
Click to collapse
Booting takes more power then normal running. Mine does it on OMFGB W/beta 8 and -50
Youre looking at a crackflashing troll with ORD
Seems like each phone has its own threshold for undervolting. I'd recommend trying out different levels (-25, -50, -75, etc) but NOT saving the setting. Then you can see how it runs and when/if it does reboot, you'll be back to stock voltages.
Well I wasn't having any luck with -25 - it was giving me reboots and getting stuck on the cyanogenmod loading animation. But after i pulled the battery it would boot up fine, but eventually would reboot (maybe after 20 minutes). So i tried going into vipermod and setting the voltages back to default, but it still gave me reboots. Now i deleted the 95havsvdd file like chad said to do if it was unstable
Hi guys,
Hoping you all can help me. I installed Vipermod and undervolted 50mV. Running MIUI 1.7.22 with Tiamat 3.3.7 SBC. Also have SetCPU runnings with various profiles. Whenever I turn my phone on it'll work for a little bit and then freeze or restart itself. Should I just nand backup to without the vipermod, or is there a way for me to edit a script with the settings to remove the undervolt setting. I'm afraid of running a nand backup and the phone freezing in the middle. Thanks, appreciate any help.
As long as you have a full charge, a nand restore is usually a pretty fool proof way to fix any problems.
That vipermod is something most kernel devs don't mess with because of exactly what you are saying. There is some benefit if you can get it to work flawlessly, but it's hard to get it to do that.
I recommend a complete wipe, then restore your last nand. Again, just make sure you have plenty of battery whenever you restore a nand backup. The only thing that can really completely brick your phone is if it dies in the middle of doing something like that.
Here's Viperboys BSM_PSM_reset script, flash this in recovery if you get stuck in a bootloop.
Also, if you have the updated setCPU, goto the main screen and press menu, you'll see an option to download their "safe mode" zip file which you also flash in recovery
The BSM_PSM_RESET zip restores your kernel to its default settings, the setCPU zip you download restores setCPU to default settings as well
Viperboys BSM_PSM_RESET zip:
http://db.tt/5sHGbaY
Sent from my PC36100 using Tapatalk
I believe this is heat related!!! I am getting intermittent, but daily reboots and every time the phone feels hot. Usually I get the reboots whenever the phone is working hard, playing a game or using google maps. I always wipe EVERYTHING when flashing roms and the last two day I decided to do some fresh installs of AOSP and quality Sense roms(all GB) and I didn't load any new apps after install. Guess what!?!?! Still getting reboots and the phone is hot when it reboots. I then pull the battery cover and put it on a cool spot or in front of the AC and it boots and runs great as long as it is being cooled. I've been a huge HTC and Android supporter since day one, but at 13 months old I shouldn't have to deal with this especially when I baby the phone. I hate to say it but I may have to switch to the evil empire. Their phones just work and keep working, oh and their battery last all day, maybe two days on one a single charge.
If you read this post because you are having the issue please make note if the phone is hot when it reboots. Allot of people believe this is software related, I on the other hand believe it is heat and hardware related. Unfortunately I refuse to lose root and go return mine... UGH!!!
No offense, really, but I do NOT understand SetCPU. People use it to overclock, for what reason?? Are you planning on Playing COD BO on your phone?? Or do rocket science?