yashsingh1/xdaforums huggingface dataset:
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] m4570d0n:
C'mon rpr, I know you've been hanging around in this playground long enough to figure that out.

Remove this line for the CM kernel from you local manifest (roomservice.xml) or comment it out by adding a "<!--" at the beginning of the line and "-->" at the end:

<project name="CyanogenMod/android_kernel_samsung_msm8660-common" path="kernel/samsung/msm8660-common" remote="github" revision="cm-11.0" />

You could also just change that line to point to CvD's kernel instead. Either way, you'll want to add a remote name for the Moretz source. Your resulting local manifest might look something like this:

<?xml version="1.0" encoding="UTF-8"?>
<manifest>
[COLOR=Red] <remote name="bitbucket"
fetch="ssh://git@bitbucket.org" />
[/COLOR]
<project name="CyanogenMod/android_device_samsung_celox-common" path="device/samsung/celox-common" remote="github" revision="cm-11.0" />
<project name="CyanogenMod/android_device_samsung_msm8660-common" path="device/samsung/msm8660-common" remote="github" revision="cm-11.0" />
<project name="CyanogenMod/android_device_samsung_qcom-common" path="device/samsung/qcom-common" remote="github" revision="cm-11.0" />
<project name="CyanogenMod/android_device_samsung_skyrocket" path="device/samsung/skyrocket" remote="github" revision="cm-11.0" />
<project name="TheMuppets/proprietary_vendor_samsung" path="vendor/samsung" remote="github" revision="cm-11.0" />
[COLOR=Red] <project name="carvsdriver/android_kernel_samsung_msm8660-common" path="kernel/samsung/msm8660-common" remote="bitbucket" revision="moretz" />
<project name="carvsdriver/vendor_moretz-kernel" path="vendor/moretz-kernel" remote="bitbucket" revision="master" />[/COLOR]
</manifest>

Then remove the kernel from the cm.dependencies file in /device/samsung/skyrocket:

https://github.com/CyanogenMod/android_device_samsung_skyrocket/blob/cm-11.0/cm.dependencies

[
{
"repository": "android_device_samsung_qcom-common",
"target_path": "device/samsung/qcom-common"
},
{
"repository": "android_device_samsung_msm8660-common",
"target_path": "device/samsung/msm8660-common"
},
{
"repository": "android_device_samsung_celox-common",
"target_path": "device/samsung/celox-common"
},
[COLOR=Red]{[/COLOR]
[COLOR=Red] "repository": "android_kernel_samsung_msm8660-common",[/COLOR]
[COLOR=Red] "target_path": "kernel/samsung/msm8660-common"[/COLOR]
[COLOR=Red] }[/COLOR]
]

Note: You can remove lines #14-17 but make sure you also remove the comma at the end of line #13 as well, or just delete lines #13-16.

If you're building for a different ROM, the dependencies file may be located in the vendor repo for that ROM instead of (or in addition to) the device repo. In PAC-man for example, it's also located at /vendor/pac/dependencies/skyrocket.dependencies:

https://github.com/PAC-man/android_vendor_pac/blob/pac-4.4/dependencies/skyrocket.dependencies
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] rpr69:
You are, of course, correct. I'm not actually in a position to look at it right now, and seeing the answer, it's pretty obvious. My apologies, should have been able to nail that one down. I do know I had tried it before on CM10.2 and couldn't make it work, but I obviously had a reading comprehension issue at the time. Thanks again, I should have looked a little more closely...
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] kennkanniff:
Next, you'll need to update your device/samsung/skyrocket/cm.mk file with this:

$(call inherit-product, carvsdriver/android_kernel_samsung_msm8660-common/AndroidKernel.mk)

EDIT: Chek next post.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] car vs driver:
Close! If you follow the guide exactly on including the init.d scripts, then you will actually add the following to your device/samsung/skyrocket/cm.mk file. Anywhere near the top should be fine.

$(call inherit-product, vendor/moretz-kernel/moretz-kernel.mk)

The above is the same whether or not you are using Moretz or Marla branches in the kernel source.

I've done a LOT of testing on the pletorha of init.d scripts that have been passed around. 99% of them are placebo crap, and some are even potentially harmful. The ones I include are very simple, and they actually work.

Remount - simply gives me a clean mount on volumes to run the remaining scripts.

Zipalign - self explanatory. This will zipalign your APK files at boot. But it's smart enough to track which ones it has aligned in a database, so it only updates newly installed ones at boot.

Vacuum - This is a quick and dirty way to defragment sqlite databases. Most apps and many things in the system use sqlite databases, so the script keeps them nice and clean for best performance.

GPU Control - that's specifically for my GPU frequency control code in the kernel.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] kennkanniff:
Thanks! Are you sure about that line bescause when I tried to compile with it I get this error:

including vendor/cm/vendorsetup.sh
build/core/product_config.mk:238: *** _nic.PRODUCTS.[[device/samsung/hercules/cm.mk]]: "vendor/moretz-kernel/moretz-kernel.mk" does not exist. Stop.
Device hercules not found. Attempting to retrieve device repository from CyanogenMod Github (http://github.com/CyanogenMod).

With my line it does build, anyway to check if the init changes made it into the rom ?

Notice that you have changed kernel path in the manifests, that is where I based my line on.

Thank you for your deeper explanation.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] car vs driver:
When you repo sync the scripts, vendor-moretz_kernel - you should use this:

<remote name="bitbucket"
fetch="ssh://git@bitbucket.org" />
<project name="carvsdriver/vendor_moretz-kernel"
path="vendor/moretz-kernel"
remote="bitbucket"
revision="master">

You'll note that it puts the project files in the directory: vendor/moretz-kernel

It is in that directory that moretz-kernel.mk lives. All this file does is copy the init.d scripts to the correct location for when it gets packaged up into the zip file.

Here's the code:

# Moretz kernel helper scripts

# init.d support
PRODUCT_COPY_FILES += \
vendor/moretz-kernel/scripts/etc/init.d/00banner:system/etc/init.d/00banner \
vendor/moretz-kernel/scripts/etc/init.d/01remount:system/etc/init.d/01remount \
vendor/moretz-kernel/scripts/etc/init.d/02gpu_control:system/etc/init.d/02gpu_control \
vendor/moretz-kernel/scripts/etc/init.d/07vaccum_sqlite:system/etc/init.d/07vaccum_sqlite \
vendor/moretz-kernel/scripts/etc/init.d/10zipalign:system/etc/init.d/10zipalign \
vendor/moretz-kernel/scripts/etc/init.d/99complete:system/etc/init.d/99complete \

If you are getting errors that the file doesn't exist, you likely synced it to a different location ...

Remember that you are syncing TWO project repos when using my kernel. Onc is the kernel itself which goes to the standard CM kernel path (kernel/samsung/msm8660-common), the second is the one noted above which goes in a different location (vendor/moretz-kernel).
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] kennkanniff:
That explains alot. The manifest you can find at the link of your post about cm11 support shows a diffrent manifest! ;)

Thanks.

EDIT: I get it now, I also should have followed the cm10 part, sorry for waisting your time and thanks again!
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] car vs driver:
No worries man.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] rpr69:
What am I missing here?

git ls-remote git@bitbucket.org:carvsdriver/vendor_moretz-kernel.git
Permission denied (publickey).
fatal: The remote end hung up unexpectedly

I have the bitbucket public key in my known_hosts file, everything I've found says to add my public key to bitbucket, but I'm not sure how to do that? Or am I having a reading comprehension moment again?
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] desalesouche:
hi can you help me ...

4.2.2 is booting but no camera....

http://pastebin.com/HLGxfz2j

E/AndroidRuntime( 2576): FATAL EXCEPTION: Camera Handler ThreadE/AndroidRuntime( 2576): Process: com.android.camera2, PID: 2576E/AndroidRuntime( 2576): java.lang.RuntimeException: setParameters failedE/AndroidRuntime( 2576): * * * *at android.hardware.Camera.native_setParameters(Native Method)E/AndroidRuntime( 2576): * * * *at android.hardware.Camera.setParameters(Camera.java:1695)E/AndroidRuntime( 2576): * * * *at com.android.camera.AndroidCameraManagerImpl$CameraHandler.handleMessage(AndroidCameraManagerImpl.java:298)E/AndroidRuntime( 2576): * * * *at android.os.Handler.dispatchMessage(Handler.java:102)E/AndroidRuntime( 2576): * * * *at android.os.Looper.loop(Looper.java:136)E/AndroidRuntime( 2576): * * * *at android.os.HandlerThread.run(HandlerThread.java:61)

native parameters don't match the parameters the camera is expecting.

does someone know how i can try to fix?

thank you
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] kennkanniff:
Use http.

<remote name="bitbucket"
fetch="http://git@bitbucket.org" />

A simple search would have told you the same. ;)
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] rpr69:
No, actually, it didn't, because I spent over an hour searching, and nothing pointed me in that direction, especially when both cvd and m4570d0n said to use ssh. When I change it to http it does sync, but the problem then is it pops up an 'Enter password' dialog, if I just click 'OK' it continues and syncs the two repos perfectly fine, but I have to hit OK twice. Does anyone know how to bypass that? It's not conducive to automated building...

My build did finish, and seems to work ok with Marla, I might try Moretz and see how it goes. edit: Moretz built and working as well, I think I like the extra tweaks available in Moretz. We'll see...

Thanks for the pointer!
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] desalesouche:
hi guys

i need your help to fix sd card problem.

the camera apk can't find sd card...

https://plus.google.com/u/0/photos/a...63100629409455

here is all information about init.rc /fstab etc etc...all these files related with sd card...

ramdisk/fstab.huawei = http://pastebin.com/3XDGuaFA

ramdisk/init.huawei.rc = http://pastebin.com/44UKSFAT

in device/huawei/msm7x30/common.mk = http://pastebin.com/rXzgi1NF

and in Storage_list.xml = http://pastebin.com/6G1nrcnu

i would be very happy to get it working....

if anyone can help...

thanks a lot
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] Rittik:
I finally made my first kernel zimage. I need to make a boot.img or a samsung odin flashable kernel. Any idea how to do it? Thanks!
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] rpr69:
I find it hard to believe I am the only person seeing the issue of a password prompt when I do a repo sync. Am I really the only one?
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] car vs driver:
Try this ...

http://qosys.info/485/bitbucket-git-prompt-for-password
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] m4570d0n:
I get the same thing using the command you used here, but I'm not sure what you're trying to do here with git ls-remote. Were you trying to look up a reference or a tag through git or something?
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] rpr69:
In my searching it was suggested as a trouble-shooting test. As it turns out, ssh was not the right protocol. Once I switched to http, I can get the repo to sync, but I get 2 or 3 popups to 'Enter password' but all I have to do is hit OK without entering a password and it continues, which is fine, except it breaks automated building since there is no console, it fails the password request. I don't know how to get around this.

---------- Post added at 12:00 PM ---------- Previous post was at 11:59 AM ----------

That seems to only apply to ssh access using keys. I am using http protocol, which I don't think this applies to. If you are saying you will give me ssh access to the repo, I'm cool with that. ;)
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] m4570d0n:
That google plus photo link is not a valid URL (you didn't post the full URL without the "..."). Also, unless that photo is public, we won't be able to view it so you probably should just use something else like imgur or minus.

Also, what ROM and what branch?

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

Yeah, I don't remember getting any popups or messages in the terminal asking for a password. With my post the other day though, I was just copying the manifest info from the overview on cvd's bitbucket for convenience, as I wasn't building with that kernel anymore at the time, and now I'm working on getting some builds going for the LG G2. Just created a new local git repo though and added the moretz repo as a remote with an ssh URL and when I try to use git fetch I see what you're saying now. So, yeah, use https instead and you should be good to go.

@car vs driver, it might be a good idea to update your overview and change the info for the manifest from using "ssh" to "https" to avoid any possible confusion later.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] mrfeuss:
Any Slim builders encounter this during a compile? I'm looking at you [MENTION=3877985]prbassplayer[/MENTION] :P I'm trying to get Slim Kat up and running on the Optimus G Pro.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] kennkanniff:
I want to build me an Omnirom for the t989. I geuss I can just follow the AOKP? Any tips or tuts would be apprieciated.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] patch_Adams:
Omni has a sort of how-to here:

http://docs.omnirom.org/Porting_Omni_To_Your_Device
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] BlownFuze:
If you can build AOKP for your device, then you can start with that "how-to" for porting that Patch posted - but that is just the tip of the iceberg.

Off the top of my head:

- cm.mk needs to be changed to omni.mk

- In your device specific directories, got through all the .mk files, and any reference to /vendor/cm needs to be changed to the omni counterpart.

- the recovery build is also different, cm builds CWM - omni builds TWRP. So you have to change the fstab location and something else (can't remember)

It's been awhile since I've built omni - I focus on AOKP mainly, but just like any build you switch to, you have to work out the idiosyncrasies by building and sorting out the make errors. Wash, rinse, and repeat. Lol
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] NoSpamDan:
I'm currently working on a build of SlimKat with Moretz. Thanks [MENTION=4685003]car vs driver[/MENTION]. I have everything added, but the stock mpdecision file must be removed. I'm cool with that, and pretty much everything else involved, but I'd like to set my build up to automatically add the command while build is packaging up, to keep the build md5 integrity.

Not a show-stopper if I can't.

Does anyone know where in the sources I can add the necessary mpdecision delete command to the updater-script file so it gets automatically added to the build when it's packaged to a zip file?
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] prbassplayer:
You could just delete the mpdecidion binary from vendor (just comment out the line that links to it)
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] NoSpamDan:
Thanks. Comment out the linking line in which file? Still new at this, sorry.

EDIT: Didn't Slim use Marla at one point? Maybe SlimBean?
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] Kiltnar:
Yes. It was accepted as THE kernel for slim. They used his repos for skyrocket and herc I believe.

I'm trying to build aosp version 4.2.2_r1 for skyrocket. It builds OK but refuses to boot into the os. Any ideas?
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] NoSpamDan:
Maybe it's THIS one in /vendor/samsung/skyrocket/skyrocket-vendor-blobs.mk?

# Proprietary files
PRODUCT_COPY_FILES += \
vendor/samsung/skyrocket/proprietary/lib/hw/nfc.qcom.so:system/lib/hw/nfc.qcom.so \
vendor/samsung/skyrocket/proprietary/vendor/firmware/libpn544_fw.so:system/vendor/firmware/libpn544_fw.so \
vendor/samsung/skyrocket/proprietary/etc/wifi/nvram_net.txt_murata:system/etc/wifi/nvram_net.txt_murata \
vendor/samsung/skyrocket/proprietary/etc/wifi/nvram_mfg.txt_murata:system/etc/wifi/nvram_mfg.txt_murata \
[B][COLOR="Red"]vendor/samsung/skyrocket/proprietary/bin/mpdecision:system/bin/mpdecision \[/COLOR][/B]
...
...
...
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] prbassplayer:
Yup just add a # to the beginning and see if that works for you.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] NoSpamDan:
Yes, that's what I've tried. What commands should I avoid to keep from overwriting it? Repo init maybe?
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] prbassplayer:
Unless you commit the change or something changes on that repo from us it won't get overwritten
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] ThdDude:
I made the changes in our repo to stop adding them. [MENTION=5105835]Cl3Kener[/MENTION]'s kernel also needs Thermald removed as well see commit. If your build requires the same you can use our repo, or fork themuppits and make changes for yourself.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] NoSpamDan:
Thanks for the info.

I haven't found any information to indicate that Marla/Moretz for the Skyrocket needs the thermald removed, although I did look at your commits, one of which removes it from the Skyrocket blobs with the Diablo kernel.

[MENTION=4685003]car vs driver[/MENTION], could you comment on the consequences of removing thermald along with mpdecision when using Marla/Moretz for the SR on KitKat?

"fork themuppits" just sounds wrong, lol.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] ThdDude:
I think, could be wrong but think [MENTION=4685003]car vs driver[/MENTION] Kernel uses the same Thermal Controls as [MENTION=5105835]Cl3Kener[/MENTION] does. I have never had the pleasure to run one of CvD's Kernels. Lmao everyone Forks themuppits ) All the devices I build with Diablo need those files removed so it was just easier to fork their repo and make those needed changes.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] NoSpamDan:
Eh, nevermind, I think I'm OK for now. /System/bin/thermald doesn't exist in the build with Moretz. It is spec'd in the skyrocket-vendor-blobs.mk file, but must not be needed (or is removed automatically?). Off to flash. Thanks for the input folks.

Merry Christmas!
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] desalesouche:
hi all .

did someone had the browser black screen problem?

and if yes how did you solved that?

http://pastebin.com/BXKguwtK
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] NoSpamDan:
Flashed my build only to boot to a black screen :(

I had removed the kernel section from slim dependencies, but didn't add the moretz one since I got errors when I tried that.

I did get a kernel and a boot.img in my out folder with the build zip although I don't see them in the actual zip file. The kernel doesn't seen to exist in is raw form in even a known good zip, FWIW. Ideas?

EDIT: the boot.img IS in the build zip that fails, sorry. Trying sync and build with adding only the moretz lines to slim.dependencies now. I had both the moretz and master kernel ones before, but I still don't know... What I DO know is that I know just enough to be dangerous, lol.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] patch_Adams:
I may have asked this in here beefore, but I am really stuck. I am able to compile omnirom for i717 but the zip won't completely boot. I get boot animation and then I get sometimes icons over boot animation, or android has stopped over animation, or a red boarder around the screen over animation. I don't know how to fix this. It's weird. Even when I press the power button, I get the reboot menu, over the boot animation. Can you help me at all, it would be greatly appreciated!!

I'm using this for device tree: https://github.com/patch-Adams/android_device_samsung_quincyatt/tree/omni44
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] kennkanniff:
Haha. Thanks alot, right now im stuck at the recovery part I think that once i figured that out it should build. :)

Thanks, I have removed thermald from my cm11 build with the marla kernel. Do you maybe have a some more info about it, I feel like its a bit smoother but I know I am extremely sensitive for the placebo effect. ;)
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] ThdDude:
We remove them with Diablo Kernel because they conflict with the way Thermal and Mpdecison are implemented (Showp1984's). Leaving those files in we would see SOD's and other issues.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] kennkanniff:
Well I did have my alarm not going off a few times. Hope it is solved now.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] m4570d0n:
Has anyone successfully built a kitkat ROM with JDK 7? I was getting compiler errors with it and reverted back to JDK 6 and that seemed to resolve the issue, but downgrading back to JDK 6 is not really a "solution."
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] NoSpamDan:
OK, probably a dumb question, but I simply cannot find the answer. I'm trying to build Dirty Unicorns, got synched up, ran lunch, picked du_skyrocket-userdebug option from menu, and get this 4 times:

I see this error message in build/vendorsetup.sh like 3 or 4 times, so somehow the script can't find the top of the tree, wherever that's supposed to be. I'm running this from my user/dirtyunicorns folder at the shell prompt.

I've hit up [MENTION=4559825]wantowan2[/MENTION] who brought the SR Beanstalk, DU JB, and most recently, Beanstalk KitKat, but he has a lot going on. No luck with Google search either. I'm guessing something fundamental is missing in my setup. Building from /home/nospamdan/dirtyunicorns/ which is where the .repo lives...

Any ideas would be most appreciated.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] ktempleton:
That is pretty much an abandoned repo however if you hold on I'll get you the link for the new org

Here you go

https://github.com/DirtyUnicorns-KitKat/manifest

The skyrocket and other qcom devices still need work but we are more than happy to accept any contributions you want to make as far as commits and stuff

It's based on omni ROM for reference to set up device folders and stuff