yashsingh1/xdaforums huggingface dataset:
[Galaxy S I9000 Android Development] didhiy:
I feel not lucky anymore ;) only works well for half hour & got so many freeze after that

almost unusable for me :(

hope someone got better solution :thumbup:

btw, my apologize to stratosk to mess up this thread with gcc things.. hope this discussion still related enough to origin semaphore topics

I'm out now
[Galaxy S I9000 Android Development] stratosk:
No problem. It's a technical discussion and it's on topic :)
[Galaxy S I9000 Android Development] Alberto96:
Can you do a test for me?

Try to build kernel with SLAB and let me know if it's stable (or stabler than SLQB) ;)
[Galaxy S I9000 Android Development] kasper_h:
You're welcome :)
[Galaxy S I9000 Android Development] didhiy:
Well since stratosk already give his permit, I'll answer this :)

It even boot with SLUB :) I disable SLUB_DEBUG, I don't know if this necessary or not

https://github.com/didhiy/android_k...mmit/9a9e81f2599d17d492673228222ba3fd2357be44

EDIT:

I don't know if the fix came from the newer linaro 4.8 itself, or something I've add to my kernel repo... I only compile with 2 different config (SLQB & SLUB both with DEBUG turn OFF)

Possible fix if it wasn't from the toolchain itself:

- turn off SLUB_DEBUG

- or this 2 patch from aosp 3.4 kernel common:

https://github.com/didhiy/android_k...mmit/bf44f29bfe0a4762ae660b7db1fcb394c1240663

https://github.com/didhiy/android_k...mmit/b35ea82017d1183256853aaa1680475d5dba8168
[Galaxy S I9000 Android Development] DerTeufel1980:
Not bad... Is it more stable now?

Gesendet von meinem SAMSUNG-SGH-I317 mit Tapatalk 2
[Galaxy S I9000 Android Development] didhiy:
It's better now. just finish playing Temple Run around 10 minutes without surfaceflinger stale. It was freezed before.

I edited my previous post with some changes that maybe fix the boot problem.
[Galaxy S I9000 Android Development] DerTeufel1980:
Ah, those are the two patches I also was talking about, but it didn't work for me.

Maybe I should try again at some point

Gesendet von meinem SAMSUNG-SGH-I317 mit Tapatalk 2
[Galaxy S I9000 Android Development] Samga:
3.4 for CyanogenMod 10.2?

Does "Semaphore >= 2.8.0 for 4.2" mean that 3.4.0 is suitable for 4.2 and 4.3 as well?

The kernel of CM 10.2 stable (Android 4.3) is dated Dec 2, while 3.3.0 is from Oct 28.

So maybe there are changes in CM that aren't reflected in 3.3?

I was trying 3.4 with 10.1, but had a freeze when booting. I had to flash 3.0 to be able to flash 10.2.

(Sorry if this is a stupid question, but I didn't find any clear answer yet.)
[Galaxy S I9000 Android Development] everb00b:
Semaphore <= 2.6.6 for 4.1.2

Semaphore >= 2.8.0 for 4.2

Semaphore >= 3.1.0 for 4.3

Semaphore >= 3.4.0 for 4.4

So 3.4 and above is only 4.4.

the partitions are different in 4.3, so it would repartition your phone.
[Galaxy S I9000 Android Development] zakitheracer:
Cm11 and Cm10.2 have the same partitions lol
[Galaxy S I9000 Android Development] jugster:
The possible fixes, was that for compilation or booting?

Just compiled Semaphore KK with latest linaro and it compiles fine, but ended up in bootloop. Could not access recovery through 3BC, had to flash Stratosks kernel through heimdall and download mode to get it working again.

Would that be a possible scenario of what could happen if I didn't have those fixes, or did I just do something wrong?

(SLUB and SLUB_DEBUG enabled)
[Galaxy S I9000 Android Development] turtuv:
:rolleyes:
[Galaxy S I9000 Android Development] didhiy:
If you test it with gcc 4.8, I think It's not bootloop, but the kernel not boot at all just like kasper & derteufel said.

If you have time to test and ready to flash semaphore tar from heimdall or odin

Try add this line in your semaphore_galaxys_defconfig to disable slub debug

# CONFIG_SLUB_DEBUG is not set

If the result still not boot, then try to add those two patches + one patch by kasper in few post before

If still not working either, maybe I'll try to build from stock cm-11 and try figure out which additional commit from my notest branch that needed to fix gcc 4.8 boot problem

UPDATE:

just test a build with my semaphore branch for sc-02b, the kernel boot properly but it's not stable (random reboot co cwm)

I attach some patches, the others can be found here:

https://github.com/didhiy/android_kernel_samsung_aries/commits/sema

I didn't test without -O3, but I think it's better to temporary revert them.
[Galaxy S I9000 Android Development] everb00b:
Indeed, but he flashed 4.3/4.4 kernel on 4.2.

So his partitions got screwed.
[Galaxy S I9000 Android Development] Samga:
So does 3.4 work on >=4.3 (10.2)?

As the kernel is based on pawitp's one and the CM kernel is younger than 3.3, could it be that 3.3 is missing any needed bugfixes/enhancements regarding to CM 10.2 stable?
[Galaxy S I9000 Android Development] grinder777:
Hi Stratos,

Hi Community,

for me it's time to say good bye here... I've got my new device, a S3mini. It's a nice one to replace my good old SGS, same in size, quiet cheap right now, but much stronger and much more RAM. Not to forget, it is real beautiful in shape!

It was a great time here, I learned much and I will miss all the developers and all of you guys n girls - but especially I will miss you, Stratos! You are a really great dev and you give so much inspiration to others. I wish someone like you were there... at least we all know, the time for SGS development is over - the hardware is no more able to follow the new androids. IMO 4.2.2 was the latest good working ROM for that. So I will give it with Malchos BlackBeast to my good wife's dad in Kenia.

I write my bye bye here because I know all you people are coming to visit Stratosk threat here earlier or later and all of you will read it here.

So let me say a huge THANKS SO MUCH to all of you who kept and keep this really good device alive!!!

Have a good time, all of you, Merry Christmas and a Happy New Year!

Some Christmas Donations will follow soon...

Bye!!!

and continue having fun!

Gesendet von meinem GT-I8190 mit Tapatalk 2
[Galaxy S I9000 Android Development] jugster:
Linaro 4.8 booting...

For anyone interested, I can confirm that the patches suggested by didhiy creates a booting kernel compiled with latest Linaro 4.8 toolchain.

Cheers,

/J
[Galaxy S I9000 Android Development] stratosk:
Hi, my friend!

I really wish to enjoy your new device as much as old i9000.

Thank you for your great support and contribution!!!

Merry Christmas!
[Galaxy S I9000 Android Development] DerTeufel1980:
Which kernel did you compile with it?

Gesendet von meinem SAMSUNG-SGH-I317 mit Tapatalk 2
[Galaxy S I9000 Android Development] jugster:
Semaphore!

Sorry, should have been more obvious. I compiled Semaphore 3.4.0 for KK (O3 enabled).

(Now running on my i9000 and has gone through quite some gaming and quite a few anututu runs)

/J
[Galaxy S I9000 Android Development] DerTeufel1980:
I just was wondering, if there already is something in semaphore code, which isn't in mine or kasper_h.

Too bad for me you also tried with semaphore. ;)

Gesendet von meinem SAMSUNG-SGH-I317 mit Tapatalk 2
[Galaxy S I9000 Android Development] kasper_h:
I will give it another try, maybe life's different in kitkat-world :)
[Galaxy S I9000 Android Development] kasper_h:
https://github.com/kasperhettinga/samsung-kernel-aries/commits/mackay-cm11-48

This one compiles and boots fine :)

Thanks didhiy!
[Galaxy S I9000 Android Development] DerTeufel1980:
Strange did you also try with using xz?

Gesendet von meinem SAMSUNG-SGH-I317 mit Tapatalk 2
[Galaxy S I9000 Android Development] kasper_h:
I got compile errors from the unzx so I reverted that one...it didn't even finish compiling.
[Galaxy S I9000 Android Development] DerTeufel1980:
Ah, OK. Just wondering what fixed booting. I also committed the 2 memset patches, and the patch to HEAD.S just fixes a warning...

Gesendet von meinem SAMSUNG-SGH-I317 mit Tapatalk 2
[Galaxy S I9000 Android Development] jugster:
Did you try JB or KK. I have only tried KK, which worked.

I have also tried another device with the same compiler but with a different optimization setting (Os) and that has been very stable (running for weeks). I wonder if these changes only come into effect with O2 or O3. Otherwise I would have thought the memset bug should have hit me by now.

Signature? Signature!
[Galaxy S I9000 Android Development] didhiy:
Glad to see that's work for mackay kernel too :)

and thanks again to stratosk for let us discuss this :good:
[Galaxy S I9000 Android Development] Unjustified Dev:
Do you plan on updating aries kernel?
[Galaxy S I9000 Android Development] jugster:
For those interested.

Testing Semaphore compiled with some memset patches and O3 enabled using Linaro 4.8 mostly works ok. A few times the phones has been in recovery mode when having left it alone not doing anything.

Running cpu burn "like" programs works sometimes ok and sometimes not. I used something called StabilityTest that is available for free on Google Play. On Stratosks original kernel built with older toolchain, it just runs forever it would seem (forever means 8 hours), on the new toolchain it sometimes runs just once, or an arbitrary amount of times. Mostly it stops after a while. Also, with older toolchain StabilityTest reports 1000MHz used all the time, while on newer toolchain it says 880Mhz is used. It is supposed to run as fast as possible.

Also, after a few of the reboots, I have been unable to boot again, requiring me to flash the rom again. Something seems to have been corrupted.

Verdict as of now: Only for the bold! Not your daily driver.

Cheers,

J
[Galaxy S I9000 Android Development] kasper_h:
On my phone it behave quite well, only one reboot. Someone who I asked to test my kernel actually had several hard-reboots.
[Galaxy S I9000 Android Development] didhiy:
Based on this gcc 4.8 changes I add this "not sure" commit

I don't know if this commit is a must and technically a right patch or just a placebo effect, but I've past 24 hours without reboot or system freeze. And everything seems run normal to me.

I didn't enable and test with -O3, but here's a quote from the previous link that might be related to -O3 fix:
[Galaxy S I9000 Android Development] Alberto96:
I'm testing GearKernel compiled with GCC 4.8 and your commits (Cortex-A8 Optimized). Performance is better than before and all is stable even with High OC. Awesome :D

I will leave my phone turned on this night to check stability.
[Galaxy S I9000 Android Development] jugster:
More Semaphore 4.8 testing information

I have now tried compiling Semaphore with 4.8 toolchain using various O levels. O3 is for me actually the most stable, which does not mean stable enough. The others make the device reboot after just playing around in the UI for a while. I don't know what kind of reboot it is, I don't know the difference. The device restarts itself anyway. Most of the times it is not able to boot properly after that.

O2 and Os behaves similarly to O3, but worse.

I also feel that the UI is more sluggish on 4.8, whatever O-level I'm compiling with. The test I made was to let it boot and then sit for a few minutes, if it survives that long without a reboot, then go straight to settings about menu. In 4.8 that takes noticably longer than with 4.7, and it very often results in a reboot as well =(.

I'm going to try with the next 4.8 release to see if it solves any problems =)

Flashing a 4.7 built kernel fixes the problems. I even tested 4.7 with the memset patches, and it behaves as expected so far. I.e, snappy and works.

Cheers,

J

Edit: I wonder if I was bitten by this bug and that was part of the reason I failed to boot properly.

https://github.com/cyanogenmod/andr...mmit/dbc0d78906ced22a66dbebe9edb5e83834f78bbb
[Galaxy S I9000 Android Development] DerTeufel1980:
Thanks for the link to the commit. I always was wondering about bootloops of this kind.

Gesendet von meinem GT-N7105 mit Tapatalk 2
[Galaxy S I9000 Android Development] a g bell:
Should kk4.3. Work on slimkat 4.4.2?
[Galaxy S I9000 Android Development] ElmirBuljubasic:
Slimkat use alredy lastest sema kernel.
[Galaxy S I9000 Android Development] twili9ht:
Finally got my Nexus 5 so I gave my Galaxy S to my sister.

I want to thank Stratosk again for this amazing kernel. I'll keep on following his work.

Here's a donation to say thanks again :):good:

7FA28368KH307520M
[Galaxy S I9000 Android Development] astrosp4c3:
Hi stratosk ,

I searched before asking this question but i didnt found anything..

My question is simple: why dont we have a 3.4 kernel as i9001? Is there a problem related to our aries hardware ? Or drivers ?

Inviato dal mio GT-I9000 utilizzando Tapatalk
[Galaxy S I9000 Android Development] N3tro:
Different hardware + i9001 gets help from code aurora.
[Galaxy S I9000 Android Development] stratosk:
Thank you very much for your donation my friend! Really appreciated!

Enjoy your new device!
[Galaxy S I9000 Android Development] astrosp4c3:
Last version of semaphore and cm11 20131217 doesnt work good. There is a bug with showing battery percentage and batterystats dont work. They just dont display...any idea?

Inviato dal mio GT-I9000 utilizzando Tapatalk
[Galaxy S I9000 Android Development] zakitheracer:
That's a bug of cm with custom kernels not the kernels fault ;)
[Galaxy S I9000 Android Development] ElmirBuljubasic:
Google has removed the ability to retrieve battery monitor statistics
[Galaxy S I9000 Android Development] aopvet:
Flashing only the latest nightly without our beloved semaphore kernel, battery meter works fine. So I guess stratos has to correct something to make his kernel compatible with cm11 again.
[Galaxy S I9000 Android Development] zakitheracer:
The problem is with CM as even on N5 the battery is messed up with custom kernel.

Just try and flash Mackay kernel and see if the problem is there or not.
[Galaxy S I9000 Android Development] astrosp4c3:
Thats what happen flashing last semaphore on last cm11...

Maybe something has changed ...

Inviato dal mio GT-I9000 utilizzando Tapatalk
[Galaxy S I9000 Android Development] fishears:
Its not a CM problem. Its a code change they've made that custom kernels need to pick up if they want to be compatible.

sent from somewhere..
[Galaxy S I9000 Android Development] hertzschi:
Who do you mean with 'they'?

CM team or google?
[Galaxy S I9000 Android Development] solar666:
I think it is quite clear reading fishears statement; They = custom kernel developer
[Galaxy S I9000 Android Development] baciany:
After isnatlling 3.4.0 on CM11 from 17/12/2013 i got stuck on Samsung Galaxy S screen and cant get recovery. Had to use ODIN to comeback to 2.36., Tried to install 3 times and the same
[Galaxy S I9000 Android Development] hertzschi:
I had the same problem.

Semaphore and also mackay didn't boot.

I flashed semaphore 3.4.0 tar with Odin.

Then cm 131215 from recovery.

This is the last cm version which works with custom kernel as it seems for now...

---------- Post added at 04:39 PM ---------- Previous post was at 04:37 PM ----------

No. As I understood that's exactly what fishears did not want to say.
[Galaxy S I9000 Android Development] solar666:
Sorry. But I still read the statement by fishears not like you obviously. Let's wait and see who will change what to become compatible with custom kernels like semaphore or Mackay.
[Galaxy S I9000 Android Development] fishears:
You read it right.

sent from somewhere..
[Galaxy S I9000 Android Development] aopvet:
My common sense says that stratos has to make his kernel compatible to cm11 again. Am I right?
[Galaxy S I9000 Android Development] jugster:
You are wrong. He doesn't have to do anything.

If he does anything, however, you should be grateful.

Signature? Signature!
[Galaxy S I9000 Android Development] DerTeufel1980:
Can you point me to a commit? I didn't find any

Gesendet von meinem SAMSUNG-SGH-I317 mit Tapatalk 2
[Galaxy S I9000 Android Development] ficko_98:
http://review.cyanogenmod.org/#/c/55212/ Maybe this? :fingers-crossed: This is only what i found in latest nightly which is related to battery.
[Galaxy S I9000 Android Development] DerTeufel1980:
Unfortunately not. We need a commit to either kernel or initramfs

Edit: seems like cm has fixed it itself. Working again on latest nightly without kernel change

Gesendet von meinem SAMSUNG-SGH-I317 mit Tapatalk 2
[Galaxy S I9000 Android Development] didhiy:
Just installed nightly 20131217 with my own kernel + ramdisk from 1st nightly (1206) and got some problems on battery percentage messed up & basic dream didn't show up

It fix by using ramdisk from 1217, I think libhealtd binary on sbin folder is causing the problem.

And there's a little changes in init.rc & init.cm.rc that make semaphore kernel not work properly

diff 1206 vs 1217:

http://pastebin.com/zVaggAfm
[Galaxy S I9000 Android Development] DerTeufel1980:
I got reported, that nightly of 18th is working well again. Let's see what happens when it is available for i9000

Gesendet von meinem GT-N7105 mit Tapatalk 2
[Galaxy S I9000 Android Development] knuckles1978:
Great work Stratos, I do certainly notice that everything runs great, more so than normal for sure, using your kernel. :good: :good:

One question however: how do I get video playback working after flashing the 3.4.0s kernel? I've read the OP and stratos's semaphore site, but I can only find a patch to flash to fix playback on JB, which I flashed anyway to try just in case, but no luck, so I'm stuck without YouTube for the moment. Thanks
[Galaxy S I9000 Android Development] zakitheracer:
http://xdaforums.com/showthread.php?p=47593682
[Galaxy S I9000 Android Development] Tarun.bhandari:
Battery Stats option missing and Battery % messed up

After installing 3.4.0s on CM11 from 17/12/2013, the Battery Stats option in Setting>Device> is no longer displayed. Also if one selects the Battery % options in Setting > Interface>Status bar> Battery Status style the % battery status is reflecting weird numbers.

If I am on stock CM11 kernel then this problem does not occur.
[Galaxy S I9000 Android Development] hertzschi:
:rolleyes: Just read a few posts (pages) before your question.... :silly:
[Galaxy S I9000 Android Development] Tarun.bhandari:
I did read the posts however it was not clearly evident whether they were referring to both the topics. I did read people talking about messed up % but did not find any mention to the Battery Stats option completely removed from the settings :rolleyes: :silly:
[Galaxy S I9000 Android Development] hertzschi:
Here it is:
[Galaxy S I9000 Android Development] DerTeufel1980:
Is it working for you again now?

Gesendet von meinem GT-N7105 mit Tapatalk 2
[Galaxy S I9000 Android Development] aopvet:
I can confirm that with today's nightly semaphore kernel works fine.
[Galaxy S I9000 Android Development] didhiy:
how about battery status?
[Galaxy S I9000 Android Development] aopvet:
No problems at all. :)
[Galaxy S I9000 Android Development] Rokostar:
Is zRam activ with this kernel
[Galaxy S I9000 Android Development] baciany:
So if its true that Semaphore working with newest Cm11 i will instal..

For Cm11 i need to use 3.4.0 or 3.4.0s ?
[Galaxy S I9000 Android Development] aopvet:
No zRam with semaphore.
[Galaxy S I9000 Android Development] hertzschi:
If you need ZRAM, you can give CyanCore a try

http://xdaforums.com/showthread.php?t=2184578
[Galaxy S I9000 Android Development] Tarun.bhandari:
Weird Battery Drain with CM11 19/12 Nightly

Hi I am on the CM11 19/12 Nightly with Semaphore 3.40s. I am experiencing weird battery drain or at least the battery % is not reflected correctly. It shows 81% and then suddenly sometime later the % drops to say 30% or so. Happened with both my batteries.

Is anyone experiencing this ?

Everything was fine with the 15/12 Nightly
[Galaxy S I9000 Android Development] N3tro:
The same happens with sema and mackay after reboot.
[Galaxy S I9000 Android Development] didhiy:
both kernel must update libhealthd binary
[Galaxy S I9000 Android Development] ts1506:
All kernels are working fine without update in the newest CM ROMs.
[Galaxy S I9000 Android Development] Rokostar:
I buy today a new headset. Philips she 9005 its with microphone and a button to take calls. So i plug them in and the sound is not good and if i press the button the sound is well. So the headset function is not working but its not important. Is this kernel releatet that they are working well as long as i press the button or a hardware oder software problem ?
[Galaxy S I9000 Android Development] ts1506:
I have a similar issue with my urBeats. They work fine in my other 2 devices (Galaxy Tab 10.1, Nokia N97), but here, it just gives a hollow sort of sound. Nothing to do with kernel.
[Galaxy S I9000 Android Development] superkoal:
Different polarity of the TRRS connectors. You can fix this by buying or soldering an adapter ;)

TRS headphones work fine.
[Galaxy S I9000 Android Development] zakitheracer:
Weird as I use a Nokia earphones with mic and they sound fine i.e no need for pressing the button on the earphones.

Although when I use them with my PC they sound hollow and when the button is pressed sounds fine.
[Galaxy S I9000 Android Development] rmsinaga:
Same experience with me when I used EarPump Aura headset. It only sounds better if I press the button.
[Galaxy S I9000 Android Development] superkoal:
This is not weird, just electronics ;)
[Galaxy S I9000 Android Development] Galaid:
meaning what exactly? better not to use 3rd party kernels on latest pawitp nightlies?
[Galaxy S I9000 Android Development] didhiy:
this mean if you find battery stat not working well in nightlies 1217 and after, then I think it caused by libhealtd binary in sbin initram folder. user can not change that, so must wait the kernel dev update that.

as you read some post before, seems it works fine in latest nightly, so I might wrong about libhealtd changes.
[Galaxy S I9000 Android Development] tetakpatak:
I've tried to flash over pawitp's CM11 20131222 nightly the Semaphore 3.4.0s.zip in CWM recovery and right after that KK-BigMem-libs from Mackay.

My i9000 didn't want to reboot anymore and I've lost the recovery mode also. I've made my i9000 working again with CM11, but I would really like to flash Semaphore and BigMem libs: does somebody know what did I do wrong? Should I rather flash tar file with Odin?
[Galaxy S I9000 Android Development] knuckles1978:
Lost recovery mode or just not selected advanced reboot mode from developer settings?

Can you not get into recovery mode with vol up+home+power any more?
[Galaxy S I9000 Android Development] gverma1:
I did exactly the same and it worked fine like always. This is what I did: reboot into recovery, flashed 20131222 nightly, flashed semaphore 3.0.4s zip, flashed KK-Bigmem libs zip, reboot. The phone came back up fine. Pls check if your zips are fine. The best way to check that is to try and open them in a file explorer (I use ES File Manager). They should open like a normal zip file showing their internal contents. If the zip is corrupt, it will not open.
[Galaxy S I9000 Android Development] tetakpatak:
Thanks.

But I've checked now and both my zip files were fine.

Any other idea why my i9000 didn't reboot anymore?
[Galaxy S I9000 Android Development] saszseb:
Try to flash bigmem.libs first then Sema_3.4.0s.
[Galaxy S I9000 Android Development] idCyber:
The way I always flash to ensure I am not getting bootloops : Flash ROM, bigmem libs, semaphore 3.4.0s, and lastly gapps
[Galaxy S I9000 Android Development] tetakpatak:
This way it worked, with the same files. Thanks, mate :)

[MENTION=4922358]idCyber[/MENTION] Thanks, I will remember that order now. My last order of flashing that resulted in light-bricking was:

cm11build.zip, gappsKK, reboot (success) sema3.4.0s.zip, KK-libs (crash by reboot)

(EDIT: guys, I'm on my limit for today, I will hit "thanks" tomorrow for both your posts)
[Galaxy S I9000 Android Development] Tarun.bhandari:
Hi what is the added benefit of flashing the KK-BigMem-libs from Mackay ? I am using CM 11 with Sema 3.40S and it shows 408mb RAM and works fine. Can you advise on the benefits of this KK-BigMem-libs from Mackay?

Can you also give me a link to these KK-BigMem-libs?

Thanks