yashsingh1/xdaforums huggingface dataset:
[AT&T Samsung Galaxy S II SGH-I777] dashrendar:
Thanks for the great work, Render. I flashed the ROM followed by your custom kernel from 3/22. No issues whatsoever so far. I'll report any issues I may find, but at the very least, I didn't encounter any installation issues.

One thing is that the new ROM has a newer recovery than the kernel I installed (CWM x.28 rather than x.27), but I assume the upcoming kernel build will have the newer version of CWM.

Thanks again!

Update: I forgot to mention that I did a dirty flash, not a clean one. 12 hours later and things are stable. Wi-Fi was working as I received both personal and work e-mails and WhatsApp messages. Used the alarm to wake up and Bluetooth audio streaming to my car's receiver and placed a call. No problems with any of those. On Zzmoove default profile of course.
[AT&T Samsung Galaxy S II SGH-I777] RenderBroken:
Thanks my brother! I appreciate you lettings others know how it has worked for you. I was thinking about merging the Stock Build with my kernel but I do think it would be best to leave it alone and have them be separate. Also right now the one building the rom is [MENTION=4795888]love4k21[/MENTION] . I has kindly lifted the burden off of me and will continue to build as his own life permits. RIght now the plan is a weekly build. I will host them on my mediafire account for faster downloads. I should start continuing work on the new kernel build. Its going to be massive!
[AT&T Samsung Galaxy S II SGH-I777] SteveMurphy:
Great news, my friend. Most of us know that the kernel is the lifeblood of the phone, so we greatly appreciate your continued support.

The ROMs some of us can take care of, the kernel... not so much!
[AT&T Samsung Galaxy S II SGH-I777] RenderBroken:
Thanks! :) Its good to see ported roms flourishing lately! Thank you for kicking butt in that dept. I will support the S2 for as long as feasible. I have some commits bookmarked for the next build that I am excited to see how they work out on the S2.
[AT&T Samsung Galaxy S II SGH-I777] d_j_l:
There was a commit that touched the mic swap in i9100 cm11 nightly. Will it changes the porting process to i777?http://review.cyanogenmod.org/#/c/63862/
[AT&T Samsung Galaxy S II SGH-I777] bondlolo:
Or maybe we can use the same nightlies? Like a unified build for the Galaxy S2?
[AT&T Samsung Galaxy S II SGH-I777] koizumi7:
Thanks for great work, love4k21! Finally the rom has regular releases.

However, you should consider letting people know about new builds you upload. Until today, I thought that the build from 03.05.2014 was the latest one...

And basing on number of downloads of the releases I was not the only one with this problem (build from 03.05 was downloaded 28 times, builds from 04.05, 11.05 and 13.05 - 5 times jointly).

For everyone wondering where to find latest releases: http://d-h.st/users/love4k21.
[AT&T Samsung Galaxy S II SGH-I777] dashrendar:
I like how love4k21 leaves comments regarding his experience with the builds.

I think we should do the same thing. Whoever downloads should leave one or more comments regarding their initial and long-term experience. This would give a better sense about the stability of the build.
[AT&T Samsung Galaxy S II SGH-I777] desteele:
Where are you seeing any build updates? I still only see 4/30 as the last build... I check Render's hosting folders, and same thing. I thought he had pretty much quit building...
[AT&T Samsung Galaxy S II SGH-I777] SteveMurphy:
He's just really busy. You know, he gave us this amazing kernel (3/22 version); if newer builds are important to you you could use it to port one for yourself, or look in the ported thread; all of the KK ports over there exist because of his great work.

I'm certain he'll update his CM build when he has the time.
[AT&T Samsung Galaxy S II SGH-I777] desteele:
Oh, that wasn't a slam or anything, I just seriously thought life had taken too much and he didn't have time to build anymore. I'm using one of the ported ROM's, and it works very well, and I'm very content with it. Thanks...
[AT&T Samsung Galaxy S II SGH-I777] cyril279:
building slim for the i777

Dear [MENTION=5438598]RenderBroken[/MENTION], (or ANYONE with build experience)

summarized: I got slim to build (twice), but it won't boot unless I sub in a different boot.img, and when it boots fully into android, I don't have use of my capacitive buttons at all.

yes, flashing your kernel over the i9100 version works, but without NFC.

Is there any hope for a proper i777 slimkat build?

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

I recently ported Slim's i9100 build to the i777 just to take it for a spin, and was very impressed. Less is definitely more! I missed the NFC functionality (i9100 doesn't have NFC), and so decided to try building it since the necessary Github projects seemed to be present. I did get an i777 build to complete succesfully (I renamed and edited the slim_i9100_defconfig**), but the raw build wouldn't boot past the initial samsung logo. I replaced the boot.img with Omni's, which allowed me to boot fully into i777-slimkat, but my capacitive buttons didn't work at all, even after flashing The RB kernel.

I feel like I am SO close, I follow instructions well enough to get a build off, but I am not any kind of developer. I'm hoping there are a few specific places that I should be looking? would it be better to contact the original i777 slim bringup dev (@Fronti90) for tips? is there a better place for this question? I was under the impression that slim frowns on porting or kanging their stuff, but I was told within the slim forum that as long as it's marked as unofficial, and credited correctly, that there would be no issue.

local_manifest.xml used:

<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<remote fetch="https://github.com/DonkeyCoyote" name="Slim" />
<project path="device/samsung/i777" name="device_samsung_i777" remote="github" revision="kk4.4"/>
<project path="device/samsung/galaxys2-common" name="device_samsung_galaxys2-common" remote="github" revision="kk4.4"/>
<project path="hardware/samsung" name="hardware_samsung" remote="github" revision="kk4.4"/>
<project path="kernel/samsung/smdk4412" name="kernel_samsung_smdk4412" remote="github" revision="kk4.4"/>
<project path="vendor/samsung" name="DonkeyCoyote/proprietary_vendor_samsung" remote="github" revision="android-4.4" />
</manifest>

**slim_i9100_defconfig changes:

line;value
--------------
432;CONFIG_TARGET_LOCALE_NAATT_TEMP=y
436;# CONFIG_TARGET_LOCALE_EUR is not set
692;CONFIG_CMDLINE="console=ttySAC2,115200 consoleblank=0"
693;CONFIG_CMDLINE_FROM_BOOTLOADER=y
694;# CONFIG_CMDLINE_EXTEND is not set
2267;CONFIG_SND_SOC_MC1N2_MIC_ADC_SWAP=y
[AT&T Samsung Galaxy S II SGH-I777] RenderBroken:
This is great! you are Very close. I am not sure why its not booting with the stock boot.img though. I would check that the ramdisk is being made properly. ALso when you say the buttons don't work? do you mean the lights or the entire button in general? You should have a file called "sec_touchkey.kl" and it should be about 113 bytes. When you flash my kernel it should add that file into the rom itself. This is was dictates the Touch Keys. (I believe)

Another thing to do is look at CM's versions of the same repos. Slims may be outdated for the i777 so you may be able to borrow the newer files from CM as long as they are the SAME file, just newer. This may fix your Kernel not booting.

Lastly I don't think NFC will work properly with KK. There are some security checks in place by the software that our version of NFC wont work with from what I have gathered. SO you may be spinning your wheels for something that won't even work. afaik Keep me updated with your progress though!
[AT&T Samsung Galaxy S II SGH-I777] cyril279:
I777 on KK is perhaps NFC challenged, but definitely capable. I use it regularly via superbeam to transfer files in between my wife's i777 and mine.

The capacitive buttons light up, but are completely non-functional, even AFTER I flash the RB kernel, which installs the correct touchkey.kl. I just noticed that slim implemented a hardware-key-rebinding setup in January, that never made it to the i777 device repos. I'll have to test it to be sure, but I've got high hopes for that making a difference.

https://github.com/SlimRoms/device_samsung_i9100/commit/10ec28d61cc14f954c3f41f5d202cdb0b42fcd10

https://gerrit.slimroms.net/#/c/2388/

Ramdisk? I'll (google how to) look into that :confused:

Thanks for pushing me (back) in the direction of looking at the device repos. The i9100 is fully functional, and there aren't many differences in between the two devices; therefore keeping the i777 afloat seems reasonably achievable.
[AT&T Samsung Galaxy S II SGH-I777] rogersb11:
Even with I working built kernel something "I"(meaning clearly subjective lol) like to do is set up my ROM and then when using custom or stock kernel use adb to extract my current and already set boot.img that clearly works and then just copy it to my fresh build zip for personalized kernel(custom or not). Note This Will Only Work If your current kernel is compatible with the ROM you are building. I assumed it was as the s2 only has a few kitkat ROMs. Adb command available on request or you can find it any kernel zip for your device in the updater-script.

PS: yikes, sorry [MENTION=5438598]RenderBroken[/MENTION]. That really ran on and I could have said tons more but less than you could no doubt haha. Endless possibilities with potential endless problems as well. Pretty damn enjoyable if you ask me
[AT&T Samsung Galaxy S II SGH-I777] cyril279:
Massive thanks for pointing me back to the repositories, I was able to track a few recent i9100 changes and I got a bootable, fully functioning build!

The i777/i9100 are both supposed to reference a "kk4.4-old" kernel branch, but that change wasn't captured in the "slim.dependencies" file of the i777 device branch.

Once I had my local_manifest pointed to the correct kernel repo, things started making more sense.

The hardware key changes live in Slim's frameworks, which explains why flashing a different kernel didn't affect it.

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

I hated the idea of on-screen navigation keys for the longest time, because it causes an already small screen, to be even smaller, when it doesn't need to be.

I was FORCED to use them in order to test my original malfunctional builds.

I actually like them a lot. The huge range of customability is addictive. Nav-ring sleep button is boss.
[AT&T Samsung Galaxy S II SGH-I777] SteveMurphy:
Great job, a huge accomplishment!
[AT&T Samsung Galaxy S II SGH-I777] geicogecko:
Anything on Sound Search yet?
[AT&T Samsung Galaxy S II SGH-I777] rogersb11:
Just out of curiosity do you have velvet.apk installed? Had this same problem on a tw kit Kat rom
[AT&T Samsung Galaxy S II SGH-I777] ElectroManiac:
I just install this rom not long a go and when I boot up, when I get into the lenguage selection part I get an error with com.android.phone.

Any idea how to fix this?
[AT&T Samsung Galaxy S II SGH-I777] rogersb11:
Go back to recovery and try wiping cache and dalvik
[AT&T Samsung Galaxy S II SGH-I777] ElectroManiac:
Did that still gettint the same error. I already try wiping data, formating system, wiping cache/davilk, re installing the rom, and still when I boot up and I have to choose the lenguage I keep getting the same error.
[AT&T Samsung Galaxy S II SGH-I777] razen_kain:
You'll have to flash renderbroken's custom kernel over it. The stock kernel is broke on that build for some reason. If you want cm mr-cook has a more up to date version in his cooked ROM thread. I don't think renderbroken is building for this device anymore.
[AT&T Samsung Galaxy S II SGH-I777] ElectroManiac:
Sorry for bothering but do you have a link for one of those kernel?
[AT&T Samsung Galaxy S II SGH-I777] razen_kain:
http://xdaforums.com/showthread.php?t=2582364
[AT&T Samsung Galaxy S II SGH-I777] ElectroManiac:
Thank you. Will give it a try
[AT&T Samsung Galaxy S II SGH-I777] rogersb11:
If anyone ever needs updated build just let me know. I run them off every night anyway for my GF. No sabermod at the moment tho
[AT&T Samsung Galaxy S II SGH-I777] dashrendar:
No problem changing language for me. I tried Arabic. No errors. What language did you try to switch to do that I can try it? I'm currently using build 5/22 and kernel 3/22.

Also not sure why the kernel would care about OS language setting.

Bio: I was born and I haven't died yet.
[AT&T Samsung Galaxy S II SGH-I777] rogersb11:
i fixed it by replacing the telephony.apk. crazy the kernel fixes too. Damn phones

---------- Post added at 02:25 AM ---------- Previous post was at 02:21 AM ----------

Here's a freshly synced build for those interested. Has SuperSU and STweaks already. Stock kernel for those that want it but can use Render's as well. Stock running fantastic tho just to note. Also if your happs replaces trebuchet with google now I HIGHLY recommend installing it again because Trebuchet is by far the better launcher and it's not even close. http://d-h.st/o8b
[AT&T Samsung Galaxy S II SGH-I777] koizumi7:
[MENTION=5438598]RenderBroken[/MENTION] [MENTION=4795888]love4k21[/MENTION] could you consider posting changelog for your new builds?

Updating version not knowing what they fixes is a bit frustrating :(
[AT&T Samsung Galaxy S II SGH-I777] SteveMurphy:
Pretty sure their builds are stock, in which case you could find the CM changelog on their official site.
[AT&T Samsung Galaxy S II SGH-I777] MO11:
i installed that update 5/26 you posted etc but no play store and when i tried to connect to google account it cannot reach to google servers

so is there is something that i shall know for this ?:cyclops:
[AT&T Samsung Galaxy S II SGH-I777] rogersb11:
You install gapps?

---------- Post added at 07:54 AM ---------- Previous post was at 07:52 AM ----------

Flashed gapps?
[AT&T Samsung Galaxy S II SGH-I777] MO11:
yes i did i always install slim gaps , or shall i install another gaps ?
[AT&T Samsung Galaxy S II SGH-I777] rogersb11:
I always use these old ass ones. It's working here. Clean install? This build is set up different than renders

---------- Post added at 08:01 AM ---------- Previous post was at 08:01 AM ----------

http://goo.im/gapps/gapps-kk-20140105-signed.zip
[AT&T Samsung Galaxy S II SGH-I777] MO11:
i always do clean install :) and yes i know that this is different than renders and i tried to download the gaps from your link but not found

am gonna try to get the gaps and try again and i would appreciate to get the update builds . thank you for the fast reply by the way :)
[AT&T Samsung Galaxy S II SGH-I777] rogersb11:
I'll upload them and send you a link. Give me minute
[AT&T Samsung Galaxy S II SGH-I777] MO11:
thank you. i was just downloading the gaps from cyanogens website now and i was referring to the future cm builds :) :cyclops:
[AT&T Samsung Galaxy S II SGH-I777] rogersb11:
No problem. By clean I mean wiping system as well , not just factory reset to be clear. At least the first time anyway
[AT&T Samsung Galaxy S II SGH-I777] MO11:
yeah i got that i do a full wipe to avoid any issues :)
[AT&T Samsung Galaxy S II SGH-I777] rogersb11:
Anyone wondering runs fine with 01052014 gapps. I'll post a link to those as well with next build to avoid troubles
[AT&T Samsung Galaxy S II SGH-I777] geicogecko:
As near as I can tell, that is Google Search, and yes, I do have that.
[AT&T Samsung Galaxy S II SGH-I777] love4k21:
http://www.cmxlog.com/11/i9100/
[AT&T Samsung Galaxy S II SGH-I777] geicogecko:
Is UMS and MTP disabled in the kernel? I cannot get it to work.
[AT&T Samsung Galaxy S II SGH-I777] MO11:
activate usb debugging option and then go to storage from system settings and from click menu option and you will find usb computer connection and then choose UMS :) hope this helps :cyclops:
[AT&T Samsung Galaxy S II SGH-I777] geicogecko:
Thanks. I didn't know that option was there. However, this confirms that my USB port is broken again. The phone just charges, and doesn't recognize that it's plugged into the computer.
[AT&T Samsung Galaxy S II SGH-I777] MO11:
at least now you know what needs to be fixed , good luck:D
[AT&T Samsung Galaxy S II SGH-I777] dashrendar:
UMS and MTP working here with build 5/22. However, I do have the issue of hanging, freezing during file transfers from the PC to the phone. I think this is a known issue, right?

My USB port is working so far. I try to take care of it by treating it gently, with the occasional foot massages and candlelight dinners.

Bio: I was born and I haven't died yet.
[AT&T Samsung Galaxy S II SGH-I777] MO11:
am on the build 5/22 and all working fine on my mac but i only notice the freezing and hanging while transferring files on windows if you have multiple devices or drives connected via usb at the same time but other than that all working for me :cyclops:
[AT&T Samsung Galaxy S II SGH-I777] rogersb11:
Almost done with a new build which now includes sabermod toolchain. Lots of fixes including reportedly fixes message notifications not going away after you've replied. I'll post a link

---------- Post added at 11:04 PM ---------- Previous post was at 10:10 PM ----------

Ok, here ya go. Noticeable speed difference. ENJOY!!! http://d-h.st/XxP
[AT&T Samsung Galaxy S II SGH-I777] love4k21:
well thats nice, since they changed something with the recovery partition i don't get a build to boot.
[AT&T Samsung Galaxy S II SGH-I777] rogersb11:
Huh? Sorry man i don't follow this thread that closely
[AT&T Samsung Galaxy S II SGH-I777] MO11:
i just updated my phone and noticing the speed is faster but didn't have enough time yet to enjoy it , thanks man for your work :) :D
[AT&T Samsung Galaxy S II SGH-I777] d_j_l:
Rogersb11's 5/31 build works for my i777. Maybe SGH-S959G needs a fork build since it has a recovery partition.
[AT&T Samsung Galaxy S II SGH-I777] rogersb11:
I actually have the 959 version myself and it works fine. I don't include the recovery in the build since they have to be flashed differently on the two phones
[AT&T Samsung Galaxy S II SGH-I777] cyril279:
Summary:

-What controls device availability for the "lunch" command?

-Can I make "lunch slim_i777-userdebug" available, when the device is on a different source remote?

[MENTION=5438598]RenderBroken[/MENTION] and anyone else with build/github experience,

I'm interested in building slim-saber. Fusion jack has a complete github setup for the i9100, but it lacks the i777 device.

would this approach work?:

fork fusion_jack's "device_samsung_i9100"

rename to "device_samsung_i777"

make relevant changes to the "device_samsung_i777" repository

point "project:device=..." of the local_manifest.xml to the new project

...but will I be able to "lunch" the i777 if it isn't a part of fusion jack's setup?

I'm trying to avoid forking his entire setup for one different repository, but I have a VERY loose concept of how github works, and of how the build process reaches out after I say "make..."
[AT&T Samsung Galaxy S II SGH-I777] rogersb11:
I'll check into it when I get the chance but I myself only use breakfast and brunch commands. I only use make if I need a clean build because I've added stuff. What you want to try in theory should work tho
[AT&T Samsung Galaxy S II SGH-I777] cyril279:
Whether using breakfast, brunch, or lunch, they all need a target.

What determines the list of available targets?

What do I need to do to make the i777 an available target?

Fusion-Jack's SlimSaber repositories do not include one for the i777, so neither neither breakfast, brunch nor lunch will yeild the i777 as an option IF I am only using Jack's sources. <-- not true at all.

edit:

manual entry works? I'll find out soon enough...
[AT&T Samsung Galaxy S II SGH-I777] rogersb11:
I just created a folder under out and product
[AT&T Samsung Galaxy S II SGH-I777] cyril279:
build environment commands:

breakfast <device> :: looks at the device dependencies to generate a 'local_manifest.xml', and sets the target build parameters for the selected device.

lunch <device> :: sets the target build parameters for the selected device, but with a few more target options available for each listed device. (behaves as though the local_manifest.xml is already established).

brunch <device> :: 'breakfast && mka bacon'

make :: build/compile and create relevant .img files

mka :: 'make' utilizing a scheduler for faster builds.

make -j# :: 'make' using '#' number of threads.

bacon :: zips and signs everything when 'make' or 'mka' is complete.

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

upon starting the terminal session, I usually initialize and set up the build environment first

. build/envsetup.sh && lunch slim_i777-userdebug

then I intentionally avoid breakfast, especially while manually editing the local_manifest.xml

make -j32 bacon

notes:

make -j32 bacon :: builds and zips Slim from scratch in less than one hour, all four cores are maxed for most of the build (q9450 w/8G RAM)

mka bacon :: builds and zips Slim from scratch in over two hours (q9450 w/8G RAM)

---------- Post added at 12:29 PM ---------- Previous post was at 12:28 PM ----------

I'll try it
[AT&T Samsung Galaxy S II SGH-I777] cyril279:
^^- this is not true at all.

all I did was repo-sync Fusion Jack's platform manifest, then tried 'lunch', and had all-kindsa options. Young upstart Cyril should try more BEFORE posting. **retreating to buildbox**

thanks [MENTION=5554845]rogersb11[/MENTION]
[AT&T Samsung Galaxy S II SGH-I777] rogersb11:
Lmao. No problem man. Glad it worked out. Wasn't positive but was fairly sure that it should work. Glad I could help tho for sure. As for github, that just takes time as it is extremely confusing for the most part if you ask me
[AT&T Samsung Galaxy S II SGH-I777] d_j_l:
6/3 build is good.
[AT&T Samsung Galaxy S II SGH-I777] rogersb11:
Build up http://d-h.st/iyK

If running my previous build dirty flash is fine unless otherwise stated
[AT&T Samsung Galaxy S II SGH-I777] d_j_l:
looks like there is a fix for our front camera taking videos

http://review.cyanogenmod.org/#/c/65134/
[AT&T Samsung Galaxy S II SGH-I777] rogersb11:
I'll run off a build when I get home this evening. Been working out since tweaks anyway
[AT&T Samsung Galaxy S II SGH-I777] rogersb11:
Build is running now but MANY changes so had to start fresh meaning longer build time. Probably just start a thread when it's done. I'll update then
[AT&T Samsung Galaxy S II SGH-I777] desteele:
Still 4.4.2?
[AT&T Samsung Galaxy S II SGH-I777] rogersb11:
SHOULD be 4.4.3, SHOULD but no promises as of yet. It was added to my build specs tho and etc etc. If not today I know very soon as I'll add it myself if I need to just no time for all the at the moment and hoping I don't need to anyway

---------- Post added at 10:48 PM ---------- Previous post was at 10:22 PM ----------

Also it appears there has been increased time and emphasis put on ART as I'm building considerably more for that runtime.... Just sayin

---------- Post added at 10:52 PM ---------- Previous post was at 10:48 PM ----------

Also tho it's still building I can confirm it WILL be 4.4.3 ?
[AT&T Samsung Galaxy S II SGH-I777] rogersb11:
Ok guys, head here http://xdaforums.com/showthread.php?p=53196269 if you would for the new build. This is the new thread I'll be posting to from now on. 4.4.3 is up and running as I type this. Get on it already lol
[AT&T Samsung Galaxy S II SGH-I777] desteele:
The times I've enabled ART I've seen negligible if any difference... do you feel like the changes they've made will make ART a viable alternative, and are you already running it?