Related
After reading some forum threads, I couldnt find any answers to my two main problems.
First of all, the battery life is horrible. After a day of medium usage the battery has to be recharged. I was trying many different things, but nothing would do any difference in battery life. I have been reading about 2-3 days of battery life. No way. Not with my device.
Isnt there anyone who has traced the problem? Is there any fix I dont know about?
Second, what is this light sensor supposed to do? There dosnt seem to be any difference having it on or off in the settings tab, nor is there any difference in various light conditions. I could hold the device in perfect dark or under a 100 Watt light, there dosnt change anything. I was wondering if this is some bug, fault or not implemented feature. A light sensor is supposed to control the keypad backlight. Am i wrong?
One last thing. Is there any setting to control the brightness setting of the device?
Thanks for your help and time.
1. battery life is great for me. have you installed any software that is doing stuff all the time ? have you changed any power settings ?
2. light sensor is only for keypad light. keypad light will not come on in bright conditions.
I don't think there is any setting for screen brightness (I have been looking all over the place). Would be a good thing for HTC to get out in the next firmware release.
First of all thank you for your reply. As it appears, the light sensor does
work as intended after doing some cleaning around the area of it.
Cant think of any reason for this as the device was never really used
outside or under heavy conditions. The battery life however still is
nowhere near good. No programs were installed at all. I did a hard
reset and avoided to install anything till I get some hold on this issue.
As for screen brightness, you are right. There are no settings to be
found in the menu and nothing seems to be posted around the web.
Any other suggestions?
I have had many pda phones. the difference is that they are full computers and can do alot more then normal phones but never have the battery life.
I have never got more then 2 days from any pda/phone, inc. nokia s60s which are supposed to have have good battery life.
I am getting around 3 days from the htc s710. This is with a few calls every day and around 30mins wifi. Although I recharge every 2 days otherwise its on 1 bar for the end of the third day which is disconcerting.
If you are getting less then this on moderate usage it might have a fault. Presumably you have it under guarantee.
I really have to recharge it every night, otherwise I am out of luck on the next
days morning. The only two reasons for this i can think of are, either its really
a fault of the device or battery, or Bluetooth is draining more energy on this
device than it did on any other I know of. Prior to this I was using a Nokia N73
with the exact same usage and was able to operate it for at least 2 days
without the need of recharging.
I am somehow disappointed by this device. While its a great smartphone overall,
the battery issue is giving me a hard time here.
How is your reception? Bad reception could be a reason for bad battery life.
Isn't the N73 a 3G phone and maybe you have better 3G reception than GSM?
Just a theory...
...i get 60 hours after the 3rd charging circle with bluetooth on all the time and two push mail accounts (company exchange server and windows live mobile push, push is active between 7 am and midnight), some phone calls and web sessions. thats absolutely acceptable.
cheers, lutz
htc-s710
same here friends
bluetooth and 1 exchange over gprs and wifi open all the time
nice battery life.
msaw said:
I really have to recharge it every night, otherwise I am out of luck on the next
days morning. The only two reasons for this i can think of are, either its really
a fault of the device or battery, or Bluetooth is draining more energy on this
device than it did on any other I know of. Prior to this I was using a Nokia N73
with the exact same usage and was able to operate it for at least 2 days
without the need of recharging.
I am somehow disappointed by this device. While its a great smartphone overall,
the battery issue is giving me a hard time here.
Click to expand...
Click to collapse
I have found a bug in the power settings.
Quick qu. (before I tell you what it is)
- have you ever changed the power settings (i.e. screen shut down)
- does your screen switch off (It will always dim - but does it switch off completely) ?
rgds
msaw said:
I really have to recharge it every night, otherwise I am out of luck on the next
days morning. The only two reasons for this i can think of are, either its really
a fault of the device or battery, or Bluetooth is draining more energy on this
device than it did on any other I know of. Prior to this I was using a Nokia N73
with the exact same usage and was able to operate it for at least 2 days
without the need of recharging.
I am somehow disappointed by this device. While its a great smartphone overall,
the battery issue is giving me a hard time here.
Click to expand...
Click to collapse
n73 is known for having an above average battery life, so expecting the s710 to be anywhere close to that is asking for dissapointment
I have an E650 and have bluetooth on all day syncd with my tom tom for handsfree calling. Spend about 3 hours a day on the phone, send about 30 txts. if battery is fully charged before i go out i'll have at least 60% left by the time i go to bed. The battery life beats the old xda exec I used to have hands down, so no complaints from me.
colonel said:
I have found a bug in the power settings.
Quick qu. (before I tell you what it is)
- have you ever changed the power settings (i.e. screen shut down)
- does your screen switch off (It will always dim - but does it switch off completely) ?
rgds
Click to expand...
Click to collapse
Yes, I have changed the power settings.
Yes the screen switches off after the set period of time.
msaw said:
Yes, I have changed the power settings.
Yes the screen switches off after the set period of time.
Click to expand...
Click to collapse
But, screen switches off or backlight switches off...is different!
Byee
Sky_Lab said:
But, screen switches off or backlight switches off...is different!
Byee
Click to expand...
Click to collapse
Backlight switches off. I cant see anything on the screen, its going black.
Cant comment if its just the backlight or the screen as well.
The problem you have is well known.
Tomtom is causing this.
You have to change some things in the registry settings.
"\HKCU\Control Panel\Power\ value display"
Make this value 30 and after 30 seconds the display is completly off.
This should solve the problem.
Found this on www.pocketinfo.nl
rademaar said:
The problem you have is well known.
Tomtom is causing this.
You have to change some things in the registry settings.
"\HKCU\Control Panel\Power\ value display"
Make this value 30 and after 30 seconds the display is completly off.
This should solve the problem.
Found this on www.pocketinfo.nl
Click to expand...
Click to collapse
Dear rademaar, I appreciate you advice and help, but I havent ever installed
or used TomTom. While I think that others programs might as well alter
some registry settings and be the cause of the problem, I have to say that we
are talking about a Hard-Reseted, no software-installed Vox here wich cant do
more than a day without charge.
Someone stated that the GSM coverage might be the cause of the problem.
I am starting to think that this might be possible.
rademaar said:
The problem you have is well known.
Tomtom is causing this.
You have to change some things in the registry settings.
value display"
Make this value 30 and after 30 seconds the display is completly off.
This should solve the problem.
Found this on www.pocketinfo.nl
Click to expand...
Click to collapse
I did however check the value you mentioned, and it appears that I dont have
any values inside "\HKCU\Control Panel\Power\", it goes deeper into
"\HKCU\Control Panel\Power\LockLevel" value display gives key "Locklevel=0".
Do you suggest to alter this value or create a new one?
if you backlight is turning off (after dimming), then its not the cause of any issue.
the backlight issue is comprehensively covered here:
http://www.modaco.com/index.php?showtopic=254042
BIG WIFI problem..
Hi, I have just bought it and after trying the wifi (while the phone was charging) I encountered in a problem. First connection ok, then I disable the connection tries again and the wifi status was always connecting...
So I reboot the phone and now I have no wifi status and it say to me that the driver is not loaded!!!!!
impossible to connect to wifi.
I have already done a clean of the system but it still dont work.
No program has been installet yet!
thank you for your help
Problem w/Vox Keyboard - Anyone Else?
Hey all...
First I want to qualify this post by saying that I ABSOLUTELY LOVE THIS SMARTPHONE! I've finally found the convergence of one-handed use w/a full keyboard that does all my contact/appointment tracking, emails, etc.
Now...my problem: I've had the phone about 30 days now, and just last week have had problems with the backspace, carriage-return, shift, function and space keys on the QWERTY keyboard. They will just stop responding in the middle of typing (doesn't matter if it's a message, email, calendar notes, etc.) The only way I can fix the problem is to slightly close & reopen the keypad with a little flex-pressure on either end of the phone.
Luckily Mobile Planet will exchange the phone for me with no charge, but I was just wondering if anyone else was having this problem.
I remember somewhere somebody reported issue with compass in our Relay.
Now I found that it is somehow related with other sensors and/or modules.
So if your compass not working properly turn off wifi, data transfer and GPS and try.
Regards
Mac
Makes no difference for me. Everything on or everything off, the compass is still hopelessly miscalibrated after a reboot. Then a calibration cycle gets it approximately right until the next one.
for me also no difference, however i try, google maps with gps is usually going sometimes ok. havent got the clue behind yet
Jax184 said:
Makes no difference for me. Everything on or everything off, the compass is still hopelessly miscalibrated after a reboot. Then a calibration cycle gets it approximately right until the next one.
Click to expand...
Click to collapse
I'm in the same boat- if I'm driving, it will correct when it uses the GPS, but standing still, it will be off. I think the issues started after updating one of the stock roms. I think the original stock rom was just fine.
I think Nardholio posted something about going back to stock, ripping the battery out with a solid GPS lock and then upgrading.
gee one said:
I'm in the same boat- if I'm driving, it will correct when it uses the GPS, but standing still, it will be off. I think the issues started after updating one of the stock roms. I think the original stock rom was just fine.
I think Nardholio posted something about going back to stock, ripping the battery out with a solid GPS lock and then upgrading.
Click to expand...
Click to collapse
That's only needed if your GPS is totally inoperable.
So the Relay 4G has horrible GPS? Seems to be an ongoing theme with Samsung phones.
Nah, the GPS works fine. It's the compass that's broken.
During the development of our CM rom, it was discovered that the GPS sometimes wouldn't work at all after flashing a custom ROM. This was because the stock ROM had put the GPS to sleep in a way which the custom ROM couldn't wake it from. That's why the battery pull technique was developed. It ensured the GPS was active when you installed the custom ROM.
I don't know if it's still needed or not. I don't think it is. If it is, it would only help you if your GPS doesn't work at all after flashing a custom ROM. If it's intermittent or has poor signal or something, you've got other problems.
Regarding GPS, if I understand correctly, Relay 4G uses both GPS and GLONASS signal, so is the GPS fix considerably quicker than in devices without GLONASS and is the satellite coverage better as well?
I'm particularly interested if there is a noticeable difference in this regard between Samsung Captivate Glide's GPS and Relay 4G's GPS+GLONASS.
Jax184 said:
Nah, the GPS works fine. It's the compass that's broken.
During the development of our CM rom, it was discovered that the GPS sometimes wouldn't work at all after flashing a custom ROM. This was because the stock ROM had put the GPS to sleep in a way which the custom ROM couldn't wake it from. That's why the battery pull technique was developed. It ensured the GPS was active when you installed the custom ROM.
I don't know if it's still needed or not. I don't think it is. If it is, it would only help you if your GPS doesn't work at all after flashing a custom ROM. If it's intermittent or has poor signal or something, you've got other problems.
Click to expand...
Click to collapse
I...don't know the difference between the GPS and the compass. I thought people were using the terms interchangeably, but apparently not.
Solkan said:
Regarding GPS, if I understand correctly, Relay 4G uses both GPS and GLONASS signal, so is the GPS fix considerably quicker than in devices without GLONASS and is the satellite coverage better as well?
I'm particularly interested if there is a noticeable difference in this regard between Samsung Captivate Glide's GPS and Relay 4G's GPS+GLONASS.
Click to expand...
Click to collapse
Okay...this is very interesting. Differences between GPS and compass aside, this still seems like good news. At least to me, cause GPS is very important to me, and its my understanding that the Captivate Glide's GPS is very hinky. Seems like if you stick with stock you'll be fine. Now, bluetooth, I have no idea how the bluetooth is on the Relay (stock or custom ROM), but at least the GPS is good and even better with this GLONASS.
The compass is a standalone chip that detects the earths magnetic fields and tells the device which way it's oriented. But Samsung screwed something up, and every time the phone boots it's way out of calibration. You can fix it by taking it through a quick calibration cycle, and then all's right with it until the next reboot.
The compass and the GPS work together for things like maps. With the compass miscalibrated, the indicator on the map will often show that you're facing a compass direction other than what you really are. And it'll sometimes act as though you're walking backwards when moving at low speeds. But the actual GPS position and tracking are correct, it just has no idea what way you're facing. Again, a compass calibration will fix this.
Jax184 said:
The compass is a standalone chip that detects the earths magnetic fields and tells the device which way it's oriented. But Samsung screwed something up, and every time the phone boots it's way out of calibration. You can fix it by taking it through a quick calibration cycle, and then all's right with it until the next reboot.
The compass and the GPS work together for things like maps. With the compass miscalibrated, the indicator on the map will often show that you're facing a compass direction other than what you really are. And it'll sometimes act as though you're walking backwards when moving at low speeds. But the actual GPS position and tracking are correct, it just has no idea what way you're facing. Again, a compass calibration will fix this.
Click to expand...
Click to collapse
Okay...I've actually been experiencing that lately with my Epic 4G on Cyanogenmod, but I blame that more on the most recent update of Google Maps which changed the entire interface than I do the ROM (I'm on the most recent stable release and before the Google Maps update GPS worked perfectly). But that's still something I'll save for that board. But what you described is exactly what I've been experiencing, the Navigation seems to work, but it takes a while for the indicator (the red arrow) to face the right direction. Since I use it to drive around my own town its not that big a deal, but if I ever go out of town, yeah it could be an issue.
Someone on one of the Relay 4G boards here opened up his Relay 4G and showed exactly where the metal components are, and how with some tweaking it may correct it without calibration...but with my luck I'd break the thing permanently.
I do wonder why the Relay 4G is like this...my only guess is that Samsung was trying to rush it out and didn't have the time to properly test it? I know it was supposed to be called something else (Blaze Q or something). But the funny thing is, even with this "error" (which from the sounds of it is easily remedied), it still seems like more of the spiritual successor to the Epic 4G than I originally thought the Captivate Glide was, or at least an Epic 4G if it was GSM. 5 rows of keys, same shape...I just don't know why this phone isn't more successful than it is. At least you can get it on eBay, new, for about $200-$300. I haven't been inside a T-mobile store in years so I don't know if they regularly keep them in stock or not. But its still available. That Captivate Glide is still available for less than $200, but with its issues with GPS and bluetooth...I don't know, seriously thinking about this phone now.
Anyway, thanks for the response. And by the way, how is the bluetooth on this phone?
EDIT: Herp derp, it was YOU who opened up their Relay 4G! My apologies, sometimes these boards blur together.
Bluetooth seems okay, but I only have one bluetooth device, so I'm hardly an expert.
The guys working on our CM ROM are trying to improve performance when both wifi and bluetooth are in use at the same time. Since they're both 2.4 GHz, they tend to step on each others toes if both are on at once.
You should try a compass calibration on the Epic to see if that helps with the pointer. First step away from large metal and electrical objects, so you're in a fairly clean magnetic environment. Then open up an app that uses the compass, like Metal Sniffer. Then, while keeping the screen on, slowly and smoothly rotate the phone 3 times around each axis. End over end 3 times, then side to side 3 times, then around and around 3 times.
At the end of it, the pointer should now point north.
On the Relay, the values of the magnetic field strength are all totally out of whack before you do this, and they suddenly drop to more rational levels after the calibration.
Jax184 said:
Bluetooth seems okay, but I only have one bluetooth device, so I'm hardly an expert.
The guys working on our CM ROM are trying to improve performance when both wifi and bluetooth are in use at the same time. Since they're both 2.4 GHz, they tend to step on each others toes if both are on at once.
Click to expand...
Click to collapse
Ah okay. Though I can't remember the last time I tried to use both at once. Also, since the Relay 4G actually has a stock JB rom, what benefits would there be getting CM instead? I'm only on CM for the Epic 4G because Samsung/Sprint stopped updating it with Gingerbread.
You should try a compass calibration on the Epic to see if that helps with the pointer. First step away from large metal and electrical objects, so you're in a fairly clean magnetic environment. Then open up an app that uses the compass, like Metal Sniffer. Then, while keeping the screen on, slowly and smoothly rotate the phone 3 times around each axis. End over end 3 times, then side to side 3 times, then around and around 3 times.
At the end of it, the pointer should now point north.
Click to expand...
Click to collapse
Thanks. The folks on the other board said it was an issue with the updated Google Maps app as opposed to the GPS/compass itself, and suggested a downgrade. I may try both solutions, though to be honest with you there's a huge learning curve with the most recent update to Google Maps (for instance still can't figure out how to get it to record my current location, which came in handy with the previous versions if I ever came across a place or store I wanted to visit again).
On the Relay, the values of the magnetic field strength are all totally out of whack before you do this, and they suddenly drop to more rational levels after the calibration.
Click to expand...
Click to collapse
Speaking of that calibration trick, where is it described in detail around here?
EpicMikeNC said:
Speaking of that calibration trick, where is it described in detail around here?
Click to expand...
Click to collapse
That was it! :laugh:
The CM ROM is faster and trimmer than the stock ROM, and fixes a couple of bugs and annoyances. No touchwiz interface, no t-mobile tethering lockout, no samsung bloatware. And while it does have a few bugs of its own, it's under active development by several people, so it's rapidly improving.
Jax184 said:
That was it! :laugh:
Click to expand...
Click to collapse
Oh. lol Ok, thought what you described for the Epic 4G was different, not the same. Gotcha. :good:
The CM ROM is faster and trimmer than the stock ROM, and fixes a couple of bugs and annoyances. No touchwiz interface, no t-mobile tethering lockout, no samsung bloatware. And while it does have a few bugs of its own, it's under active development by several people, so it's rapidly improving.
Click to expand...
Click to collapse
Well I know from my experience with the Epic 4G, you can remove the bloatware with Titanium backup and tether via an ap (if you mean hotspot tether). But at least there's options, stock or CM.
Still don't get why this phone isn't more successful than it is.
Compass is wacky on mine
On my Relay, the compass is off in bizarro land, and has been since I bought it. Stock ICS/unrooted, or stock JB/unrooted, same problem. It doesn't seem to hold calibration at all, and I can even notice that it very slowly spins as I drive. On those times I've tried Google Maps 7 (yuuuuck!), I've noticed that it cheerfully ignores your GPS heading and points the arrow to your alleged compass heading. Between the large amount of change-for-change's-sake UI stupidity, the compass problem, and its general crashiness, I've ditched the update and gone back to the original version.
I've just rooted it yesterday, but I seriously doubt that rooting would make any difference with the compass.
Bobby Tables said:
On my Relay, the compass is off in bizarro land, and has been since I bought it. Stock ICS/unrooted, or stock JB/unrooted, same problem. It doesn't seem to hold calibration at all, and I can even notice that it very slowly spins as I drive. On those times I've tried Google Maps 7 (yuuuuck!), I've noticed that it cheerfully ignores your GPS heading and points the arrow to your alleged compass heading. Between the large amount of change-for-change's-sake UI stupidity, the compass problem, and its general crashiness, I've ditched the update and gone back to the original version.
I've just rooted it yesterday, but I seriously doubt that rooting would make any difference with the compass.
Click to expand...
Click to collapse
How did you root by the way? One-Click?
But yeah, based on what you just said, I'm convinced its the update, not the compass. I don't understand how Google went backwards in regards to this so-called update to Google maps. But the Metal Sniffer solution seems to work, 9 times out of 10 anyway.
Also, I keep looking and looking, but unless I'm still missing it, didn't the update take away to ability to save your current location?
The bootloader is unlocked, there is no reason to run a rooting script. Just flash CWM with Odin/Heimdall and then supersu
I'm having a very similar experience here on CM 10.2 nightlies. Calibrating the compass doesn't always work. When it does it doesn't always stick. And when it sticks, it will be very jumpy, skipping from one direction to the other at random. This prevents compass mode in Google Maps, so it's annoying but not such a huge deal.
Hello All,
I have (2) N5's (one white, one black). I've noticed that battery life on the black one is extremely bad. I'm almost always near a charger, so it was quite a shock when I noticed the black one down to 37% by noon. The next day I swapped phones and never saw the charge on the white one drop below 97%. I wiped both phones and configured each identically and was able to duplicate very similar results over the next few days. This morning I decided to see what happened when I did not connect to a charger. My use has been almost nothing (5 mins of screen time, 3 hrs off battery), yet my phone is already at 81%. I notice "Android OS" is using approx 50% of the battery. I do have a few apps that run in the background and I also leave GPS, BT, mobile and wifi on all of the time, however this is no different than how I used the white one or any previous phones. I suspect this is a hardware problem, however I would like to try to pinpoint the cause to satisfy my own curiosity. Can anyone recommend specific apps/tools that would provide more detailed information about what is going on with the different subsystems (battery, cpu, radios, storage, etc) that could help me find the problem? Thank you.
Do some searching and reading.
It's your apps. Not a hardware problem.
Sent from my Nexus 7 using Tapatalk
Do a complete factory restore on both, with full charge, Then don't touch them at all, the post results
Sent from my Nexus 5 using XDA Premium 4 mobile app
You have a wakelock obviously. My Android OS does the same thing, but it doesnt destroy the battery that bad. My wakelock is wlan_rx_wake, and its very annoying to get rid of. Still havent found a way to kill it yet.
I've noticed if you turn the location settings to "Device only" the Nexus 5 sips battery, while the screen is off, because it isn't always waking itself 1,000+ times a day to report your location.
caribouxda said:
Do some searching and reading.
Click to expand...
Click to collapse
Pretty sure that's what I'm doing?
It's your apps. Not a hardware problem.
Click to expand...
Click to collapse
I initially thought the same thing; however, I did not install any apps after wiping the phone, yet the problem remains. Also, I do not have this problem on my other N5 with all of my normal apps installed and configured for normal use.
Do a complete factory restore on both, with full charge, Then don't touch them at all, the post results
Click to expand...
Click to collapse
I did this... mostly. After wiping both phones (by reflashing the factory image) I did charge both to 100% before using them. Unfortunately, I am on-call 24/7 and have to use one phone at all times. I did keep usage as identical as possible. I did this by not installing any apps and charging at the same times for the same amount of time. Also, my commute and time at work/home/elsewhere was almost identical. Of course there are some things that are out of my control (call, sms, emails, etc received), however it was certainly not enough to account for the difference I am seeing. If I take the phones off the charger at 7A, and use as little as possible, the white one will be >90% where the black one with be <40% by noon.
You have a wakelock obviously. My Android OS does the same thing, but it doesnt destroy the battery that bad. My wakelock is wlan_rx_wake, and its very annoying to get rid of. Still havent found a way to kill it yet.
Click to expand...
Click to collapse
This very well may be. How did you find out that your wakelock is wlan_rx_wake? This is what I'm really seeking - app recommendations or other ways to acquire this in-depth information. I've done some googling, but many of the apps that I've seen recommended do not work with KitKat. What I find most odd is how the white N5 with a 100% identical configuration does not have this problem.
I've noticed if you turn the location settings to "Device only" the Nexus 5 sips battery, while the screen is off, because it isn't always waking itself 1,000+ times a day to report your location.
Click to expand...
Click to collapse
Thank you. I suspect this would make a difference, however I am basing my expected usage on what I get with the white N5 with the same configuration. I did not change any settings on either and would like to see them similar with the same configuration. Once the issue is worked out, I will definitely take your advice and change this setting to increase my battery life.
Thank you all.
Did you download the firmware from Google then flash it in bootloader? Also you need to flash both phones to stock, Then not install any apps or settings on both so there both the same. That's a fair test.
If you can't do this, Then this thread is pointless as far as I'm concerned.
Sent from my Nexus 5 using XDA Premium 4 mobile app
markdexter said:
Did you download the firmware from Google then flash it in bootloader? Also you need to flash both phones to stock, Then not install any apps or settings on both so there both the same. That's a fair test.
Click to expand...
Click to collapse
Yes, I downloaded and flashed the stock image from Google. I run stock on all of my Nexus devices. I did not install any apps, however I had to setup E-Mail and modify my APN settings.
If you can't do this, Then this thread is pointless as far as I'm concerned.
Click to expand...
Click to collapse
Why the attitude? You're clearly a helpful person, based on the time you spend helping others on here. If you're having a bad day or dealing with some personal issues, I sincerely hope things get better for you. If you really have a problem with my test constraints, then please move along. As a UNIX Administrator for the past 15 years, and a component-level electronics tech for 5 years before that, I can tell you from experience that the real world simply does not always provide for ideal conditions. While I agree that a 100% identical setup is preferred as a control, it's simply not an option. Even with my constraints, there is no way the number of emails and texts that I sent/received on a given day are the cause here. All that said, the point of this thread was to gain insight into how I can find more detailed information about what is going on with the various subsystems - either app recommendations or other tools. Much of the information I've found has been high-level - Settings > Battery or BetterBatteryStats (which doesn't work with KitKat AFAIK).
Thank you.
Without the 100% identical test, it's a guessing game.
I don't have an attitude, if I did, I would have told you my credentials, but I didn't think that had anything to do with this thread...
I'm not being a smart-ass buddy, and I do like to help on here as much as possible or as much as my knowledge can allow me.
Better battery stats, is for sure your best bet, that app is a must have for trouble shooting. I'm sure within a few days, there will be a update.
Sent from my Nexus 5 using XDA Premium 4 mobile app
Done a quick search, can't find this mentioned on here.
Is anyone else having trouble with the compass on the Nexus 5? I have a 32Gb white, and never really used Google maps until now, when I noticed the compass is seriously broken. For example, right now, I know I'm facing north, but the arrow in maps is pointing west. Also, if I leave it for a few minutes, it will just start spinning wildly. I'm not next to any sources of magnetism, and I've ran compass calibration through 5 different apps, and it is still broke.
Anyway, I rang Google, and the nice chap said there is an update being released on the 18th to sort out a few software bugs, but my question is, does this sound like software to anyone else?
TheReverend210 said:
Is anyone else having trouble with the compass on the Nexus 5?
Click to expand...
Click to collapse
I too am hoping it's software. Sometimes mine is spot on, other times 90° out.
I've also noticed the compass is usually off. To be honest, I've never had a phone where the compass was consistently accurate but the N5's compass seems to be worse than most.
"Smart Compass" app gives you the magnetic strength, along with the compass and warns if the strength is abnormal. Thing is I've gotten, within a span of minutes, abnormal readings that are both too high and too low. An abnormally low reading seems to be particularly strange. Hopefully it is a software bug. Maybe it will get fixed.
My compass is off too. I can calibrate it, but after sometime it's screwed up again.
Unfortunately I too am affected by this problem, the nexus 5 have all the sensors do not work.
Try downloading a barometer application, you will see that it will no longer work after two days ..... and when a sensor stops, stop all other work (screen rotation, photo-sphere compass etc. ..........
So yes, I hope an update will solve these problems and fairly quickly because otherwise it will "return to sender directly"
Every smartphone I owned needed a compass calibration every now and then.
If you know how, it's not really an issue, i guess those things just happen when you have your device upside down, and in any direction/in your pocket,...
Maybe it helps some of you: This is more or less what I do to calibrate my compass.
TheReverend210 said:
Done a quick search, can't find this mentioned on here.
Is anyone else having trouble with the compass on the Nexus 5? I have a 32Gb white, and never really used Google maps until now, when I noticed the compass is seriously broken. For example, right now, I know I'm facing north, but the arrow in maps is pointing west. Also, if I leave it for a few minutes, it will just start spinning wildly. I'm not next to any sources of magnetism, and I've ran compass calibration through 5 different apps, and it is still broke.
Anyway, I rang Google, and the nice chap said there is an update being released on the 18th to sort out a few software bugs, but my question is, does this sound like software to anyone else?
Click to expand...
Click to collapse
update for 18? : Bien:
Well, I still waiting for this update: (
jokary77 said:
update for 18? : Bien:
Well, I still waiting for this update: (
Click to expand...
Click to collapse
My compass is also f'ed up
This weekend for the first time I had to use my Nexus 5 turn-by-turn navigation on Google Maps to get somewhere. I'm no stranger to the feature, as my previous Note 2 had a dashboard mounting bracket in my truck for this very reason.
Besides the speaker not being loud enough to hear the directions (one of my complaints with this devie), I found the GPS isn't very accurate at all. I have it set to High Accuracy, using GPS, WiFi and data network to find my position. The software often put the arrow about a block away from where I actually was and it kept falling behind telling me where I was supposed to turn.
I was driving at about 40-50 km/h at night with a cloudy sky. I reckon this was never an issue with my Note 2, both with stock TouchWiz and custom ROMs. My Nexus 5 is on stock 4.4.
So, what's going on here?
I honestly can't say I face this issue. My GPS is on point whether driving or just using it when I go hiking or camping.
A couple of weeks back I helped a buddy move into a new place and I loaded up my truck and he gave me the address and I popped it in the GPS, it locked within seconds and got me there just fine. No issues.
I also use it when I go camping. I'll find a nice place to pitch the tent and mark the campsite, then go exploring. Anything interesting I put a pin on it and can find my way back real easy. The speaker issue, sure. I use Viper4android (sound mod) and custom kernels to raise the output gain and make the speakers louder so that's a non-issue for me.
If you're rooted, check out FasterGPS (and if you're not rooted.. go and root).
Regarding sound loudness: try fauxsound (you'll need a compatible kernel and root). It boosts speaker, handset, and aux output significantly without adding distortion (although you can push it far enough to distort if you please).
Great, thanks for the tips.
Yes, it's rooted.
Regarding the sound boost apps, do they work on stock kernel, or do I need to flash a new one, like franco? I really don't want to do a clean wipe at the moment to install a new kernel.
GPS accuracy might be a loose antennae. As for speaker sound, not sure what to tell you. I had the phone resting on the seat beside me since I have no dock, with the radio going at highway speeds and had no problems hearing the voice directions. I didn't even have to max the volume, it was about 70%. No modifications.
Perhaps you have the extra glue around the speakers issue?
I've had the same GPS issues and they have just gotten worse over time. Have had the phone for 10 months. Finally called Google and a replacement is in the mail.
bionemesis said:
I've had the same GPS issues and they have just gotten worse over time. Have had the phone for 10 months. Finally called Google and a replacement is in the mail.
Click to expand...
Click to collapse
Let me know if the replacement is better. My GPS has also degraded significantly, but I wasn't sure if that was related to using CM11.
I haven't driven much lately, so this issue alone doesn't warrant a return for me.
However, the disappointment is stacking up over time. It seems to me that the N5 does a lot of things, but none of them very well. It's basically a tinkerer's toy with an attractive pricetag for the specs. Maybe it's because I came from a former flagship Note 2 device, but I do sometimes miss it.
Ajfink said:
Let me know if the replacement is better. My GPS has also degraded significantly, but I wasn't sure if that was related to using CM11.
Click to expand...
Click to collapse
Will do. I did go back to factory, unrooted and relocked the boot loader. GPS is much, MUCH, worse. It actually loses GPS signal now all the time. I'm convinced now more than ever that this is a hardware issue that gets worse over time combined with software that makes it worse. Hopefully the new, albeit refurbished, phone is better.
My GPS has never worked well, I have had mine for about 10 months as well. I've opened it up so the warranty is void but I don't care about that. I would fix it myself if I knew what exactly the problem was.
I use navigation at least a few times a week and I've never had a single issue with the GPS. It locks on right away, and is always accurate.
I had a nexus 5 from Sprint and the GPS was noticeably off, returned it and Sprint (terrible coverage). I got one from the play store and it's spot on.
Sent from my Nexus 5 using XDA Free mobile app
Got the replacement. Preliminary results...huge difference. Better than the phone originally was when I got it. GPS locks in immediately. And this is rooted stock with elementalx kernel. Will update again after a few days of use, but so far, so good.
Ultimate test passed earlier today. Wife and I went golfing and she dropped her phone somewhere. Loaded up Android Device Manager on my Nexus 5 and drove right to her phone. GPS was bang on.
bionemesis said:
Ultimate test passed earlier today. Wife and I went golfing and she dropped her phone somewhere. Loaded up Android Device Manager on my Nexus 5 and drove right to her phone. GPS was bang on.
Click to expand...
Click to collapse
Gps set to always on? Or can device manager swtich on gps?
doctor_droid said:
Gps set to always on? Or can device manager swtich on gps?
Click to expand...
Click to collapse
Device manager turns on GPS remotely.