Database Users

Samsung Captivate Froyo AOSP [In Development]***WE HAVE LIFT OFF*** 04/19/2010

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

Compiling android on Fedora 16

Ive spent the last week or so ever since samsung released their code, trying to compile ICS on fedora 16, after countless hours downloading and compiling code i finally got it. i wanted to share my results with you guys hopefully it will save others some troubles......
ive been using linux for 20 years, but i'm very very new to android development, and since i'm not allowed to post in the development forum i will post it here its pretty simple
but i did get it all compiled and running on my SGS2 from at&t
i'm not gonna get into the details of downloading the source code, but once you download the source code, and run the envsetup script and the lunch full-eng
follow these steps to build the os..
I untarred the samsung Platform.gz file into the android source directory first.
Some of this info i got from ttp:// rootzwiki.com/topic/8037-compile-android-on-fedora-1516-by-xoomdev/
Then:
1.) Install Packages
yum install -y zip curl gcc gcc-c++ flex bison gperf glibc-devel.{x86_64,i686} zlib-devel.{x86_64,i686} ncurses-devel.i686 libX11-devel.i686 libstdc++.i686 libsx-devel readline-devel.i686 libXrender.i686 libXrandr.i686 schedtool pngcrush
2.) Downgrade make i found release 15 is the only one that works right
yum upgrade make --nogpgcheck --releasever=15
3.) comment out line 136 of build/core/main.mk to stop a java version error
4.) UnComment line 63 of libcore/JavaLibrary.mk
5.) Add LOCAL_LDLIBS+=-lX11 to development/tools/emulator/opengl/host/renderer/Android.mk
6.) Add LOCAL_CFLAGS+=-m32 to to top Level Makefile
7.) make -j16
hope this helps.....

Thanks...I was about to start this. I wonder why the make downgrade, though...I'll check into that.
Sent from my GT-P7500 using XDA Premium HD app

Thanks you!
Is this the 64 bit version or 32 of Fadora? Sorry read your install calls THANK YOU!

Slie said:
Is this the 64 bit version or 32 of Fadora? Sorry read your install calls THANK YOU!
Click to expand...
Click to collapse
as i know android compile only on 64 bit

Cm9 Compiling problem

Ok lets see if we can find help here...i follow this guide!!
http://forum.xda-developers.com/showthread.php?t=1668483
after download the whole cm source (after this command : repo init -u git://github.com/CyanogenMod/android.git -b ics)
its sais to add his htc gits but i add the ones i found for u8800pro (device https://github.com/ivan19871002/cm9_device_u8800pro and vendor https://github.com/ivan19871002/cm9_vendor_u8800pro)
after this it sais to type . build/envsetup.sh and then lunch 4 (i found in the list that 5 is the cm_u8800_full) anyway
after this it sais that u8800pro device not found and it tries to downloaded from cm repositories that of cource didnt exists...any help thank you!

maybe you can also try this guide:
http://www.modaco.com/topic/354780-guidedevcompiling-cm910-for-zte-skate/
seems a little cleaner in my opinion
of course replace some git clone commands with the appropriate ones for u8800 pro

Moihack said:
maybe you can also try this guide:
http://www.modaco.com/topic/354780-guidedevcompiling-cm910-for-zte-skate/
seems a little cleaner in my opinion
of course replace some git clone commands with the appropriate ones for u8800 pro
Click to expand...
Click to collapse
Thx moi i will and btw im expecting some mails from you
Sent from my U8800Pro using xda premium

[Script] Build ICS/JB Kernel

Thanks to the amazing work of mapkel you can now use this script to compile and pack the kernel!
UPDATE: read mapkel's post here: http://forum.xda-developers.com/showpost.php?p=43419784&postcount=45
Thank him here.
This is an informative guide and I decline responsibility for any damage to your device.
Do not attempt to build this kernel if you are going to complain to devs about issues.
That being said, mapkel has made this so that even those with little knowledge can build the kernel without any issues. If you do have any issues, post here and I will try to assist you.
The following is a complete tutorial to building the kernel.
Credits:
Kernel Devs: krystianp, lehjr, Epinter, and mmontuori for making this kernel; without them there is no kernel.
Big thanks to mapkel for this amazing script.
Another big thanks to benouch for the original idea.
A final big thanks to zen25205 for help with building the kernel and getting the Linaro Toolchain.
Kernel Kitchen
I suggest building this with the latest CM9 MROM until the public beta is released.
You need to install Ubuntu 12.04 64bit (Google for instructions)
Prerequisites:
Open a terminal and run the following commands the first time:
Code:
sudo apt-get install -y build-essential kernel-package libncurses5-dev bzip2
Code:
sudo apt-get install git
If there are any issues with this guide, or if you have any issues building the kernel, post here and I will assist you as best I can.

Stage 1 (start at stage 2 if you have already built the kernel using this script:
Code:
cd ~
Code:
wget https://www.cubby.com/pl/kernel_script.zip/_25f010125b924ec7a42fe1d66245f36a
Code:
unzip ${HOME}/kernel_script.zip -d ${HOME}
Stage 2:
Code:
cd kernel
Code:
./script
There will be 4 choices to make throughout the script:
Clean install y/n (choose "n" on first run of script)
What defconfig? (Usually it is MROM but in the last update it is temporarily MROM2)
Compile CM9 or CM10 kernel? (self explanatory)
Name of config (Any name works. I chose "olympus".)

enjoy)

Built but cam not working

paladin881 said:
Built but cam not working
Click to expand...
Click to collapse
cameras disabled due to battery drain
Click to expand...
Click to collapse
https://github.com/CyanogenMod-Atrix/android_kernel_motorola_olympus/commits/master

Post here if it worked well for you. Give some feedback for mapkel.

No Wifi
Cheers, the script works great on Ubuntu 11.10, without a hic.
However, upon flashing the kernel, I get no wifi. I'm going to try your step by step tutorial...
Edit: I built the kernel using MROM2 defconfig and for CM10, and flashed "someone's" CM10

Newbleeto said:
Cheers, the script works great on Ubuntu 11.10, without a hic.
However, upon flashing the kernel, I get no wifi. I'm going to try your step by step tutorial...
Edit: I built the kernel using MROM2 defconfig and for CM10, and flashed "someone's" CM10
Click to expand...
Click to collapse
Strange..
The modules should copy with this.
Try CM9

atrix4g18 said:
Strange..
The modules should copy with this.
Try CM9
Click to expand...
Click to collapse
I'm updating Ubuntu, maybe the problem is on my end. Will try CM9 in the meanwhile and let you know!

Newbleeto said:
I'm updating Ubuntu, maybe the problem is on my end. Will try CM9 in the meanwhile and let you know!
Click to expand...
Click to collapse
You won't be able to do both.
If you compiled the kernel for CM10 you will only be able to use it on CM10.
Unless you are able to update Ubuntu as you compile the kernel for CM9.

atrix4g18 said:
You won't be able to do both.
If you compiled the kernel for CM10 you will only be able to use it on CM10.
Unless you are able to update Ubuntu as you compile the kernel for CM9.
Click to expand...
Click to collapse
It's impossible to compile while updating, didn't remember that, silly me :silly:
Anyhoot, wifi still doesn't work in Ubuntu 12.04. Fresh install on a different PC, way faster than updating
I'll try CM9 tomorrow, should've been asleep for a while

Can anyone or everyone list sites that work with a direct link.
That means I go to www.sitename/filename.zip and it starts downloading.

All I can think of right now is a cloud storage like Dropbox or Google Drive. I know Dropbox has a traffic limit for public files. Don't know about Google drive
Sent from my MB860 using xda app-developers app

upndwn4par has unlimited bandwidth, iirc. Maybe you can contact him and ask if you can host that one tiny script file there?
Or you could sign up with a free webhost and upload it there. There are several free webhosts with unlimited bandwidth (with a very limited space as trade-off, but I think it's more than enough for the script file).

If it's just a single script, maybe something like pastebin.com or similar might be an option? A little inconvenient since you have to copy and paste content instead of just download, but AFAIK it does have unlimited bandwidth.

atrix4g18 said:
Can anyone or everyone list sites that work with a direct link.
Click to expand...
Click to collapse
Maybe copy.com? Here is my ref for extra 5 GB: https://copy.com?r=qfhUoV
If this does not solve the problem, I can provide space for the script on my own server with a separate FTP account.

priard said:
Maybe copy.com? Here is my ref for extra 5 GB: https://copy.com?r=qfhUoV
If this does not solve the problem, I can provide space for the script on my own server with a separate FTP account.
Click to expand...
Click to collapse
Doesn't have a direct download link.

quetzalcoatl2435 said:
Doesn't have a direct download link.
Click to expand...
Click to collapse
Not quite. You can still download a file, for example using wget.
If You have a short public link, for instance: copy.com/PJzYgAUKECQm, You need to open it and copy the full link. In this case: copy.com/s/PJzYgAUKECQm/BetterBatteryStats_xdaedition_1.13.4.0.apk
then:
wget copy.com/s/PJzYgAUKECQm/BetterBatteryStats_xdaedition_1.13.4.0.apk
and done.

I will look at all the suggestions later today.
Thank you.

Delete

[Guide] [09/14/2015] Building AOSP 5.1.1_r14 for the Nexus 6-Continued!

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