[android-building] Re: Android T Preview Released

2022-07-25 Thread 'del...@google.com' via Android Building 
Hi, all,

We have pushed the kernel source for Pixel 6, Pixel 6 Pro for Android T 
Developer Beta 4.1.
There is no changes for platform GPL projects compared to Android T 
Developer Beta 4.

Tag   Project  Branch
android-t-beta-4_r0.5 device/google/oriole-kernel 
 android-gs-raviole-5.10-t-beta-4

-- 
-- 
You received this message because you are subscribed to the "Android Building" 
mailing list.
To post to this group, send email to android-building@googlegroups.com
To unsubscribe from this group, send email to
android-building+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-building?hl=en

--- 
You received this message because you are subscribed to the Google Groups 
"Android Building" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to android-building+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/android-building/12e97bb8-19a4-4fa3-b460-778634b5c033n%40googlegroups.com.

Re: [android-building] Unable to flash/boot the Pixel5 with custom build kernel

2022-07-25 Thread 李大锐 
This is the script I use to launch a custom kernel which is working on 
pixel 4a. The key is *flashing boot.img twice* after sending *.ko. 

```
$kernel_ko = $KERNEL_SRCDIR + 
"/out/android-msm-pixel-4.14/dist/*.ko"
scp "${KSERVER}:${kernel_ko}" $aosp_host_build_dir
$env:ANDROID_PRODUCT_OUT = $aosp_host_build_dir; fastboot -s 
${serial_l} flashall -w --disable-verity --disable-verification
adb wait-for-device remount
foreach ($file in (Get-ChildItem (Join-Path -Path 
$aosp_host_build_dir -ChildPath "*.ko")))  { adb push $file 
/vendor/lib/modules/ }
adb reboot bootloader
fastboot -s ${serial_l} flash boot --slot all (Join-Path -Path 
$aosp_host_build_dir -ChildPath boot.img)
fastboot -s ${serial_l} reboot
```

I think the the root cause is that the ko file built by the kernel does not 
enter the boot.img built by aosp. To fundamentally solve this problem a 
correct boot.img might be needed.

On Tuesday, July 12, 2022 at 12:47:51 AM UTC+8 xand...@gmail.com wrote:

> Hi all. Sorry. I've been trying to build a working kernel for raviole for 
> the past week. Has anyone succeeded in building a monolith kernel for Pixel 
> 6/Pro? I don't want to build aosp. Just need to replace the kernel. I keep 
> getting boot loops. Any ideas?
>
> I also tried to compile as follow:
> BUILD_BOOT_IMG=1 SKIP_VENDOR_BOOT=1 KERNEL_BINARY=Image 
> GKI_RAMDISK_PREBUILT_BINARY=gki-ramdisk.lz4 
> BUILD_CONFIG=private/gs-google/build.config.gki.aarch64 ./build/build.sh
>
> where gki-ramdisk.lz4 is the ramdisk extracted from the prebuilt images 
> found here https://developers.google.com/android/images#oriole
>
> On Tuesday, June 22, 2021 at 11:11:17 PM UTC-6 droi...@gmail.com wrote:
>
>> I managed to solve this issue. The solution is currently pending approval 
>> and is posted at the following thread:
>> https://groups.google.com/g/android-building/c/6HPwJloQkP8
>>
>> Cheers!
>> On Wednesday, 16 June 2021 at 06:35:22 UTC+8 Droid SMU wrote:
>>
>>> Hi,
>>>
>>> I also encounter the same issue.
>>> The build setup that I am using is as follows:
>>>
>>> AOSP Build ID: RQ2A.210505.003 (Tag: android-11.0.0_r37)
>>> Kernel branch: android-msm-redbull-4.19-android11-qpr2
>>> Build configuration: aosp_redfin-userdebug
>>>
>>> I got stuck at the "waiting for device" message after executing the 
>>> "fastboot flashall -w" command.
>>> Then what I did was I copied all the *.ko files into the >> tree>/device/google/redbull_kernel folder. This step was able to overcome 
>>> the error above and flash successfully.
>>> However, after flashing, the system tries to boot but it gets stuck at 
>>> the "android" logo screen (this happens after the Google logo screen).
>>>
>>> Would appreciate some advice on this topic.
>>>
>>> Thanks!
>>> On Tuesday, 15 December 2020 at 00:03:16 UTC+8 xiling.gong wrote:
>>>

 Hello Henry,

 Thanks a lot for your reply.

 I've got the same issue on Pixel4 and fixed it using your method. 

 But Pixel5 looks like a bit different and unable to be fixed with the 
 same solution.
 All the .ko built on Pixel5 is unable to be insmod into kernel. 
 Don't know where is the root cause...

 在2020年12月3日星期四 UTC+8 上午2:36:48 写道：

> Hello,
>
> I had a similar problem on a Pixel 4 and fixed it by pushing all the 
> .ko files from the kernel dist directory to /vendor/lib/modules.
>
> On Sun, 29 Nov 2020 at 19:11, xiling.gong  wrote:
>
>> Hello, I'm working on a Pixel5 with AOSP and custom build kernel.
>> The issue is that I can't flash/boot the Pixel5 with custom build 
>> kernel.
>> Anyone please help to check this issue?
>> Thanks a lot.
>>
>> *kernel source:*
>>
>> *   repo init -u https://android.googlesource.com/kernel/manifest 
>>  
>> -b android-msm-redfin-4.19-android11-d1 *
>> *AOSP source:*
>> *  repo init -u 
>> https://android.googlesource.com/platform/manifest 
>>  -b 
>> android-11.0.0_r15*
>>
>> Build the kernel
>>./build/build.sh
>> Then put
>>MSM_KERNEL/out/android-msm-pixel-4.19/dist/Image.gz-dtb 
>> to 
>>AOSP_SOURCE/device/google/redfin-kernel/
>> then build the aosp
>>source build/environment
>>lunch aosp_redfin-userdebug
>>make -j8
>>fastboot flashall
>> When do flash, the flash process will hang at 
>>< waiting for any device >
>>
>>   Bootloader Version...: r3-0.3-6776358
>>   Baseband Version.: g7250-00016-200911-B-6826885
>>   Serial Number: 09261FDD4003XC
>>   
>>   
>> Checking 'product' OKAY [

[android-building] Please push Android 13 Beta kernel manifests

2022-07-25 Thread 'flawedworld' via Android Building 
Hi, it would be greatly be appreciated if the kernel manifest for Android 
13 beta kernels for Pixel devices was pushed to  kernel/manifest - Git at 
Google (googlesource.com) 


Thanks

-- 
-- 
You received this message because you are subscribed to the "Android Building" 
mailing list.
To post to this group, send email to android-building@googlegroups.com
To unsubscribe from this group, send email to
android-building+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-building?hl=en

--- 
You received this message because you are subscribed to the Google Groups 
"Android Building" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to android-building+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/android-building/7975c7ac-5187-4b6e-8545-ab1eec21cacfn%40googlegroups.com.

[android-building] Android Developer Codelab fail to setup cuttlefish

2022-07-25 Thread Munjal Kansara 
I am trying to go through "Android Developer Codelab" on ubuntu 18.04 LTS

$ uname -a
Linux nityan-OptiPlex-7040 5.4.0-122-generic #138~18.04.1-Ubuntu SMP Fri 
Jun 24 14:14:03 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux

Step of setting up Cuttlefish device is failing, as copied below
$ acloud create --local-image --local-instance

==
Notice:
We collect anonymous usage statistics in accordance with our Content 
Licenses (https://source.android.com/setup/start/licenses), Contributor 
License Agreement (https://opensource.google.com/docs/cla/), Privacy Policy 
(https://policies.google.com/privacy) and Terms of Service 
(https://policies.google.com/terms).
==

Missing necessary acloud setup, would you like to run setup[y/N]?y

Welcome to

___ ___  __ _ 
/ _ |/ ___/ / / __ \/ / / / _ \ 
/ __ / /__/ /__/ /_/ / /_/ / // / 
/_/ |_\___//\/\// 



==
[Install cuttlefish-common packages on the host] 
This step will walk you through the cuttlefish-common packages installation 
for your host.
==


Start to install cuttlefish-common :
git clone https://github.com/google/android-cuttlefish.git 
/tmp/tmp2yb7jyr7/cf-common
cd /tmp/tmp2yb7jyr7/cf-common
debuild -i -us -uc -b
sudo dpkg -i ../cuttlefish-base_*_*64.deb || sudo apt-get install -f
sudo dpkg -i ../cuttlefish-user_*_*64.deb || sudo apt-get install -f
sudo dpkg -i ../cuttlefish-common_*_*64.deb || sudo apt-get install -f
Enter 'y' to continue, otherwise N or enter to exit: y
Run command: git clone https://github.com/google/android-cuttlefish.git 
/tmp/tmp2yb7jyr7/cf-common
cd /tmp/tmp2yb7jyr7/cf-common
debuild -i -us -uc -b
sudo dpkg -i ../cuttlefish-base_*_*64.deb || sudo apt-get install -f
sudo dpkg -i ../cuttlefish-user_*_*64.deb || sudo apt-get install -f
sudo dpkg -i ../cuttlefish-common_*_*64.deb || sudo apt-get install -f
Cloning into '/tmp/tmp2yb7jyr7/cf-common'...
remote: Enumerating objects: 3380, done.
remote: Counting objects: 100% (581/581), done.
remote: Compressing objects: 100% (172/172), done.
remote: Total 3380 (delta 462), reused 465 (delta 407), pack-reused 2799
Receiving objects: 100% (3380/3380), 907.51 KiB | 987.00 KiB/s, done.
Resolving deltas: 100% (1924/1924), done.
debuild: fatal error at line 1152:
dpkg-buildpackage -rfakeroot -us -uc -ui -i -b failed
dpkg: error: cannot access archive '../cuttlefish-base_*_*64.deb': No such 
file or directory
dpkg: error: cannot access archive '../cuttlefish-user_*_*64.deb': No such 
file or directory
dpkg: error: cannot access archive '../cuttlefish-common_*_*64.deb': No 
such file or directory

-

When i follow instructions from 
https://android.googlesource.com/device/google/cuttlefish/ then also it 
fails ...


$ debuild -i -us -uc -b -d
dpkg-buildpackage -rfakeroot -us -uc -ui -i -b -d
dpkg-buildpackage: info: source package cuttlefish-common
dpkg-buildpackage: info: source version 0.9.24
dpkg-buildpackage: info: source distribution UNRELEASED
dpkg-buildpackage: info: source changed by Jorge Moreira Broche <...>
dpkg-source -i --before-build cf-common
dpkg-buildpackage: info: host architecture amd64
fakeroot debian/rules clean
dh clean --with=config-package
dh: The use of "debhelper-compat (= 12)" is experimental and may change (or 
be retired) without notice
debian/rules override_dh_auto_clean
make[1]: Entering directory '/tmp/tmp6fc51tpn/cf-common'
rm -f host/frontend/host-orchestrator/host-orchestrator
dh_auto_clean
dh_auto_clean: The use of "debhelper-compat (= 12)" is experimental and may 
change (or be retired) without notice
make[1]: Leaving directory '/tmp/tmp6fc51tpn/cf-common'
dh_clean
dh_clean: The use of "debhelper-compat (= 12)" is experimental and may 
change (or be retired) without notice
debian/rules build
dh build --with=config-package
dh: The use of "debhelper-compat (= 12)" is experimental and may change (or 
be retired) without notice
dh_update_autotools_config
dh_update_autotools_config: The use of "debhelper-compat (= 12)" is 
experimental and may change (or be retired) without notice
dh_autoreconf
dh_autoreconf: The use of "debhelper-compat (= 12)" is experimental and may 
change (or be retired) without notice
debian/rules override_dh_auto_build
make[1]: Entering directory '/tmp/tmp6fc51tpn/cf-common'
host/frontend/goutil host/frontend/host-orchestrator build -v -ldflags="-w"
+ cd host/frontend/host-orchestrator
+ shift
+ mkdir -p /tmp/go
+ export GOPATH=/tmp/go
+ GOPATH=/tmp/go
+ export GOCACHE=/tmp/go/go-build
+ GOCACHE=/tmp/go/go-build
+ go build -v -ldflags=-w
main.go:24:2: cannot find package 
"cuttlefish/host-orchestrator/orchestrator" in any of:
/usr/lib/go-1.10/src/cuttlefish/host-orchestrator/orchestrator (from 
$GOROOT)
/tmp/go/src/cuttlef