yashsingh1/xdaforums huggingface dataset:
[Nexus 5 Q&A, Help & Troubleshooting] ej8989:
1. Anything to worry about the battery life?

Based on how you use your phone, not really. Unless there's a hardware defect.

2. Is it wise to install a "battery saving" app on the Play store?

For me, no. I once tried one and it didn't help at all. But there's no harm in trying.

3. Will heat be a factor on my "typical" day on draining my battery life?

A few weeks ago I did some heavy gaming for an hour and the phone was really warm, but I still got >5hrs SoT at the end of the day before charging again.

4. Is it true the battery life improves after a couple of charges?

Yes the battery life is somewhat improved; but what I experienced was that it improves when I stay in the same ROM for some days, and I charge it overnight when the battery is less than 5%.

5. Will the phone picking up 3G & 4G signal (switching back & forth and re-initializing again and again) be a factor in a battery drain?

In my opinion (and experience), yes.

6. What tips can you advice me on how to save battery life on my Nexus 5?

Here's a thread you can analyze: Nexus 5 Battery Results
[Nexus 5 Q&A, Help & Troubleshooting] gino_76ph:
I will mainly be using stock Android 4.4.2 ROM on my Nexus 5 and will NOT be rooting it even though it seems it might improve the battery life.

I know about turing off everything when not in use. I live in a generally "Ok" 3G/4G signal but when i travel to & from work and my work place the signal is not bad, not good either and that it switches back & forth. That's one concern.

If i keep my phone on normal 2G mode will it help extend battery life? Or putting it on Airplane mode be more helpful? Yes or No?

I for one won't probably be installing battery-saving apps as i know they might not help in battery life. Very ironic. Good plan?

I won't be doing heavy gaming for an hour or so i'm not too worried on that front.

Will charging my battery (let's say if its 10% or less) at 11pm and unplugging the charging at 6am can damage the battery cells? Is that not advisable?

Based on my routine in regards to my LG G2 by 11pm i still have roughly 10-20% battery life. This is probably because of the fact that (i) The Android OS is better "optimised", much cleaner interface with minimal bloatware, (ii) The phone has a built-in power saving mode and (iii) The phone has a bigger battery. Would you guys agree?

And another question is: Why Google hasn't implemented a power saving mode (in the battery settings) like that of Sony and Samsung?

And is there an app similar to Power saving mode which i can download?
[Nexus 5 Q&A, Help & Troubleshooting] mistahseller:
Rooting has zero effect on battery life.

2g extends the most life. I use power toggles and smart radio

I can tell you that no phone/ software is better optimized than stock. Power saving mode is a scam. All it does is a centralized way of turning brightness next to nill, control radio, turn off WiFi, Bluetooth etc, and maybe downclock the processor but don't quote me on that.

I think you're making this harder than it needs to be.

Sent from The Deathstar
[Nexus 5 Q&A, Help & Troubleshooting] ej8989:
Prove it. Well of course you won't benefit from rooting if you don't know what to do after being rooted.

In your statement it is profoundly described that power saving mode really does something.
[Nexus 5 Q&A, Help & Troubleshooting] mistahseller:
Prove what? All you do is flash superuser version x.x.x which allows you to give permission that you would not normally give to apps. But you already know this because you are a senior member, along with your post/ thanks count, I don't understand why you would make this statement.

In my opinion powersaving mode is nothing more than a marketing ploy for the masses is what I was inferring. Any other concerns/ questions?
[Nexus 5 Q&A, Help & Troubleshooting] bblzd:
To be fair that's usually all stock OEM battery savers will do as well, disable sync and turn the backlight down.

Also you're right root access itself does nothing for battery life and new users seem to think it does. In many cases they will only install new services and be forced to charge more often.
[Nexus 5 Q&A, Help & Troubleshooting] ej8989:
That rooting your device to benefit from apps that require it (like greenify) won't really do anything to decrease power usage.
[Nexus 4 Q&A, Help & Troubleshooting] olyloh6696:
I have had a Nexus 4 since the end of August.

I've been given the opportunity to upgrade to a new Nexus 5. Should I go for it, or should I wait instead and get the Nexus 6 (or whatever it will be called) in October when its released?

Any fellow N4 owners out there who can give advice? I can't see any groundbreaking improvements...?

So far I'm leaning on sticking with the N4 for now, its not even a year old yet and does pretty much all I want to do on it. I'm a casual user, no root, stock KitKat etc.

Cheers.
[Nexus 4 Q&A, Help & Troubleshooting] meZQureshi:
Don't Upgrade. Wait the the next phone.:)
[Nexus 4 Q&A, Help & Troubleshooting] badboy47:
Next nexus device won't be announce until the end of the year or early 2015. There is no ground breaking changes in nexus 5 but it's definitely a nice device.
[Nexus 4 Q&A, Help & Troubleshooting] Zehlek:
I would definitely take that offer
[Nexus 4 Q&A, Help & Troubleshooting] Mashed_Potatoes:
I've bought the N4 because it looks better IMO, and the N5 is not crucial to me, the N4 hardware is more than i will need in the next 2 years.

But the price difference is not big, a new N4 is 250 and the N5 is like 325 euros. Still cheaper than HTC One or S4
[Nexus 4 Q&A, Help & Troubleshooting] albundy2010:
Stay with the 4

Yes the 5 is better in many ways but if those better ways aren't compelling to you. Than its a pointless upgrade.

Same goes for any other upgrade. You will know when it's time to upgrade. For example when the phone becomes slow to a point when it's frustrating to use. When you actually can take advantage of the newer radios and bands. Like those folks who have a nexus 4 on att. If they have lte in the area that's a more compelling upgrade for them. If you play a lot of music locally and need the extra battery life the 5 and the s800 delivers doing that

Basically if somebody has to convince that you should upgrade. You don't need a upgrade
[Nexus 4 Q&A, Help & Troubleshooting] wulsic:
If you really want it then you should do it but i dont see why you need to do it so fast cause the nexus 4 has only some disadvantages which arent that important cause it has a good cpu,gpu and lots of ram it could even play gta sa with a little lagg if its busy and other HD games so i think it will even play all big games the next 2 years so decide:fingers-crossed:
[Nexus 4 Q&A, Help & Troubleshooting] bayuomi:
Don't Upgrade, there's no big difference between the two devices in addition to you are a casual user as you say and really you don't need the n5
[Nexus 4 Q&A, Help & Troubleshooting] sinnerghost:
If you were a "hardcore"user, I would've said yes, but seeing as you yourself said you're more casual, than you really won't feel the difference.
[Galaxy Y GT-S5360 and Duos 6102 Q&A, Help & Troubl] Schroef-77:
Hi all,

I've been reading alot on this forum but never posted anything.

Most of my problems were solved by reading the solutions found by other members with the same problem.

This time that trick doesn't work for me anymore :)

Here is my problem.

A few days ago the phone went dead after the battery run out of juice (a Mugen extended 3000 Mah battery).

After connecting the phone to a charger I noticed that I didn't see the battery icon on the screen that used to show up during charging.

After a couple of tests I noticed that the phone actually did boot up but the screen doesn't show any signs of life.

I can both hear (tmobile tune) and feel (vibration) the phone booting up.I can even hear it ringing when calling the phone with my other phone but the screen stays black and doesn't show any signs of life.

I must add the following information:the phone has been used extensively as a gps tracker in my car.

Is there a way to solve my problem?

I hope someone can help me out with this weird and unexpected problem.

Thanks in advance!
[Galaxy Y GT-S5360 and Duos 6102 Q&A, Help & Troubl] TheFixItMan:
if you put the phone into download mode does the screen work?

pull the battery and put it back in again

hold vol down home button and with these two buttons held then also hold the power button

if you can see the screen and can see download mode continue to flash stock rom via odin (search for how and note all data on phone will be lost)

if you cant see the screen in download mode chances are you have a hardware fault and should take it to a repair shop for diagnostics
[Galaxy Y GT-S5360 and Duos 6102 Q&A, Help & Troubl] Schroef-77:
I can't see anything on the screen.

It's black all the time,even when it boots up or receives a call.
[Galaxy Y GT-S5360 and Duos 6102 Q&A, Help & Troubl] TheFixItMan:
either your screen/backlight is faulty or there is a loose connection

if its a backlight you can normally still see somethiing if you hold the screen at an angle

if its the screen itself or a loose connection the screen wont turn on

you will need to take it to a repair shop for testing and repair
[Sprint Samsung Galaxy S III] marcran75:
Do you have to be on a deodexed rom? Just flashed this twice on stock MK3 and I'm getting nothin'.
[Sprint Samsung Galaxy S III] tdunham:
Yes, 99% of any mods are going to be for deodexed. That is partly why it is extremely difficult to find an odexed custom rom.
[Sprint Samsung Galaxy S III] marcran75:
That's what I figured but thought I would ask anyways.
[Sprint Samsung Galaxy S III] remotehugger:
another awesome mod !!! love it - so happy you have started making these - keep em' coming !!!!

VM SIII - jdsingle76's MK5 4.3

decimalman's TW dkp kernel
[Sprint Samsung Galaxy S III] Thebear j koss:
Between you and [MENTION=4645794]CNexus[/MENTION], I will be killing someone soon with all the extra theming you have me doing. Nice job... :)

Thebe@r'$ G@L@XY
[Sprint Samsung Galaxy S III] CNexus:
Move android.policy.jar and android.policy.jar.odex to your sdcard (to make a "backup" of them and delete at the same time) then flash this and it will work.

Deodexed mods can be used on odex, but not the other way around. Only catch is you gotta delete the affected odex files or else the system will preload those cache files and ignore the new file
[Sprint Samsung Galaxy S III] marcran75:
Tried this and got stock at boot screen. Pulled battery and still the same.
[Sprint Samsung Galaxy S III] CNexus:
Hmm...I've done this tons of times before on stock odexed and it's worked

Check the zip to see what (if any) other files are affected and move the odex files for those, then try flashing again
[Sprint Samsung Galaxy S III] bigpappags3:
Is there anyway you could make a guide. ...I would love this on Wicked sensations.

http://i.imgur.com/qrByUGN.jpg
[Sprint Samsung Galaxy S III] the_original_teknikl:
Notice youre running virgin mobile... Thanks to tdunham, I have put together a zip to get the virgin mobile network running on the wicked sensations ROM... I have stock 4.3 android thru my ota update and with the zip it works perfect in VM.

ROM is here --> http://xdaforums.com/showthread.php?t=2581010

Read the second post for the virgin mobile fix..

Just bored and saw that part of your post lol
[Sprint Samsung Galaxy S III] Thebear j koss:
Shut up clown. Don't give that other clown any ideas... Soon i'll have a 10 in 1 power menu and 60 toggles to theme...

Thebe@r'$ G@L@XY
[Sprint Samsung Galaxy S III] baldd86:
Confirm working on wicked and is nice. Nice mod
[Sprint Samsung Galaxy S III] Chad The Pathfinder:
Thanks for this tdunham. I already clicked thanks but this is just awesome. :thumbup:
[Sprint Samsung Galaxy S III] nyfl2004:
Awesome mod. Thank you very much!
[Sprint Samsung Galaxy S III] tdunham:
Update

:

Added to the OP a second New Power Menu with Airplane Mode toggle removed.

Just flash over the other one if you want to try it.
[Sprint Samsung Galaxy S III] notmyepic:
I tried this and it force closes my phone settings (sure it is related to something I did to my personal framework-res.apk). So my question is if you could tell me which if any xmls need modified?
[Sprint Samsung Galaxy S III] tdunham:
I won't do full guide until later:

framework-res.apk edits:
Add the 3 icons (from the support file) to framework-res/res/drawable-xhdpi
Add 3 new lines to framework-res/res/values/strings:
<string name="download">Bootloader</string>
<string name="recovery">Recovery</string>
<string name="global_action_screenshot_txt">Screenshot</string>
</resources>

Still no guarantees if other changes were made that alter public values that get generated when framework-res is compiled.
[Sprint Samsung Galaxy S III] Chad The Pathfinder:
Hey man, I changed he pngs to match the rest of Dandroid. In the 3rd option down instead of saying "download mode" it says "bootloader". Where would I go to change this?
[Sprint Samsung Galaxy S III] tdunham:
It's in the post before this one.

Edit: Sorry, meant the post above yours.
[Sprint Samsung Galaxy S III] notmyepic:
This should be what I was looking for. Thanks
[Sprint Samsung Galaxy S III] tdunham:
The guide is finished and posted to the OP.

If anyone tries this and has any issues, logcat is your friend.

If it was my fault and there is a typo somewhere, sorry in advance and please let me know.
[Sprint Samsung Galaxy S III] Spannaa:
Hi,

I've just gone through the guide and it's working as expected on my S3 I9300 - thanks :good:

A couple of thinks I noticed:

The Data network mode toggle is now missing from the menu (not a big deal as there's a notification toggle for this)

If I switch the Accessibility or Talkback toggles on via settings > accessibility, they don't appear in the menu as they did before (again, not a big deal)
[Sprint Samsung Galaxy S III] Chad The Pathfinder:
Thanks for the guide OP!
[Sprint Samsung Galaxy S III] tdunham:
The Data network toggle was never part of our stock menu I think. I will experiment with adding it back in when I have a few to flash back to stock rom to test it out.

I haven't seen the other two toggles for Accessibility or Talkback. I don't think we can get those back but I'm curious if it acts that way in our stock rom as well. I think when we deleted the if-nez v0, :cond_3

conditional statement to allow us to modify the menu, it may have disabled that as well since display now relies on what is defined in the array.
[Sprint Samsung Galaxy S III] Spannaa:
Not sure about on stock - I'm running NeatROM 6.5 XXUGNA7 and there was a data network mode toggle there before I modded android.policy.jar and both the Accessibility & Talkback toggles were available if switched on.

Still, as I said, no big deal - the menu is a lot more user friendly now ;)

Thanks again.

[EDIT] It is the if-nez v0, :cond_3 conditional statement that's removing the data network mode toggle and both the accessibility & talkback toggles. If I just add this line back in, the toggles revert to how they were before, even though all of the other edits are still in place. [/EDIT]
[Sprint Samsung Galaxy S III] tdunham:
Ok, I just figured out what's going on. Not completely but look at this...

Re-enable that line if-nez v0, :cond_3, then do a search for const/16 v0, 0x8. There is an entire new array and that is where the missing toggles are generated. I wonder if we were to put the array items from above into this section instead what would happen. Give it a go on your end and I'll take a shot at it as well.
[Sprint Samsung Galaxy S III] tdunham:
[MENTION=2948558]Spannaa[/MENTION]

Alright, it looks like I'm going to have to re-address the tutorial. LOL

This was a quick test and the order isn't what I normally like because I prefer Restart at the bottom but looks like my theory panned out.

(Note that data toggle is missing from ours. I'm sure yours would show as it used to).
[Sprint Samsung Galaxy S III] Spannaa:
Sorry, PC is off but that array is cond_3 isn't it?

I tried adding the new toggles to it but couldn't get it to work.

I'll look again in the morning but TBH, I'm happy with it as it is.
[Sprint Samsung Galaxy S III] tdunham:
Here is the completed second array that works and a screenshot. The toggles for Accessory and Talkback also work now for you also. I moved Power to the top and arranged everything to how I like. You can change it how you see fit.

Several things to note though...

The array (const/16 v0, 0x8) cannot be over 8 items or it gives a fatal error. This really shouldn't be an issue because that's all that fits on the screen anyway. And I'm not really sure how to make it larger anyway. LOL

I removed 3 items to make room, mBugReport, mLonglife, and mDataModeToggle . If you want Data Toggle to replace Airplane Mode in the menu, just replace the term mAirplaneModeOn with mDataModeToggle

in the array shown below.

A couple of the sections of the guide have been rewritten because of this if you want to see the difference. It actually simplified things a bit.

:cond_3

const/16 v0, 0x8

new-array v0, v0, [Lcom/android/internal/policy/impl/GlobalActions$Action;

const/4 v1, 0x0

iget-object v2, p0, Lcom/android/internal/policy/impl/GlobalActions;->mPowerOff:Lcom/android/internal/policy/impl/GlobalActions$SinglePressAction;

aput-object v2, v0, v1

const/4 v1, 0x1

iget-object v2, p0, Lcom/android/internal/policy/impl/GlobalActions;->mAccessiblityShortcut:Lcom/android/internal/policy/impl/GlobalActions$SinglePressAction;

aput-object v2, v0, v1

const/4 v1, 0x2

iget-object v2, p0, Lcom/android/internal/policy/impl/GlobalActions;->mTalkBack:Lcom/android/internal/policy/impl/GlobalActions$ToggleAction;

aput-object v2, v0, v1

const/4 v1, 0x3

iget-object v2, p0, Lcom/android/internal/policy/impl/GlobalActions;->mAirplaneModeOn:Lcom/android/internal/policy/impl/GlobalActions$ToggleAction;

aput-object v2, v0, v1

const/4 v1, 0x4

iget-object v2, p0, Lcom/android/internal/policy/impl/GlobalActions;->mScreenshot:Lcom/android/internal/policy/impl/GlobalActions$SinglePressAction;

aput-object v2, v0, v1

const/4 v1, 0x5

iget-object v2, p0, Lcom/android/internal/policy/impl/GlobalActions;->mDownload:Lcom/android/internal/policy/impl/GlobalActions$SinglePressAction;

aput-object v2, v0, v1

const/4 v1, 0x6

iget-object v2, p0, Lcom/android/internal/policy/impl/GlobalActions;->mRecovery:Lcom/android/internal/policy/impl/GlobalActions$SinglePressAction;

aput-object v2, v0, v1

const/4 v1, 0x7

iget-object v2, p0, Lcom/android/internal/policy/impl/GlobalActions;->mRestart:Lcom/android/internal/policy/impl/GlobalActions$SinglePressAction;

aput-object v2, v0, v1
[Sprint Samsung Galaxy S III] LeoDeos:
Great Guide..thanks a lot :)

I'm on I9305 4.3...ml9

I followed the guide posted yesterday and I add only screenshot...worked well but I havent data toggle.

So I just made ​​a small change to the guide.

My stock power menu..screenshot:

Yesterday guide...source:

.line 1083

const/4 v0, 0x4

new-array v0, v0, [Lcom/android/internal/policy/impl/GlobalActions$Action;

const/4 v1, 0x0

iget-object v2, p0, Lcom/android/internal/policy/impl/GlobalActions;->mPowerOff:Lcom/android/internal/policy/impl/GlobalActions$SinglePressAction;

aput-object v2, v0, v1

const/4 v1, 0x1

iget-object v2, p0, Lcom/android/internal/policy/impl/GlobalActions;->mAirplaneModeOn:Lcom/android/internal/policy/impl/GlobalActions$ToggleAction;

aput-object v2, v0, v1

const/4 v1, 0x2

iget-object v2, p0, Lcom/android/internal/policy/impl/GlobalActions;->mScreenshot:Lcom/android/internal/policy/impl/GlobalActions$SinglePressAction;

aput-object v2, v0, v1

const/4 v1, 0x3

iget-object v2, p0, Lcom/android/internal/policy/impl/GlobalActions;->mRestart:Lcom/android/internal/policy/impl/GlobalActions$SinglePressAction;

aput-object v2, v0, v1

Screenshot:

My mod...source:

.line 1083

const/4 v0, 0x5

new-array v0, v0, [Lcom/android/internal/policy/impl/GlobalActions$Action;

const/4 v1, 0x0

iget-object v2, p0, Lcom/android/internal/policy/impl/GlobalActions;->mPowerOff:Lcom/android/internal/policy/impl/GlobalActions$SinglePressAction;

aput-object v2, v0, v1

const/4 v1, 0x1

iget-object v2, p0, Lcom/android/internal/policy/impl/GlobalActions;->mDataModeToggle:Lcom/android/internal/policy/impl/GlobalActions$ToggleAction;

aput-object v2, v0, v1

const/4 v1, 0x2

iget-object v2, p0, Lcom/android/internal/policy/impl/GlobalActions;->mAirplaneModeOn:Lcom/android/internal/policy/impl/GlobalActions$ToggleAction;

aput-object v2, v0, v1

const/4 v1, 0x3

iget-object v2, p0, Lcom/android/internal/policy/impl/GlobalActions;->mScreenshot:Lcom/android/internal/policy/impl/GlobalActions$SinglePressAction;

aput-object v2, v0, v1

const/4 v1, 0x4

iget-object v2, p0, Lcom/android/internal/policy/impl/GlobalActions;->mRestart:Lcom/android/internal/policy/impl/GlobalActions$SinglePressAction;

aput-object v2, v0, v1

Screenshot:
[Sprint Samsung Galaxy S III] Spannaa:
That's exactly what I was trying to do last night but I wanted to leave everything in the array and add download, recovery & screenshot which made 11 items in total...

I changed the const/4 v1, to const/16 v1, for every item over 0x7 but it failed because I forgot that the numbering is hex and used const/16 v0, 0x11 instead of const/16 v0, 0xb for the number of items in the array and 0x10 instead of 0xa for the last item :o

I've just edited my code and it now works as expected :)

My full :cond_3

:cond_3

const/16 v0, 0xb

new-array v0, v0, [Lcom/android/internal/policy/impl/GlobalActions$Action;

const/4 v1, 0x0

iget-object v2, p0, Lcom/android/internal/policy/impl/GlobalActions;->mPowerOff:Lcom/android/internal/policy/impl/GlobalActions$SinglePressAction;

aput-object v2, v0, v1

const/4 v1, 0x1

iget-object v2, p0, Lcom/android/internal/policy/impl/GlobalActions;->mAccessiblityShortcut:Lcom/android/internal/policy/impl/GlobalActions$SinglePressAction;

aput-object v2, v0, v1

const/4 v1, 0x2

iget-object v2, p0, Lcom/android/internal/policy/impl/GlobalActions;->mTalkBack:Lcom/android/internal/policy/impl/GlobalActions$ToggleAction;

aput-object v2, v0, v1

const/4 v1, 0x3

iget-object v2, p0, Lcom/android/internal/policy/impl/GlobalActions;->mAirplaneModeOn:Lcom/android/internal/policy/impl/GlobalActions$ToggleAction;

aput-object v2, v0, v1

const/4 v1, 0x4

iget-object v2, p0, Lcom/android/internal/policy/impl/GlobalActions;->mScreenshot:Lcom/android/internal/policy/impl/GlobalActions$SinglePressAction;

aput-object v2, v0, v1

const/4 v1, 0x5

iget-object v2, p0, Lcom/android/internal/policy/impl/GlobalActions;->mDataModeToggle:Lcom/android/internal/policy/impl/GlobalActions$ToggleAction;

aput-object v2, v0, v1

const/4 v1, 0x6

iget-object v2, p0, Lcom/android/internal/policy/impl/GlobalActions;->mDownload:Lcom/android/internal/policy/impl/GlobalActions$SinglePressAction;

aput-object v2, v0, v1

const/4 v1, 0x7

iget-object v2, p0, Lcom/android/internal/policy/impl/GlobalActions;->mRecovery:Lcom/android/internal/policy/impl/GlobalActions$SinglePressAction;

aput-object v2, v0, v1

const/16 v1, 0x8

iget-object v2, p0, Lcom/android/internal/policy/impl/GlobalActions;->mRestart:Lcom/android/internal/policy/impl/GlobalActions$SinglePressAction;

aput-object v2, v0, v1

const/16 v1, 0x9

iget-object v2, p0, Lcom/android/internal/policy/impl/GlobalActions;->mBugReport:Lcom/android/internal/policy/impl/GlobalActions$SinglePressAction;

aput-object v2, v0, v1

const/16 v1, 0xa

iget-object v2, p0, Lcom/android/internal/policy/impl/GlobalActions;->mLonglife:Lcom/android/internal/policy/impl/GlobalActions$ToggleAction;

aput-object v2, v0, v1

invoke-static {v0}, Lcom/google/android/collect/Lists;->newArrayList([Ljava/lang/Object;)Ljava/util/ArrayList;

move-result-object v0

iput-object v0, p0, Lcom/android/internal/policy/impl/GlobalActions;->mItems:Ljava/util/ArrayList;

goto/16 :goto_0

Thanks again [MENTION=1042140]tdunham[/MENTION] :good:
[Sprint Samsung Galaxy S III] tdunham:
molto bello/very nice.
[Sprint Samsung Galaxy S III] tdunham:
Ahh, perfect. Thank you for the const/16, I knew it was going to be something simple.