-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Building for Lem12pro #1
Comments
Hi! The OpenWatch Project is currently not buildable because of a DMCA takedown by MediaTek >:( This repository used to contain the entire BSP provided by MediaTek under NDA (of course, we did not sign any of that), so there's no need to extract proprietary blobs -they are already included. You can find the full BSP which was not taken down here: https://github.com/mtk-watch/manifest. That's an unmodified BSP, meaning you will have to port the kernel changes (you can just clone this repository) and other repositories there. Check this xls for more information: https://gitlab.com/mtk-watch/android_vendor_mediatek/-/blob/t-alps-q0.mp1-V9.122.1/release_note/MT6739/ReleaseNote_for_MT6739_alps-mp-q0.mp1.xlsx Check the project clone script too: https://gitlab.com/mtk-watch/android_vendor_mediatek/-/tree/t-alps-q0.mp1-V9.122.1/proprietary/scripts/project_clone |
Hi, thx for the infos/links. I will check it out.
…________________________________
Von: Iscle ***@***.***>
Gesendet: Freitag, 2. Juni 2023 00:36
An: OpenWatchProject/android_device_wiite_c7s ***@***.***>
Cc: harvey186 ***@***.***>; Author ***@***.***>
Betreff: Re: [OpenWatchProject/android_device_wiite_c7s] Building for Lem12pro (Issue #1)
Hi! The OpenWatch Project is currently not buildable because of a DMCA takedown by MediaTek >:(
This repository used to contain the entire BSP provided by MediaTek under NDA (of course, we did not sign any of that), so there's no need to extract proprietary blobs -they are already included.
You can find the full BSP which was not taken down here: https://github.com/mtk-watch/manifest. That's an unmodified BSP, meaning you will have to port the kernel changes (you can just clone this repository) and other repositories there.
Check this xls for more information: https://gitlab.com/mtk-watch/android_vendor_mediatek/-/blob/t-alps-q0.mp1-V9.122.1/release_note/MT6739/ReleaseNote_for_MT6739_alps-mp-q0.mp1.xlsx
Check the project clone script too: https://gitlab.com/mtk-watch/android_vendor_mediatek/-/tree/t-alps-q0.mp1-V9.122.1/proprietary/scripts/project_clone
—
Reply to this email directly, view it on GitHub<#1 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AAUZVLQXWCUTQVUAF5UJIFLXJEKNJANCNFSM6AAAAAAYXROINA>.
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
I hope I will get my LeOS-GSI (A13) running on the Lem12pro. On other Lem watch it's working fine :)) |
Sorry, can I ask a bit more ? I have synced all, but the building command isn't doing anything
|
Hi, I have build roms for a lot of devices, but never for a watch.
I'm wondering a bit about the howto in your manifest repo.
Normally I will need device, kernel and vendor sources. Device and Kernel sources seems to be available here, but what's about vendor sources. Have I to extract them via ./extract-files.sh?
And can I build the rom with standard way
source build/envsetup.sh
lunch device_name
I'n will get my Lem12 pro in 2 weeks and want be prepared.
The text was updated successfully, but these errors were encountered: