hey guys
ive recently flashed this kernel http://forum.xda-developers.com/showthread.php?t=975349
and im getting quadrant scores btw 1400 to 1600
is there any way to increase them
i read somewhere it can be increased by using some file named ' build.prop'
I am on Darky's 10.1 using DarkCore, and I'm getting about 1200 with EXT4 lagfixes enabled.
i used to get 1900 - 2100 back on stock froyo with OCLF 2.1
if it is only about increasing the quadrant score, you could download tegrak overclock tool from market and increase the CPU to 1.25 Ghz..
or, before that you can disable lagfix, switch to CF-root, enable all tweaks (including media stage someting), and then apply overclock and it ll hit around 2350 ...
use damians latest kernel.. quadrant scores of more than 3000 are reported(use jvp as ur firmware) hope this helps..
I just can't understand why people are so obsessed with quadrant scores??? Frankly with stock Rom with ext4 the normal score is around 1500 and with custom ROM you can get around 1700-1800 - that's it (and you can gain around 100 more by removing the journaling of the the ext4 system). Quadrant isn't reliable benchmark and people should stop striving to get higher quadrant scores.
Anyway - if you want high quadrant scores just enable stagefright if you don't mind not being able to play certain video and audio formats on your phone - at least you'll be able to brag about you scores.
quardrant scores shouldnt be an obsession..... but just merely a certain reference once in awhile....
ROM: Miui MCGv 6.13.1
Kernel: Neo7
Quadrant's Score: 1737
JunaidZaka said:
hey guys
ive recently flashed this kernel http://forum.xda-developers.com/showthread.php?t=975349
and im getting quadrant scores btw 1400 to 1600
is there any way to increase them
i read somewhere it can be increased by using some file named ' build.prop'
Click to expand...
Click to collapse
Try F1 JVP ROM as base and go experiment with speedmod kernels i got up to a stable 1.5Ghz with my phone (but very short battery life):
http://forum.xda-developers.com/showthread.php?t=1058814
Also make sure all apps and processes are closed using taskmanager. Then start Quadrant score i got around 2900+ using JVP.
ROM: Miui MCGv 6.13.1
Kernel: Neo7
Quadrant's Score: 1957
No OC but UV between -50 to -125
ROM: XXJVH
Kernel: GTO
Benchmark: 3268
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Mods need to start closing some of these Quadrant threads, because, there are way too many.
Quadrant scores are great, if you are simply chasing a placebo (or you want the opportunity to grow your ePenis). If you want a phone which is productive though, throw the benchmark in the bin and run a blind test.
You are only testing if Quadrant is faster, not if other applications are. It is possible that optimising for Quadrant may lead to other applications being dramatically slower (because Quadrant isn't detailed enough). You will notice that the Wikipedia article is almost exclusively about the inaccuracies of benchmarking, and that developers generally don't use standard benchmarks (almost every developer will use a test suite that pops out pages of "user unfriendly garbage").
Quadrant simply doesn't provide enough information to tell you what operations is faster.
An optimisation might yield a 6x speedup of directory creation, at the cost of a 2x file writing slowdown. If quadrant is coded poorly and weighs the tests equally, it might tell you the optimisation was worth it (it will be 4x speedup overall). However, in normal usage, you might write to files 10000x more than create directories, so in the real world, it might be actually slower.
It's even less worth it considering that the time most people waste running benchmarks, and optimising their phone (sometimes they spend an hour or so), is never regained in productivity gains again.
That is just an opinion though
Auzy said:
Mods need to start closing some of these Quadrant threads, because, there are way too many.
Quadrant scores are great, if you are simply chasing a placebo (or you want the opportunity to grow your ePenis). If you want a phone which is productive though, throw the benchmark in the bin and run a blind test.
You are only testing if Quadrant is faster, not if other applications are. It is possible that optimising for Quadrant may lead to other applications being dramatically slower (because Quadrant isn't detailed enough). You will notice that the Wikipedia article is almost exclusively about the inaccuracies of benchmarking, and that developers generally don't use standard benchmarks (almost every developer will use a test suite that pops out pages of "user unfriendly garbage").
Quadrant simply doesn't provide enough information to tell you what operations is faster.
An optimisation might yield a 6x speedup of directory creation, at the cost of a 2x file writing slowdown. If quadrant is coded poorly and weighs the tests equally, it might tell you the optimisation was worth it (it will be 4x speedup overall). However, in normal usage, you might write to files 10000x more than create directories, so in the real world, it might be actually slower.
It's even less worth it considering that the time most people waste running benchmarks, and optimising their phone (sometimes they spend an hour or so), is never regained in productivity gains again.
That is just an opinion though
Click to expand...
Click to collapse
Yes, your right and I know it but anyway is something that cans show something of the power of the phone. (sorry by the bad english).
Now, with Miui MCGv6.15 and the Neo7 kernel I've 1939 on Quadrant
Quadrant does not tell anything from speed and you can easily cheat on that test
galaxysdev said:
Quadrant does not tell anything from speed and you can easily cheat on that test
Click to expand...
Click to collapse
Right. But if the dev's or SGS owners don't cheat the test, it could be credible.
You are all alright , but aniway ..
Quadrant : 2843
Antutu Benchmark : 2543
JVP Deodex , Alpha Damian 1 2.2
alasth said:
You are all alright , but aniway ..
Quadrant : 2843
Antutu Benchmark : 2543
JVP Deodex , Alpha Damian 1 2.2
Click to expand...
Click to collapse
Which is your kernel?
[EDIT] I see it now. Sorry ^^
JunaidZaka said:
hey guys
ive recently flashed this kernel http://forum.xda-developers.com/showthread.php?t=975349
and im getting quadrant scores btw 1400 to 1600
is there any way to increase them
i read somewhere it can be increased by using some file named ' build.prop'
Click to expand...
Click to collapse
Okay wouldnt be a better question be whats the fastest rom?
Im still on GingerReal cause it is a combination of both a stable as a fast rom. Quadrant score of GingerReal isnt that high somewhere around 1500 - 1600. I never have forced closes and loading of files etc. go like crazy.
Tried CyanModGen and MIUI which are both great roms but they arent that stable and still have some minor known issues. I'll probably change my ROM until of one of the above have a stable rom.
What is working the best for u guys (and girls offcourse)?
Sent from my GT-I9000 using XDA App
thanks for all your replies guys
i think the better question wouldve been whats the fastest rom in terms of performance?
becuz i do experience a little bit of lag while playing some games
nrbuitenhius said:
Okay wouldnt be a better question be whats the fastest rom?
Im still on GingerReal cause it is a combination of both a stable as a fast rom. Quadrant score of GingerReal isnt that high somewhere around 1500 - 1600. I never have forced closes and loading of files etc. go like crazy.
Tried CyanModGen and MIUI which are both great roms but they arent that stable and still have some minor known issues. I'll probably change my ROM until of one of the above have a stable rom.
What is working the best for u guys (and girls offcourse)?
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
I will try that ROM
Related
Hello,
I take no credit for this at all. I saw it on the I900 post. and it works on vibrant. It gets rid of the sleep->awake lag.
NOTE: YOU MUST DO THE UNLAGFIX. DO NOT RUN THIS IF YOU HAVE NOT!
http://forum.xda-developers.com/showthread.php?t=760571
Author: RyanZA
Donation Link for him: https://www.paypal.com/cgi-bin/webs...=PP-DonationsBF:btn_donateCC_LG.gif:NonHosted
I wonder if a better place for this would be the Themes and APPS section...
I only say this bc it is an app...
I don't think so - I think the subject matter of this post and APP clearly deal with development as it pertains to the many lag fixes that are out now. Furthermore, any additional developments, questions, concerns, and problems would be much better address here by DEVELOPERS rather than the larger number of laymen who read the Themes and Apps section.
I am running Vibrant6 Eclair on my phone, and have ALWAYS had problems implementing any lag fix. Be it Ryan's one click, or MODACO's playlogos1 script hack. I've never been able to increase by Quadrant score, and have constantly run into "cannot read mounted card", "file already exists", i've even had the lag fix run all the way through, and had 890 quadrant scores.
This APP finally worked for me.
I installed the APK - then I "unrooted my phone" (option in the apk)
Then rebooted, then "re-rooted" my phone (with newest Busybox / SU )
Then rebooted, got into the phone, and ran this "one click app" again.
Chose "ONE CLICK LAG FIX"
Waited about 5-8 minutes, then phone auto rebooted.
I get on, run quadrant - 2125.
However, the phone seems to be running CHOPPIER and more SLUGGISH with regards to live wallpapers and home screen scrolling - whether or not the wallpaper is static or live. I was hoping that the lag fix, with such a high quadrant score, would make my phone UI run smoother (launcher pro) however, it doesn't seem to be the case. I have been using the phone for 3 hours now though, and not ONE single "hanging lag". Used to happen quite frequently - although for only 5-10 seconds and not overly annoying, still annoying to say the least.
Hopefully with the implementation of better roms, we will be able to get rid of this home screen lag issue.
Just wanted to confirm this lag fix works on my phone, running stock kernel, vibrant6 eclair. Just run the app and watch it go.
I can tell you from trying 10+ lag fixes.
This one is by far the BEST. Now I did not unroot. I dont know if that matterrs.
But i have a 2200+ Quad and the sleep->awake lag is GONE. and All the other lag is GONE.
I have no complains. Using a TMO vibrant here.
QUOTE=RyanZA; Ah, that issue! This lag fix will also take a long time to back up. It is not a different lag fix from the others, just a safer and easier to use lag fix. People who can already install the more advanced lag fixes should rather use those! This is aimed more at people who don't want the complications of those methods. = end quote
So people know, this is a simple ext2 lag fix... Most of the fixes in this forum are much more stable if you research... This app is for the lazy/ignorant if you don't know what you are doing or don't want to learn a better way of doing it... This is not a better/different fix... In fact this is a less stable lag fix..
Sent from my SGH-T959 using XDA App
Yeah I posted this on the market for RyanZA - just search for Galaxy S, Vibrant or LagFix it should pop up. I'm running his 2.3 LagFix which has a few more enhancements over the current Market app.
My more recent Quadrant:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Stock Kernel, RyanZA's 2.3 lagfix.
QUADRANT MEANS JACK $HIT... why is it constantly referenced as a good indicator?
Maybe everyone should flash cyanogens FAKE rom that had a 9k quadrant score, lol.
s15274n said:
QUADRANT MEANS JACK $HIT... why is it constantly referenced as a good indicator?
Maybe everyone should flash cyanogens FAKE rom that had a 9k quadrant score, lol.
Click to expand...
Click to collapse
Ok, give me a benchmark utility that you find as a good indicator, and I will post that instead. Just be sure to get your panties out of a wad when I do - ok?
Its not a bad benchmark app, especially when there are few variables.. But start comparing different phones and the free version is just an average of 4 different benchmarks... Our display is what has us at the top of the list.. Not cpu or memory..
Sent from my SGH-T959 using XDA App
Letting ya know this works..I first ran the Quadrant and for a 750 then I did not unroot or anything installed the tools and did the oneclick lag fix ran the Quadrant again and got 2042
s15274n said:
QUADRANT MEANS JACK $HIT... why is it constantly referenced as a good indicator?
Maybe everyone should flash cyanogens FAKE rom that had a 9k quadrant score, lol.
Click to expand...
Click to collapse
It isn't that bad of an indicator if you didn't purposely rigged up your phone to 'cheat' the system.
Here is a really good read on why I completely disregard Quadrant and the scores our lag fix generate. PLEASE READ THIS BEFORE ARGUING.
Curious, what are the linpack scores after the lag fix? Stock is low 8's.
s15274n said:
Here is a really good read on why I completely disregard Quadrant and the scores our lag fix generate. PLEASE READ THIS BEFORE ARGUING.
Curious, what are the linpack scores after the lag fix? Stock is low 8's.
Click to expand...
Click to collapse
The problem is that linpack only benchmarks the cpu, while the lag fixes address the i/o issue that plagues the vibrant, so linpack won't be a reliable solution either
s15274n said:
Here is a really good read on why I completely disregard Quadrant and the scores our lag fix generate. PLEASE READ THIS BEFORE ARGUING.
Curious, what are the linpack scores after the lag fix? Stock is low 8's.
Click to expand...
Click to collapse
The thing is thats benchmarking different things... Linpack only benchmarks the ability of the Virtual Memory I think... and the lag fix doesnt change anything but how the data is read/written, but we can tell how much of a difference it makes on the data rw speeds...
now doing a quadrant with a vibrant in one hand and a droid x in the other is too many variables.. bc we can only get the average of the four tests it does.... now if you had the pro version it would be a little different...
I have been running the without a lag fix since last sat... had the lag fix for a while before taking it off... I cannot tell a difference in the two... I think its just a placebo effect... but like its been said before, this phone is fast before any tweaking..
Apologies, I was not implying Linpack is a better BM... just curious if they got the same score. I assume they do then. I just wish people would quit acting like the quadrant score means something with this lag fix, it does not.
I would much rather have stability than a high quadrant.... I show someone a 2000+ and they dont care...
If the do care they pull out their phone and show me FULL FLASH on their JIT compatible 2.2 enable device and that it works with a score less than 1500.. Then the guy with the i*hone starts laughing at me for being a douche...
Does this let me change the font?
I've never had a lag problem with animations off. Only experienced some lag with animations turned "all on" . Try it . I don't think we really need this fix.
Sent using xda app....
You'll be surprised. I saw a huge difference after I applied this fix. What you think you don't need, and the difference you get after you apply this fix is huge.
Before in the android market I would get 'stalls'. Now I can go non-stop only stopping to fetch the next 20 or whatever apps.
What I'm trying to say is unless you try this fix, don't dismiss it. It is a huge boost in performance.
Yes, this fix is a true lag fix. It fixed my sleep-wake lag. it fixed it all.
Anyone running differnt versions I highly reccomend uninstalling it. and using this.
It makes your quad a BIT lower. maybe 10-20 pts. But, its HELLA stable and works like a charm.
http://board.teamwhiskey.com/viewtopic.php?f=3&t=53&start=0
Project is simple in design and is a work in progress, overclock as far as we can go with ample supplied voltage for maximum stability. These are the screenshots taken last night from the last few builds of the evening, were up to something like 40 builds so far trying to get everything just the way we want it to run, look, and feel.
Currently we are overclocking both the GPU and CPU using both base frequency modifiers and multipliers. This is allowing us to directly push the GPU to its stable limit while adjusting out the CPU accordingly.
Project Developers
Morfic and Viralblack of Team Whiskey. This is and will continue to be Morfic's baby until the phone prints money and/or can transform into a jet.
The Short and Long term goals are the following:
-To optimize the kernel with the best toolchains available to us
-Inject vital code enhancements for stability and to extend the feature set of the SGS Vibrant line
-To determine Min/Max Voltage, Bus Clock, and Multiplier values for Maximum Overclock and Maximum Effecient Overclock
-Continue to push the GPU to its theoretical maximum independant of CPU clock values.
Target Numbers and Current Results.
CPU Target 2.0GHz, Current Maximum Overclock 1.6 Stable (Time limitation only, havent rebuilt to try more)
GPU Target 85 FPS Stable Bench, Current 78 FPS
At current this is a JFD Stable build thats more than fairly bulletproof on battery life. To use with JI6 builds just flash Eugene's JFD/JI6 support package.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This is NOT a hoax or scam, these are real DDMS screenshots from the build currently in progress, as it has not yet been released we do not have code or kernels available until we know its running smoothly. The following zImage is a prerelease alpha. Its strictly for proof of concept. This kernel is mildly optimized and includes the CPU and GPU overclocks. In three of three test phones the CPU was stable, in two of three phones the GPU was stable. One test phone was not able to complete neocore under this coding.
Battery life has proven about the same as traditional OC/UV kernels. This is NOT our finished product, this is an Alpha for proof of concept for other developers. Run at your own risk. There is no failsafe, this does not require SetCPU to engage. It comes out of the box at 1.6GHz with steppings of 1,2,4,8,16
Currently, tested incorporations with the zMod have shown that overclocking renders the zMod unstable and bricks the device. I personally preferred to use RyanZAs OCLF v2.2 APK.
I had one out of 20 quadrant runs fail because I switched scheduler away from deadline. CFQ proved to be less stable for one reason or another when running quadrant.
This thread will be updated as work progresses, Do not flash this if you do not know what youre doing. Suggestions are welcome for integrated features you would like to see in this kernel, we will not however be fielding bug reports as this right now is staged as a Prerelease Alpha or RC0.
If when this is flashed your phone crashes and is unable to work, my suggestion is odin the stock kernel back in place and wait for a lighter overclock version to be released.
Download -
Removed while core is being rewritten
EDIT 10/28:
To update the project and to iterate why the download link was removed, the kernel seems to be misbehaving and we havent yet nailed down the correction as of yet.
As many people pointed out once it was released, the kernel seems to slow down 3D graphics. With this information and taking a day to go through all the options and data available to me, we discovered this issue isnt limited to just 3D graphics.
Imagine if you were running at 10MPH, and while you were running time slowed down but the slowdown didnt effect you. So youre still running at 10MPH but to the rest of the slowed down world, now youre running at 15MPH, even though your speed and direction havent changed.
The changes in the code for one reason or another arent playing nice with the Android system. Instead of pushing the clock up, in most cases, what its doing is simply slowing the internal clock down to the tune of about 30%. This is what is actually providing the benchmark gains that were being recorded, not an actual gain. This doesnt mean that the project is dead, we are recompiling to get a stable overclock with the new configurations. This doesnt mean the project was a failure, it just means we need to rewrite the alpha.
Edit 10/30 -
So, we are having distinct issues removing the timing error from the kernel while maintaining the integrity of the time system. So, being that the timing is much more important, we began rewriting it all from scratch. This is currently marked as Project Core in the same forums. Core is taking the best of the overclocking and fine tuning that this kernel has and combining it with energy effeciency and stability a daily driver phone needs.
So, we will be balencing the high end power thats desired and the low power use that is needed in this new project. With that being said, I dont believe that 1.6GHz (in my own humble opinion) is even remotely necessary for 99 percent of phone, let alone for daily use. This project is being succeeded by Core to make a power friendly daily driver kernel.
The kernel will still be available from the forums Alpha/Beta Download Section, but will not be supported as its being replaced by Core.
We found the redline Now we need to find the happy medium. If you enjoyed this release, youll love Core and Core with zMod.
Thread Locked until release, OP PM me when you want to release it
Good work TW
You guys should start working on a 2.2 version (Once you get this one smooth)
Thanks, but....
The processor already gets too hot at 1ghz.
I don't feel like cooking it just to say "hey wow, look how high I pushed it before it died".
Y'all really need to let people know that overclocking creates more heat and in the confined area of a tiny little cellphone there is next to zero cooling.
It's just asking for trouble.
Not that I don't appreciate the effort you guys are putting into the tweaks tho....
n2ishun said:
Thanks, but....
The processor already gets too hot at 1ghz.
I don't feel like cooking it just to say "hey wow, look how high I pushed it before it died".
Y'all really need to let people know that overclocking creates more heat and in the confined area of a tiny little cellphone there is next to zero cooling.
It's just asking for trouble.
Not that I don't appreciate the effort you guys are putting into the tweaks tho....
Click to expand...
Click to collapse
My phone never gets hot?
But they did put a warning, and you are the one modding your device.
Oh wow! This is great! I have an Epic 4g, will I be able to benefit from this awsome project?
Eazail70x7 said:
Oh wow! This is great! I have an Epic 4g, will I be able to benefit from this awsome project?
Click to expand...
Click to collapse
Hopefully yes, the kernel will be ported to all SGS Variants if possible, Right now we have in our possession Vibrants and Captivates, were looking to expand and will probably be working with other developers to get this kernel ported across.
Master™ said:
My phone never gets hot?
But they did put a warning, and you are the one modding your device.
Click to expand...
Click to collapse
Yeah, mine will get warm, but I've never seen it get real hot.
testing now . just flash with clockwork? this is super cool guys. props
blackerwater said:
testing now . just flash with clockwork?
Click to expand...
Click to collapse
Yes, its CWM flashable, but be careful with it. There is no failsafe, if your phone cant handle the overclock itll just crash as its set automatically to 1.6GHz topend
So far so good. Just got a linpack of 12.062. Outstanding job guys!
doesn't work yet. just sits on vibrant screen. its cool ill just flash back ji6 zimage then it should boot. im on stock ji6..... I have a vibrant that can handle 1.3mhz for sure and voodo so ill keep playing with it.
Will this run with stock ji6?
Thank you so much for uploading! I reread about it in phandroid and was about to ask around for it
Sent from my SGH-T959 using XDA App
I flashed again just to make sure . it wont boot on ji6 stock but my ji6 kernel works just fine. so maybe if i was running a bionix rom?
blackerwater said:
I flashed again just to make sure . it wont boot on ji6 stock but my ji6 kernel works just fine. so maybe if i was running a bionix rom?
Click to expand...
Click to collapse
Right now ive only tested it on Fusion personally
Viralblack said:
Hopefully yes, the kernel will be ported to all SGS Variants if possible, Right now we have in our possession Vibrants and Captivates, were looking to expand and will probably be working with other developers to get this kernel ported across.
Click to expand...
Click to collapse
Excellent. I hope you guys can get an Epic soon and work some magic. Also good to hear thatyou'll be working with other devs. Good luck
blackerwater said:
I flashed again just to make sure . it wont boot on ji6 stock but my ji6 kernel works just fine. so maybe if i was running a bionix rom?
Click to expand...
Click to collapse
I have stock JI6 rom but have the "backwards compatibility for JFD kernels" flashed so maybe that's it.
Have you tried flashing the back kernel support file for JI6 then flash this kernel?
Whitehawkx said:
I have stock JI6 rom but have the "backwards compatibility for JFD kernels" flashed so maybe that's it.
Click to expand...
Click to collapse
ok ill give that a shot. thanks
Will this work with voodoo?
Bionix Fusion 1.0 Jacs Xmod Oc/Uv Kernel Color fix Voodoo
Howdy,
I've been using the CM7 nightly builds for a while now and figured it'd be nice to have a kernel that's based on CM7 with overclocking, RAM hack and couple of other tweaks. This kernel is pretty similar to the volkKernel but I wanted to have my own
Changes:
* Overclocking up to 1500 mhz (only through pimp my cpu at the moment)
* Default I/O scheduler of NOOP
I'll try to keep it up to date with the latest CM7 kernel sources.
[Releases]
Third release based on nightly #114
http://www.mediafire.com/?r57gqyuvhujwk6g
Second release based on nightly #101
* Removed RAM hack
* Balanced out the CPU clock values a little bit
http://www.mediafire.com/?1waipap3c71hat3
Initial release based on nightly #79
http://www.mediafire.com/file/w3e0s3vxwtznclz/cm7_79.zip
very nice welcome on board ^^
fallout0 said:
Howdy,
* Overclocking up to 1500 mhz (only through pimp my cpu at the moment)
Click to expand...
Click to collapse
Can't use setcpu?
i would like to use OC via CMParts ^^
Hmmm pardon me for asking, but why is it a 32mb RAM hack now instead of 64mb? Is it to resolve the gallery bugs?
I am using the original cpujauste o/c code that's why it only works with pimp my CPU. ill look into the others tomorrow to get that working
The 64mb hack caused issues for people with 1080p recording and the gallery. ill try it again and see how it works
ok, i found some bugs.
1. Reboot doesn't work. I guess thats because of the 32MB Ram Hack (for the vorkkernal, reboot doesn't work either)
2. After running a couple of hours, you only get around 50% of your CPU performance. Maybe the scheduler isn't optimized well. I recognized it by playing n64oid and it has lagged. Also I only get 3900 points at Antutu instead of ~5000 points.
ranrick said:
ok, i found some bugs.
1. Reboot doesn't work. I guess thats because of the 32MB Ram Hack (for the vorkkernal, reboot doesn't work either)
2. After running a couple of hours, you only get around 50% of your CPU performance. Maybe the scheduler isn't optimized well. I recognized it by playing n64oid and it has lagged. Also I only get 3900 points at Antutu instead of ~5000 points.
Click to expand...
Click to collapse
I think it's actually booting at ~700mhz by default so unless you set it up in pimp my cpu it'll stay at ~700 mhz. Probably why it's lagging.
We need more people working on kernels, thanks for doing so. Any improvements on battery life? Personally I find CM7 battery life to be pretty bad.
fallout0 said:
I think it's actually booting at ~700mhz by default so unless you set it up in pimp my cpu it'll stay at ~700 mhz. Probably why it's lagging.
Click to expand...
Click to collapse
Yep, now running with 1ghz again ^^
Can i request Voodoo Sound support?
Hey fallout0,
Nice work mate.
I think the general consensus is to not have the 64mb hack in kernels judging from a couple of poles about only 20% wanting the hack, probably less now.
I prefer to not have the hack at all imho, far too many instabilities for zero gain that being said I have yet to find a completely stable o/c kernel to use - stock seems to be the only completely stable kernel.
Be trying yours later on today so keep up the good work!
-smc
somemadcaaant said:
Hey fallout0,
Nice work mate.
I think the general consensus is to not have the 64mb hack in kernels judging from a couple of poles about only 20% wanting the hack, probably less now.
I prefer to not have the hack at all imho, far too many instabilities for zero gain that being said I have yet to find a completely stable o/c kernel to use - stock seems to be the only completely stable kernel.
Be trying yours later on today so keep up the good work!
-smc
Click to expand...
Click to collapse
Hey
Cheers
The ram hack and even overclocking support are pretty nasty hacks. Having said that I like the ability of adjusting voltages/maximum frequencies and until there is a better solution I think it's worth having this one
I agree about the RAM hack. I tried volkKernel and besides the reboot issue I didn't have any problems with the 32mb RAM hack. However the extra 32mb of RAM might not even be that useful.
I'll see how things pan out with this one then remove/add things as people complain
fallout0 said:
Hey
Cheers
The ram hack and even overclocking support are pretty nasty hacks. Having said that I like the ability of adjusting voltages/maximum frequencies and until there is a better solution I think it's worth having this one
I agree about the RAM hack. I tried volkKernel and besides the reboot issue I didn't have any problems with the 32mb RAM hack. However the extra 32mb of RAM might not even be that useful.
I'll see how things pan out with this one then remove/add things as people complain
Click to expand...
Click to collapse
Can't the reboot issue be easily resolved? According to RC, the bootloader expects the reboot-information to be at 128MB + 11 bytes, while the system writes it to [MB Reserved for Graphics]+11 bytes. As long as no ram-hack is applied, it'll of course be in the right place. Shouldn't it be easy for a kernel to just copy what is at [MB RESERVED]+11 to [128MB]+11 before shutdown?
Just talking by the seat of my pants here, haven't looked at any of the sourcecode, but it certainly feels feasible.
::Trym
I wish for that kernal:
- option on 32mb hack
- AVP/SD ram OC
- CMPart OC settings
thats it ^^
He-hey!))) This kernel is almost burnt my phone off.... Came upstairs after the dinner and found the phone off and very-very hooot... So, now I'm waiting for it to cool down a bit... Hope it'll turn on again)))
Update: Thank God that it didn't turn into BRICK))) Came on again and I've flashed it back to vorkkernel.
I am using MIUI ROM.
Very good works!! I have now tested with CM7 ROM "nightly full-77" version.
Fantastic Quadrant Score!!!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
TrymHansen said:
Can't the reboot issue be easily resolved? According to RC, the bootloader expects the reboot-information to be at 128MB + 11 bytes, while the system writes it to [MB Reserved for Graphics]+11 bytes. As long as no ram-hack is applied, it'll of course be in the right place. Shouldn't it be easy for a kernel to just copy what is at [MB RESERVED]+11 to [128MB]+11 before shutdown?
Just talking by the seat of my pants here, haven't looked at any of the sourcecode, but it certainly feels feasible.
::Trym
Click to expand...
Click to collapse
I thought about it, and decided against it. Writing random information into active RAM is never a good idea.
so far so good with this kernel on RC1...
we want more OC !!!
moooooooore!
Hi, a friend came by and asked me to optimize his tegra. Thanks for faux123, we have an OC kernel. Made the following changes
1. Added JRCU with lazy to optimize RCU implementation of dual cores
2. Made INTERACTIVE (not powersave) default by making changes in cpufreq drivers
3. Made noop default (can be changed in ROM)
4. Overclocked settings from 216mhz - 1400000 mhz with voltage from 750mv - 1350 mv
5. AVP/VDE overclocked to 300000 mhz
6. GPU overclocked to 400000 mhz
7. Memory speed set at 333000mhz
8. Optimized utilization of dual-cores (cpu0 and cpu1) by making changes in how cpu1 is called.
9. Reverted a few changes in the overclocking code
Again, thanks to faux123 he saved me a lot of time and made things a lot easier.
WARNING:
These timings are pretty aggressive and might not work for your atrix that is why I called it elite (fortunately my friend's Atrix handled the timings pretty well) so please backup.
-----------------------------------------------------------------
-----------------------------------------------------------------
Update: 2/6/2012
1. Increased cyanogen overclocked speed to 1.6ghz!!!
Link:
www.tunerspotter.com/clemsyn/Ultimate1.6eliteCyano.zip
-----------------------------------------------------------------
-----------------------------------------------------------------
Update: 1/30/2012
1. Updated to 2.6.32.55 (Thanks faux123)
2. Build for ATT and Cyano at 1.5 GHZ
ATT 1.5 ghz kernel
www.tunerspotter.com/clemsyn/ClemsynATT1.5elite.zip
Cyanogen 1.5 ghz kernel
www.tunerspotter.com/clemsyn/ClemsynCyno1.5elite.zip
BTW, if you like my work, please
and help me buy some diapers. Thanks.
-----------------------------------
-----------------------------------
UPDATE: 1/28/2012
1. Increased overclocked to 1.5 ghz
2. Only for Cyanogenmod ROMs at the moment
www.tunerspotter.com/clemsyn/ClemsynCyanoElite1.5kernel.zip
-----------------------------------------------------------------
-----------------------------------------------------------------
UPDATE:
1. Updated to 2.6.32.48 with faux123 optimizations and changes
2. Added 1.0 ghz kernel for both att and cyanogenmod
3. Added a few optimizations in interactive governor to improve CPU sleep and wake
4. Added 1.4 ghz for att
5. Added 1.4 with aggressive memory timings for Cyanogen
ATT VERSION 11/22/2011
1.0 ghz ELITE version
www.tunerspotter.com/clemsyn/ClemsynATT1.0elite.zip
1.4 ghz ELITE version
www.tunerspotter.com/clemsyn/ClemsynATT1.4elite.zip
Source
www.tunerspotter.com/clemsyn/kernel2.tar.gz
--------------------------------------------------------------------------
CYANOGEN VERSION 11/22/2011
1.0 ghz ELITE version Cyanogen
www.tunerspotter.com/clemsyn/ClemsynCyanoElite1.0.zip
1.4 ghz ELITE version Cyanogen
www.tunerspotter.com/clemsyn/ClemsynCyanoElite1.4.zip
1.4 GHZ Elite version with a more aggressive memory timings Cyanogen
www.tunerspotter.com/clemsyn/ClemsynCyanoElite1.4memorytimings.zip
BTW, if you like my work, please don't hesitate to click on the donation button under my sig and help me buy some diapers It will be appreciated. Thanks.
------------------------------------------------------------------------
------------------------------------------------------------------------
Older version
www.tunerspotter.com/clemsyn/ClemsynCyanogenElite.zip
I suggest you use system tuner in the market to tweak voltages/governor/io scheduler and SD cachesize
SOURCE : www.tunerspotter.com/clemsyn/kernel.tar.gz
BTW, if you want 1ghz or 1.2 ghz max overclock here are the steps.
Install system tuner ==>Tweaks===> CPU and bring the top slider down to your desired speed (1ghz or 1.2 ghz) and that will prevent the phone from going higher your desired speed
BTW, if you like my work, pls dont hesitate to click on the donate button under my sig. Thanks.
It says "elite", but do you know how many people are going to flash this (that shouldnt be flashing this) and flood this thread with "noob questions"?
God speed my friend, God speed...
andrew.cambridge said:
It says "elite", but do you know how many people are going to flash this (that shouldnt be flashing this) and flood this thread with "noob questions"?
God speed my friend, God speed...
Click to expand...
Click to collapse
I have no issue with noob questions, BTW, I am a kernel dev for Gtablet, Adam and Asus Transformer so this is not my first release and I am familiar with the kernel code for the tegras
Any wifi issues?
Sent from my MB860 using XDA App
Took it for a spin just now. -100mv on all levels undervolt. Quadrant completed 3x with no issues. Best score was 5024
On nightly 19
*edit* 150 and 200mv under lock my phone instantly but -100 on all levels seems rock solid and the phone feels snappy. Ill report back tomorrow night after a day of normal use (unless something else to flash comes out)
Sent from my MB860 using Tapatalk
Whoever tries this kernel out, please post back results of what its currently doing and a few days after. I would personally try it but, my phone needs to be stable for my job and college.
Sent from my Atrix XDA Premium App
Voelker45 said:
Whoever tries this kernel out, please post back results of what its currently doing and a few days after. I would personally try it but, my phone needs to be stable for my job and college.
Sent from my Atrix XDA Premium App
Click to expand...
Click to collapse
Flashed this on nightly build #20 ended up not booting so I cleared the caches again and next restart put me in an endless bootloop. Restored my backup gonna try a different cyanogen build with this. Anybody who has success please let everyone know what cyanogen build you are on? Gonna try this with the weekly build next.
flashing now. will update back.
Sweet Welcome!
Awesome. UVed -170 on all for now. -175 randomly rebooted after a couple minutes. Gonna work myself down until it's stable. Knowing that every step is going to be UVed to the max 100 mV limit makes UVing a LOT easier. You only have to worry about the top step.
d11dog11 said:
Took it for a spin just now. -100mv on all levels undervolt. Quadrant completed 3x with no issues. Best score was 5024
*edit* 150 and 200mv under lock my phone instantly but -100 on all levels seems rock solid and the phone feels snappy. Ill report back tomorrow night after a day of normal use (unless something else to flash comes out)
Sent from my MB860 using Tapatalk
Click to expand...
Click to collapse
I couldn't go past -100 either but it was stable at that level. Pretty solid Antutu ratings: 6539, 6767, 6774
I'm sure if I pushed it I could do better, however that hammered stability pretty well. We'll see how it goes battery-wise as well. Thanks for the upload!
Is there any chance you can make a 1.5ghz version? Not for all use but it would be fun to have. I know Kholk has one so isn't it possible?
Successfully flashed. I notice smoother screen transitions and scrolling. Not placebo, as the previous at 1.45 ghz had a very slight lag time when swiping to a different home screen. Also nice bench score on cf-bench (7800s) Thank you very much!
Just it UV'd -150 on all, hammering CF-bench. Looking pretty stable so far, and I like how it handled Quadrant earlier, I saw some positive spikes in FPS and it was smoother overall. I don't put much stock in Quadrant tests but nonetheless. Will throw up some Nenamark test as soon as I'm done hammering CF-bench.
faux123 said:
Sweet Welcome!
Click to expand...
Click to collapse
Big Thanks to you I won't be developing much for the atrix since I just developed it for my friend but I just wanted to share what I made. Currently uploading the source (Ive got a really slow internet)
clemsyn said:
Big Thanks to you I won't be developing much for the atrix since I just developed it for my friend but I just wanted to share what I made. Currently uploading the source (Ive got a really slow internet)
Click to expand...
Click to collapse
It gives us something to play with. I'm more of a 1.0GHz Blur-oriented ROM user but I like new toys, and thank you for uploading it for us junkies.
BravoMotorola said:
Is there any chance you can make a 1.5ghz version? Not for all use but it would be fun to have. I know Kholk has one so isn't it possible?
Click to expand...
Click to collapse
I actually though about pushing it to 1.6 ghz but was very hesitant since I didn't own the device and it didn't have enough room in there the disipate the heat. I just played safe with 1.4 but 1.5 should be no issue. If I get the chance to get the atrix again, I'll try to push it to 1.6 and make one for att gingerbread.
Nenamark 1: 57.2fps
Nenamark 2: 27.5fps
Great scores for an Atrix!
clemsyn said:
I actually though about pushing it to 1.6 ghz but was very hesitant since I didn't own the device and it didn't have enough room in there the disipate the heat. I just played safe with 1.4 but 1.5 should be no issue. If I get the chance to get the atrix again, I'll try to push it to 1.6 and make one for att gingerbread.
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Flashed... running fine so far, will report back. THANKS TO THE OP & FAUX!
Sent from my Atrix awaiting CM9....
Users can feel free to post their benchmarks here
Here's some of my benchmarks:
- Tests were ran from [ROM][STOCK IMAGE]Android 4.1.1 (JRO03D) ROOT, Deodexed, Busybox
- Testing done with latest Quardrant Standard
- Battery, Dalvik, and Cache were all wiped after installing kernel from zip in CWM
- Kernels tested were all the latest and highest-OC'd versions available as of 8/7
- No governers, schedulers, or clock speeds were altered from default values (I plan to reupload screenshots of performance later)
[KERNEL][GPL][Linaro][OC 1.624GHz][UV][GPU+][ZRAM][SIO+V(R)] 2012-08-03 motley 1.0.12 (GPU 520, build 175)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Kernel[006]AP33(1.55Ghz Quad)UV,CIFS+UTF-8,PowerHAL,Linux-3.x Hybrid [Aug-04] (Ultimate Edition)
[DER KERNEL] Trinity Seven (TS-1640-ALPHA41)
Stock
Note to self get an HTC One X, man thats a fast phone
Quadrant is very inconsistent with benchmarks. I would suggest Antutu/CFBench/Nenamark/GLBenchmark/RL Benchmark as being more accurate.
Sent from my Nexus 7
If you use TKT with trinity it blows the One C X away
you can do it via the terminal but idk the code and I already had TKT
Sent from my Nexus 7 using xda app-developers app
I've never seen a trinity kernel score that low. Most people score more than double overall of what you posted. Plus your I/O scores are warped. People scoring in the 7000-11,000 range. You not benching your device properly or something or using the wrong settings. Those are the worst scores I've seen posted on a nexus 7..lol.
Main tip for benching: put device in performance mode or at least ondemand. Even on stock governor, I've seen majority score higher than you. Just take a look at majority of posted benchmarks and you will see you don't have something right set up on your device.
You making those kernels look bad. Check mines out and it wasn't even on the highest setting. This is with trinity kernel OC to 1.5ghz. Stock rom and stock gpu speed.
I've never seen Motley, Infinity kernel, faux, or even stock score as low as what you have..lol.
the last quadrant I posted was on motley kernel.
huge difference in my scores and yours. plus mines on the lower end because I only benched at 1.5ghz. if I would've went top speed, scores would be even higher. we have people now benching close to and over 7000-7100 overall on quadrant. it blows any other android device out now. so much so there's been several tech news stories on how nexus 7 is blowing away other higher end android devices in benchmarks.
p.s. my nenamark2 score is 64.7fps
also I know quadrant can be inconsistent but those scores you posted still suspiciously low for those kernels they supposedly are from.
Just did 3 more ones. Stock rom. Trinity kernel CPU speed 1.5ghz. Performance governor and deadline scheduler
I find chainfire bench to be one of the best. doesn't rely on fancy graphics testing and such. this tests more raw power. as you can see, I beat out the new Samsung galaxy S3 with its 32nm high speed chip. remember also, we still in infancy stage of nexus7 development and we blowing away all benches & devices(Android) already. pretty good for a $199-249 tablet huh? lol. this performance level also translates to real world use. not just for show.
how are you getting such high scores? mine are always around 4600.. running at 1600 with trinity. doesnt make sense that yours are so high? highest ive seen by a good ways.
You’re very professional.
demandarin said:
I've never seen a trinity kernel score that low. Most people score more than double overall of what you posted. Plus your I/O scores are warped. People scoring in the 7000-11,000 range. You not benching your device properly or something or using the wrong settings. Those are the worst scores I've seen posted on a nexus 7..lol.
Main tip for benching: put device in performance mode or at least ondemand. Even on stock governor, I've seen majority score higher than you. Just take a look at majority of posted benchmarks and you will see you don't have something right set up on your device.
Click to expand...
Click to collapse
When I benched, I just had everything set at default settings (didn't change governers, clocks, or anything).
espionage724 said:
When I benched, I just had everything set at default settings (didn't change governers, clocks, or anything).
Click to expand...
Click to collapse
when you benchmark, use highest cpu/highest cpu. if you dont set it there, you let your device decide what cpu speed it actually wants to use, therefore you have no idea what cpu speed you are benching. for all you know is that on one bench it might be benching 1100mhz, on another it might be benching less or more. btw, those benchmarks are horrible, my galaxy nexus benchmarks higher
simms22 said:
when you benchmark, use highest cpu/highest cpu. if you dont set it there, you let your device decide what cpu speed it actually wants to use, therefore you have no idea what cpu speed you are benching. for all you know is that on one bench it might be benching 1100mhz, on another it might be benching less or more. btw, those benchmarks are horrible, my galaxy necus benmarks higher
Click to expand...
Click to collapse
Would setting ROM Toolbox to use the highest CPU frequency + performance be acceptable? Or should I use another program to ensure the CPU is at highest?
Edit: After doing that:
Total, CPU, Mem, I/O, 2D, 3D
Trinity: 4142, 12791, 3737, 1387, 332, 2464
Faux: 4457, 14257, 3890, 1339, 333, 2465
Motley: 5846, 15184, 3618, 7191, 300, 2935
Tests done from Glazed JellyBean 1.12
Those scores still seem worse then what some others have said though. Is there anything else I should be doing?
Sadly I have to flash back to stock kernel to make the wifi functionally. But sure the motley kernel is pretty attractive on its performance and addons.
espionage724 said:
Would setting ROM Toolbox to use the highest CPU frequency + performance be acceptable? Or should I use another program to ensure the CPU is at highest?
Edit: After doing that:
Total, CPU, Mem, I/O, 2D, 3D
Trinity: 4142, 12791, 3737, 1387, 332, 2464
Faux: 4457, 14257, 3890, 1339, 333, 2465
Motley: 5846, 15184, 3618, 7191, 300, 2935
Tests done from Glazed JellyBean 1.12
Those scores still seem worse then what some others have said though. Is there anything else I should be doing?
Click to expand...
Click to collapse
I find system tuner to be the best for those type of settings. If you run trinity kernel though, you will get more out of it by using the trinity kernel app in playstore that lets you tweak things in their kernel that even apps like system tuner can't do. But overall system tuner is the best, IMO. Its more in depth than most apps of THST nature.
Also best to use performance governor. Or on demand. Then use deadline or sio as the scheduler.
x-magic said:
Sadly I have to flash back stock kernel to make the wifi functionally. But sure the motley kernel is pretty attractive on its performance and addons.
Click to expand...
Click to collapse
Nothing wrong with wifi on motley kernels. Which build were you running? His latest runs great and no issues. Trinity kernel wifi works perfect also.
This is my score using latest trinity build 41 and pure aosp ROM.
Sent from my Nexus 7 using xda premium
saadi703 said:
This is my score using latest trinity build 41 and pure aosp ROM.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
as with others i max out at 46XX on quad if i am lucky and thats using system tuner and putting min/max sliders to 1.6 and performance gov. are you guys doing any other kernel tweaks to get these numbers
xspeed9190 said:
as with others i max out at 46XX on quad if i am lucky and thats using system tuner and putting min/max sliders to 1.6 and performance gov. are you guys doing any other kernel tweaks to get these numbers
Click to expand...
Click to collapse
I used trinity kernal build 41 with pure aosp rom. I used trinity kernel toolbox app from play store to tweak it. It is a paid app and if you don't want to buy the app then you have to use scripts but to keep things simple I used the app.
I clocked the processor to 1640 MHz, put the governor to performance which means processor would run at 1640 always. I/O scheduler to deadline and in tunable I select Fsync to faster. Good luck
Oh I forget to mention that good thing about Trinity kernel toolbox app is that you can use it with any kernel not only with trinity. The CPU temp widget is also good
Sent from my Nexus 7 using xda premium
Quadrant scores are meaningless. There are so many ways that they can be artificially inflated. I suspect that the scores in the 4000 range are the ones that truly reflect the overall performance of the device. 6000+ scores are obviously not realistic scores. Look at the IO scores, 10000 is a bogus 10x improvement over stock. No setting change anywhere is going to improve your IO performance 10x.
hecksagon said:
Quadrant scores are meaningless. There are so many ways that they can be artificially inflated. I suspect that the scores in the 4000 range are the ones that truly reflect the overall performance of the device. 6000+ scores are obviously not realistic scores. Look at the IO scores, 10000 is a bogus 10x improvement over stock. No setting change anywhere is going to improve your IO performance 10x.
Click to expand...
Click to collapse
someones feeling small..
TS-ALPHA50 + Glazed Jellybean v1.12
espionage724 said:
TS-ALPHA50 + Glazed Jellybean v1.12
Click to expand...
Click to collapse
better :victory: