yashsingh1/xdaforums huggingface dataset:
[AT&T Samsung Galaxy S 4 Original Android Developme] mf1tym:
Thank you guys for the suggestions and guide. I will look into them. Once again appreciate the help.
[AT&T Samsung Galaxy S 4 Original Android Developme] :
Good Luck with it--:good:
[AT&T Samsung Galaxy S 4 Original Android Developme] svs57:
I337, Omega 24, latest KT TW 4.4.2 kernel, MDL bootloader, NB1 GSM modem.

If I flash I337 NB1 LTE modem I lost sound at all.

If I flash back I337 MDL LTE modem everything work.

Is sound issue because of ROM or because of kernel?
[AT&T Samsung Galaxy S 4 Original Android Developme] troyolson92:
Kt better than ever with sweet updates and app!! Any chance of tasker integration? We could create our own widgets and profiles through tasker. At work sip battery profile at home fastest profile one easy example. Just an idea to put it over the top! Also could add info to dashclock through tasker. That would b ulitmate : )
[AT&T Samsung Galaxy S 4 Original Android Developme] 1weener:
Hi KT. 02/24 not working with the newest Skank... not for me anyway. Works great on the 02/27 Skank.
[AT&T Samsung Galaxy S 4 Original Android Developme] CrashTestDroid:
When you change the modem you lose sound, then change back and it works, and you wonder if it's the kernel???
[AT&T Samsung Galaxy S 4 Original Android Developme] svs57:
It's correct. But as I know sound is controlled by kernel and not by lte modem.
[AT&T Samsung Galaxy S 4 Original Android Developme] 1weener:
Not working with cm04 today either.
[AT&T Samsung Galaxy S 4 Original Android Developme] Lord_Micron:
KT Kernel 02/24 worked fine with CM11 Nightlies up to and including 03/03...

With both 03/04 and 03/05 Nightlies upon booting with the KT Kernel it results in a nonstop loop of Phone process crashes.

Reinstalling 03/03 and then KT Kernel results in dialer & acore process crashes, including clearing data and cache on all related apps to those two.

Only save was restoring dialer, phone and contact data from backup.

Tried with 03/05... got the Phone process loop, but reinstalled 03/05 w/out KT Kernel, zero issues.

Possibly a change to the phone functionality that also affects their data structures starting in 03/04 that is causing issues with KT Kernel?
[AT&T Samsung Galaxy S 4 Original Android Developme] ktoonsez:
They created another framework file that I need to add to the bootclass in the ramdisk.
[AT&T Samsung Galaxy S 4 Original Android Developme] 1weener:
Are you on the road again? Reason I ask is because its just a real pain to use the stock kernels.
[AT&T Samsung Galaxy S 4 Original Android Developme] Lord_Micron:
I'm currently 100% operational sitting on KT 02/24 w/ CM11 Nightly 03/03... Patiently awaiting an update from Ktoonsez, who I'm glad was able to so quickly recognize the issue. :good:
[AT&T Samsung Galaxy S 4 Original Android Developme] LuigiBull23:
He's had lots of debugging to do in order to get all the necessary features working properly for next release. So my guess is we should see an update by possibly Monday if not sooner.
[AT&T Samsung Galaxy S 4 Original Android Developme] 1weener:
So is the 3/3 cm11 the latest rom that works with the 24 kernel?
[AT&T Samsung Galaxy S 4 Original Android Developme] LuigiBull23:
Correct but I assure you the next release will have it fixed. In addition to that, you will all love the new wake options he's implemented!! :)
[AT&T Samsung Galaxy S 4 Original Android Developme] 1weener:
Yes, I am well aware that KT will have everything fixed with the next release; I've been using this kernel for years!
[AT&T Samsung Galaxy S 4 Original Android Developme] sprocketty:
Hi guys, am using DANVDH latest build.

Was using the 0218 version, and did an install of the 0304 version.

Now Ktweaker keeps giving me FC.

Tried clearing app data from apps menu, as well as rebooting.

If i clear app data, no FC until i hit the Ktweaker button. Once I Run ktweaker again, it starts to Ktweaker FC upon boot.

Any possible solutions?

1. Can't find "Fix Permissions" on CWM recovery. How do i do this?

2. Would it be possible to reflash Ktweaker for my phone? I'm on Danvdh AOSP Google Rom 4.4.2 which has ktoon kernal built in. Which Ktoons should I flash? Google OR AOSP?

3. I heard it MIGHT be supersu problem. How do i resolve this? Opening SuperSU i don't see ktweaker granted root. But I don't know how to manually grant it since launching ktweaker just gives me FC.

THanks in advance
[AT&T Samsung Galaxy S 4 Original Android Developme] ktoonsez:
Delete ktweaker folder on your sdcard.
[AT&T Samsung Galaxy S 4 Original Android Developme] sprocketty:
Thank you ktoons... Apologies I didnt read about this solution earlier. I was searching the wrong term...
[AT&T Samsung Galaxy S 4 Original Android Developme] ktoonsez:
Change Log 03.06.2014

1. NEW!!!!!!! LED: 3 New options in KTweaker to select from, "Disable LED Start Hour", "Disable LED Stop Hour", "Disable LED Always". Start and Stop value are in 24 hour military time.

2. NEW!!!!!!! "Screen Wake Options" of: Sweep 2 Wake, Sweep 2 Wake ONLY on Charger, Double Tap 2 Wake, Double Tap 2 Wake ONLY on Charger, Both, Both ONLY on Charger.

3. Screen Wake Options: For Sweep 2 Wake, sweep the screen from left to right or right to left to turn on the screen.

4. Screen Wake Options: For Double Tap 2 Wake, double tap the screen if the bottom left corner to turn on the screen.

5. NEW!!!!!!! "Sensor Wake Options" of: Wave 2 Wake, Wave 2 Wake ONLY on Charger, Pocket 2 Wake, Pocket 2 Wake ONLY on Charger, Both, Both ONLY on Charger.

6. Sensor Wake Options: For Wave 2 Wake, hold your hand in from of the proximity sensor for about 1/2 second and then wave it back and forth to turn on the screen.

7. Sensor Wake Options: For Pocket 2 Wake, simply have the phone in your pocket for at least 10 seconds, take it out and the screen turns on.

8. NEW!!!!!!! "Hold Wake Lock for Wake" of: Check them out, there is freaking 18 of them, lol. By using any of these methods you will guarantee that the wake methods will work, without them its a crap shoot. My favorite is "Enabled ALWAYS on LED notif", this will turn on a wake lock when the LED is blinking for a notification and will obey your "Disable LED Start Hour" and "Disable LED Stop Hour" to block a wake lock when u dont want LED on. The name of the wake lock is "kt_wake_funcs" so you can track it when using them.

9. FastCharge: Completely re-did FastCharge interface adapted from Jean-Pierre and Paul Reioux. There are 3 options now for for the main selection (Enabled, Disabled, Custom mA)

10. FastCharge: When Custom mA is selected, it will obey the "Custom USB mA" and "Custom A/C mA".

11. FastCharge: Another new option is "Fail safe", when enabled it will use the lowest A/C or USB value when the cable type is UNKNOWN. When disabled it will allow you to use any custom mA instead of the predefined ones that you will see in Ktweaker when choosing the 2 Custom mA's.

12. Removed some more dmesg spam to keep logs clean and fast.

13. Linux 3.4.82

14. New ADB binry for wifi support.

15. Ramdisk merge from the CM changes for AOSP.

16. KTweaker: KTweaker update to 6.4 adding all the features from above for wake functions and new Fast Charge options.

17. KTweaker: Added menu item on main screen to quick toggle Fast Charge for Enabled/Disabled.

18. Date added to the OP links so everybody knows what the last date that particular kernel was updated last.
[AT&T Samsung Galaxy S 4 Original Android Developme] Droidmissionary:
Is reboot required or anything? can't seem to get the wakes to work. Tried tap, sweep, and wave, with and without wake holder
[AT&T Samsung Galaxy S 4 Original Android Developme] beast3300:
No. However try deleting the kt folder on the sd card and setting up the kernel again.
[AT&T Samsung Galaxy S 4 Original Android Developme] LuigiBull23:
No reboot required.

Sweep 2 Wake: To get this working you need to swipe from the far left of the middle of the screen to the far right.

Double Tap 2 Wake: double tap the far bottom left hand corner of the screen.

Wave 2 Wake: hold your hand over the proximity sensor for at least 1/2 a second then wave your hand back and forth across the sensor.
[AT&T Samsung Galaxy S 4 Original Android Developme] Droidmissionary:
I'll give it a shot

I read the instructions and followed them without success
[AT&T Samsung Galaxy S 4 Original Android Developme] ktoonsez:
Check this file to see what the value is:

/sys/class/sensors/proximity_sensor/raw_data

If it is above 25 then the prox is dirty and needs cleaning. The screen wake options wont work if the prox is greater than 25.
[AT&T Samsung Galaxy S 4 Original Android Developme] Droidmissionary:
Okay, checked it and its reading 28, I have a glass screen protector that covers all the sensors so they can't get dirty but i did clean the screen and get it down to 20, ill retry. However, I deleted the ktfolder as suggested earlier and i can get sweep or double tap to work only once right after reboot and resetting the option, after first attempt it no longer works
[AT&T Samsung Galaxy S 4 Original Android Developme] ktoonsez:
U need to hold a wake lock to make it 100% of the time.
[AT&T Samsung Galaxy S 4 Original Android Developme] Droidmissionary:
alright, nvm. my device doesn't want to cooperate with or without wakelock
[AT&T Samsung Galaxy S 4 Original Android Developme] sloanster:
Thanks for your hard work....

Has your settings changed since???:good:
[AT&T Samsung Galaxy S 4 Original Android Developme] ktoonsez:
Havent decided on final settings
[AT&T Samsung Galaxy S 4 Original Android Developme] gravedigger76:
Any recommended troubleshooting to get both swipe and tap to wake as well as sensor wake working? I have both set while charging (screenshot below). Doesn't seem to want to work in both cases.

I redownloaded KT v5 profile and added these settings. Saved the profile. Re applied profile. What else can I try?
[AT&T Samsung Galaxy S 4 Original Android Developme] ktoonsez:
If you are A/C charging, you might need to hold a wake lock. I have found today that the wall charger does not hold a wake lock like USB does.
[AT&T Samsung Galaxy S 4 Original Android Developme] gravedigger76:
Which hold setting would you recommend? It doesn't have any "while charging" only so does it mean it'll keep wake lock on all the time? Battery impact?
[AT&T Samsung Galaxy S 4 Original Android Developme] ktoonsez:
I use LED mode. With my settings I loose less that 1% an hour (when testing with always on with screen off option), be aware this is NOT a battery option, do not even think that it is.
[AT&T Samsung Galaxy S 4 Original Android Developme] gravedigger76:
Is there any chance to possibly get a setting to hold wake lock only when charging? That way all 3 are on while plugged in :) and battery is not a concern... Or is that even possible?

Like my use case is at night while its on my night stand happily charging. Instead of looking for power button any of the wake up options would be awesome. But when its not charging during day there is no impact on batt :)
[AT&T Samsung Galaxy S 4 Original Android Developme] LuigiBull23:
Hold the Wake lock to "ALWAYS on screen off" then change your wake options to charging only. That will hold the wakelock and allow you to use the options while charging but you will need to switch your settings whenever you do unplug.
[AT&T Samsung Galaxy S 4 Original Android Developme] gravedigger76:
Right. Changing wake lock option manually is one way. Was just thinking if awesome KT can get that option for on charging only that would be sweet.
[AT&T Samsung Galaxy S 4 Original Android Developme] ktoonsez:
Ill add a wake lock option for only charging.
[AT&T Samsung Galaxy S 4 Original Android Developme] gravedigger76:
U the man dude!!!

Thank You!!!
[AT&T Samsung Galaxy S 4 Original Android Developme] LuigiBull23:
Disregard.
[AT&T Samsung Galaxy S 4 Original Android Developme] gerardo87:
My sensor is under 16 :eek: how I can clean up it??? It is dust inside or on the surface of sensor?

Inviato dal mio GT-I9505 utilizzando Tapatalk
[AT&T Samsung Galaxy S 4 Original Android Developme] blueglide:
Its only a problem if it is higher than 25. You should be fine.
[AT&T Samsung Galaxy S 4 Original Android Developme] ktoonsez:
Who is out there that is on Google Edition ROM and cant get the wake functions to work like double tap or sweep 2 wake???? Got a test kernel.
[AT&T Samsung Galaxy S 4 Original Android Developme] gerardo87:
Ok sorry for misunderstanding :D but the configuration of double tap 2 awake Still don't work :(

Inviato dal mio GT-I9505 utilizzando Tapatalk
[AT&T Samsung Galaxy S 4 Original Android Developme] ORT14:
Crap, my sensor reads 43. Any idea how to get that number to drop below 25?
[AT&T Samsung Galaxy S 4 Original Android Developme] rurouni572:
I have around 43 as well. Will this involve surgery for my phone? I have opened it up in the past to replace my broken LCD, but I'd like avoid that if possible. What's this about blowing air into the earpiece?
[AT&T Samsung Galaxy S 4 Original Android Developme] MoeisHere:
Hey guys I really don't know much when it comes to kernel tweaking. I set my kernel settings to ktoonsez's settings. Im on GE rom 4.4.2. The only problem I'm having is when I get a call, the phone rings but the screen is delayed to come on. So the phone is ringing and my screen is still black for a few rings. Anyone know how I can change that? Thank you.
[AT&T Samsung Galaxy S 4 Original Android Developme] terahertz5k:
Mine is also 43 =(
[AT&T Samsung Galaxy S 4 Original Android Developme] kasper67:
Try disabling the "disable screen off MHz call option"
[AT&T Samsung Galaxy S 4 Original Android Developme] MoeisHere:
Tried that still doing the same thing.
[AT&T Samsung Galaxy S 4 Original Android Developme] the_boo:
Flashing now, I will let you know...

Also, my prox sensor used to say 53.... No amount of compressed air would fix it... I had to take the phone apart and clean the sensor and the glass from behind with a qtip, how it reads 6...

It was actually pretty easy to do, all the screws are the same size ...way easier than it old iphone 3gs lol

---------- Post added at 12:20 PM ---------- Previous post was at 12:06 PM ----------

Edit:

Sweep to wake works every time, double tap never works, wave works about 50 percent of the time

On dans GE rom...

Also, of made me laugh out loud that there is a "pocket to wake only while charging " setting haha ;)
[AT&T Samsung Galaxy S 4 Original Android Developme] beast3300:
Try raising screen off MHz to something higher.
[AT&T Samsung Galaxy S 4 Original Android Developme] gorgy76:
katoonz is ahead of time. He had it pocket to Wake only while while charging because in the near future we can use our balls to charge the phone. Hehehe....joke:silly:
[AT&T Samsung Galaxy S 4 Original Android Developme] ktoonsez:
Lol. I added for the people that have the cases that fold over the face of the phone.
[AT&T Samsung Galaxy S 4 Original Android Developme] the_boo:
Did you need someone to test on Dan's ROM?
[AT&T Samsung Galaxy S 4 Original Android Developme] ktoonsez:
OP Updated

Change Log 03.10.2014

1. Improved Sweep 2 wake recognition.

2. Ignore double tap if more than 1 finger is used.

3. New option for "Hold Wake Lock for wake" called "Enabled ONLY while charging" so you can choose to only hold wake lock during charging.

4. Added wake lock montitor so wake locks can be kicked back on if they are killed prematurely.

5. New "Prox value when clear" added so you can specify the prox value to allow the screen wakes to still work when your prox is not functioning properly/dirty.

6. New item under "Tools" called "Prox Sensor Checker". Click it start/stop the monitor timer. Use this to see what you 100% clear prox value is, then add 20 to that number and use it for the "Prox value when clear" value mention in #5 above.

7. LEDs: Added some code that was needed on the TW version to catch all the notification scenerios.

8. Fix the issue where touch screen would become unresponsive on TW ROMs.

9. Thats all I can remember, ENJOY!!!!!
[AT&T Samsung Galaxy S 4 Original Android Developme] david.degraw54:
This update is awesome. All the wake options work now. Sensor wakes weren't working cause I have a thick screen cover but now they work fine because of the changes 5 & 6. I have a question though because my phone never wakes up after a call either, any chance I could change that value so its system-wide?
[AT&T Samsung Galaxy S 4 Original Android Developme] ktoonsez:
Thanks man. That value has nothing to do with phone calls. The ROM controls all of that thru a timer monitoring the prox value.
[AT&T Samsung Galaxy S 4 Original Android Developme] david.degraw54:
So there's no file I could edit that would make it work?
[AT&T Samsung Galaxy S 4 Original Android Developme] ktoonsez:
Not that I know of, its all in java code in the phone.apk
[AT&T Samsung Galaxy S 4 Original Android Developme] david.degraw54:
I actually know some java so maybe I'll take a look.
[AT&T Samsung Galaxy S 4 Original Android Developme] Goliath27:
KT - just flashed the latest build and I'm having the following problems:

1. Force closes when I select the option for screen wake as enabled.

edit: https://www.dropbox.com/s/o6kmm7fbrtbtvee/kt_logcat.txt

2. Display issues where the words overlap.

Any thoughts or solutions? Someone asked me before if I messed with the DPI but I've never done anything like that.
[AT&T Samsung Galaxy S 4 Original Android Developme] ktoonsez:
Your ROM has screwed over your DPI or KTweaker can not find any of the following words in build.prop:

jflte

i9505

i9505g
[AT&T Samsung Galaxy S 4 Original Android Developme] Goliath27:
Ok well, that's what I get for messing with the build prop. I changed it to jflte as you can notice from my XDA app signature below. Now it's working perfectly!

Before, it read "i337 on roids" but thought that was just used for phone name. Can I change it to i9505 or just leave it as jflte?

Thanks again!
[AT&T Samsung Galaxy S 4 Original Android Developme] ktoonsez:
Yes u can use any of the ones I mentioned
[AT&T Samsung Galaxy S 4 Original Android Developme] theshow4life:
Thanks [MENTION=4325945]ktoonsez[/MENTION] for the update your a machine!
[AT&T Samsung Galaxy S 4 Original Android Developme] troyolson92:
+2
[AT&T Samsung Galaxy S 4 Original Android Developme] Goliath27:
Ok so something strange is happening now and I'm not sure if it can be found in my last logcat. But when I'm in a phone call, my screen is off when the phone is to my face as it should be. But when I take my face away, the screen turns on and I'm in some random menu for settings or somewhere in a search.

And even worse, my phone will hang up on the call and enter Airplane mode through my screen even when it's off. Anyone report an issue like that yet?
[AT&T Samsung Galaxy S 4 Original Android Developme] ktoonsez:
Ill look at getting some more protection code in there when on a call. Your face is sweeping the screen and touching your top status bar and pressing things.
[AT&T Samsung Galaxy S 4 Original Android Developme] ktoonsez:
What version of the kernel r u using? If you can replicate problem everytime I can send u a test.
[AT&T Samsung Galaxy S 4 Original Android Developme] Goliath27:
I'm using the most resent kernel for GE 4.4.2 and would be more than happy to help. I'm working tonight and won't get a chance to teat it until later tonight, but more than happy to. For now I've just turned the wake hold off as I think that's what caused it.
[AT&T Samsung Galaxy S 4 Original Android Developme] ktoonsez:
Thanks man, but dont have the time to wait. Anybody else have this problem and can test?
[AT&T Samsung Galaxy S 4 Original Android Developme] beast3300:
I don't think I use those options but if you like I can test.
[AT&T Samsung Galaxy S 4 Original Android Developme] ktoonsez:
Thanks anyway but looking for someone that has and knows the problem. :good:
[AT&T Samsung Galaxy S 4 Original Android Developme] ktoonsez:
Change Log 03.12.2014

1. Improved "on a phone call" code to make sure it is isnt executing the screen wake code while screen is off and you are on a call.

2. Increased speed for wake up on the screen wake functions, sensor wake functions wake a little quicker too but will always be limited by the 1 second timer.

3. Finally found a better spot to trigger and make the screen turn on way quicker when an incoming call is coming in.

4. KTweaker version 6.6.

5. NEW item under "Tools" screen called "Charging Current". You can click on the item and it will update the field with the current mA it is charging at.

6. NEW item under "Fast Charge" called "MTP while fast charging". Enabled will keep MTP on so you can still access the phone, disabled will disable MTP and you will not be able to access it, just simply charges. To take effect this option requires the cable to be unplugged and re-plugged in.

7. NEW item under "Fast Charge" called "Screen ON charging limit". BE VERY CAREFUL WITH THIS ITEM!!!!!!! When enabled it will keep the Samsung limit they imposed of 1200 mA while charging and the screen is on, if it is disabled it will allow you to charge at the full 1900 mA or whatever custom mA you have set for A/C. To take effect this option requires the cable to be unplugged and re-plugged in.
[AT&T Samsung Galaxy S 4 Original Android Developme] theshow4life:
Thanks again!
[AT&T Samsung Galaxy S 4 Original Android Developme] ktoonsez:
Just made a release, hope the new code solves that issue :D :good:. We r on the same ROM so it should.
[AT&T Samsung Galaxy S 4 Original Android Developme] ktoonsez:
I just found a typo in the proximity sensor code used for the "Screen Wake" functions (the issue only occurs when you have "Screen Wake" options on and "Sensor Options" off), be sure to re-download with the same links as earlier to get the latest!
[AT&T Samsung Galaxy S 4 Original Android Developme] Phoneguy589:
Would the AOSP KK kernel work for task's AOKP?

Sent from my At&t Galaxy S4
[AT&T Samsung Galaxy S 4 Original Android Developme] kasper67:
No your WiFi won't work. But you can always try it out, if it doesn't flash the ROM again.
[AT&T Samsung Galaxy S 4 Original Android Developme] Goliath27:
Sweet you're using the Dan KitKat rom too? So I'm using the GE version of your kernel, that's the right one right?

Downloaded and flashing the new update. Will do a test run now with my wife's phone.
[AT&T Samsung Galaxy S 4 Original Android Developme] ktoonsez:
Yes, Dan and I got the kernel/ROM going for Verizon so I could run it too :D
[AT&T Samsung Galaxy S 4 Original Android Developme] beast3300:
Hey kt, have you seen or heard of WiCubic TCP congestion protocol? I have been reading and researching them when bored.
[AT&T Samsung Galaxy S 4 Original Android Developme] ktoonsez:
No, never heard of that one. Did a quick search to and nothing code wise came up.
[AT&T Samsung Galaxy S 4 Original Android Developme] beast3300:
I guess it is better suited for mobile devices. Something, something; dark side. Thanks for checking.
[AT&T Samsung Galaxy S 4 Original Android Developme] SeanHacker:
Try this one and let me know if wifi works. Thanks. :D

ROM DOWNLOAD
[AT&T Samsung Galaxy S 4 Original Android Developme] ktoonsez:
Anybody try it yet????
[AT&T Samsung Galaxy S 4 Original Android Developme] jrod091:
Tested and can confirm working WiFi!
[AT&T Samsung Galaxy S 4 Original Android Developme] ktoonsez:
Thanks for testing man. Glad that worked out :D :good: :highfive:
[AT&T Samsung Galaxy S 4 Original Android Developme] Goliath27:
Ok all done. I tested a call before flashing and my phone was doing all sorts of stuff.

After flashing, call went perfect and nothing on my screen was activated. No random Google now searches or drop down menu! Thank you KToonz!

One random tidbit, when selecting options like fast charging or vibration settings, it would freeze and fc. I've already deleted the cache and the ktweaker folder before I could use the ktweaker.
[AT&T Samsung Galaxy S 4 Original Android Developme] ktoonsez:
That happens if you are using xsposed or gravitybox, so Im guessing you are using them?