I’ve successfully flashed the transition branches on my Flame last week; using the instructions provided on the Wiki should do the trick, just make sure that you use the flame-kk target when running the config.sh script and your Flame has been pre-flashed using the V5 base image available here:
Great ! can you share the screenshots here, please
If yes, please add it to B2G Installer add-on, to help people installing B2G on flame easily
(see the dedicated topic: https://discourse.mozilla-community.org/t/b2g-installer-add-on-for-firefox/7523/15)
Hi everybody, I’m gonna try and make a blobfree build available for the Flame this weekend
/me stares at Gabriele
How was your weekend ?
My weekend was spent feeling the effects of an antibiotics treatment, I’ll do better this week
I hope so you feel better…!
I try to do this for myself and I need to ask a question:
@gsvelto, @lissyx for create this type of build(blobfree) if needed that the device is connected?.
Sorry if this is a stupid question but I`m confused with that.
Again, this is documented. You need to be able to do a full build. So you need the blobs. Device must be connected the first time, can be disconnected once you have backup-flame/ properly populated.
I don’t think you need the device to be connected, just the appropriate backup directory. Anyway I was running a blobfree build for the Flame but I’ve noticed that it’s already listed in the add-on list:
Is anything else needed?
Ya, but I think there is not for the transition branch, right?
Maybe in the future when the kanikani branch merge into the master is not needed but for the moment maybe is needed for testing somethings like calls and messages.
this are master builds, can we add a pine build to the addon?
ok now I see these builds are really old is there a reason why there are no new pine builds?
I check the version v2 and it is in the same state. Do not updated from 2015-10-11 12:20:44.
But I thinks is related with the comments C2 and C4 of the Bug 1264065.
In summary from c2 @wcosta and c4 @lissyx
c2 Flame-kk builds were removed from Taskcluster in Bug 1255644
c4 Flame KK never completed the transition to TaskCluster
yes, this was explained in the build and port meeting. But there are some suggestions to start building for flame on buildbot I think.
@gsvelto I’m trying to create a build for flame-kk but somehow I’m unable to pull /system/b2g/distribution/ from the device.
EDIT: so it seems that the directory is empty. what can I do about this?
I do not have much time for the meetings but later in the night, I have read the notes and try to help in some things, I have skills like devops and automatization tools, maybe I can help with buildbot or other system that we use for create the builds.
@TitanNano if you finish this task, please share the build because I do not have resources in home like connection for do this.
If anyone can share one build of the transition for flame(maybe @gsvelto?), would be awesome, is for testing in one flame that I have with problem in the touchscreen but at least I can see booting one more time
Blobfree Flame-KK build from 2016-05-07