[Q] Missing apps after building rom from AOSP - Nexus 5 Q&A, Help & Troubleshooting

I built a rom from aosp sources. Everything works fine, but some apps missing (no, not the google apps). I can't see the camera app, sound recorder and etc in the app drawer, but they are in the /system/app folder. The permissions seem right.
I am running ubuntu 12.04
Used this to configure my build environment.
I downloaded the drivers (KOT49H) then extracted the three .sh files and run them at the top of the source tree.
I executed these commands to build the rom:
Code:
$ . build/envsetup.sh
$ lunch aosp_hammerhead-userdebug
$ make otapackage -j8
I flashed the created zip with twrp for the first time, then I flashed it with the compiled revovery, but these apps were still missing.
I even made an update package to flash the rom in fastboot mode, but the apps were missing.
Code:
$ make updatepackage -j8
then
Code:
$ fastboot -w update aosp-hammerhead-img-eng.zip
My last atempt was to extract drivers directly from stock rom. The result was worse. The radio part was not working, and the missing apps were still missing however I can see them in /system/app
Am I doing something wrong or these apps simply not work in aosp?

Bumb
Sent from my Nexus 5 using xda app-developers app

I solved the problem. If I build rom from master branch the camera app is missing, but if i build rom from android-4.4.2_r1 branch the camera app is there and working fine
Sent from my Nexus 5 using xda app-developers app

Related

[ Q] build kernel from CM7 sources and created cwm zip

Hey all,
I wish to try some modifications I made to the CM7 kernel and I need help building the kernel.
I followed this guide: http://wiki.cyanogenmod.com/wiki/Building_Kernel_from_source
I had to use the code sourcery cross compiler since kernel.org is down.
I have 3 questions:
1. When I build the kernel, the wifi drivers fail to build with an array out of bound exception. I didn't change that code, do I need to do something special to build the wifi drivers? I managed to built the kernel by disabling wifi in the config file.
2. Where can I get CM .config file for crespo kernel? I tried getting it from the latest nightly but /proc/config.gz wasn't there!?!
3. How can I created an cwm flashable zip? I downloaded Anykernel from koush but when trying to flash I get an error saying mount need 4 args. Which branch of anykernel works with Nexus S?
Thx a lot for your help,
Steve
Sent from my Nexus S using Tapatalk
It might be worth sending a PM to mathkid95
Sent from the future to put right what once went wrong.
How to compile a kernel
First, Download the following cross compiler and extract it into your working directory http://minus.com/l0zydfa4ncuQP
Then, cd to your kernel's directory in terminal and then type the following in terminal to compile:
Code:
export PATH=$PATH:/home/your-username/your-working-directory/prebuilt/linux-x86/toolchain/arm-eabi-4.4.3/bin/
make ARCH=arm clean
make ARCH=arm herring_defconfig
make -j4 ARCH=arm CROSS_COMPILE=arm-eabi-
The herring_defconfig is the default config file for the nexus s and it in the kernel repo. Also if you are using CM kernel source, the herring_defconfig has been modified.
As for the cwr zip, download one of my any rom kernels extract it. Put the zimage and bcm.ko module in the appropriate folder and zip it.
Sent from my Nexus S
Redd has it haha
Sent from my HTC Sensation 4G using XDA App
This is great. I'll try it out tomorrow. Now that I have all those infos I'm sure everything will go smoothly.
Thanks again!
Sent from my Nexus S using Tapatalk
That worked beautifully!
This is the result: http://forum.xda-developers.com/showthread.php?t=1276278

Building From from AOSP Source help

Hi all I have been trying to compile a pure stock from for my phone using someone elces kernel, device, and vendor directories. I synced the master branch of aosp repo and symlinked my sepreatly downloaded device directories to the proper directories. When I go to build, I use the command
Code:
. /build envsetup.sh && brunch ancora_tmo[Code]
I get
[Code]Including devices/samsung/ancora_tmo/vendorsetup.sh
No command 'brunch' found
[Code]
as well as 4 other aosp devices.
I added ancora tmo by symlinking the sources to my system tree.
I tried building with the command lunch and I get
[Code] don't have product specs for: full_ancora_tmo
Do you have right report manifest[Code]
where am I going wrong on building
I followed some custom build instructions and haven't modified much source yet but am simply trying to build pure stock for my phone what am I doing wrong?
Sent from my Galaxy Exhibit running Jocala's CM9
Try these:
Make sure you run the "PATH" command that it says to in SDK setup:
Code:
$ mkdir ~/bin
$ PATH=~/bin:$PATH
Also, if you are making a new device, try to use the mkvendor.sh script in build/tools/device
WhiteHatHacker said:
Try these:
Make sure you run the "PATH" command that it says to in SDK setup:
Code:
$ mkdir ~/bin
$ PATH=~/bin:$PATH
Also, if you are making a new device, try to use the mkvendor.sh script in build/tools/device
Click to expand...
Click to collapse
I did I setup the sdk and edited The .bashrc (or something similar) file
and added the sdk path
Sent from my Galaxy Exhibit running Jocala's CM9
Maybe the '-eng' part was missing
try:
Code:
brunch full_ancora_tmo-eng
or do everything:
Code:
brunch full-eng
WhiteHatHacker said:
Maybe the '-eng' part was missing
try:
Code:
brunch full_ancora_tmo-eng
or do everything:
Code:
brunch full-eng
Click to expand...
Click to collapse
Nope, still says brunch isn't found.
possible the report sync didn't complete right
Sent from my Galaxy Exhibit running Jocala's CM9
Who's kernel are you using?
You did:
Code:
source build/envsetup.sh
correct?
WhiteHatHacker said:
Whose kernel are you using?
Click to expand...
Click to collapse
jocala's custom rooted kernel
Sent from my Galaxy Exhibit running Jocala's CM9
WhiteHatHacker said:
Who's kernel are you using?
You did:
Code:
source build/envsetup.sh
correct?
Click to expand...
Click to collapse
Yes correct
I get this error when I try and build from the lunch menu
Don't have product specs for full_ancora_tmo
Do you have right report manifests.
Sent from my Galaxy Exhibit running Jocala's CM9
Its hard for me to help without browsing your directories, but try this.
Grab your boot.img
do:
Code:
build/tools/device/mkvendor.sh device_manufacturer_name device_name /your/path/to/the/boot.img
once that finishes, do:
Code:
lunch full_device_name-eng
then if you go to devices/product/something or other to your device, you should be able to try and replace your stock kernel with his.
I'm shooting from the hip here, so if i'm f***ed up please let me know, we're all learning ;-)
WhiteHatHacker said:
Its hard for me to help without browsing your directories, but try this.
Grab your boot.img
do:
Code:
build/tools/device/mkvendor.sh device_manufacturer_name device_name /your/path/to/the/boot.img
once that finishes, do:
Code:
lunch full_device_name-eng
[CODE]
then if you go to devices/product/something or other to your device, you should be able to try and replace your stock kernel with his.
I'm shooting from the hip here, so if i'm f***ed up please let me know, we're all learning ;-)[/QUOTE]
Huh? I think my repo sync didn't complete there is no device directory in build/ tools.
my directory is only 5.4gb in size that may be my whole problem
Sent from my Galaxy Exhibit running Jocala's CM9
Click to expand...
Click to collapse
Hmmm, then I'm tapped out.
But, at least this thread has been kept bumped
Whereas mine is back down near the bottom of the page :-(
WhiteHatHacker said:
Hmmm, then I'm tapped out.
But, at least this thread has been kept bumped
Whereas mine is back down near the bottom of the page :-(
Click to expand...
Click to collapse
Yep I think my source tree is jacked up I'll resyncing everything and see how that goes
thanks for helping
Sent from my Galaxy Exhibit running Jocala's CM9
No problem, best I could do was try.

[Guide] How to build CM10.1 (Android 4.2.1) for the Galaxy R I9103

Note:
1. This is extension to the Karthik's Guide with Adam's Repo's...
2. Based on my experience i have created this Guide, I have successfully compiled the Build and sharing this with you so some one can try it...
Preparing the system:
Follow this Link until step 4.4 (i.e. 4.4 - Initialize Repository & Sync)
Start with sources:
Code:
cd ~/android/system/
Initialize Repo for Android CM10.1 (Android 4.2.1):
Code:
repo init -u git://github.com/CyanogenMod/android.git -b cm-10.1
and enter your credentials if needed.
Download the sources:
Code:
$ repo sync -j4
Wait until it's finished (takes a lot of time!).
If the process hangs use Ctrl+C to break out of it and resume the download with another
Code:
$ repo sync -j4
Initialize the environment
NOTE: If you have trouble syncing due to connection issues, try repo sync -j1. It's slower but some ISPs have issues with -j4/16
Want to make sure you didn't get any connection errors and have the complete repository? Just run the repo sync command again. It can't give you ANY errors.
Wait until it's finished (takes a lot of time!).
VERY IMPORTANT: Now, Lets add the device specific tree..
1) Open your File Browser,
2) Press Ctrl+H (to show hidden files/directories)
3) Navigate to android/system/.repo/manifest.xml
(Right Click & open the XML file in text editor)
4) Add
Code:
<project path="device/samsung/galaxyr" name="Adam77Root/android_device_samsung_galaxyr" remote="github" revision="jellybean"/>
BEFORE the manifest closing tags (</manifest>).
5) Save & Close the File.
Run another
Code:
$ repo sync
Get Device Specific Repos:
Code:
. build/envsetup.sh
Extract files from phone:
NOTE: You need to have cm10 installed on the phone.
Code:
cd ~/android/system/device/samsung/galaxyr/
./extract-files.sh
Code:
~/android/system/vendor/cm/get-prebuilts
Important Things to be taken care before Building ROM:
1. Add these line in Boarconfig.mk
Code:
TARGET_ARCH := arm
BOARD_EGL_NEEDS_LEGACY_FB := true
2. Change the below line.
Code:
BOARD_RECOVERYIMAGE_PARTITION_SIZE := 5242880
to
Code:
BOARD_RECOVERYIMAGE_PARTITION_SIZE := 7242880
3. Delete Overlay folder.
4. Go to build/tools/releasetools and open file "ota_from_target_files" and replace the whole code with this code from this link.
Ok, You are done Now...
Building the ROM:
Code:
brunch cm_galaxyr-eng
it will take around 2 - 3 Hours....
Congrats you are done
Now Go to ~/android/system/out/target/product/galaxyr/cm-10.1-XXXXXXXXX-UNOFFICIAL-galaxyr.zip copy it to mobile and flash it on your mobile..
*********************************************************************************​
Updating the Build:
Code:
cd android/system
repo sync -j1
make installclean
brunch cm_galaxyr-eng
Big Thanks to Adam for his Efforts and Device tree..
Friends if i've missed some things please correct me ...
Gr8 mj! It will be better if u post ur error and how u solved.. By that it help others...
Sent from my GT-I9103 using xda app-developers app
Waiting for cm10.1 ROM now. Using Cm 10 and it is great
Sent from my GT-I9103 using xda app-developers app
I will start building 10.1 today.
Edit: This is my 500th post.
Sent from my CM10-powered GT-I9103
Adam77Root said:
I will start building 10.1 today.
Edit: This is my 500th post.
Sent from my CM10-powered GT-I9103
Click to expand...
Click to collapse
wow that's cool buddy...
Adam77Root said:
I will start building 10.1 today.
Edit: This is my 500th post.
Sent from my CM10-powered GT-I9103
Click to expand...
Click to collapse
adam wat abt cm10 ?? will u abonden it ??
Sent from my GT-I9103 using Tapatalk 2
vipul12389mehta said:
adam wat abt cm10 ?? will u abonden it ??
Sent from my GT-I9103 using Tapatalk 2
Click to expand...
Click to collapse
Not yet. The first builds will be only previews. If 10.1 gets as stable as 10 now is, I'll change to it. But there is work to be done on 10 as well and better to do it on a working build first. But I'm also very excited to see 10.1, so will definitely work on it.
Mj, before running the get-prebuilts command, should I run extract-files.sh first to get the vendor/cm directory as mentioned in karthick's tut for CM10 ?
I'm studying through your's, karthick's, and PA's compiling guides to get to know about compiling roms and trying to understand every step.
sarun_biotech said:
Mj, before running the get-prebuilts command, should I run extract-files.sh first to get the vendor/cm directory as mentioned in karthick's tut for CM10 ?
I'm studying through your's, karthick's, and PA's compiling guides to get to know about compiling roms and trying to understand every step.
Click to expand...
Click to collapse
Yes buddy you need to run it...
Friends updated the Guide with all the details and problems i have faced, so now you can simply follow the steps and build CM 10.1...
Ran in to trouble right in the beginning. My process does not support virtualization (not a n option in BIOS too) and so cannot install 64 bit Ubuntu on VM player.
Do you guys have any alternate suggestions or is it possible to use 32 bit Ubuntu to compile ?
I used wubi... dual boot...
sarun_biotech said:
Ran in to trouble right in the beginning. My process does not support virtualization (not a n option in BIOS too) and so cannot install 64 bit Ubuntu on VM player.
Do you guys have any alternate suggestions or is it possible to use 32 bit Ubuntu to compile ?
Click to expand...
Click to collapse
Even i also faced this problem, so i need to install the Ubuntu through the CD in different partition so that i have both Windows 7 and Ubuntu 12.10 64 Bit...
If you have any problem just PM me...
Cm10 official
Is there a official CM10 for galaxy r. If yes plz snd the link.
akirockstarr said:
Is there a official CM10 for galaxy r. If yes plz snd the link.
Click to expand...
Click to collapse
CM 10 & 10.1 are official for Galaxy R users and Unofficial from CM Team point of view...
1. CM 10 Thread.
2. CM 10.1 Thread.
Guys Check out xda-university.com An answer to all our development questions. :thumbup:
Everything at a single place.
I am trying to build CM 10.1 by your instructions and while extracting files from phone (cm10.1 beta 2.2) few "not found" & chmod errors occur. Logs (only error lines) following. Sorry I could'nt attach as file.Is it fine?
Code:
[email protected]:~/mydev/cm10.1/device/samsung/galaxyr$ ./extract-files.sh
remote object '/system/etc/wifi/bcm4330_mfg.bin' does not exist
remote object '/system/etc/wifi/nvram_mfg.txt' does not exist
remote object '/system/bin/wlandutservice' does not exist
remote object '/system/bin/macloader' does not exist
remote object '/system/bin/mfgloader' does not exist
remote object '/system/bin/nv_hciattach' does not exist
chmod: cannot access `../../../vendor/samsung/galaxyr/proprietary/wlandutservice': No such file or directory
chmod: cannot access `../../../vendor/samsung/galaxyr/proprietary/macloader': No such file or directory
chmod: cannot access `../../../vendor/samsung/galaxyr/proprietary/mfgloader': No such file or directory
chmod: cannot access `../../../vendor/samsung/galaxyr/proprietary/nv_hciattach': No such file or directory
remote object '/system/bin/brcm_patchram_plus' does not exist
chmod: cannot access `../../../vendor/samsung/galaxyr/proprietary/brcm_patchram_plus': No such file or directory
remote object '/system/bin/drexe' does not exist
remote object '/system/bin/npsmobex' does not exist
chmod: cannot access `../../../vendor/samsung/galaxyr/proprietary/drexe': No such file or directory
chmod: cannot access `../../../vendor/samsung/galaxyr/proprietary/npsmobex': No such file or directory
Why are we extracting files from phone? The device tree should be holding them right?
kishoreinme said:
I am trying to build CM 10.1 by your instructions and while extracting files from phone (cm10.1 beta 2.2) few "not found" & chmod errors occur. Logs (only error lines) following. Sorry I could'nt attach as file.Is it fine?
Click to expand...
Click to collapse
Not an issue you can proceed with next command, it will take care of these files.....

Pac man compiling help

Ok, so recently i decided to try and build pacman for my p3113....
I build cm10.1 from source daily so im possitive my build environment is functioning correctly...
My problem is, it will build pacman, but when i flash it all i get is a black screen....
Here are the details:
Ubuntu 13.04 running on an old insperon desktop, 8gb swap partition, processor has been upgraded to a amd k6x2 3.2ghz, i have 3gb of physical ram and a crappy video card.... Builds without issue...
The tablet is a p3113 running philz touch for recovery, and blackhawk dual boot mod...
Ive tried installing on first, and second system...
Where i think i went wrong:
After syncing sources, i followed the setup from cm10.1 instructions...
Cd ~/pac/
Repo init blahblah
Repo sync -j16
Cd ~/pac/vendor/cm
./get-prebuilts
Cd ~/pac/
Source build/envsetup.sh
Cd ~/pac/device/samsung/p3110
.extract-files.sh
Export USE_CCACHE=1
Cd ~/pac/
. build/envsetup.sh
Croot
Breakfastp3110....
If i missed something please someone let me know....
Sent from my MB865 using xda premium
Anyone?
Sent from my MB865 using xda premium

Question about AOSP

So i decided to build AOSP gingerbread from google's repo but yet i don't have a device tree. The readme in the S7500 opensource zip i downloaded from Samsung only tells me to replace bluetooth and iproute2 in build's environment. All of the commands that i am supposed to do are "make" and then "./build.sh" . After finishing these steps, there is no way i can make an otapackage because function is not implemented. The question is, can i flash the phone in download mode through the command "fastboot -w flashall" ?
Sent from my GT-S7500 using xda app-developers app

Categories

Resources