Related
Recently, I finished finally modifying the xperia x10 that I have and one of the greatest improvements that those guys achieved was getting a lot more processing power by enabling JIT.
So naturally after seeing it work miracles on the x10, I went to look for it on my captivate and so far have come up with nothing anywhere. I saw some discussion in the past about it but nothing beyond.
Hopefully somebody can enlighten and if such a thing does seriously want to be worked on.... Here's a thread!
Sent from my GT-I9000 using Tapatalk
FroYo (2.2) and later have Just-In-Time compilation (JIT) out of the box. There are probably a dozen FroYo ROMs on the front page alone, so pick one have fun!
From what I've read, it's been a part of the ROMs since 2.1 but it needs to be enabled. Is this the case here or am I missing something?
Sent from my GT-I9000 using Tapatalk
kr3w1337 said:
From what I've read, it's been a part of the ROMs since 2.1 but it needs to be enabled. Is this the case here or am I missing something?
Sent from my GT-I9000 using Tapatalk
Click to expand...
Click to collapse
That is one of the biggest parts of froyo is that it enables JIT...so if you run a rom that has froyo its enabled unless I'm mistaken...
Sent from my GT-I9000 using XDA App
JIT is enabled by default in all Froyo ROM's. You can check the build.prop for ****s and giggles though.
The Galaxy S won't show the kinds of scores that Qualcomm based devices will, even with JIT enabled. Qualcomm included 128-bit SIMD Floating Point extensions with Snapdragon, while the Hummingbird only has 64-bit extensions.
yes with jit we get a 60-70% improvement but a qualcom gets 300%+ in floating point operation. in modern computers there are many other factors though and quardrant cpu scores are still very high for our chip (if you use the pay version you can see the score breakdown). so dont let the linpack scores discorage you. ive gotten as high as 18.2 in linpack with some overclocking though, which isn't bad. it's not the 50+ in the qualcom phones with some mods but not bad.
So that's what the story is, thanks guys! Wondering if things could be improved beyond overclocking...
I know it can be but don't know how. Some guys are getting 25+ in linpack on there website. So there is something else holding us back a bit.
Sent from my SAMSUNG-SGH-I897 using Tapatalk
Dani897 said:
I know it can be but don't know how. Some guys are getting 25+ in linpack on there website. So there is something else holding us back a bit.
Sent from my SAMSUNG-SGH-I897 using Tapatalk
Click to expand...
Click to collapse
You talking about xperia x10? really 25 on linpack? I dunno if that is even possible to OC to astronomical speeds. They run on older hardware and I think most are still on 2.1.....
All Android ROMs have a JIT compiler, it literally is what compiles all the Java on the fly. Newer versions are optimized for better performance.
So the better question is do the 2.2 Froyo ROMs have the latest JIT compiler version available or does the Nexus S have a newer more performant version we can steal. More than likely it will not work with 2.2 since the Nexus S is using 2.3.
From everything I have heard the newer JIT comp versions are optimized for the Snapdragon chipset more than anything. Which doesn't do us much good.
2.2+ have the JIT. Prior to 2.2, all programs ran entirely as interpreted bytecode on an isolated virtual machine. In 2.2+, the JIT translates the most cpu "heavy" bytecode down to native instructions during execution, stores it in cache, then runs it natively on the processor in a protected mode. Dig the video below, it's an hour long but the functionality of the JIT is explained in the first 15 minutes.
^Edited the above to accurately describe the function of the JIT
http://www.youtube.com/watch?v=Ls0tM-c4Vfo There you go, dudes. JIT Demystified.
modest_mandroid said:
2.2+ have the JIT. Prior to 2.2, all programs ran as bytecode on an isolated virtual machine. In 2.2+, the JIT translates the bytecode down to native instructions just before execution, then runs it natively on the processor in a protected mode. Could be wrong, but to my understanding, that is the major difference between 2.1- and 2.2+.
http://www.youtube.com/watch?v=Ls0tM-c4Vfo There you go, dudes. JIT Demystified.
Click to expand...
Click to collapse
This is what I saw and know too. However, I believe that the compiler that we are using is rather old and has some room for improvement. The nexus S compiler working on the captivate is a possibility that could become true after the 2.3 port is finished, provided that the developers look into it.
Sent from my GT-I9000 using Tapatalk
Hello every genius !!
Can someone add 3D driver optimisations in their fabulous kernel / rom like cyanogen mod7?
In cyanogen mod we can notice a real boost performance in 3d applications. So why not include the cyanogen 3d driver in next rom or kernel ?
Thank you all !
Jimmy from France
jimmy72 said:
Hello every genius !!
Can someone add 3D driver optimisations in their fabulous kernel / rom like cyanogen mod7?
In cyanogen mod we can notice a real boost performance in 3d applications. So why not include the cyanogen 3d driver in next rom or kernel ?
Thank you all !
Jimmy from France
Click to expand...
Click to collapse
Because 3D diver from samsung is not open.
So nobody cant take it.
True near my words
Ivan from Russia
I'll quote my post from another topic
Guys, look at that:
http://glbenchmark.com/subtest_results_of_device.jsp?D=Google+Nexus+S&id=405
There are 12 tests of Nexus S in GLBenchmark, and 11 of them are below 2400 points (more or less like our SGS), but the most recent one (uploaded at 2011.02.11) scored 3025 points, more than Tegra 2. This result's is made by someone from GLBenchmark, and shows at "GLBenchmark team tested" page of the results. How is that possible?
Click to expand...
Click to collapse
So, according to this benchmark, the performance of Nexus S'ses SGX540 increased dramatically somehow. And according to this article,
LG's software build also uses a newer version of Imagination Technologies' driver (1.6 instead of 1.5)
Click to expand...
Click to collapse
So, maybe, in the latest update (2.3.2, or whatever) Nexus S got this new 1.6 GPU driver with increased up to 30% performance?
Now this is getting interesting!
any more info about this ?
fake?
I think ots a fake or it was a special rom, i use darys rom with voodoo and have 2537
But wich driver the Cyanogen team use in their cyanogen mod7 ?
Their 3d driver score in quadrant pro is very impresive, nearly 30 to 40% more than stock froyo 2.2 rom.
I will try to ask the cyanogen team.
Kepp in touch
// oh your right
Well.. This really looks interesting.
Now this is interesting
Looking forward to this
Surprised someone with a little more knowledge hasn't commented on this yet. Hopefully we'll have an answer soon
In the meantime -> report here if the sources (I mean precompiled module, which will be inside the package) are online
jimmy72 said:
But wich driver the Cyanogen team use in their cyanogen mod7 ?
Their 3d driver score in quadrant pro is very impresive, nearly 30 to 40% more than stock froyo 2.2 rom.
I will try to ask the cyanogen team.
Kepp in touch
Click to expand...
Click to collapse
Are you sure? On my i9000 with CM7, quadrant 3D test even can't be finished normally.
Sent from my HTC Vision using XDA App
louyaorong said:
Are you sure? On my i9000 with CM7, quadrant 3D test even can't be finished normally.
Sent from my HTC Vision using XDA App
Click to expand...
Click to collapse
Gingerbread bug, same thing happens on the nexus s. I'm sure quadrant updated there app to work with gingerbread recently.
Sent from my GT-I9000 using XDA App
PaulForde said:
Gingerbread bug, same thing happens on the nexus s. I'm sure quadrant updated there app to work with gingerbread recently.
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
it seems that I need to upgrade my quadrant version.
Sent from my HTC Vision using XDA App
jimmy72 said:
But wich driver the Cyanogen team use in their cyanogen mod7 ?
Their 3d driver score in quadrant pro is very impresive, nearly 30 to 40% more than stock froyo 2.2 rom.
I will try to ask the cyanogen team.
Kepp in touch
Click to expand...
Click to collapse
What is your quadrant GPU score in CM? On JS5 2.2.1 i have 2d:293; 3d:879. Are CM scores really better?
SGX540 is much better GPU than the one used in Tegra 2.
So I guess these results are caused by the newer driver version (1.6) released by IT.
with mitra rom i have these score on quadran advanced:
overclocked to 1.3ghz (on set cpu min and max @1.3)
total score 3702
at stock 1ghz (on set cpu min and max @1ghz)
total score 2865
good score for me with this rom.
i thing that the driver are updated...
found this link at another site by user krylon360.
http://opensource.palm.com/3.0.2/index.html
Kernel: http://palm.cdnetworks.net/opensourc...nel-2.6.35.tgz
Kernel Patches: http://palm.cdnetworks.net/opensourc...35.patches.tgz
hoolahoous said:
found this link at another site by user krylon360.
http://opensource.palm.com/3.0.2/index.html
Kernel: http://palm.cdnetworks.net/opensourc...nel-2.6.35.tgz
Kernel Patches: http://palm.cdnetworks.net/opensourc...35.patches.tgz
Click to expand...
Click to collapse
given the amount of work the APQ8060 does - it seems that getting android with graphics support shouldn't be the hardest. Graphics is built into the cpu, what else? battery charging might be tricky, usb port, wifi?
The more the core CPU (APQ806) does - less driver work to get a similar device working. there's a good bit of devices that use the same SOC cpu . it would be cool if someone did a teardown to show the insides to see compare to phones/tablets and see what looks the most similar. I'd bet the touchpad is pretty reference design - to get it constructed so quickly they probably stuck to qualcomm's reference design
Here's what I posted on Reddit (context: "it should be doable"):
* The dual-core Qualcomm CPU, obviously
* Wifi: atheros 6003x (potentially same as Galaxy 5)
* Gyroscope: Invensense, who released a library for Android
* Sound: wm89583; hopefully close enough to wm8994 (Galaxy S)
* Bluetooth: Blucore 63T22. Ouch this one might be a problem.
cyansmoker said:
Here's what I posted on Reddit (context: "it should be doable"):
* The dual-core Qualcomm CPU, obviously
* Wifi: atheros 6003x (potentially same as Galaxy 5)
* Gyroscope: Invensense, who released a library for Android
* Sound: wm89583; hopefully close enough to wm8994 (Galaxy S)
* Bluetooth: Blucore 63T22. Ouch this one might be a problem.
Click to expand...
Click to collapse
Doesn't HP release the driver source along with the kernel source for their tablets? And are there any differences between drivers for a Linux kernel intended to run webOS and drivers for a Linux kernel intended to run Android?
Anyone notice the source seems to be a patch to the Android kernel? ....Is WebOS based off of Android?
Smith7018 said:
Anyone notice the source seems to be a patch to the Android kernel? ....Is WebOS based off of Android?
Click to expand...
Click to collapse
Duh. new high quality upstart mobile OSs are a branch of Android... Samsung bada too. I think they thought they could do it better or something.. noone one wants to work on a branch of a branch... they want to work on the trunk. That's why bass is destined to fail as well.
AdamOutler said:
Duh. new high quality upstart mobile OSs are a branch of Android... Samsung bada too. I think they thought they could do it better or something.. noone one wants to work on a branch of a branch... they want to work on the trunk. That's why bass is destined to fail as well.
Click to expand...
Click to collapse
Just to clear things a bit: this is not "Android kernel", it's linux kernel, that's what android was built on. There's no such thing as Android kernel. And Samsung's Bada was not built on top of it (unfortunately - it would be much easier to port android), it's built on Nucleus...
hoolahoous said:
found this link at another site by user krylon360.
http://opensource.palm.com/3.0.2/index.html
Kernel: http://palm.cdnetworks.net/opensourc...nel-2.6.35.tgz
Kernel Patches: http://palm.cdnetworks.net/opensourc...35.patches.tgz
Click to expand...
Click to collapse
Um, the hacking has been going on for over 2 years already ...
http://www.webos-internals.org/
-- Rod
rwhitby said:
Um, the hacking has been going on for over 2 years already ...
http://www.webos-internals.org/
-- Rod
Click to expand...
Click to collapse
nice necro!
anghelyi said:
Just to clear things a bit: this is not "Android kernel", it's linux kernel, that's what android was built on. There's no such thing as Android kernel. And Samsung's Bada was not built on top of it (unfortunately - it would be much easier to port android), it's built on Nucleus...
Click to expand...
Click to collapse
Bada is built on Nucleus, but is has links to Linux-community as Bada uses Enlightenment Libraries for some parts and apps.
Currently I have a Hauwei U8800, hence my choice of the forum category to post in. As mainstream is the Adreno 205 GPU, it's bottlenecking my 1.6Ghz OC Scorpion CPU (800Mhz Stock) a lot! I'm using N64oid v2.6.3, but it's just not good enough. Is there a better emulator or GPU overclocking app? I'm really dissapointed...
Moved To Q&A
Please post all questions in the Q&A section
N64oid is, as far as I know, currently the fastest emulator. I got halfway through the Deku tree using Oxygen at constant 1.2 GHz, if I remember correctly. Performance wasn't game-breaking, in my opinion.
Which ROM are you running? You could try a different one. I've tried a few and usually run an Antutu benchmark; I remember being particularly awed by the 3D performance of the CM7 ROM in this thread: http://forum.donanimhaber.com/m_57121700/tm.htm (use Google Translate if Turkish is Greek to you, like me)
I don't know why that particular version has such good 3D performance or whether or not it's just the libs it's using, but give it a try.
I don't really wanna flash 4 the third time but thanks
Sent from my U8800 using xda premium
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)
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://forum.xda-developers.com/show....php?t=2368497
Thanks for your efforts.
I'm trying to follow the link to your Desire thread and it seems it's broken.
Nevermind, found it: LINK
I think a kernel dev from the droid incredible 2 has a 3d gpu overclock in a kernel but I didn't use it in mine because I worry about the heat output being overclocked combined with that.
Sent from my ADR6400L using Tapatalk 2
disconnecktie said:
I think a kernel dev from the droid incredible 2 has a 3d gpu overclock in a kernel but I didn't use it in mine because I worry about the heat output being overclocked combined with that.
Sent from my ADR6400L using Tapatalk 2
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2372291
you must be referring to this...
Someone already showed me the commits
no one has managed gpu overclocking at all on any msm7x30/msm8x55 platform/soc devices
I saw it someone's git when I was building my kernel. I couldn't find useful posts about kernel stuff so I just looked for git accounts that were from similar devices.
Sent from my ADR6400L using Tapatalk 2
Probably Kangaroo Kernel based off of Beast Mode.
Oh ya that's the one. Been a while since i looked.
Sent from my ADR6400L using Tapatalk 2
Shaky156 said:
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://forum.xda-developers.com/show....php?t=2368497
Click to expand...
Click to collapse
I have an Inc2 id be willing to test on if you'd like...
Sent from my Maserati using XDA Premium
Everyone has been modifying the kernel graphics software layer platform data with values that dont make sense and are impossible more above with values that dont exist within thw graphics table anywayx
3d oc is abit more difficult
Devs + testers join IRC will make life easier
Irc freenode #s1gpuoc
I wouldn't recommend replacing those files in any current kernel directly. Since there is no github to see what the actual changes are isolated from the file, it's hard to say if all the changes made are compatible. Some of them were unnecessary, and simply added credits to a line that was unchanged (most likely because it has been updated since the original writing of the files).
https://github.com/StarKissed/stark...mmit/dc381024f122a114b770076e2992cd5097f5c47c <- The specific changes required
twistedumbrella said:
Does this include a sysfs interface to throttle the overclock?
https://github.com/StarKissed/stark...mmit/618b9e076f7b2c0a8f9f0c5733f61d4ef27261c0
Click to expand...
Click to collapse
There isnt any need for a sys fs at the moment due to the way qualcomm have made their msm7x30
Shaky156 said:
There isnt any need for a sys fs at the moment due to the way qualcomm have made their msm7x30
Click to expand...
Click to collapse
Any time values that aren't stock are being forced, it's good to have the option to turn it off but in this case it's only forcing stock values to persist so it doesn't really matter.
Sent from my Galaxy Nexus using Tapatalk 2
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