Related
So I've just started trying kernels. I decide to start with the popular Kingklix kernels. So I backup up my Cyanogen 6.0.2 and flashed his BFS #2
The kernel was very very snappy, but the benchmarks were really low (in the 600's) they seemed to lag at the "testing I/O" portion. But I didn't care because the phone felt as fast as the Captivate.
I charged it full, and went out for the night. The phone was dormant in my pocket for most of the time, maybe 10 texts sent... the phone died in 3 hours. This made me done with the kernel, as much as I liked it I need my battery.
So, I reverted back to stock and installed his CFS #1 kernel, I cleared Dalvik (I did this before and after the kernel flash like I did with the BFS version) and booted.I cleared the battery stats since the phone was off now and I might as well bump charge. This previous charge stayed forever! I got 1d 4h and 40m on this setup before getting 14% and the phone saying to plugin
The CFS isn't as snappy as the BFS version and I'd love the speed of the BFS one but I need more then three hours of battery... so I have a few questions.
1. Can you flash kernels ontop of eachother? or do you have to restore to stock in between flashes (much like themes on AOSP roms)
2. Are the low benchmark scores normal for Kk's BFS #2 kernel?
3. Is clearing battery stats part of the procedure? and is that what made the difference between the two kernels? or is BFS just poor on battery life?
Clearing battery stats really isnt needed, kernels can be flashed on top of each other, and king BFS 2 was really buggy, use 1 Cfs, it may not be as high in quadrant, but quadtant doesnt mean anything. Cfs is more stable, and the code for the cfs is 2.6.32.21 whereas bfs is all buggy and is 2.6.32.51.
Sent from my ADR6300 using XDA App
I knew quadrant didn't mean anything when I saw BFS and it's low scores but amazing performance. I hope he patches it up, the alternate scheduler really makes a noticable difference.
Just wondering if anybody has tried this kernel yet? Found it over on AndroidMobileJunkie.com (Followed a link in somebody's sig here n XDA that said 1.28Ghz so naturally I was curious lol) Anyways, here's the link for the post over on AMJ. http://forum.androidmobilejunkie.com/threads/kernel-ziggy471-droid-incredible-22-oct.11/
yea ziggy's kernel. It's been in discussion in both of the Desire rom port threads. 1.28 is very rough on the processor though, and mostly unstable for a lot of people's phones (mine included), even ziggy admits it's a risky business, but he has proven it is possible.
I am so tempted to try this, but I'm afraid to fry my phone. My go big or go home mentality may make me give in. Wish there was someone who posted on the thread link
I ran it. No problems a 1.28 but really didn't use it long. Here's my Quadrant post in the Desire Z port thread:
http://forum.xda-developers.com/showpost.php?p=8775977&postcount=168
X
I'd imagine that clocking the processor that high wouldn't make much difference than say, 1.19GHz.
In fact, in plenty of ROMs I've tried, anything clocking over 1152mhz actually gives me a decrease in my quadrant scores. Not to say its not a stability issue - I'd assume that most Snapdragons actually clock higher than 998mhz, but then are reduced because that's baseline performance, anything less than 998mhz would get kicked.
I've never had a ROM crash, even running at 1.19GHz, but didn't notice any performance gains, plus, unless you just happen to get a chip that is capable of 1.28GHz no problem, it's probably near bottle-neck anyway.
And Quadrant has several variables way outside of clock speed that can pull 1800's, including just your flavor ROM.
Bottom Line: It's not worth frying your phone just for a barely-existent performance gain. If you happen to have a processor that is incapable of stability at 1.28GHz, you might fry out some transistors, then get stuck with something that freezes if you clock it over 700, let alone the 998 stock.
For me personally 1.28 is no improvement over 1.152. In fact, it gives me worse benchmarks.
sorry for repost
I gave this kernel a try and I actually prefer the newest HTC 2.6.32.17 charging time has significantly decreased battery life has increased and the performance is really responsive and smooth. My quadrant scores are nothing impressive pretty average but I would rather all of the above than a high quadrant.
I tried this kernal and my camera stopped working...
HeyItsLou said:
I gave this kernel a try and I actually prefer the newest HTC 2.6.32.17 charging time has significantly decreased battery life has increased and the performance is really responsive and smooth. My quadrant scores are nothing impressive pretty average but I would rather all of the above than a high quadrant.
Click to expand...
Click to collapse
Lou hit the nail on the head. I love the .17 kernel. Im using the new guy with great performance, battery life, charging, and neat transitions. its like a new phone.
I'm using this with a vanilla froyo ROM and my battery life is amazing. Haven't noticed any freezing or any program not working.
Wow!
Thanks for all the replies guys, I think for now I'm gonna stick with the stock kernel also, I just remember back when I used to run KxK's kernels seeing great benchmarks and battery life I was always wondering if there were any faster out there lol
dimebagdan65 said:
Thanks for all the replies guys, I think for now I'm gonna stick with the stock kernel also, I just remember back when I used to run KxK's kernels seeing great benchmarks and battery life I was always wondering if there were any faster out there lol
Click to expand...
Click to collapse
There's always faster, the question is will they work. lol
When I'm running the newer Sense ports, HD or Z, I can only run 1.113, no matter how much or little voltage I give it. When I'm running an older one, I can go all the way up.
As for stability at 1.28G, I need to work on the voltage more, to find the sweet spot, I just did it 'cause Jugs said one of his Bravo buds had it working, so I had to try.
I'll keep playing with it if people are still interested, otherwise, I'll just keep at the lower speeds.
Z
Just loaded up your AOSP on Ruby 1.1.4. Running great, 1600 in Quad at 1ghz. Everything seems really smooth. Are the voltages undervolted at 1ghz? Maybe you could start your own thread?
Nevermind...found it!
ziggy471 said:
There's always faster, the question is will they work. lol
When I'm running the newer Sense ports, HD or Z, I can only run 1.113, no matter how much or little voltage I give it. When I'm running an older one, I can go all the way up.
As for stability at 1.28G, I need to work on the voltage more, to find the sweet spot, I just did it 'cause Jugs said one of his Bravo buds had it working, so I had to try.
I'll keep playing with it if people are still interested, otherwise, I'll just keep at the lower speeds.
Z
Click to expand...
Click to collapse
By the way, my post wasn't meant to disrespect your efforts to 1.28GHz, I'm just giving fair warning that someone could possibly burn out their phone if they jack it up all the way. When I'm ready for an upgrade, I'll probably put this thing to the max.
Thanks Ziggy
hajabooja said:
Just loaded up your AOSP on Ruby 1.1.4. Running great, 1600 in Quad at 1ghz. Everything seems really smooth. Are the voltages undervolted at 1ghz? Maybe you could start your own thread?
Click to expand...
Click to collapse
What AOSP kernel??? I only see one kernel, and it references skyraider, which leads me to believe it is a sense kernel
edit: I am dumb. It is a different thread on the same site as listed above
http://forum.androidmobilejunkie.com/threads/kernel-ziggy471-droid-incredible-aosp-23-oct.24/
rmaccamr said:
By the way, my post wasn't meant to disrespect your efforts to 1.28GHz, I'm just giving fair warning that someone could possibly burn out their phone if they jack it up all the way. When I'm ready for an upgrade, I'll probably put this thing to the max.
Thanks Ziggy
Click to expand...
Click to collapse
I didn't take it as such, and I agree with you fully. I prefer somewhere between 1.113 and 1.15. That's the reason I included the init script to set the max at 1.113, which I find very stable and fast, hell I'd say 1865 quad with ID's Z port isn't too shabby at 1.13.
I should be able to get 1.28 more stable with playing with the voltages, it's just that takes time, and I wasted too much this morning doing both AOSP INC and Evo kernels, so I'm worn out for awhile on kernels. I still need to fix the Evo for puertoblack, since it appears I left the debug port out, so no adb for it. lol
Z
Yesterday I put the netarchy havs less kernel on my phone and with some stress testing and general testing found that it worked well at 1.15 mhz. I carried it around all day messing with it no problem. Today, the real test came when I ran GPS on my phone in my car. The phone lasted about 3 minutes of GPS before it started rebooting. Then my 4g was broke from it somehow. Anyhow, I restored my phone and all seems well now.
I still want to mod the voltage and clock speed. Any advice on this? The phone always gets hot when I use GPS because it uses a lot of processor, frequently its on the charger and possibly in sunlight. When it was not overclocked or undervolted my phone NEVER reboots not once since I've had it.
Is the problem the undervolting, overclocking or both? Should i give up on this due to the way I use my phone?
Thanks in advance.
Try different kernels. I use netarchy sbc 4.2.2 more havs, works great. I also use his 4.3.4 more havs sbc. They both work for me. Battery life is awesome and gps works good. No prob here. Try those out and see what happens. Hope this helps.
Sent from my HTC EVO Phone, should'nt we all have one?
Okay so is there any danger to this? It seems like every time my phone starts rebooting from overclocking or undervolting apps start disappearing from my phone and stuff stops working.
I use amon RA 2.3 and every time I recover it works again but I was just wondering how dangerous it is for me to experiment they way I have been. I have already recovered my phone 3 times from issues like this that broke it.
Every phone reacts differently to kernels, undervolting, and overclocking so you will have to experiment to find out what works for you and what doesn't. Just make sure that you dont check the "set on boot" box until you know your setup is stable. A reboot shouldn't hurt anything though.
I am running Netarchy 4.3.4 more havs, overclocked to 1190 and it's as stable as can be on my phone. However, if I go over 1190 it immediately locks up and reboots.
Sent from my HTC EVO 4G with Tapatalk
kd0axs said:
Every phone reacts differently to kernels, undervolting, and overclocking so you will have to experiment to find out what works for you and what doesn't. Just make sure that you dont check the "set on boot" box until you know your setup is stable. A reboot shouldn't hurt anything though.
I am running Netarchy 4.3.2 more havs, overclocked to 1190 and it's as stable as can be on my phone.
Sent from my HTC EVO 4G with Tapatalk
Click to expand...
Click to collapse
Yeah but the reboots are hurting my phone! I have to restore it due to the problems the reboots and freezing causes (sometimes I have to battery pull due to full lockup). 2 times when I pulled battery due to full lockup apps went missing from phone memory but the available space on the phone was as if the apps were still there. Another time my 4g wouldn't turn on.
Is that abnormal? Can it mess up my phone in a way that recovering wont be able to fix or is recovering generally a sure shot?
The reboots should not be hurting the hardware, unless you overclock excessively. What the reboots are doing is corrupting your file system because open files do not get closed properly.
Are you after speed or battery life? I think the two are mutually exclusive. If you have great speed (be it governor or because of overclock), you will pay the price in battery life. I think the trick is to find the balance between the two that suits *you*.
gpz1100 said:
The reboots should not be hurting the hardware, unless you overclock excessively. What the reboots are doing is corrupting your file system because open files do not get closed properly.
Are you after speed or battery life? I think the two are mutually exclusive. If you have great speed (be it governor or because of overclock), you will pay the price in battery life. I think the trick is to find the balance between the two that suits *you*.
Click to expand...
Click to collapse
Because I use the 1-1-1 power management system (see sig) my main concern is performance. I love my phone and when I use it I want it to be fast and smooth. I would *prefer* if the extra speed didn't dramatically change my battery life but I'm okay with a small decrease in battery life if the speed gain is reasonable for the tradeoff. Anyhow I thought a lot of people ran HAVS along with overclocking to have both to a degree.
Only time I charge my battery is when I am using it in the car with my car charger. At home I charge all my batteries on an external charger - my phone is a mobile device I prefer to never be bound to a cord. I sleep with my phone next to me off the charger lol.
Okay so my phone is running more HAVS now and it seems the same as before so I guess my friend is HAVS friendly. I will run this for a day to check if any reboots happen and aim for tomorrow to overclock again. It may have been the 1.19 mhz that caused the issue. I will drop it down to 1.15 or 1.1 and see if its stable.
Okay, so my question is basically how stable is overclocking your g2? I typically keep it at 800 when I use my phone normally, than 1.5ghz for games. I wante d to keep my g2 at 1.5ghz forever.. is that bad?
My battery obviously increases in temp..
I just use 1GH. It's enough for all game now. and didn't see any bad to battery or phone
I've had my DZ for about three weeks now and all this time I've had it consistently overclocked to 1843MHz. At that high of a speed, I had to let the phone cool down after 20 minutes of use.
Just today I flashed pershoot's 1516MHz kernel and noticed no heat issues after ~45 minutes of consistent use (temps < 40C).
I have had my g2 for.... However long they been out. I have always been overclock to at least 1.5 with zero heat issues. I ran 1.8 and even 1.9 for a good long time as well. Those speeds have heat issues ones that required a battery pull a few times because it started heating up faster then i could shut down the phone. If your going to OC at those speeds makes sure you set temp profiles with alarms.
Sent from my HTC Vision using XDA App
ARM processors, like our snapdragons, are a lot more forgiving on the overclocking front than what you might find in your desktop, for instance.
I still treat overclocking on my phone like I do my computers, though... setcpu has a stress test built in that you can use if you're curious how "stable" your overclock is. but in my experience, I've found that you can get away with just playing around with it and using the phone normally and seeing how it reacts to different clockspeeds.
right now, I run it at 1.1ghz (24/7). I have run it at 1.5ghz (24/7) in the past for PSX/N64 emulators, but I've found with my new setup (pretty light; no widgets, very few things going on in the background, stripped as many unnecessary apps as possible, and not using any animations or fancy bits) that 1.1ghz is more than enough to be able to play the games I play on any emulator smoothly.
you should be fine at any speed that is currently available in the overclocking kernels we have with the exception of flippy's 1.9ghz kernel, which does require some monitoring to keep things cool and stable. but it still does vary from phone to phone. if you're running at 1.5ghz and the phone isn't doing anything wonky, then you shouldn't worry about it. if you're running it at 1.5ghz and you're experiencing stability issues, random force closes that aren't fixable through conventional methods, or heat issues, you should probably back off a bit.
some people have problems at 1.2ghz, some people are running at 1.9ghz all the time and never have problems... just find what works best for normal usage with your device and go with it.. it's not like we keep these things for more than a couple of years anyway, and the processor will be capable of handling the [stable] overclock for that period of time.
im always at 1.2ghz. 768 as min, interactive gov (when i use CM7) and battery has been fine, havent noticed any major issues. hard to tell if it was the rom bugs or OC being the issue but from what i read all my issues others have at various speeds so im guessing it was rom related
i think it depends on the rom.
when i use the Pyromod rom i dont need overclock but for other roms like sense roms those I require OC. I always keep it at 1400 when needed.
Im stone stock right now. Do you see an actual improvement in apps that need the extra O/C HP? I have one game I bought that seems to be a little choppy at times, 9mm HD, and Im not sure if its the games coding, the fact that it maybe having a problem with ICS, or just not enough hardware HP to be fluid.
I OC'ed when I first got the phone but quickly dropped it back to 1200. This phone doesn't need overclocking and if you are noticing lag in games it is most likely due to poor coding by the dev for either ICS or dual core phones or both. If it is lagging on a 1.2 GHz dual core and it is our hardware think about people running it on the Inc 2 with a 1 GHz single core processor and basically last years tech. Our phones should be fine to run most if not all games for about a half year or maybe a year before OCing will really be needed.
Why don't you just do it and find out? It's really hard to tell because no kernel is a stock kernel with 1.35 GHz / 1.4 GHz.
All these kernels featuring OC have additional features which means that it could be the features/tweaks that are fixing it rather than the OC itself.
zephiK said:
Why don't you just do it and find out? It's really hard to tell because no kernel is a stock kernel with 1.35 GHz / 1.4 GHz.
All these kernels featuring OC have additional features which means that it could be the features/tweaks that are fixing it rather than the OC itself.
Click to expand...
Click to collapse
Well,...Im just pretty content with how it performs in every other aspect, except for this one game bugs me a little. Ive been ROMed and O/Ced on this not too long ago, and TBH, theres always some sort of little thig that turns me off about it. A spontaneous reboot here, a F/C there, and I find myself going stock again. I would do it in a heart beat if it didnt mean having to set every last detail back up again when I unlock the phone.
And yes, being virtually OCD about this phone sucks, lol.
I have a question as well!
For those under-clocking or using UV kernels, do you see a noticeable improvement in battery life? I have a GSM sock GNex and the battery life is atrocious.
stevessvt said:
Well,...Im just pretty content with how it performs in every other aspect, except for this one game bugs me a little. Ive been ROMed and O/Ced on this not too long ago, and TBH, theres always some sort of little thig that turns me off about it. A spontaneous reboot here, a F/C there, and I find myself going stock again. I would do it in a heart beat if it didnt mean having to set every last detail back up again when I unlock the phone.
Click to expand...
Click to collapse
Should of unlocked the bootloader day one before playing with the phone your phone still remains stock. Just the bootloader is unlocked, you'll virtually feel no difference. Except the fact that you have to relock for warranty purposes later but you'll wipe everything so that is always good because you don't want to exchange a phone with all of your passwords.
@andythefan: Yes there is a huge battery difference. Visit the Franco Kernel thread in GSM forums for people's images of battery history.
Flash the James Bond kernel so your gpu will be upped to 384mhz. It is in the development section.
My grandma beat me down and took my nexus. Sent from a jitterbug with beats by dre.
@rbiter said:
Flash the James Bond kernel so your gpu will be upped to 384mhz. It is in the development section.
My grandma beat me down and took my nexus. Sent from a jitterbug with beats by dre.
Click to expand...
Click to collapse
Other kernels also have this feature. A lot of them do.
@stevessvt: In the myriad different combo's I've flashed (ARHD, Franco kernel, APex Kernel, bigxie ROM, AOKP rom, stock kernel, OC/No OC, Unvervolting, and 1 other kernel I can't even remember) I've yet to encounter a single random reboot, FC, or battery pull. I've also flashed countless different mods and basebands, etc.
It's all about doing your homework and really reading through threads before flashing and making sure different stuff is compatible and doing nandroids.
I can honestly say running a non-stock rom/kernel makes a noticeable difference in response and performance in daily use. Its really all the Kernel IMO, ROM's just give you features. I've however never noticed anything from OCing.
@andyfan: what build are you on? 4.0.2 has the hands down best battery life, and 4.0.3 with the Franco Kernel is nearly as good as 4.0.2 was (4.0.2 for me meant ~3% drain in 8 hours)
andythefan said:
I have a question as well!
For those under-clocking or using UV kernels, do you see a noticeable improvement in battery life? I have a GSM sock GNex and the battery life is atrocious.
Click to expand...
Click to collapse
For now any phone usage will give you terrible battery life due to the high power consumption of the screen especially if when it displays white onscreen content. Average CPU usage is very low unless you're running benchmarks consistently. Therefore UV tweaks have low impact on usage battery life.
With that said if your battery is irregularly draining while idle something may be active in the background.
Franco has made many tweaks to his kernel to reduce idle power consumption. He's gotten it down to about less than 1% drain per hour which can give you over 2 days of idle battery life. Just for ****s and giggles I have achieved that with less than 30 minutes of screen time with LTE enabled.
Franco's kernel is the best I've used in terms of overall battery life but none of the OC/UV kernels have significantly increased my usage battery life.
Sent from my Galaxy Nexus using XDA App