Touch screen issue - Galaxy Ace S5830 Q&A, Help & Troubleshooting

Hi,
There are few users(including myself) who have continuously been facing the problem of buggy touchscreen across various ROM's.
issue: Buggy touchscreen, mistype, multitouch
Note: This problem is specific to very few users and specially on OC kernel.
I would like to request all those who are facing this kind of problem to discuss it and arrive at the feasible solution.
TIA.

julieace said:
Hi,
There are few users(including myself) who have continuously been facing the problem of buggy touchscreen across various ROM's.
issue: Buggy touchscreen, mistype, multitouch
Note: This problem is specific to very few users and specially on OC kernel.
I would like to request all those who are facing this kind of problem to discuss it and arrive at the feasible solution.
TIA.
Click to expand...
Click to collapse
Use the General section please.

wrong section
and what the hell are u talking about?

julieace said:
Hi,
There are few users(including myself) who have continuously been facing the problem of buggy touchscreen across various ROM's.
issue: Buggy touchscreen, mistype, multitouch
Note: This problem is specific to very few users and specially on OC kernel.
I would like to request all those who are facing this kind of problem to discuss it and arrive at the feasible solution.
TIA.
Click to expand...
Click to collapse
i hv a sweaty hands , when my hands is sweating , the sweat left on the screen so there's one touch , so when my finger touch another place , there's another touch
so i always have problem in gaming when i'm sweating
if ur hands are like mine, it's not the screen problem but ur hands

i have the same problem. and it is not the fault of sweaty hand... believe me.

wrong section mate.
use non-OC kernel.

Yes. I have this problem! All roms using Ketut's kernel have this problem for me!! I do not over-clock above 800 Mhz and still have this problem!!
This makes typing, panning and pinch to zoom impossible. So, I always revert to stock rom or a rom which does not use Ketut's kernel.
I then experimented with the stock rom by flashing Cf-root kernel by ketut over DDKQ8. Then, the touch became buggy and there were wrong touches. I have discussed about this problem with many people and they say everything is fine and it is my fault. But this is the problem with ketut's kernel and I am damn sure as I have faced this issue in all roms using that kernel(CM7 by FAT, SGSII themed rom, and even stock rom after kernel patch is applied!)
This is a serious issue!!
BTW, please use the general thread for such posts!!

imbawind said:
i hv a sweaty hands , when my hands is sweating , the sweat left on the screen so there's one touch , so when my finger touch another place , there's another touch
so i always have problem in gaming when i'm sweating
if ur hands are like mine, it's not the screen problem but ur hands
Click to expand...
Click to collapse
I apologizes for wrong section..
and if u can't help just shut up..no need to mock.

I also have random touch when I overclock my phone but below 800 its fine
Be Kind everyone you meet is fighting a hard battle

It's mostly Kernel related.
For stock roms, try CF-ROOT B82-ex. I dont face any touch issue on this kernel (but on B83 and B84 i have problem)
For CyanogenMod roms, try Zimage Mod Kernel, or Skynet's kernel..

amrith.28 said:
It's mostly Kernel related.
For stock roms, try CF-ROOT B82-ex. I dont face any touch issue on this kernel (but on B83 and B84 i have problem)
For CyanogenMod roms, try Zimage Mod Kernel, or Skynet's kernel..
Click to expand...
Click to collapse
Its completely kernel related!
Sent from my GT-S5830 using Tapatalk 2

thnx every one for discussing it as it was specific to very users.
There is one thing that its not just OC issue bcz usually its all fine on CM9 by Maclaw.
And yep also on official CM 7.2 there is no touchscreen issue.
i am currently using Miracle V4 + Zimage Kernel...and it working smoothly without any problem.

I also face this problem since the very beginning.
I agree, this is a kernel problem, mayne mixed with hardware specification (as only few users face this issue).
So people, this is not because you do not face this problem that you have to laugh about it.
Better to try to find a solution...
My last try was the last official Cm by Coolia. Still face the problem, but very less. Zimage was also a great solution.
Skynet kernel is also good (no random touch), but i found an issue with the compass on that kernel.
I really think this is Kernel related. And please note that:
- Random touch always occurs on the lower left corner of the screen...
- The problem is heavy on Oc kernel (I mean it's even impossible to type your pin code correctly when you start your device!)
- But it also happens with non oc kernel...
- Last thing: if you underclock the cpu around 600mhz, the problem dossapear. So maybe it's related to high frequency only...
Maybe it's cpu and kernel related then... As I guess there is different version of the phone.
Hope we find a great kernel solving this problems....
Sent from my GT-S5830 using xda premium

Well guys using all ROM's based on ketut's b83/b84 and never had any touch screen issues. Can the baseband affect it in anyway?

Don't know, but i tried different baseband from different country and the problem still the same...
The problem is really related to custom roms, or customs kernel at least, as there is no such problem with stock rom.
Sent from my GT-S5830 using xda premium

hmmm well as so many users are saying, surely it's due to kernel. But i think this issue never arose for users like me though it's a major issue as buggy touch screen may lead to wrong phone operation and i guess one will like to install a ROM with that problem. I hope the devs will find any solution.

So devs, any solution?
Sent from my GT-S5830 using Tapatalk 2

so you guys are aware that this is the wrong section but continue to discuss here? Moderator please move and/or lock thread.
And yes it is kernel related

Darvadouille said:
I also face this problem since the very beginning.
I agree, this is a kernel problem, mayne mixed with hardware specification (as only few users face this issue).
So people, this is not because you do not face this problem that you have to laugh about it.
Better to try to find a solution...
My last try was the last official Cm by Coolia. Still face the problem, but very less. Zimage was also a great solution.
Skynet kernel is also good (no random touch), but i found an issue with the compass on that kernel.
I really think this is Kernel related. And please note that:
- Random touch always occurs on the lower left corner of the screen...
- The problem is heavy on Oc kernel (I mean it's even impossible to type your pin code correctly when you start your device!)
- But it also happens with non oc kernel...
- Last thing: if you underclock the cpu around 600mhz, the problem dossapear. So maybe it's related to high frequency only...
Maybe it's cpu and kernel related then... As I guess there is different version of the phone.
Hope we find a great kernel solving this problems....
Sent from my GT-S5830 using xda premium
Click to expand...
Click to collapse
Thnxx bro...skynet's kernel really solved it...
Sent from my GT-S5830 using xda premium

Related

Anyone Successful w/ROM-> Long Term, ie not constantly reloading?

I find that no matter what ROM I use, I have something that is a problem.
The most success I have had is with Serindipity. But, with that, and other 2.2.1 I9000 ROMs I have tried, after 2-3 weeks, I have the auto rotate fail. Nothing will fix it other than a flash back to stock 2.1, and then reflash of the 2.2.1 ROM. Not even a factory reset on the 2.2.1 ROM will work.
So, now I am trying UCKB1 ROM (stock 2.2 Froyo for Captivate), specifically Cognition. This one is pretty successful, except...modems are few, and I have constant problems with WiFi enabling with Tasker.
Those are the two issues that seem to haunt my phone.
What is your experience? Of course, if you don't use Tasker, maybe the WiFi issue won't be a problem for you.
I suppose the auto rotate could be a sensor trying to go out on my phone...but, EVERY time I do the reinstall of 2.1 it fixes it. So I have cannot replace the phone, and given that it always starts working, I'm not convinced it is a hardware issue.
And for those on 2.2.1, what I've seen generally is that most people putting these ROMS on are flashing addicts (I'm not saying that is a bad thing ), but I prefer to use the phone and not constantly flash. Too much other config to set up after flashing.
Oh, by the way, one fault I have is way too many apps installed. I delete some and then next thing you know I've installed others. Pretty much requires that I use an OC kernel, and I like to use UV for battery performance. Interestingly, I have been quite successful at 1400, and 1.5%/hour drain at idle, with WiFi, GPS, and BT on.
ewingr said:
I find that no matter what ROM I use, I have something that is a problem.
The most success I have had is with Serindipity. But, with that, and other 2.2.1 I9000 ROMs I have tried, after 2-3 weeks, I have the auto rotate fail. Nothing will fix it other than a flash back to stock 2.1, and then reflash of the 2.2.1 ROM. Not even a factory reset on the 2.2.1 ROM will work.
So, now I am trying UCKB1 ROM (stock 2.2 Froyo for Captivate), specifically Cognition. This one is pretty successful, except...modems are few, and I have constant problems with WiFi enabling with Tasker.
Those are the two issues that seem to haunt my phone.
What is your experience? Of course, if you don't use Tasker, maybe the WiFi issue won't be a problem for you.
I suppose the auto rotate could be a sensor trying to go out on my phone...but, EVERY time I do the reinstall of 2.1 it fixes it. So I have cannot replace the phone, and given that it always starts working, I'm not convinced it is a hardware issue.
And for those on 2.2.1, what I've seen generally is that most people putting these ROMS on are flashing addicts (I'm not saying that is a bad thing ), but I prefer to use the phone and not constantly flash. Too much other config to set up after flashing.
Oh, by the way, one fault I have is way too many apps installed. I delete some and then next thing you know I've installed others. Pretty much requires that I use an OC kernel, and I like to use UV for battery performance. Interestingly, I have been quite successful at 1400, and 1.5%/hour drain at idle, with WiFi, GPS, and BT on.
Click to expand...
Click to collapse
I've been on a phoenix 4.5 for a while, and I'm pretty happy with it right now. I should probly update it though.
To be honest... every single ROM (minus one or two random tries) in this forum are worth keeping, imo.
They all have their pros and cons, but they're all well made.
I never make it more than like 3 weeks (and that was on CM7 lol) without flashing because I'm an addict, but there are a lot of stable ROM's
A few I really like:
Phoenix
Serendipity
Continuum
There are many others, but you get the idea!
Regards
Smith
longest i was on Darky's 8.0..for 2 months...then CM7 for 3 weeks....lol...but almost all 2.2.1 roms are stable to stick on one for long time..
erm, the best 2.2 one ive been on is serendipity . It simply does everything...
When i decided to move onto 2.3, i used MIUI (Still using it)
Yes, my expectations are that all the roms are 'great'. But, as noted, I have not had ANY that don't end up with problems, as outlined above. Other problems, depending on which ROM, and kernel combination, is Blue Tooth voice dialing. Again, I'm looking for someone using them successfully long term.
I'm hearing people like sames ones I have tried, plus one or two.
What is strange is the issues I outlined above that I continue to have. May be related to my hardware...don't know. Will be interesting to see if anyone posts that indicates having same problems, and even better, having conquered them either with specific ROM or a fix.
Thanks. I'll continue to watch this thread, and will likely try a different ROM.
Over 6 weeks on Andromeda and no issues. Smoothest, most stable ROM available for the Cappy IMHO.
Did you try performing a horizontal calibration when auto rotate stopped working?
Sent from a place my wife doesn't know about
mrhaley30705 said:
Did you try performing a horizontal calibration when auto rotate stopped working?
Sent from a place my wife doesn't know about
Click to expand...
Click to collapse
Yes, I believe so. It indicated no sensor or something. But it has not been around 3 weeks since moving to 2.2, and it hasn't happened again. If it does, I will be sure to do that again.
If this continues to work w/o Auto Rotate problems, I may end up putting 2.2.1 back on, and see what happens.
I tried everything with the same reservations--the odd bug and amateur hour theming.
Until Andromeda. No bugs ; stock UI. Haven't flashed anything in 2 months.
No phone are created equal(hardware limitations) and may react differently with different types of rom or kernel but so far my phone likes paragon rc6 even with 1400mhz kernel and faster mount in ext4 my phone is pretty stable. With other rom with the same clock speed it is not as fast and stable as paragon. So flash any rom out there until your phone meet its match.
gorgy76 said:
No phone are created equal(hardware limitations) and may react differently with different types of rom or kernel but so far my phone likes paragon rc6 even with 1400mhz kernel and faster mount in ext4 my phone is pretty stable. With other rom with the same clock speed it is not as fast and stable as paragon. So flash any rom out there until your phone meet its match.
Click to expand...
Click to collapse
I've been on dillis rom for about 3 months straight. I tried cm6 a while ago and I think I tried cognition the first time I flashed but dillis is just so simple, stripped and speedy. awesome GPS too(huge for me) and batt life exceeds a day(even more huge). however, themes and fluff arent my thing. I don't think I'm the only dilli fan with this opinion.
Sent from my SAMSUNG-SGH-I897 using XDA App
Good feedback everybody. I may experiment with one, or more, of the ROMS discussed here.
At the moment, I not sure how long I've been on my current ROM (Cognition 4.2.1), but at the moment, my issues may be working out.
The WiFi issue is improved since doing a clear of cache and Dalvik cache. We'll see how that goes.
The Auto Rotate, so far, has not messed up.
The one nagging thing at the moment is my notification volume constantly changes back to very low. Not sure what is causing that.
I've seen a couple votes for Andromeda. I was looking in that thread a few days ago, and even the change log (didn't read top to bottom extensively) and I could not find what it is based on; what kernel it is using; or modem. Of course kernel and modem would be changeable, but I would like to know what base it is on.
Again, my goal is to find something working well; performing well. Its interesting that after starting this thread, my 'issues' seem close to resolved based on what I'm running. Want to give it more time.
ewingr said:
I've seen a couple votes for Andromeda. I was looking in that thread a few days ago, and even the change log (didn't read top to bottom extensively) and I could not find what it is based on; what kernel it is using; or modem. Of course kernel and modem would be changeable, but I would like to know what base it is on.
Click to expand...
Click to collapse
should have read the Q&A thread on it....
http://forum.xda-developers.com/showthread.php?t=962276
Pirateghost said:
should have read the Q&A thread on it....
http://forum.xda-developers.com/showthread.php?t=962276
Click to expand...
Click to collapse
You are right. Seems nobody has any standards on where to put that information. Seems to me the OP should contain the basic info on what it is built on. Or the release notes linked from the OP.
Whatever....
ewingr said:
You are right. Seems nobody has any standards on where to put that information. Seems to me the OP should contain the basic info on what it is built on. Or the release notes linked from the OP.
Whatever....
Click to expand...
Click to collapse
not trying to flame but isn't failure to read the reason for a lot of thread starters and posts. blame it on yourself before the rom developer.
Sent from my SAMSUNG-SGH-I897 using XDA App
rjblack11 said:
not trying to flame but isn't failure to read the reason for a lot of thread starters and posts. blame it on yourself before the rom developer.
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
EXACTLY!
yeah, it would suck to have to read a QUESTIONS AND ANSWERS thread when you have a QUESTION about the rom that needs ANSWERED
Pirateghost said:
EXACTLY!
yeah, it would suck to have to read a QUESTIONS AND ANSWERS thread when you have a QUESTION about the rom that needs ANSWERED
Click to expand...
Click to collapse
I agree with you, but I also agree with the FDA and suggest putting all BASIC info right on the bottle (the ROM OP). Would benefit everyone.
rjblack11 said:
not trying to flame but isn't failure to read the reason for a lot of thread starters and posts. blame it on yourself before the rom developer.
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
I agree with you. I do. I don't want to flame or start a war on it either.
I commented that I did not read comprehensively; and I commented in my reply that he was right about that I should have read the Q&A. My only point was I did read what I considered the logical places: the OP; and the release notes, particularly the earlier part of the release notes, whre typically what the ROM is made up if would be stored.
Does that not make some sense?
That's all I was getting at. While I have read a thread front to back, I only do so if I have decided I do want to use the ROM. Sometimes a little logic in placement of information in documentation makes the documentation so much better.
Now, I will go read, and see if I want to try Andromeda. I recall the Armani ROM coming out, and something rings a bell about that which made me stay away, but I have no idea now what that was. That was very early in my efforts to install ROMS.
Back to our regular show ...
ewingr said:
I recall the Armani ROM coming out, and something rings a bell about that which made me stay away, but I have no idea now what that was. That was very early in my efforts to install ROMS.
Click to expand...
Click to collapse
your hesitation with armani was likely a couple of us bricking our phones with the bootloader that shipped with the original armani rom. the boot loaders have been removed from the CWM flashable and do not cause bricks

what is the most stable rom?

Hi everyone,
Since last october, i have flashed numerous roms, too many to list, actually, flashed a least 20 different roms. Although, many have been impressive on looks and gizmos, none have been 100% reliable.
The most common and annoying problems recently have been losing calls due to the wonk issue, ...and yes, i do have the most recent dewonk app installedand running.
On CM6, that was not a problem, but battery life was discusting.
Another issue that i have never been able to correct, is the touchscreen problems, no rom has ever been reliable regarding that issue.
Is it that my phone is deffective ?
So the top 3 things i am looking for is
No wonkiness
no touch screen issues
and good battery life
So, if any of you guys out there know of a rom/kernell/radio combination that can offer that, i would praise you like android gods!!!
Thanks in advance for your replies..... i'm just sick of going around every week for a new miracle solution......
you might wanna try SuperAOSP from [email protected]
i've been on it since 2 months ago and i'm a happy user indeed
Sorry to burst your bubble, but roms are never "stable" per say. There are always bugs and risk factors.
Plus, this is the wrong thread to be asking the question too I believe...
But to answer the question,
I'm a CM person.
Hell if you find such rom let us know!!
N1
Yes. The touchscreen on the nexus one is defective. Google it. It cannot distinguish which x or y coordinates belong to each finger and it cannot distinguish touch points near each other.
Sent from my Nexus One using XDA App
Try the CM7 nightly BUILD #39 from imfloflo and flash wildmonks latest kernel.
The kernel is newer and contains newer drivers. The #39 is the real final version of CM7
i think it cannot be more stable
This is most certainly not development. Thread moved to Q&A, where it belongs.
Cm7 nightly 41 with intersectraven's latest is pretty darn stable
Sent from my Nexus One using XDA Premium App

Issues wid Miui 2.2.3. Need help

Hi
I am presently using Miui 2.2.3 by CacingKalung and i feel that the touch screen is kinda laggy. Many a times the touch does not react immediately and also the market force closes when i try to open few apps. Has any one else been facing this issue?
And secondly what does a kernel mean? I am really sorry if its a stupid question but i see so many discussing abt the different kernels and its uses but i just cant understand how it helps the phone. I have been following the development section for quite some time but i am still not allowed to post anything there as my number of posts are less than required. I feel its really a shame that i still cant post anything in the dev section though i have been logging in almost every day for the last 3 months now.its kinda frustrating too. so that's the reason i am posting my query here. Any help is really appreciated. Thanks in advance.
Cheers,
Shri
Kernel .....
As far as I know ..... , and correct me if i m wrong .....
Kernel is a interface which sits between your operating system and hardware (CPU,Memory etc.). So, here gigerbread,miui,CM7,ICS these all are OSs and kernel translates commands from OS to hardware and vice verse.....
Different kernels have different translating ability, so some can translate faster with your screen responses others cant,some can support two way call,better HD graphics, while some are bit slower ....
aloklike said:
As far as I know ..... , and correct me if i m wrong .....
Kernel is a interface which sits between your operating system and hardware (CPU,Memory etc.). So, here gigerbread,miui,CM7,ICS these all are OSs and kernel translates commands from OS to hardware and vice verse.....
Different kernels have different translating ability, so some can translate faster with your screen responses others cant,some can support two way call,better HD graphics, while some are bit slower ....
Click to expand...
Click to collapse
Thanks for the explanation any suggestions on installing kernels? i have tried UC kernel by Napstar but i did not see any difference in the performance of the device after installing it. so am i doing something wrong?
Thanks.
shri080 said:
Thanks for the explanation any suggestions on installing kernels? i have tried UC kernel by Napstar but i did not see any difference in the performance of the device after installing it. so am i doing something wrong?
Thanks.
Click to expand...
Click to collapse
Should give time to settled right after boot.
Feels no big different for each kernel. But if you try other than sdkernel or mock kernel, your wifi won't work on this 2.2.3.
Sent from CSL-MI410 MIUI 2.3.2
CacingKalung said:
Should give time to settled right after boot.
Feels no big different for each kernel. But if you try other than sdkernel or mock kernel, your wifi won't work on this 2.2.3.
Sent from CSL-MI410 MIUI 2.3.2
Click to expand...
Click to collapse
Thanks for the reply CacingKalung. Could you please do something about the touh sensitivity and the in call volume issue? The touch especially is kinda laggy. I am now using MIUI 2.3.7 hooney comb them based ROM by elol. The touch works perfect in this ROM and also there is no call volume issue so far but some apps force close like Fring and power amp which are very important for me. so want to switch to some other stable ROM. Any help would be appreciated. Thanks.
Cheers,
Shri
ok i re-installed the ROM and now the touch screen seems to be working fine. But i forgot to mention the main issue i am facing. The audio quality seems to have gone down. The sound is feeble now. some times accidentally it becomes louder which is actually the normal output but otherwise its feeble all the time. CacingKalung can you please do something about this? i am writing all this only because of all the ROMs i have used i liked this one the most i shoud say CacingKalung has done a wonderful job !!! and i really want to stick on to this for some time until we get a stable and fully working ICS. Hopefully there is a solution for this. Thanks in advance for any help and keep up the woderful work.
EDIT : The sound now is fine looks to me like a hardware issue but i can confirm that its not because of this ROM... so looks like all my issues are resolved
Cheers,
Shri
Nice... you can solved your problem by your self...!

What is the cause of BSODs?

I have them in GB/ICS and JB on official and custom roms. Seems that 312mhz min freq fixes for CM7 at least.
Why does this happen? Why hasn't LG fixed it? WHAT IS THE CAUSE?
Used to happen with any ROM on my Asus tf101...
Afaik until now no one know what exactly is causing this even other androids have this or all androids
Edit: oh i find it on my brain as i remember tonyp said that our cpu or the android cpu is failing to wakeup and this is a outdated binaries? Can someone correct me
Sent from my Optimus 2X using xda premium
grimmyrippy said:
Afaik until now no one know what exactly is causing this even other androids have this or all androids
Edit: oh i find it on my brain as i remember tonyp said that our cpu or the android cpu is failing to wakeup and this is a outdated binaries? Can someone correct me
Sent from my Optimus 2X using xda premium
Click to expand...
Click to collapse
As far as i know what you are saying is true...
Since people are saying the problem is more or less evident on all ROMs (custom or official) and on different phones, I am wondering whether this may (at least partially) be hardware-related, meaning a problem with the particular phone (not a model, but that very unit)? Just wondering because I am hot having this problem at all. I did see a lot of FCs or freezes while trying some experimental/unstable/beta ROMs, but with the stock-based ROM I am currently using I have not seen a single SOD. Same is true for DM ROM (also stock-based). What am I doing wrong? I admit, I am not using the phone as actively as many people do. I don't play any games. I don't install a lot of different apps. Just a regular daily use -- calls, email, browsing, WiFi/BT/GPS. But no SODs whatsoever...
I have no idea whats causing the BSOD, but my experience with my phone is it depends on which kernel I use.
Some kernels give BSOD no matter what ROM I use, but others "never" gives any BSOD.
I honestly have no idea but I have a feeling it's more hardware related than software. Also other android devices suffer from it?
-sandro- said:
I honestly have no idea but I have a feeling it's more hardware related than software. Also other android devices suffer from it?
Click to expand...
Click to collapse
Yes also other but other android is looking for deep sleep feature it mean that they actually want to have deep sleep on their phone to save battery and their something on our phone that triggers deep sleep and i think this something is the one we need to fix
Sent from my Optimus 2X using xda premium

[PETITON]Multitouch issue on stock kernel

Hi,not all know,that stock 3rd htc kernel and its kernel source have multitouch bug.So i created a petition for htc,that will be sended if we will become inaf signs.
If you are in,just follow link below and sign
http://www.ipetitions.com/petition/incredible-s-touch-screen-fix/
How would that work? HTC cant fix it, i thought kernels are google?
Sent from one of the few remaining Incredible S'
Piccilino said:
How would that work? HTC cant fix it, i thought kernels are google?
Sent from one of the few remaining Incredible S'
Click to expand...
Click to collapse
Nah HTC fubar'd the source for ICS on our device (others too iirc) so any kernel compiled from HTC's source will have the issue unless its patched.
The kernels we have are HTC's work, I think forked from google android ICS (hence being 3.0.x)
Piccilino said:
How would that work? HTC cant fix it, i thought kernels are google?
Sent from one of the few remaining Incredible S'
Click to expand...
Click to collapse
Htc's phone, their responsibility and also their job to provide both kernel and kernel source.
Sent from my Incredible S using xda app-developers app
yep.htc fault
Splux said:
Htc's phone, their responsibility and also their job to provide both kernel and kernel source.
Sent from my Incredible S using xda app-developers app
Click to expand...
Click to collapse
+1
Stupid HTC. First they stop developing for our phone then stops other people developing for our phone.
Sent from one of the few remaining Incredible S'
Just signed
kernel
I have the same problem, but my problem is with the kernel 3.0x,
so the problem is Sd card unexpectedly removed for every rom who has kernel 3.0x,
all started when i got ota ics,
htc repair center say's i have to replace motherboard for 250$, but i know, that the problem is in kernel 3.0x.
Is this multi-touch issue related to the input delay that is present on most of the Sense based roms? The only exception to this is the chinese kang kernel, where I beleive the input delay is fixed. The problem I have is that I'm not very excited by the Sense's UI. I've noticed that the 2.6.4 hacked ICS-JB kernel seems to have this input delay fixed, or greatly reduced... Is it possible to get the patches/changes we need from there?
I just got my hands on a Galaxy S1, and despite the crappy camera, lower RAM and lack of a flashlight, the seemingly perfect touch input is something that I'm very torn over. Now I'm in a position of giving my Inc S to one of my relatives, or the Galaxy S1. I love the community for the Inc S and am very excited by the progress made to JB since December but am extremely tired of not being able to play all games, or wait for my keyboard to catch up with what I've typed because of this F#[email protected]#ing input lag. Anyone have any opinion on the things I've discussed or have something to add to it? I've got a week to decide what I like better...
Before someone mentions not experiencing any input lag: There is a selectable option in developer options, called "Show Touches". If you have this enabled, and try moving your finger around your screen in various patterns, you'll notice that the white circle trails behind where your finger is by a large amount. If you try this on other phones, the distance at which the white circle trails behind your finger is greatly reduced. There are also situations where tapping the screen rapidly in different areas is occasionally completely ignored.
jancis201991 said:
I have the same problem, but my problem is with the kernel 3.0x,
so the problem is Sd card unexpectedly removed for every rom who has kernel 3.0x,
all started when i got ota ics,
htc repair center say's i have to replace motherboard for 250$, but i know, that the problem is in kernel 3.0x.
Click to expand...
Click to collapse
No one reported about that probelm,I don't think it's kernel issue,tru to format your sd card or use another if you can
so i'm from russian forum,it's big and no one repoted about it
TheMegosh said:
Is this multi-touch issue related to the input delay that is present on most of the Sense based roms? The only exception to this is the chinese kang kernel, where I beleive the input delay is fixed. The problem I have is that I'm not very excited by the Sense's UI. I've noticed that the 2.6.4 hacked ICS-JB kernel seems to have this input delay fixed, or greatly reduced... Is it possible to get the patches/changes we need from there?
I just got my hands on a Galaxy S1, and despite the crappy camera, lower RAM and lack of a flashlight, the seemingly perfect touch input is something that I'm very torn over. Now I'm in a position of giving my Inc S to one of my relatives, or the Galaxy S1. I love the community for the Inc S and am very excited by the progress made to JB since December but am extremely tired of not being able to play all games, or wait for my keyboard to catch up with what I've typed because of this F#[email protected]#ing input lag. Anyone have any opinion on the things I've discussed or have something to add to it? I've got a week to decide what I like better...
Before someone mentions not experiencing any input lag: There is a selectable option in developer options, called "Show Touches". If you have this enabled, and try moving your finger around your screen in various patterns, you'll notice that the white circle trails behind where your finger is by a large amount. If you try this on other phones, the distance at which the white circle trails behind your finger is greatly reduced. There are also situations where tapping the screen rapidly in different areas is occasionally completely ignored.
Click to expand...
Click to collapse
it's not only sense based rom's issue
you can test unofficial cm10,v1 have multitouch issue too,can't say something about later versions.
2.6.x kernel just doesn't have that multitouch bug,i think it's one more reason why all CM rom's were based on it,even 3.x kernel source was released
saneksem said:
it's not only sense based rom's issue
you can test unofficial cm10,v1 have multitouch issue too,can't say something about later versions.
2.6.x kernel just doesn't have that multitouch bug,i think it's one more reason why all CM rom's were based on it,even 3.x kernel source was released
Click to expand...
Click to collapse
No, we had CM9/10 ROM's based on the 2.6.x kernel because no one managed to get it booting with a 3.x kernel until very recently.
Splux said:
No, we had CM9/10 ROM's based on the 2.6.x kernel because no one managed to get it booting with a 3.x kernel until very recently.
Click to expand...
Click to collapse
ok,thx for information)
saneksem said:
No one reported about that probelm,I don't think it's kernel issue,tru to format your sd card or use another if you can
so i'm from russian forum,it's big and no one repoted about it
it's not only sense based rom's issue
you can test unofficial cm10,v1 have multitouch issue too,can't say something about later versions.
2.6.x kernel just doesn't have that multitouch bug,i think it's one more reason why all CM rom's were based on it,even 3.x kernel source was released
Click to expand...
Click to collapse
I have formated sd card, i have bought two new one's(same problem), and when i put files bigger then 4gb and try to run game, game starts and i get back to home screen and in notification bar shows sd card removed unexpectedly.
Everything works flalwless on every rom who uses gingerbread (hacked) kernel, on 3.0x kernel roms the problem starts all over again.
Even if you get 10 million in petition htc will not fix this. Sorry to burst your bubble.
Evilus said:
Even if you get 10 million in petition htc will not fix this. Sorry to burst your bubble.
Click to expand...
Click to collapse
why you think so?
saneksem said:
why you think so?
Click to expand...
Click to collapse
Because we tried this for kernel 3 and in the end htc said nothin.
Sent from one of the few remaining Incredible S'
Piccilino said:
Because we tried this for kernel 3 and in the end htc said nothin.
Sent from one of the few remaining Incredible S'
Click to expand...
Click to collapse
after becoming signs i will send it to htc offices,did you make it?
saneksem said:
after becoming signs i will send it to htc offices,did you make it?
Click to expand...
Click to collapse
Nope i just signed.
Sent from one of the few remaining Incredible S'
There's a multi touch fix available in the unofficial CM10 thread. OP says it is for both sense and cm/AOKP ROMs. I've flashed it on ARHD and it runs just fine. That is if you are s-off and rooted.
Dead cookies leave no trails...

Categories

Resources