yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Mini] A_U:
damn i deleted the kernel tar ball before u posted :( i thought some files were missing in the source itself :/ damn ! re-downloading..

ok will recompile..and u mean to put that module in the toolchain /bin folder itself isnt it ? @alin.p
[Samsung Galaxy Mini] Jeeko:
Nope, put the lz4 file from your home directory to the /bin folder of your main partition by typing

sudo cp lz4 /bin/

and then set the permissions with

sudo chmod 755 /bin/lz4

then recompile and you'll get the zImage
[Samsung Galaxy Mini] alin.p:
Jeeko is right. You have to put the binary inside your Linux bin folder. The image creator script of the kernel uses bash to call the compressor, and bash only works with binaries from /bin/ or other bin paths declared by the user. Otherwise, full path of the binary has to be specified. Like this:

gzip -dc "somefile" will call gzip from /bin/ to compress somefile

~/gzip -dc "somefile" or /home/username/gzip -dc "somefile" will call gzip from the specified paths to compress somefile
[Samsung Galaxy Mini] A_U:
now i am getting this..i did wat jeeko said.. [MENTION=4525074]alin.p[/MENTION]

/bin/lz4: 1: /bin/lz4: XU: not found
/bin/lz4: 1: /bin/lz4: �U: not found
/bin/lz4: 1: /bin/lz4: ELF: not found
/bin/lz4: 2: /bin/lz4: Syntax error: ")" unexpected
make[2]: *** [arch/arm/boot/compressed/piggy.lz4] Error 1
make[2]: *** Waiting for unfinished jobs....
CC arch/arm/mach-msm/dma_test.mod.o
CC arch/arm/mach-msm/reset_modem.mod.o
CC arch/arm/oprofile/oprofile.mod.o
CC drivers/input/evbug.mod.o
CC drivers/net/wireless/libra/librasdioif.mod.o
CC drivers/scsi/scsi_wait_scan.mod.o
make[1]: *** [arch/arm/boot/compressed/vmlinux] Error 2
make: *** [zImage] Error 2
make: *** Waiting for unfinished jobs..
[Samsung Galaxy Mini] alin.p:
Now that's weird.. seems like the compressing script passes a wrong command to the LZ4 compressor. I have never experienced this, and I can't solve such a problem remotely.

To save some time and sane mind, better re-clone the sources in a clean folder and restart compiling. By the way, 4.8 toolchain breaks the camera driver, so I switched back to 4.4.3, in case anyone wants to compile.
[Samsung Galaxy Mini] A_U:
i recloned again..and started a fresh compile usin 4.8..let me see wat happens

and did u test with linaro 4.6.2 ? is it breaking the driver ?

edit - still getting the same error that i got above..

so i will try wit 4.6.2 and if that gives error i will try ur toolchain
[Samsung Galaxy Mini] alin.p:
That error isn't caused by the toolchain. I think the lz4 binary is not compatible with your Linux distro. You might need to compile your own LZ4, don't worry, it is a simple gcc command.

Find the lz4.c source file of the compressor on Google and use "gcc lz4" to compile it.

I already had 4.4.3 downloaded so I didn't bother to find and re-download 4.6.2. It doesn't make any difference anyway.
[Samsung Galaxy Mini] Masrepus:
Wow [MENTION=4525074]alin.p[/MENTION] great idea this with the sensor inside the camera! I hope u manage to do that, so ur kernel will be the first and only one to enable auto brightness on mini :D

Edit:: just saw u have 1000 thanks now ;)

---------------------------------

Gesendet von Tapatalk 4 beta
[Samsung Galaxy Mini] alin.p:
Yeah, 1000 thanks :) just noticed it too. Many thanks to all for the appreciation. I hope the new version of the kernel will be worth it :p
[Samsung Galaxy Mini] Masrepus:
Of course it will be man! ;D

---------------------------------

Gesendet von Tapatalk 4 beta
[Samsung Galaxy Mini] A_U:
got the same error while i built with 4.4.3...

so its the lz4..

is this how i remove it from my bin folder ?

sudo rm /bin lz4

and is the one ? http://code.google.com/p/lz4/source/browse/trunk/lz4.c?r=102

its the latest version..16th august
[Samsung Galaxy Mini] alin.p:
Yes, that's the command for removing it.

I don't remember well but I think that is the correct source. Seems like it's been updated. I think I'll recompile it too.
[Samsung Galaxy Mini] A_U:
never mind got it..compiling now..

edit - the kernel doesnt boot ! its just shutdowns after sometime..doesnt even start to boot splash..wats wrong ? was it booting for u before u made the changes? [MENTION=4525074]alin.p[/MENTION]
[Samsung Galaxy Mini] ast00:
I'm pressing thanks on all of your post, except for times I reach my daily thanks limit.
[Samsung Galaxy Mini] alin.p:
My stable branch is exactly in the

state that the GitHub source is in too. I'll check the defconfig when I get home, this is the only file I forget to change from time to time.

EDIT: [MENTION=4677294]A_U[/MENTION]

The defconfig is updated, so nothing wrong with the source. Maybe you are using a wrong ramdisk or you have some corrupt file in it. The ramdisk for this kernel has some modifications too, but I'll have to clean my folder containing the modified ramdisks and rewrite some scripts before uploading them to git.

Also, for every feature to work, there are some more modifications to make. Per-rom modified keylayout will be added to the flashable zips, and probably a modified services.jar too, for the ROMs that have their development stopped (like CM9.2).

So, for the moment, I think it is better to wait until I finish all this stuff.

One more thing for those using CM10.1, if anyone can find the keycode and the name of the key that triggers Recent Apps.. In ICS is called APP_SWITCH but in CM10.1 I noticed this has changed.

:)) Thank you too!
[Samsung Galaxy Mini] A_U:
[MENTION=4525074]alin.p[/MENTION] here's the zimage that i compiled yesterday..

can u pack it into a boot image with the ramdisk changes that u made, to made it boot ?
[Samsung Galaxy Mini] prafiles:
I too want to know this one specifically. My zImages are compiled properly and everything but my boot.img wont boot. (I did this a long time ago from source of 1.9.2. but didnt succeed.)
[Samsung Galaxy Mini] alin.p:
It doesn't boot.. Something might be wrong in your compilation environment, I just tested a fresh compiled zImage with 4.4.3 toolchain from the source on GitHub and it boots.

But I have no idea of what could be the exact problem.
[Samsung Galaxy Mini] Dark Passenger:
hey alin check this out might give you an idea for an algorithm with a better battery life for autobrightness though this still the problem of how to activate partial camera hardware remains.

http://xdaforums.com/showthread.php?t=2280985
[Samsung Galaxy Mini] alin.p:
That is Auto-Brightness using apps. I know about the Lux Auto-Brightness for a long time, and actually this app gave me the idea of implementing this feature into the kernel, because it would be a hell lot faster, with approximately zero resources wasted (RAM, Power, CPU). The algorithm for controlling auto-brightness and making it battery-friendly is pretty easy to write. I'll use a lot of smart interrupts and some help from other drivers (LCD, Proximity, Touch, probably Accelerometer) to make sure that the brightness adjusting happens only when absolutely needed. Controlling the light sensor individually is the hard part.

I managed to cut the power of the camera and turn on only the light sensor, but the lux reading is pretty.. wrong.

Now, I have to sort out what registers have to be written to the I2C Bus so it will return the correct lux reading, then I head on to creating the whole algorithm.
[Samsung Galaxy Mini] mickey4398:
alin.p can you post some screenshot of making Kernel?
[Samsung Galaxy Mini] ast00:
Strange idea...

Tapatalk 2-vel küldve az én GT-S5570-ről
[Samsung Galaxy Mini] alin.p:
uhm.. What am I supposed to capture in the screenshot?
[Samsung Galaxy Mini] A_U:
lol wut ?
[Samsung Galaxy Mini] Masrepus:
Maybe screenshot(s) of how to compile a kernel???

---------------------------------

Gesendet von Tapatalk 4 beta
[Samsung Galaxy Mini] aakashasaj:
I want version 1.5 of this kernel, i guess it was the best, in all other above kernel i am facing heavy freeze. If anyone could provide me v. 1.5 that would be divine. Thank you.

Rom: Jeeko's Halo+project

www.twitter.com/_aakashasaj
[Samsung Galaxy Mini] Jeeko:
There is a guide http://xdaforums.com/showthread.php?t=1748297 without screens, but it's really helpful
[Samsung Galaxy Mini] prafiles:
What about the process from zImage to boot.img for our kernel? (Someone who has it booting and might want to share what settings and all?)
[Samsung Galaxy Mini] alin.p:
I sent Jeeko some customized ramdisks a while ago, but since then I made a lot more changes to the ramdisk, and right now nobody has what is required for booting the kernel and using it at its fullest (some features are activated in the ramdisk).

I promise I'll upload the ramdisks and scripts for making boot.img repacking a breeze, no matter what ROM you will be using. But I'm still doing modifications, I can't upload anything right now.
[Samsung Galaxy Mini] aamm95:
Hi alin.p

Can you see this link about mount2sd? https://github.com/SpazeDog/mounts2sd#table-of-content

On the "Safe Mode" paragraph it explains the existence of two init.d support types: One which executes scripts in the background while the OS is booting and one which executes scripts in the foreground while waiting for them to finish before booting the OS.

I think that a lot of problems with sd-ext implementations would be avoided..

It may be posible implement the second init.d support on your kernel?

PD: I think your work it's very great...Thnaks for your efforts and sorry for my poor English...
[Samsung Galaxy Mini] alin.p:
That second init you are talking (scripts executed before boot) is located in the ramdisk and can be modified only be the kernel developer or by a very experienced user. It's not a user-controlled folder like init.d. In fact, init.d was created to mimic the features of the ramdisk init scripts, but for obvious reasons it cannot be executed before boot.

Anyway, to conclude something, sd-ext issues are not caused by the moment of the execution for the ext mounting script. Issues happen because the partitions are not always universal. Some scripts might try to mount a different kind of partitions than ours and this results in wrong symlinks and bootloops.
[Samsung Galaxy Mini] aamm95:
Thanks a lot for your quick answer. I'm very, very noob at android development and there are some things that come out of my understanding....
[Samsung Galaxy Mini] alin.p:
Well, whenever you're in doubt, don't hesitate to ask. I don't mind spending 2-3 minutes to enlighten some facts.
[Samsung Galaxy Mini] Charlie:
Will badass have negative affect with pureperformance of jeeko? ---> http://xdaforums.com/showthread.php?t=2361379
[Samsung Galaxy Mini] Masrepus:
For me it did not work, many lags

---------------------------------

Phone : Samsung Galaxy Mini S5570

OS:

•AOSP ICS Touchwiz V5 by A_U

•Android 4.0.4

•Baseband XWKS2

•Kernel: 2.6.37.6 Badass v1.9 by alin.p

•Recovery CWM v4.0.0.5

Mods:

PureAudio, Mounts2SD, ODEX through Universal ODEX script, AdBlock by AdAway

---------------------------------

Gesendet von Tapatalk 4 beta
[Samsung Galaxy Mini] alin.p:
On 2.0, no other script/mod/pack will be allowed. No PurePerformance, no FlyON Mod, no Crossbreeder no whatevercoolnameyoucanthinkabout.

Every working tweak will be included in the kernel. These packs contain tweaks/settings that are not always optimized for our device, and some don't even work on Mini because they are not universal.
[Samsung Galaxy Mini] RicardoQ5:
Alin.p, when you say "mod" you don't mean interface mods, right? Like, mods to systemUI and stuff like that.

Btw, as far as I see, 2.0 will be real BadAss ;)
[Samsung Galaxy Mini] alin.p:
Of course not. I'm talking about scripts that tweak the kernel files (those located inside /sys /dev and /proc). Layout mods target the /system partition thus are always allowed. The same for odexing, it is allowed because it changes the system, not the kernel.
[Samsung Galaxy Mini] Charlie:
did you overpassed all the problems??what are you working on?is kernel ready?
[Samsung Galaxy Mini] alin.p:
Everything's working, if there are any bugs that I'm not aware of, they will come out in the final tests. I'm working on the app right now.
[Samsung Galaxy Mini] Dark Passenger:
can we get a possible eta then...like will it be in days or weeks or god forbid months.
[Samsung Galaxy Mini] swat4samp:
Man..u r killing me with frequent leaks ;)...just release the goddam kernel..
[Samsung Galaxy Mini] crullick:
you tell them man!

and for the other *****es <>> feel free to refer them to the angry serbian jew; i'll take care of it/them

sometimes i feel overprotective :D

p.s. BTW is there any company you're planning to work for \ i can buy shares now when they're cheap?
[Samsung Galaxy Mini] alin.p:
I can't estimate anything. I have no idea how much work there is to be done, until I finish it :p

I understand that some of you are impatient but please bear in mind that I work from 5 in the morning till 8-9 in the evening for my family's farm, and I only have 2-3 hours of free time that I spend on working on this kernel instead doing my kind of a big list of "real-life" hobbies.

My patience is limited too, try not to waste it with comments like this one.

Always nice to see guys like you around here :))

I seriously hope I won't be the slave of a company in the future :p maybe I'll make my own company so I can recruit my own slaves :-?
[Samsung Galaxy Mini] Charlie:
How old are you [MENTION=4525074]alin.p[/MENTION] ?? Because im glad with your work:good:
[Samsung Galaxy Mini] alin.p:
19 and counting... :)
[Samsung Galaxy Mini] ehsan-black:
thanks for spending your own free time for us! we are REALY appreciated :victory:

and is you git updated with last changes?

again thanks :o
[Samsung Galaxy Mini] hsay:
[MENTION=4525074]alin.p[/MENTION] could you please shar the deodexed version of your lenio theme?

thanx...
[Samsung Galaxy Mini] alin.p:
Not yet. I still need to fix one little bug. But after I finish the app. I'm having big trouble with this because the original app sources are pretty messy

I think I still have a backup of the theme. I'll send you the apk in a PM when I get home.
[Samsung Galaxy Mini] Dark Passenger:
Hi can you add support for android 4.3 to badass v2.0 dont know if you tried it or what you though of it but yajnab managed to make it pretty awesome.:good:
[Samsung Galaxy Mini] alin.p:
Sure. I'll do this tonight. :)
[Samsung Galaxy Mini] Dark Passenger:
Thanks (I pressed it too!)

hope you finally finished the work on the kernel or still ideas come pouring out of your brain.:-p
[Samsung Galaxy Mini] ast00:
And how is the app going?
[Samsung Galaxy Mini] alin.p:
I'm still waiting for Benee to release the sources of his KernelControl app.
[Samsung Galaxy Mini] Grawrz:
Hey alin.p,

I think there's an issue with badass kernel 1.9.2 and hotspot/tethering. I've installed a few ROMs with it baked in and I couldn't tether or have someone connect to my phone via my hotspot. Whenever I flash the plain 10.1 by rohan I don't have this issue at all. There's a possibility I could be wrong though, but I just wanted to let you know. Tethering and wifi hotspot are very important features to me since I don't have a wifi router at home.
[Samsung Galaxy Mini] deathdekid:
my cpu governor always revert back to ondemand after taking a picture. any solution? sorry for my english...
[Samsung Galaxy Mini] alin.p:
Tethering works, I didn't modify the Wi-Fi drivers. If tether works on stock, it should work on Badass too. Try using a third-party app for tethering.

This problem is gone in 2.0.
[Samsung Galaxy Mini] A_U:
could u throw some light on the the touchscreen response tweaks, and how it works ? seems to be user controllable by ur app ? thanks :)
[Samsung Galaxy Mini] alin.p:
I raised the priority of the Synaptics workqueue, forcing the CPU to spend a little more time on computing the touches. It's basically "renicing", but done low-level and definitive, which is not possible to be done by an Android user.

The new Native Multitask Enhancer really does magic for the performance. To be honest, even I am amazed how smooth is the UI right now, even when heavy multitasking. I can't understand why didn't anyone think about this until now.
[Samsung Galaxy Mini] ast00:
Mayve because developers would never do thia. But you do it as a GENIUS developer!
[Samsung Galaxy Mini] Sherpu:
Now I really can`t wait to see what the 2.0 version will do. I have big hopes for it :)
[Samsung Galaxy Mini] XDRdaniel:
You make it sound so complicated, this... whole kernel developing thing...

Is it so?
[Samsung Galaxy Mini] alin.p:
Well, everything is complicated until you understand it.

When I started kernel developing, I was just roaming around the source files with no clue about what I should do. But if you know C programming, everything becomes easier. So I started looking through some components source (e.g. LMK) and trying to understand their algorithm so I can modify it to my needs. After I have seen how these modules work, I started writing my own modules (Zen, kNative, PerformanceControl, Sweep) to fill the gaps for our low-end devices. Everything seems easy to me right now, but it took some months to become this easy. It is difficult until you start.
[Samsung Galaxy Mini] Jeeko:
Hey alin, my pc is broke, this is the why I couldn't wrote in this forum.

Anyway, how it goes this kernel? I seen a looot of new features :D
[Samsung Galaxy Mini] alin.p:
The kernel is ready. I'm in the testing stage right now. I'm trying to reach some Android-experienced owners of Galaxy Fit and Ace to test the kernel on all 3 versions of Android (4.0.4, 4.1.2, 4.2.2) while Benee finishes the app sources. I hope all this won't need more than week.
[Samsung Galaxy Mini] Jeeko:
I seen in your Sweep commits that the latency from touch to response is really small..... it will really that fast? :D

Anyway I hope that Benee releases his sources too
[Samsung Galaxy Mini] alin.p:
Yeah, 10 ms. Almost instant.

There is a problem with the proximity sensor though. In bright sunlight, the infrared sensor can be saturated and can take wrong readings, forgetting to trigger the function for turning on the touchscreen. This happens very rarely, and only when the screen is off(obviously), and can be easily repaired with a hover over the proximity sensor. But it is annoying sometimes.

Benee did a great job on the plugin interface for his app. He deserves a lot of thanks. Press the Thanks button on his thread here: KernelControl

This won't hurry the release, but show him that his work is widely appreciated.
[Samsung Galaxy Mini] Rajesh_m:
Pressed the thanks button on the thread you mention,and on your post too :) you both deserves a looot of thanks :)
[Samsung Galaxy Mini] Rajesh_m:
[MENTION=4525074]alin.p[/MENTION]: will you be adding any sound tweaks into your kernel? I am not sure whether it can be possible or not, just wanted to confirm :)
[Samsung Galaxy Mini] alin.p:
This is not possible. We don't have Codec drivers like the Nexus or S2 have.
[Samsung Galaxy Mini] swat4samp:
So will u release kernel for testing for fit :o
[Samsung Galaxy Mini] alin.p:
Nope. I'm doing the testing in private. I don't want to release Beta versions.
[Samsung Galaxy Mini] :
Alin.p in the kernel 2.0 will increase performance ?
[Samsung Galaxy Mini] A_U:
No. it will brick ur phone. :)
[Samsung Galaxy Mini] ast00:
But of course not ours :p
[Samsung Galaxy Mini] alin.p:
Well of course. The difference in performance is huge on 2.0. But I made almost every performance-dependant parameter controllable in the app. So the performance will depend a lot on the user settings for the KernelControl app.
[Samsung Galaxy Mini] Masrepus:
Will u maybe tell us the best settings for performance at release, alin? :)

---------------------------------

Phone : Samsung Galaxy Mini S5570

OS:

•AOSP ICS Touchwiz V5 by A_U

•Android 4.0.4

•Baseband XWKS2

•Kernel: 2.6.37.6 Badass v1.9 by alin.p

•Recovery CWM v4.0.0.5

Mods:

PureAudio, Mounts2SD, ODEX through Universal ODEX script, AdBlock by AdAway

---------------------------------

Gesendet von Tapatalk 4 beta
[Samsung Galaxy Mini] alin.p:
Yes, I will make the optimal settings for CM9.2 as default, and post some good settings to use on CM10.1 in the OP. Damn, I can already picture how huge the OP thread will be..
[Samsung Galaxy Mini] Masrepus:
Ya, but huge op for huge bunch of great features ;)

---------------------------------

Phone : Samsung Galaxy Mini S5570

OS:

•AOSP ICS Touchwiz V5 by A_U

•Android 4.0.4

•Baseband XWKS2

•Kernel: 2.6.37.6 Badass v1.9 by alin.p

•Recovery CWM v4.0.0.5

Mods:

PureAudio, Mounts2SD, ODEX through Universal ODEX script, AdBlock by AdAway

---------------------------------

Gesendet von Tapatalk 4 beta
[Samsung Galaxy Mini] piterdemon:
Just waiting for release of Your kernel alin.p ... Its will be awesome . Do You plan to make it for cm 10.2 too ?

Wytapatano z Ainol Novo 7 fire CM 10.2
[Samsung Galaxy Mini] A_U:
make notes of all the features, changes, fixes and derps in a separate text file :p

when updating OP, just copy paste ;)

i do the same, in case i have made many changes in my roms..
[Samsung Galaxy Mini] alin.p:
Maybe, I'm not sure if it will work. I ported the CM10.2 changes, but I didn't test them yet.

Very good idea. I tend to forget a lot of things when writing the OP.
[Samsung Galaxy Mini] Grawrz:
Just posting a follow up on the tethering and wifi hotspot issue I posted a few days ago. I tried NextLight's Halo ROM and used it for a day with the ROM's kernel and it was working well. Then I tried to use Badass Kernel 1.9.2 and it worked well too! So I don't know what caused the unknown network issue @_@ It could be the ROMs that I used or it could be something else entirely (maybe my pc was acting up that day?)

TL;DR: nothing wrong with the Kernel and tethering/wifi hotspot :)
[Samsung Galaxy Mini] jayOOMjay:
alin.p, are you planning that rom based on cm9.2 along with the kernel as you have mentioned earlier in lenio's thread ?

Thanks for all your contributions :good:
[Samsung Galaxy Mini] alin.p:
I worked day and night for the kernel. I didn't have time to work on the ROM. I'll probably start the work after the kernel is released. Probably..
[Samsung Galaxy Mini] mickey4398:
better make 10.2 ROM with new kernel :D
[Samsung Galaxy Mini] jayOOMjay:
cm9.2 is the best intermediate between JB and GB. We cannot make perfection in 10.2 coz of our hardware.

so alin.p + badass kernel + cm9.2 will be a promising combination :D
[Samsung Galaxy Mini] ShadowFax:
Agree
[Samsung Galaxy Mini] aamm95:
I'm agree too. :good:
[Samsung Galaxy Mini] lollipop:
not agree coz cm 10.1.4 (odexed) with badass is working well :laugh: and as we know that cm10.2 is better that cm10.1

a cm10.2 rom will be perfect :)
[Samsung Galaxy Mini] Charlie:
[MENTION=4525074]alin.p[/MENTION] you said every tweak like pure performance and etc that is working will be included at the kernel.But if after a month releashed a better more powerfull tweak like "BEST performance(just a name)" from another developer we wont flash it cause maybe this will missbehave with your kernel.My opinion was to create a great kernel without these "pure"performances or something.Just a great kernel with s2w and this kind of functions and the modt important a CLEAN kernel.So the mini's owner will decide about zips like pure perf.Thats my opinion have a nice day:beer:
[Samsung Galaxy Mini] ast00:
Good point, but I guess there is no possibility of making a better script. Extending the hardware limits even further can't be done by init.d. That's just my opinion.
[Samsung Galaxy Mini] alin.p:
See that text in bold? There's no such thing. Scripts and mods with cool names will appear all the time, but I assure you 100% that there will be nothing new. All the tweaks in those scripts are simply modifying some kernel parameters, and I, as a kernel developer, already know about every parameter than can be modified by a script or user intention. So just take my advice and don't flash any cool name on my kernel. I won't consider any feedback/bug report from a user who flashed something I already told not to.