![]() |
Re: Jolla User Experience Thread
the url field was always only in landscape visible. You should use your Jolla more often or stop discussing it.....
|
Re: Jolla User Experience Thread
Quote:
In landscape the url is located in the actual bar. (I had it just over the bar like in its own Urlbar). Almost never use jolla in landscape. But maybe I did once and the URL field got stuck for me in some way for a while and when I upgrade to U9 the great "bug" was fixed :( So you don't think that all type of users should be free to discuss jolla :eek: Thats why you are sucha good FanBoy :D You can see it in this video at 25 sec into the movie. https://www.youtube.com/watch?v=MWkEnBTMK5I Maybe you should pay more attention to details Morpog :rolleyes: Now, how do we get it back? Is it working in U10? |
Re: Jolla User Experience Thread
Yep now that you mention it, it used to have the url and page name visible while loading the page previously. But I think that function disappeared in summer update, I think it's been a long time since I last noticed it.
|
Re: Jolla User Experience Thread
Ah thats what he talked about, yeah that is gone long too....
Anyways, it seems we get new browser design with update 11, so no use to "fix" the old one.... |
Re: Jolla User Experience Thread
Quote:
what about redesign of some of the gui elements in os to improve usability |
Re: Jolla User Experience Thread
Quote:
|
Re: Jolla User Experience Thread
How to minimize keyboard in jolla terminal app?
|
Re: Jolla User Experience Thread
Quote:
|
Re: Jolla User Experience Thread
Quote:
|
Re: Jolla User Experience Thread
Tapping outside the keyboard bring it back too. Can be turned off from Menu. But you have to turn it on (choosing "Move" or "Fade" options) if you want it again.
|
Re: Jolla User Experience Thread
I just started using the Jolla phone, and am liking it a lot overall. My previous / other phone is an N9. Main findings so far:
- the Jolla is bigger, but feels much lighter than the N9. I did not expect this, pleasant surprise and not something I had read a lot about. - I don't find the corners sharp, they work well in my hand. - Battery life is quite good with modest use. My N9 needs much more frequent charging, perhaps because I've been using it intensely for some years and the battery is showing age. - The user interface feels completely natural. I did not feel any learning curve coming from the N9. - The browser is really fast, combination of 4G and a more modern processor. With some sites I use regularly, pages load almost instantly whereas they took many seconds to load with the N9. - The few Android apps I tested work without flaw. Dislikes: - I had to install/uninstall Android support a few times before the Yandex store worked. But perhaps that was an issue with the Yandex server, not the Jolla, I don't really know. - For some reason I can't install the native Maps application. And I fear that the old N9 Drive is better than what Maps seems to offer, that I will miss. - Not a lot of native apps yet, it seems some interesting ones are not in the official Harbour store. But at least there is the Android app option, so I'm not missing anything. |
Re: Jolla User Experience Thread
Quote:
Quote:
Quote:
Tip : avoid leaving Android support running when not used, stop it using Alien Dalvik Stop or Android runtime stop feature of "Sailfish Utilities" (from Jolla Harbour Store). Android runtime takes more than 100MB of RAM and more battery usage. My Jolla battery without Android runs for 3 days, while just one day with Android. |
Re: Jolla User Experience Thread
Hi,
I hope it's a good thread to ask about uptime and battery life of yours Jolla phones. I'm curious about uptime and battery life of your phone with newest update. Can you write yours ? I how you use your phones . I'm still thinking about buying Jolla phone and battery life is really important for me. |
Re: Jolla User Experience Thread
Hi my uptime is ~ 7 days now, as I remember I haven't rebooted it since the firmware update. It was much longer before :) But the update seems to solved my re-occuring problem with exchange sync stopping (or more like never finishing) that used to be my reason for a reboot...
Battery life is depending on your usage pattern, it can be anything from 6 hours to 3 days. For me it easily last a day with 2 email account syncing, constantly turned on Wifi, mobile net, BT (~ 1 hour/day on BT speaker and ~ 30 min talk time on this), moderate phone usage, some SMS, light web browsing and so. |
Re: Jolla User Experience Thread
,---
| SailfishOS 1.1.1.27 (Vaarainjärvi) (armv7hl) '--- [nemo@Jolla ~]$ uptime 18:55:39 up 10 days, 18:23, 0 users, load average: 1.12, 1.18, 0.97 [nemo@Jolla ~]$ And that only as I needed to boot it to check that a service I installed starts correctly at boot. As a rule I never boot my devices except to update OS. And of course I have zero tolerance of spontaneous restarts. :D I usually charge my device every night, but sometimes every second. In the latter case I usually have about 60% left when I plug it in. |
Re: Jolla User Experience Thread
,---
| SailfishOS 1.1.1.27 (Vaarainjärvi) (armv7hl) '--- [nemo@Dinghy ~]$ uptime 06:06:15 up 10 days, 9:10, 0 users, load average: 0.81, 0.91, 1.03 [nemo@Dinghy ~]$ Your uptime is 9 hours longer than mine despite a deliberate reboot? How did you manage? I restarted on the OS upgrade to 1.1.1.27, which I did on Friday when it was available for just the select few, not on Monday when it was for everyone. EDIT More than 9 hours! Just noticed that you posted 13 hours before me, making your uptime 22 hours longer! |
Re: Jolla User Experience Thread
Quote:
Actually how I managed that is simple. I got 1.1.1.27 on Monday morning 22.Dec, but as it was just a minor update from 1.1.1.26 I did not boot my device, only installed the packages and restarted lipstick. :D Yes, I know you are supposed to use the SW updater instead of manually installing packages but who cares... And I do not like the way it forces a reboot on even minor updates to non-core packages. Besides I really think that you should allow a system to go down only for kernel updates, and there are mechanisms to avoid even that. These are no windoze devices, mind you! :p |
Re: Jolla User Experience Thread
Quote:
|
Re: Jolla User Experience Thread
I don't care if it needs/wants a reboot or not. It's not a damn server..........
|
Re: Jolla User Experience Thread
This morning I made a mistake.
Having a lot of inspiration and only the Jolla at hand I started to reply an email. Then I received a few phone calls, did a web lookup. An hour later I wanted to continue the email: email closed, no draft saved. Work gone. Not pleased. Anyone else noticed such contraproductive behaviour? Haven't had a lot of pleasure out of update 10 yet, on the contrary . |
Re: Jolla User Experience Thread
Quote:
|
Re: Jolla User Experience Thread
Quote:
On a related note, if the OOM killer is going to be so strict, it may be worth pointing out to Jolla which applications aren't saving its state properly before closing. |
Re: Jolla User Experience Thread
Please, no! I don't want apps to save its state; leave that to Android. I want apps to run until I close them. When we start discussion about saving the state of apps we do not intend to close, then we can forget about having any real multitasking, because "why do you want to run the app when it will be restored to the state where you left once you open it again" will become the first argument against complains about the lack of multitasking.
EDIT: That of course doesn't apply to saving message/e-mail drafts on app's exit. And don't give me wrong, saving the state of apps can be a nice thing, but I think that the OOM's behavior must be fixed first. If an app opens on the same page where I (not OOM) closed it, I'll be quite happy. |
Re: Jolla User Experience Thread
Quote:
OOM is another subject and discussed in another thread in more detail - OOM killer must be there and must kill applications, else we go back to the times of Linux kernel 2.2 where the whole OS would crash if you run out of memory. This happens in desktop too, tuning is another matter IMO. |
Re: Jolla User Experience Thread
When you open browser in landscape and and start typing url all the urls are visible under the keyboard. Jolla must fix that. When not in landscape you can atleast click one which is enough much better and basically enough. Scrolling is not the solution here.
suggestions... 1. Search field background could be thinner to get urls closer to top. 2. Too much unused space at the top of keyboard. Remove it or place best matching url right there. |
Re: Jolla User Experience Thread
I find current spontaneous OOM killings too intrusive and erratic. It leaves me guessing if an app crashed or wtf is happening. Lucky there is a way to shut it off, which i did and enjoy update 10 a lot better.
|
Re: Jolla User Experience Thread
Quote:
|
Re: Jolla User Experience Thread
Quote:
|
Re: Jolla User Experience Thread
Quote:
Quote:
|
Re: Jolla User Experience Thread
theres a thread on here that has a patch, messing with a few values stops the OOM killing
|
Re: Jolla User Experience Thread
Quote:
http://talk.maemo.org/showthread.php?t=94358&highlight=oom feel free to post the link if this one was incorrect and happy new year. |
Re: Jolla User Experience Thread
Tigeli says here (TJC) that there are some parameters you can play with:
/sys/module/lowmemorykiller/parameters/adj (0,58,117,529,1000) /sys/module/lowmemorykiller/parameters/minfree (4096,6144,8192,12288,20000) /proc/sys/vm/extra_free_kbytes (16384) He also explains the meaning of these. In the same thread, HansA, a user says: "echo "0,0,0,0,0" > /sys/module/lowmemorykiller/parameters/minfree" OOM appkilling stops. Apps are now never closed! |
Re: Jolla User Experience Thread
Quote:
Sometimes applications become killed ahead of time as the alternative is the system thrashing. The OOM can be less extreme though and it seems to age and get a bit too moody, so that's to be changed, but the main problem is gone. |
Re: Jolla User Experience Thread
@stskeeps
Huh, i need to reconsider this, then!? |
Re: Jolla User Experience Thread
Quote:
Happy new year to all! |
Re: Jolla User Experience Thread
Quote:
|
Re: Jolla User Experience Thread
Quote:
|
Re: Jolla User Experience Thread
I guess it's real threat. With update 8 UI freezed several times completely and AFAIK new Qt 5.2 made that worse in very low memory situations. So, it's reasonable to keep certain amount of memory available for certain thing all the time. However, it's way too aggressive in update 10.
I did this tweak several days ago: http://talk.maemo.org/showpost.php?p...4&postcount=41 It doesn't stay after reboot (so it's good for tinkering :) ) and I don't know which values in Tigelis list would result in similar configuration, but so far my device has been stable and there have been no problems with UI freezing or apps getting killed. Maybe something like this might work with update 11? |
Re: Jolla User Experience Thread
I had a case just yesterday (in a middle of quite an important online chat too) that all my running apps were unexpectedly closed. There were not too many either: a browser with three tabs open and two terminal windows. That's it. Three apps. All killed simultaneously. The phone did not reboot.
Yes, I have had a few missed calls on my N900 due to a sluggish response because of too many apps open but I would rather take that risk than having apps shut on me like that. At least I would know I have only myself to blame. YMMV. |
Re: Jolla User Experience Thread
I also had ALL my apps closed a number of times, random closing of apps including gpodder or such I'm using happens more often. u10 with default values is unusable. It'll be interesting to see the values chosen for u11. It's not easy to choose. Maybe an advanced setting with "profiles" like heavy multitasker and I don't dare miss a phone call would be nice.
|
All times are GMT. The time now is 23:15. |
vBulletin® Version 3.8.8