WELCOME
I AM NOT RESPONSIBLE IF ANY DAMAGE OCCURS TO YOUR DEVICE USING THIS KERNEL
Supported Device Versions:
World Wide LTE
US LTE
WI-FI
Features:
V1.1
(Requirements - Busybox, Su)
Removed interactive default
increase read ahead to 3MB
Allow HD video playback with miricast
Enabled multicast ip support
Implemented KEXEC
Implemented CIFS (module)
Implemented ASYNC FSYNC
init.d support (Unfinished/not-working) Can use universal init.d from playstore
Basic CPU control script under /etc/init.d
Basic GPU control script under /etc/init.d
V1.0
CPU Overclock 2.5Ghz
GPU Overclock 900mhz
CPU Undervolt
GPU Undervolt
FIOPS default
XZ Compression/Decompression
WIFI Speed Increase
Supports USB Storage Devices
Hardware Accelerated AES
SHA512
Parallel Encrypt/Decrypt
PS3 Controller Support
Thermal Governors (Default Step-Wise)
DevFreq Governors
Installation:
1. Download kernel zip file
2. Reboot into recovery
3. Install zip file
Bugs????
1. From terminal/command line adb pull /proc/last_kmsg
2. Upload to pastebin/gdrive/devhost
3. Link the uploaded file in this thread along with the description about the issue.
To do List
VOLTAGE SYSFS
V1.1
Download Links:
Devhost: http://d-h.st/3Wrf
Source Code:https://github.com/Shaky156/Shield-Tablet-CPU2.5Ghz-GPU060Mhz-Overclock
Is the overclock forced or can you use tools to lower to stock?
jeebuspwnz said:
Is the overclock forced or can you use tools to lower to stock?
Click to expand...
Click to collapse
The overclock is there, you can use an application to adjust max frequency
I really really want to flash this, but I'm kind of worried about what overclocking will do to this chip, as my shield tablet gets quite warm just on stock playing intensive games.
On my 16gb WiFi model running stock, rooted, my shield freezes 30 seconds after boot when running this.
jeebuspwnz said:
On my 16gb WiFi model running stock, rooted, my shield freezes 30 seconds after boot when running this.
Click to expand...
Click to collapse
Same here... I tried to underclock, still freeze and black screen.
FoxyDrew said:
I really really want to flash this, but I'm kind of worried about what overclocking will do to this chip, as my shield tablet gets quite warm just on stock playing intensive games.
Click to expand...
Click to collapse
The device is overclocked and undervolted so the only way to damage the device is if you hit it off a wall lol!
jeebuspwnz said:
On my 16gb WiFi model running stock, rooted, my shield freezes 30 seconds after boot when running this.
Click to expand...
Click to collapse
lowsum said:
Same here... I tried to underclock, still freeze and black screen.
Click to expand...
Click to collapse
Thank you not all devices will support undervolt at that level i shall adjust it.
Just to make sure can someone pull me a log? adb pull /proc/last_kmsg
OP Updated with newer build, this should stop freezing and reboots, but its best to provide a log
Double tap 2 wake
Do you think it could be possible to add Dt2W feature?
Seems to work
Question though... how do you disable shield power control? It seems to force the CPU min/max same
lupick said:
Do you think it could be possible to add Dt2W feature?
Click to expand...
Click to collapse
I can take a look into this a little later, it wont be good on the battery...
xxsashixx said:
Seems to work
Question though... how do you disable shield power control? It seems to force the CPU min/max same
Click to expand...
Click to collapse
Other governors are available but userspace is set at the default if anyone wants to control it within their shield power control settings
Ill let you all decide if you want to allow shield power control to modify cpu freq or if you dont want that
Shaky156 said:
I can take a look into this a little later, it wont be good on the battery...
Other governors are available but userspace is set at the default if anyone wants to control it within their shield power control settings
Ill let you all decide if you want to allow shield power control to modify cpu freq or if you dont want that
Click to expand...
Click to collapse
What I think I meant was that shield power control is very stubborn.
I set it to optimized mode but then I used setcpu to control the min max but then it won't apply as shield power control controls the freq
xxsashixx said:
What I think I meant was that shield power control is very stubborn.
I set it to optimized mode but then I used setcpu to control the min max but then it won't apply as shield power control controls the freq
Click to expand...
Click to collapse
Hi, OP updated with kernel with ondemand governor, userspace disabled.
Edit: I see, will need to look into that, that'll be implemented in a future update
Would it be possible to add CIFS support?
V1 = much better. My tablet is stable.
wawyed said:
Would it be possible to add CIFS support?
Click to expand...
Click to collapse
The original release had cifs enabled, but it causes issues, unfortunately the device does not boot with cifs
Is there any change with 2.2.1 OTA? Or can i flash it without losing any change?
Shaky156 said:
The original release had cifs enabled, but it causes issues, unfortunately the device does not boot with cifs
Click to expand...
Click to collapse
We've got another kernel that works with CIFS, maybe it's the implementation of it that you are using that's causing the issue?
wawyed said:
We've got another kernel that works with CIFS, maybe it's the implementation of it that you are using that's causing the issue?
Click to expand...
Click to collapse
Cifs implemented
Great Work!
Flawlessly running at 2.5Ghz
Hey, how do I control the GPU clock? GPU control doesn't show on kernel tuner :/
Related
TKSGB KERNEL HAS BEEN RENAMED TO KGB KERNEL!
NEW THREAD HERE
PLEASE DISREGARD THE REST OF THIS POST
----------------------------------------------------------------------------------------------------------------------------
There aren't very many tweaks in yet but it should be stable again and a lot of ext4 and lowmemkiller lag issues should be gone! Here's an incomplete list of features.
Voodoo: Lagfix and sound. No color for now
CPU governors: The same ondemand, ondemandX, interactive, interactiveX, smartassv2 and ondemandX as default
I/O schedulers: The same cfq, bfqv2r1, sio, deadline, vr and deadline as default with the last three being optimized for flash
jhash3, OC/UV, BLNv9, 3rd-party batteries, boot animations
LED flashlight, CIFS and TUN
zram
User-adjustable in-call audio boost, no boost by default!
Preliminary dock audio support, need more feedback
Autogroups and Tiny RCU removed pending performance evaluation
How to adjust in-call audio and zram
Run callboost or zram from a root prompt (AS ROOT). To manually tweak zram size or call boost volumes, look in /etc/init.d/ for the startup scripts they drop after enabling. The filenames are 05zram and 91callboost.
Recommended settings for callboost are 1 or 2, 0, 0, and 0 or 1. zram is 12.5% of available RAM by default.
The zram script crashes when enabling if there isn't enough RAM free. Don't run zram enable unless you're sure you have enough RAM on hand, such as right after a fresh reboot.
How to use dock audio
Preliminary testing (thanks ACLakey even if you do have a Mesmerize ) indicates it does something right. I have no way to know if it's doing something wrong or even if it doesn't work at all so give me feedback.
How to use your phone as an access point
Get the latest Wireless Tether for Android (3.0b6 last I checked), and set mode to Samsung softap in the settings. It won't be peer-to-peer and WPA2 encryption will work.
"STABLE" DEVBUILD 1027
CWM zip: http://www.mediafire.com/?tjsadn6v0cocqy6
Odin: http://www.mediafire.com/?redm61dt4uwjpt2
Oh, and just because...
"BLEEDINGEDGE" DEVBUILD 1116
CWM zip: http://www.mediafire.com/?mg78n9a77sje6e4
Changelog: Drivers/kernel settings from EI20, except for the dpram driver which is still from EH09. Removed carrier hotspot tracking code in init.rc (doesn't make hotspot tracker directories in /system), ARM and memory and RCU updates/tweaks, changes to scripts in ramdisk.
Still pretty untested
P.S. Don't confuse one for the other, thanks
Please excuse the mess below.
----------------------------------------------------------------------------------------------------------------------------
Kernel is alpha and untested for the most part, and I cannot guarantee stability or robustness of features. Still, I've been using it every day for a few weeks now, and it's pretty stable for me. It should work on most EH09-based ROMs out there, including PowerWashed, GeeWiz and TSM Resurrection, just to name the ones I know as I am a Fascinate user. It works with Mesmerize and Showcase too, I'm given to understand, with the proper ROM tweaks (which I don't claim to know anything about).
FEATURES
Voodoo: Lagfix, Sound v10, and Color v2. Use with Voodoo Control.
CPU governors: conservative, performance, ondemand, ondemandX, interactive, interactiveX (ondemandX as default)
I/O schedulers: Noop, CFQ, BFQv2-r1, SIO, V(R), Deadline (deadline as default). The last 3 are optimized for use with flash memory.
Autogroups, jhash3, Tiny RCU for responsiveness.
OC/UV up to 1.7GHz, with Voltage Control/Pimp My CPU.
Third-party battery support allows use and charging of aftermarket batteries and batteries for other Galaxy S phones.
No hotspot monitoring with the WiFi driver from the i9000.
In-call audio boost: Higher volumes and mic gain settings. Works OK as of 10/18.
CIFS and TUN included in base kernel. UTF-8 native language support was already there.
BackLightNotifications v9 with a ported touchkey driver from the i9000. Automatic installation of the proper liblights. Use BLN Control and/or Blinky to get down to business.
Bootanimations: Works with /data/local/bootanimation.zip, /system/media/bootanimation.zip, or /system/media/sanim.zip. Automatic installation of the proper bootanimation binary.
LED flashlight: The camera LED makes a surprisingly good flashlight. Activate with any of a number of flashlight apps from the Android Market.
zram from Linux 3 (credit imoseyon). Open up a terminal and run "zram" to get started. By default "zram enable" will use 12.5% of total RAM as an LZO-compressed ramdisk and set up swap space on that. Don't run the script unless you have at least 50MB or so of RAM free. To change the size of the zram, edit the relevant line in /etc/init.d/05zram (it's in bytes, do your own math) and reboot.
Other standard features: init.d support, adb shell gives you a root prompt
Various behind-the-scenes tweaks: A growing list of ARM and Samsung kernel/driver patches for hardware errata and Linux kernel patches to enhance interactivity
CHANGELOG
For complete changes refer to github.
Code:
[size=4][B]1018[/B][/size] Most changes on this one are behind the scenes.
[b]In-Call volume boost changes[/b] +12dB at earpiece only & mic gain boosts
[b]Update interactiveX and ondemandX CPU governors[/b]
[b]ondemandX as default[/b] i'm pretty sure this is a backport from linux 3 too
[b]Use CodeSourcery 2010q1 toolchain[/b] bad Linaro, bad!
[b]zram backport[/b] and add zram script to initramfs
[b]Memory tweaks[/b] optimize memcpy functions, tweak lowmemorykiller
[b]Bugfixes[/b] to autogroups and a couple other things
[b]initramfs changes[/b] probably falls under bugfixes actually
[size=4][B]1012[/B][/size]
[b]In-Call volume boost changes[/b]
[b]dvfs lock fixed[/b], no more pegging CPU at 1440MHz with bluetooth
[b]lowmemkiller settings[/b] changed in init.rc
[size=4][B]1010[/B][/size]
[b]In-Call Volume boost[/b] numbers were chosen arbitrarily, need detailed feedback
[b]Autogroups, [strike]Tiny Preempt RCU[/strike][/b] woopz
[b]Bootanimation support[/b] install required binary on boot
[b]Add ondemandX CPU governor[/b]
[b]ondemand as default[/b] interactiveX pegs the CPU high on hw video playback
[b]optimize sio and vr[/b] for flash devices
[b]Voodoo Color fix[/b] no more green tint at low brightness
[b]More tweaks[/b] ARM, Samsung, buildflags; see github
[size=4][b]1006[/b][/size]
[b]Third-party battery support[/b] apparently works fine as of 10/10
[size=4][b]1005[/b][/size]
[b]BackLight Notifications[/b], neldar-flavored, finally!
[b]Installs liblights on boot[/b]
[b]deadline scheduler[/b] tweaked for flash memory
[b]interactiveX governor is default[/b]
[size=4][b]0927[/b][/size]
[b]Initial release[/b]
KNOWN ISSUES/TO-DO LIST
Dock audio: I've almost got this merged but have no dock and no way to test.
Lots more tweaks and testing. I know it isn't fully polished and some things could use cleanup and updating. There is also a veritable sea of tweaks out there that I haven't even started parsing through.
Autorooting, autoinstall of busybox, bash, nano, and a bunch of obnoxious init.d scripts
Recovery with crazy rainbow colors and logos, etc.
TKS does not yet come with CWM. The version most of you are using is probably the blue ClockworkMod Recovery 3.0.2.8x by I believe times_infinity. It's pretty compatible with my kernel with a couple of minor bugs. Mirrors: http://www.mediafire.com/?91cq99066cwph4d http://www.multiupload.com/QEP9U2MC2G
CWM-FLASHABLE ZIPS
NEW 1018 http://www.mediafire.com/?07nero2764ktcn4 http://www.multiupload.com/V81P3FNJOD
1012: http://www.multiupload.com/JFLEF7U7EH
1010: http://www.mediafire.com/?9f58oks4a988a7o http://www.multiupload.com/PDXE2U08IG
1006: http://www.mediafire.com/?ev1g554de7ab9g0 http://www.multiupload.com/KB7833E0E4
1005: http://www.mediafire.com/?em8md8yxq7o61ny http://www.multiupload.com/EHJFAPYW51
0927: http://www.mediafire.com/?76ea7izaqc3e7a2 http://www.multiupload.com/O1HRXNCQQW
ODIN TARS
NEW 1018: http://www.mediafire.com/?didta4h7vk0uh8p http://www.multiupload.com/EXS2REYBAI
1012: http://www.multiupload.com/W8VZQGA3AG
1010: http://www.mediafire.com/?2tiiwoeav61ha0f http://www.multiupload.com/4XORWQIQIZ
1006: http://www.mediafire.com/?p9u3ow2mw70n26c http://www.multiupload.com/58XYU7OF86
1005: http://www.mediafire.com/?5ojvasq4lurvxnp http://www.multiupload.com/4W2GPSZHU7
0927: http://www.mediafire.com/?rqwe26c1pi4766r http://www.multiupload.com/JST3N8AAIP
GITHUB
All I do is kang other people's work, get it?
https://github.com/kangtastic
Also where you can see the full changelogs.
THANKS
imoseyon: Merged Voodoo Lagfix by hand. Also, he and the next two guys and I are like the only ones doing anything with the TW GB kernel on this phone.
ccampos784: Merged Voodoo Sound, and some other dev work before I forked his branch.
djp952: Ported the i9000's Wi-Fi driver and killed VZ's hotspot monitoring dead. It wasn't the only thing he ported from the i9000 to get EH09 building. And on that note...
The Samsung Galaxy S i9000: It is truly the gift that keeps on giving. Comparing good work i9000 people have done on the i9000 and CM7 repos with the EH09 code makes broken things work again, period.
TeamSbrissenMod & Supporters: The TSM-Resurrection ROM got me to try EH09, but they've done lots of great work over the last year.
jt1134: Got me started with cross-compiling my first kernel, and he is responsible for most of the innovation on this phone.
Other "historically important" people: adrynalyne, imnuts, SirGatez, nemesis2all, navenedrob etc.
IRC people too numerous to list and random people too numerous to list from whom I have taken all sorts of ideas and code that ended up in this kernel
DISCLAIMER
I am not a developer and the sole reason I started was so that I could be happier with the kernel I use on my own phone. If something does not get added or fixed, you are welcome to do it yourself.
I take no responsibility for exploding phones, voided warranties, missed appointments, dead babies and the like which are claimed to be related to your decision to use my kernel in any way. You're in the "development forum."
That said, feel free to leave useful feedback and suggestions. For bug reports, link logcats and dmesg output. And enjoy!
INFORMATION REGARDING OC/UV VALUES
The default values in the Samsung source are as follows:
1000MHz arm_volt=1275mV int_volt=1100mV
800MHz arm_volt=1200mV int_volt=1100mV
400MHz arm_volt=1050mV int_volt=1100mV
200MHz arm_volt=950mV int_volt=1100mV
100MHz arm_volt=950mV int_volt=1000mV
arm_volt_max=1350mV int_volt_max=1250mV
Of these the values that everyone talks about are the arm_volt values. arm_volt is what is modified by Voltage Control, Pimp My CPU, etc. int_volt is a secondary line that is not reported or directly adjustable by the user. The Glitch kernel plays around with int_volt for their different "leakage" versions, demonstrating that int_volt, too, plays a significant role in max overclock, but this isn't a concern of mine at the moment.
arm_volt_max is set to 1350mV which would then be the theoretical "overvolting limit". In this example you could overvolt 1000MHz by up to +75mV before running into driver limits.
Here are the default values in TKS.
1700MHz arm_volt=1500mV int_volt=1250mV
1600MHz arm_volt=1500mV int_volt=1250mV
1500MHz arm_volt=1500mV int_volt=1225mV
1440MHz arm_volt=1500mV int_volt=1200mV
1400MHz arm_volt=1450mV int_volt=1175mV
1300MHz arm_volt=1400mV int_volt=1150mV
1200MHz arm_volt=1350mV int_volt=1125mV
1000MHz arm_volt=1250mV int_volt=1100mV
800MHz arm_volt=1200mV int_volt=1050mV
400MHz arm_volt=1050mV int_volt=1050mV
200MHz arm_volt=950mV int_volt=1050mV
100MHz arm_volt=950mV int_volt=1050mV
arm_volt_max=1500mV int_volt_max=1250mV
Let's look at 100-1000MHz first. At 1000MHz there is a slight -25mV arm_volt undervolt (or just plain old undervolt) as well as a -50mV drop in int_volt for all frequencies <1000MHz. In other words, for stock frequencies there is already an undervolt built right in that you should take into account.
At higher clock settings the values are essentially best guesses at the proper settings for that speed, refined by community experience, so talking about a "proper" undervolt level is a little bit inaccurate. Note that voltage is maxed out at 1440MHz and above, but the secondary int_volt values keep increasing. The effect is a ramping up of total power supplied with increasing clockspeed, as it should be.
So I wouldn't be at all surprised to see 100-1000MHz benefitting from a couple +25mV boosts compared to "the settings I used to use on my old kernel" here and there and I'd pay attention to differences between the default voltages, especially 1200MHz+, of the old and new kernels. With different defaults, seemingly different undervolt settings could translate into the exact same amount of mV supplied.
awesome man...great to see eh09 finally getting some kernel love
hopefully once imoseyen gets his i500 from someone sending it, u can get some more help as well
(if u bet bln working ill reactive my fascinate for awhile lol)
I can give feedback about what DOES work despite being in alpha stage:
Voodoo color is working (personally, I like to go "punchy" on gamma hack)
OC is stable at least to 1400 for me with default noop/interactive, and with 100mhz state disabled (I could only go up to 1200 on MIUI without immediate instability on Glitch)
My phone is quite stable (so far) on this kernel, more so than what you'd expect on an alpha release
I'm glad you posted your own thread for this kernel comeradesven
Another Fascinating post by my XDA app...
This kernel is what I've been looking for
With a battery fix and in-call volume fix, I think I'll have a permanent GB solution! I'm hard of hearing and most of these GB kernels just don't cut it for me. CM7 (MTD) works, but Slacker caching doesn't work because of the file system. Slacker says tough s**t, we're not supporting it. So here we are. I'll put this on my spare Fassy and test it out today.
I'm also hard of hearing, but in-call isn't too, too bad for me on speakerphone... Media volume, on the other hand... IDK if media volume has anything to do with this kernel or if it's an EH09 issue...
Another Fascinating post by my XDA app...
Does this kernel use the Nexus S color source like on Glitch's kernel?
FDro said:
Does this kernel use the Nexus S color source like on Glitch's kernel?
Click to expand...
Click to collapse
If you're talking about mDNIe values, then no. I tried adding some new values earlier and it didn't work. It does have a ported Nexus S framebuffer driver like all Voodoo Color kernels AFAIK.
Awsome work sir!!
which one is better... voltage control or pimpmycpu?
now i use voltage control oc up to 1400 with uv 50 all way down. so far run smooth.
i use noop and ondemand, if i use conservative then phone get lag
I purchased SetCPU originally, can I use it instead?
Sent from my SCH-I500 using xda premium
djblu said:
I purchased SetCPU originally, can I use it instead?
Sent from my SCH-I500 using xda premium
Click to expand...
Click to collapse
IIRC the answer to that for this variety of overclock code is as follows.
Short answer: No
Long answer: Maybe but you might/probably will have problems
will this eventually have a -100uv kernel. i've the best battery life using pbj kernels with that setup. hope this gets it too. will switch kernels once all the kinks get worked out.
thx for your efforts.
mgrimmenator said:
will this eventually have a -100uv kernel.
Click to expand...
Click to collapse
Voltage Control = roll your own undervolt
The only real missing feature is BLN.
Can't seem to get it to download on my fiancee's phone.
Just flashed 9-27 through cwm and flashlight confirmed working. Awesome job
sent from my SCH-I500 PWGB 2. 0b3 voodoo , shot v7
Does this kernel support non OEM batteries?
Idea: RAM optimization, if feasible
Another Fascinating post by my XDA app...
So far this kernel is working out great for me. Loving voodoo color. Makes me wish I waited on buying that Thunderbolt off eBay. The cwm file didnt work for me (probably a bad download, stayed on bootanimation for WAY too long, lagging the animation) so I used the Odin version instead. Booted instantly. Many thanks for putting this together.
Sent from my SCH-I500 using Tapatalk
Originally Posted by djblu
I purchased SetCPU originally, can I use it instead?
Sent from my SCH-I500 using xda premium
Click to expand...
Click to collapse
IIRC the answer to that for this variety of overclock code is as follows.
Short answer: No
Long answer: Maybe but you might/probably will have problems
Click to expand...
Click to collapse
Thanks for the clarification. next question:
how do keep from getting stuck in boot loop? Do I need to reflash my recovery immediately after flashinging the kernal?
Sent from my SCH-I500 using xda premium
Ok guys this is my first overclocking app, including the following features:
Simple management of Processor Frequencies (Min and max)
Governors management with a gesture (Swipe down)
IO Schedulers management with a gesture (Swipe up) *new
Save as safe feature, wich means you have less chance to make some excesive overclock damage
Run at boot option
Visualization Settings
Requirements:
Android 2.2+
Kernel support for overclocking
Rooted device
Features planned:
-Profiles and notifications
-Voltage control (if kernel supports)
-AutoSet best config *new
Links at second post.
Some screenshots
02/04/2012 - v1.2
Fixed some fc while switching frequences on SeekBar
Fixed wrong sort of frequencies (now always from lesser to greater)
New ICS UI (only for ICS devices)
Almost done time / temperature profiles
Changed write method to command echo "frequency" > /sys/blah...
Current ram usage - 5MB, size 45.9KB
24/01/2012 - v1.1
Profiles implemented
Save as safe feature is better now (long click to show current saved)
Profiles (for now only battery level)
Notification system (also customizable led color settings*)
Independent performance settings submenu (for now just "pi" test, wich means a load test calculating pi number on loops)
Bugfixes and improvements
Current ram usage - 2.3MB, size 45.4KB
*This feature may not work on some devices
20/01/2012 - v1.0
First release
Official List of Current Working Devices:
Samsung Galaxy S / S2 - Fully working
Sony Ericsson Xperia Family - Fully working
Huawei U8800 (IDEOS x5) - Fully working
Milestone 1 - Fully working
LG Optimus One / 2X - Fully working
LG GT540 - Fully working
Which kernel is better for this app??
icerebro said:
Which kernel is better for this app??
Click to expand...
Click to collapse
That doesn't depends on kernel, app will adapt on any kernel if it support overclock (all kernels in mini and mini pro does support oc)
I've tested and works perfectly...!
I used with Naa Kernel and Rom
As soon as I set vlaue 768 and apply phone reboots. I this just me?
hey!! D4.
nice to see u again in this forum. thank you
Banwell13 said:
As soon as I set vlaue 768 and apply phone reboots. I this just me?
Click to expand...
Click to collapse
this happens to me too (not thru the app, i OC using CMsettings) some minipro's can seemingly go only upto 691 MHZ withh one oc module..
for example with nAa kernel i can go only upto 691Mhz but with zombipanic kernel i can go to 800Mhz dunno y...
hey! d4. i saw gpu overclock stuff in ur github sources. any progress??
siddardha21 said:
hey! d4. i saw gpu overclock stuff in ur github sources. any progress??
Click to expand...
Click to collapse
Nope, GPU clocks seems to be complex to mod. And now im not in vacations so my time is not a lot cuz im almost always busy
Good work D4!!
and the app it's really small 33KB!!
just suggestions:
1
it's possible to have the stability test in a single option too?
...not linked to the save as safe feature??
2
..to write somewhere the swipe options
just in case of memory loss
thanks
ciribaski said:
Good work D4!!
and the app it's really small 33KB!!
just suggestions:
1
it's possible to have the stability test in a single option too?
...not linked to the save as safe feature??
2
..to write somewhere the swipe options
just in case of memory loss
thanks
Click to expand...
Click to collapse
I will do your first suggestion, was already planned, the other one i dont know if is so relevant
It seems my kernel doesn't support over clocking
The sliders are not moving, I guess I will have to replace the kernel. which one do you suggest? I have an Arc S.
DeepUnknown said:
It seems my kernel doesn't support over clocking
The sliders are not moving, I guess I will have to replace the kernel. which one do you suggest? I have an Arc S.
Click to expand...
Click to collapse
Could you tell me your Kernel's name (even better upload a screenshot of about phone in settings)?, also 2 more things, is your phone rooted, and did you allow superUser permissions to simple OC ?
Hi,
I cannot choose any IO schedulers - I have only 'noop' in every governor.
HTC Desire Z here and my kernel is 2.6.35.14-Andromadus-Flinny-v1 (from Andromadus ICS v8 rom).
Any suggestion?
Greets & thx for the app!
can i use this to underclock stock kernel?
stemer said:
Hi,
I cannot choose any IO schedulers - I have only 'noop' in every governor.
HTC Desire Z here and my kernel is 2.6.35.14-Andromadus-Flinny-v1 (from Andromadus ICS v8 rom).
Any suggestion?
Greets & thx for the app!
Click to expand...
Click to collapse
Can you upload a screenshot?, that may be because your kernel only supports noop io scheduler.
EDIT: On my stock kernel with no custom io schedulers, the list is reduced, so that does means your kernel only supports Noop scheduler.
romy134 said:
can i use this to underclock stock kernel?
Click to expand...
Click to collapse
Im not sure, but i will try and say you
EDIT: Yes you can, but with the new version, will release soon. Also, sliders cant be moved if your kernel does not support overclock, but you can setup easily a powersave governor, wich will underclock your cpu
universal?
what devices does this app support? all androids running 2.2+ or just xperia? i would assume that with SetCPU mentioned in the op that it is universal, but wanted to make sure. TIA
esthernrob said:
what devices does this app support? all androids running 2.2+ or just xperia? i would assume that with SetCPU mentioned in the op that it is universal, but wanted to make sure. TIA
Click to expand...
Click to collapse
My aim is to make it universal and lightweight as hell! ill need support from all devices owners, for now, it should work on any device, anyway please test it. I will release a "more universal" version soon, im talking about 2 days, almost done now.
ok nice app but its been done alread about the exac same thing with NOFRILLS CPU thats out in the market for free and has been out longer and suports more languages . so dont know why this app got recognition on xda while nofrills cpu didnt and its been out longer... if anyone intrested look up nofrills cpu its the same thing ..... ps. im not tolling or hateing just thought id point it out ...
TerraSilent 1.3.5
{
"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"
}
After a lot of testing I can release it
Well sorry for the /data partition, I don't know why, but it's stuck at RFS. I format it, I tried everything, everytime you relaunch the recovery and try to mount the partition, it mount it as RFS and wipe it out.
I advice you to let it as RFS or, change it to ext4 when you are sure you won't need to do further change in it from the recovery.
Click to expand...
Click to collapse
THIS IS ONLY FOR THE INTL AND USA VERSION OF THE GALAXY PLAYER 4.0 (YP-G1).
The kernel is based on the R3 version of Klin1344.
Current features :
All features of R3 of Klin Kernel (see below)
Battery life improvement using the patch of Entropy512
Jhash3
Optimized CFS (process scheduler)
A lot of memory tweak
TinyRCU
New Governor created for the kernel (based on smartassV2) : TerraSilent (I recommend you to use it)
CleanCache (using zCache) (see below for explanation)
zRam (see below for explanation)
Updated crc32 algorithm (that is quite used everywhere in the kernel)
Using optimized Sha1 algorithm
Lzma compressed initramfs
Swap enabled
New Boot logo (same image (but bigger) as the one in the begin of the Thread)
Feature Coming from based kernel :
V(R), BFQ, SIO Scheduler
OC to 1.2GHz
ClockWorkMod (recovery)
interactiveX, smartassV2, ondemandX, and the default governors.
Netarchy/coolbho3ks SoD patch from Entropy512's source (allows you to use screen off profiles of under 800Mhz)
Ext4 support
Voodoo Sound
etc ... see http://forum.xda-developers.com/showthread.php?t=1601773
Changelog
Version 1.3.5
[RECOVERY] Optimization of the recovery with better use of the busybox
[RECOVERY] Can save the /dbdata partition in nandroid
[USA] Added VOODOO FM
Version 1.3
[CHANGE] Zram built-in not a module anymore
[BUSYBOX] Updated busybox to last version 1.20.1 meaning any init.d script will be launched with that version.
Version 1.2
[MAJOR BUG FIX]Corrected a bug with the recovery that wasn't able to mount correctly the /data partition, it was leading to a complete wipe of data when applying ZIP that needed that partition to be mounted
[OPTIMIZATION]Using LZO Compression for ZRam also, after some test, I discover that Snappy compression is not really optimized on our device.
Feature Explanation :
faux123 said:
CleanCache (via ZCache backend)
ZCACHE is a new technology I introduced to Sensation Kernel. ZCACHE is a compressed cache similar to ZRAM but the similarity ends there. ZCache is meant to provide as many "cleancache" pages (non-dirty or untouched "virgin" memory) to apps that request for new memory. CleanCache is very easy to allocate and no additional penalty are required to hand them out, so having more CleanCache pages will improve performance. Under heavy memory pressure, often times the kernel will NOT have enough CleanCache pages, so the kernel has to do EXTRA work to reclaim dirty cache pages and clean them for the new apps that's requesting for them. The described process creates a performance hit for the kernel and the app, so the idea is to use compression to create more CleanCache pages available for use. Of course there's a penalty to pay for using compression, but the trade-off between compression penalty and the penalty for reclaiming dirty cache pages and allocating them after cleaning is smaller for compression, so in the end, CleanCache should add more performance.
Source : http://forum.xda-developers.com/showthread.php?t=1359951
Click to expand...
Click to collapse
faux123 said:
ZRAM (aka CompCache aka RAMZSwap)
ZRAM is an updated version formally known as CompCache and RAMZSwap. It was originally designed for 2.6.38.xx kernels, I have backported to our 2.6.35.xx kernel. ZRAM allows real-time compression of memory objects in RAM thus reducing memory pressure for the Linux kernel and can keep more apps in memory longer (more apps in RAM == better performance, less fetching from slower MMC or SDCard). Compression, however, is not Free. Some CPU cycles are required to do the compress/decompression, so there's a slight penalty for it. The original CompCache / RAMZSwap required a user space binary to control its behavior which adds additional penalty to performance, but the new version ZRAM eliminated the need for a separate dedicated daemon, thus reducing the overhead and increased performance from the old CompCache by 20%. Therefore, with the newer implementation of ZRAM interface, the performance penalty is almost negligible.
Source : http://forum.xda-developers.com/showthread.php?t=1359951
Click to expand...
Click to collapse
Dark_Balor said:
TerraSilent Governor
TerraSilent is completely based on the SmartAssV2 kernel with some improvement for the battery. When you are putting your device on sleeping/suspend, it's changing the frequency to 100Mz (if you set a minimum higher then that, it will be used instead) to avoid using too much battery when not needed, you can still listen to music without any lag. (if you experience some lag just change the minimum to 200Mhz).
It also less aggressive on ramp up the frequency, instead of always trying to reach the ideal frequency (400Mhz by default, I'll explain for tweaker all they can change if they want) it will try under frequency first (200Mhz if you were at 100Mhz before). Meaning using less battery.
By default when the load >= 85%, it will ramp up the frequency and if its lower than 35, ramp down it to an new frequency calculated using the current load.
Click to expand...
Click to collapse
How to tweak/activate special features
By default zCache and zRam are disabled because they can be unstable depending on the device.
By example, I don't have problem with zCache but with zRam yes, and Klin the exact opposite. The better is to try for your device and then choose which one you want, the 2 or none.
zCache :
To activate zCache, you only need to put a script in your init.d directory (in etc) or using ScriptManager to launch that line on boot :
Code:
insmod /lib/modules/zcache.ko
zRam:
To activate zRam, you only need to put a script in your init.d directory (in etc) or using ScriptManager to launch theses lines on boot :
Code:
mkswap /dev/block/zram0
swapon /dev/block/zram0
Changing by script the governator to TerraSilent
if you don't want to use (but I recommend noFrill Cpu to do that) an application to change the governator, you just need to do :
Code:
echo terrasilent > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
Tweaking TerraSilent
in /sys/devices/system/cpu/cpufreq/terrasilent you'll find these files :
Code:
debug_mask --> for debug (possible value 0(disabled),1,2,4)
up_rate_us --> µs to wait before ramp up
down_rate_us --> µs to wait before ramp down
sleep_ideal_freq --> Freq used when sleeping/suspend
sleep_wakeup_freq --> Freq use when waking up
awake_ideal_freq --> Freq ideal for daily usage
sample_rate_jiffies --> DON'T TOUCH UNLESS YOU KNOW WHAT YOU ARE DOING
ramp_up_step --> step used when ramp up in Hz (to calcule the new frequency) (0 = maximum freq will be used when ramp up)
ramp_down_step --> step used when ramp down in Hz (to calcule the new frequency) (0 = using heuristic to found the best new lowered freq)
max_cpu_load --> max load that trigger the freq change for ramp up
min_cpu_load --> min load that trigger the freq change for ramp down
Where you can put your own values. (You have to do that after every boot, the best is to create a script that change the governor to TerraSilent, and set the wanted values)
FAQ
How to create a script
With ScriptManager it's easy, just push the menu button -> New -> Script
Put the script lines you want
Menu -> save
That's done
Manually : create a file name my-script.sh
put as first line :
Code:
#! /system/bin/sh
and then what you want your script to do.
Don't forget to do a
Code:
chmod +x my-script.sh
to make it executable.
Download (ODIN PACKAGES) :
http://www.mediafire.com/?cf9aw48dnmiqi
Source Code
Kernel : https://github.com/Belphemur/Galaxy-Player-4.0-Kernel
Initramfs : https://github.com/Belphemur/initramfs_yp-g1
If you love my work, don't hesitate to click the thanks button
Thanks to
Steve for the first modded kernel of our device
Klin1344 for continuing, improving the work of Steves and testing my kernel for the USA version.
Entropy512 for the battery patch, and a lot of other tweak
Faux123 for all the patch he have backported to the 2.6.35 kernel (zCache, zRam, etc ...)
THanks for your hard work in this kernel. You certainly know more about linux kernels than me.
But for some reason now enabling zram causes crashing and reboots but zcache does not. Oh well, at least one of them works!
klin1344 said:
THanks for your hard work in this kernel. You certainly know more about linux kernels than me.
But for some reason now enabling zram causes crashing and reboots but zcache does not. Oh well, at least one of them works!
Click to expand...
Click to collapse
I'm a Computer Sciences Student, and I already compile some kernel for my server, my computer ^^
It just my first kernel for an ARM device.
Thanks for your work the Kernel fixed the error i had with R2 and R3 ( the CPU speed was at 800MHz while the screen is off and music is on. SetCPU Profile dosent works too)
Sry for my bad english
Sent from my Nexus S using XDA
ChaosChris said:
Thanks for your work the Kernel fixed the error i had with R2 and R3 ( the CPU speed was at 800MHz while the screen is off and music is on. SetCPU Profile dosent works too)
Sry for my bad english
Sent from my Nexus S using XDA
Click to expand...
Click to collapse
I just flashed, but it still runs at 800mhz constantly while playing music with the stock player!
I am using the terraslilent governor.
Sent using Tapatalk
ChaosChris said:
Thanks for your work the Kernel fixed the error i had with R2 and R3 ( the CPU speed was at 800MHz while the screen is off and music is on. SetCPU Profile dosent works too)
Sry for my bad english
Sent from my Nexus S using XDA
Click to expand...
Click to collapse
I'm sure this is a stupid question, but I don't know the answer and the only way to learn is to ask, but how do you tell what the CPU is running at with music playing and screen off?
CPU spy (search for it on the market).
My theory is that the music player is programed to run at the max CPU speed available, which is 100mhz (I think) with the stock kernal. So, when you up the Max frequency to 800mhz, than the music player runs at that. What I still don't get, though, is 1; why doesn't your terrasilent governor solve the problem for me like it did for others, and 2; why does flashing the stock kernal not solve the issue?
Anyway, I'm not entirely sure that it really is running at 800mhz, as I let it play music overnight for 8 1/2 hours, and it only drained 30% battery from 70% to 40%. That makes about 4% per hour, which seems alot lower than I would expect a device running at 800mhz constantly would get. What do you guys think?
Sent using Tapatalk
iJimaniac said:
CPU spy (search for it on the market).
My theory is that the music player is programed to run at the max CPU speed available, which is 100mhz (I think) with the stock kernal. So, when you up the Max frequency to 800mhz, than the music player runs at that. What I still don't get, though, is 1; why doesn't your terrasilent governor solve the problem for me like it did for others, and 2; why does flashing the stock kernal not solve the issue?
Anyway, I'm not entirely sure that it really is running at 800mhz, as I let it play music overnight for 8 1/2 hours, and it only drained 30% battery from 70% to 40%. That makes about 4% per hour, which seems alot lower than I would expect a device running at 800mhz constantly would get. What do you guys think?
Sent using Tapatalk
Click to expand...
Click to collapse
After a lot of testing, I'm sure the application is wrong (or disabling the early suspend state).
When suspended the device have a freq of 100Mhz, you can check it with this command :
Code:
cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_cur_freq
using adb when the device is suspended. You'll see it's 100Mhz (or the min you set if the min above 100Mhz)
The other test you can do is checking the time in state
Code:
cat /sys/devices/system/cpu/cpu0/cpufreq/stats/time_in_state
You'll see that is passing more time in 100Mhz and 400Mhz then every other states.
(for the stats SetCpu or NoFrillCpu can read it for you)
Well, setcpu says the same as cpuspy: constantly 800mhz. However, I just ran it for 1 hour, from 100%, and it drained 4%. While I used to get around 2% per hour, this still seems fairly low consumption to actually be at 800mhz. I guess I will just live with it.
One more question; is there a way I could "undo" the SoD patch, or whatever would be causing this? I thought it would be as simple as flashing stock kernal, but not so. Would a flash of a stock kernal AND factoryfs.rfs do the trick?
Actually two more questions, lol; you realize that this is only happening with the stock music app; all other apps work fine. (Just not sure if I actually made that clear)
Sent using Tapatalk
got the kernel loaded up and since my primary use of my player is music playback i've used nofrills to underclock my cpu to max out at 400 mhtz, my question is can I and if so what app to use, to under volt my cpu to maximize my battery life?
daniel644 said:
got the kernel loaded up and since my primary use of my player is music playback i've used nofrills to underclock my cpu to max out at 400 mhtz, my question is can I and if so what app to use, to under volt my cpu to maximize my battery life?
Click to expand...
Click to collapse
Voltage control (free) will let you UV
iJimaniac said:
Well, setcpu says the same as cpuspy: constantly 800mhz. However, I just ran it for 1 hour, from 100%, and it drained 4%. While I used to get around 2% per hour, this still seems fairly low consumption to actually be at 800mhz. I guess I will just live with it.
One more question; is there a way I could "undo" the SoD patch, or whatever would be causing this? I thought it would be as simple as flashing stock kernal, but not so. Would a flash of a stock kernal AND factoryfs.rfs do the trick?
Actually two more questions, lol; you realize that this is only happening with the stock music app; all other apps work fine. (Just not sure if I actually made that clear)
Sent using Tapatalk
Click to expand...
Click to collapse
I have the governor set to smartassv2 and my cycles through. It was at 800 mhz for about 35% of the time. I'm using PlayerPro with the DSP pack and voodoo sound, though, and not stock.
Yeah, just something wrong with the stock player. Oh well, I'm going to buy poweramp since I just tried the trial and now the stock player seems pathetic anyway I love the lockscreen controls!
Sent using Tapatalk
iJimaniac said:
Yeah, just something wrong with the stock player. Oh well, I'm going to buy poweramp since I just tried the trial and now the stock player seems pathetic anyway I love the lockscreen controls!
Sent using Tapatalk
Click to expand...
Click to collapse
Quick off topic question... Can you get Poweramp's settings to stick? Such as to not show the rating, EQ, etc (the look and feel settings). I like Poweramp a little better (sounds about same as PlayerPro with DSP) but the settings being wonky bothers me.
Hmm, I don't remember and my trial is up. I don't think there was a problem (that I noticed).
Sent using Tapatalk
indyssee said:
Quick off topic question... Can you get Poweramp's settings to stick? Such as to not show the rating, EQ, etc (the look and feel settings). I like Poweramp a little better (sounds about same as PlayerPro with DSP) but the settings being wonky bothers me.
Click to expand...
Click to collapse
YES, under settings / Look and feel, just go in and set the things you don't want to see to Hidden.
daniel644 said:
YES, under settings / Look and feel, just go in and set the things you don't want to see to Hidden.
Click to expand...
Click to collapse
That's my point, it just ignores everything and doesn't change anything. I've tried all different ways to get them to stick. Doesn't work on my phone, either.
indyssee said:
That's my point, it just ignores everything and doesn't change anything. I've tried all different ways to get them to stick. Doesn't work on my phone, either.
Click to expand...
Click to collapse
Have you tried unistalling rebooting then reinstalling? Are you on a custom ROM?
Any suggestions for a boot loop that doesn't involve wiping data?
rozelle25 said:
Any suggestions for a boot loop that doesn't involve wiping data?
Click to expand...
Click to collapse
NOPE, bootloops are caused by conflicting files and the ONLY way to solve is to WIPE.
You could try to get into Download Mode and flash back to the ROM/Kernel you where on before your flash that caused the bootloop.
as subject says. Has anyone tried this http://forum.xda-developers.com/showthread.php?t=1584508
Works pretty good for me
Note . Root needed i.e. for unlocked bl only
Sent from my Dell Streak using xda app-developers app
jitin02 said:
as subject says. Has anyone tried this http://forum.xda-developers.com/showthread.php?t=1584508
Works pretty good for me
Note . Root needed i.e. for unlocked bl only
Sent from my Dell Streak using xda app-developers app
Click to expand...
Click to collapse
here's the whole thread, note I have nothing related to Dev/team I am just reposting it to benefit xperia u,p,a,sola,go users
_______________________________________________________________
smokin1337 said:
CPU Editor
This mod allows you to easily change cpu settings on the fly, and supports dual core devices. Easier and cheaper $$ than available apps that do the same thing !!
Will work on most devices, it edits linux files so device manufacturer makes no difference.
Features:
Change CPU Governor
Change CPU Min/Max Frequencies
Apply Settings on Boot - Sticky Mode
Set Dual Core CPU's Independently - Governor and Frequencies
Force Dual Core - Second Core Online ALL The Time
Seperate Menus For Single and Dual Core Devices - Auto Selects
View Current Settings For Everything
Sticky Mode
OnDemand Profiling
Now uses config file to store values
Usage:
Open terminal
Type "su" without the quotes
Type "cpu" without the quotes
Make your selections
Notes:
An error appears sometimes when enabling or disabling force dual core, it's ok the settings still get applied.
Settings get applied immediately
Cores can be set independently, you can make the governors and frequencies different on each core. Could be a great battery saver by limiting the second cores resources.
Force Dual Core will make the second core stay online all the time
Some kernels do not have a available_scaling_freq so the available frequencies will not be displayed, look up the settings your kernel has either in your rom thread or kernel thread.
Sticky Mode will apply the settings you have made on reboot (requires init.d support- which most roms and most devices have)
OnDemand Profiling allows you to set profiles for ondemand governor, the settings possible are performance, performance and battery, and battery saver. Setting will only apply to ondemand govenor !! I will add more when i get some kernels for my one x.
The battery saver profile is ridiculous, my One X battery lasts a loooooong time with it on. I was at 19 hrs on battery and still at 71%. Try and see for yourself. Here is a screenshot: http://forum.xda-developers.com/showpost.php?p=27125704&postcount=3
Please report any bugs you may find here, this was tested on an evo 3d, one x, one s and a mytouch 4g.
Thanks to Orical for beta testing !!
Download:
http://goo.im/devs/smokin1337/Mods/CPU_Editor_RLS_4.zip
Click to expand...
Click to collapse
Code:
Your warranty is now void.
I'm not responsible for bricked devices, dead SD cards,
thermonuclear war, or you getting fired, because the alarm app failed. Please
do some research if you have any concerns about features included
before flashing it! YOU are choosing to make these modifications, and if
you point the finger at me for messing up your device, I will laugh at you.
So here it is. After testing for a few days I've decided to give out builds of CM 12.1 kernel with a little bit better CPU management.You may see improvement especially when you're not using 3G/LTE as it seems to drain battery almost as fast as before (depending on the use ofc). You'll get much better battery life on wifi though. You may tweak the settings using some kernel control apps but the recommended setup is already applied.
Features:
+ Bricked hotplug driver - turns off CPU cores if the CPU load is not big enough to need them.
+ Powersuspend - a driver that should turn off unused hardware components when screen is off
+ Quickwakeup driver - it allows some tasks to wake up the system to perform certain actions without fully resuming it
+ Min. CPU freq 200MHz (CM12.1 has it set to 800MHz but it seems we don't need it that high after disabling CRC checks)
+ Revised interactive governor target_loads to clock CPU more efficiently
Download:
Kernel:
CM12.1:
J500FN
J500F
J500G
J500H
J500M
J500Y
J5008
CM13:
J500FN
J500F
LOS14.1:
J500FN
J500F
J500H
J5008
GPU Max Frequency Limiting Scripts:
400 Mhz
475 Mhz
550 Mhz
650 Mhz
Installation:
Just flash the zip for your device in TWRP.
Changelog:
Code:
07.10.2017:
- First release rebased on @vince2678 kernel source and device trees (Will work only with his Los14.1 builds from now on, don't even try any older ROMs available)
- Added some tweaks by @Bulgaricus
24.07.2017:
- Rebased on newest LOS kernel
- Reimplemented some of tweaks previously reverted due to conflict (The most important being Display driver update, refresh rate should be better now)
30.05.2017:
- Merged upstream changes (new power hal compability etc.)
19.05.2017:
- Merged base kernel updates
- Enabled thermal core control
- Change throttling cpu temperature from 60°C to 80°C to avoid performance loss
- Enabled CPU_BOOST config
- Kernel now should boot on both LL and MM bootloaders (needs testing)
18.05.2017:
- First release for Lineage OS 14.1
- Rebased on @SoUnd001 kernel source (LOS 14.1 only)
- Drop CM1300/LOS13.0 support
02.03.2017:
- Fixed slow charging
- Cpusets tweaks for hotplug (multitasking related)
25.01.2017:
- Squashed update to 3.10.104
- Additional CPU & Battery tweaks
- Faster boot
16.01.2017:
- Major cleanup
- Tweaked recommended values
- Final release for CM12.1
- First release for CM13.0
08.01.2017:
- Added GPU OC up to 720MHz (you may change max frequency if you don't like OC or want it to be a little less thanks to the scripts included in downloads. Previous default freq was 400 MHz)
- Changed default gpu governor to simple_ondemand to avoid frequency bug described in #16
06.01.2017
- Initial release
- Added bricked hotplug driver
- Added powersuspend driver
- Added quickwakeup driver
- Changed CPU min freq. to 200MHz instead of 800MHz
- Optimized interactive's target_load
XDA:DevDB Information
Hotplug enabled kernel for Cyanogenmod 12.1/13.0, LOS 14.1, Kernel for the Samsung Galaxy J5
Contributors
Koloses, Nick Verse, ganesh varma, #Henkate, SoUnd001, vince2678, Bulgaricus
Source Code: https://github.com/hotplugj5
Kernel Special Features:
Version Information
Status: Stable
Created 2017-01-06
Last Updated 2017-10-07
GJ
great work on FN works pretty good
Awesome, can I request you to build one with 1.4 OC!? :silly:
Can you make for Ressurection Remix too?
Sent from my SM-J500FN using XDA Labs
Since most if not all of custom ROMs are similiar, this should work on RR, just try it. I'll look into overclocking later on since it's not the most needed feature and I wanted to release stable kernel first. I also plan adding adreno idler.
Koloses said:
Since most if not all of custom ROMs are similiar, this should work on RR, just try it. I'll look into overclocking later on since it's not the most needed feature and I wanted to release stable kernel first. I also plan adding adreno idler.
Click to expand...
Click to collapse
Yep, it's confirmed working on RR..
Well, GPU overclock seems to work (3D score) . We'll see about CPU later on as it doesn't seem to have any impact other than showing time in state. I'll add GPU OC to the next build.
First screenshot is without GPU overclock, second is overclocked GPU.
Sent from SM-J500 CM12.1
So to install this on RR we just have to flash in TWRP?
Sent from my SM-J500FN using XDA Labs
Cm 13 on lolypop bootloader will work?
Does this hurt the hardware in anyway? (Not using overclocking of course)
Sent from my SM-J500FN using XDA Labs
Koloses said:
Well, GPU overclock seems to work (3D score) . We'll see about CPU later on as it doesn't seem to have any impact other than showing time in state. I'll add GPU OC to the next build.
View attachment 3994178View attachment 3994179
Sent from SM-J500 CM12.1
Click to expand...
Click to collapse
I got higher GPU score without overclock (879).
Benchmarks may or may not reflect the real phone performance. Personally im against OC.
Any CM kernel should work on RR as well, since RR is using cm kernel.
Oh I didn't mention: First ss shows the score without OC (860) The second is OC'd (979) I'll test it further though because antutu is rather heavy benchmark. OC possibility will be included anyway but I'm thinking about making it enabled out of the box or not.
I did repeat it several times and just took 2 random screenshots from before and after. I'll edit the post to include that.
Sent from SM-J500 CM12.1
Koloses said:
Oh I didn't mention: First ss shows the score without OC (860) The second is OC'd (979)
I did repeat it several times and just took 2 random screenshots from before and after. I'll edit the post to include that.
Sent from SM-J500 CM12.1
Click to expand...
Click to collapse
Oh well, thats clearly an improvement
But im still against OC. I didnt experience any game lag when ive been playing.
OC will lead to higher temperature & battery drain. Personally, i prefer to use phone without OC, since it performs well.
Perhaps you can do a test with temperature when using CPU/GPU OC?
Alright tested this kernel and it works outstanding! My battery life has been improved and I really like that I can see how the cores turn themselves off when they are not needed, in Kernel Adiutor.
Works perfectly on RR
Sent from my SM-J500FN using XDA Labs
#Henkate said:
OC will lead to higher temperature & battery drain. Personally, i prefer to use phone without OC, since it performs well.
Click to expand...
Click to collapse
We'll see. Adreno Idler may compensate GPU OC battery drain, I need to test the temperatures too. It's only a matter of setting up default settings though because I also want to let people configure things to fit them while providing recommended configuration out of the box.
I could always apply OC out of the box and add flashable zip with init.d script to set stock frequency on boot so I won't have to build boot image twice for all the devices. Sounds fair to me.
Sent from SM-J500 CM12.1
Koloses said:
We'll see. Adreno Idler may compensate GPU OC battery drain, I need to test the temperatures too. It's only a matter of setting up default settings though because I also want to let people configure things to fit them while providing recommended configuration out of the box.
I could always apply OC out of the box and add flashable zip with init.d script to set stock frequency on boot so I won't have to build boot image twice for all the devices. Sounds fair to me.
Sent from SM-J500 CM12.1
Click to expand...
Click to collapse
I have tested Adreno Idler and according to latest Kernel Adiutor, it goes to 200mhz when phone is in idle so it is working fine and also i think there are less switches between GPU frequencies than before. Just like the other people, i have noticed battery improvement too using Adreno Idler. But read msm-adreno-tz governor bug below.
The GPU governor called simple_ondemand is working nice too. I searched for 1080p youtube video and GPU frequency stays at 200 always when watching a video (assuming the screen is not touched), which is great and can improve the battery alot for that task and also for reading.
Unlike simple_ondemand, msm-adreno-tz used to stay at 300-400mhz when watching same video. I havent tested yet with Adreno Idler though, but simple_ondemand seems a great choice for tasks like watching a video or reading something long.
When i tested msm-adreno-tz frequencies for first time (with the command from adreno idler thread, but the path is different for J5), i have found that msm-adreno-tz:
- use 300mhz freq when phone is in idle with screen on and on homescreen
- when you touch/keep sweeping with the finger on the screen (e.g. on homescreen), the GPU frequency goes to 200. It gets lowered instead higher LOL.
GPU MSM-ADRENO-TZ BUG, default on all kernels, both on stock and cm based roms.
If screen goes off (or you turn the screen off), then you turn it on, and then it goes off again (or you power it off) WITHOUT UNLOCKING THE PHONE AND TOUCHING THE SCREEN AFTER UNLOCK the GPU will stay at 400mhz until you turn the screen on, unlock and touch it.. This doesnt happen with simple_ondemand, where GPU stays at 200mhz always when screen is off or phone is in idle with screen on. Even if you dont have a lockscreen, the bug still persist.
GPU staying at 400mhz when screen is off, means that it will use power useless, for no reason. And also, it can lead to slower charging. I dont know how much power it use, but i know that it counts.
Unfortunately, even with Adreno Idler i see that the bug is still present. Or perhaps i havent implemented Adreno Idler properly? But i think i did.
This is the governor bug i wanted to talk about. I wanted to make a thread under general section.
I recommend simple_ondemand governor, although i see that it has more switches between GPU frequencies, it can lead to higher battery backup for tasks like watching a video or reading something long.
Im sorry for going a bit off-topic
EDIT:
@Koloses:
Run following commands in terminal to see the current GPU frequency, updated constantly:
PHP:
adb shell
cd /sys/devices/soc.0/1c00000.qcom,kgsl-3d0/devfreq/1c00000.qcom,kgsl-3d0
while true; do cat trans_stat; busybox sleep 0.1; done
The "*" shows the current frequency.
Total transitions = the number of total switches between frequencies.
Development talk is never ever an offtopic to me
Anyway, where did you get Adreno Idler from? https://forum.xda-developers.com/an...dreno-idler-idling-algorithm-devfreq-t3134872 This seems to be an official thread regarding it and explanation of how it works seems fine. It needs powersuspend, but we have that in kernel already. I'll look into implementing it after getting home.
Sent from SM-J500 CM12.1
Koloses said:
Development talk is never ever an offtopic to me
Anyway, where did you get Adreno Idler from? https://forum.xda-developers.com/an...dreno-idler-idling-algorithm-devfreq-t3134872 This seems to be an official thread regarding it and explanation of how it works seems fine. It needs powersuspend, but we have that in kernel already. I'll look into implementing it after getting home.
Sent from SM-J500 CM12.1
Click to expand...
Click to collapse
I got Adreno Idler 1.1 from other msm8916 kernel, as i had some troubles with the commits from the official thread ( i dont remember what troubles lol). I got PowerSuspend 1.5 from same kernel.
Im not sure if PowerSuspend is working. I enabled the debug mode, but i cant find any PowerSuspend line in dmesg, kmesg, neither logcat. But i have power_suspend folder & lib, and also i see that it is on hybrid mode, both in Kernel Adiutor and system file.
Also, in logcat (taken since boot), i see following error:
PHP:
W/libsuspend( 942): Error writing 'on' to /sys/power/state: Invalid argument
I/libsuspend( 942): Selected wakeup count
It is trying to write "on" to state file.
/sys/power/state file has two words: frezee mem.
#Henkate said:
I got Adreno Idler 1.1 from other msm8916 kernel, as i had some troubles with the commits from the official thread ( i dont remember what troubles lol). I got PowerSuspend 1.5 from same kernel.
Im not sure if PowerSuspend is working. I enabled the debug mode, but i cant find any PowerSuspend line in dmesg, kmesg, neither logcat. But i have power_suspend folder & lib, and also i see that it is on hybrid mode, both in Kernel Adiutor and system file.
Also, in logcat (taken since boot), i see following error:
PHP:
W/libsuspend( 942): Error writing 'on' to /sys/power/state: Invalid argument
I/libsuspend( 942): Selected wakeup count
It is trying to write "on" to state file.
/sys/power/state file has two words: frezee mem.
Click to expand...
Click to collapse
@Koloses
I have found this in ramdisk:
init.zygote32.rc:
Code:
service zygote /system/bin/app_process -Xzygote /system/bin --zygote --start-system-server
class main
socket zygote stream 660 root system
onrestart write /sys/android_power/request_state wake
[B][COLOR="Red"]onrestart write /sys/power/state on[/COLOR][/B]
onrestart restart media
onrestart restart netd
Thats why i got that error while booting, but i dont know why libsuspend is mentioned at the error. Also, there is no android_power folder.
This is on stock kernel 5.1.1.
Good work @Koloses !!! Keep up buddy Just to notify I had 31.800+ benchmark score with the well known kernel 5.1.1. of dj steve, without overheating... Personally I prefer more performance instead of battery life, so if you keep on tweak and overclock your kernel would be nice maybe a separate zip. To enable it. Have a nice day man!