Related
hey guys,
looking to make the jump to 2.1 rom (most probably htcclay). but ive been looking at alot of different threads and i'm seeing a lot of comments regarding overclocking, setcpu, 528Mhz, 710Mhz, and JIT.
I'm trying to make sense of it all and want to know how to understand it properly. can anyone help? or point me in the right direction with a link explaining stuff?
im currently using a 32A magic with the old radio =)
Noob tries to help noob:
MHz refers to the frequency of the CPU. This reflects the speed at which operations are executed on an overall level. The original HTC Magic ROM was around 312 MHz if I remember correctly (which was in fact underclocked). Then the threshold was pushed to original frequency (around 512 MHz).
However, the frequenzy is not fix but rather adaptive in a range (speed stepping). If an application requires CPU time, the frequency goes up to those values indicated in the paragraph above. When the processor is idle however, frequency goes done to somewhere around 200MHz to save power (as higher MHz consumes more power).
Therefore 710 MHz reflects the upper limit of the range and is beyond the factory 512 MHz. Thus you gain roughly 30% peak performance.
JIT: Just In Time compilation. Another way to compile the Java code . This methode is introduced by replacing a library in the system and available in ROMs >= Android 1.6 . The performance gain is said around 30% but... I don't now whether this affects only apps or the overall system.
Hope this helps (probably not all numbers given are correct, but the concept should be).
Romwise I stick with Sanpei's Eris port. Not overclocked but smooth and good for everyday live
thanks for that dude! that makes a hell of a lot more sense to me =)
i popped the htcclay 2.1 rom from for 32A on last night and its working a charm. i set the frequency to max 528MHz, and min 245Mhz.
Is there any recommended settings to optimize the battery life so you can use it as an everyday rom? I grown quite fond of android 2.1, and the launcherpro beta is SO fast.
i know the whole idea of SetCPU is to customise whats right for you, but because I'm knew to all this I just need some direction as to what the best general settings are
Yes the non-sense 2.1 ROMs are speed wise amazing. I missed the HTC dialer though. I like to be able to type names on the keypad which is - to my knowledge - not possible on standard dialer. Also the HTC calendar app is a thing I havily rely on and the 2.1 Andorid Calendar is simply crap in comparison. That's why I stick with Sense ROMs.
However, speaking of overclocking. There is now clear rule. To factors affect your choice: your phone usage pattern, the individual quality of your hardware.
Hardware Quality: Processors and boards are guaranteed to operate flawless in a certain frequency range. Most processors can handle more that guaranteed (because there is a safety margin introduced by the factory) . However, how much more the processory can actually handle (before it starts to throw errors and faults) is rather individual.
Usage pattern meaning: if you're a havy gamer and you play ressource hungry games you will put the upper threshold as high as possible (however, you might also consider buying an XBOX which is more fun). Also if you feel that your phone response is sluggish. But, as long as you feel fine with the response of your phone, I would not go up with frequency (not for power reasons, rather stability of the OS). Go up if you feel that you need more processing power.
The lowest threshold is probably 128 MHz. I never tried that because I read of phones which would not wake up after having gone in standby. This is not dangerous (you only have to reboot) but personally I cannot afford to miss a call because of that. So I stick above 200.
Regards,
F
well in regards to my usage pattern, i dont play any games on my phone at all. for the reason being i dont want it to consume battery on the handset.
i dont even use it much for calls. i do a LOT of sms, facebook, youtube, emails, and some widgets which requires data usage. so what would u recommend for something like this? i want the rom to be zippy, not sluggish, but not drain the battery too fast?
and how do i know which operations/apps require CPU time?
no doubt about sense-ui is amazing! im even thinking of getting a htc desire soon, or just seeing what else is coming out soon. which model of phone are u using the sanpei eris port??
32A, New Radio. Use Radio Switcher from eyegor: Sticky Post. Works like charm but be careful and read the instructions (or you might end up buying a desire sooner than you intended to). I am usind a partitioned SD with EXT 3 System for apps2SD and a cache partition. SD can be formatted this way from Recovery.
I think Sanpei's Eris is the best 2.1 compromise for the time being. However, based on your comments on how you use your phone, probably you even don't need 2.1 and are fine with 1.5. Then try this (this is also for the new Radio: use Radio Switcher)
Cursorsense's 1.5 (Most solid build I know of)
http://forum.xda-developers.com/showthread.php?t=592856
Then before booting flash this:
http://forum.xda-developers.com/showthread.php?t=681378
Boot and fasten your seatbelt. It's not as fast as HTCClay... but its the closest experience you can get with any Sense ROM...
Regards,
F
PS: Probably there is a huge flame coming our way for off topic discussion. I guess we have to stop. Going for cover
LOL! ur help has been awesome my friend =)
LOL! ur help has been awesome my friend =)
I would recommend you use cyanogenmod 5 if you want stability
sense roms cannot compare to AOSP roms for stability because they are a proprietary framework which cannot be updated unless htc releases a new version
and CM 5 is the fastest eclair rom I have tried - faster than even donut roms
i wouldnt go with 1.5....there are to many apps/widgets that wont run...
i would recommend cyan's latest 1.6 rom, 4.2.15.1 .. stable (better than stock roms), fast and has great battery life...
if you must get 2.1 then go for cyan's latest 5.0.7 test6 2.1 rom, or sanpei's if you must really want sense...
i run cyan's latest 2.1 rom and its stable as hell, as fast as his 1.6 rom, rock solid and great battery life..
ultimately its your choice.. i would stay away from JIT though, to unstable...
feicher said:
Yes the non-sense 2.1 ROMs are speed wise amazing. I missed the HTC dialer though. I like to be able to type names on the keypad which is - to my knowledge - not possible on standard dialer.
Click to expand...
Click to collapse
try DialerOne, it has the "keypad-T9" function and is free on the market
the only downside is it's really not as pretty as the sense dialer(feels a little clunky and outdated)
as far as the ROM goes, i'm using alan090's modded CM5 t5 right now, OC'd to 710MHz and with JIT enabled. best rom i've had so far, really snappy and stable. JIT seems to be very stable on my phone, i wasn't even sure i had enabled it correctly at first.. until i ran linpack and got a good 4.5 MFLOPS
I have a somewhat related question:
should i be afraid of a overclocked cpu rom heating wise? sometimes i feel my phone heating a little and i am using a default speed rom.
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.
It was suggested to me that in order to prevent excessive battery drain and heat when using CM7 I should disable one of the cores. Has anyone done this? What negative impacts could doing this cause (if any)?
webmaster said:
It was suggested to me that in order to prevent excessive battery drain and heat when using CM7 I should disable one of the cores. Has anyone done this? What negative impacts could doing this cause (if any)?
Click to expand...
Click to collapse
If anything it would increase battery drain due to all the processing being put on one single core, what I would recommend for a decrease in battery drain is different kernels with under volting options. That's what's worked best for me.
Sent from my Sensation using xda premium
Chilled26 said:
If anything it would increase battery drain due to all the processing being put on one single core, what I would recommend for a decrease in battery drain is different kernels with under volting options. That's what's worked best for me.
Sent from my Sensation using xda premium
Click to expand...
Click to collapse
It was my perception that the older single core phones had better battery life. Do you really think it would hurt the battery?
Dual core isn't properly utilized yet so it might not be a bad idea.
Here is an example of my battery drain for today with the bricked kernel v1.4.
Sent from my Sensation using xda premium
Changing kernel and undervolting did the trick for me. Getting 20 hours moderate use.
Sent from my Sensation using xda premium
Chilled26 said:
Here is an example of my battery drain for today with the bricked kernel v1.4.
Sent from my Sensation using xda premium
Click to expand...
Click to collapse
What are your settings?
Most of the time when both cores are on the 2nd isn't doing anything, because the first core isn't even pushed enough to reach max. So, I feel 1 core is sufficient, I'm running 4.1.x w/ 1 core @800 and the battery and speed are fine. Although I see others running speeds of 1.2 and higher, but I barely notice the difference of the freqs. The S3 is so fast that the higher clocks are overkill IMO.
Ace42 said:
Most of the time when both cores are on the 2nd isn't doing anything, because the first core isn't even pushed enough to reach max. So, I feel 1 core is sufficient, I'm running 4.1.x w/ 1 core @800 and the battery and speed are fine. Although I see others running speeds of 1.2 and higher, but I barely notice the difference of the freqs. The S3 is so fast that the higher clocks are overkill IMO.
Click to expand...
Click to collapse
I suspect you see a noticeable difference in battery life then? Also, what method did you use to disable the second core?
webmaster said:
What are your settings?
Click to expand...
Click to collapse
Honestly I don't even touch the settings I just run at default.
Sent from my Sensation using xda premium
Pretty snappy
su
chmod 644 /sys/devices/system/cpu/cpu1/online
echo "0" > /sys/devices/system/cpu/cpu1/online
chmod 444 /sys/devices/system/cpu/cpu1/online
Someone in faux kernel forum was talking about doing this. Gscript app makes it easy to run script. If you dont like it just reboot and 2nd core is back on.
Sent from my Sensation using XDA Premium App
Chilled26 said:
Honestly I don't even touch the settings I just run at default.
Sent from my Sensation using xda premium
Click to expand...
Click to collapse
I tried Faux's and it was ok, I plan on trying Bricked tomorrow. However if disabling a core gives even better results then that might be the way to go.
webmaster said:
I suspect you see a noticeable difference in battery life then? Also, what method did you use to disable the second core?
Click to expand...
Click to collapse
echo 0 > /sys/devices/system/cpu/cpu1/online
I do see a difference in battery life, which is why I prefer this setup, when we have ICS I will use both cores. But I feel cheated on Ginger so I use 1 for now, and whoever said two cores has better batt is wrong...Logically two cores use twice the voltage, that means 1 cores will save a significant amount of power. A weak dual core w/ 1 core on will have bad life, but a fast on is different.
Ace42 said:
echo 0 > /sys/devices/system/cpu/cpu1/online
Click to expand...
Click to collapse
Is that permanent or does it need to be run each time you reboot?
webmaster said:
Is that permanent or does it need to be run each time you reboot?
Click to expand...
Click to collapse
Every boot, you can make a linux script(.sh) if you want, and then use script manager. But, I'm only testing this for comparison, I can't see the speed difference w/ 1 or 2 so I just use 1. 1 @800 core feels how fast my MT4G did when OC'd @1.4Ghz.
Ace42 said:
Every boot, you can make a linux script(.sh) if you want, and then use script manager. But, I'm only testing this for comparison, I can't see the speed difference w/ 1 or 2 so I just use 1. 1 @800 core feels how fast my MT4G did when OC'd @1.4Ghz.
Click to expand...
Click to collapse
How long have you been running like that?
I run Faux kernel, Joe's RCU, undervolted -50mV and underclocked to 1Ghz, I can now easily make it through the day and I'm a moderate to heavy user. I'm pretty sure disabling the second core isn't necessary, and frankly, if you check out how little it's used, it probably wouldn't benefit that much anyhow.
Ace42 said:
echo 0 > /sys/devices/system/cpu/cpu1/online
I do see a difference in battery life, which is why I prefer this setup, when we have ICS I will use both cores. But I feel cheated on Ginger so I use 1 for now, and whoever said two cores has better batt is wrong...Logically two cores use twice the voltage, that means 1 cores will save a significant amount of power. A weak dual core w/ 1 core on will have bad life, but a fast on is different.
Click to expand...
Click to collapse
Completely false. Just because something has voltage across it doesnt mean that it is doing anything. Voltage times current equal power. Using power uses the battery.
You guys need to SERIOUSLY change the way you make decisions. Just because something SEEMS logical to you, doesnt mean it is correct. I see alot of BAD info being pushed around here.
I have CM7 and run Fauxs kernels. I FORCE both CPUs online and run at 1.56Ghz. My standby is around 30mAH...Nuff said.
Something else is messed up. Chase facts, not fiction people.
Another issue? UVing. You guys break so many rules in electrical engineering that it isnt even funny. Ive explained things so many times that I am sick of it. I wont anymore, but will let you know that you have missed some key facts.
Matt
mrg02d said:
Completely false. Just because something has voltage across it doesnt mean that it is doing anything. Voltage times current equal power. Using power uses the battery.
You guys need to SERIOUSLY change the way you make decisions. Just because something SEEMS logical to you, doesnt mean it is correct. I see alot of BAD info being pushed around here.
I have CM7 and run Fauxs kernels. I FORCE both CPUs online and run at 1.56Ghz. My standby is around 30mAH...Nuff said.
Something else is messed up. Chase facts, not fiction people.
Another issue? UVing. You guys break so many rules in electrical engineering that it isnt even funny. Ive explained things so many times that I am sick of it. I wont anymore, but will let you know that you have missed some key facts.
Matt
Click to expand...
Click to collapse
So me having better life w/ 1 core is false? Even though I've compared it w/ 2? And I don't know what your problem is but keep it to yourself, I didn't force you to respond to my post, only sharing my experiences.
webmaster said:
How long have you been running like that?
Click to expand...
Click to collapse
Almost 1 day, battery around 30 still. But I listened to music, internet, sync and played some games so my life was shorten.
Ace42 said:
So me having better life w/ 1 core is false? Even though I've compared it w/ 2? And I don't know what your problem is but keep it to yourself, I didn't force you to respond to my post, only sharing my experiences.
Almost 1 day, battery around 30 still. But I listened to music, internet, sync and played some games so my life was shorten.
Click to expand...
Click to collapse
I didnt say this. It is obvious what I said, so why would you even ask me? Just scroll up pal.
You didnt simply give an experience...You implied that your experience is LOGICAL. It may to you, but it is incorrect. Dont just throw things out there, please. It makes people with backgrounds in power and energy pissed off.
Also, my finding completely debuncts your theory. At night, while I sleep, I see 5mAH draw.
Matt
Hello,
I just installed the ressurection remix 1.5 rom, in combination with Thoravukk kernel, and i set my cpu to 1.6 ghz.
Set it at boot, and rebooted the device.
I'm really impressed about the boot speed, and overall smooth scrolling etcetera.
My question is, is there something else i need to do to keep it stable, or change other settings, like voltage, gpu, ram or anything else?
Because i'm really happy with the changes it's given me, but i don't want problems in a while.
Batterylife is not an issue, i don't expect it to last as long as it did on 1.2 ghz
Looking forward to information.
If i don't need to do anything else, i would like to know as well.
Thank you
Lost in space xD
Can any one help me with some info on where can I download the Thoravukk kernel. I've entered around 3 or 4 (including the official team blockbuster) sites and I don't see any download links
Why do you have it overclocked to 1.6? is there even a difference in performance? The phone's so powerful already lol, you could UV for better battery life, increase gpu for performance (in games) I don't think you need more Ram, I have the OG epic 4g and I have plenty lol
As far as stable, pushing your processor may create problems that you won't necessarily see at stock frequency, you get what ask for.
Sent from my SPH-D700 using xda premium
Fire n mage said:
Why do you have it overclocked to 1.6? is there even a difference in performance? The phone's so powerful already lol, you could UV for better battery life, increase gpu for performance (in games) I don't think you need more Ram, I have the OG epic 4g and I have plenty lol
As far as stable, pushing your processor may create problems that you won't necessarily see at stock frequency, you get what ask for.
Sent from my SPH-D700 using xda premium
Click to expand...
Click to collapse
Exactly what I had in mind
The Note is plenty powerful even amongst the current crop of droids. And no app requires a dual-core 1.6Gghz. The stock frequencies were chosen for a reason, I'm guessing it's quality. All chips burn out in time, they have a lifespan. But you overclock your device and you burn your chip faster.
So what I'm saying is stay with the original frequencies. Port an optimized ROM and that should suffice.
Thanks for your answers, but i really notice the differenct, especially with a reboot, it normally takes 30-40 seconds, and now in less then 10 secs i'm at my home screen, and ready to go.
Also it is smoother with scrolling, and apps launch even faster.
so the diff is hugh to me.
Battery life is not an issue, i said, even if it goes to crap, i replace it for €20,- (Just about $25,-)
And the performance is nice, but my question was if i have to set other things.
And i use lulzactiv governor, it uses only what it needs, it's not always the full 1.6 ghz. Only when speed is preferred.
@Kenepo112x40 this is where i found it, i use it now, so it works:
http://forum.xda-developers.com/showthread.php?t=1574672
Edit: There's a zip in attachment, that's the one, install in cwm recovery
SGS2-1989 said:
Thanks for your answers, but i really notice the differenct, especially with a reboot, it normally takes 30-40 seconds, and now in less then 10 secs i'm at my home screen, and ready to go.
Also it is smoother with scrolling, and apps launch even faster.
so the diff is hugh to me.
Battery life is not an issue, i said, even if it goes to crap, i replace it for €20,- (Just about $25,-)
And the performance is nice, but my question was if i have to set other things.
And i use lulzactiv governor, it uses only what it needs, it's not always the full 1.6 ghz. Only when speed is preferred.
@Kenepo112x40 this is where i found it, i use it now, so it works:
http://forum.xda-developers.com/showthread.php?t=1574672
Edit: There's a zip in attachment, that's the one, install in cwm recovery
Click to expand...
Click to collapse
I had to go and look for the 2.30 on another post cuz the 2.41 doesn't allows me to have data on the phone. Thanks anyway man, the problem was that they hadn't uploaded the link yet on the official site but they did yesterday.
To OP, I suggest u increase voltage at over locked 1.6 to keep it stable