yashsingh1/xdaforums huggingface dataset:
[Galaxy S I9000 Android Development] pawitp:
I don't have time to look through all 3rd party modifications. If anyone knows a patch that produces a measurable performance, please submit it on gerrit.

What do you mean by stability improvement? I've almost never had kernel-related stability issues. If you do, you should file a bug report.
[Galaxy S I9000 Android Development] ranjib:
The only thing semaphore did for me was OTG over usb.

What pawits kernel doesn't do, afaik.

But I didn't use the semaphore kernel for a long time...
[Galaxy S I9000 Android Development] Onliner09:
Dear Pawit,

could you please check, if the kernel option "PPP support for async serial ports" (see under Device Drivers"/"Network device support" ) is activated in CM11 ? If not, could you please compile this function as module and post the file ppp_async.ko, so that I can test it

(not needed any more, found an alternative solution. (BlueVPN) )
[Galaxy S I9000 Android Development] NutZInTheHead:
camera force closes after i enabled power shutter on 20140208 nightly. anyone else getting this as well?
[Galaxy S I9000 Android Development] sanguinesaintly:
Same here. Tried wiping camera/gallery dara but no luck. Solved it by deleting camera/gallery app and reflashed. Not sure if there is an easier solution.

Sent from my GT-I9000
[Galaxy S I9000 Android Development] PremanshuRaj:
I am still having the problem even after flashing this..... Incoming call is taking a lot of time to show on screen.... Any idea what's the problem?
[Galaxy S I9000 Android Development] HalphaZ:
I had the same problem, and I was returning to 2.3.6 stock for this reason.

Then I installed semaphore (non s version) and delay now is acceptable. Just give it a try, there is nothing to configure after installation (I just cleaned dalvik cache).

I'm not a fan of semaphore (I never liked it), but objectively my i9000 is running much better with this kernel and there are several feedbacks that confirm my impression.

Inviato dal mio GT-N8000 utilizzando Tapatalk
[Galaxy S I9000 Android Development] goranbm:
How do I go to stock 2.3.6 ? just normal odin flash ?
[Galaxy S I9000 Android Development] saszseb:
Yes. (Odin or Heimdall).
[Galaxy S I9000 Android Development] PremanshuRaj:
Where's the link for semaphore?
[Galaxy S I9000 Android Development] tetakpatak:
This is off topic. Use google or search tab.
[Galaxy S I9000 Android Development] geckoas:
I'm still on 21.01.2014 nightly because of the rasp not working issue. Has it been fixed meanwhile or is there still need for a update of the rsap app?

sent from my galaxy I9000 running CM11 with tapatalk
[Galaxy S I9000 Android Development] Onliner09:
This issue is solveable with a workaround: simply deny the rsap app superuser rights and it will work. Refer the website and forum of the rsap app.
[Galaxy S I9000 Android Development] everb00b:
Open stock dialer app, click dialpad, does it open correctly or you have a half blank white pad?

I clicked back and press dialpad again to get get the numbers and pad

Can anyone reproduce this issue?
[Galaxy S I9000 Android Development] guijarrelson:
cm-11-20140210-SNAPSHOT-M3-galaxysmtd.zip is out.

M3 is bigger in size comparing with cm-11-20140209-NIGHTLY-galaxysmtd.zip. Is the code updated with today's commits? Or is freezed from M2?
[Galaxy S I9000 Android Development] freakymod2120:
Hi,

same here with latest nightly 09022014 ...but i have this behaviour since using first CM11-versions, maybe our device is getting to old ...

Issue stays with another kernel (e.g. Sema-Kernel)...i tested it ...
[Galaxy S I9000 Android Development] everb00b:
[MENTION=5326164]freakymod2120[/MENTION], I tested with Stock and Mackey kernels.

I think its an issue in the dialer app.
[Galaxy S I9000 Android Development] AndroidBR:
I tried to reproduce this but thankfully my phone opens dialer normally without any delays.

The biggest problem when people call me: the phone rings but it can take up to 6 seconds for the phone to wake up, turn on the display for me to see who's calling and answer the phone. Sighs...

The phone feels slow when opening apps, switching between them and even when I select recent apps switcher, it first shows that I have no recent apps, so I back out of it, 2 seconds later if I select the recent apps switcher it displays my recent apps properly...

I'm considering going back to Jelly Bean... Phone felt a lot faster and smoother back with CM10.1...
[Galaxy S I9000 Android Development] Ego-Zogger:
for me it´s working (on 0902 nightly with semaphore)..

never experienced that in any previous nightlies..
[Galaxy S I9000 Android Development] popic_u:
For me no problems with dialer.
[Galaxy S I9000 Android Development] freakymod2120:
Maybe i should try a "clean" install with some of the next nightlies to see that the phenomen will be solved ...the others here had no prob with their dialer app..

Did you a full clean install???
[Galaxy S I9000 Android Development] ioannis_m:
Get a full backup from your data and rom and then factory reset /dalvik/cache and format system.

Then go to advanced restore and restore only data and try to reproduce.;)
[Galaxy S I9000 Android Development] freakymod2120:
Okay i will try and post here what happens ...
[Galaxy S I9000 Android Development] guijarrelson:
I see this build cm-11-20140211-EXPERIMENTAL-ignorecolor-calibration-galaxysmtd.zip in the official download page. Did you see any notice about this test build?
[Galaxy S I9000 Android Development] freakymod2120:
Hint for the Installation.Ifnos on first page...

Hi [MENTION=3117667]pawitp[/MENTION]...

i found this on CM-Homepage, maybe it could be helpful while getting "set_metadata_recursive":

---------- Post added at 08:58 AM ---------- Previous post was at 08:51 AM ----------

It is a test-build from pawitp ...look here:

http://jenkins.cyanogenmod.com/job/android/58662/parameters/

==> here is a hint of gerrit-changing-id 59420

When you fill it in the link http://review.cyanogenmod.org/#/c/59420/ ==> http://review.cyanogenmod.org/#/c/59420/

---------- Post added at 09:15 AM ---------- Previous post was at 08:58 AM ----------

Everything done and nothing changed ...the first click on the dial-pad does not open, with the second click it works ...hmhh i don`t know whats my fault ...:confused::confused:
[Galaxy S I9000 Android Development] guijarrelson:
Did anyone use Telegram app? I don't receive notifications about this app. It's installed in the internal mem, and in other phones, it works well with the same config.

Tapatalked from SGS CM 11
[Galaxy S I9000 Android Development] pawitp:
It's a build which ignores the color calibration data not written properly in some Galaxy S devices (the original driver does not read them). What do you think about the effects on the color?

Does not apply to our device where recovery cannot be upgraded separately. The instruction to deal with that error has been in the first post since forever ;)
[Galaxy S I9000 Android Development] guijarrelson:
In my device, color calibration works fine in the default setting. I can set all colours without problems. I don't have or I don't see any color bug in my screen.

Do you need any test in this experimental build?

Tell me, and I can do a easy test, if you want.
[Galaxy S I9000 Android Development] pawitp:
If nothing looks different, then great.
[Galaxy S I9000 Android Development] guijarrelson:
I am talking about of cm-11-20140210-NIGHTLY-galaxysmtd.zip, not experimental build.

Sorry if my words can be interpreted wrongly.
[Galaxy S I9000 Android Development] pawitp:
If you want to test, then flash the build to see if there's any negative effect. Color tuning will still work, but factory calibration setting will be ignored.
[Galaxy S I9000 Android Development] fran_xda:
What is your--

Phone model: Galaxy S GT-i9000

Radio (baseband): I9000XXJVU

CM version: 11-20140210-SNAPSHOT-M3

CM Download url: OP link

Gapps version: OP link

Did you--

wipe: Yes*

restore with titanium backup: No

reboot after having the issue: Yes

Are you using--

a task killer: No

a non-stock kernel: No

CMSettings/Performance settings (other than stock): No

ART Runtime: No

other modifications: No

Provide any additional information (observations/frequency of problem/last version it worked on/etc) as needed:

video of the issue: http://www.youtube.com/watch?v=7lY6UV1Yy7E

Not really apreciated in video, it is worse if you see in real. If bluetooth is on=choppy deploy of status bar/ bluetooth is off= smooth deploy. It only affects to status bar, other transitions and apps seem to be smooth in both cases. This has been happening since the first time I installed CM11 and in every nightly. Changing kernel to Semaphore haven't solved the issue either. Sometimes I get opposite behaviour (BT on=smooth/BT off=choppy), but never smooth in all situations.

*wipe: Although I actually haven't wipe before the installation of M3 I did in previous version (1-26th) and checked the issue rigth after flashing, without any settings or apps modified, the issue was exactly the same to the linked video.

Thanks for your effort.
[Galaxy S I9000 Android Development] pawitp:
While I see the issue, I believe it is very minor but very hard to debug and won't be solving this issue. Of course, any other developer is free to solve it and submit a patch. A work around is to use your finger to drag the bar all the way down to open it and you won't notice the issue.

And starting from the 20140211 nightly, you have the option to force enable graphics acceleration for the status bar at the expense of RAM in Performance Settings.
[Galaxy S I9000 Android Development] everb00b:
[MENTION=5326164]freakymod2120[/MENTION]

I wiped my device including system.

Still having this pad issue as seen in the photo I my previous post.
[Galaxy S I9000 Android Development] rhaaa:
I have a noticeable yellowish tint with the experimental build. I'm not an expert at color calibration, so that might well be equivallent to my eyes accustomed to a blueish tint with the non experimental build :)

All I can say is that the experimental build is quite warmer than the non experimental build.

I take the opportunity to thank you so much for your continued work on our old beloved device :)

Ty,

--

Rémi
[Galaxy S I9000 Android Development] HM.Carbide:
TThe screen gets noticable yellowish with the experimental build.

The kernel logo is at the beginning white.

Then it switches and the white text gets yellow.

Maybe it is possible to configure whether to load the color correction or not.

A file with 0 or 1, exists or not exists.

Gesendet von meinem GT-I9000 mit Tapatalk
[Galaxy S I9000 Android Development] need4steer:
I am seeing a little yellow / yellowish where it should be white - but nothing too major.

All I know is that thanks to this experimental fix I finally see CyanogenMod as it should be.

The bluish screen look, this annoying blue tint / hue, is impossible to watch.

I'd like to appreciate pawitp for his will to help and for his truly tremendous effort the community.
[Galaxy S I9000 Android Development] pawitp:
Is everyone else experiencing this? My screen was a little bit "blueish" from the start, so I didn't notice anything strange. Can you take a photo? Is it correctable with colour calibration? If so, what are the settings?
[Galaxy S I9000 Android Development] fran_xda:
I have tested graphics acceleration but unfortunately doesn't solve the issue...

Were any of you not having the issue? If so could baseband be the reason, as all other parameters are the same (hardware, software..)?
[Galaxy S I9000 Android Development] pawitp:
Data Collection Time - Please flash the attached kernel and post the result.

Do you see a yellow tint:

Do you prefer the old or new color:

Post your dmesg (looking for lines starting with tl2796 or color_calib):

EDIT: Completed for now.
[Galaxy S I9000 Android Development] HM.Carbide:
Do you see a yellow tint: yes

Do you prefer the old or new color: old color

Post your dmesg (looking for lines starting with tl2796 or color_calib):

<6>[ 2.800005] tl2796: c0, b-73c29df5, got v 2016000, factory wants 2016000

<6>[ 2.800209] tl2796: c1, b-7daa9d08, got v 2051000, factory wants 2051000

<6>[ 2.800343] tl2796: c2, b-91f29b8e, got v 1624000, factory wants 1624000

<4>[ 2.800538] color_calib: 73c29df5 00 00 00 02 00 07

<4>[ 2.800655] color_calib: 7daa9d08 00 00 00 05 00 03

<4>[ 2.800834] color_calib: 91f29b8e 00 00 00 05 00 fffffffc

<6>[ 2.944566] tl2796_probe successfully proved

I tried to make photos, but that doesn't help. The camera seams to correct the white colors. The yellow is on the picture even more blue, but less sharp (I'll guess due to the yellow - white correction). Maybe I'll borrow a professional camera, but this will take a day.
[Galaxy S I9000 Android Development] freakymod2120:
Hmhh maybe trying to make an entry on Jira ,but when we are the only ones who have this behaviour - i think there is no way of solution ...;)

acutally i don`t know why it happen ...
[Galaxy S I9000 Android Development] need4steer:
Do you see a yellow tint: No, I don't see a yellow tint.

Do you prefer the old or new color: I'm actually don't see any differences at all. Shall I try again and perform a wipe? Or maybe formart /system and flashing from scratch? Just a reminder, I flashed cm-11-20140211-EXPERIMENTAL-ignorecolor-calibration-galaxysmtd.zip. BTW, I see that cm-11-20140212-NIGHTLY-galaxysmtd.zip is uploaded. Shall I flash this and then reflash color-dump.zip?

Post your dmesg (looking for lines starting with tl2796 or color_calib): I'm getting "klogctl: Operation not permitted" in the dmesg.txt file. Shall I restore permission via recovery?
[Galaxy S I9000 Android Development] pawitp:
Old color = pre-ignore-calibration, which for you means the blue tint. I don't care what build you're on as long as you flash the special kernel.

You need to be root (su) to get dmesg.
[Galaxy S I9000 Android Development] need4steer:
Okay.

I'll reflash a ROM with the blue tint.

As for the "klogctl: Operation not permitted" error, I'm running adb shell dmesg > dmesg.txt from the command prompt, after I verified that "Root access" is set to "Apps and ADB" under Developer options, and I'm still getting it.

Edit: never mind about the error. I had to run adb root switch and now everything is fine.

Others who are having the "klogctl: Operation not permitted" in the log file (dmesg.txt) after running adb shell dmesg > dmesg.txt from the command prompt:

Under Settings --> Developer Options

Enable "Android debugging"

Set "Root access" to "Apps and ADB"

run adb root switch from the command prompt

only now run adb shell dmesg > dmesg.txt from the command prompt

Thanks a lot for pmsrefugee for posting this information.
[Galaxy S I9000 Android Development] pawitp:
I don't care about what build you're on, I just need the dmesg running the special kernel (which you haven't posted yet?). The other questions are for other users to gauge how ignoring color calibration data affects color display on different devices.

Other users with or without color issues, please contribute to this request for information (See http://xdaforums.com/showpost.php?p=50251166&postcount=2105)
[Galaxy S I9000 Android Development] need4steer:
Okay

Here it is:

<6>[ 2.781336] tl2796: c0, b-00000000, got v 4200000, factory wants -3308278
<6>[ 2.781541] tl2796: c1, b-00000000, got v 4200000, factory wants -3301278
<6>[ 2.781738] tl2796: c2, b-00082ada, got v 3381000, factory wants 3381000
<4>[ 2.781871] color_calib: 00 01 01 01 01 01 ffffff01
<4>[ 2.782053] color_calib: 00 01 01 01 01 01 ffffff01
<4>[ 2.782171] color_calib: 82ada 01 01 01 01 01 ffffff01
<6>[ 2.925903] tl2796_probe successfully proved

Now, you don't want also to see this log after I'll be in a bluish screen ROM and with the color-dump.zip flashed on top of it?
[Galaxy S I9000 Android Development] pawitp:
The calibration data is in the kernel, the ROM doesn't matter. As long as you have the kernel installed, the calibration data will not be used.
[Galaxy S I9000 Android Development] need4steer:
Will I be able to flash this kernel on top of the new nightly (cm-11-20140212-NIGHTLY-galaxysmtd.zip), and avoid this bluish screen?
[Galaxy S I9000 Android Development] pawitp:
Yes, though it will hopefully be fixed properly after I see all the data.
[Galaxy S I9000 Android Development] need4steer:
Cool!

I'll try it right now.

BTW, is anyone having a problem mounting the sdcard in CWM-based Recovery 6.0.4.7?

Whenever I try to mount it I'm getting /storage/sdcard0: Shared-Unmounted.

This issue is posted also in a previous thread - [NIGHTLY][ROM][4.3] CyanogenMod 10.2 for Samsung Galaxy S

I flashed CyanogenMod 11 from stock, and I was able to mount the sdcard in ClockworkMod Recovery 3.0.0.5 and in ClockworkMod Recovery 5.0.2.8 (which is installed after flashing CyanogenMod 7).

Any suggestions?

Edit: the Shared-Unmounted issue is fixed in the latest nightly (cm-11-20140213-NIGHTLY-galaxysmtd.zip).

More information about it is available in CyanogenMod's Gerrit Code Review and in GitHub.
[Galaxy S I9000 Android Development] freakymod2120:
I have found that the issue is known in Jura :good:

https://jira.cyanogenmod.org/plugins/servlet/mobile#issue/CYAN-2949

So maybe we geht a solution
[Galaxy S I9000 Android Development] gcsuri:
I installed 20140212-NIGHTLY and much faster than one month earlier one. :)) works very well! Thank you!
[Galaxy S I9000 Android Development] need4steer:
I love the color-dump.zip fix!

I can use any of CyanogenMod 11 builds without the annoying blueish screen.

Is it also good for previous CyanogenMod stable releases (like 10.2.1) or only for CM 11?

As for the /storage/sdcard0: Shared-Unmounted which I'm getting in CWM-based Recovery 6.0.4.7, well - I'm still having it. It's not a big deal, but I'd love to solve it.

The problem is that whenever I'm trying to mount the sdcard from the recovery, I'm getting that error.

Edit: the Shared-Unmounted issue is fixed in the latest nightly (cm-11-20140213-NIGHTLY-galaxysmtd.zip).

More information about it is available in CyanogenMod's Gerrit Code Review and in GitHub.
[Galaxy S I9000 Android Development] pawitp:
1) It is not meant to be a fix and is not compatible with other versions and may not be compatible with future nightlies.

2) Please stop spamming the thread with the same question. Shared-Unmounted is not an error but means that the sdcard is shared with the computer and thus unmounted on the device.
[Galaxy S I9000 Android Development] need4steer:
1. Okay, I'll just wait and see if this issue will be solved. Please update when this kernel won't be compatible anymore.

2. Good to know. Do you think is there a way to solve it so it'll work just like it's working in previous CWM versions in this device?

BTW, I didn't meant to spam. I just meant to notify that this issue still exists. However, since it's considered as spam, I'll stop it.

I'm just hoping there'll be a solution for this issue.
[Galaxy S I9000 Android Development] pawitp:
1) I don't know and don't care when it will not be compatible. It is just for debugging, you're on your own if you want to use it for other purposes.

2) Works fine for me. The message displayed just tells the status; the mount on the computer works properly. EDIT: Might be a problem with Windows, I have something that may fix it.

When you post something, be patient. Don't expect someone to reply right away....
[Galaxy S I9000 Android Development] srkonus:
Stuck on boot - Cyanogenmod logo

Hi,

i used the M3 snapshot and i was happy. But unfortionally i deceided to test the slim Kitkat and went back to CM11.

Now my phone stucks on the cyanogenmod boot logo. :crying:

I wiped all caches and have done a factory reset with no luck. Also a new factory reset after flashing with a second flash was not the answer. What must i do to flash cm11 and use it on my phone?

kind regards

srkonus
[Galaxy S I9000 Android Development] omreJ:
wife system..i meant wipe :cool:
[Galaxy S I9000 Android Development] nekuy:
Go to recovery. Install semaphore or Mackay kernel. Reinstall CM.
[Galaxy S I9000 Android Development] srkonus:
Can you give me some more informations?

1. Flash mackay 608 - 609 kernel

2. Flash CM11

3. Boot

.

.

.

Is this the right way?
[Galaxy S I9000 Android Development] mohamobo:
Bug report

infinite loops while the alarm is in fired and missed states

Logcat: http://pastebin.com/ZqPHSfKW

this happen since this commit http://review.cyanogenmod.org/#/c/58354/1

fix here http://review.cyanogenmod.org/#/c/58870/ but already abandoned
[Galaxy S I9000 Android Development] pawitp:
1) Describe your problem clearly, I have no idea what you are talking about.

2) Reading the comment, someone is already aware of the problem. Give it some time.
[Galaxy S I9000 Android Development] st379:
bug report

version: 20140203

original kernel with full wipe.

when i search for network i can only find 2 networks.

it is connected to the right network but i can not find it when i press search for network, on my sister phone with original samsung rom she can find 5 networks including the one i am connected to.

p.s. thank you pawitp for keeping our old phone alive and kicking.
[Galaxy S I9000 Android Development] mohamobo:
1) when alarm finish in notification will show missed alarm and this notification looping non-stop.

2) will wait, but just want to report here because when i search this thread no one report it.
[Galaxy S I9000 Android Development] phil_greg2001:
Hi all,

This app works fine here :

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

:cowboy:
[Galaxy S I9000 Android Development] ioannis_m:
What is your baseband version and what is your sister's?;)
[Galaxy S I9000 Android Development] st379:
jvt it is only occured on cm11.

i have no reception problem i just can't find my carrier (Golan Telecom).

it is not a problem for me as long as i have recpetion just wanted to report on this bug that will be fixed.
[Galaxy S I9000 Android Development] nekuy:
Yes. After flashing new kernel reboot.

But you should prefer semaphore (http://xdaforums.com/attachment.php?attachmentid=2436041&d=1386318973) because latest mackay use cma version.
[Galaxy S I9000 Android Development] hertzschi:
Do you see a yellow tint: Yes

Do you prefer the old or new color: Old

Post your dmesg (looking for lines starting with tl2796 or color_calib):

<6>[ 2.774409] tl2796: c0, b-73c29df5, got v 2016000, factory wants 2016000
<6>[ 2.774614] tl2796: c1, b-82cf134d, got v 2030000, factory wants 2030000
<6>[ 2.774811] tl2796: c2, b-8f1c1295, got v 1638000, factory wants 1638000
<4>[ 2.774944] color_calib: 73c29df5 00 00 00 fffffffc 00 07
<4>[ 2.775128] color_calib: 82cf134d 00 00 00 00 00 06
<4>[ 2.775245] color_calib: 8f1c1295 00 00 00 02 00 fffffffa
<6>[ 2.918939] tl2796_probe successfully proved
[Galaxy S I9000 Android Development] pawitp:
Thanks. I'm done with the data collection for now.
[Galaxy S I9000 Android Development] valenparra:
Alarm not working properly (no sound) in 20140213 nightly!
[Galaxy S I9000 Android Development] need4steer:
Well, I just woke up from its sound :) So it's working perfect for me.

What was your previous version? Did it work in it?

If you're testing the alarm sound from within its setting (clock --> settings --> Alarm volume --> click on the slider to hear the alarm) do you hear it?
[Galaxy S I9000 Android Development] HM.Carbide:
Color calibration fix in 20140214 works as intended on my phone.

Thanks a lot for your work!

Gesendet von meinem GT-I9000 mit Tapatalk
[Galaxy S I9000 Android Development] need4steer:
+1 to that!

I'm so glad to get rid of this annoying bluish screen!

pawitp, thanks a lot for your will to help with this issue and for your tremendous contribution to the community!
[Galaxy S I9000 Android Development] lucaslg26:
Anyone? :(
[Galaxy S I9000 Android Development] palera:
ART

Sorry to ask but, it has been a while since the first steps... How about ART development? Does it have been any improvements?
[Galaxy S I9000 Android Development] joonair:
is there a way to change the display resolution?
[Galaxy S I9000 Android Development] saszseb:
Grab texdroider_dpi.apk from Play Store!
[Galaxy S I9000 Android Development] tetakpatak:
Or also "build.prop" from Play Store!