[KERNEL][VZW][AOSP/TW/GE - 5.0/4.4/4.3/4.2][02/06/2015] KT-SGS4 - MJ5 - KTweaker

Mistertac · Apr 19, 2014

KToonsified V6
Liquid Smooth

This profile is running great so far. Keep in mind I run a 5200mah battery so.. Hard for me to post my shots sometimes since it can be days and also I tend to reboot a lot. I'm going to try and keep this run going though and update

Sent from my SCH-I545 using Xparent Blue Tapatalk 2

Velocifero · Apr 19, 2014

Mystique said:
What version of the kernel were you running with the V5 vs the V6.

KT 04.07 vs 04.17 just re engineered his ktoonses governor.

So, if you were running kernel 04.07 (or earlier) with V5 and just updated your kernel and wanted something new.. That would be the reason..

I was using the 04.17 kernel version 6.8.

brizey said:
Check the LED settings. Mine is set to then of from hour 23 to hour 6, or 11 pm to 6 am. I honestly can't remember if it was me that set those, lol, so they may be a default.

Sent from my SCH-I545 using Tapatalk

That fixed it thanks! But now my issue is the LED isn't fading. I feel like it's a ROM issue though, not a kernel issue because just before I updated the ROM, it worked. I restored the ROM back and it's working again. Hmm.

Mitch8892 · Apr 19, 2014

Phone Call Screen Wake

Hi, I have searched multiple times and have not been able to find a solution to my issue.

I am running CM 11 nightlies and the latest KT kernel. I have been using KTv6 profile and am having issues with phone calls. If I am in a call and my proximity sensor gets covered even the slightest bit the screen turns off and does not want to turn back on. I have to hit the home button multiple times to get the screen back and then the second battle begins. I cannot get back into the dialer because if my hand gets even close to the sensor the screen will go off again.

What settings should I change and try? I also tried Comatose Whisper profile and had the same issues.

I really hope someone can assist me here, thanks.

jamesd1085 · Apr 19, 2014

Mitch8892 said:
Hi, I have searched multiple times and have not been able to find a solution to my issue.

I am running CM 11 nightlies and the latest KT kernel. I have been using KTv6 profile and am having issues with phone calls. If I am in a call and my proximity sensor gets covered even the slightest bit the screen turns off and does not want to turn back on. I have to hit the home button multiple times to get the screen back and then the second battle begins. I cannot get back into the dialer because if my hand gets even close to the sensor the screen will go off again.

What settings should I change and try? I also tried Comatose Whisper profile and had the same issues.

I really hope someone can assist me here, thanks.

In ktweaker go into tools and click proximity checker...post the reading it gives...may need cleaned may be fixable without taking device apart

Mitch8892 · Apr 19, 2014

jamesd1085 said:
In ktweaker go into tools and click proximity checker...post the reading it gives...may need cleaned may be fixable without taking device apart

I got a reading of 51.

jamesd1085 · Apr 19, 2014

Mitch8892 said:
I got a reading of 51.

Wow...very dirty...mine was at like 32 and gave me issues... After cleaning mine stays around 8-11...you will more than likely have to clean your proximity sensor...its not as hard or scary as it sounds...give me a min and I will post video tutorial link that shows how

The two videos linked here got me through it
http://xdaforums.com/showthread.php?p=50051163&highlight=proximity#post50051163

Some recommended compressed air...I used rubbing alcohol and q-tips...its up to your preference and the tools you have at hand...good luck

Mitch8892 · Apr 19, 2014

jamesd1085 said:
Wow...very dirty...mine was at like 32 and gave me issues... After cleaning mine stays around 8-11...you will more than likely have to clean your proximity sensor...its not as hard or scary as it sounds...give me a min and I will post video tutorial link that shows how

The two videos linked here got me through it
http://xdaforums.com/showthread.php?p=50051163&highlight=proximity#post50051163

Some recommended compressed air...I used rubbing alcohol and q-tips...its up to your preference and the tools you have at hand...good luck

Thanks a ton. I will let you know if this works

jamesd1085 · Apr 19, 2014

Mitch8892 said:
Thanks a ton. I will let you know if this works

Yeah definitely let me know...if that doesn't work I have some questions and ideas on how to help...also let me know through pm or on that other thread so we don't clog up kt's forum

Mitch8892 · Apr 19, 2014

jamesd1085 said:
Yeah definitely let me know...if that doesn't work I have some questions and ideas on how to help...also let me know through pm or on that other thread so we don't clog up kt's forum

Just finished up and my proximity reading has gone from 51 down to 2-3. The screen is waking up from calls now. It worked perfectly. Thanks again

u4icpain · Apr 20, 2014

Phoenix

Sent from my SCH-I545 using Tapatalk

ktoonsez · Apr 20, 2014

AOSP KITKAT 4.4 VERSION:
04.19.2014: http://goo.gl/fKeBrT

Google Edition KITKAT 4.4 VERSION:
04.19.2014: http://goo.gl/Tl8JSn

Touchwiz Kitkat 4.4 VERSION:
04.19.2014: http://goo.gl/A6mNyr
To make wifi work when it wont turn on or connect, change this in the build.prop:
ro.securestorage.support=true TO ro.securestorage.support=false

AOSP JELLYBEAN 4.3 VERSION:
04.19.2014: http://goo.gl/RFpoBL

Touchwiz JELLYBEAN 4.3 VERSION:
04.19.2014: http://goo.gl/gBXPEB

Google Edition JELLYBEAN 4.3 VERSION:
04.19.2014: http://goo.gl/gX2Pfx

Change Log 04.19.2014
1. ktoonservativeq: Optimized new block_cycle code that was causing slow issues for some
2. Updated Ktoonserified v6, so be sure to redownload it to work with todays kernel
3. Updated KTGaming profi.e, so be sure to redownload it to work with todays kernel
4. Probably the fastest version of ktoonservativeq to date
5. Guys on 04.18 test kernel from yesterday, there is no change but might as well update so you are the newest dated file.
6. KTweaker 6.9
7. KTweaker: Added new sub screen when picking ktoonservativeq "Gov Adjustments" screen to give you the choice to show "All Parameters", "ONLY Screen ON parameters", "ONLY Screen OFF parameters" to make it easier to see only the parameters you want to see. Thanks @elesbb for the idea

8. Linux 3.4.87.
9. I was unable to reproduce the inability to download scripts, but I made a change and 2 people have told me it doesnt do that anymore with 6.9 so I think I got it fixed.
10. Updated TWRP for normal EXT4 format with 20 upstream updates and updated curtain image thanks to @9Lukas5, link is here http://goo.gl/jwMSEn
11. Updated TWRP for normal F2FS format with 20 upstream updates and updated curtain image thanks to @9Lukas5, link is here http://goo.gl/Zw1akJ

zman2107 · Apr 20, 2014

Happy Easter thanks for the gift. As always your the man KT . [emoji106]

Sent from my SCH-I545 using Tapatalk

ktoonsez · Apr 20, 2014

zman2107 said:
Happy Easter thanks for the gift. As always your the man KT . [emoji106]

Sent from my SCH-I545 using Tapatalk

Thanks man, everybody enjoy there Easter while I work a 14 hour day

. I need to quit, lol.

ktoonsez · Apr 20, 2014

Updated the change log guys, added 2 new items to bottom.

jorceshaman · Apr 20, 2014

ktoonsez said:
Thanks man, everybody enjoy there Easter while I work a 14 hour day . I need to quit, lol.

I know that feeling. I just got off a 14 hour shift myself. Hopefully I won't have another one tomorrow but either way, I don't work nearly as hard as you after work. You're a machine, man!

Sent from my SCH-I545 using Tapatalk

0reo · Apr 20, 2014

@ktoonsez,
First, thanks for all you do here, and happy Easter.

Next, a question / plea for assistance.

In brief:
I'd like to be able to log cpu frequency BUT I want each frequency hop logged BEFORE it takes place. Log first, then switch.

In detail:
Its meant to be a single-purpose debugging utility to find out what cpu frequency a phone is crashing at so its ok if overall device performance is terrible.

I'm trying to find the minimum stable voltage for each cpu clock frequency. When the voltage is set too low for a particular frequency the phone reboots. The reboot appears at random and figuring out which frequency caused it is my goal. The trouble is that all the cpu monitoring apps I'm aware of seem to display cpu frequency reactively after each frequency hop takes place. If the phone crashes after the frequency hop but before the monitoring app logs it then the log is useless if not misleading. If each frequency hop is recorded before it takes place then the log will tell me both where the cpu was and where it was going when the crash happened. That would make identifying frequencies undervolted to marginal excess so much easier.

Can you help? Please?

Edit to add: While I probably can't pay you what it's worth, I am willing to make a decent donation to help make this worth your while.

brizey · Apr 20, 2014

0reo said:
@ktoonsez,
First, thanks for all you do here.

Next, a question / plea for assistance.

In brief:
I'd like to be able to log cpu frequency BUT I want each frequency hop logged BEFORE it takes place. Log first, then switch.

In detail:
Its meant to be a single-purpose debugging utility to find out what cpu frequency a phone is crashing at so its ok if overall device performance is terrible.

I'm trying to find the minimum stable voltage for each cpu clock frequency. When the voltage is set too low for a particular frequency the phone reboots. The reboot appears at random and figuring out which frequency caused it is my goal. The trouble is that all the cpu monitoring apps I'm aware of seem to display cpu frequency reactively after each frequency hop takes place. If the phone crashes after the frequency hop but before the monitoring app logs it then the log is useless if not misleading. If each frequency hop is recorded before it takes place then the log will tell me both where the cpu was and where it was going when the crash happened. That would make identifying marginally over-undervolted frequencies so much easier.

Can you help? Please?

This is not what you are looking for, but an alternative is to set the maximum to a particular clock speed to test, performance governor, set the voltage, then run a torture test like a benchmarking app back to back a few times to see if you get a freeze or reboot. Then lower the voltage and repeat until you are pretty sure you know where the boundary is. Then move on to the next clock speed. I did that on my old Thunderbolt. Takes forever, but on a battery sucker like that POS, it was worth it.

0reo · Apr 20, 2014

And that's exactly what I've done so far but that only gets you 9x% reliability. I still have occasional reboots that I know are voltage related because I don't get the reboots at all at stock voltages. But I can't figure out exactly which freq./voltage is the problem without the logging I'm asking about. I mean, I could, in theory, after months of trial and error but the logging tool would quickly identify the problem(s).

I can set the frequency with the ktoonsez tools and benchmark test that frequency for an hour and be fine. Then 5min later (or 5hrs later) get a reboot at that same frequency during normal use of the device. So, I want something to help catch that last few percent of reliability that make the difference between a well sorted device and an annoying pain in the butt that reboots a few times a day.

tkacer · Apr 20, 2014

ktoonsez said:
Change Log 04.19.2014

10. Updated TWRP for normal EXT4 format with 20 upstream updates and updated curtain image thanks to @9Lukas5, link is here http://goo.gl/jwMSEn
11. Updated TWRP for normal F2FS format with 20 upstream updates and updated curtain image thanks to @9Lukas5, link is here http://goo.gl/Zw1akJ

ktoonsez -
Thanks for the updated TWRP! Custom curtain is awesome!! just checking but the EXT4 version has "Team Win Recovery Project v2.7.0.1.F2FS" in the title - that was intended, right?

ktoonsez · Apr 20, 2014

tkacer said:
ktoonsez -
Thanks for the updated TWRP! Custom curtain is awesome!! just checking but the EXT4 version has "Team Win Recovery Project v2.7.0.1.F2FS" in the title - that was intended, right?

CRAP, I forget to change that, Ill fix that up right now

[KERNEL][VZW][AOSP/TW/GE - 5.0/4.4/4.3/4.2][02/06/2015] KT-SGS4 - MJ5 - KTweaker

Senior Member

Senior Member

Member

Senior Member

Member

Senior Member

Member

Senior Member

Member

Senior Member

Inactive Recognized Developer

Senior Member

Inactive Recognized Developer

Inactive Recognized Developer

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Inactive Recognized Developer

Similar threads

Top Liked Posts