yashsingh1/xdaforums huggingface dataset:
[AT&T Samsung Galaxy S II SGH-I777] Slavestate:
Yeehaw after fighting with the Mac OS for a week or two I FINALLY got this thing to build..

By completely forgetting OS X and virtual machines and just installing Ubuntu on a seperate partition and doing it straight in real Linux.

ADB even worked perfectly and pulled the proprietary files unlike through VMWare Fusion.. Took like an hour to build yesterday on my first gen Mac Pro quad core 2.0Ghz machine with 4GB of ram.. This took all day in VMWare and NEVER worked, even though I followed the exact same directions I did under the real Ubuntu install. I was about to ditch it and go pure Debian but finally figured out how to get rid of Ubuntu's Unity UI a few days ago and now everything is rocking with good old plain and simple Gnome!

Think its been about a week since I even booted into OS X now but I only really need that when Im recording music so screw you Tim Cook and Apple hahaha. If I only had drivers for my MOTU firewire audio interface I might just go completely Linux altogether..

Anyways a real question for Entropy.. Mr Entropy sir, just to clarify.. If were pulling and syncing against the Team Hacksung repo and building our own rom.. Will these roms have the little fixes youre doing left and right or are we basically just building the 08/03 build over again?? I know youve said all the 'real' work and fixes are going to take some time but just wanted to verify if all the little bits and pieces youre working on are getting sent over to github or not..
[AT&T Samsung Galaxy S II SGH-I777] Entropy512:
If you pull the THS repos, you'll get nearly the latest and greatest. Worst-case you might be missing an unmerged gerrit submission (but I usually link these when I put out a build that includes them.)

So for example if you pull and build you'll have A2DP, but not fixed WPA tethering, as that's a separate gerrit push (and what is on gerrit at the moment is broken - gerrit pushing was broken this morning so I couldn't update.)
[AT&T Samsung Galaxy S II SGH-I777] Slavestate:
Cool deal! Time to learn how to use gerrit now!!
[AT&T Samsung Galaxy S II SGH-I777] Entropy512:
It actually got merged, I was expecting that to take longer.
[AT&T Samsung Galaxy S II SGH-I777] jdahlum:
Spoke with Entropy last night about my builds not applying the galaxys2common overlay settings and we couldn't come up with a solution. For some reason it was not reading the config.xml so I was stuck with the hardware keyboard being enabled after each reboot. I had to merge the config.xml with the i777 one and that resolved the problem but does anyone have any idea why it wouldn't read the common overlays?

Also, I'm getting a FC everytime I try to view the Storage settings. Anyone else experience this?
[AT&T Samsung Galaxy S II SGH-I777] jjbarisax:
I am getting the same thing and have been hunting around the source -

I see this message in my build log. This may be a stretch, but is there a duplicate name?

CyanogenMod/android_device_samsung_galaxys2-common already exists
[AT&T Samsung Galaxy S II SGH-I777] Slavestate:
Ok maybe a stupid question but...

Now that Ive got this thing building in Ubuntu.. How the heck do I mount my GS2 in Linux to copy my roms to the phone???

I see so many mtp-****** files in usr/bin I have no clue what to do with em to get this thing to mount hehe (mtp-connect and mtp-folders keep erroring out so maybe someone can tell me the proper way to do this)..
[AT&T Samsung Galaxy S II SGH-I777] stone_ship:
Exact same problem here. Mind posting the file you created that solved it?
[AT&T Samsung Galaxy S II SGH-I777] jjbarisax:
use adb push
[AT&T Samsung Galaxy S II SGH-I777] jjbarisax:
to add - as in the instructions in the user thread/Team Hacksung - adb push ~/android/system/cm*UNOFFICIAL*.zip to your sdcard - then flash it as you would any other rom - you do not need to copy the individual files over
[AT&T Samsung Galaxy S II SGH-I777] Slavestate:
Derp. I forgot all about adb! Thanks!
[AT&T Samsung Galaxy S II SGH-I777] Entropy512:
No, that's not it - I get it too and I have no issues.

adb
[AT&T Samsung Galaxy S II SGH-I777] jjbarisax:
thanks, for looking. For the settings-storage FC I get this logcat error- I mounted the sdcard in cwm and took out my external sdcard as to not stress media scanning and still got this error. Does anyone have any ideas for this err?

This happenened on a clean install of cm10 UNOFFICIAL 8-16 with a

W/MountService( 8739): getVolumeState(/mnt/sdcard): Unknown volume

E/AndroidRuntime(15057): FATAL EXCEPTION: main

E/AndroidRuntime(15057): java.lang.IllegalArgumentException

E/AndroidRuntime(15057): at android.os.Parcel.readException(Parcel.java:1429)

E/AndroidRuntime(15057): at android.os.Parcel.readException(Parcel.java:1379)
[AT&T Samsung Galaxy S II SGH-I777] Entropy512:
There is no 8/16 build. My last build is 8/13.

If you have a build dated 8/16, it's likely a kang and for whatever reason many people building kangs are getting severely broken builds that aren't properly processing the galaxys2-common stuff.
[AT&T Samsung Galaxy S II SGH-I777] adelvillar:
I'm able to create my own builds from source as per the instructions. No problem there, the only painful part was the first repo sync as it took a long time.

Is there a way to know that the galaxys2-common stuff is being processed before installing the build on the phone?
[AT&T Samsung Galaxy S II SGH-I777] Slavestate:
Mine seems fine so far but I ran into that weird issue of hardware keyboard being the default input device too. So far everything else is good..
[AT&T Samsung Galaxy S II SGH-I777] jdahlum:
If you're running into the problem with the hardware keyboard then you're not getting the galaxys2-common stuff pulled in either. Check and see if your screen turns on when you unplug it from charging. If not, you're not getting those settings.
[AT&T Samsung Galaxy S II SGH-I777] Slavestate:
I just unplugged it like 5 minutes ago and yep the screen doesn't turn on. I've also noticed in Settings>Battery its not able to pull any battery usage data. It shows me the discharging time but the app list is blank. Time to go back to Entropys build I guess!
[AT&T Samsung Galaxy S II SGH-I777] jjbarisax:
same here, I did find a minor issue in the bld log - I did a fresh sync from the repo, clean build using Pier's local_manifest with i777 mods.

I did see this error -

using device-specific extensions in device/samsung/common

unable to load device-specific module; assuming none

device/samsung/common didn't exist, but device/samsung/galaxys2-common did.

I rebuilt with a softlink of common->galaxys2-common, but got the same settings runtime error. I'm just going to enjoy jellybean for the weekend.

other than some settings errors, the rom works well,
[AT&T Samsung Galaxy S II SGH-I777] comingup:
My build keeps stopping after a few seconds and I can't find how to fix it.

make: *** No rule to make target 'bacon' . Stop

I've searched and searched to no avail. Can anyone shed some light on this please?
[AT&T Samsung Galaxy S II SGH-I777] sjwaste:
What command are you using to build? Are you using the teamhacksung build.sh script, or something else?

I've been using the teamhacksung script for CM10 on the i777, but I recall from the CM7/GB days that if you were going to mka bacon, you had to make lunch or brunch first and select your target.
[AT&T Samsung Galaxy S II SGH-I777] Entropy512:
I just use

. build/envsetup.sh && brunch i777
[AT&T Samsung Galaxy S II SGH-I777] ddominator:
By the way, is the hardware keyboard still the default with everybody on new/recent builds? Any idea how to fix it (in code)?
[AT&T Samsung Galaxy S II SGH-I777] jdahlum:
I still haven't figured out a way to get it to include the galaxy2common overlay files in order to disable the hardware keyboard. I've killed my repo several times and resynced and scoured the code to see why it's not including them and honestly I have no idea at this point. I can edit the i777 overlay config.xml to make the hardware keyboard go away but that still doesn't fix the other issues with not including the common overlay files. if anyone has any ideas I would appreciate it. Thanks!
[AT&T Samsung Galaxy S II SGH-I777] ddominator:
Would that be in device_i777 .mk files?
[AT&T Samsung Galaxy S II SGH-I777] jdahlum:
Yes I see them being called in the .mk files but something is causing them not to apply.
[AT&T Samsung Galaxy S II SGH-I777] Entropy512:
No, it is not the default and never was. It is not a problem in any of the builds I have released. It is only a problem in builds that were done improperly. I don't know what mistake people are making, but I can tell you, without a doubt - they are NOT building correctly.

No code fix to any of the device trees is needed. They build fine for all of the developers - some people are getting broken builds and I don't know why. I am unable to reproduce the problem.
[AT&T Samsung Galaxy S II SGH-I777] stone_ship:
Can I ask what version/distro Linux you are using? I've been wondering if this could be it for me--using Ubuntu 11.10.
[AT&T Samsung Galaxy S II SGH-I777] Slavestate:
I'm on 12.04 and have the issues mentioned. My setup was done using a combination of the directions posted here and Googles own instructions for building. Everything was done "by the numbers" as far as I can tell.

Maybe its something in the build.sh? I don't use the commands Entropy does I just ./build.sh i777 and go..
[AT&T Samsung Galaxy S II SGH-I777] jdahlum:
I'm also on 12.04 and followed this guide for prepping the environment:

http://pastebin.com/EPbEtUjC

I also just run "./build.sh i777" and I have the issues with the hardware keyboard as well as a few others. I've tried countless times to start over and rebuild the repo as well as looking all over the build files but everything looks totally fine. I REALLY wish I could get this figured out so I can dive in a little deeper into customizing some things I like.

Gonna try Entropy's way now and see if it changes anything but from looking at the build script I'm not expecting it to. Will report back shortly.....
[AT&T Samsung Galaxy S II SGH-I777] ddominator:
Yeah I switched from build.sh and using brunch i777 but both come up with the hardware keyboard
[AT&T Samsung Galaxy S II SGH-I777] jdahlum:
Alright guys, about to lose my mind but I want to figure this out. I completely rebuilt a laptop with Mint Linux (Ubuntu 12.0.4) and here is exactly what I did:

- Got all the dependencies - sudo apt-get install git-core gnupg flex bison gperf libsdl1.2-dev libesd0-dev libwxgtk2.6-dev squashfs-tools build-essential zip curl pngcrush schedtool g++-multilib lib32z1-dev lib32ncurses5-dev libxml2-utils

- Installed the Java6 SDK

- Downloaded the Android SDK and platform tools - Just did this to get "adb" and then put adb in /usr/bin

- Got the build file system and repo filesystem setup - mkdir -p ~/android/system, curl https://dl-ssl.google.com/dl/googlesource/git-repo/repo > ~/usr/bin/repo, chmod a+x /usr/bin/repo

- Initialized the repository from ~/android/system - repo init -u git://github.com/CyanogenMod/android.git -b jellybean

- synced the repo - repo sync -j16

- created a local_manifest.xml file in ~/android/system/.repo with the following:

<?xml version="1.0" encoding="UTF-8"?>

<manifest>

<project name="teamhacksung/buildscripts" path="buildscripts" remote="github" revision="jellybean">

<copyfile dest="build.sh" src="samsung/build.sh" />

</project>

<project name="teamhacksung/android_device_samsung_i777" path="device/samsung/i777" remote="github" revision="jellybean" />

<project name="teamhacksung/android_device_samsung_galaxys2-common" path="device/samsung/galaxys2-common" remote="github" revision="jellybean" />

<project name="teamhacksung/android_kernel_samsung_smdk4210" path="kernel/samsung/smdk4210" remote="github" revision="jellybean" />

<project name="TheMuppets/proprietary_vendor_samsung" path="vendor/samsung" remote="github" revision="jellybean" />

<project name="CyanogenMod/android_hardware_samsung" path="hardware/samsung" remote="github" revision="jellybean" />

<project name="CyanogenMod/android_packages_apps_SamsungServiceMode" path="packages/apps/SamsungServiceMode" remote="github" revision="ics" />

</manifest>

- Resynced the repo - repo sync -j16

- Pulled the Samsung proprietary files from my phone - ~/android/system/device/samsung/i777/proprietaryfiles.sh

At this point everything had gone well and I was not getting any errors at all. I then started my build with the following command:

./build.sh i777

The build completed and I had flashable zip. Flashed the zip and the galaxy-s2-common files were still not included. What the heck am I doing wrong?!? This was a clean build on a new machine with a completely clean repo and still nothing got included. Entropy, anyone, any ideas? I'd really appreciate it!!
[AT&T Samsung Galaxy S II SGH-I777] jjbarisax:
I have a similar issue and I have followed the same machine and repo/build procedure as you did, but I am on Ubuntu 12.04 64 bit

I unzipped both cm-10*UNOFFICIAL*.zips and diffed the output - I don't know if this is any help but here is the differences between Entropy's 818 cm*.zip and one that I built today from a fresh repo pull - no changes

> = Entropy 818

< = my zip 822

There are a number of files that are not in my 8/22 zip that are in 8/18

294a295,300

> ./system/vendor/lib

> ./system/vendor/lib/libwvm.so

> ./system/vendor/lib/libWVStreamControlAPI_L1.so

> ./system/vendor/lib/drm

> ./system/vendor/lib/drm/libdrmwvmplugin.so

> ./system/vendor/lib/libwvdrm_L1.so

338a345

> ./system/xbin/bash

611d617

< ./system/lib/libsamsungion.so

616a623

> ./system/lib/libsecion.so

703a711

> ./system/lib/libsecril-client-sap.so

1134a1143,1145

> ./system/etc/bash

> ./system/etc/bash/bash_logout

> ./system/etc/bash/bashrc
[AT&T Samsung Galaxy S II SGH-I777] Slavestate:
Bash didn't even get installed?? What happens when you open a terminal emulator??
[AT&T Samsung Galaxy S II SGH-I777] jjbarisax:
Its in the zip -

unzip -l cm-10-20120818-UNOFFICIAL-i777.zip | grep bash

6 2012-08-18 13:26 system/etc/bash/bash_logout

1543 2008-02-28 21:33 system/etc/bash/bashrc

435296 2008-02-28 21:33 system/xbin/bash
[AT&T Samsung Galaxy S II SGH-I777] jdahlum:
I'm telling you, I'm not one to give up but I just can't figure this out. I output the entire build process to a build.log and I don't see anything that looks suspicious. Basically, the i777.mk file calls the galaxys2-common make files which include the overlays and the file copies we need for certain things to work. It's like that whole file is being ignored.

I'm not a developer by any means but I know my way around Linux pretty well, how do we debug the build process? Line by line and figure out where the issue is? I'm having fun with this but it's also frustrating as all hell!! :-p
[AT&T Samsung Galaxy S II SGH-I777] jdahlum:
It looks as if the first nightly has been posted by Entropy today. At least a new build shows up under nightlies on the CyanogenMod download page. Does anyone know if the i777 has now been merged in the CM tree? Do we still need the TeamHacksung entries in our manifests?
[AT&T Samsung Galaxy S II SGH-I777] Entropy512:
11.10 here too - I keep forgetting to update to 12.04...

My guess is - Remove everything under out/target

Then don't use build.sh - it's one of the few difference I can think of. I only use it when building test kernel zips.

As to samsungion vs. secion - that was just changed recently. Actually I need to check to see if a matching change was made to extract-files...

codeworkx said that he forked galaxys2-common - so starting now, you SHOULD be able to build everything without any local_manifest hacks. To transition between repos, you may need to remove all of the current ones:

device/samsung/galaxys2-common
device/samsung/i777
kernel/samsung/smdk4210
.repo/projects/<everything above>.git
[AT&T Samsung Galaxy S II SGH-I777] jdahlum:
Thanks Entropy, just confirmed you do NOT need the local manifest any longer and everything has been moved to the main CM repo. When you brunch i777 it'll grab everything you need and then I had to run ./get-prebuilts under vendor/cm and my build is running now. Will report back once it's complete and let everyone know if it resolved my problems. Thanks again for all of you guys and your efforts!!!
[AT&T Samsung Galaxy S II SGH-I777] zas0006:
I just tried to build after getting rid of the local_manifest.xml and removing the directories you stated.

I used

. build/envsetup.sh && brunch i777

to build and I am getting the following error:

make: *** No rule to make target `out/target/product/i777/obj/SHARED_LIBRARIES/libmediayamahaservice_intermediates/export_includes', needed by `out/target/product/i777/obj/EXECUTABLES/mediaserver_intermediates/import_includes'. Stop.
make: *** Waiting for unfinished jobs....
external/mdnsresponder/mDNSCore/DNSDigest.c: In function 'DNSDigest_SignMessage':
external/mdnsresponder/mDNSCore/DNSDigest.c:1364:2: warning: array subscript is above array bounds [-Warray-bounds]
external/mdnsresponder/mDNSCore/DNSDigest.c:1365:8: warning: array subscript is above array bounds [-Warray-bounds]

Note: before today I had no issues with the hw keyboard or any of that. I was getting builds that matched entropy's with no issue. I have also tried make clean as well with the same results.

Any ideas as to what is going on?
[AT&T Samsung Galaxy S II SGH-I777] Entropy512:
Looks like it might be a problem with vendor/

I had that error the first time I tried to build JB, I forget how I resolved it.
[AT&T Samsung Galaxy S II SGH-I777] zas0006:
I will just blast everything and do a fresh repo sync tonight. I will report back if I run into any more issues.
[AT&T Samsung Galaxy S II SGH-I777] ddominator:
What is in your local_manifest.xml? I think the problem has to do with proprietary_vendor_samsung. I'm going to try using Team Hacksung's repo instead of TheMuppets.

EDIT: Using the Team Hacksung repo for proprietary_vendor_samsung makes stuff work! No hardware keyboard on boot.
[AT&T Samsung Galaxy S II SGH-I777] zas0006:
So I blasted everything in ~/android/system as well as ~/bin and set everything again from scratch. After I synced the repo and ran my first build it failed because it couldn't make ROM manager. I ran the get-prebuilts script and then retried the build and it completed fine but now I am getting the hardware keyboard when i first boot and all that jazz. What the deuce is going wrong?
[AT&T Samsung Galaxy S II SGH-I777] ddominator:
Well my post above yours said I used the TeamHacksung repo for the proprietary_vendor_samsung and I didn't get the hardware keyboard. Are you using TheMuppets repo?
[AT&T Samsung Galaxy S II SGH-I777] zas0006:
I am not using a custom local_manifest at all since it shouldn't be needed anymore per Entropy's previous posts. I can get the build to work if I hack it but i am wanting to know why should I have to do that if the changes should exist in mainline?

Is there a problem with what was forked to get the changes in mainline?
[AT&T Samsung Galaxy S II SGH-I777] jdahlum:
Do you mind posting your local manifest? Are you just adding the proprietary_vendor_samsung to your manifest or are you adding the other Team Hacksung stuff too? Thanks man!!
[AT&T Samsung Galaxy S II SGH-I777] Entropy512:
I'm using muppets - THS repo is pretty ancient right now.
[AT&T Samsung Galaxy S II SGH-I777] jdahlum:
Is there anything to the fact that vendor/samsung/galaxys2-common/common-vendor.mk references overlays in vendor/galaxys2-common/overlay which doesn't exist? The overlays are in device/samsung/galaxys2-common. The same applies for vendor/samsung/i777/i777-vendor.mk, it references a non-existent overlay directory.

I know the makefiles in device folders call the proper overlays so I don't know if this is it but wanted to check.
[AT&T Samsung Galaxy S II SGH-I777] jdahlum:
I don't know if what I did was the right thing but editing the make files I listed above to point to the correct overlays seems to have resolved my problems. All settings got compiled this time and everything is working perfect! No hardware keyboard, no storage FC's, nothing!!
[AT&T Samsung Galaxy S II SGH-I777] ddominator:
I just added the proprietary_vendor_samsung

Hmmm... I shall try then if that will disable hardware keyboard.
[AT&T Samsung Galaxy S II SGH-I777] zas0006:
This worked for me as well.

Entropy,

Is this something that needs to be submitted as a permanent fix or is this a fluke?
[AT&T Samsung Galaxy S II SGH-I777] XGX5309:
With all these Exynos devices launching with JB today, we ought to get a fixed HWComposer soon... correct?
[AT&T Samsung Galaxy S II SGH-I777] Nick281051:
You mean the galaxy note 2 and galaxy camera that were announced and not launched yet? The ones that have quad core processors?

Sent from team Pirate! Using Tapatalk 2
[AT&T Samsung Galaxy S II SGH-I777] robmoney215:
wrong thread...my bad
[AT&T Samsung Galaxy S II SGH-I777] XGX5309:
Exynos 4412 is Exynos 4210/12, just with two more cores, a different audio DAC and a clock bump on the GPU.

But yea, those are the ones I'm talking about.
[AT&T Samsung Galaxy S II SGH-I777] Nick281051:
Either way they haven't even been launched yet. Maybe if the international s3 gets it soon, like Samsung says it will (and we know how reliable they are with that stuff)

Sent from team Pirate! Using Tapatalk 2
[AT&T Samsung Galaxy S II SGH-I777] Entropy512:
There are significant architectural differences in the software between these, and also the 4x12 devices have a newer FIMC subsystem if I recall correctly.

Stuff for I9300/N80xx/etc usually doesn't benefit I9100/I777/N7000
[AT&T Samsung Galaxy S II SGH-I777] Entropy512:
It seems to be a fluke since none of the CM developers are having any issues.
[AT&T Samsung Galaxy S II SGH-I777] XGX5309:
Well, that's interesting. I didn't know that.
[AT&T Samsung Galaxy S II SGH-I777] Fusion777:
I run two CM10 kangs, my personal experimental one (keep to myself) and the one I post here.

The personal one was NOT updating the https://github.com/CyanogenMod/android_device_samsung_galaxys2-common sourced repository properly. It was very out of date. I checked the directory and the git remotes looked fine. Repo sync pretty much ignored it.

However when i did a proper git fetch it updated it. Strange. We'll see how it fares from here on out.

The one I post nightly does not exhibit this problem.
[AT&T Samsung Galaxy S II SGH-I777] XGX5309:
Yep. I'm noticing this as well.

I don't usually build, except on days where I have nothing to do for an hour...lol. I usually just grab one of your builds.
[AT&T Samsung Galaxy S II SGH-I777] Entropy512:
Until it got forked back from teamhacksung, I think that had no valid JB stuff. Also, when transitioning from THS to CM, it was best to:

Manually remove device/samsung/galaxys2-common and i777

Manually remove .repo/projects/device/samsung/galaxys2-common.git and i777.git

Remove it from the local manifest

Resync from scratch
[AT&T Samsung Galaxy S II SGH-I777] ddominator:
Hmmm the main repo at CyanogenMod now has the keyboard bug. Previously it didn't. Anyone else having the same problem?
[AT&T Samsung Galaxy S II SGH-I777] jjbarisax:
I just ran a repo sync and rebuilt, didn't have the keyboard problem pulling in 120912. You may want to check that these values are not vendor/samsung/*

i777-vendor.mk DEVICE_PACKAGE_OVERLAYS += device/samsung/i777/overlay

common-vendor.mk DEVICE_PACKAGE_OVERLAYS := device/samsung/galaxys2-common/overlay
[AT&T Samsung Galaxy S II SGH-I777] shri_chanakya:
I too ran into this bug, keyboard is defaulting to hardware and hence not showing the keyboard.

I checked the values in i777-vendor.mk and common-vendor.mk and they match to what you have given here. any suggestion how to resolve this?

---------- Post added at 04:18 PM ---------- Previous post was at 03:22 PM ----------

As of now have cleaned up everything and restarting from scratch even getting new "repo" file from google. would update if I still get the annoying hardware button issue.

Also I am not creating local manifest as it seems it is no longer required.
[AT&T Samsung Galaxy S II SGH-I777] ddominator:
Thanks that did the trick.