Related
It's time to have a new Opera Mobile again.
http://www.megaupload.com/?d=C54S9CCB
See why I don't like them to be built into the ROM? These things change too fast.
Can this be installed to SD?
Sorry, no storage card version yet.
But keep a watch for it here
http://forum.xda-developers.com/showthread.php?t=401643
Not sure if this version is better than the last one. Still playing with it to find out.
edit: The display is a bit messed up in this version.
Does anyone else find this the case too on their Athena?
Eagle: What numbers are you liking for the adaptive zoom? Sorry I can't answer your question as I have never messed with these settings before. Also is yours rotating your screen after you close/minimize it?
Goatmaster said:
Eagle: What numbers are you liking for the adaptive zoom? Sorry I can't answer your question as I have never messed with these settings before. Also is yours rotating your screen after you close/minimize it?
Click to expand...
Click to collapse
I set the minimum overview zoom to 70 in earlier build, but 85 in more recent builds. The only purpose is to allow me to activate a link without zooming in.
Tried this build on my X7510. A few observations:
1. Screen rotates on shut down.
2. Couldn't use hardware keyboard. After each key stroke, the entire field was highlighted, which caused the next key stroke to over-write the one before.
3. Opera was not set as default browser.
I went back to build 1184. The first two issues made it unusable for me.
magxs said:
Tried this build on my X7510. A few observations:
1. Screen rotates on shut down.
2. Couldn't use hardware keyboard. After each key stroke, the entire field was highlighted, which caused the next key stroke to over-write the one before.
3. Opera was not set as default browser.
I went back to build 1184. The first two issues made it unusable for me.
Click to expand...
Click to collapse
I'm back to 1184 also. Thanks for posting your test results.
My Touchwiz update went fine on my stock unrooted tab. However, the new pan and tilt functionality doesn't work even though I've turned on all the settings and calibrated my tab.
Am I missing something or has anyone else experienced this?
this feature looks kind of.... stupid
For photos in the Gallery and web pages you need to put two fingers on the tablet initiate it's ability to zoom. They show holding it by the bottom corners then touching the screen with your thumbs. It works as show on mine. It can also be turned OFF in settings. Make sure its not OFF if you want to try it.
Ultimately it is a gimmick. Can't see even holding the tablet that way in normal use.
ericyyou said:
this feature looks kind of.... stupid
Click to expand...
Click to collapse
Agreed. For me, pinch to zoom works much better.
I like the ability to move an icon/widget from screen to screen while holding it down and turning tab left/right.
Much better for moving icons.
4dthinker said:
For photos in the Gallery and web pages you need to put two fingers on the tablet initiate it's ability to zoom. They show holding it by the bottom corners then touching the screen with your thumbs. It works as show on mine. It can also be turned OFF in settings. Make sure its not OFF if you want to try it.
Ultimately it is a gimmick. Can't see even holding the tablet that way in normal use.
Click to expand...
Click to collapse
Apparently I'm as stupid as the feature...didn't realize two fingers had to be on the screen. Doh.
walkamongus said:
Apparently I'm as stupid as the feature...didn't realize two fingers had to be on the screen. Doh.
Click to expand...
Click to collapse
Pwned. Lol it shows a demo of how to use it the first time you open the browser.
Bear with me here, this issue is kind of hard to describe. When I am playing a game that requires touch inputs from both hands, I often get bugs. It's most obvious in games that have controller-style overlays. As is normal, I am using my left thumb to tell a character to move right or left, and then I press the button on the right to jump. However, when I release my jump, I stop running. The screen no longer recognizes that my left thumb has been pressed down the whole time and should still be moving in the direction I am pressing. This happens in Bean's Quest, Chono'n'Cash, Delver, Gunman Clive, and any other game of this nature I have tried on my device.
I played some of these games just fine on my old Evo. Is anyone experiencing this issue? I experienced it on stock as well as several custom roms I have tried.
Turn off "Htc gestures" you'll find it in settings, display & gestures!
When the display senses three finger inputs it renders it touch inputs useless...run a multi-touch test app and you'll see.
gutrrob said:
Turn off "Htc gestures" you'll find it in settings, display & gestures!
When the display senses three finger inputs it renders it touch inputs useless...run a multi-touch test app and you'll see.
Click to expand...
Click to collapse
Doesn't seem to have fixed my issue, I am still having problems with some two finger games. I will be using two fingers just fine, when I remove one finger from the display the first finger is no longer recognized even though it is still touching. I have to remove the first finger and press it again every time.
Do U have any type of lock screen installed. If so uninstall. Use only stock.
Swyped from my eVo
ryanalan82 said:
Do U have any type of lock screen installed. If so uninstall. Use only stock.
Swyped from my eVo
Click to expand...
Click to collapse
Appears that widgetlocker is the culprit! Is this issue documented or known, exactly? What causes it? Thanks so much for the help. I will surely miss widgetlocker.
Please use the Q&A Forum for questions &
Read the Forum Rules Ref Posting
Thanks ✟
Moving to Q&A
I encountered this recently
It seemed to get "stuck" after using multi touch gestures in-game. Tapping the game with two fingers often "unstuck" it, but overall it was extremely frustrating.
This was on an APK not designed for the phone, though
Sorry to bring back up an old thread (is 6 days even considered old?) anyway you HAVE to disable the HTC 3 touch setting gesture because it will ignore anything more than 2 (3 will only register if you swipe up or down, but sense itself registers it, nothing else).
Just made the video below as proof (forgive my foreign accent xD):
Our screen supports (at least) 10 different points (was going to try 11 but I could not get my nose on the screen with my fingers and my girlfriend is asleep).
EDIT: Two things, one: I had widgetlocker installed while I did the above video, it caused no problems. Two: the maximum number of inputs our phones can handle is 10, incase anyone was curious.
EDIT 2: While I don't have the issue with widgetlocker it seems that it is a known problem, but you don't have to disable the lock screen altogether. Go into widgetlocker settings> advanced> retain system key guard. Source: http://forum.xda-developers.com/showthread.php?t=1652038
Racer Of All said:
Sorry to bring back up an old thread (is 6 days even considered old?) anyway you HAVE to disable the HTC 3 touch setting gesture because it will ignore anything more than 2 (3 will only register if you swipe up or down, but sense itself registers it, nothing else).
Just made the video below as proof (forgive my foreign accent xD):
Our screen supports (at least) 10 different points (was going to try 11 but I could not get my nose on the screen with my fingers and my girlfriend is asleep).
EDIT: Two things, one: I had widgetlocker installed while I did the above video, it caused no problems. Two: the maximum number of inputs our phones can handle is 10, incase anyone was curious.
EDIT 2: While I don't have the issue with widgetlocker it seems that it is a known problem, but you don't have to disable the lock screen altogether. Go into widgetlocker settings> advanced> retain system key guard. Source: http://forum.xda-developers.com/showthread.php?t=1652038
Click to expand...
Click to collapse
Installed widget locker again. tried this, multi touch failed. Uninstalled, and back to 10.
Swyped from my eVo
ryanalan82 said:
Installed widget locker again. tried this, multi touch failed. Uninstalled, and back to 10.
Swyped from my eVo
Click to expand...
Click to collapse
Did you try my edit 2? The Retain System keyguard? I can assure you that I have Widgetlocker installed and I have the 10 inputs (that video was recorded with widgetlocker running).
[SOLVED!] - HTC Evo 4G LTE touch screen trouble - WidgetLocker is the problem
Retaining system keyguard in WidgetLocker worked for me! Thank you for this Racer for All. (Actually I found your YouTube video, and a link to this thread)
I was wondering why all the games I played all of a sudden stopped functioning properly (in terms of touch controls... Example: MineCraft PE, moving forward and trying to look left or right - suddenly character would stop moving.)
Sorry to dig up an old thread, but I want people to know if they have WidgetLocker (and don't want to uninstall it) just go to Settings - Advanced - Retain system keyguard - zmag
Because since I bought this device to make the screenshot with the gesture of the palm.
I tried a thousand times but nothing to do.
What is wrong?
I think it's easy! It 'a problem of my device?
The logical option is flagged, but never once succeeded.
Will you help me figure out if something is wrong or some application that bothers him??
Thank you!
did you enabled the motion in the settings > motion > palm swipe to capture (checked)? also tried rebooting/factory resetting it?
Go to your Settings > Motion > Scroll to the bottom and make sure that "Palm swipe to capture" option is checked and then you should be fine to take screenshot using your hands. And by saying your palm we don't mean put your hand on the screen and swipe it to the left or right we mean by the side of your palm on the screen and swipe it..
Thanks to both. I checked everything several times but to no avail!
I tried both with the original ROM when I purchased both with other rom modified (Original - Omega - Fox Hound).
I have to take care in your opinion??
No new ideas??????
The term I've heard is " karate chop" in describing it
1. Shape your hand as if you are going to "karate chop" the right hand side of the screen.
2. Chop the right side and touch the screen with the edge of your hand.
3. Keep your hand in contact with the screen and swipe right > left
I couldn't get to work either until I realised I was moving my hand across the screen too slowly works every time now.
Sent from my CM9 TouchPad
UpInTheAir said:
The term I've heard is " karate chop" in describing it
1. Shape your hand as if you are going to "karate chop" the right hand side of the screen.
2. Chop the right side and touch the screen with the edge of your hand.
3. Keep your hand in contact with the screen and swipe right > left
Click to expand...
Click to collapse
I do not know how to thank you! I did not realize and was not described in the instructions that you have to touch the screen by moving the palm! I passed over it without touching it or touch the display, I could try thousands of times and still do not understand!! Thanks, thanks and thanks again!!
Cardone71 said:
I do not know how to thank you! I did not realize and was not described in the instructions that you have to touch the screen by moving the palm! I passed over it without touching it or touch the display, I could try thousands of times and still do not understand!! Thanks, thanks and thanks again!!
Click to expand...
Click to collapse
Yep the, "Karate chop," works for me thanks. I thought I might have lost the functionality when flashing to Omega but nope still works fine. Just do it quickly and it'll work.
In fact, I was wrong from the start! Realizing now I'm happier, but not to take the screenshot with the palm, but rather believe that my device had a manufacturing defect!
I'll be modding a case soon to accommodate my extended battery, so maybe this problem will go away, but in the meantime....
I generally wear khakis or chinos to work, and carry my phone in a front pocket. Several times during the day, I'll feel my pocket getting warm and will pull out my phone to find the screen on.
I assume either the side power button or the front "home" button is getting mashed in my pocket and waking up the screen. This happens often enough that I think it affects battery endurance and also creates a risk of accidentally dialing an emergency number (the lock screen is password-protected, so I'm not worried about pocket dialing my contacts).
Anyone else having similar trouble? Are there any settings or 3rd-party apps where I can change the phone to require a multi-button press to wake the screen (like power+home simo, or power+vol up+home, or something like that)?
I also thought it'd be cool to incorporate a "password" into the wake function, like a Nintendo combo attack or something. Home-home-power-vol up or whatever.
Anything like that out there? (I'm currently stock, but if there's a 3rd party app to do this that requires root, that could be the excuse I need to do that!)
Thanks...
Having the same problem. Waiting to see others replies.
It could also be that when you get a text message the screen comes on you need to get a modded version of the mms.apk that let's you keep the screen off when getting text messages. Because if you put the phone in your pocket with the screen towards you body then it could be unlocking it when you get a text and the skin being close is keeping it awake. Specially if you have the glove feature turned on.
Sent from my SCH-I545 using Tapatalk 4 Beta
nativi said:
It could also be that when you get a text message the screen comes on you need to get a modded version of the mms.apk that let's you keep the screen off when getting text messages.
Click to expand...
Click to collapse
Good idea, but (heh) maybe I don't have enough friends but I don't get that many text messages. This happens frequently enough that I've spent a lot of time trying to figure out if some notification did something to wake up the screen, and most of the time I can find no reason for it to light up, which is why I suspect a button mash. (I also do not have the "extra sensitivity for gloved hands" option enabled.)
Maybe a tasker profile that allow the proximity sensor to detecr when the screen is firsr turned on. This way it will detect that or using the lux sensor since it will be dark, and in turn turn the screen back off
Sent from my SAMSUNG-SGH-I337 using xda premium
ktetreault14 said:
Maybe a tasker profile that allow the proximity sensor to detecr when the screen is firsr turned on. This way it will detect that or using the lux sensor since it will be dark, and in turn turn the screen back off
Click to expand...
Click to collapse
A reasonable suggestion. Might be the excuse I need to finally learn how to use Tasker. Wonder if I could get in a situation where I can't get my phone to wake up in a dark room, though....
buy a glass screen protector with at least .3mm thickness. The home button will be recessed and it'll be harder to accidentally pressed.
oilfighter said:
buy a glass screen protector with at least .3mm thickness. The home button will be recessed and it'll be harder to accidentally pressed.
Click to expand...
Click to collapse
I think this is the answer. I just got an Otterbox Defender and there's no way the buttons will get mashed in my pocket now. If the screen comes on again, I'll know there's something else causing it.
MysticCobra said:
I'll be modding a case soon to accommodate my extended battery, so maybe this problem will go away, but in the meantime....
I generally wear khakis or chinos to work, and carry my phone in a front pocket. Several times during the day, I'll feel my pocket getting warm and will pull out my phone to find the screen on.
I assume either the side power button or the front "home" button is getting mashed in my pocket and waking up the screen. This happens often enough that I think it affects battery endurance and also creates a risk of accidentally dialing an emergency number (the lock screen is password-protected, so I'm not worried about pocket dialing my contacts).
Anyone else having similar trouble? Are there any settings or 3rd-party apps where I can change the phone to require a multi-button press to wake the screen (like power+home simo, or power+vol up+home, or something like that)?
I also thought it'd be cool to incorporate a "password" into the wake function, like a Nintendo combo attack or something. Home-home-power-vol up or whatever.
Anything like that out there? (I'm currently stock, but if there's a 3rd party app to do this that requires root, that could be the excuse I need to do that!)
Thanks...
Click to expand...
Click to collapse
As some other people said, it would probably be best to get a case for the phone. I have the Otterbox Commuter and I have had no problems with any accidental button presses. Also, you can't go wrong with a little extra protection for a very expensive phone.
MysticCobra said:
Several times during the day, I'll feel my pocket getting warm and will pull out my phone to find the screen on.
I assume either the side power button or the front "home" button is getting mashed in my pocket and waking up the screen...
Click to expand...
Click to collapse
A couple slight possibilities to consider - do you have these features DISabled?
- Air View - "shows helpful information when you hover your finger over the screen"
- Motions and Gestures (Air Gesture/Motion/Palm Motion).
I think you can see where I'm going with this....
You can completely disable the home button from being able to turn on the screen if you are rooted:
Open /system/usr/keylayout/gpio-keys.kl with a root aware text editor (you should probably make a copy somewhere first in case it gets messed up) - I use root browser lite
Go to "key 172 HOME WAKE" line
Delete the word WAKE
Save and exit
Reboot phone
jbel25nyy said:
As some other people said, it would probably be best to get a case for the phone. I have the Otterbox Commuter and I have had no problems with any accidental button presses. Also, you can't go wrong with a little extra protection for a very expensive phone.
Click to expand...
Click to collapse
Great idea. That's why I posted about my Otterbox Defender in the reply right above yours.
Capp5050 said:
A couple slight possibilities to consider - do you have these features DISabled?
- Air View - "shows helpful information when you hover your finger over the screen"
- Motions and Gestures (Air Gesture/Motion/Palm Motion).
I think you can see where I'm going with this....
Click to expand...
Click to collapse
Good thoughts, but not exactly what I was looking for. These features might cause the screen to stay on once it awoke, but I was actually trying to prevent the screen from waking up in the first place.
I had the same thing happening to me until I put a case on the phone. I just have a hard silicone case, but the lip on the front it just enough to keep the home button from being pressed in my pocket.
I had a similar thing happening several times each day,except I would take my phone out to see that the camera was open. I figured out that it was because I had set a voice command to open the camera from the lock screen. I got rid of the command and it hasn't again
My problem is due to the intermittent wifi connection. My phone screen wakes up every time I get reconnected to the wifi network. It is so annoying.
Chris000001 said:
You can completely disable the home button from being able to turn on the screen if you are rooted:
Open /system/usr/keylayout/gpio-keys.kl with a root aware text editor (you should probably make a copy somewhere first in case it gets messed up) - I use root browser lite
Go to "key 172 HOME WAKE" line
Delete the word WAKE
Save and exit
Reboot phone
Click to expand...
Click to collapse
Did anyone ever figure this one out? I'm now having the same problem as the OP. The home button gets pressed all too often 'in pocket' and I'd love to disable.
The advice above is the closest thing to a solution that I've seen posted around, but in my case, the 'HOME' value for key 172 did not have the 'WAKE' or 'WAKE_DROPPED' value that some other keys have; Just 'HOME'. I'm wondering if maybe an alternate keyboard that I'm using (I usually use SwiftKey) overrides the default keyboard settings file, in which case I should be looking somewhere else?
Capp5050 said:
Did anyone ever figure this one out? I'm now having the same problem as the OP. The home button gets pressed all too often 'in pocket' and I'd love to disable.
The advice above is the closest thing to a solution that I've seen posted around, but in my case, the 'HOME' value for key 172 did not have the 'WAKE' or 'WAKE_DROPPED' value that some other keys have; Just 'HOME'. I'm wondering if maybe an alternate keyboard that I'm using (I usually use SwiftKey) overrides the default keyboard settings file, in which case I should be looking somewhere else?
Click to expand...
Click to collapse
Nothing can mess with that file without root permissions. Maybe the reason you are having the problem is that you DON'T have wake nor wake dropped in there try adding WAKE to gpio and leave the one in generic without eithet
Sent from my SCH-I545 using xda app-developers app
---------- Post added at 01:57 PM ---------- Previous post was at 01:56 PM ----------
reinaldistic said:
Nothing can mess with that file without root permissions. Maybe the reason you are having the problem is that you DON'T have wake nor wake dropped in there try adding WAKE to gpio and leave the one in generic without eithet
Sent from my SCH-I545 using xda app-developers app
Click to expand...
Click to collapse
Then add dropped to gpio if doesn't fix it
Sent from my SCH-I545 using xda app-developers app
reinaldistic said:
Nothing can mess with that file without root permissions. Maybe the reason you are having the problem is that you DON'T have wake nor wake dropped in there try adding WAKE to gpio and leave the one in generic without eithet
Sent from my SCH-I545 using xda app-developers app
---------- Post added at 01:57 PM ---------- Previous post was at 01:56 PM ----------
Then add dropped to gpio if doesn't fix it
Sent from my SCH-I545 using xda app-developers app
Click to expand...
Click to collapse
Thanks, I wasn't implying that another app over-wrote the file, only that another app may be using a different file and thus overriding the function.
For my own edits, I have been dismounting and making changes using a root-enabled file manager and editor and remounting. The changes are there. If I:
a) Remove 'HOME' from Generic.kl, the soft keys and the Power key go dead.
b) put WAKE_DROPPED Generic.kl, there is no apparent effect.
c) Remove 'HOME' from gpio, there is no apparent affect
I'll try adding WAKE_DROPPED to gkio and see what happens...
EDIT: SOLVED!
I think this was more an issue of attention deficit disorder than anything else. I was not paying close enough attention to my edits and making the changes to the wrong files (e.g., Generic.kl instead of gpio).
The original proposed solution WORKS. Specifically,
1) in /system/usr/keylayout, edit file gpio-keys.kl. (need a root-enabled file manager/editor)
2) Under Key 172, remove the word HOME
3) Save the file
4) Reboot
Power key still works for 'waking' and Home key still works for, well, returning Home (but only when awake already)
Capp5050 said:
Thanks, I wasn't implying that another app over-wrote the file, only that another app may be using a different file and thus overriding the function.
For my own edits, I have been dismounting and making changes using a root-enabled file manager and editor and remounting. The changes are there. If I:
a) Remove 'HOME' from Generic.kl, the soft keys and the Power key go dead.
b) put WAKE_DROPPED Generic.kl, there is no apparent effect.
c) Remove 'HOME' from gpio, there is no apparent affect
I'll try adding WAKE_DROPPED to gkio and see what happens...
EDIT: SOLVED!
I think this was more an issue of attention deficit disorder than anything else. I was not paying close enough attention to my edits and making the changes to the wrong files (e.g., Generic.kl instead of gpio).
The original proposed solution WORKS. Specifically,
1) in /system/usr/keylayout, edit file gpio-keys.kl. (need a root-enabled file manager/editor)
2) Under Key 172, remove the word HOME
3) Save the file
4) Reboot
Power key still works for 'waking' and Home key still works for, well, returning Home (but only when awake already)
Click to expand...
Click to collapse
Im on a Verizon Note 3. I did as you described but it did not work. Im thinking it didnt because Root Explorer made a backup file with the non altered txt. Should I delete it to get it to work?