yashsingh1/xdaforums huggingface dataset:
[Galaxy S 4 i9505 Original Android Development] DildoMaster:
I'm on a Verizon GS4 running Hyperdrive 18.1 and am having a strange problem. The phone will work perfectly fine for an undetermined amount of time but then suddenly my notifications completely cease. No facebook, SMS, Hangouts, Gmail, etc. Super annoying but fixed with a reboot until it inevitably happens again without warning. Anyone else had this problem and know how to fix?

By the way, I believe I'm running the Project Icarus - Performance Profile from the Ktweaker shop. This is one of the few that doesn't cause a bootloop on my device for whatever reason.
[Galaxy S 4 i9505 Original Android Development] elzangi:
But often my s4 stuck on boot, almost on every boot or reboot. It's a miracle if after 3 or 4 continuos reboots it boot. I have to pull down battery and do something similar. I use CM11 M9.
[Galaxy S 4 i9505 Original Android Development] tuniel:
proximity sensor

Hi [MENTION=4325945]ktoonsez[/MENTION],

i'm facing a strange issue with the proximity sensor.

I'm using GB's active screen and proximity wake up functionality, but it seems they don't work due to an odd behavior of the proximity sensor.

long story short: when the listener is activated, the proximity sensor always shows first the uncovered value (8.0 cm), then it shows the actual value.

this effectively defeats any trial in using the proximity sensor to control the wake up of the phone (i.e. pocket mode)

i tried a different kernel and the results are the same.

is it something that can be worked around at a kernel level?

thanks

GB:ModPower: Proximity sensor listener resgistered
GB:ModPower: onSensorChanged: value=8.0; maxRange=8.0; mProxSensorCovered=false
GB:ModPower: Proximity sensor listener was not alive; scheduling unreg
GB:ModPower: Waking up...
GB:ModPower: onSensorChanged: value=0.0; maxRange=8.0; mProxSensorCovered=true
GB:ModPower: Proximity sensor listener unregistered
GB:ModPower: Proximity sensor listener resgistered
GB:ModPower: onSensorChanged: value=8.0; maxRange=8.0; mProxSensorCovered=false
GB:ModPower: Proximity sensor listener was not alive; scheduling unreg
GB:ModPower: Waking up...
GB:ModPower: onSensorChanged: value=8.0; maxRange=8.0; mProxSensorCovered=false
GB:ModPower: onSensorChanged: value=0.0; maxRange=8.0; mProxSensorCovered=true
GB:ModPower: Proximity sensor listener unregistered
GB:ModPower: Proximity sensor listener resgistered
GB:ModPower: onSensorChanged: value=8.0; maxRange=8.0; mProxSensorCovered=false
GB:ModPower: Proximity sensor listener was not alive; scheduling unreg
GB:ModPower: Waking up...
GB:ModPower: onSensorChanged: value=8.0; maxRange=8.0; mProxSensorCovered=false
GB:ModPower: onSensorChanged: value=0.0; maxRange=8.0; mProxSensorCovered=true
GB:ModPower: Proximity sensor listener unregistered
GB:ModPower: Proximity sensor listener resgistered
GB:ModPower: onSensorChanged: value=8.0; maxRange=8.0; mProxSensorCovered=false
GB:ModPower: Proximity sensor listener was not alive; scheduling unreg
GB:ModPower: Waking up...
GB:ModPower: onSensorChanged: value=8.0; maxRange=8.0; mProxSensorCovered=false
GB:ModPower: onSensorChanged: value=0.0; maxRange=8.0; mProxSensorCovered=true
GB:ModPower: Proximity sensor listener unregistered
[Galaxy S 4 i9505 Original Android Development] Jsilver73:
Nothing to do with kernel, you need to recalibrate your proximity sensor > thread here <
[Galaxy S 4 i9505 Original Android Development] tuniel:
My sensor is OK. Using built in proximity sensor checks I read 5 when free and 255 when covered. It is not a problem of calibration. The problem is that when the listener is called, the sensor broadcasts a free signal at first and then the actual value. (Using Google sensors API)

So it might have something to do with the kernel or maybe it can be fixed at a kernel level
[Galaxy S 4 i9505 Original Android Development] elzangi:
Unknow baseband, empty IMEI and empty signal with your last kernel and last CM11 snapshot (M10)

There's also an often boot hang/freeze/stuck on SplashScreen and blue led blinking

Widget cause Ktweaker Crash when appling a profile and IR blaster doesn't Work very well (watchon make my Cm11 fast reboot when i try a panasonic projector device)

We need a update now [MENTION=4325945]ktoonsez[/MENTION].

We know that you're busy with your real work, but we all need you and your best kernel!
[Galaxy S 4 i9505 Original Android Development] 9Lukas5:
Hey, the kernel is only usable with the M9 and the Nightlies before.

So it's logical that the M10 will give you the same results as the Nightlies after the M9. He's busy and will update when he has time and the mood to do so. He knows that the kernel isn't compatible, to tell it again won't change anything. You could ask politeley in future.

L
[Galaxy S 4 i9505 Original Android Development] smeroni68:
... and nobody here is payed for his "free time job"... So avoid asking ETA, because it is not allowed on xda.

Inviato dal mio GT-I9505 utilizzando Tapatalk
[Galaxy S 4 i9505 Original Android Development] ustazshifu:
Are you kidding us here with "......update now......" to our dev? ? No matter what anyone mean by saying that kinda word, it's still not appropriate. Even if you "contribute" (hear the word with both ears....) 1000usd to [MENTION=4325945]ktoonsez[/MENTION] each month! Be realistic & reasonable dude.
[Galaxy S 4 i9505 Original Android Development] radz_:
Is this Kernel dead? No more update since July
[Galaxy S 4 i9505 Original Android Development] MatteoB92:
The developer is strictly busy with his real life, especially work
[Galaxy S 4 i9505 Original Android Development] ipois0n1:
fast charge doesnt work at all. whether i set it to enabled or custom, it

NEVER

goes above 900mA (which is extremely pathetic imho)

i'm using the official charger that came with the phone. it has a theoretical output of 2 amps (so providing more than 1A shouldnt be much of a problem)

do you guys have any idea why it wont go up?
[Galaxy S 4 i9505 Original Android Development] munichsfinest:
First of all, fast charge affects charging via USB, not via the actual charger. For me, it charges perfectly with 1000 mA (default 460) via USB and 1900 mA (default) via charger. Did you try another charger and cable? Maybe something's broken there. Furthermore, in case you might not know it, you have to unplug the cable and plug it in again after changing charging options in KTweaker, otherwise it doesn't work with the new settings.
[Galaxy S 4 i9505 Original Android Development] ipois0n1:
yea i know it does not affect the charger itself, how could it even. tried the cable from a s4 mini and it somehow works now. seems like my cable was faulty, even though i dont know why
[Galaxy S 4 i9505 Original Android Development] dclarkg:
You don't know the cable is faulty until you try a good cable, I had the same issue
[Galaxy S 4 i9505 Original Android Development] 012512:
My phone is still having a hard time booting up. It will just stop at samsung logo for a moment with led light notification blinking blue and then continue to boot up after a minute or so.

In addition, I cannot boot my phone when the phone is off while charging.
[Galaxy S 4 i9505 Original Android Development] rauschkugl:
If you don't provide logs you should at least tell us what kernel you're on. But probably none of your problems are kernel related if you start with a clean phone.

Gesendet von meinem GT-I9505G mit Tapatalk
[Galaxy S 4 i9505 Original Android Development] 012512:
It is kt kernel. Nothing is wrong with other kernels.
[Galaxy S 4 i9505 Original Android Development] rauschkugl:
There are 3 different kernels from Kt for our device.

Gesendet von meinem GT-I9505G mit Tapatalk
[Galaxy S 4 i9505 Original Android Development] smeroni68:
But witch rom are you using? Of witch date?

Inviato dal mio GT-I9505 utilizzando Tapatalk
[Galaxy S 4 i9505 Original Android Development] 012512:
Touchwiz kernel with a date of 7.12.

Oh. I'm using Imperium rom since v8 with kt kernel on it.
[Galaxy S 4 i9505 Original Android Development] smeroni68:
I asked the rom you are using... The Kernel is clear witch is...

Inviato dal mio GT-I9505 utilizzando Tapatalk
[Galaxy S 4 i9505 Original Android Development] 012512:
Like I said it is imperium rom. V10
[Galaxy S 4 i9505 Original Android Development] smeroni68:
Do you have a direct link to this rom thread?

Inviato dal mio GT-I9505 utilizzando Tapatalk
[Galaxy S 4 i9505 Original Android Development] smeroni68:
No problem I found it... Here the post with change log:

http://xdaforums.com/showthread.php?p=51659534

V10 is of 08 August... Can be it is based on new sammy kernel sources.

Probably V9 is working with KT, but V10 is exactly around the kernel sources change date... If this is the case, kt is not compatible with V10.

Inviato dal mio GT-I9505 utilizzando Tapatalk
[Galaxy S 4 i9505 Original Android Development] shysstkille:
Hi my friends,can you recomend a profile that is nice booth for the battery and the speed in the phone?

After I have downloaded a profile and also done a restore from sdcart to activate the profile I restart my phone,when I after that open the ktweaker I got a window with the text "your saved GPU Governor does not match current,apply cpu governor",what should I choose there,yes or no?

best regards
[Galaxy S 4 i9505 Original Android Development] kyan31:
I have no signal when I flash this on Mahdi, this is my favourite kernel! Any idea why this is happening? Thank you.
[Galaxy S 4 i9505 Original Android Development] smeroni68:
May be because the kernel is older and not updated?

Inviato dal mio GT-I9505 utilizzando Tapatalk
[Galaxy S 4 i9505 Original Android Development] SkyKer93:
Choose ktoonsified v6 im very happy with the profile.

You should choose yes so the app can change the CPU settings if not than the profiles settings will not be applied.
[Galaxy S 4 i9505 Original Android Development] ipois0n1:
thought i fixed it with the cable but now it came back. same new cable (checked the old one, even worse), same charger, same usb port and with fc enabled or set to custom, i cant get over 460mA on usb 3.0 and 1200mA on ac adapter. tried reflashing the kernel and wiping dalvik + cache but it still wont work again. any ideas? :rolleyes:
[Galaxy S 4 i9505 Original Android Development] KingTLR:
Charge to 1900mA only with screen off, otherwise 1200mA screen on
[Galaxy S 4 i9505 Original Android Development] ipois0n1:
screen on charging limit is disabled.

also, it worked with the screen on before at 1,9amps, plus galaxy charging current doesnt even show the correct set max value, which leads me to the conclusion that ktweaker just doesnt apply the values.
[Galaxy S 4 i9505 Original Android Development] tabish84:
From where can I get the .tar file of this kernel

Touchwiz
[Galaxy S 4 i9505 Original Android Development] phil.o:
Same answer as here.

°°° tapatalked °°°
[Galaxy S 4 i9505 Original Android Development] DasXardas:
Update

Any informations about new update of this great kernel? :(
[Galaxy S 4 i9505 Original Android Development] dclarkg:
I seriously doubt this great Kernel will be updated ever again :(
[Galaxy S 4 i9505 Original Android Development] kapiszon53:
Hi I'm running slim kat stable and I can't load profiles from sdcard. I tried to fix permissions by myself but it didn't worked.
[Galaxy S 4 i9505 Original Android Development] senur3:
how is the battery life on this kernel?
[Galaxy S 4 i9505 Original Android Development] gerardo87:
I hope to see an update in future ( I remember the words of the developer who said he would update this kernel though now it was mostly on s5) [emoji20]
[Galaxy S 4 i9505 Original Android Development] dclarkg:
He is busy with his work and with the s5 but I'm sure he will update the kernel if he finds time, I do understand that he doesn't have enough time and that he will choose to develop more for a device that he owns if spare time is found. Eventually we all move on to newer devices :silly:
[Galaxy S 4 i9505 Original Android Development] gerardo87:
Yeah I understand he's busy and in fact my words isn't a complaint, mine is just hope to see he here again[emoji16] real life and work is more important than an update [emoji6]
[Galaxy S 4 i9505 Original Android Development] senur3:
hi guys i did not understand how i can do this to make the wifi work
[Galaxy S 4 i9505 Original Android Development] rauschkugl:
Use a root Explorer and navigate to the system folder. Edit the line described in the build.prop file and save it.

Gesendet von meinem GT-I9505 mit Tapatalk
[Galaxy S 4 i9505 Original Android Development] elzangi:
Anyone have msm_hsic_host bug? My phone stay a lot awake with screenoff with this kernel wakelock...
[Galaxy S 4 i9505 Original Android Development] Shiroh1ge:
Since last update I lost my signal... anyone met this problem? Using i9505 and Carbon ROM. Stock kernel works fine.
[Galaxy S 4 i9505 Original Android Development] elzangi:
All says that developer is busy with its own real work, I think that kernel development is discontinued!

Inviato dal mio GT-I9505G utilizzando Tapatalk
[Galaxy S 4 i9505 Original Android Development] GabrielSousa:
i miss this kernel :(
[Galaxy S 4 i9505 Original Android Development] ISF:
The kernel is still working rock stable for me.

Sent from my BHPowered S4
[Galaxy S 4 i9505 Original Android Development] RayySP:
Yup! Same goes to me.

Sent from my SM-N910S
[Galaxy S 4 i9505 Original Android Development] GabrielSousa:
this work on the last CM builds ?
[Galaxy S 4 i9505 Original Android Development] vagaBond07:
Where art thou your awesomeness?

---------- Post added at 01:30 PM ---------- Previous post was at 01:29 PM ----------

I don't think so, CM had updated their build since early August. Im using Alucard now, since it works for F2FS file system
[Galaxy S 4 i9505 Original Android Development] GabrielSousa:
thats why i miss this kernel ;)
[Galaxy S 4 i9505 Original Android Development] FcukBloat:
hi guys, sorry if this was asked before but can't search the thread with tapatalk and don't have a pc available .

i tried this kernel (aosp version) to try dt2w feature with carbom rom and dt2w seems to work fine :) problem is that as soon as i flash this kernel, i loose ril :( no line at all.. did others have the same problem? is there a fix? thanks in advance and sorry again if that has been answered before
[Galaxy S 4 i9505 Original Android Development] pitastrudl:
Kernel hasnt been updated in a while, so it's incompatible with all the latest aosp roms.
[Galaxy S 4 i9505 Original Android Development] FcukBloat:
thanks for the answer my friend! what a pity.. so can i ask you if you know if there is another and more updated kernel around here with dt2w support? thanks in advance
[Galaxy S 4 i9505 Original Android Development] dclarkg:
So far only KT has dt2w
[Galaxy S 4 i9505 Original Android Development] Solace50:
it occurs for others as well just not noticed by many, there is a patch in regards to this but unknown if the s4 kernels have it implemented, your best bet is to find a more active kernel dev and try your luck and maybe get a test build. for myself the msm_hsic_host wakes the phone way too much as well being about 5-10% of idle time not allowing deepsleep. i highly doubt this kernel will get an update anytime soon if ever, just check the ops postings to see that his attention is directed to the s4 kernel and has also neglected issues posted 6-8 months ago that a few others confirmed existed. try other kernels to see if they remedy the issue, googys max kernel seems solid but still suffers from the same issue. its not that bad but the phone should not be awake for 2hours a day because of it.

honestly this was one of the more flexible kernels with a proper ui but i believe its a lost cause for the time being.
[Galaxy S 4 i9505 Original Android Development] ghira283:
hello guys, if you want me ask you about s4 tw rom 4.4.4 all works, other Kernell year problems with recognition on the PC, thanks and sorry for my English translated

Inviato dal mio GT-I9505 utilizzando Tapatalk
[Galaxy S 4 i9505 Original Android Development] moeburn:
Are there any kernels that ARE?
[Galaxy S 4 i9505 Original Android Development] munichsfinest:
Googy, Alucard,...
[Galaxy S 4 i9505 Original Android Development] WerWolv:
Would it be possible to add the kexec Hardboot patch to this Kernel? I really like it because it has some very unique features but I also like Multi-ROM... It would be great if we could use both at the same time. :3
[Galaxy S 4 i9505 Original Android Development] dclarkg:
Last update on this kernel was like 4 months ago and I don't think it will be updated ever again :(
[Galaxy S 4 i9505 Original Android Development] -sandro-:
I tried every possible kernel and I was never able to fix it, it doesn't happen when you're on WiFi. I'm starting to believe the bootloader could be responsible?!

For instance tonight I went to sleep at 2am with 50% I woke at 10am and I lost 27% of battery while being on standby, the phone has been awake for 35m all connected to that walelock. Signal was high and stable and battery graph with shows a deep slope with no evident stay awake time.
[Galaxy S 4 i9505 Original Android Development] Fevves:
The msm_hsic_host wakelock is present cause the 3G modem is connected to the phone as an external USB device controlled by the hsic host controller. At lest that is what everyone is stating.

How about stop blaming the kernel and do somehomework? Google Play Services is the hint for you and if you want your battery back, this is the wrong thread for that re your particular query. Another hint could, and might, be to limit that particular wakelock in any manner available and carry on.

[MENTION=4176798]Solace50[/MENTION]: Do you even have an idea of what are you talking about? Fixing the articular kernel for what Google INC is f00king up with their constant bloated updates of GPS is a nonsense. You would have to have like a stable release every month so to accompany their BS (that plagues GPS from the moment they invented it).

The flavors of KT acted like this all around with default settings/profiles? NO. Why should anyone blame the kernel for this after so much time it was performing well? Beats me...

EOL
[Galaxy S 4 i9505 Original Android Development] -sandro-:
I never said the problem was the kernel, someone suggested to try different kernels and I answered it's unrelated. Also I'm well aware of that problem coming from the nexus 4 but I believe on the s4 the problem is different because it happens randomly, sometimes the wakelocks don't appear and sometimes this rogue process drains the battery.
[Galaxy S 4 i9505 Original Android Development] Fevves:
Use BBS and other tools, pinpoint the app and/or services provoking these (logcat, dmesg reads etc), or have a (simple) go onto Amplify with Xposed, tame it and whirl on.

/EOL
[Galaxy S 4 i9505 Original Android Development] -sandro-:
Already tried all of it, no success. Only thing left to try is the new bootloader, I'm not sure if that could even be related.
[Galaxy S 4 i9505 Original Android Development] A-Sweaty-Wombat:
Guys, every time I flash this kernel my touch screen stops responding to touches. I follow the install procedure and wipe cache, dalvik and fix permissions after flashing but it always results in the same thing.

Any suggestions?

I really like this kernel and this actually happens with other kernels too. Not all but some. I'm using :

GOOGLE EDITION 4.4.4 by Danvdh, Kryten2k35 & Ktoonsez

However, if I use the 4.4.2 edition of the ROM then the phone works fine but on anything else the touch screen stops working. I need to use a custom kernel because I'm using GT-I9505 and it just randomly reboots on GOOGLE EDITION 4.4.4 by Danvdh, Kryten2k35 & Ktoonsez ROM.
[Galaxy S 4 i9505 Original Android Development] DasXardas:
out of development?

I think this kernel is out of development. :( I was good kernel, but It haven't any updates for a long time. :(
[Galaxy S 4 i9505 Original Android Development] vagaBond07:
You may try Alucard, one of the best custom kernels out there.
[Galaxy S 4 i9505 Original Android Development] Fevves:
So, try using tasker and a script for airplane mode from certain hours 'till morning certain hours, then Amplify to tame that particular wakelock, say at 900. If that's the only wakelock you see pestering your battery - it should be ok after this. It's a workaround and a solution at the same time, seen you tried changing modem. I had newest google services draining mine, all swell and ok now at <0,6 rate at night. Can get my 4 hours screen time back with 22hrs on one charge with my usual usage. I would also suggest xposed with Intelli 3G if you're not on ART. Do some nandroid, or even try to restore before this behavior, clean cache and dalvik and see how it goes.

BTW, have you also tried asking in BBS thread? Might be an idea, seen people over there are really knowledgeable. Just be sure to follow the protocol for posting logs and dumps.

[MENTION=4325945]ktoonsez[/MENTION] is active on XDA and if he feels S4 should be having an update, I'm sure he will return and add a final version. Can't blame people for switching devices and dedicating their time to other projects and family.
[Galaxy S 4 i9505 Original Android Development] mooop12:
I installed this kernel on my newly flashed SlimKat rom. It breaks GSM and WiFi. I tried adding the line specified in the OP to the build.prop file but it has not fixed anything. I'm not sure what is wrong and I don't think it's anything I did.
[Galaxy S 4 i9505 Original Android Development] Dijkstra88:
Try another kernel instead. Ktoonez kernel hasn't been updated for a while now, so that could be your problem. Look for alucard_24 or Googy kernel.
[Galaxy S 4 i9505 Original Android Development] munichsfinest:
It isn't compatible with ROMs based on CM due to major changes almost 3 months ago. As this kernel seems to be dead sadly, you're left with the choice between another kernel and an older ROM.
[Galaxy S 4 i9505 Original Android Development] mooop12:
Ohh okay then, thanks for the replies. I'll try the kernels Dijkstra88 listed and see which one performs better.
[Galaxy S 4 i9505 Original Android Development] rlorange:
I switched to Nova mid lag session and it was on Nova too. Switching to TW cured it... For me it persists till I so something to fix it. Annoying and can't pin down the cause yet
[Galaxy S 4 i9505 Original Android Development] iamnotkurtcobain:
Which governor/scheduler and other stuff?

Gesendet von meinem GT-I9505 mit Tapatalk 2
[Galaxy S 4 i9505 Original Android Development] rlorange:
I've tried every combination. Its the home screen on the launcher that stutters but other apps are unaffected. Almost like GPU acceleration fails for the launcher alone
[Galaxy S 4 i9505 Original Android Development] 9Lukas5:
[MENTION=4325945]ktoonsez[/MENTION], I have installed the nightly from today with your latest aosp kernel 26th, is there anything new in cm that prevents my wifi from connecting?

It sees my wifi network, but doesn't connect

Edit: cm10.1 nightly from 26th is working with your latest kernel, so staying with that for now :good:

L
[Galaxy S 4 i9505 Original Android Development] notegalaxy:
I get this too. Rebooting the phone solves it.
[Galaxy S 4 i9505 Original Android Development] ktoonsez:
Work on UVing to reduce heat :good:
[Galaxy S 4 i9505 Original Android Development] ktoonsez:
ZERO kernel updates in 4 days on CM, Im on 28th nightly until about 1/2 hour ago now on 29th and all still good. :good:
[Galaxy S 4 i9505 Original Android Development] rlorange:
Switch to TW launcher and back again solves it. Saves s reboot
[Galaxy S 4 i9505 Original Android Development] egendomligt:
I've been experiencing this behavior too, but in CM. With stock kernel, and KT. Switching to another launcher (from Nova, which is what I'm using) solves it there too.
[Galaxy S 4 i9505 Original Android Development] hisname:
okay, I am on Google experience rom, I flashed the touchwiz kernel, but how come it doesn't have init.d support? also, I have a FC when I click on voltage table section. is this a known issue as I have searched, but no result. if it is an unknown issue, I will post a logcat of the FC