Hey Julien, yes you paraphrased my points nicely and the proposed solutions (i.e. having different "channels" to upgrade to) would be absolutely wonderful.
About the browser crashes, I didn't know that the Alcatel was so poorly equipped with hardware. But that would certainly explain things. Thanks for the clarification on that. Cheers, Johannes On 06.06.2014 11:31, Julien Wajsberg wrote: > Hey Johannes, > > If I can summarize your thoughts, in my decreasing order of importance : > > 1. when I report bug, they basically get ignored > -> this is the #1 issue to have a sane community. > > The owners or peers of components should definitely triage their coming > bugs at least once a week. Maybe different people in the team every > week, pick your own process, but letting a user bug without an answer is > really bad. > And this must be done for every component; any component that has no > specific owner needs to have one. > > 2. I want to upgrade my phone, what should I do, which repository can I > take, what is safe ? > -> we need IMO 3 channels: "release", "beta", > "nightly-might-break-your-phone" > I think this is what we're preparing for Flame. Sadly it's more > difficult to do for other phones because binary drivers suck. I mean, > it's not even advisable to make you do this by building yourself... > > FWIW v2.0 is too much a moving target right now; some of our people are > dogfooding it but this is dangerous if you're not in the team. v1.4 is > definitely ok and quite pleasant though. > > 3. Browser is crashing > -> IMO what's really happening is that the webpage uses too much memory, > and the page "crashes" because of out of memory condition. The Alcatel > has only 256MB memory... Even on Peak (512MB) I have this issue > sometimes too. We did huge improvements lately (that you don't have on > 1.2) but still this issue happens sometimes. > > We desperately need something to distinguish a real crash from OOM > conditions; we need something that says "this page uses too much memory > and we had to close it". > We also desperately need to have a tracker blocker: preventing tracking > scripts/images from even loading would definitely save memory. > > Hope this answers some of your questions... I guess I have more > questions than you :) > > Le 03/06/2014 11:48, Johannes Bauer a écrit : >> Hey list, >> >> so I've been using Firefox OS on my Alcatel One Touch Fire since Nov >> 2013 as my only phone on a day-to-day basis. I'd like to share my >> feedback to give you an impression about what I like and dislike about >> it. I've been on branch 1.2 for pretty much the whole trip. >> >> Gernerally when I bought the phone I knew I was getting into a haphazard >> kind of development situation. I knew there was going to be fiddling >> involved and that's okay. The main reason I bought it was beacuse I was >> happy to see an alternative to Android on the market and was curious if >> it were possible to actually actively participate in the project. >> >> About the usage: One of the very very first things I noticed was that >> the phone had a irritating, annoyning and most of all completely useless >> vibration effect when pressing the home button. It's one of the first >> tickets I commented on and it was annoying enough for me to actually >> patch the relevant code (described solution in #885716). Six months >> later: I tried to pull a 1.4 branch only to realize this is still >> exactly the same code. A dev had the ticket assigned to himself only to >> disassign it a few days back saying this isn't going anywhere. >> >> I don't get it. You guys even have a "user experience" team. Those >> people should know how freakishly annoying vibration can be. Why can't >> you just comment out the two lines until it's implemented "properly"? >> Actually I don't think anyone would miss the vibration when pressing the >> home button at all. In any case, it's utterly frustrating to see that >> this is not something that is important enough to warrant attention. >> >> Other quirks: The phone has sometimes really weird behavior when >> dialing. Sometimes it dials the wrong number (i.e. I have three numers >> stored and I absolutely positively press the first one, but it dials up >> the third one). Data import and export is horrible (it was a real pain >> upgrading the phone because there was no option to delete all contacts). >> Also when the number that is dialed is busy it just goes back to the >> address book with no indication what went wrong whatsoever. This is >> pretty annoying (i.e. you have the phone on your ear for a few seconds >> and hear nothing, then you look at it again and it's stopped dialing as >> if you never dialed to begin with). Some random flickering/crashing >> issues too but not reproducible and seldomly enough to be considered >> okay. >> >> Ironically the worst thing about the phone is the browser. Wow, that >> browser sucks so much it's hard to put in words. It feels like Netscape >> Navigator again. Don't know why something with a "Firefox" label can >> have such a horrible browser (which effectively makes it not a "smart" >> phone anymore when Internet is practically unusable). Crashing *all* the >> time, display errors all over the place. Wow. >> >> In any case what I found most frustrating about it all is that I have >> got the feeling that feedback is not taken seriously. On this mailing >> list ironically people are super helpful and enthusiastic and nice, but >> once issues get in the bugtracker, they're just lost. Looking at the >> version history I couldn't even find out what version I was supposed to >> install if I wanted to upgrade. This site: >> >> https://developer.mozilla.org/en-US/Firefox_OS/Releases/1.2 >> >> Lists 1.2, 1.3, 1.4 and 2.0 ALL in pre-release stage which is utterly >> confusing. How can you have multiple branches which are all pre-release? >> Wouldn't it make sense to get just ONE to release quality so you have >> one that you can recommed to users, not just devs? Also the release >> notes focus very much on technical issues, but don't explain the impact >> for the user. So CanvasRenderingContext2D now has a addHitRegion() >> method, which is cool - but does my phone still crash? Does it still >> flicker and dial the wrong numbers? It would be nice if the actual user >> impact were described on top (even though the technical details are >> undoubly nice and helpful for devs). >> >> Ultimately, I've sadly reached my breaking point and think I'll go back >> to my Nokia 6100. Both phones are equally unable to surf the Internet, >> but at least the thing I need my phone most for (phoning people) works >> flawlessly on the Nokia. I actually thought about giving another branch >> a shot but realized that I don't even know which branch I should pick at >> the moment and that I'd have to read all docs again to even get it to >> build. I remember something about having to clone three different repos >> and making some json files to get i18n to work which was quite a PITA. >> >> In any case, hope this report is at least a bit helpful. >> Cheers, >> Johannes >> _______________________________________________ >> dev-b2g mailing list >> [email protected] >> https://lists.mozilla.org/listinfo/dev-b2g > > _______________________________________________ > dev-b2g mailing list > [email protected] > https://lists.mozilla.org/listinfo/dev-b2g _______________________________________________ dev-b2g mailing list [email protected] https://lists.mozilla.org/listinfo/dev-b2g
