[Q] SlimKat Hardware Buttons not workin - Nexus S Q&A, Help & Troubleshooting

Okay, I am a bit of a newbie at flashing roms and rooting my devices. I managed to set up the latest Slimrom of Slimkat on my Nexus S. Now the only hardware buttons that work properly are the back and menu buttons. I get haptic feed back from the search and the home button, but nothing happens. As well I have tried the Navbar with the same results. I maybe a bit of a moron here. Anyone have the same issue or a fix?
One other thing. I am not seeing notifications for any of my apps. I do feel a vibration when some come in but that's it. Wondering if it's tied to the same thing.
[edit] Never mind. Was just a bad install. Did a wipe and re-install and everything is functional now.

Related

Button Problems

Hey all, just upgraded to thingonasprings rom and im pretty chuffed so far... only a couple of problems, im sure someone will be able to help me as a newbie. Keyboard and phone buttons seem to work fine, but the dpad, backlight, voice dial and camera buttons and volume control all seem dead and the power button doesnt always bring the screen back up, i have to close the lid and re-open.
Is anyone else having this problem? Can anyone confirm them to be working in another rom that is as good as thingonasprings?
ok, i guess no one else has this problem... can anyone recommend a way to capture when a button is pressed and what reference refers to that button? Is there anything in the registry storing a button reference followed by its action. I may not be using the correct terminology.
If anyone can help it would be very much appreciated.
Thanks in advance
try to reflash it again... maybe it would help.
Thanks for the reply
I tried reflashing, and even tried changing to a different rom (I am using thingonaspring's rom, but have tried Beasty & Laurentius as well). Im guessing that this is something kinda specific to my device as it seems no-one else has had this problem. I know that the backlight button actually works as I can use it to get into the bootloader, thats why im thinking it must definately be a rom / software issue. Ive been looking for an app I can use to trace a button press, but cant find anything. I really like WM6, but without these buttons / volume slider i may need to swap back to something else... i was running 2003 with wisbar but the performance didnt seem as good as it is now, and i love realvga (I dunno if it is supported on other versions of the OS).
ok, think im getting somewhere - went back to wm5 and all was fine, went to wm6 and they worked until i reset...then nothing... hard reset and they work, until i reset again.... anyone any ideas please?
now sorted changed rom to jwrights and its much better - thanks

D-pad not working properly on RAPH

I have spent hours searching to see if someone else has had this problem and haven't been able to find anything.
My lower D-pad and its buttons/touch panel have stopped working properly. The touch part of it doesn't work at all and the buttons have reduced functionality. Only the up/down and the home buttons work. From what I can tell this was after flashing Tael's latest Sense2.5 ROM.
I have reset the phone back to standard, using an original HTC Rom, going back to standard SPL, and standard radio. This has not fixed the problem.
The only thing I can find that seems to be related, is when I go into the bootloader there is a line that says "PSOD-wrong platform". I'm guessing that a code somewhere has changed somehow telling the phone that it doesn't have a touchpad, possibly because the phone the ROM was ported from didn't have the touchpad. It might be a longshot but that is my best guess.
I have no idea how else to troubleshoot this and any help would be great.
Thanks in advance.
Craig

[Q] Think my hardware is possessed

So at first I thought the issues I am going to mention were related to the ROM, but after various flashes and really considering if they were related to Apps I have installed, I think it's the device.
Home Button - After my phone has been on for about 1/2 a day or so, I can no longer use the home button as normal. Each click acts like a long press. I also notice when this is happening some screen clicks are like a long press. If I go into the gallery app, I cant open the folders, it tries to 'Select' them as if I were going to mass delete them.
Brightness - I never use Auto Brightness and usually set my screen to Max but ill be damned if my screen doesn't somehow always go to minimum power a few times throughout the day. It can be difficult to change in the bright Phoenix days when power is set to minimum.
Any ideas? I don't use any cases that might be depressing buttons or anything like that. I do have a screen protector, but Ive used this vendor for years.
Thanks
MoreGone said:
Home Button - After my phone has been on for about 1/2 a day or so, I can no longer use the home button as normal. Each click acts like a long press.
Click to expand...
Click to collapse
What ROM are you using? I've got the same problem with the home button acting as a long press. This behavior started when I moved to a 4.2 based ROM - first CM 10.1 and now AOKP JB MR1 B5. It's really obnoxious. Not sure if it's the hardware or software since it goes away when I reboot. I'm also not using any case or screen protector.
I might try downgrading to a 4.1 ROM to see if it really is something in 4.2 or the hardware. Been hesitant to do so thanks to 4.2 moving everything on the SD card to the /data/media/0/ directory. (Can't post a link, Google 'android 4.2 0 folder')
Curious to hear if anyone else is having this issue?
Update: Should have searched Google before searching XDA! It is a known issue that was fixed 4 days after CM 10.1 M2. Google for 'CYAN-283' to find the ticket. Can't wait for M3 to come out so this can be resolved!

[Q] Disappearing Dialer on T959v

I have searched heavily for this issue and have not been able to find anything. If I have missed a post, please point me in the right direction.
I have a T-Mobile T959v that is completely stock Gingerbread. It has been carrier unlocked via NCK unlock code. Everything seems to work just fine on the phone. The problem is when I dial a number and press the call button on the screen, the dialer will swoop off to the left side of the screen and never return. The notification bar is still visible. The navigation buttons at the bottom all light up. The navigation buttons do not seem to work during this time. Even after the call is ended by the other party I have to pull the battery to get the screen back to normal and the navigation buttons work just fine until I press the send button when making another call.
I have installed a couple of new proximity sensors. - Did not fix the issue.
I have tried factory resets and clearing cache. - Did not fix the issue.
I have used the Heimdall One-Click to reflash the phone (did not reflash bootloader). - Did not fix the issue.
Anyone experience this before? Is there a solution? Are there any suggestions on what I might try?
That's very strange. I've never seen that before.
If you are willing to read and try, you could try upgrading to one of the ICS or JB custom ROMs here and see if that helps.
Sent from my Nexus 4 using xda app-developers app
I had this before on stock Gingerbread, I just flashed up to ICS. It pissed me off.

[Resolved] [Q] Why is Haptic Feedbak weird?

Hello,
Issue with haptics!
Device: Samsung Galaxy Win Duos/Grand Quattro GT-i8552.
Kernal: Stock
ROM: COSMIC (CM10)
Previously, when it was still the stock Android 4.1.2 the virtual buttons of the "Pie Controls" of GravityBox always vibrates the device when a button is selected e.g. recent apps, home, or the back button. And, that's why I did not use the Pie Controls feature, and because I don't like too much haptics espeically when just trying to check recently opened apps or even just going to the home screen.
The first time I switched to COSMIC, pressing/selecting a G.B. Pie Controls button wouldn't cause the device to vibrate, so I used the Pie Controls. The vibrations still worked for calls and messages and all that. Suddenly, after I tested it with Antutu Benchmark, all those buttons would return a haptic feedback ever time they're pressed. I didn't know where to turn this off. Went online for help but found no easy way of stopping it, so I re-flashed the ROM. Haptics was still there. I re-flashed it again, it still vibrates. I got tired, so I tried to just ignore it. And out of nowhere, I flashed it again, and fortunately, I guess it was the third or fourth time of flashing of COSMIC, those haptics on the Pie Controls buttons were gone. :laugh:
Then something happened that I have to flash it again, now the haptics are back. What's the explanation of this haptics acting like this? Is there a way to turn haptics off per app?
Thank you! :fingers-crossed:
-----
And I just discovered that toggling on the 'Power Saving' turns it off. It must have been turned on when I ran the test for maximum performance of course. This is kinda funny.

Categories

Resources