Related
I got an EVO myself and managed to overclock it to 1.267GHz. We could probably go even higher, but that requires more extensive changes. Here are the changed source files: http://dl.dropbox.com/u/36553/supersonic_oc-uv.tar.gz
It also includes an undervolt courtesy of pershoot (a whole 0.1V lower when idle, which should help battery drain a lot!). Here is a test update.zip: http://dl.dropbox.com/u/36553/supersonic_oc-uv_signed.zip (working WiFi). Make sure to do a nandroid backup first!
Sensors/camera do not currently work in this kernel because the source is not yet complete.
There is an overvolt on the highest frequencies. It should not cause any issues. Thanks to toastcfh for his source, Herver for creating the first booting overclocked kernel on the EVO, all the kernel devs in the N1 community, especially pershoot and kmobs, richardtrip from the Desire community, koush for anykernel updater, and all who helped to root the EVO. Enjoy!
Update 6/15: Fixed 950mV undervolt. Raised voltages from 1228800 above to improve stability. Source files updated and update.zip uploaded.
old said:
I posted these in an earlier thread, but I think I should bring this to everyone's attention. Here are some simple patches that will overclock the Evo up to 1.267GHz (though by any means it's not guaranteed to get that high!):
Edit: please don't flash the below update.zip, as it doesn't seem to boot. Devs, the patches are still below, and a zimage is in the anykernel update zip.
Update: I compiled it myself. Here is an update.zip: http://dl.dropbox.com/u/36553/update-oc_signed.zip. This uses toastcfh's sources, Koush's excellent anykernel updater and a config.gz pulled from a stock Supersonic. If this doesn't boot, no damage will be done to your phone. Just reboot into recovery and reinstall your ROM. You can test overclocking by grabbing SetCPU from my sig or changing the cpufreq values if you know how. Once we get this working, I will create an undervolted version for battery savings. I'd get an Evo, but it's sold out everywhere T_T
http://dl.dropbox.com/u/36553/supersonic_oc.zip
cpufreq.c and acpuclock-scorpion.c are in arch/arm/mach-msm, and supersonic_defconfig is just the config. I don't have an Evo, so I can't test these out, but these should work with the source files toastcfh posted earlier: http://forum.xda-developers.com/showthread.php?t=686240.
Undervolting can be achieved simply by adjusting the voltages (in mV) in the acpu_freq_tbl table in acpuclock-scorpoion.c. For those not familiar with his work, you can see pershoot's safe (but lower) voltages for the N1 here: http://github.com/pershoot/nexus-kernel/blob/master/acpuclock-scorpion.c. If you want to overvolt or go under 1000mV, you have to make one further adjustment to the voltage regulator in board-supersonic.c.
Note that the N1 and the Evo are completely different devices (with similar processors), so what may work for the N1 may not work for the Evo.
Click to expand...
Click to collapse
Awesome... until I am sure this is stable, I will wait, but I must have overclock
jigglywiggly said:
Awesome... until I am sure this is stable, I will wait, but I must have overclock
Click to expand...
Click to collapse
I don't recommend overclocking, the devices already can run warm at current settings.
But then again, you are entitled to do as you wish.
Options better than overclocking are to remove the Sprint bloatware and strip down parts of Sense, this speeds things up alot by removing excess background applications.
Well it ain't too bad, my Droid at 1 ghz(550 stock) runs great.
So this should be good too.
I like overclocking as much as the next geek, but on the Evo... WHY?
This phone has yet to respond anything slower than instantly to my input and I expect a difference of .26 ghz would not make it so it could read my thoughts.
Undervolting, on the other hand, could help with the abysmal battery life...
phinnaeus said:
I like overclocking as much as the next geek, but on the Evo... WHY?
This phone has yet to respond anything slower than instantly to my input and I expect a difference of .26 ghz would not make it so it could read my thoughts.
Undervolting, on the other hand, could help with the abysmal battery life...
Click to expand...
Click to collapse
Some people love to run benchmarks. Try to improve on them over and over. Others like the feeling of just going faster. Also some apps or some in the future might require a faster running phone. What better way to achieve that (other then buying a new phone) then OC.
Also in the future, are you not gunna buy a 1.5ghz processor phone running 2.1 because a 1ghz processor can already do it? OC has many benefits, just not to everyone, most because they dont understand the consequences or benefits.
My htc hero clocked to 768mhz can run 2.1 and everything near instant. Still doesnt keep be from wanting a 1ghz or higher.
Also one more thing, 2.2 will be out soon. With full flash support, i have a feeling its going to require a lot of CPU. An OC Evo would probably run many things from 2.2 a lot easier.
Well, I agree with the benchmarking comments but on the subject of Froyo... Froyo is designed to be even faster on equivalent hardware than 2.1... and 2.1 on my Evo is smooth as silk. And the Evo handles most Flash I can throw at it, so I'm not sure. I have however noticed a small performance difference with live wallpaper running, so maybe OCing will clear that up a bit.
Jus10o said:
Some people love to run benchmarks. Try to improve on them over and over. Others like the feeling of just going faster. Also some apps or some in the future might require a faster running phone. What better way to achieve that (other then buying a new phone) then OC.
Also in the future, are you not gunna buy a 1.5ghz processor phone running 2.1 because a 1ghz processor can already do it? OC has many benefits, just not to everyone, most because they dont understand the consequences or benefits.
My htc hero clocked to 768mhz can run 2.1 and everything near instant. Still doesnt keep be from wanting a 1ghz or higher.
Also one more thing, 2.2 will be out soon. With full flash support, i have a feeling its going to require a lot of CPU. An OC Evo would probably run many things from 2.2 a lot easier.
Click to expand...
Click to collapse
You know, this is an excellent point and I feel like I failed the developer community in some small way when you had to bring it up. You shouldn't have to provide a reason for wanting progress, it should happen for its own sake.
Proceed.
Jus10o said:
Some people love to run benchmarks. Try to improve on them over and over. Others like the feeling of just going faster. Also some apps or some in the future might require a faster running phone. What better way to achieve that (other then buying a new phone) then OC.
Also in the future, are you not gunna buy a 1.5ghz processor phone running 2.1 because a 1ghz processor can already do it? OC has many benefits, just not to everyone, most because they dont understand the consequences or benefits.
My htc hero clocked to 768mhz can run 2.1 and everything near instant. Still doesnt keep be from wanting a 1ghz or higher.
Also one more thing, 2.2 will be out soon. With full flash support, i have a feeling its going to require a lot of CPU. An OC Evo would probably run many things from 2.2 a lot easier.
Click to expand...
Click to collapse
Agree with everything you just said, and I am less than excited about the benchmarks with the EVO thus far
Roman G said:
Agree with everything you just said, and I am less than excited about the benchmarks with the EVO thus far
Click to expand...
Click to collapse
HAHAHA.. im sorry but i had to laugh at your sig.
Jus10o said:
HAHAHA.. im sorry but i had to laugh at your sig.
Click to expand...
Click to collapse
Ya I sold my hero a couple weeks before the EVO dropped, and had to use my wife's old phone.
phinnaeus said:
I like overclocking as much as the next geek, but on the Evo... WHY?
This phone has yet to respond anything slower than instantly to my input and I expect a difference of .26 ghz would not make it so it could read my thoughts.
Undervolting, on the other hand, could help with the abysmal battery life...
Click to expand...
Click to collapse
I'm not trying to start an argument at all but you have to think broader mathematically. If the processor runs at 1000Mhz or 999mhz (In the case of my N1) a .267 increase is 267mhz, a 26.7% increase in computational performance... That's pretty raw especially in cellphone terms, that have no way to vent or displace that kind of heat.
Has anyone noticed how much hotter the kickstand gets? I bet you that it's attached to something the cpu is connected to. $5 bucks says we will see KICKSTAND HEATSINK + FAN MOD 2GHZ OC! LOL
thebluecoat said:
I'm not trying to start an argument at all but you have to think broader mathematically. If the processor runs at 1000Mhz or 999mhz (In the case of my N1) a .267 increase is 267mhz, a 26.7% increase in computational performance... That's pretty raw especially in cellphone terms, that have no way to vent or displace that kind of heat.
Has anyone noticed how much hotter the kickstand gets? I bet you that it's attached to something the cpu is connected to. $5 bucks says we will see KICKSTAND HEATSINK + FAN MOD 2GHZ OC! LOL
Click to expand...
Click to collapse
This is a patch for developers, not a discussion thread for the merits (or lack thereof) of overclocking.
If you don't want to overclock your phone, nobody is making you.
It has worked out fine in the Desire and Nexus One community.
coolbho3000 said:
This is a patch for developers, not a discussion thread for the merits (or lack thereof) of overclocking.
If you don't want to overclock your phone, nobody is making you.
It has worked out fine in the Desire and Nexus One community.
Click to expand...
Click to collapse
how do i apply this ???????
can u make it flashable?
mccurt29 said:
how do i apply this ???????
can u make it flashable?
Click to expand...
Click to collapse
need to follow the directions in the first post. the .c files need to be loaded into the kernel source (right now just have toast's soruce) and the kernel has to be compiled with them.
if somebody wants to compile up a kernel with these, we could start testing. if i get some free time i'll help out here and compile a kernel but somebody else will prob beat me to it!
please someone let us know how this works out for your evo 4g... benchmark, test results... anything to show better/worse performance, whether your got ALOT warmer, or just a lil, etc.. ne information would be greatly appreciated it, i'm not a 100% noob, i just know how to follow instructions very well, doesn't mean i understand everything that's going on, just the basic concept of what i want. thank you in advance.
madunix said:
please someone let us know how this works out for your evo 4g... benchmark, test results... anything to show better/worse performance, whether your got ALOT warmer, or just a lil, etc.. ne information would be greatly appreciated it, i'm not a 100% noob, i just know how to follow instructions very well, doesn't mean i understand everything that's going on, just the basic concept of what i want. thank you in advance.
Click to expand...
Click to collapse
I'm waiting for someone to compile this first.
If nobody steps forward, I'll make my own attempt, but I'll be working blind with no test hardware.
I'm pretty sure most devs are waiting on the htc source kernal before playing with this. I can't wait but I understand them being hesitant to do too much with this for now. Still awesome of you to post it and have it rdy for when that time comes!
sounds good.
madunix said:
sounds good.
Click to expand...
Click to collapse
Your signature says you have a radio of 1.32.651.6, just to let you know that is not a radio, that is an HTC software OTA update. My radio is 1.39.00.05.31 for example
I was browsing the Optimas 2x forum today and ran into an awesome kernel with GPU overclock. which sounds pretty cool to me. also the dev mentioned something about overclocking "system bus" which improvers memory/2D/3D/etc. i think someone in this forum should take a look into this KERNEL and try letting us taste some of this goodness.
Here are the links:
http://forum.xda-developers.com/showthread.php?t=1119771
http://forum.xda-developers.com/showpost.php?p=14654927&postcount=36
while im no genius when it comes to this stuff, somehow i would suspect that people here are already looking into this.
i could be wrong tho lol
pyckvi said:
I was browsing the Optimas 2x forum today and ran into an awesome kernel with GPU overclock. which sounds pretty cool to me. also the dev mentioned something about overclocking "system bus" which improvers memory/2D/3D/etc. i think someone in this forum should take a look into this KERNEL and try letting us taste some of this goodness.
Here are the links:
http://forum.xda-developers.com/showthread.php?t=1119771
http://forum.xda-developers.com/showpost.php?p=14654927&postcount=36
Click to expand...
Click to collapse
The person to ask this to is Morfic. He's all about tweaking bus speeds to improve not only cpu but gpu performance as well. But much of what you've already requested has been incorporated
jlevy73 said:
The person to ask this to is Morfic. He's all about tweaking bus speeds to improve not only cpu but gpu performance as well. But much of what you've already requested has been incorporated
Click to expand...
Click to collapse
But where is he...??
G2X
CPU overclock is something that makes sense for us right now but what would a GPU overclock get us? To me thats just something that will lower the life of our phone with no real reward until games come out that our phone can't run. Right now our phone can run pretty much all games at full speed.
gpu overclocking would be sweet... now my question would be has anyone tried to load Optimas 2x kernel/software on the g2x since they are pretty much the same hardware(in theory you would think it would work)... i might even try to load this kernel onto my phone when i get home from work so if i mess anything up ill have my gear to fix it
crisis187 said:
gpu overclocking would be sweet... now my question would be has anyone tried to load Optimas 2x kernel/software on the g2x since they are pretty much the same hardware(in theory you would think it would work)... i might even try to load this kernel onto my phone when i get home from work so if i mess anything up ill have my gear to fix it
Click to expand...
Click to collapse
Please don't try to load O2x software on your G2x.
pyckvi said:
I was browsing the Optimas 2x forum today and ran into an awesome kernel with GPU overclock. which sounds pretty cool to me. also the dev mentioned something about overclocking "system bus" which improvers memory/2D/3D/etc. i think someone in this forum should take a look into this KERNEL and try letting us taste some of this goodness.
Here are the links:
http://forum.xda-developers.com/showthread.php?t=1119771
http://forum.xda-developers.com/showpost.php?p=14654927&postcount=36
Click to expand...
Click to collapse
I remember reading a while ago that GPU/System bus overclocking was attempted by some kernel dev, then later on, the dev realized through extensive testing that GPU and system bus clocks were locked, the changes to the kernel source had no effect (hardwired). Now this was a few months ago when I was reading up on Tegra kernel development before I got my G2x. Now all these could have been obsolete, and maybe now someone has found a way to do the above via kernel source updates.
Another issue that most people don't mention here and many people have been guilty of, is the GPL issue. The guy who supposedly did this overclocking has not published his kernel source code anywhere (GPL/XDA rules issues), so no one can examine what he did and prove that it worked....
GideonX said:
Please don't try to load O2x software on your G2x.
Click to expand...
Click to collapse
have you tried it yet though is my question
im not worried if i flash a kernel and it doesnt work i can reflash my old kernel if it doesnt work and gets stuck into a bootloop
crisis187 said:
have you tried it yet though is my question
Click to expand...
Click to collapse
Someone in another thread tried this and it messed up their baseband. A restore doesn't fix it apparently.
Big rush dog, the tiamat kernel guru and Guy getting engadet headlines for oc the xoom to 1.7 ghz has gpu oc in his kernels. I will be honest though, I can't tell the difference except maybe video streaming works a little smoother. I personally don't think it is worth the devs time...
Sent from my LG-P999 using XDA App
Howdy! I'm the developer of that kernel
To be honest the GPU overclocks aren't all that beneficial. There is a little bit of a speed bump (I managed to get the highest score on nenamark2 for example). But the difference is was 27fps vs 32fps. If someone is interested in incorporating that into the g2x I'll be happy to show them the changes I've made. I haven't released the source because I'm lazy but there isn't too much to it.
Actually, if you look at the voltKernel sources for the O2X you'll see the same changes there.
chuckhriczko said:
CPU overclock is something that makes sense for us right now but what would a GPU overclock get us? To me thats just something that will lower the life of our phone with no real reward until games come out that our phone can't run. Right now our phone can run pretty much all games at full speed.
Click to expand...
Click to collapse
Yes, superficial benchmarks like quadrant can be pushed to 5400 only with max cpu oc.
However, did you notice how 1.2 thru 1.5 gets you the same fps with no added benefit than more heat created?
Pushing other things other than cpu should let us remove bottlenecks and not tighten them up.
If you want your G2x to life 20yrs, 1.5ghz is not the way to go.
I have no kernel ready for release, to notice changes, I stuck to 1.5ghz, but the final result will be more likely 1.2 or 1.3ghz.
Maybe with a "don't hold my hand, give me freedom or give me death" DBU version at 1.5Ghz later.
I'm not shy to increase vcore on a SoC. But unlike the Nexus S, this thing gets HOT, fast.
Avetny pointed out that thread, I'll see if fallout hit something I have missed so far.
The clocks get compared to chip defaults in many places, choosing the smaller of the two, so it's just tedious replacing them with sane defaults, unless I stick to my current approach of offsets instead of absolutes.
We'll see.
That's also the reason I don't update my kernel often. Right now commits in cm git are only preparatory, config changes that made things smoother I already used.
I'll release something if they finish their version of BLN.
Or if I'm happy with gpu/bus/ram oc/tweaks.
not going to make people flash a kernel for no reason. As jlevy can attest, kernel not following cm git, not even based on it can work very well.
Not having latest cm commit on kernels that take another approach is not always useful.
Especially if we track regressions that cm devs back out later, that's all this gains.
So yes, there will be a gpu oc, when it's ready.
Great!
@ fallout0 thank you i hope that you can help out one of our devs on this.
morfic said:
Yes, superficial benchmarks like quadrant can be pushed to 5400 only with max cpu oc.
However, did you notice how 1.2 thru 1.5 gets you the same fps with no added benefit than more heat created?
Pushing other things other than cpu should let us remove bottlenecks and not tighten them up.
If you want your G2x to life 20yrs, 1.5ghz is not the way to go.
I have no kernel ready for release, to notice changes, I stuck to 1.5ghz, but the final result will be more likely 1.2 or 1.3ghz.
Maybe with a "don't hold my hand, give me freedom or give me death" DBU version at 1.5Ghz later.
I'm not shy to increase vcore on a SoC. But unlike the Nexus S, this thing gets HOT, fast.
Avetny pointed out that thread, I'll see if fallout hit something I have missed so far.
The clocks get compared to chip defaults in many places, choosing the smaller of the two, so it's just tedious replacing them with sane defaults, unless I stick to my current approach of offsets instead of absolutes.
We'll see.
That's also the reason I don't update my kernel often. Right now commits in cm git are only preparatory, config changes that made things smoother I already used.
I'll release something if they finish their version of BLN.
Or if I'm happy with gpu/bus/ram oc/tweaks.
not going to make people flash a kernel for no reason. As jlevy can attest, kernel not following cm git, not even based on it can work very well.
Not having latest cm commit on kernels that take another approach is not always useful.
Especially if we track regressions that cm devs back out later, that's all this gains.
So yes, there will be a gpu oc, when it's ready.
Click to expand...
Click to collapse
thanks morfic i hope everything goes smooth with your kernel, i would love to test it out once u feel it is ready. and thanks for not rushing it.
faux123 said:
I remember reading a while ago that GPU/System bus overclocking was attempted by some kernel dev, then later on, the dev realized through extensive testing that GPU and system bus clocks were locked, the changes to the kernel source had no effect (hardwired). Now this was a few months ago when I was reading up on Tegra kernel development before I got my G2x. Now all these could have been obsolete, and maybe now someone has found a way to do the above via kernel source updates.
Another issue that most people don't mention here and many people have been guilty of, is the GPL issue. The guy who supposedly did this overclocking has not published his kernel source code anywhere (GPL/XDA rules issues), so no one can examine what he did and prove that it worked....
Click to expand...
Click to collapse
You should talk to Fallout0 he seems like he got past the system bus/GPU locked issue. both of you can maybe learn something new from each other. & it would be awesome if the both of you can work on a kernel together.
Wouldn't a higher clocked G2x cause more heat? Heat being the reason this things reboots so often? Maybe a slower G2x is the way to go.
Would overclocking the gpu help run nds4droid any better? What else would ocing the gpu do? Everything seems to be very fast as it is lol
Sent from my LG-P999 using XDA Premium App
dkb218 said:
Wouldn't a higher clocked G2x cause more heat? Heat being the reason this things reboots so often? Maybe a slower G2x is the way to go.
Click to expand...
Click to collapse
Pushing cpu more I don't see useful other than keep up with your buddy's Nexus S' quadrant scores and make sure your hands stay warm in a cold Chicago winter.
I build kernels usually when things stutter or otherwise annoy me. The pushing the OC usually comes by request of those who just want more more more.
I do like to remove bottle necks.
The hardwired clocks. Well the.cpu ones are hardwired too.
The gpu/bus oc works, until boost and throttling kick in, where again values are compared to hardwired values. using offsets after the comparison would be the way around without killing boosting and throttling.
Guess main thing that stopped me is the heat at 1.5ghz, and the frowns over 1.2ghz and 1.3ghz kernels, without further "what else is in there"
Still hoping fallout can share what he/she has, it'll help making this a reality, sooner.
It's tedious. Most of all.
Guys, could u please include in our kernel deep-sleep and fast dormancy patches?
u know that its not so hard. sure, i can do it myself, but i dont want one else toolchains and kernel trees on my laptop lol. deep-sleep and dorm succesfully work on moto atrix now with 2.6* kernels
also please include stat timers in kernel configs in future?
Would you like fries with that?
Can the kernal make me sandwiches too? You know its not very hard to do just three slices of bread, toasted, Mayo, lettuce, tomato but only if its fresh, two slices of Turkey and two slices of cheese. And cut into triangles with little toothpicks holding them together.
And just to proove I'm not a jerk: please.
Sent from my LG-P999 using XDA App
LurkerRWO said:
Can the kernal make me sandwiches too? You know its not very hard to do just three slices of bread, toasted, Mayo, lettuce, tomato but only if its fresh, two slices of Turkey and two slices of cheese. And cut into triangles with little toothpicks holding them together.
And just to proove I'm not a jerk: please.
Sent from my LG-P999 using XDA App
Click to expand...
Click to collapse
some times better joise yeat sandwiches then speak
tmp_do said:
Guys, could u please include in our kernel deep-sleep and fast dormancy patches?
u know that its not so hard. sure, i can do it myself, but i dont want one else toolchains and kernel trees on my laptop lol. deep-sleep and dorm succesfully work on moto atrix now with 2.6* kernels
also please include stat timers in kernel configs in future?
Click to expand...
Click to collapse
Dude its not that easy to build a kernel.....building a rom is easy but not a kernel....
vipaman said:
Dude its not that easy to build a kernel.....building a rom is easy but not a kernel....
Click to expand...
Click to collapse
lol u kidding me? i managed kernels for moto a1200 htc hero acer liquid and ac100 and i want wat i ask.
merge some diffs from current kernel tree not so hard, u dont need developming from zero. all already done.
I'm just lazy for that
Nvm delete
nitrogen618 said:
Also, it's been proven Deep idle does not save ANY more battery than regular .
Click to expand...
Click to collapse
prooflink please. i seen against results
Let me just say please be mature.. don't answer post if you feel offended and let it rott like spme others.. plz keep the community clean.
Sent via G2X-SINGH-UI
tmp_do said:
Guys, could u please include in our kernel deep-sleep and fast dormancy patches?
u know that its not so hard. sure, i can do it myself, but i dont want one else toolchains and kernel trees on my laptop lol. deep-sleep and dorm succesfully work on moto atrix now with 2.6* kernels
also please include stat timers in kernel configs in future?
Click to expand...
Click to collapse
You know what you should do?
.........cry about it.
I can get 8 days battery life just leaving my G2x sitting there. That's proof enough that deep sleep don't do sheeeit.
Oh come on people, those requests are completely valid. Though, OP, next time don't "of course I could do it myself".
m00nman said:
Oh come on people, those requests are completely valid. Though, OP, next time don't "of course I could do it myself".
Click to expand...
Click to collapse
They're unnecessary and since no one had ever used those on a G2x kernel before, I'm assuming it would take time to figure it out. Time that would be wasted since the two things he is requesting don't help our phone at all. If he can do it himself, then he'll do it himself.
Well, those patches should increase the battery life which is pretty bad on our phone right now. My 1980mah battery did improve the situation a little, but it still doesnt come close to sony ericsson x10 or nexus s that i owned before.
Sent from my LG-P999 using xda premium
I haven't really had any battery life issues. I charge my phone at night, and then use it all day.
If I go crazy with games and tethering I might have to plug it in for a few minutes during the day, but battery life doesn't seem any worse than other phones.
Just so the OP doesn't think I'm dogging on him, there are kernel patches I've wanted before also. I'd like a kernel that supports netfilter patches so I could use a nicer wifi tether app:
http://code.google.com/p/android-wifi-tether/wiki/FAQ
But, if it can't or won't happen, I'm fine without it. If I could do it myself, I wouldn't post about being too lazy to do it.
m00nman said:
Well, those patches should increase the battery life which is pretty bad on our phone right now. My 1980mah battery did improve the situation a little, but it still doesnt come close to sony ericsson x10 or nexus s that i owned before.
Sent from my LG-P999 using xda premium
Click to expand...
Click to collapse
No, they won't. I can get over a week just leaving my phone there. Which should make it pretty clear that we don't need it.
tmp_do said:
Guys, could u please include in our kernel deep-sleep and fast dormancy patches?
u know that its not so hard. sure, i can do it myself, but i dont want one else toolchains and kernel trees on my laptop lol. deep-sleep and dorm succesfully work on moto atrix now with 2.6* kernels
also please include stat timers in kernel configs in future?
Click to expand...
Click to collapse
ok, ill start by saying im only just now getting into how the Linux kernel works on ARM devices, so i might need a real dev to confirm some of this...
deep-sleep is just a name for a sleep state on some chipsets (i think Samsung mostly uses it) tegra2 has sleep states as well, infact we have a few (LP2 and LP3 just off the top of my head) and deep-sleep is not really needed on our devices (if its even possible to implement on this device)
tegra2 as a chip itself is perfectly capable of sleeping, and does so very well, NVidia even went so far as to make their own proprietary "governor" (if you can call it that) to control speed and voltages, as well as shut down a core when its not needed. so rest assured that when its not needed, our phone is already using as little power as it can.
with regards to fast-dormancy, seeing as the base-band/radio chip in our devices is already 'flaky' at best, do you really want you phone doing the equivalent of going into 'airplane mode' every time its done sending a message? plus, unless t-mobile can use an optimized version of it (which i don't think they do) its been shown to actually increase network usage, and decrease battery life due to constantly negotiating network connections and disconnections.
also, im going to assume by stat timers you mean 'time in state', in which case that is a HUGE undertaking including rebuilding major parts of the kernel if its even possible on tegra chipsets. plus, its really only useful to see if your phone is actually sleeping, which there are other ways to do this, although they are a bit tougher.
and finally, i don't know how you meant you question to come across, put please try to be more considerate with how you phrase things. these devs, for the most part, are doing this because they want to. nobody is paying them to work on our phones (aside from an occasional donation from time to time) and they do have jobs, lives, and families outside of these phones. and despite how easy you say it is, ive been studying the kernel in this phone for almost 2 months now, pouring over forums, datasheets, and many many many versions of kernels by morfic and faux123 and im only just beginning to understand the basic ways that things are done.
hope this clears some stuff up
Thank Klathmon, for the explanation.
I am still kinda confused though, OP said Deep Sleep has been implemented into an Atrix kernel which has the same tegra chip. Maybe you are right and they just refer to one of the low power states as deep sleep. Also I tried googling for deep sleep in atrix and nothing came up
Thanks for detailed response. I think i understand all the subtleties.
So mods, please delete thread
Alright Nexus S community, First off i will say thank you to all the devs and your hard work... i havnt even begun to use all of your awesome work but there SO MUCH stuff in this forum its nutz!
I have been on an lg p500 for awhile now, running a nice CM7 port. Recently i have been given the opportunity to get a Nexus S for CHEAP. I figured why not!
So i come to you guys after about 2 hours of reading through the various threads on kernels and roms.
I am going to be looking for the combination of a kernel / rom that produces the best battery life, with good performance. It doesnt have to be the best rom in benchmarks. But one thats stable with good battery life... with a SMOOTH UI.
Obviously there is alot of developing right now due to the drop of 4.0.4... im just trying to narrow down which rom i will use and which kernel.
suggestions welcome!
Thanks
Nd4
Most ROMs that aren't HEAVILY edited don't vary much in battery life. The kernel can change the battery life a little, but it sits heavily on whether or not you are OCing/OVing. An extreme undervolt could also give you a tiny, probably negligible, boost. This is something you can change in each kernel anyway though.
As always, the biggest problem you'll face is something keeping the phone awake through a wakelock, or be woken up constantly, as well as the screen being on. No unnecessary wakelocks while idling, no rogue apps using transferring data for no reason while screen is off and no heavy OC --> great battery life.
Try out a range of ROMs and Kernels which have the features you want, here on the Nexus S forums they're all top notch
Harbb said:
Most ROMs that aren't HEAVILY edited don't vary much in battery life. The kernel can change the battery life a little, but it sits heavily on whether or not you are OCing/OVing. An extreme undervolt could also give you a tiny, probably negligible, boost. This is something you can change in each kernel anyway though.
As always, the biggest problem you'll face is something keeping the phone awake through a wakelock, or be woken up constantly, as well as the screen being on. No unnecessary wakelocks while idling, no rogue apps using transferring data for no reason while screen is off and no heavy OC --> great battery life.
Try out a range of ROMs and Kernels which have the features you want, here on the Nexus S forums they're all top notch
Click to expand...
Click to collapse
thats my problem! SO MANY awesome choices! hmmm which one to start with first.
Pick the ones which have all the features you want first, then move onto the ones which are missing one or two, and so on. TitaniumBackup will be your best friend
Harbb said:
Pick the ones which have all the features you want first, then move onto the ones which are missing one or two, and so on. TitaniumBackup will be your best friend
Click to expand...
Click to collapse
any stand out recommendations that i should at least give a try.
Thank you btw for your very warm welcome and help
nd4spdbh said:
any stand out recommendations that i should at least give a try.
Thank you btw for your very warm welcome and help
Click to expand...
Click to collapse
yes, all of them
first find a rom you like, then try all the kernels. the kernels can make a difference to the rom. it can make it worse, or much better. really, there are so many differences of opinions to whats good, as many opinions as there are users. but, being in the nexus s community, its really hard to make a wrong choice. there is just that much quality here.
personally, i use unofficial cm9 kangs as my rom with all the trinity kernels. but, i do make it a habit of trying all the kernels(and most the roms) at least once
AOKP and Bigxie ROMs, try these.
Sent from my Nexus S using Tapatalk
simms22 said:
yes, all of them
first find a rom you like, then try all the kernels. the kernels can make a difference to the rom. it can make it worse, or much better. really, there are so many differences of opinions to whats good, as many opinions as there are users. but, being in the nexus s community, its really hard to make a wrong choice. there is just that much quality here.
personally, i use unofficial cm9 kangs as my rom with all the trinity kernels. but, i do make it a habit of trying all the kernels(and most the roms) at least once
Click to expand...
Click to collapse
Pretty much this. Everyone has their personal favourite which means very little to you. Give all of the ones with features you need a try, and once you're happy with a particular ROM give it a shot with various kernels. Later you can expand your horizons.
I'm pretty sure there was a topic not too long ago about how hard it is to choose ROMs and Kernels because there are just so many of them.
Harbb said:
Pretty much this. Everyone has their personal favourite which means very little to you. Give all of the ones with features you need a try, and once you're happy with a particular ROM give it a shot with various kernels. Later you can expand your horizons.
I'm pretty sure there was a topic not too long ago about how hard it is to choose ROMs and Kernels because there are just so many of them.
Click to expand...
Click to collapse
well this is good to hear.
In the lg p500 community we had alot of roms that were almost nearly the same, and a buncha junky ones, with a few good standout roms....
Guess once i get the nexus ill begin a flashin and playing!
seems like the major kenels around here are
Air Kernel
Matrix
SG-NS-ICS
yes?
nd4spdbh said:
well this is good to hear.
In the lg p500 community we had alot of roms that were almost nearly the same, and a buncha junky ones, with a few good standout roms....
Guess once i get the nexus ill begin a flashin and playing!
seems like the major kenels around here are
Air Kernel
Matrix
SG-NS-ICS
yes?
Click to expand...
Click to collapse
dont forget Trinity Kernel, and its been around the longest
Hey all, i was hopin someone would be interested in helping me port over this kernel, its from the N7 2013(flo)
http://forum.xda-developers.com/showthread.php?t=2449919
He says it should be compatible as is or with little modifications. Thing is, i dont know where to start. Anybody interested?
EDIT: Theres a nice little network fix (PAGE 4) for anyone that has issues. I was told it could help people with network issues on T-Mobile. I haven't tested this but simms22 has.
Please read page 4 (post #33)
-----------> And give a nice big thanks to @[COLOR="SeaGreen"]simms22[/COLOR] for the suggesitons. <-------------
Andromendous said:
Hey all, i was hopin someone would be interested in helping me port over this kernel, its from the N7 2013(flo)
http://forum.xda-developers.com/showthread.php?t=2449919
He says it should be compatible as is or with little modifications. Thing is, i dont know where to start. Anybody interested?
Click to expand...
Click to collapse
you can't "port" a kernel. but you can build a kernel from n5 source based on that kernel source.
if you don't know how to build a kernel, and not just building a ready made kernel, then you have quite a bit of reading and getting educated(educating yourself even) first.
Well i guess i was hopin someone a little more educated than myself could help me through it.
I do wish you much luck though, as I'm the wrong person for help
First you learn to compile AOSP kernel for N5
then you learn how to cherry pick commits
Then you cherrypick the commits from that kernel
Sent from my Nexus 5 using Tapatalk
rootSU said:
First you learn to compile AOSP kernel for N5
then you learn how to cherry pick commits
Then you cherrypick the commits from that kernel
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
it'll involve quite a bit more than cherry picks, as the kernel, and all the numbers involved in the kernel, are for a nexus 7. the far majority of things would need to be changed/adjusted for a nexus 5.
simms22 said:
it'll involve quite a bit more than cherry picks, as the kernel, and all the numbers involved in the kernel, are for a nexus 7. the far majority of things would need to be changed/adjusted for a nexus 5.
Click to expand...
Click to collapse
Its a mammoth task. Not for the faint of heart.
Sent from my Nexus 5 using Tapatalk
I see, well anyone up for the job?
rootSU said:
Its a mammoth task. Not for the faint of heart.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
that's what I was getting to in my first post, but was trying to be easy on the op as possible
we have more ROM builders than kernel builders for a reason, because its much more involved. while it is very possible to build this kernel for the n5, it would be extremely difficult and time consuming(changing numbers and testing) for someone who has never built a basic kernel.
maybe he can talk the original dev into building a n5 variant. or talk a n5 kernel dev into it
I understand. The the original dev has been having some health issues and just got back to deving again, i really didnt want to bug him when hes already working on his own stuff,. But i assumed it wouldnt be too hard because he said it shouldnt take much modification. It would be nice if someone could do this, it is a very nice kernel. I get 7 hrs screen time with it and performance is amazing. I just thought it would be half way there considering the devices are similar
Andromendous said:
I understand. The the original dev has been having some health issues and just got back to deving again, i really didnt want to bug him when hes already working on his own stuff,. But i assumed it wouldnt be too hard because he said it shouldnt take much modification. It would be nice if someone could do this, it is a very nice kernel. I get 7 hrs screen time with it and performance is amazing. I just thought it would be half way there considering the devices are similar
Click to expand...
Click to collapse
7 hours screen on time, it's a tablet ._. Kernel hardly affects battery life in any overly major way.
Err they're not even slightly similar devices.
Sent from my Nexus 5 using Tapatalk
Lethargy said:
7 hours screen on time, it's a tablet ._. Kernel hardly affects battery life in any overly major way.
Click to expand...
Click to collapse
I beg to differ, it most definitely does. But anyways, thanks for all the help guys[emoji57]
Andromendous said:
I understand. The the original dev has been having some health issues and just got back to deving again, i really didnt want to bug him when hes already working on his own stuff,. But i assumed it wouldnt be too hard because he said it shouldnt take much modification. It would be nice if someone could do this, it is a very nice kernel. I get 7 hrs screen time with it and performance is amazing. I just thought it would be half way there considering the devices are similar
Click to expand...
Click to collapse
its a different device, period. you can not compare the two. on the n7, its very easy to get 7+ hours sot. on the nexus 5, you have to turn everything all the way down and not really use your device, except keeping the screen on for long periods. just because a kernel does well on one device, still doesn't give it a good chance on another. the best kernel for any device will be made specifically for that device. every device is completely different, has different hardware, has differently tweaked CPU(if the same CPU), has different powering and voltage needs, etc.. what can be used are the tweaks/mods he's using. but the chances are if its usable on a n5, its probably being used already.
Andromendous said:
I beg to differ, it most definitely does. But anyways, thanks for all the help guys[emoji57]
Click to expand...
Click to collapse
Nexus 5 has a 2300mAh battery and a Snapdragon 800 at 2265MHz.
Nexus 7 (2013) flo has a 3950mAh battery and a Snapdragon S4Pro quad-core 1.5GHz processor plus doesn't have a phone radio as it's Wi-Fi only.
If you're comparing battery life between the Nexus 5 and Nexus 7 you really need to do some more research.
Andromendous said:
I beg to differ, it most definitely does. But anyways, thanks for all the help guys[emoji57]
Click to expand...
Click to collapse
na, its just junk you keep hearing repeated over and over. battery life mostly depends on how you use your device, how you personally set it up, what apps you use, and the quality data(or phone) signal you get. kernel might make a slight difference, but its not really much. changing how bright you keep your screen could make a bigger difference.
For one, i didnt say i thought id get those 7hrs on my n5 im not that stupid, you are just assuming that. all i was saying is thats pretty good even for that device. I understand their different but its not like im asking to build it for the galaxy s5, THAT would be way different, get my drift?
Screen and radio are the biggest 2 drains... Keeping the CPU ramped up can do a lot too and although that is controlled by the kernel, the settings in the governor can change how the kernel controls the CPU.
Many people assume that kernel x is better on battery and kernel y is better in performance but really the difference is that dev x and dev y set their default settings for the governor in bias to battery and performance respectively.. May user can make kernel x bias toward performance and kernel y bias towards battery, the opposite to original config.
Sure some optimisations outside of this will halve small impacts over stock but devs share a lot so they're usually available across the board.
Sent from my Nexus 5 using Tapatalk
Andromendous said:
For one, i didnt say i thought id get those 7hrs on my n5 im not that stupid, you are just assuming that. all i was saying is thats pretty good even for that device. I understand their different but its not like im asking to build it for the galaxy s5, THAT would be way different, get my drift?
Click to expand...
Click to collapse
I did assume that's what you meant, sounded like it though. sorry
But i understand what your getting at, different voltages clock speeds, all i was looking for was some advice. The attitude you guys are taking about it and the attitude the dev of the kernel took about it is like the difference between two politicians at voting time, two completely different views. Now i understand he doesnt use this device but he understands what it takes to do it, now i dunno where you guys stand when it comes to the knowledge it takes to do something like this but all i was looking for was some advice, not a OMG you know nothing battle