yashsingh1/xdaforums huggingface dataset:
[Galaxy S I9000 Android Development] gverma1:
I would like to also give Slimbean official 4.3.1 a try. Have downloaded Slim-galaxysmtd-4.3.build.2.2-OFFICIAL-1768.zip from slimroms site. However, cant locate the associated gapps. Don't know if I can use the current AIO gapps from slimroms site since it has Google Launcher, etc. which may not be relevant for Android 4.3. Could you help? Thanks.

Edit: never mind.... found it.
[Galaxy S I9000 Android Development] tetakpatak:
Agree, SlimBean is amazing. But we already have a great Semaphore kernel there (stock one) :D

One more great new kernel by stratosk for the ICS would be great to have.
[Galaxy S I9000 Android Development] Kashif.Ali:
Semaphore

Best kernel ever
[Galaxy S I9000 Android Development] tsatomas:
Hi Strato, my thanks for your great work and contibution

Paypal 1KT15789S8827680Y ;)

Καλό Πάσχα
[Galaxy S I9000 Android Development] stratosk:
Hi!

Thanks so much for your donation, my friend! I really appreciate this!

Καλό Πάσχα!
[Galaxy S I9000 Android Development] geckoas:
Hello Stratosk,

I like to use Bluevpn app to connect my SGS with the built in data modem of my VW handsfree. When I use it with Semaphore 3.4.3s kernel on Cyanogen CM11 nightly 20140404 the bluetooth data connection to the handsfree gets established but Bluevpn gives the error message "your device does not support VPN connection" and no data is transfered. With the CM11 stock kernel the vpn connection gets established and data is transfered. Is it possible to have a bluetooth VPN connection with Semaphore kernel too.

sent from my galaxy I9000 running CM11 with tapatalk
[Galaxy S I9000 Android Development] gverma1:
Try enabling TUN module in Semaphore Manager. This module is needed for VPN connections. Maybe this will help.
[Galaxy S I9000 Android Development] tetakpatak:
Dear [MENTION=3750240]stratosk[/MENTION], Phil3759 has discovered few days ago that official CWM source has had a bug since longer time: it prompts by exit / reboot system if the device should be re-rooted (SU installed), but regardless of the choice, it will not be re-rooted. This bug has been there since about half year.

Have you debugged this in the Semaphore recovery?

tetakpatalked from the legendary i9000
[Galaxy S I9000 Android Development] stratosk:
Hi,

No, I'm not aware about this bug.
[Galaxy S I9000 Android Development] tetakpatak:
Did you check Phil's main thread? I think he has posted the update 2 or latest 3 days ago with bug fix. Possibly all the CWM source based recoveries are affected by this bug (PhilZ also was).

Maybe you can check Phil's commits?

In fact, if the one is rooted properly, it is not a problem. But if someone expects after this prompt to get rooted device and doesn't.....it is kind of bug. Interesting, right?

tetakpatalked from P5110
[Galaxy S I9000 Android Development] Saber:
Will this kernel work fine with the Cyanogenmod 11 M5 Snapshot?
[Galaxy S I9000 Android Development] saszseb:
Yes.

Tapatalk-kal küldve az én GT-I9000-el
[Galaxy S I9000 Android Development] vhngu930:
Hey [MENTION=3750240]stratosk[/MENTION],

I've bought a Moto G and I'm pretty happy with it. So I just want thank you for all the work you've done. I've always used your kernel and loved it.

So I just want to thank you for everything.

Bye [emoji22][emoji22][emoji25][emoji26][emoji29]
[Galaxy S I9000 Android Development] geckoas:
Hello Stratosk, I tried activating TUN module and it worked. The problem is that I have to untick and tick again the TUN module every time when I want to use VPN. Otherwise bluevpn says "your device doesn't support VPN connections".

sent from my galaxy I9000 running CM11 with tapatalk
[Galaxy S I9000 Android Development] Steephig:
So long

[MENTION=3750240]stratosk[/MENTION]

So long and thanks for all the fish kernels!

After almost 4 years of trusty service it was time to move to faster hardware. Would have been been much earlier if Semaphore didn't keep my phone much more usable all these years.

I hope the LG G2 has the same high quality kernel and dev as Semaphore.
[Galaxy S I9000 Android Development] stratosk:
Thank you for your kind words, my friend!

I hope you will enjoy your new device!.

BTW, you said "goodbye" using the title of one of my favorites books. And Douglas Adams is my favorite writer. :)
[Galaxy S I9000 Android Development] baciany:
is ART work on this kernel combined with CM11 ?
[Galaxy S I9000 Android Development] tetakpatak:
Dear [MENTION=3750240]stratosk[/MENTION], Phil3759 has totally opened the sources for his PhilZ touch last week.

Would it be any interesting idea for you to compile a Semaphore kernel version with PhilZ? I'm sure you would easily find testers for all versions of ICS, JB and KK

Or is it principally against your attitude to compile the kernel apart of Semaphore recovery?
[Galaxy S I9000 Android Development] limnaln:
That's a great idea. :) +1
[Galaxy S I9000 Android Development] limnaln:
So, is this kernel abandoned for our device and if it is, can i keep building it if the dev can't for our specific device?
[Galaxy S I9000 Android Development] idCyber:
I think you can make your own kernel based on Semaphore sources.
[Galaxy S I9000 Android Development] limnaln:
Yep, i can, should i try?
[Galaxy S I9000 Android Development] didhiy:
The source is there, the guide to build is very helpful too... the only one that helps me when try to build a kernel for sc-02b

Just fork the source, add anything that you think will improve it, test it by yourself then you may create a new thread to share your kernel
[Galaxy S I9000 Android Development] MetalPainis:
On latest CM11 Nightlies (the latest 3 I checked), the latest kernel causes force closes, when trying to open the status settings (where IMEI, signal-strength and so on can be found) among some other issues. With CM 11 stock kernel everything appears do be fine.
[Galaxy S I9000 Android Development] karbon222:
not confirmed, i open fine
[Galaxy S I9000 Android Development] Naxiz:
I can confirm this. Settings shows baseband version unknown, I don't have signal and opening status crashes settings. I've been reinstalling for a few hours now, checking all md5s, before I figured that Semaphore was the problem.
[Galaxy S I9000 Android Development] jpmccarthy:
Don't seem to have this issue on the 2 phones I have here.
[Galaxy S I9000 Android Development] Naxiz:
I tried it with both Cyanogenmod and Slim ROM now, same problem. Full clean install. Only happens with 4.4.3 it seems, at least it worked fine with 4.4.2.

However I accidently found a solution: simply remount /efs (as rw?) and you'll be asked for your SIM code a few seconds later (and baseband is restored) until reboot that is.
[Galaxy S I9000 Android Development] jeroendj2:
I installed it on stock cm and it made some phone.apk crash, and i didnt have a signal

edit: 3.4.3 worked :D
[Galaxy S I9000 Android Development] a-id:
I can confirm this too. With Mackay kernel 0.690 (2-June-2013) all is working.
[Galaxy S I9000 Android Development] TaMNoNa:
What is the newest version for Android 4.2.2 (CM 10.1.13)?
[Galaxy S I9000 Android Development] limnaln:
Read the 1-st page. Version 3.0.0.
[Galaxy S I9000 Android Development] Tusnal:
Working very good on cyanaosp 4, but can you please add touch recovery?
[Galaxy S I9000 Android Development] dmcleod:
Which kernel for OMNIROM KK the normal or the "s" version? Thanks
[Galaxy S I9000 Android Development] ★Michaelo★:
Use normal version :good:
[Galaxy S I9000 Android Development] Eleanor1967:
I'm getting camera fc's since I flashed latest kk kernel. Known problem or just me ?

MfG Eleanor1967
[Galaxy S I9000 Android Development] Angristan:
Dont use this kernel with a recent ROM, it's not up to date.
[Galaxy S I9000 Android Development] tetakpatak:
The latest Semaphore KitKat kernel works good with 4.4.2 roms, but it hasn't been updated for 4.4.3 and 4.4.4 roms, AMAIK

tetakpatalked from P5110
[Galaxy S I9000 Android Development] limnaln:
What has to be updated, it's smooth and works for 4.4 roms, what else do you need? :laugh:
[Galaxy S I9000 Android Development] tetakpatak:
IDK as I use a ICS rom on my i9000 and won't flash anymore KitKat on it. For many other devices kernel vendor blobs had to be updated again recently to make camera working properly.

tetakpatalked from P5110
[Galaxy S I9000 Android Development] limnaln:
I changed to ICS too, but i want more modern look, what rom should i use?
[Galaxy S I9000 Android Development] tetakpatak:
Try my favourite JB and KK then: either SlimBean 4.3 or Mackay Omni 4.4.2 ;)

Both roms have dark mode (flash SlimGapps) and many tweaks for maximal customizing so installing Xposed frameworks modules isn't necessary.
[Galaxy S I9000 Android Development] idCyber:
Use an android 4.2.2 ROM , stay away from 4.3 like it would be AIDS for our phone. It's way too slow for I9000
[Galaxy S I9000 Android Development] limnaln:
I'll try Mackay 4.9.6 for now if i don't notice serious lag.
[Galaxy S I9000 Android Development] Eleanor1967:
I cleared camera's data and a day later the camera just started working again, guess I'm fine for now. It's a shame this kernel is discontinued..

MfG Eleanor 1967
[Galaxy S I9000 Android Development] MetalPainis:
Well it's a little sad but understandable. It's an old device. At least all sources can be used, in case someone wants to continue the amazing work. I gave my i9000 to my sister now with mackay kernel instead, seems fine to me :)
[Galaxy S I9000 Android Development] a-id:
Hi [MENTION=3750240]stratosk[/MENTION]! Is your kernel no longer supported? I think you need to edit thread name...
[Galaxy S I9000 Android Development] stratosk:
Hi!

What do you mean by 'supported'?

Thread's name looks fine to me. What's wrong with it?
[Galaxy S I9000 Android Development] limnaln:
Hi.

He asks are you continuing the kernel or you've dropped the support.
[Galaxy S I9000 Android Development] stratosk:
Hi.

No plans for new version. I don't know if I will continue work for SGS or not

I don't like the term support.

This is not a company. I'm an individual, amateur kernel developer.

I don't provide official support but most of the time I'm willing to help if I feel that I can help.

I believe that thread's name is good and I don't have to rename it to 'unsupported' or something similar or close it.

If someone wants to read it, good. If not, good again. All the info, change log, dates are in OP and if someone read it , he can understand what he will flash.
[Galaxy S I9000 Android Development] tetakpatak:
+1
[Galaxy S I9000 Android Development] a-id:
Yes, I asked about that. Thread is OK, but it'll be good if you'll say when you'll decide to stop further development of this without a doubt a wonderful kernel...
[Galaxy S I9000 Android Development] grinder777:
It is quiet easy:

Stratos made this kernel when he has had a SGS.

Now he has a N4 and is doing kernels for that one.

He is doing this - just for fun - at his free time and he has a job and a family beside. This kernel thing is his hobby and he just let us take part. You can see that he is still following this thread and you can be sure, if something REALLY BIIG is needed, it will be done.

Thank you Stratos for this great thing you did here!!!

Gesendet von meinem K1 mit Tapatalk

---------- Post added at 03:22 PM ---------- Previous post was at 02:52 PM ----------

@stratosk

Have you seen that?

http://xdaforums.com/showthread.php?p=54421404

"...

the installer will only replace the zImage of your current flashed boot.img

and still use the ramdisk wich comes with the original boot.img

- that's why it works on every Android 4.4.4 Rom

..."

People said this kernel is working on a 4.1.2 stockROM as well...

Gesendet von meinem K1 mit Tapatalk
[Galaxy S I9000 Android Development] stratosk:
Thanks, I know about it, I use this in N4 kernel.

But it's quite difficult to do it in SGS, because of custom initramfs I use.
[Galaxy S I9000 Android Development] grinder777:
I know there were some difficulties at N4 kernel tu use it at CM or stock... for that I wrote. Nice to hear about that solved ;)

Gesendet von meinem K1 mit Tapatalk
[Galaxy S I9000 Android Development] stratosk:
CM uses some patches that I didn't include it in Semaphore N4 kernel.

This make Semaphore incompatible with CM (for N4).
[Galaxy S I9000 Android Development] kalpetros:
I flashed the latest 3.4.3s Kernel and I noticed that some of my apps are gone. I'm using the latest nightly Cyanogenmod ROM (20140801).
[Galaxy S I9000 Android Development] ★Michaelo★:
This kernel is incompatible with new nightlies
[Galaxy S I9000 Android Development] jpmccarthy:
What isn't working? Any other kernel recommendations to get big mem?
[Galaxy S I9000 Android Development] deeppans:
A big THANK YOU Stratosk!

Without you and [MENTION=3117667]pawitp[/MENTION] I don't think I would have enjoyed SGS company. May God bless both of you.

Recently my wife lost my beloved SGS. ?

although I will be leaving this thread I will be in touch as I will be using Semaphore on N4.

Thanks for your work & humble help all the time.
[Galaxy S I9000 Android Development] ★Michaelo★:
For bigmem use Mackay Kernel 0.691
[Galaxy S I9000 Android Development] jpmccarthy:
Using semaphore with latest nightly, all seems fine. What was incompatible?
[Galaxy S I9000 Android Development] Hayabusa_XDA:
CM11 and TowelRoot

Hi Stratosk,

first of all many many thanks for supporting the now old i9000 for all those years.

I'm still using it by and then although my actual main phone of course is a "little" more powerful.;)

Yes, such work shouldn't be taken for granted, but I guess most longer time members in this forum would never demand anything.

And this is kind of sad.

Of course I know SGS has reached the end of its lifetime and you don't own this phone any loger but it's still a nice pice of hardware and in some cases even has some advantage over newer phones - (e.g. could do longer gps / car navigation on battery only).

So I came to the conclusion that CM11 will be my last SGS firmware - and M9 snapshot is running nice again, maybe as good as M5(?).

The only thing that's missing to make the most out of this scenario is a working semaphore kernel.

Furthermore as there is no “TowelRoot” hardened semaphore kernel out there, this forced me to use the CM kernel at the moment and meant that there will be no going back to older Android version either.

As “TowelRoot” is such a big bug, you seriously shouldn't use a phone without a patched kernel any longer and that unfortunately means that no semaphore kernel out there can be recommended any longer.

Perhaps this might change your mind. Even if not, many thx for your work - in fact you prolonged its lifetime a lot.
[Galaxy S I9000 Android Development] tetakpatak:
True w/o doubt, but stratosk doesn't even own his i9000 anymore.

tetakpatalked from N7100
[Galaxy S I9000 Android Development] taninos:
Netflix problems with bigmem patched kernel versions

Hi [MENTION=3750240]stratosk[/MENTION] , do you know why your "s" kernel versions are not compatible with CM and Netflix. I currently use the stable CM10.2.1 combined with your 3.3.0 and both works flawless, but with 3.3.0s the rom is unable to work with Netflix. This is also happening with other forks of your kernel, the bigmem patch doesn't work with netflix, but why?

Best.
[Galaxy S I9000 Android Development] moorkai:
Problems with compiling Semaphore, help!

Hi everyone!

Sorry if this question was already answered. I've searched for the answer, but found none.

I’m trying to build Semaphore KK kernel on my Arch (OK, Antergos, to be precise) lappy with the intent of eventually trying to merge Atmel’s contribs to the mXT224 driver. While using Galaxy as my primary phone it was the most stable kernel out there, both overclocked and on stock clocks, surpassing stock CM and most of the good old custom kernels, though I don't know about the new kids on the street, a.k.a. Arrow, NeatKernel and the likes, which makes it a great foundation for all kinds of experimenting. However, with or without messing with the file structure, the build, when flashed on my Galaxy, results with a nasty bootloop, not even showing the Semaphore kernel logo.

As per build instructions on the official Semaphore website for Semaphore JB, I typed as follows (while being in the home, ~/ folder):

mkdir -p semaphore/output/galaxys
mkdir -p semaphore/output/captivate
mkdir -p semaphore/output/vibrant
cd semaphore

Then I downloaded the Linaro toolchain (I downloaded this one, wrong?), unpacked it with GNOME’s file-roller to ~/semaphore/ and symlinked to ~/semaphore/toolchain.

cd semaphore
ln -s gcc-linaro-arm-linux-gnueabihf-4.8-2013.10_linux/bin/ toolchain

Seems good, no errors for now. Next up is cloning git repos. I specified the kk-4.4 branch for both of them as I wanted to compile the KK version with the KK ramdisk, not an older JB or ICS version.

git clone -b kk-4.4 git://github.com/stratosk/samsung-kernel-aries
git clone -b kk-4.4 git://github.com/stratosk/ics-ramdisk

After a long wait (my connection is 4 Mbit/s, so ... it took quite a while till it finished), it’s downloaded. Unpacking ramdisks ...

cd ics-ramdisk
tar zxvf jb_combo.tar.gz
tar zxvf jb_combo_c.tar.gz
tar zxvf jb_combo_v.tar.gz

Skipped the third step as there was nothing to do on my side. The defconfigs are there, ready for building.

Further on, entering the kernel directory and building the kernel.

cd ~/semaphore/samsung-kernel-aries/

As ./sbuild galaxys didn’t work for me, I initiated the build process by typing sh sbuild.sh galaxys instead.

After 7 minutes and 48 seconds, the build finished (here's the log too). Regardless of the way I flash it (be it through CWM or with Heimdall), the result is a nasty bootloop as I've said in the beginning.

What am I doing wrong?
[Galaxy S I9000 Android Development] DerTeufel1980:
You shouldn't use toolchain newer than 4.7

There seems to be a kernel panic right after kernel init by using newer toolchain. I never was able to fix this, because there's no way to debug it in this early stage (at least non I know of).
[Galaxy S I9000 Android Development] kathees:
Hi stratosk,

I'm in CM 10 like 3 weeks and was waiting until I feel it stable. I thought let's try your Kernel later so that I can see the difference :). In ICS I was using yours.

Today for a by mistake wireless issue (I forgot one character in password so couldn't connect) I flashed your kernel. Accidentally I flashed 's' version Semaphore_JB_2.0.6s version. And for fast few hours I didn't had any problem with the phone. My Ram showing as 391MB. And I never done any modification to my phone so I'm pretty sure I don't have the patch. (Stock CM10).

How it's possible? Since it's working why can't I use 's' version. What I'll be missing. I know 720p vider recording will not be available for BigMem version.

Thanks for your great work...
[Galaxy S I9000 Android Development] jdogzilla:
For those on CM10 latest build and Semaphore what governors and settings are people using that is giving optimal performance without much compromise to battery life? Please share. Thanks.
[Galaxy S I9000 Android Development] matesc:
My settings:

ondemand or ondemand40

smooth ui disabled

lock min freq to 100 enabled

scheduler - CFQ

Deep idle disabled

bigmem enabled

touchwake- 15s

sdcard read ahead - 1024

auto brightness driver - dark (with turned on automatic brightness in android settings)
[Galaxy S I9000 Android Development] djlukas1983:
I need nstools to manage uv. Semaphore app does't have this option.

Wysłane z mojego GT-I9000 za pomocą Tapatalk 2
[Galaxy S I9000 Android Development] Michel38280:
Just installed with the last nightly CM10 ... it sounds good :angel:
[Galaxy S I9000 Android Development] jdogzilla:
Thanks. Any indication of how much these setting have helped? In battery life? Performance? ANybody else wants to add in their settings?
[Galaxy S I9000 Android Development] stratosk:
Hi,

's' version will work fine on cm10, except the issues in camera and in video playback. If you don't have these then most probably you have patched your ROM.
[Galaxy S I9000 Android Development] kathees:
Hi,

Thanks for the reply. Can I know what is the issue in camera and video playback? I tested it my self. Camera I can take photos without any problem. But video 480p/720p both I can't shoot.

As for video I tried a .avi video in MoboPlayer and it's playing.

I'm pretty sure I haven't patch the CM10. It's stock except your kernel.

It's looks like if we can give up video recording we can have more ram :) (Without 's' version even if we enable BigMem we can't get 391MB - But in that 480p video record-able.)

Anybody have any idea CM10 by default includes the patch??

I tried to enable BigMem and checked what happens. It's same again camera photo taking working and video playback working. Can't shoot video. In that case can I assume 'if we use "s" version in CM10 we will only lose video recording no matter normal/BigMem version'?
[Galaxy S I9000 Android Development] yahyoh:
here the latest patch it was posted 2 or 3 page back ( i didn't test it :o )
[Galaxy S I9000 Android Development] kathees:
Thanks for the patch. I don't want to use any modifications for now :). I was just wondering whether this patch is included in Cm10 by default. Because I observed I can use 's' version in Cm10 with/without BigMem and only video recording not working. (Both 480p and 720p)
[Galaxy S I9000 Android Development] yahyoh:
no its not include and it will not

big mem will break 720p , S version will not break anything if use it on patched rom or if use the patch on any rom
[Galaxy S I9000 Android Development] kathees:
Thanks, I'm aware that BigMem in normal version will break 720p.

My doubt is if we use 's' version in a unpatched rom what will break? For me only Video record breaks both 480p and 720p. I'm doing more tests to findout. Problem is with 's' version in un patched rom 480p video record also fails.
[Galaxy S I9000 Android Development] yahyoh:
it will break some video types playback and maybe 720p playback idk and it will break the camcorder :(

why u don't wanna use the patch and make things easier :)
[Galaxy S I9000 Android Development] kathees:
Hi,

You're correct. I tried to copy some of the 720p videos and play it in MoboPlayer. They are playing but very snappy. Frame rate is very very slow. But normal videos play fine. (Both with/without BigMem)

I'm going to use patch, thanks for the suggestion. :) I'm just curious to find out things ;)

Anyway now my final conclusion is, if we use 's' version in unpatched rom

1) Video recording won't work (Both 480p and 720p)

2) 720p video playback very snappy

3) camera photo taking no problem

Strange same observation for BigMem enabled and disabled :confused:

BTW,

I guess for 's' version also (if we patch the rom) enabling BigMem is same effect as normal. (i.e 720p video recording won't work) How about 720p playback? Will it work? Correct me if I'm wrong...
[Galaxy S I9000 Android Development] yahyoh:
yes it will not work :)
[Galaxy S I9000 Android Development] kathees:
Deleted!
[Galaxy S I9000 Android Development] jugster:
You probably don't mean snappy. Stuttering is probably what you want to say. Right?

Signature? Signature!
[Galaxy S I9000 Android Development] kathees:
Yeah, that's what I meant :). Video breaks play like step by step and not good sound also. Some videos I couldn't hear anything and it was like screaming :)

But just now I flashed CM10 stock kernel but still video playback is stuttering. It's some mkv format 720p videos. I play it in MoboPlayer. One song is around 250MB. Anyone can play videos this size? If not any player I can play without issues?

Okay, I downloaded some 720p videos from youtube and they work fine. But their size is less than 100MB. So I guess my files are too big to play.... :(