yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Mini] asrivastava:
Hey guys, super noob question coming through, but, I have flashed an AOSP 4.0.4 ROM on my phone and have flashed the Badass Kernel-ICS.zip via the install .zip from SD Card option. But, I restarted my phone and could only see that my initial (black) boot screen had changed from the regular Samsung Galaxy Mini (blah blah) to a white screen with Galaxy Mini written on it followed by the boot animation, that's it.

I couldn't find any additional controls to change or modify things once the phone booted.

Am I doing something wrong or is this normal and if so, how can I take advantage of all this Kernel has to offer?

(I'm not even sure its installed. -_-)

Many thanks in advance.
[Samsung Galaxy Mini] Masrepus:
This is normal :)

Only things to do are new cpu governors and io schedulers and the whitelist for taskkiller.

Yes u have installed it cause of new bootsplash

Gesendet von meinem GT-S5570 mit Tapatalk 4
[Samsung Galaxy Mini] crullick:
would Lo0o0ve to see your wonders on miui (rom)

have you ever thought about making one for us - lesser beings? :cyclops:
[Samsung Galaxy Mini] alin.p:
Yes, it is installed, and all the magic happens behind the scenes. Everything is tweaked, so the users only have to change 2 or 3 settings. Specifically, the governor, the scheduler, the zRam and the USB Fastcharge option. The kernel does the rest.
[Samsung Galaxy Mini] asrivastava:
Awesome, and what do I install to tweak the zRam? And any recommendation for the same? :)
[Samsung Galaxy Mini] alin.p:
If you use CyanogenMod, you can tweak all these settings in Settings->Performance. If you don't, then you have a zRam script installer in the first post of this thread.

PS: To enable Performance settings, you have to go to Settings->About and press the Build Number 7 times..
[Samsung Galaxy Mini] Dark Passenger:
Hmmm okay thanks anyway and finaaly I know I'm one persistant bastard but you could release framework tweaked using the smali edits on the stock cm9.2 framework right using back smali its smali code only...you know like a flashable zip mod.
[Samsung Galaxy Mini] asrivastava:
I'm on AOSP 4.0.4, what then, should I just go ahead and flash it anyway?
[Samsung Galaxy Mini] Masrepus:
Ya of course

Gesendet von meinem GT-S5570 mit Tapatalk 4
[Samsung Galaxy Mini] Jeeko:
[MENTION=4525074]alin.p[/MENTION] In your next rom, you will add the Pimp my rom tweaks? :)
[Samsung Galaxy Mini] alin.p:
After patching the CM9.2 framework with MIUI Smali code, the files are too different to make a diff and just slap it onto the stock framework. I would have to recreate the code. But I'll take some more time and I will do it anyway. I am aware that there are a bunch of people like you that just like it stock.

Pimp my Rom has a lot of tweaks that either don't work, either don't do any good to our device. I know about everything it can do and all the working tweaks are already in the kernel, or will be included in the ROM.
[Samsung Galaxy Mini] Dark Passenger:
okay all i got was

and that

though part 2 is not really awesome but part 1 makes me reallllllly happy .

so finally

Thanks,

Dark Passenger.

PS all we all(I'm pretty sure all or atleast me!) wait for is an eta and finaaly the release.
[Samsung Galaxy Mini] alin.p:
The best estimation I can do is.. by the end of this month. My real life is pretty busy in the summer :)
[Samsung Galaxy Mini] Jeeko:
[MENTION=4525074]alin.p[/MENTION] about sweep2wake... how it goes? :) It'll possible unlock the device by double-touching the screen?

(Now I have seen that it's possible unlock the device only with the menu button)
[Samsung Galaxy Mini] alin.p:
You should be happy if only sweep2wake works. Apparently, our Synaptics driver is pretty unique (not in a good way), and I can't find enough similarities in other touchscreen drivers that could help me make sweep2wake work. I'm still trying though

What you're talking about is DT2W(Double-Touch to Wake) and it is not used to unlock the screen. It is used to wake it in the first 5-10 seconds after the screen goes off, by taking account of the lock timeout. But I talked about this three times already. We don't have the power_key_clr_reset function present in the input drivers, so it is impossible to implement this feature without updating the input drivers. A week ago, I updated the input drivers too, but after this the power button was always considering a simple press as a long press. So I reverted the update.
[Samsung Galaxy Mini] Jeeko:
Well, there is any performance improvement between building a kernel with GCC 4.7 and GCC 4.6.2?
[Samsung Galaxy Mini] alin.p:
Absolutely not. I migrated to Linaro 4.8 a few days ago, but I am using it because it has a smarter warning system, that helps me debug the compiling process and optimize the code easier. The compiler optimizations are bullsh*t. We're talking about kernel compiling here.

Compiling optimizations could be done, but to another type of code, like that of an application.
[Samsung Galaxy Mini] Jeeko:
Latest quest: it's possible to add TCP Congestion/s and/or DTIM skip override to this kernel?
[Samsung Galaxy Mini] alin.p:
We already have the first one. We use Hybla as the TCP Congestion Algorithm. I did tests between CUBIC, Westwood, Reno, Veno, Highspeed and Hybla. And Hybla was the most efficient in both 3G and Wi-Fi, followed by CUBIC and Veno.

DTIM skipping is a really bad idea for our Mini. The battery drain was huge while testing. Keep in mind that we still have hardware limitations that we can not bypass.
[Samsung Galaxy Mini] Jeeko:
Yeah, you have right... I'm waiting for your 2.0 version :fingers-crossed:
[Samsung Galaxy Mini] Rajesh_m:
Sir, i hope one day you will change your mind and make this kernel to support gingerbread too ;) ( but i am sure you wont :) ) btw waiting for your rom and kernel :)
[Samsung Galaxy Mini] RootNightmareX:
gingerbread is useless now. ICS is overall the best Android for our mini.
[Samsung Galaxy Mini] Rajesh_m:
How can it be useless??!! After all we are using galaxy mini,not galaxy s3 or s4..gb roms are the most stable roms for our mini..
[Samsung Galaxy Mini] alin.p:
Well it sure isn't useless, but with a little tweaking, you can get GB performances on ICS. And the stability is the same. The only bug on CM9.2 and AOSP 4.0.4 is (or was) the headphone bug, which can be easily fixed by replacing the audio drivers from CM9.1 or CM10.1.
[Samsung Galaxy Mini] RootNightmareX:
Headphone bug ?? I didnt found anything like this in latest Jeeko build.
[Samsung Galaxy Mini] alin.p:
Can you listen to music with a pair of stereo headphones that has only two black rings on the Jack connector?
[Samsung Galaxy Mini] Harakhti:
It reroutes to the speakers with a different volume config.
[Samsung Galaxy Mini] alin.p:
Yes, I know it does this. But thankfully, the audio drivers can be easily replaced to get rid of this behavior.
[Samsung Galaxy Mini] Rajesh_m:
Agree with your point on cm9.2 sir, i was just pointing out that gb isn't useless atleast for our mini.
[Samsung Galaxy Mini] Jeeko:
[MENTION=4525074]alin.p[/MENTION] I saw a looot of page ago that you have an awesome linux theme (blu and white) which is? :D
[Samsung Galaxy Mini] A_U:
nice work :) will try 1.2
[Samsung Galaxy Mini] alin.p:
Download 1.2.1 version. I've made a huge mistake on 1.2. I had to recover the project after a commit that messed everything, and just realized that I forgot Snappy on the way to 1.2.

You might have noticed a bit of sluggish UI here and there because of this.

Did anyone try this on 4.1.2? Does it work?
[Samsung Galaxy Mini] A_U:
tried 1.2.1 on aosp..freezes as soon as it boots into home screen..had to remove battery and flash my old kernel
[Samsung Galaxy Mini] alin.p:
Well I had the same problem, but apparently it's not kernel's problem. There's something about /data partition. After a full wipe, everything works as expected. Actually, everything is faster now and I got much more space in /data even after full recovery of my app data.

I guess all this flashing and reflashing leaves some garbage data there.

Just to be sure, I'll upload the exact version that I use right now (I recompiled it after the freeze problem to make sure it wasn't a compiler issue). Download that, backup user app data (if you use to do it), wipe /data and /cache, flash the new download.
[Samsung Galaxy Mini] ast00:
Something weird here: After flashing the ICS kernel to TouchwizICS V5, I can't open play store (it just goes back to home before opening), and also sometimes if it's in deep sleep at night for about 8 hours, home button or power button can't wake it up. But if I plug in the charger, it immediately wakes up. But otherwise both keys are working.
[Samsung Galaxy Mini] alin.p:
I lost my USB cable so I can't debug to see what's causing this.

But wiping /data and /cache partition gets rid of all the errors, unexpected reboots and lags.

You don't have to do this before every flash, but this particular update seems to require it..
[Samsung Galaxy Mini] :
Alin.p thanks for more oc ( 844 mhz full stable )

I think that below 122 mhz oc (61 mhz) and above 844

1.2.1 faster than 1.1

good work
[Samsung Galaxy Mini] hsay:
Flashed on aoxp no problems anywhere ...didn't need to wipe data or anything and currently using bad ass and row with 245-600mhz ...pretty good....
[Samsung Galaxy Mini] ast00:
Xda app is dumb. Attachment size 5 bytes, I start downloading and it's 5mb. WTF?
[Samsung Galaxy Mini] hsay:
It's not just xda app even tapatalk ...
[Samsung Galaxy Mini] vishal007:
Same here
[Samsung Galaxy Mini] F4uzan:
Same, same here.

BTW, the new version is GREAT ! Thanks alin.p & A_U !
[Samsung Galaxy Mini] alin.p:
So after half a day of researching Adreno overclocking, I finally found why I couldn't find those goddamn frequencies.

Our GPU drivers are Adreno 200, and have SoC(System On a Chip) interface. That means the GPU clock is tied to the CPU.

So as we overclock the CPU, the GPU max frequency raises too.

The good thing is.. well, we have GPU overclock :D The bad thing is that we can't hope for a hell lot faster UI, we're at the max already.
[Samsung Galaxy Mini] MA-90@:
Great Kernel, the better for JB.

In the next version you could:

1-compile with the latest toolkit linaro

2-optimize / rebased the ramdisk on that of maclaw study, in my opinion is much better.

Keep up the good work.
[Samsung Galaxy Mini] alin.p:
I'm already compiling with Linaro 4.6.2. To compile with latest Linaro I have to do a lot of useless rework in dependencies. Don't worry about that, the "compiler optimization" is just a myth. :)

I'm actually interested in that optimized ramdisk, where can I find it?
[Samsung Galaxy Mini] MA-90@:
Here are the links:

Site "MaclawStudio": http://maclaw.pl/

GitHub "MaclawStudio": https://github.com/OpenMaclaw
[Samsung Galaxy Mini] alin.p:
I checked out their ramdisk in their latest update of CM10 and AOSP. The only optimizations are done on the init(something).rc side. That kind of tweaks are already hardcoded into this kernel to keep the ramdisk clean. I also added fancyinit ramdisk script from Fancy Kernel but I'm not sure it's fully working, that's why I'm not including it in the changelog.

By the way, 1.2.2 update :D

LZ4 decompressor should result in a little bit faster boot time. If I can get the kernel to boot with CPU unaligned access, the boot time would be a hell lot faster. Still working on that.
[Samsung Galaxy Mini] Jhayzt:
Hey there sir Alin.p. umm.. I come from the Galaxy Fit department. Is there by any chance make something similar to our device? The GPU overclock is tempting. I tried it on my fit but the capacitive keys aren't working. :D
[Samsung Galaxy Mini] harisangarans:
I have tried 1.2.1 version on aosp ics...i had problems with ROW schduler(system became unresponsive on opening every applications)..now i use deadline and badass and it seems perfect &faster:)

sent from my 1st android phone #galaxymini <3<3
[Samsung Galaxy Mini] -NickHalden-:
Great work. Keep going :)
[Samsung Galaxy Mini] alin.p:
I think it was Plane. :) You'll find it here: http://www.noobslab.com/2013/06/plane-gtk3-theme-for-ubuntu.html
[Samsung Galaxy Mini] Jeeko:
Yeah, Is this :)

Anyway, what do you think about KSM?
[Samsung Galaxy Mini] Dark Passenger:
hey I think I mentioned ultra ksm a while back...? that seems like a way more awesomeer feature...yes
[Samsung Galaxy Mini] alin.p:
What do you mean? It was included in the kernel since ICS, and in 2.0 I'll let it out. The CPU resources that it needs is way too high for it to work properly, and the performance goes into a regression.

There was an attempt to implement the more optimized UKSM, or PKSM, but after stripping all the x86 code, all that remained was the old KSM. So there are no ARM optimizations done in the KSM algorithm.
[Samsung Galaxy Mini] Dark Passenger:
hi so that sucks :(

anyway so erikcas is going to try and port 4.3 this weekend(cm10.2) and to quote him on what he thinks cm10.2 will be on 2.6 kernel

anythoughts from you on this...i heard that 4.3 had better ram management and was better optimised for lower end devices..
[Samsung Galaxy Mini] Jeeko:
I mean KSM Page Kernel Fusion... I have seen that you have disabled this feature on your latest kernel, so I tought that you don't consider it impoeran
[Samsung Galaxy Mini] alin.p:
I looked through the 4.3 source code changes. Whatever RAM management optimization they have done, it must be really hidden or not present at all, because all I saw was a lot of Google Nexus biased optimizations, and as far as I know that's not a low-end device.

After all, why would they optimize such a system for low-end devices, if they are not going to release it for them anyway. I guess we misinterpret Google's understanding of the term "low-end".

Jelly Bean is and will always be too much for our 256 MB of RAM..

I disabled it because it is either useless, either not good for our device. On aggressive settings, it merges a reasonable number of pages, but it consumes ~30-50% of CPU which drains the battery and hogs the system. On medium to low settings, it doesn't merge enough pages for it to have any effect on performance. So I just left it out to avoid wasting CPU cycles.
[Samsung Galaxy Mini] Jeeko:
You think that the Badass2 will be the latest definitive version?
[Samsung Galaxy Mini] Dark Passenger:
I actually wanted to know what you felt about the comment Erikcas said that in context to building cm 10.2 on a 2.6 kernel(to be precise non 3.x)

since badass2 will practically be a mashed 2.6 and 3.x kernel wanted to know if things will be that bad...or nothing else even if we did have 3.x.

EDIT : also just came across this but is there any ARM11 optimization included in the Kernel also same for jit.

u know like sparrow was for cortex a9 and krait for a15...

also is USB host still possible in v2.
[Samsung Galaxy Mini] A_U:
@alin.p ur work is spreading like wildfire my man..great job :)

already using self compiled v2 on mini and now on ace too..every thing's working properly..
[Samsung Galaxy Mini] alin.p:
Yes, it will be a pre-release version first, and a final version where I will only fix bugs if there will be any.

It will be enough if we add the new kernel code for 4.3, to get the kernel working at its fullest. The only problem would be if the code would be too dependent on 3.x core.

JIT Compiler is not a part of the kernel. It is part of the Android system.

Sparrow and Krait are optimized CPU architectures. They are new physical CPU's not some kernel code optimization.

Anyway, I included a lot of patches for the ARMv6 code in the kernel, so there are some optimizations done.

No, USB Host is not possible on our little device. Our OTG driver doesn't support this.

Glad to hear that :p

Did you diff the configs to add all the new features?

Also I think Ace has a different acpuclock driver, so the CPU clock structure has to be modified for Zen to work properly, to add the Dynamic PLL Overclock and the Undervolting. I'll compile for Ace too before the release, hope you are willing to be a tester. :)
[Samsung Galaxy Mini] A_U:
yea for mini i did diff it..

on ace i dint compile..i let that process for the op of that thread..

maybe u can help him so that he can ease ur work :) and sure will be ur tested gladly..

zen gov is very nice..just as u said.

and used old version of linaro 4.6.2 i think..is there any difference in performance btwn 4.8 and 4.6 ? or is it just a myth..
[Samsung Galaxy Mini] alin.p:
wut? What thread? Is someone trying to compile and release my kernel?

Keep in mind that Zen is optimized for 66-604, 66-658 and 66-770 frequency range. You'll get the most of it on these settings. There some more to know about this governor can do, but I'll write the instructions at the release.

Compiler optimizations are just a myth. But I modified the kernel Makefile to suit the Linaro 4.8 compiler. After I push the new commits you will have to update the compiler. Until then, stick to 4.6.2.
[Samsung Galaxy Mini] A_U:
see ace thread :)..spacecaker already started working on badass for ace and reached a v2 release..

he's havin some problems lately, maybe u can help him ? :)
[Samsung Galaxy Mini] Masrepus:
Wow, 770, really? Is dat really stable?

Oh man cool :D

Gesendet von meinem GT-S5570 mit Tapatalk 4
[Samsung Galaxy Mini] ast00:
787 is stable in mini, so I don't see why it wouldn't be stable in ace.
[Samsung Galaxy Mini] Masrepus:
Hm well, in my experience, all over 700 make many force closes... (im sure that theyre caused by frequency, cause looking at logcat says that there are some cpu errors)

Gesendet von meinem GT-S5570 mit Tapatalk 4
[Samsung Galaxy Mini] alin.p:
This varies on every device. Some have completely stable phones even on 840. So it is hardware related.
[Samsung Galaxy Mini] ast00:
Mine is stable until 787, my friend's phone is stable until 729 (pretty low), and yes, some phones are stable until 864. Everybody has to test it.
[Samsung Galaxy Mini] Charlie:
Guys any way to delete this white screen with 'Galaxy mini' on boot? xD
[Samsung Galaxy Mini] alin.p:
Why do you want do delete it? If it is for the boot time, forget it. The boot time will be the same, with or without the bootsplash. If you just don't like it, you have to unpack the boot.img with boot.img-tools, delete or replace TASS.rle, repack the boot.img, flash it.

You'll find tutorials for all these actions, here on xda.
[Samsung Galaxy Mini] Charlie:
I dont find a reason to do it as you said the boot time will be the same...so ok thnx :)
[Samsung Galaxy Mini] Masrepus:
And i find the splash quite pretty :D

Compared to the boring stock one

Gesendet von meinem GT-S5570 mit Tapatalk 4
[Samsung Galaxy Mini] alin.p:
Thanks! :) The next version will have the banner that A_U made for my kernel as bootsplash. It's badass!
[Samsung Galaxy Mini] lollipop:
[MENTION=4525074]alin.p[/MENTION]

i like this kernel too much

i use 122mhz-600 and smartassh3

it's smooth but sometime the phone freeze and i can do anything so i have always to remove battery

any ideas alin.p :confused:

i use cm9.2 version
[Samsung Galaxy Mini] darkshadow1997:
same here i use cm9.2 with this kernel + int2ext sometime the phone freezes or gives white screen it also happens when i use google playstore.in thing i will say is that other than int2ext i have no other scripts or mods installed.
[Samsung Galaxy Mini] lollipop:
but i don't use any script just i move apps to sd-card manuely
[Samsung Galaxy Mini] Charlie:
Sorry for asking but when v2 will be releashed :P? Im impatient :P
[Samsung Galaxy Mini] ast00:
You will see if it's released...
[Samsung Galaxy Mini] alin.p:
I can't announce ETA's. But the release is reaaally really close. :)
[Samsung Galaxy Mini] Charlie:
Thnx for your work alin.:good:The best kernel for mini out there is yours !:laugh:
[Samsung Galaxy Mini] Dark Passenger:
how close is reaaally really close ....jk actually am glad its soon .:good: keep up the good work
[Samsung Galaxy Mini] Charlie:
PS:there is a bug on 1.9.2 when move apps to sd a white screen open instead of app.is fixed on V2??
[Samsung Galaxy Mini] davidebeatrici:
Good job alin.p ;)

I'm waiting v2 to integrate it in my FutureNext ROM :D

P.S: Sorry for what happened with GoldenKernel...
[Samsung Galaxy Mini] alin.p:
This is not kernel related. This is the last time I am talking about this, I did not touch the ext4 drivers or any other Filesystem drivers. Everything regarding the filesystem (SD, ext2/3/4, NAND) is the same as in the stock kernel. If something doesn't work for you, then you're doing it wrong.

Sorry for sounding mean, but I have to make people understand that they have to do some tests and (very little) research before talking about a possible bug.

No problem. :) I talked with Jeeko. We're good. Just wait a little bit more, the kernel is almost ready for the public.
[Samsung Galaxy Mini] Rajesh_m:
Sir,any updates about your rom? :) is it ready for the public :) sorry for the eta :)
[Samsung Galaxy Mini] davidebeatrici:
I don't have rush, good work ;)

Thank you :)

Ehm... no problem, but ask it in the FutureNext topic ;)
[Samsung Galaxy Mini] Rajesh_m:
Lol.. i was asking to alin.p about his new cm 9.2 rom ;)
[Samsung Galaxy Mini] davidebeatrici:
Ah, sorry :silly:
[Samsung Galaxy Mini] Rajesh_m:
Sorry from my side, i didnt noticed your previous post about your rom :)
[Samsung Galaxy Mini] alin.p:
I dropped MIUIv4 development because of two ugly bugs that I couldn't get rid of, Mms FC's when closing the pop-up, and a noticeable lag from time to time. Hell, I even got themes fully working on 3.2.22, but those bugs were too much.

So, I started developing my own ROM from Erik's CM9.2 sources. Yes, I am using raw Java and C++ code, no ROM cooking at all. I'm trying to create a clean ROM, with a whole new layout and the best performances that one can find in an ICS ROM, with the least user intervention.

Because this will take some more time, I'll release the kernel first, and the ROM afterwards. Goddamn, even on a quad-core, Android compiling takes ages...
[Samsung Galaxy Mini] Rajesh_m:
You work so hard sir :) wish i could help you to reduce your burden,but the thing is i know nothing about developing rom ;) anyway eagerly waiting :)
[Samsung Galaxy Mini] jamesmuking5:
I'm reaaaallly reaaally excited dammit :D
[Samsung Galaxy Mini] Masrepus:
Oh yeaah ;D the banner is really nice :) Thx [MENTION=4677294]A_U[/MENTION]

Gesendet von meinem GT-S5570 mit Tapatalk 4
[Samsung Galaxy Mini] lollipop:
yeeeeeeeeeees, we are expecting the best ics rom with the best kernel for our mini :)
[Samsung Galaxy Mini] stety:
Alin.p: I would like to ask if you could do a new rom add support for Ad-hoc WIFI network? Or if you could do at least some. zip to flash?

I know that it works on CM7 but Android 4+ no.
[Samsung Galaxy Mini] davidebeatrici:
Where is the banner? I want to see it :)
[Samsung Galaxy Mini] Sherpu:
There you go
[Samsung Galaxy Mini] davidebeatrici:
Beautiful :cool:
[Samsung Galaxy Mini] darkshadow1997:
alin.p

i have a question why do you update badass kernel cm10 even though you do not fix the mass storage bug.not being rude here just asking.
[Samsung Galaxy Mini] alin.p:
Because there is no mass storage bug. If it works for me, it should work for you too. I didn't touch the USB drivers either, they are the same as in the stock kernel. Just try a little more to get the settings right.
[Samsung Galaxy Mini] darkshadow1997:
i am using cm10 with you kernel and mass storage is not working but with default cm10 kernel it works also i am talking about cm10 not cm10.1
[Samsung Galaxy Mini] Charlie:
i had an issue today.after badass install i had many lags reboots fc and in the ens bootloop...second time i find this bug:(
[Samsung Galaxy Mini] alin.p:
There's no use to report 1.9.2 bugs. 2.0 will have 2.6.39 as base, and will be completely stable. After the pre-release you can report bugs again.

As for the mass storage, I never tested the kernel on CM10 4.1.2 because it is not so widely used as the other two 4.0.4 and 4.2.2. But in theory, everything should work because the system uses the same usb drivers base as 4.2.2. If the bug is really present, then I won't update the CM10 version anymore, I don't have time to fix this.
[Samsung Galaxy Mini] Charlie:
So badass2 will be new?Not based on 1.9.2?