yashsingh1/xdaforums huggingface dataset:
[Galaxy S 4 Mini Android Development] kamikaze702k:
Yes bro videos were playing, it's a bit laggy this double kernel, I've calibrated, will see how the cycles go on, it's weirdly affected my volume panel too, volume goes up and down but the slider doesn't move, previously had none of these symptoms, same theme, same apps, same kernel settings, very weird bro, I've rebooted several times too, it's all small minor things, I feel as if the system is struggling hard to process things therefore some lags do occur, previously everything was flawless...
[Galaxy S 4 Mini Android Development] kamikaze702k:
Update: Instagram videos now working, I flashed an older kernel and same thing was happening then I checked xposed and it was due to an xposed module called Ad block Reborn, put Instagram into whitelist and voila!

Everything now working.

Thanks bro!!
[Galaxy S 4 Mini Android Development] csendre:
I hate Xposed, wish they never make it work on Nougat. You know how many similar comments I saw over time when people were blaming things on ROM and kernel while in reality xposed was screwing things up? I never understood why people use it.
[Galaxy S 4 Mini Android Development] kamikaze702k:
I understand bro but it's all about diagnostics and trying out, I didn't realize the module updated just before I flashed kernel.
[Galaxy S 4 Mini Android Development] kamikaze702k:
[MENTION=5416372]csendre[/MENTION] do you have PayPal? I want to give you a donation for all your hard work buddy.
[Galaxy S 4 Mini Android Development] csendre:
Thanks, but this is not why I am doing this. Lets not make it dirty with financials :laugh:
[Galaxy S 4 Mini Android Development] kamikaze702k:
I know buddy just wanted a way to show my appreciation for your work.
[Galaxy S 4 Mini Android Development] basti_b24:
Question: for I don't know which reason I can not get TWRP to work wile being able to root the phone.

CWM works fine and I'm on AICP 11 Marshmallow

Has anyone flashed the Kernel successfully with CWM?
[Galaxy S 4 Mini Android Development] csendre:
What do you mean by not being able to make TWRP to work?

Kernel should flash just fine with CWM but it is a very old recovery with no further support so TWRP is recommended
[Galaxy S 4 Mini Android Development] basti_b24:
I can make it work, that's no problem, but none of the mentioned root methods work. But never mind, I will try it :good: I thought there was some other reason that requires TWRP
[Galaxy S 4 Mini Android Development] csendre:
Root has nothing to do with TWRP or CWM. You have to enable Developer Options in settings then go in and enable root. That is a ROM feature.
[Galaxy S 4 Mini Android Development] kamikaze702k:
So I fully charged, calibrated battery rebooted now my phone won't boot, just infinite boot logo, tried wiping cache n dalvik, even a dirty flash of ROM without kernel, still nothing... Dam!! Don't really want to do a clean install or factory reset only because I didn't make any recent backups, any suggestions? Have no idea what the bleep happened!
[Galaxy S 4 Mini Android Development] Ulises31:
Perhaps you already did it, but I suffered from the same problem when I updated to Remix-kernel-CM14-v.8-LTE-20170209 version. Fortunately I got a nandroid backup before flashing and recovered my data. After that I repeated the operation, flashing v8 and same result, bootloop forever; then I removed the battery, pluged it again and a while after switching the phone on the ROM started ok. Now I have this kernel.
[Galaxy S 4 Mini Android Development] kamikaze702k:
F knows what happened, I've managed to get it past boot logo by flashing the boot.img of my ROM via twrp, now it's loading up apps, dam few hours of a nightmare, I think it was because of the calibration app not the kernel, will just get it booted up n just stick to normal kernel as I'm still risking things because I'm still on lollipop, once I jump to M/N I'll be back here more actively.
[Galaxy S 4 Mini Android Development] Mountains788:
So I have to say that I've been with the 5100 mAh kernel for three days now and there haven't been any fluctuations of any kind in the battery graph with moderate to heavy use. I'm really thankful for the modded kernel and wish that you guys keep on developing for this device and update these kernels. Keep up the good work! :highfive:
[Galaxy S 4 Mini Android Development] o0chtm0o:
He is a rich man... Doesn't need that dirty money.

I do need it https://goo.gl/G2X8id

:o :o :o :o :o :o :o :p :p :p :p :p
[Galaxy S 4 Mini Android Development] csendre:
You can take over any time, I will be happy to hand it over.
[Galaxy S 4 Mini Android Development] kamikaze702k:
Did you get any instances of the battery going to zero and shutting down then once you power off still having more battery left over?
[Galaxy S 4 Mini Android Development] csendre:
That would happen when the battery capacity is actually lower then what the kernel is configured for. You may not have an actual 5,100 MAh battery. Same happens with standard batteries as they age and their capacity drops, then people complain that they go from 30% to zero almost instantly
[Galaxy S 4 Mini Android Development] Mountains788:
This would happen with the regular, CM or Remix kernels. Don't know about 0 percent as I don't let the battery go under 10 percent most of the time. But if I were to restart or power off when I have a low charge (say less than 25%), I would have 70 % percent charge after boot. This is with the unmodded kernels for this battery. With the modded one, I have no such thing and the battery is depleted in one discharge and no reboots or power offs in between(currently on second discharge with this kernel). I'll try to fully drain it and will write back and post screenshots but I have not calibrated the battery or done anything besides flashing the kernel and doing a full charge. Try and discharge your battery to 10 - 20 percent and then leave it to charge for a night to see if there's a difference. Also, my battery is 1 month old if it makes a difference.

Edit: 2 months.
[Galaxy S 4 Mini Android Development] kamikaze702k:
Nice, that'd be great if you could get done screenshots, I made a backup and I'm trying the kernel again, previously a battery calibration app f'd me up, had to do a full clean install again, what battery calibration app did you use?
[Galaxy S 4 Mini Android Development] Mountains788:
I didn't calibrate the battery at all after flashing the kernel nor previously before that. My install is not a dirty flash or anything (except for Gapps which I update)and it's the newest one from arco's thread (20170211 version).
[Galaxy S 4 Mini Android Development] csendre:
Quick note to the self builders. Commits I have added to my remix-3 branch on github after v.8 are not upstream merges but my own picks from other (similar) kernel sources on LOS github. so you may want to leave them out from your builds.
[Galaxy S 4 Mini Android Development] Mountains788:
Just to let you know, the battery does drain all the way to zero percent. I left the phone turned off for some time after it shut down just to be sure and when I powered it on there wasn't any charge and had to plug in a charger for it to work. So you can be sure that it works though I didn't get screenshots. The battery lasted for three days.
[Galaxy S 4 Mini Android Development] kamikaze702k:
I still get the same issue. Battery claims to be dead but power on and it's more than half way then it "dies" again and again I'll power on and still some left...

View attachment 4056930
[Galaxy S 4 Mini Android Development] Mountains788:
I've attached some screenshots for you to see but the sudden drops in capacity like the ones in your screenshot (100-->0-->60-->0-->40-45) only happened with the stock CM kernel and Remix kernel ONLY in the EXACT same way. I have only dirty flashed the modded kernel over the unmodded one and did nothing more for it to work. Check your About Phone menu and compare it to this one - http://imgur.com/a/RsCCc. The discharge from the screenshots is full and I don't have to power off or anything. I'm speaking about CM14 so if you're using CM13 I can't say anything for certain as I have not used the kernel with CM13.
[Galaxy S 4 Mini Android Development] BlueBear23:
Compile Error ( Please Help )!!!

Hi guys, i am working on a modified kernel version, for kali NetHunter ( ROM overlay for ethical hacking ).

I'm originally started the development of that with the f4k kernel source, because some problems with the compile process, i'm leave this source and started the work with the remix kernel ( so good kernel bros ).

To the time of compile, start sucefull, a bit time later, send me the following erro and stop

CC arch/arm/mach-msm/perf_trace_counters.o
In file included from arch/arm/mach-msm/perf_trace_counters.h:163:0,
from arch/arm/mach-msm/perf_trace_counters.c:16:
include/trace/define_trace.h:79:43: fatal error: ./perf_trace_counters.h: No such file or directory
compilation terminated.
scripts/Makefile.build:307: fallo en las instrucciones para el objetivo 'arch/arm/mach-msm/perf_trace_counters.o'
make[1]: *** [arch/arm/mach-msm/perf_trace_counters.o] Error 1
Makefile:942: fallo en las instrucciones para el objetivo 'arch/arm/mach-msm'
make: *** [arch/arm/mach-msm] Error 2

I tried it with the msm8930_serrano_defconfig (the defect config for my device, but the result is the same error).

What if the cause of this?, its the toolchain?

Please response me :)

BlueBear23

Device: Samsung S4 Mini Serranoltexx GT-I9195

OS: LineAgeOS 14.1 [UNOFFICIAL]

Kernel: Remix kernel CM 14 V.8 serranoltexx
[Galaxy S 4 Mini Android Development] csendre:
It is coming from an incorrect interpretation of a link, strangely it does not affect inline builds. There are a couple of different ways to fix it, one would be to correct the link, but then it will keep getting overwritten when you sync your sources. In my opinion the simplest way is to just copy perf_trace_counters.h from where it is (arch/arm/mach-msm) to where the build process is looking for it: /include/trace

What modifications are you making? Anything worth to be included in remix? Please share
[Galaxy S 4 Mini Android Development] BlueBear23:
New error and response to your question

Hi csendre, thanks for view my coment, responsing to your question, i am making the modifications of the modifying kernel NetHunter GitHub Page ( i can't put the link but i'm a new user and no can't put url's on any place after me post 10 entries :rolleyes:). Search modifying kernel NetHunter on google and they might appear it.

Your solution works, the compilation process continue within errors... At least, by the moment.

A new error has arrived, now , is this:

[drivers/bluetooth/btusb.c: In function '__check_ignore_dga':
drivers/bluetooth/btusb.c:1283:1: warning: return from incompatible pointer type [enabled by default]
error, forbidden warning: btusb.c:1283
scripts/Makefile.build:307: fallo en las instrucciones para el objetivo 'drivers/bluetooth/btusb.o'
make[2]: *** [drivers/bluetooth/btusb.o] Error 1
scripts/Makefile.build:443: fallo en las instrucciones para el objetivo 'drivers/bluetooth'
make[1]: *** [drivers/bluetooth] Error 2
Makefile:942: fallo en las instrucciones para el objetivo 'drivers'
make: *** [drivers] Error 2
/CODE]

Sorry for the bad sintaxys of the code, but, i use a kali virtual machine, and the windows system not read correctly the .txt file.

Thanks for your help csendre, and i'm so excited of this kernel development, if al it's ok (assuming you response me), the first version of the kernel should be ready tomorrow ( if you response me, obviously ). And the first BETA build of NetHunter for S4 mini (serranoltexx) they be ready on 1 or 2 weeks (i'm need time to study the build system of NetHunter).

Thanks for your help to this Junior developer (literally JUNIOR, 13 years XD).:good::good:

Thanks, and i see you later.

A Junior developer, BlueBear23.
[Galaxy S 4 Mini Android Development] csendre:
[MENTION=8090060]BlueBear23[/MENTION] This one you have to troubleshoot yourself, the problem is in the kernel source.

The error message tells you where it is, it is in drivers/bluetooth/btusb.c: in line 1283 Check what that line is, or look at the modification you made that changed this file.

I am not really a developer so can't really help you with it
[Galaxy S 4 Mini Android Development] BlueBear23:
Ok, i have an idea, i can download this file of the kernel GitHub repository, and copy on the carpet.

The kernel sources isn't modified, rigth, i only need download this and copy on the rigth carpet.

Thanks for the previously solution.

A junior developer.

BlueBear23
[Galaxy S 4 Mini Android Development] csendre:
I uploaded a new set of 14.1 kernels, two commits were merged from upstream.

---------- Post added at 12:02 PM ---------- Previous post was at 11:32 AM ----------

I have been working on a project for myself and looked at many different current Lineage kernel sources to see what commits they are adding that we don't have. As a result I ended up with a developmental branch which is ~81 commits (and counting) ahead of regular Remix branch: Remix-3-Dev

As I said before, I am not a developer and would lie to say I have full understanding of everything I added, but they made sense when reading the commit message and/or seeing that multiple kernel sources adopted them. The commits include fixes/improvements with security aspects or functionality, from net, wlan, through encryption, etc. (see the commits in the source added from Feb 9 until now).

Long story short, this is what I am using for some time now and if anyone is interested let me know and I will make a build for you. However, "use it at your own" risk would be more valid then ever :)
[Galaxy S 4 Mini Android Development] kevinarol:
What will be the new feature? I would like to try
[Galaxy S 4 Mini Android Development] csendre:
There is no new feature, just various patches, fixes, etc.
[Galaxy S 4 Mini Android Development] kevinarol:
Aahh ok, anyway I would like to try those parches and fixes, if you want I'm using a serrano3gxx i9190
[Galaxy S 4 Mini Android Development] csendre:
Update: Here are both developmental kernels, use it at your own risk

Remix-3-Dev-kernel-3G-DS-20170307

Remix-3-Dev-kernel-LTE-20170308
[Galaxy S 4 Mini Android Development] whyhere:
I flashed the 5100 mAh kernel, kernel Adiutor still indicates 1900 mAh battery capacity. Correct behaviour or something went wrong?
[Galaxy S 4 Mini Android Development] Harvey_Spectar:
The kernel is for 5100 mah battery.

It will not increase your battery capacity.

This kernel is nade for the members who have 5100 mah battery.
[Galaxy S 4 Mini Android Development] whyhere:
I know, I have a 5100 mAh battery (zerolemon), reason why I expected to read the correct caoacity on kernel adiutor
[Galaxy S 4 Mini Android Development] Harvey_Spectar:
U want battery life or battery in kernel auditor?
[Galaxy S 4 Mini Android Development] whyhere:
I want simply to understand why battery capacity is not correctly read after flashing the dedicated kernel. Ok?
[Galaxy S 4 Mini Android Development] Harvey_Spectar:
its ok. nothing to worry about
[Galaxy S 4 Mini Android Development] kamikaze702k:
Mine is the same, still behaves as a normal battery and does shut down when battery is "low" but when you power back on you have more than half battery left....

Maybe it can be fixed but it works on CM14 as directed just not on CM13....
[Galaxy S 4 Mini Android Development] whyhere:
Ah ok. It seems a common problem Nothing went wrong when I flashed. I am using CM 14 kernel on resurrection remix rom. I hope it will be fixed.

---------- Post added at 11:37 AM ---------- Previous post was at 11:36 AM ----------

No problem.
[Galaxy S 4 Mini Android Development] kamikaze702k:
On CM14 it should work as intended someone previously tested and reported no shut downs or false battery stats, for me on CM13 as just as mentioned previously. Acts like a standard battery.
[Galaxy S 4 Mini Android Development] whyhere:
Thank you for the good news. I bought the battery yesterday and fully charged last night for the first time. So, I do not know its behavior. After unplugging, this morning, I have checked the battery capacity in kernel adiutor and found 1900 mAh instead of 5100 mAh as expected. I am not sure why the battery capacity is not correctly detected.
[Galaxy S 4 Mini Android Development] csendre:
No clue what kernel adiutor uses to display this.
[Galaxy S 4 Mini Android Development] whyhere:
I confirm. It works fine
[Galaxy S 4 Mini Android Development] kamikaze702k:
Works on CM14 but not CM13 as intended, I hope maybe if you could on the next release try again? Thanks
[Galaxy S 4 Mini Android Development] whyhere:
Not a deal. The 5100 mAh variant of your CM14 kernel works perfetcly. Great work. I hope you keep this variant updated.
[Galaxy S 4 Mini Android Development] kamikaze702k:
I hope the CM13 version gets another looking on the next update would be awesome to have it working properly
[Galaxy S 4 Mini Android Development] csendre:
New Remix-2 builds are up for CM/LOS 13 based ROMs

Changes: sync with upstream, arco merged some of the CM-14 kernel commits into the CM-13 one
[Galaxy S 4 Mini Android Development] Tom Mix:
BLN again and again and again ...

[MENTION=1769754]participant[/MENTION]s

this is the latest and most informational info i was able to find here:

unfortunately this seems to be not the same as BLN control like it is in KK.

no blink pattern, no time schedule...

so just a worse surrogate :crying:

am i correct that BLN is not supportet anymore since KK kernel?

are there any information what caused that?
[Galaxy S 4 Mini Android Development] csendre:
[MENTION=637936]Tom Mix[/MENTION] BLN is obviously supported by the kernel, it would not work if it wouldn't be. I am using it and have reports from other users who are using it successfully as well. You can create a script to enable it in data/local Blinking can also be enabled in script. Look at this, works for me: https://github.com/loomy/androidstuff/blob/master/userinit.sh

If you have an issue with BLN Control app, take it up with the app's developer, it has nothing to do with BLN functionality in the kernel.

Update: look at this video, just made it of my 9192 running latest AOKP and Remix kernel using the script from above

I just checked, this is not a Remix feature, it is actually part of stock kernel as well since 2014 when arco68 added it. It was not initially part of CM 10.2 and 11 kernels
[Galaxy S 4 Mini Android Development] icero:
It seems that I am very stupid because I do not get it to work for me: / I pasted the file in / data / local and it still does not work. Could I send a catch of the permits I have to give? Please excuse my lack of experience
[Galaxy S 4 Mini Android Development] csendre:
[MENTION=5870407]icero[/MENTION] I really don't know why it is not working for you. I can tell you that I used adb to push the file to my phone. If you used another method maybe is not copied right? Can you describe in detail what have you done?

With regards to permissions, I am not sure if this is needed but you can run the following adb command to make sure: "adb shell chmod a+x /data/local/userinit.sh"
[Galaxy S 4 Mini Android Development] icero:
I am pushing the file through root Explorer in the path / data / local and then restart the device: / No job for me :(
[Galaxy S 4 Mini Android Development] csendre:
OK, first make sure it is actually there.

Then use a terminal emulator like this or Termux and enter following:

su
chmod a+x /data/local/userinit.sh

After su you will be ask to grant root permissions. When done, reboot, see if it helped. Here is a screenshot, it should look like this
[Galaxy S 4 Mini Android Development] icero:
I'm definitely not made for this .........

I do exactly what you tell me and still I do not get a good result.

Thank you very much for your time. I will have to forget BLN in all Lol
[Galaxy S 4 Mini Android Development] helium314:
I'm not sure how it should be done correctly and how to change any settings, but I just copied the userinit.sh, made it executable and it works after reboot (steady light on notification).

Maybe the BLN control app had some influence, but I removed it immediately because it said that my kernel doesn't support BLN.

Is there any way to change the brightness?

Ok... after another reboot it didn't work any more.
[Galaxy S 4 Mini Android Development] Kot_Ik:
[MENTION=5416372]csendre[/MENTION] [MENTION=5870407]icero[/MENTION] [MENTION=7936379]helium314[/MENTION]

AFAIK there was some selinux issue preventing /data/local/userinit.sh execution. You can see that in logcat.

I had to make my own script placed to etc/init.d, and also put some script to addon.d to survive over nightlies installations. It works like a charm.

As an example see attachment.

To clean out BLN support delete two files with your filemanager: /system/addon.d/50-bln.sh and /system/etc/init.d/50bln

UPD there was a typo in recovery script. Download and apply it again. Sorry.
[Galaxy S 4 Mini Android Development] gay-sha:
Could some of the advanced users, make an exact tab of the procedure and file to use?

Would be of great help to the users with less experience (I include myself)
[Galaxy S 4 Mini Android Development] csendre:
Flash the above posted by [MENTION=475307]Kot_Ik[/MENTION] and see if it works.

---------- Post added at 06:07 PM ---------- Previous post was at 06:05 PM ----------

It is strange, I don't understand how it only affects some people.
[Galaxy S 4 Mini Android Development] HundVerruckt:
Hi! I'm wondering if this kernel support OTG USB, or how I can do that.
[Galaxy S 4 Mini Android Development] Harvey_Spectar:
Use y cable for it and if you want more information then read previous posts about it in this thread.
[Galaxy S 4 Mini Android Development] d3nni:
Anyone can tell me if its working with the latest 7.1.2 LineageOS build?
[Galaxy S 4 Mini Android Development] heilbron:
Yes, works for me!
[Galaxy S 4 Mini Android Development] o0chtm0o:
Hi [MENTION=5416372]csendre[/MENTION]

No news here? :)

BTW, Great job with AOKP. I'm inloved!
[Galaxy S 4 Mini Android Development] kullino:
Great work, limited_lte works fine. :)
[Galaxy S 4 Mini Android Development] MaChiMiB:
Is this still possible with the first official LOS nightly (lineage-14.1-20170428-nightly-serranoltexx)?

Not working here.

Seems /sys/class/misc/backlightnotification/enabled doesn't exist anymore
[Galaxy S 4 Mini Android Development] Kot_Ik:
I'm sad to hear it.

By default it was the symlink to /sys/devices/virtual/misc/backlightnotification

Is this path exist in current nightly? Do you use stock LOS kernel or [MENTION=5416372]csendre[/MENTION]'s one?

Can't check it for​ now, because I'm still on unofficial build (lack of time).
[Galaxy S 4 Mini Android Development] Tom Mix:
BLN again and again and again ...

since i also do have a massive lack of time to investigate this 'ISSUE' i kindly ask if one can e-x-p-l-a-i-n how it came to the drop of the highly functional Button-Back-Light-Misuse as a NotificationLED? i am on the latest available KK and this genius-mod saves me an enormous ammount of time per month. i am talking about hours! and the whole issue reads that the behaviour and possible configurations like KK BLN (with BLN control app) will not be possible ever again at all?!
[Galaxy S 4 Mini Android Development] MaChiMiB:
ah, I wasn't aware of that symlink behavior. You're right, /sys/devices/virtual/misc/backlightnotification is where the /enable and other files are. Flashing your zip file sets this to 1. But BLN isn't working, tried with default kernel and this kernel. Also tried with NSTools and BLN control.

Even installed an old 14.1 build (cm-14.1-20161222-UNOFFICIAL-serranoltexx.zip), but couldn't get it working.

I got it working on CM13.
[Galaxy S 4 Mini Android Development] csendre:
New CM-14 kernels are up, synced with upstream sources.

Not sure what to say about the BLN issue. [MENTION=5706443]DarkFrenzy[/MENTION] do you have an idea how to fix it?

I also asked [MENTION=3044346]arco68[/MENTION] for help since this is a feature coming from the stock kernel.
[Galaxy S 4 Mini Android Development] whyhere:
Do you want to build a 5100 mAh variant of the CM14 kernel?