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
Related
I'm not new to overclocking, but I AM new to Android, so when it comes to overclocking an Android phone, I'm as useless as the next guy.
I noticed people got the i9000 version as well as the Captivate version to overclock to 1.2Ghz, but I can't find anything on the Fascinate. One member mentioned in another thread they overclocked, but I don't see how.
So how do we overclock the Fascinate? If there's a guide out there, it should be a sticky here!
Need overclocked kernels to achieve that, and we don't have any as of yet.
Gotta wait for custom kernels to start rolling out, which will be soon
Man you guys are sick.
The phone is at 1Ghz right now. Almost Twice the speed the original Motorola Droid. And you want to overclock already.
What kind of things are you doing with your phone that need that kind of speed. ..
smilepak said:
Man you guys are sick.
The phone is at 1Ghz right now. Almost Twice the speed the original Motorola Droid. And you want to overclock already.
What kind of things are you doing with your phone that need that kind of speed. ..
Click to expand...
Click to collapse
Why would you not want to overclock your phone?
Sent From My Galaxy S
actually its been said(but not done yet) that these phones can easily overclock to 1.6ghz so its only a matter of time, this will eventually be one of the more popular galaxy s phones bc its on vzw which is prolly the largest network in the world if not very close. cant wait for this ****. i really dont know if vzw is that big but u would think it is
ksizzle9 said:
actually its been said(but not done yet) that these phones can easily overclock to 1.6ghz so its only a matter of time, this will eventually be one of the more popular galaxy s phones bc its on vzw which is prolly the largest network in the world if not very close. cant wait for this ****. i really dont know if vzw is that big but u would think it is
Click to expand...
Click to collapse
Seriously? 1.6ghz? Where did these numbers come from just wondering? Not that I don't believe you just skeptical. If those facts are true that's freaking awesome!
u can go to the irc chat for the i9000(international SGS) Or prolly find it n xda under i9000 I know its been said it can be done but hasn't been yet. This isn't like the Snapdragon or Dx, D2 processors that are basically maxed out at 1ghz. I don't know any specifics bit I believe it. Hit the forums and chatrooms. If I'm wrong my bad. But I know its been said at some point that this processor is capable. If u ask or find it post back with any recent info.
they call me...kick ass
http://www.intomobile.com/2010/08/1...ck-hits-1-2ghz-delivers-off-chart-benchmarks/
I can't wait for stuff like this to start coming out
My phone made words....
ksizzle9 said:
actually its been said(but not done yet) that these phones can easily overclock to 1.6ghz so its only a matter of time, this will eventually be one of the more popular galaxy s phones bc its on vzw which is prolly the largest network in the world if not very close. cant wait for this ****. i really dont know if vzw is that big but u would think it is
Click to expand...
Click to collapse
oh yes they can mine was for a bit i went back down to 1.2 though
lordmalice said:
oh yes they can mine was for a bit i went back down to 1.2 though
Click to expand...
Click to collapse
No, they cannot.
Sent from my SCH-I500 using XDA App
1.6 ghz = Fast as hell FOR 10 Mins then kaput
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?
Is it just me or is Epic development almost dead?
Two-three months ago there was CM6,MIUI,CM7 and more original roms in the works,what happened?
Yeah i know that for CM7 they are waiting for official GB to drop but what about CM6 that was 90 percent finished and MIUI that was almost finished?
I know that we still got roms but most of them with exception of ACS and few others are mostly remixes and tweaks of stock rom.
Our Epic is way behind Vibrant,Fascinate and Captivate.
It's just you. Don't knock what the amazing developers have done for us. We have plenty of roms and we will have plenty once gingerbread drops.
I agree. Feel free to learn how to dev, though. You won't sound like a detractor from the forum.
lviv73 said:
Is it just me or is Epic development almost dead?
Two-three months ago there was CM6,MIUI,CM7 and more original roms in the works,what happened?
Yeah i know that for CM7 they are waiting for official GB to drop but what about CM6 that was 90 percent finished and MIUI that was almost finished?
I know that we still got roms but most of them with exception of ACS and few others are mostly remixes and tweaks of stock rom.
Our Epic is way behind Vibrant,Fascinate and Captivate.
Click to expand...
Click to collapse
dont worry op. i feel for ya.
no disrespect, but what phones did you guys come from. i went through the mogul, the touch, touch pro and then tp2. i mean we had a **** ton of development. not all of it was quality, but i mean, real talk. epic dev just never got off the ground. im totally not ungrateful, and im still learning android and linux, and im going to kick a little ass one of these days. it just wont be with this phone.
like i said. im not a **** talker. look me up at ppcgeeks. ive got 3000 posts (6 thou if you count off topic) and a rep that doubles that.
I know the feeling I see so much stuff from may it makes it hard not to switch phones only thing keeping me around is hope at this point
Sent from my SPH-D700 using XDA Premium App
inimitableac said:
I know the feeling I see so much stuff from may it makes it hard not to switch phones only thing keeping me around is hope at this point
Sent from my SPH-D700 using XDA Premium App
Click to expand...
Click to collapse
the only thing keeping me around is sprint not dropping an evoesque phone with a keyboard. all my favorite devs went to the desire z and the evo.
austin420 said:
the only thing keeping me around is sprint not dropping an evoesque phone with a keyboard. all my favorite devs went to the desire z and the evo.
Click to expand...
Click to collapse
Yep... that and unlimited data... wish htc made a qwerty slider for android.. ill never give up my full kb.
Sent from my SPH-D700 using XDA Premium App
austin420 said:
dont worry op. i feel for ya.
no disrespect, but what phones did you guys come from. i went through the mogul, the touch, touch pro and then tp2. i mean we had a **** ton of development. not all of it was quality, but i mean, real talk. epic dev just never got off the ground. im totally not ungrateful, and im still learning android and linux, and im going to kick a little ass one of these days. it just wont be with this phone.
like i said. im not a **** talker. look me up at ppcgeeks. ive got 3000 posts (6 thou if you count off topic) and a rep that doubles that.
Click to expand...
Click to collapse
Damn, I just hit 1,000 posts over there. Big part of it seeming smaller is that the only carrier with the Epic is sprint. Android roms aren't like winmo roms where all you had to do was provision a rom to a particular carrier.
lazydazed said:
Yep... that and unlimited data... wish htc made a qwerty slider for android.. ill never give up my full kb.
Sent from my SPH-D700 using XDA Premium App
Click to expand...
Click to collapse
they do... its called the evo shift...
steviee7 said:
they do... its called the evo shift...
Click to expand...
Click to collapse
i know im picky, but i like 5 rows (dedicated number row)
i just dont want to leave sprint either. its not just the unlimited data, low prices and yearly upgrade. i just like them. i live in kc mo. right across the state line from sprint worl headquarters. we have a 18000 person arena in downtown called the sprint center. sprint logos are every where. we have the sprint cu at the kansas speedway. i mean it is my home town carrier.
shane6374 said:
Big part of it seeming smaller is that the only carrier with the Epic is sprint. Android roms aren't like winmo roms where all you had to do was provision a rom to a particular carrier.
Click to expand...
Click to collapse
good point
i got more thanks tomorrow.
This is my first experience with custom ROMs and I for one am very content with the amount of development for the Epic. I have looked at other forums and yes there may be a larger following, or more talk about development, but a lot of it seems to be garbage. I have flashed and used a few different ROMs now and they are all solid with few if any bugs. SRF is what I am running now and I have not found a single functionality issue. I also love that the Epic devs continue to improve their product instead of releasing some piece of crap ROM and never touching it again. Also the relatively smaller quantity of development makes things like qbking's videos possible and help all of us learn to better utilize the phones potential.
I say cheers to the devs for what they do and the time they put in! I could never accomplish even a portion of what they do. Thanks guys!
Please excuse any erors or typos as this massage was sent from my mobil device.
Xiutehcuhtli said:
This is my first experience with custom ROMs and I for one am very content with the amount of development for the Epic. I have looked at other forums and yes there may be a larger following, or more talk about development, but a lot of it seems to be garbage. I have flashed and used a few different ROMs now and they are all solid with few if any bugs. SRF is what I am running now and I have not found a single functionality issue. I also love that the Epic devs continue to improve their product instead of releasing some piece of crap ROM and never touching it again. Also the relatively smaller quantity of development makes things like qbking's videos possible and help all of us learn to better utilize the phones potential.
I say cheers to the devs for what they do and the time they put in! I could never accomplish even a portion of what they do. Thanks guys!
Please excuse any erors or typos as this massage was sent from my mobil device.
Click to expand...
Click to collapse
This.
Quality over quantity anyday our devs cook up some amazing stuff for us.
Sent from my SPH-D700
I love this phone. That is all.
Sent from Godot's place.
we have several quality ROMs and Themes to choose from
It should come as no surprise really. There are 3 main reasons why it may seem development is slow:
Small community. Meaning that our sample set in which developers are drawn is smaller. Thankfully, this phone was top notch in hardware when it came out, so it increased our chances of having very talented developers since it naturally drew people who seriously appreciated hardware. Hence, why we have a small number of developers but they're all very very good at what they do. It could have ended up with a small number AND not a lot of quality.
Touchwiz. What I mean by this is that we're still waiting on a fully functional AOSP based rom, with CM7 being the closest to completion. Without it, all there is to develop on is touchwiz, and we've pretty much exhausted what we can do with it (so far). Once there's one ROM on AOSP, that allows for more ROMs to be developed on AOSP. Plus, the completion of CM7 could very well attract developers who prefer to develop on AOSP to try a couple projects, and have simply been waiting for CM to be completed. This all ties in with reason number 3.
Froyo. Like touchwiz, we've pretty much done all we can do with it. With the release of gingerbread, it'll open up a whole new opportunity to develop. Remember, we went through the same thing towards the end of eclair's life. Not a whole lot of development, and everyone really just waiting for froyo. The difference was, however, that everyone was itching SO BAD for froyo that a lot of projects were done on DK28; we were truly behind the times then, and so even the developers were willing to play with a leak. Not so much now; we're not AS behind the curve considering there are still few phones (besides newly released ones) on gingerbread. This, too, is much like the anticipation of an AOSP precedent as mentioned previously: it's quite possible that there are potential developers who are simply waiting for gingerbread to be released before coming to this phone.
Sent from my SPH-D700 using XDA Premium App
can anyone explain to me how the mytouch slide 4g has cm7 and overclocked gingerbread kernels with out gb source?
austin420 said:
can anyone explain to me how the mytouch slide 4g has cm7 and overclocked gingerbread kernels with out gb source?
Click to expand...
Click to collapse
I don't know, but the easiest explanations are:
More developers? Better chance to figure out the kernel drivers on their own.
It's made by HTC? It's pretty much a known that samsungs kernel drivers are always wacky, and in general, what one phone has doesn't neccessarily help with another. With HTC, their kernel drivers are a little more consistent across phones and it's easier to make things work by borrowing and tweaking.
Linux loaded modules? Don't know if it's relevant, but it's possible to use these to overclock a phone in a round-about way.
There's something that really needs to be laid to rest here regarding the arguement that everybody gives saying "we didn't get cm6 when froyo source was released, so how are we gonna get cm7 just because of gingerbread source?" Two reasons:
One: we only had one dev working on it, noobnl. Now we have a TEAM. And each on is just as if not more talented than him.
Two: we didn't have another device to kang any AOSP driver source from. With cm7, our team borrowed what they could from the nexus s 4g. And rest assured, they DID get a little use out of it.
Sent from my SPH-D700 using XDA Premium App
austin420 said:
can anyone explain to me how the mytouch slide 4g has cm7 and overclocked gingerbread kernels with out gb source?
Click to expand...
Click to collapse
It's the same phone as every other HTC phone, once they get something working on one all the others get it pretty quickly.
063_XOBX said:
It's the same phone as every other HTC phone, once they get something working on one all the others get it pretty quickly.
Click to expand...
Click to collapse
then by the same logic, since the i9000 has gb, we should too? the only difference in the mytouch4g and most other htc phones is a keyboard and 4g. sound familiar?
First, let my apologize if I posted this in the wrong place. I am new and just rooted my epic 4G today for the first time with my friend's help.
I have CM7 and was trying to overclock my phone to see how fast it would go, most of what I've tried has only let my set it to 1000. My friend tells me if I can find something called "Titmat 2.6" it should let me boost to up to 2000. Google keeps telling me it's called Tiamat, but I see titmat used for the Evo 3D. It just so happens, that's my friend's phone aswell. Is there a copy of Titmat for my Epic 4G (non touch) that someone might be able to provide a link to? Or if not, is there another kernel you recommend for my phone? Any help would be appreciated. Again, I apologize for my newbness. :\
What you need is one of the cm7 kernels from over in development section. Shadow and Samurai are good. Then get voltage control from the market to over clock. You aren't going to get 2000 though. Samurai is 1500 I think and shadow is 1400.
Tiamat is a kernel for another phone.
Sent from my SPH-D700 using Tapatalk
You nor your friend should be overclocking. You both seem way to uneducated in it all and don't understand what you are actually doing, the negative effects, the way CPUs work, and the difference between phones. Overclocking is dangerous stuff...
Sent from my SPH-D700 using Tapatalk
marcusant said:
You nor your friend should be overclocking. You both seem way to uneducated in it all and don't understand what you are actually doing, the negative effects, the way CPUs work, and the difference between phones. Overclocking is dangerous stuff...
Sent from my SPH-D700 using Tapatalk
Click to expand...
Click to collapse
Damn marcusant lmfao don't discourage the people actually willing to learn...
But like marcusant said, its only for the evo 3d. Our phones use a different method to overclock.
If you take a stroll down to the epic 4g development section, you should see things like "cm7 kernel" in the title. Read each thread and see which kernel you like. Afterwards, just download voltage control from the marketplace and you should be able to overclock your phone
Most epics are stable upto 1.2Ghz, but some get lucky and are actually able to overclock to 1.4 and 1.5 with no ill side effects (I'm one of them )
Now, when you overclock, you're working it more than it was designed to. Fortunately, we have easily the best single core mobile processor out there right now on a mobile phone, so it can take it. However you also give it more power to run at these higher speeds so it heats up faster...and we all know what happens when silicon gets heated BUT with voltage control you can do something called "undervolting" which lowers the voltage-per-clockspeed aspect so to say. Its usually safe to undervolt by 50mV without any ill effects, but as with overclocking, some people can undervolt EVERY clock by 100mV or so (I'm not one of them.. ) I do not recommend attempting to undervolt unless you understand the risk/reward ratio fully. If you undervolt too much your phone will become corrupted, but if you do it one step at a time your phone will be super fast AND on a power diet
I recommend the shadow kernel. I haven't been on cm7 since cm9 dropped, but shadow kernel usually worked best for me.
If you have any questions I'll gladly help I will also be quick to note if a simple little search would've answered your question in a very condescending way. Fortunately your post is legit
Sent from my SPH-D700 using XDA Premium App
Marcusant is correct. Overclocking is not for the light hearted or newbies. It can damage your phone, make it unuseable if you do not know what you are doing or how to recover it. It is like adding a nitrous kit on a motorcycle for a new rider.
kennyglass123 said:
Marcusant is correct. Overclocking is not for the light hearted or newbies. It can damage your phone, make it unuseable if you do not know what you are doing or how to recover it. It is like adding a nitrous kit on a motorcycle for a new rider.
Click to expand...
Click to collapse
LOL isn't that why we're here to HELP?
Sent from my SPH-D700 using xda premium
Or is it just me?
Sent from my SPH-D700 using xda premium
A_Flying_Fox said:
LOL isn't that why we're here to HELP?
Sent from my SPH-D700 using xda premium
Click to expand...
Click to collapse
I don't mind helping people root their phone or with problems installing or running ROMs but I do not encourage overclocking period. You know I am always here to help Fox.
Sent from my SPH-D700 using xda premium
kennyglass123 said:
I don't mind helping people root their phone or with problems installing or running ROMs but I do not encourage overclocking period. You know I am always here to help Fox.
Sent from my SPH-D700 using xda premium
Click to expand...
Click to collapse
When have you ever not helped?
IMO and purely my opinion its not as dangerous as most think to be I've ran my processor to the ground and its still chuggin can't be healthy playing n64oid at 1.5/1.5 for 2 hours straight . I've yet to hear of anyone frying these hummingbird processors..correct me if I'm wrong...anyways hopefully this doesn't start an argument please pm me if you want to "discuss" this.
Sent From My SPH-D700 Running Android 4.0 :sly:
Samurai has a oc/uv apk with it. I am a noob when it comes to that stuff. but I keep mine about 800 because I don't use my phone at work. I only o/c when I am showing off my phone.
I never discourage learning. If someone understands the risk and likes to learn, they'll most likely learn something from that. Do we even have any confirmed reports of the epic bricking from overclocking?
Having said that, am I the only one who feels the phone works snappy enough w/o overclocking?
iil said:
I never discourage learning. If someone understands the risk and likes to learn, they'll most likely learn something from that. Do we even have any confirmed reports of the epic bricking from overclocking?
Having said that, am I the only one who feels the phone works snappy enough w/o overclocking?
Click to expand...
Click to collapse
No I agree its fast as is. I only overclock to play games on it or when I feel its not fast enough browsing the web
Sent From My SPH-D700 Running Android 4.0 :sly:
iil said:
I never discourage learning. If someone understands the risk and likes to learn, they'll most likely learn something from that. Do we even have any confirmed reports of the epic bricking from overclocking?
Having said that, am I the only one who feels the phone works snappy enough w/o overclocking?
Click to expand...
Click to collapse
I think this kind of went off point. Yes the phone is totally snappy enough with OC. The point was the OP came here looking for something that is not for this phone to push the speed to 2Ghz because someone else told him about it. It wasn't a question about teaching them to overclock it is more an issue to teach him to research before flashing a kernel for a different phone.
Sent from my SPH-D700 using xda premium
Wow..
Thanks for the advice guys. So my friend made me look like a jackass. It was Tiamat. Yeah, I understand that's just a special Kernal for his Evo 3D. I'm gonna look into Samurai and Shadow. I haven't read anything about any fatal damage from overclocking. Correct me if I'm wrong, but the phone just gets hotter and the battery dies faster. (correct me if I'm wrong) I have plenty of extra batteries because before EI22 my phones battery life was about 4 hours, without using it. So glad they patched that.
My $0.02...
1. Never heard of a hardbrick from overclocking with Hummingbird, phones will turn off and reboot before they get that hot. Most that would happen is data corruption, which is nothing a little Odin won't fix.
2. I would never use the titmat if that was what it was really called.
Sent from my SPH-D700 using Tapatalk
I think he means Tiamot not titmat lol. But the epic will be faster than the evo 3d no matter what your friend overclocks it to. I used an evo 3d about a month ago and it was slow as hell and the screen sucked. The 3d isn't even 3d.
Sent from my SPH-D700 using Tapatalk
samurai is dead for playing nice with other people's gpl code.
Titmat? in for pics.
I'm down with the titmat!
Sent from my SPH-D700 using XDA App
Titmat? Sounds like a prank.
At this point, things that don't work are the things I need to work. Nothing has changed for nearly two months now, so I'm just curious.
the impatience and greed around here is unbelievable...
if you want something to be fully working and perfect, you gotta make it yourself. plus rushing things isn't gonna do any good at all. it will come, just be patient... be glad we even have a Sense 4 ROM...
Dude, seriously, it was a question. That's it. Not a complaint, not impatience, and not greed. The assumptions of others on this forum is what is really unbelievable. I knew that some joker would answer back like that.
Saranhai is part of the team that brings a lot of ROM's to this device. He is probably a little frustrated that it seems like is never good enough, or fast enough for people. Your question may have been honest and purely innocent, but with the way things have been around here lately his reaction is somewhat understandable.
Several devs are hard at work on sense 4 kernels and the camera. When they have a usable fix, it will be released. If you want to add to their resolve you could always donate
Don_Perrignon said:
Dude, seriously, it was a question. That's it. Not a complaint, not impatience, and not greed. The assumptions of others on this forum is what is really unbelievable. I knew that some joker would answer back like that.
Click to expand...
Click to collapse
I'm patiently waiting too. And so you know, I'm posting this in a good mood, not frustrated or being smart. But from what I understand is its basically at a standstill until devs can get the necassary kernel to get the camera working. It's not that they are being slow..they simply don't have what's needed to accomplish it. And I may be entirely wrong..that's just what I have been thinking.
Sent from my HTC Glacier
Don_Perrignon said:
Dude, seriously, it was a question. That's it. Not a complaint, not impatience, and not greed. The assumptions of others on this forum is what is really unbelievable. I knew that some joker would answer back like that.
Click to expand...
Click to collapse
Well maybe you should've worded it better than instead of sounding like a selfish idiot... Anyway sorry for "assuming"
Sent from my Infernalized Glacier
jjbadd385 said:
I'm patiently waiting too. And so you know, I'm posting this in a good mood, not frustrated or being smart. But from what I understand is its basically at a standstill until devs can get the necassary kernel to get the camera working. It's not that they are being slow..they simply don't have what's needed to accomplish it. And I may be entirely wrong..that's just what I have been thinking.
Sent from my HTC Glacier
Click to expand...
Click to collapse
Okay. I understand, not saying anybody is being slow. I just wanted to know what the issue was. It's crazy that Sense seems to be the most troublesome UI.
saranhai said:
Well maybe you should've worded it better than instead of sounding like a selfish idiot... Anyway sorry for "assuming"
Sent from my Infernalized Glacier
Click to expand...
Click to collapse
Take it at face value MF. It's my fault that you put your own thoughts into a simple question? Seriously, it's all too common on XDA for people to needlessly attack others on the basis that people are too sensitive.
See the answer that JJ gave? That's all that we needed. I wanted to know the issues the devs were facing? If anything I was concerned, because I've never seen something give this kind of trouble on this phone. We all appreciate the works that devs do. We all act like kids in a candy store for the work that devs do.
Team Inferno member ...Awesome... is releasing a One S port. Yes, One S. Hope that fits your needs (besides camera )
Don_Perrignon said:
At this point, things that don't work are the things I need to work. Nothing has changed for nearly two months now, so I'm just curious.
Click to expand...
Click to collapse
if you did any searching youd know it all depends on when HTC releases the 3.0 kernel and we can get some kernel devs to port it to our devices..
did you really need a thread to ask for an ETA on something thats not even meant for our phone? cmon son lol
I too am impatiently waiting for a upgrade
TO A ROM I DIDN'T MAKE FROM PEOPLE I DIDN'T PAY [AND YET i DEMAND MY RIGHTS] "WHAT A SNOB"
trofmoc said:
TO A ROM I DIDN'T MAKE FROM PEOPLE I DIDN'T PAY [AND YET i DEMAND MY RIGHTS] "WHAT A SNOB"
Click to expand...
Click to collapse
Couldn't have summed it up better myself
trofmoc said:
TO A ROM I DIDN'T MAKE FROM PEOPLE I DIDN'T PAY [AND YET i DEMAND MY RIGHTS] "WHAT A SNOB"
Click to expand...
Click to collapse
You just summed up my thoughts to the OP and this thread...
Sent from my Infernalized Glacier
trofmoc said:
TO A ROM I DIDN'T MAKE FROM PEOPLE I DIDN'T PAY [AND YET i DEMAND MY RIGHTS] "WHAT A SNOB"
Click to expand...
Click to collapse
Who the **** is demanding? It was a question wanting to the the issue the devs where facing.
Oooh i think this is gonna come to a close soon. Enough fighting
Sent from my HTC Glacier
I like cereal.
That is all.
People should stop getting butthurt so easily.
I2IEAILiiTY said:
I like cereal.
That is all.
Click to expand...
Click to collapse
No way! Me too
Sent from my HTC Glacier
I think it got a little hot outside to the point it heated everything, even in the internet.... xD
The issue is that there's no HTC official kernel source for any "sister" devices - DHD/DS, and they didn't get the HTC ICS update either. Without the kernel source, devs have to use kernel source from other, less compatible devices to compile the kernel, and the binary drivers from those devices don't match the HW. There are no skilled enough and/or willing enough devs to dig in the kernel code and rewrite the API towards the drivers to match the older, working drivers from Gingerbread (that's what was done back in Gingerbread release time), mostly because it's a huge work that brings almost no benefits - the official code is likely to be better anyway, and its release will most likely be closer to this point in time than the shortest time required for "enthusiast" work.
Jack_R1 said:
The issue is that there's no HTC official kernel source for any "sister" devices - DHD/DS, and they didn't get the HTC ICS update either. Without the kernel source, devs have to use kernel source from other, less compatible devices to compile the kernel, and the binary drivers from those devices don't match the HW. There are no skilled enough and/or willing enough devs to dig in the kernel code and rewrite the API towards the drivers to match the older, working drivers from Gingerbread (that's what was done back in Gingerbread release time), mostly because it's a huge work that brings almost no benefits - the official code is likely to be better anyway, and its release will most likely be closer to this point in time than the shortest time required for "enthusiast" work.
Click to expand...
Click to collapse
I think in layman terms, that means if someone attempted to rewrite source code to match the h/w in the Glacier, by the time they would finish, better & more compatible code would be here anyway. So its best, at this point, to just wait patiently?
Sent from my HTC Glacier