Is this something foreseen that we can replace the sub-board for i3c ourselves? I will not be likely in need of this soon but I will feel rather sad if there are some TOHs that I cannot use properly (or at all) because I can only use i2c interface…
Jolla, is there any chance that Batch 4 will be affected by this? I’m expecting a definitive answer on this.
According to frengel’s instructions on iFixIt, replacing the sub-board shouldn’t be too difficult. (EDIT: it is a screw-and-plug job. Steps 9, 10 and 11 may not be needed when only replacing the I2C/I3C sub-board; i.e. you have to
- remove the battery (steps 1 to 5; unscrew and unplug)
- remove the mid-frame (steps 6 to 8; unscrew und removal of one sticker; pay attention to camera(s); they may stick to the mid-frame)
- replace I3C board (step 12; unscrew, unplug and replace)
- reassemble)
Therefore, I would be happy to eventually receive a replacement board that I can mount myself. This would be the easiest solution for Jolla.
Same here, of course I want to future proof my Jolla even if the replacement board wouldn’t be necessary right now. Maybe there could be an email to all who have the defective version of the board when the replacements are available and it would have two options; one to send the phone for repair and other to order the replacement board to be delivered to the user if they are comfortable with changing it themselves. And then of course if you don’t want to get the board replaced because sending the phone away for repair would take too long and you are not willing to do the replacement by yourself, just ignore the email notification and continue using the phone as is
You are expecting a definitive answer? Your tone seems somehow rude for me, particularly that this problem will be solvable afterwards with a new subboard.
Let me quote:
“Thus, the TOH interface itself works but only on I2C mode for now and a revised sub-board will be applied in future batches from August onwards” and as
“Batch #3 we will target to start shipping by end of August.”, batch #4 should not be affected by this bug, as far as they can say now. Maybe something goes wrong, but how should they give you now your “expected” answer?
This question was not directed at you. I read the article as well, and we were discussing the issue in general. My tone was not rude. If asking a question is considered rude, then I’m sorry, but I am a customer, and I have every right to ask about something that has not been clearly stated.
First of all, thank you in advance. The current situation does not bother me because I am in batch 4, but if I had been in one of the first three batches, I would have found it incredibly upsetting. Let me explain why: I am planning to travel abroad to buy this product because my country does not allow it to be shipped here.
Even if they say they will make up for the issue, unfortunately, once I receive the product, I will not easily be able to order anything else from them and have it shipped to my country, nor will I be able to send the phone back to them and wait for them to revise the I3C hardware. Under the conditions in my country, doing that would mean travelling abroad twice, which would also mean spending a considerable amount of money.
So thank you for your prejudice as well.
Do you really think I was being that rude just by asking this? I don’t think so. Thank you, and have a nice day.
That’s a strong wording for something someone might not even need. And wrong anyway as I2C works so “limited” is more correct.
I even believe that for many of the TOH I2C mode will suffice and they won’t need I3C mode.
You get a free orange cover + free shipment of the white one, once it’s ready.
That’s handled as good as one can handle a problem like this, in my opinion.
Fair. But I’m sure they will provide a possibility to have this sorted out, in case you need the full functionality. That being said, most I3C stuff is backward compatible and can operate in I2C legacy mode, so an I3C TOH will often still function on the buggy boards. Just slower and without some more fancy features. That’s why they says most use cases can still be prototyped on I2C. For most people the practical impact is pretty small, I’d say.
I feel like they are pretty transparent with the shipping timeline as it’s currently planned, and they are more or less within the limits of what they initially communicated? Or did I miss something?
As someone who had some similar experience with a big manufacturer: They don’t handle those situations any better. And they don’t even provide some insights in their community forums. If they even have a forum to start with.
I agree to disagree, then. Especially regarding the white backcover. You get your complete product, maybe even more (free orange backcover). Just not in one shipment.
You do you
I’m simply disappointed, but not surprised. Engineers usually do not do well outside of their field, especially when it comes to expectations management and communication.
Sounds to me like you were planning to start manufacturing very demanding TOHs immediately and also can’t afford to have a different color TOH for free before white is ready.
It’s understandable, so maybe the phone is not for you.
If I can offer a solution it would be to offer it for sale at MSRP here in the forum. I bet there will be hundreds of people that can’t care less about these things but want to get the device faster and off of your hands.
That was my point towards @pentti ![]()
I surely will, once I get it EVENTUALLY delivered!!1oneone
You don’t get my point it seems.
I get your point, it’s just that whatever could be huge issue for you might be completely irrelevant to me.
That’s why I suggested what I thought could be a solution to something you described as catastrophic from your perspective.
What a real big, professional company would do is silently change their page from i3c to i2c and then gaslight everyone it was always meant to be i2c.
(sorry, I watched too many Louis Rossmann videos
)
This is the way
And remove all WaybackMachine snapshots.
Regarding the I3C. Is there a chance they might not send the mobile to me just yet? In other words, only dispatch it once the sub-board is available and has been fitted.
Regardless of whether I need the feature or not.
For me, the open communication of Jolla rather gives reason to trust Jolla.
Apparently they are committed to quality. Otherwise, they could have ignored reduced functionality of the I3C interface and quality deficiencies of the white TOHs until some users complain (not a good approach). From my perspective, they are doing it the right way.
It’s easy for you. Just don’t trust, don’t complain, don’t buy ![]()
Problem is solved for you.
@SomeThingElse
Just a curious question: Are you such a negative and pessimistic and even prejudicial person in general or is there any strategy behind the way you argue?
Unfortunately, the nature of your comments leads me to such thoughts
.
The way how and why Jolla’s communication is as it is has been explained numerous times. Nonetheless, you bring up the same or at least similar kinds of concerns and critisim again and again.
Wouldn’t it be much more relaxed to be patient like most of the community, read the already existing threads and judge or even criticise only after things came out wrong?