yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Mini] alin.p:
Of course it works only for USB. What do you want it to work for? The AC charger always recharges the battery at maximum voltage. Only the USB charging had limits.

WheatleyPlus has been removed because it was too heavy for our CPU. The governor needs faster CPU transitions to work at its fullest. The new interactive is better.

Galaxy Spica doesn't have the same SoC as our Galaxy Mini. The sources are useless for porting. But I'm amazed that even Spica has 3.0 and we don't.
[Samsung Galaxy Mini] MA-90@:
alin.p you can make stable OC 806 Mhz?
[Samsung Galaxy Mini] Jeeko:
That would be great, even if it wouldn't be very useful.

The performance ​​are very high only at 604 mhz :p
[Samsung Galaxy Mini] alin.p:
That isn't necessary at all, even if it would be completely stable. You'll see in the changelog for 1.9.2 that this version has Dynamic PLL Overclock. This means that 604MHz, 652MHz and 768MHz are clocked higher than before, giving us higher read/write speeds and more computing power while keeping stability and battery life.

There are only two things that I need to take care of, so we can enjoy that additional speed:

1. Optimize one governor for our frequency range and transition latency

2. Optimize workqueue speed so the governor could do its calculations faster

A stable 806 would require lower PLL to be stable, which would make the frequency work slower than the 768.
[Samsung Galaxy Mini] M.z:
Your kernel ver. 1.9.2 very stable, fast and smooth .. whitelist fully function too

Thanks :thumbup: :D
[Samsung Galaxy Mini] mdtabu:
I have flashed badass 1.9.2 over cm10.1 initially everything works fine but when I reboot my phone 2nd time doesn't boot at all .have to reflash rom to get back.what am I missing?

mdtabu
[Samsung Galaxy Mini] alin.p:
Well it surely isn't the kernel's fault. You have something that conflicts with it, maybe a script or a patched file.
[Samsung Galaxy Mini] Sherpu:
Question

Does the 1.9.2 version have any problems like 1.9 [random reboots, lags, graphical bugs] on cm10.1.1 ? And why was badass governor removed, which should i use instead ?
[Samsung Galaxy Mini] alin.p:
All the bugs were fixed. You just have to be careful not to use some conflicting script. Only zRam and CrossBreeder are needed.

Badass was removed because it was using too much battery. Use Interactive or SmartassH3 for now. I'm working on a better governor right in this moment.
[Samsung Galaxy Mini] Sherpu:
After flashing zRamv2 and 1.9.2 [already had CrossBreeder] the phone locks completely after inserting pin code. Only the nav bar and the status bar remains but wont do anything, touching, locking... But before asking the pin code it responds quite good. Whats the issue here?

Had a backup before flashing those two and it seems that zRam was the problem... Flashed only 1.9.2 at it works excelent now. Thanks
[Samsung Galaxy Mini] alin.p:
I really don't know. Without a logcat, it's hard to guess. I'm trying to make 2.0 a perfectly stable version, until then, just keep reporting.
[Samsung Galaxy Mini] aakashasaj:
I flashed 1.9.2 on your rom, set to interactive 66-652, and sioplus and also implied those suggestin given on rom pg (beside flshing crossbread)

I am using seeder app and nothing else.

Had random reboot and even next browser randomly crashes.

What to do?
[Samsung Galaxy Mini] alin.p:
The random app crashes happen because the lowmemorykiller's settings are a bit too aggresive. I fixed this in 2.0 but I can't release it now. I still have a lot of work to do. The random reboots though, are not caused by the kernel. I have used it for the past 2 days and never had any reboot.
[Samsung Galaxy Mini] aakashasaj:
The rom and kernel are so awesome but dont know where i mess, i have to revert back to cm7 cause of bootloop stuck, but thanks a ton for all your efforts.

Take your time for kernal 2.0 and please will you update the rom also to latest cm. Thanks again.
[Samsung Galaxy Mini] :
Alin.p or modification of equipment overlays something to the performance?

Is the sea to work on the extension of the mobile phone while using bluetooth and wifi?

Why antutu benchmark with the same configuration of the phone returns different results?
[Samsung Galaxy Mini] alin.p:
I don't understand a word man. Please don't use Google Translate, it breaks your language in a really ugly way.
[Samsung Galaxy Mini] RicardoQ5:
Camera with graphic glitches

Hey alin.p, I'd like to report a bug that you may wanna know about. With the lastest versions of the kernel the camera faces graphic glitches, specially when I touch to focus. It's a pity because I use the camera several times in a month.
[Samsung Galaxy Mini] Nixoman:
its because overclocking the cpu, try with 600, youll see
[Samsung Galaxy Mini] alin.p:
This happens in stock kernel too when overclocking.
[Samsung Galaxy Mini] Jeeko:
[MENTION=4525074]alin.p[/MENTION] two questions

1) What does exactly this "easter egg" called Fast Charge? :)

2) In my AOSP JB I can use your CM10.1 version or I have to use the original CM kernel?
[Samsung Galaxy Mini] akuila:
Easter egg given you an ability for usb charging as it charging from charger AC.

You can see the indicator on the battery option while plugin the usb, there will be displayed AC not USB
[Samsung Galaxy Mini] alin.p:
Fast Charge is obviously only for USB, because nowadays phones have a voltage limit while charging through USB. Ours was 1200~1500 mA. With Fast Charge, the phone recognizes the USB as an AC charger and starts charging at full voltage which is 1800 mA.

Well the ramdisk for CM10.1 has a file named init.cm.rc which obviously isn't needed in the AOSP version. You might need to delete that.
[Samsung Galaxy Mini] VR.gtmini:
You can provide a patch until

-OR-

Steps to tweak it (I guess its hard :)

Cuz, the ROM bootloops after often(every) restart. I had to wipe cache or even dalwik sometimes to get booted to homescreen

TOUCHWIZ | AOSP | ICS
[Samsung Galaxy Mini] :
Alin.p I have three question .

Why my 10 class sd crad have slow speed ( 9/8mb ) ?

How's it going with the kernel 3.xx ?

What's new in 2.0 kernel version ?

Small trouble :

Sometimes I can not wake up the phone

For me there is no bootlop (10.1 cm)
[Samsung Galaxy Mini] alin.p:
I can't compile any patch, the kernel has too many changes to revert it to 1.9 version just for a patch. You have to wait. But the bootloops are not caused by the kernel, it is stable. You have something conflicting with it. After 2.0, I'll write in the first thread everything that should be avoided when installing the kernel.

I know that 1.9 is not really good, it is more of a pre-release than a complete version. I'm not developing 3.0 anymore.

2.0 has a lot of new features and optimizations, you'll see them in the changelog, I can't write all of them here. That wake problem is fixed in 2.0, you'd have to live with it until the release. :)
[Samsung Galaxy Mini] ast00:
For sd card: the phone can't handle more. There are some scripts that should make it gadget, but they conflict with everything, so you should avoid using them. I have Uh1 sd card or our Galaxy Tab 2 can't use more than 13mb/sec.
[Samsung Galaxy Mini] crullick:
ics deep sleep again

all hail great wizard alin

i know you update op meticulously, but i wonder about.....

flashed the existing cm9.2 version on ics based miui, and everything works; but i can't get it to (deep)sleep

[msm_serial_hs_dma wakelock issue]

i'm too stupid to get rid of this myself; so i was wondering if it's kernel related or...?!
[Samsung Galaxy Mini] deathdekid:
after i flash this kernel, my gps not working... anyway to fix it?
[Samsung Galaxy Mini] darkshadow1997:
crullick, its rom issue not kernel since i am using cm9.2 with badass kernel and deep sleep works.

deathdekid, which rom are you using if its cm9.2 and aosp then it does have gps issue and its not kernel related.
[Samsung Galaxy Mini] crullick:
darkshadow you're right >> i've experimented a bit more and solved it

[btw: badass + miui/cm9.2 = winning combo]

i appologise for spam
[Samsung Galaxy Mini] deathdekid:
Which MIUI did u use? Can u give me the link?
[Samsung Galaxy Mini] crullick:
i've combined these two: 1 + 2 taking the best parts from each

in addition to latest badass/zram/minfree and crossbreeder
[Samsung Galaxy Mini] :
Alin.p what you think of the increase in the kernel:

read_wakeup_threshold

write_wakeup_threshold
[Samsung Galaxy Mini] A_U:
hey @alin.p

as a token of appreciation for all ur hardwork, i just made some cool banners for ur thread..

will be making a kernel boot splash soon.

cheers :)
[Samsung Galaxy Mini] ast00:
@up

Once he said he likes light colors, so maybe you could make the black text grey. Just guessing, don't listen to me :p. BTW which font is that?
[Samsung Galaxy Mini] Jeeko:
Good work [MENTION=4677294]A_U[/MENTION] :good:
[Samsung Galaxy Mini] alin.p:
Pure awesomeness! Many thanks man, I'll include them in the first post when I finish 2.0. I like them both, don't change anything. The contrast makes it more badass. :p
[Samsung Galaxy Mini] A_U:
glad u like it :) just a humble way to show that we [mini community] like ur work very much...
[Samsung Galaxy Mini] crullick:
A_U you're the man!

[alin.p is +/- superhero] :D
[Samsung Galaxy Mini] hsay:
[MENTION=4525074]alin.p[/MENTION] please check your pm.......thanks
[Samsung Galaxy Mini] ast00:
Problem: Heavy lag after deep sleep while using dynteractive and sio plus. Can you take a look at it? Today I just couldn't answer a call because it was not reacting.
[Samsung Galaxy Mini] Lapnis:
he said that that governor was not finished... try using interactive with sioplus
[Samsung Galaxy Mini] alin.p:
I know about dyninteractive. I removed it and created my own governor for 2.0 :p
[Samsung Galaxy Mini] ast00:
Lol. And how you named it? Actually I knew it was unfinished, but I thought why shouldn't I test it and add it turned out you can't answer calls with it.
[Samsung Galaxy Mini] alin.p:
Zen. It's based on SmartassV2 and the main differences are:

1. Dynamic Awake Ideal Frequency based on idle states

2. Boostpulse linked to the Synaptics driver

3. Custom Boost Frequency (604 MHz default)

4. Snappier because of different fine-tuning of parameters.
[Samsung Galaxy Mini] Masrepus:
[MENTION=4525074]alin.p[/MENTION] u have disabled logs on badass as u have written before, but i would be glad to use them for debugging my apps. Ya i know i just could revert back to au kernel, but i really like urs so i dont really know what i should do... Could u maybe re-enable logs on next release? That would be nice from u! :)

Well other question about that, why didnt u include them, does that increase performance?

Gesendet von meinem GT-S5570 mit Tapatalk 4 Beta
[Samsung Galaxy Mini] A_U:
disabling debugging reduces boot time drastically..its the only advantage
[Samsung Galaxy Mini] :
I found something interesting related to the performance

Adrenobooster

http://xdaforums.com/showthread.php?t=2167228

Not all the lines in the configuration file are working fine.

I've tried a few and 200 points in antutu.

Sea of interest to someone who knows it.

In my mod works on Jelly Bean
[Samsung Galaxy Mini] alin.p:
I can't enable the debug feature because you can't just switch it on and off with a simple line of code. Disabling debugging required deleting and commenting a lot of lines of code. I can't revert this. The advantages are reduced boot time and increased read /write speeds.
[Samsung Galaxy Mini] RootNightmareX:
Cand lansezi v2 :fingers-crossed: ?
[Samsung Galaxy Mini] Sherpu:
Unu la mana aici vorbesti engleza... si doi la mana, nu intrebi niciodata de lansare, se va lansa cand se lansaza. Stai si asteapta :P
[Samsung Galaxy Mini] mnemonyc:
Respect the rules! Only use english language!

Respect the rules! Only use english language!
[Samsung Galaxy Mini] Sherpu:
that`s what i said to him in the comment, since i speak the same language as him. Maybe he doesn't speak english very well :P so i was clear to use english
[Samsung Galaxy Mini] RootNightmareX:
Yeah, he's a teacher :P

BTW Sorry I forgot the forum is english-only but I saw some posts in other laguanges never'mind.
[Samsung Galaxy Mini] ast00:
If you post in other languages, write the english version under it. Yes, we can use transtalor, but it's better for everybody like this.
[Samsung Galaxy Mini] Masrepus:
Ah ok so then dont worry :)

Gesendet von meinem GT-S5570 mit Tapatalk 4 Beta
[Samsung Galaxy Mini] Sherpu:
Are there any plans for cm 10.2 [ 4.3 ] ?
[Samsung Galaxy Mini] ast00:
First of all wait until CM10.2 comes out and then we can talk about the kernel supporting it.
[Samsung Galaxy Mini] Benjowee:
When I flash the kernel the CRT animation are not working? Or i think the crossbreeder idontknow.
[Samsung Galaxy Mini] darkshadow1997:
which rom are you using for me its working and i used cm10.1 and cm9.2.also crt animations are framework related not kernel or scripts.
[Samsung Galaxy Mini] alin.p:
Some ROMs have a CRT animation dependent on animation speed (you'll find these settings in Development Options). CrossBreeder changes the animation speed from 1x to 0.5x . Just change it back to 1x and you'll get your animation back.
[Samsung Galaxy Mini] A_U:
we can check our zram status with this APP
[Samsung Galaxy Mini] :
Alin.p to go work with 2.0?

I would recommend to go off all animations.

Latest cm is getting faster

Android 4.3 will be more optimal (10/20%)

What do you think about Adrenobooster?

It is a pity that there is still cm with Android 4.3
[Samsung Galaxy Mini] Masrepus:
I thought 4.3 wouldnt work that nice on mini coz of still too much ram consumption? Yet less than 4.2 but in my opinion 4.2 doesnt have great performance

Gesendet von meinem GT-S5570 mit Tapatalk 4 Beta
[Samsung Galaxy Mini] piterdemon:
On mini 4.2.2 sometimes work better than 4.2.2 on my ainol novo 7 fire ;__;

Wysłane z mojego Nexus 7 za pomocą Tapatalk 4
[Samsung Galaxy Mini] alin.p:
The kernel already has included all the tweaks that you can find in scripts. There's no need to suggest this kind of tweaks. Android 4.3 will not be more optimal. The only changes that our device will get will be app-related, and that doesn't mean much.

2.0 is in the works, and there's still pretty much to do. I can't announce any ETA.
[Samsung Galaxy Mini] addyhardiana:
How about screen flickering on camera UI? Can you confirm that on your current ROM? (I mean CM9.2)
[Samsung Galaxy Mini] hsay:
That happens on every rom if you over clock.
[Samsung Galaxy Mini] alin.p:
Yes, the flickering still happens when overclocking. I tried to fix it but it's not kernel related.
[Samsung Galaxy Mini] ast00:
Strange, because I used Gingermod overclocked and it was fine.
[Samsung Galaxy Mini] L.E.D 26:
But that is gingerbread ;) back o topic,sorry for deviation.
[Samsung Galaxy Mini] Masrepus:
Ah it is caused by oc? I always wondered how to solve that, thank you very much! :D

Gesendet von meinem GT-S5570 mit Tapatalk 4 Beta
[Samsung Galaxy Mini] addyhardiana:
No, i don't overclock it, the frequency is normal, just about 122-604mhz :)
[Samsung Galaxy Mini] Benjowee:
Is there any way to make it compatible for CM 7.2 based sir?
[Samsung Galaxy Mini] hsay:
It is not impossible but it would require a lot of time and sir alin.p

Doesn't want to spend so much time in making a buggy kernel for cm7 that not many use anyway....

He has answered this question many times ...so I thought I'd save him the trouble of answering it again.
[Samsung Galaxy Mini] Benjowee:
Any news? :)
[Samsung Galaxy Mini] Masrepus:
Hi [MENTION=4525074]alin.p[/MENTION]

I just edited ur init.d script for the taskkiller whitelist, put it in init.d and set permissions like all the other scripts, i think -rwxr-xr-x. When looking at the script, i saw that it would echo sth into a file called /sys/module/lowmemorykiller/parameters/w_list. But there wasnt any file called like that in the lowmemorykiller directory, not even yet after reboot, where ur script should've been executed. I thought maybe it would help to create the file manually and let the script edit it, but es file explorer told me 'no such file or directory'. My question is, is the whitelist working but i just dont see the file, ir do i have to mod ur script a little or what else should i do?

Thx in advance :)

Gesendet von meinem GT-S5570 mit Tapatalk 4 Beta
[Samsung Galaxy Mini] akuila:
did you use kernel 1.9.2 ?
[Samsung Galaxy Mini] alin.p:
Every modification you make in the /sys folder (create files, edit files) is gone after reboot, and creating a file that the kernel doesn't know about, would obviously be useless. But that file exists and works, but is present only in version 1.9+ of the kernel. You might be using 1.8.
[Samsung Galaxy Mini] Masrepus:
Oh that could be... i dont know exactly which version im using

Gesendet von meinem GT-S5570 mit Tapatalk 4 Beta
[Samsung Galaxy Mini] al_atlantis:
guys,tell me the best performance config for the latest version.. :)
[Samsung Galaxy Mini] A_U:
604-66 MHz smartash3 sioplus for more battery

652-66 MHz smartash3 sioplus for balance between battery and performance
[Samsung Galaxy Mini] al_atlantis:
Thanks,dude.. :)
[Samsung Galaxy Mini] Masrepus:
Well i prefer 604-652MHz smartassh3 sioplus cause with 66-652 i experienced many lags

Gesendet von meinem GT-S5570 mit Tapatalk 4 Beta
[Samsung Galaxy Mini] jamesmuking5:
I dislike sioplus. I'll stick with deadline :)
[Samsung Galaxy Mini] RootNightmareX:
Roses are red,

Violets are blue,

The Mini is (almost) dead

Is this Kernel too ?
[Samsung Galaxy Mini] alin.p:
:)) no man. I'm still working. Actually, I'm testing some new Linaro toolchains right now to see if there is any difference in performance.
[Samsung Galaxy Mini] RootNightmareX:
Thanks dude for still working on something for this device. :cowboy:
[Samsung Galaxy Mini] Masrepus:
Nice xD

Gesendet von meinem GT-S5570 mit Tapatalk 4
[Samsung Galaxy Mini] Laruku Anan:
hopefully the new build will released soon :D
[Samsung Galaxy Mini] Rivaz:
I see in LG Optimus One forum this post: http://xdaforums.com/showthread.php?t=2144790

Looks like kernel 3.0.8 works on ARM V6 devices, and run very well. Still have some bugs...

https://github.com/androidarmv6/android_kernel_lge_msm7x27-3.0.x

Can you take a look?
[Samsung Galaxy Mini] alin.p:
I know it works on LG, and it works on Galaxy 5 too. But our device has a problem with some closed source drivers(FSR drivers). That's why it is almost impossible to compile a 3.0+ kernel for Mini.
[Samsung Galaxy Mini] Rivaz:
Sorry if it's a stupid question, but Galaxy mini and Galaxy 5 dont't use allmost same drivers?

I find here something: http://madteam.co/forum/development-8/(devhack)-samsung-flex-sector-remapper-driver-discussion/

I don't know if it's usefull for you, but I hope it will help you.
[Samsung Galaxy Mini] alin.p:
They have almost the same drivers. The FSR driver is just ~98% similar. That little difference is located in the closed source file.

I know about the thread and psyke's attempt to compile 3.0 for our devices. He got a successful compile only on Galaxy 5.
[Samsung Galaxy Mini] Dark Passenger:
that is why erikcas tried for MTD and it worked once .... then the awesome revival of Samsung armv6 was over :(

hope you haven't given up on 3.0 for mini/fit...?
[Samsung Galaxy Mini] alin.p:
The new version updated to 2.6.39 gets the most of our device and really pushes it to the limits. There's no advantage anymore in compiling a 3.0+ kernel. It would only give me a lot of work. The performance and stability would be the same(or worse). The only thing that would get us more performance would be optimizing Android's framework. (which I am doing for my next ROM)
[Samsung Galaxy Mini] Masrepus:
U mean lenio, dont u?

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

we have 3.xx kernel source

in hame we 2.6.xx kernel source

we do not have the FSR driver

Is it possible to modify the source to the kernel 3.xx accepted the old driver.

What do you think?

rom

Strip libs

compress bin and xbin with upx

disable / remove DropboxManagerService
[Samsung Galaxy Mini] Jeeko:
It isn't so simple, also if we have the 3.0.x armv6 source the FSR drivers make the difference.

Apart from that this kernel has many features of the 3.x kernel (check the OP) then I do not see why compile a kernel 3.x maybe with some bug :p If you want see write in your "Device info" 3.0.8-androidarmv6-alin@imediaecc. you have only to change the "Makefile" strings with whatever number you want, then compile.

Believe me, this kernel is 1.000.000 miles ahead the others mini kernels (respect for others devs) :)
[Samsung Galaxy Mini] RootNightmareX:
Hope he makes a ICS Rom. ICSs ARE the best performance and stable ROMS for our Mini.
[Samsung Galaxy Mini] alin.p:
Yes, I am working on a completely different ROM based on CM9.2. I would have chosen AOSP but I can't live without some CM features. :)
[Samsung Galaxy Mini] Jeeko:
CM9.2 needs colors fixes (expecially the holo_background) but I bet that with your Lenio theme will be all ok ;)
[Samsung Galaxy Mini] alin.p:
You'll be surprised to see the new layout :p
[Samsung Galaxy Mini] Jeeko:
I can't wait :D
[Samsung Galaxy Mini] Masrepus:
How will u call ur rom? :curious: :D

Gesendet von meinem GT-S5570 mit Tapatalk 4
[Samsung Galaxy Mini] A_U:
" dont post bullshi*t " maybe ? :rolleyes: XD

justkiddin..
[Samsung Galaxy Mini] Dark Passenger:
actually I believed a clean code allows for the best performance you know shortest path and such.

so my idea for 3.x wasn't to get the kernel no. but rather have a kernel without the hacks(or at least lesser ones:p)so as to have as God(oops Google:o) intended.

am interested in what the framework optimizations are since that's what I always here but never truly comprehended what this is suppose to be...(trade secret...?)

finally can you if you wish that is please consider pushing the framework optimizations to erikcas's github(or at-least releasing a patch) because all respect to you I prefer a clean un-themed ROM.

EDIT also please try and include the kernel version in the future releases(yes the line that displays in the rom).Kindof makes it easier to know where your at.

EDIT2 last i swear any thoughts on ION...?
[Samsung Galaxy Mini] alin.p:
Still thinking about that :p

I did a massive code cleaning on 2.6.39, and still have something to optimize, so it is kind of the same :) I know what you are talking about, but the same hacks would have to be used in 3.0+, because that is device-specific code that our device wouldn't work without.

I compiled MIUIv4 3.2.22 to use as a base, and all their code is in smali language (dammit!), so I can't push the code changes to the original repository. I'll talk about the optimizations after I'll get them done, I'm not sure what will work and what not.

I'll include the version, thanks for telling.

I did some research on this. As I said in some earlier posts, ION doesn't get us a plus in performance, because the optimizations done on it are not for our device, but for high-end devices. But PMEM is still good, as it is optimized for our Qualcomm hardware.
[Samsung Galaxy Mini] Dark Passenger:
Glad to know and thanks for the fast reply.

I would still suggest to check the code on erikcas's github for smali and java are very smilar nonetheless I do hope you will consider releasing a patch for regular cm9.2 also.

again thanks and desperately waiting for 2.0

Regards,

Dark Passenger
[Samsung Galaxy Mini] alin.p:
I know the differences between Java and Smali code, but still, Smali uses a lot more complex code for a function that can be defined in less than 4 lines in Java. Also Smali doesn't store variable names. So recreating the Java code from Smali would be a pain in the ass.

Besides, Erik wants to keep his ROM as close to the original as he can. These patches are not for optimizing the system in general, but for optimizing it for our low-end device.

I don't have time to work on another CM9.2 ROM, but if I finish my other projects earlier, I'll work on a regular CM9 too.
[Samsung Galaxy Mini] RootNightmareX:
Nice. You can make the best rom out here something like a Good Bye ROM for Galaxy Mini because it seems development is dead.