пн, 3 июн. 2019 г., 17:49 Raymond Wanyoike <[email protected]>:

> Hello,
>
> Following the guide at
> https://source.android.com/setup/build/building-kernels for the Pixel 3
> (blueline) will put you in the same situation; a bootable kernel, but
> without touchscreen (and I suspect other drivers, like audio) working:
>
> $ repo init -u https://android.googlesource.com/kernel/manifest -b
> android-msm-crosshatch-4.9-pie-qpr2
> $ repo sync
> $ build/build.sh
> $ adb reboot bootloader
> $ fastboot boot out/dist/Image.lz4-dtb
> $ # boots, but :(
>
> > I suspect your device is missing the touch screen drivers (maybe the
> > drivers you have in your device are not compatible with your kernel).
>
> I find it odd that custom Pixel 3 kernels available on XDA (
> https://forum.xda-developers.com) boot and work (fastboot boot <kernel>)
> with stock vendor modules, but the kernels generated from the build guide
> requires workarounds to move things to /vendor/lib/modules.
>
> Would this mean that the guide is broken for Pixel 3 (blueline), that the
> *build/build.sh* script is not suitable for building stock vendor
> compatible kernels?
>
> On Friday, March 29, 2019 at 5:26:25 PM UTC+3, [email protected] wrote:
>>
>> Hi
>>
>> I have built and flashed clean AOSP.
>> fastboot flashall -w
>> Which worked like a charm.
>>
>> Thn I build msm and flashed it with
>> fastboot boot Image.lz4-dtb
>>
>> The phone reboots. But then I am not able to use the touch screen at all.
>> I cant unlock the phones sim card. If I hold down the power button for a
>> while and reboot it. The touch screen works. Not sure what causes that, but
>> maybe the kernel has been removed and switched out with the old one?
>>
>> Another similar question is. If Id like to put the Image.lz4-dtb file
>> inside the AOSP ROM. Where should I put it, and is that possible? If that
>> would make me able to flash both kernel and ROM at the same time?
>>
> --
> --
> You received this message because you are subscribed to the "Android
> Building" mailing list.
> To post to this group, send email to [email protected]
> To unsubscribe from this group, send email to
> [email protected]
> 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 [email protected].
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/android-building/362c157c-df7b-4062-91f8-45b0419326a3%40googlegroups.com
> <https://groups.google.com/d/msgid/android-building/362c157c-df7b-4062-91f8-45b0419326a3%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
-- 
You received this message because you are subscribed to the "Android Building" 
mailing list.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
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 [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/android-building/CADH%3D_7Par8tPgYXa%2BBxCX%2BeMPAvo5uHBH2Xex23tAfEXC1de6A%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to