yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Mini] crullick:
if you're a true believer and followed these 90 pages - as i am/did; you'd already know that alin.p is far from other devs >> in every +sense

his is the only kenel i used longer than "just to see if it works what it says it does" and throughout various roms << simply because it's +++ on all three questions

above all, alin.p is the rare one around here almost 24/7 for any kind of support, frequently not even related to his work

i know this sounds lame as a pepsi commercial, but....

show some faith man :fingers-crossed:
[Samsung Galaxy Mini] Charlie:
Ok,i think im happy with your answer.Im not an expert at android dev,so sorry for my inconvenience.Thank you [MENTION=4525074]alin.p[/MENTION].

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

Hahaha...:good:
[Samsung Galaxy Mini] prafiles:
I agree all these usually are scripts that change parameters as per the hardware statistics, as I got to know more and more I switched to manual settings and it worked good. But then I started to believe that these parameters should be changed dynamically to adjust to our needs, and as I was learning on how to develop android, came [MENTION=4525074]alin.p[/MENTION] and thus I simply started using his version. :D You're certainly better in one aspect, you didn't just port or make things compatible, you also became creative with it.

P.S. how do you debug a kernel in development that has no debugging code? Do you add logcat statements just where you expect the error can come?
[Samsung Galaxy Mini] alin.p:
Well, to clarify something, logcat is for the Android system, in kernel development we have dmesg which prints messages from the printk functions.

There's no best practice in this, each dev has its own way of doing it.

For example, if the module/driver I want to debug doesn't have more than 40-50 functions, I usually call printk on every function, right after all the variables have been declared. Something like printk("function called: %s/n", __func__); (you can simply copy-paste this inside every function, after the variable declaration. The __func__ returns the name of the function in which the printk is called). This way I can see inside the dmesg which was the last function called before the error has occured. Then I go to that function in the code and try to find what caused the damn error.
[Samsung Galaxy Mini] Charlie:
[MENTION=4525074]alin.p[/MENTION] about the bootsplash you said that you will use the badass logo!Its great!And for background colour prefer black,cause white like V1.9.2 is a little disturbing :P
[Samsung Galaxy Mini] alin.p:
If you prefer black, you will have to repack your own boot.img with the black logo. Everyone has different preferences, and I prefer a light background.
[Samsung Galaxy Mini] ehsan-black:
hi alin ! i want to compile your kernel but in compiling i get this error:

/bin/sh: lz4: command not found

i used this tool chain:

https://github.com/alin23/Linaro-Toolchain-4.8

but you use " android/toolchain/arm-eabi-4.4.3 " .

is my problem caused by tool chain? if yes , could you please share your tool chain? and if not what is my mistake?

i use fedora 19 64-bit.

thanks in advance :)
[Samsung Galaxy Mini] lollipop:
Alin said that the kernel is ready and it's in testing stage...so waiting is better :)
[Samsung Galaxy Mini] ehsan-black:
i know. i'm just curious about kernel building :D
[Samsung Galaxy Mini] alin.p:
Don't compile with 4.8, as it breaks the camera driver and causes reboots. Use 4.4.3, it works perfectly. But the problem is not caused by the toolchain. You need to have the LZ4 compressor binary installed inside your linux distro /bin/ folder. I would send it to you, but it would be useless anyway because without my ramdisks you can't make the kernel boot. I'll upload the ramdisks on GitHub at the release.
[Samsung Galaxy Mini] ast00:
Lol you basically disabled kernel compilation before release.
[Samsung Galaxy Mini] alin.p:
It was not on purpose. There are 6 ramdisks per each device that I have to modify and I'm still uncertain about some additions, so I can't upload them as long as they are still incomplete.
[Samsung Galaxy Mini] mickey4398:
android 4.4 will be relased in October :D
[Samsung Galaxy Mini] ast00:
And we won't get it before December.
[Samsung Galaxy Mini] prafiles:
I am really sorry I meant dmesg only that just came out wrong. :D but yes that was the function I was looking for. :D

Any book or source you'd like to recommend in general for Linux kernel or kernel module programming?

Oh my! Just became a senior member. :P
[Samsung Galaxy Mini] alin.p:
So you become a Senior after 100 posts? That explains how I got that title..

Learn C programming, this is the start that everyone should take. To engage in kernel programming, it's better to just use the resources you find on the internet. A book is too full of "other sh*t", while on the internet, you can search for a specific topic and learn about it in much less time. Module programming is very easy, as long as you have basic C skills. But what you do with that module, depends on what that infinitely creative mind of yours is capable of.
[Samsung Galaxy Mini] NqX:
Hi alin.

Could you give us some information when we can expect a new version of the kernel. ?

Sorry for asking, but I can't wait.

Best regards and thanks for the great job! :good:
[Samsung Galaxy Mini] prafiles:
I know C and I couldn't agree more to you. I was trying to find any good book but failed to do so. I guess we CS people have move beyond the era of books. :D
[Samsung Galaxy Mini] alin.p:
I'm solving some issues with the new modules right now and will probably finish the app in 3-4 days. That's if no others problems arise.

Books are my first choice too, but in this domain, books are good only if you want to specialise and probably get a job in this kind of programming. :) for kernel hacking, the internet resources are just enough.
[Samsung Galaxy Mini] Jeeko:
You're saying that Benee has released his app's sources? :D
[Samsung Galaxy Mini] A_U:
interesting changes in code..

edit- could u see some of the latest commits here

might be useful..thnx [MENTION=4525074]alin.p[/MENTION]
[Samsung Galaxy Mini] alin.p:
How come I didn't get a notification for this quote?..

Well yea, Benee's app is stable and the plugin API is working too. But I kind of changed my plans when a new source came out these days. I always wanted to use AOKP's Performance Control as the base, but I didn't like the look. A week ago, someone released a modified Light-themed version of this app, and the sources too. So I might use this in the end. Still not sure though, I have to test both apps first.

Thanks for tuning in :)

Yea, those commits are very useful, but unfortunately, not for our device. We don't get uninitialized jinodes, nor dead CPUs, as we have only one core. So those commits are just for being safe in extreme situations when weird things happen inside the code.

That Bluesleep commit seems interesting, I never checked to see if we have wakelocks on enabled Bluetooth.
[Samsung Galaxy Mini] Charlie:
So [MENTION=4525074]alin.p[/MENTION] the test you say for both apps will late the releash date??
[Samsung Galaxy Mini] alin.p:
No, there will be no delay added because of the new app. But I do have less free time because of the college, so this might add a bit of delay.
[Samsung Galaxy Mini] A_U:
[MENTION=4525074]alin.p[/MENTION] thnx for the info..

and can i ask the naming convention of the branches in ur git ? bfs, cfs :confused:
[Samsung Galaxy Mini] alin.p:
badass-cfs is the branch with the original Linux task scheduler. CFS stands for Completely Fair Scheduler.

in badass-bfs I replaced CFS with the better BFS (Brain F*ck Scheduler) by Con Kolivas. I'm using it on my Ubuntu kernel as well and I'm amazed of it's smoothness all the time.

If you are wondering what the heck is a task scheduler.. in a few words, it is that part of the system which manages tasks, processes, apps, and decides which gets more priority, which needs to be frozen etc. This is where the magic happens, and the smooth user experience begins. With BFS, the scrolling is smoother than ever, and the lag between app switching is completely gone (if you have enough free RAM, of course). It is a big improvement, but it took me a lot of tries to get it fully working like this.
[Samsung Galaxy Mini] prafiles:
I am kind a researching with my professor on Linux kernel security. Thought you might have some sources in module programming or like wise. But thanks as always. :)
[Samsung Galaxy Mini] Jeeko:
[MENTION=4525074]alin.p[/MENTION] can you please share you Lenio.apk theme for CM10.1? Thank you so much :D
[Samsung Galaxy Mini] Dark Passenger:
Hi ,

so i reaaly want to abandon Gingerbread for good and move over to 4.x

so far my options are 4.0 and 4.2 since there is 0% development for ics am looking to 4.2 or if camera is fixed 4.3(only bug camera).

now my reason to write this long sob story here is that i wanted to know what you feel for our devices on a technical level can be a better option a slightly buggy ics or an underdevelopment 4.2(I hear that 4.3 is better that 4.1 +).

keep in mind all that the usage is massive browsing(on Wifi) and maybe minor gaming and video playback and other light usage(chats, calls).

of course there is always the dream of KitKat:)

maybe i failed to mention my point in all this or lost it along the way but simply put i want to run a rom higher than gingerbread using your kernel and for that rom to work smoothly.So what are your recomendation(rating per rom will do to).

Thanks,

Dark Passenger

---------- Post added at 08:50 PM ---------- Previous post was at 08:39 PM ----------

also bfs 's latest version is 0.4.4.1.

yours being 0.3.6.3.
[Samsung Galaxy Mini] Charlie:
Hi, my opinion is that yeah ics is great(aosp by paul) but its a bit old.The best for me would be an aosp again(have great ram managment) but now on jelly bean.Will it be 4.1?4.2?4.3 whats the point?If we compare them we can find which is faster and ceate an aosp with of course badass kernel.So mini will be happy :D

Oh and for the features that aosp dont have,because many of you want them(cm features),we can have them by flashing zips or something and evreyone do the customization he want!
[Samsung Galaxy Mini] alin.p:
This is an old link of the theme, but it is the only version I've got: Lenio.apk - 536.13 KB

I know what is the last version of BFS. But every new version of BFS contains mostly adaptations to the mainline kernel. So for everyone to understand why I implemented 0.363, is because every BFS patch above this version is for kernels higher than 2.6.37. I updated the core to 2.6.39 but there are still some elements that are impossible to update the dirty way, and that are used by the scheduler. So any other version higher than 0.363 will simply not work, even this version was damn hard to implement.

Honestly, I can't use anything higher than 4.0.4 for the simple reason of user experience. I never tried ICS before installing Jelly Bean. And I was amazed to see all the new features and the beautiful look of JB. But I was getting sick of the lag I get because the JB code is too complex for our CPU and RAM. So I gave ICS a chance. I would never go back to Jelly Bean. Maybe on 4.4 Android will try to optimize the code, instead of dirty patching it.. This the only way we could get a smooth ROM above ICS.

So for ICS you have three main choices.. and their genetically modified siblings (cooked ROMs).

1. AOSP

This is by far the smoothest 4.0+ ROM you'll try. But, it is vanilla, so it is missing a lot of useful features. If you don't care about the CM/AOKP features, give AOSP a try.

2. CM9.2

This a very good and really organized ROM. Used a self compiled version for 3 months without ever flashing another ROM. My only complains are flickering lockscreen (but I got rid of this by disabling the lockscreen, as S2W plus Pocket Keyguard rendered the lockscreen useless), long boot time (I solved this by compiling my own version of CM9, though I still have no idea how I did it), statusbar contents dissapearing from time to time and reappearing after 30-40 seconds (this is what made me try the next ROM).

3. AOKP

Erik's build of AOKP ICS is purely awesome. Every AOKP feature is fully working, the ROM is smoother than CM9.2 if you do the right choices in terms of apps (e.g. lighter SU binary without RAM-consuming app to control it), and I love that the look is more controllable than on CM9.2. The only real bug which is present in all the ICS build is the audio driver. But I have fix for that if you ever need it. This is the ROM I am using at the moment, and it is flawless.
[Samsung Galaxy Mini] Charlie:
Can you provide us that fix?
[Samsung Galaxy Mini] alin.p:
Here: AudioHWUpdate.zip - 365.24 KB

Just flash it.
[Samsung Galaxy Mini] stety:
alin.p: You write that JB is not for our hardware but 4.3 is nejladší JB what I saw. I want to ask you if you have used the galaxy mini JB 4.3?

Because it is much smoother than the 4.2 and 4.1. Not so performance as ICS, but it's pretty worthy performance. In Jb 4.3 Google has done some optimization code, or why the reactions are more rapid and better multitasking?

If you can please support your kernel on JB 4.3
[Samsung Galaxy Mini] Masrepus:
Ahm [MENTION=4525074]alin.p[/MENTION] the aokp by erik i found seems to be cm 10.1?? Which one do you mean, if it has ics?

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

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:
I didn't try 4.3. I never try ROM's that don't have all the features working. I want to use my Mini as a smartphone, not as a testing device. But I have seen the code changes from 4.2.2 till 4.3, and there's 3 percent to nothing done for low-end devices. Mostly stability and security modifications (e.g. SELinux support). It may be a placebo, thinking about how many rumors everybody heard about low-end optimization.

Here, on Erik's blog: http://android.cas-online.nl/downloads/aokp/ics/
[Samsung Galaxy Mini] lollipop:
[MENTION=4525074]alin.p[/MENTION] :but as erik said that aokp ics need to fix blootooth and some ldpi layout bugs

is that right :)
[Samsung Galaxy Mini] alin.p:
Bluetooth works, I just tested it before replying to your post. Maybe it doesn't work on stock kernel, but I am using Badass and I assure you it works. And I don't see any layout not LDPI resized. There might be something that I didn't stumble upon yet, but as far as I could see, everything is LDPI resized.
[Samsung Galaxy Mini] A_U:
i think i will turn 40 when the kernel is finished :p just kiddin..

so alin y not add this thread in DEVB ?

feature req, bug reports etc..will be useful when u use 2.0 ;)
[Samsung Galaxy Mini] ashishkotnala29:
I am a bit (5 months :p) outdated in the development of Galaxy mini. Can you please give link to AOSP? As I can see there are two versions, one by Paul L. and other by Jeeko. Which one is more stable and updated? Specifically which one are you talking about? Is your kernel recommended over AOKP and AOSP both? In Erik's build of AOKP milestone 6 are all the bugs removed such as camera, video recording, GPS, bluetooth, etc. Any other minor bugs? Please explain clearly as I have told you my situation of being outdated. Sorry for so many questions but please try to understand me. Thanks. :)
[Samsung Galaxy Mini] alin.p:
The app is more than half done so we're really close to the release. I'll add the thread to DEVB then (if I find out how to do it) :) Thanks for the suggestion.

There's no noticeable difference between the two AOSP, use whatever you want. I didn't have time to use all those features on AOKP ICS, I just flashed it two days ago, but the base is the same as CM9 so everything should work. Minor bugs.. only what I've already enumerated above: Audio driver problems, which can be fixed with the zip I provided earlier.
[Samsung Galaxy Mini] swat4samp:
What exactly do u mean by audio driver problem? Is that related to notification, ringvolume and media or with low incall volume in phone? It works with fit too right? And is it only for AOKP or for CM9 too?
[Samsung Galaxy Mini] Charlie:
Its for all cm9,aosp,aokp.I tried it at aosp and it worked!The low incall volume bug dissapeard!I dont know if this works on fit.
[Samsung Galaxy Mini] alin.p:
Yes it is universal for MSM7x27 phones (Mini, Fit, Ace, whateverelseIcan'tremember). The zip is basically a bundle of the latest Androidarmv6 audio drivers and one forward-ported driver from CM9.1 for A2DP, the latest CM AudioEffect libs, and a fixed AudioFilter.csv file.

Here is the updated zip: AudioHWUpdate.zip - 366.55 KB

I forgot to add AudioFilter in the other zip.
[Samsung Galaxy Mini] Rajesh_m:
So flashing this zip increases overall volume of our mobile than just fixing the low incall volume bug? :)
[Samsung Galaxy Mini] stety:
I know you say that there are almost no major changes in the code, but once you have the time and inclination to try a JB 4.3 and you will see that it is much smoother.

But it's weird.

How can a 4.3 smoother when there are no major changes in the code?

Will your kernel (2.0) to support JB 4.3?
[Samsung Galaxy Mini] alin.p:
I'm happy with ICS for now. I don't know if Badass will support 4.3. Like I said, I didn't try 4.3 yet.
[Samsung Galaxy Mini] Jeeko:
Wich is the

latest

AOKP ICS (Milestone) now? Can you link me the thread?

(the one of The Wisp hasn't a working download link) :D
[Samsung Galaxy Mini] alin.p:
The latest AOKP for Mini is Erik's build. It doesn't have a separate thread, he just announced it in a post on his AOKB JB thread and posted a link to his web blog. You'll find it right here: http://android.cas-online.nl/downloads/aokp/ics/
[Samsung Galaxy Mini] ast00:
You said that you have an audio fix or what. Can you make a flashable zip? I never tried this AOKP ICS, but I would like to do so.
[Samsung Galaxy Mini] Rajesh_m:
You must be blind! ;) or are you talking about any other audio fix than the low incall volume? alin already shared the audio fix here!
[Samsung Galaxy Mini] alin.p:
There is a link 6 posts above. Don't just skim the posts, read them before asking something :)
[Samsung Galaxy Mini] Android Daymon:
It's not working on galaxy Fit...could you make a patch for GFit too???
[Samsung Galaxy Mini] alin.p:
Why do you people put so many question marks???????

One is enough to make it clear that you are asking something. Sorry man, it should work on Fit too, as Mini and Fit have the same audio hardware. If it doesn't work, I can't do anything.
[Samsung Galaxy Mini] rghvdberg:
AOKP ICS

Tried aokp ics (aokp_tass_milestone-6 (249) ) from eric , with audiofix but without badass kernel.

Did a full wipe , even format /system, but it performed horribly :eek: . Very unresponsive.
[Samsung Galaxy Mini] aamm95:
I've installed it too but with badass and it works fine with the exception of it seems that not supports ext4 partitions on sd-card. I've tried with int2ext+, a2sd, and my ext4 partition has been converted to ext3 type partition but internal data isn't increased...

May be this rom hasn't ext4 support?

:(
[Samsung Galaxy Mini] rghvdberg:
I had link2sd installed and that worked ok, ext4 partition dectected and used just fine.

Could be that link2sd is the cause of the poor performance although I doubt that.

We should open an AOKP-ICS discussion thread.
[Samsung Galaxy Mini] swat4samp:
I m really sorry for off topic but he's right, ur audio zip doesn't work on fit. No audio after flashing zip. What might be the problem and sorry for bothering once again :o

Edit: Thanks to [MENTION=4523093]Venkatesh[/MENTION] , there are audio.primary.tass.so and audio_policy_tass.so files in lib/hw and that might be the reason that it doesn't work on fit. May i know from where did u copy that particular file? I looked in CM9 ROM but there isn't such file.
[Samsung Galaxy Mini] alin.p:
Ah sh*t, I forgot about the names. You only need to rename those files, changing tass to beni.

For those having problems with sd-ext on AOKP, the ROM has a little problem with the init.d support. I will release the AOKP kernel with a small hack to fix this problem.
[Samsung Galaxy Mini] swat4samp:
Don't forget to update for FIT too :-d
[Samsung Galaxy Mini] Dark Passenger:
Off Topic

Hi can someone provide a mirror for AOKP ics by erikcas the latest version for fit/beni.

preferably via mediafire cause i really need some resumable support.
[Samsung Galaxy Mini] Rajesh_m:
Badass v2 landed! :)
[Samsung Galaxy Mini] XDRdaniel:
In original development section :D
[Samsung Galaxy Mini] malybru:
Mod Edit

Thread closed, by request of [OP]

malybru

Forum Moderator
[Samsung Galaxy Mini] L.E.D 26:
We are still away from cm7, but we are progressing.
[Samsung Galaxy Mini] alin.p:
The performance is equal or better if you use proper apps/tweaks. For example CM10.1 has a built-in Superuser but it is damn slow. SuperSU (app and updated binary) fixes any lag on that.

Second, the minfree values aren't tweaked for our device. You'll find proper values in the first post of this kernel.

Third, the system is bloated with "useless" apps (I say useless because the majority of users don't use them, not because they are bad). If you would like a list with what to delete and why, I can post it here.

Also a patched services.jar (framework file) can really help multitasking.

Might seem a lot to do but after having CM10.1 with CM7 performance, you'll never go back.

Quick tip: don't use any audio effects bloatware.

The only genuine things in audio effects department are:

1.Viper4Android

2.PureAudio

3.DSP Manager

4.Market equalizers or player built-in eq's

Beats, SRS or any other Sony/HTC audio effect won't work because we don't have them implemented in the kernel.

Sources: lots of flashing and debugging audio libs, AC!D, AwesomeBeats / seeing how these effects are present in HTC/Sony kernels and not in ours
[Samsung Galaxy Mini] alin.p:
Well psyke got 3.0 to boot on his Galaxy 5 so /data mounting works. I'm sure now, the phone has no chance to boot without this partition.

But maybe you are right in some way. Maybe it doesn't mount /data on our device.

Problem is (big problem) that I don't know what to fix. Everything compiles with even less warnings than 2.6. It just doesn't boot. I can't collect any debug either, the booting process doesn't even reach that part where it can write some debug messages.

So what I do now is blindly stupid trial and error. I need luck, a lot of luck to get this to work.

So.. wish me luck :))

Ah ****, double post. My bad :p
[Samsung Galaxy Mini] ast00:
Not exactly. It's not like stock kernel, but it won't make it CM7 like, because hardware makes it impossible. As TheWhisp said (I'm not quoting): A new ROM won't improve your device. And that's also true for kernels.

(I had to write this even after reading other's replies :p)

---------- Post added at 10:34 PM ---------- Previous post was at 10:32 PM ----------

DAFUQ? My thanks button disappeared. Maybe I reached daily limit? I don't think...
[Samsung Galaxy Mini] RicardoQ5:
Hey alin.p, If I'm not asking too much could you please tell us what you did to your ROM, which tweaks you have, etc.?

I've made my best but I can't seem to make CM10.1 run properly to use it daily(After some time it has wild freezes/ lags).