[KERNEL][KK][4.4.2][Custom Linaro][-O3]RenderBroken's Kernel[3/22]

Which touch recovery would you prefer?

  • TWRP (already ported and ready to go)

    Votes: 29 72.5%
  • Touch CWM (Work would be needed to port)

    Votes: 11 27.5%

  • Total voters
    40
  • Poll closed .
Search This thread

RenderBroken

Recognized Developer
Sep 14, 2013
4,297
20,085
36
/home/renderbroken/android
dont work button Home и Search if im used Render-CM11-KK-01-09-TWRP.zip but all good works on Render-CM11-KK-01-09-CWM.zip.
used rom port 9100 beanstalk.
what do you think about this?

I will include the Key Libs from here on out. I used to but stopped for some reason. Now that people are porting roms more often then I will start including the necessary files. I was starting to worry when people were complaining about the buttons not working lol

had the same problem .installed cwm 29/12 version first the cleaned with cooks kernel cleaner and installed 1/9 twrp version and all buttons worked fine on my i777 .

I will also be implementing a cleaning script when installing my kernel. I figured I will get ahead of it since I will soon have it so users can create their own profiles.

Those of you having button problems can also flash this file; it's a quick and easy fix, and only includes the i777 key lib files.

I love Copy! I really like the lack of ads and how easy it is to use and share files. Thanks again for bring this to my attention. I am very happy with it. I believe I will go ahead and move ALL my files from Dev Host to it just for records sake. Also because I am curious, what is your forte? Other than helping others.
 

razen_kain

Senior Member
Jan 28, 2013
2,563
2,484
Carthage
Well, helping others (or offering unwanted opinions :cool:) is it! I can port but I'm no dev, just don't have the time/knowledge.

It's good having you around. I know when i get email alert that Steve Murphy has responded to a thread i subscribe to, i pay attention. Always good advice. :thumbup::)

Sent from my SGH-S959G
 

azeem40

Senior Member
Jun 13, 2013
936
235
Frisco
TWRP did such a weird thing. I tried restoring my backup for CM11, and after it restored system, it formatted my data, and then reboot the phone without restoring my data, so now I lost all my CM11 data for Render's ROM. So weird...
 

cyril279

Senior Member
Jun 3, 2013
987
2,076
This is some the same behavior that we were experiencing using the omni kernel before some extra governors were ripped out.

Zzmove, in particular.

TWRP did such a weird thing. I tried restoring my backup for CM11, and after it restored system, it formatted my data, and then reboot the phone without restoring my data, so now I lost all my CM11 data for Render's ROM. So weird...
 
Last edited:
  • Like
Reactions: SteveMurphy

cyril279

Senior Member
Jun 3, 2013
987
2,076
Assuming that the backup is intact, you can dirty-flash the latest omni, and use the stock kernel/recovery to restore the backup.

It happened to me once recently on render's kernel, but I considered it a fluke, since I had already performed a successful backup on render's kernel.
At this point I think it happens less reliably on render's kernel than on the old problematic omni kernel, so it may be tougher to replicate, but I think that a last_kmsg.log helps most.

For history on the issue, there's this thread, courtesy of @bleggy, and this final comment from the jira report; OMNI-250:
Andrew Dodd added a comment - 03/Jan/14 2:37 PM
Some of the new CPU governors that were added to the kernel behaved very badly when not selected as default, triggering hung task timeouts which triggered reboots. All of the new governors were ripped out and everything is happy again.
Adaptive is most definitely not coming back, and the other governors will only be allowed back one at a time if their merits can be proven.

So, what can I do about it so it doesn't happen again?
 

RenderBroken

Recognized Developer
Sep 14, 2013
4,297
20,085
36
/home/renderbroken/android
TWRP did such a weird thing. I tried restoring my backup for CM11, and after it restored system, it formatted my data, and then reboot the phone without restoring my data, so now I lost all my CM11 data for Render's ROM. So weird...

This is some the same behavior that we were experiencing using the omni kernel before some extra governors were ripped out.

Zzmove, in particular.

Assuming that the backup is intact, you can dirty-flash the latest omni, and use the stock kernel/recovery to restore the backup.

It happened to me once recently on render's kernel, but I considered it a fluke, since I had already performed a successful backup on render's kernel.
At this point I think it happens less reliably on render's kernel than on the old problematic omni kernel, so it may be tougher to replicate, but I think that a last_kmsg.log helps most.

For history on the issue, there's this thread, courtesy of @bleggy, and this final comment from the jira report; OMNI-250:


Thanks @cyril279! I have been seeing reports about zzmove not working correctly for KK. I will be taking it out for now. Also can you tell me (if you remember) what your kernel settings were when this happened to the both of you?
 
  • Like
Reactions: SteveMurphy

cyril279

Senior Member
Jun 3, 2013
987
2,076
No special settings, I use the kernel as-is, out-of-the-box. It doesn't seem to take much (aside from time) to get the device to reboot (see below).

flashed render recovery
rebooted to recovery
initialized backup of boot, system, & data
>>unexpected reboot during /data backup<<

It was suggested in Bleggy's thread that it's more a function of time than anything else, so for the second log, I didn't do anything at all except boot to recovery, and wait.

reboot to recovery
set screen timeout to 300 seconds
wait
>>unexpected reboot<<

edit: logs: https://drive.google.com/folderview?id=0B0R9j8_Y-KixbnZSYTN0OFc3WG8&usp=sharing

Thanks @cyril279! I have been seeing reports about zzmove not working correctly for KK. I will be taking it out for now. Also can you tell me (if you remember) what your kernel settings were when this happened to the both of you?
 
Last edited:
  • Like
Reactions: SteveMurphy

grave_digger

Senior Member
Feb 16, 2011
210
132
I tried zzzmove for a few days and had at least 2 random reboots a day and a few lock ups so I changed back yesterday. A few pages back it was suggested, don't remember by who, they had used zzzmove successfully so I wanted to try it. I'm on on demand right now. Any suggestions for balanced battery life and performance?

The grave digger will be the last person in the world to let you down in a tight spot.
Sent from my SGH-S959G using xda app-developers app
 
  • Like
Reactions: RenderBroken

royahaun

Senior Member
Dec 7, 2013
66
57
okanogan
I don't have a clue what I doing different. I have been running the newest Rom build and Kernel a solid week now with NO problems using Zzmoves and SIO as the I/O scheduler 1400000khz .CPU voltages are all O V by 50mv. Boost on.
In did a clean install. I did not restore from CWM. I down loaded apps from the store. Google downloaded its back up. I have not flashed any thing for 7days . just been working on getting the most out of this ROM. Battery and cleaning up apps. I'm constantly getting AnTu scores of above 12700 And can push into the 13000.
I had some overheating and freezes first day but I think I was the cause over Tweek. A wipe and reboot cured. I would be pleased to run any test or try to answer any questions The way this ROM is performing I don't no if I want to flash Again.

Sent from my SGH-I777 using XDA Premium 4 mobile app
 
  • Like
Reactions: RenderBroken

RenderBroken

Recognized Developer
Sep 14, 2013
4,297
20,085
36
/home/renderbroken/android
Hi Render, I 've check out your kernel but stuck at setting up the SaberMod Toolchain
So, would you plz upload your configured Toolchain? I've tried to download the toolchain at https://github.com/SaberMod/android_prebuilts_gcc_linux-x86_arm_sabermod-arm-linux-androideabi-4.8 but still not getting luck...

I would use the 4.7 toolchain. I am curious though if you can build with out errors with the 4.8 one. What I do is this:

cd one directory before your kernel source. This way you don't clutter your source directory. The clone the toolchain:

git clone https://github.com/SaberMod/android_prebuilts_gcc_linux-x86_arm_sabermod-arm-linux-androideabi-4.7

Then I rename the new folder to something like:

sabermod-arm-eabi-4.7

Definitely use the dashes so you can use tab to complete the name easier. People that know linux know what I mean. Once done you need to point to in ni the Makefile. If you look at my commits you will see the required changes. You can see everything that ends in i777 is something I added/changed to make it work for me or/and the i777. If you use the 4.8 toolchain please let me know how it goes! :)
 

azeem40

Senior Member
Jun 13, 2013
936
235
Frisco
I will not be able to use my phone for a few months due to college (I need to focus. Last semester of community college), so I bid you all farewell. I might be back for a bit when the semester ends until I transfer to a new phone. Thank you RenderBroken for such an awesome ROM and Kernel. Even though the battery life on KitKat has been below average for me, this ROM was notable for giving the better battery life of the others here, and this ROM kept me from going back to stock ROM for the battery life. KitKat has grown on me, so I didn't feel like leaving it. I will continue to be active here on the i777 forums after the few months of away time.

I can't wait to see how far this ROM progresses in the coming months. Good luck man!
 

RenderBroken

Recognized Developer
Sep 14, 2013
4,297
20,085
36
/home/renderbroken/android
I will not be able to use my phone for a few months due to college (I need to focus. Last semester of community college), so I bid you all farewell. I might be back for a bit when the semester ends until I transfer to a new phone. Thank you RenderBroken for such an awesome ROM and Kernel. Even though the battery life on KitKat has been below average for me, this ROM was notable for giving the better battery life of the others here, and this ROM kept me from going back to stock ROM for the battery life. KitKat has grown on me, so I didn't feel like leaving it. I will continue to be active here on the i777 forums after the few months of away time.

I can't wait to see how far this ROM progresses in the coming months. Good luck man!

Thanks a good luck! Drop a line sometime.
 
  • Like
Reactions: azeem40

msprag13

Senior Member
Jun 17, 2011
113
22
There has been a rather important update to superSU that addresses the problem with root on kit kat. Need to watch for the update after flashing the new kernel and rerun superSU.

Sent from my SGH-I777 using XDA Premium 4 mobile app
 

Top Liked Posts

  • There are no posts matching your filters.
  • 29
    RenderBroken's Custom Kernel for
    CM11/AoCP/OmniRom & SlimKat​

    Witty paragraph goes here

    Contributors
    These are the people that have helped out this thread in their own way. Whether it by helpful info or by being or giving me motivation to do what I am doing.

    @iXNyNe, @trevor.bman, @razen_kain, @mr-cook, @royahaun, @david72262, @SteveMurphy and so on. Practically EVERYONE on both my threads are helpful and contribute to the discussion.

    Donators(I KNOW RIGHT?! I never set out to make money doing this but to have someone give me their hard earned money blows me away. THANKS!
    @royahaun
    @NePanicPas


    SGH-S959G Users: Please see Post #2

    Changelog
    General List
    * remove deleted files
    * initramfs: update initramfs
    * Setup OUT folder to creating Zips
    * Build: Setup build script
    * Defconfig: Setup for i777
    * Build: set -O3 Flags
    * stweaks: add profiles for governors
    * mach-u1: restore stock TMU profile
    * Update recoveries 22/03/2014
    * cpufreq: zzmoove v0.8 SOURCE: https://github.com/zanezam/cpufreq-governor-zzmoove/commits/master
    * mali: make sampling more lazy
    * Revert warning fixes
    * bcmdhd: wifi_pm to save power while suspended and when proximity is detected
    * build: fix some warnings
    * build: revert some of warning fixes
    * exynos: tmu: Fix warning and silence spam
    * ARM: cache: assume 64-byte L1 cachelines for ARMv7 CPUs
    * drivers: Fix general compile warnings and cleanup
    * drivers: usb: Fix compile warnings and cleanup
    * drivers: misc: Fix compile warnings and cleanup
    * drivers: mmc: Fix compile warnings and cleanup
    * drivers: input: Fix compile warnings and cleanup
    * drivers: power: Fix compile warnings and cleanup
    * drivers: video: Fix compile warnings and cleanup
    * drivers: media: Fix compile warnings and cleanup
    * exynos: Fixes and mess cleanup
    * arm: mm: Fix compile warnings for dma
    * net: Fix compile warnings
    * block: BFQ I/O scheduler v7r2 for linux 3.0.y source: http://algo.ing.unimo.it/people/paolo/disk_sched/sources.php
    * ARM: smp: Wait just 1 second for other CPU to halt Currently, the busyloop waiting for a 2nd CPU to stop takes about 4 seconds. Adjust for the overhead of the loop by looping every 1ms instead of 1us.
    * arm: LoUIS cache maintenance API
    * build: update defconfig + undervolt busfreq and set a higher threshold, this aims battery saving
    * pm-hotplug: add tegrak's secondcore support + pm-hotplug enable/disable depending on the selected cpu governor
    * input: mxt224: tweak touchscreen when plugged to charger
    * Revert "mm: Don't use CMA pages for page cache"
    * mm: Don't use CMA pages for page cache All layers of the page cache may take extra references to pages to avoid migration. This is fine for general movable pages but renders CMA pages useless as they cannot be allocated for contiguous m
    * arm: remove intelli_plug
    * intelli_plug: switch to use dedicated high priority workqueue
    * intelliplug: add GT-i9100 touch input
    * intelli_plug: tune for dual core mode
    * Intelliplug 2.0
    * bcmdhd: update to 1.61.58 from google edition jf (4.3) Applied to smdk44x2 appears to help with dialing issues on wifi. jf firmware is ideal also.
    * ondemand: Add support to consider other cpu load when scaling frequen… …cies
    * update defconfig
    * ext4: prevent kernel panic in case of uninitialized jinode
    * ARM-spinlock: use ticket algorithm for ARMv6+ locking implementation
    * ARM: Add optimised swahb32() byteswap helper
    * ARM: L1 cache optimization
    * ksm: check and skip page, if it is already scanned
    * input: touchscreen: revert mxt224_u1 changes
    * limit gpu to 440mhz
    * Revert "stweaks: remove charge control"
    * power: sec_battery_u1: Add charge current interface
    * touchscreen: mxt224_u1: use platform data struct directly to set touchscreen threshold values
    * touchscreen: prevent applying movhysti setting when the screen is off
    * tegrak's touchmove modification to set pixel sensitivity which is known as vitalij value
    * mali: create a device file in /sys/module/mali/parameters to read current utilization level
    * stweaks: show which frequencies are vpll
    * mach-u1: increase max voltage on buck3 (for gpu)
    * stweaks: vpll configuration
    * mali: exynos4_pmm.c: fix typo
    * mali: experimental vpll mode exynos4_pmm.c credits: dorimanx https://github.com/dorimanx/Doriman...mmit/a90b0f4398736d83651a61627fc751efc25970b4
    * stweaks: remove charge control
    * Revert "power: sec_battery_u1: Add charge current interface"
    * Fix typo
    * Fix typo
    * Update systemcat
    * mach-u1: Update TMU profile
    * tweak systemstatus script
    * build: fix mali libs path
    * Update recoveries 07/03/2014
    * build: add mali blobs for jb roms also add lights lib needed for BLN
    * build: create ramdisk's cpio
    * stweaks: change hotplug options for mono-core only
    * stweaks: add cpu hotplug control
    * arm: auto_hotplug: add max_online_cpus feature https://github.com/mathkid95/linux_lg_kitkat/commit/9f913bc150f0bb36152343cc994cbc65f866fa8f
    * cpufreq: remove scaling_available_freqs as it is already in the cpu_undervolting module
    * stweaks: restore customconfig.xml merged some test stuff by mistake in https://github.com/gustavoss/androi...mmit/17f5eda45047215f4aeb71210b04dd520759041c
    * build: include mali blobs for jb kernel
    * build: new build script based on codeworkx's script: https://github.com/codeworkx/GT-I9100_ClockworkMod-Recovery/blob/jellybean/build.sh
    * block: bfq: prevent aliased requests from starving other I/O
    * build: update defconfig
    * iosched: prevent aliased requests from starving other I/O
    * sched/nohz: Rewrite, fix and add more accurate load-avg computation
    * pegasusq (based on ondemand): cpuidle detection
    * sched: use cpu capacity to decide if a ILB is needed
    * cpupower: update the cpu_power according to cpu load
    * ARM: cpu topology: add debugfs
    * ARM: cpu topology: Add asym topology flag for using cpu0 1st
    * ARM: topology: Add a topology update notification
    * ARM: topology: Add a cpu_power function
    * ARM: topology: Update topology according to current sched_mc mode
    * ARM: topology: save cpu id of each core
    * sched: Ensure cpu_power periodic update
    * ARM: 7182/1: ARM cpu topology: fix warning
    * ARM: 7011/1: Add ARM cpu topology definition
    * cpufreq: ondemand: Remove unnecessary synchronization attempt
    * drivers: misc: cpu undervolting driver clean up
    * fix typos M = 10^6 m = 10^-3
    * system watch scripts
    * init: update ramdisk and recoveries, add cpu load to gpuwatch and rename it to systemwatch
    * build: fix kernel command line
    * stweaks: fix typo
    * sched: enable gentle fair sleepers by default Also set the right description from /kernel/sched/features.h I don't see any side effect when using it and it might save some battery
    * initramfs: clean up
    * mach-exynos: 2MB audio buffer
    * build: set SELinux as permissive by default
    * Updates from samsung source drop XXUGLM3


    Comprehensive List:
    Source History

    Current Build Date:2/4/2014

    Build Downloads

    STweaks Download:
    https://play.google.com/store/apps/details?id=com.gokhanmoral.stweaks.app&hl=en

    Kernel Credits
    gokhanmoral, codeworkx and all CM team for their wonderful work (99% of kernel and commits)
    franciscofranco, faux123, myfluxi, neobuddy89, omni team and geeckodev for porting mali and s3cfb drivers to smdk4210 ( 0.999%, most of the tweaks in the kernel) Gustavo_s and wiithepeng for getting me through a rough spot :)


    Sources:
    https://github.com/RenderBroken/android_kernel_samsung_smdk4412

    Testers:
    @razen_kain
    19
    Working on new build. Just hang tight. I am trying to get my kernel work onto my new VM. Its a pain in the ass lol. I am getting really weird build errors using all the same stuff so Im not sure what the problem is there but I just wanted to spread the word. Installing new HDD into my old build machine so I can hopefully and finally download the Liquid Smooth source this weekend. My wife and son will be at my inlaws for while so its time to get it done. lol. Honestly I am trying to get away from the Rom building and focus on my kernel work but I also dont want to leave anyone hanging. I am working on some partnerships so we can get active builds going again and it not all depend on the amount of free time I have. So hang tight. You may see some cool minor changes. Hopefully we can keep the ol' s2 a bit more life. If you are tired of it and want to get the best phone for the money then get a Moto G! (No I don't get paid by Motorola to endorse lol. I wish though . . .) I am working on a new kernel for the Moto G that no one has yet seen for the phone. Adding new features from other great devs. I was tired of seeing 3 different kernels but all use Faux's Intelliplug. Its not bad but I wanted more control. I am looking at a possible hotplug change here though too. We will have to see. I won't believe it til I see it. Thanks guys for being cordial and not staying on my ass about new builds. Yall have been great. Because of the space and respect I will continue to support the i777/S959G for as long as I can or as long as its relevant.

    Kind Regards,
    Zachariah
    12
    New kernel builds uploaded. Please check the source for changes. Also please note that the default STweaks profile is subject to change from build to build so make sure STweaks is setup the way you want each time you flash. I cant test every single build but the source is kept pretty stable. Also I have now started building for SlimKat. This is for those who port SlimKat currently. Lastly I encourage people to port roms from the i9100 thread. I build my kernels and package them so they should work without any other steps. You should be able to just flash the i9100 rom then my kernel. Thats it! I will update the OP when I am done cooking/eating. Enjoy the builds and as always let us know how it goes.

    Render
    11
    Some good news, I was able to find the problem with my kernel builds. I was using strict -O3 flags and something was not agreeing with that so I changed to -O2 instead. The performance hit is not noticeable. Also I had setup a build script so building kernels take A LOT less time now. What this means is i will go ahead and build CWM/TWRP for both CM11 and OMNI. This was the end user can choose what they like best. I also added a Fade effect for BLN. Check it out in STweaks. Setup new boostpulse driver. Short story is that its now working for ALL governors and is more efficient than before. And Much more.
    11
    F - F - F - Failed Build Breaker!!!!!

    I have finally been able to get a working kernel build. This new build has so many new features it will blow your pants off (Literally). If you havent been keeping up with the new ZZmoove governor then you are missing out on some pretty exciting developments. The new governor has micro profiles that can now be set on the fly with STweaks. Here is what you are instore for:

    * ------------------------------------------------------------------------------------------------------------------------------------------
    * - (1)'def' -> Default -> will set governor defaults -
    * ------------------------------------------------------------------------------------------------------------------------------------------
    * - (2)'ybat -> Yank Battery -> a very good battery/performance balanced setting -
    * - DEV-NOTE: highly recommended! -
    * ------------------------------------------------------------------------------------------------------------------------------------------
    * - (3)'ybatext'-> Yank Battery Extreme -> like yank battery but focus on battery saving -
    * ------------------------------------------------------------------------------------------------------------------------------------------
    * - (4)'zzbat' -> ZaneZam Battery -> a more 'harsh' setting strictly focused on battery saving -
    * - DEV-NOTE: might give some lags! -
    * ------------------------------------------------------------------------------------------------------------------------------------------
    * - (5)'zzbatp' -> ZaneZam Battery Plus -> NEW! reworked 'faster' battery setting -
    * - DEV-NOTE: recommended too!:) -
    * ------------------------------------------------------------------------------------------------------------------------------------------
    * - (7)'zzopt' -> ZaneZam Optimized -> balanced setting with no focus in any direction -
    * - DEV-NOTE: relict from back in the days, even though some people still like it! -
    * ------------------------------------------------------------------------------------------------------------------------------------------
    * - (6)'zzmod' -> ZaneZam Moderate -> NEW! setting based on 'zzopt' which has mainly (but not strictly only!) 2 cores online -
    * ------------------------------------------------------------------------------------------------------------------------------------------
    * - (8)'zzperf' -> ZaneZam Performance -> all you can get from zzmoove in terms of performance but still has the fast -
    * - down scaling/hotplugging behaving -
    * ------------------------------------------------------------------------------------------------------------------------------------------
    * - (9)'zzinz' -> ZaneZam InZane -> NEW! based on performance with new insane scaling active. a new experience! -
    * ------------------------------------------------------------------------------------------------------------------------------------------
    * - (10)'zzgame' -> ZaneZam Gaming -> NEW! based on performance with scaling block enabled to avoid cpu overheating during gameplay -
    * ------------------------------------------------------------------------------------------------------------------------------------------

    I will update OP#1 shortly . . .

    Kind Regards,
    Render
    (Zachariah)