Re: [b2g] Firefox OS to ZTE Open NOT C
On Sun, 11 May 2014 12:51:48 -0700 (PDT) Антон Бородюк wrote: > On Sunday, 11 May 2014 21:37:48 UTC+3, Ivan S wrote: ... > I'm worried about updates for Open C considering how long it took for > them to update the Open to 1.2. I hope both phones receive latest > updates because it would be pretty stupid to drop support for the > most wide spread firefox phone so soon. > ___ dev-b2g mailing list > dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g Other than the beta release of v1.2, is there an official release of 1.2 or the ZTE Open? Their website is only showing v1.1 as the most recent official release. http://www.ztedevices.com/support/smart_phone/cba40ed6-d3ab-44c0-bdee-3a15803dc187.html?type=software ___ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g
Re: [b2g] I can no longer access to ZTE Open nightly updates
On Sun, 20 Apr 2014 11:29:01 -0700 (PDT) Roland Lindner wrote: > On Tuesday, 1 April 2014 00:41:40 UTC+2, Naoki Hirata wrote: > > We have turned off the inari nightly update as the 1.1 gonk layer > > is out of date for 1.4 and 1.5 and is causing a lot of crashing to > > occur. > > > > The OEM would have to supply a gonk layer to match for the inaris > > to work without crashing. > > > > > > > > Regards, > > > > Naoki > > > > bummer. i just received my ZTE Open from ZTE_UK ebay store, only to > find out that i just wasted 80 Euro on a non-supported device? you > can't be serious? i explicitly bought this device because it seemed > simple to update without having to wait for ZTE to provide an update. > Only to find out now that FXOS is the same crap as Android, where the > phone manufacturer wont update your phone so you will buy a new one. > why thanks a bunch Mozilla, you may want to put that on your MDN, > because right now you are transporting a completely different > message. the ZTE open is praised as a developer device. how can it be > a developer device when it's basically stuck at FXOS 1.1? mad > dissapointed with this. it was pretty darn hard to find out where to > get a device in the first place, no info on what devices now are used > as development devices doesnt help either. i was hoping we would > finally get a real open source phone os. but these hopes seem to be > based on thin air, as it's obviously going to be the same problem as > with Android, where you are completely dependent on the phone > manufacturers. is anyone at Mozilla even interested in resolving this > with ZTE or are you going to just blame ZTE and be done with it? i > would apprechiate if anyone could answere here or at least share the > plans for the future of hardware devices with FXOS and how that > relates to already existing hardware? thanks, Roland > ___ dev-b2g mailing list > dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g Roland, you could always contact the seller and ask them how the device will be supported. As an early adopter with a ZTE Open, I would suggest returning the device for a full refund. ___ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g
Re: [b2g] Never again will I buy a ZTE anymore.
The rocket bar doesn't need to be replaceable, it needs to be removable; which in my opinion, would be the biggest improvement to the current "search bar". Forcing the users to always have a certain application on their homescreen removes the user's choice of how they want to use the homescreen. Decisions such as this should be left up to the users. On Wed, 16 Apr 2014 22:03:54 +0100 Dale Harvey wrote: > Since the rocketbar is a tightly integrated part of the OS, the > primary navigation, its going to be hard to make user replaceable, > part of designing an operating system is deciding how people are > going to use it, it is of course possible to fork gaia and build an > alternative UI > > And we are hoping the rocketbar will be a huge improvement over the > current search implementation, of course would be happy for people to > try it out as we work on it and give feedback / contribute > > Also I share your disappointment with the currently available devices, > There is a reference device that in the works that hopefully vastly > improves the situation - > https://blog.mozilla.org/blog/2014/02/23/new-developer-hardware-and-tools-show-firefox-os-ecosystem-momentum-2/ > > Cheers > Dale > > > On 16 April 2014 18:16, jezra wrote: > > > Can users remove the rocket-bar and have a homescreen with launchers > > of the users choosing? > > > > On Wed, 16 Apr 2014 19:09:11 +0200 > > Julien Wajsberg wrote: > > > > > Le 16/04/2014 18:34, jezra a écrit : > > > > Armen, > > > > I'm a ZTE Open owner so I don't have access to firefoxos images > > > > that contain the rocket bar. However, if the bar is anything > > > > like the v1.1 "search bar on the homescreen that I never use > > > > and I can't remove and replace with what I want", then I hope > > > > the rocket bar gets decoupled as well so that I as a user can > > > > remove it from my device. > > > > > > The rocket bar is basically making that search bar actually > > > useful for everybody. > > > > > > > > > > > > ___ > > dev-b2g mailing list > > dev-b2g@lists.mozilla.org > > https://lists.mozilla.org/listinfo/dev-b2g > > > > ___ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g
Re: [b2g] Never again will I buy a ZTE anymore.
Can users remove the rocket-bar and have a homescreen with launchers of the users choosing? On Wed, 16 Apr 2014 19:09:11 +0200 Julien Wajsberg wrote: > Le 16/04/2014 18:34, jezra a écrit : > > Armen, > > I'm a ZTE Open owner so I don't have access to firefoxos images that > > contain the rocket bar. However, if the bar is anything like the > > v1.1 "search bar on the homescreen that I never use and I can't > > remove and replace with what I want", then I hope the rocket bar > > gets decoupled as well so that I as a user can remove it from my > > device. > > The rocket bar is basically making that search bar actually useful for > everybody. > > signature.asc Description: PGP signature ___ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g
Re: [b2g] Never again will I buy a ZTE anymore.
Hopefully the scope includes the ability for owners/users to remove the bar. Not having the option to use my device the way I want to is extremely frustrating. Currently, someone else has made the decision for me in regards to how I should use my device; and that is definitely not user friendly. Yes, there is a ticket for this as well https://bugzilla.mozilla.org/show_bug.cgi?id=968500 On Wed, 16 Apr 2014 12:39:22 -0400 Armen Zambrano Gasparnian wrote: > Hi Jezra, > I don't know really know what is the path forward or the scope of the > rocket bar. > > On 2014-04-16, 12:34 PM, jezra wrote: > > Armen, > > I'm a ZTE Open owner so I don't have access to firefoxos images that > > contain the rocket bar. However, if the bar is anything like the > > v1.1 "search bar on the homescreen that I never use and I can't > > remove and replace with what I want", then I hope the rocket bar > > gets decoupled as well so that I as a user can remove it from my > > device. > > > > > > > > On Wed, 16 Apr 2014 > > 08:23:46 -0400 "Armen Zambrano G." wrote: > > > >> Hi jerzra, > >> I see the point of that. > >> I wonder how that decoupling will play with the rocket-bar (I > >> believe the idea is to remove the browser completely and make it > >> ubiquitous or something like that). I could be misunderstanding > >> what the plans and timelines are. > >> > >> On 2014-04-15, 5:49 PM, jezra wrote: > >>> I would say that step 1 is to uncouple the single most important > >>> application from the OS and put it in the market place so that > >>> users aren't beholden to OEMs for updates to the browser. > >>> > >>> There is already a ticket for this. > >>> https://bugzilla.mozilla.org/show_bug.cgi?id=973372 > >>> > >>> > >>> On Tue, 15 Apr 2014 10:10:12 -0400 > >>> "Armen Zambrano G." wrote: > >>> > >>>> Hi Max, Adrian, > >>>> I agree that the situation is less than ideal, however, this is > >>>> not what things will be like forever. > >>>> > >>>> I want to point out, that Firefox OS coming out on 2013 was a 1.0 > >>>> release. That means that a lot of sacrifices had to made to hit > >>>> the schedule. The mobile industry is very demanding specifically > >>>> with schedules. There's a saying in software development which > >>>> is "you have to get to 1.0 to even be able to ship a 2.0". > >>>> > >>>> It is very unfortunate that early adopters have to face these > >>>> difficulties; knowing that you're supporting us and trusting > >>>> something very dear to you (your phone and personal time if not > >>>> more than that). > >>>> > >>>> As you can probably imagine, dealing with EOMs is not easy. The > >>>> mobile industry in general is not easy. It is very cut-throat and > >>>> don't necessarily look towards long-term support. > >>>> > >>>> As far as I know, Mozilla is here to change things for the sake > >>>> of the public. There is a limit on how much we can influence the > >>>> industry, however, we have already seen a lot of changes which > >>>> eventually will percolate to the end-users (e.g. EOMs working in > >>>> "open" issues rather than behind closed doors or contributing > >>>> code to an open source initiative). > >>>> > >>>> I don't know how to help you in this specific issue, however, > >>>> look for the "Let's fix updates" thread in this mailing thread. I > >>>> assume good stuff will come out of it. > >>>> > >>>> Thank you for supporting the open web and I hope that a way to > >>>> help you can come out of all the conversations. > >>>> > >>>> sincerely yours, > >>>> Armen > >>>> > >>>> On 2014-04-14, 7:46 AM, maxrottenkol...@googlemail.com wrote: > >>>>> I can only wholeheartedly agree with adrian on this. > >>>>> > >>>>> What i expected from fxos was one thing primarily: a good web > >>>>> browser. > >>>>> > >>>>> Instead i get this excuse of a firefox that: > >>>>> * can not be upgraded > >>>>> * can not be configured > >>>>> * does not run adblock > >>>>> * crashes on 80% of all websites > >>>>> > >>>>> i get weekly updates for marketplace and wikipedia. I couldnt > >>>>> care less. > >>>>> > >>>> > >> > > ___ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g
Re: [b2g] Never again will I buy a ZTE anymore.
Armen, I'm a ZTE Open owner so I don't have access to firefoxos images that contain the rocket bar. However, if the bar is anything like the v1.1 "search bar on the homescreen that I never use and I can't remove and replace with what I want", then I hope the rocket bar gets decoupled as well so that I as a user can remove it from my device. On Wed, 16 Apr 2014 08:23:46 -0400 "Armen Zambrano G." wrote: > Hi jerzra, > I see the point of that. > I wonder how that decoupling will play with the rocket-bar (I believe > the idea is to remove the browser completely and make it ubiquitous or > something like that). I could be misunderstanding what the plans and > timelines are. > > On 2014-04-15, 5:49 PM, jezra wrote: > > I would say that step 1 is to uncouple the single most important > > application from the OS and put it in the market place so that users > > aren't beholden to OEMs for updates to the browser. > > > > There is already a ticket for this. > > https://bugzilla.mozilla.org/show_bug.cgi?id=973372 > > > > > > On Tue, 15 Apr 2014 10:10:12 -0400 > > "Armen Zambrano G." wrote: > > > >> Hi Max, Adrian, > >> I agree that the situation is less than ideal, however, this is not > >> what things will be like forever. > >> > >> I want to point out, that Firefox OS coming out on 2013 was a 1.0 > >> release. That means that a lot of sacrifices had to made to hit the > >> schedule. The mobile industry is very demanding specifically with > >> schedules. There's a saying in software development which is "you > >> have to get to 1.0 to even be able to ship a 2.0". > >> > >> It is very unfortunate that early adopters have to face these > >> difficulties; knowing that you're supporting us and trusting > >> something very dear to you (your phone and personal time if not > >> more than that). > >> > >> As you can probably imagine, dealing with EOMs is not easy. The > >> mobile industry in general is not easy. It is very cut-throat and > >> don't necessarily look towards long-term support. > >> > >> As far as I know, Mozilla is here to change things for the sake of > >> the public. There is a limit on how much we can influence the > >> industry, however, we have already seen a lot of changes which > >> eventually will percolate to the end-users (e.g. EOMs working in > >> "open" issues rather than behind closed doors or contributing code > >> to an open source initiative). > >> > >> I don't know how to help you in this specific issue, however, look > >> for the "Let's fix updates" thread in this mailing thread. I > >> assume good stuff will come out of it. > >> > >> Thank you for supporting the open web and I hope that a way to help > >> you can come out of all the conversations. > >> > >> sincerely yours, > >> Armen > >> > >> On 2014-04-14, 7:46 AM, maxrottenkol...@googlemail.com wrote: > >>> I can only wholeheartedly agree with adrian on this. > >>> > >>> What i expected from fxos was one thing primarily: a good web > >>> browser. > >>> > >>> Instead i get this excuse of a firefox that: > >>> * can not be upgraded > >>> * can not be configured > >>> * does not run adblock > >>> * crashes on 80% of all websites > >>> > >>> i get weekly updates for marketplace and wikipedia. I couldnt care > >>> less. > >>> > >> > >> > > > > ___ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g
Re: [b2g] Never again will I buy a ZTE anymore.
I would say that step 1 is to uncouple the single most important application from the OS and put it in the market place so that users aren't beholden to OEMs for updates to the browser. There is already a ticket for this. https://bugzilla.mozilla.org/show_bug.cgi?id=973372 On Tue, 15 Apr 2014 10:10:12 -0400 "Armen Zambrano G." wrote: > Hi Max, Adrian, > I agree that the situation is less than ideal, however, this is not > what things will be like forever. > > I want to point out, that Firefox OS coming out on 2013 was a 1.0 > release. That means that a lot of sacrifices had to made to hit the > schedule. The mobile industry is very demanding specifically with > schedules. There's a saying in software development which is "you have > to get to 1.0 to even be able to ship a 2.0". > > It is very unfortunate that early adopters have to face these > difficulties; knowing that you're supporting us and trusting something > very dear to you (your phone and personal time if not more than that). > > As you can probably imagine, dealing with EOMs is not easy. The mobile > industry in general is not easy. It is very cut-throat and don't > necessarily look towards long-term support. > > As far as I know, Mozilla is here to change things for the sake of the > public. There is a limit on how much we can influence the industry, > however, we have already seen a lot of changes which eventually will > percolate to the end-users (e.g. EOMs working in "open" issues rather > than behind closed doors or contributing code to an open source > initiative). > > I don't know how to help you in this specific issue, however, look for > the "Let's fix updates" thread in this mailing thread. I assume good > stuff will come out of it. > > Thank you for supporting the open web and I hope that a way to help > you can come out of all the conversations. > > sincerely yours, > Armen > > On 2014-04-14, 7:46 AM, maxrottenkol...@googlemail.com wrote: > > I can only wholeheartedly agree with adrian on this. > > > > What i expected from fxos was one thing primarily: a good web > > browser. > > > > Instead i get this excuse of a firefox that: > > * can not be upgraded > > * can not be configured > > * does not run adblock > > * crashes on 80% of all websites > > > > i get weekly updates for marketplace and wikipedia. I couldnt care > > less. > > > > ___ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g
Re: [b2g] Status of Firefox OS?
I have never read an announcement regarding a release of Firefox OS in any mailing list or tech news site that I frequent. If this were Android or iOS, you could pretty much guarantee that the entire tech world would know when a release was happening. On Tue, 18 Mar 2014 13:25:18 -0300 Adrian Custer wrote: > Hello all, > > Yesterday was an important milestone for Firefox OS, according to: > > https://wiki.mozilla.org/Release_Management/B2G_Landing#Versions_and_Scheduling > including: >* my handset's operating system reaching 'End-of-life' >* v1.3.0 reaching 'code freeze' >* v1.4.0 reaching 'functional complete' > although it might be that this wiki page is irrelevant. > > Over the last two decades, my experience in the world of free > software has been that projects reaching important milestones put out > announcements to the affected communities about the status of things, > the plans, and other relevant information through which developers, > users, document writers, the press, and the interested public can > remain informed about the project. Similar milestones have come and > gone since November without such announcements. > > Could someone in the know please explain what is going on? > > Thank you. > > ~adrian > > > > > P.S. Answers to some of the following questions would be useful: > > Does Firefox OS ever actually declare a 'release'? Did any version > hit 'release' yesterday? What is meant by the next section > > https://wiki.mozilla.org/Release_Management/B2G_Landing#Rough_Update_Graph > when it talks about '1.2 release'? > > Did FfOS 1.1 reach 'end-of-life' yesterday and what does that > actually mean? Are people buying telephones in Uruguay today > vulnerable from here on out to all security flaws discovered in the > OS and in the browser? Is the rumor that there will never be any > over-the-air updates to handsets here true? > > Did Firefox 1.3 reach 'code-freeze' yesterday? What is the status of > the code base at code freeze? Did the schedule slip successfully > address the issues which caused the slip? > > Did Firefox OS 1.4 reach 'functional complete' yesterday? Was the > planned functionality completely written? > > > > ___ > dev-b2g mailing list > dev-b2g@lists.mozilla.org > https://lists.mozilla.org/listinfo/dev-b2g ___ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g
Re: [b2g] Downgraded from 1.2 to 1.1 and saw no noticeable performance issue with the keyboard
Thank you Jed, I look forward to the follow up change in https://bugzil.la/875963 that returns the WYSIWYG keyboard functionality. On Tue, 11 Feb 2014 13:13:23 -0800 Jed Davis wrote: > On Tue, Feb 11, 2014 at 11:58:43AM -0800, jezra wrote: > > Perhaps I am missing something in regards to the performance issue > > that would necessitate changing from a WYSIWYG keyboard to the ALL > > CAPS keyboard. Other than simply using the keyboard, is there a way > > for me to reproduce the performance hit? > > There was a change to the keyboard that set `text-transform: > uppercase` and removed the *visible* change when switching case, but > the keyboard was still spending time adjusting the DOM instead of > handling input: https://bugzil.la/860318#c48 > > The followup change is https://bugzil.la/875963 which landed in what > will be 1.4 and might be uplifted to 1.3; that one takes advantage of > the lack of visible change to optimize the implementation. > > --Jed > ___ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g
[b2g] Downgraded from 1.2 to 1.1 and saw no noticeable performance issue with the keyboard
Perhaps I am missing something in regards to the performance issue that would necessitate changing from a WYSIWYG keyboard to the ALL CAPS keyboard. Other than simply using the keyboard, is there a way for me to reproduce the performance hit? Jezra Web: http://www.jezra.net Status: http://status.jezra.net Coffee: http://coffee.jezra.net ___ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g
Re: [b2g] Are real world users making the "design" decisions?
So FirefoxOS should just "think different" and copy iOS? ;) Hard as it may be for some to believe, but just because Apple does something, doesn't mean it is good for the users. On Thu, 06 Feb 2014 16:51:06 -0800 Chris Peterson wrote: > Jezra, I agree with your WYSIWYG keyboard preference, but there is a > major precedent for only displaying capital letters on the keys: iOS. > > > chris > > > On 2/6/14, 9:52 AM, jezra wrote: > > Yesterday I submitted a bug about the keyboard keys in v1.2 always > > displaying a CAPITAL letter even though the keypress will result in > > a lower case letter. My bug was marked as invalid because someone > > made the design decision that the keyboard keys should not display > > the character that will result when the key is pressed. > > > > > > https://bugzilla.mozilla.org/show_bug.cgi?id=810306#c0 > > > > I am the owner of a small screen device and I use it everyday; I > > also wear corrective lenses, and I shouldn't need to view multiple > > keys just to confirm what character will result when I press a key. > > > > Because of this design "feature", when I type, I find the key I > > want to press, see that it is a Capital letter, then I double check > > that SHIFT isn't on, then I press the key. every single time. > > > > Multiple times on this mailing list, we are told to submit bugs if > > we find a usability issue. To me this is a major usability issue > > when entering text, but it is "as designed". > > > > I am curious as to what device the design decision makers are using > > as their "daily driver"? > > > > > > Jezra > > > > Web: http://www.jezra.net > > Status: http://status.jezra.net > > Coffee: http://coffee.jezra.net > > > ___ > dev-b2g mailing list > dev-b2g@lists.mozilla.org > https://lists.mozilla.org/listinfo/dev-b2g ___ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g
Re: [b2g] Are real world users making the "design" decisions?
How probably is it that the performance hit was caused by switching the case of text as opposed to using complex borders and gradients on each key? Not very. Since late October, I've been using the ZTE Open as my sole mobile phone and haven't noticed any significant improvements in the keyboard change that would necessitate removing user desired functionality. Other than "iOS does it", I haven't seen anything from a real world user's perspective as to why this change is necessary. Perhaps all of the decision makers have iOS devices, perhaps not. What I do know, is that functionality that I appreciate has been removed and there is no option to re-enable that functionality. On Thu, 06 Feb 2014 21:04:36 -0500 Hubert Figuière wrote: > On 06/02/14 12:52 PM, jezra wrote: > > Yesterday I submitted a bug about the keyboard keys in v1.2 always > > displaying a CAPITAL letter even though the keypress will result in > > a lower case letter. My bug was marked as invalid because someone > > made the design decision that the keyboard keys should not display > > the character that will result when the key is pressed. > > > > > > https://bugzilla.mozilla.org/show_bug.cgi?id=810306#c0 > > If you read thoroughly the above bug report, you'll find links to > others like: > > https://bugzilla.mozilla.org/show_bug.cgi?id=863662 > https://bugzilla.mozilla.org/show_bug.cgi?id=860318 > > It should give your more context on why the decision has been made. It > is not a black and whit situations with rainbows and ponies. There is > a real justification, namely performance that led to sacrifice little > bits of user experience. > And if you read deeper, you'll notice that even displaying the actual > case of the letters isn't necessary the best. > > Hub > ___ > dev-b2g mailing list > dev-b2g@lists.mozilla.org > https://lists.mozilla.org/listinfo/dev-b2g ___ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g
[b2g] Are real world users making the "design" decisions?
Yesterday I submitted a bug about the keyboard keys in v1.2 always displaying a CAPITAL letter even though the keypress will result in a lower case letter. My bug was marked as invalid because someone made the design decision that the keyboard keys should not display the character that will result when the key is pressed. https://bugzilla.mozilla.org/show_bug.cgi?id=810306#c0 I am the owner of a small screen device and I use it everyday; I also wear corrective lenses, and I shouldn't need to view multiple keys just to confirm what character will result when I press a key. Because of this design "feature", when I type, I find the key I want to press, see that it is a Capital letter, then I double check that SHIFT isn't on, then I press the key. every single time. Multiple times on this mailing list, we are told to submit bugs if we find a usability issue. To me this is a major usability issue when entering text, but it is "as designed". I am curious as to what device the design decision makers are using as their "daily driver"? Jezra Web: http://www.jezra.net Status: http://status.jezra.net Coffee: http://coffee.jezra.net ___ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g
Re: [b2g] the never-ending search
I'd be more trusting if the files were hosted on either Mozilla's or ZTE's website in a similar fashion to how geeksphone handles their developer images. On Wed, 5 Feb 2014 12:28:29 -0600 "J. Ryan Stinnett" wrote: > On Wed, Feb 5, 2014 at 12:18 PM, jezra wrote: > > > I never said it was a 3rd party update, but I would definitely > > prefer if the update files weren't hosted on 3rd party file locker. > > Trust only goes so far. > > > > In the Hacks blog post Julien linked to, the files are hosted on > Dropbox from account created by ZTE. What's not trustworthy there? > > - Ryan ___ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g
Re: [b2g] the never-ending search
I never said it was a 3rd party update, but I would definitely prefer if the update files weren't hosted on 3rd party file locker. Trust only goes so far. On Wed, 05 Feb 2014 18:28:17 +0100 Julien Wajsberg wrote: > Le 05/02/2014 17:23, jezra a écrit : > > No, I have not tried upgrading to 1.2 using the files from the 3rd > > party file locker. > This is not a upgrade from a 3rd party, this is for an update that > comes directly from ZTE. Please have a look to these instructions for > more information. > signature.asc Description: PGP signature ___ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g
Re: [b2g] the never-ending search
No, I have not tried upgrading to 1.2 using the files from the 3rd party file locker. My request for install instructions from the EBay seller regarding those files was met with quite a bit of confusion. It would be absolutely wonderful, if ZTE Open owners had something like http://downloads.geeksphone.com/ for updated images. All images in one place, no hunting around trying to guess where to go for information. Based on the current release methods used by ZTE, it is terribly disheartening to know that any bugs I submit will be resolved in a version that may never see the light of day for my device. On Wed, 05 Feb 2014 09:51:55 +0100 Julien Wajsberg wrote: > Have you tried upgrading to 1.2 using the latest packages ? > > See > https://developer.mozilla.org/en-US/Firefox_OS/Developer_phone_guide/ZTE_OPEN#Firefox_OS_1.2 > and > https://hacks.mozilla.org/2014/01/upgrading-your-zte-open-to-firefox-1-1-or-1-2-fastboot-enabled/ > for more uptodate information. > > From 1.2, I think it's easier to move to the dev version of 1.3 or > even 1.4 (although I didn't tried it myself). > > Le 04/02/2014 21:25, jezra a écrit : > > As an owner and user of a ZTE Open, I would gladly give Mozilla real > > user feedback on usability issues regarding Firefox OS. > > > > However, due to the extreme difficulty in updating the ZTE Open > > developer device to any newer version of FirefoxOS (including the > > updated versions offered by the manufacturer), I have no way of > > testing new changes or addressing usability issues. > > > > When I submitted my first bug, I was extremely disheartened to learn > > that the issue had been fixed a few months prior to my submission > > in a version of Firefox OS that may never be available for my > > device without me going through the long arduous process of > > compiling the entire OS from source (something a lot of people are > > doing, but are not making the images available publicly). > > > > > > > > On Tue, 04 Feb 2014 14:37:12 -0500 > > Ben Kelly wrote: > > > >> On 2/4/2014 2:04 PM, an wrote: > >>>> Do you have a bug for your phone dialing workflow issue? I > >>>> searched, > >>>> > >>>> but could not find it. > >>> Read the posts, this is not a bug but a way of thinking, I > >>> mentioned that at least once and was told it's on the to-do list > >>> since it's a known mess. > >> I did not ask about the bug as a brush off. Bugs are how we manage > >> all our work. So the best way to get an improvement made is to > >> make sure there is a good bug with the right people looking at it. > >> > >> After some further investigation I ultimately found this bug about > >> dialing directly from call log: > >> > >>https://bugzilla.mozilla.org/show_bug.cgi?id=920011 > >> > >> I'm not sure if that is exactly the issue you were talking about, > >> but it has been getting active work. > >> > >> If this is not the issue you were referring to, I'd be happy to > >> help find the correct bug or write a new one. I'll need your help, > >> though, with better understanding the problem. > >> > >> Thank you. > >> > >> Ben > >> ___ > >> dev-b2g mailing list > >> dev-b2g@lists.mozilla.org > >> https://lists.mozilla.org/listinfo/dev-b2g > > ___ > > dev-b2g mailing list > > dev-b2g@lists.mozilla.org > > https://lists.mozilla.org/listinfo/dev-b2g > > signature.asc Description: PGP signature ___ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g
Re: [b2g] the never-ending search
As an owner and user of a ZTE Open, I would gladly give Mozilla real user feedback on usability issues regarding Firefox OS. However, due to the extreme difficulty in updating the ZTE Open developer device to any newer version of FirefoxOS (including the updated versions offered by the manufacturer), I have no way of testing new changes or addressing usability issues. When I submitted my first bug, I was extremely disheartened to learn that the issue had been fixed a few months prior to my submission in a version of Firefox OS that may never be available for my device without me going through the long arduous process of compiling the entire OS from source (something a lot of people are doing, but are not making the images available publicly). On Tue, 04 Feb 2014 14:37:12 -0500 Ben Kelly wrote: > On 2/4/2014 2:04 PM, an wrote: > >> Do you have a bug for your phone dialing workflow issue? I > >> searched, > >> > >> but could not find it. > > > > Read the posts, this is not a bug but a way of thinking, I mentioned > > that at least once and was told it's on the to-do list since it's a > > known mess. > > I did not ask about the bug as a brush off. Bugs are how we manage > all our work. So the best way to get an improvement made is to make > sure there is a good bug with the right people looking at it. > > After some further investigation I ultimately found this bug about > dialing directly from call log: > >https://bugzilla.mozilla.org/show_bug.cgi?id=920011 > > I'm not sure if that is exactly the issue you were talking about, but > it has been getting active work. > > If this is not the issue you were referring to, I'd be happy to help > find the correct bug or write a new one. I'll need your help, > though, with better understanding the problem. > > Thank you. > > Ben > ___ > dev-b2g mailing list > dev-b2g@lists.mozilla.org > https://lists.mozilla.org/listinfo/dev-b2g ___ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g
Re: [b2g] the never-ending search
If the problem is the need to scroll up the page to enter a new URL, please see the functionality of the Opera Mobile browser from 4 years ago. When scrolling up a web page, a button appears on the screen that when pressed will jump to the top of the page. Putting search or application launchers on the homescreen, and not including the ability for the user/owner to remove them is not very user friendly. jezra On Tue, 04 Feb 2014 13:42:52 -0500 Ben Kelly wrote: > If you're building your own gaia, you can disable rocketbar by doing: > >ROCKETBAR=0 make install-gaia > > Note, however, rocketbar offers other features besides search. It is > effectively the URL bar in the new browser. To me this is a great > improvement because I no longer have to scroll a web page all the way > to the top in order to go to a new URL. > > Do you have a bug for your phone dialing workflow issue? I searched, > but could not find it. > > Ben > > On 2/4/2014 1:23 PM, an wrote: > > B2G is in an endless search... it looks as if the search is the main > > goal of a smartphone and Mozilla was the only one to notice it. I > > just built v1.4 and now I have, aside from "I'm thinking of.." on > > the home screen which I'm sure no one uses and will never use it > > because it is just plain idiotic and can't get rid of it, another > > search!! in the top left corner of the screen. And I can't get rid > > of it either. People, wake up! There's so many UI improvements to > > be done like the too many screens to make a phone call, stop > > inventing idiotic features just to keep busy and pretend you're > > doing something. I saw people praising this stupid "rocketbar", for > > crying out loud, are the UI developers blind at so many other more > > important things? > > > > Anyone interested into buying a ZTE Open?, I've had it with the new > > kid on the block, he's an idiot. > > ___ dev-b2g mailing list > > dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g > > > ___ > dev-b2g mailing list > dev-b2g@lists.mozilla.org > https://lists.mozilla.org/listinfo/dev-b2g ___ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g
Re: [b2g] v1.2 for ZTE Open from the Ebay Seller
How unfortunate, yet not at all unexpected considering the device is the ZTE Open. On Thu, 23 Jan 2014 07:59:38 -0800 (PST) Eduardo González wrote: > I tried system.img, boot.img and userdata.img of your dropbox link, > flashing with fastboot but phone become a loop machine. > > > On Wednesday, January 22, 2014 11:35:10 PM UTC-4:30, jezra wrote: > > I asked the Ebay seller of the ZTE Open if there was any support > > > > planned for v1.2 of FirefoxOS. The seller responded with a link to a > > > > dropbox account. > > > > > > > > https://www.dropbox.com/sh/rnj3rja7gd54s98/kGH6LCBRmf > > > > > > > > I have not yet attempted to flash the images to my device, and to be > > > > honest, I'm a bit dubious of files hosted on 3rd party file lockers, > > > > but curiosity will eventually get the best of me. > > > > > > > > Jezra > > > > > > > > Web: http://www.jezra.net > > > > Status: http://status.jezra.net > > > > Coffee: http://coffee.jezra.net > > ___ > dev-b2g mailing list > dev-b2g@lists.mozilla.org > https://lists.mozilla.org/listinfo/dev-b2g ___ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g
[b2g] v1.2 for ZTE Open from the Ebay Seller
I asked the Ebay seller of the ZTE Open if there was any support planned for v1.2 of FirefoxOS. The seller responded with a link to a dropbox account. https://www.dropbox.com/sh/rnj3rja7gd54s98/kGH6LCBRmf I have not yet attempted to flash the images to my device, and to be honest, I'm a bit dubious of files hosted on 3rd party file lockers, but curiosity will eventually get the best of me. Jezra Web: http://www.jezra.net Status: http://status.jezra.net Coffee: http://coffee.jezra.net ___ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g
Re: [b2g] Available ROM with Firefox OS 1.1 on the ZTE site
On Wed, 11 Dec 2013 11:19:36 -0800 (PST) Ernesto Acosta wrote: > El miércoles, 11 de diciembre de 2013 12:51:49 UTC-5, jezra escribió: > > On Wed, 11 Dec 2013 09:30:27 -0800 (PST) > > > > Ernesto Acosta wrote: > > > > > > > > > El miércoles, 11 de diciembre de 2013 11:32:25 UTC-5, jezra > > > escribió: > > > > > > ZTE has removed the v1.0 update from their website. Although I > > > > do > > > > > > have > > > > ... > > > > > > > > > Yes, something similar happened to me with my phone, which ended > > > up > > > > > being a brick. But in this case I think there's hope, for all that > > > > > ZTE is launching a new ROM with Fastboot support and working > > > properly. > > > > > > > > > > Removing the problem with Fastboot, do you version 1.1 works fine? > > > > > > > > > > > > > It works. Although I certainly wouldn't call it "fine". It is quite > > > > sluggish compared to the 1.3.0.0-prerelease I had been using. > > I think it is normal. It is assumed that the version 1.2 and 1.3 > should be more optimized than 1.1 While I certainly appreciate the better web browser and keyboard, I'd rather have the ability to flash compiled images to my device restored. ___ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g
Re: [b2g] Available ROM with Firefox OS 1.1 on the ZTE site
On Wed, 11 Dec 2013 09:30:27 -0800 (PST) Ernesto Acosta wrote: > El miércoles, 11 de diciembre de 2013 11:32:25 UTC-5, jezra escribió: > > ZTE has removed the v1.0 update from their website. Although I do > > have ... > Yes, something similar happened to me with my phone, which ended up > being a brick. But in this case I think there's hope, for all that > ZTE is launching a new ROM with Fastboot support and working properly. > > Removing the problem with Fastboot, do you version 1.1 works fine? > It works. Although I certainly wouldn't call it "fine". It is quite sluggish compared to the 1.3.0.0-prerelease I had been using. ___ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g
Re: [b2g] Available ROM with Firefox OS 1.1 on the ZTE site
ZTE has removed the v1.0 update from their website. Although I do have a copy of the old update file ,but when I try to install it on my 'Open', I get the following errors: E:failed to verify whole-file signature E:signature verification failed fastboot is still enable on my device. The problem is that when I try to use fastboot to write to my device, the device restarts and the write fails. jezra On Wed, 11 Dec 2013 08:13:48 -0800 (PST) Ernesto Acosta wrote: > El miércoles, 11 de diciembre de 2013 10:56:01 UTC-5, jezra escribió: > > After installing the 1.1 "update", I could no longer use fastboot to > > > > install custom compiled images. > > > > `adb reboot bootloader` will work to put the device into fastboot > > mode, > > > > but when I use `fastboot flash cache ramdisk.img` the device > > restarts. > > Mmm .. And you can return to the previous version? > > I can not believe that ZTE wrong again and have not activated the > Fastboot for ZTE Open. ___ > dev-b2g mailing list > dev-b2g@lists.mozilla.org > https://lists.mozilla.org/listinfo/dev-b2g ___ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g
Re: [b2g] Available ROM with Firefox OS 1.1 on the ZTE site
After installing the 1.1 "update", I could no longer use fastboot to install custom compiled images. `adb reboot bootloader` will work to put the device into fastboot mode, but when I use `fastboot flash cache ramdisk.img` the device restarts. On Wed, 11 Dec 2013 06:28:27 -0800 (PST) Ernesto Acosta wrote: > You can download it from here: D > > http://www.ztedevices.com/support/smart_phone/b5a2981a-1714-4ac7-89e1-630e93e220f8.html?type=software > > Thanks ZTE, thanks > ___ > dev-b2g mailing list > dev-b2g@lists.mozilla.org > https://lists.mozilla.org/listinfo/dev-b2g ___ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g
Re: [b2g] Developing on the ZTE open
On Thu, 7 Nov 2013 12:19:01 -0800 (PST) Bob Thulfram wrote: > On Thursday, November 7, 2013 11:26:14 AM UTC-8, jezra wrote: . > > > > jezra > > Where did you get it and how easy was it to install? I'd be fine with > 1.3 since I already got bit by the change from > mozRequestAnimationFrame to requestAnimationFrame. > ___ dev-b2g mailing list > dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g The OS was compiled for me by someone in Scotland, and I used a 3rd party boot.img from http://sl.edujose.org/2013/10/adapted-boot-image-for-use-with-b2g.html Once I finally managed to get the correct instructions for flashing the device with precompiled images, everything was fairly easy. Basically, I put all of the compiled images into the same directory and ran the following: adb reboot bootloader fastboot devices fastboot flash cache ramdisk.img fastboot flash userdata userdata.img fastboot flash system system.img fastboot flash boot boot.img fastboot reboot jezra ___ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g
Re: [b2g] Developing on the ZTE open
On Wed, 6 Nov 2013 08:53:55 -0800 (PST) Bob Thulfram wrote: > On Wednesday, November 6, 2013 7:54:08 AM UTC-8, roo...@gmail.com > wrote: > > Hi, > > > > Just got a ZTE Open from ebay.co.uk with the intent of using the > > phone for development. > > > > > > > > For remote debugging I believe I need to have > FFOS 1.2. Am I > > correct in saying that the first step is in getting to > > OPEN_EU_DEV_FFOS_V1.0.0B02. From there I need to build an FFOS 1.3 > > image or attempt the precompiled image at > > https://developer.mozilla.org/en-US/docs/Mozilla/Firefox_OS/Developer_phone_guide/ZTE_OPEN > > > > > > > > Thanks > > > > Danny > > I've been developing with the original ZTE Open and learning its > quirks. But I'm still not sure it is safe to upgrade to FFOS 1.2 or > 1.3 (I'm at 1.0). I've heard of people bricking their ZTE Open. > > Anyone had any good experiences upgrading the ZTE Open? > > I'm okay with it right now and I'm happily writing software and > running it on the ZTE Open. I did have one problem with the OS > versioning, which is that requestAnimationFrame wasn't supported > until after 1.0. > > Other ZTE Open quirks on my blog > http://firefoxosgaming.blogspot.com/search/label/zte%20open. > ___ dev-b2g mailing list > dev-b2g@lists.mozilla.org > https://lists.mozilla.org/listinfo/dev-b2g For what it is worth, I'm running 1.3.0.0-prerelease on my device, and I'd say it requires about as many reboots per day as 1.0.0 did. My usage is mostly limited to making phone calls, playing audio, and browsing the web. There were enough improvements in the OS that outweigh the instability of a bleeding edge release to the point that I have no desire to downgrade to a more "stable" release. I also have the peace of mind that any bugs I submit will relevant to current development. jezra ___ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g
Re: [b2g] Suggesting Sites for "Im thinking of.."
On Mon, 4 Nov 2013 07:59:52 -0800 (PST) an wrote: > On Monday, November 4, 2013 1:16:13 PM UTC+2, lucascar...@gmail.com > wrote: > > is there a way to suggest apps for the search feature? > > This is a general comment not exactly an answer to the question... > I'm not sure what group of people is Mozilla targeting with B2G but > this search thing right in the middle of the home page with no way to > get rid of it seems totally useless to me. IMO it should be an > optional app (as it used to) not a defining one for the homepage, I > mean how many people, how many times would fire up their phone to > search... apps? ___ > dev-b2g mailing list dev-b2g@lists.mozilla.org > https://lists.mozilla.org/listinfo/dev-b2g I couldn't agree more. Giving owners the ability to put apps on the homescreen was a long overdue change, but putting an app on the homescreen, especially one that is rarely used (I only click it by accident), and having no way to remove that app is extremely annoying indeed. ___ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g
Re: [b2g] ZTE Open-- bricked when updating OS
While I have no solution to your problem, I understand how frustrating it is to ask for help and receive no response. Trust me, you are not alone in your displeasure with ZTE and Mozilla. Had I known the level of support that early adopters would receive, I probably never would have purchased the so called "Open". On Thu, 24 Oct 2013 06:43:26 -0700 (PDT) andres@gmail.com wrote: > I have tried the same procedure that Sven, and get the same message: > > -- Install /sdcard ... > Finding update package... > Opening update package... > Verifying update package... > E:failed to verify whole-file signature > E:signature verification failed > Installation aborted. > > I was very happy to have a new smartphone, but now I'm very pissed > off and dissapointed with ZTE and Mozilla. > > El jueves, 17 de octubre de 2013 10:42:16 UTC-5, Sven Ehret escribió: > > I have a sort-of bricked UK ZTE Open. Recovery dialoge still works, > > but the update from > > http://www.ztedevices.com/support/smart_phone/cba40ed6-d3ab-44c0-bdee-3a15803dc187.html > > cannot be installed. It says verification failed. Maybe because I > > tried upgrading/flashing it before, copypasting things with > > boot.img. > > > > > > > > Can anyone help? > > > > > > > > Best, Sven. > ___ > dev-b2g mailing list > dev-b2g@lists.mozilla.org > https://lists.mozilla.org/listinfo/dev-b2g ___ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g
Re: [b2g] I need some help with my zte open.
On Mon, 21 Oct 2013 07:58:30 +0200 Alexandre Lissy wrote: > Le 21/10/2013 05:14, jezra a écrit : > > [...] > > > > > It has been my experience that the device only loses access to the > > SD card when USB Storage has been enabled *and* the device is > > plugged into a computer. If I am wrong in this assertion, please > > let me know. > > > > Since I don't know the habits of other ZTE Open users/owners, I can > > only comment on my own experiences. When I plug the ZTE Open into my > > computer, 10% of the time, I do so for charging the battery, the > > rest of the time is for accessing the files on the device; Either > > adding or removing music, or copying an image or two off of the > > device so that I can upload images to the web. > > UMS will disable sdcard dwhether you plug or not in a computer ; plus > your usecase might not be the same as all of the other users :) > > One way to mitigate this would be to integrate some popup when you > plug into the computer, to propose UMS, maybe. > > ___ > dev-b2g mailing list > dev-b2g@lists.mozilla.org > https://lists.mozilla.org/listinfo/dev-b2g Enabling USB storage on my device has never disabled access to the SD Card except when plugged into a computer. My use case may not be like the others, but since the web browser on my device doesn't open a file selection dialog when I click on a file input field of a web form, I have no choice but to connect to a another computer and copy images off of my ZTE Open. ___ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g
Re: [b2g] Updating ZTE Open to 1.1
On Mon, 21 Oct 2013 18:03:00 +0200 Julien Wajsberg wrote: > Le 18/10/2013 19:30, jezra a écrit : > > When I first used my ZTE Open, I found a bug and reported the bug. > > For all I know, the bug I reported was fixed a few months ago in > > v1.1, but since there is no easy way for beta testers to keep their > > ZTE devices up to date, I may have just been wasting valuable > > developer time. > > > > Don't worry, filing dupe bugs is never wasting time. It usually means > the initial bug was not easy to find, and your new duplicated bug will > make it easier to find for other users and contributors. > > So don't feel bad about this, and thanks a lot. Please continue filing > other bugs if you find some without an existing bug :-) > > Although it's right we probably fixed most of 1.0 issues already, and > bugs for 1.2 would be more valuable, so I really thank all people > helping others to upgrade their phone. It really should be easier. > > Thanks for your support, It isn't just developer time that is getting wasted, the people answering questions on the "support" site are also dealing with people having problems with 1.0 on ZTE Open. signature.asc Description: PGP signature ___ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g
Re: [b2g] Will ZTE Open be kept up-to-date?
On Mon, 21 Oct 2013 06:00:07 -0700 (PDT) danni...@gmail.com wrote: > I have read that some people have installed 1.1 on ZTE Open. But that > wasn't through the built-in updater then? Will every new version of > Firefox OS face the same level of uncertainty of reaching ZTE Open? > ___ dev-b2g mailing list > dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g In short, Yes. Owners of a ZTE Open will need to either download the source of firefox os and compile it themselves, or they will need to wait and hope that ZTE provides an update of some sort. If you really want a device running Firefox OS, get a geeksphone. Then you will be able to go to http://downloads.geeksphone.com/ and get precompiled images for the device, and you, the owner, will get to pick which version of Firefox OS runs on your device. ___ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g
Re: [b2g] I need some help with my zte open.
On Sun, 20 Oct 2013 10:49:59 +0200 Alexandre Lissy wrote: > Le 20/10/2013 10:48, Panos Astithas a écrit : > > On Sat, Oct 19, 2013 at 11:44 PM, jezra wrote: > > > >> 1. Open the settings app > >> 2. scroll down to 'storage' > >> 3. click "Enable USB Storage" > >> > >> Why this isn't on be default is beyond me. > >> > > > > Presumably because if your locked phone got stolen or briefly > > "borrowed", one would only need to plug it into a computer to steal > > your data. > > Or because when you enable UMS, then the device loses its access to > the SDCard for apps, which is not really a good thing. > > > ___ > > dev-b2g mailing list > > dev-b2g@lists.mozilla.org > > https://lists.mozilla.org/listinfo/dev-b2g > > > > ___ > dev-b2g mailing list > dev-b2g@lists.mozilla.org > https://lists.mozilla.org/listinfo/dev-b2g It has been my experience that the device only loses access to the SD card when USB Storage has been enabled *and* the device is plugged into a computer. If I am wrong in this assertion, please let me know. Since I don't know the habits of other ZTE Open users/owners, I can only comment on my own experiences. When I plug the ZTE Open into my computer, 10% of the time, I do so for charging the battery, the rest of the time is for accessing the files on the device; Either adding or removing music, or copying an image or two off of the device so that I can upload images to the web. ___ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g
Re: [b2g] I need some help with my zte open.
On Sat, 19 Oct 2013 17:58:04 -0400 Hubert Figuière wrote: > On 19/10/13 04:44 PM, jezra wrote: > > 1. Open the settings app > > 2. scroll down to 'storage' > > 3. click "Enable USB Storage" > > > > Why this isn't on be default is beyond me. > > This is not MTP btw. > > Hub > ___ > dev-b2g mailing list > dev-b2g@lists.mozilla.org > https://lists.mozilla.org/listinfo/dev-b2g You are correct, but now you can access the device from your Ubuntu computer. ___ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g
Re: [b2g] I need some help with my zte open.
1. Open the settings app 2. scroll down to 'storage' 3. click "Enable USB Storage" Why this isn't on be default is beyond me. On Sat, 19 Oct 2013 11:26:47 +0200 Esteban Izaguirre wrote: > It's not being detected by ubuntu 13.04. In the ubuntu irc, the told > me to enable mtp on the phone. I googled to no avail, how can you > enable mtp on the zte open, on firefox os? Thanks. > ___ > dev-b2g mailing list > dev-b2g@lists.mozilla.org > https://lists.mozilla.org/listinfo/dev-b2g ___ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g
Re: [b2g] Updating ZTE Open to 1.1
On Fri, 18 Oct 2013 08:51:14 -0700 Aaron Borden wrote: > On Thu, 2013-10-17 at 08:37 -0700, jezra wrote: > > If the owners of ZTE Opens had a nice easy way to get the latest > > stable and testing images for their devices (like the geeksphone > > users have at http://downloads.geeksphone.com/) none of this would > > be an issue. > > Agreed. It's a bummer that a device marketed as a "development" device > cannot be used for development out of box. > > -Aaron > > > ___ > dev-b2g mailing list > dev-b2g@lists.mozilla.org > https://lists.mozilla.org/listinfo/dev-b2g It seems as though they have taken a page from Tizen's book and consider a "developer" to only mean someone that will be developing an html5 app for the app store. When I first used my ZTE Open, I found a bug and reported the bug. For all I know, the bug I reported was fixed a few months ago in v1.1, but since there is no easy way for beta testers to keep their ZTE devices up to date, I may have just been wasting valuable developer time. ___ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g
Re: [b2g] Updating ZTE Open to 1.1
On Thu, 17 Oct 2013 01:28:10 -0700 (PDT) Eduardo González wrote: > Hi! I'm author of adapted boot image, and is correct is not > recommended use files from third party as file hosted by me, but the > issue about create own boot.img is not so easy. Before talk about > boot.img, is necessary remember that flashing the zte open > using ./flash.sh require fastboot full supported. If you get problems > using flash.sh (as exact messages posted by Sven) then you have a > device without fastboot full supported. In order to enable fastboot > you must update using DEV images from ztedevices.com, for example the > images of UK American Standard or European Standard. Check > https://developer.mozilla.org/en-US/docs/Mozilla/Firefox_OS/Developer_phone_guide/ZTE_OPEN > > Next step is use boot image adapted by me as explained on > http://sl.edujose.org/2013/10/adapted-boot-image-for-use-with-b2g.html > By default, b2g tree do not create boot.img. You must define on > device tree (/device) the elements required so kernels is > compiled and generate boot.img. Additionally stock boot.img contain a > kernel using particular modules (zte blobs) not included into b2g > kernel source ___ dev-b2g > mailing list dev-b2g@lists.mozilla.org > https://lists.mozilla.org/listinfo/dev-b2g If the owners of ZTE Opens had a nice easy way to get the latest stable and testing images for their devices (like the geeksphone users have at http://downloads.geeksphone.com/) none of this would be an issue. ___ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g
Re: [b2g] ZTE Open-- bricked when updating OS
Thank you. I suppose I was expecting something more "official" than a file hosted on a 3rd party file locker, but if it works I'll be content. On Tue, 15 Oct 2013 15:51:14 -0700 "平田修樹 (Naoki Hirata)" wrote: > It's the second link I emailed; here is the link again, courtesy of > Eduardo : > > http://sl.edujose.org/2013/10/adapted-boot-image-for-use-with-b2g.html > > > > On 10/15/13 1:54 PM, jezra wrote: > > Thank you. It appears that boot.img is not part of the build > > process; only ramdisk.img, userdata.img, and system.img get built. > > How/where do I find the boot.img? > > > > On Tue, 15 Oct 2013 13:36:10 -0700 > > "平田修樹 (Naoki Hirata)" wrote: > > > >> This should basically do what you want if you create this as a > >> script. If you want to keep your user data, you'll want to just > >> skip/remove the userdata lines. > >> > >> #!/bin/bash > >> echo + using adb to reboot to fastboot mode && > >> adb reboot bootloader > >> > >> echo + Checking to see if we see the device using fastboot && > >> fastboot devices && > >> echo + Flashing cache && > >> fastboot flash cache ramdisk.img && > >> echo + Flashing userdata && > >> fastboot flash userdata userdata.img && > >> echo + Flashing system && > >> fastboot flash system system.img && > >> echo + Flashing boot && > >> fastboot flash boot boot.img && > >> echo + Flashing rebooting the device && > >> fastboot reboot && > >> echo + Done! > >> > >> > >> On 10/15/13 12:50 PM, jezra wrote: > >>> I am using Linux, and I have adb and fastboot installed. > >>> > >>> On Tue, 15 Oct 2013 12:45:11 -0700 > >>> "平田修樹 (Naoki Hirata)" wrote: > >>> > >>>> I apologize. I wasn't aware that you had not built your own > >>>> images, that was my bad assumption. > >>>> > >>>> Have you installed the android sdk? You will need to do so in > >>>> order to flash the device. > >>>> Also which platform are you using ( Windows, Mac or linux )? > >>>> > >>>> Regards, > >>>> Naoki > >>>> On 10/15/13 12:25 PM, jezra wrote: > >>>>> Presumably, the 'flash.sh' script runs 3 or 4 commands that > >>>>> involve fastboot; and it shouldn't be necessary for beta testers > >>>>> (which is what anyone who purchased a ZTE Open is), to install > >>>>> the full build environment just to use fastboot for flashing > >>>>> images to their device. > >>>>> > >>>>> As I fall within the category of people who don't have the > >>>>> resources for a full build environment, I have downloaded > >>>>> compiled images from a fellow ZTE owner who was kind enough to > >>>>> compile Firefox OS from source. Now that I have these .img > >>>>> files, I would like to know how to use fastboot to install them > >>>>> onto my device. > >>>>> > >>>>> Any instructions for using fastboot would be greatly > >>>>> appreciated. > >>>>> > >>>>> jezra > >>>>> > >>>>> On Tue, 15 Oct 2013 11:03:59 -0700 > >>>>> "平田修樹 (Naoki Hirata)" wrote: > >>>>> > >>>>>> The script flash.sh in the main repository should flash all the > >>>>>> parts including the boot.img. > >>>>>> ie: /flash.sh > >>>>>> > >>>>>> On 10/15/13 11:03 AM, jezra wrote: > >>>>>>> Thank you for the instructions for putting the ZTE Open into > >>>>>>> fastboot mode. If possible, can you also supply the > >>>>>>> instructions for using fastboot to flash compiled B2G images > >>>>>>> onto the ZTE Open? > >>>>>>> > >>>>>>> On Tue, 15 Oct 2013 10:55:41 -0700 > >>>>>>> "平田修樹 (Naoki Hirata)" wrote: > >>>>>>> > >>>>>>>> https://wiki.mozilla.org/B2G/QA/Tips_And_Tricks#Hardware_Cheat_codes > >>>>>>>> FYI, Inari refers to the ZTE Open. > >>>>>>&g
Re: [b2g] ZTE Open-- bricked when updating OS
Thank you. It appears that boot.img is not part of the build process; only ramdisk.img, userdata.img, and system.img get built. How/where do I find the boot.img? On Tue, 15 Oct 2013 13:36:10 -0700 "平田修樹 (Naoki Hirata)" wrote: > This should basically do what you want if you create this as a > script. If you want to keep your user data, you'll want to just > skip/remove the userdata lines. > > #!/bin/bash > echo + using adb to reboot to fastboot mode && > adb reboot bootloader > > echo + Checking to see if we see the device using fastboot && > fastboot devices && > echo + Flashing cache && > fastboot flash cache ramdisk.img && > echo + Flashing userdata && > fastboot flash userdata userdata.img && > echo + Flashing system && > fastboot flash system system.img && > echo + Flashing boot && > fastboot flash boot boot.img && > echo + Flashing rebooting the device && > fastboot reboot && > echo + Done! > > > On 10/15/13 12:50 PM, jezra wrote: > > I am using Linux, and I have adb and fastboot installed. > > > > On Tue, 15 Oct 2013 12:45:11 -0700 > > "平田修樹 (Naoki Hirata)" wrote: > > > >> I apologize. I wasn't aware that you had not built your own > >> images, that was my bad assumption. > >> > >> Have you installed the android sdk? You will need to do so in > >> order to flash the device. > >> Also which platform are you using ( Windows, Mac or linux )? > >> > >> Regards, > >> Naoki > >> On 10/15/13 12:25 PM, jezra wrote: > >>> Presumably, the 'flash.sh' script runs 3 or 4 commands that > >>> involve fastboot; and it shouldn't be necessary for beta testers > >>> (which is what anyone who purchased a ZTE Open is), to install > >>> the full build environment just to use fastboot for flashing > >>> images to their device. > >>> > >>> As I fall within the category of people who don't have the > >>> resources for a full build environment, I have downloaded compiled > >>> images from a fellow ZTE owner who was kind enough to compile > >>> Firefox OS from source. Now that I have these .img files, I would > >>> like to know how to use fastboot to install them onto my device. > >>> > >>> Any instructions for using fastboot would be greatly appreciated. > >>> > >>> jezra > >>> > >>> On Tue, 15 Oct 2013 11:03:59 -0700 > >>> "平田修樹 (Naoki Hirata)" wrote: > >>> > >>>> The script flash.sh in the main repository should flash all the > >>>> parts including the boot.img. > >>>> ie: /flash.sh > >>>> > >>>> On 10/15/13 11:03 AM, jezra wrote: > >>>>> Thank you for the instructions for putting the ZTE Open into > >>>>> fastboot mode. If possible, can you also supply the instructions > >>>>> for using fastboot to flash compiled B2G images onto the ZTE > >>>>> Open? > >>>>> > >>>>> On Tue, 15 Oct 2013 10:55:41 -0700 > >>>>> "平田修樹 (Naoki Hirata)" wrote: > >>>>> > >>>>>> https://wiki.mozilla.org/B2G/QA/Tips_And_Tricks#Hardware_Cheat_codes > >>>>>> FYI, Inari refers to the ZTE Open. > >>>>>> > >>>>>> Doing the vol down+up + power should put you in fastboot mode. > >>>>>> This means that the "fastboot" should be able to see the > >>>>>> device. ie: fastboot devices > >>>>>> > >>>>>> If that is the case, then you can flash partition images onto > >>>>>> the phone using fastboot. This is what the flash.sh script > >>>>>> does. It puts the device in fastboot mode and then flashes > >>>>>> the images per fastboot. > >>>>>> > >>>>>> Chances if you are in fastboot mode then the boot.img that they > >>>>>> pointed you to worked. The problem is described by Eduardo on > >>>>>> a separate thread: > >>>>>> http://sl.edujose.org/2013/10/adapted-boot-image-for-use-with-b2g.html > >>>>>> > >>>>>> Once you place the boot.img in the proper location, give > >>>>>> flash.sh another go. If that still doesn't work please let me > >&
Re: [b2g] ZTE Open-- bricked when updating OS
I am using Linux, and I have adb and fastboot installed. On Tue, 15 Oct 2013 12:45:11 -0700 "平田修樹 (Naoki Hirata)" wrote: > I apologize. I wasn't aware that you had not built your own images, > that was my bad assumption. > > Have you installed the android sdk? You will need to do so in order > to flash the device. > Also which platform are you using ( Windows, Mac or linux )? > > Regards, > Naoki > On 10/15/13 12:25 PM, jezra wrote: > > Presumably, the 'flash.sh' script runs 3 or 4 commands that involve > > fastboot; and it shouldn't be necessary for beta testers (which is > > what anyone who purchased a ZTE Open is), to install the full build > > environment just to use fastboot for flashing images to their > > device. > > > > As I fall within the category of people who don't have the > > resources for a full build environment, I have downloaded compiled > > images from a fellow ZTE owner who was kind enough to compile > > Firefox OS from source. Now that I have these .img files, I would > > like to know how to use fastboot to install them onto my device. > > > > Any instructions for using fastboot would be greatly appreciated. > > > > jezra > > > > On Tue, 15 Oct 2013 11:03:59 -0700 > > "平田修樹 (Naoki Hirata)" wrote: > > > >> The script flash.sh in the main repository should flash all the > >> parts including the boot.img. > >> ie: /flash.sh > >> > >> On 10/15/13 11:03 AM, jezra wrote: > >>> Thank you for the instructions for putting the ZTE Open into > >>> fastboot mode. If possible, can you also supply the instructions > >>> for using fastboot to flash compiled B2G images onto the ZTE Open? > >>> > >>> On Tue, 15 Oct 2013 10:55:41 -0700 > >>> "平田修樹 (Naoki Hirata)" wrote: > >>> > >>>> https://wiki.mozilla.org/B2G/QA/Tips_And_Tricks#Hardware_Cheat_codes > >>>> FYI, Inari refers to the ZTE Open. > >>>> > >>>> Doing the vol down+up + power should put you in fastboot mode. > >>>> This means that the "fastboot" should be able to see the device. > >>>> ie: fastboot devices > >>>> > >>>> If that is the case, then you can flash partition images onto the > >>>> phone using fastboot. This is what the flash.sh script does. It > >>>> puts the device in fastboot mode and then flashes the images per > >>>> fastboot. > >>>> > >>>> Chances if you are in fastboot mode then the boot.img that they > >>>> pointed you to worked. The problem is described by Eduardo on a > >>>> separate thread: > >>>> http://sl.edujose.org/2013/10/adapted-boot-image-for-use-with-b2g.html > >>>> > >>>> Once you place the boot.img in the proper location, give flash.sh > >>>> another go. If that still doesn't work please let me know. > >>>> The other thing we could potentially do is flash just gecko/gaia > >>>> on the device provided that you can reboot the device and have > >>>> adb access. This is done by : > >>>> /flash.sh gecko > >>>> /gaia/make reset-gaia > >>>> > >>>> Regards, > >>>> Naoki > >>>> > >>>> On 10/15/13 10:29 AM, daniel.i...@googlemail.com wrote: > >>>>> Michael: Thank you but, it took around 15 e-mails and over two > >>>>> weeks mailing around with the eBay seller until they actually > >>>>> understood my problem. They kept pointing me to the download > >>>>> already discussed in this thread over and over again, and I had > >>>>> the impression that I was talking to a wall. As explained, when > >>>>> they finally realized the actual problem they offered me a new > >>>>> phone for 80% of the initial price (which is a 20% discount). > >>>>> > >>>>> Again, I am not willing to throw an almost completely new phone > >>>>> (never carried around, no scratches, screen cover not removed > >>>>> yet etc.) in the trash can and buy a (discounted) new one just > >>>>> because the firmware is bricked and ZTE refuses to reflash it. > >>>>> This is the complete opposite of what I was expecting from a > >>>>> device marketed as developer phone - not mentioning that it's > >>>>> completely crazy
Re: [b2g] ZTE Open-- bricked when updating OS
Presumably, the 'flash.sh' script runs 3 or 4 commands that involve fastboot; and it shouldn't be necessary for beta testers (which is what anyone who purchased a ZTE Open is), to install the full build environment just to use fastboot for flashing images to their device. As I fall within the category of people who don't have the resources for a full build environment, I have downloaded compiled images from a fellow ZTE owner who was kind enough to compile Firefox OS from source. Now that I have these .img files, I would like to know how to use fastboot to install them onto my device. Any instructions for using fastboot would be greatly appreciated. jezra On Tue, 15 Oct 2013 11:03:59 -0700 "平田修樹 (Naoki Hirata)" wrote: > The script flash.sh in the main repository should flash all the parts > including the boot.img. > ie: /flash.sh > > On 10/15/13 11:03 AM, jezra wrote: > > Thank you for the instructions for putting the ZTE Open into > > fastboot mode. If possible, can you also supply the instructions > > for using fastboot to flash compiled B2G images onto the ZTE Open? > > > > On Tue, 15 Oct 2013 10:55:41 -0700 > > "平田修樹 (Naoki Hirata)" wrote: > > > >> https://wiki.mozilla.org/B2G/QA/Tips_And_Tricks#Hardware_Cheat_codes > >> FYI, Inari refers to the ZTE Open. > >> > >> Doing the vol down+up + power should put you in fastboot mode. > >> This means that the "fastboot" should be able to see the device. > >> ie: fastboot devices > >> > >> If that is the case, then you can flash partition images onto the > >> phone using fastboot. This is what the flash.sh script does. It > >> puts the device in fastboot mode and then flashes the images per > >> fastboot. > >> > >> Chances if you are in fastboot mode then the boot.img that they > >> pointed you to worked. The problem is described by Eduardo on a > >> separate thread: > >> http://sl.edujose.org/2013/10/adapted-boot-image-for-use-with-b2g.html > >> > >> Once you place the boot.img in the proper location, give flash.sh > >> another go. If that still doesn't work please let me know. > >> The other thing we could potentially do is flash just gecko/gaia on > >> the device provided that you can reboot the device and have adb > >> access. This is done by : > >> /flash.sh gecko > >> /gaia/make reset-gaia > >> > >> Regards, > >> Naoki > >> > >> On 10/15/13 10:29 AM, daniel.i...@googlemail.com wrote: > >>> Michael: Thank you but, it took around 15 e-mails and over two > >>> weeks mailing around with the eBay seller until they actually > >>> understood my problem. They kept pointing me to the download > >>> already discussed in this thread over and over again, and I had > >>> the impression that I was talking to a wall. As explained, when > >>> they finally realized the actual problem they offered me a new > >>> phone for 80% of the initial price (which is a 20% discount). > >>> > >>> Again, I am not willing to throw an almost completely new phone > >>> (never carried around, no scratches, screen cover not removed yet > >>> etc.) in the trash can and buy a (discounted) new one just because > >>> the firmware is bricked and ZTE refuses to reflash it. This is the > >>> complete opposite of what I was expecting from a device marketed > >>> as developer phone - not mentioning that it's completely crazy > >>> when looking at it from an ecologic perspective. > >>> > >>> Vinayak: Well, this is as similar to my situation, I assume you > >>> can also access see the device over USB being in diagnostic mode > >>> when you boot it by holding both voldown+volup + power although > >>> the screen remains black? > >>> ___ dev-b2g mailing > >>> list dev-b2g@lists.mozilla.org > >>> https://lists.mozilla.org/listinfo/dev-b2g > >> ___ > >> dev-b2g mailing list > >> dev-b2g@lists.mozilla.org > >> https://lists.mozilla.org/listinfo/dev-b2g > > ___ > dev-b2g mailing list > dev-b2g@lists.mozilla.org > https://lists.mozilla.org/listinfo/dev-b2g ___ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g
Re: [b2g] ZTE Open-- bricked when updating OS
Thank you for the instructions for putting the ZTE Open into fastboot mode. If possible, can you also supply the instructions for using fastboot to flash compiled B2G images onto the ZTE Open? On Tue, 15 Oct 2013 10:55:41 -0700 "平田修樹 (Naoki Hirata)" wrote: > https://wiki.mozilla.org/B2G/QA/Tips_And_Tricks#Hardware_Cheat_codes > FYI, Inari refers to the ZTE Open. > > Doing the vol down+up + power should put you in fastboot mode. > This means that the "fastboot" should be able to see the device. ie: > fastboot devices > > If that is the case, then you can flash partition images onto the > phone using fastboot. This is what the flash.sh script does. It > puts the device in fastboot mode and then flashes the images per > fastboot. > > Chances if you are in fastboot mode then the boot.img that they > pointed you to worked. The problem is described by Eduardo on a > separate thread: > http://sl.edujose.org/2013/10/adapted-boot-image-for-use-with-b2g.html > > Once you place the boot.img in the proper location, give flash.sh > another go. If that still doesn't work please let me know. > The other thing we could potentially do is flash just gecko/gaia on > the device provided that you can reboot the device and have adb > access. This is done by : > /flash.sh gecko > /gaia/make reset-gaia > > Regards, > Naoki > > On 10/15/13 10:29 AM, daniel.i...@googlemail.com wrote: > > Michael: Thank you but, it took around 15 e-mails and over two > > weeks mailing around with the eBay seller until they actually > > understood my problem. They kept pointing me to the download > > already discussed in this thread over and over again, and I had the > > impression that I was talking to a wall. As explained, when they > > finally realized the actual problem they offered me a new phone for > > 80% of the initial price (which is a 20% discount). > > > > Again, I am not willing to throw an almost completely new phone > > (never carried around, no scratches, screen cover not removed yet > > etc.) in the trash can and buy a (discounted) new one just because > > the firmware is bricked and ZTE refuses to reflash it. This is the > > complete opposite of what I was expecting from a device marketed as > > developer phone - not mentioning that it's completely crazy when > > looking at it from an ecologic perspective. > > > > Vinayak: Well, this is as similar to my situation, I assume you can > > also access see the device over USB being in diagnostic mode when > > you boot it by holding both voldown+volup + power although the > > screen remains black? > > ___ dev-b2g mailing > > list dev-b2g@lists.mozilla.org > > https://lists.mozilla.org/listinfo/dev-b2g > > ___ > dev-b2g mailing list > dev-b2g@lists.mozilla.org > https://lists.mozilla.org/listinfo/dev-b2g ___ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g
Re: [b2g] instructions for using fastboot to flash ZTE Open
On Mon, 14 Oct 2013 16:08:26 -0700 (PDT) trevorc.rit...@gmail.com wrote: > On Sunday, October 13, 2013 8:30:29 PM UTC-7, jezra wrote: > > Does anyone have instructions for using fastboot to flash the ZTE > > Open? > > > > > > > > Jezra > > > > > > > > Web: http://www.jezra.net > > > > Status: http://status.jezra.net > > > > Coffee: http://coffee.jezra.net > > I used the instructions on the Mozilla developer wiki to flash my ZTE > Open to 1.2. Start here: > https://developer.mozilla.org/en-US/docs/Mozilla/Firefox_OS/Firefox_OS_build_prerequisites > > Note that I ran into an error with settimeofday at the end of the > flash process. The build did not create a boot.img and I had to use > one provided by Eduardo González in this thread: > https://groups.google.com/forum/#!topic/mozilla.dev.b2g/S5gNK3Mj22k > > > Trevor > ___ > dev-b2g mailing list > dev-b2g@lists.mozilla.org > https://lists.mozilla.org/listinfo/dev-b2g Those instructions deal with the prerequisites for building the OS, at the end of the page is a link to the instructions for getting ready to compile the OS. Neither of those pages contains information about using fastboot. The closest I've been able to find is on https://developer.mozilla.org/en-US/docs/Mozilla/Firefox_OS/Installing_on_a_mobile_device but the instructions assume one has set up a full build environment and compiled the source, and the instructions do not cover using fastboot. ___ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g
Re: [b2g] ZTE Open-- bricked when updating OS
My comment wasn't directed at your judgment. I was actually agreeing with you and I feel that Mozilla did an extremely poor job in vetting ZTE as a 'partner'. As an owner of a ZTE Open, my best advise would be to avoid the ZTE and get a phone from a company that seems to care. If the rollout of 1.1 is any indication, get a geeksphone; they've had 1.1 for a few months and, from what I can tell, they haven't had anti-consumer locks on the devices that they manufacture. jezra On Mon, 14 Oct 2013 21:18:09 +0300 andu novac wrote: > Can you elaborate, which part is "extremely poor" in my judgement? The > fact that we have this exchange on this list should at least tell you > that I am both interested in this OS and also aware of its current > state/problems from people who actually work on it. I also installed > it on my phone but since I didn't get any usable help on the power > button issue I gave up on that. Also the fact that I was willing to > spend 80E on a less then minimally attractive device just for its OS > should also tell you something (yeah, maybe this is the poor judgement > you were referring to). But what do you say about the "partners" who > market a phone that bricks itself while upgrading and instead of > providing service or replacement they want to sell you a new one? > > On Mon, Oct 14, 2013 at 7:12 PM, jezra wrote: > > Extremely poor judgment when vetting "partners" > > > > On Sun, 13 Oct 2013 12:08:47 -0700 (PDT) > > an wrote: > > > >> "Unfortunately, ZTE refuses any support (even if you would pay for > >> the reflash!) in this case and redirects all requests to the eBay > >> seller who proposes to send me a new device for 80% of the price. > >> Sorry guys, but this is absolutely unacceptable!" > >> > >> Thanks for this, I was planing to get a zte open "developer device" > >> shitty as it is. > >> > >> But don't blame zte, they never claimed to not being there just for > >> your money, blame Firefox execs who rushed out there with a barely > >> working OS on top of garbage hardware. > >> ___ dev-b2g mailing > >> list dev-b2g@lists.mozilla.org > >> https://lists.mozilla.org/listinfo/dev-b2g > > ___ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g
Re: [b2g] ZTE Open-- bricked when updating OS
Extremely poor judgment when vetting "partners" On Sun, 13 Oct 2013 12:08:47 -0700 (PDT) an wrote: > "Unfortunately, ZTE refuses any support (even if you would pay for > the reflash!) in this case and redirects all requests to the eBay > seller who proposes to send me a new device for 80% of the price. > Sorry guys, but this is absolutely unacceptable!" > > Thanks for this, I was planing to get a zte open "developer device" > shitty as it is. > > But don't blame zte, they never claimed to not being there just for > your money, blame Firefox execs who rushed out there with a barely > working OS on top of garbage hardware. > ___ dev-b2g mailing list > dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g ___ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g
[b2g] instructions for using fastboot to flash ZTE Open
Does anyone have instructions for using fastboot to flash the ZTE Open? Jezra Web: http://www.jezra.net Status: http://status.jezra.net Coffee: http://coffee.jezra.net ___ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g
Re: [b2g] How do I flash an image without download all of the source code?
While trying to flash my ZTE Open using fastboot, running `fastboot flash boot boot.img` outputs "< waiting for device >" Running `adb reboot recovery` however, will reboot the device. On Thu, 10 Oct 2013 19:07:09 +0100 Chris Mills wrote: > > On 10 Oct 2013, at 16:22, jezra wrote: > > > In this case, my issues had less to do with the build, and more to > > do with getting a machine running an appropriate distro and more > > importantly, having enough free space on the harddrive. > > Oh, ok. No worries then. Let me know if any issues with the docs do > crop up, and I'll be glad to fix them. > > > > > P.S. check your audio port for pocket lint. it happens. > > ;-) ___ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g
Re: [b2g] How do I flash an image without download all of the source code?
In this case, my issues had less to do with the build, and more to do with getting a machine running an appropriate distro and more importantly, having enough free space on the harddrive. P.S. check your audio port for pocket lint. it happens. On Thu, 10 Oct 2013 09:35:10 +0100 Chris Mills wrote: > Hrm, this doesn't sound good. Do you want to share the problems you > encountered during the config/build process? At > > https://developer.mozilla.org/en-US/docs/Mozilla/Firefox_OS/Developer_phone_guide/ZTE_OPEN#Device_support > > I included the instructions to follow the MDN build procedure, > treating the ZTE as if it is an Inari device. I found this to work > ok, but it'd be good to work out why it is going wrong for you, so we > can update the instructions to be more helpful. > > Best regards, > > Chris Mills >Senior tech writer || Mozilla > developer.mozilla.org || MDN >cmi...@mozilla.com || @chrisdavidmills > > > > On 10 Oct 2013, at 07:33, jezra wrote: > > > Yup, did it a few days ago, but then I ran into enough issues trying > > to set up a build environment that I decided to wait until someone > > shared a compiled image. > > > > On Thu, 10 Oct 2013 06:39:49 +0100 > > Chris Mills wrote: > > > >> Hi Jezra, > >> > >> Have you updated the device to be fastboot-enabled, as detailed at > >> > >> https://developer.mozilla.org/en-US/docs/Mozilla/Firefox_OS/Developer_phone_guide/ZTE_OPEN#Device_revisions > >> > >> ? > >> > >> Chris Mills > >> Senior tech writer || Mozilla > >> developer.mozilla.org || MDN > >> cmi...@mozilla.com || @chrisdavidmills > >> > >> > >> > >> On 10 Oct 2013, at 02:21, jezra wrote: > >> > >>> I'm trying to flash an image to my ZTE Open that was compiled by > >>> someone else. When I try to run the flash.sh script in my B2G > >>> directory, I am greeted with: > >>> > >>> load-config.sh: line 7: /storage/Systems/ZTEShitty/B2G/.config: No > >>> such file or directory Could not load .config. Did you run > >>> config.sh? > >>> > >>> According to the docs, running config.sh will take "tens of hours" > >>> and will also download multiple gigabytes of files to my computer. > >>> Is it really necessary for me to fill my harddrive and wait "tens > >>> of hours" in order to flash an image onto my device? > >>> > >>> Jezra > >>> > >>> Web: http://www.jezra.net > >>> Status: http://status.jezra.net > >>> Coffee: http://coffee.jezra.net > >>> ___ > >>> dev-b2g mailing list > >>> dev-b2g@lists.mozilla.org > >>> https://lists.mozilla.org/listinfo/dev-b2g > >> > > > > ___ > dev-b2g mailing list > dev-b2g@lists.mozilla.org > https://lists.mozilla.org/listinfo/dev-b2g ___ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g
Re: [b2g] How do I flash an image without download all of the source code?
Yup, did it a few days ago, but then I ran into enough issues trying to set up a build environment that I decided to wait until someone shared a compiled image. On Thu, 10 Oct 2013 06:39:49 +0100 Chris Mills wrote: > Hi Jezra, > > Have you updated the device to be fastboot-enabled, as detailed at > > https://developer.mozilla.org/en-US/docs/Mozilla/Firefox_OS/Developer_phone_guide/ZTE_OPEN#Device_revisions > > ? > > Chris Mills >Senior tech writer || Mozilla > developer.mozilla.org || MDN >cmi...@mozilla.com || @chrisdavidmills > > > > On 10 Oct 2013, at 02:21, jezra wrote: > > > I'm trying to flash an image to my ZTE Open that was compiled by > > someone else. When I try to run the flash.sh script in my B2G > > directory, I am greeted with: > > > > load-config.sh: line 7: /storage/Systems/ZTEShitty/B2G/.config: No > > such file or directory Could not load .config. Did you run > > config.sh? > > > > According to the docs, running config.sh will take "tens of hours" > > and will also download multiple gigabytes of files to my computer. > > Is it really necessary for me to fill my harddrive and wait "tens > > of hours" in order to flash an image onto my device? > > > > Jezra > > > > Web: http://www.jezra.net > > Status: http://status.jezra.net > > Coffee: http://coffee.jezra.net > > ___ > > dev-b2g mailing list > > dev-b2g@lists.mozilla.org > > https://lists.mozilla.org/listinfo/dev-b2g > ___ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g
[b2g] How do I flash an image without download all of the source code?
I'm trying to flash an image to my ZTE Open that was compiled by someone else. When I try to run the flash.sh script in my B2G directory, I am greeted with: load-config.sh: line 7: /storage/Systems/ZTEShitty/B2G/.config: No such file or directory Could not load .config. Did you run config.sh? According to the docs, running config.sh will take "tens of hours" and will also download multiple gigabytes of files to my computer. Is it really necessary for me to fill my harddrive and wait "tens of hours" in order to flash an image onto my device? Jezra Web: http://www.jezra.net Status: http://status.jezra.net Coffee: http://coffee.jezra.net ___ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g
Re: [b2g] Non-stock headphones with the ZTE Open
So the problem isn't with headphones per se, but with a headphone/mic combo? On Wed, 09 Oct 2013 18:09:41 -0500 Jim Porter wrote: > Well, darn. I guess I'll have to buy an adapter then. At least then I > can use a better pair of headphones! :) > > - Jim > > On 10/09/2013 05:58 PM, Naoki Hirata wrote: > > It's the phone connector that makes the difference: > > http://en.wikipedia.org/wiki/Phone_connector_%28audio%29 > > > > see https://bugzilla.mozilla.org/show_bug.cgi?id=812607#c4 > > > > Regards, > > Naoki > > > > On 10/9/13 3:51 PM, Jim Porter wrote: > >> Does anyone know what's required to make non-stock headphones work > >> with the ZTE Open? The headphones that came with it (or maybe that > >> came with the Unagi?) work fine, but other headphones don't work at > >> all. Plugging them in shows the headphone icon in the utility tray, > >> but audio doesn't come out of the headphones. I've tested multiple > >> pairs and they all do this. > >> > >> To make matters worse, I lost the pair of headphones that does work > >> with the ZTE Open, making it a lot harder for me to dogfood. > >> > >> Any ideas? > >> > >> - Jim > > ___ > dev-b2g mailing list > dev-b2g@lists.mozilla.org > https://lists.mozilla.org/listinfo/dev-b2g ___ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g
Re: [b2g] Non-stock headphones with the ZTE Open
The issue you are experiencing has never manifested on my device, and I've used headphones that I've soldered myself as well as using the audio port to connect to my car stereo. With this in mind, it may be that there is an issue with your device. On Wed, 09 Oct 2013 17:51:21 -0500 Jim Porter wrote: > Does anyone know what's required to make non-stock headphones work > with the ZTE Open? The headphones that came with it (or maybe that > came with the Unagi?) work fine, but other headphones don't work at > all. Plugging them in shows the headphone icon in the utility tray, > but audio doesn't come out of the headphones. I've tested multiple > pairs and they all do this. > > To make matters worse, I lost the pair of headphones that does work > with the ZTE Open, making it a lot harder for me to dogfood. > > Any ideas? > > - Jim > ___ > dev-b2g mailing list > dev-b2g@lists.mozilla.org > https://lists.mozilla.org/listinfo/dev-b2g ___ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g
Re: [b2g] Need help un-bricking my ZTE Open
Unless you are in the USA, then you need to select 'United Kingdom'; or I could just include the link to final page. http://www.ztedevices.com/support/smart_phone/b5a2981a-1714-4ac7-89e1-630e93e220f8.html?type=software On Tue, 24 Sep 2013 14:20:33 -0700 (PDT) Eduardo González wrote: > Try download firmware from > http://www.ztedevices.com/support/selectproduct.html?type=software > Selecting your region and follow pdf instructions included into zip > file. ___ dev-b2g mailing > list dev-b2g@lists.mozilla.org > https://lists.mozilla.org/listinfo/dev-b2g ___ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g
