![]() |
Re: Jolla User Experience Thread
Quote:
Browsing FF:FF:FF:00:00:00 ... Service Name: Nokia OBEX PC Suite Services Service RecHandle: 0x10000 Service Class ID List: UUID 128: 00005005-0000-1000-8000-0002ee000001 Protocol Descriptor List: "L2CAP" (0x0100) "RFCOMM" (0x0003) Channel: 24 "OBEX" (0x0008) Profile Descriptor List: "" (0x00005005-0000-1000-8000-0002ee000001) Version: 0x0100 Service Name: Object Push server Service RecHandle: 0x10001 Service Class ID List: "OBEX Object Push" (0x1105) Protocol Descriptor List: "L2CAP" (0x0100) "RFCOMM" (0x0003) Channel: 9 "OBEX" (0x0008) Profile Descriptor List: "OBEX Object Push" (0x1105) Version: 0x0100 Service Name: Headset Audio Gateway Service RecHandle: 0x10002 Service Class ID List: "Headset Audio Gateway" (0x1112) "Generic Audio" (0x1203) Protocol Descriptor List: "L2CAP" (0x0100) "RFCOMM" (0x0003) Channel: 12 Profile Descriptor List: "Headset" (0x1108) Version: 0x0102 Service Name: Hands-Free Audio Gateway Service RecHandle: 0x10003 Service Class ID List: "Handsfree Audio Gateway" (0x111f) "Generic Audio" (0x1203) Protocol Descriptor List: "L2CAP" (0x0100) "RFCOMM" (0x0003) Channel: 13 Profile Descriptor List: "Handsfree" (0x111e) Version: 0x0105 Service Name: AVRCP TG Service RecHandle: 0x10004 Service Class ID List: "AV Remote Target" (0x110c) Protocol Descriptor List: "L2CAP" (0x0100) PSM: 23 "AVCTP" (0x0017) uint16: 0x103 Profile Descriptor List: "AV Remote" (0x110e) Version: 0x0100 Service Name: Audio Source Service RecHandle: 0x10005 Service Class ID List: "Audio Source" (0x110a) Protocol Descriptor List: "L2CAP" (0x0100) PSM: 25 "AVDTP" (0x0019) uint16: 0x102 Profile Descriptor List: "Advanced Audio" (0x110d) Version: 0x0102 Service Name: SyncML Client Service RecHandle: 0x10006 Service Class ID List: UUID 128: 00000002-0000-1000-8000-0002ee000002 Protocol Descriptor List: "L2CAP" (0x0100) "RFCOMM" (0x0003) Channel: 25 "OBEX" (0x0008) Profile Descriptor List: "" (0x00000002-0000-1000-8000-0002ee000002) Version: 0x0100 Service Name: SyncML Server Service RecHandle: 0x10007 Service Class ID List: UUID 128: 00000001-0000-1000-8000-0002ee000001 Protocol Descriptor List: "L2CAP" (0x0100) "RFCOMM" (0x0003) Channel: 26 "OBEX" (0x0008) Profile Descriptor List: "" (0x00000001-0000-1000-8000-0002ee000001) Version: 0x0100 |
Re: Jolla User Experience Thread
Just to inform anyone that uses outlook.com
Jolla has fixed the bug which didn't let you sync anything from outlook.com with Exchange. The update will be released soon. |
Re: Jolla User Experience Thread
Question about battery life:
I found I could boost my N9's battery life by installing profilematic and setting a rule that forces 2G instead of 3G when I'm on wifi. So my questions to Jolla users are: Is there a setting like this in SailfishOS? Is profilematic already in the Jolla store? Plus, bonus question: Does anyone know if profilematic is being ported at all? |
Re: Jolla User Experience Thread
Quote:
2. Not at the moment 3. Hopefully :) |
Re: Jolla User Experience Thread
Quote:
|
Re: Jolla User Experience Thread
The complaints over Android support are here... why? It's a gateway into non-fan territory that currently have Android apps that are there and not yet native/ported over to Sailfish and don't want some knockoff variant of Instagram that'll be locked out before the next update.
You don't want it, don't install it. It's that simple. But for them not to have it, that would have been a crucial mistake. Don't have Netflix? Sideload it. Don't have Autodesk Sketchbook Pro? Sideload it. Don't have Firefox? Sideload it. Don't want to sideload anything? Don't use it. The reviews... so far shows me how much the reviewers are so used to Android and iOS and aren't willing to think in other terms. If the N9 was more widespread distributed and/or BB10 was actually popular, a lot of the UI/UX complaints would have probably become constructive criticisms. But the N9 didn't get worldwide distribution, the reviewers are reluctant to switch from their "preciousssssss" and we're having to figure out a way to educate folks that don't want to learn/listen/think independently. Uphill battle? Yep. Being angry about it? Useless. Correcting where it needs to be corrected? I'm down for that. |
Re: Jolla User Experience Thread
I'm also a bit afraid of the whole Android thing. It's great that it's compatible, but I suppose official apps like Facebook and Twitter will never get a proper Sailfish version since they are already available for Jolla as Android apps... And they will probably never run comparable to a real Android device.
|
Re: Jolla User Experience Thread
Did someone disassemled the jolla?
Would like to see HW pictures :D regards |
Re: Jolla User Experience Thread
|
Re: Jolla User Experience Thread
Quote:
http://i2.photobucket.com/albums/y16...ps820cf690.png Avatar full screen in call http://i2.photobucket.com/albums/y16...psada39f67.png |
Quote:
|
I don't think, the android support is that bad for Jolla.
See that from the other side: Jolla needs customers. Without at least standard apps like WhatsApp, Twitter, Facebook and so on, nobody will buy a Jolla. I think that was a big point on the N9, too. With a growing user base, the need for good apps will grow also. But only native sailfish apps can be qualitatively good on Jolla and the developers will probably start to port their apps to sailfish os, if there are enough users. So, at first Jolla needs many apps to have a chance to get many customers and then the market will regulate itself. That is how I see this and I think this is the right decision of Jolla. I hope it is clear what i meant, sorry for my bad English :-) |
Re: Jolla User Experience Thread
Quote:
|
Re: Jolla User Experience Thread
Quote:
In fact, all platform development will come from those of us who will reject to install the Android runtime no matter what, and thus will be in severe need of native applications. Unless a friggin miracle -- that did never happen in the many years a big name such as Nokia was behind this -- occurs and commercial developers start targeting the device. * If you don't think that is the case, ask yourself: Would the Whatsapp protocol have been RE'd if it the official application could have been run in N9 since day 1? |
Re: Jolla User Experience Thread
Quote:
I'd rather go without calendar/contacts syncing than using advertising companies like google, microsoft. And while you can get paid accounts, without the ads (and hopefully without the invasive tracking, but somehow I doubt that...) but they use non-standard protocols which they tend to change at their whims as well. Use open protocols and trustworthy services. They are out there, really. |
Re: Jolla User Experience Thread
Quote:
The part about less itches to scratch... man, tell me about it. I think it's an isolation tactic that's counterproductive in terms of having native apps or rarely seen/used apps because it's not popular here but overlooking the popularity elsewhere. Quote:
Sadly, the way that anything popular is shunned here, say goodbye to native Instagram, Skype, Vine and a few others because well... nobody here would use it, the market that owns a Jolla phone also would rather use Diaspora, Tox.im, and something else (lord I forgot the name of that pic sharing web app, M-something). Quote:
|
Re: Jolla User Experience Thread
Quote:
|
Re: Jolla User Experience Thread
Quote:
|
Re: Jolla User Experience Thread
Quote:
Quote:
My 2 cents: If WhatsApp was available on day one, the people who complained about insecurity would be the ones who most likely have the ability to develop their own "secure" alternative... if they wanted to. That said, those people who wanted a secure alternative would probably be allergic to WhatsApp and insist on using something like SilentCircle or whatnot. The majority of people who picked up the N9 and just wanted to use WhatsApp would probably never have even signed up on TMO in the first place if that had happened :D |
Re: Jolla User Experience Thread
Quote:
Quote:
I am realistic: if you're interested in having access to as many programs as possible, then I'm certain the emulator strategy will work much better for you. But precisely because you will be content, you will not call as much for native applications (e.g. to developers on this forum) and the net result is less native applications. Therefore, (a) `isolationists' lose (b) Jolla loses. Quote:
a) Jolla device ends up getting money and marketshare b) Jolla device never gets money and marketshare By my first point on this post, I'm going to assume that shipping an emulation layer does not have an impact on whether a or b is most probable (debatable). If (a) happens, then it does not matter whether you destroyed demand for native applications by shipping an emulator -- you will have native applications either way. So win win situation. If (b) happens, which is, IMHO, the most probable, then only hobbists will be the ones actually developing for the platform. In this case, and by arguments in my previous post, you've basically killed your platform by shipping an emulator. Or at a minimum, you've made it way less enticing for hobbists to develop native applications for the platform. Quote:
Quote:
And thus I lost a bit more faith in humanity, but that's another story. |
Re: Jolla User Experience Thread
Quote:
I suspect such a large set of people is only possible when basically a big % of N9 owners demand it i.e. when they cannot run the official client via emulation -- but maybe we should ask the actual N9 Whatsapp client devs :) |
Re: Jolla User Experience Thread
Quote:
Quote:
Quote:
|
Re: Jolla User Experience Thread
Quote:
Quote:
Quote:
Quote:
I'm game for stuff like Tox.im to replace Skype. But for that to happen, Jolla needs to be as disruptive as Hades and folks that have been isolated need to discuss openly and clearly why better options exist. And folks will have to be willing to jump ship and learn new things... Oh hell. We're doomed. Quote:
Quote:
Great points all around from you. Thanks for sharing them. |
Re: Jolla User Experience Thread
All great points guys and very interesting, but please MODS move those Android-compatibility-a-plus-or-a-curse posts to a separate thread, how is this user experience on Jolla?
|
Re: Jolla User Experience Thread
Well, we developers are users too and with a device like the Jolla, where you can actually develop on the device, "user experience" takes on a larger meaning.
|
Re: Jolla User Experience Thread
Please share your developer experience with Jolla, not just Jolla anticipation and worries about ecosystem and if android is gonna help or not, that is hardly an experience yet, just speculation, not for experience thread
|
Re: Jolla User Experience Thread
Dude, we're almost a 1000 posts in, lighten up.
|
Re: Jolla User Experience Thread
Quote:
|
Re: Jolla User Experience Thread
Quote:
Kidding aside, can anyone tell me whether searching in Mail app works well? Also, can I edit quotes when replying? How about copying texts in a mail? |
Re: Jolla User Experience Thread
Does anyone know how Viber and Skype work on Jolla?
I also wonder how Facebook and GTalk messaging works. I am currently using Windows Phone and Facebook messaging is horrible (notifications are very problematic) and GTalk is not integrated. I miss N9's messaging capabilities. Is there instant notifications when a Facebook or GTalk message is sent to me? |
Re: Jolla User Experience Thread
Quote:
Editing quotes when replying works: tap where you want to edit and start writting or deleting text. I could copy mail text from reply mode but I couldn't figure out how to do it in the mail view mode. |
Quote:
|
Re: Jolla User Experience Thread
User experience seems to be connected if you are a jolla fan or not. Drop a jolla phone in a real usability test and I fear that usability result will be very bad. Might be wrong but that is what I read from this thread.
|
Quote:
|
Re: Jolla User Experience Thread
Quote:
At least the rest are better than N9... |
Re: Jolla User Experience Thread
Quote:
So far only supporters bought it for what ever reason. I hope that next device can be a bit more for end users. |
Re: Jolla User Experience Thread
Quote:
The N9 (only and final consumer HW to run Harmattan) had an uncorrectable hardware design error though: the Pentile display that proved to be incompatible with my eyes and usage pattern. Hardly usable for reading small text. As far as I can tell at present now there will be no such thing with the Jolla, For certain I will discover the Jolla to have untolerable and incomprehensible shortcomings, but all fixable in software. So let's lighten up and follow the real story: how Sailfish matures through updates during first half of 2014? |
Re: Jolla User Experience Thread
Quote:
You can expect reviewers to switch to a brand new OS, as long as it comes from some big company they know. You can't expect the reviewers to help Jolla to make it. Jolla has to make it on its own and become big. Then and only then will the press start paying attention. |
Re: Jolla User Experience Thread
Quote:
|
Re: Jolla User Experience Thread
Not following your logic here. Apple and Google both didn't have a mobile OS before 2006. Google bought theirs, Apple made theirs. And they both started from "ground zero" in terms of acceptance. There were no guarantees.
In fact, the two players that had long-term OS's - Windows and Palm were both outclassed by the upstarts. Both had some serious usability issues that were later overcome via the simplification of iOS and Android. Windows survived (much to my dismay) and Palm morphed into WebOS which was doomed due to Leo Apotheker's bad decisions. People switched because the older way phones were done - notice I'm ignoring Nokia - it wasn't how folks wanted them. 7 years into this cycle of iOS/Android, it's time for something new. For something new from the next soon-to-be-big company. Let it be Jolla. Quote:
Quote:
People switch all the time. Otherwise, we'd all be using Windows Mobile still (which also commanded a major percentage of prior generation smartphones). |
All times are GMT. The time now is 07:21. |
vBulletin® Version 3.8.8