yashsingh1/xdaforums huggingface dataset:
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] mtdew:
Gs2usr has gotten boot but is plagued by issues with storage maybe talk to him.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] wantowan2:
Could somebody else running ANY slim build try this test for init.d functionality?

Just put the red text into a file, save it as, say, touch(no extension), put it in system/etc/init.d folder and reboot. Then, go find '/data/local/tmp/' and see if there is a file called 'init.d_log_test.txt' in there?

Thanks guys....
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] prbassplayer:
You need to set proper permissions before reboot or fix permissions in recovery.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] ganja_guru:
roger_n thank you so much for this. I can confirm working Voip with tango on this and no issues to report. Skype call testing worked too, will report back when I make an actual call with Skype. Congrats on building the only 4.2.2 ROM that fixes the voip issue. Now you should definitely start a new thread for this beast.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] roger_n:
Thanks if you scroll back a few pages I also post CM10.1, and Slim with working VOIP.

---------- Post added at 08:51 AM ---------- Previous post was at 08:45 AM ----------

I haven't seen you mention that the file "touch" has to owned by "root" and made executable for it to work. Do you think that may be your problem?
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] wantowan2:
Sure, tried that too. Didn't work. I know init.d scripts only need rwxr-xr-x to run. I've been looking at this for weeks over multiple builds. The only way I can run an init.d script is to call it specifically in init.qcom.post_boot.sh

---------- Post added at 07:35 PM ---------- Previous post was at 07:00 PM ----------

This looks interesting. Would this be automatically included in my sync?

From git://github.com/CyanogenMod/android_hardware_qcom_display-caf
+ 26b8e68...6f3a586 caf-rebase -> github/caf-rebase (forced update)
2166f79..fc5c7c5 cm-10.1 -> github/cm-10.1
Fetching projects: 6% (21/339) remote: Counting objects: 25, done.
remote: Compressing objects: 100% (4/4), done.
remote: Total 15 (delta 5), reused 14 (delta 4)
Unpacking objects: 100% (15/15), done.

This "caf-rebase (forced update)". Assuming I needed it, would I have to call rebase as a revision?
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] onlychevys:
Is it just me, or do ya'll have to totally mess with your slim build every time you sync? What a pain in the nether places!
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] prbassplayer:
What do you mean?
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] onlychevys:
I can't get a good build after a repo sync for nothing! I have to fight errors every time. I will give you my new one's in a few because I know it will error soon.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] prbassplayer:
If its related to vendor files and hercules device folder git pull request. I can add to our repo eventually. Or don't commit the changes, they shouldn't delete themselves on sync (I think)
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] wantowan2:
Totally agreed! Have to revert my vendor mods and manifest then add back and resync....it works.....but.....

Hey, PR or anybody. I am having the say exact errors that I was having with Baked but it has hit my slim build. I changed nothing , just synced. Too many of these to post but heres the jist

hardware/qcom/media/mm-video/vidc/vdec/src/omx_vdec.cpp:8963:41: warning: comparison between signed and unsigned integer expressions [-Wsign-compare]
hardware/qcom/media/mm-video/vidc/vdec/src/omx_vdec.cpp:8965:391: warning: format '%d' expects argument of type 'int', but argument 5 has type 'OMX_S32 {aka long int}' [-Wformat]
hardware/qcom/media/mm-video/vidc/vdec/src/omx_vdec.cpp:8965:391: warning: format '%d' expects argument of type 'int', but argument 6 has type 'OMX_S32 {aka long int}' [-Wformat]
hardware/qcom/media/mm-video/vidc/vdec/src/omx_vdec.cpp:8965:391: warning: format '%d' expects argument of type 'int', but argument 7 has type 'OMX_S32 {aka long int}' [-Wformat]
hardware/qcom/media/mm-video/vidc/vdec/src/omx_vdec.cpp:8965:391: warning: format '%d' expects argument of type 'int', but argument 8 has type 'OMX_S32 {aka long int}' [-Wformat]
hardware/qcom/media/mm-video/vidc/vdec/src/omx_vdec.cpp: In member function 'OMX_ERRORTYPE omx_vdec::handle_demux_data(OMX_BUFFERHEADERTYPE*)':
hardware/qcom/media/mm-video/vidc/vdec/src/omx_vdec.cpp:9320:133: warning: format '%d' expects argument of type 'int', but argument 4 has type 'OMX_U32 {aka long unsigned int}' [-Wformat]
hardware/qcom/media/mm-video/vidc/vdec/src/omx_vdec.cpp: In member function 'bool omx_vdec::allocate_color_convert_buf::set_color_format(OMX_COLOR_FORMATTYPE)':
hardware/qcom/media/mm-video/vidc/vdec/src/omx_vdec.cpp:9777:71: warning: zero-length gnu_printf format string [-Wformat-zero-length]
hardware/qcom/media/mm-video/vidc/vdec/src/omx_vdec.cpp: In member function 'OMX_ERRORTYPE omx_vdec::allocate_color_convert_buf::allocate_buffers_color_convert(OMX_HANDLETYPE, OMX_BUFFERHEADERTYPE**, OMX_U32, OMX_PTR, OMX_U32)':
hardware/qcom/media/mm-video/vidc/vdec/src/omx_vdec.cpp:9925:138: warning: format '%d' expects argument of type 'int', but argument 5 has type 'OMX_U32 {aka long unsigned int}' [-Wformat]
make: *** [/home/wantowan2/sb2/out/target/product/skyrocket/obj/SHARED_LIBRARIES/libOmxVdec_intermediates/src/omx_vdec.o] Error 1

Whatever fixes this, fixes Baked too.... damn

omx_vdec.o
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] wantowan2:
Haha, look up ^^^^^^

You think that rebase merge broke SR?

I think that manifest commit got reverted. I resynced and I think it fixed. Building again...
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] prbassplayer:
I need to see the make error, scroll up and/or compile j2 or j1

Do you have Qcom CAF realted repos?
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] wantowan2:
Ya, same as always. There was a manifest change earlier. Around 4-5 hours ago. I started building, then it failed about 3/4 of the way through. I resynced, it made another manifest change???? made bacon and the build finished. v.3.4

IRC for slimroms, cool.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] prbassplayer:
The manifest change was related to NFC. What did change was Qcom/media and Qcom/display-caf. The First one was needed to work with current caf and the latter was a ifdef for xperia devices. Btw Should have init.d now :p
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] wantowan2:
IC, nice.

AND YES! INIT.D Is back! Thank you sir. What a relief. I checked out (recently) like 3 cm based roms and they all didn't have init.d support. Honestly, who knows how many people 'thought/think' they are all set up with a nice tweaked rom. NON have even their first boot coverage even done yet. How could cm leave something like that for soooo long? I'd say....2-3 months.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] prbassplayer:
As far as I know CM rarely adds init.d support. I implemented it through msm8660-common's init.qcom.rc. What I added should work on pretty much any device's .rc file. Look at the commit.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] wantowan2:
Ok, I will. Good stuff to know for the future.

@PR Here is a gift for you. Add this pic to your sig.....hahaha

Over the last while. in my travels, I have see something very close to this. I even think that I added it to a few different files in etc... But it never took. I even made a recovery*****.sh and it didn't work...

Hey, is there any way to get touch sensitivity to work again in settings/device/advanced/... It's there, but greyed out. It used to work but not for a loooong while. I see the dialog for it all over the rom source.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] wantowan2:
Here is an example. I have added a few apps in vendor/slim/prebuilt/common/app. I then had to add the items, current path and install path, to the vendor/slim/config/common.mk.

But when I sync, I get errors, like this:

The way around it is to hide them for 1 sync, put them back and resync. Is there a better way to do it?
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] wantowan2:
WHOA! Did I just see tumbleweed blow by....? ecco))))))
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] epapsiou:
That is a sign of everything working perfect :)
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] car vs driver:
It's also getting nice out ... I think most of us are spending less time inside in front of a computer :)
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] wantowan2:
OK, good. Just check'n. I was sick there and when I checked, mine was the last post and it was 6 days prior.

Gotta say, true. I've been building Moretz into my slim 4.1 and anybody would love it.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] wantowan2:
So, I really want to modify the various config. files in 'packages/apps/Settings/res/values'. I want to preset my personal defaults to some items in them.

I tried but build fails.

Defaults like :

zram

dpi

clock possition

real dark slim

"RE enable" touch screen sense in settings/device/

Anyway to do this?
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] car vs driver:
What are the build errors?
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] car vs driver:
Anyone catch this? http://xdaforums.com/showthread.php?t=2247146

Pulling the repos now to see if I can get it up and running on our device. Looks promising.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] BMP7777:
Thanks for the head's up! Like to port this badboy for the N4.....:cool:
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] car vs driver:
Been up and running with it for about 20 minutes now. Seems pretty slick so far. Everything is working too, that's refreshing. :highfive:

And as promised ...

Download: http://tinyw.in/6GQb

I'm going to get in touch with the dev, confirm he's OK that I post it up and will start a new thread for it tonight.

Edit 8:29PM ET 4-23-13:

Updated the zip with a few tweaks ... added some scripts, removed mpdecision conflict.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] wantowan2:
Oh wow, too many. Just a quick 3 pages of them. I just was wondering if I was looking in the wrong places, if something says 'non translatable' is that literal?

---------- Post added at 04:50 PM ---------- Previous post was at 04:43 PM ----------

I was also wondering if you might do a quick and nasty -/+ tut for this ROM. By that I mean, if you say, compared it to cm10.1. (Which anybody can build) just list what the diff is as apposed to a whole tut. Or (for the interest of maintaining the thread) just say that the original topic thread is good enough?

Edit: local_manifest?
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] car vs driver:
Sure thing man, it was easy ... here's the steps ... taken from the original thread and tweaked for the SR.

Setup a new build directory, name it beanstalk and all of the following commands are issued from that new location

1. type 'repo init -u git://github.com/scotthartbti/android.git -b cm-10.1'. This will setup the folders to be synced.

2. type 'repo sync'. This will sync the folders to your beanstalk directory. Note - This will take some time depending on internet connection. Be patient!

3. After the repo sync finally finishes, all you need to do is add your device, kernel, vendor specific files for the device you are building for... (the next steps cover this)

Skyrocket Specifics:

4. Go into your .repo directory,

5. Create a new directory called local_manifests

6. Create a new file called roomservice.xml in local_manifests and paste in the following:

<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="CyanogenMod/android_device_samsung_skyrocket" path="device/samsung/skyrocket" remote="github" revision="cm-10.1" />
<project name="CyanogenMod/android_device_samsung_hercules" path="device/samsung/hercules" remote="github" revision="cm-10.1" />
<project name="CyanogenMod/android_device_samsung_msm8660-common" path="device/samsung/msm8660-common" remote="github" revision="cm-10.1" />
<project name="CyanogenMod/android_device_samsung_celox-common" path="device/samsung/celox-common" remote="github" revision="cm-10.1" />
<project name="CyanogenMod/android_device_samsung_qcom-common" path="device/samsung/qcom-common" remote="github" revision="cm-10.1" />
<project name="TheMuppets/proprietary_vendor_samsung" path="vendor/samsung" remote="github" revision="cm-10.1" />
<project name="carvsdriver/msm8660-common_marla" path="kernel/samsung/msm8660-common" remote="github" revision="master" />
</manifest>

7. You can replace the kernel path with something other than Marla (use the stock CM10.1 kernel or Moretz if you prefer). If you keep Marla (or use any other non-stock kernel from the main CM10 repo), you'll need to continue following the next steps. If you swap that out with the stock CM10.1 kernel, stop here and goto step 9.

8. You need to edit device/samsung/skyrocket/cm.dependencies and make it look like the follwing code. This will remove the stock kernel as a dependency. If you don't do this, it'll overwrite whatever non-stock kernel you put in roomservice.xml whenever you build.

{
"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"
}
]

9. Run the following command: vendor/cm/get-prebuilts

10. Type '. build/envsetup.sh && brunch "device name"'

11. Wait patiently for build to run ...

Original BeanStalk thread ...

http://xdaforums.com/showthread.php?t=2091900
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] icythunder:
Nice!

Hey CvD! do we need GAPPS to install on top of it?
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] car vs driver:
Yup, my zip is the ROM only. I strongly recommend a factory reset / full wipe prior to installation.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] fham:
I have been using this with my Infuse. On that device and with the build you have to flash GAPPS after flashing the ROM.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] wantowan2:
Nice dude! Now, if this gets popular, we can get it added to the OP. My only question now is @ the end, when I add "skyrocket" where indicated, it wants to build cm_skyrocket. Same when I lunch. There is no mention of beanstalk_skyrocket anywhere?
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] car vs driver:
Nope, just brunch cm_skyrocket-userdebug should do the trick.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] car vs driver:
Just a heads up for you guys in case you don't follow my kernel threads ...

Starting with the 4/24 nightly you cannot use marla or moretz in your builds. They are completely incompatible with the gigantic amount of changes pushed yesterday. I reforked the main kernel repo so that I can basically start over to recreate the kernels on the newly rebased source.

This will be painful ...

Also, BLN doesn't work starting today. So expect people to start freaking out about it.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] mtdew:
Thank god bln is gone.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] car vs driver:
Hopefully not for long. I talked to Topprospect about it already, I'm going to look into fixing it based on his work with the previous kernel version (where it was broken there too). I should get some time tonight to dig into it, if not, this weekend for sure.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] mtdew:
Why would you fix it that means I gotta listen to more crap about how do I make my bln turn on or how can I make it do this:rolleyes:.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] prbassplayer:
Wait what changes? o_O

Edit: Disregard I just saw the MASSIVE dump done yesterday... Damn I go a day and msm8660 now needs a ton of testing.... -_-;
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] car vs driver:
The shorter answer would be to state what didn't change ... it's going to be a long weekend.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] wantowan2:
Hey, so I did a beanstalk build to try it out. (meah....) however, the one thing that works again with it (as apposed to being greyed out with every other rom) is touch sense in advanced settings. (*wink*wink*, nudge nudge....)
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] prbassplayer:
Whats touch sense? o_O

On a second note OMFG CM rebased their display-caf and audio-caf.... and I'm scared on using it now lol I have a slight feeling that it will break crap lol....
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] liquidzoo:
Wonder if that's going to break things like King Beatz... People are going to be mad if it does, I'd bet.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] prbassplayer:
Don't know I'm updating all the new msm8660 things, I'm going to try and not mess with display-caf and audio-caf for now see if it works. Hmm seems like one of the msm8660 changes will force to update radio....
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] wantowan2:
Touch Sensitivity. Found in advanced settings of every cm based ROM. Currently, with exception of this beanstalk, the button is there(greyed out) clicking it does nothing. BUT you used to be able to (cm9ish)enter there to adjust the sensitivity of the device touch screen. So, clearly, this valuable feature is disabled due to oversight and not hw limitations
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] wantowan2:
So, a current slim/moretz will not boot as of now?
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] prbassplayer:
4.2 should work fine. As for compiling right now I don't know. My compiled kernel is larger than cm's last nightly and that worries me lol
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] car vs driver:
Moretz/marla will not compile with 4/24 and later. I'm planning to get that fixed over the weekend.

EDIT:

Work has begun. I created a new repo so I can keep the upstream CM10.1 updates properly merged into my source. That was painful because I had to dump and reset a few other repos in my git to make it work. Apparently you can only fork something once .. who knew ...

Anyway, here's the link to my new repo for Moretz/Marla ... those branches will be named appropriately. I already started on Marla, that one will be done first. When you see the v2.0 commit hit, that means it's good to pull into your builds.

https://github.com/carvsdriver/android_kernel_samsung_msm8660-common

Any questions in the meantime, let me know.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] wantowan2:
Gotch ya. So when it's ready, moretz will look like this.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] car vs driver:
You got it
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] wantowan2:
So I haven't changed my setup at all for Slim and now I am getting a whole thwack of video lib errors. mm-video, fatal error: video/msm_hdmi_modes.h: No such file or directory....etc
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] prbassplayer:
It needs some updates from cm which I have but my kernel is like 0.1MB bigger than CM's. Going to pull their caf repos and verify.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] car vs driver:
The rebased kernel moved some stuff around and what you are seeing is a result of centralizing a specific header file for resolution modes. The header is actually in the kernel repo, but it is referenced outside the kernel now as well.

Here's the relevant commit in the post 4/24 kernel ...

https://github.com/CyanogenMod/andr...mmit/a0d8de3de86fb1b9bdef4305a7a53dceb3235c63

When building with source post 4/24, you have to resync your entire repo. Things are starting to get much more integrated.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] wantowan2:
Ok, so..... delete repo and repo init again?
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] car vs driver:
You don't need to delete the repo ... if you are building with anything from CM-10.1 branches, you have to re-sync everything. If you are pulling in repos from somewhere else as well (like frameworks for example), you'll have to make sure that they have also merged in the appropriate changes that dropped on 4/24.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] wantowan2:
I definitely resync before I build tho. So your slim is building fine?
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] mtdew:
Anyone wanna try and take the challenge of pa? I think most peoples issue was not using the jellybean-legacy branch.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] prbassplayer:
Hey I'm out for the weekend but I need some help with skyrocket kernel. I'm lost as to why kernel I compile is 0.1MB larger than latest nightlies.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] ktempleton:
If I had a skyrocket I'd flash it and see if it works its such a small amount
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] car vs driver:
Did you change the kernel compression type?
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] car vs driver:
I'd take a look at the header first ... that may be what's throwing the whole thing off ...

/home/wantowan2/sb2/kernel/samsung/msm8660-common/drivers/video/msm/hdmi_msm.h:142: error: old-style parameter declarations in prototyped function definition

Other than that, you clearly seem to have a missing { or } somewhere.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] prbassplayer:
if I owned one I would as well but giving out to other people duno I'd like to find out what's up with it.

Nope upstream cm I'm just compiling inline.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] ktempleton:
My Buddy has one I should see him tomorrow if you pm me a link I'll test it for you
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] wantowan2:
What about running them with meld to see the diff?
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] prbassplayer:
There isn't like I said kernel is upstream cm from fresh source. I don't touch kernel source at all never have.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] wantowan2:
That's 102.4Kb. About the size of a large driver file.

So, your comparing 2 kernels. 1 before the big commit and 1 after. Both cm from your slim build folder? I take it the file count is the same...
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] prbassplayer:
No I'm comparing new kernel + device folder + hardware folder (qcom caf things) to latest cm nightlies
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] wantowan2:
That's some crazy quality control dude....lol I think my builds can differ by many many megs..... I guess it's not the same thing. Between build 4-4.1 there was .3meg diff for me.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] prbassplayer:
Builds don't worry me it's the boot.img. Rom itself changes size every day depending on changes but kernel size diff worries me. Again if o owned the device I'd flash it myself lol but giving out to other users to test... I don't like bricking mate and worst case could lead to that. So ya I want to find out why it's different.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] wantowan2:
Well, if there is something you would like me to try and replicate, please let me know. I can easily stash anything non stalk and so on. If I'm not building 4.3 I'd like to help.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] wantowan2:
Apparently (and it's compiled with every build anyway) we are supposed to be able to simply type 'emulator' after a build completes and while it's still in memory to test build that way. I personally haven't made this work but what about that?
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] GTDarthYoda:
I want to test it but I've killed my skyrocket once... Not looking to do it again... But then again I got a good backup device and last time it only cost me $20 to get a new board so... i just might >.< Trying to wait till monday but I get too antsy sometimes. That's have the reason i have a good backup device now :P
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] car vs driver:
I wouldn't worry about the size difference, as long as it flashes to the correct partition the worst that could happen is that it won't boot.