UMIDIGI F1 | In-Depth Review | Everything you need to know about the F1

AurioDK

eugyxx replied at 2019-5-3 02:27
Just got my F1 and I have exactly the same "calls with low volume" problem. It only affects the ea ...

Are you referring to the use of the jack stick or the speaker in the phone itself when held up against your ear?

I only have USB headphones and those work perfectly well, no problems with sound.

As for normal calls I don´t have any problems either, the only thing I can´t try is the jack.

I posted my settings but I assume you all have done that as well.

libertysky

I have call volume turned up to max. When you adjust the settings, all the other sounds are super loud. Only call volume comes out really quiet.
= Software bug

DrSalvador555

So I posted earlier about getting the "no sound from top speaker" problem fixed...Well that was only temporary, it's again doing it, and I don't know what is causing it. It MUST be software, as game audio and speakerphone work fine, and the top speaker was working (though quietly...) but now it's flat out not working. This is twice it was working and now it's not (once out of box, once after the 'fix') so if anyone has any ideas, that'd be great! At this point I'm ready to root it, change the ROM, the OS, whatever, I can't afford to have it not work for phone calls.

eugyxx

In general the sound volume is fine (for multimedia, games, youtube, netflix, etc et)... but the phone calls answered using the phone and no headset (bluetooth or cable) are really really low volumen. In a quiet office environment it's usable, but outdoors is nearly impossible to hear the other person. I tried configuring different options in the MTK engineering mode and still no luck, the call volume is very low.

Again, using a bluetooth headset the volume is fine. But that's not the point. The point is we have a phone that can't be used to make phone calls by itself as it's nearly impossible to hear the other person talking.

AurioDK

It´s really hard to imagine why things are bad, I tried to mess with some settings and couldn´t get the call volume to be low. That said, it´s not loud at my end and I do have to keep it near the ear but it goes through just fine, I am used to doing that anyway.

The only possible solution I can think of is to do a reset but that´s kinda of crappy if you already invested too much time on setting up your phone.

eugyxx

Resetting the phone is an option, of course, and still not so many things configured, so might give it a try, but really doesn't make a lot of sense, and the fact that some others are having  the same issue make me think about something much more complex than just a specific software or config problem.

DrSalvador555

I've factory reset the phone already and can confirm it neither fixed my low call volume or my top speaker's issue. It's just so broken on the software end.

DrSalvador555

I've discovered another temporary fix, it seems it's getting stuck on headphone mode, even if it's not showing it. A free app called "Lesser AudioSwitch" seems to fix it, just toggle it around a few times and then try a phone call. It fixed it for me, still low volume though.

eugyxx

DrSalvador555 replied at 2019-5-4 02:37
I've discovered another temporary fix, it seems it's getting stuck on headphone mode, even if it's n ...

I guess you are talking about some other problem, because I never experienced the phone getting stuck on headphone mode. So far, the only solution is to use a bluetooth headset and wait until Umidigi does something about it.

Anyone knows if someone from Umidigi visits this forum? If no fix, phone goes back for refund.

AurioDK

If you guys are running the latest update then it could be a hardware flaw, I see no reason to why things function on my end with the same software. Especially now that you have tried a reset without it solving the problem.

I just spoke to another guy here in Denmark who also bought the F1, he too has no problems with calls.
PS: Have you guys tried making a call with Whatsapp or Messenger using call mode only and wifi? .... Could be a carrier problem?  I am just guessing at this point.