yashsingh1/xdaforums huggingface dataset:
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] roger_n:
As you can tell by the name I set up this temporary irc for The_Blue_Waffle all gripes and complaints should be directed to him. ;)

Roger:cool:
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] car vs driver:
Make sure you guys register your nick's on freenode so I can +V and +O people as appropriate.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] BMP7777:
STILL CAN"T GET MINE REGISTERED!!! I have some kind of irc handicap. Can there really be that many people out there with my initials and 53 '7's after their name??
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] m4570d0n:
The jellybean branch is not the "earlier version." All commits for jb merged after the stable release still go to the jellybean branch. That is still the current, up to date branch and the primary branch for all things jellybean. When the mr1-staging branch is merged, it will be merged into a "CM10.1" branch, and then eventually merged into the primary 'jellybean' branch as well.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] :
Lol I just registered mine
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] BMP7777:
I hear you. i only meant that the average 'rookie' will want to use the one marked 'stable', and a choice might be confusing. If you think there should be an option given, I can do that as well. Whatever you think makes the most sense. Let me know...
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] wantowan2:
Great post but, huh? lol Just say'n cuz with the detail of your post, that seems like a lot to be missing?

Never had probs with dirty flashes or wiping in recovery. Nor the errors you mention.

Are you saying that the BusyBox binary from the cm repo isn't correct?

The only problem that I have is in AOKP 'settings/(Device Options)advanced settings/touch sensitivity' is greyed out. And I would really like to be able to access these settings. (No matter what kernel)
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] car vs driver:
Good question ... if your zip has busybox already, then extract and use that instead. But, you'll notice that busybox is part of the installation which happens after you do your cleaning of volumes.

Granted, I could be way off base here. But I've been having weird things happen during my install that I fixed as noted in the post.

If you wipe through recovery, then no worries there. My post was geared toward people who want to wipe during the installer-script execution process as well.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] onlychevys:
Mine is registered!
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] car vs driver:
Thread has been quiet for a bit ... what's everyone working on? Any new projects happening?
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] BMP7777:
Just my N7 project that's been put on hold due to the repo still being 4.1.2. Gonna update the thread with the aroma tut as soon as I feel better and make some room. Post #1 literally can't hold anymore text :banghead:
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] car vs driver:
Oh crap, I totally forgot ... I owe you that tutorial for the thread. I can bang that out tonight.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] :
Pm'd you about the fix for aroma
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] BMP7777:
Not in any hurry brother
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] dakpluto:
Just got my build environment back up and running. Working on a new custom ROM for when 10.1 is ready. Doing some graphic work right now. Not dead and gone, just been really really busy with school.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] dakpluto:
haven't played with Aroma in a while on Skyrocket, does it still have the ****ty colors, or does it finally look good on our phone now?
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] car vs driver:
In theory, the force_colorspace should fix it, but it made my installation freeze when launching aroma. I may have a bad file on my phone, will try it again in a bit and double check.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] BMP7777:
I remember boobah having constant fc issues when trying to adjust the color to true, I think he just said **** it. Not having it be as esthetically pleasing isn't the absolute end if the world.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] dakpluto:
No, it's not, was mostly just curious. Got used to it looking so pretty on my Nexus 7, lol.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] BMP7777:
I hear ya. Just got one and am working towards a PAC build for it. Successful builds but no boot. Waiting for the reoo to update to 4.2 then good to go.:D
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] ktempleton:
I'm building PAC for my I 577 compiles but won't boot. Do you think its the merge?
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] car vs driver:
Did you run a logcat during boot to see what's failing? That's a really generic question without having some specific details.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] ktempleton:
Not near the computer. Was going to when I get home I just saw above my post and remarked without thinking. Lack of sleep. Lol
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] car vs driver:
Word ... post a logcat and we can probably help.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] BMP7777:
Talked with the guy who posted the gits and he told me that the error is the 4.2 gits trying to compile on a 4.1.2 repo. He said that once the repo is updated there should be no trouble. Only thing is' he didn't mention when that would be:(
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] car vs driver:
Had an idea today that I want to bounce off you guys ... haven't tested it yet, I won't get a chance until probably tomorrow night to do so. But, here's my theory.

There are some scripts that I want to kick off after the phone has fully booted up. Of course, init.d scripts execute on boot (when the bootanim is running usually). That's fine and dandy, but it can slow down your boot while it waits for scripts to run.

Some scripts I have in nibbles can run at any time after boot, so as not to slow down the boot I want them to fire off much later. Scripts such as renice, permission fixes, zipalign and maybe even sqlite db cleaning.

At any rate, my idea is pretty straight forward ...

In init.d move the scripts out that I want to run later, say to /system/etc/postBoot

At the top of the newly move script put in a sleep command, lets say..

#!/system/bin/sh

sleep 300

.... rest of script

The next part is to create a new script in init.d that kicks off the postBoot scripts as background processes ...

#!/system/bin/sh

/system/etc/postBoot/script1 &
/system/etc/postBoot/script2 &
/system/etc/postBoot/script3 &
....
etc

I think this will work. Any thoughts? Or is there a much better way to do this ... I don't believe we have rc.d support so I couldn't go that route, which would have been easier.

Yes, this is the kind of crap that randomly pops up in my head.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] BMP7777:
Does yours take a long time to complete a boot? I typically have a 30 second boot time myself. My init.d file only has 2 items in it, and one of them are a ram tweak. I think it's a good idea, but it actually never occurred to me to find a way to adjust it. My laptop on the other hand, I have gone through the start-up programs and disabled them at will to reduce the length of boot time. But, that is a totally different animal. The code looks sound, but my eyes are hardly a professional viewpoint :) Get down with yer bad ass:cool:
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] car vs driver:
Well, I mentioned a couple that could take some time ...

I zipalign application APKs at boot and I clean and vacuum all sqlite dbs on boot. Both could take a while depending on changes since last boot. But, they can also run in the background with no ill effect to the user. Zipalign at least has its own db, so it doesn't zipalign previously aligned APKs - that one isn't too much of a worry.

The third one I have does a process renice, but process (like launcher) have to be up and running for it to actually work right. Again, that can be done at any time without screwing up the user, but it has to be done after the device is fully up and running. This one is really the one i'm targeting, really doesn't make a whole lot of difference on performance, i'm just bored and I want it to work properly.

I'll fiddle with it tomorrow and see what happens.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] m4570d0n:
question: was this thought by any chance derived from playing around with Conky?
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] ktempleton:
OK guys I have a question I have a boot image that I want to make a flashable zip with. How would I go about doing that? Thanks for your help
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] softballjunkee13:
Oops. :eek:
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] car vs driver:
Do you have the boot.img compiled? If so, it's a pretty simple installer-script in your flashable zip. Looks just like this (assuming you boot.img is in the root of your zip file):

mount("ext4","EMMC","/dev/block/mmcblk0p24","/system");
write_raw_image("boot.img","/dev/block/mmcblk0p8");
unmount("/system");

The installer script really is that simple. Of course, you'll want to add progress and messaging to the user so they know what's going on. Also, that's very specific to the skyrocket - use it on another device and you'll brick it.

I'd highly recommend adding cache and dalvik cache wiping to that script as well, usually a requirement when switching kernels (just a couple delete_recursve() calls at the top along with the appropriate mounts for /data and /cache).

---------- Post added at 09:23 AM ---------- Previous post was at 09:22 AM ----------

What's Conky?
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] liquidzoo:
Ok, search is down at the moment and I don't have the time to go through 270+ pages to see if this is answered...

In the OP, for kernel compiling it says that you need to install libwxgtk2.6-dev

Since Ubuntu 12.10 (I believe, maybe earlier), this file has been removed from their repos (based on a google search and the fact that I am not able to find it with a simple sudo apt-get install command).

Does anyone have a replacement for this file or a repo that I can add where I can get it? Just missing this one file, everything else installed just fine.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] BMP7777:
Conky is the Rainmeter of Linux. Good stuff; I am running one on my Luninux desktop as we speak. :cyclops: Love the name of it too.... always ask my wife if she wants to see my conky. I think it's funny anyway...
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] car vs driver:
I believe that package is optional ... give it a rip without it if you have to.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] m4570d0n:
I see it in my package manager in the repos for Ubuntu 10.04/10.10, but I don't have it installed. It's not necessary.

Package info:

---------- Post added at 02:12 PM ---------- Previous post was at 02:05 PM ----------

Found a commit on CM that seems like it would make kernel building/packaging rather easy. But it would require modifying the updater-script as you outlined above, and modifying the build.sh script for our kernel:

http://review.cyanogenmod.org/#/c/24053/1

Here's a few examples of it:

http://www.webupd8.org/search/label/conky

The reason I asked is that I have a few conky rc's that start up at boot with a sleep delay bash script like you mentioned.

#!/bin/bash

sleep 20 && # 0 good for Xfce - use 20 to 30 for Gnome

conky -c ~/.conkyrc &

sleep 20 &&

conky -c ~/.conkyrc-mem &

sleep 20 &&

conky -c ~/.conkyrc-hd &

sleep 20 &&

conky -c ~/.conkyrc-net &

sleep 20 &&

conky -c ~/.conkyrc-weather &

exit
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] ktempleton:
Hey guys I ran a build of liquid smooth and all it does is boot loop at the animation the log cat only says

- exec '/system/bin/sh' failed: No such file or directory (2) -[

Any ideas what went wrong and how I can fix it? Thanks for all your help
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] car vs driver:
Put it into recovery, connect into it with adb shell and poke around a bit. Make sure you got a clean flash and all the system files are where they should be. Also, check your zip for completeness and a valid installer-script.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] ktempleton:
Thanks I'll check it out when I get off from work
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] xcrazydx:
Conky is a character on the show Trailer Park Boys.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] wantowan2:
I've used this one before.

#!/system/bin/sh
# For compatibility on multiple ROMs, sleep for 2 min so the other scripts won't execute too early in the boot.
sleep 120
wait
exit 0

...also, does naybody know if this one will work on JB? Last time I used it was ICS.... :-/

#!/system/bin/sh
echo "50" > /sys/devices/virtual/sec/sec_touchscreen/tsp_threshold
exit 0
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] m4570d0n:
yes. You can check it by opening up a terminal emulator and typing:

cat sys/devices/virtual/sec/sec_touchscreen/tsp_threshold

Mine is at 70 which I assume is the default when charging.

I think it's defined in the kernel source at kernel/samsung/msm8660-common/drivers/input/touchscreen/qt602240_ts.c

btw, I just noticed your avatar. Did you base that off my theme? :)

I made this icon and use it in my theme as the default app icon and the sytemui icon:
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] BMP7777:
I am going to be in the process of updating the OP again, and would like to get some fresh ROM postings to keep the thread relevant in the development section. I have toyed with the idea of removing the ROM postings altogether in an attempt to create more space for tutorials. But, the thread would almost certainly be moved to general then, and I think most everyone likes this thread being here. So, if anybody has built a recent ROM in one of the categories, give me a link and features or a PM and I'll get it up there. Running out of room!
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] m4570d0n:
Here's my last build of PAC-man v18.0.0 from 12-04/12-05.

Nothing all that special. Includes:

transparent-themed Contacts

transparent-themed Mms (which includes Handscent-style theming with the fix for Mms pics overlapping text)

Optimus 4x style Circles lockscreen, Blackberry 10 style lockscreen and additional lockscreen theming options (clock position, colors, BG alpha, and some other stuff)

CM10-style circle battery

ADW launcher

Root Explorer

TitaniumBackup

SuperSU

ParanoidPreferences is also included and everything is set by default to the normal phone mode @ 240dpi so you can choose your own dpi and whether or not you want to use tabletIU mode on stuff.

Download Link:

http://d-h.st/AS9
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] rpr69:
Figures, the one day I *don't* check on you on d-h.st, you post an update. Thanks, I'll be installing tonight!
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] car vs driver:
So, does anyone have the touchwiz frameworks and jars handy? I think I might be missing a few pieces ... working on getting the slick new Note II gallery working on the skyrocket and I think it needs some of the tw frameworks. Hopefully it doesn't require the launcher, because that thing is dirt grade.

Anyone else try screwing with this thing yet?
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] BMP7777:
Duplicate post sorry
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] BMP7777:
Sounds good, I'm in. How'd you get the bb lock screen in there, I've been wanting to get that for a while. Great work!
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] car vs driver:
The bb lock is neat for like 30 seconds .... I've debated putting it in my ROM as optional.

Also, conky is sweet. And I hate unity. Switching to gnome as I write this.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] kchen96:
Why don't any of you guys like it? What are you guys currently using because personally I love it. I don't use any locks or passwords
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] car vs driver:
I'm using the stock lock screen that has slider shortcuts to my most used apps.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] m4570d0n:
With lots of frustration haha. I spent more time than I should have trying to merge it with the the current framework and ROM Control. Eventually, I got frustrated, said fudge it, reverted the Circles Lock stuff in ROMControl, and added everything in Settings the way it's implemented in Slim Bean, with some slight massaging. That was a whole lot easier. :)

New Lockscreens BlackBerry and Optimus 4x 1/2

Lockscreen fixes and features Part 1/2 frameworkbase

New Lockscreens BlackBerry and Optimus 4x 2/2

Lockscreen fixes and features Part 2/2 settings

Now that I have it, I regret wasting so much time messing around with adding it.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] car vs driver:
Getting a kernel build failure ... i'm not a kernel guy, so if anyone can help, i'd appreciate it. I'm using the TFQ-LZ kernel ...

Running into this at build:

make -C kernel/samsung/msm8660-common O=/home/carvsdriver/cm10/out/target/product/skyrocket/obj/KERNEL_OBJ ARCH=arm CROSS_COMPILE=" /home/carvsdriver/cm10/prebuilt/linux-x86/toolchain/arm-eabi-4.4.3/bin/arm-eabi-" cyanogenmod_skyrocket_defconfig
make[1]: Entering directory `/home/carvsdriver/cm10/kernel/samsung/msm8660-common'
GEN /home/carvsdriver/cm10/out/target/product/skyrocket/obj/KERNEL_OBJ/Makefile
HOSTCC scripts/kconfig/zconf.tab.o
scripts/kconfig/zconf.tab.c:206:24: fatal error: zconf.hash.c: No such file or directory
compilation terminated.
make[3]: *** [scripts/kconfig/zconf.tab.o] Error 1
make[2]: *** [cyanogenmod_skyrocket_defconfig] Error 2
make[1]: *** [sub-make] Error 2
make[1]: Leaving directory `/home/carvsdriver/cm10/kernel/samsung/msm8660-common'
make: *** [/home/carvsdriver/cm10/out/target/product/skyrocket/obj/KERNEL_OBJ/.config] Error 2
make: *** Waiting for unfinished jobs....
target Strip: libc (/home/carvsdriver/cm10/out/target/product/skyrocket/obj/lib/libc.so)

So I figured I'd look for the zconf.hash.c file. What I found was that file, jsut named slightly different ... zconf.hash.c_shipped

There were a few others in kernel/samsung/msm8660-common/scripts/kconfig with the _shipped name at the end. Should I just rename them?

BMP7777, you just ran a build with that kernel .. what are the files you have in that directory? Here's mine ...

carvsdriver@ubuntu:~/cm10/kernel/samsung/msm8660-common/scripts/kconfig$ ls
check.sh expr.c gconf.glade kxgettext.c lkc_proto.h mconf.c nconf.gui.c qconf.cc symbol.c zconf.hash.c_shipped zconf.y
conf.c expr.h images.c lex.zconf.c_shipped lxdialog menu.c nconf.h qconf.h util.c zconf.l
confdata.c gconf.c kconfig_load.c lkc.h Makefile nconf.c POTFILES.in streamline_config.pl zconf.gperf zconf.tab.c_shipped
carvsdriver@ubuntu:~/cm10/kernel/samsung/msm8660-common/scripts/kconfig$

Build was working fine until I ran a repo sync yesterday. I really don't want to refresh my build directory, I'd have to redo too many merges of my own code and that's just a pain in the ass.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] gs2usr:
You can commit your changes locally so they're permanent and when you do a repo sync it won't revert them.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] car vs driver:
Ok, so I'm terrible at using code repositories. But I decided that if I'm building my own kernel, I will learn to use git properly and share the source.

For those that don't know how to create their own repo on git and upload code, here's a very quick noob tutorial.

1. navigate to the base directory of your source code

2. execute the following commands:

git init
git add .
git commit -m "Initial commit"

3. Go to github and create a new repository.

4. Go back to your terminal window and execute the following commands:

git remote add origin https://github.com/carvsdriver/msm8660-common_nibbles.git
git push -u origin master

Then just wait. The last command will take a while depending on how big your local source is (this is where the code gets uploaded to git).

Next, to sync changes, just do this ..

git commit -am "Your comments here"
git push -u origin master

When you're done, you'll have all your source in git with a branch called "master".

This is probably remedial to the vast majority of you guys, but I figured if I had to search to learn how, someone else probably does too.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] m4570d0n:
You could also fork the kernel repo. You would just go to TFQ's github (or wherever), go to the msm8860 kernel repo, and click on the Fork button. Now you'll have that repo on your github and you can clone the source code and push changes back to your github. One advantage here is is that it's a lot easier to pull in upstream changes from the repo you forked that were made after you forked it.

https://help.github.com/articles/fork-a-repo
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] car vs driver:
Yes, that's probably a much better way to do it if you're starting from another base of code. I didn't do it that way because I wasn't thinking in advance ... I started with the CM10 base and already started making changes.

How can I reset this to fork CM10, then sync with the changes I've already made? (I already know how to make a fork)

Can I just create the forked repo in git, then push my changes in from my local source?

I'm so lost when it comes to git ... a step by step would be enormously helpful.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] m4570d0n:
yes. I just did it myself to test it.

First, for simplicity, let's say you have the source code locally on your computer but you downloaded it as a zip from github and so you don't have a git repo initialized yet.

You would start by initializing the repo

cd carvsdriver/cm10/kernel/samsung/msm8660-common
git init

setup the remote and upstream repos (change the URLs here as necessary).

git remote add github https://github.com/carvsdriver/android_kernel_samsung_msm8660-common.git
git remote add upstream https://github.com/Cyanogenmod/android_kernel_samsung_msm8660-common.git

In a lot of the reference info and guides and such, it will use "origin" here instead of "github". It doesn't really matter what you name it, but I chose "github" because that is what CM uses (it's in the default manifest at the top. You can also see this in /msm8660-common/.git/config).

Now, since you haven't checked out any branches or created any yet, but already have files, when you type "git status" it will say you are on the 'master' branch and list all the files in root of your kernel source as Untracked files. What you need to do is first add all the files

git add -A

then commit them

git commit -a

Now you can rename this master branch to whatever you want. In my test just now I wanted to create a new branch so I named mine "jb-b0rked"

git branch -m master jb-b0rked

Now push the commit to your github repo:

git push github jb-b0rked

I suppose you could change that to jellybean if you wanted to push these files to the jellybean branch. I don't know if there might be any conflicts with doing that. You could create a new branch like I did above and then just merge the branches. To do that you would push to the new branch like I just mentioned above, then:

git checkout -b jellybean
git merge jb-b0rked

This will merge the jb-borked branch into the jellybean branch.

Going back to the beginning of this post, if you had already cloned the repo and therefore already have a git repo initialized, one option would be to just delete the ".git" folder in your source and then do everything as noted above. You could change the remote from pointing to the original source, to pointing to your forked repo instead, but I don't know if you would run into any issues/conflicts with the the refs, heads, commit messages, etc. that are already in your .git folder.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] car vs driver:
You are a gentlemen and a scholar, thank you sir.