Related
Im averaging around 8 on the benchmark test. I was wondering what everyone else was getting. I just saw the Droid 2 review on Engaget and it scored like 14 something.
Sent from my SAMSUNG-SGH-I897 using XDA App
avg ~ 7.8 with stock/JF6/ext2 1.0
Oh, and the 14 the droid got was on Froyo.
Mine has gone down badly with this JH2 firmware update.
With the stock out of the box I was over 8 mflops, now I am in the mid 6's? I am not too sure about the cause of this if it's the firmware or if it's something else.
JH2 + EXT2 Lag Fix + OC1.2ghz....
9.87 on LInpack
2550 on quadrant
My linpack went back up to low 8.1/8.2 range consistently by removing ext2 lag fix. Just curious if anyone running a lag fix had similar issues. Just installed the 1.2 OC and hit 9.7 mflops and 1051 quadrant with no lag fix.
i just wanted to know what kind of scores you guys get with your d2g's, i havent gotten my d2g yet, should be coming in a day or two, but the highest score i heard someone get with the stock rom was 1800, which seems amazing to me.
I think 1800 is unrealisic
My milestone 2 with the same processor overclocked at 1,2Ghz gets 1590 in quadrant standard
I get 1590-1620 pretty regularly.
Ya I get about 1500 or so I think 1583 was the highest for me and this is on a rooted but stock CPU 1.2 ghz
I keep getting 1550 - 1630. The highest I got was 1680 odd..
Seems kinda low. Im on a plain D2 and just ran Quadrant with 1.2 Ghz and got 1675+ every single time
Hehe, with stagefright enabled I get 2500 on quadrant. Normally though I get about 1700:
Sent from my WICKED FAST Droid 2 Global with fission using XDA app
Rusty,
are you using a cooked ROM? Or the stock one?
PS: I am a newbie, so "stagefright enabled" just flew over my head. Whats that? I know its a new media platform in Froyo.. But is it disabled by default?
yeah, its disabled by default, its a bit buggy, well actually theres only one bug that i know of, it doesnt let you play videos you recorded with your own camera, but since i dont record videos with my phone, i felt like turning it on. it certainly helps when playing other videos as it is much better than the stock decoder.
Whoa... I ran it and I got 1580.. I ran it again immediately.. it went up to 1670.. After that I ran it consequetively 8 times and every time it was above 1670.. five times it was 1700+ highest being 1799.. Awesome..
1585 than I cleaned cache and ran 1628. Fission Rom.
don't need to run it again, the phone is smooth and fast,
enough said
couple more posts then I and post pictures.......
1250 at 800 Mhz on Fission 2.4.3 which is the speed I normally run at.
I got 1650 at 1.2 Ghz on Fission 2.4.3 right after the first one.
karthikmurs said:
Whoa... I ran it and I got 1580.. I ran it again immediately.. it went up to 1670.. After that I ran it consequetively 8 times and every time it was above 1670.. five times it was 1700+ highest being 1799.. Awesome..
Click to expand...
Click to collapse
I ran it 3 times in a row after a reboot.
1 - 1878
2 - 1939
3 - 1998
Hmmm.
Ok, sorry if this seems like a stupid question but... I have flashed/tested all of the Tiamat Kernels onto my xoom and it seems that I can only run the 1.4 Ghz Kernel with no random reboots. So I thought that if i download the higher 1.5Ghz or the 1.6Ghz and just under-clock it to 1.4Ghz that should stop it from doing random reboots, but sadly it doesnt and I still get random reboots even with Setcpu Under-clocking it to 1.4Ghz. Now is this typical or am I missing or misunderstanding something? Is there a reason why I cant use the higher Kernels and Under-clock them to 1.4Ghz and get no random reboots? I am only asking because I flashed the Riptide and under-clocked it to 1.4Ghz and it really made my xoom feel much faster and nicer in my hands and would love to keep using the Riptide Kernel.
Thanks in advance,
-Dez
I have the same issues and have been wondering the same thing.
I have similar , with 1.6 with ums
only flashed to get ums , and had a few crash/reboots for the first time since i bought my xoom about a month ago.
what i could do with is a stock speed kernal with all the bells on !
nexan21 said:
I have similar , with 1.6 with ums
only flashed to get ums , and had a few crash/reboots for the first time since i bought my xoom about a month ago.
what i could do with is a stock speed kernal with all the bells on !
Click to expand...
Click to collapse
I too have noticed this, after reading your post I tried keeping the Kernels but with no OC and left it at 1.0Ghz and it still has random reboots. So is there something in the Higher Kernels that are causing it to be unstable regardless of what Ghz you clock it to?
watch setcpu at times. It doesn't matter what you set the clock at in setcpu it will still go to the max clock the kernel allows. I am not sure if it is a bug with setcpu or if it is just the way the kernel works. If you reboot your Xoom when setcpu is at 1ghz, then go and play with the xoom after reboot for awhile. Go back into setcpu and look under the info tab. You will see that the cpu has indeed been running the higher clocks then 1ghz at times. It doesn't run those higher clocks much but it does. Which is most likely why you are getting lockups or reboots. My Xoom seems to love the 1.5ghz kernel but hates the 1.6ghz one.
Funny I was on the same boat. Started out with 1.6...reboots. went to 1.4 no problems. Tried riptide. Got app force closes. Now on 1.5...stable once again. The thing is im not even using OC on any of them
Sent from my SGH-T959 using Tapatalk
tribalb said:
Funny I was on the same boat. Started out with 1.6...reboots. went to 1.4 no problems. Tried riptide. Got app force closes. Now on 1.5...stable once again. The thing is im not even using OC on any of them
Sent from my SGH-T959 using Tapatalk
Click to expand...
Click to collapse
The oc is in the kernal i think , i dont have setcpu installed but cpu still at times peaks at the max 1.504 ghz ac ording to
"Temp+cpu"
https://market.android.com/details?id=com.sanels.tempcpuv2&feature=more_from_developer
Hi I am posting here because I can t post in the Development area yet.
So here is whats happening, I went and got the Latest CWM installed and rebooted. Then I flashed the newest Tiamat Xoom Rom 1.1 and signed in with my google account, let it download all my apps, then I restored all other missing apps + system data from Titanium and everything went a sweet as Pie. My missing apps was now there, my home screens were back to my previous layout and I was all happy as a kid can be... That is until i noticed my Xoom doing a random Reboot out of the corner of my eye. So I went into Setcpu and checked what I had OC'ed my xoom to and it was set to 1.4...Which i know is fine for my xoom. (Max I can go with mine is 1.5) So I went and clocked it to 1.2 and to my surprise about an hr later it did it again.... Mind you this is with my xoom sitting there not doing anything with no one touching it. So I decided to Flash back the 1.4.4 Tiamat Kernnel and OC'ed to 1.4 and all seems to be fine with no random reboots.
So, I would like to know if anyone else is/was having random reboots with the Tiamat Xoom Rom 1.1 w/the 1.4.5 Tiamat Kernnel?? If so what was their solution?
I did notice that with the 1.4.5 Kernnel the xoom did feel smoother. Also just some thing i noticed, in Setcpu with the 1.4.5 Kernnel there are optons to undervolt, however when I flashed back down to the 1.4.4 Kernnel that option is no longer an option in Setcpu.
Any thoughts??
No problems Here
I followed the same path you did. I installed Tiamat 1.1 yesterday, have SetCPU at 1200 interactive. Been running all day . . . very smooth, no reboots. In the past the only time I had random reboot was if I set the CPU at or above 1500. An update to setCPU came out a day or so ago. Maybe that might help.
I too am on v1.1 on 1.4.5 kernal typing this running at 1504 mghz smoothly. I been using my Xoom quite extensively since v1.1 at this clockspeed with no random reboots. My browser will occationally crash but I'm unsure if that's even related. When I first flashed the 1.1 rom on, I was running all out at 1.7 ghz but it started to generate screen artifacts and did reboot twice. Been running just fine at 1.5 tho.
Sent from my Tiamat Powered Xoom
Still No luck..
Ok, so I wiped/factory reset then re-flashed the Tiamat Xoom Rom 1.1 and I thought everything was all good as it went the day without a random reboot. Then Last night as i was laying in bed falling asleep and the xoom hooked up to the charger I notice a bright blue light.... it was the Xoom doing a random reboot.....grrrrrrr. Could it be a Setcpu issue?? Should I not set anything on boot?? As of right now, I Force Closed Setcpu and did a Cache Clear and then reopened Setcpu and had it "Auto Detect the speeds" and just Oc'ed to 1.4 and left "Set on boot" unchecked. I hope this will work, cause it seems alot smoother with the 1.4.5 Kernnel rather then the 1.4.4 Kernnel.
Just a Thought...(as I dont understand UV Kernnels), but could it have something to do with the Voltage of the 1.4.5 kernnel? Is setcpu with the 1.4.5 Kernnel you can change the Voltage of the frequencies...Should I even bother with this?
Thoughts??
I am seeing the exact same behavior.. Continual reboots all night, even if the screen is off and I am not doing anything.
It has happened 2x in the last hour while I'm sitting here at work.. Very strange. I'm uninstalling every app I installed, 1 at a time, in order to try to figure out if it is one of them. So far, WeatherBug and SetCPU are removed, I'll let you know if it helps.
vincentdeeney said:
I am seeing the exact same behavior.. Continual reboots all night, even if the screen is off and I am not doing anything.
It has happened 2x in the last hour while I'm sitting here at work.. Very strange. I'm uninstalling every app I installed, 1 at a time, in order to try to figure out if it is one of them. So far, WeatherBug and SetCPU are removed, I'll let you know if it helps.
Click to expand...
Click to collapse
Run a logcat and see what is causing the reboots...its common that some devices can't handle the overclocking....you can try flashing the stock GPU kernel and see if they go away. My device can't handle being overclocked...this is very common with any motorola device I have ever owned besides the droid 1.
dhemke17 said:
Run a logcat and see what is causing the reboots...its common that some devices can't handle the overclocking....you can try flashing the stock GPU kernel and see if they go away. My device can't handle being overclocked...this is very common with any motorola device I have ever owned besides the droid 1.
Click to expand...
Click to collapse
That is the killer.. I'm not even overclocking. Stock was absolutely fine.. even OC'ing in the past was fine, its just this 1.1 Rom that has caused this behavior.
Upside is, since removing those 2 apps, no reboots. If your not choosing to change the CPU/Volts, does SetCPU still change things in the background?
I've had the same problem. I have uninstalled Setcpu so I'll let you know if this stops the reboots.
Glad to see I'm not alone here. although I even had the problem on 1.0 rom. I'm still trying to fix it :-\
I have also been having issues with reboots. I flashed the 1.1 rom as directed and did everything exactly as I should. I think its an issue with the rom or the new kernel. I'm overclocked to 1.504ghz and always have been and have never had reboot issues until flashing the new rom. My xoom is stable up to 1.6ghz but I keep it on the 1.504ghz. But even at stock speeds and profiles to keep it running a max:216 min:216 my battery life has decreased alot it seems.
"My browser will occationally crash but I'm unsure if that's even related." I don't think it is related. I have two identical zooms ones been rooted since root was available, the other stayed stock and updated with the ota. Both are experiencing browser crashes when in the stock browser, so I'm not exactly sure what's goin on there.
Sent from my Xoom using XDA Premium App
Hwy guys I had the same problem to, here is a log I started,
One of the guys on the org thread stated that it may be a overclocked gpu problem causing reboots, which the 1.1 tiamat is oc gpu, he suggested that I try lunch pad kernel, which so far has worked without a reboot yet. You can install it on to of tiamat 1.1. Which is good cause I keep most all the benefits, but with no gpu overclocking, which is lead to be the cause of reboots.
Reboot times and events
My tablet: WIFI xoom, abd root (not one click), tiamat rom 1.1 with mod pack one.
Time and date: 7/8/11 6:45 pm cst
Currect status: standby, screen off
Cpu setting: stock 1.0 ghz max , 816 mhz min. Scaling set to interactive
Cpu app: setcpu
Time and date: 7/8/11 8:41 pm cst
Current status: just competed download of mp4, file size 205.9 meg
Cpu setting: overclocked at 1.2ghz max, 1.0 min. Scaling set to on demand
Cpu app: antutu cpu master
*updated
Time and date: 7/8/11 10:51pm cst
Current status: standby, screen off
Cpu setting: stock
Cpu app: all cpu overclocking apps uninstalled
** updated
Time and date: 7/9/11 12:11am cst
Current status: standby, screen off
Cpu setting: stock
Cpu app: all cpu overclocking apps uninstalled
IM SEEING A DEF PATTERN
People please see if reboots are spaced out evenly in time
runandhide05 said:
Hwy guys I had the same problem to, here is a log I started,
One of the guys on the org thread stated that it may be a overclocked gpu problem causing reboots, which the 1.1 tiamat is oc gpu, he suggested that I try lunch pad kernel, which so far has worked without a reboot yet. You can install it on to of tiamat 1.1. Which is good cause I keep most all the benefits, but with no gpu overclocking, which is lead to be the cause of reboots.
Reboot times and events
My tablet: WIFI xoom, abd root (not one click), tiamat rom 1.1 with mod pack one.
Time and date: 7/8/11 6:45 pm cst
Currect status: standby, screen off
Cpu setting: stock 1.0 ghz max , 816 mhz min. Scaling set to interactive
Cpu app: setcpu
Time and date: 7/8/11 8:41 pm cst
Current status: just competed download of mp4, file size 205.9 meg
Cpu setting: overclocked at 1.2ghz max, 1.0 min. Scaling set to on demand
Cpu app: antutu cpu master
*updated
Time and date: 7/8/11 10:51pm cst
Current status: standby, screen off
Cpu setting: stock
Cpu app: all cpu overclocking apps uninstalled
** updated
Time and date: 7/9/11 12:11am cst
Current status: standby, screen off
Cpu setting: stock
Cpu app: all cpu overclocking apps uninstalled
IM SEEING A DEF PATTERN
People please see if reboots are spaced out evenly in time
Click to expand...
Click to collapse
Is the gpu overclocked more in this kernel than tiamat 1.4.4? Cause i never had reboots with that kernel and it had an overclocked cpu.
Sent from my Xoom using XDA Premium App
phouse1025 said:
Is the gpu overclocked more in this kernel than tiamat 1.4.4? Cause i never had reboots with that kernel and it had an overclocked cpu.
Sent from my Xoom using XDA Premium
The gpu is overclock in this kernel, unlike the 1.4 which the gpu is not overclocked, just the cpu.
I installed lunchpad on to of the 1.1 last night and I didn't loose any of the features from 1.1 other than the overclocked gpu. Still have sd card and usb hosting and overclocked CPU. I would definitely do it if I were any of you guys having the reboot issues. One guy on the orig thread had to send his xoom back and moto repaired it and said that the gpu was fried. So again until there is a way to set the gpu back to stock on 1.1 user beware
Sent from my Xoom using XDA Premium App
Click to expand...
Click to collapse
runandhide05 said:
phouse1025 said:
Is the gpu overclocked more in this kernel than tiamat 1.4.4? Cause i never had reboots with that kernel and it had an overclocked cpu.
Sent from my Xoom using XDA Premium
The gpu is overclock in this kernel, unlike the 1.4 which the gpu is not overclocked, just the cpu.
I installed lunchpad on to of the 1.1 last night and I didn't loose any of the features from 1.1 other than the overclocked gpu. Still have sd card and usb hosting and overclocked CPU. I would definitely do it if I were any of you guys having the reboot issues. One guy on the orig thread had to send his xoom back and moto repaired it and said that the gpu was fried. So again until there is a way to set the gpu back to stock on 1.1 user beware
Sent from my Xoom using XDA Premium App
Click to expand...
Click to collapse
I could be wrong but if you check the post for 1.4.4 it says they have 2 versions, one with oc gpu and one without.
Sent from my Xoom using XDA Premium App
Click to expand...
Click to collapse
phouse1025 said:
runandhide05 said:
I could be wrong but if you check the post for 1.4.4 it says they have 2 versions, one with oc gpu and one without.
Sent from my Xoom using XDA Premium App
Click to expand...
Click to collapse
I just noticed that, but when I was running it I did not have the gpu oc'ed one, sorry fur the mis info
Sent from my Xoom using XDA Premium App
Click to expand...
Click to collapse
runandhide05 said:
phouse1025 said:
I just noticed that, but when I was running it I did not have the gpu oc'ed one, sorry fur the mis info
Sent from my Xoom using XDA Premium App
Click to expand...
Click to collapse
It's not a problem. I had the gpu overclocked version and never had reboots, that's what Leeds me to believe that the reboots are caused by something else in the new kernel or something in the new rom. Same with the decreased battery life issue that I hear has also affected alot of devices here recently.
Edit: I flashed the new launchpad kernel. No reboots since. Hopefully team tiamat can figure out the problem cause switching from the tiamat kernel was the last thing I wanted to do, but I had to have stability untilled things get worked out.
Sent from my Xoom using XDA Premium App
Click to expand...
Click to collapse
I had a lot of random reboots with 1.1. I resolved them by doing the following
Updating the CMW recovery img to the most recent one posted in the dev forum.
Wipe
Install ROM
Boot
The issue for me was that my recovery img was quite old so updating it and then applying the ROM resolved all of my issues. I had a few issues with the 1.4.5 kernel so I am running LaunchPad 1.2.3 now and that seems to be a bit more stable. 1.4.4 I was running at 1.4Ghz 1.4.5 I could only run at 1.2Ghz. LaunchPad 1.2.3 I am back to 1.4Ghz stable
Just an update, Since my last post on the 5th of july, I have flashed 1.4.4 OC'ed GPU Kernel and have been running Tiamat Rom 1.1 with no random reboots or any other issues. So I do believe there is something with the Stock 1.4.5 Kernel that could be making some of the xoom reboot randomly. Oh and I can OC up to 1.5 again (my xoom's max), but I leave it at 1.4 with Setcpu. Over all i'm happy once again.
Psyclic_1 said:
I had a lot of random reboots with 1.1. I resolved them by doing the following
Updating the CMW recovery img to the most recent one posted in the dev forum.
Wipe
Install ROM
Boot
The issue for me was that my recovery img was quite old so updating it and then applying the ROM resolved all of my issues. I had a few issues with the 1.4.5 kernel so I am running LaunchPad 1.2.3 now and that seems to be a bit more stable. 1.4.4 I was running at 1.4Ghz 1.4.5 I could only run at 1.2Ghz. LaunchPad 1.2.3 I am back to 1.4Ghz stable
Click to expand...
Click to collapse
Can post a link to the most recent CMW recovery ima, just so i can confirm that I have the latest??
Thanks
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?