Related
I am Developing an AOSP Froyo build for the Samsung Captivate.
It is being built from the ground up and will be missing many of the
bells and whistles that this community has grown accustom to.
NO samsung or att bloat
although that also means no samsung goodies.
I also won't be including google apps. (this can easily be added in later)
This is not a CM build. although a lot of help comes from that arena.
I feel it would be better to build from a pure AOSP base.
knowing that it was created and fully compatible with the device that
it is being used on.
from there, all the optional extras can be added.
for now it will need to be built from source
here is some reading material for those that don't know how...
http://forum.xda-developers.com/showpost.php?p=6243873&postcount=1
http://help.github.com/
http://www.cmsgs.com/mediawiki/index.php?title=Howto:_Install_the_Android_SDK
http://developer.android.com/sdk/index.html
http://source.android.com/source/index.html
some helpful sources
www.github.com/CyanogenMod
www.github.com/teamhacksung
www.github.com/cmsgs
these are just a few I had immediately available.
IF ANYONE HAS BETTER SUGGESTIONS PLEASE LET ME KNOW AND I WILL ADD IT HERE.
what doesn't work:
cell network...( probably just needed to flash a modem)
wifi...
bluetooth
sdcard (internal & external)
audio
camera
gps
accelerometer/sensors
keymapping incorrect Fixed 4/21/2011
what works:
boots up
most apps that I had installed (I didn't wipe data so it kept all my apps)
live wallpapers
crazy fast graphics (next time I will run some benchmarks to compare)
the dim settings for brightness was a TON dimmer than stock (most likely better on battery)
touchscreen very responsive/accurate.
I am looking for any assistance on this. I have a lot that I plan on doing still but I don't have a lot of time to work on it.
So the more help I get the faster it gets done.
HOW TO BUILD FROYO FOR CAPTIVATE
After reading the reference material above
I use Ubuntu 10.04 32bit at ubuntu.com
10.04 is a LTS release (long term support) so even though there are newer releases I would stick to that one.
you will need java5 NOT 6 so if you have 6 installed already you should uninstall it.
(there is a way to have both at the same time but I don't recall the steps at the moment)
Code:
sudo apt-get install sun-java5-jdk
some extra stuff you will need
Code:
sudo apt-get install git-core gnupg flex bison gperf libsdl-dev libesd0-dev libwxgtk2.6-dev build-essential zip curl libncurses5-dev zlib1g-dev valgrind
make sure you are in your home directory (~/ = home directory)
Code:
cd ~/
create a working directory and go into it
Code:
mkdir mydroid
cd mydroid
copy my repo to your computer
Code:
git clone git://github.com/aosp4captivate/froyo.git
once that is done. (takes a while)
download this captivate_update.zip
and this initramfs.zip
Place the captivate_update.zip in the ~/mydroid/froyo folder.
Extract the initramfs folder from the initramfs.zip into ~/mydroid/froyo/device/samsung/captivate
there seems to be a permissions issue transferring from github
for now here is a quick fix for this
Code:
cd ~/mydroid
chmod -R 777 froyo
go into the captivate folder and run unzip script
Code:
cd ~/mydroid/froyo/device/samsung/captivate
. unzip-files.sh
yes that is a period before unzip-files.sh
now from the froyo directory setup the build
Code:
cd ~/mydroid/froyo
. build/envsetup.sh
lunch
select the captivate build
then
Code:
make -j4
I use 4 because my computer can handle 4 Jobs at once
just leave the -j4 off if you have a slow single processor.
this takes a LOOOOOOOONG time
for me an initial build takes about 1 hour.
subsequent builds are faster.
the result is in ~/mydroid/froyo/out/target/product/captivate
this is just off the top of my head so again
IF YOU HAVE ANY BETTER BUILD INSTRUCTIONS PLEASE LET ME KNOW...
Hey Man before you put all of this work in, why dont you make a gingerbread asop rom. I dont see the point in putting all of this work into an outdated os
bpodz34 said:
Hey Man before you put all of this work in, why dont you make a gingerbread asop rom. I dont see the point in putting all of this work into an outdated os
Click to expand...
Click to collapse
why don't you?
bpodz34 said:
Hey Man before you put all of this work in, why dont you make a gingerbread asop rom. I dont see the point in putting all of this work into an outdated os
Click to expand...
Click to collapse
Froyo is easier at this point.. and im sure some people prefer aosp over touchwiz
a.vandelay said:
why don't you?
Click to expand...
Click to collapse
No need to be a ****, just trying to help
bpodz34 said:
Hey Man before you put all of this work in, why dont you make a gingerbread asop rom. I dont see the point in putting all of this work into an outdated os
Click to expand...
Click to collapse
I already addressed this statement in the OP...
a.vandelay said:
why don't you?
Click to expand...
Click to collapse
bpodz34 said:
No need to be a ****, just trying to help
Click to expand...
Click to collapse
please don't clutter this up with this nonsense!!!
An AOSP Froyo build would be an important step for the Captivate community, good luck with your work!
good luck, look forward to it.
Appreciate your work. Good luck.
Awesome. Looking forward to it.
Sent from my liberated Captivate via XDA App.
Good idea ! I can help with testing if you like.
Sent from my SGH-I897 using XDA App
Sign me up for testing I actually am in the minority for working GPS so I can test that
I'm glad to hear that!
I'm in for testing as well if you need help.
Good luck!
Yes please.
And I'm DTT.
Down To Test.
not a troll, or hater, or dev but I thought an asop build was not possible because the touchwiz framework is tied in to deep and no open source drivers..
best of luck to you, im here to help test if needed
Grandelama said:
An AOSP Froyo build would be an important step for the Captivate community, good luck with your work!
Click to expand...
Click to collapse
I fail to understand this statement please explain ?
g0dzilla32 said:
not a troll, or hater, or dev but I thought an asop build was not possible because the touchwiz framework is tied in to deep and no open source drivers..
Click to expand...
Click to collapse
everything is possible , not that I understnad the need for it ...
mnjm9b said:
I was going to get involved with the CM builds but
I feel it would be better to build from a pure AOSP base.
knowing that it was created and fully compatible with the device that
it is being used on.
Click to expand...
Click to collapse
Maybe im misquoting you , and dont get me wrong here , any captivate development is good , but I fail to understand why starting form CM is a bad idea and even why we need to work of ( like fork roms of ) something that was AOSP build for samsung while you already stated that :
mnjm9b said:
the only captivate roms are actually hacks from the samsung builds.
Click to expand...
Click to collapse
we woudl then be makin roms 'ripped ' from CM like sooooo many other phone ..
IMHO , your work is redoing what CM is doing for many phones already , wouldnt it be much easier / not to mention rewarding for the community to just try and build cm 'from source' for the samsung captivate ?
g0dzilla32 said:
not a troll, or hater, or dev but I thought an asop build was not possible because the touchwiz framework is tied in to deep and no open source drivers..
Click to expand...
Click to collapse
Naw, I'm running an AOSP build myself right now. While the drivers aren't opensource for the Captivate, do you remember that there is a little phone called the Nexus S that has almost IDENTICAL hardware? Everything from the Nexus is opensource (pretty sure...) and the drivers are compatible with our Captivates. The only thing that we have that they don't is the second SD Card, which is an easy hack-in, and the audience noise-canceling mic (also easy, as the Nexus 1 has the same mic/chip.)
did the OP's cappy blow up or something, the accounts disabled >,> ~inches back~ joke aside, if you do have any thing needed testing give me a shout looking for something built off the cappys them selfs to though I must admit there is a (explicit) ton of roms for nomage as it is from the vibs source that are all well and good. Good luck, well back to flashing
I want to start developing a custom rom(or at least to try).But firstly I don't know how to setup git and python on ubuntu.I read on google that I need that files.And when I set them up,how can I get the source code?If you know,please help.
Thanks in advance.
Edit: We downloaded the cyanogenmod source code successfully with repo.
Another question: Do I need python when I have eclipse?
If you know how, please tell us!
I know you can download source codes at github.com.
That's all I know....
Joost
Get linux and learn to use then get git then use git to get repo then use repo to download sources.
Mark
Pm me where u are at and i will help more in depth with u.
Mark
pashinator said:
Get linux and learn to use then get git then use git to get repo then use repo to download sources.
Mark
Click to expand...
Click to collapse
I know how to use ubuntu.I think I downloaded the kernel yesterday but don't know where it is.
Currently there are no proper manifest for compiling Android 2.2 or 2.3 for LG Swift, those that exist are outdated or deleted by the developers. We need a correct manifest for,lg shift device, vendor, kernel..etc to start building.
fdespotovski said:
I want to start developing a custom rom(or at least to try).But firstly I don't know how to setup git and python on ubuntu.I read on google that I need that files.And when I set them up,how can I get the source code?If you know,please help.
Thanks in advance.
Edit: We downloaded the cyanogenmod source code successfully with repo.
Another question: Do I need python when I have eclipse?
Click to expand...
Click to collapse
Can somebody tell us how to compile the system and kernel for unsupported devices like the lg gt540?
this is from the readme with Quarx rom if that helps
Компиляция:
make -j3 ARCH=arm CROSS_COMPILE=/путь до ndk/build/prebuilt/linux-x86/arm-eabi-4.4.0/bin/arm-eabi-
eoghan2t7 said:
this is from the readme with Quarx rom if that helps
Компиляция:
make -j3 ARCH=arm CROSS_COMPILE=/путь до ndk/build/prebuilt/linux-x86/arm-eabi-4.4.0/bin/arm-eabi-
Click to expand...
Click to collapse
Thanks for your reply!
any ideas about using /framework/base from git to compile trebulchet or systemui?
i'm using IntelliJ IDEA
thank you
fabiosarts said:
any ideas about using /framework/base from git to compile trebulchet or systemui?
i'm using IntelliJ IDEA
thank you
Click to expand...
Click to collapse
This is the Trebuchet repo: https://github.com/CyanogenMod/android_packages_apps_Trebuchet
i got the trebuche package and others i would need by downloading the entire cm10 source git using repo, the only problem is the libraries i need to compile it
i've found i could compile it, but the prebuilt gcc is 32 bits, i can't run it, since i got a 64 bits system, but there's a 64 bit gcc there, but i can't make to make use it instead using the 32 bits
fabiosarts said:
i've found i could compile it, but the prebuilt gcc is 32 bits, i can't run it, since i got a 64 bits system, but there's a 64 bit gcc there, but i can't make to make use it instead using the 32 bits
Click to expand...
Click to collapse
Shouldn't the 32 bit version run in compatibility mode?
sadly my debian and slackware didn't came with 32 bit compatibility
i could compile it on mac os, but all i got it's a final dexed jar, no android APIs there D:
Disclaimer: I'm not responsible for what this does to your shiny device, SO DON'T BLAME ME!!!
Requirements:
Ubuntu 12.10 64-bit
15GB of disk space (25Gb recommended)
Internet connection
Brain
First:
Install required packages:
Code:
apt-get install git-core gnupg flex bison gperf libsdl1.2-dev libesd0-dev libwxgtk2.8-dev squashfs-tools build-essential zip curl libncurses5-dev zlib1g-dev openjdk-6-jre openjdk-6-jdk pngcrush schedtool libxml2 xsltproc g++-multilib lib32z1-dev lib32ncurses5-dev lib32readline-gplv2-dev gcc-4.7-multilib g++-4.5-multilib
Install repo:
Code:
mkdir -p ~/bin
mkdir -p ~/cm10.1
curl https://dl-ssl.google.com/dl/googlesource/git-repo/repo > ~/bin/repo
chmod 755 ~/bin/repo
echo "export PATH=\${PATH}:~/bin" >> ~/.bashrc
export PATH=${PATH}:~/bin
Second:
Sync all the sources
Code:
cd ~/cm10.1
repo init -u git://github.com/CyanogenMod/android.git -b cm-10.1
mkdir -p .repo/local_manifests
curl -L -o .repo/local_manifests/local_manifest.xml -O -L https://raw.github.com/pikachukaki/android_local_manifest/cm-10.1/local_manifest.xml
repo sync -jx (Choose number depenting on how good your speed is)
Go sleep for the night, because this takes overnight
Code:
Download this file [URL="http://sourceforge.net/projects/pikachukaki/files/HwQcomRIL.java/download"]Here[/URL]
Place it in cm10.1/device/huawei/u8800pro/ril (create the rils folder)
Code:
Also go to folder /cm10.1/device/huawei/u8800pro and rename sd.mk to cm.mk and open the file and change PRODUCT_NAME := shendu_u8800pro to PRODUCT_NAME := cm_u8800pro
Third:
Build:
Code:
cd ~/cm10.1/vendor/cm
./get-prebuilts
cd ~/cm10.1/device/huawei/u8800pro
./extract-files.sh
cd ~/cm10.1
. build/envsetup.sh
lunch cm_u8800pro-userdebug
make otapackage
ENJOY!!!
If you are having problems (that you will) you need to sync this repo too
https://gitcafe.com/pikachukaki/android_hardware_qcom_media
Thanks @tcf38012 for the tutorial..i just edit the lines needed for u8800pro to make it easier for you...this is the one from the 5th tutorials i used....
Q&A
------------------
Changelog
1)Added the ril file to make the rom have signal and working phone
2)Add the fix you have to do to a file so the compiler can understand that you wanna compile cyanogen and not shendu!
Also im now compiling latest cm for u+ i will post it for testing when its done!!
Also for the love of god...pls don't start asking how to install ubuntu..and what is this and what is that...if you don't know anything about linux or basic PC thinks wait someone else to do it for you!!!
Well, I now understand why pa is so heavy . thanks pika.
Is the phone capable of aokp ?
Sent from my U8800-51 using Tapatalk 2
Somcom3X said:
Well, I now understand why pa is so heavy . thanks pika.
Is the phone capable of aokp ?
Sent from my U8800-51 using Tapatalk 2
Click to expand...
Click to collapse
Cm and aokp are basically the same...pacman,pa and all those roms are great roms but they aren't for u+..i dont really like them even on my n4...i prefer slimbeam!!great light rom with cherry picks from aokp...i love the center clock with date! ^_^
It seems that there is a problem with qcom/media files..ivan give me another repo with the fixes for it..but im tired now and i reboot to windows...i will fix the tutorial when im done!!
pikachukaki said:
It seems that there is a problem with qcom/media files..ivan give me another repo with the fixes for it..but im tired now and i reboot to windows...i will fix the tutorial when im done!!
Click to expand...
Click to collapse
I was just about to mention that. His legacy_manifest needs updating
Sent from my U8800-51 using Tapatalk 2
Slims nice have a ported version running on rite now. But still idk why am in love with PAK.
Sent from my U8800pro using xda premium
Rittik said:
Slims nice have a ported version running on rite now. But still idk why am in love with PAK.
Sent from my U8800pro using xda premium
Click to expand...
Click to collapse
Its a good rom but have many unused stuff and wants too much resources!
pikachukaki said:
Its a good rom but have many unused stuff and wants too much resources!
Click to expand...
Click to collapse
Agreed
Sent from my GT-N5100 using xda premium
https://gitcafe.com/yemod/android_hardware_qcom_media this fixes the media related problems you will face during compiling...
Also i notice you still trying to create roms with apk and lib changing..even that was the way i was making roms.you will NEVER...and i say NEVER create a perfect rom when you aren't compiling from source...even with ivan's 90% device tree..the fixes providing from cm source can make your device work differently...
anyway take care!!
pikachukaki said:
https://gitcafe.com/yemod/android_hardware_qcom_media this fixes the media related problems you will face during compiling...
Also i notice you still trying to create roms with apk and lib changing..even that was the way i was making roms.you will NEVER...and i say NEVER create a perfect rom when you aren't compiling from source...even with ivan's 90% device tree..the fixes providing from cm source can make your device work differently...
anyway take care!!
Click to expand...
Click to collapse
@pikachukaki when I last tried to use this guide to compile cm10.1 from source everything was good but the downloading of the repo was always stuck at the same place... Is this problem fixed with this?
SvTeam said:
@pikachukaki when I last tried to use this guide to compile cm10.1 from source everything was good but the downloading of the repo was always stuck at the same place... Is this problem fixed with this?
Click to expand...
Click to collapse
What repo?cm or ivans?
pikachukaki said:
What repo?cm or ivans?
Click to expand...
Click to collapse
@pikachukaki repo sync -j5 (Choose number depenting on how good your speed is) <--- on this step
everything was good but it sticks always at the same place
I tried 3-4 times always sticks at the same place
Repo is over 80GB includes all android files from 2.2 Android. Thats why it takes so much time. Leave it for 1day
-Rik[Rittik]
Rittik said:
Repo is over 80GB includes all android files from 2.2 Android. Thats why it takes so much time. Leave it for 1day
-Rik[Rittik]
Click to expand...
Click to collapse
For me it syncs in about 4 hours
Maybe you just have slow internet connection
I have 125KBps you guys must be in like some MBps. Well Somcom made it in like 2.5hrs ..well Depends on speed..80gb is huge
-Rik[Rittik]
Rittik said:
Repo is over 80GB includes all android files from 2.2 Android. Thats why it takes so much time. Leave it for 1day
-Rik[Rittik]
Click to expand...
Click to collapse
I let it over 12 hours :/ Anyway I will try one more time.
EDIT: last time I did it it was like 7-20 GB(cant really remember lol) probably wasn't correct. The thing is that while it was stuck there the repo size wasn't increasing at all. Same size all time.
SvTeam said:
I let it over 12 hours :/ Anyway I will try one more time.
Click to expand...
Click to collapse
Yep Best of luck
-Rik[Rittik]
Rittik said:
Yep Best of luck
-Rik[Rittik]
Click to expand...
Click to collapse
OK I started this again. Hopefully this time it will work. Will post screenshots tomorrow.
Building AOSP for the Nexus 6 - Continued!
Scott is no longer working with the N6 and he has graciously allowed me to continue his thread . We all owe @scrosler a special THANKS for his work on the original thread. Better yet please go buy him a beer!! I also want to personally thank all who contributed to the original thread. You all make it work!!
Preface
1. I want to start by saying that I am still a relative newb. I built my first aosp rom for my N9 using the the guide from the original thread and followed up with one for my N6. I hope that by moving this thread forward we can continue to help others get started while we continue our own learning.
2. All questions concerning the build process and setup are welcome. They may not all get answered but please ask.
This guide continuation assumes the following:
1. You have read the original thread's OP and scanned the remainder of that thread before posting here.
2. To get things started you can test a rom built from android-5.1.1_r14. Get rom below. Vendor blobs updated from here and include the updated LYZ28E blobs. I also added some missing build props.
3. I am also linking the github source for the rom. You can build your own. Get github source below.
4. I hope to add a short get started github tut in OP#2 and add a vendor folder setup discussion in OP#3. I'm still trying to figure out how @sykopompos did his. All help on this subject is welcome.
FYI TO ALL!!! All my testing is on USA Verizon netwok.
LINK TO ORIGINAL THREAD OP
Get ROM HERE
Get GIT SOURCE HERE
==========================================================================================================
The following copied from original OP with some minor editing.
This guide assumes the following
Have Ubuntu 14.04 or equivalent setup, fully operation, and up to date. Hard Machine or Virtual, makes no difference. Must meet the minimum specs for compiling. Info from Google HERE
Understand terminal command line entry as this is all command line processes.
Lets Begin!
Add Java
Code:
sudo apt-get install openjdk-7-jdk
Add Build tools (Adds the required packages at the time of this posting)
Code:
sudo apt-get install git gnupg flex bison gperf build-essential \
zip curl libc6-dev libncurses5-dev:i386 x11proto-core-dev \
libx11-dev:i386 libreadline6-dev:i386 libgl1-mesa-glx:i386 \
libgl1-mesa-dev g++-multilib mingw32 tofrodos \
python-markdown libxml2-utils xsltproc zlib1g-dev:i386
Add Repo command (Syncs Google Repository with your local machine)
Code:
mkdir ~/bin && curl http://commondatastorage.googleapis.com/git-repo-downloads/repo > ~/bin/repo && chmod a+x ~/bin/repo
Add bin folder to path for repo command (After you do this close Terminal and re-open to institute changes (easy way))
Code:
sudo gedit .bashrc
export PATH=~/bin:$PATH <-(add to end of bashrc)
Identify Yourself to the Repo (One day you may make commits so think about that when choosing your info!)
Code:
git config --global user.email "[email protected]"
git config --global user.name "yourpreferredusername"
Sync Repo (Download source... Sit back and grab a pop and a sandwich...)
Code:
mkdir ~/AOSP
cd ~/AOSP
repo init -u https://android.googlesource.com/platform/manifest -b android-5.1.1_r14
repo sync
Note: I use AOSP as my directory name. You can use what you want. You could use "aosp" or "Source" or "android" or "whateveryoulike"
Set up ccache (this makes subsequent compiling much faster!)
First: Close then re-open the terminal so you are in the home root
Code:
sudo gedit .bashrc
export USE_CCACHE=1 <-Append that line to .bashrc then save and close
cd AOSP
prebuilts/misc/linux-x86/ccache/ccache -M 25G <-I use 25 gigs but you can change that value to any size you feel appropriate)
fhem Alternate ccache setup.
Install ccache using package manager (I use synaptic)
set ccache size - One ccache for all directories.
Code:
ccache -M 35G (I use 35 gigs but you can change that value to any size you feel appropriate)
I do not edit my .bashrc I use the following before my final make command. See Readme Build It
You can choose to use or not use ccache for any build/operation from any directory.
Code:
export USE_CCACHE=1
ccache manual
Install proprietary binaries (Needed for things like GPS and Bluetooth, they are not Open Source like Android) (Install proprietary binaries from here in the root of AOSP folder (or whatever you called yours))
Code:
https://developers.google.com/android/nexus/drivers
Run envsetup.sh
Code:
source build/envsetup.sh
Choose Device
Code:
lunch aosp_shamu-userdebug
Build it!
Code:
make -j16 otapackage
Note: using -j16 means 16 worker threads. This is fine if you have 8 logical CPU's so you may need to adjust that to a smaller or larger number if you have more or less Logical CPU's. Example: I have an i7 K edition Haswell so I have 8 logical cores; so I build with -j16. If you have an i5 quad core CPU which is 4 logical cores then you may want to consider -j8 as the set number of worker threads. Oddly enough Google actually recommends 3 to 4 times the number of logical CPU's. When I do that I have nothing but build crashes. You may need to experiment to get the right blend of performance and stability during build!
If you use
Code:
make -j `getconf _NPROCESSORS_ONLN` otapackage
it may take a little longer but it won't crash.
Find it
Should be located here: /home/yourusername/AOSP/out/target/product/shamu
Congrats!
Your know among the elite enthusiast that can build from source! Pat yourself on the back!
Git Hub Tips
There is already much written on git use so I am not going to try and reinvent that wheel!!!! I will provide some usefull links for your reading pleasure. I will also provide some tips based on my personal experiences using git. I have found there are many ways to get the same result using git and there are also many ways to break your your work. I did a lot of trial and error and deleting to learn what works best for me. Start small, don't be intimidated, and stay patient -- it will come. The following assumes we are using a linux distro.
1. Open a GitHub account ----- its easy. Keep it simple. Follow the setup instructions and use recommended HTTPS connection.. I also suggest caching your login info - I use 60 mins for my default cache time.
2. Install git. It is easiest to install Git on Linux using the preferred package manager of your Linux distribution. I use Synaptic Package Manager. Keep it simple. Follow the setup instructions and use recommended HTTPS connection.
3. Git Tools: I prefer using Geany with terminal and File and Tree Browser and VC control plug-ins. There are many tools available and you may need to find one that works for you. You can install Geany and its plug-ins using your distro package manager.
4. ROM Tree Structure Very Important. I recommend keeping your rom GitHub tree structure in line with the Android Git Repositories.
Useful links:
1. http://git-scm.com/docs
2. http://gitref.org/creating/
3. http://forum.xda-developers.com/showthread.php?t=1877040 Thanks @eagleeyetom
4. http://forum.xda-developers.com/showthread.php?t=2763236 Thanks @jabza
5. http://forum.xda-developers.com/showthread.php?t=2329228 Thanks @Red Devil
I hope the above is helpful to getting you started on GitHub. Good Luck!!
reserved vendor folder discussion.
fhem said:
Building AOSP for the Nexus 6 - Continued!
Scott is no longer working with the N6 and he has graciously allowed me to continue his thread . We all owe @scrosler a special THANKS for his work on the original thread. Better yet please go buy him a beer!! I also want to personally thank all who contributed to the original thread. You all make it work!!
Preface
1. I want to start by saying that I am still a relative noob. I built my first aosp rom for my N9 using the the guide from the original thread and followed up with one for my N6. I hope that by moving this thread forward we can continue to help others get started while we continue our own learning.
2. All questions concerning the build process and setup are welcome. They may not all get answered but please ask.
This guide continuation assumes the following:
1. You have read the original thread's OP and scanned the remainder of that thread before posting here.
2. To get things started you can test a rom built from android-5.1.1_r4 using Sykopompos vendor blobs for 5.1. Get rom below.
3. I am also linking the github source for the rom. You can build your own. Get github source below.
4. I hope to add a short get started github tut in OP#2 and add a vendor folder setup discussion in OP#3. I'm still trying to figure out how Sykopompos did his. All help on this subject is welcome.
FYI TO ALL!!! All my testing is on USA Verizon netwok.
LINK TO ORIGINAL THREAD OP
Get ROM HERE
Get GIT SOURCE HERE
Click to expand...
Click to collapse
Lots and lots of dark magic ?
Hey great to see you. I thought you were kyaking LOL. You coming back for M????
fhem said:
Hey great to see you. I thought you were kyaking LOL. You coming back for M????
Click to expand...
Click to collapse
I actually just ordered my kayaking last night so hopefully I'll have it in time for next weekend.
Just popping in really and checking M out and seeing how it develops
sykopompos said:
I actually just ordered my kayaking last night so hopefully I'll have it in time for next weekend.
Just popping in really and checking M out and seeing how it develops
Click to expand...
Click to collapse
Still waiting for the full platform on aosp. Hey did you diff the stock rom and aosp rom to get your vendor blobs. I was setting up with BeyondCompare to give it a look. LOL Enjoy your time off and your family. Life is too short.
fhem said:
Still waiting for the full platform on aosp. Hey did you diff the stock rom and aosp rom to get your vendor blobs. I was setting up with BeyondCompare to give it a look. LOL Enjoy your time off and your family. Life is too short.
Click to expand...
Click to collapse
For the most part, you can diff and find file differences but aosp has it's own files and stuff like that so you gotta be able to figure out what they do
sykopompos said:
For the most part, you can diff and find file differences but aosp has it's own files and stuff like that so you gotta be able to figure out what they do
Click to expand...
Click to collapse
I was afraid you were going to tell me that. :laugh: Oh well It will give my old brain and google a workout. hahahaha Thanks and enjoy yourself.
Hey @fhem! Glad to see you take over, you're always very helpful!
In your Repo Int code above, did you mean "android-5.1.1_r4"? I wanted to double check that part for the guide.
purian23 said:
Hey @fhem! Glad to see you take over, you're always very helpful!
In your Repo Int code above, did you mean "android-5.1.1_r4"? I wanted to double check that part for the guide.
Click to expand...
Click to collapse
Yep. That's the latest. That's what I built above if you look at the fhemaosp default manifest.
fhem said:
Yep. That's the latest. That's what I built above if you look at the fhemaosp default manifest.
Click to expand...
Click to collapse
Okay cool! Just trying to save some headache if someone grabs the guide one listed lol.
purian23 said:
Okay cool! Just trying to save some headache if someone grabs the guide one listed lol.
Click to expand...
Click to collapse
Fixed thanks for catching that typo.
sykopompos said:
I actually just ordered my kayaking last night so hopefully I'll have it in time for next weekend.
Just popping in really and checking M out and seeing how it develops
Click to expand...
Click to collapse
Hello @sykopompos, I am just glad to see you here! Thanks for all your contributions!
I let @fhem take over the thread since he is more active than I. But I appreciate all the help you have given and will continue to give!
Knowledge is TRULY priceless!
-Scott
EDIT: Can someone put that on my tombstone, lol
Can we have guide about building ROM from open source? e.g LG open source. Actually I was trying to build a M1 review ROM with the LG open source but it fails. I tried several times and finally give op due to errors. I downloaded the android source and then follow this guide and then download LG G4 ROM from following.
http://opensource.lge.com/osSch/list?types=ALL&search=H815
I set up the environment and then started building but it fails again and again. I think it will be very helpful for every one who interested in building ROM from open source. Thanks
Sent from my LG-H815 using Tapatalk 2
janjan said:
Can we have guide about building ROM from open source? e.g LG open source. Actually I was trying to build a M1 review ROM with the LG open source but it fails. I tried several times and finally give op due to errors. I downloaded the android source and then follow this guide and then download LG G4 ROM from following.
http://opensource.lge.com/osSch/list?types=ALL&search=H815
I set up the environment and then started building but it fails again and again. I think it will be very helpful for every one who interested in building ROM from open source. Thanks
Sent from my LG-H815 using Tapatalk 2
Click to expand...
Click to collapse
I have never worked with any LG source codes. I would suggest you start your own thread on the LG G4 Forum. It definately sounds like you got enough to get one rolling. Good luck with the G4.
Hello,
I am trying to build android 5.1.1_r6 for the Nexus 6 and was able to get it to build and install. Had a weird issue where gapps would not install, but I think I fixed that by flashing a different set of gapps. My issue is that I am unable to hear people through the handset speaker when I make phone calls. I have no idea what it is. Apparently they can hear me, but I cant hear them. I can use speaker phone, but even that seems lower volume than normal.
Also, side question, since I am building AOSP 5.1.1_r6 am I supposed to use the preview binaries found here: https://developers.google.com/android/nexus/blobs-preview
or just use the factory image binaries?
Thank you
KerryWood34 said:
Hello,
I am trying to build android 5.1.1_r6 for the Nexus 6 and was able to get it to build and install. Had a weird issue where gapps would not install, but I think I fixed that by flashing a different set of gapps. My issue is that I am unable to hear people through the handset speaker when I make phone calls. I have no idea what it is. Apparently they can hear me, but I cant hear them. I can use speaker phone, but even that seems lower volume than normal.
Also, side question, since I am building AOSP 5.1.1_r6 am I supposed to use the preview binaries found here: https://developers.google.com/android/nexus/blobs-preview
or just use the factory image binaries?
Thank you
Click to expand...
Click to collapse
I haven't been able to get _r6 to build due to errors in frameworks/opt ever since merging so good for you on that. As for the binaries It was found a while back that the Google one were incomplete. People were using The vendor files from chroma in their stead. I haven't spoken to fhem in a couple of days but it looks like his github is under construction atm. I forked the vendor repo from him since he had changes that fixed some no sound issues as well. Again I've yet to build _r6 successfully so no idea if these will solve your issue but you're welcome to try them out? You can get them from my github here: https://github.com/rockinroyle/platform_vendor_moto_shamu
Let us know how it goes? I'm trying again after I clone frameworks from scratch.
rockinroyle said:
I haven't been able to get _r6 to build due to errors in frameworks/opt ever since merging so good for you on that. As for the binaries It was found a while back that the Google one were incomplete. People were using The vendor files from chroma in their stead. I haven't spoken to fhem in a couple of days but it looks like his github is under construction atm. I forked the vendor repo from him since he had changes that fixed some no sound issues as well. Again I've yet to build _r6 successfully so no idea if these will solve your issue but you're welcome to try them out? You can get them from my github here: https://github.com/rockinroyle/platform_vendor_moto_shamu
Let us know how it goes? I'm trying again after I clone frameworks from scratch.
Click to expand...
Click to collapse
I had no luck with r6 either. I reverted back to r5. I looked at chroma/zephk on git and I don't think he took the whole r6 merge to his git repos - not sure what he did.
I'm sticking to to r5 for now.
I've been building r6 fine with zero issues. Did notice the speaker issue on call but fixed it with two commits from chroma in device/moto/shamu for audio. I've also been using the latest binaries posted by google on the aosp page, no issues that I can tell. WiFi calling/normal calling, sound all around, SMS/MMS, all works.
Sent from my Nexus 6 using Tapatalk