Hi Friends,
I got a problem. In the CyanogenMod I have an Offset on the bottom of the screen (2mm) when I hold the softbuttons in my right hand. This problem occured in the official builds of CM and in the FXP - buils, including the latest, too. This bug is really annoying (especially while writing).
Do you have any idea?
Hi, i have this problem too in FXP054, exactly on left side of screen. I noticed another 2 problems:
1) Czech keyboard is QWERTZ not QWERTY!
2) CArrier network data should be turned off after firts installation, it has eaten me half of my credit!
I'm much new, so posted here.
Do you have the problem also when you got the screen in horizontal mode? It's very complicated to hit the buttton for changing the layout to numbers or to make a dot.
Have you tried other builds?
Which model do you own?
I own ST15i, Cyanogenmod 7.2.0 RCO FXP054. But the offset was in nightly 20 too.
The problem is only in horizontal mode i think (only in 90°). Hitting space when writing is my nightmare!
Did you report the bug via bugtracker?
Sent from my ST15 using XDA App
Can anybody help us?
Ok, I found out something:
The bug isn't present in any other orientation than the horizontal mode (softbuttons pointing to the right)
In Multitouch, when I keep another point pressed, also not present.
I already tryed screen recalibration and everything. Please anybody help me.
Update:
The bug is sadly still present in FXP103 CM7.2 - I tried everything that I could imagine.
CM9 is still very unstable, but from what I tested, the bug didn't occure there.
Please, expirienced members: help me!!
Related
Anyone experiencing unresponsive touch screen issue with GingerDX, this issue only occur in bottom area of display, such as "space button" "delete button" on virtual keyboard and all apps. I need to touch it many times to make it work.
GingerDX is my first ROM, hope someone can tell me how to fix it... According developer thread i have do this :
If you get unresponsive touchscreen, please wipe cache partition, dalvik cache, and reboot twice
Click to expand...
Click to collapse
and I have do it, but still no luck.
Thanks
Sorry my English bad
Kind Regard.
Try factory reset and installing again. It helps you too much
It's not just you - I get the same problem (hard to drag the notification bar back up, bottom row of keys is unresponsive on certain keyboards) - also using GingerDX
I did see the dev acknowledge the notification dragging issue as "a common problem with gingerbread roms" so I'm not sure what's going on.
edit: http://forum.xda-developers.com/showthread.php?p=16699717&highlight=notification#post16699717
benjymous said:
It's not just you - I get the same problem (hard to drag the notification bar back up, bottom row of keys is unresponsive on certain keyboards) - also using GingerDX
I did see the dev acknowledge the notification dragging issue as "a common problem with gingerbread roms" so I'm not sure what's going on.
edit: http://forum.xda-developers.com/showthread.php?p=16699717&highlight=notification#post16699717
Click to expand...
Click to collapse
alll CM7 based ROM's havethis issue because of a bug in CM7 itself i think
To the people of Turl's and Jokersax' CM9.
I have a touchscreen re-calibration app, I just tested it out and it seems to be working perfect. Don't hold me to it, but i think this is a pretty good temporary fix.
I'd love feedback, i didn't code this but after a few searches i was able to realize this is a universal fix for touchscreens that have been acting up.
Special thanks to gojimi. At least i hope.
Can you link the source please.
Cheers!
Just a question, do we actually need touch calibration after flashing cm9? Cause AFAIK, when I tried the jokersax rom, the only problem I had was app incompatibility and APN errors...
helmy96 said:
Just a question, do we actually need touch calibration after flashing cm9? Cause AFAIK, when I tried the jokersax rom, the only problem I had was app incompatibility and APN errors...
Click to expand...
Click to collapse
Sometimes, it will act up.
Ouh. Ok, didn't think it would happen... hope u don't think n
that I a newb thru this question, I'm well informed, just not very active due to sch...
helmy96 said:
Ouh. Ok, didn't think it would happen... hope u don't think n
that I a newb thru this question, I'm well informed, just not very active due to sch...
Click to expand...
Click to collapse
I know what you mean, sometimes homework takes away most of my time too. But just use CM9 as your daily driver, and you'll be well informed on any issues that will occur.
This actually screwed up my touchscreen..anyway to uninstall?
Hi,
I have a software issue with my touchscreen :
1/ Got stock ROM, then CM7, then CM7-Neutrino-2.2 => screen was OK
2/ Installed CM9-Turl-v8 => an unresponsive horizontal line appeared, around 100px high
3/ Tried to come back to CM7, CM7-Neutrino, CM9-Joker-0.4 => bug still there
4/ Tried this calibration app, but couldn't click the button because it was under the unresponsive line, so turned the phone into landscape or upside-down to execute => bug still there
5/ Flashed PDS fix => bug still there, fear of a hardware issue
6/ Installed CM9-Joker-0.5 with awesome Installer => touch screen goes totally crazy (phantom-touches), BUT the line is finally responsive !! So, le wild idea appears
7/ Retried this calibration app, this time in the right way => SCREEN FINALLY OK !!!...
8/ ... For about 2 hours... Now my phone combines 2 issues : a new horizontal line is unresponsive (thinner than the old one), and crazy phantom-touches happen really often...
I was desperate, but now I know my problem is software, I see hope ! Am I the only one to have this problem ?
Thank you in advance
David Guillot said:
Hi,
I have a software issue with my touchscreen :
1/ Got stock ROM, then CM7, then CM7-Neutrino-2.2 => screen was OK
2/ Installed CM9-Turl-v8 => an unresponsive horizontal line appeared, around 100px high
3/ Tried to come back to CM7, CM7-Neutrino, CM9-Joker-0.4 => bug still there
4/ Tried this calibration app, but couldn't click the button because it was under the unresponsive line, so turned the phone into landscape or upside-down to execute => bug still there
5/ Flashed PDS fix => bug still there, fear of a hardware issue
6/ Installed CM9-Joker-0.5 with awesome Installer => touch screen goes totally crazy (phantom-touches), BUT the line is finally responsive !! So, le wild idea appears
7/ Retried this calibration app, this time in the right way => SCREEN FINALLY OK !!!...
8/ ... For about 2 hours... Now my phone combines 2 issues : a new horizontal line is unresponsive (thinner than the old one), and crazy phantom-touches happen really often...
I was desperate, but now I know my problem is software, I see hope ! Am I the only one to have this problem ?
Thank you in advance
Click to expand...
Click to collapse
You are not the one who have this problem I had nottachtrix at first and touchscreen was working well when I instal MIUI 2.4.27 from there started my problem now my buttons sometime stop working when I bloc and then unblock phone buttons start working sometime it need restart phone I didn't try this ap yet but I think it's software because when buttons stop working my touchscreen is working full only buttons are not responsive is there some fix pleas PM me
After using nottachtrix arora installer to calibrate my touch would have random deadzones and w,e,s,z didnt work. Tried recalibrating with installer to only make it randomly worse or slightly better. This did the trick thoough. Thanks very much!!
help me
i was used gingermod rom and change to aokp milestone 6 suddenly yesterday seen that there are area in screen didnt work i have tryied to back to gingermod still not work try this software but also didnt work what i have to do please help me
hi help me
hi help me
i have one tablet eken w70 wiht the touch invsted help me
this touchRecelibrete not succes
help me
[email protected]
Can you please give us the correct way for Re calibration
Sent from my MB860 using xda app-developers app
i'll try it, my screen not responding now
Hello,
I'm about 2 hours trying to solve this problem but nothing came to me.
I have the common bug of multitouch on atrix (and notice that trying to use SwiftKey)
When I press 2 points fast, I line is draw (like a swype on the screen) [Tested on Dev Tools > Pointer Locations]
I'm using the CM7 Nightly with the 5 points of touch.
Kernel not changed.
Can someone point a fix or something that can help me?
Thanks in advance.
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.
Hey guys,
Found a bug on CM10 Beta 1 by Ivendor for Samsung i9001. when tilting from portrait to landscape in text messaging half the keyboard turns black. Is there somewhere i can post this so that the people who can address it can see it? Or should i just try the dev forum for that rom?
I would start off by sending a private message to Ivendor?
Spheron said:
Hey guys,
Found a bug on CM10 Beta 1 by Ivendor for Samsung i9001. when tilting from portrait to landscape in text messaging half the keyboard turns black. Is there somewhere i can post this so that the people who can address it can see it? Or should i just try the dev forum for that rom?
Click to expand...
Click to collapse
Can you get this bug all of the times when you turn your phone or just 1 time? I've never met this type of bug since I tried this ROM with Nexus kernel.
I did send Ivendor a PM but he must have missed/ignored it as the issue was not fixed in CM10 Beta 2.
The issue will not be there when you first tilt the phone after a reboot but do it a second time and there she blows.
Sadly this is the best ROM out there for i9001. I tried SlimBean and it has a horrible battery drain. EHNDROIX II looks and moves awesome but it keeps the phone awake at times which makes for another battery drainer and, iGO Primo runs horribly on this one... sound is ok but the screen stutters like crazy.