yashsingh1/xdaforums huggingface dataset:
[Galaxy S I9000 Android Development] pikachu01:
Actually, you could flash Semaphore first (which will remove your boot sound automatically), then flash Talon again and try Voodoo lagfix.
[Galaxy S I9000 Android Development] jlieu:
Sharpness and color needs improvement. :)
[Galaxy S I9000 Android Development] pikachu01:
To each his own. Color and sharpness looks good on my phone. :)
[Galaxy S I9000 Android Development] jlieu:
Which setting you use in voodoo color setting?

voodoo color profile?

how about Screen v1 gamma hack and SRB multipliers?

mine is

1) Screen v1 gamma hack: (try to +4 each if you feel bad about it)

-50 red

-53 green

-44 blue

2) SRB multipliers:

Red ="2300875360"

Green ="2300875360"

Blue ="2709919680"

The color become true color as black is black , blue is blue and so on. no white tint or yellow tint.
[Galaxy S I9000 Android Development] pikachu01:
Voodoo Profile

Red = 1901846320

Green=1996670000

Blue = 2484945440

Red= -25

Green = -27

Blue = -27

It looks good for me but it might differ for some people depending on their own phones. Not every SGS have the same quality of AMOLED displays.
[Galaxy S I9000 Android Development] folkg:
Memory still seems to be leaking, zram on. I'll turn it off and try.
[Galaxy S I9000 Android Development] SamHaLeKe:
@ existz

Bug report for 0.4.4.13-15

While Tethering true USB the connection is regularly lost (every few minutes). It seems the USB connection gets broken and so is Tethering. Sometimes the whole USB connection is lost and I have to replug the USB cable.

This is for all versions

after

0.4.4.9. I tested it on 0.4.4.9 and there everything works without dropping the connection. Also tested it on latest SpeedMod on there it works fine to. So this is most definitely something in latest test versions of the kernel.

Something to do with latest voltage changes perhaps?

Can you please take a look at this. I will test any new version and give feedback on this thread.

grtz,

-sam-
[Galaxy S I9000 Android Development] betoNL:
I think we need a plumber
[Galaxy S I9000 Android Development] Rootax:
For the record, on snail 16, I've no memory leak. Don't know if that can help you.
[Galaxy S I9000 Android Development] Flynny75:
I think I still have it. I cant disable ZRAM... Phone goes into 'Safe Mode'. Never seen this before...
[Galaxy S I9000 Android Development] betoNL:
Your phone is suffering from EOCF ( Exhaustion due Obssessive Compulsive Flashing)

Cure:

Stick with one version of one Kernel and one version of one rom....then do like most developers: Get a sgs2, or a HTC Sensation or a Nexus Prime or something like that:D:D:D
[Galaxy S I9000 Android Development] existz:
Did you flash with sgs kernel flasher? I've seen this happen awhile back, just re-flash... I would flash with Odin/heimdall
[Galaxy S I9000 Android Development] Flynny75:
Nope, through CWM. What is this safe mode? Happened when I set ZRAM to 0
[Galaxy S I9000 Android Development] psyren:
This may have come up many times now, but has anyone experienced the wifi turn on bug?

I've searched for solutions, but they're either useless or unrelated.

Seeing as this is the most recent kernel I've had the issue with, I'm hoping someone could shed light onto the issue.

Running 0.4.4.15 non-OC on SURFACE 3.1.
[Galaxy S I9000 Android Development] existz:
Try turning it on in settings, with it erroring out from dropdown/power widget its just something we are gonna have to live with for awhile, atleast it fixes the reboot issue, but introduces this... if its still happening from settings menu, try clearing both caches and reflash the kernel...this seems to help as its a random thing from time to time
[Galaxy S I9000 Android Development] jaiiscool:
For the first time after a zillion versions, my phone went into sleep of death, it would not wake up, i had to force restart via long press power button. I dont uv.

Using #15 1200mhz
[Galaxy S I9000 Android Development] shaarky:
With the latest version my BT (rSAP, Handsfree in car) problems are gone now.

Also during the night (8hours), when I'm disabling with Tasker data mode,I'm loosing only between 4-3%, which is excellent ! :D

I'm able to UV significantly, which was not possible with other kernels - the only exception is on 1200MHz, where I have to use 1300mV, instead of previously stable 1275mV - didn't know then Kernel can influence it.

So currently I'm on 1200MHz - 1300mV (-0), 800MHz - 1125mv (-75), 400MHz - 950mV (-100), 200MHz - 800mV (-150), 100MHz - 750mV (-200). (using Voltage control for setting it).

Remarks :

Display colors - I'm still trying to find "correct" values, 1st time facing such difficulties, mainly fighting with RED color and with the overall contrast combination.

Brightness changes seems to be somehow more random then really initiated by the measurement of the sensor. Sometimes it's "blinking" in 2-3sec intervals - can someone else confirm this as well ?
[Galaxy S I9000 Android Development] JhonnyGo:
Never had a snappier phone!

But I'm still having that green effect while turning off the screen.

Is it for everyone or I'm the only?
[Galaxy S I9000 Android Development] ale0crysis:
I' m using your same settings just 1.2 Ghz on 1275 mV without any issue

Incredible!
[Galaxy S I9000 Android Development] pikachu01:
Just had a forced reboot on sleep after 12 hours of uptime with 0.4.4.15. Not sure what's changed as I've never had this problem after 2 days of uptime before this.
[Galaxy S I9000 Android Development] :
Hi existz

can you look into the sources from galaxian? lukiqq reworked the OLED driver without Voodoo Color and for me the result is even better that voodoo color from talon 0.4.3.

here are some points from lukiqq's changelog:

- reworked OLED driver (once again...), everythings should be fine at start right now, vivid colors (but not oversaturated), nice brightness and contract, white is white, black is black (removed Voodoo Color support)

- Speedmod UI MDNIE values for less sharpness

- adjusted RGB individually on every brightness step (29 steps...uff)

- more fluid brightness steps (less jumps)

- sharpness increased by ~15% (now should be OK)

- for me the screen is now looking better than it was with Voodoo Color (more natural)

thanks

Tobi
[Galaxy S I9000 Android Development] omnia-one4all:
I'm on same version and phone has been up for 18 hours
[Galaxy S I9000 Android Development] pikachu01:
Yeah, that's why it's weird as I have a higher uptime before this and everything was fine. I'll just attribute this to my phone's wonkiness :P
[Galaxy S I9000 Android Development] omnia-one4all:
I had a fc on stock jvr so I hope it's a very raw samsung fault :)
[Galaxy S I9000 Android Development] pikachu01:
FC on what app? If it's the phone app, it's attributed to Samsung's JVP/JVQ/JVR Phone apk that is incompatible with certain bluetooth headset calling.
[Galaxy S I9000 Android Development] omnia-one4all:
Fc was the wrong term, sry. The phone went into a deep sleep and couldn't wakeup. That would be DSOD, right :)
[Galaxy S I9000 Android Development] pikachu01:
Hmmm ... might be related to what I'm having. I'll need to test more to get to the root cause of this bug.
[Galaxy S I9000 Android Development] Mangus_U*RA:
after some days ok with .15, here another bsod while in standby, with wifi and 3g on, bt off, no OC/UV, no strange tasks in background.

edit: i repeat, I have those bsod ONLY with the phone in standby, never happened while I was using it (just a couple of reboots while in a call with low battery...), so It is difficoult to me to say exactly was the phone was doing...

I wonder if it have something to do with some problem waking up screen from standby, because even during those bsod, the phone seems to work well: it could receive sms and calls.
[Galaxy S I9000 Android Development] currydude:
What are you UV settings?
[Galaxy S I9000 Android Development] Mangus_U*RA:
I've wrote: NO OC/UV
[Galaxy S I9000 Android Development] corgar:
He say no oc/uv at all.

Tapatalked, powered by Corgar Slim Rom GB Edition.
[Galaxy S I9000 Android Development] Tatsuya79:
I would try without S97screenstate_scaling.

And perhaps without S95 unless it's usefull for you.
[Galaxy S I9000 Android Development] currydude:
LOLS oops sorry, been a hefty exam period for me (2nd last exam period before I come back to the Android development scene :P)

Delete all those scripts, reboot and a new _99ramscript should reproduce. I think the S97screenstate_scaling script is causing the problems though
[Galaxy S I9000 Android Development] pikachu01:
Yes, I'm in fact using screenstate scaling as well hence might be facing the same problem. Might be due to that. I'll disable it and test again.
[Galaxy S I9000 Android Development] zacharias.maladroit:
afaik screenstate_scaling is broken on stock-based kernels (including talon)

so that indeed might be the issue

haven't figured out yet why it doesn't switch properly & reliably
[Galaxy S I9000 Android Development] fifa_king:
For those with memory leak with zram

I have been testing the newest .15 kernel for about a day and a bit more with zram enabled as stock on a deodexed jvr rom.

What I realized is the memory leak only happens after the initial cwm flash. Both versions .14 and .15 gave me about 20-30mb (I know OMG) after about 3 (voluntary) reboots throughout about 1 day of use.

Now everytime I reboot it, I still have that extra memory and no more leak. What I noticed is that the ram management is significantly better due to the extra ram and the phone is so much snappier. Less system drain as well!

Don't know if others can confirm so try it out with zram enabled for about a day and give it about 3 reboots inbetween and hopefully you will get the leaked memory back as well.

I wasnt able to test them for longer than a day but I will post feedback.

Just thought I had to share this so that there are less people now misjudging this kernel after 10 minutes of use.

One more thing is I keep my system/app as small as I can. I realized that this folder is the main drainer for the ram use as well.

Edit: just thought Id post that now Im getting avg 197 free ram (without exaggeration) when I go to settings->applications->running services with the surface+talon combination. Will post screenshot if somebody doesnt believe.

Edit 2: in the running services it actually says 120m used and 195-198 free so I get about 320m ram as opposed to the 340m as stated in the topic but whatever at least I got the other 20m ram back.
[Galaxy S I9000 Android Development] Tatsuya79:
Indeed, I'm testing his SP4 kernel and his colours setting is perhaps the best I saw on this device (don't have voodoo Froyo anymore to compare).

He got rid of the low brightness red tint (3rd one in particular which was really wrong on stock is now fixed), saturation defects are toned down in the darkest tones, brightness scaling is smooth. No gamma strangeness like on current voodoo hack.

Max brightness is just perhaps a bit lower than stock? not sure here.

But we still can't adjust RGB, can't have everything yet.
[Galaxy S I9000 Android Development] Mangus_U*RA:
I've the same suspects as you, but why other people with same rom doesn't have this problem?

Now I'll delete that script, but there is no way to reproduce the bug...so I can only wait and see in the next days...
[Galaxy S I9000 Android Development] pikachu01:
Installing kernel wipes the screenstate scaling file. I have to manually put it there. That's your answer :)
[Galaxy S I9000 Android Development] Mangus_U*RA:
I'm not sure that i've understood...

We're a group of people with same phone, same rom, same kernel...but only I have this "bug".
[Galaxy S I9000 Android Development] pikachu01:
Do you use the screenstate_scaling init.d script?
[Galaxy S I9000 Android Development] mawardi:
On 0.4.4.15, I got no 1000 MHz scaling available. What went wrong? I'm on JVQ, the kernel is 1200 version.
[Galaxy S I9000 Android Development] darckengel:
The 1Ghz step was removed.
[Galaxy S I9000 Android Development] Mangus_U*RA:
yes, like the others. It's included with the rom.
[Galaxy S I9000 Android Development] pikachu01:
But wouldn't it get cleared when your friends upgrade to a new version?

Every install (through CWM deletes the scripts inside init.d).You must manually insert the script into the init.d directory to use it after installing 0.4.4.15.

Until now there are no ROMs yet released with 0.4.4.15, hence with you manually installing this version, you MUST have manually re-inserted the script (whereas your friend did not)
[Galaxy S I9000 Android Development] Mangus_U*RA:
so...that procedure of wipe init.d doesn't work.

Me too have flashed talon from version .8 to .15 on the same rom, and the scripts are still there.
[Galaxy S I9000 Android Development] pikachu01:
delete("/system/etc/init.d/S98screenstate_scaling");

The filename is different. That's why. Hmmm ... that's weird. No UV/OC as well. Might be due to your hardware (certain voltages are still unstable under certain conditions)?

Other than that, I'm not sure. Could be a rogue app. Can't say for sure without knowing what apps that you have.
[Galaxy S I9000 Android Development] Mangus_U*RA:
now i've deleted that scripts and we'll see..

here's my app list:

http://www.appbrain.com/user/il.Mangus/
[Galaxy S I9000 Android Development] Mangus_U*RA:
just a new bsod even without that script...I think that i'll flash talon .8 again...never had a bsod with that in about 10 days...
[Galaxy S I9000 Android Development] pikachu01:
Could you enable logcat and check what happens when you went BSOD? Paste it here.

Thanks!

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

A fun activity to try if your 100MHz UV can reach -250mv.

1. Download SetCPU.

2. Download Pimp My CPU!

3. Go to Voltage Settings in SetCPU.

4. Choose a custom value. There's an edit box in SetCPU and put it -975 (Yes -975. 100MHz's base voltage is 950mv)

5. Look at your voltage settings in Pimp My CPU! It should display -25mv (Yes, your 100MHz is powered up by -25mv of voltage which is ridiculous. You can even set it up at -950 making your base settings as 0mv)

6. Limit Pimp My CPU! Max frequency to 100MHz (WARNING, it'll be slow as molasses when you limit your CPU to 100MHz)

7. ????

8. Profit

9. LULZ

This proves that your 100MHz is now processing your data at 0mV or negative mV.

Actually, this is a feature. The kernel limits how much you can UV, and after you hit a certain point, it stops going lower than that even though voltage control apps report it otherwise.
[Galaxy S I9000 Android Development] :
Lukiqq has updated to SP4 and the changelog is very interesting...

- adjusted RGB levels

- sharpness adjust (UI, Video, Camera)

- color temperature is now set to 6800K, nice compromise between warm and cold tone
[Galaxy S I9000 Android Development] zacharias.maladroit:
Lukiqq should consider hosting his stuff on git / github, too

like lots of the kernel devs already do

makes porting & mutual improvements much easier and less time-wasting
[Galaxy S I9000 Android Development] Gvdn:
Sorry for little offtopic here, but lmfao Zach the animation in your signature makes my day everytime. Just wanted to let u know.

Sorry once again for offtopic. Long time reader and follower of this thread. Great work guys.
[Galaxy S I9000 Android Development] zacharias.maladroit:
haha - glad you like it :p

it got posted on the talon IRC channel - and what shall I say

love it ! :D

existz, Kodos96, Ytt3r:

important issue reported from a German forum:

weird issue - I dunno maybe ram, adc UV could be issue ? [was this even included in .6 ?]
[Galaxy S I9000 Android Development] jetcz:
I never had that issue so far on talon nor snail.

I'd say the have too much uv on 100mhz.

Becuase normally, when you uv too much, you get reboot. But when you are on charger, phone do not reboot, but turns off itself instead. And since there is 100mhz lock for charging state, this "issue" appears mostly while on charger.
[Galaxy S I9000 Android Development] existz:
The RAM/ADC uV has been in Talon for quite some time (also LCD) (originally added on 7/17), which i reverted it back on 8/6, then readded just RAM/ADC again on 8/9 (which was 0.4.4.13), i dont remember the exact build it got reverted, but from 7/17-8/6 the same uV was there.., so im not sure if this is the problem, if so i dont believe any issues were reported before..but it is possible i guess.., Also, since the 1ghz step was removed, this changes how it scales some..so OC/UV settings might have to be adjusted..as its going to be spending more time on different frequencies

But i might try and get another test up today.. got a few ARM/S5P fixes added, a couple cpufreq fixes, and a ton of ext4 fixes i pulled from zachs cm7 kernel...about 40 some ext4 commits.. Plus compiled with Linaro 4.5.4 with O3 and Graphite optimizations
[Galaxy S I9000 Android Development] Mangus_U*RA:
sure but..where is the option to turn on logcat? :confused:
[Galaxy S I9000 Android Development] existz:
Type "logcat-enable" in terminal emulator and reboot (info is in the OP)
[Galaxy S I9000 Android Development] jeebspawnshop:
I'm so hot for you, right now.
[Galaxy S I9000 Android Development] pikachu01:
Logcat Instructions

To enable/disable Logcat, type "logcat-enable" or "logcat-disable" in a terminal emulator and reboot

http://developer.android.com/guide/developing/tools/logcat.html

Basically, after reboot, wait until you encounter the bsod. Then go to the terminal emulator again and type:

logcat -f <filename>

Upload the file (or paste it in here)

All must be done as superuser :) (type su then only perform the commands)
[Galaxy S I9000 Android Development] zacharias.maladroit:
thanks guys !

I had something similar in the past

-> posted on the german forum & asking wheter massive UV was involved

but this never happened when the phone was attached to a charger or USB-cable

I'm way too cautious to do massive UV or OC without testing it previously &

I'm too paranoid that the phone could blow up if the kernel hardlocks while it is being charged (obviously others are not ^^)
[Galaxy S I9000 Android Development] Mangus_U*RA:
ok but after bsod I must reboot the phone keeping pushed the power button...does the phone wipe the log after reboot?

I followed your guide, terminal>su logcat-enable>reboot but with "alogcat" app after reboot I still see nothing in the log.

edit: ok now it works, it doesn't need "su" before the "logcat-enable" command :)

Next time i'll get bsod i'll post the log here :) does it contains any personal data that I should be aware of?
[Galaxy S I9000 Android Development] anoneemooz:
Giving Talon a try again just for the heck of it.

First comment after flashing:

I prefer the old "Talon" logo over the nexus-y one of the current version ;) but that's just me I guess hahahaha
[Galaxy S I9000 Android Development] cthonctic:
Actually I have seen the same issue three times since I changed to 0.4.4.15 1200 and I UV very carefully (max -50mA, only -25mA at 100MHz). In fact, today I reset voltage settings completely to check if it happens without any UV whatsoever. Turns out it does...

Today it looked like the device turned itself off when it reached 100% charge, I just wanted to unplug it to place a call and there we go... shutdown to charging screen. No idea what causes it but I also had a single unrelated reboot today, never had those on 0.4.3. :confused:

I'm also on android-hilfe.de (the German forum zach mentioned) but I prefer to go right to the source for my flashing needs (and support). ;)

I'll try to provide a logcat dump when it happens next if that helps.

Actually, does the "logcat-enable" command persist beyond reboots or does it have to be re-enabled? Was wondering about that already because the app Smartwidget requires running logcat but doesn't seem to work as promised...
[Galaxy S I9000 Android Development] Flynny75:
Its persistent. Ive not had any of these issues... BSOD or death on 100%. And my phone is plugged in at my PC almost all the time...
[Galaxy S I9000 Android Development] pikachu01:
From what Existz mentioned, enabling logcat is persistent across reboots.

Logcat doesn't have any personally identifiable information AFAIK. You can paste the last few lines before reboot and filter them out if there are any. We just need that last few lines before you get a BSOD/reboot.
[Galaxy S I9000 Android Development] existz:
Was it with USB or wall charger?
[Galaxy S I9000 Android Development] are-red:
hi.. I got usb tether problem using this kernel..others thing is excellence.. Anyone with me?
[Galaxy S I9000 Android Development] Flynny75:
Yeah. Doesnt want to stay tethered. Seems to be my only problem at the moment though...
[Galaxy S I9000 Android Development] pikachu01:
The tethering problem is a known issue. Most probably caused by the Linaro toolchain. Existz is looking into it :)
[Galaxy S I9000 Android Development] existz:
0.4.4.16 Public Test

0.4.4.16

Changelog since 0.4.4.15

- tons of ext4 upstream/aosp fixes

- some upstream/aosp cpufreq fixes

- more cgroup/sched upstream fixes; fixes from CodeAurora

- CodeSourcery 2011.03 (GCC 4.5.2) with O3 and Graphite optimizations

Let me know if tethering is better/worst in this version (dropping every couple minutes)
[Galaxy S I9000 Android Development] pikachu01:
Thanks for the new build existz!! :)
[Galaxy S I9000 Android Development] jeebspawnshop:
Thanks for the new version - again - you rock my socks off ;)
[Galaxy S I9000 Android Development] cronosmachine:
This will be difficult to adjust single amoled color on every phone. Notice not all production from samsung make great color default.

I have two galaxy s one is black edition last year purchase good color and white edition last month purchase suffer from yellowish.

I use screen filter. Both unit I use screen filter in order to have lower brightness also save battery.

So I hoping you still able the voodoo color on every single kernel.

I want set my own color setting. And be able save permanent after I apply it. If satisfied with color I adjusted then I can remove voodoo control apps my self.
[Galaxy S I9000 Android Development] rlorange:
I'm confused, surely screen stare scaling can't possibly work with the latest talon as the only remaining governor code is for ondemand and performance.

**Simply Honey3.9, Talon kernel1.3ghz**
[Galaxy S I9000 Android Development] jlieu:
Thanks for the update!
[Galaxy S I9000 Android Development] mawardi:
Why did you remove 1 GHz step in 1200 version?
[Galaxy S I9000 Android Development] Mangus_U*RA:
ok.

How could I know what is the "moment before reboot"? Anyway, no bsod atm...but it could take days before I get another one.
[Galaxy S I9000 Android Development] pikachu01:
The screen state scaling script loads an insmod of the conservative governor, hence I used it without much other thought. :)
[Galaxy S I9000 Android Development] pikachu01:
Having a 5 step CPU scale is much better for performance as the CPU only have to scale another 4 times to get to the maximum.
[Galaxy S I9000 Android Development] Mangus_U*RA:
But I removed that script...as you said...(and still had bsod)
[Galaxy S I9000 Android Development] omnia-one4all:
Regarding camera

Anyone got a reddish shimmer when going close to a white surface ?

On 15 and odexed stock

Don't know if it's like that on stock kernel
[Galaxy S I9000 Android Development] pikachu01:
Yup, which we need a logcat to know what's going on. :) Hoping to delve into it when you have more information.

Thanks!

I'm having it too, this seems to be a problem in SGS2 as well. My best guess is that it's the sensor's limitation. It's not well equipped for macro shots.
[Galaxy S I9000 Android Development] omnia-one4all:
Ok. We had it on winmo and there it was the camera driver but there it was not only macro shots
[Galaxy S I9000 Android Development] kitkitfok:
stability......