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] [April 21] Bulletproof

[KERNEL] [April 21] Bulletproof
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Bulletproof Kernel
for Google Play Edition and Sense-based ROMs​
This version works on every HTC One variant except Sprint and Verizon
The Sprint HTC One version is here: http://forum.xda-developers.com/showthread.php?t=2280576
Bulletproof is an enhanced stock kernel for those who depend on their phone and need 100% stability.  It is highly optimized for smooth performance and extended battery life.  Enhancements include several sleep/wake options (S2W, DT2W, L2W), pocket detection to prevent accidental wakes, full compatibility with paid apps, button light notification, 60Hz refresh rate for HDMI, HTC logo as menu button, support for many gamepads and more.
Click to expand...
Click to collapse
Code:
* Standard disclaimer:
* Your warranty is now void.  Use at your own risk.
* In other words: It is your choice to use this software,
* I am not responsible for any damage or problems!
FEATURES:
Aroma installer
sweep2wake
doubletap2wake
logo2menu
logo2wake
pocket detection
optimized for battery life
button light notification
/system writable
NTFS r/w support
exFAT support
faux123 sound control support
CIFS support
USB forece fastcharge
/dev/frandom
voltage control
intellidemand governor
FIOPS and SIO i/o schedulers
fix MHL refresh rate
maintains compatibility with all paid apps
support more game controllers
optimized -O3 Linaro 4.7.3
Please hit the Thanks button if you download this
If you really like it, please consider a donation to encourage continued developement
Thanks to those who have donated!
DOWNLOAD
HTC Sense 5.5 & Sense 6 Android 4.4.2
Bulletproof-m7-14.2
Google Play Edition Android 4.4.2
Bulletproof-m7-11.0
HTC Sense 5.5 Android 4.4
Bulletproof-m7-10.3
Google Play Edition Android 4.4
Bulletproof-m7-9.1
HTC Sense 5.5 Android 4.3
Bulletproof-m7-8.1
HTC Sense 5 Android 4.3
Bulletproof-m7-6.2
Google Play Edition Android 4.3
Bulletproof-m7-5.3
HTC Sense 5 or Google Play Edition Android 4.2.2
Bulletproof-m7-4.4
HTC Sense 5 Android 4.1.2
Bulletproof-m7-2.1
For more options and tweaking, try my other kernel: ElementalX
INSTALLATION
1. Install zip from Recovery
2. Reboot!
For installation, it seems a lot of people have finicky phones when it comes to flashing stuff with aroma.
If the installer gets stuck at 0% then you need to reboot to bootloader and do fastboot erase cache
If the installer reboots at 10%, you need to do a nandroid backup of /system partition and restore it. I think a dirty flash would also work.
After you install it, if you get a black screen or stuck at the HTC logo, no need to worry. Just hold down the power button untill the capacitive buttons start flashing and the phone restarts. The kernel installed correctly.
Previous releases:
Bulletproof-m7-14.1
Bulletproof-m7-13.0
Bulletproof-m7-9.0.3-GPE
Bulletproof-m7-10.2
Bulletproof-m7-10.1
Bulletproof-m7-10.0
Bulletproof-m7-8.0
Bulletproof-m7-7.0.1
Bulletproof-m7-7.0
Bulletproof-m7-6.1
Bulletproof-m7-6.0
Bulletproof-m7-4.3
Bulletproof-m7-4.2
Bulletproof-m7-4.1
Bulletproof-m7-4.0
Bulletproof-m7-3.4
Bulletproof-m7-3.2
Bulletproof-m7-3.1
Bulletproof-m7-2.0
Bulletproof-m7-1.10
Bulletproof-m7-1.9
Bulletproof-m7-1.8
Bulletproof-m7-1.7.1
Bulletproof-m7-1.6
Bulletproof-m7-1.5
Bulletproof-m7-1.4
Bulletproof-m7-1.3
Bulletproof-m7-1.2
Bulletproof-m7-1.1
Bulletproof-m7-1.0
Bulletproof-m7-0.5
Bulletproof-m7-0.4
Bulletproof-m7-0.3.1
Bulletproof-m7-0.2
Bulletproof-m7-0.1
Credits and Thanks:
@tbalden:  logo2menu, bln, camera fix on sense 4.3
@mkasick: Fix for empty app-mounted directories
@deagleone:  awesome bulletproof logo
NOTES
Kernel Tuner/TricksterMod/Venom Tweaks, etc
You don't need these apps because the Bulletproof installer sets everything up automatically, but if you want to check or change settings, you can use these apps. Just be aware that some of them (e.g. Kernel Tuner) are set by default to apply settings on boot, which can interfere with the settings you chose in the Bulletproof installer.
init.d script template
The installer automatically adds an init.d script template so you can apply settings automatically at boot. It is not needed and does nothing by default, but you can use it to fine tune some settings if you like.
The script is named /etc/init.d/99bulletproof.  This is where you would set the button_timeout if you don't like the default settings.  There are other example settings in the file related to sweep2wake, doubletap2wake, logo2wake, pocket detection, logo2menu, button light notification, USB fastcharge, HTC color enhancement
To make settings apply automatically at boot, remove the # in front of the desired setting and change the setting, eg: removing the # in front of echo 0 > /sys/android_touch/button_timeout would disable that setting
If you edit the file, make sure it has execute permissions, or it won't apply. You can do this with ES File Explorer or other similar apps
Sweep2Wake
Sweep2wake (S2W) allows you to wake up your device by swiping your finger across the capacitive buttons from left to right. Swiping from right to left will put it back to sleep (sweep2sleep). The options are: sweep2wake/sweep2sleep, sweep2sleep only, and disabled. If you use apps such as Kernel Tuner, the sweep2sleep only option can be selected by choosing "On with backlight".  
/sys/android_touch/sweep2wake
0=disabled
1=enable sweep2wake + sweep2sleep
2=enable sweep2sleep only
Sweep2wake button timeout
In earlier versions, sweeping to sleep brought you back to the homescreen. Starting in version 4.3, if you swipe fast enough, it will not register a home button press in the sweep, and your last app will be there when you unlock the phone again. Depending on how quick your fingers are, double tapping home could put the phone to sleep instead of opening recent apps. I've made the default button_timeout such that it is almost impossible for this to happen in normal use (button_timeout = 6). If you find that it happens too often, you can set button_timeout to a lower number, or disable it completely by setting it to 0.
/sys/android_touch/button_timeout
Accepted values are 0 to 15. 0 disables button timeout
• Higher values make it more likely that your last app will be open after you sweep to sleep, but there is a higher risk of accidentally putting the device to sleep when double tapping home.
• Lower values make it less likely that your last app will be open after you sweep to sleep, but reduces the chance of a double tap of home being mistaken for a sweep2sleep.
• Setting button_timeout to 0 disables this feature completely
The setting can be changed after installation in /etc/init.d/99bulletproof
DoubleTap2Wake
DoubleTap2Wake (DT2W) allows you to wake the device by double tapping in the bottom inch or so of the screen, above the capacitive buttons.  
/sys/android_touch/doubletap2wake
0=disabled
1=enable doubletap2wake
Logo2Wake
Logo2Wake (L2W) allows you to sleep or wake the device by long pressing the HTC logo. You have to press just slightly above the HTC logo.  The screen will automatically turn on or off with a long press.
/sys/android_touch/logo2wake
0=disabled
1=enable logo2wake
Pocket Detection
Pocket detection protects against accidental wakes while S2W, DT2W or L2W are enabled and the phone is in your pocket.  Pocket detection uses the proximity sensor.  A few people have a problem with their proximity sensor that makes DT2W not work, so I've made an option to disable pocket detection.
/sys/android_touch/pocket_detect
0=disabled
1=enable pocket detection
Logo2Menu
Enabling Logot2Menu (L2M) allows you to use the HTC logo as a menu button.  You must press just slightly above the HTC logo.
/sys/android_touch/logo2menu
0=disabled
1=enable logo2menu
Button Light Notification
With Button Light Notification (BLN), the capacitive buttons will blink on and off when you have a new notification.  As soon as the screen comes on, BLN is canceled and the lights will no longer blink until you have another notification.  Please note that if you have your screen set to turn on when a message arrives, you will not see the buttons blinking because once the screen comes on, the button light notification is canceled.  
/sys/class/leds/button-backlight/blink_buttons
0 = disabled
1 = BLN enabled
CPU voltages
CPU voltages are fully customisable with apps such Kernel Tuner or Trickster Mod.  Be careful, lowering voltages can cause instability. Generally, having reboots while the phone is asleep is a sign that your minimum voltage is too low. The minimum voltage allowed is 700mV.
Be careful with undervolting. If you have bluetooth or sound issues, try increasing the minimum voltage.
Camera
On 4.2.2 ROMs, using HDR mode in low light with automatic flash may freeze the camera app.
NTFS support
This is for anyone who wants to use OTG to connect a USB stick or portable harddrive formatted with Microsoft's NTFS filesystem. You will need Stickmount or a similar app, HTC Sense does not automatically detect NTFS filesystem.
Paid Apps
All the cryptographic modules load properly, so you shouldn't have an issues with paid apps.
Other stuff
This kernel supports many game pads and controllers, including PS3 controllers and some X-Box controllers.  It has full OTG support.  A refresh rate of 60Hz for HDMI output allows you to play games on the big screen without choppiness.  CIFS support is built into the kernel.  Faux sound control is also supported.
Click to expand...
Click to collapse
​
CHANGELOG:
December 15, 2013 - Bulletproof-11.0
-update for Google Play Edition Android 4.4.2
-add multiboot support
-remove 3-dot menubar option
December 14, 2013 - Bulletproof-10.3
-restrict doubletap2wake to bottom half of screen
-update installer
December 14, 2013 - Bulletproof-9.1
-restrict doubletap2wake to bottom half of screen
-update installer
-battery saving tweaks
December 7, 2013 - Bulletproof-10.2
-remove doubletap2sleep
-battery saving tweaks
December 4, 2013 - Bulletproof-10.1
-fix bln setting
-add doubletap2sleep
-restrict doubletap2wake to bottom half of screen
December 1, 2013 - Bulletproof-10.0
-update for Sense 5.5 Android 4.4
December 1, 2013 - Bulletproof-9.0.3
-remove "remove 3-dot menubar" option
November 27, 2013 - Bulletproof-9.0.2
-fix module installation
November 27, 2013 - Bulletproof-9.0.1
-remove "restore 3-dot menubar" option
November 26, 2013 - Bulletproof-9.0
-update with HTC Google Play Edition source code
November 24, 2013 - Bulletproof-8.1
-fix pocket detection
-fiops is default scheduler
November 23, 2013 - Bulletproof-8.0
-update with HTC source code
-adjust touch wake functions
-restore stock camera app and libs
October 21, 2013 - Bulletproof-7.0.1
-update camera apk
October 14, 2013 - Bulletproof-7.0
-fix camera (thanks tbalden)
-update ramdisk for Sense 5.5
September 14, 2013 - Bulletproof-6.2
-free up more RAM
-camera fix for 3.17 base (thanks @tbalden)
-updated ramdisk to 3.17 version
September 9, 2013 - Bulletproof-6.1
-AIO: Don't plug the I/O queue in do_io_submit()
-fsync switch (on by default)
-update installer
September 8, 2013 - Bulletproof-6.0
-support sense android 4.3
September 3, 2013 - Bulletproof-4.4
-update with 4.2.2 Sense source
-update modules
-adjust Makefiles
-fix logo2wake bug
-add exfat support
August 12, 2013 - Bulletproof-5.3
-adjust build options
-fix logo2wake active after finger leaves logo area
August 10, 2013 - Bulletproof-5.2
-adjust build options
August 10, 2013 - Bulletproof-5.1
-remove log spam
August 9, 2013 - Bulletproof-5.0
-update to GE 4.3 source
-update installer
July 25, 2013 - Bulletproof-4.3
sweep2wake fixes
-doubletap2wake adjustments
-Makefile optimizations
-install-recovery.sh command added to ramdisk
-updated modules
-updated installer
-add init.d script template
July 22, 2013 - Bulletproof-4.2
-add option to enable fastcharge automatically
-fix sweep2wake bugs
July 21, 2013 - Bulletproof-4.1
-installer fixes
-new logo (thanks @deagleone)
-linaro 4.8.1 O3 build
July 20, 2013 - Bulletproof-4.0
-use Google Android toolchain 4.6
-update installer options
-fix sweep2wake bugs
-fix for home button options (if not using logo2menu)
-add ability to restore 3-dot menu
-fix capacitive buttons sometimes still active while screen off
July 11, 2013 - Bulletproof-3.4
-fix touchscreen registering input during calls
-add TCP congestion algorithm options
-fix fastcharge (@tbalden)
-vibration feedback for s2w
-add sysfs config for sleep/wake vibration strength
-change lower voltage limit to 700mV
June 30, 2013 - Bulletproof-3.2
-fix BLN setting not applied
-update BLN
-fix for app-mounted directories (thanks @mkasick)
June 29, 2013 - Bulletproof-3.1
-add support for Android 4.2.2
-update aroma installer
June 23, 2013 - Bulletproof-2.1
-adjust doubletap2wake
-tweak hsic
June 20, 2013 - Bulletproof-2.0
-update to latest HTC sources (still 4.1.2!)
-updated camera (works with .16 base ROMs)
-updated capacitive button sensitivity
-revert earpiece audio patch
-remove camera fix
-adjust doubletap2wake sensitivity
-pocket detection only active when screen off
May 22, 2013 - Bulletproof-1.10
-make camera fix optional
-wifi as module
-revert arm rwsem algorithm
-adjustments and fixes to sweep/wake options
May 14, 2013 - Bulletproof-1.9
-add option to disable pocket detection
-add new settings schema for sleep/wake functions
-fix bug dt2w not working when s2w disabled
-change l2w to automatically sleep/wake after pressed for a certain time
May 12, 2013 - Bulletproof-1.8
-suppress accidental wakes with s2w and dt2w
-fix dt2w setting not sticking
-add button light notification @tbalden)
May 10, 2013 - Bulletproof-1.7.1
-fix for camera on .16 based ROMs (thanks to he_stheone64)
May 5, 2013 - Bulletproof-1.7
-add DoubleTap2Wake
-update faux sound control support
-add option to disable menubar
-minor fixes
May 1, 2013 - Bulletproof-1.6
-add vibration to logo2wake (tbalden)
-fix hsic wakelock
-faux123 sound control (faux123)
-update to latest HTC sources
-optimized arm rwsem algorithm
-optimized AES and SHA1 routines
-disable usb whitelist
-fix fastcharge
April 28, 2013 - Bulletproof-1.5
-add logo2wake
April 26, 2013 - Bulletproof-1.4
-add logo2menu (thanks tbalden)
-adjust sweep2wake
-add aroma options
April 25, 2013 - Bulletproof-1.3
-voltage control
-camera fix included
-added /dev/frandom
-glibc memcpy
April 22, 2013 - Bulletproof-1.2
-new implementation of sweep2wake
-CIFS fix (thanks tbalden)
April 21, 2013 - Bulletproof-1.1
-Fixed  moc_crypto loading (kernel name is same as stock:  3.4.10-g42e6c45)
April 21, 2013 - Bulletproof-1.0
-fix earpiece sound in calls (many thanks to tbalden!)
April 16, 2013 - Bulletproof-0.5
-adjust sweep2wake
-force fastcharge (untested: use at your own risk)
-re-enable perflock
April 16, 2013 - Bulletproof-0.4
-adjust sweep2wake
April 16, 2013 - Bulletproof-0.3.1
-adjust boot.img
April 16, 2013 - Bulletproof-0.3
-add sweep2wake
-wifi driver built-in
April 15, 2013 - Bulletproof-0.2
-disable perflock
-arm cpu topology
-update cpu_power according to cpu load
-mhl change to [email protected]
-add CIFS support
-add FIOPS and SIO i/o schedulers
-update ramdisk
April 13, 2013 - Bulletproof-0.1
-compiled -O3 with Linaro 4.7.3
-aroma installer
-based on HTC source code 1.28
-intellidemand governor
-init.d support
-ntfs r/w support
-xz kernel compression
-disable system write protection
-adjust readahead to 2048
-fast rcu nohz
Click to expand...
Click to collapse
Source:
Bulletproof-m7 (Android 4.2.2)
Bulletproof-m7 (GPE Android 4.3)
Bulletproof-m7 (Sense 5.5 Android 4.3)
Bulletproof-m7 (GPE Android 4.4)
XDA:DevDB Information
Bulletproof | S2W | L2M | DT2W | BLN , a Kernel for the HTC One
Contributors
flar2
Kernel Special Features:
Version Information
Status: Stable
Current Stable Version: 14.2
Stable Release Date: 2014-04-21
Created 2013-07-30
Last Updated 2014-04-22

Reserved

sweep2wake demo
logo2wake and logo2menu demo

Hope someone can test this on 1.28, be cool to have a intellidemand governor.

works this on 1.29?
sent from my HTC One powered by TrickDroid

Hopie said:
works this on 1.29?
sent from my HTC One powered by TrickDroid
Click to expand...
Click to collapse
It will work, except for the problem with sound in phone calls. I'm waiting for someone to post logs so I can see if it is possible to fix.

It wont install via recovery.
Get error code 7.

Nekromantik said:
It wont install via recovery.
Get error code 7.
Click to expand...
Click to collapse
It does After a reboot look at Setting --> Info --> Software --> Advanced.
I also got error 7, but it worked.

Ok
Here are my files after a phone call. Im on base 1.29 however.
Here is logcat as its too big to host on here.
https://www.dropbox.com/s/v5d2mpfqx00ubd8/logcat.txt

Don´t know why, but I´m not able to set another CPU freq. --> Doesn´t work with SetCPU or SystemTuner.

biohaufen said:
Don´t know why, but I´m not able to set another CPU freq. --> Doesn´t work with SetCPU or SystemTuner.
Click to expand...
Click to collapse
In his changelog he did not state he disabled perflock.

please port these with disabled perflock to 1.29 base

altensalz said:
please port these with disabled perflock to 1.29 base
Click to expand...
Click to collapse
You cannot "port" a kernel.
HTC have to release source code for 1.29 in order for devs to create custom ones.

altensalz said:
please port these with disabled perflock to 1.29 base
Click to expand...
Click to collapse
The point of his bulletproof kernels is to be stockish with some improvements. Besides since its not over clocked disabling perflock is pretty much useless
There's a kernel with perflock disabled already if you want one
Sent from my Nexus 4 using Tapatalk 2

perfect 2 way call recording ???

Besides since its not over clocked disabling perflock is pretty much useless
Click to expand...
Click to collapse
why is usless without overclocking? without preflock you can downclock the frequency and set profiles - both is very usefull

I disabled perflock, but still no overclocking or anything like that.
Let me know if this works.
Download:
Bulletproof-m7-0.2
Changes:
-disable perflock
-arm cpu topology
-update cpu_power according to cpu load
-mhl change to [email protected]
-add CIFS support
-add FIOPS and SIO i/o schedulers
-update ramdisk

Whoops, I forgot to update the wifi module
I added it to the zip just now.
If you want wifi, please re-download and install.

flar2 said:
Whoops, I forgot to update the wifi module
I added it to the zip just now.
If you want wifi, please re-download and install.
Click to expand...
Click to collapse
Still got the issues with calls mate?
If so what logs do you need and when do you need them?

SlimKat weekly 3.6 released

Jenkins is running for new weekly build 3.6. A lot of work has been done to recents and fixing problems. Might not look like much but for more details download the device specific changelog or look at gerrit/github. Have fun.
Changelog
Smart pull down to SlimActions
Notification Remindder new layout and fixes
Allow SlimRecents be closed in the middle of animation
Fix 3rd party recents call on SlimRecennts
Allow IME board alive while SlimRecents is open
Make SlimRecents multiuser compatible
Fix random fc on pinch to close all
Frameworks: go kikat + style tweaks and follow googles color scheme
Smooth spinners
Allow virtual keys to preload recents
SlimRecents call app details correctly
PackageManager: Fix reconnection logic in installer
Massive update from upstream to caf frameworks/av & libhardware
Some Bionic optimizations for cortex-a15
Some fixes to our bluetooth repos
Browser: Various fixes
Smdk4412: updates to touchwake (kernel and device settins)
p31xx & p51xx: Bluetooth changes
Rhine: add radish blobs
Honami: Various optimization to glibc and rwsem to kernel
G2: update power profiles
G2: add usb to ipv6
Mako/Geeb: Readd sl(aou)b updates, zram optimizations, mpdecision/thermald updates and compile with linaro 4.8.
Mako/Geeb: Disable boost pulse and depend on cpu governor, set interactive as default
Update on translations
Various other fixes and optimizations

installed
Installed just there on my I9505.
Upgrade from weekly 3.4 - simple wipe cache/dalvik, format system and installed it and the AIO gapps again.
Came up fine and no issues so far.
Love the Slim..keep up the good work

Battery problem
fozz33 said:
Installed just there on my I9505.
Upgrade from weekly 3.4 - simple wipe cache/dalvik, format system and installed it and the AIO gapps again.
Came up fine and no issues so far.
Love the Slim..keep up the good work
Click to expand...
Click to collapse
Instaled on N 7000
Excelent Rom.. but same problems with battery.
I saw also a lot of people encounter battery problems with this rom: meaning the battery will report to be fully charged and after a some time when the level down to 20-30% the phone not respond or shout down and never up. after connected the charger will say to be 1%. Also when turning off the device, which has its battery completely drained and then gently touching the power button in order to see whether it is charging > it will say the battery is already on 30%... I have tried this with two different batteries...

[DISCONTINUED][KERNEL][6.x/7.x][ULTIMATE™][3.10.104] for Lenovo K3 note

Warnings:-
Code:
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards, dead cats,
* thermonuclear war, or you getting fired because the alarm app failed.
* YOU are choosing to make these modifications, and no point
* in pointing the finger at me for messing up your device
*/
FEATURES
Compiled with UBERTC-6.0.x
Added CPU Governers
->Intellidemand
->ThunderX
->Wheatley
->Alucard
->Interactiveplus
->Elementalx
->Adaptive
->Lionheart
Added I/O Schedulers
->sio
->fiops
->zen
->tripndroid
->vr
->bfq
WiFi Power management control
Wake Gestures
ThunderQuake Engine 1.0 - Vibration Intensity Controller
Add OC 1.9Ghz
CPU Hotplugging
->Thunderplug
->Intelliplug
Dynamic FSync for better performance
F2FS & NTFS support
Selinux set to permissive
Added Advanced new TCP Congestion controls
Lock initial TCP window size to 64k (Improves network ping and output)
Init.d support
Overclock/Underclock
Android Nougat support
INSTALLATION INSTRUCTIONS
Make a BACKUP of boot partition using TWRP just to be on safeside!!.
Flash the zip according to the ROM which you are using.
Note:
1. Wake gestures can be controlled by using this app.
2. All thunder features can be controlled from ThunderZap Control app. Download it from playstore.
3. Use Kernel Adiutor to enable/disable options.
4. I personally recommend to use EX Kernel Manager by flar2.
**SweeptoSleep works only at bottom of screen i.e above navigation bar (Area where you open app drawer).
All thunder stuff can be known at this site.
5. Please use intelliplug driver when frequency transistion doesnt take place in right way.(It may crosses the freqency to max one.)
DOWNLOADS
Non Overclock
Ultimate v1.4.zip
Ultimate v1.3_Vibe.zip
Ultimate v1.3.zip
Overclock
Ultimate v1.4 (OC).zip
Ultimate v1.3 (OC).zip
Ultimate v1.3_Vibe (OC).zip
View attachment 3971231
View attachment 3971230
View attachment Ultimate_v1.1.zip
View attachment Ultimate_v1.0.zip
CHANGELOG
Version 1.4
Few fixes for full Nougat compatibility.
Change the modem default to LWG.
Version 1.3
Enable UID_CPUTIME.
Update GT9XX touch driver(Fix to avoid button touches being recognized as digitizer presses when wakegestures are turned on).
Set Westwood as default TCP Congestion Alogorithm.
Seperated into OC and Non OC flashable zips.(as per user's request).
Version 1.2
F2FS & NTFS support.
Selinux : Permissive.
Added various TCP Congestion algorithms.(Check out this for more information)
Init.d support.
Added Intelliplug hotplug driver.
Android N support.
Upgraded Dynamic Fsync to 2.0.
Optimized for performance.
LED notifications are fixed now.(Separated into two flashable zips for Stock/VIBE and CM/AOSP Roms. You need to flash accordingly.)
Added various clock rates (including overclock frequencies) in default DVFS table. (You can even underclock frequencies which are not Stock enabled).
Temporarily removed thunder charge driver as it depends on linear charging but our device implements Lenovo standard charging support.(Need to switch to linear charge before implementing the driver. Will look into this later).
Version 1.1
Added Dynamic fsync.
Improved Wake gestures with Haptic feedback.(Use Wake Gesture App)
Removed Tap2Unlock.
Added OC 1.9 Ghz.
Fixed LED notification bug.
Removed Smartmax Governor
3.10.103->3.10.104
Version 1.0
Added CPU Governers
Added I/O Schedulers
WiFi Power management control
Wake Gestures(Wake Gestures : Sweep2wake, Sweep2sleep, DoubleTap2wake and Tap2Unlock).
ThunderQuake Engine 1.0 - Vibration Intensity Controller
ThunderCharge Fast Charge Driver
XDA:DevDB Information
ULTIMATE Kernel, Kernel for the Lenovo K3 Note
Donations:
Contributors
GSandeep
Thanks to
1. Daniel_hk for fixing tfa9897.:good:
2. Varun.chitre15 for his thunder drivers.
3. faux123 for Intelliplug driver.
4. flar2 for elementalx.
Source : https://github.com/GSandeep96/Kernel_Ultimate_6.0-7.1_k50a40
Anykind of bugs if you come across can be notified.
My email Id : [email protected]
Version Information
Status: Stable
Current Stable Version: 1.4
Stable Release Date: 2017-02-23
Created 2016-11-16
Last Updated 2017-02-23

Reserved

I'm replying so the thread would be seen in XDA Labs. It's apparently a known issue.
EDIT: Threads with no replys are sometimes not shown inside XDA Labs app. Okay, now the thread is visible. I will test the kernel later...

anyone try this already?

GSandeep said:
Warnings:-
FEATURES
Compiled with UBERTC-6.0.x
Added I/O Schedulers
->sio
->fiops
->zen
->tripndroid
->vr
->bfq
Wake Gestures
ThunderCharge Fast Charge Driver
CPU Hotplugging(thunderplug driver)
Make a BACKUP of boot partition using TWRP just to be on safeside!!.
Added Dynamic fsync.
Removed Tap2Unlock.
Fixed LED notication bug.
3.10.103->3.10.104
Version 1.0
Added CPU Governers
WiFi Power management control
ThunderQuake Engine 1.0 - Vibration Intensity Controller
ThunderCharge Fast Charge Driver
XDA:DevDB Information
ULTIMATE Kernel, Kernel for the Lenovo K3 Note
Contributors
GSandeep
Thanks to
1. Daniel_hk for fixing tfa9897.:good:
2. Varun.chitre15 for his thunder drivers.
3. Sandeep.sethi for fixing thunder quake & LED bug.
Source : https://github.com/GSandeep24/Kernel_Ultimate_K50a40
Anykind of bugs if you come across can be notified.
My email Id : [email protected]
Version Information
Status: Stable
Current Stable Version: 1.1
Stable Release Date: 2016-11-17
Created 2016-11-16
Last Updated 2016-11-16
Click to expand...
Click to collapse
Can you tell me how to increase battery and better ram management?

GSandeep said:
....
Click to expand...
Click to collapse
Downloading and testing. Will report soon.

Can someone tell me what do the options in WiFi power management mean? Searched on the internet but couldn't find anything

raghuM said:
Can someone tell me what do the options in WiFi power management mean? Searched on the internet but couldn't find anything
Click to expand...
Click to collapse
WiFi sleeps when your device is docked

how to control the wake from back key..

jomypjose said:
how to control the wake from back key..
Click to expand...
Click to collapse
Use kernel auditor app

Flahsed with 1631 vdt rom... working well so far..
Thanks for this kernel and keep it up... :good:
Sent from my Lenovo K50-t5 using XDA Labs

Here it is all about!
raghuM said:
Can someone tell me what do the options in WiFi power management mean? Searched on the internet but couldn't find anything
Click to expand...
Click to collapse
There are three power modes for the Wi-Fi Power Management area and they are:
PM_CAM
PM_FAST
PM_MAX
CAM (Constantly Awake Mode) – keeps the radio powered up continuously to ensure there is minimal lag in response time. This power save setting consumes the most power but offers the highest throughput.
Fast – switches between PSP mode and CAM mode, depending on network traffic. For example, it switches to CAM when it is receiving a large number of packets and switches back to PSP after the packets have been retrieved. Fast is recommended when power consumption and throughput is a concern.
Maximum – the access point buffers incoming messages for the radio. The radio occasionally ‘wakes up’ to determine if any buffered messages are waiting and then returns to sleep mode after it requests each message. This setting conserves the most power but also provides the lowest throughput. It is recommended for radios in which power consumption is most important (such as small battery-operated devices).

GSandeep said:
There are three power modes for the Wi-Fi Power Management area and they are:
PM_CAM
PM_FAST
PM_MAX
CAM (Constantly Awake Mode) – keeps the radio powered up continuously to ensure there is minimal lag in response time. This power save setting consumes the most power but offers the highest throughput.
Fast – switches between PSP mode and CAM mode, depending on network traffic. For example, it switches to CAM when it is receiving a large number of packets and switches back to PSP after the packets have been retrieved. Fast is recommended when power consumption and throughput is a concern.
Maximum – the access point buffers incoming messages for the radio. The radio occasionally ‘wakes up’ to determine if any buffered messages are waiting and then returns to sleep mode after it requests each message. This setting conserves the most power but also provides the lowest throughput. It is recommended for radios in which power consumption is most important (such as small battery-operated devices).
Click to expand...
Click to collapse
Ok now i get it. Thanks

Sorry.
jomypjose said:
how to control the wake from back key..
Click to expand...
Click to collapse
I didnt get you. If you are troubling with wake gestures. Just go to Kernel Aduitor app. Go to wake menu... enable all options and check Apply on boot. Also use wake gestures app to customize. Check out screenshots that i have posted.

Rajendran Rasa said:
Use kernel auditor app
Click to expand...
Click to collapse
there is only dt2w,s2w and s2s no option for back key

just flash this kernel , and wow! i never think this cpu can boost up to 1.9 ghz! and so far no issue because is just an hour ago.
Can you share what is the best setting for thunderplug ? Or we remain it as default?

this is the second time phone reboot because game halt.
not sure is frequency too high or thunderplug cause it .

adikri said:
Flahsed with 1631 vdt rom... working well so far..
Thanks for this kernel and keep it up... :good:
Sent from my Lenovo K50-t5 using XDA Labs
Click to expand...
Click to collapse
Good news, is the notification led working with your rom?
Thanks

ekihd said:
Good news, is the notification led working with your rom?
Thanks
Click to expand...
Click to collapse
Yes, it working as well..

temporary back to renice because this kernel makes so much auto reboot . i already limited cpu frequency to 1.6ghz .switch off the thunderplug .only select governor as wheatley .
but phone still hang .
not sure whats going on