yashsingh1/xdaforums huggingface dataset:
[Galaxy S 4 Mini Android Development] csendre:
It is not about will, it is about time

---------- Post added at 08:47 PM ---------- Previous post was at 08:46 PM ----------

I made a build where I enabled BLN in the kernel by default. it doesn't even work that way. Lets see if anyone has an idea ...
[Galaxy S 4 Mini Android Development] Tom Mix:
however...

i appreciate the effort. it is sad to read that it did not work... a new hope though!
[Galaxy S 4 Mini Android Development] RedSkull23:
Hi, just a question.

Flashing this kernel on the first official nightly of Los14.1 could correctly apply some benefits to the battery duration if i setup well some settings like cpu clocking, ecc? I have a GT-I9195 with still stock battery (my phone has 4 years in this august) and i can quietly reach the 2nd day if i don't overheat it that much, but i would like to tweak a lil' bit more with ram/cpu configuration to benefit even more... TIA.

Edit at 9th of may; [MENTION=5706443]DarkFrenzy[/MENTION] sorry if i ask ya directly but I've got no answers...
[Galaxy S 4 Mini Android Development] lm124:
Hello there, I flashed last kernel fro CM 14.1 to latest AOKP build. It seems to bring down max frequency to 270 Mhz or 162Mhz. Has Anyone this issue? It is only me?

Thanks in advance.
[Galaxy S 4 Mini Android Development] kevinarol:
Hi [MENTION=5416372]csendre[/MENTION] with the AOKP from 2017.05.01 and the Remix Kernel V10 I'm facing overheat
[Galaxy S 4 Mini Android Development] Kot_Ik:
[MENTION=5416372]csendre[/MENTION]

i have working BLN on both stock (official LOS 14.1 nightly) and your kernels.

Other thing i should mention is that i have constant heavy battery drainage on your kernel. I try to use kernel as it is, without any tweaks. Seems that at some point in time default CPU governer stuck with max frequency on both cores, phone get hot and battery quickly discharge. It was second time i try to use your kernel (for LTE, v9 on arco's unofficial build and the last one, v10, on official build). With clean system installs (after wipes). No luck. May be there is some influence of installed apps, but i try not to use any system tweaks as much as i can, so i don't even know what the reason. The only changes from clean LOS are BLN support and nano Gapps.
[Galaxy S 4 Mini Android Development] MaChiMiB:
wow, nice. Looks like I'm too stupid to get it running on my own... :(

Can you please elaborate what you do to activate it, besides flashing your bln-signed.zip from post #1717
[Galaxy S 4 Mini Android Development] Kot_Ik:
Well, uhm, you should flash zip-file, reboot to system, configure any app that support LED notification to light the LED when it needed, that's all.

Telegram and Inbox, for example, can be manually configured, although they works well by default; stock SMS and Phone lights the leds without any additional configuration.

Main things are all under the hood of system libraries, they provide interface to interact with leds. My script just enables this interaction, no more no less. After that any app that supports led notification can light leds through system calls.
[Galaxy S 4 Mini Android Development] MaChiMiB:
not working here.

clean install of lineage-14.1-20170428-nightly-serranoltexx together with open_gapps-arm-7.1-nano-20170502.zip and your bln-signed.zip.

Boot up. Select set up as new device. Minimal setup, didn't even set up wifi. I don't use the software navbar, but instead the capacitive keys (default). Wait a little until everything has settled. Miss a call. Get no BLN (the capacitive keys do not stay lid up to signal me the missed call).
[Galaxy S 4 Mini Android Development] csendre:
Please share what you have done to make it work

Edit: Sorry never mind, I completely missed that post of yours. Will have to look into that selinux denial

Not sure what to say, I don't see an obvious reason why. Try to set a different governor, play with multicore power saving and CPU hotplugs. For governors try alucard, yankactive, impule (or others). For CPU hotplugs alucard ot intelliplug are good choices (you can set a performance profile too). With patience you should be able to find the profile that is best for you.
[Galaxy S 4 Mini Android Development] Kot_Ik:
Is there something in logcat, selinux related? Do the init.d script (that 50bln) really run at system boot? Is there "1" in /sys/class/misc/backlightnotification/enabled after boot?

Can you provide ls -lZ /system/etc/init.d output?

You can try to control LEDs over rooted adb, to see if BLN really works, but from phone I can't find that GitHub repo, where I saw how to make all that magic things manually from commandline. May be later today.

We have an identical hardware and software, so I can't see any reason why should you suffer from lack of BLN support.

UPD

Got it: Loomy's androidstuff. Can't see if it can help though. You should have undiscarded notification, have "1" in /sys/class/misc/backlightnotification/enabled and only then you can play over adb with /sys/class/misc/backlightnotification/blink_control

Not really helpful with fact that you should see leds on without touching blink_control.
[Galaxy S 4 Mini Android Development] helium314:
I noticed there is somewhat higher CPU load and battery consumption when using remix kernel (no kernel control app installed)

For example when playing music with default kernel (AOKP) there is 77% 384 MHz, 18% 486 MHz and 4% 594 MHz, and with remix it is 74% / 19% / 7%. Not so much difference, but this is reproducible with different versions of default and remix kernel.

There is also a noticable difference in battery consumption, remix is usually about 0.5%/h higher. Also idle consumtion seems to increase slightly, from 1.8-2.2% / h to 2-2.4% / h, but those values may be too close to each other to really trust them. Even when I tried underclocking / undervolting with kernel adiutor, battery consumption did not drop below default kernel.

Why is this happening with remix kernel?
[Galaxy S 4 Mini Android Development] MaChiMiB:
your bln-signed.zip, as well as the Loomy's androidstuff, as well as the NSTools work flawless. They all use the symbolic link /sys/class/misc/backlightnotification/enabled to set /sys/devices/virtual/misc/backlightnotification/enabled to 1. That stays at 1 even after a restart. So there is no problem.

With

adb shell "echo 1 > "/sys/class/misc/backlightnotification/enabled""

I can enable that manually, but BLN still doesn't work.

With

adb shell "echo 1 > "/sys/class/misc/backlightnotification/notification_led""

I can trigger the button backlights. They stay lit until I wake up the devices. This command only works if /sys/devices/virtual/misc/backlightnotification/enabled is set to 1.

When I tested that with the Loomy's androidstuff script, the buttons also showed the blinking.

When I switch to the software navbar, there is no difference.

The liblights.c code uses this /notification_led to trigger the BLN behavior. So the very basics of the BLN features work. But I got no idea how that liblight.c code is triggered by notifications.

EDIT: installed a whole lot of different builds. Just the OS and the bln-signed.zip. Did nothing else, then I just missed a call and checked if the buttons stay lit up after.

BLN does work on LOS(cm)13, even the most recent 13.0 nightly and doesn't work on LOS(cm)14, even the very first test version of 14.0

So the step from 13.0 to 14.0 killed BLN.
[Galaxy S 4 Mini Android Development] kevinarol:
Sorry was false alarm, I had put touchboost :silly:
[Galaxy S 4 Mini Android Development] Kot_Ik:
For your case only. I don't have any problems with BLN from CM13 to LOS14.1.

Just checked the "missing call" case: one second after screen turn off - leds lights on.

It seems mysterious.
[Galaxy S 4 Mini Android Development] Rainy_2k:
I don't have any problems with BLN too. After dirty flash of the latest build, I copied csendre's script "userinit.sh" to /data/local to test BLN. Just asked my wife to send me a message on whatsapp and it works. Hardware buttons are blinking while phone is locked and screen is off.

Отправлено с моего GT-I9192 через Tapatalk
[Galaxy S 4 Mini Android Development] csendre:
BLN started working again on latest 7.1.2_r8 based builds (Both AOKP and LOS) even with the /data/local placed userinit scripts. I guess selinux denials were addressed as not just this but no other user scripts were running and I saw a lot complaints about this on forums.

People having issues, please update your ROM. This is definitely not a kernel problem.
[Galaxy S 4 Mini Android Development] Tyranio:
3800 mha battery

Hey there!

I'm running "lineage-14.1-20170428-nightly-serranoltexx-signed". I've bought a 3800 mha battery and flashed "Remix-kernel-CM14-v.8-LTE-Double_Size_Battery-20170215". Kernel Adiutor is still showing 1900 mha as capacity. Am I doing something wrong?
[Galaxy S 4 Mini Android Development] whyhere:
Same here with 5100 mAh battery. Capacity is not correctly read, but the cm14 kernel works fine. There a previous post of mine reporting the issue.
[Galaxy S 4 Mini Android Development] MaChiMiB:
update on BLN:

BLN works with calender notifications and messages if ambient display is disabled (settings -> display).

BLN works with missed calls if you set "do not disturb" or toggle through it (activate and then deactivate it) EVERY time you restart your phone. The ambient display setting does not effect this in any way. So if no "do not disturb" setting is selected and you restart your phone BLN will not work until you select (or toggle through) one.

Google Keep notifications don't work properly . (worked one in 20 cases)

Could someone please confirm this?
[Galaxy S 4 Mini Android Development] csendre:
New set of CM-14 kernels are up. Synced with upstream
[Galaxy S 4 Mini Android Development] kevinarol:
Thanks :highfive:
[Galaxy S 4 Mini Android Development] Kot_Ik:
Nope. BLN works as it should.
[Galaxy S 4 Mini Android Development] Tyranio:
Is there any chance that the kernels for the bigger batteries going to be updated as well? It would be so lovley, the S4 Mini is such a good devices with the double sized battery. Thanks you alot for your work, an take a part of keeping this old devices alive! (I hope my last setence makes sence in English). Greetings!
[Galaxy S 4 Mini Android Development] csendre:
I may do this once or twice a year, but that's it. Think about it, people have at least 3 popular battery sizes, x2 type of kernels + the 2 regular ones, that would be 8 kernel builds to do every time. I have no time for that.

People with custom batteries should learn how to self build, it is not hard and not resource intensive so it works on slower computers as well. I always keep sources on my github up to date, so this is not a problem either.

Or, and this would be the best; perhaps someone who already knows how to build could pitch in, make the builds and post links here. Any volunteers?
[Galaxy S 4 Mini Android Development] Tyranio:
if i have some time i'm going to start to read about building kernels, maybe i will be able to do that.
[Galaxy S 4 Mini Android Development] Harvey_Spectar:
If you want I can do that.

If you agree then we can talk about it in private
[Galaxy S 4 Mini Android Development] csendre:
Ok, so for those who want to compile for larger batteries, this is what you need to do. Here is the file you need to modify:

https://github.com/csendre/android_...blob/remix-3/drivers/power/pm8921-bms.c#L1238

In the highlighted line insert the following:

/*scale factor multiplied by 2 for extended battery */
scalefactor *= 2;

The scale factor (2 in the above example) has to be calculated for your specific battery, in this case it would be double size (1900x2=3800mAh) If you have a 5100mAh battery, the scale factor is 5100/1900=2.7

Now here are the sources you need:

Remix 2 (MM ROMs)

Remix 3 (Nougat ROM's)

Build tool source (Uber TC):

https://bitbucket.org/UBERTC/arm-eabi-4.9
[Galaxy S 4 Mini Android Development] csendre:
New set of cm14 kernels are up (v.12); synced with upstream changes
[Galaxy S 4 Mini Android Development] Rainy_2k:
Still version 11 in the filename.

Remix-kernel-CM14-v.11-3G-DS-20170521
[Galaxy S 4 Mini Android Development] csendre:
Crap. I'll fix it. The kernel is actually v.12
[Galaxy S 4 Mini Android Development] csendre:
v.13 is up, arco merged some more commits after I made the previous build
[Galaxy S 4 Mini Android Development] Tyranio:
I've tried to compile a kernel for the double sized battery, but i failed. Does anybody where i can find a good tutorial?
[Galaxy S 4 Mini Android Development] csendre:
Post the error along with commands and toolchain used to compile
[Galaxy S 4 Mini Android Development] fankool:
I tried for 3 years to enable BLN on my s4 mini, never worked. Now I'm using Resurrection Remix N 5.8.3 [7.1.2] and I tried using BNL control app. With original kernel and this kernel there's the same output, " this kernel does not support BLN.". Can someone explain me how can I enable or suggest a link with information?

thank you
[Galaxy S 4 Mini Android Development] csendre:
v.14 of CM-14 kernel is uploaded; HOWEVER, I would not use it on builds made on or before May 28. It goes together with a commit in serrano-common merged today by arco.68 Not sure how it behaves without it. Also, I left out a commit by arco68 which disables ultrasound driver as it was reported by a user in the AOKP thread that this breaks functionality with certain apps
[Galaxy S 4 Mini Android Development] Tyranio:
Allright, so this is what i did:

- Setting up a clean Ubuntu 16.04.2 LTS 64 bit

- Updated Ubuntu

- Cloned the Kernel Source (git clone https://github.com/csendre/android_kernel_samsung_msm8930-common.git)

- Cloned UBER TC (git clone git clone https://bitbucket.org/UBERTC/arm-eabi-4.9.git)

- Edited the Kernel Source as you said via nano

No problems so far. Questions:

- Do I need additional packages in my clean Ubuntu enviroment. If so, wich?

- Wich commands I have to enter to start the compiling process?

I've tried some tutorials, but there are all different or old and nothing worked so far. It can't be that hard to just start a compiling process.

Greetings!
[Galaxy S 4 Mini Android Development] Ulises31:
Hi

I did same as you, I tried with several distros: Ubuntu, Mint and Zorin installations. At the end, the best was with Ubuntu, but no success. When compiling, with make namedevice_defconfig no problem, then I performed the make -j# (# is the number of cores in my CPU) and the errors appeared. It looked as if several files were lost. Previously I installed the jdk and any other packets I found in several tutorials.

So, I don't know which packages were missed. I will go on trying.
[Galaxy S 4 Mini Android Development] csendre:
This is why I was hoping that someone who knows how to build picks this up, I don't want to turn this kernel thread into a tutorial. I know there are several people out there who could do it but nobody seems to want to contribute any more.

Here is a good thread for building and how to set up build environment https://xdaforums.com/showthread.php?t=1748297

If you have a build environment set up for ROM building, you should be OK for kernel as well, you just need the tool chain. For ROM build environment there is a good tutorial on RR github https://github.com/ResurrectionRemix/platform_manifest

For building you run these (this example is for 3G/DS):

export ARCH=arm
export CROSS_COMPILE=~/(your path to the toolchain you are using)
make VARIANT_DEFCONFIG=msm8930_serrano_eur_3g_defconfig samsung_serrano_defconfig
SELINUX_DEFCONFIG=selinux_defconfig
make -jx (x depends on the number of your cpu cores; recommended to use number of cores x2)

For example if you cloned 4.9 toolchain into ~/android/toolchains/arm-eabi-4.9 then the second line is:

export CROSS_COMPILE=~/android/toolchains/arm-eabi-4.9/bin/arm-eabi-

If you are building for LTE, the third line is:

make VARIANT_DEFCONFIG=msm8930_serrano_eur_lte_defconfig samsung_serrano_defconfig

For the j option, if you are using a quad core CPU you can use make -j8 in the last line.

And of course, you run all this from the folder where you have downloaded the kernel source.

Once you made the change to pm8921-bms.c, you should also commit the change otherwise you will build a "dirty" kernel. For this you can use something like:

git commit drivers/power/pm8921-bms.c -m "commit message e.g. duoble capacity battery"

If all goes well, when build completes you will have a zimage file in arch/arm/boot which is your actual kernel. You will also have a few files with .ko extension all over the kernel folder (you will have to search for these) which are your modules.

To make a flashable zip you can either search for "Anykernel" in this thread and use it (it is what I am using) or you can just replace zimage and the modules in one of my builds and flash it
[Galaxy S 4 Mini Android Development] kevinarol:
Thank you for this guide [MENTION=5416372]csendre[/MENTION], just one more question How do I change the name of the kernel display in "about"? (where it say "Remix-v14...") :highfive:
[Galaxy S 4 Mini Android Development] csendre:
Here https://github.com/csendre/android_...arch/arm/configs/samsung_serrano_defconfig#L4
[Galaxy S 4 Mini Android Development] kevinarol:
Thanks [MENTION=5416372]csendre[/MENTION] :good: I forget something, for update the project in case you merge some changes just run the "git clone" and update just the new, right?
[Galaxy S 4 Mini Android Development] csendre:
git pull from within the repo's folder when you already have the repo cloned
[Galaxy S 4 Mini Android Development] kevinarol:
Thank you very much for your help ?
[Galaxy S 4 Mini Android Development] AgentOrange96:
I was building both for vzw and lra, and yesterday my builds were bricking my SCH-i435L. (It would never get past the Samsung screen, it kept rebooting) I have built in the past for these with no problem. Unfortunately, I was dumb and deleted my old builds, so I guess I'm stuck on the regular kernel for now. (My bad) I figured I'd give a heads up.

I did disable auditing support, but I've done that in the past too.
[Galaxy S 4 Mini Android Development] Ringgss:
Since last nightly of lineage bluetooth media sharing force closes and bluetooth wont turn on. On stock kernel no probleem with bluetooth.
[Galaxy S 4 Mini Android Development] iceviper2610:
Same here, i reverted to the previous build an everything is working again.
[Galaxy S 4 Mini Android Development] Anewkine:
Hello,

Just a small question about whether I am the only one in the case.

I have a GT-I9195, when I flash this version of the Kernel ==> Remix-kernel-CM14-v.14-LTE-20170528.zip

I have this small bug. It is written in the version of the Kernel "v13"

Personally it does not bother me at all, everything works perfectly.

Thanks for hard work for our beloved S4 Mini. :svetius:

Regards. :p

Anewkine
[Galaxy S 4 Mini Android Development] jake3317:
I have the same issue with bluetooth with the 0604 ROM from AICP. What do you mean with 'previous build'? Kernel or ROM?
[Galaxy S 4 Mini Android Development] Ringgss:
Probably ROM, with previous kernel I have the same bug.
[Galaxy S 4 Mini Android Development] csendre:
I am not saying you are not right, but it doesn't make sense. v.14 has all the commits as stock kernel and unchanged since May 28. So if the previous nightly worked with Remix kernel there is no reason why this one wouldn't or there is no reason why it would with stock since both kernels are unchanged since then ....

Update: Thanks to [MENTION=5902252]Anewkine[/MENTION] I realized something. For some reason not all commits got pulled into the build. Will delete my local sources, re-sync and make a new build of v.14 later tonight or tomorrow.
[Galaxy S 4 Mini Android Development] csendre:
OK, so I deleted the old v.14 kernels and uploaded new builds. You can tell by the build date, these were built today 06/07

Please report back if the BT sharing issue still persist or is it same now as on stock

People who flashed previous v.14, please flash the new one. .Sorry about this.
[Galaxy S 4 Mini Android Development] JimmyRay:
Great support csendre, keep up the good work!
[Galaxy S 4 Mini Android Development] iceviper2610:
Just tested the new build and it seems to solve the problem. Bluetooth is back alive ;) Thanks for the good job [MENTION=5416372]csendre[/MENTION] Keep up the good work! :good:
[Galaxy S 4 Mini Android Development] Ringgss:
No force close @ enabaling bluetooth. Not tested on carkit yet. Looks like its working again. Tnx csendre for this quick fix. Youre awsome!

Ps no need to say sorry m8. Im really happy with you and youre kernel. This is why I still use this device after 4 years.
[Galaxy S 4 Mini Android Development] o0chtm0o:
Don't worry. Thanks and don't leave us ever please :good: :fingers-crossed: :highfive:
[Galaxy S 4 Mini Android Development] Ringgss:
FYI bluetooth is working fine with new build on my carkit again.
[Galaxy S 4 Mini Android Development] DarkFrenzy:
Ya u flashed the duos kernel i posted and it worked
[Galaxy S 4 Mini Android Development] milouk:
yep i remember what you are talking about...i'll change the boot.img form your CM 13 kernel with the one in the UB rom and i will report
[Galaxy S 4 Mini Android Development] DarkFrenzy:
Oh i posted a wrong link check the prevous post of ... the guy
[Galaxy S 4 Mini Android Development] DarkFrenzy:
Oh thankyou i didnt see that.

Is smartassh3 working
[Galaxy S 4 Mini Android Development] DarkFrenzy:
http://xdaforums.com/showthread.php?p=64994897

Sorry i was in hurry
[Galaxy S 4 Mini Android Development] o0chtm0o:
This is Bliss LTE latest boot.img LINK

FM Radio is working
[Galaxy S 4 Mini Android Development] milouk:
thanks man

---------- Post added at 02:50 PM ---------- Previous post was at 02:49 PM ----------

no worries :P

---------- Post added at 03:00 PM ---------- Previous post was at 02:50 PM ----------

---------- Post added at 03:02 PM ---------- Previous post was at 03:00 PM ----------

@DarkFrenzy ...just change the boot.img from your kernel to boot.img from Bliss Kernel (the correct one) and still no FM radio...so probably it has something to do with your kernel..
[Galaxy S 4 Mini Android Development] DarkFrenzy:
What u mean u replaced the boot.img in my xx.zip with blissrom (by tgudo) kernel
[Galaxy S 4 Mini Android Development] DarkFrenzy:
Is smartassh3 working bro?
[Galaxy S 4 Mini Android Development] o0chtm0o:
SmartAssH3 is just on F4k kernel my friend. Bliss still doesn't have that one implemented on it
[Galaxy S 4 Mini Android Development] DarkFrenzy:
[MENTION=6057323]tioguda[/MENTION] can u build your bliss kernel for Tab 3 lt02 sprint. its just about deconfig so thats easy. i will give u my deconfig u just make using that one. or if u cant can u give your kernel source in a zip file
[Galaxy S 4 Mini Android Development] KevinX8:
Latest version 02/22 broke OC on cm 13 lte version going back to 02/17
[Galaxy S 4 Mini Android Development] DarkFrenzy:
Hey try the aicp11 ltexx from attachments and see that someone told oc is fine plz test that.
[Galaxy S 4 Mini Android Development] KevinX8:
Um I'm not on aicp11 I'm on cm 13 will it still work?
[Galaxy S 4 Mini Android Development] DarkFrenzy:
Oh thats tru but try
[Galaxy S 4 Mini Android Development] piskor:
[MENTION=5706443]DarkFrenzy[/MENTION]

Is it possible to add current date / time to attached kernels when they are uploaded to the OP?

Now we can see only, when first post is updated, but it is hard to recognize which attachment was changed.

You are to fast :)
[Galaxy S 4 Mini Android Development] KevinX8:
Followed your advice can confirm it works and OC works too but am unsure how stable it is. Will report any random reboots
[Galaxy S 4 Mini Android Development] flapane:
In general, a changelog and the date in the file name would be much appreciated.
[Galaxy S 4 Mini Android Development] DarkFrenzy:
Ok. Rigth now only the aicp11 ltexx.is changed or updated or the new one
[Galaxy S 4 Mini Android Development] milouk:
OC is fine FM radio still broken
[Galaxy S 4 Mini Android Development] Anewkine:
How fast to update !!! :D

Many thanks for your hard work.:good:

Regards.

Anewkine