yashsingh1/xdaforums huggingface dataset:
[Nexus One Android Development] Geniusdog254:
Android doesn't have a window server in the traditional linux sense of the term. It has SurfaceFlinger, which handles all the system graphics. SurfaceFlinger inits after the main kernel does, so you can see in the logs when it inits, unfortunately with IR's kernel, the kernel never boots at all, so not even logging inits so we can't see what went wrong.

Thanks for the input though!
[Nexus One Android Development] tolis626:
You're welcome! :)

It must be crashing with something that starts very early in the boot process...Can it be something that has to do with the SPL or the radio?It seems really weird that it cannot even start the kernel.From my experince(which is not much,but gets me from A to B)it should start the boot process,initialize the kernel and then crash if there was a problem.The fact that the kernel won't start causes me a great deal of confusion.Maybe we should start looking on some less obvious places.Although a linux dev's help is always welcome and deeply appreciated! :D
[Nexus One Android Development] Dany0:
Hey I have an idea! Can't we "hack" the radio to make it "patch" the drivers when it boots up? Fail-Safe IMHO!
[Nexus One Android Development] tolis626:
Well,if that is possible then yeah,I think it would help.But I also think that messing with the radio is quite dangerous and could permanently destroy your device once flashed.Let the experts talk now! :)
[Nexus One Android Development] storm99999:
I've actually put some thought into that. The problem is that we are working with undocumented hardware, with a locked off reference implementation, with no yet known way to recover.

Reprogramming the radio is a skill that maybe at best 3 people in this entire website community have the skill to do. A more visual way to approach it is that it's like having a switchboard a thousand buttons wide and tall, asking us to find the right button, with the knowledge that half the buttons will break our phone completely.

In other news, my research has been... unfruitful. I PM'd a few people, asked in certain IRC rooms, no response anywhere. Though to be honest, I wouldn't be surprised if a few just don't check PMs here. Someone with better connections may do better than me.
[Nexus One Android Development] babijoee:
edit: cm 6 22.7.10 nightly

nenamark= 13.9

necore=28.9
[Nexus One Android Development] dogiedogie:
How can one go up and one down, surely thats just showing us the inconsistency with whatever testing methodology was used.
[Nexus One Android Development] babijoee:
No its showing that theres improvement in PaulObrien desire port on neocore.

I've never got over 30 for cm roms. so its what i have observed
[Nexus One Android Development] tolis626:
Well,what would make the biggest visible difference now would be 2D graphics.We will experience smoother UIs and menus etc.But 2D and 3D go together here...

Is there any chance the new driver will be implemented in the 2.2 update by HTC?I mean,the radio can be updated and allow for the new driver to boot at least.
[Nexus One Android Development] charnsingh_online:
I don't think radio stuff is required here. It won't boot due to driver incompatibility with the kernel /main system. When working on 720p I remember graphics got messed up when increasing static ram to camera. So everything has to made compatible to each other at kernel level. From ram allocated to the clock of the system n gpu
[Nexus One Android Development] Dany0:
okay, what about creating a clean driver. It'd work this way, the driver would be 100% clean, just pointing to a folder on the sd card. The SD Card folder would contain experimental drivers. And instead of booting up regularly it'd test the GPU(Is it working? Yes. Can user see this pop-up? Yes. Can we boot up? Yes. Is the temperature okay? Yes can you run this benchmark? Yes. At least any/some performance boost? Yes.). And if it'd pass all these experimental drivers it'd go back to the original one.

or what about emulating android in android(yeah sure it's possible), and try to hack the other android? seriously!
[Nexus One Android Development] Geniusdog254:
I think most of you are overthinking this. I'm sure its just a problem with the kernel setup
[Nexus One Android Development] storm99999:
I strongly suspect (though no one has yet confirmed it) that the majority of the GPU driver resides in the radio. It has a security protocol going on as reported by Jack_R1 that won't give the kernel any more control than it needs.

My current goal is to get the Acer Liquid E driver ported over. It resides in userspace and operates on the same hardware, with wiring differences of course. So, if the radio is controlling this, we have three choices. One is to rewrite the radio to give the kernel access to the hardware so that the kernel can run the userspace part, crater the entire GPU control system and write the kernel driver more completely, or rewrite the radio to have similar hooks to the Acer Liquid E.

Rewriting the radio would give us compatibility. So, I hope those aren't our options and that we can work around it somewhere else, but it looks grim. Too bad I can't find anyone who has detailed knowledge of this stuff to help.
[Nexus One Android Development] tolis626:
So is it possible to rewrite the radio without putting our devices in danger?

And a noob-kind-of question...All this applies to the Desire too,right?The Nexus One and the Desire being almost the same device...Right?
[Nexus One Android Development] storm99999:
There is basically no way to safely do this, nor is there much a way to do this.

I wouldn't get your hopes up.
[Nexus One Android Development] fstluxe:
I don't think HTC Will go that far.. by limiting the clock speed in the radio.. if so then the had could do that also with the CPU clock speed ;)...

We're not 100 % sure that its controlled by the radio, do we ?

why not just not let some C pro take a look at this kernel.. I'm almost sure we're doing something wrong ..
[Nexus One Android Development] charnsingh_online:
I dont think how are you guys pushing the radio in there, its more of kernel thing. When you integrate new drivers you have to make everything compatible with each other. I remember effing up the graphics when moving static ram to camera(coolbho sent me those patches). When you put in something new you have to make sure you update the older stuff everywhere needed
[Nexus One Android Development] Geniusdog254:
Thats the point I've been getting at all along. It's just an issue with making these drivers boot. For one, QCOMM is building them in a .32 kernel, and I'm willing to stake a bet that all the kernels we've tried to build them in are either a .34, .35, or .29. Since my Nexus one is a .34 and my Evo one is .29, that's why it won't build for me I'm sure.

Someone needs to try cloning the whole CodeAurora kernel repo & then build it. I don't have time or I would.

On a side note: the GPU clock speed is definitely locked in the radio. A hardware engineer at Qualcomm has shown us that. Think about it, we can change the CPU because it has to scale in the kernel, or else it would be on max the whole time & slaughter the battery. The GPU doesn't have to scale, just turn on or off, so why let people screw with it's clock in the kernel?
[Nexus One Android Development] tolis626:
About that last one...For fun! :p

But seriously,it's not the best idea the way I understand it...Why would they lock the GPU speed in the radio?Probably that's how they perceive security...But anyway,I wouldn't mind that much changing the clock,but rather try a newer driver.We can get a good boost in performance without abusing the hardware.And since most,if not all,of the driver is in the kernel,I believe that is achievable.I will agree that we need a C expert and then start building new kernels from source...
[Nexus One Android Development] :
EDIT:

Suck meh balls.
[Nexus One Android Development] Jack_R1:
If you go some pages back and look at my post explaining clock structure of a generic ASIC device - you might get an idea, what are clocks about and why there is only so much you can do with them, and it's not about the radio. That might be educational for you, and also for fstluxe. Clocks aren't created by SW, and you can't assign any clock you want to any place you want. People are used to PCs and think that the phone is a sort of PC - well, they're wrong.

I wish I could help with porting the driver.. Unfortunately, it's way out of my skill set.
[Nexus One Android Development] Jack_R1:
You would have done good to not write about something when you're clueless, and didn't even bother reading before.

The thread name is misleading, and lots of good SW info gets lost in its depths. I suggest opening another thread dealing with porting the new graphics driver.
[Nexus One Android Development] fstluxe:
Thank You Jack_R1,

But I still don't get it why and how the winmobo device HTC vogue with Linux ported= able to let the frequenting changed by the kernel>

http://xdaforums.com/showthread.php?t=697673

with neocore scores +- 36 fps

I know its the old msm 75xx chip.

This is The only strange thing I can't understand..
[Nexus One Android Development] Jack_R1:
Because the clock structure there is different. It's another, ages old chip, which barely has anything in common with QSD8250.
[Nexus One Android Development] Dany0:
Where is our pro =.=
[Nexus One Android Development] tolis626:
Ok...Well,it was stated before that old MSM7xxx chips are easily overclockable.

@Jack_R1

I have been tracking this thread since the beginning and have read your post thoroughly.Thanks by the way,I learned a lot from it.What I wanted to say is that it's not the brightest idea to lock all of the gpu's modules etc in the radio because,clearly,it will be harder to port some newer driver or something like that there.Not only for us here but for the guys at HTC too.Overclocking is another thing now.Would be nice being able to overclock the Adreno but ok,I am happy without it.But a newer driver would be nice!

Oh,and I agree we should open a new thread about porting the driver.
[Nexus One Android Development] :
HELL NAH

I got a hammer and already oc'd it. Noob.
[Nexus One Android Development] Radmeister:
If the GPU scales with the CPU when it is overclocked would it not be possible to provide dummy clocks for the CPU speed? Lets say you have your cpu running at 1113mhz, and have the kernel believe it is running at 2113mhz. Maybe it would scale the GPU based on the dummy frequency. Just a thought.
[Nexus One Android Development] tolis626:
2113 MHz?Never thought my phone could be used as a frying pan! :p

But seriously,with a more sane value this could prove to be helpful.If any of the experts here can try and do this...
[Nexus One Android Development] Jack_R1:
Ok, this will be my last reply to stupid ideas. I hope the devs were smart enough to read and understand, everyone else can waste their time as much as they want to.

Back again to square 1, as simple as it gets, I don't know how to make it any simpler:

You have a kind of "root" clock, directly related to CPU clock. You have other stuff in the system, that is the CPU clock divided by something. Let's say graphics is divided by X.

The HW DOESN'T CARE WHAT THE HELL KERNEL "THINKS", NOR DOES IT CARE ABOUT SW AT ALL!!! THIS X WON'T BE CHANGED BY SW, BECAUSE IT CAN'T BE CHANGED UPWARDS! SW DOESN'T SCALE ANYTHING, BECAUSE IT CAN'T! IT DOESN'T CREATE/GENERATE/PROVIDE/DIVIDE/SCALE CLOCKS, IT ONLY SELECTS THE OPTIONS HW GIVES!

How hard it is to understand that? Think of these clocks as if they're tied with a rope. No matter what you do in SW - the GPU clock remains tied. IN HARDWARE. Not "restricted by radio", not "reading the CPU clock and scaling itself", not anything of the sort.
[Nexus One Android Development] dogiedogie:
I like what he was saying, I think you understood it wrong though. He wants the CPU to be running @ 1113, but the system (ie the GPU) to THINK its running off 2113 and so scale upwards.
[Nexus One Android Development] tolis626:
Ok man,don't get mad at us!Chill out...
[Nexus One Android Development] fstluxe:
I agree!,

New topic "make the new driver Compatible"

Close.
[Nexus One Android Development] Geniusdog254:
I was never thinking we could magically "change" clocks. I figured it was set up somewhat similar to the CPU, with several PLLs we could scale thru, or that it coulda been using the global PLL or scaling the modem one. I'm familiar with the CPU overclocking on these devices, and figured the GPU would use similar structures. I guess it doesn't :o lol

If someone else opens a new thread, I'll participate, but I don't have the experience nor the time to do it myself.
[Nexus One Android Development] Dany0:
OK to sum it up:

1.) We can't SW command GPU to change clock.

2.) The GPU clock is always clocked in ratio 1:7,984 against the CPU clock.

3.) If we OC the CPU we OC the GPU too.

4.) If we want to OC the GPU we have to change the ratio. Like to 1:7,5.

5.) But this is hard.

6.) It's easier to first use the Acer Liquid E drivers to safely enhance the performance.

7.) Then we can enhance the newly open sourced drivers to get even better performance.

8.) And then we can think of oc'ing the gpu.

So we've been talking about the 1-6 points sir Jack_R1. Chill out.
[Nexus One Android Development] Jack_R1:
Actually, what I said, that point 5 isn't just hard, it's impossible, not to the direction you want to take it. And yes, I've checked a lot to answer that, I'm not taking it out of my head. Back to my long post about clock structure, examples 1 and 2 could hint you, why it's impossible. Remember that it's SoC we're talking about.

Geniusdog, I should have supposed that the basic assumption would be - a device has PLLs in the same manner a modern PC does, on each peripheral bus. The thing is, PLLs cost power, so they won't necessarily be everywhere in powersaving-oriented devices, only in a very few places. Clock dividers are just as good, and cost much less resources. Unfortunately, they're not nearly as overclock-friendly as PLLs.

Sorry if I was harsh.
[Nexus One Android Development] fstluxe:
isn't there a Way Letting HTC integrates the new open source driver?kernel/user space..
[Nexus One Android Development] dogiedogie:
I say we just take lots of drugs and pretend our phones are getting 600+ in linpack :)
[Nexus One Android Development] Dany0:
it's not. The HW has to take the clock somewhere. Even if it's "Locked" there is always a bridge.

Let's say we have the CPU frame:

._________.

||------|--|

||-CPU-|--|

||clocks|--| <<---this remembers which clocks are available/ratio

||_____|--|

|------\....|

|-------\...| <<---this is the bridge we can hack

|-----__|. |

|----|???\.| <<---this asks for the clock

|----|GPU||

|----|___|.|

understood?
[Nexus One Android Development] Jack_R1:
If you think you're smarter than a HW engineer that met a clock tree or two in his life, has the relevant pages from the HW document of the chip laid on his desk, and happens to understand, what's written there - good luck. Tell me when you're finished trying.

I can't even start describing, how this stupid thing in your post that I quoted is far from anything real. But I don't want to. I already explained, what clocks are, for those that can actually understand. Anyone else can do whatever the hell they want to. Enjoy the ride.
[Nexus One Android Development] android.activate:
Can we just close this thread if its not going anywhere.. ? It was a great run Mr Jack and we all appreciate it. The community salutes you for your and everybody else's efforts who was involved in it.

Lets not stretch it till it breaks ( someone's sanity )
[Nexus One Android Development] egzthunder1:
Stay on subject fellas.
[Nexus One Android Development] Nauren:
These are not the clocks you're looking for.

And thanks Jack, for those of us that read your post it was interesting and informative.
[Nexus One Android Development] AzN1337c0d3r:
Whoops I donno why I am reviving a dead thread.
[Nexus One Android Development] flo90:
Have you a project to overclock the adreno 205 on desire HD??
[Nexus One Android Development] kamranh3:
+1 for the Desire HD!
[Nexus One Android Development] TeroZ:
+1 for the DHD.

But I really doubt if there is any feasible way to change the GPU frequency in software layer.

Sorry again for reviving a dead thread?

EDIT:

Ohh. I am stupid enough not to read the entire replys...

So we are definately impossible to change the GPU clock by software modification, right?

Thanks for all guys that providing infomative posts. Thank you!

But I don't think my GPU clock are changed when I overclocking CPU.
[Nexus One Android Development] BlackRainX:
And Any idea how to oc GPU in MSM 7201A?.. I know by activating turbo = PLL will set to 960 MHz from 768MHz. But i want to try 1056MHz PLL1. Is there any step to do it?. (I can compile kernels of course)
[Nexus One Android Development] :
BUMP

I've been looking into this myself

any dev interested?
[Nexus One Android Development] Dany0:
Shaky, it's a closed discussion. No way we can do that. The dev stormed(hahaha get it?) away ages ago ;) The few tweaks we have are enough IMO. I mean, with ICS and all the tricks we have we beat out Galaxy S GPU on the original, first 2.1 ROM. So that is more then adequate IMO.

Edit:

Oh by the way, were the Acer Liquid E drivers ever ported? I heard you could achieve the same effect with Chainfire 3d, but it didn't give the boost as big as the Liquid E drivers were giving, or I'm confusing something here.
[Nexus One Android Development] Dany0:
Oops double post sorry.
[Nexus One Android Development] Saphroxx:
I sure as hell am interested in this, with N1 possibly not getting CM9, an OC GPU or improved graphics driver (which original was **** for N1) would make ICS run smoother on N1 and also improve our chances of actually getting an official CM9 release.

Unfortunately I have no coding skills at all when it comes to Android, so I can't be of assistance with this project. Although I'm keeping an eye on this thread for follow up.
[Nexus One Android Development] Dany0:
Saphrox, you idiot, you can't OC just the adreno GPU, THE END. Read the thread first...
[Nexus One Android Development] Saphroxx:
I had subscribed to this thread and it was a long time ago that I checked it. At the point I checked this more frequently there was still no certainty as to OC'ing the CPU would also affect GPU clocks etc.

Shaky bumped this thread, I got a notification for it, read it and replied that I'm interested if after all there would be progress on this improving GPU performance with Qualcoms latest Adreno 2xx releases. All I was trying to do is to get more power out of my N1 to properly run ICS, as I know the gfx drivers and digitizer for N1 are ****. So no need to get frustrated over little details and call people names here, idiot.
[Nexus One Android Development] :
Guys chill n take it easy mahn, anyways, last year i looked into ocing the msm8255 adreno205 gpu, i didnt finish it off due to running a diff os.

I did have a few ideas but i havent tried them

I did manage to successfully overclock the gpu on dhd, as i saw the evidence myself but the system threw back the clock to default frequency

@dan0: no offence have you tried yourself? Or is it from the word of other people? Where is the evidence?

GREAT example of dont believe everything you hear is when people on xda claimed wiping battery stats gives better battery? Or something similar and dianne proved it wrong
[Nexus One Android Development] tommypacker:
You say you're a kernel Dev.... Do you think you could fix a modem issue with Nikez kernel 3.0 for qsd?
[Nexus One Android Development] FeraVolt:
Done.

Good night. Peace out!
[Nexus One Android Development] tommypacker:
In the Evervolv kitkat/jb branches, I can only find the file acpuclock-qsd8x50.c not acpuclock-q8x50.c. Are they the same file?
[Nexus One Android Development] FeraVolt:
Just forgot to mention little thing.. Since we have now overclocked cpu..we have to correct max freq. value in acpuclock-8x50

So search for this:

case 0x00:
max_acpu_khz = 998400;

and change the value to 1190400.. Now you're done.

[YOUTUBE]950lU5hWGWo[/YOUTUBE]​

Another QSD8K goodies will be here:

http://xdaforums.com/showthread.php?p=49202903
[Nexus One Android Development] GlennBrownie:
I'd recommend a noob-proof patch if possible?
[Nexus One Android Development] Valantur:
Promising. It'd be awesome to have a flashable zip at our disposal to test it out.:fingers-crossed:
[Nexus One Android Development] tommypacker:
I'll try to make one once i get my Nexus One out of a vegetable state
[Nexus One Android Development] GlennBrownie:
Any luck with this [MENTION=5154992]tommypacker[/MENTION] ?
[Nexus One Android Development] FeraVolt:
http://xdaforums.com/android/software-hacking/hack-overclocking-tuning-snapdragon-s1-t2883708

Much better (Y)
[Nexus One Android Development] mshipXZ:
Adreno 305

Well I saw Galaxy Mega 6.3 had Adreno 305 clocked @ 500MHz is uses Qualcomm Snapdragon MSM8930AB Chipset but how did it come up with 500MHz if thats compatible with Adreno 305 then the ones in Xperia T2 Ultra [MENTION=1034050]450[/MENTION] MHz could do it too like Samsung but Xperia T2 Ultra uses MSM8928(Mine) and Adreno 305 runs @ 450 MHz is 500 MHz compatible with T2's Adreno 305? On anTUTU 5.4 @ 450 MHz it gave 3D score highest on mine was 4105 I think while @ 500 MHz it was 5075 on 3D I saw it with my eyes. That is why I'm asking this question. Thanks. :)
[Nexus One Android Development] Joel Oliveira:
is possible only in overclocking gpu for Otus ? perhaps this topic help in something . http://xdaforums.com/showthread.php?t=710850&page=3

?
[Nexus One Android Development] Dcfan200:
Hello. Does anyone have any information to share about possibly overclocking the Adreno 530?
[Nexus One Android Development] jlevy73:
Be curious to see what increasing the memory of the GPU will do. I do recall when coohlbro came up with the 21mb hack. I took this straight from the OP of that thread (because I am too tired to paraphrase it):

This time, my RAM hack expands memory by 21MB total from the stock kernel. And this time, no camera PMEM is taken away! This is all thanks to the incrediblec kernel source released by HTC giving me some insight.

This is what I did, starting from the 8MB RAM hack:

- Expanded EBI1_BANK0 by 8MB because the incrediblec source said I could

- Moved 5MB GPU memory from EBI1_BANK0 to SMI

- Created extra memory bank in EBI1_BANK0 totalling 13MB

- Added 8MB camera PMEM back into SMI, and re-enabled camera PMEM

Version 2:

- Eliminated third memory bank in EBI1_BANK0 and added that memory into the first memory bank

As far as I know it's not possible to create a memory bank in the SMI and live to tell the tale, so that's why we're squeezing the 8MB of camera PMEM in there. In total, this adds 21MB of RAM from stock cm-kernel with seemingly no compromises.

The zImage is meant to be a proof of concept and only contains this tweak on top of normal cm-kernel. I don't suggest using this zImage for long, as it doesn't contain any "extras," and the regular custom kernels with all the extra features/optimizations will probably incorporate this soon.
[Nexus One Android Development] Geniusdog254:
Changing the RAM tables won't be too difficult. I'm gunna play with some values here in a minute & try it out. I don't have my Nexus with me so I won't be able to test it for the next hour or two, but I will be able to go through some source right now.

As if we needed more proof as to how much we need is OC, look here: http://bit.ly/csSIzp

Our chip shouldn't struggle to come close to that at all, yet it does.