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
Related
hello every body....
this is first time to me in this forum and i'm new on android world
please i need your help
i have an official update 2.1 update1 at my mobile and i dont need any rom coz i tried many roms there is all have a bug i prefer to be at this firmware.
but the point that i need to have multi touch i cant play angrybird and what about overclock can i get it how ?!?!
please i need help with links and files
I feel so sad when i read things like this.........
freedompals said:
hello every body....
this is first time to me in this forum and i'm new on android world
please i need your help
i have an official update 2.1 update1 at my mobile and i dont need any rom coz i tried many roms there is all have a bug i prefer to be at this firmware.
but the point that i need to have multi touch i cant play angrybird and what about overclock can i get it how ?!?!
please i need help with links and files
Click to expand...
Click to collapse
Next time use search functions on forums before posting like these.
There are threads regarding multitouch development. As of now we don't have this feature yet.
When playing angry birds, I don't use two fingers to play. I can play with single touch with no problems though lol.
Overclocking, use ROMs developed neither by owain94, slade 87, D4rKn3sSyS. Not all custom ROMs have major bugs. The said developers created custom ROMs we can use daily.
or once again use the search function to search on how you can overclock your phone without installing custom ROMs.
Lastly, don't forget those people who created ROMs that you will be using
fictionworld said:
Next time use search functions on forums before posting like these.
There are threads regarding multitouch development. As of now we don't have this feature yet.
When playing angry birds, I don't use two fingers to play. I can play with single touch with no problems though lol.
Overclocking, use ROMs developed neither by owain94, slade 87, D4rKn3sSyS. Not all custom ROMs have major bugs. The said developers created custom ROMs we can use daily.
or once again use the search function to search on how you can overclock your phone without installing custom ROMs.
Lastly, don't forget those people who created ROMs that you will be using
Click to expand...
Click to collapse
sorry sir I did not mean to offend Programmer....i respect him
but really i tried a lot of rom's through i follow the instruction but i faced a lot of bugs and so many restart issue
about the post i wrote it coz there is many subject and you will lost in forum
sorry again
freedompals said:
sorry sir I did not mean to offend Programmer....i respect him
but really i tried a lot of rom's through i follow the instruction but i faced a lot of bugs and so many restart issue
about the post i wrote it coz there is many subject and you will lost in forum
sorry again
Click to expand...
Click to collapse
I'm just telling no need to say sorry lol. I'm just a regular user of their custom ROM too lol. XD
Hmm. Before we customize our ROM we need to know first what's the requirements. What ROMS did you use? And what are your kernel version, android version and build number? You said you're on stock ROMs at the moment right? please do correct me if I'm wrong. xD
ok man thats clear
i followed the instruction every once i install rom i tried
MiniCM6-1.0.0
xCyanogenMini 7
and others i didnt remeber
but alway have so many reboots
i have now
2.1 update 1
m76xx-tsncjolym-53404015
2.1.1.a.0.6
hmm call me noob but uhh, your phone's a mini pro?
MiniCM6-1.0.0
I think the problem is that you are using ROMs which is only made for xperia mini. That's why you're getting a lot of bugs.
Please do correct me if I'm wrong.
Currently I use slades87 work, and its xCyanogen6 for mini pro. It works perfectly for me. Why won't you try that? The infos you gave me suited it actually.
no sir my phone is x10 mini not pro
what's are the exact problems that you are experiencing?
did you do a factory reset before installing the rom?
-factory reset
-wipe stats wipe dalvik-cache
-wipe cache
then try installing custom rom.
do you still have xrecovery installed?
open the zip file of your rom you want to flash with winrar
browse to /system/lib/modules/
highlight x8oc.ko and hit delete
copy zip to your sd again
reflash
be happy
Why need to do this??
Can I do in running room?
slade87 said:
open the zip file of your rom you want to flash with winrar
browse to /system/lib/modules/
highlight x8oc.ko and hit delete
copy zip to your sd again
reflash
be happy
Click to expand...
Click to collapse
axpira said:
Why need to do this??
Can I do in running room?
Click to expand...
Click to collapse
This is only if you have reboots, cuz if you have still reboots on froyo rom, you SHOULD delete overclock module !
x8oc.ko - this module can overclocks Your phone. Overclocking means that it's CPU runs faster than it is for. It is working for someones and do not work for others (!). Could bring dangerous unstableness, reboots.
Wise advice to delete it, but I can't understand why overclock a modROM by default? (if this is the case)
.x.x.x.Peria said:
x8oc.ko - this module can overclocks Your phone. Overclocking means that it's CPU runs faster than it is for. It is working for someones and do not work for others (!). Could bring dangerous unstableness, reboots.
Wise advice to delete it, but I can't understand why overclock a modROM by default? (if this is the case)
Click to expand...
Click to collapse
i've installed a few roms for my mini pro, they came with the max clock at 600mhz, only the overclocked version of slade87 MiniCM came with the max clock at 710 mhz. i don't know any rom for mini (not pro), but i think it should be similar
I'm using Franco's Kernel v15 + ZRAM with Mik's CM7 6.5.2. At first it was a dream, 1352 points on quadrant and 58.5fps on neocore @480/729Mhz Smartass. Everything running smooth and really fast.
About 6 hours of intense testing some apps (many, in fact) started crashing for no reason. Mostly google apps like Calendar and even Market. But also some widgets and running services.
I reflashed everything, even re-formatted (and re-partitioned) my sdcard and everything was fine again but after a reboot to install google applications (gapps-gb-20110325-signed.zip) the crashes started again. And I was running w/o overclocking at this time.
Searching for some info on the issue I saw a post stating that v15 kernel is for FROYO only so it's not compatible with CM7 but Franco always said that his Kernel was compatible with CM7 and there's no such info coming from Franco himself so I want to be sure of it before flashing a Froyo ROM.
Any thoughts on this issue? Any help is appreciated.
Edit:
Maybe it's worth noting that my phone is a O1 p500h, apart from the 3.2mp camera I don't really know if there's other differences in hardware that may cause problems.
That h is ur problem I think
I really hope not. I've been using Franco Kernel + CM7 for many versions and never had any problems with it (well, aside CM7's known bugs).
I'm from Brazil and CM7 is the only ROM I know that has Brazilian Portuguese (pt-BR) language support. All other ROMs I tried are strictly european and only have support for Portugal's Portuguese (pt-PT), which is kinda different and "sounds" quite annoying at some times.
And while I feel quite confortable using english, it's not the same thing as your mother tongue.
Its weird some users reported this kind of stuff.
I think its safer to use dookmatt kernel than franco kernel
Could a theme cause this kind of instability? I just remembered that on both times the crashes started I was experimenting with a XperiaArc theme for CM7.
Are you using app2sd or data2sd? These may cause such conflicts at time.
Vip_blast said:
Are you using app2sd or data2sd? These may cause such conflicts at time.
Click to expand...
Click to collapse
Nope, but I have an Ext4 partition on my SD-Card so I get more "internal" memory for installing apps.
You need to use some external app/hack for what you have described, so, essentially the answer is yes, not no
Sent from my LG-P500 using XDA App
doktornotor said:
You need to use some external app/hack for what you have described, so, essentially the answer is yes, not no
Sent from my LG-P500 using XDA App
Click to expand...
Click to collapse
The answer remains "no", I'm not using app2sd nor data2sd.
You missed the point. Whatever are you using for this can cause the instability. Apparently top secret stuff, so... go help yourself I guess.
Sent from my LG-P500 using XDA App
I am facing certain problems like you after flashing devoid.franco+kernel V15+ ZRAM.
I had following issues for the past 15 days.
1. changed the stock ROM to devoid Franco + V14
I agree the performance of the phone increased. Did OC using Set CPU. Score over the Quadrant was never over 650, not an issue with this as long as i can feel the diff in the performance.
One major change i saw was - as you all know the SMSes get threaded with a particular contact (both recd and sent msgs.). In my case if i receive sms from TD-I-mint, the message was shown as received from TD-Reylon, similar with all the SMSes, the actual sender was never possible to know when you see the list of msgs. Only after you open the msgs then you could find out the sender.
this is continuing still with Kernel 15.
2. same situation after flashing V14.1, V14.2, V14.2.2.
3. with Kernel V 15 + devoid.francoROM with little change. I wiped everything, SD was partitioned and upgraded to EXT 4. Flashed new ROM (05-06-2011), rebooted, flashed Kernel V15, rebooted, flashed ZRAM, rebooted, but phone never came to life, had to remove the battery and reboot, same result. Then wiped cache and dev cache, then flashed ZRAM, the phone was breathing.
Then tried to flash the system apps downloaded from first post of http://forum.xda-developers.com/showthread.php?t=1049518&page=1, the phone lost its life and had to re-do the whole process of flashing ROM....
With update of ROM + Kernel V15, i had to re-do the whole process for 5-6 times. I never had this problem with older kernels or flashing custom ROM.
One major issue is - msgs and other apps like TB (list of backups) some times display vertically. Today for the first time the SMS app was force closed.
Any-body facing issues like this or issues and you have the solution , I request you to post here.
I guess the best solution for me is to use the stock ROM with franco.kernel. This way I maintain my country's language (and, most important, GPS configuration) and still get some nice tweaks from Franco's.
By reading the comments on v15 kernel, it seems wise to wait for a new version before installing it. There are several users experiencing heavy battery drain. Or maybe install v14.2, but I don't have it anymore.
So, is it safe to use franco.kernel v14-v15 with LG stock ROM (mine came with v10A, android 2.2.1)? Or does it have any compatibility issues?
Thanks for your replies.
touch fix
hi, Does this kernel has the touch fix like Mik_os' kernel?
cas0404 said:
hi, Does this kernel has the touch fix like Mik_os' kernel?
Click to expand...
Click to collapse
Yes it does. Am running stock 2.2.2 with Franco's kernel v15 and its smooth as butter.
Running 2.2.1 stock ROM + franco.kernel v15 for about 10 hours now, so far no significant change on battery use.
But I miss mik's ROM performance... FPS on neocore dropped from 57fps to 36.5fps. And my old score on quadrant was 1350 and now is 615.
Is there any improvements I can install on my stock ROM? JIT? HW accel? I really could use some more performance.
drakull said:
Is there any improvements I can install on my stock ROM? JIT? HW accel? I really could use some more performance.
Click to expand...
Click to collapse
Wait for 2.3 to be released.
Hello everybody, after the installation of the ROM tw008 and custom kernel 3.60 photos does not register and video does not work , somebody would have a solution?
I test all the goro's kernel and its always the same problem . Please help me!!
vinss68 said:
I test all the goro's kernel and its always the same problem . Please help me!!
Click to expand...
Click to collapse
I really want to help but unfortunately i don't know what to help you on:
But:
1: Did you install the ROM/kernel properly?
2: Did you try re-installing?
3: Did you try flashing stock firmware than Wolfbreak's ROM.
4. Did it work on stock kernel?
5. DID YOU MAKE SURE YOU DOWNLOADED THE RIGHT 3.60 KERNEL BECAUSE GORO PUT THE WRONG LINK? (oops caps)
Download the goro kernel again and flash it HERE
Hope this helps
Hello thank you for your reponse, indeed I tried some thing, and with the good kernel .
I have try:
- to make a fresh instalation of bb.67 and of the ROM tw008, then of the custom kernel 360 (by trying all the camera resolution, and play on frequence cpu, anything has to make its not working). I have not try to make a fresh installation of firmware via SEUS (I try it now!!)
-Camera is completely functional with the stock kernel , with z's custom kernel (22,23,05) and with custom kernel 3.47 when i was on tw7 bb52, but I prefere the ck 360 for the underclock and bb.67
- with and without the theme which I use
And camera make always her tantrums
Well I try the fraiche installation firmware and I informed
Works fine for me and everyone else using it...
Must be something you're doing
Just for information if it can help to resolve the problem, when I takes a photo the image gallery makes an black screen and when I want to pass in video mode the application makes a sudden closure
always similar after a full fresh installation of all.... i don't know what's the problem. i think i will wait a future kernel with underclocking and stay with z's kernel for the moment ,but if anyone got a idea or question about situation ...
vinss68 said:
always similar after a full fresh installation of all.... i don't know what's the problem. i think i will wait a future kernel with underclocking and stay with z's kernel for the moment ,but if anyone got a idea or question about situation ...
Click to expand...
Click to collapse
you might be flashing the wrong version of the kernel for your rom....
it's strange because all working fine, just this problem with camera . i trying to reorganize my sd card she's in a mess... maybe it's the cause of my problem.
some opinion?
I don't think its related to the rom or custom kernel. I've had this problem on some of the custom roms I've tried. What ultimately fixed it for me is by formatting the sd card so make a backup of your entire sd card then format it.
Sent from my X10x using XDA App
Good news,
my problem is resolved. Yesterday evening I completely cleaned my card sd then I left the telephone have it reconfiguré. I remake fresh installation rom tw008 and of the custom kernel 360 and hop all work fine. I think that the problem came because I tested several applications camera,background which created several files for photos,images, because which never clean .i am finally going to be able to take advantage of quite its hey hey.
Thx all to be interested in you has my case and sorry for my bad english
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!
I've recently installed the fxp cm9 ICS firmware port and kernel on my X10. Now, it turns out several games have a bit of a problem with touchscreen commands. For example, after having installed the mobile Rayman game, the buttons on the main menu seem to respond to my touch at first, but don't actually do anything.
Having looked around for this problem, I ultimately found this quote:
"that problem is with your Kernel. There's a problem with the ICS Kernel 4.1.B.0.431 using touch games. You have to upgrade to a Kernel based on 4.1.B.0.587 or a CyanogenMod Kernel."
I'm not that knowledged in the field of android development, but I'm under the impression that the kernel I installed along with the CM9 x10 port is obviously a CM kernel. All kernels currently available on the X10 dev forums here seem to be based on the fxp cm9 kernel port as well. Thus, my question is: has anyone else encountered this problem, is the problem really relevant to the kernel as stated in that quote, and is there anything specific I need to know or do to fix this problem?
Thanks in advance for your help!
Draycken said:
Hello!
I've recently installed the fxp cm9 ICS firmware port and kernel on my X10. Now, it turns out several games have a bit of a problem with touchscreen commands. For example, after having installed the mobile Rayman game, the buttons on the main menu seem to respond to my touch at first, but don't actually do anything.
Having looked around for this problem, I ultimately found this quote:
"that problem is with your Kernel. There's a problem with the ICS Kernel 4.1.B.0.431 using touch games. You have to upgrade to a Kernel based on 4.1.B.0.587 or a CyanogenMod Kernel."
I'm not that knowledged in the field of android development, but I'm under the impression that the kernel I installed along with the CM9 x10 port is obviously a CM kernel. All kernels currently available on the X10 dev forums here seem to be based on the fxp cm9 kernel port as well. Thus, my question is: has anyone else encountered this problem, is the problem really relevant to the kernel as stated in that quote, and is there anything specific I need to know or do to fix this problem?
Thanks in advance for your help!
Click to expand...
Click to collapse
Same rom with version 5.1 kernel with same problem. The games seem to work when you first load them but doesn't last long until it stops recognizing the touch screen.
dgoby said:
Same rom with version 5.1 kernel with same problem. The games seem to work when you first load them but doesn't last long until it stops recognizing the touch screen.
Click to expand...
Click to collapse
So what you mean, the game doesn't responding anymore even when u touch menu it didnt exit so have to force restart?
Sent from my GT-I8150 using xda app-developers app
Oyongx said:
So what you mean, the game doesn't responding anymore even when u touch menu it didnt exit so have to force restart?
Sent from my GT-I8150 using xda app-developers app
Click to expand...
Click to collapse
It it's the same problem I have, here's an example: you get into angry birds, select your level, fire about once or twice with slingshot and then no response from the screen. Back, menu and home buttons work but not the screen.
Yeah, I hadn't tried angry birds yet after having installed the new firmware, but I just gave one of the games a testrun and I can't even get in-game, main menu is completely unresponsive.
But no, there's no freezing or anything, I can just leave the game with my hard buttons, it's only the touchscreen in-game that's being unresponsive.
Not all games either since there's plenty of stuff that still works though.
dgoby said:
It it's the same problem I have, here's an example: you get into angry birds, select your level, fire about once or twice with slingshot and then no response from the screen. Back, menu and home buttons work but not the screen.
Click to expand...
Click to collapse
I see.. that must be kernel problem. Im using cm9 galaxy w but no such issue.. have u tried other kernel?
Sent from my GT-I8150 using xda app-developers app
I'm not sure but I thought the other kernels for ICS for X10 were all based on the FXP CM9 port... Please correct me if I'm mistaken.
Hey, a very noob question, but does flashing just another kernel, and not flashing a whole new firmware, also result in all your data being lost? If not, I could just try a few different kernels out without having to take a new backup.
Draycken said:
I'm not sure but I thought the other kernels for ICS for X10 were all based on the FXP CM9 port... Please correct me if I'm mistaken.
Hey, a very noob question, but does flashing just another kernel, and not flashing a whole new firmware, also result in all your data being lost? If not, I could just try a few different kernels out without having to take a new backup.
Click to expand...
Click to collapse
Nope. But for just in case, do a full backup using cwm recovery. A backup is a must when you do such thing.. As long as you read ics kernel for your x10 not other device maybe everything will be okay. Get what i mean? (Bad english )
Sent from my GT-I8150 using xda app-developers app
Oyongx said:
I see.. that must be kernel problem. Im using cm9 galaxy w but no such issue.. have u tried other kernel?
Sent from my GT-I8150 using xda app-developers app
Click to expand...
Click to collapse
Not yet but I was looking to try Amin for CM9, unless you have another suggestion for Fera V4 ICS.
Edit: Amin Kernel didn't even allow the phone to boot, next
Draycken said:
I'm not sure but I thought the other kernels for ICS for X10 were all based on the FXP CM9 port... Please correct me if I'm mistaken.
Hey, a very noob question, but does flashing just another kernel, and not flashing a whole new firmware, also result in all your data being lost? If not, I could just try a few different kernels out without having to take a new backup.
Click to expand...
Click to collapse
The kernel has ntn to do with ur apps n data. It is the basic link between ur hardware and ur os. It has the libraries and drivers etc. So ur data won't be lost
Sent from my Xperia X10 using xda app-developers app
---------- Post added at 11:11 AM ---------- Previous post was at 11:08 AM ----------
dgoby said:
Not yet but I was looking to try Amin for CM9, unless you have another suggestion for Fera V4 ICS.
Edit: Amin Kernel didn't even allow the phone to boot, next
Click to expand...
Click to collapse
I'm using feralab v4 ROM with kernel v5.1.. I don't hv ne such issues. I didn't hv these issues on ne cm based kernel for that matter.
Sent from my Xperia X10 using xda app-developers app