call me a noob but i gotta ask, just what does the kernals do to the phone thats so special, and all the ghz talk means what. i rooted my device for the teather and customizing, and now i see all this talk of kernal this, overclock that, and different ghz people are getting can someone explain to me what this does for your phone, should i be interested???
popcorn kernals?
the higher your ghz the faster your phone is.
overclocking is making your ghz higher
and kernals is what allows you to overclock(sorta)
lol dude...you should prob. take your time with customization but ghz is in reference to the speed of the processor. So...theoretically the higher the number the better your phone should perform...t, eoretically lol. Note that with a higher ghz value the worse your battery life will be unless the kernel is written really well. Also the kernel is the code that controls the devices hardware. (brain)
The nice thing is that you can generally play with different kernels without having to wipe and redo your phone. Also, if you really want to play with the various kernels out there you should get setcpu from the market. It let's you set your phone to make use of the processor in an over clocked (OC) application but it can also let you under clock your phone when your not using it, such as when the screen is off. This will help you conserve battery life. But be careful, over clocking can lead to over heating and other problems if you''re not careful
sounds very interesting, hmmm. so in the coming months people could create kernals to acheive speeds to challenge dual core phones
the kernels already are challenging dual core phones. The thunderbolt currently has a 2ghz kernel. The motorola atrix is a 1 ghz dual core... Thunderbolt definately rivals it with overclock kernel
Sent from my ADR6400L using XDA App
A "kernel" is the OS layer that sits between the applications and hardware. So, when an application says "light up LED" it eventually goes through the kernel to do this, most likely by a request/system call.
The speed of a CPU is measured in hertz (frequency). So, a 1 Ghz CPU can perform over 1 billion operations in one second. The frequency can be increased (overclocked). When you do so, this can damage the CPU (most likely due to heat). Heat can also cause the CPU to run efficiently. So, if you overclock too high, you COULD end up running slower than if you had just left it at 1 Ghz. Changing the frequency can also hinder stability.
so with it being so dangerous how do u know what kernal to trust and whats a safe limit in hertz, do u stop at 1.5, because 2ghz sounds like pushing it
This thread is so full of misinformation it is comical. To start, higher clock speed does not always result in better performance.
Secondly, everyone has their own preference. The best bet is to find the perfect balance for your needs. For many people, overclocking the CPU is not very beneficial... since the device is already plenty fast at stock 1GHz speeds. A lot of users would rather use custom kernels to make their device more power efficient and use SMARTASS governors and lower voltages.
Mess around with kernels and see what you like the best! (always remember to create a backup before flashing... this allows you to easily revert back if something goes awry).
You mean they're not popcorn kernels?? Lol
bmcclure937 said:
This thread is so full of misinformation it is comical. To start, higher clock speed does not always result in better performance.
Secondly, everyone has their own preference. The best bet is to find the perfect balance for your needs. For many people, overclocking the CPU is not very beneficial... since the device is already plenty fast at stock 1GHz speeds. A lot of users would rather use custom kernels to make their device more power efficient and use SMARTASS governors and lower voltages.
Mess around with kernels and see what you like the best! (always remember to create a backup before flashing... this allows you to easily revert back if something goes awry).
Click to expand...
Click to collapse
Very well written and informative post, thanks brah!
skinien said:
A "kernel" is the OS layer that sits between the applications and hardware. So, when an application says "light up LED" it eventually goes through the kernel to do this, most likely by a request/system call.
The speed of a CPU is measured in hertz (frequency). So, a 1 Ghz CPU can perform over 1 billion operations in one second. The frequency can be increased (overclocked). When you do so, this can damage the CPU (most likely due to heat). Heat can also cause the CPU to run efficiently. So, if you overclock too high, you COULD end up running slower than if you had just left it at 1 Ghz. Changing the frequency can also hinder stability.
Click to expand...
Click to collapse
+1 ninja point for correctly saying "over 1 billion"
Sent from my ADR6400L using XDA App
It should be noted that most phones are definitely capable of being overclocked to a reasonable extent.
the majority of kernels we nexus one users play with, is undervolting the and playing with teh voltage tables to maximize standby battery life, at the same time overclocking the high end to improve performance. but really its about lowering voltage to improve battery life.
Related
Hi... I have rooted my Samsung GS2 and payed for the OC app TEGRAK ..
But every time I go over 1400mhz the phone gets very unstable.
It even feezes at 1400 mhz when i use my navigon app...
I have tested it at 1500 mhz.. But reboots in a kind of save mode.,,,
At 1400mhz i runs Quadrant smooth with 4200 in score
And 56 MFLOPS in Linpack
But why is my phone so unstalbe?
But why is my phone so unstalbe?
Click to expand...
Click to collapse
Because it's supposed to run at 1.2Ghz.
If every SGS2 was able to run at 1.4Ghz without any issue I guess Samsung would have set them at 1.4Ghz by default (since battery life is obviously the least of their concerns ^^). When CPUs are produced, there's always variations in quality. what usually happens on x86 CPUs is that they're tested, sorted according to their max stable frequency, and then sold under different names and at different prices. For Exynos my guess is that any CPU that fails to pass the 1.2Ghz bar is just ditched, and they keep the others, some of which will work at 1.4Ghz, whereas some won't.
Now if you want to gain more stability, you can always try to increase the voltage, it usually gets more stable as voltage increases, but it also gets hotter (which can cause it to crash, or may even permanently damage the processor).
BlueScreenJunky said:
Because it's supposed to run at 1.2Ghz.
If every SGS2 was able to run at 1.4Ghz without any issue I guess Samsung would have set them at 1.4Ghz by default (since battery life is obviously the least of their concerns ^^). When CPUs are produced, there's always variations in quality. what usually happens on x86 CPUs is that they're tested, sorted according to their max stable frequency, and then sold under different names and at different prices. For Exynos my guess is that any CPU that fails to pass the 1.2Ghz bar is just ditched, and they keep the others, some of which will work at 1.4Ghz, whereas some won't.
Now if you want to gain more stability, you can always try to increase the voltage, it usually gets more stable as voltage increases, but it also gets hotter (which can cause it to crash, or may even permanently damage the processor).
Click to expand...
Click to collapse
At 1.4ghz the phone will also get hotter and it decreases the lifetime if you run 24/7 at 1.4ghz
Ok.. I know about the x86 cpu's.. But didn't think it was the same in ARM cpu's-
But I see ALOT SGS2 that runs 1800mhz..
I guess that I just have one of the not so OC lilkes...
Overclocking won't always work for everyone at same levels.
I've also seen evidence to suggest that OCing significantly reduces the life of the SGS2. Nobnut had his phone vastly overheating even on stock speeds, and constantly rebooting... He overclocked. A number of others reported similar.
Overclocking is not simple and it is not that you just click on 1400/1500 MHz and you are Overclocked. A lot of things matter here. When we overclock in our Desktops then we have to test it very thoroughly, setting up the right VCore, Bus voltage, Multiplier, checking the stability and temperature etc. etc. Tegrak OC is a nice and simple software to use, but it can't be perfect when you can't set all the settings manually other that just higher the clock rate. Personally I'd always stay with stock speed as incorrect OC could harm my CPU and GPU.
Regards.
If you know anything about overclocking then you'll understand that there are a variety of factors that affect the overclocking of a system. The overclock headroom you get from a processor varies, add to that the variables in component tolerance in the circuit board and you have a huge variety of factors that can limit the maximum frequency that you can overclock your system to.
I'll give you an example using my computers. Click on the images below:
Both processor overclock similarly on using the same components and that was the maximum I could get out of them. Now when I bought an EVGA X58 Classified motherboard and overclocked the Xeon W3520 I got it up to 4704 MHz with less vCore and less CPU VTT. All of this was done with aircooling.
My point is that not all systems will overclock the same even though they share the same model components.
Hi im thinking of doing a overclock to 1.5 ghz is it safe for the processor and the battery life witch already sucks. has anyone on here whos done it using setcpu and the rom had any problems after doing so ? and how much faster is 1.5 ghz compared to 1.2 ghz on the galaxy s2 ? and is it safe in general for the hardware of the phone will the phone get hotter or have over heating problems ? also what should my settings be for minimum maximum and the voltages ?
Of course oc is going to make ur battery life a lot worse.
Sent from my Inspire 4G using xda premium
I haven' used Setcpu in a while but I believe it's got a feature to stress test the settings to see if it can handle it. Generally the worst that happens is it'll crash. So long as it doesn't get hot. Heat=death for electronics :')
I'm using tegrak (from market) to overclock to 1.4. I found 1.5 was too unstable. Noticeable difference between 1.2 & 1.4 is almost none. Also voltage increase of 50mv was needed to gain stability. There is not much point of overclocking the device IMO unless like me u just get some satisfaction out of knowing its running faster!
Sparksltd said:
I'm using tegrak (from market) to overclock to 1.4. I found 1.5 was too unstable. Noticeable difference between 1.2 & 1.4 is almost none. Also voltage increase of 50mv was needed to gain stability. There is not much point of overclocking the device IMO unless like me u just get some satisfaction out of knowing its running faster!
Click to expand...
Click to collapse
This is true. I see no difference between 1.2 & 1.5ghz. But that doesn't keep me from running it at 1.5 when I'm playing a game anyway :'D
Sent from my Inspire 4G using xda premium
GMoneyDTP said:
Hi im thinking of doing a overclock to 1.5 ghz is it safe for the processor and the battery life witch already sucks. has anyone on here whos done it using setcpu and the rom had any problems after doing so ? and how much faster is 1.5 ghz compared to 1.2 ghz on the galaxy s2 ? and is it safe in general for the hardware of the phone will the phone get hotter or have over heating problems ? also what should my settings be for minimum maximum and the voltages ?
Click to expand...
Click to collapse
Well it's not safe, that I can say. Nothing is safe when you don't know what other things are changing with the clock rate. But still you could do that. You just have to make sure that the temperature is within limit, it will be definitely high, but make sure it's not that high.
And upping the clock rate to 1.5 GHz won't drain any extra battery than 1.2 GHz.
Regards.
GMoneyDTP said:
Hi im thinking of doing a overclock to 1.5 ghz is it safe for the processor and the battery life witch already sucks. has anyone on here whos done it using setcpu and the rom had any problems after doing so ? and how much faster is 1.5 ghz compared to 1.2 ghz on the galaxy s2 ? and is it safe in general for the hardware of the phone will the phone get hotter or have over heating problems ? also what should my settings be for minimum maximum and the voltages ?
Click to expand...
Click to collapse
I tried the overclocking and each phone is different, increase then test, there are many benchmarking apps out there, I was stable at 1.4, my kernel does not include 1.5 GHz, and irregardless of what people may say, running the phone at higher clock speeds consistently DOES drain the battery more than 1.2GHz, unless you have found a way to manipulate the laws of physics. I don't see how one can fathom the thought that you can get a faster CPU at absolutely no cost.
Many people think when the CPU running faster means you complete tasks faster, hence 1.5 would complete a task faster than 1.2 and hence save battery, but I believe we use this phone as more than a calculator, so when you are performing a task that causes the CPU to run at 1.5 for a period of time e.g playing a game, browsing or whatever you do with your phone, then the CPU has to draw more power to keep the frequency at 1.5 as compared to the CPU running at 1.2
All in all, I dialed back because I was doing fine without it and I did not need it, other people may need it, and I wasn't gaining anything. to answer your question directly, it all depends on what you do with your phone, I'm not a huge gamer or anything and the 1.2GHz has proven to be more than enough for me to have a very pleasant experience using this device
Using it occasionally is safe, unless you stress your mobile at 1.5+ ghz for more than an hour or so.
The cpu governor will only make use of higher frequencies when there is a need, so mostly you will see your mobile idling at 200 mhz.
HTCinspiration said:
Of course oc is going to make ur battery life a lot worse.
Click to expand...
Click to collapse
Not necessarily a lot worse. It depends on how you are using your phone, and what is causing it to run fast. If overclocking allows the phone to spend longer in deep sleep state, your battery will win. If its games, and by OC you achieve a higher frame rate, then the phone is doing more work, and this will be reflected in the battery life going down.
Most of the time, screen on is going to dominate. If you are a low screen-on user, I guess there is more chance for a higher max_cpu to be beneficial (it won't be used unless there is a task that requires it). More accurately, it helps some of the time, so the net result is not always obvious to predict.
How about undervolting?
Any danger in doing so- other than crashing when voltage is too low?
Before over clocking it might be worth downloading cpuspy from the market and seeing what time you spend in each speed.
Chances are most of the time you won't even hit 1.2 so might not have anything to gain by over clocking.
Then again I dont know how you use your device but I do know I was surprised when I found out.
Sent from my GT-I9100 using XDA App
I've played with the SuperSonic version of this phone (which has a 1.5Ghz core) and the results from photos/video are much better, I'm pretty sure the cameras are exactly the same but the SuperSonic benefits from the higher CPU.
I think it would be cool if somebody could write an app that states
IF user opens Camera application voltage + clock speed is increased to allow stable 1.5GHz speed
WHEN user closes camera application overclock turns off.
Thoughts?
You have a smartphone! Not a pc!
I didnt see any advantage if you oc to 1.5
Btw In normal use your phone keep in 200mhz not 1.2.
I think i only hit 1.2 two or 3 times for 3 seconds in a full battery cycle.
Sent from my GT-I9100 using xda premium
oc dosnt make sense ,there no noticeable diff,an yes very few times i hit 1.2 mostly its on 800 or few times on 1000....using a device with 1.5ghz proccesor an oc a device to 1.5 ghz which has 1ghz processor is very diff in nature....
Fair enough.
Well I wouldn't mind an app that mazes out at 1.2GHz with camera app open, as it can lag when shooting HD.
oc upto 1.4 ghz is fair enough, anything more than that is a waste. though you cant find any visible difference between 1,1.2 and 1.4 it does helps in maintaining smoothness on some situations.
yes very true i had oc my sgs1 at 1.2ghz and sgs2 at 1.4ghz but frankly i dint see the diff so after few days use i turnd to orignal settings....but many use oc an phone works fine,but depends on personel use......an yes as bala_gammer says its fine on 1.4ghz......cheeeerz
is overclocking galaxy s2 to 1.3gh safe
HEY pople and friends i want to overclock my samsung galaxy s2 to 1.3gh soo is it safe ??????.
imad.d said:
HEY pople and friends i want to overclock my samsung galaxy s2 to 1.3gh soo is it safe ??????.
Click to expand...
Click to collapse
hey mate
u really think 100mhz would make that much change? its safe btw... seen people running s2 at clock speed higher than 1.3ghz
Plz help @..Longtime hd gaming(gta sa,nfs mw , asphalt,modern combat...) using 1.4 ghz is safe?
I also noted that gameloft games are makes more over heat for phone..
Which is the best and safe voltage level for 1.4 ghz 1250mv or 1275mv or 1300mv
Iam using siyah v6.0b5 kernel with wizzedkat 3.1..
Sent from my GT-I9100 using XDA Premium 4 mobile app
Well u do not see much difference on daily usage due to oc..but it does give a smoother experience while playing high quality games
Sent from my GT-I9100 using Tapatalk
Hello, I have an HTC thunderbolt, rooted with CM7, and installed setcpu and used autodetect and I put the CPU govern to "conservative" with minimum GHz 245 and maximum 1.8GHz and I am just wondering if this is safe? because I read some threads about Compatible kernels and I jave no idea what that means, they were also talkimg about undervolting, which agaim I do not know means, anyways thanks for reading
Watoy said:
Hello, I have an HTC thunderbolt, rooted with CM7, and installed setcpu and used autodetect and I put the CPU govern to "conservative" with minimum GHz 245 and maximum 1.8GHz and I am just wondering if this is safe? because I read some threads about Compatible kernels and I jave no idea what that means, they were also talkimg about undervolting, which agaim I do not know means, anyways thanks for reading
Click to expand...
Click to collapse
If your device will run reliably at 1.8GHz, then there's not much to worry about as long as the voltage isn't too high. High voltages and heat can shorten the SoC's life or kill it altogether. Generally, I don't recommend running that fast because the performance increase isn't as great from 1.6GHz to 1.8GHz as it is from 1.41GHz to 1.6GHz. These cores weren't meant to run any faster than 1.5GHz really, and anything past that doesn't increase the performance as much as the numbers might suggest.
Also, a conservative governor probably isn't ideal if you're willing to run a device that fast. That governor would seldom, if ever, use that kind of speed. I'd suggest smartass, smartassV2, ondemand, or interactive if you're looking to see a good boost in performance.
If you're looking for an app to view and adjust voltages, IncrediControl works well. For all the nitty-gritty of overclocking, I'd recommend reading my OC guide. It's in the "Second Post" of my Q&A thread. If you've got any questions, feel free to hit me up.
So does over clocking just speed things up? What are the real benefits
Boggus said:
So does over clocking just speed things up? What are the real benefits
Click to expand...
Click to collapse
I look at it like this. My screen eats up most of my battery. The less time it's on, the better. Overclocking uses more power for the CPU, but the display spends less time telling you it's waiting. It doesn't really add functionality, just speed and efficiency.
Hey guys,
i know that there was an overclocked kernel for GB, just curious if any developers are planning on coming out with an updated kernel for the View Honeycomb that will support overclocking....now with HC we can really push these things to the limit and get the most out of them.
hasseye said:
Hey guys,
i know that there was an overclocked kernel for GB, just curious if any developers are planning on coming out with an updated kernel for the View Honeycomb that will support overclocking....now with HC we can really push these things to the limit and get the most out of them.
Click to expand...
Click to collapse
LeeDroid's ROM has a kernel which allows overclocking.
http://forum.xda-developers.com/showthread.php?t=1406851
You need kennel source first
Sent from my HTC Flyer P510e using xda premium
The CPU usable limit is about 1.8 vs. stock 1.5 Ghz. So you can get a little more, but you have to remember for most of the intensive tasks, its not the CPU.... but the GPU that does the brunt of the work, therefore you might not even notice the difference when the CPU is overclocked. For example your Gt3 game won't frame any faster because the video is rendered by the GPU, not the CPU. The custom kernels also enable some difference CPU governor schemes, which might improve observed performance for some things. All of these things factor into battery usage. In general increased performance means more aggressive use of battery power.
DigitalMD said:
The CPU usable limit is about 1.8 vs. stock 1.5 Ghz. So you can get a little more, but you have to remember for most of the intensive tasks, its not the CPU.... but the GPU that does the brunt of the work, therefore you might not even notice the difference when the CPU is overclocked. For example your Gt3 game won't frame any faster because the video is rendered by the GPU, not the CPU. The custom kernels also enable some difference CPU governor schemes, which might improve observed performance for some things. All of these things factor into battery usage. In general increased performance means more aggressive use of battery power.
Click to expand...
Click to collapse
Hey, what about our bragging rights?
We already have the fastest CPU on the market. Do you want to crush and disenfranchise the competition?
I actually would prefer under clocking, undervolting better process management. I want better battery life.
Leedroids, custom kernel , and others, allow for under or over and also for precise voltage adjustments at each speed. Other ways to get better battery are various governors that are less aggressive than the performance governor. Check the Leedroid and other treads for more info. Of course the biggest power eaters are the display and the GPU, if you are doing video or games the GPU will consume a lot and there is not much to can do with that. Display on eats battery, you can reduce brightness to help.
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