yashsingh1/xdaforums huggingface dataset:
[Galaxy S I9000 Android Development] rlorange:
@Zak.

Ahhhh this is the open source spirit! Trying out your version of Talon shortly....

Curious how did you add back 1.3ghz? I thought it was still unstable with talon-crew code. Only Damian's kernel had stable 1.3 oc I thought... and he doesn't like to share code...

**Simply Honey3.5, Talon 0.2.kernel 1.2ghz, ZSJV5 modem**
[Galaxy S I9000 Android Development] 94kram01:
I just cannot come to use it... It boot loops... I even repartitioned my phone, and then flashed, but it just keeps flashing the Android text.

I had a question more, can any of you compare it to fugumod4? I know, I know, do experience it yourself, but I just cannot... So any ideas, which is better? And I do know its only dev state yet
[Galaxy S I9000 Android Development] rlorange:
**** yeah! Zak you are THE MAN! your modded talon has serious claws!!!!!

**Simply Honey3.5, Talon 0.2.1 kernel 1.2ghz, ZSJV5 modem**
[Galaxy S I9000 Android Development] paratox:
@ zachs build: had one reboot with standard voltage. it also stucks at 1GHz at sleep, no down scaling below. while in use / screen on it is all the time at max frequency. this behavior sucks battery like hell. i`m back on talon. but i would be happy to test another more stable build from zach! :)
[Galaxy S I9000 Android Development] maisi:
According to this thread noop or sio are the way to go ;)
[Galaxy S I9000 Android Development] rom08:
Thanks for the link
[Galaxy S I9000 Android Development] gonova:
Thanks a lot for your confirmation. So now I have full confidence to eliminate this sucked Gallery :D
[Galaxy S I9000 Android Development] gonova:
In the above thread, other users' tests show that noop is even better than the current default sio in Talon.

And I also saw about BFQ many times in many other kernels posts too. It seems that this is the fastest the most efficient one, but I have no knowledge to judge. It seems to me that BFQ is little faster and smoother in my personal feeling.

But why existz and zacharias.maladroit don't use BFQ as default if it is the best ? :confused:
[Galaxy S I9000 Android Development] Blondasisko:
No issues after 2 days

After initial failure with 0.4.1 I flashed 0.4.2 (no issues) and for a trial 0.4.3 OCed to 1200. Everything smooth after 2 days. Memory management good. GPS, BT, Wifi without any issues. A beer is coming :)
[Galaxy S I9000 Android Development] fishcake13:
quick report after 2 days..... only had one issue where phone didn't wake up from deep sleep. other then that everythings working and smooth @ 1200mhz
[Galaxy S I9000 Android Development] jaiiscool:
You can use the SGS Tools from the Market and replace stock gallery with modded gallery....

It eliminates the problem completely. I use it myself.
[Galaxy S I9000 Android Development] LockeOn:
How about this for our I9000 - http://www.xda-developers.com/android/enter-godmode/ Mabye yaffs2+ext2 would bring us closer to CM7 I/O speed since it uses similar yaffs2+ext4?
[Galaxy S I9000 Android Development] .:Crack:.:
http://xdaforums.com/showpost.php?p=16034959&postcount=13
[Galaxy S I9000 Android Development] theos0o:
Since updating to 0.4.3-1200 (from 0.3.1) adbWireless ain't working.. :(

When I push 'adb connect blabla' on PC, it won't connect.

Tried rebooting my SGS, re-installing adbWireless, wiping app data. Nothing.

The app seems to be working fine on the phone side. Gets SU and appears to be ok.

Anyone knows a solution/workaround/alternative for wireless adb connections? :D
[Galaxy S I9000 Android Development] zacharias.maladroit:
Hi benjieg,

thanks !

battery-efficiency, security, performance & stability are my main goals for every kernel ^^

please don't forget that it's existz' baby after all :)
[Galaxy S I9000 Android Development] betoNL:
Well, not every sgs is the same. I have been testing some schedulers and VR feels good....

But I think that at the end, I will be going back to "Deadline"
[Galaxy S I9000 Android Development] zenosteam:
What does it do deadline?
[Galaxy S I9000 Android Development] betoNL:
Talking about (I/O) schedulers:

noop / deadline / cfq / sio / vr / bfq

Read some pages back
[Galaxy S I9000 Android Development] :
i have found some features that could be nice for talon...

-TinyRCU

- ondemand governor from Galaxy S2

- jpeg driver table from galaxy tab, more vivid photos

- removed dvfs from usb driver, no longer lock @200MHz when USB cable is connected
[Galaxy S I9000 Android Development] flypubec:
When having /system mounted read-only (by default) I see the following kernel error messages with dmesg

<4>[ 676.032392] [RFS:CRT:10:VolWriteVolume@/linux_volume.c#750]Volume is mounted read-only
<4>[ 682.032208] [RFS:CRT:10:VolWriteVolume@/linux_volume.c#750]Volume is mounted read-only
<4>[ 688.032226] [RFS:CRT:10:VolWriteVolume@/linux_volume.c#750]Volume is mounted read-only
<4>[ 694.032229] [RFS:CRT:10:VolWriteVolume@/linux_volume.c#750]Volume is mounted read-only
<4>[ 700.032471] [RFS:CRT:10:VolWriteVolume@/linux_volume.c#750]Volume is mounted read-only
<4>[ 706.032230] [RFS:CRT:10:VolWriteVolume@/linux_volume.c#750]Volume is mounted read-only
<4>[ 712.032203] [RFS:CRT:10:VolWriteVolume@/linux_volume.c#750]Volume is mounted read-only
<4>[ 718.032160] [RFS:CRT:10:VolWriteVolume@/linux_volume.c#750]Volume is mounted read-only
<4>[ 724.032213] [RFS:CRT:10:VolWriteVolume@/linux_volume.c#750]Volume is mounted read-only
<4>[ 730.032256] [RFS:CRT:10:VolWriteVolume@/linux_volume.c#750]Volume is mounted read-only
<4>[ 736.032331] [RFS:CRT:10:VolWriteVolume@/linux_volume.c#750]Volume is mounted read-only
<4>[ 742.032189] [RFS:CRT:10:VolWriteVolume@/linux_volume.c#750]Volume is mounted read-only
<4>[ 748.032300] [RFS:CRT:10:VolWriteVolume@/linux_volume.c#750]Volume is mounted read-only

When I remount system RW, this is gone.

Seems that something tries to write to /system every 6 sec

Can someone please confirm or is this just me.

Simply type "dmesg" in terminal emulator or in adb shell

I am stock JVQ with talon 0.4.3

This also happens regardless of lagfix

EDIT: If I remount the /system as rw and then back as ro the messages are also not appearing anymoe.

I've tried to put the remount rw and then ro to init.rc (I've rebuilt the kernel) and it didn't help.

EDIT2: It seems that the system must be at least 6s in rw, so this thing, which happens every 6s is able to do it's job and then it does not bother anymore.

Quick and dirty solution was to add the following at the end of /bin/post-boot.sh (and recompile the kernel of course)

mount -o remount,rw /dev/block/stl9 /system
sleep 7
mount -o remount,ro /dev/block/stl9 /system

I also notice the the mounting commands in .rc scripts will not work when mount is taken from $PATH (/system/bin/mount), since the syntax for /system/bin/mount is different from the one for /bin/mount (which works)
[Galaxy S I9000 Android Development] existz:
IMO Classic RCU gives better performance than TinyRCU, and SGS2 ondemand is identical to SGS, you can diff the 2 and there's literally no difference, exact same file....don't believe everything u read
[Galaxy S I9000 Android Development] :
Okay. What features can we expect in the next few weeks? :-)
[Galaxy S I9000 Android Development] rlorange:
Anyone having issues getting Tegrak oc app to load its kernel module on public release 0.4.3?

I just tried it for the first time on the latest beta 0.4.4.1 test and its not loading

**Simply Honey3.9, Talon kernel1.3ghz**
[Galaxy S I9000 Android Development] madd0g:
Flashed the non O/C 0.4.3 over DarkCore kernel on ext4, removed "darkyram" script, sdcard speed tweak, on F1 mod v9 JVP ROM. Set the I/O scheduler to noop, works smooth as **** :] Thanks for this !
[Galaxy S I9000 Android Development] LockeOn:
@Existz

How about implementing God Mode http://www.xda-developers.com/android/enter-godmode/ - yaffs2 + ext2 to Talon?
[Galaxy S I9000 Android Development] rlorange:
Don't know if this screenshot will upload showing the tegrak oc app error.

Edit: nope phone browser is not making it easy to attach an image.
[Galaxy S I9000 Android Development] .:Crack:.:
I'd think existz won't include it.

One reason would be that ext2 leads to data corruption.

So if he thinks about if i bet he'd only do it withh yaffs2+ext4.

edit: yaffs2+ext4 gives crappy results.
[Galaxy S I9000 Android Development] jontoo:
I'm with Tlon 0.4.3 no OC and tegrak's modul is loadig OK, no problems here
[Galaxy S I9000 Android Development] rlorange:
No oc version? I'm on the 1200 version maybe that's the problem...ill try non oc version. Thanks

**Simply Honey3.9, Talon kernel1.3ghz**
[Galaxy S I9000 Android Development] theos0o:
Bump - anyone?

Tried another app for that too, but still PC can't connect.

Anyone can try if it's ok on his phone?
[Galaxy S I9000 Android Development] Netman_:
Is any chance to add touch screen sensitive from galaxian? :)
[Galaxy S I9000 Android Development] rlorange:
Still no tegrak overclock action on the non oc version... weird

**Simply Honey3.9, Talon kernel1.3ghz**
[Galaxy S I9000 Android Development] jlieu:
Is it Possible increase device Ram by Running app background Data on Sd card?

Share Memory to RAM.

Adding some new feature to this kernel will be nice! such as Touch sensitivity mentioned by Netman.
[Galaxy S I9000 Android Development] zacharias.maladroit:
Hi existz,

I have tons of additional patches (only compile-tested not tested in practice on the device yet)

(located in my cm7-kernel repo)

Link

:

general-fixes

PM01

XZ-decompress

RCU01

autogroupv4_new

especially the autogroupv4_new branch might be interesting since it contains the "automated per session task groups" (instead of per tty - what is currently used in talon) and several fixes - and

most importantly

the fix for the memory leak :)

since I need to focus on other stuff & won't have much time for kernel development

I thought maybe you guys could test what you like & add it to Talon

Thanks !
[Galaxy S I9000 Android Development] betoNL:
Smooth as **** !:D:D:D:D:D
[Galaxy S I9000 Android Development] zacharias.maladroit:
seems to work:

RCU, general-fixes, PM, autogroupv4_new

added to snail kernel-tree and running on my phone right now

(as monolithic commits however)

snail13_t5

not sure about stability & data integrity

but the phone boots up ;)
[Galaxy S I9000 Android Development] madd0g:
Same here, the connection just dies on the phone when I click the button.
[Galaxy S I9000 Android Development] jaiiscool:
Today out of nowhere, my wifi would not turn on, just says error in the settings menu.

I tried to re-install the ROM to no effect.

I am now installing everything from scratch after re-partition and everything, lets see............

EDIT: It worked, started from scratch and all is ok till now.
[Galaxy S I9000 Android Development] ltylty123:
Anyone still encounter reboot during call?

I had 2 auto reboot last night while having a phone conversation. Battery of phone was low at that time(10% left).

Had 3 phone conversations this afternoon with battery at 70+% without experiencing reboot.

Here are my phone specs

Galaxy S I9000

Juwe Rom 5.2 (without S97newramscript)

Talon 0.4.3 non-oc (ext4)

Undervolted:

1000mhz - 1250mv

800mhz - 1150mv

400mhz - 1000mv

200mhz - 875mv

100mhz - 875mv

Other than this, phone is working perfectly fine without any other reboot or hang.
[Galaxy S I9000 Android Development] :
@zach: i have flashed to snail13.t5 and this kernel is fast, very fast... i hope, that this new patches will be included in the next talondev kernel...
[Galaxy S I9000 Android Development] doomsdaycs:
talon could you also add the updated graphoc driver to the source code.. it has a lot of performance benifits.. here is the link http://www.lg.com/global/support/opensource/opensource-detail.jsp?detailCustomerModelCode=LGP920 ..thank u
[Galaxy S I9000 Android Development] Mull1s:
I havent used any custom kernel now for a while so i have some questions about this one (a friend told me talondev was the best ^^)

What do i have to do to run 1.2GHz stable and 24/7? Will it change back to normal on reboot? I know about the app Control Freak, but what is the best settings?

What kernel-settings should i use in recovery for speed/stability?

I am currently on the firmware JVH, will this kernel work with it?

I have seen that Odin has had many new releases, which version is recommended?

Thanks

:o
[Galaxy S I9000 Android Development] existz:
Its from froyo source. .. going to take someone with more know how than me to port a driver from different device + different kernel/os platform, even though its still sgx540, its alot different than ours
[Galaxy S I9000 Android Development] Grillmaster:
Hi, i try this 4.3 version and its fast, but some parts does not work.

- gallery not working

- system properties (sound)

- video not properly work, very green display, scrambled...

(running 2.3.4 ficeto rom (jvp) )

So I go back to SpeedMod, but keep an eye on this kernel, has a lot of potential.

Wait for the next version :)

Cheers
[Galaxy S I9000 Android Development] zenosteam:
what , hummm really strange
[Galaxy S I9000 Android Development] Cy4n1d3:
Those are most likely not related to the kernel. Settings and gallery work fine here, green tint though might be because of the kernels display driver.
[Galaxy S I9000 Android Development] Hrithan2020:
Regarding the green display, do you have autobrightness enabled?

Also, have you changed the gamma values? If so , try resetting all to 0 and see.
[Galaxy S I9000 Android Development] madd0g:
Hm, also restored back to DarkCore, was getting quite some microlags after a day.
[Galaxy S I9000 Android Development] betoNL:
Nope, no reboots and no issues whatsoever, also no OC only UV and smooth as butter on RFS

Working hard to find issues , and that's why I went testing also many versions of the Galaxian kernel, since the list of bugs over there seems to be bigger

And here are my conclusions (some quotes first from the galaxian thread) :

I rest my case :rolleyes:

.
[Galaxy S I9000 Android Development] existz:
Yea, but im on ext4, I ALWAYS use ext4, and never experience any of the issues either, so I really really dont think its an ext4/rfs issue...it dont matter which one your on,...your on rfs with no issues, im on ext4 with no issues...so going as far as saying RFS gives less problems, i HIGHLY disagree...like I said, im always on ext4 and never experience any of these issues either...99% of the time its user error
[Galaxy S I9000 Android Development] zacharias.maladroit:
hm, RFS - interesting :cool:

so could those that get reboots during calls please try to convert their FS to rfs and see whether that solves it ?

there are sooooooooo many factors that could contribute to this issue :\
[Galaxy S I9000 Android Development] Mangus_U*RA:
the memory management is awful, I must say it...always about 40 Mb free and so...the phone isn't responsive as it should be and there are so much micro lag,
[Galaxy S I9000 Android Development] existz:
There have been reports on RFS as well, from a few on IRC
[Galaxy S I9000 Android Development] existz:
As ive stated multiple times before, we know and we are working on it...so please no more reports of this..its aware of

There does seem to be a memory leak and we are trying to locate it
[Galaxy S I9000 Android Development] zacharias.maladroit:
try the new autogroup + fixes :)

(perhaps that helps)

I have no proper access to my repo otherwise I would push it
[Galaxy S I9000 Android Development] existz:
Already on it...its in 0.4.x branch...still testing out the general fixes before commiting
[Galaxy S I9000 Android Development] betoNL:
I read your answer over there also( galaxian thread).

Just to enphasize I mentioned Ext4, but it could be ext2 or any other file system, it doesn't matter...

What I meant is that something goes wrong when you try to convert a proprietary file system ...

What is more interesting, why you and other developers like Lukiqq, try to fix "bugs" that actually dont exist since as you say 99% of the time its user error, you dont have those bugs (99%) I dont have them (100%) and many dont have them as well?

And saying that all other Android devices use Ext4 with no probs, makes no sense either...The other Android devices didnt have to convert samsung's proprietary file system to get EXT4 ..

But never mind, maybe you are right, maybe all of this is out of my league, so I am going to really:o rest my case now...at least on this thread :D

Cheers

.
[Galaxy S I9000 Android Development] Tatsuya79:
No problem here concerning memory but I've kept Juwe's script in init.d folder.

You could use it while waiting for a new version, no micro lags and 100mo free after 3 days.

Is the difference in voltage real or just a bad report before? (1275mv for 1200MHZ before, 1300mv now)
[Galaxy S I9000 Android Development] existz:
I get what your saying and agree with some of it, but my point is that most of the reported problems are on both ext4 and rfs...so alot of the time its not caused by one or the other, or even just the converting ... your point was your always on rfs and never have problems, mine is tthat I always use ext4 and never do either ..its usually always something more, for example the BT issue..it happened to most people and you stated since your on RFS and you don't have the problem, basically stating that's the reason why you don't have the problem...which I never had the issue either, nor the cpu scaling issue some reported... so its clearly not the reason why one would have the issue or not...im just pointing out that using ext4 or converting filesystem all together is not the reason why there's a problem, since it happens to people both on rfs and ext4, as well as people not having the problem which who are on ext4 and rfs..

Im not saying ext4 is better, just that its not the root to all evil as you state, problems usually happen regardless of what file system they are on... Most of the time when there's a problem, then that particular thing would happen to everyone...so if its converting or ext4 thats the problem, then it would happen to everyone who's on ext4, otherwise something else is causing it...
[Galaxy S I9000 Android Development] Mangus_U*RA:
Sorry you're right, I've flashed from scratch today and I had never reported enything about 0.4.3 yet :)

........zip...........

:P
[Galaxy S I9000 Android Development] chrystal0925:
Where is boot animation stored on 0.2.2? I hate the android logo

from my vibe with honey love
[Galaxy S I9000 Android Development] existz:
Add custom bootanimation to /system/media/ and name it sanim.zip
[Galaxy S I9000 Android Development] rlorange:
@Existz any ideas on tegrak overclock not working? Sent you a pm with the error message

**Simply Honey3.9, Talon kernel1.3ghz**
[Galaxy S I9000 Android Development] existz:
Not sure, works fine for me
[Galaxy S I9000 Android Development] existz:
Posted this in Captivate section, figured id post here too..

Next version should have a few new features..so far been messing with ...

Updated sched_autogroup v4 patch with a few new upstream fixes (fixes memory leak in sched_autogroup)...not sure yet if that fixes the actual memory leak ...

Switched to TinyRCU (for smaller memory footprint) ...plus some new upstream fixes to RCU/TinyRCU ---still needs testing

Added and switched to XZ kernel compression; also switch initramfs compression to none (cuts kernel size down to 5.5mb!) ---still needs testing

Plus some general fixes from zacharias.maladroits snail kernel

...which we are looking into the actual memory leak and can hopefully locate it soon...(hopefully the new sched_autogroup fixes will fix it)..

Lastly, Shane87 has msg me and has made some progress on his/our new app 'MemoryFreak'... which will eliminate everyones LMK settings issue, you will be able to select from several different LMK presets from within the app.

Also fixed USB charging lock to 100mhz instead of 200mhz.
[Galaxy S I9000 Android Development] jeebspawnshop:
That's a helluva gift-bag, Ex! Thanks to you, Zach and the team for all this hotness.

Looking forward to it real hard.
[Galaxy S I9000 Android Development] existz:
And we are only on 2nd test, there's alot more to come!
[Galaxy S I9000 Android Development] Grillmaster:
Hi, thanks for the advice

I had nothing changed, mean flash the kernel from SpeedMod reboot, and that's it and enabled vodoo.

Hmm may a vodoo issue?

Because reflash to SpeedMod and all works, but I like that kernel with all the Options....

Will try later again with vodoo disabled to check if the issues still there.

And autbrithness was on..

Cheers
[Galaxy S I9000 Android Development] awesomeandroid:
0.4.3 is it JVQ compatible? :confused:
[Galaxy S I9000 Android Development] Hrithan2020:
Yes!!

It is compatible
[Galaxy S I9000 Android Development] ImJamIN:
Hi,

when I load this kernel (cwm3), are voodoo lagfix already enable ?

I would like to use RFS (no EXT4) and I don't want to confert rfs to ext4 and rfs again.

How can i do this ?

Thank you.
[Galaxy S I9000 Android Development] Blondasisko:
No, just flash

If you are on rfs it will stay on rfs.
[Galaxy S I9000 Android Development] Blondasisko:
I guess you can do it from many other apps, like Autokiller Memory Optimizer, Android Assistant, System Tuner, etc. And it works AFAIK, I am using Autokiller.
[Galaxy S I9000 Android Development] Grillmaster:
I tested again and now sound properties works, don't know why but work now.

Green display come from brightness, don't know why was set to zero, and fixed.

So all looks fine, continue testing...

Cheers
[Galaxy S I9000 Android Development] ImJamIN:
Thank you. I'll try it.

So, I MUST go an advance to enable ext4 ?

When I read on 1 page that voodoo lagfix is enable, and on title that talon use ext4, I've blocked flash.
[Galaxy S I9000 Android Development] LockeOn:
How about using Supercharger V6 script in order to control ram management? It is supposed to work with any rom and any kernel.
[Galaxy S I9000 Android Development] Atom960i:
@existz

just if you are interested... I've overclocked 4.2 up to 1.6 GHz with tegrak and its rather stable. Lol, will try to oc higher up to 1.9

Question: when phone is off and i'm plugging in charging cable, the big fat battery appears on display (bigger than stock) for about 30 sec and i can't turn on phone during it, i have to wait till it dissapears (then stock battery animation comes) and only then i can turn phone on.
[Galaxy S I9000 Android Development] jocke_lulle:
Hi

i flashed jetpack-rom and that rom includes talon kernel. I came from stock odex jvq (only rooted with speedmod) and the phone reboot itself from time to time (2-4 times aday). Is this happen for some other that uses this kernel?
[Galaxy S I9000 Android Development] pikachu01:
What UV settings are you using?
[Galaxy S I9000 Android Development] jocke_lulle:
I havent changed any UV settings. I have just used it as it is.
[Galaxy S I9000 Android Development] TheGoD:
With all that bug-reports and complaint's coming in (mostly constructive) I thought I share real quick that I really love the new color configuration! No more red tint in low brightness settings and everything looks real good and vivid.

Other than that, the kernel is really fast and stable as expected. Didn't use the phone yet, thou...
[Galaxy S I9000 Android Development] existz:
V6 works, and is better to use than just a normal "ramhack" script as it actually sets the values correctly and not just the kernel parameters.... but it wont be the same as what im talking about...you will be able to adjust swappiness, zram size..etc..etc..which you cannot do with normal "optimizers"... Using swap and/or zram changes how it uses memory management versus a kernel that does not use swap/zram.. so a script or app that's made for one that does not use those will not give the same results. That's why we HIGHLY recommend NOT using these "ramhack" scripts, it will not give the same performance as say, on speedmod or a stock kernel...Im not saying they will suck or not work, just its a different ballgame and might not perform as it would on other kernels ...so that's why we are making our own, especially for Talon