Unfortunately I’m at the moment quite busy so I can not really test much. Anyway, I want to correct my statement regarding the battery life. It is not outstanding, it’s unbelievable.
The last time the device was charged was before I flashed Sailfish. Since then, I installed a good portion of apps. Did a little bit of browsing and tests. Did 5 or 6 reboots (at least 4 of them unintentionally, alas). SIM Card was just in the phone for around half a day, but it was connected to WiFi all the time and left it for some hours on my desk with GPS switched on. Most time anyway the device lay just on my desk.
Guess what,t it still runs and shows 42% battery power left. 
2 Likes
Don’t worry, that battery life will reduce when you start using it actively. 
That’s out of question. Anyway I never had a sailfish device which I could just left in the corner and pick it up after 4 days with still a lot of capacity left. Not even the J1.
I think I will wait still a bit until it gets my daily driver. While I had no unexpected reboots anymore, the problem with the not reacting touchscreen after some unlocking events seems to somehow settle. On top of the long wake up time this is somehow a bit too irritating. So I will wait for the next flashable image and will then do a full reflash.
If you guys need further things from me for debugging let me know. I then need some instructions, though.
I will play further with the device anyway.
Interesting thing: I used the browser now much more for testing reasons. I was astonished that I NEVER had any browser crash like I do with all of my other devices (Xperia 10 II, III and Volla Quintus) have you tweaked somehow the browser, or is that coincidence? And Yes, browsing the net eats some battery, but still to a VERY acceptable extend.
1 Like
it is weird that screen start takes long time and I am not sure what we can do about it. in my case, I have FP enabled and double-tap enabled. whether this makes it faster or I don’t get that troubled - no idea.
re browser: more RAM helps. angelfish runs on that too, but then you need to setup qt6 repos pointing to piggz OBS
1 Like
This is not what I see on my 5 iv. Do you have USB telnet access to get logs when this screen lag happens? Or even ssh over wifi. Just journalctl -f and use some paste service.
For the reboots, it would be interesting if /sys/fs/pstore contains some console ramoops logs. Again, ssh or telnet needed
1 Like
Are the kernelmodules that are needed by AAS already included in your port? Do you discuss with Jolla if there could be official AAS-Support for the phones once the ports are ready?
(I’m sorry, if this is a disturbing question at this point - but I’m highly interested in your port. 10IV is not getting ready, J2 still a long time to wait, and I need a new Daily-Driver and your port and the 1IV/5IVs are looking really promising)
1 Like
This is when I wakeup the screen with it’s delayed wakeup:
Unfortunately not with a freeze of the touch screen at the moment. I’ll try to catch such a situation as well.
/sys/fs/pstore is empty.
But there were no unexpected reboots anymore, So I think we can ignore this issue, that was two times right after flashing and since then it did not happen anymore.
The Volla Quintus has 8GB of RAM. Same amount as the Xperia 5IV. On https://www.stuttgarter-zeitung.de my other devices are crashing very often. Sofar the 5IV has no problems with the website.
You mean double tap on the screen? You acivated it via mce tools?
Ok here the screen didn’t react anymore or at least not to that extend I want to. It still shows the hinting row, but I’m not able to do further actions, like showing the app drawer…
yes, via mce tools
re logs: don’t see much in them. do you happen to know when you pressed a button (time in seconds precision)? from your description I don’t really follow what’s the problem. is the screen not turning on? or it lids up, but you cannot unlock? or it is unlocked, but you cannot enter apps drawer?
there are no discussions with Jolla behind the doors (haven’t looked nor stumbled on those). whether we have all modules enabled for it, no idea. as for port being ready - that depends on definition. already now, for me, its a daily driver
1 Like
First log:
I pressed the power button at:
Dez 08 16:36:59 Xperia5IV kernel: i2c_read: err wakeup of wq
Here the screen showed up and I then unlocked via FP:
Dez 08 16:37:02 Xperia5IV lipstick[8633]: [W] unknown:122 - file:///usr/share/lipstick-jolla-home-qt5/lockscreen/LockItem.qml:122:5: QML ContrastBackground: Binding loop detected for property "screenY"
So it is around 3 seconds from pressing the power button to screen showing up.
Regarding the second:
I have no clue, when I did what. I did for sure 30 lock and unlock actions to trigger the problem.
The problem is, that the Screen shows up. I unlock it. But then I am not able to make any actions. the only thing that worked is when I double tapped the screen, the hinting row showed up. It’s not possible to swipe or to do anything else. If it helps, I can make the next time a video of the problem.
Re delay: please enable double tap to wake and see if it goes away. otherwise we have seen it too.
With the screen only other issue is Xperia 1 IV Doubled-input Tochscreen · Issue #60 · sailfishos-sony-nagara/main · GitHub . but I couldn’t find the way to reproduce it nor fix it
Ok, I will have a look if it goes away with double-tap.
Yes, looking at the Video, this looks just like the problem I have.
Sad, it wasn’t possible to nail any culprit.
So, we have 2 issues:
-
slow start of the screen. should be “cured” with enabling double tap
-
weird touchscreen issue on start. try to see if it is the same double touch by trying to switch to pin entry mode using non-registered finger and see if you have the same effect as in the issue. note that there was a workaround towards the end of the thread
2 Likes
I can confirm, that double tap cures this problem.
Regarding the workaround with volume changing I will see the next time if that works.
1 Like
Why doesn’t this surprise me?
1 Like
I think from a technical standpoint the same kernel options needed for Waydroid are used for AppSupport too. However, waydroid currently does not work And if AppSupport would work partially we wouldn’t know how to fix it.
But I do also remember Jolla saying that it will allow AppSupport on ports at one time, can you refresh my memory, was that in a community meeting?
Wow, this means we should enable it by default or something
4 Likes
They said it here in the context of the status of the port for 10iv/10v
and also in september (minute 16:08) rainemak states they are thinking about how to enable AAS to ports.
So, wouldn’t it be great if your port would be the first community port to get AAS officially?
2 Likes
Currently AAS works here, with three limitations - I couldn’t get the camera to not crash on snapping, videos are not playing and mobile internet not working, only wifi. There is a tool that Jolla provides, that lists the missing kernel config options - I can list them here, if you want, there are only listed config options for networking, so probably won’t affect the camera.
1 Like