Related
Hello everyone I have a problem with touchsreen on GingerCrust v2.3,
Firstly I want to say sorry because this question is supposed to be in development thread but, since I still have a less posts in this forum so I have to post it in this thread.
Okay this is the problem
I already succeed to flash the GingerCrust v2.2 via CWM 5.0.2.6
And I found there's no problem with touchscreen and then I did the GingerCrust v2.3
And i've got the touchscreen problem (the touchscreen strongly not accurate and hard to swipe for changing app drawer and desktop page)
I already tried to do touch screen calibration test via *#*#2664#*#* touch screen test
but the code won't work
and I tried to find additional framework on it's official thread(by nims11) but there's none of it.
Did anybody have a problem like me? Is there already a solution for the problem that I found
Thats new bug you phased not anyone tell about and not im phasing any that thing
v2.2 and v2.3 are almost same just few things like odexed and some fix not much other thing
I have this problem also.
It's most apparent when typing, because random keys will frequently touch itself, mostly the s and d keys.
For example, I write "I love you", it will turn out as:
"Ids sdldovsed ysdous"
or something like that. Very frustrating.
I really like Gingercruzt, but I'm unable to use it because of that touchscreen bug. I think it's a bug from CM7.2, since the J.A.F's and jusada's ROM also have this problem.
Sent from my GT-S5830
I got this too http://forum.xda-developers.com/showthread.php?t=1271268
I don't have that bug... did you flash the framework for v2.2 before flashing 2.3? maybe this dosn't afect to the touchscreen but just only to see what was your flashing process.
@CambaStorm I already tried flash the framework when in GingerCrust 2.2 (without framework Gingercrust v2.2 didn't have bootloop) with frameworkgcv2.2.zip , but after flashing the framework, I had the bootloop everytime v after that i flash again with Gingercrust v2.3 and i got the touchscreen problem but the bootloop already solved.
@nims11 thanks for the reply, I want to ask some questions to you. Is there additional framework for Gingercrust 2.3 or the framework for 2.2 still valid in 2.3? I mean if I want to upgrade from 2.2 to 2.3, is it required to flash the framework again? or the GC 2.2 that you post in http://forum.xda-developers.com/showthread.php?t=1324628 already have modified framework inside? Thanks nims!! I really want to try the GC v2.3 by the way it's really a very great work of you!!
@adinq yeah I have the same problem in GingerCrust v2.3 just like your video in your thread
acesteady said:
@CambaStorm I already tried flash the framework when in GingerCrust 2.2 (without framework Gingercrust v2.2 didn't have bootloop) with frameworkgcv2.2.zip , but after flashing the framework, I had the bootloop everytime v after that i flash again with Gingercrust v2.3 and i got the touchscreen problem but the bootloop already solved.
@nims11 thanks for the reply, I want to ask some questions to you. Is there additional framework for Gingercrust 2.3 or the framework for 2.2 still valid in 2.3? I mean if I want to upgrade from 2.2 to 2.3, is it required to flash the framework again? or the GC 2.2 that you post in http://forum.xda-developers.com/showthread.php?t=1324628 already have modified framework inside? Thanks nims!! I really want to try the GC v2.3 by the way it's really a very great work of you!!
@adinq yeah I have the same problem in GingerCrust v2.3 just like your video in your thread
Click to expand...
Click to collapse
moded framework allready gave in rom
touchscreen prob of keypad you tell is not happen atall in my phone
Im reply all things from my phone not from pc means not phasing that stuff yet
will try to solve for those phasing in new version
adeklipse said:
I have this problem also.
It's most apparent when typing, because random keys will frequently touch itself, mostly the s and d keys.
For example, I write "I love you", it will turn out as:
"Ids sdldovsed ysdous"
or something like that. Very frustrating.
I really like Gingercruzt, but I'm unable to use it because of that touchscreen bug. I think it's a bug from CM7.2, since the J.A.F's and jusada's ROM also have this problem.
Sent from my GT-S5830
Click to expand...
Click to collapse
thanks for the quick reply nims, just info for you the bug that I found is just exactly the same as adeklipse said
acesteady said:
Hello everyone I have a problem with touchsreen on GingerCrust v2.3,
Firstly I want to say sorry because this question is supposed to be in development thread but, since I still have a less posts in this forum so I have to post it in this thread.
Okay this is the problem
I already succeed to flash the GingerCrust v2.2 via CWM 5.0.2.6
And I found there's no problem with touchscreen and then I did the GingerCrust v2.3
And i've got the touchscreen problem (the touchscreen strongly not accurate and hard to swipe for changing app drawer and desktop page)
I already tried to do touch screen calibration test via *#*#2664#*#* touch screen test
but the code won't work
and I tried to find additional framework on it's official thread(by nims11) but there's none of it.
Did anybody have a problem like me? Is there already a solution for the problem that I found
Click to expand...
Click to collapse
I have exactly the same problem. The cause of his OC kernel is unfortunately in some lucky so forth. I asked about this before but no one knows the solution. The only way that works is throwing a kernel that is nonOC "cm-7.1-kernel-2.6.35.7-perf-CL562111.zip" from this topic. http://forum.xda-developers.com/showthread.php?t=1296905 and the problem is gone.
icemanhi said:
I have exactly the same problem. The cause of his OC kernel is unfortunately in some lucky so forth. I asked about this before but no one knows the solution. The only way that works is throwing a kernel that is nonOC "cm-7.1-kernel-2.6.35.7-perf-CL562111.zip" from this topic. http://forum.xda-developers.com/showthread.php?t=1296905 and the problem is gone.
Click to expand...
Click to collapse
And "#throwinag##"% fthus akernael wdill make it wsorks,h rigsht?
This is the text that I typed without any correctionss
And "throwing" thus kernel will make it work, right?
Sent from my GT-S5830
Sorry for the dopost.
I think I've figured out why the touchscreen is acting up (thanks to icemanhi, I'll be pressing that thanks button when I get on the computer). It does have something to do with the OC kernel, but not specifically because of it.
I underclocked my device to 700MHz, and the problem dissappeared. I OCed it to just above 800, and would start seeing it again. I OCed all the way up to just under 900, and it was very apparent.
So possible solutions are:
1. Underclock to <800MHz (for max clock)
2. Flash ketut's regular, non-OC kernel (link provided by icemanhi).
Sent from my GT-S5830
adeklipse said:
Sorry for the dopost.
I think I've figured out why the touchscreen is acting up (thanks to icemanhi, I'll be pressing that thanks button when I get on the computer). It does have something to do with the OC kernel, but not specifically because of it.
I underclocked my device to 700MHz, and the problem dissappeared. I OCed it to just above 800, and would start seeing it again. I OCed all the way up to just under 900, and it was very apparent.
So possible solutions are:
1. Underclock to <800MHz (for max clock)
2. Flash ketut's regular, non-OC kernel (link provided by icemanhi).
Sent from my GT-S5830
Click to expand...
Click to collapse
I take the 2nd solution..... underclock????? i think flash non-oc kernel is better than that
matur nuhun.......
acesteady said:
I take the 2nd solution..... underclock????? i think flash non-oc kernel is better than that
matur nuhun.......
Click to expand...
Click to collapse
Yep, I went with flashing the non-oc kernel as well. Underclocking will still leave you with the problem.
Sami-sami.
*ane orang Banjar nyasar ke Bandung, gan.
Sent from my GT-S5830
I use 800 MHz on oc kernel and not facing this problem.. maybe I'll try above 800..
1. Underclock to <800MHz (for max clock) THIS SOLVE PROBLEM
2. Flash ketut's regular, non-OC kernel (link provided by icemanhi). THIS NOT
Can somehow fix this without reducing the MHz to 700?
adinq said:
1. Underclock to <800MHz (for max clock) THIS SOLVE PROBLEM
2. Flash ketut's regular, non-OC kernel (link provided by icemanhi). THIS NOT
Can somehow fix this without reducing the MHz to 700?
Click to expand...
Click to collapse
Yes: reduce to 800MHz. Though I still have some problems with that.
Sent from my GT-S5830
I also have the same Problem.
It was all fine with froyo 2.2, when i switched to stock 2.3.3 kpe or 2.3.4 kph this problem occured. It stopped happening with 2.3.3 kpy and its perfectly fine with the 2.3.5 stock firmwares.
My big problem is, i cant use any custom roms, it happens with every single custom rom.
So it's not really a warranty issue when it happens with custom roms. Coz samsung could say it works fine with stcok firmware, 2.3.3 kpy for example.
I really don't know what the cause of the problem is, because my friends galaxy ace doesnt have these problems with the custom roms i tried.
I'm not sure but besides the kernel i kinda think it might be a battery issue, because it happens less frequently when its plugged to the charger.
adeklipse said:
Yes: reduce to 800MHz. Though I still have some problems with that.
Sent from my GT-S5830
Click to expand...
Click to collapse
may be this mod can help you..
http://forum.xda-developers.com/showthread.php?t=1365434
i OCed to 883MHz without problem on touchscreen
matur nuwun
aku wong solo bro...╋╋ム ╋╋ム ╋╋ム =)) ╋╋ム ╋╋ム ╋╋ム
pls press thanks button if you like this.
sorry for my bad english
I installed galaxy task v14 from galaxytabhacks.com and the kernel that was a seperate dowload but was supposed to be for it. It all works very well but the autorotation isnt working and it is driving me insane.
Anyone else have this issue, and if so any idea how to fix?
Don't mean to cause offence but have u checked to make sure its enabled? I knocked it off by accident once lol
Sent from my GT-N7000 using xda premium
neonymbus said:
I installed galaxy task v14 from galaxytabhacks.com and the kernel that was a seperate dowload but was supposed to be for it. It all works very well but the autorotation isnt working and it is driving me insane.
Anyone else have this issue, and if so any idea how to fix?
Click to expand...
Click to collapse
If I'm not mistaken. The v.14 from task is installed with the normal kernel from samsung. The kernel that you install separately is a custom one. Does it work with the normal kernel?
I had the same issue after upgrading to stock 3.2. I tried messing around with the calibration settings, and it worked. Maybe it'll work for you too! Goods luck!
Sent from my GT-P7500 using Tapatalk
The problem is because the kernel listed in galaxytabhacks.com is for HC 3.1 and "Galaxy Task 14" is a HC 3.2 ROM.
The right kernel can be found in pershoot's blog:http://droidbasement.com/db-blog/
Direct link to kernel: 10.1-Wifi, Touchwiz UX (OTA, GT-P7510)
BTW, I suggest you to check the official "Galaxy Task 14" thread: http://forum.xda-developers.com/showthread.php?t=1340064
Maple you are my hero, wiped cache, dalvik cache, and reflashed new kernel now it works like a dream. big thanks bro
I'll go straight to the problem:
There are 2 rows of pixels, (one below another) that are too sesitive on all ROMs except: CM7.2 by vo-1 WITH zImage kernel and XWKPT WITHOUT cf-root (I'm stuck with these 2, because on any other the thing happens). They very frequently react to touches all over the screen and even touch-buttons.
Why is that happening? Does anyone have a problem like that too? How can I fix it?
Sonic0509 said:
I'll go straight to the problem:
There are 2 rows of pixels, (one below another) that are too sesitive on all ROMs except: CM7.2 by vo-1 WITH zImage kernel and XWKPT WITHOUT cf-root (I'm stuck with these 2, because on any other the thing happens). They very frequently react to touches all over the screen and even touch-buttons.
Why is that happening? Does anyone have a problem like that too? How can I fix it?
Click to expand...
Click to collapse
Yes, that is kernel problem. even i had that problem in ketut's blackhawk and other OC kernel. i flashed ketut's non-oc kernel then the problem was solved. u can try flashing zImage v1.5 or ketut's 7.1 kernel(lenovo). i hope this helps
But would zImage or keut's 7.1 work on stock based ROM?
Sent from my GT-S5830 using XDA
Sonic0509 said:
But would zImage or keut's 7.1 work on stock based ROM?
Sent from my GT-S5830 using XDA
Click to expand...
Click to collapse
Unfortunately no. But I prefer stock kernel when I'm on stock, it's smoother for me (I dont use init.d)
Sent from my GT-S5830 using Tapatalk
Sonic0509 said:
I'll go straight to the problem:
There are 2 rows of pixels, (one below another) that are too sesitive on all ROMs except: CM7.2 by vo-1 WITH zImage kernel and XWKPT WITHOUT cf-root (I'm stuck with these 2, because on any other the thing happens). They very frequently react to touches all over the screen and even touch-buttons.
Why is that happening? Does anyone have a problem like that too? How can I fix it?
Click to expand...
Click to collapse
i am facing the same problem...i too use zImage 1.5 ..it seems to be a bit hardware issue as well...bcz there are very few users facing this type of problem..till now i came across only three of them.
but thnx for mentioning this..
i musing ddkq6 and have same problem..
have the same issue. but reverted back to CF-ROOT B82-EX kernel and no more problems on any ROM. but sometimes(very rarely) i experience less responsive screen.
amrith.28 said:
have the same issue. but reverted back to CF-ROOT B82-EX kernel and no more problems on any ROM. but sometimes(very rarely) i experience less responsive screen.
Click to expand...
Click to collapse
Less responsive screen wouldn't be bad for me and cf-root b82 sounds promising. Thanks for a hint
Sonic0509 said:
I'll go straight to the problem:
There are 2 rows of pixels, (one below another) that are too sesitive on all ROMs except: CM7.2 by vo-1 WITH zImage kernel and XWKPT WITHOUT cf-root (I'm stuck with these 2, because on any other the thing happens). They very frequently react to touches all over the screen and even touch-buttons.
Why is that happening? Does anyone have a problem like that too? How can I fix it?
Click to expand...
Click to collapse
I got the same problem
Same problem for me. I think it's a combination of hardware issue and kernel problem as it's not present on every kernel...
Did all of you bought the Ace at the very begininng when it went out?
I did, and i think that maybe Samsung solved the problem in the older relase of ace...
Sent from my GT-S5830 using xda premium
Yeh im having that problem too on oc kernels...
Darvadouille said:
Same problem for me. I think it's a combination of hardware issue and kernel problem as it's not present on every kernel...
Did all of you bought the Ace at the very begininng when it went out?
I did, and i think that maybe Samsung solved the problem in the older relase of ace...
Sent from my GT-S5830 using xda premium
Click to expand...
Click to collapse
Yep. Just when it came out in Poland.
If there is only small group of us, complaining about it, there is high chance that Samsung really fixed touch sensors in later releases.
Hello,
Aint sure if other roms did it but now using RR rom some times few times a day i notice that i touch specific thing on screen even keyboard and it wont register my touch, I need touch again to register it...
Ideas?
Galaxy s2 with Samsung CPU, EU Version
Thanks!
rommark said:
Hello,
Aint sure if other roms did it but now using RR rom some times few times a day i notice that i touch specific thing on screen even keyboard and it wont register my touch, I need touch again to register it...
Ideas?
Galaxy s2 with Samsung CPU, EU Version
Thanks!
Click to expand...
Click to collapse
Tried changing kernels? Each kernel usually has modified touch parameters.
Nasty_z said:
Tried changing kernels? Each kernel usually has modified touch parameters.
Click to expand...
Click to collapse
Which one you suggest in following terms:
- Support android 4.1.1.1 RR Rom
- Keyword lagg in emails (got it now actually)
- Snappy (100% smoothness in UI/Apps explorer APEX)
- Touch accuracy without loosing touch / reg touch issues
- Rom that I can install via CWM and not ODIN
Please suggest mate,
Thanks!
rommark said:
Which one you suggest in following terms:
- Support android 4.1.1.1 RR Rom
- Keyword lagg in emails (got it now actually)
- Snappy (100% smoothness in UI/Apps explorer APEX)
- 3D performance
- Touch accuracy without loosing touch / reg touch issues
- Rom that I can install via CWM and not ODIN
Please suggest mate,
Thanks!
Click to expand...
Click to collapse
1. Dream Kernel,Siyah are currently support JB.
2. No way till HW acc works u cant expect 100% smoothness,
3. It already has 3D performance
4. I never faced such touch issue.. Try Siyah u might get better.
5. ROM?? U already on RR rite?? U meant kernel flashable thru CWM??
Prashanthme said:
1. Dream Kernel,Siyah are currently support JB.
2. No way till HW acc works u cant expect 100% smoothness,
3. It already has 3D performance
4. I never faced such touch issue.. Try Siyah u might get better.
5. ROM?? U already on RR rite?? U meant kernel flashable thru CWM??
Click to expand...
Click to collapse
1) DreamKernel via CWM? I have only Odin version here... any link for CWM version?
2) There is no H/w ACC on 4.1.1, i thought it was added in JB?
3) Correct
4) Got CWM version of Siyah Kernel?
5) Meant KERNEL
Tnx!
rommark said:
1) DreamKernel via CWM? I have only Odin version here... any link for CWM version?
2) There is no H/w ACC on 4.1.1, i thought it was added in JB?
3) Correct
4) Got CWM version of Siyah Kernel?
5) Meant KERNEL
Tnx!
Click to expand...
Click to collapse
1.http://forum.xda-developers.com/showthread.php?t=1788021&highlight=dream+irc It has CWM version.
2.:FACEPALM: Dude U using RR v2.6.1 or RR v3.0.1?? 2.6.1 is ICS AOKP, 3.0.1 is Jelly Bean... 2.6.1 has HW acc... 3.0.1 doesnt have!!!
3. Done.
4. http://forum.xda-developers.com/showthread.php?t=1555259
5. Yes links r above
Prashanthme said:
1.http://forum.xda-developers.com/showthread.php?t=1788021&highlight=dream+irc It has CWM version.
2.:FACEPALM: Dude U using RR v2.6.1 or RR v3.0.1?? 2.6.1 is ICS AOKP, 3.0.1 is Jelly Bean... 2.6.1 has HW acc... 3.0.1 doesnt have!!!
3. Done.
4. http://forum.xda-developers.com/showthread.php?t=1555259
5. Yes links r above
Click to expand...
Click to collapse
1) Installed the dream kernel via CWM, Lets see if I feel none registered touches again in the next few days.
2) (Stupid/Funny Question) Those phones by the way built for situations when some one mistakenly can sit down on his phone? it happened to me today while it was laying on my bed (soft bed mattress).
rommark said:
1) Installed the dream kernel via CWM, Lets see if I feel none registered touches again in the next few days.
2) (Stupid/Funny Question) Those phones by the way built for situations when some one mistakenly can sit down on his phone? it happened to me today while it was laying on my bed (soft bed mattress).
Click to expand...
Click to collapse
2- LOL i thought u misunderstood what s HW acc..
2.:FACEPALM: Dude U using RR v2.6.1 or RR v3.0.1?? 2.6.1 is ICS AOKP, 3.0.1 is Jelly Bean... 2.6.1 has HW acc... 3.0.1 doesnt have!!!
I\ve the JB RR so does it have HW ACC?
Tnx!
No. hwcomposer is buggy so it's disabled at the moment.
Hi guys! i just have rooted my galaxy s2, kernel siyah, and i have a problem with my home button it doesnt respond and if click on it 4 times i think the screen becomes neutral. help me please!!!!
0xx_Linux_ said:
Hi guys! i just have rooted my galaxy s2, kernel siyah, and i have a problem with my home button it doesnt respond and if click on it 4 times i think the screen becomes neutral. help me please!!!!
Click to expand...
Click to collapse
Did u flash a rom/kernel?
If yes try to flash it again.
If it not works, do it again.
If u didn't change anything u can try a factory reset (backup first!),
but it also can mean that ur device has a hardware defect.
Much success
CHEERS
It musn't be hardware problem, because the 4x home button feature is a natural feature on Siyah kernel. I used official AOKP, and the home button didn't responded too, so maybe it will be the problem, but I don't know how to solve the AOKP problem Maybe they will release a patch.
Re: Problem with home button </noob>
Did you run dorimanx before that?
Sent from my gt-9100 powered by dorimanx
You can thank me if i helped you
Re: Problem with home button </noob>
EverByte said:
It musn't be hardware problem, because the 4x home button feature is a natural feature on Siyah kernel. I used official AOKP, and the home button didn't responded too, so maybe it will be the problem, but I don't know how to solve the AOKP problem Maybe they will release a patch.
Click to expand...
Click to collapse
That's why I ask the question I asked, first
CHEERS
Sent from my GT-I9100 with RootBox
Re: Problem with home button </noob>
Ockay first of all, i m running on stock rom, and i'm gonna flash dorimanx soon to see.