yashsingh1/xdaforums huggingface dataset:
[Galaxy S 4 General] robertostorm:
Hello [MENTION=4167023]AndreiLux[/MENTION] can you pls fix the kernel, for it to work on cm11?
[Galaxy S 4 General] ice.modding:
i cant use this kernel, when the finish flash, im go to open synapse and not open. Weird :( but in my status phone the kernel is flashed :/ any idea why? :eek:

when i open synapse: No UCI support detected. :(
[Galaxy S 4 General] HassanM:
Make sure Synapse has been granted Super User access...
[Galaxy S 4 General] ice.modding:
yes. :/ i tried full wipe, but no change... same message :( No UCI support detected, but i dont know why! I'm on firmware INU with Omega v20 :/
[Galaxy S 4 General] NEOAethyr:
[MENTION=4491473]ice.modding[/MENTION]

The 1st run on the new kernel, at least for me..., kinda screws up and supersu doesn't notice it.

If you are able to close synapse down after running it for the 1st time, then re-run it, supersu should catch it and ask if you want to grant it super user access from then on.

Otherwise, the only thing I can think of is the kernel needs to be re-installed.

I got that once on an older kernel, synapse was missing so I had to re-install the kernel.

I use philz touch to flash the kernel.

To close most apps down, hold the middle button thing select close all.

That might eventually get rid of the blacked screen 1st run synapse, your launcher may crash but after that everything should be fine.

If the thing becomes 100% unresponsive, press the power button, eventually it'll register that and go into sleep mode.

From there just press the power button again and you'll get back to the launcher, which at this point probably crashed, but its not a biggy.
[Galaxy S 4 General] ice.modding:
Well, it did not work, the truth seems too weird. Now I installed cyanogen, does not work with this right? :'(

ice tapatalk
[Galaxy S 4 General] sak500:
on wanam 4.4.2 rom, nothing wrong with the default kernel but when i install perseus l2_hsic wake lock doesn't let it go into deep sleep. Changed many settings in snaypse nothing works. restarted many times, left it overnight on charge etc nothing fixes it unless i install another kernel.
[Galaxy S 4 General] zetlaw:
i had that too. i guess its wanamrom bug. on Thunder it doesn't happen.
[Galaxy S 4 General] sak500:
easier to change kernel than rom ;) I'll switch to omega kernel

edit: Solved by flashing another modem.

edit#2: Back again after restart so had to install omega kernel.
[Galaxy S 4 General] aashuG:
I just reflashed the kernel using better battery stat i found that I2_hsic wakelock keeps awake the phone
[Galaxy S 4 General] ivanchin99:
Faulty sensor?

While restoring titanium backups
[Galaxy S 4 General] skivnit:
L2_hsic wakelock existed in early kernel versions as well. Don't understand why AndreiLux thinks it's a user's problem
[Galaxy S 4 General] zetlaw:
Because its a user problem. In some roms it doesnt happends. Meaning user problem.
[Galaxy S 4 General] skivnit:
I'm using stock rom so...
[Galaxy S 4 General] JaviLerma:
Rom stock, odex, Intelli3g, Greenfy.

Enviado desde mi GT-I9500 mediante Tapatalk
[Galaxy S 4 General] ice.modding:
anyone know because some AOKP kernel it works correctly and sometimes not? for example in official cyanogenmod does not work, but if it works AICP?
[Galaxy S 4 General] NEOAethyr:
Pretty sure Ive said this before, I'm on I9500UBUFNB3 TTT, samsung ~stock rom 4.4.2.

Tweaked rom or not the kernel doesn't work on my side.

It just locks when charging during sleep.

Plus I think it doesn't goto sleep anyways... it ate a ton of my battery when I had it just sitting around, shutdown and not charging.

I can get synapse working np, it just takes a 2nd run after the 1st run crashes...

Supersu doesn't catch it the 1st time around so synapse just sits at a back screen waiting, pretty sure that's what's happening.

But I don't even care about that.

I just want the kernel not to hardlock my phone when I shut it down with the usb pugged in, previous perseus kernel ver's didn't do that, on roms 4.3 and 4.2.2.

It's been like a month since the kernel release I have been using the stock kernel the whole time because it's broken.

It's not a user error..., it mucks up on a untouched rom...

If someone here knows a 4.4.2 samsung stock rom that actually works with this kernel say which one it is... ^^

I don't think it even matters what region you flash...

I've never tried flashing a diff one though, I always stuck with ttt (my stock).

... Offtopic

I stick with the stock roms, I've just been gutting & tweaking them to my tastes.

The custom roms are like aosp's, I'de rather use the samsung setup myself, at least for now.
[Galaxy S 4 General] zetlaw:
Im using my own rom with this kernel. At first i had few problems like wakelocks and a15 cores not working. But after few restarts and clear cache. It got fixed.
[Galaxy S 4 General] zetlaw:
Logcat i cought with the problem occurs.

it seems this bug comes and goes. restart sometimes solve this issue.

https://mega.co.nz/#!8xFziLxD!tdiuYZEe8da9XkUEcAzuPxrkiwM6Gmqf7Ib5nXx9Zn4
[Galaxy S 4 General] farid993:
[MENTION=4167023]AndreiLux[/MENTION]

Persian translation added.

And i have a request. Is it possible to add vibration intensity controller?
[Galaxy S 4 General] AndreiLux:
I don't think so but I'll look into it.
[Galaxy S 4 General] ice.modding:
why you think your kernel does not work on official cyanogen, but in other custom roms such as AICP?
[Galaxy S 4 General] NEOAethyr:
Possible to add support for loading /etc/sysctl.conf during boot ?

I've got a half dozen network tweaks I put in there, but at the moment I have to apply them via shell script.
[Galaxy S 4 General] StellMonkey:
I'm using ROM switcher and it works with latest cm nightly
[Galaxy S 4 General] ice.modding:
I'd without a rom switcher
[Galaxy S 4 General] NEOAethyr:
A min ago I just restored to 4.2.2 from 4.4.2.

I wanted to check the difference in gamma radiation readings in cpm, between the 2 roms.

Radiation readings were double that then normal, and it hasn't rained in a few days.

Well to end this offtopic stuff, it's the rom, I get 2-3x more cpm then the 4.2.2 rom (new cam firmware apparently sucks).

Anyways.... :) to the point.

After restoring, to a 4.2.2 rom that had perseus already on it, of course the sound didn't work lol...

So I did a power off, and guess what?, it hard locked like it does on 4.4.2.

I went from 4.4.2 with stock kernel, to 4.2.2 with perseus kernel.

The same exact crash that happens on 4.4.2 with perseus happens on the older rom with the older kernel.

Shutdown, plug in the usb cable and crash, have to pull the battery.

This never happened before on 4.2.2.

So it's something todo with the bootloader or something.

And yeah I've always updated the bootloader.

Never had a prob with knox until I flashed perseus on 4.3... but I don't even care.

I think I now know why AndreiLux hasn't had issues...

Because dudes on the stock 4.2.2 bootloader probably...

Edit:

(Offtopic, cam's are the same on both roms, I was getting high readings last night for some reason, just wanted to clear that up, that the cam firmwares were not diff)

(I know this doesn't have anything todo with the kernel, it's just what led me to find out the bug with the older kenel and new bootloader)
[Galaxy S 4 General] skivnit:
I fixed my wakelocks issue by flashing maxfu kernel so no it isn't a user fault and my s4 is getting a great battery life. I think you should into the l2_hsic wakelock as it's kernel related
[Galaxy S 4 General] AndreiLux:
I'm on the KK bootloader.

It's not kernel related.
[Galaxy S 4 General] NEOAethyr:
Huh, hmm :).

Weird.

I wonder what the heck is causing my hardlock after shutdown when the usb is plugged in then.

It only happens on perseus on 4.4.2 nb3.

Before I updated past 4.3, I had no probs.

Now if I recover back to 4.2.2 I have the same probs as 4.4.2.

Unless I use the stock kernel, then there's no prob.

I checked the power thingy in synapse and it wasn't saying unstable or anything like that.

I'm gonna try it again, and post back my usb power readings, I'll try a charger instead of my pc as well this time.

This will be my 3rd or 4th time trying it on the newer rom.

Still, .... why would it not would it not be working on the older roms now when it used to...

AndreiLux

What exact rom are you using?

Can you point to which one from here, pointing to the dl link would help so I know the region and ver:

http://samsung-updates.com/device/?id=GT-I9500&details=Galaxy_S_4__Exynos_Octa

The ttt I9500UBUFNB3 is just not working out.

Really that's the only thing I've been waiting on, is the kernel, after that I can update my apps and all that, I got my emu working so I can sandbox new apps to check for spyware again (I do that every time I do a round of updates).

I don't mean to bug the crap out of ya or anything, this is your spare time and everything :).
[Galaxy S 4 General] AndreiLux:
I have a Russian I9500XXUFNB3 stock base and I9500XXUFNA6 modem.
[Galaxy S 4 General] NEOAethyr:
Awesome, I will probably dl that and try it.

I just flashed the kernel again, clear the cache and dalvik before flashing this time instead of after.

Restarted, after updating the apps progress thing it hard locked and had a ton of screen corruption, had to pull the battery.

That's only happened once when I tried that logcat boot boot animation app.

1st time this has happened when flashing your kernel, something is goofy.

I had google search crash the previous rom flash on 4.4.2 (been switching back and forth to check the camera diffs).

So I re-flashed 4.4.2 and it seemed fine, I had thought maybe I ran the terminal to quickly right after flashing or something, but maybe something is up.

The phone is not sleeping at all, I rolled a cig and it's been sitting for around 10mins with the screen on and me not touching it.

Anyways time to test the charging thing.

Wall charger:

Phone says it's charging.

Ah synapse actually worked the 1st time around, supersu came right up, that's diff.

input 1200ma

avg 1600ma

now 999ma

With it left plugged in, shutdown, after the refresh logo looking battery thing it crashed, no light in the corner, no green battery fill image thing.

Pc (usb 2, front panel, not sure if it's tied to other grounds... lol oui):

Says it's charging (has the little lightning bolt batt icon).

Input 460ma

Avg 460ma

Now 432ma

Pc usb3 (back panel, usb 2a charging mode enabled and so on):

input 1200ma

avg 1600ma

now 999ma

Gonna try a factory reset, been a while since I did this because I don't like doing it lol.

Ok synapse didn't startup right the 1st time around, no supersu prompt.

2nd time it worked, this seems normal for me anyways, it'll work from now on.

A15 cores are definitely working, the other boots it was saying a7 on the main page of synapse...

It put it's self to sleep while I was typing on my pc here...

Powering off while plugged in the usb 2 port.

Crashed :(.

Alright :(, I'm gonna recover to my 4.4.2 backup for now, and dl the same rom you have and try that.

(I assume it's region code SER)

I'm dl'ing it right now, it's gonna take all day but that's alright :), my internet is not so fast.
[Galaxy S 4 General] AndreiLux:
If you have horizontal lines then it's caused by low voltage on the internal, other crashes probably same reason. If you confirm this then I might change some stuff.
[Galaxy S 4 General] NEOAethyr:
They were 2 big blocks of white, and some garbage in between them and such.

It's never happened before on that kernel.

I don't really don't know what happened there.

It worked fine right afterwards, and it seemed to be booting fine at the time, I turned my back for a min while it was updating, you know, you flash the kernel the 1st time it does that updating thing.

Well after that it did screen corruption.

I have a 2nd cam around but I don't know if it works anymore, I need some new AA's for it to check it, otherwise I would of took a pic of it.

I'll try it again for ya but I gotta get some batteries 1st.

:)

I just gotta make sure to clear the caches before flashing the kernel.

Normally I do that right after flashing the kernel, before restarting from recovery.

I doubt there's a difference, but who knows.

I can keep trying lol.

If you think it's worth checking out I'll doit :).

I'll have some money to get some batteries in a day or 2, I've been having probs with a fam member stealing money out of everyone's accounts :(, sounds nuts, I can't afford double A's lol...

But I'll get on it :).
[Galaxy S 4 General] skivnit:
That's too much underclocking
[Galaxy S 4 General] NEOAethyr:
I'm not underclocking though.

That was right after flashing the kernel, with no previous synapse installed.

I was trying to get the corruption to show up again and here's my notes, no luck so far but still, some oddities with the audio.

Not sure what to make of the a15 thing, it's probably not being loaded up enough, yet on some boots it consistently shows up when loaded :\.

Notes (just bare in mind they are just raw notes):

cleared cache

flashed kernel

synapse worked 1st run

batt

input 500ma

avg 0ma

now 466ma

cpu a7, max 1200mhz, a15 not kicking in

flashed kernel

a15 1200 showed up

definitely faster at loading videos

turned off power savings (not seeing the a15 anymore, didn't reboot or anything...)

Still not seeing the a15 anymore, restarting

seeing 1200mhz a15

Apparently I only see the a15 cores running right after bootup

maybe it's not being loaded up enough, or maybe they stop working, I don't know, I'm not used to checking for them.

powered off

plugged in usb

1st batt image

crash, had to pull batt

ran synapse, seen a glance of 1600mhz a15

core temps were up to 60c and quickly cooled down to 39-43c

a15 is consistently showing up now, it's switching back and forth between the a9 and a15 (I'm using the home button to switch back and forth between the home screen and synapse to check)

audio and video is not working, not sure what's going on there...

rebooting

audio is working again

a15 showed up right after boot in synapse, but now isn't showing up anymore

Ok... gonna restore my backup then flash the kernel again to see if I can't get that screen corruption like I was going for in the 1st place...

;;;;;;;;;;;;;

I just got done restoring I'll keep messing around for a bit.

Edit:

Ok apperently the temp will go up to 68c on core2 at times right after boot, must be normal.

1st boot the a15 was showing up alot, 2nd boot showed up right after boot but can't get it to show up anymore, probably normal.

I did a global reset in synapse for the heck of it.

Gonna try the usb charge one more time.

Crashed again...

Maybe that screen corruption on 1st boot was from synapse settings from the old kernel on 4.2.2?

It could of been stweaks, I would have to restore to remember lol.

What I mean is, even though I did a recovery, and never down clocked or overclocked, perhaps some conflicting settings got through.

It is possible, it's able to retain some data but all of it from a recovery.

I've seen bits and pieces of data left over before.

I think the only thing that completely wipes the internal flash is odin.

I'm betting that's what that was, because it's never happened before, and today was the 1st day I went back to 4.2.2 from 4.4.2 (done it from 4.3 before though).

I think are probably working fine, the sleep I have normally set to 15mins so.

But there's definitely something up with the charging when powered off.

And "I think" it doesn't charge while it's sleeping.

I'm at 80%, I'm check real quick before recovering and leaving it be.

Yeah it's charging in sleep, taking a bit though but it's at 81% now.

So charging isn't completely broken on my end :).
[Galaxy S 4 General] NEOAethyr:
I just installed the russian rom ser nb3, got supersu 1.9.3 installed, installed the latest philz touch recovery, then installed the perseus kernal v18.

Still crashing after shutdown when plugging the usb cable in.

I don't know what's going on, it kinda bums me out.

Anyone else have this prob or is it just me?

Edit:

I'm not sure if this will help, since it stopped logging before the crash.

adb shell su -c "cat /proc/kmsg" > c:\kmsg.log

http://www.sendspace.com/file/lfd2wl

The kernel doesn't have last_kmsg, the default one does though but that likely won't be of any help.

The log above was taken with rom 4.3, stock no apps, nothing installed, though supersu was still around for some reason.

Of course it still crashed on me lol, I figured it was worth a shot though.
[Galaxy S 4 General] m4iN_sd:
i like the phone the original karnel and custom rom makess it :good:
[Galaxy S 4 General] Cleverfish:
hi guys,

been reading through the discussion about the A15 not kicking in. i've been using about half an hour and i have "problem" that A15 is always kicking in.. well it actually when in really really heavy load (listening mp3, facebook, wechat, whatsapp, sync enabled, xda app, browsing, blah blah) but if you just playing around with the phone, it will stay in A7.

i would like to share my config:

-stock 4.4.2 (Malaysia - XME) with new KK bootloader

-latest busybox

-xposed framework with dozens of modules

-latest PhilZ touch recovery

-power saving enabled but only for LCD

[MENTION=4167023]AndreiLux[/MENTION], until now i don't had any problems. charging also is good as usual.

Sent from my GT-I9500
[Galaxy S 4 General] Cleverfish:
AndreiLux, i've experience it few hours ago..

Sent from my GT-I9500
[Galaxy S 4 General] beatsmaster0510:
Installed perseus a18 with Omega v20 and Wi-Fi Hotspot is not working. Same problem happened when I was in Omega v19. This is likely a kernel issue since the function was working using the Omega kernel.
[Galaxy S 4 General] beatsmaster0510:
Also confirming horizontal lines issue. I am currently on stock settings for CPU and GPU on a18. Such behavior appeared while reading comments on an Facebook post. Scrolling the list of comments up and down showed the horizontal lines.
[Galaxy S 4 General] JaviLerma:
+1 with Rom stock
[Galaxy S 4 General] ice.modding:
But this bug was already reported some time

ice tapatalk
[Galaxy S 4 General] beatsmaster0510:
Yeah, but still not solved.
[Galaxy S 4 General] beatsmaster0510:
Seems that andreilux is now busy with the S5 octa that update to the kernel was 7 weeks ago. Looks like it's time to upgrade to or change to other phone.
[Galaxy S 4 General] AndreiLux:
I'm not busy with the S5, stop assuming things. I've been working on synapse for the last weeks.

I've already told people if they have instabilities in the current version to raise internal and memory voltages a notch.

And frankly beyond that, I have nothing to update in the first place.
[Galaxy S 4 General] beatsmaster0510:
I honestly don't care what's eating your time but at least when we report bugs, please advise how we can fix it. I already told what changes I have made prior to the wi-fi tethering problem. Also, others confirmed the bug.

Thanks for letting us know that we're expecting a Synapse update and letting us experience your great kernel.
[Galaxy S 4 General] AndreiLux:
Am I your nanny to take care of you or what? Read the wiki. And I've posted plenty of times here.

The Wi-Fi thing is something that happens from compiling from clean source and affects other kernels too , I'm in no mood in searching the needle in the haystack that causes it.
[Galaxy S 4 General] farid993:
vibration intensity controller? :p
[Galaxy S 4 General] zetlaw:
this is really a sad day for me.

andreilux i know we cannot force to do anything but im really sad that S4 development stopped somewhere in 4.3 :(.

i really appreciate what you have done to our devices your kernel is amazing. but in the correct kitkat with V18 its just not usable.

im having WIFI tether problems, USB tether workes but the CPU always on MAX speed. L2_Hsic wakelock and A15 cores arent working.

i think i am downgrading to JB because i cant live without this amazing kernel.
[Galaxy S 4 General] dr.ngk:
I'm on stock KitKat 4.4.2 with v18 WiFi hotspot is not working....any solutions?
[Galaxy S 4 General] ice.modding:
the hotspot not working under this custom kernel.
[Galaxy S 4 General] dr.ngk:
If I move to another Kernel will I lose root?I really don't wish to but wifi hotspot is the only way I use my laptop n it is really important for me
[Galaxy S 4 General] NEOAethyr:
No you won't lose root...

You generally get root with supersu, not with the kernel lol.
[Galaxy S 4 General] JaviLerma:
New v19...

Enviado desde mi GT-I9500 mediante Tapatalk
[Galaxy S 4 General] NEOAethyr:
v19

I'm getting the same crash as before when trying to charge when powered off.

I got an error too in Synapse:

CPUFreq governor > Governor tunables

STreeDescriptor has failed:

java.lang.ClassNotFoundException:

com.af.synapse.elements.STreeDescriptor
[Galaxy S 4 General] bala_gamer:
thats sad indeed.... never expected 9500 would reach dooms day this short on the custom kernels part...
[Galaxy S 4 General] cmd512:
Working perfectly here, did you upgrade to latest Synapse?
[Galaxy S 4 General] NZnewbie:
Hi.. maybe try to delete synapse data and restart

QUOTE=NEOAethyr;52197559]v19

I'm getting the same crash as before when trying to charge when powered off.

I got an error too in Synapse:

CPUFreq governor > Governor tunables

STreeDescriptor has failed:

java.lang.ClassNotFoundException:

com.af.synapse.elements.STreeDescriptor[/QUOTE]
[Galaxy S 4 General] AndreiLux:
I forgot to update the bundled APK, will re-upload later, or just update in Play.
[Galaxy S 4 General] xdamami:
Hi guys on Omega rom working perfectly try omega rom! Thanks Andrei for good job!

GT-I9500 cihazımdan Tapatalk kullanılarak gönderildi
[Galaxy S 4 General] zetlaw:
Im on stock kitkat nc1 odexed rooted with 4.2.2 bootloader. I still have A15 problem and l2hsic wakelock.
[Galaxy S 4 General] powermax91:
It happens to me too ,because it's odexed rom, try an deodexed rom like omega and you should have a working A15 and no more l2hsic wakelock like me.
[Galaxy S 4 General] NEOAethyr:
You're lucky, All my backup's kernels crash on me when charging @ power off.

Never had this prob until I updated to v4.4.2 :(.

Sucks because I can't use any of the perseus kernels now (on 4.3 and 4.2.2 it was fine).

I liked the screen adjustments, with power saving enabled it's kinda blurry, without the custom kernel I can't fix that.

The only stock kernel that works for me now is the stock 4.4.2 one :(.

Ticks me right off, I paid over $700 for an unlocked phone so I could eventually write software for it and samsung keeps screwing us over on every update.

I got everything working, including usb mass storage mode and I'm stock with the stock kernel.

[/QUOTE]

Where are the settings stored?

I looked in /mnt/sdcard/ but I don't see anything in there related to synapse settings.

I would like to de-odex but I don't trust the binaries going around.

I would have to run them in the emulator 1st, I don't usually have terminal installed on the emu, and I most certainly don't have root on that.

I'll have to look it up, I don't really need terminal I could use adb, I'll just have to grab one of those de-odex zips, tear it apart and look at the script.

And then run it manually from adb on the emulator to check for spyware.

I check EVERYTHING before it goes on my phone, well 99% of it, the other stuff I check on my phone using Network Connections and Network Log.

Last thing I need is someone stealing my imei and such before I even use it my self (had my phone since it came out and haven't put service on it yet lol)
[Galaxy S 4 General] powermax91:
try this Universal Deodexer

http://xdaforums.com/showthread.php?t=2213235
[Galaxy S 4 General] ice.modding:
It is difficult to have this kernel on cyanogen?

ice tapatalk
[Galaxy S 4 General] nagpalkapil:
We hv a perfect working version V19 released on 25th. We also hv a new thread started by Andrei for it. I say after using kernel for two days it's pure awesomeness in terms of battery, performance and features. You and everyone may use and try it.

Please don't say Thanks but press Thanks Button if someone has helped you.

Sent from I9500 using Tapatalk pro.
[Galaxy S 4 General] ice.modding:
where is the link?

you installed a custom rom based on Cyanogenmod?