Related
have been pratting about with this over the last day, have found the following.
I am using overclock module to set a custom setting of 900mhz/46vsel
However, when performing a cat /proc/overclock/mpu_opps I get the following
mpu_opps[3] rate=900000000 opp_id=3 vsel=46
mpu_opps[2] rate=600000000 opp_id=2 vsel=48
mpu_opps[1] rate=300000000 opp_id=1 vsel=33
So whilst we are changing the max_freq and max_vsel we are not doing anything to reduce the vsel on the lower frequencies and thus not getting max battery life. The stock vsel at 600mhz is actually more than 900!
So I made a script so as to change the vsel values to lower for the lower frequencies as below:
setscaling.sh
echo 46 > /proc/overclock/max_vsel
echo 900000 > /proc/overclock/max_rate
echo 1 300000000 28 > /proc/overclock/mpu_opps
echo 2 600000000 38 > /proc/overclock/mpu_opps
echo 3 900000000 46 > /proc/overclock/mpu_opps
echo 0 900000 > /proc/overclock/freq_table
echo 1 600000 > /proc/overclock/freq_table
echo 2 300000 > /proc/overclock/freq_table
mpu_opps then read as I want it:
mpu_opps[3] rate=900000000 opp_id=3 vsel=46
mpu_opps[2] rate=600000000 opp_id=2 vsel=38
mpu_opps[1] rate=300000000 opp_id=1 vsel=28
I can run the script manually, and it works a treat, however, on reboot it has to be manually applied. Tried a number of ways to get this to run at boot (scripts and also autostart app in the market) however it doesn't apply and the reason behind this is due to it trying to apply the script before the overclock module has been applied.
I then tried to exclude the Milestone overclock app and use the overclock.ko module directly into /system/lib/modules/overclock.ko. The module itself seems to run ok, however when I then apply my setscaling.sh it cause the phone to reboot.
So a few questions if anyone can help.
1)is there anyway to delay a script from running for a period of time after boot (eg once the overclock module has loaded)
2) Any ideas why the phone is rebooting when using the overclock module directly outside the app, but the script works fine in conunction with the app.
I think I am just missing something obvious thats staring me in the face!
I guess it would be quite simple for whoever coded milestone overclock to just add a setting where we can choose the vsel for multiple frequencies...
Good job though, was wondering also if that was possible!
Will try and find how to contact him
Damool said:
I guess it would be quite simple for whoever coded milestone overclock to just add a setting where we can choose the vsel for multiple frequencies...
Good job though, was wondering also if that was possible!
Will try and find how to contact him
Click to expand...
Click to collapse
I have added my setscaling.sh place it in /system/binx and execute it.
You can ammend it to put your own frequencies in there, be careful though!
Thanks will try when back from skiing
Higgsy, do you know how Android natively sets the frequency and voltage levels? Is there a config file or is it hard coded into the kernel or a module? My googling skills didn't turn up much.
Zaben said:
Higgsy, do you know how Android natively sets the frequency and voltage levels? Is there a config file or is it hard coded into the kernel or a module? My googling skills didn't turn up much.
Click to expand...
Click to collapse
The default levels should be the reset values in the hardware itself. The Milestone Overlock App contains a kernel driver to communicate with the OMAP processors PLL and voltage chip (the TWL5030 chip) using the I2C buss to be able to modify these registers and their reset values. Higsy is communicating with this kernel driver using the /proc to set some of the registers that the kernel driver has mapped out. So it's more a case of being able to set these registers when the kernel module is being loaded to avoid doing it once the driver has been loaded.
Xhit said:
The default levels should be the reset values in the hardware itself. The Milestone Overlock App contains a kernel driver to communicate with the OMAP processors PLL and voltage chip (the TWL5030 chip) using the I2C buss to be able to modify these registers and their reset values. Higsy is communicating with this kernel driver using the /proc to set some of the registers that the kernel driver has mapped out. So it's more a case of being able to set these registers when the kernel module is being loaded to avoid doing it once the driver has been loaded.
Click to expand...
Click to collapse
Yeah thats it, any suggestions then? At the mo I'm still running my script manually on boot after everything is loaded, to be fair I do it without thinking about it now, but would be good to automate it
Higgsy said:
Yeah thats it, any suggestions then? At the mo I'm still running my script manually on boot after everything is loaded, to be fair I do it without thinking about it now, but would be good to automate it
Click to expand...
Click to collapse
Hmmm, seems I was mistaken in my last post. The kernel driver does not write to the TWL5030 directly, some registers in this chip has already been mapped out by and OMAP kernel driver and the overclock kernel driver is just used to be able to get to the OMAP driver parameters and other kernel parameters. All this according to the documentation found in code.google.com/p/milestone-overclock/wiki/KernelModule . And according to the same you can set some parameters when you insmod the kernel driver, "insmod overclock.ko mpu_opps_addr=0xc050a848 max_rate=800000 max_vsel=62". So you could try to set the arguments you want in freq_table and mpu_opps at insmod instead to see if that works?
EDIT: According to the FAQ, changing the freq_table and mpu_opps can only be done using a script writing to /proc.
http://code.google.com/p/milestone-overclock/wiki/FAQ
Edit 2: Checked the source code of overclock kernel driver. And the freq_table and mpu_opps is not a module_param meaning you can not set them during kernel load. However it would be very easy to add a couple of module_params to the source code be able to set them during kernel driver load. However you would need the complete cross-compiler environment to build it once modified, which I guess is the major time consumer to make this change. So kindly asking Tiago Sousa whos written it would maybe be the quickest..
Xhit said:
Hmmm, seems I was mistaken in my last post. The kernel driver does not write to the TWL5030 directly, some registers in this chip has already been mapped out by and OMAP kernel driver and the overclock kernel driver is just used to be able to get to the OMAP driver parameters and other kernel parameters. All this according to the documentation found in code.google.com/p/milestone-overclock/wiki/KernelModule . And according to the same you can set some parameters when you insmod the kernel driver, "insmod overclock.ko mpu_opps_addr=0xc050a848 max_rate=800000 max_vsel=62". So you could try to set the arguments you want in freq_table and mpu_opps at insmod instead to see if that works?
EDIT: According to the FAQ, changing the freq_table and mpu_opps can only be done using a script writing to /proc.
http://code.google.com/p/milestone-overclock/wiki/FAQ
Edit 2: Checked the source code of overclock kernel driver. And the freq_table and mpu_opps is not a module_param meaning you can not set them during kernel load. However it would be very easy to add a couple of module_params to the source code be able to set them during kernel driver load. However you would need the complete cross-compiler environment to build it once modified, which I guess is the major time consumer to make this change. So kindly asking Tiago Sousa whos written it would maybe be the quickest..
Click to expand...
Click to collapse
Right I cracked it!
all I had to do was the following
My setscaling.sh resides in system/xbin
I created an Install-recovery.sh and placed in system/etc
The content of Install-recovery.sh is:
#!/system/bin/sh
sleep 90
setscaling.sh
Hence making the script wait 90 secs before it initialises my setscaling.sh - plenty of time for the overclock module to load.
It may not be the best solution but it works a treat.
Wow that was fast. I've been playing with the voltages and it seems that stability depends on both the starting freq/vsel and also the current battery level. For example I can lower the voltage for 300MHz slowly while staying at 300MHz, but jumping from 600MHz I have to be much more careful so the resulting vsel has be to much more conservative. Milestone-overclock isn't always successful when you hit "apply" (including false read back) and I had to use Quadrant's system info to verify each time. This was much more touchy compared to undervolting a laptop.
Is there an "init.d" directory? Equipment I work on have this directory and all across are run when it resets.
Sent from my MB525 using XDA App
Drop this file in your /system/etc folder, replacing the stock one. Cleaned up, and modified to work with a stock kernel or lean kernel.
Please open up the file, and read some of the notes I added, so you know what this does and how to change it if you so desire. It is very basic and straightforward.
Also, please remember one thing, if you want to go to the stock kernel, simply change any words in the scripts from "interactiveX" to "interactive".
Recommended lean kernel 3.16 with these scripts.
Designed to work with ALL Galaxy Note 3's running touch wiz 4.4.2 ROMs and running lean kernel or stock kernel. Other kernels are not guaranteed due to the voltages applied.
This will make a huge difference in performance and battery. Been using this (developed by me) for a long time now.
Summary:
*I/O optimization
*tuned interactive parameters
*fixed sysfs permissions for cpu's (root now has full control of sysfs tuneables)
*GPU sysfs identified for user to customize
*screen off frequency set to 1.2 GHz (can be changed by user)
*custom voltage set for bin 2 device. (Read instructions within file to adjust for others bins accordingly)
*custom mpdecision tuning and other relevant instruction regarding mpdecision binary
*general CPU tweaks for better performance, responsiveness and battery life (yes all 3 can be achieved, and are)
Again, open the file with a file explorer (or notepad+ in windows). Read it, understand it, adjust what you want, or leave it be. These settings are very much dialed in for the interactiveX governor of LK. It won't get much better. I'd say take a look at the voltage portion and mpdecision for now (found at the end).
Once more, drop file into the /system/etc directory... Replace the existing one, and reboot.
FILE DOWNLOAD
Updated today... many useful changes, and fixes (set up for stock kernel for now)
https://www.dropbox.com/s/tjlygujptls3lks/init.qcom.post_boot.sh?dl=0
Reserved for any common questions, or general information.
red_can_soda said:
Reserved for any common questions, or general information.
Click to expand...
Click to collapse
Nice bud, I'll have to see if it works on Lollipop TW
Using it in pvs bin 0 lol
So far so good. Make sure to set permissions to 755
i'll have to see if theres a difference between replacing the current file.... or firing it off in init.d
kevp75 said:
i'll have to see if theres a difference between replacing the current file.... or firing it off in init.d
Click to expand...
Click to collapse
Needs to be done post boot, otherwise the stock "post_boot" file does what it does post boot. Make sense?
Init.d executes earlier in the boot sequence. Therefore, some of the parameters will be overridden.
red_can_soda said:
Needs to be done post boot, otherwise the stock "post_boot" file does what it does post boot. Make sense?
Init.d executes earlier in the boot sequence. Therefore, some of the parameters will be overridden.
Click to expand...
Click to collapse
ehh but those if us who need a hack for init.d runparts inside this script (u have it in yours as well)
i have it in my init.d and it appears (notice the appears) to be working.
Im definately noticing a bit more responsiveness... as well I toned down the screen off max freq a bit and am getting pretty decent battery life.
kevp75 said:
ehh but those if us who need a hack for init.d runparts inside this script (u have it in yours as well)
i have it in my init.d and it appears (notice the appears) to be working.
Im definately noticing a bit more responsiveness... as well I toned down the screen off max freq a bit and am getting pretty decent battery life.
Click to expand...
Click to collapse
Forgot I had that there... Lol. Threw that in a while back so init.d would operate with a 100% stock boot.img
@kvp75, can I drop this into Phoenix Rom?
Chefedogg said:
@kvp75, can I drop this into Phoenix Rom?
Click to expand...
Click to collapse
It will work with any galaxy note 3 using Qualcomm hardware.
Chefedogg said:
@kvp75, can I drop this into Phoenix Rom?
Click to expand...
Click to collapse
shuld be able to... but dont really need to. phoenix has cpuntweaking built intobthe settings doesnt it?
sry been workin on DomPop
red_can_soda said:
Drop this file in your /system/etc folder, replacing the stock one.....
Click to expand...
Click to collapse
Lmao....Cob
kevp75 said:
shuld be able to... but dont really need to. phoenix has cpuntweaking built intobthe settings doesnt it?
sry been workin on DomPop
Click to expand...
Click to collapse
All good, I went ahead and did it anyway, it's def making a difference, battery life was not great but now it's better! Thanks for all the hard work guys, keep it up! I'll reflash DomPop again soon, it was unstable for me but Phoenix has been great
This activated all cores and set to performance... when i selected interactive the min value was 422... Am I doing something wrong? Everything stock and rooted 442
Edit. .. Ok I changed from interactivex to interactive and that fixed gov problem but all cores activated and min set to 422... Is that right?
Yes, minimum is 422 MHz because the l2 cache is bumped into action at that speed (as opposed to not being so at 300) and the voltage is the same.
In short, 300 is no5 used because 422 is faster, and without the extra hit on battery
Will this work with 4.4.4 w/o any issues? Been thinking on trying it on but I don't want it to mess anything and re-install stuff.
d-wad,
I cannot give you a definite answer there, as I have not yet looked at anything in 4.4.4.
If you can provide me a copy of the post_boot file for 4.4.4, I can take a look at it and see. I can't imagine why anything would have changed in this file, but you never know. All it takes is one line of code to cause something to go a little wonky for you.
Thanks, and just shoot me a PM.
Just giving you all a heads up.... I think there may have been a few errors in the stock init.qcom.post_boot file (they are human too, remember).
I am testing a few small changes to certain lines in the "factory" script to make sure. A brief explanation of it is that there are certain lines I removed from the one you all are using right now, and I did so because the file paths being called out did not exist!
However, I was going over this again tonight, getting ready for the official LP release and decided to review this odd discrepancy one more time. After doing some digging, I found that the file that some of those values were intended to be written to, were actually somewhere else!
Doh! - Sammy/QC. It is very possible that this location changed from a previous design or fs structure and somebody simply forgot to modify the script. Very interesting indeed.
Anyways, after I run this for a couple of days and do a little bit more investigating, I'll post the updated script for all of you.
Updated file and link... I recommend using this file or implementing these items into your current set up. Many of the changes are critical errors existing in the stock post_boot file, or simple optimization enhancements for our devices.
How to revert?
Sorry... TOTAL NOOB here...Do I just copy the orig file somewhere else, and drop this in place as you instruct? ( may have answered my own Q)
Seems a wise precaution.
I am running effortless rom rev 8 (lovin it too)
Disclaimer: I am not responsible for your broken phone , broken memory card, etc. All my kernels I test first on my own phones , and then upload here
If you like my works please do not forget donate to me(PayPal account you may find in my profile)
Very often people not read full description(then write me to email "device not start, help me" even in the middle of the night) therefore write here with giant words:
UNLOCKED BOOTLOADER REQUIRED OTHERWISE DEVICE CAN'T START WITH CUSTOM KERNEL (YOU GET USB LOGO PICTURE OR TO YOU THROW INTO RECOVERY OR BOOTLOADER)
I never add fake overclock and overclock, because for now(or forever) no method for real overclock and underclock
Random reboots for most users probably fixed in 16.04.2016 and higher
For max stability I recommend to use Interactive governor
Kernel features:
1) USB Mass Storage Support
2)
3) DT2W support (to activate it, you should install Zenmotion)
4) KVM support (Kernel Virtual machine for Intel)
5) Added support of init.d. scripts
6) Added support of exFAT file system for external sd card.
7) ZRAM is disabled for old versions, on version of December 6 and higher- ENABLED.
8) Added CD emulating feature
9) Added SWAP support(need create swap partition on sdcard)
10)
12) Add more governors and I/O schedulers
13) USB-HID mouse & keyboard function(required USB Keyboard app from GPhttps://play.google.com/store/apps/details?id=remote.hid.keyboard.client&hl=en)
14) Support joysticks (DragonRise, Inc ang others)
15) Add more TCP IPv4 congestion algorithms (May change via TricksterMod or Kernel Auditor apps)
16) Reduce min display backlight for autobrightness. For use min backlight level you should to use autobrightness and set it to the left
Deprecated features:
1. Overclock to 2000 Mhz (for A501CG only) and Overclock to 2400 Mhz (for A500CG only). Idea and work by @TheSSJ (it have been removed since 26.12.2015)
2. Based on Asus Zenfone 2 ZE551ML 2.20.40.44(more than 50%) + Asus Zenfone 6 3.24.40 sources
3. Underclock to 667 Mhz. Idea and work by @TheSSJ
4.Hotplug for all governors
5. Frandom Linux kernel generator
Note: This kernel will work on stock Lollipop firmware only like 3.24.40.87, 3.24.40.78 or 3.23.40.60 or 3.23.40.52
This kernel was created by BORETS24 So if you need more information you can pm to him.
How to flash this kernel:Method 1(via PC)Step 0:
Bootloader unlock is required for every custom rom. You can use this tool for unlock:
https://drive.google.com/file/d/0B-Fin8UxrD6PRU9MM1lQZkV0SG8/view
Step 1:
You should download files for flashing:
ADB v1.0.32: Download from Google Drive
Step2:
You should reboot your phone in the droidboot mode. (turn off you gadget then press Turn off button and volume + button)
Then go to the ADB folder and hold Shift + Right Mouse button and write this command:
Code:
fastboot flash boot new_bootXX.XX.img
,where XX.XX- numbers after words "new_boot"
Step3:
Reboot to Android.
Method 2(through CWM/TWRP, without PC)1. Download Flashable ZIP archive on phone
2. Go to recovery mode
3. Click Install ZIP and choose this archive
4. Then reboot
Archieves You make take from this post http://forum.xda-developers.com/showpost.php?p=64640638&postcount=364(Thanks to @Don No 1)
How to install Zenmotion:(it needed for DT2W)1) Download this file (asus.hardware.touchgesture.double_tap.xml) :
https://drive.google.com/file/d/0B-Fin8UxrD6PWWRBT1gwak16Tnc/view?usp=sharing
2) Put this file into system/etc/permissions
Set file permissions. It is a 0644 rw- r-- r--
3) Reboot the phone
4) Find Zenmotion in the Settings and activate it.
(It will work if you flash this kernel)
Changelog:
25.10.2016
I not remember that I removed, let's start that I changed and added
USB Mass Storage mode
Removed few unstable governors
I started to compile with use Zenfone 2 source code for Marshmallow
Existed governors from 6.0.1 source
Removed lz4- caused bugs, drain battery, very slow interface
Added bootboost feature into ramdisk such as Zenfone 2
Now drain battery less and interface speed is high
12.06.2016
Reduce min display backlight brightness to 5(no need to set to 2, no difference between 5 and 2- I checked).For use min backlight level you should to use autobrightness and set it to the left
ZRAM now turn on automatically only for 1 Gb RAM devices, for 2 Gb it disabled by default
Return to "1 core per modules" CPU mode
Return Interactive Pro and Intel governors
Remove InteractiveX and Hotplug governors(sometime caused problems)
Replace WI-FI from module into kernel
03.06.2016
Full NTFS support for SD card
NTFS OTG full support by sibling Asus File Manager(read/write), from others file managers you can to see OTG NTFS devices, may see OTG NTFS devices from file chooser but you can't edit data. But you can edit platform.xml via NextAPP SDfix and can write on NTFS OTG devices with any apps
14.05.2016
Full ExFAT SDcard support such as stock kernel(Now you can see ExFAT sdcard in file chooser, can modified data even without Next APP SDfix)
Remove UKSM and disable KSM
16.04.2016
Fixed: restore signal after long dissapear
Fixed: random reboots in phone calls
Standart processor mode "2 cpus per module"
Remove Intel, Lagfree governors and FIFO scheduler(caused reboots)
Compile with standart GCC 4.9, remove -O3 optimization(unuseless, placebo effect)
Add idle from Linux 4.6
17.03.2016
LZ4 kernel compress
LZ4 zram compress/decompress
Remove Hotplug(caused reboots, overheats) driver and return Hotplug governor
Speed-up interface
More less battery drain
Compile with SaberMod 4.9.3
Others optimizations
05.03.2016
Added again hotplug driver but modified, cores not jumping, not dancing, strongly CPU0+CPU1 always online
Approximately 90% sibling source 3.24.40
Hybrid ramdisk from 87+60 firmware
Some changes in dt2w code
Fixed CD emulation
14.02.2016
Based on Asus Zenfone 2 ZE551ML 2.20.40(more than 50%) + Asus Zenfone 6 3.24.40 sources, remove hotplug driver, return Hotplug governor
06.02.2016
Hotpluging for all governors via MSM hotplug driver(I set 2 cores always online by default, you may tuning this driver via Kernel Auditor, point CPU Hotplug), possible fix the impossibility of restoring the network signal after a long stay outside the network, remove Hotplug governor(is no longer needed)
31.01.2016
Add Hotplug governor and set it by default, without load on CPU 1,2 or 3 cores will go to offline https://www.youtube.com/watch?v=WBbCBahSgrM&feature=youtu.be
30.01.2016
Remove hotplugging from Interactive governor again, add InteractiveX V2 governor with adaptation for Quad core devices( 1 phisical core= 2 threads CPU go to offline, when screen off)
27.01.2016
Interactive governor from Asus ZenPad S 8.0 with adding hotplugging(2 threads=1 core go to offline, when screen off), underclock to 533 MHz, many code and drivers from source Asus Zenfone 2 ZE500CL, Ofast optimization
19.01.2016
Add and turn on Ultra kernel samepage merging(UKSM) technology a place of KSM, underclock to 450 MHz, may be fixed all random reboots besides during long phone calls, when dt2w is on(or fix? I don't know)
16.01.2016
Use new source code 3.24.40
Tweak Interactive governor: hispeed_freq and touchboost_freq down to 1333 Mhz
09.01.2016
May be, fix all random reboots
04.01.2016
Fixed freezes and reboots on third-party governors, when connection speed faster than 20 Mbit/s, return hotplugging to Interactive governor, return Intel and Yankactive governors, some bug fixes
02.01/2016
Compile without Ofast optimization, removed Hotplugging from Interactive governor, removed Yankactive governor, may be, this actions fix random reboots.
31.12.2015
Compile without Ofast optimization, processor works now in '1 core per modules' mode, now disable 3 core(3 threads), when screen off, on Interactive governors, try at random fix reboots on all version of devices
28.12.2015
Try to fix reboots on 1 Gb RAM modifications(return stock process drivers)
28.12.2015
a)Change toolchan from stock GCC to SaberMod 4.8.5
b) Add Hotpluging to Interactive governor, when screen off
c) Add F2FS support
d) Fix some warnings during compilations
25.12.2015
Attempt to fix screen freeze or reboots during long phone calls: change process.c driver on modifity driver from Zenfone 2. Read about it here https://github.com/kirananto/ZENFONE2/commit/044ad3da5263ba256a59b517e96a272b4e3f19f6, Fix almost all warnings in proximiry/lightsensor driver "ISO C90 forbids mixed declarations and code" during compiling, remove "fake" overclock
23.12.2015
Fix freeze and reboots of device, when chaging governors and/or schedulers, add more TCP IPv4 congestion algorithms and set Westwood by defauls in place of stock Cubic
Add some joysticks support, now may use device as keyboard and mouse for PC, move KVM from kernel to modules
15.12.2015
Underclock to 316 MHz, add Adaptive, Yankactive(with Hotplugging implementation by @TheSSJ] ) and conservativeX governors
12.12.2015
Add if.bin into kernel, to attempt fix screen freezing, push also if.bin to system/etc/firmware and reboot phone.
if.bin
11.12.2015
1. Add frandom Linux kernel generator
2. Add Bioshock, Lagfree, lionheart, Wheatley governors
3. Add BFQ, SIO, SIOplus, FIFO, FIOPS, VR I/O schedulers
06.12.15
Add ZRam support
10.11.15
1. Add SWAP support
2. Kernel build with Ofast optimization.
Now I will upload new versions on Yandex Disk
https://yadi.sk/d/tBN8eYlVr3mVZ
XDA:DevDB Information
Custom Lollipop kernel for Zenfone 5 & Zenfone 6 by BORETS24(Intel only), Kernel for all devices (see above for details)
Contributors
tank0412, BORETS24
Source Code: https://github.com/BORETS24/Kernel-fo-Zenfone-6-by-BORETS24
Kernel Special Features:
Version Information
Status: Stable
Current Beta Version: 1.0
Created 2015-11-02
Last Updated 2016-10-25
Bugs:
Some users reported that they have random reboots or screen freezes after call.
This issue have not solved yet.
Btw @tank0412 did u tried contacting borets if he can update this kernel for rr rom [emoji14]
Sent from my ASUS_T00J using Tapatalk
no_name said:
Btw @tank0412 did u tried contacting borets if he can update this kernel for rr rom [emoji14]
Click to expand...
Click to collapse
Yeah. I drop him a line on 4PDA. It looks like he stoped developing because he do not have device and he can not fix freezes after call + random reboots.
Actually in his kernel there's no freeze btw I think if he can release source then someone may work on it to make it compatible with rr rom ?
Sent from my ASUS_T00J using Tapatalk
no_name said:
Actually in his kernel there's no freeze btw I think if he can release source then someone may work on it to make it compatible with rr rom
Sent from my ASUS_T00J using Tapatalk
Click to expand...
Click to collapse
But he did this yesterday
https://github.com/BORETS24/Kernel-fo-Zenfone-6-by-BORETS24
Wow great ?
Sent from my ASUS_T00J using Tapatalk
What apps can i use to underclock overclock this kernel?
geepee410 said:
What apps can i use to underclock overclock this kernel?
Click to expand...
Click to collapse
Kernel auditor.
But this kernel has a default underclock/overclock. (400mhz/2000Mhz)
tank0412 said:
Bugs:
Some users reported that they have random reboots or screen freezes after call.
This issue have not solved yet.
Click to expand...
Click to collapse
Hi mate I am using this custom kernel and dt2w and its in ON state for three days now and I can confirm I don't have any freezes or reboots.... I had flashed internal data, system and cache before installing, and also had first installed. 44. Version KitKat..... During installing KitKat I relocked boot loader and flashed stock recovery. Then I installed. 54 version then lollipop. 60 and finally. 78 lollipop.. After this i unlocked bootloader and flashed twrp... Then flashed custom kernel and zen motion, no lags [emoji2]. Only my phone wakes everytime when I am on 2G data enabled and WiFi off..
Sent from my ASUS_T00F using Tapatalk
tank0412 said:
But he did this yesterday
https://github.com/BORETS24/Kernel-fo-Zenfone-6-by-BORETS24
Click to expand...
Click to collapse
U should share this to Quanqanh
kunalshah912 said:
Hi mate I am using this custom kernel and dt2w and its in ON state for three days now and I can confirm I don't have any freezes or reboots.... I had flashed internal data, system and cache before installing, and also had first installed. 44. Version KitKat..... During installing KitKat I relocked boot loader and flashed stock recovery. Then I installed. 54 version then lollipop. 60 and finally. 78 lollipop.. After this i unlocked bootloader and flashed twrp... Then flashed custom kernel and zen motion, no lags [emoji2]. Only my phone wakes everytime when I am on 2G data enabled and WiFi off..
Sent from my ASUS_T00F using Tapatalk
Click to expand...
Click to collapse
Hello there heheh i can see rr members here hahah
Yerp i am using it for 2 days, everything ok. Only screen freeze when temp high up to 42 degree.
Might be bootloader unlock. Later will try relock back and see wat will happen
Sent from my ASUS_T00J using XDA Forums
mshazrul82 said:
Hello there heheh i can see rr members here hahah
Yerp i am using it for 2 days, everything ok. Only screen freeze when temp high up to 42 degree.
Might be bootloader unlock. Later will try relock back and see wat will happen
Sent from my ASUS_T00J using XDA Forums
Click to expand...
Click to collapse
For relocking you need to install stock recovery
Sent from my ASUS_T00F using Tapatalk
@quanganh2627 if you interested in sources of borets kernel then you can see sources are released by him and one thing to tell you that in his kernel "no freeze after call" or any such type of bug,his kernel is supper smooth so maybe you can do something to make it work on our rr rom ?
Sent from my ASUS_T00J using Tapatalk
hey @tank0412 what new on update 2/11 ,sir ?
ChungVan said:
hey @tank0412 what new on update 2/11 ,sir ?
Click to expand...
Click to collapse
Nothing. i just created own topic for it on XDA.
Is this the same kernel that you post in the rr thread? @tank0412
myrul said:
Is this the same kernel that you post in the rr thread? @tank0412
Click to expand...
Click to collapse
Yeah, it is a same.
kunalshah912 said:
For relocking you need to install stock recovery
Sent from my ASUS_T00F using Tapatalk
Click to expand...
Click to collapse
R u using stock .78 with dt2w kernel, if yes then what type of settings r u using as my battery is draining very fast and r u also using power saver? Please reply.
Thanks
tank0412 said:
Bugs:
Some users reported that they have random reboots or screen freezes after call.
This issue have not solved yet.
Click to expand...
Click to collapse
with this kernel , no random reboots or screen freezes after call.
i think it have only one problem was limited 3 minutes when call . after 3 minutes , the call will auto end
Note: This kernel will work on stock firmware2.20.40.184, 2.20.40.183, 2.20.40.178, 2.20.174, 2.20.40.168, 2.20.40.165, 2.20.40.164 and may be lower, also working on some stock-based ROMs(EchoeROM V3,for example).
Disclaimer: I am not responsible for your broken phone , broken memory card, etc. All my kernels I test first on my own phones , and then upload here
If you like my works please do not forget donate to me(PayPal account you may find in my profile)
Bootloader unlock is required for every custom rom, custom kernel, custom recovery. Unlock Tool here:http://forum.xda-developers.com/zenfone2/general/tool-one-click-bootloader-unlock-root-t3155884
Changelog:
03.06.2016
Full NTFS support for SD card
NTFS OTG full support by sibling Asus File Manager(read/write), from others file managers you can to see OTG NTFS devices, may see OTG NTFS devices from file chooser but you can't edit data. But you can edit platform.xml via NextAPP SDfix and can write on NTFS OTG devices
14.05.2016
Migration to newest source code from Zenfone Zoom ZX551ML from 20 april 2016
Ramdisk from 183 firmware
Some optimization in code
17.04.2016
Full support exFAT SDcard format, now you may write/delete/rename by standart method of Android 5
16.04.2016
Great game performance
Remove Hotplug driver
Remove -Ofast optimization(loud words-not take effects, placebo)
Remove optimization flag -march=silvermont(loud words, did not work on 3.10 kernels)
Remove touchboost from Interactive governor
Modified Interactive, Interactive Pro, Intel, Cyan governors: CPU2 and CPU3 turn off when screen off
Idle from Linux kernel 4.6
Gpu governor simple_ondemand from Linux kernel 4.6
Based on source code from Zenfone Zoom ZX551 from march 17
zram and kernel compression is LZ4
04.03.2016
Rework MSM Hotplug, now only CPU0+CPU1 online, no dancing CPUs.
For humor and proof that overclock in others kernels is fake added "overclock" to 5GHz
28.02.2016
Re-work MSM Hotplug. Now if load more than 79 but lower than 99- only another 1 core go to online(CPU2 or CPU3)) and processor working on 3 cores online, if load more than 99- CPU3 and CPU2 go to online together and processor working on all 4 cores online DO NOT set fast lane 99 and higher!!!
Made 12 thermal states for video adapter a place of 3. If on 457 MHz have overheating- freq go to 400 MHz, if overheating on 400- go to 355, if hot on 355-go to 320 MHz and so on. In stock kernel if overheating on 457 MHz- processor goes in 200 MHz and was lags in games
25.02.2016
Compile with new march=silvermont optimizationmarch=silvermont(thanks to @Dan_Jacques )
Tuning MSM hotplug for Zenfone 2: now interface faster, smoother even when min cpus online = 2. And maybe drain battery less.
Unlocked almost all hidden GPU frequencies. Now available gpu frequencies 106, 133,160,177 MHz(I think this NOT fake underclock). I made Kernel Auditor version for our GPU PowerVR 6430 (see screnshots here http://i10.pixs.ru/storage/5/8/1/Bezimyanni_7545670_20843581.png ) https://drive.google.com/file/d/0BxVRXQGBg4DTaThjQUtoRFBrdms/view?usp=sharing
21.02.2016
Based on Asus Zenfone Zoom source code
Fixed hotplug driver and tuning(Now drain battery much less and fixed charging: now no overheating)
Added Cyan governor
Changed Interactive governor to Interactive from Asus Zenfone Zoom
18.02.2016
Now 2 different versions: for ZE551ML and for ZE550ML, Tuning MSM Hotplug(2 cores always online, Fast Lane up to 150), added Interactive Pro governor and set by default
04.02.2016
Interactive governor by default, realtime Hotplugging now on any governors, on Interactive too(Extra CPU cores disabled without load) Idea and work @mrg666 . You may to set parameters of hotplug driver via Kernel Auditor, point "CPU Hotplug"
Remove Hotplug governor(no longer needed)
Kernel Features:
1.Based on Zenfone Zoom ZX551ML source
2. Add zram support in LZ4 format(no need to turn on it, if no problem with multitasking and never no need to turn on for devices with 4GB RAM), kernel compression LZ4 too
3. Adaptation InteractiveX V2 governor for quad core devices, I make that 2 cores go to offline, when screen off
4. Processor work in "1 cpu per module" mode a place of "2 cores per module"(4 independent cpus, not pair)
5. Ofast and march=silvermont(thanks @Dan_Jacques optimization with GCC 4.9
6. Init.d support. You should install BusyBox in /xbin folder/
7. SELinux Permissive
8. KVM support (Kernel Virtual machine for Intel)
9. Added SWAP support
10. USB-HID mouse & keyboard functions(required USB Keyboard app from GPhttps://play.google.com/store/apps/details?id=remote.hid.keyboard.client&hl=en)
11. Ultra kernel samepage merging(UKSM) a place of KSM. Disabled by default, if you want you may turn on it via Kernel auditor
12. Full auto brightness. I removed minimal level 15, now level 5
13. More governovs and I/O schedulers
14.Zram disabled
15. More TCP algorithms, Westwood by default
16. Unlocked GPU frequencies 106, 133, 160, 177 MHz
17. NTFS support for SD card and OTG
Deprecated features:
1.Hotplug governor by default. Extra CPU cores disabled without load(it have been removed sinse 04/02/2016)
2. For correct work on ZE550ML you should change DPI to 320, for example via init.d script(root required).
1). Before flash kernel, you should install BusyBox in xbin folder, then create init.d folder in system/etc and set 755 permissions on it.
2) Download dpi320.zip, then extract dpi320 file and put it in system/etc/init.d folder, check that on it set 755 permissions
https://yadi.sk/d/6hg6bDDioCNbT
3). You may flash kernel.
3. Interactive governor from Asus ZenPad S 8.0 by default with some tuning(for example, hi_speed freq = 1583 MHz) and hotplugging additions( 2 cores go to offline, when screen off) Idea and work by @TheSSJ
4. Realtime hotplugging for all governors. You may to set parameters of hotplug driver via Kernel Auditor, point "CPU Hotplug"
5. Interactive governor from Asus Zenfone Zoom by default with some tuning(for example, hi_speed freq = 1750 MHz), InteractiveX and Interactive Pro have hispeed_freq 1750 MHz too.
Step 1:
You should download files for flashing:
ADB v1.0.32: Download from Google Drive
IMG file with kernel:
03.02.2016 https://yadi.sk/d/FuJhWqc9oCLZy
04.02.2016 https://yadi.sk/d/PcDiDaumoJMb7
All versions from 18.02.2016 and higher will be here: https://drive.google.com/folderview?id=0BxVRXQGBg4DTSVV5Q19mSVUxQk0&usp=sharing
Step2:
You should reboot your phone in the droidboot mode. (turn off you gadget then press Turn off button and volume + button)
Then go to the ADB folder and hold Shift + Right Mouse button and write this command:
Code:
fastboot flash boot bootXX.XX.img
,where XX.XX- numbers after word "boot"
Step3:
Reboot to Android.
Method 2( via TWRP, without PC)1. Download bootXX.XX.img
2. Go to recovery mode
3. Click Install, choose this bootXX.XX.img, choose boot partition and flash
4. Then reboot
Method 3(via Terminal Emulator, without PC)(root required)1. Download bootXX.XX.img and put it in root of internal memory
2. in command prompt write
Code:
su
dd if=/sdcard/bootXX.XX.img of=/dev/block/by-name/boot
reboot
And device started with custom boot.img
XDA:DevDB Information
Custom Lolipop Kernel for Asus Zenfone 2 ZE551ML/ZE550ML, Kernel for the Asus ZenFone 2
Contributors
BORETS24
Source Code: https://github.com/BORETS24/Kernel-for-Asus-Zenfone-2.git
Kernel Special Features:
Version Information
Status: Testing
Created 2016-02-02
Last Updated 2016-09-03
Nice work, especially the Hotplug features (maybe you should transfer your post under http://forum.xda-developers.com/zenfone2/development ?)
nazagan said:
maybe you should transfer your post under http://forum.xda-developers.com/zenfone2/development ?)
Click to expand...
Click to collapse
Maybe... How I can to do this?
Can you add flashable zip please? thank you.
serhangelgor said:
Can you add flashable zip please? thank you.
Click to expand...
Click to collapse
Why?
Method 2(through CWM/TWRP, without PC)
1. Download bootXX.XX.img
2. Go to recovery mode
3. Click Install, choose this bootXX.XX.img, choose boot partition
4. Then reboot
Or you can flash without PC and without custom revovery
Method 3(through Terminal Emulator, without PC)(root required)
1. Download bootXX.XX.img and put it in root of internal memory
2. in command prompt write
Code:
su
dd if=/sdcard/bootXX.XX.img of=/dev/block/by-name/boot
reboot
And device started with custom boot.img
BORETS24 said:
Why?
Method 2(through CWM/TWRP, without PC)
1. Download bootXX.XX.img
2. Go to recovery mode
3. Click Install, choose this bootXX.XX.img, choose boot partition
4. Then reboot
Or you can flash without PC and without custom revovery
Method 3(through Terminal Emulator, without PC)(root required)
1. Download bootXX.XX.img and put it in root of internal memory
2. in command prompt write
Code:
su
dd if=/sdcard/bootXX.XX.img of=/dev/block/by-name/boot
reboot
And device started with custom boot.img
Click to expand...
Click to collapse
hey bro, if you don't mind can I add up a few things for you?? it will reduce your work and since you are on kernel 3.10.20 you can try to use my direct jump patch to jump to kernel.org v3.10.94 here's the link https://github.com/Zenfone2-Dev/direct-kernel-patch
and nice work.
installed and opened only 1 core, its too good and battery life is amazing, thanks so much for this amazing work, can you add underclock feature? it will give more batterry life
serhangelgor said:
can you add underclock feature? it will give more batterry life
Click to expand...
Click to collapse
No, I don't want to add fake underclock. It give more interface freeze and nothing else besides placebo effect and boastfulness. I started to make kernel for zenfone 2 in july 2015 and using "underclock" some time- no different battery life between 500 and 250 MHz, I tried and 166 MHz and even 83 MHz- no effect besides slow and freeze interface.
say99 said:
hey bro, if you don't mind can I add up a few things for you?? it will reduce your work and since you are on kernel 3.10.20 you can try to use my direct jump patch to jump to kernel.org v3.10.94 here's the link https://github.com/Zenfone2-Dev/direct-kernel-patch
and nice work.
Click to expand...
Click to collapse
Thank you very much, may be apply this patch in future.
BORETS24 said:
Thank you very much, may be apply this patch in future.
Click to expand...
Click to collapse
made a pull request keep working and if you want you can switch to gcc 5.3.0 toolchain https://github.com/Zenfone2-Dev/x86_64-toolchain-GCC-5.3.0
BORETS24 said:
No, I don't want to add fake underclock. It give more interface freeze and nothing else besides placebo effect and boastfulness. I started to make kernel for zenfone 2 in july 2015 and using "underclock" some time- no different battery life between 500 and 250 MHz, I tried and 166 MHz and even 83 MHz- no effect besides slow and freeze interface.
Click to expand...
Click to collapse
BORETS24, can you add F2FS support? I feel the IO more smooth with it (in other phones there is a huge difference between ext4 and f2fs, like Moto G), but requires changes in kernel config file (easy) and a modified ramdisk with edited fstab (more complicated). There is an Project T version that includes a fstab with the needes changes [link=http://forum.xda-developers.com/zenfone2/development/project-t-custom-kernel-zenfone-2-t3150822/post64366155]here[/link] (but only boot with all /system /data / cache formatted in F2FS). With the correct lines, it's possible to make a mixed fstab, and supports both fs.
Changelog:
04.02.2016
Interactive governor by default, realtime Hotplugging now on any governors, on Interactive too(Extra CPU cores disabled without load), remove Hotplug governor(no longer needed)
BORETS24 said:
Changelog:
04.02.2016
Interactive governor by default, realtime Hotplugging now on any governors, on Interactive too(Extra CPU cores disabled without load), remove Hotplug governor(no longer needed)
Click to expand...
Click to collapse
hey bro, I can't find the commit for realtime hotplugging
Sent from my ASUS_Z00A using Tapatalk
Im using it, looks good, thanks
say99 said:
hey bro, I can't find the commit for realtime hotplugging
Sent from my ASUS_Z00A using Tapatalk
Click to expand...
Click to collapse
If will no critical bugs I will upload to Github, need time for test by users.
BORETS24 said:
If will no critical bugs I will upload to Github, need time for test by users.
Click to expand...
Click to collapse
just an advice : always upload up the commits and make two builds, test builds and stable builds, you can always revert the things you pushed to git
Sent from my ASUS_Z00A using Tapatalk
say99 said:
just an advice : always upload up the commits and make two builds, test builds and stable builds, you can always revert the things you pushed to git
Sent from my ASUS_Z00A using Tapatalk
Click to expand...
Click to collapse
I'm just recently start to use Github, for me easier delete changes from sources on PC Ubuntu than from github before changes,I keep stable source in zip archieves, old school And I can't to know which version of boot.img is stable which is not. Will make two unstable build? Alone I can't test everything, all hope on users. If you don't want to wait, I may to say that use Autosmp hotplug driver...
BORETS24 said:
I'm just recently start to use Github, for me easier delete changes from sources on PC Ubuntu than from github before changes,I keep stable source in zip archieves, old school And I can't to know which version of boot.img is stable which is not. Will make two unstable build? Alone I can't test everything, all hope on users. If you don't want to wait, I may to say that use Autosmp hotplug driver...
Click to expand...
Click to collapse
haha I can understand maybe that's y I added up the build script. A single command and you get a flashable zip without any need to manage them and that command is ./buildzf2
and yeah I have changed the defconfig in script and made a pull request so just get a hold on that
Sent from my ASUS_Z00A using Tapatalk
Add to description of kernel:
You may to set parameters of hotplug driver via Kernel Auditor, point "CPU Hotplug"
I really love your works. You made a big update for this cpu. Can you make a undervolt for this kernel, master ?
Hey Guys,
I thought while waiting for the first custom kernels that maybe i should have a look at the interactive values and try to tweak them based on this way:
http://forum.xda-developers.com/nexus-5x/general/guide-advanced-interactive-governor-t3269557
So i took a script from @Alcolawl and modified it to work with our device. Many thanks for his scripts.
I adjusted the values to our snapdragon 820 as the original scripts are for the nexus 6p which runs with a snapdragon 810. (octa on the 810 vs quad-core on the 820)
I´d highly recommend to try these values as it gave me a significant boost in battery life. here is a screenshot:
https://drive.google.com/file/d/0BxbxiBXaZVu-N1lsRTMyZ2hsY1k/view?usp=sharing
https://drive.google.com/file/d/0BxbxiBXaZVu-N1MzamRvM2FVZlk/view?usp=sharing
BIG UPDATE: with base 1.80 i´m not able to trick the touch/Input boost from htc´s pnpmgr with a chmod command like i did before. so all versions since Butterfly v11 will disable pnpmgr completely.
that means if you Play high end games and your device overheats like crazy please Report back. i had no Problem until now.
also there are now 2 versions. the oc one is for overclocked cpus with elementalx. without oc is for the default clock speeds.
here are explanations on what the 2 different stragies do:
Butterfly - A culmination of all strategies, provides smoothest performance of all currently published settings, though battery savings are a little more modest. Excellent for light and moderate users; heavy/marathon users might want to check out a different setting profile as it gets battery intense with heavy usage.
GhostPepper - Uses a quantized, frequency-aligned parametric curve to influence low core clock rates while providing extremely smooth transitions from each clock rate and exceptional battery life. Good for light to medium usage and multitasking.
So basically there will be two ways of applying this mod.
First one is via scripts. this allows to set parameters outside of the interactive governor controls like cpu boost, editing of pnpmgr, min/max frequencies etc. so basically there´s more control.
Second one is via EX Kernel Manager. I will upload the profiles and you can apply them directly into the app. This will however only affect the tunables of the interactive governor. Touchboost has to be set manually for the profile to work exactly as intended.
when the phrase "elex" is in the zips name it is for use with ex kernel manager app (loading profile in governor options screen.
so to try the script method follow these steps. (and before do a nandroid as always)
1. download the attched file.
2. unzip the file, choose the correct script (oc if you have overclocked)
3. with a root explorer or terminal copy the file to system/su.d
4. set the correct permissions (rwxr-xr-x)
now you may either choose to change the settings temporary (step 5A) until the next reboot or permanently upon each reboot (step 5B)
5A. rename the file to 50ghostpeppertenv3.sh
use any script manager and run the script from this location (system/su.d)
alternatively use any terminal emulator app with the following commands
su
cd system/su.d
sh 50ghostpeppertenv3.sh
Be advised that the script takes in its current state 60 seconds to be applied. So the changes need a minute to be applied.
now check if the script has applied
- to do this go to sys/devices/system/cpu/cpu0/cpufreq/interactive/target_loads
- if it looks like this: "25 480000:35 652800:45 844800:60 960000:75 1113600:85 1228800:90 1401600:95 1593600:100" the script was applied successfully
- the values changed with each update. what´s important to check is just the generel layout
5B. (-if you did the temporary approach beforehand remove the .sh)
- it should look like 50ghostpeppertenv3 (make sure there are now spaces at the end)
reboot and check if the script has applied
- to do this go to sys/devices/system/cpu/cpu0/cpufreq/interactive/target_loads
- if it looks like this : "25 480000:35 652800:45 844800:60 960000:75 1113600:85 1228800:90 1401600:95 1593600:100" the script was applied successfully.
-- the values changed with each update. what´s important to check is just the generel layout
Important!!!
if you run permissive and run into no signal issue due to this look here
if you should run into a no signal issue where your baseband shows as unknown under software status ( currently on custom roms eg leedroid) you have to put a script to system/su.d that sets selinux to permissive. attached is such a script.
unzip it. copy it to system/su.d
set the same permissions as the ghostpepper script and your good to go.
running in terminal the command "getenforce" should return permissive.
Second method via Elemental App:
1. Download the desired profile from the attachments
2.Extract the Profiles from the zip
3. Choose the Overclocked(oc) version if you overclocked
4.Copy the file to sdcard/ElementalX/gov_profiles
5. Open the app and apply the values
let me know if it brings a little battery boost for you. you may also let me know if you face performance issues.
Thank you and have fun testing it.
Changelog:
Ghostpepper:
v1: Initial Release
v2: Tweaking The Script so the values will get applied properly on all roms
adding a permissive script in case of getting enforced
v3: Removed touchboost so the profile may unleash its full potential <<--- results in overall slower device.
v4: Added back short input boost
v4withtb: Added back original touch boost from htc
v8: New try on getting the interface smooth and disabling touchboost (minimal stutter remains)
v8withtb: same as v8 touchboost is still active
v9: only one version with touchboost now. tweaked target loads (lower freqs are used more), short input boost
there are now two files inside the zip.
v10: try to further improve frequency usage, less aggressive scaling
v11: fix in case Little cores might get stuck at highest clock
Butterfly
v4: Initial Release
v4withtb: Initial Release with original touch boost from htc (extremely smooth)
v6withtb: tuned the values and kept touchboost from pnpmgr, kernel touch boost is disabled, extremely smooth for me
v7: less aggressive scaling, performance should be really good while reducing less power than v6
v9: basically scaling is tuned to respect the crossover effieciency point from big and little cluster
v11: updated to work on base 1.80
- disable pnpmgr completely because the chmod trick for disabling pnpmgr´s touchboost is no longer working
- enable msm_thermal and core_control
v12: tweak some values to work better with the new base
v13: hotfix as i made a mistake in the previous version
credits:
thanks to @Alcolawl for the script template
also thanks to @soniCron for the original thread
reserved
Thanks for this - about to try it out now.
Question, though - Instead of using init.d, which requires a modified ramdisk, why not just use su.d, which only requires SuperSU?
EDIT: It doesn't seem to be loading when using su.d either.
Thanks. I'm using it now. Will let you know if there are any performance problems.
Can you also make a script that makes the phone smoother?
Captain_Throwback said:
Thanks for this - about to try it out now.
Question, though - Instead of using init.d, which requires a modified ramdisk, why not just use su.d, which only requires SuperSU?
EDIT: It doesn't seem to be loading when using su.d either.
Click to expand...
Click to collapse
Yeah it's strange. When flar will Releases his kernel, init.d will be hopefully working.
Seems like we have to apply it manually for now. When exkm gets updated we can switch profiles there so maybe we should just find good values now.
gusoldier said:
Thanks. I'm using it now. Will let you know if there are any performance problems.
Can you also make a script that makes the phone smoother?
Click to expand...
Click to collapse
Did you face a performance loss with these values? For me it's already pretty smooth.
But sure I may trim it more performance oriented yes.
Freak07 said:
Did you face a performance loss with these values? For me it's already pretty smooth.
But sure I may trim it more performance oriented yes.
Click to expand...
Click to collapse
Compared to stock I feel no performance loss, as smooth as stock. What I actually meant was a new script for buttery smooth nexus like experience.
Btw I will also check how hot it will get. On stock the phone gets sometimes hot watching youtube etc. Hopefully it'll better with this script
gusoldier said:
Compared to stock I feel no performance loss, as smooth as stock. What I actually meant was a new script for buttery smooth nexus like experience.
Btw I will also check how hot it will get. On stock the phone gets sometimes hot watching youtube etc. Hopefully it'll better with this script
Click to expand...
Click to collapse
yeah. I can try this later. But compared to my nexus 6 and my pixel c the 10 is about as smooth.
Freak07 said:
Yeah it's strange. When flar will Releases his kernel, init.d will be hopefully working.
Seems like we have to apply it manually for now. When exkm gets updated we can switch profiles there so maybe we should just find good values now.
Click to expand...
Click to collapse
Got it working with su.d. Just needed to add some sleep at the beginning of the script, otherwise it runs too early and the parameters can't be set .
P.S. You didn't answer my question about why you're not using su.d instead of init.d?
Captain_Throwback said:
Got it working with su.d. Just needed to add some sleep at the beginning of the script, otherwise it runs too early and the parameters can't be set .
Click to expand...
Click to collapse
Can you post it? I will add it to op thank you captain!
Edit: didn't think about it I'm not that knowledgeable.
Or is it just like "sleep 30"?
Edit2: it is indeed. thank you again.
Freak07 said:
Can you post it? I will add it to op thank you captain!
Edit: didn't think about it I'm not that knowledgeable.
Click to expand...
Click to collapse
Sure, right now I'm just trying to find the minimum sleep value that works, and once I do, I'll post it.
RE: su.d, see the 2nd paragraph here: http://su.chainfire.eu/#selinux-policies-supolicy
An additional advantage besides the ones listed there is that in a systemless root setup, su.d doesn't require modifying system at all, which is important for being able to take OTA updates in the future. On this device, I try to touch system as little as possible (if at all), so it might be a better alternative, and doesn't require a custom ramdisk.
Captain_Throwback said:
Sure, right now I'm just trying to find the minimum sleep value that works, and once I do, I'll post it.
RE: su.d, see the 2nd paragraph here: http://su.chainfire.eu/#selinux-policies-supolicy
An additional advantage besides the ones listed there is that in a systemless root setup, su.d doesn't require modifying system at all, which is important for being able to take OTA updates in the future. On this device, I try to touch system as little as possible (if at all), so it might be a better alternative, and doesn't require a custom ramdisk.
Click to expand...
Click to collapse
yeah you´re right. thanks for the reference and the hint. i knew about it but didn´t remember i could use this see my edited last post. with sleep 30 it´s working for me. i updated the op.
besides, do you had any luck in finding your pvs bin? i´m extremely intersted in this. i only found my voltage table so far. maybe you may post yours too. i opened a thread here:
http://forum.xda-developers.com/htc-10/how-to/post-voltage-table-chip-t3383494
if we had a way to check our pvs bin it would be even more helpful.
Freak07 said:
yeah you�´re right. thanks for the reference and the hint. i knew about it but didn�´t remember i could use this see my edited last post. with sleep 30 it�´s working for me. i updated the op.
besides, do you had any luck in finding your pvs bin? i�´m extremely intersted in this. i only found my voltage table so far. maybe you may post yours too. i opened a thread here:
http://forum.xda-developers.com/htc-10/how-to/post-voltage-table-chip-t3383494
if we had a way to check our pvs bin it would be even more helpful.
Click to expand...
Click to collapse
sleep 30 didn't work for me, as I have another script running before this one. It's probably safer to go with sleep 60 to make sure it loads for everyone (sleep 45 did work for me too, but 30 was too short - figured it's better to allow more time). Just a suggestion, or you could just tell people that if it doesn't load for them to increase the sleep value. Up to you, really.
EDIT: And I don't know anything about a pvs bin
Captain_Throwback said:
sleep 30 didn't work for me, as I have another script running before this one. It's probably safer to go with sleep 60 to make sure it loads for everyone (sleep 45 did work for me too, but 30 was too short - figured it's better to allow more time). Just a suggestion, or you could just tell people that if it doesn't load for them to increase the sleep value. Up to you, really.
EDIT: And I don't know anything about a pvs bin
Click to expand...
Click to collapse
Okay i'll edit it to 60.
This is what I'm talking about. Every Chip has a pvs bin. The higher the bin the lower the voltage for a certain cpu frequency.
And every bin has its own voltage table.
http://forum.xda-developers.com/htc-one-m8/general/guide-snapdragon-801-clocking-voltage-t2807173
Hey @Freak07,
Wondering if you can help.. Can't seem to get this working?? Please see attachment. I've set permissions and used terminal to get it working but no dice?
Edit: Nevermind.... I can't follow simple instructions to unzip a file (I was renaming the zip rather than unzipping and renaming that to .sh).... #Special
Edit 2: Went straight for option 5b (so it should have worked on reboot). When I rebooted I lost the radio and have had to clean flash my ROM? I was on Leedroid's Rom when it happened.
rav101 said:
Hey @Freak07,
Wondering if you can help.. Can't seem to get this working?? Please see attachment. I've set permissions and used terminal to get it working but no dice?
Edit: Nevermind.... I can't follow simple instructions to unzip a file (I was renaming the zip rather than unzipping and renaming that to .sh).... #Special
Edit 2: Went straight for option 5b (so it should have worked on reboot). When I rebooted I lost the radio and have had to clean flash my ROM? I was on Leedroid's Rom when it happened.
Click to expand...
Click to collapse
Which Kernel were you on?
This morning i had the same issue when flashing tbalden Kernel using leedroid and my Script.
Freak07 said:
Which Kernel were you on?
This morning i had the same issue when flashing tbalden Kernel using leedroid and my Script.
Click to expand...
Click to collapse
Hey buddy,
I was on the kernel built into Leedroid.
Hope that helps.
rav101 said:
Hey buddy,
I was on the kernel built into Leedroid.
Hope that helps.
Click to expand...
Click to collapse
How did you recover? Full Wipe?
Delete
Freak07 said:
How did you recover? Full Wipe?
Click to expand...
Click to collapse
Yeah, I tried a dirty wipe but that didn't work so had to do a full wipe.