Sorry being a new member I could not reply directly to this thread under developers but I wanted to let people know that this rom should be avoided. The default clockspeed is downgraded from 1.5ghz to 1.2ghz with this and even when overlocked back to 1.5ghz it's still not as fast as before. Linpack hardly even hits 150 now when before was around 200. Quardrant scores is also very low now, the memory and IO scores were significantly lower than before.
As for those who are having the wifi issue, i discovered that the problems started happening after the one click root. Right before I rooted this new rom i was able to connect to my wifi just fine, after the root it started having problems connecting.
gtung99 said:
Sorry being a new member I could not reply directly to this thread under developers but I wanted to let people know that this rom should be avoided. The default clockspeed is downgraded from 1.5ghz to 1.2ghz with this and even when overlocked back to 1.5ghz it's still not as fast as before. Linpack hardly even hits 150 now when before was around 200. Quardrant scores is also very low now, the memory and IO scores were significantly lower than before.
As for those who are having the wifi issue, i discovered that the problems started happening after the one click root. Right before I rooted this new rom i was able to connect to my wifi just fine, after the root it started having problems connecting.
Click to expand...
Click to collapse
What proof do you have of this? I don't see any difference in performance. I guess I'll just wait for the next update.
Sent from my HTC One X using Tapatalk 2
gtung99 said:
Sorry being a new member I could not reply directly to this thread under developers but I wanted to let people know that this rom should be avoided. The default clockspeed is downgraded from 1.5ghz to 1.2ghz with this and even when overlocked back to 1.5ghz it's still not as fast as before. Linpack hardly even hits 150 now when before was around 200. Quardrant scores is also very low now, the memory and IO scores were significantly lower than before.
As for those who are having the wifi issue, i discovered that the problems started happening after the one click root. Right before I rooted this new rom i was able to connect to my wifi just fine, after the root it started having problems connecting.
Click to expand...
Click to collapse
Wowsers! That's good to know. I haven't updated yet as I'm on Rogers, but I'll keep that in mind when a Rogers version comes around.
As for the WiFi issue, I've had it the whole time. I went 9 days before rooting, and it's been maybe 15 days since I rooted. It existed pre- and post-root for me.
mobilehavoc said:
What proof do you have of this? I don't see any difference in performance. I guess I'll just wait for the next update.
Sent from my HTC One X using Tapatalk 2
Click to expand...
Click to collapse
Mine seems to be running at 1.5ghz fine. I'm on the new version. I smell FUD.
Sent from my HTC One X using Tapatalk 2
same as above, no issues here.
Also have the update no issues
Sent from my HTC One X using Tapatalk 2
I went from the full detox to 1.82 and after start up i ran both quadrant and antutu benchmarks. I noticed that quadrant score was only 4k when it used to be 4.5k. antutu was also lower and thats when I noticed the clock speed being listed at 1243 mhz (something around there). I downloaded the antutu cpu master free and it allowed me to move the slider back up to 1512 mhz.
Only sharing what I expierenced, now i'm trying to go back to 1.73 and having trouble...seems like it doesn't want me to move back down.
gtung99 said:
Sorry being a new member I could not reply directly to this thread under developers but I wanted to let people know that this rom should be avoided. The default clockspeed is downgraded from 1.5ghz to 1.2ghz with this and even when overlocked back to 1.5ghz it's still not as fast as before. Linpack hardly even hits 150 now when before was around 200. Quardrant scores is also very low now, the memory and IO scores were significantly lower than before.
As for those who are having the wifi issue, i discovered that the problems started happening after the one click root. Right before I rooted this new rom i was able to connect to my wifi just fine, after the root it started having problems connecting.
Click to expand...
Click to collapse
Ok, im curious, what program is reporting to you that your clockspeed is 1.2? Im not doubting what you are saying....at least not completely. I ask because when i was researching the phone before it was released on ATT, i was reading reviews and reports of people benchmarking the ATT demo phones and how the clock speed was 1.2 compared to the 1.5 of the tegra 3. So, im curious if its maybe just that the actual app you are using is reporting it wrong OR, if this is even possible, that maybe there is a different kernel with the clock set differently that somehow slipped through the cracks.
I have done the update already, and all my benchmarks are almost identical to what they were before and my clock speed is still 1512 as it was before.
As far as the wifi issue, most people were reporting that issue before root was even possible on this phone so to point there as being the culprit cant be right.
cloudraker said:
Ok, im curious, what program is reporting to you that your clockspeed is 1.2? Im not doubting what you are saying....at least not completely. I ask because when i was researching the phone before it was released on ATT, i was reading reviews and reports of people benchmarking the ATT demo phones and how the clock speed was 1.2 compared to the 1.5 of the tegra 3. So, im curious if its maybe just that the actual app you are using is reporting it wrong OR, if this is even possible, that maybe there is a different kernel with the clock set differently that somehow slipped through the cracks.
I have done the update already, and all my benchmarks are almost identical to what they were before and my clock speed is still 1512 as it was before.
As far as the wifi issue, most people were reporting that issue before root was even possible on this phone so to point there as being the culprit cant be right.
Click to expand...
Click to collapse
Antutu benchmark listed it at 1.2ghz. Previously it was at 1.5ghz on 1.73. I was stupid and tried to run full detox after the upgrade and root and got some kind of error saying memory full. Now the phone is soft bricked. I just tried the stock 1.73 RUU and its giving me a boot 140 error saying bootloader mismatch.
Any ideas?
gtung99 said:
Antutu benchmark listed it at 1.2ghz. Previously it was at 1.5ghz on 1.73. I was stupid and tried to run full detox after the upgrade and root and got some kind of error saying memory full. Now the phone is soft bricked. I just tried the stock 1.73 RUU and its giving me a boot 140 error saying bootloader mismatch.
Any ideas?
Click to expand...
Click to collapse
Im guessing that like the only other HTC phone ive owned, downgrading wont happen without s-off. So the only thing i can suggest is to instead try going back to 1.82 and get the phone functional so at least its not a brick and if its still showing an incorrect clock speed maybe you can get an exchange.
gtung99 said:
Antutu benchmark listed it at 1.2ghz. Previously it was at 1.5ghz on 1.73. I was stupid and tried to run full detox after the upgrade and root and got some kind of error saying memory full. Now the phone is soft bricked. I just tried the stock 1.73 RUU and its giving me a boot 140 error saying bootloader mismatch.
Any ideas?
Click to expand...
Click to collapse
Yea you can't go back down.Have to wait for the official ota and see if its any different.
My phone runs much smoother with the new update...almost like a different phone. I could care less what the benchmarks say...I'm a real world guy.
Sent from my HTC One X using Tapatalk 2
I was lucking, using the 1.82 RUU again I reflashed it and now the phone is back up and running. Running antutu I see the clock speed is now defaulted to 1.5ghz again.
I really don't know what screwed up with my clockspeed before, but hopefully this will work nicely now.
1.73 here...
5,013 -- Quadrant Standard
So perhaps something is just wrong with you're phone. Also, I thought you couldn't modify your clock speed without unlocked bootloader + root/s-off or whatever. I know the basics, Just not the full technical explanation of it all. Sounds to me like you have a problem though from the beginning to have <5K of a quadrant score.
Just removed everything I dont need. De-oxed and removed bloatware + added a couple games. Cleared "multi-tasker" and used task manager [not the stock] widget to free up memory... Which made it go to 4,760. So doing all this stuff to "help" somewhat backfired. Im wondering if its the task manager widget/app always running :b Idk. Point is, I think its your phone. Even if i'm not at 1.8~.
gtung99 said:
I was lucking, using the 1.82 RUU again I reflashed it and now the phone is back up and running. Running antutu I see the clock speed is now defaulted to 1.5ghz again.
I really don't know what screwed up with my clockspeed before, but hopefully this will work nicely now.
Click to expand...
Click to collapse
good to know. and FYI, though it's not my forte, i was reading either the "Update 1.82" thread or the thread with the title named the same as the 1.82 patch (can't recall which one) and I remember someone mentioning that to roll back to 1.72 after upgrading, you need to edit a certain .apk file, which, if done improperly, will totally brick the device. glad you were able to get 1.82 to run properly. I've decided to wait for the full OTA from ATT since my wi-fi issues are generally minimal.
Scores are lower on the 1.82 but same clockspeed I'm fairly certain. Dont know why. Quadrant drops about 500 points. Still seems faster.
ThisWasATriumph said:
Scores are lower on the 1.82 but same clockspeed I'm fairly certain. Dont know why. Quadrant drops about 500 points. Still seems faster.
Click to expand...
Click to collapse
The IO score is lower now. Can't wait until Franco or someone else releases some kernels that will really make this phone rock. I had a galaxy nexus before with the stock rom but running Franco latest kernel that boosted the Quadrant score from 2200 to 3600. Mostly it was due to enhancements that dramaticlly increased memory and IO performance.
I installed the leaked update and my wifi still doesn't work right. It is extremely slow and crashes my entire network and brings it to its knees. Wifi will not work on a single device when my one x is connected to my wifi network. Ideas? Has anyone else experience this?
I hadn't thought of this being the cause but I have noticed that my wifi at home, specially when watching netflix is way slow. I always have my wifi on my HOX turned on when at home. I'm on 1.82 and running Clean ROM 2.3. Are you saying that this could be causing my slowness on all my devices that are also hooked into my wifi at home?
Related
I have been looking for a couple of days, and I can't seem to find my answer anywhere. Sorry if this question has already been asked. Does the Tiamat Kernel come overclock already, or do you need to use an app like SetCPU?
SetCPU is needed
Thank Brenardo.
I really want to root so i can get the USB host, and SD card. I just didn't want the overclock. I was told that Tiamat was overclock from the get go.
anovinger said:
Thank Brenardo.
I really want to root so i can get the USB host, and SD card. I just didn't want the overclock. I was told that Tiamat was overclock from the get go.
Click to expand...
Click to collapse
If you do not run an overclock program, the stock max is still on the CPU.
Sent from my Xoom
Do you know what the set Max is on the tiamat kernel?
anovinger said:
Do you know what the set Max is on the tiamat kernel?
Click to expand...
Click to collapse
1ghz
Sent from my Xoom
bwcorvus said:
1ghz
Sent from my Xoom
Click to expand...
Click to collapse
even without an OC app running my CPU sometimes runs up to 1504mhz. I've tried every kernel since the first tiamat one. I have a Canadian xoom rooted with one click. I'm using tiamat 1.4.1 and the issue isn't fixed. I've read many others experiencing the same issue. I've tried using setcpu and Droid OC to limit it to 1ghz but it still hits 1504. There both uninstalled now but I'm still having spikes. Just my 2 cents not trying to hyjack your thread. But if anyone has any input as to whats happening I'd appreciate it.
Also my battery life is significantly shorter since rooting. From about 9 hours to 4 now.
Any suggestions ?
Bandit504 said:
even without an OC app running my CPU sometimes runs up to 1504mhz. I've tried every kernel since the first tiamat one. I have a Canadian xoom rooted with one click. I'm using tiamat 1.4.1 and the issue isn't fixed. I've read many others experiencing the same issue. I've tried using setcpu and Droid OC to limit it to 1ghz but it still hits 1504. There both uninstalled now but I'm still having spikes. Just my 2 cents not trying to hyjack your thread. But if anyone has any input as to whats happening I'd appreciate it.
Also my battery life is significantly shorter since rooting. From about 9 hours to 4 now.
Any suggestions ?
Click to expand...
Click to collapse
How are you seeing its over with no app? I'm not calling you a liar, just trying to get all the facts. In all test we have done, even with the setcpu oc to 1.5/1.5, we actually see the cpu running at 1 ghz after a wakeup.
Sent from my PC36100
bwcorvus said:
How are you seeing its over with no app? I'm not calling you a liar, just trying to get all the facts. In all test we have done, even with the setcpu oc to 1.5/1.5, we actually see the cpu running at 1 ghz after a wakeup.
Sent from my PC36100
Click to expand...
Click to collapse
I'm watching the temp+CPU widget to monitor what's happening. Are you suggesting its giving inaccurate readings? Setcpu at 1ghz would still show random spikes to 1504mhz. I don't have any OC tools installed right now but my widget still shows it hitting 1504 especially under load. I was thinking of returning to stock and rooting manually but it not a huge problem just strange. I was hoping the new kernel would fix it but its still happening. Is there anything I can do besides start from scratch?
Bandit504 said:
I'm watching the temp+CPU widget to monitor what's happening. Are you suggesting its giving inaccurate readings? Setcpu at 1ghz would still show random spikes to 1504mhz. I don't have any OC tools installed right now but my widget still shows it hitting 1504 especially under load. I was thinking of returning to stock and rooting manually but it not a huge problem just strange. I was hoping the new kernel would fix it but its still happening. Is there anything I can do besides start from scratch?
Click to expand...
Click to collapse
Yea setcpu is not 100% yet. Does your widget show both cpus? What we were testing was the second CPU. After you xoom goes to sleep, the second CPU is never set again by setcpu (known bug). So lets say you are running 1.0/1.5. After you xoom goes to sleep you will wake up with cpu 0 at a max of 1.5, but cpu 1 will have a max of 1.0. The info i gave earlier was said wrong. I was actually looking at the wrong line, so you may in fact be correct on the 1.5ghz random jump . Gonna stop talking now, as we are hyjacking someone else's thread .
In theory, you should not need overclocking software, as the max is set at 1ghz on both cpus. But as said above by Bandit504, this may NOT be the case .
Thanks bwcorvus and Bandit504 . So I guess to call it is safe, it would be good idea to use SetCPU, or Droid Overclock and have the maximum set to 1 ghz, to keep the proc from hitting the 1.5 ghz speed. I just hate to ruin the hardware with the overclock, and have to drop another $600 for another xoom.
Does anyone know the dangers of running the inspire OC'd on a regular basis up in the 1500000 range?
I've personally never have run into any issues, besides maybe shorter battery life.
I keep a profile in SetCPU for the temp if it gets over a certain temp. Don't have my phone with me so I couldn't tell you. But it seems fine overall.
That is one of my concerns. With the DAEMON setup on TB Fusion and some other newer roms there is no provision for a temp profile. Simply 6 files to change the settings in as far as I know.
Not sure and I have not read about possible cpu damage running it at say 1.5 or 1.7 for long perios of time. Even though it will still throttle back so to say by means of the chosen governor.
A question for someone with more experience than I!
SNadler said:
That is one of my concerns. With the DAEMON setup on TB Fusion and some other newer roms there is no provision for a temp profile. Simply 6 files to change the settings in as far as I know.
Not sure and I have not read about possible cpu damage running it at say 1.5 or 1.7 for long perios of time. Even though it will still throttle back so to say by means of the chosen governor.
A question for someone with more experience than I!
Click to expand...
Click to collapse
If you are worried about that, the DAEMON setup gets disabled if you run setcpu or something else like that.
Sent from my Desire HD using Tapatalk
gmurphy0487 said:
If you are worried about that, the DAEMON setup gets disabled if you run setcpu or something else like that.
Sent from my Desire HD using Tapatalk
Click to expand...
Click to collapse
Understood, I do want the increased performance tough.
I mostly want to know if there is any data showing that OC will do permanant damage to the device if used in that manner for extended period of time.
i dont know about overclocking phones but i assume the answer would be similiar to overclocking computers...
the answer is it does shorten the lifespan of the chip, but we are talking about minor differences over time - for example: instead of your chip lasting for 25 years it may last for 20. HOWEVER are you really going to be using your phone for that long?
So the short answer is no. This is assuming you are overclocked to a stable setting. If it is unstable then the setting is way too high/hot - you wouldnt be able to use it long enough to damage it (assuming you dont keep trying)
I ran my Inspire at 1.5x ghz for a couple of days, but I got random complete lock ups (had to pull the battery) and fc's. Slowed it back to 1.26 ghz and the issues went away.
Also, the temp never got very high, so it was not an overheating issue IMO.
Just a quick question for you guys: I recently purchased an Infuse from the marketplace here, and so far I've gotten an absolute TON of lag using the device. I've flashed Infused 1.5 and Bionix with the Infusion kernel, and so far the lag has gotten better, but it's not totally cleared up. I'm definitely not new to Android, but I haven't seen anything like this before. I know that Quadrant isn't a reliable benchmark, but I'm scoring about 1900, OCed to 1.5Ghz.
Just to give an example: I'm using desktop visualizer to add some custom icons to my screen. When I go to select an icon image, it's fine, but it freezes for about 90 seconds when a list of my apps comes up.
Anyone experience this before? And if so, how did you solve it? If this was widespread, I'd imagine there would be complaints all over here.
Which app are you using to set your overclock settings, how many clock speeds do you have enabled, are you under or over volting, and *which governor* are you running?
I have seen some similar problems here when I was using conservative governor with poor choices of clock speed. Right now Infusion 1.5.2 kernel has some issues with not liking the ondemand governor, so I reduced my number of available clock speeds so it would jump to the top more quickly while using the conservative governor.
Also, did you use either the return to stock, or the ultimate unbrick flash before you flashed your ROM? If it was a used Infuse, I would do one of the above before I start looking anywhere else, then reflash your rom/kernel of choice.
I'm using SetCPU with the OnDemand gov (400/1500), no undervolting. I have a profile set to underclock it to 300/700 on conservative when I'm charging, but that's about it.
I think I'm going to use GTG's unbrick/return to stock and root the thing myself, I figured I'd ask before I did anything drastic. My UI is a ***** to set up every time, and I hate wiping because of it.
Just a quick note, I've had some serious lag using the oc kernel... Like real world usage got worse after oc'ing
Sent from my SAMSUNG-SGH-I997 using XDA App
Although it is counter intuitive to the way governors should work I have seen less lag on Infusion 1.5.2 when I use conservative. The ondemand governor seems to be having some issues with the most recent update. If you flash back to 1.0 Infusion you get a max overclock of 1.4, but it is much more stable IMHO. Also FFC is presently broken in 1.5.2 and will hard freeze the phone (battery pull).
I'm debating flashing back to community kernel, but I am going to wait and see how long it takes my battery to drain because I am using some undervolting. You might try using conservative governor and only enable 100, 400, (800 or 1000), (1200 or 1300) and 1500. Honestly the infuse is my first smartphone, but I've tinkered with desktop hardware the last 15 years. It literally amazes me everytime I pull the battery out of this phone and feel how light it is.
I also used the desktop vis app and yes it lagged when chosing apps however it seemed to get better after three or four times but that seems to be the only place it lags for me im using the oc-uv kernal 1.0 clocked to 1.4 seems bulletproof compared to later versions im getting great speed and batt life with this kernal but i had the same lag in the same event as you
Sent from my SAMSUNG-SGH-I997 using XDA Premium App
I'm going to try bringing it back to stock and re-rooting it myself, if only because I trust myself with adb//scripts/rooting, and I'm hesitant to trust someone I don't know. Lag has gotten a lot better since switching to conservative, OCing to 1.6 and undervolting a tad, but it still lags when opening apps or scrolling through long lists. Desktop Vis is of course, still a nightmare.
Oh well, I'll report my findings tomorrow I guess. Hopefully I'll be scoring higher than the 1700 I just pulled in quadrant.
entropism said:
I'm going to try bringing it back to stock and re-rooting it myself, if only because I trust myself with adb//scripts/rooting, and I'm hesitant to trust someone I don't know. Lag has gotten a lot better since switching to conservative, OCing to 1.6 and undervolting a tad, but it still lags when opening apps or scrolling through long lists. Desktop Vis is of course, still a nightmare.
Oh well, I'll report my findings tomorrow I guess. Hopefully I'll be scoring higher than the 1700 I just pulled in quadrant.
Click to expand...
Click to collapse
Sent from my SAMSUNG-SGH-I997 using XDA App
Do you use spareparts?
usually yes, but I dont believe I installed it yet on the infuse. Why?
lag on stock also
I'm 100% stock & get lag also. Definitely in the situation you describe, when the app list comes up for adding shortcuts to any homescreen. Takes forever for that list to come up. Secondly, simply from running for a while, i have to kill all the apps using the built in task manager in order to get it to run smoothly again. It's like it never closes an app. I'm new to android, but guessing this is a problem inherit to android. Can't see how samsung or at&t could have screwed this soo badly to cause it to never close an app. Hoping memory management is better in Gingerbread.
Blario, you're new to Android, so you need to read up on how memory management works with Android. It's not SUPPOSED to kill apps, and that's not what's lagging your phone. In your case, I'd think it was more of a case of WHICH apps you were running.
yeah, the longer I have the phone the more it lags it seems
probably going to push me towards the Evo3D
If you're on stock and after a week or two your phone gets slow as hell (mine did), install a Voodoo lagfix kernel. All the current ROMs include it.
superweapons said:
If you're on stock and after a week or two your phone gets slow as hell (mine did), install a Voodoo lagfix kernel. All the current ROMs include it.
Click to expand...
Click to collapse
I did
I still have random slow downs when it gets bogged down with stuff
I'd give a left nut to have this phone with dual core
entropism said:
Blario, you're new to Android, so you need to read up on how memory management works with Android. It's not SUPPOSED to kill apps, and that's not what's lagging your phone. In your case, I'd think it was more of a case of WHICH apps you were running.
Click to expand...
Click to collapse
I don't do much. Twitter, "Web" (some mozilla stock ish), SMS, phone, Android Market app (browsing), and Maps. I've had it lag up using only those. Far less often, I use Yelp... that's about it.
Not supposed to kill apps? When I kill them it fixes the problem. Maybe it *should* be killing apps?? If its supposed to flush their state to disk... it seems to be doing a poor job at it.
I would be suspicious of your microSD card (if you have one). Do you know what class it is? Have you tried removing it and performing the same functions in which you see lag?
hydrogenman said:
I did
I still have random slow downs when it gets bogged down with stuff
I'd give a left nut to have this phone with dual core
Click to expand...
Click to collapse
I'd more readily assume the 512MB RAM is the issue. Looking forward to SGSII
SolusCado said:
I would be suspicious of your microSD card (if you have one). Do you know what class it is? Have you tried removing it and performing the same functions in which you see lag?
Click to expand...
Click to collapse
It's the stock card that came with the phone. Any way to check? The apps are installed to it... so removing it I wouldn't have the apps available anymore.
A little update: I returned back to stock and re-rooted. I installed 3E, then CWM, then threw on Infused 1.5 and Infusion, OCed to 1.6Ghz and slightly undervolted (about 25-100mv along the range) using SetCPU.
As of right now, it still lags on occasion, but not as bad as it did. Quadrant is giving me a whopping 1300 average score, with a low of 800 and a high of 1600. This is just pathetic.
I've recently tried the Quadrant Standard Benchmark and noticed that my phone's score is severely lower than that of other reviewer's benchmarks? I usually score between 960-1060. Any Idea why I'm not getting into the 1100s? Even my brother's Infuse reached 1300.
Quadrant scores necessarily don't mean squat. But just out of curiosity, what have you done to your phone? Are you running the stock shipped ROM?
Sent from my SGH-I997 using xda premium
I've just rooted it. Bricked it. Used the ultimate Unbrick for Rogers Infuse 4g. Now here I am. One thing I've thought of is space since I have lots of games but eve when I removed almost all of my downloaded Apps. The score hardly improved. I'm wondering whether for those games(mainly Gameloft) where they require a larger download to fully install, when you uninstall those games are the rest of the files from the extra download still on ur phone taking up space?
RazorWare said:
I've just rooted it. Bricked it. Used the ultimate Unbrick for Rogers Infuse 4g. Now here I am. One thing I've thought of is space since I have lots of games but eve when I removed almost all of my downloaded Apps. The score hardly improved. I'm wondering whether for those games(mainly Gameloft) where they require a larger download to fully install, when you uninstall those games are the rest of the files from the extra download still on ur phone taking up space?
Click to expand...
Click to collapse
To be honest, if you're not noticing any lag then all should be fine. I recommend running a custom ROM. pretty much all the infuse roms convert your system to ext4 which is much faster than stock. If you need help with anything don't hesitate to ask, but in the right forum
Sent from my SGH-I997 using xda premium
RazorWare said:
I've just rooted it. Bricked it. Used the ultimate Unbrick for Rogers Infuse 4g. Now here I am. One thing I've thought of is space since I have lots of games but eve when I removed almost all of my downloaded Apps. The score hardly improved. I'm wondering whether for those games(mainly Gameloft) where they require a larger download to fully install, when you uninstall those games are the rest of the files from the extra download still on ur phone taking up space?
Click to expand...
Click to collapse
Apps don't influence ur score much. These scores are based on how ur CPU, GPU and memory works, not based on how apps work.
Repeat the quadrant a couple times in a row. First run always seems to give lower values. After 1-2 runs, take average of next 2-3 and you will get the proper score.
Reboot your phone, give it some time to settle, and then run quadrant.
But like pointed above, stock ROMs give lower scores than custom mainly cos of faster file system. Plus, I enabled GPU based graphics by updating my build.xml and am getting about 1800 with my clock set at max 800.
diablo009 said:
Apps don't influence ur score much. These scores are based on how ur CPU, GPU and memory works, not based on how apps work.
Repeat the quadrant a couple times in a row. First run always seems to give lower values. After 1-2 runs, take average of next 2-3 and you will get the proper score.
Reboot your phone, give it some time to settle, and then run quadrant.
But like pointed above, stock ROMs give lower scores than custom mainly cos of faster file system. Plus, I enabled GPU based graphics by updating my build.xml and am getting about 1800 with my clock set at max 800.
Click to expand...
Click to collapse
apps running in the background can consume resources and affect the score. also rogers roms tend to score lower. it was that way on the captivate too. btw what's a build.xml? do you mean build.prop?
and to the op your score is in line with what you can expect. if you dont have any specific issues i wouldnt worry about it. quadrant is soo sensitive to atleast 2 areas (encoding/decoding media and file system reads) but not others that you can take an infuse to 4200 but it isnt gonna do too much that it didnt do before.
theROMinator said:
Quadrant scores necessarily don't mean squat. But just out of curiosity, what have you done to your phone? Are you running the stock shipped ROM?
Sent from my SGH-I997 using xda premium
Click to expand...
Click to collapse
They really don't!! Neither does Antutu or Linpack.. Gives you a different number every time LOL!! But Definitely look at some of the other roms out there! The few dev's we have left need all the support we can give them!! THANKS INFUSE DEV's!!!!
I opened this thread to help shed some light on the battery issues that keep occurring (and many ppl trying to downgrade end up bricking because of that).
I'm not sure the leak was meant for all revisions, because some have problems running it properly.
This guy made the connection, and i think he might be on to something:
moofree said:
I think there may be two different AT&T MB865's in the wild- the originally release fcc id IHDT56MV1 approved in September 2011 and the IHDT56MV2 that passed through the FCC in January 2012.
This may explain the 1.2ghz clock on your phones, cause mine is definitely still 1.0ghz.
Click to expand...
Click to collapse
You can check it if you remove battery, its on a sticker on the back.
You can check your default clock with setcpu(2.23 avaliable for free on xda), OR search for "cpu" in play store, "antutu cpu master" will show up, its free and reports same values as setcpu.
I'll start: im running V1 /default 1.2clock /no batter issues (I was bootlooping at 1.2 on GB, so i used 1125).
Please vote so we can get an idea whats happening with the clocks and why do people have battery problems !!
Well I am a V1 and 1GZ clock, NEVER over or under clocked the phone before with any of the ROMs... so, I am thinking might have something to do with it... Also no battery issues.
V1 1ghz. And I was overclocked on 2.3.6 to 1.2 battery on ics is great for me
Motorola lied and I'm still locked mb865
V1, 1.2. I was overclocked through Romulus 2.0 which was at 1130 if i'm not mistaken.
And I have AMAZING battery life with ICS. Much better than GB.
I've found something interesting, not sure if the guy is talking hot air though, source:
Actually the 4430 isn't overclocked in the RAZRs, it's running at 1.2GHz "Turbo" mode, an undocumented clock speed for 4430 chips tested at the factory to be stable at 1.2 GHz and run at normal temperatures. These chips are separated from the rest of the production run and sold at a premium with the 1.2 GHz "Turbo" identification.
Click to expand...
Click to collapse
It really isnt documented, this is from ti.com
OMAP4430 operates at up to 1 GHz
Click to expand...
Click to collapse
And the RAZR was 1.2 from day one. Considering its realease date, and the start of sampling of 4430 (ti.com says "currently sampling" as of 28 March 2011) they well had enough "Turbo certified" samples to make a phone using only those.
In short, hes story seems legit.
But why do we have two different clocks and how does the rom determine which setting its going to run on.
I dont think CPUs themselves "know" if they are certified, they are just placed in another box after the tests(being a bit vague here).
Just like some OC edition video cards; fitted with a better cooler, placed in a different retail package(with higher price).
Then again some OC video cards do get a modded bios (but not at the OEM level).
If they had a different firmware/serial numbering like desktop cpus then it would be documented and listed on the ti.com site.
But could it be that they "know" it after all? I'm not even sure these ARM SoC-s have something like a GPU bios register that tells them the voltages per states and clock rates(that they could flash while still on the test line) at all.
The reason this is interesting is that if its burned in on an individual chip level, the hw revision holds no relevance at all.
OR There could be some test after first install and it falls back to 1.0 if you get a reboot... obviously I didnt stumble into this and it wouldn't seem like a professional method from motorola at all.
Anyone running 1.0 carefully watching(and remembering, lol) the process could clear this one up though.
I'm on V1, setcpu is reading 1 ghz, I think my battery on ics seems OK, maybe drains a slight slight bit faster than before, but maybe that's my imagination!
Sent from my Motorola Droid Xyboard 10.1 with Verizon 4G LTE
V1 at 1.0. Ran overclocked on 2.3.6 Roms at 1125.
1.2 bootlooped on every rom I flashed .
And I tried them all.
ICS leak is running sweet. Only interesting thing I've seen is uninstalling stock bloat, ATT crap, through Absolute System app (which is step 3 after every flash) is it says it uninstalls but it don't.
Like ATT family map or YouTube.
Says successful uninstall. Google restore is off, so no clue. Of course stopped trying after hard brick scare.
Battery is great, wifi and data fast. Only installed spare parts to set animation and window transition to fast. Originally it popped up on slow setting. That was odd.
Hit my upgrade date last week, but for some reason ATRIX is my choice. I had the original also.
Sent from my MB865 using xda premium
dicksteele said:
V1 at 1.0. Ran overclocked on 2.3.6 Roms at 1125.
1.2 bootlooped on every rom I flashed .
And I tried them all.
ICS leak is running sweet. Only interesting thing I've seen is uninstalling stock bloat, ATT crap, through Absolute System app (which is step 3 after every flash) is it says it uninstalls but it don't.
Like ATT family map or YouTube.
Says successful uninstall. Google restore is off, so no clue. Of course stopped trying after hard brick scare.
Battery is great, wifi and data fast. Only installed spare parts to set animation and window transition to fast. Originally it popped up on slow setting. That was odd.
Hit my upgrade date last week, but for some reason ATRIX is my choice. I had the original also.
Sent from my MB865 using xda premium
Click to expand...
Click to collapse
You know with ics, the at&t bloat can just be disabled, which is probably safer than uninstalling!
Sent from my MB865 using Tapatalk
big ach said:
You know with ics, the at&t bloat can just be disabled, which is probably safer than uninstalling!
Sent from my MB865 using Tapatalk
Click to expand...
Click to collapse
Yeah I agree just get a bloat freezer app, much safer.
I had a v1 and ICS was clocked @1200 for me. I have never been that high - always got unstable around 1175 on gb - but it was smooth as butter on ics.. recovery operations were so damn quick.
Sent from my phone's mind
My phone is V1 and I used to run at 1.335 on GB. I am now clocked at 1.0 ghz by default on ICS.
jimbridgman said:
Yeah I agree just get a bloat freezer app, much safer.
Click to expand...
Click to collapse
No, I was saying that you don't even need a bloat freezer app, by default in stock ics you are able to disable (freeze) any system apps. Its a new feature in ics!
Sent from my MB865 using Tapatalk
big ach said:
No, I was saying that you don't even need a bloat freezer app, by default in stock ics you are able to disable (freeze) any system apps. Its a new feature in ics!
Sent from my MB865 using Tapatalk
Click to expand...
Click to collapse
So far, I haven't gotten a single app to show me the disable button, just force stop and uninstall.
My battery life is GARBAGE. I used to get 18 hours + on a single charge, but now I barely make it 12 hours.
V1 - 1000 Ghz - Battery Problems
Even though I didn't install the ICS leak, I wanted to chime in because I've been having battery issues for some weeks/months.
When I bought the phone the battery worked well. After the 2.3.6 update the battery lasted even longer than before. So I was happy and everything. Now a few weeks/months ago I get to the end of the night with only 20% or 10%. Sometimes it even dies! I tried everything, even replacing the battery, and nothing, still poor battery.
I think battery life is also subjective. There should be a standard as to what is good or bad. I have used my phone pretty heavily today with wifi on and im at 9 hrs and 30% remaining. This seems okay to me, but I noticed some people getting over 24 hrs on a charge so maybe half a day isn't that great.
My battery life is definitely better on ICS though. And it's also possible some of you are playing with all the fun stuff involving ICS for long periods of time which is making the battery die faster then boring GB where it stays in your pocket the whole day.
Anyway, I have a V1 and i'm at 1 ghz, ICS is noticeably faster. In GB I could run as high as 1.25ghz, and I would overclock using a script, not an overclocked ROM
I'm v1 clocked at 1.2 ics leak. I bootlooped at 1.2 on gb. At first I thought my battery wasn't right. Seemed to charge really slowly. After a couple cycles though I'm pretty happy with it. I have basically the same battery life as before.
Edit
I was using Remus on gd.
I uninstalled all the at&t bloat with no problem.
Sent from my MB865 using Tapatalk 2
[email protected], no battery issues.
Sent from my MB865 using xda app-developers app
has anyone else noticed that no one with a v2 has even voted? are we sure there is a v2? lol
where do i check my a2 versioN?
fromanbr said:
where do i check my a2 versioN?
Click to expand...
Click to collapse
under the battery look at the fcc number and compare to first post.