yashsingh1/xdaforums huggingface dataset:
[Galaxy S 4 i9505 Android Development] david19au:
Hah, just flashed M15 and it instantly crashed right after rebooting from recovery, after a hard reset I was able to get it booting, here are logs
[Galaxy S 4 i9505 Android Development] david19au:
More logs from crashes - running yankactive with zen 2048kb readahead and simple GPU. I'm gonna try and turn off Bluetooth and see if it helps

EDIT - Nope, it didn't, it even crashes more frequently for some reason ¯\_(ツ)_/¯ looks like I'm going back to Imperium Kernel... also what is that "mmc1: CMD52: Command timeout" thing in the logs? When I read through the logs it's spammed everywhere
[Galaxy S 4 i9505 Android Development] sonickles9:
Hmm, is it just me, or this kernel seems to have a MAJOR problem with high-load scenarios?

At least on my case, random reboots on high-load scenarios happened on *every* rom I used (I used lollirom, Thor, WizCyan 2.9 and 3.0)

and the ported ones seem to have the most difficulty

Hasn't been using machinex for a while because I thought I was getting notifications but I wasn't lol, will try today

hope it is fixed :)

Enviado de meu GT-I9505 usando Tapatalk
[Galaxy S 4 i9505 Android Development] devsnor:
For me it is actually more stable than it was before, however my radio goes to sleep all the time, and I really mean all the time, I had to toggle flight mode a few times just to be able to post this, also making phone calls is impossible, it always drops after a few secs. The only things i changed in synapse this time were hotplug (lazy, found it to be much better stability wise than alucard or msm while being a tiny bit snappier than intelli, btw my problems with reboots in antutu were mostly solved on lazyplug), OC to 1998000, and noop scheduler. These 3 tunables alone give me the score of 42k. I dont care for it much but i do use that benchmark to test stability and to check if playing with some settings has a positive effect on performance.

PS: [MENTION=6018519]sonickles9[/MENTION], is wizcyan any good? Ive been tempted to try that one for a while now but after trying kushan ultra light a while back im not so sure (I had to manually dl some system apps the dev cut out and mess with the permissions in the system folder just to get accessibility to work for tasker and greenify). Thanks.
[Galaxy S 4 i9505 Android Development] sonickles9:
WizCyan is better than Thor IMO (cause Thor has some crap I like to remove but I hate when there are broken entries on system settings, not to mention its rather sloppy way of pushing updates), and its latest update made the rom even more snappy, though I have been struggling with WizCyan+machinex. Random reboots I can't explain and some related to high load.

However if you are looking for a nice debloated stock s6 port, then WizCyan is it.

Enviado de meu GT-I9505 usando Tapatalk
[Galaxy S 4 i9505 Android Development] Andycar:
Hi there! I'm testing the 15th machinex for the whole day today and it works fine for me. No more modem disconnects. God job!

Отправлено с моего SM-A510F через Tapatalk
[Galaxy S 4 i9505 Android Development] devsnor:
How? It's a completely different story here, had to flash back to stock for today cause i needed my phone to be able to answer calls lol. I don't see how that could make the modem to behave like it does but im using smartnetwork module to automatically toggle mobile data on and off depending on display state. I doubt that could cause such severe random modem dcs though...
[Galaxy S 4 i9505 Android Development] Andycar:
Dunno, I just flashed markFifteen over the 15P2... :)) BTW, my modem is I9505XXUPPI1 (the latest), but Idoubt that matters much...
[Galaxy S 4 i9505 Android Development] sonickles9:
hm that burst a light...

hey [MENTION=4763308]robcore[/MENTION], is it possible that an outdated bootloader/modem can cause issues with the kernel?

Enviado de meu GT-I9505 usando Tapatalk
[Galaxy S 4 i9505 Android Development] robcore:
Ah sorry guys busy weekend!

There are definitely issues that can arise from mismatches in modem, BL, system and kernel. That said, besides the rare exception, updates for our device for 5.0.1 barely change. Nothing drastic at least.

If anything, I would blame the kernel code for recent modem issues, as I tested a few updates to the modem code that are being reverted for the next release. Some of them include voltage, and it's interesting that the changes fixed issues for some and caused issues for others.

As it stands, I plan to release an update soon with the most ideal modem settings we've had thus far, because it's a pretty big deal ; ) also found the last remaining panic (rr) and am working on squashing it as we speak. : )
[Galaxy S 4 i9505 Android Development] david19au:
What about looking at Imperium Kernel sources and try to figure out the problem via looking at that kernel modem settings. Since both kernel are Sammy based, it could help I think (I know nothing about kernels). Oh, there's the new PPI1 modem and bootloader, would it fix the modem issues when you *update* the initramfs to that from PPI1?
[Galaxy S 4 i9505 Android Development] robcore:
Nope the ramdisk barely changes. I've already identified the issues and am working on the fix.

As far as imperium goes, slim keeps his way closer to stock than I do (hence his stability). My project is experimental as I chose to embark on a mission to update the code for a largely undocumented SoC. Our snapdragon 600 is not like any others, except for maybe the HTC butterfly S. Even then, the best sources I've found for updated drivers have had to come from samsung, and luckily they've let a few updates ones for our device slip into sources for slightly newer devices. That's our best bet so far unless someone can find me an illegally obtained samsung qrd document for their variation of the 8064...
[Galaxy S 4 i9505 Android Development] david19au:
Well, at least I tried suggesting something :/ I still don't get why Samsung won't release all sources for our device that's already 3, soon 4 years old :p
[Galaxy S 4 i9505 Android Development] Superperry96:
It's been more than a week or 2 I've been trying your kernel and I can say pro and cons:

Pros:

-Performance and smooth is okay and better than other kernels I've tried

-Audio Volume is High here

-For now always fast for correcting bugs

-Stable overclock (for me) and undervolt (no reboot for me and I can go to all -0.75 V)

-Good battery management and adjustable battery charge.

Cons:

-Synapse boot takes few seconds to start but I can understand it because maybe it's normal when rebooted.

-For me, games are playable but crashes (tried unison league and bf rpg) when doing specific command, tried even with adjusting i/o read ahead and/or scheduler and the most stable is 128 kb which is low imo and the problem is not in uv because I tried uv and stock.

Anyway I'm still using it due to good performances and is more battery friendly than other kernels. Stability is okay for me and for normal usage it is okay, but since I'm more gaming user, well I can still play normally but sometimes it crashes...

Continue your good work.
[Galaxy S 4 i9505 Android Development] robcore:
Synapse Boot, I'm afraid, is out of my hands...it's a third party app created by a brilliant developer who has since moved on...maybe I'll make my own kernel control app one day, but kernel comes first.

As far as graphics performance goes, I'm going to release a toggle for a lesser known "feature" on our gpu that may be responsible for the slowdown. I read into it, and it turns out the kgsl driver has a "powernap" feature that has nothing to do with system suspend. It makes the gpu "rest" between frames and is marketed as a battery saving feature. That said, it slows down performance and could arguably be a battery drainer as all of this switching between "rest" and full operating speed is expensive. For now you can find the value to change here if you want to experiment:
[Galaxy S 4 i9505 Android Development] robcore:
Actually the synapse boot was a lie, I changed the uci service to early start from late start and its like 5 seconds faster now
[Galaxy S 4 i9505 Android Development] david19au:
Whoa, the 16th is much better, I haven't experienced a single rr while in ROM. Here's the catch, everytime I REBOOT, I get in loop - the bootanimation freezes and the phone reboots again and the same happens. It's fine when I poweroff the device tho. Will provide logs later. :D Also, I thought the kernel had init.d enabled but according to GovTuner it doesn't o.0
[Galaxy S 4 i9505 Android Development] robcore:
It does. Chmod your scripts to 777 and chown them to 0:2000
[Galaxy S 4 i9505 Android Development] robcore:
Also if you could, next time you loop on reboot, grab me a kmesg. It should come out of the loop on its own
[Galaxy S 4 i9505 Android Development] david19au:
Okay, now I'm getting modem problems... the mobile connection every minute or so :mad: not sure what log to provide to help you
[Galaxy S 4 i9505 Android Development] Superperry96:
Rob, is there a mode to try overclocking gpu?

When you told me where to see pwrmap of gpu, I also saw gpu available frequency so I was wondering if gpu oc is possible.
[Galaxy S 4 i9505 Android Development] robcore:
Throw me the dmesg, logcat, and last kmesg when you're having issues...hmm it could be the rom, which one are you on?
[Galaxy S 4 i9505 Android Development] robcore:
Gpu OC is a maybe in the future, I've tried it out a few times but it always gets buggy. Thing is, there are bottlenecks between it, the qdsp6 processor, and the mipi connections to the panel that would need to be sorted out. Without bandwidth adjustments, the OC does more harm than good for performance. Same with the cpu actually, which still has a bottle neck I'm researching.
[Galaxy S 4 i9505 Android Development] david19au:
I just restarted the phone, the issue is gone for now, will get the logs when I get the problems again. I'm on WizCyan 3.1 with PPI1 bootloader and modem
[Galaxy S 4 i9505 Android Development] david19au:
This isn't for the modem thing but just had a rr so I'll provide some logs for that
[Galaxy S 4 i9505 Android Development] david19au:
Logs for modems problems
[Galaxy S 4 i9505 Android Development] sonickles9:
Hey [MENTION=4763308]robcore[/MENTION], often my cpu gov tunables would end up like this:

Enviado de meu GT-I9505 usando Tapatalk
[Galaxy S 4 i9505 Android Development] robcore:
I used to get that more often too, but they shouldn't as much with uci moved to class main in the ramdisk. When that does happen, force close the app and go back in and you should see it. Doesn't happen to me anymore!
[Galaxy S 4 i9505 Android Development] robcore:
I needed to update my pm qos code (duh rob!). Been working on it all day :)
[Galaxy S 4 i9505 Android Development] Superperry96:
Reboot is a problem because it crashes at least 2 times before starting.

Attached files:
[Galaxy S 4 i9505 Android Development] david19au:
Will the update be anytime soon? I hate to ask this but I had to, since I need my phone to answer calls
[Galaxy S 4 i9505 Android Development] Andycar:
I can confirm that. Crashes 2 times instead of straight reboot, this started on 14th I think...
[Galaxy S 4 i9505 Android Development] sonickles9:
For me it happened since marktwo, but on the most recent versions this happens more often.

Enviado de meu GT-I9505 usando Tapatalk
[Galaxy S 4 i9505 Android Development] robcore:
I'm on it!
[Galaxy S 4 i9505 Android Development] parser:
3rd confirmation! I thought my phone was behaving strange since its old.
[Galaxy S 4 i9505 Android Development] robcore:
I think I've fixed it.

In every single rr/modem related log I've read (including my own), the panic happened on msm_hsic_host trying to go into pm runtime suspend. Now check out these logs:

<7>[ 835.158966] msm_hsic_host msm_hsic_host: suspend root hub
<7>[ 835.159210] msm_hsic_host msm_hsic_host: EHCI runtime idle
<7>[ 835.159240] msm_hsic_host msm_hsic_host: EHCI runtime suspend
<7>[ 835.159393] msm_hsic_host msm_hsic_host: HSIC-USB in low power mode
<7>[ 836.244995] msm_hsic_host msm_hsic_host: msm_hsic_wakeup_irq: hsic remote wakeup interrupt cnt: 158
<7>[ 836.245117] msm_hsic_host msm_hsic_host: EHCI runtime resume
<7>[ 836.245269] msm_hsic_host msm_hsic_host: HSIC-USB exited from low power mode

It's sleeping and waking up perfectly! New kernel out today.
[Galaxy S 4 i9505 Android Development] robcore:
Update will be out in 30 mins or so. Thanks for your patience, gang.
[Galaxy S 4 i9505 Android Development] Andycar:
Whoo-hoo, we're rolling! So many features, we like it!

Отправлено с моего SM-A510F через Tapatalk
[Galaxy S 4 i9505 Android Development] sonickles9:
Second here, no rr's so far

thanks robcore!

however there is something bugging me...

/data/.machinex folder is not being created by anything at all, and every time I flash an update the folder I create is deleted.

Is there something you can do about it? setting hotplug and voltages go haywire if the folder is not there lol

Enviado de meu GT-I9505 usando Tapatalk
[Galaxy S 4 i9505 Android Development] Helloziro:
thanks all

Please new features:good:
[Galaxy S 4 i9505 Android Development] parser:
Gonna try it out. But first can some 1 confirm that there are no rr and twice reboots after phone turns off.
[Galaxy S 4 i9505 Android Development] Andycar:
I can confirm that for me multiple reboots are gone. Tried it 4 times in a row to reboot. Each time goes strait to OS, as it should.

What exactly do you miss in this ROM?

Отправлено с моего SM-A510F через Tapatalk
[Galaxy S 4 i9505 Android Development] parser:
First rr camera related I presume.

Wizcyan rom I tried to take a photo with snap camera app

Aaaand random reboot.

Booted directly to OS though.
[Galaxy S 4 i9505 Android Development] sonickles9:
I got a RR recently

There were 2 kinds of rr's before: one which the system would freeze for some time and then reboot

and the other where the system would freeze for a longer time and then the screen would go crazy for a moment before rebooting

the second one is gone

but the first one just happened

it's too late to take any logs though :(

Enviado de meu GT-I9505 usando Tapatalk
[Galaxy S 4 i9505 Android Development] raff28:
thanks for the kernel.now it's works perfectly on PPI1 stock rom.
[Galaxy S 4 i9505 Android Development] robcore:
Check your telegram!
[Galaxy S 4 i9505 Android Development] robcore:
Dunno if you noticed, but boot up takes a little longer now. Basically I sacrificed a little boot time so that powersuspend and state_notifier could be set off during boot and then be turned on once boot is complete.

Unfortunately, our older style of graphics drivers use the same sequence for both boot and screen on event once the device is booted. So with the panel hooks enabled by default, system resume was getting called on boot, throwing the whole system out of wack thinking it was resuming on boot when it was actually just booting. Because my c programming skills are beginner/intermediate at best, and I haven't found a good indicator in the boot code to specify the difference to the panel hooks, this workaround is a temporary necessity. I'm hoping to figure out something in the kernel code though so the ramdisk work around becomes irrelevant!
[Galaxy S 4 i9505 Android Development] robcore:
Like what?
[Galaxy S 4 i9505 Android Development] robcore:
I'm gonna leave this here...did some ramdisk work this morning and I think everyone will benefit from it. It *might* break boot from poweroff charging. On the flip side, it might make it better. I haven't tried that yet. But yeah the new ramdisk changes overall are more efficient, and this has an extra hsic patch for safer spinlocks around threaded irq functions. So try it out if you dare!
[Galaxy S 4 i9505 Android Development] Superperry96:
I was wondering if f2fs is supported in this kernel, but I'm not very confident since I heard tw roms are not supported because it's based on linux 3.8 I think...

I want to try f2fs format one day... (end of OT)

Your kernel became a little bit more stable in terms of gaming and overall usage, so far no rr nor crash on reboot for me. I'm still wondering why 2 of my games crashes when maybe overstressed or I don't really know the reason, whatever...

I tried another kernel and my games are more stable...

Btw I'm still sticking with this kernel because it's good and smooth.
[Galaxy S 4 i9505 Android Development] robcore:
You know, Ive always been curious about f2fs format too, just never got around to it. That said, I've done some research on the subject and have decided against it for a reason other than backporting or tw compatibility. Lol half of this kernel is backported, so that's not a concern. Also, people have long since figured out how to get it working with tw. So again, no problem there.

My reason is simple. In all of the reports and throughput tests using f2fs, the difference in speed gains is miniscule since android's switch to the ART runtime. We are talking like milliseconds up to 3 seconds of difference in increase. So given the man hours it would take to implement it in the kernel, the alterations that would have to be done to the rom, and the f2fs patches needed for a custom recovery, at this juncture the benefits are simply too minor compared to the amount of work that would go into the implementation.

As far as your game crashes go, when it happens I need you to immediately get me all 3 logs from synapse (like RIGHT after) or there is nothing I can do. As the OP says, "logs or it didn't happen." ;)
[Galaxy S 4 i9505 Android Development] Superperry96:
Here are the logs (stock voltage):
[Galaxy S 4 i9505 Android Development] robcore:
The logs tell me a little.

A) Specifying in your post that you are on stock voltage, when the logs show voltage being changed, looks bad.

B) My kernel is made for roms that have the model number GT-I9505 and specifiy Android 5.0.1. You may want to check with your rom developer regarding the values in these photos.

C) Overheating happened. Intellithermal had to throttle you down to like 918000 on all four cores.

D) The updated GPU/Adreno code in the kernel actually validates the values being given to it from userspace. If there are native drivers in your rom that weren't built for this device, and if they are failing to communicate with kernel space, again it's another issue to take up with your rom developer.

E) I'm seeing a lot of permisison errors. Make sure, when using custom roms and kernels, that SuperSU is set to be as permissive as possible so you don't get knox blocked. Here are the crucial settings:

- ENABLE SU during boot

- DISABLE (untick) Mount namespaces separation

- Install SuperSU into /system

- ENABLE Trust System User

Those settings are kinda par for the course when it comes to android modding.

In the cases of your crashes, the kernel worked as was intended to. It would be irresponsible of me to use poor quality coding practices in order to try and make it compatible with the bugs in a custom rom.
[Galaxy S 4 i9505 Android Development] sonickles9:
When you mean "use poor coding practices" on that context, what would be the code and why it would be bad?

I'm just curious. :)

Enviado de meu GT-I9505 usando Tapatalk
[Galaxy S 4 i9505 Android Development] Superperry96:
I had reverted to stock voltage but it seems it really didn't work, lol such an embarassing thing.

I'll figure it out.

Thanks anyway.
[Galaxy S 4 i9505 Android Development] robcore:
Good question.

First off: quality. Remember the days of stock kernel's video glitches, audio/video sync errors, "YouTube fixes," etc? I still try to forget those days. I refuse to ever go back! The I9505 is my only device (besides a hobby skyrocket I have no time for.), and I use my kernel as my dd, so on top of wanting to provide quality to you guys, I have personal incentive to make it operate well.

Secondly: Memory Leaks. Bare metal (aka hardware, aka C) programming means my code is responsible for the allocation and de-allocation of every bit of physical memory being used by the operating system. The goal for this type of programming is tailoring the kernel code to hardware it's built for, and I can't account for shared objects that were built for a different board. Unlike Java programming, i don't have a wide array of safety nets for memory hogging programs at my disposal. There are limits to what we can do with syscalls that are attempting to do something our device can't do.

I don't want people to abandon roms or anything, but I definitely want rom issues brought to the attention of their respective developers, because I have enough on my plate with the kernel issues!
[Galaxy S 4 i9505 Android Development] Superperry96:
I didn't know you can use C programming for kernel. I'm actually learning it in university and on my spare time (when I got time I also want to learn java), so I'm still a real noob.

Btw I'm gonna try mark18 right now.
[Galaxy S 4 i9505 Android Development] robcore:
Mark18 is my baby : D

Yup the kernel is pretty much all C, though the build system is comprised of many languages.

Lol is it weird that i find Java harder than C?
[Galaxy S 4 i9505 Android Development] david19au:
Some logs from rr and modem crashes, hope this helps!
[Galaxy S 4 i9505 Android Development] robcore:
Questions:

Which rom?

Any voltage changes?

What are your synapse settings?

Any audio mods, build.prop mods, "battery saving" mods, etc?

What were you doing when happened?

Are you on MarkEighteen?
[Galaxy S 4 i9505 Android Development] david19au:
WizCyan 3.1, GT-I9505

GPU: Simple governor

CPU: intelliactive, 1.9GHz, PE Workq. enabled

I/O: int. = zen, 2048kb, ext. = fifo, 1024kb

Charging: Custom levels, 2000 on AC, 700 on USB

TCP: Westwood

A.R.I.S.E sound mod, no build.prop mods, Xposed with Greenify and Amplify

Random reboots were when I had my phone in my pocket and modem problem after switching off airplane mode.

Right now I am on M18, some of the logs were still from M17 but on M18 I face similar issues.

On M18 it takes me 2 reboots to actually use the phone, since after a reboot the phone freezes and I have to hardreboot it.
[Galaxy S 4 i9505 Android Development] Superperry96:
My curiosity on using f2fs is so bad I was wondering if I should dare to try it with my current rom and your kernel...

Edit: nevermind, soneone said me tw rom doesn't support f2fs so... lol

Anyway no rr, only straight reboot for me and no crashes so far (apart for gaming and I still don't think it's the rom's problem since on another kernel it is more stable but well I can survive with a few crash).

Edit2: I opened a q&a thread to have a clear answer but it seems no one wants or can't give an answer.
[Galaxy S 4 i9505 Android Development] david19au:
Okay, this one is really weird, yesterday I went home with my battery completely dead, so I charged my phone while it was off. (Just the battery on the screen) I just woke up, just to see, that it wasn't full, after 7 hours of charging... what the hell? This can't be right, right? (It went from 0% to 95% in 7 hours, I use the Samsung boxed charger, that has max. of 2000mA and usually with Imperium or with CM13 it took me only 2hrs max to get full charge)
[Galaxy S 4 i9505 Android Development] chiruscan:
Been running m17 all day. Impressed with how stable it is compared to its predecessors.

No rr or crashing for me on Thors7 Rom. Only thing I notice is a bit of lag coming from deep sleep. Great job Robcore.
[Galaxy S 4 i9505 Android Development] robcore:
I may have broken power off charging in the ramdisk. I'll revert the change I made on a hunch and attach it here asap.
[Galaxy S 4 i9505 Android Development] david19au:
Also, the poweroff charging doesnt seem to dim the screen sometimes.. I had to reboot a few times to get it to dim the screen
[Galaxy S 4 i9505 Android Development] Andycar:
For me there were no problem with offline charging on M18. Check these two photos- the time difference between them were like 20 or 25 minutes only.

[]

So you can see that in my case charge reaches 100% correctly.

P. S. I'm on that near stock PPI1 RON, debloated.

Отправлено с моего SM-A510F через Tapatalk
[Galaxy S 4 i9505 Android Development] raff28:
on mark17 my modem sometimes dc.switch back to stock kernel.did try yet the mark18.