{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Paranoid Android 3+
Device: JFLTEATT
WARNING
Flash at your own risk! I am NOT responsible for bricks!
Keep the forum on topic please, no trash talking, trolling, or talking of other ROMS.
INSTRUCTIONS
Wipe device
Wipe Cache & Dalvik
Install ROM
Install Paranoid GApps Package http://goo.im/devs/paranoidandroid/roms/gapps
Reboot
DOWNLOAD LINK
(BUILDING - coming soon)
chaosclarity said:
Building as I type this! Once it's done, I'll post it up. Then, mods can move this over to the dev section.
Click to expand...
Click to collapse
Looking forward to it.. I like some of the touchwiz features hence still being on a touchwiz ROM but I used PA3+ on my note 2 and would love to give it a shot on this
Sent from my WICKED AT&T S4 i337
Sync is taking a bit.. probably won't get build done until morning at this rate.
excited
chaosclarity said:
Sync is taking a bit.. probably won't get build done until morning at this rate.
Click to expand...
Click to collapse
hey brother i am excited to see it i am using cyanogenmod and i like it but i like the idea of the options you put in it .... would halo be available for this
Yeah is halo an option for this? I know the source isn't released but could you port it over from another phone that has halos already. Thanks
Sent from my SGH-1337 using Tapatalk 4 Beta
Sweet. Been waiting for this.
Hit a snag.. any devs care to chime in on this one?
Code:
Building ParanoidAndroid v3.56
Looking for device files
Device tree found. Skipping step.
Setting up environment
including device/generic/armv7-a-neon/vendorsetup.sh
including device/generic/armv7-a/vendorsetup.sh
including device/samsung/jfltetmo/vendorsetup.sh
including device/ti/panda/vendorsetup.sh
including vendor/cm/vendorsetup.sh
including vendor/pa/vendorsetup.sh
including sdk/bash_completion/adb.bash
Lunching device
build/core/product_config.mk:209: *** No matches for product "pa_jfltetmo". Stop.
Device jfltetmo not found. Attempting to retrieve device repository from CyanogenMod Github ().
Found repository: android_device_samsung_jfltetmo
CyanogenMod/android_device_samsung_jfltetmo already exists
Syncing repository to retrieve project.
fatal: Couldn't find remote ref refs/heads/jellybean
fatal: Couldn't find remote ref refs/heads/jellybean
error: Cannot fetch CyanogenMod/android_device_samsung_jfltetmo
error: Exited sync due to fetch errors
Repository synced!
Looking for dependencies
Done
build/core/product_config.mk:209: *** No matches for product "pa_jfltetmo". Stop.
** Don't have a product spec for: 'pa_jfltetmo'
** Do you have the right repo manifest?
Starting compilation
build/envsetup.sh: line 1666: schedtool: command not found
Total time elapsed: 1 minutes (102.701881915 seconds)
Try make clean/clobber and try building again see if it gives the same output
It seems there's no device tree for the galaxy s4 official?
jetlitheone said:
It seems there's no device tree for the galaxy s4 official?
Click to expand...
Click to collapse
I had to clobber something up.. but you're right it's a bit sketchy at the moment.
I used a few device tree sources I found from the i9505 section on this forum - all are hosted on CyanogenMod's Github from his Tmobile build. It *should* work.. but at the moment it's a bit of a mess.
chaosclarity said:
I had to clobber something up.. but you're right it's a bit sketchy at the moment.
I used a few device tree sources I found from the i9505 section on this forum - all are hosted on CyanogenMod's Github from his Tmobile build. It *should* work.. but at the moment it's a bit of a mess.
Click to expand...
Click to collapse
Looks like CM has jflteatt up.. will go at it again tonight.
Resyncing currently.. hope it builds later! :laugh:
chaosclarity said:
Resyncing currently.. hope it builds later! :laugh:
Click to expand...
Click to collapse
How long will that take?
Maybe I'll help out if you want.
Do you need a fast PC for this?
I'm getting tired:
Code:
Building ParanoidAndroid v3.50
Looking for device files
Device tree found. Skipping step.
Setting up environment
including device/generic/armv7-a-neon/vendorsetup.sh
including device/generic/armv7-a/vendorsetup.sh
including device/samsung/jflteatt/vendorsetup.sh
including device/samsung/jfltetmo/vendorsetup.sh
including device/ti/panda/vendorsetup.sh
including vendor/cm/vendorsetup.sh
including vendor/pa/vendorsetup.sh
including sdk/bash_completion/adb.bash
Lunching device
Looking for dependencies
============================================
PLATFORM_VERSION_CODENAME=REL
PLATFORM_VERSION=4.1.2
TARGET_PRODUCT=pa_jflteatt
TARGET_BUILD_VARIANT=userdebug
TARGET_BUILD_TYPE=release
TARGET_BUILD_APPS=
TARGET_ARCH=arm
TARGET_ARCH_VARIANT=armv7-a-neon
HOST_ARCH=x86
HOST_OS=linux
HOST_OS_EXTRA=Linux-3.5.0-17-generic-x86_64-with-Ubuntu-12.10-quantal
HOST_BUILD_TYPE=release
BUILD_ID=JZO54K
OUT_DIR=/home/kaschenberg/android/system/out
============================================
Starting compilation
============================================
PLATFORM_VERSION_CODENAME=REL
PLATFORM_VERSION=4.1.2
TARGET_PRODUCT=pa_jflteatt
TARGET_BUILD_VARIANT=userdebug
TARGET_BUILD_TYPE=release
TARGET_BUILD_APPS=
TARGET_ARCH=arm
TARGET_ARCH_VARIANT=armv7-a-neon
HOST_ARCH=x86
HOST_OS=linux
HOST_OS_EXTRA=Linux-3.5.0-17-generic-x86_64-with-Ubuntu-12.10-quantal
HOST_BUILD_TYPE=release
BUILD_ID=JZO54K
OUT_DIR=/home/kaschenberg/android/system/out
============================================
build/core/binary.mk:11: *** external/bzip2: LOCAL_NDK_VERSION is now retired.. Stop.
WTF!?
Found the issue probably - no build tonight guys.
Resyncing again...
Finally, it's building. Goodnight!
cant wait no rush
By the way guys, there's no halos that's not open source yet.
What's the verdict Chaos? Been itching all day to try this out after seeing it reviewed on the S3 =3
Sent via the Bacon Powered GS4
Related
Anyone have any information as to where I can go to learn how to build/compile a kernel for my nexus s 4g? Id like to take a feeble stab at it. Thanks!
Here are some guides I used for getting started:
» [How-To] compile the Nexus S kernel from source
» [HOW-TO] Compile AOSP Gingerbread + [ROM] Master AOSP
» Building Kernel from source - CyanogenMod Wiki
Please note that most of the time you cannot just follow the guides verbatim. Just use it as "guidelines" and adapt it to suit your development environment.
Also you should have basic to moderate understanding in Git in order to apply patches/mods to your kernel properly.
Thanks. Almost easier to pay someone, what with being lazy and all.
Yeah, that's what I do now -- using a "tried and tested by community" kernel/ROM is much easier for life.
I think there are enough kernel threads in XDA that you should find one that suits your needs, and you can send a donation to the developer to show you appreciation in his/her work
There are quite a few, yes. Although I want a 'feature from this kernel and a tweak from that kernel'...or 'Id use this one if it didnt have that feature'...so I just sit at stock...
Lol, sounds like a "walk in the middle path" philosophy
That's a good decision though, nowadays instead of spending time compiling my own kernel, I spend as much time in checking the Development forum -- looking for new kernel(s) update everyday. It's kinda addict once you've tried flashing them
Hey Tails,
I am trying to take a stab at compiling my own kernel too. How did it go for you? I am having problems myself.
Sent from my Google Nexus S using Tapatalk
suomaf said:
Hey Tails,
I am trying to take a stab at compiling my own kernel too. How did it go for you? I am having problems myself.
Sent from my Google Nexus S using Tapatalk
Click to expand...
Click to collapse
I completely abandoned my attempts at building kernels. Sorry.
I'll leave it to the vets
Sent from my Nexus S 4G using xda premium
I would also like to give it a go, wonder if there is anyone that can give me advice. I have sync repo but can not for the life of me find where the new kernel sources are.
Sent from my A500 using Tapatalk
suomaf said:
I would sol like to give it a go, winner if there is anyone that can give me advice. I have sync repo but can not for the life of me find where the new kernel sources are.
Sent from my A500 using Tapatalk
Click to expand...
Click to collapse
May be here?
suksit said:
May be here?
Click to expand...
Click to collapse
Thanks for the quick reply, I think I have repo sync'd and also done
Code:
git clone https://android.googlesource.com/kernel/samsung.git
But I end up with an empty directory called samsung with a hidden directory .repo
Is this correct? Is the 3.0 kernel for nexus s somewhere else?
Well I haven't update the kernel sources since kernel.org was down... However, I think this may also be a good starting point.
suksit said:
Well I haven't update the kernel sources since kernel.org was down... However, I think this may also be a good starting point.
Click to expand...
Click to collapse
Thank you very much, will try to git clone https://bitbucket.org/KalimochoAz/samsung-kernel-3.git
---------- Post added at 11:15 AM ---------- Previous post was at 11:01 AM ----------
sigh.. this is hard,
Code:
git clone https://bitbucket.org/KalimochoAz/samsung-kernel-3.git
Cloning into samsung-kernel-3...
error: RPC failed; result=22, HTTP code = 502
fatal: The remote end hung up unexpectedly
I am guessing maybe the server is down or something? because git clone worked for me when testing
git clone git://github.com/git/hello-world.git
suomaf said:
Thanks for the quick reply, I think I have repo sync'd and also done
Code:
git clone https://android.googlesource.com/kernel/samsung.git
But I end up with an empty directory called samsung with a hidden directory .repo
Is this correct? Is the 3.0 kernel for nexus s somewhere else?
Click to expand...
Click to collapse
Just finished cloning samsung.git from googlesource. I suppose the directory name should be .git? If so, from within samsung directory, type the following command:
Code:
git branch -a
This will list all branches in the repository. You should see something like this:
Code:
* master
remotes/origin/HEAD -> origin/master
remotes/origin/android-samsung-2.6.35-gingerbread
remotes/origin/android-samsung-3.0-ics-mr1
remotes/origin/master
If you want the kernel code for ICS (linux 3.0), type the following command:
Code:
git checkout android-samsung-3.0-ics-mr1
This will checkout the code from the corresponding branch name. If things go well, you should see something like this:
Code:
Checking out files: 100% (37465/37465), done.
Branch android-samsung-3.0-ics-mr1 set up to track remote branch android-samsung-3.0-ics-mr1 from origin.
Switched to a new branch 'android-samsung-3.0-ics-mr1'
Git will create a new local branch for you. To see it, just type git branch -a again.
Now it's time to play!
thanks boss,
Really appreciate you taking the time to do this, it was successful. Here I go to brick my nexus S
suomaf said:
thanks boss,
Really appreciate you taking the time to do this, it was successful. Here I go to brick my nexus S
Click to expand...
Click to collapse
lol
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
No bricks so far, but has not been able to get the phone to boot. Did what I think is a default compile then took the ram disk from the phone. The damn thing just wont boot. Does this mean that I will have to compile the whole ics and use that ram disk? or am I just doing it wrong?
suomaf said:
No bricks so far, but has not been able to get the phone to boot. Did what I think is a default compile then took the ram disk from the phone. The damn thing just wont boot. Does this mean that I will have to compile the whole ics and use that ram disk? or am I just doing it wrong?
Click to expand...
Click to collapse
That sounds correct to me. However, I haven't done this for almost a year so I'll just try to recall from my memory =.= Usually the steps should be:
get the boot partition from the phone using dd?
use extract-bootimg.pl to extract the ramdisk
use mkbootimg to create a new boot image from the extracted ramdisk and your zImage
try it with fastboot boot newbootimage.img
Sorry that I couldn't be of more help
You have been great help. Thanks.
Sent from my Google Nexus S using Tapatalk
Just think about another way to do it: AnyKernel
BTW, it's my pleasure helping ppl to brick their phone lol
I wanted to get the ball rolling on getting a working AOSP 4.1 ROM built. So far i was able to get it to compile but i cannot get it to boot or get adb working. I need help on this one so lets all work together and get this working! :laugh:
The majority of the compile errors were gps related so i have disabled the building of gps in the device tree for now as that is not important to get a booting build. If you follow these instructions you will be able to build without any errors. But the end product still will not boot. but its close.
Here is how to download the 4.1 AOSP repo (straight from the android source website):
Code:
$ mkdir ~/bin
$ PATH=~/bin:$PATH
$ curl https://dl-ssl.google.com/dl/googlesource/git-repo/repo > ~/bin/repo
$ chmod a+x ~/bin/repo
$ mkdir WORKING_DIRECTORY
$ cd WORKING_DIRECTORY
$ repo init -u https://android.googlesource.com/platform/manifest
$ repo init -u https://android.googlesource.com/platform/manifest -b android-4.1.1_r1
$ repo sync -j16 (this will take about and hour and a half depending on your interwebs speed)
then download the device trees and proprietary files from here:
Code:
$ cd WORKING_DIRECTORY
$ git clone https://github.com/sk8erwitskil/aosp-android_device_samsung_skyrocket.git device/samsung/skyrocket/
$ git clone https://github.com/sk8erwitskil/aosp-android_device_samsung_msm8660-common.git device/samsung/msm8660-common/
$ git clone https://github.com/sk8erwitskil/android_vendor_samsung_skyrocket.git vendor/samsung/skyrocket/
then:
Code:
$ . build/envsetup.sh (notice the period)
$ lunch full_skyrocket-userdebug
$ make -j(number of CPUs/threads +1) otapackage
i have 2 cpus with 2 cores and multi threaded so i do -j9
2(cpus) x 2(cores each) x2(threads per core) + 1 = 9 (so i do make -j9 otapackage)
i got one to completely compile but i cannot get it to boot. i had to edit the updater-script to get it to even install. if you do get one compiled make sure to delete all the lines that have to do with installing recovery from the updater-script. you dont want to overwrite your recovery. and delete the folder "recovery" from inside the finished zip file. i already did that in this one:
JELLYBEAN 4.1 AOSP (NOT BOOTING YET)
Click to expand...
Click to collapse
Click to expand...
Click to collapse
not booting rom is still uploading. should be done in about 5 mins
edit: finished uploading
cant wait to see the progress on this very excited thanks
Getting the ball rolling my friend? Good luck
Get hold of Seanzscreams. His Alpha was not booting yet, but he had adb working. We were doing logcats and dmesg's on it. A bit of advice from him on getting adb going might help you along a bit quicker.
rebel1699 said:
Get hold of Seanzscreams. His Alpha was not booting yet, but he had adb working. We were doing logcats and dmesg's on it. A bit of advice from him on getting adb going might help you along a bit quicker.
Click to expand...
Click to collapse
I am in NO way trying to disrespect anyone, and have no idea how to development process works. But why does it seem like there are small groups of people trying to get their own versions to boot. Why not collaborate until there's at least a solid base, then branch off?
I am going to start playing with it too, maybe I will figure something out but probably not
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
doood amazing
editing the cm.mk
and vendor.sh
was my hinderence
thanks compiling a build now as well
sk8erwitskil said:
not booting rom is still uploading. should be done in about 5 mins
Click to expand...
Click to collapse
also have you tried bringing over the android runtime lib
and also in egl.conf changing it to 0 1android and 0 0 adreno
seanzscreams said:
also have you tried bringing over the android runtime lib
and also in egl.conf changing it to 0 1android and 0 0 adreno
Click to expand...
Click to collapse
i have not edited any of the libs yet. i have only had time to get the compile done and edited the updater-script to get it to install. i will try this tho and see how much further into the boot process i can get. thanks
oh btw, how did you get adb to start. were there changes to init.rc that you had to make?
Compiled and adb is running
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I brought over only a few specific lines. Not replacing any. When I compared them side by side
And included init.trace
Thanks for like 5 tips in the op that got me going I was up all damn night. But. Changing full skyrocket user debug. Worked. Ahhh
So close now
Using my own compile. But. Will def give props for this guide
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
Good to see there's a few people working on a jb port. More people=sooner releases and more roms. Thanks.
Sent from my SGH-I727 using XDA
Great news... CAF (code aurora forums) just updated their github with new Jellybean sources, and our own msm8660 processor is among them. Same stuff I used for my port of ICS. https://www.codeaurora.org/xwiki/bin/QAEP/jb
This is what we need to compile and build from; as it's actually designed for our processor it will be much easier in getting a stable jellybean build up and running.
jomeister15 said:
Great news... CAF (code aurora forums) just updated their github with new Jellybean sources, and our own msm8660 processor is among them. Same stuff I used for my port of ICS. https://www.codeaurora.org/xwiki/bin/QAEP/jb
This is what we need to compile and build from; as it's actually designed for our processor it will be much easier in getting a stable jellybean build up and running.
Click to expand...
Click to collapse
Thanks limited, but <3
jomeister15 said:
Great news... CAF (code aurora forums) just updated their github with new Jellybean sources, and our own msm8660 processor is among them. Same stuff I used for my port of ICS. https://www.codeaurora.org/xwiki/bin/QAEP/jb
This is what we need to compile and build from; as it's actually designed for our processor it will be much easier in getting a stable jellybean build up and running.
Click to expand...
Click to collapse
thanks. dl'ing now
edit: looks like codeaurora has kernel in it as well??
sk8erwitskil said:
thanks. dl'ing now
edit: looks like codeaurora has kernel in it as well??
Click to expand...
Click to collapse
I think it's safe to say that you guys will have a working ROM fairly soon. Keep this up and you'll have something up and running in week
"error: Cannot fetch platform/external/webkit"
thats from the codeaurora repo. ugh. it hangs
Glorious work y'all
Sent from my SGH-T989 using xda app-developers app
Just wanted to personally say thank you, Sk8er for reaching out, if more devs did that then there probably wouldn't be so many questions killing these forums for everyone.
Keep up the awesome work and i will do anything i can to help. you guys rock!
Sent from my i727 DÅÅTH machine
sk8erwitskil said:
thanks. dl'ing now
edit: looks like codeaurora has kernel in it as well??
Click to expand...
Click to collapse
The kernel will need to be replaced by a modified ICS one. I'd get downloading on the source but I currently don't have access to my linux machine.
Welcome To CyanogenMod 7
Source Compilation Guide
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Hello Folks, This Guide is about Compiling CyanogenMod 7 From Source For Galaxy Fit (Beni) .
This is my small attempt to Motivate everyone In Compiling Android . I HATE Porting
Click to expand...
Click to collapse
Remember, I'm NOT responsible if something, or anything goes wrong at your end, on any device or system.
Requirements:
Ubuntu Box (Computer) 12.04 (64-Bit) (Recommended)
At least 2.5 Gig core2duo Processor & 2GB RAM
Stable Internet Connection (Atleast 1Mbps)
30Gb Hdd space
Device running latest CM7
Useable Brain
Basic Computer Knowledge
Lot of Patience
Installing some packages:
Open Terminal(Ctrl+Alt+T)
Code:
sudo apt-get install git-core gnupg flex bison gperf libsdl1.2-dev libesd0-dev libwxgtk2.6-dev squashfs-tools build-essential zip curl libncurses5-dev zlib1g-dev sun-java6-jdk pngcrush schedtool
Install Oracle Java 6 JDK Using This Guide
Install Android SDK Using This Guide
Install Android Debug Beidge (ADB) Using This Guide
Make two folders in home directory bin & android.
Code:
curl https://dl-ssl.google.com/dl/googlesource/git-repo/repo > ~/bin/repo
Make the repo command executable:
Type:
Code:
chmod a+x ~/bin/repo
You may need to reboot for the changes to take place.(Recommended)
Downloading the source:
cd to android folder
Code:
cd ~/android
Code:
repo init -u git://github.com/CyanogenMod/android.git -b gingerbread --repo-url=git://github.com/android/tools_repo.git
Code:
repo sync
If u have good internet connection. Do repo sync -jn (n= Number of simultaneous downloads)
P.S You can download Compressed CyanogenMod 7 Source (Thanks To Keyur2Maru)
Download Device Config and extract it to android/device/samsung/beni (Thanks to tj_style)
Copying of the Proprietary files from Fit running CyanogenMod 7
Connect the device and ensure ADB is working.Type the following for copying:
Code:
cd ~/android/device/samsung/beni/
Code:
./extract-files.sh
Downloading ROM Manager (I hate ROM manager like anything)
Code:
~/android/system/vendor/cyanogen/get-rommanager
Compiling CyanogenMod 7
Code:
cd ~/android/
Code:
. build/envsetup.sh && brunch beni
It will take 70-75mins to compile depending upon your system . After finishing you will get .zip file from ~/android/out/target/product/beni/update.cm-XXXXX-signed.zip. Extract it and delete recovery folder inside it. Make .zip file and flash it via CWM
Thanks & Credits:
Guys Please Press Thanks To Them Too
#My Best Friends (For Inspiring Me)
#My Father (For Giving Me G-Fit)
#Google (For Wonderful Android)
#Speed_bot (For Helping Me Always)
#Wilfredcool007 (For Helping Me Always)
#Tj_Styles(For CWM)
#Feras.Rahman
#xda(For The Platform)
#Me( For The Efforts )
P.S: This Guide is just for reference, Don't Spam the development section
Sry for being noob but if we dual boot ubuntu with windows...can we compile with ubuntu then???
Sent from my GT-S5570 using xda premium
ya
droider007 said:
Sry for being noob but if we dual boot ubuntu with windows...can we compile with ubuntu then???
Sent from my GT-S5570 using xda premium
Click to expand...
Click to collapse
Yup..why not
Superb guide remove that vendors extraction part as you have already linked it to my git..just a suggestion..
AND GUYS ANY BUILD ERRORS FEEL FREE TO POST HERE
http://forum.xda-developers.com/showthread.php?t=2059939
I WILL BE HAPPY TO REPLY
---------- Post added at 11:31 PM ---------- Previous post was at 11:28 PM ----------
Path to the vendors extraction is wrong check it bro..
speed_bot said:
Superb guide remove that vendors extraction part as you have already linked it to my git..just a suggestion..
AND GUYS ANY BUILD ERRORS FEEL FREE TO POST HERE
http://forum.xda-developers.com/showthread.php?t=2059939
I WILL BE HAPPY TO REPLY
---------- Post added at 11:31 PM ---------- Previous post was at 11:28 PM ----------
Path to the vendors extraction is wrong check it bro..
Click to expand...
Click to collapse
Ya done. was about to link ur thread for errors
superb work rishabh !
:thumbup:
Sent from my GT-S5670 using xda premium
soham jambhekar said:
superb work rishabh !
:thumbup:
Sent from my GT-S5670 using xda premium
Click to expand...
Click to collapse
Thank u so much
I'm surprised... in other guides made me go back to ubuntu 11.10 cause they said that 12.04 was not supported for compiling
Shall I move other time to 11.10???
Thank you for the super guide!!!
Sorry for my eng
Sent from my GT-S6500D using Tapatalk 2
manu19thebest said:
I'm surprised... in other guides made me go back to ubuntu 11.10 cause they said that 12.04 was not supported for compiling
Shall I move other time to 11.10???
Thank you for the super guide!!!
Sorry for my eng
Sent from my GT-S6500D using Tapatalk 2
Click to expand...
Click to collapse
Compiling isn't specific for one distribution. It can be done on any Linux based os which has all required packages
You Can also compile on MacOS!
Sent from my C2104 using XDA Premium 4 mobile app
I cannot download compressed cm7 source.. It asks for a password and username... Can someone help me?
mathm2013 said:
I cannot download compressed cm7 source.. It asks for a password and username... Can someone help me?
Click to expand...
Click to collapse
post a request on this thread
http://forum.xda-developers.com/showthread.php?t=1876035
mathm2013 said:
I cannot download compressed cm7 source.. It asks for a password and username... Can someone help me?
Click to expand...
Click to collapse
Enjoy!
http://forum.xda-developers.com/showthread.php?t=1876035
Sent from my C2104 using XDA Premium 4 mobile app
gt6802
Hello, I'm a newbie, could these same steps also be used to compile CM7 for samsung gt 6802?
Code:
. build/envsetup.sh && brunch s5670
including device/motorola/jordan-common/vendorsetup.sh
including device/samsung/beni/vendorsetup.sh
including device/samsung/s5670/vendorsetup.sh
including vendor/cyanogen/vendorsetup.sh
including vendor/cyanogen/vendorsetup.sh
============================================
PLATFORM_VERSION_CODENAME=REL
PLATFORM_VERSION=2.3.7
TARGET_PRODUCT=cyanogen_s5670
TARGET_BUILD_VARIANT=eng
TARGET_SIMULATOR=false
TARGET_BUILD_TYPE=release
TARGET_BUILD_APPS=
TARGET_ARCH=arm
TARGET_ARCH_VARIANT=armv6-vfp
HOST_ARCH=x86
HOST_OS=linux
HOST_BUILD_TYPE=release
BUILD_ID=GINGERBREAD
============================================
make: *** No rule to make target `bacon'. Stop.
System: Ubuntu-14.04 32-bit
Harpratap said:
Code:
. build/envsetup.sh && brunch s5670
including device/motorola/jordan-common/vendorsetup.sh
including device/samsung/beni/vendorsetup.sh
including device/samsung/s5670/vendorsetup.sh
including vendor/cyanogen/vendorsetup.sh
including vendor/cyanogen/vendorsetup.sh
============================================
PLATFORM_VERSION_CODENAME=REL
PLATFORM_VERSION=2.3.7
TARGET_PRODUCT=cyanogen_s5670
TARGET_BUILD_VARIANT=eng
TARGET_SIMULATOR=false
TARGET_BUILD_TYPE=release
TARGET_BUILD_APPS=
TARGET_ARCH=arm
TARGET_ARCH_VARIANT=armv6-vfp
HOST_ARCH=x86
HOST_OS=linux
HOST_BUILD_TYPE=release
BUILD_ID=GINGERBREAD
============================================
make: *** No rule to make target `bacon'. Stop.
System: Ubuntu-14.04 32-bit
Click to expand...
Click to collapse
Which Device tree did you use?
Sent from my C1905 using XDA Premium 4 mobile app
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Application for Github Tutorial
Introduction:
Hi,
This is an application developed for helping people with github who are especially new to it.
Features:
1.Basic section where all the basics of github is presented.
2.Intermediate section.
3.Advance section.
4.You can take test in the "Judge your learning section"
Note:
If you have any suggestions/queries then you can send me a mail ( [email protected] ).
And Press the back button to go to navigation menu after you open the app.
Download link:
Github tutorial with Ads
Github tutorial without Ads
Source
Credits:
@major190 for helping me with some app issues and motivation. good person
XDA:DevDB Information
Github Tutorial, App for all devices (see above for details)
Contributors
Vivek_Neel
Version Information
Status: Stable
Current Stable Version: 1
Stable Release Date: 2014-12-16
Created 2014-12-16
Last Updated 2015-01-01
Awesome Brother
Love Your Work
And my bro just started with git
Awesome work bro!
Thanks
Awesome!
Sent from my BlakKat CM11 powered OnePlus One "BACON"
This is just what I needed.
And another of great work
Good job! It looks really good :good:
Finally. Simply awesome
Can any body upload the app to Attachments please
Thanks for the app
Upload kernel, vendor and device tree.
Nice im going to try this app. I normall see guide that tell the basic stuff. Those guides and in how easy it is to upload the device tree files to master on github. And they tell how to add ore remove some files I get that.!
I have a device tree in master that is cm9. I want to upload a nother device tree to cm 10.2 and 11 using the terminal.
Here is my github: https://github.com/Frank77GLD/android_device_YG_m805_892x
For now i used a option in github to copy the cm9 project files to the cm10.2 github tree. I did have to change most files in cm10.2
My cm11 device tree is still empty. What should be the right way to upload my cm11 project files to the cm11 device tree?
This year i made a github with kernel files. 1 with vendor files and a device tree. I did have the problem that files got uploaded in the wrong device tree. Vendor files went in the kernel tree and the kernel files wint in like the devie tree. How to logon to the right device tree ore log out ore use the right command in my terminal? Im a bit scared when i upload files that they will go in the wrong device tree. I hope you're app can help out.
Can any one please attach the app because i can't download it From play stre
Thanks for this! Just in time for my in-laws' Christmas party. Something to read and learn while everyone else has fun. This is something that I have looking for.
Just to let you know you guys. This app has been featured on xda headlines.
http://www.xda-developers.com/android/github-tutorial-app/
Thank you xda
[email protected] said:
Nice im going to try this app. I normall see guide that tell the basic stuff. Those guides and in how easy it is to upload the device tree files to master on github. And they tell how to add ore remove some files I get that.!
I have a device tree in master that is cm9. I want to upload a nother device tree to cm 10.2 and 11 using the terminal.
Here is my github: https://github.com/Frank77GLD/android_device_YG_m805_892x
For now i used a option in github to copy the cm9 project files to the cm10.2 github tree. I did have to change most files in cm10.2
My cm11 device tree is still empty. What should be the right way to upload my cm11 project files to the cm11 device tree?
This year i made a github with kernel files. 1 with vendor files and a device tree. I did have the problem that files got uploaded in the wrong device tree. Vendor files went in the kernel tree and the kernel files wint in like the devie tree. How to logon to the right device tree ore log out ore use the right command in my terminal? Im a bit scared when i upload files that they will go in the wrong device tree. I hope you're app can help out.
Click to expand...
Click to collapse
I will have a look on this
Awesome it can help so much
awesome!!
Thanks muchly for this bro you're simply awesome!
Great Contribution
Awesome work @Vivek_Neel
Keep up the Good work Mate :angel:
Very cool.
Hello everybody,
I have finally completed version 1 of my device tree for our device.
You can find it at
https://github.com/alterbang/android_device_xiaomi_libra
If you have a working CM local source you can lunch && mka otapackage for the glory
A few details:
I forked from xiaomi-dev, xiaobai's testing repo
Copied include folder from https://github.com/CyanogenMod/android_device_xiaomi_cancro
Edited AndroidBoard.mk with an "#alterbang" section with dir creation and patched files copy
Edited BoardConfig.mk with TARGET_SPECIFIC_HEADER_PATH := $(LOCAL_PATH)/include
Added "#alterbang" section with missing files to proprietary-files.txt, and removed a couple files.
BONUS: i have added a script "extract-files-from-miui-zip" to extract files from a miui.zip file (like the roms over at xiaomi.eu) so you can extract them without having to flash miui to your phone
ANY COMMENT OR COLLABORATION IS WELCOME
It's the first time i work actively with CM, so have mercy on me
I created this project because i believe in collaboration and openness, so get your hands dirty!
Thank you!
alterbang
Build 20160129 DOWNLOAD LINK
https://mega.nz/#!wBVlUJ4D!E-TDy01wNqBuLQvbznNfOd6bfkpPvaAcSePWZdlDXbY
-works: everything
-bugs: wakeup is sometimes slow. if you know how to fix, please tell me
Wow, awesome work!!
I'm not a dev, but I build CM 12.1 for klimtlte and CM 13 for mako (before I got my shiny new Mi 4c ...).
Double thumbs-up for your work on the extract-files-from-miui-zip.sh. Have you thought about uploading the files to TheMuppets github? Would make it even easier to build, and aries and cancro are already there.
Also I like that you shared your findings and how you got it to work and what you used to get it to work, much appreciated!! This is the way to do it in my opinion!
I very much like the idea of running my own build on my phone, however I am not sure if I should put too much effort into 12.1 any more with all the nice CM13 roms getting better and better (Team Superluminals cm13 builds work great on my phone) ... I will keep an eye on your github, though, and might ask your for your local manifest in the future
Again, you did great work so far!
Oh, one mroe thing: Whats the state of SELinux with your build? Is it permissive? Or did you or xiobai have an enforcing SELinux working?
Thank you muff99!
As for your question: i saw SELinux permissive removed in the mk files, but i don't know if that's enough. I'll let you know!
For Marshmallow / CM13: the idea is to do the same thing also for that branch
Hey !
Somebody could explain me what are the differences of this version between the Xiaobi one ?
Ty
DFurax said:
Hey !
Somebody could explain me what are the differences of this version between the Xiaobi one ?
Ty
Click to expand...
Click to collapse
You can compile this to yourself, you can take part of the development with this tree.
Sent from my Mi-4c using Tapatalk
Here are non open source binaries :
https://github.com/AndropaX/proprietary_vendor_xiaomi_libra
Pull requests with updates (from dev version please) are welcome.
Wysłane z mojego Mi-4c przy użyciu Tapatalka
Hi,
I'm new in building ROM, so i'm trying to build rom but it seems local_manifest.xml needed ?! Where i can found it?!
Thx in advance
I am trying to put together a cm 13 build, this is how my local manifest looks so far:
Code:
<manifest>
<remote name="ghub" fetch="git://github.com/"/>
<!-- <project name="thune-xiaobai/android_device_xiaomi_libra.git" path="device/xiaomi/libra" remote="ghub" revision="cm-13.0"/>-->
<project name="xiaomi-dev/android_device_xiaomi_libra.git" path="device/xiaomi/libra" remote="ghub" revision="cm-13.0"/>
<project name="CyanogenMod/android_device_qcom_common" path="device/qcom/common" remote="ghub" revision="cm-13.0"/>
<project name="AndropaX/proprietary_vendor_xiaomi_libra" path="vendor/xiaomi/libra" remote="ghub" reviSion="master"/>
...
</manifest>
It seems like Xiaobai is not using his thune-xiaobai Github any more, but he is contributing to xiaomi-dev, so I chose that device tree as did @alterbang.
@dexxa05:
Thnx! You sure the dev roms are a good source? After this locked-bootloader news I am hesitant to use dev rom files ...
Got until this one:
Code:
make: *** No rule to make target `/home/freddi/android/system/out/target/product/libra/obj/KERNEL_OBJ/usr', needed by `/home/freddi/android/system/out/target/product/libra/dt.img'. Stop.
Seems like @alterbang ran into this here:
http://forum.xda-developers.com/mi-...12-1-mi-4c-t3226541/post64204905#post64204905
Which dependencies did you add to fix this?
Oh btw, I dont wanna hijack your cm 12.1 thread to talk about cm 13 ... should I open another thread?
UPDATE: Oh I just saw all the stuff that you did to your device tree in /include, have to work through that ... cancro already has cm13, looks like there is even a kernel source.
that is just a missing dir, search my repo and yes please open a new thread! so we can start together on cm13
Hi Guys,
Small issues i'm trying to build 12.1 but the system try to build 13.0
Code:
============================================
PLATFORM_VERSION_CODENAME=REL
PLATFORM_VERSION=6.0.1
CM_VERSION=13.0-20160119-UNOFFICIAL-libra
TARGET_PRODUCT=cm_libra
TARGET_BUILD_VARIANT=userdebug
TARGET_BUILD_TYPE=release
TARGET_BUILD_APPS=
TARGET_ARCH=arm64
TARGET_ARCH_VARIANT=armv8-a
TARGET_CPU_VARIANT=generic
TARGET_2ND_ARCH=arm
TARGET_2ND_ARCH_VARIANT=armv7-a-neon
TARGET_2ND_CPU_VARIANT=cortex-a53
HOST_ARCH=x86_64
HOST_OS=linux
HOST_OS_EXTRA=Linux-3.2.0-4-amd64-x86_64-with-debian-7.9
HOST_BUILD_TYPE=release
BUILD_ID=MMB29T
OUT_DIR=/home/dexxa05/android/system/out
============================================
Do you know how to change that?!
Thx in advance
dexxa05 said:
Hi Guys,
Small issues i'm trying to build 12.1 but the system try to build 13.0
Do you know how to change that?!
Thx in advance
Click to expand...
Click to collapse
How did you init your repo? You have to do it like this, I guess:
repo init -u https://github.com/CyanogenMod/android.git -b cm-12.1
Also, check the "revision" attribute in your .repo/local_manifests/*.xml files, it should be "revision="cm-12.1" " for you
AndropaX said:
Here are non open source binaries :
https://github.com/AndropaX/proprietary_vendor_xiaomi_libra
Pull requests with updates (from dev version please) are welcome.
Wysłane z mojego Mi-4c przy użyciu Tapatalka
Click to expand...
Click to collapse
Is that from the latest MIUI?
From china dev rom 6.1.11
Wysłane z mojego Mi-4c przy użyciu Tapatalka
Ok, now updated to 16.1.14
Great job AndropaX
Where you got kernel sources for mi4c?
Nowhere, i'm still using a prebuilt kernel...
We're still waiting for Xiaomi to comply to GPL.
And unfortunately nothing seems to indicate that's happening soon.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
sup
Updated the first post with the flashable zip
Is it possible to have the snapdragon camera on cm12.1?