[MOD][DEPRECATED] Overclock support - LG Optimus Black

Content deprecated and removed to avoid confusion.

Note 31/07/2011: Updated for Nova Script
Note 10/08/2011: The method is a bit different but you get the overall idea after reading this
II. How to overclock (applies to Nova)
So, you just want to overclock eh?
Ok, you have several ways to do this:
a) Using Nova built-in overclock script
b) Typing commands by hand (terminal, adb, etc)
(No, SetCPU does not work on OMAP devices, only for choosing governors)
I will also cover how you get your Optimus Black to auto-overclock (at least in Nova).
But first of all, very very important, please open this spreadsheet - it has a listing of values of clocks and the corresponding voltages which can be: stock ones, low ones, ultra low ones and high ones. For speed & battery compromise, I suggest low ones. However, if you're a gamer, you better stick with stock for instance.
Print that.
Done? let's move on.
a) Using Nova built-in overclock script
Now, I made a hilariously simple script for you to use on Nova to facilitate your overclock.
You just have to open the terminal application and:
Type "su" (without ""), press enter, click allow if it asks - very important step (needs root).
Type "nova" (without ""), press enter and congratulations, you've just entered the nova (overclock) script!
There just choose "overclock!". Remember, first the voltage, then the clock.
For example:
Type "su" (without "") on terminal, press enter. Click allow if it asks.
Type "nova" (without "") on terminal, press enter.
Type "1" (without "") and press enter.
Type "62" (without "") and press enter.
Type "1100000" (without ""; this is 1.1 Ghz) and press enter.
Enjoy your overclocked and undervolted phone.
Oh, terminal emulator has some kinks:
- If your keyboard disappears hit menu button and click 'toggle soft keyboard'.
- If you exit and it stays on the statusbar, re-enter terminal, hit menu button and click 'reset'.
P.S. You can also run this via ADB.
But how to auto-overclock on boot?
Now in latest Nova Script it will ask you if you want to set them on boot!
If by some reason you didn't test and found out that your device is stable with those settings and you can't boot your device or if it does it's all laggy and craps, you can just power it off, remove microSD card, use an adapter and put it on your PC or laptop and remove the file, then insert the microSD card back and reboot the phone. I chose a file in the microSD card especially because of this safeguard.
b) Typing commands by hand
If you're feeling too pro for the overclock script, you can just type them by hand:
- echo "xx" > /proc/overclock/max_vsel
- echo "xxxxxxx" > /proc/overclock/max_rate
If you want to auto-overclock, use the same method as above.
This is it. Simple.
A few reminders:
Voltage first; then frequency.
Check the table in the beginning of the post for frequencies and recommended voltages
Frequency has to be for example 1200000, not 1.2. It's in Mhz, not Ghz.
Test the **** out of your device with a frequency/voltage before setting it at boot.
Most Optimus Black won't be stable beyond 1.2 Ghz.
If you can't boot or are having problems because of auto-overclock, just delete the file.
Done.

Sorry for the delay, I'm finished now.
Time to go upload Nova v1.7.27.

Instructions updated; I forgot the "su" part.

Thanks for the detailed tutoring!

Thanks! I really appreciate this

Interesting...
From where have you obtained the recommended voltaje/freq?
Thanks!

From a reference of Droid X which uses the same chipset as us.

my first thing is to set the min freq to about 100Mhz XD

Is not working...
After boot, cat /proc/overclock/max_rate says 550000
Changing auto_ocuv in /sdcard/nova/overclock/ has no effect. After reboot, the same 550000...
Changing manually with oc script works, after that the report is correct.
Anyway, is not much difference between the two cases... It seems a little bit increased speed, but maybe is just me...
I used 62 and 1150000...
Untill now it is OK.
How the setting must be arranged in auto_ocuv? Mine is 621150000.. Is this correct?

rgabi88 said:
Is not working...
After boot, cat /proc/overclock/max_rate says 550000
Changing auto_ocuv in /sdcard/nova/overclock/ has no effect. After reboot, the same 550000...
Changing manually with oc script works, after that the report is correct.
Anyway, is not much difference between the two cases... It seems a little bit increased speed, but maybe is just me...
I used 62 and 1150000...
Untill now it is OK.
How the setting must be arranged in auto_ocuv? Mine is 621150000.. Is this correct?
Click to expand...
Click to collapse
That's because you have vold/179:16.
It works for 179:17.
Today I will get it working for everyone. I suppose you can't also use App Inj.
But no worries, just wait for today's version.

Noejn said:
From a reference of Droid X which uses the same chipset as us.
Click to expand...
Click to collapse
That's why quadrant advanced bar results precentage is very similar. Both suck in cpu processing very nice in I/O hhahaha.
Sent from my LG-P970 using Tapatalk

Noob question, could optimus black get more overclock potential with Android 2.3 ? Or always unstable with 1.2 ghz+ ?

Thanks! Using your overclock, I could overclock my Optimus Big (Only for Korea)!
I used 1200/64... However I tried to overclock my phone more than 1.2GHz, but I can't do that. It's so hard to find right voltage for 1.3GHz or 1.25GHz

Hi I'm new to this. What is the different between overlocking and unlocking a the phone? Thanks.

Related

[HOWTO] renice live wallpapers to speed up UI

This is quite a simple howto and I don't even know if it's appropriate to post it here instead on legend general. I post here as it requires root privileges, if someone think this is the wrong section for it just ask a mod to move it somewhere else
This (quite simple) howto is intended if you are experiencing lags or slowdowns with live wallpapers, and it's working very well for me. I think most of you can do this without an howto but I hope someone less experienced in messing with terminal will find it useful I just try to help.
Will work better if you disable the wallpaper scrolling in the launcher's properties. The thread is titled 'renice live wallpapers' but I found it works better to renice the launcher. However you can try both
I would like to thank BlaY0 for the help.
you'll need:
- root privileges
- a terminal emulator
- live wallpapers
- GScript
what you have to do is:
- download GScript from market (lite or paid version, works with both)
- launch it, then press Menu/Add script
- give it a name, be sure to check 'Needs SU', then type this in the text field below
renice -15 `pgrep android.process.acore'
where android.process.acore is the LauncherPro process name. If you're using another launcher you have to do a google search and find its
process name
- now save, and try executing it and see if it works
- add a shortcut to GScript on your home which launches the script. With this approach you have to launch it after every reboot
Maybe you want to try to renice the live wallpaper too (this may slow it down, I would not suggest to do it). To do this
- launch the terminal
- write 'ps' then press enter
- will appear a list of processes. here you should find one that has a name similar to the LWP you're using (for example, I'm using Pixel Zombies Infection and the process name is haydenTheAndroid.liveWallpaper.pixelZombies)
now you can renice it either from terminal or from GScript.
To renice from terminal:
- check the number *** which the process has in the PID row. You have to remember this number
- write 'su' then press enter. now you have root privileges
- write 'renice N ***' where N is the nice number you want (20=minimum priority ; -20=maximum priority, which you obviously don't want). You can set it to 20 to give the LWP the minimum priority
To renice from GScript go in the script you already created and add a similar line, by substituting "-15" with "20" and the process name with your LWP's process name.
You should now see an increased smoothness when scrolling homescreens and app drawer
wow will try...............
FOLLOW ME http://smartsreenath.blogspot.com/
Thanks, let me know
Sent from my Legend using Tapatalk
Corra said:
...
what you have to do is:
- launch the terminal
- write 'ps' then press enter
- will appear a list of processes. here you should find one that has a name similar to the LWP you're using (for example, I'm using Pixel Zombies Infection and the process name is haydenTheAndroid.liveWallpaper.pixelZombies)
- now check the number *** which it has in the PID row. You have to remember this number
- write 'su' then press enter. now you have root privileges
- write 'renice N ***' where N is the nice number you want (20=minimum priority ; -20=maximum priority, which you obviously don't want). You can set it to 20 to give the LWP the minimum priority
...
Click to expand...
Click to collapse
Just tried it out with the Light Grid LWP (com.joko.lightgrid) and ADW Launcher. All I can say is that this feeling is so smooth, it is like an angel pissed on my Legend just now
PS: I used adb instead of terminal emulator.
LOL this is pure poetry
Sent from my Legend using Tapatalk
Hi , i tried this and it really works!
But it is at the cost of the smoothness of the LWP i guess our puny 600mhz processor aint up to speed to handle LWP properly T^T
I oupdated with a script that does the procedure automatically but I'm encountering some issues with its permissions... no time to think about it now, will try again later
D-Lo said:
Just tried it out with the Light Grid LWP (com.joko.lightgrid) and ADW Launcher. All I can say is that this feeling is so smooth, it is like an angel pissed on my Legend just now
Click to expand...
Click to collapse
Hey, I'm the dev for Light Grid. Just wondering about performance issues - did you try the Battery Life slider in the Performance settings? That should lower the amount of time Light Grid spends taking up the CPU, which should help 'lag' issues.
Will this setting keep after a reboot?
Of course not...
You would need a script that would do that on every reboot.
JokoInteractive said:
...
Just wondering about performance issues - did you try the Battery Life slider in the Performance settings? That should lower the amount of time Light Grid spends taking up the CPU, which should help 'lag' issues.
Click to expand...
Click to collapse
I just tried your suggestion (overlooked it somehow ^^").
The LWP is indeed faster/smoother when maxed on 100fps, result? Terrible, terrible lag in the drawer. Also tried 15fps and no joy, the launcher is still suffering by it when opening the drawer (unless renice'd ofc ).
offtopic: My guess is that the lwp's are getting a little too high priority by default that actually make the launchers lag on a phone like this. Maybe even a rom setting?
I made a script but I don't know how to autorun it at boot. Unfortunately I'm very very noob
Sent from my Legend using Tapatalk
There are several possibilities:
find some app on market that does that
use GScript to run the script manually on every reboot
use run-parts approach through init.rc
run the script directly from init.rc
...there are some more.
until I figure out how to autostart the script at boot I updated the howto including GScript. thanks
I have written something about run-parts a while ago into dsixda's Kitchen thread in Chef Central subforum...
can anyone post the script?
Had not time to think about it but you can use it with GScript which is quite simple
Sent from my Legend using Tapatalk
I'd like to try this in form of SL4A script in order to use my already-running Tasker rather than gScript.
Do you guys have some hint for me to do this ?

rubiX Focused 2.0: Raising the Bar Another Notch!

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

[MOD] IncrediControl - Easy control of voltages and kernel settings!

Please read this post through thoroughly before downloading.
This app allows you to control your CPU voltages with an easy to use interface. You can increase or decrease voltages (undervolt or overvolt) for all frequencies or fine tune voltages for each individual frequency.
! HTC DEVICES, currently only single core devices are supported !
! ROOT is Required !
! Kernel that supports HAVS or SVS voltage adjustment REQUIRED !
In addition, if you are an Incredikernel user, the app may also be used to toggle Incredikernel specific features on and off, namely USB fast charging and audio boost.
Get it over at http://www.incredikernel.com
IncrediControl is now also available in the market:
IncrediControl
IncrediControl - Ad Free
Additionally, all donators are eligible to receive the Ad Free version. It doesn't matter how much or how little you donate or have donated. If you don't want to purchase the app from the market, you may donate using the button on this page. Please register on the site first and include your username in the comments box.
All previous donators, please register on the site if you have not done so and contact me with your username!
NOTE: The settings in the general tab are only functional in kernels that have implemented the simple sysfs interfaces for usb fast charging and audio boost. If you toggle them, its not going to break anything, but they won't work and the app may crash. If you would like your kernel dev to implement the interfaces, please direct them to these two commits:
https://github.com/Chad0989/android_kernel_common/commit/a7c21fa0391c225900f93960362535179c0cecc9
https://github.com/Chad0989/android_kernel_common/commit/41dc138bae23dc7582de72a4d9895aaa8e1f8b2d
NOTE2: It is a requirement of the HAVS adjustment that the kernel you are using has the HAVS sysfs interface implemented. If it does not, it will not work. Most non-stock gingerbread kernels have the HAVS adjustment. Very few sense kernels have the adjustment. I believe ziggy's latest is the only one that does.
NOTE3: Before using, please delete any boot scripts you may have in /etc/init.d that toggle any of the settings this app controls.
Get it at http://www.incredikernel.com
Restore script - use this if you went too low and find yourself in a boot loop. Flash through recovery:
http://www.incredikernel.com/?p=229
This excites me.
Neat
Sent from my Synergy Rom using Tapatalk
Great chad! Finally an app that does all the work.
Sent from my ADR6300 using XDA App
Hey Preview 2 has the HAVS, I think you should put the minus on the left of each number field. So that way it's like
- [voltage] +
mikeymop said:
Hey Preview 2 has the HAVS, I think you should put the minus on the left of each number field. So that way it's like
- [voltage] +
Click to expand...
Click to collapse
I concur. And will this work on the incredikernel?
J/k on the the question part (because I know someone will take that seriously ). Great work, chad.
Chad, here's something to ponder or consider. Please think about putting in some way to back-up your settings. That way when flashing new roms you could just restore from back rather than settings all again. Just a thought.
Great thanks!
I know viperboy was working on something similar.
I have to say though your aggressive undervolt package is the tits. It is rock solid for me, and I can't lower anything -25v from there without crashing.
RebelShadow said:
Chad, here's something to ponder or consider. Please think about putting in some way to back-up your settings. That way when flashing new roms you could just restore from back rather than settings all again. Just a thought.
Click to expand...
Click to collapse
That may come in the future.
@everyone: Anyone try it on other devices that have havs + sysfs interface? Evo, desire?
effing sweet..... no more term emulator for me
Chad, I've noticed that after I reboot the phone and go back into the app, the boxes for "set on boot" are unticked.
Also I know you already know this but it's sort of a pain in the ass to set the SD card speed (your other app) after every boot, so if you could do a "set on boot" for that one too that'd be awesome.
Keep up the good work, I like how every time I check back here you have a bunch of updates
I've noticed after installing a new nightly with no wipes, the values revert to stock, even with set on boot.
POQbum said:
Chad, I've noticed that after I reboot the phone and go back into the app, the boxes for "set on boot" are unticked.
Also I know you already know this but it's sort of a pain in the ass to set the SD card speed (your other app) after every boot, so if you could do a "set on boot" for that one too that'd be awesome.
Keep up the good work, I like how every time I check back here you have a bunch of updates
Click to expand...
Click to collapse
The boxes are unticked on purpose, so that the file is only written when you specify that you want to set the current settings on boot. The other option is to have it ticked when the boot script is found, but then you would have to untick it when you want to just play with voltages (but not change your boot script) and then tick it again to set on boot. Would everyone prefer it that way?
I should also specify that when you tick set on boot, you also must click set in order to truly set it on boot. There is also the option to have it write the file when set on boot is ticked. I just need to know what everyone's preference is.
SDspeed might be added to a future release and would have the set on boot option.
PonsAsinorem said:
I've noticed after installing a new nightly with no wipes, the values revert to stock, even with set on boot.
Click to expand...
Click to collapse
That's because new nightlies overwrite the /system folder where the boot script is stored. I'll probably add a backup option too so you can load the defaults, either that or change over to storing the values in a database and loading them via the app on boot as opposed to the boot script.
Looks cool.
Backup database - yes!
Default set on boot once it's been ticked - yes!
Thanks for this, Chad!
Zeam & Incredikernel
CM7 latest Nightly
7/19/2011 - Preview 3:
Changes include:
Added +/- All Min and All Max buttons
Reordered the + and – buttons to flank the voltages to clean up the layout a bit.
Removed the title bar for more vertical screen space
Next up is feature checking / disabling of functions your kernel doesn’t support as well as voltage checking.
Get it at http://www.incredikernel.com
Here's an icon I made in photoshop for the time being, so there won't have to be that plain android icon.
Download it here: http://dl.dropbox.com/u/12361010/volts.png
nagasgura said:
Here's an icon I made in photoshop for the time being, so there won't have to be that plain android icon.
Download it here: http://dl.dropbox.com/u/12361010/volts.png
Click to expand...
Click to collapse
Thanks, I'll add it for the next release.
The + on the Max voltage doesn't display for me.
Love it, fast and simple volt changing.. Makes viperMOD ancient news.

[KERNEL][3.0.31][HDMI][FULL HD][GUIDE 1.8]JBX-Kernel Hybrid [1,5ghz]

/// JellyBeanX-kernel ///​
DISCLAIMER
Me, XDA-Developers.com and anyone else doesn't take any repsonsibilty for damages on your device!
Rooting your device will void your warranty!
Don't play with settings you aren't familiar with, you could burn your device!!
Click to expand...
Click to collapse
READ THIS: READ BEFORE YOU ASK and HELP TO KEEP THIS THREAD MORE CLEAN! BUT ALSO BETTER ASK ONCE MORE BEFORE YOU MESS UP YOUR PHONE! If you find something missing in this OP/FAQ, please PM me and I will add it. Thank you!
This is a custom kernel mostly based on Motorola's 3.0.8 Hybrid Kernel which was initiated first by the STS-Dev-Team (Hashcode, Dhacker).
I created this kernel for my main goal: BATTERY LIFE! Like many other custom kernels this one also supports several performance related features like OVERCLOCKING, UNDERVOLTUNG, GPU CONTROL, CPU OPTIONS, RAM TWEAKS, etc etc... But my main goal was not to bring up a kernel which is fast as hell - I want to bring up a kernel that is fast + a long lasting battery! Many custom kernels are also very fast but they don't save battery. JBX-Kernel is supposed to push your device to great speed while being on low power settings. I hope you enjoy it!
If you want to support me and my work just leave me a beer.
You can find the FAQ at the bottom of this post!
LATEST CHANGES
FULL HD Video Recording is working now!!! See Downloads section below!
--> DETAILED CHANGELOG JBX-kernel Hybrid 4.4 <--
Kernel Guide by Placca 1.8!!
Check the FAQ section at the bottom of this post to download it! It will make many things easier for you and help you to understand the kernel and its features!
FEATURES
JBX-Kernel Hybrid
Battery Friend toggle (a battery friendly mode)
Intelli-Plug (Kernel side replacement for msm MPDecisions) by Faux123 + patches by me (no hotplugging when screen is ON)
Dynamic Hotplug: Second core will be turned off ONLY while screen is off - independent from selected governor. (Not needed when using Intelli-Plug)
Optimized OPP Table for smooth CPU scaling
Frequencies: 100, 200, 300, 400, 500, 600, 700, 800, 900, 1000, 1100, 1200, 1300
Modifed Smartreflex driver (Custom Sensor for detecting n-Value).
Smartreflex Tuning Interface: Set min/max calibrated voltage
Overclocking using Live OC (mine runs stable at a maximum frequency of 1,498ghz!)
hwmod, uart, IRQs - cleanups from pre-kexec config to safe power
CPU: lower voltages for CORE and IVA. Give CORE the abbility to scale up to higher voltage if needed
Added IVA_NITROSB
Dynamic fsync control: FSYNC interval is dynamic depending on screen state (SCREEN OFF: synchronous, SCREEN ON: asynchronous)
HTC's Asynchronous Fsync port - read explanation below*
Dynamic page-writeback: Page writeback interval is dynamic depending on screen state.
Frandom v2
JRCU / Tiny RCU (currently JRCU in use)
Raised voltage limits for mpu a bit
Raised the temperature limits from 64c* to 74c* (degrees)
optimized CRC32 algorithm (better code generation)
RW Readahead dynamically depending on storage device (automatic detection of the best value)
zRAM support
GPU has 4 scaling steps and OC to 384mhz (Base freq: 102 mhz --> 154 mhz, 307 mhz, 384 mhz)
GPU C4 states / GPU Control (Governors, Frequencies)
Multicore Power Saving Mode Control
ARCH Dependant Power feature
Gamma Control
Front Buffer Delay Control (draw in x msecs on early suspend)
Screen/Display: Modified OMAPDSS for sharpness and lightning colors
OMAPDSS: Added variable clock rate and OPP - allows the screen to scale down power and voltage
lowmemkiller: Heavy modified for R/W Speed and efficient performance
ZCACHE, ZSMALLOC, XVMALLOC backported from 3.4, 3.7 and 3.10 (ZCACHE currently not in use)
Custom Voltage Support
IO-Schedulers: SIOPlus, Fifo, Row, VR, Noop, Deadline, CFQ, BFQ
ROW Scheduler is heavily tweaked to be the fastest scheduler ever!
CPU: More Governors
Deep Idle
ARM Topology
Many improvements in overall OMAP PM
SELinux permissive
GREAT performance!
battery life!
Support for Trickster Mod Kernel Control App (Download from Gplay)
*]Too much stuff to list here. See "Sources" below and check my Github
* HTC's Asynchronous Fsync and Dynamic Fsync:
Asynchronous fsync (called "afsync" or "async fsync") from HTC is ported into this kernel. By default it's enabled and dynamic fsync is disabled (and as well it isn't needed anymore). But just to test a little bit around to see which one of both features is the better one - for battery & performance. But currently Tricktser Mod doesn't support a toggle for afsync, so I had to find another way to use Trckster. Finally I did it like this:
The dynamic fsync toggle in Trickster Mod is now serving both functions - the dynamic fsync AND the asynchronous fsync! How? By default Dynamic Fsync is disabled, and Afsync is enabled. If you now enable Dynamic fsync using the toggle, Afsync will be automatically disabled, so both functions are not conflicting each other - and this way we have a working toggle for both of them.
CAUTION
This is a work in progress! Some of the current features are still not in final stat. If you are facing issues report back here and DON'T spam the threads of the rom you're using!
Be careful with some settings such like Voltage and Overclocking!!! If you aren't experienced with these things, dont play with 'em!
Click to expand...
Click to collapse
REQUIREMENTS
NOTE: This will NOT work on Stock(-based) Roms!!
Rooted device
Must use a Kexec Rom (CM, AOKP, AOSP)
Recovery (BMM, SS)
REMOVE any kernel modules you used before
DEACTIVATE ANY CPU tweaks, onboot settings etc otherwise your phone may not boot!
CAUTION: The kernel needs a clean setup related to CPU tweaks / Settings, etc...Keep your device as clean as possible regarding to Tweaks, CPU special settings, etc. The Kernel brings its own CPU settings and after you can boot it succesfully, you can set it like you want!
This kernel may not work on all roms! Check and report.
TO DO LIST
- Fix bugs
INSTRUCTIONS
NOTE: CLICK here for a detailled Installation Guide (about the Aroma Installer, the features to select and more)
Download zip file from below
Reboot into recovery
Flash the kernel (BMM users: DON'T use the "Flash Kernel" Option! This is a usual zip file!)
Reboot
Download Trickster Mod App from Gplay! Read the FAQ to learn about playing with kernel features!
Enjoy!
NOTE: For updates you can use the built-in OTA UpdateMe App!
DOWNLOAD
NOTE:
Only for Android 4.4!
JBX-Kernel 3.0.8 Version:
2.x == > Android 4.4
JBX-Kernel 3.0.31 Versions:
3.x == > Android 4.4
TEST BUILDs
Test builds are potential prerelease builds which need some more testing before pushing to all users.
CAUTION: Should be stable mostly! But use at your own risk though!!
---> TEST BUILDS [CF] <---
XPERIMENTAL BUILDs
These builds include features without promises to work.
CAUTION: There is no promise that these version are stable/working/whatever! Use at your own risk!!
---> XPERIMENTAL Builds [Dev-Host] <---
---> XPERIMENTAL Builds [CF] <---
Click to expand...
Click to collapse
Something went wrong?
If you think you have set wrong "on-boot-values" in Trickster Mod flash this:
TRICKSTER RESET: http://dtrailer.de/kernel/trickster_reset.zip
FAQ
CAUTION: This FAQ and the whole OP, additional informations about Governors, IO Schedulers and detailed informations about the usage of Trickster Mod and this kernel can be viewed in the awesome Kernel Guide by Placca!
Kernel Guide 1.8
PDF: http://www.mediafire.com/download/7zaddcmvtxfk9ry/JBX+Kernel+Guide_v1.8.pdf
CHM: http://www.mediafire.com/download/g3ck1bf1k3a3j38/JBX+Kernel+Guide_v1.8.chm
CLICK THE BUTTON BELOW TO OPEN THE FAQ!
Please check the following points if you don't know how to use the features of the kernel or you are facing any kind of issues.
INDEX
1. Kernel Features
1.1 Smartreflex (Turn ON/OFF, adjust min/max range)
1.2 Live OC (Realtime Overclocking)
1.3 Custom Voltage (EMIF)
1.4 GPU Overclock & GPU Governor (UPDATED)
1.5 Gamma Control
1.6 Battery Friend
1.7 Suspend Governor (CURRENTLY DISABLED)
1.8 IVA Overclock
1.9 DPLL Cascading
1.10 HDMI toggle
1.11 Intelli-Plug
2. Issues
1.1 How can I change the smartreflex minimum/maximum voltage
What is Smartreflex?
SR is compareable with an CPU governor but not for scaling frequencies but for voltages. That means SR has a fixed range of voltage (min/max) and calculates the optimal voltage for each CPU frequency. In example on light use of the CPU it scales down to lower voltage - on heavy use it can sclae to higher voltage. This is an efficient system to save power! Compared to EMIF which uses the hardcoded voltages it saves more power because it's variable. EMIF cannot vary between the values.
This interface has a hardcoded range of 830mV min to 1450mV max. Usually there is no need to adjust these values but irt can be usefull in example when using high overclocked frequencies above 1,5ghz! Usually SR cannot handle frequencies above 1,5ghz and I have hardcoded the maximum range of 1,45mV which should allow SR to handle it. In prior times the users had to turn off SR when OCing above 1,5ghz which causes the CPU to eat more power. But you can try around and report your results.
CAUTION: Don't raise the maximum SR voltage too high! It can burn your board = no phone anymore! I recommend to not use higher values than 1490mV! As already mentioned: THe default value should be enough!
ANd also: USUALLY THERE IS NO NEED TO CHANGE ANYTHING ON SR! IF YOU DON'T KNOW WHAT YOU'RE DOING, PLEASE LEAVE IT ALONE!
Ok, now let's see how to do this:
Turn ON/OFF SR
1. Open Trickster Mod
2. Head to the "Specific section"
3. Scroll down to "Smartreflex"
4. You can toggle ON/OFF SR for each component (IVA, CORE, MPU)
Usually I recommend to keep SR ON because it saves power! But in some cases when overclocking the CPU (MPU) the device could freeze - whether you OCed too much or SR couldn't handle the frequency! In this case you can try to raise the vmax value of SR a little bit (CAREFULLY!) and try again. If it sitll freezes and you're sure that you didn't OC too much, turn SR OFF at least for MPU!
Maximum Voltage
Currently there is no app which supports the feature of adjusting the SR vmax value, because I wrote this feature some days ago.
But in the next Trickster Mod version this option will be supported!
example:
# To read the current vmax value. Replace XXX with one of the following:
sc_core - for core max sr voltage
sr_iva - for iva max sr voltage
sr_mpu - for mpu max sr voltage (mpu is most related for CPU scaling)
cat /sys/kernel/debug/smartreflex/XXX/vmax
# You will get an output, e.g. for mpu = 1450000 (1450mV)
# To set a new value, do the following command (replace XXX with a value like above - BE CAREFUL! USUALLY THE DEFAULT VALUE ENOUGH AND YOU CAN LEAVE IT UNTOUCHED!)
echo XXX > /sys/kernel/debug/smartreflex/XXX/vmax
Minimum Voltage
It's easy because Trickster Mod supports it!
1. Open Trickster Mod
2. Head to the "Specific section"
3. Scroll down to "Smartreflex"
4. Below each SR component (IVA, CORE, MPU) there is displayed a value (usually 830 default) which means this is the lowest scalable voltage for this component. You can try to decrease this value for the case you want to UV a bit more - or raise it a bit for the case you think that the set range is too low and causes freezes on your device.
1.2 How do I use Live OC (Live OVerclock)?
This feature allows you to overclock the CPU in realtime. It works with a multiplier value set by the user. The default multplier value is "100", which means: No OC! If you want to raise the OC frerquency, just raise this value step by step.
FOr my device the maximum working OC value is "111" which means the maximum frequency is running at 1498mhz!
NOTE: Keep in mind that you tunr Smartreflex OFF for higher freqs than 1500mhz - or raise the maximum SR voltage range for "MPU" a little bit and test if it works.
Ok, how to use Live oC in action:
Open Trickster Mod App and swipe to the tab "Specific". There you will find something like this:
Code:
MPU OC [100]
DON'T TOUCH THE "CORE OC" SECTION, IT WILL CAUSE FREEZES!
Now slowly increase the value "100" to something higher, e.g. "105". Tap the hook in the right upper corner to confirm. To see your new set of frequencies you can now whether close and restart Trickster Mod or just use any monitoring app like Cool Tool which will show your frequencies in real time. That's it!
CAUTION: You can damage your phone forever!!!! This feature allows you to set very high frequencies (also up to 2,0ghz...) - That DOESN'T mean that your phone can run these frequencies!
If your phone freezes or crashes you have probably set too high OC - or your voltage is too low.
1.3 How do I use Custom Voltage (EMIF)?
NOTE: This only adjusts the fixed voltage! When you have Smartreflex ON it can still vary! You have to see the bigger picture: This voltage value sets the "middle point" for voltages. Smartreflex is still able to increase or decrease the voltage. When Smartreflex is OFF the CPU will stay on this voltage you set here and probably eats also more power.
How does EMIF works together with Smartreflex:
Code:
-------
| CPU |
-------
|
------------------ ------------------
|Voltage 1015 mV | ---->| SMARTREFLEX ON| = 1015mV +/- "vmax"/"vmin"
------------------ -------------------
|
--------------------
|SMARTREFLEX OFF| ----> 1015mV FIXED! No changes!
-------------------
Thi smeans if you change the voltage for a scaling step (OPP) while SR is ON, SR will adjust the voltage from this value, means: mV-Value +/- SR vmin/vmax. WHen SR is OFF it will stay on this mV as a fixed value.
How to adjust the voltage?
Well, this feature can be used with all generic apps which are supporting voltage settings. But we are prepared well, you can adjust voltages also with the "Trickster Mod App".
When you open the app, head to the tab "Specific" and below the "Live OC Section" you will find your voltage table, which looks like this:
Code:
<-->
1200 [1398]
1000 [1388]
900 [1371]
...
..
..
Now just tap the arrows in the right upper above the first voltage value and just type or tap (per direction) a value, e.g. "-25". To apply it, confirm by tapping the hook in the right upper corner of your screen. That's it, your new voltage values are now set and applied. And also mind here: If your phone freezes you porbably have set it too low.
CAUTION: NEVER SET HIGHER VOLTAGE THAN 1490mv here!!!!! Or you might damage your phone FOREVER!
This voltage is not the same like Smartreflex! But it's still voltage! Just be carefull!!
1.4 How can I use GPU OC and GPU Governor?
GPU Overclock doesn't work like Live OC! You cannot really set custom frequencies for the GPU, but you can select and set the maximum frequency from a hardcoded range!
For the GPU there are the following available frequencies:
154mhz (FIXED!)
307mhz
384mhz
416mhz
The minimum frequency of 154 is FIXED! This means you cannot change it because the GPU needs a minimum speed to run with. But the kernel allows you to select the maximum speed. This can be usefull for playing games and also for saving power . In example when not playing games you don't need the GPU to run at 416mhz! Set it to 307mhz in this case and save power.
When you open Trcikster Mod and head to the "specific section tab", you will find "GPU MAX FREQUENCY" and it's currently set maximum frequency. Tap on it to select your preferred one:
- 154 Mhz
- 307 MHz
- 384 MHz
That's it. The new setting will be your new maximum GPU frequency.
Below there's another option called "GPU Governor". Just tap on it and select your prefered one.
NOTE: If you want to track current GPU frequencies and watch governor's behavior, just switch to Trickster's "Informations" - Tab and watch the frequencies clock.
1.5 How can I use Gamma Control?
What is gamma? The gamma setting sets the color range for the screen. You can compare it to the contrast. We all know that the touchscreen eats most of the power compaerd to all other components in a smartphone! A lower brightness causes less power consumption and a lower gamma or contrast range alos helps a little bit to save power.
In this kernel you can choose from a range of "5 - 10" while "5" is very bright while "10" is very dark. The default setting is "5" BUT CAUTION: Trickster Mod will display a range of "0" to "10" and the default setting will be shown as "0". This is caused by the fact that this feature was ported from the Gnex device where you can choose from a higher range. The only sideeffect is that the values "0" - "5" won't show any difference.
How to set the gamma value?
Well, once again open Trickster Mod and swipe to the tab on the right end. Just select your preferred value by using the slider.
Alternately you can use sysfs by terminal or adb:
OMAP Gamma interface:
echo i > /sys/devices/platform/omapdss/manager0/gamma
Replace i with 0-10 of your choice.
1.6 What is "Battery Friend and how to use it?
Battery Friend is a simple toggle (ON/OFF) which sets your device into a battery friendly mode without the need to play with all settings in Trickster Mod /sysfs until you find a good setting. In fact it does the job for you.
What does it affect?
NOTE: Doesn't lock anyx frequencies anymore!
locks dynamic Fsync enabled
locks Fsync disabled
Doesn't allow any OC (Live OC will not have any effect, Core OC is not allowed in this kernel)
Increases the dirty ratio interval to 90% (starts working at this value)
Enables Dynamic Hotplug: This doesn't allow hotplugging during device is active - and it will always turn CPU1 OFF during suspend! It also prevents from conflicts when user uses a hotplug governor (which isn't a good idea though) - but hotplug governors are causing higher battery drain!
Dynamic Page-writeback always enabled
How to toggle Battery Friend:
For now the only way is via terminal, adb shell or root explorer (text editor)
For terminal and adb:
Code:
echo 1 > sys/kernel/battery_friend/battery_friend_active /* Enable */
echo 0 > sys/kernel/battery_friend/battery_friend_active /* Disable */
For Root Explorer
Open Root Explorer
Navigate to sys/kernel/battery_friend/
Open "battery_friend_active" with Text Editor
Change "0" to "1" and safe the file to enable
Change "1" to "0" and safe the file to disable
1.7 Suspend Governor Control (CURRENTLY DISABLED)
Suspend Governor Control is a kernel module written by me. You can use it to set your preferred Screen-Off-governor.
For now it's only supported by sysfs (Trickster Mod will support all my current and upcoming features as soon as it gets updated with its new UI mode!
How to set suspend governor
Open a terminal or use adb shell
Code:
su
echo "x" > /sys/kernel/suspend_gov/suspend_gov
Replace x with one of these values:
0 = Ondemand
1 = Ktoonservative
2 = Conservative
3 = OndemandX
NOTE: No matter what governor you use for suspend mode, if Battery Friend is enabled the second core will be turned off during suspend!
1.8 IVA Overclock
What is IVA OC?
IVA OPPs are controlling the CPU load for sound events. It could be useful (in some cases) when you get sound related laggs. Just set the maximum frequency to highspeed. This will allow more CPU power for sound events but also will cause higher battery consumption.
How to use IVA OC?
If you want to check the current IVA frequency. Just type in Terminal or ADB:
Code:
cat /sys/devices/system/cpu/cpu0/cpufreq/iva_clock
You will get an output like this:
Code:
132 Mhz
2. You can whether enable IVA highspeed: 130 - 430 Mhz ["1"] or enable IVA normal speed: 130 - 332 Mhz ["0"]
320 Mhz max: echo "0" > sys/devices/system/cpu/cpu0/cpufreq/iva_freq_oc
430 Mhz max: echo "1" > sys/devices/system/cpu/cpu0/cpufreq/iva_freq_oc
1.9 DPLL Cascading
DPLL: Davis–Putnam–Logemann–Loveland (DPLL) algorithm
To get more info about this please see wiki
But to sum it up shortly: It helps to use/stream media (music) in a low power mode.
NOTE: DPLL Cascading will be available to be switched easily via Trickster Mod App soon!
How to switch DPLL?
DPLL is ENABLED by default!
Open Trickster Mod -> Speicific Tab --> DPLL (soon)
sysfs:
Turn off:
Code:
echo 0 > /sys/kernel/dpll/dpll_active
Turn on:
Code:
echo 1 > /sys/kernel/dpll/dpll_active
1.10 HDMI toggle
Some users are facing a RAZR-sepcific problem: HDMI cable is detected, even though there is no cable plugged!
Therefor I included a toggle to switch HDMI wether ON or OFF. Additinally there's an init.d script included within the AROMA Installer you can select during the installation of JBX-Kernel.
To enable/disable HDMI on-the-fy:
sysfs:
Turn off:
Code:
echo 0 > /sys/kernel/hdmi/hdmi_active
Turn on:
Code:
echo 1 > /sys/kernel/hdmi/hdmi_active
1.11 Intelli-Plug
For intelli-plug hotplugging is now only allowed when the device enters sleep.
To enable hotplugging universally just change the value of the following entry whether to 1 (on) or 0 (off):
Code:
sys/module/intelli-plug/parameters/int_hotplug
2. If anyone has the following issues:
Issue
Media Process FC
No SD-Card in File Explorer
My CPU Settings (frequencies, etc) won't be saved (it sets itself back to Kernel default after screen off)
My phone freezes/reboots always when I try to set options in Trickster Mod
The device is lagging very hard
Solution
Media FC: Open App settings, head to "Download Manager" and "Media Storage" and hit the "delete data" button. Reboot. Now it shouldn't give any FCs anymore and after a little bit of waiting it will find all Media (Pictures, Videos, etc..)
No SD-Card: Reboot into recovery, go to "Mounts & Storage", tick "mount int" or "mount ext".
USB: Make sure the screen is ON while plugging the cable in.
CPU Settings: This is a bug which cannot be solved at the moment. Temporary solution: In Trickster Mod just activate the "Frequency Lock" and your settings will persist.
Trickster Mod:: Open App settings, Trickster Mod and select "uninstal updates". Now it should work.
Crashes, Freezes, lagging, something doesn't work, etc
There are too many reasons which could cause crashes! So here is a checklist for you to look for. Check each point and try the following workaround:
- Your rom has CPU tweaks (e.g. Kernel modules, init.d folder, etc)
- You have set custom CPU settings (e.g. custom frequencies with apps like No-Frills CPU Control, Set-CPU, Antutu, etc...)
- You have undervolted too low
- You have overclocked too high
- You have applied higher "Core OC" value in Trickster Mod App
- You are running any other kernel tweaks which are regarding to the CPU and/or performance (e.g. Kernel modules by Whirleyes eventually set by init.d, etc..)
- After setting some settings (e.g. in Trickster Mod) your device doesn't boot anymore
- adb doesn't work / shows only "device offline"
- You are facing hard lagging
If any point here matches your setting, please revert from it:
- Remove any CPU init.d script from /System/etc/init.d
- Uninstall any CPU controling app (e.g. Set-CPU, No-Frills, etc..)
- Remove all extra kernel modules from system/lib/modules (e.g. cpu_control.ko, cpufreq_smartass2.ko, etc..)
- Unset any custom settings from any other kernel / CPU - tweaking app which is NOT Trickster Mod
- Maybe your governor causes issues. Hotplug is know for bugs at the moment...I'm going to fix it..
- NEVER set your CPU Settings (e.g. in Trickster Mod App) on boot!!!! - before you aren't sure that your settings are safe!!!
- You may flash the kernel again after reverting related settings
- to make adb work / show device online, download latest SDK platform-tools and confirm access on device (4.2 security feature of Android)
- Don't use any task killers, memory killers, seeder apps! They may conflict with the kernel/Rom settings.
If none of these suggestions work for you your rom may be incompatible. Please report it here that I can add the rom to the list of imcompatible roms
If you have any issue, please read this:
First check:
- is it really a kernel issue?
- did I see this bug with the roms original kernel?
- what are the people in the rom thread saying?
- what are the people in the kernel thread saying?
- can I find this issue on a bug list?
- how about my settings? Is it my fault it crashed?
- can I find something useful in the kernel FAQ?
- Is it maybe a well known issue and can be solved
withing seconds? Just like wifical.sh?
- Where to repeat that issue? Rom or kernel?
I know it's sometimes difficult to track the issues, and we can't know for sure if it's caused by the rom or by the kernel, but if you try at least to get some information you might find an answer sometimes. If you are able to understand logs, you may report whatever you find.
All this helps to keep the threads more clear. Thank you.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
DONATE
If you like my work and want to support me, I'd enjoy a little beer or coffee. You can find my beer mug below my username
SOURCE
JBX-Kernel 4.4
CREDITS
Shurribbk - Co-Development
Kholk & [mbm] - Kexec inital Release
Hashcode & Dhacker - Making Kexec stable and initiating compatible kernels
Motorola - 3.0.8 Kernel Source
Surdu_Petru - Sharing Knowledge and helping with problems
nithubhaskar - Hints and answering my questions
Ezekeel, Imoseyon - Custom Voltage, Live OC, Temp Control, Gamma Control Source Code
faux123 - Some features, like Intelli-Plug, Intellidemand, Intelliactive
bigeyes0x0 - Trickster Mod App
Team Trickster - Great support and adding new features from my suggestions
Placca - Awesome kernel guide
RandomPooka - for special testing and support
- reserved -
Hey guys, welocme to JBX-Kernel for Targa! This is the first initial release and needs to be tested! Please give me some feedback if it boots and how it works for you. It comes with built-in OTA Updater and many extra stuff. Just check it out.
Keep in mind that this release will only work on 4.4 builds! Currently I don't have the time for others. Also you should use a newer build with Full HD Cam support! When using this kernel with older 4.4 builds your camera won't work.
Oh cool, i happy Someone help you with targa kernel ?
Maksim_ka said:
Oh cool, i happy Someone help you with targa kernel ?
Click to expand...
Click to collapse
Nope.. But it doesn't matter. Currently I have a problem with paying my server, and as long as I am able to build I wanted to release the Targa Kernel. The only difference seems to be in the CMD-line (Targa doesn't have a utags partition), so I just had to switch this line and build it with CM11 Targa sources to get the right ramdisk and modules. The whole source is the same like RAZR kernel.
I test it, and dont see weighty differences with RAZR kernel, have same bugs, display backlights don't turn on sometimes. I think you can talk with Hush about it, he can help.
Maksim_ka said:
I test it, and dont see weighty differences with RAZR kernel, have same bugs, display backlights don't turn on sometimes. I think you can talk with Hush about it, he can help.
Click to expand...
Click to collapse
You mean Hashcode? I am in static contact with him. But thx
What do you mean with "backlight doesn't turn on sometimes" ? I don't see this problem on RAZR... But sometimes you need to be a little patient when you want to wake it up. That's because of things like "DEEP IDLE" and others which keep the device in "deeper" sleep mode. It can take 1 or 2 seconds until you will see the lights - but it will turn on for sure. Maybe you're talking about something else? What bugs else exactly?
dtrail1 said:
You mean Hashcode? I am in static contact with him. But thx
What do you mean with "backlight doesn't turn on sometimes" ? I don't see this problem on RAZR... But sometimes you need to be a little patient when you want to wake it up. That's because of things like "DEEP IDLE" and others which keep the device in "deeper" sleep mode. It can take 1 or 2 seconds until you will see the lights - but it will turn on for sure. Maybe you're talking about something else? What bugs else exactly?
Click to expand...
Click to collapse
Yep, i mean Hashcode.
It will happened if use proximity sensor when calling, and sometimes when wake up phone. Backlight don't turn on generally, help only reboot. And it don't happened if change frequency to 300-1xxx. I think if you change minimal frequency to 300mhz it gone.
Maksim_ka said:
Yep, i mean Hashcode.
It will happened if use proximity sensor when calling, and sometimes when wake up phone. Backlight don't turn on generally, help only reboot. And it don't happened if change frequency to 300-1xxx. I think if you change minimal frequency to 300mhz it gone.
Click to expand...
Click to collapse
Well that's not an issue, but a well known phenomen. Some devices cannot handle 100 MHz (depends on silicon, each one is different). The min frequency is 300 by default, and the battery friend min frequency is 200 by default. Just check your settings in trickster mod.
Gesendet von meinem XT910 mit Tapatalk 4
I'm able to boot the kernel but cannot get radio. Any ideas?
Sent from my XT875 using Tapatalk
BZguy06 said:
I'm able to boot the kernel but cannot get radio. Any ideas?
Sent from my XT875 using Tapatalk
Click to expand...
Click to collapse
Not yet. I need more informations from other users. Any feedback here????
Just try the today's OTA (soon). I forgot to update device tree sources in yesterday's builds.
Because I had a weird drain myself on yesterday's RAZR kernel (not very much, but noticable)
EDIT: I got a workaround for the RADIO issue - if it's actually an issue Wait for the OTA.
I was only able to get radio working on your 1-08 build of the kernel for rzr. Ever since then I haven't been able to get it to come up.
Edit: I went ahead and installed your 1-21 update and its better. It eventually connects to LTE but only holds it for 30 secs and then drops with no radio. Thanks for the help in advance.
Sent from my XT875 using Tapatalk
BZguy06 said:
I was only able to get radio working on your 1-08 build of the kernel for rzr. Ever since then I haven't been able to get it to come up.
Edit: I went ahead and installed your 1-21 update and its better. It eventually connects to LTE but only holds it for 30 secs and then drops with no radio. Thanks for the help in advance.
Sent from my XT875 using Tapatalk
Click to expand...
Click to collapse
Please download the latest build from same links again (any mirror, I overwrote it). It should have fixed radio now. But you have to replace your build.prop with that one from your rom or open it and remove all additions made by JBX. The easiest way is to flash the rom again, then flash jbx.
I went ahead and redownloaded and reinstalled and I'm still getting the same thing. Attached is my "phone info" screen. And under "select preferred network" my only option is unknown
{
"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"
}
Sent from my XT875 using Tapatalk
Just flashed latest 1/21 JBX with cm 1/20. Have lte. Haven't played with settings yet. Need to read the faq first. Thanks void time buddy.
Sent from my XT875 using Tapatalk 2
BZguy06 said:
I went ahead and redownloaded and reinstalled and I'm still getting the same thing. Attached is my "phone info" screen. And under "select preferred network" my only option is unknownView attachment 2530635
Sent from my XT875 using Tapatalk
Click to expand...
Click to collapse
So, have you reset your build.prop before as I said above?
Btw: just open it in a text editor (I.e. With root Explorer), scroll down until you see "dtrail - build.prop additions". Delete everything below that line. Now reboot and flash jbx (after downloaded again).
Gesendet von meinem XT910 mit Tapatalk 4
dtrail1 said:
So, have you reset your build.prop before as I said above?
Btw: just open it in a text editor (I.e. With root Explorer), scroll down until you see "dtrail - build.prop additions". Delete everything below that line. Now reboot and flash jbx (after downloaded again).
Gesendet von meinem XT910 mit Tapatalk 4
Click to expand...
Click to collapse
Yes. I went ahead and wiped system and data, installed cm11 1-20, and then installed the 1-21JBX targa kernel
Sent from my XT875 using Tapatalk
BZguy06 said:
Yes. I went ahead and wiped system and data, installed cm11 1-20, and then installed the 1-21JBX targa kernel
Sent from my XT875 using Tapatalk
Click to expand...
Click to collapse
Just flash the latest jb radio and don't change band in settings.
P.S. targa don't have BMM
Maksim_ka said:
Just flash the latest jb radio and don't change band in settings.
P.S. targa don't have BMM
Click to expand...
Click to collapse
I have the latest JB radio (CDMA_N_05.22.00R LTEDC_U_09.1D.00). My radio works fine using the stock CM11 kernel. I really wanna try out dtrails' work.

[GUIDE] ROM setup after flash for better work

This is how I setup my rom after flash, and device is working very well with 52 installed apps
1. Configure settings
-Go to wifi and disable scanning always on
-Open mobile network and chose 2G (use 3G only when you need it)
-Go to more and then to mobile broadcasts and disable all (when it enabled, consume RAM)
-configure sound,display, and interface... As you want
-go to accounts and disable sync which you don't need.
-go to About and taping on blablabla, you know to enable Developer options and rom performance.
-Go to developer options set all animations(you have three) to 0.5
-Performance??
-you don't need it, I will show you in next step.
2. Flash this:
L Speed
Or make this manualy
2.1. Install&Configure TricksterMod
-For cpu freq the best is to set device default, like on stock rom, don't forget to press Lock freq.
-Minfree setup
-8mb
-12mb
-17mb
-25mb
-29mb
-33mb
-Syscontrol setup
-Set swappiness to 60
-Set vm.vfs_cache_pressure to 40
-vm.dirty_ratio = 90
-vm.dirty_background_ratio = 70
Set this from tricksterMOD
-CPU freq
The best is
-Min freq
320Mhz
-Max freq
1008mhz
-Scheduler
SIO
-Governor
SmartassV2 or SmartassH3
-GPU freq
-That is your choice min freq will increase battery life, but some laggs is possible, max freq will drain battery faster, but there is less possibility to have lag.
After all don't forget to set run on boot.
3.Install&Configure Greenify
-You already know Hibernate what you want expect Alarm clock, messaging apps, trickster mod, etc.
You already know if you hibernate app with push notifications, you don't get it.
4. Apps
-what about apps??
There is too much apps which user don't use, that apps use ram like other.
Now you need to delete everything what you don't use (live wallpapers, cm wallpapers, etc.) or change apps with some lightweigh, like gallery and keyboard. Download QuickPIC and google keyboard (lollipop themed) {{i will add link later }}
5.build.prop
-leave build.prop to default as much as possible.
-change DPI to device standard, in some reasons my device lag on 200, then I move back to 240 as default. This is for L7.
For L5, there is no line that define DPI, you can skip this step.
-Change ro.max.fling from 4000 to 8000 (don't add ro.min)
-Change vm.heapsize to 64m (I don't go under that, but difference is big from 128 to96 choose between 96 or 64
-Change lowRAM from false to true (you will get little more free RAM).
When you change it to true, you will lose transparent statusbar.
6.init.d
-keep device without any special tweaks, devs which make this rom, they choose the best.
Helpful tips:
-Don't use battery boosters, ram boosters and apps call like that. System do better than one app. There is low memory killer (lmk).
Also this app use ram which you maybe need for something.
Nice tips buddy!
Good job!
Sent from my IdeaTab A2107A-H using Tapatalk
skyinfo said:
Nice tips buddy!
Good job!
Sent from my IdeaTab A2107A-H using Tapatalk
Click to expand...
Click to collapse
Thanks dude
Realy good,i add some of the sets into my rom,thanx!!!
NERDIFIED TILL DEATH!!!
thnx a lot, i hope it all works for me too
since gpu freq is not changing to 245 (for some reason) I decided to stick with 380 because I run ePSXe on my phone
turkiktxhc said:
thnx a lot, i hope it all works for me too
since gpu freq is not changing to 245 (for some reason) I decided to stick with 380 because I run ePSXe on my phone
Click to expand...
Click to collapse
Is device faster???
Everyone who have L7 know speed
-CALIBAN666- said:
Realy good,i add some of the sets into my rom,thanx!!!
I
NERDIFIED TILL DEATH!!!
Click to expand...
Click to collapse
I will post video tonight to see speed of my device
But say me how to post video on xda
Paget96 said:
Is device faster???
Click to expand...
Click to collapse
It's extremely fast at this point, i'm only afraid of it gradually slowing down after days of use
right now, it's really fine
-CALIBAN666- said:
Realy good,i add some of the sets into my rom,thanx!!!
NERDIFIED TILL DEATH!!!
Click to expand...
Click to collapse
Quality is too bad, but.
https://www.youtube.com/watch?v=tm5ay4alFPQ&feature=youtube_gdata_player
Vrh brate
Thank you for these settings
Paget96 said:
This is how I setup my rom after flash, and device is working very well with 52 installed apps
1. Configure settings
-Go to wifi and disable scanning always on
-Open mobile network and chose 2G (use 3G only when you need it)
-Go to more and then to mobile broadcasts and disable all (when it enabled, consume RAM)
-configure sound,display, and interface... As you want
-go to accounts and disable sync which you don't need.
-go to About and taping on blablabla, you know to enable Developer options and rom performance.
-Go to developer options set all animations(you have three) to 0.5
-Performance??
-you don't need it, I will show you in next step.
2. Install&Configure TricksterMod
-For cpu freq the best is to set device default, like on stock rom, don't forget to press Lock freq.
-Minfree setup
-8mb
-12mb
-17mb
-25mb
-29mb
-33mb
-Syscontrol setup
-Set swappiness to 60
-Set vm.vfs_cache_pressure to 40
-vm.dirty_ratio = 90
-vm.dirty_background_ratio = 70
-Gpu freq
-That is your choice min freq will increase battery life, but some laggs is possible, max freq will drain battery faster, but there is less possibility to have lag.
After all don't forget to set run on boot.
3.Install&Configure Greenify
-You already know Hibernate what you want expect Alarm clock, messahing apps, trickster mod, etc.
4. Apps
-what about apps??
There is too much apps which user don't use, that apps use ram like other.
Now you need to delete everything what you don't use or change apps with some lightweigh, like gallery and keyboard. Download QuickPIC and google keyboard (lollipop themed) {{i will add link later }}
5.build.prop
-leave build.prop to default as much as possible.
-change DPI to device standard, in some reasons my device lag on 200, then I move back to 240 as default.
-Change ro.max.fling from 4000 to 8000 (don't add ro.min)
-Change vm.heapsize to 64m (I don't go under that, but difference is big from 128 to96
-Change lowRAM from false to true (you will get little more free RAM).
6.init.d
-keep device without any special tweaks, devs which make this rom, they choose the best.
Only if you want add zipalign.
Click to expand...
Click to collapse
pretty good and usefull tips :good: :good: but if i edit the build.prob i get black screen on boot
Jobloxx said:
pretty good and usefull tips :good: :good: but if i edit the build.prob i get black screen on boot
Click to expand...
Click to collapse
You think bootloop?? Or just black screen??
Anf which device you use?
Dj_Luxor said:
Thank you for these settings
Click to expand...
Click to collapse
no problem
Thanks for using my setup.
Paget96 said:
You think bootloop?? Or just black screen??
Anf which device you use?
Click to expand...
Click to collapse
When i manually edited the build.prop I ended up black screen too, then i tried out the build.prop Editor app, which worked for me.
vangama said:
When i manually edited the build.prop I ended up black screen too, then i tried out the build.prop Editor app, which worked for me.
Click to expand...
Click to collapse
Then ok
@Paget96 really cool! This is actually what I'm trying to do bro and thanks muchly for this configuration tips. I got more infos:thumbup:
Paget96 said:
You think bootloop?? Or just black screen??
Anf which device you use?
Click to expand...
Click to collapse
No blackscreen and i have l7
junephel said:
@Paget96 really cool! This is actually what I'm trying to do bro and thanks muchly for this configuration tips. I got more infos:thumbup:
Click to expand...
Click to collapse
Ok
Thanks for helping.
Added little stuff
Maybe someone use it
Jobloxx said:
No blackscreen and i have l7
Click to expand...
Click to collapse
now working used an editor working great

Categories

Resources