I have experience modifying the Lollipop AOSP source and building images and flashing them onto devices but I want to modify and build for a wearable.
There is an android-wear-5.0.0_r1 tag and I've downloaded that source code but there's in it which is specific to a wearable - for example there's no new wearable source code, and the lunch menu contains android device lunch items not wearable device lunch items (i.e. the lunch menu doesn't contain dory, sprat, minnow build options) so there's no way of building it for a wearable.
Does anybody know if its possible to build an image for a wearable?
mungbeans said:
I have experience modifying the Lollipop AOSP source and building images and flashing them onto devices but I want to modify and build for a wearable.
There is an android-wear-5.0.0_r1 tag and I've downloaded that source code but there's in it which is specific to a wearable - for example there's no new wearable source code, and the lunch menu contains android device lunch items not wearable device lunch items (i.e. the lunch menu doesn't contain dory, sprat, minnow build options) so there's no way of building it for a wearable.
Does anybody know if its possible to build an image for a wearable?
Click to expand...
Click to collapse
Were you able to accomplish anything? We are also working with a custom ROM but we don't see any way how we can merge and build the branch Android W 5.0.0_r1. I don't think is the full source for Android Wear
Related
Hello!
Im currently trying to build a vannila froyo 2.2 rom from the source! How do i flash the images when im ready? Is there something like fastboot on the g1 or htc magic?
Landroid
I haven't had the time to try to build myself, but wouldn't you be better off starting with the Samsung open source for your carrier/model rather than trying to figure out all the changes you'd need to make to get AOSP to run on the Tab?
BuglessFan said:
I haven't had the time to try to build myself, but wouldn't you be better off starting with the Samsung open source for your carrier/model rather than trying to figure out all the changes you'd need to make to get AOSP to run on the Tab?
Click to expand...
Click to collapse
Erhh - Samsung open source only contains the kernel. You need the rest of Android, which is what the AOSP is for!
Regards,
Dave
Don't know about the others, but the one for the SCH-I800 on VZW is not just the kernel. All of the things like the custom notification bar/settings for white and black levels, et cetera, go well beyond vanilla android in the Tab. I haven't gone through the platform.tar, but it has notices about stuff for, TouchWiz, et cetera (now whether it can actually run as built directly from what they've made available all bets are off, I know a direct compile of the kernel code didn't work for me, but I haven't had time to do more than a simple straight attempt to build and may have screwed something simple up). It's around 85MB for the DJ11 code for Verizon.
Edit: I'd understand if you needed most of it from AOSP though for a full build, and stand corrected.
And how do i flash the created system.img and data.img? The kernel will be in the zImage format as im going to build the kernel from samsung's opensource files!
Landroid said:
And how do i flash the created system.img and data.img? The kernel will be in the zImage format as im going to build the kernel from samsung's opensource files!
Click to expand...
Click to collapse
You don't. Samsung uses different partition layout and formats.
Use the Samsung tar files to overlay over AOSP as described in their readme file.
Ah ok! Thank you
from Readme file:
How to build:
< Kernel >
1. Unzip SPH-P100_Kernel.tar.
( You can find SPH-P100_Kernel.tar in the same directory with this README.txt . )
2. Refer another "README.txt" in the tar file to build the kernel source code.
< Platform >
* NOTICE *
Galaxy Tab is launched in many countries, including Europe and North Amarica.
S/W is almost the same but there are some differences between the European version(GT-P1000) and the US Sprint version(SPH-P100).
The open source codes to be open here are only the differences.
1. Get Android open source code:
: version info - Android froyo 2.2 (android-cts-2.2_r2)
( Download site : http://source.android.com )
2. Get GT-P1000 open source code
: GT-P1000_OpenSource.zip
( Download site : http://opensource.samsung.com )
Unzip it, then you will see the file GT-P1000_Platform.tar.bz2 which includes the platform source code.
3. Overwrite GT-P1000 Platform OpenSource to the Android open source.
4. Get SPH-P100 open source code:
: SPH-P100_OpenSource.zip
( Download site : http://opensource.samsung.com , version info : DJ14 )
5. Overwrite SPH-P100_Platform_DJ14 OpenSource to the Android + GT-P1000(European) Platform open source code.
6. Overwrite the Platform source code that comes from the Sprint version(SPH-P100_Platform_DJ30).
7. Do "make"
Click to expand...
Click to collapse
Landroid said:
And how do i flash the created system.img and data.img? The kernel will be in the zImage format as im going to build the kernel from samsung's opensource files!
Click to expand...
Click to collapse
If I understand correct. (for the kernel at least) You could just take a package like monks then swap out the zImage and *.ko files for the samsung ones. resign the zip. Then flash it from the clockworkmod recovery.
I believe we need repo init -b android-cts-2.2_r2 ... and overlay the Samsung tar contents on top of it.
Hi
I have successfully upgraded my Ideos X5 U8800 to 2.3.5 official Gingerbread, rooted it, and then repartitioned it using Blepart recovery. Subsequently I have checked out cm11 source, including Blefish repositories/code for the U8800 (thanks for good work, by the way!), compiled/built and installed a ROM. This was my first build.
OK. Good so far. Only I am looking to build cm10.1 because my goal is to eventually get this handset running Ubuntu Touch. Therefore, the next step is to get it running on cm10.1.
My problem is that I cannot find the source I need. I have tried to set up a fresh source tree and check out cm10.1 source combined with Blefish's source by specifying branch cm10.1 for the latter, using the files I used in .repo/local_manifests to get the cm11 device source etc. from Blefish. However, something seems to be missing as the lunch command fails and compilation aborts. Also, I can see that development has been discontinued on this branch for the U8800.
Any suggestions?
The cm-10.1 branch is deprecated, and I am not planning to update it as cm-11.0 is better in any way.
Is the Ubuntu Touch source code only based on cm-10.1 code though? Maybe you could have success using the cm-11.0 code as it is right now? I am not familiar to how Ubuntu uses the lunch commands, it might be different than Android's default.
Blefish said:
The cm-10.1 branch is deprecated, and I am not planning to update it as cm-11.0 is better in any way.
Is the Ubuntu Touch source code only based on cm-10.1 code though? Maybe you could have success using the cm-11.0 code as it is right now? I am not familiar to how Ubuntu uses the lunch commands, it might be different than Android's default.
Click to expand...
Click to collapse
Thanks for the quick response!
The Ubuntu Touch guide specifically states cm-10.1, but I will sign up with their forums and check whether I can use cm-11.
The following passage from the Ubuntu Touch Porting Guide gives the impression I might be able to base my work on cm-11? Would you agree?
"For quick reference, these are the current components used from Android:
Linux Kernel (stock Android kernel provided by the vendor, with a few changes to support some extra features needed by Ubuntu, such as Apparmor)
OpenGL ES2.0 HAL and drivers
Media (stagefright) HAL, to re-use the hardware video decoders
RILD for modem support
As Ubuntu is running as the main host on top of an Android kernel and the communication between the Android services and HAL happens via Binder, Sockets and libhybris. "
I am hoping this could work, as it would be a tremendous help, now that I have a running ROM built on 20 May with your source tree for the device specific code etc. which works like a charm! :good:
Best regards,
aribk
Hello!
I'm hoping to get custom kernel & rom development up and running quickly for the G5 community, and have created a git repository which provides a kernel source base to start with.
What I've done is taken the v10a release sources and modified them to work with build directories and multiple variants. (should they be unlocked or receive the CodeFire treatment at any time)
Here's where to start: https://github.com/jcadduono/nethunter_kernel_g5/tree/stock-6.0
If you'd like a somewhat updated kernel, the stock-6.0.y branch will be patched from Linux 3.18.y branch at kernel.org, see:
https://github.com/jcadduono/nethunter_kernel_g5/tree/stock-6.0.y
Different from the absolute stock defconfigs, I've made the following changes:
Module signature verification disabled
Unnecessary debugging flags separated into debug_defconfig (use EXTRA_DEFCONFIG=debug_defconfig to enable them)
Flags that were previous set to module (=m) have been set to =y (built-in) in case incompatibilities are unable to load stock modules
Each known variant & target is listed in build.sh comments. The default variant when building with ./build.sh is h850 with debugging disabled.
When using the Makefile, VARIANT_DEFCONFIG=variant_xxx_defconfig adds the additional settings per variant to the target defconfig. (by default stock_defconfig)
build.sh is set up to automatically build a dtb.img after creating the kernel Image.gz based on whichever variant you've built for.
You can use ./menuconfig.sh to modify the stock defconfig, or you can copy the stock_defconfig to another name such as my_defconfig and use TARGET=my ./menuconfig or TARGET=my ./build.sh
It's easier to just set the default target in build.sh/menuconfig.sh - each have their configuration options near the top of the files.
Be sure to edit the config variables in build.sh and menuconfig.sh before using. The VERSION file gets appended to the kernel version shown in `uname` when using build.sh.
The toolchain must be pointed to the correct location before it can build. Be sure to have libncurses5-dev and colordiff packages installed for menuconfig.sh.
For a toolchain, I recommend using the GCC Linaro aarch64 5.3 2016.02 release. You can use basically any aarch64 toolchain though.
Download here: https://releases.linaro.org/compone...o-5.3-2016.02-x86_64_aarch64-linux-gnu.tar.xz
You can start by forking my repository on GitHub and giving it your own name if you like. Extra interesting commits are available in the other branches that you should be able to cherry-pick without issues should you be interested in them.
Looking to test your kernel Image.gz + dtb.img?
Look no further than my LazyFlasher repository!
See here: https://github.com/jcadduono/lazyflasher/tree/kernel-flasher
Simply do:
Code:
git clone -b kernel-flasher https://github.com/jcadduono/lazyflasher.git kernel-flasher
cd kernel-flasher
cp /path/to/Image.gz /path/to/dtb.img ./
make
(simply place your kernel Image.gz (optional) and dtb.img (optional) in the root of the repository and type make!)
And you'll have your own dynamic kernel flashing zip for custom recoveries!
The kernel-flasher repository is capable of great things. You can create scripts in patch.d to do anything you like.
Add files to the ramdisk-patch folder and create a script that copies them into the $ramdisk folder and they will be rebuilt into the ramdisk!
By default, no-verity-opt-encrypt is there as an example.
Using setprop in patch.d scripts allows you to set props in default.prop with ease.
Add functions to patch.d-env to make them globally usable across patch.d scripts.
See other branches for more examples, like how to add f2fs lines to the fstab, or patch for system mode SuperSU.
LazyFlasher is the installer used in the Kali NetHunter project. You can also find more examples in the kali-nethunter GitHub!
Good luck, and happy kernel developing!
Thanks so much for posting this.
Code:
./obligatoryn00bstatement
Sorry for not being too knowledgeable here (yet?) and if this sort of comment doesn't belong.
I am a Computer Science major who really wants to learn some skills to hopefully give back to the community.
Is this an area that I could be of use or should I perhaps spend more time going through material on the XDA-U site?
toefurkey said:
Thanks so much for posting this.
Code:
./obligatoryn00bstatement
Sorry for not being too knowledgeable here (yet?) and if this sort of comment doesn't belong.
I am a Computer Science major who really wants to learn some skills to hopefully give back to the community.
Is this an area that I could be of use or should I perhaps spend more time going through material on the XDA-U site?
Click to expand...
Click to collapse
I'm a little tired and somewhat intoxicated here at 3:45 AM so this is going to be a bit of rambling and so on...
While it's certainly a good idea to study up on what interests you before digging into it, sometimes it really can be easier just to dive in to your hobby.
I'm a high school drop out, never made it through college. Everything I've learned is by taking the great work done by the open source community and reading their code and applying it to other projects. That's the great thing about open source and nonrestrictive licenses. Everything is there for you to figure out, make changes, borrow code, run into problems, and the best part - search for solutions that others have already provided in their struggle to do exactly what you're doing.
Have an idea for a great feature? You can probably find it already implemented in another kernel somewhere.
Find the work someone else has done and modify it to fit your needs, but don't forget to give them credit for their work that you've used!
If you're going to start writing your own code, be certain to keep it tidy and variables/functions with meaningful names and comments so that not only others can understand and learn from it, but that you can return to the same code later on and understand it. Confusing code is how bugs tend to show up and become almost impossible to squash.
What I'm trying to get across here is don't be afraid to not be original. Don't be afraid to use others work to accomplish what you want, so long as they receive some attribution. The quickest way to learn how things work is by understanding what's already there and available to you.
You'll notice that there's projects all over XDA with special features ported from one device to another. Isn't it great having the all the best features people have added to other devices on one really nice device that you have?
PS I've never been on the XDA-U site before, so I can't give an opinion there.
I forgot what I was on about so I'll end this here lol.
?jcadduono you're on fire man thank you for everything you've been doing so far with such little resources.
Sent from my LG-H820 using XDA-Developers mobile app
jcadduono, thanks for the info and wonderful words of wisdom!
I totally agree on what you're saying and my goal is to try diving into this as a hobby. The hardest part for me isn't so much the coding part, but just figuring out a starting point to get grounded and build upon and I feel like what you've provided here is perhaps the starting point I need. Now it's just up to me to push myself in my free time.
Hi, i am new to kernel developing, but i did some roms myself before, so no total linux noob.
I cloned your 6.0.y and want to start from there, but im a little bit lost. Do i need to follow the steps @ github, or is your branch kinda pre setup ?
Toolchain path is also set to the one you gave a link too.
Pinu'u said:
Hi, i am new to kernel developing, but i did some roms myself before, so no total linux noob.
I cloned your 6.0.y and want to start from there, but im a little bit lost. Do i need to follow the steps @ github, or is your branch kinda pre setup ?
Toolchain path is also set to the one you gave a link too.
Click to expand...
Click to collapse
Hopefully once the toolchain path is set you should only need to run ./build.sh to actually build the kernel and dtb.
You may be missing some items for menuconfig.sh, which should just be solved by apt-get install colordiff libncurses5-dev
If building inside a ROM tree, it should be fairly simple for developers to adjust their ROM configs to add more to the kernel make command line, such as VARIANT_DEFCONFIG.
No matter what i do, kernel builds, but no dtb.img will be created. Any ideas where to look / what to test ?
I have stock-6.0.y, and did the h850 one.
Hi, is the stock-6.0.y branch removed?
I didnt find it. and need the right defconfig
greetz
mericon
Hi,
I want to learn more about Android kernel development so I'm trying to compile AOSP (Android 7) from source for my Nexus 7. I have prior experience doing Linux kernel development but the real hurdle for me is the Android build environment.
I have checked out android-7.1.2_r39 with the proprietary blobs for Nexus 7 and I've made it to the point where I need to choose a target.
However because I'm trying to compile Android 7, `full_grouper-userdebug` does not show up on the build target list when running `lunch`.
Is it enough to grab the /device/asus/grouper directory from a tree where it is included and add that to my AOSP tree or is there something else I need to do to compile Android 7 for this device?
Hello,
For those interested in the original kernel source code for the SM-T813 :
As I am learning how to make ports for Android, I am trying to train on the original sources of the Linux kernel for the SM-T813.
After several weeks of research, I couldn't find the origin of the different kernel repositories.
Also on https://opensource.samsung.com, it was impossible to find the sources. So I contact them at the end of January to have an access to this sources...
... And they are now available !
You can download them on https://opensource.samsung.com (search SM-T813 at mobile phone on release center) or on my repository at https://github.com/Akipe/android_kernel_samsung_gts210vewifi_original_samsung
It is based on the T813XXS2BTK3 firmware with Android 7 Nougat.
I will see to ask for sources of similar tablets.
Will this help with porting new Adnoid version to these tablets?
Pawel_ said:
Will this help with porting new Adnoid version to these tablets?
Click to expand...
Click to collapse
I don't think so,
Kernel sources for this tablet already exist, and are ported to newer versions.
It is more useful for those who want start from scratch, and want to inspect the unmodified source code.
But my goal would be to successfully create from scratch for the SM-T813 LineageOS 14.1 (Android 7); and then try to move to the latest versions.
Since I am a beginner, I still have a lot to learn, and I don't have much time, so we will see