Database Info

[Q] Changing ROM pngs?

Is it possible to take a ROM zip (AOKP, for example) and change around some of the pngs (in SystemUI.apk, for example) before it is installed?
I know how to make the changes I would want to do, and I have the pngs I would want to change; I just want to know if it's possible to do so prior to installation without any issues.

Anyone know?
If not, does anyone know if doing this might mess up my phone? I'd rather not brick my phone.

This is really interesting..
Even I am waiting for the answer :fingers-crossed:

Yea that should work fine. Just don't unzip the ROM. Leave it zipped and copy/paste in and out of it.
And once you flash the ROM, you can always make more PNG edits to SystemUI.apk, etc. and just cut and paste it into your phone using root explorer.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2

For the most part, you can usually add/remove/edit individual files/apks inside a ROM zip as long as you're not messing with the folder structure too much. Just open up the updater-script in notepad++ and you can see how the ROM is actually being installed. It usually just extracts the system folder as a whole, so it's essentially oblivious to what's actually inside it.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2

Great, thanks for the input.
I've never made a ROM of my own, but I've done some APK theming. I'll have to give it a try. I'll post back with the results.

How to changeout camera apk in roms.

I'm interested in flashing the Sabsa Prime rom, http://forum.xda-developers.com/showthread.php?t=1839004 , but there are currently reported issues with the camera not working correctly. It's said (by the dev himself) that you can change the current camera apk with a previous one but I'm not exactly sure how to do this. I already have the camera.apk from the earlier version that works great, can I just extract the current rom and replace the camera.apk with the working one and rezip it as a .zip file and flash it? Or would I need to do something else to make it flashable or a different step all together? Thanks!

That sounds about right. Just keep the originals in case there are additional steps. Flash and test.
However, using that other cam apk, if it's the one I'm thinking, not sure if it's allowed. For personal use without re-distributing it, maybe but not quite sure.
Sent from a dream.

Unzip replace and rezip. I do this with all roms I use. There are apks I like to add and delete as well as system audios and bootani. You can alter the rom to your liking just remember not all apks work for a rom in other words you can not use sense apks on a aokp rom for example. And second if you do alter a rom you can not ask the Dev for help if something goes wrong with it, you altered it. With that said alter at your own risk and enjoy the learning.
Sent from my Ice Cold Inspire 4G

[Q] How to remove the Verizon Wireless on the stock lockscreen

Anyone successfully remove the Verizon Wireless from the lock screen yet. I have made many attempts via framework–res to no avail. I have made changes to the eri.xml as well as adding/changing the spn-conf. Any ideas or tips would be appreciated.
Thanks

I am assuming the info comes from the SIM card because when its not inserted the phrase, "No SIM card, Emergency Calls Only" is displayed in the same place Verizon Wireless normally is. There has to be a handoff between the SIM Card and code via an XML file someplace but I have yet to find it. If anyone has any info please let me know.

I'd be willing to bet 5 bucks there is an xml edit in framework-res.apk or systemui.apk that would get rid of it , If I come across it i'll let you know for sure.

natethegreat86 said:
I'd be willing to bet 5 bucks there is an xml edit in framework-res.apk or systemui.apk that would get rid of it , If I come across it i'll let you know for sure.
Click to expand...
Click to collapse
Ive checked strings in both and neither had any reference. I will check again because i am pretty sure it has to be in framework-res.

Ya I see a lot of lock screen entries in framework-res strings.xml but nothing with plain verizon wireless, i see all the other possible things that could popup and it does look like its linked to the sim from there. I also see a reference to carrierLabel in systemui public.xml with an id of 0x7f0f00ae no idea where its linked to though as of yet will keep digging.
EDIT: Question for you guys are you running ICS touchwiz roms or aosp or what? I ask because I'm on a AOSP jelly bean rom and it might be different then what you guys have
I'm thinking this is going to require editing some smali files most likely, do me a favor and see if you have this file in your systemui.apk:
SystemUI\com\android\systemui\statusbar\phone\CarrierLabel.smali

natethegreat86 said:
Ya I see a lot of lock screen entries in framework-res strings.xml but nothing with plain verizon wireless, i see all the other possible things that could popup and it does look like its linked to the sim from there. I also see a reference to carrierLabel in systemui public.xml with an id of 0x7f0f00ae no idea where its linked to though as of yet will keep digging.
Click to expand...
Click to collapse
Thanks.
The two entries I am looking for are:
Verizon Wireless
No Sim Card..Emergency calls Only
Those two phrases pop up in the same place on the lock screen when booting and/or once booted up.
Some other phones like the Nexus have thier carrier lable linked to an eri.xml and/or an spn-conf.xml located in /system/etc and or in /data right on the phone. No need to even decompile an APK, but the GS3 seems to be a little different as none of those tricks worked.
There is an eri.xml located in framework-res/res/xml/eri.xml. But nothing there referencing verizon or a sim card. Looks like a generic xml.

natethegreat86 said:
EDIT: Question for you guys are you running ICS touchwiz roms or aosp or what? I ask because I'm on a AOSP jelly bean rom and it might be different then what you guys have
I'm thinking this is going to require editing some smali files most likely, do me a favor and see if you have this file in your systemui.apk:
SystemUI\com\android\systemui\statusbar\phone\CarrierLabel.smali
Click to expand...
Click to collapse
I am running a stock deodexed TW ICS Rom.
Yes I have that xml in SystemUI but that smali should reference a string I would have thought? I thought the smali was to execute and not dictate what the actual phrase. I am far from an experienced coder though so what do I know.
Its late, I will look over this smali tomorrow when I have a little more time.
If we could get a few people digging for this we could probably find it in less than a week...
Thanks for the help!

Not sure if this will do it or not but seems like its definitely worth a try http://forum.xda-developers.com/showthread.php?t=1773879
As that xml is there in that location and the id is also there, I'll try it out on my rom when I get the chance as well and let you know.
---------- Post added at 03:58 AM ---------- Previous post was at 03:08 AM ----------
Well after some more searching I came across a post to remove the carrier name on jelly bean for the nexus and it actually worked for me, I don't know if this will work on touchwiz ICS or not but you may want to do a nandroid and try it. I used the second set of steps putting the eri.xml in /data and left the values blank and no more carrier label

natethegreat86 said:
Not sure if this will do it or not but seems like its definitely worth a try http://forum.xda-developers.com/showthread.php?t=1773879
As that xml is there in that location and the id is also there, I'll try it out on my rom when I get the chance as well and let you know.
---------- Post added at 03:58 AM ---------- Previous post was at 03:08 AM ----------
Well after some more searching I came across a post to remove the carrier name on jelly bean for the nexus and it actually worked for me, I don't know if this will work on touchwiz ICS or not but you may want to do a nandroid and try it. I used the second set of steps putting the eri.xml in /data and left the values blank and no more carrier label
Click to expand...
Click to collapse
I have tried those too...LOL. They seem to be for either ASOP only or JB. Just for giggles I tried them again to be sure and still no go.
Glad it worked for you though!

Derp I goofed I didnt give you the link in the second edit for what actually worked for me anyhow I'll give you what you need for your ics version.
Do a nandroid backup before making any changes just in case
1) Download eri.xml onto your desktop or some folder you will remember where it has been placed.
2) Open "eri.xml" with something such as NotePad or WordPad and edit everywhere you see "Whatever you want or delete this and nothing will show up". You can simply change the text or delete the text between the quotations and nothing will show up.
3) Save "eri.xml" and copy it to the root of your SD Card.
4) Open Root Explorer or an app similar, copy "eri.xml" from your SD card to "/data" directory.
5) Reboot, and Enjoy!
eri.xml http://www.mediafire.com/?edv0q6jvyh7hk4g

natethegreat86 said:
Derp I goofed I didnt give you the link in the second edit for what actually worked for me anyhow I'll give you what you need for your ics version.
Do a nandroid backup before making any changes just in case
1) Download eri.xml onto your desktop or some folder you will remember where it has been placed.
2) Open "eri.xml" with something such as NotePad or WordPad and edit everywhere you see "Whatever you want or delete this and nothing will show up". You can simply change the text or delete the text between the quotations and nothing will show up.
3) Save "eri.xml" and copy it to the root of your SD Card.
4) Open Root Explorer or an app similar, copy "eri.xml" from your SD card to "/data" directory.
5) Reboot, and Enjoy!
eri.xml http://www.mediafire.com/?edv0q6jvyh7hk4g
Click to expand...
Click to collapse
Tried that one too....no go.
Stupid Verizon.....

Grrr lol we will find a way for you eventually. Alright just for kicks try the eri.xml file I used for JB it just may work follow my thread over here http://forum.xda-developers.com/showthread.php?t=1897808

natethegreat86 said:
Grrr lol we will find a way for you eventually. Alright just for kicks try the eri.xml file I used for JB it just may work follow my thread over here http://forum.xda-developers.com/showthread.php?t=1897808
Click to expand...
Click to collapse
No go...strike #8....lol. Where the hell is this thing hiding?

Lmao dang was worth a try, this is harder for me now since i'm on cm10 aosp and I don't have a ics tw rom to look further into.
Alright one more try on one other thing that may work as well, definitely do a nandroid before you try this one as well.
1) Download spn-conf.xml file i have attached onto your desktop or some folder you will remember where it has been placed.
2) Open "spn-conf.xml" with something such as NotePad or WordPad and edit where you see Verizon Wireless.
3) Save "spn-conf.xml" and copy it to the root of your SD Card.
4) Open Root Explorer or an app similar, copy "spn-conf.xml" from your SD card to "System/etc" directory.
5) Reboot, and Enjoy!
spn.conf.xml http://www.mediafire.com/?qz6o28y822lxh5g

Strike #9.
The search continues.

Grrr lol I can't believe none of those worked, what rom are you running just curious?

natethegreat86 said:
Grrr lol I can't believe none of those worked, what rom are you running just curious?
Click to expand...
Click to collapse
Stock Deodexed Rom with a dozen or so self installed MODs. All I did was root, custom recovery, and start loading up a few favorite mods like:
Time toggle on/off
AM/PM toggle on/off
center clock
small am/pm
expanded setting for MMS
battery full removed
keyboard icon removed
...and a few others.
Otherwise, stock ROM rooted and deodexed.

Well you may want to consider going with a custom rom, things like this are so much easier on a custom rom because dev's enable these type of goodies . I don't know why anybody isn't on cm10 builds personally ive been running paranoid android for several weeks as my daily driver with no issues at all. But if you like the TW UI I can understand.

natethegreat86 said:
Well you may want to consider going with a custom rom, things like this are so much easier on a custom rom because dev's enable these type of goodies . I don't know why anybody isn't on cm10 builds personally ive been running paranoid android for several weeks as my daily driver with no issues at all. But if you like the TW UI I can understand.
Click to expand...
Click to collapse
well I have painfully gone through each and every XML in framework and none hold the key to removing the carrier name from the lockscreen. I know this because I have swapped each XML from a sprint rom (which does not have the carrier name on the lockscreen) with mine and the Verizon Wireless remained in place. I will go through some of the APKs in /system/app next and see what I can find. I was sure it would have been in framework though.

Didact74 said:
well I have painfully gone through each and every XML in framework and none hold the key to removing the carrier name from the lockscreen. I know this because I have swapped each XML from a sprint rom (which does not have the carrier name on the lockscreen) with mine and the Verizon Wireless remained in place. I will go through some of the APKs in /system/app next and see what I can find. I was sure it would have been in framework though.
Click to expand...
Click to collapse
I have a cool crisp $1 bill waiting to be donated to who ever can figure out how to make this go away on a stock, rooted, deodexed, ICS 4.04 ROM.
Seriously, I have just about exhausted all possibilities that I can think of.
Thanks for any help anyone can offfer!

[Q] Updater script and build.prop

Hello all!
I am looking to automate a couple things I do when I flash a new build of Cyanogen mod. Namely my couple edits of the build.prop.
Yes I do understand that some will disagree with me editing the build.prop, and some may say it's dangerous. I'm not here to discuss those matters.
What I do want to discuss is that I want to create a flashable zip that contains an updater script that will essentially add my changes for me before I even start Cyanogen mod and save me time and effort. I am very unfamiliar with such things and was hoping someone could give me a hand and point me in the right direction. That way I can do my own thing and ask less questions in the future.
P.S. Do note I do prefer to be taught than just handed a script with everything I want in it.

Zadeis said:
Hello all!
I am looking to automate a couple things I do when I flash a new build of Cyanogen mod. Namely my couple edits of the build.prop.
Yes I do understand that some will disagree with me editing the build.prop, and some may say it's dangerous. I'm not here to discuss those matters.
What I do want to discuss is that I want to create a flashable zip that contains an updater script that will essentially add my changes for me before I even start Cyanogen mod and save me time and effort. I am very unfamiliar with such things and was hoping someone could give me a hand and point me in the right direction. That way I can do my own thing and ask less questions in the future.
P.S. Do note I do prefer to be taught than just handed a script with everything I want in it.
Click to expand...
Click to collapse
Same here my friend same here.
But what i do to my ROMs when i have edits i wanna make is i extract the build.prop from the zip and edit what i want using Notepad++ then drag the build.prop back to the 7zip window to add it back to the zip and i flash. Simple as that
Now, if you really wanna get fancy, you could create an sh script that will read the build.prop AFTER flashing the ROM. It will read the build.prop, then change the things you want for you.. I dont really recommend this method as its not very simple and quite frankly im too lazy to create the sh script for myself. But i do believe it is possible.

elesbb said:
Same here my friend same here.
But what i do to my ROMs when i have edits i wanna make is i extract the build.prop from the zip and edit what i want using Notepad++ then drag the build.prop back to the 7zip window to add it back to the zip and i flash. Simple as that
Now, if you really wanna get fancy, you could create an sh script that will read the build.prop AFTER flashing the ROM. It will read the build.prop, then change the things you want for you.. I dont really recommend this method as its not very simple and quite frankly im too lazy to create the sh script for myself. But i do believe it is possible.
Click to expand...
Click to collapse
Interesting... I have tried the modify then drop the build.prop back into the zip, using 7-zip even, and it refuses to do so. hence me trying to do it in the manner of an updater script.

Zadeis said:
Interesting... I have tried the modify then drop the build.prop back into the zip, using 7-zip even, and it refuses to do so. hence me trying to do it in the manner of an updater script.
Click to expand...
Click to collapse
You could always make a second zip containing your modded build.prop. I remember having to do this with one of my edits on my S2 cause the ROM wouldnt set itself up with the changed Build.prop.

elesbb said:
You could always make a second zip containing your modded build.prop. I remember having to do this with one of my edits on my S2 cause the ROM wouldnt set itself up with the changed Build.prop.
Click to expand...
Click to collapse
Hmm maybe. I'll try using winrar to see if it makes any difference using the same drag and drop new build.prop method just to satisfy my curiosity.

Could it be an MD5 issue since you are "modifying" the zip?
Still Charged Up

Reilly1812 said:
Could it be an MD5 issue since you are "modifying" the zip?
Still Charged Up
Click to expand...
Click to collapse
Actually winrar worked. 7-zip can delete files from a CM archive but not add for some reason when winrar can do both. Not sure why but I still prefer 7-zip myself for everything else.
Though while this method does work I still wouldn't mind knowing how to add my changes via build.prop to streamline the entire process of updating CM.

Zadeis said:
Actually winrar worked. 7-zip can delete files from a CM archive but not add for some reason when winrar can do both. Not sure why but I still prefer 7-zip myself for everything else.
Though while this method does work I still wouldn't mind knowing how to add my changes via build.prop to streamline the entire process of updating CM.
Click to expand...
Click to collapse
7zip works for me without any issues..
Sent from my ASUS Transformer Pad TF300T using Tapatalk 2

[Q] Volume Rocker Wake for Nexus 5

Hi all, I'm hoping someone will be able to help me out.
I am running stock 4.4/rooted with TWRP 2.6.3.2 recovery.
I am looking for either a pre-packed mod or instructions of how to create the mod myself to allow the volume rocker to wake the Nexus 5.
I really miss this function from my Galaxy Nexus and I really don't like using the power button all the time...it just seems sensible to have this mod to spread the use of the buttons.
I'm sure people would agree that it is absolutely baffling that Google hasn't included this as standard in stock Android.
I used the following mod on my Galaxy Nexus:
[MOD][JWR66V] Add Screen Lock button to Statusbar - by: evilisto
I realise this is mainly aimed at adding the screen lock button but it also includes an option to enable volume rocker wake.
I then obviously used the options included in CM after this.
I have done various Google searches and searched the xda forums, there are various references and mod instructions, but nothing that refers to Nexus 5.
I also know that various custom ROMs have this function already, but I am wary of flashing anything currently with all the custom recovery problems people are having (including myself...I've already had to restore phone with factory image once), going to wait until recoveries are more stable.
Basically, I am hoping someone can point me in the direction of this mod if it already exists, or if not, instructions of how to carry out the mod myself. I would be interested to learn how to do it in fact, it would be rather satisfying to carry out the mod myself!
Many thanks in advance for your help everyone!!
Sent from my Nexus 5 using Tapatalk

I haven't seen any patch for this yet, but a bunch of roms in the dev section have this built in. So either wait for a patch or install the whole rom.

peachpuff said:
I haven't seen any patch for this yet, but a bunch of roms in the dev section have this built in. So either wait for a patch or install the whole rom.
Click to expand...
Click to collapse
Thanks for the reply, as I said though I am wary of flashing ROMs at the moment due to all the problems people are having with recoveries.
I am quite happy to create the mod myself, and share it with others if they would like to use it, but I need instructions of how to do it though.
I believe there are two different system files that need modifying to produce this effect?
It also seems that it is possible on both odexed and deodexed systems, but I am not 100% sure.
If it means the system needs to be deodexed for it to work, then you are right, I will be better to just take the plunge and flash a ROM with the mod included.
As there are a number of ROMs with the mod included, there must be a process to adding this functionality, and I would be very interested to find out how it is done. It is a learning exercise just as much as anything else for me.
Sent from my Nexus 5 using Tapatalk

i remember when i was using my old phone, replace the file "android.policy.jar" udner system/framework
of coz thenew android.policy.jar is a mod from other rom with the function "volume wake". not sure if this helps...
got this link, not try yet.
[MOD] Volume wake mod for Android 4.4
http://forum.xda-developers.com/showthread.php?p=47691484

hk_aquarius said:
i remember when i was using my old phone, replace the file "android.policy.jar" udner system/framework
of coz thenew android.policy.jar is a mod from other rom with the function "volume wake". not sure if this helps...
got this link, not try yet.
[MOD] Volume wake mod for Android 4.4
http://forum.xda-developers.com/showthread.php?p=47691484
Click to expand...
Click to collapse
Ah yes, I saw this too whilst searching for information...
Do we need to just replace the android.policy.jar with modified version or are there other steps to carry out, I have noticed other threads mentioning editing both...
/system/build.prop
and
/system/usr/keylayout/Generic.kl
Are these edits required as well in 4.4/Nexus 5 or can we just use modified android.policy.jar?
If this is the case, in theory you could pull this file from a custom ROM with the volume rocker wake mod included and replace it in your own system files and reboot?
Also...would these files taken from a deodexed ROM work on an odexed factory image?
Sent from my Nexus 5 using Tapatalk

for my previous experience on u8800 (4.0.4) and mi2s (4.1.2), just need to replace "android.policy.jar" and remove odex file, then reboot; thus to enable volume rocker wake.
please backup the old set, .jar and odex file. in case of failure, will need to use adb to connect and then restore.

hk_aquarius said:
for my previous experience on u8800 (4.0.4) and mi2s (4.1.2), just need to replace "android.policy.jar" and remove odex file, then reboot; thus to enable volume rocker wake.
please backup the old set, .jar and odex file. in case of failure, will need to use adb to connect and then restore.
Click to expand...
Click to collapse
That's interesting, thanks.
I assume when you reference the odex file you are referring to 'android.policy.odex'?
If this is the case, it does raise another question...
All the other files in framework are odexed, will the deodexed version of android.policy.jar work side by side with these?
Sent from my Nexus 5 using Tapatalk

wilskywalker said:
That's interesting, thanks.
I assume when you reference the odex file you are referring to 'android.policy.odex'?
If this is the case, it does raise another question...
All the other files in framework are odexed, will the deodexed version of android.policy.jar work side by side with these?
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
I am eager to give this a try but still need to know the answer to the above questions?
Basically, will adding a deodexed (android.policy.jar) element into the stock odexed framework cause issues?
Many thanks
Sent from my Nexus 5 using Tapatalk

I tried it and it didnt really work, i pulled the jar file from a rom and copied it over and got some strange description when i pressed the power button, the vibration motor would go off every 5 seconds too.
I made sure to pull it from a ktm but perhaps the dev made some other changes that weren't compatible with my stock rom.
Don't be discouraged though, as long as you backup you'll be fine.
Sent from my Nexus 5

peachpuff said:
I tried it and it didnt really work, i pulled the jar file from a rom and copied it over and got some strange description when i pressed the power button, the vibration motor would go off every 5 seconds too.
I made sure to pull it from a ktm but perhaps the dev made some other changes that weren't compatible with my stock rom.
Don't be discouraged though, as long as you backup you'll be fine.
Sent from my Nexus 5
Click to expand...
Click to collapse
Thanks for giving this a try, normally I would already have tried myself, but as I said I have already had a complete nightmare with using custom recoveries on this phone so am a little more reluctant to experiment than usual.
I did wonder if this would cause issues. As you said in your post, it looks as though other changes were made to the android.policy.jar you used, that is my worry with any version of this file pulled from another ROM as I don't know what else this file is used for so there could be multiple other changes made that wouldn't then be compatible with a stock factory image.
I also still wonder if the odexed and deodexed files will work properly together as well? Is it the case that this mod is only possible on a deodexed system?
There must be a way of making this mod myself though, I would be happy to learn how to do it and make the changes myself, does anyone know how to do this, or can they point me in the direction of instructions of how to do so?
As always, thanks everyone!

Alright i finally got volume wake working but in a completely different way.
Install xposed framework http://forum.xda-developers.com/showpost.php?p=47771876&postcount=5621
Install modaco module http://d-h.st/PeV
Run module, goto htc one settings and enable volume wake, reboot and voila it works
Also suggest installing gravity box and xblast tools modules.

peachpuff said:
Alright i finally got volume wake working but in a completely different way.
Install xposed framework http://forum.xda-developers.com/showpost.php?p=47771876&postcount=5621
Install modaco module http://d-h.st/PeV
Run module, goto htc one settings and enable volume wake, reboot and voila it works
Also suggest installing gravity box and xblast tools modules.
Click to expand...
Click to collapse
Very interesting work round, I will have to give it a go, thanks
I would still like to know how this mod is achieved via system edits rather than installing apk's, if anyone is aware? I am interested to learn!
Many thanks all
Sent from my Nexus 5 using Tapatalk

wilskywalker said:
That's interesting, thanks.
I assume when you reference the odex file you are referring to 'android.policy.odex'?
If this is the case, it does raise another question...
All the other files in framework are odexed, will the deodexed version of android.policy.jar work side by side with these?
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
i just tried it on nexus 5, it works!

hk_aquarius said:
i just tried it on nexus 5, it works!
Click to expand...
Click to collapse
Hi there,
Can you please give some information about your system (odexed or deodexed/stock factory image or custom ROM etc)?
Also, could you outline exactly what you have done to get this working and what files you used and or modified?
This would be really useful...my plan if I can find out how this is done is to package it for others to use too...I cannot be the only person that wants this mod.
Many thanks for your help!
Sent from my Nexus 5 using Tapatalk

wilskywalker said:
Hi there,
Can you please give some information about your system (odexed or deodexed/stock factory image or custom ROM etc)?
Also, could you outline exactly what you have done to get this working and what files you used and or modified?
This would be really useful...my plan if I can find out how this is done is to package it for others to use too...I cannot be the only person that wants this mod.
Many thanks for your help!
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
OK, i use stock 4.4 Kitkat on my Nexus 5 out of the box.
Download the mod android.policy.jar from the link below: (credit goes to javi851, thanks...)
http://forum.xda-developers.com/showthread.php?p=47691484
transfer this file to the root of /sdcard
I suppose bootloader is "unlocked" and root access is "ready".
use Root Explorer
go to system/framework
rename android.policy.jar to android.policy.jar.ORG
rename android.policy.odex to android.policy.odex.ORG
copy the mod android.policy.jar to system/framework
** make sure the filename is android.policy.jar
change permission to rw-r--r--
turn off the phone, then turn it on
it will take a while, it says to upgrade android files 100+
leave it there until it completes.
try pressing the power button to turn it off, then press either volume button and you can wake the screen for that.
hope my try helps people who need volume rocker wake function!

hk_aquarius said:
OK, i use stock 4.4 Kitkat on my Nexus 5 out of the box.
Download the mod android.policy.jar from the link below: (credit goes to javi851, thanks...)
http://forum.xda-developers.com/showthread.php?p=47691484
transfer this file to the root of /sdcard
I suppose bootloader is "unlocked" and root access is "ready".
use Root Explorer
go to system/framework
rename android.policy.jar to android.policy.jar.ORG
rename android.policy.odex to android.policy.odex.ORG
copy the mod android.policy.jar to system/framework
** make sure the filename is android.policy.jar
change permission to rw-r--r--
turn off the phone, then turn it on
it will take a while, it says to upgrade android files 100+
leave it there until it completes.
try pressing the power button to turn it off, then press either volume button and you can wake the screen for that.
hope my try helps people who need volume rocker wake function!
Click to expand...
Click to collapse
Hi mate,
Really good instructions thanks.
Can I ask what the significance of renaming the .jar and .odex files to .jar.ORG and .odex.ORG is?
Many thanks
Sent from my Nexus 5 using Tapatalk

wilskywalker said:
Hi mate,
Really good instructions thanks.
Can I ask what the significance of renaming the .jar and .odex files to .jar.ORG and .odex.ORG is?
Many thanks
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
just in case for fallback, as i am afraid i will not get OTA upgrade afterwards.
.ORG means original files for me.

hk_aquarius said:
just in case for fallback, as i am afraid i will not get OTA upgrade afterwards.
.ORG means original files for me.
Click to expand...
Click to collapse
Ah right thanks. So basically a way of backing up the files in their original file location so the system ignores them.
A very good idea my friend, very similar to Root File Explorer, it backs up system files you make changes to by renaming the original file with a .bak suffix.
I have asked the OP in the thread you linked to what changes he made to the android.policy.jar and how he did it, I am hoping to learn how to actually make the changes myself and create a mod for others to use too.
I'm going to give your process a go in the mean time though, thanks.
Sent from my Nexus 5 using Tapatalk

hk_aquarius said:
just in case for fallback, as i am afraid i will not get OTA upgrade afterwards.
.ORG means original files for me.
Click to expand...
Click to collapse
Hi buddy,
I've tested your method and it is working fine, wakes the phone normally and from deep sleep. Two days of use and no other problems.
I'm going to try and create a flashable zip with this file, just need to work out the edify commands to rename the original files rather than delete, so people have a backup of their files.
Sent from my Nexus 5 using Tapatalk

wilskywalker said:
Hi buddy,
I've tested your method and it is working fine, wakes the phone normally and from deep sleep. Two days of use and no other problems.
I'm going to try and create a flashable zip with this file, just need to work out the edify commands to rename the original files rather than delete, so people have a backup of their files.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
I would advise against posting an android.policy.jar from a different device since there are some differences within the policy jar between the two. It's a little sad that the other guy ignored a request for what the actual edit is considering it's so figgin simple. After diff'ing some other jar files, I found what the edit is. All you need to do is remove 2 lines from PhoneWindowManager.smali. Attached pic shows 2 lines that need removal (stock is on the right).
good day.