Related
I would really appreciate any suggestion in regard to this topic. I have a Tmous HD2 that is still under warranty with T-Mobile. I need to return the device back for a replacement as two out of three of the metal pieces in the back where it touches the battery are badly bent out of shape and they seem as if they can jz break off anytime. I guess this is the result of playing with different roms and having to take the battery out for resets
My question is .. what is the best way to restore it back to factory rom/radio? I have hspl3 and upgraded radio to 2.15 and I later also have mgldr 1.13 installed as well. Can someone please tell me how I can find/flash a stock rom/radio and wipe out all that stuffs to return it? I remember seeing a thread on this topic a while back but couldn't find it now.
Again, any help or suggestions are greatly appreciated .. thanks guys!!!
Sent from my HTC HD2 using XDA App
Go to the TMo site, find the HD2, there there'll be a tab with 'downloads'. Then just download the stock ROM from there and flash it from HSPL from the RUU.
And once its flashed run hspl.exe and choose 2.08.0000 or 2.10.0000 since the above post, whilst correct, wont remove hspl.
Or, flash the rom from SD card to restore everything Inc. Spl to stock.
samsamuel said:
And once its flashed run hspl.exe and choose 2.08.0000 or 2.10.0000 since the above post, whilst correct, wont remove hspl.
Or, flash the rom from SD card to restore everything Inc. Spl to stock.
Click to expand...
Click to collapse
Sam! You're always correcting me, stop it! haha.
This might be a silly question but what you are referring to as 2.08 and 2.10 is the radio right? So jz the stock rom then radio? And thanks a lot for the fast respond guys .. I love the spirit of this community
samsamuel said:
And once its flashed run hspl.exe and choose 2.08.0000 or 2.10.0000 since the above post, whilst correct, wont remove hspl.
Or, flash the rom from SD card to restore everything Inc. Spl to stock.
Click to expand...
Click to collapse
Sent from my HTC HD2 using XDA App
an easier way
flash the stock ROM you got from HTC via SD, that way it overwrites HSPL with the correct SPL and flashes the correct radio that came with your phone.
You really don't want to end up like this guy:http://forum.xda-developers.com/showthread.php?t=1025001
so make sure you are good to go before sending it in.
qdochemistry said:
I need to return the device back for a replacement as two out of three of the metal pieces in the back where it touches the battery are badly bent out of shape and they seem as if they can jz break off anytime. I guess this is the result of playing with different roms and having to take the battery out for resets
Click to expand...
Click to collapse
I am not trying to be a wise ass here, but I really do not understand people always wanting to do a battery pull to do a soft reset of their HD2. It has a soft reset button on the back under the battery cover. Now I am no Enstien or Sir Isak Newton but the designers of the HD2 had tro have included this for a reason. I think the reason was to be able to reset the device without doing a battery pull as the pins for the battery on the HD2 are some what delicate. Doing a battery pull not only puts more ware and tear on the battery pins, but the abrupt loss of power is some what detrimental to the performance of the device as well. You see the devices software has protocols that it goes through to shut down just like the IPL of bootloader initializes all the hardware on boot it has to up shut everything down. When you do a battery pull the hardware that did not get de initialized at shut down may have problems initialized on start up, this leads to one having to do a hard reset and thinking the device is crap or the ROM is crap. When actually it is kinda their own doing that has messed the performance of the device up. I mean the hardware and software have to be functioning correctly together for the device to perform at expected levels.
Thanks for the heads up .. imma read up on it before trying cuz I haven't flash by SD before
Sent from my HTC HD2 using XDA App
http://shipped-roms.com/index.php?category=windows mobile&model=Leo
maybe there is your ROM
I have two HD2 and the other one is for my wife .. when you are on the go or on an important phone call and it freezes on you (happens a lot back then with the early days of winnow roms and beta android) its jz convenient to reset by pulling battery cuz I don't carry anything on me specifically that fits the tiny button. As far as performance goes, both devices are running rock solid regardless of the battery pulls.
When I do test a rom and experience problems I simply report back to the chef hoping there will be a fix .. and if I am the only person experiencing it then it is something on my part. However, that has never been the case!
As for your comment, I definitely agree with everyone in this forum that HD2 is the most flexible device to date. Since we didn't want to be bound to the additional 50/mth data plan contract for both devices we bought them at retail price. Even with that price .. and even if both of them malfunction at this point, I have no regret about my decision! We had so much fun playing with this phone and we are proud owners of HD2.
I created this thread as it was unfortunate that one of them has its pin coming loose and I need to seek help from the community. Thanks again .. to those members that pointed me in the right direction.
For the record, I'm also NOT Einstein or Newton .. but I am a PhD chemist. I wont say that you are being a wise ass .. but I think your comment is harsh and irrelevant!
T-Macgnolia said:
I am not trying to be a wise ass here, but I really do not understand people always wanting to do a battery pull to do a soft reset of their HD2. It has a soft reset button on the back under the battery cover. Now I am no Enstien or Sir Isak Newton but the designers of the HD2 had tro have included this for a reason. I think the reason was to be able to reset the device without doing a battery pull as the pins for the battery on the HD2 are some what delicate. Doing a battery pull not only puts more ware and tear on the battery pins, but the abrupt loss of power is some what detrimental to the performance of the device as well. You see the devices software has protocols that it goes through to shut down just like the IPL of bootloader initializes all the hardware on boot it has to up shut everything down. When you do a battery pull the hardware that did not get de initialized at shut down may have problems initialized on start up, this leads to one having to do a hard reset and thinking the device is crap or the ROM is crap. When actually it is kinda their own doing that has messed the performance of the device up. I mean the hardware and software have to be functioning correctly together for the device to perform at expected levels.
Click to expand...
Click to collapse
Sent from my HTC HD2 using XDA App
Awesome!! I'll look thru those .... thanks
birdra said:
http://shipped-roms.com/index.php?category=windows mobile&model=Leo
maybe there is your ROM
Click to expand...
Click to collapse
Sent from my HTC HD2 using XDA App
qdochemistry said:
For the record, I'm also NOT Einstein or Newton .. but I am a PhD chemist. I wont say that you are being a wise ass .. but I think your comment is harsh and irrelevant!
Click to expand...
Click to collapse
I am truly sorry you feel this way about my comments as they were truly not meant that way. I just felt it was needed to further point out the cause of your problem as so many have suffered the same problem as you. I have seen plenty with your problem here in the forums. Even you yourself admited it was a problem of your own making. I do not carry something around to push the rset button with either but I am a firm believer in using the reset button and not doing a battery pull.
I am glad you and your wife have not experienced any bad side effects off doing a battery pull. But when I first got my HD2 8 months ago I was doing battery pull after battery pull and the more I pulled the battery the worse my HD2 got. It would freeze one the orange Windows splash screen at least 10 times in a row, I tried hard reset after hard reset and no joy. So I got a replacement HD2 sent to me and I have not done one battery pullthe whole 5 and a half months I have had it. I am running Android on it now but that has only been for a little over a week. ran stock ROM on it until now besides testing several custom ROMs out for a couple of hours to a day. I hardly had any lock up or freeze issues the whole time.
I hope you get your problem fixed, but please just take my words into consideration.
Thanks for sharing the experience .. afterall it is what the xda community is about
T-Macgnolia said:
I hope you get your problem fixed, but please just take my words into consideration.
Click to expand...
Click to collapse
Sent from my HTC HD2 using XDA App
T-Macgnolia said:
I am truly sorry you feel this way about my comments as they were truly not meant that way. I just felt it was needed to further point out the cause of your problem as so many have suffered the same problem as you. I have seen plenty with your problem here in the forums. Even you yourself admited it was a problem of your own making. I do not carry something around to push the rset button with either but I am a firm believer in using the reset button and not doing a battery pull.
I am glad you and your wife have not experienced any bad side effects off doing a battery pull. But when I first got my HD2 8 months ago I was doing battery pull after battery pull and the more I pulled the battery the worse my HD2 got. It would freeze one the orange Windows splash screen at least 10 times in a row, I tried hard reset after hard reset and no joy. So I got a replacement HD2 sent to me and I have not done one battery pullthe whole 5 and a half months I have had it. I am running Android on it now but that has only been for a little over a week. ran stock ROM on it until now besides testing several custom ROMs out for a couple of hours to a day. I hardly had any lock up or freeze issues the whole time.
I hope you get your problem fixed, but please just take my words into consideration.
Click to expand...
Click to collapse
I am of the same opinion with you.
In the past, I frequently flashed my Leo and used to remove the battery for easy and fast hard reset. I just followed the instruction in the relevant threads without thinking that it might damage the NAND.
I experienced many freezes but I just ignored it until the time when I cannot flash NAND Android anymore and I found it so many badblocks in the NAND.
Luckily, I still can go back to Winmo. Although, some custom roms still cause freezing. But, with Athine OS (check my sig) I never experience freeze so far, and I still can use Android via SD Card.
Cheers...
After a week of awesome usage with these two items......... I'm *****ing up a storm to a co worker.
I looked at the phone before I made the call 32% battery life.
less than 5 mins later I get the battery low warning beeps, phone drops the call and reboots, STUCK on loading screen.
Phone is FARKED at this point.
In order for me not to throw it through a window I put it away in a drawer and will check it out tomorrow at some point.
Just a warning.
Odd, but I assure you, the ROM has nothing to do with it. Nor, neccesarily, does the kernel!
Try turning it off, booting into CWM and resetting the battery stats.
J3ff said:
After a week of awesome usage with these two items......... I'm *****ing up a storm to a co worker.
I looked at the phone before I made the call 32% battery life.
less than 5 mins later I get the battery low warning beeps, phone drops the call and reboots, STUCK on loading screen.
Phone is FARKED at this point.
In order for me not to throw it through a window I put it away in a drawer and will check it out tomorrow at some point.
Just a warning.
Click to expand...
Click to collapse
So? Just restore your last backup and you should be fine, assuming you make frequent backups as are very highly suggested by ACS and Rodderick, especially in Rodderick's kernel, which he says has decent chance of causing data corruption needing a restore.
Yeah. Its happened to me a bit as well. Usually a battery pull fixes it. But at least if you can get cwm up you can reflash.
cd's or tapes?
Running the same combo and no problems here.
Sent From My Evo Killer!
mis3 said:
So? Just restore your last backup and you should be fine, assuming you make frequent backups as are very highly suggested by ACS and Rodderick, especially in Rodderick's kernel, which he says has decent chance of causing data corruption needing a restore.
Click to expand...
Click to collapse
Its not just a suggestion, its common sense. If your to lazy or don't have time to make a 10 minute backup, then flashing roms and kernels should be the last thing on your mind.
Rule number one after rooting should be; boot into clockwork, make a backup and then wipe 3x and restore it. We would never see posts like the op, I do hope he made a backup tho
why is this even a thread? Isnt this the norm when playing with roms and kernels? After flashing a jillion times, found out certain phones dont like certain kernels and roms.
http://www.sdx-developers.com/sdx/the-truth-behind-battery-re-calibration/
So it seems like your battery isn’t lasting very long. You search the Forum at SDX Developers and hear about this thing called “Battery Re-Calibration” and how its supposed to be great for increasing your battery life. Well, sorry to burst your bubble, but the guides for “Battery Calibration” lead you through some steps that actually do more harm than good!
And here’s the reason why:
The batteries in your mobile forms are high-capacity lithium-ion batteries. This kind of battery technology cannot be simply reset and “re-calibrated.” When you follow the steps to recalibrate your battery and delete the batterystats.bin file from your phone, you are getting rid of more than what you think… Stored inside that batterystats.bin file, your phone keeps detailed logs of the capacity of your battery and uses it on how it can be utilized more efficiently. By deleting this file, it basically wipes the phone’s memory on what the battery can really do. This actually does damage to your battery by using up valuable charging cycles, all while giving a fraction of battery life and performance.
Now, you might be saying uh-oh, I’ve already re-calibrated my battery! What do I do?!
Well here’s your answer. Use your phone like normal. Yes, your battery and phone wont perform as good as it can for a while, but after a few days, you will notice that it starts doing better and better. Give it time, its trying to rebuild all those logs that you just deleted
I hope this helps and clears up this argument once and for all!
Figured as much...
I've always had horrible life after deleting battery stats.
- Ron
What happens to the stats and how they are used if I use multiple batteries?
Sent from my Transformer TF101 using XDA Premium App
I would've thought that after flashing a new rom, this would be better, cuz then the phone wouldn't think it has less power than it has
nebrando said:
What happens to the stats and how they are used if I use multiple batteries?
Sent from my Transformer TF101 using XDA Premium App
Click to expand...
Click to collapse
I'm wondering the same thing. I usually have a spare battery and swap them out
Sent from my SPH-D700 using XDA App
nebrando said:
What happens to the stats and how they are used if I use multiple batteries?
Sent from my Transformer TF101 using XDA Premium App
Click to expand...
Click to collapse
Smarter batteries expose information (ie: serial number) to the device they power. Then again smarter batteries also store the charge history/life experience/charge cycle logs on the battery themselves. No clue what our batteries are capable of.
xboxfanj said:
I would've thought that after flashing a new rom, this would be better, cuz then the phone wouldn't think it has less power than it has
Click to expand...
Click to collapse
Considering the fact that flashing often overwrites all system files (depending on what you're flashing), and an Odin flash completely overwrites *almost* everything (device programming is retained, you'll notice that you do
NOT need to redo the cellular network setup each time), out stands to reason that that file may get deleted through several other processes in addition to wiping the stats. So I would say that this isn't as bad as the OP makes it sound.
And if you experience any sort of file corruption, the battery stats file could be affected; I don't care who you ask, no data is far better than bad data any day of the week
Sent from my SPH-D700 using XDA App
My rule of thumb was to wipe stats when ever I had a kernel change. From what iv read around xda, performing a wipe was to let your phone adjust to the new software and reteach its self how to use the battery. I never see any harm in it besides crappy battery life the frst couple of days.
Sent from my epic
sprkat85 said:
My rule of thumb was to wipe stats when ever I had a kernel change. From what iv read around xda, performing a wipe was to let your phone adjust to the new software and reteach its self how to use the battery. I never see any harm in it besides crappy battery life the frst couple of days.
Sent from my epic
Click to expand...
Click to collapse
You're essentially correct, the existing stats are based on the system configuration in place when the stats were recorded, so the data may not be as helpful as intended after changing components of the operating system such as the kernel.
Sent from my SPH-D700 using XDA App
styles420 said:
You're essentially correct, the existing stats are based on the system configuration in place when the stats were recorded, so the data may not be as helpful as intended after changing components of the operating system such as the kernel.
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
Where can I find info on what data fields are in batterystats.bin?
Considering the fact that I always get substantially better battery life when I flash a new ROM, and then wipe battery info, vs flashing a new rom and never wiping, I think this post isn't necessarily accurate.
If I flash a new rom, and DON'T wipe battery, I'm always disappointed with the battery life for several days before I remember to charge all the way and wipe stats. I've never had a situation where I get poor life by doing the standard flash+wipe combo. I can see the downside of doing a full-on calibration (bump charging several times, then wiping, for no reason) but my personal experience disagrees with the overall post.
You don't just wipe battery stats and call it a day. You charge your phone to 100%, wipe battery stats, and then run the phone down to nothing. So now the ONLY information stored in the battery stats file should be the absolute full charge of the battery from 100% until the phone literally turns off because of low voltage. How is that not more efficient?
muyoso said:
You don't just wipe battery stats and call it a day. You charge your phone to 100%, wipe battery stats, and then run the phone down to nothing. So now the ONLY information stored in the battery stats file should be the absolute full charge of the battery from 100% until the phone literally turns off because of low voltage. How is that not more efficient?
Click to expand...
Click to collapse
Because as far as I can tell it's just conjecture... Don't get me wrong, not saying anyone hasn't observed what they think they have but this sounds simple to solve to me if two questions are answered:
1) What data is stored in batterystats.bin (correct filename?)
2) How does the Android OS use this data file related to charging/displayed remaining/etc
These are answerable questions but I haven't seen them answered (not searching hard). Until they are we can all assume whatever we want based on our observations but what we see often has little to do with fact.
From what I've read in the OP, it's exactly why I wipe the stats. Yes they will have to figure themselves out but just as they do when I wipe my Market cache to avoid force closes. Bad files are bad files and if people want to clear and rebuild them, it certainly doesn't make it a bad process.
muyoso said:
You don't just wipe battery stats and call it a day. You charge your phone to 100%, wipe battery stats, and then run the phone down to nothing. So now the ONLY information stored in the battery stats file should be the absolute full charge of the battery from 100% until the phone literally turns off because of low voltage. How is that not more efficient?
Click to expand...
Click to collapse
Everytime I wipe battery stats, it always starts reading my battery % wrong. One sec it'll say I'm at 90%, the next at 92. The only fix is to flash a new ROM.
machx0r said:
Because as far as I can tell it's just conjecture... Don't get me wrong, not saying anyone hasn't observed what they think they have but this sounds simple to solve to me if two questions are answered:
1) What data is stored in batterystats.bin (correct filename?)
2) How does the Android OS use this data file related to charging/displayed remaining/etc
These are answerable questions but I haven't seen them answered (not searching hard). Until they are we can all assume whatever we want based on our observations but what we see often has little to do with fact.
Click to expand...
Click to collapse
Would you install a sound system, tune it perfectly for the acoustics in your living room, and then expect that same tuning to work just as well in any other room in your house?
When you change to a new room and/or kernel, you completely change the environment in which the battery is operating. It makes no sense whatsoever to assume that the battery would run better with data that is irrelevant to the current setup than it would with a clean slate
Edit: another point to consider - the battery had to start at a clean slate when it was manufactured - is the OP suggesting that this is bad for the battery? What sense would that make?
Sent from my SPH-D700 using XDA App
styles420 said:
Would you install a sound system, tune it perfectly for the acoustics in your living room, and then expect that same tuning to work just as well in any other room in your house?
When you change to a new room and/or kernel, you completely change the environment in which the battery is operating. It makes no sense whatsoever to assume that the battery would run better with data that is irrelevant to the current setup than it would with a clean slate
Edit: another point to consider - the battery had to start at a clean slate when it was manufactured - is the OP suggesting that this is bad for the battery? What sense would that make?
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
Trust me, I get what you are saying and follow the logic. It makes sense to me an personally I calibrate my battery when it starts feeling wonky. Do the same on my laptop that definitely reports serial, charge cycles, etc.
My only point was that until someone takes the time to figure out what is really going on here then arguing that one strategy is better than the other is not very useful.
Consider your sound system example... Perhaps there is an issue in the with the calibration logic of your receiver that causes the settings for your living room to provide better sound quality in your bedroom (against the results of the calibration you did there).
All I'm getting at is I wish I understood what was really going on here so I could make an objective decision rather than a subjective one.
machx0r said:
Trust me, I get what you are saying and follow the logic. It makes sense to me an personally I calibrate my battery when it starts feeling wonky. Do the same on my laptop that definitely reports serial, charge cycles, etc.
My only point was that until someone takes the time to figure out what is really going on here then arguing that one strategy is better than the other is not very useful.
Consider your sound system example... Perhaps there is an issue in the with the calibration logic of your receiver that causes the settings for your living room to provide better sound quality in your bedroom (against the results of the calibration you did there).
All I'm getting at is I wish I understood what was really going on here so I could make an objective decision rather than a subjective one.
Click to expand...
Click to collapse
I get your desire for objectivism and I share it, but this ties back to the simple fact that most hacking communities are filled with superstitious habits fuelled by anecdotal evidence and users who get extremely defensive if someone comes along and raises questions about currently accepted conclusions. Sure, these are devices operating on fundamental instructions and every single tiny behavior is governed by code and measured capabilities...
But if you want to see an analysis of that file, you'll have 100x more luck figuring it out on your own than you'd ever have changing the minds of people who sprinkle pixie dust, spin in a circle, rub their earlobes, and clap twice before every flash.
Sent from my SPH-D700 using Tapatalk
josidhe said:
I get your desire for objectivism and I share it, but this ties back to the simple fact that most hacking communities are filled with superstitious habits fuelled by anecdotal evidence and users who get extremely defensive if someone comes along and raises questions about currently accepted conclusions. Sure, these are devices operating on fundamental instructions and every single tiny behavior is governed by code and measured capabilities...
But if you want to see an analysis of that file, you'll have 100x more luck figuring it out on your own than you'd ever have changing the minds of people who sprinkle pixie dust, spin in a circle, rub their earlobes, and clap twice before every flash.
Sent from my SPH-D700 using Tapatalk
Click to expand...
Click to collapse
I concur!
Need analytics/metrics, controlled test environments, hard facts from vendor specs to replicable results. Too many variants and factors involved from avg. 2yr life span of a battery to coronals chicken tweaks. All just theories until proven otherwise.
I am the OP, but I just copy-pasted the article so people know that it may not be a good thing to do, because I had never heard of anything bad about it.
Maybe I just had really high expectations for this phone, maybe I just got a bad unit or maybe it's just that way.
When I first got my N6P, I had a time flashing it. My computer would freeze and the phone came back saying it was corrupt, then the phone reset itself. The files on my N5 are still on my N5 since it's so painful to transfer files. Here are some problems I'm having.
The Google app is telling me that the app is not compatible with my version of Android. What?? That makes absolutely no sense, and since it isn't compatible, I can't update it. I'm using an LG G Watch, and the device shows it's connected, but I am getting zero notifications on it. I open the Wear app and it tells me to update the Google app. This is where I hit a wall.
Second is Snapchat. I barely use Snapchat, but when I do, the app will not work. It freezes, stutters, lags, and requires a force close always. My Nexus 5 worked absolutely fine.
Third is the camera. The camera, since I rooted just will not open. I've looked up this issue and apparently its common, and flashing vendor.img fixes it. So I downloaded vendor.img and flashed it. I then got an error saying something was wrong internally with my device. Then I downloaded the latest factory image (that I'm on) and flashed that vendor.img instead of the one I downloaded. The error went away and the camera opened. Then that was that, it never opened again. Apps like Instagram, Facebook, Snapchat, etc will not use the camera at all, because I guess the camera API is corrupted. Why does this happen on the 6P after root?
Lastly is the battery life. I'm a college student with bills and have got to wait until next payday to get my phone turned on with service, so I've been using airplane mode with WiFi. Adaptive brightness is off, 20% brightness, NFC, WiFi and Bluetooth scanning is off, GPS off, ambient display is off since I have my watch, and I get almost 3 hours SOT, usually 2.5. Keep in mind, this is in airplane mode! I see people getting 4, 5, and 6+ hours SOT on the forums, saying that everything is turned on and pulling data, etc. This is insanely disappointing to me, as I hoped with the big battery and Marshmallow, it would be more optimized. I paid 700 dollars for this 128GB phone, so I expected the battery to be better than my N5 was back in 2013. Currently I have 87% battery and it's dropping while I'm not using it. I have 18 minutes SOT.
The phone itself though is truly amazing and beautiful. Very premium feeling, very sleek, very thin and light. The front facing speakers BLOWS my mind on how crisp and loud they are. They are wonderful. The display colors and crispness is gorgeous. The fingerprint scanner is really great to have, and the phone is very fast.
I don't know what to do. If I can't get better battery life then I'm going to need to return the phone, even though I sincerely don't want to.
Help with any of these? I really just want better battery from such a premium device and it truly saddens me now.
snappycg1996 said:
Maybe I just had really high expectations for this phone, maybe I just got a bad unit or maybe it's just that way.
When I first got my N6P, I had a time flashing it. My computer would freeze and the phone came back saying it was corrupt, then the phone reset itself. The files on my N5 are still on my N5 since it's so painful to transfer files. Here are some problems I'm having.
The Google app is telling me that the app is not compatible with my version of Android. What?? That makes absolutely no sense, and since it isn't compatible, I can't update it. I'm using an LG G Watch, and the device shows it's connected, but I am getting zero notifications on it. I open the Wear app and it tells me to update the Google app. This is where I hit a wall.
Second is Snapchat. I barely use Snapchat, but when I do, the app will not work. It freezes, stutters, lags, and requires a force close always. My Nexus 5 worked absolutely fine.
Third is the camera. The camera, since I rooted just will not open. I've looked up this issue and apparently its common, and flashing vendor.img fixes it. So I downloaded vendor.img and flashed it. I then got an error saying something was wrong internally with my device. Then I downloaded the latest factory image (that I'm on) and flashed that vendor.img instead of the one I downloaded. The error went away and the camera opened. Then that was that, it never opened again. Apps like Instagram, Facebook, Snapchat, etc will not use the camera at all, because I guess the camera API is corrupted. Why does this happen on the 6P after root?
Lastly is the battery life. I'm a college student with bills and have got to wait until next payday to get my phone turned on with service, so I've been using airplane mode with WiFi. Adaptive brightness is off, 20% brightness, NFC, WiFi and Bluetooth scanning is off, GPS off, ambient display is off since I have my watch, and I get almost 3 hours SOT, usually 2.5. Keep in mind, this is in airplane mode! I see people getting 4, 5, and 6+ hours SOT on the forums, saying that everything is turned on and pulling data, etc. This is insanely disappointing to me, as I hoped with the big battery and Marshmallow, it would be more optimized. I paid 700 dollars for this 128GB phone, so I expected the battery to be better than my N5 was back in 2013. Currently I have 87% battery and it's dropping while I'm not using it. I have 18 minutes SOT.
The phone itself though is truly amazing and beautiful. Very premium feeling, very sleek, very thin and light. The front facing speakers BLOWS my mind on how crisp and loud they are. They are wonderful. The display colors and crispness is gorgeous. The fingerprint scanner is really great to have, and the phone is very fast.
I don't know what to do. If I can't get better battery life then I'm going to need to return the phone, even though I sincerely don't want to.
Help with any of these? I really just want better battery from such a premium device and it truly saddens me now.
Click to expand...
Click to collapse
What are you running. Stock or custom. I am on full stock and don't have any of those issues. I also only plug in my phone about an hour a day and I am a heavy user. It seems you may just have a bad chip though. It happens.
Gizmoe said:
What are you running. Stock or custom. I am on full stock and don't have any of those issues. I also only plug in my phone about an hour a day and I am a heavy user. It seems you may just have a bad chip though. It happens.
Click to expand...
Click to collapse
I agree, I wanna say he have a bad unit, I get 4-5 hours of screen on time and I'm on my phone from the minute I get up, until I go to sleep. I'm a really heavy user
so, by the sounds of it, you flashed a bunch of things improperly, and now are wondering why things aren't working?
(before you get sassy, you did flash things imporoperly (comp freezing, phone resetting), because you had some errors, and your vendor was out of date etc.. This isn't an insult, happens to all of us at some point or another)
follow THIS guide, and go back to COMPLETE stock:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
from there, I am more than certain you will see things improve. drastically.
The Camera not working is usually an indication of an improper kernel/boot img.
Gizmoe said:
What are you running. Stock or custom. I am on full stock and don't have any of those issues. I also only plug in my phone about an hour a day and I am a heavy user. It seems you may just have a bad chip though. It happens.
Click to expand...
Click to collapse
I'm not the only one with this bad battery it seems though. Are there really that many defective units??? I'm on complete stock 6.0.1 with latest February patch.
TyrellP said:
I agree, I wanna say he have a bad unit, I get 4-5 hours of screen on time and I'm on my phone from the minute I get up, until I go to sleep. I'm a really heavy user
Click to expand...
Click to collapse
I don't know. I'm gonna factory reset I guess, battery is draining pretty rapidly now. 38 mins SOT and 48% battery...
Soulfly3 said:
so, by the sounds of it, you flashed a bunch of things improperly, and now are wondering why things aren't working?
(before you get sassy, you did flash things imporoperly (comp freezing, phone resetting), because you had some errors, and your vendor was out of date etc.. This isn't an insult, happens to all of us at some point or another)
follow THIS guide, and go back to COMPLETE stock:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
from there, I am more than certain you will see things improve. drastically.
Click to expand...
Click to collapse
I'm gonna try factory resetting. As of now, battery is complete garbage. I don't see how a wrong root/vendor.ing flash could cause dramatic battery loss.
dratsablive said:
The Camera not working is usually an indication of an improper kernel/boot img.
Click to expand...
Click to collapse
I flashed the wrong vendor.IMG for my version which probsbly is causing it. I'm gonna just factory reset.
What do y'all make of this??
snappycg1996 said:
What do y'all make of this??
Click to expand...
Click to collapse
you have massive wakelocks which is draining your battery.
Just factory reset and follow the instructions in the link i gave you to go to the latest stock
Soulfly3 said:
you have massive wakelocks which is draining your battery.
Just factory reset and follow the instructions in the link i gave you to go to the latest stock
Click to expand...
Click to collapse
I will after I deplete the battery lower, I just wanna see how long it lasts.
The device is also now slowing down a bit. The RAM is really being used..
EDIT: tries uploading screenshots. It's over 2 GBs being used on RAM.
Your phone is just messed up, I'm sure that once you get it completely stock, it'll work better and have a better SOT.
There's been some reports of bluetooth causing wakelocks when using smartwatches.
snappycg1996 said:
I'm a college student with bills and have got to wait until next payday to get my phone turned on with service, so I've been using airplane mode with WiFi.
Click to expand...
Click to collapse
snappycg1996 said:
I'm using an LG G Watch
Click to expand...
Click to collapse
snappycg1996 said:
I paid 700 dollars for this 128GB phone, so I expected the battery to be better than my N5 was back in 2013.
Click to expand...
Click to collapse
Not judging. Just confused.
Sounds to me like you've done something to the phone yourself that's causing these problems. Especially the camera not opening, that's a symptom of having the wrong boot.img flashed to the device. Factory resetting won't help if you have the wrong boot.img flashed. You need to flash the factory images to ensure that everything is in line. See my guide for details:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
adotkdotjh said:
Not judging. Just confused.
Click to expand...
Click to collapse
What's confusing? I saved up the money over my paychecks and then my college mkney came back in and I was able to buy it finally. The G Watch was on sale for 100 when I bought it.
TonzaTheChosenOne said:
Your phone is just messed up, I'm sure that once you get it completely stock, it'll work better and have a better SOT.
There's been some reports of bluetooth causing wakelocks when using smartwatches.
Click to expand...
Click to collapse
It just doesn't make sense how it could be making my battery so bad. But like I said, I'm working on flashing the factory image right now.
Heisenberg said:
Sounds to me like you've done something to the phone yourself that's causing these problems. Especially the camera not opening, that's a symptom of having the wrong boot.img flashed to the device. Factory resetting won't help if you have the wrong boot.img flashed. You need to flash the factory images to ensure that everything is in line. See my guide for details:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
Click to expand...
Click to collapse
I am gonna flash the stock image 6.0.1 and then root systemless and see if that helps. Besides that though, I'm not sure how that could be causing such terrible battery. It's very disappointing.
snappycg1996 said:
It just doesn't make sense how it could be making my battery so bad. But like I said, I'm working on flashing the factory image right now.
I am gonna flash the stock image 6.0.1 and then root systemless and see if that helps. Besides that though, I'm not sure how that could be causing such terrible battery. It's very disappointing.
Click to expand...
Click to collapse
It kinda does make sense, I don't know exactly what you've done to cause these problems but mismatches can affect battery performance. Go back to stock, flash the latest SuperSU beta and nothing else and see how it performs.
Heisenberg said:
It kinda does make sense, I don't know exactly what you've done to cause these problems but mismatches can affect battery performance. Go back to stock, flash the latest SuperSU beta and nothing else and see how it performs.
Click to expand...
Click to collapse
Should I lock my bootloader and then unlock it again? Or just flash factory?
snappycg1996 said:
Should I lock my bootloader and then unlock it again? Or just flash factory?
Click to expand...
Click to collapse
No need to mess with the bootloader, just leave it unlocked.
It has to be your unit. Of the four users I know none have these issues. If restoring doesn't fix it...
cstrife999 said:
It has to be your unit. Of the four users I know none have these issues. If restoring doesn't fix it...
Click to expand...
Click to collapse
It doesn't have to be the unit at all, it's likely to be a result of inexperience and bad flashing.
Heisenberg said:
It doesn't have to be the unit at all, it's likely to be a result of inexperience and bad flashing.
Click to expand...
Click to collapse
Soulfly3 said:
so, by the sounds of it, you flashed a bunch of things improperly, and now are wondering why things aren't working?
(before you get sassy, you did flash things imporoperly (comp freezing, phone resetting), because you had some errors, and your vendor was out of date etc.. This isn't an insult, happens to all of us at some point or another)
follow THIS guide, and go back to COMPLETE stock:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
from there, I am more than certain you will see things improve. drastically.
Click to expand...
Click to collapse
Flashed back to complete stock, and rooted. Phone feels faster, camera now works, BUT battery is still not up to par with what others get and reviews say. I can barely get two hours, it's usually around 2:40. I have no rogue apps, I have BBS, and WLD showing nothing out of the ordinary. Normal drainers like scanning is off and I am using greenify. With no luck. Battery life is still just like my N5 when it was brand new in 2013. For a 2015/2016 phone, it's very disappointing.
Anything else you guys would recommend?
snappycg1996 said:
Flashed back to complete stock, and rooted. Phone feels faster, camera now works, BUT battery is still not up to par with what others get and reviews say. I can barely get two hours, it's usually around 2:40. I have no rogue apps, I have BBS, and WLD showing nothing out of the ordinary. Normal drainers like scanning is off and I am using greenify. With no luck. Battery life is still just like my N5 when it was brand new in 2013. For a 2015/2016 phone, it's very disappointing.
Anything else you guys would recommend?
Click to expand...
Click to collapse
Uninstall Greenify, it's known for messing up with Doze.
Btw, are you living in a bad reception area? Do you use wifi or 4G most of the time? Brightness?
So I just switched to 7.0 U firmware from 7.0 att.
I have done a lot of stuff to save battery on this phone and still no luck. So far this is what I have today. Not even 2 hours of screen on time and it's almost dead... any helps?
Factory rest and cleared cache several times after switching and no luck
Start the RMA process. You have a bad battery.
Krazie99 said:
So I just switched to 7.0 U firmware from 7.0 att.
I have done a lot of stuff to save battery on this phone and still no luck. So far this is what I have today. Not even 2 hours of screen on time and it's almost dead... any helps?
Factory rest and cleared cache several times after switching and no luck
Click to expand...
Click to collapse
From my experience, you could have an app that is doing the dirty deed. Try to factory wipe without restoring apps, do a basic set up and see how it works.
Also, try going back to the stock AT&T release.
kangi26 said:
From my experience, you could have an app that is doing the dirty deed. Try to factory wipe without restoring apps, do a basic set up and see how it works.
Also, try going back to the stock AT&T release.
Click to expand...
Click to collapse
It's possible, but the screen shot lists the usual top three suspects and only a couple of hours of SOT is abysmal, even for stock.
It's certainly worth a shot going back to stock and installing nothing but the bare essentials, but I'd say there is a better than average chance the device has a hardware problem with those kinds of numbers.
jshamlet said:
It's possible, but the screen shot lists the usual top three suspects and only a couple of hours of SOT is abysmal, even for stock.
It's certainly worth a shot going back to stock and installing nothing but the bare essentials, but I'd say there is a better than average chance the device has a hardware problem with those kinds of numbers.
Click to expand...
Click to collapse
I would rather keep the u firmware with stuff I need and have bad battery then have stock with nothing on it. I was thinking of going back to stock when I switched to U but only the that held me back ass all the bloatware on att. So should I get a new battery?
Krazie99 said:
I would rather keep the u firmware with stuff I need and have bad battery then have stock with nothing on it. I was thinking of going back to stock when I switched to U but only the that held me back ass all the bloatware on att. So should I get a new battery?
Click to expand...
Click to collapse
IMO, the bloat that is on the stock ROM's are somewhat irrelevant now. You may not be able to un-install it, but you can disable it, and in the grand scheme of things has little impact on the device or performance once that's done. Annoying? YES, but......
I'd say if the U ROM isnt performing, ditch it
Again, In My Opinion
kangi26 said:
IMO, the bloat that is on the stock ROM's are somewhat irrelevant now. You may not be able to un-install it, but you can disable it, and in the grand scheme of things has little impact on the device or performance once that's done. Annoying? YES, but......
I'd say if the U ROM isnt performing, ditch it
Again, In My Opinion
Click to expand...
Click to collapse
Updated. Have any idea what can cause this?