Related
Vogue GPU overclock
Changes that were made can be found here
That's a MSM7k device, we have a MSM7kA device which has a slightly higher stock GPU clock at 256mhz(actually the driver lists it at 128mhz, lol wtf) compared to the non A devices 128mhz(downclocked to 100mhz).
Chances of a few small edits gettings this to work? likely.
dzo said:
The GPU in the 7x00A is very similar to the one in the 7x00 so it should be possible but you will need to talk to your kernel devs to add this functionality.
Click to expand...
Click to collapse
I'll tinker around but I would love multiple people on this
EDIT: Whoops, wrong forum. Can a MOD move this to Development?
Holy...
Why even buy an EVO? This, plus AOSP, plus overclock CPU.... Then we'll undervolt it (which I'm surprised hasn't happened yet given that the EVO already has undervolted ROMS).... I love my Hero and I love this community
where do we get this and how do we apply it. Good work on this find decadence
Im looking into this right now.. But im so tired its not even funny. This will give me something to do with my time off tomorrow.
Ill compile a kernel with it undervolted as well and see how well it works when booted. I think i actually have one somewhere on my linux boot up.
anything further on this?
Jus10o said:
Im looking into this right now.. But im so tired its not even funny. This will give me something to do with my time off tomorrow.
Ill compile a kernel with it undervolted as well and see how well it works when booted. I think i actually have one somewhere on my linux boot up.
Click to expand...
Click to collapse
If anything, can you try and get the undervolt first? It would be nice to have more battery life before killing it all on an OC GPU xD But I'm glad to know that it shouldn't be too hard
mrinehart93 said:
If anything, can you try and get the undervolt first? It would be nice to have more battery life before killing it all on an OC GPU xD But I'm glad to know that it shouldn't be too hard
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=6885956&postcount=1041
darchstar said:
http://forum.xda-developers.com/showpost.php?p=6885956&postcount=1041
Click to expand...
Click to collapse
YES!!!! I'm going to try this ASAP. Is it a flashable zip or no? And does the cpu still scale (can OC)? Sorry Im tired haha.
Edit
nvm that. I just flashed it, and according to uname -a, it is #15 like you said. So far, the boot's fine. Any way I can check the undervolt is working?
Aaaaaaaand she booted xD Nice work Darch!
I'm very excited by this prospect. Like had been said, why buy an evo, especially when it's capped at 30 fps. I bet we get close to 40 with this!
-------------------------------------
Sent via the XDA Tapatalk App
This would be something I would be willing to donate for if it has any chance of working successfully
I am getting 21.7 FPS with this kernel. But I am not sure that he has done a whole lot to it to make it go Zoom Zoom.
so i flashed this over buufed 2.0b, hopefully it works i'll let you know results
well i flashed and booted up fine,
while running this for 10 minutes my battery took a **** on itself, dropping 6% in under 10 minutes of extremely light use. gahhhhhhhh
Sent from my HERO200 using the XDA mobile application powered by Tapatalk
Im guessing everyone is talking about what Darch posted??
yupp, my battery somewhat stablized but i havent noticed much of an increase, :/ meh
Yeah, how about back on topic here. Lol although I love the under volt. Lol. But any of you brilliant kernel guys try the gpu part yet?
-------------------------------------
Sent via the XDA Tapatalk App
Ok well I figured where our driver identifies the clock settings:
But i'm not sure where the settings come from?
http://github.com/darchstar/CdMa-HeRoC-2.6.29/blob/master/drivers/video/msm/gpu/kgsl/kgsl.c
Line 130:
Code:
static void kgsl_clk_enable(void)
{
clk_set_rate(kgsl_driver.ebi1_clk, 128000000);
clk_enable(kgsl_driver.imem_clk);
clk_enable(kgsl_driver.grp_clk);
#ifdef CONFIG_ARCH_MSM7227
clk_enable(kgsl_driver.grp_pclk);
#endif
}
Then kgsl.h would contain the struct for this: http://github.com/darchstar/CdMa-HeRoC-2.6.29/blob/master/drivers/video/msm/gpu/kgsl/kgsl.h
If I'm not mistaken.
So who do i need to beg to make this happen?!
beyondinferno said:
So who do i need to beg to make this happen?!
Click to expand...
Click to collapse
I think at this point Darch is the only one left who can do something of this magnitude.
abcdfv said:
I think at this point Darch is the only one left who can do something of this magnitude.
Click to expand...
Click to collapse
I dont think darch could do it.. He is smart and can figure a lot out. But we would either have to do a lot of trial and error or get toasts to look into it. He still does small work on the hero and im sure what he learns from the hero he could implement it to the Evo.
Latency decreased from like 540 ms to 65ms and data speeds spiked from like 2 mb/s to about 4.6 mbits per second now.
I flashed ka6 OVER NEROV5 AND IT IS AWESOME.
Just to forewarn you. You'll get a message about the titles of this thread.
But any other enhancements to this ROM?
the rom has alot of elements from gingerbread and nexus s phone and gingerbread multitouch keyboard.
What are these...elements of Gingerbread you speak of? You're the first person to say anything about the build..
I think he thought you were talking about Nero.
I didn't like it, was getting slower data speed on this one.. so flashed back to ka5
just a ququestion.. i never noticed this till like now, the back of my phone is hot, i just checked and it's 106 degrees.. is that normal? I'm not charging right now, just listening to music and browsing the web, is it because of the leaked firmware?
That's 41'C right? Even so, that's pretty hot.
presence06 said:
That's 41'C right? Even so, that's pretty hot.
Click to expand...
Click to collapse
The phone is having a fever. Nothing serious. Just reboot and it will be much happier.
presence06 said:
That's 41'C right? Even so, that's pretty hot.
Click to expand...
Click to collapse
I know right.. coz i hardly not have the case on it so i never really noticed, after flashing the new leaked rom then flashed back, i haven't put the case on and just noticed how hot it is..
Do I flash back to j16? Maybe I should, or do I even have to worry at all?
swehes said:
The phone is having a fever. Nothing serious. Just reboot and it will be much happier.
Click to expand...
Click to collapse
Will do that.. thanks
I'd keep an eye on it and see if it happens again or continues to stay hot.
presence06 said:
That's 41'C right? Even so, that's pretty hot.
Click to expand...
Click to collapse
that's not too bad. i'm pretty sure i've seen mine get in excess of 50*C (according to setcpu widget) with no problems.
Ms_Vibrant said:
I didn't like it, was getting slower data speed on this one.. so flashed back to ka5
just a ququestion.. i never noticed this till like now, the back of my phone is hot, i just checked and it's 106 degrees.. is that normal? I'm not charging right now, just listening to music and browsing the web, is it because of the leaked firmware?
Click to expand...
Click to collapse
Try replacing the water pump
Sent from my SGH-T959 using XDA App
That's why I run nitrogen cooling.
It just needs more cowbell.
KA6
Really, doesn't everything need more cowbell?
KA6: I have been using it since it was released. It is nice. Better GPS than the previous releases. I do wonder why its not giving a faster quadrant score. I think it's RFS and the absence of a JIT compiler. Why can't Samsung just change to EXT 4? I'm not an expert by any means but the lag fixes use EXT 4. I know Quadrant is not an end-all-be-all test, but why would the Nexus one be putting out big numbers on older hardware?
briaking said:
Really, doesn't everything need more cowbell?
KA6: I have been using it since it was released. It is nice. Better GPS than the previous releases. I do wonder why its not giving a faster quadrant score. I think it's RFS and the absence of a JIT compiler. Why can't Samsung just change to EXT 4? I'm not an expert by any means but the lag fixes use EXT 4. I know Quadrant is not an end-all-be-all test, but why would the Nexus one be putting out big numbers on older hardware?
Click to expand...
Click to collapse
Absence of a JIT compiler? I thought THAT was a feature added in Froyo.
Who said this build didn't have a JIT compiler? It runs 13-14 Linpack scores just like every other SGS Froyo build. The compiler is not optimized for our processor, so you don't get the N1 type of scores. Gingerbread is optimized, which is the reason for the giant leap in stock Quadrant (ext 4 helps too). Patiently waiting for Krylon to work the bugs out of GB
Just went from a noob to a super duper updated vibrant, now running KA6 with Voodo kernel lagfix
Trying to locate bc's 1.8 oc kernel with no luck. Can someone point me in the right direction please?
Sent from my Evo Shift.
Apologies if this is posted in the wrong area...
Sent from my Evo Shift.
http://www.thebcblends.com/shift/
There's a few different kernels in there. Look at the file names. GB is for Gingerbread roms, AOSP for AOSP roms, Sense... well that's obvious.
Don't feel bad, I don't believe it was ever posted.
Sent from my HTC Speedy
Edit: fixed the link.
Thanks. Felt totally retarded not being able to find it.
Sent from my Evo Shift.
Now for a second question. When flashing this kernel, is it necessary to flash the 1.5 kernel before hand? I think I read somewhere that it is suggested but don't remember any confirmation on this matter. Also, any suggestions for roms?
Sent from my Evo Shift.
bobtsunam said:
Now for a second question. When flashing this kernel, is it necessary to flash the 1.5 kernel before hand? I think I read somewhere that it is suggested but don't remember any confirmation on this matter. Also, any suggestions for roms?
Sent from my Evo Shift.
Click to expand...
Click to collapse
I don't know the answer to that but..
Also when flashing a new kernel don't forget to clear your delvik cache.
bobtsunam said:
Now for a second question. When flashing this kernel, is it necessary to flash the 1.5 kernel before hand? I think I read somewhere that it is suggested but don't remember any confirmation on this matter. Also, any suggestions for roms?
Sent from my Evo Shift.
Click to expand...
Click to collapse
Someone had posted that just flashing the 1.8 kept giving them a boot loop and when they flashed 1.5 to 1.8 it worked fine
Edit: Pg11 on the kernel topic posted is where they discuss this
Sent from my PG06100 using XDA App
kbrn said:
I don't know the answer to that but..
Also when flashing a new kernel don't forget to clear your delvik cache.
Click to expand...
Click to collapse
Would not clearing delvik cache cause random reboot? I don't remember doing it so I'm guessing I didn't. I have the 1.5 kernel flashed now and when I had it maxed out it rebooted once while I was trying to post earlier through the xda app. I have it set to 1.4 now and haven't had a problem. Could this be the max my processor can handle? Should I even give the 1.8 kernel a chance given the reboot issue? Thanks to everyone who is helping.
Sent from my Evo Shift.
You could wipe dalvik and flash the 1.8..I personally wouldn't set my max to 1.8 just cause I had problems overheating and a few reboots but you could try something in the 1.5-1.7 range and see how that goes...then again I over heated trying to get higher linpacks and ended up just over 65
Sent from my PG06100 using XDA App
I will give it a try and see what happens. At least I have nandroid to fall back on if all else fails. How about ROMs? Does anyone have any suggestions? I came from a Moto Cliq and was using ADLX's ROM (I think 2.1) and loved what he did for the phone. Definitely like using Launcher Pro but am growing partial to Sense. Opinions and suggestion openly welcomed. Will prolly try a few before I settle. I am definitley anxious to try Gingerbread but have heard that it may be skipped over for alot of phones in favor of Honeycomb?...
JKILO said:
You could wipe dalvik and flash the 1.8..I personally wouldn't set my max to 1.8 just cause I had problems overheating and a few reboots but you could try something in the 1.5-1.7 range and see how that goes...then again I over heated trying to get higher linpacks and ended up just over 65
Sent from my PG06100 using XDA App
Click to expand...
Click to collapse
Dont't feel bad, I'm sure there'll be quite a few more users that can't make it that high.
@OP - I helped somebody in the IRC who got bootloops even when wiping cache and dalvik cache. Ultimately the only thing the worked for him was to flash the 1.5 then the 1.8. Every user will, sadly, have a slightly different experience.
Sent from my HTC Speedy
Will be giving it a go after I get home. Work is such a burden when you have more fascinating things to do....
Sent from my Evo Shift.
I have flashed the 1.8 oc kernel and seems to be stable at the moment. Scored a 2217 on Quadrant. Only minimal improvement from the 1.5 kernel. Scored a 2063 with that one. Also haven't maxed out the new kernel. Running just under max. Will do some stress testing and see what happens.
Sent from my Evo Shift.
bobtsunam said:
I have flashed the 1.8 oc kernel and seems to be stable at the moment. Scored a 2217 on Quadrant. Only minimal improvement from the 1.5 kernel. Scored a 2063 with that one. Also haven't maxed out the new kernel. Running just under max. Will do some stress testing and see what happens.
Sent from my Evo Shift.
Click to expand...
Click to collapse
That's actually a pretty reasonable improvement. A few people in the IRC have broken 3000, including myself, on Evervolv. However, I had virtually NOTHING on the phone when I got that.
Its a shame benchmarks don't accurately reflect phone performance, cause this phone is amazing even on the stock rom @ 800 mhz.
Sent from my Speedy Shift.
http://forum.xda-developers.com/showthread.php?t=894345
That thread shows proof of the attached pic below.
Perhaps this may give people a reason to switch to the Nexus S when it's released on Sprint.
We have pretty much all the same hardware. If I'm correct, hell the nexus one is still pretty damn fast. I believe that since GB calls upon the hardware to accelerate the ui that many graphical aspects are supercharged. I'm not saying our epics could hit that level stock but with Sprints bloat that would be almost impossible. Unless when we get CM7 fully we can match that. Just wishing lol.
Sent from The Epic Land Of The Lost.
Fyi that's on a oced kernel. Team whiskey got 1.4 stable on the nexus s. If we can get a 1.4ghz oc we would be just as fast. You notice from that screen its not showing the 2d or 3d results. Besides the cpu where right on target with memory and I/0.
Sent from my SPH-D700 using Tapatalk
MysteryEmotionz said:
Fyi that's on a oced kernel. Team whiskey got 1.4 stable on the nexus s. If we can get a 1.4ghz oc we would be just as fast. You notice from that screen its not showing the 2d or 3d results. Besides the cpu where right on target with memory and I/0.
Sent from my SPH-D700 using Tapatalk
Click to expand...
Click to collapse
+1 its almost exact hardware only difference is
Keyboard/no keyboard and that is no where near a reason to want me to upgrade ill be waiting till most likely the Evo 3d comes out and i see the specs because Development behind that thing will also be huge
MysteryEmotionz said:
Fyi that's on a oced kernel. Team whiskey got 1.4 stable on the nexus s. If we can get a 1.4ghz oc we would be just as fast. You notice from that screen its not showing the 2d or 3d results. Besides the cpu where right on target with memory and I/0.
Sent from my SPH-D700 using Tapatalk
Click to expand...
Click to collapse
The OP in the linked thread said - "Quadrant score w/trinity kernel running my modifications (2d/3d scores are 0 because quadrant does not currently support these tests for the Nexus S, its crashes)"
That's why the 2D/3D is 0. Still though, that's a beast score. LOL
I'm holding off for now (upgrade is available in April.) But these specs look promising.
Overstew said:
The OP in the linked thread said - "Quadrant score w/trinity kernel running my modifications (2d/3d scores are 0 because quadrant does not currently support these tests for the Nexus S, its crashes)"
That's why the 2D/3D is 0. Still though, that's a beast score. LOL
I'm holding off for now (upgrade is available in April.) But these specs look promising.
Click to expand...
Click to collapse
There just scores and mean nothing in real world.
Fyi: team whiskey is known for putting out placebos. Look at what they did with there 1.6kernel and they have between caught mounting there data differently to cheat quadrant. I forget the exact cheat but if we do it to the epic we would get those save scores. Remember the nexus s and the epic is almost identical. The only reason I will make the switch is cause of google support. To me that's the only thing the nexus s had over they epic
Sent from my SPH-D700 using Tapatalk
Nexus s is faster because of gingerbread the enabled hardware acceleration...
Until epic gets gb were not reaching those scores even with the same oc.
Sent from my SPH-D700 using XDA App
So with my old viper rom I had on dk28 there was a terminal hack that would allow you to change the hardware exceleraton on ad it seamed to make the phone faster but I can't seem to activate it again when I switched to bonsai 3.0.1 is there another way to turn this on.
Sent from my SPH-D700 using XDA App
omg Im so going to jump for the same Hardware and no keyboard now! Or not.. Im sure were going to get every update that the Sprint Nexus S gets a few weeks later (thanks to our devs) bc they're going to be the exact same phone except for the keyboard and that stupid chip the Nexus S has...
Double post...
There's a point at which these numbers mean nothing.
I have no lag on my phone with a Quadrant of 1902. A score of 3500+ wouldn't be much different...if at all. It's just a **** contest.
Is it really going to be that easy to port it over to the Epic?
Sent From My Command Center... (aka basement)
flopez76 said:
Is it really going to be that easy to port it over to the Epic?
Sent From My Command Center... (aka basement)
Click to expand...
Click to collapse
Yea if it comes to sprint with 4g.
the only diff. would be the Keyboard and the NFS chip
so our devs will kill it
it'll be as easy as making a fat girl horny
iSaint said:
Yea if it comes to sprint with 4g.
the only diff. would be the Keyboard and the NFS chip
so our devs will kill it
it'll be as easy as making a fat girl horny
Click to expand...
Click to collapse
Good analogy
epic
I'm getting it as long is it is clean android none of that samsung crap.
akijikan said:
I'm getting it as long is it is clean android none of that samsung crap.
Click to expand...
Click to collapse
As soon as Cyanogemnod is finished (already 85% of the way there) you will have "clean android" on the Epic without spending the money on the "upgrade"
063_XOBX said:
As soon as Cyanogemnod is finished (already 85% of the way there) you will have "clean android" on the Epic without spending the money on the "upgrade"
Click to expand...
Click to collapse
True that
Sent from my SPH-D700 using XDA Premium App
Stock 4.2.1 with franco's kernel: 1723
Stock 4.2.1 without franco's kernel: 1841
Now here comes the weird part...
CM10.1 4.2.1 with franco's kernel: 1243
What gives? What's with the sudden drop in the score? Is anybody else getting similar results? Is it because CM10.1 shuts off two of the cores? This comes as a surprise to me because I've been running CM10.1 for the past hour and it's noticeably smoother than the stock rom.
Silencer96 said:
Stock 4.2.1 with franco's kernel: 1723
Stock 4.2.1 without franco's kernel: 1841
Now here comes the weird part...
CM10.1 4.2.1 with franco's kernel: 1243
What gives? What's with the sudden drop in the score? Is anybody else getting similar results? Is it because CM10.1 shuts off two of the cores? This comes as a surprise to me because I've been running CM10.1 for the past hour and it's noticeably smoother than the stock rom.
Click to expand...
Click to collapse
So why care what worthless benchmarks say? Your phone - your experience. Screw what any benchmark app says mate. :thumbup:
Vangelis13 said:
So why care what worthless benchmarks say? Your phone - your experience. Screw what any benchmark app says mate. :thumbup:
Click to expand...
Click to collapse
I could care less about the benchmark itself. What worries me is whether or not CM10.1 shuts down two of my Nexus' four cores.
Silencer96 said:
I could care less about the benchmark itself. What worries me is whether or not CM10.1 shuts down two of my Nexus' four cores.
Click to expand...
Click to collapse
Probably franco's kernel does that. Which one are you on?
P. S. Why does it matter if phone runs ok for your usage..?
Vangelis13 said:
Probably franco's kernel does that. Which one are you on?
P. S. Why does it matter if phone runs ok for your usage..?
Click to expand...
Click to collapse
r72.
Also, because I paid top dollar to make the switch from my Galaxy S. If I really wanted functionality and nothing more, I would've just stuck with my Galaxy S.
Would you mind running an Antutu benchmark and telling me what you get? It could be an error on my side. thx
Silencer96 said:
r72.
Also, because I paid top dollar to make the switch from my Galaxy S. If I really wanted functionality and nothing more, I would've just stuck with my Galaxy S.
Would you mind running an Antutu benchmark and telling me what you get? It could be an error on my side. thx
Click to expand...
Click to collapse
Hm, can't do that, sorry. Last time I run a benchmark was more than a year ago, I hate them passionately. Particularly with the crappy job LG has done in the building of this phone, antutu is like the devil..
Isn't that r72 supposed to turn the cores off though? Try a different one?
Vangelis13 said:
Hm, can't do that, sorry. Last time I run a benchmark was more than a year ago, I hate them passionately. Particularly with the crappy hob LG has done in the building of this phone, antutu is like the devil..
Isn't that r72 supposed to turn the cores off though? Try a different one?
Click to expand...
Click to collapse
Nope, r72 introduced hot-plugging. Anyway, that definitely had nothing to do with the score seeing as to how I was running the same kernel on stock when I ran the test.
You got serious problems if you can't break 2000 on antutu. Because i can tell you at least one app that runs awfully slow for you, and thats antutu.
meangreenie said:
You got serious problems if you can't break 2000 on antutu. Because i can tell you at least one app that runs awfully slow for you, and thats antutu.
Click to expand...
Click to collapse
Sorry, what?
meangreenie said:
You got serious problems if you can't break 2000 on antutu. Because i can tell you at least one app that runs awfully slow for you, and thats antutu.
Click to expand...
Click to collapse
only those devices running bionic patched roms are going over 20000 in antutu, devices running the normal roms score a little less.
simms22 said:
only those devices running bionic patched roms are going over 20000 in antutu, devices running the normal roms score a little less.
Click to expand...
Click to collapse
yeah a little less, not 18000+ less though, lol
meangreenie said:
yeah a little less, not 18000+ less though, lol
Click to expand...
Click to collapse
oh, i see what you are saying. i think he just accidentally dropped a digit at the end of each score.
Sent from my Nexus 4 using xda app-developers app