Is there a mod out there that can be applied to the ota that let's us power on the screen with the trackpad? Reminds me of my old Eris.
Sent from my ADR6300 using Tapatalk
I'm pretty sure last time I checked that remapping the trackball was not possible
Sent from my ADR6300 using XDA App
It is possible. I do believe Chads kernel comes with it. That or CM7 has it. I can do it with my phone, at least. It doesn't always work on the first press, so you sometimes have to hold it down. I noticed when I'm charging it works first time, every time. Unsure why that is though.
Sent from my Droid Incredible running some random CM7 nightly.
You can use Button Remapper from the market or google it. Also Sky Raiders, OVO, Synergy, CM7 and most roms that are not stock have the option for trackepad wale
Sent from my OVO Community ROM using XDA App
if you poke around in /system/usr/keylayout you can find two files "incrediblec-keypad.kl" and "qwerty.kl" these two handle the mapping of the keys so that android OS knows how to handle they key events.
I don't have the OTA so I haven't tested it but back in the day you would find the DPAD_CENTER line and change it from WAKE_DROPPED to WAKE.
I played a lot with these files because I really wanted a decicated CAMERA button and the OJ was perfect for me. Hope this helps and I wish I could test this before I started making suggestions to you. Good luck.
SteveG12543 said:
It is possible. I do believe Chads kernel comes with it. That or CM7 has it. I can do it with my phone, at least. It doesn't always work on the first press, so you sometimes have to hold it down. I noticed when I'm charging it works first time, every time. Unsure why that is though.
Sent from my Droid Incredible running some random CM7 nightly.
Click to expand...
Click to collapse
As far as the why, it is because the phone screen is still "Awake" if I remember correctly. If you power your phone off then immediately press the optical button, your screen will come on but it won't if you wait say five seconds. I've noticed the same as what you stated occur in one of Nils' older gingersense roms.
SlimSnoopOS said:
As far as the why, it is because the phone screen is still "Awake" if I remember correctly. If you power your phone off then immediately press the optical button, your screen will come on but it won't if you wait say five seconds. I've noticed the same as what you stated occur in one of Nils' older gingersense roms.
Click to expand...
Click to collapse
Huh, weird lol. Never noticed that myself. I usually don't lock then unlock lol. Quite interesting, though.
Sent from my Droid Incredible running some random CM7 nightly.
Related
I finally stepped into the world of evo ") I got my phone last night rooted it and installed the newest nightly from cyanogen mod 6.0. Everything is running so perfect. My only question is, is there a way to turn on the backlights at the bottom, ie. The home key, menu key etc. Thanks
E-Rock
Sent from my PC36100 using XDA App
E_Rock said:
I finally stepped into the world of evo ") I got my phone last night rooted it and installed the newest nightly from cyanogen mod 6.0. Everything is running so perfect. My only question is, is there a way to turn on the backlights at the bottom, ie. The home key, menu key etc. Thanks
E-Rock
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
These are on anytime the screen is on.
I see you are using cyanogen mod 6.0. In that case you should goto the cyanogen thread and see if other users have this issue.
actually they are only on when the screen is on and the phone is not plugged. Are they not coming on at all for you? if not were they coming on before you rooted/flashed cm6?
I have my backlight set to auto.
Anytime I take my phone someplace dark, the turn on. Even if I am not using the phone. I really like it, so I can see the buttons and know the orientation of the phone in pitch black.
Hmm, actually in looking at it now, they may just always be on. I am on hardware 02 from the google conference.
I'm new to rooting, installed MIUI and loving it so far. My hw is 003. Everything is working so far but i have a few questions -
1. Do you use the default kernel or replaced it? I've seen screen tearing a few times and battery life could be better so I'm thinking of trying a different one. Read a number of threads in the root section.
2. Did you replace the lockscreen? I'm asking because I love its look, but if you enable security there's no slide to unlock and its not so useful.
3. How often do you update the MIUI build - I read it comes out every Fri, do they have major changes?
#3, the official build is done on friday, porting to individual phones is on/around sunday
1. I'm on the 1.1.28 build and using the kernel that came with it. Savage 1.6. It is by far the best kernel I have ever had the pleasure of flashing and I have no reason to use anything else. When I update to a newer build, I will most likely flash this kernel over it.
2. Still using stock lockscreen. I agree that the pattern lock could have been implemented better.
3. What elegantai said.
2 more issues I noticed -
1. Back button is now killing apps. The only way to fix it is turn off 'long press kills app', reboot, and turn it back on.
2. When in a call the notification bar cannot be dragged down.
Both are minor issues, just wondering if they are common.
1. That's not an issue at all, it's supposed to do that, and I think that's an awesome feature. If you just tap back it won't kill the app, and you can set how long the long press needs to be.
2. Never really noticed that before. Can you pull it down with a Sense ROM? It's been so long I can't remember. You can always hit the home key while in a call and pull the bar down from there.
ECrispy said:
2 more issues I noticed -
1. Back button is now killing apps. The only way to fix it is turn off 'long press kills app', reboot, and turn it back on.
2. When in a call the notification bar cannot be dragged down.
Both are minor issues, just wondering if they are common.
Click to expand...
Click to collapse
I actually have the same problem with the app killing. Great feature yes but it always kills the app regardless of how long or short I press it lol. Changing the duration didnt seem to help.
Sent from my PC36100 using XDA App
_MetalHead_ said:
1. That's not an issue at all, it's supposed to do that, and I think that's an awesome feature. If you just tap back it won't kill the app, and you can set how long the long press needs to be.
.
Click to expand...
Click to collapse
It kills the app even when I just tap back, that's the bug. When its working yes, it only kills after a 2s tap.
ECrispy said:
It kills the app even when I just tap back, that's the bug. When its working yes, it only kills after a 2s tap.
Click to expand...
Click to collapse
That's odd, it works perfectly for me. What MIUI build are you on?
_MetalHead_ said:
That's odd, it works perfectly for me. What MIUI build are you on?
Click to expand...
Click to collapse
Latest - 1.2.11
I dunno, maybe it's a bug with that build.
from my observations the back tap close program happens only when a program is lagging. if you dont have too many things going on at once it shouldnt be a problem
yeahh it is a problem occasionally for me. I normally skip and flash every other week. This week im gonna flash again though, because it seems slow.
I've only had this phone for a couple of days, but I am somewhat annoyed by the slight lag when pressing the power button. I am presently running Calks ROM. The stock rom did it as well.
Anyway to fix where when I press the power button my screen instantly turns on?
yes, search first, after that, take out your memory card.
it causes screen wake delay. take it out..it disappears.
hope this helps! search before posting its been discussed a million times already
Is there a way to keep the sdcard and not have this issue
biggggant said:
Is there a way to keep the sdcard and not have this issue
Click to expand...
Click to collapse
Yes learn how to edit the android os files without breaking anything, and release your own ROM.
Sent from my SPH-D710 using Tapatalk
So, in contemplating upgrading to this phone, but here's my concern: When full-screen apps like YouTube force close, or when I want to exit and stop watching the current video, what do I do?
Is there a way to hack the buttons so that they stay on the screen at ALL times, regardless of the app running such that the on screen buttons are essentially equivalent to hardware/capacitive buttons?
Sent from my x10 mini running the latest version of minicm 7.
Buttons r hidden when play YouTube video. When tap anywhere on the screen, all buttons reappear.
Actually, I would prefer all apps can auto hide the buttons to get full screen. Looks so much nicer...
Sent from my Galaxy Nexus using XDA App
But what if the YouTube app hangs and the phone freezes? Is a battery pull the only way?
Sent from my x10 mini running the latest version of minicm 7.
i think the buttons would still show up (they are not part of the youtube app)
When playing videos, it will go to full screen and 1 tap of the screen will show the buttons. Most of the time the buttons will disappear and be replaced by 3 barley lite circles.
Sent from my Galaxy Nexus using XDA App
Oh, I see. Thanks. And what I meant was that both the app and the phone freeze. Is there a way to force reboot when the phone totally hangs? Like, using some button combination like how it is possible on my current device?
Sent from my x10 mini running the latest version of minicm 7.
Just thinking out loud here. But if the app force closes on you, you can pick the force close button that pops up or it will just close itself and bring you back to your home screen. So no problems there really, and also I don't see why so many people are scared to pull the battery out of their phones? Is it just because of the hassle? Otherwise I see people saying they're scared of breaking the back cover?
Uhm, that's not what I mean. I mean the app totally hangs and the phone freezes too, not responding to touch input.
Sent from my x10 mini running the latest version of minicm 7.
Battery pull.
Sent from my Galaxy Nexus using xda premium
even if u did have hardware buttons and the phone freezed ud still have to do a battery pull, ive witnessed it a few times when working with my droid eris..
Yeah, currently the only way to force a reboot is through pulling the battery. On my Galaxy S i9000 you could hold Power + Home and it would reboot even if the phone was totally frozen
MrBig0 said:
Yeah, currently the only way to force a reboot is through pulling the battery. On my Galaxy S i9000 you could hold Power + Home and it would reboot even if the phone was totally frozen
Click to expand...
Click to collapse
same thing on my current phone. Doing battery pulls is a terrible pain if I have installed a protective casing.
@mrbig0 see what I quoted
Sent from my x10 mini running the latest version of minicm 7.
If your whole phone freezes (shouldn't) then of course you have to do a battery pull regardless of the ROM you're running or what buttons you have...
^My experience, reading above apparently some phones do so. Regardless, I use my phone 10 hours + daily and have never had the whole phone freeze.
To the OP, the phone never really freezes. Ive been with android since donut and this phone has been the most stable even with custom roms. I think I've only had one force close the whole month I've had the phone and it's never completely frozen on me. You dont have anything to worry about.
bigmike2424 said:
To the OP, the phone never really freezes. Ive been with android since donut and this phone has been the most stable even with custom roms. I think I've only had one force close the whole month I've had the phone and it's never completely frozen on me. You dont have anything to worry about.
Click to expand...
Click to collapse
not unless im doing overclocking, hackery and the like.
Sent from my x10 mini running the latest version of minicm 7.
RMatt1992 said:
If your whole phone freezes (shouldn't) then of course you have to do a battery pull regardless of the ROM you're running or what buttons you have...
^My experience, reading above apparently some phones do so. Regardless, I use my phone 10 hours + daily and have never had the whole phone freeze.
Click to expand...
Click to collapse
Not true. On my current phone, pressing a button combo will reboot the phone whether it's frozen or not. It's a hard reset.
Sent from my x10 mini running the latest version of minicm 7.
aloy99 said:
not unless im doing overclocking, hackery and the like.
Sent from my x10 mini running the latest version of minicm 7.
Click to expand...
Click to collapse
thats true, i never mess with set cpu or set speeds, but if that's the case then battery pulls might be necessary haha
I never have experienced it with the Samsung Galaxy nexus and I did crazy things.
Guys/gals
I have noticed that while in CWM, the up and down presses of the volume button are acting weirdly. Sometimes it will scroll through 3-5 lines while other times it is doing what it should and moving one spot at a time. I am rooted running gummynex and using the proper CWM version. Any others experience this also?
On a side note, this sometimes disables the functionality of the 'enter' button on the right side also.
Never had any problems with CWM navigation here ... maybe re-flash CWM?
Edit: Does your volume key act weirdly just adjusting the volume? If so it may be bad hardware
Mine does the same. Its when you hold the rocker down for a long period of time. Just tap one by one and you'll be good. I kinda like the ability. It allows for faster scrolling.
Sent from my Galaxy Nexus using Tapatalk
it is only in CWM... volume functionality is perfect in normal actions. it is extremely sensitive in CWM. sometimes i can choose carefully and get it to move one option at a time, but it is far too sensitive to be fun to use in this way.
maybe i'll try the touch version and see if that is any easier. it does not seem hardware related since I have seen 3 or 4 others with the same issue only in CWM.
Be careful with the touch version. I've seen a few zip files where the developer specifically states not to use the touch version. Just a Tuesday morning fair warning.
Sent from my Galaxy Nexus using Tapatalk
http://forum.xda-developers.com/showthread.php?t=1428338
Fix.
I've never had a problem with the touch version. I'd recommend just using that.
Sent from my GalaxyNexus using XDA App