Hi guys! I was just checking out this thread in the Bionic section and they have an overclock without that many prerequisites. http://forum.xda-developers.com/showthread.php?t=1439013All we need is a rom with init.D support and tekahuna's "symsearch.ko" and "opptimizer.ko" modules. DroidTh3ory already has init.D support in this Bionic rom so if we could get that in our roms and just find a way to apply tekahuna's modules, our device may be able to get an overclock. Let me know what you guys think. I'm not sure if this is possible but I just want to try and help the Razr XDA community. Sorry if this is arbitrary and completely unapplicable to our device.
Intriguing - conveniently, there's a thread on enabling init.d support that just popped up: http://forum.xda-developers.com/showthread.php?t=1444545
Sent from my XT910 using xda premium
Works on the atrix2
From what I read in original thread on rootzwiki Razr can gain only 50MHz addition with this.
theEnzy said:
From what I read in original thread on rootzwiki Razr can gain only 50MHz addition with this.
Click to expand...
Click to collapse
Ha, funny. Given the RAZR is factory overclocked to 1.2ghz, I suppose it's to be expected. I've underclocked mine to the 1ghz the chip is rated for to save juice anyway.
Sent from my XT910 using xda premium
razr is not overclocked versus the other omap4430 1.0Ghz devices. Parts are tested in the fab, and the ones that can do 1.2g without crash andd without heating a lot are selled to be 1.2-compatible. Other are only 1.0G approved.
It means also that overclocking a 1.0 to 1.2 may cause crash and excessive heat.
For the 1.2G parts of the razr, don't expect great overclock. the omap is more enclosed than in bionic and is already reaching the thermal policy barriere that underclock it when intensive use. If you clock the opp-max over this frequency, you will hit the barrier faster and then finish by using lower opps most of time...
greg_mp said:
razr is not overclocked versus the other omap4430 1.0Ghz devices. Parts are tested in the fab, and the ones that can do 1.2g without crash andd without heating a lot are selled to be 1.2-compatible. Other are only 1.0G approved.
It means also that overclocking a 1.0 to 1.2 may cause crash and excessive heat.
For the 1.2G parts of the razr, don't expect great overclock. the omap is more enclosed than in bionic and is already reaching the thermal policy barriere that underclock it when intensive use. If you clock the opp-max over this frequency, you will hit the barrier faster and then finish by using lower opps most of time...
Click to expand...
Click to collapse
Interesting, so not all 4430s are born equal? Is there an actual variant thereof rated at 1.2, or do they actually test every single chip individually? I wasn't implying it's unstable at 1.2ghz, and hardware design does of course come into it as you've said, but as far as I'm aware it's the exact same chip that TI rated at 1.0.
Perhaps 'clocked higher than the chip has been generally rated for by its manufacturer' is a more accurate description than 'factory overclocked'?
Sent from my XT910 using xda premium
hmmm.. this is all very interesting. I feel like the OMAP 4430 in the Razr should be at more capable than 1.2ghz. My OG Droid ran stable at 1.275ghz and it had a 3430 which was built on the 65nm chip process vs the 45 in the Razr. I must say 1.25gz as a max is quite underwhelming. I was hoping this bad boy would at least be capable of 1.5ghz.
MeNaCe2s0cieTy said:
hmmm.. this is all very interesting. I feel like the OMAP 4430 in the Razr should be at more capable than 1.2ghz. My OG Droid ran stable at 1.275ghz and it had a 3430 which was built on the 65nm chip process vs the 45 in the Razr. I must say 1.25gz as a max is quite underwhelming. I was hoping this bad boy would at least be capable of 1.5ghz.
Click to expand...
Click to collapse
I feel the same, but reality is cruel
I read some time ago on a tech website that the 4460 (1.5) and the 4430 were made from the exact same materials. The only difference is that the ones that hit a very high threshold at 1.5 were stamped 1.5. 4460's. It's not that the 4430's couldn't do 1.5ghz , most could. Just that they couldn't run the benchmark all the way to the end the amount of times needed to qualify. Odds are that any 4430 could do 1.5ghz and probably stable. We will never stress it out the way these benchmarks do.
Does anybody know if this hack could actually work and allow us to overclock our device. I think we can worry about how far we can overclock after we get an actual overclock lol. Would anyone be able to rewrite the "symsearch.ko" and "opptimizer.ko" modules for our device so we can get an overclock on our device?
MeNaCe2s0cieTy said:
Does anybody know if this hack could actually work and allow us to overclock our device. I think we can worry about how far we can overclock after we get an actual overclock lol. Would anyone be able to rewrite the "symsearch.ko" and "opptimizer.ko" modules for our device so we can get an overclock on our device?
Click to expand...
Click to collapse
No rewriting necessary. It was developed on a RAZR. Available in the download section of the OPPtimizer site. 0.1 modules only adjust top frequency. 0.2 modules adjust top frequency and voltage. As stated on the homepage, symsearch.ko is the creation of Skrilax_CZ. In case you don't know who that is, he's the guy who got 2nd-init functioning for all of us.
http://opptimizer.googlecode.com
---------- Post added at 08:21 PM ---------- Previous post was at 07:54 PM ----------
greg_mp said:
razr is not overclocked versus the other omap4430 1.0Ghz devices. Parts are tested in the fab, and the ones that can do 1.2g without crash andd without heating a lot are selled to be 1.2-compatible. Other are only 1.0G approved.
It means also that overclocking a 1.0 to 1.2 may cause crash and excessive heat.
For the 1.2G parts of the razr, don't expect great overclock. the omap is more enclosed than in bionic and is already reaching the thermal policy barriere that underclock it when intensive use. If you clock the opp-max over this frequency, you will hit the barrier faster and then finish by using lower opps most of time...
Click to expand...
Click to collapse
Very true, and something to consider the when overclocking OMAP4 devices. They don't clock as high as some would think. Although, I'm not so sure that the lag that most people are describing is the thermal policy kicking in. I've noticed that this lag can be cleared up with additional voltage, and not exhibit the behavior of getting clamped down on by the thermal policy. For example, 1250MHz on my Droid RAZR at stock 1.375V, is flaky, bump the nominal voltage to 1.388V, and it holds, and up to 1280MHz without the lagging condition.
You appear to be well informed on this subject. Good points you raise!
Lol. I'm still trying to understand the fact that we had a overclock this entire time. I never found one on the forums but I guess we had the tools available all this time. I honestly didn't know we had one.
Sent from my XT910 using xda premium
MeNaCe2s0cieTy said:
Lol. I'm still trying to understand the fact that we had a overclock this entire time. I never found one on the forums but I guess we had the tools available all this time. I honestly didn't know we had one.
Sent from my XT910 using xda premium
Click to expand...
Click to collapse
The kernel modules were only recently release. Some early testing was done in the LG Thrill community, as that was my original test device. Development was stalled a little by issues which I now realize were with the LG Thrill's kernel itself, rather than what I was doing. Got a RAZR on opening day and was able to come up with some code I feel comfortable releasing. It's only been available to the public for about a week now. I think some RAZR's will hit low 1300's... Don't know about much more.
Does this work? Is there a script for it? I have init.d support on stock from a bionic init.d cwr zip from droidrazr.com that works. What would a script look like to change voltages/ect?
Nevermind i see...its in the download section on link.
How do you run it or setup?
frostincredible on RootzWiki has created some flashable zip for Bionic, but they only work for my 0.1 modules that only support frequency manipulation. I have 0.2 modules that control voltage as well for Droid 3. You can open up his zip file and get an idea how to get things going with init.d... You can actually use his script, and just modify the echo line to say "echo 1122000000 1388000 > /proc/opptimizer", to send a voltage value, along with frequency.
http://rootzwiki.com/topic/14698-in...or-tekahunas-omap4-overclock-modules-1-10-12/
Page 2/3/4 on the official thread also has some info on init.d scripts for this.
http://rootzwiki.com/topic/14511-op...ng-kernel-modulesofficial-thread/page__st__20
CDjones over on DroidForums.net also started a good thread with some useful information:
http://www.droidforums.net/forum/dr...imental-voltage-control-support-tekahuna.html
Not the same device, but same idea.
orateam said:
I read some time ago on a tech website that the 4460 (1.5) and the 4430 were made from the exact same materials. The only difference is that the ones that hit a very high threshold at 1.5 were stamped 1.5. 4460's. It's not that the 4430's couldn't do 1.5ghz , most could. Just that they couldn't run the benchmark all the way to the end the amount of times needed to qualify. Odds are that any 4430 could do 1.5ghz and probably stable. We will never stress it out the way these benchmarks do.
Click to expand...
Click to collapse
This is not true. OMAP4460 and OMAP4430 are different chips. E.G. there are [email protected] and [email protected] the fact that the 2 products exists should be enough to say there are different.
I reckon they are not drastically different, most of the things are common.
So has anyone gained any noticable performance improvements with this? Also so it can 0nly be OC'd to 50mz more so 1.25ghz is the max? At this point is this mod developed enough for the razr for it to be a usable worth while tweak? Not dogging any devs just want to see if its worth it yet to start messing with this...
Also in the download section there is now this "MO_simple_spyder_1.5-beta-01.zip Milestone Overclock ported to Motorola Droid RAZR"
Whats that?
It depends on your particular processor, because every one is little bit different. I was able to run mine at 1300 MHz quite stable with stock voltage. But I don't see any need for more CPU power now, maybe someday
More interesting is undervolting to achieve longer battery life, which can be done with OPPtimizer too.
theEnzy said:
It depends on your particular processor, because every one is little bit different. I was able to run mine at 1300 MHz quite stable with stock voltage. But I don't see any need for more CPU power now, maybe someday
More interesting is undervolting to achieve longer battery life, which can be done with OPPtimizer too.
Click to expand...
Click to collapse
Has anyone had any good success with undervolting and battery life?
Related
How high do you think we can clock the processors on the EVO 3D? I recall they are 1.5 ghz chips underclocked to conserve battery life. Think these can hit that magical 2.0? Or at least 1.8?
I could see maybe 1.6 but honestly nothing over 1.4ghz is worth it... (batter>speed)
And nothing currently requires anything over 1.2ghz or 1.5ghz for that matter, other than peoples e-penis.
Id like to see a 1.4ghz uv kernel over 1.8ghz 1 hour battery killer but I will use and test all of them
sent from anything but an iPhone
nate420 said:
I could see maybe 1.6 but honestly nothing over 1.4ghz is worth it... (batter>speed)
And nothing currently requires anything over 1.2ghz or 1.5ghz for that matter, other than peoples e-penis.
Id like to see a 1.4ghz uv kernel over 1.8ghz 1 hour battery killer but I will use and test all of them
sent from anything but an iPhone
Click to expand...
Click to collapse
Well that's your opinion. I highly doubt a overclocking the processor to 1.8 would bring the phone down to one hour of battery life. It's not like it would be constantly running at that speed. I would prefer speed over battery life as I charge my phone every night and have plenty left over even overclocked to almost 1.3 on my EVO.
nate420 said:
I could see maybe 1.6 but honestly nothing over 1.4ghz is worth it... (batter>speed)
And nothing currently requires anything over 1.2ghz or 1.5ghz for that matter, other than peoples e-penis.
Id like to see a 1.4ghz uv kernel over 1.8ghz 1 hour battery killer but I will use and test all of them
sent from anything but an iPhone
Click to expand...
Click to collapse
I think this is less about practicality and more about pushing our phone to the limits. overclocking on an already fast enough processor on a device which runs for the most part on battery, is not needed. however it is fun and nice to see the benchmarks soar.
I say 1.8ghz-2ghz
If they're anything like the EVO 4G, then it wont be a very high overclock
But assuming all are capable of 1.5 GHz, then it would be at least a 400-450 MHz overclock!
freeza said:
If they're anything like the EVO 4G, then it wont be a very high overclock
But assuming all are capable of 1.5 GHz, then it would be at least a 400-450 MHz overclock!
Click to expand...
Click to collapse
My g2x was overclocked to 1.6ghz and its only a 1ghz dual core phone...
Id say we could see maybe 1.8ghz if this phone is really 1.5 dropped down to 1.2
sent from anything but an iPhone
fmedina2 said:
Well that's your opinion. I highly doubt a overclocking the processor to 1.8 would bring the phone down to one hour of battery life. It's not like it would be constantly running at that speed. I would prefer speed over battery life as I charge my phone every night and have plenty left over even overclocked to almost 1.3 on my EVO.
Click to expand...
Click to collapse
Again for e-penis and bragging rights on benchmarks nothing more...
As for saying 1.8 oc would kill it in a hour I was joking...
And I bet dollars to donuts you don't see a change in "speed" past 1.6ghz other than a hot battery.
Ginger bread can't fully optimize dual cores it does the job but untill a new os is out
no point ruining a battery for "speed" you won't see
sent from anything but an iPhone
While performance is key, I'd say this phone is well above the bar of expectations for most Android Apps at the current time. I'm more interested in squeezing the most battery life I possibly can via Underclocking. It will be nice to see how far this can be pushed with Two Cores to spread the workload across.
nate420 said:
I could see maybe 1.6 but honestly nothing over 1.4ghz is worth it... (batter>speed)
And nothing currently requires anything over 1.2ghz or 1.5ghz for that matter, other than peoples e-penis.
Id like to see a 1.4ghz uv kernel over 1.8ghz 1 hour battery killer but I will use and test all of them
sent from anything but an iPhone
Click to expand...
Click to collapse
btw the way i have the bigest e penis lol it is googolplex inchs
why are people saying such low numbers the second gen snapdragons can go to what 1.9? if ours is 1.5 stock dropped down to 1.2 then i think we can at least hit 2
I'd bet that the chips in these phones will be those that were unstable at 1.5 ghz. That's how chip makers do these things. They make them all the same, then those with unstable silicon are sold as a lower clock speed. Not sure I'd expect over 1.5 and that might require higher voltage. Hope I'm wrong. We'll see I guess.
hdad2 said:
I'd bet that the chips in these phones will be those that were unstable at 1.5 ghz. That's how chip makers do these things. They make them all the same, then those with unstable silicon are sold as a lower clock speed. Not sure I'd expect over 1.5 and that might require higher voltage. Hope I'm wrong. We'll see I guess.
Click to expand...
Click to collapse
Wrong, to lazy to explain for now.
toxicfumes22 said:
Wrong.....
Click to expand...
Click to collapse
Hope so!
10char
toxicfumes22 said:
Wrong, to lazy to explain for now.
Click to expand...
Click to collapse
OK, a little less lazy right now. But simply the way that manufactures choose the speeds for processors is actually simple. In the case of the 3D it IS underclocked. The processor is an asynchronous dual core with clock speeds initially set at 1.5 by Qualcom and is used in Qualcom's phone they produce for developers. It is underclocked by HTC because of battery problems listed from the 4G and the unnecessary need of 1.5GHz in a F*ing phone. Manufactures for the most part do not underclock the CPU. The reason it is set at the level it is, is because it is most stable, efficient and meets the heat extraction needs (People forget CPUs are just circuits and produce heat with more voltage). OK lets back this up shall we. OK.
That is why I'm too lazy to post thing, I have to search up a link cause most of this is my general knowledge. Anyways, the QSD8650 found in the EVO 4G is clocked at 1GHz and has been posted to a stable 1.3GHz I believe by a recent post. Now the MSM8660 is posted to be a 1.5GHz CPU, so its overclocking potential is more near 2GHz but I would suspect it to get a little warm(sweaty palms anyone?) and I wouldn't know how stable it would be either (I don't know phones the best). Why is it underclocked? Because people kept *****ing at how much battery the EVO used and as technology improves so does the efficiency of CPUs so they go with the most recent and just underclock it. I've seen a comparison graph somewhere by Qualcom but I spent about 10minutes looking for it and couldn't find it but it was really nifty. If someone finds it plz post it, it shows the energy vs Clock speed and it is very cool.
Anyways, to respond to whoever said that the 1.5GHz is the max and that all manufacturers underclock the CPU based upon the silicon is WRONG, wrong WrOnG and Rong/wong (Im sorry I dont remember the exact response). Anyways, its the heat extraction and the silicon hurts it because it doesn't let all the heat through, which is one of the reason your PS3 may have yellow lighted on you(Yes its because of the CPU disconnecting from the Motherboard, but why do you think this extra heat was generated?).
Sorry this is so long and I got distracted a few times while writing it so it I messed up or something doesn't make sense I apologize but being lazy is really a pain in the ass.
hdad2 said:
I'd bet that the chips in these phones will be those that were unstable at 1.5 ghz. That's how chip makers do these things. They make them all the same, then those with unstable silicon are sold as a lower clock speed. Not sure I'd expect over 1.5 and that might require higher voltage. Hope I'm wrong. We'll see I guess.
Click to expand...
Click to collapse
That would be the case if this wasn't an MSM 8660. You're thinking like when AMD makes chips for the HD 6970 and some are found not to be stable at 880 mhz so they bin it to use in the HD 6950 which runs at 800 mhz. These are actually sold as two separate products. In the case of the processor in the Evo it's an MSM 8660 which is sold by qualcomm to be run at speeds as high as 1.5 ghz. If they wanted to sell chips binned for lower speeds they'd have to sell it as a different model since it wouldn't be capable of the 1.5hz.
jersey221 said:
why are people saying such low numbers the second gen snapdragons can go to what 1.9? if ours is 1.5 stock dropped down to 1.2 then i think we can at least hit 2
Click to expand...
Click to collapse
1.9?
No sir it was 1.19stable...
Sent from my PC36100 using Tapatalk
donatom3 said:
That would be the case if this wasn't an MSM 8660. You're thinking like when AMD makes chips for the HD 6970 and some are found not to be stable at 880 mhz so they bin it to use in the HD 6950 which runs at 800 mhz. These are actually sold as two separate products. In the case of the processor in the Evo it's an MSM 8660 which is sold by qualcomm to be run at speeds as high as 1.5 ghz. If they wanted to sell chips binned for lower speeds they'd have to sell it as a different model since it wouldn't be capable of the 1.5hz.
Click to expand...
Click to collapse
Can you explain this to me please.
toxic and donatom,
Your explanations make perfect sense. So I hope to be wrong. Does qualcomm sell a processor with that same architecture and a lower clock advertised?
Just seems like they're not gonna throw them away if they are stable and 1.2 or 1.4 but less stable at 1.5+. The 3vo seems like a good way for them to unload those processors.
hdad2 said:
toxic and donatom,
Your explanations make perfect sense. So I hope to be wrong. Does qualcomm sell a processor with that same architecture and a lower clock advertised?
Just seems like they're not gonna throw them away if they are stable and 1.2 or 1.4 but less stable at 1.5+. The 3vo seems like a good way for them to unload those processors.
Click to expand...
Click to collapse
To my knowledge, if this happens it gets recycled. But.....if this happens a lot then they need to change their manufacturing process or that the technology isn't there yet. Like now we have the technology to do 64GB MicroSD, but why do it because most devices can only do 32GB. For the companies that do sell them, well....I don't have good words for them, I also don't know of this happening. I can understand that it could be useful for donations to universities or others that could use them for damn near free prices, but not resold even under a different name.
toxicfumes22 said:
Can you explain this to me please.
Click to expand...
Click to collapse
Well in the case of AMD with many of their chip lines they produce a higher end chip. The ones that don't fully pass the tests at the higher speed get sold as a different model with a lower clock and voltage.
I have the most experience with the HD 6970 and 6950. They both use the same GPU, but the ones in the 6950 didn't pass AMD's tests at higher speeds so they are set at a lower clock and voltage than the 6970 (they also have some shaders disbaled). They are sold as two different models even though they were made the exact same way with the same silicone. This is not new chip manufacturers have been doing this for a while.
Think of it this way I make 100k chips out of those 100k I'm going to have a percentage that can't perform at their top performance, so instead of throwing them away I make a different model and underclock it and still make money on the chips that didn't pass at the higher speed. Now sometimes I will sell more of the lower end model so I actually have to take some chips that probably would have passed as the higher end model and sell them at the lower end. In this case the user gets lucky and can unlock their chip to the performance of the higher priced model.
EDIT: What HTC is doing here is buying a 1.5ghz chip but purposely underclocking it to save battery, since they figured most users wouldn't see the .3 ghz difference but would see the difference in battery life. Again in video cards you see this but usually the other way around. A manufacturer such as Asus, gigabyte, whomever takes the best of their chips they bought and overclocks them because again some were made even better than the standards set by AMD or Nvidia.
I guess what I'm trying to say here is that ALL these chips should do 1.5 ghz stable without question, unless there isn't enough space inside for the cooling requirements at 1.5ghz (which I doubt), and most should easily go above 1.6.
Edit again since I just saw this post:
toxicfumes22 said:
To my knowledge, if this happens it gets recycled. But.....if this happens a lot then they need to change their manufacturing process or that the technology isn't there yet. Like now we have the technology to do 64GB MicroSD, but why do it because most devices can only do 32GB. For the companies that do sell them, well....I don't have good words for them, I also don't know of this happening. I can understand that it could be useful for donations to universities or others that could use them for damn near free prices, but not resold even under a different name.
Click to expand...
Click to collapse
This is something that happens mostly in higher end processors because their tolerances at those speeds are less forgiving. No manufacturing process is perfect, you're going to have some that won't perform at those very high speeds, and recycling would cost more to the company and environment then simply selling them at lower speeds. These chips are not bad, and not defective, just found to not be stable at those highest speeds, but are perfectly fine at the speeds they are being sold at, so why throw them away. If they don't meet the standards at the lower speed then yes they would be recycled.
I have a question about the 3D's dual core that I'd like more clarification on the vague answers I'm getting by searching this site and google. So I've read that the core is asynchronous so basically meaning the second core doesn't do much work unless needed as others like the tegra 2 and exynos have both cores running or something similar to that, and that this is affecting the benchmark scores. I also read that one would basically double the score of the 3D to get a more accurate reading. Can anyone confirm or further explain this?
Yes, asynchronous is when something operates on another thread whereas the main thread is still available for operating. This allows for better performance in terms of managing tasks. Now just because it doesn't score high on a benchmark, it doesn't mean it is going to perform. Also this allows for better performance for the battery.
I haven't slept for the past 12 hours so if this doesn't help you, just let me know and I will fully elaborate on how the processor will operate on the phone. Now time for bed :'(
In short, asynchronous operation means that a process operates independently of other processes.
Think of transferring a file. A separate thread will utilized for doing so. You will then be able to do background things such as playing with the UI, such as Sense since you will be using the main thread. If anything were to happen to the transferring file (such as it failing), you will be able to cancel it because it is independent on another thread.
I hope this makes sense man, kind of tired. Now I'm really going to bed.
Sent from my PC36100 using XDA App
To be more specific by asynchronous they mean that each core can run at different clock speeds. Core 1 could be at 1.2 ghz while core 2 is at 200 mhz. Most multi core processors are synchronous meaning all the cores are running at the same speed.
donatom3 said:
To be more specific by asynchronous they mean that each core can run at different clock speeds. Core 1 could be at 1.2 ghz while core 2 is at 200 mhz. Most multi core processors are synchronous meaning all the cores are running at the same speed.
Click to expand...
Click to collapse
^This too
Sent from my PC36100 using XDA App
I was also very curious to learn a little more about the async cores and how it differes from a standard "Always-On" dual core arctechiure.
Thh first page/video I found talks about the SnapDragon core specifically.
http://socialtimes.com/dual-core-snapdragon-processor-qualcomm-soundbytes_b49063
From what I've gathered, it comes down to using the second core and thus more power, only when needed. Minimizing voltage and heat to preserve battery life.
The following video goes into similar and slightly deeper detail about the processor specifically found in the EVO 3D. The demo is running a processor benchmark with a visual real time usage of the two cores. You can briefly see how the two cores are trading off the workload between each other. It was previously mentioned somewhere else on this forum, but I believe by seperating a workload between two chips, the chip will use less power across the two chips vs putting the same workload on a sinlge chip. I'm sure someone else will chime in with some additional detail. Also, after seeing some of these demos, I'm inclined to think that the processor found in the EVO 3D is actually stable at 1.5 but has been underclocked to 1.2 to conserve battery. Only time spent within our hands will tell.
Another demo of the MSM8660 and Adreno 220 GPU found in the EVO 3D. Its crazy to think we've come this far for mobile phone technology.
What occurred to me is how complex Community ROMs for such a device may become with the addition of Video Drivers that may continue to be upgraded and improved (think early Video Card tweaks for PC). Wondering how easy/difficult it will be to get our hands on them, possibly through extraction of updated stock ROMs.
EDIT: As far as benchmarks are concerned, I blame the inability of today's bench marking apps to consider async cores or properly utilize them during testing to factor the over all score. Because the current tests are most likely to be spread across cores which favors efficiency, the scores are going to be much lower than what the true power and performance of the chips can produce. I think of it as putting a horsepower governor on a Ferrari.
thanks for the explanation everyone
The best demonstration is in the first video posted, notice when Charbax looks at the monitor. There on the top right are the frequencies of the two cores, and you'll notice the both of them jumping around a lot, independent of the other. Using the cores "on-demand" only when needed ends up saving a lot of battery power, but doesn't give you any performance loss.
Harfainx said:
The best demonstration is in the first video posted, notice when Charbax looks at the monitor. There on the top right are the frequencies of the two cores, and you'll notice the both of them jumping around a lot, independent of the other. Using the cores "on-demand" only when needed ends up saving a lot of battery power, but doesn't give you any performance loss.
Click to expand...
Click to collapse
Actually I was thinking that not just the battery savings but there could be a performance gain. Think of this if the manufacturer knows they only have to clock one core up to speed when needed they can be more aggressive about their timings and have the core clock up faster than a normal dual core would since they know they don't have to clock up both processors when only one needs the full speed.
I wonder if the drop to 1.2 GHz also serves to keep heat under control. It might not just be battery savings, maybe the small case of a phone doesn't allow for proper cooling to hit 1.5 safely.
I'd love to see some confirmation that the asynchronous nature of this chipset is what's responsible for the seemingly lackluster benchmarking.
mevensen said:
I wonder if the drop to 1.2 GHz also serves to keep heat under control. It might not just be battery savings, maybe the small case of a phone doesn't allow for proper cooling to hit 1.5 safely.
I'd love to see some confirmation that the asynchronous nature of this chipset is what's responsible for the seemingly lackluster benchmarking.
Click to expand...
Click to collapse
The "horrible" benchmark scores are simply due to the tests inability to consider async core performance. Wait till the tests are able to take this into consideration.
Sent from my HERO200 using XDA Premium App
RVDigital said:
The "horrible" benchmark scores are simply due to the tests inability to consider async core performance. Wait till the tests are able to take this into consideration.
Sent from my HERO200 using XDA Premium App
Click to expand...
Click to collapse
I went through all of your links, I didn't see anything that confirms that the benches are somehow affected by the asynchronous nature of the chipset. It's not that I don't believe you, I actually had that same theory when the benches first came out. I just don't have any proof or explanation of it. Do you have a link that provides more solid evidence that this is the case?
NVIDIA actually tells a different story (of course)
http://www.intomobile.com/2011/03/24/nvidia-tegra-2-outperforms-qualcomm-dualcore-1015/
AnandTech's article does explain some of the differences
http://www.anandtech.com/show/4144/...gra-2-review-the-first-dual-core-smartphone/4
It appears that Snapdragon (Scorpion) will excel in some tasks (FPU, non-bandwith constrained applications), but will fall short in others .
I'm pretty sure none of the benchmark apps have even been updated past the release of the sensation so yeah....How could they update the app to use the asynchronus processors the if the only phones to use them have only recently been released.
Sent from my zombified gingerbread hero using XDA Premium App
I had the G2x for like 3 days and never got to root. Poor service where I live. But could the cores be set to a specific frequency independently when rooted like computers?
tyarbro13 said:
I had the G2x for like 3 days and never got to root. Poor service where I live. But could the cores be set to a specific frequency independently when rooted like computers?
Click to expand...
Click to collapse
Yea, if someone were to develop an app for that. I do not see why not.
Sent from my PC36100 using XDA App
Hmm...
If a program such as Smart bench (which takes advantage of dual cores) is stressing both cores to 1.2ghz then regardless of if both cores are active or not the bench will be accurate.
I would rather NOT have asyncronus cores as there would be lag during frequency changes...
Ex:
2 cores running at 500mhz vs 1 core @ 1ghz and other not active.
The 2 cores will produce less heat and use less energy...
Maedhros said:
Hmm...
If a program such as Smart bench (which takes advantage of dual cores) is stressing both cores to 1.2ghz then regardless of if both cores are active or not the bench will be accurate.
I would rather NOT have asyncronus cores as there would be lag during frequency changes...
Ex:
2 cores running at 500mhz vs 1 core @ 1ghz and other not active.
The 2 cores will produce less heat and use less energy...
Click to expand...
Click to collapse
There dual, it would be better for them to run asynchronous. Not only that, but it is a phone so there will be no lag between frequency changing. 2 Cores running at 500mhz will perform better than 1 core at 1ghz.
Sent from my PC36100 using XDA App
tyarbro13 said:
I had the G2x for like 3 days and never got to root. Poor service where I live. But could the cores be set to a specific frequency independently when rooted like computers?
Click to expand...
Click to collapse
This is something that the hardware needs to be capable of. Software can only do so much. As far as I've seen Tegra isn't capable of it.
I read the anandtech article and I came with conclusion that everyday task you might not see the difference between the two and while tegra2 might bench higher. The main thing people dont talk about is the GPU. Adreno 220 is a powerhouse GPU, it will probably stand strong when tegra 3 comes out.
DDiaz007 said:
There dual, it would be better for them to run asynchronous. Not only that, but it is a phone so there will be no lag between frequency changing. 2 Cores running at 500mhz will perform better than 1 core at 1ghz.
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
Huh... what are u saying? Sorry dont understand... On one hand you say asynchronous is better and on the other ur saying 2 cores @ 500 will work better?
nkd said:
I read the anandtech article and I came with conclusion that everyday task you might not see the difference between the two and while tegra2 might bench higher. The main thing people dont talk about is the GPU. Adreno 220 is a powerhouse GPU, it will probably stand strong when tegra 3 comes out.
Click to expand...
Click to collapse
What?!?
Andreno 220 is a horrible GPU. AT BEST it is equal to the GPU in the Original SGS.
The reason benches are so different is because Qualcomm has made NO improvements in the CPU. Desire HD CPU is the same as Sensations. While... SGS2 + Tegra have IMPROVED CPUs.
Arm 7 vs arm 9?
Maedhros said:
Huh... what are u saying? Sorry dont understand... On one hand you say asynchronous is better and on the other ur saying 2 cores @ 500 will work better?
What?!?
Andreno 220 is a horrible GPU. AT BEST it is equal to the GPU in the Original SGS.
The reason benches are so different is because Qualcomm has made NO improvements in the CPU. Desire HD CPU is the same as Sensations. While... SGS2 + Tegra have IMPROVED CPUs.
Arm 7 vs arm 9?
Click to expand...
Click to collapse
Dude go back to sleep. You have no clue what you are talking about.
Sent from my PC36100 using XDA Premium App
My phone is running on CM7 Beta 3 and I want to overclock it to 1.5 Ghz I followed the inscructions here http://bugbig.com/how-to-overclock-motorola-atrix-4g-to-1-5-ghz
and when I typed on the emulator : ''insmod olympus_overclock.ko'' it was written : insmod: init_module 'olympus_overclock.ko' failed (exec format error)
I'm running on Faux's kernel (faux123) so what can I do to overclock my phone to 1.5 Ghz ?
Thank you in advance
Why 1.5? What's magic about that number? Doubt we will ever see 1.5 on Atrix. Dual core already gets hot enough at 1.1 and there is no cooling available. Different to a single core OC.
Assimilated via WinBorg 4G
that guide is extremely outdated. the kernel module you're trying to use was released before the bootloader was unlocked, and as far as i've read from Faux123 there is something limiting our ability to overclock that we just haven't broken through yet.
belig1234 said:
My phone is running on CM7 Beta 3 and I want to overclock it to 1.5 Ghz I followed the inscructions here http://bugbig.com/how-to-overclock-motorola-atrix-4g-to-1-5-ghz
and when I typed on the emulator : ''insmod olympus_overclock.ko'' it was written : insmod: init_module 'olympus_overclock.ko' failed (exec format error)
I'm running on Faux's kernel (faux123) so what can I do to overclock my phone to 1.5 Ghz ?
Thank you in advance
Click to expand...
Click to collapse
A few things to consider.
May be the kernel you are using is not meant to work with CM7 Beta.
May be you are following the steps but the guide itself is broken.
May be you are trying to OC your phone to 1.5 GHz but the script is broken.
You said you are running Faux's kernel, well that kernel is only taking your phone to 1.1 GHz, how and why do you expect your phone to magically OC itself to 1.5?
Just 2 cents : I agree with CaelanT, this phone is a Monster itself. When you OC your phone to 1.1, it just bloody flies... Whats the need to OC it all the way to 1.5? Also, while OC'd, it heats up like a *****... I have seen my phone temperature reaching > 45 degrees... Man, it feels like a burning charcoal... I am just wondering if one will actually end up blowing up his/her phone just cuz of OC'd phone.
I actually keep mine underclocked...
Cheers!!!
creativedevil said:
A few things to consider.
May be the kernel you are using is not meant to work with CM7 Beta.
May be you are following the steps but the guide itself is broken.
May be you are trying to OC your phone to 1.5 GHz but the script is broken.
You said you are running Faux's kernel, well that kernel is only taking your phone to 1.1 GHz, how and why do you expect your phone to magically OC itself to 1.5?
Just 2 cents : I agree with CaelanT, this phone is a Monster itself. When you OC your phone to 1.1, it just bloody flies... Whats the need to OC it all the way to 1.5? Also, while OC'd, it heats up like a *****... I have seen my phone temperature reaching > 45 degrees... Man, it feels like a burning charcoal... I am just wondering if one will actually end up blowing up his/her phone just cuz of OC'd phone.
I actually keep mine underclocked...
Cheers!!!
Click to expand...
Click to collapse
+10
/10 chars
Hi,
If there is a limit on clock frequencies, in my experience that implies a multiplier register needs to be changed. But a 50% overclock is rather ambitious, 10% is probably the safest range.
Cheers!
NFHimself said:
Hi,
If there is a limit on clock frequencies, in my experience that implies a multiplier register needs to be changed. But a 50% overclock is rather ambitious, 10% is probably the safest range.
Cheers!
Click to expand...
Click to collapse
Excessively overclocking mobile devices - is an incredibly stupid idea,... unless you have no problem getting a hardbrick one day.
Try overclocking your desktop PC up to 50% without additional cooling and let us know how it goes. Phones have NO cooling, they weren't meant to be overclocked that much.
Besides our current Tegra 2 setup has enough performance for everything available on Android at this moment.
If anything is lagging for you, that's because:
1. Motorola released crappy laggy motoblur
2. some app developer released crappy laggy app
Why does overclocking always turn into a penis measuring contest?
Focus on software optimisation, not on more raw performance to make up for crappy code.
ok thank you everyone I'll stick with kernel faux123
xploited said:
Excessively overclocking mobile devices - is an incredibly stupid idea,... unless you have no problem getting a hardbrick one day.
Try overclocking your desktop PC up to 50% without additional cooling and let us know how it goes. Phones have NO cooling, they weren't meant to be overclocked that much.
Besides our current Tegra 2 setup has enough performance for everything available on Android at this moment.
If anything is lagging for you, that's because:
1. Motorola released crappy laggy motoblur
2. some app developer released crappy laggy app
Why does overclocking always turn into a penis measuring contest?
Focus on software optimisation, not on more raw performance to make up for crappy code.
Click to expand...
Click to collapse
Hi,
The internet has heard your complaint and will adjust itself accordingly. Lol
Cheers!
Sent from my MB860 using xda premium
Faux just tweeted ATRIX can be overclocked to 1.3 http://rootzwiki.com/showthread.php?t=1873
Sent from my MB860 using XDA App
I just overclocked my sgs 2 to 1.6ghz so I'm sure the Atrix will get there soon.
Sent from my Xoom using xda premium
I would like to see 1.5ghz too. hopefully our chipset can handle that
When I look in system info in quadrant after running full bench it only shows 1 core but when I reboot or end application and relaunch it recognizes both cores.
belig1234 said:
My phone is running on CM7 Beta 3 and I want to overclock it to 1.5 Ghz I followed the inscructions here http://bugbig.com/how-to-overclock-motorola-atrix-4g-to-1-5-ghz
and when I typed on the emulator : ''insmod olympus_overclock.ko'' it was written : insmod: init_module 'olympus_overclock.ko' failed (exec format error)
I'm running on Faux's kernel (faux123) so what can I do to overclock my phone to 1.5 Ghz ?
Thank you in advance
Click to expand...
Click to collapse
That module doesnt work, please check 0.1.8 from faux, everybody is having bootloops, but im loving to have 1.3ghz OC ^^
Sent from my MB860 using XDA App
ChongoDroid said:
I just overclocked my sgs 2 to 1.6ghz so I'm sure the Atrix will get there soon.
Sent from my Xoom using xda premium
Click to expand...
Click to collapse
SGS2 starts out with dual core 1.2GHz, so technically you haven't reached a .5GHz OC there. Even if you did, comparing the SGS2 to the Atrix is apples to oranges.
The problem with the Atrix is not only whether the hardware will OC to 1.5GHz. Heat is the biggest problem, and with very high temps on a 1.1GHz OC under load I doubt as I mentioned before we will ever reach 1.5GHz.
I don't know what temps the SGS2 processor gets to, so I can't comment on that.
1.1/1.2 GHz is quite fast enough for me, and as someone else said, it just turns into an epeen war, with no actual rhyme or reason for wanting to OC so high other than to see if it is possible, which is all good and well.
I can OC my PC way higher than it currently is, but I choose a conservative approach because I do not want to fry any components, have graphical artifacts, etc. Same goes for my phone. I want stability and to not have to wave it around in the air to manually actively cool it!
CaelanT said:
SGS2 starts out with dual core 1.2GHz, so technically you haven't reached a .5GHz OC there. Even if you did, comparing the SGS2 to the Atrix is apples to oranges.
The problem with the Atrix is not only whether the hardware will OC to 1.5GHz. Heat is the biggest problem, and with very high temps on a 1.1GHz OC under load I doubt as I mentioned before we will ever reach 1.5GHz.
I don't know what temps the SGS2 processor gets to, so I can't comment on that.
1.1/1.2 GHz is quite fast enough for me, and as someone else said, it just turns into an epeen war, with no actual rhyme or reason for wanting to OC so high other than to see if it is possible, which is all good and well.
I can OC my PC way higher than it currently is, but I choose a conservative approach because I do not want to fry any components, have graphical artifacts, etc. Same goes for my phone. I want stability and to not have to wave it around in the air to manually actively cool it!
Click to expand...
Click to collapse
hahahaha well said! but how is comparing the 2 apples to oranges??? aren't they almost identical
I have used the cpu5.sh script to overclock the prime to 1.6Ghz, and benchmark shows a good improvement. I started streaming a 720P movie, mkv format, and everything played perfect but after only 5minutes the whole aluminum frame started to heat up noticeably . So I suggest waiting for some tested overclocked rom's before overclocking to be sure you don't blow it up.
You cant say it is the CPU tweak.
1.5 & 1.6 are built into this CPU. So, technically, your not "over clocking" as your not taking this chip beyond it's design spec. It is a 1.6 capable chip.
Moto did the same thing in the first Droid. They sent the phone out "under clocked" and then later did an update and gave users a claimed speed boost, but all they did was ope up the chip to it's full capable speed & sold it as a speed improvement. That is all that has been done here, we just beat Asus to it.
Lock-N-Load said:
You cant say it is the CPU tweak.
1.5 & 1.6 are built into this CPU. So, technically, your not "over clocking" as your not taking this chip beyond it's design spec. It is a 1.6 capable chip.
Moto did the same thing in the first Droid. They sent the phone out "under clocked" and then later did an update and gave users a claimed speed boost, but all they did was ope up the chip to it's full capable speed & sold it as a speed improvement. That is all that has been done here, we just beat Asus to it.
Click to expand...
Click to collapse
You're looking at it way to simple. The fact that the tegra3 chip is capable of running at higher speed, does not mean that in the Prime it is designed to do so.
Not saying you can't run at those speeds, but at extreme conditions (warm weather) , it could be a problem.
Yeah, I don't buy into that the "Prime is not designed to" argument nor that it is the proven issue here for what I said and given the CPU tweak he is talking about does not ramp all cores so I can't see an issue that would cause one to fret... but we can agree to disagree.
What the OP should have done was use CPU Spy and look and see for how long and IF he was even using 1.5 or 1.6 speeds.
Hey - I do think we need to be careful using these tweaks and things should be watched, but give the chip is 1.6 capable, I fully believe the Prime and the cpu's can take it just fine. And either way, this is not "over clocking" technically speaking.
I would imagine (could be wrong) that this chip has overheat and quite possibly overvolt protection. Almost every chip in the last 6-8 years has had this. I remeber turning my athlon x2 on with no heatsink and it actually stayed on for about 10 minutes before turning off. Even at 1.3-1.4 it can overheat. Infact the small overclock will be minimal on heat gain until additional voltage is applied. I would be suprised.if this overclock heated this chip up more than 5 c vs stock.
Sent from my DROID RAZR using Tapatalk
benefit14snake said:
I would imagine (could be wrong) that this chip has overheat and quite possibly overvolt protection. Almost every chip in the last 6-8 years has had this. I remeber turning my athlon x2 on with no heatsink and it actually stayed on for about 10 minutes before turning off. Even at 1.3-1.4 it can overheat. Infact the small overclock will be minimal on heat gain until additional voltage is applied. I would be suprised.if this overclock heated this chip up more than 5 c vs stock.
Sent from my DROID RAZR using Tapatalk
Click to expand...
Click to collapse
IT DOES. Viperboy already confirmed this while looking around in the kernel or whatever. He posted that response in his thread in developement section. IT HAS a failsafe mechanism. I would love to know more details about it though.
PLUS what op said could be said about stock also. THE PRIME BACKPLATE GETS hot in regular performance mode. PLUS I've ran the "Real True" Overclocking. That's the combination of viperboy control mod n system tuner where all 4 cores are maxed out to 1.6Ghz. VIPERBOY control mod alone doesn't do that. PRIME runs fine n does get hot sometimes. It depends on what you doing. PLUS its always good to have a battery temperature widget so you always see the temp. IF CPU is working like crazy. You will see the battery temp go up alot. PRIME was actually designed with 1.6ghz in mind. THats why its part of the kernel. ALL ASUS did was disable it for battery longevity purposes.
Regarding the 1.6Ghz and cpuspy I had just reset the timer before I started streaming and afterwords it showed it had used 99% of the time at 1.6Ghz
Sendt from my Transformer Prime TF201 with Tapatalk
Guys, look up "speed binning". Not every CPU is capable of max speed.
tinky1 said:
Guys, look up "speed binning". Not every CPU is capable of max speed.
Click to expand...
Click to collapse
http://www.pcpitstop.com/news/maxpc/overclock.asp
I read it. Long story short, Tegra3 can easily handle it. Its all about money. WHY would Asus/Nvidia release its first quad core device already maxed out? They want people to be more hyped up down the road when they easily enable the 1.6ghz on future devices, which will have the exact same tegra3 chip in them. Prime was their testing device for future speed increases down the road on future devices. Another reason theybdidnt enable it was because tl promote battery longevity. IF IT wasn't possible or supported or tested already, it wouldn't be in the kernel for us to easily enable it with root access.
If speed binning was an issue most people would need additional voltage to get to 1.6ghz. While this may be the case i in my experiences (HUGE PC overclocker) dont believe this to be the case. I have personally achieved a 1.8 to 3.4ghz overclock on -25c temps. So i have a bit of experience.
Sent from my DROID RAZR using Tapatalk
I posted this in another thread, but the Lenovo tablet running the Tegra 3, shown at CES, is being advertised as running at 1.6ghz.
No worries about running at that speed. Once the bootloader is opened up, I'd feel perfectly fine running at 2.0ghz myself.
Sent from my cellular telephone using magic
I do not yet have a Nexus 7 to test this with. You use this at your own risk!
This is the first real kernel work I've done, so don't be surprised if it doesn't work. I've only provided a boot.img as fastboot is easy enough to use on the Nexus 7.
Features (If it works):
CPU OC to 1.7GHz maximum
CPU over volt to hopefully reach 1.7GHz
GPU OC to 600MHz
Simple IO scheduler
SmartAssV2 CPU governor
The boot.img is attached. Source can be found at my github.
If anyone here has a Nexus 7 it would be very helpful to know if it works. I should have mine soon though. If it works well, enjoy. Feedback is always welcomed, as are benchmarks. Thanks.
Removed link until fixed!
This is scary looking, an untested Overclock that's never been run on the hardware before.
I'm guessing that the T30L is just a speed binned T30 and as such this shouldn't damage it. The same overvolt (and higher) has been successful on the T30 to get even higher clocks (1.8GHz). I would test this given hardware, however I don't yet have my Nexus 7.
ben1066 said:
I'm guessing that the T30L is just a speed binned T30 and as such this shouldn't damage it. The same overvolt (and higher) has been successful on the T30 to get even higher clocks (1.8GHz). I would test this given hardware, however I don't yet have my Nexus 7.
Click to expand...
Click to collapse
This sounds interesting. Especially the 600mhz gpu OC but may I ask if you are thinking of implementing some kind of app interface to control gpu clock and voltages etc like Extweeks on google play please? As I am guessing a lot of people won't be able to go to 600mhz stably, so a way to change the OC to something like 520mhz (to bring it to T30 speed) would be a good option
I've seen voltage tweaks controlled from userspace on other devices but not the GPU clock. I'd like to get it working first, then I guess I'll look at such things, especially if there is interest.
Cel1084 said:
This is scary looking, an untested Overclock that's never been run on the hardware before.
Click to expand...
Click to collapse
you go first!
bencozzy said:
Glados kernel on the galaxy nexus allows gpu oc control.
Click to expand...
Click to collapse
Siyah kernel for the galaxy s2 and galaxy s3 both let you control gpu clock speed and voltages, might be cool to have something similar
I don't even have my Nexus yet, and i'm already downloading things to flash to it, hahah. Will report back once Google ships to the US!
if this kernel works can we control the clocks with antutu or similar?
The CPU clock should be controllable, and I'm working on making the overvolt controllable. The GPU clock is not yet controllable, and I'm not so sure where to start on that.
ben1066 said:
The CPU clock should be controllable, and I'm working on making the overvolt controllable. The GPU clock is not yet controllable, and I'm not so sure where to start on that.
Click to expand...
Click to collapse
you should put the gpu clock to 520mhz arnt t30l 413mhz stock and kai would be even slower assuming its the budget tegra3 soc
Right, here's the thing. I've spoofed the SoC speedo ID to be that of the standard T30, however, without looking through with a fine tooth comb, it seems that the top that that id goes is 600MHz. In usage, it may be 520MHz, but I'm not sure. In addition I'm fairly sure these are just speed binned, and can probably run at the higher clocks if we just add a bit more voltage, or they get a little hotter. If anyone can tell me if this actually works, then I can adjust either way.
Look at tegra3_dvfs.c, line 256-262. It seems to indicate a maximum of 600MHz.
This should be helpful to you. tegra3 technical reference manual. everything there is to know about all variants of the chip. how it works, what its capable of, schematics, diagrams, chip layout, etc,,
http://db.tt/vWWou2Fu
Thanks but I already have access to NVidia's Tegra portal, which includes the TRM for Tegra 2 and Tegra 3. I'm hoping I shouldn't have to mess with it that low level
I don't understand why anyone would want to overclock a Tegra3, which is plenty fast enough already, especially when they have never even touched the device.
Also, I don't understand why anyone with any sense would use Simple IO scheduler, which has a higher latency and lower throughput than deadline, or even the bloat that is CFQ for that matter.
And finally, I don't understand why any real 'developer' would release something like this without testing it, especially with possibly dangerous overclocking and overvoltage settings. Only on XDA...
With all due respect, you should remove it until you have tested it *yourself* and confirmed that it doesn't make your Nexus 7 vanish in a cloud of smoke.
When I feel the need the need for speed owww.
_thalamus said:
I don't understand why anyone would want to overclock a Tegra3, which is plenty fast enough already, especially when they have never even touched the device.
Also, I don't understand why anyone with any sense would use Simple IO scheduler, which has a higher latency and lower throughput than deadline, or even the bloat that is CFQ for that matter.
And finally, I don't understand why any real 'developer' would release something like this without testing it, especially with possibly dangerous overclocking and overvoltage settings. Only on XDA...
With all due respect, you should remove it until you have tested it *yourself* and confirmed that it doesn't make your Nexus 7 vanish in a cloud of smoke.
Click to expand...
Click to collapse
Our Tegra 3 CPU is a lower clock version that the normal T30, it's the T30L. I have no doubt that this will not damage your device, the voltages used are still less than used by some TF201 ROMs (the TF201 uses the T30). I included Simple IO scheduler since it is something that seems popular, latency isn't the only thing that matters (read http://www.vincentkong.com/wiki/-/w...42041E#section-Android+IO+Schedulers-Deadline). I have seen benchmarks that show both SIO and deadline as better than each other, it depends what metric you record. I didn't remove CFQ, it's not that I've added it. The scheduler can be changed if you so desire anyway.
I have not provided a simple flash package and I've clearly stated in red writing that this is UNTESTED. I do not have the device, and it is yes untested however I didn't see the point on keeping something potentially useful private. If you have the knowledge to use fastboot to flash a boot.img, you probably know how to flash back the old one too.
_thalamus said:
I don't understand why anyone would want to overclock a Tegra3, which is plenty fast enough already, especially when they have never even touched the device.
Also, I don't understand why anyone with any sense would use Simple IO scheduler, which has a higher latency and lower throughput than deadline, or even the bloat that is CFQ for that matter.
And finally, I don't understand why any real 'developer' would release something like this without testing it, especially with possibly dangerous overclocking and overvoltage settings. Only on XDA...
With all due respect, you should remove it until you have tested it *yourself* and confirmed that it doesn't make your Nexus 7 vanish in a cloud of smoke.
Click to expand...
Click to collapse
seriously harsh man, just because you don't understand doesn't mean its wrong, or right for that matter
ben1066 said:
Our Tegra 3 CPU is a lower clock version that the normal T30, it's the T30L.
Click to expand...
Click to collapse
I take it you understand why similar chips are rated at various speeds for different devices? Because they are designed with a lower thermal output and / or the cooling characteristics / power characteristics of the device are different. The T30L has lower speed apps processors, lower speed GPU and lower speed memory. All in all, it will pump out much less heat than a T30.
I have no doubt that this will not damage your device, the voltages used are still less than used by some TF201 ROMs (the TF201 uses the T30).
Click to expand...
Click to collapse
You don't *know* that it won't damage someones device, you are assuming that it won't. The likelihood is that it probably won't, but would you stake your life on it? I wouldn't, and I've been doing Android kernel development for some time.
Also, this isn't the TF201, and it isn't the T30. It is a different device with different thermal characteristics and a different SoC, you can't compare them like that.
I included Simple IO scheduler since it is something that seems popular, latency isn't the only thing that matters
Click to expand...
Click to collapse
Latency of reads and writes and throughput are the only 2 things which matter (and I mentioned both), and SIO is poor at both of them. Justin Bieber is popular, but he's still ****, so including something which is popular isn't really a good reason.
---------- Post added at 06:44 PM ---------- Previous post was at 06:33 PM ----------
foxorroxors said:
seriously harsh man, just because you don't understand doesn't mean its wrong, or right for that matter
Click to expand...
Click to collapse
Harsh perhaps, but I prefer honest. Necessary, most certainly.
It is stupid and irresponsible to release something which is untested and potentially dangerous as it isn't fair on the poor muppet that flashes it and then f**ks their device up.
It has only been released because some 'developer' wants to make his epenis bigger by releasing something for a brand new device on XDA. Not that I am saying that he is the only one, there's plenty of others that do it, but as I have one of these on order I am taking an interest in these threads and was quite surprised with what I saw.
As someone who has done kernel development for some time now, I would never dream of releasing something I haven't tested thoroughly myself, or which I have got a trusted tester to thoroughly test, but hey, this is XDA and the standards are low.
ben1066 just out of curiosity may I ask how the gpu scales frequencies on the Tegra 3 t30l please? As I am used to the galaxy s2 and s3 where you have numerous frequency steps like 166mhz, 260mhz, 350mhz and 440mhz and you have an up and down threshold to govern whether you jump up or down the available frequencies, is this similar to how the gpu in works on the tegra 3 please?
Also when you say overclock the gpu, is it replacing 416mhz with 600mhz or is it adding an extra gpu frequency step after 416mhz, so 416mhz is still available to be used if needed? Sorry one last question, if the gpu does have frequency steps like other gpus, what ones are available for use please?
I am sorry to ask, I am just so curious about these questions, and I can't find them anywhere on the internet, so any help would be greatly appreciated. Thank you so much