Related
Hi all,
I've finally received my FP1 and started to familiarise myself with the device. I already noticed some problems I'm going to report here, and afterwards to Fairphone support. (And I hope you are ok with that sequence!)
1) Screen glitches when playback stops.
I tried out to stream music from a Synology NAS, using the app DS-Audio provided by Synology. Whenever playback stops, the lock screen freaks out and gives graphics glitches. It looks like it's trying to show something, and not succeeding. Can anyone confirm this, and point me to a solution? (Minor priority)
2) BT pairing with a Motorola S805 stereo headset does not work.
When I pair the FP1 with the headset, the system reports sucess. However, nothing works. Sound is still played back via the Fairphone's speakers. I deleted the headset from the pairing list, rebooted, re-paired - to no avail. The headset works fine when paired as headphone (i.e. as pure audio sink), including controls (play/pause/skip, volume) with several other computers and handhelds. Also works as sink/source (e.g. for skype calls, including controls) when paired as headset (which I rarely did).
Any suggestions? (High priority, at least for me...)
The case does not allow audio jacks to connect, getting it OUT of the case every time you need a headset/headphone is tedious.
3) When turned off, alarm is not played.
3.1) I used the power schedule to power off the Fairphone and power it on the next morning. I also have an alarm programmed, but it's later than the power on. My device boots, but awaits pin entry for decryption and will not ring the alarm. Alarm is also not rang afterwards.
3.2) I turned off the phone manually. It did not turn on and rang the alarm at a set time.
(High priority!)
Might this be an encryption problem?
If so, can I change this without turning off encryption (and, if not, do I have to reset my FP)?
It was a major YAY for FP, if I remember correctly - and now it's br0ken.
Hi there,
boondiordna said:
Hi all,
I've finally received my FP1 and started to familiarise myself with the device. I already noticed some problems I'm going to report here, and afterwards to Fairphone support. (And I hope you are ok with that sequence!)
1) Screen glitches when playback stops.
I tried out to stream music from a Synology NAS, using the app DS-Audio provided by Synology. Whenever playback stops, the lock screen freaks out and gives graphics glitches. It looks like it's trying to show something, and not succeeding. Can anyone confirm this, and point me to a solution? (Minor priority)
Click to expand...
Click to collapse
Same here. I don't have a solution other than just ignoring it I have this glitches also when I do not stream something.
boondiordna said:
2) BT pairing with a Motorola S805 stereo headset does not work.
When I pair the FP1 with the headset, the system reports sucess. However, nothing works. Sound is still played back via the Fairphone's speakers. I deleted the headset from the pairing list, rebooted, re-paired - to no avail. The headset works fine when paired as headphone (i.e. as pure audio sink), including controls (play/pause/skip, volume) with several other computers and handhelds. Also works as sink/source (e.g. for skype calls, including controls) when paired as headset (which I rarely did).
Any suggestions? (High priority, at least for me...)
The case does not allow audio jacks to connect, getting it OUT of the case every time you need a headset/headphone is tedious.
Click to expand...
Click to collapse
Same here. Not with a headset but with my car. Other people have the same problem, too. See:
https://fairphone.zendesk.com/hc/co...ons/200674643-Bluetooth-and-PBAP?locale=en-us
and
https://fairphone.zendesk.com/hc/en-us/articles/201896728-Bluetooth-connection-Cars-
boondiordna said:
3) When turned off, alarm is not played.
3.1) I used the power schedule to power off the Fairphone and power it on the next morning. I also have an alarm programmed, but it's later than the power on. My device boots, but awaits pin entry for decryption and will not ring the alarm. Alarm is also not rang afterwards.
3.2) I turned off the phone manually. It did not turn on and rang the alarm at a set time.
(High priority!)
Might this be an encryption problem?
If so, can I change this without turning off encryption (and, if not, do I have to reset my FP)?
It was a major YAY for FP, if I remember correctly - and now it's br0ken.
Click to expand...
Click to collapse
I do not understand if 3.2) works or does not work. It reads for me as 3.1) the alarm does not ring but in 3.2) it does.
If so I suspect that the sim-pin-input supresses the alarm (and other activities of the phone). So what you can try is setting the boot AFTER the alarm. Or not using a pin lock for the sim (might not be a feasable solution for you).
clarification: alarm not working when phone turned off
Hyst said:
I do not understand if 3.2) works or does not work. It reads for me as 3.1) the alarm does not ring but in 3.2) it does.
Click to expand...
Click to collapse
Sorry, should have been more clear: if the phone is turned off, I've got no alarms. Neither with a power-on scheduled before or after the alarm.
Hey, this was meant to be a real cool feature. Drat.
Hyst said:
If so I suspect that the sim-pin-input supresses the alarm (and other activities of the phone). So what you can try is setting the boot AFTER the alarm. Or not using a pin lock for the sim (might not be a feasable solution for you).
Click to expand...
Click to collapse
SIM pin is turned of. System encryption is turned on, this needs a device-lock via a (custom) pin or a password. I chose the latter option. I don't want to reset my phone and turn off the encryption. The SIM is prepaid - so if it's stolen, not much harm can be done.
If the phone gets stolen, however, I want nosy people to be locked out. (Suspecting android encryption is quite hackable.)
boondiordna said:
Sorry, should have been more clear: if the phone is turned off, I've got no alarms. Neither with a power-on scheduled before or after the alarm.
Hey, this was meant to be a real cool feature. Drat.
SIM pin is turned of. System encryption is turned on, this needs a device-lock via a (custom) pin or a password. I chose the latter option. I don't want to reset my phone and turn off the encryption. The SIM is prepaid - so if it's stolen, not much harm can be done.
If the phone gets stolen, however, I want nosy people to be locked out. (Suspecting android encryption is quite hackable.)
Click to expand...
Click to collapse
Encryption makes the scheduled on function of very limited use - the device will wait for the passcode required to decrypt the device before doing anything else. It makes a frequent clicking sound after a while if no input is given.
I can confirm that in Fairphone OS 1.1 the phone will not switch on and sound the alarm if the device is encrypted. I've not tried on an encrypted device (don't have one) nor on Fairphone OS 1.0.
If you want to use the alarm clock, you will need to keep the device on (but it can be locked). I'm using llama to automate some profile switching - one of whitch is to turn off a lot of features and set a silent profile when I'm home at night.
There are some reports around the net of issue where a phone would randomly reboot during the night (and then get stuck on the decryption password prompt - which means the alarm will not sound). I've luckily not experienced this on the fairphone.
Hi all. I have a spare Note 2 that I would like to turn into a dedicated media player for my car. Meaning, I don't care about any other apps really, just Spotify and my media player on the device itself.
Technically there really isn't probably much of a reason to root the device that I know of. Admittedly, I don't know anything about rooting a device, so I don't know all the benefits.
Having said that, there is one problem I'm hoping rooting will allow me to bypass. When I turn my note 2 volume all the way up, the connect to my car, when a song begins to play, the volume will sound loud for about 1 second, then all of a sudden drops several DBs. This seems to happen on both of my Note phones, Note 2 and Note 4. I'm hoping that rooting my phone will allow me to bypass what ever is happening on the phone.
I started to go through the process of rooting, one of the first things the instructions say to do is to backup the phone. I followed this h t t p : / / beginnerguides.net/android/how-to-backup-every-mobile-device
However, after starting the process, the backup software said it was unable to connect to my phone. Which I'm not sure why, Windows 10 sees the phone just fine in Explorer.
If I don't care about anything that's on my phone, is there any real need to perform the backup??? Can I just skip this step and move onto rooting?
Did you try to just use another media player? like Shuffle+ for example.
For car use, I recommend AutoMate Car Dashboard app, is really cool :silly:
FUSIONdev said:
Did you try to just use another media player? like Shuffle+ for example.
For car use, I recommend AutoMate Car Dashboard app, is really cool :silly:
Click to expand...
Click to collapse
i've tried an iPhone and a Windows Surface. Neither of those devices had the volume issue.
RickBlacker said:
i've tried an iPhone and a Windows Surface. Neither of those devices had the volume issue.
Click to expand...
Click to collapse
Try another music app like Shuttle+.
If this doesn't fix your issue, root and install agni kernel with boeffla sound control.
With boeffla you can bypass the android audio compressor and reach whatever volume you want.
ps: the volume drop you listen, is just a protection, the track is just loud.
FUSIONdev said:
Try another music app like Shuttle+.
If this doesn't fix your issue, root and install agni kernel with boeffla sound control.
With boeffla you can bypass the android audio compressor and reach whatever volume you want.
ps: the volume drop you listen, is just a protection, the track is just loud.
Click to expand...
Click to collapse
Not sure shuttle will be what I want. I use Spotify, so 90% of all the music I play is through their player.
I will look into agni and boeffla.
Will these work on my Samsung SGH-I317?
Ok suppose a better question is, If I install the AGNI kernel, will I still be able to run Spotify?
RickBlacker said:
Ok suppose a better question is, If I install the AGNI kernel, will I still be able to run Spotify?
Click to expand...
Click to collapse
I supposed you connecting your devices via Bluetooth. It is possible your phones to recognize faulty your connection with car as Bluetooth headset and lowering the volume for protection for your ears. There is a setting "Limited Headphone Volume". You can disable this at some roms at settings or at media player settings.
Sent from my GT-N7100
vagsvag said:
I supposed you connecting your devices via Bluetooth. It is possible your phones to recognize faulty your connection with car as Bluetooth headset and lowering the volume for protection for your ears. There is a setting "Limited Headphone Volume". You can disable this at some roms at settings or at media player settings.
Sent from my GT-N7100
Click to expand...
Click to collapse
I was reminded last night why I even bothered upgrading from my Note 2 to the Note 4… The headphone jack is messed up on it. So, at this point, it does not even matter at this point unless I get that fixed.
As I was digging around last night, I read here at XDA that the AT&T Note 4 is unrootable.
Hi all, having issues with Android Auto - connected via USB. It's been hit and miss re playing music - sometimes plays at normal volume and can be controlled using my car stereo volume controls, sometimes it connects and plays at a low volume that can't be adjusted on either the phone itself or the car controls. Have researched this a lot and none of the suggested fixes have worked. Anyone experiencing similar or got any fixes from experience? TIA
drmorten said:
Hi all, having issues with Android Auto - connected via USB. It's been hit and miss re playing music - sometimes plays at normal volume and can be controlled using my car stereo volume controls, sometimes it connects and plays at a low volume that can't be adjusted on either the phone itself or the car controls. Have researched this a lot and none of the suggested fixes have worked. Anyone experiencing similar or got any fixes from experience? TIA
Click to expand...
Click to collapse
I'm on global (I think, in the UK) and I don't even have Android auto as an app. It's installed but I believe it's an issue with dual apps on MIUI. How did you get it to show?
Yes, it's inbuilt now and not a separate app any longer... when you connect it to android auto you can press the circle bottom right of car screen to open the interface on your phone and adjust settings that way, or download the separate phone companion. Either way, adjusting things didn't fix the issue.
drmorten said:
Yes, it's inbuilt now and not a separate app any longer... when you connect it to android auto you can press the circle bottom right of car screen to open the interface on your phone and adjust settings that way, or download the separate phone companion. Either way, adjusting things didn't fix the issue.
Click to expand...
Click to collapse
A little bit annoying as in one of my cars as its older I don't have Android Auto so used to use the app alone and hang it from a holder
I guess if you download the phone screen companion you could still do that.
Hi everyone,
My problem is that after turning on my Nokia 5.1 Plus the volume goes down on my earphones (plugged). I mean, if I start listening music right after turning on the music volume is ok, and after few seconds it goes down without any notice and if I try to turn it up it's at it maximum, but if I restart the phone and turn it up right after it's a few points below the maximum. And the loop continues this way.
I've switched dev options of audio limitations regarding bluetooth, because I didn't find any for plugged earphones. I think this started happening after upgrading to Android 10, but I'm not sure.
Is there any solution? Is this a bug or a limitation done by android on purpose and has to be disabled via rooting?
Thank you all in advance!
Hey guys, pretty sure a lot of people out there are using a smartwatch along with their Pixel so maybe someone can help me with this: when my Galaxy Active 2 smartwatch is connected most of the time I can not use voice input with Google Assistant / search. When I wake up the Assistant by long-pressing power the device starts listening but apparently can't hear me. When I disable Bluetooth or power off the watch everything's working just fine.
The weird part is this though: most of the time the watch is connected, a Bluetooth icon with two dots on the left and right can be seen in the status bar, but not always! And only when the icon is NOT there, while the watch is STILL connected and fully usable, voice commands DO work! What on earth is going on there?
Same thing with the camera app: when the watch is connected and the icon is there, the cam app tells me a Bluetooth microphone is connected. When the watch is connected and the icon is NOT there, the app doesn't tell me. With the cam it is not a problem either way though because here I can choose what audio source I wanna use, while in the Google app I can't.
Any ideas?
It seems that your Galaxy Active 2 gets recognized by the P6 as a Bluetooth microphone capable device, ergo it won't use the in-build phone microphones.
Does it have microphones, by the way?
You can always change the system "primary" source of a microphone/sound source by going into the Sound menu (press volume rocker, press on three dots, change there or go into See more).
Morgrain said:
You can always change the system "primary" source of a microphone/sound source by going into the Sound menu (press volume rocker, press on three dots, change there or go into See more).
Click to expand...
Click to collapse
Yeah I'm looking for a way to do that, change primary audio source, but I don't see any options for that in the sound or any other menu...
I'll add another bug to the list.
When a watch capable of making and receiving calls (Huawei Watch GT2 Pro) is connected, initiating a phone call from a BT headset/earbuds starts a phone call through the headset, but as soon as the phone call connects, the audio switches from BT headset to phone internal speaker.
You have to disable the "phone" function of the BT settings for the smartwatch to get this to work properly.
This didn't use to be the case, so it's clearly a new bug either in P6P or Android 12.