There is NO way this update was tested. Nothing hardly works

[emva]

Hi

I now proclaim myself to be the “forum police”… Please slow down or stop… This is not helping anyone.

[deprecated]

Firstly if you want to have your ego in the spot light, please do it somewhere else.

This has nothing to do with ego. It is a statement of fact. If that fact offends you, then that’s your issue. Not mine.

It is not your business what I have done and if you are smart enough you could find out yourself.

Right. Given that “logic”, it’s none of your business what I type in this thread. Am I getting that right?

I also do not ask for your workarounds.

So, essentially exactly what I said earlier? “I don’t want a solution, I want to complain about the problem!”

Odd.

I personally ask for better QA and more stability.

You don’t know how this works at all, do you?

Secondly Jolla is a company and the community has nothing to do with the company … your statement is false.

… What? This is what this community is for.

It is not the community project we are talking about here - it is the official releases Jolla makes as a company.

… Which are discussed in this community, up to and including real and actual bug reports. Astonishing.

Funny, that no one asked for your opinion how you persive the world.

Funny, this has absolutely nothing to do with opinions, which was my point.

Also interesting how you are insulting people by stating “(admittedly limited) experience”

That wasn’t an insult. It was a statement of fact. The supporting evidence is in this very thread.

You are lucky you are not around.

… I’m lucky I’m not around what? What does that even mean? Inferring from context, that sounds like a threat. Are you so upset with reality that you’re threatening people now? How… quaint.

Also very interesting that you call workaround a solution.

A workaround literally is a solution.

You are insulting again!

That wasn’t an insult.

Please give us a break! And thank you in advance for not answering me.

A break from what, exactly? This is becoming cyclic.

I am quite sure they can do better. If they could remove all bugs from Harmattan and we know what “all” means, then they really can do it, but they do not want to do it, so it is getting worse and worse with each release.

Hint: this isn’t Harmattan. Remember, Harmattan was a Nokia product. Nokia had substantially more staffing, more funding, and more commercial presence. Moreover, your statement is qualitatively wrong.

We just let our frustration out.

Bug reports aren’t the place for venting or vitriol, which is the point I have been making – repeatedly – since I became involved in this thread.

I do not see why I should have two devices and I should spent time debugging stuff.

Then… don’t?

It is the same disaster as with linux desktops - it is the same mentality - perhaps it is the same people.

What are you on about now? What does Linux on the desktop have to do with Sailfish, Jolla, or anything in this thread?

You are missing the point again.

No, I’m quite literally not.

It is not about the bug reports or workarounds. It is about the number of issues that are coming with each new release.

… Which are addressed through actual bug reports. Why is this a difficult concept to grasp?

But to inform you, yes, I reported the issues. Some of them were solved, some not. The IntexAqua was not fixed.

Is that ancient thing still supported? I thought it went extinct with the JP1.

Missing the point again. It is the many new issues.

Yeah, the many new issues that are so prevalent that every Sailfish user is experiencing them with every device, on every revision. It’s completely unusable!

Do you see how hyperbolic (and pointless) that sounds?

Yes, I do, as long as I have relation with Jolla, I definitely do.

Hilariously, you’re missing the point.

Yes, there is a point, but I am not sure you are getting this point. The point is : Jolla and the software are great, but the QA is bad and recently it comes too often to buggy releases. It is getting annoying!

The hyperbole is what’s getting annoying, in earnest. Passive aggressive “bug reports”, exaggeration and ridiculous expectations? Good idea!

I hope you get it and leave your irrelevant stories. Again thank you in advance!

… What?

In all seriousness, why don’t you go back to Android or something better suited to your expectations?

[808]

I have what ever the appoved sony phone is… has Jolla HQ stated they are no longer supporting the phone…

Why.is the x2A a problem…can you share?

[deprecated]

I think his point was that there is no “X2A”.

[Steve_Everett]

I’d think we’d all be grateful if both of you (808 and Deprecated) would just stop now. This thread is now just a schoolyard slanging match, long since devoid of any positive contribution

[Levone1]

Sorry - I was just being light; I thought a little humor might help… Anyway, my 2 cents here is that nobody on this forum has a hard time with you pointing out that there are problems, (even many problems). Mist of us have known it for years… There’s just a way to communicate… Almost every forum you will ever visit, (except that it’s maybe devoted to anarchy), will have a “Read This Before Posting”-type of post that states general guidelines of what’s acceptable in the content of a post, (FAQ - Sailfish OS Forum). There’s a general agreement here that your initial post, and several others since, have not held to that standard.

If you just change the title and contents of the original post, and simply lay out the specifics of what’s not working, without the strong attitude or insults, all of these same people will not only be able to help with most of it, but will actually agree and appreciate your points, and even hit the “like” button …

[WT.Sane]

Mine is working yours apparently not.
Must be the OS!

[WT.Sane]

Watch out! We are right behind you.

[808]

lets just let it be… it’s not worth it. The devs have plenty to work with in regards to the bugs and issues reported by multiple people in this report thread. he or she is not important as it relates to who we report issues to.

Hopefully the next release will be better.
Thanks everyone.

[Kea]

Indeed, it must be, for it happened after the latest update (4.3). This update was/is full of bugs.

[808]

Adding to this bug report…I wanted make sure I could reproduce the issue.

If a sms message comes in while thethe smssms app is up and you close it. I will not open a again and just spins. At that point other apps will not load. In this case the clock app will not start.

The window tiles will just spin and after about 10 or so seconds it just goes away. Most apps stop loading. The browser will still load when The phone is in this state. As an example I took another screen shot whike tapping this message out and native messaging app will not load. only why to fix this seems to be rebooing the phone.

[emva]

You can also use Sailfish Utilities to restart the window manager./ user interface.

[808]

I did…it reset the UI. Also when it happened again it sort of fixed itself after about an hour ago… I guessing this is a know thing since the utility actually fixes it?

[deprecated]

Just tried to reproduce this one on three SFOS devices.

Couldn’t. How odd.

[peterleinchen]

And I have seen this earlier on a fresh reset (so vanilla state) testing device after playing/installing/uninstalling a new build of defender. At some point the app could not be started anymore from the icon.

So, could. How even!

_
@808
could you start the app with opening terminal and type e.g.

jolla-clock

[Steve_Everett]

I have seen this too occasionally. Its almost as something in the OS has ‘locked’ a particular resource (enough RAM perhaps?) that all apps need when they open, so any newly opened app just has to wait until that resource is released, which it never is. For me, restarting the Home Screen using the Sailfish utilities will fix things. I just put it down to one of Sailfish’s many quirks and never bothered to report it since it happens infrequently.

[deloptes]

I reported issue with hciattach beginning of the year (4.0 or 3.4).
What they did for 4.3 is to make it even worse in the hope somehow it fixes itself …
It is simply disappointing. I will now bisect and compile backword versions to see who broke things

Dec 11 08:53:11 XperiaX bluetooth_rfkill_event[699]: main(bluetooth_rfkill_event.c:1241): BT power driver unblocked
Dec 11 08:53:12 XperiaX bluetooth_rfkill_event[699]: free_hci(bluetooth_rfkill_event.c:906): killing hciattach failed
Dec 11 08:53:12 XperiaX bluetooth_rfkill_event[699]: attach_hci(bluetooth_rfkill_event.c:923): executing hciattach  -d -m /dev/ttyHS0 bcm43xx 3000000 flow sleep 9c:5c:f9:b2:f8:e1 failed
Dec 11 08:53:12 XperiaX bluetooth_rfkill_event[699]: attach_hci(bluetooth_rfkill_event.c:926): Failed to execute hciattach  -d -m /dev/ttyHS0 bcm43xx 3000000 flow sleep 9c:5c:f9:b2:f8:e1, exiting
Dec 11 08:53:12 XperiaX systemd[1]: bluetooth-rfkill-event.service: Main process exited, code=exited, status=1/FAILURE
Dec 11 08:53:12 XperiaX bluetoothd[718]: Failed to set mode: Failed (0x03)
Dec 11 08:53:12 XperiaX bluetoothd[718]: bluetoothd[718]: Failed to set mode: Failed (0x03)
Dec 11 08:53:12 XperiaX bluetoothd[718]: bluetoothd[718]: Endpoint unregistered: sender=:1.89 path=/MediaEndpoint/A2DPSink/sbc
Dec 11 08:53:12 XperiaX bluetoothd[718]: bluetoothd[718]: Endpoint unregistered: sender=:1.89 path=/MediaEndpoint/A2DPSource/sbc
Dec 11 08:53:12 XperiaX bluetoothd[718]: Endpoint unregistered: sender=:1.89 path=/MediaEndpoint/A2DPSink/sbc
Dec 11 08:53:12 XperiaX systemd[1]: bluetooth-rfkill-event.service: Failed with result 'exit-code'.
Dec 11 08:53:12 XperiaX bluetoothd[718]: Endpoint unregistered: sender=:1.89 path=/MediaEndpoint/A2DPSource/sbc
Dec 11 08:53:12 XperiaX connmand[2595]: Bluetooth device /org/bluez/hci0 not enabled Failed
Dec 11 08:53:12 XperiaX kernel: msm_hs_shutdown(): removing extra vote
Dec 11 08:53:12 XperiaX kernel: msm_hs_shutdown: Client vote on, forcing to 0
Dec 11 08:53:12 XperiaX [2913]: [D] unknown:0 - "void Buteo::TransportTracker::onBtInterfacesRemoved(const QDBusObjectPath&, QStringList)" :Entry
Dec 11 08:53:12 XperiaX [2913]: [D] unknown:0 - "void Buteo::TransportTracker::onBtInterfacesRemoved(const QDBusObjectPath&, QStringList)" :Exit, execution time: 0 ms
Dec 11 08:53:12 XperiaX [2913]: [D] unknown:0 - "void Buteo::TransportTracker::onBtInterfacesRemoved(const QDBusObjectPath&, QStringList)" :Entry
Dec 11 08:53:12 XperiaX [2913]: [D] unknown:0 - "void Buteo::TransportTracker::onBtInterfacesRemoved(const QDBusObjectPath&, QStringList)" :Exit, execution time: 0 ms
Dec 11 08:53:12 XperiaX systemd[1]: bluetooth.target: Unit not needed anymore. Stopping.
Dec 11 08:53:12 XperiaX systemd[1]: Stopped target Bluetooth.
Dec 11 08:53:13 XperiaX systemd[1]: bluetooth-rfkill-event.service: Service hold-off time over, scheduling restart.
Dec 11 08:53:13 XperiaX systemd[1]: bluetooth-rfkill-event.service: Scheduled restart job, restart counter is at 1.
Dec 11 08:53:13 XperiaX systemd[1]: Stopped Bluetooth rfkill event daemon.
Dec 11 08:53:13 XperiaX systemd[1]: Started Bluetooth rfkill event daemon.
Dec 11 08:53:13 XperiaX bluetooth_rfkill_event[4888]: main(bluetooth_rfkill_event.c:1146): Starting bluetooth_rfkill_event
Dec 11 08:53:13 XperiaX bluetooth_rfkill_event[4888]: main(bluetooth_rfkill_event.c:1241): BT power driver unblocked
Dec 11 08:53:13 XperiaX bluetooth_rfkill_event[4888]: free_hci(bluetooth_rfkill_event.c:908): No hciattach process to be found
Dec 11 08:53:13 XperiaX bluetooth_rfkill_event[4888]: attach_hci(bluetooth_rfkill_event.c:923): executing hciattach  -d -m /dev/ttyHS0 bcm43xx 3000000 flow sleep 9c:5c:f9:b2:f8:e1 failed
Dec 11 08:53:13 XperiaX bluetooth_rfkill_event[4888]: attach_hci(bluetooth_rfkill_event.c:926): Failed to execute hciattach  -d -m /dev/ttyHS0 bcm43xx 3000000 flow sleep 9c:5c:f9:b2:f8:e1, exiting
Dec 11 08:53:13 XperiaX systemd[1]: bluetooth-rfkill-event.service: Main process exited, code=exited, status=1/FAILURE
Dec 11 08:53:13 XperiaX systemd[1]: bluetooth-rfkill-event.service: Failed with result 'exit-code'.
Dec 11 08:53:14 XperiaX systemd[1]: bluetooth-rfkill-event.service: Service hold-off time over, scheduling restart.
Dec 11 08:53:14 XperiaX systemd[1]: bluetooth-rfkill-event.service: Scheduled restart job, restart counter is at 2.
Dec 11 08:53:14 XperiaX systemd[1]: Stopped Bluetooth rfkill event daemon.
Dec 11 08:53:14 XperiaX systemd[1]: Started Bluetooth rfkill event daemon.
Dec 11 08:53:14 XperiaX bluetooth_rfkill_event[4892]: main(bluetooth_rfkill_event.c:1146): Starting bluetooth_rfkill_event
Dec 11 08:53:14 XperiaX bluetooth_rfkill_event[4892]: main(bluetooth_rfkill_event.c:1241): BT power driver unblocked
Dec 11 08:53:15 XperiaX bluetooth_rfkill_event[4892]: free_hci(bluetooth_rfkill_event.c:908): No hciattach process to be found
Dec 11 08:53:16 XperiaX bluetooth_rfkill_event[4892]: attach_hci(bluetooth_rfkill_event.c:923): executing hciattach  -d -m /dev/ttyHS0 bcm43xx 3000000 flow sleep 9c:5c:f9:b2:f8:e1 failed
Dec 11 08:53:16 XperiaX bluetooth_rfkill_event[4892]: attach_hci(bluetooth_rfkill_event.c:926): Failed to execute hciattach  -d -m /dev/ttyHS0 bcm43xx 3000000 flow sleep 9c:5c:f9:b2:f8:e1, exiting
Dec 11 08:53:16 XperiaX systemd[1]: bluetooth-rfkill-event.service: Main process exited, code=exited, status=1/FAILURE
Dec 11 08:53:16 XperiaX systemd[1]: bluetooth-rfkill-event.service: Failed with result 'exit-code'.
Dec 11 08:53:17 XperiaX systemd[1]: bluetooth-rfkill-event.service: Service hold-off time over, scheduling restart.
Dec 11 08:53:17 XperiaX systemd[1]: bluetooth-rfkill-event.service: Scheduled restart job, restart counter is at 3.
Dec 11 08:53:17 XperiaX systemd[1]: Stopped Bluetooth rfkill event daemon.
Dec 11 08:53:17 XperiaX systemd[1]: Started Bluetooth rfkill event daemon.
Dec 11 08:53:17 XperiaX bluetooth_rfkill_event[4896]: main(bluetooth_rfkill_event.c:1146): Starting bluetooth_rfkill_event
Dec 11 08:53:17 XperiaX bluetooth_rfkill_event[4896]: main(bluetooth_rfkill_event.c:1241): BT power driver unblocked
Dec 11 08:53:17 XperiaX bluetooth_rfkill_event[4896]: free_hci(bluetooth_rfkill_event.c:908): No hciattach process to be found
Dec 11 08:53:17 XperiaX bluetooth_rfkill_event[4896]: attach_hci(bluetooth_rfkill_event.c:923): executing hciattach  -d -m /dev/ttyHS0 bcm43xx 3000000 flow sleep 9c:5c:f9:b2:f8:e1 failed
Dec 11 08:53:17 XperiaX bluetooth_rfkill_event[4896]: attach_hci(bluetooth_rfkill_event.c:926): Failed to execute hciattach  -d -m /dev/ttyHS0 bcm43xx 3000000 flow sleep 9c:5c:f9:b2:f8:e1, exiting
Dec 11 08:53:17 XperiaX systemd[1]: bluetooth-rfkill-event.service: Main process exited, code=exited, status=1/FAILURE
Dec 11 08:53:17 XperiaX systemd[1]: bluetooth-rfkill-event.service: Failed with result 'exit-code'.
Dec 11 08:53:18 XperiaX systemd[1]: bluetooth-rfkill-event.service: Service hold-off time over, scheduling restart.
Dec 11 08:53:18 XperiaX systemd[1]: bluetooth-rfkill-event.service: Start request repeated too quickly.
Dec 11 08:53:18 XperiaX systemd[1]: bluetooth-rfkill-event.service: Failed with result 'exit-code'.
Dec 11 08:53:21 XperiaX kernel: msm_hs_request_clock_off(): ioctl count -ve, client check voting
Dec 11 08:53:21 XperiaX kernel: Bluetooth: hsuart_power: Turning UART clock off failed (-1)
Dec 11 08:54:11 XperiaX systemd[1]: Started Bluetooth rfkill event daemon.
Dec 11 08:54:11 XperiaX bluetooth_rfkill_event[4906]: main(bluetooth_rfkill_event.c:1146): Starting bluetooth_rfkill_event
Dec 11 08:54:11 XperiaX bluetooth_rfkill_event[4906]: main(bluetooth_rfkill_event.c:1241): BT power driver unblocked
Dec 11 08:54:11 XperiaX bluetooth_rfkill_event[4906]: free_hci(bluetooth_rfkill_event.c:908): No hciattach process to be found
Dec 11 08:54:12 XperiaX bluetooth_rfkill_event[4906]: attach_hci(bluetooth_rfkill_event.c:923): executing hciattach  -d -m /dev/ttyHS0 bcm43xx 3000000 flow sleep 9c:5c:f9:b2:f8:e1 failed
Dec 11 08:54:12 XperiaX bluetooth_rfkill_event[4906]: attach_hci(bluetooth_rfkill_event.c:926): Failed to execute hciattach  -d -m /dev/ttyHS0 bcm43xx 3000000 flow sleep 9c:5c:f9:b2:f8:e1, exiting
Dec 11 08:54:12 XperiaX systemd[1]: bluetooth-rfkill-event.service: Main process exited, code=exited, status=1/FAILURE
Dec 11 08:54:12 XperiaX systemd[1]: bluetooth-rfkill-event.service: Failed with result 'exit-code'.
Dec 11 08:54:13 XperiaX systemd[1]: bluetooth-rfkill-event.service: Service hold-off time over, scheduling restart.
Dec 11 08:54:13 XperiaX systemd[1]: bluetooth-rfkill-event.service: Start request repeated too quickly.
Dec 11 08:54:13 XperiaX systemd[1]: bluetooth-rfkill-event.service: Failed with result 'exit-code'.

[deloptes]

Although bluetooth-rfkill-event is creepy I traced the issue with BT to bluez5.

Downgraded bluez5 to “HEAD is now at cf4572ddd Merge branch ‘jb48791’ into ‘master’”
and everything is working fine.

@deprecated - I guess you helped testing the software especially bluez5 after this commit

BR

[kuronoyurei]

I got exactly the same issue since the last update. But wasn’t able to now exactly what initiate this issue.
Restarting the UI, using the Utilities app is useless. Only a reboot seems to resolve troubles as you confirm.

[pawel.spoon]

the people have wrong expectations and are used to get everything for free.
so when they do pay no 50 bucks they expect something special, something golden …

btw. a similar statement is also on ubports webpage … and ubtouch is not as far as sfos

when i bought jolla1 i did expect a brick and was positively surprised.