yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Fit GT 5670] alin.p:
Updated the kernel to 1.9.2. Everything is fixed. I spent the last 4 hours testing everything I could on CM9 and CM10.1.

If something doesn't work for you, the problem is on your part.

Edit: Please use the updated Interactive governor for now. DynInteractive has a small fault that I missed when I was fixing the code.
[Samsung Galaxy Fit GT 5670] galfit:
Tested now!

Works perfectly! No glitches or lags :) Thank you so much,alin.p!!

So, I've a question: In this kernel there is "Predefined minfree"...It means that the "minfreeV2.zip" is useless??
[Samsung Galaxy Fit GT 5670] alin.p:
Yes, no minfree script needed from now on.
[Samsung Galaxy Fit GT 5670] galfit:
Ok, but i've noticed that the predefined minfree is set to 60mb.... With 1.8 kernel and minfreeV2.zip, the value was 100mb.

I hope that this not decrease the performance!
[Samsung Galaxy Fit GT 5670] alin.p:
The adj values are different and the new Lowmemorykiller is more aggressive so I had to lower the minfree values. I have to lower them a little bit more in the next version, they are too aggressive sometimes. You calculated the MB on the last value. The performance doesn't rely on that value but on the combination between minfree and adj.
[Samsung Galaxy Fit GT 5670] galfit:
Ok understood :)

I've found some bugs:

- With Interactive governor, the ROM is fast but after about 15-20 minutes, when the phone is in deep sleep,when I press the central button,the scren doesn't work, so I must remove battery and re-turn on.

- With smartassH3 governor, the ROM is fast but after about an hour(sometimes more than an hour), when i use it,the phone become freeze and it remains with screen on without response!

Now I use on demand governor,...another review coming soon!
[Samsung Galaxy Fit GT 5670] swat4samp:
So i installed the latest kernel on cm10.1 and everything worked fine until this morning..all of a sudden my phone got stuck, so i hard rebooted the phone and then it ran into bootloop :(..i didnt do anything other than restoring apps from titanium backup app which i did late night..i restored to aosp ics and installed aosp kernel and again the phone didnt boot (stuck on bootanimation)...did i do something wrong Mr. Alin.p?

Edit: Forgot to mention i used interactive governor and sioplus scheduler
[Samsung Galaxy Fit GT 5670] ehsan-black:
same thing for me in AOKP JB and SmartassH3 governor and deadline I/O scheduler! and 68-600 MHZ CPU frequency!
[Samsung Galaxy Fit GT 5670] galfit:
With Ondemand governor, I've the same problems as Interactive :(

Please, someone has 1.8 kernel version???
[Samsung Galaxy Fit GT 5670] alin.p:
Guys, I don't experience any of these problems. And I tested every governor. Anyway, just hope that 2.0 will not have these bugs. I'm fixing every bug I find, but what you experience doesn't happen on my Mini. I think I'll write a new CPU clock structure only for Beni.
[Samsung Galaxy Fit GT 5670] galfit:
Ok thank you for working for us :)

Waiting for a new update, can you post (if you have it) the 1.8 version? Cause it's the only stable release for Fin in this moment
[Samsung Galaxy Fit GT 5670] alin.p:
I can't keep old versions. I compile more than 30 builds a day. Maybe someone else has it.
[Samsung Galaxy Fit GT 5670] hrgh:
here is 1.8 version for AOKP JB and CM 10.1
[Samsung Galaxy Fit GT 5670] Dark Passenger:
[MENTION=4525074]alin.p[/MENTION] are you going to implement SLUB men allocator in v2.0 ...? if not why...?
[Samsung Galaxy Fit GT 5670] alin.p:
I already did this in an older build. It was slower than SLAB.
[Samsung Galaxy Fit GT 5670] Dark Passenger:
whaaa seriously.damn who knew.

PS is USB host possible for our phones.
[Samsung Galaxy Fit GT 5670] alin.p:
What do you mean by USB host?
[Samsung Galaxy Fit GT 5670] Dark Passenger:
well its basically the device can read any attached peripheral flash device acting as a host.

but seems tough as I dont really know(most likely not) if our devices can support power transfer via the usb port if not then an external power source is required for this to work.

PS have you tried SLQB and SLUB+Q allocators they suppose to have better performance than SLAB while keeping more efficient memory management than SLUB.

EDIT USB OTG should work since we got USB 2.0 on our device(architecture includes it).

Hell we can get Wifi direct to work too.(specs require device to have 802.11 a,g,or n).
[Samsung Galaxy Fit GT 5670] alin.p:
I tried SLQB too and it's almost impossible to implement. Too many missing functions.

Every kernel has USB OTG. It's used for recognizing the types of cable connected to the device. I'm using this driver to implement fast charge.

I'll take a look on usb host, seems like a nice feature to have. The memory allocators won't make much difference anyway. I'll focus on the more important stuff.
[Samsung Galaxy Fit GT 5670] Dark Passenger:
USB host will be awesome though if an external power source is required it kindof kills it.
[Samsung Galaxy Fit GT 5670] alin.p:
USB cables have individual wires for electricity transfer and two other wires for data transfer. I think it could be possible to charge the phone while using it for connecting to an USB Host. That's if you connect it to a PC. Connecting it to another mobile device would drain the battery.
[Samsung Galaxy Fit GT 5670] Dark Passenger:
I think you have miss understood me.

eg.

you will be implementing usb otg mode where the device can figure out wether it is the host or the peripheral device.

now while in host mode its acting like the PC when you connect a pen drive to it.thus for the other device the power and data transfer are all taking place at the same instance.(and yes this will drain the battery).

other times when the device recognises that it is a peripheral device and functions as normal.

PS and to sumaries THIS IS AWESOME.(usb otg cable pre-requisited).

PPS can you do something for wifi direct cause thats like an awesomer and better version of bluetooth.or is that only possible with a rom.

---------- Post added at 06:03 PM ---------- Previous post was at 05:57 PM ----------

hey can you make the scrolling cache as default enabled might allow for a smoother scrolling experience.
[Samsung Galaxy Fit GT 5670] alin.p:
I understood what you were talking about from the first time. I just said that the wires for charging are apart from those for data transfering, so we can keep the charging on while connecting the phone in host mode. It might need a bit of hacking, but it has potential.

About Wi-Fi Direct, I don't have wi-fi at home so I can't do that. I wouldn't have where to test it.

Edit: Scrolling cache is set in the framework of the ROM. The kernel doesn't control that. And it's already enabled by default in CM roms
[Samsung Galaxy Fit GT 5670] Dark Passenger:
Okay right now I get it. as i already said if it works its awesome\m/

about wifi direct thats the whole point if you got access to another device with wifi then you should be able to transfer files to without the need of a wifi network(though some rom modding might be required like enabling it in cm settings for our devices).
[Samsung Galaxy Fit GT 5670] alin.p:
The only device with Wi-Fi in my house is my phone. That's why I said I can't test the feature.
[Samsung Galaxy Fit GT 5670] Dark Passenger:
okay you can release a public beta.

you ain't got this device doesn't stop you from releasing a kernel for it(for which I am glad).
[Samsung Galaxy Fit GT 5670] Harpratap:
I had those issues in 1.8. 1.9.2 is perfect for me.

I guess its nothing to do with the kernel, we must be dirty flashing it or doing wrong tweaks.

Don't underclock it till 68mhz..i feel no difference in battery use even when i keep it 122.

Use interactive+sioplus+652/122.

Use greenify app and hibernate everything except IMs. Do not flash any scripts.
[Samsung Galaxy Fit GT 5670] swat4samp:
I wiped cache, dalvik cache after flashing..and do not overclock at all...i use default settings (604,245) and tried all the governors including interactive after which i faced the problems..
[Samsung Galaxy Fit GT 5670] alin.p:
The problem is that you have a more sensible CPU. The PLL overclock makes it unstable, which doesn't happen on Mini. Like I said, I can't test on Fit. I'm blindly developing for your device. :)
[Samsung Galaxy Fit GT 5670] Dark Passenger:
just oc the device most problems will go away.

I'm at 66,652 interactive and sioplus.

and all's well.
[Samsung Galaxy Fit GT 5670] swat4samp:
So u didn't have bootloops or screen freezes after OC??
[Samsung Galaxy Fit GT 5670] Dark Passenger:
yup.

though all system modifications should be done on any other kernel and the flash 1.9.2 no wipes.pretty good.

PS [MENTION=4525074]alin.p[/MENTION] I noticed the cache pressure might not be enough as sudden lag occurs when system retakes memory.
[Samsung Galaxy Fit GT 5670] swat4samp:
Finally

Thanks for the tip [MENTION=4600968]Dark Passenger[/MENTION]..now the kernel is stable as previous builds..found a bit laggy while on interactive governor..switched to smartassh3 and now its good :victory:
[Samsung Galaxy Fit GT 5670] alin.p:
Yes, I know. I raised the pressure right after I released 1.9.2. I just forgot to take care of this before compiling. :)
[Samsung Galaxy Fit GT 5670] Dark Passenger:
cool:good:

can you explain why oc as ^^ swat said works to smooth out the wrinkles and make the phone much more stable...?

PS:

one request if possible can you make a simple app like say <devicename>parts that can have check boxes for enabling and disabling settings.

and make modular undervolting an option(so it can be switched).

thanks.

PPS yes I kanged the idea from cm's mako and marguroparts.
[Samsung Galaxy Fit GT 5670] alin.p:
Like I said, your device has a much more sensible CPU than Mini's. Undervolting and PLL Overclocking was initially intended for Mini's configuration. 604 freq has a higher clock speed than before, and staying there too much, causes instability in your device. Overclocking gives higher freqs more priority and the CPU doesn't stay in 604 longer than it should. I'll create a different clock structure for FIT to get rid of that instability.

About that app, I was planning on making something for enabling and disabling features like Sweep2Wake, Pocket Keyguard, Fast Charge and some smaller ones. But modular undervolting is hard to implement and not necessary at all. While undervolting, our devices have complete stability and the same performances, I tested this myself to make sure it's not just placebo (I'm pretty skeptical sometimes). Why would someone want to disable this?

Also, customizing the voltage values from userspace isn't possible for our device because we don't have an individual voltage regulator. Everything is implemented in the clock structure.
[Samsung Galaxy Fit GT 5670] Dark Passenger:
actually about undervolting I just read that qualcomn overvolts its cpus by default so guess your prognosis on uv is fair.

about clock structure seems fit might need something else...will wait for 2.0 as for the app my suggestion was so that any other rom dev could include in in their roms with the kernel and make slight edits to the settings to access the menu.

on the whole seems 2.0 might be the answer we were waiting for in a more comprehensive fashion.

EDIT :

care to elaborate.
[Samsung Galaxy Fit GT 5670] alin.p:
The ROM developers won't have to edit anything in the app's settings. The app takes care of the kernel's features only. And it will be an individual app, not a Settings-integrated app. Those are made per-rom and I don't develop roms, neither have the time to make an app for every Android version.

I can't tell yet what those smaller features would be, because I have to test if they really improve the kernel before adding them. :)
[Samsung Galaxy Fit GT 5670] Dark Passenger:
cool nonetheless it will be easy to integrate if you opensource the app.

also can these be implemented and will they be useful(just spitballing here).

live oc

Ultra KSM

Deep idle

touch wake

and last.

does the kernel have anything to do with the ability of the video player resolution limit?

:fingers-crossed:
[Samsung Galaxy Fit GT 5670] alin.p:
Live OC - Already done, but I can't leave the values to the users wish. Our SoC needs it's clock values to be calculated by the developer. The average user doesn't know how to calculate that and would mess up the whole system.

Ultra KSM - This seems like a nice feature, will take a look into that

Deep Idle - This is for another type of CPU Architecture. We don't have those functions. Though I implemented something similar in the CPU Idle driver in 2.0.

Touch Wake - I tried to implement this, but it needs a power_key_reset function which we don't have. If I find a another approach, I'll do this.

No, the kernel doesn't control this. Only the video player (or, maybe, the ROM) can control this.
[Samsung Galaxy Fit GT 5670] Dark Passenger:
cool seems 2.0 will be a massive update.
[Samsung Galaxy Fit GT 5670] tarkan-t29:
Flashed the 1.9.2 on my CM10.1, at first, it was very smooth, I did not even overclock it. I then Deoxed all the ROM with apps, it was greatly stable but some time after, it crashed. Even if the system boot correctly and everything is up, it freezes some time after. Did anyone got the same problem? :/

PS: Your work is greatly appreciated and I'm waiting for more, having CM10 on my GFit is a dream that became truth thanks to devs like you :) !
[Samsung Galaxy Fit GT 5670] @ssasin.monish:
First of all awesome work mahn!!!!!! u rock!!!!!!!!

But i m facing a problem as soon as i flash the kernel my camera stops working it says "Can't connect to camera" but after i reboot it 2-3 times it works... I tried this on many cm 10.1 based rom like touchwiz, PAC, cm10.1 by erickas but getting the same issue

Pls help...

Is anyone facing the same problem on 1.9.2
[Samsung Galaxy Fit GT 5670] ehsan-black:
Thanks man! Your trick works well :) . Now it's stable.

But when i flash your in2ext+ patch end in boot loop:( . I don't know problem is in kernel or Script:( . Do you have any soloution for this? :)

PS. Thanks for your great work alin.p! Please don't stop kernel development for our device. You rock! \O/
[Samsung Galaxy Fit GT 5670] hosseinrod:
problem

Hi

I use Badass kernel

and it always isn't stable

sometimes freeze , somtimes reboot ...

and in 652 maximum frequency , camera dosen't work
[Samsung Galaxy Fit GT 5670] Dark Passenger:
hey so the patch is outdated.

The latest cronmod(int2ext) has included the patch for 4.2 and well other stability updates try that.

here

PS a word of advice odex the rom and move apps to sd(native solution).It will allow the apps to perform the best(better than all app2sd scripts I swear!) and the space is still plenty.
[Samsung Galaxy Fit GT 5670] Harpratap:
I didnt get that :confused:

You mean I should not use sd-ext and move apps to my FAT partition using that settings>manage apps>move to sd that we see for some of the installed apps?
[Samsung Galaxy Fit GT 5670] faatoos:
can you make an Kernel for CM7 cuz our phone is poor for RAM and CM10 consum more ram than cm7 and when we open FB or Instagram :S our phone so slowly and some times blocked for few seconds, thnx sorry for my bad english....
[Samsung Galaxy Fit GT 5670] ehsan-black:
hi! [MENTION=4525074]alin.p[/MENTION] i don't know if it's a known bug or not but i flashed AICS kernel patch on AOSP ICS*and stuck in bootloop! even adb doesen't work at all( to make logcat...) . CM9 kernel works perfect!

and again thanks for your great work on kernel for our device:)
[Samsung Galaxy Fit GT 5670] swat4samp:
U mean cm9 kernel works perfect on aosp ics??
[Samsung Galaxy Fit GT 5670] alin.p:
I'll make an individual AOSP ICS version when I'll finish 2.0. ADB works, but logcat doesn't work because I disabled debugging to gain some memory and free some CPU cycles. This is written in red at the beginning of the first thread. You guys should stop being so lazy and read the damn OP :)
[Samsung Galaxy Fit GT 5670] swat4samp:
When can we xpect new kernel sir?? And will u make for aosp, aokp and cm9,cm10 n cm10.1?
[Samsung Galaxy Fit GT 5670] alin.p:
It will work on every 4.0+ ROM. But I can't estimate a release date. I don't know how much time I'll need to finish the remaining work.
[Samsung Galaxy Fit GT 5670] ehsan-black:
sorry about being lazy :( . adb doesn't work for me at all. i tried to access shell (by typing adb shell) but adb says :"-waiting for devices-" . i don't know if others facing adb problem in aosp ics.

we are eagerly waiting for new version. thanks sir! :o

no! i mean CM9 kernel works perfect on CM9 rom. (of course you can add required libraries to aosp and flash CM9 kernel on it)
[Samsung Galaxy Fit GT 5670] swat4samp:
Can u tell me exactly what libraries to be added to flash CM9 kernel on AOSP ??i will try coz right now im on AOSP rom..
[Samsung Galaxy Fit GT 5670] alin.p:
You don't have to add any library. You have to:

1. Unpack the boot.img of my kernel(any version)

2. Unpack the stock AOSP boot.img

3. Repack the boot.img-kernel of Badass with the stock boot.img-ramdisk

4. Flash the resulted boot.img

There are some ramdisk modifications to do, but until 2.0 comes out, you can live without them. :)
[Samsung Galaxy Fit GT 5670] ehsan-black:
how about camera? because i think camera hal is diffrent in aosp ics and cm9. we have some issues in aosp camera.

i use this method for porting roms from gmini.it's also works for using another kernel.

1- replace boot.img of cm9

2- delete these folders and add them from cm9 rom:

/system/lib/modules

/system/lib/hw

/system/usr/keychars (i think it's just for porting from mini)

/system/usr/keylayout(i think it's just for porting from mini)

/system/etc/wifi

/system/etc/ppp

/system/wifi

replace this files from cm9:

/system/etc/vold.fstab

in system/lib:

libarccamera.so

libcamera.so

libcameraservice.so

libcamera_client.so

libCaMotion.so

liboemcamera.so

libseccamera.so

libseccameraadaptor.so
[Samsung Galaxy Fit GT 5670] alin.p:
No no no. The kernel doesn't depend on the Camera HAL or any other library. It just needs the appropriate ramdisk for the respective ROM. What you enumerated there is only for porting ROMs
[Samsung Galaxy Fit GT 5670] swat4samp:
Well that's technical stuff..so better will wait for a stable 2.0 release :good:
[Samsung Galaxy Fit GT 5670] 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 Fit GT 5670] galfit:
Wow, great job man :)

Have you resolved the problem with app-freezing on CM10.1 rom?
[Samsung Galaxy Fit GT 5670] alin.p:
Theoretically, yes. But I don't have a Galaxy Fit, neither am I using CM10.1 to test this.
[Samsung Galaxy Fit GT 5670] swat4samp:
What exactly is the function of sweep2wake?? Is it like sweeping the phone wakes up the device ??
[Samsung Galaxy Fit GT 5670] alin.p:
It allows you to sweep your finger in the middle of the screen from left to right to wake the screen. Much easier than pressing the power or home button.
[Samsung Galaxy Fit GT 5670] swat4samp:
Excellent...now i cant wait at all :fingers-crossed:..is it possible to make double tap wakeup just like in lg g2??
[Samsung Galaxy Fit GT 5670] alin.p:
It may be possible with some workarounds, but it would make the Touchscreen driver work slower and possibly drain the battery because it would have to continuously use timers to count how many msecs have passed since the last touch. I think Sweep2Wake is enough for now. I'm working on something new, based on this feature so stay tuned :)
[Samsung Galaxy Fit GT 5670] Utkarsh-ezzo:
aosp ice kernel not booting

i am on aosp ics stable buit by superman,

i installed aosp ics version of kernel but the phone is not booting its stuck at bootanimation, neither i am able to see the new bootsplash its showing that old samsung boot splash.

any solution OP??
[Samsung Galaxy Fit GT 5670] alin.p:
Use the stock kernel until I release 2.0. 1.9.2 is ages behind, I can't solve any problem about this version anymore.
[Samsung Galaxy Fit GT 5670] Utkarsh-ezzo:
ok will wait
[Samsung Galaxy Fit GT 5670] hrgh:
Can't wait fo V2 :D
[Samsung Galaxy Fit GT 5670] yajnab:
The feature is good but the touchscreen needs to be semi active which you cannot stop. It will pull down the battery backup of the device. And moreover sweeping will take you to the lockscreen which you again need to unlock with second sweep. I dont think this feature is anything more than a cosmetic change

.

---------- Post added at 11:12 AM ---------- Previous post was at 11:03 AM ----------

YOu can do one thing. Make two drivers for the touchscreem.

In the makefile

you do like this

obj-$(CONFIG_TOUCHSCREEN_SYNAPTICS_I2C_RMI)	+= synaptics_i2c_rmi.o

obj-$(CONFIG_TOUCHSCREEN_SYNAPTICS_I2C_RMI_S2W	+= synaptics_i2c_rmi_s2w.o

Name the new touchscreen driver synaptics_i2c_rmi_s2w.c where you include the changes for the sweep to wake. An app can be developed later which can make a function to swap bewteen two drivers

More modification can be made making a synaptics.c

which will include like this

#ifdef CONFIG_S2W

#incluide "synaptics_i2c_rmi_s2w.c"

#elseif

##incluide "synaptics_i2c_rmi.c"

Third step will be just doing it in defconfig

CONFIG_S2W=m

This will make the S2W a module keeping the S2W and modified syanptics drivers out of the kernel thus not slowing the kernel down and app modulation for users who want to use it or not.

Keeping s2w on for full time will degrade the quality of the kernel
[Samsung Galaxy Fit GT 5670] alin.p:
I understand your point but if you would have taken a good look through the code, you'd have seen that there is enough made to ensure that battery life will not be affected, and that separation of the drivers is unnecessary and not so possible anyway.

The touchscreen driver will not be active if the phone is suspended and the proximity sensor is covered, so no battery life wasted here. Also if the proximity is not covered, the touchscreen algorithm stays in an idle state until the loop for touch checking is broken, again, battery life wasted will be zero as this loop can function in deep sleep.

Then if a touch is detected, there are other interrupts that would send the algorithm back into the idle loop if a sweep is not intended. All this, by continously staying in deep sleep.

If you are concerned about the lockscreen, it can be easily disabled in the Settings. You don't have to worry about accidental unlocks in the pocket either, the kernel has a Pocket Keyguard which disables the wake keys when proximity is covered.

All this stuff is user controllable. I'll make an app for controlling these features. You just have to switch Sweep2Wake and DoubleTap2Wake off in the app and the touchscreen driver will function like the stock one.
[Samsung Galaxy Fit GT 5670] Dark Passenger:
hey can you implement SLQB memory allocator in next build(2.0) cause I believe it's suppose to be better than SLAB for low mem single CPU devices.
[Samsung Galaxy Fit GT 5670] alin.p:
Actually I did a thorough research on all this memory allocator thing. SLQB is used by most of the kernel devs because it has evolved as a trend. But SLUB is much better, there is a thread here on xda that benchmarks all these allocators. SLUB-Q should be even better.

But I spent two days implementing the SLUB allocator, only to find out that the kernel doesn't boot with SLUB. It compiles without any complain, but it never gets past the bootsplash. In that state, there's no way to debug without a special connection which I don't have, so we're stuck on SLAB.