Hi guys, here is my first kernel for the Galaxy Tab Pro 8.4 WiFi edition.
I'll update this post to look prettier and with more information regarding the kernel but for now--here it is. This kernel is based solely on stock with tweaks. I do this to keep it as stable as the stock kernel as possible. There will be no features added that may impact stability because I am also keeping it as close to Samsung source as possible. But it does include a few things: Overclocking up to 2.72GHz, GPU overclocking support, voltage table support, removed debugging, and random tweaks here and there.
Please remember that all phones are not equal and choosing a frequency over stock (2.26GHz) can introduce instabilities, but it is not due to a crappy kernel or crappy coding. I've tried my best to calculate my overclocking voltages based on the stock voltage table.
Also, please leave feedback on your experience, requests, dislikes, pretty much anything you can so I can know what I need to do with this kernel to improve it.
For those who want to see what CPU BIN you have (the higher the better) run this command, from adb or terminal: cat /sys/devices/system/soc/soc0/soc_pvs
Post your results and I will try my best to reply to them with information on your particular CPU. The results will be a single number ranging 0-6.
Huge thanks to imoseyon and morfic for all of their help, support, and general awesomeness.
Other thanks: Faux123.
SpeedBurst? Yup! You may notice that your CPU spikes up to 2.3GHz (Roar) or 2.41GHz (Rage) occasionally. This is "SpeedBurst," and is meant to give you that extra burst of speed when you need it most lol. These two frequencies are given the most performance increases because it is assumed that most, if not all Tab Pro 8.4s can handle it since it is such a small step up from the stock 2.26GHz frequency.
Features:
Overclocking support. (up to 2.72GHz)
Voltage table support.
GPU overclocking up to 600MHz.
NTFS Support.
Interactive and OnDemand governor tweaks with cpufreq_screen_off support.
FauxSound.
More.
BeastMode is now being released with 3 versions:
CALM: This is essentially CatMode but with all other non OC/UV related tweaks done as well. This means no L2 or bus changes, but all other changes are included.
ROAR: This is a step up and includes a slight bump for L2 with a slightly higher L2 in frequencies 2.3-2.41 GHz. (Most tablets should handle this fine.)
RAGE: This is BeastMode in its current form with a heavy bump for L2 as well as bus with the highest bump in frequencies 2.3-2.41 GHz.
Keep in mind that voltages, L2, and bus speeds are and will always remain stock for all frequencies up to 2.26 GHz for all versions of BeastMode.
Source: Here
KitKat 4.4.2:
Stable kernel ROAR version 1.0: Download here
Rage and Calm coming soon.
Beta kernels:
I've started to post beta versions of the kernel before stable release. These may introduce issues, but more than likely the issues will be small.
KitKat 4.4.2:
None.
Stable changelog:
6/1/14-1.0-KitKat:
Initial release
XDA:DevDB Information
BeastMode Kernel for Galaxy Tab Pro 8.4 T320, Kernel for the Samsung Galaxy Tab Pro 12.2, 10.1, 8.4
Contributors
freeza
Kernel Special Features:
Version Information
Status: Stable
Current Stable Version: 1.0
Stable Release Date: 2014-06-01
Created 2014-06-01
Last Updated 2014-09-02
Fantastic news - first TW kernel for T320.
Thank you for your hard work!
The beast mode kernel is what this device needed, getting better overall performance, and noticeable performance improvement in Asphalt 8.
Pls continue this fantastic work!
:good:
Thanks for the kernels. Greate for us with a T320, Thanks again.
A question, how/where i can download the different Beastkernels versions downunder? I tried soures but just got this downloaded "BeastModeKernel-ROAR-1.0-T320"
CALM: This is essentially CatMode but with all other non OC/UV related tweaks done as well. This means no L2 or bus changes, but all other changes are included.
ROAR: This is a step up and includes a slight bump for L2 with a slightly higher L2 in frequencies 2.3-2.41 GHz. (Most tablets should handle this fine.)
RAGE: This is BeastMode in its current form with a heavy bump for L2 as well as bus with the highest bump in frequencies 2.3-2.41 GHz.
What program do you recommend for set up the kernel? At the moment I use Trickster
lasset said:
Thanks for the kernels. Greate for us with a T320, Thanks again.
A question, how/where i can download the different Beastkernels versions downunder? I tried soures but just got this downloaded "BeastModeKernel-ROAR-1.0-T320"
CALM: This is essentially CatMode but with all other non OC/UV related tweaks done as well. This means no L2 or bus changes, but all other changes are included.
ROAR: This is a step up and includes a slight bump for L2 with a slightly higher L2 in frequencies 2.3-2.41 GHz. (Most tablets should handle this fine.)
RAGE: This is BeastMode in its current form with a heavy bump for L2 as well as bus with the highest bump in frequencies 2.3-2.41 GHz.
What program do you recommend for set up the kernel? At the moment I use Trickster
Click to expand...
Click to collapse
The links to Calm and rage appear forthcoming.
As to programs, I use SetCPU for one profile set at boot, utilizing charge state as the event trigger, and Trickster for overall CPU and GPU overclocking.
Sent from my SM-N900P using Tapatalk
micmars said:
The links to Calm and rage appear forthcoming.
As to programs, I use SetCPU for one profile set at boot, utilizing charge state as the event trigger, and Trickster for overall CPU and GPU overclocking.
Sent from my SM-N900P using Tapatalk
Click to expand...
Click to collapse
Ok, thank you!!
My CPU BIN 2
Gesendet von meinem SM-T320 mit Tapatalk
I am using Trickster Mod to set the max CPU freq to 2.419 GHZ, and GPU freq to 600 MHZ.
This gets an Antutu Score of ~ 37,000, higher than the new Galaxy S5.
The lags in the transition animations also disappears with the GPU overclock.
{
"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"
}
No GPU or CPU Overclock. I am using Android Tuner for more Option.
Gesendet von meinem SM-T320 mit Tapatalk
Great news! First kernel! :good:
a Mandroid can you make test with 3dmark at the same frequency?
Just wanted to say I've been running Roar all day and it's fantastic. No lag whatsoever. Apps open instantly. Well done!
Sent from my SM-T320 using XDA Free mobile app
killflaker said:
Great news! First kernel! :good:
a Mandroid can you make test with 3dmark at the same frequency?
Click to expand...
Click to collapse
Using the Roar Kernel (2.419Ghz CPU and 600 MHZ GPU) and Stock Samsung ROM, the 8.4 Wifi Tab pro gets a 3D Mark score of ~16,090 and Antutu score of ~ 37,600
The difference may not be much in terms of numbers, but enough to make a noticeable improvement in user experience.
Thanks, me with all stock i have 15800~ in 3dmark and 36000 in antutu.
For comparaison, you have a real gain in physics score, oc cpu ok but no gain with gpu.
Same result, Gt1 76,6fps and Gt2 59,7fps.
Any plans to compile this kernel for the other two version of the tab?
Will you offer this kernel for the lte version of the 8.4 Tablet? SM-T325
This would be awesome
Wipe dalvik and cache, then flash in recovery? Thanks...
Sent from my HTC_Amaze_4G using XDA Free mobile app
+1 for SM-T325 Tab Pro 8.4 LTE
Add SM-T325 support pls
I have to give the OP a thanks even though I run an AOSP ROM (the ported SlimKat), just for starting the custom kernel party.
From my Pro Tab 8.4
Hey I made this install video of your cool kernel check it out here hope you like it and feel free to place it in the OP if you want to
http://youtu.be/gXv1THycwew
Related
So, for all us CM7 users, there have recently been alot of questions as to why there is such a disparity between the stock CM7 kernel, and the 1.1Ghz kernel, given both are made by the same person (dalingrin). Really, there are two questions -
1) Why is the quadrant score different between the kernels?
2) How does this equate to real-world use?
To help answer #1, i went ahead and purchased a copy of Quadrant Advanced. The advanced version lets me run the bench offline (helpful at work ), and also shows each piece of the score (the important part, as seen in the results). this breakdown shows where the difference is.
But to answer #2, I have to go well beyond Quadrant, and look at many different benches. I tried to find a variety of both system and 3D benches in a hope to uncover any problems anywhere. If there is a more widespread problem, it may be uncovered in other benchmarks. So, without further ado, the test system:
CM7- nightly 27, running on eMMC
Stock CM7 Kernel, 925Mhz, Performance Governor
OC CM7 Kernel, 1000Mhz, Performance Governor
OC CM7 Kernel, 1100Mhz, Performance Governor
I kept the gov on performance, to help rule out any differences between governors. Performance runs the CPU at full speed all the time, so it keeps the benches comparable. For every CPU speed/kernel change, i rebooted the system, and ran each bench once in the order listed. And the results!
Stock kernel
CPU @ 925, Performance gov,
Quadrant (First run only):
Total: 1536
CPU: 2504
Mem: 1080
I/O: 3629
2D: 188
3D: 278
Linpack:
12.078Mflops
NenaMark:
16.7 Fps
Benchmark PI (https://market.android.com/details?id=gr.androiddev.BenchmarkP):
Pi found in 1636ms
Antutu System benchmark (https://market.android.com/details?id=com.antutu.ABenchMark):
Total Score: 1675
Memory: 407
CPU Integer: 578
CPU Float: 129
2D Graphics: 100
3D Graphics: 276
Database IO: 10
SD Card Write: 5.0 MB/s
SD Card Read: 12.5 MB/s
An3DBench (https://market.android.com/details?id=com.threed.jpct.bench):
Fillrate ST/MT: 6.21/6.22 MP/s
High object count: 27.03 Fps
Multiple Lights: 40.19 Fps
High polygon count: 19.97 Fps
Keyframe animation: 39.97 Fps
Game level: 30.04 Fps
Total score: 4278
3/16 Overclock Kernel
CPU @1000Mhz, Performance gov
Quadrant (First run only):
Total: 960
CPU: 2693
Mem: 1099
I/O: 522
2D: 202
3D: 286
Linpack:
12.983Mflops
NenaMark:
17.0 Fps
Benchmark PI:
Pi found in 1627ms
Antutu System benchmark :
Total Score: 1832
Memory: 445
CPU Integer: 631
CPU Float: 144
2D Graphics: 109
3D Graphics: 302
Database IO: 20
SD Card Write: 5.8 MB/s
SD Card Read: 12.3 MB/s
An3DBench:
Fillrate ST/MT: 6.23/6.19 MP/sec
High object count: 30.46 fps
Multiple Lights: 39.96 fps
High polygon count: 20.16 fps
Keyframe animation: 40.40 fps
Game level: 30.43 fps
Total score: 4397
CPU @1100Mhz, Performance gov
Quadrant (First run only):
Total: 1001
CPU: 2833
Mem: 1085
I/O: 566
2D: 213
3D: 306
Linpack:
MFlops: 13.917
NenaMark:
16.8 Fps
Benchmark PI:
Pi found in 1460
Antutu System benchmark:
**Would not run at 1100**
Total Score:
Memory:
CPU Integer:
CPU Float:
2D Graphics:
3D Graphics:
Database IO:
SD Card Write:
SD Card Read:
An3DBench :
Fillrate ST/MT: 5.89/6.01
High object count: 17.53 fps
Multiple Lights: 40.22 fps
High polygon count: 20.13 fps
Keyframe animation: 40.37 fps
Game level: 30.44
Total score: 4054
The results speak alot, i think, and yet they don't. The big difference, is that the IO score on Quadrant tanks on the OC kernel, but is fine/better on every other test. Specifically, i noticed that file system writes takes much longer on the OC kernel, than the stock. 3D performance makes obvious gains with increasing clock speed, and other CPU / IO benches show no problem either.
The antutu bench failing at 1.1 is very odd, since my system has never shown any instability at this speed. It crashes almost immediately , where are 1.0Ghz makes it through just fine. Could it be my system is instable? Possibly...
just for the heck of it, i set the gov to interactive, and here is what i got (1100Mhz, OC kernel, Interactive Gov):
Antutu System benchmark:
Total Score: 1089
Memory: 481
CPU Integer: 701
CPU Float: 154
2D Graphics: 101
3D Graphics: 209
Database IO: 10
SD Card Write: 4.9 MB/s
SD Card Read: 10.4 MB/s
who knows....
Thus, I am left with this question: Is the Quadrant bench testing an IO function that no other bench i tried is, or is it testing something in a way no other bench does, and just doesn't like this kernel? Obivously, SOMETHING is going on, becuase the problem is measurable and repeatable. The kernel change showing the problem alludes to a possible issue, but other benches say that the likelyhood of noticing it is minimal.
That said, our device isn't the only one that seems like it has a problem with IO scores: http://androidforums.com/samsung-captivate/136969-quadrant-scores.html
Hopefully, this is a starting point for people, and might even help a dev or two pinpoint what might be happening. I am no expert, but am willing to help where i can.
Data Formatting
Thanks for the bench scores. Hopefully its a starting point to understand the issue.
Here is a better looking version of your numbers :
{
"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"
}
Wow.. many thanks for the awesome graph; it really makes things so much neater!
Also the guesses that it may be a problem with quadrant may pan out. I always thought the OC kernel seemed snappier as far as user interaction (especially launching the applications list w/ animations.)
chisleu said:
Also the guesses that it may be a problem with quadrant may pan out. I always thought the OC kernel seemed snappier as far as user interaction (especially launching the applications list w/ animations.)
Click to expand...
Click to collapse
The user interaction improvement is due to increased CPU clock and 2D performance. IO matters when you install or load something.
amtrakcn said:
The user interaction improvement is due to increased CPU clock and 2D performance. IO matters when you install or load something.
Click to expand...
Click to collapse
Except those numbers are inaccurate.
chisleu said:
Except those numbers are inaccurate.
Click to expand...
Click to collapse
The performance increase I've experianced with the o/c kernal leads me to agree with your point about the quad benchmark numbers being off the mark. That said, I was wondering if your statement is based on a deeper understanding of what is causing the low io quadrant numbers, and if it is, that you would be willing to share your thoughts. Thanks.
I think the statement really is worth looking into - the performance variance should be explored; just because quadrant is the only bench that shows and issue, doesn't mean there isn't one in the system...
Divine_Madcat, just wanted to say I appreciated the way you analyzed the issue and presented your findings. I learned alot from your approach. Enjoying your post. I'll send a thanks your way next time I sign in from my web browser.
Sent from my SGH-I897 using XDA App
vizographic said:
The performance increase I've experianced with the o/c kernal leads me to agree with your point about the quad benchmark numbers being off the mark. That said, I was wondering if your statement is based on a deeper understanding of what is causing the low io quadrant numbers, and if it is, that you would be willing to share your thoughts. Thanks.
Click to expand...
Click to collapse
I am not making a statement based on personal knowledge, but simply parroting something the guy who manages the kernal builds said.
So which should we use?
evilmerlin said:
So which should we use?
Click to expand...
Click to collapse
The OC Kernel. The OP was documenting something in detail to try to help out. There is a weird issue causing the OC kernel to show up slower than the stock in one benchmark. It's faster in all other benchmarks. There is probably something wrong with the benchmark.
chisleu said:
The OC Kernel. The OP was documenting something in detail to try to help out. There is a weird issue causing the OC kernel to show up slower than the stock in one benchmark. It's faster in all other benchmarks. There is probably something wrong with the benchmark.
Click to expand...
Click to collapse
Thanks for all the feedback guys. Chisleu, i would say you are correct, that it probably is the bench. Yet, there is just this small nagging part of me that wonder if quadrant isn't using something nothing else is, and found a hidden problem. Needless to say, i am not done looking at all this yet.
Divine_Madcat said:
Thanks for all the feedback guys. Chisleu, i would say you are correct, that it probably is the bench. Yet, there is just this small nagging part of me that wonder if quadrant isn't using something nothing else is, and found a hidden problem. Needless to say, i am not done looking at all this yet.
Click to expand...
Click to collapse
It is worth investigating though I must say it is low on my priority list. I don't put much weight in Quadrant and especially their I/O tests. Their I/O tests are known to be especially flaky.
When I get a chance, I will go through and remove the tweaks that are not in common with the CM7 kernel to see what is causing it. Unless someone beats me to it. *hint hint*
Thank you, Mr. Divine_Madcat! Hopefully you will continue your highly valuable benchmarking work with every significant CM7 nightly and RC, and Froyo/HC, to show the progress and better appreciate the work of our devs.
Quadrant marks peculiarities are, yes, puzzling. And they are not just in their absolute values, but the scatter of these between consequent benchmarkings.
Also, I know it's not the opportune time, but just to get into an understanding of a baseline FPS for OpenGL ES HW acceleration (or lack thereof), it might be worth the effort to do Neocore, at least on CM7 builds.
Thank you.
dalingrin said:
It is worth investigating though I must say it is low on my priority list. I don't put much weight in Quadrant and especially their I/O tests. Their I/O tests are known to be especially flaky.
When I get a chance, I will go through and remove the tweaks that are not in common with the CM7 kernel to see what is causing it. Unless someone beats me to it. *hint hint*
Click to expand...
Click to collapse
I got confused going into the kernel code. It looked like you guys only changed 8-10 lines of code from the B&N release. The last CVSystem I've used was CVS. heh. This new fangled "git" thingie is blowing my mind.
EDIT: NM... I wasn't seeing all the commits. Now I get it. Do we have to make config/menuconfig/whatever to setup the kernel, or are all the flags ready to go?
EDIT: Man I have some catching up to do. I remember when menuconfig was hot ****. The last kernel I built was 2.2.something IIRC.
Can't find the .config. Surely it's not hidden?
i know that quadrant puts a big emphasis on i/o score. just going from ext3 to ext4 on a archos 101 gave ~800-1000 pts.
scores have been around 2900 on quadrant for a device that feels slower than a galaxy tab.
I seem to have more touchscreen lag/miscalibration when using the oc kernal. It's only really apparent when i'm typing on the keyboard. I was using the stock kernal for about a week with no real issues. Is this something anyone else is experiencing? I was going to flash back to stock, but if it seems isolated, and i'll just flash the new nightly and the OC kernal on top of it again.
xwint3rxmut3x said:
I seem to have more touchscreen lag/miscalibration when using the oc kernal. It's only really apparent when i'm typing on the keyboard. I was using the stock kernal for about a week with no real issues. Is this something anyone else is experiencing? I was going to flash back to stock, but if it seems isolated, and i'll just flash the new nightly and the OC kernal on top of it again.
Click to expand...
Click to collapse
search for the touchscreen calibration. it's like 1 su/adb command.
chisleu said:
I am not making a statement based on personal knowledge, but simply parroting something the guy who manages the kernal builds said.
Click to expand...
Click to collapse
Thanks for the clarification. I take it you are referring to dalingrin. I think I recall the issue being addressed in a thread but I can't remember exactly what was said or where it was brought up. Do you have the threads post number by chance, since any observations on his part are worthy of serious consideration. Just hoping to learn something new here. Thanks in advance.
Web page refresh showed post by chisleu which quoted dalingrin on the io issue. If this was the post You were referring to then please ignore the above request.
Based on the newest HTC source code.
Overclocked CPU, added optimized CPU frequency tables with CPU frequencies up to 1836 MHz and L2 cache frequencies up to 1566 MHz.
Increased CPU voltage limits (700 mV - 1400 mV).
Added CPU Voltage Table interface that allows voltage adjustment.
Fixed CPUFreq.
Overclocked GPU, increased maximum GPU frequency in 3D mode from 267 MHz to 320 MHz (300 MHz by default), increased bus bandwidth.
Added USB OTG.
Enabled USB Host.
Added support for different types of USB peripherals: USB Hub, USB mass storage devices (e. g. USB HDD, USB Stick, MP3 player), USB HID devices (e. g. USB mouse, USB keyboard, Wireless mouse or keyboard with USB receiver).
v1.4.0
First release built from kernel source code vigor-ics-crc-3.0.16-d0049f1. Thanks to HTC!
Optimized.
Added higher values to L2 cache frequency tables.
Updated CPU frequency tables.
Fixed ACPU and perflock to allow setting different maximum CPU frequency than highest available.
Fixed issue with changing minimum and maximum CPU frequencies by the system daemons. Replaced thermald.
Extended CPU voltage limits.
Added 300 MHz GPU clock settings.
Increased GPU bus bandwidth in 3D mode.
Modified Adreno220 drivers.
Overclocked GPU in 3D mode to 300 MHz by default, maximum 320 MHz.
Enabled USB OTG.
Added NTFS support.
Added SCSI.
Added USB Host.
Added USB storage and USB storage drivers.
Added USB HID.
Added drivers for USB HID devices.
Added support for zRam swap.
CIFS, SquashFS.
Enabled CPUFreq stat.
Added CPU Voltage Table - interface that allows adjustment of the CPU voltage (thanks to snq-, faux123 and show-p1984).
v1.3.0
Based on new kernel 3.0.16-g480e1b0 (August 3).
v1.20
Based on new kernel 3.0.16-g4a9c8a3 (March 10).
Fixed CPUFreq, mfreq related bug (which caused performance issues).
v1.10
Three kernel variants with different maximum CPU frequency.
First release based on kernel 3.0.16-g837f300.
Modified CPU frequency tables, CPU speed limits and voltage limits.
Modified information about CPU frequency displayed in Hardware information.
CPU Temperature daemon:
thermald v1.0.0 (SebastianFM)
The thermald daemon is a system service which monitors CPU temperature. It turns on the thermal sensor and sets thresholds to the thermal driver. Threshold are defined in file /system/etc/thermald.conf. If temperature reaches threshold, kernel sends notification to userspace. When thermald receives notification, it decreases CPU frequency to avoid CPU overheat.
The stock thermald doesn't work properly because when the CPU temperature drops below threshold, or when mpdecision turns on the second core, it always sets maximum CPU frequency to the highest available frequency.
I wrote my own thermald daemon which works very similiar, but when the CPU temperature is too high, it saves the current maximum CPU frequency and restores it later.
Currently my thermald doesn't parse external config file, it uses predefined thresholds.
Code:
[tsens_tz_sensor0]
sampling 3000
thresholds 75 78 81 84 87
thresholds_clr 72 75 78 81 84
actions cpu cpu cpu cpu cpu
action_info 1296000 1188000 918000 756000 384000
If you include my thermald in your ROM or kernel package, please don't forget give credit to me.
Current downloads:
v1.4.0, link, md5: 6ea612dd76b816e1ef10b5bf637b0d16
Older downloads:
v1.3.0 1728 MHz, link, md5: 3f6ab21ade2972f466baa8bbb80f7ab3
v1.3.0 1782 MHz, link, md5: f40b4578fb3c97f1556c53e926adfeb1
v1.3.0 1836 MHz, link, md5: 982e3fad23402556c48442f218d080b4
v1.20 1728 MHz, link 1, link 2, md5: d451991973bf26db28b6de1dcd1c6250
v1.20 1782 MHz, link 1, link 2, md5: 8051e4a094245ad0bad60b502ea264c9
v1.20 1836 MHz, link 1, link 2, md5: 42ae1d7416d46d68b59000f7c8d2995b
Installation:
This is flashable zip intended for install from recovery.
If your device is S-ON, installation will fail but PH98IMG.zip will be created on SD card. Reboot into bootloader, kernel will be flashed from this file.
OC:
The CPU frequency 1782 MHz should be stable but every device is different.
To increase maximum GPU frequency in 3D mode to 320 MHz:
echo 320000000 > /sys/devices/platform/kgsl-3d0.0/kgsl/kgsl-3d0/max_gpuclk
{
"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"
}
Source code:
GitHub
Thanks:
zone23, for testing and for AnTuTu scores, thank you.
con247, my installation scripts are based on con247's work, thanks.
I love you!! i went on your thread on the sensation a couple of weeks ago begging for this kernel and asking how you did this without source and everyone told me how amazing you were, im soo glad to see you on this thread for the rezound. Thank you!
Oh baby this is hot!
zetsumeikuro said:
Oh baby this is hot!
Click to expand...
Click to collapse
Nice choice of words...
Yum
Sent from my ADR6425LVW using XDA App
so im guesing that this will only work on a sense based ics rom correct?
JohnShaft69 said:
so im guesing that this will only work on a sense based ics rom correct?
Click to expand...
Click to collapse
Yup. HTC bases only for this kernel.
this kernel doesnt work. gets stuck at white screen on Joelz Rom, im sure its a easy fix. still hyped over this. especially antutu scores
Easton999GS said:
this kernel doesnt work. gets stuck at white screen on Joelz Rom, im sure its a easy fix. still hyped over this. especially antutu scores
Click to expand...
Click to collapse
I'm on Joelz Rom, not having that issue. Running great for me.
Sent from my ADR6425LVW using xda premium
Works for me, on 4.0.1 with Sense, very smooooooth. Using CPU Master though, and the frequencies I set do not always stick... any suggestions?
TheRedmonian said:
I'm on Joelz Rom, not having that issue. Running great for me.
Sent from my ADR6425LVW using xda premium
Click to expand...
Click to collapse
Are you running the latest version of Joel's ROM that he posted last night?
If so, is this running better than the kernel from his ROM?
WizeGuyDezignz said:
Are you running the latest version of Joel's ROM that he posted last night?
If so, is this running better than the kernel from his ROM?
Click to expand...
Click to collapse
Yes and Yes. Much smoother.
Sent from my ADR6425LVW using xda premium
SebastianFM said:
This is hex edited by me, overclocked, stock HTC kernel.
Thanks:
con247 for script and tests.
Click to expand...
Click to collapse
Thanks again for doing this! I tested this on an older version of Tachi91's rom Here (2.x maybe?) for the past few days and it has ran fine and been stable. It should work on any sense ics rom seeing that we dont have kernel source yet and the current ics kernels floating around are either the same are almost the same.
SebastianFM said:
This is hex edited by me, overclocked, stock HTC kernel.
Features:
v 1.00
Unlocked and increased CPU and L2 cache maximum frequency and voltage limit.
Added values to frequency tables for CPU up to 1.728 GHz and for L2 cache up to 1.566 GHz.
Installation:
This is flashable zip intended for install from recovery.
I used con247 Automatic Kernel Installation for S-ON Unlocked Devices, so you can flash this kernel on any ROM.
Download:
1.728 GHz OC kernel 3.0.13-gaf15497-dirty v1.00 md5sum:
Thanks:
con247 for script and tests.
Click to expand...
Click to collapse
Sebastian do you recommend a specific app to manage the OC, governor, I/O scheduler with this Kernel or is it purely self contained?
TheRedmonian said:
Yes and Yes. Much smoother.
Sent from my ADR6425LVW using xda premium
Click to expand...
Click to collapse
Awesome, thanks for the reply!
Are you using SetCPU or anything similar, or just the kernel as is? If you are using an app, what do you have your settings at?
I only ask because I'm running the same ROM as you and would like to duplicate your results!
Thanks!
I can confirm that this works extremely well on newts sense rom. No problems and very smooth
I'm living on a yellow submarine
WizeGuyDezignz said:
Awesome, thanks for the reply!
Are you using SetCPU or anything similar, or just the kernel as is? If you are using an app, what do you have your settings at?
I only ask because I'm running the same ROM as you and would like to duplicate your results!
Thanks!
Click to expand...
Click to collapse
I've been running as is for now.
Sent from my ADR6425LVW using xda premium
Working good for me on Newts senseless. Now all we need is done governors to go with and it will be perfect. Great job!
Sent from my ADR6425LVW
Njenson said:
Working good for me on Newts senseless. Now all we need is done governors to go with and it will be perfect. Great job!
Sent from my ADR6425LVW
Click to expand...
Click to collapse
I believe the governors and I/O scheduler stuff might have to wait until the ICS kernel source is released (at least to make them as effective as possible and backport the latest kernel changes from Linux).
This is orgasmic.
Sent from my ADR6425LVW
So I followed Droidstyles "how to" guide on how to put ics on my phone.( http://forum.xda-developers.com/showthread.php?t=1238070 )
I love it so far but now it leaves me wanting more from my phone. Im trying to learn how to overclock my cpu.
I currently have Teamhacksung 6.1 on my phone. And in my "about phone" section my kernel version reads
3.0.8-g0d5605e-dirty
[email protected] #1
Not too sure if those are the same thing. Can i overclock my CPU with the current kernel i have or do i have to put another one on my phone?
Thanks alot for any replies!
Djp2012 said:
So I followed Droidstyles "how to" guide on how to put ics on my phone.( http://forum.xda-developers.com/showthread.php?t=1238070 )
I love it so far but now it leaves me wanting more from my phone. Im trying to learn how to overclock my cpu.
I currently have Teamhacksung 6.1 on my phone. And in my "about phone" section my kernel version reads
3.0.8-g0d5605e-dirty
[email protected] #1
Not too sure if those are the same thing. Can i overclock my CPU with the current kernel i have or do i have to put another one on my phone?
Thanks alot for any replies!
Click to expand...
Click to collapse
Flash Glitch v14 located in the Development forum.
Please Remember to use nstools for overclocking.
Sent from my SCH-I500 using XDA App
Wow thanks for the fast reply.
Do i have to uninstall any of the other kernels I have or go back to any versions?
Or can I download glitch v14 and use odin to flash it from the version im on?
Djp2012 said:
Wow thanks for the fast reply.
Do i have to uninstall any of the other kernels I have or go back to any versions?
Or can I download glitch v14 and use odin to flash it from the version im on?
Click to expand...
Click to collapse
Flash via CWM.
Hold power button
Select 'Reboot'
then select 'Reboot Recovery'
Then flash.
No Odin needed.
That's it.
You cant uninstall a kernel, it boots the phone. You can flash different kernels though. (e.g Glitch Kernel)
Be careful when overclocking. Especially with LiveOC.
If you do not know how liveOC works, please, do not use it.
Have fun
Sent from my SCH-I500 using XDA App
Wow so i got it to work just by doing what you said. I know there is benefits for overclocking as well as some consequences if i dont do it right.
Is there anywhere i could go to read up more on how liveOC works on the fascinate? Like i said, i really want that extra edge that I can get from doing so
Also I downloaded NSTOOLS to get me started
Djp2012 said:
Wow so i got it to work just by doing what you said. I know there is benefits for overclocking as well as some consequences if i dont do it right.
Is there anywhere i could go to read up more on how liveOC works on the fascinate? Like i said, i really want that extra edge that I can get from doing so
Also I downloaded NSTOOLS to get me started
Click to expand...
Click to collapse
Here's the thread (quoted it to save you time)
Tk-Glitch said:
LiveOC and Custom Voltage guide by TkGlitch
for Glitch kernel V14
{
"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"
}
Warning!
Overclocking is dangerous and is meant only for experienced users!
1- Introduction :
The "normal" overclocking system on SGS til now was the addition of some frequency steps past the stock 1GHz step. V13 kernel was using 7 overclocked steps
to push the maximum selectable speed to 1.7GHz.
In V14, less overclocked steps are present, but you can still overclock to 1.7GHz if you want (and if your phone is able to do it), and even up to 2.25GHz as a maximum.
You will need NSTools to use LiveOC and custom Voltage features in Glitch kernel V14.
To begin with, I'll explain you some basic things you have to know.
2- Clocks :
The CPU speed is the result of a bus speed and a multiplier.
Bus speed is linked to and equal to GPU and RAM speed.
The multiplier is per step and hardcoded by the kernel developer.
It does look like that : CPU speed = bus speed x multiplier.
Here are my values in V14 :
1500 MHz = 200 x 7.5
1400 MHz = 200 x 7
1300 MHz = 200 x 6.5
1200 MHz = 200 x 6
1000 MHz = 200 x 5
800 MHz = 200 x 4
400 MHz = 200 x 2
200 MHz = 200 x 1
100 MHz = 100 x 1
LiveOC gives you the access to direct and on-the-fly bus overclocking by 1% steps (150% being the maximum available). I'll say it again : BUS overclocking !
Though, it'll overclock the bus on all the steps at the same time, for the same percentage.
We'll talk about that later.
So if I want to overclock my 1GHz step to 1.1GHz, I'll have to select 1GHz as max frequency, and push LiveOC to 110%.
My bus speed beeing overclocked by 10% will give the following :
220 x 5 (1GHz multiplier) = 1100 MHz.
If you want to go higher than 1.5GHz, it's the same :
Set 1500 MHz as maximum frequency (for example), and push LiveOC. Let's say to 110%. You will get the following :
220 x 7.5 (1.5GHz multiplier) = 1650 MHz.
Pushing it to 114% will give 1710 MHz (228MHz bus) and so on, up to 150% giving 2250 MHz running an inachievable 300MHz bus.
3- The limits :
THE MAIN LIMIT AND PHONE KILLER IS HIGH TEMPERATURE. WARM IS OK, HOT IS TOO HOT. DON'T PLAY STUPID.
Obviously, so much control over the bus speed, frozen til now to what the kernel developer set, will also give you the ability to find the limits of your chip.
The main clocking limit is generally the RAM, corrupting itself when the bus speed is too high. And since the GPU uses the RAM as well, it'll become crashy too. That's why I have decided to add some steps with a bigger multiplier, to lower the bus for a higher CPU frequency.
The bus speed limits for you will be anywhere between 240 and 270 Mhz, depending on your device potential (higher and lower exists but rare).
Average is 240 MHz.
The CPU speed limits will be anywhere between 1300 and 1800 MHz (higher and lower exists but rare as well).
Average is 1400 MHz.
With that in mind, I wouldn't go too far past 130% (giving 260MHz bus speed).
4- The sweet spot :
What you want when overclocking is to get the best balance for each part. Since the bus is linked to RAM and GPU, you obviously want it as high as possible for gaming, video playing, web browsing etc. (even more now with GPU acceleration in Android 4.0+). Though, as you know already if you've read this guide til now, all steps in V14 are using the stock 200MHz frequency.
So what to do if I want a lower CPU speed with a higher bus/GPU speed ? Simple ! Just select a lower frequency step as starting point.
Let's say we want 250 MHz bus speed, so we'll use 125% LiveOC :
Using 800MHz step, you'll get 1GHz.
Using 1GHz step, you'll get 1.250GHz.
Using 1.2GHz step, you'll get 1.500GHz.
Using 1.3GHz step, you'll get 1.625GHz.
Using 1.4GHz step, you'll get 1.750GHz.
Using 1.5GHz step, you'll get 1.875GHz.
5- The issues :
With a new overclocking system obviously comes some new problems related to it.
With the ability to fine tune the frequencies, you'll find that some frequencies are buggy somewhat, giving low performances. For example, using 115% Live OC with the 1.3GHz step will give some poor performances, when 114 and 116% won't. It could be a NSTools issue, but I think it has more to do with the hardware. It's well known that on CPUs some frequencies or even frequency ranges can be buggy, unstable, or slow. If you encounter that, try to add or remove a percent to LiveOC.
As said earlier, LiveOC will overclock the bus for all steps at the same time by the same amount of %.
Knowing that, you'll have to adapt your voltages for all the frequencies to stay stable, and this for any sensible change on LiveOC percentage.
6- Custom Voltage :
What would be LiveOC without Custom Voltages ?!
I did add leakage values to Glitch kernel features when I saw that some phones were overclocking much better with the right balance between ARM and Int voltages, depending on the phone, with very different results. The leakage value was basically that : balance between the two.
Well, as you probably know if you did read the changelogs, you have now the capacity to overvolt/undervolt both the ARM voltage (the CPU voltage you know well already), and the Int (internal) voltage. The last one is the voltage going to the GPU/memory controller, and will need to be tweaked accordingly to your phone.
As a starting point, here are the Int voltage values I was using for each leakage, adapted for V14 new frequency table :
HIGH LEAKAGE :
1500 : 1.225
1400 : 1.200
1300 : 1.175
1200 : 1.150
1000 : 1.125
800 : 1.100
400 : 1.100
200 : 1.100
100 : 1.000
MEDIUM LEAKAGE :
1500 : 1.200
1400 : 1.175
1300 : 1.150
1200 : 1.125
1000 : 1.100
800 : 1.100
400 : 1.100
200 : 1.100
100 : 1.000
LOW LEAKAGE :
1500 : 1.175
1400 : 1.150
1300 : 1.125
1200 : 1.100
1000 : 1.100
800 : 1.100
400 : 1.100
200 : 1.100
100 : 1.000
Of course, using LiveOC will force you to change these voltages accordingly.
Here are some advices about this :
- Try to stay around 1.225 - 1.250V for your highest frequencies;
- Try not to ever go past 1.300V if you don't want to kill your phone quickly;
- Be VERY gentle when tweaking it as it is VERY sensitive;
- Try to follow a more or less linear curve for Int voltage on OC frequencies;
- Going below 1.000V on 100MHz step will generally kill stability with no battery gain.
This guide may change depending on my decisions related to the Glitch kernel development, or to polish / add things to it.
Thanks to Ezekeel from Nexus S section for these awesome tools.
LiveOC : http://forum.xda-developers.com/showthread.php?t=1288015
Custom Voltages : http://forum.xda-developers.com/showthread.php?t=1331610
23/01/2012 - UPDATED TO REFLECT V14-B1 CHANGES.
09/02/2012 - UPDATED TO REFLECT V14-B3 CHANGES.
Click to expand...
Click to collapse
Sent from my SCH-I500 using XDA App
Yeah the guide is highly confusing but ill attempt to decipher it lol. As of now though ill just run the liveoc at %110
And once again thanks for the help, trying to figure it out on my own was driving me nuts
Djp2012 said:
Yeah the guide is highly confusing but ill attempt to decipher it lol. As of now though ill just run the liveoc at %110
And once again thanks for the help, trying to figure it out on my own was driving me nuts
Click to expand...
Click to collapse
I use 110%, stock voltages, and the 1200 max step
Sent from my SCH-I500 using xda premium
whats the downside to just using voltage control and keeping it simple?
droidstyle said:
whats the downside to just using voltage control and keeping it simple?
Click to expand...
Click to collapse
No downside that I can tell
Terminators run on Android
The downside is that it's just utilizing extra frequency steps for CPU overclocking as opposed to being able to fine-tune BUS (CPU+GPU+RAM) speed.
droidstyle said:
whats the downside to just using voltage control and keeping it simple?
Click to expand...
Click to collapse
A bottleneck in the buss.. The old glitch v13 overclocked the buss for you. Check the op in the v13 thread. In this kernel by just overclocking cpu I'm sure your bound to not have an efficient setup as the gpu and buss and ram will be stock
Sent from my SCH-I500 using xda premium
Think of a Manure spreader flinging crap against a brick wall, you're manure is your data, the brick wall is your bottle neck.. Well your bottle neck had a 1 foot hole in it. That's your throughput. You speeding up your spreader without making that hole bigger gives you a wall o' ****.
Just because your overclocking to 1.5ghz dont Mean you'll process any more any quicker.. I can use a performance governer and oc to 1.8 GHz then lock my screen.. What does that give me? A battery sucker that is not throughputing the amount of info the step I'm on suggests i could be
Sent from my SCH-I500 using xda premium
currently 14hrs run time @ 42% battery, 2hrs screen on time. seems fairly efficient and fast idk. I was running nstools and using live oc with no issues previously, but i noticed no improvement over using voltage control. i guess ill switch back to nstools and give live oc another go.
droidstyle said:
currently 14hrs run time @ 42% battery, 2hrs screen on time. seems fairly efficient and fast idk. I was running nstools and using live oc with no issues previously, but i noticed no improvement over using voltage control. i guess ill switch back to nstools and give live oc another go.
Click to expand...
Click to collapse
To tell you the truth, i don't think any overclock will make a noticeable difference. These ics roms with the glitch kernel are so fast to begin with. But when it comes to heavy apps i know you won't see the performance of v13 just using vc. Because v13 overclocked the buss/gpu.
And i had 84% battery after 10 hours today. With at least an hour of screen on. But I'll keep track tomorrow with some screenies if you want to compare
Sent from my SCH-I500 using xda premium
MOD NOTE: IT APPEARS THIS KERNEL IS FOR 4.1.x ONLY. Flashing on 4.2 will result in bootloop. also, this kernel is unsupported by the OP, so thread is currently CLOSED
First and foremost, I would like to thank _motley for his kernel since this is based on his kernel. I chose his kernel because I have worked with him and IMO is the best kernel out there at the moment . Second, I would like to thank pinoyto and secret for testing the kernels. Also thanks to Koush, Blades, faux123, pershoot, chatch15117, all the Gtab, Asus Transformer and Motorola Atrix users, and other devs that I may have missed. BIG THANKS to my beloved wife for watching the kids while I do this.
I call this kernel elite since the timings are pretty aggressive and voltage are decreased on the low side and increased on the high side. This kernel might not work on your device because of these so be sure that you have a backup and and that you are familiar on restoring your device.
The following are the difference with motley's kernel
1. JRCU is implemented
2. Lowest backlight setting set to 5 (save battery and better reading at night, if you have screen flicker issue it will be more noticable because of this so I suggest covering the ground pin of wifi)
3. Core voltage increased from 1200 to 1250mv on the high side to hit 1.7 frequency and 600 GPU but decreased from 950 to 900mv on the low side.
4. Increased CPU voltage to 1240mv for 1.7 frequency but allows decreased 750mv in low side
5. Increased GPU clock to 600 and pixclock increased (please let me know if you have problems on screen due to pixclock increase but so far no issues on testers)
6. Built using gcc 4.5.2 ( I know, I'm an oldie)
7. DVFS core table completely changed to allow max clock of host1x and pll_c and hit most max frequencies.
8. Enable Thermal_Sys to throttle at 68 (BTW, if you are using system tuner, the reading is +10 as per secret)
Added 484 GPU and 520 GPU. LMK how it goes.
Link is below
Source in compliance with GPL
https://github.com/clemsyn/Grouper
IF YOU WANT THE UNDERVOLTED VERSION PLEASE SEE SECOND POST
------------------------------------------------------------------------------
------------------------------------------------------------------------------
UPDATED 09/23/2012
Releasing another 1.8ghzCPU and 650mhz GPU
Here are the differences with the last 650gpu
1. Used Linaro compiler
2. Increased 3d/2d bus, pll_c, and host1x for higher scores
3. Removed the pixclock overclock, This is running on default pixclock by Asus. This will limit the fps to 60 fps max, so old benchmarks will not score over 100 fps but will only max at 60. I suggest newer benchmarks like GL2.5 or Benchmark 2.0 ES Taiji...
4. EMC voltage decreased to 1.100 mv (Not sure if your device can handle this but pinoyto's device was fine with it)
Here is the link
https://rapidshare.com/files/2462982943/1.8ghz650GPUNopix.zip
If you like my work, please click on Donate button on my Sig and add on to my Nexus 7 fund Thanks
--------------------------------------------------------------------------------------
-------------------------------------------------------------------------------------
UPDATED 9/20/2012
*** SPECIAL RECOGNITION goes to PINOYTO for the first donation of this project. THANKS for rewarding my hard work!! ***
Thanks to masterg0g0 for 2nd donation
Also thanks to all the testers of the 700mhz GPU.
This latest kernel comes with the 1.8ghz CPU and 700 GPU with 3 types of pixclocks.
First off is the max pixclock. This has the highest pixclock of all the kernels and will limit your fps to over 100 fps. The downside is the pink screen issue.
https://rapidshare.com/files/901768617/1.8ghz700GPUMAXPIXoc.zip
Second is the mid pixclock overclock. If you have a pink issue on the first one, try this. This will limit your fps to about 90 fps. The downside is you might still have a pink screen
https://rapidshare.com/files/4017246162/1.8ghz700GPUMEDPIXoc.zip
Third is the NO pixclock overclock. This for sure will have no pink issue but will limit your fps to about 65 fps.
https://rapidshare.com/files/258377771/1.8ghz700gpuNOPIXOC.zip
Here are the changes made from this latest kernels
1. GPU increased to 700 gpu, vcore and vrail voltages increased
2. pll_c, host1x increased to accomodate the increase in GPU speed
3. Compiled using Linaro toolchain.
WARNING:
The timings in this kernel are very aggressive, voltages although within Nvidia limits are high. Please make sure you backup and be very familiar in recovering your device.
IF YOU LIKE MY WORK, PLEASE CLICK on the "DONATE TO ME" BUTTON UNDER MY SIG TO SHOW YOUR APPRECIATION and ADD on to my "NEXUS 7 FUND". Your donation will be GREATLY APPRECIATED. THANK YOU.
---------------------------------------------------------------
---------------------------------------------------------------
UPDATED 8/17/2012
Overclocked to 1.8ghz with GPU at 650..WARNING THIS IS GOING TO GET HOT!!!
https://rapidshare.com/files/1034477848/Clemsyn1.8GPU650.zip
Pink fix
https://rapidshare.com/files/223841402/Clemsyn1.8GPU650Pinkfix.zip
Changes:
1. Temp limit increased to 70
2. Voltages increased to accomodate 1.8ghz and 650 gpu
--------------------------------------------------------------------
--------------------------------------------------------------------
BTW, if you like my work, please dont hesitate to click on the Donate button under my username. Thanks.
Updated 8/23/2012
This new kernel is based upon what I believe is the best overclocking speed (1.5 ghz) and a cpu nominal voltage of 1.150mv and a core of 1.175 mv (core default is 1.2) while lowering the lowest voltage of 750mv and 900mv respectively. This kernel hits the max speeds of the GPU at 600 while utilizing the lower voltages to insure better battery life and less heat. Also pixclock has been decreased to minimize pink issues on the screen Again, this might not run on all Nexus 7 due to aggressive lowering of voltages. HAVE FUN!!
Also make sure you have a backup and familiar with restoring your device.
BTW, if you like my work. Don't hesitate to DONATE and help me buy some diapers Thanks
Finally got the issue why most devices where not working right. Also was able to undervolt MORE because of this finding. Here are the changes
1. Vcore undervolted to 1.15 mv (default at 1.2) cpu mv at 1.15 mv running 1.5ghz
2. pll_c decrease from maximum (this was what was causing all the issue)
3. This kernel is set to 1.5ghz automatically. However if your ramdisk is programed to 1.3, then it boots to 1.3 intially. After pressing the power button once (or letting it sleep), it automatically resumes to 1.5 ghz without any CPU program.
I highly recommend that these settings be used for better battery life, LESS HEAT and power usage... Good for daily use
Here is the link
https://rapidshare.com/files/1026092132/Clemsyn1.5extremeUndervoltedFINAL.zip
BTW, if you like my work please show your appreciation and click on the Donations link under my signature. Thanks.
------------------------------------------------------------------------------------------------
-------------------------------------------------------------------------------------------------
Update: 8/17/2012
OK, updated this version of the kernel to increase CPU Core to 1.2mv for some stability for some users...Here is the link
link deleted for latest version above
----------------------------------------------------------
----------------------------------------------------------
This new kernel is based upon what I believe is the best overclocking speed (1.5 ghz) and a cpu nominal voltage of 1.150mv and a core of 1.175 mv (core default is 1.2) while lowering the lowest voltage of 750mv and 900mv respectively. This kernel hits the max speeds of the GPU at 600 while utilizing the lower voltages to insure better battery life and less heat. Also pixclock has been decreased to minimize pink issues on the screen Again, this might not run on all Nexus 7 due to aggressive lowering of voltages. HAVE FUN!!
Also make sure you have a backup and familiar with restoring your device.
BTW, if you like my work. Don't hesitate to DONATE and help me buy some diapers Thanks
Downloading now. Will reply with results asap
Edit*
Booted up fine but didn't last too long, saw temps hit 72C and then it rebooted.
Now I guess I could give this a try and report on smoke or injuries if anything.
Rafase282 said:
Now I guess I could give this a try and report on smoke or injuries if anything.
Click to expand...
Click to collapse
LOL, doubt about the smoke because of the Thermal control at 68 but if you would be willing to test my 1.8ghz kernel with 700 GPU LMK (kidding).
clemsyn said:
LOL, doubt about the smoke because of the Thermal control at 68 but if you would be willing to test my 1.8ghz kernel with 700 GPU LMK (kidding).
Click to expand...
Click to collapse
I had to clearn and uninstall system tuner and reinstall to be able to set thing right.
1. I noticed it goes from 1.5 to 1.5, then 1.54 then 1.54 then 1.7
Is it supposed to be like that?
2. What tools do you want me to use for testing? Any recommended way for testing like turn off wifi or something?
You can have my first born. This thing flies!
Holy smokes! This sh!t sounds dangerous! I am all over it
Sent from my Glazed-over Nexus 7
Very interesting. Thanks for making this. I already downloaded. Ill give this a go shortly. Ill make sure to delete data from system tuner to make sure no default voltages are saved from motleykernel.
I hope my device can handle the 1.7ghz, since you increased the top end voltages. With 1.7ghz and 600mhz gpu oc, I'm not expecting this to e old on battery. It's more like you said, pushing the limits of what we capable of. Wish me luck! Lol. Anxious to see how this benches. Did you add the I/o tweak and disable fysnc in this build? Or will running commands from motley thread do the trick? I'm notbsure if tkt app will allow fsync on faster if the file path tnot the same on this kernel.
Ill report back letting you know how it went
evonc said:
Downloading now. Will reply with results asap
Edit*
Booted up fine but didn't last too long, saw temps hit 72C and then it rebooted.
Click to expand...
Click to collapse
Temp is actually 62, secret says that System Tuner reading is +10.
demandarin said:
Very interesting. Thanks for making this. I already downloaded. Ill give this a go shortly. Ill make sure to delete data from system tuner to make sure no default voltages are saved from motleykernel.
I hope my device can handle the 1.7ghz, since you increased the top end voltages. With 1.7ghz and 600mhz gpu oc, I'm not expecting this to e old on battery. It's more like you said, pushing the limits of what we capable of. Wish me luck! Lol. Anxious to see how this benches. Did you add the I/o tweak and disable fysnc in this build? Or will running commands from motley thread do the trick? I'm notbsure if tkt app will allow fsync on faster if the file path tnot the same on this kernel.
Ill report back letting you know how it went
Click to expand...
Click to collapse
It's based from _motley, using his defconfig to build it (aside from the GPU overclock and JRCU) so his commands should work.
scarygood536 said:
You can have my first born. This thing flies!
Click to expand...
Click to collapse
Thanks for trying it I already have four kids and they take a lot of my time
I get reboots when running CF-Bench with interactive and sio at 1.7 stock voltages.
---------- Post added at 01:17 AM ---------- Previous post was at 01:16 AM ----------
clemsyn said:
Thanks for trying it I already have four kids and they take a lot of my time
Click to expand...
Click to collapse
Sell the 5th for body parts. Organs are not easy to find.
Dude.... WTF!? 106 FPS!!?! That can't be right, can it?
{
"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"
}
Sent from my Glazed-over Nexus 7
Rafase282 said:
I had to clearn and uninstall system tuner and reinstall to be able to set thing right.
1. I noticed it goes from 1.5 to 1.5, then 1.54 then 1.54 then 1.7
Is it supposed to be like that?
2. What tools do you want me to use for testing? Any recommended way for testing like turn off wifi or something?
Click to expand...
Click to collapse
Skipped 1.6 since _motley kernel has that so next stepping is 1.54
Try benchmarking it or undervolting it using system tuner but I suggest keeping 1.7 at 1240 mv.
boynamedstacy said:
Dude.... WTF!? 106 FPS!!?! That can't be right, can it?
Sent from my Glazed-over Nexus 7
Click to expand...
Click to collapse
Yup its right, GPU at 600 with max timings in the table
Rafase282 said:
I get reboots when running CF-Bench with interactive and sio at 1.7 stock voltages.
---------- Post added at 01:17 AM ---------- Previous post was at 01:16 AM ----------
Sell the 5th for body parts. Organs are not easy to find.
Click to expand...
Click to collapse
LOL, sorry didn't work for you, Timings on this kernel is pretty aggressive. If it works, you are lucky to have an elite device. Try 1.54 with GPU at 600 and see how it goes.
clemsyn said:
LOL, sorry didn't work for you, Timings on this kernel is pretty aggressive. If it works, you are lucky to have an elite device. Try 1.54 with GPU at 600 and see how it goes.
Click to expand...
Click to collapse
I wont give up
boynamedstacy said:
Dude.... WTF!? 106 FPS!!?! That can't be right, can it?
Sent from my Glazed-over Nexus 7
Click to expand...
Click to collapse
Mines booted up. Got scared for a moment..lol. seemed stuck on Google screen. Bit it eventually booted up. Running default speed. I haven't cranked it up yet to test top speeds.
As for your fps scores, I'm not surprised with this being 600mhz gpu. Bit the crazy thing is our displays can't handle or really display more than 60fps.
Please report CPU temps running at 1.7ghz. Especially while benchmarking, gaming, and normal use.
Battery life would be interesting also.
106 fps?! what trickery is this?!
DRAGON KERNEL SOURCE PROJECT FOR
J51x AND J5x devices
{
"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"
}
Supported devices:
SM-J510FN (High binned)
SM-J500FN (High binned)
SM-J500G (Low binned
SM-J500H (Low binned)
SM-J500M (Low binned)
Features:
CPU governors: blu_active, cultivation, chill, interactive (default), ondemandplus, performance and relaxed
I/O schedulers: bfq, cfq, deadline, fiops, maple (default), noop, sioplus, and zen
CPU hotplugs: AutoSMP
Custom voltage control
Power Efficient workqueues
Backported Zen Interactive tunings from Zen 4.10
WireGuard support
KCAL advanced color control (http://forum.xda-developers.com/andr...ntrol-t3032080)
Fsync on/off support
USB fast charge
State notifier
Compiled with Linaro GCC 4.9.4 toolchain
Features for hight binned produtcs:
CPU frequency up to 1.36 GHz
GPU frequency up to 620 MHz
Various efuse registers
Downloads:
DRAGON-V2
XDA:DevDB Information
DRAGON, Kernel for the Samsung Galaxy J5
Contributors
BulgarianJesus
Source Code: https://github.com/DragO0nFly/android_kernel_samsung_msm8916_j5x-DRAGON
Kernel Special Features:
Version Information
Status: Stable
Created 2018-10-03
Last Updated 2018-10-05
<Mod Edit>
Thread closed
Changelog
V2.1
Toolchain: Switched to Linaro GCC 7.1.3
CPU: unlocked low binned devices and their registers
CPU: overclocked low binned devices up to 1.36 GHz
GPU: unlocked low binned devices and their registers
GPU: unlocked 465 MHz for low binned devices
GPU: Overclocked both low and high binned devices up to 620 MHz
GPU: initial power-up level set at 200 MHz for better battery life
Information
CPU: Binning
Some devices are high binned, meanwhile others are low binned. If your device is high binned, it will boot at 1.36 GHz CPU and 465 MHz GPU default speeds, if this process fails it means your device is low binned and it's not really designed for being overclocked. Even if I stated that FN models are high binned, I found out that some J5F models are also high binned. All this depends on luck actually, my OC is different compared to others! Due to the fact I use the stock Qualcomm values, speed bins and register in order to obtain such type of overclock.
CPU: Overclocking
Overclocking is the increase of clock speed beyond the manufacturer's maximum rated clocks. Since manufacturers are only required to meet the minimum advertised specifications, the potential for overclocking of a product is not typically tested during the binning process. Therefore, it should not be assumed that higher-rated products will overclock better than lower-rated ones. Applying to this, our source code is limited in a really stupid way. The SoC can't switch between speed-bins which allow it to change efuse as well. Having the right efuse and speed-bin, unlock the "default" state of MSM8916 which is 1.36 GHz on CPU and 465 MHz on GPU. Previous methods of OC, just re-write manually the speed-bin to workload as 1.36 GHz without using an efuse or the correct speed-bin.
GPU: Overclocking
Both high binned and low binned devices support maximum frequency up to 620 MHz, with or without an efuse.
BUS: Overclocking
Current bus clock is 595.2 MHz, but it does support a frequency up to 740 MHz
Is it a touchwiz or aosp kernel?
Flegmon said:
Is it a touchwiz or aosp kernel?
Click to expand...
Click to collapse
touchwiz but soon it will be also AOSP I hope
Where is J510F??
Great
Working fine on J510GN :good:
Congratulations for the amazing kernel, my j500F even though low binned seems ultra fast.
Battery usage is also balanced..
Great work dude and Welcome! ??
Best kernel runa greda on j510FN lighting nastane ice cool but how to overxloxk bus oni se kernel auditorium?
works great on my J510GN.
Doesnt lag while gaming.
jscheah said:
works great on my J510GN.
Doesnt lag while gaming.
Click to expand...
Click to collapse
What rom do you use?
Kernel is very good.It's on par with quasar.It matches quasar for gaming and that is something.Games run fast and smooth and framerates are great and sound is superb.The only negative was in memory it benchmarks 2000 less for memory than quasar but matches everything else.Will run it and see how battery is but that is minor to me.Nice work.
RicardoArantes said:
What rom do you use?
Click to expand...
Click to collapse
revenge os
Congratulations for the amazing kernel, my j510fn
I am really glad, you people like it @updesh94 thanks a lot man @Bogdans29 the BUS is already overclocked, it's designed to work at maximum speed with the specific overclock
deleted
Keep up the great work ??
jscheah said:
revenge os
Click to expand...
Click to collapse
Do you have the 3.0 link?
Battery is amazing doesn"t run at stupid high frequencies when not necessary and the battery usage is truly amazing hardly any percentage drop with phone apps been running 5 hours and 3 hours deep sleep incredible.This is better than quasar.The memory benchmark the only difference but phone can deal with that.You have the best nougat TW kernel Bulgarian Jesus.Congratulations superb work.