Thread Updated: February 24th, 2012Rom Name: HoliRaider
Developer: bananacakes
Version: 1.6 / 1.6-4G
Last Update: February 23th, 2012
Features:
Based on SKT KR 2.31.911.2 LTE
Rooted
Ultra Smooth Rosie (thanks to hamdir)
the latest Beats Audio(Thanks to RcmixTeam) & cyanogen-dsp manager
A ton of languages included
Completely De-odexed
EXT4 Optimization Complete
5X5 app drawer
XLOUD engine Powered by Sony Corporation
Advanced Power Menu
some Imported Sensation Xl audio driver
Amaze Camera V8 fully working With 3.5 Stock gallery(thanks to CdTDroiD & Baadnewz)
Imported Full Bravia engine(lib, etc, framework)
Advance Powermenu
Improved Adreno220 configuration for better quality and performance
Added Bliss Default Videoplayer
Tweaks for a smooth, faster and better performance
Improved mms(Secure sms and block list, trashcan, backup & restore, enable in sms setting)
Improved Audio(Extremely enhanced sound for Delight your music)
Improved auto-brightness values
Fixed key backlight Issue
Imported paintdriver from Bliss
Full bash shell with nano
Fixed Native Screen capture
Extended quicksettings added (flashlight, hot reboot, wireless adb)
Added BatteryBar Settings (Thanks to pvyParts)
Remove unnecessary apk
Tweak DB & more (from Warm ROMS)
And more.. more tweak for a smooth..
Updates:
v1.7
SUPER FAST & BETTER PERFORMANCE
Disabled MMS Compression
Enabled 3D Home screens with toggle in display settings
Added Drop clean caches
Tweak Threshold
Tweak Render UI with GPU
Attempting to stabilizing
More Smooth & intuitive response
Tethering hopefully fixed
Disabled Scrolling Cache (Smooter UI)
Modified Beats audio
Vdd Cpu set (For stabilizing )
echo "+25000" > /sys/devices/system/cpu/cpufreq/vdd_table/vdd_levels
Net debugging hopefully fixed
Updated some drivers
heat & bootloop & battery drain hopefully fixed
And more..
Click to expand...
Click to collapse
**Notice***
I am a full time employee & student. If something is urgent please PM me and I will add it. Otherwise I will try to update this thread weekly.
Frequently Asked Questions
Q: Highest phone can be overclocked too?
A: 1.5ghz or 1.7ghz depending on your kernel. Use SetCPU to control the ranges and profiles.
Q: How do I use SetCPU?
A: First off no two phones perform exactly the same. Trust me.
Thanks DavidCampbell
The profiles I use are below in order of priority
1. Screen off 192 Max 192 Min
2. temp (greater than) > 44.9 C 864Max 192Min (important one)
3. Battery < 30% 756max 192 min
4. Battery < 60% 972max 192min
I have an extended battery and 30% and 60% are actually more like 10% and 5% its just the phone doesnt read the battery properly.
I leave the main slider at 1188000 and set on boot
oh and I use on demand for all of the options except the 30% on and the screen off one which I use powersave
Click to expand...
Click to collapse
Q: My phone doesn't wake up while sleeping when I get a phone call.
A: Flash the CRT Patch here
**placeholder**
What's the fastest this can be overclocked to?
bangorang said:
What's the fastest this can be overclocked to?
Click to expand...
Click to collapse
some older kernals went all the way up to 1.8 but currently the two kernals are 1.7 or 1.5 ghz on this specific rom as of the 15th
bigballa said:
some older kernals went all the way up to 1.8 but currently the two kernals are 1.7 or 1.5 ghz on this specific rom as of the 15th
Click to expand...
Click to collapse
Which kernel goes up to 1.7? I flashed the one he made a thread for but it went to 1566000... or is that equivalent to 1.7? I though that was 1.5.
bangorang said:
Which kernel goes up to 1.7? I flashed the one he made a thread for but it went to 1566000... or is that equivalent to 1.7? I though that was 1.5.
Click to expand...
Click to collapse
I think those with native 1.2 are allowed up to 1.56, and those with native 1.5 has the higher limit with the kernel. Keep in mind QC only had to make sure the processor runs at 1.2 for the Vivid and not 1.5, so even though the APQ8060 is rated up to 1.5, there is no guarantee that the Vivid will run PERFECTLY at 1.5 or beyond.
I reflashed and am now able to overclock at 1.7. I used the kernel from his kernel thread. Thanks!
Sent from my HTC Raider X710e using XDA App
dizzyraider said:
I think those with native 1.2 are allowed up to 1.56, and those with native 1.5 has the higher limit with the kernel. Keep in mind QC only had to make sure the processor runs at 1.2 for the Vivid and not 1.5, so even though the APQ8060 is rated up to 1.5, there is no guarantee that the Vivid will run PERFECTLY at 1.5 or beyond.
Click to expand...
Click to collapse
This isn't logical. The only reason HTC vivid is at 1.2 is because att likely wanted it underclocked so that the skyrocket would be showcased with higher specs. The true stock clock is 1.5. Hence oc to 1.7 to 1.8 would cause no more potential damage to it than if it were the velocity which are the exact same phone.
Sent from my HTC Raider X710e using xda premium
Thankfully mine is stock at 1.5... I suggest to those overclocking you use setcpu and set profiles to force the phone to underclock at certain temperatures, this has saved my phones in the past, I've never blown a cpu.
I beleive the vivid and raider are at 1.2 to give better battery saving. I run mine at 1.18 most of the time anyway.
davidcampbell said:
Thankfully mine is stock at 1.5... I suggest to those overclocking you use setcpu and set profiles to force the phone to underclock at certain temperatures, this has saved my phones in the past, I've never blown a cpu.
I beleive the vivid and raider are at 1.2 to give better battery saving. I run mine at 1.18 most of the time anyway.
Click to expand...
Click to collapse
What CPU settings on each profile? That should definitely be a FAQ. I have setCPU and I just use inteldemand with the min at its lowest and max at the highest of 1.7
Sent from my HTC Raider X710e using XDA App
bangorang said:
What CPU settings on each profile? That should definitely be a FAQ. I have setCPU and I just use inteldemand with the min at its lowest and max at the highest of 1.7
Sent from my HTC Raider X710e using XDA App
Click to expand...
Click to collapse
If i see some good profiles written out anywhere ill add them to the FAQ if not then ill go ahead and create a base template to how i use it.
bigballa said:
If i see some good profiles written out anywhere ill add them to the FAQ if not then ill go ahead and create a base template to how i use it.
Click to expand...
Click to collapse
Ok thank you so much, I just don't wanna brick my phone for not knowing how to set my setcpu
Sent from my HTC Raider X710e using XDA App
---------- Post added at 11:28 AM ---------- Previous post was at 11:27 AM ----------
A little something you can put in this thread (just trying to help you out since you already have work and school on your hands haha).
If you have AT&T, download This and this kernel View attachment 02_15_2_flash_boot.rar. Remember to also flash the Kernel a second time after you flashed the ROM.
If you want your LTE symbol, flash the View attachment 1.6a_stabilizing_patch.zip after you've flashed your kernel for the second time
Q: How do I get my Wifi and tethering back?
A: Chances are, you only flashed the Kernel once (right before you flashed the ROM). Reflash it after the ROM is installed and it should be fixed.
The profiles I use are below in order of priority
1. Screen off 192 Max 192 Min
2. temp (greater than) > 44.9 C 864Max 192Min (important one)
3. Battery < 30% 756max 192 min
4. Battery < 60% 972max 192min
I have an extended battery and 30% and 60% are actually more like 10% and 5% its just the phone doesnt read the battery properly.
I leave the main slider at 1188000 and set on boot
oh and I use on demand for all of the options except the 30% on and the screen off one which I use powersave
Text message issue - only 80 characters per 1 text?
I flashed my Raider already over 50 times. Tested many ROMs.
I've noticed that only Holiraider by Bananacakes (all versions) has only 80 characters per 1 txt message even when Support special accent characters is OFF.
Factory ROM or any other ROM from different Developer has all the time 160 per 1 text (as it supposed to be).
Anyone knows how to get 160 characters per 1 text msg on Holiraider by Bananacakes ?
Any fix for this issue would make this ROM completly perfect
I'm sticking with HoliRaider ROM because has integrated Beats and Amaze Camera which those features are awesome and everything else works perfectly
davidcampbell said:
The profiles I use are below in order of priority
1. Screen off 192 Max 192 Min
2. temp (greater than) > 44.9 C 864Max 192Min (important one)
3. Battery < 30% 756max 192 min
4. Battery < 60% 972max 192min
I have an extended battery and 30% and 60% are actually more like 10% and 5% its just the phone doesnt read the battery properly.
I leave the main slider at 1188000 and set on boot
oh and I use on demand for all of the options except the 30% on and the screen off one which I use powersave
Click to expand...
Click to collapse
I know both HoliRaider as well as the WCX Rom has a native script that sets the cpu governor and clock speed on boot, it is recommended that you delete this if you want to run SetCPU or utilities as such. Without deleting the script, the settings might not stick as there could be conflict.
The file that should be deleted is /system/etc/init.d/15-screenstate_scaling
or
you could open the file with any text editor and change the setting according to your need
xavier_largeaux said:
I flashed my Raider already over 50 times. Tested many ROMs.
I've noticed that only Holiraider by Bananacakes (all versions) has only 80 characters per 1 txt message even when Support special accent characters is OFF.
Factory ROM or any other ROM from different Developer has all the time 160 per 1 text (as it supposed to be).
Anyone knows how to get 160 characters per 1 text msg on Holiraider by Bananacakes ?
Any fix for this issue would make this ROM completly perfect
I'm sticking with HoliRaider ROM because has integrated Beats and Amaze Camera which those features are awesome and everything else works perfectly
Click to expand...
Click to collapse
I'm not having this problem on stock SMS or even using GoSmsPro
I'm on 1.7 now.
cifs module?
Is there a CIFS module compatible with this kernel/ROM at the moment?
Since bananacakes would probably already include it, I'm guessing there's no cifs module at the moment. But, I just thought I'd check to be sure.
Thanks again!
need a mirror site for 1.7 depositfiles is down -_-
jh64dsb877r said:
Is there a CIFS module compatible with this kernel/ROM at the moment?
Since bananacakes would probably already include it, I'm guessing there's no cifs module at the moment. But, I just thought I'd check to be sure.
Thanks again!
Click to expand...
Click to collapse
not that i know of or see throughout the thread.
Related
Check out the review by Blair at GizmoNinja! Droid X ROM Review, rubiX ROMs! Updated 12/26/2010 NEW rubiX ROM 1.9.5 Release!!
YOU MUST BE ON 2.3.340 OTA FOR THIS TO WORK
ALSO NOTE: IF YOU INSTALLED THE NEW TRANQUILITY, THE TOOLBOX WILL INSTALL UNLESS YOU SBF BEFORE INSTALL. THIS IS TRUE FOR ANY ROM, NOT JUST RUBIX.
IF YOU USED THE NEW SCRIPT, YOU MUST REBOOT AFTER INSTALL AND INITIAL SETUP
This script runs on first boot to scan the SDCard rubiX Folder for apps. If they are there, it copies them to /data/app and corrects their permissions. Reboot for this to take effect.
YOU MUST wipe data before install.
Change Log for 2.0:
* Sysctl.conf adjustments:
Changed vm.dirty_background_ratio to 70 from 60
* Added rm /dev/log/main for extra performance/free memory
* Changed NO_NEW_FAIR_SLEEPERS to NO_FAIR_SLEEPERS; this was a typo, as there are no new fair sleepers in the dx kernel already.
* Cleaned up the /system/app folder
The following market apps were further removed:
Talkback
Kickback
Soundback
* Added new Interactive and Conservative kernel scaling governors (credit Milestone team)
This is a Droid X first. These two governors bring a big difference to the table; here is what they do:
(Credit Cyanogenmod GITHub for this, source is here: https://github.com/CyanogenMod/cm-k...60f39120/Documentation/cpu-freq/governors.txt)
Interactive:
Advantages:
+ significantly more responsive to ramp cpu up when required (UI interaction)
+ more consistent ramping, existing governors do their cpu load sampling in a workqueue context, the 'interactive' governor does this in a timer context, which gives more consistent cpu load sampling.
+ higher priority for cpu frequency increase, rt_workqueue is used for scaling up, giving the remaining tasks the cpu performance benefit, unlike existing governors which schedule rampup work to occur after your performance starved tasks have completed.
Conservative:
The CPUfreq governor "conservative", much like the "ondemand"
governor, sets the CPU depending on the current usage. It differs in
behaviour in that it gracefully increases and decreases the CPU speed
rather than jumping to max speed the moment there is any load on the
CPU. This behaviour more suitable in a battery powered environment.
The governor is tweaked in the same manner as the "ondemand" governor
through sysfs with the addition of:
freq_step: this describes what percentage steps the cpu freq should be
increased and decreased smoothly by. By default the cpu frequency will
increase in 5% chunks of your maximum cpu frequency. You can change this
value to anywhere between 0 and 100 where '0' will effectively lock your
CPU at a speed regardless of its load whilst '100' will, in theory, make
it behave identically to the "ondemand" governor.
down_threshold: same as the 'up_threshold' found for the "ondemand"
governor but for the opposite direction. For example when set to its
default value of '20' it means that if the CPU usage needs to be below
20% between samples to have the frequency decreased.
Basically, this means more speed and battery life control
* Adjusted 01cpu for a better sampling rate if the new conservative governor is found.
* Added script: gov
gov allows you to control which governor you use; ondemand, conservative, or interactive. The function is:
gov -ondem for the ondemand governor
gov -cons for the conservative governor
gov -inter for the interactive governor
Alternately, these can be changed via SetCPU or Droid Overclock.
To remove data throttling, click this:
http://www.droidforums.net/forum/dr...-9-7-back-better-than-ever-3.html#post1228193
Credit to Plower.Net
How to install:
Download
Place on SDCard
Bootstrap Recovery via Bootstrap App
Reboot to Clockwork Mod Recovery
Wipe data/factory reset
Select install from sdcard
Choose zip from sdcard
select rubiXFocused2.0.zip
Select yes
Reboot
Enjoy!
Download:
http://www.mediafire.com/?6s32joduwkwyhwa
Will have a mirror up shortly as well.
If you like my work, please support me going to Google I/O Developer's Conference 2011! All donations received are going towards a plane ticket.
https://www.paypal.com/cgi-bin/webscr?cmd=_s-xclick&hosted_button_id=TYYWQBR78DW7U
reserved for me
drod2169 said:
reserved for me
Click to expand...
Click to collapse
what this says ^^^^
Hey drod, thanks for the new release! Will def give this a try!
Sent from my DROIDX using XDA App
SysAdmin-X said:
Hey drod, thanks for the new release! Will def give this a try!
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
Is this fo real Rubix Focus 1.9.7 is it only released on here because i can't find 1.9.7 anywhere else ? .
Hey Drod, Keep Bangin em out.Rubix in General Is StR8 up Sik lookin forward to this one!
about to start installing in 2 min
Got my Approval bruh..Bring on Tron Theme..LOL
d/ling now. Can't wait to try it. Thank you for bring the art of the DX forward a notch or two!
drod2169 said:
reserved for me
Click to expand...
Click to collapse
jawonder said:
Is this fo real Rubix Focus 1.9.7 is it only released on here because i can't find 1.9.7 anywhere else ? .
Click to expand...
Click to collapse
Yes it's really rubiX Focused 1.9.7
will the themes for 1.95 work on this rom (black jiuce)?
Will this work for the droid 2 ? Since the
Old rubix was said to be working for the droid 2..
Just wanted to say the clock-speed/voltage optimization app is amazing. I get better battery life on RubiX than on any other ROM (and I have tried them all).
This is faster than liberty was for me. Glad I came back to RubiX.
Is there a zip to remove animation and put it back to stock. This is rom is so fast that I hit the quadrant score of 1500 without overclocking. Thxs for a great rom. I tried them all.
Sent from my DROIDX using XDA App
I am going to install this rom tonight. I currently have liberty installed and am happy with it and not having any trouble but unless I try other ones I won't know if I like any others better. I would like to see better battery life and it sounds like I might see it with this rom.
drod2169 said:
ALSO NOTE: IF YOU INSTALLED THE NEW TRANQUILITY, THE TOOLBOX WILL INSTALL UNLESS YOU SBF BEFORE INSTALL. THIS IS TRUE FOR ANY ROM, NOT JUST RUBIX.
Click to expand...
Click to collapse
I was able to permanently get rid of the TranQ Toolbox without SBF. Basically, you just need Root Explorer (or equivalent) to remove all the TranQ files from /data, /data/data, /data/dalvik-cache, /data/preinstall_md5, /preinstall/app, /preinstall/md5, etc. The easiest way is to do a search (at /) in Root Explorer for tranq, and then manually remove them.
Does anybody know how to enable 3 d gallery through terminal emulator. Everytime I try to enable it, it tells me not found. Yes I give it SU permission. It gives me the options either 3d or 2d. I type 3d hit enter, then it tells me not found.
Sent from my DROIDX using XDA App
Never mind I figured it out.
I'm having problems with images showing up as black in any of the galleries or image viewers. Sometimes the thumbnails will display properly, though. In the camera app, if I take a picture and then look at the gallery, thumbnails of images on my sd card will show up, but only one for each picture I took. Pictures taken with the camera never show up. What is going on here and is there a way to fix it? I think rubix is great, otherwise, and would really like to continue using it if the camera and image problems can be fixed.
-------------------------------------
Sent via the XDA Tapatalk App
inokumum said:
I'm having problems with images showing up as black in any of the galleries or image viewers. Sometimes the thumbnails will display properly, though. In the camera app, if I take a picture and then look at the gallery, thumbnails of images on my sd card will show up, but only one for each picture I took. Pictures taken with the camera never show up. What is going on here and is there a way to fix it? I think rubix is great, otherwise, and would really like to continue using it if the camera and image problems can be fixed.
-------------------------------------
Sent via the XDA Tapatalk App
Click to expand...
Click to collapse
try swapping to the 3d gallery
type in terminal emulator:
su
gallery -3d
Did anyone by any chance make a flashable zip of the modified services.jar file for this rom for uncapped data? That would be awesome if someone can post it!
Sent from my DROIDX using XDA App
DISCLAIMER: I AM NOT RESPONSIBLE FOR ANY HARD OR SOFTWARE BASED DAMAGE. IF YOUR PHONE BRICKS, YOU LOSE IMPORTANT DATA, OR OTHERWISE INCUR LOSSES AS A RESULT OF RUNNING THIS KERNEL, ITS NOT MY FAULT.
DELETE ALL VOLTAGE CONTROL SETTINGS, AND REMOVE BOOT SETTINGS FROM CM SETTINGS AND VOLTAGE CONTROL AND DISABLE SETCPU PROFILES BEFORE FLASHING THE LATEST UPDATE. THIS GOES FOR ALL UPDATES, INCLUDING UPDATING CM.
This is a CM7 based kernel with a 1.6 Ghz overclock, Voodoo sound and color fixes, uv support, and BLN. See the changelog for all the updates and features.
Informations (THESE CHANGE ON A REGULAR BASIS):
1. Max clock is set to 1GHz on the first boot, set the max clock in CM settings or voltage control or setCPU.
2. I cannot possibly stress this enough. IF YOU EXPERIENCE BUGS WHILE ON THIS KERNEL, POST HERE. Do NOT submit bug reports to the CM team, until you have flashed back to stock CM, and can verify the bug exists there too.
3. Use Xan's UV app to undervolt.It's in that market, search "Voltage Control".
4. Want to go back to stock? First, if there's any particular reason, please let me know. I love to feedback, good or bad. Then, just flash the latest official update.
5. Sources --> https://github.com/TheEscapistxda/andoroid_kernel_samsung_aries
6. BLN is disabled by default. Please enable it by using the BLN control app from the market.
7. Its not a bug. You're not bricked. Let it boot up.
Thanks to Netarchy for his Nexus S oc code, coolhbo for setCPU, the CMSGS team for their work, Supercurio for Voodoo, raspdeep for his oc/uv patches(showed me how to create a sysfs interface for uv), Xan for the uv app, neldar for BLN, and cyanogen for his amazing rom.
CHANGELOG:
V1:
Initial release
V2:
Voodoo Sound v4 added!
v2.2
Fixed the OC bug from v2
Fixed the OC bug from (the unreleased) v2.1
Added some initial testing code for UV!
Removed v2 from the downloads
Added a stock kernel to downloads
v2.3
Added wifi sleep workaround from coolya
v2.4
Updated to be in sync with the official releases
Removed some debug code (coolya)
Added compatibility with the cpusettings in CMparts(coolya & atinm) (Only works under updates after march 04 update, as it requires code in the actual rom.)
v3.0
Added compatibility with Xan's uv app!
v3.1
Added the new wifi sleep fix
Fixed the uv bug (hopefully)
Removed v3
v3.2
updated to stay in sync with the 03122011 nightly
yas259 fixes(don't ask me about these, this driver is way over my head)
radio fixes(not ril polling)
config edits
v3.3
updated to keep in sync with the 20111303 nightly
Lots of little tweaks
-kernel hz = user hz =100
-update timings (Thanks Kang)
-enabled Tiny RCU
Removed the returntostock kernel
v3.4
Updated Voodoo sound to v5
Implemented voodoo color v2
v3.5
Updated Voodoo sound driver number to v5 (now the control app says 5)
Added 600mhz and 1.3Ghz steps
Added interactive and smartass cpu frequency governors
Some initial work on BLN (disabled)
Added frequency_voltage_table for compatibility with custom frequencies in the uv app (disabled due to bugs)
v4.0 - (BUGGY, BETA RELEASE)
Increased voltage on 600mhz and 1.3ghz steps (let me know how this affects stabilty, guys)
Implemented BLN (VERY EXPERIMENTAL AND BUGGY)
Added states table to Voltage Control app that doesn't actually do anything.
Added Atimn/eifert's fix for the bad block issue.
v4.1
Fixed the stability issue on 1300mhz (Big thanks to kang for his help)
Added in the cardock fixes from xcaliburinhand (grab the "DockSound Redirector" app from the market)
fixed the ?mv bug in voltage control
Fixed bln (thanks to neldar)
Added 1000hz version of the kernel
Did a few tweaks to smartass, it's still kinda sketchy though
Updated voodoo sound to v6
There's probably more, I just can't remember them.
v4.2
More stability tweaks on 1300mhz
-The voltage for 1300mhz is now the same as 1200mhz, so you won't be able to undervolt it as much in the app, but it seems to help with stability.
Latest bln from neldar (fixes the touchkey disabled bug, and the touchkey on during sleep bug)
Enabled the microphone presets for voodoo sound
v4.3
Added 1400, 1500, and 1600mhz steps
Updated voodoo sound v7 (very little feature changes though)
Unlocked FPS cap
Built on latest upstream code (pulls in all fixes in recovery, etc. If people are still having bad block issues, let me know)
v4.4
Disabled some debug code
Fixed the ?mv bug on 400, 200, and 100mhz steps in voltage control
Fixed up smartass
Integrated the sdcard r/w cache fix (Thanks to Existz for pointing it out)
v4.5
Upstream fixes:
-New wifi driver
-New kernel flashing method, which should help bad block people
-Dual sd card sharing
Added a time that a frequency must stay at before scaling up in smartass
- You can tweak it same way as you can tweak all the other settings, its ramp_up_rate_ns
v4.6
Upstream fixes:
- Lots of random JVB merges, code clean up, etc.
Fixed the notification bug crash on the first v4.6
v5.0[May 3]
- Extend battery polling to 15s
- Sched_autogroup patch (increases smoothness under heavy load)
- New bootlogo
- Fix setCPU crashing on screen off
-Unified HZ (256) (should increase battery life, and has no adverse effect on performance)
- Reunlock fps cap
-Switch to the Codesourcery toolchain (should result in faster/smoother code)
-Full compatibility with 2.3.4
v5.0b[May 4][First Vibrant supported/tested version]
-Fixed touchkeys for real this time
-Temporarily enabled debugging (will be disabled in the next update)
-Fixed the crazy battery stats
-Reenable smartass governor
v5.1[May 6]
-Lots of upstream gpio changes
-Camera drivers kanged from JVB (REQUIRE THE LATEST NIGHTLY TO WORK)
- -03 optimizations
- Switched to hardware based floating point calculations (seems to increase performace under certain loads)
- Dropped 1.6ghz to 1.55ghz
-set default governor to conservative
- New captivate/vibrant specific initramfs
v5.2[May 12]
-new(old) modem_ctl
-tvout stuff
-fsa switch sleep
-overvolting cap
v5.3[May 16]
-upstream initramfs/initial flash changes
-Upstream change to the way battery percentage is calculated
-Lots of little( irrelevant) upstream changes
-Actually fixed the kernel version.
NIGHTLIES/WHENEVERS
#0[May 27]
+Way too many to list. Big changes include an update to 2.6.35.13, voodoo sound v9, and a properly working ril.
#1[May 29]
+States table in voltage control kinda works now, but is herp derp.
+Disabled ext2
+Re added the 1.6Ghz step
+Upped 1.55ghz freq by a few mhz
#2[July 12]
+Up to date with everything
+GPU bus controllable via Control Freak
+Other stuff
TheEscapist said:
NOTE: I need testers, as I dont have a vibrant. There *shouldn't* be anything that breaks specifically on the vibrant, but still.
Click to expand...
Click to collapse
Miui?? Trying it neways thanks
nickmcminn60 said:
Miui?? Trying it neways thanks
Click to expand...
Click to collapse
Epic Fail! So this should work with miui tomorrow after the 2.3.4 update? Can you post a 2.3.3 version?
nickmcminn60 said:
Epic Fail! So this should work with miui tomorrow after the 2.3.4 update? Can you post a 2.3.3 version?
Click to expand...
Click to collapse
I dont have a 2.3.3 source tree right now, so no. As for miui, probably, but I'm not officially supporting miui.
Sent from my SGH-I897 using XDA Premium App
TheEscapist said:
I dont have a 2.3.3 source tree right now, so no. As for miui, probably, but I'm not officially supporting miui.
Sent from my SGH-I897 using XDA Premium App
Click to expand...
Click to collapse
No worries, ill just flash with miui tomorrow.
This kernel didnt boot it just went to the screen with the little computer
Went into recovery and flashed another kernel and it booted smoothly.
Sent from my SGH-T959 using XDA App
es7241 said:
This kernel didnt boot it just went to the screen with the little computer
Went into recovery and flashed another kernel and it booted smoothly.
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
That's the custom boot screen. if the kernel didn't boot, you wouldn't have been able to get into recovery.
Sent from my SGH-I897 using XDA Premium App
i been running it for a day now
1.2 ghz smooth
1.3 ghz smooth
1.4 ghz starts to get choppy
1.5 ghz locks up reboots
1.6 un useable .
but its giving me good color, and operates pretty smooth at 1-1.3 ghz
brian(: said:
i been running it for a day now
1.2 ghz smooth
1.3 ghz smooth
1.4 ghz starts to get choppy
1.5 ghz locks up reboots
1.6 un useable .
but its giving me good color, and operates pretty smooth at 1-1.3 ghz
Click to expand...
Click to collapse
It sounds like you're unstable at the higher frequencies. Try playing with the voltages settings (I can't run 1.5 without undervolting), that might help.
Sent from my SGH-I897 using XDA Premium App
TheEscapist said:
It sounds like you're unstable at the higher frequencies. Try playing with the voltages settings (I can't run 1.5 without undervolting), that might help.
Sent from my SGH-I897 using XDA Premium App
Click to expand...
Click to collapse
what settings do you reccomend ?
brian(: said:
what settings do you reccomend ?
Click to expand...
Click to collapse
Its different for every phone. If you want something to start off with, there is lots of people who have posted theirs in my captivate thread, and there is also an overclocking/undervolting guide by shaolin in the captivate forums.
Sent from my SGH-I897 using XDA Premium App
TheEscapist said:
Its different for every phone. If you want something to start off with, there is lots of people who have posted theirs in my captivate thread, and there is also an overclocking/undervolting guide by shaolin in the captivate forums.
Sent from my SGH-I897 using XDA Premium App
Click to expand...
Click to collapse
ah, nonee seem to be working, i got 1.4 ghz to run tho, but im only getting 1744 in quadrant?
brian(: said:
ah, nonee seem to be working, i got 1.4 ghz to run tho, but im only getting 1744 in quadrant?
Click to expand...
Click to collapse
Because Quad scores are the be all and end all of a phone. (fyi: I pull anywhere from 1900 to 2600 at 1.55ghz).
If you're concerned, run linpack or some other cpu intensive task. If you keep getting an "Inaccurate" error in Linpack, you're probably unstable at that frequency, which could cause crashing, lag, slowness, etc.
Been running this for about 15 minutes and its running good so far, but one question how dangerous is this to the phone running at 1.5ghz as compared to 1.3ghz?
Sent from my SGH-T959 using XDA App
es7241 said:
Been running this for about 15 minutes and its running good so far, but one question how dangerous is this to the phone running at 1.5ghz as compared to 1.3ghz?
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
Any overclocking reduces the lifespan of a device, though typically from decades down to several years to a decade. Voltage wise, its a 100mv increase (though you can decrease it). It shouldn't be that much of a difference, and ive been at 1.5 for a while now, but obviously, there's always a chance.
Sent from my SGH-I897 using XDA Premium App
TheEscapist said:
Any overclocking reduces the lifespan of a device, though typically from decades down to several years to a decade. Voltage wise, its a 100mv increase (though you can decrease it). It shouldn't be that much of a difference, and ive been at 1.5 for a while now, but obviously, there's always a chance.
Sent from my SGH-I897 using XDA Premium App
Click to expand...
Click to collapse
Thanks for the quick reply, I have voltage for 1.5, 1.4, & 1.3ghz to -25 , and the rest stock , ill see how that goes because either way ill probably end up buying a new phone soon 8)
Sent from my SGH-T959 using XDA App
es7241 said:
Thanks for the quick reply, I have voltage for 1.5, 1.4, & 1.3ghz to -25 , and the rest stock , ill see how that goes because either way ill probably end up buying a new phone soon 8)
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
Just watch you temp. Run it at 130f all the time it wont last a month.....just keep it cool.....
nickmcminn60 said:
Just watch you temp. Run it at 130f all the time it wont last a month.....just keep it cool.....
Click to expand...
Click to collapse
Not sure what that is in celcius (Canadian here), but under 45c is a good limit to aim for. Charging cuts off around there, not sure the exact value off the top of my head.
Sent from my SGH-I897 using XDA Premium App
Introducing the new variant of Bali kernel, Bali for CM7. The main goal of this kernel is the same as other Bali kernel, balanced performance and battery life. I can't guaranteed you will get the same battery life as Bali for Froyo but you will definitely get an improve battery life over stock kernel.
Features:
- OC/UV up to 1.4GHz (Safe boot to 1GHz) [require setCPU from market]
- Voodoo Sound v10
- Voodoo Color
- Multiple CPU governor, smartass included (default: ondemand)
- Multiple IO scheduler (default: BFQ)
- LED notification support (no external app required)
- CIFS support
- Support SetCPU screen off 100/400 profile
- Dock sound redirector support [need Galaxy Dock Sound Redirector app from market]
Disclaimer:
As always, I'm not responsible with any damage cause to your phone.
Special Thanks:
- Team Whiskey - you guys are awesome.
- Alexia - for great work on the new splash image.
- Supercurio - for awesome work on Voodoo
- xcaliburinhand - for wonderful work on dock sound redirector.
- Everybody at CM dev community for their hard work on this awesome ROM.
- Everybody at #teamwhiskey for beta testing this kernel and their support.
I apologize if I miss anyone ..
Flashing Instruction:
- If you're coming from another kernel, flash "Ultimate Kernel Cleaning Script" by lippol94 first (http://www.multiupload.com/XFH1GCK4MB)
- Once that's done .. then flash Bali-CM
If you don't know how to flash then this is not for you.
Download:
Bali-CM_v2.2.2
Change Log:
Code:
- 2.2.2 [10/18/2011]
CM update
Re-enabled LED by default
- 2.2.1 [9/12/2011]
Fixed screen jitter issue
- 2.2 [9/10/2011]
Upgraded BFQ to v2
Added Smartass v2 with extra tweak
Fixed ondemand and tweaked for smoother experience
Set ondemand as default governor
Other fixes and tweaks
- 2.1 [9/1/2011]
Disabled SLQB and revert back to SLUB
Disabled LED notification for the time being
Added more UV settings
GPU tweaks
Added v(r) scheduler
Added Tiny Preempt RCU
And other tweaks and fixes
- 2.0 [8/25/2011]
Disabled ramzswap and switched to zram
Enabled zcache for better IO performance
Memory tweak, now gives you 340MB
More tweaks
- 1.2.1 [8/19/2011]
Fixed video playback issue
Fixed battery report when charging, it goes to 100% now
- 1.2 [8/18/2011]
Updated source with the latest CM patches
Added SLQB slab allocator for better memory management
Added more tweaks
- 1.1.1 [7/26/2011]
Fixed kernel instability that cause random reboot
- 1.1 [7/26/2011]
Added Voodoo color V2
Fixed UV portion to make it easier to manage
Added Voltage Control support
Added compiler tweak
- 1.0 [7/22/2011]
Initial release
A little explanation on different governors (taken from Lord ClockAn thread):
- interactive - Instead of sampling the cpu at a specified rate, the governor will scale the cpu frequency up when coming out of idle. When the cpu comes out of idle, a timer is configured to fire within 1-2 ticks. If the cpu is 100% busy from exiting idle to when the timer fires then we assume the cpu is underpowered and ramp to MAX speed.
- smartass - Is an improved version of interactive governor
- ondemand – Available in most kernels, and the default governor in most kernels. When the CPU load reaches a certain point (see “up threshold” in Advanced Settings), ondemand will rapidly scale the CPU up to meet demand, then gradually scale the CPU down when it isn't needed.
- conservative – Available in some kernels. It is similar to the ondemand governor, but will scale the CPU up more gradually to better fit demand. Conservative provides a less responsive experience than ondemand, but can save battery.
- performance – Available in most kernels. It will keep the CPU running at the “max” set value at all times. This is a bit more efficient than simply setting “max” and “min” to the same value and using ondemand because the system will not waste resources scanning for CPU load.
- powersave – Available in some kernels. It will keep the CPU running at the “min” set value at all times.
- userspace – A method for controlling the CPU speed that isn't currently used by SetCPU. For best results, do not use the userspace governor.
Q and A:
My screen has green, yellow, or orange tint.
Use Voodoo Control to set color profiles (courtesy of d_phekt)
Screen RGB Multipliers:
Red = 230996000
Green = 230996000
Blue = 2704668800
Screen v1 Gamma Hack:
Red = -50
Green = -53
Blue = -44
is GPS still functional with this kernel?
gamikzone said:
is GPS still functional with this kernel?
Click to expand...
Click to collapse
Yes .. GPS still functional.
drhonk said:
Yes .. GPS still functional.
Click to expand...
Click to collapse
im about to flash this hows ur battery life compared to stock? im getting pretty good battery on stock who knows how great it will be with this
gamikzone said:
im about to flash this hows ur battery life compared to stock? im getting pretty good battery on stock who knows how great it will be with this
Click to expand...
Click to collapse
Just like other Bali kernel .. it takes 2 - 3 days to settle in, but my beta testers reported anywhere from 15 - 20 hrs average. I myself got 18hrs with 2 push email accounts, twitter, sms, and few calls.
drhonk said:
Just like other Bali kernel .. it takes 2 - 3 days to settle in, but my beta testers reported anywhere from 15 - 20 hrs average. I myself got 18hrs with 2 push email accounts, twitter, sms, and few calls.
Click to expand...
Click to collapse
thats good im getting around 14 hours with stock, have u tried the ondemand setting for your cpu? i seem to get better battery life with that compared to conservative
gamikzone said:
thats good im getting around 14 hours with stock, have u tried the ondemand setting for your cpu? i seem to get better battery life with that compared to conservative
Click to expand...
Click to collapse
Try smartass with this kernel ..
drhonk said:
Try smartass with this kernel ..
Click to expand...
Click to collapse
i think i will try this out tonight
I believe this will be ok to use with miui.
Nice animation.
Looks like not meant for Miui. after seeing the animation (Approved Cyanogen Bali), it turns black and wont turn on. Need to pull the battery.
jay661972 said:
I believe this will be ok to use with miui.
Nice animation.
Click to expand...
Click to collapse
Trying it out , any recommeneded UV settings?
Sent from my T959 using XDA App
jay661972 said:
Looks like not meant for Miui. after seeing the animation (Approved Cyanogen Bali), it turns black and wont turn on. Need to pull the battery.
Click to expand...
Click to collapse
It does work on miui,
Sent from my T959 using XDA App
drhonk said:
Try smartass with this kernel ..
Click to expand...
Click to collapse
would downloading SetCPU and just setting the governor to smartass improve battery life? or do you have to actually UV and all that
Really, how did you do that? I did the clean script first and flash Bali.
es7241 said:
It does work on miui,
Sent from my T959 using XDA App
Click to expand...
Click to collapse
Okay I will try this one more time.
jay661972 said:
Okay I will try this one more time.
Click to expand...
Click to collapse
confirmed .. it works on MIUI since I just flashed MIUI with it.
jay661972 said:
after seeing the animation (Approved Cyanogen Bali), it turns black and wont turn on. Need to pull the battery.
Click to expand...
Click to collapse
Same here except im flashing from trigger redux #12 and ive tried flashing from trig w/glitch and w/du jour
Sent from a cell tower to the XDA server to you.
now that's the trick. if you have glitch kernel, you need to re-flash stock miui rom then flash Bali. It works now for me
drhonk said:
confirmed .. it works on MIUI since I just flashed MIUI with it.
Click to expand...
Click to collapse
jay661972 said:
now that's the trick. if you have glitch kernel, you need to re-flash stock miui rom then flash Bali. It works now for me
Click to expand...
Click to collapse
So you can't flash bali on miui energy? You have to revert to stock miui?
Sent from my T959 using XDA Premium App
ok, nothing seemed to be making the touchscreen responsive with the ICS beta n its derivatives.
except one thing just did.
i changed the sampling rate from 200000(2 lak) to 20000 (20 hazar), n of course i had to change the up-threshold so i changed that to 95 (i did all these in rom-toolbox's kernel tweaks settings)
now everything is super-responsive (app startups, physical buttons, onscreen buttons, switching, yo name it) N while you are just lets say reading stuff on the screen, the cpu is generally at its lowest
what that means is : both responsiveness and higher battery.
please comment.
UPDATE : check the 7th post on this forum for more tweaks for snappy app launching n switching here http://forum.xda-developers.com/showthread.php?t=1570374#post24186676
UPDATE : ADDITIONAL TWEAK (more battery life) : in rom-toolbox change powersave bias to 35 (in rom toolbox) : saves a lot more battery by preventing the cpu from rushing to full-frequency while you are doing simple tasks like flicking the screen.
UPDATE : 3/31/12 : an interesting observation about "force gpu" 's causing poor performance on my post here : http://forum.xda-developers.com/showthread.php?t=1570374&page=2#post24266342
UPDATE : 4/7/12 : want even more battery life n smoothness?
add these to your build.prop save , reboot into recovery, clean dalvik-cache and /cache partition then reboot into system. things should be faster. and oh, underclock it.
ro.kernel.android.checkjni=0
dalvik.vm.execution-mode=int:jit
ro.ril.disable.power.collapse=0
ro.mot.buttonlight.timeout=1
dalvik.vm.verify-bytecode=false
dalvik.vm.dexopt-flags=v=n,o=v
you can also do a semi-odex using titanium backup's integrate system dalvik into rom thing, but then you won't be able to change any file in the rom (like applying patches, mods etc until you've either done undo integration thing in titanium backup or just used adb shell to delete *.odex from /system/apps n rebooted)
UPDATE : 4/28/12 : if you are using a derivative of the .562 ICS then you can change the kernel tweaks/sysctl settings to dirty_ratio = 80 dirty_background_ratio = 20 and vfs_cache_pressure = 20 to get snappy app startups up_threshold and powersave_bias can both be set to 90 and select ignore_nice_load. if you use lots of apps then raise the dirty background ratio and dirty ratio both by 15 points and reduce vfs_cache_pressure by 15 for low cpu usage while the apps are running. i've noticed that many of the custom roms have started getting my tweaks or similars preincluded , plus the official ics is much better than icsbeta in memory management. and oh, use arcknight kernel. its super awesome for both features and battery life. i switch my governor to interactivex or smartassv2 when i am recording using the 14mbps camcorder mod, and then back.
the android backup & restore under person in settings should be turned off. it takes a lot of cpu, battery, data n memory. its aweful.
if this works for you, press the thanks button.
How can this be done?
Duvel999 said:
How can this be done?
Click to expand...
Click to collapse
i used rom toolbox pro, its free version is available here - https://play.google.com/store/apps/details?id=com.jrummy.liberty.toolbox
anything else that can edit sysctl.conf (e.g. https://play.google.com/store/apps/details?id=com.jrummy.sysctl.config and https://play.google.com/store/apps/details?id=scd.atools ) will also work.
Gonna try it
system seems to be a bit snappier
thx mate
thnx mate.
for snappy app switching i discovered another bunch of settings
in rom toolbox's kernel tweaks under performance, change min free kbytes to [CORRECTION]8192[not 8096] (or [UPDATE] 6144 - whichever one you like), dirty ratio to 95, dirty background ratio to 70 and vfs cache pressure to 5 (n of course check the apply on boot option)
let me know how you like this additional tweak
UPDATE: some observations ; high dirty ratio causes lower cpu usage n faster app-switching, low dirty background ratio causes faster app startups but uses too much cpu, vfs cache pressure above 5 or 10 causes high cpu usage n lags. (i use lots of apps)
UPDATE #2 FURTHER IMPROVEMENTS (fast all around with acceptable cpu usage, super app switching, n decently fast launcher without sacrificing cpu-speed n battery life)
Kernel Tweaks :
reduce dirty background ratio to 50
check the OOM kill allocating task (if your device crashes after this, uncheck this, it may kill the android system n android os processes as well in some cases)
Auto Memory Manager :
foreground 6
visible 8
secondary 32
hidden 40
content 48
empty 120
Thnks
[white10char]
The up-threshold and powersave bias settings do not stick for some reason. They return to default values after a reboot even though Apply on boot is checked.
Sent from my LT15i (Xperia arc) on KA ICSony
sunbriel said:
The up-threshold and powersave bias settings do not stick for some reason. They return to default values after a reboot even though Apply on boot is checked.
Sent from my LT15i (Xperia arc) on KA ICSony
Click to expand...
Click to collapse
It is the same for me. I guess we'll have to review each init.d script to see what is the one that is changing these values on restart.
estuardo4 said:
It is the same for me. I guess we'll have to review each init.d script to see what is the one that is changing these values on restart.
Click to expand...
Click to collapse
perhaps kickass kernel script
sunbriel said:
The up-threshold and powersave bias settings do not stick for some reason. They return to default values after a reboot even though Apply on boot is checked.
Sent from my LT15i (Xperia arc) on KA ICSony
Click to expand...
Click to collapse
estuardo4 said:
It is the same for me. I guess we'll have to review each init.d script to see what is the one that is changing these values on restart.
Click to expand...
Click to collapse
check the 98kickasskernelizer (i'd find the respective values - especially min-free n change them in the script itself), there are two other not so popular scripts out there too that you may be using.
please share with us whatever was causing the overriding of rom toolbox's (or sysctl etc)'s settings.
Hey there thanks for the tip. Already tried it but I don't think there's any major improvement. In fact, antutu graphic score is down a bit. But don't know why. Maybe just my phone.
sent from my white ray using XDA App
hansip87 said:
Hey there thanks for the tip. Already tried it but I don't think there's any major improvement. In fact, antutu graphic score is down a bit. But don't know why. Maybe just my phone.
sent from my white ray using XDA App
Click to expand...
Click to collapse
the benchmarks dont tell you about usability. better responsiveness is due to faster cpu response to situations.
antutu's benchmark tests for continuous high performance (battery hogging w/lags) while running just one app.
my settings are for giving great experience (touch, app switching and app launching as well)
think of it as antutu being a mr. universe test, while mine are a gymnastics olympics tournament.
Well thanks. A lot less sluggish when scrooling..
Sent from my LT18i using XDA
darth5zaft said:
Well thanks. A lot less sluggish when scrooling..
Sent from my LT18i using XDA
Click to expand...
Click to collapse
thank you.
i just posted another slight tweak for higher battery life. its in the first post.
sunbriel said:
The up-threshold and powersave bias settings do not stick for some reason. They return to default values after a reboot even though Apply on boot is checked.
Sent from my LT15i (Xperia arc) on KA ICSony
Click to expand...
Click to collapse
estuardo4 said:
It is the same for me. I guess we'll have to review each init.d script to see what is the one that is changing these values on restart.
Click to expand...
Click to collapse
i tried 6144, restarted n it sticks. try 8192 (i haven't tried restarting after that) : my 8096 was a mistake - i accidently doubled 1024 to 2048 n that to 4096 and then stupidly to 8096.
it is possible that numbers that are not multiples of 1024 are ignored if set on boot.
that occurred to me since init.d scripts are loaded much before rom-toolbox gets a chance to do its magic.
estuardo4 said:
It is the same for me. I guess we'll have to review each init.d script to see what is the one that is changing these values on restart.
Click to expand...
Click to collapse
Could it be that these settings are conflicting with Supercharger?
Sent from my LT15i (Xperia arc) on KA ICSony
hootnath said:
i tried 6144, restarted n it sticks. try 8192 (i haven't tried restarting after that) : my 8096 was a mistake - i accidently doubled 1024 to 2048 n that to 4096 and then stupidly to 8096.
it is possible that numbers that are not multiples of 1024 are ignored if set on boot.
that occurred to me since init.d scripts are loaded much before rom-toolbox gets a chance to do its magic.
Click to expand...
Click to collapse
I tried and it stuck after a reboot. It is working fine now. My battery is lasting more indeed, but wifi is always on, even after I made the suggested changes. I guess I'll have to reinstall Doomkernel v04 and JJ's ROM from scratch. But even with wifi always on, I'm having better battery life and less lag.
Thank you again.
estuardo4 said:
I tried and it stuck after a reboot. It is working fine now. My battery is lasting more indeed, but wifi is always on, even after I made the suggested changes. I guess I'll have to reinstall Doomkernel v04 and JJ's ROM from scratch. But even with wifi always on, I'm having better battery life and less lag.
Thank you again.
Click to expand...
Click to collapse
i found another interesting thing today.
the force GPU for 3d in the settings -> developer options actually uses a lot of the cpu and causes lags. i turned it off and have instead done the following
Get rid of CPU rendering:
Navigate to /system/lib/egl/
Open the file named "egl.cfg"
Delete the first line. It should say "0 0 android" or something similar
Go back into the egl folder and delete libGLES_android.so
What this does is remove the entire soft-rendering pathway from the OS.
source : http://www.ifans.com/forums/threads/ics-performance-tweaks.369959/ ;
now, i have changed the powersave bias in teh romtoolbox's kernel tweaks to 95 instead of {correcton}35{not]95. the cpu is spending more time @ 122mhz and deep sleep now without lags (which means more battery)
if this thing works for you, please press thanks.
*** Disclaimer
I am not responsible for any kind of damage to your device,
or in case it explodes, your surroundings.
Please use it at your own risk!
Click to expand...
Click to collapse
Features :
-O3, Cortex-A53, NEON, VFPv4 optimizations
Compiled from latest Linaro GCC 4.9.3 2015.02 Toolchain [Christopher83]
Upstreamed to 3.10.71 from kernel.org, from 3.10.28
Asynchronous Fsync ported from HTC Devices
Dynamic Fsync v2.0 [faux123/varunchitre15]
PowerSuspend v1.7 driver support (replaces EarlySuspend) [yank555.lu & faux123]
Android early_suspend/late_resume PM kernel driver framework has been
deprecated by Google. This new powersuspend PM kernel driver is a replacement
for it.
Conserves battery much better.
Triggered by Screen on/off.
Intelli_plug v3.9 driver [faux123]
Intelligent hotplug cpu driver with eco mode.
KCAL - Advanced color control
Disabled MMC CRC check for extra 30% boost in IO
Reduced debugging = More performance
Simple GPU Algorithm [faux123]
FIOPS, BFQ + stock I/O Schedulers
Filesystems support : NTFS, F2FS
Sysfs implementation for changing vibrator intensity [varunchitre15]
Zswap, Frontswap and znswap [faux123]
Support for kernel-mode NEON [faux123]
Increased charging current to 1.2A
Frandom - Fast Kernel Random Number Generator driver added
Added ARM NEON Crypto functions
Click to expand...
Click to collapse
Download :
Velocity v1.1 <- Mirror
Velocity v1.0 <- Mirror
Camera Fix
Changelog :
v1.1
- Added KCAL - Advanced color control (Thanks to @savoca for his great job) check this thread for more info
- Numerous fixes from android kernel_common 3.10 and 3.10.y repos.
- Enabled Conservative governor
v1.0
- Initial release
Installation :
1. Download and save the latest zip to your phone
2. Flash this zip from any custom recovery (eg. TWRP, CWM, Philz)
3. If camera doesn't work, perform steps 1 & 2 for the zip containing camera fix
Recommended Settings :
Min. CPU freq. : 400MHz (Under this might cause SOD)
GPU Governor : simple_ondemand
I/O Scheduler : FIOPS
Read-ahead size : 1536 kB
Intelliplug profiles :
* For general use : Eco Performance/Eco Conservative
* For gaming : Balanced/Disabled
Kernel apps : FauxClock, Kernel Adiutor, Trickster MOD
Credits :
@varun.chitre15
@faux123
@Christopher83
XDA:DevDB Information
Velocity Kernel, Kernel for the YU Yureka
Contributors
neomanu
Source Code: https://github.com/neomanu/android_kernel_yu_msm8916/tree/cm-11.0_exp
Kernel Special Features:
Version Information
Status: Stable
Current Stable Version: v1.1
Stable Release Date: 2015-03-11
Created 2015-03-07
Last Updated 2015-03-11
Reserved
ooo new kernel...
hello bro first of all thanks for contributions towards Development of yu yureka..
Now downloading...
FEEDBACK AFTER SOME HOURS OF PLAYING....
Hey, can I flash it directly on other custom kernel
screen shots??
ankurvvvv said:
screen shots??
Click to expand...
Click to collapse
Its a kernel not a rom. What do you need screenshots of?
My bad. too excited with my new Yureka that not paying attention to anything
flashed this kernel and used it for 5 hrs.
Good BATTERY command.
i attended a con-call for 90 plus minutes and battery drained only 5%
No lag while using basic games like clash of clan or clash of lords
Issues identified
screen black out while on call, you cant control your calls like add new call or check text while you are on phone calls. but no issue in voice and reception.
while making call you cant drop call as screen goes black out.
No heating issue as far i observed.
colour reproduction is good.
seems need little fine tune can make this kernel a must install.
All the very best to develops
Regards
question
MIUI custom ROM supported???
sunilnair007 said:
flashed this kernel and used it for 5 hrs.
Good BATTERY command.
i attended a con-call for 90 plus minutes and battery drained only 5%
No lag while using basic games like clash of clan or clash of lords
Issues identified
screen black out while on call, you cant control your calls like add new call or check text while you are on phone calls. but no issue in voice and reception.
while making call you cant drop call as screen goes black out.
No heating issue as far i observed.
colour reproduction is good.
seems need little fine tune can make this kernel a must install.
All the very best to develops
Regards
Click to expand...
Click to collapse
you are talking about proximity sensor issue , is it right?
Sent from my AO5510 using XDA Free mobile app
Review after using a whole day.
1. First & best intelli_plug driver - loved the live and smooth activation and deactivation of cores acc to load. only single core runs while using light apps (whatsapp,hike,tapatalk etc) i.e. full utilization of a single core.
2. Highly customizable using the FauxClock pro app.
3. cpu temp was usually higher (50-60 degrees) than my last kernel (Tz).
4. As @sunilnair007 posted the screen goes black while call. But one thing i noticed was when i press just at the side of proxi sensor the screen wakes up Exactly same as the Yureka proximity issue but on all other kernels the proxi was working fine on my phone (stock, thunderzap)...
5. i didn't used the phone for an hour or so i.e. phone was in deep sleep the i tried to wake up the device by the power button several times but finally had to remove battery and put again and booted the device :c
and after turning on the battery was 12% (earlier it was above 75%) and it was increasing by itself >.> battery usage graph ss --- i.imgur.com/y9QCyCz.png
and after keeping it turned off for sometime and restarting the battery got stable at 46% and started decreasing as per usage. (so got much less battery backup)
How to make best use of it.
Installed this kernel.
However, it seems very complex to make best use of it by a person like me who is not used to Custom Kernels. Before this I have used ThunderZap2, and Xcelerate, without much of tweaking. In Xcelerate for example, I found that different cores where shutting down by default. Here all the core are working by default. Obviously with this Kernel it seems I will have to do some tweaking.
I have also installed Kernel Adiutor as recommended in OP. However, information on recommended setting is too sketchy.
Would like to more detailed information as how to tweak / set this kernel to make best use of it.
tons of thanks to you bro... for kcal addition
Bro thanks a lot for adding kcal colour management to YU yureka..
Very nice bro..
One thing bro the hotplug is only working with 4 cpu of first cluster only...
I'm using kernel audiutor beta...
And please rommended any setting to run it cooller because comparing to other custom kernel it run little high temp..
Otherwise working grate.....
[KERNEL][3.10.71][KCAL] Velocity v1.1
Seems developer worked hard and results are visible.
No complaints so far testing since morning.
Need 2 days time to give a stable review.
Best wishes and please keep this spirit intact
Regards
Tarry! said:
5. i didn't used the phone for an hour or so i.e. phone was in deep sleep the i tried to wake up the device by the power button several times but finally had to remove battery and put again and booted the device :c
Click to expand...
Click to collapse
Noticed this too. Pressing the volume buttons once/twice, when it is unresponsive, wakes it right back up.
esukhdev said:
Here all the core are working by default. Obviously with this Kernel it seems I will have to do some tweaking.
I have also installed Kernel Adiutor as recommended in OP. However, information on recommended setting is too sketchy.
Would like to more detailed information as how to tweak / set this kernel to make best use of it.
Click to expand...
Click to collapse
Firstly, I'll try to simplify the recommended settings.
Secondly, hotplugging is not enabled by default.
Enable it by going to CPU Hotplug in Kernel Adiutor and enabling Intelliplug.
DGEEEK said:
One thing bro the hotplug is only working with 4 cpu of first cluster only...
I'm using kernel audiutor beta...
And please rommended any setting to run it cooller because comparing to other custom kernel it run little high temp..
Otherwise working grate.....
Click to expand...
Click to collapse
Set the Intelliplug profile to Eco Conservative/Eco Performance to hotplug upto 7 cores.
I'm looking into the cluster problem as mentioned.
To run cooler, try reducing the max frequency.
Tarry! said:
1. First & best intelli_plug driver - loved the live and smooth activation and deactivation of cores acc to load. only single core runs while using light apps (whatsapp,hike,tapatalk etc) i.e. full utilization of a single core.
2. Highly customizable using the FauxClock pro app.
3. cpu temp was usually higher (50-60 degrees) than my last kernel (Tz).
4. As @sunilnair007 posted the screen goes black while call. But one thing i noticed was when i press just at the side of proxi sensor the screen wakes up Exactly same as the Yureka proximity issue but on all other kernels the proxi was working fine on my phone (stock, thunderzap)...
5. i didn't used the phone for an hour or so i.e. phone was in deep sleep the i tried to wake up the device by the power button several times but finally had to remove battery and put again and booted the device :c
and after turning on the battery was 12% (earlier it was above 75%) and it was increasing by itself >.> battery usage graph ss --- i.imgur.com/y9QCyCz.png
and after keeping it turned off for sometime and restarting the battery got stable at 46% and started decreasing as per usage. (so got much less battery backup)
Click to expand...
Click to collapse
Regarding point 5 , I faced same behavior in TZ as well xccelerate kernel.I don't understand the problem.the battery completely drained out and more heat on backside of the mobile.whenever if i would make any changes on IO SCHEDULER or governed faced the issue.
Sent from my AO5510 using XDA Free mobile app
androidgalaxyman said:
Regarding point 5 , I faced same behavior in TZ as well xccelerate kernel.I don't understand the problem.the battery completely drained out and more heat on backside of the mobile.whenever if i would make any changes on IO SCHEDULER or governed faced the issue.
Sent from my AO5510 using XDA Free mobile app
Click to expand...
Click to collapse
The issue is that if you set performance profile to "Power save", gov "ondemand" & min frequency lesser than 500MHz, phone sleeps to death & you have to hard reboot to get back on. Its a known bug and is present in stock kernel too. Check if settings i stated are the reason for you. Doesn't happen with "Interactive" because it never scales lower.
Sent from my AO5510 using XDA Free mobile app
@neomanu , Do I need to wipe cache and dalvik cache while flashing this kernel over any ROM. Also I have flashed a custom kernel previously and now I want to flash this, so Should I simply follow your instructions or need to wipe something.
No Need to wipe anything. To give u extra boost you can wipe dalvik cache which will rebuild cache again and its always good. no need of cache or data wipe
Is this kernel support's volte?
Sent from my AO5510 using XDA-Developers Legacy app