yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Mini] alin.p:
It still has the 1.9.2 history in the back, but the core of the kernel will be updated from 2.6.37 to 2.6.39 which comes with a lot of error and memory leaks fixing and optimized calculations inside the important algorithms.
[Samsung Galaxy Mini] the chros:
Can you release a version with enabled logs?
[Samsung Galaxy Mini] alin.p:
No. The logs can not just be "switched" on and off. I have put 1 or 2 full days of work into stripping the debugging to make the kernel code cleaner for the average user. It would be close to impossible to re-add the debugging code.

Sorry :p I need that feature too, but I'm too lazy to work 2 more days to add the debugging code, so I just flash a stock kernel when I need to use logcat.
[Samsung Galaxy Mini] the chros:
Ok, I'll use a stock kernel when i need to use logs :good:
[Samsung Galaxy Mini] alin.p:
Sweep2Wake working (finally!)

I have some good news for you :) I finally got Sweep2Wake working. The algorithm is in a really primitive state right now, but it works. I'm gonna use the next two days for finishing and optimizing the Sweep2Wake algorithm, then I'll release the 2.0 version of the kernel after I get the results from the testers.

Meanwhile, live like an instrument, and stay tuned :p
[Samsung Galaxy Mini] addyhardiana:
Very good news, can't wait :D
[Samsung Galaxy Mini] Masrepus:
Yes! :D

Gesendet von meinem GT-S5570 mit Tapatalk 4
[Samsung Galaxy Mini] :
Alin.p

Great news. Sweep2wake a very useful feature.

Is it possible to have something from this list:

logo2menu

logo2wake

pocket detection

Most wanted to me to pocket detection.

???

(only question)
[Samsung Galaxy Mini] alin.p:
Yes I am already working on that pocket detection feature.

But what logo are you talking about? We don't have a touchable logo :p

Anyway, we'll have a bunch of new features, and I have to make an app to control all these features. This may sound good, but this means that the release will be delayed a little :)
[Samsung Galaxy Mini] crullick:
man this sounds better than great; but you just made me too afraid to even mention Lenio....

ooops did it (again)

btw

i was always wondering - howcome badass doesn't fit in the "original" development?!

am familiar with the usual xda, blah, blah.... but

there's way too many emulation and modifications that you do <> that it gets far better than "the original" work

and i really hate seeing such a piece of work (lost) among other crap in this forum

thnx once again for your hard work offered to lazy bums, or stoopid ones like myself

you deserve a medal :good:
[Samsung Galaxy Mini] alin.p:
Unfortunately, Lenio will stay as it is. I'm working on a completely new ROM based on CM9.2 sources by Erik. Compiling the ROM from sources takes much more time than just cooking a flashable ROM, but the big advantage is that it allows for much more modifications.

Badass doesn't fit there because it is not.. well.. original(here, original means stock) :) It has too many differences from a stock kernel, only things compiled from original sources like pure CM, AOSP, AOKP or stock kernels fit there.
[Samsung Galaxy Mini] Masrepus:
Haha, touchable logo would be a nice do-it-yourself project xD (but too difficult :( )

Gesendet von meinem GT-S5570 mit Tapatalk 4
[Samsung Galaxy Mini] crullick:
when i wrote "lenio" i meant THE rom out of your kitchen :fingers-crossed:

you've almost completely described my state of affairs (favorite for quite some time now):

running a miui v4, based on erikcas cm9.2 with badass plug

hope you get some sleep too!

[nevermind my signature]
[Samsung Galaxy Mini] alin.p:
Yeah, I should go to sleep every once in a while..

I'm working hard to create an ICS ROM with unprecedented performance and look, so I really hope I will shock you somehow :D

I am glad that you like MIUI because my ROM will be light-themed too :

..nice signature, by the way. had a good laugh on it :p
[Samsung Galaxy Mini] Dark Passenger:
noooooo.....ooooo.....oooo!!!!
[Samsung Galaxy Mini] alin.p:
Sorry :p

We'll also have

- Sweep2Lock (this is an indispensable feature for those who have their power button broken)

- Sweep4[Home/Back/Recents] (this will hopefully solve the problem of not having soft keys, or enough screen estate for a navigation bar)

I have to create an application that will allow the users to turn these features on and off individually, and also customize some things like the keycode for Sweep4[insert_key_here] or the sensitivity of the gesture.
[Samsung Galaxy Mini] Rajesh_m:
Reallyyyyy happyy to hear that these features will be included in version 2.0 :):victory::D These are some nice useful features which most of us are waiting for( or atleast me ;) ) :) eager to try your kernel sir :) and as you said earlier,cm9.2 is as good as gb.. now my mini is running cm9.2 with your kernel, and everything seems perfect :):good:
[Samsung Galaxy Mini] deathdekid:
can u tell me which rom did you use?
[Samsung Galaxy Mini] Rajesh_m:
http://xdaforums.com/showthread.php?t=2226141

This is the rom which i use :)
[Samsung Galaxy Mini] prafiles:
You have made some specific changes to tass_defconfig concerning toolchain. I wanted to ask you which toolchain are you using? the one in your github? or 4.6.2?
[Samsung Galaxy Mini] alin.p:
I'm using the latest Linaro 4.8 from the official Linaro website. I made some modifications in the ARM Makefile to make it work. But don't compile the kernel until I release 2.0. It is unstable now because I'm in the middle of the work for optimizing the input and touchscreen drivers' algorithms.
[Samsung Galaxy Mini] A_U:
i bcame greedy and compiled it yesterdy nite.. :3

regreted da moment y i flashed it..:p still a wip
[Samsung Galaxy Mini] alin.p:
Yea, the Sweep functions are in the implementing stage right now. The optimizing stage comes after I finish implementing all the functions. So, better wait until I say it's stable. :)

I'm also working on a DoubleTap2[Wake/Play/Pause] feature right now, and I want to know if there are people who want this feature, or if there are more who want only the DoubleTap2Wake.

As you already know, after the screen-on timeout which you specify in the Android Settings (usually 1 minute), the screen goes off, and it waits another 5 seconds(lock timeout) before it locks the screen. If you turn on the screen before this lock timeout, you can return to what you were doing without activating the lockscreen.

The feature works like this:

- If the screen has been off for less than 5 seconds(or 10, I don't know exactly yet), you can double tap the screen to wake it without activating the lockscreen.

- If the screen has been off for more than 5-10 seconds, the double tap gesture will act as a Media Play/Pause button for your media player. I listen to a lot of music and this allows me to control the music without turning on the screen at all.

Of course, you can still wake the screen using Sweep2Wake.
[Samsung Galaxy Mini] Rajesh_m:
Does that mean double tap won't work after 10 secs?

Doubletap2wake is a great feature sir, it's very annoying when we are reading something and the display goes off and we have to press the power/home key to turn on the screen again. DoubleTap2Wake will be very useful :)

And i really hope these features wont drain the battery much :) afterall, battery issue is what we all concern about our little mini :)
[Samsung Galaxy Mini] A_U:
[MENTION=4525074]alin.p[/MENTION] ofcourse people like to have D2W..but its u who have to code :) so its upto u..and if u find it working good, then release..

btw i was wondering what would be the effect of battery with all these features depending on wakelocks..

experienced considerable drain in battery when using yesterday ur unfinished kernel..i know its unfinished but yet..
[Samsung Galaxy Mini] alin.p:
Exactly, double tapping the screen after the lock timeout has passed will not wake the screen, but act as a play/pause button.

The battery usage for these functions will be close to zero after I finish optimizing the algorithm.

For these functions to work, the Proximity Sensor and the Touchscreen handlers will continue working after the screen goes off. This might have a little impact on battery, but it will be minimal.

I have not finished implementing all the interrupts, so in the build you have compiled, the touchscreen and proximity drivers are on even when they are not needed. That's why you are experiencing battery drain.
[Samsung Galaxy Mini] arpitkh96:
Can u please release a stable kernel first.then add custom features:D
[Samsung Galaxy Mini] alin.p:
No, sorry. I would have to revert a lot of work to get a stable version without the new updates.

I want to release a final version and finally start working on the ROM.
[Samsung Galaxy Mini] Jeeko:
ah yess, you're a genius I knew you could do it :D:good::victory:
[Samsung Galaxy Mini] A_U:
this post gave me cancer -_-
[Samsung Galaxy Mini] arpitkh96:
Lol. I don't understand why?::D:confused:
[Samsung Galaxy Mini] A_U:
since he is already way too deep into implementing s2w and other gesture based features, its too hard to revert them back to wat the kernel was...so...:p
[Samsung Galaxy Mini] arpitkh96:
I was only saying that if possible firstly stabilize kernel then add those (not necessary )features .I have no idea about how long and difficult is that:)
[Samsung Galaxy Mini] Masrepus:
[MENTION=4525074]alin.p[/MENTION] double tap acting as media control is a genius idea man :D

I dont think d2w is really that necessary, but i think it wont hurt, and... if i am using this for a while i maybe dont want to miss that feature anymore, so... ;D

Gesendet von meinem GT-S5570 mit Tapatalk 4
[Samsung Galaxy Mini] alin.p:
Well, yeah, already having S2W makes DT2W pretty much unnecessary. But as Rajesh said, it is annoying to see the screen going off when you are reading something. The ability to wake the screen just by double-tapping it before it locks solves this problem.

I just finished implementing this two minutes ago after a long day of work, I think I deserve some sleep :p

I'll work on the interrupts and battery usage tomorrow.
[Samsung Galaxy Mini] Masrepus:
Nice to hear! :D

Well, as i said, we have to try that and i think it will be great, even if it is not THAT necessary, lets see :)

Gesendet von meinem GT-S5570 mit Tapatalk 4
[Samsung Galaxy Mini] Jeeko:
Well, I think that S2W is amazing but I think that DT2W is

awesome

I love the Nokia Lumia's DT2W feature, and porting this one to our low-end android device is a work worthy of a superhero :cowboy:

Anyway alin, in which part of the screen S2W works? (I have to train in the sweep motion) :)
[Samsung Galaxy Mini] alin.p:
At the release, I will post a full tutorial on how to use all the new stuff. S2W for example, works (by default) between the 120 and 200 pixels. The screen height being 320 px, you can have an idea on how big is the touchable zone. All this stuff regarding sensitivity will be controllable, so don't worry if you don't find the values suitable for your fingers.

DT2W works perfectly now, and the DT2PlayPause can be disabled if you want, making DT2W to work even after the lock timeout (5sec).
[Samsung Galaxy Mini] Jeeko:
ahhhh yeesss!! It's a really really really (x10) good notice!! :laugh:

Thanks, thanks, thanks!!!

And, latest thing.... how much these awesome features will afflict the battery life?
[Samsung Galaxy Mini] Rajesh_m:
Waiting to try your kernel :) hope you will release it soon ;) :)
[Samsung Galaxy Mini] alin.p:
Almost.. let's say.. zero. :)

I made sure that the touchscreen would be turned off while the screen is off and the proximity sensor is covered, and in these conditions, the CPU will go straight into a Power Collapse(Deep Sleep). Also the proximity sensor will be turned on only when the screen is off, or when the Android system needs it. All the other parts of the algorithm will not be executed until the loop for touch checking is broken, which was the default behavior anyway.
[Samsung Galaxy Mini] Lapnis:
i can't wait anymoooooooore!!! :eek:
[Samsung Galaxy Mini] Charlie:
Sir is release date close :P?
[Samsung Galaxy Mini] jamesmuking5:
This kernel is OVER NINE THOUSAND!!!!!
[Samsung Galaxy Mini] Jeeko:
Man, don't ask for eta... he can work a long time on this release, but I assure you it will be outstanding!
[Samsung Galaxy Mini] Charlie:
And one more question...your new rom will be smoother from aosp from sir paul or will be same smoothness but in cm9?Cause i like aosp much.But if your rom is faster i will prefer cm9:silly:
[Samsung Galaxy Mini] Jeeko:
CM9 has a loot of features that aosp doesn't have, so alin and a loot of other members prefer Ice Cream Sandwich by Cyanogenmod.

The next genius's rom will be a CM!! :)
[Samsung Galaxy Mini] XDRdaniel:
What do you think about 2 way call recording support? Can it be done?
[Samsung Galaxy Mini] Charlie:
I ask something else :p I ask if cm9 can be smoother than aosp from sir paul.I dont like so much mods and customizations...i like simplicity...But im waiting for the kernel like hell:cyclops:
[Samsung Galaxy Mini] Lapnis:
i was not asking for eta, i just was expressing my feelings.. :D
[Samsung Galaxy Mini] alin.p:
This is a hard thing to do as it implies working with driver addressing in Qualcomm's Hexagon DSP drivers. Our drivers are QDSP5 version and as far as I know, 2-way call recording was only done on QDSP6v2 and higher. If I find a source with 2-way call recording done on QDSP5, I'll try to replicate it. But I don't have the time to learn how to use kernel driver addressing right now.

CM9 can be a hell lot smoother than AOSP with the right system apps and a few compiling tricks. For example, I compiled a barebones su binary, stripped of everything but the superuser functions, in the end having only 5 kb. Unlike the other binaries full of unnecessary code, this one is instant. Also, disabling some debugging services in the code and compiling the libs in a different way can make the system much more snappier than AOSP.

But.. (again, there has to be a but) CM9.2 still has some bugs that I can't get rid of. They might seem small and unnoticeable, but when using the ROM daily, they become really annoying.

I'm talking about:

1.Low volume in call

2.Expanded status bar contents disappearing from time to time, and reappearing in a minute or so

3.Lockscreen flickering

Because of these bugs, I'll drop ROM development until a 4.3 version of Android comes to our Mini. I'm not hoping that this version will do magic, but it will be a little better than 4.2 in terms of memory usage. If I think it would be worth it, I'll start development on the CM10.2 sources.

I don't know how close is the release because not even I don't know how much work I still have to do. Bugs appear when I least expect them, and this causes delays.

I'm approaching the final phase of the Sweep development. After this, there is only one more thing to update, then I have to start working on the application for controlling all the new stuff that 2.0 brings. I hope you realize that all this work can't be easily measured in days :p
[Samsung Galaxy Mini] A_U:
i think u r talking about this - http://xdaforums.com/showthread.php?t=1978253

already someone did it already..u can just use his work by givin credits :)
[Samsung Galaxy Mini] alin.p:
Yes, that's the base I am using, but I deleted 70% of the code. It's not what _n0p_ has released to the public.

Anyway, I was not planning on releasing the binary as a work of mine, that's why I didn't talk about SimpleSU. :)
[Samsung Galaxy Mini] lollipop:
so there is no cm9 from you alin.p :(
[Samsung Galaxy Mini] Masrepus:
Oh no :crying:

Gesendet von meinem GT-S5570 mit Tapatalk 4
[Samsung Galaxy Mini] A_U:
oh no..i think u took my words wrongly man..i did not say u r using his work as urs..:)

i just pointed out that since the work is already done, u dont have invest ur time working on the binary..i was just trying to help :) sorry..
[Samsung Galaxy Mini] stety:
I look forward to 4.3 CM10.2 :)

Alin.p: So much work as you can not handle or robot :)

Thank you that even developing on an old but immortal galaxy mini.

I think that everything is all about optimization.
[Samsung Galaxy Mini] Rajesh_m:
How is ur work goin sir? :) it seems many here are impatient to try your kernel :) , and that includes me too ;)
[Samsung Galaxy Mini] A_U:
might take till the august ending..still he needs to work on the app for toggling options in his kernel and make some final optimizations in system interrupts for s2w and d2w..thats only a guess..and he plans to add more optimizations..

but hey, we all know hes very good at coding, so expect nothing less than a week atleast.
[Samsung Galaxy Mini] Rajesh_m:
Let him take all the time he needs, i m sure he will amaze us all with his kernel :)
[Samsung Galaxy Mini] XDRdaniel:
will you re-add 729 Mhz in badass 2.0?
[Samsung Galaxy Mini] lollipop:
please help.

what is the solution for low internal memory and witch is work nice with badass kernel :)
[Samsung Galaxy Mini] alin.p:
My god.. Guys, I hope you realize that I can't answer that many questions. I'll try to answer what I can :)

Oh, yeah. I misunderstood you :p Anyway, _n0p_ did a wonderful job on the binary, I just made it as simple as it can be.

I left it out because when overclocking to 770, the transition was not smooth enough because of 729 and 748. If you want, after the release, you will get a custom build with 729 enabled. Just ask.

What exactly are you talking about? Low RAM or low disk memory?
[Samsung Galaxy Mini] Masrepus:
I think he is meaning disk memory.

Im using mounts2sd from play store, its working wonderfully :)

Gesendet von meinem GT-S5570 mit Tapatalk 4
[Samsung Galaxy Mini] lollipop:
i mean low disk memory :)
[Samsung Galaxy Mini] Masrepus:
Ok :)

So then as is said, try mounts2sd

Gesendet von meinem GT-S5570 mit Tapatalk 4
[Samsung Galaxy Mini] Jeeko:
[MENTION=4525074]alin.p[/MENTION] whare I can find the Linaro Toolchain 4.8?

I need this for an S Advance kernel thanks :)

Edit: found!
[Samsung Galaxy Mini] alin.p:
Right here. :)

The kernel has nothing to do with the disk memory.

You can get more free memory by:

1.Deleting the apps you don't use (which I strongly advise, so your RAM doesn't get cluttered with useless background apps)

2.Using App2SD or any form of this script, to move your apk(only your apks) to an ext4 partition on your sdcard.

3.Odexing your system

4.Deleting garbage data collected by the Android system using apps like SDMaid
[Samsung Galaxy Mini] Charlie:
Delete this post.
[Samsung Galaxy Mini] A_U:
is that supposed to happen ? :eek:

In file included from arch/arm/mach-msm/include/mach/board.h:22:0,
from arch/arm/mach-msm/io.c:30:
include/linux/input.h:13:30: fatal error: uapi/linux/input.h: No such file or directory
#include <uapi/linux/input.h>
^
[B]compilation terminated.[/B]
make[1]: *** [arch/arm/mach-msm/io.o] Error 1
make: *** [arch/arm/mach-msm] Error 2
make: *** Waiting for unfinished jobs....
[Samsung Galaxy Mini] Charlie:
Sir [MENTION=4525074]alin.p[/MENTION] if you dont plan to create a cm9 due to bugs why you dont take aosp ics by paul and make the best aosp stable fast smooth rom for mini?

Its just my opinion:D
[Samsung Galaxy Mini] alin.p:
Ah sh*t. I forgot to add that file to the git repository. I just added it but I can't commit yet because I am in the middle of the work on something else.

It would be a good idea, but AOSP is missing some CM9 functions that I can't live without. Like long-press volume to skip music or the performance settings. So I'll stick to CM10.1 for now until CM10.2 comes out.
[Samsung Galaxy Mini] A_U:
its ok..i will compile later..:)
[Samsung Galaxy Mini] Charlie:
Ok!:good:
[Samsung Galaxy Mini] A_U:
[MENTION=4525074]alin.p[/MENTION] how about this feature ?
[Samsung Galaxy Mini] Rivaz:
[MENTION=4525074]alin.p[/MENTION]

In your next rom will you include HALO?

It's a very awesome feature.

I see someone on mini forum who make this work's on cm 10.1.
[Samsung Galaxy Mini] alin.p:
I already made every Sweep feature completely controllable. For example, Sweep2Wake has a sensitivity factor which the user can adjust to make the Sweep distance shorter and the Sweep zone in the middle of the screen bigger, or viceversa. I'll talk about all the adjustable parameters at the release.

If I will find a good base to work on (perhaps CM10.2), I will look into Halo. :)
[Samsung Galaxy Mini] piterdemon:
Alin.p You can make own app to control sweep gestures and add it to google play or include to package with kernel :)
[Samsung Galaxy Mini] alin.p:
That's what I wanted to do anyway :p I already talked about this more than a few times. But I can't release it on Google Play. There is a 25$ fee to pay when creating a developer account on Play.
[Samsung Galaxy Mini] A_U:
but once people install ur app, wont u get money for that ? i think google pays for app installs for every milestone sorts ?

dont know exactly how it works..
[Samsung Galaxy Mini] alin.p:
No. :)

A developer gets money only if:

1.Someone buys his app (paid app, not free.. obviously)

2.Someone donates or buys a donation app addition

3.Google AdMob ads (which I hate so much that I wouldn't include not even if a hitman points his gun at me. yep, that much I hate ads)

4.In-App monetization (buying parts of the app, or add-ons, after installing that particular app)
[Samsung Galaxy Mini] Spincervino:
I have a little request to be done:

When you're done with everything, a little fancy thing you could do, is change the kernel version lines in phone's info..

The 3 lines of geeky stuff isn't worth the fanciness of seeing "Badass Kernel 2.0"

That, in my opinion would be awesome! :D And since you're making the app, I think it wouldn't be too hard to change that meanwhile! ;)
[Samsung Galaxy Mini] lollipop:
+1:laugh:
[Samsung Galaxy Mini] Charlie:
+1:good:
[Samsung Galaxy Mini] Jeeko:
Yes you will see something like this :) I assure you
[Samsung Galaxy Mini] alin.p:
Yes, that is already done (somewhat). You won't see written exactly "Badass Kernel 2.0", but the new "2.6.39.1" and "badassv2" will be present in the version lines.
[Samsung Galaxy Mini] Rajesh_m:
Whenever i come online,the first thing that i check is whether this thread name has been changed to [KERNEL][STABLE] Badass 2.0 ;) :D :)
[Samsung Galaxy Mini] Charlie:
Hahaha me too...every day !
[Samsung Galaxy Mini] Spincervino:
Nice to hear that! So you rebased the kernel on 2.6.39.1?

Curious to know the total changelog!
[Samsung Galaxy Mini] Jeeko:
Rebased? :)

Our latest official Mini kernel is 2.6.35 so...
[Samsung Galaxy Mini] Spincervino:
Yup, and the base, Badass is currently in, is 2.6.37..

If you want we call it an update ;)

But i think it's one of the major update we'll have before someone figure out how to compile a 3.0 kernel..

Because, if i'm not wrong, the last release for the 2.* kernel is 2.6.39.4, and they're not gonna update it anymore!
[Samsung Galaxy Mini] aini12aian:
Is there a chance that this will become kernel 3.x.x?

*just asking* :o
[Samsung Galaxy Mini] mickey4398:
mybe. i think a 2.x.x.x is a closed source.i am right? can anybody make 3.x.x for galaxy mini??:D
[Samsung Galaxy Mini] alin.p:
I didn't rebase it, because this was not necessary. Most of the 2.6.39 update don't even apply to our hardware. I updated to 2.6.39 only the core components that are used by our device. I had to do this file by file, commit by commit, because as you know, our kernel already has a lot of 3.0, 3.4, 3.8 and 3.10 functions and components.

A 3.0 would make no difference for our device. Don't bang your head about that too much. The only hope would be a 3.8, compiled with the least hacks possible. But that is close to impossible, and too much time consuming to be worth it.

Nope, sorry :) you have the reason why above.
[Samsung Galaxy Mini] Charlie:
[MENTION=4525074]alin.p[/MENTION] i want to ask if some bugs of badass 1.9.2 will be and on 2.Cause v1.9.2 after 2 days my phone stack on bootloop and it was soo laggy.Sorry if my question is newby but i want to know that badass 2 wont put me again to install again new rom isntall all my apps etc...