No hoax here, i saw some vids about other phones having problems with their touch screen. So i decided to test em myself.
Get some software from the market or whatever that lets you see where the touch point is registered.
Divide the screen into four equal parts, by drawing an imaginary half-line on the two axis, and lets label them from the top left going clockwards, 1-4.
I put my finger on quadrant 1, and the other on quadrant 3.
Then, i moved quadrant 1 finger to quadrant 2
and the finger on quadrant 3 to quadrant 4.
And when i do that, the touch point becomes reversed, specifically, the touch points are registered left and right mirrored.
Anyone suffer those symtoms?
+ The phone can't register more than 2 points. Is that normal?
++ Just checked there is no other thread about this problem
Cheers
dongimin2 said:
No hoax here, i saw some vids about other phones having problems with their touch screen. So i decided to test em myself.
Get some software from the market or whatever that lets you see where the touch point is registered.
Divide the screen into four equal parts, by drawing an imaginary half-line on the two axis, and lets label them from the top left going clockwards, 1-4.
I put my finger on quadrant 1, and the other on quadrant 3.
Then, i moved quadrant 1 finger to quadrant 2
and the finger on quadrant 3 to quadrant 4.
And when i do that, the touch point becomes reversed, specifically, the touch points are registered left and right mirrored.
Anyone suffer those symtoms?
Click to expand...
Click to collapse
Yes: this problem is found in many smartphones, including the LG P500. Google for "axis inversion bug" if you wanna know more.
dongimin2 said:
+ The phone can't register more than 2 points. Is that normal?
Click to expand...
Click to collapse
It is normal. Cheaper multitouch screens don't support more than two fingers. Again, it's a limitation common to many other smartphones.
Thats why we cannot play Slice It.
I was wondering.. what if someone writes an app that runs in background, that intercepts the touches from the user and send the (reversed) input to the proper system "thingamabomb"?
I mean... this problem occours in a precise way (multitouch+slide): there has to be a way to fix it with some user-written software! come on dev community, surprise us!
Sent from my LG-P500 using XDA App
Related
Hello everyone,
My x10 screen is kinda jumpy when i initially slide my finger on the screen. like on the home screen or in web browser, if i pick my finger up and place it back down then slowly slide it, it take about 3 or 4 milimeters before the touch is register and the rest of the screen suddenly jumps to the position where the finger is. But if i leave my finger on the screen and slide it around it does not jump anymore, its only when i pick my finger up and place it back down, its like the touch has a dead band or something and doesn't get register until it is slide away at a certain radius from where it was initially started.
Like on an iphone, the touch is register right away as soon as my finger is placed on the screen. like when i place my finger on the screen and make a really small slide movement the screen will respond to even the smallest finger movement. but on the x10 i have to slide my finger for a small distance for the screen to acknowledge the presence of the touch and then the screen jumps to the position.
It might not bother some of you but it make it look not smooth in scrolling.
is there anyway to make it to the screen acknowledge the touch right away.
Thanks
What firmware 1.6 or 2.1 r u running or ROMS r u running?
Sent from XDA Premium from my X10a rooted running 2.2.1 CM Rom from Rendeiro2005
I'm using the stock sony ericsson 2.1 firmware with jit mod.
Are you not experiencing this twitchy effect on your device?
No i am not. What version of jit do u have?
Jit is probably doin that
Sent from XDA Premium from my X10a rooted running 2.2.1 CM Rom from Rendeiro2005
That's strange. well how do i know what version of jit do i have. can i uninstall it?
The jumpy effect i'm talking about is, let say on you main screen, then you pick up your finger and place it back down onto the screen and then slowly slide it about two or three milimeter to the left or the right, the scrolling desktop doesn't acknowledge the touch right away until you slide your finger a little further than about three milimeter away from the original position where you first place your finger, then the desktop scrolling just suddenly jumps right into position. It hapen on all scrolling in everywhere else too, not just the desktop screen. the scrolling doesn't start as soon as you place the finger on the screen.
But as long as i keep my finger on the screen to scroll around its fine, its just when i pick up my finger and place it back down again when it reinitialize the touch again.
Everyone with a 2.1 ROM has it. It's because of the FPS cap. When bootloader gets cracked this will be fixed
You need to tweak the maxeventspersecond in the build prop to 260...
Makes a huge diff!
Search maxevents on here to find the exact line to add to your build prop...
Or just switch to cm 6.1.3 by wolfbreak
windowsmgr.max_events_per_sec=260
Add that to your build prop
just tried that windowsmgr.max_events_per_sec=260 trick. it only made the scrolling smoother. but the touch acknowlegement from the screen is still the same. i had to slide my finger for about two to three milimeters for the screen to respond. when i do it fast it look smooth. but when i do it slow i can see the screen just suddenly snaps into position when i slide my finger just a little bit.
somehow i have a feeling sony ericsson use a cheap technology digitiger for the x10.
oh well.
xxcysxx said:
just tried that windowsmgr.max_events_per_sec=260 trick. it only made the scrolling smoother. but the touch acknowlegement from the screen is still the same. i had to slide my finger for about two to three milimeters for the screen to respond. when i do it fast it look smooth. but when i do it slow i can see the screen just suddenly snaps into position when i slide my finger just a little bit.
somehow i have a feeling sony ericsson use a cheap technology digitiger for the x10.
oh well.
Click to expand...
Click to collapse
Try froyo.. wolfbreaks cm 6.1.3 is smooth as silk. I have none of the issues you describe, my touchscreen reacts instantly
fiscidtox said:
windowsmgr.max_events_per_sec=260
Add that to your build prop
Click to expand...
Click to collapse
Hey i wanna try that....where in build.prop do i add it? At the very end?
Sent from my X10a using XDA App
Mr Patchy Patch said:
Hey i wanna try that....where in build.prop do i add it? At the very end?
Sent from my X10a using XDA App
Click to expand...
Click to collapse
yes on mine it's the third last line
fiscidtox said:
yes on mine it's the third last line
Click to expand...
Click to collapse
Yeah, i should have edited my post. Got it in there, scrolling does seem better. Wolfs rom is still untouchable tho.
Sent from my X10a using XDA App
I've searched long and at any places, but nowhere was an answer. Everybody goes crazy if we talk about sensitivity, but what are the benefits of a higher sensitivity really?
I mean, here on mother earth, you can't get something better, without decreasing other features...
So if i turn the sensitivity higher (or lower), i mean if its more precise... Where are the disadvantages?
Higher battery drain?
Please help me to understand
I you slide you finger over the screen it takes a small distance before the phone reactes and moves the part of the display. Try it and you will notice this small distance on the homescreen. It is like a dead zone where you move your finger but nothing happens.
With the toch sensitivity fixes or apps or scripts you can decrease this distance to 0 or any other value. I think a value around 5 is quite common. I am not sure but I thought 15 is default, so you usually want to decrease it.
A disadvatage is, that if you set it too low, the phone might recognize klicks a swipes.
Schindler33 said:
A disadvatage is, that if you set it too low, the phone might recognize klicks a swipes.
Click to expand...
Click to collapse
That was the answer i wanted! Thank you!
On some older kernels, when your phone is on ac power, the screen becomes very unresponsive. That's why people came up with the need to change the touch sensitivity.
Sent from my GT-I9100 using Tapatalk
Hi guys,I bought a Xperia Mini Pro to my girlfriend.
Like my Xperia Mini has the worst touchscreen that I ever seen/touched.
Try to play Fruit Ninja is impossible,because the touchscreen lose your fingers.
If you draw a circle very fast with a paint app,it's lose your touch.
This is annoying when I navigate on the browser or scroll contacts and music.
Why no one has noticed this problem?
The only problem on your list that i noticed is with fruit ninja but the weird thing is that it's working well with the other app called fruit slice
That's the only problem i noticed about the touchscreen in 2 month of use (sk17)
otherwise I am quite satisfied.
I have Mini Pro (SK17i) and I still get nearly 1000 points in Fruit Ninja (Arcade Mode), not too much but I think it's not bad at all.
I advice you to download "Multi Touch Paint" and you will discover how malfunctioning this touchscreen.
Use this app in "Kids Mode" and made a continuos circle very fast.
In Xperia Mini there are some disconnects.
In Xperia Mini Pro the touch screen is crazy,because the pen is going where don't touch.
I dont know why are you having hard time with screens, but my Xperia mini works perfect, never had any problems with it
Sent from my ST15i using XDA App
peexl said:
The only problem on your list that i noticed is with fruit ninja but the weird thing is that it's working well with the other app called fruit slice
That's the only problem i noticed about the touchscreen in 2 month of use (sk17)
otherwise I am quite satisfied.
Click to expand...
Click to collapse
Because Fruit Ninja use multitouch while fruit slice use single touch.
Alchnemesis said:
I dont know why are you having hard time with screens, but my Xperia mini works perfect, never had any problems with it
Sent from my ST15i using XDA App
Click to expand...
Click to collapse
I send it to Sony Ericsson Support,I hope that they can fix it.
Using an (constantly under RAM pressure) X8 at the moment I unfortunately have to agree that touchscreen responsiveness is noticeably inferior on both the mini and the mini pro. I noticed when using the device one handed, i.e. operating the screen with the thumb. Fast scrolling is nearly not possible. We're not talking about performance here, the device ist fast. It is about the digitizer being unable to register quick flings over a short distance.
To visualize this I tried Kids Paint Free. It simply draws gestures with random colors for each stroke. This is perfect to determine whether the digitizer has lost the finger: if it has, a new color will be drawn.
I drawed a couple of QUICK vertical up-down flings of about one inch length each at about four strokes per second. The X8 registered these correctly and displayed them at the given length. The mini (and also a mini pro I tried at a local store) registered only at most half an inch of the movement. If you increase gesture speed even further, some are being registered as taps (resulting in a dot being drawn)!
This is exactly what happens when scrolling around: it feels laggy, because you can't input a certain length of fling in a short time, i.e. "give power to the scroll". Occasionally you might even end up with a false tap where you actually wanted a scroll.
Another test is to start on the upper right corner an try to fill the whole screen by diagonally wiping to an fro until you reach the lower left corner. This will even end up in the digitizer not responding until you lift the finger again. It was not possible to fill the screen in one long gesture! Again no problem on the X8.
I returned my mini yesterday for this very reason, it renders the device unusable to me. A real pity, given the otherwise good specs of it.
Now: have I encountered defective devices? Can anyboy confirm? Is there a parameter to set some kind of progression like with mouse pointers on a PC?
You phone might have problem with heating and navigation keys. Keys are connected to screen, so every time you hold you finger on the screen, keys may react by themselves. Send it to service if you have warranty.
Its very strange that you have screen issues... I have sk17i and also try st15 in store. Feelings just awesome,
sensivity and speed is very good. No lag or stucks at all time. Maybe you sould return that one for warranty
Sent from my SK17i using XDA App
I have the very same stupid problem, is there any fix ??
I also unlocked the bootloader and installed last CM Nightly and the problem still exists !
Nope. Doesnt have this problems on my SK17i. It only happens on your device. Your made topic sounds ridiculous
Sent from my SK17i using XDA App
My Xperia mini pro has perfect touchscreen mayb this mans on bad luck!!
Sent from my SK17i using XDA Premium App
What do you mean by writing "Xperia Xperia Mini and Mini Pro have the worst touchscreen ever seen!" ?
I'm using sk17i for about 3 months and it just worked fine,well if u dont like sk17i buy another phone then,everything have positive and negative side.
If u cant live with sk17i,i recommend u to buy another phone
No offense,just saying
Touchscreen responsiveness Xperia Mini (Pro)
Hi all,
thank you for your input. Please don't blame the thread title, I didn't choose it and just didn't want to clutter the forum with another thread on the same topic.
Just for the right scope: my Mini did not overheat in any way, the two soft buttons worked perfectly. Also I'm not complaining about scrolling performance of the OS or the device. Once it scrolls, it does so smooth, lag-free and fast. I'm all about giving drive or momentum into quick (respectively short) strokes.
Please find two screenshots made with Kids Paint to illustrate what I mean. Sorry that I may not yet post image links. I'd be glad if anyone who is content with his or her digitizer performance could try the same on a their mini (pro)s. The APK is also attached.
Test case 1 (vertical flings):
Speed is absolutely of the essence. This screen has to be drawn in less than three seconds. There's no point in doing it slower, it will work. On the Minis I tried it was not possible to get the lines that long in the given time.
Test case 2 (screen fill):
Start at the upper right corner and fill the screen in one continuous stroke. Again, this has to be done in at most five seconds. I have not been able to do so, the Mini's digitizer lost my finger (new color drawn) and stopped completely reacting at about 3/4 of the screen.
I'd happily accept that I had devices from a defective lot and try another. I wouldn't invest time here on this issue if I didn't think that the Mini was THE phone for me (price- and spec-wise).
cmfan said:
Hi all,
thank you for your input. Please don't blame the thread title, I didn't choose it and just didn't want to clutter the forum with another thread on the same topic.
Just for the right scope: my Mini did not overheat in any way, the two soft buttons worked perfectly. Also I'm not complaining about scrolling performance of the OS or the device. Once it scrolls, it does so smooth, lag-free and fast. I'm all about giving drive or momentum into quick (respectively short) strokes.
Please find two screenshots made with Kids Paint to illustrate what I mean. Sorry that I may not yet post image links. I'd be glad if anyone who is content with his or her digitizer performance could try the same on a their mini (pro)s.
Test case 1 (vertical flings):
Speed is of absolutely of the essence. This screen has to be drawn in less than three seconds. There's no point in doing it slower, it will work. On the Minis I tried it was not possible to get the lines that long in the given time.
Test case 2 (screen fill):
Start at the upper right corner and fill the screen in one continuous stroke. Again, this has to be done in at most five seconds. I have not been able to do so, the Mini's digitizer lost my finger (new color drawn) and stopped completely reacting at about 3/4 of the screen.
I'd happily accept that I had devices from a defective lot and try another. I wouldn't invest time here on this issue if I didn't think that the Mini was THE phone for me (price- and spec-wise).
Click to expand...
Click to collapse
Like i said,everything have a weakness
Like i said,everything have a weakness
Click to expand...
Click to collapse
Maybe. Though I had expected SE to do at least as well as they did 1,5 years ago on the now outdated X8, wouldn't you?
Anyway, so does your comment mean your Mini Pro behaves the same way?
cmfan said:
Anyway, so does your comment mean your Mini Pro behaves the same way?
Click to expand...
Click to collapse
My daughter's xperia mini pro behaves the same way:-( Fast swype movements are not registered or misregistered to clicks. The problem is worsening, when the phone is on the charger. Overall, I am not satisfied with it, I will exchange it to an experia pro.
Sent from my Galaxy Nexus using xda premium
I have the same problem, and my touch buttons are not working properly either, and fast swyping is also terrible.
Sent from my SK17i using xda premium
I have the same problem with the screen. But is it case of warranty? Or just a feature in Apple style?
I havent face any issue yet
Sent from my SK17i using xda premium
Are there other ways to increase the touchscreen sensitivity? or Increase the X10 multi-touch Accuracy?
I want to ask this question too, but just specific on accuracy.
When I use apps to test the muiltitouch function, it will show a completely wrong result when I using two fingers.
It just show the result just like a "X"
(Assume that the end points of \ are my fingers and the end points of another / are the result)
eh_hk said:
I want to ask this question too, but just specific on accuracy.
When I use apps to test the muiltitouch function, it will show a completely wrong result when I using two fingers.
It just show the result just like a "X"
(Assume that the end points of \ are my fingers and the end points of another / are the result)
Click to expand...
Click to collapse
jrchan01 said:
Are there other ways to increase the touchscreen sensitivity? or Increase the X10 multi-touch Accuracy?
Click to expand...
Click to collapse
Short answer = (almost) "Impossible"
Almost cuz - you can maybe get the Multi-touch if you write the drivers from scratch (I guess you aren't good to driver coding )
Guys, accuracy and sensitivity are the opposite of capacitive touchscreens...
Its the bad on their technology and it is currently impossible to adjust their performance.Hw doesnt support it.
All is caused by massive "cool" fingerfriendy display hungry population.
Btw I am still crying for good phone with stylus performace screen capable for drawing...
So...
maybe I just pretend I am using a phone without muiltitouch
Is anyone able to play with the Archos 80 9g?
I got the Turbo 1,5ghz version but im not able to play frontline commando or shadowgun because the touchscreen is.. how should i say.. maybe unresponsive?
it feels like the touchscreens resolutions itself is very low and you cant aim precisely. Using latest Archos ICS (4.06 atm)
cheers
*snip*
I have the same issue..maybe a anti reflex display protection might work? I know that they make a smooth and "soft" feeling!
Ncyde47 said:
Is anyone able to play with the Archos 80 9g?
I got the Turbo 1,5ghz version but im not able to play frontline commando or shadowgun because the touchscreen is.. how should i say.. maybe unresponsive?
it feels like the touchscreens resolutions itself is very low and you cant aim precisely. Using latest Archos ICS (4.06 atm)
cheers
Click to expand...
Click to collapse
I noticed the exact same thing.
I installed the following app from the Play store:
Input Benchmark (not allowed to post external links yet)
It's really simple and it has only three tests: Touch, Accelerometer, Multitouch.
Touch test shows the frequency of the touch events. My G9 shows only 50 to 52 touch events per second if you move your finger really fast. My phone (Samsung Galaxy Spica) shows 60 events per second.
Accelerometer shows around 130 events per second, and my phone shows around 100 events per second.
The multi-touch test shows the pixel positions of all touch points. My phone can detect sub-pixel changes. After you calculate the touch resolution it recognizes around 1024*1024 touch points on a 3.2 inch screen (480x320).
My Archos G9 80 Turbo shows only around 227*227 touch points. Usually the touch quantization works out to 3.37335 pixels vertical and 4.4978 pixels horizontal. This means that the touchscreen cannot resolve finer movements, and this is the reason why homescreen scrolling from left to right looks very choppy if you keep your finger on the screen, and much smoother if you fling (start the transition with rapid finger movement and take the finger off of the screen). Sometimes I got other pixel values that were about in between other the values I usually got. I think that this means that the touchscreen is at least capable of double the current precision (probably around 512*512 touch points), but it still lags behind my phone from 2009/2010.
In the teardown tread the touchscreen controller is identified as Cypress TMA 340. I found some Cypress presentations that classify this as a 3rd Generation touchscreen controller that is intended for screens with less than 5.1" diagonal, with a notice that 4 point multi-touch should be used on screens smaller than 4.6 inches.
I found that HTC Sensation (that had a lot of touchscreen issues) also uses a Cypress TMA 340 series 4-point multi-touch digitizer as a replacement digitizer (there are at least 4 different digitizers used on the Sensation production). On a international HTC Sensation I get around 1024*1024 touch points resolution @ 60 touch events per second, so the controller should be capable of at least that. It isn't ideal for our screen size but it would be a significant improvement over the current situation.
This means the issue could be either hardware (the capacitive matrix is low-res), or software (the driver is broken or poorly written). If the issue is hardware, we can't do anything about it (except to perhaps replace the digitizer with a better one, and add support for it in the kernel). If the issue is software, we maybe get some improvement later via improved or tweaked drivers (Cypress has released their drivers as open source)
Perhaps there is a trade off between 4-point multi-touch and 2-point multi-touch, and we could get better touch resolution if we allow only 2-point multi-touch.
neur0mans3r said:
...
My Archos G9 80 Turbo shows only around 227*227 touch points. Usually the touch quantization works out to 3.37335 pixels vertical and 4.4978 pixels horizontal. This means that the touchscreen cannot resolve finer movements...
Click to expand...
Click to collapse
This explains why when using a stylus and drawing a diagonal line I see an image that looks like a fine staircase rather than a smooth line.
So what can we do?
Does any1 know if Archos is aware of this fact?
Anyone willing to downgrade to honeycomb and test? Then we can know if its a kernel problem or a hardware problem
I made a basic test that displays the touch data provided by Android. For my G9 80 it shows a touchscreen resolution of 2048x2048, but in most cases the actual resolution is much lower.
When you move your finger horizontally or vertically, the difference between touch points on the main axis (the direction your finger is moving) is around 9 points (around 4.5 pixels horizontally and 3.37 pixels vertically). However, on the other axis you get much better results (all the way down to 1 touch point). The apparent touchscreen resolution depends on the angle between the motion of the finger and the horizontal and vertical axises of the digitizer.
To recap, in the most basic use case when moving your finger horizontally to navigate homescreen and app drawer, you get stuttering because the touch events are reported like that, not because the hardware is slow to render.
Since in games you usually move your fingers in the direction you need them to go this does not work as expected because the aiming jumps around too much.
I really hope this is a driver issue (some sort of poorly written averaging filter).
Shano56 said:
Anyone willing to downgrade to honeycomb and test? Then we can know if its a kernel problem or a hardware problem
Click to expand...
Click to collapse
I am on Honeycomb most of the time (my Gen9 doesn't like ICS)
Gen9 101 1GHz 512MB, using Input Benchmark:
Touch- 62-75 Hz
Accelerometer- 125-130 Hz
Multitouch- max x-y is correct (1280x800) but touch point move is registered
a)for "normal" speed- every 4-5 pixels for X and every 3-4 pixels for Y
b)for slow speed (press a finger to the touchscreen and tilt it slowly left/right)- readings are inaccurate- it registers 1 pix for X and 1 pix for Y but there is plenty of places where registered point "goes back" (eg- 630->tilt right->blinks between 627 and 631) and/or touch is not detected (this also flickers)
neur0mans3r said:
My phone (Samsung Galaxy Spica) shows 60 events per second.
Click to expand...
Click to collapse
I guess you use tom3q's CM7?
Were you by any chance using FrankenKenrel or FrozenLake previosuly?
gen_scheisskopf said:
I guess you use tom3q's CM7?
Were you by any chance using FrankenKenrel or FrozenLake previosuly?
Click to expand...
Click to collapse
Yes, tom3q's CM7 with the underclocked-overclocked-synced kernel (sound silly but is an accurate description) . I was mainly using Yonip kernels with FroYo.
I made a simple test app (attached in the above post) that shows the difference in the coordinates of touch events in pixels and touch points themselves. I tried it on a HTC Sensation and it's working OK with sub-pixel precision.
It looks like this behavior is not ICS specific, but Archos specific (maybe even G9 80 specific).
neur0mans3r said:
Yes, tom3q's CM7 with the underclocked-overclocked-synced kernel (sound silly but is an accurate description) .
Click to expand...
Click to collapse
I know what you mean, I did some pre-alpha tests for tom3q
neur0mans3r said:
I was mainly using Yonip kernels with FroYo.
Click to expand...
Click to collapse
Competition.....
FrankenKernel was for Ecalir btw
neur0mans3r said:
I made a simple test app (attached in the above post) that shows the difference in the coordinates of touch events in pixels and touch points themselves. I tried it on a HTC Sensation and it's working OK with sub-pixel precision.
It looks like this behavior is not ICS specific, but Archos specific (maybe even G9 80 specific).
Click to expand...
Click to collapse
Tested and
-"normal" speed 4-5 pixel precision for both X and Y
-slow speed- 4-5 pixel precision for the main movement axis and at the same time 1 pixel precision for the second axis
gen_scheisskopf said:
Tested and
-"normal" speed 4-5 pixel precision for both X and Y
-slow speed- 4-5 pixel precision for the main movement axis and at the same time 1 pixel precision for the second axis
Click to expand...
Click to collapse
I think the difference in touch points is more representative because we get an integer (4-5 pixels is 9-10 touch points).
Main question is can this be fixed (or atleast improved somewhat) with a driver update/fix, or is this a limitiation of the digitizer.
P.S. I skipped Eclair and went straight to criminal's CM 6.1.
neur0mans3r said:
I think the difference in touch points is more representative because we get an integer (4-5 pixels is 9-10 touch points).
Main question is can this be fixed (or atleast improved somewhat) with a driver update/fix, or is this a limitiation of the digitizer.
Click to expand...
Click to collapse
Main question- how outdated are drivers and touchscreen firmware (if present), and who wrote them (read: can we source newer/not broken/just better ones?)
neur0mans3r said:
P.S. I skipped Eclair and went straight to criminal's CM 6.1.
Click to expand...
Click to collapse
SM-Froyo by any chance?
gen_scheisskopf said:
Main question- how outdated are drivers and touchscreen firmware (if present), and who wrote them (read: can we source newer/not broken/just better ones?)
Click to expand...
Click to collapse
Look in the hardware hacking thread, it looks like we only need to set a smaller active distance value in the controller configuration. I think the default value (8) is used (maybe the active distance value is not even configured explicitly so it defaults to 8).
gen_scheisskopf said:
SM-Froyo by any chance?
Click to expand...
Click to collapse
I used Voku's CM Mod+X for quite some time also, but then the phone would freeze and/or crash when using 3G to surf while commuting. After I lost data due to a damaged /data ext2 partition, I switched to CM7.4. It's really stable for me (over 400h uptime today, battery lasts 3 days since I don't use the phone much).
neur0mans3r said:
Look in the hardware hacking thread, it looks like we only need to set a smaller active distance value in the controller configuration. I think the default value (8) is used (maybe the active distance value is not even configured explicitly so it defaults to 8).
Click to expand...
Click to collapse
I've seen your post. Unfortunately I don't have enough time to dig in sources now
neur0mans3r said:
I used Voku's CM Mod+X for quite some time also
Click to expand...
Click to collapse
...which is based on SpicagenMod
gen_scheisskopf, by any chance, have you tried new 4.0.7? What problems did your G9 have on ICS? I suggest you RMA that s***
Shano56 said:
gen_scheisskopf, by any chance, have you tried new 4.0.7?
Click to expand...
Click to collapse
Nope, last ICS I used was 4.0.6-test4
Shano56 said:
What problems did your G9 have on ICS?
Click to expand...
Click to collapse
-device gets hot quite fast and it's quite hot even when I use not very demanding apps (pdf readers mostly)
-connected with above- shorter battery life
-there are system freezes (reset required) even when using not very demanding apps
-there seems to be a problem with memory management- sometimes using "ram heavy" app (like Firefox or Aurora) shell restarts
Shano56 said:
I suggest you RMA that s***
Click to expand...
Click to collapse
I have to contact service anyway- charger died
Anyway before that I have to return to stock partition layout (and I need tablet right now, still 5 test to pass, all materials are in pdf and reading them on a PC is killing me)
Tell them your GPS doesn't work or something, they'll say its a hardware error and replace it
Shano56 said:
Tell them your GPS doesn't work or something, they'll say its a hardware error and replace it
Click to expand...
Click to collapse
I don't know what is required to replace the device (maybe I'll run an infinite benchamark loop on ICS with tablet wrapped in a blanket or something? )
gen_scheisskopf said:
I don't know what is required to replace the device (maybe I'll run an infinite benchamark loop on ICS with tablet wrapped in a blanket or something? )
Click to expand...
Click to collapse
my otg usb port/charger port stopped working like many others, i simply said the device no longer received a charge (wasn't sure if it was the chargers fault or the tablets fault) and they said to ship the tablet and shipped a replacement to me after they received.