Develop Bugs

So what time can we expect a 2.2 port on here then you clever cookers?!

Just wondered who will be first to port it and how long it takes them as it's on the developer sdk download!?
The stopwatch is running you smartarse's!

The SDK is developing apps - it is not the OS itself.
With respect to the actual Froyo source code, it seems that some code has been release to the AOSP, but not all of it. There can't be a full Froyo ROM until all the code is released, though you can be reasonably certain that Cyanogen and others will be adding what is available to their existing builds.
Regards,
Dave

A few questions about the new aosp update

Here it is :
1. How exactly are updates pushed to aosp? Are they pushed only when they announce a release like the new 4.0.4? Looking at this page https://android-review.googlesource.com/ it appears the updates are in real time but why is it that we are waiting for 4.0.4?
2. Let's say I build from the latest aosp now including the proprietary drivers specific to my nexus device. Is the result exactly the same as factory ota image? Or does Google make some small specific changes specific to devices?
3. Why is it that non nexus devices that get ICS unofficial roms even after the official release from the manufacturer still lack some functionally? Why is it not possible to use the proprietary libraries and drivers from the official update?
4. Does this page https://android-review.googlesource.com/ include all the changes the Google makes to aosp? What are the important ones compared to 4.0.3?
5. How do rom developers like teamkang or gummy etc port their 4.0.3 roms to 4.0.4? Do they have to add their extra code manually to each file or do code management tools like git take care of everything?
Sorry about the long questions I'm just really curious.
Thanks!

ArmanUV said:
Here it is :
1. How exactly are updates pushed to aosp? Are they pushed only when they announce a release like the new 4.0.4? Looking at this page https://android-review.googlesource.com/ it appears the updates are in real time but why is it that we are waiting for 4.0.4?
2. Let's say I build from the latest aosp now including the proprietary drivers specific to my nexus device. Is the result exactly the same as factory ota image? Or does Google make some small specific changes specific to devices?
3. Why is it that non nexus devices that get ICS unofficial roms even after the official release from the manufacturer still lack some functionally? Why is it not possible to use the proprietary libraries and drivers from the official update?
4. Does this page https://android-review.googlesource.com/ include all the changes the Google makes to aosp? What are the important ones compared to 4.0.3?
5. How do rom developers like teamkang or gummy etc port their 4.0.3 roms to 4.0.4? Do they have to add their extra code manually to each file or do code management tools like git take care of everything?
Sorry about the long questions I'm just really curious.
Thanks!
Click to expand...
Click to collapse
1. All Nexus OS versions are AOSP. We are waiting for the OTA because Google only sends the update to a few people at a time, because sending it to everyone all at once would make their servers very unhappy.
2. You'd just be missing the radio I believe.
3. The proprietary stuff is for their skinned OS versions, and is not necessarily usable for vanilla Android.
4 and 5 are beyond me :/
Sent from my Galaxy Nexus

I s it possible the rooted Galaxy Nexus to get the OTA ICS 4.0.4?

ragnarokx said:
1. All Nexus OS versions are AOSP. We are waiting for the OTA because Google only sends the update to a few people at a time, because sending it to everyone all at once would make their servers very unhappy.
2. You'd just be missing the radio I believe.
3. The proprietary stuff is for their skinned OS versions, and is not necessarily usable for vanilla Android.
4 and 5 are beyond me :/
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
thanks. you misunderstood my first question though. I know that nexus images are based off aosp. What I meant is that the changes on android gerrit review system are public and in real time. So why is it that a release like 4.0.4 is a big deal?
CakraMas said:
I s it possible the rooted Galaxy Nexus to get the OTA ICS 4.0.4?
Click to expand...
Click to collapse
Not the best place to ask this question but I think if you're on yajuko and you have stock bootloader (not cwm) then you may be able to get ota but you'll lose root.

4.0.4 ota is compiled by google from it's internal tree.
What you see in gerrit is the reviewing process for the master branch (and a few others), where everyone can submit, which should be updated (merged) with google internal tree everytime a ota/source gets released.

ArmanUV said:
thanks. you misunderstood my first question though. I know that nexus images are based off aosp. What I meant is that the changes on android gerrit review system are public and in real time. So why is it that a release like 4.0.4 is a big deal?
Not the best place to ask this question but I think if you're on yajuko and you have stock bootloader (not cwm) then you may be able to get ota but you'll lose root.
Click to expand...
Click to collapse
Because those sources are actually not released until google starts the ota update. They develop behind closed doors then release all new code at once with the ota. Some people dont like this but i dont think it matters prrsonally.
---------- Post added at 06:53 AM ---------- Previous post was at 06:51 AM ----------
5. Github has a diff function that can compare any two files and even merge the code together. So the devs likely use diff to check all new code and merge.
4. You can look thru all the commits to actually see the newest code changes to see whats important etc.

bk201doesntexist said:
4.0.4 ota is compiled by google from it's internal tree.
What you see in gerrit is the reviewing process for the master branch (and a few others), where everyone can submit, which should be updated (merged) with google internal tree everytime a ota/source gets released.
Click to expand...
Click to collapse
so Gerrit commits are just a very small percentage of all the changes, right?
and does that mean that ota updates may be (slightly) different from aosp compiles?
and that they are no changes to aosp between releases?
thanks!

ArmanUV said:
so Gerrit commits are just a very small percentage of all the changes, right?
and does that mean that ota updates may be (slightly) different from aosp compiles?
and that they are no changes to aosp between releases?
thanks!
Click to expand...
Click to collapse
gerrit commits to the master branch are most of time submitted by people working outside of google.
yes, compiling from the master branch of aosp is slightly diferent than from compiling through release tags (4.0.3_r1, 4.0.4_r1.1).
tagged releases are the same as an OTA, except it doesn't have radio/bootloader images, since they're binaries. they don't change, ever. now the builds compiled from aosp master branch do change, even if it is only under the hood changes.

Android Wear 2.0 for SmartWatch 3 port progress Thread & Creation of OSS project

Hello,
As some people heard, i really try to get Android Wear 2.0 for our beloved SmartWatch 3.
And it's possible, sources, device trees, all exist to build a working own compiled Android Wear 2.0.
So this thread tells about the current process of the port
PROGRESS
Code:
Repo synced
First build finished (not buildable yet due no blobs included
GAPPS Porting in progress
Fixed to 99% the device tree
Updating Blobs to M1D64T in progress
Using own Device tree
SOURCES
Device Tree for tetra:
https://github.com/Sony-SmartWatch-3-OSS/android_device_tree_tetra_eng_prerelease
Device Kernel for tetra (unmodified):
https://android.googlesource.com/kernel/bcm/+/android-wear-6.0.1_r0.99
(we can use MM kernel on Nougat too, maybe some patches needed but that's okay)
Prebuilts/Blobs for tetra:
https://github.com/Sony-SmartWatch-3-OSS/vendor_prebuilts_tetra
For Discussions go to this thread please: https://forum.xda-developers.com/smartwatch-3/general/companion-thread-android-wear-2-0-t3565693
If you want to help me on this project, write to me via telegram: https://t.me/PDesire

I need that so much any ETA ?
By the way keep up the good work !

Nice to see someone is working on this :victory:
Sent from my Sony Xperia Z5 using XDA Labs

Thanks for your job.
Enviado desde mi Redmi Note 3 mediante Tapatalk

great!!! thanks

Dear PDesire,,
My support can be only moral..... :crying:
And I hoping good news soon from you
Thx again for your great hard work :good:

thankx you great hard work and good luck my friend

I checked out your device tree. It looks like it's based off an Open Devices tree. I don't think we need the following lines
Code:
include device/sony/common-headers/KernelHeaders.mk
-include device/sony/common-kernel/KernelConfig.mk
in BoardConfig.mk.
Also, what about the HALs? Asteroid OS used the system.img from a stock build, but we will need to build from source. I do not think it is open source, as it is not available on google git servers.
EDIT: I do not think building from source will work. This is what I found the Google Android building group:
Certain components of Android (and therefore Wear) come from third parties and have licenses which require the source code to be made available (e.g. the Linux kernel). The components made available via the AOSP repositories for releases like Wear are, afaik, the components which have that type of license.
Wear is a release which has taken the same path as Honeycomb. I can understand that for open source fans and people looking to tinker with a working system it’s somewhat disappointing to see, but those are the choices Google has made.
Click to expand...
Click to collapse
Looks like the only way to go forward is to port it from a pre-compiled version for another watch, like they did for the Galaxy Gear devices.
EDIT 2: Refer:
https://groups.google.com/forum/#!s...nce/android-building/R0r9BBn4M3g/-KexIWTCDwAJ
https://groups.google.com/forum/#!s...nce/android-building/vx0Hcy88Ofs/USxAUaKVAwAJ
These sources are incomplete and only include GPL licensed projects. It is not the complete source, just like google releases preview sources for AOSP preview builds (M, N etc). I suggest you not waste your quota in downloading the source.

drakonizer said:
I checked out your device tree. It looks like it's based off an Open Devices tree. I don't think we need the following lines
Code:
include device/sony/common-headers/KernelHeaders.mk
-include device/sony/common-kernel/KernelConfig.mk
in BoardConfig.mk.
Also, what about the HALs? Asteroid OS used the system.img from a stock build, but we will need to build from source. I do not think it is open source, as it is not available on google git servers.
Click to expand...
Click to collapse
Yeah I've seen these, and already fixed. Patch comes soon.
Things for WLAN and BT for example are on google repo too and if a library or something is missing we can use it from M1D64T
EDIT: I do not think building from source will work. This is what I found the Google Android building group:
Looks like the only way to go forward is to port it from a pre-compiled version for another watch, like they did for the Galaxy Gear devices.
EDIT 2: Refer:
https://groups.google.com/forum/#!s...nce/android-building/R0r9BBn4M3g/-KexIWTCDwAJ
https://groups.google.com/forum/#!s...nce/android-building/vx0Hcy88Ofs/USxAUaKVAwAJ
These sources are incomplete and only include GPL licensed projects. It is not the complete source, just like google releases preview sources for AOSP preview builds (M, N etc). I suggest you not waste your quota in downloading the source.
Click to expand...
Click to collapse
Lel then I can't understand why the build is working xD at least I am building in time and already 14% finished
I know some libs we have to grab from the Marshmallow FW but that shouldn't be a big deal
At least we also need some things from Preview 2 so we can get our AW 2.0 Preview 2 working
So I try my best to grab much from source and if required also from FW, but all in all its possible for our SmartWatch 3 to get Android Wear 2.0
Your PDesire

but there's one thing i don't understand ... why r u using preview 2 instead of a feature complete newer version or the final version?

xpatze85x said:
but there's one thing i don't understand ... why r u using preview 2 instead of a feature complete newer version or the final version?
Click to expand...
Click to collapse
Because there aren't any sources of the final version.

@PDesire :
You're the man...keep up a good work ???

Hey @PDesire , any news? I'm sooooo hyped!!!

Thank bro I hope

Thanks for this!

So current status is:
Code:
Repo synced
First Test build stopped to fix things on device tree
Expected in future:
Code:
Blobs dump
Fully fixed Device tree
Creating vendor for tetra
Adding overlays for framework to device tree
Some mix with armv7-a-neon generic
Gapps Dump
Expected in far future:
Code:
Creating an OSS project for tetra (like sonyxperiadev but for tetra)
So guys I will do more tomorrow as I am awake already from Friday 7AM - 3AM Saturday (right now GMT +1) and working on it and I need my sleep xD
So Goodnight guys and I can confirm our dream of Android Wear 2.0 for SmartWatch 3 comes nearer
Your PDesire

PDesire said:
So Goodnight guys and I can confirm our dream of Android Wear 2.0 for SmartWatch 3 comes nearer
Click to expand...
Click to collapse
And I can confirm my donation is coming when a working build is ready, and I suppose others are coming, isn't it guys? ???

Is it possible that this could give us Android pay or will that only work with official AW2?
Sent from my SM-G920F using XDA-Developers Legacy app

Neo Cortex said:
Is it possible that this could give us Android pay or will that only work with official AW2?
Sent from my SM-G920F using XDA-Developers Legacy app
Click to expand...
Click to collapse
No. That'll only work on an official firmware, unfortunately...

Thank you very much, hope you will finish it without problems~!

[REFERENCE] Pixel 2 kernel source with linux-stable (4.4.162)

Introduction
Hello everyone, this is a thread to introduce both users and kernel developers to the concept of linux-stable as well as give developers some tips and a tree to either merge into their own, use as a base, or just as a reference. Feel free to ask questions and enjoy!
What is it?
linux-stable is, as the name implies, the stable branch of the Linux kernel, the base of Android. The phone could not run without the Linux kernel (at least not without reworking a lot of stuff). The Android kernels are based on the longterm stable trees:
Longterm
There are usually several "longterm maintenance" kernel releases provided for the purposes of backporting bugfixes for older kernel trees. Only important bugfixes are applied to such kernels and they don't usually see very frequent releases, especially for older trees.
Click to expand...
Click to collapse
Source: https://www.kernel.org/category/releases.html
All Linux development happens on the master branch, which is governed by Linus Torvalds. When issues are discovered there, the fixes are applied then backported to these various stable trees for consumption. It is not uncommon for a fix to need to go back a few years.
There is a LOT more information available in the notes repo in the android-linux-stable organization if you care to learn more in-depth: https://github.com/android-linux-stable/notes
What does this mean for me?
If you are a developer, this means you should be merging these changes into your own tree. These are vetted, stable fixes to real world problems and they are being handed out for free. It does not take long to get up to date (as you can just merge this tree directly into your own or do it yourself using the tree as a reference) and once you are up to date, there is usually a release once every two weeks, give or take. I provide a rebuttal to a lot of various complaints here. If you still feel like there is a good reason not to do this, please let me know, I'll be happy to try and debate on it!
If you are a user, it means that you should be looking for and using kernels that have these fixes, as it shows the developers care for your security and stability. The current version for this device is 4.4.116 and the current version upstream is 4.4.162 so all you need to do is go into Settings > About phone and look at the kernel version to know if you are up to date.
How do I use?
If you are a developer, the reference tree is located in the android-linux-stable organization: https://github.com/android-linux-stable/wahoo
This can either be merged into your existing kernel tree if you have one or be used as a fresh base. You do not need my permission to use it nor do you need to give me credit (although it would be appreciated).
If you are a user, use a kernel that has the changes added in!
Getting notified about updates
There are a few ways to get notified of linux-stable updates:
The linux-kernel-announce mailing list: http://vger.kernel.org/vger-lists.html#linux-kernel-announce
The android-linux-stable Telegram channel: https://t.me/alsupdates
Subscribe to this thread
Follow me on Google+ or Twitter
Getting help
If you have any issues with getting these changes into your tree or want to ask a question, there are a few different ways to do it:
Post in this thread
Join the linux-stable support chat on Telegram: https://t.me/joinchat/C1UAJ1EMSX31PCFdwLnOSg
File an issue either in the android-linux-stable notes repo or the android-linux-stable repo for this device
When requesting help, please give some solid details as to what you are struggling with, as I am happy to provide assistant and clarity but not to do something for you (unless I screwed up).

4.4.103 has been merged in.

This is my first Nexus / Pixel (VZW Galaxy Nexus I don't count), how soon does Google typically release the kernel source for the DP's? Only after the official software release?
I'm torn between stable + your kernel and DP + stock kernel.

Telperion said:
This is my first Nexus / Pixel (VZW Galaxy Nexus I don't count), how soon does Google typically release the kernel source for the DP's? Only after the official software release?
I'm torn between stable + your kernel and DP + stock kernel.
Click to expand...
Click to collapse
It depends. Longer DPs like the initial release of a new major number (7.0, 8.0, etc) typically get kernel source within a month of the new DP version dropping. Smaller DPs usually don't get source until release (7.1 is the only other small DP that has ever happened so not much history).

:good::good::good:

I dont mean to go too offtopic here, but does that apply to the android source codes too? I meam does it usualy take that long for them to release the sources? I am guessing we still dont have any custom roms because the sources were not released by google yet?

4.4.104 has been merged in, with conflict notes updated accordingly.

The repo location has changed (new link is in the OP).
Additionally, an 8.1 branch has been created. Google went from 4.4.56 to 4.4.88 so the branch was redone to avoid conflicts and go with Google's resolution. The notes have been updated as well. Happy kerneling!

4.4.106 has been merged in (conflict notes).

4.4.107 has been merged in.

4.4.108 has been merged in.

4.4.109 has been merged in (conflict notes).

4.4.110 has been merged in (conflict notes).

4.4.111 has been merged in.
Just as a heads up, I started school on Monday so while the updates will still continue, they may not be as timely as they have in the past, especially if there are conflicts that I need to document.

4.4.112 has been merged in (conflict notes).
I used this conflict in my video talking about thinking through linux-stable conflicts, check it out! https://www.youtube.com/watch?v=yWvU8_0O66A

4.4.113 has been merged in (conflict notes).

4.4.114 has been merged in.

4.4.115 has been merged in (conflict notes).

4.4.116 has been merged in.

The OP has been updated, including some more information for users as well as some more ways of getting help and notified of updates! Enjoy

General XDA Article: Google starts uploading Android 13 source code to AOSP

Google starts uploading Android 13 source code to AOSP
After much anticipation, Google has finally released the source code for Android 13. The final version has also launched, too!
www.xda-developers.com
August 15, 2022 1:00pm Timi Cantisano
Google starts uploading Android 13 source code to AOSP​
After some anticipation, Google has released the source code for Android 13. Although the release came a bit later than expected, the company has started uploading the source code to Android Open Source Project (AOSP) Git repositories. This can often take some time, often requiring hours for the update to be fully populated. As a result, be patient if you don’t see it. This source code release also comes alongside the full release of Android 13.
Before the release, Google updated its Android 13 Security Release Notes which contained details about security vulnerabilities that were present in Android. The update showed security vulnerabilities that have been fixed in Android 13. Devices running Android 13 with a security patch level of 2022-09-01 or later will be protected from these issues. If you’d like to check what version of Android you’re running and the security patch level, most manufacturers have it listed under the About Phone section under Settings.
XDA VIDEO OF THE DAY
The release of Android 13’s source code is important, not only for those that want to tinker with the OS but also for communities that build custom ROMs and aftermarket distributions of Android like LineageOS. Major manufacturers must also rely on this repository for their own Android releases. You can have a look at the Android 13 source code by heading over to Google Git.
For developers, this is an important time as it is time to release compatible versions of their apps and build out more features with APIs. Google is releasing the Android 13 source code under the Apache License version 2.0. Apache 2.0 is a permissive rather than copyleft license, meaning developers can modify and distribute the code freely without being required to open-source their modifications. This licensing system is what allows smartphone makers to develop their own closed-source forks of Android.
If you’re interested in analyzing the Android 13 source code, you can head over to the Android Git repositories and look for the new Android 13 branches and tags. Specifically, look for the “android-13.0.0_r#” tags. It takes a while for the entirety of Google’s internal codebase to be pushed to the public AOSP repositories, so expect to wait a few hours before you can sync everything. Google also uploads the commit history for each release, which provides a lot of insight into the Android team’s thought process when adding or removing features.
Click to expand...
Click to collapse
http://www.facebook.com/sharer.php?...arts uploading Android 13 source code to AOSP