yashsingh1/xdaforums huggingface dataset:
[Galaxy Note GT-N7000 Android Development] chasmodo:
Setting up the Build Environment

First things first: you need to download and install 64-bit version of Ubuntu 12.04. A 32-bit one won't cut it.

Installed it? Good, let's move on.

Now do a system update; click that little switch icon in the top right hand corner and you'll get a menu. Launch Update Manager and install everything it finds.

Now that your Ubuntu is up to speed you need to download and install some more stuff. Launch the terminal (Ctrl + Alt + T).

Copy the below code and paste it (right-click and paste or Shift + Insert, Ctrl + V doesn't work) in the terminal, hit enter.

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

If 'lib32ncurses5-dev' fails, delete it from the list, install everything else.

Now you need to add the following repos, again copy/paste each line into the terminal, hit enter. Repeat for each line of the code below.

sudo add-apt-repository "deb http://archive.ubuntu.com/ubuntu hardy main multiverse"

sudo add-apt-repository "deb http://archive.ubuntu.com/ubuntu hardy-updates main multiverse"

sudo add-apt-repository "deb http://archive.canonical.com/ lucid partner"

sudo apt-get update

Now you are going to install Synaptic.

sudo apt-get install synaptic

Done? Good.

Click the 'Dash Home' button (top left hand corner of your desktop), find and launch Synaptic Package Manager. Search for 'Sun Java6 JDK' and install it will all the dependencies except sun-java6-demo and sun-java6-doc.

Now go to http://developer.android.com/sdk/index.html and download the linux version of the Android SDK. It provides the API libraries and developer tools necessary to build. When your download is done, open it with Archive Manager, extract it somewhere, and move the extracted folder to your Home folder. Rename it to 'SDK' for simplicity.

Now you need to download and install Android SDK Platform Tools. Use file manager to navigate to your SDK sub-folder Tools. Find 'android' and double-click to run it. You'll be asked what you want to download. Choose the 'Platform Tools' and the Android 4.1.2 SDK Level 16 and the Android 4.2 SDK level 17 Dev tools and hit install. Let it download; it might take some time, depending on your download speed.

Now the time is ripe for you to setup your Android repos. Copy/paste the following commands into the terminal, hit enter after each one.

mkdir -p ~/bin

mkdir -p ~/cm10.1

curl http://commondatastorage.googleapis.com/git-repo-downloads/repo > ~/bin/repo

chmod a+x ~/bin/repo

export PATH=~/bin:$PATH

You have to reboot after this for changes to take effect.
[Galaxy Note GT-N7000 Android Development] chasmodo:
Initial Repo, local_manifest

Once reboobed, open the terminal once again and do this:

cd cm10.1

repo init -u git://github.com/CyanogenMod/android.git -b cm-10.1

repo sync

Your initial sync will take some time. After it is is done, go to your cm10.1/.repo folder (/.repo is hidden, so press Ctrl + H in your file manager for it to show up). Create a

subfolder called local_manifests in /.repo. Then create a blank document called roomservice.xml in /.repo/local_manifests. Copypasta™ the below code into roomservice.xml,

save it, close the document.

NOTE: All in the above posts needs to be done only once, prior to compiling your first build.

For all your subsequent builds you'll have to do just the steps listed in the next posts.
[Galaxy Note GT-N7000 Android Development] chasmodo:
Start the Build

It's time for you to do another repo sync to pull Samsung device-specific stuff.

repo sync

This sync is going to be considerably shorter than the first one. After it is done, it's time for you to start the build.

~/cm10.1/vendor/cm/get-prebuilts

. build/envsetup.sh

export USE_CCACHE=1

prebuilts/misc/linux-x86/ccache/ccache -M 50G

brunch n7000

If everything goes right, you should see this at the end of the compile:

Your cm10.1 rom zip will be in cm10.1/out/target/product/n7000 folder.

This is how it looks when the build gets going:

[YOUTUBE]UbB8oURLJpY [/YOUTUBE]
[Galaxy Note GT-N7000 Android Development] chasmodo:
Subsequent Builds

You'll want to do another build tomorrow once your first one has gone through fine.

There are two ways you can go about it.

#1: do a

cd cm10.1

repo sync

export USE_CCACHE=1

~/cm10.1/vendor/cm/get-prebuilts

. build/envsetup.sh

brunch n7000

The build system should notice which source files have changed and need rebuilding, and should only build the new stuff. This is what you might want to do when there were no major changes in the merged commits here: http://review.cyanogenmod.org/#/q/status:merged,n,z

However, what I always do and would always recommend

#2:

cd cm10.1

make clean

repo sync

~/cm10.1/vendor/cm/get-prebuilts

. build/envsetup.sh

brunch n7000

'make clean' command will delete your whole /out folder, and your new build will start from scratch. Instead of 'make clean' you can also use 'make clobber'; the difference between the commands is explained here.

There is a way to completely automate your compiling process à la CyanogenMod's Jenkins. You can learn how from AndroidSlave here: http://xdaforums.com/showthread.php?p=46110939
[Galaxy Note GT-N7000 Android Development] chasmodo:
Cherry Picking

***Cherry picking from CM Gerrit***

This is one of the perks of compiling CM10.1 yourself. Official nightlies have a lot of features, but there's also a lot of stuff waiting for a review on Gerrit.

You can follow the commits waiting to be reviewed and merged into the main repo here: http://review.cyanogenmod.org/#/q/status:reviewed,n,z

You can cherry-pick anything from the upcoming features and incorporate it into your Rom before the official CM10.1 does the same.

Let's say that you want to have this commit before it becomes merged: http://review.cyanogenmod.org/30878

The commit says:

Project	CyanogenMod/android_packages_apps_LockClock

It's quite simple to do that. Fire up the Terminal (Ctrl + Alt + T) and navigate to your LockClock folder.

cd cm10.1/packages/apps/LockClock

In other words you must be in the same folder as stated in 'Project' for cherry-picking to work.

Now minimize the terminal (don't close it) and switch to the Gerrit page in your browser.

http://review.cyanogenmod.org/#/c/30878/

Click on cherry-pick button here.

Then click several times on the little clipboard icon at the end of the cherry-pick URL.

This automagically copies the cherry-pick URL into your clipboard. Now, go back to your terminal, paste the cherry-pick URL in it and hit enter.

That is all: the commit will get pulled and incorporated into your local repo. You are ready to compile a build which will contain the feature you have just cherry-picked.

***Cherry-picking from Github***

http://xdaforums.com/showpost.php?p=42486858&postcount=449
[Galaxy Note GT-N7000 Android Development] chasmodo:
How to compile CM10.1 for Nexus 4

If you have never built CM10.1 then you need to do everything from post #3 here, and this part

cd cm10.1

repo init -u git://github.com/CyanogenMod/android.git -b cm-10.1

repo sync

from post #4.

After the initial repo sync is done, now comes the Nexus 4 specific bit. As stated before, go to your cm10.1/.repo folder and create a blank document called local_manifest.xml. Paste the below code into local_manifest.xml, save it, close the document.

If you already have local_manifest.xml with n7000 stuff in it, then just add all the lines beginning with <project name= from below to it, save and exit Gedit.

Now do the second repo sync to pull Nexus 4 specific stuff.

repo sync

Do the following after the second sync has gone through.

~/cm10.1/vendor/cm/get-prebuilts

Now it's time to start the build.

. build/envsetup.sh

export USE_CCACHE=1

brunch mako

That's it. Wait for the build to get compiled and flash your CM10.1_UNOFFICIAL_mako.zip from cm10.1/out/target/product/mako folder.
[Galaxy Note GT-N7000 Android Development] chasmodo:
How to compile CM10.1 for Note II LTE (t0lte)

If you have never built CM10.1 then you need to do everything from post #3 here, and this part

cd cm10.1

repo init -u git://github.com/CyanogenMod/android.git -b cm-10.1

repo sync

from post #4.

After the initial repo sync is done, now comes the Note II LTE specific bit. As stated before, go to your cm10.1/.repo folder and create a blank document called local_manifest.xml. Paste the below code into local_manifest.xml, save it, close the document.

If you already have local_manifest.xml with n7000 stuff in it, then just add all the lines beginning with <project name= from below to it, save and exit Gedit.

Note: you might already have some of the lines in your local_manifest.xml if you have compiled a build for n7000. If that's the case, skip adding the lines you already have.

Now do the second repo sync to pull Note II specific stuff.

repo sync

Do the following after the second sync has gone through.

~/cm10.1/vendor/cm/get-prebuilts

Now it's time to start the build.

. build/envsetup.sh

export USE_CCACHE=1

brunch t0lte

That's it. Wait for the build to get compiled and flash your CM10.1_UNOFFICIAL_mako.zip from cm10.1/out/target/product/t0lte folder.
[Galaxy Note GT-N7000 Android Development] chasmodo:
Reserved

How to set up a build environment in Ubuntu 13.04:

http://xdaforums.com/showthread.php?t=2224142
[Galaxy Note GT-N7000 Android Development] chasmodo:
Discarding Failed or Unwanted Cherry Picks

If you want to get rid of something you have cherry-picked this is what needs to be done.

We'll stick to the cherry-picking example described in the previous post.

Start the Terminal and navigate to the folder containing your unwanted cherry-pick, in this case LockClock.

cd cm10.1/packages/apps/LockClock

From here you need to persuade Git to discard the cherry-picked thing. Do this:

git reset --hard

And that is that.

However, sometimes git has its quirks and doesn't want to do what it's been told. If that is the case, you'll get warnings when doing your next repo sync.

If that happens, repeat the two steps from above and delete the top folder where your cherry-pick was located. In this case, it is /packages.

Do the repo sync again and the folder will be redownloaded and stored on your machine in pristine state.
[Galaxy Note GT-N7000 Android Development] chasmodo:
How to compile CM10.1 for Nexus 7

If you have never built CM10.1 then you need to do everything from post #3 here, and this part

cd cm10.1

repo init -u git://github.com/CyanogenMod/android.git -b cm-10.1

repo sync

from post #4.

After the initial repo sync is done, now comes the Nexus 7 specific bit. Do this:

~/cm10.1/vendor/cm/get-prebuilts

. build/envsetup.sh

breakfast grouper

This will download the device specific configuration and kernel source for your device.

Now it's time to extract proprietary blobs from your tablet.

Go to your grouper CM10.1 folder.

cd cm10.1/device/asus/grouper

Connect your Nexus 7 to the computer using USB cable. Make sure that adb debugging is on in Developer's Options. Now paste this into the terminal:

./extract-files.sh

If you get adb errors, that means that adb is not in the path of execution. Close the terminal, start your file manager and when in your /home folder press Ctrl + H for hidden stuff to appear. Open .bashrc file with Gedit and add the following line at the end of the code:

export PATH=${PATH}:/<your path to sdk>/platform-tools

(My <path to sdk> looks like this: export PATH=${PATH}:/home/chasmodo/android-sdk/sdk/platform-tools)

Save the file, open a new terminal window, go to cd cm10.1/device/asus/grouper and repeat

./extract-files.sh

The adb command should now be available and your blobs pulled. After this has been done go back to cm10.1 folder and start the build.

cd ~/cm10.1 (or croot, same thing)

export USE_CCACHE=1

brunch grouper

After the compile goes through, your CM10.1_UNOFFICIAL_grouper.zip will be waiting for you in cm10.1/out/target/product/grouper folder.
[Galaxy Note GT-N7000 Android Development] chasmodo:
How to compile CM10.1 for Note II (n7100)

If you have never built CM10.1 then you need to do everything from post #3 here, and this part

cd cm10.1

repo init -u git://github.com/CyanogenMod/android.git -b cm-10.1

repo sync

from post #4.

After the initial repo sync is done, now comes the Note II specific bit. As stated before, go to your cm10.1/.repo folder and create a blank document called local_manifest.xml. Paste the below code into local_manifest.xml, save it, close the document.

If you already have local_manifest.xml with n7000 stuff in it, then just add all the lines beginning with <project name= from below to it, save and exit Gedit.

Note: you might already have some of the lines in your local_manifest.xml if you have compiled a build for n7000. If that's the case, skip adding the lines you already have.

Now do the second repo sync to pull Note II specific stuff.

repo sync

Do the following after the second sync has gone through.

~/cm10.1/vendor/cm/get-prebuilts

Now it's time to start the build.

. build/envsetup.sh

export USE_CCACHE=1

brunch n7100

That's it. Wait for the build to get compiled and flash your CM10.1_UNOFFICIAL_mako.zip from cm10.1/out/target/product/n7100 folder.
[Galaxy Note GT-N7000 Android Development] answersun:
thumbs up, really appreciate sharing your knowledge :good:
[Galaxy Note GT-N7000 Android Development] antiochasylum:
Re: [HOWTO] Build CM10.1 for N7000

I build on the first gen i7 @ 2.0ghz, 8gigs of ram, 120gig SSD, clean compile is about 30-35 min.

My next machine will be a i7 @ 3.4, 16gigs of ram and 250gig SSD

I suggest a minimum of an i3 with 8gigs of ram, otherwise you'll be compiling for hours.

Then reason I suggest that as a minimum is because if for instance you cherry pick something, that breaks the build, you'll need to revert that pick and re build. It could be a very time consuming process.
[Galaxy Note GT-N7000 Android Development] happiboi:
This is great~!

i'm going to have to try this out haha... ubuntu in a VM environment on an i7 + 256gb ssd

hope you're up for questions guys haha :silly:
[Galaxy Note GT-N7000 Android Development] chasmodo:
Of course we are up for questions, that's why this thread is here.
[Galaxy Note GT-N7000 Android Development] Galaxtus:
Excellent Article.

Hmmmm now where did i keep my Computer
[Galaxy Note GT-N7000 Android Development] teraxul:
Odp: [HOWTO] Build CM10.1 for N7000

Thanks for tutorial Chas :)

Wysłane z mojego GT-N7000 za pomocą Tapatalk 2
[Galaxy Note GT-N7000 Android Development] ukicar:
great thing ... short, precise .... Keep it up Chas
[Android Q&A, Help & Troubleshooting] tamer92:
hey

i donno if this is the right place to post this thread,

but i really have a big problem

i have dropped my xperia s on the floor yesterday

after almost two hours

the device made a restart

then turned off

it's dead till now

i tried to start the phone with (volume up) button pressed

it vibrates, flashes, the sony logo appears, then xperia logo appears, then it make a restart automatically

also it sometimes make a restart when the sony logo appears

it still restarts till it die with the white bar still on

even if i put it on charge, it can't charge

the red led lights, but it doesn't charge

plz help me plz :(
[Android Q&A, Help & Troubleshooting] SammiSaysHello:
your question should've been asked here :p but nevertheless, it seems to be a bootloop, so try flashing a generic firmware with flashtool and see if the issue persists :) You can learn everything about that in the forum I linked
[Nexus 7 Q&A, Help & Troubleshooting] sophism:
I unlocked then rooted my nexus 7 8GB. Mainly to access external storage. This I achieved and with stickmount was able to achieve the objective, reading from a usb stick.

I felt at the time that there was something wrong as installed app Titanium backup pro - but could never find it. though google still tells me it is installed.

Rom manager states I have ClockworkMod 6.0.1.0 & that 6.0.2.3 is available BUT after dowloading "Flash ClockworkMod Recovery" an error occures.

I installed root checker pro. It advises that not rooted properly although busybox is installed correctly. Reports attached

I have both superuser installed at original root. Since also installed Super su, neither will install binary code.

Is there anything I can do to ensure I am rooted and stay that way?

Thanks for any help offered.
[Nexus 7 Q&A, Help & Troubleshooting] xxxo:
Easiest thing to do boot into recovery, make a backup always,do a wipe flash a custom ROM plenty out there
[Nexus 7 Q&A, Help & Troubleshooting] Saturny:
You may have lost your root, so try to reroot. As for keeping root, DL Voodoo OTA RootKepper from the Play Store. Works like a charm.
[T-Mobile LG G2x] Yuvin:
So, recently, I've been having problems with my headphone jack. Issue is that the audio is all distorted and it sounds like some very bad surround sound setup. I've already tried switching roms and using different headphones. The problem is probably in the Jack itself. If I hold my headphone jack at the correct position with the right amount of pressure on it, the music comes out as it should. I've also tried blowing it out, still noting. What do you guys think I should do? I've seen some links on ebay for headphone jacks going around 20 dollars. I don't even know if it's worth it to repair my G2X as it also has a cracked digitizer.
[T-Mobile LG G2x] SpaceRanger69:
if it's pressure related (and I don't know if it's possible), but have you checked the solder-joints where the jack is mounted to the pcb?
[T-Mobile LG G2x] mansa_noob:
Or clean the Jack with some compressed air.
[T-Mobile LG G2x] Yuvin:
Thanks for the suggestions guys. I did try cleaning the jack with Compressed air already and nothing changed. I'm going to guess it's something wrong with the solder joins. I ordered a new Headphone Jack and power button combination and also a new digitizer from eBay. Hopefully, they'll arrive and I can replace that part. Thank god the Headphone port isn't mounted to the motherboard of this phone! Atleast LG knows how to build a phone well (Except for the screen bleeding) :P
[Kindle Fire Q&A, Help & Troubleshooting] petemess95:
I was following a youtube tutorial to rooting my Fire, when the damn thing got stuck in the boot loop. I have a factory cable, but I still can't seem to figure out how to fix it. When I go through ADB and type "adb devices" all it says is "Listing Devices" or something like that and nothing else comes up. It shows in the device manager as "Android ADB Device" and has the correct hardware IDs. I found somebody with a similar problem in this post http://xdaforums.com/showthread.php?t=1660636 but I followed the steps to solve it exactly as he posted them and they all seemed to work, but at the end it never booted up, and just stayed at the Kindle Fire logo.

This is really getting frustrating because nothing I try seems to work. If you can, please show me toward the steps that I need to take to fix this. If you need any other information, just ask. I hope this doesn't have an obvious answer!
[Kindle Fire Q&A, Help & Troubleshooting] Vlasp:
Is the logo blue or orange? Blue is fff and you can go to twrp and wipe everything, then mount and install a Eton. Otherwise you are in fast boot and you can flash a recovery and fff. You can pm me for Questions.

Devices:

Kindle Fire with AlienDroid primary and Modaco secondary
[HTC Rezound] jski711:
Just looking for a review. I have been flashing ROMs and making backups like crazy so if this makes it easier I might spend the money. All these new ROMs to choose from! Damn devs! LOL (just clarifying that was a joke!)

Thanks!!
[HTC Rezound] jtwebfusion:
I use it. It's like having kernel tuner and titanium backup in one app.
[HTC Rezound] ktdt00:
I bought it and have used it off/on for about 6 months. I always end up going back to discreet apps (SetCPU, AdFree, Amon-Ra vs CWM, Uninstaller, TiBu, etc.). Rom ToolBox does a lot of stuff and most of it pretty well. But the discreet apps, at least to me, usually do it better or simpler.
[HTC Rezound] chupajr:
I don't use the pro version but I love it anyway. I only recently realized you could use it to queue up flashables like in ROM Manager, which alone makes it worthwhile to me. Nothing like being able to create a backup, wipe, and flash multiple zips without having to do a thing in Recovery!
[HTC Rezound] saintsfan09:
Imo it's a must have app if u have a rooted device. It does literally everything. What doesn't it do?
[Motorola Droid RAZR] heleonardman:
I have the maxx, and for the last few months my sim card pops itself out of its holder, and my phone flips out and looses signal and says no sim card inserted. It has gotten so bad that I have to keep an otter box case on it to hold the sim door shut. I am rooted and rom'md, and I bought it last June so I do not know what my options/fixes are. Has anyone had this problem before? Should I just unroot/return to stock and try to get a new maxx? I do not have the money for a new phone and my upgrade is late this year...opinions? Thanks guys.

Sent from my Motorola Galaxy s3
[Motorola Droid RAZR] m.sasti:
Just replace it if it's on a warranty. It's a mechanical problem, it shouldn't be a problem even if you return it rooted or with a custom rom. (depending on the terms of the warranty and where you live)
[Motorola Droid RAZR] Draxin:
Have you stuck someone elses Sim card in and seen if it stays? It should lock in like the sd card, so i would check with a different Sim card first, maybe your cards tab is worn out.
[Motorola Droid RAZR] heleonardman:
I guess I'll call *611 tonight and see if I can send it in for a replacement, I would like to start on a fresh phone anyways. Thanks guys, I was thinking super glue the sim card in there but then I thought again...
[Verizon Samsung Galaxy S III] amazin1988:
I'm looking for a rom that is pretty stock with a lot of 4.2.1 features I've tried one but didn't really like it and still getting used to flashing anyone know a rom that fits this profile

iTzAmazed
[Verizon Samsung Galaxy S III] mapatton82:
For stock I know h3llsrom 1.22 is a stripped down stock rom with 4.2.1 apps.

http://xdaforums.com/showthread.php?t=2102168
[Verizon Samsung Galaxy S III] Nnyan:
Wrong forum for general questions.
[Verizon Samsung Galaxy S III] RCOVA:
Holy crap... There's a lot of posting in wrong forums lately..
[Verizon Samsung Galaxy S III] droidxxxxx:
Yeah I got my ass spanked for it once.. I'm sure Kenny or somebody will move it lol

Sent from my S3 on Unlimited Data from Verizon..yeah boy...

Running Beans Build 8, Lean Kernal vers. 1.4, rpm and modem..rock solid
[Samsung Epic 4G Touch] garwynn:
For most folks you probably won't even want to read this.

For devs wanting this information I figured it wouldn't hurt to have it.

I'm trying to find a way to easily port Agat's modifications to Sprint FL24 kernel source over to Virgin and Boost's versions. But in order to really do it right you need to know what is different between each one.

That's what these files are.

Each file is titled "Diff<A>to<B>" to tell you which is A and which is B.

I cut out what "fat" I could to give only the raw changes between each.

One interesting note is the way includes are handled in Boost versus Virgin.

Hope this will help devs out for future possible support of all 3:

Sources compared:

Sprint FL24

Boost FL24

Virgin FL26

Sprint to Boost Comparison

Sprint to Virgin Comparison

Boost to Virgin Comparison
[Samsung Epic 4G Touch] cerj:
Incredible, Im sure this will help many
[HTC One V] jmandawg:
[YOUTUBE]xsHeSVcs9jQ[/YOUTUBE]

I made the audio file have a really low volume because the stock One V rom likes to blast it's boot sound at full volume.

This is only tested on stock rooted virgin mobile rom.

1. Backup your old files if you want to revert.

2. Copy both files to /system/customize/resource/

3. chmod 644.

4. reboot

DOWNLOADS:

boot animation

http://www.mediafire.com/?g5o06oni04b5sw0

Sound File:

http://www.mediafire.com/?ztu3umykf2tniz9
[HTC One V] cybervibin:
Ohh will try on cm