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.
Related
Has anybody tried "Music Control Lite?" This was developed for the Droid and I couldn't get it to work for the Hero. But I've been looking for something like this for MONTHS, something where I could advance the songs by pressing a hardware button (i.e., when I'm on a treadmill from my pocket without having to swipe open the screen). Blackberry's have allowed you to advance or go back by hard-pressing the volume buttons since my old Curve. Does anybody know anything that does this with the Hero?
I know I can get a BT Headset with the buttons but my Hero rooted, non-rooted no matter what ROM I'm on just skips and slows to a crawl in BT mode ever since I got it last October...
Someone told me that Darchdroid rom had this ability, but was just checking to see if an app did this before I loaded a new rom, on Fresh 2.3.3 now..
Like many others(non-rooted) Nexus one, I rely on using Widget Locker to wake my N1 because sleep/wake button on my N1 doesn't work.(stopped working around 6 months back)
Have read a couple of reviews @ market.android.com that Widget locker currently does not support Gingerbread. Now with Gingerbread update hitting anytime, I am a little concerned and need to find a "working" app to wake my N1 after Gingerbread.
Any thoughts?
If you want to switch on and off you screen, use both screen off and lock and no lock.
(Dev of WidgetLocker)
*Insert rant about Cyanogen Nightlys being unsupported by the Cyanogen team but Market commenters complaining to app devs if something doesn't work on such*
I got the Nexus S the day it came out and tested WidgetLocker 1.2.8.1 on it. If something was seriously broken I would've released a small 1.2.8.2 update that day or soon after. Everything worked fine. Since then, the Nexus S/Gingerbread have been one of my primary testing platforms for the coming (big) update. (Don't worry, I haven't forgotten my Nexus One, I've been testing on that too).
I've received a small handful of emails from people suggesting issues due to Gingerbread and/or Nightly-roms-that-aren't-supported-by-their-own-developers but none has actually been at all related to Gingerbread. Most bugs reports I get are related to settings or third-party apps and relatively easy to resolve.
Thanks for the update. Hopefully as you indicated we won't have an issue when Gingerbread is rolled out.
Sent from my Nexus One using XDA App
Trackball wake does not seem to work on stock Nexus One Gingerbread. I'm still looking into it, but wanted to let you know.
It is possible that no third-party-application, such as WidgetLocker, will be able to enable trackball wake. It may have to be done at the rom/kernel level in which case unrooted Gingerbread on the Nexus One will not be able to have trackball wake.
The volume keys DO work with Easy Wake Mode to wake the device.
-Kevin
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?
Hi all,
I am using Sensation 3.0 ROM on N1, this 's really awesome except no TB wake up.
Pls help if someone knows the solution for this.
Thanks all,
Thien
If there was a solution, it would have been posted in the ROM thread already.
Which means - there is no solution.
Now, with dbasabe working on proper Gingerbread Sense kernel, the solution might appear.
The rage gets harder and harder to resist these days...
The only real solution is to use the volume rocker if you can't use the power button. Maybe a solution will be found in ICS once Sense reaches that point.
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