yashsingh1/xdaforums huggingface dataset:
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] calikevin:
Can anyone help me out here, this is hopefully a really simple fix but I just can't seem to figure it out.

I'm trying to build slimbean for my device, but it's currently unsupported.. What do I need to do in order to build slim bean using my device files? I can get it to show up in the lunch menu but here's what happens when I run it-

kevin@KevWebTech1558z:~/Documents/slimbean-src$ lunch slim_holiday-userdebug
Trying dependencies-only mode on a non-existing device tree?

============================================
PLATFORM_VERSION_CODENAME=UNOFFICIAL
PLATFORM_VERSION=4.3
SLIM_VERSION=Slim-4.3.build.1-UNOFFICIAL-20130917-0533
TARGET_PRODUCT=slim_holiday
TARGET_BUILD_VARIANT=userdebug
TARGET_BUILD_TYPE=release
TARGET_BUILD_APPS=
TARGET_ARCH=arm
TARGET_ARCH_VARIANT=armv7-a-neon
TARGET_GCC_VERSION=4.7
TARGET_USE_O3=
TARGET_CPU_VARIANT=scorpion
HOST_ARCH=x86
HOST_OS=linux
HOST_OS_EXTRA=Linux-3.8.0-28-generic-x86_64-with-Zorin-7-raring
HOST_BUILD_TYPE=release
BUILD_ID=JSS15Q
OUT_DIR=/home/kevin/Documents/slimbean-src/out
============================================

Any help is greatly appreciated
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] ktempleton:
That's setting up to build the error would be after that
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] BMP7777:
- This doesn't typically constitute an error. Let it run and see what happens next....

Kinda what I was thinking.....
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] calikevin:
Yea my bad, I was really tired last night when I posted that and didn't even try running bacon. When I do try to build it tells me it can't find the kernel source and it stops the building before it completes.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] BMP7777:
Whats your local_manifest look like?
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] calikevin:
I actually don't have anything in local manifest, I never made an XML with sources in it. This is my first attempt at building from source, hence missing steps haha
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] BMP7777:
---------- Post added at 04:31 PM ---------- Previous post was at 04:26 PM ----------

Research the correct device specific files and make a local_manifest. You should get much further then. You could ask around your forum too, it may save time.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] calikevin:
What device specific files do I need to locate, kernel is one right? And to make a local manifest I'll need to add the git URL pointing to the device-specific kernel and other files to an XML? Can you give me an example of what the local manifest should look like perhaps? Thank you for all the help!
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] car vs driver:
An example local manifest is in the first post of this thread. It contains everything you need, you just have to make sure you replace the device specific bits with your device.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] titanic_fanatic:
Hey guys, so I have successfully built and an running cm10.1. I had it booting before, but my display was black. I hit that fixed by using the legacy display drivers. Now I need to work out some bugs, and the biggest one is no audio. I tried using the legacy audio drivers and that at least let's me get audio to play through bt, but it won't play through the speakers.

I have an sgh-i757m, closest relative is the skyrocket. So my board is an msm8660 with adreno 220.

Can someone point me in the right direction, maybe to a commit that would help work out the audio issues.

Also, my video seems to not fully refresh all the time, like the refresh rate is wrong or the redraw just isn't happening. What could cause this? Is there a commit for a similar issue somewhere.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] m4570d0n:
I can't imagine why you would have to revert to using the legacy display or legacy audio sources. Your phone is essentially the same as ours but newer, and come with an upgraded 4.65in (1280x720 px) display rather than our 4.5in (800x480 px) display. AFAIK, the audio hardware/firmware is the same for both devices.

What's your local manifest look like?
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] rpr69:
Ah ha. My build failed last night, now I know why.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] titanic_fanatic:
I thought the same, but could not get anything to show up on my display until I switched over to display-legacy and media-legacy. It's probably something to do with my adreno drivers. I have not updated them because when I did update them from TheMuppets/proprietary_vendor_samsung/skyrocket I get a bootloop. If I used my old adreno drivers, I would get no display during boot, but then would get a flickering display at the welcome screen. I did however, have audio at that time.

Using my old adreno drivers and the legacy branches, I can get it to a usable state.

My local_manifest.xml look like this:

<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="SlimRoms/device_samsung_msm8660-common" path="device/samsung/msm8660-common" remote="github" revision="jb4.2" />
<project name="SlimRoms/device_samsung_celox-common" path="device/samsung/celox-common" remote="github" revision="jb4.2" />
<project name="SlimRoms/device_samsung_qcom-common" path="device/samsung/qcom-common" remote="github" revision="jb4.2" />
<project name="SlimRoms/hardware_qcom_display-caf" path="hardware/qcom/display-caf" remote="github" revision="jb4.2" />
<project name="SlimRoms/hardware_qcom_audio-caf" path="hardware/qcom/audio-caf" remote="github" revision="jb4.2" />
<project name="SlimRoms/device_samsung_skyrocket" path="device/samsung/skyrocket" remote="github" revision="jb4.2" />
<project name="titanic-fanatic/android_kernel_samsung_msm8660-common" path="kernel/samsung/msm8660-common" remote="github" revision="cm-10.1" />
<project name="titanic-fanatic/android_device_samsung_celoxhd" path="device/samsung/celoxhd" remote="github" revision="cm-10.1" />
<project name="titanic-fanatic/android_vendor_samsung_celoxhd" path="vendor/samsung/celoxhd" remote="github" revision="cm-10.1" />
</manifest>

I was using the -caf branch, but it didn't work no matter what I tried. Kept getting a bootloop if I used the new adreno drivers, and no display if I used the old ones. It wasn't until I built using display-legacy and media-legacy that my display started working.

Thank you both for sharing the patches that you use. I'm going to review each and every one and try re-building on the caf branch with these patches.

One other question though, in regards to the adreno drivers, it's just simply replacing the old ones right (drag & drop)? That's what I've done anyways. I will try again with the new adreno drivers as that would most definitely be the best option if I can achieve that.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] BMP7777:
Been building Beanstalk with no problems lately, so I thought I'd get squirrely and try to build with a custom kernel made by a guy in the m7spr forum that has worked well with the BS. Its forked directly from CM 10.2 so I figured it was as close as it was gonna get. But, I came up with this:

Symlink: /home/bmp7777/beanstalk/out/target/product/m7spr/recovery/root/sbin/setprop -> recovery
Symlink: /home/bmp7777/beanstalk/out/target/product/m7spr/recovery/root/sbin/setserial -> busybox
Symlink: /home/bmp7777/beanstalk/out/target/product/m7spr/recovery/root/sbin/setsid -> busybox
Symlink: /home/bmp7777/beanstalk/out/target/product/m7spr/recovery/root/sbin/setup_adbd -> recovery
LD security/selinux/built-in.o
Symlink: /home/bmp7777/beanstalk/out/target/product/m7spr/recovery/root/sbin/sh -> busybox
LD security/built-in.o
Symlink: /home/bmp7777/beanstalk/out/target/product/m7spr/recovery/root/sbin/sha1sum -> busybox
Symlink: /home/bmp7777/beanstalk/out/target/product/m7spr/recovery/root/sbin/sha256sum -> busybox
Symlink: /home/bmp7777/beanstalk/out/target/product/m7spr/recovery/root/sbin/sha512sum -> busybox
Symlink: /home/bmp7777/beanstalk/out/target/product/m7spr/recovery/root/sbin/sleep -> busybox
make[1]: *** [sub-make] Error 2
make[1]: Leaving directory `/home/bmp7777/beanstalk/kernel/htc/m7'
make: *** [TARGET_KERNEL_BINARIES] Error 2
make: *** Waiting for unfinished jobs....
bmp7777@bmp7777-HP-Pavilion-dv7-Notebook-PC:~/beanstalk$

Looked as far up as I was able to see if there was an earlier error, but I didn't see one. Does anyone have an idea about this? Obviously, the kernel didn't go in seamlessly, but I don't see it pointing in any specific direction. But, what do I know....
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] calikevin:
We did build slim from source using our own working CM 10.1 base, then editing some lines and renaming some files but the main source build was done by another developer, not by me... I just did a 'lazy port' using a Sensation version that booted on our device to get the ball rolling but it had major issues. Our device is not officially supported by SlimROMs either, so when we did get the source built Slim to boot it still had a few issues like camera recording and video playback. I suppose if you could all help me figure that out so it's at least daily driver worthy I'd be a happy camper. I was trying to get the newest SlimROM to boot on our device but I'm sure it will happen eventually.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] prbassplayer:
I don't know if msm8660 specifics or caf report for 4.2.2 have changed much but I'd make sure nothing important has happened and might consider using cm's as base. Slims repo stopped being updated when we started working on 4.3
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] titanic_fanatic:
Hey guys, so I'm now definitely on the caf branch. I reworked my vendor blobs (pulled all new drivers from our latest stock rom from Samsung), then I replaced all the adreno drivers with the new updated ones.

Now I'm back at square 1, I have boot, but no boot animation and the display is frozen when it boots to the welcome screen. I was able to pull a logcat and found this:

This was littered throughout the logcat. I have been searching google for a fix to this, but have not found anything useful. It's obviously related to the new graphics subsystem, but I don't really know what the problem is. The adreno drivers were taken from TheMuppets/proprietary_vendor_samsung/adrenoblobs4.2

What would be the next step in resolving this issue, I don't think I want to go back to legacy as I don't think I should need to, but how to fix this EGL issue?

EDIT:

Also this error appears:

I think this is related to kgsl.... How do I update that?

EDIT 2:

So I found this in my defconfig (it doesn't even exist in the skyrocket defconfig):

Not sure if this is the issue, but it relates to old kgsl compatibility, so I'm assuming it's partially to blame for the errors I'm getting. I'm re-building with this disabled.

EDIT 3:

So the CONFIG_KGSL_COMPAT did not fix my display issue. What could be the issue with the display drivers???
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] patch_Adams:
Can you guys help me with this here?? I am getting a rotation issue here:

I don't know where or how to fix this, I know very little java yet....

09-20 13:23:31.248: E/WindowManager(7071): Activity o.덁 has leaked window com.android.internal.policy.impl.PhoneWindow$Decor View{42270830 V.E..... R......D 0,0-1280,800} that was originally added here

09-20 13:23:31.248: E/WindowManager(7071): android.view.WindowLeaked: Activity o.덁 has leaked window com.android.internal.policy.impl.PhoneWindow$Decor View{42270830 V.E..... R......D 0,0-1280,800} that was originally added here

09-20 13:23:31.248: E/WindowManager(7071): at android.view.ViewRootImpl.<init>(ViewRootImpl.java :345)

09-20 13:23:31.248: E/WindowManager(7071): at android.view.WindowManagerGlobal.addView(WindowMan agerGlobal.java:239)

09-20 13:23:31.248: E/WindowManager(7071): at android.view.WindowManagerImpl.addView(WindowManag erImpl.java:69)

09-20 13:23:31.248: E/WindowManager(7071): at android.app.Dialog.show(Dialog.java:281)

09-20 13:23:31.248: E/WindowManager(7071): at o.ǳ.onClick(Source:804)

09-20 13:23:31.248: E/WindowManager(7071): at android.view.View.performClick(View.java:4247)

09-20 13:23:31.248: E/WindowManager(7071): at android.view.View$PerformClick.run(View.java:17728 )

09-20 13:23:31.248: E/WindowManager(7071): at android.os.Handler.handleCallback(Handler.java:730 )

09-20 13:23:31.248: E/WindowManager(7071): at android.os.Handler.dispatchMessage(Handler.java:92 )

09-20 13:23:31.248: E/WindowManager(7071): at android.os.Looper.loop(Looper.java:137)

09-20 13:23:31.248: E/WindowManager(7071): at android.app.ActivityThread.main(ActivityThread.jav a:5288)

09-20 13:23:31.248: E/WindowManager(7071): at java.lang.reflect.Method.invokeNative(Native Method)

09-20 13:23:31.248: E/WindowManager(7071): at java.lang.reflect.Method.invoke(Method.java:525)

09-20 13:23:31.248: E/WindowManager(7071): at com.android.internal.os.ZygoteInit$MethodAndArgsCa ller.run(ZygoteInit.java:743)

09-20 13:23:31.248: E/WindowManager(7071): at com.android.internal.os.ZygoteInit.main(ZygoteInit .java:559)

09-20 13:23:31.248: E/WindowManager(7071): at dalvik.system.NativeStart.main(Native Method)

I deleted my frameworks folder and did a resync thinking it would help, but still the error persists....
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] m4570d0n:
I believe TheMuppets/proprietary_vendor_samsung/adrenoblobs4.2 was for or from the Mako (Nexus 4). It still isn't clear to me if you have tried this yet, but what happens when you build straight CM using CM's manifest and using this for your local manifest?:

<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="CyanogenMod/device_samsung_msm8660-common" path="device/samsung/msm8660-common" remote="github" revision="cm-10.2" />
<project name="CyanogenMod/device_samsung_celox-common" path="device/samsung/celox-common" remote="github" revision="cm-10.2" />
<project name="CyanogenMod/device_samsung_qcom-common" path="device/samsung/qcom-common" remote="github" revision="cm-10.2" />
<project name="CyanogenMod/device_samsung_skyrocket" path="device/samsung/skyrocket" remote="github" revision="cm-10.2" />
<project name="CyanogenMod/android_kernel_samsung_msm8660-common" path="kernel/samsung/msm8660-common" remote="github" revision="cm-10.2" />
<project name="TheMuppets/proprietary_vendor_samsung" path="vendor/samsung/celoxhd" remote="github" revision="cm-10.2" />
<project name="titanic-fanatic/android_device_samsung_celoxhd" path="device/samsung/celoxhd" remote="github" revision="cm-10.2" />
</manifest>

I also noticed in the local manifest you posted, you were using your own kernel source and using the cm-10.1 branch. If that was not a typo, that's probably not a good thing.

Also, I would get on IRC and talk to teamchpsticks
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] prbassplayer:
I believe it's adreno blobs from mako used for d2 devices.

I'd recommend pulling the blobs from your stock rom (I'd imagine 4.1.2?) and using that.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] wantowan2:
Hey guys, is there any reason why sk8's touch recov can't be updated? I'm failing miserably here lol

https://bitbucket.org/wantowan2/touch_recovery_cm10.2/src

.....I know, I know. I tend to ask loaded questions...lol
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] m4570d0n:
Yes. The touch code he is using is not open source. He got a lot of it from PhillZ who has stated he will never make it open source because it would have a lot of the features only available in the paid version of CWM touch. The repo has tons of code that refers to source directories that are locally on sk8's computer and but not in his repo on github.

for example:

https://github.com/sk8erwitskil/and...28f7431eeb8e8b1e262f2672924d8a138acefc#L1L383
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] soccerfan6789:
Did anyone ever experience or know anyone who had SD card mounting issues on 4.3?
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] wantowan2:
Thanks. Wont waste my time anymore....lol Wonder how sk8 got his hands on it then? Maybe we were just a testing pool.

Have any ideas about these 2 probs I have?

I'm getting these red borders around the screen like that developers setting. I thought that maybe it was turned on by default or something because it happened at first boot. I think that it is a legacy function now because that whole part of dev settings has changed.

Also, I am having DATA/WIFI issues. Yes, I have the correct radio...etc. Wifi shows null and the icons only show grey. Never flash blue at all. Anybody else?
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] ktempleton:
Change the build type from eng to user debug to get rid of the red border it's in the vendor setup sh not sure about the Wi-Fi

You can edit the build prop to change it to user debug you don't have to run another build
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] Kiltnar:
The radio icons not turning blue are because its not reaching Google servers. (Correct me if I'm wrong.) Thought I remember setting that on the forum somewhere. Also happens if you don't install gapps.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] vincom:
you need to install/reinstall/ gapps to connect to google services then login to your google account to get the blue icons
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] zun321:
problem in compiling kernel

Guyz i m having this error-------android/kernel/toolchains/arm-eabi/bin-gcc: No such file or directory

Is your PATH set correctly?

ANY HELP!!!!!
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] BMP7777:
More information.......what ROM are you building? Where is the error code? Are you trying to build with toolchains or is this embedded? Just from this, I would say dump your build directory and start fresh, with no additions. As a novice builder myself, I always say that you need to build a plain, no extras version of whatever ROM it is BEFORE you attempt additions. You will come across many issues in the quest for a new ROM, and knowing for sure that 'xzy' builds on it's own is crucial. Otherwise you'll never have any idea what you did to make a successful (or unsuccessful) build. Whenever I am having build issues, I check my environment first. Does CM10.2 build without issues? <yes> - check a vanilla version of your ongoing build. <no> - research fixing your build environment. Does your vanilla build compile and boot? <yes> - you know at this point that your additions are borking the build somewhere. <no> - you know your build has issues that need to be fixed before a successful compilation will take place. I consider this good info for anyone new to this process. Regardless of your coding chops, if you have no idea where to even look for your build issues, you may as well buy an iPhone.......
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] prbassplayer:
Means you have tool chain path set incorrectly. First off error should say

android/kernel/toolchains/arm-eabi/bin/arm-eabi-gcc: No such file or directory

This is probably for kernel I assume so it should look like (when exporting or in makefile)

/home/user*/android/toolchains/arm-eabi/bin/arm-eabi-

If rom same difference but pointing at prebuilt / prebuilts folder.

Edit: BMP7777 was faster than me lol
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] BMP7777:
Maybe, but your information was better.......:highfive:
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] wantowan2:
That's messed up. I have never needed the 'userdebug' with beanstalk before... compiling now....(fingers crossed)

As for the icons and not reaching google.... why would this be that way from first boot. I've probably tested 100 builds in the last few months, I wonder why now all of a sudden?

Ex: I always skip by google reg on first boot and don't reg until I have restored my apps. I'll either add in settings/sync or when I open playstore. I have always had full wifi/data capability... It's not just the icon color. gmail will sync but I can't get to a website in browser. If wifi is on at all, if I toggle it, it shows up 'null' in wifi settings.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] BMP7777:
My Latest build for the One has had reports of the same thing.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] patch_Adams:
A quick Google search and I'm right back here to this great forum. I had my local pulling my kernel into /lge/kernel instead of just /kernel....doh....You guys here are great!!
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] zun321:
gettin the same errors guyz!! :(

guyz my toolchain is located here-arm-eabi-4.7 in the screenshot below!!! i have attatched the attatchment!!1

so with my knowledge i guess the code would be- export CROSS_COMPILE=~/home/zunaid/android/kernel/toolchains/arm-eabi-4.7/bin- right???

but i m getting the same error!! :(
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] zun321:
Guyz here is the screenshot of the error !!!
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] herna:
I got the same problem and it was because environment and toolchain. I fixed setting up environment again for if something failed, and also used gcc 4.6 and worked. Idk if it worked because the environment or the other but worked.

Enviado desde mi GT-N7000 usando Tapatalk 4
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] prbassplayer:
The post you quoted has the answer mate....
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] wantowan2:
@ktempleton, That fixed me right up. switching from 'eng' to 'userdebug' in 'vendorsetup.sh' fixed me right up. for the red border and wifi/data issues.

Also, for BeanStalk, there was an added entry in the system prop in device folder. It's an added permission for tcp stack dump. I had to delete that too.