HWMOD OC KERNEL FOR MEDIAPAD ICS
Here is my 3.0.42 Overclocked Kernel for Mediapad ICS.
It was developed to suit my modified C232B005 firmware.
Should work in combination with all released Huawei ICS firmwares.
The main objective was to have longer battery life, not sure I got 100% of it,
however it seems pretty stable. The choice about avoiding higher clock frequencies
was deliberate and aimed to avoid forced close, freezes and unexpected reboots.
Really higher frequencies seemed unstable to me during my tests.
CHANGES
- latest stable kernel-3.0.42 Overclocked, clock up to 1.782 MHz
- undervolting from 750 mV @ 192Mhz to 1.275 mV @ 1.782 MHz
- default clock 1.188 MHz as in stock but governor ondemand
- "arkusuma" touch screen driver and sysfs modifications
- mt9m114 driver embedded in the kernel (not a module)
- size optimized dhd kernel module for Wifi networking
- added SIO scheduler but kept "deadline" as default
- cleaned up errors due to non existing hardware
- removed several unused driver from the kernel
- various fixes and tweaks from other platforms
HOW TO INSTALL
- extract the "boot.img" file from the "boot-3.0.42-hwmod.zip" archive
- using "fastboot" erase and then write "boot.img" to the boot partition:
Code:
fastboot erase boot
fastboot flash boot boot.img
- extract the "modules" folder from the "modules-3.0.42-hwmod.zip" archive
- copy the complete content of the "modules" folder to "/system/lib/modules/"
BOOT PARTITION (updated 2012/09/10)
Size: 3.999.362 bytes - MD5: aa7e4676d85f45a354c29aaadbdb8eab
Contains "boot.img" file to be flashed with "fastboot" to the "boot" partition:
http://www.gamefront.com/files/22241072/boot-3.0.42-hwmod.zip
KERNEL MODULES (updated 2012/09/10)
Size: 272.341 bytes - MD5: 6406f7778a4054160f2d415673cde0ca
Contains 3.0.42 kernel modules to be copied in "/system/lib/modules":
http://www.gamefront.com/files/22241073/modules-3.0.42-hwmod.zip
As always have fun and enjoy,
.:HWMOD:.
LOCAL DOWNLOAD FROM XDA
.
Nice one but i have problem with wifi. Very very slov
Sent from my HUAWEI MediaPad using XDA Premium HD app
CSCicus said:
Nice one but i have problem with wifi. Very very slov
Sent from my HUAWEI MediaPad using XDA Premium HD app
Click to expand...
Click to collapse
The "dhd.ko" module is the original one shipped by Huawei.
It was just stripped off of symbols and other debug informations
which are not necessary for the functionality of the Wifi driver.
I have had no sign of Wifi slow down and other people on Androidiani forum
are using this same kernel and they have not reported problems so far:
http://www.androidiani.com/forum/hu...rmware-mediapad-ics-4-0-3-hwmod-c232b005.html
You could try to perform a complete "Factory data reset" if you are not
worried about reinstalling your application and data from a backup.
any other governor added to above kernel ?
I have my device 3days. I have instaled yours rom. Everything its wiped. I noticed i dont have this problem all time. On first instalation of all things was ok. But after that speed gos down to 100k/200k i disable wifi . After 2h i try it again and it was again ok.Maybe its some problem with my mikrotik router. But i have lot of wifi devices and i dont have this problems. For now its working. Thanks
Sent from my HUAWEI MediaPad using XDA Premium HD app
kakabobo said:
any other governor added to above kernel ?
Click to expand...
Click to collapse
No, I thought the standard 5 governors were enough for normal usage.
Personally I only use "ondemand" and "performance".
Which one are you missing ?
hwmod said:
No, I thought the standard 5 governors were enough for normal usage.
Personally I only use "ondemand" and "performance".
Which one are you missing ?
Click to expand...
Click to collapse
Is Ondemand have screen off profile? Iirc, the standard Ondemand governor don't have it. I don't know how much screen off profile would save battery, but I believe it's a nice thing to have.
rurou said:
Is Ondemand have screen off profile? Iirc, the standard Ondemand governor don't have it. I don't know how much screen off profile would save battery, but I believe it's a nice thing to have.
Click to expand...
Click to collapse
Hmm ... not enough knowledge about those governors details, sorry !
My objective was an usable and stable kernel with a few improvements.
As you can see there is no edge OC either and voltage has been kept to a minimum even at the cost of performances.
I haven't boosted L2 too much either, bus BW remains at max. 310Mhz.
I kept focussed on the stability of the device without changing to many things at once.
Maybe related to your question I know that "Deep Sleep" mode works while the governor is "ondemand".
So it enters this extra power saving mode every time the screen switches off for a couple of seconds.
You can check it works by downloading CPUSpy (free from the market).
Obviously it can't enter "Deep Sleep" while connected through "adb".
Hi hwmod
Is this an update to the Kernal 3.0.42 that you posted on your main thread or is it a new
one. The reason I ask is that I have the Kernal from that thread installed and have problems with
using fastboot. You previous was much easier to install.
Stransky
Sent from my HUAWEI MediaPad using xda premium
Stransky said:
Hi hwmod
Is this an update to the Kernal 3.0.42 that you posted on your main thread or is it a new
one. The reason I ask is that I have the Kernal from that thread installed and have problems with
using fastboot. You previous was much easier to install.
Stransky
Sent from my HUAWEI MediaPad using xda premium
Click to expand...
Click to collapse
No it is not an update, it is exactly the same 3.0.42 kernel and modules used in the other thread.
I extracted kernel and modules from that since there could be users wanting to try the kernel
but not wanting to install the complete package in post #2 of my modded firmware thread.
If you already installed the complete C232B005 HWMODed firmware you are fine.
Does anyone face some problems after flashing this?
hamdimo said:
Does anyone face some problems after flashing this?
Click to expand...
Click to collapse
It's running fine for me and seems a few others too.
Any more info or description about the problem you are facing ?
Hi
No problems here.
Stransky
Sent from my HUAWEI MediaPad using xda premium
A bug has been found in the kernel.
The internal microphone is not working.
External mic (from headset) works fine however.
hwmod said:
A bug has been found in the kernel.
The internal microphone is not working.
External mic (from headset) works fine however.
Click to expand...
Click to collapse
Is the bug there in the full firmware tooo? 'Cos I'm planning to flash tomorrow and don't wanna use my headset all the time for Skype.
Sent from my HUAWEI MediaPad using XDA Premium HD app
shiranmotha said:
Is the bug there in the full firmware tooo? 'Cos I'm planning to flash tomorrow and don't wanna use my headset all the time for Skype.
Sent from my HUAWEI MediaPad using XDA Premium HD app
Click to expand...
Click to collapse
No the bug is related to the kernel only.
I am looking into this to find a definitive solution.
It looks like I left out some configuration bit that is needed.
I uploaded a new kernel-3.0.42 and related modules in the OP.
This fixes the bug with the integrated microphone not working.
Thank you for your patience.
Have fun,
.:HWMOD:.
Del
Can someone tell if he noticed longer battery use? How much on WIFI, 3G, movies?
Related
Hiya everyone,
I've ported Dumfuq's overclocking patches from 2.6.29 to 2.6.32.21! This applies to those of us using the stock HTC OTA and allows the use of programs like SetCPU. This kernel was built from the source code from http://developer.htc.com and the kernel config is an identical copy of the one included in the latest Froyo OTA (my leak).
My current method of providing this is as an update.zip... just put this on your SDcard, boot into Clockwork, and flash it. If it kills your kittens, do not blame me.
Also, reminder: flashing this zip alone is not enough to overclock your device. Afterward, use a program (from the Market) such as SetCPU to overclock your device.
Download: http://www.multiupload.com/2XEWYRL62U
Change Log:
- Revision 2
Fix Wifi issues (as well as any other kernel module loading issues).
Add support for CPUfreq governers 'interactive' and 'smartass'.
Change the default governer from 'ondemand' to 'interactive' - this dramatically improves redraw performance and other user-interface responsiveness.
To change to the Smartass governer use something like SetCPU.
Include the MSM KGSL TLB performance tweak changes that are present in CM's kernel repository. You may or may not notice any video performance improvement, but it provides a possibility of improvement.
Fixed the kernel version string to properly read '2.6.32.21' not '2.6.32.17' - the first version wasn't .17, it was .21.
Please remember to disable the HTC Perflock in SetCPU by pressing the Menu key (while in SetCPU) and selecting 'Perflock Disabler'.
Happy? Donate.
Hey I'm running your NB 2.15 Mod ROM and just flashed this kernel. It broke the WiFi. I am now getting an Error when attempting to enable WiFi.
What is the max frequency of this kernel? And does it include smartass governer?
Sent from my T-Mobile myTouch 3G Slide using Tapatalk
pettigrew95 said:
Hey I'm running your NB 2.15 Mod ROM and just flashed this kernel. It broke the WiFi. I am now getting an Error when attempting to enable WiFi.
Click to expand...
Click to collapse
Ahh, one thing I didn't test, although I suspected it might break. I'll fix it tonight and post a new update.zip for ya'll.
agentg1001 said:
What is the max frequency of this kernel? And does it include smartass governer?
Click to expand...
Click to collapse
It's identical to Dumfuq's patches, so 864000Hz. And no, it doesn't include the smartass governer - I will investigate that possibility tonight, however I suspect I will be able to implement it. Additionally I will be disabling HTC Perflock in the kernel so it doesn't have to be done by SetCPU.
Toodles.
EDIT: I'll also be adding the new 'interactive' CPUfreq governer.
nbetcher said:
Ahh, one thing I didn't test, although I suspected it might break. I'll fix it tonight and post a new update.zip for ya'll.
It's identical to Dumfuq's patches, so 864000Hz. And no, it doesn't include the smartass governer - I will investigate that possibility tonight, however I suspect I will be able to implement it. Additionally I will be disabling HTC Perflock in the kernel so it doesn't have to be done by SetCPU.
Toodles.
EDIT: I'll also be adding the new 'interactive' CPUfreq governer.
Click to expand...
Click to collapse
I have made the changes, however I decided to NOT disable HTC Perflock through the kernel config, so please make sure to disable it (via SetCPU) first before trying to overclock or change your governer. New version uploaded, see OP.
Could you also include some higher frequencies? (Preferibly up to 960)? That would be great because my phone is stable up to 921. Also compcache enabled (like drowning child's kernel) would be awesome.
Sent from my T-Mobile myTouch 3G Slide using Tapatalk
I'm not sure why but my slide didn't like this kernel
http://pastebin.com/hVgG467j
Thank the devs for nandroid!
My slide not working with this kernel too (
Are you both running NB_Mod-2.15.531.1 Revision 2? Otherwise this won't work properly. Besides, according to that logcat your problems aren't related to the kernel... Android is unable to mount any of the MTD partitions (/system, /cache, /data, etc).
Please let me know more about what you're running.
Also, I'll be working on making a separate version of this that has OC enabled up to 960MHz, but 960MHz is very dangerous... 800MHz+ is even asking for trouble despite our processor's normal clockrate being 800MHz (T-Mobile downclocked it to 600MHz out-of-the-box).
I'll look into Compcache as well.
im IN.
good job, will try after work. gj
how long does it take to boot the first time?
been stuck at the white MT3GS boot screen for a few minutes now.
running CM7 RC4
EDIT: oops, did not know this is only for the leaked froyo update
pettigrew95 said:
Hey I'm running your NB 2.15 Mod ROM and just flashed this kernel. It broke the WiFi. I am now getting an Error when attempting to enable WiFi.
Click to expand...
Click to collapse
I just flash the this new Kernel and i'm also getting Error on the WiFi when trying to Enable it, also the SetCPU won't go higher then 600. The Rom i'm using is the 3rdSense 1.00
Thankfully i did a Rom Backup so i'm restoring my system
Sefy said:
I just flash the this new Kernel and i'm also getting Error on the WiFi when trying to Enable it, also the SetCPU won't go higher then 600. The Rom i'm using is the 3rdSense 1.00
Thankfully i did a Rom Backup so i'm restoring my system
Click to expand...
Click to collapse
This kernel is only to be flashed if youre running NB Mod 2.15 ROM. It wont work on 3rd sense
pettigrew95 said:
This kernel is only to be flashed if youre running NB Mod 2.15 ROM. It wont work on 3rd sense
Click to expand...
Click to collapse
Well, it showed it as the kernel in the "About" so it appeared to have flashed it (and it did kill the WiFi) so it did get flashed
Either way, i got back to the previous one (.17[aka .21]) and it's working fine again.
Sefy said:
Well, it showed it as the kernel in the "About" so it appeared to have flashed it (and it did kill the WiFi) so it did get flashed
Either way, i got back to the previous one (.17[aka .21]) and it's working fine again.
Click to expand...
Click to collapse
Hmm, .17 isn't AKA .21. They're two different kernels and contain different code. The kernel you're using in 3rdSense was from the HTC Legend release of 2.6.32.17 and had different Wifi drivers. When a kernel and its driver modules are built, the build process puts the kernel's version string into the modules, so if you try to load them on a different kernel it will fail. This is what happened to you... you have 3rdSense which uses 2.6.32.17 Wifi drivers and my 2.6.32.21 kernel cannot (well, I fib a little on that) load the .17 drivers. Get it? Got it? Good.
nbetcher said:
Hmm, .17 isn't AKA .21. They're two different kernels and contain different code. The kernel you're using in 3rdSense was from the HTC Legend release of 2.6.32.17 and had different Wifi drivers. When a kernel and its driver modules are built, the build process puts the kernel's version string into the modules, so if you try to load them on a different kernel it will fail. This is what happened to you... you have 3rdSense which uses 2.6.32.17 Wifi drivers and my 2.6.32.21 kernel cannot (well, I fib a little on that) load the .17 drivers. Get it? Got it? Good.
Click to expand...
Click to collapse
So... what you are saying is, a kernel from a different device all together, is working on a hardware which it doesn't really belong to. While a Kernel made specifically for this, will kill the WiFi of the device it's designed for?
From what i recall from Linux, and i could be wrong and this doesn't apply to Android, the Kernel and the UI are two separate components. The Kernel has all the drivers and the UI is the interface! but again, i could be wrong.
Sefy said:
So... what you are saying is, a kernel from a different device all together, is working on a hardware which it doesn't really belong to. While a Kernel made specifically for this, will kill the WiFi of the device it's designed for?
From what i recall from Linux, and i could be wrong and this doesn't apply to Android, the Kernel and the UI are two separate components. The Kernel has all the drivers and the UI is the interface! but again, i could be wrong.
Click to expand...
Click to collapse
What I'm saying is that the boot.img that I have in the update.zip from this post does NOT contain the modules for Wifi since the modules are stored on your /system MTD and the scope of this update.zip is for the kernel. Could I replace the modules from there with the ones shipped with the Froyo OTA? Sure, but where does it stop?
Anyways, the Legend is not a completely different device. The Legend is basically the UK version of the Slide, minus the keyboard. Same exact hardware all the way down to the Wifi and BT.
Let me explain things a little bit more:
There's sdio.ko and tiwlan_drv.ko in /system/lib/modules. NB_Mod has ones compiled from 2.6.32.21, 3rdSense has ones compiled from 2.6.32.17. This thread's kernel (boot.img, to dumb it down a bit ) is 2.6.32.21. So, when the system goes to load the modules from /system/lib/modules, it sees that you're running kernel 2.6.32.21, but the modules in that directory are for 2.6.32.17. It fails.
As far as Android being separate from the kernel... yes, of course. But touching "Wifi" (to enable Wifi) in Settings doesn't scurry out little Android gremlins to magically carry the firmware from your MTD to the Wifi chipset... all it does it say "Hey, kernel, would you mind loading the wifi module you have listed in init.rc? Thanks Linus! *kisses*" Then Android does some other stuff, but I won't bore you with the entire process or else I'll have to write a book (oops, too late).
EDIT: in hind-sight this all seems to not really answer your question and only further supports the need for a better answer to you, but hopefully you'll find some clarity.
nbetcher said:
What I'm saying is that the boot.img that I have in the update.zip from this post does NOT contain the modules for Wifi since the modules are stored on your /system MTD and the scope of this update.zip is for the kernel. Could I replace the modules from there with the ones shipped with the Froyo OTA? Sure, but where does it stop?
Anyways, the Legend is not a completely different device. The Legend is basically the UK version of the Slide, minus the keyboard. Same exact hardware all the way down to the Wifi and BT.
Let me explain things a little bit more:
There's sdio.ko and tiwlan_drv.ko in /system/lib/modules. NB_Mod has ones compiled from 2.6.32.21, 3rdSense has ones compiled from 2.6.32.17. This thread's kernel (boot.img, to dumb it down a bit ) is 2.6.32.21. So, when the system goes to load the modules from /system/lib/modules, it sees that you're running kernel 2.6.32.21, but the modules in that directory are for 2.6.32.17. It fails.
As far as Android being separate from the kernel... yes, of course. But touching "Wifi" (to enable Wifi) in Settings doesn't scurry out little Android gremlins to magically carry the firmware from your MTD to the Wifi chipset... all it does it say "Hey, kernel, would you mind loading the wifi module you have listed in init.rc? Thanks Linus! *kisses*" Then Android does some other stuff, but I won't bore you with the entire process or else I'll have to write a book (oops, too late).
Click to expand...
Click to collapse
Everyday you learn something new! thanks for being the teacher!
nbetcher said:
Are you both running NB_Mod-2.15.531.1 Revision 2? Otherwise this won't work properly.
Click to expand...
Click to collapse
Well now I feel a bit sheepish, I guess that's what I get for not reading closely enough, I'm running CM7 RC4, sorry about that.
Does anyone happen to have a copy of this kernel laying around somewhere? Megaupload is long gone unfortunately
This Thread is intended to answer some common questions asked by users of TEMASEK's CM10.1 - Unofficial ROM. I am not an expert user, I just did this to help out some people who are having some difficulties. I have been using this ROM for a long time now and I compiled most commonly asked questions. I tried to answer these questions from my knowledge and from other people's responses so these might not work for you. In fact to keep myself safe from any accusations I copied the disclaimer from Temasek's thread. If anyone wants to add some more question and answers feel free to suggest.
/*
* Your warranty is now void.
*
* I am 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 in this ROM
* 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. Hard. A lot.
*/
Frequently asked questions
Is this ROM the same like CM10.1?
Yes and No. Mainly this ROM does look similar to CM 10.1 because they have a common source. Using Temasek's own words "I sync from cm source and merge with my source, add some open commits (cherrypicks) and some external sources. Then I compile from the source I have to build this cm10.1 unofficial build"
What are cherry picks?
Cherry picks are modifications or software which Temasek adds to his ROM. An example of Cherry pick is the centre clock and the exit button on the stock browser
Does this ROM come with a kernel?
Yes this ROM comes with stock CM kernel. However you can opt to choose another one of your liking. Temasek has his own kernel as well which you can download from the website mentioned in his OP. Remember that you need to reflash the kernel (if you are not using the CM stock kernel) every time you flash an update
Is Siyah Kernel compatible with this ROM?
Unfortunately Gokhan is not updating the Kernel as fast as CM10.1 is updating itself. Therefore this might lead to some problems especially if you are using V60 onwards. That is CM10.1 has to be the one before 20130223
What happens if i have cm10.1 as second boot? Will it boot if I am using Siyah Kernel?
In this case you will be able to boot in your first rom but not in Temasek's CM 10.1
Where can I download the ROM / Temasek’s Kernel / Gapps?
You can download all of the above from this location: http://temasek.hopto.org/
If you want the ROM, click on Samsung Galaxy S3 – i9300, then CM 10.1 and you will find the ROM there.
For Kernel click on Samsung Galaxy S3 – i9300, then CM 10.1, then Temasek Kernel
For GAPPS, click on Samsung Galaxy S3 – i9300, then CM 10.1 and then MISC and press GAPPS JB
What is the difference between GAPPS-JB-20121212 and GAPPS-JB-20121212-FIXED?
In Temasek’s case GAPPS-JB-20121212 unrooted his mobile phone. Therefore he fixed GAPPS, hence there is GAPPS-JB-20121212-FIXED
Can I install the new GAPPS-JB-20130301?
Yes it suggested that you update GAPPS to this version. However be sure that you are running on Android 4.2.2, i.e. Temasek's CM10.1 unofficial or any other AOSP/AOKP ROM using android 4.2.2
Do I need to wipe data?
If you are coming from another ROM you have to do a clean install. If you are coming from previous versions of this ROM you can do without a wipe data. However if you have issues with the ROM it is recommended to wipe data, and format system.
Can I install this ROM over the official cm10.1?
Yes you can install this ROM over the official Cm10.1, and you can do a dirty install i.e. Install without wiping data and formatting system.
What is the process to update this ROM?
Process is pretty easy and straightforward. Follow these steps and you should not have any difficulties
Step 1:
Download the ROM
Step 2:
Put the ROM into your SD Card
Step 3:
Reboot into custom recovery
Step 4:
Install the Downloaded ROM
If you wish to use Stock CM kernel follow step 5, if you want to install another Kernel follow step 6
Step 5:
Reboot System
Step 6:
Install Custom Kernel
Step 7:
Reboot
What are the steps for a new installation?
First I am assuming that your device is rooted and a custom recovery is installed. If you already did these you can do the following:
Step 1:
Download the ROM, GAPPS & (optional) custom kernel (if you do not want Stock CM Kernel)
Step 2:
Put the ROM, GAPPS and Kernel (optional) into your SD Card
Step 3:
Reboot into custom recovery
Step 4:
Install the Downloaded ROM
Step 5:
Install GAPPS
Step 6 (optional – if you want CM kernel you can go to step 7):
Install Kernel
Step 7:
Reboot System
Can I use Titanium Backup?
TB can be used as long as you do not restore system apps. It is suggested that you do not restore user applications if you are coming from Android Jelly Bean 4.1.1 / 4.1.2. What you can do is first install the applications from the Market and then restore the DATA (only) of these applications
Installed this ROM and I cannot find developer options!
Developer options are hidden and you can enable this option by pressing BUILD NUMBER under the About Phone menu
I lost the 3 options of Reboot?
You can re-enable this feature in developer options
Installed Temasek's kernel but I can see no difference in the sound?
For the time being Temasek's kernel alone is not going to make a difference until you install Boeffla Sound Control App which can be found in the playstore: https://play.google.com/store/apps/details?id=com.near.boefflasound
What is the difference between STock cm10.1 kernel and Temasek's Kernel?
Temasek's kernel has additional features compared to Stock CM 10.1. These include:
- Andreilux's Charging Control Mechanism
- Ability to CPU OC and CPU UC
- Ability to tweak Audio (Using Boeffla Engine)
- Ability to tweak CPU voltage
- Ability to change voltage usage of the internal memory
- Ability to change I/O scheduler for internal memory and sd card
- Ability to change charging power
- Ability to change screen preferences such as: Digital Noise, Chroma Saturation and others
How can I change the charging voltage?
There are two ways how you can do this.
Option 1:
You can use the application developed by FastJack2: http://www.mediafire.com/FastJack2 in folder public/ChargeControl
Option 2:
If you are running temasek's kernel (date 5th March onwards), you can easily install Stweaks (Play store link: https://play.google.com/store/apps/details?id=com.gokhanmoral.stweaks.app) and then edit the charging settings under the Power Tab.
I did not understand the charging voltage options?
This part is taken from the OP of the Temasek's CM10.1 thread:
Directory
/sys/devices/platform/samsung-battery/
Charging Currents
Charging currents are dictated by input and charging current limits. The input current is the current flowing into the device through the USB port at 5V. The charging current is the current delivered to the battery at usually 4.35V. The device can have a higher charging current than input current because of the voltage differential, usually a 15% discrepancy. You can also have much higher input currents than charging currents, this can be useful when you are using the device in situations like gaming and charging your battery at the same time, provided your charger actually can provide the power.
There are 3 USB charger type categories
Dedicated Charging Ports (DCP)
- includes AC chargers, but also special USB plugs
dcp_ac_chrg_curr
- default 1000
- max 1200 (specification max is 1500)
- min 500
dcp_ac_input_curr
- default 1000
- max 1200 (specification max is 1500)
- min 500
Standard Downstream Ports (SDP)
- usually includes almost all data enabled USB ports
sdp_chrg_curr
- default 475
- max 900
- min 475
sdp_input_curr
- default 475
- max 900
- min 475
Charging Downstream Ports (CDP)
- includes also data enabled USB ports but which are designed to provide more power, usually on newer laptops where the USB port has a lightning logo next to it
cdp_chrg_curr
- default 1000
- max 1200 (specification max is 1500)
- min 500
cdp_input_curr
- default 1000
- max 1200 (specification max is 1500)
- min 500
Voltage control
- Hard voltage control: 4.20, 4.35V, and 4.40V charging voltages are available. This is included for anybody running on third-party batteries, whom most of them have a 3.7V battery chemistry as opposed to the 3.8V on the stock battery. These batteries should be charged at 4.2V instead of 4.35V.
batt_chrg_hard_volt
- default 4300000
- alternative value 4200000
- user can choose only either 4200000 or 4300000
- Soft voltage control: As opposed to the hard voltage control which is the voltage which the charger chip provides to the battery while charging, the soft-voltage is the battery voltage itself. 3.7V batteries have a top-off voltage of 4.2V and 3.8V again 4.35V. The default limit on the stock battery is 4.30V before the charger logic stops and considers the battery as full. This is also merely provided for 3rd party batteries which should be charged at lower voltages. If you overcharge your battery beyond these what are safe considered voltages, such as raising the default 4.30 top-off voltage to the design 4.35V or even higher, you are running into the risk of damaging the battery or even causing it to melt-down.
batt_chrg_soft_volt
- default 4300000
- alternative value 4200000
- user can choose only either 4200000 or 4300000
Can I OC(over clock) and UC (Under clock) temasek's kernel?
If you have installed temasek's kernel (date 5th March onwards) you can alter the speed and voltage of the CPU. This can be done using stweaks which can be found from playstore.
I cannot OC GPU!
For the time being it is not possible to OC the GPU (if you are using temasek's kernel), but it might be possible in the future.
My battery stops charging at 89%!
DO not worry, this can be fixed through stweaks settings.
- Download Stweaks from google play if you have not downloaded it
- Open stweaks
- Go on Power Tab
- Scroll to the bottom of the page until you find the section "Battery Charging Voltages"
- Press "Charge Hard Voltage"
- Change from 4.2V to 4.3V
- Press Apply
I Under voltaged my GS3 and now it went into a boot loop!
- Go into recovery (Hold Power Button, Volume Up and Home Button)
- Install ROM and Kernel again
- ROM should boot fine
- Next time do not select "Set on Boot" from Stweaks before you are sure that your settings are working
OpenDroid is not working!
OpenPDroid is not compatible with multiuser.
So basic rules for multiuser
1. Must be on stock theme
2. Must not be on openpdroid build
Re: Q&A - TEMASEK's CM10 - Unofficial
CM10.1 not cm10.
You can add a question as to what are thesw cherry picks as alot have this question.
Also i believe you answer for the kernel is not clear. Yoy can straightforward say that kernel cominf with rom is stock cm10.1 kernel and if you want temaseks kernel you flash it from here.
Sent from my GT-I9300 using xda premium
AW: Q&A - TEMASEK's CM10.1 - Unofficial
You can add that you can just flash over temasek's rom over official cm10.1. You mentioned something but it didn't came out that clear.
And under cherry picks. It should be stock browser I think?
Sent from my third Galaxy phone.
WoW.. should help ppl a lot..
Sent from my GT-I9300
iExitus said:
You can add that you can just flash over temasek's rom over official cm10.1. You mentioned something but it didn't came out that clear.
And under cherry picks. It should be stock browser I think?
Sent from my third Galaxy phone.
Click to expand...
Click to collapse
I will add the suggestions however I did not understand the part of the stock browser. In the cherry picks I added that the stock browser has an exit button. Do you think it needs to be rephrased?
Thank you
Sent from my GT-I9300 using xda app-developers app
You've written stock button in op mate.
Sent from my GT-I9300 using xda premium
Mr Woolf said:
You've written stock button in op mate.
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
Thank you very much, I did not realise the spelling error. Thank you both for pointing it out.
iExitus said:
You can add that you can just flash over temasek's rom over official cm10.1. You mentioned something but it didn't came out that clear.
And under cherry picks. It should be stock browser I think?
Sent from my third Galaxy phone.
Click to expand...
Click to collapse
Sent from my GT-I9300 using xda app-developers app
You may wanna update this cos the new STweaks compatibility.
Sent from my GT-I9300 using Tapatalk 2
rickoslyder said:
You may wanna update this cos the new STweaks compatibility.
Sent from my GT-I9300 using Tapatalk 2
Click to expand...
Click to collapse
I did update it. Can you check out whether it includes the necessary updates?
Thanks
And the GAPPS info is outdated.
And Boeffla sound
Suggest the salient elements of STweaks and Boeffla are listed here rather than linked. Messy otherwise.
You may wish to add detail on the Temasek kernel (what it does differently, why the lib file differences etc.) even without STweaks etc.
Big job...
rickoslyder said:
You may wanna update this cos the new STweaks compatibility.
Sent from my GT-I9300 using Tapatalk 2
Click to expand...
Click to collapse
I did update it again, I did my best to include all the information I know and the other information I found on the thread. If you have other information do not hesitate to tell me
LenAsh said:
And the GAPPS info is outdated.
And Boeffla sound
Suggest the salient elements of STweaks and Boeffla are listed here rather than linked. Messy otherwise.
You may wish to add detail on the Temasek kernel (what it does differently, why the lib file differences etc.) even without STweaks etc.
Big job...
Click to expand...
Click to collapse
Sorry but I have no idea about lib file differences. Is there somewhere specified on the thread so that I can copy it?
Thanks
AW: Q&A - TEMASEK's CM10.1 - Unofficial
I have installed the new kernel of temasek.
But my battery will not charge to 100%
What can I do?!
Gesendet von meinem GT-I9300 mit Tapatalk 2
bocke85 said:
I have installed the new kernel of temasek.
But my battery will not charge to 100%
What can I do?!
Gesendet von meinem GT-I9300 mit Tapatalk 2
Click to expand...
Click to collapse
In Stweaks, change hard control voltage to 4.35V
temasek said:
In Stweaks, change hard control voltage to 4.35V
Click to expand...
Click to collapse
I'll try just this, thanks a bunch.
And thanks OP for the FAQ.
I'd like to find more information about all the options available in Stweaks for undervolting, where should I check?
Siyah's had a general -100mV option possibility, which applied to my custom voltage settings. Should I just downvolt 200mV altogether from all my stock values?
Choristav said:
I'll try just this, thanks a bunch.
And thanks OP for the FAQ.
I'd like to find more information about all the options available in Stweaks for undervolting, where should I check?
Siyah's had a general -100mV option possibility, which applied to my custom voltage settings. Should I just downvolt 200mV altogether from all my stock values?
Click to expand...
Click to collapse
Sweet spot for everyone is different. U have to find your own values. Bear in mind no one device is the same with regards to oc / uv tolerance.
temasek said:
Sweet spot for everyone is different. U have to find your own values. Bear in mind no one device is the same with regards to oc / uv tolerance.
Click to expand...
Click to collapse
Alright, thanks! Although, I was wondering if for example, at 1400MHz (which has 1.3V by default), setting it to 1.1V would be the same as setting it to 1.2V with Siyah's kernel but with the general -100mV setting (you could also choose the -25, -50 or -75mV, aside from the individual voltage level)?
bocke85 said:
I have installed the new kernel of temasek.
But my battery will not charge to 100%
What can I do?!
Gesendet von meinem GT-I9300 mit Tapatalk 2
Click to expand...
Click to collapse
Thank now you question is added in the FAQ
I am on latest build and I don't have temasek folder in data (I have enabled settings to view hidden folders and tried different file explorers)
Also Stweaks says no kernel support... what am I doing wrong?
Sent from my GT-I9300 using Tapatalk 2
Dist kernel 4/2(Japan Time) VERY UNSTABLE release
I will release a VERY UNSTABLE version of dist kernel.
Target
Stock rom .75 (cm9 try to make to find the spare time)
changelog
2013/04/02 -Upgrade to 3.0.71.
- change algorithm pegasusq. In pegasusq but no longer.
- Crosstool-ng back to the C compiler.
- I was back to a value of 3 AppDeepSleep. I freeze it 5.
2013/03/21 - Compiler version mismatch! (SOOOOORRYYYY!)
- maybe fix CWM freeze
BUG!
Random reboot
Random freeze
Random ....
Reason
When I followed up on gdb, stop the process and I'm able to do a check syscall. I think that, as things stand unbroken kernel version up of the mach-ux500 probably.
No more or start kgdb from ttyAMA0, but to implement a serial poll to ttyGS0.
But the kernel is not the man you're waiting, try a little more luck.
Features
I have a memory compression using zram. I'm using 25%. I have now started by default.
Use Ultra KSM, We have been in the memory deduplication.
I have to increase the clock of the CPU. I have become 150,200,400,600,800,1150. As DeepSleep zone, I included the 200 and 150.
Review of the power supply to each module. Because the risk is greater, DRMS was decided not to use. (Also no longer freeze)
I respond to a bug in the Cortex-a9.
I have introduced the CWM. I come from Park Cyanogenmod 9.1.
In order to stabilize the operation, we have changed the behavior during earlysuspend. > From aosp
Have been raised to the level of kernel 3.0.71.
Kernel modules that are required, such as radio has developed below / system / lib /. was to reduce the size of the ramdisk ramdisk by pasting a link / lib.
Kernel is compressed by LZMA. ramdisk performs compression xz, brought down the overall size.
There can be added by adding a addhoc, the cpugovener. whelthy, Luluzactiveq, Pegasusq is it. (Think of multicore-ready, the default has been to whelthy)
IOscheld had been originally added, are using fiops (IO scheduler for flash).
In the experience seems to have become a little early. (Compared to stock)
source code
https://github.com/haskerl/LT22-kernel
- Thanks
- ThP kernel
reserve
reserve
going to have a try
AW: [kernel] dist kernel v1.0 [stock]
You seem to be pretty new. 3 posts and only a few thanks. And then you start off with a kernel?
I don't know, this makes me kind of skeptical.
Anyway :
Thanks for your
Sent from my LT22i using xda app-developers app
---------- Post added at 11:13 AM ---------- Previous post was at 11:13 AM ----------
Work. I'm going to taste it this afternoon.
Sent from my LT22i using xda app-developers app
But because it started as a hobby, it is about popularity I guess should I called on.
I'm not touching the kernel is the first time, I actually.
Pant3320 said:
But because it started as a hobby, it is about popularity I guess should I called on.
I'm not touching the kernel is the first time, I actually.
Click to expand...
Click to collapse
Random shutdown, am i right? the default governor/io is pegasusq/sio. Because I have flashed from a clean rom and I got pegasusq as my default, but the O.P says wheatley? should i use wheatley/fiops?
niko626 said:
Random shutdown, am i right? the default governor/io is pegasusq/sio. Because I have flashed from a clean rom and I got pegasusq as my default, but the O.P says wheatley? should i use wheatley/fiops?
Click to expand...
Click to collapse
Ummm... I also confirmed the random shutdown ...Even if any govener, so like to be like that, I'll try to debug.
Random shutdown
Hello! First of all, my english is not the best so ill try to do it quickly. Some of you may know, or maybe not, but on MIUI only 2 cores works by default, to get the 4 cores working you need to use the "Performance" profile on battery settings, so, you can fix this with any custom kernel, or now, you can flash this zip.
This will enable your 4 cores to being used when you need them without using the "Performance" profile, plus you will get some optimizations that i added so you will feel MIUI like you never done before. Well, lets go for it!
This fix works for MI 3 and MI 4
Things that fix do:
- Allows you to use the 4 core and not only 2
- Better multitasking(Follow recomendations steps)
- Stops some useless services
- Tweaks the VM for better performance
- Tune-up the Interactive Governor for battery without losing performance
Latest Version
Now there is two versions, one a bit focused on battery and the other on performance so, youre free to test and choose
Battery: http://www.mediafire.com/file/moidapk07hfwsch/FIX_Nasus_v15_Bat.zip
(Updated) Performance: http://www.mediafire.com/file/bmcuu3x1cxqma6k/FIX_Nasus_v15.4.zip
Note: If you are comming from any verson after 8.2 of the fix you can just flash the latest version without any problem. Or if its your first time flashing this just go for the latest version.
Apps to test this
CPU Float: https://play.google.com/store/apps/details?id=com.waterdaaan.cpufloat
With this app you can see that by default MIUI only uses 2 cores and when the battery temperature gets kinda high(which is most of time) the frecuency locks at 1.19 ghz, with the fix the frecuency will step down the frec one by one so you wont feel the lag that hard and it wont overheat that easy as usually MIUI do.
Instalation:
Just flash it on TWRP, you dont need to wipe anything.
Recomendations:
Go to delevoper settings and turn off Memory Optimization so the fix will work perfect without any MIUI locks.
Turning off MIUI Optimizations its optional since it do not change anything to the fix, its just if you have problems with some apps, that will be because of the MIUI optimizations. Turning off this will also allow you to make your MIUI more like android stock in term of how apps works and how they dont get close and just get all permissions that they need, since you will be able to disable all MIUI permissions manager and battery saver.
Thats all! If you have any question just ask for it, ill answer ASAP!
Enjoy
Original Post: http://www.htcmania.com/showthread.php?t=1304306
Thank u very much....
Thanks mate!
How is the battery for you?
Does it really work with 4 cores?
Which miui version should I install?
lazye53 said:
How is the battery for you?
Does it really work with 4 cores?
Which miui version should I install?
Click to expand...
Click to collapse
1. As it was before.
2. Yes.
3. I'm using it with 7.6.14 xiaomi.eu rom
Hi. Thanks to you for your works. But tell me please, what is mpdecision file using in your patch?
And which changes in other files?
Thanks.
Update Bard 8.6
Changes on virtual memory and seeder deleted, not worth with actual virtual memory changes
Does this work with pisces?
Hello, thank you for this zip it works fine. Do you have any zip that removed or disables all useless Miui apps and services?
Currently testing your cpufix on my Mi3(cancro) running the latest stable MIUI8 china rom. Device feels snappier than before. I am loving it. But I observe no significant difference in terms of battery saving. Will continue to test for another 48-72 hours and post my conclusion. Thanks.
Update(this was released a few time ago, but i had no time to post it here). Cassiopeia v9.3
A few updates ago i just changed one of the files and now the 4 cores works kinda most of time, and btw, i did a few test and leaving the 4 cores on all time uses less battery than normal way to turn on and off the cores. Also did some changes for better performance without losing battery life. The file its on the OP.
Enjoy <3
Broken download link
mdki1996 said:
Broken download link
Click to expand...
Click to collapse
The download link works for me.
Btw, if I were to flash this zip. Is there any way to restore to the original (uninstall)?
I'm interested to give this a try but afraid if things doesn't work there's no way for me to revert.
Any thoughts?
chiwawa10 said:
The download link works for me.
Click to expand...
Click to collapse
Try clicking the download button
chiwawa10 said:
Btw, if I were to flash this zip. Is there any way to restore to the original (uninstall)?
I'm interested to give this a try but afraid if things doesn't work there's no way for me to revert.
Any thoughts?
Click to expand...
Click to collapse
Just copy the zip files and replace whatever on the zip with the original one, if things doesnt work, u can flash that zip (the zip with original files)
tokict said:
Just copy the zip files and replace whatever on the zip with the original one, if things doesnt work, u can flash that zip (the zip with original files)
Click to expand...
Click to collapse
Do you mean that I need to extract the original files from my phone first (as backup)? In case I want to restore, I will need to use them later?
Is that what you mean?
chiwawa10 said:
Do you mean that I need to extract the original files from my phone first (as backup)? In case I want to restore, I will need to use them later?
Is that what you mean?
Click to expand...
Click to collapse
Yup
chiwawa10 said:
Btw, if I were to flash this zip. Is there any way to restore to the original (uninstall)?
I'm interested to give this a try but afraid if things doesn't work there's no way for me to revert.
Any thoughts?
Click to expand...
Click to collapse
You will not need to revert this. Just do a TWRP backup and flash it, just the "system" backup is necesary
Arthur King said:
You will not need to revert this. Just do a TWRP backup and flash it, just the "system" backup is necesary
Click to expand...
Click to collapse
When I read your first post again, it sounds like its fixing a flaw in MIUI. What if I am not using MIUI but other custom ROMs. Will this be useful? I used to be on Lineage OS 14.1. Recently I moved to AOSiP 6.2, both of which are buttery smooth. What's you think?
Introduction:
Hello everyone!
The idea to this 'project' did blossom after having an conversation with @pkgnex in the past about the general idea of creating something else that follows what he started with his PK's Tuning Script for Pixel 2 (XL) but with a twist, mainly as a complement to his own thread that you can find here, but also with a completely different vision and focus on what the script itself should achieve (and deliver) for kind of results for myself and for all of you personally, of course, that wants to try it out and use it as a "daily driver".
Shortly explained.
This script is created with the goal of improving both battery life and performance on our Pixel 3 (XL) devices, and after a whole range of configurations and various set-ups, I've come up with something that, in my eyes, is worth sharing with all of you so that you can try it out yourself and judge on your own, with constructive feedback on what can be improved or added in future releases - if desired. My philosophy is, and will always be, this:
If something can be improved or altered in a positive way so the average user can feel and see a difference, then go for it. Non stop.
The latest release can be found here.
Disclaimer:
This is presented as "what if". If this modification screws up or breaks anything for you, I am not the one to be held responsible. It's a free will to try out this kind of changes/modifications/addons/tweaks, just don't blame the inventors for eventual bad results and/or screw-ups.
Note: This script is not recommended to be modified or customized by the user.
Features:
Reduced battery consumption
Device specific enhancements for best possible balance between battery life & performance
Enabled, and fully configured, Boeffla generic kernel wakelock blocker
Disabled a lot of useless stuff at kernel level (Improves battery life as well as performance)
CPUSet improvements & optimizations
Schedtune tweaks (Improves responsivness)
Power efficiency enhancements
Wide IO block tuning (Reduces the possibility of hiccups, lags and overhead)
Possibly other miscellaneous things I've forgotten to write down here, both big and small.
Requirements/what you need for getting this script fully working:
An unlocked bootloader
Your own specific choice of kernel
Latest possible version of Magisk
Busybox for Android NDK Magisk Module by @osm0sis
Patience
Installation/How-To use & abuse:
1) Download the attached ZIP
2) Extract the script
3) Move the script to the following location;
/data/adb/service.d and give it the following & needed file permissions (0755)
4) Reboot your phone, let Android boot to the launcher and let Magisk boot service do its crucial magic (takes a few seconds before the scripts is fully up and running around behind the scenes)
5) Enjoy!
Note: If you still are unsure how to do for making my kernel configuration / modification work & be up and running behind the scenes, then please read @Phalanx7621 phenomenal guide here or check out @Phalanx7621in-depth video here. The installation method is the same for all generations of released Pixels!
Credits:
@franciscofranco for all the information on which kernel wakelocks that is safe to block
@Phalanx7621 for his phenomenal how-to guide
@Lord Boeffla for his awesome generic kernel wakelock blocker
@pkgnex for inspiring me walking into this partially unknown territory.
@flar2 for his excellent EXKM application and ElementalX Kernel
@osm0sisfor his Magisk Busybox module
Everyone that I've forgotten to mention here
Telegram:
If you want to try out betas / previews of my script before they are officially released, or just hangout and chat a little, then join the official Telegram group here
To-Do list:
Optimize and properly tune things even further for best possible balance between battery life, system responsivness and performance
Contributors:
@xFirefly93
Created: 2019-01-07
Last updated: 2019-01-07
Update!
Note: Don't forget make a folder named "logs" at the root of your internal storage before applying version 1.0.
Version 1.0 (Initial release):
- Initial release!
- Copied over a huge amount of various enhancements from BlackenedMod for Wahoo (Pixel 2 / Pixel 2 XL) + tuned a couple "crucial" Pixel 3 (XL) specific easter eggs
- Blocked a few safe-to-fully-purge kernel wakelocks for slightly improved battery life during idle / deep sleep
- Fully enabled and adjusted all of the Schedutil hispeed based / specific tunables for both of the clusters with the intention of keeping the phone both smooth and snappy while maximizing overall battery life as far as possible
- Included, but commented out, so you can enable power efficient workqueues on-the-fly directly within the script
- Some very additional minor & miscellaneous enhancements and adjustments both here and there
Enjoy!
Magisk manager app keeps stopping while checking for updates after installing script. Is this expected?
Edit, after a reboot magisk is back to normal. I'll keep an eye on this to see if I can repeat it and maybe capture a logcat.
Sent from my [device_name] using XDA-Developers Legacy app
Very interesting! Thanks for the effort! As I consider myself a modding-greenhorn, I'm waiting for the experiences other users have with that Mod!
cheers
georgs_town said:
Very interesting! Thanks for the effort! As I consider myself a modding-greenhorn, I'm waiting for the experiences other users have with that Mod!
cheers
Click to expand...
Click to collapse
Do you have any first impressions so far to share?
*Cheers*
Rommco05 said:
Blackenedmod is heavymetal magic. Pure awesomeness, I run this mod on Mi8 and my breath time to time stop. I don't feel any performance degreasing (maybe opposite) but huge improvement in battery life. Thanks!
(I removed some lines which aren't suitable for Mi8)
Click to expand...
Click to collapse
Which specific lines did you remove?
Testing currently on my op6t.
jacksummers said:
Testing currently on my op6t.
Click to expand...
Click to collapse
Enjoy!
:highfive:
xFirefly93 said:
Enjoy!
:highfive:
Click to expand...
Click to collapse
Loving it.. u should release it everywhere....
Thanks man!
This is the OnePlus 6t T-Mobile version coverted to international version..
Can you use this with the stock kernel or does it need to be with a custom kernel? I'm currently unlocked and rooted with Magisk but running stock otherwise. Thanks
What files should be in the logs folder? I made the logs folder but it's disappeared on reboot so I don't know if working or not?
cooltech786 said:
Can you use this with the stock kernel or does it need to be with a custom kernel? I'm currently unlocked and rooted with Magisk but running stock otherwise. Thanks
Click to expand...
Click to collapse
Should work with stock.
acidspider said:
What files should be in the logs folder? I made the logs folder but it's disappeared on reboot so I don't know if working or not?
Click to expand...
Click to collapse
A automatically generated output log file which tells you if the script is working or not.
A little, but important, update will be released at the end of this week once I am off from work. Perhaps at Saturday if everything is going as planned!
Just wait.
How have the initial release btw performed so far for everyone? :highfive:
xFirefly93 said:
Should work with stock.
A automatically generated output log file which tells you if the script is working or not.
Click to expand...
Click to collapse
Any of these? Dates are not right, phone wasn't even released then. ???
acidspider said:
What files should be in the logs folder? I made the logs folder but it's disappeared on reboot so I don't know if working or not?
Click to expand...
Click to collapse
I saw someone post on here to create the log folder on root and of course it doesn't survive a reboot. I read thru his script and had a duh moment. You need to create the logs folder at the root of the sdcard, /storage/emulated/0.
Sent from my [device_name] using XDA-Developers Legacy app
jd1639 said:
I saw someone post on here to create the log folder on root and of course it doesn't survive a reboot. I read thru his script and had a duh moment. You need to create the logs folder at the root of the sdcard, /storage/emulated/0.
Click to expand...
Click to collapse
That's better. ???
Have been using it for the past few days. Definitely notice better battery life through the blocking of wakelocks. Haven't noticed any difference in performance so seems to be worth running. No issues with stability at all either. Great work!
Can this be run along side naptime ? Also layman question: is this similar to naptime?
Edit: Ok I tried it on Pixel 3 with Elemental X kernal and I'm stuck on the white boot screen with google logo...Any idea ?
I had your script running along side Magisk v18 Stable on Bootleggers Ver. 4 and noticed Viper4Android wouldn't load correctly. It was showing in the Magisk logs but not showing in my app drawer. Per the link below I noticed the last think to load was your script so I deleted it and rebooted. Viper then worked and I was able to reproduce the issue by adding back the script and once again fix it by deleting the script. I really love your script and would like to use it but, Viper is a must for me. Are there any lines in the script that could be deleted or altered for Viper4Android to load correctly via Magisk?
https://www.google.com/amp/s/forum....module-viper4android-fx-2-5-0-5-t3577058/amp/
jon2jay said:
Just an update. Script is great im getting approximately 6 and change hours of SOT.
AOD off.
Location on.
WiFi always on.
kirisakura kernel
Exkm installed (no real tweaks made no idea where to start)
Also in response to previous post, viper working fine for me w/ script, root and this init script.
Click to expand...
Click to collapse
Are you running the factory image? It might be related to me running Bootlegger v4.
jon2jay said:
Just an update. Script is great im getting approximately 6 and change hours of SOT.
AOD off.
Location on.
WiFi always on.
kirisakura kernel
Exkm installed (no real tweaks made no idea where to start)
Also in response to previous post, viper working fine for me w/ script, root and this init script.
Click to expand...
Click to collapse
A update will come when I feel that I've found something that is worth sharing