yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Mini] alin.p:
v2 will be completely bug free. If anyone experiences bootloops, freezes or whatever else, they should take a better read through the OP. The kernel can't corrupt the data on the device. I'll write there what shouldn't be used with this kernel. For example, in terms of scripts or mods, ONLY Crossbreeder or Seeder is allowed. All the other possible tweaks are already included.

I have more than one month of using this kernel with equal periods on CM9.2 and on CM10.1. There were absolutely no problems. After 2.0, I won't answer anymore to bug reports, for obvious reasons.

What you experienced, was not caused by the kernel, but by using a third-party app/script/mod that interfered with the kernel. As I said more than ten times already, the kernel does not have any control on /data or /system partitions, which are the only that can cause any bootloop.
[Samsung Galaxy Mini] Spincervino:
Reply in quote ^.^
[Samsung Galaxy Mini] Charlie:
Sorry for asking :) Just to know i had no scripts on my rom! Btw maybe something in my rom made bootloop!Do your best for V2:highfive:
[Samsung Galaxy Mini] alin.p:
Maybe, someday, if I am really really bored and there's no other way left to procrastinate, I will take a look in the latest 3.8 Kernel for MSM SoC's to see how hard it would be to get a working build.

There is absolutely no problem with asking. As someone probably famous said, "The only stupid questions are those not asked".

I had problems with data corruptions and bootloops too, but after debugging, the problems were either some framework modification, either an app, either a script that was enough to work erroneously only one time, to corrupt one vital file and make the phone go into an infinite bootloop. I know 1.9.2 was, at times, unstable. But the only way it could corrupt the data, was to force reboot the phone while it was syncing the changed data, which was a really rare situation and will be completely avoided in 2.0.
[Samsung Galaxy Mini] ast00:
Any chances of getting kernel 3.8 easier than 3.0? Logically it makes no sense, but I guess you have a reason to check on it.
[Samsung Galaxy Mini] piterdemon:
Lol what do You want from mini ? My Tablet running perfectly on 4.3 and have only 3.0.5 kernel
[Samsung Galaxy Mini] alin.p:
I just had a good laugh reading something. :laugh: You guys need to read this too, and finally stop all this babbling about 3.0.

So the big leap to 3.0 was made just because Linux was entering its third decade, that's all..

See that text in red? Those are the only changes worth compiling a 3.0 kernel. But.. big but.. I have already backported ALL those changes when I was working for upgrading the LMK to the one from 3.9-experimental. So, basically, we have a good part (and probably the most important part) of the 3.0 kernel.

3.8 really has a lot of important fixes and additions to the core, that's why I was talking about it instead of 3.0. The difficulty of compiling such a kernel for our device is the same, no matter what 3.x kernel we try to compile. But it's not a promise at all. It is just a vague possibility.
[Samsung Galaxy Mini] ast00:
I never considered it as a promise. My head would explode if I would take 5 minutes and look into the sources. All what I know is that it looks complicated and it is very complicated.
[Samsung Galaxy Mini] Jeeko:
Well alin, I think that if you have backported a lot of 3.x features we don't need the original Linux Kernel 3.x at all. Anyway I think that a lot of person want the 3rd version of the kernel because they want to see in your phone info 3.0.84 or something else.

Keep up with your work :D
[Samsung Galaxy Mini] :
Kernel 3.0 is a legend such as free premium account on rapidshare.com

I think it could be done with a fake message kernel version

Alin.p knows what he's doing and encountered the kernel gives us new opportunities
[Samsung Galaxy Mini] prafiles:
It would be helpful if you created branches of your code when you think its a milestone. Just a suggestion. There are a huge number of changes that you commit. :D And i am grateful for what you do! Difficult to keep track of them. As always awesome work.!
[Samsung Galaxy Mini] alin.p:
Yeah, it is a good idea. But I should have thought about it before starting the work for 2.0. This version will be final, so no future milestones whatsoever.
[Samsung Galaxy Mini] Charlie:
How is your kernel going sir badass :P??
[Samsung Galaxy Mini] alin.p:
Almost reached the finish line. :) because of the new ideas that I had to implement yesterday, one day of delay has been added too. I think tomorrow I'll finish porting all the features for Galaxy Fit and Ace too, then I start working on the app.
[Samsung Galaxy Mini] prafiles:
Ha ha finally its good to see your streak stop.! :D Don't get me wrong but I wished to study your code. Its hard to that when you're moving ahead so fast. Finally can catch up! :D
[Samsung Galaxy Mini] alin.p:
Now that you say this, I think I should have added some comments in there :p I was kind of egoistic while working on the code, I never thought of making the code easier to understand for other developers. If you have any questions, feel free to ask :)
[Samsung Galaxy Mini] Charlie:
For which app are you talking about??:confused:
[Samsung Galaxy Mini] alin.p:
The app for controlling all the new features present in the kernel. I had been talking about this continuously for the last week.
[Samsung Galaxy Mini] prafiles:
Frankly sir in a world where people try to do good for themselves only, you trying to openly develop and share your work is a big move. This XDA community and culture is great. I feel happy only to get the source and being able to control what OS I run on my hardware. And as you've offered to help already I feel that its more than what I need.
[Samsung Galaxy Mini] Masrepus:
Now that i see it, im wonderimg why you are not a recognized developer or something like that, [MENTION=4525074]alin.p[/MENTION] ? For that amazing work you do :)

Gesendet von meinem GT-S5570 mit Tapatalk 4
[Samsung Galaxy Mini] mickey4398:
will V2 work with CM 10.2 for galaxy mini beacuse cm 10.2 relased today for G.mini ?:laugh:
[Samsung Galaxy Mini] lollipop:
false not today :silly:
[Samsung Galaxy Mini] alin.p:
I guess I have to collect a predefined number of thanks (probably 1000) to get a "Recognized" title.

Well, there are no changes in the Androidarmv6 kernel for CM10.2 so yeah, it will work with the new version. But who said it will be released today?
[Samsung Galaxy Mini] aamm95:
Here you are the mine thanks!!!
[Samsung Galaxy Mini] NextLight:
I thought was necessary some ramdisk changes. If I don't remember wrong they had to do so for every new android version..
[Samsung Galaxy Mini] alin.p:
Yes, that might be necessary. But that's not a problem, I will simply repack the kernel with CM10.2's ramdisk if there are any changes.
[Samsung Galaxy Mini] NextLight:
Right. Do you know what kind of changes it needs?
[Samsung Galaxy Mini] A_U:
or u can create 3 branches CM10, 10.1 and 10.2..

compile 3 separate ziamges and repack them in their respective ramdisks..

since usb mount points are different for cm10 and other 2 branches..

and there is slight possibility of bluetooth too..
[Samsung Galaxy Mini] mickey4398:
link http://xdaforums.com/showthread.php?t=2423901
[Samsung Galaxy Mini] aamm95:
It seems it's a lie (fake or cooked rom)... :rolleyes:
[Samsung Galaxy Mini] alin.p:
I'm talking about source compiled CM10.2. When Androidarmv6 releases CM10.2, I will do the appropriate changes to support it.

Actually, the zImage is the same for all the ROMs. The kernel is hardware specific, not ROM specific. Only CM10 has a USB Storage problem, but that is a system problem. When we are talking about filesystem problems in one Android version and everything working in other two different versions, the ROM source should be adapted to the kernel, not the opposite.

Probably some lines changed in the init.rc script and maybe another version of the init binary. But you'll find all this stuff in the ramdisk after unpacking CM10.2's boot.img.
[Samsung Galaxy Mini] Rivaz:
[MENTION=4525074]alin.p[/MENTION]

Can you release first kernel (with s2w and d2w disabled by default), and after that start workin on app for these functions and when it's ready to release the just apk?

I respect your work and hope you keep our galaxy mini updated. It's just a suggestion, because I just wait Badass V2.

Good luck with your projects!
[Samsung Galaxy Mini] deathdekid:
+1
[Samsung Galaxy Mini] alin.p:
No, I can not do this. There isn't just S2W and DT2W, there are more than 15 new features waiting for an app that could control them. Releasing a kernel with all these features needs full tutorials on how to use them. A lot of users will start to complain about "fake claims" because of the inability to use these features. I'm not willing to risk this, I want a successful and clean release.

I see a lot of posts like this on this forum. Believe me, if a developer can't or doesn't want to do something, a million "+1's" won't do **** for his decision. :p

This is just an advice for your future posts, and I wish that more users could read it :)
[Samsung Galaxy Mini] Rivaz:
OK

No problem.

Good luck again!
[Samsung Galaxy Mini] Charlie:
So [MENTION=4525074]alin.p[/MENTION] the kernel now is finished?All done good?Now you are working on the app that will control those great features???
[Samsung Galaxy Mini] Masrepus:
Yes he said so some time ago

Gesendet von meinem GT-S5570 mit Tapatalk 4
[Samsung Galaxy Mini] alin.p:
Nope, not yet. Today I had another great idea, much harder to implement but I think I have a clue on how to do it. Problem is, while implementing it, I noticed that Camera doesn't work. I didn't test it until I had to actually use it. So now I'm trying to fix this problem. Another long night..
[Samsung Galaxy Mini] Masrepus:
Another idea? Cool :)

Good luck with fixing camera

Gesendet von meinem GT-S5570 mit Tapatalk 4
[Samsung Galaxy Mini] Dark Passenger:
[MENTION=4525074]alin.p[/MENTION]

dude use that massive brain power of your and help out here please...

-LINK-

short summary :

erikcas,yajnab,psyke and ounao managed to get the MTD drivers to read and write to the partitions now the partitions load(so I say) but all blocks are marked as bad so there are no usable blocks remaining.

you gonna help...mainly refer to erikcas's post its number 9
[Samsung Galaxy Mini] Jeeko:
15 new features? Yeeessss, now I can't wait more :laugh:
[Samsung Galaxy Mini] prafiles:
Will you consider releasing source of the android app?
[Samsung Galaxy Mini] alin.p:
:)) I think it's already released. I will use an open-source app. Either pedja1's Kernel Tuner, either Benee's Kernel Control

Benee will release the sources later, after the debugging stage so I might use Kernel Tuner.

It will still be a lot of work to do on the app. Our sysfs folders are 90% different than what that app controls, and we have a ton of new controllable features. Anyway, after the release, I'll make it open source. :)
[Samsung Galaxy Mini] Jeeko:
Benee's version is graphically awesome! If he releases the sources for Kernel Control, in future, use this one, it will get a new awesome look to your kernel: amazing features with an amazing app control! :cowboy:
[Samsung Galaxy Mini] Charlie:
The release will be in about a month or you are gona close to upload it soon??
[Samsung Galaxy Mini] alin.p:
Yes, I talked with him about giving me some exclusive access to the sources before the release, but he is in the middle of the work for the new layout plugins and he can't revert to a stable form of the source. I'll use KernelTuner for now, as it is completely stable and already available.

I fixed the camera yesterday, now I am working on Auto-Brightness and after this, I can finally say everything is done.
[Samsung Galaxy Mini] Jeeko:
You're working on a new Badass bootspalsh too?
[Samsung Galaxy Mini] Masrepus:
How do u do autobrightness, if we dont even have light sensor?

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

Gesendet von Tapatalk 4 beta
[Samsung Galaxy Mini] Jeeko:
You're kidding :p we have the light sensor (is the 1st mini-circle on the top of the screen)
[Samsung Galaxy Mini] Rajesh_m:
We only have the proximity sensor!
[Samsung Galaxy Mini] addyhardiana:
This kernel works great in my phone :good:

Can you backporting kernel 3.0.x for our device maybe? :silly:
[Samsung Galaxy Mini] alin.p:
That's because of Fit, Gio and Ace have some different drivers. Have some patience, A_U is compiling for your device.

Well that's because of the collisions between read and write operations. ROW doesn't handle them very well because it needs some functions from 3.0.xx kernel. I backported those functions but because of one single file, the kernel doesn't boot. So I'll keep ROW like this for the moment.

But the updated Deadline in 1.2.2 is better even than the latest version of ROW. Use that until something better comes out.

I heard that Maclaw tried that with no success. I'll try too, just to see if it has potential.
[Samsung Galaxy Mini] aakashasaj:
Hey just a noob question,

this update 1.2.2 is the one in 1st post attachment or update are from abother links?

Read few last pages but dint found any ans in it.

Sorry for such post, But you know.
[Samsung Galaxy Mini] alin.p:
Don't worry, it's better to make sure :D

Yeah it is the link in the first post. You'll find every updated version under Download in the first post.

The only outdated version I keep is 1.0 where it says (for logcat support) if anyone needs debugging.

So in other news, CrossBreeder was updated today. I remodified it. Follow the instruction in the first post to update it.
[Samsung Galaxy Mini] addyhardiana:
I think you have potential to make it boot on our device, I see your argument about kernel is make sense, keep your work, we support you :thumbup:
[Samsung Galaxy Mini] OJ:
Will this kernel work with CM9.1 ??
[Samsung Galaxy Mini] aakashasaj:
Boot splash "mini"is awwwwsome
[Samsung Galaxy Mini] :
Alin.p now you know where you stand (only gpu oc impassible)

I have a few ideas:

more cpu oc (844 full stable) (up to 900 mhz) (864 884 904)

disable hardware overlays

kernel, vm and scheduler (the rest) tweaks
[Samsung Galaxy Mini] alin.p:
Yes, use the link for 4.0 version.

Well thanks :D nice to know someone likes it :))

I didn't say GPU oc is impossible, just that it is already done. :)

I'll post an experimental version with further OC for the "risk takers", probably tomorrow.

Kernel tweaks are being added all the time, I just don't write them in the changelog, VM tweaks also. But the only schedulers I'll tweak will be Deadline and ROW, because the other can't reach their performance no matter how much I tweak them. Probably I'll add some new scheduler if I find a better one.

Thanks for the ideas and stay tuned, I started work on 3.0.xx also :)
[Samsung Galaxy Mini] hsay:
Why not oc to 1ghz it should be stable in Antarctica ...
[Samsung Galaxy Mini] MA-90@:
which kernel version 3.x are building?
[Samsung Galaxy Mini] alin.p:
I think everybody knows that stability doesn't rely only on using the phone without reboots. Stability means low cpu and battery temperature, no battery drain, no hang-ups, no reboots. If he has the balls to try 900, I won't stop him.

There's psyke83's port which boots and kinda works on Galaxy 5. I figured that it would be easier to compile this for our Mini because the two phones have the same chip family. It it 3.0.31 version but if I get it to work without errors I'll keep it updated from the original sources.
[Samsung Galaxy Mini] :
Alin.p you're a good developer, you count the opinion of others (few of these people have been) waiting for more oc. What do you think about tweak vr scheduler. In the last kernel 1.2.2 has increased productivity (3 fps on 3D tests) (dedline) ( antutu 4621 scores without memory card ) ( a lot? ) . Keep up the
[Samsung Galaxy Mini] ast00:
Please keep us informed about EVERYTHING! Even if I have no idea what are you talking about, I would like to know if you get the internal storage mounted. Or whatever that lib does which was not working for other devs...
[Samsung Galaxy Mini] alin.p:
Thanks man :d

Well VR has it's values tweaked already. But as you probably know, benchmarking with VR is very imprevisible because of it's way of handling reads. So benchmarks won't reflect actual performance in long-term use. I'll take a look at the VR algorithm to see if I can improve something, but I doubt it would be better than the actual Deadline. But I'm curious too :)

You mean /data partition? Really? 'Cause I can't imagine how could the phone work without that. Or are you talking about SD, although I'm sure that's called "external storage".

EDIT: News about 3.0:

Compile: After editing the config file to match our device I made the first attempt at compiling the kernel.

The only thing complaining was the LCD driver which I fixed quickly and it compiled succesfully.

Boot: The only thing I see is a white flash of the screen then the phone shuts down.

I'll keep you updated.
[Samsung Galaxy Mini] MA-90@:
Hello alin.p I created new bootsplash image I think it's more beautiful than the currently used.

How about replacing it with this in the next version?
[Samsung Galaxy Mini] alin.p:
Well, you know, we can't discuss tastes :)

But I like light backgrounds, light themes.. yea, I'm more on the "light" side :))

So I'd like to keep my bootsplash as a kind of "brand". But you can always unpack the boot.img and repack it with your own bootsplash to suit your tastes.

Don't get me wrong, this is not about "better" and "more beautiful". It's about branding and having something of my own. ;)
[Samsung Galaxy Mini] L.E.D 26:
Thanks alin.p for your work !!! As everyone says,please keep us updated !! In our CM10.1 RC5 boot 17 seconds ! (only bootanimation)
[Samsung Galaxy Mini] Jeeko:
How are the performances on CM10.1 RC5??

It's almost like CM7??
[Samsung Galaxy Mini] ast00:
It's been a loooong time since last time I saw it written, but I mean /data. I could be wrong... Maybe I should do some research...
[Samsung Galaxy Mini] Jeeko:
The galaxy mini has two sensors (one near the other).

There are both near the samsung label, click the show button
[Samsung Galaxy Mini] Rajesh_m:
If i am not wrong,that is accelerometer,used for detecting motions..

Galaxy mini with a light sensor!!! U must be kidding me man! :p
[Samsung Galaxy Mini] Charlie:
GT S5570: No secondary video-call camera or ambient light sensor

Source: GOOGLE
[Samsung Galaxy Mini] Rajesh_m:
Guys,we are going offtopic.. let us stop it here.. :)

Bottomline: Galaxy mini doesn't have a light sensor ;)
[Samsung Galaxy Mini] alin.p:
I will use that banner that A_U made as bootsplash too.

We have a light sensor. Just that it isn't frontal and individual. It is located inside the Camera hardware. Controlling it individually is a challenge, but I like challenges.

Proximity works by taking infrared reading from those two sensors, none of them is for light detection.

The accelerometer is a whole other thing, located inside the device, invisible from the outside.
[Samsung Galaxy Mini] A_U:
so how will auto-brightness work finally ? a little bit confused..hover over proximity i am guessing ? since i used some apps which controlled brightness using proximity..:confused: but they drank battery like vampires drink blood..
[Samsung Galaxy Mini] Rajesh_m:
So all were wrong( including me;) ).. ;) so autobrightness will work on our mini by using your kernel!? You are the man!! :)
[Samsung Galaxy Mini] alin.p:
The proximity won't be included in the equation. I will use the camera light sensor to read the lux value, then with some simple calculation I will convert that value into a backlight value and pass it to the LCD driver. This is the skeleton of the feature. Of course the light sensor won't read the light all the time. I will use a user-controllable timeout (which will probably be defaulted to 2 mins), and some value test to avoid changing the backlight when it is not needed.

The hard part is turning on the light sensor without turning on all the camera hardware. After this is done, the battery use will be close to zero, as the light sensor will be turned only for 1-2 secs and only if:

1. The screen is on

2. The timeout has passed

3. Probably some more conditions that I'll think of later.

I will implement a Force Adjust sweep too if one want to auto-adjust the brightness before the timeout has passed.
[Samsung Galaxy Mini] NextLight:
Alin Said

So it will use the camera i guess. :p

EDIT: Woops.. Alin beat me and his response is far better :p
[Samsung Galaxy Mini] Charlie:
[MENTION=4525074]alin.p[/MENTION] can you tell us which are the 15+ more features at the kernel just to know??:confused:
[Samsung Galaxy Mini] piterdemon:
This kernel will put mini on definitly new level of functionality :good:

Wytapatano z Ainol Novo 7 fire CM 10.2
[Samsung Galaxy Mini] alin.p:
I can't simply enumerate some cool names without talking about every one of them. You can read about them in the monster huge OP I will have to create at the release.
[Samsung Galaxy Mini] Jeeko:
Every day my curiosity goes up and up and up and up..... :good:
[Samsung Galaxy Mini] Spincervino:
Wow, I like this feature :Q

I think a very good moment to auto-adjust brightness would be when you first unlock the device (or better to say, when you turn on the phone from sleep), then every 2 mins or whatever the user set..

Also a thing to take in mind, but probably will be difficult to, is when you lay down the telephone on a table and the auto-adjust kicks on, it'll set the brightness level to minimum because the camera is covered by the table..

As crazy as it sounds, you may want to also check the accelerometer to know when the phone is lying and with the screen up..

But don't take my words as gold, it is probably very difficult to set it up as i said, and it'll probably make you take longer in the kernel..

I think Franco would be proud of you, if he'd know how much you're doing for this LITTLEbutBIG phone

Thanks Alin <3
[Samsung Galaxy Mini] A_U:
[MENTION=4525074]alin.p[/MENTION]

all compiled well except the ending...here's the error :/ no zimage in the end..

derp much ? :p

LZ4 arch/arm/boot/compressed/piggy.lz4
/bin/sh: 1: lz4: not found
make[2]: *** [arch/arm/boot/compressed/piggy.lz4] Error 1
make[2]: *** Waiting for unfinished jobs....
CC drivers/input/evbug.mod.o
make[1]: *** [arch/arm/boot/compressed/vmlinux] Error 2
make: *** [zImage] Error 2
make: *** Waiting for unfinished jobs....
CC drivers/net/wireless/libra/librasdioif.mod.o
CC drivers/scsi/scsi_wait_scan.mod.o
LD [M] arch/arm/mach-msm/reset_modem.ko
LD [M] arch/arm/oprofile/oprofile.ko
LD [M] arch/arm/mach-msm/dma_test.ko
LD [M] drivers/input/evbug.ko
LD [M] drivers/net/wireless/libra/librasdioif.ko
LD [M] drivers/scsi/scsi_wait_scan.ko
[Samsung Galaxy Mini] alin.p:
Yeah, I thought about that too. Well think about this: you have the timeout set to 2 mins. You are using the phone, at some moment the brightness gets adjusted, the timer resets itself, after some seconds you put your phone in the pocket.

- If you get the phone out of your pocket after 2 minutes, the timer will recognize this situation and adjust the brightness.

- If you get the phone out in less than 2 minutes, it probably doesn't even need to adjust the brightness, as the environment lighting doesn't drastically change in such a little time.

- In the exception cases where the lighting changes in less than two mins, you can always sweep your finger (I'll think about how and where later) to trigger the auto-adjust.

The other problem involving the phone being on a table can be solved in other ways. In that situation, the lux reading will always be 0, and I will simply make this an exception, and not adjust the brightness. I have to think more about this, but using the accelerometer is not necessary, as it would have to read the position all the time and would use too much power.

Your /bin/ folder doesn't have the lz4 binary.

lz4 - 27.95 KB

Move it in /bin/ and set full permissions then compile again :)