yashsingh1/xdaforums huggingface dataset:
[HTC Desire S] kylon:
I cannot push the code to github

I can give you my files, tonight

EDIT:

the 3d oc is still there, even if it is not a real oc, it gives us a performance boost
[HTC Desire S] Shaky156:
My attempt on the 3d-core gpu oc isnt finished/released yet. Anyways the errors on your side, I set 245760000hz on purpose(reason behind it) one thing i fail to understand is where you're pulling 266mhz?? I think i know where its come from but can you explain the logic behind 266mhz?
[HTC Desire S] kylon:
It comes from the previous "oc"

Why?
[HTC Desire S] Shaky156:
I understand it comes from your previous oc, but wheres the logic? How did you get the figure 266mhz for gpu and where from?
[HTC Desire S] kylon:
I was just trying, to achive more performances
[HTC Desire S] Shaky156:
I fully understand what youre sayin, you probably got it from somewhere im seeing it on every msm7x30/msm8x55 soc out there, who is the original author of this commit?
[HTC Desire S] kylon:
As i sayd, sezsco, from the incredible s section

The first oc commit was his
[HTC Desire S] Shaky156:
Ahhhh i see, well check the 3d core clk like you checked the 2d clk, gaurantee your 3d core clk is underclocked to 192mhz instead of the overclocking you want lol
[HTC Desire S] kylon:
No, the clock is 245 here
[HTC Desire S] Shaky156:
If u have 245 within the platform data it will hit245 if you keep 245 lowest itll keep at 245mhz only but if u set it to 300+ only then itll push back to 192, itll never hit the 300+ or even 266mhz
[HTC Desire S] kylon:
245 is in list clocks

Platform says 350
[HTC Desire S] Shaky156:
You get the point im making though wveryone on the msm7x30 soc thats claiming 266 or anything above 245mhz is all a lie, there is 0-nothing-nada- no gpu oc in existence for the msm7x30 soc, personally would remove it from all kernel dev op that people claiming to oc the gpu above 245
[HTC Desire S] kylon:
so, the limit is 245?

what exactly is this(the 3d "oc"), then? a tweak?

anyway, i also tried 245 but it does not work
[HTC Desire S] Shaky156:
It is what it says in the title of the thread, 2d-core gpu oc, 3d is being worked on atm, it isn't a tweak

Must be an error on your side, other devs have implemented successfully
[HTC Desire S] kylon:
Wait

I said, the fake 3d oc that i m using gives a performance boost, so what is it?

I ll try again to add it and i ll link github

Do you have a diff? Just to be sure that i m doing it correctly
[HTC Desire S] Shaky156:
Fake oc is basically when u benchmark ondemand set low freq to lets say 128mhz and high freq to 1.7ghz lets say u benchmark and get 4000 score on antutu (made fake figured just for example lol) now say if u set the minimum freq to 1.7ghz and benchmark your score will increase

Basically setting the min gpu 3d-core freq to 245mhz will have that effect, the gpu has np chance of scaling down to 192mhz, what the debug fs clks output is what the core true frequency is running at

Link to diff

http://xdaforums.com/showthread.php?p=43808664

Will update diff later to newet version and 3d-oc
[HTC Desire S] kylon:
this does not exist on saga

--- a/arch/arm/mach-msm/devices-msm7x30.c

+++ b/arch/arm/mach-msm/devices-msm7x30.c

@@ -1319,11 +1319,7 @@ struct resource kgsl_3d0_resources[] = {

static struct kgsl_device_platform_data kgsl_3d0_pdata = {

.pwrlevel = {

{

- .gpu_freq = 364800000,

- .bus_freq = 249600000,

- },

- {

- .gpu_freq = 245760000,

+ .gpu_freq = 245760000, /*Restore correct GPU frequency and bus frequency (Shaky156)*/

.bus_freq = 192000000,

},

{

@@ -1336,7 +1332,7 @@ static struct kgsl_device_platform_data kgsl_3d0_pdata = {

},

},

.init_level = 0,

- .num_levels = 4,

+ .num_levels = 3,

.set_grp_async = set_grp3d_async,

.idle_timeout = HZ/20,

.nap_allowed = true,

this should be the right diff

--- a/arch/arm/mach-msm/devices-msm7x30.c

+++ b/arch/arm/mach-msm/devices-msm7x30.c

@@ -1376,25 +1376,25 @@ struct resource kgsl_3d0_resources[] = {

static struct kgsl_device_platform_data kgsl_3d0_pdata = {

.pwrlevel = {

{

- .gpu_freq = 245760000,

+ .gpu_freq = 245760000, /*Restore correct GPU frequency and bus frequency (Shaky156)*/

.bus_freq = 192000000,

},

{

i did a clean up and the 2-core is working, thanks

so if i understood

stock gpu

2d-clock=min_freq=192mhz

3d-clock=max_freq=245mhz

your 2d-core

2d-clock=min_freq=245mhz

3d-clock=max_freq=245mhz(waiting for an higher freq Lol )

so here the perf boost, right?
[HTC Desire S] Shaky156:
That is correct basically i worked from patchas kernel on desire hd which the 3d core was set incorrectly same for the bus, so that was included in the diff for dhd, yes 50mhz increase in freq theoretical perf increase = 25% people have benchmarked and its true but benchmarks vary and not can jump here and there.

3d-core oc is very difficult, doing a test soon will find out whats happening :)
[HTC Desire S] Shaky156:
Okay after looking @ GPU Overclock for 2 weeks, This is the news on GPU OC for MSM8x55/MSM7x30 socs.

My findings...

2D-core OC from 192mhz to 245mhz successful.

3D-core OC will not happen without me obtaining the datasheet (which is proprietary)

The clocks are protected, via Ownership/Permissions, and maybe an RCU/MPU

No Overclocking the CPU does NOT Overclock the GPU, thats the worst thing I've heard in my life lol.

The lowest the GPU can hit is 192mhz or lpxo freq

Bus is not overclockable, it always is 192mhz

EBI_2D_clk will and has always been 0mhz

Modifying kgsl platform data and/or the graphics table with random values or even calculated values from correct pll freqs will NOT OC the gpu

it's ashame the GPU clocks are protected.

IF anyone is looking to continuing this project and is on the right track you're more than welcome to get in contact with me, especially if you have the msm7x30 datasheet.

The QSD8x50 soc is more open than this soc, so I'm doing a few tests on the HD2
[Xperia Play Q&A, Help & Troubleshooting] azkay:
I'm not sure if it's the battery that is the problem, as I bought this r800i the other day sold as a demo unit.

I've been experimenting with different roms/kernels and decided to stick with AtoMic Gb 7 and LuPuS-GingerBread-v12.

From all the research I made before buying it I was seeing posts on people getting 5ish hours with wifi off and lowest screen brightness etc, not sure how from my experience.

eg; Playing Yoshis Island with SuperGNES on the train, lowest screen brightness, wifi off, data off, gps etc off my battery went from 82% to 14% in 15 minutes.

Any ideas/tips/etc?
[Xperia Play Q&A, Help & Troubleshooting] crazymonkey05:
That sounds like an insane amount of battery loss try getting a new battery there like $10-$15 on ebay
[Xperia Play Q&A, Help & Troubleshooting] azkay:
Thought it was a little odd, my battery just now went to around 60% from 100% in 23 minutes according to the battery usage thing.

Time for a new battery, I'll update this when I get one.
[Xperia Play Q&A, Help & Troubleshooting] RavenB:
WTF??thats crazy man,15 minutes will drain 5%(maximum)with screen brightness at 75%,get a new battery!!
[Xperia Play Q&A, Help & Troubleshooting] Toasty Clown:
Hey man, I was around back when lupus GB V12 was released, look at the posts from then and you'll see some users complain about bad battery life and excessive heating found only in this update (link here), use one of the official or user-provided links to get V11, I use it with Gin2JB overclocked to 1.4GHZ, smartassv2, sio, no undervolt, and get a good 4-6 hours on Mupen64Plus AE (configured for maximum accuracy) with a heavy N64 game such as Majora's Mask (which was so much so that it required the expansion pack and even then had its FPS capped at 20). With Snes9x EX+ I can go about an entire day using it, let alone little more than a mere hour. Safe to say, my battery life's pretty damn good, well, for my standards anyway. Stock battery too! I'm familiar with an X8 and a Galaxy Ace original, similarly modded by myself, both have comparably terrible battery life and performance, even in general. Still, I'm with Raven and CrazyMonkey as I certainly wouldn't rule out a perma-dead battery.
[Xperia Play Q&A, Help & Troubleshooting] azkay:
I've ordered a 2500mAh battery, should be here in a few days. I highly doubt it'll be 2500mAh, but also doubt it'll be less than 1500mAh.

I'll look at v11, too.

I get lots of power offs, too. Tends to happen more when I'm not charging and using anything that uses more power: eg; data/screen brightness/gps and it'll just instantly turn off. So it really looks like the battery is just a dud. Today I was trying to check something on google maps, I had to turn it back on around 15 times before I got far enough into the menu to turn data off for it to stop turning off on me.
[Xperia Play Q&A, Help & Troubleshooting] azkay:
Haven't had any problems since getting the new battery. No reboots, poweroffs or 85% charge lost for no reason.
[Xperia Play Android Development] Shaky156:
Finally after someone pm'd me I looked back into GPU Overclocking.

New thread created issues with old thread OP permissions (people seem to be asking the same questions over and over again all information will be kept in OP & DO READ THE THREAD, repetitive questions will now be ignored)

Benefits:

Smoother UI

Handle 2d & 3d core GPU intensive applications & games

Currently only 2D core has been overclocked working on 3D core OC

2D-core original value - 192mhz OC to 245mhz DONE achieved 25% performance boost grp_2d_clk outputs 245760000hz

3D-core original value - 245mhz OC to 300+mhz WIP hoping to achieve 40-50% performance boost

2D-core OC only Download: Coming soon...

Download Links for other devices coming soon...

Works for all HTC Sense/Cm9/Cm10 kernels (Just ask a kernel developer for your device to implement the source code)

Note: Don't have internet on PC so providing 3 main files that need replaced for 2D-core OC to work :)

Download link to source code: http://d-h.st/wbH

3D-CORE OC TESTS Download: Coming soon...

Do check under sys/kernel/debug/htc_clock/clks/ look for file with all clocks & look for GRP_clks (Graphics clock)
[Xperia Play Android Development] Shaky156:
OK so basically today I've been thinking and I've come to the conclusion that I will release the 2D-core OC patch As Soon As Possible, 3D-core Core OC is NOT Impossible but for now I'll give it a break, I will attempt 3D-core OC If/When I can get a hold of a msm7x30/msm8x55 device, as it will make it much easier for both me & users.

So for now you can enjoy the 50mhz increase/bump up, perf boost 25% in 2D-core (will increase performance in both 2D/3D intensive appications as 2D-core is used for 3D AFAIK and increase User Interface performance (Note: This will not take a hit on battery life)), I will also release a couple of fixes on patchas kernel that shouldnt be there/set etc.

(Theres a device available in my area for roughly £90, if anyone wants to contribute towards getting that device or can donate a device , more than welcome and shoot me a PM so I can list you here.)

(This isnt a promise of 3D-Overclock if you donate, if you donate please do so expecting nothing I will only attempt 3D-overclock)

Working device list - all kernel 3.0+ msm7x30/msm8x55 soc devices.

Main thread is in Desire HD Android Development section: http://xdaforums.com/show....php?t=2368497
[Xperia Play Android Development] extremetempz:
Don't over clock The GPU On MSM7X30 I over clocked the gpu from 245 to 260 it caused severe battery drain and laggy fps
[Xperia Play Android Development] Shaky156:
Sorry but no one has managed to overclock GPU yet (until ive released) modifying kgsl pdata only is NOT overclocking at all itll push the 3dcore back to 192 in sync with axi, please show me the work (source code) and dmesg showing successful overclock including grp_3d_clk outputting overclocked value
[Xperia Play Android Development] extremetempz:
I found in the kernel source code arch/arm/mach-msm semc_board_Zeus and i changed the clockspeed from 245MHz to 260 MHz and I have checked the clock speed In root explorer and it seemed to work as I said it makes the device hot,lag and causes battery drain not to mentain the long time effects
[Xperia Play Android Development] Shaky156:
Honestly what people say on here I take with a pinch of salt, why? cause people are narrow minded, people said GPU OC is impossible yet I have managed it. I don't won't take your advice based on what you say, show me code/show me evidence then I will believe you. BTW heres some advice takes more than modifying 1 file to GPU OC the 3d-core ;)

Like I said show me evidence then I will believe you :)
[Xperia Play Android Development] extremetempz:
this is an example from dooms github

https://github.com/DooMLoRD/Xperia-...mmit/8ea76470f307426d3f4b0db322708e7f862b474a
[Xperia Play Android Development] Shaky156:
Hi, thanks, as I said, it takes more than editing the kernel graphics software layer platform data ;), that was not overclocking lol!
[Xperia Play Android Development] zefyx:
Wow, great work dev! This is incredibly awesome, especially for us Jellybean users who could use every bump in performance possible. After a lot of hard work, I finally have my 4.1.2 r800x on Paranoid Android at in AnTuTu. I can't wait to see what increases I yield with the 2D overclock and ESPECIALLY the 3D overclock. Please, oh please, try and get 3D overclocking implemented successfully. You will be a god-send to many of us Xperia Play users. While an old device, its purpose built and many of us still use it daily as a phone if not simply for an advanced gaming device. Expect a donation your way soon. I'm not sure if this falls on you or kernel developers but please make sure CDMA users aren't left outside the gate. We miss far too much in what's already a small development scene and I'm afraid this is something we simply cant afford to miss. Thanks again for your hard work. Keep it up!

On a side note, Turbo Kernel is no longer in development. Would you or anyone else be willing to patch these changes and compile the source for us still using the kernel? It's the best kernel I tested that works irregardless of phone or software version.
[Xperia Play Android Development] extremetempz:
it does work because many devs that have included in their kernel have taken it out and if u push your min clock speed to 245MHz its an immediate GPU over clock but.it has many side effects
[Xperia Play Android Development] Shaky156:
It falls on kernel developers as I have released the source, GPU OC isn't GSM specific so CDMA users sure will get it :).

I usually release kernel before source code but due to my slow PC & Laptop, and I only have net access on the slow laptop I released source code first, cause kernel compiling for me is time consuming, when I do get more time, I sure will pull and compile that kernel for you :)

hahaha I've requested multiple times evidence and you have failed to provide it, if you believe that was GPU OC please flash that kernel with those changes with debug file system enabled and show me the graphics clocks, if you simply cannot provide evidence I will start reporting your posts as troll posts, thank you

EDIT: I have simply done the job for you

https://github.com/DooMLoRD/Xperia-...mmit/4df2f67a4bc475116cec29fd7abe4d388474b191

take your time to read the comments within that commit
[Xperia Play Android Development] extremetempz:
I don't have my play ATM

but if you ask one of the users using my dxengine extreme or fast editions they will be able to provide for you
[Xperia Play Android Development] Nuck-TH:
we havent working 3.x kernel. so this thread is useless.

better if you make this for 2.6.x kernels, and with antutu cpu master's GPU control support.
[Xperia Play Android Development] Shaky156:
You dont have a working 3.0?!? Didnt expect that, no problem ill create a kernel patch for k2.x

Its the 2d-core OC only at the moment at 245mhz there isnt any need for GPU control support
[Xperia Play Android Development] McXeno:
"300mhz+ ... " You said. Well you man are awesome if u make that happen! If you need tester or anything i'll test anything with pleasure ! I see you have double thanks than posts so I'm sure you're good so good luck !!
[Xperia Play Android Development] McXeno:
R800i is GSM

R800x is CDMA

R800a i don't know

R800at i think is at&t's 4G variant.
[Xperia Play Android Development] Shaky156:
Is it zeus? Pheonix? Ayame? Iyokan? Haida? Anzu? Hallon?
[Xperia Play Android Development] MegaRacingHD:
zeus
[Xperia Play Android Development] Shaky156:
Cheers, compiling kernel now check the sys/kernel/debug/clk/grp_2d_clk if its running @ 245mhz

Compiling turbo_zeus kernel
[Xperia Play Android Development] Shaky156:
https://dl.dropboxusercontent.com/u/58024932/2.6xXplayGPUOC - Copy.zip

devhost was giving issues so i dropboxed it instead

not a flashable zip

included kernel & modules

turbo kernel + 2dcore gpu OC
[Xperia Play Android Development] CriGiu:
Thanks for your work man, I will gladly check this when released, if it's confirmed that gpu overclock is not dangerous.

P.S.: zeus is the GSM version (r800 - r800i) while zeusc is the CDMA version
[Xperia Play Android Development] Shaky156:
I fail to understand how people can claim its dangerous when they were unsuccessful at overclocking, really shocking, ill let my development speak for itself :p (overclocking only becomes dangerous when voltage is messed with, i assure you higher frequency, same voltage)

Once whoever flashes the kernel please report the 2d core frequency
[Xperia Play Android Development] Lefteris Fragiadakis (Frago):
Can this include in doomlord ics v3 for tests?
[Xperia Play Android Development] Shaky156:
Link me to his github (last kernel for the day)

Edit: dont have time now maybe later, released turbo kernel need report of 2d graphica xlock
[Xperia Play Android Development] Lefteris Fragiadakis (Frago):
OK maybe tomorrow
[Xperia Play Android Development] zefyx:
I successfully flashed the 2D zip from your Desire HD thread, the 3D zip failed. AnTuTu benchmarks showed improvement, who knows? But I've tried to help spread the word and I'm rooting for you. Don't let the trolls get to you, they obviously don't realize this is a project spanning over multiple phones, some, with flashable zips and a large user base. Keep up the great work!
[Xperia Play Android Development] Shaky156:
Dont flash the zip from desire hd thread!! Thats for desire hd! Theres a zip in this thread that isnt flashable but has the kernel that needs tested
[Xperia Play Android Development] zefyx:
It was mainly just to see what would happen. No damage occurred and it has since been wiped. I'll check out the zip from this thread now and try to test the kernel.
[Xperia Play Android Development] Shaky156:
Kool 3d oc is abit more difficult

Devs + testers join IRC will make life easier

Irc freenode #s1gpuoc
[Xperia Play Android Development] abdel12345:
I can test on jelly bean for you if you need it

Sent from my Xperia Play (r800x)
[Xperia Play Android Development] Shaky156:
I dropped a kernel in this thread earlier you can test that :)
[Xperia Play Android Development] fma965:
Hey great work,

Let's clear a few things up. OP is clearly developing this for tons of phones. (most likely with same or near hardware)

@OP, Any Xperia 2011 device can not have it's kernel flashed via CWM so even if your zip was a flashable zip it wouldn't flash as... well mainly the partition is not accessible from CWM.

Any chance of getting this patch added to like Lupus JB v8?
[Xperia Play Android Development] ~iSamur@i:
Maybe is better if you also post this patch into the development section of the mogami board, it is more active in development (and if I am right we have the same GPU into every xperia 2011),they are also working on the kernel 3.x
[Xperia Play Android Development] zefyx:
Checked out the chat earlier and it was empty, I tried :(
[Xperia Play Android Development] Enri1196:
I'm really sorry, but i'm just asking guys :confused:, is this thread gone with his project?? because i didn't see any reply for the last 5-6 days. Maybe this thread has been moved to another section more active?? I don't know... if yes, can someone give me a link?? so i can keep myself updated about this awesome project :D
[Xperia Play Android Development] Shaky156:
Okay after looking @ GPU Overclock for 2 weeks, This is the news on GPU OC for MSM8x55/MSM7x30 socs.

My findings...

2D-core OC from 192mhz to 245mhz successful.

3D-core OC will not happen without me obtaining the datasheet (which is proprietary)

The clocks are protected, via Ownership/Permissions, and maybe an RCU/MPU

No Overclocking the CPU does NOT Overclock the GPU, thats the worst thing I've heard in my life lol.

The lowest the GPU can hit is 192mhz or lpxo freq

Bus is not overclockable, it always is 192mhz

EBI_2D_clk will and has always been 0mhz

Modifying kgsl platform data and/or the graphics table with random values or even calculated values from correct pll freqs will NOT OC the gpu

it's ashame the GPU clocks are protected.

IF anyone is looking to continuing this project and is on the right track you're more than welcome to get in contact with me, especially if you have the msm7x30 datasheet.

The QSD8x50 soc is more open than this soc, so I'm doing a few tests on the HD2

Also I already dropped a kernel for test, NO one here tested while everyone wants to test they cant search a thread for the kernel I dropped??. I wont waste my time trying to explain or babyfeeding users here its quite simple. Users are being lied to with fake GPU OC that dont make sense and are impossible on the msm7x30 socs and everyones taking it in, do what you want guys, implement the patch or not doesnt bother me :)
[Xperia Play Android Development] abdel12345:
I wanted to test but the only Kernel working for me is lupus v13 and fxp kernel. The test was turbo kernel so I couldn't test sorry

Sent from my Xperia Play (r800x)
[Xperia Play Android Development] DiamondBond:
Dude like [MENTION=4348417]fma965[/MENTION] said our Plays dont have a cwm that can access the kernel partition so no one can flash this, please urself read behind a bit to see what everyone has said, as what u said about NO one testing is untrue as it is impossible for us to test this!

But good work anyways! ;)
[Xperia Play Android Development] fma965:
not quite sure what your chatting but it ain't the truth, I never said this couldn't be used i said that we simply can not flash kernels via CWM we can still use FASTBOOT!

----------------------------------------

Also FYI here is the link to his kernel with OC i believe its turbo kernel based. https://dl.dropboxusercontent.com/u/58024932/2.6xXplayGPUOC - Copy.zip

It's a zImage so uh you will need to update the existing zImage in the turbo kernel img but apart from that there is no reason it won't flash to our phone.
[Xperia Play Android Development] abdel12345:
Yes but this patch is for kernels so we can't flash it because we can't access kernel via recovery so he has to apply it to the kernel or someone else themselves. That's what pizzadox meant

Sent from my Xperia Play (r800x)
[Xperia Play Android Development] fma965:
Yeah but from what i researched its not hard to inject zImage in to kernel.
[Xperia Play Android Development] abdel12345:
OK I was just explaining what pizza dox meant by what I understood

Sent from my Xperia Play (r800x)
[Xperia Play Android Development] fma965:
OK Cool, He didn't explain it very well imo, But thanks for clearing that up, Any way lets back on topic :)
[Xperia Play Android Development] jianjian0255:
When will it launch? I'm looking forward to his performance
[Xperia Play Android Development] fma965:
A Kernel was already released but just he zImage part so some one with time needs to inject the zImage in to turbo kernel 3.1, Also i think he gave up due to something about being locked from OC.
[Xperia Play Android Development] jianjian0255:
Where to download it?
[Xperia Play Android Development] yekasangredevago:
[MENTION=4348417]fma965[/MENTION] , sorry for the off topic comment ...

But someone could continue the development of Turbo Kernel 3.1?? , Optimize a bit more & correjirle some small errors that still has?? .. is very good experience to have GB / ICS / JB installed at the same time in our Xplay .. :D