Database Info

[ROM] CyanogenMod 10 (qwerty)

Here is where I'll post my CM10 builds.
qwerty was the name I gave to the kernel I used to post here before I started to post entire ROM builds.
This is based on the amazing dhiru1602's work, big thanks to him.
Dowloads:
Google Drive
You can't resume downloads with GDrive. If you prefer other hosting websites, you can use the direct link of my builds to remotely upload them somewhere else. Dev-Host allows you to do that and allows you to resume downloads. Feel free to mirror my files.
Sources:
Device, kernel, vendor
Misc changes/instruction to build this ROM. The patches not available on Github are here.
Please, read carefully the whole post.
There are two different versions of the ROM. One is using the kernel 3.0, the other the kernel 2.6.35. Read the known bugs and flash the one you prefer.
I did some changes to this CM-10, I updated it and added some extra features such as inbuilt SD swap (Settings > Storage > Use external storage), possibility to show the navbar without rebooting (System > Power menu > navbar and enable it from the power menu. It doesn't work perfectly, keyboards and notification panel can go behind it) possibility to limit the number of background apps and other handy options.
I also backported some performance patches and misc fixes from CM-10.1 and some apps: Trebuchet, Apollo, Gallery (camera), Clock, CM File Manager and Superuser.
CyanogenMod 10 - kernel 3.0
Click to expand...
Click to collapse
Known bugs:
Backlight issues for some users: the screen backlight will automatically turn on when it's supposed to stay off.
Audio/video sync issues while recording videos at 720p, along with frames and fps drops.
Rare reboots. If they happen, post the content of /proc/last_kmsg.
CyanogenMod 10 - kernel 2.6.35
Click to expand...
Click to collapse
Known bugs:
Missing HW composer.
WiFi doesn't work perfectly. Some users report continuous disconnections or problems connecting to netowroks. Try to use a static IP in case you have problems.
Native USB tethering doesn't work. Use a third party app (tested: android-wired-tether).
The inbuilt Wi-Fi hotspot can be used only once, sometimes more, and after that a reboot is required to use it again. You can though use this modified version of android-wifi-tether, reboots are not required.
HD video playback suffer low framerate issues.
The 720p preview framerate is intentionally limited, especially while recording. The recorded video is (almost) fine.
There are sometimes lags in the preview while video calling with the front facing camera
Poor bluetooth headset sound quality. (I don't own a bluetooth headset, hence it's very hard for me to find the problem) - flash libaudio-BT-NR-fix.zip.
Release changes:
Code:
Look for the name of the zip in this thread to find its changes. This is no more updated.
...
20130425: Camera HAL updates. Removed background apps limit. Use the modified dev settings to choose the number of background apps.
20130416: Camera HAL: experimental changes
20130407: Partially working WiFi tethering (perfect with [I]android-wifi-tether[/I])
20130402: Several kernel changes, UMS regression fixed
20130329: Video pillarbox. Regression: UMS requires adb
20130326: Optimized build
20130320: SSID fetch fixed
20130319: Better wpa_supplicant support: WiFi scan and disconnecting bug fixed. Missing WiFi signal intensity fixed.
Instructions
Click to expand...
Click to collapse
Stock ROM / CM7 / CM9 / CM10 Alpha3 (or older):
dhiru1602 said:
IMPORTANT! READ BEFORE FLASHING THIS RELEASE!
This ROM will wipe data due to different partitioning. The device would reboot while flashing and resume again.
Once on this ROM, the most effective way of going back to any other ROM would be to repartition from Odin.
While converting the filesystem, your efs that has your IMEI is backed up to /emmc/backup/efs. Keep a backup on your PC just in case.
Incase if you don't get a network signal, check if your IMEI and Baseband are proper. If not, go back to stock and try again.
Do NOT use Odin to flash Modems. Due to different partitions, Odin will screw up your existing MTD setup.
Click to expand...
Click to collapse
Stock ROMs only: Make sure you have CWM. Flash a custom kernel otherwise
Download the zip of the ROM and save it into the internal SD or the external one (*)
Reboot to recovery
Flash the downloaded zip
optional: Flash mobiledata_off.zip if you want mobile data off during the first setup
optional: Flash Google Apps (for Android 4.1.2, many things will break otherwise)
Reboot
(*) While flashing, the device will reboot and you'll see a different recovery after that.
If the zip is inside the internal SD, the flash will re-start automatically after the reboot.
If the zip is inside the external SD, you have to re-start the flash manually re-flashing the zip. If you don't do that, only recovery will work until you flash the zip.
CyanogenMod 10:
Download the zip of the ROM and save it into the external SD or the internal memory
Reboot to recovery
Flash the downloaded zip
optional: Flash Google Apps (if you have already flashed them once, you can skip this step)
Reboot
Data wipes are mandatory only if you are not using CM10, it's not required otherwise.
It doesn't matter if you are going to flash the version with the 3.0 kernel and you are using the other, it should work.
CyanogenMod 10.1/10.2:
Download the zip of the ROM and save it into the external SD or the internal memory
Reboot to recovery
Flash the downloaded zip
optional: Flash Google Apps
optional: Flash mobiledata_off.zip if you want mobile data off during the first setup
Wipe data/factory reset
Reboot
Downgrades are probably not expected, that's why you need to do a data wipe.
Important note:
The modem is always replaced with XXLE4 modem when this ROM is flashed over a stock ROM, CM9 or CM10 Alpha 3 (or older).
You can easly replace it. Take modem.bin from the tar of a stock ROM, place it in /radio overwriting the existing one and reboot. This is required only once, modem.bin is never replaced while updating the ROM. I9003L must do this, I9003 users can use the included modem, but it's better to use the modem made for your region.
Useful informations
Click to expand...
Click to collapse
The latest versions of Instagram are not working due to a problem with related to the GPU binary blob. Instagram 3.4.0 is the latest working version. Probably every device using the same binary blob is affected (Optimus Black for example). You can download a modified version from here that will allow you to login.
The latest versions of Skype do not work properly, the preview is stretched and wrongly rotated. Use Skype 2.9.0.315 or see this post.
LEDs are not supposed to blink when a new notifcation arrives. They'll light up, but they won't blink. Making them blink would prevent the device from entering deep sleep.
(3.0 kernel) Once the battery is fully charged, it will start discharging and it won't be recharged automatically if at least 90 minutes have passed. You can forcefully charge it by unpluggin and re-pluggin the cable. This is an intended behaviour, charging the battery continuosly to keep it at 100% can shortnmyself toer its life.
This ROM allows you to force two apps to stay in memory. See this post for more info.
I made possible to toggle the navbar state directly from the powermenu modifying the existing expanded desktop feature, however it's not working perfectly. The navbar can go over the notification panel and the keyboard while in landscape. However it works as expected if you enable the navbar by setting qemu.hw.mainkeys or modding framework-res.apk. I have no intention to "fix" this as I can't see the utility of the navbar on our device.
(3.0 kernel) For some reason when the screen is turned off during a call by the proximity sensor, if enough time has passed it won't be turned on automatically. You can wake the screen immediately by pressing the home button or the power button or you can increase the backlight timeout from the settings. That will make the proximity sensor work for longer (I'm not sure, but I think the proximity sensor stops working exactly after this timer has expired). this problem is maybe solved.
FM radio is available through third party apps, such as Spirit FM
"Native" 3G video calls are not supported and most likely never will, flash a stock ROM if you need them. GTalk, Skype and all the other apps works though.
(3.0 kernel) if you lost your IMEI, WiFi will probably not work. See this for more info and instructions to fix the problem. No more required.
(3.0 kernel) part of the RAM is reserved. You'll see that we have 442MB 454MB of RAM, that's fine, the missing RAM is not really lost, it's still used.
If the keyboard keeps crashing, you probably flash the wrong gapps.
The magnetic sensor sometimes reports wrong values. When it happens, the field intensity is very high. This was observed with the 3.0 kernel, but probably the same thing happens with a 2.6.35 kernel.
(3.0 kernel) my SD card (it's probably a cheap SD card) is not working properly and I often have corrupted files. It worked fine with the kernel 2.6.35, so if you often have corrupted files, try a different SD card or use the old kernel.
Weird activity in standby? Read this.
(3.0 kernel) 1.2GHz is not stable on every device. I had to disable SmartReflex because it was causing crashes on my device. This means that the voltage of the OPP5 is locked the value I chose is not universally good. I'd prefer not to increase it more, if you have too many reboots, don't overclock. WARNING: don't tick "Set on boot" unless you are sure your device can handle OC. f you are stuck in a bootloop, flash disable_opp5.zip.
In case the max frequency is 1.1GHz, then SmartReflex is enabled and the option in DeviceParts has no effect.
If you find a bug not listed, please report.
Post as many informations as possible, ways to reproduce it and logs.
You can easily grab (almost) all the logs I need by pressing vol down, vol up and power at the same time ("recent" builds only). LEDs will blink and /storage/sdcard0/logs_qwerty/log_DATE.txt will be created. In case the memory is not ready, you'll find the files in /data/logs_qwerty/log_DATE.txt.
The standalone kernel is no more mantained. Flash the ROM instead.
Click to expand...
Click to collapse
Kernel - 2.6.35
Click to expand...
Click to collapse
After months of use, I decided to publicly release my kernel.
This is for CyanogenMod 10 Alpha 4.
It's based on the GB kernel sources released by Samsung (GT-I9003_GB_Opensource_Update2.zip), modified (mostly by dhiru1602) to work with CyanogenMod.
Because of my lack of fantasy I named it "qwerty". It sucks, but at least it's easy to remember.
Main features:
XDA_Bam's code and fixes:
◦ 5 OPPs
◦ Booting at stock speed (1000MHz)
◦ Slight undervolt (3%) on all OPPs
◦ Home button double presses fix
◦ Lowered processor transition latency
◦ Stable Bluetooth connections
Modified light sensor driver: [1]
◦ Disabled hardcoded filter. CyanogenMod has its own filters, enable it from the settings.
◦ Dynamic polling interval
◦ Code cleanup
Modified battery driver [2]
CPU Governors:
◦ Ondemand (default)
◦ SmartassV2
◦ Conservative
◦ Performance
I/O schedulers:
◦ Deadline (default)
◦ Noop
◦ CFQ
◦ SIO
Toggable FSync
Fixed always ON LEDs bug when used for notifications only
VPN networks support (not tested)
Slightly increased touchkeys sensitivity (from 45 to 35)
Other minor changes and optimizations
Downloads:
version 4.0: kernel-qwerty-cm-10-galaxysl-v4.0.zip: kernel with custom DeviceParts.apk [3], hostap and tiap_drv.ko [5]
clean-qwerty-cm-10-galaxysl.zip: restore zip with dhiru1602's kernel
UPDATE: USB composite is still a bit messed up. Windows can't recognize the phone when RNDIS (USB tethering) is enabled (working fine with Linux).
If you need RNDIS, flash this kernel release or the previous one.
Additional zips:
powerHAL-cm-10-galaxysl.zip: power HAL for boosting the CPU when ondemand is used [4]
libsensor-cm-10-galaxysl.zip: custom libsensor. Read note [1]
Changelog:
Code:
22/04/13: [URL="https://github.com/sconosciuto/android_kernel_samsung_latona/compare/v3.1...v4.0"]v4.0[/URL]
02/04/13: [URL="https://github.com/sconosciuto/android_kernel_samsung_latona/compare/v3.0...v3.1"]v3.1[/URL]
01/03/13: [URL="https://github.com/sconosciuto/android_kernel_samsung_latona/compare/v2.1...v3.0"]v3.0[/URL]
12/02/13: [URL="https://github.com/sconosciuto/android_kernel_samsung_latona/compare/v2.0...v2.1"]v2.1[/URL]
09/02/13: [URL="https://github.com/sconosciuto/android_kernel_samsung_latona/compare/v1.0...v2.0"]v2.0[/URL]
08/02/13: [URL="https://github.com/sconosciuto/android_kernel_samsung_latona/commits/v1.0"]v1.0[/URL] - Initial release
Notes:
[1] I made it compatible with the prebuilt libsensor included in CyanogenMod, but I'm using my own libsensor and maybe I didn't test this kernel with the stock one for long enough. I hence added my libsensor, just in case. If you want to restore the original libsensor, simply remove /system/lib/hw/sensors.latona.so.
[2] You can modify "samsung-battery" wakelock length through DeviceParts. By default it behaves like the original module. If you see "Android System" or anything else eating your battery with no reasons, increase the delay or restore the default one.
[3] DeviceParts.apk (System Settings > Advanced) is included because of some additional settings useful when this kernel is used. I'm not a Java dev, so it's probably not perfect, but it works quite well. I took pieces of code from other devices (mostly Crespo, Aries and S2). The source code is available, suggestions are more than welcome.
[4] Power HAL will make the CPU jump to a certain frequency (I set 800MHz) whenever Android requires it (when the screen is touched for example). Power HAL will also limit the max freq to 800MHz (my choice, not too fast, not too slow) when the screen is off. You can change the boosting freq from my custom DeviceParts. CPU frequencies changes (See XDA_Bam's thread for more info about variable overclocking) are not expected. If you don't like it, simply remove /system/lib/hw/power.latona.so. Few more lines about power HAL here.
[5] hostap and tiap_drv.ko make WiFi tethering possible using this modified version of android-wifi-tether.
Special thanks to dhiru1602 and XDA_Bam for their awesome work.

Wow. I'll flash it for sure.
Thanks for sharing.
Update:
Flashed and it works just fine. Just changed max freq to 1200.
Deviceparts looks very professional as well.

Hats off to u buddy. Also kernel name is really good buddy. Dont worry about that
Suggestion : Can u add SIO schedular? For me smartassv2 (thanks for adding it) with sio works really well.
Request : Sorry but I am not exactly getting power HAL description. Can u please explain me a little bit.

Re: [KERNEL][CM10] qwerty [08/02/13]
have any issues of wifi connections? like always dc.. and got any problem connecting back?
Sent from my GT-I9003 using xda app-developers app

Re: [KERNEL][CM10] qwerty [08/02/13]
I am now on slimbean rom, please kindly advise a proper flash procedure becoz I always stuck on the Samsung splash screen …
Sent from my GT-I9003

imjustafq said:
have any issues of wifi connections? like always dc.. and got any problem connecting back?
Sent from my GT-I9003 using xda app-developers app
Click to expand...
Click to collapse
Works fine for me. Try wiping cache+dalvik cache.
erickkhhk said:
I am now on slimbean rom, please kindly advise a proper flash procedure becoz I always stuck on the Samsung splash screen …
Sent from my GT-I9003
Click to expand...
Click to collapse
Are you using SIRI kernel?

Hetalk said:
Works fine for me. Try wiping cache+dalvik cache.
Are you using SIRI kernel?
Click to expand...
Click to collapse
I am just using the signal fix kernel by loSconosciuto before ...........

^ Did you flash kernel, then wipe cache/dalvik ... if yes try fixing permissions and see if it works. Else, post in the slimbean thread ... Lolation might be able to advise on how to make it work. I see he did thank the OP here.

Re: [KERNEL][CM10] qwerty [08/02/13]
How's this kernel's battery drain? Is it as good as alpha 11 kernel?
I'm so pleased with alpha 11 but I'd love to switch to this kernel.
Sent from my GT-I9003 using xda premium

Re: [KERNEL][CM10] qwerty [08/02/13]
Hetalk said:
^ Did you flash kernel, then wipe cache/dalvik ... if yes try fixing permissions and see if it works. Else, post in the slimbean thread ... Lolation might be able to advise on how to make it work. I see he did thank the OP here.
Click to expand...
Click to collapse
i post here becoz i wanna flash this kernel will try what u say later, thx
Sent from my U9GT2 from moage.com using xda premium

^ You'll need to wait for users to get thru a battery cycle to report battery drain. I did charge my phone to 100% after flashing qwerty .. so will report my experience tomorrow.

Re: [KERNEL][CM10] qwerty [08/02/13]
just flashed this kernel.. on top of my cracker that i am using previously.. no problem on boot.. upgrading apps as usual.. ive noticed the speed, scrolling and such.. its faster than cracker .. the speed of gb is there..gonna test for some time.. thanks.. via slimbean 3.1 A4..
Sent from my GT-I9003 using xda app-developers app

I am pleased thank you very much !!!
Governor smartassV2 and IO Scheduler deadline (reputable boost daily)
Mini CPU 300/1000 is an exellent choice (I guess the hotboot fix)
it's just what I need ^^
Thank you for taking us solicitous

Thank you for the kernel...I'm on Dhiru's CM10 A4 with Alpha 11 kernel, now switched to this kernel, I do not find "DeviceParts" installed..is it normal?

just added a tab (specific options) available in the parameter menu

vishal24387 said:
Request : Sorry but I am not exactly getting power HAL description. Can u please explain me a little bit.
Click to expand...
Click to collapse
As you may know, what a CPU governor does is to decide when the current frequency needs to be changes and what's the target frequency. These decisions mostly depend on the current CPU load: high load -> high freq.
What power HAL does is to require a high CPU frequency regardless the load. This mostly happen on user interactions (ie: the screen is touched)
Its aim is to provide a smoother experience, because basically it's trying to predict high CPU loads. The downside is that sometimes the CPU is boosted for no reasons.
For example if you touch the screen to scroll a page, when the scrolling starts the CPU is already at a high freq and there won't be probably initial lags. If you tap the screen, just for the sake of it, the CPU will be boosted for no reasons (by default a CPU boost will last 500ms).
I think it's part of the project butter.
The only governor with a boostpulse interface between those included is ondemand. The other governors included most likely will never have a boostpulse interface.
Try to use ondemand with and without power HAL. You can "see" the difference with CPU Spy. 800MHz will be used a lot when power HAL is present (you can change the boosting freq from the advanced settings).
By the way I updated ondemand, it's faster than in the original kernel.
vishal24387 said:
Suggestion : Can u add SIO schedular? For me smartassv2 (thanks for adding it) with sio works really well.
Click to expand...
Click to collapse
Try to use Deadline for a while. I tweaked it to better perform on flash devices. Anyway I don't think that changing I/O scheduler will make a tangible difference.
imjustafq said:
have any issues of wifi connections? like always dc.. and got any problem connecting back?
Click to expand...
Click to collapse
All our kernels based on the sources released by Samsung use a prebuilt module for WiFi. Dhiru tried to use the opensource driver, but it didn't work.
This prebuilt module, taken from our stock ROMs, requires a prebuilt and modified wpa_supplicant which is not completely compatible with Android 4.0+ (Samsung didn't give us the changes required to make the opensource one work). To make things worse there's dhcpcd, we have to use an old version because of the old wpa_supplicant.
In other words: it sucks.
With some access point there are no issues, with others WiFi works, but not so well and with some others nothing works.
EDIT:
Now that I think of that, there are maybe some differences when this kernel is used. I took the prebuilt module from XXLE4 instead of taking it from EDIT2: XXKPM
The warning message I get the first time I turn WiFi (maybe it happens even with the other module, I didn't try it) on suggests me that something was changed in XXLE4, but I don't know if this is a good thing or not.
erickkhhk said:
I am now on slimbean rom, please kindly advise a proper flash procedure becoz I always stuck on the Samsung splash screen …
Click to expand...
Click to collapse
I'm starting to think the problem is CWM. For now only you and spacebar2011 had issues. I will PM you something when I'll have some free time to find the problem. If nothing works, I'll just give you the tars to flash the kernel with ODIN as I did with my signal fix kernel.
@Hetalk
Thanks for trying to help, but he is a peculiar situation. The problem is not the updated blob or a wrong flash, he (and spacebar2011) tried to flash my signal fix kernel several times over a clean CM10 with no success.
rodero95 said:
How's this kernel's battery drain? Is it as good as alpha 11 kernel?
I'm so pleased with alpha 11 but I'd love to switch to this kernel.
Click to expand...
Click to collapse
Dunno, battery life had never been exceptional for me. If you use your phone a lot, any kernel will give you a bad battery life. You can see differences only if you keep your phone most of the time in idle, with mobile data disabled.
wee2wee said:
Thank you for the kernel...I'm on Dhiru's CM10 A4 with Alpha 11 kernel, now switched to this kernel, I do not find "DeviceParts" installed..is it normal?
Click to expand...
Click to collapse
As I wrote in note [3]:
DeviceParts: System Settings > Advanced
It's not in the app drawer.

loSconosciuto said:
As I wrote in note [3]:
DeviceParts: System Settings > Advanced
It's not in the app drawer.
Click to expand...
Click to collapse
Thanks...found it...

loSconosciuto said:
As you may know, what a CPU governor does is to decide when the current frequency needs to be changes and what's the target frequency. These decision mostly depends on the current CPU load: high load -> high freq.
What power HAL does is to require a high CPU frequency regardless the load. This mostly happen on user interactions (ie: the screen is touched)
Its aim is to provide a smoother experience, because basically it's trying to predict high CPU loads. The downside is that sometimes the CPU is boosted for no reasons.
For example if you touch the screen to scroll a page, when the scrolling starts the CPU is already at a high freq and there won't be probably initial lags. If you tap the screen, just for the sake of it, the CPU will be boosted for no reasons (by default a CPU boost will last 500ms).
I think it's part of the project butter.
The only governor with a boostpulse interface between those included is ondemand. The other governors included most likely will never have a boostpulse interface.
Try to use ondemand with and without power HAL. You can "see" the difference with CPU Spy. 800MHz will be used a lot when power HAL is present (you can change the boosting freq from the advanced settings).
By the way I updated ondemand, it's faster than in the original kernel.
Try to use Deadline for a while. I tweaked it to better perform on flash devices. Anyway I don't think that changing I/O scheduler will make a tangible difference.
Click to expand...
Click to collapse
Thanks for ur simplified explaination This means in order to bring smoothness ondemand will keep most of the time freq at 800 mhz (as per ur settings). But definitely its going to affect battery life as just for a simple touch freq will raise to 800 mhz directly. Anyway overall it depends on user who want battery life or smoothness
I have used ur fixed signal kernel for longer time. That kernel really works very well when we use phone (even with 2g net). But surprisingly in deep sleep mode (means with gsm network on on and 2g net off) then there is very heavy battery drain For me its 25% battery drain in 9hr deep sleep mode. But if we keep our phone phone offline in deep sleep mode then it will drain battery just 4% in 9hr. Strange...!!!
I will monitor tonight also with that signal fix kernel. and final tomorrow I will flash this kernel on clean cm10a4 so that I can compare both ur kernels
EDIT : My doubt was right. Your previous signal fix kernel works really good. Yesterday night tested and I found that lost 3% battery in 8 hrs standby. Means my previous 25% battery loss was not a correct observation. Anyway now I will flash this kernel and tell u the results

Re: [KERNEL][CM10] qwerty [08/02/13]
Well, its obvious that keeping a continuous connection with the network costs battery and that when we are connected with mobile network it will eventually change between signal modes (2g, HSDPA, edge, etc) and that also costs battery.
That's why mobile network use to consume more battery than WiFi or offline.
Sent from my GT-I9003 using xda premium

Really nice Kernel with good combination of battery and performance and many good tweaks
Thank you very much Sir :laugh:

[KERNEL] [UNIVERSAL] [AOSP] WildKernel Reloaded v008 - October 21, 2013

WildKernel
README
Emmanuel U said:
Ugh... (oh how I've dreaded making this post, go grab the kleenex or you can just skip the next paragraph and get to the jist)
So my (previously used and "refurbished") myTouch is slowly becoming useless. So I had originally dropped it onto concrete (a month and a half ago) in which I didn't notice any visual/cosmetic damages so I assumed I was fine. However promptly after attempting to open my keyboard I notice my phone would freeze for 5 or seconds before registering the hardware event and rotating screen etc. It eventually began to progress to display weird digital artifacts at random times during use (which would cause annoying lag). Then one faithful day, the 'lag' was getting to excessive while I urgently needed to use my phone so I battery pulled in hopes of rebooting the phone as quickly as possible to use...but just my luck; the phone turned back on but the display didn't (in the sense that I felt the phone vibrate when I initially pressed the power button alongside seeing the small red light in my trackpad light up). So after a stressful day of trying to play with my phone in fastboot/adb I managed to turn my display back on. But now the display failure has progressed to the point of my phone only being usable when they keyboard is pulled out around 2/5 of the way and kept in that position....all other positions render the display useless. This makes it fairly difficult to use the device seeing as it has to be kept in this abnormal position to function.
Jist: I ordered a temporary Galaxy S2 off ebay until my contract ends so that I can switch carriers all together. So I won't really be able dev on this phone like I use to with it being broken. However I'll try to still occasionally update my roms as far as upstream...but any bug fixes at this point sadly won't be able to come from me as debugging on this phone is tedious. But keep in mind I'll still poke my head periodically in this forum and see if my 2 cents is needed anywhere. But don't expect anything more from me then 'upstream updates'.
Good day guys and remember to have a firm grip on your phone at all times.
Update:
First of all I'm quite flattered to all the people who offered up a MT4GS to giveaway, such a generous community we have here :good:
However this will not be necessary as I still have a slightly working MT4GS...the only reason I got a GSII is because it's not functional enough to be my daily driver due to the position it has to be held in to function. Nevertheless I can still develop on the phone (which was why I stated I was planning on updating this rom soon). But I'd like to say thanks again directly to @BaconPancakes and @Ziida and anyone else who may have been planning to offer me a a MT4GS...but it won't be needed.
Click to expand...
Click to collapse
Please report anything good and bad so that I know what to keep and what not to keep for a final release. This also helps me push out fixes faster when presented with lots of information.
Please wipe cache and dalvik cache
Note: If your S-ON, after flashing the zip you'll see a file called "WildKernel-boot.img" on your sdcard, use that to flash the kernel in fastboot (bootloader) with the following commands:
Code:
1. *connect device to computer and adb*
2. adb pull /sdcard/WildKernel-boot.img
3. fastboot flash boot WildKernel-boot.img
4. fastboot reboot
Download Latest WildKernel for All Android Versions (AOSP) S/ON + S/OFF
Mirror (HTTP) / (FTP)
OLD Downloads for WildKernel ICS and JB for S-ON(Mirror)
View all public kernel releases (Mirror)
You may find my source hosted @ Github
Info on Governors/Schedulers
Changelog:
Code:
[B]October 21, 2013 - ver008 reloaded[/B]
1. Rebase to Linux 3.0.100
2. Support for Android 4.3.1
3. Enable universal CPU frequency synchronization for all roms (not just mine)
4. Add back all governors
[B]August 27, 2013 - ver007 reloaded[/B]
1. [B]MAJOR[/B] Update to Kernel, lots of fixes
2. Now Universal with any Rom, S-ON/S-OFF (see first post for details)
3. Recommended if using any earlier version of WildKernel
4. Rebase to Linux 3.0.93
[B]April 29, 2013 - ver006 reloaded[/B]
1. Thermal updates
2. GPIO updates
3. MSM Framebuffer tweaks + YUV4444 additions to support recent CM 10.1
4. Update to Git Kernel v3.0.75
5. Add QCOM crypto engine [lomarb]
6. Fixed all battery/reboot issues that may have been kernel or rom related
7. Lots of driver updates (crypto, genlock, rotator, frame-buffer, kgsl, etc.)
[B]April 19, 2013 - ver005 reloaded[/B]
1. Change low clock speeds to stable volts to fix BSoDs
2. Update to Git Kernel v3.0.74
3. Update the Battery Driver
4. Build CIFS, TUN, and NIFS as modules to reduce zImage size
5. Update to CodefireX Linaro 4.7.3 optimized toolchain
6. Updated Early Suspend/Late resume drivers [intellidemand]
7. More tweaks from faux and showp1984 [intellidemand & badass]
8. -03 compiler optimizations
9. Fixed some bluetooth wakelocks
[B]April 17, 2013 - ver004 reloaded[/B]
1. Add QDSP6 V3
2. Update to to Git Kernel v3.0.73
3. Update to Latest CAF Bluetooth Drivers
4. Thermal changes and improvements
5. Major revamp to CM kernel (fixed black screens of death)
6. Lower Ondemand/Intellidemand phase frequencies to be more battery saving
7. Snapdragon Optimizations from earlier WildKernels
8. NEON optimizations
9. GPIO power button tweaks [upstream]
10. Increased Max frequency to 1728mhz (1512mhz by default)
11. Imported moderate undervolting from earlier WildKernels
12. Wifi Optimizations for battery life
[B]March 17, 2013 - ver003 reloaded[/B]
1. Major update upstream to scherhagen's base
2. Update to to Git Kernel v3.0.69
3. Update to Latest CAF Bluetooth Drivers
4. KGSL hacks to ensure glitch free changing on speeds and better hang detection
5. KGSL updare to Ville
6. Use Linaro Toolchain
7. Use *really* low power Wifi when idle
8. Allow Flash to be used at any battery percentage
9. Lower Badass phase frequencies to be more battery saving
[B]Sep 3, 2012 - ver003[/B]
1. Bluetooth updates upstream
2. Downgrade to linux Kernel v3.0.39 with custom libs to *really* fix lag
3. Badass back to default governor as the most stable
4. More LMK tweaks
[B]Sep 2, 2012 - ver002[/B]
1. Implemented USB forced fast charge v3.1
2. Downgrade to linux Kernel v3.0.40 to fix lag
3. Ondemand tweaks, early suspend updates, and is now default governor because of balance of stababilty, battery, and speed.
4. LMK tweaks
5. Updates to bluetooth from CAF (more battery saving and stable)
6. Updates to scheds from faux
7. mpdec ready but disabled until stabalized
8. A lot of improvements since ver001
Thanks:
SilverL
Scverhagen
Team Hydra
TeamDS
faux123
Sultan
Tamcore
cretin45
showp1984
RomanBB
and any others I may have missed

boot.img
please kernel boot.img from divice S-ON

Re: [KERNEL] WildKernel Reloaded v003 - March 17, 2013
Will try this tomorrow on CM 10.1 (by SilverL)
Greets Vauvenal7
Sent from my myTouch 4G Slide

Could you kindly list the governors this kernel? Also, am i right to say that this kernel contains all the features found in scverhagen's kernel? Thanks in advance.

This kernel is pretty good in performance and behaves better than scverhagen's but wifi isn't working properly.

SKAm69 said:
This kernel is pretty good in performance and behaves better than scverhagen's but wifi isn't working properly.
Click to expand...
Click to collapse
Whats wrong with wifi?

xmc wildchild22 said:
Whats wrong with wifi?
Click to expand...
Click to collapse
At times, it wouldn't turn on or the speeds be very slow. Reboot helps though.
But I like the kernel and how it works with option "disable HW overlays" unchecked. And video playbacks aren't glitchy. Also, it gave me about 5fps gain in NenaMark2 gbench.

Update, enjoy (and report feedback)

Thanks for the update!
FPS in NenaMark2 seems to be lower even on max 1.7Ghz. Still testing the kernel.

SKAm69 said:
Thanks for the update!
FPS in NenaMark2 seems to be lower even on max 1.7Ghz. Still testing the kernel.
Click to expand...
Click to collapse
Which governor/scheduler?
Everyone:
Update, enjoy (and report feedback)

xmc wildchild22 said:
Which governor/scheduler?
Everyone:
Update, enjoy (and report feedback)
Click to expand...
Click to collapse
Both intellidemand and Badass.
Will try the 005 version.

SKAm69 said:
Both intellidemand and Badass.
Will try the 005 version.
Click to expand...
Click to collapse
also you said scores are lower, but lower compared to what?

Build 005 broke my camera viewfinder.
The picture is fine after you snap the photo but green/garbled picture while looking before taking the shot (if that makes sense)
I tried screenshotting but the picture was also fine!
Might be just me, I wiped Dalvik after the flash though.

xmc wildchild22 said:
also you said scores are lower, but lower what?
Click to expand...
Click to collapse
I was getting around 48 fps on SilverL's and Tbalden's AOKP and CM stock kernels (scverhagen's base I think), now it's less than 42fps on v.004. 43-44fps on v.005.
The test is NenaMark2.
But overall the kernel seems to be smooth and nice.

SKAm69 said:
I was getting around 48 fps on SilverL's and Tbalden's AOKP and CM stock kernels (scverhagen's base I think), now it's less than 42fps on v.004. 43-44fps on v.005.
The test is NenaMark2.
But overall the kernel seems to be smooth and nice.
Click to expand...
Click to collapse
This is to be expected. These two governors seem to be doing what they're supposed to. They not made for benchmarks. The way mine is currently they have a middle ground frequency which i assume you may be hitting most of the time while this is going.
These 2 governors also take gpu into consideration and adjust their speeds accordingly. If it doesnt need both cpu and gpu to process, the cpu will actively throttle and not stay maxed which possibly results in the fluctuating scores. I get 42 fps on mine...(currently not updated to latest). You probably just ended up running the tests at times where something else was keeping the cpu at a higher frequency.
When I use the performance governor I get 52 but that governor keeps the cpu at the current max frequency (mine being 1080).
OpenGL scores will fluctuate with these governors... its nothing to worry about. I ran the test too, it doesnt seem to be as intensive as any game would be, doesnt require user interaction(something which also drives the cpu frequency throttling in games), so I wouldnt worry about these benchmarks. If you want to benchmark you should really be using performance as the stepping in any other governor will always vary based on load, and this tests puts more load on the gpu allowing the cpu to change frequencies as it sees fit.
Should mention my intellidemand score is 48 and badass is 42.

SilverL said:
This is to be expected. These two governors seem to be doing what they're supposed to. They not made for benchmarks. The way mine is currently they have a middle ground frequency which i assume you may be hitting most of the time while this is going.
These 2 governors also take gpu into consideration and adjust their speeds accordingly. If it doesnt need both cpu and gpu to process, the cpu will actively throttle and not stay maxed which possibly results in the fluctuating scores. I get 42 fps on mine...(currently not updated to latest). You probably just ended up running the tests at times where something else was keeping the cpu at a higher frequency.
When I use the performance governor I get 52 but that governor keeps the cpu at the current max frequency (mine being 1080).
OpenGL scores will fluctuate with these governors... its nothing to worry about. I ran the test too, it doesnt seem to be as intensive as any game would be, doesnt require user interaction(something which also drives the cpu frequency throttling in games), so I wouldnt worry about these benchmarks. If you want to benchmark you should really be using performance as the stepping in any other governor will always vary based on load, and this tests puts more load on the gpu allowing the cpu to change frequencies as it sees fit.
Should mention my intellidemand score is 48 and badass is 42.
Click to expand...
Click to collapse
Thanks for exlaining the things about these governors. But I've noticed that Badass keeps the max frequency only up to 908Mhz even if the load is 100% unlike intellidemand. That's weird. BTW I've tried the 1.7 performance and got only 48 without any background tasks.

i think this is a kernel issue...why does the phone keep resetting the max frequency is 1188?! happens no matter what i do. is it an adaptive governor limitation or something?

anitgandhi said:
i think this is a kernel issue...why does the phone keep resetting the max frequency is 1188?! happens no matter what i do. is it an adaptive governor limitation or something?
Click to expand...
Click to collapse
set the max freq with an app that is set to restore on boot (SetCPU, CM performance, etc.)

That's what I've been doing. And I even tested by restarting and it'll keep the 1512, then I'll check a bit later and it's back to 1188.
So I switched to kernel tuner thinking that won't have the issue, but I just checked and it switched back to 1188 and I haven't restarted in between.
Within one boot session it shouldn't just reset the frequency. And it's not just adaptive cuz I'm on badass now
Sent from my MyTouch 4G Slide using xda app-developers app

anitgandhi said:
That's what I've been doing. And I even tested by restarting and it'll keep the 1512, then I'll check a bit later and it's back to 1188.
So I switched to kernel tuner thinking that won't have the issue, but I just checked and it switched back to 1188 and I haven't restarted in between.
Within one boot session it shouldn't just reset the frequency. And it's not just adaptive cuz I'm on badass now
Sent from my MyTouch 4G Slide using xda app-developers app
Click to expand...
Click to collapse
Sounds like you may have conflicting bootup settings or init.d settings. I would find a way to clean those up. Id suggest wipiing but no one ever likes doing that.

[Kernel][23-12-2014]halaszk-UNIVERSAL5420

Changelog and downloads here:
https://github.com/halaszk/halaszk-UNIVERSAL5420/wiki

Issues and solutions :
https://github.com/halaszk/halaszk-UNIVERSAL5420/issues

https://github.com/halaszk/halaszk-UNIVERSAL5420/blob/master/arch/arm/configs/halaszk_defconfig_N900
I love your setting
Well i'm on the phone so i didn't see something but.. i advise to put row as the main scheduler (best for ssd hardware) and the conservative governor modified with the sampling rate min at 50.000.. the same for the ondemand..
If you need i'll patch those 2 for you.. (i don't know how to use github but i can patch the *.c)
Anyway the kernel seems good.. i'll test it tomorrow
---------- Post added at 04:36 AM ---------- Previous post was at 03:40 AM ----------
http://www.imgur.com/mLVh6cc.png
Works good with correct uv :thumbup::thumbup:

this is the best kernel with so many controls including LED which i was missing coz note 2's led is much brighter than ours
now i can fade in and out
cheers !

I think now I really need to root and install CWM on my phone!!!!!!!!
Features are great man. thanks. keep up the good work

When ever I change the display controls noting happened ..same in charging control when I change the voltage it does not increase

great work best kernel for n900

karthickkatta said:
When ever I change the display controls noting happened ..same in charging control when I change the voltage it does not increase
Click to expand...
Click to collapse
If you enabled "enable register hook and master sequence" in screen tab under synapse this settings works perfectly!
Sometimes charging settings some roms applied after reboot the phone. My phone on Chrisleko Rom V4, and it works perfectly without restartat the phone. (the charge control menu not a voltage settings)

halaszk88 said:
If you enabled "enable register hook and master sequence" in screen tab under synapse this settings works perfectly!
Sometimes charging settings some roms applied after reboot the phone. My phone on Chrisleko Rom V4, and it works perfectly without restartat the phone. (the charge control menu not a voltage settings)
Click to expand...
Click to collapse
Yes it works now ..what about AC main input current how to control it ? Will new features be added ?

synapse not work in screen setting in cpu and io it works i use trickster mod and its work when enabledmaster sequence or register hook

Cortexbrain script should be great. found this piece of information from dorimanx weblog,
This script will manipulate all the system / cpu / battery behavior. Based on chosen EXTWEAKS profile+tweaks and based on SCREEN ON/OFF state.
When User select battery/default profile all tuning will be toward battery save! But user loose performance -20% and get more stable system and more battery left.
When user select performance profile, tuning will be to max performance on screen ON!
When screen OFF all tuning switched to max power saving! as with battery profile, so user gets max performance and max battery save but only on screen OFF.
This script change governors and tuning for them on the fly!
Also switch on/off hotplug CPU core based on screen on/off.
This script reset battery stats when battery is 100% charged.
This script tune Network and System VM settings and ROM settings tuning.
This script changing default MOUNT options and I/O tweaks for all flash disks and ZRAM.
Click to expand...
Click to collapse

Flashed, need a couple of days testing, but at glance that is impressed
Sent from my SM-N900 using Tapatalk

Cortexbrain script functions from Dorimanx SGSII kernel with auto screen on/off module
Click to expand...
Click to collapse
You bring the best from Dorimanx kernel!!!

Synapse can't work ,FC everytime

who can recommend / advise the settings which will increase the battery life?
may be there is any instruction with examples?
thank you in advance!

Coffee
.
Hi halaszk,
Thanks for you work.
I have sent you a coffee over paypal. Confirmation number: 1C413099LN2241531
Keep up your work. Thanks again.

Sview Cover
Hi halaszk,
Everything working properly and I can UV more than other kernels. Stability is perfect.
Features you add are perfect too.
I wanna ask about two thing,
1. My Sview Cover does not work. This was happen on hannry kernel 2.0A before and solved on 3.0A. Also it is working on pekaka kernel.
2. could you put sched_mc control on synapse.
Thanks for your effort and knowledge.

No uci support detected

alleshi said:
No uci support detected
Click to expand...
Click to collapse
After a reboot it worked for me.

First of all thank you halaszk for the best kernel for our note 3. Cheers and keep up the work. Just a little confusion. On set cpu n cpu spy the min frequency is 100mhz (the whole frequency table is different than the one in synapse) I'm a little confused due to this. Can somebody explain?
kadiremrah said:
Hi halaszk,
Everything working properly and I can UV more than other kernels. Stability is perfect.
Features you add are perfect too.
I wanna ask about two thing,
1. My Sview Cover does not work. This was happen on hannry kernel 2.0A before and solved on 3.0A. Also it is working on pekaka kernel.
2. could you put sched_mc control on synapse.
Thanks for your effort and knowledge.
Click to expand...
Click to collapse
Can you post your voltages pls. Thank you

Tips To Increase Battery backup and Life

To get better battery backup
Turn off WiFi and Bluetooth Scanning in Location Sevices...

You can save 10% straight by ​turning off Location​ and ​turning off Background Data on Google Play Services​

If u rooted ur phone and then
1.. install Greenify
2.. Add Background Running App (User App And Some System App "CAUTION")
2.. Flash Xposed Framework
3.. Enable Doze On the Go

I add 2 liitle root tips around doze (iam not Big fan of greenify)
MM doze is quite bad, improve it, inactive_to Will enable doze after 10 min (30 min default with mm and nougat), sensors wont prevent doze anymore :
adb shell settings put global device_idle_constants inactive_to=600000,sensing_to=0,locating_to=0,location_accuracy=20.0,motion_inactive_to=0,idle_after_inactive_to=0,idle_pending_to=120000,max_idle_pending_to=120000,idle_pending_factor=2.0,idle_to=1800000,max_idle_to=21600000,idle_factor=2.0,min_time_to_alarm=3600000,max_temp_app_whitelist_duration=300000,mms_temp_app_whitelist_duration=60000,sms_temp_app_whitelist_duration=20000
Doze googlePlayServices, by default it can't be dozed :
Go to /system/etc/sysconfig, find the filegoogle.xml and edit it :
<!-- <allow-in-power-save package="com.google.android.gms" /> -->

fablebreton said:
I add 2 liitle root tips around doze (iam not Big fan of greenify)
MM doze is quite bad, improve it, inactive_to Will enable doze after 10 min (30 min default with mm and nougat), sensors wont prevent doze anymore :
adb shell settings put global device_idle_constants inactive_to=600000,sensing_to=0,locating_to=0,location_accuracy=20.0,motion_inactive_to=0,idle_after_inactive_to=0,idle_pending_to=120000,max_idle_pending_to=120000,idle_pending_factor=2.0,idle_to=1800000,max_idle_to=21600000,idle_factor=2.0,min_time_to_alarm=3600000,max_temp_app_whitelist_duration=300000,mms_temp_app_whitelist_duration=60000,sms_temp_app_whitelist_duration=20000
Doze googlePlayServices, by default it can't be dozed :
Go to /system/etc/sysconfig, find the filegoogle.xml and edit it :
<!-- <allow-in-power-save package="com.google.android.gms" /> -->
Click to expand...
Click to collapse
Great it's Working

For me Gov Tuner Project is number one in saving battery, especially with agressive doze.

u can also install gravitybox and enable smart network from there.i have option to have 3g (or 4g) ONLY when i have enabled data.When i turn off data,it automatically mode goes to only 2g for battery and lower radiation.there is also an option to dissable data when screen is off.there is also a widget for smart radio.

My battery life with Jio VoLTE

I advise Leandroid, available on the Play Store here.
It allow to switch 4G to 2G without internet data when the screen goes off, re-activate it during 1 minute every 60 minutes so as to sync your stuffs.
possibility to not reactivate 4G and data as long as device is not unlocked, so you can read the time or check notifications without unintentionally re-activating the connections.

Battery Temperature reaches to 45% During charging through Turbo Charger...
Plz help??

this is normal.in order to have longer battery life..(the heat is the reason that reduces battery life and not the quickcharger) I always put it the ground and it is cooling very much and my battery will live longer.

use squid kernel nd glassfish 1.2 script,dere ll b no heating problms aftr dat nd u ll get a great battery life
6.30-7.30 SOT

ayepandey said:
Battery Temperature reaches to 45% During charging through Turbo Charger...
Plz help??
Click to expand...
Click to collapse
Are you on Stock or Custom ROM?
Custom ROMS usually have lots of problems with thermal control.

rohitpaul9000 said:
use squid kernel nd glassfish 1.2 script,dere ll b no heating problms aftr dat nd u ll get a great battery life
6.30-7.30 SOT
Click to expand...
Click to collapse
What about lags?
I often avoid to use that type of mods because I'm afraid of lags. With Optimus Kernel and optimus governor I reach 6h~ SoT with no lags at all...

nplezka said:
What about lags?
I often avoid to use that type of mods because I'm afraid of lags. With Optimus Kernel and optimus governor I reach 6h~ SoT with no lags at all...
Click to expand...
Click to collapse
Started using FairPark script as i want to balance between life and performance. No lags so far and we will see how the battery performs

SOT With 3 Reboot
Sent from my XT1562 using Tapatalk

ayepandey said:
SOT With 3 RebootView attachment 4166637
Sent from my XT1562 using Tapatalk
Click to expand...
Click to collapse
Some information would be quite useful...

ayepandey said:
Battery Temperature reaches to 45% During charging through Turbo Charger...
Plz help??
Click to expand...
Click to collapse
If you have set the Phone to sync Photos, Update apps, download mails, or youtube offline content, then there is a chance.
In my case normal temp is mostly 35 Degrees indoors.
Pls try to keep the Battery Side Up, and Fan a/c running while charging...
I am sure being a pro, you might have already tried all these.:good:
Pls try charging with a Normal Motorola 1100 mAH charger as well

[APP][ROOT][4.0+]Battery Charge Limit v1.1.1

Please read the following before installing the app:
This app requires a rooted mobile (Android 4.0 or later)
Before uninstalling the app, disable limit in the app (if forgotten, reboot after uninstalling)
Usage instructions and app details:
Enable limit in the app
Change the limit up to which it should charge (default: 80)
Check which control file suits best for your device, see Q/A section below for hints. In most cases, the pre-selected choice should be the best that's available for your device.
The app only gets kicked in while you connect a charger (or USB), and automatically closes shortly after unplugging charger (or USB) i.e it only runs in the background as long as it is plugged in, and won't affect your battery life.
If your device is not charging even after disabling the limit (which shouldn't happen, just in case), uninstall the app and reboot the device (The changes made by the app don't survive a reboot). Your device should charge normally then.
If the app says "your device is not yet supported"
There are various control files in different devices (due to OEMs), and toggling the values in them (0 and 1) makes it possible to enable and disable charging via software (might not be possible for every device), though the charging cable is still physically connected.
Since we cannot own every device, it is impossible for us to find every file. We can support a lot more devices with information provided by testing possible files on different devices by you, the people in the community.
Hence, for support to be provided to other devices, you need to do some detective work to find the files on the respective devices. Please refer to this file for control files of currently supported devices, so you can know where they are generally present: https://github.com/sriharshaarangi/BatteryChargeLimit/blob/master/app/src/main/res/raw/control_files.json
You can send us a pull request or open an issue on GitHub. If necessary, you can also post the name of the device and the file here.
FAQ
Q) Can you please add support for... (insert arbitrary device name here)?
A) Maybe, but we need your help. Bottom line, this app does nothing but modifying the content of a certain "control file", some more details are given above. If you find such a control file for your device, please let us know (ideally, open a GitHub issue here: https://github.com/sriharshaarangi/BatteryChargeLimit/issues) and we will add support for your device.
Q) I think I observed a bug. Can you fix it?
A) We'll do our best, but we need your help: Please open an issue on GitHub (https://github.com/sriharshaarangi/BatteryChargeLimit/issues) and provide as much information as possible about the problem.
In most cases, we need the "logcat" logs of your device to find out about the exact issue. In order to provide those, you could use aLogcat (https://play.google.com/store/apps/details?id=rs.pedjaapps.alogcatroot.app).
FOR CHARGING-RELATED ISSUES: Select the "Time" format in the preferences of aLogcat, so we can see precise timings, and filter for "(Charging|Power) State" with "Apply as regular expression" ticked.
FOR CRASHES: Please also select the "Time" format and provide unfiltered logcat data that includes the stack trace of the crash.
Q) Why do you want to limit charge to a lower capacity?
A) In short, to prolong battery life in long term usage. For more information, refer this : http://batteryuniversity.com/learn/article/how_to_prolong_lithium_based_batteries
Q) How does this app work? Does it modify something in the ROM/Kernel to stop charging?
A) It writes "0" or "1" to a control file that represents some state of the power supply hardware, as simple as that. The file is normally read-only, so you need root to overwrite it.
The change might be automatically reversed by the OS if the power supply situation changes. Anyway, it should never survive a reboot of the device.
Q) I can select multiple more than one control file in the radio group. Which one should I use?
A) For most devices, battery_charging_enabled or store_mode are preferable. Try those first and see if it works. If you observe any bugs, try another file.
Q) I have a OnePlus device, and the app doesn't work correctly for me. What to do?
A) Check that the control file you selected is NOT battery_charging_enabled! Although it should be preferred in general, there are known issues for this file with OnePlus devices.
Q) I use the store_mode on a Samsung device. My device always stops charging at 70 % (or other specific percentage), no matter what limit I have set.
A) The store_mode implementation differs among the supported (Samsung) devices.
Normally, it freezes the level at the current percentage when store_mode is triggered until the cable is unplugged for some seconds. This is a normal condition due to Samsung's kernel implementation, it's not a bug of this app.
If this is a problem for you, try to switch to another control file (e.g. batt_slate_mode), if supported.
Q) How does the "automatic stats reset" work?
A) The automatic reset should perform a stats reset when your power supply is removed while the battery level is within the desired range. Everything else is wrong behavior.
Q) No matter if I the "automatic stats reset" is enabled or not, my phone is always resetting my battery statistics. Why?
A) Are you using a threshold above 90%? If yes, your ROM will most likely clear the stats when the power is removed. There is nothing we can do about that.
Downloads:
The app is available on Google Play Store
Alternate APK download links:
v1.1.1: https://www.androidfilehost.com/?fid=674106145207486851
v1.1.0: https://www.androidfilehost.com/?fid=817906626617956614
v1.0.4: https://www.androidfilehost.com/?fid=889764386195927297
v1.0.3: https://www.androidfilehost.com/?fid=745425885120755941
v1.0.2: https://www.androidfilehost.com/?fid=889764386195923345
v1.0.1: https://www.androidfilehost.com/?fid=889764386195919111
v1.0.0: https://www.androidfilehost.com/?fid=817550096634789023
v0.11.0: https://www.androidfilehost.com/?fid=961840155545580765
v0.10.0: https://www.androidfilehost.com/?fid=961840155545576298
v0.9.2: https://www.androidfilehost.com/?fid=457095661767160082
v0.8.2: https://www.androidfilehost.com/?fid=673368273298951679
Please uninstall versions < 0.8 before installing this!
Changelog:
1.1.1:
Fix charging status layout issues and misc UI fixes @xdnax
Added switch to disable toasts on service changes @xdnax
Added switch to show temperature in notification @xdnax
Ensuring write permissions on the charging control file @real_milux
Fixed notification sound on limit reach @sriharshaarangi
Fixed a bug causing crash
Added Russian translation
Updated Bengali, German and Brazilian Portuguese translations
Added control file for Amazon Tate (LineageOS 14.1)
1.1.0:
UI & icon redesign @xdnax
Custom control file data support @xdnax
Improved control file lists @real_milux
ICS (Android 4.0, API 14) compatibility @real_milux
Pixel/Pixel 2 support fixes @xdnax
Added control files for Pixel/Pixel 2, Xiaomi Redmi Note 2, Sony XPERIA Mini, Le 1s, Huawei P10 lite, HTC One, Motorola Defy+, Xiaomi Mi A1
Bengali translation @AdroitAdorKhan
Spanish translation @Joseahfer
Lots of bugfixes and minor improvements
1.0.4:
New "always write" setting for devices that modify their control files in a problematic way
Experimental support for Xiaomi MiPad 2, Nexus 5, Nexus 9, Galaxy Nexus (maguro) and Xiaomi Mi6
1.0.3:
Fixed service starting after boot when disabled
1.0.2:
Fixed ignoring "ACTION_POWER_CONNECTED" when service was disabled
Experimental support for Nexus 10, Nvidia Shield and Xiaomi Mi6
1.0.1:
Added preference to disable limit enforcement aka "state fixing"
Added expert preference to enable immediate reaction to power state events (be careful!)
1.0.0:
Tested Magisk 13.x support
Improved UI
Even higher service priority (against being killed by Android)
Online limit change support (limit changeable while service is active)
Settings with control file selection and temperature scale
Fahrenheit temperature info support
Greatly improved "state fixing" with exponentially increasing delay (hopefully fixing GitHub issue #15 aka "rapid cycling")
Greatly improved SU shell speed/performance
German translation
0.11.0:
Improved UI (Using NumberPickers, GitHub issue #13)
Show voltage and temperature in app and notification (GitHub issue #14)
0.10.0:
The recharge threshold can now be customized between 0 and the chosen charging limit
Sending a charging limit of 100 via (broadcast) intent will disable the service.
Sending values between 40 and 99 will enable and start the service if it was previously disabled.
0.9.2:
Fixed crash on some devices that are unrooted or unsupported
0.9.1:
Fixed widget not showing in some devices
0.9:
Added Widget to toggle service
Added scrollable view
0.8.2:
experimental Amazon Fire support
0.8.1:
Bugfixes
0.8:
State check after boot (starting monitoring service as necessary)
Bugfixes
0.7:
Experimental support for Huawei and Nexus 4 devices
Support for external control over charging limit
Bug fixes
0.5
Ability to select recharge limit (Range: 10%)
Automatic file selection
Added store_mode for Samsung devices
Added option to auto reset stats
(Huge code refactoring)
0.3
Updated to support 7.1.1
Auto-select the battery charging file for Samsung, Pixel and Nexus devices
Added clear battery stats button
Auto-whitelisting from Doze mode
XDA:DevDB Information
Battery Charge Limit, App for all devices (see above for details)
Contributors
harsha1397, real_milux
Source Code: https://github.com/sriharshaarangi/BatteryChargeLimit
Version Information
Status: Stable
Current Stable Version: 1.1.1
Stable Release Date: 2018-10-17
Current Beta Version: 1.0.4
Beta Release Date: 2017-09-04
Created 2017-02-15
Last Updated 2020-08-05

Todo:
- Check for charging on device boot
- Widget for quick toggle
- Widget to reset batterystats
- Limit reached alert
- Low battery alert - Needs a service running in the background
- UI overhaul
- on/off switch to enable/disable charging

I can't believe it. You can't imagine how long I was looking for such an app .
Will try it!

I remember this was a feature that some kernels had years ago, and I would limit the charge to 85%. On my laptop I can cap it to 60%, which is great because I leave the charger in often.
Anyway, thank you for making this app!

Freezy202 said:
I can't believe it. You can't imagine how long I was looking for such an app .
Will try it!
Click to expand...
Click to collapse
Ace42 said:
I remember this was a feature that some kernels had years ago, and I would limit the charge to 85%. On my laptop I can cap it to 60%, which is great because I leave the charger in often.
Anyway, thank you for making this app!
Click to expand...
Click to collapse
Did you get a chance to test it? Is it working as expected?

harsha1397 said:
Did you get a chance to test it? Is it working as expected?
Click to expand...
Click to collapse
Unfortunately it does not work as it should :/. It doesn't really limit. Even when I unplug the notification doesn't go away as you mentioned.
I have a HTC One M8, android 6.

Freezy202 said:
Unfortunately it does not work as it should :/. It doesn't really limit. Even when I unplug the notification doesn't go away as you mentioned.
I have a HTC One M8, android 6.
Click to expand...
Click to collapse
Does the battery percentage continue to rise beyond the limit? Regarding notification, it doesn't immediately go away after unplugging. It goes away after the percentage drops 3% below the limit. It is to ensure that the phone again charges to the limit if the phone is still plugged in. If it is not plugged in, then notification closes.

very good idea, thanks for app, was looking for app like this for a long time will report in half hour if app works

thanks!I always was searching such an app cause:
1)I read if u charge your battery till 80% it will last more time..
2)At the end of the day,I always have 40% battery left and I cant trust my phone for the next day without charge.
Thanks again It works on my moto x play!It stopped at 79% but its ok not such a big deal!

ok, so it worked, but first time, when i unpluged and pluged app didn't noticed pluging and continued charging. after that i tried several times and it worked again. so there should be somewhere bug in monitoring pluging charger sometimes is left unnoticed.
Sent from my ONE A2005 using Tapatalk

harsha1397 said:
Did you get a chance to test it? Is it working as expected?
Click to expand...
Click to collapse
Seems to work on my LeEco Pro 3. Charging icon switched to normal battery at 80%.

This is what I have been looking for!
Thank you for the app!
I tried it and its stop charging after 95% ?
Im on xperia z5 Nougat.
But the notification doesnt go away when I unplug the charger's cable from the phone.
Turning off the app but did make the notification disappear.
Another question.
Does it really stop the charger from giving electricity to our phone?
Or does it only change the charging status?
Im scared that the app tells that it stopped charging, but the electricity is still going on.
Gesendet von meinem E6653 mit Tapatalk

Can somebody explain to me, why someone would want to limit the charging current?

chitose_ndy said:
This is what I have been looking for!
Thank you for the app!
I tried it and its stop charging after 95%
Im on xperia z5 Nougat.
But the notification doesnt go away when I unplug the charger's cable from the phone.
Turning off the app but did make the notification disappear.
Another question.
Does it really stop the charger from giving electricity to our phone?
Or does it only change the charging status?
Im scared that the app tells that it stopped charging, but the electricity is still going on.
Gesendet von meinem E6653 mit Tapatalk
Click to expand...
Click to collapse
1. Regarding notification, (I have updated the OP as well):
The app only gets kicked in while you connect a charger (or USB), and automatically closes shortly after unplugging (not immediate, it closes after percentage drops more than 3% below the limit because the app doesn't know whether the cable is physically connected or not, since we disable charging at the limit. So, after it drops below 3% and (a)the charger is still connected, it charges again to the limit, and (b)if it is disconnected, then the notification closes) .
So, it is not a bug.
2. Does it really stop the charger from giving electricity to our phone?
It actually stops charging at the limit. It is in the same way any phone automatically stops charging when the battery reaches 100% capacity.

Freddy1X said:
Can somebody explain to me, why someone would want to limit the charging current?
Click to expand...
Click to collapse
tl;dr : To prolong battery life in long term
For more information: http://batteryuniversity.com/learn/article/how_to_prolong_lithium_based_batteries

harsha1397 said:
Does the battery percentage continue to rise beyond the limit? Regarding notification, it doesn't immediately go away after unplugging. It goes away after the percentage drops 3% below the limit. It is to ensure that the phone again charges to the limit if the phone is still plugged in. If it is not plugged in, then notification closes.
Click to expand...
Click to collapse
Exactly. It continues to charge.

Freezy202 said:
Exactly. It continues to charge.
Click to expand...
Click to collapse
Weird. Seems to work on other devices.

harsha1397 said:
Weird. Seems to work on other devices.
Click to expand...
Click to collapse
Is it possible that some kernels aren't compatible with this, or even certain SoCs? I have a Kindle Fire with a mediatek, so I'll test the app on there later.

harsha1397 said:
Weird. Seems to work on other devices.
Click to expand...
Click to collapse
Maybe I'll try another kernel. Anyway I wanted to change my rom . Actually it's always the other way around. Other people have Bugs except me, this time I have no luck haha.

Ace42 said:
Is it possible that some kernels aren't compatible with this, or even certain SoCs? I have a Kindle Fire with a mediatek, so I'll test the app on there later.
Click to expand...
Click to collapse
I don't know the reason(I don't think this is kernel dependent), but this file is the key: /sys/class/power_supply/battery/charging_enabled
It should be 1 by default. And when it reaches the limit, the value is made 0 by the app.