-
Notifications
You must be signed in to change notification settings - Fork 11
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
Machine abstraction, Pixel 3a and Android 10 #40
Conversation
937821f
to
b8a2e76
Compare
a10ca67
to
bb515fe
Compare
I did a second clean built and successfully tested a OTA update <3. Remaining issues:
Workaround found and tested:
Fixed:
Not relevant, fixed for myself:
|
@lrvick Why did you drop the "ignore allowBackup="false" of apps" patch in aae983a? I think this is still useful so I ported it to Android 10 (only a small change) and am testing it in my next build. Edit: Working. You still have it mentioned in the README: "Backup - Minor OS changes made to allow backing up any app". |
At least bluecross.
Based on commit: 4001e56467169b7e3315607782415c8ad31ea38b In: https://github.com/GrapheneOS/platform_frameworks_base.git
I am done for now. My 4th build is good enough for me to actually use it. I have a few other improvements/ideas laying around but I want to tested them more before I feel comfortable submitting them. See you when it is time to build the 2019-12-05 security patches 😉 Also then, I will maybe reattempt to build F-Droid in tree. |
Ref: 8836d44ddc901f14c115ea8b08fc3d1b35e1916b (https://gitlab.com/fdroid/privileged-extension)
No changes are needed to build the 2019-12-05 patch level. Confirmed working on sargo. |
I wanted to try the build so i cloned you're repository and changed the branch to machine-abstraction |
Hi @rkunschke I guess the docs are not precise about that. Fixed in a09df67 and hashbang/aosp-build#12. $ make tools
$ ll build/base/out/.path/make_key
lrwxrwxrwx 1 builder builder 19 2019-12-22 09:43 build/base/out/.path/make_key -> ../.path_interposer
The project provides a Makefile which you should use. Not sure where you got that command. Looks random. Such manual docker commands should not be required :) |
@ypid
I just want to build a flashable file |
I guess the project still requires some knowledge of Docker, Makefiles and Android and the ability to fix issues yourself to get started. You need to run those commands in https://github.com/hashbang/aosp-build which builds the image that https://github.com/hashbang/os can then use. Please try to get some understanding how this all is supposed to fit together! |
Thank you for this tip. My problem was that i try'ed to build in os repository. Now the build is working without a problem so far. I think I know understand. aosp build starts a docker container which pulls os and builds it. |
patch: **** malformed patch at line 32
A build error (ref: hashbang/aosp-build#9) prevents me from building the 2020-01-05 security patches. Any input would be highly appreciated. |
hashbang/aosp-build#9 does not longer prevent me to build the update. Only a small fix was needed to build 2020-01-05 for sargo, ref: hashbang/aosp-build#12 and 9481753. |
I was skeptical if it was actually useful in practice as many apps seem to ignore it. Happy to see it included back if you have confirmed it does in fact play nice for you. |
This is a lot of solid work in the right direction and gets us close! That said, I see the lack of chromium/F-droid as a major regression we need to address before we merge to master. Also we can't take the GrapheneOS webview as this is just an unsigned binary on github with no supply chain integrity. We will have to find a solution to build this from source as well. Will be continuing to play with this and likely merge most of it once I get a working build (even if missing features) |
Honestly, the more I think about it, it may be better to just drop chromium from the project entirely and stick with the default webview by default until maybe there is a nice in-tree chromium-webview that builds from source... but even then leave the standalone browser out of it. My thinking is:
|
This has proven to be useful for me. When you check logcat while making an adb backup, you can see what apps do not want to be backed up. When I applied this patch and restored my backup, a few more apps worked right away that had to be setup manually without the patch.
They are at least signed by Daniel Micay’s OpenPGP key. But I agree with you.
Sounds reasonable to me. This is also what I do right now, I don’t include the browser in the build and let F-Droid install/update my browser. The only issue is the webview, because I did not find a way to install it without root as I figured it must be part of the /system build? |
2020-02-05 and 2020-03-05 can be build. For 2020-03-05 967a7c3 was needed. Currently the WebView is broken but I assume that is because the app ID of Vanadium was changed. I pushed an untested commit which should fix that. I guess I will make another build in a few days to see if that works. I generated the repo XML files for all supported devices. Generating those took hours. @lrvick Is that just my connection or does it take very long for you as well? Happy building :) |
Unfortunately, my quick and dirty attempt to fix the web view did not work. I will leave it as this for now until the next security patch. Feel free to pick up the work. This is still a workaround anyway. |
It does take quite a while, but better than actually cloning all the repos
from scratch to get the hashes... tradeoffs.
…On Mon, Mar 9, 2020 at 2:27 PM Robin Schneider ***@***.***> wrote:
2020-02-05 and 2020-03-05 can be build. For 2020-03-05 967a7c3
<967a7c3>
was needed.
Currently the WebView is broken but I assume that is because the app ID of
Vanadium was changed. I pushed an untested commit which should fix that. I
guess I will make another build in a few days to see if that works.
I generated the repo XML files for all supported devices. Generating those
took hours. @lrvick <https://github.com/lrvick> Is that just my
connection or does it take very long for you as well?
Happy building :)
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#40?email_source=notifications&email_token=AAAQ4UAK5VHZGIBF3BHO4NTRGVNKXA5CNFSM4JLM4Y52YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEOJEIBQ#issuecomment-596788230>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAAQ4UAV3RKV5LEI3VPYKF3RGVNKXANCNFSM4JLM4Y5Q>
.
|
No changes are needed to build the 2020-04-05 patch level. Confirmed working on sargo. |
No changes are needed to build the 2020-05-05 patch level. Confirmed working on sargo. |
hashbang/aosp-build#23 is required to build 2020-06-05. Confirmed working on sargo. |
No changes are needed to build the 2020-07-05 patch level. Confirmed working on sargo. |
No changes are needed to build the 2020-08-05 patch level. Confirmed working on sargo. |
I am going to merge this. The browser integration changes with GrapheneOS anyway. |
Status: Successfully boots on sargo.
Known issues: Backup app missing form build? It has been build because I needed to fix an issue/update it.
Depends on: hashbang/aosp-build#5MergedDepends on: hashbang/aosp-build#12Merged