I think we need a spare parts for the nexus one. Please add your wishes too.
Notification:
Notification LED flash rate
Notification LED color for Each Google Experience App
Check box for Blink or Glow
Screen Wake up:
Use default (power button) or box with provide your own keystroke. i.e. trackball, double trackball, volume down, volume down twice... ect.
Check box for using the slide unlock or not
Screen sleep:
Long press OR extended long press Trackball or some screen button (they should be active since the screen is on). Again this could be a provide your own keystroke.
This is a Android phone, it should not force us to conform to one way to use it.
Spare Parts is something out of the default Android codebase that wasn't included in the actual OS, unless we see it in AOSP for 2.1 when it hits, someone would have to spend a while porting the old one.
I'm sure it's doable, but it's a lot of work, so unless you're volunteering, it might be better to wait for AOSP to hit.
spare parts is in the SDK ROM for 2.1 so no need to port. Just extract it from there. (No idea what is in the spare parts for 2.1, just saw it when I was testing)
Related
Hello everyone,
I have an unlocked Nokia Lumia 710 running a custom ROM and all in all the phone is good. However, the proximity sensor doesn't seem to work properly (I don't know if the problem is from the custom ROM or from the phone itself but it doesn't really matter) - when I'm in a call I keep pressing the Hold and Mute buttons (no matter how I hold the phone) which makes me really irritated. So I was wondering, there should be registries I guess that make the buttons active when pressed during a phone call. Can someone point me to the correct registries that control if the buttons are active or not when pressed so that I will hopefully be able to completely disable these two buttons (so that when pressed nothing happens)? I don't use them anyways, so completely disabling them would certainly fix my problems. I'm posting in the general WP7 section because I guess the location of these registries would most probably be the same for all phones...
Thanks a lot in advance!
There's a registry value that is updated automatically by the proximity sensor and indicates its current status system-wide, but I doubt you'd want to use it. For one thing, it would almost certainly get immediately reset by the sensor, faulty or otherwise. For another, the Phone app isn't the only thing that uses the proximity sensor; you would end up locking out the touchscreen in some other apps too. Finally, this would also prevent you from pressing the End Call button!
I don't know of a registry value that's specific to the Phone app's use of the proximity sensor. However, even if there is, the first and third reasons above still apply.
I instead recommend that you simply tap the power button when putting the phone up to your ear to talk. This will turn off the touchscreen (and incidentally save power) and you can tap the Power button again to access the Phone app or any other app on the phone when you need them, without interfering with the call.
There may also be a tool in some built-in Manufacturer or Diagnostics app that would let you test and adjust the sensitivity of the proximity sensor. This would perhaps be the best option, but I don't know where or if it exists on a Lumia.
What I want to do is not to play with the proximity sensor itself but rather with the buttons on the screen during a call. I guess I didn't make myself clear enough, sorry about that. The idea is that when I'm in a call, the proximity sensor does not work properly and I always press either the Mute or the Hold buttons. So, these buttons can still appear during a call but when you press them, I don't want anything happening. I mean, the idea is even when the phone is not next to your ear and the screen is active during a call, pressing the buttons to do nothing. I'm just following some simple logic, which might of course be incorrect (or too simple), but I'm thinking that there is most probably a separate registry for each button that controls whether this button does some action when pressed or not. I'm also hoping that they'll be separate registries for each button so that I can, for example, disable the actions for the Hold and Mute buttons, but leave the End Call button active. The problem is that I have no idea where to look for this registry since I'm still new to WP OS.
Heck, it would even be OK for me to completely remove the buttons from the screen during a call (or substitute the current buttons with some 1x1 px transparent images), if that's possible, so if someone knows how to do even that, tell me.
I was also considering using the power button when in call but I first want to see if there is any other way to do what I want. And since I'm not using the Mute and Hold functions at all, I just thought about disabling them.
No, I understood you. I was suggesting the "fix your proximity sensor" option because normally, the problem you're experiencing just doesn't happen; that's what the prox sensor is for. Sometimes it's miscalibrated, though, or something is covering it up (some poorly-cut or installed screen protectors do this, for example).
The "Phone" app isn't a Silverlight app like third-party ones; it's a native EXE that we pretty much can't modify without using a custom ROM. That's going to make changing it the ways you suggest (disabling or resizing certain buttons, etc) quite difficult.
I'm pretty sure you don't want to disable all the buttons always, even if that were possible. For one thing, that would prevent you from hanging up, as I mentioned before. It would also prevent you from dialing any numbers, which would make the use of touch-tone automated services impossible.
The Power button option really seems like the best fit for you. It's easy, doesn't require any hacks, doesn't break any other functionality, and should be the next-best solution beyond actually solving the problem.
I see now, makes sense. In my head it sounded simpler than what it really is. I was considering resizing the buttons because I'm also using iOS and I quite enjoy digging in the OS and changing some elements, so it's possible there to, for example, substitute some buttons with transparent 1x1 px images, etc. But that's irrelevant. Looks like WP is different and I still need some time to get in to it. Anyways, thanks for your help.
P.S. The screen protector was the first thing I "accused" but unfortunately it wasn't causing the problem.
On a custom ROM, you could definitely tweak the Phone app if you wanted to. However, the way WinCE (the kernel behind WP7) works, OS files are almost always marked as "in ROM" which means that the filesystem driver will refuse to modify them while the OS is booted. This makes tempering with the stock OS difficult; we have to find ways to modify the behavior of apps and system features without modifying the apps or features themselves.
The soft key lights on this device seem to work differently then most other android devices with back light soft keys. I've been trying to figure this out for a while. When exactly does the phone decide to turn them off, and and why can't I turn them off using apps like screen filter, and even on the stock t mobile rom?
Is this a hardware or software issue?
What I know is that the soft key lights in kj6 (gingerbread) roms turn on every time you turn the screen on or touch the screen, and turn off after 3 seconds of inactivity (not touching the screen or pressing any buttons).
But it seems that in some situations the soft keys turn off and stay off, even when touching the screen, which is seemingly random. Why does it do this?
Does anybody know when exactly the soft key lights decide to turn off?
From what I can tell, the Team Acid ICS driver does what it is supposed to do -- turn on and off the lights when the magic number is written to the right sysfs location.
The control of the lights is supposed to happen in the Android world with PowerManager and LightsService. The "problem" is that it seems as though the chip that controls the touchkeys and their backlight have a mind of their own and turn on the lights when you touch them. This gets the Android world's idea of if they are on or not confused, resulting in LightsService not "turning off" the light as it thinks they are already off.
I'm working through a good way to resolve this. Messing with the framework code is not the best as it means that TeamAcid would have their own version, and keeping up with upstream changes would be more difficult. Unfortunately, how it was done in GB is something of a mystery as it isn't clear to me from the Samsung code drop.
https://github.com/teamacid/android_device_samsung_galaxys4gmtd/issues/32
Are the soft key lights on the sgs4g the same as the original us versions of the Samsung galaxy (the vibrant/captivate)? If they have a fix for this (I assume they might because they have a larger development community) , would it work for our device?
I'm looking into if I can find some dev information for the Cypress/Melfas key controller, and possibly the Atmel mXT224 and looking for other devices that use it (Motorola Atrix, for example). If I can disable the "LED on when touched" behavior, things are a lot easier.
i was wondering about this as well... my back button, is messed up and has no sensitivity at all so im trying to disable the whole bar and just use an onscreen nav bar. i know that paranoid as it in their settings but that rom eats up the battery like a mad man ill be down to zero by noon i dont get that problem with CM9 BUT CM9 doesnt have the onscreen Nav Bar
does any one know where i can find more info on adding this nav bar to CM9?
Aokp has it too
V1R3Z said:
my back button, is messed up and has no sensitivity at all
Click to expand...
Click to collapse
You might try Hefe Kernel Of Darkness (second post in that thread) to mainly turn off the touchkey backlight.
I'm curious as to what poor back-button sensitivity problems you are seeing. You can PM to keep the thread clean.
Found on BensBargains (site with the least pleasant user community - so don't blame me if somebody's rude to you there)
Audio plug with button.
$2.00 w free ship or .39 with code GBSMR (no idea how long that'll last).
It's basically a button you can stick into the audio jack - and you're supposed to be able to "do things" when the button is pressed. Which means you probably need some sort of APK to make things go - or maybe it's triggering "audio jack insterted". Dunno - just ordered it.
Posting here as I've read that the power button on our tf700s is a tad fragile, so this might give someone an alternate button.
BTW, you don't need an off button if you've got CM or CROMI installed - just go to settings / interface . status bar / double-tap to sleep.
Alright so running the leaked L build that our lord and savior @digitalhigh n ole' piratety Cap'n Throwback managed to get running on our devices but have one thing that is really bothering me. Screen. Off. My power button has for ages been messed up and weak to the click and well It's truly horrid to press and I used to always have 'hold back key to turn screen off' but well I don't anymore. Xposed is gone, my one true love...how can I replace her...how can I get over her beauty and learn to let her go and potentially even replace her?
My heart is with you Xposed!! But we must go our separate paths! - A very sad Shadow
( @Captain_Throwback lol )
Incase anyone managed to misunderstand my sad love story I'll skip to the point, is there any alternative ways to avoid pressing power button to turn screen off? For instance double tap status bar to sleep or holding back button to power off (both required Xposed 'I THINK', keyword "I THINK").
S1L3nTShaDoWz said:
Alright so running the leaked L build that our lord and savior @digitalhigh n ole' piratety Cap'n Throwback managed to get running on our devices but have one thing that is really bothering me. Screen. Off. My power button has for ages been messed up and weak to the click and well It's truly horrid to press and I used to always have 'hold back key to turn screen off' but well I don't anymore. Xposed is gone, my one true love...how can I replace her...how can I get over her beauty and learn to let her go and potentially even replace her?
My heart is with you Xposed!! But we must go our separate paths! - A very sad Shadow
( @Captain_Throwback lol )
Incase anyone managed to misunderstand my sad love story I'll skip to the point, is there any alternative ways to avoid pressing power button to turn screen off? For instance double tap status bar to sleep or holding back button to power off (both required Xposed 'I THINK', keyword "I THINK").
Click to expand...
Click to collapse
I ran 5.0 for a short time but ended up switching back to Sinless before I could check. On many devices going back to and including the T-Bolt (EDIT: I was searching for the same thing back then because of the same reason), I used an app from the play store called Screen Off and Lock and I personally use the donate version and always had it tied in with the "search" feature (either a physical button or drag up from the navbar without buttons). One (big) reason for me to switch back is not having Xposed.
bb1981 said:
I ran 5.0 for a short time but ended up switching back to Sinless before I could check. On many devices going back to and including the T-Bolt (EDIT: I was searching for the same thing back then because of the same reason), I used an app from the play store called Screen Off and Lock and I personally use the donate version and always had it tied in with the "search" feature (either a physical button or drag up from the navbar without buttons). One (big) reason for me to switch back is not having Xposed.
Click to expand...
Click to collapse
That app is good enough, as long as I don't have to press the power button xD. Thanks! I'll check out the donate version in a second as from the looks of it the free one only has the option of tapping the icon to turn screen off but oh well.
EDIT: NVM
For anyone else who sees this thread feel free to leave more options if you have any! More options the better.
No problem and I couldn't remember the difference between the versions. EDIT: There should be 2 different icons in the launcher, one being the app itself to turn the screen off (?) and one just for the configuration unless it's set up differently on the free one.
Hello all,
Recently the power button on my Nexus 5 has been acting really weird. Sometimes it works flawlessly, others it requires pressing it really hard to work. In order to prevent it to stop working indefinetely, I am looking for a way to remap my volume-up button so it can work as a power button. I don't need it to turn my phone on or to work in the recovery mode (from what I read, it seems to be impossible), only when Android is running.
I've already tried some workarounds:
1) Volume Unlock Power Button Fix app: I tried it, but it just allowed me to turn on my phone with volume but not turning off. Also, it drains a LOT of power.
2) Buttonremapper app: It would theoretically do exactly what I wanted, but did not work at all.
3) Editing generic.kl: I tried switching volume-up and power buttons codes in generic.kl, but also did not work. Maybe I need to modify another file?
3) Xposed Framework + Additions: The installation of Xposed went Ok, but after installing Additions module I got stucked in bootloop. I am running Android 5.1 stock, maybe this module is not yet compatible.
So, can anyone help me? Do I need to install a custom ROM?
PS: I live outside US, so no warranty for me. Otherwise I would just use it
Thanks in advance for any help!
Cheers,
Humberto
Hi folks,
Just a heads up for anyone who might be facing the same issue. I decided to change from stock to Cataclysm ROM due to some specific features (listed below). After the installation, here's what I did to work around this problem:
1) Enabled "Volume wake" and "Sleep button on status bar" in "Cataclysm Settings / Miscellaneous".
2) Enabled "Swipe to sleep" and resized NavBar to 115% in "Cataclysm Settings / Navigation bar options". -> This way I can swipe in NavBar at any time (except lockscreen) to turn off screen. I raised it a little to facilitate the swipe gesture.
3) Changed Lockscreen Dialer shortcut to ""Turn off Screen" app shortcut (just search for it in the play store) in "Cataclysm Settings / Lockscreen options" -> This allows me to just swipe right and turn off the screen when my security settings are disabled (which accounts for most of the time). I found it way faster than pressing sleep button in status bar, especially when I'm driving and I can't look at the screen. Plus, I don't really use the dialer function of my phone so often since the invention of Whatsapp ;P
I realize this is not the perfect solution, but I don't see a better way to deal with this power button malfunction problem (except from a hardware fix).
Hope this helps!
Cheers,
Humberto
PS: I am really enjoying Cataclysm. It's a very nice ROM, completely stable and with a lot of other interesting features aside from the ones mentioned above. I strongly encourage anyone to give it a try!
I'm facing the exact same problem but I really need to eliminate the power button or I will need a power button fix soon.
The solutions you found hthiengo are good if not needing to turn off (or worst: running out of battery, something that happens me sometimes). I'm in the situation that next time I hit power button I will need to replace the button, or throw the nexus away
I did installed the xposed additions for lollipop but it is not working, and the Cataclysm trick is not enough in this case
Ok, after some research I've found a temporary solution:
For the power button you can remap modifying the file gpio-keys.kl under system/usr/keylaout (i wonder why anyone could figure out thise before, no that difficult). I would like to map power button leeaving it useless but I've found it impossible to remap the power button (probably because the key number is not 116). I would have liked to see xposed additions to help me map the keys but is not functional at least for me.
If the phone runs out of battery I've found that if I plug the power cable by pressing both volume buttons at the same time, eventually it starts up with the bootloader so I can plug the pc cable and it will reboot sucessfully.
So despite the phone know is pretty disfunctional (not the best phone for a hurry without battery), I can still use it for some weeks before I plan buying a new one or something (or I find a place for reparing). Its a shame I could not find a better solution for example, ADT when powered off so I could just reboot it by using ADT reboot command while powered off.
And It would be really amazing if the volume up button could also power it on from the powered off state.
In my case the power button is broken, but sometimes it gets stuck and puts the phone in a reboot loop: To avoid pressing the power button accidentally I've made a hole in the protective case so its pretty difficult to access it.
That's all for now. If anyone can make it better I will be glad to hear him/her