Fairphone 2 support for B2G-Installer, landed!

Nothing before, it’s in your temp dir. Logs from JS console ?

I think you are guiding for Linux as tmp sounds like that. Im on OS X.
Search of a b2g folder in OS X doesn’t find any… (my builds are made in a Linux VM…)
And the JS console doesn’t allow me to copy the output.

Any idea how to get hold of the logs?

No. I don’t know osx.

<
https://ci5.googleusercontent.com/proxy/kY0yCMmDzLJk1E96ido5ikNAHe5zh52D3YphR1X2xsrOEU-akWaRVcb05gCxw4tWSLqENnwem5Tm-NtFWoV2NCt4Wc-JGW_Dh5C7jzgcntlxIgUGOQWTDe7tfUEQonn_B38KBuLWG02k6YjYTd1RxOikuyZQHm2_UG72p17U=s0-d-e1-ft#https://discourse.mozilla-community.org/user_avatar/discourse.mozilla-community.org/novski/45/4829_1.png>
Novski Ivan Hörler
July 15
<
https://ci3.googleusercontent.com/proxy/a6EMeT_h5MyWLSl50LcVcJUcuUEikIXcNOGXGJp-rrXv_7kQn0Wq-HQyymFXmI0doJHrcmzOsl7o4aRl636hcMyALwftzCNk9QPOpt9NxLIADNXTj0GcC0i1vgWFaHC0yIhNPOj5vscsw7s=s0-d-e1-ft#https://discourse.mozilla-community.org/letter_avatar_proxy/v2/letter/l/ecb155/40.png
lissyx:

/tmp/b2g-installer/DEVICE/images/

<
https://ci3.googleusercontent.com/proxy/a6EMeT_h5MyWLSl50LcVcJUcuUEikIXcNOGXGJp-rrXv_7kQn0Wq-HQyymFXmI0doJHrcmzOsl7o4aRl636hcMyALwftzCNk9QPOpt9NxLIADNXTj0GcC0i1vgWFaHC0yIhNPOj5vscsw7s=s0-d-e1-ft#https://discourse.mozilla-community.org/letter_avatar_proxy/v2/letter/l/ecb155/40.png
lissyx:

Nothing before, it’s in your temp dir.

I think you are guiding for Linux as tmp sounds like that. Im on OS X.
Search of a b2g folder doesn’t find any… (my builds are made in a Linux
VM…)
And the JS console doesn’t allow me to copy the output.

Any idea how to get hold of the logs?


Visit Topic or reply to this email to respond.


In Reply To

<
https://ci5.googleusercontent.com/proxy/awzTLeZSQ4NoIfBlGZA3lo26kZQVVC_BjmANCNdQ4J3ntLbC3OZJIeAQFM53I2NXMRdNwx5dc_wrzQauIPOWKNBxCWTk2WOuGwsP5-7iO_OBAvvokOOWFV5k6nWiczuxCcFLpgrVlO3SS2U=s0-d-e1-ft#https://discourse.mozilla-community.org/letter_avatar_proxy/v2/letter/l/ecb155/45.png>
lissyx

Ok. I asked that in the Firefox developing topic of discourse.mizilla-community.org and have to wait until i get an answer there.
I also recognized that at some point i can click on the second image (first is “B2G Nightly user build for Fairphone 2” and second “B2G OS Transision” but it installs the first image.
It then boots with FXOS 2.6.0.0. instead of B2G where it still doesn’t boot.

So to flash FXOS, i have first to downgrade to FP2_gms43_1.2.8 ?
I cannot find this build anywhere anymore…

It would be easier if we could directly upgrade from fp2-sibon-16.06.0 or FP2_gms59_1.5.1 which are respectively the latest open-source and gms builds.

What should i do?

I guess novski had a build against latest gms now you need to debug why it does not boot :-/

Mozilla Discourse a écrit :


patata

July 21

So to flash FXOS, i have first to downgrade to FP2_gms43_1.2.8 ?

I cannot find this build anywhere anymore…

It would be easier if we could directly upgrade from fp2-sibon-16.06.0 or FP2_gms59_1.5.1 which are respectively the latest open-source and gms builds.

What should i do?


Visit Topic or reply to this email to respond.


In Reply To

NovskiIvan Hörler

July 15Ok. I asked that in the Firefox developing topic of discourse.mizilla-community.org and have to wait until i get an answer there. I also recognized that at some point i can click on the second image (first is “B2G Nightly user build for Fairphone 2” and second “B2G OS Transision” but it installs the…


Visit Topic or reply to this email to respond.

To stop receiving notifications for this particular topic, click here.

To unsubscribe from these emails, change your user preferences.

Envoyé depuis Firefox OS

sorry @patata i was not able to fix the blobfree buld before my vacations. you can manualy do by following post 11 in this tread and by downloading my blobfree build from here: https://github.com/mozilla-b2g/b2g-installer-builds/releases/download/b2gos-experimental-fp2/FP2.blobfree-dist.zip otherwise im back in 10 days…

I would recommend comparing the two boot partitions: the one generated after a ./build.sh that works, and the one rebuilt by the installer. Is it possible something changed kernel side ? Or that there is a dt.img not being picked up properly ?

I made a new build after i recognized that i am still using kanikani. Now the new build runs on the blobfull build perfect but the blobfree flashed device does not boot. I tried two times. The blobfree build with kanikani did boot correctly only some issues like the one with the slider was faulty. How come? the log does not give out any warning or error during pulling, building and flashing. Any idea where to search?

I guess we need more informations regarding what it means “do not boot”.
Can you elaborate? Does it gets past bootloader? Is ADB responding, getting
you some logs? If Gecko is starting but displays nothing, it’s probably an
easy fix.

it boots so i see the logo “Fairphone” then it reboots, and i the logo again but it passes to recovery… i then have some variables like whipe data partitiion or cache wich i all tried to apply without any success.

I’m sorry, I really cannot do anything unless you tell us if it boots with
ADB. You should make sure you clean everything also, to be certain nothing
gets screwed because of mismatch between builds. It really makes no sense
that just Gaia would change anything …

ok adb and fastboot do not respond by tring with adb logcat on startup and fastboot logcat.
do you mean to clean my b2g-installer build directory (i was searching for the place it stores the images but didn’t find them…)
or do you mean to clean the data and cache storage on the device?
I know it does not make sense… Maybe i have to do another blobfree build its maybe broken…?

Cannot tell without more informations. Clean b2g-installer build dir, but
also your build tree completely :slight_smile:

And make sure you can boot with ./flash.sh, if it is not working, blobfree
is not going to work better :slight_smile:

Thanks.
Can you tell where the b2g-installer stores the temporary images? I don’t find them…
./flash.sh works!

Temp images are stored in /tmp/b2g-installer//images/

ok, so if flash.sh works maybe it is just somethign screwed with the
/tmp/b2g-installer/, clean up all of it, start from scratch the flashing
with Android on the device. Then you can compare the behavior with what is
done after using ./flash.sh :slight_smile:

If it is still not booting, you can try reflashing only boot.img from the
B2G/out/target/product/FP2/ directory ; if that boots we know something
failed building the boot partition within the addon :confused:

If still nothing, you can try the same with system.img :slight_smile:

Thanks for those explanations and ideas!
I tried as you sayed to delete the temp data but didn’t find the folder on osx so i googled and read that on osx that data gets trashed by reboot so i rebooted my mac and tried. It workded the pull and build was made new.
But it didn’t change the behavour that it doesn’t boot so i tried as you sayed and flashed the boot partition from my build.
That didn’t change anything so i thaught to go on and try another partition. I tried the system as next and it boots now correctly and the Homescreen get loaded.
So in fact it seams to me that the system partition is not built correctly somehow…
How can i debug that partialy?

Do you mean, that flashing ONLY the system partition (not the boot one)
produced by flash.sh works? But not the one from B2G Installer? That
reminds me of an issue yes, that was caused by something related to
metadata for selinux :confused:

Make sure that only flashing the system partition does the trick, and if
so, collect all logs: B2G Installer log, and build log for the system.img
(rm out/target/product/FP2/system.img; ./build.sh out/target/product/FP2/system.img 2>&1 | tee system.log)

no. only flashing system.img does not help. Don’t know why but the first time that i have done it it didn’t boot with only flashing bootloader. also after a second reboot not.
well i hounted for the data on my mac a bit further and finaly found it. (never trust a library folder visibul on a mac. it didn’t contian all it actualy has insid that folder. don’t know why…)
But anyway i found that the boot.img was missing and in the log i then found that boot.img was not writen… :confounded:
so in line 1079 of this http://pastebin.com/jPr7uXYg you can find the snipet:

Flash for Object { sourceDir: “/Users/FirefoxNightly/Library/Cache…”,
imageFile: “/Users/FirefoxNightly/Library/Cache…”, partition: “boot” }
returned Object { sending: false, sendingOk: false, writing: false,
writingOk: false, finished: false } about.js:1151:11

and in 1009 its building the image but that image does not exist if i look in to the path:

and i think it may has something to do with this:


you see behind boot.img its empty…
It is already empty when i unzip the FP2.blobfree-dist.zip
can you help me find out what causes this?