Related
I'm having several problems with my Qtek 9090
There's a rather loud constant high-pitched noise comming from the screen whenever it is turned on (which is when the device is on!). At first I though it was comming from the speaker, but the screen is definitely the source of the noise. It doesn't matter if the backlight is on or off.
People can't hear what I say when using the phone - it makes no difference whether I use the included headphones or just speak directly into the microphone.
I haven't been able to find a BT headset that works with it. They all have the same problem; The sound scratch so much they're unusable. I tried 3 different brands that all works well with my 2020!
The GSM link often "falls out" - even though there's plenty of link the phone doesn't work (nothing happens when I try to call someone). A soft reset solves this problem!
As you can see, I can hardly use the device as a phone at all I've had the device replaced once, but all the problems persists on the replacement.
Does anyone have similar problems?
1. No, don't have this problem. Strange that it happened on the replacement too.
2. Yes.
3. I have just ordered a jabra headset in the hope it will fix problem#2.
4. Yes.
These problems with GSM are a real headache. One of the primary reasons for buying the PDA2k was to consolidate my mobile into one device. I have seen other people experiencing such problems but from what I could gather, voice over BT worked much better. Have you updated the ROM since you bought it? I should know the answer to 3 today, if DHL delivers, and I can tell you I will not be a happy man if the answer is Yes!
Try a Motorola HS810 headset... works fine for me.
harry_mb said:
1. No, don't have this problem. Strange that it happened on the replacement too.
2. Yes.
3. I have just ordered a jabra headset in the hope it will fix problem#2.
4. Yes.
These problems with GSM are a real headache. One of the primary reasons for buying the PDA2k was to consolidate my mobile into one device. I have seen other people experiencing such problems but from what I could gather, voice over BT worked much better. Have you updated the ROM since you bought it? I should know the answer to 3 today, if DHL delivers, and I can tell you I will not be a happy man if the answer is Yes!
Click to expand...
Click to collapse
I've already tried Jabra Freespeak 250, which didn't work for me
No I haven't updated the ROM as I've been told by the supplier that no new version is available yet!
outz said:
Try a Motorola HS810 headset... works fine for me.
Click to expand...
Click to collapse
I also tried both a Motorola and a SonyEricsson BT headset, but I don't remember the specific models - they both scratched immensely
i use SE 60 and it works ok
As you said, the Jabra250 is pretty much unusable!
Crackling is not constant but goes in waves, even though I do not move.
Am at a bit of a loss what to do now... the device is great apart from this.
>> People can't hear what I say when using the phone - it makes no difference whether I use the included headphones or just speak directly into the microphone
yes PBT read my other post
I have the same problem!!
it is scandalous to sel an device with this big defect!!
Sony HBH-660 works good for me.
People say that they can't hear me when I use the handset, but I don't have any crackling, etc with the headset and voice is clear. You just never know if the headset is going to connect when the phone rings though.
sound from screen
there's a rather loud constant high-pitched noise comming from the screen whenever it is turned on (which is when the device is on!). At first I though it was comming from the speaker, but the screen is definitely the source of the noise. It doesn't matter if the backlight is on or off
Click to expand...
Click to collapse
I have this problem also, I was told to use the new rom but this has made no difference, Please let me know if you have found a solution
[/quote]
Guys,
the hissing coming from the screen is a power supply problem. keep swapping phones until it goes away! I used to build switching power supply and the hissing (in a system designed to operate well above 20kHz) is only able to be heared when unstable, inductor core or cap is broken. The hissing is very 'not normal'.
It appears that the Q9090 is standing out as having more problems than the MDAIII, one is the mic volume, most of the other phones are not complaining about this so there may be something with they way the Q9090 are updated or shipped.
With the Jabra 250, don't forget to pair it pressing BOTH the volume and phone button on the headset on discovery with the 9090.(On bonding, turn off headset, turn on again pressing both buttons)
Funny thing is, I had the cracking also. I deleted the headset in BT manager and paired it again as described above. Now it works ok.
Hi,
I bought a Qtek 9090 a few days ago and I also have the same problem with volume level. People can't hear me when speaking, either with the headset or base microphone.
Using a different headset doesn't help (that's even worse sometimes) but I didn't try a BT heaset (and I don't want to as it would raise potential connection problems). I'm going to contact Qtek for support on this...
Pierre
I too am having problems with the Jabra 250 BT headset and my SPV M2000. The Jabra 250 worked fine on the XDAII but is terribly crackly on the newer model.
This is even when pairing it with the enhanced pairing of pressing Volume Up and Phone button together to pair.
Any ideas?
qtek 9090 bluetooth problem
Hi All,
I have new qtek9090 with cellink bluetooth headset. It is work normal, but i am loosing connection to headset each time qtek go to stand by mode. I need to switch off/on the bluetooth in order to restore the connection. Any ideas?
I often get a message stating:
"The Bluetooth Radio failed to turn ON due to insufficient driver momory available. You must perform a normal reset before you can turn ON the Bluetooth Radio."
Does your device also give you this message?
Is it also using the Broadcom "Bluetooth for Windows CE BT-PPC/PE Version 1.0.0 Build 2200"?
Interested to know if you have the same problems with the same bluetooth driver.
same problem
My qtek 9090 shows te same problem
This is a known problem with the Blue Angel, unfortunately, until they bring out a fix, all you can do is a soft reset.
upgrade
hi all,
how can i get updates from www.imateclub.com?
I can't register there, because I have qtek 9090 and not i-mate
thanks
O2 Sourced info on which BT headsets work
See: http://www.my-xda.com/downloads/Other_Bluetooth.pdf
THE PDA2K is a TERRIBLE MACHINE!
SSSoo many bugs....
1) BLUETOOTH JUNK
Bluetooth (after their so called patch), still headset causes it to turn on repeatedly draining your battery in no time. So unless you are connected to a powersupply, the bluetooth headset is useless cause I have to turn off the bluetooth anyway (if I want battery). Yes, I know it's been discussed many times, it still amazes me everyday.
2) ALBUM MOVIE PLAYER DOESN'T WORK AFTER BLUETOOTH PATCH
yep, I've made many tests, clean hardreset machine with no bt patch = I can record video and playback video (MP4) with no problem. Now after installing the BT patch, clicking on the ALBUM app or clicking on PREVIEW after fliming a video in mp4 will freeze the machine for about 5 seconds, and then soft reset it automatically. I've hard reseted twice to check and it's obvious the BT patch ruins it. Mysteriously, it sometimes does work even after the patch. I just wanted to show off my machine today and got laughed at (with good reason!) by a P900 user.
3) CASE IS USELESS
The case that comes with the machine is a joke, it pressed all the buttons even if you almost don't touch the case. They should have left alittle padding. Locking the keys is a must.
4) MORE BLUETOOTH ISSUES
I get repeatable bizzare errors of "memory problems" with bluetooth, and I need to reset the machine (ain't it great?). I also got twice a message about my BT expired.. LMAO. more resets. I actually thing about mapping one of the primary front keys to do a soft-reset.
5) BUILT-IN FAX SOFTWARE IS RUBBISH
A friend of mine tried it numerous times with no success. At clubimate they told him it doesn't work properly. (So why the hell did they put it there?)
6) POWER BUTTON TOO NEAR THE STYLUS
Happened to me several times that when I try to pull out the stylus, it pressed the power button and poweroff the machine. (bad human engineering here)
7) MORE BLUETOOTH MANIA
Amazingly the BT Headset (I tried 3 different models) cannot function for voice recognition, recording or hearing prompts. Seems the driver doesn't support it. If it did, the voice recognition with my Logitech new headset could have been better. Car BT hands-free also don't work for anything else than strictly during a conversation. I almost purchased a Motoroal Handfree BT Car set because I thought I could also use to hear navigation with my GPS Navigation software. I can't gear prompts cause again, it only functions during the conversation, lously.
8) TERRIBLE MICROPHONE DURING CONVERSATION
I've had several people complaining about not hearing me at all while I use the PDA2K directly (no BT headset). I have to should and hold the machine funny close to my mouth. Oh, and setting the microphone AGC gain control to Enable, does NOTHING for increasing microphone sensitivity, it only works for voice recording/notes taking.
9) OK, SO AT LEAST SET THE MICROPHONE AGC ENABLE FOR NOTES TAKING RIGHT? WRONG!
For taking voice notes or recording conversation, setting the microphone to AGC is a must or else you will hear almost nothing. So you Enable it out of no choice... But OOPS.. Now you find out the Voice Recognition software (Both Microsoft Voice Command or Fonix Voice Central) will disable it back, voice recognition software don't work well with the AGC gain enable. So.. you have to choose here Notes taking? Or voice recognition?
I have the machine just about two weeks and already got tired of it. It is a game, it's not a professional machine that you can actually work flawlessly with. Like a delicate toy, far from being a sturdy trusted pocket pc. Don't get me wrong, I'm a gadget freak, and I am willing to 'eat it up and shut up' but this is just to much. I've had a Cassiopeia E-125 for 4 years !!!! And Wwoooff.. ONLY now I can truly appreciate the Casio, 4 years and worked perfectly even though I dropped it many times, slept on it once, hit it by mistake and so on. Never failed me, and I didn't even knew what the Reset button looked like!
I'm truly disappointed... You get many features, but you pay the price of total instability and absolutly horrible amature like support from the HTC guys. No matter how many bugs other can find on iPaqs such as the 6315, I doubt it can reach to the extent this machine has.
:evil: :x :roll: :?
you are the weakest link...
goodbye
Well, since 3 of your 9 are bluetooth and 1 is the case, I think that says good things for the phone that you couldn't come up with any more...
I have the Sprint PPC-6601, which is basically the same phone with no wifi, but with fast 'vision' internet access...
I notice the bluetooth issues too. I have the zenphone profilier, and only turn bluetooth on when I am actually using it, in the car, for instance...
Other than that, I haven't had your issues. Power button seems fine to me. Callers report hearing me loud and clear, and I can hear them extremely well (it's the first phone I've had that can be made 'too' loud...)
Fax/Album/Recording. Haven't tried the fax. I use Resco for Album and recording, as the internal apps are really just 'lite' programs.
For my money, this is a great phone, and I'm very happy. Will be 100% when the get bluetooth working properly..
- Regards,
Ben
ben1000 said:
Well, since 3 of your 9 are bluetooth and 1 is the case, I think that says good things for the phone that you couldn't come up with any more...
I have the Sprint PPC-6601, which is basically the same phone with no wifi, but with fast 'vision' internet access...
I notice the bluetooth issues too. I have the zenphone profilier, and only turn bluetooth on when I am actually using it, in the car, for instance...
Other than that, I haven't had your issues. Power button seems fine to me. Callers report hearing me loud and clear, and I can hear them extremely well (it's the first phone I've had that can be made 'too' loud...)
Fax/Album/Recording. Haven't tried the fax. I use Resco for Album and recording, as the internal apps are really just 'lite' programs.
For my money, this is a great phone, and I'm very happy. Will be 100% when the get bluetooth working properly..
- Regards,
Ben
Click to expand...
Click to collapse
Actually, I found dozens of similar complaints at the clubimate forums (as well as here) In particular, the so many BT complaints, microphone. I've used WINCE ever since it was version 2 16-gray scal on an old casio with 8mb of ram (gee that's history), I just wish HTC could have made a good job of actually making all the features work. The potential is super, and I guess (and hope) that most of the bug can easily be fixed with a decent programmatical procedures. You'll see dozens of complaints at the clubimate forums, lots of disappointed customers. Only HTCs fault for not making enough QA (or some say none)
To use the fax you have to have it enabled by your mobile provider (if they provide it at all)
You sound frustrated....sell it now and move on... Oh thats right there is NOTHING else like it out there.
When they get the bluetooth issues solved (and Im sure they will) you can then rebuy it.
BlueTooth is going to stuck until Microsoft can integrate a decent stack into the OS. It shouldn't be the job of the phone manufacturer to have to do that.
But it should be their job to properly QA it prior to selling it to their customer base.
Hi
I see all your issues and a load more. This device has the capability to be excellent. I hope that they fix the bugs promptly, and that the manufacturers take the bug fixes, and release appropriate updates shortly after.
Currently, O2 are sending out standard replies to all queries regarding this device (O2 XDA IIs) basically they say 'if you're not happy, send it back for a refund'. This is exactly the same as I got when I phoned them.
They keep offering to replace it, but that will not help to solve a software issue!
They did (eventually) fix most of the issues on the XDA II (although bluetooth still does not work correctly on that device either). I hope that the IIs gets the same treatment (with working bluetooth as well!)
Perhaps we should just ignore new releases, run 1 release behind... When the XDA 4 comes out, buy the 3, buy the 4 when they ship the 5 !!
We, the consumer are partly responsible for the manufacturers rushing products to market well before they are ready I suppose.
I checked out the reviews of the XDA IIs (and its friends) before I bought it, they did not have a bad word to say about it. All I can think is that the reviewers, either A) never even clapped eyes on the device, or B) never used it in anger, or C) were only allowed to review it if they said nice things about it. If I had seen a review that listed all the problems, then I would have waited a while --> and probably bought the Motorola MPx instead (which is probably just as bad, and ships with a *stupid* 32MB memory!!)
Nigel
I wish more companies were like Nebula-Electronics.com They released a freeview card 2 years ago, and have been improving upon the software ever since and offering it to customers for free. Their releases are spot on, they respond to bug reports, and they *beta* test the software with end users before they actually release the new version.
The nebula is is the best bit of software/hardware that I have ever bought... Unfortunately, most companies are not like nebula and simply move onto new hardware products without first having fixed the issues in old products.
Nigel
I bought a PDA2k from eXpansys USA, and was NOT able to repro the problem with the video camera. I was able to take video and play it back without any problems at all.
Perhaps you have a truly defective unit. Can you try returning it under warranty?
When the MPX finally ships, (which must be soon as Motorola have finally officially announced it last week and said it will be available to Asian markets this month and Europe Q1 2005) I think we're really going to see what a buggy device can be. I can't see that it's possible to run any software concurrently with wifi or bluetooth with only 32Mb of RAM and wm2003se taking up more than a third of that from bootup.
Still, the form factor is the appeal of the MPX and I can't wait to get one.
I have had my SX66 since Wednesday. Here are the issues I have found, and if anyone has any suggestions, PLEASE let me know!
1. Bluetooth is really bad. Scratchy, drop connections, says signal is low even when headset (Jabra 250) is right next to the unit. (I have the O2 3500 stack installed)
2. Bluetooth response time for headset answer button is SLOW, as is sending the data to the headset when a call comes in and is answered by headset.
3. When Bluetooth is ON, the phone will turn the display ON at random intervals, killing the battery if the backlight is left in the on mode.
4. WiFi is horrible, drops connections constantly, even in same room with router (Linksys w/5db antennas atached). Also, it will NOT work with a network unless the SSID s broadcast - so much for security!
5. The phone features are SO vastly different than regular phones, it makes you wonder if it is working. My unit will NOT echo the DTMF into the headset (which every phone I have ever owned did) to confirm pressing (for VM retirval, etc.). Very confusing.
6. Answer after x rings is a joke. I have it set to 2 rings, and it will never answer automatically headset or not...what's the point?
I hope someone out there can help, otherwise, I may have to put this baby on eBay...because it really sucks at this point!
Tom
Update
Well, I downloaded the O2 update, and that seems to have made a difference in the STABILITY of the BT connection; the unit did not drop my headset at all during the day; further the "response" of the SX66 to a command from the headset seems faster.
Also, since I installed this update, I have NOT seen the screen turn on...perhaps this helped that problem...?
:evil: The BT is STILL scratchy/noisy, but not as bad...perhaps the next round will help...?
I will keep you posted!
I have/had the same issues you are describing. The bluetooth patch 3500-124 fixed almost all my BT issues except the extremely low signal. I tried the HS810, HS820 and the Jabra 250. All were horrible. I even went as far as installing the latest i-mate pda2k ROM 1.22.00 wwe on my sx66. I finally took the advice of a poster on another forum (thanks mswlogo) and purchased a sony hbh-300. So far it has been great. It handles the low signal like a champ and doesnt offer any static or popping.
Need a friggin repeater!
Someone should make a BT repeater...or maybe I should try one of those internal antennas..."as seen on tv!"
Hi,
I have a bluetooth phone in my car, when I first connected the HTC Desire HD up, it had no problems, it paired and everything looked fine... around 10 minutes later, I noticed the bluetooth had simply disconnected from the car but was still running on the phone. I tried to reconnect it up to the car but it wouldn't, I then turned it off, and turned it back on.. it struggled to come back on, but after a few attempts it did come on and the car connected again...
About 5 minutes later the same thing happened again. At this point my phone started to really slow down, I looked in watchtower and the bluetooth was at the top of the list, soon as I turned off bluetooth the phone was responding fine again.
I have since tried connecting to the car multiple more times and have contacted HTC about it, but it seems to disconnect at random times.
Has anyone else experienced similar problems? I heard of similar problems with the original desire so wondering whether it could be something similar.
Kev
Hi Kev,
I am having similar problems with my Desire HD and Audi in car bluetooth system. I posted on another forum and found others were finding the same...
I pair my phone and within couple of minutes the phone has disconnected and won't re-connect.
Not found any definitive answer as yet, but seems BT in this phone isn't so good. Also read a post saying HTC were aware of this but an update wouldn't be available for sometime.
Hopefully someone else can shed some light!
Ben
I also noticed this the last few days with my Bury CC9056 carkit. I have my DHD since October 18th, and up till last friday it connected fine. Since then it connects to the carkit, but within a few seconds the connection is lost...
Sent from my Desire HD using XDA App
Me too. My connection to my Jabra car kit is stable once connected... but trying to get it connected in the first place is a total headache.
Never had this problem with my Desire, so why HTC should change the Bluetooth function in the HD is a mystery.
Sent from my Desire HD using XDA App
tbh i'm glad its not just me thats experiencing problems meaning it could be a software problem rather than something with my handset in particular.
I have been in touch with HTC about this, and I have just sent them the link to this thread so they can see i'm not the only one with this issue, so if anyone else has this issue it may be good to try and keep it all in here.
quentin_rayner said:
Hi Kev,
I am having similar problems with my Desire HD and Audi in car bluetooth system. I posted on another forum and found others were finding the same...
I pair my phone and within couple of minutes the phone has disconnected and won't re-connect.
Not found any definitive answer as yet, but seems BT in this phone isn't so good. Also read a post saying HTC were aware of this but an update wouldn't be available for sometime.
Hopefully someone else can shed some light!
Ben
Click to expand...
Click to collapse
Mines also the audi in car system - do you find that you struggle to turn the bluetooth off and on again once it disconnects or that your phone becomes a little laggy until you turn the bluetooth off?
Yeah - I use the bluetooth widget on the home screen and once it disconnects, it will either take ages to turn off and on again, or it takes 2 presses to turn off.
I have just purchased a Plantronics 230 headset as need bluetooth for my job and it works perfectly - it's no where near the quality of the in car one though.
Also booked in my Audi as it's still under warranty - spoke to them on the phone and they said they will try and update the firmware but the Desire HD isn't on their supported phone list. Have seen a copy of this and not many phones are!!
I would of thought though, that as long as the phone does connect to the phone system in the car that it is compatible.
I have had 30mins once out of it before it disconnected and it was absolutely perfect in that time, including the phone book etc.
I do believe its something to do with the bluetooth on the phone as its a bit strange the way it struggles to turn on again once it fails.
quentin_rayner said:
.. Also booked in my Audi as it's still under warranty - spoke to them on the phone and they said they will try and update the firmware but the Desire HD isn't on their supported phone list. Have seen a copy of this and not many phones are!!
Click to expand...
Click to collapse
That really hacks me off. I mean, BT is a standard. The only reason Audi can give for not supporting a phone that supports at least the same level of BT as them is that they (Audi) do not adhere to the BT standard.
Now, we all know in real life that cars and phones have problems/bugs/whatever BUT unless they can show that there is indeed a *bug* with the phone then the onus should be on Audi to support it.
Dave
Just for the record, it is not just Audi. With me it is together with the Bury carkit, where it first worked fine. (and also works with all other phones...)
Leon
Sent from my Desire HD using XDA App
I can confirm the issues with the BT. I have a parrot Mki9000 in my car and the first time when i tried to connect the DHD , the phone stopped to respond and I was forced to restart it. Since then the phone is paired with the car kit and works fine in a2dp mode for playing music, but when i try to make a call it simply not work. Yo better discribe the problem I will give an example:
The phone i properly connected and playing music, then it's ringing, but the ring sound is coming from the phone speaker not from the car. Then If i answer the call the sound comes from the phone (it shows that there is connection to the car kit). I've tried to press the speaker icon and there is a list with output devices (the phone, loudspeaker, and my car kit) I've tried to select the car kit several times , but there was no success. When I close the phone the music start to play from my car's BT system , so I think there is a problem with the handsfree function/protocol only a2dp works great , and I didn't have any issues with it. Also I've tried file transfer via BT, it works fine two.
Mitsubish Outlander carkit
I can confirm the same issue with the Mitsubish outlander carkit. It even happens that it drops the conversation. sometimes it's ok for half an hour, sometimes it disconnects after 1-2 minutes.
I also have a Jabra (bluetooth) headphone and noticed that if you pick up a call on the phone the sounds doesn't route to the headphone. If I pickup on the headphone it works fine.
ZoidAndroid said:
I can confirm the same issue with the Mitsubish outlander carkit. It even happens that it drops the conversation. sometimes it's ok for half an hour, sometimes it disconnects after 1-2 minutes.
I also have a Jabra (bluetooth) headphone and noticed that if you pick up a call on the phone the sounds doesn't route to the headphone. If I pickup on the headphone it works fine.
Click to expand...
Click to collapse
I have a Pioneer head unit with BT in the car and that seems to work OK, not withstanding the fact that the HU has BT issues of its own (hardware fix needed - I'll get a new unit rather than fix it as I want one with A2DP) but once connected it works fine.
I have a Plantronics headset that seems to exhibit the same problems as your Jabra. At least if I use the phone to answer the call the sound comes through the phone. Also, if I have been using the headset the next call I make goes through the phone speaker which is a pain.
I'm wondering if HTC are routing the sound through the device that's actually *controlling* the call? So even if a headset is paired and connected to the phone, if you use the phone to make the call, as most people would, then it assumes that that's where the sound should get routed. If so, doh .....!!!!!
Just to add, if the sound does get routed to the phone you can use the 'choose speaker' option on the screen to route it to the headset but you shouldn't have to do this.
Anyone reported these issues to HTC and got a meaningful response?
Dave
I did send an email to HTC. Their wonderfull answer was about: "is your phone mentionned in the compatabilylist of the carkit, if not drop the problem there"...
I am still waiting for a response from HTC.
Mines got to a point now where I cant even make a call, it connects to the car, I go through phone book (on car) choose person to call, press call.. it tries for a couple of seconds then comes up disconnected, about 10 seconds later the phone disconnects from the car and will nto reconnect.
My phone then lags like mad until I turn bluetooth off which according to watch tower is taking up about 80% of the CPU.
any updates/solution to all these problems ?
I need it to work with MW600 before buying Desire HD
Last contact I had with HTC is they told me it had been escalted to the software team, so i'm guessing next time a software update comes out it could come about in that, but at the minute no still not fixed.
ZoidAndroid said:
I also have a Jabra (bluetooth) headphone and noticed that if you pick up a call on the phone the sounds doesn't route to the headphone. If I pickup on the headphone it works fine.
Click to expand...
Click to collapse
I've always thought that that's the way it is on all BT headset phones, it makes sense, if the incoming call was for my girlfriend, she can answer from the phone itself, and it automatically routes this through the phones speaker, and if it was answered from the headset, then it routes to the headset.. makes sense to me, I think it's quite good that it does that!
Do any of you have the process com.android.phone crashing when making a phone call through BT?
Ditto my mitsubishi outlander factory bt system. Seemed to work fine first time but then disconnected during first call and would not reconnect for days. Then after connecting not all functions would work ...no incoming call alert on car system, no dialling from car etc. I know the car system is fine as all functions work perfectly with my old nokia xpress music.
Sent from my Desire HD using XDA App
I trust that all of you bother to report this to HTC, at least once per instance ?
- otherwise I don't know when they'll fix this..
Hi, well the Nokia 6.1 is my first Nokia after many, many years on Motorola. It's a good and very beautiful fon. But tow problems annoy me. First thing, the Camera App. Laggy, sometimes, the fon frezze. When In take a Shot from Whatsapp directly, the fon is freezing. Please Update!
Second, so many Problems with Bluetooth-Connect. I'll paire the Nokia with my Garmin Vivoactive 3 - the initial Pair and the intial Synch will works fine. Leave the Connection-Area, the Nokia doesen't reconnect the Watch. I'll test with a Motorola fon and a Amazon Fire Tabelt, the reconncet works very well - it's must be a problem on the Nokia / Oreo Side...
Well, hope your undersand my pooooooor English Greetings from Germany, Andreas
Andreas_SQL said:
Hi, well the Nokia 6.1 is my first Nokia after many, many years on Motorola. It's a good and very beautiful fon. But tow problems annoy me. First thing, the Camera App. Laggy, sometimes, the fon frezze. When In take a Shot from Whatsapp directly, the fon is freezing. Please Update!
Second, so many Problems with Bluetooth-Connect. I'll paire the Nokia with my Garmin Vivoactive 3 - the initial Pair and the intial Synch will works fine. Leave the Connection-Area, the Nokia doesen't reconnect the Watch. I'll test with a Motorola fon and a Amazon Fire Tabelt, the reconncet works very well - it's must be a problem on the Nokia / Oreo Side...
Well, hope your undersand my pooooooor English Greetings from Germany, Andreas
Click to expand...
Click to collapse
Keep in mind that the phone is just released here in Europe. We can't expect them to just have fixed every problem in the universe.
I too have sometimes problems with some minor lag, but I just think we need to be a little more patient for Nokia/Google to release improvements.
Same problems here with Bluetooth connections and overall phone lagginess...
TA-1068 - two different Bluetooth headsets connect flawlessly, but when the phone is in my pocket I experience some connection problems, like losing connection for a moment. If it's out of the pocket and near the headset, connection is ok. Guess some range problems...
I was experiencing the lagging as well, very very noticeable and not good considering previous phone was Moto g2015 and felt just as slow as the Nokia.
So I decided to try something which seems to have fixed all lagging. I disabled the camera app that came with the phone, installed Google camera, and then restarted. Lag is now gone. It really sucks they shipped this phone with a buggy camera app but glad I figured out a fix
Andreas_SQL said:
Second, so many Problems with Bluetooth-Connect. I'll paire the Nokia with my Garmin Vivoactive 3 - the initial Pair and the intial Synch will works fine. Leave the Connection-Area, the Nokia doesen't reconnect the Watch. I'll test with a Motorola fon and a Amazon Fire Tabelt, the reconncet works very well - it's must be a problem on the Nokia / Oreo Side...
Click to expand...
Click to collapse
I'm having very annoying audio problems with the 6.1, with both Bluetooth and the audio jack.
When I connect my phone to a speaker or headset via Bluetooth, the audio is constantly dropping out. Once every 10-20 seconds it sounds like someone turns the sound to 0, pauses, then slowly turns the volume back up again. And this happens with the phone sitting less than 2 feet away from the speaker/headphones. I've tried with two Bluetooth devices (3-4 year old jLab Crasher; brand new Anker headphones) and 2 apps (Amazon Music; Podcast Addict) and all 4 combinations had the constant drop outs. I've tried rebooting the phone. I've used the Bluetooth headset on a different, much older, device and had no issue, so I'm nearly positive it's the phone. Are other people experiencing these frequent drop outs too? Or do I just have a defective Bluetooth radio in my phone?
Normally I don't even use Bluetooth because I prefer the consistency of a plugged in cable. I probably wouldn't have even discovered the Bluetooth problem were it not for the audio jack. It's not as consistent but just as annoying. I'll be listening to Podcast Addict and suddenly the audio will just stop playing through my headphones. I'll look at the app and about half the time the podcast will be paused but the other half it'll still be playing and I'll have to do a weird combination of unplugging and re-plugging the headphones combined with closing and reopening the podcast before it'll play through the headphones again. Again, is anyone else experiencing headphone jack issues?
Similar 3.5mm audio plug problems here also.
Tremelo said:
I'm having very annoying audio problems with the 6.1, with both Bluetooth and the audio jack.
When I connect my phone to a speaker or headset via Bluetooth, the audio is constantly dropping out. Once every 10-20 seconds it sounds like someone turns the sound to 0, pauses, then slowly turns the volume back up again. And this happens with the phone sitting less than 2 feet away from the speaker/headphones. I've tried with two Bluetooth devices (3-4 year old jLab Crasher; brand new Anker headphones) and 2 apps (Amazon Music; Podcast Addict) and all 4 combinations had the constant drop outs. I've tried rebooting the phone. I've used the Bluetooth headset on a different, much older, device and had no issue, so I'm nearly positive it's the phone. Are other people experiencing these frequent drop outs too? Or do I just have a defective Bluetooth radio in my phone?
Normally I don't even use Bluetooth because I prefer the consistency of a plugged in cable. I probably wouldn't have even discovered the Bluetooth problem were it not for the audio jack. It's not as consistent but just as annoying. I'll be listening to Podcast Addict and suddenly the audio will just stop playing through my headphones. I'll look at the app and about half the time the podcast will be paused but the other half it'll still be playing and I'll have to do a weird combination of unplugging and re-plugging the headphones combined with closing and reopening the podcast before it'll play through the headphones again. Again, is anyone else experiencing headphone jack issues?
Click to expand...
Click to collapse
You can start this problem at the Nokia support app. They can help you through chat. Maybe they know the solution for that
I too came from Moto
BrunkBeard said:
Keep in mind that the phone is just released here in Europe. We can't expect them to just have fixed every problem in the universe.
I too have sometimes problems with some minor lag, but I just think we need to be a little more patient for Nokia/Google to release improvements.
Click to expand...
Click to collapse
the camera issues can be remedied by side loading the 7 plus camera apk and with BT try disabling BT "scanning" in the settings. I also noticed an improvement with Wifi by disabling "scanning" as well .
john.r.m said:
and with BT try disabling BT "scanning" in the settings. I also noticed an improvement with Wifi by disabling "scanning" as well .
Click to expand...
Click to collapse
At the risk of jinxing things, I think that fixed it! I had seen something for the Nokia 6 (2017) about disabling BT scanning but I couldn't find it anywhere on my menu so I thought it was specific to that model. Dopey me. Finally found it and switched scanning off and now I've listened over 5 minutes without a single drop out. Thanks!
Edit: Well, that worked for one night. Turned off the Bluetooth and Wifi scanners and was able to listen over Bluetooth for over an hour with just one drop. Then this morning got 5 drops in a minute. Rebooted the phone and got even more. Will contact Nokia support.
Strange. I have obviously switched off the scanning at first set up, but Bluetooth problem is there...
Tremelo said:
At the risk of jinxing things, I think that fixed it! I had seen something for the Nokia 6 (2017) about disabling BT scanning but I couldn't find it anywhere on my menu so I thought it was specific to that model. Dopey me. Finally found it and switched scanning off and now I've listened over 5 minutes without a single drop out. Thanks!
Edit: Well, that worked for one night. Turned off the Bluetooth and Wifi scanners and was able to listen over Bluetooth for over an hour with just one drop. Then this morning got 5 drops in a minute. Rebooted the phone and got even more. Will contact Nokia support.
Click to expand...
Click to collapse
Same here. Tried disabling scanning (after finding it under security of all places!!!) still have dropouts on bluetooth.
divvykev said:
Same here. Tried disabling scanning (after finding it under security of all places!!!) still have dropouts on bluetooth.
Click to expand...
Click to collapse
I used the Nokia support app and this is what transpired:
1) They had me try the Bluetooth in Safe Mode (while holding power button down tap Restart and then a prompt should pop up for Safe Mode; Click that).
2) In Safe Mode listened to 10 minutes of YouTube drop-free
3) Rebooted into Normal Mode and got 3 drops in the first 1 minute.
4) Back to the chat, where Support had me clear the Bluetooth cache (Applications --> Show System Apps (from 3 dots drop down in upper right corner) --> Bluetooth --> Storage --> Clear cache --> Restart) Did not help me. 3 drop outs in first 60 seconds after restart.
5) Next Support had me Reset Network Settings. (Settings --> Network & Internet--> 3 dots in upper right corner --> Reset WiFi, Mobile & Bluetooth)
6) This works!... For now at least. I'll use it and slowly re-add other Bluetooth devices like my car, my Fitbit, etc. If the audio drops suddenly reappear it may give me a clue on what is causing the problem.
Tremelo said:
I used the Nokia support app and this is what transpired:
1) They had me try the Bluetooth in Safe Mode (while holding power button down tap Restart and then a prompt should pop up for Safe Mode; Click that).
2) In Safe Mode listened to 10 minutes of YouTube drop-free
3) Rebooted into Normal Mode and got 3 drops in the first 1 minute.
4) Back to the chat, where Support had me clear the Bluetooth cache (Applications --> Show System Apps (from 3 dots drop down in upper right corner) --> Bluetooth --> Storage --> Clear cache --> Restart) Did not help me. 3 drop outs in first 60 seconds after restart.
5) Next Support had me Reset Network Settings. (Settings --> Network & Internet--> 3 dots in upper right corner --> Reset WiFi, Mobile & Bluetooth)
6) This works!... For now at least. I'll use it and slowly re-add other Bluetooth devices like my car, my Fitbit, etc. If the audio drops suddenly reappear it may give me a clue on what is causing the problem.
Click to expand...
Click to collapse
Thanks for this. Will give it a go and report back. Thanks
I don't remember if I mentioned, but the may update for pixels fixes a similar problem, so in a couple of days it might get fixed for us also.