nice! please update the topic above. I will share the news
please whait until we have the blobfree b2g-installer running! To much unproper information will harm the viralness… Once it is done then please…
For the history…
Sorry I didn’t follow this topic since a while (~50 replies ^^)
Does that mean that you have a working build ready ? Yeah !
Yes i have a functional blobFULL- build. And i tested it. It works.
But there are a few things i had to change in the manifest and those aren’t yet in the main branch.
I have problems understanding the words of the programers that helped me sort out how to make my environement work. @lissyx told me here https://bugzilla.mozilla.org/show_bug.cgi?id=1294725 to make a PR with everything but i don’t know what that means (whats: - squash your PR branch into one commit).
And how can i test it if its not in the repo yet?
Second topic is the blobfree build what also succeded, but to flash it needs some more investigation.
I managed to fix the b2g-installer proprietary-files.txt to make the b2g-installer download the blobs from the device but it does not work on boot up it freezes. So it seams that to download the bloobs from the device i need the new version of proprietary-file.txt that has no system/ prefix and to make b2g-installer build correctly i need the old verstion of proprietary-files.txt with the prefix system/.
So now that will take a few hours to figure out how i can fix that, and i don’t have time in the moment to do that… If someone wold like to take that pleas don’t hesitate. This is the bugnr: https://bugzilla.mozilla.org/show_bug.cgi?id=1285793
I just got informed from @TitanNano that there is a bug in B2G OS that might has missleading my interpretation above.
Lets wait until https://bugzilla.mozilla.org/show_bug.cgi?id=1295011 is fixed.
Dev/git user jargon ^^
You can test your patch locally You just apply it to your files, build, test if it’s working, and if so you go to the next step.
After that, include all the changes in only 1 file (the commit), that you submit for a Pull Request (PR) which means that you request to “pull” your changes inside of the repository.
Ok, I’m glad to see those good progress (please keep us updated and ask questions when needed ).
Keep going, you’re on the right way !
Your work will be really valuable, the Fairphone 2 will be a great flagship for B2G OS
PS: BTW I’m updating the Compatible Devices pages with this information.
When the blob free version will be ready, please mention on this page that it is available on B2G Installer
That bug would not surface on non debug builds :-).
Regarding the extra system/, it probably cones from the logic in
gonk-misc/Android.mk that deals with finding blobs.
Ok, I’m glad to see those good progress (please keep us updated and ask
questions when needed <
Keep going, you’re on the right way !<
Your work will be really valuable, the Fairphone 2 will be a great
flagship for B2G OS <
PS: BTW I’m updating the Compatible Devices pages with this information.
When the blob free version will be ready, please mention on this page
that it is available on B2G Installer <
Visit Topic or reply to this email to respond.
In Reply To
I just got informed from @TitanNano that there is a bug in B2G OS that
might has missleading my interpretation above. Lets wait until
https://bugzilla.mozilla.org/show_bug.cgi?id=1295011 is fixed.
Is that file called during build or b2g-installer flash?
Build. Novski, I don’t want to sound disrespectful or blaming you, but it would really help that you learn basics of Android build system like Makefile and stuff around
Any Android.mk file present in the tree (whatever level) will be sources by AOSP build system and evaluated. So gonk-misc/Android.mk is one of them (and quite an important one since it is the one defining the |gecko| module).
Inside you can find the blobfree target. From there, with the game of dependencies, all sub targets needed for blobfree are visible. One of them is to handle the detection of which blobs are being used. Please refer to the comments in the file, the git commit description, and the bug introducing blobfree at build system level for more documentation.
@Novski One thing you should pay attention too is that if you are pulling newer blobs, then there might have been upstream sources changes that are also needed. So you should check and rebase any forked repo, especially the device tree ones, agaisnt upstream to ensure to have something that matches.
@Novski Can you also ensure, if you are using an updated upstream blobset, that the layout of |TARGET_DEVICE_BLOBS_SRC_DIR := vendor/qcom/proprietary/target/product/FP2/| has not been changed ? Maybe they just modified the paths and this is why it screws you for generating the blob list file.
Download and extract the set of blobs references in download-blobs.sh and compare the tree structure with your new blobs
No, that is not your problem. Assertion failures would only happen on a B2G_DEBUG=1 build. A non debug build (which is the default) would work.
Thats why im asking… I can abort here if there is no need, but i think it’s better to have somebody working slow than nobody at all. Mozilla support is gone and the only people left are some entusiasticaly connected peoples. There are verry few programmers with knowledge of B2G anyway so if you take some more time to explaine me the details (and the words used as synonym so oftenly) i will learn how to manage code faster.
i found echos in that file that seam to be same as b2g-installer popups…
does that mean that the proptietay-files.txt file is generated during the build? I don’t think so…
what does “upstream” mean, the only upstream i know is in water…
Thanks for clarification. I will start debuging that when i have more time…
i’m struggling to flash fxos on my fp2.
I have downgraded to 1.2.8 and “USB debbugging connected” on the screen.
i have Ubuntu, i run nightly with ADB helper. In a new profile i open about:b2g-installer, connect my device. The files are opening, but the b2g-installer still doesn’t see the device.
I’m a simple user, have no specific knowledge on the topic. I’ve been told to run this:
patata@librem13:~$ adb devices
- daemon not running. starting it now on port 5037 *
- daemon started successfully *
List of devices attached
Then i’ve been told to add udev rules, but i don’t know how to do that. i’d like to see full procedure in the manual.
Please use the VM to make sure.
go to settings and scroll all the way down. Tap on the last entry of the list and scroll all down to the buildNr. and tap that one 10 times.
As soon as you have developer go back to settings “first page” and tap on developer. Second last entry.
Enable USB Debuging.
Then you have to uncheck all options in the connection notification pull down.
It will then be recognized but the available B2G OS version has a bug and will not pull the blobs correctly so ther is no point to flash your device by now… I will fix that soon.
The problem is that most of your questions are not B2G specific at all. Basic knowledge of make, gcc, git are really needed to be able to pursue, but it has nothing specific with the project. And if you lack those knowledges, then it’s even harder for us to help you
What are the “echos in that file that seems to be same as b2g-installer popups” ? I really doubt, because I wrote both
The proprietary-file.txt is being used by the build system to copy/install the blobs, and read . Blob-free detection of blobs does not rely on this. Basically, what the gonk-misc/Android.mk shell magic does is that is computes sha1 to identify the blobs. So we read the filenames from proprietary-file.txt, but we re-build a mapping of blobs.
uncheck all options in the connection notification pull down
Thanks Novski, that was it!