I am very new to Android development. My need is to
1. Modify an Android service in the Android OS source code
2. Then to build the Android OS with that modification
3. Then install it on a device for example Google Nexus S
At this time I am just trying to build the Android OS as it is following the guidelines given on the page source[dot]android[dot]com[/]source[/]download[dot]html
I am using Ubuntu 64 bit and I have achieved all the rest of steps successfully but the last step that is make command is not working.
I would like to know if anyone has followed this guideline as it is and come up with success.
Otherwise I will like to know if anyone can tell me whether the instructions on this page are exclusively enough to build the Android OS source code. If yes then why I am getting errors.
Regards,
Asif
Can anyone reply to this message or even point to me where should I put this question to get any answer? Thanks.
what kind of answer are you expecting if you didn't even tell anything about the error message?
My advice: Make sure you're on Precise. Then POST THE BUILD LOG, SCREENSHOT, ERRORS, WHATEVER THE BUILD PROCESS IS TELLING YOU WHEN IT STOPS.
Otherwise, go google it and leave these good people alone.
Related
Hi, so I'm a student learning Android app development and trying to modify the AOSP calendar to fit my needs so I downloaded the source code from git and made a project with 2.2 FroYo as the basis through Eclipse with ADT and all but I ran into a problem. So I run into:
android.provider.Calendar cannot be resolved into a variable
I did some research and found that the SDK apparently does not have the calendar code nor the database which is why I am running into these issues. So I learned from here jimblackler[dot]net/blog/?p=151 all that. He does have a solution except I have no idea what he is saying. He posted a bunch of code but I have no idea where that code is supposed to go in and I dont understand what he is trying to do with "content://calendar/calendars"
So I just decided to ignore the errors and obviously I couldn't compile it through eclipse so I made an unsigned apk and tried to install it unto the Emulator via ADB but as an unsigned apk it would not let me install it I tried to sign it by going through google's developer site but I am at lost again. I'm a noob to these things unfortunately..
I was wondering if anybody could help me out and point me in a good direction, I would be eternally grateful. Thanks.
P.S. sorry if I was being vague about the google's developer site and source code site but as a newbie I can't post links properly
Hi Everybody,
I want to ask for some informations what is need to do to build SlimRom for a new device. I found a lot of informations about CM, but nothing is really in a way that I really know what I have to do at the end. So is there a Howto, which describes it a little bit more in detail? A lot of howtos was found which describe to get a build-system, and to generate something for a know device. But everybody then describes only: you have to get the vendor files, made your Board-config but only on a very high level.
What I did:
- set up a building-server on ubuntu.
- get Slim-Sources branch JB4.3, and build the version for galaxysmtd to be sure that the buildprocess is ok.
- get "Nonreallyfree"-Opensources from Samsung for my I8200, and try to put them in the right places, and try to implement all needed files in the device/samsung/i8200 folder.
Up to now I think I have everything in place more or less, but the system told me that there is no rule for make 'bacon', but lunch seems to work right with setting the variables...
Up to now I did not used the blobs of the devices. The question is, if that is needed if I have the sources from open Samsung?
I know, jb43 is not the newest, but I start here, because up to now the sources are based on that level, and the kernel have no selinux implemented... If this start point will work, then I will try to go ahead with higher versions... end goal will be Slimkat...
Any help is very much appreciated!!
BR
SP
Hello everyone, today I tried to install bliss os and when the boot remains on the x86-64 writing: and I can not do anything.
And long ago I tried to install Android x86 and gave me the same problem some time ago.
How can I solve this problem?
A good start would be to move this questions to the official support thread found here https://forum.xda-developers.com/bliss-roms/bliss-roms-development/x86-bliss-x86-pc-s-t3534657
Second would be to provide relevant information about the device you are installing to. Device, make, model #, cpu chipset, your instalation method(there are several listen in the "install instructions" portion of the OP)
Right now you are simply stating "i tried this, it did not work, why not?"
Nobody can possibly assist you if you are not willing to provide useful information about your process. Also, please read through the above linked thread. there is much useful information already available for troubleshooting.
I am not an experienced dev, and only know enough to be dangerous. that said, i used twrpdtgen from https://github.com/twrpdtgen/twrpdtgen to generate what ought to be the berlna device tree with the necessary board files etc.
what do i have to do, specifically, to clone the twrp source via git/repo? can anybody here explain it like you realize i don't know what i am doing i'll figure git and repo out eventually, but this will go quicker if someone would enlighten me
which android version do i want to build twrp with? apparently 12.1 support isn't finished yet, so i should use 11 with aosp source?
note, for our deivce you need to use the script on upon boot.img as we've a/b format, grab from latest stock rom to gen yourself, or see attached. also, necessary to use WSL on windows with a linux distro, or a linux vm, python on windows will not work.
please feel free to use these if it furthers the cause of compiling twrp before i learn how to use git and repo and compile it.. hehe
I wanted to try my hand at this and start digging into git and repo. I got as far as getting all the files ready, setting up the tree where it needed to be, used ". build/envsetup.sh", then lunched with option 5, which is omni-berlna_eng, which is closest to the twrp minimal manifest build option.
After I lunch, the issue arrives with the fact that omni-berlna_eng uses a depreciated PRODUCT_STATIC_BOOT_CONTROL_HAL, whatever that means. So I tried using lunch option 2, which would be an aosp-arm64_eng, but that just gives me the error "#### failed to build some targets (1 seconds) ####".
As of now, I'm at a loss. I don't have the extra time to spend working on this to make it function, and I only get a few hours at a time to get a crack at it, but nothing seems to work.
Edit:
I should mention, this is my first attempt at anything android development. I got this phone as a secondary carry on and I've dirtyflashed Pixel Experience onto it using a method found for Moto G Power TONGA. Wanted to see if I could get TWRP running since dirty flashing killed my mms and calling services.
Hey guys, you have the excellent opportunity to prevent a complete nervous breakdown today.
I have been trying for days to build AOSP Android 13 for an Xperia 5 handset, according to the official guide: https://developer.sony.com/develop/open-devices/guides/aosp-build-instructions/build-aosp-android-13
But when I boot into Android I cannot access the camera (app crashes), WiFi does not work, SIM card is not detected (it prompts me to provide the SIM code, I see the signal icon in the tray light up, but no phone reception or internet connection), dialling a phone number and pressing "Call" crashes the whole system and the phone reboots (I find that quite funny for some reason). Probably something else too that I have forgotten about.
Currently I am running AOSP Android 13 on Sony's msm-4.19 kernel.
I have managed to follow along all the way through their guide, flashed AOSP to my device, together with the vendor software binaries. Everything according to their instructions, but is this really the intended end result?
What I suspect is some kind of kernel/driver problem somewhere, so I have tried to recompile the kernel, but to no avail. I am not knowledgeable enough to troubleshoot within the actual source code files or makefiles. So I am sitting here calling for any help at all.
You lot seem very knowledgeable in this field, your suggestions will probably help me get this phone going before my rent is due in two days, I have lost faith in myself (lol)
tbh, using open device to build aosp isn't going well.
gonna suggest to bringup lineageos tree from scratch. (yep, it's hard. but doable)
and yea, i tried bringup los tree for xperia 5 / 1. except it didn't boot, and i don't have device to catch certain crash log
loipuru said:
tbh, using open device to build aosp isn't going well.
gonna suggest to bringup lineageos tree from scratch. (yep, it's hard. but doable)
and yea, i tried bringup los tree for xperia 5 / 1. except it didn't boot, and i don't have device to catch certain crash log
Click to expand...
Click to collapse
Thanks for your input loipuru, do you know how one would go about bringing up los tree from scratch? Do you need to edit the source code much? Any resources that could help when doing research?
terminal_overflow said:
Thanks for your input loipuru, do you know how one would go about bringing up los tree from scratch? Do you need to edit the source code much? Any resources that could help when doing research?
Click to expand...
Click to collapse
i did bringup for scratch, but it didn't boot (well, i don't have device to catch pstore log and see why)
still need to fix something before i can actually made it public