Related
Hey Ive seen issues with people having trouble with the distribution of LEDs on the keyboard with not seeing keys and others to bright and thats not me haha. I was wondering though if anybody knew a registry hack or something that would let the backlight on the keyboard stay on longer than 5 seconds? That is the biggest annoyance of this phone that ive seen so far.
aaron580 said:
Hey Ive seen issues with people having trouble with the distribution of LEDs on the keyboard with not seeing keys and others to bright and thats not me haha. I was wondering though if anybody knew a registry hack or something that would let the backlight on the keyboard stay on longer than 5 seconds? That is the biggest annoyance of this phone that ive seen so far.
Click to expand...
Click to collapse
Do a search for a utility called Advanced Config, it has a setting to change the backlight timeout, among a lot of other things. You'll need to have the ARM4i version of ppc .NET 3.5 installed also.
BEWARE: Use the tool at your own risk. Don't turn menu animations and start menu animations on, as it has caused my start menu to go really wonky (all the colors are jumbled and its impossible to read) Turning this off made it behave as expected. Just a warning
Hey thanks man. I didnt even know that setting was in advanced config and ive used since the mogul lol.
Doesnt work
I have tried the tweak in advanced config and nothing changed, has anyone else had luck with this?
oldquser said:
i have tried the tweak in advanced config and nothing changed, has anyone else had luck with this?
Click to expand...
Click to collapse
it can not be changed
This is one of the most annoying things about the TP. Anytime you pause for 5 seconds the keyboard backlight goes off! Grrr!
No kidding. I completely disabled the light sensor on my P4000, it was always on as long as the slider was open. I even watched an hour long episode of top gear while I sat in a Mazda dealership while having an oilchange done on my car.
I too have been equally frustrated with this. With no solution in sight, I think I might have thought of a program that could save our sanity. The only problem is that i've only THOUGHT of it and it doesn't exist yet. I've started a thread in the 'Development and Hacking' section. Here's the link http://forum.xda-developers.com/showthread.php?t=490267
Add comments, add ideas, just add support
Has anyone noticed a change in how the touchscreen behaves after installing ICS?
It seems to me that it is biased a little more towards interpreting a touch as swipe or scroll rather than select. For example clicking links in a webpage or tapping icons on the homescreen seem to require a much more deliberate effort to select/open. It's not awful, but I would like to be able to bias it back a little more to selecting rather than swiping.
Is there a setting for this anywhere or an app available that allows adjustment?
I would to know too.. I hate this..
But it's not just from latest ICS 4.0.3 International, the Beta version also suffer same thing.
Is HC not like this? (I upgraded to 4.0.3 Beta as soon as after bought Mediapad )
Yes, I noticed it also. When you turn on Settings - Developer options - Pointer location, it clearly shows how your clicks/dots becomes swipes/lines.
yes, you're right.. it sometime (most time ) cause texting experience not so fluid (letter not appear as it's detected as swipe not click).
got the same thing.. i've changed the launcher, so with the Apex launcher it's not that bad in the homescreens.. when i enabled the option to show "pointer location" i can see the "tap" as a line, or a "swipe" line :\
tried the same on my Galaxy S, and all the "taps" are only a small point.. it's much better than on the MediaPad.. i hope it's just a software issue and it can be solved..
maybe, we could try something like "screen booster" or "touchscreen booster" from the Market (Play)
Erratic screen while charging
The other thing I've noticed after ICS international is that the touchscreen is now erratic while charging and in a case. I believe this is a common problem with capacitive touchscreens, but hadn't noticed it until after flashing ICS. It is not an issue if I remove the pad from the case and hold it in my hand.
Anyone else seen this?
This sensitive touchscreen isn't Angry Birds friendly. Constantly shakes a little bit.
soooo.....is there any solutions?
noaustin said:
soooo.....is there any solutions?
Click to expand...
Click to collapse
Not unless huaweis coders tweak it or releases the source code.
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
This ROM is working very well on my UK Rhod 100. Very stable & fast and since the latest update I have the correct HW keyboard layout. Battery life is limited but carrying a second battery is an easy solution.
The previous problems where the screen would not turn on after several pushes of the power button almost never occurs. However when the battery runs down to about 30% the screen always changes such that a red overlay occurs visible mainly on screens with a white background (see pics). Also when the screen changes ghost images remain from previous screens. Also at this point sometimes the screen will not turn on despite repeated use of the power button. Strangley, even though there is nothing visible on the screen I can unlock the phone by swiping in the expected area (and get haptic feedback) and long press the power button and turn off the device by pressing in the expected areas. Upon a reboot the screen will initially be back to normal but then if the battery is below 30% the problem will return. These issues never occur if the battery is above 30%. If I take screenshots with shootme the pics captured look normal when viewed after a reboot before the problem recurs. Not sure what the system does when the battery falls to this level but the screen is definitely affected. This problem also occurs with a fresh install with no apps installed.
If anyone has any ideas as to what could be the cause (and even better a solution) it would be most welcome. Thanks to all those behind this project.
Sorry you are having troubles. Unfortunately as noted in the first post for that thread we only have RHOD400s to test with. No one else has reported any similar issues. The 100s are known to be the problem children of the RHOD family. If you come up with a fix let us know, and we will try to include it in any future releases.
wizardknight said:
Sorry you are having troubles. Unfortunately as noted in the first post for that thread we only have RHOD400s to test with. No one else has reported any similar issues. The 100s are known to be the problem children of the RHOD family. If you come up with a fix let us know, and we will try to include it in any future releases.
Click to expand...
Click to collapse
Did you look at ACL's work on RE'ing that panel code...?
He said something about the panel power up/power down sequence on the 100's (the AUO panel specifically) to be quite a bit different.
arrrghhh said:
Did you look at ACL's work on RE'ing that panel code...?
He said something about the panel power up/power down sequence on the 100's (the AUO panel specifically) to be quite a bit different.
Click to expand...
Click to collapse
arrrghhh, I noted your post in the ROM development thread regarding the start up sequence in the OMGB kernel for the AUO panel. Perhaps this would solve my issue as well. If this change could be added to the next edition of this ROM my device would be virtually bug free.
As noted in the thread, we do not have any RHOD100s to test with. It is very unlikely that this will happen. If you would like to make your own kernel with these changes I can post it.
issue or not?
hi,
thanks a lot, first of all.
I've been trying to figure out how to get an Italian keyboard layout.
any suggestion?
-p.
paolora999 said:
hi,
thanks a lot, first of all.
I've been trying to figure out how to get an Italian keyboard layout.
any suggestion?
-p.
Click to expand...
Click to collapse
try using AItype Keyboard Plus which supports multiple languages and keyboard layouts
Sorry I didn't express myself properly. I meant the physical keyboard. In other thread I read something about a startup.txt file, I don't know if it applies to this ROM (and moreover I can't find it).
paolora999 said:
Sorry I didn't express myself properly. I meant the physical keyboard. In other thread I read something about a startup.txt file, I don't know if it applies to this ROM (and moreover I can't find it).
Click to expand...
Click to collapse
startup.txt files are only for the SD card versions of the android roms.
You would need to edit the keyboard map. Here is generic android keyboard map info.
There may be apps out there than can change your keyboard map, but I don't know any details about that.
Also in the future it would be best to start your own thread, rather than using an unrelated one. Better yet, post the questions about the rom you are working with in the thread for that rom.
i am having also a screen problem with that Rom and Kernel:
My screen is not calibrated. When i press it's being pressed on somewhere else on the screen.
P.S.
My RAM is not 100 +- this rom showing me 33 for usage on the device :S.
Can someone help me with those two ?
MTN_Cool said:
i am having also a screen problem with that Rom and Kernel:
My screen is not calibrated. When i press it's being pressed on somewhere else on the screen.
P.S.
My RAM is not 100 +- this rom showing me 33 for usage on the device :S.
Can someone help me with those two ?
Click to expand...
Click to collapse
Did you read the link that covered screen calibration listed under related goodies, or did you search for the threads that cover screen calibration under android? Tell us what you have tried, but didn't work.
No idea what you mean by the ram is not 100.
What the heck is going on here? Is this just the thread to jack?
Let's focus on the display issues please folks, as in your response should be related to the original post.
arrrghhh said:
What the heck is going on here? Is this just the thread to jack?
Let's focus on the display issues please folks, as in your response should be related to the original post.
Click to expand...
Click to collapse
idc if they will move my question the the original one...
but i can't fix my calebration points...every time i need to launch the HTC program :\
Problem resolved?
akk29 said:
This ROM is working very well on my UK Rhod 100. Very stable & fast and since the latest update I have the correct HW keyboard layout. Battery life is limited but carrying a second battery is an easy solution.
The previous problems where the screen would not turn on after several pushes of the power button almost never occurs. However when the battery runs down to about 30% the screen always changes such that a red overlay occurs visible mainly on screens with a white background (see pics). Also when the screen changes ghost images remain from previous screens. Also at this point sometimes the screen will not turn on despite repeated use of the power button. Strangley, even though there is nothing visible on the screen I can unlock the phone by swiping in the expected area (and get haptic feedback) and long press the power button and turn off the device by pressing in the expected areas. Upon a reboot the screen will initially be back to normal but then if the battery is below 30% the problem will return. These issues never occur if the battery is above 30%. If I take screenshots with shootme the pics captured look normal when viewed after a reboot before the problem recurs. Not sure what the system does when the battery falls to this level but the screen is definitely affected. This problem also occurs with a fresh install with no apps installed.
If anyone has any ideas as to what could be the cause (and even better a solution) it would be most welcome. Thanks to all those behind this project.
Click to expand...
Click to collapse
In an attempt to bring this thread back on topic I thought I'd report back that the original problem has not happened for a few weeks. My setup is essentially unchanged, the only change is that I have been using One Power Guard to try and improve battery life, which by the way seems to be effective. Managed 13hours with light use (few calls/occassional data for email web browsing)
Anyway it could be coincidence but it is possible that one of the tweaks performed by the app has sorted this issue. Since nobody else has reported the same problem I'm not sure how useful this info is but hopefully it may be of use to someone.
[Q] Flashing/blinky screen in black but only on "application level" of display
Hey folks,
So what I'm seeing is the application area/layer of the screen blacking-out in a blinky way, and this seems to happen when there's screen updates like from the application or when I'm scrolling with my finger. The weird thing is this only seems to affect the "application level" layer -- the Status bar and other things like CPU usage (and overlay apps like SwipePad) are unaffected and don't black-flash.
I'm running PAC-MAN ROM (Android 4.4.4) but have experienced this on other ROMS so I think this is either a Note i717 thing and/or something that I'm doing to create this issue. It actually happened with less intensity with other roms of previous Android versions. (probably back to 4.4.2)
What I done wrong? I'm getting a hurt real bad. (a Russell Peters reference, for those who haven't heard his older material)
mentalfloss said:
Hey folks,
So what I'm seeing is the application area/layer of the screen blacking-out in a blinky way, and this seems to happen when there's screen updates like from the application or when I'm scrolling with my finger. The weird thing is this only seems to affect the "application level" layer -- the Status bar and other things like CPU usage (and overlay apps like SwipePad) are unaffected and don't black-flash.
I'm running PAC-MAN ROM (Android 4.4.4) but have experienced this on other ROMS so I think this is either a Note i717 thing and/or something that I'm doing to create this issue. It actually happened with less intensity with other roms of previous Android versions. (probably back to 4.4.2)
What I done wrong? I'm getting a hurt real bad. (a Russell Peters reference, for those who haven't heard his older material)
Click to expand...
Click to collapse
If you would consider this a screen flicker, you may want to try disabling HW Overlay in the developer options.
Another option may be to read up on POLLUTIONS "Patch". There is a thread for it, but I cannot say as to what issues it will fix. Apparently it is a miracle cure in tye Beanstalk thread.
Thats why I say....read on it first.
Sent from my SAMSUNG-SGH-I527 using XDA Free mobile app
captemo said:
If you would consider this a screen flicker, you may want to try disabling HW Overlay in the developer options.
Another option may be to read up on POLLUTIONS "Patch". There is a thread for it, but I cannot say as to what issues it will fix. Apparently it is a miracle cure in tye Beanstalk thread.
Thats why I say....read on it first.
Click to expand...
Click to collapse
Yeah those are some good ideas, but here's some more info:
I don't have the HW Overlay option enabled.
The "flickering" is not the entire screen, and it's more like a "black flicker", and ONLY on the "application layer"
I found the patch you mentioned in this thread and I'll see if it addresses it when I get a chance to work on the device.
Oddly, I just booted the phone with OTG HDMI connected to a monitor and the flicker is gone! :/ Not really a solution but an interesting oddity.