Galaxy Nexus Unusable - Samsung Galaxy Nexus

Here's my problem: no matter what app is used to control my CPU, no matter what ROM I use, or Kernel I run, my phone cycles over and over down to 350mhz. I've even changed the voltages and governor to no avail. At this point I want to throw this thing against the wall and go ballistic.
Does anybody else have this problem? Or know how to fix it.
~Jasecloud4
Sent from the Nexus of another Galaxy.

Does this problem occur when you are running stock?

Stock root yes. Never had the problem while unrooted.
Sent from the Nexus of another Galaxy.

So...what is the problem?
The phone spends most of its time at 350mhz on any kernel.

That's weird, even with full wipes in between your ROM flashes it still cycles down to 350? You've also selected run on boot in your kernel settings and verified that the init.d file was written? Do you keep restoring with Titanium Backup or something after all your ROM flashes or do you actually start fresh?

adrynalyne said:
So...what is the problem?
The phone spends most of its time at 350mhz on any kernel.
Click to expand...
Click to collapse
The problem? Have you used this phone at 350mhz? It's worse than a G1 on Eclair...I didn't buy the latest phone to run at 1/4 of the max. Not trying to troll, but the lag between key strokes as the processor cycles down and up over and over is ridiculous. It makes the phone a terror to use.
opensourcefan said:
That's weird, even with full wipes in between your ROM flashes it still cycles down to 350? You've also selected run on boot in your kernel settings and verified that the init.d file was written? Do you keep restoring with Titanium Backup or something after all your ROM flashes or do you actually start fresh?
Click to expand...
Click to collapse
Yes, I wipe repeatedly just to make sure. No Titanium for me. Yes, run on boot is good.
Sent from the Nexus of another Galaxy.

Your explanation was confusing. I thought you meant it was spending most of its time at 350mhz, not stuck with 350mhz as a cap.
Have you returned to stock? Because rooting alone won't do this.

adrynalyne said:
Your explanation was confusing. I thought you meant it was spending most of its time at 350mhz, not stuck with 350mhz as a cap.
Have you returned to stock? Because rooting alone won't do this.
Click to expand...
Click to collapse
I apologize I wasn't clearer. The phone will switch to a high frequency and then drop all the way down to 350mhz and stay there.
No matter how much I try and change it, the phone will switch frequencies for roughly twenty seconds and drop down to 350mhz, regardless of settings.
After 3 or 4 times of doing this, the phone will stick to 350mhz and not change at all, until I reboot the phone.
Sent from the Nexus of another Galaxy.

Have you run CPU Spy through a course of a day to see what is actually happening?

jasecloud4 said:
I apologize I wasn't clearer. The phone will switch to a high frequency and then drop all the way down to 350mhz and stay there.
No matter how much I try and change it, the phone will switch frequencies for roughly twenty seconds and drop down to 350mhz, regardless of settings.
After 3 or 4 times of doing this, the phone will stick to 350mhz and not change at all, until I reboot the phone.
Sent from the Nexus of another Galaxy.
Click to expand...
Click to collapse
As a test, use something like setcpu and cap yourself at 1.2ghz and see if it stays there. You might have a bad cpu.

I had this same problem using setcpu on my old htc sensation.
I can't remember exactly what I did to fix it. I think I just got rid of setcpu and stopped messing with the clock speeds.
Sent from my Galaxy Nexus using xda premium

adrynalyne said:
As a test, use something like setcpu and cap yourself at 1.2ghz and see if it stays there. You might have a bad cpu.
Click to expand...
Click to collapse
Blah. I hope it's not bad. Dealing with insurance blows. I've done that already but I'll try again.
Maybe I should just rewrite the kernel so that 1.2ghz and 1.35ghz are the only options.
Sent from the Nexus of another Galaxy.

jasecloud4 said:
Maybe I should just rewrite the kernel so that 1.2ghz and 1.35ghz are the only options.
Click to expand...
Click to collapse
what? Its so hard to understand you. I am still not 100% sure what is the problem or what you've done because they are rather conflicting.
Not even any close to his suggestions either. Do yourself a favour and follow his instructions.
Rewriting kernel?? Er what??

Try removing all CPU control apps and see if it becomes usable
Sent from my ADR6425LVW using XDA App

s2d4 said:
what? Its so hard to understand you. I am still not 100% sure what is the problem or what you've done because they are rather conflicting.
Not even any close to his suggestions either. Do yourself a favour and listen to him.
Click to expand...
Click to collapse
No joke rofl. Having a very hard time understanding whats actually going on here lol.

I think I just put it all together. He claims 350mhz to be "1/4" of the max. So he's trying to oc to 1.4ghz and his cpu, like most, can't handle it and the system clocks down to minimum on its own.
Could be wrong but his case sounds like exactly what happened to me when trying out 1.42ghz. Even on performance gov. It just isn't stable on all cpus. Voltage tweaking may or may not help.
Sent from my Galaxy Nexus using Tapatalk

jasecloud4 said:
I apologize I wasn't clearer. The phone will switch to a high frequency and then drop all the way down to 350mhz and stay there.
No matter how much I try and change it, the phone will switch frequencies for roughly twenty seconds and drop down to 350mhz, regardless of settings.
After 3 or 4 times of doing this, the phone will stick to 350mhz and not change at all, until I reboot the phone.
Click to expand...
Click to collapse
No, I it's what he said above. His phone isn't using all the available cpu frequencies, his cpu gets stuck at 350mhz and doesn't change.
Sent from my Galaxy Nexus using xda premium

opensourcefan said:
No, I it's what he said above. His phone isn't using all the available cpu frequencies, his cpu gets stuck at 350mhz and doesn't change.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Your exactly right.
Sent from the Nexus of another Galaxy.

I'm having this same issue, was anyone able to figure out what causes it?

Related

How do you overclock your EVO

Still learning in the scene but I rooted my phone sometime 1 month ago and now using MikFroyo custom rom. Now I hear you can overclock the device to get a better benchmark on the device. My question is how ??
Please be easy on me lol. I am coming from a iPhone which is pretty pampered over there.
Thanks.
Set CPU from market
kingofslackerz said:
Set CPU from market
Click to expand...
Click to collapse
Then what I am setting ? Like I see the max @ 998400 min 245000..... Should I change the scaling ?
thanks.
You need a custom kernel first. Developement section's got a nice selection, with tons of posts showing peoples set-ups.
Don't get too caught up in benchmarks. A better score doesn't necessarily mean it is faster in real world usage. More for braggin rights than anything else.
Welcome to the EVO forum.
Its a great way to heat up, shorten battery life and cause more force closures. Good Luck!
Sent from my PC36100 using XDA App
fgarcia25 said:
Then what I am setting ? Like I see the max @ 998400 min 245000..... Should I change the scaling ?
thanks.
Click to expand...
Click to collapse
You can't overclock with a stock kernel. Like chris66 said you gotta go with a custom one.
Check out netarchys kernels, great work he does.
What is a safe range for battery temp.? I'm running in the mid 90s F. Sometimes it even gets up to 104 or so....... ?
cpu settings are built into CM7 now, thats how i manage it
bigjack100 said:
What is a safe range for battery temp.? I'm running in the mid 90s F. Sometimes it even gets up to 104 or so....... ?
Click to expand...
Click to collapse
That's normal. Basically, if you get to 50C (122F), then it's time to shut off your phone and yank the battery then stick them both by the window. Android will start *****ing at you that it's too hot at that point.

high heat temperature issue on higher than 920Mhz speeds (AOKP+Faux)

Ever since I had my nexus I only flashed AOKP and Faux's kernel. But the annoying part is that when Im using interactive or ondemand and the phone go to a higher speed, the phone gets too hots, and when it reaches 1200Mhz it gets too hot to the fact that I cant touch the top of the screen or the back cover on the camera side. Only way out of it is me using conservative and UC to 920Mhz and the phone wont reach that speed anyway. Any help please?
::No more than whatsapp and Gtalk are installed::
::Heat only happens when the screen is on. when its off it goes into deep sleep without wake ups::
::I have a GSM Nexus with WiFi only on and 2G connected without data::
Try a different kernel?
Sent from my Galaxy Nexus running Slim ICS
theking_13 said:
Try a different kernel?
Sent from my Galaxy Nexus running Slim ICS
Click to expand...
Click to collapse
I tried Franocs, Popcorn, CMPlus, Trinity and more. still the heat occurs when it reaches high speeds
How about stock?
adrynalyne said:
How about stock?
Click to expand...
Click to collapse
I unlocked and flashed AOKP as soon as I got the device haha. So I have no idea.
How hot exactly? What temperature?
What brightness is your screen set to?
adrynalyne said:
How about stock?
Click to expand...
Click to collapse
I would follow adrynalyne suggestion on this. flash stock, see if it still behavs like that, and, if it does, I would suggest returning it.
Sent from my Transformer Prime TF201
Try flashing Faux's reset kernel followed by his latest release.
nodstuff said:
How hot exactly? What temperature?
What brightness is your screen set to?
Click to expand...
Click to collapse
I dont know how much but it burns! its just way too hot. I had a phone call when it was that hot and when I put the phone on my ear I almost threw it away because of the heat!! My screen brightness is at its lowest but I have the color multiplier from faux kernel on.
bk201doesntexist said:
I would follow adrynalyne suggestion on this. flash stock, see if it still behavs like that, and, if it does, I would suggest returning it.
Sent from my Transformer Prime TF201
Click to expand...
Click to collapse
I just love AOKP and Faux's kernel I cant leave those!!
tibere86 said:
Try flashing Faux's reset kernel followed by his latest release.
Click to expand...
Click to collapse
Tried it and I still had the same issue.
Dude, temporarly. *facepalm*
sent from my i9250
Hi,
Temperature is subjective,I mean if you just touch your phone and say "it's hot"...
If I wash my hands with cold water then I take my phone...I find it hot...
Cools your hands (in the fridge ) and use your phone 5 mins, you will find it very hot...
There are already many threads about this...Arrrrgh,can't use the search function ,but for sure for the last week there is about 2 threads about that...
Try a fresh install,starts from scratch with full wipe etc,just your current ROM and if it continues flash another kernel...
Monitor your CPU temp with an app,not just your feeling,it may be biased (System Tuner for example or maybe an app like cpu temp,on the Play Store),for their respective (if you test anothers) kernel try Franco kernel updater or Glados control to monitor the CPU temp.
Also see if there isn't an app,a script,etc...that could fully or almost load your CPU...
iKarido said:
I just love AOKP and Faux's kernel I cant leave those!!
Tried it and I still had the same issue.
Click to expand...
Click to collapse
After that...If your phone is burning but you don't want change your config for see if it helps...Bah...What else?
viking37 said:
Hi,
Temperature is subjective,I mean if you just touch your phone and say "it's hot"...
If I wash my hands with cold water then I take my phone...I find it hot...
Cools your hands (in the fridge ) and use your phone 5 mins, you will find it very hot...
There are already many threads about this...Arrrrgh,can't use the search function ,but for sure for the last week there is about 2 threads about that...
Try a fresh install,starts from scratch with full wipe etc,just your current ROM and if it continues flash another kernel...
Monitor your CPU temp with an app,not just your feeling,it may be biased (System Tuner for example or maybe an app like cpu temp,on the Play Store),for their respective (if you test anothers) kernel try Franco kernel updater or Glados control to monitor the CPU temp.
Also see if there isn't an app,a script,etc...that could fully or almost load your CPU...
After that...If your phone is burning but you don't want change your config for see if it helps...Bah...What else?
Click to expand...
Click to collapse
Thanks alot. I running Gummy now with another kernel and the heat issue decreased in a big way.

[Q] T-Mobile S3 - Low Benchmark Scores/Processor not going 100%?

I've had my Galaxy S3 from T-Mobile now for about a week. The phone seems to run perfectly fine. However when I attempt to run Quadrant for example my friends are averaging anywhere from 4900 - 5300 for their stock T-Mobile S3. My same phone, stock, everything closed/killed from task manager, only manages to score 3100 - 3600.
When I check system information in Quadrant sometimes it says my current clock speed is 912Mhz, 1134Mhz etc.. Rarely do I see it at the full 1512Mhz..
Power saving mode is definitely turned off. Even after doing a factory reset and running quadrant on a fresh install it still scores the same. Beginning to get frustrated this phone isn't living up to the hype.
Ideas anyone? Thanks.
I did a battery pull, killed all my apps, cleared my memory, waited a few seconds, ran Quadrant again and still can only manage to score 3100.
No offence but who cares about benchmarks...... the phones soooo smooth and awsome
Sent from my SGH-T999 using xda premium
Don't have mine yet but I have seen someone have the same problem on here and what was wrong with theirs was they didn't know they could set the CPU Max mhz in the settings. Perhaps yours is not set to Max? Not sure where exactly in the settings it is but I'm sure it isn't hard to find
Sent from my SPH-D700 using XDA
I've been through the settings menu in the phone numerous times. Have not seen an option like that nor do I think it exists? For the most part the phone runs smooth I do notice it lags/hangs up sometimes but I'm guessing that's because the processor isn't going to full potential.
Anyone else have any ideas or where I can find this mysterious setting?
I've noticed on my sprint phone that as the phone gets warm the upper limit that the CPU can scale to seems to be reduced. The day I got it the first quad run was about 5k, but after 30min of nonstop usage the next run was down to 3.5 or so. Check it yourself with setcpu, it will start capping at 1100-1200.
OgremustCrush said:
I've noticed on my sprint phone that as the phone gets warm the upper limit that the CPU can scale to seems to be reduced. The day I got it the first quad run was about 5k, but after 30min of nonstop usage the next run was down to 3.5 or so. Check it yourself with setcpu, it will start capping at 1100-1200.
Click to expand...
Click to collapse
I will check it out but considering even after a battery pull and letting the phone sit power off for an hour I still get crappy scores. Then theres others who can run Quadrant back to back to back to back to back and achieve 4500 - 5100 constantly. I can't even get it on one try! I'll download SetCPU and see.
If you are that concerned, wipe and try it all over again.
EDIT - Damn my spotty reading, you already tried that. Sorry. Not much else to do, unless you try to restore the OS through Kies. A fresh install from a fresh source?
Or sell it on craigslist :laugh:
The phone works fine. Everything is very smooth and responds fast. It's pretty much just the benchmark scores that are throwing me off. I'll see what happens with the second S3 I will receive tomorrow. I can't imagine the heat playing a factor because this S4 is supposed to be one of the coolest running processors out there. There's a huge video on it somewhere where they did a butter melting test. Anyways time will tell I suppose.
Why do you care so much about benchmarks? Also the phone won't ramp the processor up to 1500 if it has no reason to..
Sent from my GT-I9300 using Tapatalk 2
joshnichols189 said:
Why do you care so much about benchmarks? Also the phone won't ramp the processor up to 1500 if it has no reason to..
Sent from my GT-I9300 using Tapatalk 2
Click to expand...
Click to collapse
What's the point of having the newest hottest phone right away? To be able to say it can do what others cant. One of those things being blowing away other phones in the benchmark arena. I just don't see why others are able to hit 5000+ scores and my device can't seem to even come close. It just makes me think there's something wrong with my handset. Do you blame me for being skeptical after the price we pay for these things?
Chicago281 said:
What's the point of having the newest hottest phone right away? To be able to say it can do what others cant. One of those things being blowing away other phones in the benchmark arena. I just don't see why others are able to hit 5000+ scores and my device can't seem to even come close. It just makes me think there's something wrong with my handset. Do you blame me for being skeptical after the price we pay for these things?
Click to expand...
Click to collapse
This is why I buy awesome phones. I love bleeding edge hardware lol.
Sent from my Axiom MAXX!!
Chicago281 said:
What's the point of having the newest hottest phone right away? To be able to say it can do what others cant. One of those things being blowing away other phones in the benchmark arena. I just don't see why others are able to hit 5000+ scores and my device can't seem to even come close. It just makes me think there's something wrong with my handset. Do you blame me for being skeptical after the price we pay for these things?
Click to expand...
Click to collapse
Considering you say it works just fine and are basing these problems that you have off of Quadrant..
Also I guess I will try and help since you are from Chicago they're should definitely be a setting somewhere that allows you to change the CPU settings. I'm not positive where but I did read in a review this was the first phone out of the box able to adjust governors. I would look but I'm on CM9
Sent from my GT-I9300 using Tapatalk 2
I've searched AndroidForums, Here, Google, can't find anything on being able to change the cpu speed without rooting.
Someone have the setcpu xda download page need the link, thx.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Chicago281 said:
I've searched AndroidForums, Here, Google, can't find anything on being able to change the cpu speed without rooting.
Click to expand...
Click to collapse
It might only be the international version.. I read it in a review from one of the tech sites.
Sent from my GT-I9300 using Tapatalk 2
Do you perhaps have the CPU Power Saving option on in the Power Saving menu?
Diviance said:
Do you perhaps have the CPU Power Saving option on in the Power Saving menu?
Click to expand...
Click to collapse
First post last paragraph.. No
Sent from my GT-I9300 using Tapatalk 2
Chicago281 said:
I've been through the settings menu in the phone numerous times. Have not seen an option like that nor do I think it exists? For the most part the phone runs smooth I do notice it lags/hangs up sometimes but I'm guessing that's because the processor isn't going to full potential.
Anyone else have any ideas or where I can find this mysterious setting?
Click to expand...
Click to collapse
There is a setting for this, it's actually incorporated in the power savings mode. If you read through it, there is an area that says the max cpu speed is actually lowered when it's enabled. But, if you're not using the power saver mode, then it's irrelevant to your situation. It could have to do with the bloat though, and also the international is almost double the scores as ours yet there is minimal difference in speed presented in side by side real usage testing. I wouldn't get too hung up on the benchmarks, it kind of ruins the enjoyment you get from just using the phone, and seeing how smooth and flawless most everything is. Also, once debated and tweaked, those scores will most definitely improve and will probably ease your mind a bit.

How much is safe for overclocking?

I'm running Blackout v3.0, and it's running pretty smooth at first. But now my phone is stuffed with bunch of apps, making it running slower and slower. I want to keep those apps so I'm willing to overclock but I afraid of damaging my phone. So I would like to ask what's the safe overclocking frequency? I want the optimum frequency, fast enough and safe/stable.
ImjuzCY said:
I'm running Blackout v3.0, and it's running pretty smooth at first. But now my phone is stuffed with bunch of apps, making it running slower and slower. I want to keep those apps so I'm willing to overclock but I afraid of damaging my phone. So I would like to ask what's the safe overclocking frequency? I want the optimum frequency, fast enough and safe/stable.
Click to expand...
Click to collapse
Any overclocking can be unsafe as it can shorten the lifespan of your memory and CPU. But with that said I run mine at 1200 with no issues. Most people don't go higher than 1600 but anything 1400 or lower is not going to burn it up too quick IMO. Everyones hardware will react differently though.
Sent from my Inspire 4G using xda app-developers app
They usually say phone will get damaged, but I think its a myth. You can go up to 1600. After that it will get unstable.
Sent from my Inspire 4G
ImjuzCY said:
I'm running Blackout v3.0, and it's running pretty smooth at first. But now my phone is stuffed with bunch of apps, making it running slower and slower. I want to keep those apps so I'm willing to overclock but I afraid of damaging my phone. So I would like to ask what's the safe overclocking frequency? I want the optimum frequency, fast enough and safe/stable.
Click to expand...
Click to collapse
I run IceColdSandwich and have found 1459MHz to be the best combo of performance and stability on my phone. Every phone handles OCing a little differently, some can reportedly take over 1600 without a flinch and others will lock regularly with even a slight OC. Just experiment with the "set at boot" option turned off until you find something that works reliably on your phone.
Is it true you guys aren't seeing ill effects on your battery by overclocking like that?
Sent from my HTC Desire HD using Tapatalk 2
asif9t9 said:
Is it true you guys aren't seeing ill effects on your battery by overclocking like that?
Sent from my HTC Desire HD using Tapatalk 2
Click to expand...
Click to collapse
I think OC can affect battery drain only if you use an application which utilizes a full cpu load. But, if you're using this app in normal mode, economy will not be great also. So, when you using your phone for calling or general usage you will not see any problems with battery discharge.
I'm using DHD with Blackout v3.0 and I set 1200Mhz for maximum cpu value. I have no problems, phone is stable. Some time ago I used Leedroid ROM and set also 1200Mhz, but phone was rebooted by itself very often. More than twice a day.
You should try to use OC, as someone said above, without "set on boot" option. I think there is no danger for hardware up to 1600Mhz.
asif9t9 said:
Is it true you guys aren't seeing ill effects on your battery by overclocking like that?
Click to expand...
Click to collapse
Not under normal use. There's a school of thought that says even though the increased speed requires more power, it can also finish tasks and go back to sleep faster, so it ends up being a wash. I've overclocked all three smartphones I've owned to date and haven't experienced any significant difference in battery life.
ai6908 said:
They usually say phone will get damaged, but I think its a myth. You can go up to 1600. After that it will get unstable.
Sent from my Inspire 4G
Click to expand...
Click to collapse
They say that as a precautionary measure just as they say flashing a custom ROM can be dangerous. For people who don't know what they're doing. But precaution aside, just like you said you can go up to 1600 MHz safely on this phone. I know every phone behaves differently but on average no one has issues upto that frequency. But above that frequency the phone might be unstable. The CPU will be drawing much more power at high frequencies and will heat up more. The CPU heating up too much and too frequently reduces the life of the CPU. So it's not a myth.
Sent from my Desire HD using xda premium
2ghz.... the phone is old now. Make it bleed.
Sent from my Desire HD
Don't try to Cross above 1600.

[Q] Has anyone gotten their D2spr device to over clock past 1.7Ghz?

As the title says, no matter what I try, I cannot push my device up to 1809Mhz or higher. Has anyone been able to? Could you drop a tip or two about what voltages I should try?
tpike1296 said:
As the title says, no matter what I try, I cannot push my device up to 1809Mhz or higher. Has anyone been able to? Could you drop a tip or two about what voltages I should try?
Click to expand...
Click to collapse
Depends on the kernel too. Some phones will be better to support higher speeds than others.
tpike1296 said:
As the title says, no matter what I try, I cannot push my device up to 1809Mhz or higher. Has anyone been able to? Could you drop a tip or two about what voltages I should try?
Click to expand...
Click to collapse
I've gone up to 2106MHz with @ktoonsez kernel using the default voltages, I was also able to undervolt too.
Edit, some differences in the manufacturing causes each phone to be different. What works with one phone might not work with another. My point: some phones can't be over clocked passed a certain point. My E4GT couldn't go pass 1.5GHz no matter what I did.
Second edit: why do you want / feel the need to overclock this phone?
Aaron Swartz, Rest in Pixels.
jamcar said:
I've gone up to 2106MHz with @ktoonsez kernel using the default voltages, I was also able to undervolt too.
Edit, some differences in the manufacturing causes each phone to be different. What works with one phone might not work with another. My point: some phones can't be over clocked passed a certain point. My E4GT couldn't go pass 1.5GHz no matter what I did.
Second edit: why do you want / feel the need to overclock this phone?
Aaron Swartz, Rest in Pixels.
Click to expand...
Click to collapse
I haven't felt the need, currently running BMS kernel-asswax gov. Superb battery life.
Sent from my hybrid GalaxyS3
joeyhdownsouth said:
I haven't felt the need, currently running BMS kernel-asswax gov. Superb battery life.
Sent from my hybrid GalaxyS3
Click to expand...
Click to collapse
I haven't either, with this phone, other than to do a benchmark and to say I could. I'm just wondering why the OP feels the needs.
Aaron Swartz, Rest in Pixels.
tpike1296 said:
As the title says, no matter what I try, I cannot push my device up to 1809Mhz or higher. Has anyone been able to? Could you drop a tip or two about what voltages I should try?
Click to expand...
Click to collapse
You could try raising your voltages alittle
Sent from my SPH-L710 using xda premium
If you are in TW, search ziggy's in Google.
infected with the unspeakable
Yeah, I suggest you look up "CPU binning" and see what you have as not all processors can handle the same things, and you can seriously damage your phone by overclocking too high or something similar.
jamcar said:
I've gone up to 2106MHz with @ktoonsez kernel using the default voltages, I was also able to undervolt too.
Edit, some differences in the manufacturing causes each phone to be different. What works with one phone might not work with another. My point: some phones can't be over clocked passed a certain point. My E4GT couldn't go pass 1.5GHz no matter what I did.
Second edit: why do you want / feel the need to overclock this phone?
Aaron Swartz, Rest in Pixels.
Click to expand...
Click to collapse
The only real reason I wanted to overclock was to say that I could (and do some benchmarks). Curiosity, mainly. I've since realized that even going to 1728Mhz has proven fairly useless except if I want to reduce battery life, or get a *tiny* boost when emulating the N64. Thank you for the explanation of why it most likely wouldn't work. Seems I always get devices that don't really like overclocking, as my HTC EVO 4G didn't seem to like more than a tiny boost, either.

Categories

Resources