[Q] Soft Keys - Nexus One Q&A, Help & Troubleshooting

Hi all,
On my N1, sometimes the soft keys (back, menu, home, search) does not work correctly. I keep having to press couple times or above the picture to register. Is there any fix for this? I'm currently on stable Cyanogen Mod 6.1.1.
Thanks!

For best results, aim just above them

Thanks Rusty, but is there any fix/resolution for this. Or this is how all N1 are?

It's how they are really.

sbatchu said:
Thanks Rusty, but is there any fix/resolution for this. Or this is how all N1 are?
Click to expand...
Click to collapse
It's the same for all Nexus ones. Personally I never really run into this problem but I think that's simply because I grew accustomed to pressing slightly above

Tapping just above the SK is how the N1 was designed to be used.

Thanks for all your reply guys!

Related

Trackball wakeup on Desire rom?

Im sorry if this has been addressed already, but i was wondering if there was a way to enable the phone to be woken up by pressing the trackball as opposed to the power button.
Thanks!
paul doesn't even maintain the rom, why do you use it ?
use cm buddy.
because i have no issues with it, and i like the way it looks and how it operates, buddy.
Thread moved since it isn't development.
Hi, is there anyway to wake the phone up using the trackball or other buttons on a stock unrooted rom?... So far the apps Like Lock2.0 and Lockbot does that but has been really buggy...
rheza02 said:
paul doesn't even maintain the rom, why do you use it ?
use cm buddy.
Click to expand...
Click to collapse
lol
People are funny.

[Q] Rom suggestion with trackball wake

I've never rooted my phone but am about to receive my third nexus one because of power button failure and I don't want to do it again. I watched some Nexus One development video where they were using a machine to depress the trackball thousands of times, to simulate lifetime use and test for failure. I guess they didn't test the power button.
Any suggestions on a ROM similar to stock but that has wake on trackball press? I was looking at cyanogenmod.
It seems like there should be an app for this, but I noticed an enhancement request on Google code, I guess that ability was removed in 2.3.3.
I am currently using anyunlock to wake my phone with the volume button but am not really a fan. I don't want to adjust the volume and it replaces the lock screen.
Thanks a lot.
CM7. Like Stock but...better!
DirkGently1 said:
CM7. Like Stock but...better!
Click to expand...
Click to collapse
+1
CyanogenMod is one of the best alternative ROMs out there. All the features of stock with a ton more added (along with bugfixes).
archinloaf said:
I've never rooted my phone but am about to receive my third nexus one because of power button failure and I don't want to do it again. I watched some Nexus One development video where they were using a machine to depress the trackball thousands of times, to simulate lifetime use and test for failure. I guess they didn't test the power button.
Any suggestions on a ROM similar to stock but that has wake on trackball press? I was looking at cyanogenmod.
It seems like there should be an app for this, but I noticed an enhancement request on Google code, I guess that ability was removed in 2.3.3.
I am currently using anyunlock to wake my phone with the volume button but am not really a fan. I don't want to adjust the volume and it replaces the lock screen.
Thanks a lot.
Click to expand...
Click to collapse
agreed with cm7 (if you prefer the normal stock look) I personally don't like all that sense / miui stuff. now that the big bugs are fixed, i don't see why you shouldn't give it a try.
cyanogen 7 really is easily the best option. and with the newest battery increases and optimizations, its a no brainer to use cm7 over stock.
Running Kang-o-rama-1.2 . . . . It's just CM7, kind of.
Loaded it last night and seems to be the best so far. The least amount of lost MMS compared to regular CM7.
samson_420 said:
Running Kang-o-rama-1.2 . . . . It's just CM7, kind of.
Loaded it last night and seems to be the best so far. The least amount of lost MMS compared to regular CM7.
Click to expand...
Click to collapse
There were issues with MMS messages in the nightlies due to a merging conflict when they merged to the 2.3.4. This has been resolved for the last couple of weeks.
I'm not sure if that is what you were talking about.
How much free memory do you have on your phone?

[Q] Software buttons ICS on ICS roms.

Hey guys, lately i've been really annoyed because i can't use any ICS rom properly, mainly because my MENU button is not working.
I got this app "ButtnRemapper" which reassigned my hardware keys to the one i wanted.
So i switched the home button to menu and it worked great on the Gingerbread ones, but on the ICS roms it would not work!
That's why i'm asking if there is any possibilites of porting software button as the Galaxy Nexus has.
bump le bump
Not meaning to be captain obvious, but why not consider getting your home button fixed? Flash your phone back to original state and no warranty problems there - and after some time you'll finally be able to fully enjoy your phone.

[Q] Home Button (Capacitive and Software) not working with CM9 / AOKP?

Hi folks,
Apologies if this question has been asked on the Bionic forums elsewhere; I did a search and didn't find anyone with an answer.
I've been experimenting with custom ICS ROMs on my Droid Bionic, and of the four I tried, three of them leave me in a situation where my Home button doesn't work. This applies to both the capacitive key on the Bionic bezel as well as the soft key which is native to ICS in phones that don't have capacitive or hard buttons (but can be enabled for the Bionic in custom ROMs).
Let me break down what I mean by "work". When I press or long-press Home, I get the appropriate visual and and haptic feedback as expected. But nothing happens in the OS. I expect it to take me to my home screen from any app; it does not. I expect the capacitive button long-press to bring up the Recents for multi-tasking, and it doesn't. I've assigned different behaviors to the soft key in the launcher, both press and long-press, and none work. All other capacitive and soft keys work just fine, and CM10 on my Iconia A100 doesn't exhibit any home button issue.
Here are the ROMs I tried which exhibited this issue for me:
CyanogenMod 9 (CM9 20120725 build, unofficial)
AOKP (Targa 20120725 Milestone 6 build)
LiquidSmooth MR 2.6 (Jester's JMOD modification of LiquidSmooth v1.5)
Currently I'm running on LiquidSmooth v1.5 MR 1, and it works perfectly. One thing I noticed is that CM9 runs the Trebuchet launcher, and AOKP and the JMOD of LiquidSmooth both run Nova Launcher. Meanwhile, the Liquidsmooth build I'm on is running what looks like LiquidSmooth's own modified Launcher (forgive me as I betray my n00b roots). I can only assume that the launcher is the issue and that perhaps if I just ripped LiquidSmooth's launcher APK I could run/use it in any other ROM, but this is just an assumption. I'm just wondering if anyone else experienced what I did, because from the looks of it I haven't found anyone who has.
Thanks for any insight anyone can provide!
This issue with the Home Button is not Bionic specific. I have had this issue with both Bionic and OG Droid. It has more to do with the OS I believe. I know I've read about this somewhere but I don't remember where. Usually it happens when you upgrade your phone with a custom rom and for some reason it disables the home button. In my case I just reinstall said rom until it works. It's happened a few times with my OG Droid considering I would switch roms always weekly due to the unlocked bootloader. Not so much on the Bionic since it's locked. Waiting for Motorola to release the bootloader unlock for our Bionic...hurry up Motorola or Google...I know I didn't really answer your question but that's my experience.
amageus said:
This issue with the Home Button is not Bionic specific. I have had this issue with both Bionic and OG Droid. It has more to do with the OS I believe. I know I've read about this somewhere but I don't remember where. Usually it happens when you upgrade your phone with a custom rom and for some reason it disables the home button. In my case I just reinstall said rom until it works. It's happened a few times with my OG Droid considering I would switch roms always weekly due to the unlocked bootloader. Not so much on the Bionic since it's locked. Waiting for Motorola to release the bootloader unlock for our Bionic...hurry up Motorola or Google...I know I didn't really answer your question but that's my experience.
Click to expand...
Click to collapse
Even though it wasn't a direct answer I definitely appreciate the insight! It's good to know what's happening out there and I now have some more context around the situation... It's weird because Liquid is really the only one that works for me. I just now tried a CM9 update just for kicks and again the Home button doesn't work. (Using Trebuchet natch.)
MrCHUPON said:
Even though it wasn't a direct answer I definitely appreciate the insight! It's good to know what's happening out there and I now have some more context around the situation... It's weird because Liquid is really the only one that works for me. I just now tried a CM9 update just for kicks and again the Home button doesn't work. (Using Trebuchet natch.)
Click to expand...
Click to collapse
I know that the Bionic and the OG Droid are not the only ones who experience this dreaded dead home button issue. It exist in a lot of android phones. You could google it and get a lot of hits on different phones. I know I have the first time I experienced this issue with the OG Droid. Could have something to do with the coding in the roms you are installing and it seems to be a hit and miss. Apparently your phone is picky about which rom it wants you to install lol. Maybe a developer could chime in and explain a bit more? Or someone with a lot more knowledge?
t
amageus said:
I know that the Bionic and the OG Droid are not the only ones who experience this dreaded dead home button issue. It exist in a lot of android phones. You could google it and get a lot of hits on different phones. I know I have the first time I experienced this issue with the OG Droid. Could have something to do with the coding in the roms you are installing and it seems to be a hit and miss. Apparently your phone is picky about which rom it wants you to install lol. Maybe a developer could chime in and explain a bit more? Or someone with a lot more knowledge?
Click to expand...
Click to collapse
Ino developer but I had this problem as well but once I flashed the latest gapps all was well.
Hope this helps

Want to go to Gingerbread!

Where can I find a stock Gingerbread ROM at? When I purchased my phone it already had ICS on it, and honestly I do not like it at all. I jumped to my favorite phone mod site (XDA) and did some searching but came up empty handed. Can anyone assist me with my request? Thanks!
qtipextra said:
Where can I find a stock Gingerbread ROM at? When I purchased my phone it already had ICS on it, and honestly I do not like it at all. I jumped to my favorite phone mod site (XDA) and did some searching but came up empty handed. Can anyone assist me with my request? Thanks!
Click to expand...
Click to collapse
Sorry. There are not any GB ROMs for the D4 that will work on ICS. The GB D4 ROMs there are are not compatible with the ICS kernel. Maybe if you can describe the issues you are having with ICS we can help you with those.
Sent from my XT894 using Tapatalk 2
Mainly just nitpicking things, but the one thing I've had an issue with ICS is the fact that I cannot link notification and ringer volumes together.
Another issue I'm having is when typing using the hardware keyboard, I'll be typing something and the cursor will
jump and start typing at the beginning. Happened just as I was typing this reply, too.
qtipextra said:
Mainly just nitpicking things, but the one thing I've had an issue with ICS is the fact that I cannot link notification and ringer volumes together.
Another issue I'm having is when typing using the hardware keyboard, I'll be typing something and the cursor will
jump and start typing at the beginning. Happened just as I was typing this reply, too.
Click to expand...
Click to collapse
That is odd stock ICS does not have the functionality to link notification and ringer volume. You should be able to find an app on the market that will give you this functionality. Found this on another forum with a quick google search: "Get cvolume from the market. Under settings you need to check notification volume not(Use incoming call volume for notifications). Works great" aarong03 - DroidForums
There are other volume control apps out there as well that may have similar functions. Try some out and let us know!
Not sure about the cursor jumping on you. It seems like I had this problem once too and it ended up being something I was doing that was causing it but I cannot think for the life of me what it was. Some button I was hitting or something.
kwyrt said:
That is odd stock ICS does not have the functionality to link notification and ringer volume. You should be able to find an app on the market that will give you this functionality. Found this on another forum with a quick google search: "Get cvolume from the market. Under settings you need to check notification volume not(Use incoming call volume for notifications). Works great" aarong03 - DroidForums
There are other volume control apps out there as well that may have similar functions. Try some out and let us know!
Not sure about the cursor jumping on you. It seems like I had this problem once too and it ended up being something I was doing that was causing it but I cannot think for the life of me what it was. Some button I was hitting or something.
Click to expand...
Click to collapse
Thanks for the information. I have tried many volume apps that claim to link the volumes together, but do not work. I basically just want to use my hardware volume buttons as a master volume control, so when I set it with the hardware buttons, nothing is higher. or lower than that volume. I had a Samsung captivate glide on att that was running GB and the app that I used on that phone did not work on my D4 for linking volume. I tried this cvolume app and it doesn't seem to be working either, even though the option to link them is set.
qtipextra said:
Thanks for the information. I have tried many volume apps that claim to link the volumes together, but do not work. I basically just want to use my hardware volume buttons as a master volume control, so when I set it with the hardware buttons, nothing is higher. or lower than that volume. I had a Samsung captivate glide on att that was running GB and the app that I used on that phone did not work on my D4 for linking volume. I tried this cvolume app and it doesn't seem to be working either, even though the option to link them is set.
Click to expand...
Click to collapse
I use audio manager pro. It costs about $3 but is well worth it - Play Store
-
There is also a free version that just doesn't allow saving of profiles.
azrael293 said:
I use audio manager pro. It costs about $3 but is well worth it - Play Store
-
There is also a free version that just doesn't allow saving of profiles.
Click to expand...
Click to collapse
I've been using AudioGuru for profile selection, but I would much rather be able to dynamically change the volume of notifications and ringer together from the hardware buttons instead of set profiles with defined volume levels at each.
I have not found an app yet that works on this phone/ICS that works to lock both volumes together.
Perhaps I will just have to wait until JB is officially released for our phones. But I really liked GB on my previous phone, its too bad I can't get a ROM to work from ICS to GB, considering that the phone was originally released with GB.
Another thing I don't like about ICS is the stock messaging only let's you save a maximum of 1000 messages per contact. I would prefer messages never get automatically deleted, and in ICS it cannot be disabled, you can only change the max number of kept messages.
If you attempt to downgrade the phone to official GB there is a very high risk of bricking the phone.
I'd recommend you stop trying to do this and instead try to either get used to ICS or to replace the bits you don't like with some 3rd party apps.
I'm always having that cursor problem with the keyboard. Happens whenever I open up the keyboard and immediately start typing. Wait a second or two before typing, and it's usually ok. Seems the input editor is too slow to initialize itself, so it's still trying to set the cursor to column zero by the time you start typing...
Sent from my DROID4 using Tapatalk
If you need to back to gingerbread dowlnoad official moto ginger software
http://sbf.droid-developers.org/cdma_maserati/list.php
niko99 said:
If you need to back to gingerbread dowlnoad official moto ginger software
http://sbf.droid-developers.org/cdma_maserati/list.php
Click to expand...
Click to collapse
did you try yourself before suggesting?
There is no risk in downgrading to GB via SBF. No risk, because you will most certainly B R I C K your phone. So learn to live with it.
I too have some issues with ICS. The cursor jump happens to me too, and I hate it. I also have issues with BT volume control. Music is no problem, but controlling Youtube volume does not work for me. And when docked (lapdock or plain HDMI cable) volume also doesn't work. On or off, nothing in between.
But still, I think ICS runs much smoother than GB.
with locked bootloader is unable to brick droid ( always is way to get back phone to life) but ppl must know what ar they doing
niko99 said:
with locked bootloader is unable to brick droid ( always is way to get back phone to life) but ppl must know what ar they doing
Click to expand...
Click to collapse
Yes you can (maybe) bring your phone back to life, but one thing that will definitely not happen is that Gingerbread ROM actually booting. The locked bootloader does not allow you to downgrade.
Do not even bother trying to downgrade it will waste your time and you may end up with a brick.
highlandsun said:
I'm always having that cursor problem with the keyboard. Happens whenever I open up the keyboard and immediately start typing. Wait a second or two before typing, and it's usually ok. Seems the input editor is too slow to initialize itself, so it's still trying to set the cursor to column zero by the time you start typing...
Sent from my DROID4 using Tapatalk
Click to expand...
Click to collapse
Die Bruine said:
There is no risk in downgrading to GB via SBF. No risk, because you will most certainly B R I C K your phone. So learn to live with it.
I too have some issues with ICS. The cursor jump happens to me too, and I hate it. I also have issues with BT volume control. Music is no problem, but controlling Youtube volume does not work for me. And when docked (lapdock or plain HDMI cable) volume also doesn't work. On or off, nothing in between.
But still, I think ICS runs much smoother than GB.
Click to expand...
Click to collapse
At least I know I am not the only one with the cursor jump issue. And yes, I notice it only happens to me when I open the keyboard and immediately start typing. I will have to start being patient and give it a few seconds before typing.
I've tried many different Volume apps, and even when locking volume settings are enabled, the volumes are not locked when I adjust it with the hardware volume rocker.
I did read that JB will be getting an official push to the D4, but they have not said when. ICS just doesn't set too well with me for some reason. Yes, it runs pretty smooth, but I don't like it's all black theme, some functionality that was left out, and the new widget being part of the app list doesn't always show new widgets immediately. I guess my biggest upset about it is that it seems rather... buggy or undeveloped. To me, GB seemed to be more developed and work the way you would come to expect an android OS to run now days, and ICS just isnt there yet. Hopefully JB will be better...
niko99 said:
with locked bootloader is unable to brick droid ( always is way to get back phone to life) but ppl must know what ar they doing
Click to expand...
Click to collapse
I bricked my first droid 4 without problems with locked bootloader. do you want a link I sell it for parts?
olegfusion said:
I bricked my first droid 4 without problems with locked bootloader. do you want a link I sell it for parts?
Click to expand...
Click to collapse
unless you borked your bootloader or had a hardware failure niko is right there is no way to hard brick your phone just by flashing roms/sbf's
as long as your bootloader is intact you are able to recover your device
All that said, there's no reason someone couldn't get a vanilla AOSP GB build working with the ICS kernel for use with safestrap. On the XDAndroid project we had a single Linux 3.5 kernel working for Froyo, GB, and ICS. It's not a slamdunk, but the amount of patching required isn't that bad.
Sent from my DROID4 using Tapatalk

Categories

Resources