Thanks for the help on this Viral/Kobalt/others!
So I have updated the information on MDN. First, this section has been updated according to Viral’s instructions on the bug:
https://developer.mozilla.org/en-US/Firefox_OS/Developer_phone_guide/ZTE_OPEN_C#Upgrading_Gecko_and_Gaia
Can you verify that this is ok?
Second, can you confirm whether these instructions for upgrading Gaia only are ok?
https://developer.mozilla.org/en-US/Firefox_OS/Developer_phone_guide/ZTE_OPEN_C#Upgrading_Gaia
If they don’t work, can they be upgraded to work, or should I just delete the section completely?
Best regards,
Chris Mills
Senior tech writer || Mozilla
developer.mozilla.org || MDN
cmi...@mozilla.com || @chrisdavidmills
On 29 May 2014, at 04:28, Viral Wang <vw...@mozilla.com> wrote:
> Hi Kobalt,
>
> Maybe you can do "make reset-gaia" in gaia folder also?
> If we move gecko to master branch, we should move gaia to master at same time.
> Thank you for your feedback and I think I should update it in bug 1016867 :)
>
> Here's my steps to make a clean build and I'm sure it works in my open C
> $ rm -rf objdir-gecko/ out/ backup-flame/
> $ ./config.sh flame openc.xml
> $ ./build.sh gecko
> $ ./flash.sh gecko
> $ cd gaia
> $ make reset-gaia
>
> Regards,
> viral
>
> ----- Original Message -----
> From: "Kobalt Kitsuné" <cobal...@gmail.com>
> To: mozilla...@lists.mozilla.org
> Sent: Thursday, May 29, 2014 6:41:10 AM
> Subject: Re: [b2g] ZTE Open C
>
> On Wednesday, May 28, 2014 5:00:02 AM UTC-5, Viral Wang wrote:
>> Hi,
>>
>>
>>
>> Actually Open C and flame should not used same code base.
>>
>> The reason that open C can use flame before is we use the build for msm8x10 in the beginning.
>>
>> After that, we add some specific features like NFC in flame.
>>
>> That's why some of errors happened if you only have open C in your hand.
>>
>>
>>
>> https://bugzilla.mozilla.org/show_bug.cgi?id=1016867#c1
>>
>> Here's a quick fix to use the first version for device-flame.
>>
>> That's pretty close to pure msm8x10 from CAF should work for open C
>>
>>
>>
>> Regards,
>>
>> viral
>
> Hello viral, I tried using the manifest (openc.xml) that was provided in the link, but after flashing the phone seems to be stuck in a boot loop. I've factory reset the phone thinking that would fix it, but that didn't do anything. One thing that may shed some light on this was when I went into adb shell and navigated to /system/b2g on the device, I then ran ./b2g and it gave me:
>
> CANNOT LINK EXECUTABLE: could not load library "libmozglue.so" needed by "./b2g"; caused by library "libmozglue.so" not found
>
> Does anyone have any ideas about how to correct this?
>
> Thanks,
>
> Kobalt
Hi Rewarp,
Maybe you should update gaia after ./flash.sh gecko
> $ ./build.sh gecko
> $ ./flash.sh gecko
> $ cd gaia
> $ make reset-gaia
Regards,
viral
----- Original Message -----
From: "Rewarp" <rew...@gmail.com>
To: "Chris Mills" <cmi...@mozilla.com>
Cc: "Viral Wang" <vw...@mozilla.com>, "Kobalt Kitsuné" <cobal...@gmail.com>, "mozilla-dev-b2g" <mozilla...@lists.mozilla.org>
Sent: Thursday, May 29, 2014 4:50:28 PM
Subject: Re: [b2g] ZTE Open C
Thanks for the work Viral Wang. I was able to run the build script but it*--Bitmessage <http://bitmessage.org/> me*
is now stuck on the boot screen with the fox animation after doing
./flash.sh gecko. It's still stuck in the loop. Any advice?
*BM-2D97QV3Y4VRfjayrWahqE61XKuQw6dJvj6*
On 29 May 2014 03:04, Chris Mills <cmi...@mozilla.com> wrote:
> Thanks for the help on this Viral/Kobalt/others!
>
> So I have updated the information on MDN. First, this section has been
> updated according to Viral’s instructions on the bug:
>
>
> https://developer.mozilla.org/en-US/Firefox_OS/Developer_phone_guide/ZTE_OPEN_C#Upgrading_Gecko_and_Gaia
>
> Can you verify that this is ok?
>
> Second, can you confirm whether these instructions for upgrading Gaia only
> are ok?
>
>
> https://developer.mozilla.org/en-US/Firefox_OS/Developer_phone_guide/ZTE_OPEN_C#Upgrading_Gaia
>
> If they don’t work, can they be upgraded to work, or should I just delete
> the section completely?
>
> Best regards,
>
> Chris Mills
> Senior tech writer || Mozilla
> developer.mozilla.org || MDN
> cmi...@mozilla.com || @chrisdavidmills
>
>
>
> On 29 May 2014, at 04:28, Viral Wang <vw...@mozilla.com> wrote:
>
> > Hi Kobalt,
> >
> > Maybe you can do "make reset-gaia" in gaia folder also?
> > If we move gecko to master branch, we should move gaia to master at same
> time.
> > Thank you for your feedback and I think I should update it in bug
> 1016867 :)
> >
> > Here's my steps to make a clean build and I'm sure it works in my open C
> > $ rm -rf objdir-gecko/ out/ backup-flame/
> > $ ./config.sh flame openc.xml
> > $ ./build.sh gecko
> > $ ./flash.sh gecko
> > $ cd gaia
> > $ make reset-gaia
> >
> > Regards,
> > viral
> >
> > ----- Original Message -----
> > From: "Kobalt Kitsuné" <cobal...@gmail.com>
> > To: mozilla...@lists.mozilla.org
> > Sent: Thursday, May 29, 2014 6:41:10 AM
> > Subject: Re: [b2g] ZTE Open C
> >
> > On Wednesday, May 28, 2014 5:00:02 AM UTC-5, Viral Wang wrote:
> >> Hi,
> >>
> >>
> >>
> >> Actually Open C and flame should not used same code base.
> >>
> >> The reason that open C can use flame before is we use the build for
> msm8x10 in the beginning.
> >>
> >> After that, we add some specific features like NFC in flame.
> >>
> >> That's why some of errors happened if you only have open C in your hand.
> >>
> >>
> >>
> >> https://bugzilla.mozilla.org/show_bug.cgi?id=1016867#c1
> >>
> >> Here's a quick fix to use the first version for device-flame.
> >>
> >> That's pretty close to pure msm8x10 from CAF should work for open C
> >>
> >>
> >>
> >> Regards,
> >>
> >> viral
> >
> > Hello viral, I tried using the manifest (openc.xml) that was provided in
> the link, but after flashing the phone seems to be stuck in a boot loop.
> I've factory reset the phone thinking that would fix it, but that didn't do
> anything. One thing that may shed some light on this was when I went into
> adb shell and navigated to /system/b2g on the device, I then ran ./b2g and
> it gave me:
> >
> > CANNOT LINK EXECUTABLE: could not load library "libmozglue.so" needed by
> "./b2g"; caused by library "libmozglue.so" not found
> >
> > Does anyone have any ideas about how to correct this?
> >
> > Thanks,
> >
> > Kobalt
oops, I forgot to add the link! It is now added to the article.
On 29 May 2014, at 10:40, Rewarp <rew...@gmail.com> wrote:
> Sorry, somehow I only sent a Reply instead of Reply All.
>
> Thank you again Viral Wang. Worked like a charm. So do I need to rerun
>
> $ rm -rf objdir-gecko/ out/ backup-flame/
> $ ./config.sh flame openc.xml
>
> before building gecko again? Or can I transition directly to building after doing "git pull"? Also, is it normal to lose all user account settings after each installation? Because I have had to rerun the first-run setup again.
>
> Also, the Open C page on MDN lacks a link to the openc.xml file.
>
> --
> Bitmessage me BM-2D97QV3Y4VRfjayrWahqE61XKuQw6dJvj6
>
>
> On 29 May 2014 04:15, Viral Wang <vw...@mozilla.com> wrote:
> Hi Rewarp,
>
> Maybe you should update gaia after ./flash.sh gecko
>
> > $ ./build.sh gecko
> > $ ./flash.sh gecko
> > $ cd gaia
> > $ make reset-gaia
>
> Regards,
> viral
>
> ----- Original Message -----
> From: "Rewarp" <rew...@gmail.com>
> To: "Chris Mills" <cmi...@mozilla.com>
> Cc: "Viral Wang" <vw...@mozilla.com>, "Kobalt Kitsuné" <cobal...@gmail.com>, "mozilla-dev-b2g" <mozilla...@lists.mozilla.org>
> Sent: Thursday, May 29, 2014 4:50:28 PM
> Subject: Re: [b2g] ZTE Open C
>
> Thanks for the work Viral Wang. I was able to run the build script but it
> is now stuck on the boot screen with the fox animation after doing
> ./flash.sh gecko. It's still stuck in the loop. Any advice?
>
>
> *--Bitmessage <http://bitmessage.org/> me*
> *BM-2D97QV3Y4VRfjayrWahqE61XKuQw6dJvj6*
>
>
> On 29 May 2014 03:04, Chris Mills <cmi...@mozilla.com> wrote:
>
> > Thanks for the help on this Viral/Kobalt/others!
> >
> > So I have updated the information on MDN. First, this section has been
> > updated according to Viral’s instructions on the bug:
> >
> >
> > https://developer.mozilla.org/en-US/Firefox_OS/Developer_phone_guide/ZTE_OPEN_C#Upgrading_Gecko_and_Gaia
> >
> > Can you verify that this is ok?
> >
> > Second, can you confirm whether these instructions for upgrading Gaia only
> > are ok?
> >
> >
> > https://developer.mozilla.org/en-US/Firefox_OS/Developer_phone_guide/ZTE_OPEN_C#Upgrading_Gaia
> >
> > If they don’t work, can they be upgraded to work, or should I just delete
> > the section completely?
> >
> > Best regards,
> >
> > Chris Mills
> > Senior tech writer || Mozilla
> > developer.mozilla.org || MDN
> > cmi...@mozilla.com || @chrisdavidmills
> >
> >
> >
> > On 29 May 2014, at 04:28, Viral Wang <vw...@mozilla.com> wrote:
> >
> > > Hi Kobalt,
> > >
> > > Maybe you can do "make reset-gaia" in gaia folder also?
> > > If we move gecko to master branch, we should move gaia to master at same
> > time.
> > > Thank you for your feedback and I think I should update it in bug
> > 1016867 :)
> > >
> > > Here's my steps to make a clean build and I'm sure it works in my open C
> > > $ rm -rf objdir-gecko/ out/ backup-flame/
> > > $ ./config.sh flame openc.xml
> > > $ ./build.sh gecko
> > > $ ./flash.sh gecko
> > > $ cd gaia
> > > $ make reset-gaia
> > >
> > > Regards,
> > > viral
> > >
> > > ----- Original Message -----
> > > From: "Kobalt Kitsuné" <cobal...@gmail.com>
> > > To: mozilla...@lists.mozilla.org
> > > Sent: Thursday, May 29, 2014 6:41:10 AM
> > > Subject: Re: [b2g] ZTE Open C
> > >
> > > On Wednesday, May 28, 2014 5:00:02 AM UTC-5, Viral Wang wrote:
> > >> Hi,
> > >>
> > >>
> > >>
> > >> Actually Open C and flame should not used same code base.
> > >>
> > >> The reason that open C can use flame before is we use the build for
> > msm8x10 in the beginning.
> > >>
> > >> After that, we add some specific features like NFC in flame.
> > >>
> > >> That's why some of errors happened if you only have open C in your hand.
> > >>
> > >>
> > >>
> > >> https://bugzilla.mozilla.org/show_bug.cgi?id=1016867#c1
> > >>
> > >> Here's a quick fix to use the first version for device-flame.
> > >>
> > >> That's pretty close to pure msm8x10 from CAF should work for open C
> > >>
> > >>
> > >>
> > >> Regards,
> > >>
> > >> viral
> > >
> > > Hello viral, I tried using the manifest (openc.xml) that was provided in
> > the link, but after flashing the phone seems to be stuck in a boot loop.
> > I've factory reset the phone thinking that would fix it, but that didn't do
> > anything. One thing that may shed some light on this was when I went into
> > adb shell and navigated to /system/b2g on the device, I then ran ./b2g and
> > it gave me:
> > >
> > > CANNOT LINK EXECUTABLE: could not load library "libmozglue.so" needed by
> > "./b2g"; caused by library "libmozglue.so" not found
> > >
> > > Does anyone have any ideas about how to correct this?
> > >
> > > Thanks,
> > >
> > > Kobalt
> > On 29 May 2014, at 04:28, Viral Wang wrote:
>
> >
>
> > > Hi Kobalt,
>
> > >
>
> > > Maybe you can do "make reset-gaia" in gaia folder also?
>
> > > If we move gecko to master branch, we should move gaia to master at same
>
> > time.
>
> > > Thank you for your feedback and I think I should update it in bug
>
> > 1016867 :)
>
> > >
>
> > > Here's my steps to make a clean build and I'm sure it works in my open C
>
> > > $ rm -rf objdir-gecko/ out/ backup-flame/
>
> > > $ ./config.sh flame openc.xml
>
> > > $ ./build.sh gecko
>
> > > $ ./flash.sh gecko
>
> > > $ cd gaia
>
> > > $ make reset-gaia
>
> > >
>
> > > Regards,
>
> > > viral
Ah, so that's why it wouldn't boot; I had forgot to flash gaia as well.
I just got through doing a clean build of gecko this morning and followed your instructions and it's now starting up normally.
Thanks for the help viral!
FFOS 2.0 seems to be more stable then when I tried it out a few days ago.
The keyboard works this time and for some reason I have better signal strength. The only problem I've noticed so far is a bit of lag when typing with the on-screen keyboard. I'll keep checking for any bugs that have yet to be listed on bugzilla.
Also Rewarp, I checked under my Device\More Information and I am able see my MAC address. Maybe it is something unique to your build? I am running the latest version of gecko / gaia
I have also been losing my user settings when updating gecko. Updating just gaia seems to preserve them though. I know having to go through the first time user experience multiple times can get annoying after a while, so can make a .userconfig file to disable it.
You will need place it in the root of your B2G build tree for it to work. See:
https://developer.mozilla.org/en-US/Firefox_OS/Customization_with_the_.userconfig_file
Hmm. I am pretty sure I am following the latest Flame build, at least that's the impression I got from following the instructions given. Maybe it will fix itself next time I flash it.Thanks for the tip on the .userconfig file. Viral sent me a reply telling me how to preserve the settings via the alternate route of
$ ./flash.sh gaia
instead of
$ cd gaia
$ make reset-gaia
Maybe you may want to try this out as well.
On 29 May 2014 14:45, Kobalt Kitsuné <cobal...@gmail.com> wrote:
> > On 29 May 2014, at 04:28, Viral Wang wrote:
>
> >
>
> > > Hi Kobalt,
>
> > >
>
> > > Maybe you can do "make reset-gaia" in gaia folder also?
>
> > > If we move gecko to master branch, we should move gaia to master at same
>
> > time.
>
> > > Thank you for your feedback and I think I should update it in bug
>
> > 1016867 :)
>
> > >
>
> > > Here's my steps to make a clean build and I'm sure it works in my open C
>
> > > $ rm -rf objdir-gecko/ out/ backup-flame/
>
> > > $ ./config.sh flame openc.xml
>
> > > $ ./build.sh gecko
>
> > > $ ./flash.sh gecko
>
> > > $ cd gaia
>
> > > $ make reset-gaia
>
> > >
>
> > > Regards,
>
> > > viral
Ah, so that's why it wouldn't boot; I had forgot to flash gaia as well.
I just got through doing a clean build of gecko this morning and followed your instructions and it's now starting up normally.
Thanks for the help viral!
FFOS 2.0 seems to be more stable then when I tried it out a few days ago.
The keyboard works this time and for some reason I have better signal strength. The only problem I've noticed so far is a bit of lag when typing with the on-screen keyboard. I'll keep checking for any bugs that have yet to be listed on bugzilla.
Also Rewarp, I checked under my Device\More Information and I am able see my MAC address. Maybe it is something unique to your build? I am running the latest version of gecko / gaia
I have also been losing my user settings when updating gecko. Updating just gaia seems to preserve them though. I know having to go through the first time user experience multiple times can get annoying after a while, so can make a .userconfig file to disable it.
You will need place it in the root of your B2G build tree for it to work. See:
https://developer.mozilla.org/en-US/Firefox_OS/Customization_with_the_.userconfig_file