We've just launched our map. Add yourself by clicking here!
Module failure notification.
- This topic has 6 replies, 2 voices, and was last updated 8 years ago by
.
One of the greatest innovations behind this phone is the ability to replace a single part after it has malfunctioned. But, let’s say an essential part to the phone such as the screen, cpu, or ram malfunction? There would be no way for the phone to tell you that a part broke or which one it is if any of those parts broke. To fix this problem, each blok needs to have a little red led light that turns on when the blok has confirmed that it is broken. Another solution is to have bare minimum requirements to run a very simple OS within the base, and that can give the phone the ability to notify via the screen that a part has gone bad. Although, if the base itself goes bad, then I don’t see any choice other than to have a little led light kick on as soon as it detects a problem within itself. There could possibly be a backup-bare-minimum-requirements blok which might help, but it wouldn’t have access to the screen if the base is out.What are some of your thoughts on this?
PianoMastR64 wrote: One of the greatest innovations behind this phone is the ability to replace a single part after it has malfunctioned. But, let’s say an essential part to the phone such as the screen, cpu, or ram malfunction? There would be no way for the phone to tell you that a part broke or which one it is if any of those parts broke. To fix this problem, each blok needs to have a little red led light that turns on when the blok has confirmed that it is broken. Another solution is to have bare minimum requirements to run a very simple OS within the base, and that can give the phone the ability to notify via the screen that a part has gone bad. Although, if the base itself goes bad, then I don’t see any choice other than to have a little led light kick on as soon as it detects a problem within itself. There could possibly be a backup-bare-minimum-requirements blok which might help, but it wouldn’t have access to the screen if the base is out.What are some of your thoughts on this? I think Phonebloks should show it on the screen, like: your Wi-Fi or camera brokes. Hehe. If the processor had some issue, Phonebloks should have an emergency processor block, smaller then the processor block.
Thanks. 🙂 Also, the screen would need to have a little led light to let the owner know that it needs to be replaced (given that the screen is broken in a way that is not immediately obvious. e.g. a crack). Even if all the other parts worked, including the base, a graphical output to the screen would not be an option. By this logic, I’ve concluded that at least the screen and the base need to have their own little “I’m broken” led light. If these precautions have been designed into the phone correctly, then there should hardly ever be a need for a separate device designed to test each blok. (I’m imagining something like a base into which components can be inserted to test their functionality.) If a situation arises in which some component is broken, but the phone has been rendered into a state such that it has no ability to inform the owner as to which one it is, such a blok tester will be necessary. Although, the need for such a device must be seriously avoided to maintain the advantage of modularity.
PianoMastR64 wrote: Thanks. 🙂 Also, the screen would need to have a little led light to let the owner know that it needs to be replaced (given that the screen is broken in a way that is not immediately obvious. e.g. a crack). Even if all the other parts worked, including the base, a graphical output to the screen would not be an option. By this logic, I’ve concluded that at least the screen and the base need to have their own little “I’m broken” led light. If these precautions have been designed into the phone correctly, then there should hardly ever be a need for a separate device designed to test each blok. (I’m imagining something like a base into which components can be inserted to test their functionality.) If a situation arises in which some component is broken, but the phone has been rendered into a state such that it has no ability to inform the owner as to which one it is, such a blok tester will be necessary. Although, the need for such a device must be seriously avoided to maintain the advantage of modularity. Yeah.
HUELANDER wrote: I think Phonebloks should show it on the screen, like: your Wi-Fi or camera brokes. Hehe. If the processor had some issue, Phonebloks should have an emergency processor block, smaller then the processor block. That’s sort of what I was going for with the idea of the base itself having the minimum requirements (cpu, ram, …) to allow the phone to continue functionality enough to graphically notify the user of a specific essential component that had gone bad. I think a backup blok for each essential component would get in the way in the face of normal/ideal functionality, unless the backup components were all combined into one simple blok. What do you think? Should the minimum required backup components reside within the base or in a detachable blok?
PianoMastR64 wrote: That’s sort of what I was going for with the idea of the base itself having the minimum requirements (cpu, ram, …) to allow the phone to continue functionality enough to graphically notify the user of a specific essential component that had gone bad. I think a backup blok for each essential component would get in the way in the face of normal/ideal functionality, unless the backup components were all combined into one simple blok. What do you think? Should the minimum required backup components reside within the base or in a detachable blok? I’m doing a special topic for it right now!
You must be logged in to reply to this topic.
