Check your syncing and make sure your device isn't syncing too often. Could be a number of things that can cause the issue. Also are you using DS Battery Saver? If so you'll see a increase because of that, as the app disables all Google services during screen off. Once you turn screen back on it will try to restore and run its processes as it normally would.
Check your syncing and make sure your device isn't syncing too often. Could be a number of things that can cause the issue. Also are you using DS Battery Saver? If so you'll see a increase because of that, as the app disables all Google services during screen off. Once you turn screen back on it will try to restore and run its processes as it normally would.
I do but haven't had this problem in the past. My Google location services were on since I reflashed my rom so I'm gonna try that.
On a side note :
Latest tweaks. Tasty.
I do but haven't had this problem in the past. My Google location services were on since I reflashed my rom so I'm gonna try that.
On a side note :
Latest tweaks. Tasty.
I do but haven't had this problem in the past. My Google location services were on since I reflashed my rom so I'm gonna try that.
On a side note :
Latest tweaks. Tasty.
-75UV All across the board. (Fast) CPU // Adjust if Nominal or Slow.
Touch boosters active, view Screenshots.
No Screen Off profiling
No Change in Governor or Scheduler with Screen Off.
Governor Adjustments:
MW86 Tweaked BFQ I/O Scheduler:
Results:
Battery life was pretty great, unfortunately I forgot to take screen shots of results but ended up at around 23 hours/4 hours screen on time. 4g all day and some minimal WiFi usage when arriving home from work. I did a ton of flip board reading, twitter, business calls, texting, and YouTube. Performance was good, rarely saw lag but it does happen occasionally with the BFQ scheduler. All in all I'm very happy with this setup.
I am trying this now. My processor is fast as well, and I have to say, I am impressed with how well this has run so far. It is well balanced between battery and performance. After sacrificing performance for battery here recently, I am more apt for settings that even things out across the board.
I am trying this now. My processor is fast as well, and I have to say, I am impressed with how well this has run so far. It is well balanced between battery and performance. After sacrificing performance for battery here recently, I am more apt for settings that even things out across the board.
Thanks for posting it. Seriously, this is more than likely going to become my main setup. I have tried the Peg/row setups as well as Ktoons/Zen, both had strengths but lacked at different points with either lag or drain on battery. This has been the perfect middle for me. Great job.
Found some useful information from Google pertaining to Zen I/O scheduler adjustment table. Thought I'd share.
fifo_batch is used to control the time between issuing expired requests. Lowering this value will result in tighter deadlines at the cost of throughput, while increasing it will improve throughput while increasing latency variation.
sync_expire and async_expire control the expiry times for synchronous and asynchronous requests, respectively. Reads or synchronous writes (i.e. writes using O_DIRECT or O_SYNC) are treated as synchronous requests; all others are considered asynchronous. Deadlines can be disabled entirely by setting sync_expire=async_expire=0.
Found some useful information from Google pertaining to Zen I/O scheduler adjustment table. Thought I'd share.
fifo_batch is used to control the time between issuing expired requests. Lowering this value will result in tighter deadlines at the cost of throughput, while increasing it will improve throughput while increasing latency variation.
sync_expire and async_expire control the expiry times for synchronous and asynchronous requests, respectively. Reads or synchronous writes (i.e. writes using O_DIRECT or O_SYNC) are treated as synchronous requests; all others are considered asynchronous. Deadlines can be disabled entirely by setting sync_expire=async_expire=0.
Great info, what weird i i have good performance even going to 10000/0/600 on Zen in last day been very smooth. So a higher fifo increases bandwith but it increases latency so i see its a balancing act of ones prefence of handling. I wonder how much higher fifo actually raises straight through put.
Great info, what weird i i have good performance even going to 10000/0/600 on Zen in last day been very smooth. So a higher fifo increases bandwith but it increases latency so i see its a balancing act of ones prefence of handling. I wonder how much higher fifo actually raises straight through put.
First full day on the new tweaks in OP. Here's what I got so far. Start my day at 5am gym time meaning listening to music for an hour and a half. Then pretty much all day at work. Includes sync on, twitter and Facebook often with some texting. Good work gents and it's only the first full day!
/*
* Zen IO scheduler
* Primarily based on Noop, deadline, and SIO IO schedulers.
*
* Copyright (C) 2012 Brandon Berhent <bbedward@gmail.com>
*
* FCFS, dispatches are back-inserted, deadlines ensure fairness.
* Should work best with devices where there is no travel delay.
*/
#include <linux/blkdev.h>
#include <linux/elevator.h>
#include <linux/bio.h>
#include <linux/module.h>
#include <linux/slab.h>
#include <linux/init.h>
enum zen_data_dir { ASYNC, SYNC };
static const int sync_expire = HZ / 4; /* max time before a sync is submitted. */
static const int async_expire = 2 * HZ; /* ditto for async, these limits are SOFT! */
static const int fifo_batch = 1;
struct zen_data {
/* Runtime Data */
/* Requests are only present on fifo_list */
struct list_head fifo_list[2];
unsigned int batching; /* number of sequential requests made */
/* tunables */
int fifo_expire[2];
int fifo_batch;
};
static void
zen_merged_requests(struct request_queue *q, struct request *req,
struct request *next)
{
/*
* if next expires before rq, assign its expire time to arq
* and move into next position (next will be deleted) in fifo
*/
if (!list_empty(&req->queuelist) && !list_empty(&next->queuelist)) {
if (time_before(rq_fifo_time(next), rq_fifo_time(req))) {
list_move(&req->queuelist, &next->queuelist);
rq_set_fifo_time(req, rq_fifo_time(next));
}
}
/* next request is gone */
rq_fifo_clear(next);
}
static void zen_add_request(struct request_queue *q, struct request *rq)
{
struct zen_data *zdata = zen_get_data(q);
const int dir = rq_data_dir(rq);
static void zen_dispatch(struct zen_data *zdata, struct request *rq)
{
/* Remove request from list and dispatch it */
rq_fifo_clear(rq);
elv_dispatch_add_tail(rq->q, rq);
/* Increment # of sequential requests */
zdata->batching++;
}
/*
* get the first expired request in direction ddir
*/
static struct request *
zen_expired_request(struct zen_data *zdata, int ddir)
{
struct request *rq;
if (list_empty(&zdata->fifo_list[ddir]))
return NULL;
rq = rq_entry_fifo(zdata->fifo_list[ddir].next);
if (time_after(jiffies, rq_fifo_time(rq)))
return rq;
return NULL;
}
/*
* zen_check_fifo returns 0 if there are no expired requests on the fifo,
* otherwise it returns the next expired request
*/
static struct request *
zen_check_fifo(struct zen_data *zdata)
{
struct request *rq_sync = zen_expired_request(zdata, SYNC);
struct request *rq_async = zen_expired_request(zdata, ASYNC);
if (rq_async && rq_sync) {
if (time_after(rq_fifo_time(rq_async), rq_fifo_time(rq_sync)))
return rq_sync;
} else if (rq_sync) {
return rq_sync;
} else if (rq_async) {
return rq_async;
}
return 0;
}
static struct request *
zen_choose_request(struct zen_data *zdata)
{
/*
* Retrieve request from available fifo list.
* Synchronous requests have priority over asynchronous.
*/
if (!list_empty(&zdata->fifo_list[SYNC]))
return rq_entry_fifo(zdata->fifo_list[SYNC].next);
if (!list_empty(&zdata->fifo_list[ASYNC]))
return rq_entry_fifo(zdata->fifo_list[ASYNC].next);
return NULL;
}
static int zen_dispatch_requests(struct request_queue *q, int force)
{
struct zen_data *zdata = zen_get_data(q);
struct request *rq = NULL;
/* Check for and issue expired requests */
if (zdata->batching > zdata->fifo_batch) {
zdata->batching = 0;
rq = zen_check_fifo(zdata);
}
if (!rq) {
rq = zen_choose_request(zdata);
if (!rq)
return 0;
}
Welcome to Team Kernalizers's VZW Thread. This thread will attempt to teach you and show you how to maximize the performance and battery life of your GS3 running the KT747 kernel by Ktoonsez.
In this thread, you will learn everything you need to know about Governors, I/O Schedulers, Underclocking (UC), Overclocking (OC), Undervolting (UV) and the KTweaker application. We will also provide you with pre-configured tweaks to use.
This is a friendly support community. You can post your benchmarks, battery stats, feedback and settings. We will also help troubleshoot any problems that you may encounter while using this kernel and our tweak packages.
Rules
Please consider these rules before using this thread:
1. Follow XDA Forum rules (http://xdaforums.com/announcement.php?f=1712)
2. There will be NO FLAMING, NO SPAMMING, NO HARRASMENT of any kind. These will not be tolerated. You have been warned!
3. Search the thread first before asking questions. Most likely, your question may have been answered already.
4. If you are stuck and need help, DO NOT post comments like "this is not working". It will be ignored. You must provide necessary information like ROM Type (AOSP/TW), Kernel Version, OC, UV ...etc. You get the picture. The more you provide the better we can help
5. Please allow time for the team to find an answer if we can’t figure it out we know enough people to help us out finding a answer thank you
6. Be Patient We have our own personal lives outside of here. Allow the team some time to find answers. We will do our best to help.
7. If you post screenshots, you are allowed a maximum of 3 screenshots.
8. Keep posts/threads on-topic
By post in this thread, you are agreeing to the above rules.
Team Kernalizers members, Ktoonsez, and ROM developers are not responsible for bricked devices or any other device issues you experience as a result of using information in this thread.
Every phone is different, especially since it was found that we have slow, nominal, and fast variations.
Tweaks provided are extremely experimental and should be avoided by beginners and people who have important responsibilities tied to the usage of their phone.
You Have Been Warned: Use of any information, tweaks and applications in this thread at your own risk. You assume full responsibility for your own actions.
Downloads
Huge thanks to MorphiousGX for our live report form. Please report battery usages at these links.
We will use this information to help make better adjustments to our tweaks. It will collect the necessary information to make sure people compare apples to apples*
You can also view results after you submit, and filter on any of the questions asked (i.e. Tweaker's name, governor, release date..etc).
Individual renaming of the following bin Files for battery savings:
gsiff_daemon
mpdecision
qosmgr
smd
smdexe
Renames bin files with .bak
Bin File Restore
Individual restoring of the following bin files:
gsiff_daemon
mpdecision
qosmgr
smd
smdexe
Restores bin files to their original state.
Mods
KT747 Bootanimation Fix:
Use only if bootanimation is broken. Usually occurs on TW Roms.
Team Kernelizers TouchWiz Build Prop Tweaks
Team Kernelizers AOSP Build Prop Tweaks
Restore of Original TouchWiz Build Prop
Restore of Original AOSP Build Prop
Changelog
Located in TKMod zip
Contest Splash Screens
You now have access to all Team Kernelizers Contest Splash Screens in one zip!
1st Place Splash Screen:
2nd Place Splash Screen:
3rd Place Splash Screen:
4th Place Splash Screen:
5th Place Splash Screen:
6th Place Splash Screen:
7th Place Splash Screen:
8th Place Splash Screen:
9th Place Splash Screen:
10th Place Splash Screen:
11th Place Splash Screen:
Stock Splash Screen: Reverts to Original Splash Screen.
Thanks from luis86dr
Edgehood for answering all my questions about Aroma! Thanks buddy!
steelers_exe for his awesome splash screen for Aroma Installer.
RErick for his build prop updater script & for providing Splash Screen zips.
mw86 for his build prop tweaks.
GMan for testing and helping me. Also for providing mirrors!
decimalman for making the build prop script work!
Ktoonsez for such a awesome Kernel and inspiring us to do what we do.
Everyone who helped with testing!
Team Kernelizers for being so damn awesome!
Known Bugs
Splash Screens will only work on TouchWiz
Working on finding out the cause of these issues. Please report bugs in either of the Team Kernelizers threads.
This is still in Beta, more is yet to come!!!!!!
General Installation Instructions (for both TW and AOSP):
1. Download correct version of kernel for your device and rom. This is important as you may brick your phone is you use the wrong version.
2. Flash kernel using your preferred recovery
3. Do the following AFTER installing the kernel and BEFORE you reboot your phone:
a. Clear cache
b. Clear dalvik
c. Fix Permissions
4. Reboot your device.
TW Specific Kernel Instructions:
(can be used with AOSP too)
There are some files on your TouchWiz phone that need to be renamed in order to maximize the battery life of your phone. There has been some debate on whether or not this is necessary, but for now we would recommend renaming these files to ensure that there is no chance of excessive battery drain.
Part 1:
These steps are only necessary on TouchWiz ROMs, however you can also do this on AOSP as well:
1. You must have ROOT. You will need to have a root enabled file explorer on your phone (ES File Explorer works very well and you can get it from the play store (https://play.google.com/store/apps/details?id=com.estrongs.android.pop&hl=en). When you get it, open it up and go the the settings and scroll all the way down until you see the Root Settings. Go in there and enable ALL of the root settings.
2. After that is done, navigate to your root folders using the Folder Up icon at the top. Once you are in your root folders, navigate to /system/bin and locate the following files. You will need to rename them with a ".bak" at the end of the filename
gsiff_daemon --> gsiff_daemon.bak
mpdecision --> mpdecison.bak
qosmgr --> qosmgr.bak
smd --> smd.bak
smdexe --> smdexe.bak
Renaming these files will not harm your phone. Many users rename these files every time they flash a rom, and no damge is done.
Also, some ROMs come with these files renamed or deleted entirely, so if you don’t find a file, don’t be alarmed.
You have to do this every time you flash the ROM and/or Kernel.
If you feel uncomfortable doing this yourself, you can use the TK-MOD (see Downloads section) and it will handle this for you.
Part 2:
Stopping mpdecision from being called:
1. Open terminal emulator and type the following code:
su
2. When terminal emulator asks for root permission hit 'Grant' or 'Allow'.
3. At the # prompt type:
stop mpdecision
Using Rom Toolbox (https://play.google.com/store/apps/details?id=com.jrummy.liberty.toolbox) we will make a script that will stop mpdecision from being called at each boot so you don't need to use terminal emulator each time
1. Open Rom Toolbox and scroll down to the Scripter option
2. In the scripter, click the “+” button in the top right corner, then select 'Create'
3. Type a name for our new script, lets call it “stop mpdecision”
4. In the commands enter the following text:
#!/system/bin/sh
stop mpdecision
5. Hit the disk icon to save it
6. Select the script that you just created and a dialog box should pop up, select set at boot
Were done here
AOSP Specific Kernel Instructions:
When coming from a 3.0 Kernel to a 3.4 Kernel there is a new method with kernel updates. Skipping these steps will cause phone instability, due to some bad data left behind. This is a flaw in the Android OS, not the application. You must follow the instructions below (Thanks ktoonzs for the new method of the ktweaker app)
1. Go to Settings on the phone
2. Go to app manager then all apps
3. Scroll down to ktweaker app n open it
4. Once open hit FORCE STOP and then hit CLEAR DATA
5. Reboot and flash your new update of ktoonzs kernel
6. Repeat steps 1-4 in the above “General Installation” section
You should be good to go after that
Okay so Team Kernelizers now has a place to download the KTweaker backups. This should reduce the number of questions about where the latest tweaks are. All you have to do is download them to your KTweaker folder and in the KTweaker app use the restore feature! Every team member has a folder so you can see all of them all that is in mine is the latest Pegasusq/Zen tweaks from the op. I will have more when I am released from this prison people like to call "work"