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.
I know there are countless threads related to G2x Problems but none of the threads are focusing on isolating the reasons of Freezing Issue. I have recently upgraded my phone from Galaxy S Vibrant to G2x and i have to say i love the hardware and performance. Only Issue for me is random freezing.
After using the phone for 2 weeks and trying 3 roms
1. Stock
2. EB 1.04
3. Dark Sinister 1.1
I have come to a conclusion that kernel and rom is not the solution. At least not for me.
So i will try to solve the problem using hardware testing.
From my past 2 weeks experience.
1. Phone Freezes at night during charging
2. Phone Freezes when ever i turn off/on wifi and bluetooth and gps and Data (4g/3g) (Still have to figure out which of them is the cause. Cause i usually turn all off when i need to save battery).
Test Day 1
For Reason 1
I am using SetCpu and have changed Min from 216 to 312Mhz. I am trying this because i think very low cpu usage in standby for a very long period causes the phone to freeze. Its a Hunch i am not sure.
For Reason 2
I will keep wifi, Bluetooth and GPS off.
I will keep 4g/3g Data On all the time.
To My Surprise its been 16 hours no freeze. It includes charging at night. Lets see how long i can go without a freeze. Upon freezing i will make some changes.
Update 31/5/2011 (Test Day 2)
Ok its been more than 40 hours and not a single crash...
I removed the following possibilities as well....
It wont crash upon excessive usage.
Also Normal Heat up does not cause the crash.
As i have been playing Samurai II Vengeance all day long... Until I ended it. Several times charging along playing. I even played it on TV using HDMI. Not a single crash. I used to have around 3 crashes a day on stock rom when i unboxed my new G2x.
I also started using GPS from today. So lets see how it goes. I will update it every 24 hour.
Update 3/6/2011 (Test Day 5)
Ok i am considering Random Freezing On standby as solved because i havent had a single freeze at night after setting CPU Clock at 312 MHz using SetCPU. There are also other comments that back up my solution. I am considering this the solution of one problem.
2nd Issue of freezing while using cell phone apps is because of certain applications that are either buggy or not compatible with tegra Platform. For that i will start another thread with individual application testing for all apps that can cause the system to freeze or crash.
Please Discuss apps System Bloat-ware/User Apps that cause your G2x to Crash or Freeze in the following thread i created:
http://forum.xda-developers.com/showthread.php?p=14399089
Thanks for all the feedback.
Luckily I dont get that issue, buy I think this is a good test :u
Good point. I have not had these issues but i do have trinity kernel and minimum speed is 300
G2x with CM7 and trinity kernel
All you have to do is be careful what apps you install. I've had the phone for over a month and the one time it rebooted or froze was when I used an app the phone didn't agree with.
I am almost certain that people are experiencing reboots and freezing because of the apps they have on their phone. Hopefully the update will solve the problem because it shouldn't be that way.
Sent from my LG-P999 using XDA App
In my opinion, the shut down has to do with temperature of the phone. As long as I keep the phone cool by not charging and multitask with other things, then my phone is fine.
garrychau said:
In my opinion, the shut down has to do with temperature of the phone. As long as I keep the phone cool by not charging and multitask with other things, then my phone is fine.
Click to expand...
Click to collapse
I used to think the same thing but the problem is my phone gets hot and works fine. I am almost positive it has something to do with an issue in the kernel that's being exposed by certain apps. My Xoom on release had reboots and SOD and it went away with app updates and removals. It also has Tegra 2
Sent from my LG-P999 using XDA App
mobilehavoc said:
I used to think the same thing but the problem is my phone gets hot and works fine. I am almost positive it has something to do with an issue in the kernel that's being exposed by certain apps. My Xoom on release had reboots and SOD and it went away with app updates and removals. It also has Tegra 2
Sent from my LG-P999 using XDA App
Click to expand...
Click to collapse
Do you or @kangxi remember what Apps gave you issues?
it has to be a driver issue, its virtually the only explanation for why devs have not hammered it out yet or even CM7 team for that matter... it has problems on pure AOSP which leaves drivers or overheating (unlikely)... LG has to come up with the fix because they know their drivers and hardware better than everyone else...
Well the obvious problem I see is that they are all based on the stock rom. Try using one build from AOSP or a CM variety.
I didn't stay stock long but I did have reboot using the leaked Gingerbread (which is what EB is built from). I don't follow it but one is based off the stock 2.2.2 rom and the other is based off the leaked 2.3.3 rom.
I had nothing but problems with the stock roms. Thus your problem I think. Move over to Bionic, CM7, Gigglebread, or something.
I tested my phone and I didn't have a reset in like 5 days (which then my battery died overnight because I forgot to plug it in). I usually crackflash the CM nightlies and haven't had any problems with reboots or any issues requiring a reboot (aside from the flashlight killing audio, but just don't use it).
There are definitely two problems - software and the battery. I used to way more problems until I exchanged the battery for a new one and that solved most of my issues. The issues that remain are definitely software based.
tackleberry said:
Good point. I have not had these issues but i do have trinity kernel and minimum speed is 300
G2x with CM7 and trinity kernel
Click to expand...
Click to collapse
Thanks for this information/ Changing the minimum speed didnt affect the battery life but it has survived two nights without crashing. So i am planning to keep it at 312Mhz min.
kangxi said:
All you have to do is be careful what apps you install. I've had the phone for over a month and the one time it rebooted or froze was when I used an app the phone didn't agree with.
I am almost certain that people are experiencing reboots and freezing because of the apps they have on their phone. Hopefully the update will solve the problem because it shouldn't be that way.
Sent from my LG-P999 using XDA App
Click to expand...
Click to collapse
I Completely Agree with you. Some Applications do cause system crashes. But I have removed all the t-mobile bloatware and i only have few games and GPS apps. All games are from tegra zone. So I am sure they are supported.
For GPS App i am using Copilot and it didnt crash on me once.
I just installed setcpu and set minimum to 312. I'm keeping everything else the same to see if this change has any difference. Will report back.
Sent from my LG-P999 using XDA App
Looks like you are gaining progress. Sounds like keeping the processor revved up a little more does the trick.
It would be a simple fix for people to try that have reboot issues. I can't get mine to reboot, so unfortunately I cannot help you. My contribution was to resist from flashing for as long as possible to test how long I could get my "uptime" to. I got up to 127 hours when I passed out without charging it.
I'm running 20 hours now because I forgot to charge it again (seems to be my only problem, lol).
Looks like you may have fixed your rebooting issues. It sounds feasible that the clock speed could be causing it. I never had a reboot so I can't help you out but I can tell you that I have a profile under SETCPU that clocks it at 216 min and 216 max when the display is off and I don't have a problem. I wonder why the low clock speeds would only effect certain devices? Maybe it's certain apps that stay running in the background (since there poorly written) that require higher clock speeds than what the G2X gives at idle?
jrwingate6 said:
Looks like you may have fixed your rebooting issues. It sounds feasible that the clock speed could be causing it. I never had a reboot so I can't help you out but I can tell you that I have a profile under SETCPU that clocks it at 216 min and 216 max when the display is off and I don't have a problem. I wonder why the low clock speeds would only effect certain devices? Maybe it's certain apps that stay running in the background (since there poorly written) that require higher clock speeds than what the G2X gives at idle?
Click to expand...
Click to collapse
I've definitely noticed that the G2X wakes up faster and smoother (fade in from screen off) when min is set to 312mhz that's for sure. if this is all it will take to stop the reboots, I'll be super happy because otherwise this phone is just amazing.
mobilehavoc said:
I've definitely noticed that the G2X wakes up faster and smoother (fade in from screen off) when min is set to 312mhz that's for sure. if this is all it will take to stop the reboots, I'll be super happy because otherwise this phone is just amazing.
Click to expand...
Click to collapse
Have you noticed any changes in battery usage? I haven't really played around with SETCPU much but can the clock speed be set lower and if it can, have you tried slightly lower settings than 312mhz?
y are u guys using setcpu? and its def cuz the min is too low faux has his at 400 and no problems morfic also has his a little higher then what is it i think 216?? thats too low thats y setcpu isnt supported yet.....pimp my cpu
Someone asked me a question earlier. Only app I had issues with was fring. Soon as I opened it and started playing around with it, phone rebooted.
I uninstalled and it never happened again.
Sent from my LG-P999 using XDA App
mobilehavoc said:
No clue what you're trying to say but setCPU works fine. At startup for first time I selected Tegra2 and it works great. I have max set to 1000 and min to 312mhz (default was min to 216mhz). I'm running stock ROM but with root. that's all.
Click to expand...
Click to collapse
well thats y it works for u, u cant overclock over a thousand mhz so in ur situation ur ok i guess it only applies for people running a custom kernel then setcpu doesnt work, then u would need pimp my cpu
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.
It was suggested to me that in order to prevent excessive battery drain and heat when using CM7 I should disable one of the cores. Has anyone done this? What negative impacts could doing this cause (if any)?
webmaster said:
It was suggested to me that in order to prevent excessive battery drain and heat when using CM7 I should disable one of the cores. Has anyone done this? What negative impacts could doing this cause (if any)?
Click to expand...
Click to collapse
If anything it would increase battery drain due to all the processing being put on one single core, what I would recommend for a decrease in battery drain is different kernels with under volting options. That's what's worked best for me.
Sent from my Sensation using xda premium
Chilled26 said:
If anything it would increase battery drain due to all the processing being put on one single core, what I would recommend for a decrease in battery drain is different kernels with under volting options. That's what's worked best for me.
Sent from my Sensation using xda premium
Click to expand...
Click to collapse
It was my perception that the older single core phones had better battery life. Do you really think it would hurt the battery?
Dual core isn't properly utilized yet so it might not be a bad idea.
Here is an example of my battery drain for today with the bricked kernel v1.4.
Sent from my Sensation using xda premium
Changing kernel and undervolting did the trick for me. Getting 20 hours moderate use.
Sent from my Sensation using xda premium
Chilled26 said:
Here is an example of my battery drain for today with the bricked kernel v1.4.
Sent from my Sensation using xda premium
Click to expand...
Click to collapse
What are your settings?
Most of the time when both cores are on the 2nd isn't doing anything, because the first core isn't even pushed enough to reach max. So, I feel 1 core is sufficient, I'm running 4.1.x w/ 1 core @800 and the battery and speed are fine. Although I see others running speeds of 1.2 and higher, but I barely notice the difference of the freqs. The S3 is so fast that the higher clocks are overkill IMO.
Ace42 said:
Most of the time when both cores are on the 2nd isn't doing anything, because the first core isn't even pushed enough to reach max. So, I feel 1 core is sufficient, I'm running 4.1.x w/ 1 core @800 and the battery and speed are fine. Although I see others running speeds of 1.2 and higher, but I barely notice the difference of the freqs. The S3 is so fast that the higher clocks are overkill IMO.
Click to expand...
Click to collapse
I suspect you see a noticeable difference in battery life then? Also, what method did you use to disable the second core?
webmaster said:
What are your settings?
Click to expand...
Click to collapse
Honestly I don't even touch the settings I just run at default.
Sent from my Sensation using xda premium
Pretty snappy
su
chmod 644 /sys/devices/system/cpu/cpu1/online
echo "0" > /sys/devices/system/cpu/cpu1/online
chmod 444 /sys/devices/system/cpu/cpu1/online
Someone in faux kernel forum was talking about doing this. Gscript app makes it easy to run script. If you dont like it just reboot and 2nd core is back on.
Sent from my Sensation using XDA Premium App
Chilled26 said:
Honestly I don't even touch the settings I just run at default.
Sent from my Sensation using xda premium
Click to expand...
Click to collapse
I tried Faux's and it was ok, I plan on trying Bricked tomorrow. However if disabling a core gives even better results then that might be the way to go.
webmaster said:
I suspect you see a noticeable difference in battery life then? Also, what method did you use to disable the second core?
Click to expand...
Click to collapse
echo 0 > /sys/devices/system/cpu/cpu1/online
I do see a difference in battery life, which is why I prefer this setup, when we have ICS I will use both cores. But I feel cheated on Ginger so I use 1 for now, and whoever said two cores has better batt is wrong...Logically two cores use twice the voltage, that means 1 cores will save a significant amount of power. A weak dual core w/ 1 core on will have bad life, but a fast on is different.
Ace42 said:
echo 0 > /sys/devices/system/cpu/cpu1/online
Click to expand...
Click to collapse
Is that permanent or does it need to be run each time you reboot?
webmaster said:
Is that permanent or does it need to be run each time you reboot?
Click to expand...
Click to collapse
Every boot, you can make a linux script(.sh) if you want, and then use script manager. But, I'm only testing this for comparison, I can't see the speed difference w/ 1 or 2 so I just use 1. 1 @800 core feels how fast my MT4G did when OC'd @1.4Ghz.
Ace42 said:
Every boot, you can make a linux script(.sh) if you want, and then use script manager. But, I'm only testing this for comparison, I can't see the speed difference w/ 1 or 2 so I just use 1. 1 @800 core feels how fast my MT4G did when OC'd @1.4Ghz.
Click to expand...
Click to collapse
How long have you been running like that?
I run Faux kernel, Joe's RCU, undervolted -50mV and underclocked to 1Ghz, I can now easily make it through the day and I'm a moderate to heavy user. I'm pretty sure disabling the second core isn't necessary, and frankly, if you check out how little it's used, it probably wouldn't benefit that much anyhow.
Ace42 said:
echo 0 > /sys/devices/system/cpu/cpu1/online
I do see a difference in battery life, which is why I prefer this setup, when we have ICS I will use both cores. But I feel cheated on Ginger so I use 1 for now, and whoever said two cores has better batt is wrong...Logically two cores use twice the voltage, that means 1 cores will save a significant amount of power. A weak dual core w/ 1 core on will have bad life, but a fast on is different.
Click to expand...
Click to collapse
Completely false. Just because something has voltage across it doesnt mean that it is doing anything. Voltage times current equal power. Using power uses the battery.
You guys need to SERIOUSLY change the way you make decisions. Just because something SEEMS logical to you, doesnt mean it is correct. I see alot of BAD info being pushed around here.
I have CM7 and run Fauxs kernels. I FORCE both CPUs online and run at 1.56Ghz. My standby is around 30mAH...Nuff said.
Something else is messed up. Chase facts, not fiction people.
Another issue? UVing. You guys break so many rules in electrical engineering that it isnt even funny. Ive explained things so many times that I am sick of it. I wont anymore, but will let you know that you have missed some key facts.
Matt
mrg02d said:
Completely false. Just because something has voltage across it doesnt mean that it is doing anything. Voltage times current equal power. Using power uses the battery.
You guys need to SERIOUSLY change the way you make decisions. Just because something SEEMS logical to you, doesnt mean it is correct. I see alot of BAD info being pushed around here.
I have CM7 and run Fauxs kernels. I FORCE both CPUs online and run at 1.56Ghz. My standby is around 30mAH...Nuff said.
Something else is messed up. Chase facts, not fiction people.
Another issue? UVing. You guys break so many rules in electrical engineering that it isnt even funny. Ive explained things so many times that I am sick of it. I wont anymore, but will let you know that you have missed some key facts.
Matt
Click to expand...
Click to collapse
So me having better life w/ 1 core is false? Even though I've compared it w/ 2? And I don't know what your problem is but keep it to yourself, I didn't force you to respond to my post, only sharing my experiences.
webmaster said:
How long have you been running like that?
Click to expand...
Click to collapse
Almost 1 day, battery around 30 still. But I listened to music, internet, sync and played some games so my life was shorten.
Ace42 said:
So me having better life w/ 1 core is false? Even though I've compared it w/ 2? And I don't know what your problem is but keep it to yourself, I didn't force you to respond to my post, only sharing my experiences.
Almost 1 day, battery around 30 still. But I listened to music, internet, sync and played some games so my life was shorten.
Click to expand...
Click to collapse
I didnt say this. It is obvious what I said, so why would you even ask me? Just scroll up pal.
You didnt simply give an experience...You implied that your experience is LOGICAL. It may to you, but it is incorrect. Dont just throw things out there, please. It makes people with backgrounds in power and energy pissed off.
Also, my finding completely debuncts your theory. At night, while I sleep, I see 5mAH draw.
Matt
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?