Just got brand new Lumia 900. Using Nokia Drive for an hour, suddenly it shows "lost GPS", then it is trying to look for GPS signals for ever. I let the phone "looking for GPS" for 20 minutes, still not successful. Turn off the phone completely and turn it on, GPS works. Anyone have same problem?
Yep, I saw this behavior with Navigon and Nokia Drive. Looks like a software (firmware) issue...
I have had this issue a few times already. Restarting the app does it for me.
Related
Hi,
I have been using the BH 500 bluetooth receiver happily for about a month. Today something strange happened. Bad connections with the mobile device, and then silence.
I tried to pair my device with my cellphone again, but my BH500 seems to be in some sort of coma. The led is turned red, no way to get the device awake.
A small press on the powerbutton, a longer and even a very long press on the powerbutton does nothing at all (and I have tried MANY times)
Anyone has an idea what happens and what can be done about it?
Thanks,
B
The problem is solved. After three days, I guess that the battery was exhausted. The led went out and I was able to recharge the device again.
I just got a Lumia 900 white and i have noticed the following issues.
The Lumia restarts on its own. It has restarted twice since i got it.
Weird purple screen in low light condition
Rattling sound when phone vibrates. Not like the usual vibrate
Would not connect to a specific router whereas all my other devices can. It can still connect to other routers though
I am running OS version: 7.10.8773.98 and firmware revision number: 2715.1601.8773.12141 which i assume is the latest (tango).
Should i be facing all these issues? I googled around a bit and i found that these issues were previously addressed with updates.
To note, it's an unlocked phone. I can use it with any carriers i want to.
Is there anyway i can re-install tango? I am assuming it's a software issue.
Help please?
Mine never restarted on its own.
I still have the purple screen problem pending a firmware update.
The vibration sound in this phone is like that. All models sound like this.
Never had trouble connecting to any wifi access point/router.
I am having rebooting issues. I think I've narrowed it down to low signal issues. My office is in the basement floor behind the elevators so I'm constantly in and out of signal. I fluctuate between 1-2 bars of 4G or LTE and no signal at all. If I have no signal, it will not reconnect unless I switch it to airplane mode and back. On a few occasions, it has rebooted on me only when I'm at my office. I have contacted Nokia customer support and they wanted me to send it in under warranty. I told them that was useless and that my replacement would have the same issue and told them to try to reproduce the issue with their QA/Dev teams. No response yet.
Mine has shut down twice now for no apparent reason, Always after using Nokia Drive, It was a real pain to start the phone back up too, Had to hold power button for a while, I did think it may be down to signal drops as when travelling the phone has to switch a fair bit I imagine, The phone did get a bit hot so maybe overheating as on both occasions the weather was very warm especially in the car.
no reboot, no purple screen, no ratteling sounds...
but WP7 have some issues with connecting to AP or routers set above chenel 10 (if you are not using automatic). my home router and AP were set at 11 and 12 and my HD 7 could never get connected... and when i changed to lower then 10 it was fine... so now my AP and routers are always set this way.
I have had my phone shut itself down three times now for no obvious reason. That's a bit of a worrying issue if you're on call for work and need people to be able to contact you at any time.
The phone restarting by itself is definitely a weird issue. I never had that happen to me before.
The only weird thing I encountered was the touch screen stopped responding. So I locked the phone and then unlocked it and it worked.
The issues you guys are bringing up here should definitely be covered by Nokia.
Only issue I have is the lumia not syncing contacts to my car's hu...
Sent from my Lumia 900 using Board Express
Yes...
I have had my Lumia 900 for one week, and also had a few a few problems:
1. Two restarts (phone is on, but asks for pin and lock code). Both of which are in a location with very poor/no reception. Both where during the morning (4am and 6am) (can see boot time using a program).
2. Complete discharge, wont initiate charge from computer (think it might have been because I skipped the "red low battery charge phase" (or what we should call it?). Does however charge from a computer if I let it charge with the red battery for a while, then boot it self and after a while it will start charing (with the charge icon blinking.
3. When using the radio in loudspeaker mode, and the screen is locked, after a while (5-10 seconds maybe), it (sometimes) stops, or (sometimes) starts to lag, as if the reception is poor (although the phone hasn't been moved.) pressing the power button, (at slide to unlock) the lag instantly stops. Anyone else wanna test this one? (try a bunch of times, doesn't always happened on mine.)
4. (Pure hardware problem): Rubber gasket between case and USB has been incorrectly paced, and "flaps" in the USB contact. (clearly visible if looking directly into the USB port).
Should I take it back and say I want a new one?
OS Version: 7.10.8773.98
Firmware revision number: 2175.1601.8773.12141
You guys need to exchange for a new phone. My first Lumia 900 had restart issues while idling. The new one doesn't have any reboot problem. My G2X before had reboot problem and screen bleed. I went and exchanged for a new G2X, and problem solved. I will send my Lumia 900 to Nokia for repair as I have another hardware issue. The capacitive buttons aren't very responsive when playing audio through speaker phone.
Has anyone else experienced frequent disconnects between the watch and the phone?
It was happening with my modded Note 3, which had a custom kernel so I was thinking it may be that. But now (for 2 weeks) I've been on a stock Note 4, and it keeps happening. Every once in a while, once a day or maybe once every two days, the phone and watch disconnect.
Android Wear says "connecting" but never does unless I click on Disconnect and then click on Connect, at which point it connects immediately.
I had "Find My Phone" installed, which would notify me when I got disconnected, so I thought it may be that. Uninstalled it a few days ago. Still happens. It's not a huge deal, but it's annoying and I don't see why it should happen.
Any idea?
Noticed the same with my 360 and Nexus 5. Both on stock latest versions.
Issue with mine is that the Moto360 constantly says Disconnected when trying to connect to my Note4. I click connect, it says connected and then quickly changes to Disconnected.
Been trying to figure it out for 3 days now.
I think I realized that the issue is in reconnecting.
I still don't know why sometimes it disconnects, but disconnecting itself wouldn't be an issue if then it proceeds to reconnect on its own.
But I realized that when I'm at home, I leave my phone by the computer and walk around. If I walk outside of the bluetooth range, then it disconnects. That's fine. But then it should reconnect when I come back into range, and it never does. It says "Connecting" and never reconnects unless I do it manually as I said in the OP.
So I guess the question becomes: why does it get stuck on "connecting" when it's in range and should be connected? Is this a Samsung issue or a Moto360 issue?
I have seen the same issue with my Moto 360 and an original Moto X. It normally reconnects but then once in a while it just won't. The easiest solution I have found is to turn bluetooth off and then on again on my Moto X. That always brings it back, a reboot of the 360 does not.
Well as I said in the OP, if I go into Android Wear, click Disconnect and then click Connect, it works. But there is absolutely no reason why it shouldn't auto-connect. If it disconnects, and I don't notice, the rest of the day I go without notifications until I realize the watch has disconnected. That's not how this should work.
Max_Pain said:
Has anyone else experienced frequent disconnects between the watch and the phone?
It was happening with my modded Note 3, which had a custom kernel so I was thinking it may be that. But now (for 2 weeks) I've been on a stock Note 4, and it keeps happening. Every once in a while, once a day or maybe once every two days, the phone and watch disconnect.
Android Wear says "connecting" but never does unless I click on Disconnect and then click on Connect, at which point it connects immediately.
I had "Find My Phone" installed, which would notify me when I got disconnected, so I thought it may be that. Uninstalled it a few days ago. Still happens. It's not a huge deal, but it's annoying and I don't see why it should happen.
Any idea?
Click to expand...
Click to collapse
Hi, i have the same problem, my watch always disconect to my phone (moto x), and then the bluetooth system never start again. When I enter in setup ---- bluetooth---- the bluetooth switch doesn t turn on again until phone reboot.
this is so annoying. and it seems like there's a few people experiencing the same thing but nobody seems to have hit a solution. I have yet to come up with one. if I do, i'll post on here.
Same happens with mine. It just prompts me with a "connect" screen on my phone once in a while. After connecting 2-3 times, it won't appear until next time I turn off Bluetooth.
I get this problem about 2 times per day...running with a Note 2 running 4.4.2 stock but rooted....
Hi guyz,
I'm in possession of a Galaxy S3 Neo and I've got a problem few days ago.
Practically, the phone was connected to a power bank but it went bananas doing strange things during the charging.
I've rebooted the phone plugging off the power bank and the internal battery of the phone.
It seemed to be normal, but after few minutes the phone started to ask me to reinstall stock applications (wi-fi direct, software update, clock, help, neighbours devices service, video player, and so on). With some applications, clicking "ok to reinstall" they are ok, but others seem to be impossible to "reinstall" giving an error.
Idk what i can do, except a full-wipe of the phone. Anyway, I would like to know the cause of the problem (is it the power bank?) and how I can quickly fix the strange issue.
As usual, thx you
My pixel 3 xl will connect to Android auto via USB.... Work for a few minutes then randomly disconnect. Never happened with my pixel 2.
Any suggestions??...I have tried new USB cable.... Still does same thing.
Sent from my Pixel 3 XL using Tapatalk
I have had occassional issues with Android Auto as well -
When I first got the Pixel XL I was able to connect fine via USB and even wirelessly to my Kenwood headunit - but the other day, after connecting to Android Auto, when I tried to make a phone call, Blue Tooth was not connected and I could not get it to connect. I eventualy toggled on and off Airplane Mode - and after that
it connected fine. Havn't had an issue since (knock on wood)
for your situation, have you made sure that USB Debugging i turned off? It won't work with that turned on....
Same problem here.
Never had an issue with my Pixel XL, Pixel 2 or Pixel 2 XL. Yesterday I received my new Pixel 3 XL and Android Auto keeps disconnecting. Sometimes it does last a few minutes, sometimes it does so after a few seconds. It doesn't matter if an app like Spotify or Maps is being started or if I just connect the cable. Android Auto doesn't stop on the phone but only disconnects.
As you can't deinstall Android Auto I already tried wiping cache, wiping data and deactivate. I even tried three different cables.
When I connect my work phone Pixel 2 I don't see this problem. The connection is kept as usual.
I'm getting grey hair over this.
Has anyone found a solution or workaround for this issue?
I've tried absolutely everything, even rolled back to a nano SIM after started with an eSIM.
Gonna RMA this week and cross my fingers.
I wonder if it's a hardware issue or software. Unfortunately I don't have another phone that runs pie so I can't test it. My v30 running nougat works fine. I'm kinda waiting for the next pixel update to see if it fixes it.
If you do rma your phone let us know if that fixes the issue.
Turn off adaptive battery and see if that helps you
Nope, that doesn't help. As I mentioned I have every previous Pixel and all of them work flawlessly with my head unit. All preferences are the same.
There's only one obvious difference: Android Auto is pre-installed on the 3 XL.
Unfortunately I don't know anybody with Android Auto in the car nor owning a Pixel 3 XL to check out if it's something with my head unit.
In a German forum 2 people say they have it working properly...
One of the most frustrating parts is that - for me - it sometimes it works 10 minutes. After I switched back to nano SIM yesterday on my drive home I connected, listened to great music, whatsapped my wife that it is working and boom...disconnect and from then on the known behavior started again.
Did the new rma device fix the issue?
Just send it today and because I bought from provider I've a couple of days for the new one. Used my good ol' Pixel XL today working like a charme...
I'll update when the replacement has arrived.
Experiencing same issue with Pixel 3 non-xl and 2016 Honda Accord. Android Auto disconnects anywhere from 20 minutes to just seconds after I've connected.
I've tried the following:
-Variety of brands of USB-C > A cables
-Disabling all power saving options (whole phone, specific apps)
-Setting screen to stay on when charging (solved AA disconnect issues on my LG V20)
-Re-pairing bluetooth with car
-Re-pairing AA with car
-Resetting car head unit
-Resetting phone
I've had no issues with disconnects, but I use wireless connection with Pioneer headunit.
I got my replacement today and for now the problem looks to be solved but I only sat 20 minutes in the garage messing around with it but that are 19:50 more than my last attempt with the old one.
But I already installed both Android Auto app updates that came in the last couple of days.
/me is crossing his fingers
I'll drive about one hour in the evening and hope everything stays how it is now
It's a pixel 3 software issue. Big thread in the Android Auto support forums. Google doesn't seem to be in a hurry to fix it. Said the November update should, it did not.
Anyone ever find a fix for this? I'm having the same issue, but now cannot connect at all. (Was working. Stopped the car, went into Starbucks, came out and AA won't connect.) My Pixel 2 XL works fine, but I want to sell it.
Like I said I RMAd it and it works flawlessly ever since.
Android Auto Closing Out on Pixel 3
Did anyone find a fix for this? I'm having same problem with a new Pixel 3 (not XL). It will project to the car screen/monitor temporarily, but then disconnect and close out of Android Auto. Sometimes it will automatically switch back in a few seconds. Other times I need to disconnect the USB cable from the car and reconnect to get it to project the screen again. It closes out Bluetooth and stops playing from the phone too. This seems to be an issue with the phone, as I've had this problem in multiple cars. My only solution is to run AA on the phone and not project it. Is Google doing anything about this?
Wahoodean said:
Did anyone find a fix for this? I'm having same problem with a new Pixel 3 (not XL). It will project to the car screen/monitor temporarily, but then disconnect and close out of Android Auto. Sometimes it will automatically switch back in a few seconds. Other times I need to disconnect the USB cable from the car and reconnect to get it to project the screen again. It closes out Bluetooth and stops playing from the phone too. This seems to be an issue with the phone, as I've had this problem in multiple cars. My only solution is to run AA on the phone and not project it. Is Google doing anything about this?
Click to expand...
Click to collapse
My phone connects fine to AA. It stays connected with the cable. Perhaps try a new cable to connect it. I'm on stock rooted.
Sent from my Pixel 3 XL