Re: [b2g] Is this the correct OTA update URL?

Hi Augustine, You can track the bug https://bugzilla.mozilla.org/show_bug.cgi?id=1169735 for the OTA status. Thanks, No-Jun > On Jun 3, 2015, at 3:29 AM, Augustin Trancart > wrote: > > Hi Naoki, > > Thanks for the info! Is the last know

Re: [b2g] Is this the correct OTA update URL?

Hi Naoki, Thanks for the info! Is the last known good build number tracked somewhere? And is there also a way to know which bugs are blocking an OTA? Thanks! Regards, Augustin On 02/06/2015 22:38, Naoki Hirata wrote: I found out the situation. The last known good build is 20150521142045 due

Re: [b2g] Is this the correct OTA update URL?

Many thanks Naoki! I'll follow the bugs till they are fixed so I'll know when to expect a new update. It's good to know I have the correct xml! BTW, could you please help me with a wifi issue I have since a long time now? I filed the bug 7 months ago and I followed all the suggestions I received b

Re: [b2g] Is this the correct OTA update URL?

I found out the situation. The last known good build is 20150521142045 due to the following blocker bugs: https://bugzilla.mozilla.org/show_bug.cgi?id=1170611[Keyboard] Having a keyboard active will disable all app interaction if the user has typed anything https://bugzilla.mozilla.org/

Re: [b2g] Is this the correct OTA update URL?

Hi Naoki, The logcat regarding the update url is the following: *** AUS:SVC Checker:getUpdateURL - update URL: https://aus4.m ozilla.org/update/3/B2G/41.0a1/20150528143550/flame/en-US/nightly/Boot2Gecko%203 .0.0.0-prerelease%20(SDK%2019)/default/default/update.xml?force=1 I/Gecko ( 211): I

Re: [b2g] Is this the correct OTA update URL?

Right, thanks Naoki! I'll d it as soon as I get back home. Best regards, Gabriela On 2 June 2015 at 12:38, Naoki Hirata wrote: > It's similar to android device, make sure that the adb is turned on in the > developer tools of the settings. (you will have to turn in dev tools via > settin

Re: [b2g] Is this the correct OTA update URL?

It's similar to android device, make sure that the adb is turned on in the developer tools of the settings. (you will have to turn in dev tools via settings -> device info -> more information ): adb logcat From there while you have adb logcat running try doing an update via the settings -> dev

Re: [b2g] Is this the correct OTA update URL?

Hi Naoki, I am on 3.0, base image v.18D (nightly), you told me to flash this last time I had the same issue. I was on v.188 before. For the logcat, I would greatly appreciate if you could please tell me how to obtain it. Many thanks! Best regards, Gabriela QA Mozilla Hispano Team Responsible

Re: [b2g] Is this the correct OTA update URL?

Hi Gabriela, Thanks for the suggestion. Which version are you on and what does your update url point to in logcat when you try to do an update? Chances are that you may be on a bad build and need to update manually or modify the url in order to get the correct url to update. Let's check that p

Re: [b2g] Is this the correct OTA update URL?

Hi, I haven't received any OTA updates since May 28. Would this be a bug? Should I file it? Many thanks! Best regards, Gabriela QA Mozilla Hispano Team Responsible http://www.mozilla-hispano.org http://twitter.com/mozilla_hispano http://facebook.com/mozillahispano On 2 June 2015 at 02:36,

Re: [b2g] Is this the correct OTA update URL?

You were on a build that had the code that was reverted. You will have to update it again manually. The code has been changed on the client side and will be changed on the client side once again when bug 1166522 lands. Regards, Naoki On Jun 1, 2015, at 7:26 PM, Kan-Ru Chen (陳侃如) wrote: > H

[b2g] Is this the correct OTA update URL?

Hi, I haven't got any OTA updates on my flame ever since I flashed it using build from the public ftp. I "flashed" it by adb push b2g directory onto the phone /system/b2g. The update URL it uses is https://aus4.mozilla.org/update/3/B2G/41.0a1/20150525160205/flame-eng/en-US/nightly/Boot2Gecko%203.