Database Info

Please advise. Captivate issues galore...

Hi all. I just got a Captivate after using Mattc on my HD2 and I used an Aria for a couple weeks as well. I used Mattc on the HD2 for a couple months and really liked it. I understood it was running from the SD and lived with the other issues like slow wake up and occasional goofiness.
So when I got my Captivate I was thinking, wow, I'll have one of(if not the) fastest Android phone on it's native hardware. Everything should rock. I should be blown away... Not.
HELP!
The brightness settings. WTF! Why did they implement like 10 ways the brightness screws with your day. On my HD2 w/Mattc I set the brightness in settings to where I wanted and it stayed. Forever. Also when it hits 10% it kicks the brightness all the way down. 10%? Com on maybe 5%. But what is worse is when it does kick it down I kick it back up but it dims again at every percent it goes down. ANNOYING. Please let me control my phone... Oh and don't get me started on the Browser brightness. Huh? Even with the browser brightness set at max it's still dimmer than my regular brightness setting. Noticably. I only keep my brightness at like 75-80% too.
Also what the hell is with the lame Calendar notification settings? Are there any?
My question is this. Is there any ROM out there that will strip all that Samsung ideology and give me a stock Android experience. Especially without the brightness issues. Why do I need to slide my notification bar to change brightness? All it does for me is just cause my brightness to vary accidentally when I don't want it to.
Why must I add on programs for my Calendar alerts to function normally? Why?
So again. Is there a ROM out there that will strip all the Samsung goofiness? If I can't get this phone to work like I want I'm going to sell it and look for a Telus HTC Desire to use on ATT. HTC phones are the best man. IMHO
Thanks.

juiceppc said:
The brightness settings. WTF! Why did they implement like 10 ways the brightness screws with your day. On my HD2 w/Mattc I set the brightness in settings to where I wanted and it stayed. Forever. Also when it hits 10% it kicks the brightness all the way down. 10%? Com on maybe 5%. But what is worse is when it does kick it down I kick it back up but it dims again at every percent it goes down. ANNOYING. Please let me control my phone... Oh and don't get me started on the Browser brightness. Huh? Even with the browser brightness set at max it's still dimmer than my regular brightness setting. Noticably. I only keep my brightness at like 75-80% too.
Click to expand...
Click to collapse
Turn off auto brightness and pick a setting you like. Done.
Also what the hell is with the lame Calendar notification settings? Are there any?
Click to expand...
Click to collapse
I don't know what lame is, but I use my Google calendar and I can set notifications. I get notified. Is there a specific problem you have?
My question is this. Is there any ROM out there that will strip all that Samsung ideology and give me a stock Android experience. Especially without the brightness issues. Why do I need to slide my notification bar to change brightness? All it does for me is just cause my brightness to vary accidentally when I don't want it to.
Click to expand...
Click to collapse
There is no stock Android experience. Android is just the core - Samsung, HTC, etc, they all add specific things in order for their specific hardware to function. If you don't want what comes on your AT&T Captivate, then you can root and uninstall the apps you don't like, flash one of the many, many cooked ROMs available on this forum (just look around - they are everywhere, and all with great pictures and descriptions and huge threads full of information), tweak settings to your heart's content, or anything else you want to do.
Why must I add on programs for my Calendar alerts to function normally? Why?
Click to expand...
Click to collapse
I don't have any add-ons and I get my alerts. What exactly isn't working for you?

Auto brightness has been off. First thing I do-
I do not get audible alerts when a Calendar reminder goes off-(and there is no where in settings to change/check this)
I had to install "Calendar Snooze" to play an audible alert for a Calendar reminder-
Phone is at 10% now fully dimmed. Nice... Considering how bad the battery life is for this phone(for me) I'll be spending a lot of time with the screen fully dimmed.

juiceppc said:
Auto brightness has been off. First thing I do-
I do not get audible alerts when a Calendar reminder goes off-(and there is no where in settings to change/check this)
I had to install "Calendar Snooze" to play an audible alert for a Calendar reminder-
Phone is at 10% now fully dimmed. Nice... Considering how bad the battery life is for this phone(for me) I'll be spending a lot of time with the screen fully dimmed.
Click to expand...
Click to collapse
Try reading a little and you will see you can set the brightness at where you want it by un-checking the automatic brightness setting..Then you can swipe along the status bar to raise and lower the brightness..It will stay where you had it set IF the automatic brightness is unchecked..Where you have the slider at will be the brightest it will swipe to..
Set your alerts to something you can hear and turn up the volume..They work fine.
Battery life is not a issue provided you follow some advise..Bump charge it 1 time and then use it till it drains down to single digits before recharging...also make sure you back out of all programs and turn off wi-fi and gps and syncing when you don't need them. Loose any task killer program you have and run it stock..you will find your battery life is excellent..if not you may or may not have a bad battery..Lastly..if you are really dissatisfied with it..take it back..
Good Luck
Mac

In regards to the brightness, turn off auto brightness and the 'power saving option.', that should solve your issue.
As far as removing the AT&T bloatware goes, try Unleash the beast.
If you want to run Froyo try flashing a rom, I used the latest version of Cognition.

Run far away from this phone if you still have the chance.

MikeyMike01 said:
Run far away from this phone if you still have the chance.
Click to expand...
Click to collapse
Broad-brush damnations do nothing to help anyone.

Mac11700 said:
Try reading a little and you will see you can set the brightness at where you want it by un-checking the automatic brightness setting..Then you can swipe along the status bar to raise and lower the brightness..It will stay where you had it set IF the automatic brightness is unchecked..Where you have the slider at will be the brightest it will swipe to..
Set your alerts to something you can hear and turn up the volume..They work fine.
Battery life is not a issue provided you follow some advise..Bump charge it 1 time and then use it till it drains down to single digits before recharging...also make sure you back out of all programs and turn off wi-fi and gps and syncing when you don't need them. Loose any task killer program you have and run it stock..you will find your battery life is excellent..if not you may or may not have a bad battery..Lastly..if you are really dissatisfied with it..take it back..
Good Luck
Mac
Click to expand...
Click to collapse
Thanks for the advice. Although I have done all of those things. I'm kind of coming to one real main pain point that I can't seem to solve. The screen dimming at 10%. Does anyone know how to disable that? Even if I kick the brightness back up after it dims at 10% it will redim at 9% and so on...

Bitter. But hopeful.
Picsman said:
Broad-brush damnations do nothing to help anyone.
Click to expand...
Click to collapse
Unfortunately, running away from this phone does seem to be good advise. It doesn't mater how slick it is in theory. Uber display and kickass hardware are useless if the basic functionality suffers due to glitches most of the other options don't seem to exibit.
I decided to play the "mod and wait" game with this thing, and I'm regretting it. Broad-brush damnations would have helped me. At this point, enough issues have came up about this hardware that a "broad-brush" sticky may be warranted. The alert issues found by the OP, may be related to his speaker begining to fail. I had a similar issue. Calander and alarm notifications began failing in some apps, but not others. The phone would still ring. Some apps could still use the speaker. Within a week, nothing could use the speaker, and I had to do the "push-on-it" fix.
It's a forum. Posts are opinions. I've been impressed occasionally by the raw performance of this phone. Yet, I've also spent hours, hours, researching problems, applying fixes, flashing, pushing on the speaker, etc. And I've spent hours "waiting" for the thing to do something simple like send an email when it did fine the day before. With as much time and effort as I've put into researching and working on this phone, I feel like I (and others) have not gotten enough stability out of it.
I propose a broad brush damnation for this phone: "slick but intermittent".

fshalor said:
Unfortunately, running away from this phone does seem to be good advise. It doesn't mater how slick it is in theory. Uber display and kickass hardware are useless if the basic functionality suffers due to glitches most of the other options don't seem to exibit.
I decided to play the "mod and wait" game with this thing, and I'm regretting it. Broad-brush damnations would have helped me. At this point, enough issues have came up about this hardware that a "broad-brush" sticky may be warranted. The alert issues found by the OP, may be related to his speaker begining to fail. I had a similar issue. Calander and alarm notifications began failing in some apps, but not others. The phone would still ring. Some apps could still use the speaker. Within a week, nothing could use the speaker, and I had to do the "push-on-it" fix.
It's a forum. Posts are opinions. I've been impressed occasionally by the raw performance of this phone. Yet, I've also spent hours, hours, researching problems, applying fixes, flashing, pushing on the speaker, etc. And I've spent hours "waiting" for the thing to do something simple like send an email when it did fine the day before. With as much time and effort as I've put into researching and working on this phone, I feel like I (and others) have not gotten enough stability out of it.
I propose a broad brush damnation for this phone: "slick but intermittent".
Click to expand...
Click to collapse
haha. Thanks for the ,.. opinion. I'm starting to feel the same way about this phone. I had super high hopes. But I'm really going to stick with HTC. They just get it. IMHO.

I think most people regret buying this phone. Or they will, when FroYo never arrives, the lag gets worse and worse, the phone dies on them, and the GPS never come close to working, the market decides not to intall your app, this, that, or the other thing force closes, etc. etc. etc.

MikeyMike01 said:
I think most people regret buying this phone. Or they will, when FroYo never arrives, the lag gets worse and worse, the phone dies on them, and the GPS never come close to working, the market decides not to intall your app, this, that, or the other thing force closes, etc. etc. etc.
Click to expand...
Click to collapse
Umm froyo is already leaked and OTA is on its way.
Lag has never been an issue.
And GPS is a software fix... proven on these boards over and over.
SHEESH... I'd say go tell somewhere else.
Sent from my SAMSUNG-SGH-I897 using XDA App

yeah, 5 million people are completely dissatisfied because one guy managed to not know how to operate his phone.....

MikeyMike01 said:
I think most people regret buying this phone. Or they will, when FroYo never arrives, the lag gets worse and worse, the phone dies on them, and the GPS never come close to working, the market decides not to intall your app, this, that, or the other thing force closes, etc. etc. etc.
Click to expand...
Click to collapse
I think your wrong. I think quite a few people got defective phones and haven't bothered returning them,thinking that if they root it and flash a different rom that would magically fix a broken phone. This is XDA and folks here mostly do this..thus the reason for most of the complaints. Problem is..it won't change much of anything to reflash if the phone is defective..If it is broken to begin with..it will be broken no matter what you do to it.. If yours is defective..quite *****ing about it and get one that isn't..or a different phone entirely. The working ones are great..just like they are supposed to be.
I have 2 of them built in September..both work and neither is defective.This tells me many of those built prior have some issues..perhaps not all of them..but some of them certainly. This certainly doesn't make it right by anyones account..just saying if yours is defective..return it and get one that isn't.
I honestly don't understand people who have the option of doing this,not doing it.The folks at my AT&T store opened 7 different boxes and checked every one of them for any blue tint on the screen and having the 3 button recovery option..for my second one bought at the same time,so I do know there are many out there that ain't working properly..The OP of this thread..is unhappy with it..damn..loose it and be done with it if you are that unhappy..or take that one back and get them to open up the boxes and show you one that works properly...If it was bought mail order..then you should just return it as defective and get your money back..and buy where you can see it first..It's your choice...and your money.
Mac

haptiClock get the time by tapping your phone

haptiClock vibrates you the time (haptic feedback) if you shake/bump/tap your phone. It works when your screen is off, doesn't use much battery. The pattern to decipher the time from the pulses is simple to learn.
Great for checking the time on the sly, or when you can't pull your phone out.
Free version for trial then limited, and then paid for full version. Send me feedback, I want to make this a useful app! QR code at ... well as a total newb here I can't post links even a barcode, but lookitup!
-Phil

Permission: Prevent phone from sleeping
Makes me very nervous about battery life.
Otherwise, very interesting idea, and I'll check it out.
EDIT: I'm getting constant force-closes just reading the tutorial. Galaxy S phone (Android 2.1)

"I'm getting constant force-closes just reading the tutorial. Galaxy S phone (Android 2.1) "
Wow thanks for the info, I'll look into it... been tested on Droid, Droid X, Nexus
edit:<strike>The battery use isn't as bad as I thought it would be</strike>!
apparently it is using more juice than I had seen during beta testing
Android is really challenging- lots of hardware (IMO this is a good thing) and versions make testing unreliable...

Version 1.1 just uploaded should fix problem Izkata had... THANKS FOR THE INFO!

Just a quick test this morning, and it does appear to be fixed.
I'll test it more thoroughly later today.

I just downloaded the free version of this and it looks really promising.
While the screen was on and the app still open it worked perfectly, but when I turned the screen off and activated it again, it did hours fine and the rounded min fine, but the 2nd activation didn't work.

OK, noted ADeadlySpoon... thanks.
There is a time window to second tap to get the exact minutes, it's 10 seconds, you can also just go into "one tap" mode and time to exact minute every time. Still, I'll try to re-create your issue.

Wont work if screen is off.. on my EVO

drummer2780 said:
Wont work if screen is off.. on my EVO
Click to expand...
Click to collapse
Same with Desire HD which makes it useless for me atm.
But it's a nice App, hope this will work soon.

Okay, so - I left it running with the screen off and phone unused for about an hour and a half, to check the battery usage.
(Phone: Samsung Captivate (Galaxy S on ATT))
Normally, on average, I lose just under 1% per hour when the phone is not in use. With haptiClock active, I lost right around 1% per 10 minutes, while the phone was not in use. So the drop isn't as bad as I was expecting (yay!), but it's not something I'd leave on all the time, either.
No force-closes, ether, so the fix earlier seems to have fixed it entirely.
I have a habit of discreet time-checking, so this'll be great. Best trigger for me seems to be about 13 or 14 - juuust enough that I don't have to whack my phone/make an obvious movement to trigger it.

I have to change the language on the help, because when it did appear in my battery use stats it was always about the same as Cell Standby, which didn't seem to make sense, I should have grabbed Izkata's app (and will now) to check battery usage. It is important to turn off when you don't anticipate needing it.
On the Desire HD & EVO, I have no idea why ATM, but will look into it over the next 24hrs. I did test it on an HTC myTouch 3G and it worked.
If either of you get a chance, could you post OS version / API level and any mods?
Thanks for checking it out.
-Phil

upperTriangle said:
I have to change the language on the help, because when it did appear in my battery use stats it was always about the same as Cell Standby, which didn't seem to make sense, I should have grabbed Izkata's app (and will now) to check battery usage. It is important to turn off when you don't anticipate needing it.
Click to expand...
Click to collapse
Yey, thanks
It's not the best thing for measuring usage like this, though. To get the numbers in my previous post, I just recorded the percent before and after, and manually divided. 'Tho you can see in the History graph when it drops faster, so that helps.
upperTriangle said:
If either of you get a chance, could you post OS version / API level and any mods?
Click to expand...
Click to collapse
Android 2.1-update1 / API 7, rooted, but with no mods.

When screen is on, it works alright. But when screen turned off, no response from the app. Great idea though. I'm using a wildfire btw..

To those of you for whom the app doesn't work when the screen is off, this is an Android bug affecting certain phones. I believe it is a problem (be it a feature whereby the manufacturer is trying improve battery usage profile, or a bug) with the firmware. The HTC phones with Sense UI seem to be among the more commonly afflicted devices.
I remember seeing this bug report I started working on the app:
http://code.google.com/p/android/issues/detail?id=3708
BUT by the time it was getting close to done, my impression was that this had basically been fixed, and I didn't mention it anywhere in the release, none of the phones I tested on had this problem.
Now, there is another newer Android bug report regarding this issue, please STAR it (upper left of page)
http://code.google.com/p/android/issues/detail?id=11028
and hopefully we will see more rapid resolution of this issue, I think the OS isn't the problem, but perhaps manufacturer firmware updates could help resolve it.
Please don't leave negative comments on the Market if the app doesn't work with the screen off. Because of users doing this (which I should have seen coming) my star rating is started to go down. I have included language on the Market entry which should prevent people from giving the app a low rating solely because of this issue.
Lastly, there is a workaround of sorts for this which will fix the problem on some phones. I will implement it, but am going to proceed very cautiously, because last thing I want to do is break the app for users for whom it is currently functioning appropriately.
As such, I would really appreciate it if people who are experiencing this issue would beta test a new release with the workaround prior to my releasing it on the market.
So drummer2780,Testuser_01,thunderskain, ADeadlySpoon(?) ... if any of you would be so kind as to receive an APK file from me for testing on your device, in return I'll try to somehow get you the full version gratis of course (how we'll do that I'm not sure as I don't want an APK with licensing disabled floating around out there!, perhaps you can buy it from the Market and I'll refund the payment)
Izkata, for your help I'd like to do the same (give you free version) so if you buy it I will refund. I don't *think* a refund will invalidate the licensing, but I'm not sure, it is unclear from the Google distribution agreement language.
Thanks for checking out my app, I'm hoping people are finding it useful!

Izkata said:
Best trigger for me seems to be about 13 or 14 - juuust enough that I don't have to whack my phone/make an obvious movement to trigger it.
Click to expand...
Click to collapse
Since you are using it at a pretty sensitive setting:
Go to settings->overall sensitivity and select "Make more sensitive" and you'll find you can be a little more in the middle of the range and will have better precision for where you'd like the trigger to be, of course set it back if you want to use it and you're being more active.
-Phil

upperTriangle said:
So drummer2780,Testuser_01,thunderskain, ADeadlySpoon(?) ... if any of you would be so kind as to receive an APK file from me for testing on your device, in return I'll try to somehow get you the full version gratis of course (how we'll do that I'm not sure as I don't want an APK with licensing disabled floating around out there!, perhaps you can buy it from the Market and I'll refund the payment)
Izkata, for your help I'd like to do the same (give you free version) so if you buy it I will refund. I don't *think* a refund will invalidate the licensing, but I'm not sure, it is unclear from the Google distribution agreement language.
Click to expand...
Click to collapse
Since we both have a paid version of an app out, we could just do a "trade" and buy each others' apps, assuming you haven't already. The difference in pricing is small enough that I wouldn't really worry about it. Or we could try out the refund idea, then have experience to advise others in the future (I haven't bought haptiClock yet, and might not for a while - various stuff going on IRL)
upperTriangle said:
Go to settings->overall sensitivity and select "Make more sensitive" and you'll find you can be a little more in the middle of the range and will have better precision for where you'd like the trigger to be, of course set it back if you want to use it and you're being more active.
Click to expand...
Click to collapse
I'll take another look at the setting(s) eventually, and try and remember to post my comparisons in this thread once I do. (However, I'm starting a new job this week and don't want to mess with stuff/might not have time to mess with stuff until next weekend)

Great app! I've been looking for an app that did this for a really long time.
I was thinking though. The vibrate system's a little confusing, and I don't really need to know the exact time. Usually I only need to know it to the closest 15 minutes. Perhaps you could set toggles for the 10/15 minute vibe, the 5 minute vibe, and the 1 minute vibe?

SamUserInterface said:
Uually I only need to know it to the closest 15 minutes. Perhaps you could set toggles for the 10/15 minute vibe, the 5 minute vibe, and the 1 minute vibe?
Click to expand...
Click to collapse
There is a setting which allows you to only receive the 10/15 vibe (at least it requires an add'l tap to get the exact minute)... but I do like your idea of being able to specifically set where to stop. It would be a fairly extensive task for me to implement, as I basically have it set up to do just to the minute, or require add'l tap. We'll see how it goes, I can't say I'm going to be spending a bunch more time on this thing unless it attracts more users.
Thanks for the feedback!

Doesn't work with the screen off on the dell streak running dj steves 1.6.0 froyo ROM. Would definetly be interested in buying when (if) it can.

Well, it looks like all workarounds I've tried for phones which don't respond to the sensor when the screen is off (in standby mode) have failed. This is likely a firmware issue which ought to be addressed by the manufacturer. The code should run the same on all devices, this is the point of Android!
Given that it works on most phones, it is a "bug" or "defect".
Please take a moment to star the issue at code.google:
Issue 11028
Also, contact your phones manufacturer rolleyes: HTC) regarding this issue.
I think there are lots of possibilities here and hopefully it will get fixed because there are similar apps I'm creating which rely on the accelerometer working in standby as I've implemented in haptiClock.
Thanks
Phil

[Q] App that tells time when asked

I'm rather near sighted so unless I duct tape the alarm clock to my head I have no chance in hell to actually see the numbers displayed on it at night without contacts or glasses. I've been looking around for app that does one simple thing: tell me the time when i say "time" (or something similar).
My search so far has come up mostly short. I found an app that tells me the time when I shake, touch, or wave my hand over the device. There are also half a million bad Siri knockoffs that will tell me the time if I push a button. However what I really want is an app that monitors audio the entire night and doesn't need to be prodded in any way to notice me speaking to it.
There has to be something out there that can do this. I mean, the built in voice thing responds to "hi galaxy" which could in theory work if it would just understand when I ask it for the time. There are also sleep recorders and such apps that obviously don't mind monitoring audio all night long, as long as you plug it in so power isn't an issue.
Does anyone have any ideas for such an app?
EDIT: If I'm to be very feature-greedy I also wouldn't mind if it turned on the LED when I say "lights" or something like that, but I imagine that's more than just a little bit unlikly to exist
EDIT2: Forgot I was in a general part of the forum, so just to be clear, will be using this on a galaxy s ii or galaxy tab 7.0 plus

The device doesn't really matter, such app should run on any device.
I like the idea!
I will give it a shot after my exam on thursday, but no promises , already have some cool ideas .
You should be aware that this is not battery efficient at all and if your phone is not connected to a charger it might run empty during the night.

Dark3n said:
You should be aware that this is not battery efficient at all and if your phone is not connected to a charger it might run empty during the night.
Click to expand...
Click to collapse
Of course, as I said that's what sleep talk monitors require too.
I did actually find something...on my iPad. There are a couple of apps like that on iOS. I ended up with one where you simply clap to hear the time. Hasn't been updated in ages but still works. There's another one that you actually say "time" to but I think you need to say its name to wake it up first, so didn't even try that one.
Would definitely prefer to have it on Android though, so would be awesome f you got something working
EDIT: decided to buy the other app for iOS just to make a video as a reference:
http://www.youtube.com/watch?v=uXgS0aW10v8
Seems that development simply stopped on that one. Not been updated in ages. Having to say "hello kei" every time is indeed annoying

Spent my first night with the clap activated clock on the iPad. Wow, this truly makes a world of difference to someone like me who's practically blind without glasses or contacts. Ended up waking up a few times during the night, especially close to the time to get up, so being able to get the time without fumbling around for glasses and actually waking up in the process literally made it easier to sleep too

Horrible Battery Life

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

Battery discharge while on charger

Using CM11 snapshot january update
I woke up late last night to see my phone still with the yellow charging light on while it was on the charger. i found that odd since it had been on the charger for almost 4 hours. i went to bed with it at 75% and when i went to the battery page it was at 50%. wierd thing is the graph says "3hr and 50 min on battery" but the line graph shows that its is, in fact, charging. another thing ive noticed is that the wifi line graph is solid, im not 100% sure its supposed to be intermittent, i.e. phone is sleeping and what not.
once i noticed that it was still discharging i looked at running apps, nothing outside what anyone else would have running at the end of the night. after i cleared the running apps it started charging again.
i know that i may have answered my own question at the end of the second paragraph but chargers put out more power than a phone can consume while being dormant so im trying to isolate a handful of things.
1. is the wifi line graph supposed to be solid all the time? (I didnt think so but)
2. is the rom im using (cm11 snapshot current update) on an outdated kernel?
3. whatever else that can brainstormed
and before i get a but of wrong forum reply's, i dont have a choice i need my 10 reply's to get this into the correct forum..... unless admin moves it into a developer forum....eh...eh?
thanks for any help you guys can provide.

Justyn86 said:
Using CM11 snapshot january update
I woke up late last night to see my phone still with the yellow charging light on while it was on the charger. i found that odd since it had been on the charger for almost 4 hours. i went to bed with it at 75% and when i went to the battery page it was at 50%. wierd thing is the graph says "3hr and 50 min on battery" but the line graph shows that its is, in fact, charging. another thing ive noticed is that the wifi line graph is solid, im not 100% sure its supposed to be intermittent, i.e. phone is sleeping and what not.
once i noticed that it was still discharging i looked at running apps, nothing outside what anyone else would have running at the end of the night. after i cleared the running apps it started charging again.
i know that i may have answered my own question at the end of the second paragraph but chargers put out more power than a phone can consume while being dormant so im trying to isolate a handful of things.
1. is the wifi line graph supposed to be solid all the time? (I didnt think so but)
2. is the rom im using (cm11 snapshot current update) on an outdated kernel?
3. whatever else that can brainstormed
and before i get a but of wrong forum reply's, i dont have a choice i need my 10 reply's to get this into the correct forum..... unless admin moves it into a developer forum....eh...eh?
thanks for any help you guys can provide.
Click to expand...
Click to collapse
forgot..

solid wifi line.. go to the phones main settings, wifi, wifi settings(3 dots bottom right), advanced, disable scanning always available.
cm uses cm kernel. outdated is when a kernel is no longer good, a lower kernel number doesnt mean anything.
and this kind of post have no business being in development, no mod would ever even consider moving it there. development is for development, not questions that are very basic. you actually got the right forum.

Weird. As Sims said turn wifi scanning to off.
It could be a nightly issue with CM at the current moment, check there.
PS: There are other ROMs than just buying a phone and throwing cyanogen mod on it.

Good deal. Thanks guys.
I know I could put any ROM on a phone I used to have an s4 and did several ROMs with that. Then I had to send it in and they gave me one that was mf3 and I was just tired of jumping through hoops. But I put cm on mine because I getting away from full service and using strictly Google voice on a data only plan for cheaper service (Att is the best service overall where i am but their no contract sucks), and cm, so far, is the only one that has voice plus to integrate gv SMS into you native SMS app. That's my big thing. But if there's other ROMs at utilize voice+ I'm open to them.

I'm going to be of no help to you, but just to let you know, this is the correct forum. Nothing except something that you developed goes in development. Nothing. Questions and all other random things go in either Q&A or General.

I don't see you mention which charger you used. Wired? Stock charger and cable? The WiFi bar will be solid over night with your WiFi on and never intermittent.
Sent from my Nexus 5 using Tapatalk

Yea after I was told to look at the WiFi settings, I changed some settings. But yes Its wired. I played around with the cable and it wiggles a bit but I didn't notice it disconnecting but I'll do More investigating on that front over the next few days.
Sent from my Nexus 5 using Tapatalk

Justyn86 said:
Yea after I was told to look at the WiFi settings, I changed some settings. But yes Its wired. I played around with the cable and it wiggles a bit but I didn't notice it disconnecting but I'll do More investigating on that front over the next few days.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Wiggle won't effect charge speed. Using a different adapter or cable then what came with your phone will effect charging speed however as well as the phone's current draw.

Well yea right. What I meant to say was that I may not be getting a solid connection, and if I had it sitting a certain way, it may not be charging at all, making appear as though the battery was draining "while charging" when it actually wasn't even charging. My biggest thing was that this is the first I've noticed it so. Maybe the cable is just crappy and is giving out. ( not the OE cable)
Sent from my Nexus 5 using Tapatalk

Justyn86 said:
Well yea right. What I meant to say was that I may not be getting a solid connection, and if I had it sitting a certain way, it may not be charging at all, making appear as though the battery was draining "while charging" when it actually wasn't even charging. My biggest thing was that this is the first I've noticed it so. Maybe the cable is just crappy and is giving out. ( not the OE cable)
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Most likely it's just the cable then. You may be interested in the contents of this thread including a quick comparison video Bacon made.
http://forum.xda-developers.com/showthread.php?t=2609087
http://www.youtube.com/watch?v=wGYkt4CeYuk&feature=youtu.be

Wow that's pretty impressive makes me want to get Motorola cable
Sent from my Nexus 5 using Tapatalk

Turns out a combo of things. One being the cable with now power output. And the other was just being a cheap cable and was fitting in the port loosely and not maintaining a connection all the time. Thanks for the help.
Sent from my Nexus 5 using Tapatalk