Hey all, I'm trying to figure out how to get some brightness settings for the touch key brightness to stick. I've used LG 2x Notifications and O2x Touch Key Brightness, and they both work up until the point where i put the phone to sleep by tapping the power button. As soon as I wake it up, the brightness goes straight to zero unless i head back to the app and raise it up again. And if i uninstall the apps, the brightness on my keys stay off until i re-flash or reinstall the app again. Help!
My issue is a little different but similar. It worked fine for me on every basic gingerbread rom, but when I switched to a cm7 based rom the lights change with the brightness of the screen. I turned off all the light notifications but it did not help.
If anyone has any ideas, I'd love to hear them.
What rom?
Sent from my LG-P999 using XDA
redmonke255 said:
What rom?
Sent from my LG-P999 using XDA
Click to expand...
Click to collapse
On SinghUI but it doesn't have built-in LED notifications, if that's what you're getting at.
If the setting from one of those apps doesn't stick, then it's most likely being set by your ROM or Kernel. Have you tried checking if you get the same issue with other ROMs?
@jcbofkc That's a built-in setting that can't really be changed unless you get a custom ROM or Kernel cooked up to remove the link between the brightnesses.
xBIGREDDx said:
If the setting from one of those apps doesn't stick, then it's most likely being set by your ROM or Kernel. Have you tried checking if you get the same issue with other ROMs?
@jcbofkc That's a built-in setting that can't really be changed unless you get a custom ROM or Kernel cooked up to remove the link between the brightnesses.
Click to expand...
Click to collapse
90% sure the ROM doesn't have built in notifications. I'm noticing now that very rarely the settings do stick. Perhaps there is a way to force the app to stay in memory?
rrroach said:
90% sure the ROM doesn't have built in notifications. I'm noticing now that very rarely the settings do stick. Perhaps there is a way to force the app to stay in memory?
Click to expand...
Click to collapse
That wouldn't work. All that those apps do is write a number from 0-20 to the text file:
/sys/devices/platform/star_touch_led/wled
in your root file system.
When you read the file, it shows you the current output to the LEDs (from 0uA to 2000uA).
When you write to the file, it interacts with the Kernel and sets the brightness.
The Touch Key Lights type apps, all they do is when you move the slider they write a value to that file, and that's it. The only reason it wouldn't stick is if your ROM or Kernel is changing the value in the background. For example it will set it to 0 when you turn the screen off, and then it should set it back to wherever it was before when you turn the screen on again.
The closest you could get is to take the source for LG Touch LED Notifications and modify it to set the brightness every few seconds or something, but that probably wouldn't be too good for your battery life.
Based on your symptoms it appears that either your ROM or your phone doesn't really handle the modifying of the brightness very well. It looks like SinghUI does use a kernel from CM7, so I don't think your kernel is the problem. I'd suggest flashing the most recent CM7.2 RC, and seeing if you have the same problem there. CyanogenMod will change your LED brightness based on your screen brightness though.
EDIT: Ignore all that for a moment, try this first. It is a post from January 21st in the SinghUI thread, so it might not work now, but go ahead and try it: http://forum.xda-developers.com/showpost.php?p=21652744&postcount=293
Also I'd suggest posting in the SinghUI thread as everyone there is using your ROM, so they might be able to help better.
xBIGREDDx said:
That wouldn't work. All that those apps do is write a number from 0-20 to the text file:
/sys/devices/platform/star_touch_led/wled
in your root file system.
When you read the file, it shows you the current output to the LEDs (from 0uA to 2000uA).
When you write to the file, it interacts with the Kernel and sets the brightness.
The Touch Key Lights type apps, all they do is when you move the slider they write a value to that file, and that's it. The only reason it wouldn't stick is if your ROM or Kernel is changing the value in the background. For example it will set it to 0 when you turn the screen off, and then it should set it back to wherever it was before when you turn the screen on again.
The closest you could get is to take the source for LG Touch LED Notifications and modify it to set the brightness every few seconds or something, but that probably wouldn't be too good for your battery life.
Based on your symptoms it appears that either your ROM or your phone doesn't really handle the modifying of the brightness very well. It looks like SinghUI does use a kernel from CM7, so I don't think your kernel is the problem. I'd suggest flashing the most recent CM7.2 RC, and seeing if you have the same problem there. CyanogenMod will change your LED brightness based on your screen brightness though.
EDIT: Ignore all that for a moment, try this first. It is a post from January 21st in the SinghUI thread, so it might not work now, but go ahead and try it: http://forum.xda-developers.com/showpost.php?p=21652744&postcount=293
Also I'd suggest posting in the SinghUI thread as everyone there is using your ROM, so they might be able to help better.
Click to expand...
Click to collapse
Thanks for the link. It turns out that the ROM does have led notifications. However, disabling them didn't help the problem. :/ the g2x has just been an awful experience for me! :/
Related
Alright so Yesterday I installed the android os on my touch pro (raph 500)
i orginally have windows mobile 6.5 which is preety fast
but android is really slow!
i turned off all the settings which i would think it used alot of memory but still no help, so i started seeing videos on overclcking?
can someone explain to me on how to do this,
with links to the download
i really need to speed this up ,it would be amazing if it worked.
also if you give me a response that helps me , ill donate 10.00+ to you .
I do not require funds as I enjoy helping out!
From THIS thread and THIS post:
Overclocking
acpuclock.oc_freq_khz=XXXXXX ( suggested 600000-640000 )
but it is very unstable if you try to get higher than 650000-700000
Click to expand...
Click to collapse
Basically, you add that to the startup.txt file somewhere between the parentheses with an added space between the next command. Keeping in mind, with added OC, you may and may not notice a difference in stability. I honestly never use OC and I am using FroYo from THIS thread. Additionally you can try out Gingerbread Alpha from THIS thread. Please leave feedback in their respective threads, thanks!
n-Joie! (Enjoy)
thanks but this is my startup text :
set ramsize 0x10000000
set ramaddr 0x10000000
set mtype 2182
set KERNEL zImage
set initrd initrd.gz
set cmdline "lcd.density=210 msmvkeyb_toggle=off physkeyboard=raph board-htcraphael-navi.wake=0 gsensor_axis=2,-1,3 acpuclock.force_turbo=1"
boot
Click to expand...
Click to collapse
so which am i supposed to edit, sorry im a noob lol
& u said that was the one you used,
is it fast?
Actually, I can't use that one because I have an at&t Fuze. If you have a RAPH500, you might want to use the following:
set ramsize 0x10000000
set ramaddr 0x10000000
set mtype 2182
set KERNEL zImage
set initrd initrd.gz
set cmdline "lcd.density=210 msmvkeyb_toggle=off physkeyboard=raph board-htcraphael-navi.wake=0 gsensor_axis=2,-1,3 pm.sleep_mode=1 acpuclock.oc_freq_khz=XXXXXX"
boot
Click to expand...
Click to collapse
Where XXXXXX is equal to a value between 600000-640000
Additional note: make sure you type something like 600000 or any value up to 640000
lol thanks im trying to see if theres a difference in speed.
but you used froyo?
is that running fast?
It's running fine with sync and a few other apps running in the background. I would be mindful of livewallpaper and HQ video at the moment as this project is currently still under development, at best. At least that is what I have noticed as far as performance is considered. I have also run a stripped Gingerbread alpha build (the one I linked you to earlier) and it is running faster/smoother than FroYo. To be expected without all the bells and whistles...
NOTE: Speed is relative to performance at the moment. Hence why I say it's still under development...
intresting ill test that out in about 15 mins
but does yours take a long time to come out of sleep mode?
Hmmm, that might be the notorious sleep of death SOD. I usually do something that most don't like but I sort of turn off the screen time out by first making the screen time out greater than 10 or 30 minutes. After that it should make things easier as far as disabling the auto back light/screen timeout feature. Keep in mind this is only a work around, I believe there is mention of actually fixing this issue. You'll need to download a free app called batterybooster (use the link if you want to read up on it a little). Once installed, run it and look for the far right icon and tap it. Set the timeout to Never and you'll notice a decent performance enhancement in the screen off and screen on.
NOTE: You will need to manually turn it off from here-on. You can try to play around with the setting but I find it somewhat problematic. Meaning that if you enable the timeout, it might and it might not work.
alright well i tried the gingerbread and that didnt work it lagged .
i tried froyo , it was amazing then i found out wifi didnt work
so now im back to the regular android one i had before ill be trying to see if theres a difference now that i "overclocked" it .
but thanks for all the help.
ill post back if i need something!
Odd, wifi(wap not wep) works for me... Must be a random occurrence? Have you attempted to update any files and are you using OC? Probably best to stick to a stock-like startup till you get a good feel of most of the basic functions, which may or may not include wifi, gps, 3d and camera; these should be on the "to be worked on" list of things for the devs to complete.
R^7Z said:
Odd, wifi(wap not wep) works for me... Must be a random occurrence? Have you attempted to update any files and are you using OC? Probably best to stick to a stock-like startup till you get a good feel of most of the basic functions, which may or may not include wifi, gps, 3d and camera; these should be on the "to be worked on" list of things for the devs to complete.
Click to expand...
Click to collapse
it works for you?
wth!
and i havenet updated any files on the deive.
no im not using overclock on this onr,
but on another android version which is on my sd card i am
& is there a way i can lock my screen so it doesn't touch any buttons in my pocket &kepp it from going into SOD .
ndnmaster096 said:
it works for you?
wth!
and i havenet updated any files on the deive.
no im not using overclock on this onr,
but on another android version which is on my sd card i am
& is there a way i can lock my screen so it doesn't touch any buttons in my pocket &kepp it from going into SOD .
Click to expand...
Click to collapse
NVM I got the wifi to work now .
Glad to hear about the wifi success story I don't know if I could walk you through that as it seems that wifi can be temperamental ( or just mental )
The only way I could get out of the SOD issue was to try for that work around (setting it to never timeout with the app mentioned) and to set a pattern unlock
R^7Z said:
Glad to hear about the wifi success story I don't know if I could walk you through that as it seems that wifi can be temperamental ( or just mental )
The only way I could get out of the SOD issue was to try for that work around (setting it to never timeout with the app mentioned) and to set a pattern unlock
Click to expand...
Click to collapse
well i set it to never timeout and i have a lock pattern
but since it never times out it wont lock .
also now im starting to notice froyo is rebooting for some weird reason automatically .
Calm down, that is kind of "usual behavior" . There are quire a few things going on and the OS is attempting to "handle it". Sometimes it can't and just quits instead of freezing up ( which would be the lesser of two evils ). To get it to lock, you will have to turn it off manually (power button). Unfortunately, I think if the keyboad slides out, it self unlocks (kind of a self defeating purpose, more or less). If you turn the screen off and wait like 10 seconds then turn the screen on (power key), you should see the lock. I can't say for sure but it does work for me. I don't really have much time for troubleshooting today, as I am at work currently but do look over the threads I linked you to earlier if at all possible.
okay so i turned it off using the power button and it booted to windows mobile (odd)
then i tried running haret.exe & got this message:
"The file HARET cannot be opened. Either it is not signed with a trusted certificate, or one of its components cannot be found. IF the problem persists, try reinstalling or restoring the file."
im not sure what to do.
i tryed reformatting the card and installing fresh files, which didnt work so now im left questioned?
When you say you turned it off, did you hold the button or just press it once? If you pressed it once, then, that is definitly not "usual" behavior. I recall having that issue once upon a time but for the life of me, I don't recall what I did to recover from it. However, it sounds like you are attempting to run from a shortcut that references the program(haret) that is no longer there. To resolve this, I need you to confirm that you are running from the microSD and not a shortcut. Also, you aren't formatting under windows, right? If you are formatting from windows, that would be a "no-no"
Find something like the HP tool (can be googled) that everyone else talks of or even something like the free version of partition wizard should work.
i held the button and it gave me options
1) airplane mode
2)shutoff
3)vibrate
i did try to make a shortcut but i deleted it and now when i checked i was running it from the actual application.
lastly, i did format from windows but i downloaded hp format tool
and formated my device in quick format.
reinstalled the programs and it still gave me the same error message,
please help, i really miss android =(
Try deleting data.img and letting it recreate the file. To clarify about the screen off issue, when you press the power button once (not hold), what does it do? Also, which kernel package are you using and have you attempted to download a newer kernel package yet?
Also, try THIS kernel package; I got it from THIS site. It looks like that kernel package is specific to our devices.
What files do i need to adjust to make my phone brighter when using auto brightness my phone is way too dim.
It seems like the max level of auto brightness is whatever the slider was set at before choosing "auto".
Try turning off auto, running the slide to where you want it and then turning auto brightness back on.
Well just tried that and still no luck ....Guess Im gonna have to change ROMs
david032766 said:
Well just tried that and still no luck ....Guess Im gonna have to change ROMs
Click to expand...
Click to collapse
As far as I know, brightness levels are controlled by kernel, not ROM. So if u like the ROM, try changing the kernel.
diablo009 said:
As far as I know, brightness levels are controlled by kernel, not ROM. So if u like the ROM, try changing the kernel.
Click to expand...
Click to collapse
Hmmmm well coredroid is too dark with mdj kernel or any other i have tried and mdj vivo is just right with the same mdj kernel ..... So i dunno might just give up on coredroid
Sent from my Desire HD using XDA Premium App
david032766 said:
Hmmmm well coredroid is too dark with mdj kernel or any other i have tried and mdj vivo is just right with the same mdj kernel ..... So i dunno might just give up on coredroid
Sent from my Desire HD using XDA Premium App
Click to expand...
Click to collapse
Try gingerbeast 2.1.1 or Android Revolution 5.1.6. I used both, and both are good.
OP, if you're going to be trying out different ROMs be sure to check out CyanogenMod. It has a ton of tweakable auto brightness settings that simply don't exist in most ROMs. Among the many settings, you can dial in the exact screen brightness you want for a given ambient light level. Once you get the settings to your liking, there will be very few (if any) situations where you'll need to manually adjust the brightness; it will be done automatically the way you want instead of the way the ROM developer likes it.
henrybravo said:
OP, if you're going to be trying out different ROMs be sure to check out CyanogenMod. It has a ton of tweakable auto brightness settings that simply don't exist in most ROMs. Among the many settings, you can dial in the exact screen brightness you want for a given ambient light level. Once you get the settings to your liking, there will be very few (if any) situations where you'll need to manually adjust the brightness; it will be done automatically the way you want instead of the way the ROM developer likes it.
Click to expand...
Click to collapse
CM7 was the first rom i used after root ..... If it wasnt for giving up full screen MMS messages i'd still be using it.
david032766 said:
CM7 was the first rom i used after root ..... If it wasnt for giving up full screen MMS messages i'd still be using it.
Click to expand...
Click to collapse
That issue appears to be fixed...I can open mms pictures full screen in the stock messaging app as well as chompSMS. Running 7.0.3 stable that came out a few weeks ago.
cool ill check iy out again ....thanks
On the sensation is it possible to configure the LEDs to blink until you read the txt message for example. I think it is currently set to blink for about a minute. On the HD2 I was able to make registery changes to do this.
I am on a stock 1.50 rom with stock kernel.
I think faux has changed the led blink time, you'll have to look at his kernel. It requires a change in the kernel.
Sent from my HTC Sensation 4G
Show's kernel also does this.
Just spotted this post from Faux. Exactly what I am looking for just need to find out how to do it now
Originally Posted by faux123
Ah crap.. forgot about that...
BTW, it's not clean to hack the LED driver... much cleaner to hack the ROM... ask your ROM devs to hack the LED timer since it is SET by the ROM and kernel only does the blinking part....
So as you can see, by hacking the blinking part, it is an Ugly hax.. Just have the ROM tell the kernel to blink for longer...
Does anybody know how to tweak the rom to get the leds blinking continiously?
Any ideas?
This might do the trick http://forum.xda-developers.com/showthread.php?t=1407403&highlight=phone+notifier
I currently use noLed. Our led is crap IMO lol...
https://market.android.com/details?...lt#?t=W251bGwsMSwxLDEsImNvbS5sZWQubm90aWZ5Il0.
Works fine for me. I set it where it shuts off in 5 mins though.
Here is BLN control
https://market.android.com/details?id=neldar.bln.control.free&feature=search_result
I tried it using the stock kernel and it was a no go. I think I'll play with kernels to see if any work for our phones. Anyone else have a go at this app yet?
Those arnt quite what I am looking for. Faux123 suggested that you should be able to edit a file in the rom its self to control the time of the leds. I think you can make it stay on by setting it to 0. I just cant remember what file to edit.
As far as I know the kernel only defines the colour of the led and the time between each flash, not the actual length of time it flashes for. It is the rom that defines that. I am continuing to look and see if I can find the file.
i think this is default from htc sense o.0
otherwise - with miui you can set however you want
GhostXSeries said:
Those arnt quite what I am looking for. Faux123 suggested that you should be able to edit a file in the rom its self to control the time of the leds. I think you can make it stay on by setting it to 0. I just cant remember what file to edit.
As far as I know the kernel only defines the colour of the led and the time between each flash, not the actual length of time it flashes for. It is the rom that defines that. I am continuing to look and see if I can find the file.
Click to expand...
Click to collapse
Bricked kernel will keep your led flashing till you read your messages or emails.
Sent from my HTC Sensation 4G using XDA App
Sorry the title couldn't describe much, but this situation with my VZWGS3 is a special one. I have not been able to find a situation similar to mine by searching this forum or the internet.
My problem, is that when i wake my device with the power button, it automatically ducks my brightness down to minimum. In my brightness settings, I disabled auto brightness and I have the slider at 100%. I have to tickle the brightness slider to get it to come back up to 100% brightness. My first thought is that the lock screen is forcing the screen to dim. It isn't even a smooth transition. When I do enable auto brightness, it still dims the screen on wake, but it only changes when the ambient lighting changes (thus causing auto brightness to kick in) and then it looks normal. The result of this problem is that I cant see my screen when i turn it on outside or in bright rooms. This does not have anything to do with battery, because this happens even when it is plugged in and at 100%
I'm on a deodexed stock pre-rooted touchwiz rom. Baseband version: I535VRBMF1. Android Version: 4.1.2. Kernel: 3.0.31-1152558 [email protected] #1
Android build number: JZO54K.I535VRBMF1
Later on today, I can make a video of this happening to better describe the issue. For now, just let this ponder in your heads.
Also, is it possible to debug which apps cause something to happen to the system? For instance, scan to see which apps & processes are controlling brightness.
jtcressy said:
Also, is it possible to debug which apps cause something to happen to the system? For instance, scan to see which apps & processes are controlling brightness.
Click to expand...
Click to collapse
Oops accidentally thanked you haha. But back on topic, I dont know of a way to debug that type of problem. what i would suggest since you're rooted is to make a backup in Titanium and a Nandroid. Then try doing a factory reset. That is a very strange problem indeed..
Sent from my Galaxy S3
TheKucho said:
Oops accidentally thanked you haha. But back on topic, I dont know of a way to debug that type of problem. what i would suggest since you're rooted is to make a backup in Titanium and a Nandroid. Then try doing a factory reset. That is a very strange problem indeed..
Sent from my Galaxy S3
Click to expand...
Click to collapse
Thanks for your reply. I'll probably try a factory reset. Can't hurt. There's a question I have about TiBu when it restores apps, so i'll ask that in another forum before I begin the process. In the meantime, this thread is still open to ideas.
Ok. This is a bit of a *facepalm* moment. Let it be noted that the main reason my GS3 was having this problem was the app called "Light Flow". I came upon this conclusion by giving the safemode of android a try. The problem immediately disappeared, so I realized it was an app. I thought a bit about what app could be controlling the lights of the phone, and the lightbulb went off. Uninstalled Light Flow and the problem stopped. I guess I kinda miss the custom notification light, which is why I downloaded Light Flow in the first place because I miss some of the notification light customization features on other Cyanogen based roms. Later on I heard from a buddy that Light Flow really screws up some things on the GS3.
jtcressy said:
Ok. This is a bit of a *facepalm* moment. Let it be noted that the main reason my GS3 was having this problem was the app called "Light Flow". I came upon this conclusion by giving the safemode of android a try. The problem immediately disappeared, so I realized it was an app. I thought a bit about what app could be controlling the lights of the phone, and the lightbulb went off. Uninstalled Light Flow and the problem stopped. I guess I kinda miss the custom notification light, which is why I downloaded Light Flow in the first place because I miss some of the notification light customization features on other Cyanogen based roms. Later on I heard from a buddy that Light Flow really screws up some things on the GS3.
Click to expand...
Click to collapse
Yeah, I tried light flow a while back and wound up uninstalling it for weird behavior.
Sent from my SCH-I535 using xda app-developers app
Hi all It might not sound wise but I just got myself an second hand Infuse 4G for a nice price, and like every device I've owned, got CM running on it in hours. However, there's something that bugs me for a bit, and that is the touch key backlight.
On other devices I have, CM's Settings-Buttons part controls touch key backlight well, leaving it on for whatever duration or turning it off. But on all ROMs I've tried till now (CM10, CM10.2, CM11), either this option is absent (CM10's Infuse Settings is incomplete), or the option doesn't work properly:
1) When I set the keys to light up, they don't light up automatically when I wake the phone up from sleep, I'll have to press the keys to activate them.
2) When I turn the light off, the light indeed goes off immediately, but when I press any of the keys, they come back to life again and simply stay on, ignoring the settings.
I remembered that on many HTC phones there was a way to manually control button backlight behavior by altering values of a certain file in /sys/class/..., so after some work, I found the file: /sys/devices/virtual/misc/melfas_touchkey/brightness, and indeed, setting it to 0 will make the light go off. The thing that doesn't work out is that it won't persist - pressing any of the keys still make the light come back. I've set the permission to 0444 and even made a init.d script for that, and I can guarantee that the script itself is working properly, but still it can't keep the light under control... And now I'm stuck.
1) Is there a way to make the option in Infuse Settings or Settings-Buttons work as they should?
2) Any separate app that could also do this?
3) Why won't my manual adjustment persist?
Answering any of these questions would be of help, thank you in advance!
AndyYan said:
Hi all It might not sound wise but I just got myself an second hand Infuse 4G for a nice price, and like every device I've owned, got CM running on it in hours. However, there's something that bugs me for a bit, and that is the touch key backlight.
On other devices I have, CM's Settings-Buttons part controls touch key backlight well, leaving it on for whatever duration or turning it off. But on all ROMs I've tried till now (CM10, CM10.2, CM11), either this option is absent (CM10's Infuse Settings is incomplete), or the option doesn't work properly:
1) When I set the keys to light up, they don't light up automatically when I wake the phone up from sleep, I'll have to press the keys to activate them.
2) When I turn the light off, the light indeed goes off immediately, but when I press any of the keys, they come back to life again and simply stay on, ignoring the settings.
I remembered that on many HTC phones there was a way to manually control button backlight behavior by altering values of a certain file in /sys/class/..., so after some work, I found the file: /sys/devices/virtual/misc/melfas_touchkey/brightness, and indeed, setting it to 0 will make the light go off. The thing that doesn't work out is that it won't persist - pressing any of the keys still make the light come back. I've set the permission to 0444 and even made a init.d script for that, and I can guarantee that the script itself is working properly, but still it can't keep the light under control... And now I'm stuck.
1) Is there a way to make the option in Infuse Settings or Settings-Buttons work as they should?
2) Any separate app that could also do this?
3) Why won't my manual adjustment persist?
Answering any of these questions would be of help, thank you in advance!
Click to expand...
Click to collapse
As far as I know, the Infuse hasn't had effective backlight control since Gingerbread. If you wanna go back to that, it should work fine. Otherwise, all of the newer ROMs are using an outdated kernel that doesn't support backlight control. I highly doubt we will see it working again since very few people are still using the Infuse.
niral7 said:
As far as I know, the Infuse hasn't had effective backlight control since Gingerbread. If you wanna go back to that, it should work fine. Otherwise, all of the newer ROMs are using an outdated kernel that doesn't support backlight control. I highly doubt we will see it working again since very few people are still using the Infuse.
Click to expand...
Click to collapse
I can bear returning to GB and I did, but I've tried both stock UCLB3 and CM7, and neither contains any settings about button backlight...
Sent from Google Nexus 4 @ CM11
[WARNING: XDA Premium 4.0.13 lacks Signature function - do not update]
AndyYan said:
I can bear returning to GB and I did, but I've tried both stock UCLB3 and CM7, and neither contains any settings about button backlight...
Sent from Google Nexus 4 @ CM11
[WARNING: XDA Premium 4.0.13 lacks Signature function - do not update]
Click to expand...
Click to collapse
The Infuse supports backlight control in gingerbread. In order to use it, you'll have to download a third party app in the play store. I don't think CM7 will support it either.
niral7 said:
The Infuse supports backlight control in gingerbread. In order to use it, you'll have to download a third party app in the play store. I don't think CM7 will support it either.
Click to expand...
Click to collapse
Not even CM7? No dice then, I guess... Thanks for the tip anyway.
Sent from Google Nexus 4 @ CM11
[WARNING: XDA Premium 4.0.13 lacks Signature function - do not update]