yashsingh1/xdaforums huggingface dataset:
[Galaxy S 4 i9505 Android Development] chiruscan:
Robcore thanks for continuing work on this impressive kernel. One question: is there anyway to get HBM to stick after the screen turns off?
[Galaxy S 4 i9505 Android Development] robcore:
That sucks. I'd love to fix it, but without logs taken immediately after the crash I can't.
[Galaxy S 4 i9505 Android Development] robcore:
That is a damn good question....Now you have me wondering the same ;) let's see what kind of hack I can think of eh?
[Galaxy S 4 i9505 Android Development] chiruscan:
Is it possible a simple build.prop edit can make the HBM by default?
[Galaxy S 4 i9505 Android Development] robcore:
Haha I wish my friend! Hbm is only actually consistently working because I hacked the driver. BUT I'm considering an even cooler way to implement it that will include re-enabling it upon resume thanks to you. It will be based on the newer devices that actually have an hbm_mode sysfs option and I don't know why I didn't think of this before.
[Galaxy S 4 i9505 Android Development] kekate:
I use the performance profile with some of my tweaked settings and after reset, the changes I've done to that profile revert to the default performance profile. why is that? every restart need to apply my tweaks again
[Galaxy S 4 i9505 Android Development] darkrevlis:
[MENTION=4763308]robcore[/MENTION], any advance about kgsl/gpu?
[Galaxy S 4 i9505 Android Development] chiruscan:
Perhaps theres a way to tie it in with the auto brightness setting?
[Galaxy S 4 i9505 Android Development] robcore:
What you need to do is save your changes in your own profile (second last tab), then change the "preset" back to "none" on the first page. Then reboot. Once you reboot, you can load your custom profile you saved and it will stick.
[Galaxy S 4 i9505 Android Development] robcore:
A few advances, especially on the upcoming version!
[Galaxy S 4 i9505 Android Development] robcore:
It actually already is, that's how qcom/Sammy implemented it on these legacy boards. The command for hbm is just echoing "6" to the auto brightness sysfs interface. I actually may have found the reason it isn't restored up on screen off/on events so this may be easier than I thought.

EDIT:

Nevermind all that, turns out I actually DID fix it last night whilst trying to ensure that the mode is preserved on sleep/wakeup. So yeah..it's fixed! I just forgot I'd fixed it! :)
[Galaxy S 4 i9505 Android Development] chiruscan:
Its still not sticking for me after a screen off event on Mark 82 on ThorS7. The box remains ticked but the screen dims on turning on again.
[Galaxy S 4 i9505 Android Development] robcore:
Make sure to disable the cabl prop in your build prop. Also check your pm's man!
[Galaxy S 4 i9505 Android Development] chiruscan:
qualcomm.cabl=0?
[Galaxy S 4 i9505 Android Development] robcore:
Yep, though I set it at boot anyway...strange this is. You're not using it with auto brightness are you? That wont work.

Edit:oh also, if you use the "screen dimming" fix in synapse, that gets rid of Samsung's deprecated screen dimming "feature." I have a button there to restore back to stock as well!
[Galaxy S 4 i9505 Android Development] chiruscan:
Just changed it, still not working for me. Also in settings it shows my kernel as Mark81 even though Synapse says Mark82
[Galaxy S 4 i9505 Android Development] robcore:
That won't happen again, I've made it dynamically linked to my zip script since. We will see for Mark83, all I know is it works for me...strange
[Galaxy S 4 i9505 Android Development] xell75:
I made qualcomm.cabl=0 rebooted but it's not sticking for me too [MENTION=4763308]robcore[/MENTION]
[Galaxy S 4 i9505 Android Development] robcore:
It's in the works:)
[Galaxy S 4 i9505 Android Development] xell75:
You're the best! ??
[Galaxy S 4 i9505 Android Development] mikussj3:
hi. l've random reboots with mark83(stock setings). my rom WizzCyan3.3

not sure if its kernel problem but my wifi reconect time to time
[Galaxy S 4 i9505 Android Development] mart123:
Hi robcore! Is the hs200 working?
[Galaxy S 4 i9505 Android Development] robcore:
What is the hs200?

Edit: do you mean mmc and external sd? Because yup it's working.
[Galaxy S 4 i9505 Android Development] kekate:
I like the phrases you put on Synapse after every release :)
[Galaxy S 4 i9505 Android Development] robcore:
Thanks :) It's a fun way to keep the creative spark alive!
[Galaxy S 4 i9505 Android Development] kekate:
I'm not sure if I need to provide logs as no crash happened but on the latest version there is some issue. Apps and everything, whole phone starts to stutter and lag very weirdly. I suspected temps, so the kernel underclocks or even shuts down cores but no. Temps are 54c for CPU. I flashed back to Mark 83. anyone else experiencing it?
[Galaxy S 4 i9505 Android Development] fatal05boy:
How is this kernel on Super Wizcyan 3.3? thank you :)

the last post about super wizcyan getting lags is related on the screenshot on 1st posts. "Default settings my not be stable and reasons for random reboots" change some values you know dude even slight changes.
[Galaxy S 4 i9505 Android Development] Hez13:
Thanks for your hardwork [MENTION=4763308]robcore[/MENTION] Mark84 has no problems for me. Im on stock HPA1 rom btw.
[Galaxy S 4 i9505 Android Development] kekate:
mark 85 fixed the stuttering for me
[Galaxy S 4 i9505 Android Development] kekate:
running very good
[Galaxy S 4 i9505 Android Development] mart123:
Running very good but sometimes the phone reboots or stays black and have to remove batery. Logs after a reboot.
[Galaxy S 4 i9505 Android Development] robcore:
Anyone wanna help me rewrite a sound driver? We can't have full 3.9 workqueues backported until I do.

Edit: nevermind, our device's source is so messed up that it's easier to pull in 3.15 workqueues than update the bloody sound driver/slimbus.
[Galaxy S 4 i9505 Android Development] Helloziro:
- Kexec HardBoot support (dual

boot)
[Galaxy S 4 i9505 Android Development] Helloziro:
Tweaked sound drivers in 5.0?
[Galaxy S 4 i9505 Android Development] robcore:
I think you meant to post this one in Imperium ;) as for kexec hardboot, I've had it (and have been updating it) since MarkOne, my friend.
[Galaxy S 4 i9505 Android Development] Helloziro:
thanks you ('-') ('-') Themes Material Design
[Galaxy S 4 i9505 Android Development] dimuthu7:
hi dev great work and can you add ums(usb mass storage mod)

if it can it will be grateful for me .thanks for your work
[Galaxy S 4 i9505 Android Development] benmater:
thinks .this good ..

---------- Post added at 06:16 AM ---------- Previous post was at 06:11 AM ----------

does it work on your s4 gt-i9515 lollipop 5.0.1
[Galaxy S 4 i9505 Android Development] Belgas14:
Machinex 90 will have huge updates!
[Galaxy S 4 i9505 Android Development] mikussj3:
Battery problem - Mark91, interactive, wizzcyan v4.0

Hello. I have a battery drain. The reason may be the CPU clock management. I include bbs screenshot.
[Galaxy S 4 i9505 Android Development] anhminhon:
I installed Mark.90 last night and have a lot of problem, random reboot, battery drain although i choose save battery profile, ui very lag if i set thermal about 60°C in hot.plug max cpu heat, although at moment my device only about 40°C. About Synapse, i think it very trouble because it have too many feature not needed. If replace it with Stweak will make everything is simple than more. If someone say this kernel is stable, i don't think so yet! :)
[Galaxy S 4 i9505 Android Development] robcore:
If you don't provide logs, I can't fix anything you report.

If you're not on the latest version (mark91), your reports are irrelevant.

Regarding synapse vs stweaks, they both use a similar backend and have nothing to do with any issues you've mentioned.

Mark92 has updates and fixes for everything you've mentioned, but the settings you use will always be the deciding factor on performance and stability.

Please do not post regarding issues if you don't include crash logs. Read the op again.
[Galaxy S 4 i9505 Android Development] anhminhon:
Ok man, thank for your work. I will try v91 later.
[Galaxy S 4 i9505 Android Development] robcore:
I will be releasing 92 today anyway, might as well wait for it.
[Galaxy S 4 i9505 Android Development] anhminhon:
I hope you will add some cpu governor like imperimum or optimized the Synapse :laugh:
[Galaxy S 4 i9505 Android Development] robcore:
Are you kidding me? There are tons of cpu govs. And I have done my best to ensure the synapse backend is consistent. What "optimisations" are you looking for?
[Galaxy S 4 i9505 Android Development] anhminhon:
No! man, i don't kidding you, simple is i can't see some govs i usually to use like Intellim, Yank. :o don't argry
[Galaxy S 4 i9505 Android Development] robcore:
Yankactive and yankdemand both present. There are 28 govs in total. Intelimm was removed due to older code, a memory leak dorimanx discovered, and because really any governor's tunables can be configured to do the same thing.
[Galaxy S 4 i9505 Android Development] Razvan:
Thread cleaned.

Treat all members with the same respect you expect for yourself.

Rudeness, flaming, and lack of respect can lead to infraction.

Regards,

Razvan

Forum Moderator
[Galaxy S 4 i9505 Android Development] AleksandarRadivojevic:
Lineage 14.1

Will it work on nougat? Gt-i 9505 on lineage 14.1...cant find any other kernel that would work..
[Galaxy S 4 i9505 Android Development] Andycar:
It's fit for Touchwiz only, dude. Look at the thread title. It says: [TW]

Отправлено с моего SM-G930F через Tapatalk
[Galaxy S 4 i9505 Android Development] ferdossi:
Hi,

I have a I9505X (live demo unit) with Kushan ROM TW 5.0.1 installed, I had a drain battery issue with msm_hsic_host wakelock. I was very enthusiastic trying this Kernel from what I read in posts.

So the cleaning script and installation went well with TWRP 3.0.2. But after about 10mn, I see that not only the msm_hsic_host is not solved, but also have a huge battery drain with the Kenel (Android OS) seen with GSAM.

Can you tell why?
[Galaxy S 4 i9505 Android Development] robcore:
When it comes to the hsic wakelock, it is a relatively normal occurrence given that the hsic interface is a link between the majority of connection-related peripherals on the board. What I have been able to with it is ensure it works properly, and I've found that the best way to limit its prevalence is to minimize the amount of radio-centric services running in the background if they aren't being used. For instance: gps, mobile data, bluetooth, nfc, wifi, all of these things use the hsic connection to transmit and receive info. On my set up, I have Wi-Fi set to sleep in advanced settings, and I don't keep anything that I'm not using on unnecessarily.

For the gservices wakelocks, I've been implementing a common "fix" (which is really just pm disabling certain battery draining gservices background services) in the init sequence, but based on recent reports will probably just include it as a synapse add-on going forward. I think Google services may have changed recently and the fix may not be as necessary as it used to be.

As for battery drain, I think you'll find the next release a healthy reprieve from the issues described as I have FINALLY managed to do the RCU bringup required to make some major advances in our scheduling core. So far I am able to get pretty amazing battery life on the rest versions I'm running, and am confident my users will have a similar experience. That said, remember that the more network/connection services that stay on, the less battery life you will have. All of the kernel updates in the world will do nothing if you have peripherals constantly searching for a connection that isn't there, or connected but unused by the user.
[Galaxy S 4 i9505 Android Development] ferdossi:
Thx for your response. The battery result I gave are based on a complete disabling of any kind of network/radio/3G/WIFI/NFC/GPS....
[Galaxy S 4 i9505 Android Development] juandiazmora:
Really nice work, much optimizations, I used it on SuperTouchWiz v3 with good performance, but I have an issue with the swap process "kwapsd0" using 100% of one CPU core with overheating too.. Any suggestion?

Thanks!
[Galaxy S 4 i9505 Android Development] robcore:
Mark93 will be awesome for heat mitigation. As for the kswapd issue, thanks for the tip! I'm gonna have a look into that immediately actually. You can try lowering "swappiness" in synapse to a better value like 60 in the meantime!
[Galaxy S 4 i9505 Android Development] juandiazmora:
Thanks for the fast reply. That would be nice, I really liked this kernel. I tried lowering that value to 60, even to 0 with the same result, it persist using 100% of one core keeping it at 1890MHz all the time, but it suspends with no wakelock. Even if I let it for one hour working follows doing the same...
[Galaxy S 4 i9505 Android Development] Gamer-king:
First of all I want to say thank you from the bottom of my heart that you keep on the development for such an old device. I am currently running Imperium Rom v17 with Imperiumkernel V5.1 but I am really looking forward to test this kernel. Should I falsh and test Mark92 or is there already Mark93 in sight? Don't get me wrong I am not asking for ETA, but for me it dosen't make sense to flash and test Mark92 when Mark93 will be released lets say in a few days or a week or so. If Mark93 will take more time I will happyly test Mark92 and give as much constructive feedback as possible.
[Galaxy S 4 i9505 Android Development] robcore:
Thanks mate!

Tbh a timeline for 93 is unknown as I'm in the midst of a HUGE scheduling api update that is proving as challenging as ever. That said, it will be a masterpiece once complete. Umm my advice would be to hold off, as any feedback on 92 is irrelevant by now because so much has been changed/fixed since then and I am more than aware of its issues :)
[Galaxy S 4 i9505 Android Development] Gamer-king:
Thanks for the fast reply. So I will stick with my current setup even though reading this makes me even more curious about Mark93 but don't hurry take your time. If you might need another tester I am willing to help. I have already been a tester for Tkkg1994 the developer of the Hulk kernel.
[Galaxy S 4 i9505 Android Development] Helloziro:
best kernel thank you so much robcore!
[Galaxy S 4 i9505 Android Development] n3m35152:
Would this kernel work on S4 I9506 (LTE)?
[Galaxy S 4 i9505 Android Development] robcore:
Nope i9505/i337m only officially supported
[Galaxy S 4 i9505 Android Development] Helloziro:
- CPU overclock to 2.3GHZ

- GPU overclock to 700MHZ
[Galaxy S 4 i9505 Android Development] robcore:
Dude, I appreciate your enthousiasm for the kernel, but OC has been tried and failed by every kernel developer for this device. It hasn't worked ever due to the drastic variance in device models, and the lack of cooling for mobile devices. Also, 700 mhz for our gpu would never happen. It wouldn't even boot.
[Galaxy S 4 i9505 Android Development] 4shared:
[MENTION=4763308]robcore[/MENTION]

Thank you for the hack above the hall sensor broblem.

Can you create a version of your Machinex kernel with the hack integrated, for me.

To generate sviewcover door close event, you can simply put a small magnet as the photo show

Thank you again, and sorry i m asking too much :silly:
[Galaxy S 4 i9505 Android Development] robcore:
No worries, this one actually coincides with something I've been working on anyway (I ported the galaxy s7 gpio keys driver in order to fix home button wakeup events for my backported power framework). Quick question, does the bypass need to report flip "open" or "closed" in order to solve your problem? I have it ready to go here, just want to make sure it accomplishes what's needed.
[Galaxy S 4 i9505 Android Development] 4shared:
I'm not sure either,

but following the discussion in this thread:

https://xdaforums.com/showthread.php?t=2410452

The value must be "OPEN"

but i'm not too sure

there is no hall_detect file in the cm13 rom that i'm using now
[Galaxy S 4 i9505 Android Development] robcore:
That's my guess too, I think leaving it as "open" is the correct way to go. Like I said, I don't use the flip cover (though your solution for simulating looks interesting and I might give it a shot!), but in the absence of a flip cover mine just reports "open" when the screen is on and I look at the sysfs value reported. Before my final release of Mark93, I'm gonna remove a couple of the hooks in the gpio_key driver that I think are over kill (it should still register the interrupt, just not have any input or wakeup events triggered by it). I think I went too far with it and am now going over the logic in my head, and now I'm thinking out loud!

But yeah...coming soon for you to test.
[Galaxy S 4 i9505 Android Development] 4shared:
Keep up the good work

Waiting to test.

Greets,
[Galaxy S 4 i9505 Android Development] Belgas14:
guys, 93 is amazing!!!
[Galaxy S 4 i9505 Android Development] 4shared:
Thank you [MENTION=4763308]robcore[/MENTION] for the new update Mark93.

My problem with the hall sensor still persist.

The Sview big clock is gone but the screen still black.

So there is something else other than the hall_detect key taking effect ...
[Galaxy S 4 i9505 Android Development] robcore:
I think that the something else involves /sys/class/sec/sec_touchkey/flip_mode I will do some more digging
[Galaxy S 4 i9505 Android Development] robcore:
I think I've got it!
[Galaxy S 4 i9505 Android Development] 4shared:
Good luck,

this feature will be a great addition in the kernel

Of course it will resolve my problem :)

And from my searching about it, a lot of people asking to disable the S View for other reasons such using a magnetic car holder, working near a magnetic field and so on ...

thanks,
[Galaxy S 4 i9505 Android Development] robcore:
Try out the new one for me? :)
[Galaxy S 4 i9505 Android Development] 4shared:
As Mark93, the screen still black with battery status bar :rolleyes:.
[Galaxy S 4 i9505 Android Development] robcore:
Before I try out my next idea, would you be open to trying the bypass alongside the shell command I gave you before? echo 0 > /sys/devices/virtual/input/input11/enabled
[Galaxy S 4 i9505 Android Development] 4shared:
I can only do that via Recovery, because when i boot to system i do not have a usb debugging authorizations.
[Galaxy S 4 i9505 Android Development] robcore:
That is strange, you should be able to if you enable adb debugging in developer settings...I have a special patched adb binary in sbin that allows full, insecure adb access. Either way I'll quickly make an init.d script for you to flash to see if it works for you.
[Galaxy S 4 i9505 Android Development] robcore:
Actually I'm pretty busy today, you can do it in a terminal emulator too
[Galaxy S 4 i9505 Android Development] 4shared:
I can't acces to developer settings, in fact in can't access to anything because my phone locked in s view mod

can i do that by recovery? by flashing something?

I still wonder how [MENTION=6283150]timhovius[/MENTION] manage to disable the sensor in his builts.

I contacted him, and he built a cm14 also without sensor for me,

He is ready to explain how to build without Hall sensor,

but i am not familiar with building android myself.

I wonder if this trick will be useful for the stock roms?

I will give it a try later, I'm in school now

Thank you very much.
[Galaxy S 4 i9505 Android Development] robcore:
Building without the sensor isn't a problem, its just changing a config setting. Thing is, I don't have the time to maintain more than one kernel version, so my goal is to be able to disable/enable it at runtime. That said, it sounds like removing a screw where your sensor is might help, as apparently they can get magnetized and wreak havoc on the sensor (as yours is). I will keep searching. How were you able to access synapse to turn on the bypass?
[Galaxy S 4 i9505 Android Development] 4shared:
I removed the screw but not helping, I even opened my phone searching the hall sensor in the motherboard but sadly it's a part of the screen.

Isn't the bypass active by default? Or I have to turn it on?, as you know i have no access to my phone when it boot to the system, I have to do it by recovery.
[Galaxy S 4 i9505 Android Development] robcore:
Ohhh no it's not active by default I'm afraid. Yours is definitely a special case that I would like to help with, but by default I need to keep flip enabled for my other users...hmmm we will figure this one out don't worry
[Galaxy S 4 i9505 Android Development] robcore:
Here, try out this init d script, it enables the bypass and disables the magnetic sensor, let's see if this works.
[Galaxy S 4 i9505 Android Development] 4shared:
still the same, black scr with battery state,

the good news is that with your kernel i have now the usb adb access ,

i sent the 2 init lignes via terminal but still blocked .
[Galaxy S 4 i9505 Android Development] angarato_surion:
Your kernel for some reason raised my cpu temperature at 60c and kept it there

And it was between 97 and 98% charge for hours
[Galaxy S 4 i9505 Android Development] robcore:
Lower the temperature thresholds in synapse, as for charging, sounds like a charger problem. I get 100 % charge every time
[Galaxy S 4 i9505 Android Development] angarato_surion:
It was just recreating the dalvik cache
[Galaxy S 4 i9505 Android Development] angarato_surion:
Alo it rebooted while iwas using SDmaid to clean cache .. for some reason ..
[Galaxy S 4 i9505 Android Development] robcore:
That's the perfect log thanks man. I was using an experimental scheduling option that isn't panning out, so next build will fix it.
[Galaxy S 4 i9505 Android Development] robcore:
Hey I have an idea for you, which rom are you using? I looked around some of my spare decompiled system files yesterday and found a simple boolean(true/false) variable in framework-res that might solve your issues.
[Galaxy S 4 i9505 Android Development] 4shared:
I use SuperTouchWiz v5 for testing ur kernel.

for daily use: a miui 8 with hall sensor disabled, i manage to port the cm kernel for it from timhovius built :D
[Galaxy S 4 i9505 Android Development] robcore:
Nice! K in gonna try my hand at a little framework hacking for you, if it works, I will give you the details on the change so you can do it yourself for whichever Rom you use (except for machinex as it is odexed). Which gives me an idea of just making an overlay...hmm...
[Galaxy S 4 i9505 Android Development] 4shared:
Thank you,

I tried before to decompile those framework files, but i didn't know what change that I should make, as there are many files relative to s view:

framework-res.apk

framework.jar

services.jar

systemui.apk

.
[Galaxy S 4 i9505 Android Development] robcore:
My policy on trial-and-error hacking is try the simple changes first, in case they work ;) in this instance, the sview bool in framework-res
[Galaxy S 4 i9505 Android Development] robcore:
Okay so this will replace your framework-res and SystemUI apks. You may want to make backups of your current ones, but my guess is that you do fresh installs anyway given that this is simply a test for you anyway. Either way, I'd be remiss to not encourage you to backup the two files.

Anyhow, here goes test one!

https://www.androidfilehost.com/?fid=529152257862724552
[Galaxy S 4 i9505 Android Development] 4shared:
I did a fresh install, flashed the test1, phone still sview locked.
[Galaxy S 4 i9505 Android Development] robcore:
Oky doke, on to the next idea I guess...hey if you are able to, could you grab me a dmesg and logcat the next time you boot it up in tw? adb shell dmesg > /sdcard/dmesg.txt and then same thing but with logcat instead of dmesg. Logcat is continuous so you may want to hit ctrl+c after 10-20 seconds
[Galaxy S 4 i9505 Android Development] 4shared:
Here is the log files
[Galaxy S 4 i9505 Android Development] robcore:
Thanks, yup that mod was a dud, it seems that some sview options are deeply linked with Wi-Fi/modem connectivity. But your logs have helped me find the method being called regarding the cover at least. So I'll hunt some more
[Galaxy S 4 i9505 Android Development] Leone/kyleproxx:
Will ROM get updated
[Galaxy S 4 i9505 Android Development] angarato_surion:
more crashes when I run sd maid in latest version..