Related
So I installed SetCPU today. Been testing the kernels ability to work underclocked at the max of 918mhz. Also set the scaling to conservative. After a days use it's been as good as normal full speed, 1512mhz
The battery lasted throughout the day, compared to my first two days of stock settings with only 6 hours of good use.
I'll keep playing. Still want to do some testing and benchmarks to make sure it's not under performing. But at least at the user level it seems to react the same.no lag.
I did confirm the clock speed out side of SetCPU using system panel.
Sent from my rezound.
Don't bother using benchmarks to rate a phones performance that is a fatal error there. Benchmarks never effectively rate a phones performance. I just go by how smooth the phone runs and it does it run everything I throw at it. If so gg pz end of story.
zetsumeikuro said:
Don't bother using benchmarks to rate a phones performance that is a fatal error there. Benchmarks never effectively rate a phones performance. I just go by how smooth the phone runs and it does it run everything I throw at it. If so gg pz end of story.
Click to expand...
Click to collapse
True, but people still like to get the general idea. There are many factors.hence why I said the over all feel seems the same. Im going to use antutu, and quadrant. 5 times each to get a range.=-)
Sent from my rezound.
Izeltokatl said:
True, but people still like to get the general idea. There are many factors.hence why I said the over all feel seems the same. Im going to use antutu, and quadrant. 5 times each to get a range.=-)
Sent from my rezound.
Click to expand...
Click to collapse
Well whatever works for you. Just saying Quadrant is a poor tool to use to bench for many reasons which I won't go over. Antutu is nice for SD speed testing I think, oter than that meh. Benches are just for numbers for people to flex their epeens with. They just really don't truly gauge a devices performance.
zetsumeikuro said:
Well whatever works for you. Just saying Quadrant is a poor tool to use to bench for many reasons which I won't go over. Antutu is nice for SD speed testing I think, oter than that meh. Benches are just for numbers for people to flex their epeens with. They just really don't truly gauge a devices performance.
Click to expand...
Click to collapse
Benchmarks do have a some good uses... while comparing different phone models with benchmarks can be iffy, it can give an overall insight, (things like graphics capabilities with very GPU extensive games) but in the end user experience and daily use are the real judges.
Where benchmarks can be of the most use, is when comparing changes to the same phone model.
E.G. Comparing performance impacts of AOSP vs Sense, overclocking and under-clocking, and de-sensing/bloat removal.
When used for these reasons, you can get a really good feel for how changes are affecting your device overall. Even then, benchmarks are not the be all end all, and user experience is still important. As you may introduce lag or other performance issues that do not show up in benchmarks.
Which temp root method are you using? Mine isn't staying rooted long enough for me to justify using setCPU at all...
The new version and the one that comes with the newest clean tool stays until reboot.
Marine6680 said:
The new version and the one that comes with the newest clean tool stays until reboot.
Click to expand...
Click to collapse
Thx for the info, guess I must still be using the outdated method. I'll run the latest version of Scott's Clean tool and give it a shot.
Izeltokatl said:
So I installed SetCPU today. Been testing the kernels ability to work underclocked at the max of 918mhz. Also set the scaling to conservative. After a days use it's been as good as normal full speed, 1512mhz
The battery lasted throughout the day, compared to my first two days of stock settings with only 6 hours of good use.
I'll keep playing. Still want to do some testing and benchmarks to make sure it's not under performing. But at least at the user level it seems to react the same.no lag.
I did confirm the clock speed out side of SetCPU using system panel.
Sent from my rezound.
Click to expand...
Click to collapse
Please let us know what settings you use that work for you.
I generally stay temprooted unless I'm going to be away from a charger for a bit and need BT (since you can't turn BT back on after temproot). I wouldn't have SetCPU autostart on boot (since it won't ever be able to get root access immediately after boot).
Meanwhile, I also set it to conservative and will see what that accomplishes.
A kernel needs to support setcpu, stock kernels do not. You need to flash a custom kernel, so you need a development phone or s-off.
Sent from my ADR6400L using XDA App
This kernel apparently does work with SetCPU. I've confirmed using other cpu monitoring apps that the clock speed changes are capped.
I own 7 android phones, and have been rooting, overclocking, undervolting each and every single one of them (well one I still cant get rooted). I know when the cpu is under clocked and when it is not. Been doing these tweaks for 4 years now. If you use a tool like System Panel, at stock settings you can see the max cpu around 1500 on our little bad boy. When it peaks out the clock speed is shown. When you under clock it, then check again it won't go beyond the max cpu set in my testing I put a ceiling at 918mhz. System Panel reported full CPU usage (100%) at clock speed 918mhz. Typically with stock kernels, your absolutely right, changes to SetCPU do nothing at all to the real cpu. Which is confirmed, when I reboot and dont have root, if I attempt to use SetCPU and make the changes, System Panel reports 1500mhz (roughly) at full load regardless of what I set it to in SetCPU. If I did this to any of my other phones with stock kernels, you are correct it makes no difference as SystemPanel reports the stock max setting.
No I'm not being mean or aggressive, just saying. =-) And no don't believe me, but test it yourself and confirm or prove me wrong some other way and I admit error. Either way, half the fun is messing with the phone and trying to get it to do things it should not do.
Grnlantern79 said:
A kernel needs to support setcpu, stock kernels do not. You need to flash a custom kernel, so you need a development phone or s-off.
Sent from my ADR6400L using XDA App
Click to expand...
Click to collapse
Sent from my rezound.
Izeltokatl said:
No I'm not being mean or aggressive, just saying. =-) And no don't believe me, but test it yourself and confirm or prove me wrong some other way and I admit error. Either way, half the fun is messing with the phone and trying to get it to do things it should not do.
Click to expand...
Click to collapse
Or I would say, "half the fun is messing with the phone and trying to get it to do things it should have always been allowed to do...." Just sayin'.
Are you using the profiles at all? Im interested to know what seems to be working out the best for you.
Izeltokatl said:
True, but people still like to get the general idea. There are many factors.hence why I said the over all feel seems the same. Im going to use antutu, and quadrant. 5 times each to get a range.=-)
Sent from my rezound.
Click to expand...
Click to collapse
In my view, the "benchmarks" would be an OK measurement if you were comparing apples to apples.
I tried running both Linpack and Quadrant on the very recently and dearly departed Incredible right after a fresh reboot and having charged the battery overnight...when the thing should have been at it's freshest.
I got wildly different scores each time I ran it after a reboot...knowing that on both programs the scores would improve the more times you ran the test.
It didn't seem to me that either program was a reliable indicator of what my phone was capable of. I didn't even trust them to tell me whether something I'd done...cleared cache or deleted bloatware...had any real effect.
It simply boils down to how the phone feels. That's not scientific, but it works for me.
douger1957 said:
In my view, the "benchmarks" would be an OK measurement if you were comparing apples to apples.
I tried running both Linpack and Quadrant on the very recently and dearly departed Incredible right after a fresh reboot and having charged the battery overnight...when the thing should have been at it's freshest.
I got wildly different scores each time I ran it after a reboot...knowing that on both programs the scores would improve the more times you ran the test.
It didn't seem to me that either program was a reliable indicator of what my phone was capable of. I didn't even trust them to tell me whether something I'd done...cleared cache or deleted bloatware...had any real effect.
It simply boils down to how the phone feels. That's not scientific, but it works for me.
Click to expand...
Click to collapse
Linpack and Quadrant are not reliable benchmarks. TBH I don't take any of the benchmarks seriously, they are more for entertainment for me. But to each their own right?
Yeah some of the benchmark apps are a bit unreliable to say the least...
If I use one, I try to use ones that Anandtech uses. I trust them to find the better benchmark tools.
First, I KNEW the thread title would get your attention. Second, i hear 95% of you calling BS, and I would too. In fact, I am still not sure what to make of it, and it makes ME think the number I am getting is BS.
Here's the deal. Got my replacement Prime back from repair, and like more than a few (read the RMA thread) I was lucky enough to get a replacement instead of a repair. I had sent in my Prime, originally received on 1/3 (shipped on 12/23... GROUND, from Best Buy, though I had paid for overnight. Serial was: BCOKAS**5153
Sent if for repair mostly for a cosmetic issue, scratches on screen border, but I had among the worst GPS compared to others I have seen, no sats indoors, maybe 3-4 outside, never a lock. After the 1/19 update (the one that we still haven't seen a change-log for) I started getting reasonably crappy GPS, LOL as in 4-6 sats inside, and 9-12 Outside, occasional locks, but nothing usable. My Wifi was decent, actually quite good I would say. Bluetooth did not dropout when streaming to BT headset watching Netflix.
The support folks offered to open the replacement and test it before sending, and I said: **** yeah: Test everything: GPS, Wifi/BT check for stuck pixels, make sure the serial shows, also check for light bleed. I was promised they would do all these things. Then it was overnighted to me.... All in all I felt it was a reasonably GOOD RMA/support/repair experience, especially in light of the horror stories, and stories of general incompetence we have seen.
New unit arrived, looked cosmetically perfect. One spot on back, it was glue or tape adhesive from assembly no doubt. Screen appears perfect, with just the tiniest bit of light bleed. Wifi is decent, not outstanding, but close to what I had. No stuck pixels, have yet to test BT streaming. GPS? I got another dead one. I have yet to see a SINGLE FREAKING SATELLITE, Outdoors or in, though it's cloudy here today, LOL (If it's so bad that clouds kill it, it's pretty ****ed up)
So that was a bummer. Yes, it's true I will probably not use it in the car (though I did use my OG that way once in a while, but I refuse to accept something that does not work. It is not in me to say: I can do without that.... even if I CAN, LOL. They are gonna get me another one, cause I am NOT RMA'ing this and going without it a week again... not for GPS anyway. If the WiFi was borked, it would be a different story.
One additional improvement. The power button on this one works correctly. I never knew how bad mine was, but compared to the 3 TF101's I had, it sucked. You never felt it bottom ot, or any detectable motion al all. It was just stiff and stuck, and I had to just press on it super hard to get any effect from it. The new one is perfect, the spring is stronger than the TF101 switches were, but at least it has a positive motion, with a solid detent, and you can tell when it hits bottom. Man, I can't believe how bad what I had was, and I had fully planned to live with it, LOL!
Okay so now for the weirdness. I am putting the new one through tests today, and among the, I ran Antutu. The numbers I got were nothing all that amazing, but the Processor speed threw me for a loop: 1600 Hz. WTF?????
Serial is C1OKAS**1793 I thought I was hallucinating. This thins is NOT ROOTED. I have NO performance tweaks, and nothing changed other than my 126 installed apps... How weird is this???
The numbers that I got were 10222, and a couple more in that range. This was running in Balanced mode. I switched it to Performance Mode (what used to be "normal" back in the Honeycomb days" ) rebooted, and ran Antutu again. Best number to date is 11089. Like I said, not up to par with folks that have REALLY overclocked, but somewhat better than my original... Anyone want to take a stab at explaining this to me? Maybe I am missing something super obvious?
Attached the Antutu result, and one other thing: The box sticker from a "C" serial number, for those who are curious: Check it: NO GPS LISTED!!!!I forgot to take a picture of my original box before RMA, screwed up there. Took dozens of the tablet to protect myself against claims of "CID" Customer Induced Damage, and forgot the box... grrrr.
GOOD NEWS: At least for the present the BOX LABEL still shows GPS. As many of us have discussed, as long as it SAYS GPS, we can still break chops to get them to fix it (or try to, I suppose) but what is with the question mark? Does anyone know the significance of that? That is kind of weird. I am pleased they left GPS spec on the box, expecially since I now have a completely dead GPS setup. I guess it's time to practice my Vulcan Nerve Pinch, but the few squeezes I gave it so far near the GPS Pogo Pins have been completely useless. Not a SINGLE SATELLITE HAS APPEARED YET.
An the Asus Support guy went on about how the Jan 19th patch was on this one. I said: as long as you see a few sats. send it along, He said (laughably) that it would get GPS performance as good as my TF101 did. Hmm. Well, to do that, it would need to start by getting ANY performance, LOL. Then it would need to work, in the car, with CoPilot live, all the way up the East Coast... Somehow, I don't see it happening. Sorry for the long post, but I was up late last night reading the huge tear down thread, and I had no energy for posting to a dozen separate threads today, on my latest "interesting" mix of features and performance with my new Prime. These feel like hand built devices.. every one is unique, LOL!
Hmm i have a C serial too and my GPS is fine. Little worse than my dhd but fine.
Get something like CPU Spy & see what it shows in the "unused cpu states" list at the bottom.
It's not overclocked at all, since ICS the Prime has 1.5 and 1.6 ghz in the kernel, however, they are both disabled. This is the only reason we currently have over clock scripts, with root we can enable these settings.
Sent from my HTC Desire HD using xda premium
Doktaphex said:
It's not overclocked at all, since ICS the Prime has 1.5 and 1.6 ghz in the kernel, however, they are both disabled. This is the only reason we currently have over clock scripts, with root we can enable these settings.
Sent from my HTC Desire HD using xda premium
Click to expand...
Click to collapse
thisssss
TF201 | XDA Premium
Antutu says mine is 1600 too.
Doktaphex said:
It's not overclocked at all, since ICS the Prime has 1.5 and 1.6 ghz in the kernel, however, they are both disabled. This is the only reason we currently have over clock scripts, with root we can enable these settings.
Sent from my HTC Desire HD using xda premium
Click to expand...
Click to collapse
This was what I was going to show with the cpu spy app
I just checked my prime, 1.6ghz with the latest update, no modifications.
^
Mine too
BCOKAS serial number
Lock-N-Load said:
This was what I was going to show with the cpu spy app
Click to expand...
Click to collapse
Exactly. If you all use cpu spy like lock says you will see it never enters the 1.6 state. The processor has those steps built in but aren't enabled in the firmware
People in here are funny..lmao. we already went thru this when ICS first dropped. All primes were showing 1.6ghz in the stats n benchmarks. But this isn't the case. WE KNOW THIS FOR A FACT. If you take CPU spy app n look it'll show the 1.5 n 1.6Ghz speeds disbled. MEANING YOU ARE NOT OVERCLOCKED. Only real overclock you can have is if your rooted and Running ViperControl mod or using SaturnDe ATP tweaks app or running script manually from directory /system/etc..
I was the first one to assume what all of you are saying also when ICS first came out. Then we dug in n researched further n found out this wasn't the case. It did lead us to a true overclock though since we knew it was in the kernel but just disabled. Me, I'm running a "TRUE" 1.6Ghz overclock using ATP tweaks app. Mines is confirmed through CPU spy. Plus my Antutu scores are well over 13,000. So 10,000 would be bad for an overclock like that if you really had one.
SORRY TO RAIN ON YALL PARADE BUT YOURE NOT OVERCLOCKED. Only through Root n methods I listed would you "Truely" be overclocked. CPU Spy will confirm your false claim. Don't feel bad, we thought so to at first when ICS first came out but quickly realized the real truth.
No Biggie
demandarin said:
People in here are funny..lmao. we already went thru this when ICS first dropped. All primes were showing 1.6ghz in the stats n benchmarks. But this isn't the case. WE KNOW THIS FOR A FACT. If you take CPU spy app n look it'll show the 1.5 n 1.6Ghz speeds disbled. MEANING YOU ARE NOT OVERCLOCKED. Only real overclock you can have is if your rooted and Running ViperControl mod or using SaturnDe ATP tweaks app or running script manually from directory /system/etc..
I was the first one to assume what all of you are saying also when ICS first came out. Then we dug in n researched further n found out this wasn't the case. It did lead us to a true overclock though since we knew it was in the kernel but just disabled. Me, I'm running a "TRUE" 1.6Ghz overclock using ATP tweaks app. Mines is confirmed through CPU spy. Plus my Antutu scores are well over 13,000. So 10,000 would be bad for an overclock like that if you really had one.
SORRY TO RAIN ON YALL PARADE BUT YOURE NOT OVERCLOCKED. Only through Root n methods I listed would you "Truely" be overclocked. CPU Spy will confirm your false claim. Don't feel bad, we thought so to at first when ICS first came out but quickly realized the real truth.
Click to expand...
Click to collapse
Uhm... No rain on MY parade. I think you misread my meaning I don't Have any great desire to overclock my ATP. Maybe later, for now I AM interested in the Kernel Module for Background I/O. Cranking up the processor does diddly when the Prime lags, and freezes every so often, especially under any type of background disk activity. 1.4 single. 1.3 ghz Multicore speeds are more than sufficient. People that overclock do so often for the wrong reasons. Why should I be cranking along at 1.6 ghz to browse a news article? If I had ultimate control I would like to control WHEN the additional core kick in, not how fast they tick along, doing a lot of nothing. I did miss your discovery that with ICS, it shows these rates. Right now I would give my right arm to know how, if you do all your posting with the prime, you deal with the cursor misbehavior in text boxes, like when it jumps to the first character position in the box, or insists on jumping to a spot and only the arrow keys will override that. And why is it "mines" do you have multiple Primes?
Edit: Also, I wasn't stating that "11, 089" was a enormous score, if you read I was stating that it was a BETTER score than my returned Prime, but not what I would expect if overclocked. I'm glad your numbers are so impressive. Maybe someday MY Prime will have a Antutu score of over 13,000! That's really fast! And that helps exactly how?
Also, since the processor has those steps built in it technically isn't overclocking to enable the 1.6GHz step. You are only overclocking when you go above that.
SmartAs$Phone said:
Uhm... No rain on MY parade. I think you misread my meaning I don't Have any great desire to overclock my ATP. Maybe later, for now I AM interested in the Kernel Module for Background I/O. Cranking up the processor does diddly when the Prime lags, and freezes every so often, especially under any type of background disk activity. 1.4 single. 1.3 ghz Multicore speeds are more than sufficient. People that overclock do so often for the wrong reasons. Why should I be cranking along at 1.6 ghz to browse a news article? If I had ultimate control I would like to control WHEN the additional core kick in, not how fast they tick along, doing a lot of nothing. I did miss your discovery that with ICS, it shows these rates. Right now I would give my right arm to know how, if you do all your posting with the prime, you deal with the cursor misbehavior in text boxes, like when it jumps to the first character position in the box, or insists on jumping to a spot and only the arrow keys will override that. And why is it "mines" do you have multiple Primes?
Edit: Also, I wasn't stating that "11, 089" was a enormous score, if you read I was stating that it was a BETTER score than my returned Prime, but not what I would expect if overclocked. I'm glad your numbers are so impressive. Maybe someday MY Prime will have a Antutu score of over 13,000! That's really fast! And that helps exactly how?
Click to expand...
Click to collapse
You are correct. Stock speeds are more than sufficient for everyday usage. Overclock just makes everything even more faster n snappier. Web pages load up faster, apps open up faster, etc.. Its not for everyone. But for me its so easy to do and has no ill effects on my tablet. I'm like why not harness the extra power. Its in the kernel anyways and newer tegra3 tablets down the line will have exact same chip but the 1.6Ghz speeds enabled Stock. I do find myself going back to stock speeds alot because I truly appreciate how fast this device already is stock and ill get better battery life on stock. I do get pretty good battery life also on 1.6Ghz overclock.
Also, yes, I DO ALL MY POSTINGs, from the prime. I don't experience the major slowdowns or lags some seem to experience. Mostly only occurred sporadically in stock browser. I used ATP settings to change scheduler from noop(stock) to cfq. It seemed to help for a while but then came across an issue before, where I never had before, where the whole stock browser seemed to just freeze up or stop loading. Before it might freeze n then prompt come up saying to wait or close. After the switch it didn't do any of this. So i switched back to noop I/o scheduler n everything has been running great for me. I mainly just use the ATP tweaks app now for quick access to overclocking. Less steps needed vs. Having to go into terminal emulator and pulling up vipercontrol. With ATP all I do is open up the app n press Turbo2 n I'm overclocked. I did try out the deadline I/o scheduler also but didn't seem to make much of a difference. Actually acted kinda funny at times so i switched back to Noop. As Noop is the best out of all of them. Its just some people switch to other schedulers based on their needs for prime to PC file transfers n such. So its really a preference thing and what you experience with your personal usage and benefit the change makes for you.
AS far as bench scores go, I just said that cuz you mentioned yours n wanted to show another form of proof you weren't overclocked. Now for the cursor jumping around, I know what you mean..lol. but I use thumb keyboard, split mode, n very use to using the arrow keys to correct anything. Yeah the cursor does jump around at times but it still goes where you want most of the time through touching where u want it. Plus copying n pasting is very easy for me now that o got the technique down packed. So all of this is working pretty well for me and not a hassle at all as majority of my post count had been made with my prime alone. Before I got the prime, I was posting from my Ipad n Atrix4g. I can type very fast using thumb keyboard. Love it. Also, I only have one prime. The "mines" must've been a typo.
---------- Post added at 11:52 PM ---------- Previous post was at 11:50 PM ----------
rand4ll said:
Also, since the processor has those steps built in it technically isn't overclocking to enable the 1.6GHz step. You are only overclocking when you go above that.
Click to expand...
Click to collapse
Yeah yeah..lmfao but we can't enable it stock. So its still "Technically" considered overclocked since it is higher than allowed out the box. Only if you running a "true" overclock using vipercontrol mod or ATP tweaks.
It's all good.
demandarin said:
You are correct. Stock speeds are more than sufficient for everyday usage. Overclock just makes everything even more faster n snappier. Web pages load up faster, apps open up faster, etc.. Its not for everyone. But for me its so easy to do and has no ill effects on my tablet. I'm like why not harness the extra power. Its in the kernel anyways and newer tegra3 tablets down the line will have exact same chip but the 1.6Ghz speeds enabled Stock. I do find myself going back to stock speeds alot because I truly appreciate how fast this device already is stock and ill get better battery life on stock. I do get pretty good battery life also on 1.6Ghz overclock.
Also, yes, I DO ALL MY POSTINGs, from the prime. I don't experience the major slowdowns or lags some seem to experience. Mostly only occurred sporadically in stock browser. I used ATP settings to change scheduler from noop(stock) to cfq. It seemed to help for a while but then came across an issue before, where I never had before, where the whole stock browser seemed to just freeze up or stop loading. Before it might freeze n then prompt come up saying to wait or close. After the switch it didn't do any of this. So i switched back to noop I/o scheduler n everything has been running great for me. I mainly just use the ATP tweaks app now for quick access to overclocking. Less steps needed vs. Having to go into terminal emulator and pulling up vipercontrol. With ATP all I do is open up the app n press Turbo2 n I'm overclocked. I did try out the deadline I/o scheduler also but didn't seem to make much of a difference. Actually acted kinda funny at times so i switched back to Noop. As Noop is the best out of all of them. Its just some people switch to other schedulers based on their needs for prime to PC file transfers n such. So its really a preference thing and what you experience with your personal usage and benefit the change makes for you.
AS far as bench scores go, I just said that cuz you mentioned yours n wanted to show another form of proof you weren't overclocked. Now for the cursor jumping around, I know what you mean..lol. but I use thumb keyboard, split mode, n very use to using the arrow keys to correct anything. Yeah the cursor does jump around at times but it still goes where you want most of the time through touching where u want it. Plus copying n pasting is very easy for me now that o got the technique down packed. So all of this is working pretty well for me and not a hassle at all as majority of my post count had been made with my prime alone. Before I got the prime, I was posting from my Ipad n Atrix4g. I can type very fast using thumb keyboard. Love it. Also, I only have one prime. The "mines" must've been a typo.
---------- Post added at 11:52 PM ---------- Previous post was at 11:50 PM ----------
Yeah yeah..lmfao but we can't enable it stock. So its still "Technically" considered overclocked since it is higher than allowed out the box. Only if you running a "true" overclock using vipercontrol mod or ATP tweaks.
Click to expand...
Click to collapse
I am glad that I am not alone with the cursor thing. A bit distracting, but for the most part I use the Hardware Keyboard in the dock when doing any serious typing. Like with my TF101 I like that the dock acts as a "stand" and a cover/case. and at home I tend to do a lot of wen/newsreader browsing, and posting, as you know.
I know you mentioned that battery life seems decent when running at full clock speed (okay, we know it's technically not "overclocked") so I say "full speed to avoid being corrected, LOL! I am curious about battery performance with it running at a true 1.6, and before you answer that it is not bad, can you say for certain, as in have you tested the discharge times with the Turbo2 enabled full time? Or, if you can at least say that it's not too bad, what would you peg the loss to be? 10% or more? I agree that if I had an app to easily toggle it on/off like the build in app that prioritizes processors, I would like to use it at times.. The built in one I think does the following:
Power Saving: Runs all Cores at reduced speed, I think its 600 MHz, 700 MHz when three are active, and 1 GHz when one or two are active
in "Balanced mode" - the cores are capped at 1.2 GHz
and in Performance Mode (used to be normal mod, just to keep it sounding exciting, they changed it to "Performance with ICS, LOL!) a single core runs at 1.4, or all 4 cores can run at full clip of 1.3
Not sure where they came up with these choices, but I will bet it was only after Nvidia ran them every which way, and came to these numbers as the best compromise of power and battery life. I think the Tegra 3 SOC also controls the video brightness and depth on the fly as well. All told a nice implementation. I still see lags occasionally, and games like Riptide GP freeze in a "Stutter Frame" kind of lock, till I exit to home screen, and resume the game, and it's good again.
Anyone else get that?
SmartAs$Phone said:
I am glad that I am not alone with the cursor thing. A bit distracting, but for the most part I use the Hardware Keyboard in the dock when doing any serious typing. Like with my TF101 I like that the dock acts as a "stand" and a cover/case. and at home I tend to do a lot of wen/newsreader browsing, and posting, as you know.
I know you mentioned that battery life seems decent when running at full clock speed (okay, we know it's technically not "overclocked") so I say "full speed to avoid being corrected, LOL! I am curious about battery performance with it running at a true 1.6, and before you answer that it is not bad, can you say for certain, as in have you tested the discharge times with the Turbo2 enabled full time? Or, if you can at least say that it's not too bad, what would you peg the loss to be? 10% or more? I agree that if I had an app to easily toggle it on/off like the build in app that prioritizes processors, I would like to use it at times.. The built in one I think does the following:
Power Saving: Runs all Cores at reduced speed, I think its 600 MHz, 700 MHz when three are active, and 1 GHz when one or two are active
in "Balanced mode" - the cores are capped at 1.2 GHz
and in Performance Mode (used to be normal mod, just to keep it sounding exciting, they changed it to "Performance with ICS, LOL!) a single core runs at 1.4, or all 4 cores can run at full clip of 1.3
Not sure where they came up with these choices, but I will bet it was only after Nvidia ran them every which way, and came to these numbers as the best compromise of power and battery life. I think the Tegra 3 SOC also controls the video brightness and depth on the fly as well. All told a nice implementation. I still see lags occasionally, and games like Riptide GP freeze in a "Stutter Frame" kind of lock, till I exit to home screen, and resume the game, and it's good again.
Anyone else get that?
Click to expand...
Click to collapse
See I don't even have a dock n typed all that with no problem. Thumb keyboard makes typing so easy n fast on the prime. All I use is 2 thumbs to type n can do it very fast with the split keyboard mode.
AS for battery life if you ever ran the built in performance mode full time, then you will know it drains the fastest out of all modes because its running the higher speeds. Now with 1.6Ghz it drains about the same or a lil faster than performance mode. I've noticed lately I've been getting battery life even better than performance mode on my overclock. For the quick implementation of it that's easy. It can't get no easier then this. Check this out..lol. if you rooted, all you have to do is go into prime developement section. Go to ATP tweaks thread. Download and install ATP app into prime. Then open it. Allow superuser permissions. Then just press the Turbo2 tab n bam! Now you St 1.6Ghz overclock. The real one. You can use CPU spy to confirm that 1.6ghz speed is enabled.
hen if you want to disable it, just reboot tablet. Then whenever u want. All u have to do is open up that app n press turbo2 tab. There's a turbo1 also n that's for 1.5Ghz.. There is a step to do a more hardcore overclock to where you can run ALL 4 CORES @1.6GHZ at the same time all the time. Of course this burns up the battery the fastest. I doubt u ready for that yet though... lmfao just take it slow..lol use the regular overclocks. Get ATP tweaks app in developement section.
For the games, I don't have no stutters or freezes even on stock speeds.
I'm curious about the state of fine tuned overclocking on the note.
Of course, we have Da G's OC Kernel, and a couple roms.
But i've never been so unlucky when it comes to receiving some free performance via overclocking.
I've been blessed with a solid piece of silicon on my transformer and my desktop setups.
I find that even at 1.72ghz, i FC every 20-25 minutes or so. Just enough to make me want to avoid OCing it.
At 1.78 it's worse, and although i've heard that the majority of users have no issues at 1.83 ghz, i crash hard at that settings--within a quarter-minute of applying it.
I've tried different governors, and had more luck with smartassv2. I have a feeling that i just received a mediocre piece of silicon.
I only have a couple options-- i've had other issues with my note--namely the buttons; soft keys, as well as hard, and display brightness--unfortunately im just past my 30 days to return the note, so i'd have to replace it through Black-Tie Protection....i have no idea how this even works.
The other option is to bump up the voltages, but in SetCPU, there are no options, and CPU Master is the same. The only app I've found that even lists voltage options is System Tuner Pro, and while i'm not fond of the UI, i could deal with it.
Edit:
It turns out, bumping up the voltages @ 1.83ghz to 1375mV seems like it buys me a few seconds more before i crash and burn, but this could be a placebo affect.
So, the pupose of this thread is two-fold:
A: Find out if voltage adjustment is a function of the app, and a logic board component.
B: Find out if voltage adjustment must be supported at the kenel and/or ROM level in order to function, and the settings i'm changing are just dummy settings without said support.
2.
A: Find out how much variation on overclocking yield is standard.
B: Poll and share the results.
it is non sense having a poll for that because although we have the same device, still they are not the same if u know what i mean. stop overclocking if it crashes unless you want your phone to die, or just get it replaced with another one and see if it works fine. 1 question, why you need to oc?
This thread is for discussing overclocking methods, settings, support, and to answer my questions about the above listed specificity.
The poll is meant to survey our (us @ the LTE Galaxy Note forums on XDA) sample (albeit, a small one) to find out where our numbers fall. Unless we have a volunteer to read the thread every day, and report back on how many users are stable @ the clock speeds listed above, a poll is the most efficient, concise, objective, and standardized method to gather such information via forum.
Us non-cyborgs (organic humans) just don't do well when it comes to looking at a ton of numbers and extrapolating 411 from 'em over, and over, and over again.
*********
I've read on several ROM forums that only certain apps utilize or dual cores. go to sys/devices/system/cpu/cpu1 there is a file there. When using one of the above said apps it populated cpu1 with freq folders etc, changes that one file from 0 to 1 enabling it. without one if these apps there is no freq tables for cpu1.
****my question: using Linux and cpu i ran speed tests. Over 70 tests in total. There is zero performance difference in using one app versus another versus cm performance cpu menu. I understand how it looks like two cores are only utilized from certain apps looking at the folders. However it does not change performance at all. Tests show same speed any way to control cpu. Also feels the same. Is there really a difference our is it monkey say????
Also in my tests i found using "VR" versus sio or noob or cfq to be the fastest. I didn't feel a difference however changing i/o setting.
Sent from my SGH-I717 using xda premium
Their are claims that Intel’s internal handset testing has shown multi-core implementations running slower than single core, however they did not cite any particular chip. If you take a look a lot of handsets on the market, when you turn on the second core or having the second core there [on die], the [current] leakage is high enough and their power threshold is low enough because of the size of the case that it isn’t entirely clear you get much of a benefit to turning the second core on. In some of the use cases they cited, having a second core is actually a detriment, because of the way some of the software engineers have not implemented their thread scheduling properly.......
That being said, one could argue the concept that a single core chip, running a slight overclock, would produce a far better result, than a dual core application. But again, thread scheduling detracts from any governor efforts anyway...IMHO....g
Hum. I would have to agree then that in our case and in my tests dual core doesn't help nor hinder performance results but does appear to reduce battery life. Now these are my tests using two different programs to test performance and using combo of setcpu/system pro/Cm10 performance built in/Tasker to control cpu. I have done enough testing to know that on cm10 roms dual core, or so the sys files indicate, is of zero performance upgrade and appears to drain battery faster.
Sent from my SGH-I717 using xda premium
Yes ...I agree with your findings.
I suppose it's safe too say then, when using the AOSP rom source, within it's normal configuration, that unless development is done beyond the current schedules, the stated performance is well ....overstated ??
Of course , CM is in a constant state of change, and I suppose that after they are finished with the functional repairs, they may focus more on the kernel.
I'd be very interested to see your same tests against another kernel, say flappjaxxx latest JB build.
I do know that he, and several other developers have made some great improvements to the source kernels, and although there will likely always be bugs present, after running my own evaluation of them, the governors are functional and do make at least a perceived difference.
But as you stated, albeit at the cost of battery life.
I choose not to overclock, as I feel that the marginal reward , as proven by your testing , and by testing from several reputable sources, is simply not worth the risk ...g
I agree Greg, i will test other kernels... Samsung ROM is probably the only one i won't test... I also don't overclock, i do under clock at work and screen off using Tasker for battery life. That does help greatly. I'll post back after testing different kernels tonight.
Sent from my SGH-I717 using xda premium
troyolson92 said:
I agree Greg, i will test other kernels... Samsung ROM is probably the only one i won't test... I also don't overclock, i do under clock at work and screen off using Tasker for battery life. That does help greatly. I'll post back after testing different kernels tonight.
Sent from my SGH-I717 using xda premium
Click to expand...
Click to collapse
Excellent....
And I suppose, since this is the Premier development site, that it would be of great value to the community if you could perhaps publish your results here ?
These aspects of the android OS have been of great interest to me for some time.
Without doubt, many other users would enjoy this information as well in forming their decision regarding roms, kernels etcetera.
Thanks to you, for your inspiring thread. I look forward to the forthcoming information ....g
Ok with out posting tons of pics i tested all available kernels (new). Results were the same. No real difference in single core versus dual core...
The following pics show how to know whether the second core is online or not and my results and how i tested this time around... I was more through the first time but results the same.
Sent from my SGH-I717 using xda premium
troyolson92 said:
Ok with out posting tons of pics i tested all available kernels (new). Results were the same. No real difference in single core versus dual core...
The following pics show how to know whether the second core is online or not and my results and how i tested this time around... I was more through the first time but results the same.
Sent from my SGH-I717 using xda premium
Click to expand...
Click to collapse
I am posting pictures for first time hope this turns out.
What do you use to disable the second core? Read this with some interest. Would like to try this with ics Rom. With oc'ing fRom 1.56 to 1.72 i see a consistent jump of 300-400 in my antutu scores. Currently on flapjaxx ics b4.
I know it is just a score, but is your score indicative of the cm builds? It just seems really low.
Here is my 'stock 1.56 speed' with ondemand governor. Want to a get a single core sample.to compare with it.
How interesting ....
I can say that both of your posted results lead toward our initial assumptions, that indeed we are seeing a consistent draw against the systems cores with little or no improvement upon activation of the second core.
Some Time ago, shortly after my note arrived, I began some simple tests with low speed dual core activation. My thought process was simply this.
Slow speed dual core operation (both cores running in the 650mhz range ) would ideally produce a faster process response.
My initial results were favorable, as I had a noticeably quicker device during screen transitions, and even in several multitasking functions.
I even went so far as to create a small script to handle this function for me. I'm no developer, and ultimately I didn't possess the programming skills I needed to complete and implement my script into an actual, flash worthy modification. And based on what we are seeing here , the results provided would indicate that my attempt is flawed due to chip current leakage, if the cores are allowed to ramp to high, and perhaps even the use of improper source schedule interference.
I'm so busy these days, I simply haven't time to explore the low speed theory further at this point.
But perhaps with your test bench already set, a simple test using my concept could be carried out??
As we know, CPU [current] thresholds are plagued by voltage bleeding at maximum CPU frequencies, but the thought has just occurred to me that [current ] bleeding is highly controllable when the CPU is driven at lower voltage inputs. And too combine a reduced frequency with reduced voltage over a multiple core platform, could, or should balance the loss and equal the output levels.
Are you up for another test ??
If so ....I suggest the following parameters.
Core "0" at 600/700 MHz
Core "1" at 600/700 MHz
Governor at "interactive "
Voltage at "-24Mv"
Then we'll see if the theory holds water.
P.S. thanks gents, I'm enjoying the heck out of this thread ......g
Mad383max, look at your folders from my pics to tell if two cores are running. Typically on after market roms one core is running until you enable the second from other software like from my pics.
Will test at lunch. I like this lower voltage idea. If i were a betting man i would guess with speeds you proposed and two cores i would guess similar to higher results. Let's see....
Sent from my SGH-I717 using xda premium
troyolson92 said:
Mad383max, look at your folders from my pics to tell if two cores are running. Typically on after market roms one core is running until you enable the second from other software like from my pics.
Will test at lunch. I like this lower voltage idea. If i were a betting man i would guess with speeds you proposed and two cores i would guess similar to higher results. Let's see....
Sent from my SGH-I717 using xda premium
Click to expand...
Click to collapse
Agreed......
I'm excited to see the results....and thank you !!...g
I have to reflash ROM so pics might be a little awhile. I messed up some things and somehow lost my Google account. reflashing gapps and ROM didn't fix it.
Anyway results were 2600 something at 700 both cores underclocked 25... Slightly more than half of normal speed at slightly less than half clock speed... For kicks i tried 1.5 clock speed undervolted 75 (most my phone will go without lockups) and got 5k results. Best yet.
You are on to something. Less voltage = more speed. I now need to try single core undervolted. Give me couple hours for pics etc.. Got to get phone working with Google again and spend time with wife. She hates me on the phone.
Sent from my SAMSUNG-SGH-I717 using xda premium
No worries Troy. ...
Take all the time you need.....
I do appreciate the excellent testing you have undertaken. I know that the results are going to benefit the community.
And i am highly intrigued by your first run under the parameter set you've chosen...
It's leading down the exact path that i suspected. ..
I'll talk with you soon. ...g
A few additional items that I have failed to consider during my testing, could weigh heavily on our testing results and should be considered during testing.
They are, battery power levels, charger connection and type....(wall/PC), and rom power save levels.
I do know that the android OS will adjust itself during varying power levels, much like our setting the CPU to UC/UV settings, only on a much smaller scale.
I feel its important that we are able to control the input levels in the following way...
Battery to full charge, with no charger connection, and if the cable is needed we use a non powered port. Next would be controlling the rom power settings if the rom contains them, as found in most GB and ICS builds.
If these baselines are met, we should be able to greater rely on the mark scores we are seeing. These variables could explain why we continue to see so many peaks and valleys in scores when two users share the same builds, on like devices.....(speculation)..
Additionally, are we able to control the background processes to the extent, they will remain constant for testing?
Sorry for the rant.....Im just concerned about the ability to quantify our findings once testing is complete.
Ive started some tests on my end as well, and certainly do not want to give you the impression that I expect you to do all of the work.
After all, you did ask first....lol and I feel like Im dumping this effort into your lap.
And please forgive my pathetic punctuation in this post, as my keyboard of choice decided to fail tonight....g
Battery does effect performance greatly.... Also noticed none of the apps to test are very repeatable. Fluctuation seemed to be about 100.
Having issues up loading pics from phone, I'm away from laptop for a few days.
In the end i found -12 v single core to provide the best battery and performance that was equal to dual core. I tried over under voting many differences.... over voting did nothing, under voting a little made small preformance improvements. I believe some of fluctuations are related to app, battery, etc.... In the end it's too say dual core has no speed improvement. I would be cool to test an app that it's specifically for dual core. I am better off without the second core speed is same anyway, and battery is much better. There is definitely voltage leakage..
Let me know what y'all find in your tests....
Sent from my SAMSUNG-SGH-I717 using xda premium
Outstanding !!
I appreciate the hard work !!
So it seems we are better off using the note running a single core and about 12mv under volt.
And I'm of the belief that our second core is rather pointless...unless it can be proven that the second core is absolutely needed to perform a function.
And so far, I haven't found anything I use that requires activation of the second core.
I'll continue my tests, but the way it looks now, Intel is right, and Samsung pushed a dual core chip to this device for nothing more than a market share increase. As it is quite clear that the device does "not " need it to function well, and at a Very respectable speed.
Now we have a quad core version, and I highly question the motivation behind that move, beyond marketing as well.
These statements may offend some, and folks will certainly disagree, but if you want a great running device and great battery life, you need a single core chip ...IMHO ....g
Agreed Greg. Someone will get upset when they do thirty own tests and realize what we see, and what you said, good marketing by Samsung. Numbers don't lie and i did tests as controlled as possible. Even my battery shows in the picks... A true second useful core would have easily bested the single core results. Plus undervolting tella the bigger story...
I must say though. It had been very useful.. My battery life is so much better now!!!
For me the only true performance gain had been from v6 supercharger.
Sent from my SAMSUNG-SGH-I717 using xda premium
Fyi: same exact results using cm9 versus cm10. Neither ROM benchmarks faster than the other as of 9/16 cm9 and 9/15 cm10 builds. Dual core zero performance upgrade.
Tried quadrant again and result very up to 20% back to back so that app is useless to me.
Can someone try a Samsung based ROM. I'm curious add to a difference in roms. just use antutu benchmark and set cpu however you wish to whatever you wish just report cpu clock speed, type of test, and results
Sent from my SAMSUNG-SGH-I717 using xda premium
Out of town this week Troy, but i'm gonna bump it for ya...g
Hello I own the Samsung Vibrant for two years now and even though I was a bit reluctant to overclock the phone at first as new phones were coming out in the market and its (Vibrant's) performance deficit was becoming all the more significant (in comparison to newer phones) I "succumbed to the temptation". At first by a little margin (no more than 20% overclock) but eventually -as I was seeing my phone to be capable for it- for even greater ones. There was a time that I was using my phone at 50% over-the-stock clocks.... those were the days
Eventually -it seemed- as if it somehow starting becoming less and less capable holding the clocks so I started lowering my clock thresholds eventually killing the overclock altogether. Mind you the grand total of the time(s) that I had my phone overclocked (up until then) was not that great...
But then ICS came out with all its fancy tools and the "temptation" overcame me again and as if from a miracle I was able to maintain 50% overclocks like the good ole days (1512Mhz to be exact). To be sure -that time around- that that is a stable clock I devised a slew of different test from extensive software decoding, to 3D and CPU rendering. My phone was rock solid. To address the battery issue I bought an extended battery and all was well in "Vibrant-Ville"...
To my dismay though even though my phone seemed rock solid I seemingly starting losing my overclocking capacity (once again) as I migrated into Jelly Bean, so I said to myself "oh no, no, I'm not going through this again, I'd choose a moderate overclock and I'll leave at that". So I disabled Live-OC, custom voltages, hell even deleted NSTools and used the standard 1.2GHz setting, my battery was better, my phone was rock solid once again and thanks to jelly bean my phone was still fast enough...
Two days ago -though- the ghosts of the past reared their ugly head once again, out of the blue my phone lost its stability. Anytime I was trying to do anything remotely complex and it would reboot (BTW I'm using Helly-Bean right now, using the "Smooth" setting, Smartass governor @ 1.2ghz, pretty standard stuff).
I love this phone but I feel it's nearing its death-bed, what's your opinion guys?
I'll prolly remove the oc altogether but I fear it won't be enough, I fear that instability would start encroaching the 1ghz setting as well one of the days and then it would be game over. I want to avoid this fate at all costs, so anything you could recommend I would try, even changing my rom.
Also to those who used overclocks in the long term what was your own experience?
Thanks for your attention
No response(s)?
Sorry for the bump but I take it none of you guys ever have/had any of the problems I'm describing. Hmm, that means that I was unlucky with my piece of hardware it seems... pity :/
More than likely an aging chip is the case. Personally my phone runs smooth at 1GHz, so I don't see the need to unnecessarily overwork the CPU. After reading your original post, one line stuck out to me in particular. You mentioned that you ran the CPU at 150% for a time, and to me that sets off a red flag. Setting the CPU at 1.5GHz is risky and can cause some major wear on the CPU. Not to say I've never overclocked that high, but I usually only set it that high when playing a high graphics game. Even then, 1.5GHz is not recommended if you wish to use your device long-term. Even 1.4GHz is considerably pushing it. Although our devices can handle it, eventually, they're going to tire out. Now some phones may be able to last longer than others, it depends on the amount of iron in the sand used to make the silicon processors or other minuscule things could play a role. Essentially, it's random. No two chips will be exactly identical nor run exactly the same. So in your case, that may be the case. Perhaps your device really is nearing the its end. Considering that your phone was made to last only a few years at stock speeds, you should still be pleased with how long it's lasted. However, it is understandable if you're upset with this. The only thing I can suggest is to not overclock anymore and to try and keep its temperature low. Perhaps try undervolting? But if you want your phone to last, don't overclock (if your phone's processor is already starting to fail at 1.2GHz, when it used to run rock solid at 1.4 or 1.5GHz, then you definitely need to stop overclocking entirely). More than likely you won't hear other Vibrant users discuss similar problems because they've already moved on to new devices, before the long-term effects of high overclocking began to take its toll. But if you do a little research, you'll find other users on other devices having similar problems to what you are having.
Wish you the best in your efforts, and hopefully you'll get a year or two more out of the device... Hopefully someone will come forward with a better recommendation/solution to your problem. Since I pretty much stated what you probably already knew.
I'm not for overclocking, nor have i overclocked my vibrant.
With that being said, i have never had any performance issues, and I'm having difficulty recalling any issues with stability either..
I hope you treat your new phone with more respect..
I'm sure it will live you much longer for it.
Sent from my amazingly stable SGH-T959 using SlimICS