maemo.org - Talk
Page 4 of 32 « First 23 4 5614 Last »
Show 40 post(s) from this thread on one page

maemo.org - Talk (https://talk.maemo.org/index.php)
-   SailfishOS (https://talk.maemo.org/forumdisplay.php?f=52)
-   -   SailfishOS 2.0 Nexus 5 CM12.1 Alpha1 | Sfdroid Pre-Alpha/Early Preview (https://talk.maemo.org/showthread.php?t=96932)

tomislav 2016-09-15 13:55
Re: SailfishOS 2.0 Nexus 5 CM12.1 Alpha1 | Sfdroid Pre-Alpha/Early Preview
 
How do install patch ? I just flashed earlier version of multi room

mautz 2016-09-15 14:22
Re: SailfishOS 2.0 Nexus 5 CM12.1 Alpha1 | Sfdroid Pre-Alpha/Early Preview
 
Just boot into CM13, install Multirom app from Play Store and let it patch your kernel, but do not update the recovery. Just take a look at the xda link in the wiki.

juiceme 2016-09-15 20:50
Re: SailfishOS 2.0 Nexus 5 CM12.1 Alpha1 | Sfdroid Pre-Alpha/Early Preview
 
Quote:
Originally Posted by minimec (Post 1514897)
Lipstick freeze workaround

I do also encounter UI freezes from time to time (once a day seems accurate and NOT during calls). My workaround is the Powermenu2 app in combination with a launcher I created, which basically restarts the lipstick UI. So when the screen is 'on' I can simply 'long press' the power button and lipstick will restart..
That's a good workaround, and since I have had 2 such freezes last week I thought of setting that up.

HOWEVER it seems I have today found a way to get out of the lipstick freeze without that, using just gestures! :D
(To be confirmed yet, I'll have to wait for the next freeze and try to unlock my device again the same way before I can say it is official)

So, provided your freezing is the same kind as mine;

When my device locks up in lipstick freeze, what happens is the screen still responds in a "partial way"; When I for example pull it out of my pocket when the screen is off, the LPM screen activates and by double-tapping I get the "bright lockscreen" where I'd need to swipe left or right to enter unlock code. Now, this is where the screen is not responding, I cannot pull it right or left, it just don't move.

Now, I realized if I push power button quickly twice, I will get to the unlock code entering dialog. Well, cannot do much there since there's the freeze and none of my tapping of the numbers works.

Now comes the funny part, I found out how to enter the lock code numbers!
It seems that you need to do two-finger taps, and not one-finger taps to activate the screen as "one tap", so when keying in the numbers, at the same time with each keystroke tap the upper part of the screen with another finger!!!
Magic happens; the numbers are reacting, and when you tap the "open" button you will get to normal SFOS screen and it is not hung any longer!!

tomislav 2016-09-15 21:27
Re: SailfishOS 2.0 Nexus 5 CM12.1 Alpha1 | Sfdroid Pre-Alpha/Early Preview
 
Quote:
Originally Posted by mautz (Post 1515092)
Just boot into CM13, install Multirom app from Play Store and let it patch your kernel, but do not update the recovery. Just take a look at the xda link in the wiki.

Thanks a lot, any walk arounds for viber app

explit 2016-09-15 21:37
Re: SailfishOS 2.0 Nexus 5 CM12.1 Alpha1 | Sfdroid Pre-Alpha/Early Preview
 
Quote:
Originally Posted by juiceme (Post 1515125)
That's a good workaround, and since I have had 2 such freezes last week I thought of setting that up.

HOWEVER it seems I have today found a way to get out of the lipstick freeze without that, using just gestures! :D
(To be confirmed yet, I'll have to wait for the next freeze and try to unlock my device again the same way before I can say it is official)

So, provided your freezing is the same kind as mine;

When my device locks up in lipstick freeze, what happens is the screen still responds in a "partial way"; When I for example pull it out of my pocket when the screen is off, the LPM screen activates and by double-tapping I get the "bright lockscreen" where I'd need to swipe left or right to enter unlock code. Now, this is where the screen is not responding, I cannot pull it right or left, it just don't move.

Now, I realized if I push power button quickly twice, I will get to the unlock code entering dialog. Well, cannot do much there since there's the freeze and none of my tapping of the numbers works.

Now comes the funny part, I found out how to enter the lock code numbers!
It seems that you need to do two-finger taps, and not one-finger taps to activate the screen as "one tap", so when keying in the numbers, at the same time with each keystroke tap the upper part of the screen with another finger!!!
Magic happens; the numbers are reacting, and when you tap the "open" button you will get to normal SFOS screen and it is not hung any longer!!
Hm.... Will try on my Fairphone 2 next time, when it hangs....

juiceme 2016-09-18 17:14
Re: SailfishOS 2.0 Nexus 5 CM12.1 Alpha1 | Sfdroid Pre-Alpha/Early Preview
 
Quote:
Originally Posted by juiceme (Post 1515125)
That's a good workaround, and since I have had 2 such freezes last week I thought of setting that up.

HOWEVER it seems I have today found a way to get out of the lipstick freeze without that, using just gestures! :D
(To be confirmed yet, I'll have to wait for the next freeze and try to unlock my device again the same way before I can say it is official)
And it is confirmed, today I got the screen lockup again and managed to get out of it by the same method;
  • 1.) when the device stopped responding to touches, did double-push power button to lock it, then again double-push to get to the lockscreen pin entry.
  • 2.) did the number entry with 2-finger-taps and was able to unlock the device, unfreezing lipstick :)
Note; at least my device is prone to lipstick freeze after a phonecall, altough not every time, maybe one out of every 5 or so... Somehow dependant on what gestures I do after ending the call.

BluesLee 2016-09-18 19:18
Re: SailfishOS 2.0 Nexus 5 CM12.1 Alpha1 | Sfdroid Pre-Alpha/Early Preview
 
Quote:
Originally Posted by juiceme (Post 1515259)
And it is confirmed, today I got the screen lockup again and managed to get out of it by the same method;
  • 1.) when the device stopped responding to touches, did double-push power button to lock it, then again double-push to get to the lockscreen pin entry.
  • 2.) did the number entry with 2-finger-taps and was able to unlock the device, unfreezing lipstick :)
Note; at least my device is prone to lipstick freeze after a phonecall, altough not every time, maybe one out of every 5 or so... Somehow dependant on what gestures I do after ending the call.
Confirmed.

BluesLee 2016-09-21 05:49
Re: SailfishOS 2.0 Nexus 5 CM12.1 Alpha1 | Sfdroid Pre-Alpha/Early Preview
 
Quote:
Originally Posted by juiceme (Post 1515259)
And it is confirmed, today I got the screen lockup again and managed to get out of it by the same method;
  • 1.) when the device stopped responding to touches, did double-push power button to lock it, then again double-push to get to the lockscreen pin entry.
  • 2.) did the number entry with 2-finger-taps and was able to unlock the device, unfreezing lipstick :)
Note; at least my device is prone to lipstick freeze after a phonecall, altough not every time, maybe one out of every 5 or so... Somehow dependant on what gestures I do after ending the call.
Do we know the reason for those two UI freezes? I encounter them more often in the last months, is it related to the underlying CM, SFOS version ...?

juiceme 2016-09-21 10:53
Re: SailfishOS 2.0 Nexus 5 CM12.1 Alpha1 | Sfdroid Pre-Alpha/Early Preview
 
Quote:
Originally Posted by BluesLee (Post 1515391)
Do we know the reason for those two UI freezes? I encounter them more often in the last months, is it related to the underlying CM, SFOS version ...?
Not sure, I'll have a look at journal the next time it happens, now that I know how to get out of it.
Just a hunch, could be that some operation in UI gets lipstick in a non-happy path. Something that happens when an application's window is delayed in closing like the phone application does.

mautz 2016-09-21 12:24
Re: SailfishOS 2.0 Nexus 5 CM12.1 Alpha1 | Sfdroid Pre-Alpha/Early Preview
 
For me your workaround does not work, but maybe its because i use mazelock patch.

BluesLee 2016-09-21 12:26
Re: SailfishOS 2.0 Nexus 5 CM12.1 Alpha1 | Sfdroid Pre-Alpha/Early Preview
 
Quote:
Originally Posted by juiceme (Post 1515401)
Not sure, I'll have a look at journal the next time it happens, now that I know how to get out of it.
Just a hunch, could be that some operation in UI gets lipstick in a non-happy path. Something that happens when an application's window is delayed in closing like the phone application does.
For me it happens too often now. People here use different SFOS versions and CM bases so that they may not encounter it. I migrated everything from one phone to the other using multirom and tars and the issue happens more often but it should not be hardware related ...

juiceme 2016-09-21 17:50
Re: SailfishOS 2.0 Nexus 5 CM12.1 Alpha1 | Sfdroid Pre-Alpha/Early Preview
 
Quote:
Originally Posted by mautz (Post 1515407)
For me your workaround does not work, but maybe its because i use mazelock patch.
I suppose so. For mazelock to work you need to track finger-drawn vertexes on the touchscreen which is very different from getting input from taps.

mautz 2016-09-23 06:07
Re: SailfishOS 2.0 Nexus 5 CM12.1 Alpha1 | Sfdroid Pre-Alpha/Early Preview
 
Rooting Sfdroid

Start Sfdroid and open settings.
Tap on about phone and look for the build number. Tap the build number 7 times, after a few taps you'll get a counter which tells you how many taps are left until the developer options are activated.

Enter the developer options and enable root for apps.

Restart the phone into recovery and flash SuperSU 2.52, newer versions did not work.

I have uploaded it here: https://www.dropbox.com/s/q7h2f8v92d...v2.52.zip?dl=0

Reboot the phone and enjoy root in Sfdroid.

I've tested this version with Multirom, but it should also works with a normal installation.

biketool 2016-09-23 11:01
Re: SailfishOS 2.0 Nexus 5 CM12.1 Alpha1 | Sfdroid Pre-Alpha/Early Preview
 
Looks great!
I have been looking for an easy install Sailfish image for my (flo) Nexus7 64gb.
Cyanogen+Fdroid is less of a toilet than Android+GooglePlay but I want a real OS and just sandbox the Cyanogen for a few apps.
I tried Ubuntu Touch but it is just too sparse, reminded me of the sparse catalog for my old OpenMoko and still had non-standard commands from using Android bits..
Well, once I fix the cracked touchscreen I will be ready to install. Then on to helping bug hunt sfdroid! Will any config files need edited to run sfdroid on the Nexus7?

mautz 2016-10-01 08:57
Re: SailfishOS 2.0 Nexus 5 CM12.1 Alpha1 | Sfdroid Pre-Alpha/Early Preview
 
Quote:
Originally Posted by juiceme (Post 1515418)
I suppose so. For mazelock to work you need to track finger-drawn vertexes on the touchscreen which is very different from getting input from taps.
It works!

Just lock and unlock the phone to be prompted with the maze dots. Now you have to tap with three fingers of whom one finger has to touch a dot in the top row. The dot touch gets registered and everything is back to normal and you can swipe your maze.

Thanks again for your great find!

trashHeap 2016-10-03 16:02
Re: SailfishOS 2.0 Nexus 5 CM12.1 Alpha1 | Sfdroid Pre-Alpha/Early Preview
 
This works like a dream save for MMSes.

By and large MMSes work on 3G but dont work on 4G (T-Mobile USA)

Annoyingly enough though there is virtually no 3G coverage in my area, just spotty 2G and fairly good 4G coverage. I *think* they might work over 2G but my 2G connection is so weak they often fail to download in such a way that there is no option to retry.

When I am in range of 3G they do work over 3G but I dont live or work in range of 3G.

Ive tried a number of different APN settings and tweaks and I can't get 4G MMS to work. 4G data appears to work fine.

If anybody knows a solution I would be much obliged.

juiceme 2016-10-03 16:56
Re: SailfishOS 2.0 Nexus 5 CM12.1 Alpha1 | Sfdroid Pre-Alpha/Early Preview
 
Odd, since I have not seen any problems with either sending or receiving MMS'es, and I use MMS a lot.

Do your problems relate to sending or receiving?
Have you checked what's in the journal when you have problems, and compared to cases when it works OK?
Does SMS work correctly to you?

My network setting is "prefer 4G" but I have to confess I have not checked on which network my device is anchored to when sending MMS messages.

trashHeap 2016-10-03 17:17
Re: SailfishOS 2.0 Nexus 5 CM12.1 Alpha1 | Sfdroid Pre-Alpha/Early Preview
 
Quote:
Do your problems relate to sending or receiving?
I cannot send or receive a MMS on 4G. (T-Mobile USA)
I can reliably do both on 3G.
I seem to have intermittent problems with both on 2G. 2G might be choking on large file sizes or having issues with signal strength, im not sure.
The data connection is always fine for the browser across 3G and 4G.

Quote:
Have you checked what's in the journal when you have problems, and compared to cases when it works OK?
Im extremely new to Sailfish OS, though I am a fairly experienced desktop Linux user (though I havent logged much time with systemd). How would I do that? I know how to ssh into the device. Are you talking about Journalctl ?

Quote:
Does SMS work correctly to you?
Vanilla SMS is fine.

trashHeap 2016-10-03 23:23
Re: SailfishOS 2.0 Nexus 5 CM12.1 Alpha1 | Sfdroid Pre-Alpha/Early Preview
 
I ran the MMS logger from the Jolla Store and captured a failed MMS over 4G here: http://pastebin.com/dG8Btqyb

And a success over 2G here: http://pastebin.com/FVBLXiUi

Ive tried three or four different recommended APN settings for various phones, all with identical results.

This error seems telling but im not sure of what:

Quote:
2016-10-03 18:53:52 [mms-task-http] HTTP status 4 (Cannot connect to destination)
Does anyone know if its possible this im running against an ofono bug like this one? https://bugs.launchpad.net/ubuntu/+s...o/+bug/1360403

nh1402 2016-10-04 07:14
Re: SailfishOS 2.0 Nexus 5 CM12.1 Alpha1 | Sfdroid Pre-Alpha/Early Preview
 
Quote:
Originally Posted by biketool (Post 1515475)
Looks great!
I have been looking for an easy install Sailfish image for my (flo) Nexus7 64gb.
Cyanogen+Fdroid is less of a toilet than Android+GooglePlay but I want a real OS and just sandbox the Cyanogen for a few apps.
I tried Ubuntu Touch but it is just too sparse, reminded me of the sparse catalog for my old OpenMoko and still had non-standard commands from using Android bits..
Well, once I fix the cracked touchscreen I will be ready to install. Then on to helping bug hunt sfdroid! Will any config files need edited to run sfdroid on the Nexus7?
I'm afraid installing sfdroid on the Nexus 7 isn't as easy as that, you will have to get the Android sources and compile it yourself, moving forward we're using a very specific version of CM12.1 for sfdroid, the reasoning behind this will become clear soon.

juiceme 2016-10-04 10:08
Re: SailfishOS 2.0 Nexus 5 CM12.1 Alpha1 | Sfdroid Pre-Alpha/Early Preview
 
Quote:
Originally Posted by trashHeap (Post 1516076)
I ran the MMS logger from the Jolla Store and captured a failed MMS over 4G here: http://pastebin.com/dG8Btqyb

And a success over 2G here: http://pastebin.com/FVBLXiUi

Ive tried three or four different recommended APN settings for various phones, all with identical results.

This error seems telling but im not sure of what:



Does anyone know if its possible this im running against an ofono bug like this one? https://bugs.launchpad.net/ubuntu/+s...o/+bug/1360403
It's possible; it is a well-known fact that some network features are implemented a bit differently on different operators networks, MMS being one of the most patch-up cases.
(And I believe VOLTE is going to be the next problem-nest, when it gains more users...)

mautz 2016-10-05 10:01
Re: SailfishOS 2.0 Nexus 5 CM12.1 Alpha1 | Sfdroid Pre-Alpha/Early Preview
 
Quote:
Originally Posted by minimec (Post 1514897)
Lipstick freeze workaround


Content of liprestart.sh
Code:
#!/bin/bash
systemctl --user restart lipstick
Sometimes restarting lipstick does not work, so i edited the command to first kill lipstick and then restart it.

Code:
#!/bin/bash
killall lipstick && systemctl --user restart lipstick

And by the way, does anyone know when 2.04 will be available for us Nexus users?

juiceme 2016-10-05 10:06
Re: SailfishOS 2.0 Nexus 5 CM12.1 Alpha1 | Sfdroid Pre-Alpha/Early Preview
 
@mautz, it is enough just to do "killall lipstick", no need to restart it...
System will automatically restart it when killed. :)

juiceme 2016-10-05 10:13
Re: SailfishOS 2.0 Nexus 5 CM12.1 Alpha1 | Sfdroid Pre-Alpha/Early Preview
 
Quote:
Originally Posted by mautz (Post 1516146)
And by the way, does anyone know when 2.04 will be available for us Nexus users?
Good question. MER build targets is still on 2.0.2.48 level, and when that is updated; your guess is as good as mine :)

mautz 2016-10-05 10:34
Re: SailfishOS 2.0 Nexus 5 CM12.1 Alpha1 | Sfdroid Pre-Alpha/Early Preview
 
Quote:
Originally Posted by juiceme (Post 1516147)
@mautz, it is enough just to do "killall lipstick", no need to restart it...
System will automatically restart it when killed. :)
I thought the same thing...my phone was in a weird state today, apps took ages to load or didn't even load and the restart lipstick script did not work. Restarting it from terminal did also not work, i then killed lipstick, but it did not restart itself, so i had to do a hard reset.

Quote:
Originally Posted by juiceme (Post 1516148)
Good question. MER build targets is still on 2.0.2.48 level, and when that is updated; your guess is as good as mine :)
Ok, i can wait a few days ;)

BluesLee 2016-10-05 14:27
Re: SailfishOS 2.0 Nexus 5 CM12.1 Alpha1 | Sfdroid Pre-Alpha/Early Preview
 
We need some migration path here: i am still on sfos 2.0.0.10 with cm12.1 snapshot, no sfdroid. What do you use?

mautz 2016-10-05 14:31
Re: SailfishOS 2.0 Nexus 5 CM12.1 Alpha1 | Sfdroid Pre-Alpha/Early Preview
 
2.02.51 with CM12.1 and sfdroid. Updated via OTA.

BluesLee 2016-10-05 15:10
Re: SailfishOS 2.0 Nexus 5 CM12.1 Alpha1 | Sfdroid Pre-Alpha/Early Preview
 
Quote:
Originally Posted by mautz (Post 1516187)
2.02.51 with CM12.1 and sfdroid. Updated via OTA.
You did the OTA coming from which sfos version? Are you using 12.1-20150901-SNAPSHOT
-YOG4PAO237-hammerhead?

mautz 2016-10-05 18:48
Re: SailfishOS 2.0 Nexus 5 CM12.1 Alpha1 | Sfdroid Pre-Alpha/Early Preview
 
Yes, i'm using the same CM version. I updated from 2.0.0.10 to 2.0.2.4x and then to 2.0.2.51, because 2.0.2.51 wasn't released when i updated.

mautz 2016-10-05 20:04
Re: SailfishOS 2.0 Nexus 5 CM12.1 Alpha1 | Sfdroid Pre-Alpha/Early Preview
 
Just updated my test installation to 2.0.4.13. Took about half an hour and i only nedded to interrupt and reboot once. Sfdroid still works. Haven't used it much, only checked if my most needed patches are working, which wasn't the case. So i'm back to my normal install with 2.0.2.51, which will get updated if the patches are working.

dlas.revo 2016-10-06 05:29
Re: SailfishOS 2.0 Nexus 5 CM12.1 Alpha1 | Sfdroid Pre-Alpha/Early Preview
 
Hello to all of you! After just reading for a long time, I'd like to do my first post ;-) Thanks to all of you for your good work and helpfulness !

Do you consider an update to 2.0.4 safe? Just set RELEASE to the new version and version --dup with the usual repos enabled?

I'd like to try the update, as I suffer from bad battery life (CPU never suspends) and want to benefit from the updated buteo.

Greetings
Daniel

juiceme 2016-10-06 06:14
Re: SailfishOS 2.0 Nexus 5 CM12.1 Alpha1 | Sfdroid Pre-Alpha/Early Preview
 
Quote:
Originally Posted by mautz (Post 1516222)
Just updated my test installation to 2.0.4.13. Took about half an hour and i only nedded to interrupt and reboot once. Sfdroid still works. Haven't used it much, only checked if my most needed patches are working, which wasn't the case. So i'm back to my normal install with 2.0.2.51, which will get updated if the patches are working.
You mean, update with setting release and then doing dup?
I was under the impression it really only works with officially supported devices (sbj1, tablet, model-C, AquaFish) ??

I myself was going to wait until the new Mer build version 2.0.4.x is released and then rebuild my SFOS image...
Is it safe doing version dup on a non-supported device, if it is your daily driver?

BluesLee 2016-10-06 07:48
Re: SailfishOS 2.0 Nexus 5 CM12.1 Alpha1 | Sfdroid Pre-Alpha/Early Preview
 
Quote:
Originally Posted by juiceme (Post 1516235)
You mean, update with setting release and then doing dup?
I was under the impression it really only works with officially supported devices (sbj1, tablet, model-C, AquaFish) ??

I myself was going to wait until the new Mer build version 2.0.4.x is released and then rebuild my SFOS image...
Is it safe doing version dup on a non-supported device, if it is your daily driver?
Hello juiceme,

in generell OTA should be possible. In case of 2.0.0.10 --> 2.0.4.x it seems to be broken, tried twice, OTA was damn slow and it was not successful.

Its easy to try it without risk using multirom and copies of sfos installation, just remove the device lock and do a cp -av from a third rom. If you are using 2.0.2.x it might work.

mautz 2016-10-06 08:34
Re: SailfishOS 2.0 Nexus 5 CM12.1 Alpha1 | Sfdroid Pre-Alpha/Early Preview
 
Just use the OTA instructions of the first post. OTA using SSH. The update can be slow. 2.0.0.10 to 2.0.2.4x took about 3hours. If the update process hangs at a package fir more than 5 minutes, abort the update with CTRL+C, type "sync" and reboot. Most of the time you have to hard reset your device. When its back up, SSH into it and continue the update with version --dup. If it hangs again repeat the above steps. I didn't update my main SFOS installation because not all patches i need are available.

If you don't use Multirom, ciuldn't you do a full backup with TWRP before updating?

juiceme 2016-10-06 12:03
Re: SailfishOS 2.0 Nexus 5 CM12.1 Alpha1 | Sfdroid Pre-Alpha/Early Preview
 
OK, maybe I'll have a go at it.

However doing OTA that way will only update the bits that come as RPM's, right? So if there is a change in kernel or modules it will of course not update those.
Also the adaptation stays the same, even if there's a new nightly of CM that'd correct some bugs...
That's why thought of rebuilding the whole shebang.

mautz 2016-10-06 12:48
Re: SailfishOS 2.0 Nexus 5 CM12.1 Alpha1 | Sfdroid Pre-Alpha/Early Preview
 
Yes only the RPMs get updated.

I don't think that there will be a new version of CM12.1, the latest snapshot is 13 months old.

abyzthomas 2016-10-06 16:26
Re: SailfishOS 2.0 Nexus 5 CM12.1 Alpha1 | Sfdroid Pre-Alpha/Early Preview
 
Is everyone happy with the voice call quality on CM12.1 Nexus 5? I can hear the caller most of the time fine, but the caller always have a hard time hearing or has a lot of echo effect. I was hoping this update will fix it, but still same. I tried it on 2 Nexus 5 devices and both are doing exact same.

Also, does this build use the second microphone to reduce background noice? It doesn't look like it does.

Any ideas to fix it?

mautz 2016-10-07 10:35
Re: SailfishOS 2.0 Nexus 5 CM12.1 Alpha1 | Sfdroid Pre-Alpha/Early Preview
 
Quote:
Originally Posted by mautz (Post 1516250)
Just use the OTA instructions of the first post. OTA using SSH. The update can be slow. 2.0.0.10 to 2.0.2.4x took about 3hours. If the update process hangs at a package fir more than 5 minutes, abort the update with CTRL+C, type "sync" and reboot. Most of the time you have to hard reset your device. When its back up, SSH into it and continue the update with version --dup. If it hangs again repeat the above steps.
To be on the safe side reinstall the package where the installation crashed with
Code:
devel-su pkcon install <packagename>
after the reboot before starting the update process again.

juiceme 2016-10-07 10:51
Re: SailfishOS 2.0 Nexus 5 CM12.1 Alpha1 | Sfdroid Pre-Alpha/Early Preview
 
Quote:
Originally Posted by abyzthomas (Post 1516300)
Is everyone happy with the voice call quality on CM12.1 Nexus 5? I can hear the caller most of the time fine, but the caller always have a hard time hearing or has a lot of echo effect. I was hoping this update will fix it, but still same. I tried it on 2 Nexus 5 devices and both are doing exact same.

Also, does this build use the second microphone to reduce background noice? It doesn't look like it does.

Any ideas to fix it?
I don't know whether it uses noise cancellation but the voice quality has always been exellent in my setup. Only voice via BT headset is bad, it is absolutely unintelligible.

When I am listening to music via BT and a call comes, I need to reject the call, disconnect BT and then call back, it is that bad.

Bundyo 2016-10-07 11:57
Re: SailfishOS 2.0 Nexus 5 CM12.1 Alpha1 | Sfdroid Pre-Alpha/Early Preview
 
Quote:
Originally Posted by juiceme (Post 1516339)
I don't know whether it uses noise cancellation but the voice quality has always been exellent in my setup. Only voice via BT headset is bad, it is absolutely unintelligible.

When I am listening to music via BT and a call comes, I need to reject the call, disconnect BT and then call back, it is that bad.
Why don't you just redirect it back to the phone after taking the call?


All times are GMT. The time now is 08:11.
Page 4 of 32 « First 23 4 5614 Last »
Show 40 post(s) from this thread on one page

vBulletin® Version 3.8.8