Active Topics
-
The N900 is now 15 years old! (9)
to Nokia N900 by Arno_11 - 14 hrs, 7 mins ago -
Sailfish OS for the Motorola Moto G7 Power (XT1955-5) - (ocean) (4)
to SailfishOS by Maemish - 6 days, 2 hrs ago - more...
| The Following User Says Thank You to horus For This Useful Post: | ||
 |
|
2009-12-08
, 09:47
|
|
Posts: 3,159 |
Thanked: 2,023 times |
Joined on Feb 2008
@ Finland
|
#12
|
Originally Posted by horus
I don't get your point...
Don't ever have babies. Haha I kid..
Whilst quality control is rarely 100%, it is possible to minimise error rates on a first batch through quality practices.
yes. and random reboots seem to be very minimal problem when compared to devices that doesn't have the problem. but it is inevidable that those devices must end up to someone..
__________________
Want to know something?
K.I.S.S. approach:
wiki category:beginners. Browse it through and you'll be much wiser!
If the link doesn't help, just use
Google Custom Search
Want to know something?
K.I.S.S. approach:
wiki category:beginners. Browse it through and you'll be much wiser!
If the link doesn't help, just use
Google Custom Search
|
|
2009-12-09
, 01:08
|
|
Posts: 716 |
Thanked: 303 times |
Joined on Sep 2009
@ Sheffield, UK
|
#13
|
Originally Posted by horus
What about when a device tested rock-solid at the factory but had a dry solder joint that only became a problem due to all the bumping around during shipping half way around the world? How do you propose they prevent that?
Don't ever have babies. Haha I kid..
Whilst quality control is rarely 100%, it is possible to minimise error rates on a first batch through quality practices.
Its the same principle with the software. It might prove rock-solid under most configurations but you cannot predict what happens out in the wild. Someone might delete, edit, overwrite a file either intentionally or by installing a piece of software which did not exist during testing, which has a domino effect bringing everything down.
I currently am having WiFi problems where using a weak signal over an hour or so eventually WiFi seems to crash. Could they predict that? Probably not, as it may only happen with a certain chipset router, or with certain chipset routers broadcasting on a stronger signal than the one you are trying to use. There are far far too many variables.
__________________
http://www.speedtest.net/result/877713446.png
My Websites
CSD Projects - Flickr - UAE4Maemo (UAE4All Compatibility List)
Favourite N900 Applications
Picodrive - UAE4All
Please post your UAE4All compatibility reports. Even better, post them to my UAE4Maemo site!
Not sure how UAE4All works such as mouse emulation? Read the FAQ.
http://www.speedtest.net/result/877713446.png
My Websites
CSD Projects - Flickr - UAE4Maemo (UAE4All Compatibility List)
Favourite N900 Applications
Picodrive - UAE4All
Please post your UAE4All compatibility reports. Even better, post them to my UAE4Maemo site!
Not sure how UAE4All works such as mouse emulation? Read the FAQ.
 |
|
2009-12-09
, 01:15
|
|
Posts: 373 |
Thanked: 40 times |
Joined on Nov 2009
@ Norwich
|
#14
|
Originally Posted by solpete
But what if there was a dry joint on one of the address or power supply pins for the CPU?? The resistivety would be quite high making it hard for the electrons to travel therefore causing slowness and/or instability.
Whenever someone starts a thread or writes something about n900 performance being sluggish, immediately some other dude replies that his phone must be faulty.
Phones are identical, either they work or they dont. If the phone reboots then, sure, it could be a geometrical error in design on that specific phone. But still, this geometrical imperfection is within production design limits. The phone is not faulty - the production is.
But when performance is sluggish, I find it very unlikely that there is a hardware error on that phone. I think it is way more probable that the person complaining has higher expectations and/or standards of what is acceptable.
Stop complaining about guys complaining just because you have low expectations and drool as soon as a phone does something where no phone has gone before.
It may well be a flaw in production but in anycase its an intermitant one at least and not all devices are affected. I think its important in these issues to try to be as objective as possible and not jump to conclusions and say that all devices produced are boned.
__________________
i finally have the device and its even better than i could have ever possibley imagined! well done nokia, very well done indeed!
i finally have the device and its even better than i could have ever possibley imagined! well done nokia, very well done indeed!
 |
|
2009-12-09
, 01:17
|
|
Posts: 909 |
Thanked: 216 times |
Joined on Nov 2009
@ Bremen, Germany
|
#15
|
Originally Posted by solpete
wait wait wait - what are we supposed to drool over then, if not something where no phone has gone before???
and drool as soon as a phone does something where no phone has gone before.
dont crush my dreams...
|
|
2009-12-09
, 01:17
|
|
Posts: 373 |
Thanked: 40 times |
Joined on Nov 2009
@ Norwich
|
#16
|
Originally Posted by Alex Atkin UK
haha i didnt even read your post at first but just noticed you mentioned the whole dry joint thing too! I think its a likely scenario.
What about when a device tested rock-solid at the factory but had a dry solder joint that only became a problem due to all the bumping around during shipping half way around the world? How do you propose they prevent that?
Its the same principle with the software. It might prove rock-solid under most configurations but you cannot predict what happens out in the wild. Someone might delete, edit, overwrite a file either intentionally or by installing a piece of software which did not exist during testing, which has a domino effect bringing everything down.
I currently am having WiFi problems where using a weak signal over an hour or so eventually WiFi seems to crash. Could they predict that? Probably not, as it may only happen with a certain chipset router, or with certain chipset routers broadcasting on a stronger signal than the one you are trying to use. There are far far too many variables.
__________________
i finally have the device and its even better than i could have ever possibley imagined! well done nokia, very well done indeed!
i finally have the device and its even better than i could have ever possibley imagined! well done nokia, very well done indeed!
|
|
2009-12-09
, 01:20
|
|
Posts: 1,179 |
Thanked: 770 times |
Joined on Nov 2009
|
#17
|
Originally Posted by solpete
I could not agree with you more. It is very very annoying. It is always that those who have problems with their device are linux or maeomo noobs and have done something wrong with the phone. Don't understand why some here think Nokia can do no wrong.
Whenever someone starts a thread or writes something about n900 performance being sluggish, immediately some other dude replies that his phone must be faulty.
Phones are identical, either they work or they dont. If the phone reboots then, sure, it could be a geometrical error in design on that specific phone. But still, this geometrical imperfection is within production design limits. The phone is not faulty - the production is.
But when performance is sluggish, I find it very unlikely that there is a hardware error on that phone. I think it is way more probable that the person complaining has higher expectations and/or standards of what is acceptable.
Stop complaining about guys complaining just because you have low expectations and drool as soon as a phone does something where no phone has gone before.
I love Nokia more than anyone and I love this phone but it is really frustrating at times how it takes so long to do anything. I give it credit for being able to do so many things at the same time but I wish it could be as snappy as the iphone when doing one thing.
 |
|
2009-12-09
, 11:45
|
|
Posts: 190 |
Thanked: 101 times |
Joined on Oct 2009
|
#18
|
Originally Posted by Alex Atkin UK
If the phone sustained damage from simple shipping practices then it was obviously not thoroughly tested and henceforth Nokia did not apply quality practices.
What about when a device tested rock-solid at the factory but had a dry solder joint that only became a problem due to all the bumping around during shipping half way around the world? How do you propose they prevent that?
|
|
2009-12-09
, 13:26
|
|
Posts: 1,255 |
Thanked: 393 times |
Joined on Oct 2009
@ US
|
#19
|
Originally Posted by solpete
You are assuming mathematical constants on an electronic device with many parameters:
Whenever someone starts a thread or writes something about n900 performance being sluggish, immediately some other dude replies that his phone must be faulty.
Phones are identical, either they work or they dont. If the phone reboots then, sure, it could be a geometrical error in design on that specific phone. But still, this geometrical imperfection is within production design limits. The phone is not faulty - the production is.
But when performance is sluggish, I find it very unlikely that there is a hardware error on that phone. I think it is way more probable that the person complaining has higher expectations and/or standards of what is acceptable.
Stop complaining about guys complaining just because you have low expectations and drool as soon as a phone does something where no phone has gone before.
1. Production
2. Chip population
3. Rom builds and OS population
4. QC control
5. Running OS changes (took place with N900 as published)
6. Connector mating to chipset and case
7. Component sources
I could go on and on. We had problems with something as "simple" as motherboard population- not counting all the other things.
Please do not use your arguements as an opening to a thesis
Last edited by Rushmore; 2009-12-09 at 13:28.
 |
|
2009-12-09
, 13:41
|
|
Posts: 378 |
Thanked: 206 times |
Joined on Dec 2009
@ Denmark
|
#20
|
If someone writes in here, that he got his n900, started it up and was disappointed, because it randomly reboots, it has low framerate in ui animations and hangs all the time when starting up apps...
And then i think about my own n900 experiences since i got the phone.. not a single reboot, smooth ui animations and rarely hangs when starting anything up.
If this is how his phone behaved right out of the box, i think the only conclution anyone can draw from that, is faulty hardware.. or am i wrong?
Last edited by mthmob; 2009-12-09 at 13:43.
And then i think about my own n900 experiences since i got the phone.. not a single reboot, smooth ui animations and rarely hangs when starting anything up.
If this is how his phone behaved right out of the box, i think the only conclution anyone can draw from that, is faulty hardware.. or am i wrong?
Last edited by mthmob; 2009-12-09 at 13:43.
Whilst quality control is rarely 100%, it is possible to minimise error rates on a first batch through quality practices.