Related
hi,
I've been playing with a few system information apps, and they all show the same thing,
Total cores : 4
Available cores : 3
both system panel (lite) and elixir2 show the same thing
have I missed a setting somewhere ? Can we enable the 4th core ? Am I being thick ?
Cheers,
Malty
seems i was being a little hasty, i loaded up a cpu intensive application and all 4 sprang into life, i guess i was just expecting to see them available and idle, not unavailable.
my bad
malty
the 4th one is probably for redundancy
maltloaf said:
seems i was being a little hasty, i loaded up a cpu intensive application and all 4 sprang into life, i guess i was just expecting to see them available and idle, not unavailable.
my bad
malty
Click to expand...
Click to collapse
yeah, and your OP suggests to me that it was using just one instead of using 3 and leaving one out. this makes sense since you said that all 4 were active with a CPU intensive prog.
This is a feature, not a bug =)
Samsung's pegasusq governor (the tool that controls the CPU clockspeed and it's variations) has a hotplug feature, meaning it will disable any non-necessary cores to save power.
Afaik Tegra3 implements the same with it's hardware-based solution (helper core). Leave it to NVIDIA to make something easy be very complicated and expensive. Especially since Linux and the ARM-structure already allow for online hotplugging of CPU's
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
So i was really bored and messing around with the watch and ran an AnTuTu benchmark on it.
8,692 was the score. I I'm on the stock 5.0.1 just rooted.
I've pieced together some screenshots of the score and I'll attach them below.
After turning on all 4 cpus, setting the governor to performance, and changing the gpu governor to performance I got a 16,827.
Pointless but fun.
Really bored, weren`t you?
reb1995 said:
After turning on all 4 cpus, setting the governor to performance, and changing the gpu governor to performance I got a 16,827.
Pointless but fun.
Click to expand...
Click to collapse
i was unaware that the g watch was quad core i thought it was a lousy dual or single core. strange that the Galaxy live has a little powerful single core.
Trozzul said:
i was unaware that the g watch was quad core i thought it was a lousy dual or single core. strange that the Galaxy live has a little powerful single core.
Click to expand...
Click to collapse
Quad-core Cortex-A7 1.2GHz, but only one core is online and its locked at 0.7GHz.
ruben46_ said:
Really bored, weren`t you?
Click to expand...
Click to collapse
Very bored....
Trozzul said:
i was unaware that the g watch was quad core i thought it was a lousy dual or single core. strange that the Galaxy live has a little powerful single core.
Click to expand...
Click to collapse
Yeah the Snapdragon 400. Not sure what the Gear Live is though but I think it is also the Snapdragon 400.
The a72 cores always keeps running at 883 mhz but I noticed when battery level is very low, it turns off automatically, so is there anyway to turn off the a72 cores? or is it possible to make to work dynamically like when theres enough load it will turn on and in normal uses it would be off. It will drastically improve battery life and lessen heating.
If you have some kernel knowledge this could be done with the implementation of hotplug which permits disabling unneeded cores dynamically
aaz03 said:
If you have some kernel knowledge this could be done with the implementation of hotplug which permits disabling unneeded cores dynamically
Click to expand...
Click to collapse
Looks like I have to wait for a custom kernel
Turn off core control in thermal settings now u can turn off one of the cores.
With the #su, find the file "/etc/init.qcom.post_boot.sh"
Add "echo 48 > /sys/module/msm_thermal/core_control/cpus_offlined" after "case "$target" in "msm8952")"
48(110000) meams ,turn off both A72 core,
32(010000) meams ,turn off one A72 core,
12(001100) meams ,turn off two A53 cores,
Binary 1 means turning off the core ,the first two core is A72 ,others means A53 cores
846999999 said:
With the #su, find the file "/etc/init.qcom.post_boot.sh"
Add "echo 48 > /sys/module/msm_thermal/core_control/cpus_offlined" after "case "$target" in "msm8952")"
48(110000) meams ,turn off both A72 core,
32(010000) meams ,turn off one A72 core,
12(001100) meams ,turn off two A53 cores,
Binary 1 means turning off the core ,the first two core is A72 ,others means A53 cores
Click to expand...
Click to collapse
Will try, what does 48, 32 and 12 mean? will this make a72 dynamic? or it will just shut them off?
Use kernel ardiutor and untick the big cores. That will disable them for you. I used it to drop them from 800mhz to 400mhz.
Grantius said:
Use kernel ardiutor and untick the big cores. That will disable them for you. I used it to drop them from 800mhz to 400mhz.
Click to expand...
Click to collapse
It doesn't work like that
Rajdip said:
It doesn't work like that
Click to expand...
Click to collapse
Yes, it does. I just did it. I unticked the big cores and it forces them offline.
Grantius said:
Yes, it does. I just did it. I unticked the big cores and it forces them offline.
Click to expand...
Click to collapse
well it doesnt work for me, Im on AOSP 5.1.1, did you disable something before unticking the cores?
Rajdip said:
well it doesnt work for me, Im on AOSP 5.1.1, did you disable something before unticking the cores?
Click to expand...
Click to collapse
It works if u use custom kernel.And u must turn off core control or any thermal setting.
sanjib734 said:
It works if u use custom kernel.And u must turn off core control or any thermal setting.
Click to expand...
Click to collapse
give me a link to a custom kernel, I'll try
Rajdip said:
give me a link to a custom kernel, I'll try
Click to expand...
Click to collapse
https://www.androidfilehost.com/?fid=24499762636006037
sanjib734 said:
It works if u use custom kernel.And u must turn off core control or any thermal setting.
Click to expand...
Click to collapse
is that any issue occur if we disable both big core in kernal audtre? like hardware fail etc?
No, but phone will be slower
Denis:) said:
No, but phone will be slower
Click to expand...
Click to collapse
thanks for opinion
I have just bought an used LG as second phone. It runs Cyanogenmod 12.1 Lollipop 5.1.1. How can I know if the phone has been overclocked? The ex-owner isn't an expert so I wouldn't trust to keep the phone overclocked as long as it is.
Jeff Weight said:
I have just bought an used LG as second phone.
Click to expand...
Click to collapse
First install the setcpu or similar cpu overclocking app. Look for cpu clock frequency or match to your highest original cpu frequency. Means If your device support to 1.8ghz and it sets to 2.0ghz then its overclocked.
Ashwinrg said:
First install the setcpu or similar cpu overclocking app. Look for cpu clock frequency or match to your highest original cpu frequency. Means If your device support to 1.8ghz and it sets to 2.0ghz then its overclocked.
Click to expand...
Click to collapse
Thanks. Indeed that's what I thought to do..install one of those apps and check. If it is overclocked how do I remove the overclock? Would a hard reset be enough?
Jeff Weight said:
Thanks. Indeed that's what I thought to do..install one of those apps and check. If it is overclocked how do I remove the overclock? Would a hard reset be enough?
Click to expand...
Click to collapse
No. No need to hard reset. Just set to your device default max frequency.
Ashwinrg said:
No. No need to hard reset. Just set to your device default max frequency.
Click to expand...
Click to collapse
Thanks again! But if I do perform a hard reset then I can be sure 100% that a possible overclock is removed ? Sorry for my fussiness but I really care about this phone which is the same like one I had years ago and then got lost..