Hi all,
I installed the ICS Passion V13.1 ROM on my little guy here, and he looks sick.
Aside from the operating system itself functioning fantastically there are 2 problems that no amount of google or forum searching have helped me relieve.
1) Hard and soft buttons appear to have identity problems. The volume buttons are inverted, and the home and settings soft keys have decided to switch as well. It's inconvenient at the worst but I would still like to fix it.
2) And this one is much more annoying: the screen orientation is 90 degrees clockwise to the physical orientation of the phone. By that I mean that the "top" of the displayed screen is never at the top of the screen when holding the phone- it's always to the right.
Running android verson 4.0.3,
Kernel Version 3.1.10_ICS_KISS Yum_yum_good#1
ICS Passion version 13.1
Build number IML74K
Any suggestions here would be amazing. I cannot find any options to calibrate the gyros or the accelerometers.
Thanks all.
I guess you're in the wrong forum here.
This forum is only for i9003.
Related
Hello,
My Raphael 100 dpad buttons are not working in android roms!
I can't go 'back' or to 'home' in Android
"Home" button and "call" button act as navigation key (left)
"back" button and "call end" button act as navigation key (right)
I have tried numerous roms (neofroyo, thunderbolt, hercules, cbv2, cherrypie and more), even non-cwm roms (frx07, froyob v5, v6)
Non of them worked
I also tried with several different kernels (very old, old and new) but still same.
Does anyone have solution for this?
Haven't had that problem in a while but then again I haven't really played with XDAndroid about that long. Even still, never had that much of an issue. Usually I could just cycle the screen off then on and the problem was gone.
Is it possible that you are constantly sliding across the buttons? I know I can get it to go crazy after sliding across the buttons a few times...
No its completely not working only in android roms as if the keys are not mapped
I even tried FRX03 (which was working fine couple of months back in the time) but somehow the keys are not working now... really strange
That's a new issue to me. I take it the d-pad works in winmo but not after you boot into android? Have you filed a bug report yet?
Curious, does the screen react to touch?
Curious said:
Nope it doesn't light when I touch dpad
Click to expand...
Click to collapse
So the d-pad doesn't work in winmo or does it?
it works ! but will take full advantage of your d–pad, your driver must generate the proper virtual key codes ~ http://msdn.microsoft.com/en-us/library/bb821761.aspx
I've installed CM9 (latest nightly) on my Tab 2 7.0 and prefer to use the phone UI. I've added the following to system/build.prop
ro.sf.lcd_density=240
qemu.hw.mainkeys=0
This successfully changes to the phone UI and displays the nav bar at the bottom. Unfortunately, the soft keys (Back / Home / Recent) do not display.
It is possible to edit the navigation bar through the settings menu, but only the Menu button can be reassigned. It is also the only button to appear when editing.
Any ideas on how this can be fixed to properly display the buttons?
zinfinion said:
I've installed CM9 (latest nightly) on my Tab 2 7.0 and prefer to use the phone UI. I've added the following to system/build.prop
ro.sf.lcd_density=240
qemu.hw.mainkeys=0
This successfully changes to the phone UI and displays the nav bar at the bottom. Unfortunately, the soft keys (Back / Home / Recent) do not display.
It is possible to edit the navigation bar through the settings menu, but only the Menu button can be reassigned. It is also the only button to appear when editing.
Any ideas on how this can be fixed to properly display the buttons?
Click to expand...
Click to collapse
Aokp (rom control) allows you to change the keys around.
I would love to play around in a phone ui on here too.
scottx . said:
Aokp (rom control) allows you to change the keys around.
I would love to play around in a phone ui on here too.
Click to expand...
Click to collapse
I tried AOKP Milestone 6 as well. Similar but different issue. The soft keys appear when using the phone UI DPI, but they are stacked vertically in the horizontal bar. Basically you can see a half cutoff back button and a half cutoff home button. The recent button is off screen. And if you rotate the device, the soft keys rotate in place, and are then horizontal in the vertical bar.
I'm getting the impression that at this stage in their releases neither CM9 nor AOKP are accounting for the Tab 2.0's 90 degree offset default sensor coordinates. Another bug that convinces me of this is that Mega Jump (notorious for tablet issues) when launched rotated to landscape when using AOKP (using tablet UI / DPI=160) but appeared vertical on the landscape oriented screen, pillarboxed on both sides. To avoid any confusion envision the tablet being held in landscape orientation, with the 352 wide x 600 tall game boxed on both sides by black 336 x 600 rectangles. Hopefully that makes sense (I had similar issues with some of Aldiko's menus wanting to prefer landscape over portrait as well, no pillarboxing though).
Anyhow, I then switched to stock rooted deodexed UEALD3, Mega Jump launched, stayed in portrait orientation, and filled the screen as it should. Either orientation, stock or AOKP, the tilt controls worked fine.
Long story short, all this has me sticking with stock for now. I'm interested to see if the Nexus 7 is prone to these sort of issues, or if it has a default portrait oriented sensor akin to most phones, since it basically appears to be designed to be used in portrait. A big phone without the phone as it were.
Please let me know if there are any other things you think might work. I'd be thrilled to get around this issue.
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.
I really love the Nexus 5, But I have noticed that when trying to use the bottom row of buttons on the keyboard It aperantly detects one of the 3 on screen buttons and does what ever that button does! Which is a P.I.T.A. when your trying to type!
After the first few times of it doing it I thought something was wrong with my keyboard but after being a little more carefull and watching where I was touching the screen it definately has a invisible detection line for the buttons thats a tad too tall!? [I hope this is proper name for the description IDK the tech lingo for this]
Device info:
Stock Nexus 5
swype [paid] keyboard
portrait mode
Thanks in advance.
Questions belong in the Q&A forum. That's what it's there for.
Never heard of that happening.
Removed
[Q] Help with possessed keyboard & unusable homescreen column in Galaxy S4 sch-1545?
I am having problems with my new Galaxy Verizon S4 Sch-1545. I have searched forums and google and have been unable to find working solutions for the following 3 problems:
1. On the home screen and all of the other 6 screens, any app icon that is placed into the second column from the right becomes unusable and unmovable. In effect, it becomes a picture of an icon. I can tap and hold an icon in any other column then use it to bump icons in the 2nd column but when I release the icon, the bumped icon snaps back into the 2nd column. The only solution I've found is to use Wondershare Mobilego to connect the S4 to my pc, turn on mirroring so the s4 screen appears on my pc screen, then use my laptop's mouse pad to tap/hold and move icons out of the second column. After they are no longer in the 2nd column, icons become useable again. I made sure Interaction control in settings is OFF and that no part of the touch screen is blocked by the interaction control setting. Turning the phone off/on doesn't help nor does removing the battery. I have Malwarebytes installed and it has found no malware.
2. The Samsung stock keyboard randomly types letters, especially in portrait mode. In fact, I gave up using the keyboard in portrait mode. For example, when I type the letter h, the phone enters the letters gj. Sometimes the backspace key flickers and letters are randomly entered and erased very quickly while I sit there and watch without touching the phone. I have disabled, swype, predictive text, gestures, everything I can possibly find that might cause the phone to enter letters I didn't type. I'm using Touchwiz and have no other launcher installed on the S4. When I tried other keyboards like Smart Keyboard, I had the same problems.
3. In Settings, swype keeps turning itself on no matter how many times I turn it off.
Not a technical person but I'm pretty comfortable with trying technical solutions if need be. I just switched from iPhone (which I'm beginning to regret) and I jailbroke the iPhone after each operating system update so if the problems above call for a technical solution, just point me at the step-by-step instructions
Android version 4.4.2
Baseband 1545VRUFNK1
Kernal 3.4.0 Nov 4, 2014
Build number KOT 49H.1545VRUFNK1
Hardware version 1545.07
Security software version MDF v1.0 Release 3
VPN v1.4 Release 2
Hi
Thanks for writing to us at XDA Assist. It looks to me like you're dealing with a hardware failure, specifically a faulty digitizer. I'd suggest you find an app on the Play Store to test your digitizer, it sounds like you have a dead spot/column.
No response in two days, thread closed, thanks.