Hello all,
Im newbie in the site and also in Android AOSP.
I would like to know if is possible:
I have a AOSP X86 Emulator and I made some changes in HAL . So I desire to test in a Pixel 6 . i believe that I need to install the custom ROM.
Some Steps that I identified.
1- Convert my X86_64 AOSP Android 12 Custom ROM => ARM.
2- De-activate BootLoader .
3- Flash my Pixel 6.
Would you help me if these steps are correct?
I have no idea where to start. Any suggestion to tacke the task is well apreciated.
Thanks a lot
Convert? I'm not sure that is the right word here, though I know it can be done if you have the source code. In essence you would be compiling with ARM as the target processor instead of x64. From there your steps are essentially correct, though I would take steps to ensure you can recover from a problem prior to unlocking the bootloader and flashing the ROM.
Thanks a lot for your reply!. Sorry to bother again.
In my case I did some changes in HAL AOSP Master X86_64 and I've tested in Cuttlefish Emulator (aosp_cf_x86_64_phone-userdebug).
If I didn't misunderstand, what you suggest firstly is to compile, Im a little confused in which I have to use:
lunch:
1-armv8-eng
2-aosp_arm64-eng
3-aosp_cf_arm64_phone-userdebug
4-aosp_oriole-userdebug ->( I guess this one).
and then continue with the steps detailed above.
Many Thanks for your help!
@Palinamarne And I wouldn't be able to tell you which one to use. My days of tinkering that deeply beneath the hood of Android are long since behind me.
@Strephon Alkhalikoi No problem! I'll play around a bit and put the details here. Thank you very much for your help.
Were you able to run this custom aosp build in an emulator?
Related
Dear experts,
like many ppl, I am new to Android Development, and would be able to cook my own rom with amazing home-made features before the end of the week... and I want it to be easy, funny, and eventually Fast....
... Indeed, I don't want all of this, so I'll try to be realistic in my incoming questions and beg for your indulgence if some things sound stupid / inexact / already documented and so on : I have performed a long search process before I decided to post here and would not ask it otherwise.
So, first, here's what I have know about android:
- Android Architecture (various layers)
- Android + java programming (beginner with both but skilled with general OOP and smartphone -iPhone- programming)
- Rom flasing process : rooting, bootloader / recovery flashing , using adb, filesystem of a ROM
- Android official source building (from git repository) and patch apply.
- Basic cooking without any source code modification: use of dsixda's kitchen with xda members' home-made roms mainly
Then, the material I am working with :
- Max OS 10.6.5
- A HTC - Tattoo : rooted, with nandroid and busybox installed (also have an available HTC - Hero)
- adb 1.0.26
- HTC Android Kitchen 0.106 - by dsixda
- Android official source from http://android.git.kernel.org/
Now, what I don't know about is advanced cooking... I read a lot about ppl wondering the same, and generally there was no basic answers (not to mention guide/tutorials).
Since I will surely be the nth to ask this, let's try to ask a specific question.
I downloaded from Android github a patch I am very interested in. This patch applies on the framework and does not impact any other layer (especially not the kernel nor the hardware related libs). After building the source, I thus get a framework.jar I would like to replace some target framework.jar with .
I was quite sure it was not very bright to do such with a custom ROM, even a quite standard FroYo-based one, since there was little chance that such a cooked-rom used a virgin framework taken as-it from android github. But I tried anyway with some of the FroYo-based roms taken from the xda list for my tattoo device. I basicely replaced the framework.jar with mine.
... and indeed, it failed : I kept getting stuck at the boot screen everytime I do such.
So.... I am trying to understand what I do wrong.
- I am quite sure I miss some signing process, but although I read many threads about such a signing about apk files, I did not manage to figure out how to do this with frameworks / jar files. Could someone bring me some light about this?
- Provided the signing is not the (only) problem here, could someone explain where / why I am wrong?
- Eventually, since I did not manage to find full source for a FroYo-based (running) cooked rom , do you know of such a source repository I could work with instead of working with android official sources (including the framework java files + compatible with HTC-tattoo / HTC-hero if possible)?
Thanks for all of you for reading until here, whatever your answers (or silence) may be.
And thanks in advance to those who may have some answers or any constructive criticism.
Roger_Rabbit
--------------------------
An old fashioned rabbit
First a short question. What is the device configuration.(For example:https://github.com/TeamICS/android_device_htc_heroc) Which information does it contain? I don't think it's the whole Rom, but they update it, change stuff and so on?
Now my actual question:
I want to port a Kernel+System on an unsupported device.
Where do I have to start. Is there a difference between building it from source or port one from a similar device? Is one solution slower, more complicated or anything? There are many tutorials for porting, just bundle a system with a working kernel, but what to do if I want to have the Kernel also?
How do I extract the Device Proprietary Files without an github of the device?
Links, short explanation of the steps or anything else would be helpful.
I am sorry if this post seems to be ill informed, but I am searching and searching and can't find really helpful information..
chaoskoch said:
First a short question. What is the device configuration.(For example:https://github.com/TeamICS/android_device_htc_heroc) Which information does it contain? I don't think it's the whole Rom, but they update it, change stuff and so on?
Now my actual question:
I want to port a Kernel+System on an unsupported device.
Where do I have to start. Is there a difference between building it from source or port one from a similar device? Is one solution slower, more complicated or anything? There are many tutorials for porting, just bundle a system with a working kernel, but what to do if I want to have the Kernel also?
How do I extract the Device Proprietary Files without an github of the device?
Links, short explanation of the steps or anything else would be helpful.
I am sorry if this post seems to be ill informed, but I am searching and searching and can't find really helpful information..
Click to expand...
Click to collapse
First off what device do you have?
This link might be helpful
How to Port Android to Another Device
Now in regard to your questions i'll do my best to answer them best I can. The device configuration think of it as a fingerprint every fingerprint is unique (Although some a very similar), basically when building from source is tells the build what device you want the version of android your compiling to run on. They update and change the device configuration to reflect changes in the different versions of Android (Going from Gingerbread to ICS for example). Porting Kernels is not easy if you don't know C, things about embedded systems, basic Linux knowledge, among other skills but take a look at Guidance regarding Kernel porting, and what do you mean by port system? Here is a basic place to start for kernels AOSP Building Kernels and Building Your First Kernel. Yes their is a difference between porting a kernel and building from source, porting implies taking a kernel from device A and porting it to device B, while building from source means your building directly for device A. Porting in your case is probably going to be harder then building from source. If you want to have the kernel also again you have to modify it to run on the device you are porting it too. To extract proprietary files you have to hook your device up to your computer, turn on usb debugging, and using ADB run these commands:
Code:
cd ~/android/system/device/motorola/sholes/ # Replace Motorola and Sholes with your vendor such as HTC, Samsung, etc. and your device codename
Then run:
Code:
./extract-files.sh
Look at this guide for more info Compiling ICS from Source. Hope this helps you in some way :good:.
Hello there guys,
As we all know we only have 3? 4? developers for the HOX+ . And they are really doing all they can to help keep the phone upto date.
But as we all know they are all busy and can't update their roms that much any longer.
EDIT: Lloir already has a guide : http://forum.xda-developers.com/showthread.php?t=2187266 but I don't think he covers how to fix camera and gps and stuff
So! Is it possible to make guide on how to compile the rom from the source? I know tombridden and lloir already made a one post guide on how to build some roms but it was too specific.
I now have an extra machine (a laptop) with 500gb free storage and ubuntu as the main OS. It's quite powerful too with 6gb RAM and i7. So Why not use it to help the community while others are busy? In the meantime I will look around for some guides for other phones but I don't think they will help that much.
And please include the answers to those questions if you make a guide:
1- What to do to fix camera/GPS/wifi/Data/sensors ?
2- What approach should I take when compiling a new ROM. For example: there are no developers for PACMAN , how will it differ during compiling between it and AOKP/CM/AOSP .
I am talking about a rom that wasn't approached by Lloir so he won't have the repos for them. What to do then?
Thanks a lot and I can't wait to help
@Lloir @tombriden @PippoX3 @mike1986. and any other developer out there.
you can start by looking at XDA-University
The reply is correct. All of us moved first steps studying at XDA University.
Anyway the case is more complex than others.
For this device there are really few developers. Other device have a lot of support from constructors, many dev and the team-work result in a lot of kernels/roms to flash for the final user.
If you wanna taste the happyness for build a rom, I'll send you a guide to setup your ubuntu, download the sources and build.
But in this case, where enrc2b is not officially support, the things are more difficult.
You must have a minimal practical with java, cpp, android and kernel code (if so).
For the moment I'm in trouble to build an AOKP 4.2.2 with new kernel. I haven't device to try, 'cause the hard is build&&try continuosly.
Not the fact to have a pc turned on for hours and hours.... and the eyes&&mind open for hours and hours... but the patience to continuously try time after time.
Now I am in a dead point... many users like have S2W enable on new CM kernel... but.... the kernel won't!
Thanks a lot anyway. Thanks to @Lloir, @tombriden, @maxwen and alls who's workin' for this device.
Stay tuned....
PippoX3 said:
The reply is correct. All of us moved first steps studying at XDA University.
Anyway the case is more complex than others.
For this device there are really few developers. Other device have a lot of support from constructors, many dev and the team-work result in a lot of kernels/roms to flash for the final user.
If you wanna taste the happyness for build a rom, I'll send you a guide to setup your ubuntu, download the sources and build.
But in this case, where enrc2b is not officially support, the things are more difficult.
You must have a minimal practical with java, cpp, android and kernel code (if so).
For the moment I'm in trouble to build an AOKP 4.2.2 with new kernel. I haven't device to try, 'cause the hard is build&&try continuosly.
Not the fact to have a pc turned on for hours and hours.... and the eyes&&mind open for hours and hours... but the patience to continuously try time after time.
Now I am in a dead point... many users like have S2W enable on new CM kernel... but.... the kernel won't!
Thanks a lot anyway. Thanks to @Lloir, @tombriden, @maxwen and alls who's workin' for this device.
Stay tuned....
Click to expand...
Click to collapse
That's what i did already. I set up the periphals/kernel/device info GITs and now i am looking for the roms, I found CM and stuff but I can't find PURE AOSP , does that mean i must download it and upload it?
I also have Oracle java installed. Do I have to have open JDK?
Ghand0ur said:
That's what i did already. I set up the periphals/kernel/device info GITs and now i am looking for the roms, I found CM and stuff but I can't find PURE AOSP , does that mean i must download it and upload it?
I also have Oracle java installed. Do I have to have open JDK?
Click to expand...
Click to collapse
https://github.com/pure-aosp/android
Lloir said:
https://github.com/pure-aosp/android
Click to expand...
Click to collapse
Now that we begin to have a solid CM base, will possible to build at least CM for enrc2b for noobs too.
And eventually "port" device/kernel" parts to others platforms. So who like e.g. PA can do...
If you agree, I can paste my personal appoints to a guide, from client setup (Sun java don't works) to the build zip rom.
Updated and corrected to last KK.
PippoX3 said:
Now that we begin to have a solid CM base, will possible to build at least CM for enrc2b for noobs too.
And eventually "port" device/kernel" parts to others platforms. So who like e.g. PA can do...
If you agree, I can paste my personal appoints to a guide, from client setup (Sun java don't works) updated and corrected to last KK.
Click to expand...
Click to collapse
Go for it. Saves me doing it which I was about to do
Sent from my One X+ using Tapatalk
Hello wise XDA sages,
Today I am working on a project that has me working with the Android Kernel and I need some help / directions from you all who know much more on the subject than me. I am trying to get the USB Griffin Powermate Dials to work with Android (via OTG), so I can use them in an application I am writing. Luckily, this has already been done: youtube.com/watch?v=xt6Ny8lG15s so I know the driver is available for Android. Moreover, the individual was nice enough to post his modified driver here: gist.github.com/tlorens/488752123c056202ac31
So, I have spent the last two days reading and studying the android Kernel and how to make/compile your own kernel. The only instructions via Google leave me with a few questions. I was able to build a generic kernel from scratch, but have found less documentation on how to add the driver in question and then how to load the zImage once it has been created to a device so that it will use it.
Could any of you help me with this project, or point me toward more detailed resources that can walk me through this process? I have a feeling that once I do this once, it will be easy to do in the future.
My questions are:
1. How do I take the above Android driver and integrate it into an Android Kernel for one of the following phones: Galaxy Nexus, Nexus 10, Nexus 7, Nexus 5, Galaxy S4, Galaxy Tab 4 (I am lucky enough to have access to many devices - which is the easiest to use? Does it matter?).
2. Do I need to make an entire AOSP rom to make this work, or will the kernel be sufficient.
I appreciate you masters helping a noob at kernel work. If this becomes hard to do, I would even be willing to toss anyone willing to help some cash via paypal for a step-by-step set of instructions for making the Powermate work on any of my devices. Biggest thing, is I want to learn how to do this myself
As always I appreciate this community,
Larry
Hello guys,
I hope I'm in the right forum.
I've studied several days, if it is possible to update my Smartbook S10 (smartbook.de/produktfeatures/72/technische-daten is the link from the manufacturer) from Android 4.4.2 to at least 7 (best case to the newest 9, that I'm trying atm).
It has got only 8GB of space, so I wanted to ask, if it's even possible with that low space and processor (RK3026)? Couldn't find clear information about this.
I've come that far, that I've created a new AOSP device tree and inserted all data I know/could find. But it fails now at the kernel.
I've tried to compile the common actual kernel 4.19 with Google's Android tools and getting this error:
Code:
/home/test/Android_Kernel/build/_setup_env.sh: line 28: /home/test/Android_Kernel/build.config: No such file or directory
My build repo lays at /home/test/Android_Pie. What am I missing or doing wrong?
Thanks in advance
Greetings
Andi448 said:
Hello guys,
I hope I'm in the right forum.
I've studied several days, if it is possible to update my Smartbook S10 (smartbook.de/produktfeatures/72/technische-daten is the link from the manufacturer) from Android 4.4.2 to at least 7 (best case to the newest 9, that I'm trying atm).
It has got only 8GB of space, so I wanted to ask, if it's even possible with that low space and processor (RK3026)? Couldn't find clear information about this.
I've come that far, that I've created a new AOSP device tree and inserted all data I know/could find. But it fails now at the kernel.
I've tried to compile the common actual kernel 4.19 with Google's Android tools and getting this error:
Code:
/home/test/Android_Kernel/build/_setup_env.sh: line 28: /home/test/Android_Kernel/build.config: No such file or directory
My build repo lays at /home/test/Android_Pie. What am I missing or doing wrong?
Thanks in advance
Greetings
Click to expand...
Click to collapse
Hello Andi,
I've got a similar question about the device, although I'm not at all an expert as you seem to be. Just want to run it with an COS (lineage, etc). So I am looking for a COS for this device.
Did you manage to solve your problem?
Do you have any idea what COS would run on a smartbook S10?
Thanks for your answer
Hi Willi,
I'm sorry to disappoint you, but I gave up this project after a few days, because I couldn't find any further information and I'm no dev at all. This was my very first attempt to compile a new kernel for an (additionally pretty unknown) Android device. The thing, which helped me the most was watching YouTube videos from https://www.youtube.com/channel/UCnGqG_jyyXmTzdamBpKfeHA (AlaskaLinuxUser AKLU).
Maybe some more experienced users can help you here.
Greetings