Database Users

Linpack scores for Droid Wrist over 15 megaflops?!

Sent from my Eris using the XDA mobile application powered by Tapatalk

according to the Droid Eris linpack scores, evil Eris 3 seems to be coming out as it was posted as one of the roms
Sent from my Eris using the XDA mobile application powered by Tapatalk

Holy **** he's right though.
Check this out:
http://www.greenecomputing.com/apps/linpack/linpack-by-device/

andrew8806 said:
LMAO.... its become a trend, you guys are mean.. i love it...
Click to expand...
Click to collapse
Thinking about buying an incredible...
not because the better specs, but so I can get out of the eris boards :S

That's right Evil Eris 3 and a magical 1.3ghz overclock.

1300mhz???? Hmmmm

They are fake, you can submit anything you want to that site long as you know how.

I thought I read that they had a pretty extensive anti-cheating system in place Maybe someone has liquid cooling in their eris

I can confirm they are fake. I am not, nor have I ever had EE3 on my phone, yet I got 8mflops out of it.

What rom are you running. 8 is pretty amazing. Getting barely 3...
-------------------------------------
Sent via the XDA Tapatalk App

Mines not fake... Beesley @ 5.45 mflops. 806mhz. not fake. not much to brag about, but no fake.

You guys with the fast speeds, can you post what settings you have your setcpu at, current rom and any tweaks you have? I am running Aloyius v11 MAPS version and only get 2.8

rw6497 said:
What rom are you running. 8 is pretty amazing. Getting barely 3...
-------------------------------------
Sent via the XDA Tapatalk App
Click to expand...
Click to collapse
I think he was saying "I don't have that rom and yet it says I have 8 mflops even though I never did that" or something. As jcase said, they're probably all fake. There's no way our little old eris could handle 1300mhz without like exploding. Hell I don't even think it could reach it in the first place.

droidkevlar said:
You guys with the fast speeds, can you post what settings you have your setcpu at, current rom and any tweaks you have? I am running Aloyius v11 MAPS version and only get 2.8
Click to expand...
Click to collapse
Kevlar,
The ROMs that are the Vanilla ROM's with JIT are the ones that pull down high 4's and low 5's. Aloysius is a sense based the ave scores on these ROMs are 2.8-3.2. I am currently running sense-able and get 3.2. I have ran Eris lightning bolt and gotten 5. Oh my phone was at 729 when doing this.

Sheen160 said:
I think he was saying "I don't have that rom and yet it says I have 8 mflops even though I never did that" or something. As jcase said, they're probably all fake. There's no way our little old eris could handle 1300mhz without like exploding. Hell I don't even think it could reach it in the first place.
Click to expand...
Click to collapse
They are fake, some of them are me showing how that site means jack. I can post 200mhz with 200mflops if you want.

jcase said:
They are fake, some of them are me showing how that site means jack. I can post 200mhz with 200mflops if you want.
Click to expand...
Click to collapse
Lol I'd like to see that. Not that I don't believe you, I just think it'd be funny.

jonathanphx1 said:
Kevlar,
The ROMs that are the Vanilla ROM's with JIT are the ones that pull down high 4's and low 5's. Aloysius is a sense based the ave scores on these ROMs are 2.8-3.2. I am currently running sense-able and get 3.2. I have ran Eris lightning bolt and gotten 5. Oh my phone was at 729 when doing this.
Click to expand...
Click to collapse
OK. So no sense= 1 1/2x speed. I guess I need to decide which none sense ROM to check out. Thanks for the input.

droidkevlar said:
OK. So no sense= 1 1/2x speed. I guess I need to decide which none sense ROM to check out. Thanks for the input.
Click to expand...
Click to collapse
Why? Aloysius with OC is plenty fast. You're not gonna get it up to like Nexus one speed if that's what you're trying for. But anyway, I think tainted vanilla would be a good one. I would say vanilladroid but it's outdated and I had lots of problems with it.

Sheen160 said:
Why? Aloysius with OC is plenty fast. You're not gonna get it up to like Nexus one speed if that's what you're trying for. But anyway, I think tainted vanilla would be a good one. I would say vanilladroid but it's outdated and I had lots of problems with it.
Click to expand...
Click to collapse
It is fast. BUT I need different ringtones for different callers and v11 doesnt work in that area. So I went back to v6 with my mods. Its decent enough without OC. But I am just amazed at how fast ppl are getting with linpack. I guess its the I just wanna do it myself thing, ya know?

http://www.androidpolice.com/2010/0...-it-compared-to-2-1-oh-only-about-450-faster/

T-Mobile G2 with Google, first T-mobile HSPA+ phone

T-Mobile G2 with Google, first HSPA+ phone from T-Mobile.
http://g2.t-mobile.com/
Specs?

Can't wait for the g2. Gonna be hard to give up my NEXUS.

I don;t think the G2 will be the replacement of my N1. According to all the articles that I've read, they say it will be a 800MHz (only speculations at this time) processor and not a +1GHz. If this is true, then I'll wait for the N2.
http://androidspin.com/2010/08/12/rumor-t-mobiles-first-hspa-device-g1-blazehtc-g2/

I dont think its going to be the vision to be honest.
Its pointless to have a phone with scorching web speeds and an inferior processor. Android spin starts more bull**** rumors then anyone anyway.

jcohenlv said:
I dont think its going to be the vision to be honest.
Its pointless to have a phone with scorching web speeds and an inferior processor. Android spin starts more bull**** rumors then anyone anyway.
Click to expand...
Click to collapse
This phone will not have anything past 1ghz snapdragons we all know as of right now. The new line isn't coming until the end of the year.

I think I might give up my nexi, I've been dying for a keyboard phone comparable to the nexus one. This may be it.

Not me. I rooted mine when the 1-click root app came out and it gave me more reasons to keep mine. I love it even more! I can't believe i thought of replacing it.
Sent from my Nexus One using XDA App

so now that cyanogen has told us it's a different processor I'm hoping it'll be good. they need to release official specs soon

mcp2009 said:
so now that cyanogen has told us it's a different processor
Click to expand...
Click to collapse
A) Link?
B) How would he know?

Paul22000 said:
A) Link?
B) How would he know?
Click to expand...
Click to collapse
If you check his twitter account, he posted the details of the processor a couple of days ago. But yeah I think it said between 800mhz-1ghz

sstang2006 said:
I don;t think the G2 will be the replacement of my N1. According to all the articles that I've read, they say it will be a 800MHz (only speculations at this time) processor and not a +1GHz. If this is true, then I'll wait for the N2.
http://androidspin.com/2010/08/12/rumor-t-mobiles-first-hspa-device-g1-blazehtc-g2/
Click to expand...
Click to collapse
This is one of those cases where MHz won't matter one bit. The chip has a whole bunch of new features not found on the N1, including many hardware multimedia accelerators. Plus, you really won't notice much of a different with just a 200MHz drop.
With a faster radio, more memory and better hardware acceleration, the CPU speed becomes less important.
I'll upgrade if it offers speedy HD video, HDMI out and more memory as those are the things I'm missing on my N1.

The phone will have the scorpion chip set which equivalent too the snapdragon, but with a better cpu and wvga screen
Sent from my Nexus One using XDA App

It's going to be hard for me to give my Nexus up as well. I'm still trying to weigh my options on whether I should just go ahead and get the G2 or keep my N1. If the screen size is not 4.3" I will be keeping my Nexus until a 4.3" T-Mobile Android deice come out.
Sent from my Nexus One using XDA App

Heres a link but I'm not sure how he knows

mcp2009 said:
Heres a link but I'm not sure how he knows
Click to expand...
Click to collapse
Information from the leaked g2rom

mcp2009 said:
Heres a link but I'm not sure how he knows
Click to expand...
Click to collapse
Thanks.
I'm still waiting for a 1.3-1.5 GHz phone before replacing my Nexus.

Honestly, im waitng for the next Dev phone, personally the mod community on the Nexus One is far superior to anything it could be on any other phone. So i'll wait, im not a slide out keyboard guy anyway. Google tends to release a new "dev" phone for each major release:
G1 - 1.0 &1.5
MT3G - 1.6 (i think)
Droid -2.0
Nexus One -2.1 & 2.2

Droid was never a development phone

JCopernicus said:
Droid was never a development phone
Click to expand...
Click to collapse
no but is was a pure android phone (no skin or anything) and was the flagship phone for 2.0, so as far as im concerned it was an unofficial dev phone

JCopernicus said:
Droid was never a development phone
Click to expand...
Click to collapse
Blueman101 said:
no but is was a pure android phone (no skin or anything) and was the flagship phone for 2.0, so as far as im concerned it was an unofficial dev phone
Click to expand...
Click to collapse
Not to mention Google was giving it away along with Nexus One's to developers.

1.28GHz IS NOT REAL

1.28GHz IS NOT REAL
I know I posted it, and people have been running it. But after looking over the code more last night, I realized that I had been had. I took the word of another developer on the line for 1.28GHz, added it to my kernel, and it magically worked. After looking at it closer, whether intentional or not, he had the multiplier set at 0x1E(30), which is 1.152GHz. So even though it's reporting 1.28GHz, it's really running at 1.152GHz.
I've learned my lesson trusting someone else for what I should have looked into more closely, and I hope you all don't think worse of me for doing that. I apologize for leading people astray with this, but hey, at least I'm man enough to admit it.
Again, I really feel bad for misleading people on this, it's not in my nature to do that, ok maybe some, but not with something like this.
With that all said, I could do one showing maybe 4.71GHz, now that'd be awesome for screenshots. lol
Z

No worries. The cool thing is that my phone was actually mostly stable at 1.15 which was never really possible before. Usually i get freezes and bootloops. On yours the worse i got was an app quitting once in awhile.

no worries dude you did the right thing

So if I get up to 88 miles per hour my phone won't put out the 1.28 gigawatts to make me time travel? That's a shame.
Sent from my ADR6300 using XDA App

brownie points for coming clean
has anyone made a custom oc uv with the new .17 kernel yet?
EDIT: i feel dumb...didn't realize source wasn't out for the new kern.

I didn't use the kernel, but you doing this makes me (and hopefully everyone else) respect you even more as a developer.

jdkoreclipse release another ROM?...

Ianxcom said:
No worries. The cool thing is that my phone was actually mostly stable at 1.15 which was never really possible before. Usually i get freezes and bootloops. On yours the worse i got was an app quitting once in awhile.
Click to expand...
Click to collapse
HeyItsLou said:
no worries dude you did the right thing
Click to expand...
Click to collapse
djh816 said:
brownie points for coming clean
has anyone made a custom oc uv with the new .17 kernel yet?
EDIT: i feel dumb...didn't realize source wasn't out for the new kern.
Click to expand...
Click to collapse
g00s3y said:
I didn't use the kernel, but you doing this makes me (and hopefully everyone else) respect you even more as a developer.
Click to expand...
Click to collapse
At least I'm getting the response I was hoping for, thank you all for understanding. I'll be re-doing all my kernels this evening. I may even do some capped at 2.6496GHz, that way people can play to see how high they really can go. Brownie points to anyone that figures out why I choose that freq. lol
adamd1169 said:
So if I get up to 88 miles per hour my phone won't put out the 1.28 gigawatts to make me time travel? That's a shame.
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
Sorry dude, I was hoping for time travel myself, but for now, we're stuck in the present.
Z

Not a problem man, it wasn't like you were doing it on purpose. So all is good. We appreciate your work!

Makes sense. I tried it on the Feather ROM and was getting almost exactly the same performance/scores.
Much appreciated for coming clean and letting everyone know. I doubt anyone would hold it against you.

Z,
You are a good person for accepting the blame for somebody else's mistake. Either way your kernels are better than almost all others on the desire ports so I am sticking to them. Happy with the performance and it being stable at 1.152. Made me follow you on twitter.
2 other comments/questions:
1. did u take out the debug script that you had posted about on twitter? I did not see battery loss anyways...
2. I tried your incredible AOSP kernel on ultimate droid 1.0.0 but it turned the touch screen into unresponsive mode. Did dalvik wipe etc. Given that UD is like CM, I would have thought it would need an AOSP kernel but perhaps I was wrong. Could you please take a look at that?
Thanks and keep up the good work.

ziggy471 said:
1.28GHz IS NOT REAL
I know I posted it, and people have been running it. But after looking over the code more last night, I realized that I had been had. I took the word of another developer on the line for 1.28GHz, added it to my kernel, and it magically worked. After looking at it closer, whether intentional or not, he had the multiplier set at 0x1E(30), which is 1.152GHz. So even though it's reporting 1.28GHz, it's really running at 1.152GHz.
I've learned my lesson trusting someone else for what I should have looked into more closely, and I hope you all don't think worse of me for doing that. I apologize for leading people astray with this, but hey, at least I'm man enough to admit it.
Again, I really feel bad for misleading people on this, it's not in my nature to do that, ok maybe some, but not with something like this.
With that all said, I could do one showing maybe 4.71GHz, now that'd be awesome for screenshots. lol
Z
Click to expand...
Click to collapse
Placebo I love it, lol Hey thanks for clearing that up ziggy!!
ID
P.S. Can we get a placebo of over 9000!!!!! I kidd

Spider man
Sent from my ADR6300 using XDA App

khanam said:
Z,
You are a good person for accepting the blame for somebody else's mistake. .......
Click to expand...
Click to collapse
I'm currently using the aosp kernel with shadow rom and it's working great. Just that slight battery drain with screen on is the only issue I have with it currently.
Sent from my Incredible using Tapatalk.

whewstoosae said:
I'm currently using the aosp kernel with shadow rom and it's working great. Just that slight battery drain with screen on is the only issue I have with it currently.
Sent from my Incredible using Tapatalk.
Click to expand...
Click to collapse
I know what the problem is, and will try and post new kernels tonight.
So ID wanted a 9GHz kernel, should I do it just for grins???
Z

Hm. Will this be good with battery drain as well as a decent performer?

Much respect Ziggy, takes a real man to admit a gaff, even if it's not your gaff to own up to!
Sent from my ADR6300 using XDA App

djh816 said:
brownie points for coming clean
Click to expand...
Click to collapse
haha... hows his ass taste?
sorry you fell right into that one

I hadn't heard of your kernels before this thread, but I'm giving the latest a try. I'm one of the lucky few that can run stable at 1.19 GHz, so 1.28 would have been insane.

The latest kernel is running great. The only issue I'm having, I can't connect to wifi file explorer. Anyone have any suggestions?

What do you think we can expect from kernels in the future?

The other day a friend of mine with the new Evo 3D told me that, even while the phone has a locked bootloader and no root, someone was able to overclock the phone to 1.8 Ghz...That's insane! It's 1.2 by default.
Ours is 1.0 of course, what do you think we could max it out at in the future, as more development happens on the phone down the road?
And for that matter, do you think we'd be able to see those "trickle" battery kernel things implemented at some point? I read about those some time ago and it seemed pretty awesome/great for battery life without being limited on usage.
What are some of your thoughts on our kernel-ish future?

Tegra 2 optimization with 1.5 ghz max overclock imo.
I'm not putting my phone past 1.2 though. 1.2 tegra results are 3300ish/2800ish on smartbench, and that's good enough for anything on android atm.
We just need a CM7 build on the atrix. Even if it's not too great. That'll attract a huge crowd to it and then we'll have an even more active dev community.

1.8ghz Evo3d is about equal with a 1.0ghz atrix lol
The Xoom Tegra 2's seem to be overclocking rather well.
1.5ghz looks like the sweet spot.

Magnetox said:
Tegra 2 optimization with 1.5 ghz max overclock imo.
I'm not putting my phone past 1.2 though. 1.2 tegra results are 3300ish/2800ish on smartbench, and that's good enough for anything on android atm.
We just need a CM7 build on the atrix. Even if it's not too great. That'll attract a huge crowd to it and then we'll have an even more active dev community.
Click to expand...
Click to collapse
well last night i asked aliasxerog on twitter how the port was going and he said, "I have a kernel in the oven as we speak" I can't wait

msd24200 said:
well last night i asked aliasxerog on twitter how the port was going and he said, "I have a kernel in the oven as we speak" I can't wait
Click to expand...
Click to collapse
Whoa whoa whoa hold the phone lol..who is this aliasxerog anyway??
@Kingkuba, what do you mean the 1.8 evo is the same as 1.0 atrix? Honestly I'm a n00b and I always seem to think "the more Ghz the better", which I know is stupid but I can't help it lol.

http://twitter.com/#!/aliasxerog
thebeardedchild said:
Whoa whoa whoa hold the phone lol..who is this aliasxerog anyway??
@Kingkuba, what do you mean the 1.8 evo is the same as 1.0 atrix? Honestly I'm a n00b and I always seem to think "the more Ghz the better", which I know is stupid but I can't help it lol.
Click to expand...
Click to collapse

msd24200 said:
http://twitter.com/#!/aliasxerog
Click to expand...
Click to collapse
Excellent. So is he one of the guys that had an Atrix Sent to him?
Sent from my Motorola Atrix using the XDA App

thebeardedchild said:
Excellent. So is he one of the guys that had an Atrix Sent to him?
Sent from my Motorola Atrix using the XDA App
Click to expand...
Click to collapse
Pretty sure, but hes def devving cm7 roms

Magnetox said:
Pretty sure, but hes def devving cm7 roms
Click to expand...
Click to collapse
Cool beans. I had no idea that they had any progress, especially this far along
Sent from my Motorola Atrix using the XDA App

thebeardedchild said:
Cool beans. I had no idea that they had any progress, especially this far along
Sent from my Motorola Atrix using the XDA App
Click to expand...
Click to collapse
I think he may be having trouble getting a bootable rom though. So hopefully it works out with his new kernel/magics. Read through his twitter a bit, some golden nugs in there

The moto XOOM, which has Tegra 2, is stable at 1.7 ghz
Sent from my MB860 using Tapatalk

How is cooling in the XOOM compared to the Atrix? I know my phone gets hot on the bottom at stock clock when doing processing-heavy tasks... I can't imagine 1.7ghz could be very good.

humjaba said:
How is cooling in the XOOM compared to the Atrix? I know my phone gets hot on the bottom at stock clock when doing processing-heavy tasks... I can't imagine 1.7ghz could be very good.
Click to expand...
Click to collapse
It all depends on the voltage.
Correct me if I'm wrong but I believe the clock doesn't affect the heat of the chip, only the voltage does (which can change with the clock, but doesn't have to). So you can have a 1.2 ghz cpu running at 6mv and a 1.0 ghz cpu running at 6mv and they will run at the same temps (if I'm correct).

He tweeted again
Sent from my MB860 using XDA Premium App

So it seems some of you guys think 1.5 will be the most we might be able to overclock? What would be the reasoning behind this? I mean I've seen a lot of phones, dual core and single core that get up to like 1.8...
Sent from my Motorola Atrix using the XDA App

humjaba said:
How is cooling in the XOOM compared to the Atrix? I know my phone gets hot on the bottom at stock clock when doing processing-heavy tasks... I can't imagine 1.7ghz could be very good.
Click to expand...
Click to collapse
I have my Xoom stable at 1.6ghz. From what I've read, that seems to be pretty standard, some unlucky soles have to settle for 1.4 (or even less) but there's also a decent number of lucky ones who have it running stably 1.7ghz.
I've had my Atrix for a month or so now, and being international, can't unlock the bootloader (yet). Can't wait to see some custom ROMs/kernels!!

thebeardedchild said:
So it seems some of you guys think 1.5 will be the most we might be able to overclock? What would be the reasoning behind this? I mean I've seen a lot of phones, dual core and single core that get up to like 1.8...
Sent from my Motorola Atrix using the XDA App
Click to expand...
Click to collapse
I say 1.5 is easy for us. Perhaps 1.7/1.8 can come at a later time, but I've seen Faux's kernel on the G2X for 1.5, and that just seems to be a sweet spot for Tegra2.

thebeardedchild said:
Whoa whoa whoa hold the phone lol..who is this aliasxerog anyway??
@Kingkuba, what do you mean the 1.8 evo is the same as 1.0 atrix? Honestly I'm a n00b and I always seem to think "the more Ghz the better", which I know is stupid but I can't help it lol.
Click to expand...
Click to collapse
The processor in the Atrix has 2 cores where as the EVO has 1.. that = moar powa!

ChumleyEX said:
The processor in the Atrix has 2 cores where as the EVO has 1.. that = moar powa!
Click to expand...
Click to collapse
The evo 3d is dual core though..
Edit: oh I see I accidentally said just evolution, sorry.
Sent from my Motorola Atrix using the XDA App

Been stuck at 1.1 for a while...

It's beginning to look like this phone won't go any higher than 1.1 Ghz for OC. Kind of disheartening..
Are there any other phones that have had similar barriers that could perhaps give some insight on to how our 1.1 barrier can be passed? I'm by no means a dev, but that doesn't mean I can't organize an effort! Perhaps a bounty is in order for this?

thebeardedchild said:
It's beginning to look like this phone won't go any higher than 1.1 Ghz for OC. Kind of disheartening..
Are there any other phones that have had similar barriers that could perhaps give some insight on to how our 1.1 barrier can be passed? I'm by no means a dev, but that doesn't mean I can't organize an effort! Perhaps a bounty is in order for this?
Click to expand...
Click to collapse
Dual coreeeeeee bro! Haha jk. Im sure Moto just doesn't want us having fun.
Sent from my MB860 using XDA Premium App

2.2 GHz in a phone is oh so slow
But yeah - the Optimus 2X can overclock to 1.5GHz. I'd love to see that!

blackalice said:
2.2 GHz in a phone is oh so slow
But yeah - the Optimus 2X can overclock to 1.5GHz. I'd love to see that!
Click to expand...
Click to collapse
Dual core doesn't mean you can stack the clock speeds like that. Each processor can still only process at 1.1.

bilbert said:
Dual core doesn't mean you can stack the clock speeds like that. Each processor can still only process at 1.1.
Click to expand...
Click to collapse
Lol yea it's funny how people don't understand that. A lot is lost with two processors because it is going back and forth.

BravoMotorola said:
Lol yea it's funny how people don't understand that. A lot is lost with two processors because it is going back and forth.
Click to expand...
Click to collapse
You're making fun of people but you're using the wrong terminology.......hmm.
The phone doesn't have two processors, it has two cores on one bus.
And plus, "a lot is lost with two processors because it is going back and forth." - LOL @ that statement

k4zyn said:
You're making fun of people but you're using the wrong terminology.......hmm.
The phone doesn't have two processors, it has two cores on one bus.
And plus, "a lot is lost with two processors because it is going back and forth." - LOL @ that statement
Click to expand...
Click to collapse
I think processors is an acceptable term for dual core chips...but I guess the politically correct term is dual core processor. Anyways, bickering about it is not helping.
Sent from my MB860 using XDA Premium App

paravorheim said:
I think processors is an acceptable term for dual core chips...but I guess the politically correct term is dual core processor. Anyways, bickering about it is not helping.
Sent from my MB860 using XDA Premium App
Click to expand...
Click to collapse
Really, I've never seen such a forum where no matter what the topic, everyone wastes time bickering about terminology, or rules or blah.
im trying to get people thinking about possible ways to break past this 1.1 barrier. Or to decide right now if its even possible!
Sent from my Motorola Atrix using the Premium XDA App

I think it would be best to just wait until the devs work on it instead of creating pointless posts like this one...
They have enough work on their hands with cm7 and right now is another 100mhz x 2 really going to make a diff at this point?? I personally would rather see a stable cm then worry about that. Another thing Id like to see on this forum is less whining and more encouraging posts (I came from a HTC Aria and am really starting to miss their community)
Sent from my MB860 using XDA App

I don't see why not. The XOOM can do it. But im sure Moto put up some road blocks.
Sent from the coolest voided warranty phone ever.

crossix said:
I think it would be best to just wait until the devs work on it instead of creating pointless posts like this one...
They have enough work on their hands with cm7 and right now is another 100mhz x 2 really going to make a diff at this point?? I personally would rather see a stable cm then worry about that. Another thing Id like to see on this forum is less whining and more encouraging posts (I came from a HTC Aria and am really starting to miss their community)
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
Yeah you're post isn't contributing well to this apparently poor community either. Like I said, if you haven't anything productive to say, gtfo. There's more to be done than to just wait for devs to magically do it. Us lowly non devs can still look into what can be done. What do you suggest we do in these forums if not to promote discussion of enhancements to our phone?
The point of this thread is to sort of take the pressure off the devs to figure it all out on their own.
If you're gonna wastes everyones time, we'd like you to kindly take your whining back to the aria forum or something..
Sent from my Motorola Atrix using the Premium XDA App

Whining stops now.
If you want to discuss getting a bounty together for overclocking beyond 1.1Ghz, by all means continue to do so.
Otherwise, this thread will be closed.

Heh hopefully if a mod says what I've been harping this whole time it sticks. Well, anyone think a bounty for this is worth it? Honestly, other dual core phones are almost to 2.0. If we're fast at 1.1 can you imagine more? I'm never content with where I'm at so I say we get this phone as high as it can.
That being said, one concern is that anything higher than 1.1 is physically impossible no matter how you cut it. Like I said other dual cores are oc'd high, but who knows how this thing is different!
The real question before bounty talks can be made is: can we determine if its possible? Were other phones in this situation?
I remember when faux initially discussed it, he made it sound like it was some simple code holding it back but I dunno really..
Sent from my Motorola Atrix using the Premium XDA App

In my coding experience(I do it for fun here and there) if it were simple code it probably could've been replaced by now unless it were hardware dependent... which it shouldnt be because there are other Tegra 2 phones well past 1.1ghz... which sorta just leaves me in a conundrum...
I was hoping this would be fixed in cm7 because it uses a different kernal and whatnot so we'd find a work around... but I guess not yet
It would probably help me to pm someone like faux or knoll who have worked with it first hand though.
Anyways lets hope for a breakthrough soon to show everyone else how much better our phones are from theirs
Sent from my MB860 using XDA App

whatsaqazza said:
In my coding experience(I do it for fun here and there) if it were simple code it probably could've been replaced by now unless it were hardware dependent... which it shouldnt be because there are other Tegra 2 phones well past 1.1ghz... which sorta just leaves me in a conundrum...
I was hoping this would be fixed in cm7 because it uses a different kernal and whatnot so we'd find a work around... but I guess not yet
It would probably help me to pm someone like faux or knoll who have worked with it first hand though.
Anyways lets hope for a breakthrough soon to show everyone else how much better our phones are from theirs
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
Those are good points. And yeah I probably worded that wrong, with the "simple line of code" thing, because now that you mention it that sounds TOO simple lol. I can't really remember what he said, but at the time it seemed less serious, as in 'the next version of my kernel would bypass it', ya know what I mean? But now here we are, still at 1.1. However, at the same time, the only guy really working on getting higher than 1.1 had halted his kernel progress to work on CM7, so I dunno. Perhaps a bounty would be good to get more devs in to take a look at it and see what to do.
And yeah it's a little reassuring to know that the Xoom did it, with essentially the same processor. Does anyone know if it had the same type of roadblock associated with it, where they couldn't OC much higher for a time?

From the little I've heard the xoom was able to oc to 1.5 without any kind of roadblocks(Idk about after that) but I've never rly heard of something like this for android phones from all the tech nerds I know haha... I think starting a bounty would be a good idea(and Id totally donate to something like that) but I also think once cm7 is stable they'll be more devs trying to fix this problem... who knows they might find something out by just tinkering with it on cm7
Sent from my MB860 using XDA App

whatsaqazza said:
From the little I've heard the xoom was able to oc to 1.5 without any kind of roadblocks(Idk about after that) but I've never rly heard of something like this for android phones from all the tech nerds I know haha... I think starting a bounty would be a good idea(and Id totally donate to something like that) but I also think once cm7 is stable they'll be more devs trying to fix this problem... who knows they might find something out by just tinkering with it on cm7
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
Yeah I'd be willing to donate as well, of course (a given, as I seem to be worrying about this too much anyways ).
I've wondered if, since faux announced that "barrier", if either him or anyone else has even attempted to look at what causes it. I'm not saying 'those lazy bastards!!!11!' or anything, but if that's the case I'd almost feel better since that explains why it hasn't been done yet. Otherwise, the longer they HAVE looked at it with no avail, the more likely it is we're stuck at 1.1
Maybe tinkering will help...I honestly thought it would help while they developed it in the first place, since like you said earlier, it seems like it's not a hardware thing so a new ROM could have helped...

Someone with coding knowledge should contact whoever made the xoom overclock.
Sent from my Atrix running CM7

Remember that a phone is essentially a small computer. It's not just the CPU which is involved. Memory timings, voltages, and cooling all play a huge part in OC'ing a CPU. This may be where the problem lies. If the phone requires memory timings which make it extremely unstable/unuseable at an OC higher than 1.1GHz, then it will always be a no go, no matter how you look at it. Similarily, if you have to step up the voltage, you induce more heat, and there is no active cooling in a phone.
In essence, there are many reasons why the OC may have stopped at 1.1GHz. It seems people really need to understand overclocking overall before commenting on what is and is not possible.
There is also the chance that nobody has really looked at this as important because all the work has gone into creating CM7, etc. I would say OC'ing past 1.1GHz is low on the totem pole for the few devs who are capable of doing it.

kholk claims to be releasing a 1.2 kernal today, I believe lt to be for testing to make sure it works but we shall see.
Sent from my Atrix running CM7